Online Slitaz Next/Next64 Cooker: Too many failed cooks

(4 posts) (2 voices)

Tags:

No tags yet.

mistfire

offline
Member

I noticed that online Slitaz Next Cooker (http://cook.slitaz.org/next/) and Next64 Cooker (http://cook.slitaz.org/next64/) was on the move, I noticed that there are many failed cooks. When I checked the logs, the most common problem on the failed cooks are here are follows

1. Missing GTK+ package (The same problem as the rolling one which was fixed)
2. Missing linux source code (especially linux-drm)
3. Missing kernel components (Some packages receipt look for files on /lib/modules/[kernel version]/)
4. Missing aufs patch
5. It always shows this error message
stat: can't read file system information for '[filename]': No such file or directory

Posted 4 years ago #
mistfire

offline
Member

When I checked the compile logs of GTK+ applications that failed to compile on both next and next64. libffi was missing upon compiling GTK+ applications

Posted 4 years ago #
mojo

offline
Key Master

Out of courtesy and consideration for other slitaz users a contributor with hg credentials should never commit a package update or change without successfully building and testing the updated package on their own computer.
In most cases a failed build removes the package from tazpkg database files.
While the old package still exists on the mirror, tazpkg shows nothing Available.

Posted 4 years ago #
mistfire

offline
Member

It seems no one ever tried to fix these next/next64 online cooker issues.

Posted 4 years ago #

Reply

You must log in to post.