Bug#1052602: bind9-host should have versioned Depends on bind9-libs
Package: bind9-host Version: 1:9.16.42-1~deb11u1 Severity: normal Dear Maintainer, when updating only package bind9 and then trying to use the host command from bind9-host (as our ansible-based upgrade procedure does, doing the latter to check if the local named is still working as expected), you get to see $ host debian.org host: error while loading shared libraries: libdns-9.16.42-Debian.so: cannot open shared object file: No such file or directory No big issue, but I guess this means there should be a versioned dependency declared. Cheers Wolfgang *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** -- System Information: Debian Release: 11.7 APT prefers oldstable-updates APT policy: (500, 'oldstable-updates'), (500, 'oldstable-security'), (500, 'oldstable') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-25-amd64 (SMP w/1 CPU thread) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages bind9-host depends on: ii bind9-libs 1:9.16.44-1~deb11u1 ii libc6 2.31-13+deb11u6 ii libidn2-0 2.3.0-5 bind9-host recommends no packages. bind9-host suggests no packages. -- no debconf information
Bug#960492: Any updates?
Hi, I just saw the mail on debian-devel-announce that the code freeze for bullseye has begun, will this be reverted before? Cheers Wolfgang signature.asc Description: PGP signature
Bug#960492: vim-pathogen: Do not depend on 'vim-*' packages, plain 'vim' is enough
Package: vim-pathogen Version: 2.4-1 Severity: normal Dear Maintainer, as mentioned in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914583 vim-pathogen works fine without Python support, so the Dependency should be reduced to 'vim' again. Thanks Wolfgang -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 5.6.0-1-686-pae (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Init: systemd (via /run/systemd/system) Versions of packages vim-pathogen depends on: ii vim2:8.2.0716-3 ii vim-addon-manager 0.5.10 Versions of packages vim-pathogen recommends: pn vim-scripts vim-pathogen suggests no packages. -- no debconf information
Bug#914583: vim-pathogen: Depend on vim compiled with Python support
Hello, this got my attention: After this operation, 93.9 MB of additional disk space will be used. This is vim-gtk, but even for vim-nox: After this operation, 14.4 MB of additional disk space will be used. I know, everyone thinks disk space is cheap these days, but where is this requirement on Python documented? I've used vim-pathogen for years now, and I've never had to install anything but the plain vim package. Cheers Wolfgang signature.asc Description: PGP signature
Bug#826701: gnuplot-data: Version 5.0.3+dfsg3-1 tries to overwrite a file which is also in package gnuplot-tex 4.6.6-3
Related to this: after installing the -data package with --force-overwrite, the apt-get -f install complains about an alternatives entry related to the -x11 package: Setting up gnuplot-x11 (5.0.3+dfsg3-1) ... update-alternatives: error: alternative link /usr/share/gnuplot/gnuplot.gih is already managed by gnuplot4 After removing the gnuplot4 link group with update-alternatives --remove-all gnuplot4 I could finish the installation. Cheers Wolfgang signature.asc Description: Digital signature
Bug#826701: gnuplot-data: Version 5.0.3+dfsg3-1 tries to overwrite a file which is also in package gnuplot-tex 4.6.6-3
Package: gnuplot-data Version: 4.6.6-3 Severity: grave Justification: renders package unusable Dear Maintainer, Can't upgrade 4.6.6-3 -> 5.0.3+dfsg3-1: Preparing to unpack .../gnuplot-data_5.0.3+dfsg3-1_all.deb ... Unpacking gnuplot-data (5.0.3+dfsg3-1) over (4.6.6-3) ... dpkg: error processing archive /var/cache/apt/archives/gnuplot-data_5.0.3+dfsg3-1_all.deb (--unpack): trying to overwrite '/usr/share/texmf/tex/latex/gnuplot/gnuplot-lua-tikz-common.tex', which is also in package gnuplot-tex 4.6.6-3 Cheers Wolfgang -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (x86_64) Foreign Architectures: amd64 Kernel: Linux 4.5.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Init: sysvinit (via /sbin/init) Versions of packages gnuplot-data depends on: ii aglfn1.7-3 pn gnuplot-tex gnuplot-data recommends no packages. gnuplot-data suggests no packages. -- no debconf information
Bug#826247: needrestart: Improve performance when checking interpreters by not running multiple times for the same script
Package: needrestart
Version: 2.8-1
Severity: wishlist
Tags: patch
Dear Maintainer,
on a system with a perl-based daemon spawned by postfix many many times,
needrestart was very slow.
That's because it re-scans all the perl module source files over and
over again, for each PID once, even though once per script should be
enough.
The patch attached is a crude hack against the jessie version (it
applies with some offsets/fuzz to the sid version), but on said system
the runtime is improved quite a bit:
before:
real1m34.101s
user1m30.924s
sys 0m2.988s
afterwards:
real0m4.838s
user0m4.384s
sys 0m0.264s
Obviously this would need to be done properly and not only for Perl.pm.
Cheers
Wolfgang
-- Package-specific info:
needrestart output:
Your outdated processes:
ApacheDirectory[9304], at-spi-bus-laun[2309], at-spi2-registr[2346], bash[2104,
2116, 2110, 2243, 2245, 2108, 2246, 2241], chromium[3587, 3576, 3545, 3537],
dane-plug[3958],
dbus-daemon[2340, 1846], dbus-launch[1845], dconf-service[19859],
dnssec-plug[3843], gconfd-2[3638], gkrellm[2055], gvfsd[1952],
gvfsd-metadata[20750], gvfsd-trash[19829],
gvfs-udisks2-vo[19817], mosh-client[8020], panel-13-systra[1983],
panel-16-action[1984], sh[1809], systemd[1796], Thunar[1881],
thunderbird[9255], tpb[1854],
wicd-client[2092], xfce4-panel[1883], xfce4-session[1871],
xfce4-volumed[2100], xfconfd[1875], xfdesktop[1982], xfrun4[9247],
xfsettingsd[1888], xfwm4[1879],
xscreensaver[2097], xterm[2062, 2056, 2058, 2061, 2063, 2060, 2059, 2057],
x-www-browser[3634]
checkrestart output:
-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 4.5.0-2-686-pae (SMP w/4 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: sysvinit (via /sbin/init)
Versions of packages needrestart depends on:
ii dpkg 1.18.7
ii gettext-base 0.19.7-2
ii libintl-perl 1.24-1
ii libmodule-find-perl0.13-1
ii libmodule-scandeps-perl1.21-1
ii libproc-processtable-perl 0.53-1+b1
ii libsort-naturally-perl 1.03-1
ii libterm-readkey-perl 2.33-1+b1
ii perl 5.22.2-1
ii xz-utils 5.1.1alpha+20120614-2.1
needrestart recommends no packages.
Versions of packages needrestart suggests:
ii libnotify-bin 0.7.6-2
-- no debconf information
diff -Nurp a/usr/share/perl5/NeedRestart/Interp/Perl.pm b/usr/share/perl5/NeedRestart/Interp/Perl.pm
--- a/usr/share/perl5/NeedRestart/Interp/Perl.pm 2016-06-03 16:09:21.885469436 +0200
+++ b/usr/share/perl5/NeedRestart/Interp/Perl.pm 2016-06-03 16:13:04.181830614 +0200
@@ -83,6 +83,7 @@ sub source {
sub files {
my $self = shift;
my $pid = shift;
+my $files_cache = shift;
my $ptable = nr_ptable_pid($pid);
unless($ptable->{cwd}) {
print STDERR "$LOGPREF #$pid: could not get current working directory, skipping\n" if($self->{debug});
@@ -105,6 +106,13 @@ sub files {
return ();
}
my $src = $ARGV[0];
+if ( defined($$files_cache{$src}) && $$files_cache{$src} == 1 ) {
+print STDERR "already know $src\n" if ($self->{debug});
+return ();
+} else {
+print STDERR "remembering $src\n" if ($self->{debug});
+$$files_cache{$src} = 1;
+}
unless(-r $src && -f $src) {
chdir($cwd);
print STDERR "$LOGPREF #$pid: source file not found, skipping\n" if($self->{debug});
diff -Nurp a/usr/share/perl5/NeedRestart.pm b/usr/share/perl5/NeedRestart.pm
--- a/usr/share/perl5/NeedRestart.pm 2016-06-03 16:09:29.905626777 +0200
+++ b/usr/share/perl5/NeedRestart.pm 2016-06-03 16:09:29.905626777 +0200
@@ -132,6 +132,10 @@ sub needrestart_interp_init($) {
}
}
+{
+
+my %files_cache = ();
+
sub needrestart_interp_check($$$) {
my $debug = shift;
my $pid = shift;
@@ -144,7 +148,7 @@ sub needrestart_interp_check($$$) {
print STDERR "$LOGPREF #$pid is a ".(ref $interp)."\n" if($debug);
my $ps = nr_ptable_pid($pid);
- my %files = $interp->files($pid);
+ my %files = $interp->files($pid, \%files_cache);
if(grep {$_ > $ps->start} values %files) {
if($debug) {
@@ -161,6 +165,8 @@ sub needrestart_interp_check($$$) {
return 0;
}
+}
+
sub needrestart_interp_source($$$) {
my $debug = shift;
my $pid = shift;
Bug#826220: needrestart: Allow usage of different config file when run from APT
Package: needrestart Version: 2.8-1 Severity: wishlist Dear Maintainer, currently the apt-pinvoke helper exec's needrestart without any arguments when run from APT. If you want to use different modes of operation when using APT and when using needrestart interactively it's currently necessary to use the standard config file for APT, which means the user has to add -c for each interactive calls, which is a bit burdensome. My use case is the following: 1.) by default when run from APT restart a less important services automatically, the more important ones are blacklisted in a file in /etc/needrestart/conf.d/ 2.) the admin user can then use needrestart to list/restart the more important services manually and while on the machine, by providing a different config file (which is ignoring the blacklist in conf.d/), which currently means calling it with -c It would be nice to be able to set a different config for APT, so the interactive call of needrestart is could be plain 'needrestart' again. Cheers Wolfgang -- Package-specific info: needrestart output: Your outdated processes: ApacheDirectory[9304], at-spi-bus-laun[2309], at-spi2-registr[2346], bash[2241, 2245, 2104, 2116, 2246, 2108, 2243, 2110], chromium[3537, 3545, 3587, 3576], dane-plug[3958], dbus-daemon[2340, 1846], dbus-launch[1845], dconf-service[19859], dnssec-plug[3843], gconfd-2[3638], gkrellm[2055], gvfsd[1952], gvfsd-metadata[20750], gvfsd-trash[19829], gvfs-udisks2-vo[19817], mosh-client[8020], panel-13-systra[1983], panel-16-action[1984], sh[1809], systemd[1796], Thunar[1881], thunderbird[9255], tpb[1854], wicd-client[2092], xfce4-panel[1883], xfce4-session[1871], xfce4-volumed[2100], xfconfd[1875], xfdesktop[1982], xfrun4[9247], xfsettingsd[1888], xfwm4[1879], xscreensaver[2097], xterm[2060, 2061, 2058, 2057, 2063, 2056, 2059, 2062], x-www-browser[3634] checkrestart output: -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 4.5.0-2-686-pae (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Init: sysvinit (via /sbin/init) Versions of packages needrestart depends on: ii dpkg 1.18.7 ii gettext-base 0.19.7-2 ii libintl-perl 1.24-1 ii libmodule-find-perl0.13-1 ii libmodule-scandeps-perl1.21-1 ii libproc-processtable-perl 0.53-1+b1 ii libsort-naturally-perl 1.03-1 ii libterm-readkey-perl 2.33-1+b1 ii perl 5.22.2-1 ii xz-utils 5.1.1alpha+20120614-2.1 needrestart recommends no packages. Versions of packages needrestart suggests: ii libnotify-bin 0.7.6-2 -- no debconf information
Bug#820064: lgogdownloader: Needs fix to work with new jsoncpp version
Package: lgogdownloader Version: 2.27-1 Severity: grave Justification: renders package unusable Dear Maintainer, the upgrade to the new libjsoncpp1 version seems to have introduced a problem: $ lgogdownloader --update-cache terminate called after throwing an instance of 'Json::RuntimeError' what(): ConstIterator to Iterator should never be allowed. Aborted Applying the patch from https://github.com/Sude-/lgogdownloader/commit/519cb78d38be04a3af79784b5326e21651ced6e1 and rebuilding the package fixes this issue for me. Cheers Wolfgang -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 4.4.0-1-686-pae (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Init: sysvinit (via /sbin/init) Versions of packages lgogdownloader depends on: ii libboost-date-time1.58.01.58.0+dfsg-5+b1 ii libboost-filesystem1.58.0 1.58.0+dfsg-5+b1 ii libboost-program-options1.58.0 1.58.0+dfsg-5+b1 ii libboost-regex1.58.01.58.0+dfsg-5+b1 ii libboost-system1.58.0 1.58.0+dfsg-5+b1 ii libc6 2.22-5 ii libcss-parser-pp0v5 0.86-1 ii libcss-parser0 0.86-1 ii libcurl3-gnutls 7.47.0-1 ii libgcc1 1:5.3.1-13 ii libhtmlcxx3v5 0.86-1 ii libjsoncpp1 1.7.2-1 ii liboauth0 1.0.1-1 ii librhash0 1.3.3-1 ii libstdc++6 5.3.1-13 ii libtinyxml2.6.2v5 2.6.2-3 lgogdownloader recommends no packages. lgogdownloader suggests no packages. -- no debconf information
Bug#810814: libgnutls26: Encrypted LDAP connection doesn't work after libgnutls26 update
Package: libgnutls26 Followup-For: Bug #810814 Hi, I can confirm that the addition of 'SECURE256' in the cipher suites configuration seems to be the problem, switching from olcTLSCipherSuite: SECURE256:!ARCFOUR-128:!3DES-CBC:-VERS-SSL3.0 to olcTLSCipherSuite: NORMAL:!ARCFOUR-128:!3DES-CBC:-VERS-SSL3.0 worked for me, but is of course not ideal. Debugging with gnutls-cli yields the same results as in the related Ubuntu bug report https://bugs.launchpad.net/ubuntu/+source/gnutls26/+bug/1534230 i.e. 'SECURE256' doesn't work, while 'SECURE256:+SIGN-ALL' does work with gnutls-cli (but unfortunately the +SIGN-ALL doesn't help when configuring slapd's olcTLSCipherSuite). Cheers Wolfgang -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 4.2.0-1-686-pae (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Init: sysvinit (via /sbin/init) Versions of packages libgnutls26 depends on: ii libc6 2.19-22 pn libgcrypt11 ii libp11-kit00.23.1-3 ii libtasn1-6 4.7-2 ii multiarch-support 2.19-22 ii zlib1g 1:1.2.8.dfsg-2+b1 libgnutls26 recommends no packages. libgnutls26 suggests no packages.
Bug#805406: libatlas3-base: Syntax error in preinst maintainer script
Package: libatlas3-base Version: 3.10.2-8 Severity: normal Dear Maintainer, today while upgrading a sid system I noticed the following: . . Preparing to unpack .../libatlas3-base_3.10.2-8_i386.deb ... /var/lib/dpkg/tmp.ci/preinst: line 7: [: argument expected . . Looking at the preinst in /var/lib/dpkg/info/libatlas3-base.preinst this looks wrong if [ $1 = "upgrade" -a `dpkg --compare-versions "$2" ge 3.8.4-4~exp1` -a `dpkg --compare-versions "$2" lt 3.10.1-1` ] which probably is meant to be: if [ "$1" = "upgrade" ] && dpkg --compare-versions "$2" ge 3.8.4-4~exp1 && dpkg --compare-versions "$2" lt 3.10.1-1 Cheers Wolfgang -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 4.2.0-1-686-pae (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Init: sysvinit (via /sbin/init) Versions of packages libatlas3-base depends on: ii libblas-common 1.2.20110419-11 ii libc6 2.19-22 ii libgcc1 1:5.2.1-23 ii libgfortran35.2.1-23 libatlas3-base recommends no packages. libatlas3-base suggests no packages. -- no debconf information
Bug#798510: [Pkg-xen-devel] Bug#798510: xen-utils-common: xendomains domU auto-starting fails after upgrade to Debian 8
Hi Ian, On 15-11-05 10:43:56, Ian Campbell wrote: > I suppose these domains all start just fine by hand, because the race > is well over by then... Indeed they do. > Do you get anything further under /var/log/xen when this occurs? In > particular the xl files associated with the domain and > /var/log/xen/xen-hotplug.log Specifically xen-hotplug.log isn't modified at all, it's actually pretty old while both the dom0 and also the domU were restarted a couple of times today. -rw-r--r-- 1 root adm6735 Sep 9 10:13 xen-hotplug.log The domU log files in /var/log/xen only seem to contain the shutdown sequences, all start with lines like Waiting for domain test-inetng1 (domid 1) to die [pid 1336] but nothing related to the start of the domU. > What does the disk configuration look like in domU.cfg? $ sed -n '/^disk/,/]/p' /etc/xen/test-inetng1.cfg disk= [ 'phy:/dev/inetng1/test-inetng1-disk,xvda2,w', 'phy:/dev/inetng1/test-inetng1-swap,xvda1,w', 'phy:/dev/inetng1/test-inetng1-data,xvdb,w', ] > It would also be useful to edit /etc/init.d/xendomains to change: > out=$(xen create --quiet --defconfig "$file" 2>&1 1>/dev/null) > to > out=$(xen -vvv create --quiet --defconfig "$file" 2>&1 1>/dev/null) > > (adding -vvv before create) and maybe replace /dev/null with something > like /tmp/xendomains.$(basename $file).log > > Hopefully something in there will give us some clue what is not ready > yet. I've changed it to out=$(xen -vvv create --quiet --defconfig "$file" 2>&1 | ts "%b %d %H:%M:%.S" 1>/tmp/xendomains.$(basename $file).log) to get some timestamps into the log with the help of moreutil's ts. Also, I've added exec 5>> /tmp/xen-script-block-$1-$$.log BASH_XTRACEFD="5" PS4='+ \011$(date "+%b %d %H:%M:%S.%N"): $LINENO: ' set -x to the top of the helper script in /etc/xen/scripts/block. With the additional timing information available, a colleague spotted logger being late in the non-working case: in the logs in /tmp/xen*: Nov 12 13:47:29.614355156: 21: logger -p daemon.debug -- /etc/xen/scripts/block: add XENBUS_PATH=backend/vbd/1/51728 Nov 12 13:47:39.422965 libxl: debug: libxl_device.c:1059:device_hotplug_timeout_cb: killing hotplug script /etc/xen/scripts/block add because of timeout in /var/log/syslog: Nov 12 13:47:41 inetng1 logger: /etc/xen/scripts/block: add XENBUS_PATH=backend/vbd/1/51728 Disabling logger in /etc/xen/scripts/logging.sh made the problem go away and the domU was started successfully at boot time. But of course this is not a real solution but only a workaround, as much as adding sleep to the default file. > > Inserting a 'sleep 10' into /etc/defaults/xendomains solves the issue, > > so it seems to be some timing problem. > > Whereabouts? Near the start I guess. No, I've added it to the end of the file. Cheers Wolfgang PS: My colleague also found this mailing list article http://lists.freedesktop.org/archives/systemd-devel/2014-August/021767.html mentioning the problem with logging being blocked at boot time with systemd. PPS: In case you need the full logs, I can attach them to the bug report. signature.asc Description: Digital signature
Bug#800001: backuppc: Do not delete /etc/backuppc recursively in postrm
Package: backuppc Version: 3.3.1-1 Severity: important Hello, backuppc's postrm currently includes running rm -rf /etc/backuppc which is likely to delete user data not installed by the package. C.f. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=309707 for further reasoning. I guess rm -f /etc/backuppc/config.pl should be enough, since it's the only non-conffile installed by the package (and handled by ucf) as far as I can see. Cheers Wolfgang
Bug#798510: xen-utils-common: xendomains domU auto-starting fails after upgrade to Debian 8
Package: xen-utils-common Version: 4.4.1-9+deb8u1 Severity: important Dear Maintainer, After upgrading to Debian 8, auto-starting of domUs via /etc/xen/auto fails with errors like this Sep 09 09:29:21 host xendomains[948]: Starting Xen domain domU (from /etc/xen/auto/domU.cfg)...failed. Sep 09 09:29:21 host xendomains[948]: libxl: error: libxl_exec.c:129:libxl_report_child_exitstatus: /etc/xen/scripts/block add [-1] died due to fatal signal Killed Sep 09 09:29:21 host xendomains[948]: libxl: error: libxl_exec.c:129:libxl_report_child_exitstatus: /etc/xen/scripts/block add [-1] died due to fatal signal Killed Sep 09 09:29:21 host xendomains[948]: libxl: error: libxl_exec.c:129:libxl_report_child_exitstatus: /etc/xen/scripts/block add [-1] died due to fatal signal Killed Sep 09 09:29:21 host xendomains[948]: libxl: error: libxl_create.c:1054:domcreate_launch_dm: unable to add disk devices Services seem to get started in the correct order according to LSB headers in the init scripts: Sep 9 09:28:49 host systemd[1]: Starting LSB: Xen daemons... Sep 9 09:28:49 host xenstored: Checking store ... Sep 9 09:28:49 host xenstored: Checking store complete. Sep 9 09:28:49 host xen[880]: Starting Xen daemons: xenfs xenstored xenconsoled init-dom0. Sep 9 09:28:49 host systemd[1]: Started LSB: Xen daemons. Sep 9 09:28:49 host systemd[1]: Starting LSB: Start/stop secondary xen domains... Inserting a 'sleep 10' into /etc/defaults/xendomains solves the issue, so it seems to be some timing problem. Cheers Wolfgang
Bug#773607: autofs uses nonportable -s option, mounting fails
Package: autofs Version: 5.0.8-2 Followup-For: Bug #773607 Dear Maintainer, there's a patch for this at http://www.spinics.net/lists/autofs/msg01018.html which got applied to the latest OpenSuSE packages at https://build.opensuse.org/package/show/home:mszeredi:branches:openSUSE:13.2:Update/autofs Please see if this is a possible solution, because at the moment there's no simple way around this problem other than for example using a wrapper around the respective mount.* program and filter out the excess '-s' option. Cheers Wolfgang -- System Information: Debian Release: 8.0 APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.16.0-4-686-pae (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Init: sysvinit (via /sbin/init) Versions of packages autofs depends on: ii libc6 2.19-15 ii libxml22.9.2+dfsg1-3 ii multiarch-support 2.19-15 ii ucf3.0030 Versions of packages autofs recommends: ii kmod 20-1 ii module-init-tools 20-1 ii nfs-common 1:1.2.8-9 autofs suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
