Processed: notfixed 608451 in 0.2.11-1, reopening 608451
Processing commands for cont...@bugs.debian.org:
notfixed 608451 0.2.11-1
Bug #608451 {Done: un...@debian.org (Dmitry E. Oboukhov)} [rtpg-www] rtpg-www
modifies conffile in postinst/postrm
Bug No longer marked as fixed in versions rtpg/0.2.11-1.
# Bug still exists in 0.2.11-1
reopen 608451
Bug #608451 {Done: un...@debian.org (Dmitry E. Oboukhov)} [rtpg-www] rtpg-www
modifies conffile in postinst/postrm
thanks
Stopping processing here.
Please contact me if you need assistance.
--
608451: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=608451
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#607857: tex-common: Hard-coded path in proposed patch
On 02.01.11 Norbert Preining (prein...@logic.at) wrote: On Fr, 31 Dez 2010, Hilmar Preusse wrote: Happy new year, Not good[TM]. I'll open a wishlist bug to have that changed. Should be that hard to source /etc/texmf/texmf.cnf at the beginning of these Can you transplant the X hierarchy somewhere else? I suspect not. Can you move /usr/share/gnome-* somewhere else? I suspect not. I didn't check, but I suspect these packages don't even pretend this would be possible. We have a config file where things can be changed and it may happen that people expect this can be done. And yes: I don't see either a good reason to do so. H. -- sigmentation fault -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#608689: RM: pytris -- security issues; abandoned upstream
On Sun, Jan 02, 2011 at 08:14:17PM +0200, Stefano Rivera wrote: Package: pytris Version: 0.98+nmu1 Severity: grave Tags: security Justification: user security hole The setgid wrapper for this game makes no attempt at security. ... I believe the best solution is removal, from unstable, squeeze, and lenny. Radovan, are you OK with reassigning this to ftp.debian.org? Yes, that is probably something that I should have made earlier. (and I think it is time to go through my older packages and see which of them are no more relevant) -- --- | Radovan Garabík http://kassiopeia.juls.savba.sk/~garabik/ | | __..--^^^--..__garabik @ kassiopeia.juls.savba.sk | --- Antivirus alert: file .signature infected by signature virus. Hi! I'm a signature virus! Copy me into your signature file to help me spread! signature.asc Description: Digital signature
Processed: Re: Bug#608689: RM: pytris -- security issues; abandoned upstream
Processing commands for cont...@bugs.debian.org: retitle 608689 RM: pytris -- RoM; security issues; abandoned upstream Bug #608689 [pytris] RM: pytris -- security issues; abandoned upstream Changed Bug title to 'RM: pytris -- RoM; security issues; abandoned upstream' from 'RM: pytris -- security issues; abandoned upstream' clone 608689 -1 Bug#608689: RM: pytris -- RoM; security issues; abandoned upstream Bug 608689 cloned as bug 608740. reassign 608689 ftp.debian.org Bug #608689 [pytris] RM: pytris -- RoM; security issues; abandoned upstream Bug reassigned from package 'pytris' to 'ftp.debian.org'. Bug No longer marked as found in versions pytris/0.98+nmu1. reassign -1 release.debian.org Bug #608740 [pytris] RM: pytris -- RoM; security issues; abandoned upstream Bug reassigned from package 'pytris' to 'release.debian.org'. Bug No longer marked as found in versions pytris/0.98+nmu1. user release.debian@packages.debian.org Setting user to release.debian@packages.debian.org (was stef...@rivera.za.net). usertag -1 rm Bug#608740: RM: pytris -- RoM; security issues; abandoned upstream There were no usertags set. Usertags are now: rm. thanks Stopping processing here. Please contact me if you need assistance. -- 608740: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=608740 608689: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=608689 -1: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=-1 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#603986: qgis crashes on startup on PowerPC
tags 603986 patch
thanks
Hi,
On Sat, 1 Jan 2011 12:00:28 +0100
Gabriele Giacone 1o5g4...@gmail.com wrote:
I confirm it starts properly on ppc with -fno-strict-aliasing.
Attached patch.
me too, and I tried to apply the change for powerpc only.
Here's a proposed patch.
diff -u qgis-1.4.0+12730/debian/control qgis-1.4.0+12730/debian/control
--- qgis-1.4.0+12730/debian/control
+++ qgis-1.4.0+12730/debian/control
@@ -73,7 +73,7 @@
Package: qgis-plugin-grass
Architecture: any
-Depends: qgis (= ${binary:Version}), qgis-plugin-grass-common (=
${source:Version}), ${shlibs:Depends}, ${misc:Depends}, libgdal1-1.6.0-grass,
grass640-6
+Depends: qgis (= ${binary:Version}), qgis-plugin-grass-common (=
${source:Version}), ${shlibs:Depends}, ${misc:Depends}, libgdal1-1.6.0-grass,
grass
Description: GRASS plugin for Quantum GIS
Quantum GIS is a Geographic Information System (GIS) which manages, analyzes
and display databases of geographic information.
diff -u qgis-1.4.0+12730/debian/rules qgis-1.4.0+12730/debian/rules
--- qgis-1.4.0+12730/debian/rules
+++ qgis-1.4.0+12730/debian/rules
@@ -8,6 +8,8 @@
# 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_HOST_ARCH ?= $(shell dpkg-architecture -qDEB_HOST_ARCH)
+
QGIS_MAJOR=$(shell sed -ne 's/SET(CPACK_PACKAGE_VERSION_MAJOR
\([0-9]*\))/\1/p' CMakeLists.txt)
QGIS_MINOR=$(shell sed -ne 's/SET(CPACK_PACKAGE_VERSION_MINOR
\([0-9]*\))/\1/p' CMakeLists.txt)
@@ -50,6 +52,10 @@
LDFLAGS += -pg
endif
+ifneq (,$(findstring powerpc,$(DEB_HOST_ARCH)))
+ CFLAGS += -fno-strict-aliasing
+endif
+
define gentemplate
$(2): $(1)
sed \
diff -u qgis-1.4.0+12730/debian/changelog qgis-1.4.0+12730/debian/changelog
--- qgis-1.4.0+12730/debian/changelog
+++ qgis-1.4.0+12730/debian/changelog
@@ -1,3 +1,11 @@
+qgis (1.4.0+12730-3.1) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * set CFLAGS += -fno-strict-aliasing for powerpc to avoid crash
+Thanks to Gabriele Giacone 1o5g4...@gmail.com (Closes: #603986)
+
+ -- Hideki Yamane henr...@debian.org Mon, 03 Jan 2011 15:26:16 +0900
+
qgis (1.4.0+12730-3) unstable; urgency=low
* Updated debian/control for current Grass snapshot.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#603986: qgis crashes on startup on PowerPC
Processing commands for cont...@bugs.debian.org: tags 603986 patch Bug #603986 [qgis] qgis crashes on startup on PowerPC Added tag(s) patch. thanks Stopping processing here. Please contact me if you need assistance. -- 603986: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=603986 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#608568: bup: needs tight dependency on python
On Sat, Jan 01, 2011 at 04:54:35PM +0100, Jakub Wilk wrote: bup builds a private Python extension[0]. Such extensions are normally not binary compatible across different Python versions, so the package must declare tight dependency on the version for which the extension was built. The attached patch fixes this bug. Thanks - I've uploaded a 0.16b-2squeeze1 carrying this patch to testing-proposed-updates. I'm finishing another packaging change before I upload a new sid package, but it will carry this too. -- Jon Dowland signature.asc Description: Digital signature
Bug#607857: tex-common: Hard-coded path in proposed patch
On Mon, Jan 03, 2011 at 09:41:04AM +0100, Hilmar Preusse wrote:
Happy new year,
Not good[TM]. I'll open a wishlist bug to have that changed. Should
be that hard to source /etc/texmf/texmf.cnf at the beginning of these
Can you transplant the X hierarchy somewhere else? I suspect not.
Can you move /usr/share/gnome-* somewhere else? I suspect not.
I didn't check, but I suspect these packages don't even pretend this
would be possible. We have a config file where things can be changed
and it may happen that people expect this can be done.
And yes: I don't see either a good reason to do so.
Happy new year to all, too!
Most significantly, the tex-common postinst is designed to handle the
installation of new files through the package maintenance system. The
files in those packages will be installed into the standard places on
the system, and tex-common behaves accordingly:
/usr/share/texmf{,-texlive} and /var/lib/texmf are the directories
handled by packages, and therefore tex-common should use those same
directories.
If a sysadmin wished to change this, they would have to divert every
single package installation - I can imagine this being painful and
pointless
Ho hum
Incidentally, the advice about using --nohash should be included in
the Debian TeX Policy so that other packages don't stumble upon this
bug.
Julian
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#594967: Bug #594967: [poulsbo] grub-pc Hangs After Welcome to GRUB!
On Mon, Jan 03, 2011 at 12:13:01AM +, Colin Watson wrote: Whoops, I forgot to right-shift the header word. Can you try 4.iso instead, at the same location? I also made it handle PCI-to-CardBus bridges the same way as PCI-to-PCI bridges since that's what pciutils does. (In addition to 'set debug=pci', I'd recommend also doing 'set pager=1' so that lspci's output will be paged.) 4.iso: grub set debug=pci grub set pager=1 grub lspci bus/pci.c:92: bus 0x0 00:00.0 8086:8100 [0600] Host Bridge 00:02.0 8086:8108 [0300] VGA Controller 00:1b.0 8086:811b [0403] Multimedia device bus/pci.c:143: bridge range 0x2-0x2 00:1c.0 8086:8110 [0604] PCI-PCI Bridge bus/pci.c:143: bridge range 0x3-0x3 00:1c.1 8086:8112 [0604] PCI-PCI Bridge 00:1d.0 8086:8114 [0c03] USB Controller 00:1d.1 8086:8115 [0c03] USB Controller 00:1d.2 8086:8116 [0c03] USB Controller 00:1d.7 8086:8117 [0c03] USB Controller [PI 20] 00:1f.0 8086:8119 [0601] ISA Bridge 00:1f.1 8086:811a [0101] IDE Controller [PI 80] bus/pci.c:92: bus 0x2 02:00.0 10ec:8136 [0200] Ethernet Controller bus/pci.c:92: bus 0x3 03:00.0 168c:001c [0200] Ethernet Controller grub -- Steve McIntyre, Cambridge, UK.st...@einval.com Because heaters aren't purple! -- Catherine Pitt -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: Grub installed to wrong disk
Processing commands for cont...@bugs.debian.org: severity 603942 serious Bug #603942 [grub-installer] installation-report: Grub installed to wrong disk Severity set to 'serious' from 'critical' merge 568529 603942 Bug#568529: overwrites MBR of installation medium Bug#603942: installation-report: Grub installed to wrong disk Bug#579519: grub-installer - Overwrites bootloaders on different device Bug#589823: debian-installer (squeeze alpha): Writes grub on usb-stic with installer Bug#604992: Installs GRUB on USB stick during a USB install Bug#605562: installation-report: Installation from usb stick lead to unbootable system (und unbootable usb stick) Merged 568529 579519 589823 603942 604992 605562. thanks Stopping processing here. Please contact me if you need assistance. -- 605562: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=605562 589823: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=589823 568529: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=568529 604992: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=604992 579519: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=579519 603942: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=603942 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#608793: Upgrade deletes symlinks /usr/share/zoneminder/events and ../images, replacing with hard dirs.
Package: zoneminder Version: 1.24.2-7 Severity: grave Justification: causes non-serious data loss Like many zoneminder users wanting to use a dedicated mount for cctv storage, I replace /usr/share/zoneminder/events and images with symlinks to the right place (ie, a bigger drive not in /usr) zoneminder upgrade silently deletes these symlinks and recreates the original hard directories there. zoneminder then restarts and zmaudit can no longer find the associated files so kills the events database entries. Result - total emptying of zoneminder database and non-recovery of sorted events, including those archived. Lost three weeks recordings (2tb) data from an entire site, plus archives going back for a year. :( Please include tests for symlinks and leave in place if found. Thanks. -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.26-2-686 (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages zoneminder depends on: ii apache22.2.9-10+lenny7 Apache HTTP Server metapackage ii apache2-mpm-prefork [a 2.2.9-10+lenny7 Apache HTTP Server - traditional n ii ffmpeg 4:0.5.2-6 multimedia player, server and enco ii libapache2-mod-php55.3.3-6 server-side, HTML-embedded scripti pn libarchive-tar-perlnone(no description available) ii libarchive-zip-perl1.30-3Perl module for manipulation of ZI ii libavcodec52 4:0.5.2-6 ffmpeg codec library ii libavformat52 4:0.5.2-6 ffmpeg file format library ii libavutil494:0.5.2-6 ffmpeg utility library ii libc6 2.11.2-7 Embedded GNU C Library: Shared lib ii libdate-manip-perl 6.11-1module for manipulating dates ii libdevice-serialport-p 1.04-2+b1 emulation of Win32::SerialPort for ii libdirac-encoder0 1.0.2-3 open and royalty free high quality ii libgcc11:4.4.5-8 GCC support library ii libgnutls262.8.6-1 the GNU TLS library - runtime libr ii libjpeg62 6b1-1 The Independent JPEG Group's JPEG ii libjs-mootools 1.2.4.0~debian1-1 compact JavaScript framework ii libmime-lite-perl 3.027-1 module for convenient MIME message ii libmime-tools-perl 5.428-1 Perl5 modules for MIME-compliant m ii libmysqlclient16 5.1.49-3 MySQL database client library ii libpcre3 8.02-1.1 Perl 5 Compatible Regular Expressi ii libphp-serialization-p 0.34-1Perl module to manipulate serializ ii libstdc++6 4.4.5-8 The GNU Standard C++ Library v3 ii libswscale04:0.5.2-6 ffmpeg video scaling library ii libwww-perl5.836-1 Perl HTTP/WWW client/server librar ii mysql-client-5.0 [mysq 5.0.51a-24+lenny3 MySQL database client binaries ii mysql-server 5.0.51a-24+lenny3 MySQL database server (metapackage ii mysql-server-5.0 [mysq 5.0.51a-24+lenny3 MySQL database server binaries ii perl-modules [libmodul 5.10.1-16 Core Perl modules ii php5 5.3.3-6 server-side, HTML-embedded scripti ii php5-mysql 5.3.3-6 MySQL module for php5 ii rsyslog [system-log-da 4.6.4-2 enhanced multi-threaded syslogd ii zip3.0-3 Archiver for .zip files ii zlib1g 1:1.2.3.4.dfsg-3 compression library - runtime zoneminder recommends no packages. zoneminder suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#594967: Bug #594967: [poulsbo] grub-pc Hangs After Welcome to GRUB!
On Mon, Jan 03, 2011 at 11:04:17AM +, Steve McIntyre wrote:
On Mon, Jan 03, 2011 at 12:13:01AM +, Colin Watson wrote:
Whoops, I forgot to right-shift the header word. Can you try 4.iso
instead, at the same location? I also made it handle PCI-to-CardBus
bridges the same way as PCI-to-PCI bridges since that's what pciutils
does.
(In addition to 'set debug=pci', I'd recommend also doing 'set pager=1'
so that lspci's output will be paged.)
4.iso:
grub set debug=pci
grub set pager=1
grub lspci
bus/pci.c:92: bus 0x0
00:00.0 8086:8100 [0600] Host Bridge
00:02.0 8086:8108 [0300] VGA Controller
00:1b.0 8086:811b [0403] Multimedia device
bus/pci.c:143: bridge range 0x2-0x2
00:1c.0 8086:8110 [0604] PCI-PCI Bridge
bus/pci.c:143: bridge range 0x3-0x3
00:1c.1 8086:8112 [0604] PCI-PCI Bridge
00:1d.0 8086:8114 [0c03] USB Controller
00:1d.1 8086:8115 [0c03] USB Controller
00:1d.2 8086:8116 [0c03] USB Controller
00:1d.7 8086:8117 [0c03] USB Controller [PI 20]
00:1f.0 8086:8119 [0601] ISA Bridge
00:1f.1 8086:811a [0101] IDE Controller [PI 80]
bus/pci.c:92: bus 0x2
02:00.0 10ec:8136 [0200] Ethernet Controller
bus/pci.c:92: bus 0x3
03:00.0 168c:001c [0200] Ethernet Controller
grub
This looks right to me. Excellent. Vladimir, how does this patch look,
on top of my previous one? (This is edited slightly relative to what
Steve tested, to make sure that the bus number never overflows
bus_present; this will never happen on x86 but might happen on other
architectures. I've smoke-tested this change.)
2011-01-03 Colin Watson cjwat...@ubuntu.com
* grub-core/bus/pci.c (grub_pci_iterate): Only scan bus 0 plus any
buses linked by PCI-to-PCI or PCI-to-CardBus bridges.
* include/grub/pci.h: Add definitions for bridges.
=== modified file 'grub-core/bus/pci.c'
--- grub-core/bus/pci.c 2010-06-30 00:30:05 +
+++ grub-core/bus/pci.c 2011-01-03 00:05:27 +
@@ -20,6 +20,7 @@
#include grub/dl.h
#include grub/pci.h
#include grub/mm.h
+#include grub/misc.h
/* FIXME: correctly support 64-bit architectures. */
/* #if GRUB_TARGET_SIZEOF_VOID_P == 4 */
@@ -78,9 +79,18 @@ grub_pci_iterate (grub_pci_iteratefunc_t
grub_pci_address_t addr;
grub_pci_id_t id;
grub_uint32_t hdr;
+ grub_uint8_t bus_present[(GRUB_PCI_NUM_BUS + 7) / 8];
+
+ grub_memset (bus_present, 0, sizeof (bus_present));
+ bus_present[0] = 1; /* bus 0 is always enabled */
for (dev.bus = 0; dev.bus GRUB_PCI_NUM_BUS; dev.bus++)
{
+ if (!(bus_present[dev.bus / 8] (1 (dev.bus % 8
+ continue;
+
+ grub_dprintf (pci, bus 0x%x\n, dev.bus);
+
for (dev.device = 0; dev.device GRUB_PCI_NUM_DEVICES; dev.device++)
{
for (dev.function = 0; dev.function 8; dev.function++)
@@ -112,6 +119,38 @@ grub_pci_iterate (grub_pci_iteratefunc_t
continue;
#endif
+ /* On bus 0, look for PCI-to-PCI bridges and mark all buses
+within their ranges as present. */
+ if (dev.bus == 0)
+ {
+ addr = grub_pci_make_address (dev, GRUB_PCI_REG_CACHELINE);
+ hdr = grub_pci_read (addr);
+
+ switch ((hdr 16) 0x7F) {
+ case GRUB_PCI_HEADER_PCI_BRIDGE:
+ case GRUB_PCI_HEADER_CARDBUS_BRIDGE:
+ {
+ grub_uint32_t bus_numbers;
+ grub_uint32_t secondary, subordinate, i;
+
+ addr = grub_pci_make_address
+ (dev, GRUB_PCI_REG_SEC_LAT_TIMER);
+ bus_numbers = grub_pci_read (addr);
+ secondary = (bus_numbers 8) 0xFF;
+ subordinate = (bus_numbers 16) 0xFF;
+
+ grub_dprintf (pci, bridge range 0x%x-0x%x\n,
+ secondary, subordinate);
+
+ for (i = secondary;
+i = subordinate i GRUB_PCI_NUM_BUS; i++)
+ bus_present[i / 8] |= (1 (i % 8));
+
+ break;
+ }
+ }
+ }
+
if (hook (dev, id))
return;
=== modified file 'include/grub/pci.h'
--- include/grub/pci.h 2010-08-11 02:18:07 +
+++ include/grub/pci.h 2011-01-02 17:32:28 +
@@ -68,6 +68,24 @@
#define GRUB_PCI_REG_MIN_GNT 0x3e
#define GRUB_PCI_REG_MAX_LAT 0x3f
+/* Alternative register meanings if header type is 1 (PCI-to-PCI bridge). */
+#define GRUB_PCI_REG_SEC_LAT_TIMER 0x18
+#define GRUB_PCI_REG_SUB_BUS_NUMBER0x19
+#define GRUB_PCI_REG_SEC_BUS_NUMBER0x1a
+#define GRUB_PCI_REG_PRI_BUS_NUMBER0x1b
+#define GRUB_PCI_REG_SEC_STATUS0x1c
+#define GRUB_PCI_REG_IO_LIMIT 0x1e
+#define GRUB_PCI_REG_IO_BASE 0x1f
+#define GRUB_PCI_REG_MEM_LIMIT 0x20
+#define
Bug#603942: Grub installed to wrong disk
found 603942 1.57 merge 568529 603942 thanks Hello Christian Perrier, I found this bug still beeing present in beta2 installer using grub-installer 1.57 (See #605562). Bug 603942 seems to be another duplicate of #568529, so I merge them. Best Regards Joachim -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#605562: installation-report: Installation from usb stick lead, to unbootable system (und unbootable usb stick)
Processing commands for cont...@bugs.debian.org: severity 568529 serious Bug #568529 [grub-installer] overwrites MBR of installation medium Bug #579519 [grub-installer] grub-installer - Overwrites bootloaders on different device Bug #589823 [grub-installer] debian-installer (squeeze alpha): Writes grub on usb-stic with installer Bug #604992 [grub-installer] Installs GRUB on USB stick during a USB install Bug #605562 [grub-installer] installation-report: Installation from usb stick lead to unbootable system (und unbootable usb stick) Severity set to 'serious' from 'important' Severity set to 'serious' from 'important' Severity set to 'serious' from 'important' Severity set to 'serious' from 'important' Severity set to 'serious' from 'important' tags 568529 - moreinfo Bug #568529 [grub-installer] overwrites MBR of installation medium Bug #579519 [grub-installer] grub-installer - Overwrites bootloaders on different device Bug #589823 [grub-installer] debian-installer (squeeze alpha): Writes grub on usb-stic with installer Bug #604992 [grub-installer] Installs GRUB on USB stick during a USB install Bug #605562 [grub-installer] installation-report: Installation from usb stick lead to unbootable system (und unbootable usb stick) Removed tag(s) moreinfo. Removed tag(s) moreinfo. Removed tag(s) moreinfo. Removed tag(s) moreinfo. Removed tag(s) moreinfo. thanks Stopping processing here. Please contact me if you need assistance. -- 568529: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=568529 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed (with 1 errors): Re: Grub installed to wrong disk
Processing commands for cont...@bugs.debian.org: found 603942 1.57 Bug #603942 [grub-installer] installation-report: Grub installed to wrong disk Bug Marked as found in versions grub-installer/1.57; no longer marked as fixed in versions grub-installer/1.57. merge 568529 603942 Bug#568529: overwrites MBR of installation medium Bug#603942: installation-report: Grub installed to wrong disk Mismatch - only Bugs in same state can be merged: Values for `severity' don't match: #568529 has `important'; #603942 has `critical' thanks Stopping processing here. Please contact me if you need assistance. -- 603942: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=603942 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#608794: libsnmp-dev: Missing depends on libperl-dev
Package: libsnmp-dev Version: 5.4.3~dfsg-1 Severity: serious Hi, Your package is shipping .la files in which contain lines like this: libnetsnmpagent.la:dependency_libs=' /usr/lib/libnetsnmp.la -lcrypto -lwrap -L/usr/local/lib -L/usr/lib/perl/5.10/CORE -lperl -ldl -lm -lpthread -lc -lcrypt' libnetsnmphelpers.la:dependency_libs=' /usr/lib/libnetsnmpagent.la -lwrap -L/usr/local/lib -L/usr/lib/perl/5.10/CORE -lperl -ldl -lm -lpthread -lc -lcrypt /usr/lib/libnetsnmp.la -lcrypto' libnetsnmpmibs.la:dependency_libs=' /usr/lib/libnetsnmphelpers.la -L/usr/local/lib -L/usr/lib/perl/5.10/CORE /usr/lib/libnetsnmpagent.la -lwrap -lperl -lm -lpthread -lc -lcrypt /usr/lib/libnetsnmp.la -lcrypto -ldl -lsensors' libnetsnmptrapd.la:dependency_libs=' /usr/lib/libnetsnmpmibs.la /usr/lib/libnetsnmphelpers.la -L/usr/local/lib -L/usr/lib/perl/5.10/CORE /usr/lib/libnetsnmpagent.la -lwrap -lsensors /usr/lib/libnetsnmp.la -lcrypto -lperl -ldl -lm -lpthread -lc -lcrypt' This means that you're telling other packages to link to all those libraries. You seem to have Depends for most of them, but atleast libperl-dev seems to be missing. Kurt -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#591782: ccid: FTBFS on kfreebsd-*: configure: error: libusb.h not found
Processing commands for cont...@bugs.debian.org: fixed 591782 1.4.1-1 Bug #591782 [src:ccid] ccid: FTBFS on kfreebsd-*: configure: error: libusb.h not found Bug Marked as fixed in versions ccid/1.4.1-1. thank Stopping processing here. Please contact me if you need assistance. -- 591782: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=591782 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#591782: marked as done (ccid: FTBFS on kfreebsd-*: configure: error: libusb.h not found)
Your message dated Mon, 3 Jan 2011 16:04:10 +0100 with message-id aanlkti=nwqezbn5lmdzaewobvgqd5igxe2ul8ttqb...@mail.gmail.com and subject line Re: Bug#591782: ccid: FTBFS on kfreebsd-*: configure: error: libusb.h not found has caused the Debian Bug report #591782, regarding ccid: FTBFS on kfreebsd-*: configure: error: libusb.h not found 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 this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 591782: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=591782 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: ccid Version: 1.4.0-1 Severity: serious Justification: FTBFS User: debian-...@lists.debian.org Usertags: kfreebsd Hi, your package no longer builds on kfreebsd-*: | checking for LIBUSB... yes | checking libusb-1.0/libusb.h usability... no | checking libusb-1.0/libusb.h presence... no | checking for libusb-1.0/libusb.h... no | configure: error: libusb.h not found, install libusb or use ./configure LIBUSB_CFLAGS=... | == config.log == Full build logs: https://buildd.debian.org/status/package.php?p=ccidsuite=experimental Mraw, KiBi. ---End Message--- ---BeginMessage--- fixed 591782 1.4.1-1 thank 2010/8/5 Cyril Brulebois k...@debian.org: Source: ccid Version: 1.4.0-1 Severity: serious Justification: FTBFS User: debian-...@lists.debian.org Usertags: kfreebsd Hi, your package no longer builds on kfreebsd-*: | checking for LIBUSB... yes | checking libusb-1.0/libusb.h usability... no | checking libusb-1.0/libusb.h presence... no | checking for libusb-1.0/libusb.h... no | configure: error: libusb.h not found, install libusb or use ./configure LIBUSB_CFLAGS=... | == config.log == Full build logs: https://buildd.debian.org/status/package.php?p=ccidsuite=experimental This bug has been fixed in upstream release 1.4.1 but I forgot to close this bug in the debian/changelog. Bye -- Dr. Ludovic Rousseau ---End Message---
Bug#608801: Fails to build on i386
Package: u-boot Version: 2010.12-1 Severity: serious Tags: patch User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu ubuntu-patch natty Hey u-boot fails to build on i386: https://buildd.debian.org/fetch.cgi?pkg=u-boot;ver=2010.12-1;arch=i386;stamp=1293575883 make[1]: Entering directory `/build/buildd-u-boot_2010.12-1-i386-2mPTrO/u-boot-2010.12' gcc -DDO_DEPS_ONLY \ -g -Os -ffunction-sections -fvisibility=hidden -D__KERNEL__ -DCONFIG_SYS_TEXT_BASE=0x0600 -I/build/buildd-u-boot_2010.12-1-i386-2mPTrO/u-boot-2010.12/include -fno-builtin -ffreestanding -nostdinc -isystem /usr/lib/gcc/i486-linux-gnu/4.4.5/include -pipe -fno-strict-aliasing -Wstrict-prototypes -mregparm=3 -fomit-frame-pointer -ffreestanding -fno-toplevel-reorder -fno-stack-protector -mpreferred-stack-boundary=2 -DCONFIG_I386 -D__I386__ -march=i386 -Werror -fno-dwarf2-cfi-asm -Wall -Wstrict-prototypes -fno-stack-protector \ -o lib/asm-offsets.s lib/asm-offsets.c -c -S lib/asm-offsets.c: In function 'main': lib/asm-offsets.c:25: error: invalid application of 'sizeof' to incomplete type 'struct global_data' make[1]: *** [lib/asm-offsets.s] Error 1 I reported this issue upstream a couple of weeks ago and I've just sent a patch which I'm attaching here. I'm raising this as serious despite the fact that u-boot is a new package in Debian because this provides the build of mkimage which is a dependency of other packages in the archive (it used to be provided by uboot-mkimage which is pending removal). Cheers, -- Loïc Minier -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#605912: runit: Upgrade failure lenny - squeeze
tags 605912 patch
thanks
Hi,
I guess it is due to lack of flag in debconf templates file.
Here's a proposal patch, it works in my chroot environment.
diff -u runit-2.1.1/debian/runit.templates.in
runit-2.1.1/debian/runit.templates.in
--- runit-2.1.1/debian/runit.templates.in
+++ runit-2.1.1/debian/runit.templates.in
@@ -11,0 +12,4 @@
+
+Template: runit-run/install
+Type: boolean
+Default: false
diff -u runit-2.1.1/debian/control runit-2.1.1/debian/control
--- runit-2.1.1/debian/control
+++ runit-2.1.1/debian/control
@@ -7,7 +7,7 @@
Package: runit
Architecture: any
-Depends: procps, ${shlibs:Depends}
+Depends: procps, ${shlibs:Depends}, debconf (= 0.5) | debconf-2.0
Recommends: fgetty
Suggests: runit-run, socklog-run
Description: system-wide service supervision
diff -u runit-2.1.1/debian/changelog runit-2.1.1/debian/changelog
--- runit-2.1.1/debian/changelog
+++ runit-2.1.1/debian/changelog
@@ -1,3 +1,13 @@
+runit (2.1.1-6.2) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * debian/control
+- add missing depenedency debconf (= 0.5) | debconf-2.0
+ * debian/runit.templates.in
+- add runit-run/install (Closes: #605912)
+
+ -- Hideki Yamane henr...@debian.org Tue, 04 Jan 2011 01:06:45 +0900
+
runit (2.1.1-6.1) unstable; urgency=low
* Non-Maintainer Upload.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#608801: Fails to build on i386
On Mon, Jan 03, 2011, Loïc Minier wrote:
I reported this issue upstream a couple of weeks ago and I've just sent
a patch which I'm attaching here.
Actually attaching the patch --
--
Loïc Minier
From e8c5ca62988a692559ad1efd74a4bfc4537dcf29 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Lo=C3=AFc=20Minier?= loic.min...@linaro.org
Date: Mon, 3 Jan 2011 16:39:36 +0100
Subject: [PATCH] Use sizeof(gd_t), not sizeof(struct global_data)
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
The eNET (x86) build fails with invalid application of 'sizeof' to
incomplete type 'struct global_data' because x86 doesn't define
struct global_data. Change sizeof(struct global_data) to sizeof(gd_t)
which is always available.
Cc: Graeme Russ graeme.r...@gmail.com
Signed-off-by: Loïc Minier loic.min...@linaro.org
---
lib/asm-offsets.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/lib/asm-offsets.c b/lib/asm-offsets.c
index 2209561..6a4084e 100644
--- a/lib/asm-offsets.c
+++ b/lib/asm-offsets.c
@@ -23,7 +23,7 @@ int main(void)
{
/* Round up to make sure size gives nice stack alignment */
DEFINE(GENERATED_GBL_DATA_SIZE,
- (sizeof(struct global_data)+15) ~15);
+ (sizeof(gd_t)+15) ~15);
return 0;
}
--
1.7.2.3
Bug#606950: sd_mod: Unknown symbol blk_queue_physical_block_size_fixed
I have the same problem when trying to install with http://ftp.fi.debian.org/debian/dists/testing/main/installer- armel/current/images/kirkwood/netboot/marvell/sheevaplug/uImage and http://ftp.fi.debian.org/debian/dists/testing/main/installer- armel/current/images/kirkwood/netboot/marvell/sheevaplug/uInitrd (the files are dated 28-Nov-2010 04:12) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#606950: sd_mod: Unknown symbol blk_queue_physical_block_size_fixed
On Mon, 2011-01-03 at 19:36 +0200, Mikko Tuumanen wrote: I have the same problem when trying to install with http://ftp.fi.debian.org/debian/dists/testing/main/installer- armel/current/images/kirkwood/netboot/marvell/sheevaplug/uImage and http://ftp.fi.debian.org/debian/dists/testing/main/installer- armel/current/images/kirkwood/netboot/marvell/sheevaplug/uInitrd (the files are dated 28-Nov-2010 04:12) Those are the installer kernel and initrd, which are an older version than the kernel and modules that get installed in the filesystem. You then need to run flash-kernel to copy the kernel into the proper flash partition. (I don't know why that isn't being done automatically but it's unlikely to be a kernel bug.) Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. signature.asc Description: This is a digitally signed message part
Bug#606370: CVE-2010-2761 CVE-2010-4410 CVE-2010-4411
On Mon, Dec 27, 2010 at 04:12:16PM +0100, gregor herrmann wrote: tag 606370 + patch tag 606995 + patch thanks On Mon, 27 Dec 2010 16:23:40 +0200, Niko Tyni wrote: http://security-tracker.debian.org/tracker/CVE-2010-2761 http://security-tracker.debian.org/tracker/CVE-2010-4410 http://security-tracker.debian.org/tracker/CVE-2010-4411 I'm not quite sure yet what CVE-2010-4411 refers to. It seems that the fix for CVE-2010-2761 was not complete, but it is not a different, new issue? https://github.com/markstos/CGI.pm/commit/77b3b2056c003edee034a2a890212edab800900d Thanks for digging this out; I was looking a few times and never understood CVE-2010-4411 ... Assuming this is the case, I'm attaching preliminary patches for Thanks! I haven't looked at libcgi-simple-perl at all. I think Damyan has started to look at it. Could you upload the fixes targeted at squeeze to tpu? Cheers, Moritz -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#608793: Upgrade deletes symlinks /usr/share/zoneminder/events and ../images, replacing with hard dirs.
On Mon, Jan 03, 2011 at 01:15:17PM +, Simon Avery wrote: Like many zoneminder users wanting to use a dedicated mount for cctv storage, I replace /usr/share/zoneminder/events and images with symlinks to the right place (ie, a bigger drive not in /usr) /usr/share/zoneminder/events is a symlink to /var/cache/zoneminder/events in the package, though the same issue could come up for /var. what about mounting /var/cache/zoneminder/events directly (either on it's own filesystem, or using bind mounts), rather than mucking around with symlinks? zoneminder upgrade silently deletes these symlinks and recreates the original hard directories there. i believe this happens at the dpkg level, so might be hard or inappropriate to fix in zoneminder. zoneminder then restarts and zmaudit can no longer find the associated files so kills the events database entries. Result - total emptying of zoneminder database and non-recovery of sorted events, including those archived. Lost three weeks recordings (2tb) data from an entire site, plus archives going back for a year. :( ouch! this seems like a pretty severe way to handle all the files disappearing. will try and reproduce and see if there's a way to detect and avert this situation. just to be clear, it deleted the database entries for the recordings, and not the actual files? Please include tests for symlinks and leave in place if found. while it certainly shouldn't purge cached data so unconditionally, i'm not sure what zoneminder can do when dpkg-managed symlinks and directories are changed manually. so i think we'd have to come up with some alternate method. live well, vagrant -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#605240: tenshi: fails to upgrade from lenny
On Mon, Dec 27, 2010 at 18:27, gregor herrmann gre...@debian.org wrote: What keeps me from uploading is that - Ansgar was dealing with this package already - I'm not sure if the changes are not a bit too much for a freeze exception at that point Hi gregor, Sorry for the late response. I just came back yesterday from my holidays to see that Ansgar had uploaded my package. Now that you say it, I must admit that I am quite afraid that the changes might be too important for a freeze-exception. Anyways, I have just requested a freeze-exception [1]. I cross my fingers for it to be granted.. :) Cheers, Ignace M [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=608827 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#606950: sd_mod: Unknown symbol blk_queue_physical_block_size_fixed
Those are the installer kernel and initrd, which are an older version than the kernel and modules that get installed in the filesystem. You I want to install to a usb stick and I can't because sd_mod doesn't load. # modprobe sd_mod FATAL: Error inserting sd_mod (/lib/modules/2.6.32-5- kirkwood/kernel/drivers/scsi/sd_mod.ko): Unknown symbol in module, or unknown parameter (see dmesg) [ 374.383993] sd_mod: Unknown symbol blk_queue_physical_block_size_fixed Should this bug report then be filed against the installer? -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: tagging 607967
Processing commands for cont...@bugs.debian.org: tags 607967 + patch Bug #607967 [src:cdebconf-terminal] cdebconf-terminal: FTBFS on all architectures (missing aclocal) Added tag(s) patch. thanks Stopping processing here. Please contact me if you need assistance. -- 607967: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=607967 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#608467: kmail: Content of messages is not displayed although subjects are visible
Hi there, When using kmail to display IMAP mails the content of the mail is not visible although the subjects are listed an can be selected. Does this happens allways to you? It sometimes happens to me, but not allways, in kmail 4:3.5.9-5... Does this happens in all messages, or only in the ones with attachments[1]? [1] http://bugs.kde.org/show_bug.cgi?id=250459 -- Marcos Marado -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#608655: scotch and gbase: error when trying to install together
Hi there, The problem is in scotch, that changed all the binary names from scotch_$binary to just $binary (see [1]). The gbase in scotch is completely different than the one from the gbase package. My first idea would be to just revert the gbase name change on scotch, but looking at gbase on debian... It hasn't been updated, upstream didn't release anything since 2007 and is now 404'd. No package depends on it. Popcon shows[2] only 74 people having it. Shouldn't we just drom gbase from Debian, and add a Conflicts just to make sure machines where gbase is already installed don't suffer from this? [1] http://git.debian.org/?p=debian-science/packages/scotch.git;a=commitdiff;h=00d7dad1884e5db6bd6995cb9e5c21c76c989705 [2] http://qa.debian.org/popcon.php?package=gbase -- Marcos Marado -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#607988: python2.6: the latest update is totally broken and can't byte compile *modules*
severity 607988 grave retitle 607988 python: OSError: [Errno 2] byte-compiling packages on upgrade (dangling symlinks) quit dave b wrote: Setting up python (2.6.6-3+squeeze4) ... Linking and byte-compiling packages for runtime python2.6... Traceback (most recent call last): File /usr/bin/pycompile, line 314, in module main() File /usr/bin/pycompile, line 300, in main options.force, options.optimize, e_patterns) File /usr/bin/pycompile, line 196, in compile ftime = os.stat(fn).st_mtime OSError: [Errno 2] No such file or directory: '/usr/lib/python2.6/dist-packages/bzrlib/plugins/gtk/merge.py' Could you send the relevant portion of /var/log/dpkg.log*? More specifically, I am interested to know what version of python-central is installed when python's postinst runs. See also http://bugs.debian.org/552595 (python-central: please remove dangling symlinks at upgrade). Matthias, maybe something like Conflicts: python-central ( 0.6.15) is needed in the python2.[567]-minimal and python packages to ensure a smooth upgrade? Hope that helps, Jonathan -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: python2.6: the latest update is totally broken and can't byte compile *modules*
Processing commands for cont...@bugs.debian.org: severity 607988 grave Bug #607988 [python2.6] python2.6: the latest update is totally broken and can't byte compile *modules* Severity set to 'grave' from 'critical' retitle 607988 python: OSError: [Errno 2] byte-compiling packages on upgrade (dangling symlinks) Bug #607988 [python2.6] python2.6: the latest update is totally broken and can't byte compile *modules* Changed Bug title to 'python: OSError: [Errno 2] byte-compiling packages on upgrade (dangling symlinks)' from 'python2.6: the latest update is totally broken and can't byte compile *modules*' quit Stopping processing here. Please contact me if you need assistance. -- 607988: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=607988 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#608467: kmail: Content of messages is not displayed although subjects are visible
On Mon, Jan 3, 2011 at 19:22:48 +, Marcos Marado wrote: Hi there, Marcos, if you want the submitter to see your message, you need to cc them explicitly. Cheers, Julien signature.asc Description: Digital signature
Bug#608179: tendra: FTBFS: mv: cannot stat `debian/tendra/usr/share/man/man1/tcc.1': No such file or directory
* Mark Brown broo...@sirena.org.uk, 2010-12-31, 17:46: Clearly this used to work in the past. Putting the block in place so the bugs are linked, but clearly we can bodge around this. If we're going to bodge, though, it's probably more useful to look at the man page and figure out how to tune it to make file happy as that's likely to involve figuring out the ultimate bug with file. Or, better, stop using dh_installmanpages. It's been deprecated for over 6 years for very good reasons. See the attached patch. -- Jakub Wilk diff -u tendra-4.1.2/debian/rules tendra-4.1.2/debian/rules --- tendra-4.1.2/debian/rules +++ tendra-4.1.2/debian/rules @@ -44,7 +44,7 @@ dh_installdocs -a dh_installexamples -a dh_installmenu -a - dh_installmanpages -a + dh_installman -a $(shell find -type f -name '*.[0-9]') mv debian/tendra/usr/bin/tcc debian/tendra/usr/bin/tendracc mv debian/tendra/usr/share/man/man1/tcc.1 debian/tendra/usr/share/man/man1/tendracc.1 rm debian/tendra/usr/bin/trans debian/tendra/usr/share/man/man1/trans.1
Bug#608467: kmail: Content of messages is not displayed although subjects are visible
severity 608467 important thanks Hello, On penktadienis 31 Gruodis 2010 09:27:52 Norbert Schmitz wrote: Package: kmail Version: 4:4.4.7-2 Severity: grave Justification: renders package unusable When using kmail to display IMAP mails the content of the mail is not visible although the subjects are listed an can be selected. This might happen if your Internet connection is flacky. kio_imap4 is known not to recover if your Internet connection was cut for some time (e.g. TCP problems). You have to restart kio_imap4 like close kmail $ killall kio_imap4 (wait until all kio_imap4 processes die, maybe even use $ killall -9 kio_imap4) start kmail ps aux displays many lines in the form norbert 6420 0.0 1.0 98604 33524 ?S08:24 0:00 kdeinit4: kio_imap4 [kdeinit] imaps local:/tmp/ksocket-norbert/klauncherMT4252.slave-socket local:/tmp/ksocket-norbert/kontactFa5061.slave-socket norbert 6434 0.1 1.0 98128 32712 ?S08:25 0:00 kdeinit4: kio_imap4 [kdeinit] imap local:/tmp/ksocket-norbert/klauncherMT4252.slave-socket local:/tmp/ksocket-norbert/kontactag5061.slave-socket That's normal. This bug makes it completely impossible to read mails which renders it unusable for me. What about other mail clients? FWIW, I'm writing this answer from kmail connected to my account via IMAP. So the bug does not everyone and I'm pretty sure the problem is the one I described above. Marking appropriately. -- Modestas Vainius modes...@vainius.eu signature.asc Description: This is a digitally signed message part.
Processed: Re: kmail: Content of messages is not displayed although subjects are visible
Processing commands for cont...@bugs.debian.org: severity 608467 important Bug #608467 [kmail] kmail: Content of messages is not displayed although subjects are visible Severity set to 'important' from 'grave' thanks Stopping processing here. Please contact me if you need assistance. -- 608467: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=608467 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#608793: deletes symlinks /usr/share/zoneminder/events and ../images, replacing with hard dirs.
Package: zoneminder FYI, dpkg should not change symlinks to directories or vice versa. Policy 6.6(4) documents this. In my experience, this works as documented, but dpkg does have bugs of course. Also, I've never used zoneminder, so I don't know what the dirs are for, but from this bug report it sounds like events images contain important data. But you've symlinked them to /var/cache in the package, which is certainly not a good place to store important data! /var/cache must only be used for things your program can regenerate. To quote the FHS, The application must be able to regenerate or restore the data. Unlike /var/spool, the cached files can be deleted without data loss. -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing'), (200, 'unstable'), (100, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.36-trunk-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#606950: sd_mod: Unknown symbol blk_queue_physical_block_size_fixed
* Mikko Tuumanen mikko.tuuma...@utu.fi [2011-01-03 20:57]: Should this bug report then be filed against the installer? A new version of the installer is currently in preparation. When a new version is in preparation, the old version of the netboot images are broken since the kernel and modules get out of sync. Until the new version of the installer is out, you can use the daily installer image from http://people.debian.org/~joeyh/d-i/armel/images/daily/ -- Martin Michlmayr http://www.cyrius.com/ -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#608655: scotch and gbase: error when trying to install together
On Mon, Jan 03, 2011 at 08:16:49PM +, Marcos Marado wrote: Hi there, The problem is in scotch, that changed all the binary names from scotch_$binary to just $binary (see [1]). The gbase in scotch is completely different than the one from the gbase package. My first idea would be to just revert the gbase name change on scotch, but looking at gbase on debian... It hasn't been updated, upstream didn't release anything since 2007 and is now 404'd. No package depends on it. Popcon shows[2] only 74 people having it. Shouldn't we just drom gbase from Debian, and add a Conflicts just to make sure machines where gbase is already installed don't suffer from this? [1] http://git.debian.org/?p=debian-science/packages/scotch.git;a=commitdiff;h=00d7dad1884e5db6bd6995cb9e5c21c76c989705 [2] http://qa.debian.org/popcon.php?package=gbase I'm not impressed with this kind of a reasoning, when http://qa.debian.org/popcon-graph.php?packages=scotch indicates an analogous number of users (109). Frankly, I think it's pretty rude of you to show such blatant disrespect for the existing gbase user base, no matter what its size. -- 2. That which causes joy or happiness. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: RM bug severity
Processing commands for cont...@bugs.debian.org: severity 608740 normal Bug #608740 [release.debian.org] RM: pytris -- RoM; security issues; abandoned upstream Severity set to 'normal' from 'grave' severity 608689 normal Bug #608689 [ftp.debian.org] RM: pytris -- RoM; security issues; abandoned upstream Severity set to 'normal' from 'grave' thanks Stopping processing here. Please contact me if you need assistance. -- 608689: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=608689 608740: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=608740 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#608710: [Debian-med-packaging] Bug#608710: probcons: FTBFS: cp: cannot stat `debian/tmp/pc-project': No such file or directory
Le Sun, Jan 02, 2011 at 11:19:06PM +0100, Andreas Tille a écrit : On Sun, Jan 02, 2011 at 10:34:10PM +0100, Cyril Brulebois wrote: your package FTBFS on a number of archs with: | dh_install | cp: cannot stat `debian/tmp/pc-project': No such file or directory | dh_install: cp -a debian/tmp/pc-project debian/probcons-extra/usr/bin// returned exit code 1 | make: *** [binary-arch] Error 2 Full build logs: https://buildd.debian.org/status/package.php?p=probcons Isn't this the same problem as #607729? If yes, we should upload the current status of SVN. Hi Andreas, it looks like a race condition: in the failing builds, the patches are applied too late. I do not know how to check if parallel build was enabled on the buildds, but I hope that disabling parallel build will solve the problem. Have a nice day, -- Charles -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#608844: pymvpa: FTBFS in sid: error: svm.h: No such file or directory
Source: pymvpa Version: 0.4.5~dev23-2 Tags: sid Severity: serious Justification: fails to build from source pymvpa failed to build from source in a clean sid i386 chroot (it builds fine in squeeze). The interesting parts of the build log: | running build_ext [...] | compile options: '-I/usr/include/numpy -I/usr/include/libsvm-2.0/libsvm -I/usr/include/libsvm -I/usr/local/include/libsvm -I/usr/local/include/libsvm-2.0/libsvm -I/usr/local/include -I/usr/lib/pymodules/python2.5/numpy/core/include -I/usr/include/python2.5 -c' | g++: /build/sbuild-pymvpa_0.4.5~dev23-2-i386-mFuktT/pymvpa-0.4.5~dev23/build/src.linux-i686-2.5/mvpa/clfs/libsvmc/svmc_wrap.cpp | /build/sbuild-pymvpa_0.4.5~dev23-2-i386-mFuktT/pymvpa-0.4.5~dev23/build/src.linux-i686-2.5/mvpa/clfs/libsvmc/svmc_wrap.cpp:2792:17: error: svm.h: No such file or directory | /build/sbuild-pymvpa_0.4.5~dev23-2-i386-mFuktT/pymvpa-0.4.5~dev23/build/src.linux-i686-2.5/mvpa/clfs/libsvmc/svmc_wrap.cpp:2798: error: 'svm_parameter' does not name a type | /build/sbuild-pymvpa_0.4.5~dev23-2-i386-mFuktT/pymvpa-0.4.5~dev23/build/src.linux-i686-2.5/mvpa/clfs/libsvmc/svmc_wrap.cpp:2801: error: ISO C++ forbids declaration of 'svm_node' with no type | /build/sbuild-pymvpa_0.4.5~dev23-2-i386-mFuktT/pymvpa-0.4.5~dev23/build/src.linux-i686-2.5/mvpa/clfs/libsvmc/svmc_wrap.cpp:2801: error: expected ';' before '*' token | /build/sbuild-pymvpa_0.4.5~dev23-2-i386-mFuktT/pymvpa-0.4.5~dev23/build/src.linux-i686-2.5/mvpa/clfs/libsvmc/svmc_wrap.cpp: In function 'PyObject* svm_node_matrix2numpy_array(svm_node**, int, int)': | /build/sbuild-pymvpa_0.4.5~dev23-2-i386-mFuktT/pymvpa-0.4.5~dev23/build/src.linux-i686-2.5/mvpa/clfs/libsvmc/svmc_wrap.cpp:2837: error: invalid use of incomplete type 'struct svm_node' | /build/sbuild-pymvpa_0.4.5~dev23-2-i386-mFuktT/pymvpa-0.4.5~dev23/build/src.linux-i686-2.5/mvpa/clfs/libsvmc/svmc_wrap.cpp:2819: error: forward declaration of 'struct svm_node' | /build/sbuild-pymvpa_0.4.5~dev23-2-i386-mFuktT/pymvpa-0.4.5~dev23/build/src.linux-i686-2.5/mvpa/clfs/libsvmc/svmc_wrap.cpp:2837: error: invalid use of incomplete type 'struct svm_node' | /build/sbuild-pymvpa_0.4.5~dev23-2-i386-mFuktT/pymvpa-0.4.5~dev23/build/src.linux-i686-2.5/mvpa/clfs/libsvmc/svmc_wrap.cpp:2819: error: forward declaration of 'struct svm_node' [...and so on] | error: Command g++ -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall -g -O2 -g -Wall -O2 -fPIC -I/usr/include/numpy -I/usr/include/libsvm-2.0/libsvm -I/usr/include/libsvm -I/usr/local/include/libsvm -I/usr/local/include/libsvm-2.0/libsvm -I/usr/local/include -I/usr/lib/pymodules/python2.5/numpy/core/include -I/usr/include/python2.5 -c /build/sbuild-pymvpa_0.4.5~dev23-2-i386-mFuktT/pymvpa-0.4.5~dev23/build/src.linux-i686-2.5/mvpa/clfs/libsvmc/svmc_wrap.cpp -o /build/sbuild-pymvpa_0.4.5~dev23-2-i386-mFuktT/pymvpa-0.4.5~dev23/./build/temp.linux-i686-2.5/build/sbuild-pymvpa_0.4.5~dev23-2-i386-mFuktT/pymvpa-0.4.5~dev23/build/src.linux-i686-2.5/mvpa/clfs/libsvmc/svmc_wrap.o failed with exit status 1 [...] | make: *** [debian/python-module-stampdir/python-mvpa-lib] Error 1 -- Jakub Wilk -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: tagging 608568
Processing commands for cont...@bugs.debian.org: tags 608568 + pending Bug #608568 [src:bup] bup: needs tight dependency on python Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 608568: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=608568 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#594967: Bug #594967: [poulsbo] grub-pc Hangs After Welcome to GRUB!
On Mon, Jan 03, 2011 at 12:13:01AM +, Colin Watson wrote: On Sun, Jan 02, 2011 at 10:41:50PM +, Steve McIntyre wrote: 2.iso: goes all the way through to bus ff and returns to a grub prompt This is interesting and suggests a measure of coincidence. What that patch did was skip remaining functions on a device that doesn't implement function 0, taking that as an indication that it doesn't exist. This was based on: http://en.wikipedia.org/wiki/PCI_configuration_space#Bus_enumeration Vladimir, are you OK with this change to trunk? 2011-01-02 Colin Watson cjwat...@ubuntu.com * grub-core/bus/pci.c (grub_pci_iterate): Skip remaining functions on devices that do not implement function 0. I've applied this patch to trunk following an ack from Vladimir on IRC. I'll prepare an updated package for unstable shortly. Nevertheless, I'm not confident that this will fix the problem on all machines, so I would like to sort out the bridge handling as well. This may be more complicated than I thought. Seth Goldberg pointed out that my approach fails to deal with peer host bridges correctly (i.e. cases where there are multiple trees, not just a single one rooted at bus 0). Linux deals with this by asking the PCI BIOS for the last bus number, but at this point things get complicated as you have to do things in different ways for different firmware. I am inclined to try the first piece alone and see how this works out, and if we can fix the affected systems by just probing function 0 on every device on every bus then let it stand at that, even if it feels less elegant. Inventing new piles of infrastructure to handle a case I'm unsure about in a subsystem I don't know well isn't my idea of a good time. -- Colin Watson [cjwat...@debian.org] -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#604134: ppc: after debian installation MacOS 9.2 won't recognize, disk anymore
Dear Mr Wittau! To make sure that nothing unexpected will cause you troubles, please read through my complete text first before doing anything: I successfully run Debian Lenny, Mac OS 9, Mac OS X 10.4, and 10.5 on my PowerMac G4/800MHz Quicksilver using just one hard disk drive with various partitions. I can confirm that after an installation of Debian - Debian 5.0.7 Lenny, but such problems also occured with a testing version of Squeeze I tested in August 2010 or so - on a NewWorld PowerPC Macintosh you might run into trouble booting a separate Mac OS 9 OS from a different partition which you had installed before. Please make sure that the program Drive Setup, respectively Laufwerke konfigurieren (German system version of Mac OS 9) recognises the hard disk drive you use, for, actually, there are IDE HDDs which are not supported by this program, and then you cannot use it. As you intend to use yaboot I assume that the HDD is connected with an internal IDE port, i. e. the same hard disk drive(!) might cause troubles if you try to connect it via FireWire in an external case, for in many cases Drive Setup / Laufwerke konfigurieren will not recognize it anymore if connected externally via FireWire. (Problems regarding FireWire support of external hard disk drives and file systems were, however, fixed by Apple in later releases of Mac OS X operating systems, AFAIR.) Quoting wit...@lnxnt.org (wit...@lnxnt.org): the Linux partition was first on the disk, that's what the d-i manual recommends Which manual do you actually refer to? Do you refer to the Debian manual for PowerPC installations? I think that the sequence of partitions used for operating systems should not matter too much, and personally I set up my Linux partitions in the final section of my hard disk drive (at the end of the disk space available). After initializing my HDD with Mac OS 9's Drive Setup / Laufwerke konfigurieren eight partitions were created, and they were named Apple, seven times Macintosh, and 1 x Patch Partition. I did not touch them with the Debian installer, and their sizes only come up to an amount of 25kb to about 300kb, each. It seems that Mac OS 9 needs these partitions to mount HFS(+) formatted volumes; well, actually I am sure of that. The first partition I use for the data of my operating systems is hda9. Preferably, Mac OS Extended (HFS+) should be used as a file system for Mac OS 9 (and Mac OS X) operating systems. I added several other partitions (hda10...hda16) for my daily work purposes. Yet, I created the final Debian partitions on my HDD with the Debian installation tool from the netboot.iso disc, I think, i.e. during the process of the installation of Debian GNU/Linux. In my case I allowed the Debian installer to create a partition hda17 of 1.0MB (could be even less, I think, but I used 1MB; nevermind) as a sort of boot partition on NewWorld PowerPC computers for the yaboot boot loader. It is followed by a /root partition for Debian GNU/Linux hda18 sized about 12.5GB. On my HDD hda19 equals a /home partition of 35GB. Finally, I opted to use about 1.9GB of disc space on my Swap partition hda20, and that's it, for I own 1.5GB of physical memory in this machine. Actually, if you're still trying to fix your problem, I think, however, that you probably do not have to reorganize your set of partitions; at least if you did not destroy any of those small partitions required by Mac OS 9. If your Debian GNU/Linux testing system is up and running and if you did not destroy the partitions Mac OS 9 created during the hard disc initialisation process (including the HFS partition you used to install Mac OS 9 on, of course), please just restart your Macintosh with your Mac OS 9 installation CD. If you then run Drive Setup, respectively Laufwerke konfigurieren (German system version of Mac OS 9), this program will report an IDE disc which was not initialized. Of course, you _must_not_ use this tool to initialize your HDD again, for we actually KNOW that it has already been initialized by Mac OS 9, whilst Debian just added a couple of additional partitions. (If you wanted to reinitialize you would have to start over again to install Debian from the start.) So just use this tool Drive Setup / Laufwerke konfigurieren to update the driver (Treiber aktualisieren) of your hard disk drive. You should find this function in a pull-down menu (and you might have to select this device _once_ with your mouse button before, until its background is shaded with a sort of purple color). If Mac OS 9 can successfully update your HDD's driver the HFS(+) partition(s) of the Mac OS 9 OS you had created before might appear on your screen. Yet, you might also have to reboot your Macintosh one more time from the Mac OS 9 installation CD to (hopefully) see it/them mounted. Updating the HDD driver using Drive Setup does, AFAIK, not have any effect on partitions primarily
Bug#607988: python2.6: the latest update is totally broken and can't byte compile *modules*
well it was 1. reportlab and 2. bzr (gtk). I am not sure on the exact packages - isn't there an easier way to simply check for every python package (available). ii python-central 0.6.16+nmu1 register and build utility for Python packages -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#607988: python2.6: the latest update is totally broken and can't byte compile *modules*
dave b wrote: well it was 1. reportlab and 2. bzr (gtk). Just to confirm, old python-central was not installed when you sent the report, right? What does zgrep 2010-12-2.*python-central /var/log/dpkg.log* say? ii python-central 0.6.16+nmu1 There goes that theory. Alternatively this could be a bug in packages that moved from dh_pycentral to dh_python2 as Sandro suggested. If so, does anyone have a pointer to a page describing what these packages should do to avoid the problem? Sorry for the noise. Jonathan -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#594967: Bug #594967: [poulsbo] grub-pc Hangs After Welcome to GRUB!
On Jan 3, 2011, at 4:06 PM, Colin Watson cjwat...@debian.org wrote: On Mon, Jan 03, 2011 at 12:13:01AM +, Colin Watson wrote: On Sun, Jan 02, 2011 at 10:41:50PM +, Steve McIntyre wrote: 2.iso: goes all the way through to bus ff and returns to a grub prompt This is interesting and suggests a measure of coincidence. What that patch did was skip remaining functions on a device that doesn't implement function 0, taking that as an indication that it doesn't exist. This was based on: http://en.wikipedia.org/wiki/PCI_configuration_space#Bus_enumeration Vladimir, are you OK with this change to trunk? 2011-01-02 Colin Watson cjwat...@ubuntu.com * grub-core/bus/pci.c (grub_pci_iterate): Skip remaining functions on devices that do not implement function 0. I've applied this patch to trunk following an ack from Vladimir on IRC. I'll prepare an updated package for unstable shortly. Nevertheless, I'm not confident that this will fix the problem on all machines, so I would like to sort out the bridge handling as well. This may be more complicated than I thought. Seth Goldberg pointed out that my approach fails to deal with peer host bridges correctly (i.e. cases where there are multiple trees, not just a single one rooted at bus 0). Linux deals with this by asking the PCI BIOS for the last bus number, but at this point things get complicated as you have to do things in different ways for different firmware. The proper way to do this on modern systems is to traverse the system's [DSDT/SSDT] ACPI tables looking for Device objects with the host bridge HID/CID and evaluate the BBN object (which can be a method), if it exists (which it must if there are multiple host bridges). Since grub2 does not have a full ACPI interpreter (pulling in Intel's acpica would work ;), though the license may force it to be a grub-extra), going that route with anything less would never cover all systems' BBNs, so PCI BIOS would be simplest. Things get a bit more complicated when a system has multiple PCI segments (i.e.: using the MCFG table, MMIO addresses that may be 4G, etc.), but that can be tackled later. --S I am inclined to try the first piece alone and see how this works out, and if we can fix the affected systems by just probing function 0 on every device on every bus then let it stand at that, even if it feels less elegant. Inventing new piles of infrastructure to handle a case I'm unsure about in a subsystem I don't know well isn't my idea of a good time. -- Colin Watson [cjwat...@debian.org] ___ Grub-devel mailing list grub-de...@gnu.org http://lists.gnu.org/mailman/listinfo/grub-devel -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#607368: Please decide how kernel ABI should be managed
On Mon, 27 Dec 2010, Ben Hutchings wrote: On Sun, 2010-12-26 at 15:55 -0800, Don Armstrong wrote: Ok. And am I correct in assuming that if the ABI change would break an OOT module, you would normally change the ABI number? In the time I've been involved in the kernel team, I haven't yet seen a case where a bug fix required an ABI change that I knew would break an OOT module. So in this case, if it was clear that the change would have broken an OOT module, the kernel team would normally either postpone the change, or change the ABI number. Anything distributed by Debian should meet those qualifications, but users such as Julien also care about modules from other sources. I normally use Google Code Search to check for OOT modules using symbols that have changed ABI and which I think might be ignorable. Ok. For some reason, I hadn't originally noticed that this was concerning an OOT module which Debian itself didn't actually distribute. [Julien: I'm correct in that, right?] But that's probably fine. How are the symbols that those OOT modules use communicated to the kernel team? They aren't. Would putting the onus on OOT maintainers to maintain such a list be of benefit to the kernel maintainer team? What does the kernel maintainer team feel should be done by the maintainer in this case to ensure continuity of upgrades and rebuilds of the OOT modules? [...] We recommend that OOT module package makes use of DKMS. DKMS includes hook scripts to trigger rebuilding OOT modules automatically for each new kernel ABI version, if the end user or administrator installs the module source and the appropriate linux-headers package. In a more tightly controlled environment where such packages should not be installed on production servers, the administrator must rebuild modules elsewhere and deploy them along with the kernel upgrade. DKMS provides various means for this. Makes sense. What about this case? What should Julien do? Julien: Are you currently shipping a kernel in production which would be affected by this change if we don't change the ABI number? Or does this only affect cases where you are testing squeeze? Could it be worked around by using DKMS or similar with prebuilt binaries and requiring exact kernel version dependencies? Don Armstrong -- I don't care how poor and inefficient a little country is; they like to run their own business. I know men that would make my wife a better husband than I am; but, darn it, I'm not going to give her to 'em. -- The Best of Will Rogers http://www.donarmstrong.com http://rzlab.ucr.edu -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
