On Wed, Apr 25, 2018 at 02:14:04PM +0200, Ludovic Courtès wrote: > Hello, > > Marius Bakke skribis: > > > Ludovic Courtès writes: > > > >> Hi Mark, > >> > >> Mark H Weaver skribis: > >> > >>> I've successfully updated my x86_64 GuixSD system to my private branch > >>> based on 'core-updates' with recent 'master' and 'staging' merged into > >>> it. This system includes a full GNOME desktop environment plus a few > >>> programs based on Qt. It all works quite well. > >>> > >>> My branch includes a few draft fixes and workarounds that I haven't yet > >>> pushed, but nothing that would require many rebuilds to update later. > >>> > >>> So, I think it might be time to ask Hydra to build all of core-updates, > >>> after staging is merged into it. > >> > >> I agree. There was an issue with cross-compiling ‘bootstrap-tarballs’ > >> that Marius reported a few days ago, which I’m looking into right now. > >> I don’t expect the fix(es) to trigger a full rebuild. > >> > >> If Marius and others don’t object, I’d say go for it! > > > > No objections from me. However I do have a bunch of fairly innocent > > updates in my queue, such as SQLite, Glib and CMake. It's also tempting > > to get rid of that Perl graft. Is it too late for such changes? > > I think it’s OK for sqlite/glib/cmake, but changing Perl would further > delay things, which perhaps is not desirable. > > > Hydra will be busy for a couple of days with 'master' and 'staging', so > > there's little use in starting it immediately. > > It took me a couple of days to reply :-), so maybe we can start the > evaluation now? > > We can also get berlin to build all of ‘core-updates’ if we want. > > Thanks, > Ludo’. > Perl should be straight forward, considering it would've been a normal graft except for the version string part. Unless you're refering to starting the rebuilds further down the tree. -- Efraim Flashner אפרים פלשנר GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351 Confidentiality cannot be guaranteed on emails sent or received unencrypted