Package: mrtg
Version: 2.16.3-3
Severity: grave
Justification: renders package unusable
The upgrade in sid to perl 5.12 renders mrtg unuseable. The error
message you get is the following.
Bareword "P_DETACH" not allowed while "strict subs" in use at
/usr/share/perl5/MRTG_lib.pm line 1181.
Compila
Package: irssi
Version: 0.8.15-3
Severity: normal
As mentioned in the subject, patch "bind_utf8-fix" which was added in
the latest revision, breaks Alt/ESC-UP/DOWN for me. Instead of switching
to the next window it emits a [B or [A. For testing purposes I reverted
the patch and the key combo start
Sorry, the last working version was of course.
1.98+20100804-14. It worked with -9 as well though.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Package: grub-pc
Version: 1.99~rc1-2
Severity: important
With the current version grub-setup fails when trying to install on a
RAID-1 device. Apparently it tries to install on a partition instead of
the disk itself. Here is part of the verbose output
Working: (1.98+20100804-9)
+ /usr/sb
reopen 604774
thanks
I still get compilation errors with the latest version. Apparently this
is caused by not having the complete initial patch applied which also
removes the setting of the LD_LIBRARY_PATH.
SET_CROSS_LIB_PATH =
LD_LIBRARY_PATH=$${LD_LIBRARY_PATH:+$$LD_LIBRARY_PATH:}/$(PF)/$(DEB_
Package: apt-cacher-ng
Version: 0.4.9-2
Severity: normal
I noticed with 0.4.9 (0.4.7-1 is ok ) that the expire-caller.pl script started
to hang each day. Running it manually I saw that it never returned. For
me it looks like the server is not closing the socket correctly so the
script never exits.
Package: grub-pc
Version: 1.98+20100710-1
Severity: normal
Due to recent changes in iterate_devices dpkg-reconfigure grub-pc no
longer shows MD devices for installation. To work around this you can
run grub-install '(md0)' manually.
-- Package-specific info:
*** BEGIN /proc/
On 07 May 10 00:22, Petter Reinholdtsen wrote:
> I see from init.d/.depend.boot that kdb is not considered a
> interactive script by insserv. It is just as if the X-Interactive
> header no longer have any effect. :(
For other packages it seems to work ok (udev).
>
> A workaround for you might be
On 06 May 10 23:17, Petter Reinholdtsen wrote:
> [Michael Guntsche]
> > The header already has this.
>
> OK. Good.
>
> Can you provide the output from /usr/share/insserv/make-testsuite, for
> us to try to reproduce the problem.
>
Attached you'll find the output.
On 06 May 10 23:00, Petter Reinholdtsen wrote:
> Does it help to add "X-Interactive: true" in the LSB header of the kbd
> init.d script? I suspect that is the correct solution to your
> problem. :)
The header already has this.
### BEGIN INIT INFO
# Provides: kbd
# Required-Start:$rem
Package: insserv
Version: 1.14.0-1
Severity: important
Under certain circumstances the kbd init script just hangs during boot. While
Ctrl-C fixes this it is a big problem if you restart a remote server
only to find out that it is no longer reachable.
Since it only started happening recently I had
Package: libc6
Version: 2.10.2-6
Severity: normal
Starting with 2.10.2-7 the powerpc version depends on debconf instead of
Suggests:
This is different from at least i386 which still suggests debconf.
While this is a minor issue for a powerpc system using it in a cross
build chain is a lot more di
Package: maildir-utils
Version: 0.6-1
Severity: normal
As the subject says, mu index -q still outputs a newline character. If
used via cron this yields an empty mail message to the user. I had a
look at it, the problem is at mu-cmd.c:416
g_print("\n);
This just prints a newline character to the
Package: maildir-utils
Version: 0.6~beta1-1
Severity: normal
Tags: patch
Although stated in the manpage the new version does not use ~/Maildir if
it exis but asks for the maildir instead. Looking at the code I
saw that one check was inverted. The following patch fixes this.
--- src/mu-util.c.orig
Package: rpcbind
Version: 0.2.0-2
Severity: important
While rpcbind installs just fine it does not have an init script and so
is not started automatically. Since it is a replacement of portmap it
should also start during bootup.
Furthermore shouldn't it replace/conflict with the portmap
package a
Looking at it some more, I noticed the following.
If i boot up I have /dev/ttyS[23] 0 and 1 is completely missing. If I do
rmmod 8250_pnp;modprobe 8250_pnp ttys1 is created but not 0.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble
Package: udev
Version: 146-4
Severity: normal
I have a system two serial devices where /dev/ttyS0 is connected to a
headless remote machine. After I recently upgraded the kernel to
2.6.31.2 and after reboot I noticed that /dev/ttyS0 was no longer
created while /dev/ttyS1 was. At first I thought th
Package: maildir-utils
Severity: normal
Tags: patch
Use an already existing function to check if -q is used.
--- index/mu-index.c.orig 2008-10-28 22:38:36.0 +0100
+++ index/mu-index.c2009-08-19 19:39:51.0 +0200
@@ -195,8 +195,9 @@
result = run_callback_maybe (dat
Package: maildir-utils
Version: 0.4-2
Severity: normal
Running mu-index with the --quiet/-q option causes an immediate
segfault. Looking at the source I noticed that a NULL-pointer gets
dereferenced.
File index/mu-index.c:199
++data->_stats->_processed;
With -q _stats is set to NULL.
I fixed i
Package: radvd
Version: 1:1.3-1
Severity: normal
The Default-Start entry contains also runlevel "S".
If you install the radvd package with the insserv package already
installed this yields S entries in BOTH rcS.d and rc[2345].
Removing the S entry fixes the problem.
-- System Information:
Debian
On Aug 8, 2009, at 20:49, Michael Meskes wrote:
On Sat, Aug 08, 2009 at 07:56:15PM +0200, Michael Guntsche wrote:
wd_keepalive to Required-Start: in /etc/init.d/watchdog. This makes
sure that it is started before watchdog.
No, this is not the major problem. wd_keepalive has to be started as
On Aug 8, 2009, at 19:20, Michael Meskes wrote:
I reassign the bug to insserv without evaluating insserv
possibilities. If
there is a way so the watchdog package can solve this problem,
please tell me
and reassign back. I don't see one either.
Well, you can add
wd_keepalive to Require
Package: watchdog
Version: 5.6-4
Severity: normal
If insserv with STARTPAR is used the wd_keepalive AND watchdog are
started at the same time.
Normally wd_keepalive should be started early, while the "real" watchdog
daemon starts later on. Now both are started in parallel.
"watchdog" stops "wd_ke
Package: apt-cacher-ng
Version: 0.3.8-1
Severity: normal
The DISABLED flag introduced with #522186 does not work as expected.
The reason for this is that the variable is checked BEFORE the defaults are
read.
test -z "$DISABLED" || exit 0
# Include apt-cacher-ng defaults if available
if [ -f /et
Package: lvm2
Version: 2.02.39-6
Severity: normal
Testing the dependency based boot sequence with insserv I found a minor
issue in the init.d script for lvm2. The "Should-Start" includes "mdadm"
instead of "mdadm-raid" and the Should-Stop does not include
"mdadm-raid" at all. While I did not see a
On Wed, 05 Nov 2008 23:19:41 +0900, Paul Wise <[EMAIL PROTECTED]> wrote:
> Please paste the error output you got. If it was just the WARNING lines
> then that is intentional - the postinst cannot know if you are using an
> initrd but you don't have links in the root directory.
Hello,
I get these
Package: lilo
Version: 1:22.8-6.3
Severity: normal
I have a rather old router that is only using a kernel-image,
which is smaller then 1.2MB and has no initramfs/initrd. Since this
hardware is rather old I did not enable large_memory after the upgrade
to the latest version. The problem is that the
On Wed, 15 Oct 2008 22:58:04 +0100, Mark Hindley <[EMAIL PROTECTED]>
wrote:
> I am afraid I can't reproduce this behaviour (admittedly I have the
> apt-cacher version 1.6.6 which is still to be uploaded. If you want to
> try it and see if it is any better you can get it from
> http://www.hindley
Without libberkeleydb-perl installed "apt-cacher-cleanup.pl" which is run
from a daily cron job also fails to start since it depends on it.
Installing it fixes the problem. I just noticed it today since cron sent me
an error mail.
Kind regards,
Michael
--
To UNSUBSCRIBE, email to [EMAIL PROTE
On Feb 10, 2008, at 17:45, Robert Millan wrote:
GRUB isn't supposed to have a stable ABI. Never use an old
core.img with
a new grub-setup, or for that matter, any combination of core.img,
*.lst,
*.mod and grub-setup where all of them aren't the same version.
It is better to just use gru
Package: grub-pc
Version: 1.96+20080209-1
Severity: important
With build 20080209 grub-setup is no longer able to install on a
lvm root-device.
With the previous version (20080203) it worked.
grub-setup - -r '(fatoftheland-main)' '(hd0)'grub-setup: info:
prefix = /boot/grub
grub-setup: info
Ok, so I took a further look at it and noticed that the problem is
the trailing input/inputx that's added in 2.6.23.
pci:00/:00:1d.0/usb1/1-2/1-2:1.0/input/input6
Everything is ok up to here ---^
input and input6 shouldn't be parsed since we already found the
necessary module
Forgot to attach this to the first report.
This is the input related output of yaird --verbose --test
Input devices:
Power Button (FF) is LNXPWRBN/button/input0 at virtual/input/
input0 [event0,kbd] [KEY,EV] (KBD)
Power Button (CM) is PNP0C0C/button/input0 at virtual/input/
inpu
Package: yaird
Version: 0.0.12-22
Severity: grave
Justification: renders package unusable
I recently installed a 2.6.23 kernel for testing purposes and noticed
that yaird is no longer able to create a valid ramdisk. The errors I get
are
..
yaird error: unrecognised device:
/sys/devices/pci000
Hi,
I also had to enable several modules to get AuthUserFile
authentication working.
* auth_basic
* authz_user
* authn_file
After adding them and reloading apache2 authentication worked as
expected.
Kind regards,
Michael
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of
Package: libapr1
Version: 1.2.7-6
Severity: normal
Apache2 segfaults on startup because libapr1 is compiled with epoll
support, which is not supported by a 2.4 kernel.
Recompiling the package with a 2.4 kernel fixes the problem.
-- System Information:
Debian Release: testing/unstable
APT prefe
to do or change the definition of the PIDFILE definition in /etc/
init.d/fetchmail.
Kind regards,
Michael Guntsche
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
correct pidfile.
Changing the definition to the one in the old version made it work
again.
Kind regards,
Michael Guntsche
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i586)
Shell: /bin/sh linked to /bin/
Package: hylafax-server
Version: 2:4.2.4-1
Severity: normal
I recently upgrade my hylafax setup here. Doing a quick test showed that
the notification after sending a fax no longer works.
I tried
sendfax -R -d
The fax got sent without a problem but I did not get a notification by
mail. Looking
saw that part of the
unicode support was changed, maybe this is the problem.
Kind regards,
Michael Guntsche
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i586)
Shell: /bin/sh linked to /bin/b
Package: isdnlog
Version: 1:3.7.2005-07-09-2
Severity: important
I think this problem is related to the libc6 changes regarding the
malloc checks in recent version. If you send a -SIGHUP or -SIGINT the program
stops with a
*** glibc detected *** free(): invalid pointer: 0x40019000 ***.
So there
I downloaded 3.0.20 from the main samba server, compiled it and did a
quick test.
The new version seems to have fixed this problem.
Kind regards,
Mike
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
I had a look at this problem again and surfed through the python-dev ML
archives.
Since the current development effort is in a kind of flux there doesn't
seem to be a lot of bugfixing going on right now. Watching a particular
thread I found the following patches though.
http://www.dscpl.com.au/
I think I am having a similar problem with the latest version although
not directly related to the "persist" option.
I use the "demand" option to bring up the interface in question when
needed and kill it after there was no outbound traffic for 5 minutes.
Sometimes the connection wouldnt succeed
Some more information.
I used c2faxsend and c2faxrecv in HylaFax mode and got this on the
c2faxsend side.
SESSION BEGIN 0004 +43.xxx
SEND FAX: JOB 4 DEST COMMID 0167
Try to connect to fax number in Hylafax mode on controller 1.
Dial and starting transfer of TIFF-File docq/d
Package: capi4hylafax
Version: 1:01.02.03-7
Severity: important
Starting with version 01.02.03-8 of this package I am no longer able do
recieve faxes.
Running c2faxrecv from the terminal with "c2faxrecv -v -f TIFF" I see
the following with version-7
-
Device "faxCAPI" uses 2 receive thread(
Ok, I think I found out what's causing this problem.
Function "setactivefilter" in options.c seems to be the problem.
<..>
int ret = 0;
pc = pcap_open_dead(DLT_PPP_WITHDIRECTION, 65535);
if (pcap_compile(pc, &active_filter, *argv, 1, netmask) == -1) {
option_error("error in active-filter
Package: ppp
Version: 2.4.3-20041231+2
Severity: important
Hi,
I upgraded ppp to the latest version today (2.4.3) and found out that I
wasn't able to start it with "pon" or via "ifup".
So I tried starting it from the command-line with "pppd call provider".
Still didn't work.
Stracing it I found
48 matches
Mail list logo
