Your message dated Wed, 14 Nov 2018 16:14:44 +0100 with message-id <a36d1b58-f5f1-24b7-7e21-4df15034b...@siduction.org> and subject line Re: connman: unable to upgrade 1.33-1 -> 1.36-1 has caused the Debian Bug report #913730, regarding connman: unable to upgrade 1.33-1 -> 1.36-1 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 ow...@bugs.debian.org immediately.) -- 913730: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913730 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: connman Version: 1.36-1 Severity: grave Justification: causes non-serious data loss Hi! Upgrade of connman from 1.33-1 to 1.36-1 fails. Unable to upgrade normally, used full-resolver to remedy. This upgraded the package but removed /etc/resolv.conf and deconfigured the wireless network interface as well as rfkilled it. Thanks for your work. -- Per -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 4.8.0-1-686-pae (SMP w/2 CPU cores) Locale: LANG=sv_SE.UTF-8, LC_CTYPE=sv_SE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages connman depends on: ii dbus 1.10.12-1 ii iptables 1.8.1-2 ii libc6 2.27-6 ii libdbus-1-3 1.10.12-1 ii libglib2.0-0 2.50.2-2 ii libgnutls30 3.5.6-7 ii libreadline7 7.0-1 ii libxtables12 1.8.1-2 ii lsb-base 9.20161101 Versions of packages connman recommends: ii bluez 5.43-1 ii ofono 1.18-1 ii wpasupplicant 2.5-2+v2.4-3+b1 Versions of packages connman suggests: pn connman-vpn <none> -- no debconf information
--- End Message ---
--- Begin Message ---Hi Per, the bug you found is valid, but it might be that you are a little bit late to that special party - nevermind, missing a fix for two years might happend. Fixed in: connman (1.33-3) unstable; urgency=high * Fix connman.postrm (Closes: #849345) - don't remove state-dir unless when purge - make removing the resolv.conf symlink more sophisticated * Suggests: connman-vpn -- Alf Gaida <aga...@siduction.org> Mon, 26 Dec 2016 02:12:30 +0100 Cheers Alf
--- End Message ---
