Felix Yan

I'm rebuilding the package as a quick fix, but the root cause is yet to be discovered.

I have tried to debug a bit. The stuck-at-starting-kernel issue is probably indeed a too-large initramfs: But after I tried to update u-boot as suggested, I could never make it...

Thanks for the investigation. I have successfully booted my D1 with your mentioned modules added to the `MODULES` array. It seems only the `fixed` regulator module was missing from the...

Please try to upstream the change so we don't have to keep it downstream forever :)

Please try to upstream the change so we don't have to keep it downstream forever :)

Release 里我重新打了一份，除了安卓（懒）以外的应该都有了

That's unfortunate ._. I use a file lock on the db server and didn't notice any incomplete db generation etc. Probably I need to keep more logs to find out...

@Ast-x64 这个大概不应该在咱们这里合吧……（我们这边有需要用到吗

The workaround looks rather weird to me, besides it doesn't really fix anything here. Yarn may have some weird timeout measurement that took something other than networking into account. ```...

Hit by this issue again with text-textual,0.3.0.2 built with scientific,0.3.4.11 (no problem with 0.3.4.10, though): ``` haddock: internal error: : hPutChar: invalid argument (invalid character) ```