Package: adjtimex
Version: 1.29-2.2
Severity: minor
Dear Maintainer,
Under the -p, --print section the time_status kernel variable needs updating.
It does not discuss time_status for kernels newer than 2.6.
I noticed because on my 3.2 systems I have time_status of 8193, so apparently
8192 is a
I’m in agreement here.
I created a local fork without debugging disabled and installed this across
many systems for testing.
smime.p7s
Description: S/MIME cryptographic signature
I agree. But shouldn't this bug be filed against gnome and not
xul-ext-adblock-plus?
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
I would say this should be a bug for upstream to fix. It's usually a bad idea
to use
sudo within a script because suddenly the script is opaquely running as
different
users. Instead, the script should either require the user to be root (or within
sudo);
or handle the situation where the user is
I've patched this problem and sent a pull request.
https://github.com/astraw/stdeb/pull/65
If accepted you can remove the sudo package from the control file.
Or you can leave it in suggests since the README still references sudo.
--
To UNSUBSCRIBE, email to
I see the same problem, same version in Debian Wheezy.
This bug was apparently previously reported and fixed:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=509942
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
I this this bug is fixed in 0.9.7.7 and can therefore be closed.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
I've applied the patch to Linus' master HEAD
(43c422eda99b894f18d1cca17bcd2401efaf7bd0, at the time) and the patch seems to
work fine.
/proc/self/mounts correctly reflects whether or not the user specified to use a
trailing slash - and nothing is obviously broken.
If the patch looks fine to
I haven't had a chance to test it yet thanks. I'll be too busy until at least
mid-next week, but I will test it then if nobody beats me to it.
-Chris
On Sep 30, 2012, at 2:23 PM, Jonathan Nieder jrnie...@gmail.com wrote:
Thanks for looking it over. Did you get a chance to test Ben's patch?
I had a couple friends over today and we made a trivial patch to remove
trailing slashes. We do not know C and have never created a patch for the
kernel before, so there is undoubtedly a better way to do it. However we hope
this helps in your efforts.
On Sep 16, 2012, at 7:00 AM, Ben Hutchings wrote:
This was my first thought - but what if userland provides a device name
with a slash on the end? I think we have to report it back with the
slash in that case.
That is a great point. We could not find any standard as to whether or not
Just an update, I emailed Alexander Viro twice and I haven't heard back from
Alexander Viro or anyone on the kernel development mailing lists.
I am surprised that this issue is being ignored.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe.
Package: network-manager
Version: 0.9.5.95-1
Severity: wishlist
Tags: patch
Dear Maintainer,
Unfortunately network-manager is required by gnome to be installed at the
moment.
I am asking the Debian Gnome team if this can be fixed, but it might also
be nice to be able to disable network manager
Package: approx
Version: 5.2-1
Severity: important
Approx is having trouble downloading Google Chrome's Release file and I'm not
sure why.
Every other repository is working fine.
The error seems to be in the filesize calculation:
Size of google-chrome/dists/stable/Release should be -1, not
Just to make it clear, this was tested in Squeeze and not Wheezy despite
what was listed at the beginning of the initial bug report.
The mixup comes from the fact that I tried to install the Wheezy version
under Squeeze but it failed and I didn't completely roll it back before
submitting the
On Aug 23, 2012, at 7:37 PM, Eric Cooper wrote:
I'll upload a new version shortly, but it won't be in wheezy due to
the freeze.
Dang that freeze ;-). But half-seriously maybe we could consider this a serious
bug?
It certainly has the potential to cripple the usability of the package, e.g.
I can confirm this bug in network-manager version 0.9.5.95-1.
I created an upstream bug report here:
https://bugzilla.gnome.org/show_bug.cgi?id=681103
You may want to add a comment upstream confirming that the bug happens for you
too.
Thanks,
Chris
--
To UNSUBSCRIBE, email to
I can reproduce this; I get a failed slapd upgrade from Squeeze to Wheezy.
For some reason slapcat is never run and the .ldif file is never created.
Then load_databases() is run and tries to access a file that doesn't
exist.
chiestand@sagan:/tmp/openldap-2.4.31/debian$ sudo dpkg --configure -a
,
Chris Hiestand
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
On Jun 17, 2012, at 3:31 PM, Jonathan Nieder wrote:
I should have said v2.6.39-rc1~460^2^ (nfs: switch NFS from -get_sb()
to -mount(), 2011-03-16). So:
Thanks Jonathan,
Based on this tip I tested that commit and neighboring commits and was
able to find the commit that introduced the
Package: apt
Version: 0.9.3
Severity: normal
Dear Maintainers,
It seems that the install-recommended option will treat recommended exactly
like depends. However in some cases this is not the desired behavior. For
example, you would not want a recommended package's installation to force
the
Package: linux-source-3.2
Version: 3.2.15-1
Severity: normal
Tags: upstream
Dear Maintainer,
I believe it is convention to leave a trailing slash off of the nfs export
in /etc/fstab, e.g.:
nfsserver:/srv/ubuntu-32 /mnt/ubuntu-32 nfs
Package: mount
Version: 2.20.1-4
Severity: minor
File: /bin/mount
Dear Maintainer,
mount -t nfs -va attempts to mount everything in fstab, verbosely.
The minor problem is that eventhough all nfs shares are mounted
successfully, mount reports nothing was mounted at the end.
I'm speculating that
Unfortunately the answer from upstream is upgrade from 2.4.23, so
unless Debian can raise an exception to push a version update into
squeeze then it's going to require someone to perform a git bisection
and backport the fix :(
An easier workaround might be to package up the same version as
Package: slapd
Version: 2.4.23-7.2
Severity: normal
Tags: patch
I believe in previous versions of slapd there was a line in /etc/init.d/slapd
setting the ulimit -n higher. However this is not present in the current
version.
The original bug was reported in #378261. I am re-using the perl script
That's all fair enough, I've moved this to wishlist. I would find this patch,
or something like it, useful in order to make it easy for admins of
heavily-used servers to easily increase the ulimit and not have to maintain a
forked init file. Maintaining forks strains my technomage capabilities
On Feb 22, 2012, at 3:55 PM, Quanah Gibson-Mount wrote:
I would note the only reason this is being hit at all is because slapd has
been linked to tcpwrappers. I personally frown on such linking, as you can do
much more sophisticated filtering at the ACL level in OpenLDAP, and all it
does
Dear Paul,
I did try it out and it worked, thank you very much.
I tried it and it solves my problem.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
I have had the same problem, where I could not pxeboot from an alias of an
interface. eg pxeboot worked from hosts connected to eth0, but not to hosts
connected to eth0:1.
tcpdump shows what's happening:
18:41:00.618219 ARP, Request who-has 10.70.200.1 tell 10.70.200.167, length 46
Package: vnc4server
Version: 4.1.1+X4.3.0-37
Severity: normal
A repeated bad login generates a blacklist against 0.0.0.0 - but it
should be against the remote IP address. If a user then tries to connect
from a different IP, they will find that they are blacklisted.
A series of bad logins from any
Actually it does work!
On Apr 30, 2011, at 1:06 PM, Arthur de Jong wrote:
From the logs above
it seems that you are mixing ldaps:// with StartTLS. I think nslcd may
be trying to use StartTLS on an ldaps:// connection. Perhaps the slave
should provide a referral with ldap:// instead?
I
Package: xserver-xorg-core
Version: 2:1.7.7-13
Severity: wishlist
Tags: upstream
It would be nice to be able to specify where the auto-created
configuration file is saved instead of having to assume (that after new
versions) the file is still put in /root/xorg.conf.new
Ideally I'd like to be
In the development branch I've implemented an extra test
to see whether we're dealing with and LDAP password before doing
anything.
Great. Thank you. I look forward to the next version.
Anyway, for your environment I would suggest you try the minimum_uid
option.
I am using it, but I
Package: libpam-ldapd
Version: 0.7.13
Severity: wishlist
It's a little confusing at the moment why local users are prompted for an LDAP
password if you have specified ignore_unknown_user within your passwd
PAM configuration:
password sufficient pam_ldap.so debug ignore_unknown_user
Package: nslcd
Version: 0.7.13
Severity: normal
The passwd command is failing when consumer (slave) ldap servers are
specified before provider (master) ldap servers in nslcd.conf.
CLI:
username@host:/tmp$ passwd
Enter current password:
You can now choose the new password or passphrase.
I see what I was missing now. It's a little confusing to use the word default
in 2 different contexts:
1. As an argument meaning the LSB standard values for Default-Stop|Stop -
start 2 3 4 5, stop 0 1 6
2. In the error message meaning the script's value for LSB Default-Start|Stop.
I think a
Package: sysv-rc
Version: 2.88dsf-13.1
Severity: minor
Tags: patch
It seems to me that when an init script has non-lsb-standard runlevels,
they get misreported by update-rc.d:
sudo update-rc.d foobar defaults 25
update-rc.d: using dependency based boot sequencing
update-rc.d: warning: foobar
libsmbios is not in the squeeze distribution after the freeze date. I suppose
this means that we are not going to be able to use the Dell utilities in
squeeze unless we package them ourselves, port the ubuntu version, or perhaps
make a squeeze-backports version?
I'd like to have this package
Package: debconf
Version: 1.5.24
Severity: wishlist
It would be useful if we could take debconf-get-selections output, parse
it, and plug that into a debconf db file besides the system default.
For example, when administering many systems it is expedient to preload
debconf, and it is very useful
Package: debconf
Version: 1.5.24
Severity: normal
To reproduce put this into your /etc/debconf.conf file:
Name: mydb
Driver: DirTree
Directory: /tmp/mydb
Required: false
Extension: .txt
When using DirTree of
We also have an in-house tool to warn of expired certificates.
This is intentional, for the purpose of verifying older certificates.
To me, at first glance it would make more sense to remove expired
certificates. I assume the benefit of leaving expired certs installed
is that an
Package: nagios3
Version: 3.0.1-1~bpo40+1
Severity: minor
It's possible that this problem has been fixed in the already
available upstream version, and the debian version does need
to be bumped again. But the nagios sounds won't play in my web
browsers, Firefox 2.0.0.14 or Safari 3.1.1.
I
Package: libpam-ldap
Version: 180-1.8
Severity: important
We have recently set up a 2slave, 1 master ldap configuration using
replication and redirection. So the clients point at the slaves and are
redirected to the master for updates.
When ssl is set to 'start_tls' in pam_ldap.conf and a user
We're noticing what looks like the same bug when upgrading to snmpd
5.2.3-7etch2 . Could there have been a regression?
I have reproduced the bug on a system which seemed to be running fine
by running dpkg-reconfigure snmpd (ps -ef --forest):
root 23011 22986 0 12:08 pts/000:00:00
44 matches
Mail list logo
