Date: Fri, 17 Oct 2008 10:10:50 +0200 From: Erik Trulsson <ertr1013@student.uu.se> To: Colin Brace <cb@lim.nl> Cc: freebsd-questions@freebsd.org Subject: Re: updating a port with problems (libxml2) Message-ID: <20081017081050.GA99756@owl.midgard.homeip.net> In-Reply-To: <20028504.post@talk.nabble.com> References: <20028504.post@talk.nabble.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Oct 17, 2008 at 01:01:09AM -0700, Colin Brace wrote: > > Hi all, > > I use portsnap to keep the port tree of my FreeBSD 7 box up to date. > According to portaudit, which I run nightly, there is a problem with the > current version of libxml2. So, as usual, I run "sudo portsnap fetch && > sudo portsnap update", and then: > > $ cd /usr/ports/textproc/libxml2 > $ sudo make deinstall > $ sudo make reinstall clean > > But this last command results in an error: > > ===> libxml2-2.6.32 has known vulnerabilities: > => libxml2 -- two vulnerabilities. > Reference: > <http://www.FreeBSD.org/ports/portaudit/d71da236-9a94-11dd-8f42-001c2514716c.html>; > => Please update your ports tree and try again. > > It would appear that the port has not yet been updated. Is this some > temporary glitch? Otherwise, the approach I use is not very robust, since I > have now managed to deinstall a library upon which a dozen or so programs > depend. However, this is the first time this has happened. > > Comments, suggestions most welcome. > Sometimes it takes a while after a problem has been found with a port until a fixed version is available in the ports tree. In the worst case the port might never get fixed. So, no, your approach is not very robust. -- <Insert your favourite quote here.> Erik Trulsson ertr1013@student.uu.se
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20081017081050.GA99756>