I had to do an update on one of our unstable machines today. It is (was)
running Mailman. I was using aptitude and actually marked Mailman as "hold"
but it upgraded it anyway. When Mailman tried to install, I got the
following errors:
--begin errors
Preconfiguring packages ...
Traceback (most re
On Sunday 04 January 2004 03:54, Naomi Ridge wrote:
> --- Martin Büchler <[EMAIL PROTECTED]> wrote: > On
> Saturday 03 January 2004 22:59, Naomi Ridge
>
> > You should set the loopback ip (i.e dont let it
> > unconfigured but add "address
> > 127.0.0.1" to /etc/network/interfaces for the lo
> > de
* "Trey Nolen"
| I haven't been able to remove the package either (same sort of errors). Has
| anyone seen this issue with Mailman on unstable? Got any recommendations for
| a fix? I don't want to purge because I have a LOT of configuration/data in
| Mailman.
python2.3 is broken, not mailman.
> * "Trey Nolen"
>
> | I haven't been able to remove the package either (same sort of errors).
Has
> | anyone seen this issue with Mailman on unstable? Got any recommendations
for
> | a fix? I don't want to purge because I have a LOT of configuration/data
in
> | Mailman.
>
> python2.3 is broken
On Sat, 3 Jan 2004, Naomi Ridge wrote:
> That doesn't seem to be the problem - the loopback
> device appears to be up and running:
>
> > ifconfig
>
> [snip]
>
> loLink encap:Local Loopback
> UP LOOPBACK RUNNING MTU:16436 Metric:1
> RX packets:216 errors:0 dropped:0 ov
* "Trey Nolen"
| Is there a way to go back to the older python?
downgrading should work fine; try snapshot.debian.net, or testing for
the older release.
--
Tollef Fog Heen,''`.
UNIX is user friendly, it's just picky about who its friends
6 matches
Mail list logo
