Date: Thu, 25 Aug 2011 03:11:44 -0700 From: Doug Barton <dougb@FreeBSD.org> To: Florian Riehm <florian.riehm@unibw.de> Cc: freebsd-ports@freebsd.org Subject: Re: Update of libnotify and libproxy failed Message-ID: <4E561FE0.4000509@FreeBSD.org> In-Reply-To: <4E561DAE.3040609@unibw.de> References: <4E55F8DA.5060501@gwdg.de> <4E5605CA.5090806@gmx.de> <4E5617EF.3060801@gwdg.de> <4E5619AA.6040805@gmx.de> <4E561DAE.3040609@unibw.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On 08/25/2011 03:02, Florian Riehm wrote: > I tried Dougs way of upgrading and got in trouble too. Brasero don't > build because of a similar failture like Rainers Error during the > py-gnome-desktop build. You have to update libnotify and libproxy first > because some ports don't build with a new libnotify version and an old > libproxy versin. > > The following way works for me: > > # portmaster devel/libnotify net/libproxy > # portmaster -r libnotify-0 > # portmaster -r libproxy-0 You could add the -R option to the two -r lines to avoid having to rebuild the ports again. > # portmaster -a Having given this some more thought, you could do a poor man's version of multiple -r by doing this: pkg_info -qR libnotify-0\* libproxy-0\* | sort -u > list portmaster libnotify-0 libproxy-0 portmaster `cat list` hth, Doug -- Nothin' ever doesn't change, but nothin' changes much. -- OK Go Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.com/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4E561FE0.4000509>