Bug#838407: RFA: cdlabelgen -- generates front cards and tray cards for CDs and DVDs
Hi, Sorry, no I don't. Cheers, On 20/11/16 16:21, Dominique Dumont wrote: Hello I take over cdlabelgen and will maintain it on behalf of debian-perl team. Stephen, do you have a repo of this package ? Otherwise, I'll start from scratch with dgit. All the best
Bug#816168: O: hdparm -- tune hard disk parameters for high performance
Package: wnpp Severity: normal I intend to orphan the hdparm package. I no longer have any hardware that uses it, so I can not effectively look after it. The package description is: Get/set device parameters for Linux SATA/IDE drives. Primary use is for enabling irq-unmasking and IDE multiplemode. Cheers, -- - | ,''`. Stephen Gran | | : :' :sg...@debian.org | | `. `'Debian user, admin, and developer | |`- http://www.debian.org | - signature.asc Description: Digital signature
Bug#810148: varnish: Discard old VCL after reload
Package: varnish
Version: 4.0.2-1
Severity: wishlist
Tags: patch
Hi,
The very nice varnish reload script currently does not clean up old vcl
on reload. I think the attached patch does this, and would be pleased
if you included it (or something like it) in the package.
I used nmudiff to give you a reasonably clean diff, but I am not
planning to NMU this. If you see any references to an impending NMU, my
apologies.
Cheers,
--
-
| ,''`. Stephen Gran |
| : :' :sg...@debian.org |
| `. `'Debian user, admin, and developer |
|`- http://www.debian.org |
-
diff -Nru varnish-4.0.2/debian/reload-vcl varnish-4.0.2/debian/reload-vcl
--- varnish-4.0.2/debian/reload-vcl 2014-10-14 21:54:12.0 +0100
+++ varnish-4.0.2/debian/reload-vcl 2016-01-06 23:33:45.0 +
@@ -157,13 +157,25 @@
exitstatus=1
fi
fi
+if [ -n "${VCL_KEEP}" ]
+then
+for vcl in $(varnishadm vcl.list | awk '/^available/ { print $3 }' | head -n -1 | tac | tail -n +${VCL_KEEP})
+do
+if $varnishadm -T $mgmt_interface -S ${secret} vcl.discard ${vcl}
+then
+printf "$vcl_discard_failed" $vcl
+else
+printf "$vcl_discard_succeeded" $vcl
+fi
+done
+fi
else
printf "$msg_compile_failed" $vcl_label $vcl_file
exitstatus=1
fi > $logfile
# Blather
-if [ -z "${quiet}" -o -n "$exitstatus" ]
+if [ -n "$exitstatus" -o -z "${quiet}" ]
then
grep -v '^$' >&2 $logfile
fi
diff -Nru varnish-4.0.2/debian/varnish.default varnish-4.0.2/debian/varnish.default
--- varnish-4.0.2/debian/varnish.default 2014-10-14 21:54:12.0 +0100
+++ varnish-4.0.2/debian/varnish.default 2016-01-06 23:24:34.0 +
@@ -18,6 +18,9 @@
# you need to increase this number as well
MEMLOCK=82000
+# How many vcl versions to retain on reload
+VCL_KEEP=5
+
# Default varnish instance name is the local nodename. Can be overridden with
# the -n switch, to have more instances on a single server.
# You may need to uncomment this variable for alternatives 1 and 3 below.
signature.asc
Description: Digital signature
Bug#775795: Patch to use /usr/sbin/service in Debian service provider
Hi,
This one time, at band camp, Stig Sandbeck Mathisen said:
>
> Hello,
>
> Thanks for the patch. It looks like it has the correct solution, using
> the Debian abstraction layer over the alternative init systems.
>
> However, I've found a problem with it using the "puppet resource"
> command. Could you see if you find what causes it?
>
> With puppet 3.7.22-1:
>
> ,
> | root@dagon:~# puppet resource service apache2
> | service { 'apache2':
> | ensure => 'stopped',
> | enable => 'true',
> | }
> `
>
> With your patch:
>
> ,
> | root@dagon:~# puppet resource service apache2
> | Error: Could not run: undefined local variable or method `service' for
> #
> `
Try this (lightly tested) one instead. The problem is in the definition
and use of the service command in the first patch.
Cheers,
--
-
| ,''`.Stephen Gran |
| : :' :sg...@debian.org |
| `. `'Debian user, admin, and developer |
|`- http://www.debian.org |
-
From 2eae3a2a71de50889535f0e917ac6f4ecaeb8975 Mon Sep 17 00:00:00 2001
From: Gaudenz Steinlin
Date: Sat, 31 Jan 2015 16:09:08 +0100
Subject: [PATCH] Use /usr/sbin/service in Debian service provider
Closes: #775795
---
.../0004-debian-service-provider-use-service.patch | 56 ++
debian/patches/series | 1 +
2 files changed, 57 insertions(+)
create mode 100644 debian/patches/0004-debian-service-provider-use-service.patch
diff --git a/debian/patches/0004-debian-service-provider-use-service.patch b/debian/patches/0004-debian-service-provider-use-service.patch
new file mode 100644
index 000..29a4277
--- /dev/null
+++ b/debian/patches/0004-debian-service-provider-use-service.patch
@@ -0,0 +1,56 @@
+From: Gaudenz Steinlin
+Subject: Use /usr/sbin/service for service management on Debian
+
+In Debian jessie systemd will be the default init system. But the old system V
+and other alternative init systems are still supported. /usr/sbin/service
+provides an abstraction layer which is able to start, stop and restart
+services independent of the init system used.
+
+Bug: https://tickets.puppetlabs.com/browse/PUP-2023
+Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775795
+---
+Index: puppet/lib/puppet/provider/service/debian.rb
+===
+--- puppet.orig/lib/puppet/provider/service/debian.rb 2015-01-31 17:30:09.0 +0100
puppet/lib/puppet/provider/service/debian.rb 2015-01-31 23:05:10.477108925 +0100
+@@ -16,6 +16,11 @@
+ # is resolved.
+- commands :invoke_rc => "/usr/sbin/invoke-rc.d"
++ commands :invoke_rc => "/usr/sbin/invoke-rc.d", :service => "service"
+
+ defaultfor :operatingsystem => :debian
+
+ # Remove the symlinks
+@@ -61,4 +66,28 @@
+ update_rc "-f", @resource[:name], "remove"
+ update_rc @resource[:name], "defaults"
+ end
++
++ # The start, stop, restart and status command use service
++ # this makes sure that these commands work with whatever init
++ # system is installed
++ def startcmd
++service @resource[:name], "start"
++ end
++
++ # The stop command is just the init script with 'stop'.
++ def stopcmd
++service @resource[:name], "stop"
++ end
++
++ def restartcmd
++(@resource[:hasrestart] == :true) && service @resource[:name], "restart"
++ end
++
++ # If it was specified that the init script has a 'status' command, then
++ # we just return that; otherwise, we return false, which causes it to
++ # fallback to other mechanisms.
++ def statuscmd
++(@resource[:hasstatus] == :true) && service @resource[:name], "status"
++ end
++
+ end
diff --git a/debian/patches/series b/debian/patches/series
index 471a23b..6543a01 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -1,3 +1,4 @@
0001-Do-not-require-rubygems.patch
0002-Set-passenger-puppet-master-document-root.patch
0003-fix-puppet-master-logcheck-rule.patch
+0004-debian-service-provider-use-service.patch
--
2.1.4
Bug#770314: RFP: gpcslots2 -- text console casino for *nix
Hi, This is code by someone who routinely trolls Debian. I doubt we want any more poisonous upstreams in Debian, so I at least would prefer this never get packaged. Cheers, -- - | ,''`. Stephen Gran | | : :' :sg...@debian.org | | `. `'Debian user, admin, and developer | |`- http://www.debian.org | - signature.asc Description: Digital signature
Bug#731315: qa.debian.org: [UDD] Seems vcs gatherer needs to be adapted to new alioth
This one time, at band camp, Andreas Tille said: > Hi, > > it seems the VCS gatherer needs to be adapted to the new Alioth server. pet has moved. The database is on bmdb1. You should have firewall access from ullmann, but I don't know if you have pg_hba access. Let me know how it goes - I have no idea what account you use for rummaging around in pet's DB. Cheers, -- - | ,''`. Stephen Gran | | : :' :sg...@debian.org | | `. `'Debian user, admin, and developer | |`- http://www.debian.org | - signature.asc Description: Digital signature
Bug#640651: please set default FIRST_SYSTEM_UID=1 and FIRST_SYSTEM_GID=1
This one time, at band camp, Harald Dunkel said: > You mean policy is more important than compatibility? Compatibility > is a quality criteria. But "policy"? Yes, sorry. Adduser is primarily designed to be a helper tool for maintainers to make sure that user management related to packages are handled in a policy compliant manner. Making adduser break policy violates its only reason for existence. > > I see your issue, but that would better be solved with a possibility > > to tell the installer to change these variables. > > Some debconf menu for adduser to be run before the first "dynamic > UID/GID" package is installed would be fine. Since all packages > adding UIDs/GIDs should depend upon adduser this could actually work. If you have a large, grown environment, why are you still doing things manually? Get a gold image, package up a custom d-i that does what you want, etc. This stuff isn't that hard, and it's the right way to do it. Adduser is not going to make this change by default. Cheers, -- ----- | ,''`.Stephen Gran | | : :' :sg...@debian.org | | `. `'Debian user, admin, and developer | |`- http://www.debian.org | - signature.asc Description: Digital signature
Bug#732744: [Pkg-clamav-devel] Bug#732744: clamav: use dh-autoreconf for better new-port coverage
This one time, at band camp, Dimitri John Ledkov said: > Hi, > > The ppc64el port requires a patch to libtool.m4. I don't think that's in > Debian yet, but when it is it will require autoreconfing a bunch of > packages to pick it up. clamav could handle this quite easily by using > dh-autoreconf, when libtool is in use (as of course it is here), > dh-autoreconf is a superset of autotools-dev, and it seems to still > build just fine if I do the following. I did have to do a bit of extra > work to make things happy with new automake. > > * Convert to dh-autoreconf in order to update libtool.m4 for new > ports. > * Remove -Werror from automake flags, to avoid failing autoreconf with > new automake. Removing -Werror is not a decision to be taken quite so lightly. What fails and why can't that be fixed instead? Cheers, -- ----- | ,''`.Stephen Gran | | : :' :sg...@debian.org | | `. `'Debian user, admin, and developer | |`- http://www.debian.org | - signature.asc Description: Digital signature
Bug#730107: adduser --system and addgroup --system should ignore remote directory services
This one time, at band camp, Harald Dunkel said: > On 11/21/13 20:40, Stephen Gran wrote: > > > > adduser uses the system nss routines. It's up to the admin of the > > system to set them up appropriately, sorry. > > nsswitch.conf does not provide an interface to introduce new group > IDs. getent uses nss, but this is a bug report about adduser. Sure it does. man putgrent, although you are right, it is file based. adduser does not know about directory services, it calls the system nss routines to determine user and group information, and then it uses the passwd and related commands to manipulate users and groups. If those don't do the right thing with your directory services, then adduser can't help you. Cheers, -- - | ,''`. Stephen Gran | | : :' :sg...@debian.org | | `. `'Debian user, admin, and developer | |`- http://www.debian.org | - signature.asc Description: Digital signature
Bug#730107: adduser --system and addgroup --system should ignore remote directory services
This one time, at band camp, Harald Dunkel said: > Problem: > adduser --system or addgroup --system refuse to proceed > if the name is already provided by a remote directory > service for passwd or group. On the next reboot the user > or group names cannot be resolved, if the (unrelated!) > directory service is not available yet. > > The system users and groups should be defined locally, > independent from the availability of a foreign directory > service. adduser uses the system nss routines. It's up to the admin of the system to set them up appropriately, sorry. Cheers, -- - | ,''`. Stephen Gran | | : :' :sg...@debian.org | | `. `'Debian user, admin, and developer | |`- http://www.debian.org | - signature.asc Description: Digital signature
Bug#729676: systemd: service command has wrong exit code for unknown service
This one time, at band camp, Michael Biebl said: > Am 15.11.2013 17:18, schrieb Stephen Gran: > > Package: systemd > > Version: 44-11 > > Severity: normal > > > > Hi, > > > > steve@varinia:~$ sudo systemctl disable NetworkManager.service > > rm '/etc/systemd/system/dbus-org.freedesktop.NetworkManager.service' > > rm '/etc/systemd/system/multi-user.target.wants/NetworkManager.service' > > rm '/etc/systemd/system/network-manager.service' > > steve@varinia:~$ sudo service network-manager stop > > [ ok ] Stopping network-manager (via systemctl): network-manager.service. > > steve@varinia:~$ > > > > This probably should have failed, or mentioned that it didn't know what > > I was talking about. > > This service isn't unknown, you still have > /etc/init.d/network-manager (and systemctl status > network-manager.service) should tell you that it is using the legacy > SysV init script. The "Alias" symlink in network-manager should probably > be shipped in the network-manager package directly instead of creating > it dynamically [1] steve@varinia:~$ pgrep NetworkManager 22753 steve@varinia:~$ sudo systemctl disable NetworkManager.service rm '/etc/systemd/system/dbus-org.freedesktop.NetworkManager.service' rm '/etc/systemd/system/multi-user.target.wants/NetworkManager.service' rm '/etc/systemd/system/network-manager.service' steve@varinia:~$ sudo service network-manager stop [ ok ] Stopping network-manager (via systemctl): network-manager.service. steve@varinia:~$ pgrep NetworkManager 22753 steve@varinia:~$ sudo systemctl status NetworkManager.service NetworkManager.service - Network Manager Loaded: loaded (/lib/systemd/system/NetworkManager.service; disabled) Active: active (running) since Tue, 19 Nov 2013 15:15:45 +; 16h ago Main PID: 22753 (NetworkManager) CGroup: name=systemd:/system/NetworkManager.service └ 22753 /usr/sbin/NetworkManager --no-daemon systemd should either stop the service, or the service command should exit non-zero. Cheers, -- - | ,''`.Stephen Gran | | : :' :sg...@debian.org | | `. `'Debian user, admin, and developer | |`- http://www.debian.org | - signature.asc Description: Digital signature
Bug#729676: systemd: service command has wrong exit code for unknown service
Package: systemd Version: 44-11 Severity: normal Hi, steve@varinia:~$ sudo systemctl disable NetworkManager.service rm '/etc/systemd/system/dbus-org.freedesktop.NetworkManager.service' rm '/etc/systemd/system/multi-user.target.wants/NetworkManager.service' rm '/etc/systemd/system/network-manager.service' steve@varinia:~$ sudo service network-manager stop [ ok ] Stopping network-manager (via systemctl): network-manager.service. steve@varinia:~$ This probably should have failed, or mentioned that it didn't know what I was talking about. Cheers, -- System Information: Debian Release: 7.2 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.10-0.bpo.2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.utf8) Shell: /bin/sh linked to /bin/dash Versions of packages systemd depends on: ii dpkg 1.16.12 ii initscripts 2.88dsf-41+deb7u1 ii libacl1 2.2.51-8 ii libaudit01:1.7.18-1.1 ii libc62.13-38 ii libcap2 1:2.22-1.2 ii libcryptsetup4 2:1.4.3-4 ii libdbus-1-3 1.6.8-1+deb7u1 ii libkmod2 9-3 ii liblzma5 5.1.1alpha+20120614-2 ii libpam0g 1.1.3-7.1 ii libselinux1 2.1.9-5 ii libsystemd-daemon0 44-11 ii libsystemd-id128-0 44-11 ii libsystemd-journal0 44-11 ii libsystemd-login044-11 ii libudev0 175-7.2 ii libwrap0 7.6.q-24 ii udev 175-7.2 ii util-linux 2.20.1-5.3 Versions of packages systemd recommends: ii libpam-systemd 44-11 Versions of packages systemd suggests: ii python2.7.3-4+deb7u1 ii python-cairo 1.8.8-1+b2 ii python-dbus 1.1.1-1 pn systemd-gui -- no debconf information -- - | ,''`. Stephen Gran | | : :' :sg...@debian.org | | `. `'Debian user, admin, and developer | |`- http://www.debian.org | - signature.asc Description: Digital signature
Bug#722598: partman-ext3: more mount options for ext4
This one time, at band camp, Julien Cristau said: > On Thu, Sep 12, 2013 at 17:26:02 +0100, Stephen Gran wrote: > > Hi, > > > > I'd like to be able to pressed a few more mount options, so I knocked > > up a quick patch. I think this should be all that's needed. > > > nodiratime is fs-independent, maybe it should be allowed for other > filesystems as well? Sure, I'd be happy with that. Who gets that bug report? Is that partman-base? Cheers, -- - | ,''`.Stephen Gran | | : :' :sg...@debian.org | | `. `'Debian user, admin, and developer | |`- http://www.debian.org | - signature.asc Description: Digital signature
Bug#722598: partman-ext3: more mount options for ext4
Package: partman-ext3 Version: 78 Severity: wishlist Hi, I'd like to be able to pressed a few more mount options, so I knocked up a quick patch. I think this should be all that's needed. Cheers, -- System Information: Debian Release: 7.1 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.10-0.bpo.2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.utf8) Shell: /bin/sh linked to /bin/dash -- - | ,''`. Stephen Gran | | : :' :sg...@debian.org | | `. `'Debian user, admin, and developer | |`- http://www.debian.org | - From edc608cc49ba18e39d71301378173c01f5538af6 Mon Sep 17 00:00:00 2001 From: Stephen Gran Date: Thu, 12 Sep 2013 17:19:54 +0100 Subject: [PATCH] more mount options for ext4 Signed-off-by: Stephen Gran --- mountoptions/ext4 |2 ++ 1 file changed, 2 insertions(+) diff --git a/mountoptions/ext4 b/mountoptions/ext4 index 25bc519..300b628 100644 --- a/mountoptions/ext4 +++ b/mountoptions/ext4 @@ -1,4 +1,6 @@ +discard noatime +nodiratime relatime nodev nosuid -- 1.7.10.4 signature.asc Description: Digital signature
Bug#625758: [Adduser-devel] Bug#625758: 'adduser --disabled-login' does not behave as documented.
This one time, at band camp, Sam Morris said: > On Sat, 2013-07-27 at 08:44 +0100, Stephen Gran wrote: > > So, I think that maybe I'm confused - I am under the impression that > > you started by saying that there is no useful difference between the > > two states 'locked' and 'disabled'. I responded by saying there was. > > In defense of your statement, you've pointed me to a bug report that > > says that pam now looks elsewhere to distinguish between the two states, > > and that it was a bug in shadow not to set that other flag, and that > > that bug is now fixed. > > Sorry, I meant to also draw your attention to the clone bug, > <http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=389183#122>. The fix > was reverted because, as it turns out, people were used to the old > behaviour (that 'passwd -l' would lock the password, and not the entire > account). `passwd -l` should only lock the password, not the account. That is correct. But this, again, only underlines that there is a difference between locking the password and locking the account, right? Look, maybe I'm being dense, but I think we're going around in circles a bit here. I think there is a semantic difference between these two states. I think it makes sense for adduser to expose that semantic difference for the initial state of a new user. I think that you are arguing that there is no difference between the states, but you keep doing so by pointing at things discussing how the two states aren't the same. The whole discussion of passwd or shadow fields is a red herring - adduser just uses the tools from the shadow suite, so once they decide with PAM what combination of fields make sense, adduser will do the right thing. If you think that there is no difference between a password that can't be matched and an account that cannot login, or you think that adduser shouldn't expose this difference, please enlighten me. Cheers, -- - | ,''`.Stephen Gran | | : :' :sg...@debian.org | | `. `'Debian user, admin, and developer | |`- http://www.debian.org | - signature.asc Description: Digital signature
Bug#625758: 'adduser --disabled-login' does not behave as documented.
This one time, at band camp, Sam Morris said: > On Fri, 2013-07-26 at 19:39 +0100, Stephen Gran wrote: > > This one time, at band camp, Sam Morris said: > > > Therefore I don't see the use of having both options, unless some other > > > software cares about the difference between the two values, > > > > They do mean something different: > > > > From the wikipedia page: > > > > "NP" or "!" or null - No password, the account has no password. > > "LK" or "*" - the account is Locked, user will be unable to log-in > > > > There is a semantic difference between the two. ! in the field says > > that authentication with a password should never succeed. * says that > > login should never succeed, even if alternate forms of authentication > > (such as ssh keys) are in use. The above chunk of code is correct if it > > is in a password checking routine - both should return false for > > authentication. > > See <http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=219377>. It is > possible to SSH in to a machine as an account with only * in its > password field. In addition, shadow(5) doesn't draw any distinction > between the two values: > > If the password field contains some string that is not a valid > result of crypt(3), for instance ! or *, the user will not be > able to use a unix password to log in (but the user may log in > the system by other means). > > pam_unix's accounting code doesn't use the password field at all--only > the additional fields in the shadow file. > > My gut feeling is that if there ever was a distinction between the two > values, it is lost to history. Perhaps * used to be used before the > advent of shadow files to indicate that the entire account was locked > rather than just the password. I don't know, I wasn't around in those > days. :) So, I think that maybe I'm confused - I am under the impression that you started by saying that there is no useful difference between the two states 'locked' and 'disabled'. I responded by saying there was. In defense of your statement, you've pointed me to a bug report that says that pam now looks elsewhere to distinguish between the two states, and that it was a bug in shadow not to set that other flag, and that that bug is now fixed. It seems to me that the resolution here is, "there is a semantic difference between these two states". How that is expressed in the passwd file doesn't actually matter to adduser - adduser just uses passwd and the other tools to manipulate the files. If there were bugs in their handling of the files that are now fixed, then all is well, right? Cheers, -- - | ,''`.Stephen Gran | | : :' :sg...@debian.org | | `. `'Debian user, admin, and developer | |`- http://www.debian.org | - signature.asc Description: Digital signature
Bug#625758: 'adduser --disabled-login' does not behave as documented.
This one time, at band camp, Sam Morris said:
> tag 625758 + patch
> thanks
>
> With --disabled-password, the password field is set to '!'; with
> --disabled-login, it is set to '*'. pam_unix checks for both in
> verify_pw_hash:
>
> } else if (!p || *hash == '*' || *hash == '!') {
> retval = PAM_AUTH_ERR;
>
> Therefore I don't see the use of having both options, unless some other
> software cares about the difference between the two values,
They do mean something different:
From the wikipedia page:
"NP" or "!" or null - No password, the account has no password.
"LK" or "*" - the account is Locked, user will be unable to log-in
There is a semantic difference between the two. ! in the field says
that authentication with a password should never succeed. * says that
login should never succeed, even if alternate forms of authentication
(such as ssh keys) are in use. The above chunk of code is correct if it
is in a password checking routine - both should return false for
authentication.
Cheers,
--
-----
| ,''`.Stephen Gran |
| : :' :sg...@debian.org |
| `. `'Debian user, admin, and developer |
|`- http://www.debian.org |
-
signature.asc
Description: Digital signature
Bug#711763: ITP: igmpproxy -- simple dynamic Multicast Routing Daemon
Package: wnpp Severity: wishlist Owner: Stephen Gran * Package name: igmpproxy Version : 0.1 Upstream Author : Johnny Egeland * URL : http://sourceforge.net/projects/igmpproxy/ * License : GPL-2+ Programming Lang: C Description : igmpproxy: simple dynamic Multicast Routing Daemon IGMPproxy is a simple dynamic Multicast Routing Daemon using only IGMP signalling. It's intended for simple forwarding of Multicast traffic between networks. Cheers, -- - | ,''`. Stephen Gran | | : :' :sg...@debian.org | | `. `'Debian user, admin, and developer | |`- http://www.debian.org | - signature.asc Description: Digital signature
Bug#696130: 2.1-4 upgrade error "Died at /usr/sbin/ferm line 1719"
Package: ferm Version: 2.1-4 Followup-For: Bug #696130 Hi, I've tested the patch at http://repo.or.cz/w/ferm.git/commitdiff/ce961438fb742c7830dae50c6571ec736344e465 and it fixes the problem for a relatively simple ruleset. It looks like the problem is that it gets confused when the @include depth (maybe?) crosses domain from ip to ip6. I'm increasing the severity, as this makes the package unusable for anyone with dual stack firewalls. Cheers, -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: armhf (armv7l) Kernel: Linux 3.2.0-4-mx5 Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.utf8) Shell: /bin/sh linked to /bin/dash Versions of packages ferm depends on: ii debconf 1.5.48 ii iptables 1.4.14-3 ii lsb-base 4.1+Debian8 ii perl 5.14.2-16 Versions of packages ferm recommends: pn libnet-dns-perl ferm suggests no packages. -- Configuration Files: /etc/default/ferm changed: FAST=yes CACHE=yes OPTIONS= ENABLED="yes" /etc/ferm/ferm.conf [Errno 13] Permission denied: u'/etc/ferm/ferm.conf' -- debconf information: ferm/enable: yes -- - | ,''`. Stephen Gran | | : :' :sg...@debian.org | | `. `'Debian user, admin, and developer | |`- http://www.debian.org | - -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#696092: [Pkg-clamav-devel] Bug#696092: clamav-daemon - clamd dies with GPF
This one time, at band camp, Bastian Blank said: > On Sun, Dec 16, 2012 at 07:49:03PM +0000, Stephen Gran wrote: > > Can you please install the debug package, get a backtrace and send it? > > Lets see. First I need a core-file and I don't think clamd have logic > for this. You said it happens every now and then. You can leave it running with gdb attached and get a backtrace whenever it dies. > > The file that is being scanned at the time would also be helpful. > > It was idle at the time. Interesting. Are you sure the memory is OK in the machine? cheers, -- - | ,''`. Stephen Gran | | : :' :sg...@debian.org | | `. `'Debian user, admin, and developer | |`- http://www.debian.org | - signature.asc Description: Digital signature
Bug#696092: [Pkg-clamav-devel] Bug#696092: clamav-daemon - clamd dies with GPF
Hi, This one time, at band camp, Bastian Blank said: > clamd dies with a GPF every now and then on a lightly used machine: > > | [759148.769473] clamd[1904] general protection ip:7fecaaf5da6b > sp:7fff33328198 error:0 in libstdc++.so.6.0.17[7fecaaee4000+e8000] > | [1119285.532421] clamd[12733] general protection ip:7f1f0052ba6b > sp:7fff27e29bf8 error:0 in libstdc++.so.6.0.17[7f1f004b2000+e8000] Can you please install the debug package, get a backtrace and send it? The file that is being scanned at the time would also be helpful. Cheers, -- - | ,''`. Stephen Gran | | : :' :sg...@debian.org | | `. `'Debian user, admin, and developer | |`- http://www.debian.org | - signature.asc Description: Digital signature
Bug#679746: [Adduser-devel] Bug#679746: Bug#679746: Bug#679746: default --system home directory leads to piuparts RC bugs
Hi, This one time, at band camp, Marc Haber said: > On Thu, Dec 13, 2012 at 07:17:47AM +0000, Stephen Gran wrote: > > This one time, at band camp, Andreas Barth said: > > > Currently, packages become RC-buggy for just adding system users > > > without --no-home and no --home (even if not relying on the > > > directory). I think that - if we read policy as that - then it's > > > better to fail the postinst then to have hidden RC bugs. Explicit RC > > > bugs are always better then well hidden ones. (Of course, all of that > > > for after this cycle.) > > > > So we're not going to do an MBF, but we're going to make code changes > > so that packages blow up at install time and users do the MBF for us, > > one by one? How bizarre. That can't be what you're actually saying. > > A first step could be to have adduser --system spew a warning in this > case. Maintainers should notice that when testing packages before > upload. Additionally, there could be a lintian check for that. Yes, that would be fine, so long as we remove the warning again before release. I see no reason to bother users for the next several years with a message aimed at developers. Is one of you interested in filing a bug on lintian for the new warning? Cheers, -- ----- | ,''`.Stephen Gran | | : :' :sg...@debian.org | | `. `'Debian user, admin, and developer | |`- http://www.debian.org | - signature.asc Description: Digital signature
Bug#679746: [Adduser-devel] Bug#679746: Bug#679746: default --system home directory leads to piuparts RC bugs
This one time, at band camp, Andreas Barth said: > * Stephen Gran (sg...@debian.org) [121212 08:19]: > > This one time, at band camp, Andreas Barth said: > > > > Now, I don't agree that this is a bug in adduser - I think this is a bug > > > > in packages invoking adduser. I think the right way to do this is a > > > > mass bug filing on those packages. > > > > > > I think I disagree here. > > > > > > If we have a switch on adduser "--system" saying that the user to be > > > created is a system-user, I tend to think that adduser should then > > > select an appropriate place to create $HOME. (I wouldn't mind if we > > > say that for the upcoming release, this still is within /home, and we > > > fix that for the next stable release.) > > > > Where would you suggest? > > I suggest to tolerate the current behaviour for the upcoming release. > Afterwards, I suggest to either require either --no-home or --home for > system users. Or switch defaults to another location, e.g. > /var/lib/syshome (or whatever else). Ew. That seems to me to be inventing something ad-hoc and Debian-specific, which feels wrong. > > I can't think of a better place, in the > > absence of direction, than /home. If packages rely on the presence of a > > home directory, it's up to them to ask for a sensible one. > > Currently, packages become RC-buggy for just adding system users > without --no-home and no --home (even if not relying on the > directory). I think that - if we read policy as that - then it's > better to fail the postinst then to have hidden RC bugs. Explicit RC > bugs are always better then well hidden ones. (Of course, all of that > for after this cycle.) So we're not going to do an MBF, but we're going to make code changes so that packages blow up at install time and users do the MBF for us, one by one? How bizarre. That can't be what you're actually saying. Cheers, -- - | ,''`.Stephen Gran | | : :' :sg...@debian.org | | `. `'Debian user, admin, and developer | |`- http://www.debian.org | - signature.asc Description: Digital signature
Bug#679746: [Adduser-devel] Bug#679746: default --system home directory leads to piuparts RC bugs
This one time, at band camp, Marc Haber said: > On Wed, Dec 12, 2012 at 07:05:24AM +0000, Stephen Gran wrote: > > Where would you suggest? I can't think of a better place, in the > > absence of direction, than /home. > > Creating /home/foo will break in the case of an nfs mounted /home, and > other packages are going out of wheezy for using adduser's --system > default. Yes, I know that your argument is "putting stuff under /home is bad". My question was, and I'll repeat it: "Where would you suggest?" So far, no one has made a constructive suggestion. I'd say that that might be because there isn't a good default outside of /home. If we take that as correct, then we have two choices: continue the current behavior, or fail and abort with an error. I'd suggest the latter behavior is even less friendly. Cheers, -- --------- | ,''`.Stephen Gran | | : :' :sg...@debian.org | | `. `'Debian user, admin, and developer | |`- http://www.debian.org | - signature.asc Description: Digital signature
Bug#679746: [Adduser-devel] Bug#679746: default --system home directory leads to piuparts RC bugs
Hi, This one time, at band camp, Andreas Barth said: > > Now, I don't agree that this is a bug in adduser - I think this is a bug > > in packages invoking adduser. I think the right way to do this is a > > mass bug filing on those packages. > > I think I disagree here. > > If we have a switch on adduser "--system" saying that the user to be > created is a system-user, I tend to think that adduser should then > select an appropriate place to create $HOME. (I wouldn't mind if we > say that for the upcoming release, this still is within /home, and we > fix that for the next stable release.) Where would you suggest? I can't think of a better place, in the absence of direction, than /home. If packages rely on the presence of a home directory, it's up to them to ask for a sensible one. Cheers, -- --------- | ,''`.Stephen Gran | | : :' :sg...@debian.org | | `. `'Debian user, admin, and developer | |`- http://www.debian.org | - signature.asc Description: Digital signature
Bug#694334: ferm: modifies files under /etc (still)
Package: ferm Version: 2.1-3 Severity: normal Hi Alexander, After an upgrade of some of the wheezy machines that DSA look after, followed by a puppet run, puppet had to make the following modifications to fix up what happened during the ferm upgrade: /etc/ferm/conf.d/defs.conf: group changed 'adm' to 'root' /etc/ferm/conf.d: group changed 'adm' to 'root' /etc/ferm/conf.d/interfaces.conf: group changed 'adm' to 'root' /etc/ferm/conf.d/load_nf_conntrack_ftp.conf: group changed 'adm' to 'root' /etc/ferm/conf.d/me.conf: group changed 'adm' to 'root' /etc/ferm/dsa.d/00_dsa-bacula-fd-v4: group changed 'adm' to 'root' /etc/ferm/dsa.d/00_dsa-exim: group changed 'adm' to 'root' /etc/ferm/dsa.d/00_dsa-exim-v6: group changed 'adm' to 'root' /etc/ferm/dsa.d/00_dsa-ident: group changed 'adm' to 'root' /etc/ferm/dsa.d/00_dsa-munin-v4: group changed 'adm' to 'root' /etc/ferm/dsa.d/00_dsa-munin-v6: group changed 'adm' to 'root' /etc/ferm/dsa.d/00_dsa-nagios-v4: group changed 'adm' to 'root' /etc/ferm/dsa.d/00_dsa-nagios-v6: group changed 'adm' to 'root' /etc/ferm/dsa.d/00_dsa-ntp: group changed 'adm' to 'root' /etc/ferm/dsa.d/00_dsa-ssh: group changed 'adm' to 'root' /etc/ferm/dsa.d/00_dsa-ssh-v6: group changed 'adm' to 'root' /etc/ferm/dsa.d: group changed 'adm' to 'root' /etc/ferm/ferm.conf: group changed 'adm' to 'root' /etc/ferm: group changed 'adm' to 'root' /etc/ferm: mode changed '2750' to '0755' --- /etc/default/ferm 2012-11-25 15:16:05.519046916 + +++ /tmp/puppet-file20121125-31675-l4up3b-0 2012-11-25 15:45:31.441192158 + @@ -10,5 +10,5 @@ OPTIONS= # Enable ferm on bootup? -ENABLED="yes" +ENABLED=yes I'm sure none of this is necessary except on initial install. Cheers, -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: armhf (armv7l) Kernel: Linux 3.2.0-3-mx5 Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.utf8) Shell: /bin/sh linked to /bin/dash Versions of packages ferm depends on: ii debconf 1.5.46 ii iptables 1.4.14-3 ii lsb-base 4.1+Debian8 ii perl 5.14.2-15 Versions of packages ferm recommends: pn libnet-dns-perl ferm suggests no packages. -- Configuration Files: /etc/default/ferm changed: FAST=yes CACHE=yes OPTIONS= ENABLED=yes /etc/ferm/ferm.conf [Errno 13] Permission denied: u'/etc/ferm/ferm.conf' -- debconf information: ferm/enable: yes -- - | ,''`.Stephen Gran | | : :' :sg...@debian.org | | `. `'Debian user, admin, and developer | |`- http://www.debian.org | - -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#684641: [request-tracker-maintainers] Bug#684641: request-tracker3.8: broken HTML entities in footer
This one time, at band camp, Dominic Hargreaves said: > On Sun, Aug 12, 2012 at 11:38:23AM +0100, Stephen Gran wrote: > > See https://rt.debian.org/index.html for an example. > > > > This seems to be caused by the code in > > /usr/share/request-tracker3.8/html/Elements/Footer > > > > If I can be helpful, please let me know. > > Hi, > > Could you let us know a bit more about the configuration, please? > I've not seen this sort of brokenness before so it's likely to be > specific to the way RT is configured. In fact I'll start by asking: > do you have any customisations in /usr/local/share/request-tracker3.8? > Specifically, I am suspicious that the copyright years are listed as > 1996-2006 when the Debian 3.8 packages say 1996-2009. aha. It seems we do - sorry about that, I knew to look there before pestering you, but it seems I forgot that. I'll make sure that's actually the cause of the problem and close this if so. Sorry for the noise. -- ----- | ,''`.Stephen Gran | | : :' :sg...@debian.org | | `. `'Debian user, admin, and developer | |`- http://www.debian.org | - signature.asc Description: Digital signature
Bug#684641: request-tracker3.8: broken HTML entities in footer
Package: request-tracker3.8 Version: 3.8.8-7+squeeze4 Severity: normal Hi, See https://rt.debian.org/index.html for an example. This seems to be caused by the code in /usr/share/request-tracker3.8/html/Elements/Footer If I can be helpful, please let me know. Cheers, -- System Information: Debian Release: 6.0.5 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.utf8) Shell: /bin/sh linked to /bin/dash -- - | ,''`. Stephen Gran | | : :' :sg...@debian.org | | `. `'Debian user, admin, and developer | |`- http://www.debian.org | - signature.asc Description: Digital signature
Bug#678356: pts-static-n...@qa.debian.org seems to be broken
This one time, at band camp, Raphael Hertzog said: > Hi, > > (Ccing debian-admin because we need their troubleshooting help) > > On Thu, 21 Jun 2012, Ben Hutchings wrote: > > In response to comments on #636010, I'm trying to add static news for > > linux-2.6, linux-kbuild-2.6 and linux-latest-2.6 about their being > > renamed. > > It looks like the mail never arrives to its destination. > > They are not in the backup mailbox at least: > hertzog@quantz:/srv/packages.qa.debian.org/mail$ ls -al > archive/incoming-news-static* > -rw-r- 1 qa qa0 9 juil. 06:57 archive/incoming-news-static > -rw-r- 1 qa qa17448 18 avril 2010 archive/incoming-news-static.0 > -rw-r- 1 qa qa 327737 18 avril 2010 archive/incoming-news-static.1.gz > -rw-r- 1 qa qa 1347901 10 avril 2010 archive/incoming-news-static.2.gz > -rw-r- 1 qa qa 455629 3 avril 2010 archive/incoming-news-static.3.gz > -rw-r- 1 qa qa 200659 16 août 2006 archive/incoming-news-static.4.gz > -rw-r- 1 qa qa 34823420 15 août 2006 archive/incoming-news-static.5.gz > > (the recent timestamp on the first file is only because I tried creating it > to see if it helps) > > My own tries have been delivered however: > Jul 9 08:52:27 mail postfix/smtp[20133]: 7CFC022005D: > to=, > relay=quantz.debian.org[2607:f8f0:610:4000:216:36ff:fe40:3860]:25, delay=12, > delays=0.09/0/11/1.3, dsn=2.0.0, status=sent (250 OK id=1So7pa-00042B-8Z) 2012-07-09 06:52:26 1So7pa-00042B-8Z <= raph...@ouaza.com H=(mail.vm.ouaza.com) [2a01:e0b:1000:23:5054:ff:fe00:d7] P=esmtp S=1429 id=20120709065158.ga2...@rivendell.home.ouaza.com 2012-07-09 06:52:27 1So7pa-00042B-8Z => /srv/packages.qa.debian.org/mail/archive/incoming-default (_static-n...@packages.qa.debian.org) R=virt_direct T=address_file QT=1s DT=1s 2012-07-09 06:52:27 1So7pa-00042B-8Z => | /srv/packages.qa.debian.org/bin/dispatch.pl (_static-n...@packages.qa.debian.org) R=virt_direct T=address_pipe QT=1s DT=0s 2012-07-09 06:52:27 1So7pa-00042B-8Z Completed > Jul 9 09:01:40 mail postfix/smtp[21088]: EA29122005D: > to=<_static-n...@packages.qa.debian.org>, > relay=quantz.debian.org[2607:f8f0:610:4000:216:36ff:fe40:3860]:25, delay=10, > delays=0.09/0/8.9/1.2, dsn=2.0.0, status=sent (250 OK id=1So7yU-0005AW-A1) 2012-07-09 07:01:39 1So7yU-0005AW-A1 <= raph...@ouaza.com H=(mail.vm.ouaza.com) [2a01:e0b:1000:23:5054:ff:fe00:d7] P=esmtp S=1447 id=20120709070112.ga3...@rivendell.home.ouaza.com 2012-07-09 07:01:39 1So7yU-0005AW-A1 => /srv/packages.qa.debian.org/mail/archive/incoming-default <_static-n...@packages.qa.debian.org> R=virt_direct T=address_file QT=1s DT=0s 2012-07-09 07:01:39 1So7yU-0005AW-A1 => | /srv/packages.qa.debian.org/bin/dispatch.pl <_static-n...@packages.qa.debian.org> R=virt_direct T=address_pipe QT=1s DT=0s 2012-07-09 07:01:39 1So7yU-0005AW-A1 Completed I don't know what dispatch.pl does, so I'll leave that to you. As for archiving, it looks to me like the .forward file for _static-news is not matching because exim is considering -news as a local_part_suffix rather than a part of the email address. I'd suggest trying with _static_news instead and see how it goes? Cheers, -- - | ,''`.Stephen Gran | | : :' :sg...@debian.org | | `. `'Debian user, admin, and developer | |`- http://www.debian.org | - signature.asc Description: Digital signature
Bug#680615: nagios3: init script confusion between 'check' and 'status'
Package: nagios3
Version: 3.2.1-2
Severity: normal
excerpts from /etc/init.d/nagios3:
status()
{
log_action_begin_msg "checking $DAEMON"
if check_started; then
log_action_end_msg 0 "running"
else
if [ -e "$THEPIDFILE" ]; then
log_action_end_msg 1 "$DAEMON failed"
exit 1
else
log_action_end_msg 1 "not running"
exit 3
fi
fi
}
status () {
$DAEMON -v $NAGIOSCFG
}
case $1 in
status)
status
;;
check)
check
;;
esac
~# /etc/init.d/nagios3 check
/etc/init.d/nagios3: 247: check: not found
Cheers,
-- System Information:
Debian Release: 6.0.5
APT prefers stable
APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.32-5-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) (ignored: LC_ALL
set to en_US.utf8)
Shell: /bin/sh linked to /bin/dash
Versions of packages nagios3 depends on:
pn nagios3-cgi(no description available)
pn nagios3-core (no description available)
nagios3 recommends no packages.
Versions of packages nagios3 suggests:
pn nagios-nrpe-plugin (no description available)
--
-----
| ,''`.Stephen Gran |
| : :' :sg...@debian.org |
| `. `'Debian user, admin, and developer |
|`- http://www.debian.org |
-
signature.asc
Description: Digital signature
Bug#679751: please clarify package account and home directory location in policy
This one time, at band camp, Marc Haber said: > The package itself caters only for presenter and collector on the same > machine, which is done to give a working setup after installation. The > package is not likely to be used in this configuration in any > productive environment. ssh is one of the variants that is offered to > the admin as optional, local configuration. So she needs to manually > touch ssh stuff. I'd argue you're Doing It Wrong, putting this stuff in a system account user's $HOME. Have sshd look in /etc/ssh/userkeys for an additional authorized_keys file, and set up an /etc/ssh/known_hosts for the hosts you want the machine to log into. The machines that need the private key part can use a key stored anywhere on the system with ssh -i. There is no need to go into complicated backbends about policy to support local misconfiguration. I think it's fairly clear that in this case, the package doesn't depend on anything in $HOME, so it doesn't matter where it goes, except as Russ points out, for practical reasons (nfs mounted /home with root_squash, eg). I'd even argue that this is a site policy decision - where adduser puts new home directories by default is configurable, and if you decide to nfs mount /home you should probably change the default to something that will work. If you find a package that, out of the box, depends on something in $HOME and places $HOME under /home, please file a bug on that package. That is fairly obviously buggy. Cheers, -- - | ,''`.Stephen Gran | | : :' :sg...@debian.org | | `. `'Debian user, admin, and developer | |`- http://www.debian.org | - signature.asc Description: Digital signature
Bug#679746: [Adduser-devel] Bug#679746: default --system home directory leads to piuparts RC bugs
Hi, This one time, at band camp, Marc Haber said: > On Sun, Jul 01, 2012 at 03:43:42PM +0100, Stephen Gran wrote: > > This one time, at band camp, Marc Haber said: > > > Thus, packages using adduser --system and relying on adduser doing the > > > right thing will get a piuparts-based RC bug in no time. Adduser > > > should change its default behavior to something that QA will accept. > > > > And what directory would that be, then? > > Since policy does not give any hints about that, adduser --system > should probably insist on --home being given. I think I'd like to summarize, if I may: Policy says packages can't rely on the layout of /home/ Some packages invoke adduser --system without the switch --home In this case, adduser creates a user with $HOME under /home/ There is so far no evidence that these packages rely on the presence of that directory You think this is a release-critical bug in adduser You have filed this as we freeze Congratulations. Now, I don't agree that this is a bug in adduser - I think this is a bug in packages invoking adduser. I think the right way to do this is a mass bug filing on those packages. Your suggestion of a 'fix' makes lots of packages insta-buggy, which is effectively the same as a mass bug-filing. So, unless you can give me compelling arguments that this is actually adduser's problem to solve, I'd like you to talk about your prospective mass bug-filing on -devel. Cheers, -- --------- | ,''`.Stephen Gran | | : :' :sg...@debian.org | | `. `'Debian user, admin, and developer | |`- http://www.debian.org | - -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#679746: default --system home directory leads to piuparts RC bugs
This one time, at band camp, Marc Haber said: > Thus, packages using adduser --system and relying on adduser doing the > right thing will get a piuparts-based RC bug in no time. Adduser > should change its default behavior to something that QA will accept. And what directory would that be, then? I think this is a strange interpretation of policy, that it's the tool that is buggy and not the invocation. Cheers, -- - | ,''`. Stephen Gran | | : :' :sg...@debian.org | | `. `'Debian user, admin, and developer | |`- http://www.debian.org | - signature.asc Description: Digital signature
Bug#678247: [Pkg-clamav-devel] Bug#678247: Fix debdiff
This one time, at band camp, Scott Kitterman said: > I did test it. It defaults to 8080 if you don't specify. Perfect :) Just my memory being bad, then. Cheers, -- - | ,''`. Stephen Gran | | : :' :sg...@debian.org | | `. `'Debian user, admin, and developer | |`- http://www.debian.org | - signature.asc Description: Digital signature
Bug#678247: [Pkg-clamav-devel] Bug#678247: Fix debdiff
This one time, at band camp, Scott Kitterman said: > Attached. Hi, Have you tested that that is a valid config file? I have some vague memory of freshclam not being happy with a proxyhost but not a proxyport. Cheers, -- - | ,''`. Stephen Gran | | : :' :sg...@debian.org | | `. `'Debian user, admin, and developer | |`- http://www.debian.org | - signature.asc Description: Digital signature
Bug#673461: [Pkg-puppet-devel] Bug#673461: facter: processor fact is wrong on some arches
Hi, This one time, at band camp, Stig Sandbeck Mathisen said: > Version: 1.6.2-1 > > micah anderson writes: > > > Can you try the newest bpo version of facter to see if it still is > > the same? > > in 1.5.7, facter parses /proc/cpuinfo, which unfortunately has a > different format for each architecture. > > In 1.6.2 (commit at http://deb.li/ii11z), the "processor" facts > started using sysfs instead. I'll mark this bug as closed, with this > version. It's quite a bit better, in that it now gives the correct processorcount on linux machines. It still doesn't give a processorcount on kfreebsd at all. It seems this is trying to use sysfs as well - that won't work on kfreebsd. While processorcount is now correct, it seems that other processor information is still missing on s390, s390x, ppc, mips and mipsel. That just seems to be missing switches in the case statement. Cheers, -- ----- | ,''`.Stephen Gran | | : :' :sg...@debian.org | | `. `'Debian user, admin, and developer | |`- http://www.debian.org | - signature.asc Description: Digital signature
Bug#673461: facter: processor fact is wrong on some arches
Package: facter Version: 1.5.7-3 Severity: normal Hello, I recently broke a few things (oops, mea culpa) by assuming rather naively that all machines have processors. Apparently, facter does not agree. A quick looks says: arm/armel: abel.debian.org.yaml:processorcount: "0" agricola.debian.org.yaml:processorcount: "0" alain.debian.org.yaml:processorcount: "0" alwyn.debian.org.yaml:processorcount: "0" ancina.debian.org.yaml:processorcount: "0" antheil.debian.org.yaml:processorcount: "0" arcadelt.debian.org.yaml:processorcount: "0" argento.debian.org.yaml:processorcount: "0" arne.debian.org.yaml:processorcount: "0" arnold.debian.org.yaml:processorcount: "0" mips/mipsel: ball.debian.org.yaml:processorcount: "0" corelli.debian.org.yaml:processorcount: "0" eder.debian.org.yaml:processorcount: "0" eysler.debian.org.yaml:processorcount: "0" gabrielli.debian.org.yaml:processorcount: "0" lucatelli.debian.org.yaml:processorcount: "0" mayer.debian.org.yaml:processorcount: "0" rem.debian.org.yaml:processorcount: "0" sparc: lebrun.debian.org.yaml:processorcount: "0" schroeder.debian.org.yaml:processorcount: "0" smetana.debian.org.yaml:processorcount: "0" sompek.debian.org.yaml:processorcount: "0" spontini.debian.org.yaml:processorcount: "0" stadler.debian.org.yaml:processorcount: "0" ppc: parry.debian.org.yaml:processorcount: "0" partch.debian.org.yaml:processorcount: "0" piston.debian.org.yaml:processorcount: "0" porpora.debian.org.yaml:processorcount: "0" poulenc.debian.org.yaml:processorcount: "0" praetorius.debian.org.yaml:processorcount: "0" s390: zandonai.debian.org.yaml:processorcount: "0" zappa.debian.org.yaml:processorcount: "0" zelenka.debian.org.yaml:processorcount: "0" zemlinsky.debian.org.yaml:processorcount: "0" It seems as though this fact really only works the way it's intended to work on intel/amd chips? Cheers, -- System Information: Debian Release: 6.0.5 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.utf8) Shell: /bin/sh linked to /bin/dash Versions of packages facter depends on: ii bind9-host [host 1:9.7.3.dfsg-1~squeeze4 Version of 'host' bundled with BIN ii libruby1.8 [libo 1.8.7.302-2squeeze1 Libraries necessary to run Ruby 1. ii net-tools1.60-23 The NET-3 networking toolkit ii ruby1.8 1.8.7.302-2squeeze1 Interpreter of object-oriented scr Versions of packages facter recommends: ii pciutils 1:3.1.7-6 Linux PCI Utilities facter suggests no packages. -- no debconf information -- - | ,''`.Stephen Gran | | : :' :sg...@debian.org | | `. `'Debian user, admin, and developer | |`- http://www.debian.org | - signature.asc Description: Digital signature
Bug#669255: hdparm: Harddisk continuously spins up and down whilst on battery power
reassign 669255 gnome-power-manager thanks This one time, at band camp, Martin Erik Werner said: > On Wed, 2012-04-18 at 18:53 +0100, Stephen Gran wrote: > > This one time, at band camp, Martin Erik Werner said: > > > Dear Maintainer, > > > During roughly the last couple of weeks my laptop disk has stared to > > > continuously spin up and down excessively, resulting in hiccups in GNOME > > > and > > > applications. > > > > > > I'm suspecting that this might be due to hdparm introducing new settings > > > for > > > apm_battery, since if I set that to 128 instead of the default 127 the > > > behaviours goes away (obviously). > > > > hdparm does not set anything by default. Can you let me know what power > > management you use so that I can reassign this bug to them? > > > > Cheers, > > Hmm, I don't actually know which I am using to be honest, whatever is > the default? > I have stock gnome3 install from a direct Wheezy install. Would the > power management be simply GNOME / gnome-power-manager? Sounds like it. I'll reassing now. Cheers, -- - | ,''`.Stephen Gran | | : :' :sg...@debian.org | | `. `'Debian user, admin, and developer | |`- http://www.debian.org | - signature.asc Description: Digital signature
Bug#669255: hdparm: Harddisk continuously spins up and down whilst on battery power
This one time, at band camp, Martin Erik Werner said: > Dear Maintainer, > During roughly the last couple of weeks my laptop disk has stared to > continuously spin up and down excessively, resulting in hiccups in GNOME and > applications. > > I'm suspecting that this might be due to hdparm introducing new settings for > apm_battery, since if I set that to 128 instead of the default 127 the > behaviours goes away (obviously). hdparm does not set anything by default. Can you let me know what power management you use so that I can reassign this bug to them? Cheers, -- - | ,''`. Stephen Gran | | : :' :sg...@debian.org | | `. `'Debian user, admin, and developer | |`- http://www.debian.org | - signature.asc Description: Digital signature
Bug#660897: ping?
Hi, It's been a month. Have you had a chance to look at this yet? I'm going to change the severity to important, as it is going to mean that, out of the box, syslog-ng does not work on machines using a local recursor. As this is a reasonably common arrangement on servers, I would think this bug will end up hitting a fair number of people. Cheers, -- - | ,''`. Stephen Gran | | : :' :sg...@debian.org | | `. `'Debian user, admin, and developer | |`- http://www.debian.org | - signature.asc Description: Digital signature
Bug#664869: /usr/sbin/addgroup: syntax `adduser user group' not mentioned
Hi, This one time, at band camp, Mike Dornberger said: > Hi, > > neither the man page of addgroup nor the output of `addgroup -h' > mentions the valid syntax `addgroup user group' to add the user to the > specified group, but in fact this works: Ah, it shouldn't. Thanks for letting us know :) Cheers, -- - | ,''`. Stephen Gran | | : :' :sg...@debian.org | | `. `'Debian user, admin, and developer | |`- http://www.debian.org | - signature.asc Description: Digital signature
Bug#660448: Using winbind in nsswitch.conf broken due to missing libs
This one time, at band camp, Kevin Shanahan said: > Using winbind in /etc/nsswitch.conf is completely broken since > 3.5.11~dfsg-4 due to missing libraries: > >/lib/libnss_winbind.so.2 >/lib/libnss_wins.so.2 > > It seems they were there up to 3.5.11~dfsg-2 and then just > disappeared. > > This is on amd64 - I haven't checked any other arch. They seem to have migrated to libpam-winbind. Cheers, -- - | ,''`. Stephen Gran | | : :' :sg...@debian.org | | `. `'Debian user, admin, and developer | |`- http://www.debian.org | - signature.asc Description: Digital signature
Bug#658750: host type cannot represent a host with more than one ip
Package: puppet Version: 2.6.2-5+squeeze3 Severity: normal Hi, This is now http://projects.puppetlabs.com/issues/12438 Cheers, -- System Information: Debian Release: 6.0.3 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.utf8) Shell: /bin/sh linked to /bin/dash Versions of packages puppet depends on: ii adduser 3.112+nmu2 add and remove users and groups ii facter 1.5.7-3 a library for retrieving facts fro pn libopenssl-ruby(no description available) ii libruby [libxmlrpc-r 4.5 Libraries necessary to run Ruby 1. ii libshadow-ruby1.81.4.1-8 Interface of shadow password for R ii lsb-base 3.2-23.2squeeze1Linux Standard Base 3.2 init scrip ii puppet-common2.6.2-5+squeeze3Centralized configuration manageme ii ruby1.8 1.8.7.302-2squeeze1 Interpreter of object-oriented scr Versions of packages puppet recommends: pn libaugeas-ruby1.8 (no description available) ii ruby [rdoc] 4.5An interpreter of object-oriented Versions of packages puppet suggests: pn libselinux-ruby1.8 (no description available) pn puppet-el (no description available) pn vim-puppet (no description available) -- no debconf information -- - | ,''`. Stephen Gran | | : :' :sg...@debian.org | | `. `'Debian user, admin, and developer | |`- http://www.debian.org | - signature.asc Description: Digital signature
Bug#658750: host type cannot represent a host with more than one ip
Package: puppet
Version: 2.6.2-5+squeeze3
Severity: normal
Hi,
Just as an example of how this should work, and some of the complaints
from puppet:
sgran@harris:~$ cat /etc/hosts
##
## THIS FILE IS UNDER PUPPET CONTROL. DON'T EDIT IT HERE.
## USE: git clone
git+ssh://$u...@puppet.debian.org/srv/puppet.debian.org/git/dsa-puppet.git
##
127.0.0.1 localhost
172.28.17.17harris.debian.org harris
2001:41b8:202:deb:214:22ff:fe13:492b heininen.debian.org heininen
82.195.75.98 heininen.debian.org heininen
2607:f8f0:610:4000:216:36ff:fe40:380c lotti.debian.org lotti
206.12.19.121 lotti.debian.org lotti
# The following lines are desirable for IPv6 capable hosts
::1 localhost ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts
sgran@harris:~$ getent hosts heininen.debian.org
2001:41b8:202:deb:214:22ff:fe13:492b heininen.debian.org heininen
sgran@harris:~$ telnet heininen.debian.org 22
Trying 82.195.75.98...
Connected to heininen.debian.org.
sgran@harris:~$ puppet resource host heininen.debian.org
warning: Host heininen.debian.org found in both parsed and parsed; skipping the
parsed version
warning: Host lotti.debian.org found in both parsed and parsed; skipping the
parsed version
warning: Host localhost found in both parsed and parsed; skipping the parsed
version
host { 'heininen.debian.org':
ip => '82.195.75.98',
host_aliases => ['heininen'],
target => '/etc/hosts',
ensure => 'present'
}
Cheers,
-- System Information:
Debian Release: 6.0.3
APT prefers stable
APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.32-5-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) (ignored: LC_ALL
set to en_US.utf8)
Shell: /bin/sh linked to /bin/dash
Versions of packages puppet depends on:
ii adduser 3.112+nmu2 add and remove users and groups
ii facter 1.5.7-3 a library for retrieving facts fro
pn libopenssl-ruby(no description available)
ii libruby [libxmlrpc-r 4.5 Libraries necessary to run Ruby 1.
ii libshadow-ruby1.81.4.1-8 Interface of shadow password for R
ii lsb-base 3.2-23.2squeeze1Linux Standard Base 3.2 init scrip
ii puppet-common2.6.2-5+squeeze3Centralized configuration manageme
ii ruby1.8 1.8.7.302-2squeeze1 Interpreter of object-oriented scr
Versions of packages puppet recommends:
pn libaugeas-ruby1.8 (no description available)
ii ruby [rdoc] 4.5An interpreter of object-oriented
Versions of packages puppet suggests:
pn libselinux-ruby1.8 (no description available)
pn puppet-el (no description available)
pn vim-puppet (no description available)
-- no debconf information
--
---------
| ,''`.Stephen Gran |
| : :' :sg...@debian.org |
| `. `'Debian user, admin, and developer |
|`- http://www.debian.org |
-
signature.asc
Description: Digital signature
Bug#658750: puppet: host type cannot represent a host with more than one ip
Package: puppet
Version: 2.6.2-5+squeeze3
Severity: normal
Hi,
The puppet host type seems to think that all hostnames map to one and
only one ip address. This is just not true. This makes it impossible
to represent, for instance, the following:
steve@varinia:~$ getent hosts google.com
74.125.230.80 google.com
74.125.230.81 google.com
74.125.230.82 google.com
74.125.230.83 google.com
74.125.230.84 google.com
Or, the more interesting use case for me, a multi-homed host. If the
host type didn't conflate $name with the first entry after the ip, you
could kludge this with
host {
$host-ipv4:
hostname => $host,
ip => 1.2.3.4;
$host-ipv6:
hostname => $host,
ip => 2001::1;
}
But I can't even do that. I think the best thing is for ip to be
changed to be able to take an array, personally, but I'm also not picky
about how this is resolved (not an intentional pun there, sorry).
Cheers,
-- System Information:
Debian Release: 6.0.3
APT prefers stable
APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.32-5-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) (ignored: LC_ALL
set to en_US.utf8)
Shell: /bin/sh linked to /bin/dash
Versions of packages puppet depends on:
ii adduser 3.112+nmu2 add and remove users and groups
ii facter 1.5.7-3 a library for retrieving facts fro
pn libopenssl-ruby(no description available)
ii libruby [libxmlrpc-r 4.5 Libraries necessary to run Ruby 1.
ii libshadow-ruby1.81.4.1-8 Interface of shadow password for R
ii lsb-base 3.2-23.2squeeze1Linux Standard Base 3.2 init scrip
ii puppet-common2.6.2-5+squeeze3Centralized configuration manageme
ii ruby1.8 1.8.7.302-2squeeze1 Interpreter of object-oriented scr
Versions of packages puppet recommends:
pn libaugeas-ruby1.8 (no description available)
ii ruby [rdoc] 4.5An interpreter of object-oriented
Versions of packages puppet suggests:
pn libselinux-ruby1.8 (no description available)
pn puppet-el (no description available)
pn vim-puppet (no description available)
-- no debconf information
--
-
| ,''`. Stephen Gran |
| : :' :sg...@debian.org |
| `. `'Debian user, admin, and developer |
|`- http://www.debian.org |
-
signature.asc
Description: Digital signature
Bug#658665: [Pkg-clamav-devel] Bug#658665: clamav-daemon: assumes clamav uid and gid are the same
This one time, at band camp, Matt Taggart said: > Package: clamav-daemon > Version: 0.97.3+dfsg-1~lenny1 > > Somewhere in clamav-daemon it's assuming that the clamav uid and gid are > the same. If I remove /var/run/clamav/clamav.ctl and then restart clamav, > I get this > > /var/run/clamav# ls -la clamd.ctl > s- 1 clamav postdrop0 Feb 4 15:07 clamd.ctl > > On my system the clamav user has uid 108 and the postdrop group has gid 108. > > When I set them to both use the same number then it works > > srw-rw-rw- 1 clamav clamav 0 Feb 4 15:58 clamd.ctl Can you send the output of `getent passwd clamav` ? Cheers, -- - | ,''`.Stephen Gran | | : :' :sg...@debian.org | | `. `'Debian user, admin, and developer | |`- http://www.debian.org | - signature.asc Description: Digital signature
Bug#654873: hdparm -i on a USB external drive adapter causes connection reset
This one time, at band camp, Olivier Berger said: > Trying to spot why I get lots of messages (every 5 minutes) in the logs like : > Jan 6 14:20:11 sheeva kernel: [15786.065467] usb 1-1.4: reset high speed USB > device using orion-ehci and address 5 > Jan 6 14:20:12 sheeva kernel: [15786.265469] usb 1-1.4: reset high speed USB > device using orion-ehci and address 5 > > I happened to execute : > # hdparm -i /dev/sdb > > and get : > > /dev/sdb: > HDIO_DRIVE_CMD(identify) failed: Invalid argument > HDIO_GET_IDENTITY failed: Invalid argument > > Which causes an immediate log in question. This error message means hdparm got EINVAL back from an ioctl to get information. This is almost always a driver issue. I'd say 2 things to this: First, if a userspace process can cause a bus reset by calling a well-defined ioctl, this is a kernel bug. Second, hdparm doesn't run by itself, so it didn't create all those lines in your logs. I'm happy to leave this bug open while you take a look on your system for other things that may be calling hdparm (or calling the HDIO_DRIVE_CMD and HDIO_GET_IDENTITY ioctl()s directly), but I don't think this is likely to end up as an hdparm issue. Cheers, -- --------- | ,''`.Stephen Gran | | : :' :sg...@debian.org | | `. `'Debian user, admin, and developer | |`- http://www.debian.org | - signature.asc Description: Digital signature
Bug#654792: monit: why is the daemon binary moved?
Package: monit Version: 1:5.3.2-1 Severity: normal Hello, I understand that the same binary can be used to connect to the daemon, so it might be useful for some corner cases to have it in /usr/bin. However, I'd think the vast majority of people using monit expect it to be a system service with config in /etc and run as root, which means the old location of /usr/sbin might be more appropriate. I didn't see anything in README.Debian about this, by the way - I would have thought a change that broke scripts would at least be mentioned. Cheers, -- System Information: Debian Release: 6.0.3 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.utf8) Shell: /bin/sh linked to /bin/dash -- - | ,''`. Stephen Gran | | : :' :sg...@debian.org | | `. `'Debian user, admin, and developer | |`- http://www.debian.org | - signature.asc Description: Digital signature
Bug#654449: monit: error in init script
Package: monit Version: 1:5.3.2-1 Severity: normal Hi, Today's upgrade saw: Installing new version of config file /etc/init.d/monit ... /etc/init.d/monit: 39: [: start: unexpected operator Line 39 is: if [ "$1" == "start" ] Which is a bashism. Please either use '=' or set the shebang to be /bin/bash. As an aside, your bug script should probably handle EPERM a little better :) Cheers, -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: armhf (armv7l) Kernel: Linux 2.6.35.3 (PREEMPT) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.utf8) Shell: /bin/sh linked to /bin/dash Versions of packages monit depends on: ii libc62.13-24 ii libgcc1 1:4.6.2-9 ii libpam0g 1.1.3-6+b1 ii libssl1.0.0 1.0.0e-3 ii lsb-base 3.2-28 monit recommends no packages. Versions of packages monit suggests: ii exim4-daemon-heavy [mail-transport-agent] 4.77-1+b1 -- Configuration Files: /etc/default/monit changed: startup=0 /etc/monit/monitrc [Errno 13] Permission denied: u'/etc/monit/monitrc' -- no debconf information -- - | ,''`.Stephen Gran | | : :' :sg...@debian.org | | `. `'Debian user, admin, and developer | |`- http://www.debian.org | - -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#652009: [Pkg-clamav-devel] Bug#652009: Bug#652009: /usr/share/doc/clamav-testfiles: test signature not found in all files
This one time, at band camp, Farmbuyer said: > On Tue, Dec 13, 2011 at 11:34 PM, Scott Kitterman wrote: > > On Tuesday, December 13, 2011 09:58:55 PM Farmbuyer wrote: > >> Package: clamav-testfiles > >> Version: 0.97.3+dfsg-2 > >> Severity: minor > >> File: /usr/share/doc/clamav-testfiles > >> > >> The files in clamav-testfiles are all supposed to be "infected" with > >> a known test signature. Two of them aren't: > >> > >> $ clamscan /usr/share/clamav-testfiles/* | grep -v ClamAV-Test-File > >> /usr/share/clamav-testfiles/clam-v2.rar: OK > >> /usr/share/clamav-testfiles/clam-v3.rar: OK > > > > Do you have libclamunrar from non-free installed? Clamav can't scan rar > > files > > without it. > > I do not. Is this documented somewhere? I don't have access to > /use/share/doc/clamav-testfiles right now to check. A note in README.Debian > would be enough, if it's not already there. ~$ apt-cache show libclamunrar6 But yes, I suppose a note in README.Debian might be clearer. I've checked something in now. Cheers, -- - | ,''`.Stephen Gran | | : :' :sg...@debian.org | | `. `'Debian user, admin, and developer | |`- http://www.debian.org | - signature.asc Description: Digital signature
Bug#618728: patch for issues
tag 645016 + patch tag 631580 + patch tag 618728 + patch thanks Hi, The attached patch should sort out these two issues. Cheers, -- - | ,''`. Stephen Gran | | : :' :sg...@debian.org | | `. `'Debian user, admin, and developer | |`- http://www.debian.org | - diff -u samhain-2.6.2/debian/samhain.logrotate.d samhain-2.6.2/debian/samhain.logrotate.d --- samhain-2.6.2/debian/samhain.logrotate.d +++ samhain-2.6.2/debian/samhain.logrotate.d @@ -8,7 +8,7 @@ create 640 root adm sharedscripts postrotate - if [ -f /var/run/samhain.pid ]; then \ + if [ -f /var/run/samhain/samhain.pid ]; then \ /etc/init.d/samhain reload > /dev/null; fi endscript } diff -u samhain-2.6.2/debian/samhain.init samhain-2.6.2/debian/samhain.init --- samhain-2.6.2/debian/samhain.init +++ samhain-2.6.2/debian/samhain.init @@ -36,6 +36,7 @@ if test -f /var/samhain/.samhain_lock; then rm -f /var/samhain/.samhain_lock fi + mkdir -p /var/run/samhain start-stop-daemon --start --quiet --exec $DAEMON log_end_msg $? # diff -u samhain-2.6.2/debian/rules samhain-2.6.2/debian/rules --- samhain-2.6.2/debian/rules +++ samhain-2.6.2/debian/rules @@ -11,6 +11,18 @@ # This is the debhelper compatability version to use. # export DH_COMPAT=5 +ifeq (linux,$(DEB_HOST_ARCH_OS)) +ifeq (ia64,$(DEB_HOST_ARCH)) +DNMALLOC = --disable-dnmalloc +else ifeq (s390,$(DEB_HOST_ARCH)) +DNMALLOC = --disable-dnmalloc +else +DNMALLOC = --enable-dnmalloc +endif +else +DNMALLOC = --disable-dnmalloc +endif + build: build-stamp build-stamp: dh_testdir @@ -19,8 +31,9 @@ --with-config-file=/etc/samhain/samhainrc \ --with-state-dir=/var/state/samhain \ --with-prelude \ + $(DNMALLOC) \ --enable-network=no \ - --with-pid-file=/var/run/samhain.pid \ + --with-pid-file=/var/run/samhain/samhain.pid \ --with-log-file=/var/log/samhain/samhain.log $(MAKE) diff -u samhain-2.6.2/debian/changelog samhain-2.6.2/debian/changelog --- samhain-2.6.2/debian/changelog +++ samhain-2.6.2/debian/changelog @@ -1,3 +1,12 @@ +samhain (2.6.2-2.1) unstable; urgency=low + + * Non-maintainer upload. + * Disable dnmalloc where we know it doesn't work (closes: #618728) + * Switch back to /var/run/samhain, as /var/run is now a symlink to /run, and +samhain won't run if it's piddir is a symlink. (closes: #645016, #631580) + + -- Stephen Gran Wed, 12 Oct 2011 07:27:14 + + samhain (2.6.2-2) unstable; urgency=low * Change configuration so that the pidfile used is /var/run/samhain.pid signature.asc Description: Digital signature
Bug#645016: samhain: /run transition: fails to start
pd file=/etc/munin/plugins/apache_accesses file=/etc/munin/plugins/apache_processes file=/etc/munin/plugins/apache_volume file=/etc/munin/plugins/apache_servers file=/etc/munin/plugins/exim_mailqueue file=/etc/munin/plugins/exim_mailstats file=/etc/munin/plugins/postfix_mailqueue file=/etc/munin/plugins/postfix_mailvolume file=/etc/apache2/conf.d/ressource-limits file=/etc/apache2/mods-enabled/info.conf file=/etc/apache2/mods-enabled/info.load file=/etc/apache2/mods-enabled/server.conf file=/etc/apache2/mods-enabled/server.load file=/etc/apache2/conf.d/server-status file=/etc/apache2/conf.d/local-serverinfo file=/etc/apache2/sites-available/www.debian.org file=/etc/apt/preferences file=/etc/apt/sources.list.d/volatile.list file=/etc/apt/sources.list.d/security.list file=/etc/apt/sources.list.d/buildd.list file=/etc/apt/sources.list.d/debian.org.list file=/etc/apt/sources.list.d/debian.restricted.list file=/etc/apt/sources.list.d/debian.list file=/etc/apt/sources.list.d/backports.org.list file=/etc/apt/apt.conf.d/local-recommends file=/etc/apt/apt.conf.d/local-pdiffs file=/etc/puppet/puppet.conf file=/etc/default/puppet file=/etc/default/postgrey file=/etc/default/schroot file=/etc/default/syslog-ng file=/etc/logrotate.d/exim4-paniclog file=/etc/logrotate.d/exim4-base file=/etc/logrotate.d/syslog-ng file=/etc/syslog-ng/syslog-ng.conf file=/usr/sbin/dsa-update-apt-status file=/usr/sbin/dsa-update-samhain-status file=/etc/nagios/nrpe.d/nrpe_dsa.cfg file=/etc/nagios/nrpe.d/debianorg.cfg file=/etc/nagios/obsolete-packages-ignore file=/etc/nagios/obsolete-packages-ignore.d/hostspecific file=/usr/lib/nagios/plugins/dsa-check-packages file=/usr/lib/nagios/plugins/dsa-check-soas file=/usr/lib/nagios/plugins/dsa-check-mirrorsync file=/usr/lib/nagios/plugins/dsa-check-samhain file=/usr/lib/nagios/plugins/dsa-check-statusfile file=/usr/lib/nagios/plugins/dsa-check-dabackup-server file=/usr/lib/nagios/plugins/dsa-check-config file=/usr/lib/nagios/plugins/dsa-check-hpacucli file=/usr/lib/nagios/plugins/dsa-check-raid-mpt file=/usr/lib/nagios/plugins/dsa-check-puppet file=/usr/lib/nagios/plugins/dsa-check-running-kernel file=/usr/lib/nagios/plugins/dsa-check-raid-3ware file=/usr/lib/nagios/plugins/dsa-check-dabackup file=/usr/lib/nagios/plugins/dsa-check-raid-dac960 file=/usr/lib/nagios/plugins/dsa-check-udldap-freshness file=/usr/lib/nagios/plugins/dsa-check-raid-areca file=/usr/lib/nagios/plugins/dsa-check-raid-sw file=/usr/lib/nagios/plugins/dsa-update-samhain-status file=/etc/sudoers file=/etc/sysctl.d/mmap_min_addr.conf file=/etc/pam.d/sudo file=/etc/monit/monitrc file=/etc/monit/monit.d/01puppet file=/etc/monit/monit.d/00debian.org file=/etc/cron.d/dsa-puppet-stuff file=/etc/cron.d/dsa-buildd dir=1/etc/ferm/dsa.d file=/etc/ferm/conf.d/me.conf file=/etc/ferm/conf.d/defs.conf file=/etc/ferm/ferm.conf dir=2/etc/ssl/debian file=/etc/unbound/unbound.conf [IgnoreNone] [Prelink] [ReadOnly] dir=/usr/bin dir=/bin dir=/boot dir=3/sbin dir=/usr/sbin dir=/lib dir=3/usr/lib dir=3/usr/share dir=3/etc file=/usr/lib/pt_chown [User0] [User1] [EventSeverity] SeverityReadOnly=crit SeverityLogFiles=crit SeverityGrowingLogs=warn SeverityIgnoreNone=crit SeverityAttributes=crit SeverityIgnoreAll=info SeverityFiles=crit SeverityDirs=crit SeverityNames=warn [Log] MailSeverity=crit PrintSeverity=none LogSeverity=info SyslogSeverity=alert [Misc] Daemon = yes ChecksumTest=check SetLoopTime = 600 SetFileCheckTime = 7200 SetMailTime = 86400 SetMailNum = 10 SetMailAddress=samhain-repo...@harris.debian.org SetMailRelay = localhost MailSubject = [Samhain at %H] %T: %S SyslogFacility=LOG_LOCAL2 [EOF] -- debconf information: samhain/init-log: -- - | ,''`. Stephen Gran | | : :' :sg...@debian.org | | `. `'Debian user, admin, and developer | |`- http://www.debian.org | - -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#644870: libshadow-ruby1.8: wrong path on armhf
Package: libshadow-ruby1.8 Version: 1.4.1-8 Severity: important Hi, On installing puppet on some new machines for the armhf bringup, we found that it wouldn't run. Investigation showed that it's because /usr/lib/ruby/1.8/arm-linux-eabi/shadow.so is in the wrong place. Creating a symlink from /usr/lib/ruby/1.8/arm-linux-eabihf/shadow.so backed to the shipped file works just fine, so it's clear that it's not being miscompiled, just placed in the wrong path. Cheers, -- System Information: Debian Release: wheezy/sid APT prefers unreleased APT policy: (500, 'unreleased'), (500, 'unstable') Architecture: armhf (armv7l) Kernel: Linux 2.6.35.3 (PREEMPT) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.utf8) Shell: /bin/sh linked to /bin/dash Versions of packages libshadow-ruby1.8 depends on: ii libc6 2.13-21 ii libruby1.8 1.8.7.352-2 libshadow-ruby1.8 recommends no packages. libshadow-ruby1.8 suggests no packages. -- no debconf information -- - | ,''`. Stephen Gran | | : :' :sg...@debian.org | | `. `'Debian user, admin, and developer | |`- http://www.debian.org | - -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#644869: libaugeas-ruby1.8: wrong path on armhf
Package: libaugeas-ruby1.8 Version: 0.3.0-1.1 Severity: important Hi, On installing puppet on some new machines for the armhf bringup, we found that it wouldn't run. Investigation showed that it's because /usr/lib/ruby/1.8/arm-linux-eabi/_augeas.so is in the wrong place. Creating a symlink from /usr/lib/ruby/1.8/arm-linux-eabihf/_augeas.so backed to the shipped file works just fine, so it's clear that it's not being miscompiled, just placed in the wrong path. Cheers, -- System Information: Debian Release: wheezy/sid APT prefers unreleased APT policy: (500, 'unreleased'), (500, 'unstable') Architecture: armhf (armv7l) Kernel: Linux 2.6.35.3 (PREEMPT) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.utf8) Shell: /bin/sh linked to /bin/dash Versions of packages libaugeas-ruby1.8 depends on: ii libaugeas0 0.8.1-2 ii libc6 2.13-21 ii libruby1.8 1.8.7.352-2 ii ruby1.8 1.8.7.352-2 libaugeas-ruby1.8 recommends no packages. libaugeas-ruby1.8 suggests no packages. -- - | ,''`. Stephen Gran | | : :' :sg...@debian.org | | `. `'Debian user, admin, and developer | |`- http://www.debian.org | - -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#610306: Fwd: [Pkg-net-snmp-devel] Bug#610306: marked as done (wrong status when snmptrapd not configured to start)
This one time, at band camp, Jochen Friedrich said: > Hi Stephen, > > did I miss something or are NMUs for minor bug allowed now even > without a delay slot? > > BTW: The way you did it (without opening a bug with the corresponding > patch) would habe been a good way to ensure the bug will be back in > the next version, as the patch does not magically appear in our SVN > just by submitting an NMU ;-) Hi, Sorry about that - I was planning to do the nmudiff dance, and got distracted. I've done so now. The upload was based on this conversation on #debian-release: 16:51:11< sgran> hello. 610306 is biting me at work. Would you consider an upload with that patch for a stable point release update? 16:51:56 * jcristau holds the 'not before it's fixed in sid' card 16:52:51< sgran> that's fair enough 16:52:56< sgran> I'd be willing to do both 16:52:59< adsb> there's that, but in general yeah from a first glance it sounds reasonable enough 16:53:13< sgran> cool 16:53:29< sgran> I'll try to get it uploaded in the next few days and then follow up with a mail? 16:53:55< adsb> the severity's below our technical radar for stable, but I'd argue the bug should be > minor anyway 16:54:24< sgran> the issue we're seeing is that it breaks puppet's logic for "is the service running", so it restarts snmpd on every puppet run 16:54:35< adsb> sgran: a usertagged bug would be nice if you could :) they're easier to keep track of than random mails on the list 16:54:45< sgran> sounds good 16:54:46< sgran> will do 16:54:48< sgran> thanks 16:55:02< adsb> that sounds suboptimal. and not "minor". at least imho Sorry for not sending that to the bug log earlier. Cheers, -- - | ,''`.Stephen Gran | | : :' :sg...@debian.org | | `. `'Debian user, admin, and developer | |`- http://www.debian.org | - signature.asc Description: Digital signature
Bug#639511: net-snmp: diff for NMU version 5.4.3~dfsg-2.3
Package: net-snmp Version: 5.4.3~dfsg-2.2 Severity: normal Tags: patch pending Dear maintainer, I've prepared and uploaded an NMU for net-snmp (versioned as 5.4.3~dfsg-2.3) based on the patch in the bug report. Regards. -- - | ,''`. Stephen Gran | | : :' :sg...@debian.org | | `. `'Debian user, admin, and developer | |`- http://www.debian.org | - diff -Nru net-snmp-5.4.3~dfsg/debian/changelog net-snmp-5.4.3~dfsg/debian/changelog --- net-snmp-5.4.3~dfsg/debian/changelog 2011-05-09 10:19:06.0 +0100 +++ net-snmp-5.4.3~dfsg/debian/changelog 2011-08-27 10:18:25.0 +0100 @@ -1,3 +1,12 @@ +net-snmp (5.4.3~dfsg-2.3) unstable; urgency=low + + * Non-maintainer upload. + * Fix for init script status command when trapd is not running. Thanks to +Steve Camfield for the patch +(closes: #610306) + + -- Stephen Gran Sat, 27 Aug 2011 09:10:09 + + net-snmp (5.4.3~dfsg-2.2) unstable; urgency=high * Non-maintainer upload. diff -Nru net-snmp-5.4.3~dfsg/debian/snmpd.init net-snmp-5.4.3~dfsg/debian/snmpd.init --- net-snmp-5.4.3~dfsg/debian/snmpd.init 2011-01-05 12:12:04.0 + +++ net-snmp-5.4.3~dfsg/debian/snmpd.init 2011-08-27 09:55:59.0 +0100 @@ -90,8 +90,12 @@ ;; status) status=0 -status_of_proc /usr/sbin/snmpd snmpd || status=$? -status_of_proc /usr/sbin/snmptrapd snmptrapd || status=$? +if [ "$SNMPDRUN" = "yes" -a -f /etc/snmp/snmpd.conf ]; then + status_of_proc /usr/sbin/snmpd snmpd || status=$? +fi +if [ "$TRAPDRUN" = "yes" -a -f /etc/snmp/snmptrapd.conf ]; then + status_of_proc /usr/sbin/snmptrapd snmptrapd || status=$? +fi exit $status ;; *) signature.asc Description: Digital signature
Bug#636082: /usr/bin/timeout: coreutils: timeout doesn't seem to work on kfreebsd
Package: coreutils Version: 8.5-1 Severity: normal File: /usr/bin/timeout Hi, sgran@finzi:~$ date Sat Jul 30 21:11:46 UTC 2011 sgran@finzi:~$ ps axuf | grep 'Jul23' root 2152 0.0 0.0 3076 8 ?SJul23 0:00 \_ /usr/sbin/cron root 2153 0.0 0.0 2456 8 ?Ss Jul23 0:00 \_ bash root 2807 0.0 0.0 1712 904 ?SJul23 0:00 \_ egrep --text -v -f /tmp/filerO64S4 root 2806 0.0 0.0 1640 8 ?SJul23 0:00 \_ timeout 3600 /usr/sbin/puppetd -o --no-daemonize root 2808 0.6 2.0 67244 63808 ?SJul23 77:25 \_ /usr/bin/ruby1.8 /usr/sbin/puppetd -o --no-daemonize root 2983 0.0 0.0 74372 8 ?Ss Jul23 0:00 \_ /usr/bin/ruby1.8 /usr/sbin/puppetd -o --no-daemonize sgran39721 0.0 0.0 4936 1316 ?S+ 21:11 0:00 \_ grep Jul23 sgran@finzi:~$ date Sat Jul 30 21:11:51 UTC 2011 gran@finzi:~$ (and yes, it is a separate issue that ruby doesn't know how to exit). Cheers, -- System Information: Debian Release: 6.0.2 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: kfreebsd-i386 (i686) Kernel: kFreeBSD 8.1-1-686-smp Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.utf8) Shell: /bin/sh linked to /bin/dash Versions of packages coreutils depends on: ii libc0.1 2.11.2-10+b1 Embedded GNU C Library: Shared lib coreutils recommends no packages. coreutils suggests no packages. -- no debconf information -- - | ,''`. Stephen Gran | | : :' :sg...@debian.org | | `. `'Debian user, admin, and developer | |`- http://www.debian.org | - -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#636037: hdparm does not use reasonable default settings for apm
reassign 636037 pm-utils thanks This one time, at band camp, Ralf Jung said: > Hi, > > > Can you let me > > know which power management stack you're using so this can be reassigned > > to the right people? > I am using whatever is the default in current Debian testing - I assume it is > pm-utils, at least I just managed to configure different hdparm settings for > AC/battery mode by adding a custom script to /etc/pm/power.d. Cool, thanks for that - I'll reassign over now. > > hparm does not install any apm settings by default. > That's exactly the problem here - something should be set somewhere by > default. Sorry if hdparm is not the right place to put this. No problem. I think it's better in the power management stack, as hdparm itself can't know what the user wants on it's own. Cheers, -- ----- | ,''`.Stephen Gran | | : :' :sg...@debian.org | | `. `'Debian user, admin, and developer | |`- http://www.debian.org | - signature.asc Description: Digital signature
Bug#636037: hdparm does not use reasonable default settings for apm
This one time, at band camp, Ralf Jung said: > After installing Debian, I noticed that my HDD would spin up and down much > more > often than before (I used Kubuntu 10.10 previously). The Load_Cycle_Count as > reported my smartctl started to skyrocket, i.e. go up by 30 to 80 per hour. > Some research showed that Ubuntu has had the same issue [1] and they changed > hdparm to set apm (the -B option) to a reasonable value of above 200 when the > PC is not in battery mode and introduce an "apm_battery" option in > /etc/hdparm.conf. Something like this should be done here, too (which also > required to properly integrate hdparm into power management - currently it > seems to support apmd only which is not even enabled for Debian's kernels) - > or > maybe there are better solutions. > The current settings have a negative effect on disc life-time, so it is IMHO > quite important to deal with the problem. Sorry if the priority setting is > inappropriate. Hello, hparm does not install any apm settings by default. Can you let me know which power management stack you're using so this can be reassigned to the right people? Cheers, -- --------- | ,''`.Stephen Gran | | : :' :sg...@debian.org | | `. `'Debian user, admin, and developer | |`- http://www.debian.org | - signature.asc Description: Digital signature
Bug#634475: [Adduser-devel] adduser --system in maintainer scripts (re: Bug #634475)
This one time, at band camp, Simon McVittie said: > On Mon, 30 May 2011 at 09:12:59 +0100, Stephen Gran wrote: > > This one time, at band camp, Roger Leigh said: > > > [...] However, most > > > postinsts wrap the call to adduser with a check for whether the > > > account already exists [...] > > > > I know that people do that, but it is unnecessary scaffolding. adduser > > already handles that just fine. Maybe the documentation is lacking, but > > the design goal is that you can just call adduser --system --quiet $args > > in your postinst, and adduser will do what you meant: > > > > steve@varinia:~$ getent passwd postfix > > postfix:x:112:120::/var/spool/postfix:/bin/false > > steve@varinia:~$ sudo adduser --system --quiet postfix > > [sudo] password for steve: > > steve@varinia:~$ echo $? > > 0 > > We use adduser --system --quiet in the dbus package without checking for > existence of the user first, as recommended here. However, bug #634475 > reveals that if the messagebus user is present, but is not in the system UID > range, this will make the upgrade fail. Correct, and this is arguably correct behavior. I don't think we want to guess about what to do in this case. The options available are: renumber the account (and optionally find all files on the file system owned by this user and chown them to the new uid or delete them) don't renumber the account, which is in violation of debian and/or local policy. Neither is acceptable, frankly. I think it's best to fail in such a way that it forces the admin to deal with it. > Peter Chubb (reporter of #634475) wrote: > > Simon> If you have enough backups of /etc/passwd to be able to answer > > Simon> these questions: what were the messagebus user's home > > Simon> directory, numeric UID, and primary group ID before the > > Simon> upgrade? What was the messagebus group's numeric GID? Did you > > Simon> have any other users or groups whose numeric UID/GID collided > > Simon> with messagebus? > > > > In the backup from two days ago: > > > > : wombat ; grep messagebus passwd group > > passwd:messagebus:x:110:107::/var/run/dbus:/bin/false > > group:messagebus:x:107: > > wombat ; grep 110 passwd > > messagebus:x:110:107::/var/run/dbus:/bin/false > > : wombat ; grep 107 group > > messagebus:x:107: > > > > I think the issue I have is that because of legacy accounts, > > LAST_SYSTEM_UID is 99 in /etc/adduser.conf, and for some reason the > > account was already existing with a higher UID than that. > > Presumably, on Peter's system, messagebus was either created while > LAST_SYSTEM_UID was higher, or possibly before 2003 when dbus created > messagebus as a non-system group (#222563 - which was undeniably itself a bug, > but we should do what we can to recover from historical bugs). > > In the opinions of the adduser maintainers, what should daemon-user-creating > packages like dbus be doing about this? I think for this specific one, a change in local policy made the account no longer correct, so again, I think adduser is behaving correctly here. We have a whole class of bugs that want effectively an "ensure user is in correct range" flag. If this didn't involve file ownership, this would be relatively straight forward, as we could just delete and recreate them with the correct uid/gid. Unfortunately, almost no package that installs a user has no files owned by that user, so it gets a little more complicated. Cheers, -- - | ,''`.Stephen Gran | | : :' :sg...@debian.org | | `. `'Debian user, admin, and developer | |`- http://www.debian.org | - signature.asc Description: Digital signature
Bug#630750: [Adduser-devel] Bug#630750: default NAME_REGEX value in /etc/adduser.conf is incorrect
tags -patch thanks Hi, This one time, at band camp, Georgios M. Zarkadas said: > The default value of variable NAME_REGEX shipped within the package's file > /usr/share/adduser/adduser.conf (which is copied upon installation to > etc/adduser.conf) is incorrect. > > current value / should-be value (the patch - append "?$" to it): > > - --- adduser.conf2011-06-17 00:51:05.718593580 +0300 > +++ adduser.conf 2011-06-17 00:51:32.282093072 +0300 > @@ -82,4 +82,4 @@ > > > # check user and group names also against this regular expression. > - -#NAME_REGEX="^[a-z][-a-z0-9_]*\$" > +#NAME_REGEX="^[a-z][-a-z0-9_]*\$?$" This can't be fixing it, the default is commented out. > The problem realised when tried to install hal (which installs user haldaemon) > with the regex enabled and it failed to install with the following message: > > - --- > Γίνεται εγκατάσταση hal (0.5.14-3) ... > adduser: Please enter a username matching the regular expression configured > via the NAME_REGEX configuration variable. Use the `--force-badname' > option to relax this check or reconfigure NAME_REGEX. > dpkg: σφάλμα στην επεξεργασία του hal (--configure): > η υποδιεργασία installed post-installation script επέστρεψε κατάσταση λάθους > 1 > - --- > > After checking the postinst script of hal package I didn't found anything > suspicious in its adduser invocation, nor on the tried out username > (haldaemon) > so I started to study the adduser source code. > > Seeing the 'checkname' routine and the initial test expression, I finally came > up with the patch which was tried and hal installation succeeded. I wonder if this is a locale specific problem. Can you try (in a chroot, whatever), installing haldaemon with a default config for adduser to try to reproduce it? I am curious if it will succeed if you then set LANG=C and install it again. I suspect it will install. If this is the case, can you let me know? Cheers, -- - | ,''`.Stephen Gran | | : :' :sg...@debian.org | | `. `'Debian user, admin, and developer | |`- http://www.debian.org | - signature.asc Description: Digital signature
Bug#613009: On upgrade preconf: /tmp/adduser.config.PID: line 2[36]: [: too many arguments
This one time, at band camp, Lionel Elie Mamane said: Hi, > On Sun, Jun 12, 2011 at 06:00:55PM +0100, Stephen Gran wrote: > > This one time, at band camp, Lionel Elie Mamane said: > > >> When upgrading from 3.110: > > >> Preconfiguring packages ... > >> /tmp/adduser.config.50053: line 23: [: too many arguments > >> /tmp/adduser.config.50053: line 23: [: too many arguments > >> /tmp/adduser.config.50053: line 26: [: too many arguments > >> /tmp/adduser.config.50053: line 26: [: too many arguments > > > Please provide the output of this command: > > cat /etc/adduser.conf | sed -ne 's/^DIR_MODE=\(.*\)$/\1/p;' > > $ cat /etc/adduser.conf | sed -ne 's/^DIR_MODE=\(.*\)$/\1/p;' > 0755 > 0755 So, what tripped the bug is that you have the same directive twice. I've made the test more robust, which will stop the config script from complaining like this in the future, but I would suggest commenting out one of those two on your local system. Cheers, -- ----- | ,''`.Stephen Gran | | : :' :sg...@debian.org | | `. `'Debian user, admin, and developer | |`- http://www.debian.org | - signature.asc Description: Digital signature
Bug#613009: On upgrade preconf: /tmp/adduser.config.PID: line 2[36]: [: too many arguments
This one time, at band camp, Lionel Elie Mamane said: > When upgrading from 3.110: > > Preconfiguring packages ... > /tmp/adduser.config.50053: line 23: [: too many arguments > /tmp/adduser.config.50053: line 23: [: too many arguments > /tmp/adduser.config.50053: line 26: [: too many arguments > /tmp/adduser.config.50053: line 26: [: too many arguments Please provide the output of this command: cat /etc/adduser.conf | sed -ne 's/^DIR_MODE=\(.*\)$/\1/p;' Cheers, -- - | ,''`. Stephen Gran | | : :' :sg...@debian.org | | `. `'Debian user, admin, and developer | |`- http://www.debian.org | - signature.asc Description: Digital signature
Bug#545426: a menu.lst that didn't work
Hi, Attached. Cheers, -- - | ,''`. Stephen Gran | | : :' :sg...@debian.org | | `. `'Debian user, admin, and developer | |`- http://www.debian.org | - # menu.lst - See: grub(8), info grub, update-grub(8) #grub-install(8), grub-floppy(8), #grub-md5-crypt, /usr/share/doc/grub #and /usr/share/doc/grub-legacy-doc/. serial --unit=1 --speed=115200 --word=8 --parity=no --stop=1 terminal --timeout=10 serial console timeout 10 ## default num # Set the default entry to the entry number NUM. Numbering starts from 0, and # the entry number 0 is the default if the command is not used. # # You can specify 'saved' instead of a number. In this case, the default entry # is the entry saved with the command 'savedefault'. # WARNING: If you are using dmraid do not change this entry to 'saved' or your # array will desync and will not let you boot your system. default 0saved ## timeout sec # Set a timeout, in SEC seconds, before automatically booting the default entry # (normally the first entry defined). timeout 5 # Pretty colours color cyan/blue white/blue ## password ['--md5'] passwd # If used in the first section of a menu file, disable all interactive editing # control (menu entry editor and command-line) and entries protected by the # command 'lock' # e.g. password topsecret # password --md5 $1$gLhU0/$aW78kHK1QfV3P2b2znUoe/ # password topsecret # # examples # # title Windows 95/98/NT/2000 # root (hd0,0) # makeactive # chainloader +1 # # title Linux # root (hd0,1) # kernel/vmlinuz root=/dev/hda2 ro # # # Put static boot stanzas before and/or after AUTOMAGIC KERNEL LIST ### BEGIN AUTOMAGIC KERNELS LIST ## lines between the AUTOMAGIC KERNELS LIST markers will be modified ## by the debian update-grub script except for the default options below ## DO NOT UNCOMMENT THEM, Just edit them to your needs ## ## Start Default Options ## ## default kernel options ## default kernel options for automagic boot options ## If you want special options for specific kernels use kopt_x_y_z ## where x.y.z is kernel version. Minor versions can be omitted. ## e.g. kopt=root=/dev/hda1 ro ## kopt_2_6_8=root=/dev/hdc1 ro ## kopt_2_6_8_2_686=root=/dev/hdc2 ro # kopt=root=UUID=cb718b09-90cd-4818-bfd1-c52e4a8a4070 ro ## default grub root device ## e.g. groot=(hd0,0) # groot=(hd0,0) ## should update-grub create alternative automagic boot options ## e.g. alternative=true ## alternative=false # alternative=true ## should update-grub lock alternative automagic boot options ## e.g. lockalternative=true ## lockalternative=false # lockalternative=false ## additional options to use with the default boot option, but not with the ## alternatives ## e.g. defoptions=vga=791 resume=/dev/hda5 # defoptions=console=tty0 console=ttyS1,115200n8 ## should update-grub lock old automagic boot options ## e.g. lockold=false ## lockold=true # lockold=false ## Xen hypervisor options to use with the default Xen boot option # xenhopt= ## Xen Linux kernel options to use with the default Xen boot option # xenkopt=console=tty0 ## altoption boot targets option ## multiple altoptions lines are allowed ## e.g. altoptions=(extra menu suffix) extra boot options ## altoptions=(single-user) single # altoptions=(serial console, single-user mode) console=tty0 console=ttyS1,115200n8 single # altoptions=(no serial console) 2 # altoptions=(no serial console; recovery) single ## controls how many kernels should be put into the menu.lst ## only counts the first occurence of a kernel, not the ## alternative kernel options ## e.g. howmany=all ## howmany=7 # howmany=all ## should update-grub create memtest86 boot option ## e.g. memtest86=true ## memtest86=false # memtest86=true ## should update-grub adjust the value of the default booted system ## can be true or false # updatedefaultentry=false ## should update-grub add savedefault to the default options ## can be true or false # savedefault=false ## ## End Default Options ## title Chainload into GRUB 2 root(hd0,0) kernel /boot/grub/core.img title � root title When you have verified GRUB 2 works, you can use this command to root title complete the upgrade: upgrade-from-grub-legacy root title � root title Debian GNU/Linux, kernel 2.6.32-5-686 root(hd0,0) kernel /boot/vmlinuz-2.6.32
Bug#621206: [Pkg-clamav-devel] Bug#621206: clamav: diff for NMU version 0.97+dfsg-2.1
This one time, at band camp, Luk Claes said: > tags 621206 + patch > thanks > > Dear maintainer, > > I've prepared an NMU for clamav (versioned as 0.97+dfsg-2.1) and > will *not* upload it unless you tell me otherwise. Hi Luk, That seems sane enough. Just out of curiousity, has it been tested? I ask because clamav does use libltdl directly (to load the non-free rar support) and I'd hate to break this, which is why I've been sitting on my hands a bit. Cheers, -- - | ,''`. Stephen Gran | | : :' :sg...@debian.org | | `. `'Debian user, admin, and developer | |`- http://www.debian.org | - signature.asc Description: Digital signature
Bug#623995: occasional hangs, resulting in no new entropy for host
Package: ekeyd-egd-linux Severity: normal Hi, Just a follow up to say I've now seen this several times. Unfortunately the strace isn't any better on any of the more recent hangs. Please let me know if you'd like me to do anything to help debug this. Cheers, -- System Information: Debian Release: 6.0.1 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.utf8) Shell: /bin/sh linked to /bin/dash -- - | ,''`. Stephen Gran | | : :' :sg...@debian.org | | `. `'Debian user, admin, and developer | |`- http://www.debian.org | - signature.asc Description: Digital signature
Bug#626547: [Pkg-clamav-devel] Bug#626547: incorrect /var/run/clamav/freshclam.pid owner set if clamav installed on system with HAL
This one time, at band camp, juan.r.d.silva said: > Package: clamav > Version: 0.97+dfsg-2~squeeze1 > Severity: important > > If you install Clamav after HAL was installed on system, a file > /var/run/clamav/ > freshclam.pid is created with root:haldaemon group:owner permissions and > the following error is generated after installation: "ERROR: Can't save > PID to file /var/run/clamav/freshclam.pid: Permission denied" > > But if you install Clamav on a fresh squeeze without HAL installed, the > ownership of the same file is root:clamav instead, and Clamav does > produce this error. Hi, I don't see how this is possible. Can you please send the output of id clamav id haldaemon Cheers, -- - | ,''`.Stephen Gran | | : :' :sg...@debian.org | | `. `'Debian user, admin, and developer | |`- http://www.debian.org | - signature.asc Description: Digital signature
Bug#624380: [Pkg-clamav-devel] Bug#624380: Bug#624380: clamav-base: Please package huge example files seperately or move them to clamav-docs
This one time, at band camp, Axel Beckert said: > Hi Stephen, > > Stephen Gran wrote: > > > With the exception of the example configuration file, those files are > > > probably not needed by the vast majority of the clamav users, yet all of > > > them have to waste those 26 MB of disk space and download time when > > > installing e.g. freshclam which has a hard dependency. > > > > We've been around this before, unfortunately. The problem is that we > > can't require a network connection for users installing the software, > > and without these files, the dependencies can end up installing > > non-functional software. I'm afraid I don't see any way out of this > > one. > > Hmm, I then see the following three problems (or just don't understand > the reasoning for it): Reading the postinst for clamav-base is a good place to start if you're not sure what is going on. > A) Why are files necessary to get a working software installed in >/usr/share/_doc_/$package/_examples_? IMHO that's a totally >inappropriate location for them. They are copied into place for use if they are not there. This is a compromise with clamav-data, as the maintainer of that package wanted to ship them in place and didn't want a file clash. This also ensures that we don't overwrite a potentially newer downloaded version of the signatures with what we ship in the package, eg, on a security upgrade. > B) What is the package clamav-data then for? It has btw. also a size >of 26 MB. Coincidence? This is one of two possible dependencies for clamav. The other is freshclam, which needs to provide the files by the time it's postinst finishes. If a user chooses to run freshclam as a daemon (the default answer), the download is not guaranteed to finish by the time freshclam's postinst exits. > C) clamav doesn't depend on clamav-base, it just recommends it. Just >clamav-freshclam does depend on it, which, according to your >arguments, does not need those files as the sole purpose of package >is to fetch signature updates via the internet. clamav will install, but not do very much, in the absence of signatures. clamav-daemon and clamav-milter will not start in the absence of signatures. This is what is being addressed with this arrangement. Yes, we could ship the signatures with clamav-freshclam, but this means 26MB* in the archive instead of just 26MB. The current arrangement is a compromise, and possibly not the best one. If you have a suggestion that satisfies the following, I'd be happy to work with you on it: a) an installation of clamav-daemon or clamav-milter will always result in signatures being in place for use by the time their postinst runs. This means that the relationship to a package containing signatures is expressed in Dependencies in the packaging system. b) installation of signatures must be satisfiable in the archive. Network download of the signatures after install cannot be assumed. c) Putting the signatures into an arch any package instead of an arch all package is probably a no-go, as it's an extra 260MB in the archive for no real gain. Cheers, -- - | ,''`.Stephen Gran | | : :' :sg...@debian.org | | `. `'Debian user, admin, and developer | |`- http://www.debian.org | - -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#624380: [Pkg-clamav-devel] Bug#624380: clamav-base: Please package huge example files seperately or move them to clamav-docs
This one time, at band camp, Axel Beckert said: > With the exception of the example configuration file, those files are > probably not needed by the vast majority of the clamav users, yet all of > them have to waste those 26 MB of disk space and download time when > installing e.g. freshclam which has a hard dependency. Hi, We've been around this before, unfortunately. The problem is that we can't require a network connection for users installing the software, and without these files, the dependencies can end up installing non-functional software. I'm afraid I don't see any way out of this one. Cheers, -- - | ,''`. Stephen Gran | | : :' :sg...@debian.org | | `. `'Debian user, admin, and developer | |`- http://www.debian.org | - signature.asc Description: Digital signature
Bug#549692: Bug still present?
This one time, at band camp, David Paleino said: > Hello, > could you please confirm whether this bug is still reproducible with the > current version in sid? (1.3-1) Hi, Sorry to not follow up sooner - thanks for the prod. I can no longer reproduce it with ii bash-completion 1:1.2-3 programmable completion for the bash shell Cheers, -- - | ,''`. Stephen Gran | | : :' :sg...@debian.org | | `. `'Debian user, admin, and developer | |`- http://www.debian.org | - signature.asc Description: Digital signature
Bug#623995: ekeyd-egd-linux: occasional hangs, resulting in no new entropy for host
Package: ekeyd-egd-linux Version: 1.1.3-3 Severity: normal Hello, We're using a setup with 4 entropy keys, and several dozens of hosts. The communication between the hosts that have entropy keys and the others is done over an stunnel connection over the public internet. Occasionally, it seems there is a hiccough or something in the communication, and we consistently see the client ekeyd-egd-linux process hang in: restart_syscall(<... resuming interrupted call ...> I realize that's not all that helpful, but that's all strace will give me. If there's anything I can do to help track it down, let me know. Cheers, -- System Information: Debian Release: 6.0.1 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.utf8) Shell: /bin/sh linked to /bin/dash -- - | ,''`. Stephen Gran | | : :' :sg...@debian.org | | `. `'Debian user, admin, and developer | |`- http://www.debian.org | - signature.asc Description: Digital signature
Bug#620222: security.debian.org: One server unreachable in IPv6
This one time, at band camp, Raphael Geissert said: > Hi, > > On 31 March 2011 01:45, Bernhard Schmidt wrote: > > Package: security.debian.org > > Severity: minor > > > > One IPv6 server in the current security.ipv6.debian.org (and > > security.debian.org) rotation has been not responding in IPv6 for > > some days now. This introduces timeouts of a few minutes every time > > you want to update the package list. > > Thanks for the report. This bit of the infrastructure is handled by > the DSA team, who I'm CC'ing. Quoting the complete message for their > benefit. > > > > security.debian.org has IPv6 address 2001:8d8:2:1:6564:a62:0:2 > > security.debian.org has IPv6 address 2001:a78:5:0:216:35ff:fe7f:be4f > > security.debian.org has IPv6 address 2001:a78:5:1:216:35ff:fe7f:6ceb > > > > mail.svr01.mucip.net:~# ping6 2001:a78:5:0:216:35ff:fe7f:be4f > > PING 2001:a78:5:0:216:35ff:fe7f:be4f(2001:a78:5:0:216:35ff:fe7f:be4f) 56 > > data bytes > > ^C > > --- 2001:a78:5:0:216:35ff:fe7f:be4f ping statistics --- > > 17 packets transmitted, 0 received, 100% packet loss, time 16127ms Thanks for the report. It seems that this machine has lost it's ability to route packets over v6. I've failed the v6 address out of the rotation, so you should see better results fairly quickly. I'll investigate what's going wrong. Cheers, -- - | ,''`.Stephen Gran | | : :' :sg...@debian.org | | `. `'Debian user, admin, and developer | |`- http://www.debian.org | - signature.asc Description: Digital signature
Bug#611019: [Nsspampgsql-devel] Bug#611019: libnss-pgsql2: Does not correctly handle empty string in query result
severity 611019 wishlist thanks This one time, at band camp, Thomas Damgaard said: > This has worked fine while running lenny. > After upgrading to squeeze, I started getting the error. > Having spent hours debugging this, it turned out that > 'getent shadow backup001' returns: > backup001:*:14551:0:9:7:0:0:0 > and not the expected > backup001:*:14551:0:9:7::: > > So, it returns 0 instead of empty string. > I had to turn on query logging in the database. > I noticed that the query did in fact select ''. > I tried modifying the query to return 9 instead of '' and then > 'getent shadow backup001' returns: > backup001:*:14551:0:9:7:0:0:9 > And best of all: now login works! > > So I guess the problem is that libnss-pgsql handles the empty string > incorrectly and returns 0 to PAM instead of ''. This has probably also > been the case in lenny, however, some semantics in PAM must have > changed in squeeze so that it now interprets 0 as 'account expired'. > Which is probably correct. > > I think this is a very severy bug, since this will make login fail > for users who upgrade to squeeze. > I hope this will be fixed before squeeze is released. Hello, I'm afraid this is a design decision, rather than a bug. The code explicitly casts the return to a numeric value: result->sp_lstchg = (long int) atol(PQgetvalue(res, 0, SHADOW_LSTCHG)); result->sp_min = (long int) atol(PQgetvalue(res, 0, SHADOW_MIN)); result->sp_max = (long int) atol(PQgetvalue(res, 0, SHADOW_MAX)); result->sp_warn = (long int) atol(PQgetvalue(res, 0, SHADOW_WARN)); result->sp_inact = (long int) atol(PQgetvalue(res, 0, SHADOW_INACT)); result->sp_expire = (long int) atol(PQgetvalue(res, 0, SHADOW_EXPIRE)); result->sp_flag = (unsigned long int) atol(PQgetvalue(res, 0, SHADOW_FLAG)); I suspect you're right that something changed in pam to make it suddenly stop working for you, but it never should have worked with that configuration. The example config doesn't contain a query with '' in it, but I suppose it could be clearer, hence I've marked this wishlist with the idea that we'll update the example config to make it clearer what the library expects. Cheers, -- - | ,''`.Stephen Gran | | : :' :sg...@debian.org | | `. `'Debian user, admin, and developer | |`- http://www.debian.org | - signature.asc Description: Digital signature
Bug#610937: [Pkg-clamav-devel] Bug#610937: clamav: clam segfault
This one time, at band camp, Salvatore Tomaselli said: > [ 40.848975] clamd[3091]: segfault at 1 ip b74e7df7 sp bfb79928 error 4 in > libc-2.7.so[b7472000+155000] This is unfortunately not enough to go on to figure out what's going wrong. I'd like to see you update to the version in volatile, so that you are running a more recent version of clamav, and if you still are experiencing this issue, I'd like to help you get us more information. Are you able to do both of those things? Cheers, -- - | ,''`. Stephen Gran | | : :' :sg...@debian.org | | `. `'Debian user, admin, and developer | |`- http://www.debian.org | - signature.asc Description: Digital signature
Bug#609683: [Pkg-clamav-devel] Bug#609683: clamscan useless with amavis
This one time, at band camp, Grzegorz Bizon said: > Default amavis invokes clamscan with --disable-summary deprecated > option, and clamscan 0.96.5 version requires --no-summary option. > > --disable-summary shouldn't be ignored as to provide backward > compatibility for amavisd-new package in stable. Hi, It's been some time since I looked at amavis, but isn't that configurable? Cheers, -- - | ,''`. Stephen Gran | | : :' :sg...@debian.org | | `. `'Debian user, admin, and developer | |`- http://www.debian.org | - signature.asc Description: Digital signature
Bug#605122: [Pkg-clamav-devel] Bug#605122: excessive logging of "Network is unreachable" fills up /var[/log/clamav/freshclam.log]
This one time, at band camp, Enrico Zini said: > although I purged freshclam (and clamav) from my system, a > "/usr/bin/freshclam -d --quiet" process was left running, which kept the > huge freshclam.log open, which left its disk space in /var/ allocated > although I had deleted the file manually. > > freshclam being purged meant that the stop script in /etc/init.d was not > there anymore to be used to shut freshclam down; killing the freshclam > process manually obviously put an end to all the sufferings and freed > that 1.2Gb I needed in my /var. > > I personally have no problems dealing with a scenario of "disk space is > not freed while the file is still open" coupled with "purging freshclam > leaves the daemon running" and "freshclam keeps its logfile open all the > time", but I can see how it all can cause a rather bad friday afternoon > to many, especiall because at that point "du" and friends will not show > you where the disk space is used anymore :( du and df disagreeing is almost always a sign of an open but deleted file. lsof is your friend in these cases. It sounds like the main bug is that the init script failed to kill freshclam here. Can you provide any more info or help us to reproduce it? I know that freshclam blocks some of the useful shutdown signals while it's in the chunk of code concerned with downloads (which, without a network, will be more time than normal), but the initscript does try very hard to make sure it's killed off even so. Cheers, -- --------- | ,''`.Stephen Gran | | : :' :sg...@debian.org | | `. `'Debian user, admin, and developer | |`- http://www.debian.org | - signature.asc Description: Digital signature
Bug#607053: [Pkg-clamav-devel] Bug#607053: clamav-freshclam.ucf-dist created in cron.d directory
This one time, at band camp, Simon Day said: > The file /etc/cron.d/clamav-freshclam.ucf-dist is created during > install when you choose not to keep the maintainers version. > > While this is the desired behaviour for most config files, this is not > desired in cron.d as it results in both your version and the > maintainers version being executed > > This may be indicative of a wider problem with the packager/installer > with any .d style config directory. I've checked in an rm -f for that file. Cheers, -- - | ,''`. Stephen Gran | | : :' :sg...@debian.org | | `. `'Debian user, admin, and developer | |`- http://www.debian.org | - signature.asc Description: Digital signature
Bug#604242: [Adduser-devel] Bug#604242: [patch] Allow dots in username by default
This one time, at band camp, Milan Bouchet-Valat said:
> I don't think there's a reason not to allow usernames to contain dots
> (.), as they are also allowed to contain underscores (_) and dashes (-).
> useradd accepts this.
>
> Attached is a patch that makes dots be allowed just as other special
> chars. One could also add the point in this line in /etc/adduser.conf:
> #NAME_REGEX="^[a-z][-a-z0-9_]*\$"
> but providing a patch for that makes the change harder to perform! ;-)
>
>
> This fix would be appreciated for the gnome-system-tools, because
> currently users-admin says dots are accepted, and this is false on
> Debian. Saying dots are not allowed would be an issue because other
> platforms allow for them, which means Debian should carry a specific
> patch...
- $configref->{"name_regex"} = "^[a-z][-a-z0-9_]*\$";
- $configref->{"name_regex_system"} = "^[A-Za-z][-A-Za-z0-9_]*\$";
+ $configref->{"name_regex"} = "^[a-z][-a-z0-9_.]*\$";
+ $configref->{"name_regex_system"} = "^[A-Za-z][-A-Za-z0-9_.]*\$";
That's a regex, so a bare . is almost certainly not what you want there.
Why does users-admin use adduser instead of useradd? It's not that
it shouldn't, but adduser is primarily designed as a policy compliant
method for maintainers to interface in a policy compliant way with user
management in maintainer scripts - extending it to be a general purpose
user management script for all manner of environments isn't what it's
aimed at, and I'm not convinced it will be a good thing to make it
general purpose. I think before changing the naming policy of adduser,
it does make sense to stop for a moment and check if you're using the
right tool for the job.
Cheers,
--
-
| ,''`.Stephen Gran |
| : :' :sg...@debian.org |
| `. `'Debian user, admin, and developer |
|`- http://www.debian.org |
-
signature.asc
Description: Digital signature
Bug#598862: hdparm: Nasty messages from the kernel on boot
This one time, at band camp, Cesare Leonardi said: > As i reported upstream, today this problem happened with a kernel > different from the Squeeze one: 2.6.36-rc6. Hi, Did this setting you're using ever work without provoking errors from the drive? Cheers, -- - | ,''`. Stephen Gran | | : :' :sg...@debian.org | | `. `'Debian user, admin, and developer | |`- http://www.debian.org | - signature.asc Description: Digital signature
Bug#600908: [Pkg-clamav-devel] Bug#600908: Improvement to clamav-milter init script
This one time, at band camp, Chris Moules said: > We have recently experienced the case that clamav-milter was 'running' > but the socket file was missing. This caused our mail system (postfix) > to reject mail with a temporary error. > > Monitoring the service by checking the return code from > '/etc/init.d/clamav-milter status' did not catch this situation. > > I have updated the 'status' check to include a check for the sockets > existence and an alternate error code (LSB correct, I believe). See > attached patch. > > The patch also fixes the call to 'status_of_proc' with the variable > $BASENAME in place of $NAME (which does not exist). It also moves the > 'local' copy of the function 'status_of_proc' below the sourcing of > '/lib/lsb/init-functions' so that this version of the function gets > called. Before, this local copy of the function was just unused code > in the init script. This local copy of the LSB function now checks the > existence of the clamav-milter socket as defined in '$SOCKET_PATH'. Hi, Thanks for the patch. The status_of_proc function definition is only there for backports to older systems where the lsb_base stuff doesn't define it. It's designed to be overridden when possible. I'd like to leave it that way as much as possible, so we may rework your patch somewhat, but the idea is a good one. Cheers, -- - | ,''`.Stephen Gran | | : :' :sg...@debian.org | | `. `'Debian user, admin, and developer | |`- http://www.debian.org | - signature.asc Description: Digital signature
Bug#600917: python2.6: python gets "Segmentation fault" when executing a script and HOME is on a nfs volume:
This one time, at band camp, Richard Limanowski said: > rl...@prod[ntt] 508 $ python p.py test.odt out.pdf > python: malloc.c:5145: malloc_consolidate: Assertion > `p->fd_nextsize->bk_nextsize == p' failed. > Aborted > > rl...@prod[ntt] 509 $ python p.py test.odt out.pdf > Segmentation fault > > rl...@prod[ntt] 510 $ HOME=$(pwd)/HOME python p.py test.odt out.pdf Can you reproduce this issue when you're not using the python-uno module? If not, I'd be inclined to reassign this to python-uno. Cheers, -- - | ,''`.Stephen Gran | | : :' :sg...@debian.org | | `. `'Debian user, admin, and developer | |`- http://www.debian.org | - signature.asc Description: Digital signature
Bug#574897: this is not wishlist anymore...
This one time, at band camp, Henrique de Moraes Holschuh said: > retitle 574897 hdparm: version 9.32 required to fix nasty issues in 9.27+ > severity 574897 important > thanks > > hdparm-9.32: major bug fixes > > hdparm-9.32 is now released. This includes fixes for the bugs introduced in > 9.27 (which nobody emailed me about). So now, many flags such as -B and -M > should be working again for most people. > > IMO, this is quite serious enough to warrant an update of the version that > should ship with squeeze. A broken hdparm -B will have VERY detrimental > effects for owners of many laptops. > > If you need an NMU, just say so. I will have some time tomorrow and again mid week. If there is no upload by Friday, please proceed with an NMU. Thanks for the heads up, and cheers, -- - | ,''`. Stephen Gran | | : :' :sg...@debian.org | | `. `'Debian user, admin, and developer | |`- http://www.debian.org | - signature.asc Description: Digital signature
Bug#596291: offlineimap getting stuck when run with multiple threads/connections
This one time, at band camp, Stephen Gran said: > I have so far been unable to reproduce this when running offlineimap > under strace, which suggests a timing dependant bug (kind of as > suspected, but still not all that helpful, I realize). The earlier > strace (and the strace I see when attaching after it hangs) does suggest > that a lock is not being releaesed somewhere, but I can't immediately > see anything obviously wrong with the logic in the code. Trying to run with -d thread under python2.6 gets me a recursion exceeded exception, but I did manage to capture a lockup under 2.5: Folder sync Lobefin[packaging.clamav]: .acquire: success, value=0 Folder sync Lobefin[packaging.clamav]: .start(): starting thread Copy message 2200 from packaging.clamav: .__bootstrap(): thread started Copy message 2200 from packaging.clamav: Copy message 2200 IMAP[packaging.clamav] -> Maildir[packaging.clamav], LocalStatus[packaging.clamav] Copy message 2200 from packaging.clamav: .acquire: success, value=0 Folder sync Lobefin[packaging.clamav]: .acquire(1): blocked waiting, value=0 Copy message 2200 from packaging.clamav: .release: success, value=1 Copy message 2200 from packaging.clamav: , 1)>.notify(): notifying 1 waiter Folder sync Lobefin[packaging.clamav]: , 0)>.wait(): got it Folder sync Lobefin[packaging.clamav]: .acquire: success, value=0 Folder sync Lobefin[packaging.clamav]: .release: success, value=1 Folder sync Lobefin[packaging.clamav]: , 0)>.notify(): no waiters Folder sync Lobefin[packaging.clamav]: .acquire(1): blocked waiting, value=0 Copy message 2200 from packaging.clamav: .release: success, value=1 Copy message 2200 from packaging.clamav: , 1)>.notify(): notifying 1 waiter Copy message 2200 from packaging.clamav: .__bootstrap(): normal return Folder sync Lobefin[packaging.clamav]: , 0)>.wait(): got it Copy message 2200 from packaging.clamav: , 0)>.notify(): no waiters Folder sync Lobefin[packaging.clamav]: .acquire: success, value=0 Folder sync Lobefin[packaging.clamav]: .start(): starting thread Copy message 2201 from packaging.clamav: .__bootstrap(): thread started Copy message 2201 from packaging.clamav: Copy message 2201 IMAP[packaging.clamav] -> Maildir[packaging.clamav], LocalStatus[packaging.clamav] Copy message 2201 from packaging.clamav: .acquire: success, value=0 Folder sync Lobefin[packaging.clamav]: .acquire(1): blocked waiting, value=0 Copy message 2201 from packaging.clamav: .release: success, value=1 Copy message 2201 from packaging.clamav: , 1)>.notify(): notifying 1 waiter Folder sync Lobefin[packaging.clamav]: , 0)>.wait(): got it Folder sync Lobefin[packaging.clamav]: .acquire: success, value=0 Folder sync Lobefin[packaging.clamav]: .release: success, value=1 Folder sync Lobefin[packaging.clamav]: , 0)>.notify(): no waiters Folder sync Lobefin[packaging.clamav]: .acquire(1): blocked waiting, value=0 Copy message 2201 from packaging.clamav: .release: success, value=1 Copy message 2201 from packaging.clamav: , 1)>.notify(): notifying 1 waiter Copy message 2201 from packaging.clamav: .__bootstrap(): normal return Folder sync Lobefin[packaging.clamav]: , 0)>.wait(): got it Copy message 2201 from packaging.clamav: , 0)>.notify(): no waiters Folder sync Lobefin[packaging.clamav]: .acquire: success, value=0 Folder sync Lobefin[packaging.clamav]: .start(): starting thread Copy message 2202 from packaging.clamav: .__bootstrap(): thread started Copy message 2202 from packaging.clamav: Copy message 2202 IMAP[packaging.clamav] -> Maildir[packaging.clamav], LocalStatus[packaging.clamav] Copy message 2202 from packaging.clamav: .acquire: success, value=0 Folder sync Lobefin[packaging.clamav]: .acquire(1): blocked waiting, value=0 And there it hangs. -- --------- | ,''`.Stephen Gran | | : :' :sg...@debian.org | | `. `'Debian user, admin, and developer | |`- http://www.debian.org | - -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#596291: offlineimap getting stuck when run with multiple threads/connections
Hi, A couple of final notes. I get this hang even when running with -1, and I only get this hang when on the same LAN as the IMAP server. When fetching remotely, it's fine. Again, this points to a timing dependant bug that is only tickled when the sync isn't being slowed down by latency or something else. Sorry I'm not being more helpful. Cheers, -- - | ,''`. Stephen Gran | | : :' :sg...@debian.org | | `. `'Debian user, admin, and developer | |`- http://www.debian.org | - signature.asc Description: Digital signature
Bug#596291: offlineimap getting stuck when run with multiple threads/connections
This one time, at band camp, Stephen Gran said:
> Copy message 3166 from lists.clamav-users:
>Copy message 3166 IMAP[lists.clamav-users] -> Maildir[lists.clamav-users],
> LocalStatus[lists.clamav-users]
> Copy message 3166 from lists.clamav-users:
>DEBUG[imap]: 49:23.94 > GAHI1199 UID FETCH 3166 (BODY.PEEK[])
>
> The server is just sat in:
> epoll_wait(5, {}, 4, 5000) = 0
I've managed to correlate the server side and the client side a bit
more:
Copy message 2099 from debian.amd64.2007:
Copy message 2099 IMAP[debian.amd64.2007] -> Maildir[debian.amd64.2007],
LocalStatus[debian.amd64.2007]
Copy message 2100 from debian.amd64.2007:
Copy message 2100 IMAP[debian.amd64.2007] -> Maildir[debian.amd64.2007],
LocalStatus[debian.amd64.2007]
But the server sees:
[pid 12586] read(0, "BHAJ7358 UID FETCH 2099 (BODY.PEEK[])\r\n"..., 3029) = 39
[pid 12586] write(1, "* 2099 FETCH (UID 2099 BODY[] {5143}\r\nReturn-path:
<, 4094) = 4094
[pid 12586] write(1, "BHAJ7358 OK Fetch completed.\r\n"..., 1120) = 1120
[pid 12586] epoll_wait(5,
[pid 12568] <... epoll_wait resumed> {}, 14, 1000) = 0
[pid 12568] epoll_wait(10,
[pid 12586] <... epoll_wait resumed> {}, 3, 517) = 0
[pid 12586] epoll_wait(5,
[pid 12568] <... epoll_wait resumed> {}, 14, 1000) = 0
and there it hangs. So it looks like the client thinks it's sent a
FETCH, but the server never sees it. Hope this is helpful.
I have so far been unable to reproduce this when running offlineimap
under strace, which suggests a timing dependant bug (kind of as
suspected, but still not all that helpful, I realize). The earlier
strace (and the strace I see when attaching after it hangs) does suggest
that a lock is not being releaesed somewhere, but I can't immediately
see anything obviously wrong with the logic in the code.
Cheers,
--
---------
| ,''`.Stephen Gran |
| : :' :sg...@debian.org |
| `. `'Debian user, admin, and developer |
|`- http://www.debian.org |
-
signature.asc
Description: Digital signature
Bug#596291: offlineimap getting stuck when run with multiple threads/connections
This one time, at band camp, Rogério Brito said:
> As I reported in another bug (about offlineimap dying too easily under
> many circumstances), attached is what I see when I strace one of the
> running threads of offlineimap when it is run with 10 connections to
> initially mirror my gmail account to a local maildir.
>
> I am not trying anymore to push the messages to the gmail server---I am
> now trying to pull a fresh copy of them from there.
>
> If there is anything that would be desired and if I can reproduce it,
> then, please, let me know.
Hi,
Just a me too report. I'm seeing it die after fetching a few thousand
mails here, although the time to hang is variable. I've tried running
it against both the lenny dovecot and the current bpo dovecot, and it's
the same. I've also tried with both python 2.6 and 2.5 to see if the
recent python transition is what's broken it, but it also hangs with 2.5.
Below is the end of the debug imap output. Trying to run debug thread
(which is where it seems to actually hang) throws a recursion exceeded
exception, which is slightly unhelpful :)
Thanks for looking at this.
Copy message 3166 from lists.clamav-users:
Copy message 3166 IMAP[lists.clamav-users] -> Maildir[lists.clamav-users],
LocalStatus[lists.clamav-users]
Copy message 3166 from lists.clamav-users:
DEBUG[imap]: 49:23.94 > GAHI1199 UID FETCH 3166 (BODY.PEEK[])
The server is just sat in:
epoll_wait(5, {}, 4, 5000) = 0
So it looks like they've somehow got out of sync with each other. I'm
assuming the server thinks it's answered the last request, and
offlineimap thinks it's made the last request, so they're deadlocked
waiting for the other side to do something.
Cheers,
--
-----
| ,''`.Stephen Gran |
| : :' :sg...@debian.org |
| `. `'Debian user, admin, and developer |
|`- http://www.debian.org |
-
signature.asc
Description: Digital signature
Bug#593125: puppet: 2.6.0 produces empty files on client with 2.5.x puppetmaster
Package: puppet
Version: 2.6.0-2
Severity: normal
Hello,
We run 4 squeeze freebsd servers, and the puppet clients talk to a lenny
+ bpo puppetmaster. When 2.6.0 migrated to squeeze, we started to get
empty files on the clients. The clients knew that the checksum was
non-empty, but never pulled the data down, eg:
notice: //Nagios::Client/File[/etc/nagios/nrpe.d/nrpe_dsa.cfg]/content: content
changed '{md5}d41d8cd98f00b204e9800998ecf8427e' to
'{md5}a5043ad9ae1e3173348704fffb001613'
(d41d8cd98f00b204e9800998ecf8427e is the md5sum of the empty string, and
a5043ad9ae1e3173348704fffb001613 is the correct md5sum of the file.
However, the file would still be 0 byte at the end of the puppet run.
Downgrading to the version below produces correct behavior.
Cheers,
-- System Information:
Debian Release: squeeze/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: kfreebsd-i386 (i686)
Kernel: kFreeBSD 8.1-1-686
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) (ignored: LC_ALL
set to en_US.utf8)
Shell: /bin/sh linked to /bin/dash
Versions of packages puppet depends on:
ii adduser 3.112add and remove users and groups
ii facter 1.5.7-1 a library for retrieving facts fro
pn libopenssl-ruby(no description available)
ii libruby [libxmlrpc-ruby 4.5 Libraries necessary to run Ruby 1.
ii libshadow-ruby1.8 1.4.1-8 Interface of shadow password for R
ii lsb-base3.2-23.1 Linux Standard Base 3.2 init scrip
ii puppet-common 0.25.4-2~bpo50+1 common files for puppet and puppet
ii ruby1.8 1.8.7.299-2 Interpreter of object-oriented scr
Versions of packages puppet recommends:
ii libaugeas-ruby1.8 0.3.0-1.1 Augeas bindings for the Ruby langu
ii ruby [rdoc] 4.5An interpreter of object-oriented
Versions of packages puppet suggests:
pn puppet-el (no description available)
pn vim-puppet (no description available)
-- Configuration Files:
/etc/default/puppet changed:
START=no
exit 0
DAEMON_OPTS="-w 5 --factsync"
-- 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
Bug#592322: [Pkg-clamav-devel] Bug#592322: Bug#592322: freshclam.conf: update moves DatabaseMirror line
This one time, at band camp, Török Edwin said: > Changing order here does something wrong with newlines, I get: > DatabaseMirror db.ro.clamav.net > < │ DatabaseMirror db.local.clamav.net DatabaseMirror > db.local.clamav.net │ DatabaseMirror database.clamav.net DatabaseMirror > database.clamav.net │ > DatabaseMirror db.ro.clamav.net Sorry for being slow, busy week at work. That is truely bizarre. I'll have time this weekend (hopefully!) to get a look at that. At first glance, I don't see a reason for it. Cheers, -- - | ,''`. Stephen Gran | | : :' :sg...@debian.org | | `. `'Debian user, admin, and developer | |`- http://www.debian.org | - signature.asc Description: Digital signature
Bug#592322: [Pkg-clamav-devel] Bug#592322: freshclam.conf: update moves DatabaseMirror line
This one time, at band camp, Török Edwin said:
> On Mon, 9 Aug 2010 12:55:32 +0100
> Stephen Gran wrote:
>
> > This one time, at band camp, Török Edwin said:
> > > After updating clamav-freshclam I got this diff:
> > > --- /etc/clamav/freshclam.conf 2010-06-10 15:40:04.624888178 +0300
> > > +++ /var/lib/clamav/freshclam.conf 2010-08-09 12:03:46.265177327
> > > +0300
> >
> > I agree this is most likely a bug - we're probably not popping off the
> > list in the same order we push onto it or something.
> >
> > However:
> >
> > > -- Package-specific info:
> > > --- configuration ---
> > > Checking configuration files in /usr/local/etc
> >
> > Can you try without local versions installed, just to make sure
> > nothing funny is happening as a result?
>
> Well I can't reproduce this with an apt-get --reinstall
> clamav-freshclam.
>
> What should I do to try and reproduce this bug? Revert to older
> clamav-freshclam then upgrade again?
Just eliminating the local version, and running
dpkg-reconfigure -phigh clamav-freshclam
once or twice should do it.
Although, looking at the way the list is set up, I can see that we are
in fact setting it up wrong:
We set up the variable:
if [ -e "$CLAMAVCONF" ]; then
for variable in `egrep -v '^[[:space:]]*(#|$)' "$CLAMAVCONF" | awk '{print
$1}'`; do
case "$variable" in
DatabaseMirror)
if [ -z "$DatabaseMirror" ]; then
for i in `grep ^$variable $CLAMAVCONF | awk '{print $2}'`; do
value="$i $value"
done
else
continue
fi
;;
Then store that in debconf:
if [ -n "$DatabaseMirror" ]; then
if [ -e /usr/share/doc/clamav-freshclam/mirror-list.gz ]; then
if zgrep -q "$DatabaseMirror"
/usr/share/doc/clamav-freshclam/mirror-list.gz;then
db_set clamav-freshclam/local_mirror `zgrep "$DatabaseMirror"
/usr/share/doc/clamav-freshclam/mirror-list.gz` || true
else
db_set clamav-freshclam/local_mirror "$DatabaseMirror" || true
fi
fi
fi
Then pull it out to construct the config file:
db_metaget clamav-freshclam/local_mirror value || true
[ "$RET" = "" ] || rawmirrors="$RET"
if echo "$rawmirrors" | egrep -q '(\(|\))'; then
mirrors=`echo "$rawmirrors" | awk '{print $1}'`
else
mirrors="$rawmirrors"
fi
And then finally write out the temporary copy of the config file:
if [ -n "$mirrors" ]; then
for i in $mirrors; do
echo "DatabaseMirror $i" >> $DEBCONFILE
done
fi
if ! echo "$mirrors" | grep -q database.clamav.net; then
echo "DatabaseMirror database.clamav.net" >> $DEBCONFILE
fi
if [ -n "$DatabaseMirror" ]; then
for m in $DatabaseMirror; do
grep -q "$m" "$DEBCONFILE" || echo "DatabaseMirror $m" >> $DEBCONFILE
done
fi
So it looks like the simple fix will be to change:
value="$i $value"
to
value="$value $i"
in /var/lib/dpkg/info/clamav-freshclam.config and
/var/lib/dpkg/info/clamav-freshclam.postinst
If the naive first try of dpkg-reconfigure still does the wrong thing
for you after removing the local copy, can you try this fix and let me
know if it does the right thing? I suspect that's all that's needed,
but as you have a handy test case, it would be useful to confirm it.
My fear is that it will be a more subtle bug with the way we are using
debconf to store the data (that the template expects a single value, and
we are potentially storing a space seperated multi-value list, some of
which aren't in the debconf list of things to pick from). If the above
simple case doesn't fix it for you, I may ask you to do some more set -x
debugging to confirm that.
Cheers,
--
-
| ,''`.Stephen Gran |
| : :' :sg...@debian.org |
| `. `'Debian user, admin, and developer |
|`- http://www.debian.org |
-
signature.asc
Description: Digital signature
Bug#592322: [Pkg-clamav-devel] Bug#592322: freshclam.conf: update moves DatabaseMirror line
This one time, at band camp, Török Edwin said: > After updating clamav-freshclam I got this diff: > --- /etc/clamav/freshclam.conf 2010-06-10 15:40:04.624888178 +0300 > +++ /var/lib/clamav/freshclam.conf 2010-08-09 12:03:46.265177327 +0300 I agree this is most likely a bug - we're probably not popping off the list in the same order we push onto it or something. However: > -- Package-specific info: > --- configuration --- > Checking configuration files in /usr/local/etc Can you try without local versions installed, just to make sure nothing funny is happening as a result? Cheers, -- - | ,''`. Stephen Gran | | : :' :sg...@debian.org | | `. `'Debian user, admin, and developer | |`- http://www.debian.org | - signature.asc Description: Digital signature
Bug#583815: df plugin fails for many tmpfs mounts
This one time, at band camp, Tom Feiner said: > Hi Stephen, > > Thanks for the bug report! > > From what I can tell, this bug has been fixed in munin 1.4. You can see the > diff in the df plugin between 1.2.6 and 1.4.5 at [1]. There's some special > attention for tmpfs and udev mounts. > > Can you confirm that the latest version of the df plugin solves your issue? It does, thank you, although config currently fails because print_threshhold() is undefined - presumably Munin::Plugin has been updated as well. Cheers, -- - | ,''`. Stephen Gran | | : :' :sg...@debian.org | | `. `'Debian user, admin, and developer | |`- http://www.debian.org | - signature.asc Description: Digital signature
Bug#588599: [Pkg-clamav-devel] Bug#588599: /usr/bin/freshclam: freshclam tries to mmap() with READ/WRITE/EXECUTE access
This one time, at band camp, Russell Coker said:
> type=AVC msg=audit(1278729355.797:22750): avc: denied { execmem } for
> pid=2649 comm="freshclam" scontext=system_u:system_r:freshclam_t:s0
> tcontext=system_u:system_r:freshclam_t:s0 tclass=process
> type=SYSCALL msg=audit(1278729355.797:22750): arch=c03e syscall=9
> success=no exit=-13 a0=0 a1=1000 a2=7 a3=22 items=0 ppid=1 pid=2649
> auid=4294967295 uid=104 gid=108 euid=104 suid=104 fsuid=104 egid=108 sgid=108
> fsgid=108 tty=(none) ses=4294967295 comm="freshclam" exe="/usr/bin/freshclam"
> subj=system_u:system_r:freshclam_t:s0 key=(null)
>
> The above messages are logged when running this on a SE Linux system. It
> appears to work correctly anyway so it seems that the code has some fallback
> option for if execmem is denied.
>
> I can't think of a good reason for a program to have write/execute access to
> memory when all it does is download data from the network.
I agree. Can you provide some help tracking it down?
Cheers,
--
---------
| ,''`.Stephen Gran |
| : :' :sg...@debian.org |
| `. `'Debian user, admin, and developer |
|`- http://www.debian.org |
-
signature.asc
Description: Digital signature
Bug#586796: [Pkg-clamav-devel] Bug#586796: clamav failed to update daily & incremental db from remote server
This one time, at band camp, naths said: > when trying to update with freshclam, it fail to update as > " daily-10813.cdiff not found on remote server (IP: 61.177.194.226) > Can't download daily-10813.cdiff from db.local.clamav.net and > Incremental update failed, trying to download daily.cvd > Trying host db.local.clamav.net (61.177.194.226)... > Downloading daily.cvd [100%] WARNING: Mirror 61.177.194.226 is not > synchronized. > > earlier there was no problem with db update. Hi Luca, This sounds like a mirror gone stale. Can you take a look please? Cheers, -- - | ,''`. Stephen Gran | | : :' :sg...@debian.org | | `. `'Debian user, admin, and developer | |`- http://www.debian.org | - signature.asc Description: Digital signature
Bug#585560: dvdbackup someties lies about which vob file had read errors
This one time, at band camp, Kolja Nowak said: > This happens because dvdbackup.c:DVDCopyTitleVobX reads the source dvd using > an abstract api using only title ids and no file names, and therefore needs > to reconstruct a file name when printing error messages. It includes the > correct title set id in the fake file name, but sets the vob number always > to zero, which is only correct for the first vob in a title set. > DVDCopyTitleVobX already has the correct vob number and uses it to construct > the the correct target vob file name, and therefore its trivial to use the > same number to create a correct file name for the error message. > > My attached patch does exactly this. Looks perfect! Thanks for the investigation and the patch. Cheers, -- - | ,''`. Stephen Gran | | : :' :sg...@debian.org | | `. `'Debian user, admin, and developer | |`- http://www.debian.org | - signature.asc Description: Digital signature
Bug#585002: [Pkg-clamav-devel] Bug#585002: clamav-daemon segfault at start
This one time, at band camp, Sebastian Hofmann said: > After upgrading start of clamav-daemon fails with a segfault: > > Starting ClamAV daemon: clamd /etc/init.d/clamav-daemon: line 308: 16305 > Speicherzugriffsfehler start-stop-daemon --start -o -c $User --exec > $DAEMON > failed! > > > Running clamd from command line, only this message is logged: > > Jun 8 10:33:30 s15210388 kernel: clamd[16637] general protection > rip:2aba8f6ad730 rsp:7fff1b400c10 error:0 > > Nothing else to see in the logs. Does clamscan also segfault? Cheers, -- - | ,''`.Stephen Gran | | : :' :sg...@debian.org | | `. `'Debian user, admin, and developer | |`- http://www.debian.org | - signature.asc Description: Digital signature
Bug#584603: bind9: incomplete geoip patch
Package: bind9
Version: 1:9.7.0.dfsg.P1-1
Severity: normal
Tags: patch
Hi,
It looks like you've merged the geoip patch into bind9, which is
fantastic. Sadly, I've noticed that I probably sent you an incomplete
version, which doesn't handle v6 correctly. I found during debugging
that you need a seperate geoip context per database, so we need to
create a second geoip context and do the v6 lookups against that. Patch
attached.
This bug is being written on a machine with bind9 installed from lenny,
but please ignore the version numbers below - they are irrelevant to the
bug report. The relevant version is above.
Cheers,
-- System Information:
Debian Release: 5.0.4
APT prefers stable
APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.32-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.utf-8, LC_CTYPE=en_US.utf-8 (charmap=UTF-8) (ignored: LC_ALL
set to en_US.utf-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages bind9 depends on:
ii adduser 3.110add and remove users and groups
ii bind9utils 1:9.5.1.dfsg.P3-1+lenny1 Utilities for BIND
ii debconf [debcon 1.5.24 Debian configuration management sy
ii libbind9-40 1:9.5.1.dfsg.P3-1+lenny1 BIND9 Shared Library used by BIND
ii libc6 2.7-18lenny2 GNU C Library: Shared libraries
ii libcap2 2.11-2 support for getting/setting POSIX.
ii libdb4.64.6.21-11Berkeley v4.6 Database Libraries [
ii libdns451:9.5.1.dfsg.P3-1+lenny1 DNS Shared Library used by BIND
ii libisc451:9.5.1.dfsg.P3-1+lenny1 ISC Shared Library used by BIND
ii libisccc40 1:9.5.1.dfsg.P3-1+lenny1 Command Channel Library used by BI
ii libisccfg40 1:9.5.1.dfsg.P3-1+lenny1 Config File Handling Library used
ii libkrb531.6.dfsg.4~beta1-5lenny4 MIT Kerberos runtime libraries
ii libldap-2.4-2 2.4.11-1+lenny1 OpenLDAP libraries
ii liblwres40 1:9.5.1.dfsg.P3-1+lenny1 Lightweight Resolver Library used
ii libssl0.9.8 0.9.8g-15+lenny6 SSL shared libraries
ii libxml2 2.6.32.dfsg-5+lenny1 GNOME XML library
ii lsb-base3.2-20 Linux Standard Base 3.2 init scrip
ii net-tools 1.60-22 The NET-3 networking toolkit
ii netbase 4.34 Basic TCP/IP networking system
bind9 recommends no packages.
Versions of packages bind9 suggests:
pn bind9-doc (no description available)
ii dnsutils1:9.5.1.dfsg.P3-1+lenny1 Clients provided with BIND
pn resolvconf (no description available)
pn ufw(no description available)
-- debconf information:
* bind9/different-configuration-file:
* bind9/run-resolvconf: true
* bind9/start-as-user: bind
--
-
| ,''`. Stephen Gran |
| : :' :sg...@debian.org |
| `. `'Debian user, admin, and developer |
|`- http://www.debian.org |
-
--- lib/dns/acl.c.old 2010-06-05 00:41:38.0 +0100
+++ lib/dns/acl.c 2010-06-05 00:48:43.0 +0100
@@ -35,6 +35,9 @@
#ifdef SUPPORT_GEOIP
static GeoIP *geoip = NULL;
+#ifdef GEOIP_V6
+static GeoIP *geoip6 = NULL;
+#endif
#endif
/*
@@ -396,25 +399,31 @@
case dns_aclelementtype_ipcountry:
/* Country match */
if (NULL == geoip) {
- geoip = GeoIP_new(GEOIP_MEMORY_CACHE);
+if (GeoIP_db_avail(GEOIP_COUNTRY_EDITION))
+ geoip = GeoIP_open_type(GEOIP_COUNTRY_EDITION, GEOIP_MEMORY_CACHE);
}
- if (NULL != geoip) {
- const char *value = NULL;
+#ifdef GEOIP_V6
+ if (NULL == geoip6) {
+if (GeoIP_db_avail(GEOIP_COUNTRY_EDITION_V6))
+ geoip = GeoIP_open_type(GEOIP_COUNTRY_EDITION_V6, GEOIP_MEMORY_CACHE);
+ }
+#endif
- if (reqaddr->family == AF_INET) {
-value = GeoIP_country_code_by_addr(geoip,inet_ntoa(reqaddr->type.in));
+const char *value = NULL;
+
+ if (reqaddr->family == AF_INET) {
+ value = GeoIP_country_code_by_addr(geoip,inet_ntoa(reqaddr->type.in));
#ifdef GEOIP_V6
- } else if (reqaddr->family == AF_INET6) {
-value = GeoIP_country_name_by_ipnum_v6(geoip, (geoipv6_t)reqaddr->type.in6);
+ } else if (reqaddr->family == AF_INET6) {
+ value = GeoIP_country_name_by_ipnum_v6(geoip6, (geoipv6_t)reqaddr->type.in6);
#endif
- }
+ }
- if ((NULL != value) && (2 == strlen(value))) {
-if ((e->country[0] == value[0]) && (e->country[1] == value[1])) {
- return (ISC_TRUE);
-}
+ if ((NULL != value) && (2 == strlen(val
Bug#583815: munin-plugins-extra: df plugin fails for many tmpfs mounts
Package: munin-plugins-extra Version: 1.2.6-10~lenny2 Severity: normal fetch df _dev_sda1.value 73 tmpfs.value 0 udev.value 1 tmpfs.value 1 _dev_sda2.value 89 tmpfs.value 5 . quit Compare to http://wagner-xen1.debian.org/munin/debian.org/wagner-xen1.debian.org-df.html Only /tmp is (theoretically) being graphed, but it's actually getting the values of /lib/init/rw. -- System Information: Debian Release: 5.0.4 APT prefers oldstable APT policy: (500, 'oldstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.18-6-xen-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.utf8) Shell: /bin/sh linked to /bin/bash Versions of packages munin depends on: ii adduser 3.110 add and remove users and groups pn libdigest-md5-perl (no description available) ii libhtml-template-perl2.9-1 HTML::Template : A module for usin ii librrds-perl 1.3.1-4 Time-series data storage and displ pn libstorable-perl (no description available) ii perl [libtime-hires-perl 5.10.0-19lenny2 Larry Wall's Practical Extraction ii perl-modules 5.10.0-19lenny2 Core Perl modules ii rrdtool 1.3.1-4 Time-series data storage and displ Versions of packages munin recommends: ii libdate-manip-perl 5.54-1 a perl library for manipulating da ii munin-node 1.2.6-10~lenny2 network-wide graphing framework (n Versions of packages munin suggests: ii apache2-mpm-prefork [htt 2.2.9-10+lenny7 Apache HTTP Server - traditional n ii lynx-cur [www-browser] 2.8.7dev9-2.1 Text-mode WWW Browser with NLS sup ii w3m [www-browser]0.5.2-2+b1 WWW browsable pager with excellent -- 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
Bug#583319: slapd: built-in schema for uidNumber/gidNumber does not have ordering directive
Package: slapd Version: 2.4.11-1+lenny1 Severity: normal Hello, It is frequently useful to be able to do searches like (uidNumber>=1). This used to be possible by munging the NIS schema to include: ORDERING integerOrderingMatch on the uidNumber and gidNumber attributes. Now that the attributes are built in, this is not possible. Please consider adding an ORDERING directive to the attribute definition. Cheers, -- System Information: Debian Release: 5.0.4 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-3-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf-8, LC_CTYPE=en_US.utf-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.utf-8) Shell: /bin/sh linked to /bin/bash Versions of packages slapd depends on: ii adduser 3.110 add and remove users and groups ii coreutils 6.10-6 The GNU core utilities ii debconf [debconf- 1.5.24 Debian configuration management sy ii libc6 2.7-18lenny2 GNU C Library: Shared libraries ii libdb4.2 4.2.52+dfsg-5 Berkeley v4.2 Database Libraries [ ii libgnutls26 2.4.2-6+lenny2 the GNU TLS library - runtime libr ii libldap-2.4-2 2.4.11-1+lenny1OpenLDAP libraries ii libltdl3 1.5.26-4+lenny1A system independent dlopen wrappe ii libperl5.10 5.10.0-19lenny2Shared Perl library ii libsasl2-22.1.22.dfsg1-23+lenny1 Cyrus SASL - authentication abstra ii libslp1 1.2.1-7.5 OpenSLP libraries ii libwrap0 7.6.q-16 Wietse Venema's TCP wrappers libra ii perl [libmime-bas 5.10.0-19lenny2Larry Wall's Practical Extraction ii psmisc22.6-1 Utilities that use the proc filesy ii unixodbc 2.2.11-16 ODBC tools libraries Versions of packages slapd recommends: ii libsasl2-modules 2.1.22.dfsg1-23+lenny1 Cyrus SASL - pluggable authenticat Versions of packages slapd suggests: ii ldap-utils 2.4.11-1+lenny1 OpenLDAP utilities -- debconf information: slapd/password_mismatch: slapd/tlsciphersuite: slapd/invalid_config: true * shared/organization: lobefin.net slapd/upgrade_slapcat_failure: slapd/slurpd_obsolete: * slapd/backend: HDB slapd/dump_database: when needed * slapd/allow_ldap_v2: false * slapd/no_configuration: false slapd/move_old_database: true slapd/suffix_change: false slapd/dump_database_destdir: /var/backups/slapd-VERSION * slapd/purge_database: false * slapd/domain: lobefin.net -- - | ,''`. Stephen Gran | | : :' :sg...@debian.org | | `. `'Debian user, admin, and developer | |`- http://www.debian.org | - signature.asc Description: Digital signature
Bug#583110: Fails to restore raid speed on error
This one time, at band camp, Goswin von Brederlow said: > In my case I have a SATA Port Multiplier, last one I ever buy :), and > it seems that takes a while to work after a boot. Sometimes its disks > just aren't there fast enough during boot and for example the fsck run > fails. I'm guessing the hdparm script fails too and then the raid > speed remains at 0. Instead of guessing, would it be possible for you to debug this? Cheers, -- - | ,''`. Stephen Gran | | : :' :sg...@debian.org | | `. `'Debian user, admin, and developer | |`- http://www.debian.org | - signature.asc Description: Digital signature
Bug#577499: [Pkg-clamav-devel] Bug#577499: Bug#577499: Me too
This one time, at band camp, Gordon Haverland said: > After the 4 dpkg-reconfigure runs, things seem to be working. > That was the end result mentioned above. That nothing in > /etc/clamav changed after the fresh re-install (after purging) was > interesting. What it looks like happened was: Due to a bug in our maintainer scripts, debconf put a bad value in the config file. This made clamd a bit wobbly and made freshclam unable to talk to it. You updated the config file manually. From here on, configuration did not change. The dpkg-reconfigure runs were to ensure that we didn't further screw up your configuration files - we passed that test, at least, by not writing more garbage into them. The reason it's all working now is that you have (by way of running dpkg-reconfigure in the right order) restarted both clamd and freshclam now that the correct config file is in place. You should be ok now, and thanks for helping us debug this. Cheers, -- - | ,''`. Stephen Gran | | : :' :sg...@debian.org | | `. `'Debian user, admin, and developer | |`- http://www.debian.org | - signature.asc Description: Digital signature
