[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: HEADS-UP: /bin/sh memory management bug fixes committed
Date: Sun, 18 Jun 2017 19:28:19 +0000
From: "Thomas Mueller" <mueller6725%twc.com@localhost>
| What do you use instead of pkg_rolling-replace, while waiting for
| portupgrade and portmaster to be imported from FreeBSD ports (wishful
| What do you do when you want to update many packages?
I have my own scripts from before pkg_rolling-replace (or almost any of the
various other tools) existed. They work out what I have installed that
is out of date (well, lintpkgsrc does that), figure out the dependencies,
sort them all into the correct build order, and build binary packages for
all of the packages that need rebuilding.
Once that's all done (which can take time, as not all packages
always build properly all the time...) I just install a complete new set of
packages into an empty /usr/pkg from the binary packages I have built.
This step only takes a few minutes. If there's a problem, I just
move the old /usr/pkg back, while I fix (or wait for someone else to fix)
whatever went wrong.
| Was graphics/graphite2 one of the packages seen to have problems?
No - or more correctly, that isn't one that I knew of.
| Trying to configure that segfaulted and dumped core, no informative log.
That would be the kind of problem I expect the sh bug may have caused.
That is, just flat out breakage (the bug was subtle, and rare, the effects
So for that, just try again with a new shell (and a rebuilt libtool I
would suggest as well.)
I will try building it on my test system, if it doesn't take too long
(including whatever dependencies it needs that aren't already there from
my other pkgsrc building tests.)
| My last system update dates were Jun 14 (i386) and Jun 11 (amd64),
| within the vulnerable time for /bin/sh bugs.
Main Index |
Thread Index |