Bug#403426: [Pkg-cryptsetup-devel] Bug#403426: kernel corrupts LUKS partition header on arm
* Jonas Meurer <[EMAIL PROTECTED]> [2006-12-30 04:49]: > I'm currently preparing a new upload of cryptsetup 1.0.4+svn22, which is > identical with the current upstream svn snapshot. does this version fix > bug #403426, or does it still occur? It still doesn't work on ARM, but with SVN (or 03_no_header_conv.dpatch which was taken from SVN) it no longer corrupts the LUKS header, so once this patch is applied this bug can be downgraded to important. -- Martin Michlmayr http://www.cyrius.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#404876: Output of gst-launch
On Sat, Dec 30, 2006 at 09:23:38AM +0200, Yavor Doganov wrote: > On Fri, Dec 29, 2006 at 02:45:14PM -0800, David Schleef wrote: > > Could you run: > > > > rm ~/.gstreamer-0.10/registry.*.xml > > GST_DEBUG=*:3 gst-launch --gst-debug-no-color > > > > and attach the output? > > Attached is the output produced on my machine running unstable. Now try: rm ~/.gstreamer-0.10/registry.*.xml gdb -args gst-launch-0.10 --gst-disable-registry-fork and give gdb the command 'run'. GDB will stop once with a SIGILL in the function 'test_altivec()' called by 'oil_cpu_fault_try()'. Use the command 'c' to continue when this happens (since it's not a problem). It should stop again with a SIGILL. Please capture the backtrace at this point and attach it to the bug. Just in case I forgot about some other CPU detection code, please enter 'c' again. It should say something like "Process Terminated, killed by signal". If it doesn't, it will probably continue along until it hits another SIGILL, at which point you should create a second backtrace. As an off the cuff guess, it's probably due to the ffmpeg plugin, /usr/lib/gstreamer-0.10/libgstffmpeg.so. You could attempt removing that to see if it starts working. (The test command above is bogus and will print an error, but it's not supposed to crash.) dave... -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#404471: wacom-kernel-source: cannot build/install using m-a or adept
severity 404471 important thanks On Mon, Dec 25, 2006 at 11:01:54AM +0100, Thomas Hühn wrote: > I'd like to get wacom-kernel-source building. > When I do a "m-a auto-build wacom" I see the ncurses dialog > "Build of the package wacom-kernel-source failed! How do you > wish to proceed?", but "VIEW" doesn't show a build log, so I exit. Support for module-assistant isn't release-critical by any means. > Then I try installing the package wacom-kernel-source in adept: > /var/lib/dpkg/info/wacom-kernel-source.postinst: line 49: [: too many > arguments > Warning: kernel headers don't match running Linux version. > Building wacom modules for Linux _CODE 13262 (this may take a few > minutes)... > and it exits the installation. And I can't reproduce this error. If the module source is only needed for older kernels, as mentioned, then there's no reason it /needs/ to be removed from etch; and the other userspace packages from this source package are certainly useful. So I'm downgrading this bug. Thanks, -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/
Processed: Re: Bug#404471: wacom-kernel-source: cannot build/install using m-a or adept
Processing commands for [EMAIL PROTECTED]: > severity 404471 important Bug#404471: wacom-kernel-source: cannot build/install using m-a or adept Severity set to `important' from `serious' > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#404358: NMU uploaded
Hi,
I uploaded an NMU of your package.
Please see this as help to get the package into a releaseable condition for
etch.
Please find the used diff below.
Cheers,
Andi
diff -Nur ../atari-fdisk-0.7.1~/debian/changelog
../atari-fdisk-0.7.1/debian/changelog
--- ../atari-fdisk-0.7.1~/debian/changelog 2006-10-23 18:32:43.0
+
+++ ../atari-fdisk-0.7.1/debian/changelog 2006-12-30 09:52:56.0
+
@@ -1,3 +1,11 @@
+atari-fdisk (0.7.1-5.3) unstable; urgency=high
+
+ * Non-maintainer upload.
+ * Using glibcs lseek() instead of the kernels to avoid failure in
+64bit-environments. Closes: #404358
+
+ -- Andreas Barth <[EMAIL PROTECTED]> Sat, 30 Dec 2006 09:50:10 +
+
atari-fdisk (0.7.1-5.2) unstable; urgency=medium
* Non-maintainer upload.
diff -Nur ../atari-fdisk-0.7.1~/disk.c ../atari-fdisk-0.7.1/disk.c
--- ../atari-fdisk-0.7.1~/disk.c2006-10-23 18:35:51.0 +
+++ ../atari-fdisk-0.7.1/disk.c 2006-12-30 09:53:46.0 +
@@ -60,13 +60,12 @@
"$Id: disk.c,v 1.10 1997/08/22 12:35:38 rnhodek Exp $";
#endif /* lint */
+#define _FILE_OFFSET_BITS 64
+
#include
#include
#include
#include
-#ifdef __linux__
-#include
-#endif
#include
#include
@@ -81,43 +80,13 @@
/*
* sseek: seek to specified sector - return 0 on failure
*
- * For >4GB disks lseek needs a > 32bit arg, and we have to use llseek.
+ * For >4GB disks lseek needs a > 32bit arg.
* On the other hand, a 32 bit sector number is OK until 2TB.
- * The routines _llseek and sseek below are the only ones that
- * know about the loff_t type.
+ *
+ * Thanks to _FILE_OFFSET_BITS, we can have GNU libc use an 64bit off_t even on
+ * 32bit platforms.
*/
-#ifdef SYS__llseek
-
-#define _llseek(fd, hi, lo, res, wh) syscall(SYS__llseek, fd, hi, lo, res, wh)
-
-/* seek to a sector */
-int sseek( unsigned int fd, unsigned long s )
-{
-loff_t in, out;
-
-in = (loff_t)s * SECTOR_SIZE;
-out = 1;
-
-if (_llseek (fd, in>>32, in & 0x, &out, SEEK_SET) != 0) {
- perror( "llseek" );
- fprintf( stderr, "seek error - cannot seek to sector %lu\n", s );
- return 0;
-}
-
-if (in != out) {
- fprintf( stderr, "seek error: wanted 0x%08x%08x, got 0x%08x%08x\n",
-(uint)(in>>32), (uint)(in & 0x),
-(uint)(out>>32), (uint)(out & 0x) );
- return 0;
-}
-return 1;
-}
-
-#else
-
-/* Sorry, kernel doesn't know _llseek call :-((( */
-
int sseek( unsigned int fd, unsigned long s )
{
off_t in, out;
@@ -136,8 +105,6 @@
return 1;
}
-#endif
-
/* read one sector */
void sread( char *buffer, unsigned long secno )
{
--
http://home.arcor.de/andreas-barth/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#404876: Backtrace
On Sat, Dec 30, 2006 at 12:49:36AM -0800, David Schleef wrote: > Now try: > >rm ~/.gstreamer-0.10/registry.*.xml >gdb -args gst-launch-0.10 --gst-disable-registry-fork > > and give gdb the command 'run'. GDB will stop once with a SIGILL in > the function 'test_altivec()' called by 'oil_cpu_fault_try()'. Use > the command 'c' to continue when this happens (since it's not a > problem). It should stop again with a SIGILL. Please capture the > backtrace at this point and attach it to the bug. It's not exactly as you describe: Program received signal SIGILL, Illegal instruction. [Switching to Thread 805422944 (LWP 16781)] 0x0e9fb2a8 in oil_cpu_get_flags () from /usr/lib/liboil-0.3.so.0 (gdb) bt #0 0x0e9fb2a8 in oil_cpu_get_flags () from /usr/lib/liboil-0.3.so.0 #1 0x0e9fb388 in oil_cpu_fault_check_try () from /usr/lib/liboil-0.3.so.0 #2 0x0e9fb544 in oil_cpu_fault_check_enable () from /usr/lib/liboil-0.3.so.0 #3 0x0e9fc660 in oil_init () from /usr/lib/liboil-0.3.so.0 #4 0x0ea6bc08 in gst_video_box_get_type () from /usr/lib/gstreamer-0.10/libgstvideobox.so #5 0x0fef69e4 in g_type_class_ref () from /usr/lib/libgobject-2.0.so.0 #6 0x0ff6a96c in gst_element_register (plugin=0x10050f48, name=0xea6d118 "videobox", rank=0, type=269068808) at gstelementfactory.c:273 #7 0x0ea6b904 in gst_video_box_get_type () from /usr/lib/gstreamer-0.10/libgstvideobox.so #8 0x0ff88050 in gst_plugin_register_func (plugin=0x10050f48, module=, desc=) at gstplugin.c:259 #9 0x0ff88648 in gst_plugin_load_file (filename=0x1003f4e8 "/usr/lib/gstreamer-0.10/libgstvideobox.so", error=0x0) at gstplugin.c:450 #10 0x0ff8e668 in gst_registry_scan_path_level (registry=0x10029000, path=0xffbf5fc "/usr/lib/gstreamer-0.10", level=10) at gstregistry.c:834 #11 0x0ff8e8f8 in gst_registry_scan_path (registry=0x10029000, path=0xffbf5fc "/usr/lib/gstreamer-0.10") at gstregistry.c:872 #12 0x0ff4dbd8 in scan_and_update_registry (default_registry=0x10029000, registry_file=0x1002acf8 "/home/yavor/.gstreamer-0.10/registry.powerpc.xml", write_changes=1) at gst.c:634 #13 0x0ff4de90 in init_post () at gst.c:674 #14 0x0fdd29a0 in g_option_context_parse () from /usr/lib/libglib-2.0.so.0 #15 0x10003618 in main (argc=2, argv=0x7f8d8a34) at gst-launch.c:551 (gdb) c Continuing. Program received signal SIGILL, Illegal instruction. 0x0d74e4cc in visual_cpu_get_tsc () from /usr/lib/libvisual-0.4.so.0 (gdb) bt #0 0x0d74e4cc in visual_cpu_get_tsc () from /usr/lib/libvisual-0.4.so.0 #1 0x0d74e588 in visual_cpu_initialize () from /usr/lib/libvisual-0.4.so.0 #2 0x0d748d88 in visual_init () from /usr/lib/libvisual-0.4.so.0 #3 0x0d77a2a0 in gst_visual_get_type () from /usr/lib/gstreamer-0.10/libgstlibvisual.so #4 0x0ff88050 in gst_plugin_register_func (plugin=0x100e4570, module=, desc=) at gstplugin.c:259 #5 0x0ff88648 in gst_plugin_load_file (filename=0x10103168 "/usr/lib/gstreamer-0.10/libgstlibvisual.so", error=0x0) at gstplugin.c:450 #6 0x0ff8e668 in gst_registry_scan_path_level (registry=0x10029000, path=0x100e4570 "\020\002l\030", level=10) at gstregistry.c:834 #7 0x0ff8e8f8 in gst_registry_scan_path (registry=0x10029000, path=0xffbf5fc "/usr/lib/gstreamer-0.10") at gstregistry.c:872 #8 0x0ff4dbd8 in scan_and_update_registry (default_registry=0x10029000, registry_file=0x1002acf8 "/home/yavor/.gstreamer-0.10/registry.powerpc.xml", write_changes=1) at gst.c:634 #9 0x0ff4de90 in init_post () at gst.c:674 #10 0x0fdd29a0 in g_option_context_parse () from /usr/lib/libglib-2.0.so.0 #11 0x10003618 in main (argc=2, argv=0x7f8d8a34) at gst-launch.c:551 (gdb) c Continuing. reading register r0 (#0): No such process. > As an off the cuff guess, it's probably due to the ffmpeg plugin, > /usr/lib/gstreamer-0.10/libgstffmpeg.so. You could attempt removing > that to see if it starts working. Removing this file doesn't change the behaviour. However, if I remove libgstlibvisual.so, I get the following while launching the first command with LANG=C: 0:00:01.701811000 16833 0x1001ae50 INFO GST_PIPELINE gstparse.c:150:gst_parse_launch: parsing pipeline description 0:00:01.702656000 16833 0x1001ae50 ERROR GST_PIPELINE ./grammar.y:765:_gst_parse__yyparse: empty pipeline not allowed ERROR: pipeline could not be constructed: empty pipeline not allowed. Amazingly, if I restore the file I continue to get the same error (removing ~/.gstreamer-0.10/registry.powerpc.xml every time). -- Best regards / SSC Varna | E-mail: [EMAIL PROTECTED] Yavor Doganov| Mobile: +359 88 7517748 Southway Shipping Consultancy Ltd.-Gibraltar, Varna Branch Ph: +359 52 600129, 600130, 603643 | Fax: +359 52 603612 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#405006: libgphoto2: mistake in udev rules gives permissions to non-gphoto2 devices
Package: libgphoto2-2
Version: 2.2.1-12
Severity: grave
Tags: security
In /etc/udev/libgphoto2_generic_ptp_support.rules, there is the following
rule:
ACTION=="add", SUBSYSTEM=="usb_device", ENV{INTERFACE}="6/1/1", \
PROGRAM="/bin/sh -c 'K=%k; K=$${K#usbdev}; printf bus/usb/%%03i/%%03i
$${K.*} $${K#*.}'", \
NAME="%c", MODE="0660", GROUP="plugdev"
The single = sign after ENV{INTERFACE} means that the INTERFACE environment
variable is set, not queried. The result is that all USB devices, and not
only the PTP ones, are set to the plugdev group, thus giving some users
access to devices they should not have access to.
Suggested fix: put two equals signs
Regards,
--
Nicolas George
Irrelevant system information:
ii adduser 3.100
ii libc6 2.3.6.ds1-8
ii libexif12 0.6.13-5
ii libgphoto2-port0 2.2.1-12
ii libjpeg62 6b-13
ii libltdl3 1.5.22-4
ii udev 0.103-1
Linux hellroy 2.6.18-3-686 #1 SMP Mon Dec 4 16:41:14 UTC 2006 i686 GNU/Linux
signature.asc
Description: Digital signature
Bug#404358: marked as done (atari-fdisk-cross: after Etch upgrade to kernel 2.6.18, no longer works)
Your message dated Sat, 30 Dec 2006 10:17:02 + with message-id <[EMAIL PROTECTED]> and subject line Bug#404358: fixed in atari-fdisk 0.7.1-5.3 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) --- Begin Message --- Package: atari-fdisk-cross Version: 0.7.1-5.2 Severity: grave Justification: renders package unusable -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 After upgrading to Etch, immediately after the freeze started, I needed to access this ATARI disk to fetch old files. While the ext2 partions can be accessed, the FAT partitions no longer can. As a test, I tried listing the partition table, which gave me this: 8X- <[EMAIL PROTECTED]:/root># atari-fdisk -l <[EMAIL PROTECTED]:/root># atari-fdisk -r /dev/sdb Unable to open /dev/sdb <[EMAIL PROTECTED]:/root># grep ATARI /boot/config-2.6.18-3-486 CONFIG_ATARI_PARTITION=y <[EMAIL PROTECTED]:/root># 8X- The kernel seen above is: ii linux-image-2.6.18-3-486 2.6.18-7 Linux 2.6.18 image on x86 The relevant part from 'dmesg': 8X- SCSI device sdb: 8925000 512-byte hdwr sectors (4570 MB) sdb: Write Protect is off sdb: Mode Sense: b9 00 00 08 SCSI device sdb: drive cache: write back SCSI device sdb: 8925000 512-byte hdwr sectors (4570 MB) sdb: Write Protect is off sdb: Mode Sense: b9 00 00 08 SCSI device sdb: drive cache: write back sdb: AHDI sdb1 sdb2 sdb3 XGM< sdb4 sdb5 sdb6 sdb7 sdb8 sdb9 sdb10 sdb11 > sd 0:0:1:0: Attached scsi disk sdb 8X- ...and the relevant /etc/fstab fragment: /dev/sdb1 /TT030/C msdos errors=remount-ro,noauto,atari=yes 0 2 /dev/sdb2 /TT030/D msdos errors=remount-ro,noauto,atari=yes 0 2 /dev/sdb3 /TT030/E ext2 errors=remount-ro,noauto 0 2 /dev/sdb4 /TT030/F ext2 errors=remount-ro,noauto 0 2 /dev/sdb5 /TT030/G ext2 errors=remount-ro,noauto 0 2 /dev/sdb6 /TT030/H ext2 errors=remount-ro,noauto 0 2 /dev/sdb7 /TT030/I vfat errors=remount-ro,noauto,atari=yes 0 2 /dev/sdb8 /TT030/J swap sw 0 2 /dev/sdb9 /TT030/K ext2 errors=remount-ro,noauto 0 2 /dev/sdb10 /TT030/L msdos errors=remount-ro,noauto,atari=yes 0 2 /dev/sdb11 /TT030/M ext2 errors=remount-ro,noauto 0 2 - -- System Information: Debian Release: 4.0 APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i586) Shell: /bin/sh linked to /bin/dash Kernel: Linux 2.6.18-3-486 Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8) Versions of packages atari-fdisk-cross depends on: ii libc62.3.6.ds1-8 GNU C Library: Shared libraries atari-fdisk-cross recommends no packages. - -- no debconf information -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFFjaqoeXr56x4Muc0RAqHyAJ4/y3l6bSZuc5+Y5dSiBPy/FWiSxACfZJ79 mitmFU/jz6I8B45iFvzffJI= =5COz -END PGP SIGNATURE- --- End Message --- --- Begin Message --- Source: atari-fdisk Source-Version: 0.7.1-5.3 We believe that the bug you reported is fixed in the latest version of atari-fdisk, which is due to be installed in the Debian FTP archive: atari-fdisk-cross_0.7.1-5.3_amd64.deb to pool/main/a/atari-fdisk/atari-fdisk-cross_0.7.1-5.3_amd64.deb atari-fdisk_0.7.1-5.3.dsc to pool/main/a/atari-fdisk/atari-fdisk_0.7.1-5.3.dsc atari-fdisk_0.7.1-5.3.tar.gz to pool/main/a/atari-fdisk/atari-fdisk_0.7.1-5.3.tar.gz A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Barth <[EMAIL PROTECTED]> (supplier of updated atari-fdisk package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sat, 30 Dec 2006 09:50:10 + Source: atari-fdisk Binary: atari-fdisk-cross atari-fdisk-udeb atari-fdisk Architecture: source amd64 Version: 0.7.1-5.3 Distribution: unstable Urgency: high Maintainer: Roman Hodek <[EMAIL PROTECTED]> Changed-By: Andreas Barth <[EMAIL PROTECTED]> Description: atari-fdisk-cross - Partition edito
Processed: Ugly bug
Processing commands for [EMAIL PROTECTED]: > severity 380396 serious Bug#380396: Paramétrage de xfonts-cmex-big5p (0.1-5.1) ...usage error: unrecognized option Severity set to `serious' from `normal' > tags 380396 help Bug#380396: Paramétrage de xfonts-cmex-big5p (0.1-5.1) ...usage error: unrecognized option There were no tags set. Tags added: help > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#403426: kernel corrupts LUKS partition header on arm
At Fri, 29 Dec 2006 21:24:34 +0100, Martin Michlmayr <[EMAIL PROTECTED]> wrote: > > * Clemens Fruhwirth <[EMAIL PROTECTED]> [2006-12-29 11:52]: > > Please try the version from subversion > > http://luks.endorphin.org/svn/cryptsetup > > With 1.0.4 plus the attached 2 patches from SVN I no longer get any > corruption but I also cannot access my encrypted data. That's good :) > Is there anything else I should try? > foobar:~# cryptsetup luksOpen /dev/sda5 x > Enter LUKS passphrase: > device-mapper: table: 254:0: crypt: Device lookup failed > device-mapper: ioctl: error adding target to table > device-mapper: ioctl: device doesn't appear to be in the dev hash table. > Failed to setup dm-crypt key mapping. > Check kernel for support for the aes-cbc-essiv:sha256 cipher spec and verify > that /dev/sda5 contains at least 133 sectors. > Failed to read from key storage Are you sure we don't see any device mapper problems here? You might just go over to a box where LUKS works (when the LUKS partition does not contain anything security relevant to you), and do dmsetup table mappingname > dm-table-file open it up, and find the 7th entry that says something like x:y (major:minor device number of your underlaying device). Replace this by your correct device path on the arm box, copy that file over to arm and set it up as dmsetup create mappingname dm-table-file If that does not work, we are seeing a dm-crypt layer problem here. > Enter LUKS passphrase: I just commited a patch that prevents password retrying with I/O errors. -- Fruhwirth Clemens - http://clemens.endorphin.org for robots: [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#391404: NMU uploaded
Hi,
I uploaded an NMU of your package. The real issue was BTW that make
install installed the man pages in libapache2-modxslt, and dh_installman
installed them somewhere else.
Please see this as help to get the package into a releaseable condition for
etch.
Please find the used diff below.
Cheers,
Andi
diff -Nur ../modxslt-2005072700~/debian/changelog
../modxslt-2005072700/debian/changelog
--- ../modxslt-2005072700~/debian/changelog 2006-12-30 10:43:36.0
+
+++ ../modxslt-2005072700/debian/changelog 2006-12-30 10:54:43.0
+
@@ -1,3 +1,14 @@
+modxslt (2005072700-2.1) unstable; urgency=high
+
+ * Non-maintainer upload.
+ * Remove debian/modxslt-config.1, debian/modxslt-parse.1 and
+debian/modxslt-perror.1 and use the originals in doc/man instead.
+ * Use $packagename.manpages to ship the manpages.
+ * Ship modxslt-config.1 in libmodxslt0, modxslt-parse.1 and
+modxslt-perror.1 only in modxslt-tools. Closes: #391404
+
+ -- Andreas Barth <[EMAIL PROTECTED]> Sat, 30 Dec 2006 10:43:48 +
+
modxslt (2005072700-2) unstable; urgency=low
* Dropped 01_autotools.dpatch
diff -Nur ../modxslt-2005072700~/debian/rules ../modxslt-2005072700/debian/rules
--- ../modxslt-2005072700~/debian/rules 2006-12-30 10:43:36.0 +
+++ ../modxslt-2005072700/debian/rules 2006-12-30 11:07:55.0 +
@@ -101,6 +101,8 @@
./configure --prefix=/usr --with-sapi=apache2 --enable-exslt
$(MAKE) SAPI_CC=gcc
$(MAKE) install DESTDIR=$(CURDIR)/debian/libapache2-modxslt
+ # remove the just installed manpages again - we do that different
within debian
+ rm -rf $(CURDIR)/debian/libapache2-modxslt/usr/share/man/
cp debian/modxslt.load
$(CURDIR)/debian/libapache2-modxslt/etc/apache2/mods-available/
cp $(CURDIR)/debian/modxslt.libapache2
$(CURDIR)/debian/libapache2-modxslt/etc/apache2/conf.d/modxslt
rm -rf $(CURDIR)/debian/libapache2-modxslt/usr/{bin,include,man}
$(CURDIR)/debian/libapache2-modxslt/usr/lib/lib*
@@ -134,8 +136,7 @@
dh_installchangelogs -a
dh_installdocs -a
dh_installexamples -a
- dh_installman -pmodxslt-tools debian/modxslt-perror.1
debian/modxslt-parse.1
- dh_installman -plibmodxslt0-dev debian/modxslt-config.1
+ dh_installman -a
dh_link -a
dh_strip -a
dh_compress -a
diff -Nur ../modxslt-2005072700~/debian/modxslt-tools.manpages
../modxslt-2005072700/debian/modxslt-tools.manpages
--- ../modxslt-2005072700~/debian/modxslt-tools.manpages1970-01-01
00:00:00.0 +
+++ ../modxslt-2005072700/debian/modxslt-tools.manpages 2006-12-30
10:53:43.0 +
@@ -0,0 +1,2 @@
+doc/man/modxslt-perror.1
+doc/man/modxslt-parse.1
diff -Nur ../modxslt-2005072700~/debian/libmodxslt0.manpages
../modxslt-2005072700/debian/libmodxslt0.manpages
--- ../modxslt-2005072700~/debian/libmodxslt0.manpages 1970-01-01
00:00:00.0 +
+++ ../modxslt-2005072700/debian/libmodxslt0.manpages 2006-12-30
10:54:13.0 +
@@ -0,0 +1 @@
+doc/man/modxslt-config.1
diff -Nur ../modxslt-2005072700~/helpers/config.sub
../modxslt-2005072700/helpers/config.sub
--- ../modxslt-2005072700~/helpers/config.sub 2006-12-30 10:43:36.0
+
+++ ../modxslt-2005072700/helpers/config.sub2006-12-30 10:55:41.0
+
@@ -4,7 +4,7 @@
# 2000, 2001, 2002, 2003, 2004, 2005, 2006 Free Software Foundation,
# Inc.
-timestamp='2006-09-20'
+timestamp='2006-07-02'
# This file is (in principle) common to ALL GNU software.
# The presence of a machine in this file suggests that SOME GNU software
@@ -276,7 +276,6 @@
| pdp10 | pdp11 | pj | pjl \
| powerpc | powerpc64 | powerpc64le | powerpcle | ppcbe \
| pyramid \
- | score \
| sh | sh[1234] | sh[24]a | sh[23]e | sh[34]eb | sheb | shbe | shle |
sh[1234]le | sh3ele \
| sh64 | sh64le \
| sparc | sparc64 | sparc64b | sparc64v | sparc86x | sparclet |
sparclite \
@@ -285,7 +284,7 @@
| tahoe | thumb | tic4x | tic80 | tron \
| v850 | v850e \
| we32k \
- | x86 | xc16x | xscale | xscalee[bl] | xstormy16 | xtensa \
+ | x86 | xscale | xscalee[bl] | xstormy16 | xtensa \
| z8k)
basic_machine=$basic_machine-unknown
;;
@@ -368,7 +367,7 @@
| tron-* \
| v850-* | v850e-* | vax-* \
| we32k-* \
- | x86-* | x86_64-* | xc16x-* | xps100-* | xscale-* | xscalee[bl]-* \
+ | x86-* | x86_64-* | xps100-* | xscale-* | xscalee[bl]-* \
| xstormy16-* | xtensa-* \
| ymp-* \
| z8k-*)
@@ -910,10 +909,6 @@
sb1el)
basic_machine=mipsisa64sb1el-unknown
;;
- sde)
- basic_machine=mipsisa32-sde
- os=-elf
- ;;
sei)
basic_machine=mips-sei
os=-seiux
@@ -1371,9 +1366,6 @@
# system, and we'll never get to
Bug#405012: libwmf: Dependencies problem on experimental
Package: libwmf Version: 0.2.8.4-2 Severity: grave Justification: renders package unusable *** Please type your report below this line *** As of Sat 30 Dic 2006 this package is not installable on debian experimental due to dependancies problem (libgtk2.0-0 (=2.10.6-4) conflicts with libwmf0.2-7 (<=0.2.8.4-2)) Plese note that this also breaks gimp (and possibily other stuff which depends on libwmf0.2-7 (>=0.2.8.4-2)) How to fix: just bump the revision to -3. Gimp works for me if I do so. No errors reported by make -- System Information: Debian Release: 4.0 APT prefers experimental APT policy: (990, 'experimental'), (800, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-nanomad Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#380396: Happens here, too.... here is the message in English
* Anthony DeRobertis ([EMAIL PROTECTED]) [061003 08:03]:
> Just hit this in a Sarge + Backports -> Etch upgrade:
>
> Setting up xfonts-cmex-big5p (0.1-5.1) ...
> usage error: unrecognized option
> Usage: update-fonts-dir DIRECTORY ...
>update-fonts-dir { -h | --help }
I *think* this comes from the fact that postinst calls:
# Automatically added by dh_installxfonts
if which update-fonts-dir >/dev/null 2>&1; then
update-fonts-dir --x11r7-layout misc;update-fonts-alias misc
fi
# End automatically added section
However, the package depends on xutils, which doesn't necessarily have
the new update-fonts-dir. Solution: Fix the dependency.
Cheers,
Andi
--
http://home.arcor.de/andreas-barth/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#382030:
I've seen SIGPIPE from cfexecd from time to time, but not from cfservd. It's usually, in my experience, and from what I've seen on the cfengine mailing list, due to configuration errors. I agree that a configuration error should not cause the daemon to crash, and it's therefore a bug, but you should switch on the runtime debugging with - d2 as a command line option to cfservd, which should help you discover what's going on (and the same option will help the second poster here, whose problem sounds like a different one to me, just use it on cfagent rather than cfservd) I think SIGPIPE tends to happen when cfengine is spawning a task to do something, but a configuration error causes that subtask to exit unexpectedly. Tim -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#405014: planner: potential FTBFS since newest python-support
Package: planner Version: 0.14.2-1 Severity: serious Justification: no longer builds from source -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 While polishing the packaging of another software, I noticed that recent versions of either CDBS, dh_python or dh_pysupport require an environment variable called DEB_PYTHON_SYSTEM in debian/rules. I have already patched debian/control and debian/rules to fix this (upload pending); this report just files the existence of this potential FTBFS bug. - -- System Information: Debian Release: 4.0 APT prefers testing APT policy: (550, 'testing') Architecture: powerpc (ppc) Shell: /bin/sh linked to /bin/dash Kernel: Linux 2.6.18-imac Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8) Versions of packages planner depends on: ii gconf2 2.16.0-3 GNOME configuration database syste ii libart-2.0-2 2.3.17-1 Library of functions for 2D graphi ii libatk1.0-01.12.3-1 The ATK accessibility toolkit ii libbonobo2-0 2.14.0-3 Bonobo CORBA interfaces library ii libbonoboui2-0 2.14.0-5 The Bonobo UI library ii libc6 2.3.6.ds1-8 GNU C Library: Shared libraries ii libcairo2 1.2.4-4 The Cairo 2D vector graphics libra ii libfontconfig1 2.4.1-2 generic font configuration library ii libgconf2-42.16.0-3 GNOME configuration database syste ii libgda2-3 1.2.3-3 GNOME Data Access library for GNOM ii libglade2-01:2.6.0-3 library to load .glade files at ru ii libglib2.0-0 2.12.4-2 The GLib library of C routines ii libgnome-keyring0 0.6.0-3 GNOME keyring services library ii libgnome2-02.16.0-2 The GNOME 2 library - runtime file ii libgnomecanvas2-0 2.14.0-2 A powerful object-oriented display ii libgnomeprint2.2-0 2.12.1-7 The GNOME 2.2 print architecture - ii libgnomeprintui2.2-0 2.12.1-4 GNOME 2.2 print architecture User ii libgnomeui-0 2.14.1-2 The GNOME 2 libraries (User Interf ii libgnomevfs2-0 2.14.2-4 GNOME virtual file-system (runtime ii libgtk2.0-02.8.20-3 The GTK+ graphical user interface ii libice61:1.0.1-2 X11 Inter-Client Exchange library ii liborbit2 1:2.14.3-0.1 libraries for ORBit2 - a CORBA ORB ii libpango1.0-0 1.14.8-3 Layout and rendering of internatio ii libpopt0 1.10-3lib for parsing cmdline parameters ii libsm6 1:1.0.1-3 X11 Session Management library ii libx11-6 2:1.0.3-4 X11 client-side library ii libxcursor11.1.7-4 X cursor management library ii libxext6 1:1.0.1-2 X11 miscellaneous extension librar ii libxfixes3 1:4.0.1-5 X11 miscellaneous 'fixes' extensio ii libxi6 1:1.0.1-4 X11 Input extension library ii libxinerama1 1:1.0.1-4.1 X11 Xinerama extension library ii libxml22.6.27.dfsg-1 GNOME XML library ii libxrandr2 2:1.1.0.2-5 X11 RandR extension library ii libxrender11:0.9.1-3 X Rendering Extension client libra ii libxslt1.1 1.1.19-1 XSLT processing library - runtime ii python2.4 2.4.4-1 An interactive high-level object-o ii scrollkeeper 0.3.14-11 A free electronic cataloging syste ii shared-mime-info 0.19-1FreeDesktop.org shared MIME databa ii zlib1g 1:1.2.3-13compression library - runtime Versions of packages planner recommends: ii gda2-postgres 1.2.3-3PostgreSQL backend plugin for GNOM - -- no debconf information -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFFllGYeXr56x4Muc0RAtBnAKCMZh5b9b2dvvS9yoPsfKC6L75gzACgqR5b zH/2SpXATsaqGwk+/ScUsH0= =j+sH -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#391404: marked as done (libapache2-modxslt: conflicts with modxslt-tools)
Your message dated Sat, 30 Dec 2006 11:32:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#391404: fixed in modxslt 2005072700-2.1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) --- Begin Message --- Package: libapache2-modxslt Version: 2005072700-1 Severity: normal I tried to dist-upgrade my testing system today, resulting in this error: Preparing to replace libapache2-modxslt 2004112100-3.1 (using .../libapache2-modxslt_2005 072700-1_i386.deb) ... Unpacking replacement libapache2-modxslt ... dpkg: error processing /var/cache/apt/archives/libapache2-modxslt_2005072700-1_i386.deb ( --unpack): trying to overwrite `/usr/share/man/man1/modxslt-parse.1.gz', which is also in package m odxslt-tools Errors were encountered while processing: /var/cache/apt/archives/libapache2-modxslt_2005072700-1_i386.deb E: Sub-process /usr/bin/dpkg returned an error code (1) -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.15-1-686 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) Versions of packages libapache2-modxslt depends on: ii libapr02.0.55-4.1the Apache Portable Runtime ii libc6 2.3.6.ds1-4 GNU C Library: Shared libraries ii libmodxslt02005072700-1 modxslt libraries to parse XML usi ii libpcre3 6.4-2 Perl 5 Compatible Regular Expressi ii libxml22.6.26.dfsg-3 GNOME XML library ii libxslt1.1 1.1.17-4 XSLT processing library - runtime libapache2-modxslt recommends no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: modxslt Source-Version: 2005072700-2.1 We believe that the bug you reported is fixed in the latest version of modxslt, which is due to be installed in the Debian FTP archive: libapache-modxslt_2005072700-2.1_amd64.deb to pool/main/m/modxslt/libapache-modxslt_2005072700-2.1_amd64.deb libapache2-modxslt_2005072700-2.1_amd64.deb to pool/main/m/modxslt/libapache2-modxslt_2005072700-2.1_amd64.deb libmodxslt0-dev_2005072700-2.1_amd64.deb to pool/main/m/modxslt/libmodxslt0-dev_2005072700-2.1_amd64.deb libmodxslt0_2005072700-2.1_amd64.deb to pool/main/m/modxslt/libmodxslt0_2005072700-2.1_amd64.deb modxslt-doc_2005072700-2.1_all.deb to pool/main/m/modxslt/modxslt-doc_2005072700-2.1_all.deb modxslt-tools_2005072700-2.1_amd64.deb to pool/main/m/modxslt/modxslt-tools_2005072700-2.1_amd64.deb modxslt_2005072700-2.1.diff.gz to pool/main/m/modxslt/modxslt_2005072700-2.1.diff.gz modxslt_2005072700-2.1.dsc to pool/main/m/modxslt/modxslt_2005072700-2.1.dsc A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Barth <[EMAIL PROTECTED]> (supplier of updated modxslt package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sat, 30 Dec 2006 10:43:48 + Source: modxslt Binary: modxslt-tools libapache-modxslt modxslt-doc libmodxslt0 libapache2-modxslt libmodxslt0-dev Architecture: source amd64 all Version: 2005072700-2.1 Distribution: unstable Urgency: high Maintainer: Riccardo Setti <[EMAIL PROTECTED]> Changed-By: Andreas Barth <[EMAIL PROTECTED]> Description: libapache-modxslt - XSLT processing module for Apache based on libxml2 libapache2-modxslt - XSLT processing module for Apache 2.0.x based on libxml2 libmodxslt0 - modxslt libraries to parse XML using XSLT stylesheets libmodxslt0-dev - Development header for libmodxslt modxslt-doc - Documentation for modxslt modxslt-tools - modxslt command line tools Closes: 391404 Changes: modxslt (2005072700-2.1) unstable; urgency=high . * Non-maintainer upload. * Remove debian/modxslt-config.1, debian/modxslt-parse.1 and debian/modxslt-perror.1 and use the originals in doc/man instead. * Use $packagename.manpages to ship the manpages. * Ship modxslt-config.1 in libmodxslt0, modxslt-parse.1 and modxslt-perror.1 only in modxslt-tools. Closes: #391404 Files: f113c
Bug#391404: NMU uploaded
On Sat, Dec 30, 2006 at 12:17:08 +0100, Andreas Barth wrote: > diff -Nur ../modxslt-2005072700~/debian/changelog > ../modxslt-2005072700/debian/changelog > --- ../modxslt-2005072700~/debian/changelog 2006-12-30 10:43:36.0 > + > +++ ../modxslt-2005072700/debian/changelog2006-12-30 10:54:43.0 > + > @@ -1,3 +1,14 @@ > +modxslt (2005072700-2.1) unstable; urgency=high > + > + * Non-maintainer upload. > + * Remove debian/modxslt-config.1, debian/modxslt-parse.1 and > +debian/modxslt-perror.1 and use the originals in doc/man instead. > + * Use $packagename.manpages to ship the manpages. > + * Ship modxslt-config.1 in libmodxslt0, modxslt-parse.1 and > +modxslt-perror.1 only in modxslt-tools. Closes: #391404 > + > + -- Andreas Barth <[EMAIL PROTECTED]> Sat, 30 Dec 2006 10:43:48 + > + I don't think you want to install any manpage in libmodxslt0, as that would make it conflict with a future libmodxslt1. The manpage should be in libmodxslt0-dev, IMHO. Cheers, Julien signature.asc Description: Digital signature
Bug#391404: libapache2-modxslt: conflicts with modxslt-tools
tags 391404 + patch
thanks
Hi!
I would like to send a patch, which fixes this bug. It's a minimal patch,
which simply removes manual pages from libapache2-modxslt binary package.
It's a part of my new maintainer application, so it looks like non-maintainer
upload. If you will use this patch, you may update changelog as you wish.
--
Sergei Golovan
diff -ruN modxslt-2005072700.orig/debian/changelog
modxslt-2005072700/debian/changelog
--- modxslt-2005072700.orig/debian/changelog2006-12-30 15:06:43.0
+0300
+++ modxslt-2005072700/debian/changelog 2006-12-30 15:06:59.0 +0300
@@ -1,3 +1,11 @@
+modxslt (2005072700-2.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Removed manual pages from libapache2-modxslt module to resolve conflict
+with libmodxslt0-dev and modxslt-tools (closes: #391404).
+
+ -- Sergei Golovan <[EMAIL PROTECTED]> Sat, 30 Dec 2006 14:22:41 +0300
+
modxslt (2005072700-2) unstable; urgency=low
* Dropped 01_autotools.dpatch
diff -ruN modxslt-2005072700.orig/debian/rules modxslt-2005072700/debian/rules
--- modxslt-2005072700.orig/debian/rules2006-12-30 15:06:43.0
+0300
+++ modxslt-2005072700/debian/rules 2006-12-30 15:06:59.0 +0300
@@ -103,7 +103,7 @@
$(MAKE) install DESTDIR=$(CURDIR)/debian/libapache2-modxslt
cp debian/modxslt.load
$(CURDIR)/debian/libapache2-modxslt/etc/apache2/mods-available/
cp $(CURDIR)/debian/modxslt.libapache2
$(CURDIR)/debian/libapache2-modxslt/etc/apache2/conf.d/modxslt
- rm -rf $(CURDIR)/debian/libapache2-modxslt/usr/{bin,include,man}
$(CURDIR)/debian/libapache2-modxslt/usr/lib/lib*
+ rm -rf $(CURDIR)/debian/libapache2-modxslt/usr/{bin,include,share/man}
$(CURDIR)/debian/libapache2-modxslt/usr/lib/lib*
dh_install --sourcedir=debian/tmp
signature.asc
Description: Digital signature
Processed: Re: libapache2-modxslt: conflicts with modxslt-tools
Processing commands for [EMAIL PROTECTED]: > tags 391404 + patch Bug#391404: libapache2-modxslt: conflicts with modxslt-tools There were no tags set. Tags added: patch > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#223774: marked as done (amavis-ng: amavis-ng breaks mail delivery)
Your message dated Sat, 30 Dec 2006 13:45:13 +0100 with message-id <[EMAIL PROTECTED]> and subject line amavis-ng removed has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) --- Begin Message --- Package: amavis-ng Version: 0.1.6.6-1 Severity: serious Hi! I use amavis-ng, postfix and the virus scanners f-prot, clamscan and antivir processing mails during delivery. Since the update to amavis-ng 0.1.6.6.-1 yesterday I have received numerous error messages, and all the messages have been frozen. amavis-ng receives the mails postfix sends and the virus scanners go through the mails. However, The delivery back to postfix fails. ,[ amavis-ng log level 5 ] | Dec 12 10:37:18 mittelerde amavis[30745]: ***WARN*** Use of uninitialized value in concatenation (.) or string at /usr/share/perl5/AMAVIS/MTA/SMTP.pm line 516, line 3. | Dec 12 10:37:24 mittelerde amavis[30745]: AMAVIS: Error while accepting message | Dec 12 10:37:24 mittelerde amavis[30745]: AMAVIS::MTA::SMTP: Freezing message ` Postfix's "mailq" says: , | BE619138788 Fri Dec 12 11:02:42 [EMAIL PROTECTED] | (lost connection with 127.0.0.1[127.0.0.1] while sending end of data -- message may be sent more than once) | [EMAIL PROTECTED] ` -- System Information: Debian Release: testing/unstable Architecture: i386 Kernel: Linux mittelerde 2.4.23 #1 Sun Nov 30 15:01:54 CET 2003 i686 Locale: LANG=de_DE, [EMAIL PROTECTED] Versions of packages amavis-ng depends on: ii debconf 1.3.22 Debian configuration management sy ii libconfig-inifiles-perl 2.38-2 A module for reading .ini-style co ii libfile-mmagic-perl 1.20-1 Perl module to guess file type ii libmime-perl 5.411-2Perl5 modules for MIME-compliant m ii logrotate 3.6.5-2Log rotation utility ii perl [libmime-base64-perl]5.8.2-2Larry Wall's Practical Extraction ii perl-modules [libnet-perl]5.8.2-2Core Perl modules. ii perl-suid 5.8.2-2Runs setuid Perl scripts. -- debconf information: amavis-ng/filename-changes: --- End Message --- --- Begin Message --- amavis-ng has been removed because it's no longer maintained upstream. Please switch to amavis-new. amavis-ng and amavis-new diverged a long time ago so I'm closing your bug in the blief that it doesn't apply to amavis-new. If you can find the bug in amavis-new too, please file a new bug report. -- Martin Michlmayr http://www.cyrius.com/ --- End Message ---
Bug#203598: marked as done (amavis-ng: Problem messages remain in queue in addition to being saved)
Your message dated Sat, 30 Dec 2006 13:45:13 +0100
with message-id <[EMAIL PROTECTED]>
and subject line amavis-ng removed
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: amavis-ng
Version: 0.1.6.4-3
Severity: normal
Tags: patch
I am using amavis-ng in SMTP daemon mode with postfix. I have set it up
with a timeout value so amavis-ng doesn't get tell postfix that it has
it until it is done processing. The problem is if a message has a
problem being re-injected it drops the connection with the first side.
As it should a copy is saved the to problem directory. However the
message also remains in the queue. The next time the queue is processed
the message will be tried again. However as their is a problem with the
message it will again be copied to the problems directory and again left
in the queue. Obviously as the message is always going to fail it should
not be left in the queue to fail again. A single notification to the
administrator should be enough. What should be done IMO is once the
message has a problem it should be dropped from the queue and have a
copy saved as a message is that is quaratinied. This way a single copy
is saved that the administrator can deal with an re-inject as
neccessary, and the system does not continue to try to deliver the same
message over and over having it fail everytime. Adding a single line to
the SMTP.pm file allows this to happen. I'm not sure of the exact line
number but it is around 400-410 (at least on the version on my system).
The necessary line is shown below.
# First try to put the message into the problems directory.
if (AMAVIS->quarantine_problem_message($args)) {
+ $self->drop_message($args);
return 1;
}
# If that fails, reject the message
-- System Information
Debian Release: 3.0
Architecture: i386
Kernel: Linux P133 2.4.18-1-586tsc #1 Fri Jun 6 21:58:41 EST 2003 i586
Locale: LANG=C, LC_CTYPE=C
Versions of packages amavis-ng depends on:
ii arj 3.10g-1 Archiver for .arj files
ii bzip21.0.2-1 A high-quality block-sorting file
ii debconf 1.0.32 Debian configuration management sy
ii libarchive-tar-perl 0.22-2 module for manipulation of tar arc
ii libarchive-zip-perl 0.11-1 Module for manipulation of ZIP arc
ii libcompress-zlib-perl1.16-1 Perl module for creation and manip
ii libconfig-inifiles-perl 2.27-1 A module for reading .ini-style co
ii libconvert-tnef-perl 0.16-2 Perl module to read TNEF files
ii libconvert-uulib-perl0.201-2 Perl interface to the uulib librar
ii libfile-mmagic-perl 1.15-2 Perl module to guess file type.
ii libmime-base64-perl 2.12-4 MIME/Base64 decoding for Perl
ii libmime-perl 5.411-1 Perl5 modules for MIME-compliant m
ii libnet-perl 1:1.09.01-1 Implementation of Internet protoco
ii logrotate3.5.9-8 Log rotation utility
ii nomarch 1.3-1 Unpacks .ARC and .ARK MS-DOS archi
ii perl 5.6.1-8.2 Larry Wall's Practical Extraction
ii perl-suid5.6.1-8.2 Runs setuid Perl scripts.
ii suidmanager 0.52Manage File Permissions
ii unzoo4.4-2 zoo archive extractor
--- End Message ---
--- Begin Message ---
amavis-ng has been removed because it's no longer maintained upstream.
Please switch to amavis-new.
amavis-ng and amavis-new diverged a long time ago so I'm closing your
bug in the blief that it doesn't apply to amavis-new. If you can find
the bug in amavis-new too, please file a new bug report.
--
Martin Michlmayr
http://www.cyrius.com/
--- End Message ---
Bug#295415: marked as done (amavis-ng: Fails to start with perl errors)
Your message dated Sat, 30 Dec 2006 13:45:13 +0100 with message-id <[EMAIL PROTECTED]> and subject line amavis-ng removed has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) --- Begin Message --- Subject: amavis-ng: Fails to start with perl errors Package: amavis-ng Version: 0.1.6.9-1 Severity: critical Justification: breaks unrelated software After an upgrade, amavis started spewing a lot of emergency errors and stoped working (bringing down all mail delivery with it). I use the Courier module and it started complaining about two things: Feb 15 15:05:21 mime amavis[32018]: ***EMERG*** AMAVIS::MTA::Courier does not define $AMAVIS::MTA::Courier::VERSION--version check failed at (eval 5) line 1, line 520. Feb 15 15:05:21 mime amavis[32018]: ***EMERG*** AMAVIS::MTA::Courier does not define $AMAVIS::MTA::Courier::VERSION--version check failed at (eval 5) line 1, line 520. Feb 15 15:05:21 mime amavis[32018]: ***EMERG*** BEGIN failed--compilation aborted at (eval 5) line 1, line 520. Feb 15 15:17:22 mime amavis[25189]: ***EMERG*** Global symbol "$directory" requires explicit package name at /usr/share/perl5/AMAVIS/MTA/Courier.pm line 111, line 520. Feb 15 15:17:22 mime amavis[25189]: ***EMERG*** Compilation failed in require at (eval 4) line 1, line 520. Feb 15 15:17:22 mime amavis[25189]: ***EMERG*** Global symbol "$directory" requires explicit package name at /usr/share/perl5/AMAVIS/MTA/Courier.pm line 111, line 520. Feb 15 15:17:22 mime amavis[25189]: ***EMERG*** Compilation failed in require at (eval 4) line 1, line 520. Feb 15 15:17:22 mime amavis[25189]: ***EMERG*** BEGIN failed--compilation aborted at (eval 4) line 1, line 520. Feb 15 15:17:22 mime amavis[25189]: AMAVIS: Couldn't load AMAVIS::MTA::Courier These errors, of course, repeated a lot. I imagine this is something specifically wrong with the Courier module. Cheers -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.7 Locale: LANG=C, LC_CTYPE=pt_BR (charmap=ISO-8859-1) Versions of packages amavis-ng depends on: ii debconf 1.4.45 Debian configuration management sy ii libconfig-inifiles-perl 2.38-3 Read .ini-style configuration file ii libfile-mmagic-perl 1.22-1 Perl module to guess file type ii libmime-perl 5.417-1Perl5 modules for MIME-compliant m ii logrotate 3.7-2 Log rotation utility ii perl [libmime-base64-perl]5.8.4-6Larry Wall's Practical Extraction ii perl-modules [libnet-perl]5.8.4-6Core Perl modules ii perl-suid 5.8.4-6Runs setuid Perl scripts -- debconf information: amavis-ng/filename-changes: --- End Message --- --- Begin Message --- amavis-ng has been removed because it's no longer maintained upstream. Please switch to amavis-new. amavis-ng and amavis-new diverged a long time ago so I'm closing your bug in the blief that it doesn't apply to amavis-new. If you can find the bug in amavis-new too, please file a new bug report. -- Martin Michlmayr http://www.cyrius.com/ --- End Message ---
Bug#404897: pcscd: infinite loop when trying to start the daemon
Le 29.12.2006, à 01:29:21, Martin Waitz a écrit: > hoi :) Hello, > The pcscd postinst tried to start the daemon but it failed: > > Starting PCSC Lite resource manager: pcscdStatus of PCSC Lite resource > manager: pcscd not running already running. > Stopping PCSC Lite resource manager: pcscd. > failed! > Starting PCSC Lite resource manager: pcscdStatus of PCSC Lite resource > manager: pcscd not running failed! > already running. > Stopping PCSC Lite resource manager: pcscd. > Starting PCSC Lite resource manager: pcscdStatus of PCSC Lite resource > manager: pcscd not running already running failed! > . > Stopping PCSC Lite resource manager: pcscd. > Starting PCSC Lite resource manager: pcscdStatus of PCSC Lite resource > manager: pcscd not running failed! > already running. > Stopping PCSC Lite resource manager: pcscd. > Starting PCSC Lite resource manager: pcscd already running. > Stopping PCSC Lite resource manager: pcscdStatus of PCSC Lite resource > manager: pcscd not running failed! > . > Starting PCSC Lite resource manager: pcscdStatus of PCSC Lite resource > manager: pcscd not running failed! > already running. > Stopping PCSC Lite resource manager: pcscd. > Starting PCSC Lite resource manager: pcscdStatus of PCSC Lite resource > manager: pcscd not running already running. > Stopping PCSC Lite resource manager: pcscd failed! > . Your logs are strange. Can you send me the /etc/init.d/pcscd file you are using? > It looks very fragile to use restart in the start function and the start > function in restart. Yes. But this should have been solved with bug #392357 I will try to improve the init script post etch. Regards -- Dr. Ludovic Rousseau[EMAIL PROTECTED] -- Normaliser Unix c'est comme pasteuriser le camembert, L.R. --
Bug#403426: kernel corrupts LUKS partition header on arm
* Clemens Fruhwirth <[EMAIL PROTECTED]> [2006-12-30 11:50]: > > Is there anything else I should try? > > foobar:~# cryptsetup luksOpen /dev/sda5 x > > Enter LUKS passphrase: > > device-mapper: table: 254:0: crypt: Device lookup failed Strange. I haven't changed cryptsetup but now I don't get this message anymore. I simply get: foobar:~# cryptsetup luksOpen /dev/sdb2 x Enter LUKS passphrase: Enter LUKS passphrase: Enter LUKS passphrase: Command failed: No key available with this passphrase. But I'm sure I've typed the passphrase correctly, and it works on my x86 box (on which I created the LUKS partition). > dmsetup create mappingname dm-table-file > > If that does not work, we are seeing a dm-crypt layer problem here. This works: foobar:~# cat map 0 1954808 crypt aes-cbc-essiv:sha256 a0671e89e060742caf3f9a3e7d762b24 0 /dev/sdb2 1032 foobar:~# dmsetup create x map foobar:~# mount /dev/mapper/x /mnt foobar:~# ls -l /mnt total 20 drwx-- 2 root root 16384 Dec 30 2006 lost+found -rw-r--r-- 1 root root 5 Dec 30 2006 x foobar:~# -- Martin Michlmayr http://www.cyrius.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: tagging 403980
Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.9.27 > tags 403980 + experimental Bug#403980: gcc-snapshot_20061217-1(sparc/experimental): FTBFS due to missing stubs-64.h There were no tags set. Tags added: experimental > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#385841: marked as done (package build-depends on g++-3.4, which is not available on hppa)
Your message dated Sat, 30 Dec 2006 13:17:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#385841: fixed in wordtrans 1.1pre14-4 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) --- Begin Message --- Package: wordtrans Version: 1.1pre14-2 Severity: serious the package build-depends on g++-3.4 or g++-4.0, which is not available on hppa. Please build using g++-4.1. If the package cannot be built using g++-4.1, please make sure that a bug report is filed against the g++-4.1 package. Is 3.4 really needed on arm and m68k? --- End Message --- --- Begin Message --- Source: wordtrans Source-Version: 1.1pre14-4 We believe that the bug you reported is fixed in the latest version of wordtrans, which is due to be installed in the Debian FTP archive: wordtrans-data_1.1pre14-4_all.deb to pool/main/w/wordtrans/wordtrans-data_1.1pre14-4_all.deb wordtrans-dict_1.1pre14-4_all.deb to pool/main/w/wordtrans/wordtrans-dict_1.1pre14-4_all.deb wordtrans-doc_1.1pre14-4_all.deb to pool/main/w/wordtrans/wordtrans-doc_1.1pre14-4_all.deb wordtrans-kde_1.1pre14-4_i386.deb to pool/main/w/wordtrans/wordtrans-kde_1.1pre14-4_i386.deb wordtrans-qt_1.1pre14-4_i386.deb to pool/main/w/wordtrans/wordtrans-qt_1.1pre14-4_i386.deb wordtrans-web_1.1pre14-4_all.deb to pool/main/w/wordtrans/wordtrans-web_1.1pre14-4_all.deb wordtrans_1.1pre14-4.diff.gz to pool/main/w/wordtrans/wordtrans_1.1pre14-4.diff.gz wordtrans_1.1pre14-4.dsc to pool/main/w/wordtrans/wordtrans_1.1pre14-4.dsc A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Javier Fernandez-Sanguino Pen~a <[EMAIL PROTECTED]> (supplier of updated wordtrans package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sat, 30 Dec 2006 14:04:21 +0100 Source: wordtrans Binary: wordtrans-dict wordtrans-doc wordtrans-data wordtrans-qt wordtrans-kde wordtrans-web Architecture: source all i386 Version: 1.1pre14-4 Distribution: unstable Urgency: low Maintainer: Javier Fernandez-Sanguino Pen~a <[EMAIL PROTECTED]> Changed-By: Javier Fernandez-Sanguino Pen~a <[EMAIL PROTECTED]> Description: wordtrans-data - Multi Language Word Translator for Linux wordtrans-dict - Multi Language Word Translator for Linux wordtrans-doc - Multi Language Word Translator for Linux wordtrans-kde - Multi Language Word Translator for Linux wordtrans-qt - Multi Language Word Translator for Linux wordtrans-web - Multi Language Word Translator for Linux Closes: 385841 Changes: wordtrans (1.1pre14-4) unstable; urgency=low . * Acknowledge NMU fix which I missed in my previous upload (Closes: #385841) Files: d385f2e9c606b13df6c67ee28faf3c83 983 text optional wordtrans_1.1pre14-4.dsc 918477c3e1bd3888c78ead77c96f8dc2 118782 text optional wordtrans_1.1pre14-4.diff.gz 5a89c7a1e82bb00358b37424d051a970 126158 text optional wordtrans-data_1.1pre14-4_all.deb d06dadae8a70451fa575b50a3b8f7cc8 173484 doc optional wordtrans-doc_1.1pre14-4_all.deb 0dcfaf47a283894dbdd796ab930dfccc 38528 text optional wordtrans-web_1.1pre14-4_all.deb b21cbca9591d084df1d28cf8d3961bea 21700 text optional wordtrans-dict_1.1pre14-4_all.deb 542f47edd81ebd6a15b6afe567ec9d9a 278242 text optional wordtrans-qt_1.1pre14-4_i386.deb 64cfb0e0796485b206b9643e985d3c89 242120 text optional wordtrans-kde_1.1pre14-4_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iQCVAwUBRZZk0/tEPvakNq0lAQIjhAP+OE34JLVHnC1veiQeuhswkquspTmZAfl5 i3mWZSiXk4j4HmBpYOPOexvuB/K5o9+y6LO9ernd73sJhDzxDBgXks2Xz4WBeeYt 8yUnLvGlBISMCvbrun2M7gctxDE2wzyF0ObVir8pf1lrHsP1G+1u9aTiWF/SA3HR ekEHXJmmwCA= =yFjc -END PGP SIGNATURE- --- End Message ---
Bug#405025: /etc/init.d/pcscd is a fork bomb
Package: pcscd Version: 1.3.2-4 Severity: critical "/etc/init.d/pcscd start" (which is run on upgrades) starts an infinite number of copies of itself. Load was over 500 before I was able to kill the scripts. The terminal was flooded with messages like: Starting PCSC Lite resource manager: pcscdStatus of PCSC Lite resource manager: pcscd not running already running. failed! Stopping PCSC Lite resource manager: pcscd. Starting PCSC Lite resource manager: pcscd already runningStatus of PCSC Lite resource manager: pcscd not running. failed! Stopping PCSC Lite resource manager: pcscd. Starting PCSC Lite resource manager: pcscd already runningStatus of PCSC Lite resource manager: pcscd not running. failed! Stopping PCSC Lite resource manager: pcscd. -- System Information: Debian Release: 4.0 APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/dash Kernel: Linux 2.6.18.1 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) Versions of packages pcscd depends on: ii libc62.3.6.ds1-9 GNU C Library: Shared libraries ii libccid [pcsc-ifd-handler] 1.1.0-1 PC/SC driver for USB CCID smart ca ii libusb-0.1-4 2:0.1.12-2 userspace USB programming library ii lsb-base 3.1-22 Linux Standard Base 3.1 init scrip pcscd recommends no packages. -- no debconf information -- ciao, Marco signature.asc Description: Digital signature
Bug#380396: using update-fonts-dir --x11r7-layout in maintainer scripts breaks partial upgrades
Hi,
while looking at #380396, I noted the breakage is actually in an
unfortunate combination of update-fonts-dir (in xfonts-utils)
requiring the --x11r7-layout option and debhelper unconditionally
putting it in generated postinst/postrm files (dh_installxfonts).
Adding ${misc:Depends} adds the (previously missing) dependency on
xfonts-utils, but does not make it versioned.
postinst:
# Automatically added by dh_installxfonts
if which update-fonts-dir >/dev/null 2>&1; then
update-fonts-dir --x11r7-layout misc;update-fonts-alias misc
fi
# End automatically added section
postrm:
# Automatically added by dh_installxfonts
if [ -x "`which update-fonts-dir 2>/dev/null`" ]; then
update-fonts-dir --x11r7-layout misc;update-fonts-alias misc
fi
# End automatically added section
I believe the fix is to make --x11r7-layout the default (#363005) and
at the same time revert the debhelper change (#362820). All xfonts
using debhelper would then need (bin?)nmus to get maintainer scripts
without --x11r7-layout.
Christoph
--
[EMAIL PROTECTED] | http://www.df7cb.de/
signature.asc
Description: Digital signature
Bug#366365: libcvsservice0 should only recommend cvs (not depend)
Package: libcvsservice0 Version: 4:3.5.5-3 Followup-For: Bug #366365 libcvsservice0 is depended upon by many packages which link it in, even though cvs functionality is not needed nor wanted. quanta is one such package. Because libcvsservice0 depends on cvs, it must be installed as wel. But cvs is not actually used by libcvsservice0 until it is needed, and it will function perfectly (doing nothing) without it. In fact Quanta did complain during startup, but only it because cervesia wasn't installed (again, I don't need it), not because cvs wasn't. The situation where a library is depended upon which itself recommand the package it actually use happen many times within debian, and so can be relied upon to be accepted by all. One example is Kerberos, an other is mysql. Both have runtimes libs which are often installed because of some dependancy even though neither kerberos nor mysql is installed. please change dependancy for cvs to recommand instead of depend. thank you. -- System Information: Debian Release: 4.0 APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.19.1vmware Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Versions of packages libcvsservice0 depends on: ii cvs1:1.12.13-5 Concurrent Versions System ii kdelibs4c2a4:3.5.5a.dfsg.1-5 core libraries and binaries for al ii libc6 2.3.6.ds1-8 GNU C Library: Shared libraries ii libgcc11:4.1.1-19GCC support library ii libstdc++6 4.1.1-19 The GNU Standard C++ Library v3 libcvsservice0 recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#404876: Output of gst-launch
On Dec 30, 2006, at 2:23 AM, Yavor Doganov wrote: On Fri, Dec 29, 2006 at 02:45:14PM -0800, David Schleef wrote: Could you run: rm ~/.gstreamer-0.10/registry.*.xml GST_DEBUG=*:3 gst-launch --gst-debug-no-color and attach the output? Attached is the output produced on my machine running unstable. Interesting. I'm not getting the mail from David Schleef, but I am getting the replies from Yavor Doganov. David, would you like me to try the same things on my Beige G3 under Etch? Rick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: notfound 366365 in 4:3.5.5-3
Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.9.27 > notfound 366365 4:3.5.5-3 Bug#366365: cervisia: should depend on libcvsservice0 Bug marked as not found in version 4:3.5.5-3. (By the way, this Bug is currently marked as done.) > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#366365: Oops
Sorry for confusing extra info to this bug. it was ment as a new minor bug, not as an appending to this grave bug. Please ignore. Ernest ter Kuile. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#402750: marked as done (genisoimage: missing mkzftree binary)
Your message dated Sat, 30 Dec 2006 16:17:02 + with message-id <[EMAIL PROTECTED]> and subject line Bug#402750: fixed in cdrkit 9:1.1.1-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) --- Begin Message --- Package: genisoimage Version: 9:1.1.0-1 Severity: important Tags: patch Once again, genisoimage package is missing the mkzftree binary (last time it was in the mkisofs package, see #387927). The attached patch fixes the issue. I didn't set this bug severity to RC because I was not sure, but I think it's important to get it fixed for etch. Aurel --- genisoimage.install.orig 2006-12-12 13:54:27.0 +0100 +++ genisoimage.install 2006-12-12 13:50:38.0 +0100 @@ -4,6 +4,7 @@ debian/tmp/usr/bin/isodump debian/tmp/usr/bin/isovfy debian/tmp/usr/bin/dirsplit +debian/tmp/usr/bin/mkzftree debian/tmp/usr/share/man/man8/genisoimage.8 debian/tmp/usr/share/man/man8/isoinfo.8 debian/tmp/usr/share/man/man1/dirsplit.1 --- End Message --- --- Begin Message --- Source: cdrkit Source-Version: 9:1.1.1-1 We believe that the bug you reported is fixed in the latest version of cdrkit, which is due to be installed in the Debian FTP archive: cdda2wav_1.1.1-1_all.deb to pool/main/c/cdrkit/cdda2wav_1.1.1-1_all.deb cdrecord_1.1.1-1_all.deb to pool/main/c/cdrkit/cdrecord_1.1.1-1_all.deb cdrkit-doc_1.1.1-1_all.deb to pool/main/c/cdrkit/cdrkit-doc_1.1.1-1_all.deb cdrkit_1.1.1-1.diff.gz to pool/main/c/cdrkit/cdrkit_1.1.1-1.diff.gz cdrkit_1.1.1-1.dsc to pool/main/c/cdrkit/cdrkit_1.1.1-1.dsc cdrkit_1.1.1.orig.tar.gz to pool/main/c/cdrkit/cdrkit_1.1.1.orig.tar.gz genisoimage_1.1.1-1_i386.deb to pool/main/c/cdrkit/genisoimage_1.1.1-1_i386.deb icedax_1.1.1-1_i386.deb to pool/main/c/cdrkit/icedax_1.1.1-1_i386.deb mkisofs_1.1.1-1_all.deb to pool/main/c/cdrkit/mkisofs_1.1.1-1_all.deb wodim_1.1.1-1_i386.deb to pool/main/c/cdrkit/wodim_1.1.1-1_i386.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Eduard Bloch <[EMAIL PROTECTED]> (supplier of updated cdrkit package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sat, 30 Dec 2006 16:45:31 +0100 Source: cdrkit Binary: cdda2wav mkisofs cdrkit-doc genisoimage cdrecord wodim icedax Architecture: source all i386 Version: 9:1.1.1-1 Distribution: unstable Urgency: medium Maintainer: Joerg Jaspert <[EMAIL PROTECTED]> Changed-By: Eduard Bloch <[EMAIL PROTECTED]> Description: cdda2wav - Dummy transition package for icedax cdrecord - Dummy transition package for wodim cdrkit-doc - Documentation for the cdrkit package-suite genisoimage - Creates ISO-9660 CD-ROM filesystem images icedax - Creates WAV files from audio CDs mkisofs- Dummy transition package for genisoimage wodim - command line CD/DVD writing tool Closes: 369677 377069 401791 401821 402044 402190 402750 403193 403536 403899 404289 404986 Changes: cdrkit (9:1.1.1-1) unstable; urgency=medium . * New upstream version + more verbose abort message if track is specified with some maintainance command (closes: #369677) + BURN-Free enabled by default (closes: #403899) + uses correct CFLAGS variable (closes: #402190) + moved *iso* manpages to section 1, many manpage fixes (closes: #404289, #402044) + icedax.1 updates, cdda2wav specific expalanations removed (closes: #401821) + getting maximum DMA transfer size from sysfs (closes: #377069) + coexisting hppa/alpha boot code possible now (closes: #404986) * Add mkzftree binary again (sorry... closes: #402750) * Add /usr/bin/readcd -> readom compatibility symlink (closes: #403536, #403193) and set conflict with older xcdroast package revisions (closes: #401791) Files: 1d50cf284a3e1c7fab6f9831a18e28bb 862 otherosfs optional cdrkit_1.1.1-1.dsc 937f87c13ce268522c14daa9ba8fdbf0 1404826 otherosfs optional cdrkit_1.1.1.orig.tar.gz a50228a40678392f75bb3985c60bb82c 24845 otherosfs optional cdrkit_1.1.1-1.diff.gz 1a456943ce64d434e26af89dcfa213ae 157606 doc optional cdrkit-doc_1.1.1-1_all.deb df4277c2147b637a347f86472b3d5d14 1162 otherosfs opti
Bug#401791: marked as done (wodim must conflict with xcdroast (<< 0.98+0alpha15-11))
Your message dated Sat, 30 Dec 2006 16:17:02 + with message-id <[EMAIL PROTECTED]> and subject line Bug#401791: fixed in cdrkit 9:1.1.1-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) --- Begin Message --- Package: wodim, xcdroast Severity: serious <-- snip --> $ xcdroast ** (xcdroast:8852): WARNING **: No /usr/bin/readcd installed ** (xcdroast:8852): WARNING **: (Invalid lib-directory? Check -l option) $ <-- snip --> If this was intended: - xcdroast and other packages depending on it have to be fixed and - wodim has to conflict with unfixed versions of these packages. --- End Message --- --- Begin Message --- Source: cdrkit Source-Version: 9:1.1.1-1 We believe that the bug you reported is fixed in the latest version of cdrkit, which is due to be installed in the Debian FTP archive: cdda2wav_1.1.1-1_all.deb to pool/main/c/cdrkit/cdda2wav_1.1.1-1_all.deb cdrecord_1.1.1-1_all.deb to pool/main/c/cdrkit/cdrecord_1.1.1-1_all.deb cdrkit-doc_1.1.1-1_all.deb to pool/main/c/cdrkit/cdrkit-doc_1.1.1-1_all.deb cdrkit_1.1.1-1.diff.gz to pool/main/c/cdrkit/cdrkit_1.1.1-1.diff.gz cdrkit_1.1.1-1.dsc to pool/main/c/cdrkit/cdrkit_1.1.1-1.dsc cdrkit_1.1.1.orig.tar.gz to pool/main/c/cdrkit/cdrkit_1.1.1.orig.tar.gz genisoimage_1.1.1-1_i386.deb to pool/main/c/cdrkit/genisoimage_1.1.1-1_i386.deb icedax_1.1.1-1_i386.deb to pool/main/c/cdrkit/icedax_1.1.1-1_i386.deb mkisofs_1.1.1-1_all.deb to pool/main/c/cdrkit/mkisofs_1.1.1-1_all.deb wodim_1.1.1-1_i386.deb to pool/main/c/cdrkit/wodim_1.1.1-1_i386.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Eduard Bloch <[EMAIL PROTECTED]> (supplier of updated cdrkit package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sat, 30 Dec 2006 16:45:31 +0100 Source: cdrkit Binary: cdda2wav mkisofs cdrkit-doc genisoimage cdrecord wodim icedax Architecture: source all i386 Version: 9:1.1.1-1 Distribution: unstable Urgency: medium Maintainer: Joerg Jaspert <[EMAIL PROTECTED]> Changed-By: Eduard Bloch <[EMAIL PROTECTED]> Description: cdda2wav - Dummy transition package for icedax cdrecord - Dummy transition package for wodim cdrkit-doc - Documentation for the cdrkit package-suite genisoimage - Creates ISO-9660 CD-ROM filesystem images icedax - Creates WAV files from audio CDs mkisofs- Dummy transition package for genisoimage wodim - command line CD/DVD writing tool Closes: 369677 377069 401791 401821 402044 402190 402750 403193 403536 403899 404289 404986 Changes: cdrkit (9:1.1.1-1) unstable; urgency=medium . * New upstream version + more verbose abort message if track is specified with some maintainance command (closes: #369677) + BURN-Free enabled by default (closes: #403899) + uses correct CFLAGS variable (closes: #402190) + moved *iso* manpages to section 1, many manpage fixes (closes: #404289, #402044) + icedax.1 updates, cdda2wav specific expalanations removed (closes: #401821) + getting maximum DMA transfer size from sysfs (closes: #377069) + coexisting hppa/alpha boot code possible now (closes: #404986) * Add mkzftree binary again (sorry... closes: #402750) * Add /usr/bin/readcd -> readom compatibility symlink (closes: #403536, #403193) and set conflict with older xcdroast package revisions (closes: #401791) Files: 1d50cf284a3e1c7fab6f9831a18e28bb 862 otherosfs optional cdrkit_1.1.1-1.dsc 937f87c13ce268522c14daa9ba8fdbf0 1404826 otherosfs optional cdrkit_1.1.1.orig.tar.gz a50228a40678392f75bb3985c60bb82c 24845 otherosfs optional cdrkit_1.1.1-1.diff.gz 1a456943ce64d434e26af89dcfa213ae 157606 doc optional cdrkit-doc_1.1.1-1_all.deb df4277c2147b637a347f86472b3d5d14 1162 otherosfs optional cdrecord_1.1.1-1_all.deb 2d8335e7a13dabd1b2da13369b1b8989 842 sound optional cdda2wav_1.1.1-1_all.deb bdae976e37253c270620186a5c486bc4 886 otherosfs optional mkisofs_1.1.1-1_all.deb d1900d8460ae53e749ef9d6a6504c37f 417334 otherosfs optional wodim_1.1.1-1_i386.deb a7e3ea5165a68d1af7dd621e51acf1f1 171176 sound optional icedax_1.1.1-1_
Bug#404888: glib destabilization and ways forward
Le vendredi 29 décembre 2006 à 10:48 -0800, Thomas Bushnell BSG a écrit : > Despite what Josselin has said, I can see no indication from a brief > perusal of the upstream branch sources in trac that upstream gnucash > either no longer uses these key files or has changed away from the keys > with embedded spaces. Then they must stop using GKeyFile. There is no way that they will get this supported by GLib developers. > 1) Decide that glib should not migrate into testing (it is a freeze, > after all); if there are particular fixes of RC issues in more recent > versions, then those fixes should be added, but otherwise the wholesale > importation of many changes should not be permitted. That leaves us with the silent data loss that can happen when using broken key names (like, well, gnucash does). Whether this is or not a RC issue, I'll let the release team decide. > 2) Decide that glib can migrate into testing, with the particular change > of checking key values reverted to its pre-2.12.5 behavior, since this > is a destabilizing change in the Debian context. Same answer. At least we can get the other bug fixes. > 3) Decide that glib can migrate into testing with the destabilizing > change intact, migrate an upstream gnucash fix into testing at the same > time. This is the sanest solution because this is the one that gets us with the lesser number of bugs. -- .''`. : :' : We are debian.org. Lower your prices, surrender your code. `. `' We will add your hardware and software distinctiveness to `-our own. Resistance is futile. signature.asc Description: Ceci est une partie de message numériquement signée
Bug#404235: segfault patch for 404235
Hi Nico,
On Fri, Dec 29, 2006 at 07:08:29PM +0100, Nico Golde wrote:
> I attached 2 patches for trr_update and trr_format which
> should fix this.
> Please test them before you upload the changes since I don't
> use emacs and have no idea of the program.
thanks for the patch.
> +++ trr_format.c 2006-12-29 18:27:26.0 +0100
> main(int argc, char **argv){
> - char textfile[256], formattedfile[256], lockfile[256], *tmpfname;
> - char command[256], line[1024];
> + char textfile[_POSIX_PATH_MAX], formattedfile[_POSIX_PATH_MAX],
> lockfile[_POSIX_PATH_MAX], *tmpfname;
> + char command[_POSIX_PATH_MAX], line[_POSIX_PATH_MAX];
Please note that this will probably not work with the Hurd. This system
tries to avoid all useless limitations and _POSIX_PATH_MAX is one of
these. The proper solution is to create the buffers dynamically ...
Jens
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#404235: segfault patch for 404235
Hey,
* Jens Seidel <[EMAIL PROTECTED]> [2006-12-30 18:19]:
> On Fri, Dec 29, 2006 at 07:08:29PM +0100, Nico Golde wrote:
> > +++ trr_format.c2006-12-29 18:27:26.0 +0100
> > main(int argc, char **argv){
> > - char textfile[256], formattedfile[256], lockfile[256], *tmpfname;
> > - char command[256], line[1024];
> > + char textfile[_POSIX_PATH_MAX], formattedfile[_POSIX_PATH_MAX],
> > lockfile[_POSIX_PATH_MAX], *tmpfname;
> > + char command[_POSIX_PATH_MAX], line[_POSIX_PATH_MAX];
>
> Please note that this will probably not work with the Hurd. This system
> tries to avoid all useless limitations and _POSIX_PATH_MAX is one of
> these. The proper solution is to create the buffers dynamically ...
Yes that would be better then I didnt do this cause the code
doesnt really need dinamically allocated buffers. Anyway the
patch should just show all the other problems that exist in
the code but I would suggest a documentation of secure
programming and a complete rewrite of the code to the
upstream author. Also the substitution of SED and GREP via
the makefile in the c-files and then calling system() is
really ugly.
Kind regards, happy new year
Nico
--
Nico Golde - http://www.ngolde.de
JAB: [EMAIL PROTECTED] - GPG: 0x73647CFF
Forget about that mouse with 3/4/5 buttons,
gimme a keyboard with 103/104/105 keys!
pgp93RaqwMg3W.pgp
Description: PGP signature
Processed: Re: Bug#405027: libwww-mechanize-ruby: missing dependency against libopenssl-ruby
Processing commands for [EMAIL PROTECTED]: > severity 405027 grave Bug#405027: libwww-mechanize-ruby: missing dependency against libopenssl-ruby Severity set to `grave' from `important' > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#404897: marked as done (pcscd: infinite loop when trying to start the daemon)
Your message dated Sat, 30 Dec 2006 18:02:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#404897: fixed in pcsc-lite 1.3.2-5 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) --- Begin Message --- Package: pcscd Version: 1.3.2-4 Severity: grave Justification: renders package unusable -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 hoi :) The pcscd postinst tried to start the daemon but it failed: Starting PCSC Lite resource manager: pcscdStatus of PCSC Lite resource manager: pcscd not running already running. Stopping PCSC Lite resource manager: pcscd. failed! Starting PCSC Lite resource manager: pcscdStatus of PCSC Lite resource manager: pcscd not running failed! already running. Stopping PCSC Lite resource manager: pcscd. Starting PCSC Lite resource manager: pcscdStatus of PCSC Lite resource manager: pcscd not running already running failed! . Stopping PCSC Lite resource manager: pcscd. Starting PCSC Lite resource manager: pcscdStatus of PCSC Lite resource manager: pcscd not running failed! already running. Stopping PCSC Lite resource manager: pcscd. Starting PCSC Lite resource manager: pcscd already running. Stopping PCSC Lite resource manager: pcscdStatus of PCSC Lite resource manager: pcscd not running failed! . Starting PCSC Lite resource manager: pcscdStatus of PCSC Lite resource manager: pcscd not running failed! already running. Stopping PCSC Lite resource manager: pcscd. Starting PCSC Lite resource manager: pcscdStatus of PCSC Lite resource manager: pcscd not running already running. Stopping PCSC Lite resource manager: pcscd failed! . ... It looks very fragile to use restart in the start function and the start function in restart. - -- System Information: Debian Release: 4.0 APT prefers proposed-updates APT policy: (500, 'proposed-updates'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/dash Kernel: Linux 2.6.18-3-686 Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Versions of packages pcscd depends on: ii libc62.3.6.ds1-9 GNU C Library: Shared libraries ii libccid [pcsc-ifd-handler] 1.1.0-1 PC/SC driver for USB CCID smart ca ii libusb-0.1-4 2:0.1.12-2 userspace USB programming library ii lsb-base 3.1-22 Linux Standard Base 3.1 init scrip pcscd recommends no packages. - -- no debconf information -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFFlGFXj/Eaxd/oD7IRAlgnAJ0Spppx3gwg5WoeLCQFsn0/VmAvLQCfRRlK QjZO0+M8eOQLdXIzcbMpWmM= =sILr -END PGP SIGNATURE- --- End Message --- --- Begin Message --- Source: pcsc-lite Source-Version: 1.3.2-5 We believe that the bug you reported is fixed in the latest version of pcsc-lite, which is due to be installed in the Debian FTP archive: libpcsclite-dev_1.3.2-5_i386.deb to pool/main/p/pcsc-lite/libpcsclite-dev_1.3.2-5_i386.deb libpcsclite1_1.3.2-5_i386.deb to pool/main/p/pcsc-lite/libpcsclite1_1.3.2-5_i386.deb pcsc-lite_1.3.2-5.diff.gz to pool/main/p/pcsc-lite/pcsc-lite_1.3.2-5.diff.gz pcsc-lite_1.3.2-5.dsc to pool/main/p/pcsc-lite/pcsc-lite_1.3.2-5.dsc pcscd_1.3.2-5_i386.deb to pool/main/p/pcsc-lite/pcscd_1.3.2-5_i386.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ludovic Rousseau <[EMAIL PROTECTED]> (supplier of updated pcsc-lite package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sat, 30 Dec 2006 18:37:45 +0100 Source: pcsc-lite Binary: libpcsclite-dev libpcsclite1 pcscd Architecture: source i386 Version: 1.3.2-5 Distribution: unstable Urgency: high Maintainer: Ludovic Rousseau <[EMAIL PROTECTED]> Changed-By: Ludovic Rousseau <[EMAIL PROTECTED]> Description: libpcsclite-dev - Middleware to access a smart card using PC/SC (development files) libpcsclite1 - Middleware to access a smart card using PC/SC (library) pcscd - Middleware to access a smart card using PC/SC (daemon side) Closes: 404897 405025 Changes: pcsc-lite (1.3.2-5) unstable; urgency=high . * debian/pcscd.init: rewrite
Bug#405025: marked as done (/etc/init.d/pcscd is a fork bomb)
Your message dated Sat, 30 Dec 2006 18:02:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#405025: fixed in pcsc-lite 1.3.2-5 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) --- Begin Message --- Package: pcscd Version: 1.3.2-4 Severity: critical "/etc/init.d/pcscd start" (which is run on upgrades) starts an infinite number of copies of itself. Load was over 500 before I was able to kill the scripts. The terminal was flooded with messages like: Starting PCSC Lite resource manager: pcscdStatus of PCSC Lite resource manager: pcscd not running already running. failed! Stopping PCSC Lite resource manager: pcscd. Starting PCSC Lite resource manager: pcscd already runningStatus of PCSC Lite resource manager: pcscd not running. failed! Stopping PCSC Lite resource manager: pcscd. Starting PCSC Lite resource manager: pcscd already runningStatus of PCSC Lite resource manager: pcscd not running. failed! Stopping PCSC Lite resource manager: pcscd. -- System Information: Debian Release: 4.0 APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/dash Kernel: Linux 2.6.18.1 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) Versions of packages pcscd depends on: ii libc62.3.6.ds1-9 GNU C Library: Shared libraries ii libccid [pcsc-ifd-handler] 1.1.0-1 PC/SC driver for USB CCID smart ca ii libusb-0.1-4 2:0.1.12-2 userspace USB programming library ii lsb-base 3.1-22 Linux Standard Base 3.1 init scrip pcscd recommends no packages. -- no debconf information -- ciao, Marco signature.asc Description: Digital signature --- End Message --- --- Begin Message --- Source: pcsc-lite Source-Version: 1.3.2-5 We believe that the bug you reported is fixed in the latest version of pcsc-lite, which is due to be installed in the Debian FTP archive: libpcsclite-dev_1.3.2-5_i386.deb to pool/main/p/pcsc-lite/libpcsclite-dev_1.3.2-5_i386.deb libpcsclite1_1.3.2-5_i386.deb to pool/main/p/pcsc-lite/libpcsclite1_1.3.2-5_i386.deb pcsc-lite_1.3.2-5.diff.gz to pool/main/p/pcsc-lite/pcsc-lite_1.3.2-5.diff.gz pcsc-lite_1.3.2-5.dsc to pool/main/p/pcsc-lite/pcsc-lite_1.3.2-5.dsc pcscd_1.3.2-5_i386.deb to pool/main/p/pcsc-lite/pcscd_1.3.2-5_i386.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ludovic Rousseau <[EMAIL PROTECTED]> (supplier of updated pcsc-lite package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sat, 30 Dec 2006 18:37:45 +0100 Source: pcsc-lite Binary: libpcsclite-dev libpcsclite1 pcscd Architecture: source i386 Version: 1.3.2-5 Distribution: unstable Urgency: high Maintainer: Ludovic Rousseau <[EMAIL PROTECTED]> Changed-By: Ludovic Rousseau <[EMAIL PROTECTED]> Description: libpcsclite-dev - Middleware to access a smart card using PC/SC (development files) libpcsclite1 - Middleware to access a smart card using PC/SC (library) pcscd - Middleware to access a smart card using PC/SC (daemon side) Closes: 404897 405025 Changes: pcsc-lite (1.3.2-5) unstable; urgency=high . * debian/pcscd.init: rewrite using /etc/init.d/skeleton as example. start rule do not call restart any more Closes: #404897 "pcscd: infinite loop when trying to start the daemon" Closes: #405025 "/etc/init.d/pcscd is a fork bomb" Files: fe054854cd167af9be7a64467431ada2 670 misc extra pcsc-lite_1.3.2-5.dsc 03aa89fb60f34d4d71ef4c3ca7573651 13238 misc extra pcsc-lite_1.3.2-5.diff.gz 845b82f787bdf6782e708342195abf9e 67176 misc extra pcscd_1.3.2-5_i386.deb 37717e1eba5f25e3f675c733d29d4811 286766 libdevel optional libpcsclite-dev_1.3.2-5_i386.deb 6ed04d870e21a0d68a73119723a1e96f 36724 libs optional libpcsclite1_1.3.2-5_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFFlqTNP0qKj+B/HPkRAtsTAJ99UqVBAbFL+hPjP4d3L0g0I5GksgCgjar2 XWm+6uxNOH44ixGlYhnr0yg= =hpJd -END PGP SIGNATURE- --- End Message ---
Bug#380396: Bug#362820: using update-fonts-dir --x11r7-layout in maintainer scripts breaks partial upgrades
Christoph Berg wrote:
> Adding ${misc:Depends} adds the (previously missing) dependency on
> xfonts-utils, but does not make it versioned.
Why does it need to be versioned? There has not been any version of
xfonts-utils that did not support --x11r7-layout.
--
see shy jo
signature.asc
Description: Digital signature
Bug#380396: using update-fonts-dir --x11r7-layout in maintainer scripts breaks partial upgrades
* Christoph Berg ([EMAIL PROTECTED]) [061230 06:15]:
> while looking at #380396, I noted the breakage is actually in an
> unfortunate combination of update-fonts-dir (in xfonts-utils)
> requiring the --x11r7-layout option and debhelper unconditionally
> putting it in generated postinst/postrm files (dh_installxfonts).
>
> Adding ${misc:Depends} adds the (previously missing) dependency on
> xfonts-utils, but does not make it versioned.
As xfonts-utils doesn't exist in sarge, this is no longer RC-buggy then.
> I believe the fix is to make --x11r7-layout the default (#363005) and
I agree on this.
> at the same time revert the debhelper change (#362820). All xfonts
> using debhelper would then need (bin?)nmus to get maintainer scripts
> without --x11r7-layout.
I don't think we're at the right moment now to revert the debhelper
change - otherwise, we need to insert a versioned dependency on the new
xfonts-utils for the reverted debhelper script.
Cheers,
Andi
--
http://home.arcor.de/andreas-barth/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#404888: glib destabilization and ways forward
Josselin Mouette <[EMAIL PROTECTED]> writes:
> Le vendredi 29 décembre 2006 à 10:48 -0800, Thomas Bushnell BSG a écrit :
>> 1) Decide that glib should not migrate into testing (it is a freeze,
>> after all); if there are particular fixes of RC issues in more recent
>> versions, then those fixes should be added, but otherwise the wholesale
>> importation of many changes should not be permitted.
> That leaves us with the silent data loss that can happen when using
> broken key names (like, well, gnucash does). Whether this is or not a RC
> issue, I'll let the release team decide.
It is no regression over the prior situation and was never reported in
the BTS, even though GKeyFile was "broken" (ie too liberal when taking
input from application) in this way for some time.
>> 3) Decide that glib can migrate into testing with the destabilizing
>> change intact, migrate an upstream gnucash fix into testing at the same
>> time.
> This is the sanest solution because this is the one that gets us with
> the lesser number of bugs.
We don't know which other applications may rely on gkeyfile without
input checking. I don't want to find out at this point of the release
cycle, so this is not an option.
>> 2) Decide that glib can migrate into testing, with the particular change
>> of checking key values reverted to its pre-2.12.5 behavior, since this
>> is a destabilizing change in the Debian context.
> Same answer. At least we can get the other bug fixes.
I would prefer to leave the new input validation routines in place, but
replace all current "return FAIL" in the new g_key_file_is_group_name
and g_key_file_is_key_name function with g_warning("'%s' is not a valid
GKeyFile key/group name", bla) and only do a return FAIL if the old
condition (string is empty) was met. Of course, reverting to the old
version would also be an option.
Marc
--
BOFH #121:
halon system went off and killed the operators.
pgplnEh1AjLyq.pgp
Description: PGP signature
Bug#385364: gnome-tasksel: the GUI isn't listing the tasks.
Tags: patch thanks Hi Gustavo, This patch (actually not patch, but the .tar.gz file) do not solve all problems of the using GtkTreeView widget, but it is my attempt to help you to fix this bug. I don't fully understand and I can't remember how this program worked and how looked like on 'stable'. If you could send me such a screenshot where could be seen the "package_list" and the "task_tree" with the toggled checkbox, I would try to continue this work and try to get the same result with the GtkTreeView widget of Gtk+ version 2.0. Best regards, -- Kęstutis Biliūnas <[EMAIL PROTECTED]> gnome-tasksel_0.9.8~pre2.tar.gz Description: application/compressed-tar signature.asc Description: Ši laiško dalis yra pasirašyta skaitmeniniu būdu
Bug#380396: using update-fonts-dir --x11r7-layout in maintainer scripts breaks partial upgrades
* Andreas Barth ([EMAIL PROTECTED]) [061230 10:57]: > * Christoph Berg ([EMAIL PROTECTED]) [061230 06:15]: > > at the same time revert the debhelper change (#362820). All xfonts > > using debhelper would then need (bin?)nmus to get maintainer scripts > > without --x11r7-layout. > > I don't think we're at the right moment now to revert the debhelper > change - otherwise, we need to insert a versioned dependency on the new > xfonts-utils for the reverted debhelper script. On further consideration, I think changing debhelper is useful as well. We have the following kind of packages: - uses misc:depends: will get a versioned dependency on xfonts-utils, works as good as now (except there is some dependency in getting stuff into testing, but well) - depends on xfonts-utils but doesn't use misc:depends: This package will be slightly broken when installed on a not fully upgraded machine. In case xfonts-utils is changed in a way that on upgrade the stuff is inserted in the right directory anyways, I don't mind about the temporary breackage - especially as only affects half-broken packages, and it doesn't happen in stable - depends on xutils and doesn't use misc:depends: This package is broken now and might fail to install on half-upgrades, and will be less broken later. Cheers, Andi -- http://home.arcor.de/andreas-barth/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#404888: glib destabilization and ways forward
On Sat, 2006-12-30 at 17:15 +0100, Josselin Mouette wrote: > Le vendredi 29 décembre 2006 à 10:48 -0800, Thomas Bushnell BSG a > écrit : > > Despite what Josselin has said, I can see no indication from a brief > > perusal of the upstream branch sources in trac that upstream gnucash > > either no longer uses these key files or has changed away from the keys > > with embedded spaces. > > Then they must stop using GKeyFile. There is no way that they will get > this supported by GLib developers. This is an advertised interface for glib. If you want to change that, it requires an soname bump. > That leaves us with the silent data loss that can happen when using > broken key names (like, well, gnucash does). Whether this is or not a RC > issue, I'll let the release team decide. As upstream gnucash has pointed out, in the message I just forwarded, the previously advertised interface *did* make spaces legal in key names. > > 3) Decide that glib can migrate into testing with the destabilizing > > change intact, migrate an upstream gnucash fix into testing at the same > > time. > > This is the sanest solution because this is the one that gets us with > the lesser number of bugs. As it turns out, if upstream gnucash is correct, this *is* a substantial change to the *advertised interface* for the functions. Now you are saying the functions must not even be used at all, and yet, you are documenting them! Please decide what you want the interface to be, and since clearly you want something different from the previous one (whether prohibiting use of key files or changing the syntax of keys) bump the soname. Thomas signature.asc Description: This is a digitally signed message part
Processed: This is a serious issue
Processing commands for [EMAIL PROTECTED]: > severity 295375 serious Bug#295375: gpsd: Please split libgps into separate packages Severity set to `serious' from `wishlist' > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#405061: xserver-xorg-video-savage: Undefined symbol in savage driver
Subject: xserver-xorg-video-savage: Undefined symbol in savage driver Package: xserver-xorg-video-savage Version: 1:2.1.2-2 Severity: grave Justification: renders package unusable *** Please type your report below this line *** There is no such thing as SavageMamMem. No doubt, the fix to 397084 was supposed to call SavageMapMem. As it is, the drive can't be loaded due to an undefined symbol. -- Package-specific info: Contents of /var/lib/x11/X.roster: xserver-xorg /etc/X11/X target unchanged from checksum in /var/lib/x11/X.md5sum. X server symlink status: lrwxrwxrwx 1 root root 13 2006-04-12 18:12 /etc/X11/X -> /usr/bin/Xorg -rwxr-xr-x 1 root root 1597868 2006-12-30 02:39 /usr/bin/Xorg Contents of /var/lib/x11/xorg.conf.roster: xserver-xorg VGA-compatible devices on PCI bus: 01:00.0 VGA compatible controller: S3 Inc. SuperSavage IX/C SDR (rev 05) /var/lib/x11/xorg.conf.md5sum does not exist. Xorg X server configuration file status: -rw-r--r-- 1 root root 3813 2006-06-04 21:42 /etc/X11/xorg.conf Contents of /etc/X11/xorg.conf: Section "Files" FontPath"unix/:7100"# local font server # if the local font server has problems, we can fall back on these FontPath"/usr/share/fonts/X11/misc" FontPath"/usr/share/fonts/X11/misc" FontPath"/usr/lib/X11/fonts/misc" FontPath"/usr/share/fonts/X11/cyrillic" FontPath"/usr/share/fonts/X11/cyrillic" FontPath"/usr/lib/X11/fonts/cyrillic" FontPath"/usr/lib/X11/fonts/100dpi/:unscaled" FontPath"/usr/lib/X11/fonts/75dpi/:unscaled" FontPath"/usr/lib/X11/fonts/TrueType" FontPath"/usr/lib/X11/fonts/Speedo" FontPath"/usr/share/fonts/X11/100dpi" FontPath"/usr/share/fonts/X11/100dpi" FontPath"/usr/lib/X11/fonts/100dpi" FontPath"/usr/share/fonts/X11/75dpi" FontPath"/usr/share/fonts/X11/75dpi" FontPath"/usr/lib/X11/fonts/75dpi" FontPath"/usr/share/fonts/X11/Type1" FontPath"/usr/share/fonts/X11/Type1" FontPath"/usr/lib/X11/fonts/Type1" FontPath"/home/jk/.fonts/GillSans" EndSection ### BEGIN DEBCONF SECTION # XF86Config-4 (XFree86 server configuration file) generated by dexconf, the # Debian X Configuration tool, using values from the debconf database. # # Edit this file with caution, and see the XF86Config-4 manual page. # (Type "man XF86Config-4" at the shell prompt.) # # If you want your changes to this file preserved by dexconf, only make changes # before the "### BEGIN DEBCONF SECTION" line above, and/or after the # "### END DEBCONF SECTION" line below. # # To change things within the debconf section, run the command: # dpkg-reconfigure xserver-xfree86 # as root. Also see "How do I add custom sections to a dexconf-generated # XF86Config or XF86Config-4 file?" in /usr/share/doc/xfree86-common/FAQ.gz. Section "Module" Load"bitmap" Load"dbe" Load"ddc" Load"dri" Load"extmod" Load"freetype" Load"glx" Load"int10" Load"record" Load"type1" Load"vbe" EndSection Section "InputDevice" Identifier "Generic Keyboard" Driver "keyboard" Option "CoreKeyboard" Option "XkbRules" "xorg" Option "XkbModel" "pc101" Option "XkbLayout" "no" Option "XkbVariant""nodeadkeys" EndSection Section "InputDevice" Identifier "Configured Mouse" Driver "mouse" Option "CorePointer" Option "Device""/dev/psaux" Option "Protocol" "PS/2" Option "ZAxisMapping" "4 5" EndSection Section "InputDevice" Identifier "Generic Mouse" Driver "mouse" Option "CorePointer" Option "SendCoreEvents""true" Option "Device""/dev/input/mice" Option "Protocol" "ImPS/2" Option "ZAxisMapping" "4 5" EndSection Section "Device" Identifier "Generic Video Card" Driver "savage" EndSection Section "Monitor" Identifier "Generic Monitor" HorizSync 30-92 VertRefresh 50-85 Option "DPMS" EndSection Section "Screen" Identifier "Default Screen" Device "Generic Video Card" Monitor "Generic Monitor" DefaultDepth24 SubSection "Display" Depth 1 Modes "1280x1024" "1280x960" "1152x864" "1024x768" "800x600" "640x480" EndSubSection
Bug#405062: CVE-2006-4842: setuid/setgid programs linked with NSPR allow elevation of privilege
Package: libnspr4-0d Version: 1.8.0.8-1 Severity: grave Tags: security A vulnerability has been found in libnspr. From [1] : "NSPR logging is controlled with a couple of environment variables, one to enable it, and a second to control the name of the log file. This appears to all work in "optimized" (non-debug) builds. So, if any setuid root program is linked with NSPR, any user can clobber any file on the system (any root writable file) by setting NSPR's environment variables to log to that file, and then running a setuid root program linked with NSPR." I couldn't find any setuid binary in Debian that links against libnspr but there is "camel-lock-helper-1.2" in evolution-data-server which is setgid mail. AFAICS the above argument works also with setgid binaries. So this might allow to overwrite other people's mail if evolution-data-server is installed. The fix in [1] seems to only fix the setuid case. I am not sure whether this bug should be RC. Feel free to downgrade if you don't think so. [1] https://bugzilla.mozilla.org/show_bug.cgi?id=351470 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#404616: [Monotone-devel] Re: Bug#404616: monotone: Segmentation fault
(gdb) bt #0 0x0fe35ecc in __dynamic_cast () from /usr/lib/libstdc++.so.6 #1 0x100c1ef0 in std::out_of_range::~out_of_range () #2 0x10209214 in boost::detail::shared_count::~shared_count () #3 0x1012a674 in boost::gregorian::bad_month::~bad_month () #4 0x1012b060 in boost::gregorian::bad_month::~bad_month () #5 0x1012b27c in boost::gregorian::bad_month::~bad_month () #6 0x100f6ed8 in std::out_of_range::~out_of_range () #7 0x100f70e8 in std::out_of_range::~out_of_range () #8 0x100f7644 in std::out_of_range::~out_of_range () #9 0x100b7304 in std::out_of_range::~out_of_range () #10 0x1006f78c in std::_Rb_tree, std::_Select1st >, std::less, std::allocator > >::_M_erase () #11 0x102bcbec in std::vector >::~vector () #12 0x102befc8 in std::vector >::~vector () #13 0x0fb49994 in __libc_init_first () from /lib/tls/libc.so.6 #14 0x0fb49994 in __libc_init_first () from /lib/tls/libc.so.6 #15 0x0fb49994 in __libc_init_first () from /lib/tls/libc.so.6 Previous frame inner to this frame (corrupt stack?) which would seem to imply the stack is corrupt, and very possibly meaningless. That's a completely implausible stacktrace, too, so I think you're right. Things to try at this point: 1) Make absolutely sure that the Boost libraries are compiled with the same version of GCC as Monotone itself. This is the #1 cause of inexplicable segfaults. 2) Run the crashing command under valgrind - valgrind does support PPC now, I believe - and get us a backtrace from that. zw -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#405012: libwmf: Dependencies problem on experimental
severity 405012 important thanks Hi, * Nanomad ([EMAIL PROTECTED]) [061230 03:30]: > Package: libwmf > Version: 0.2.8.4-2 > Severity: grave > Justification: renders package unusable this doesn't render the package unusable, but "just" uninstallable in experimental. Cheers, Andi -- http://home.arcor.de/andreas-barth/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: Re: libwmf: Dependencies problem on experimental
Processing commands for [EMAIL PROTECTED]: > severity 405012 important Bug#405012: libwmf: Dependencies problem on experimental Severity set to `important' from `grave' > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#380396: using update-fonts-dir --x11r7-layout in maintainer scripts breaks partial upgrades
On Sat, Dec 30, 2006 at 03:16:20PM +0100, Christoph Berg wrote: > I believe the fix is to make --x11r7-layout the default (#363005) As recently noted, this was already done. The --x11r7-layout option to update-fonts-dir is supposed to be a no-op now, and AFAICS debhelper can drop that argument at any time. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: Re: This is a serious issue
Processing commands for [EMAIL PROTECTED]: > severity 295375 important Bug#295375: gpsd: Please split libgps into separate packages Severity set to `important' from `serious' > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#295375: This is a serious issue
severity 295375 important thanks * Adrian Bunk ([EMAIL PROTECTED]) [061230 12:06]: > Please package libgps correctly in libgps15 and libgps-dev. > > With the current setup, all packages linking with libgps.so.15 will > break if a gpsd containing libgps.so.x (x != 15) will ever enter the > archive. Though this statement is true, that is not release critical *yet* - because no such package has entered Debian yet. Of course, this sounds like a worthwhile goal for the Lenny release cycle to make such potential future RC bugs go away, but - currently, it is not release critical. Cheers, Andi -- http://home.arcor.de/andreas-barth/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#404733: dpkg error upgrading iceweasel
I've solved the problem unninstalling the packages flashplugin-nonfree totem-mozilla and sun-java5-plugin. After this upgrade the iceweasel and installing again flashplugin-nonfree totem-mozilla and sun-java5-plugin. Now all is working. Fabiano.
Processed: setting smbfs hard link bug to serious
Processing commands for [EMAIL PROTECTED]: > severity 384991 serious Bug#384991: smbfs: hard links are not supported any more Severity set to `serious' from `important' > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#385806: marked as done (eagle-usb - FTBFS: Uses not exported linux header)
Your message dated Sat, 30 Dec 2006 22:02:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#385806: fixed in eagle-usb 2.1.1-3 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) --- Begin Message --- Package: eagle-usb Version: 2.1.1-2.1 Severity: serious There was an error while trying to autobuild your package: > Automatic build of eagle-usb_2.1.1-2.1 on lxdebian.bfinv.de by sbuild/s390 85 [...] > make[1]: Entering directory `/build/buildd/eagle-usb-2.1.1/driver/user' > cc -O2 -pipe -Wall -pedantic -DLINUX -g -DCONF_DIR="\"/etc/eagle-usb\"" > -DBIN_DIR="\"/usr/share/eagle-usb/dsp\"" '-DEAGLEUSBVERSION="2.1.1"' > eaglectrl.c -o eaglectrl > In file included from /usr/include/asm/bitops.h:831, > from ../eu_types.h:29, > from ../eagle-usb.h:30, > from eaglectrl.c:40: > /usr/include/asm-generic/bitops/ffs.h:13: error: static declaration of 'ffs' > follows non-static declaration > make[1]: *** [eaglectrl] Error 1 > make[1]: Leaving directory `/build/buildd/eagle-usb-2.1.1/driver/user' > make: *** [build-arch-stamp] Error 2 > ** > Build finished at 20060902-2341 > FAILED [dpkg-buildpackage died] asm/bitops.h is not on the list of the linux headers which are safe to be used in userspace. Bastian --- End Message --- --- Begin Message --- Source: eagle-usb Source-Version: 2.1.1-3 We believe that the bug you reported is fixed in the latest version of eagle-usb, which is due to be installed in the Debian FTP archive: eagle-usb-data_2.1.1-3_all.deb to pool/main/e/eagle-usb/eagle-usb-data_2.1.1-3_all.deb eagle-usb-modules-source_2.1.1-3_all.deb to pool/main/e/eagle-usb/eagle-usb-modules-source_2.1.1-3_all.deb eagle-usb-utils_2.1.1-3_i386.deb to pool/main/e/eagle-usb/eagle-usb-utils_2.1.1-3_i386.deb eagle-usb_2.1.1-3.diff.gz to pool/main/e/eagle-usb/eagle-usb_2.1.1-3.diff.gz eagle-usb_2.1.1-3.dsc to pool/main/e/eagle-usb/eagle-usb_2.1.1-3.dsc A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Paul Cupis <[EMAIL PROTECTED]> (supplier of updated eagle-usb package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sat, 30 Dec 2006 21:23:00 + Source: eagle-usb Binary: eagle-usb-utils eagle-usb-modules-source eagle-usb-data Architecture: source i386 all Version: 2.1.1-3 Distribution: unstable Urgency: low Maintainer: [EMAIL PROTECTED] Changed-By: Paul Cupis <[EMAIL PROTECTED]> Description: eagle-usb-data - Data for Eagle USB ADSL modems eagle-usb-modules-source - EAGLE-USB binary kernel module source for Eagle USB ADSL modems eagle-usb-utils - Userspace tools for Eagle USB ADSL modems Closes: 304692 307177 310105 311606 311608 319032 330778 336998 349146 353804 358262 376562 377326 377326 379970 381755 385806 388112 402302 Changes: eagle-usb (2.1.1-3) unstable; urgency=low . * Change package maintainer. * Acknowledge NMUs since last maintainer upload. . eagle-usb (2.1.1-2.3) unstable; urgency=low . * Non-maintainer upload. - upload to unstable even though testing is frozen for etch as packages are self-contained and should not affect the freeze. * Debconf translation updates: - es, thanks to César Gómez MartÃn (closes: #402302) - vi, thanks to Clytie Siddall (closes: #311606) - pl, thanks to Emil Nowak (closes: #353804) - cs, thanks to Miroslav Kure (closes: #307177) - ja, thanks to Hideki Yamane (closes: #310105) - template/en, thanks to Clytie Siddall (closes: #311608) - da, thanks to Claus Hindsgaul (closes: #319032) - sv, thanks to Daniel Nylander (closes: #330778) - nl, thanks to Kurt De Bree (closes: #379970, #388112) * Add Depends on binutils for 'strings' invocation in utils/scripts/eagleconfig (closes: #304692) * Fix ENC bug in eagleconfig (closes: #336998) . eagle-usb (2.1.1-2.2) experimental; urgency=low . * Non-maintainer upload. - upload to experimental as I am still working on some of the bugs as well as looking at new
Bug#377326: marked as done (eagle-usb-modules-source: fails to compile)
Your message dated Sat, 30 Dec 2006 22:02:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#377326: fixed in eagle-usb 2.1.1-3 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) --- Begin Message --- Package: eagle-usb-modules-source Version: 2.1.1-2 Severity: grave Justification: renders package unusable -- System Information: Debian Release: 3.1 APT prefers testing APT policy: (1001, 'testing'), (101, 'unstable') Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.17.3 Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8) Versions of packages eagle-usb-modules-source depends on: ii debhelper 5.0.37.2 helper programs for debian/rules ii make 3.81-2 The GNU version of the "make" util Versions of packages eagle-usb-modules-source recommends: ii kernel-package10.049 A utility for building Linux kerne ii module-assistant 0.10.4 tool to make module package creati -- debconf-show failed Hi, this seems to be the cause: USE_CMVS=0 make -C /lib/modules/2.6.17.3/source SUBDIRS=/usr/src/modules/eagle-usb/driver modules make[1]: Entering directory `/usr/src/linux-2.6.17.3' CC [M] /usr/src/modules/eagle-usb/driver/eu_main.o In file included from /usr/src/modules/eagle-usb/driver/eagle-usb.h:30, from /usr/src/modules/eagle-usb/driver/eu_main.c:41: /usr/src/modules/eagle-usb/driver/eu_types.h:54:5: warning: "USE_CMVS" is not defined /usr/src/modules/eagle-usb/driver/eu_main.c:176: error: unknown field 'owner' specified in initializer /usr/src/modules/eagle-usb/driver/eu_main.c:176: warning: initialization from incompatible pointer type /usr/src/modules/eagle-usb/driver/eu_main.c:253: error: expected ')' before string constant /usr/src/modules/eagle-usb/driver/eu_main.c:255: error: expected ')' before string constant /usr/src/modules/eagle-usb/driver/eu_main.c:1101:5: warning: "USE_CMVS" is not defined /usr/src/modules/eagle-usb/driver/eu_main.c:1336:5: warning: "USE_CMVS" is not defined /usr/src/modules/eagle-usb/driver/eu_main.c:1404:5: warning: "USE_CMVS" is not defined make[2]: *** [/usr/src/modules/eagle-usb/driver/eu_main.o] Error 1 make[1]: *** [_module_/usr/src/modules/eagle-usb/driver] Error 2 make[1]: Leaving directory `/usr/src/linux-2.6.17.3' make: *** [eagle-usb.ko] Error 2 The kernel is compiled from the original tarball using kernel-package utility and the compiler is gcc-4.0.4 $ LC_ALL=C cc -v Using built-in specs. Target: x86_64-linux-gnu Configured with: ../src/configure -v --enable-languages=c,c++,java,f95,objc,ada, treelang --prefix=/usr --enable-shared --with-system-zlib --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --enable-nls --program-suffix= -4.0 --enable-__cxa_atexit --enable-clocale=gnu --enable-libstdcxx-debug --enabl e-java-awt=gtk --enable-gtk-cairo --with-java-home=/usr/lib/jvm/java-1.4.2-gcj-4 .0-1.4.2.0/jre --enable-mpfr --disable-werror --enable-checking=release x86_64-l inux-gnu Thread model: posix gcc version 4.0.4 20060507 (prerelease) (Debian 4.0.3-3) Best Regards, Manolo. --- End Message --- --- Begin Message --- Source: eagle-usb Source-Version: 2.1.1-3 We believe that the bug you reported is fixed in the latest version of eagle-usb, which is due to be installed in the Debian FTP archive: eagle-usb-data_2.1.1-3_all.deb to pool/main/e/eagle-usb/eagle-usb-data_2.1.1-3_all.deb eagle-usb-modules-source_2.1.1-3_all.deb to pool/main/e/eagle-usb/eagle-usb-modules-source_2.1.1-3_all.deb eagle-usb-utils_2.1.1-3_i386.deb to pool/main/e/eagle-usb/eagle-usb-utils_2.1.1-3_i386.deb eagle-usb_2.1.1-3.diff.gz to pool/main/e/eagle-usb/eagle-usb_2.1.1-3.diff.gz eagle-usb_2.1.1-3.dsc to pool/main/e/eagle-usb/eagle-usb_2.1.1-3.dsc A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Paul Cupis <[EMAIL PROTECTED]> (supplier of updated eagle-usb package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sat, 30 Dec 2006 21:23:00 + Source: eagle-usb Bina
Bug#405027: marked as done (libwww-mechanize-ruby: missing dependency against libopenssl-ruby)
Your message dated Sat, 30 Dec 2006 23:13:21 +0100 with message-id <[EMAIL PROTECTED]> and subject line Please allow libwww-mechanize-ruby 0.6.3-2 into testing has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) --- Begin Message --- Package: libwww-mechanize-ruby Version: 0.6.3-1 Severity: important libwww-mechanize-ruby seems to depend on libopenssl-ruby: /usr/lib/ruby/1.8/mechanize.rb:15:in `require': no such file to load -- net/https (LoadError) from /usr/lib/ruby/1.8/mechanize.rb:15 from ./test.rb:3:in `require' from ./test.rb:3 -- System Information: Debian Release: 4.0 APT prefers testing APT policy: (990, 'testing'), (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.15.7 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Versions of packages libwww-mechanize-ruby depends on: ii libwww-mechanize-ruby1.8 0.6.3-1Automate interaction with websites libwww-mechanize-ruby recommends no packages. -- no debconf information --- End Message --- --- Begin Message --- Package: libwww-mechanize-ruby Version: 0.6.3-2 Ari Pollak <[EMAIL PROTECTED]> writes: > libwww-mechanize-ruby 0.6.3-2 contains only two changes to fix RC bug #405027, > which required adding dependencies on libopenssl-ruby1.8 and > libopenssl-ruby1.9. I'd like to request that this be moved into testing. Unblocked. Please note that you have a typo in the changelog, so the bug wasn't closed (fixed with this mail). Marc -- BOFH #367: Webmasters kidnapped by evil cult. --- End Message ---
Processed: severity of 405027 is serious
Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.9.27 > severity 405027 serious Bug#405027: libwww-mechanize-ruby: missing dependency against libopenssl-ruby Severity set to `serious' from `grave' > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#405006: libgphoto2: mistake in udev rules gives permissions to non-gphoto2 devices
On Sat, Dec 30, 2006 at 10:49:26AM +0100, Nicolas George wrote:
> Package: libgphoto2-2
> Version: 2.2.1-12
> Severity: grave
> Tags: security
> In /etc/udev/libgphoto2_generic_ptp_support.rules, there is the following
> rule:
> ACTION=="add", SUBSYSTEM=="usb_device", ENV{INTERFACE}="6/1/1", \
> PROGRAM="/bin/sh -c 'K=%k; K=$${K#usbdev}; printf bus/usb/%%03i/%%03i
> $${K.*} $${K#*.}'", \
> NAME="%c", MODE="0660", GROUP="plugdev"
> The single = sign after ENV{INTERFACE} means that the INTERFACE environment
> variable is set, not queried. The result is that all USB devices, and not
> only the PTP ones, are set to the plugdev group, thus giving some users
> access to devices they should not have access to.
> Suggested fix: put two equals signs
Isn't the plugdev group empty by default? This is obviously a bug, but I'm
not sure it qualifies as a grave security bug.
For that matter, with which devices are you seeing this problem? After
upgrading to this version of libgphoto2-2, plugging in a USB hard drive
still gives me:
brw-rw 1 root disk 8, 0 2006-12-30 15:30 /dev/sda
brw-rw 1 root disk 8, 1 2006-12-30 15:30 /dev/sda1
What class of USB devices are ending up under group plugdev that shouldn't?
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
[EMAIL PROTECTED] http://www.debian.org/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#404876: Backtrace
On Sat, Dec 30, 2006 at 11:51:03AM +0200, Yavor Doganov wrote: > Program received signal SIGILL, Illegal instruction. > 0x0d74e4cc in visual_cpu_get_tsc () from /usr/lib/libvisual-0.4.so.0 > (gdb) bt > #0 0x0d74e4cc in visual_cpu_get_tsc () from /usr/lib/libvisual-0.4.so.0 > #1 0x0d74e588 in visual_cpu_initialize () from /usr/lib/libvisual-0.4.so.0 > #2 0x0d748d88 in visual_init () from /usr/lib/libvisual-0.4.so.0 > #3 0x0d77a2a0 in gst_visual_get_type () from > /usr/lib/gstreamer-0.10/libgstlibvisual.so > However, if I remove libgstlibvisual.so, I get the following while > launching the first command with LANG=C: Ok, that is approximately what I expected, although I'm a bit confused. Could you (or someone) get back to the state where it's broken, and run ulimit -c unlimited rm ~/.gstreamer-0.10/registry.powerpc.xml gst-launch-0.10 And let it crash. Then run: gdb gst-launch-0.10 core and do a backtrace. (The core file might have a pid suffix.) dave... -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#403542: python-mutagen: Does not write syncsafe datalen flags
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 It's SVN changeset 3966[0]. [0] http://sacredchao.net/quodlibet/changeset/3966 Thanks, - -- Daniel T. Chen[EMAIL PROTECTED] GPG key: 0xC88ABDA3 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFlvq7e9GwFciKvaMRAp5VAJ40YTRB0ReAvdFKVZrg4H0a3jmxIQCgki0E 7UMb0DWHRT6wnzMSHMK1FXU= =jEs6 -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#405006: libgphoto2: mistake in udev rules gives permissions to non-gphoto2 devices
Le decadi 10 nivôse, an CCXV, Steve Langasek a écrit : > Isn't the plugdev group empty by default? This is obviously a bug, but I'm > not sure it qualifies as a grave security bug. The administrator is encouraged to add to this group users that need to access cameras and similar devices. I believe this qualifies as a security risk: users that had no access to some resources now can access them, without the administrator knowing. The "grave" qualification is probably exaggerated, but I was under the impression that all security bugs should have it; maybe I was wrong; if so I am sorry. > For that matter, with which devices are you seeing this problem? After > upgrading to this version of libgphoto2-2, plugging in a USB hard drive > still gives me: > > brw-rw 1 root disk 8, 0 2006-12-30 15:30 /dev/sda > brw-rw 1 root disk 8, 1 2006-12-30 15:30 /dev/sda1 > > What class of USB devices are ending up under group plugdev that shouldn't? It concerns the raw USB devices, in /dev/bus/usb/, used by libusb for userland drivers. At the time where it was in /prob/bus/usb/, I believe only devices with no kernel driver were available there, but it seems no longer the case. In your example, you could probably have full access to the disk using a userland mass-storage driver (there is such a thing floating around on the web). Regards, -- Nicolas George signature.asc Description: Digital signature
Processed: PuTTY bug maintenance
Processing commands for [EMAIL PROTECTED]: > forwarded 287960 > http://www.chiark.greenend.org.uk/~sgtatham/putty/wishlist/gcc4-warnings.html Bug#287960: putty: FTBFS (amd64/gcc-4.0): pointer targets in passing argument 2 of 'hmacmd5_key' differ in signedness Forwarded-to-address changed from [EMAIL PROTECTED] to http://www.chiark.greenend.org.uk/~sgtatham/putty/wishlist/gcc4-warnings.html. (By the way, this Bug is currently marked as done.) > retitle 323791 PuTTY window title changes to reverse IP address Bug#323791: PUTTY window title change to reverse IP adress Changed Bug title. > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#403215: marked as done (tendra: provides /usr/bin/trans, also in transcriber)
Your message dated Sun, 31 Dec 2006 00:02:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#403215: fixed in tendra 4.1.2-16 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) --- Begin Message --- Package: tendra Version: 4.1.2-15 Severity: normal dpkg: error processing /var/cache/apt/archives/tendra_4.1.2-15_i386.deb (--unpack): trying to overwrite `/usr/share/man/man1/pl.1.gz', which is also in package gnustep-base-runtime bug also send to gnustep-base-runtime -- System Information: Debian Release: 4.0 APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.17.8 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) --- End Message --- --- Begin Message --- Source: tendra Source-Version: 4.1.2-16 We believe that the bug you reported is fixed in the latest version of tendra, which is due to be installed in the Debian FTP archive: tendra_4.1.2-16.diff.gz to pool/main/t/tendra/tendra_4.1.2-16.diff.gz tendra_4.1.2-16.dsc to pool/main/t/tendra/tendra_4.1.2-16.dsc tendra_4.1.2-16_i386.deb to pool/main/t/tendra/tendra_4.1.2-16_i386.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Mark Brown <[EMAIL PROTECTED]> (supplier of updated tendra package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sat, 30 Dec 2006 22:37:52 + Source: tendra Binary: tendra Architecture: source i386 Version: 4.1.2-16 Distribution: unstable Urgency: medium Maintainer: Mark Brown <[EMAIL PROTECTED]> Changed-By: Mark Brown <[EMAIL PROTECTED]> Description: tendra - A C and C++ compiler and checker using TDF/ANDF Closes: 403215 Changes: tendra (4.1.2-16) unstable; urgency=medium . * Don't ship trans and drop confict with transcriber (closes: #403215). Files: 678f3f23c8a741be9b066152f974da7c 548 devel extra tendra_4.1.2-16.dsc 29927ca6431ffb919aa5031e5dbfc1d1 7098 devel extra tendra_4.1.2-16.diff.gz e354e1d2e15602b32f67f71f16e9cdd7 2121558 devel extra tendra_4.1.2-16_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFFlvU6J2Vo11xhU60RAtreAKDdD2XiyU0cDMD2i6EDBVa4tBhkcQCgk/nf yc1i4AvJExKFKrxDPg6n5bM= =bTsq -END PGP SIGNATURE- --- End Message ---
Bug#405061: marked as done (xserver-xorg-video-savage: Undefined symbol in savage driver)
Your message dated Sun, 31 Dec 2006 00:32:02 + with message-id <[EMAIL PROTECTED]> and subject line Bug#405061: fixed in xserver-xorg-video-savage 1:2.1.2-3 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) --- Begin Message --- Subject: xserver-xorg-video-savage: Undefined symbol in savage driver Package: xserver-xorg-video-savage Version: 1:2.1.2-2 Severity: grave Justification: renders package unusable *** Please type your report below this line *** There is no such thing as SavageMamMem. No doubt, the fix to 397084 was supposed to call SavageMapMem. As it is, the drive can't be loaded due to an undefined symbol. -- Package-specific info: Contents of /var/lib/x11/X.roster: xserver-xorg /etc/X11/X target unchanged from checksum in /var/lib/x11/X.md5sum. X server symlink status: lrwxrwxrwx 1 root root 13 2006-04-12 18:12 /etc/X11/X -> /usr/bin/Xorg -rwxr-xr-x 1 root root 1597868 2006-12-30 02:39 /usr/bin/Xorg Contents of /var/lib/x11/xorg.conf.roster: xserver-xorg VGA-compatible devices on PCI bus: 01:00.0 VGA compatible controller: S3 Inc. SuperSavage IX/C SDR (rev 05) /var/lib/x11/xorg.conf.md5sum does not exist. Xorg X server configuration file status: -rw-r--r-- 1 root root 3813 2006-06-04 21:42 /etc/X11/xorg.conf Contents of /etc/X11/xorg.conf: Section "Files" FontPath"unix/:7100"# local font server # if the local font server has problems, we can fall back on these FontPath"/usr/share/fonts/X11/misc" FontPath"/usr/share/fonts/X11/misc" FontPath"/usr/lib/X11/fonts/misc" FontPath"/usr/share/fonts/X11/cyrillic" FontPath"/usr/share/fonts/X11/cyrillic" FontPath"/usr/lib/X11/fonts/cyrillic" FontPath"/usr/lib/X11/fonts/100dpi/:unscaled" FontPath"/usr/lib/X11/fonts/75dpi/:unscaled" FontPath"/usr/lib/X11/fonts/TrueType" FontPath"/usr/lib/X11/fonts/Speedo" FontPath"/usr/share/fonts/X11/100dpi" FontPath"/usr/share/fonts/X11/100dpi" FontPath"/usr/lib/X11/fonts/100dpi" FontPath"/usr/share/fonts/X11/75dpi" FontPath"/usr/share/fonts/X11/75dpi" FontPath"/usr/lib/X11/fonts/75dpi" FontPath"/usr/share/fonts/X11/Type1" FontPath"/usr/share/fonts/X11/Type1" FontPath"/usr/lib/X11/fonts/Type1" FontPath"/home/jk/.fonts/GillSans" EndSection ### BEGIN DEBCONF SECTION # XF86Config-4 (XFree86 server configuration file) generated by dexconf, the # Debian X Configuration tool, using values from the debconf database. # # Edit this file with caution, and see the XF86Config-4 manual page. # (Type "man XF86Config-4" at the shell prompt.) # # If you want your changes to this file preserved by dexconf, only make changes # before the "### BEGIN DEBCONF SECTION" line above, and/or after the # "### END DEBCONF SECTION" line below. # # To change things within the debconf section, run the command: # dpkg-reconfigure xserver-xfree86 # as root. Also see "How do I add custom sections to a dexconf-generated # XF86Config or XF86Config-4 file?" in /usr/share/doc/xfree86-common/FAQ.gz. Section "Module" Load"bitmap" Load"dbe" Load"ddc" Load"dri" Load"extmod" Load"freetype" Load"glx" Load"int10" Load"record" Load"type1" Load"vbe" EndSection Section "InputDevice" Identifier "Generic Keyboard" Driver "keyboard" Option "CoreKeyboard" Option "XkbRules" "xorg" Option "XkbModel" "pc101" Option "XkbLayout" "no" Option "XkbVariant""nodeadkeys" EndSection Section "InputDevice" Identifier "Configured Mouse" Driver "mouse" Option "CorePointer" Option "Device""/dev/psaux" Option "Protocol" "PS/2" Option "ZAxisMapping" "4 5" EndSection Section "InputDevice" Identifier "Generic Mouse" Driver "mouse" Option "CorePointer" Option "SendCoreEvents""true" Option "Device""/dev/input/mice" Option "Protocol" "ImPS/2"
Bug#404733: Conflicts between symbolic links and directories
Debian bug #404733 shows a case where installation of a package fails because it contains a symbolic link with the same path as a directory included in an installed package. I think this is the expected behaviour. However, installation of this package worked for me in a similar situation, and presumably has for other users. Has there been any deliberate change in dpkg that would explain why this does work in some cases or versions? Ben. -- Ben Hutchings For every action, there is an equal and opposite criticism. - Harrison signature.asc Description: This is a digitally signed message part
Bug#404876: Re:
On Dec 30, 2006, at 8:11 PM, Paul Mackerras wrote: Rick Thomas writes: However, after rebooting following the install, and logging in to gnome, it seems to be repeatedly trying to start/re-start something having to do with the appearance of the desktop. Things are very slow (as if a process in continually crashing and restarting) and the appearance of the desktop cycles thru a series of subtle but disturbing changes that I'll call "wiggling" for want of a better word. I have seen behaviour more or less like this when the clock was set wrongly, i.e. to 1904 or something, so check that the clock setting is reasonable. (I have no idea why a bogus clock setting upsets gnome so much.) Paul. A good thought. Unfortunately, the date & time are correct on this machine. I just did "aptitude update && aptitude upgrade" and it installed newer versions of lots of gnome related stuff. But no joy. The wiggles haven't gone away. Still hoping that somebody can help me debug this thing! Rick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: severity of 384991 is important
Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.9.27 > severity 384991 important Bug#384991: smbfs: hard links are not supported any more Severity set to `important' from `serious' > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#405014: marked as done (planner: potential FTBFS since newest python-support)
Your message dated Sun, 31 Dec 2006 03:32:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#405014: fixed in planner 0.14.2-2 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) --- Begin Message --- Package: planner Version: 0.14.2-1 Severity: serious Justification: no longer builds from source -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 While polishing the packaging of another software, I noticed that recent versions of either CDBS, dh_python or dh_pysupport require an environment variable called DEB_PYTHON_SYSTEM in debian/rules. I have already patched debian/control and debian/rules to fix this (upload pending); this report just files the existence of this potential FTBFS bug. - -- System Information: Debian Release: 4.0 APT prefers testing APT policy: (550, 'testing') Architecture: powerpc (ppc) Shell: /bin/sh linked to /bin/dash Kernel: Linux 2.6.18-imac Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8) Versions of packages planner depends on: ii gconf2 2.16.0-3 GNOME configuration database syste ii libart-2.0-2 2.3.17-1 Library of functions for 2D graphi ii libatk1.0-01.12.3-1 The ATK accessibility toolkit ii libbonobo2-0 2.14.0-3 Bonobo CORBA interfaces library ii libbonoboui2-0 2.14.0-5 The Bonobo UI library ii libc6 2.3.6.ds1-8 GNU C Library: Shared libraries ii libcairo2 1.2.4-4 The Cairo 2D vector graphics libra ii libfontconfig1 2.4.1-2 generic font configuration library ii libgconf2-42.16.0-3 GNOME configuration database syste ii libgda2-3 1.2.3-3 GNOME Data Access library for GNOM ii libglade2-01:2.6.0-3 library to load .glade files at ru ii libglib2.0-0 2.12.4-2 The GLib library of C routines ii libgnome-keyring0 0.6.0-3 GNOME keyring services library ii libgnome2-02.16.0-2 The GNOME 2 library - runtime file ii libgnomecanvas2-0 2.14.0-2 A powerful object-oriented display ii libgnomeprint2.2-0 2.12.1-7 The GNOME 2.2 print architecture - ii libgnomeprintui2.2-0 2.12.1-4 GNOME 2.2 print architecture User ii libgnomeui-0 2.14.1-2 The GNOME 2 libraries (User Interf ii libgnomevfs2-0 2.14.2-4 GNOME virtual file-system (runtime ii libgtk2.0-02.8.20-3 The GTK+ graphical user interface ii libice61:1.0.1-2 X11 Inter-Client Exchange library ii liborbit2 1:2.14.3-0.1 libraries for ORBit2 - a CORBA ORB ii libpango1.0-0 1.14.8-3 Layout and rendering of internatio ii libpopt0 1.10-3lib for parsing cmdline parameters ii libsm6 1:1.0.1-3 X11 Session Management library ii libx11-6 2:1.0.3-4 X11 client-side library ii libxcursor11.1.7-4 X cursor management library ii libxext6 1:1.0.1-2 X11 miscellaneous extension librar ii libxfixes3 1:4.0.1-5 X11 miscellaneous 'fixes' extensio ii libxi6 1:1.0.1-4 X11 Input extension library ii libxinerama1 1:1.0.1-4.1 X11 Xinerama extension library ii libxml22.6.27.dfsg-1 GNOME XML library ii libxrandr2 2:1.1.0.2-5 X11 RandR extension library ii libxrender11:0.9.1-3 X Rendering Extension client libra ii libxslt1.1 1.1.19-1 XSLT processing library - runtime ii python2.4 2.4.4-1 An interactive high-level object-o ii scrollkeeper 0.3.14-11 A free electronic cataloging syste ii shared-mime-info 0.19-1FreeDesktop.org shared MIME databa ii zlib1g 1:1.2.3-13compression library - runtime Versions of packages planner recommends: ii gda2-postgres 1.2.3-3PostgreSQL backend plugin for GNOM - -- no debconf information -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFFllGYeXr56x4Muc0RAtBnAKCMZh5b9b2dvvS9yoPsfKC6L75gzACgqR5b zH/2SpXATsaqGwk+/ScUsH0= =j+sH -END PGP SIGNATURE- --- End Message --- --- Begin Message --- Source: planner Source-Version: 0.14.2-2 We believe that the bug you reported is fixed in the latest version of planner, whi
Processed: Re: Bug#405014: planner: potential FTBFS since newest python-support
Processing commands for [EMAIL PROTECTED]: > severity 405014 normal Bug#405014: planner: potential FTBFS since newest python-support Severity set to `normal' from `serious' > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#405014: planner: potential FTBFS since newest python-support
severity 405014 normal thanks On Sat, Dec 30, 2006 at 01:46:33PM +0200, Martin-Éric Racine wrote: > While polishing the packaging of another software, I noticed that recent > versions of either CDBS, dh_python or dh_pysupport require an environment > variable called DEB_PYTHON_SYSTEM in debian/rules. > I have already patched debian/control and debian/rules to fix this (upload > pending); this report just files the existence of this potential FTBFS bug. I have no idea what you mean by "potential" FTBFS. This package builds fine under both etch and sid. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/
Bug#405091: jokosher: missing dependence in pygst module
Package: jokosher Version: 0.2-1.1 Severity: grave Justification: renders package unusable Can't run jokosher at all: [EMAIL PROTECTED]:~$ jokosher Error loading Jokosher: No module named pygst I've seen already several bug reports related to missing dependence. Please, dudes! Claudio -- System Information: Debian Release: 4.0 APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/dash Kernel: Linux 2.6.18-1-686 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Versions of packages jokosher depends on: ii gstreamer0.10-gnomevfs0.10.10-2 GStreamer plugin for GnomeVFS ii gstreamer0.10-gnonlin 0.10.6-2 non-linear editing module for GStr ii gstreamer0.10-plugins-base0.10.10-2 GStreamer plugins from the "base" ii gstreamer0.10-plugins-good0.10.4-3 GStreamer plugins from the "good" ii librsvg2-common 2.14.4-2 SAX-based renderer library for SVG ii python2.4.4-2An interactive high-level object-o ii python-alsaaudio 0.2-1 Alsa bindings for Python ii python-cairo 1.2.0-1Python bindings for the Cairo vect ii python-dbus 0.71-3 simple interprocess messaging syst ii python-glade2 2.8.6-8GTK+ bindings: Glade support ii python-gnome2 2.12.4-5 Python bindings for the GNOME desk ii python-gst0.100.10.5-5 generic media-playing framework (P ii python-gtk2 2.8.6-8Python bindings for the GTK+ widge ii python-setuptools 0.6c3-3Python Distutils Enhancements ii python-support0.5.6 automated rebuilding support for p jokosher recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#405092: pitivi: won't run due to supposedly missing pygtk dependence
Package: pitivi Version: 0.10.1-2 Severity: grave Justification: renders package unusable When running I get the following error: [EMAIL PROTECTED]:~$ pitivi PyGTK couldn't be found ! and the program quits. -- System Information: Debian Release: 4.0 APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/dash Kernel: Linux 2.6.18-1-686 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Versions of packages pitivi depends on: ii gstreamer0.10-gnonlin 0.10.6-2 non-linear editing module for GStr ii gstreamer0.10-plugins-base0.10.10-2 GStreamer plugins from the "base" ii gstreamer0.10-plugins-good0.10.4-3 GStreamer plugins from the "good" ii gstreamer0.10-x 0.10.10-2 GStreamer plugins for X11 and Pang ii libgstreamer0.10-00.10.10-2 Core GStreamer libraries and eleme ii python2.4.4-2An interactive high-level object-o ii python-central0.5.12 register and build utility for Pyt ii python-glade2 2.8.6-8GTK+ bindings: Glade support ii python-gst0.100.10.5-5 generic media-playing framework (P ii python-gtk2 2.8.6-8Python bindings for the GTK+ widge pitivi recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
