On Wed, Apr 06, 2005 at 07:22:41PM +0200, Luk Claes wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
> Andre Lehovich wrote:
> > On Wed, 6 Apr 2005, Frank Lichtenheld wrote:
> >
> >>- It is a apt-get bug only, aptitude handles the same situation just
> >> fine. But both apt-get from wood
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Andre Lehovich wrote:
> On Wed, 6 Apr 2005, Frank Lichtenheld wrote:
>
>>- It is a apt-get bug only, aptitude handles the same situation just
>> fine. But both apt-get from woody and sarge bail out.
>
>
> Is apt-get a supported upgrade route from W
On Wed, 6 Apr 2005, Frank Lichtenheld wrote:
> - It is a apt-get bug only, aptitude handles the same situation just
> fine. But both apt-get from woody and sarge bail out.
Is apt-get a supported upgrade route from Woody to Sarge?
The release notes [1] recommend using aptitude instead.
[1]
http
On Wednesday 06 April 2005 11:26 am, Frank Lichtenheld wrote:
> - It is a apt-get bug only, aptitude handles the same situation just
> fine. But both apt-get from woody and sarge bail out.
That's really weird, because aptitude does nearly the same thing as apt-get
when calculating upgrades.
On Wed, Apr 06, 2005 at 04:09:08PM +0200, Wichert Akkerman wrote:
> I just looked at upgrading a server from woody to sarge and the result
> was, well, interesting. The output from "apt-get -o
> Debug::pkgProblemResolver=true dist-upgrade" starts off with:
>
> Investigating perl
> Package perl has
I just looked at upgrading a server from woody to sarge and the result
was, well, interesting. The output from "apt-get -o
Debug::pkgProblemResolver=true dist-upgrade" starts off with:
Investigating perl
Package perl has broken dep on libterm-readline-perl-perl
Considering libterm-readline-perl-
6 matches
Mail list logo