Martin Schulze <[EMAIL PROTECTED]> writes:
> Steve Langasek wrote:
>> > There is one case in which users can be bitten by this: when using apt-get
>> > dist-upgrade to sarge, so when documenting the woody-sarge upgrade, it
>> > should
>> > be at least mentioned that the user can run into this and
Steve Langasek wrote:
> > There is one case in which users can be bitten by this: when using apt-get
> > dist-upgrade to sarge, so when documenting the woody-sarge upgrade, it
> > should
> > be at least mentioned that the user can run into this and should first
> > upgrade apt to solve this proble
On Sat, Jan 29, 2005 at 02:26:45PM -0800, Steve Langasek wrote:
> > There is one case in which users can be bitten by this: when using apt-get
> > dist-upgrade to sarge, so when documenting the woody-sarge upgrade, it
> > should
> > be at least mentioned that the user can run into this and should
On Sat, 29 Jan 2005, Steve Langasek wrote:
> On Sat, Jan 29, 2005 at 12:24:43PM +0100, Henning Glawe wrote:
>
> > I must have some supernatural powers to always attract the same bug: woodys
> > apt fed too short lists into dpkg and thus broke the configuration of
> > circular depending packages (N
On Sat, Jan 29, 2005 at 12:24:43PM +0100, Henning Glawe wrote:
> I must have some supernatural powers to always attract the same bug: woodys
> apt fed too short lists into dpkg and thus broke the configuration of
> circular depending packages (Note: "dpkg --configure blah blubb", where blah
> depe
Moin,
I must have some supernatural powers to always attract the same bug: woodys
apt fed too short lists into dpkg and thus broke the configuration of
circular depending packages (Note: "dpkg --configure blah blubb", where blah
depends on blubb and blubb depends on blah works; if you try to run it
6 matches
Mail list logo
