Date: Wed, 23 Mar 2005 21:28:20 +0100 (CET) From: Andreas Davour <ante@Update.UU.SE> To: Marco Beishuizen <marco@beishuizen.info> Cc: freebsd-questions@freebsd.org Subject: Re: Acroread7 Message-ID: <Pine.LNX.4.62.0503232127190.15221@Psilocybe.Update.UU.SE> In-Reply-To: <20050323202358.C715@yokozuna.lan> References: <Pine.LNX.4.62.0503231249590.11985@Psilocybe.Update.UU.SE> <Pine.LNX.4.62.0503232006440.15221@Psilocybe.Update.UU.SE> <20050323202358.C715@yokozuna.lan>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 23 Mar 2005, Marco Beishuizen wrote: > On stardate Wed, 23 Mar 2005, the wise Andreas Davour entered: > >> Exactly the same. >> >> As Erik (et al) wrote, it will all be pulled in and resolved as >> dependencies if you have a sufficienyly up-to-date ports tree. >> >> Kind of annyoing that it wasn't caught before it was comitted at all, but >> considering the total confusion that reigns right now with two different >> acroread ports it's just what can be expected. >> >> I did a cvsup 30 minutes ago, and then it worked. >> >> /Andreas > > Hmm I also did a cvsup, but it makes no difference, I still get the sam > error. I guess I have an other problem on my system. You'll have to pkg_delete the old acroread port, and I did a "make clean" as well. Try that, and it might work. /Andreas -- A: Because it fouls the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.LNX.4.62.0503232127190.15221>