Processed: Re: Bug#416098: kills my server on install
Processing commands for [EMAIL PROTECTED]: reassign 416098 linux-image-2.6.18-4-amd64 Bug#416098: kills my server on install Bug reassigned from package `munin-node' to `linux-image-2.6.18-4-amd64'. retitle 416098 MegaRAID SAS adapter locks up Bug#416098: kills my server on install Changed Bug title to MegaRAID SAS adapter locks up from kills my server on install. quit Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#416098: kills my server on install
reassign 416098 linux-image-2.6.18-4-amd64 retitle 416098 MegaRAID SAS adapter locks up quit * Steinar H. Gunderson I'm unsure if this is a munin bug or a kernel bug; I'm filing against munin, but it should perhaps be reassigned. I installed munin on a Dell PowerEdge 2950: Setting up munin-node (1.2.5-1) ... Initializing plugins.. At this point, ssh froze. I connected through the remote admin console, which was filled with messages like: megasas: [65] waiting for 140 requests to complete megasas: [70] waiting for 140 commands to complete megasas: [75] waiting for 140 commands to complete megasas: [80] waiting for 140 commands to complete I googled this error message and it seems a lot of people have seen lockups with this SAS adapter (without there being any mention of Munin). Unless you can reproduce this I agree with Stephen that the kernel (or hardware) is at the prime suspect, and that it happened during a Munin installation was just random chance. Therefore I'm reassigning the bug. To repeat the step the init script did at the time of the crash, you run the following command: munin-node-configure --shell --debug | sh -x That does the same, but with more debug information. The server never recovered, and I had to (remote) reset it. In other words, some plugin in munin-node kills the megasas driver, which in turn kills the entire server. Well, I'm not aware of any plugins that could possibly do this. The only plugins I know that are run with elevated privileges and that have something to do with block devices is smart_ and hddtemp_smartctl, but they both rely on the helper program smartctl so the bug has would have had to be in that program anyway. * Stephen Gran Disclaimer: I am not a munin maintainer. Would you like to be? :-) I really need a comaintainer or for someone to take over the package completely - way too little free time these days. Regards -- Tore Anderson -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: severity of 416098 is important
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.10.1 severity 416098 important Bug#416098: MegaRAID SAS adapter locks up Severity set to `important' from `grave' End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: notfound 416146 in 71
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.10.1 notfound 416146 71 Bug#416146: postgresql-common: missing /var/lib/postgresql Bug#416228: fails to install - chown: cannot access `/var/lib/postgresql' Bug marked as not found in version 71. End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: [bts-link] source package upx-ucl-beta
Processing commands for [EMAIL PROTECTED]: # # bts-link upstream status pull for source package upx-ucl-beta # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # user [EMAIL PROTECTED] Setting user to [EMAIL PROTECTED] (was [EMAIL PROTECTED]). # remote status report for #409719 # * http://sourceforge.net/tracker/?func=detailatid=102331aid=1673616group_id=2331 # * remote status changed: Pending - Closed # * closed upstream tags 409719 + fixed-upstream Bug#409719: upx-ucl-beta_1:2.92-1(hppa/experimental): FTBFS: #error ACC_ABI_ENDIAN There were no tags set. Tags added: fixed-upstream usertags 409719 - status-Pending Bug#409719: upx-ucl-beta_1:2.92-1(hppa/experimental): FTBFS: #error ACC_ABI_ENDIAN Usertags were: status-Pending. Usertags are now: . usertags 409719 + status-Closed Bug#409719: upx-ucl-beta_1:2.92-1(hppa/experimental): FTBFS: #error ACC_ABI_ENDIAN There were no usertags set. Usertags are now: status-Closed. thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: [bts-link] source package mhash
Processing commands for [EMAIL PROTECTED]: # # bts-link upstream status pull for source package mhash # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # user [EMAIL PROTECTED] Setting user to [EMAIL PROTECTED] (was [EMAIL PROTECTED]). # remote status report for #350088 # * http://sourceforge.net/tracker/?func=detailatid=104286aid=1449417group_id=4286 # * remote status changed: Open - Closed # * closed upstream tags 350088 + fixed-upstream Bug#350088: libmhash2: crc32 segfaults on big endian machines There were no tags set. Tags added: fixed-upstream usertags 350088 - status-Open Bug#350088: libmhash2: crc32 segfaults on big endian machines Usertags were: status-Open resolution-Accepted. Usertags are now: resolution-Accepted. usertags 350088 + status-Closed Bug#350088: libmhash2: crc32 segfaults on big endian machines Usertags were: resolution-Accepted. Usertags are now: resolution-Accepted status-Closed. thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#413311: marked as done (linux-image-2.6.18-4-686: Install routine fails due to readlink error)
Your message dated Mon, 26 Mar 2007 09:17:28 + with message-id [EMAIL PROTECTED] and subject line Bug#413311: fixed in linux-2.6 2.6.18.dfsg.1-12 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) ---BeginMessage--- Package: linux-image-2.6.18-4-686 Version: 2.6.18.dfsg.1-11 Severity: grave Justification: renders package unusable Attempting to do an upgrade produces the following error: Setting up linux-image-2.6.18-4-686 (2.6.18.dfsg.1-11) ... Running depmod. Finding valid ramdisk creators. Using mkinitrd.yaird to build the ramdisk. readlink: invalid option -- m Try `readlink --help' for more information. readlink: invalid option -- m Try `readlink --help' for more information. Failed to symbolic-link initrd.img-2.6.18-4-686 to initrd.img. dpkg: error processing linux-image-2.6.18-4-686 (--configure): subprocess post-installation script returned error exit status 17 Errors were encountered while processing: linux-image-2.6.18-4-686 E: Sub-process /usr/bin/dpkg returned an error code (1) A package failed to install. Trying to recover: A quick check of the man page for readlink does indeed show that there is no such option. So, the kernel install is left in a partial state, and attempting to remove linux-image-2.6.18-4-686 with aptitude attempts to remove other packages as well, such as linux-image-686. -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.18-4-686 Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) Versions of packages linux-image-2.6.18-4-686 depends on: ii coreutils 5.2.1-2The GNU core utilities ii debconf [debconf-2.0] 1.4.30.13 Debian configuration management sy ii module-init-tools 3.2-pre1-2 tools for managing Linux kernel mo ii yaird [linux-initramfs-tool] 0.0.12-18 Yet Another mkInitRD -- debconf information: linux-image-2.6.18-4-686/preinst/failed-to-move-modules-2.6.18-4-686: linux-image-2.6.18-4-686/preinst/lilo-initrd-2.6.18-4-686: true linux-image-2.6.18-4-686/preinst/elilo-initrd-2.6.18-4-686: true linux-image-2.6.18-4-686/preinst/overwriting-modules-2.6.18-4-686: true linux-image-2.6.18-4-686/prerm/removing-running-kernel-2.6.18-4-686: true linux-image-2.6.18-4-686/prerm/would-invalidate-boot-loader-2.6.18-4-686: true linux-image-2.6.18-4-686/postinst/bootloader-test-error-2.6.18-4-686: linux-image-2.6.18-4-686/preinst/abort-overwrite-2.6.18-4-686: linux-image-2.6.18-4-686/postinst/old-system-map-link-2.6.18-4-686: true linux-image-2.6.18-4-686/postinst/depmod-error-2.6.18-4-686: false linux-image-2.6.18-4-686/preinst/abort-install-2.6.18-4-686: linux-image-2.6.18-4-686/postinst/depmod-error-initrd-2.6.18-4-686: false linux-image-2.6.18-4-686/postinst/old-initrd-link-2.6.18-4-686: true linux-image-2.6.18-4-686/preinst/bootloader-initrd-2.6.18-4-686: true * linux-image-2.6.18-4-686/preinst/already-running-this-2.6.18-4-686: linux-image-2.6.18-4-686/postinst/old-dir-initrd-link-2.6.18-4-686: true linux-image-2.6.18-4-686/postinst/kimage-is-a-directory: shared/kernel-image/really-run-bootloader: true linux-image-2.6.18-4-686/preinst/lilo-has-ramdisk: linux-image-2.6.18-4-686/postinst/bootloader-error-2.6.18-4-686: linux-image-2.6.18-4-686/preinst/initrd-2.6.18-4-686: linux-image-2.6.18-4-686/postinst/create-kimage-link-2.6.18-4-686: true ---End Message--- ---BeginMessage--- Source: linux-2.6 Source-Version: 2.6.18.dfsg.1-12 We believe that the bug you reported is fixed in the latest version of linux-2.6, which is due to be installed in the Debian FTP archive: linux-2.6_2.6.18.dfsg.1-12.diff.gz to pool/main/l/linux-2.6/linux-2.6_2.6.18.dfsg.1-12.diff.gz linux-2.6_2.6.18.dfsg.1-12.dsc to pool/main/l/linux-2.6/linux-2.6_2.6.18.dfsg.1-12.dsc linux-doc-2.6.18_2.6.18.dfsg.1-12_all.deb to pool/main/l/linux-2.6/linux-doc-2.6.18_2.6.18.dfsg.1-12_all.deb linux-headers-2.6.18-4-all-powerpc_2.6.18.dfsg.1-12_powerpc.deb to pool/main/l/linux-2.6/linux-headers-2.6.18-4-all-powerpc_2.6.18.dfsg.1-12_powerpc.deb linux-headers-2.6.18-4-all_2.6.18.dfsg.1-12_powerpc.deb to pool/main/l/linux-2.6/linux-headers-2.6.18-4-all_2.6.18.dfsg.1-12_powerpc.deb linux-headers-2.6.18-4-powerpc-miboot_2.6.18.dfsg.1-12_powerpc.deb to pool/main/l/linux-2.6/linux-headers-2.6.18-4-powerpc-miboot_2.6.18.dfsg.1-12_powerpc.deb
Bug#412143: marked as done (linux-2.6 - vserver patch allows renice of processes in different context)
Your message dated Mon, 26 Mar 2007 09:17:28 +
with message-id [EMAIL PROTECTED]
and subject line Bug#412143: fixed in linux-2.6 2.6.18.dfsg.1-12
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
---BeginMessage---
Package: linux-2.6
Version: 2.6.18.dfsg.1-11
Severity: serious
Tags: security patch
User: debian-kernel@lists.debian.org
Usertags: dkt-waiting-etch-security-update
The included version of the vserver patch allows contexts to renice
processes in other contexts. See patch.
diff -NurpP linux-2.6.19.3-vs2.2.0-rc13.3/kernel/pid.c
linux-2.6.19.3-vs2.2.0-rc13.4/kernel/pid.c
--- linux-2.6.19.3-vs2.2.0-rc13.3/kernel/pid.c 2006-12-04 01:47:02 +0100
+++ linux-2.6.19.3-vs2.2.0-rc13.4/kernel/pid.c 2007-02-23 00:30:28 +0100
@@ -286,6 +286,9 @@ void fastcall transfer_pid(struct task_s
struct task_struct * fastcall pid_task(struct pid *pid, enum pid_type type)
{
struct task_struct *result = NULL;
+
+ if (type == PIDTYPE_REALPID)
+ type = PIDTYPE_PID;
if (pid) {
struct hlist_node *first;
first = rcu_dereference(pid-tasks[type].first);
@@ -300,11 +303,17 @@ struct task_struct * fastcall pid_task(s
*/
struct task_struct *find_task_by_pid_type(int type, int nr)
{
+ struct task_struct *task;
+
if (type == PIDTYPE_PID)
nr = vx_rmap_pid(nr);
- else if (type == PIDTYPE_REALPID)
- type = PIDTYPE_PID;
- return pid_task(find_pid(nr), type);
+
+ task = pid_task(find_pid(nr), type);
+ if (task (type != PIDTYPE_REALPID)
+ /* maybe VS_WATCH_P in the future? */
+ !vx_check(task-xid, VS_WATCH|VS_IDENT))
+ return NULL;
+ return task;
}
EXPORT_SYMBOL(find_task_by_pid_type);
diff -NurpP linux-2.6.19.3-vs2.2.0-rc13.3.1/include/linux/pid.h
linux-2.6.19.3-vs2.2.0-rc13.4/include/linux/pid.h
--- linux-2.6.19.3-vs2.2.0-rc13.3.1/include/linux/pid.h 2006-11-08 04:57:52
+0100
+++ linux-2.6.19.3-vs2.2.0-rc13.4/include/linux/pid.h 2007-02-22 18:09:39
+0100
@@ -105,7 +105,8 @@ static inline pid_t pid_nr(struct pid *p
struct pid *pid___ = find_pid(who); \
if (pid___ != NULL) \
hlist_for_each_entry_rcu((task), pos___,\
- pid___-tasks[type], pids[type].node) {
+ pid___-tasks[type], pids[type].node) \
+ if (vx_check((task)-xid, VS_WATCH_P|VS_IDENT)) {
#define while_each_task_pid(who, type, task) \
} \
@@ -124,7 +124,8 @@ static inline pid_t pid_nr(struct pid *p
struct hlist_node *pos___; \
if (pid != NULL)\
hlist_for_each_entry_rcu((task), pos___,\
- pid-tasks[type], pids[type].node) {
+ pid-tasks[type], pids[type].node) \
+ if (vx_check((task)-xid, VS_WATCH_P|VS_IDENT)) {
#define while_each_pid_task(pid, type, task) \
} \
Bastian
--
Power is danger.
-- The Centurion, Balance of Terror, stardate 1709.2
---End Message---
---BeginMessage---
Source: linux-2.6
Source-Version: 2.6.18.dfsg.1-12
We believe that the bug you reported is fixed in the latest version of
linux-2.6, which is due to be installed in the Debian FTP archive:
linux-2.6_2.6.18.dfsg.1-12.diff.gz
to pool/main/l/linux-2.6/linux-2.6_2.6.18.dfsg.1-12.diff.gz
linux-2.6_2.6.18.dfsg.1-12.dsc
to pool/main/l/linux-2.6/linux-2.6_2.6.18.dfsg.1-12.dsc
linux-doc-2.6.18_2.6.18.dfsg.1-12_all.deb
to pool/main/l/linux-2.6/linux-doc-2.6.18_2.6.18.dfsg.1-12_all.deb
linux-headers-2.6.18-4-all-powerpc_2.6.18.dfsg.1-12_powerpc.deb
to
pool/main/l/linux-2.6/linux-headers-2.6.18-4-all-powerpc_2.6.18.dfsg.1-12_powerpc.deb
linux-headers-2.6.18-4-all_2.6.18.dfsg.1-12_powerpc.deb
to
pool/main/l/linux-2.6/linux-headers-2.6.18-4-all_2.6.18.dfsg.1-12_powerpc.deb
linux-headers-2.6.18-4-powerpc-miboot_2.6.18.dfsg.1-12_powerpc.deb
to
pool/main/l/linux-2.6/linux-headers-2.6.18-4-powerpc-miboot_2.6.18.dfsg.1-12_powerpc.deb
linux-headers-2.6.18-4-powerpc-smp_2.6.18.dfsg.1-12_powerpc.deb
to
Bug#398470: marked as done (key serial number collision (CVE-2007-0006))
Your message dated Mon, 26 Mar 2007 09:17:27 + with message-id [EMAIL PROTECTED] and subject line Bug#398470: fixed in linux-2.6 2.6.18.dfsg.1-12 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) ---BeginMessage--- Package: linux-image-2.6.18-1-686 Version: 2.6.18-3 While running some not-very-intensive upload tasks via samba (this server being the recipient of the data), I got the following two oopses: Nov 11 04:18:47 dearing kernel: BUG: unable to handle kernel paging request at virtual address 00100104 Nov 11 04:18:47 dearing kernel: printing eip: Nov 11 04:18:47 dearing kernel: c0196a22 Nov 11 04:18:47 dearing kernel: *pde = Nov 11 04:18:47 dearing kernel: Oops: 0002 [#1] Nov 11 04:18:47 dearing kernel: SMP Nov 11 04:18:47 dearing kernel: Modules linked in: reiserfs drbd ipv6 button ac battery loop tsdev sg e752x_edac intel_rng edac_mc shpchp pci_hotplug psmouse floppy serio_ra w evdev pcspkr rtc ext3 jbd mbcache dm_mirror dm_snapshot dm_mod raid1 md_mod ide_generic sd_mod ide_cd cdrom piix generic ide_core mptspi mptscsih mptbase scsi_transport_sp i uhci_hcd ehci_hcd usbcore scsi_mod e1000 thermal processor fan Nov 11 04:18:47 dearing kernel: CPU:0 Nov 11 04:18:47 dearing kernel: EIP:0060:[c0196a22]Not tainted VLI Nov 11 04:18:47 dearing kernel: EFLAGS: 00010217 (2.6.18-1-686 #1) Nov 11 04:18:47 dearing kernel: EIP is at keyring_destroy+0x27/0x77 Nov 11 04:18:47 dearing kernel: eax: 00200200 ebx: d7d29240 ecx: d7d2928c edx: 00100100 Nov 11 04:18:47 dearing kernel: esi: d7d29248 edi: dfa31380 ebp: 0296 esp: dfa5bf58 Nov 11 04:18:47 dearing kernel: ds: 007b es: 007b ss: 0068 Nov 11 04:18:47 dearing kernel: Process events/0 (pid: 10, ti=dfa5a000 task=dffefaa0 task.ti=dfa5a000) Nov 11 04:18:47 dearing kernel: Stack: d7d29240 d7d29248 dfa31380 0296 c019656e c02d1840 c02d1844 c012ac34 Nov 11 04:18:47 dearing kernel:c01964bd dfa31394 dfa31380 dfa3138c c012b51e 0001 Nov 11 04:18:47 dearing kernel: dfa81f3c 0001 dffefaa0 c011777c 00100100 Nov 11 04:18:47 dearing kernel: Call Trace: Nov 11 04:18:47 dearing kernel: [c019656e] key_cleanup+0xb1/0xca Nov 11 04:18:47 dearing kernel: [c012ac34] run_workqueue+0x78/0xb5 Nov 11 04:18:47 dearing kernel: [c01964bd] key_cleanup+0x0/0xca Nov 11 04:18:47 dearing kernel: [c012b51e] worker_thread+0xd9/0x10b Nov 11 04:18:47 dearing kernel: [c011777c] default_wake_function+0x0/0xc Nov 11 04:18:47 dearing kernel: [c012b445] worker_thread+0x0/0x10b Nov 11 04:18:47 dearing kernel: [c012d897] kthread+0xc2/0xef Nov 11 04:18:47 dearing kernel: [c012d7d5] kthread+0x0/0xef Nov 11 04:18:47 dearing kernel: [c0101005] kernel_thread_helper+0x5/0xb Nov 11 04:18:47 dearing kernel: Code: 4e 04 fc ff 55 57 56 53 89 c3 83 78 48 00 74 39 b8 b0 18 2d c0 e8 ef a4 0e 00 8b 53 4c 85 d2 74 1d 8d 4b 4c 39 ca 74 16 8b 41 04 89 4 2 04 89 10 c7 41 04 00 02 20 00 c7 43 4c 00 01 10 00 f0 81 Nov 11 04:18:47 dearing kernel: EIP: [c0196a22] keyring_destroy+0x27/0x77 SS:ESP 0068:dfa5bf58 Nov 11 04:20:03 dearing kernel: 1BUG: unable to handle kernel NULL pointer dereference at virtual address 0008 Nov 11 04:20:03 dearing kernel: printing eip: Nov 11 04:20:03 dearing kernel: c01b8f64 Nov 11 04:20:03 dearing kernel: *pde = Nov 11 04:20:03 dearing kernel: Oops: [#2] Nov 11 04:20:03 dearing kernel: SMP Nov 11 04:20:03 dearing kernel: Modules linked in: reiserfs drbd ipv6 button ac battery loop tsdev sg e752x_edac intel_rng edac_mc shpchp pci_hotplug psmouse floppy serio_ra w evdev pcspkr rtc ext3 jbd mbcache dm_mirror dm_snapshot dm_mod raid1 md_mod ide_generic sd_mod ide_cd cdrom piix generic ide_core mptspi mptscsih mptbase scsi_transport_sp i uhci_hcd ehci_hcd usbcore scsi_mod e1000 thermal processor fan Nov 11 04:20:03 dearing kernel: CPU:3 Nov 11 04:20:03 dearing kernel: EIP:0060:[c01b8f64]Not tainted VLI Nov 11 04:20:03 dearing kernel: EFLAGS: 00010286 (2.6.18-1-686 #1) Nov 11 04:20:03 dearing kernel: EIP is at __rb_rotate_left+0xc/0x50 Nov 11 04:20:03 dearing kernel: eax: d7d29ac8 ebx: d7d29ac8 ecx: d7d29248 edx: Nov 11 04:20:03 dearing kernel: esi: dfb31e48 edi: c0377580 ebp: esp: c9949ec8 Nov 11 04:20:03 dearing kernel: ds: 007b es: 007b ss: 0068 Nov 11 04:20:03 dearing kernel: Process smbd (pid: 27308, ti=c9948000 task=e255c000 task.ti=c9948000) Nov 11 04:20:03 dearing kernel: Stack: d7d29248 d7d29ac8 dfb317c8 c01b9084
Bug#415112: marked as done (linux-image-2.6.18-4-amd64: kernel oops in keyring_destroy)
Your message dated Mon, 26 Mar 2007 09:17:27 + with message-id [EMAIL PROTECTED] and subject line Bug#398470: fixed in linux-2.6 2.6.18.dfsg.1-12 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) ---BeginMessage--- Package: linux-image-2.6.18-4-amd64 Version: 2.6.18.dfsg.1-11 Severity: important Hi, I'm running kernel 2.6.18-4-amd64 on a FujitsuSiemens RX 400 computer, equipped with 8 GB RAM. The computer is used as our file server and unfortunately, it crashed two times this week with the following kernel oops (a full dmesg output is available at ( http://www-ds.e-technik.uni-dortmund.de/~jplatte/dmesg.txt ) Unable to handle kernel paging request at 00100108 RIP: [802ec036] keyring_destroy+0x32/0x96 After posting this bug on LKML I got a reply stating that this bug is already known and a fix is available: http://bugzilla.kernel.org/show_bug.cgi?id=8067 http://bugzilla.kernel.org/show_bug.cgi?id=7727 After the oops the computer is mostly unusable, for example samba is unable to handle any requests and it is unable to shut down and reboot properly. Therefore I'm marking this bug important. -- System Information: Debian Release: 4.0 APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-4-amd64 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Versions of packages linux-image-2.6.18-4-amd64 depends on: ii coreutil 5.97-5.3The GNU core utilities ii debconf 1.5.11 Debian configuration management sy ii e2fsprog 1.39+1.40-WIP-2006.11.14+dfsg-2 ext2 file system utilities and lib ii initramf 0.85f tools for generating an initramfs ii module-i 3.3-pre4-2 tools for managing Linux kernel mo linux-image-2.6.18-4-amd64 recommends no packages. -- debconf information: linux-image-2.6.18-4-amd64/postinst/kimage-is-a-directory: linux-image-2.6.18-4-amd64/postinst/bootloader-test-error-2.6.18-4-amd64: shared/kernel-image/really-run-bootloader: true linux-image-2.6.18-4-amd64/preinst/lilo-initrd-2.6.18-4-amd64: true linux-image-2.6.18-4-amd64/preinst/initrd-2.6.18-4-amd64: linux-image-2.6.18-4-amd64/preinst/abort-overwrite-2.6.18-4-amd64: linux-image-2.6.18-4-amd64/preinst/failed-to-move-modules-2.6.18-4-amd64: linux-image-2.6.18-4-amd64/postinst/old-initrd-link-2.6.18-4-amd64: true linux-image-2.6.18-4-amd64/postinst/depmod-error-initrd-2.6.18-4-amd64: false linux-image-2.6.18-4-amd64/postinst/create-kimage-link-2.6.18-4-amd64: true linux-image-2.6.18-4-amd64/preinst/lilo-has-ramdisk: linux-image-2.6.18-4-amd64/postinst/old-dir-initrd-link-2.6.18-4-amd64: true linux-image-2.6.18-4-amd64/postinst/depmod-error-2.6.18-4-amd64: false linux-image-2.6.18-4-amd64/prerm/removing-running-kernel-2.6.18-4-amd64: true linux-image-2.6.18-4-amd64/postinst/bootloader-error-2.6.18-4-amd64: linux-image-2.6.18-4-amd64/postinst/old-system-map-link-2.6.18-4-amd64: true linux-image-2.6.18-4-amd64/preinst/already-running-this-2.6.18-4-amd64: linux-image-2.6.18-4-amd64/preinst/bootloader-initrd-2.6.18-4-amd64: true linux-image-2.6.18-4-amd64/preinst/overwriting-modules-2.6.18-4-amd64: true linux-image-2.6.18-4-amd64/preinst/elilo-initrd-2.6.18-4-amd64: true linux-image-2.6.18-4-amd64/preinst/abort-install-2.6.18-4-amd64: linux-image-2.6.18-4-amd64/prerm/would-invalidate-boot-loader-2.6.18-4-amd64: true ---End Message--- ---BeginMessage--- Source: linux-2.6 Source-Version: 2.6.18.dfsg.1-12 We believe that the bug you reported is fixed in the latest version of linux-2.6, which is due to be installed in the Debian FTP archive: linux-2.6_2.6.18.dfsg.1-12.diff.gz to pool/main/l/linux-2.6/linux-2.6_2.6.18.dfsg.1-12.diff.gz linux-2.6_2.6.18.dfsg.1-12.dsc to pool/main/l/linux-2.6/linux-2.6_2.6.18.dfsg.1-12.dsc linux-doc-2.6.18_2.6.18.dfsg.1-12_all.deb to pool/main/l/linux-2.6/linux-doc-2.6.18_2.6.18.dfsg.1-12_all.deb linux-headers-2.6.18-4-all-powerpc_2.6.18.dfsg.1-12_powerpc.deb to pool/main/l/linux-2.6/linux-headers-2.6.18-4-all-powerpc_2.6.18.dfsg.1-12_powerpc.deb linux-headers-2.6.18-4-all_2.6.18.dfsg.1-12_powerpc.deb to pool/main/l/linux-2.6/linux-headers-2.6.18-4-all_2.6.18.dfsg.1-12_powerpc.deb linux-headers-2.6.18-4-powerpc-miboot_2.6.18.dfsg.1-12_powerpc.deb to pool/main/l/linux-2.6/linux-headers-2.6.18-4-powerpc-miboot_2.6.18.dfsg.1-12_powerpc.deb
Bug#407171: proxy stops working after upgrading from sarge
Peter Samuelson [EMAIL PROTECTED] wrote: I think I've fixed this for the next upload (to be done in the next day or two - I'm away from home but I'll still try), and I consider it a release-critical upgrade issue, so I hope the release managers will allow it into etch. Any news on this? A patch maybe or a tip how you intend to solve it, so that someone else can start testing, and NMU in case you won't find time? Regards, Frank -- Dr. Frank Küster Single Molecule Spectroscopy, Protein Folding @ Inst. f. Biochemie, Univ. Zürich Debian Developer (teTeX/TeXLive)
Processed: kaddressbook: Looses all kontacts when shutting down
Processing commands for [EMAIL PROTECTED]: found 349316 4:3.5.6.dfsg.1-1 Bug#349316: kaddressbook: Looses all kontacts when shutting down Bug marked as found in version 4:3.5.6.dfsg.1-1. thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#349316: kaddressbook: Looses all kontacts when shutting down
found 349316 4:3.5.6.dfsg.1-1 thanks I seem to have hit this, or a similar bug (again). It happens with contacts located on a slow NFS server. When I shut down the KDE session I see a progress dialog indicating that the address book is being written. The progress indicator is at zero and gets interrupted by the logout process quickly. The address book file gets truncated to length zero. Previously I had this problem with a remote address book on an SSH connection. Marcus -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#416146: postgresql-common: Cannot work with /var/lib/posgresql a symlink
Package: postgresql-common Version: 72 Followup-For: Bug #416146 I have a symplink for /var/lib/postgresql to another disk. The upgrade keeps removing it, and I do not dare making it work on another directory. -- System Information: Debian Release: 4.0 APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-4-k7 Locale: LANG=C, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Versions of packages postgresql-common depends on: ii adduser 3.102 Add and remove users and groups ii debconf [debconf-2.0] 1.5.13 Debian configuration management sy ii lsb-base 3.1-23.1 Linux Standard Base 3.1 init scrip ii postgresql-client-common 72 manager for multiple PostgreSQL cl ii procps1:3.2.7-3 /proc file system utilities ii ssl-cert 1.0.14 Simple debconf wrapper for openssl postgresql-common recommends no packages. -- debconf information: postgresql-common/obsolete-major: postgresql-common/untransitioned: -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#414857: zoneminder_1.22.3-4(ia64/unstable): FTBFS: arch-specific struct sigcontext fields
Hello. You should probably add the --disable-crashtrace option to the configure line for archs other than amd64 and i386. Best regards, Mateusz Skowroński
Processed: tagging 415393
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.10.1 tags 415393 + help Bug#415393: uim: is not upgradable from uim 1.2 Tags were: experimental Tags added: help End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#414857: zoneminder_1.22.3-4(ia64/unstable): FTBFS: arch-specific struct sigcontext fields
Hello.
The attached patch contains the fix for build problems on archs other
than i386 and amd64.
Best regards,
Mateusz Skowroński
--- ZoneMinder-1.22.3/debian/rules 2007-03-26 16:31:35.0 +0200
+++ ZoneMinder-1.22.3.fix/debian/rules 2007-03-26 16:34:45.0 +0200
@@ -13,10 +13,30 @@
# from having to guess our platform (since we know it already)
DEB_HOST_GNU_TYPE ?= $(shell dpkg-architecture -qDEB_HOST_GNU_TYPE)
DEB_BUILD_GNU_TYPE ?= $(shell dpkg-architecture -qDEB_BUILD_GNU_TYPE)
+DEB_BUILD_ARCH ?= $(shell dpkg-architecture -qDEB_BUILD_ARCH)
CFLAGS = -Wall -g
CXXFLAGS = -DZM_FFMPEG_CVS
+CONFIGURE_OPTS = \
+ --host=$(DEB_HOST_GNU_TYPE) \
+ --build=$(DEB_BUILD_GNU_TYPE) \
+ --sysconfdir=/etc/zm \
+ --prefix=/usr \
+ --mandir=\$${prefix}/share/man \
+ --infodir=\$${prefix}/share/info \
+ --with-mysql=/usr \
+ --with-webdir=/usr/share/zoneminder \
+ --with-cgidir=/usr/lib/cgi-bin \
+ --with-webuser=www-data \
+ --with-webgroup=www-data
+
+ifneq ($(DEB_BUILD_ARCH), i386)
+ifneq ($(DEB_BUILD_ARCH), amd64)
+ CONFIGURE_OPTS += --disable-crashtrace
+endif
+endif
+
ifneq (,$(findstring noopt,$(DEB_BUILD_OPTIONS)))
CFLAGS += -O0
else
@@ -26,7 +46,7 @@
config.status: patch configure
dh_testdir
# Add here commands to configure the package.
- CFLAGS=$(CFLAGS) CXXFLAGS=$(CXXFLAGS) ./configure --host=$(DEB_HOST_GNU_TYPE) --build=$(DEB_BUILD_GNU_TYPE) --sysconfdir=/etc/zm --prefix=/usr --mandir=\$${prefix}/share/man --infodir=\$${prefix}/share/info --with-mysql=/usr --with-webdir=/usr/share/zoneminder --with-cgidir=/usr/lib/cgi-bin --with-webuser=www-data --with-webgroup=www-data
+ CFLAGS=$(CFLAGS) CXXFLAGS=$(CXXFLAGS) ./configure $(CONFIGURE_OPTS)
#perl zmconfig.pl -noi
build: build-stamp
Bug#349316: kaddressbook: Looses all kontacts when shutting down
reopen 349316 thanks I suspect that my problem is caused or initiated by kmail. I saw such a progress dialog where the source file looked like /tmp/*kmail* (as a pattern, not verbatim). pgpwxkpKD5JY2.pgp Description: PGP signature
Processed: kaddressbook: Looses all kontacts when shutting down
Processing commands for [EMAIL PROTECTED]: reopen 349316 Bug#349316: kaddressbook: Looses all kontacts when shutting down Bug reopened, originator not changed. thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#416287: gaim-encryption: fails to handshake with newer versions of gaim
Package: gaim-encryption
Version: 3.0~beta7-1
Severity: serious
Tags: patch
Due to changes in protocol strings between gaim 2.0b5 and 2.0b6,
gaim-encryption will not communicate with users with the higher gaim
version (such as other distros, windows, etc). We discussed this back in the
end of January but I failed to follow up, you have my appologies.
This is the only code change between this upstream version
and the latest (though there are autoconf and PO updates, assumably
automatically generated). I've attached the relevent diff, but it may be
better to upload a new version.
If I don't hear back, I plan to upload an NMU to the delayed queue tonight or
tommorow.
Regards,
Benjamin
-- System Information:
Debian Release: 4.0
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-4-amd64
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Versions of packages gaim-encryption depends on:
ii gaim1:2.0.0+beta5-11 multi-protocol instant messaging c
ii libc6 2.3.6.ds1-13 GNU C Library: Shared libraries
ii libnspr4-0d 1.8.0.10-3 NetScape Portable Runtime Library
ii libnss3-0d 1.8.0.10-3 Network Security Service libraries
gaim-encryption recommends no packages.
-- no debconf information
--- gaim-encryption-3.0beta7/encrypt.c 2006-10-22 22:09:30.0 -0400
+++ gaim-encryption-3.0beta8/encrypt.c 2007-01-28 21:29:56.0 -0500
@@ -633,6 +633,8 @@
} else { /* No encrypt-o-header */
GE_set_rx_encryption(conv, FALSE);
gaim_debug(GAIM_DEBUG_MISC, gaim-encryption, No header: %s\n, *message);
+ gaim_debug(GAIM_DEBUG_MISC, gaim-encryption,
+Proto '%s', header should be: %s\n, gaim_account_get_protocol_id(acct), header);
strip_crypto_smiley(*message);
}
}
@@ -1124,6 +1126,13 @@
g_hash_table_insert(notify_table, g_strdup(prpl-oscar),
g_strdup(A HREF=\Gaim-Encryption Capable\/A));
+ g_hash_table_insert(header_table, g_strdup(prpl-aim),
+ g_strdup(*** Encrypted with the Gaim-Encryption plugin A HREF=\));
+ g_hash_table_insert(footer_table, g_strdup(prpl-aim),
+ g_strdup(\/A));
+ g_hash_table_insert(notify_table, g_strdup(prpl-aim),
+ g_strdup(A HREF=\Gaim-Encryption Capable\/A));
+
/* If jabber stops stripping HTML, we can go back to these headers */
/*g_hash_table_insert(header_table, g_strdup(prpl-jabber), */
/*g_strdup(*** Encrypted with the Gaim-Encryption plugin A HREF=')); */
Bug#407171: proxy stops working after upgrading from sarge
[Frank Küster] Any news on this? A patch maybe or a tip how you intend to solve it, so that someone else can start testing, and NMU in case you won't find time? My work in progress can be seen at: svn diff -c303 svn://svn.debian.org/pkg-apache/branches/etch-apache2 I still have to do something about #416231 before uploading, and I'm also still trying to figure out exactly which modules need to be enabled for which upgrade scenarios. Peter signature.asc Description: Digital signature
Bug#416295: Same behaviour seen on bug #145766 is still present on this
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Package: cyrus-2.2 Version: 2.2 Severity: grave Justification: renders package unusable *** Please type your report below this line *** While authenticating to cyradm, cyrus-imapd is signaled to death by signal 6, which is similiar to what happens on #145766. I also tried to compile libldap2 without sasl support as sugested on the Cyrus README doc, but same problem happens. My use case is what's shown on that doc. I use libpam-ldap libnss-ldap and saslauthd. If any more info is need please ask, I'll gently provide it. - -- System Information: Debian Release: 4.0 APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18.5-vs2.1.1.3-p3-squash-drbd-256ip-ipv6 Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) - -- Pedro Algarvio __ ___ ___ ______ __ | Y .' _| _ .-.' _| |_ .-..-. |. | | _| 1___| _ | _| _|__| _ | _| _ | |. | |__| | |_|__| ||__|_|__| |___ | |: 1 ||: 1 | |_| |::.. . ||::.. . | ufs [AT] ufsoft [DOT] org `---'`---'ufs [AT] sapo [DOT] pt -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2.2 (GNU/Linux) iD8DBQFGB/5NniPxVTX2hA4RAkjnAJ44Uy5v3Uw7qS0yMx5u8mdISqFojgCgm9gf 9KO/DkegJIxmVnQR10d4c8g= =ehnd -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#416284: marked as done (udev: Persistent net naming breaks system when hardware )
Your message dated Mon, 26 Mar 2007 19:10:10 +0200 with message-id [EMAIL PROTECTED] and subject line Bug#416284: udev: Persistent net naming breaks system when hardware change; effect undocumented has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) ---BeginMessage--- Package: udev Version: 0.105-3 Severity: grave Justification: renders package unusable Recent udev and/or kernel versions appear to have introduced a feature that is problematic. /lib/udev/write_net_rules -- NOT a conffile -- is saving persistent network information by default. This means that the system breaks when: * An Ethernet card is swapped for a different hardware it may now become eth4 or some such instead of eth0 * A hard drive is moved to a new machine Even if the Debian kernel can autodetect the hardware appropriately, suddently the network breaks because again eth0 is taken to be a MAC address that doesn't exist * A tool such as systemimager is used to manage the installation of multiple Debian machines based on a common image I can understand why the feature exists, BUT: * Should it be on by default? I think not. If software probing stability is so poor that this is needed by default, the problem lies elsewhere. * This is not documented anywhere obvious. It should at least be documented in the interfaces manpage, and hopefully elsewhere (somewhere more obvious than buried in udev) I think that this ought to be fixed for etch; otherwise, we'll have some nasty surprises. -- Package-specific info: -- /etc/udev/rules.d/: /etc/udev/rules.d/: total 12 lrwxrwxrwx 1 root root 20 2007-03-08 07:17 020_permissions.rules - ../permissions.rules lrwxrwxrwx 1 root root 19 2007-03-08 07:17 025_libgphoto2.rules - ../libgphoto2.rules lrwxrwxrwx 1 root root 16 2007-03-12 13:13 025_libsane.rules - ../libsane.rules lrwxrwxrwx 1 root root 18 2007-03-08 07:17 025_visioneer.rules - ../visioneer.rules lrwxrwxrwx 1 root root 15 2007-03-08 07:17 85-pcmcia.rules - ../pcmcia.rules lrwxrwxrwx 1 root root 13 2007-03-08 07:17 udev.rules - ../udev.rules lrwxrwxrwx 1 root root 25 2007-03-08 07:17 z20_persistent-input.rules - ../persistent-input.rules lrwxrwxrwx 1 root root 19 2007-03-08 07:17 z20_persistent.rules - ../persistent.rules -rw-r--r-- 1 root root 820 2006-11-13 12:07 z25_persistent-cd.rules -rw-r--r-- 1 root root 1059 2007-03-07 08:41 z25_persistent-net.rules -rw-r--r-- 1 root root 32 2006-11-12 08:31 z30_custom_ram lrwxrwxrwx 1 root root 33 2007-03-08 07:17 z45_persistent-net-generator.rules - ../persistent-net-generator.rules lrwxrwxrwx 1 root root 12 2007-03-08 07:17 z50_run.rules - ../run.rules lrwxrwxrwx 1 root root 16 2007-03-08 07:17 z55_hotplug.rules - ../hotplug.rules lrwxrwxrwx 1 root root 19 2007-03-08 07:17 z60_alsa-utils.rules - ../alsa-utils.rules lrwxrwxrwx 1 root root 15 2007-03-08 07:17 z60_hdparm.rules - ../hdparm.rules lrwxrwxrwx 1 root root 33 2007-03-08 07:17 z60_xserver-xorg-input-wacom.rules - ../xserver-xorg-input-wacom.rules lrwxrwxrwx 1 root root 29 2007-03-08 07:17 z75_cd-aliases-generator.rules - ../cd-aliases-generator.rules lrwxrwxrwx 1 root root 12 2007-03-08 07:17 z99_hal.rules - ../hal.rules -- /sys/: /sys/block/hda/dev /sys/block/hda/hda1/dev /sys/block/hda/hda2/dev /sys/block/hda/hda5/dev /sys/block/hda/hda6/dev /sys/block/hda/hda7/dev /sys/block/hda/hda8/dev /sys/block/hda/hda9/dev /sys/block/hdc/dev /sys/block/loop0/dev /sys/block/loop1/dev /sys/block/loop2/dev /sys/block/loop3/dev /sys/block/loop4/dev /sys/block/loop5/dev /sys/block/loop6/dev /sys/block/loop7/dev /sys/block/ram0/dev /sys/block/ram10/dev /sys/block/ram11/dev /sys/block/ram12/dev /sys/block/ram13/dev /sys/block/ram14/dev /sys/block/ram15/dev /sys/block/ram1/dev /sys/block/ram2/dev /sys/block/ram3/dev /sys/block/ram4/dev /sys/block/ram5/dev /sys/block/ram6/dev /sys/block/ram7/dev /sys/block/ram8/dev /sys/block/ram9/dev /sys/class/drm/card0/dev /sys/class/graphics/fb0/dev /sys/class/graphics/fb1/dev /sys/class/input/input0/event0/dev /sys/class/input/input1/event1/dev /sys/class/input/input2/event2/dev /sys/class/input/input2/mouse0/dev /sys/class/input/input2/ts0/dev /sys/class/input/input3/event3/dev /sys/class/input/input3/mouse1/dev /sys/class/input/input3/ts1/dev /sys/class/input/input4/event4/dev /sys/class/input/mice/dev /sys/class/misc/agpgart/dev /sys/class/misc/device-mapper/dev /sys/class/misc/hpet/dev /sys/class/misc/nvram/dev /sys/class/misc/psaux/dev /sys/class/misc/rtc/dev /sys/class/misc/snapshot/dev
Processed: Asterisk bug #385060
Processing commands for [EMAIL PROTECTED]: found 385060 1.0.0-1 Bug#385060: CVE-2006-4346: Asterisk MGCP AUEP Response Handling Buffer Overflow Bug marked as found in version 1.0.0-1. thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: Re: Bug#416295: Same behaviour seen on bug #145766 is still present on this
Processing commands for [EMAIL PROTECTED]: reassign 416295 cyrus-imapd-2.2 Bug#416295: Same behaviour seen on bug #145766 is still present on this Warning: Unknown package 'cyrus-2.2' Bug reassigned from package `cyrus-2.2' to `cyrus-imapd-2.2'. -- Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#416228: marked as done (fails to install - chown: cannot access `/var/lib/postgresql')
Your message dated Mon, 26 Mar 2007 17:17:25 + with message-id [EMAIL PROTECTED] and subject line Bug#416228: fixed in postgresql-common 73 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) ---BeginMessage--- Package: postgresql-common Version: 72 Severity: serious Setting up postgresql-common (72) ... chown: cannot access `/var/lib/postgresql': No such file or directory dpkg: error processing postgresql-common (--configure): subprocess post-installation script returned error exit status 1 Errors were encountered while processing: postgresql-common -- System Information: Debian Release: 4.0 APT prefers unstable APT policy: (900, 'unstable'), (5, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.20.4 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Versions of packages postgresql-common depends on: ii adduser 3.102 Add and remove users and groups ii debconf [debconf-2.0] 1.5.13 Debian configuration management sy ii lsb-base 3.1-23.1 Linux Standard Base 3.1 init scrip ii postgresql-client-common 72 manager for multiple PostgreSQL cl ii procps1:3.2.7-3 /proc file system utilities ii ssl-cert 1.0.14 Simple debconf wrapper for openssl postgresql-common recommends no packages. -- debconf information: * postgresql-common/obsolete-major: postgresql-common/untransitioned: ---End Message--- ---BeginMessage--- Source: postgresql-common Source-Version: 73 We believe that the bug you reported is fixed in the latest version of postgresql-common, which is due to be installed in the Debian FTP archive: postgresql-client-common_73_all.deb to pool/main/p/postgresql-common/postgresql-client-common_73_all.deb postgresql-common_73.dsc to pool/main/p/postgresql-common/postgresql-common_73.dsc postgresql-common_73.tar.gz to pool/main/p/postgresql-common/postgresql-common_73.tar.gz postgresql-common_73_all.deb to pool/main/p/postgresql-common/postgresql-common_73_all.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Martin Pitt [EMAIL PROTECTED] (supplier of updated postgresql-common package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 26 Mar 2007 18:51:27 +0200 Source: postgresql-common Binary: postgresql-client-common postgresql-common Architecture: source all Version: 73 Distribution: unstable Urgency: low Maintainer: Martin Pitt [EMAIL PROTECTED] Changed-By: Martin Pitt [EMAIL PROTECTED] Description: postgresql-client-common - manager for multiple PostgreSQL client versions postgresql-common - manager for PostgreSQL database clusters Closes: 416146 416228 Changes: postgresql-common (73) unstable; urgency=low . * debian/postgresql-common.dirs: Ship /var/lib/postgresql again, creating it dynamically causes various upgrade failures. Closes: #416146, #416228 * debian/postgresql-common.postinst: Call adduser with --no-create-home. This avoids the 'wrong owner' warning as well. Files: ddfcfafd08b501db8ce187028f79347f 604 misc optional postgresql-common_73.dsc 33016f2ef1b4b0f58e1b692b98bb5bba 98796 misc optional postgresql-common_73.tar.gz b15dd4c3c14af464cd06ce2c775d58d4 103262 misc optional postgresql-common_73_all.deb 2201a1dae0afe073fd0b13082ec10f6f 40468 misc optional postgresql-client-common_73_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFGB/sADecnbV4Fd/IRArlyAJ98fzKOs7OtjoDLNpSnM2TBIU3SdACgqVBg tmXlGdk6lwKdfByy/dKh9OA= =RFgJ -END PGP SIGNATURE- ---End Message---
Bug#416146: marked as done (postgresql-common: missing /var/lib/postgresql)
Your message dated Mon, 26 Mar 2007 17:17:25 + with message-id [EMAIL PROTECTED] and subject line Bug#416228: fixed in postgresql-common 73 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) ---BeginMessage--- Package: postgresql-common Version: 71 Severity: normal Hi Upgrade to postgresql-common (72) fails like so: Setting up postgresql-common (72) ... chown: cannot access `/var/lib/postgresql': No such file or directory dpkg: error processing postgresql-common (--configure): subprocess post-installation script returned error exit status 1 this is an empty dir installed by postgresql-common (71). Can be fixed like so: # touch /var/lib/postgresql and redo the upgrade to postgresql-common (72) . Not sure this is how it _should_ be. Regards Gijs -- System Information: Debian Release: 4.0 APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-4-686 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Versions of packages postgresql-common depends on: ii adduser 3.102 Add and remove users and groups ii debconf [debconf-2.0] 1.5.13 Debian configuration management sy ii lsb-base 3.1-23.1 Linux Standard Base 3.1 init scrip ii postgresql-client-common 72 manager for multiple PostgreSQL cl ii procps1:3.2.7-3 /proc file system utilities ii ssl-cert 1.0.14 Simple debconf wrapper for openssl postgresql-common recommends no packages. -- debconf information: postgresql-common/obsolete-major: postgresql-common/untransitioned: -- When there isn't sufficient virtual memory, the compiler bails out, giving an internal error message. When I kill some processes, the error goes away. And what is the compiler supposed to do instead? Go shopping for you and buy more memory? -- Falk Hueffner, on the GNU C++ compiler ---End Message--- ---BeginMessage--- Source: postgresql-common Source-Version: 73 We believe that the bug you reported is fixed in the latest version of postgresql-common, which is due to be installed in the Debian FTP archive: postgresql-client-common_73_all.deb to pool/main/p/postgresql-common/postgresql-client-common_73_all.deb postgresql-common_73.dsc to pool/main/p/postgresql-common/postgresql-common_73.dsc postgresql-common_73.tar.gz to pool/main/p/postgresql-common/postgresql-common_73.tar.gz postgresql-common_73_all.deb to pool/main/p/postgresql-common/postgresql-common_73_all.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Martin Pitt [EMAIL PROTECTED] (supplier of updated postgresql-common package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 26 Mar 2007 18:51:27 +0200 Source: postgresql-common Binary: postgresql-client-common postgresql-common Architecture: source all Version: 73 Distribution: unstable Urgency: low Maintainer: Martin Pitt [EMAIL PROTECTED] Changed-By: Martin Pitt [EMAIL PROTECTED] Description: postgresql-client-common - manager for multiple PostgreSQL client versions postgresql-common - manager for PostgreSQL database clusters Closes: 416146 416228 Changes: postgresql-common (73) unstable; urgency=low . * debian/postgresql-common.dirs: Ship /var/lib/postgresql again, creating it dynamically causes various upgrade failures. Closes: #416146, #416228 * debian/postgresql-common.postinst: Call adduser with --no-create-home. This avoids the 'wrong owner' warning as well. Files: ddfcfafd08b501db8ce187028f79347f 604 misc optional postgresql-common_73.dsc 33016f2ef1b4b0f58e1b692b98bb5bba 98796 misc optional postgresql-common_73.tar.gz b15dd4c3c14af464cd06ce2c775d58d4 103262 misc optional postgresql-common_73_all.deb 2201a1dae0afe073fd0b13082ec10f6f 40468 misc optional postgresql-client-common_73_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux)
Bug#416228: marked as done (fails to install - chown: cannot access `/var/lib/postgresql')
Your message dated Mon, 26 Mar 2007 17:17:25 + with message-id [EMAIL PROTECTED] and subject line Bug#416146: fixed in postgresql-common 73 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) ---BeginMessage--- Package: postgresql-common Version: 72 Severity: serious Setting up postgresql-common (72) ... chown: cannot access `/var/lib/postgresql': No such file or directory dpkg: error processing postgresql-common (--configure): subprocess post-installation script returned error exit status 1 Errors were encountered while processing: postgresql-common -- System Information: Debian Release: 4.0 APT prefers unstable APT policy: (900, 'unstable'), (5, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.20.4 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Versions of packages postgresql-common depends on: ii adduser 3.102 Add and remove users and groups ii debconf [debconf-2.0] 1.5.13 Debian configuration management sy ii lsb-base 3.1-23.1 Linux Standard Base 3.1 init scrip ii postgresql-client-common 72 manager for multiple PostgreSQL cl ii procps1:3.2.7-3 /proc file system utilities ii ssl-cert 1.0.14 Simple debconf wrapper for openssl postgresql-common recommends no packages. -- debconf information: * postgresql-common/obsolete-major: postgresql-common/untransitioned: ---End Message--- ---BeginMessage--- Source: postgresql-common Source-Version: 73 We believe that the bug you reported is fixed in the latest version of postgresql-common, which is due to be installed in the Debian FTP archive: postgresql-client-common_73_all.deb to pool/main/p/postgresql-common/postgresql-client-common_73_all.deb postgresql-common_73.dsc to pool/main/p/postgresql-common/postgresql-common_73.dsc postgresql-common_73.tar.gz to pool/main/p/postgresql-common/postgresql-common_73.tar.gz postgresql-common_73_all.deb to pool/main/p/postgresql-common/postgresql-common_73_all.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Martin Pitt [EMAIL PROTECTED] (supplier of updated postgresql-common package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 26 Mar 2007 18:51:27 +0200 Source: postgresql-common Binary: postgresql-client-common postgresql-common Architecture: source all Version: 73 Distribution: unstable Urgency: low Maintainer: Martin Pitt [EMAIL PROTECTED] Changed-By: Martin Pitt [EMAIL PROTECTED] Description: postgresql-client-common - manager for multiple PostgreSQL client versions postgresql-common - manager for PostgreSQL database clusters Closes: 416146 416228 Changes: postgresql-common (73) unstable; urgency=low . * debian/postgresql-common.dirs: Ship /var/lib/postgresql again, creating it dynamically causes various upgrade failures. Closes: #416146, #416228 * debian/postgresql-common.postinst: Call adduser with --no-create-home. This avoids the 'wrong owner' warning as well. Files: ddfcfafd08b501db8ce187028f79347f 604 misc optional postgresql-common_73.dsc 33016f2ef1b4b0f58e1b692b98bb5bba 98796 misc optional postgresql-common_73.tar.gz b15dd4c3c14af464cd06ce2c775d58d4 103262 misc optional postgresql-common_73_all.deb 2201a1dae0afe073fd0b13082ec10f6f 40468 misc optional postgresql-client-common_73_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFGB/sADecnbV4Fd/IRArlyAJ98fzKOs7OtjoDLNpSnM2TBIU3SdACgqVBg tmXlGdk6lwKdfByy/dKh9OA= =RFgJ -END PGP SIGNATURE- ---End Message---
Bug#416146: marked as done (postgresql-common: missing /var/lib/postgresql)
Your message dated Mon, 26 Mar 2007 17:17:25 + with message-id [EMAIL PROTECTED] and subject line Bug#416146: fixed in postgresql-common 73 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) ---BeginMessage--- Package: postgresql-common Version: 71 Severity: normal Hi Upgrade to postgresql-common (72) fails like so: Setting up postgresql-common (72) ... chown: cannot access `/var/lib/postgresql': No such file or directory dpkg: error processing postgresql-common (--configure): subprocess post-installation script returned error exit status 1 this is an empty dir installed by postgresql-common (71). Can be fixed like so: # touch /var/lib/postgresql and redo the upgrade to postgresql-common (72) . Not sure this is how it _should_ be. Regards Gijs -- System Information: Debian Release: 4.0 APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-4-686 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Versions of packages postgresql-common depends on: ii adduser 3.102 Add and remove users and groups ii debconf [debconf-2.0] 1.5.13 Debian configuration management sy ii lsb-base 3.1-23.1 Linux Standard Base 3.1 init scrip ii postgresql-client-common 72 manager for multiple PostgreSQL cl ii procps1:3.2.7-3 /proc file system utilities ii ssl-cert 1.0.14 Simple debconf wrapper for openssl postgresql-common recommends no packages. -- debconf information: postgresql-common/obsolete-major: postgresql-common/untransitioned: -- When there isn't sufficient virtual memory, the compiler bails out, giving an internal error message. When I kill some processes, the error goes away. And what is the compiler supposed to do instead? Go shopping for you and buy more memory? -- Falk Hueffner, on the GNU C++ compiler ---End Message--- ---BeginMessage--- Source: postgresql-common Source-Version: 73 We believe that the bug you reported is fixed in the latest version of postgresql-common, which is due to be installed in the Debian FTP archive: postgresql-client-common_73_all.deb to pool/main/p/postgresql-common/postgresql-client-common_73_all.deb postgresql-common_73.dsc to pool/main/p/postgresql-common/postgresql-common_73.dsc postgresql-common_73.tar.gz to pool/main/p/postgresql-common/postgresql-common_73.tar.gz postgresql-common_73_all.deb to pool/main/p/postgresql-common/postgresql-common_73_all.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Martin Pitt [EMAIL PROTECTED] (supplier of updated postgresql-common package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 26 Mar 2007 18:51:27 +0200 Source: postgresql-common Binary: postgresql-client-common postgresql-common Architecture: source all Version: 73 Distribution: unstable Urgency: low Maintainer: Martin Pitt [EMAIL PROTECTED] Changed-By: Martin Pitt [EMAIL PROTECTED] Description: postgresql-client-common - manager for multiple PostgreSQL client versions postgresql-common - manager for PostgreSQL database clusters Closes: 416146 416228 Changes: postgresql-common (73) unstable; urgency=low . * debian/postgresql-common.dirs: Ship /var/lib/postgresql again, creating it dynamically causes various upgrade failures. Closes: #416146, #416228 * debian/postgresql-common.postinst: Call adduser with --no-create-home. This avoids the 'wrong owner' warning as well. Files: ddfcfafd08b501db8ce187028f79347f 604 misc optional postgresql-common_73.dsc 33016f2ef1b4b0f58e1b692b98bb5bba 98796 misc optional postgresql-common_73.tar.gz b15dd4c3c14af464cd06ce2c775d58d4 103262 misc optional postgresql-common_73_all.deb 2201a1dae0afe073fd0b13082ec10f6f 40468 misc optional postgresql-client-common_73_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux)
Bug#416016: Might I adopt/co-maintain this package?
Hi Angus, (and hi, pkg-perl group!) You are the current maintainer of libembperl-perl. I would like to co-maintain this with you, or complete adopt it (putting it as one of the pkg-perl group's packages). Would you agree with this? Why am I asking? Because I need this package... I'm using it in a production server, and it broke after a Sarge-Etch upgrade (see bug #395870). Sadly, my NMU broke it in more ways in which I'm trying to fix it (FTBFS because of some tests hanging, it seems)... But it suffered from a bug which broke it under Apache2 (which, I guess, is what many people use) for some months. I'm sending a copy of this mail to the bug report opened by Vorlon reporting of my NMU's breakage. I'm sorry if I'm utterly mistaken, but I think you have reduced your Debian activity, and I think getting this package in shape to be part of Etch requires me to make this move _now_ ;-) Of course, I'll be delighted to be proven wrong. Thank you for your time and reply. -- Gunnar Wolf - [EMAIL PROTECTED] - (+52-55)5623-0154 / 1451-2244 PGP key 1024D/8BB527AF 2001-10-23 Fingerprint: 0C79 D2D1 2C4E 9CE4 5973 F800 D80E F35A 8BB5 27AF signature.asc Description: Digital signature
Bug#413041: jasper: heap corruption and segv's
On Sun, Mar 11, 2007 at 06:15:38PM +0100, Roland Stigge wrote: Hi, I can reproduce the problem with i386, too. Working on it. Has there been any progress on this? Kurt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#385060: Processed: Asterisk bug #385060
Elizabeth, Not quite sure why you raised this. asterisk-1.0.0-1 hasn't been in Debian for a very long time, even before the current stable version. Mark On Monday 26 March 2007 18:27, Debian Bug Tracking System wrote: Processing commands for [EMAIL PROTECTED]: found 385060 1.0.0-1 Bug#385060: CVE-2006-4346: Asterisk MGCP AUEP Response Handling Buffer Overflow Bug marked as found in version 1.0.0-1. thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) ___ Pkg-voip-maintainers mailing list [EMAIL PROTECTED] http://lists.alioth.debian.org/mailman/listinfo/pkg-voip-maintainers pgpaVF7YkXOAb.pgp Description: PGP signature
Bug#416300: kqemu-source: Undefine Symbols
Package: kqemu-source Version: 1.3.0~pre11-3 Severity: grave Justification: renders package unusable The following from dmesg | grep kqemu: kqemu: Unknown symbol kqemu_init kqemu: Unknown symbol kqemu_exec kqemu: Unknown symbol kqemu_delete kqemu: Unknown symbol kqemu_global_init kqemu: Unknown symbol kqemu_global_delete kqemu: Unknown symbol kqemu_get_cpu_state -- System Information: Debian Release: 4.0 APT prefers unstable APT policy: (990, 'unstable'), (650, 'testing'), (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.20.3-davidb-rt Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) Versions of packages kqemu-source depends on: ii bzip2 1.0.3-6high-quality block-sorting file co ii debhelper 5.0.42 helper programs for debian/rules ii dpatch2.0.21 patch maintenance system for Debia ii make 3.81-3 The GNU version of the make util ii module-assistant 0.10.11tool to make module package creati kqemu-source recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#385060: Processed: Asterisk bug #385060
On Mon, Mar 26, 2007 at 06:39:53PM +0100, Mark Purcell wrote: Not quite sure why you raised this. asterisk-1.0.0-1 hasn't been in Debian for a very long time, even before the current stable version. The security annoucement said that versions 1.0.0 - 1.2.10 were vulnerable. This tag ought to mark the intermediate versions, which includes the version in sarge. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#392312: xserver-xorg-core: [sparc] Freezes system
On Mon, Mar 19, 2007 at 19:13:00 +0100, Mico Naddeo wrote: Hi, it seems that the bug is back in the experimental version of this package. please see: https://launchpad.net/ubuntu/+source/xorg-server/+bug/93041 Hi Jurij, it was reported that #392312 is back in xorg-server 1.2.0, despite the patch that was added in 2:1.1.1-10. Could you have a look at what might have broken this? Thanks, Julien signature.asc Description: Digital signature
Bug#416016: NMU uploaded, FTBFS fixed
tags 416016 + patch thanks This package was FTBFSing because part of its test suite involves bringing up an Apache server and running a battery of tests against it - and then Apache is killed, which makes gdb kill the whole process. I modified debian/rules so it executes only those tests which do not require firing Apache. Patch is attached, NMU is uploaded. -- Gunnar Wolf - [EMAIL PROTECTED] - (+52-55)5623-0154 / 1451-2244 PGP key 1024D/8BB527AF 2001-10-23 Fingerprint: 0C79 D2D1 2C4E 9CE4 5973 F800 D80E F35A 8BB5 27AF diff -ru libembperl-perl-2.2.0_after_nmu.1/debian/changelog libembperl-perl-2.2.0_after_nmu.2/debian/changelog --- libembperl-perl-2.2.0_after_nmu.1/debian/changelog 2007-03-26 13:27:54.0 -0600 +++ libembperl-perl-2.2.0_after_nmu.2/debian/changelog 2007-03-26 13:29:09.0 -0600 @@ -1,3 +1,11 @@ +libembperl-perl (2.2.0-1.2) unstable; urgency=high + + * Non-maintainer upload. + * No longer spawns Apache processes to run the test scripts, as it leads +to FTBFS (Closes: #416016) + + -- Gunnar Wolf [EMAIL PROTECTED] Mon, 26 Mar 2007 11:49:17 -0600 + libembperl-perl (2.2.0-1.1) unstable; urgency=low * Non-maintainer upload. diff -ru libembperl-perl-2.2.0_after_nmu.1/debian/rules libembperl-perl-2.2.0_after_nmu.2/debian/rules --- libembperl-perl-2.2.0_after_nmu.1/debian/rules 2007-03-26 13:27:54.0 -0600 +++ libembperl-perl-2.2.0_after_nmu.2/debian/rules 2007-03-26 13:29:09.0 -0600 @@ -73,7 +73,13 @@ build%: config% dh_testdir $(MAKE) OPTIMIZE=$(OPTIMIZE) LD_RUN_PATH= - $(MAKE) TESTARGS=$(TESTARGS) test + +# Part of the regular test process involves bringing up an Apache +# server and connecting to it. Unfortunately, this easily brings up +# FTBFS errors or (horror!) might leave unneeded processes in our buildds - +# Run the tests in offline mode only by passing the -oxrea switches. +# (see bug #416016) + $(MAKE) TESTARGS=$(TESTARGS) -oxrea test install: build dh_testdir signature.asc Description: Digital signature
Processed: NMU uploaded, FTBFS fixed
Processing commands for [EMAIL PROTECTED]: tags 416016 + patch Bug#416016: libembperl-perl 2.2.0-1 (all/testing): FTBFS: Terminated There were no tags set. Tags added: patch thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#416016: marked as done (libembperl-perl 2.2.0-1 (all/testing): FTBFS: Terminated)
Your message dated Mon, 26 Mar 2007 19:47:04 + with message-id [EMAIL PROTECTED] and subject line Bug#416016: fixed in libembperl-perl 2.2.0-1.2 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) ---BeginMessage--- Package: libembperl-perl Version: 2.2.0-1 Severity: serious Hi Angus, I imagine you've seen that Gunnar NMUed libembperl-perl for bug #395870. Unfortunately, that NMU has failed to autobuild on all architectures with this error: [...] #258 epform.htm...ok All tests have been passed successfully! make[2]: *** wait: No child processes. Stop. make[2]: *** Waiting for unfinished jobs make[2]: *** wait: No child processes. Stop. make[1]: *** wait: No child processes. Stop. make[1]: *** Waiting for unfinished jobs make[1]: *** wait: No child processes. Stop. make: *** wait: No child processes. Stop. make: *** Waiting for unfinished jobs make: *** wait: No child processes. Stop. [...] A full build log can be found at http://buildd.debian.org/fetch.cgi?pkg=libembperl-perl;ver=2.2.0-1.1;arch=amd64;stamp=1174612943. Further investigation shows that the problem also affects the version currently in testing. It's also trivially reproducible for me in a clean chroot. I'm not sure why this issue didn't manifest in earlier archive build tests, but it does certainly prevent resolving bug #395870, even by way of binNMU. Sadly, after reviewing it I think bug #395870 is downgradable, but in contrast this build failure prevents security support for the package. A quick fix would definitely be appreciated for this; otherwise libembperl-perl is likely to be dropped from the etch release. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ ---End Message--- ---BeginMessage--- Source: libembperl-perl Source-Version: 2.2.0-1.2 We believe that the bug you reported is fixed in the latest version of libembperl-perl, which is due to be installed in the Debian FTP archive: libembperl-perl_2.2.0-1.2.diff.gz to pool/main/libe/libembperl-perl/libembperl-perl_2.2.0-1.2.diff.gz libembperl-perl_2.2.0-1.2.dsc to pool/main/libe/libembperl-perl/libembperl-perl_2.2.0-1.2.dsc libembperl-perl_2.2.0-1.2_i386.deb to pool/main/libe/libembperl-perl/libembperl-perl_2.2.0-1.2_i386.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Gunnar Wolf [EMAIL PROTECTED] (supplier of updated libembperl-perl package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 26 Mar 2007 11:49:17 -0600 Source: libembperl-perl Binary: libembperl-perl Architecture: source i386 Version: 2.2.0-1.2 Distribution: unstable Urgency: high Maintainer: Angus Lees [EMAIL PROTECTED] Changed-By: Gunnar Wolf [EMAIL PROTECTED] Description: libembperl-perl - A system for building dynamic websites with Perl Closes: 416016 Changes: libembperl-perl (2.2.0-1.2) unstable; urgency=high . * Non-maintainer upload. * No longer spawns Apache processes to run the test scripts, as it leads to FTBFS (Closes: #416016) Files: 20ef64e9a7042c2414a962398426cbe4 878 web optional libembperl-perl_2.2.0-1.2.dsc dcccf2ca70fa895c91df4eaa5adef0ac 10334 web optional libembperl-perl_2.2.0-1.2.diff.gz 71e495a9a70f1e6ced79b4152ae82be8 977750 web optional libembperl-perl_2.2.0-1.2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFGCBtP2A7zWou1J68RAv7oAJ0Q85KT2E0Q29VEC+67H+/f8WbDMgCcCiVC zSimxEU4afwoAKkx2XYGgwc= =6EIZ -END PGP SIGNATURE- ---End Message---
Bug#416311: mozilla-tabextensions: No longer useable after upgrade 2.1.2006031301-5 with iceweasel 2.0.0.3-1
Package: mozilla-tabextensions Version: 2.1.2006031301-5 Severity: grave Justification: renders package unusable The extension has simply disappeared from the iceweasel menubar as well as the 'add-on' list. It is, however, still useable through iceape. mozilla-tabextensions_2.1.2006031301-4_all.deb works fine with iceweasel 2.0.0.3-1. -- System Information: Debian Release: 3.0 APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages mozilla-tabextensions depends on: ii iceape-browser1.0.8-4Iceape Navigator (Internet browser mozilla-tabextensions recommends no packages. -- debconf-show failed -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#416295: Same behaviour seen on bug #145766 is still present on this
On Mon, 26 Mar 2007, Pedro Algarvio, aka, s0undt3ch wrote: While authenticating to cyradm, cyrus-imapd is signaled to death by signal 6, which is similiar to what happens on #145766. I also tried to compile libldap2 without sasl support as sugested on the Cyrus README doc, but same problem happens. My use case is what's shown on that doc. I use libpam-ldap libnss-ldap and saslauthd. If any more info is need please ask, I'll gently provide it. Copy of /etc/nssswitch.conf, /etc/imapd.conf and /etc/cyrus.conf please? -- One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie. -- The Silicon Valley Tarot Henrique Holschuh -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#416195: marked as done (lwat is vulnerable if there is malicious code in the cn: ldap field)
Your message dated Mon, 26 Mar 2007 20:47:44 +
with message-id [EMAIL PROTECTED]
and subject line Bug#416195: fixed in lwat 0.13-2
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
---BeginMessage---
Package: lwat
Version: 0.13-1
Severity: grave
Tags: security
I tested today lwat if there is it is vulnerable for malicious html code
if this values are already inside the ldap database.
I used ldif to add something like this as the cn:
cn: /aa href=javascript:; onclick=window.alert('Thanks for this
hack'); Test User/aa
The result was that if I search for Test user and click on it I got a
popup with 'Thanks for this hack' in it.
This issue is similiar to: #415379
I will attach a fix soon, and will upload it then, since I'm the
maintainer of this package ;-)
Greetings
Patrick
-- System Information:
Debian Release: 4.0
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Versions of packages lwat depends on:
ii apache2-mpm-prefork [apache2] 2.2.3-3.3 Traditional model for Apache HTTPD
ii debconf [debconf-2.0] 1.5.13 Debian configuration management sy
ii libapache2-mod-php5 5.2.0-10 server-side, HTML-embedded scripti
ii php5 5.2.0-10 server-side, HTML-embedded scripti
ii php5-ldap 5.2.0-10 LDAP module for php5
ii smarty-gettext1.0b1-2provides gettext support for smart
lwat recommends no packages.
-- debconf information excluded
---End Message---
---BeginMessage---
Source: lwat
Source-Version: 0.13-2
We believe that the bug you reported is fixed in the latest version of
lwat, which is due to be installed in the Debian FTP archive:
lwat_0.13-2.diff.gz
to pool/main/l/lwat/lwat_0.13-2.diff.gz
lwat_0.13-2.dsc
to pool/main/l/lwat/lwat_0.13-2.dsc
lwat_0.13-2_all.deb
to pool/main/l/lwat/lwat_0.13-2_all.deb
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Patrick Winnertz [EMAIL PROTECTED] (supplier of updated lwat package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [EMAIL PROTECTED])
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Sun, 25 Mar 2007 22:40:37 +0200
Source: lwat
Binary: lwat
Architecture: source all
Version: 0.13-2
Distribution: unstable
Urgency: high
Maintainer: Patrick Winnertz [EMAIL PROTECTED]
Changed-By: Patrick Winnertz [EMAIL PROTECTED]
Description:
lwat - LDAP Web-based Administration Tool
Closes: 416195
Changes:
lwat (0.13-2) unstable; urgency=high
.
* Added patch to escape data fetched from the ldap databse to
avoid executing malicious codeblocks found in ldap.
(Closes: #416195)
* Set urgency to high since this is a security fix.
* Modified rules to run dpatch in build and clean target.
* Added build-dep on dpatch.
* The german and norwegian translations of lwat have been updated.
* Upload sponsored by Petter Reinholdtsen.
Files:
7c7fd70980b5fc1ca3e45528f8c8a4e1 638 misc optional lwat_0.13-2.dsc
f3bd5896ead542bc5bb56f6f11ad61ac 13122 misc optional lwat_0.13-2.diff.gz
b65cf0f86d371de8a07a5a8845bc1b61 51284 misc optional lwat_0.13-2_all.deb
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFGCCfy20zMSyow1ykRAlDMAJ9Ncz6+pkSAgknRWEoTehSVXom1QACfQazP
aATceXY3R3xo1XjYeG0hQl8=
=TRA4
-END PGP SIGNATURE-
---End Message---
Bug#416311: mozilla-tabextensions: No longer useable after upgrade 2.1.2006031301-5 with iceweasel 2.0.0.3-1
severity 416311 wishlist thanks On Mon, Mar 26, 2007 at 04:19:14PM -0400, salman wrote: Package: mozilla-tabextensions Version: 2.1.2006031301-5 Severity: grave Justification: renders package unusable The extension has simply disappeared from the iceweasel menubar as well as the 'add-on' list. It is, however, still useable through iceape. mozilla-tabextensions_2.1.2006031301-4_all.deb works fine with iceweasel 2.0.0.3-1. That's not what bug #412314 says. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: Re: Bug#416311: mozilla-tabextensions: No longer useable after upgrade 2.1.2006031301-5 with iceweasel 2.0.0.3-1
Processing commands for [EMAIL PROTECTED]: severity 416311 wishlist Bug#416311: mozilla-tabextensions: No longer useable after upgrade 2.1.2006031301-5 with iceweasel 2.0.0.3-1 Severity set to `wishlist' from `grave' thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: severity of 416287 is important
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.10.1 # 'serious' is the maintainer's prerogative severity 416287 important Bug#416287: gaim-encryption: fails to handshake with newer versions of gaim Severity set to `important' from `serious' End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#416318: kdelibs4c2a: Vulnerable to CVE-2007-1564 - exploitable passive ftp connections
Package: kdelibs4c2a Version: 4:3.5.5a.dfsg.1-5 Severity: grave Tags: security patch Justification: user security hole The FTP protocol implementation in Konqueror 3.5.5 allows remote servers to force the client to connect to other servers, perform a proxied port scan, or obtain sensitive information by specifying an alternate server address in a FTP PASV command. http://nvd.nist.gov/nvd.cfm?cvename=CVE-2007-1564 This issue have ben addressed in the -7 upload. /Sune -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#416318: marked as done (kdelibs4c2a: Vulnerable to CVE-2007-1564 - exploitable passive ftp connections)
Your message dated Mon, 26 Mar 2007 23:22:04 +0200 with message-id [EMAIL PROTECTED] and subject line Bug#416318: kdelibs4c2a: Vulnerable to CVE-2007-1564 - exploitable passive ftp connections has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) ---BeginMessage--- Package: kdelibs4c2a Version: 4:3.5.5a.dfsg.1-5 Severity: grave Tags: security patch Justification: user security hole The FTP protocol implementation in Konqueror 3.5.5 allows remote servers to force the client to connect to other servers, perform a proxied port scan, or obtain sensitive information by specifying an alternate server address in a FTP PASV command. http://nvd.nist.gov/nvd.cfm?cvename=CVE-2007-1564 This issue have ben addressed in the -7 upload. /Sune ---End Message--- ---BeginMessage--- Version: 4:3.5.5a.dfsg.1-7 This issue have ben addressed in the -7 upload. ..and marking it closed.. /Sune -- Man, how can I debug the fan? First of all you neither have to receive from a firewall, nor must overclock the microkernel to insert the Fast DVD minitower. pgpk6K3y17Rr2.pgp Description: PGP signature ---End Message---
Bug#416324: FTBFS: needs udpate for new ion3-dev in unstable
Package: ion3-mod-ionflux Version: 20061022-3 Severity: serious ion3-mod-ionflux needs an update for the new ion3 in unstable: Automatic build of ion3-mod-ionflux_20061022-3 on coconut0 by sbuild/ia64 0.49 ... Setting up ion3-dev (20070318-2) ... Checking correctness of source dependencies... After installing, the following source dependencies are still unsatisfied: ion3-dev(inst 20070318-2 ! wanted 20061224) Source-dependencies not satisfied; skipping ion3-mod-ionflux -- Martin Michlmayr http://www.cyrius.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: severity of 416295 is important
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.10.1 # specific to a particular config, does not make the package completely unusable severity 416295 important Bug#416295: Same behaviour seen on bug #145766 is still present on this Severity set to `important' from `grave' End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#415775: RC-ness (AddDefaultCharset)
I recommend in favour of considering this RC. AddDefaultCharset is an *evil* feature that is only intended to be used as a dirty hack for broken setups. I suggest a quick google search: http://www.google.com/search?hl=enq=AddDefaultCharset First two hits are official apache documentation discouraging its use. Followed by stuff like: AddDefaultCharset considered harmful http://lists.w3.org/Archives/Public/www-tag/2003Sep/0176.html AddDefaultCharset is bad, bad, bad http://ungwe.org/blog/2004/01/26/22:52/ -- Robert Millan My spam trap is [EMAIL PROTECTED] Note: this address is only intended for spam harvesters. Writing to it will get you added to my black list. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed (with 1 errors): reassign 416337 pbnj [ 2.04-1 ]
Processing commands for [EMAIL PROTECTED]: reassign 416337 pbnj [ 2.04-1 ] Unknown command or malformed arguments to command. severity 416337 serious Bug#416337: Scanpbnj mySQL failure to add new data Severity set to `serious' from `normal' -- Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#415379: fixed in testing but what about unstable
this bug has been fixed in testing through a TPU upload but there doesn't seem to be any information on if it is still present in unstable. -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.5.446 / Virus Database: 268.18.18/733 - Release Date: 25/03/2007 11:07
Bug#416337: Scanpbnj mySQL failure to add new data
Package: pbnj Version: 2.04-1 Title: Broken MySQL I should have a fix for this tested and uploaded soon. Regards, Josh On 26.Mar.2007 09:29PM -0400, Ben Smith wrote: Package: Pbnj Version: 2.0 When scanning a system with scanpbnj it writes to mysql fine. However when new system is added mysql errors out debian:~/.pbnj-2.0# scanpbnj 192.168.1.0/24 -- Starting Scan of 192.168.1.1 Inserting Machine addServices: mid not defined at /usr/bin/scanpbnj line 1255. I am using Debian GNU/Linux Etch Unstable latest updates -- Joshua D. Abraham Northeastern University College of Computer and Information Science www.ccs.neu.edu/home/jabra -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#416347: kqemu-source: Source fails to build using module-assistant
Package: kqemu-source Version: 1.3.0~pre11-3 Severity: grave Justification: renders package unusable Kqemu-source fails to build when I use module-assistant. When I upgraded and rebuilt the package everything went smoothly. When I tried to add the pre11-3 module, I got the same error as in bug #416300. I decided to purge all kqemu-related packages and try to build again. When I tried to rebuild, I got an error from module-assistant. Since it worked the first time (and apparently built ok for someone, otherwise #416300 would have never been filed in the first place), this may be a works for me bug. Truncated buildlog output: make -C /lib/modules/2.6.18-4-k7/build M=`pwd` modules make[3]: Entering directory `/usr/src/linux-headers-2.6.18-4-k7' CC [M] /usr/src/modules/kqemu/kqemu-linux.o make[4]: *** No rule to make target `/usr/src/modules/kqemu/kqemu.mod.o', needed by `/usr/src/modules/kqemu/kqemu.o'. Stop. make[3]: *** [_module_/usr/src/modules/kqemu] Error 2 make[3]: Leaving directory `/usr/src/linux-headers-2.6.18-4-k7' make[2]: *** [kqemu.ko] Error 2 make[2]: Leaving directory `/usr/src/modules/kqemu' make[1]: *** [binary-modules] Error 2 make[1]: Leaving directory `/usr/src/modules/kqemu' make: *** [kdist_build] Error 2 -- System Information: Debian Release: 4.0 APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-4-k7 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Versions of packages kqemu-source depends on: ii bzip2 1.0.3-6high-quality block-sorting file co ii debhelper 5.0.42 helper programs for debian/rules ii dpatch2.0.21 patch maintenance system for Debia ii make 3.81-3 The GNU version of the make util ii module-assistant 0.10.11tool to make module package creati kqemu-source recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: (no subject)
Processing commands for [EMAIL PROTECTED]: package slapd Ignoring bugs not assigned to: slapd severity 403010 grave Bug#403010: init script doesn't start slapd Severity set to `grave' from `important' found 403010 2.3.30-5 Bug#403010: init script doesn't start slapd Bug marked as found in version 2.3.30-5. thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
