On Sun, Jun 17, 2007 at 09:59:25PM -0400, Felipe Sateler <[EMAIL PROTECTED]>
was heard to say:
> On Sunday 17 June 2007 20:22:20 Daniel Burrows wrote:
> > The problem can be fixed by reading/writing the installation
> > states again after step 2, at the cost of making installs take
> > longer.
On Sunday 17 June 2007 20:22:20 Daniel Burrows wrote:
> Ooh, that's a nasty one. To make it more fun, it occurs in the
> previous releases of aptitude as well.
>
> I think I have a pretty good idea what's going on.
>
> (1) You install wesnoth with apt-get. So far so good.
> (2) You re
It may be of interest that when unmarking the deletions, dependencies aren't
unmarked. So, if for example foo brought libfoo in, I unmark foo for removal,
libfoo isn't unmarked, I have to manually do that.
--
Felipe Sateler
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subje
Ooh, that's a nasty one. To make it more fun, it occurs in the
previous releases of aptitude as well.
I think I have a pretty good idea what's going on.
(1) You install wesnoth with apt-get. So far so good.
(2) You remove wesnoth with aptitude, *from the command-line*.
aptit
Package: aptitude
Version: 0.4.5.2-1
Severity: normal
This is the way to reproduce it:
apt-get install package
aptitude remove package
apt-get install package
Now if you enter the aptitude ui, package will be marked for removal.
-- System Information:
Debian Release: lenny/sid
APT prefers uns
5 matches
Mail list logo
