Your message dated Tue, 8 Sep 2015 19:35:03 +0100
with message-id <[email protected]>
and subject line Re: aptitude: unable to purge a package
has caused the Debian Bug report #710587,
regarding aptitude --refresh-state
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
710587: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=710587
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: aptitude
Just like
dpkg --update-avail, --merge-avail Packages-file
Update dpkg's and dselect's idea of...
There needs to be some aptitude command, that will relieve aptitude of
mistaken notions:
# aptitude purge ~c
The following packages will be REMOVED:
iproute{p}
0 packages upgraded, 0 newly installed, 1 to remove and 8 not upgraded.
Need to get 0 B of archives. After unpacking 0 B will be used.
Do you want to continue? [Y/n/?]
dpkg: warning: ignoring request to remove iproute which isn't installed
--- End Message ---
--- Begin Message ---
2015-09-08 17:45 shirish शिरीष:
So I am not sure about what was wrong at the time, but I think that this
bug is not present anymore.
Dear Manuel,
I would suggest you just close the bug, it's too far in the back now.
OK, thanks.
Also, I asked about this to the dpkg maintainer and he hinted that there
was a time 1 or 2 years ago when apt and aptitude appended the main arch
to packages even when they were arch:all or dpkg was not multiarch
ready, or some similar problems.
To try to reproduce it again, I also installed, removed and then purged
postgresql-common and postgresql-client-common, which are arch:all (to
see if it made any difference), but also I couldn't reproduce it and
everything works fine with 0.7.1-1.
Lastly, nobody reported it recently, despite the stable release being
out for a few months.
So, all in all, I agree that this can be closed now, doing it. I am
sure that somebody will reopen or create a new bug report if it
continues to be an issue in some use case; and in the meantime there are
plenty of other issues to fix...
Cheers.
--
Manuel A. Fernandez Montecelo <[email protected]>
--- End Message ---
_______________________________________________
Aptitude-devel mailing list
[email protected]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/aptitude-devel
