| Message ID | cover.1677997633.git.vivien@planete-kraus.eu |
|---|---|
| Headers | show |
| Series | Update GNOME Builder to 43.6 | expand |
Am Sonntag, dem 05.03.2023 um 07:27 +0100 schrieb Vivien Kraus: > Dear guix, > > Thank you so much for the website at qa.guix.gnu.org. It told me that > libpanel description was not wrapped properly, and that a few > packages unrelated to GNOME Builder failed to build. I believe I got > them working again. It still reports some build errors (are those cached by chance?), but more importantly, there are new profile collisions. I think you'd have to build a version of gtk that propagates glib-next and propagate that from gtksourceview-5 to make things really work. Having typed that, I need to wash my hands. Cheers
Hi, Le dimanche 05 mars 2023 à 08:35 +0100, Liliana Marie Prikler a écrit : > It still reports some build errors (are those cached by chance?), but > more importantly, there are new profile collisions. I think you'd > have > to build a version of gtk that propagates glib-next and propagate > that > from gtksourceview-5 to make things really work. > > Having typed that, I need to wash my hands. I think I’ll pass, and wait for an update of glib to land in guix. Thank you anyway! Vivien
Hello, Liliana Marie Prikler <liliana.prikler@gmail.com> skribis: > Am Sonntag, dem 05.03.2023 um 07:27 +0100 schrieb Vivien Kraus: >> Dear guix, >> >> Thank you so much for the website at qa.guix.gnu.org. It told me that >> libpanel description was not wrapped properly, and that a few >> packages unrelated to GNOME Builder failed to build. I believe I got >> them working again. > It still reports some build errors (are those cached by chance?), but > more importantly, there are new profile collisions. We don’t see at <https://qa.guix.gnu.org/issue/61968> which package those lint warnings relate to. If those warnings are not for ‘gnome-builder’ itself, then that’s probably fine in that one can still install ‘gnome-builder’ in their profile. Vivien, could you check? qa.guix can be quite demanding at times. :-) Thanks, Ludo’.
Am Donnerstag, dem 16.03.2023 um 22:56 +0100 schrieb Ludovic Courtès: > Hello, > > Liliana Marie Prikler <liliana.prikler@gmail.com> skribis: > > It still reports some build errors (are those cached by chance?), > > but more importantly, there are new profile collisions. > > We don’t see at <https://qa.guix.gnu.org/issue/61968> which package > those lint warnings relate to. True, but gnome-builder is not the only package changed here, gnome- text-editor and gnome-calculator are too. > If those warnings are not for ‘gnome-builder’ itself, then that’s > probably fine in that one can still install ‘gnome-builder’ in their > profile. It turns out that both gnome-text-editor and gnome-calculator fail to find the improperly propagated glib-next. Speaking of which, a stable glib 2.76.0 has been released, that we should probably use everywhere, but that'd require a lot of rebuilds. Should we do a gnome-team branch, so that we can do this in one nice swoop? (Apropos gnome-team, there isn't a formal gnome team yet, but I think one should be formed covering gnome.scm, gnome-xyz.scm and gstreamer.scm, perhaps glib-or-gtk-build-system and meson-build-system as well.) Cheers
Le vendredi 17 mars 2023 à 06:22 +0100, Liliana Marie Prikler a écrit : > > If those warnings are not for ‘gnome-builder’ itself, then that’s > > probably fine in that one can still install ‘gnome-builder’ in > > their > > profile. > It turns out that both gnome-text-editor and gnome-calculator fail to > find the improperly propagated glib-next. Speaking of which, a > stable > glib 2.76.0 has been released, that we should probably use > everywhere, > but that'd require a lot of rebuilds. Should we do a gnome-team > branch, so that we can do this in one nice swoop? Yes, please! I can help for the easy things and for testing. GNOME 44 is around the corner, it would be a good strategy to start looking at it now to know what problems lie ahead ;) Best regards, Vivien
Hi, Liliana Marie Prikler <liliana.prikler@gmail.com> skribis: > It turns out that both gnome-text-editor and gnome-calculator fail to > find the improperly propagated glib-next. Speaking of which, a stable > glib 2.76.0 has been released, that we should probably use everywhere, > but that'd require a lot of rebuilds. Should we do a gnome-team > branch, so that we can do this in one nice swoop? Sounds like a good idea! > (Apropos gnome-team, there isn't a formal gnome team yet, but I think > one should be formed covering gnome.scm, gnome-xyz.scm and > gstreamer.scm, perhaps glib-or-gtk-build-system and meson-build-system > as well.) Yeah, agreed. Thanks, Ludo’.
Le jeudi 16 mars 2023 à 22:56 +0100, Ludovic Courtès a écrit : > If those warnings are not for ‘gnome-builder’ itself, then that’s > probably fine in that one can still install ‘gnome-builder’ in their > profile. > > Vivien, could you check? Unfortunately, it does not work: guix install: error: profile contains conflicting entries for glib guix install: error: first entry: glib@2.75.4 /gnu/store/49ah85w38vnz7y2i3hqzpq5rlp9v9nhl-glib-2.75.4 guix install: error: ... propagated from gtksourceview@5.7.2 guix install: error: ... propagated from gnome-builder@43.6 guix install: error: second entry: glib@2.70.2 /gnu/store/z6c305j8xvhvizvnyp5961gssmw3zjr2-glib-2.70.2 guix install: error: ... propagated from fluidsynth@2.2.4 hint: Try upgrading both `gnome-builder' and `fluidsynth', or remove one of them from the profile. Vivien