Am 16.09.2010 01:30, schrieb Barbara:
I've just run portupgrade -ap, after getting the new autotools and reading
UPDATING.
From what I can understand, as it's not a version bump but a new port (I
realized it too late...). So maybe I should have used something like:
# portupgrade -o
On 16/09/2010 11:43:04, Matthias Andree wrote:
Am 16.09.2010 01:30, schrieb Barbara:
I've just run portupgrade -ap, after getting the new autotools and reading
UPDATING.
From what I can understand, as it's not a version bump but a new port (I
realized it too late...). So maybe I should
Hi, all--
On Sep 15, 2010, at 4:43 PM, Barbara wrote:
About my previous mail, shouldn't the upgrade be handled by the entry in
MOVED? Is it a portupgrade problem?
Is the rebuild of ports like xmms or libX11 really necessary after a new
version of autoconf?
It looks like maybe a repocopy
On Sep 15, 2010, at 4:43 PM, Barbara wrote:
About my previous mail, shouldn't the upgrade be handled by the entry in
MOVED? Is it a portupgrade problem?
Is the rebuild of ports like xmms or libX11 really necessary after a new
version of autoconf?
With sweeping ports such as autotools, the
Hi, Ade--
On Sep 15, 2010, at 5:13 PM, Ade Lovett wrote:
On Sep 15, 2010, at 18:48 , Chuck Swiger wrote:
It looks like maybe a repocopy is going on (or has gone wrong), since it is
pointing to autoconf-2.62:
You need to update your ports tree. Makefile is revision 1.77, not 1.75 as
you
