Package: postfix
Version: 2.9.6-1
Severity: grave
Justification: renders package unusable
-- System Information:
Debian Release: 7.0
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 3.2.0-4-686-pae (SMP w/2 CPU cores)
Locale:
Package: munin-node
Version: 1.4.5-1
Severity: minor
Tags: lenny
Solution:
s/spesifics/specifics/
-- System Information:
Debian Release: squeeze/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'stable')
Architecture: i386 (i686)
Kernel: Linux 2.6.32-trunk-686 (SMP w/2 CPU
On Mon, 2010-07-19 at 08:37 -0400, Holger Levsen wrote:
tags 589633 - lenny
# 1.4.5-1 is not in lenny
tags 589633 + unreproducable
thanks
Hi Danny,
I cant find that typo:
~/Projects/munin/trunk$ rgrep spesifics .
~/Projects/munin/trunk
~/Projects/munin/squeeze$ rgrep spesifics
Quoting Holger Levsen (hol...@layer-acht.org):
the machine in question ( a firewall) has no mail installed.
So the bug report was made from another machine running sid,
That might have added to the confusion.
I should have made that clear in my description.
But the bug is really there in lenny
Package: xmms
Version: 1:1.2.10+20070601-1
Severity: serious
Justification: unkown
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.21-1-vserver-686 (SMP w/2 CPU cores)
Locale:
build from debian sources: same problem
Enabled -g in the Makefile
Ran the program with gdb:
---
Starting program: /usr/src/procinfo-18/procinfo
Program received signal SIGSEGV, Segmentation fault.
0x00407d3b in first_page (sl=500) at procinfo.c:555
555
Quoting martin f krafft ([EMAIL PROTECTED]):
Certainly not, but are you sure that the arrays weren't degraded
beforehand?
Hmm.. machine rebooted on the 23th..
from kern.log:
May 23 05:50:24 localhost kernel: devfs_mk_dev: could not append to parent for
md/0
May 23 05:50:24 localhost kernel:
Quoting martin f krafft ([EMAIL PROTECTED]):
This is ugly, but only aestethically speaking.
so only a warning !?
You setup looks weird. mdadm.conf contains /dev/md0 and you are
already using /dev/md/d0p6 (partitionable arrays).
How about this one:
usenetgateway (amd64 with scsi controller
Quoting Steve Langasek ([EMAIL PROTECTED]):
Can you tell us what version of mdadm you had installed prior to this?
I just upgraded my machine and this happened:
Preparing to replace mdadm 1.9.0-2.3 (using .../mdadm_1.9.0-3_i386.deb) ...
Stopping RAID monitor daemon: mdadm -F.
Unpacking
Quoting Steve Langasek ([EMAIL PROTECTED]):
Can you tell us what version of mdadm you had installed prior to this?
nope, sorry
it's a pitty that apt/dpkg doesn't write this info to a log file !
I couldn't scroll back for enough!
--
4 questions of life: What is sacred? What is the spirit
Quoting Steve Langasek ([EMAIL PROTECTED]):
tags 310368 = moreinfo unreproducible
severity 310368 important
thanks
I've verified that there is no code path in this package that would cause
/etc/mdadm/mdadm.conf to be removed on upgrade, so I don't really see how
this can be the package's
11 matches
Mail list logo
