[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#266959: marked as done (aptitude: remove packages in proper order)

Your message dated Wed, 14 Sep 2011 19:34:17 +0200
with message-id <CAAZ6_fDgsrxgvhLi6SCBR4ry9eGWL8NkUw9Sw44BeuYSvqXG1w@mail.gmail.com>
and subject line Close: "apt-get --purge remove ..." purges package before uninstalling depending package
has caused the Debian Bug report #262887,
regarding aptitude: remove packages in proper order
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 owner@bugs.debian.org
immediately.)


-- 
262887: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=262887
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: aptitude
Version: 0.2.15.2-1
Severity: normal

I seem to recall in apt-get, the packages are removed in proper order
so the user sees no disturbing "dependency problems" messages. Nor is
there a danger in the case of interrupt, that there will be a broken
packages state, or whatever it's called.

# aptitude purge gedit
The following packages will be REMOVED:
  gedit gedit-common 
0 packages upgraded, 0 newly installed, 2 to remove and 328 not upgraded.
Do you want to continue? [Y/n/?] 
Writing extended state information... Done
dpkg: gedit: dependency problems, but removing anyway as you request:
 gedit-common depends on gedit.
(Reading database ... 163431 files and directories currently installed.)
Removing gedit ...
Purging configuration files for gedit ...
(Reading database ... 163401 files and directories currently installed.)
Removing gedit-common ...

By the way, the following lines have trailing blanks:

Reading Package Lists... Done             
Building Dependency Tree       
Reading extended state information

--- End Message ---
--- Begin Message --- 
> indeed. Seems like apt is ignoring policy 7.2
> | The Depends field should also be used if the postinst, prerm or postrm
> | scripts require the package to be present in order to run.

The (current) policy in this section also says:
> Finally, the Depends field should be used if the depended-on package is
> needed by the postrm script to fully clean up after the package removal.
> There is no guarantee that package dependencies will be available when
> postrm is run, but the depended-on package is more likely to be available
> if the package declares a dependency (particularly in the case of postrm
> remove). The postrm script must gracefully skip actions that require a
> dependency if that dependency isn't available.

Adding that all these removes happen in the same dpkg call it's in the
end dpkg who decides which packages is removed first, but as either
way is valid according to policy this is not a bug.


Given that ordering is constantly improved in dpkg and APT it's likely
that this non-issue is even already fixed. I am therefore closing this
"bug" now, but feel free to reopen it, if i am on the wrong track.


Best regards

David Kalnischkies

--- End Message ---
Reply to: