Re: package upgrade strategy

2017-09-28 Thread Alistair Crooks
On 28 September 2017 at 08:40, Jeff_W wrote: > % cd /pkgsrc/foo/pkg-A > % sudo make clean && sudo make replace > > If the above breaks pkg-C: > > % cd /pkgsrc/foo/pkg-C > % sudo make clean && sudo make clean-depends && sudo make update Orthogonal to this discussion - pkgsrc was

Re: package upgrade strategy

2017-09-28 Thread Jeff_W
> I hope someone can give an answer to this question from a newbie: how can > I handle situations when an already installed package (say A) needs to be > upgraded due to a newly installed package (say B) as it's being a > dependency for it but another already installed package (say C) still >

Re: package upgrade strategy

2017-09-28 Thread Jeff_W
Alistair Crooks wrote: > On 28 September 2017 at 08:40, Jeff_W wrote: > > % cd /pkgsrc/foo/pkg-A > > % sudo make clean && sudo make replace > > > > If the above breaks pkg-C: > > > > % cd /pkgsrc/foo/pkg-C > > % sudo make clean && sudo make clean-depends && sudo

Re: package upgrade strategy

2017-09-28 Thread Jeremy C. Reed
On Thu, 28 Sep 2017, r0ller wrote: > By the way, what kind of difference is indicated by the number in the > 'nb' suffix? Means the original code (upstream source) was not changed. The nb means we may be building or installing it differently (like due to a new patch, new build option, or a

Re: package upgrade strategy

2017-09-28 Thread Brad Spencer
r0ller writes: > Hi Brad, > > I'd do that if it was possible (having the newest versions of all my > packages) but as said, midori is not available any more in the 7.1 package > repo so it cannot be upgraded (not even the same version of midori is > available with just an

Re: package upgrade strategy

2017-09-28 Thread coypu
I suspect this is more fallout from people mis-updating libraries. try manually deleting and adding midori again. I'm hoping it rebuilt the package even though there's no indication to the binary package bits that it changed.

package upgrade strategy

2017-09-28 Thread r0ller
Hi All, I hope someone can give an answer to this question from a newbie: how can I handle situations when an already installed package (say A) needs to be upgraded due to a newly installed package (say B) as it's being a dependency for it but another already installed package (say C) still

Re: package upgrade strategy

2017-09-28 Thread r0ller
Hi Brad, I'd do that if it was possible (having the newest versions of all my packages) but as said, midori is not available any more in the 7.1 package repo so it cannot be upgraded (not even the same version of midori is available with just an updated list of dependencies) and if I upgrade