Bug#412874: mutagen: diff for NMU version 1.8-1.2
Package: mutagen Version: 1.8-1.1 Severity: normal Tags: patch Hi, Attached is the diff for my mutagen 1.8-1.2 NMU. diff -u mutagen-1.8/mutagen/id3.py mutagen-1.8/mutagen/id3.py --- mutagen-1.8/mutagen/id3.py +++ mutagen-1.8/mutagen/id3.py @@ -291,10 +291,6 @@ except ID3JunkFrameError: pass def __load_framedata(self, tag, flags, framedata): -if self.f_unsynch or flags 0x40: -try: framedata = unsynch.decode(framedata) -except ValueError: pass -flags = ~0x40 return tag.fromData(self, flags, framedata) f_unsynch = property(lambda s: bool(s.__flags 0x80)) @@ -974,7 +970,7 @@ # all we need are the raw bytes. datalen_bytes = data[:4] data = data[4:] -if tflags Frame.FLAG24_UNSYNCH and not id3.f_unsynch: +if tflags Frame.FLAG24_UNSYNCH or id3.f_unsynch: try: data = unsynch.decode(data) except ValueError, err: if id3.PEDANTIC: diff -u mutagen-1.8/tests/test_id3.py mutagen-1.8/tests/test_id3.py --- mutagen-1.8/tests/test_id3.py +++ mutagen-1.8/tests/test_id3.py @@ -140,7 +140,7 @@ id3._ID3__load_framedata(Frames[TPE2], 0, badsync), [u\xffab]) id3._ID3__flags = 0x00 self.assertEquals(id3._ID3__load_framedata( -Frames[TPE2],0x40, badsync), [u\xffab]) +Frames[TPE2], 0x02, badsync), [u\xffab]) tag = id3._ID3__load_framedata(Frames[TPE2], 0, badsync) self.assertEquals(tag, [u\xff, uab]) diff -u mutagen-1.8/debian/changelog mutagen-1.8/debian/changelog --- mutagen-1.8/debian/changelog +++ mutagen-1.8/debian/changelog @@ -1,3 +1,13 @@ +mutagen (1.8-1.2) unstable; urgency=high + + * Non-maintainer upload. + * Apply patch from upstream Subversion repository (r3965), which complements +the ID3 fix from -1.1 and thus really Closes: #403542. + * Fix APEv2 writing, applying patch from upstream Subversion (r3989, r3991), +making sure no invalid tags are written. (Closes: #411433) + + -- Steinar H. Gunderson [EMAIL PROTECTED] Wed, 28 Feb 2007 17:42:43 +0100 + mutagen (1.8-1.1) unstable; urgency=medium * NMU to fix RC bug; urgency medium only in patch2: unchanged: --- mutagen-1.8.orig/tests/test_apev2.py +++ mutagen-1.8/tests/test_apev2.py @@ -10,7 +10,7 @@ import mutagen.apev2 -from mutagen.apev2 import APEv2File, APEv2 +from mutagen.apev2 import APEv2File, APEv2, is_valid_apev2_key DIR = os.path.dirname(__file__) SAMPLE = os.path.join(DIR, data, click.mpc) @@ -18,6 +18,17 @@ BROKEN = os.path.join(DIR, data, brokentag.apev2) LYRICS2 = os.path.join(DIR, data, apev2-lyricsv2.mp3) +class Tis_valid_apev2_key(TestCase): +uses_mmap = False +def test_yes(self): +for key in [foo, Foo,f ~~~]: +self.failUnless(is_valid_apev2_key(key)) + +def test_no(self): +for key in [\x11hi, ffoo\xFF, u\u1234, a, , foo * 100]: +self.failIf(is_valid_apev2_key(key)) +add(Tis_valid_apev2_key) + class TAPEWriter(TestCase): offset = 0 @@ -146,6 +157,10 @@ shutil.copy(OLD, self.filename) self.audio = APEv2(self.filename) +def test_invalid_key(self): +self.failUnlessRaises( +KeyError, self.audio.__setitem__, u\u1234, foo) + def test_guess_text(self): from mutagen.apev2 import APETextValue self.audio[test] = ufoobar only in patch2: unchanged: --- mutagen-1.8.orig/mutagen/apev2.py +++ mutagen-1.8/mutagen/apev2.py @@ -16,9 +16,11 @@ decoders and taggers. APEv2 tags, like Vorbis comments, are freeform key=value pairs. APEv2 -keys can be any UTF-8 string, but restricting keys to ASCII is -strongly recommended. Keys are case-insensitive, but usually stored -title-cased (e.g. 'Artist' rather than 'artist'). +keys can be any ASCII string with characters from 0x20 to 0x7E, +between 2 and 255 characters long. Keys are case-sensitive, but +readers are recommended to be case insensitive, and it is forbidden to +multiple keys which differ only in case. Keys are usually stored +title-cased (e.g. 'Artist' rather than 'artist'). APEv2 values are slightly more structured than Vorbis comments; values are flagged as one of text, binary, or an external reference (usually @@ -33,6 +35,10 @@ import struct from cStringIO import StringIO +def is_valid_apev2_key(key): +return (2 = len(key) = 255 and min(key) = ' ' and max(key) = '~' and +key not in [OggS, TAG, ID3, MP+]) + # There are three different kinds of APE tag values. # 0: Item contains text information coded in UTF-8 # 1: Item contains binary information @@ -41,7 +47,7 @@ TEXT, BINARY, EXTERNAL = range(3) HAS_HEADER = 1L 31 -HAS_FOOTER = 1L 30 +HAS_NO_FOOTER = 1L 30 IS_HEADER = 1L 29 class error(IOError): pass @@ -233,9 +239,15 @@ self[key] = APEValue(value, kind) def
Bug#411063: verilog: diff for NMU version 0.8-4.2
tags 411063 + patch
thanks
Hi,
Attached is the diff for my verilog 0.8-4.2 NMU.
diff -u verilog-0.8/debian/changelog verilog-0.8/debian/changelog
--- verilog-0.8/debian/changelog
+++ verilog-0.8/debian/changelog
@@ -1,3 +1,11 @@
+verilog (0.8-4.2) unstable; urgency=high
+
+ * Non-maintainer upload.
+ * Use sysconf(_SC_PAGESIZE) instead of PAGE_SIZE macro; fixes FTBFS with
+newer kernel headers. (Closes: #411063)
+
+ -- Steinar H. Gunderson [EMAIL PROTECTED] Wed, 28 Feb 2007 17:16:07 +0100
+
verilog (0.8-4.1) unstable; urgency=low
* NMU as part of the GCC 4.1 transition.
only in patch2:
unchanged:
--- verilog-0.8.orig/vvp/main.cc
+++ verilog-0.8/vvp/main.cc
@@ -66,15 +66,17 @@
{
FILE *statm;
unsigned siz, rss, shd;
+ long page_size = sysconf(_SC_PAGESIZE);
+ if (page_size==-1) page_size=0;
statm = fopen(/proc/self/statm, r);
if (!statm) {
perror(/proc/self/statm);
return;
}
if (3=fscanf(statm, %u%u%u, siz, rss, shd)) {
- a-ru_maxrss = PAGE_SIZE * siz;
- a-ru_idrss = PAGE_SIZE * rss;
- a-ru_ixrss = PAGE_SIZE * shd;
+ a-ru_maxrss = page_size * siz;
+ a-ru_idrss = page_size * rss;
+ a-ru_ixrss = page_size * shd;
}
fclose(statm);
}
Bug#411844: sendfile: diff for NMU version 2.1b-3.1
tags 411844 + patch thanks Hi, Attached is the diff for my sendfile 2.1b-3.1 NMU. diff -u sendfile-2.1b/debian/changelog sendfile-2.1b/debian/changelog --- sendfile-2.1b/debian/changelog +++ sendfile-2.1b/debian/changelog @@ -1,3 +1,14 @@ +sendfile (2.1b-3.1) unstable; urgency=high + + * Non-maintainer upload. + * Remove extraneous commands from clean target; we do not need to duplicate +actions in clean that are already present in the .orig.tar.gz. This fixes +an FTBFS, since doc/NEWS now seems to be a pure copy of doc/LIESMICH.neu +and not a symlink, and the .diff.gz can't represent a file becoming a +symlink. (Closes: #411844) + + -- Steinar H. Gunderson [EMAIL PROTECTED] Wed, 28 Feb 2007 17:59:15 +0100 + sendfile (2.1b-3) unstable; urgency=low * Upstream: correct exit code now on error [src/sendmsg.c] diff -u sendfile-2.1b/debian/rules sendfile-2.1b/debian/rules --- sendfile-2.1b/debian/rules +++ sendfile-2.1b/debian/rules @@ -40,11 +40,6 @@ clean: debclean rm -rf stamp-build $(MAKE) clean - rm -rf *~ - ln -sf doc/README - ln -sf doc/LIESMICH - ln -sf doc/COPYING - (cd doc; ln -sf LIESMICH.neu NEWS) debclean: # Cleans debian binary directories to allow binary creation
Bug#405461: jabber: diff for NMU version 1.4.3-3.2
tags 405461 + patch
thanks
Hi,
Attached is the diff for my jabber 1.4.3-3.2 NMU.
diff -u jabber-1.4.3/debian/changelog jabber-1.4.3/debian/changelog
--- jabber-1.4.3/debian/changelog
+++ jabber-1.4.3/debian/changelog
@@ -1,3 +1,12 @@
+jabber (1.4.3-3.2) unstable; urgency=high
+
+ * Non-maintainer upload.
+ * init-ssl.dpatch: Properly initialize the OpenSSL library; fixes issues
+when using OpenSSL 0.9.8, patch originally from Sugree Phatanapherom.
+(Closes: #405461)
+
+ -- Steinar H. Gunderson [EMAIL PROTECTED] Wed, 28 Feb 2007 18:07:55 +0100
+
jabber (1.4.3-3.1) unstable; urgency=medium
[ Sergei Golovan ]
diff -u jabber-1.4.3/debian/patches/00list jabber-1.4.3/debian/patches/00list
--- jabber-1.4.3/debian/patches/00list
+++ jabber-1.4.3/debian/patches/00list
@@ -6,0 +7 @@
+init-openssl
only in patch2:
unchanged:
--- jabber-1.4.3.orig/debian/patches/init-openssl.dpatch
+++ jabber-1.4.3/debian/patches/init-openssl.dpatch
@@ -0,0 +1,37 @@
+#! /bin/sh -e
+## init-openssl.dpatch by Steinar H. Gunderson [EMAIL PROTECTED]
+##
+## All lines beginning with `## DP:' are a description of the patch.
+## DP: Properly initialize OpenSSL, fixing issues with 0.9.8. Patch
+## DP: originally by Sugree Phatanapherom.
+
+[ -f debian/patches/00patch-opts ] . debian/patches/00patch-opts
+patch_opts=${patch_opts:--f --no-backup-if-mismatch}
+
+if [ $# -ne 1 ]; then
+echo 2 `basename $0`: script expects -patch|-unpatch as argument
+exit 1
+fi
+case $1 in
+ -patch) patch $patch_opts -p1 $0;;
+ -unpatch) patch $patch_opts -Rp1 $0;;
+ *)
+ echo 2 `basename $0`: script expects -patch|-unpatch as argument
+ exit 1;;
+esac
+
+exit 0
[EMAIL PROTECTED]@
+diff -urNad jabber-1.4.3~/jabberd/mio_ssl.c jabber-1.4.3/jabberd/mio_ssl.c
+--- jabber-1.4.3~/jabberd/mio_ssl.c 2007-02-28 18:11:08.0 +0100
jabber-1.4.3/jabberd/mio_ssl.c 2007-02-28 18:12:44.008205137 +0100
+@@ -63,7 +63,8 @@
+
+ log_debug(ZONE, Handling configuration using: %s, xmlnode2str(x));
+ /* Generic SSL Inits */
+- OpenSSL_add_all_algorithms();
++SSL_library_init();
++OpenSSL_add_all_algorithms();
+ SSL_load_error_strings();
+
+ /* Setup our hashtable */
Bug#412566: ITP: aes2501-wy -- userspace software for usb aes2501 fingerprint scanner
On Tue, Feb 27, 2007 at 02:50:24AM -0500, Joey Hess wrote: I'd post the beautiful fingerprint scan I just did, but that's perhaps not a great idea. ;-) Don't sorry, I'm quite sure I'll be able to grab a few ones from your glasses at next Debconf. :-) /* Steinar */ -- Homepage: http://www.sesse.net/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#410111: Updated to 8.34.8; still fails due to GPL symbols
On Tue, Feb 27, 2007 at 04:41:50PM +0100, Loïc Minier wrote: The ATI fglrx proprietary driver fails to link with 2.6.20 and it seems this is due to CONFIG_PARAVIRT. People with custom kernels without CONFIG_PARAVIRT could build this module. Is there a workaround we could use in the Debian kernel packages to permit building? Do you see any other way to solve this problem? FWIW, I believe Ubuntu made some hotfixes for this for Feisty. /* Steinar */ -- Homepage: http://www.sesse.net/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#412722: libapache2-mod-speedycgi: too strict Depends
Package: libapache2-mod-speedycgi Version: 2.22-4 Severity: important libapache2-mod-speedycgi has: Depends: speedy-cgi-perl, apache2-mpm-prefork (= 2.0.50-10), apache2.2-common, libc6 (= 2.3.6-6) It should also be able to work just fine with apache2-mpm-itk, so please add that as an alternative. -- System Information: Debian Release: 4.0 APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.19 Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#410111: Updated to 8.34.8; still fails due to GPL symbols
On Tue, Feb 27, 2007 at 05:30:48PM +0100, Loïc Minier wrote: Do you happen to know where this fix is? I grabbed linux-restricted-modules-2.6.20 and found the build fix I applied, but no other fix. I grabbed linux-source-2.6.20, but did not find any patches in debian/. Sorry, no. Ask Tollef Fog Heen (aka Mithrandir), I know he did some patching of drivers for paravirt compatibility. /* Steinar */ -- Homepage: http://www.sesse.net/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#410818: s2ram's stderr output needs to be sent to /dev/null
Package: hal Version: 0.5.8.1-6 Severity: normal s2ram by default outputs a lot of stuff to stderr. This makes HAL (at least gnome-power-manager) think that the command was not successful, even though it returns an exit status of 0. A simple 2/dev/null after s2ram makes gnome-power-manager stop complaining. :-) -- 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.19.1 Locale: LANG=nb_NO.UTF-8, LC_CTYPE=nb_NO.UTF-8 (charmap=UTF-8) Versions of packages hal depends on: ii adduser 3.102Add and remove users and groups ii dbus1.0.2-1 simple interprocess messaging syst ii libc6 2.3.6.ds1-11 GNU C Library: Shared libraries ii libdbus-1-3 1.0.2-1 simple interprocess messaging syst ii libdbus-glib-1-20.71-3 simple interprocess messaging syst ii libexpat1 1.95.8-3.4 XML parsing C library - runtime li ii libglib2.0-02.12.6-2 The GLib library of C routines ii libhal-storage1 0.5.8.1-6Hardware Abstraction Layer - share ii libhal1 0.5.8.1-6Hardware Abstraction Layer - share ii libusb-0.1-42:0.1.12-4 userspace USB programming library ii libvolume-id0 0.103-2 libvolume_id shared library ii lsb-base3.1-23 Linux Standard Base 3.1 init scrip ii pciutils1:2.2.4-1Linux PCI Utilities ii udev0.103-2 /dev/ and hotplug management daemo ii usbutils0.72-7 USB console utilities Versions of packages hal recommends: ii eject 2.1.4-2.1 ejects CDs and operates CD-Changer -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#410669: ITP: pfstools -- set of command line programs for editing HDR images
On Mon, Feb 12, 2007 at 03:59:20PM +0100, Sebastian Harl wrote: * Package name: pfstools FWIW, there are preliminary packages for pfstools and most associated tools at http://storage.sesse.net/pfs-sources.tar.gz There are some bugs in them, but if you haven't packaged them by yourself already, they might be a useful starting point. /* Steinar */ -- Homepage: http://www.sesse.net/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#408669: Reopening #408669: Funny error message: errno 0 (Sucess)
On Sun, Feb 11, 2007 at 05:00:18PM +0100, Arnaud Giersch wrote: I have seen this error message too, on different machines. I however never bothered to write a proper bug report. It seems harmless, and I thought that the NFS developpers would notice it sooner or later. BTW, there is a typo in writting. AFAICS, these messages appeared with some kernel between 2.6.18 and 2.6.19. I don't know which one exactly. With earlier kernels, the file /proc/fs/nfsd/portlist does not exist, and the function nfssvc_setfds() from nfssvc.c exits early and silently. Hm, that's interesting information. I still believe it's a kernel bug, though; could you please reassign to the appropriate kernel package? /* Steinar */ -- Homepage: http://www.sesse.net/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#410208: patch to support Ashtech chipsets
On Thu, Feb 08, 2007 at 04:23:39PM +0100, Steinar H. Gunderson wrote: Attached is a patch to support the Ashtech professional-grade chipsets. It has been tested with a G12. I just forgot to add: This patch will trigger bug #410138, so the patch from that bug should probably be applied together with this one. /* Steinar */ -- Homepage: http://www.sesse.net/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#410160: nfs-kernel-server: NFSv4 inconsistent client behaviour on etch
reassign 410160 linux-image-2.6.18-3-686 thanks On Thu, Feb 08, 2007 at 09:32:09AM +0100, Herbert Valerio Riedel wrote: I'm not sure this is the right place for describing the strange behaviour I'm experiencing with NFSv4, but I'll do it anyway :-) It sounds like you're experiencing a kernel bug; nfs-utils only takes care of the initial setup, and from there it's the kernel all the way. Reassigning. /* Steinar */ -- Homepage: http://www.sesse.net/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#410133: misreports mode when no GSA string is available
Package: gpsd
Version: 2.33-4
Severity: important
Tags: patch
gpsd normally relies on the GSA string to supply the type of fix (none,
2D or 3D). However, when it gets position data from an RMC string,
it also tries to set the type of fix accordingly if there is no GSA
data. (The logic is that if the RMC string says that there is Valid
position data, we must at least have a 2D fix. I believe this could be
done for GGA; I don't know why this is not done.)
This fix is, however, broken -- what happens (at least on my system) is
that session-gpsdata.newdata.mode contains MODE_2D for some reason,
without MODE_SET ever being set in any mask. This means that the
corrected mode data never makes its way from session-gpsdata.newdata
into session-gpsdata.fix, which means that gpsd claims M=0 (no fix)
when it has enough data to understand that there should be a fix.
I believe the included patch corrects this logic; it looks at the data
from session-gpsdata.fix (which should, if I understand the gpsd logic
correctly, contain the currently parsed information from this packet so
far) when deciding whether to override the mode or not.
diff -ur gpsd-2.33/nmea_parse.c gpsd-2.33.patched/nmea_parse.c
--- gpsd-2.33/nmea_parse.c 2006-06-09 14:36:07.0 +0200
+++ gpsd-2.33.patched/nmea_parse.c 2007-02-07 22:41:55.0 +0100
@@ -126,7 +126,7 @@
session-gpsdata.status = STATUS_NO_FIX;
mask |= STATUS_SET;
}
- if (session-gpsdata.newdata.mode = MODE_2D) {
+ if (session-gpsdata.fix.mode = MODE_2D) {
session-gpsdata.newdata.mode = MODE_NO_FIX;
mask |= MODE_SET;
}
@@ -157,7 +157,7 @@
session-gpsdata.status = STATUS_FIX; /* could be DGPS_FIX,
we can't tell */
mask |= STATUS_SET;
}
- if (session-gpsdata.newdata.mode MODE_2D) {
+ if (session-gpsdata.fix.mode MODE_2D) {
session-gpsdata.newdata.mode = MODE_2D;
mask |= MODE_SET;
}
-- 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.19.1
Locale: LANG=nb_NO.UTF-8, LC_CTYPE=nb_NO.UTF-8 (charmap=UTF-8)
Versions of packages gpsd depends on:
ii debconf [debconf-2.0] 1.5.11 Debian configuration management sy
ii libc6 2.3.6.ds1-11 GNU C Library: Shared libraries
ii libdbus-1-3 1.0.2-1 simple interprocess messaging syst
ii libgcc1 1:4.1.1-21 GCC support library
ii libstdc++6 4.1.1-21 The GNU Standard C++ Library v3
ii lsb-base3.1-23 Linux Standard Base 3.1 init scrip
ii netbase 4.29 Basic TCP/IP networking system
Versions of packages gpsd recommends:
ii gpsd-clients 2.33-4 clients for the GPS daemon
ii python2.4.4-2An interactive high-level object-o
-- debconf information:
* gpsd/start_daemon: true
* gpsd/device: /dev/ttyUSB0
* gpsd/daemon_options:
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#410132: ZDA+GLL parsing is broken (ZDA+GGA is fine)
Package: gpsd
Version: 2.33-4
Severity: normal
Tags: patch
Hi,
If you try to use a GPS device which reports both ZDA and GLL (but no
year in RMC), you'll get
can't use GGA/GGL time until after ZDA or RMC has supplied a year.
This is due to a bug in the GLL code (yes, it's GLL, even if the error
message says GGL :-) ), easily fixed with the given trivial patch:
diff -ur gpsd-2.33/nmea_parse.c gpsd-2.33.patched/nmea_parse.c
--- gpsd-2.33/nmea_parse.c 2006-06-09 14:36:07.0 +0200
+++ gpsd-2.33.patched/nmea_parse.c 2007-02-07 22:41:55.0 +0100
@@ -200,7 +200,7 @@
mask = 0;
merge_hhmmss(field[5], session);
- if (session-driver.nmea.date.tm_year != 0)
+ if (session-driver.nmea.date.tm_year == 0)
gpsd_report(1, can't use GGA/GGL time until after ZDA or RMC has
supplied a year.\n);
else {
mask = TIME_SET;
Interestingly, code like this exists for the GGA path as well, but is
correct there.
-- 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.19.1
Locale: LANG=nb_NO.UTF-8, LC_CTYPE=nb_NO.UTF-8 (charmap=UTF-8)
Versions of packages gpsd depends on:
ii debconf [debconf-2.0] 1.5.11 Debian configuration management sy
ii libc6 2.3.6.ds1-11 GNU C Library: Shared libraries
ii libdbus-1-3 1.0.2-1 simple interprocess messaging syst
ii libgcc1 1:4.1.1-21 GCC support library
ii libstdc++6 4.1.1-21 The GNU Standard C++ Library v3
ii lsb-base3.1-23 Linux Standard Base 3.1 init scrip
ii netbase 4.29 Basic TCP/IP networking system
Versions of packages gpsd recommends:
ii gpsd-clients 2.33-4 clients for the GPS daemon
ii python2.4.4-2An interactive high-level object-o
-- debconf information excluded
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#410138: cycle detection is completely broken
Package: gpsd Version: 2.33-4 Severity: important (I'm unsure if this should be RC or not; it's possible to work around depending on your GPS, though.) gpsd has the concept of a cycle, that is, a set of related data from the GPS receiver. It tries to identify these cycles by the timestamps contained in some lines, such as the GLL and ZDA lines; if the timestamp differs from the last one, the start a new cycle flag is set, and the current fix information is thrown away entirely to make room for new data. Unfortunately, the logic looks like this (libgpsd_core.c, starting at line 577): session-gpsdata.sentence_time = NAN; [...] received = session-device_type-parse_packet(session); parse_packet, in turn, contains the logic that compares session-gpsdata.sentence_time with the timing information from the line that was just read. Unsurprisingly, this check will always return different from last time (after all, it was just set to NaN!), so _any_ NMEA command with timing information will start a new cycle. This means that if you have two commands that both have giming information (such as GGA and ZDA), gpsd will think it deals with two different cycles, and fluctuate between the information they give. This gives completely bogus fix and altitude information, among others -- probably a lot of other issues as well. (xgps seems to have a similar issue, but I haven't bothered to debug it.) The following patch sets the sentence time to NaN at initialization time only, which AFAICS would be the _correct_ logic. However, I fear that it might uncover other latent bugs -- after all, if _no_ line contains timing information, a new cycle would _never_ get set. It makes gpsd' output a lot more sane here, though, and ultimately I believe it is correct, so please consider applying it. :-) diff -ur gpsd-2.33/libgps.c gpsd-2.33.patched/libgps.c --- gpsd-2.33/libgps.c 2006-06-09 14:34:09.0 +0200 +++ gpsd-2.33.patched/libgps.c 2007-02-07 23:54:13.0 +0100 @@ -142,6 +142,7 @@ } gpsdata-status = STATUS_NO_FIX; +gpsdata-sentence_time = NAN; gps_clear_fix(gpsdata-fix); return gpsdata; /*@ +branchstate @*/ diff -ur gpsd-2.33/libgpsd_core.c gpsd-2.33.patched/libgpsd_core.c --- gpsd-2.33/libgpsd_core.c2006-06-07 17:04:52.0 +0200 +++ gpsd-2.33.patched/libgpsd_core.c2007-02-07 23:54:29.0 +0100 @@ -574,7 +575,6 @@ (char *)session-outbuffer, (size_t)session-outbuflen, 2); /*@ -nullstate @*/ - session-gpsdata.sentence_time = NAN; session-gpsdata.sentence_length = session-outbuflen; session-gpsdata.d_recv_time = timestamp(); -- 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.19.1 Locale: LANG=nb_NO.UTF-8, LC_CTYPE=nb_NO.UTF-8 (charmap=UTF-8) Versions of packages gpsd depends on: ii debconf [debconf-2.0] 1.5.11 Debian configuration management sy ii libc6 2.3.6.ds1-11 GNU C Library: Shared libraries ii libdbus-1-3 1.0.2-1 simple interprocess messaging syst ii libgcc1 1:4.1.1-21 GCC support library ii libstdc++6 4.1.1-21 The GNU Standard C++ Library v3 ii lsb-base3.1-23 Linux Standard Base 3.1 init scrip ii netbase 4.29 Basic TCP/IP networking system Versions of packages gpsd recommends: ii gpsd-clients 2.33-4 clients for the GPS daemon ii python2.4.4-2An interactive high-level object-o -- debconf information: * gpsd/start_daemon: true * gpsd/device: /dev/ttyUSB0 * gpsd/daemon_options: -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#409839: kismet: newer version available
Package: kismet Version: 2006.04.R1-1.1 Severity: wishlist Kismet-2007-01-R1b is the latest version, according to the web page; Debian's version is in other words now nine months old. It would be nice to have this version in experimental (or unstable, when etch is released). Thanks! :-) -- System Information: Debian Release: 4.0 APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.19 Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8) Versions of packages kismet depends on: ii libbz2-1.0 1.0.3-6 high-quality block-sorting file co ii libc6 2.3.6.ds1-11 GNU C Library: Shared libraries ii libexpat1 1.95.8-3.4 XML parsing C library - runtime li ii libfreetype62.2.1-5 FreeType 2 font engine, shared lib ii libgcc1 1:4.1.1-21 GCC support library ii libgmp3c2 2:4.2.1+dfsg-4 Multiprecision arithmetic library ii libice6 1:1.0.1-2X11 Inter-Client Exchange library ii libjasper-1.701-1 1.701.0-2The JasPer JPEG-2000 runtime libra ii libjpeg62 6b-13The Independent JPEG Group's JPEG ii liblcms11.15-1 Color management library ii libmagick9 7:6.2.4.5.dfsg1-0.13 Image manipulation library ii libncurses5 5.5-5Shared libraries for terminal hand ii libpng12-0 1.2.15~beta5-1 PNG library - runtime ii libsm6 1:1.0.1-3X11 Session Management library ii libstdc++6 4.1.1-21 The GNU Standard C++ Library v3 ii libtiff43.8.2-7 Tag Image File Format (TIFF) libra ii libx11-62:1.0.3-5X11 client-side library ii libxext61:1.0.1-2X11 miscellaneous extension librar ii libxml2 2.6.27.dfsg-1GNOME XML library ii wireless-tools 28-1 Tools for manipulating Linux Wirel ii wireshark-common0.99.4-4 network traffic analyser (common f ii zlib1g 1:1.2.3-13 compression library - runtime kismet recommends no packages. -- debconf-show failed -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#408669: Funny error message: errno 0 (Sucess)
On Sat, Jan 27, 2007 at 08:28:52PM +0100, Steinar H. Gunderson wrote: Use strace -vff or similar. But yes, it looks like it's coming from rpc.nfsd; there are two different lines capable of emitting that message, though. The success thing is a bit of a misnomer; the write was short, but not completely failed. The strace should tell how much was attempted written and how much was actually written... Any progress on this? /* Steinar */ -- Homepage: http://www.sesse.net/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#396653: listen: Fails to start with home over NFS
On Sun, Jan 28, 2007 at 11:35:58AM -0200, [EMAIL PROTECTED] wrote: I've just tested it on a different setup. Instead of getting the same error as I've got before, listen simply takes forever to start. This time I've tried harder to fix it. Installing nfs-common in the client solved the problem. I was able to start listen with home over NFS. Urm, if you don't have nfs-common installed, I'm surprised you can mount NFS shares at all. I'd simply close this with user error; it's a basic misconfiguration which has nothing to do with listen. /* Steinar */ -- Homepage: http://www.sesse.net/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#408669: Funny error message: errno 0 (Sucess)
On Sat, Jan 27, 2007 at 06:22:51PM +0100, Oliver Chief O'Cordes wrote: I got now some funny error messages during the start fo nfsd: nfsd[8663]: nfssvc: writting fds to kernel failed: errno 0 (Success) I think this message will confuse someone, please check carefully the error codes. This looks like an oddity in your kernel; could you please run it under strace? /* Steinar */ -- Homepage: http://www.sesse.net/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#408669: Funny error message: errno 0 (Sucess)
On Sat, Jan 27, 2007 at 08:05:43PM +0100, Oliver-Mark Cordes wrote: Okay, but how? If I start rpc.nfsd with strace I get only some lines because rpc.nfsd is detaching after this. I don't see this error message during the day on another machine with the same setup. But the message is coming from rpc.nfsd or am I wrong? Use strace -vff or similar. But yes, it looks like it's coming from rpc.nfsd; there are two different lines capable of emitting that message, though. The success thing is a bit of a misnomer; the write was short, but not completely failed. The strace should tell how much was attempted written and how much was actually written... /* Steinar */ -- Homepage: http://www.sesse.net/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#341140: Bug#400952: rc order of portmap,nis,autofs
On Thu, Jan 25, 2007 at 01:17:18AM +0100, Jan Christoph Nordholz wrote:
But IMO this solution is an ugly hack and highly counterintuitive - init
scripts are config files after all, and if I wanted to adapt a package's
initscript to my needs, I'd expect to find it at /etc/init.d/${package},
not /etc/init.d/zz${package} or the like.
You don't need to rename the /etc/init.d file, just the symlink in
/etc/rc?.d.
/* Steinar */
--
Homepage: http://www.sesse.net/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#407780: libapreq2: apreq_body doesn't work as expected when body like a=1=c=3 is passed
Hi,
There is a problem with the apreq_body function.
When I submit a form with malformed input (ie fields without name like
{input type=text name= value=} ) all others parameters in the form
are missed by apreq_body and resulting apr_table_t is empty.
Could you please report this upstream as well? (apreq-dev@httpd.apache.org
should do it, AFAIK)
/* Steinar */
--
Homepage: http://www.sesse.net/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#407459: refuses to launch, tap support is broken
Package: kvm Version: 11-1 Severity: grave This command line used to work with kvm 7: fugl:~ sudo kvm -hda /dev/evms/winxp -net nic -net tap Incorrect number of arguments for command Usage: brctl addif bridge device add interface to bridge /etc/kvm/kvm-ifup: could not launch network script Could not initialize device 'tap' It looks like for some reason, the new kvm-ifup script _requires_ that the user uses bridged networking, which has never worked properly for me. -- 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.20-rc4 Locale: LANG=nb_NO.UTF-8, LC_CTYPE=nb_NO.UTF-8 (charmap=UTF-8) Versions of packages kvm depends on: ii libasoun 1.0.13-1ALSA library ii libc62.3.6.ds1-10GNU C Library: Shared libraries ii libsdl1. 1.2.11-7Simple DirectMedia Layer ii libuuid1 1.39+1.40-WIP-2006.11.14+dfsg-1 universally unique id library ii qemu 0.8.2-5 fast processor emulator ii zlib1g 1:1.2.3-13 compression library - runtime kvm recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#407458: package does not purge properly
Package: kvm Version: 11-1 Severity: serious kvm does not purge properly (apologies for the Norwegian in the dpkg line, but I guess it should be quite obvious what happens nevertheless): fugl:~ sudo dpkg --purge kvm (Leser database ... 102778 filer og kataloger er installerte.) Fjerner kvm ... Renser ut oppsettsfiler for kvm ... + '[' purge = purge ']' + '[' -L /etc/udev/rules.d/z60_kvm.rules ']' dpkg: Feil ved behandling av kvm (--purge): underprosessen post-removal script returnerte feilstatus 1 Det oppsto feil ved behandling av: kvm (The set -x is added by myself.) -- 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.20-rc4 Locale: LANG=nb_NO.UTF-8, LC_CTYPE=nb_NO.UTF-8 (charmap=UTF-8) Versions of packages kvm depends on: ii libasoun 1.0.13-1ALSA library ii libc62.3.6.ds1-10GNU C Library: Shared libraries ii libsdl1. 1.2.11-7Simple DirectMedia Layer ii libuuid1 1.39+1.40-WIP-2006.11.14+dfsg-1 universally unique id library ii qemu 0.8.2-5 fast processor emulator ii zlib1g 1:1.2.3-13 compression library - runtime kvm recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#407264: nfs-common: support root-access on krb5-mounts
On Wed, Jan 17, 2007 at 11:16:09AM +0200, Timo Aaltonen wrote: Linked is a patch, described by the author: Thanks! I'll be sure to push this into experimental now (it won't reach etch), but you'll probably have to ask for a sync into Ubuntu yourself. Could you also please push it to upstream? If they don't want it, I don't think it's sustainable for Debian in the long run -- and if they want it, we'd have one less Debian-specific patch. /* Steinar */ -- Homepage: http://www.sesse.net/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#406275: kvm doesn't work on 2.6.20-rc4
On Fri, Jan 12, 2007 at 08:08:36AM +0200, Leonard Norrgård wrote: Btw, work is underway to get kvm-11 packaged, eta: in a few days. Any progress on this? /* Steinar */ -- Homepage: http://www.sesse.net/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#407355: ipw3945-source: new upstream version available, works with 2.6.20
Package: ipw3945-source Version: 1.1.3-2 Severity: normal Hi, 1.1.3 doesn't work with kernel 2.6.20 -- however, 1.2.0 (which was released a bit over a week ago) does. Having it in experimental would probably be useful, even if etch won't ship with it. -- System Information: Debian Release: 4.0 APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.19 Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#406976: aptitude: source-strictness is not strict enough
Package: aptitude Version: 0.4.4-1 Severity: normal Hi, I'm trying to force in newer evince (since I need it for a presentation) _and_ still keep GNOME: fugl:~ LANG=C sudo aptitude install gnome evince/experimental Reading package lists... Done [...] The following packages are BROKEN: gimp libgtk2.0-0 The following packages are unused and will be REMOVED: bsh gcj-4.1-base gij gij-4.1 gimp-data gnuplot gnuplot-nox gnuplot-x11 lapack3 libg2c0 libgcj-bc libgcj-common libgcj7-0 libgd2-noxpm libhsqldb-java libicu36 libjaxp1.2-java libjaxp1.3-java libjline-java libmdbtools libneon26 libpoppler0c2-glib libservlet2.3-java libstlport4.6c2 libufsparse libwpd8c2a libxalan2-java libxerces2-java libxt-java openoffice.org openoffice.org-base openoffice.org-calc openoffice.org-common openoffice.org-core openoffice.org-draw openoffice.org-impress openoffice.org-java-common openoffice.org-math openoffice.org-writer python-uno refblas3 ttf-opensymbol The following NEW packages will be automatically installed: gimp-print gimp-svg gnome-office libwmf0.2-7 The following NEW packages will be installed: gimp-print gimp-svg gnome gnome-office libwmf0.2-7 0 packages upgraded, 6 newly installed, 42 to remove and 0 not upgraded. Need to get 3422kB/3448kB of archives. After unpacking 295MB will be freed. The following packages have unmet dependencies: gimp: Depends: gimp-data (= 2.2.13-1) but it is not installable Conflicts: libgimp2.0 (= 2.3.0) but 2.3.13-1 is installed. libgtk2.0-0: Conflicts: libwmf0.2-7 (= 0.2.8.4-2) but 0.2.8.4-2 is to be installed. Resolving dependencies... open: 59; closed: 34; defer: 0; conflict: 11 .The following actions will resolve these dependencies: Keep the following packages at their current version: libpoppler0c2-glib [0.4.5-5 (testing, unstable, now)] Downgrade the following packages: bug-buddy [2.16.0-1 (experimental, now) - 2.14.0-4 (testing, unstable)] evince [0.6.1-1 (experimental, now) - 0.4.0-3 (testing)] gimp-data [2.3.13-1 (experimental, now) - 2.2.13-1 (testing, unstable)] gtk2-engines [1:2.8.2-2 (experimental, now) - 1:2.8.2-1 (testing, unstable)] gtk2-engines-pixbuf [2.10.7-1 (experimental, now) - 2.8.20-4 (unstable)] libgimp2.0 [2.3.13-1 (experimental, now) - 2.2.6-1sarge1 (stable)] libgnomeui-0 [2.16.1-1 (experimental, now) - 2.14.1-2 (testing, unstable)] libgnomeui-common [2.16.1-1 (experimental, now) - 2.14.1-2 (testing, unstable)] libgtk2.0-0 [2.10.7-1 (experimental, now) - 2.8.20-4 (unstable)] libgtk2.0-common [2.10.7-1 (experimental, now) - 2.8.20-4 (unstable)] librsvg2-2 [2.16.0-3 (experimental, now) - 2.14.4-2 (testing, unstable)] librsvg2-common [2.16.0-3 (experimental, now) - 2.14.4-2 (testing, unstable)] Score is -298 Given that my Request-Strictness is set to 1 (which is now the default, I believe), this score is too high; my guess is that it thinks having evince 0.4.0-3 satisfies my request for evince/experimental. In any case, it appears to be quite impossible to ask it to drop all solutions mentioning evince from testing/unstable, short of removing them from the local Packages files. -- System Information: Debian Release: 4.0 APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.19 Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8) Versions of packages aptitude depends on: ii apt [libapt-pkg-libc6.3-6-3 0.6.46.4 Advanced front-end for dpkg ii libc6 2.3.6.ds1-10 GNU C Library: Shared libraries ii libgcc1 1:4.1.1-21 GCC support library ii libncursesw55.5-5Shared libraries for terminal hand ii libsigc++-2.0-0c2a 2.0.17-2 type-safe Signal Framework for C++ ii libstdc++6 4.1.1-21 The GNU Standard C++ Library v3 Versions of packages aptitude recommends: ii aptitude-doc-en [aptitude-doc 0.4.4-1English manual for aptitude, a ter -- debconf-show failed -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#405796: xserver-xorg-input-wacom: missing Depends: line
Package: xserver-xorg-input-wacom
Version: 0.7.4.1-5
Severity: normal
xserver-xorg-input-wacom has no Depends: line. Building gives:
dh_shlibdeps -a -L wacom-tools -l debian/wacom-tools/usr/lib
dh_gencontrol -a
dpkg-gencontrol: warning: unknown substitution variable ${shlibs:Depends}
Actually wacom_drv.so is linked with -nostdlib and static libgcc, so it
_has_ no dependencies. It should still have a dependency on the server,
though.
-- System Information:
Debian Release: 4.0
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.19
Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8)
-- debconf-show failed
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#404723: src/ne_uri.c:ne_uri_parse():179 (uri_lookup(x) macro) - SIGSERV when parsing a non-ASCII character (128)
On Wed, Dec 27, 2006 at 10:55:16PM +0200, Modestas Vainius wrote: P.S. For some reason, OOo does not crash in my i386 chroot. I don't know why since the bug is clearly arch independent. Possibly since on i386, unsigned and char* have the same size, and thus p[(unsigned)-128] will really be equivalent to p[-128], which is small enough to not overflow. Anyhow, I've NMUed with your patch, sans the noopt part. Thanks for the analysis :-) /* Steinar */ -- Homepage: http://www.sesse.net/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#404723: neon26: diff for NMU version 0.26.2-3.1
tags 404723 + patch
thanks
Hi,
Attached is the diff for my neon26 0.26.2-3.1 NMU.
diff -u neon26-0.26.2/debian/changelog neon26-0.26.2/debian/changelog
--- neon26-0.26.2/debian/changelog
+++ neon26-0.26.2/debian/changelog
@@ -1,3 +1,13 @@
+neon26 (0.26.2-3.1) unstable; urgency=high
+
+ * Non-maintainer upload.
+ * In the uri_lookup() macro, cast to unsigned char instead of unsigned
+(which equals unsigned int), to avoid buffer overruns and SIGSEGV when
+parsing URIs with non-ASCII characters; patch from Modestas Vainius.
+(Closes: #404723)
+
+ -- Steinar H. Gunderson [EMAIL PROTECTED] Fri, 5 Jan 2007 21:40:29 +0100
+
neon26 (0.26.2-3) unstable; urgency=medium
* Fix FTBFS caused by my previous upload, patch didn't apply on 64 bit
only in patch2:
unchanged:
--- neon26-0.26.2.orig/src/ne_uri.c
+++ neon26-0.26.2/src/ne_uri.c
@@ -110,7 +110,7 @@
/* Fx */ OT, OT, OT, OT, OT, OT, OT, OT, OT, OT, OT, OT, OT, OT, OT, OT
};
-#define uri_lookup(ch) (uri_chars[(unsigned)ch])
+#define uri_lookup(ch) (uri_chars[(unsigned char)ch])
char *ne_path_parent(const char *uri)
{
Bug#405558: quilt.make should set PHONY
Package: quilt Version: 0.45-5 Severity: normal As there are no files patch and unpatch, quilt.make should specify: .PHONY: patch unpatch This avoids a stat or two, as well as odd bugs if someone would happen to have a file called patch or unpatch in the local directory. -- System Information: Debian Release: 4.0 APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.19 Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8) Versions of packages quilt depends on: ii bzip2 1.0.3-6high-quality block-sorting file co ii diffstat 1.43-2 produces graph of changes introduc ii gawk 1:3.1.5.dfsg-4 GNU awk, a pattern scanning and pr ii gettext 0.16.1-1 GNU Internationalization utilities ii patch 2.5.9-4Apply a diff file to an original quilt recommends no packages. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#341140: rc order of portmap,nis,autofs
On Fri, Jan 05, 2007 at 02:27:35AM +0100, Jan Christoph Nordholz wrote: I (as the new maintainer of autofs) would like to have the issue settled before Etch is released... what consequences do you fear could arise from moving the script? The present situation forces all users of nisautofs to manually shuffle their init scripts around, and this is a very common setup... Moving autofs to start later (i.e. at 20) is probably unwise (as explained earlier), although this seems to be what most users currently do as a workaround. FWIW, the solution I more-or-less decided upon before giving away autofs was to simply figure out a name that was after 19nis and before 20apache. 195autofs should do, for instance, or 20Autofs. /* Steinar */ -- Homepage: http://www.sesse.net/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#398058: [NFS] nhfsstone license
On Mon, Dec 18, 2006 at 11:52:02PM +0100, Steinar H. Gunderson wrote: No hard feelings, we're just going to fix it for the next release instead, I guess. :-) FWIW, the nfs-utils version currently in experimental (1:1.0.10-6~quilt.1) now ships without nhfsstone, but the source is still in the upstream tarball. Once 1.0.11 is out, I'll use that and this bug will be closed -- once etch is out, whatever is in experimental will get uploaded to unstable (the end changes in the binary package are minimal). /* Steinar */ -- Homepage: http://www.sesse.net/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#404477: dcraw options in delegates.xml are outdated
On Thu, Dec 28, 2006 at 04:01:47PM +0100, Daniel Kobras wrote: Simply removing the -3 flag should be the correct fix for graphicsmagick, but might lose information with imagemagick that uses a 16bit quantum. TBH using 16-bit is really a bit of a pain even with ImageMagick; since dcraw skips the normalization step when outputting 16-bit, raw images become _way_ too dark compared to everything else. Can you please either send me a raw test image for import, or check whether replacing -3 with -4 works as well? http://pr0n.sesse.net/solskogen06/?yres=-1;xres=-1 should have plenty from my camera, at least. /* Steinar */ -- Homepage: http://www.sesse.net/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#402481: Severity of 402481 is important
severity 402481 important thanks After discussing with Andreas, I'm downgrading this one. I'm still NMUing for it, though. /* Steinar */ -- Homepage: http://www.sesse.net/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#404679: apt-proxy: diff for NMU version 1.9.35-0.1
Package: apt-proxy
Version: 1.9.35
Severity: normal
Tags: patch
Hi,
Attached is the diff for my apt-proxy 1.9.35-0.1 NMU.
diff -Nru /tmp/NrgCfDj69G/apt-proxy-1.9.35/apt_proxy/fetchers.py /tmp/pPXWdysC6N/apt-proxy-1.9.35/apt_proxy/fetchers.py
--- /tmp/NrgCfDj69G/apt-proxy-1.9.35/apt_proxy/fetchers.py 2006-08-14 14:44:57.0 +0200
+++ /tmp/pPXWdysC6N/apt-proxy-1.9.35/apt_proxy/fetchers.py 2006-12-27 12:33:47.0 +0100
@@ -21,7 +21,7 @@
network backends
-import re, os, string, time, glob, signal, stat, base64
+import re, os, string, time, glob, signal, stat, base64, urllib
from twisted.web import static, http
from twisted.internet import protocol, reactor, defer, error, abstract
from twisted.python import failure
@@ -244,6 +244,23 @@
self.connection_closed(self.fetcher)
self.deferred.callback((True, ))
+def uri_path_to_path(path, check_part):
+# Split into parts and unescape them.
+parts = [urllib.unquote(part) for part in path.split('/')]
+for part in parts:
+if not check_part(part):
+return None
+# Join up the parts.
+return os.sep.join(parts)
+
+def is_valid_local_path_part(part):
+# Deny use of parent directory or characters that are invalid in a
+# path part.
+return not (part == os.pardir
+or '\0' in part
+or os.sep in part
+or (os.altsep and os.altsep in part))
+
class FileFetcher:
A Fetcher that simply copies files from disk
@@ -268,7 +285,11 @@
self.cache_mtime = mtime
self.request_uri = uri
-self.local_file = self.backendServer.uri[len(file://):] + '/' + uri
+path = uri_path_to_path(uri, is_valid_local_path_part)
+if path is None:
+self.parent.file_not_found()
+return
+self.local_file = self.backendServer.uri[len(file://):] + '/' + path
if not os.path.exists(self.local_file):
self.parent.file_not_found()
return
@@ -508,6 +529,13 @@
self.connection.transport.loseConnection()
self.isConnected = False
+# RFC 959 says pathnames must be ASCII and not include CR or LF.
+ftp_path_part_re = re.compile(r'[^\r\n\x80-\xFF]+$')
+def is_valid_ftp_path_part(part):
+# Also deny use of parent directory, assuming Unix path conventions
+# on the server.
+return part != '..' and ftp_path_part_re.match(part)
+
class FtpFetcher(protocol.Protocol):
This is the secuence here:
@@ -575,8 +603,12 @@
self.parent = fetcher
self.cache_mtime = mtime
self.request_uri = uri
+path = uri_path_to_path(uri, is_valid_ftp_path_part)
+if path is None:
+self.parent.file_not_found()
+return
self.remote_file = (self.parent.backendServer.path + '/'
-+ uri)
++ path)
self.ftpFetchMtime()
def ftpFetchMtime(self):
@@ -645,11 +677,11 @@
def ftpListResult(self, msg):
__pychecker__ = 'unusednames=msg'
-if len(filelist.files)== 0:
+if len(self.filelist.files)== 0:
log.debug(Not found on backend server,'ftp_client')
self.parent.file_not_found()
return
-file = filelist.files[0]
+file = self.filelist.files[0]
self.parent.server_size(file['size'])
fetcher.ftpFetchFile()
@@ -1101,4 +1133,4 @@
def stop(self):
for q in self.queues.values():
-q.stop()
\ No newline at end of file
+q.stop()
diff -Nru /tmp/NrgCfDj69G/apt-proxy-1.9.35/debian/changelog /tmp/pPXWdysC6N/apt-proxy-1.9.35/debian/changelog
--- /tmp/NrgCfDj69G/apt-proxy-1.9.35/debian/changelog 2006-08-15 00:01:41.0 +0200
+++ /tmp/pPXWdysC6N/apt-proxy-1.9.35/debian/changelog 2006-12-27 12:33:23.0 +0100
@@ -1,3 +1,16 @@
+apt-proxy (1.9.35-0.1) unstable; urgency=high
+
+ * Non-maintainer upload.
+ * Use self.filelist instead of filelist in ftpListResult() (in
+fetchers.py), as the latter is a non-existant variable, giving 500
+errors when SIZE failed in an FTP session for some reason.
+(Closes: #402481)
+ * Make the FTP fetcher unescape file names before fetching, which makes
+~ in file names work again with FTP; patch from Ben Hutchings.
+(Closes: #393483, #386344)
+
+ -- Steinar H. Gunderson [EMAIL PROTECTED] Wed, 27 Dec 2006 12:20:45 +0100
+
apt-proxy (1.9.35) unstable; urgency=low
* http_proxy option:
diff -Nru /tmp/NrgCfDj69G/apt-proxy-1.9.35/doc/po/apt-proxy.pot /tmp/pPXWdysC6N/apt-proxy-1.9.35/doc/po/apt-proxy.pot
--- /tmp/NrgCfDj69G/apt-proxy-1.9.35/doc/po/apt-proxy.pot 2006-08-14 14:48:00.0 +0200
+++ /tmp/pPXWdysC6N/apt-proxy-1.9.35/doc/po/apt-proxy.pot 2006-12-27 12:26:20.0 +0100
@@ -6,7 +6,7 @@
msgid
msgstr
Project-Id-Version: PACKAGE VERSION\n
-POT-Creation-Date: 2006-08-14 12:59+0100\n
+POT-Creation-Date: 2006-12-27 12
Bug#402816: utf brocken
On Tue, Dec 12, 2006 at 10:19:54PM +0100, Daniel Baumann wrote: Hrm, just found out that at least dmenu suffers from the same utf breackage as dwm before 2.1-2 does (maybe some others too, needs checking too). dmenu needs also a ~10 line fix. Will prepare package on thursday, no time before. While I understand that this is mainly a placeholder bug to remind yourself of the issue, it would be helpful if you could in fact write _what_ the issue is. After searching a bit, I found out that dwm 2.1-2 was uploaded to testing-proposed-updates (that explains why it's not mentioned in the changelog), but #402671 is not any more forthcoming that this bug report, and the 99-utf.patch in the package also just says fix utf support. Half of it seems to be mucking around with the X pointer anyhow... (It does remove a few setlocale(foo, ) calls, but what that fixes is non-obvious to me.) As you haven't uploaded the package, we're now left with the situation that there's an RC bug in the BTS that nobody but you actually knows what is about, and thus it's a bit hard to get it fixed :-) /* Steinar */ -- Homepage: http://www.sesse.net/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#392357: pcsc-lite: diff for NMU version 1.3.2-3.1
tags 392357 + patch thanks Hi, Attached is the diff for my pcsc-lite 1.3.2-3.1 NMU. diff -u pcsc-lite-1.3.2/debian/pcscd.init pcsc-lite-1.3.2/debian/pcscd.init --- pcsc-lite-1.3.2/debian/pcscd.init +++ pcsc-lite-1.3.2/debian/pcscd.init @@ -25,6 +25,7 @@ DESC=PCSC Lite resource manager PIDFILE=/var/run/$NAME.pid +PUBFILE=/var/run/$NAME.pub SCRIPTNAME=/etc/init.d/$NAME # Gracefully exit if the package has been removed (but not purged). @@ -36,14 +37,16 @@ start) log_daemon_msg Starting $DESC $NAME # if the daemon is already running we REstart it - if [ -f $PIDFILE ]; then - log_progress_msg already running, - $0 restart - else - start-stop-daemon --start --quiet --pidfile $PIDFILE \ - --exec $DAEMON -- --error - log_end_msg $? + if [ -f $PIDFILE ] || [ -f $PUBFILE ]; then + log_progress_msg already running, stopping, + start-stop-daemon --stop --quiet --oknodo --pidfile $PIDFILE \ + --retry 10 --name $NAME + log_progress_msg restarting + rm -f $PIDFILE $PUBFILE fi + start-stop-daemon --start --quiet --pidfile $PIDFILE \ + --exec $DAEMON -- --error + log_end_msg $? ;; stop) @@ -51,6 +54,7 @@ start-stop-daemon --stop --quiet --oknodo --pidfile $PIDFILE \ --retry 10 --name $NAME log_end_msg $? + rm -f $PIDFILE $PUBFILE ;; restart|force-reload) diff -u pcsc-lite-1.3.2/debian/changelog pcsc-lite-1.3.2/debian/changelog --- pcsc-lite-1.3.2/debian/changelog +++ pcsc-lite-1.3.2/debian/changelog @@ -1,3 +1,19 @@ +pcsc-lite (1.3.2-3.1) unstable; urgency=high + + * Non-maintainer upload. + * Fix issues with looping init script. (Closes: #392357) +* restart calls stop ; start, but start calls restart if the pid file + still exists. This is obviously not a good idea if stop doesn't remove + the pid file properly. Make start stop the daemon itself instead of + calling restart, which kills the loop. +* Also, make the stop target rm -f the pid file after calling + start-stop-daemon, just in case, and to avoid extraneous stops from the + start target. +* Finally, also check and rm /var/run/pcscd.pub, as the daemon doesn't + like starting if it's already there. + + -- Steinar H. Gunderson [EMAIL PROTECTED] Tue, 26 Dec 2006 13:45:25 +0100 + pcsc-lite (1.3.2-3) unstable; urgency=high * urgency high to correct a RC bug
Bug#392357: pcsc-lite: diff for NMU version 1.3.2-3.1
tags 392357 + patch thanks Hi, Attached is the diff for my pcsc-lite 1.3.2-3.1 NMU. diff -u pcsc-lite-1.3.2/debian/pcscd.init pcsc-lite-1.3.2/debian/pcscd.init --- pcsc-lite-1.3.2/debian/pcscd.init +++ pcsc-lite-1.3.2/debian/pcscd.init @@ -25,6 +25,7 @@ DESC=PCSC Lite resource manager PIDFILE=/var/run/$NAME.pid +PUBFILE=/var/run/$NAME.pub SCRIPTNAME=/etc/init.d/$NAME # Gracefully exit if the package has been removed (but not purged). @@ -36,14 +37,16 @@ start) log_daemon_msg Starting $DESC $NAME # if the daemon is already running we REstart it - if [ -f $PIDFILE ]; then - log_progress_msg already running, - $0 restart - else - start-stop-daemon --start --quiet --pidfile $PIDFILE \ - --exec $DAEMON -- --error - log_end_msg $? + if [ -f $PIDFILE ] || [ -f $PUBFILE ]; then + log_progress_msg already running, stopping, + start-stop-daemon --stop --quiet --oknodo --pidfile $PIDFILE \ + --retry 10 --name $NAME + log_progress_msg restarting + rm -f $PIDFILE $PUBFILE fi + start-stop-daemon --start --quiet --pidfile $PIDFILE \ + --exec $DAEMON -- --error + log_end_msg $? ;; stop) @@ -51,6 +54,7 @@ start-stop-daemon --stop --quiet --oknodo --pidfile $PIDFILE \ --retry 10 --name $NAME log_end_msg $? + rm -f $PIDFILE $PUBFILE ;; restart|force-reload) diff -u pcsc-lite-1.3.2/debian/changelog pcsc-lite-1.3.2/debian/changelog --- pcsc-lite-1.3.2/debian/changelog +++ pcsc-lite-1.3.2/debian/changelog @@ -1,3 +1,19 @@ +pcsc-lite (1.3.2-3.1) unstable; urgency=high + + * Non-maintainer upload. + * Fix issues with looping init script. (Closes: #392357) +* restart calls stop ; start, but start calls restart if the pid file + still exists. This is obviously not a good idea if stop doesn't remove + the pid file properly. Make start stop the daemon itself instead of + calling restart, which kills the loop. +* Also, make the stop target rm -f the pid file after calling + start-stop-daemon, just in case, and to avoid extraneous stops from the + start target. +* Finally, also check and rm /var/run/pcscd.pub, as the daemon doesn't + like starting if it's already there. + + -- Steinar H. Gunderson [EMAIL PROTECTED] Tue, 26 Dec 2006 13:45:25 +0100 + pcsc-lite (1.3.2-3) unstable; urgency=high * urgency high to correct a RC bug
Bug#392357: fixed in pcsc-lite 1.3.2-3
On Tue, Dec 26, 2006 at 03:55:32PM +0100, Ludovic Rousseau wrote: ...or that it dies across suspend/resume, without rm-ing the pid file. That would be a bug in pcscd. I do not use suspend/resume myself. I would be interested in more inverstigations if you can. Actually, I think I know what is happening. Sometimes my machine does not properly wake from resume, so I have to hard-reboot it; that leaves the pid and pub files. Similarly, any other unclean shutdown will probably do the same. Yes. But that is not what your NMU is doing. It may not be a good idea to remove $PIDFILE and $PUBFILE instead of letting pcscd do it itself. Well, it will do it itself -- assuming it gets shut down properly. Nevertheless I believe having start call restart and restart call start is a really bad idea, especially as the loop spawns new processes all the time and eventually kills your entire machine if you don't stop it. I really cannot find any good reason why it should be that way. /* Steinar */ -- Homepage: http://www.sesse.net/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#404447: nfs-kernel-server: Transferred files get corrupted
reassign 404447 linux-2.6 thanks On Tue, Dec 26, 2006 at 03:32:37PM +0100, Moritz Muehlenhoff wrote: This error message is coming from the kernel NFS code (linux-2.6-2.6.18/fs/nfs/*) Anibal, I suppose you should reassign this to linux-2.6. Doing so -- the nfs-kernel-server package is for the userland support only, as soon as the mount has happened it stays out of the way. /* Steinar */ -- Homepage: http://www.sesse.net/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#392357: fixed in pcsc-lite 1.3.2-3
On Tue, Dec 26, 2006 at 09:05:22PM +0100, Ludovic Rousseau wrote: Files in /var/run/ should be removed by /etc/init.d/bootclean called by /etc/rcS.d/S36mountall-bootclean.sh and /etc/rcS.d/S46mountnfs-bootclean.sh I guess you have a _strange_ configuration if /var/run/ is not cleaned at boot on your system. I don't know if it should be supported. Hm, that's odd. The links are indeed in place... Perhaps my analysis was simply wrong, and it does indeed die across suspend/resume? I'll give it a try as soon as I get the energy. :-) What should happen if /etc/init.d/pcscd start is called when pcscd is already running? Just do nothing? Calling the restart target is _not_ the same as restarting the daemon. But yes, normally it should do nothing. /* Steinar */ -- Homepage: http://www.sesse.net/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#298670: nfs-kernel-server: [exportfs] File structure /etc/exports should allow spaces
On Wed, Mar 09, 2005 at 09:32:58AM +0200, Jari Aalto wrote: The file format of /etc/exports should allow spaces between the HOST and DEF. Like from this: /tmp 192.168.1.0/28(rw,sync,no_root_squash,sync) to this: /tmp 192.168.1.0/28 (rw,sync,no_root_squash,sync) = This would allow writing more structured entried that can be lined up with other lines. After contemplating this, I'm not sure it's such a good idea. The problem is that this actually has a meaning; the latter means the same as: /tmp 192.168.1.0/28(sync) *(rw,sync,no_root_squash,sync) Changing that is going to break people's /etc/exports; you can call (foo) = *(foo) a pathological case, but I'm fairly certain 192.168.1.0/28 = 192.168.1.0/28(default options) is in actual use. This would also create an unclear grammar. What would this be? /tmp 127.0.0.1 (async) (async) Backtracking and guessing in the parser would not be popular among upstream, and I'm not sure if it's a good idea polluting the code with it either. :-) /* Steinar */ -- Homepage: http://www.sesse.net/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#400918: apache2 reload produces error
On Fri, Dec 01, 2006 at 11:43:05AM +0100, Beat Binotto wrote: This error happens on all our machines. php an ssl are enabled as modules. (see below). It happens on 6 different amd64 machines all with kernel 2.6. It also happens on 3 different i386 machines with kernel 2.6. Out of curiosity, does this also happen without PHP? /* Steinar */ -- Homepage: http://www.sesse.net/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#402481: apt-proxy: '500'-error still exists/has returned in version 1.9.35
On Tue, Dec 12, 2006 at 11:51:45PM +0100, Folkert van Heusden wrote: Could you attach your /var/log/apt-proxy.log please? Here it is! Looks like the error is from a SIZE failing (which triggers a LIST trying to figure it out that way instead, which also fails, which gives the error message). Could you please also send your apt-proxy-v2.conf, and a new log with full debugging enabled (debug = all:9 in apt-proxy-v2.conf) while reproducing the problem? /* Steinar */ -- Homepage: http://www.sesse.net/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#402481: apt-proxy: '500'-error still exists/has returned in version 1.9.35
On Wed, Dec 27, 2006 at 02:49:55AM +0100, Steinar H. Gunderson wrote: Looks like the error is from a SIZE failing (which triggers a LIST trying to figure it out that way instead, which also fails, which gives the error message). Could you please also send your apt-proxy-v2.conf, and a new log with full debugging enabled (debug = all:9 in apt-proxy-v2.conf) while reproducing the problem? Nevermind, after about half an hour after the mirror you seem to be using (today's thanks go out to KDE, for providing 300MB of packages I never use myself, and thus a nice target for a huge apt install), I reproduced it with debugging on: 2006/12/27 02:52 CET [FTPClient,client] -- MDTM /debian/pool/main/e/ekg/libgadu3_1.7%7erc2-1_i386.deb 2006/12/27 02:52 CET [FTPClient,client] -- 213 20061121104814 2006/12/27 02:52 CET [FTPClient,client] [Fetcher] File mtime: 1164109694.0 2006/12/27 02:52 CET [FTPClient,client] -- SIZE /debian/pool/main/e/ekg/libgadu3_1.7%7erc2-1_i386.deb 2006/12/27 02:52 CET [FTPClient,client] -- 550 Could not get file size. 2006/12/27 02:52 CET [FTPClient,client] [ftp_client] ftp size failed: [Failure instance: Traceback (failure with no frames): twisted.protocols.ftp.CommandFail ed: ['550 Could not get file size.'] ] 2006/12/27 02:52 CET [FTPClient,client] -- PASV 2006/12/27 02:52 CET [FTPClient,client] -- 227 Entering Passive Mode (213,197,30,53,139,249) 2006/12/27 02:52 CET [FTPClient,client] -- LIST /debian/pool/main/e/ekg/libgadu3_1.7%7erc2-1_i386.deb 2006/12/27 02:52 CET [FTPClient,client] -- 150 Here comes the directory listing. 2006/12/27 02:52 CET [FTPClient,client] -- 226 Directory send OK. 2006/12/27 02:52 CET [FTPClient,client] [ftp_client] ftp list failed: [Failure instance: Traceback: exceptions.NameError: global name 'filelist' is not define d /usr/lib/python2.4/site-packages/twisted/internet/defer.py:307:_runCallbacks /usr/lib/python2.4/site-packages/twisted/internet/defer.py:497:_cbDeferred /usr/lib/python2.4/site-packages/twisted/internet/defer.py:229:callback /usr/lib/python2.4/site-packages/twisted/internet/defer.py:294:_startRunCallbacks --- exception caught here --- /usr/lib/python2.4/site-packages/twisted/internet/defer.py:307:_runCallbacks /usr/lib/python2.4/site-packages/apt_proxy/fetchers.py:648:ftpListResult ] 2006/12/27 02:52 CET [FTPClient,client] [fetcher] (/debian) internal error: Could not list directory 2006/12/27 02:52 CET [FTPClient,client] [Fetcher] download_failed: (500) Could not list directory Basically: 1. The FTP server at the other end (debian.concepts.nl) appears to be broken somehow; it should not send out intermittent 550s on SIZE. I notice that there is a tilde in the filename that gets escaped in the log, though; however, note that it works on the MDTM. Telnetting to the server a few times allowed me to reproduce this: MDTM /debian/pool/main/e/ekg/libgadu3_1.7~rc2-1_i386.deb 213 20060827124706 SIZE /debian/pool/main/e/ekg/libgadu3_1.7~rc2-1_i386.deb 550 Could not get file size. MDTM /debian/pool/main/e/ekg/libgadu3_1.7~rc2-1_i386.deb 213 20060827124706 SIZE /debian/pool/main/e/ekg/libgadu3_1.7~rc2-1_i386.deb 550 Could not get file size. PASV 227 Entering Passive Mode (213,197,30,53,113,146) RETR /debian/pool/main/e/ekg/libgadu3_1.7~rc2-1_i386.deb 550 Failed to open file. Isn't that fishy? Sometimes it gets MDTM but not SIZE (as in this example), sometimes neither, sometimes both work. The tilde doesn't matter either: MDTM /debian/pool/main/e/ekg/libgadu3_1.5+20050411-5_i386.deb 213 20051007134706 SIZE /debian/pool/main/e/ekg/libgadu3_1.5+20050411-5_i386.deb 550 Could not get file size. Even though apt-proxy shouldn't escape tildes (package names with tildes seem to give a consistent 404 when the server works?), I'm fairly certain this is a server bug. 2. fetchers.py:648 should use self.filelist instead of filelist (ditto for line 652). While this is a bug, I'm not sure if it's the actual root cause. So, my conclusion: We have two genuine apt-proxy bugs here (both should be rather easily fixable if the release team would want them fixed in etch), but the main conclusion is that the FTP server in the other end is what is causing these issues. /* Steinar */ -- Homepage: http://www.sesse.net/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#403849: bazaar: diff for NMU version 1.4.2-5.3
On Fri, Dec 22, 2006 at 02:43:46PM +0100, Steinar H. Gunderson wrote: Attached is the diff for my bazaar 1.4.2-5.3 NMU, currently in DELAYED/5-day. Under the new NMU policy, I moved it two days forward in the queue, which means it hit 0-day today. Merry Christmas :-) /* Steinar */ -- Homepage: http://www.sesse.net/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#392415: sun-java5: diff for NMU version 1.5.0-10-1.1
tags 392415 + patch thanks Hi, Attached is the diff for my sun-java5 1.5.0-10-1.1 NMU. diff -u sun-java5-1.5.0-10/debian/changelog sun-java5-1.5.0-10/debian/changelog --- sun-java5-1.5.0-10/debian/changelog +++ sun-java5-1.5.0-10/debian/changelog @@ -1,3 +1,12 @@ +sun-java5 (1.5.0-10-1.1) unstable; urgency=high + + * Non-maintainer upload, reapplying the changes from 1.5.0-08-1.1, which +appears to have been overlooked. + * Move the demo and example files out of /usr/share, to comply with the FHS. +(Closes: #392415) + + -- Steinar H. Gunderson [EMAIL PROTECTED] Mon, 25 Dec 2006 12:49:55 +0100 + sun-java5 (1.5.0-10-1) unstable; urgency=medium * New upstream release. Closes: #393153. diff -u sun-java5-1.5.0-10/debian/rules sun-java5-1.5.0-10/debian/rules --- sun-java5-1.5.0-10/debian/rules +++ sun-java5-1.5.0-10/debian/rules @@ -741,11 +741,11 @@ $(d_jdk)/$(lintian_overrides)/$(p_jdk) ifneq (,$(findstring demo, $(NO_PACKAGES))) - cp -a $(srcdir)/demo $(d_jdk)/usr/share/doc/$(p_jdk)/ - cp -a $(srcdir)/sample $(d_jdk)/usr/share/doc/$(p_jdk)/examples + cp -a $(srcdir)/demo $(d_jdk)/$(basedir)/demo + cp -a $(srcdir)/sample $(d_jdk)/$(basedir)/sample - echo usr/share/doc/$(p_jdk)/demo $(basedir)/demo $(d_jdk).links - echo usr/share/doc/$(p_jdk)/examples $(basedir)/sample $(d_jdk).links + echo $(basedir)/demo usr/share/doc/$(p_jdk)/demo $(d_jdk).links + echo $(basedir)/sample usr/share/doc/$(p_jdk)/examples $(d_jdk).links : # add lintian overrides cat debian/$(p_demo).overrides \ @@ -786,11 +786,11 @@ $(basedir) \ $(lintian_overrides) - cp -a $(srcdir)/demo $(d_demo)/usr/share/doc/$(p_jdk)/ - cp -a $(srcdir)/sample $(d_demo)/usr/share/doc/$(p_jdk)/examples - - echo usr/share/doc/$(p_jdk)/demo $(basedir)/demo $(d_demo).links - echo usr/share/doc/$(p_jdk)/examples $(basedir)/sample $(d_demo).links + cp -a $(srcdir)/demo $(d_demo)/$(basedir)/demo + cp -a $(srcdir)/sample $(d_demo)/$(basedir)/sample + + echo $(basedir)/demo usr/share/doc/$(p_jdk)/demo $(d_demo).links + echo $(basedir)/sample usr/share/doc/$(p_jdk)/examples $(d_demo).links cp -p debian/sun_java_app.xpm \ $(d_demo)/usr/share/icons/$(basename)-app.xpm
Bug#404477: dcraw options in delegates.xml are outdated
Package: imagemagick Version: 7:6.2.4.5.dfsg1-0.13 Severity: important NEF support is currently completely broken, since delegates.xml specifies the -3 flag to dcraw. Just remove the -3 flag and it's working again. -- System Information: Debian Release: 4.0 APT prefers testing APT policy: (800, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: i386 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.19 Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8) Versions of packages imagemagick depends on: ii libbz2-1.0 1.0.3-6 high-quality block-sorting file co ii libc6 2.3.6.ds1-8 GNU C Library: Shared libraries ii libfreetype62.2.1-5 FreeType 2 font engine, shared lib ii libice6 1:1.0.1-2X11 Inter-Client Exchange library ii libjasper-1.701-1 1.701.0-2The JasPer JPEG-2000 runtime libra ii libjpeg62 6b-13The Independent JPEG Group's JPEG ii liblcms11.15-1 Color management library ii libmagick9 7:6.2.4.5.dfsg1-0.13 Image manipulation library ii libpng12-0 1.2.15~beta5-1 PNG library - runtime ii libsm6 1:1.0.1-3X11 Session Management library ii libtiff43.8.2-6 Tag Image File Format (TIFF) libra ii libx11-62:1.0.3-4X11 client-side library ii libxext61:1.0.1-2X11 miscellaneous extension librar ii libxml2 2.6.27.dfsg-1GNOME XML library ii libxt6 1:1.0.2-2X11 toolkit intrinsics library ii zlib1g 1:1.2.3-13 compression library - runtime imagemagick recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#404073: ITA: autofs
On Sat, Dec 23, 2006 at 12:00:18PM +0100, Daniel Baumann wrote: Assuming it is OK with your sponsor (ie. he is willing to take the responsibility if you should for some reason disappear), I have no objectinos. This is ok with me. Fine. :-) Jan: It's yours. Take good care of it. :-) /* Steinar */ -- Homepage: http://www.sesse.net/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#403849: bazaar: diff for NMU version 1.4.2-5.3
tags 403849 + patch
thanks
Hi,
Attached is the diff for my bazaar 1.4.2-5.3 NMU, currently in DELAYED/5-day.
diff -u bazaar-1.4.2/debian/patches/06_neon26.dpatch bazaar-1.4.2/debian/patches/06_neon26.dpatch
--- bazaar-1.4.2/debian/patches/06_neon26.dpatch
+++ bazaar-1.4.2/debian/patches/06_neon26.dpatch
@@ -1,13 +1,98 @@
#! /bin/sh /usr/share/dpatch/dpatch-run
## 06_neon26.dpatch by Clint Adams [EMAIL PROTECTED]
+## Updated by Steinar H. Gunderson [EMAIL PROTECTED]
##
## All lines beginning with `## DP:' are a description of the patch.
## DP: No description.
@DPATCH@
+diff -urNad bazaar-1.4.2~/src/baz/libarch/pfs-dav.c bazaar-1.4.2/src/baz/libarch/pfs-dav.c
+--- bazaar-1.4.2~/src/baz/libarch/pfs-dav.c 2006-12-22 13:57:17.0 +0100
bazaar-1.4.2/src/baz/libarch/pfs-dav.c 2006-12-22 13:58:41.0 +0100
+@@ -97,13 +97,13 @@
+ static int dav_is_dir (struct arch_pfs_dav_session * pfs, char * dir);
+ static int pfs_rmdir (struct arch_pfs_session * p, t_uchar * path, int soft_errors);
+ static int pfs_rm (struct arch_pfs_session * p, t_uchar * path, int soft_errors);
+-static void dav_is_dir_results (void * userdata, const char * uri, const ne_prop_result_set * set);
++static void dav_is_dir_results (void * userdata, const ne_uri * uri, const ne_prop_result_set * set);
+ static int dav_client_cwd (struct arch_pfs_dav_session * pfs, t_uchar * path, int soft_errors);
+ static int dav_client_auth (void * userdata, const char * realm, int attempt,
+ char * username, char * password);
+ static t_uchar * abs_path (t_uchar * cwd, t_uchar * path);
+ static t_uchar * dirfold (t_uchar *dir);
+-static void results (void * userdata, const char * uri, const ne_prop_result_set * set);
++static void results (void * userdata, const ne_uri * uri, const ne_prop_result_set * set);
+
+
+
+@@ -815,19 +815,23 @@
+
+
+ static void
+-dav_is_dir_results (void * userdata, const char * uri, const ne_prop_result_set * set)
++dav_is_dir_results (void * userdata, const ne_uri * uri, const ne_prop_result_set * set)
+ {
+ struct dav_is_dir_ls_data * data = (struct dav_is_dir_ls_data *)userdata;
+ int len;
+
++ char *textual_uri = ne_uri_unparse(uri);
++
+ len = str_length (data-uri);
+- if (!str_cmp_n (uri, len, data-uri, len))
++ if (!str_cmp_n (textual_uri, len, data-uri, len))
+ {
+- if (uri[str_length (uri) - 1] == '/')
++ if (textual_uri[str_length (textual_uri) - 1] == '/')
+ data-is_dir = 1;
+ else
+ data-is_dir = 0;
+ }
++
++ free(textual_uri);
+ }
+
+ static int
+@@ -998,21 +1002,24 @@
+ }
+
+ static void
+-results (void * userdata, const char * uri, const ne_prop_result_set * set)
++results (void * userdata, const ne_uri * uri, const ne_prop_result_set * set)
+ {
+ int n;
+ char * file, * tmp;
+ struct ls_data * data = userdata;
++ char * textual_uri = ne_uri_unparse(uri);
+
+- if (str_cmp (data-uri, uri))
++ if (str_cmp (data-uri, textual_uri))
+ {
+- if (1 == (n = str_length (uri)))
++ if (1 == (n = str_length (textual_uri))) {
++free(textual_uri);
+ return;
++ }
+
+- if (uri[n - 1] == '/')
++ if (textual_uri[n - 1] == '/')
+ n--;
+
+- file = str_chr_rindex_n (uri, n, '/') + 1;
++ file = str_chr_rindex_n (textual_uri, n, '/') + 1;
+
+ n = str_length (file);
+ if (file[n - 1] == '/')
+@@ -1025,6 +1032,7 @@
+ data-files = str_realloc_cat_many (0, data-files, tmp, \r\n, str_end);
+ free (tmp);
+ }
++ free(textual_uri);
+ }
+
+
diff -urNad bazaar-1.4.2~/src/baz/libarch/pfs-sftp.c bazaar-1.4.2/src/baz/libarch/pfs-sftp.c
bazaar-1.4.2~/src/baz/libarch/pfs-sftp.c 2005-06-20 17:59:37.0 -0400
-+++ bazaar-1.4.2/src/baz/libarch/pfs-sftp.c 2006-12-01 12:58:08.516166732 -0500
+--- bazaar-1.4.2~/src/baz/libarch/pfs-sftp.c 2006-12-22 13:57:17.0 +0100
bazaar-1.4.2/src/baz/libarch/pfs-sftp.c 2006-12-22 13:58:17.0 +0100
@@ -1496,7 +1496,7 @@
*/
arch_uri_heuristics (parsed_uri);
@@ -18,8 +103,8 @@
if (parsed_uri.port)
{
diff -urNad bazaar-1.4.2~/src/baz/libarch/pfs.c bazaar-1.4.2/src/baz/libarch/pfs.c
bazaar-1.4.2~/src/baz/libarch/pfs.c 2006-12-01 12:57:57.022973848 -0500
-+++ bazaar-1.4.2/src/baz/libarch/pfs.c 2006-12-01 12:58:08.520167147 -0500
+--- bazaar-1.4.2~/src/baz/libarch/pfs.c 2006-12-22 13:58:04.0 +0100
bazaar-1.4.2/src/baz/libarch/pfs.c 2006-12-22 13:58:17.0 +0100
@@ -514,10 +514,10 @@
char *at_pos = str_chr_index (parsed_uri-host, '@');
if (!at_pos)
@@ -36,8 +121,8 @@
}
diff -urNad bazaar-1.4.2~/src/baz/libarch/tests/unit-sftp.c bazaar-1.4.2/src/baz/libarch/tests/unit-sftp.c
bazaar-1.4.2~/src/baz/libarch/tests/unit-sftp.c 2005-06-20 17:59:37.0 -0400
-+++ bazaar-1.4.2/src/baz/libarch/tests/unit-sftp.c 2006-12-01 13:00:00.271764380 -0500
+--- bazaar-1.4.2~/src/baz/libarch/tests/unit-sftp.c 2006-12-22 13:57
Bug#397886: apache2.2-common: non wanted behaviour during upgrade: charset MUST not be created without user consent
On Fri, Dec 22, 2006 at 06:42:46PM +0100, Daniel Déchelotte wrote: But setting such a DefaultCharset *breaks* *working* pages (and perfectly valid ones) for very little benefit. Sites that use latin encoding for latin characters are *not* broken. Discussions about best behavior aside, just to summarize: The bug here (if any) is that AddDefaultCharset is added even on an upgrade. The problem is, of course, that it's difficult for apache2.2-common to see that it was upgraded from apache2-common. /* Steinar */ -- Homepage: http://www.sesse.net/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#404073: ITA: autofs
On Sat, Dec 23, 2006 at 01:06:16AM +0100, Jan Christoph Nordholz wrote: Would you agree with me adopting autofs? Assuming it is OK with your sponsor (ie. he is willing to take the responsibility if you should for some reason disappear), I have no objectinos. /* Steinar */ -- Homepage: http://www.sesse.net/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#392357: fixed in pcsc-lite 1.3.2-3
reopen 392357 thanks On Fri, Oct 13, 2006 at 03:47:15PM -0700, Ludovic Rousseau wrote: * debian/pcscd.init: really commit a local patch that should already be in 1.3.2-2. Closes: #392357 fails to stop; postinst goes into infinite loop Sorry, this still does not work (I missed the close message, so I assumed it was still open, I guess): fugl:~/nmu sudo /etc/init.d/pcscd restart Stopping PCSC Lite resource manager: pcscd. Starting PCSC Lite resource manager: pcscd already running, Stopping PCSC Lite resource manager: pcscd. Starting PCSC Lite resource manager: pcscd already running, Stopping PCSC Lite resource manager: pcscd. Starting PCSC Lite resource manager: pcscd already running, Stopping PCSC Lite resource manager: pcscd. Even better, if I'm stupid enough to close the xterm at that point, it turns into a forkbomb and kills my machine :-) /* Steinar */ -- Homepage: http://www.sesse.net/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#404073: RFA: autofs
Package: wnpp Severity: normal Hi, I cannot anymore give autofs the proper care it needs -- for one, I do not have any places where I run autofs anymore, and as I'm not taking proper care of the non-RC bugs, I'm trying to find a new maintainer. The package is not especially big or complex; it has no RC-bugs, and upstream is usually quite easy to work with. The diff against upstream is also of a reasonable size; most patches come directly from upstream (most custom patches have long since been fed back). It should be in OK shape for etch; for lenny, we should probably switch to autofs 5 (currently in beta). As a personal request, I'd like the new maintainer to not have a lot of packages already, as the package is going to require a bit of constant care. -- System Information: Debian Release: 4.0 APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.19 Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#392357: fixed in pcsc-lite 1.3.2-3
On Thu, Dec 21, 2006 at 10:12:29PM +0100, Ludovic Rousseau wrote: It looks like pcscd does not want to die. ...or that it dies across suspend/resume, without rm-ing the pid file. It is my understanding that if the daemon is not there when stop runs, it should simply nuke the pid file. We will try to debug. Do: fugl:~ cat /var/run/pcscd.pid 4720 fugl:~ ps -eo pid args -ww|grep $(cat /var/run/pcscd.pid) 5096 grep 4720 fugl:~ sudo /etc/init.d/pcscd stop Stopping PCSC Lite resource manager: pcscd. fugl:~ cat /var/run/pcscd.pid 4720 fugl:~ ps -eo pid args -ww|grep $(cat /var/run/pcscd.pid) 5112 grep 4720 fugl:~ sleep 10 fugl:~ cat /var/run/pcscd.pid 4720 fugl:~ ps -eo pid args -ww|grep $(cat /var/run/pcscd.pid) 5133 grep 4720 Also send me the output of: fugl:~ find /usr/lib/pcsc/ /usr/lib/pcsc/ /usr/lib/pcsc/services /usr/lib/pcsc/drivers /usr/lib/pcsc/drivers/ifd-ccid.bundle /usr/lib/pcsc/drivers/ifd-ccid.bundle/Contents /usr/lib/pcsc/drivers/ifd-ccid.bundle/Contents/Info.plist /usr/lib/pcsc/drivers/ifd-ccid.bundle/Contents/Linux /usr/lib/pcsc/drivers/ifd-ccid.bundle/Contents/Linux/libccid.so.1.1.0 /usr/lib/pcsc/drivers/serial /usr/lib/pcsc/drivers/serial/libccidtwin.so.1.1.0 /* Steinar */ -- Homepage: http://www.sesse.net/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#403818: xserver-xorg: no video or keyboard after upgrading to sarge (deps too loose)
On Tue, Dec 19, 2006 at 09:22:34PM -0500, David Nusinow wrote: I can't imagine what that would be... I'd love to know. Was this on x86? It was on x86, yes. Perhaps for video 'xserver-xorg-video-all | xserver-xorg-video-vesa' in the recommends. That could work as well; OTOH a well-functioning aptitude (ie. one not faced with conflicts) would already pull in xserver-xorg-video-all, so I'm not sure if there's a particularly good reason to put -all in the recommends. I still think the best basic idea is to give aptitude a simple choice to work with, with no alternatives. /* Steinar */ -- Homepage: http://www.sesse.net/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#403945: apache2-mpm-itk: uninstallable on arm
On Wed, Dec 20, 2006 at 10:33:08PM +0100, Aurelien Jarno wrote: The problem has already been sorted out by the release team, but failed on arm due to a recurrent problem with the build daemon. In that case, it is not a bug in apache2-mpm-itk; closing after conferring with the RMs. Where should I report this problem then? This package is *not* in a releasable state on ARM, this has to be *tracked* somewhere. I guess the RMs already know about it...? It's not really the first time a package has been late in building for some reason, and the BTS isn't really needed to track such skews. Cc-ing -release; I'm sure they can help you if you have further issues. /* Steinar */ -- Homepage: http://www.sesse.net/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#403800: update-manager: should suggest update-notifier
Package: update-manager Version: 0.42.2ubuntu22-7 Severity: normal I installed update-manager in the hopes of having automated updates, but couldn't get it to work. Even after searching the documentation, there wasn't really any good hints; at last I had to ask on IRC, and was told that I needed update-notifier. Could update-manager at least not have a Suggests: on update-notifier? -- System Information: Debian Release: 4.0 APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.19 Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#403818: xserver-xorg: no video or keyboard after upgrading to sarge (deps too loose)
Package: xserver-xorg Version: 1:7.1.0-8 Severity: serious Justification: 23:28 vorlon Sesse: I'd call it RC, no? After dist-upgrading (using etch's aptitude) from sarge to etch, one machine here was completely without keyboard or mouse support, and X refused to work. A bit of hunting revealed that aptitude had pulled in xserver-xorg-input-magictouch and xserver-xorg-video-siliconmotion to fulfill xserver-xorg's dependencies on xserver-xorg-video-all | xserver-xorg-video and xserver-xorg-input-all | xserver-xorg-input, respectively. This is clearly not satisfiable. AFAICS there are two OK ways of solving this: 1. Make the depends into xserver-xorg-video, xserver-xorg-input, and add Recommends for the -all packages instead. 2. Add xserver-xorg-input-kbd and xserver-xorg-input-mouse explicitly to the list of depends (or possibly recommends?), which should make aptitude Do The Right Thing (hopefully). This won't solve the issue for video, though. One could use a combination of 1 and 2. Note that the request to aptitude install xorg, which was given by debconf, was a no-op, since all the dependencies were already fulfilled. Also, xorg.conf was blank after the upgrade, but I guess that's for another bug, which will be far harder to track down... :-) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#403849: segfault on baz ancestry-graph
Package: bazaar Version: 1.4.2-5.2+b1 Severity: grave During import to bzr, I got a segfault. The following command reproduces it: pannekake:~ baz ancestry-graph [EMAIL PROTECTED]/pitch--mainline--0.1--patch-14 zsh: segmentation fault baz ancestry-graph [EMAIL PROTECTED]/pitch--mainline--0.1--patch-1 The archive in question is available from http://arch.sesse.net/[EMAIL PROTECTED] . Downgrading bazaar to the version in sarge made the import work flawlessly, so this must be a newer issue somehow. -- System Information: Debian Release: 4.0 APT prefers testing APT policy: (800, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: i386 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.19 Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8) Versions of packages bazaar depends on: ii diff 2.8.1-11 File comparison utilities ii gawk 1:3.1.5.dfsg-4 GNU awk, a pattern scanning and pr ii libc6 2.3.6.ds1-8GNU C Library: Shared libraries ii libgpgme111.1.2-2GPGME - GnuPG Made Easy ii libneon26-gnutls 0.26.2-3 An HTTP and WebDAV client library ii patch 2.5.9-4Apply a diff file to an original bazaar recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#403849: segfault on baz ancestry-graph
found 403849 1.4.2-5.2 thanks On Wed, Dec 20, 2006 at 02:41:43AM +0100, Steinar H. Gunderson wrote: During import to bzr, I got a segfault. The following command reproduces it: FWIW, binary searching using snapshot.debian.net shows that this segfault was introduced in version 1.4.2-5.2 (-5.1 is fine). /* Steinar */ -- Homepage: http://www.sesse.net/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#403818: xserver-xorg: no video or keyboard after upgrading to sarge (deps too loose)
On Tue, Dec 19, 2006 at 08:40:26PM -0500, David Nusinow wrote: Ouch. This is a bug in aptitude, aiui. It should be choosing the first option if nothing is currently installed, and allowing the second to substitute. Probably something in -all caused a conflict, and the conflict resolution manager preferred a random choice providing -input instead. Either way, it's probably too late to fix this in aptitude for etch, so a workaround is necessary... Most upgrades will probably happen with the aptitude from sarge, BTW. 1. Make the depends into xserver-xorg-video, xserver-xorg-input, and add Recommends for the -all packages instead. If I build a package set with this, will you be able to test it to make sure it works? Unfortunately, no; the machine was just my mother's workstation. However, I've picked out the dpkg status backup and reconstructed the aptitude lines; talk to Julien Cristau, he has the data in question. Also, xorg.conf was blank after the upgrade, but I guess that's for another bug, which will be far harder to track down... :-) Gyah... did xserver-xorg error out during postinst? I'll have to look for a codepath that can cause that beyond errors. No, it didn't error out. It just showed the warning debconf template, and then continued as nothing was wrong. Note that due to some conflicts etc., the upgrading line was aptitude install gnome (the full dist-upgrade was not done until later); it _might_ be that a full dist-upgrade is luckier somehow, but I'm not going to bet on it. Just giving aptitude the explicit hint that the user would probably like to have -input-(kbd,mouse) and -video-vesa sounds like the best hint to me, especially as they're not likely to conflict with anything (so the conflict resolver accepts that more or less right away). /* Steinar */ -- Homepage: http://www.sesse.net/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#398058: [NFS] nhfsstone license
On Tue, Dec 19, 2006 at 09:49:36AM +1100, Neil Brown wrote: It seems like nobody does, judging from the response. Is there any chance of a relatively quick 1.0.11 without nhfsstone? We have frozen in Debian at the moment, but fixing such a license bug would probably be allowed past the freeze. I've removed nhfstone from the git repository, but I'm not going to roll up an 1.0.11 release just now - sorry. Maybe in January. No hard feelings, we're just going to fix it for the next release instead, I guess. :-) /* Steinar */ -- Homepage: http://www.sesse.net/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#397412: wmaker: Wmaker crash on creating desktop
On Fri, Dec 15, 2006 at 12:14:02PM +0100, Raphael Hertzog wrote: I could reproduce the bug. It's locale-dependent. Using ru_RU.KOI8-R or ru_RU.UTF-8 allowed me to reproduce the bug. Oh, but that makes it rather obvious. Line 1418, src/workspace.c: strcpy(title, scr-workspaces[ws]-name); title is defined as char title[MAX_WORKSPACENAME_WIDTH+1]; with (wmaker/src/wconfig.h) #define MAX_WORKSPACENAME_WIDTH 32 The ru_RU string for a new workspace is 'Рабочее пространство 1', which is 41 bytes long in UTF-8. Classic stack smash. Just increase MAX_WORKSPACENAME_WIDTH, or stop using strcpy; both should fix the problem. /* Steinar */ -- Homepage: http://www.sesse.net/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#397412: wmaker: diff for NMU version 0.92.0-6.1
tags 397412 + patch thanks Hi, Attached is the diff for my wmaker 0.92.0-6.1 NMU, currently in DELAYED/7-day. diff -u wmaker-0.92.0/debian/changelog wmaker-0.92.0/debian/changelog --- wmaker-0.92.0/debian/changelog +++ wmaker-0.92.0/debian/changelog @@ -1,3 +1,11 @@ +wmaker (0.92.0-6.1) unstable; urgency=high + + * Non-maintainer upload. + * 70_fix_overrun.diff: New patch, fix buffer overrun when creating new +workspaces in Romanian locales. (Closes: #397412) + + -- Steinar H. Gunderson [EMAIL PROTECTED] Fri, 15 Dec 2006 18:22:42 +0100 + wmaker (0.92.0-6) unstable; urgency=medium * New Maintainer. only in patch2: unchanged: --- wmaker-0.92.0.orig/debian/patches/70_fix_overrun.diff +++ wmaker-0.92.0/debian/patches/70_fix_overrun.diff @@ -0,0 +1,11 @@ +--- wmaker/src/wconfig.h.in 2006-12-15 18:20:27.0 +0100 wmaker/src/wconfig.h.in 2006-12-15 18:21:00.0 +0100 +@@ -470,7 +470,7 @@ + + #define HRESIZE_THRESHOLD 3 + +-#define MAX_WORKSPACENAME_WIDTH 32 ++#define MAX_WORKSPACENAME_WIDTH 64 + #define MAX_WINDOWLIST_WIDTH 160 /* max width of window title in + * window list */ +
Bug#403232: nfs-kernel-server: map_daemon option silently ignored in /etc/export
On Fri, Dec 15, 2006 at 04:01:23PM +0100, Thiemo Nagel wrote:
The nfs-kernel-server seems to silently ignore the map_daemon option. I
don't know whether uid/gid mapping via ugidd is a feature of
nfs-kernel-server or not, i.e. whether map_daemon should work at all,
however silently ignoring the option has (maybe mild, feel free to
adjust the proposed severity) security implications:
I'm not sure what the option is even supposed to do. The only reference I can
find to it is in a commented-out section of the exports man page; I believe
it's parsed for legacy reasons only.
Anyhow, NFSv4 does away with the uid stuff completely, so I'm not sure how
relevant this is. I could of course make a patch that just removes the
map_daemon handling, but I'm unsure whether it has any uses at all.
Also note
if (exp-m_export.e_maptype != CLE_MAP_IDENT) {
xlog(L_ERROR, %s: unsupported mapping; kernel supports only
'identity' (default),
exp-m_export.m_path);
errno = EINVAL;
return 0;
}
so it looks like it _should_ just give an error. Any ideas?
/* Steinar */
--
Homepage: http://www.sesse.net/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#403232: nfs-kernel-server: map_daemon option silently ignored in /etc/export
On Fri, Dec 15, 2006 at 08:38:47PM +0100, Thiemo Nagel wrote: The option is valid for nfs-user-server (and works just fine in my setup), 'man exports' (with nfs-user-server package installed) gives a detailed description about it (better than I can do). nfs-user-server is horribly, horribly outdated, and should not really be used, much less as a reference. :-) so it looks like it _should_ just give an error. Any ideas? That is interesting. Where is that message supposed to show up? I can find it neither in dmesg nor in kern.log nor in syslog. No idea, sorry. /* Steinar */ -- Homepage: http://www.sesse.net/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#403232: nfs-kernel-server: map_daemon option silently ignored in /etc/export
On Fri, Dec 15, 2006 at 10:40:43PM +0100, Thiemo Nagel wrote: nfs-user-server is horribly, horribly outdated, and should not really be used, much less as a reference. :-) Well, if it shouldn't be used, it shouldn't be packaged... ;-) You are right, it should be removed, but it won't happen for etch. Anyways, if nfs-user-server is really so horrible, nfs-kernel-server should not just quietly ignore its options, but throw an error instead... Yes, I guess so. I could upload a fix to unstable, but it doesn't seem like a good idea right now, with the freeze and all. Anyhow, I'm tempted to downgrade; not giving an error on an old, undocumented, deprecated option doesn't sound like important to me. /* Steinar */ -- Homepage: http://www.sesse.net/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#401900: wmaker: crashes when using putty in wine
tags 401900 + patch
severity 401900 important
thanks
23:36 Sesse vorlon: I have a DELAYED/7-day going for the other rc bug.
what do you say about a) I add the patch to the bts, b) we
downgrade to important, c) we'll see if the maintainer takes
it, and in that case uploads it at the same time?
23:36 vorlon sounds fair to me
So, here's a proposed patch to fix the issue; I'm not sure if it's correct,
but the same technique seems to be used in other places, and it seems to
solve the problem OK. Just drop in debian/patches.
/* Steinar */
--
Homepage: http://www.sesse.net/
--- wmaker-0.92.0/src/wmspec.c 2005-05-15 18:41:09.0 +0200
+++ wmaker-0.92.0/src/wmspec.c 2006-12-15 23:32:09.0 +0100
@@ -1268,11 +1273,13 @@
XFree(data);
}
-ChangeStackingLevel(wwin-frame-core, layer);
-wwin-frame-flags.need_texture_change = 1;
-wWindowConfigureBorders(wwin);
-wFrameWindowPaint(wwin-frame);
-wNETWMUpdateActions(wwin, False);
+if (wwin-frame) {
+ChangeStackingLevel(wwin-frame-core, layer);
+wwin-frame-flags.need_texture_change = 1;
+wWindowConfigureBorders(wwin);
+wFrameWindowPaint(wwin-frame);
+wNETWMUpdateActions(wwin, False);
+}
}
Bug#400215: nut-usbups.rules being overriden by a symlink
On Wed, Dec 13, 2006 at 02:56:33PM +0100, Arnaud Quette wrote: @Steinar: while we're at it, would you be interested in co maintaining these packages? I would be really glad if you accept ;-) I do not even have an UPS, so sorry. :-) /* Steinar */ -- Homepage: http://www.sesse.net/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#398058: [NFS] nhfsstone license
On Mon, Nov 20, 2006 at 05:20:34PM -0500, J. Bruce Fields wrote: No modification required if we remove it from upstream too. Do people use it? It seems like nobody does, judging from the response. Is there any chance of a relatively quick 1.0.11 without nhfsstone? We have frozen in Debian at the moment, but fixing such a license bug would probably be allowed past the freeze. /* Steinar */ -- Homepage: http://www.sesse.net/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#402402: lightspeed: crushes on start
On Sun, Dec 10, 2006 at 07:26:55PM -0800, Steve Langasek wrote: It does not follow that just because an assertion failure happens in fontconfig that the bug is in fontconfig. This problem hasn't been reported against any other programs besides lightspeed, It has been reported for several other programs -- abiword and ImageMagick, for instance. It's easily fixed, though; just remove the FcFini. At least that's what the abiword people did... /* Steinar */ -- Homepage: http://www.sesse.net/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#402402: lightspeed: crushes on start
reassign 402402 lightspeed thanks On Mon, Dec 11, 2006 at 02:47:35PM +0100, Ola Lundqvist wrote: Removed from where? In lightspeed case the FcFinit is not called directly but rather via gtk libraries. Wrong. Check src/ogl-ftgl.cc, line 70. I'm reassigning back to fontconfig. If the function that is calling fontconfig should be changed, please reassign to that library. lightspeed is the one calling fontconfig... /* Steinar */ -- Homepage: http://www.sesse.net/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#402654: fails to build against kernel 2.6.19
Package: kvm-source
Version: 5-2
Severity: normal
Hi,
Running module-assistant --text auto-install kvm on 2.6.19 gives:
make[3]: Entering directory `/usr/src/linux-2.6.19'
LD /usr/src/modules/kvm/built-in.o
CC [M] /usr/src/modules/kvm/svm.o
In file included from /usr/src/modules/kvm/svm.c:22:
/usr/src/modules/kvm/kvm_svm.h:12: error: ‘MSR_STAR’ undeclared here (not in
a function)
/usr/src/modules/kvm/kvm_svm.h:12: error: ‘MSR_LSTAR’ undeclared here (not in
a function)
/usr/src/modules/kvm/kvm_svm.h:12: error: ‘MSR_CSTAR’ undeclared here (not in
a function)
/usr/src/modules/kvm/kvm_svm.h:12: error: ‘MSR_SYSCALL_MASK’ undeclared here
(not in a function)
/usr/src/modules/kvm/kvm_svm.h:12: error: ‘MSR_KERNEL_GS_BASE’ undeclared
here (not in a function)
/usr/src/modules/kvm/kvm_svm.h:16: error: ‘MSR_FS_BASE’ undeclared here (not
in a function)
/usr/src/modules/kvm/kvm_svm.h:16: error: ‘MSR_GS_BASE’ undeclared here (not
in a function)
/usr/src/modules/kvm/svm.c:118:42: error: macro read_cr2 passed 1
arguments, but takes just 0
/usr/src/modules/kvm/svm.c:119: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
‘__attribute__’ before ‘{’ token
/usr/src/modules/kvm/svm.c:126: error: expected identifier or ‘(’ before ‘asm’
/usr/src/modules/kvm/svm.c: In function ‘svm_is_long_mode’:
/usr/src/modules/kvm/svm.c:159: error: ‘EFER_LMA’ undeclared (first use in
this function)
/usr/src/modules/kvm/svm.c:159: error: (Each undeclared identifier is
reported only once
/usr/src/modules/kvm/svm.c:159: error: for each function it appears in.)
and several other errors.
-- 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.19
Locale: LANG=nb_NO.UTF-8, LC_CTYPE=nb_NO.UTF-8 (charmap=UTF-8)
Versions of packages kvm-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 make 3.81-3 The GNU version of the make util
ii module-assistant 0.10.8 tool to make module package creati
kvm-source recommends no packages.
-- no debconf information
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#401964: nfs-common - mount expects that rpc.idmapd writes a pidfile but it does not
reassign 401964 mounts severity 401964 minor reopen 388006 merge 401964 388006 thanks On Thu, Dec 07, 2006 at 01:32:16AM +0100, Bastian Blank wrote: mount for nfs4 expects that rpc.idmapd writes a pidfile to show its availability. The daemon does not write one, so I can only get all-mapped mounts: | Warning: rpc.idmapd appears not to be running. | All uids will be mapped to the nobody uid. This looks like a duplicate of #376931, #383308, #385879 and #388006. It seems that only the check for rpc.gssd was removed; probably the one for rpc.idmapd should, too. /* Steinar */ -- Homepage: http://www.sesse.net/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#401755: gs-gpl: ps2write is missing opdfread.ps
Package: gs-gpl Version: 8.54.dfsg.1-5 Severity: important ps2ps gives: trofast:/usr/src/prosjekt/doc# ps2ps2 gpuwave.ps gpuwave2.ps Configuration error : library file opdfread.ps not found ! Unrecoverable error: undefinedfilename in opdfread.ps Operand stack: --nostringval-- gs_mgl_e.ps gs_mro_e.ps gs_agl.psopdfread.ps Copying lib/opdfread.ps from the source tree into /usr/share/gs-gpl/8.54/lib/ resolves the problem. -- System Information: Debian Release: 4.0 APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.19 Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8) Versions of packages gs-gpl depends on: ii gs-common0.3.11 Common files for different Ghostsc ii libc62.3.6.ds1-8 GNU C Library: Shared libraries ii libice6 1:1.0.1-2 X11 Inter-Client Exchange library ii libpaper11.1.21 Library for handling paper charact ii libsm6 1:1.0.1-3 X11 Session Management library ii libx11-6 2:1.0.3-4 X11 client-side library ii libxext6 1:1.0.1-2 X11 miscellaneous extension librar ii libxt6 1:1.0.2-2 X11 toolkit intrinsics library Versions of packages gs-gpl recommends: ii gsfonts 1:8.11+urwcyr1.0.7~pre41-1 Fonts for the Ghostscript interpre ii psfontmgr 0.11.10PostScript font manager -- part of -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#397412: wmaker: Wmaker crash on creating desktop
On Tue, Dec 05, 2006 at 12:47:50AM +0500, jamhed wrote: when wmaker source package is compiled with default gcc (gcc version 4.1.2 20061028 (prerelease) (Debian 4.1.1-19)), it crashes. when it compiled with gcc-3.4 (gcc version 3.4.6 (Debian 3.4.6-4)), with export CC=gcc-3.4 before making package, it works just fine. This is most likely by accident -- as we saw, building it without optimization does the same thing. wmaker compiled with gcc-4.1 just is not usable. Well, it worked for me, and seemingly for most other people. I'm not sure what makes your configuration special, though :-) /* Steinar */ -- Homepage: http://www.sesse.net/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#397412: wmaker: Wmaker crash on creating desktop
On Mon, Dec 04, 2006 at 11:48:31PM +0500, jamhed wrote: Which GCC version did you used ? 4.1.2, AFAICS. /* Steinar */ -- Homepage: http://www.sesse.net/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#400707: copy to NFS server locks up
On Tue, Nov 28, 2006 at 12:34:07AM -0500, Gary Dale wrote: I'm running Etch on an AMD64 system which connects via NFS to a server running Sarge (i686). I can copy files from the server and the copy chugs along at about 10 - 11 MB/Sec before completing. However, when I copy files to the server, the speed goes up and down, sometimes as high as 45MB/Sec before stalling. Usually it restarts and again goes to a high value before stalling again. On other copies, it might simply go up and down between 15 5 MB/Sec with few stalls. This is not a problem in nfs-utils; it's a problem in the kernel on one of the sides. nfs-utils only sets up the connection, after that it's all the kernel. Since you did not use reportbug, it's not possible for me to know what kernel package to reassign this to, so you'll have to do it yourself. :-) /* Steinar */ -- Homepage: http://www.sesse.net/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#400656: autofs init script
retitle 400656 please add LSB dependency headers to the init script severity 400656 withlist thanks On Mon, Nov 27, 2006 at 09:00:13PM +0100, Antonio Larrosa wrote: It seems a block like this is missing in /etc/init.d/autofs : Uhm. This kind of dependency information is _not_ mandatory in Debian by any standards. Please do not pretend it is. This makes sure that autofs is run after the nis service (by having nis in Required-Start). If this block is missing (like now), it's possible that nis and autofs are run at the same time, which leaves autofs in a bad state since it cannot retrieve the automount map throught nis (this happened to me, and I fixed it adding that block). If you have such problems, please do not use parallelized bootup; it is not defined in Debian policy as of today. /* Steinar */ -- Homepage: http://www.sesse.net/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#399523: [Pkg-uml-pkgs] Processed: really reassign
On Thu, Nov 23, 2006 at 02:28:12PM +0100, Nicolas Boullis wrote: Some more information: if I set my filesystem to noauto, everything goes fine (rpc.statd is correctly registered) except that I have to mount it manually after booting... In that case, it sounds more like a bug in initscripts to me? /* Steinar */ - always trigger happy at the reassigning :-) -- Homepage: http://www.sesse.net/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#399454: [autodir] [EMAIL PROTECTED]: Bug#399454: autodir: fails with alert: unexpected autofs packet type 3]
On Thu, Nov 23, 2006 at 05:49:08AM -0800, ramana wrote: As for the compatibility check, Autodir supports only protocol 4 and in the future 5. So only check for protocol 4 is needed at this moment. FWIW, after etch I'll put autofs 5 into Debian; etch will, however, stay with autofs 4. /* Steinar */ -- Homepage: http://www.sesse.net/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#399523: [Pkg-uml-pkgs] Processed: really reassign
On Thu, Nov 23, 2006 at 04:51:40PM +0100, Nicolas Boullis wrote: In that case, it sounds more like a bug in initscripts to me? Sorry, I don't understand why you think it would be a bug in initscripts... Because initscripts is the package checking the fstab for NFS file systems, attempting to start nfs-common appropriately if needed. Also, its behaviour with regard to NFS at boot-time was recently changed multiple times... /* Steinar */ -- Homepage: http://www.sesse.net/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#398634: [phpgacl] alternative patch without hard dependencies on both db clients.
On Wed, Nov 22, 2006 at 01:44:43PM +0100, Andreas Henriksson wrote: Since I've already created it I'll send this patch to the BTS just for reference. This one takes the alternative route of not having a hard-dependency on both mysql- and postgresql-client, but instead recommends them both and checks which one is available during configuration. Shouldn't this code rather reside in dbconfig-common? /* Steinar */ -- Homepage: http://www.sesse.net/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#398563: poppassd: diff for NMU version 1.8.5-3.1
tags 398563 + patch thanks Hi, Attached is the diff for my poppassd 1.8.5-3.1 NMU. diff -Nru /tmp/dnGDzWSJFT/poppassd-1.8.5/debian/changelog /tmp/D3vuDdgJJt/poppassd-1.8.5/debian/changelog --- /tmp/dnGDzWSJFT/poppassd-1.8.5/debian/changelog 2006-11-21 19:57:16.0 +0100 +++ /tmp/D3vuDdgJJt/poppassd-1.8.5/debian/changelog 2006-11-21 19:57:16.0 +0100 @@ -1,3 +1,12 @@ +poppassd (1.8.5-3.1) unstable; urgency=high + + * Non-maintainer upload. + * Don't try to use update-inetd at purge time unless it is actually +available; fixes purge in some cases, patch from Andreas Henriksson. +(Closes: #398563) + + -- Steinar H. Gunderson [EMAIL PROTECTED] Tue, 21 Nov 2006 19:54:57 +0100 + poppassd (1.8.5-3) unstable; urgency=low * Move debian/copyright and debian/watch back to the old location. With diff -Nru /tmp/dnGDzWSJFT/poppassd-1.8.5/debian/postrm /tmp/D3vuDdgJJt/poppassd-1.8.5/debian/postrm --- /tmp/dnGDzWSJFT/poppassd-1.8.5/debian/postrm2006-11-21 19:57:16.0 +0100 +++ /tmp/D3vuDdgJJt/poppassd-1.8.5/debian/postrm2006-11-21 19:57:16.0 +0100 @@ -1,7 +1,10 @@ #!/bin/sh set -e -update-inetd --remove '^poppassd' -update-inetd --comment-chars #disabled# --enable poppassd + +if which update-inetd /dev/null 21 ; then + update-inetd --remove '^poppassd' + update-inetd --comment-chars #disabled# --enable poppassd +fi #DEBHELPER#
Bug#392953: [NONFREE-DOC:GFDL] package contains non-free documentation
On Sat, Nov 18, 2006 at 01:54:42PM +1030, Ron wrote:
I don't profess to be an authority on the details of this, which is why
I'm seeking clarification -- but it does seem fairly obvious to me that
any invariant section which inhibits our freedom to modify the source is
clearly not DFSG free...
What is not obvious to me, is that the invariant section here (in at
least the case I quoted) does anything of that sort at all. In this
case it just seems to make explicit something which has always been
the case, and which wouldn't change without that invariant section:
namely that you can't modify the GPL text included with, and referred
to by, that source.
After actually grep-ing through the source, I begin to see what you mean, I
think. I can only actually find a single GFDL source in the MinGW
documentation (perhaps the docs are in some other tarball?), namely
gcc-3.4.5-20060117-1/libstdc++-v3/docs/html/17_intro/porting.texi . It states
Copyright @copyright{} 2000, 2001, 2002, 2003 Free Software Foundation, Inc.
Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License, Version 1.2 or
any later version published by the Free Software Foundation; with the
Invariant Sections being ``GNU General Public License'', the Front-Cover
texts being (a) (see below), and with the Back-Cover Texts being (b)
(see below). A copy of the license is included in the section entitled
``GNU Free Documentation License''.
(a) The FSF's Front-Cover Text is:
A GNU Manual
(b) The FSF's Back-Cover Text is:
You have freedom to copy and modify this GNU Manual, like GNU
software. Copies published by the Free Software Foundation raise
funds for GNU development.
So, we have one invariant section (the GNU GPL), and front- and back-cover
texts. The invariant section, even here, is not actually a no-op; you cannot,
for instance, copy anything from porting.texi without including the invariant
section (save fair use). (I believe that if the GFDL permitted removal of
invariant sections, we wouldn't really have cared about them, but that's a
different story.) In addition, you have the front- and back-cover texts,
which are mini-invariant sections in their own rights; I believe they were
also covered by the GR.
/* Steinar */
--
Homepage: http://www.sesse.net/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#337562: qsynaptics: diff for NMU version 0.22.0-6.1
tags 337562 + patch
thanks
Hi,
Attached is the diff for my qsynaptics 0.22.0-6.1 NMU.
diff -Nru /tmp/uPsn7lvAZS/qsynaptics-0.22.0/debian/changelog
/tmp/SP7YEQSWCs/qsynaptics-0.22.0/debian/changelog
--- /tmp/uPsn7lvAZS/qsynaptics-0.22.0/debian/changelog 2006-11-18
12:56:50.0 +0100
+++ /tmp/SP7YEQSWCs/qsynaptics-0.22.0/debian/changelog 2006-11-18
12:56:50.0 +0100
@@ -1,3 +1,11 @@
+qsynaptics (0.22.0-6.1) unstable; urgency=high
+
+ * Non-maintainer upload.
+ * Revert change to architecture field to the version in 0.22.0-5; this
+package should not be built for s390. (Closes: #337562)
+
+ -- Steinar H. Gunderson [EMAIL PROTECTED] Sat, 18 Nov 2006 12:52:40 +0100
+
qsynaptics (0.22.0-6) unstable; urgency=low
* New maintainer (Closes: #373897)
diff -Nru /tmp/uPsn7lvAZS/qsynaptics-0.22.0/debian/control
/tmp/SP7YEQSWCs/qsynaptics-0.22.0/debian/control
--- /tmp/uPsn7lvAZS/qsynaptics-0.22.0/debian/control2006-11-18
12:56:50.0 +0100
+++ /tmp/SP7YEQSWCs/qsynaptics-0.22.0/debian/control2006-11-18
12:56:50.0 +0100
@@ -7,7 +7,7 @@
Standards-Version: 3.7.2
Package: qsynaptics
-Architecture: any
+Architecture: alpha amd64 arm hppa i386 ia64 m68k mips mipsel powerpc sparc
Depends: ${shlibs:Depends}, ${misc:Depends}, xserver-xorg-input-synaptics
Description: Synaptic TouchPad configuration tool
QSynaptics aims to help desktop users to configure their synaptics
Bug#389695: up-imapproxy: diff for NMU version 1.2.4-5.1
tags 389695 + patch thanks Hi, Attached is the diff for my up-imapproxy 1.2.4-5.1 NMU. diff -Nru /tmp/ltDENmLScu/up-imapproxy-1.2.4/debian/changelog /tmp/hJRo061wx6/up-imapproxy-1.2.4/debian/changelog --- /tmp/ltDENmLScu/up-imapproxy-1.2.4/debian/changelog 2006-11-18 15:55:38.0 +0100 +++ /tmp/hJRo061wx6/up-imapproxy-1.2.4/debian/changelog 2006-11-18 15:55:38.0 +0100 @@ -1,3 +1,12 @@ +up-imapproxy (1.2.4-5.1) unstable; urgency=high + + * Non-maintainer upload. + * Remove the odd grep hack; it broke upgrades, as we don't get any warnings +on stop anymore, and the non-zero return status of grep killed the init +script. (Closes: #389695) + + -- Steinar H. Gunderson [EMAIL PROTECTED] Sat, 18 Nov 2006 15:51:36 +0100 + up-imapproxy (1.2.4-5) unstable; urgency=high * Code enhancements
Bug#397412: wmaker: Wmaker crash on creating desktop
On Fri, Nov 17, 2006 at 01:55:17PM +0500, jamhed wrote: We got it. Finally :) Well, it's a step, at least, but it doesn't really help all that much. Lines 123 and 124 are 123 wWorkspaceMenuUpdate(scr, scr-workspace_menu); 124 wWorkspaceMenuUpdate(scr, scr-clip_ws_menu); And the only way it could SIGSEGV in line 124, was if scr (that is, the pointer) was somehow invalid -- but if line 123 was run first (which I'd assume, even with -O2), scr would have to be valid (unless, of course, wWorkspaceMenuUpdate was inlined, but it's big and -O2 doesn't normally inline functions like that). Did you try running it in valgrind? It might shed some light on what's happening here. /* Steinar */ -- Homepage: http://www.sesse.net/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#397412: wmaker: Wmaker crash on creating desktop
On Fri, Nov 17, 2006 at 04:59:28PM +0500, jamhed wrote: What is strange to me that different compiler optimization produces such a devastating difference. Not really; if it's doing undefined stuff (like writing outside structs), it's just what you would expect happening: Crashes that vary at random with seemingly non-related changes (often with optimization). Could it be a compiler bug also ? Yes, but it's rather unlikely. /* Steinar */ -- Homepage: http://www.sesse.net/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#397412: wmaker: Wmaker crash on creating desktop
On Fri, Nov 17, 2006 at 05:13:17PM +0500, jamhed wrote: .xinitrc: valgrind --tool=memcheck --leak-check=full --log-file=/tmp/wmaker.grind wmaker Well, could you please try the debug2 version too? It looks like this was the debug1 version -- or doesn't it crash in valgrind? /* Steinar */ -- Homepage: http://www.sesse.net/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#397902: seq24: diff for NMU version 0.8.6-1.1
tags 397902 + patch thanks Hi, Attached is the diff for my seq24 0.8.6-1.1 NMU. -- Homepage: http://www.sesse.net/ diff -Nru /tmp/JCeWur6T65/seq24-0.8.6/debian/changelog /tmp/qxvnCKBV3A/seq24-0.8.6/debian/changelog --- /tmp/JCeWur6T65/seq24-0.8.6/debian/changelog2006-11-17 16:28:10.0 +0100 +++ /tmp/qxvnCKBV3A/seq24-0.8.6/debian/changelog2006-11-17 16:28:10.0 +0100 @@ -1,3 +1,16 @@ +seq24 (0.8.6-1.1) unstable; urgency=high + + * Non-maintainer upload. + + [ Steve Langasek ] + * High-urgency upload for RC bugfix. + * Call autoconf *explicitly* when building, to ensure that our +configure script is built from macros that are reliably consistent +with the Makefile.in's generated by automake. Closes: #397902. + * Add autoconf to the build-depends for the above. + + -- Steinar H. Gunderson [EMAIL PROTECTED] Fri, 17 Nov 2006 16:20:55 +0100 + seq24 (0.8.6-1) unstable; urgency=low * New upstream version diff -Nru /tmp/JCeWur6T65/seq24-0.8.6/debian/control /tmp/qxvnCKBV3A/seq24-0.8.6/debian/control --- /tmp/JCeWur6T65/seq24-0.8.6/debian/control 2006-11-17 16:28:10.0 +0100 +++ /tmp/qxvnCKBV3A/seq24-0.8.6/debian/control 2006-11-17 16:28:10.0 +0100 @@ -2,7 +2,7 @@ Section: sound Priority: optional Maintainer: Guenter Geiger (Debian/GNU) [EMAIL PROTECTED] -Build-Depends: debhelper ( 4.0.0), automake1.9, autotools-dev, cdbs, libgtkmm-2.4-dev, libasound2-dev, libjack0.100.0-dev | libjack-dev +Build-Depends: debhelper ( 4.0.0), automake1.9, autoconf, autotools-dev, cdbs, libgtkmm-2.4-dev, libasound2-dev, libjack0.100.0-dev | libjack-dev Standards-Version: 3.6.2 Package: seq24 diff -Nru /tmp/JCeWur6T65/seq24-0.8.6/debian/rules /tmp/qxvnCKBV3A/seq24-0.8.6/debian/rules --- /tmp/JCeWur6T65/seq24-0.8.6/debian/rules2006-11-17 16:28:10.0 +0100 +++ /tmp/qxvnCKBV3A/seq24-0.8.6/debian/rules2006-11-17 16:28:10.0 +0100 @@ -6,6 +6,8 @@ build-tree/$(DEB_TAR_SRCDIR)/RTC DEB_AUTO_UPDATE_AUTOMAKE := 1.9 +DEB_AUTO_UPDATE_ACLOCAL := 1.9 +DEB_AUTO_UPDATE_AUTOCONF := 2.50 include /usr/share/cdbs/1/rules/tarball.mk include /usr/share/cdbs/1/rules/simple-patchsys.mk
Bug#397412: wmaker: Wmaker crash on creating desktop
On Fri, Nov 17, 2006 at 11:59:27PM +0500, jamhed wrote: Well, could you please try the debug2 version too? It looks like this was the debug1 version -- or doesn't it crash in valgrind? What is debug2 ? I didnt figured it from man. The last Debian package I sent you. /* Steinar */ -- Homepage: http://www.sesse.net/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#397412: wmaker: Wmaker crash on creating desktop
On Sat, Nov 18, 2006 at 12:21:57AM +0500, jamhed wrote: The last Debian package I sent you. It was debug2. I've run it with valgrind and crash it. That's odd; the valgrind log you sent didn't contain anything about a crash. Actually, when I look at it, it looks incomplete; it's supposed to print out more stuff when it ends... /* Steinar */ -- Homepage: http://www.sesse.net/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#396653: listen: Fails to start with home over NFS
severity 396653 important thanks On Tue, Nov 14, 2006 at 07:13:43PM +0100, Julien Valroff wrote: I have been able to launch listen with home over NFS (tested with NFS server in both Sarge and Unstable, with both clients in Etch and Unstable). Please try the proposed tests to check if your .listen is corrupted or not. Since nobody else can reproduce this, I've been given permission from the RMs to downgrade the bug. /* Steinar */ -- Homepage: http://www.sesse.net/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#399127: FTBFS
Package: missingpy Version: 0.8.9 Severity: serious Hi, When trying to build missingpy to look closer at #395104, I discovered that it does not build from source: [ 9 of 12] Compiling MissingPy.FileArchive.GZip ( MissingPy/FileArchive/GZip.hs, dist/build/MissingPy/FileArchive/GZip.o ) [10 of 12] Compiling MissingPy.FileArchive.BZip2 ( MissingPy/FileArchive/BZip2.hs, dist/build/MissingPy/FileArchive/BZip2.o ) [11 of 12] Compiling Python.Objects.Dict ( Python/Objects/Dict.hs, dist/build/Python/Objects/Dict.o ) [12 of 12] Compiling MissingPy.AnyDBM ( MissingPy/AnyDBM.hs, dist/build/MissingPy/AnyDBM.o ) Python/Objects/File.hs:63:7: Could not find module `MissingH.IO.HVIO': Perhaps you haven't installed the profiling libraries for package MissingH-0.16.0? Use -v to see a list of the files searched for. Preprocessing library MissingPy-0.8.6... Building MissingPy-0.8.6... ./setup build files: 256 at /usr/share/haskell-devscripts//Dh_Haskell.pm line 138, COMPAT_IN line 1. make: *** [install] Error 9 debuild: fatal error at line 1228: fakeroot debian/rules binary failed -- 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-rc5 Locale: LANG=nb_NO.UTF-8, LC_CTYPE=nb_NO.UTF-8 (charmap=UTF-8) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#399127: FTBFS
On Fri, Nov 17, 2006 at 05:49:19PM -0600, John Goerzen wrote: That is weird. libghc6-missingh-dev is a build-depend. Did you have it installed? fugl:~/nmu/missingpy-0.8.9 dpkg -s libghc6-missingh-dev | grep -E '(Status|Version)' Status: install ok installed Version: 0.16.2 Or perhaps you turned on profiling? I didn't turn on anything; I just sourced the package and ran pbuilder-satisfydepends. What version of haskell-devscripts do you have? 0.5.14. /* Steinar */ -- Homepage: http://www.sesse.net/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
