On Sat, 16 Sep 2006 01:51:06 -0300
Henry Lenzi [EMAIL PROTECTED] wrote:
A nice portupgrade feature would be to grok UPDATING, and present
you with any such notes before the upgrade occurs.
Mike
I fully agree. It's not the best solution to have an UPDATE file that
is very large and
On 14/09/06 Pete Slagle said:
This one bit me too, but we have only ourselves to blame; there was a
clear (well, pretty clear) warning of the change in /usr/ports/UPDATING.
You would never forget to check UPDATING before running portupgrade
would you? :)
A nice portupgrade feature would
A nice portupgrade feature would be to grok UPDATING, and present you with any
such notes before the upgrade occurs.
Mike
I fully agree. It's not the best solution to have an UPDATE file that
is very large and that is not integrated in the updating process.
UPDATE should be machine-readable,
Hi,
I know the mistake was on my side, I was not carefull enough when
using portupgrade on a production machine but...
Yesterday I froze our system for about one hour when I used
portupgrade to upgrade Samba. It was a very minor upgrade (from 3.0.10
to 3.0.23c,1 I think), but it happens that in
Olivier Nicole wrote:
I know the mistake was on my side, I was not carefull enough when
using portupgrade on a production machine but...
Yesterday I froze our system for about one hour when I used
portupgrade to upgrade Samba. It was a very minor upgrade (from 3.0.10
to 3.0.23c,1 I think),
