@Marius,
Sorry, I expected the original bug report to at a minimum tell me what
package version and Ubuntu release were affected, which is why I jumped
straight away to the standard template response asking for apport-
collect, as this would normally fill all of that information in. I
didn't notice that you had purged the package, and apport-collect them
won't be able to report its installed version, etc. I'm not sure about
your failure in comment #3.
@Rolf,
Thanks, that explains this bug. I agree that it's currently expected
behaviour, but I do think it's a little buggy that the config file is
still active after the package is removed. I wonder if it might be
possible for /etc/apt/apt.conf.d/30autoproxy to test for /usr/share
/squid-deb-proxy-client/apt-avahi-discover before calling it or
something?
Since there might be a little scope for user experience improvement
here, I'll leave this open until someone determines if this is possible
or not.
** Changed in: squid-deb-proxy (Ubuntu)
Importance: Undecided => Low
** Summary changed:
- apt-get removing squid-deb-proxy-client leaves a stale config file
+ Removing squid-deb-proxy-client leaves a stale but active config file,
breaking apt
** Changed in: squid-deb-proxy (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to squid-deb-proxy in Ubuntu.
https://bugs.launchpad.net/bugs/1501217
Title:
Removing squid-deb-proxy-client leaves a stale but active config file,
breaking apt
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/squid-deb-proxy/+bug/1501217/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
