Your message dated Sun, 16 Apr 2023 18:49:18 +0200
with message-id
<caknhny_tqzfjutqogrsvxkwoajg+atlh63nmg2sm1eqtyfr...@mail.gmail.com>
and subject line Re: Bug#781175: packagekit: when purging packagekit it leaves
some files in /etc/Packagekit behind.
has caused the Debian Bug report #781175,
regarding packagekit: when purging packagekit it leaves some files in
/etc/Packagekit behind.
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.)
--
781175: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=781175
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: packagekit
Version: 1.0.1-2
Severity: normal
Dear Maintainer,
I was purging packagekit and it still left some things. See
Removing packagekit (1.0.1-2) ...
D000001: ensure_diversions: same, skipping
D000001: removal_bulk package packagekit:amd64
D000001: ensure_diversions: same, skipping
D000001: removal_bulk cleaning info directory
D000001: removal_bulk purging? foundpostrm=1
Purging configuration files for packagekit (1.0.1-2) ...
D000001: ensure_diversions: same, skipping
dpkg: warning: while removing packagekit, directory '/etc/PackageKit'
not empty so not removed
D000001: removal_bulk purge done, removing list
'/var/lib/dpkg/info/packagekit.list'
D000001: removal_bulk purge done, removing postrm
'/var/lib/dpkg/info/packagekit.postrm'
D000001: removal done
I had to manually remove the contents within /etc/Packagekit.
Don't know if this is an oversight or a feature ? It would be nice if
all the events and transactions are moved to apt in case packagekit is
purged.
-- System Information:
Debian Release: 8.0
APT prefers testing
APT policy: (600, 'testing'), (500, 'testing-updates'), (1,
'experimental'), (1, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_IN, LC_CTYPE=en_IN (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--
Regards,
Shirish Agarwal शिरीष अग्रवाल
My quotes in this email licensed under CC 3.0
http://creativecommons.org/licenses/by-nc/3.0/
http://flossexperiences.wordpress.com
EB80 462B 08E1 A0DE A73A 2C2F 9F3D C7A4 E1C4 D2D8
--- End Message ---
--- Begin Message ---
Hi!
Checking with piuparts and many local installations and purges, the
directory is indeed cleanly removed all the time, *unless* a user has
indeed put something there. On my own system, this was a
"Vendor.conf.dpkg-old" file from dpkg comparing diffs to a
configuration file in the past.
I am guessing this must have been a similar case here.
I'm closing this bug for now, but feel free to reopen it in case this
is still an issue.
Cheers,
Matthias
--
I welcome VSRE emails. See http://vsre.info/
--- End Message ---
