Your message dated Thu, 19 Dec 2019 14:39:22 +0000
with message-id <e1ihwxw-000ivd...@fasolo.debian.org>
and subject line Bug#946609: fixed in resolvconf 1.81
has caused the Debian Bug report #946609,
regarding resolvconf: broken init script: "/run/resolvconf is neither a
directory nor a symbolic link"
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.)
--
946609: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946609
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: resolvconf
Version: 1.80
Tags: patch
The create_runtime_directories() function in the resolvconf init script
worked under assumption that $RUN_DIR is a symlink (either broken or
pointing to a directory). Now that $RUN_DIR is just /run/resolvconf,
resolvconf no longer starts on boot:
Setting up resolvconf...failed (/run/resolvconf is neither a directory nor a
symbolic link).
-- System Information:
Architecture: i386
Versions of packages resolvconf depends on:
ii lsb-base 11.1.0
ii debconf 1.5.73
--
Jakub Wilk
--- /etc/init.d/resolvconf 2019-12-10 16:45:20.000000000 +0100
+++ /etc/init.d/resolvconf 2019-12-11 20:30:41.564651091 +0100
@@ -54,11 +54,8 @@
{
umask 022
if [ ! -d "$RUN_DIR" ] ; then
- [ -L "$RUN_DIR" ] || log_action_end_msg_and_exit 1 "$RUN_DIR is neither a directory nor a symbolic link"
- # It's a symlink. Its target is not a dir.
- { RUN_CANONICALDIR="$(readlink -f "$RUN_DIR")" && [ "$RUN_CANONICALDIR" ] ; } || log_action_end_msg_and_exit 1 "Canonical path of the run directory could not be determined"
# Create directory at the target
- mkdir "$RUN_CANONICALDIR" || log_action_end_msg_and_exit 1 "Error creating directory $RUN_CANONICALDIR"
+ mkdir "$RUN_DIR" || log_action_end_msg_and_exit 1 "Error creating directory $RUN_DIR"
fi
# The resolvconf run directory now exists.
if [ ! -d "${RUN_DIR}/interface" ] ; then
--- End Message ---
--- Begin Message ---
Source: resolvconf
Source-Version: 1.81
We believe that the bug you reported is fixed in the latest version of
resolvconf, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 946...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Andrej Shadura <andre...@debian.org> (supplier of updated resolvconf package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Format: 1.8
Date: Thu, 19 Dec 2019 15:19:16 +0100
Source: resolvconf
Architecture: source
Version: 1.81
Distribution: unstable
Urgency: medium
Maintainer: resolvconf team <team+resolvc...@tracker.debian.org>
Changed-By: Andrej Shadura <andre...@debian.org>
Closes: 850783 946609
Changes:
resolvconf (1.81) unstable; urgency=medium
.
[ Russell Coker ]
* Set correct SE Linux context on created directories and files
(Closes: #850783).
.
[ Jakub Wilk ]
* Drop symlink resolving logic from the init script (Closes: #946609).
Checksums-Sha1:
7765917b0be729dfaa4d867b3b480e8cff9bb735 1483 resolvconf_1.81.dsc
a05a36af2f8cba3d00339bc02ea52ccd5e4b687d 72900 resolvconf_1.81.tar.xz
Checksums-Sha256:
7e2bb5f62686b94715657fd6e3f87bfde6a4a5afdb3706dba2e61692fc0246ce 1483
resolvconf_1.81.dsc
68c0700befb473355d353ce5ea20d44b62e0a7b01a0ac5e214e33ea692934d3e 72900
resolvconf_1.81.tar.xz
Files:
20e58ff37fcddfdae9564f7bf5318c07 1483 net optional resolvconf_1.81.dsc
016294998dafc3b28b1c8c418c2040c5 72900 net optional resolvconf_1.81.tar.xz
-----BEGIN PGP SIGNATURE-----
iQEzBAEBCAAdFiEEeuS9ZL8A0js0NGiOXkCM2RzYOdIFAl37hw0ACgkQXkCM2RzY
OdL3HQf/cph4Uq6yIi83+uGycy1HXQs8eNUd0XkMBEx/KUp3pyyrQWvhEnV77CiK
MZ7Rt3grB/AVxICRJmX5Zeb/uqiozpajsSz4zmsb1EqPnR+JEy9f/cu/pqisA7mj
D7pEkMzx1lupbz2PO1fvGVM5FBOQ/D9p/w1D6V3MFrofJyRmKuLPqHjR0+V+Frbf
7hbhrweHB1CEb13gi0ol9UE23xVVmtsCm3m73G5a7AXN6m8b01no7HPGM2Q92ujM
cOAA1n9DEUNZbtt0keWTDhdFz+EM7fGoj9RhjQnWci2Aguo2/jzyyXXFNgUU3IF1
S9K+zIk4qMNMaa6JbxrSbgYRUN8UuQ==
=7sOC
-----END PGP SIGNATURE-----
--- End Message ---
