Re: Wrongly cached eggs
Mario Domenech Goulart via Chicken-users <[email protected]>
| Newsgroups | gmane.lisp.scheme.chicken |
|---|---|
| Message-ID | <[email protected]> |
On Thu, 14 Aug 2025 21:07:43 +0200 Mario Domenech Goulart via Chicken-users <[email protected]> wrote: > On Wed, 13 Aug 2025 19:43:19 +0200 Mario Domenech Goulart via Chicken-users <[email protected]> wrote: > >> tl;dr: Some eggs have been wrongly cached and some caches are still in a >> broken state (see more details below). To work around the issue when >> installing eggs with chicken-install, set call-cc as the primary server >> in the $PREFIX/share/chicken/setup.defaults file (i.e., put >> `(server "call-cc")' _before_ `(server "kitten-technologies")'. You >> might need to run `chicken-install -purge` to remove broken local caches. >> >> Due to what we believe to have been a glitch in GitHub, some eggs hosted >> there have been incorrectly cached on the 8th of August. During some >> hours of that day, GitHub seems to have served .release-info files from >> wrong branches. >> >> Some versions of some eggs are CHICKEN major version-specific, and they >> use branches as a way to map releases to their corresponding compatible >> CHICKEN version. Since GitHub served .release-info files from wrong >> branches, that compatibility map was broken. >> >> The following eggs have been affected: >> >> * concurrent-native-callbacks >> * gochan >> * sendfile >> >> sendfile is particularly problematic because many eggs depend on it and >> the sendfile version for CHICKEN 6 ended up being cached for CHICKEN 5, >> which leads to breakages, as the sendfile for CHICKEN 6 is not >> compatible with CHICKEN 5. >> >> The caches in the call-cc.org server have been fixed, but at the time of >> this writing our main egg server (chicken.kitten-technologies.co.uk) is >> still serving wrongly cached eggs. >> >> The content of the git repositories [0] and egg tarballs [1] have still >> not been fixed (they should be fixed in the next days). >> >> [0] https://wiki.call-cc.org/how-to-obtain-the-source-code-of-eggs#all-eggs >> [1] https://code.call-cc.org/egg-tarballs/ >> >> See the suggested workaround in the tl;dr to make chicken-install fetch >> eggs from the call-cc.org server, whose caches have been fixed. >> >> Apologies for the inconveniences this issue might have caused to your >> workflows. > > Update: the content of the git repositories [0] and egg tarballs [1] have > been fixed. > > [0] https://wiki.call-cc.org/how-to-obtain-the-source-code-of-eggs#all-eggs > [1] https://code.call-cc.org/egg-tarballs/ Update: the caches in the main egg server have been fixed. With that, all cache-related problems reported in this thread have been fixed. All the best. Mario -- https://parenteses.org/mario