You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With buster's metacity (3.30), when SLB boots, after the choose-your-colors page, it opens the journal, with no apparent way to get out. This makes it unusable for anyone who doesn't know the F3 trick to get to the Favourites page.
I suggest documenting how to work round this in README.md of which the simplest is something like:
Including these packages in the sugar-live-build distro would change its license from public domain to mixed, with the obbligation to provide or say where to get and how to build the packages, as well as being far larger than sugar-live-build itself.
After the workaround is documented, the build script could be modified to download them itself, but from where? Debian does not appear to keep a copy of all packages ever, and using a third-party site adds an extra possible point of failure/insecurity. Can sugarlabs host them temporarily?
Many thanks @quozl for helping find and work round this
The text was updated successfully, but these errors were encountered:
As this is a problem with Metacity, not with Sugar Live Build, I'll like to close this once documentation for the situation is merged. I suggest a "Debian Buster" section.
Debian does keep copies. https://snapshot.debian.org is a "wayback machine" for the Debian archive. I'm not sure if the later packages can be used on Debian Buster though, as dependency naming may have changed.
With buster's metacity (3.30), when SLB boots, after the choose-your-colors page, it opens the journal, with no apparent way to get out. This makes it unusable for anyone who doesn't know the F3 trick to get to the Favourites page.
I suggest documenting how to work round this in README.md of which the simplest is something like:
Including these packages in the sugar-live-build distro would change its license from public domain to mixed, with the obbligation to provide or say where to get and how to build the packages, as well as being far larger than sugar-live-build itself.
After the workaround is documented, the build script could be modified to download them itself, but from where? Debian does not appear to keep a copy of all packages ever, and using a third-party site adds an extra possible point of failure/insecurity. Can sugarlabs host them temporarily?
Many thanks @quozl for helping find and work round this
The text was updated successfully, but these errors were encountered: