Bug#817232: Stil present in 1.158

2017-01-20 Thread sacrificial-spam-address
# dpkg -s keyboard-configuration Package: keyboard-configuration Status: install ok installed Priority: optional Section: utils Installed-Size: 2502 Maintainer: Debian Install System Team Architecture: all Multi-Arch: foreign Source: console-setup Version: 1.137

Bug#802638: "rlimit memlock -1" fixes it

2015-10-22 Thread sacrificial-spam-address
I was having the same problem, and indeed this fixes it.

Bug#793745: [PATCH] I'm seeing it too.

2015-08-02 Thread sacrificial-spam-address
Since I run a pool server, I have a customized config. That means that I have the pool servers commented out, and the comment on the rlimit command says it's not needed in that case, so I left it out of my config. And ran into the same problem. Really, ntpd should make calls like getpwuid()

Bug#793745: [pkg-ntp-maintainers] Bug#793745: [PATCH] I'm seeing it too.

2015-08-02 Thread sacrificial-spam-address
Maybe the comment is a little misleading. How about # Preventing ntpd from swapping (with mlockall()) reduces time delays, # but resource limits (ulimit -l) cause out-of-meory errors that lead to # ntpd quitting with strange (or no) error messages. Particular trouble # spots are the -u option

Bug#722604: Workaround patch

2013-09-20 Thread sacrificial-spam-address
Thank you very much, your positive feedback is appreciated as well. When you do this in your spare time a nice word now and then makes a huge difference. Although I tried not to be a complete asshole about it, I was pretty pissed off at the beginning, and in particular I saw some friction

Bug#722604: Workaround patch

2013-09-18 Thread sacrificial-spam-address
I've been installing 204-4 on various machines, and I wanted to thank you for both the nice clear informative warning *and* the override provision so that I can do the upgrade before rebooting into the new kernel. Much appreciated! -- To UNSUBSCRIBE, email to

Bug#722604: I also had a non-booting machine...

2013-09-17 Thread sacrificial-spam-address
Just to send a me, too!, I also recently bumped udev to the systemd version and also had a non-booting machine. Now, most of my machines had a sufficiently well-populated static /dev that I could boot and actually didn't notice the lack of udevd. On the non-booting machine, it was getting

Bug#722604: Workaround patch

2013-09-17 Thread sacrificial-spam-address
Control: tags 722604 + patch udev 204-3 will work, with a hand-rolled kernel and no initramfs, if you do the following: 1. Enable CONFIG_DEVTMPFS=y. DEVTMPFS_MOUNT is not required. 2. Apply the following patch to /etc/init.d/udev. There are five parts to this patch: 1. Add the quotes to

Bug#722604: Workaround patch

2013-09-17 Thread sacrificial-spam-address
Or you just update to 204-4 which has been uploaded a few hours ago. Well, yes, thank you, but it wasn't even in the BTS when I started work on the bug, and it still isn't on ftp.debian.org as of a few seconds before I send this message. ftp ls udev_* 200 PORT command successful. Consider using

Bug#709502: Debhelper 9.20130518 breaks file-rc

