Package: bind9
Version: 1:9.16.2-3
Severity: critical
Justification: breaks unrelated software
Dear Maintainer,
Life was good on my DNS server until my recent update to 9.16.2-3.
After upgrading, the exact configuration that was happy now fails to
start. Example:
# named -g -u bind
26-Apr-2020
Package: samba4
Version: 4.0.0~beta1+dfsg1-1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
I recently attempted to install the samba4 package on my system; this fails
persistently with the following output:
Setting up samba4 (4.0.0~beta1+dfsg1-1) ...
Traceback (most
Package: duplicity
Version: 0.6.18-1
Severity: minor
Dear Maintainer,
Every time I run duplicity, I receive the following trio of messages:
** (process:3384): WARNING **: Trying to register gtype 'GMountMountFlags' as
flags when in fact it is of type 'GEnum'
** (process:3384): WARNING **:
Package: mediatomb
Version: 0.12.1-2
Severity: normal
Tags: upstream
I'm guessing about the upstream part. I happened to notice my system has a
huge /var/log/mediatomb.log.5 file that's still being written.
The /etc/logrotate.d/mediatomb script specifies that a pkill -HUP mediatomb
should be
Package: linux-2.6
Version: 2.6.32-15
Severity: normal
Here is an oops reported by my system against my trusty DE500 card:
Jun 8 09:34:04 buzz kernel: [213252.816043] WARNING: at
Well, this is interesting...
In an attempt to minimize the impact of this problem, I switched my config
to use the DEC tulip-based card I also have in my system. This morning I got
almost exactly the same trace (inline below). This suggests that whatever
the problem is, it isn't specific to just
Package: linux-2.6
Version: 2.6.32-15
Severity: normal
This appears to be the same bug as:
https://bugzilla.kernel.org/show_bug.cgi?id=11663
I have attached kernel output; once the timeout occurs, the interface is
unusable and bounces spastically (without becoming operational) until the
system
Package: linux-image-2.6.30-1-alpha-smp
Version: 2.6.30-2
Severity: important
Well, the firmware loading logic has been flaky on my system for a few
releases now. I previously reported bug 527265 against 2.6.29, where the
qla1040 firmware would not load at all, and that was resolved in a later
Package: linux-image-2.6.29-1-alpha-smp
Version: 2.6.29-3
Severity: important
Yes, I have the firmware on the system. The non-free package
firmware-qlogic (from sid) is installed, /lib/firmware/qlogic/1040.bin
exists and update-initramfs doesn't whine about missing firmware. ;-)
See the
Package: linux-image-2.6.29-1-sparc64
Version: 2.6.29-3
Severity: normal
This kernel fails to boot on my Ultra60. Immediately after loading the initrd
image,
the message Fast Data Access MMU Miss appears and I get dropped back to the
PROM
ok prompt without any additional output.
This appears
Package: duplicity
Version: 0.5.06-2
Severity: wishlist
Tags: patch
I find myself attempting to perform secure backups that must transit a proxy
server to reach their destination. Generally I use PuTTY for these types of
connections, as it understands how to deal with the proxy (unlike OpenSSH).
Package: linux-image-2.6.25-2-amd64
Version: 2.6.25-2
Severity: normal
I see that both linux-image-2.6.25-1-amd64 and
linux-image-2.6.25-2-amd64 no longer include the atp870u SCSI module
(normally selected via CONFIG_SCSI_ACARD). This is a bummer since I have
one of these cards in my system. :-p
Package: initramfs-tools
Version: 0.92a
Severity: important
This seems very similar to reported (old) bugs, but it's a change in
behavior for me so I'm opening this new problem to flag it. I recently
updated to version 0.92 (I believe -- a couple days prior to 0.92a,
which also exhibits the
Package: aboot
Version: 1.0~pre20040408-2
Severity: important
My present kernel (2.6.22-3-alpha-smp) is the last Debian
kernel I have been able to boot successfully. I spent a lot of time
thinking this might be the kernel, but on reflection reading the console
output I blame aboot. :-)
For
Package: linux-image-2.6.24-1-alpha-smp
Version: 2.6.24-2
Severity: normal
I think the subject line says it all; this is on a 3-way AS4100. I am
attaching console output of a boot attempt. As failure occurs prior to
loading the initrd image, I am not sure any further configuration
details are
Package: libpam-krb5
Version: 3.5-1.1
Severity: normal
Don't panic over the version. :-) This is package 3.5-1 with some local
instrumenting added in an attempt to understand what is going on.
Documentation claims:
If the username provided to PAM contains an @ and Kerberos can,
treating the
Package: initramfs-tools
Version: 0.85g
Severity: important
Tags: patch
I just upgraded a ton of stuff (including LVM) after it hit testing
folllowing the etch release. :-) The new LVM version uses a different
file layout and consequently the lvm2 hook tries to grab the wrong file
(which no
Package: bacula-director-pgsql
Version: 1.38.11-6
Severity: minor
I assume this is a bogus dependency that crept in during the build process.
-- System Information:
Debian Release: testing/unstable
Architecture: alpha
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.17-6+scsi
Locale:
Package: mdadm
Version: 2.5.2-7
Severity: minor
The automatic check on first Sunday of month logic is b0rken. :-) The
specifier used in /etc/cron.d/mdadm is 6 1 1-7 * 7, but the problem is
that man 5 crontab (and unhappy experience) shows that the rule
triggers when minute, hour, month (6, 1,
Package: bacula-sd
Version: 1.38.9-7
Severity: important
I just upgraded from the long-suffering 1.36.3 release and started
tweaking my bacula-sd.conf file to add an Autochanger stanza as required
for the new version. With my old 1.36.3 configuration, everything ran
okay if you overlooked the
.
*
**/
-#define QLA1280_VERSION 3.26
+#define QLA1280_VERSION 3.26.rsb
/*
Revision History:
+Rev 3.26.rsb, May 10, 2006 R. Scott Bailey
+ - Increase timeouts (?) from 30 to 900 sec for tape support
Package: nfs-kernel-server
Version: 1:1.0.7-9
Severity: important
The change introduced in this update to check for init_nfsd instead of
nfsd_version caused the server to fail to restart on my system after
this upgrade. I manually edited /etc/init.d/nfs-kernel-server to change
the test back to
Package: linux-source-2.6.12
Version: 2.6.12-1
Severity: important
Well, in attempting to check 2.6.12 to see if it fixes md bugs in 2.6.10
and SCSI problems in 2.6.11, I have run into another problem... The
system fails to find my serial console and init dies at the beginning of
the bootstrap
Package: kernel-source-2.6.10
Version: 2.6.10-5
Severity: important
Tags: patch
The attached patch against 2.6.10-5, due to Neil Brown, corrects a
problem in 2.6.10 which causes the md driver to leak bios -- eventually
resulting in a OOM condition. The problem appears to have been corrected
Package: onak
Version: 0.3.2-1
Severity: important
I don't know if this is an actual bug, or just user stupidity. :-) I
haven't done a lot of playing with onak, but decided to exercise it a
little bit by loading it with the debian keyring:
gpg --export --keyring
Package: bind9
Version: 1:9.3.1-2
Severity: important
Bummer. I just updated and find that /usr/sbin/dnssec-makekeyset is
missing, making it very difficult to generate my signed zone files. :-(
Interestingly, although dpkg -L does not show this file is included in
this package, looking at
Package: bacula-sd
Version: 1.36.2-2
Severity: normal
I noticed this change in behavior when I upgraded my system from kernel
2.4.27 to 2.6.10. Attempting to position to the end of data on a tape in
order to append backups no longer works:
unmount
mount
run something
09-May 16:02 hamster-sd:
27 matches
Mail list logo
