Date: Tue, 10 Mar 2015 18:08:31 -0400 (EDT) From: doug@safeport.com To: Mike Clarke <jmc-freebsd2@milibyte.co.uk> Cc: Julien Cigar <jcigar@ulb.ac.be>, freebsd-questions@FreeBSD.org Subject: Re: pkg question upgrade question Message-ID: <alpine.BSF.2.11.1503101756320.87616@fledge.watson.org> In-Reply-To: <20150309204933.3bab9fc2@curlew.lan> References: <alpine.BSF.2.11.1503091510550.72994@fledge.watson.org> <20150309203133.GH6600@mordor.lan> <20150309204933.3bab9fc2@curlew.lan>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 9 Mar 2015, Mike Clarke wrote: > On Mon, 9 Mar 2015 21:31:33 +0100 > Julien Cigar <jcigar@ulb.ac.be> wrote: > >> 1) tigervnc depends on graphics/png (direct dependency) >> 2) you did "pkg upgrade tigervnc" >> 3) there was an upgrade for graphics/png too, with a shared library bump >> 4) pkg upgraded tigervnc, png, and other dependencies >> >> AFAIK pkg doesn't handle this scenario properly as reverse dependencies >> of graphics/png aren't upgraded at the same time... and you end up with >> a semi-"broken" system :( >> >> I hope this will be fixed in a close future as this is pretty annoying >> and limiting > > In the meantime the way to avoid this is to run pkg upgrade before > installing any new package. Ah - I misread this -- yes, I got it thanks > It's quite likely that running pkg upgrade now will rectify the problem. And it did. My initial problem was I did not want to do that remotely. Again, thank you. I had to read your email a couple of times to understand it. The only issue was with xfce/xdm, which has nothing to do with pkg.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.11.1503101756320.87616>