2013-05-23 Thread sacrificial-spam-address
Package: debhelper Version: 9.20130518 Severity: serious (I already sent this with a different title, but submit@ appended it to the closed bug 708720, which isn't helpful, as this is a different bug; the connection is just that the fix for that introduced this.) Since this version, packages are

Bug#677650: Here's a patch that APPEARS to work

2012-12-06 Thread sacrificial-spam-address
I don't know Ruby AT ALL, but I did a bit of googling and this appears to make unhide.rb work with 1.9: --- unhide.rb.orig 2012-12-06 23:53:57.0 -0500 +++ unhide.rb 2012-12-06 23:52:51.0 -0500 @@ -29,7 +29,11 @@ # Support for libc functions not covered by the standard Ruby

Bug#691311: Upgrading liboctave1 confirmed to fix

2012-10-25 Thread sacrificial-spam-address
I confirm this. The solution is to upgrade your liboctave1 package to version 3.6.3-2. Thanks for the tip; I would have upgraded that at the same time, but managed to overlook it since it's a long way away in an alphabetical list. That does indeed fix it. -- To UNSUBSCRIBE, email to

Bug#659784: Which version of libblas3 is #659784 fixed in?

2012-06-13 Thread sacrificial-spam-address
As I reported on June 6, I'm still seeing the bug in libblas3 version 1.2.20110419-3: http://bugs.debian.org/cgi-bin/bugreport.cgi?msg=75;bug=659784 I notice it was re-marked fixed on the 9th, but I don't actually see a fixed version anywhere. I waited a few days for one to propagate through the

Bug#659784: Which version of libblas3 is #659784 fixed in?

2012-06-13 Thread sacrificial-spam-address
Make sure atlas is also updated. It is likely to be your problem. Especially if you mix testing unstable. Huh; I've used unstable (not testing) for years. I actually do have testing in the sources.list, but I'm not using it. I think what's happened is that I have a specialized atlas package

Bug#641873: closed by Michael Gilbert michael.s.gilb...@gmail.com (Bug#641873: fixed in xpdf 3.03-9)

2012-02-24 Thread sacrificial-spam-address
Thanks, I'll test it as soon as it reaches the FTP site. Sorry I haven't been following all the activity this last month... -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#658258: Cups 1.5.0-16 breaks plain text printing

2012-02-07 Thread sacrificial-spam-address
# grep texttops /etc/cups/mine.convs application/x-cshell application/postscript 33 texttops This is a local configuration file, not shipped by cups. So this does not break the package for everybody, but nevertheless is a rather important upgrade issue. But I don't want to argue about

Bug#658258: Cups 1.5.0-16 breaks plain text printing

2012-02-01 Thread sacrificial-spam-address
Package: cups Version: 1.5.0-16 Severity: grave [521]$ echo Hello, world | lpr lpr: Unsupported document-format text/plain. The split off of a separate cups-filters package omits the texttops command which is called for in /etc/cups/mime.convs. # dpkg-deb -c cups-filters_1.0~b1-3_i386.deb |

Bug#647598: chgrp: cannot access `/var/run/named': No such file or directory

2011-12-29 Thread sacrificial-spam-address
Package: bind9 Version: 1:9.8.1.dfsg-1.1 I was updating an old system from bind 8, and there was no existing pid file in /var/run. Thus, postinst failed: Installing new version of config file /etc/bind/db.root ... Installing new version of config file /etc/bind/db.local ... Adding group `bind'

Bug#649099: BIND 9 Resolver crashes after logging an error in query.c

2011-11-17 Thread sacrificial-spam-address
Package: bind9 Version: 1:9.8.1.dfsg-1 Severity: serious Tags: security upstream As you have probably heard, someone has found a way to remotely crash a bind9 server: http://isc.sans.edu/diary.html?storyid=12049 https://www.isc.org/software/bind/advisories/cve-2011-4313 A stopgap patch

Bug#647909: NetAddr::IP versions 4.045 through 4.053 are BROKEN

2011-11-07 Thread sacrificial-spam-address
Package: libnetaddr-ip-perl Version: 4.056+dfsg-0 Severity: serious CPAN bug #71925 is preventing spamassassin from functioning correctly. The bug was fixed in 4.053. An additonal buglet (affecting only Perl 5.6.1 and older) was fixed in 4.054, which doesn't affect Debian, but the author

Bug#643967: prelink -u fails on some binaries; this breaks debsums

2011-10-01 Thread sacrificial-spam-address
Package: prelink Version: 0.0.20090925-1 Severity: serious On i386, consider the following series of commands: # dpkg -i psmisc_22.14-1_i386.deb (snipped) # /usr/sbin/prelink -y --md5 /usr/bin/pstree bb296a950a089ec8a837a1c97b47eeb9 /usr/bin/pstree # /usr/sbin/prelink -mR -T /usr/bin/pstree #

Bug#536640: [Pkg-samba-maint] Bug#536640: Bug#536640: Samba 2:3.4.0-1 crashes on startup

2009-07-23 Thread sacrificial-spam-address
Nothing unfortunately happened about that bug report. To submitter: I guess the problem is still happening, right? Er, well, I of course backed the version down and haven't tried again, but I expect it to fail exactly the same way. Testing... yes, it still blows up. Backing down to 3.3.6-1

Bug#536640: Samba 2:3.4.0-1 crashes on startup

2009-07-11 Thread sacrificial-spam-address
Package: samba Version: 2:3.4.0-1 Severity: grave After upgrading a working 3.3.6-1 configuration to 3.4.0-1, smbd started exploding on startup. This is an i386 (32-bit) userland on an AMD quad-processor (Phenom) with a 64-bit kernel. All packages from current debian/unstable. The failure is

Bug#532517: Blum-Blum-Shub is unnecessary overkill

2009-06-22 Thread sacrificial-spam-address
You want a cryptographically secure PRNG, but you don't need something as provably secure as BBS. Even more importantly, you need a cryptographically secure seed. (Fortunately, easy on Linux, where you can just use /dev/urandom.) There are any number of suitable CPRNGs. Probably a good safe

Bug#515720: [Pkg-hpijs-devel] Bug#515720: hp-setup -i dies when picking PPD

2009-03-15 Thread sacrificial-spam-address
Mark Purcell m...@debian.org wrote: Can I ask you to try: the workaround: LANG= gksu hp-setup Actually, I did # LANG= hp-setup -i (I don't have the python-qt4 packages installed, so couldn't run GUI mode if I wanted to.) And it indeed did not blow up, although test page printing

Bug#515720: [Pkg-hpijs-devel] Bug#515720: hp-setup -i dies when picking PPD

2009-03-15 Thread sacrificial-spam-address
Mark Purcell m...@debian.org wrote: Actually, I did # LANG= hp-setup -i (I don't have the python-qt4 packages installed, so couldn't run GUI mode if I wanted to.) And it indeed did not blow up, although test page printing failed. Excellent. At least we are getting somewhere now. Have a

Bug#515720: hp-setup -i dies when picking PPD

2009-03-08 Thread sacrificial-spam-address
I suspect this is the same bug, so I'm appending it to the existing bug report. When I run hp-setup -i, it starts out working okay. Select connection type... network/ethernet Select device... (probe delay)... hp:/net/HP_LaserJet_4100_Series?ip=192.35.100.71

Bug#390893: The apache2-common removal workaround

2006-10-03 Thread sacrificial-spam-address
Oh, I'm sorry it wasn't obvious. The problem is that 1) apache2-common's prerm runs /etc/init.d/apache2 stop, which 2) runs /usr/sbin/apache2 -t, which 3) parses the config files, and does a full apache setup, which 4) tries to load all the modules, but 5) apache2-mpm-prefork has already been

Bug#320621: libdjvulibre1 3.5.14-6 changes soname without warning

2005-07-30 Thread sacrificial-spam-address
Package: libdjvulibre1 Version: 3.5.14-6 Severity: serious Any number of packages that link to /usr/lib/libdjvulibre.so.14 (I hit evince 0.3.0-2 first) break horribly when libdjvulibre.so.15 is installed ahead. I'm not sure how this should be handled, but neither the changelog nor the version