On Thu, Jan 15, 2009 at 07:17:27AM +0100, Zbigniew Szalbot wrote:
>
> Hello,
>
> >> 1/ backing up the hacked [mailman] files and restoring them later (but I
> >> will
> >> overwrite the newer files with older ones perhaps breaking something).
> >> 2/ making them read only (but the end result will
Hello,
>> 1/ backing up the hacked [mailman] files and restoring them later (but I
>> will
>> overwrite the newer files with older ones perhaps breaking something).
>> 2/ making them read only (but the end result will be the same and
>> upgrading as root I will overwrite them anyway).
>
> Keep in
On Jan 14, 2009, at 12:03 PM, Zbigniew Szalbot wrote:
1/ backing up the hacked [mailman] files and restoring them later
(but I will
overwrite the newer files with older ones perhaps breaking something).
2/ making them read only (but the end result will be the same and
upgrading as root I will
On Wed, Jan 14, 2009 at 07:03:02PM +0100, Zbigniew Szalbot wrote:
> Dear all,
>
> I am now full into planning the 7.0-RELEASE to 7.1-RELEASE upgrade. I
> know that at the end of the day it will also mean upgrading all ports
> (portupgrade -af).
Not necessarily. Upgrading all ports is only mandat
Zbigniew Szalbot wrote:
> Dear all,
>
> I am now full into planning the 7.0-RELEASE to 7.1-RELEASE upgrade. I
> know that at the end of the day it will also mean upgrading all ports
> (portupgrade -af). I have one port - mailman - which I have customized
> a lot and do not really want to upgrade i
Dear all,
I am now full into planning the 7.0-RELEASE to 7.1-RELEASE upgrade. I
know that at the end of the day it will also mean upgrading all ports
(portupgrade -af). I have one port - mailman - which I have customized
a lot and do not really want to upgrade it as it will most likely mean
I will