This bug was fixed in the package apt-cacher-ng - 0.7.14-1
---
apt-cacher-ng (0.7.14-1) unstable; urgency=low
* New upstream version
+ prevents background looping (closes: #703296)
+ stop spamming apt-cacher.err when verbosity is not set to debug mode
(closes: #714146
** Branch linked: lp:debian/apt-cacher-ng
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1185547
Title:
Removing package fails to remove user
To manage notifications about this bug go to:
https://bu
It's not entirely clear that the apt-cacher-ng user *should* be removed
on package removal. See
http://wiki.debian.org/AccountHandlingInMaintainerScripts for unresolved
discussion of such ☺.
It's also worth noting that the patch as written will fail if adduser is
installed *and* the apt-cacher-ng
@Eduard: any reason why this can't be done via Debian?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1185547
Title:
Removing package fails to remove user
To manage notifications about this bug go t
The attachment "Little postrm modification to work without adduser
tools" seems to be a debdiff. The ubuntu-sponsors team has been
subscribed to the bug report so that they can review and hopefully
sponsor the debdiff. If the attachment isn't a patch, please remove the
"patch" flag from the attac
Ah, I had no idea that it mattered if the user had a system id. It's
very possible that my configuration management mucked about with the
user id (or maybe even created the user instead of the package creating
the user).
Thanks for clearing up the source of the error.
--
You received this bug no
** Patch added: "Little postrm modification to work without adduser tools"
https://bugs.launchpad.net/ubuntu/+source/apt-cacher-ng/+bug/1185547/+attachment/3690184/+files/use_passwd_tools.diff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed t
It does already but only if deluser tool is available.
However, this is a minor bug because normally it does not hurt even if
the user account remains on the system.
Why this you might ask? Because the installation normally does not fail
since it's a system user account. Unless... somebody (YOU?)
