guix-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH] gnu: boost: Update to 1.61.0.


From: Eric Bavier
Subject: Re: [PATCH] gnu: boost: Update to 1.61.0.
Date: Fri, 23 Sep 2016 12:05:12 -0500
User-agent: Roundcube Webmail/1.0.6

On 2016-09-22 16:16, Marius Bakke wrote:
Andreas Enge <address@hidden> writes:

On Wed, Sep 21, 2016 at 06:11:31PM +0200, Andreas Enge wrote:
boost has quite a few dependencies, as Ricardo already pointed out, and in my experience tends to be a bit fragile. So maybe the best option would be to create a boost-update branch and have it built on hydra to see whether there are problems. It not, one could then cherry-pick the commit to master.

I replied before reading all the messages in that thread. Of course if Eric has tried the commit locally and tested that nothing breaks, this could be
pushed to master directly.

Should this not be pushed to core-updates? `guix refresh -l` reports:

Building the following 190 packages would ensure 395 dependent packages
are rebuilt: [...]

That's kind of on the edge of what's acceptable for master, as long as hydra isn't already overloaded, which it wasn't in this case.

That will take a while on Hydra, and in the mean time anyone trying to
install any dependent (or sub-dependent) package will have to compile
them locally.

It's already finished rebuilding those dependents.

Unless there is a security issue, isn't this exactly what core-updates
is for?

Indeed, but for security updates grafts are preferable.

Is `guix refresh recursive`?

Yes.

--
`~Eric



reply via email to

[Prev in Thread] Current Thread [Next in Thread]