Processed: ara FTBFS bogus
Processing commands for [EMAIL PROTECTED]: severity 290338 important Bug#290338: ara: [m68k] FTBFS dh_testdir: I have no package to build Severity set to `important'. 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#267799: nvidia module not autoloading
Why can't the package just be modified so that the postinst does an 'echo nvidia /etc/modules' if it is not already in there? While this is an acceptable workaround while they look for a real solution, in general, this is not a very good thing to do. Not everybody wants to have X to start up on boot via xdm/kdm/gdm/whateverdm, so loading nvidia is also unneeded in that case (when loaded, it consumes resources -- by allocating kernel memory, installing the interrupt handler etc.) Also, if you are trying to isolate a reason for a crash that you suspect is a kernel bug unrelated to nvidia, you must do it w/o loading the modules like nvidia that taint your kernel, otherwise the kernel developers will typically disregard your report. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: Re: Bug#291386: kernel-image-2.4.27-2-686: creates bad initrd with complex lvm2 setup
Processing commands for [EMAIL PROTECTED]: reassign 291386 initrd-tools Bug#291386: kernel-image-2.4.27-2-686: creates bad initrd with complex lvm2 setup Bug reassigned from package `kernel-image-2.4.27-2-686' to `initrd-tools'. 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#291386: kernel-image-2.4.27-2-686: creates bad initrd with complex lvm2 setup
reassign 291386 initrd-tools thanks On Thu, Jan 20, 2005 at 02:17:34PM +0100, Eric Deplagne wrote: Package: kernel-image-2.4.27-2-686 Version: 2.4.27-7 Severity: critical Justification: breaks the whole system When the install of kernel-image tries to create initrd, those lines go to /var/log/messages: Jan 20 09:39:39 fregate kernel: device-mapper: unknown block ioctl 0x801c6d02 Jan 20 09:39:40 fregate last message repeated 14 times I do have 15 logical volumes, which explains how many times the message is emitted... I guess I should mention a bit of my partitionning scheme, out of my /etc/fstab: # system /dev/mapper/vg-root / ext3defaults,errors=remount-ro 0 1 /dev/mapper/vg-usr_lib /usr/lib ext3defaults 0 1 /dev/mapper/vg-usr_share /usr/share ext3defaults 0 1 /dev/mapper/vg-doc /usr/share/docext3defaults 0 1 /dev/mapper/vg-locale /usr/share/localeext3defaults 0 1 /dev/mapper/vg-cache_apt /var/cache/apt/archivesext3defaults 0 2 maybe my having /usr/lib on a different logical volume is relevant... just a guess of mine, of course... my other logical volumes are one for /home, and some for subdirectories of /home, so should not be relevant... Last thing I guess I can mention is that on another machine, with only one logical volume for /, and one for /home, /var/log/messages gets its two lines, but the system boots properly... you might notice I presently run a 2.4.27-1-686, this is my rescue that I had a hard time to setup when the problem first happend to me with the last update of 2.4.27-1-868, which really hang the computer, having overwritten my working kernel. (that did not happen this time because of the -1-686 to -2-686 move) -- System Information: Debian Release: 3.1 APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.4.27-1-686 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) Versions of packages kernel-image-2.4.27-2-686 depends on: ii coreutils [fileutils] 5.2.1-2The GNU core utilities ii fileutils 5.2.1-2The GNU file management utilities ii initrd-tools 0.1.76 tools to create initrd image for p ii modutils 2.4.26-1.2 Linux module utilities -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- Horms -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#289139: marked as done (plan_1.8.7-2_arm: FTBFS: yacc: Command not found)
Your message dated Mon, 24 Jan 2005 09:58:32 +0100 with message-id [EMAIL PROTECTED] and subject line Closing, intermittend buildd chroot screwup 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) -- Received: (at submit) by bugs.debian.org; 7 Jan 2005 12:24:41 + From [EMAIL PROTECTED] Fri Jan 07 04:24:41 2005 Return-path: [EMAIL PROTECTED] Received: from cpe-138-217-163-107.vic.bigpond.net.au (motilon.apana.org.au) [138.217.163.107] by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1CmtAX-0008UM-00; Fri, 07 Jan 2005 04:24:41 -0800 Received: from calima.apana.org.au (tairona.apana.org.au [203.12.238.226]) by motilon.apana.org.au (Postfix) with ESMTP id E87F32099 for [EMAIL PROTECTED]; Fri, 7 Jan 2005 23:24:43 +1100 (EST) Received: from nukak.apana.org.au (nukak.apana.org.au [203.12.238.230]) by calima.apana.org.au (Postfix) with ESMTP id 839821FF1 for [EMAIL PROTECTED]; Fri, 7 Jan 2005 23:24:38 +1100 (EST) Received: by nukak.apana.org.au (Postfix, from userid 1000) id 133CD1D1433; Fri, 7 Jan 2005 23:24:38 +1100 (EST) Date: Fri, 7 Jan 2005 23:24:38 +1100 From: Anibal Monsalve Salazar [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: plan_1.8.7-2_arm: FTBFS: yacc: Command not found Message-ID: [EMAIL PROTECTED] Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol=application/pgp-signature; boundary=OqZxW6Yu4sgZZmrd Content-Disposition: inline User-Agent: Mutt/1.5.6+20040907i Delivered-To: [EMAIL PROTECTED] X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 (1.212-2003-09-23-exp) on spohr.debian.org X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE autolearn=no version=2.60-bugs.debian.org_2005_01_02 X-Spam-Level: --OqZxW6Yu4sgZZmrd Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Package: plan Severity: serious Version: 1.8.7-2 Tags: sid Justification: fails to build from source There was an error while trying to autobuild your package: Automatic build of plan_1.8.7-2 on smackdown by sbuild/arm 1.170.5 Build started at 20050106-2339 [...] ** Using build dependencies supplied by package: Build-Depends: debhelper (= 4.1.16), dpatch, patch, lesstif2-dev | lesstif-dev, xlibs-dev, flex (= 2.5.4a-17), bison [...] yacc -d parser.y make[2]: yacc: Command not found make[2]: *** [parser.c] Error 127 Full build logs are available on buildd.debian.org. Please refer to the build log at: http://buildd.debian.org/fetch.php?pkg=planver=1.8.7-2arch=armstamp=1105056190file=logas=raw If this problem has been reported already, please merge it with the appropiate bug report. If you believe this bug should be reassigned to one or more packages, you must clone it and then reassign it to the other packages, like so: clone bug# -1 clone bug# -2 clone bug# -3 reassign -1 package1 reassign -2 package2 reassign -3 package3 thanks Anibal Monsalve Salazar -- .''`. Debian GNU/Linux : :' : Free Operating System `. `' http://debian.org/ `- http://v7w.com/anibal --OqZxW6Yu4sgZZmrd Content-Type: application/pgp-signature; name=signature.asc Content-Description: Digital signature Content-Disposition: inline -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.5 (GNU/Linux) iD8DBQFB3n+FipBneRiAKDwRAtanAKC37/1Yr3YpZhawq20wY5uHHP6UegCgjpdr KP+RVq3gmHwUY/Yi00+nQ9I= =+sEo -END PGP SIGNATURE- --OqZxW6Yu4sgZZmrd-- --- Received: (at 289139-done) by bugs.debian.org; 24 Jan 2005 08:59:07 + From [EMAIL PROTECTED] Mon Jan 24 00:59:07 2005 Return-path: [EMAIL PROTECTED] Received: from mx4.informatik.uni-tuebingen.de [134.2.12.29] by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1Ct03u-0003Kg-00; Mon, 24 Jan 2005 00:59:07 -0800 Received: from localhost (loopback [127.0.0.1]) by mx4.informatik.uni-tuebingen.de (Postfix) with ESMTP id EE9331401 for [EMAIL PROTECTED]; Mon, 24 Jan 2005 09:58:35 +0100 (NFT) Received: from mx4.informatik.uni-tuebingen.de ([127.0.0.1]) by localhost (mx4 [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 35732-04 for [EMAIL PROTECTED]; Mon, 24 Jan 2005 09:58:35 +0100 (NFT) Received: from localhost.localdomain (semeai.Informatik.Uni-Tuebingen.De [134.2.15.66]) by mx4.informatik.uni-tuebingen.de (Postfix) with ESMTP id 800A01400 for [EMAIL PROTECTED]; Mon, 24 Jan 2005 09:58:35 +0100 (NFT) Received: from mrvn by localhost.localdomain with
Bug#291600: Bug #291600: gibraltar-bootcd is potentially undistributable
Hi, going to the RC bugs I saw this one and having worked on other packages that reuse debs or sources I have some things to add: 1. You can not assume /etc/apt/sources.list or even network access is functional inside the buildd chroot. You may not use the outside network at all during build. This is an unwritten policy. 2. You can not include (GPL) binaries in a deb without including the source in the source package. Your gibraltar-bootcd deb can stay around for a long time while the sources/debs you used get updated. That would mean that you have binaries without source in your deb. That is a violation of the DFSG for one thing and a violation of the binaries licences. Compare with amd64-libs, which is the latest such package being added to debian. ftp-master insisted on amd64-libs having sources included. MfG Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#291952: ia32-libs: Source package does not include source
Package: ia32-libs Version: 0.7 Severity: serious Justification: DFSG ia32-libs contains a bunch of deb files that might have version skews compared to the debian archive. Any such version skew results in a deb without source in clear violation of the DFSG and the packages license. I know it sucks to include all those sources but for amd64-libs ftp-master insisted on including it and for the same reason ia32-libs must too. MfG Goswin -- System Information: Debian Release: 3.1 Architecture: amd64 (x86_64) Kernel: Linux 2.6.8-frosties-1 Locale: LANG=en_US, LC_CTYPE=en_US -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#288464: Patch for pytables 0.9.1-1.1 NMU
Hi Luk, Thanks for your help in fixing those bugs. The fact is that they were addressed some time ago, and I was waiting for my sponsor (Daniel Bungert) to upload the new version. However, Daniel seems to be rather busy during the last times, so, if you are willing to upload yourself the new version, I'll be more than happy. You can find the new maintainer version at: http://pytables.sourceforge.net/Debian/ Cheers, A Diumenge 23 Gener 2005 22:55, Luk Claes va escriure: Hi I intend to NMU pytables to fix the libucl0 bug (by rebuilding) and the FTBFS (amd64/gcc-4.0) bug. You can upload a version yourself in the coming 7 days to fix the bug(s) as the NMU is uploaded to the DELAYED queue in 7-day. Cheers Luk -- qo Francesc Altet http://www.carabos.com/ V V Cárabos Coop. V. Enjoy Data
Bug#291545: tetex-bin: initex fails to generate some etmf files
Margarita Manterola [EMAIL PROTECTED] wrote: Hola Frank Küster! This is a really low value. For debugging, we need some more information. Can you please send us the output of the following commands: grep trie_size /etc/texmf/texmf.d/95NonPath.cnf [EMAIL PROTECTED]:~$ grep trie_size /etc/texmf/texmf.d/95NonPath.cnf % `ssup_trie_opcode' and `ssup_trie_size' in tex.ch (and rebuild TeX); trie_size = 262000 This is the unchanged value, as the file is included in the deb. So far, so good. grep trie_size /etc/texmf/texmf.cnf [EMAIL PROTECTED]:~$ grep trie_size /etc/texmf/texmf.cnf % `ssup_trie_opcode' and `ssup_trie_size' in tex.ch (and rebuild TeX); trie_size = 64000 texmf.cnf is created from files in /etc/texmf/texmf.d/, and therefore in an ideal world the value should be the same here. It is not, and this indicates either a bug, or that someone has edited the file - which is allowed, of course, but done on one's own risk. If that someone is an other package, as you suspect, this would be a grave bug, of course, and it would be really good if we could find this out. To find out what happened, please do the following, and send us the output: grep texmf.cnf /var/lib/ucf/hashfile md5sum /etc/texmf/texmf.cnf update-texmf -d If it asks you about changes made, you can look at the diff, but for debugging purposes, you should choose not to accept the maintainer changes, as suggested, but keep your installed version. After this do again: grep trie_size /etc/texmf/texmf.cnf grep texmf.cnf /var/lib/ucf/hashfile md5sum /etc/texmf/texmf.cnf If after the call to update-texmf the trie_size in texmf.cnf is still not 262000, please go on like this: Open /etc/texmf/texmf.d/95NonPatch.cnf in an editor and change an arbitrary comment. For example, go to the line before the trie_size setting and write something like % this must be at least 262000 After this, run update-texmf -d again. Now it should really display a dialog: It should tell you that there are changes that need to merged, and offers you to show the differences. Please look at the differences. If the only difference is the comment you added and the setting of trie_size, please accept the maintainer changes - this means the changes that come from the files in texmf.d. If there are more differences, things are more difficult. It might be that you or some other admin on that machine edited the file, and the changes actually make sense - then it would be advisable to also make the changes in the respective file in texmf.d - then update-texmf will no longer ask you. If you don't have any idea where those changes might come from, it might in fact be that some other package did these changes in a wrong way. Please send us the diff - you need not copypaste it. Instead, simply chose to _not_ accept the maintainer changes, and look at the filename that is displayed in the end, something like Keeping temporary file /tmp/tmp.rB9Inp/texmfXko4iou You can then make a diff between this file and /etc/texmf/texmf.cnf. Regards, Frank -- Frank Küster Inst. f. Biochemie der Univ. Zürich Debian Developer
Bug#290733: torsmo bug
Hi, I wanted to track this bug but can't reproduce it on amd64: Linux frosties 2.6.8-frosties-1 #2 Sun Oct 3 22:06:03 CEST 2004 x86_64 GNU/Linux Get:1 http://debian-amd64.alioth.debian.org testing/main torsmo 0.18-1 [37.7kB] MfG Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#290685: vcdimager: Patch
Package: vcdimager
Version: 0.7.20-2
Followup-For: Bug #290685
Hi,
attached is a patch to make vcdimager compile again and thereby
makeing it installable again.
Compile tested on amd64 sarge and a clean i386 sid chroot.
MfG
Goswin
-- System Information:
Debian Release: 3.1
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.8-frosties-1
Locale: LANG=en_US, LC_CTYPE=en_US
Versions of packages vcdimager depends on:
ii libc6 2.3.2.ds1-19.0.0.2.pure64 GNU C Library: Shared libraries an
ii libcdio0 0.68-2library to read and control CD-ROM
ii libiso9660-0 0.68-2library to work with ISO9660 files
ii libpopt0 1.7-5 lib for parsing cmdline parameters
ii libvcdinfo00.7.20-2 library to extract information fro
ii libxml22.6.11-5 GNOME XML library
ii zlib1g 1:1.2.2-4 compression library - runtime
-- no debconf information
diff -u vcdimager-0.7.20/debian/changelog vcdimager-0.7.20/debian/changelog
--- vcdimager-0.7.20/debian/changelog
+++ vcdimager-0.7.20/debian/changelog
@@ -1,3 +1,14 @@
+vcdimager (0.7.20-2.1) unstable; urgency=low
+
+ * NMU by Goswin von Brederlow to fix FTBFS and uninstallable bug
+(Closes: #290685)
++ Fix type mismatch in image.c
++ Fix for libcdio API changes
++ Fix test/vcd20_nrg3.right to updated info string
++ Fix test/Makefile.am to clean *.nrg files
+
+ -- Goswin von Brederlow [EMAIL PROTECTED] Mon, 24 Jan 2004 11:06:15 +0200
+
vcdimager (0.7.20-2) unstable; urgency=low
* Fix pkg-config description for libvcdinfo since libvcd is a private
only in patch2:
unchanged:
--- vcdimager-0.7.20.orig/test/Makefile.am
+++ vcdimager-0.7.20/test/Makefile.am
@@ -42,4 +42,4 @@
XFAIL_TESTS = testassert
-MOSTLYCLEANFILES = *.bin *.cue core.* *.dump
+MOSTLYCLEANFILES = *.bin *.cue core.* *.dump *.nrg
only in patch2:
unchanged:
--- vcdimager-0.7.20.orig/test/Makefile.in
+++ vcdimager-0.7.20/test/Makefile.in
@@ -247,7 +247,7 @@
testassert
XFAIL_TESTS = testassert
-MOSTLYCLEANFILES = *.bin *.cue core.* *.dump
+MOSTLYCLEANFILES = *.bin *.cue core.* *.dump *.nrg
all: all-am
.SUFFIXES:
only in patch2:
unchanged:
--- vcdimager-0.7.20.orig/test/vcd20_nrg3.right
+++ vcdimager-0.7.20/test/vcd20_nrg3.right
@@ -1,4 +1,4 @@
- INFO: detected v50 (32bit offsets) NRG magic
+ INFO: detected Nero version 5.0 (32-bit offsets) NRG magic
INFO: SAO type image (ETNF) detected
---
VCD/INFO.VCD
only in patch2:
unchanged:
--- vcdimager-0.7.20.orig/lib/image.c
+++ vcdimager-0.7.20/lib/image.c
@@ -76,7 +76,7 @@
}
int
-vcd_image_sink_write (VcdImageSink *obj, void *buf, uint32_t lsn)
+vcd_image_sink_write (VcdImageSink *obj, void *buf, lsn_t lsn)
{
vcd_assert (obj != NULL);
only in patch2:
unchanged:
--- vcdimager-0.7.20.orig/lib/info.c
+++ vcdimager-0.7.20/lib/info.c
@@ -1806,7 +1806,7 @@
}
if (obj-vcd_type == VCD_TYPE_SVCD || obj-vcd_type == VCD_TYPE_HQVCD) {
-statbuf = iso9660_fs_stat (obj-img, MPEGAV, true);
+statbuf = iso9660_fs_stat (obj-img, MPEGAV);
if (NULL != statbuf) {
vcd_warn (non compliant /MPEGAV folder detected!);
@@ -1814,7 +1814,7 @@
}
-statbuf = iso9660_fs_stat (obj-img, SVCD/TRACKS.SVD;1, true);
+statbuf = iso9660_fs_stat (obj-img, SVCD/TRACKS.SVD;1);
if (NULL != statbuf) {
lsn_t lsn = statbuf-lsn;
if (statbuf-size != ISO_BLOCKSIZE)
@@ -1836,7 +1836,7 @@
iso9660_fs_readdir(img, EXT, true) and then scanning for
the files listed below.
*/
-statbuf = iso9660_fs_stat (img, EXT/PSD_X.VCD;1, true);
+statbuf = iso9660_fs_stat (img, EXT/PSD_X.VCD;1);
if (NULL != statbuf) {
lsn_t lsn= statbuf-lsn;
uint32_t secsize = statbuf-secsize;
@@ -1852,7 +1852,7 @@
return VCDINFO_OPEN_ERROR;
}
-statbuf = iso9660_fs_stat (img, EXT/LOT_X.VCD;1, true);
+statbuf = iso9660_fs_stat (img, EXT/LOT_X.VCD;1);
if (NULL != statbuf) {
lsn_t lsn= statbuf-lsn;
uint32_t secsize = statbuf-secsize;
@@ -1877,13 +1877,13 @@
iso9660_fs_readdir(img, SVCD, true) and then scanning for
the files listed below.
*/
-statbuf = iso9660_fs_stat (img, MPEGAV, true);
+statbuf = iso9660_fs_stat (img, MPEGAV);
if (NULL != statbuf) {
vcd_warn (non compliant /MPEGAV folder detected!);
free(statbuf);
}
-statbuf = iso9660_fs_stat (img, SVCD/TRACKS.SVD;1, true);
+statbuf = iso9660_fs_stat (img, SVCD/TRACKS.SVD;1);
if (NULL == statbuf)
vcd_warn (mandatory /SVCD/TRACKS.SVD not found!);
else {
@@ -1892,7 +1892,7 @@
free(statbuf);
}
-statbuf = iso9660_fs_stat (img, SVCD/SEARCH.DAT;1, true);
+statbuf = iso9660_fs_stat (img, SVCD/SEARCH.DAT;1);
if (NULL == statbuf)
vcd_warn
Processed: blootbot
Processing commands for [EMAIL PROTECTED]: package blootbot Ignoring bugs not assigned to: blootbot tag 228053 -patch Bug#228053: blootbot: Blootbot fails to connect to mysql database after installation and setup Tags were: pending patch upstream confirmed Tags removed: patch tag 228053 -pending Bug#228053: blootbot: Blootbot fails to connect to mysql database after installation and setup Tags were: pending upstream confirmed Tags removed: pending tag 117595 -pending Bug#117595: blootbot: incorrect reponse for news when bot is not in channel. Tags were: pending Tags removed: pending tag 205772 -pending Bug#205772: blootbot: Please switch to gettext-based debconf templates Tags were: pending patch Tags removed: pending tag 206733 -pending Bug#206733: blootbot: French translation of gettext debconf templates Tags were: pending l10n patch Tags removed: pending tag 212514 -pending Bug#212514: blootbot: Source contains CVS directory Tags were: pending confirmed upstream Tags removed: pending tag 244341 -pending Bug#244341: blootbot: New Upstream Release Tags were: pending Tags removed: pending noowner 228053 Bug#228053: blootbot: Blootbot fails to connect to mysql database after installation and setup Removed annotation that Bug was owned by Guilherme de S. Pastore [EMAIL PROTECTED]. noowner 244341 Bug#244341: blootbot: New Upstream Release Removed annotation that Bug was owned by Guilherme de S. Pastore [EMAIL PROTECTED]. thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: Fixed in NMU of viewcvs 0.9.2+cvs.1.0.dev.2004.07.28-1.4
Processing commands for [EMAIL PROTECTED]: tag 241832 + fixed Bug#241832: viewcvs: Updated Japanese po-debconf template translation (ja.po) Tags were: l10n patch Tags added: fixed tag 244514 + fixed Bug#244514: Update of the french debconf translation Tags were: l10n patch Tags added: fixed tag 289466 + fixed Bug#289466: viewcvs: breaks config file on upgrade Tags were: patch Tags added: fixed tag 289639 + fixed Bug#289639: [INTL:nl] New po-debconf translation in Dutch for viewcvs. Tags were: l10n patch Tags added: fixed quit Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: tagging 289923
Processing commands for [EMAIL PROTECTED]: tags 289923 + patch Bug#289923: vlc: FTBFS on 64 bit arches: error: call of overloaded `wxComboBox(wxPanel*, anonymous enum, const wchar_t[1], wxPoint, wxSize, int, NULL)' is ambiguous Tags were: sid Tags added: patch End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: tagging 290685
Processing commands for [EMAIL PROTECTED]: tags 290685 + patch Bug#290685: vcdimager: Package uninstallable Tags were: sid Tags added: patch 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#289923: vlc: Patch
Package: vlc
Followup-For: Bug #289923
Hi,
looking over this bug I don't think this is an change in the ABI of
wxWindows but rather a gcc update with stricter ansi c++ checking.
Attached is a patch that removes two default parameters each from the
ambigious calls resulting in g++ finding an unambigious one.
The patch compiles and runs (only divx/avi file tested) fine on amd64.
MfG
Goswin
-- System Information:
Debian Release: 3.1
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.8-frosties-1
Locale: LANG=en_US, LC_CTYPE=en_US
diff -u vlc-0.8.1/debian/changelog vlc-0.8.1/debian/changelog
--- vlc-0.8.1/debian/changelog
+++ vlc-0.8.1/debian/changelog
@@ -1,3 +1,11 @@
+vlc (0.8.1-3.1) unstable; urgency=low
+
+ * NMU by Goswin von Brederlow (Closes: #289923)
++ debian/patches/30_ambiguity.dpatch: Remove default parameter to
+ avoid ambiguity
+
+ -- Goswin von Brederlow [EMAIL PROTECTED] Mon, 24 Jan 2005 11:25:02 +0100
+
vlc (0.8.1-3) unstable; urgency=low
* debian/control:
only in patch2:
unchanged:
--- vlc-0.8.1.orig/debian/patches/00list
+++ vlc-0.8.1/debian/patches/00list
@@ -1,2 +1,3 @@
20_ffmpeg
20_interfaces
+30_ambiguity
only in patch2:
unchanged:
--- vlc-0.8.1.orig/debian/patches/30_ambiguity.dpatch
+++ vlc-0.8.1/debian/patches/30_ambiguity.dpatch
@@ -0,0 +1,57 @@
+#! /bin/sh -e
+## 30_ambiguity.dpatch by [EMAIL PROTECTED]
+##
+## All lines beginning with `## DP:' are a description of the patch.
+## DP: Remove default parameter to avoid ambiguity
+
+if [ $# -lt 1 ]; then
+echo `basename $0`: script expects -patch|-unpatch as argument 2
+exit 1
+fi
+
+[ -f debian/patches/00patch-opts ] . debian/patches/00patch-opts
+patch_opts=${patch_opts:--f --no-backup-if-mismatch} ${2:+-d $2}
+
+case $1 in
+-patch) patch -p1 ${patch_opts} $0;;
+-unpatch) patch -R -p1 ${patch_opts} $0;;
+*)
+echo `basename $0`: script expects -patch|-unpatch as argument 2
+exit 1;;
+esac
+
+exit 0
+
[EMAIL PROTECTED]@
+diff -Nurd vlc-0.8.1.orig vlc-0.8.1
+--- vlc-0.8.1.orig/modules/gui/wxwindows/streamout.cpp
vlc-0.8.1/modules/gui/wxwindows/streamout.cpp
+@@ -168,7 +168,7 @@
+ wxStaticText *mrl_label = new wxStaticText( panel, -1,
+ wxU(_(Destination
Target:)));
+ mrl_combo = new wxComboBox( panel, MRL_Event, wxT(),
+-wxPoint(20,25), wxSize(120, -1), 0, NULL );
++wxPoint(20,25), wxSize(120, -1));
+ mrl_combo-SetToolTip( wxU(_(You can use this field directly by typing
+ the full MRL you want to open.\nAlternatively, the field will be
+ filled automatically when you use the controls below)) );
+@@ -452,7 +452,7 @@
+ subpanel_sizer = new wxFlexGridSizer( 3, 2, 20 );
+ label = new wxStaticText( access_subpanels[1], -1, wxU(_(Filename)) );
+ file_combo = new wxComboBox( access_subpanels[1], FileName_Event, wxT(),
+- wxPoint(20,25), wxSize(200, -1), 0, NULL );
++ wxPoint(20,25), wxSize(200, -1) );
+ wxButton *browse_button = new wxButton( access_subpanels[1],
+ FileBrowse_Event, wxU(_(Browse...)) );
+ subpanel_sizer-Add( label, 0, wxALIGN_RIGHT | wxALIGN_CENTER_VERTICAL );
+--- vlc-0.8.1.orig/modules/gui/wxwindows/subtitles.cpp
vlc-0.8.1/modules/gui/wxwindows/subtitles.cpp
+@@ -85,7 +85,7 @@
+ char *psz_subsfile = config_GetPsz( p_intf, sub-file );
+ if( !psz_subsfile ) psz_subsfile = strdup();
+ file_combo = new wxComboBox( panel, -1, wxL2U(psz_subsfile),
+- wxPoint(20,25), wxSize(300, -1), 0, NULL );
++ wxPoint(20,25), wxSize(300, -1));
+ if( psz_subsfile ) free( psz_subsfile );
+ wxButton *browse_button = new wxButton( panel, FileBrowse_Event,
+ wxU(_(Browse...)) );
Bug#286905: perl-modules: File::Path::rmtree makes setuid
On Wed, Jan 12, 2005 at 05:02:41PM -0500, Aaron Sherman wrote: [p5p:] If anyone had a cleaner (and cross-platform) fix, I'd love to hear of it. Well, certainly relying on rm (and you assumed a -v option which, AFAIK implies GNU rm specifically) is right out. I'm sure others will say the same. Sure, it was proposed as a quick hack for the Debian package, where it is safe to assume /bin/rm is from GNU coreutils. If it weren't for the requirement to retain the current API (returning the number of deletions, and verbose output) then a thin wrapper around system 'rm', '-rf', @paths would suffix for POSIX systems. Quick fix? Reduce the race by making any changes just before and just after an operation, not in preparation for a whole directory. Now you still have a problem, but a smaller one. A race is a race, no matter how small the window. --bod -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#291979: zope-exuserfolder: NEWS.Debian is not in binary package
On Mon, Jan 24, 2005 at 01:26:03PM +0100, Andreas Tille wrote: zope-exuserfolder version 0.50 is incompatible to verison 0.20 as it is mentioned in #284572. This is solved by an explanation what to do in NEWS.Debian. Unfortunately exactly this file is not contained in the binary package which in consequence does not inform the local administrator about the broken installation. This is a grave bug because it leaves the system unusable. Hi Andreas, thanks for pointing this out: I've missed it in debian/rules. I'll upload the fixed packages ASAP. Thanks, -- Fabio Tranchitella http://www.kobold.it Studio Tranchitella Assoc. Professionale http://www.tranchitella.it _ 1024D/7F961564, fpr 5465 6E69 E559 6466 BF3D 9F01 2BF8 EE2B 7F96 1564 signature.asc Description: Digital signature
Processed: reopen 284572
Processing commands for [EMAIL PROTECTED]: reopen 284572 Bug#284572: zope-exuserfolder: exUserFolder 0.50 breaks existing installations Bug reopened, originator not changed. severity 284572 grave Bug#284572: zope-exuserfolder: exUserFolder 0.50 breaks existing installations Severity set to `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#290733: torsmo bug
On Mon, Jan 24, 2005 at 10:14:39AM +0100, Goswin von Brederlow wrote: Hi, I wanted to track this bug but can't reproduce it on amd64: Right. I've been working with the submitter without much success. I asked for a shell account but that wasn't a possibility. Coredumps all indicate a stack smash. And the strace indicates some problem during initialization, before the call to init_X11. I've given the submitter debugging instructions, involving a gdb trap on SIGFPE (though it will probably just show stack damage), and also the old stick-a-printf-after-reading-everything-in. Maybe there are uninitialized variables, or something.. I was looking for 2.4isms (like /proc/meminfo), but there appear to be 2.6isms instead.. Note that this is a sid-only bug. Justin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#283690: segfault in /etc/init.d/console-screen.sh
Hi Martin, You wrote: BTW: I'm running loadkeys from an initrd beforehand, that's why this is no critical bug for me. Keyboard layout is already fine when the console startup scripts run and fail. May that be the cause of this bug? As an outsider to this package I suppose that's a possibility, and I would like to see if this helps reproduce the problem. Can you tell us more about your initrd config? Thanks, -- Steve Langasek postmodern programmer signature.asc Description: Digital signature
Processed: Fixed in NMU of devilspie 0.8-2
Processing commands for [EMAIL PROTECTED]: tag 291894 + fixed Bug#291894: Uninstallable on i386 Tags were: sid Tags added: fixed quit Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#291993: RM: kissme -- upstream unable to maintain compatibility with classpath library
Package: ftp.debian.org Severity: grave Justification: renders package unusable The classpath library is under development and from time to time makes changes that require the JVMs using the library to adapt to a new API. kissme is not being actively developed and thus has fallen behind the changes in classpath. kissme is not used in Debian by any other package and it is unlikely that it is used by any Debian users. There are other free JVMs that use the classpath library, that are being actively developed/maintained and that are packaged for Debian (see jamvm and sablevm) John Leuner -- System Information: Debian Release: 3.1 APT prefers testing APT policy: (650, 'testing'), (600, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.8 Locale: LANG=en_ZA, LC_CTYPE=en_ZA (charmap=ISO-8859-1) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#292002: Decrypt::makeFileKey2() Buffer Overflow
Package: kpdf Version: 3.x Severity: grave Tags: security patch TITLE: KOffice Decrypt::makeFileKey2() Buffer Overflow SECUNIA ADVISORY ID: SA13934 VERIFY ADVISORY: http://secunia.com/advisories/13934/ CRITICAL: Highly critical IMPACT: System access WHERE: From remote SOFTWARE: KOffice 1.x http://secunia.com/product/4155/ DESCRIPTION: A vulnerability has been reported in KOffice, which can be exploited by malicious people to compromise a user's system. For more information: SA13903 The vulnerability has been reported in versions 1.3 through 1.3.5. SOLUTION: Apply patch. KOffice 1.3.5: ftp://ftp.kde.org/pub/kde/security_patches/post-1.3.5-koffice.diff ORIGINAL ADVISORY: http://www.kde.org/info/security/advisory-20050120-1.txt OTHER REFERENCES: SA13903: http://secunia.com/advisories/13903/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#291545: tetex-bin: initex fails to generate some etmf files
Margarita Manterola [EMAIL PROTECTED] schrieb: Hola Frank Küster! To find out what happened, please do the following, and send us the output: grep texmf.cnf /var/lib/ucf/hashfile 2150a9c617c9c8f221dcb152bd9f34d2 /etc/texmf/texmf.cnf md5sum /etc/texmf/texmf.cnf bde0d80810778ec19464ef7ad0004b35 /etc/texmf/texmf.cnf The md5sum registered with ucf and the actual md5sum differ. This shows that the file has been changed directly (instead of using the preferred way, namely to edit or add files in /etc/texmf/texmf.d/. If it asks you about changes made, you can look at the diff, but for debugging purposes, you should choose not to accept the maintainer changes, as suggested, but keep your installed version. After this do again: It asked nothing. I don't know if that's good or bad. That is good - it is what is expected, since there were no changes to the files in texmf.d since the last run in postinst. ucf remembers that you wanted the file to be different from what is generated from this particular combination of files in texmf.d. It will only ask and eventually change things if the files in texmf.d change. grep trie_size /etc/texmf/texmf.cnf % `ssup_trie_opcode' and `ssup_trie_size' in tex.ch (and rebuild TeX); trie_size = 64000 Still too low, this is consistent. grep texmf.cnf /var/lib/ucf/hashfile 2150a9c617c9c8f221dcb152bd9f34d2 /etc/texmf/texmf.cnf md5sum /etc/texmf/texmf.cnf bde0d80810778ec19464ef7ad0004b35 /etc/texmf/texmf.cnf Nothing changed - this is consistent, too. If after the call to update-texmf the trie_size in texmf.cnf is still not 262000, please go on like this: Open /etc/texmf/texmf.d/95NonPatch.cnf in an editor and change an arbitrary comment. Ok, I assume the file is 95NonPath.cnf. This is interesting, look: [EMAIL PROTECTED]:~$ ls /etc/texmf/texmf.d/ 05TeXMF.cnf 55Fonts.cnf 85Misc.cnf.dpkg-old 05TeXMF.cnf.dpkg-old 65BibTeX.cnf 90TeXDoc.cnf 15Plain.cnf 75DviPS.cnf 95NonPath.cnf 45TeXinputs.cnf 75DviPS.cnf.dpkg-old 95NonPath.cnf.dpkg-old 45TeXinputs.cnf.dpkg-old 85Misc.cnf So, at some point these files where changed and I assume I chose install the new maintainer version, but the .dpkg-old files are still there. Yes, this is usually done when dpkg has to ask - either the dpkg-old files (your old versions that differed from the old package versions), or the dpkg-new files (the new ones from the package, when you chose to keep your old ones that differed from the old package's files) stay around. And then: [EMAIL PROTECTED]:~$ grep trie_size /etc/texmf/texmf.d/95NonPath.cnf trie_size = 262000 [EMAIL PROTECTED]:~$ grep trie_size /etc/texmf/texmf.d/95NonPath.cnf.dpkg-old trie_size = 64000 So, for some reason it's using the old one instead of the new one. I'll keep going with your instructions, anyway. I suspect the following: You (or some buggy package) had made changes to some of the files in texmf.d. When the upgrade came, the first thing was that dpkg asked whether to take the new ones, or the old ones which were changed from the old packages's versions. You told it to install the new ones (and dpkg left the dpkg-old files around, for reference). After that, texmf.cnf was created newly from the updated files in texmf.d. It could be that for some reason you chose here to keep the old version of texmf.cnf (reflecting the old state of the files in texmf.d, with local changes). For example, go to the line before the trie_size setting and write something like % this must be at least 262000 After this, run update-texmf -d again. Now it should really display a dialog: It should tell you that there are changes that need to merged, and offers you to show the differences. Please look at the differences. The differences are quite a lot. I don't really get it, it didn't tell me anything before, and now it has an awful lot of differences, when I just changed one line. Quite magic, not? Actually the differences were always there, but update-texmf (through the ucf utility) knew that you wanted it that way. Now there is a third version: First the one you kept (registered by update-texmf as wanted), second the one that update-texmf always tried to generate previously (registered as unwanted), and third the one update-texmf tried to generate this time (not registered). The latter two only differ in the added comment, but update-texmf doesn't know about many differences or small differences. It just noticed that there was a third version that it didn't know about yet, and now it starts asking; and what it shows are the differences between the old used version (previously wanted) and the newly generated one (unregistered). Ok, I'm attaching the diff file. I hope you can find a solution to the mistery. Yes, this tells me that I was right. I do not know for sure to which version the dpkg-old files actually belong, but from the comments
Bug#291709: reassign to libmisdn-dev
Hi, It appears that libmisdn-dev does not provide a shared library, so I think this should be reassigned there. The API/ABI is not yet stable, so there is a static library that should also be compiled with -fPIC, but only in the most recent version, which chan_misdn should also build-depend on (I have successfully built the package on hppa, where non-PIC libraries also fail. A new version of chan_misdn is out, and I'll see whether I can manage to update the package today, but I fear this FTBFS is caused by the version of libmisdnnet-dev not being recent enough on the autobuilder. Simon signature.asc Description: OpenPGP digital signature
Bug#291545: tetex-bin: initex fails to generate some etmf files
Hola Frank Küster! I suspect the following: You (or some buggy package) had made changes to some of the files in texmf.d. When the upgrade came, the first thing was that dpkg asked whether to take the new ones, or the old ones which were changed from the old packages's versions. You told it to install the new ones (and dpkg left the dpkg-old files around, for reference). After that, texmf.cnf was created newly from the updated files in texmf.d. It could be that for some reason you chose here to keep the old version of texmf.cnf (reflecting the old state of the files in texmf.d, with local changes). Ok, this sounds plausible and understandable. I usually answer install the maintainer's version to all questions of software that I know I didn't modify. But since this was a major upgrade, it's perfectly possible that I made a mistake when the second question was asked. Now, the fact is that it asked me the same question twice (now that the mistery is solved, I have the sensation that I remember looking at the diff and thinking isn't this the same diff I saw before?), therefore causing my making the mistake of not accepting it twice. Is there a way to prevent this? Some way of preseeding update-texmf so that it doesn't happen? Yes, this tells me that I was right. I do not know for sure to which version the dpkg-old files actually belong, but from the comments update-texmf put in texmf.cnf (or rather, didn't put) it seems to me as if the texmf.cnf you were using was the one that was generated for tetex-bin_1.0.7 in woody. Yes, that's really probable. This machine used to be woody, not so long ago, and it is only updated once in a very long while, since it's a thin-client server. So I think your guess is correct. So, in order to fix your system, do the following: - make an arbitrary comment change in 95NonPath.cnf (e.g. remove the line you just added, or whatever) - run update-texmf, and this time agree to install the package maintainer's version. After this, you should be able to run dpkg --configure -a or dpkg-reconfigure tetex-bin without problems. If this is true, I'm happy again, please don't forget to tell us. Ok, I've done this and it has worked. Now, this bug was not a bug, but a human's (namely, me) fault, yet I feel that something should be done to prevent this from happening again, don't you think? Thanks a lot for all the help -- Besos, Maggie. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#264678: marked as done (jmk: FTBFS: compile error)
Your message dated Mon, 24 Jan 2005 09:47:17 -0500 with message-id [EMAIL PROTECTED] and subject line Bug#264678: fixed in jmk 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) -- Received: (at submit) by bugs.debian.org; 9 Aug 2004 21:53:49 + From [EMAIL PROTECTED] Mon Aug 09 14:53:49 2004 Return-path: [EMAIL PROTECTED] Received: from pd9e7e98b.dip.t-dialin.net (stigge.org) [217.231.233.139] by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1BuI5V-00080q-00; Mon, 09 Aug 2004 14:53:49 -0700 Received: (qmail 16955 invoked from network); 9 Aug 2004 21:53:47 - Received: from unknown (HELO atari.stigge.org) (192.168.1.99) by sbo.stigge.org with SMTP; 9 Aug 2004 21:53:47 - Received: by atari.stigge.org (Postfix, from userid 1001) id D2FD3100442B0; Mon, 9 Aug 2004 23:53:46 +0200 (CEST) Content-Type: text/plain; charset=us-ascii MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: Roland Stigge [EMAIL PROTECTED] To: Debian Bug Tracking System [EMAIL PROTECTED] Subject: jmk: FTBFS: compile error X-Mailer: reportbug 2.64 Date: Mon, 09 Aug 2004 23:53:46 +0200 Message-Id: [EMAIL PROTECTED] Delivered-To: [EMAIL PROTECTED] X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25 (1.212-2003-09-23-exp) on spohr.debian.org X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE autolearn=no version=2.60-bugs.debian.org_2004_03_25 X-Spam-Level: Package: jmk Version: 1.5-2 Severity: serious Hi, trying to build the package, I got: = [...] dpkg-source: building jmk using existing jmk_1.5.orig.tar.gz dpkg-source: building jmk in jmk_1.5-2.diff.gz dpkg-source: building jmk in jmk_1.5-2.dsc debian/rules build dh_testdir # Add here commands to configure the package. touch configure-stamp dh_testdir # Add here commands to compile the package. /usr/bin/make make[1]: Entering directory `/tmp/buildd/jmk-1.5' jikes -classpath /usr/share/kissme/classpath/:. edu/neu/ccs/jmk/*.java Issued 1 semantic warning compiling edu/neu/ccs/jmk/ClassOperator.java: 40. private final String name = forname; ^--^ *** Semantic Warning: Final field name is initialized with a constant expressi on and could be made static to save space. Issued 1 semantic warning compiling edu/neu/ccs/jmk/Rule.java: 42. boolean made = false; ^--^ *** Semantic Warning: Local made shadows a field of the same name in edu.neu. ccs.jmk.Rule. jikes: tuple.h:429: T ConvertibleArrayT::Next() [with T = MethodSymbol*]: Ass ertion `! array' failed. Aborted make[1]: *** [build] Error 134 make[1]: Leaving directory `/tmp/buildd/jmk-1.5' make: *** [build-stamp] Error 2 = Thanks for considering. bye, Roland -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.7 Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (ignored: LC_ALL set to en_GB.UTF-8) --- Received: (at 264678-close) by bugs.debian.org; 24 Jan 2005 14:53:02 + From [EMAIL PROTECTED] Mon Jan 24 06:53:02 2005 Return-path: [EMAIL PROTECTED] Received: from newraff.debian.org [208.185.25.31] (mail) by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1Ct5aP-0004rK-00; Mon, 24 Jan 2005 06:53:02 -0800 Received: from katie by newraff.debian.org with local (Exim 3.35 1 (Debian)) id 1Ct5Ur-0006nN-00; Mon, 24 Jan 2005 09:47:17 -0500 From: John Leuner [EMAIL PROTECTED] To: [EMAIL PROTECTED] X-Katie: $Revision: 1.55 $ Subject: Bug#264678: fixed in jmk 1.5-3 Message-Id: [EMAIL PROTECTED] Sender: Archive Administrator [EMAIL PROTECTED] Date: Mon, 24 Jan 2005 09:47:17 -0500 Delivered-To: [EMAIL PROTECTED] X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 (1.212-2003-09-23-exp) on spohr.debian.org X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER autolearn=no version=2.60-bugs.debian.org_2005_01_02 X-Spam-Level: Source: jmk Source-Version: 1.5-3 We believe that the bug you reported is fixed in the latest version of jmk, which is due to be installed in the Debian FTP archive: jmk_1.5-3.diff.gz to pool/main/j/jmk/jmk_1.5-3.diff.gz jmk_1.5-3.dsc to pool/main/j/jmk/jmk_1.5-3.dsc jmk_1.5-3_all.deb to
Bug#291776: marked as done (gnunet: Should depend on libltdl3.)
Your message dated Mon, 24 Jan 2005 09:47:10 -0500 with message-id [EMAIL PROTECTED] and subject line Bug#291776: fixed in gnunet 0.6.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) -- Received: (at submit) by bugs.debian.org; 23 Jan 2005 02:20:09 + From [EMAIL PROTECTED] Sat Jan 22 18:20:09 2005 Return-path: [EMAIL PROTECTED] Received: from p15163250.pureserver.info (arthur.pweis.com) [82.165.43.81] by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1CsXMG-0002Pg-00; Sat, 22 Jan 2005 18:20:09 -0800 Received: from pweis by arthur.pweis.com with local (Exim 4.34 #1 (Debian)) id 1CsXM5-00081M-Jq; Sun, 23 Jan 2005 03:19:57 +0100 Date: Sun, 23 Jan 2005 03:19:57 +0100 From: Philipp Weis [EMAIL PROTECTED] To: Debian Bug Tracking System [EMAIL PROTECTED] Subject: gnunet: Should depend on libltdl3. Message-ID: [EMAIL PROTECTED] Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Reportbug-Version: 3.2 User-Agent: Mutt/1.5.6+20040907i Delivered-To: [EMAIL PROTECTED] X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 (1.212-2003-09-23-exp) on spohr.debian.org X-Spam-Status: No, hits=-7.0 required=4.0 tests=BAYES_00,DATING,HAS_PACKAGE autolearn=no version=2.60-bugs.debian.org_2005_01_02 X-Spam-Level: Package: gnunet Version: 0.6.5-2 Severity: serious Justification: Policy 3.5 For some reason, I did not have libextractor installed. Libextractor depends on libltdl3, but gnunet does not. Therefore I did not have libextractor installed as well. Updating gnunet leads to the following error messages. Setting up gnunet (0.6.5-2) ... Migrating previous GNUnet data (gnunet-update) gnunet-update: error while loading shared libraries: libltdl.so.3: cannot open shared object file: No such file or directory dpkg: error processing gnunet (--configure): subprocess post-installation script returned error exit status 127 Errors were encountered while processing: gnunet E: Sub-process /usr/bin/dpkg returned an error code (1) Ack! Something bad happened while installing packages. Trying to recover: Setting up gnunet (0.6.5-2) ... Migrating previous GNUnet data (gnunet-update) gnunet-update: error while loading shared libraries: libltdl.so.3: cannot open shared object file: No such file or directory dpkg: error processing gnunet (--configure): subprocess post-installation script returned error exit status 127 Installing libextractor solved the problem, but I think installing libltdl3 alone would have solved it as well. -- System Information: Debian Release: 3.1 APT prefers testing APT policy: (600, 'testing'), (550, 'experimental'), (550, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.9 Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) Versions of packages gnunet depends on: ii debconf 1.4.30.11 Debian configuration management sy ii libdb4.3 4.3.21-11 Berkeley v4.3 Database Libraries [ ii libgcrypt11 1.2.0-4LGPL Crypto library - runtime libr ii libgmp3 4.1.4-5Multiprecision arithmetic library ii libgpg-error0 1.0-1 library for common error values an -- debconf information: * gnunet/gnunet_user: gnunet * gnunet/gnunet_group: gnunet gnunet/failed: * gnunet/launch_at_startup: true * gnunet/warning: -- Philipp Weis[EMAIL PROTECTED]http://pweis.com/ --- Received: (at 291776-close) by bugs.debian.org; 24 Jan 2005 14:54:10 + From [EMAIL PROTECTED] Mon Jan 24 06:54:10 2005 Return-path: [EMAIL PROTECTED] Received: from newraff.debian.org [208.185.25.31] (mail) by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1Ct5bW-0005nD-00; Mon, 24 Jan 2005 06:54:10 -0800 Received: from katie by newraff.debian.org with local (Exim 3.35 1 (Debian)) id 1Ct5Uk-0006mm-00; Mon, 24 Jan 2005 09:47:10 -0500 From: Arnaud Kyheng [EMAIL PROTECTED] To: [EMAIL PROTECTED] X-Katie: $Revision: 1.55 $ Subject: Bug#291776: fixed in gnunet 0.6.5-3 Message-Id: [EMAIL PROTECTED] Sender: Archive Administrator [EMAIL PROTECTED] Date: Mon, 24 Jan 2005 09:47:10 -0500 Delivered-To: [EMAIL PROTECTED] X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 (1.212-2003-09-23-exp) on spohr.debian.org X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER autolearn=no
Bug#292002: marked as done (Decrypt::makeFileKey2() Buffer Overflow)
Your message dated Mon, 24 Jan 2005 11:48:08 -0300 with message-id [EMAIL PROTECTED] and subject line 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) -- Received: (at submit) by bugs.debian.org; 24 Jan 2005 14:16:50 + From [EMAIL PROTECTED] Mon Jan 24 06:16:50 2005 Return-path: [EMAIL PROTECTED] Received: from mail.arcert.gov.ar [200.47.53.18] by spohr.debian.org with smtp (Exim 3.35 1 (Debian)) id 1Ct51N-0004zT-00; Mon, 24 Jan 2005 06:16:49 -0800 Received: (qmail 8446 invoked from network); 24 Jan 2005 14:16:44 - X-Scanned-By: ArCERT. Received: from unknown (HELO clementina.arcert.gov.ar) (arcert) by mail.arcert.gov.ar with SMTP; 24 Jan 2005 14:16:44 - Subject: Decrypt::makeFileKey2() Buffer Overflow From: Luciano Bello [EMAIL PROTECTED] To: Submit BTS [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Content-Type: text/plain Date: Mon, 24 Jan 2005 11:14:57 -0300 Message-Id: [EMAIL PROTECTED] Mime-Version: 1.0 X-Mailer: Evolution 2.0.3 Content-Transfer-Encoding: 7bit Delivered-To: [EMAIL PROTECTED] X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 (1.212-2003-09-23-exp) on spohr.debian.org X-Spam-Status: No, hits=-7.0 required=4.0 tests=BAYES_01,HAS_PACKAGE autolearn=no version=2.60-bugs.debian.org_2005_01_02 X-Spam-Level: Package: kpdf Version: 3.x Severity: grave Tags: security patch TITLE: KOffice Decrypt::makeFileKey2() Buffer Overflow SECUNIA ADVISORY ID: SA13934 VERIFY ADVISORY: http://secunia.com/advisories/13934/ CRITICAL: Highly critical IMPACT: System access WHERE: From remote SOFTWARE: KOffice 1.x http://secunia.com/product/4155/ DESCRIPTION: A vulnerability has been reported in KOffice, which can be exploited by malicious people to compromise a user's system. For more information: SA13903 The vulnerability has been reported in versions 1.3 through 1.3.5. SOLUTION: Apply patch. KOffice 1.3.5: ftp://ftp.kde.org/pub/kde/security_patches/post-1.3.5-koffice.diff ORIGINAL ADVISORY: http://www.kde.org/info/security/advisory-20050120-1.txt OTHER REFERENCES: SA13903: http://secunia.com/advisories/13903/ --- Received: (at 292002-done) by bugs.debian.org; 24 Jan 2005 14:50:03 + From [EMAIL PROTECTED] Mon Jan 24 06:50:02 2005 Return-path: [EMAIL PROTECTED] Received: from mail.arcert.gov.ar [200.47.53.18] by spohr.debian.org with smtp (Exim 3.35 1 (Debian)) id 1Ct5XW-00038h-00; Mon, 24 Jan 2005 06:50:02 -0800 Received: (qmail 9615 invoked from network); 24 Jan 2005 14:49:54 - X-Scanned-By: ArCERT. Received: from unknown (HELO clementina.arcert.gov.ar) (arcert) by mail.arcert.gov.ar with SMTP; 24 Jan 2005 14:49:53 - Subject: From: Luciano Bello [EMAIL PROTECTED] To: [EMAIL PROTECTED] Content-Type: text/plain Date: Mon, 24 Jan 2005 11:48:08 -0300 Message-Id: [EMAIL PROTECTED] Mime-Version: 1.0 X-Mailer: Evolution 2.0.3 Content-Transfer-Encoding: 7bit Delivered-To: [EMAIL PROTECTED] X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 (1.212-2003-09-23-exp) on spohr.debian.org X-Spam-Status: No, hits=-1.5 required=4.0 tests=BAYES_00,NOSUBJECT autolearn=no version=2.60-bugs.debian.org_2005_01_02 X-Spam-Level: It's done acording to http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=291245 Sorry -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#291545: tetex-bin: initex fails to generate some etmf files
severity 291545 normal retitle 291545 upgrade of files in texmf.d shows diff twice (plain ucf and update-texmf) stop Margarita Manterola [EMAIL PROTECTED] schrieb: Now, the fact is that it asked me the same question twice (now that the mistery is solved, I have the sensation that I remember looking at the diff and thinking isn't this the same diff I saw before?), therefore causing my making the mistake of not accepting it twice. Is there a way to prevent this? Some way of preseeding update-texmf so that it doesn't happen? Actually, I fear it is not possible. We *could* make things easy and straightforward: If we would put the generated texmf.cnf file into /var/lib/texmf, then only the files in texmf.d would be configuration files, and only there could a question come. By the way, the reason for all this is to enable other packages to add their own configuration to texmf.cnf, like e.g. jadetex does. However, the problem with this is that texmf.cnf is known as the configuration file for teTeX, it is referenced in many README files or tutorials, and, to make things worse, since it must always be possible for TeX to find it, users can find it with the same means: kpsewhich --format='web2c files' texmf.cnf /usr/share/texmf/web2c/texmf.cnf (actually you can use it without the --format stuff). This is why we have chosen to keept texmf.cnf in /etc/texmf, as a configuration file - people would have edited anyway. But this makes the double checking necessary. Now, this bug was not a bug, but a human's (namely, me) fault, yet I feel that something should be done to prevent this from happening again, don't you think? Yes, it would be good. I'll think it over, and keep the bug open under a different title, and with lower severity. Regards, Frank -- Frank Küster Inst. f. Biochemie der Univ. Zürich Debian Developer
Processed: Bug #289838 should not be RC
Processing commands for [EMAIL PROTECTED]: severity 289838 normal Bug#289838: postinst script unusable due to serious errors Severity set to `normal'. tags 289838 +help Bug#289838: postinst script unusable due to serious errors 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#292031: libhttpfetcher1: Fails to work on systems with newer glibc and kernel
Package: libhttpfetcher1
Version: 1.0.1-1.1
Severity: grave
Tags: patch
Justification: renders package unusable
The source for libhttpfetcher1 declares 'extern int errno' directly,
instead of using errno.h, which causes all programs using the library to fail
miserably on start on systems with a newer glibc, for thread reasons.
Enclosed is a simple patch to fix this problem:
diff -u http_fetcher-1.0.1/src/http_fetcher.c
http_fetcher-1.0.1-fixed/src/http_fetcher.c
--- http_fetcher-1.0.1/src/http_fetcher.c 2001-07-30 14:47:15.0
-0400
+++ http_fetcher-1.0.1-fixed/src/http_fetcher.c 2005-01-15 16:07:10.0
-0500
@@ -25,6 +25,7 @@
#include sys/types.h
#include sys/time.h
#include http_fetcher.h
+#include errno.h
/* Globals */
int timeout = DEFAULT_READ_TIMEOUT;
@@ -457,7 +458,6 @@
*/
const char *http_strerror()
{
- extern int errno;
extern int *sys_errlist[];
if(errorSource == ERRNO)
-- System Information:
Debian Release: 3.1
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.10
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Versions of packages libhttpfetcher1 depends on:
ii libc6 2.3.2.ds1-20 GNU C Library: Shared libraries an
-- no debconf information
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: severity of 290733 is important
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.8.10 severity 290733 important Bug#290733: torsmo: Floating point exception Severity set to `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]
Processed: tagging 291700
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.8.6 tags 291700 pending Bug#291700: broken check for peer prevents startup Tags were: patch Tags added: pending 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#291386: kernel-image-2.4.27-2-686: creates bad initrd with complex lvm2 setup
Hi... I'm comming with news that might explain things... First I've diffed the initrds on the two machines I talked about in my initial report... The one that breaks is 1 and the one that works is 2... I attach the diff file... Another interesting detail is dpkg -l lvm\*... On 1 it gives me: un lvmnone (no description available) un lvm-binaries none (no description available) ii lvm-common 1.5.17 The Logical Volume Manager for Linux (common files) ii lvm10 1.0.8-8 The Logical Volume Manager for Linux ii lvm2 2.00.24-1 The Linux Logical Volume Manager un lvm5 none (no description available) un lvm6 none (no description available) On 2 it gives me (I guess the french locales won't be a problem): un lvmnéant (aucune description n'est disponible) un lvm-binaries néant (aucune description n'est disponible) ii lvm-common 1.5.17 The Logical Volume Manager for Linux (common files) un lvm10 néant (aucune description n'est disponible) ii lvm2 2.00.24-1 The Linux Logical Volume Manager un lvm5 néant (aucune description n'est disponible) un lvm6 néant (aucune description n'est disponible) Now I've a guess on my mistake... after a little test Good guess... After removing lvm10, reinstalling kernel-image does give a good initrd... I attach the diff between 2 and the new one 3 for info... I guess the diffs are easily explained by the differences between the two boxes... Now the problem seems clear to me... Remains to choose how to solve it... -- Eric Deplagne Binary files /mnt/initrd1/bin/awk and /mnt/initrd2/bin/awk differ Only in /mnt/initrd2/bin: mkdir Only in /mnt/initrd2/bin2: mkdir File /mnt/initrd1/dev/console is a character special file while file /mnt/initrd2/dev/console is a character special file Only in /mnt/initrd1/dev: lvm File /mnt/initrd1/dev/null is a character special file while file /mnt/initrd2/dev/null is a character special file Only in /mnt/initrd2/etc: lvm diff -ru /mnt/initrd1/etc/modules.conf /mnt/initrd2/etc/modules.conf --- /mnt/initrd1/etc/modules.conf 1970-01-01 01:00:00.0 +0100 +++ /mnt/initrd2/etc/modules.conf 1970-01-01 01:00:00.0 +0100 @@ -95,6 +95,24 @@ ### update-modules: end processing /etc/modutils/paths +### update-modules: start processing /etc/modutils/setserial +# +# This is what I wanted to do, but logger is in /usr/bin, which isn't loaded +# when the module is first loaded into the kernel at boot time! +# +#post-install serial /etc/init.d/setserial start | logger -p daemon.info -t setserial-module reload +#pre-remove serial /etc/init.d/setserial stop | logger -p daemon.info -t setserial-module uload +# +alias /dev/tts serial +alias /dev/tts/0serial +alias /dev/tts/1serial +alias /dev/tts/2serial +alias /dev/tts/3serial +post-install serial /etc/init.d/setserial modload /dev/null 2 /dev/null +pre-remove serial /etc/init.d/setserial modsave /dev/null 2 /dev/null + +### update-modules: end processing /etc/modutils/setserial + ### update-modules: start processing /etc/modutils/arch/i386 alias parport_lowlevel parport_pc alias char-major-10-144 nvram Only in /mnt/initrd2/lib: libdevmapper.so.1.00 Only in /mnt/initrd2/lib: libdl.so.2 Only in /mnt/initrd1/lib: liblvm-10.so.1 Only in /mnt/initrd2/lib: libm.so.6 Only in /mnt/initrd1/lib: lvm-10 Only in /mnt/initrd2/lib: lvm-200 diff -ru /mnt/initrd1/loadmodules /mnt/initrd2/loadmodules --- /mnt/initrd1/loadmodules1970-01-01 01:00:00.0 +0100 +++ /mnt/initrd2/loadmodules1970-01-01 01:00:00.0 +0100 @@ -29,4 +29,4 @@ modprobe -k via82cxxx /dev/null 21 modprobe -k ide-detect modprobe -k ide-disk -modprobe -k lvm-mod +modprobe -k dm-mod Only in /mnt/initrd1/sbin: vgscan diff -ru /mnt/initrd1/script /mnt/initrd2/script --- /mnt/initrd1/script 1970-01-01 01:00:00.0 +0100 +++ /mnt/initrd2/script 1970-01-01 01:00:00.0 +0100 @@ -1,7 +1,16 @@ unload_unused_ide 'yes' pdc202xx_new adma100 aec62xx alim15x3 amd74xx atiixp cmd640 cmd64x cs5530 cy82c693 generic hpt34x hpt366 ns87415 opti621 pdc202xx_old piix rz1000 sc1200 serverworks siimage sis5513 slc90e66 triflex trm290 via82cxxx ROOT=/dev/mapper/vg-root -[ -c /dev/lvm ] || mknod /dev/lvm c 109 0 -mount_tmpfs /etc -vgscan +mkdir /devfs/vg +mount_tmpfs /var +if [ -f /etc/lvm/lvm.conf ]; then +cat /etc/lvm/lvm.conf /var/lvm.conf +fi +mount_tmpfs /etc/lvm +if [ -f /var/lvm.conf ]; then +cat /var/lvm.conf /etc/lvm/lvm.conf +fi +mount -nt devfs devfs /dev vgchange -a y vg -umount -n /etc +umount /dev +umount -n /var +umount -n /etc/lvm Binary files /mnt/initrd2/bin/awk and /mnt/initrd3/bin/awk differ File /mnt/initrd2/dev/console is a character special file while file /mnt/initrd3/dev/console is a
Bug#290339: Test build of supercollider 040926-3 succeded on mips
Hi Thiemo,
Did you compile it in a chroot using pbuilder ? If not, could you try
that? It is possible the invocation of sclang fails in a chroot because
LD_LIBRARY_PATH gets overriden. There is a better version available at
http://piem.org/~piem/debian/pool/supercollider/
Thanks for trying,
Paul
On Sun, 2005-01-23 at 18:34 +0100, Thiemo Seufer wrote:
I wasn't able to reproduce the FTBFS on mips with version 040926-3. The
package builds but has some warnings in the build log as pasted below.
Thiemo
[snip]
# adding some tests after the install
mkdir synthdefs
if ! LD_LIBRARY_PATH=./debian/supercollider/usr/lib
./debian/supercollider/usr/bin/sclang.real -l
./debian/supercollider/etc/sclang$echo outch, sclang test failed.
sclang does not support 64 bit mode yet; \
exit 1; \
fi
./debian/supercollider/etc/sclang.cfg,10: couldn't resolve path
/usr/share/SuperCollider/SCClassLibrary/Linux
./debian/supercollider/etc/sclang.cfg,13: couldn't resolve path
/usr/share/SuperCollider/SCClassLibrary/Common
./debian/supercollider/etc/sclang.cfg,14: couldn't resolve path
/usr/share/SuperCollider/SCClassLibrary/DefaultLibrary
./debian/supercollider/etc/sclang.cfg,15: couldn't resolve path
/usr/share/SuperCollider/SCClassLibrary/backwards_compatibility
init_OSC
-TempoClock_stopAll
-TempoClock_stopAll
compiling class library..
NumPrimitives = 483
pass 1 done
There is a discrepancy.
numClassDeps 0 gNumClasses 78
-TempoClock_stopAll
-TempoClock_stopAll
rm -rf synthdefs archive.sctxar
/usr/bin/make -f debian/rules DH_OPTIONS=-a binary-common
make[1]: Entering directory
`/home/ths/colo/supercollider/supercollider-040926'
dh_testdir
dh_testroot
dh_installchangelogs
dh_installdocs
dh_installexamples
dh_installmenu
dh_installemacsen
dh_installman
dh_link
dh_strip
dh_compress -X.rtf
dh_fixperms
dh_makeshlibs
dh_installdeb
dh_shlibdeps -L supercollider -l debian/supercollider/usr/lib
Use of uninitialized value in scalar assignment at /usr/bin/dh_shlibdeps line
138, COMPAT_IN line 3.
dh_gencontrol
dpkg-gencontrol: warning: unknown substitution variable ${misc:Depends}
dpkg-gencontrol: warning: unknown substitution variable ${shlibs:Depends}
dpkg-gencontrol: warning: unknown substitution variable ${misc:Depends}
dh_md5sums
dh_builddeb
dpkg-deb: building package `supercollider' in
`../supercollider_040926-3_mips.deb'.
dpkg-deb: building package `supercollider-dev' in
`../supercollider-dev_040926-3_mips.deb'.
make[1]: Leaving directory `/home/ths/colo/supercollider/supercollider-040926'
dpkg-genchanges -B
dpkg-genchanges: arch-specific upload - not including arch-independent
packages
dpkg-genchanges: binary-only upload - not including any source code
dpkg-buildpackage: binary only upload (no source included)
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#288464: Patch for pytables 0.9.1-1.1 NMU
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Francesc Alted wrote: | Hi Luk, Hi | I've addressed the issues you reported. The new packages are at the usual | location http://pytables.sourceforge.net/Debian/. Please, as the files are | named the same than old ones, be sure that you have downloaded the new | versions and not those that might be in-cache (either locally or in the | net). Ok, no problem. | By the way, how did you discovered the warnings: | | description-synopsis-starts-with-a-capital-letter | | and | | description-synopsis-starts-with-an-article | | ?? my lintian -i (or linda -i) commands did not show anything of that. Latest lintian (1.23.7), I use lintian -iI to have some more info when there is an error or warning message. | I've addressed them as well, although I don't know whether I succeeded or | not. No, you have changed it in the manpages, but the only thing (according to lintian/linda) that should change in the manpage is the hyphen-used-as-minus-sign. The description-* are to be dealt with in the Description fields in the control file. So, please change the manpages back (except the hyphen-used-as-minus-sign) and change the control file and check your changes with the latest lintian. Cheers Luk -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.5 (GNU/Linux) iD8DBQFB9UYj5UTeB5t8Mo0RAiwjAKCbLv6lL1ynLWbplTMZak2/xzNlzACggZsB Ix3gQId1oOcAFCwiaASlIvk= =Wn/V -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#288464: Patch for pytables 0.9.1-1.1 NMU
A Dilluns 24 Gener 2005 20:01, Luk Claes va escriure: Latest lintian (1.23.7), I use lintian -iI to have some more info when there is an error or warning message. Oh, I see. | I've addressed them as well, although I don't know whether I succeeded or | not. No, you have changed it in the manpages, but the only thing (according to lintian/linda) that should change in the manpage is the hyphen-used-as-minus-sign. The description-* are to be dealt with in the Description fields in the control file. So, please change the manpages back (except the hyphen-used-as-minus-sign) and change the control file and check your changes with the latest lintian. Ok. Done. Now lintian 1.23.7 passes everything. Hope everything would be in place now. Cheers, -- Francesc Alted -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#292048: xwhois_0.4.2-6: FTBFS: automake-1.4 is needed
Package: xwhois Severity: serious Version: 0.4.2-6 Tags: sid Justification: fails to build from source There was an error while trying to autobuild your package: Automatic build of xwhois_0.4.2-6 on aahz by sbuild/m68k 1.170.5 Build started at 20050123-0758 [...] ** Using build dependencies supplied by package: Build-Depends: libgtk1.2-dev [...] make[1]: Entering directory `/build/buildd/xwhois-0.4.2' cd . /build/buildd/xwhois-0.4.2/missing automake-1.4 --gnu --include-deps Makefile WARNING: `automake-1.4' is needed, and you do not seem to have it handy on your system. You might have modified some files without having the proper tools for further handling them. Check the `README' file, it often tells you about the needed prerequirements for installing this package. You may also peek at any GNU archive site, in case some other package would contain this missing `automake-1.4' program. make[1]: *** [Makefile.in] Error 1 make[1]: Leaving directory `/build/buildd/xwhois-0.4.2' make: *** [build] Error 2 Full build logs are available on buildd.debian.org. Please refer to the build log at: http://buildd.debian.org/fetch.php?pkg=xwhoisver=0.4.2-6arch=m68kstamp=1106487039file=logas=raw If this problem has been reported already, please merge it with the appropiate bug report. If you believe this bug should be reassigned to one or more packages, you must clone it and then reassign it to the other packages, like so: clone bug# -1 clone bug# -2 clone bug# -3 reassign -1 package1 reassign -2 package2 reassign -3 package3 thanks Anibal Monsalve Salazar -- .''`. Debian GNU/Linux : :' : Free Operating System `. `' http://debian.org/ `- http://v7w.com/anibal signature.asc Description: Digital signature
Bug#292052: ntp_4.2.0a+stable.orig.tar.gz missing
Package: ntp Version: 4.2.0a+stable-2 Severity: grave Justification: renders package unusable, license violation Hi, while updating my debian mirror I noticed the sid ntp is missing its source: 7c24cb3955f0d38cc596429e93541fe3 842 ntp_4.2.0a+stable-2.dsc 30f8b3d5b970c14dce5c6d8c922afa3e 2272395 ntp_4.2.0a+stable.orig.tar.gz 74d7db968e54ebd31cbd6333e94e2dac 228139 ntp_4.2.0a+stable-2.diff.gz and ntp_4.2.0a+stable.orig.tar.gz is nowhere to be found. MfG Goswin -- System Information: Debian Release: 3.1 Architecture: amd64 (x86_64) Kernel: Linux 2.6.8-frosties-1 Locale: LANG=en_US, LC_CTYPE=en_US -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#291613: notes on this bug
Making xshisen use O_EXCL when writing its rc file seems like the easiest way to fix this hole, but I don't trust it, since O_EXCL doesn't (always?) work on NFS, and a user's home directory could be on a NFS volume. If I maintained this package I would look at its prior (miserable) security history and remove the sgid bit. A global high score file isn't worth it. -- see shy jo signature.asc Description: Digital signature
Bug#261824: more sunfire280 stuff
When netbooting, I can complete the install w/ a d-i nightly; however,
after the reboot:
Sun Fire 280R (2 X UltraSPARC-III) , No Keyboard
OpenBoot 4.0, 2048 MB memory installed, Serial #50387568.
Ethernet address 0:3:ba:0:da:70, Host ID: 8300da70.
Rebooting with command: boot
Boot device: /[EMAIL PROTECTED],60/SUNW,[EMAIL PROTECTED]/[EMAIL
PROTECTED],0/[EMAIL PROTECTED],0:a
File a
SILO Version 1.4.8
boot:
Allocated 8 Megs of memory at 0x4000 for kernel
Uncompressing image...
Loaded kernel version 2.6.8
Loading initial ramdisk (3514368 bytes at 0x7F802000 phys, 0x40C0
virt)...
-
Remapping the kernel... Fast Instruction Access MMU Miss
{0} ok WARNING: There is a TBD problem with ps2.
WARNING: There is a TBD problem with ps2.
.registers
Normal Alternate MMU Vector
0: 0000
1:43f1e01 fff646c0 f0008b58
2: 0 4e2ae0 f000 1000
3:6f1c48 fff780004 6c02c0
4:63470004 30
5:6342bc fff72ab0 de0f0
6:630700 4480001607 fff78000 6cbe80
7: 1 4e 4048 2000
%PC ac40 %nPC ac44
%TBA f000 %CCR 0 XCC:nzvc ICC:nzvc
{0} ok ctrace
PC: ac40
Last leaf: XXXfrom 9c8
0 w %o0-%o7: (6f1d18 606ed0 6009a8 634418 634380 4 633ad1 9c8 )
jmpl 18from 43f1e0
1 w %o0-%o7: (606ed0 101 1 6f1d18 7f0e2000 0 633b91 43f1e0 )
call 43eda0from 69ff18
2 w %o0-%o7: ( 3fe00 6d1400 3a 3a
633c61)
call 697a20from 694490
3 w %o0-%o7: (0 6345e4 0 0 d 6d312c 633d71 694490 )
call 694480from 40466c
4 w %o0-%o7: (6345e0 6345e8 20 10 4e7ff0 0 633e41 40466c )
{0} ok %pc
{0} ok dis
ac40 Fast Data Access MMU Miss
{0} ok WARNING: There is a TBD problem with ps2.
--
Andres Salomon [EMAIL PROTECTED]
signature.asc
Description: This is a digitally signed message part
Bug#267799: nvidia-glx dropped from sarge because of this bug?
Was nvidia-glx really dropped from sarge due to this bug? That seems incredibly harsh for a bug like this (especially with a rather simple workaround provided). Does anybody know needs to happen for nvidia-glx to get back into sarge? noah -- Noah Meyerhans System Administrator MIT Computer Science and Artificial Intelligence Laboratory signature.asc Description: Digital signature
Processed: tagging 292052
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.8.5 tags 292052 sid Bug#292052: ntp_4.2.0a+stable.orig.tar.gz missing There were no tags set. Tags added: sid 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#288464: Patch for pytables 0.9.1-1.1 NMU
On Mon, 24 Jan, 2005 at 12:48:24 +0100, Luk Claes wrote: | However, Daniel seems to be rather busy during the last times, so, if you | are willing to upload yourself the new version, I'll be more than happy. You | can find the new maintainer version at: No problem. Daniel: shout if you disagree ;-) Not at all, please do. -- Daniel Bungert -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#292086: stock installed master.cf file causes postfix to fail to start
Package: postfix Version: 2.1.5-4 Severity: grave Justification: renders package unusable I did a satellite install (as shown in the debconf information below). The postinst script then installed /usr/share/postfix/master.cf.local as /etc/postfix/master.conf. This file contains this line: sed -ne 81p /usr/share/postfix/master.cf.local ::1:smtp inet n - - - - smtpd This caused postfix not to start: Jan 24 19:33:44 ayer postfix/postfix-script: starting the Postfix mail system Jan 24 19:33:45 ayer postfix/master[2382]: fatal: /etc/postfix/master.cf: line 84: bad hostname or network address: ::1 Commenting out the line makes it work fine. If I 'insmod ipv6', then the line works, too, but I shouldn't have to install the ipv6 kernel module for postfix to work. Marc -- System Information: Debian Release: 3.1 APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.4.27-2-686-smp Locale: LANG=en_US.ISO8859-1, LC_CTYPE=en_US.ISO8859-1 (charmap=ISO-8859-1) Versions of packages postfix depends on: ii adduser 3.59 Add and remove users and groups ii debconf [debconf-2.0] 1.4.30.11Debian configuration management sy ii dpkg1.10.26 Package maintenance system for Deb ii libc6 2.3.2.ds1-20 GNU C Library: Shared libraries an ii libdb4.24.2.52-17Berkeley v4.2 Database Libraries [ ii libgdbm31.8.3-2 GNU dbm database routines (runtime ii netbase 4.19 Basic TCP/IP networking system -- debconf information: postfix/master_upgrade_warning: postfix/db_upgrade_warning: true * postfix/mailname: connecterra.com postfix/dynamicmaps_upgrade_warning: postfix/recipient_delim: + * postfix/main_mailer_type: Satellite system postfix/transport_map_warning: * postfix/relayhost: smtp.connecterra.net postfix/procmail: true postfix/bad_recipient_delimiter: * postfix/chattr: true * postfix/root_address: marc postfix/rfc1035_violation: false postfix/mynetworks: 127.0.0.0/8 * postfix/destinations: ayer.connecterra.net, localhost.connecterra.net, localhost postfix/nqmgr_upgrade_warning: postfix/not_configured: postfix/mailbox_limit: 0 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#288876: [Flac-dev] liboggflac1 soname
--- Henrique de Moraes Holschuh [EMAIL PROTECTED] wrote: On Mon, 10 Jan 2005, Ralph Giles wrote: As such it's an incompatible change, for which you should also zero the 'age' field. So 1.1.1-beta1 should have been 2:0:0, not 2:0:1. [...] Yes, I agree. The numbering is all about coexisting installs of the various versions. Ok. I need to know what to do about this... is 1.1.2 with fixed sonames just around the corner? What should we do to fix sonames in Debian? OK, I am going to do a 1.1.2 earlier than I wanted in order to fix this. anyway there are some bug fixes and speedups that will be of benefit. because of the mess and since there have been API changes and additions in both libFLAC and libOggFLAC since 1.1.1 I plan on bumping all the libtool numbers as follows: current++, revision=0 age=0. if this will cause problems please let me know. I'll try to get this ready as soon as possible. Josh __ Do you Yahoo!? All your favorites on one personal page Try My Yahoo! http://my.yahoo.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#290597: marked as done (fails to configure because gs-common is not configured)
Your message dated Mon, 24 Jan 2005 14:25:40 -0800 with message-id [EMAIL PROTECTED] and subject line unreproducible - done 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) -- Received: (at submit) by bugs.debian.org; 15 Jan 2005 03:53:34 + From [EMAIL PROTECTED] Fri Jan 14 19:53:26 2005 Return-path: [EMAIL PROTECTED] Received: from zoot.lafn.org [206.117.18.6] by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1Cpf0A-0002ad-00; Fri, 14 Jan 2005 19:53:26 -0800 Received: from localhost.localdomain (wbar6-lax1-4-10-199-134.lax1.dsl-verizon.net [4.10.199.134]) (authenticated bits=0) by zoot.lafn.org (8.12.3p3/8.12.3) with ESMTP id j0F3rOak001189 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NO) for [EMAIL PROTECTED]; Fri, 14 Jan 2005 19:53:25 -0800 (PST) (envelope-from [EMAIL PROTECTED]) Received: from kraai by localhost.localdomain with local (Exim 4.34) id 1CpZkL-va-Qk for [EMAIL PROTECTED]; Fri, 14 Jan 2005 14:16:47 -0800 Date: Fri, 14 Jan 2005 14:16:45 -0800 From: Matt Kraai [EMAIL PROTECTED] To: [EMAIL PROTECTED] Message-ID: [EMAIL PROTECTED] Mime-Version: 1.0 Content-Disposition: inline User-Agent: Mutt/1.5.6+20040907i X-SA-Exim-Connect-IP: locally generated X-SA-Exim-Mail-From: [EMAIL PROTECTED] Subject: fails to configure because gs-common is not configured Content-Type: text/plain; charset=us-ascii X-SA-Exim-Version: 4.1 (built Wed, 18 Aug 2004 01:12:09 +) X-SA-Exim-Scanned: Yes (on localhost.localdomain) X-Virus-Scanned: ClamAV 0.80/629/Tue Dec 14 11:01:57 2004 clamav-milter version 0.80j on zoot.lafn.org X-Virus-Status: Clean Delivered-To: [EMAIL PROTECTED] X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 (1.212-2003-09-23-exp) on spohr.debian.org X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE autolearn=no version=2.60-bugs.debian.org_2005_01_02 X-Spam-Level: Package: gs-gpl Version: 8.01-5 Severity: serious The Desktop task failed to install while installing Debian because gs-gpl failed to configure because gs-common was not configured: dpkg: dependency problems prevent configuration of gs-gpl: gs-gpl depends on gs-common (= 0.2); however: Package gs-common is not configured yet. dpkg: error processing gs-gpl (--configure): dependency problems - leaving unconfigured -- Matt --- Received: (at 290597-done) by bugs.debian.org; 25 Jan 2005 03:16:12 + From [EMAIL PROTECTED] Mon Jan 24 19:16:12 2005 Return-path: [EMAIL PROTECTED] Received: from zoot.lafn.org [206.117.18.6] by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1CtHBb-oP-00; Mon, 24 Jan 2005 19:16:11 -0800 Received: from localhost.localdomain (wbar6-lax1-4-10-192-126.lax1.dsl-verizon.net [4.10.192.126]) (authenticated bits=0) by zoot.lafn.org (8.12.3p3/8.12.3) with ESMTP id j0P3G7Q2081929 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NO) for [EMAIL PROTECTED]; Mon, 24 Jan 2005 19:16:08 -0800 (PST) (envelope-from [EMAIL PROTECTED]) Received: from kraai by localhost.localdomain with local (Exim 4.34) id 1CtCeV-00011x-41 for [EMAIL PROTECTED]; Mon, 24 Jan 2005 14:25:44 -0800 Date: Mon, 24 Jan 2005 14:25:40 -0800 From: Matt Kraai [EMAIL PROTECTED] To: [EMAIL PROTECTED] Message-ID: [EMAIL PROTECTED] Mime-Version: 1.0 Content-Disposition: inline User-Agent: Mutt/1.5.6+20040907i X-SA-Exim-Connect-IP: locally generated X-SA-Exim-Mail-From: [EMAIL PROTECTED] Subject: unreproducible - done Content-Type: text/plain; charset=us-ascii X-SA-Exim-Version: 4.1 (built Wed, 18 Aug 2004 01:12:09 +) X-SA-Exim-Scanned: Yes (on localhost.localdomain) X-Virus-Scanned: ClamAV 0.80/680/Sun Jan 23 15:16:15 2005 clamav-milter version 0.80j on zoot.lafn.org X-Virus-Status: Clean Delivered-To: [EMAIL PROTECTED] X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 (1.212-2003-09-23-exp) on spohr.debian.org X-Spam-Status: No, hits=-3.0 required=4.0 tests=BAYES_00 autolearn=no version=2.60-bugs.debian.org_2005_01_02 X-Spam-Level: Howdy, I can't reproduce this bug any more, so I'm closing it. -- Matt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: zope-excuserfolder wasn't in woody, so upgrade bugs are not RC
Processing commands for [EMAIL PROTECTED]: severity 291979 important Bug#291979: zope-exuserfolder: NEWS.Debian is not in binary package Severity set to `important'. severity 284572 important Bug#284572: zope-exuserfolder: exUserFolder 0.50 breaks existing installations Severity set to `important'. 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#291979: zope-excuserfolder wasn't in woody, so upgrade bugs are not RC
severity 291979 important severity 284572 important thanks Hi Fabio, Since zope-exuserfolder has not previously been in a stable release of Debian, bugs such as these are important -- but not release-critical. Thanks, -- Steve Langasek postmodern programmer signature.asc Description: Digital signature
Bug#291846: marked as done (Bugs not fixed from 2.6.8)
Your message dated Mon, 24 Jan 2005 21:36:46 -0800 with message-id [EMAIL PROTECTED] and subject line Bugs not fixed from 2.6.8 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) -- Received: (at submit) by bugs.debian.org; 23 Jan 2005 16:33:35 + From [EMAIL PROTECTED] Sun Jan 23 08:33:35 2005 Return-path: [EMAIL PROTECTED] Received: from 80-218-227-31.dclient.hispeed.ch (hal9000) [80.218.227.31] by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1Cskg7-0002Jz-00; Sun, 23 Jan 2005 08:33:31 -0800 Received: from [192.168.42.12] (aragon [192.168.42.12]) by hal9000 (Postfix) with ESMTP id 4830436C0D0 for [EMAIL PROTECTED]; Sun, 23 Jan 2005 17:33:21 +0100 (CET) From: Peter Walser [EMAIL PROTECTED] Date: Sun, 23 Jan 2005 17:33:24 +0100 User-Agent: KMail/1.7.2 MIME-Version: 1.0 Content-Disposition: inline To: [EMAIL PROTECTED] Subject: Bugs not fixed from 2.6.8 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: [EMAIL PROTECTED] Delivered-To: [EMAIL PROTECTED] X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 (1.212-2003-09-23-exp) on spohr.debian.org X-Spam-Status: No, hits=-4.3 required=4.0 tests=BAYES_00,FORGED_YAHOO_RCVD, HAS_PACKAGE autolearn=no version=2.60-bugs.debian.org_2005_01_02 X-Spam-Level: Package: kernel-image-2.6.8-2-686 Version: 2.6.8-12 Severity: grave hi Has someone looked at the bugs in kernel-image-2.6.8-1-386 and kernel-image-2.6.8-1-686? http://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=kernel-image-2.6.8-1-386 Grave functionality bugs - outstanding (1 bug) Important bugs - outstanding (5 bugs) Normal bugs - outstanding (9 bugs) Wishlist items - outstanding (1 bug) Grave functionality bugs - resolved (2 bugs) http://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=kernel-image-2.6.8-1-686 Critical bugs - outstanding (1 bug) Important bugs - outstanding (8 bugs) Normal bugs - outstanding (21 bugs) Minor bugs - outstanding (2 bugs) Wishlist items - outstanding (1 bug) Normal bugs - resolved (1 bug) At least not all bugs are tested, if they are still present and the people are not informed to test with the newer version kernel-image-2.6.8-2-686. My bug #282800 is still not fixed and you shouldn't go out with this 2.6.8. In Kernel 2.6.10 this bug is fixed. Peter --- Received: (at 291846-done) by bugs.debian.org; 25 Jan 2005 05:36:49 + From [EMAIL PROTECTED] Mon Jan 24 21:36:49 2005 Return-path: [EMAIL PROTECTED] Received: from dsl093-039-086.pdx1.dsl.speakeasy.net (localhost.localdomain) [66.93.39.86] by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1CtJNg-0006AC-00; Mon, 24 Jan 2005 21:36:49 -0800 Received: by localhost.localdomain (Postfix, from userid 1000) id 994E311AF3C; Mon, 24 Jan 2005 21:36:46 -0800 (PST) Date: Mon, 24 Jan 2005 21:36:46 -0800 From: Steve Langasek [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Re: Bugs not fixed from 2.6.8 Message-ID: [EMAIL PROTECTED] Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol=application/pgp-signature; boundary=/NkBOFFp2J2Af1nK Content-Disposition: inline User-Agent: Mutt/1.5.6+20040907i Delivered-To: [EMAIL PROTECTED] X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 (1.212-2003-09-23-exp) on spohr.debian.org X-Spam-Status: No, hits=-3.0 required=4.0 tests=BAYES_00 autolearn=no version=2.60-bugs.debian.org_2005_01_02 X-Spam-Level: --/NkBOFFp2J2Af1nK Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Peter, These bugs have not been lost; there's really no reason to open new release critical bugs just to point at release critical bugs that are already open. If anything, the bugs open against the -1 kernel images probably need to be reassigned to the -2 kernel images, but it should be confirmed that these bugs are still present in the new images before doing so. The release-critical bugs you've pointed to will be addressed before the sarge release. --=20 Steve Langasek postmodern programmer --/NkBOFFp2J2Af1nK Content-Type: application/pgp-signature; name=signature.asc Content-Description: Digital signature Content-Disposition: inline -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFB9drsKN6ufymYLloRApYmAKDBNpL+ZZLuHjt5MDg7fECV06todgCgj64C iqXTWkGVrzE4fqarTVusiNo= =869X -END PGP SIGNATURE-
Bug#283171: clisp: FTBFS on mipsel: testsuite failure
Hi Will, This release-critical bug report about clisp failing to build on mipsel has been open for some time. Has there been any progress on resolving the testsuite problems on this architecture? Since the only package depending on clisp (mcvs) has already had its mipsel binaries removed from the archive because previous clisp binaries that did build on mipsel weren't usable, perhaps it would be better to ask ftpmaster to remove clisp's binaries for this architecture as well? Thanks, -- Steve Langasek postmodern programmer signature.asc Description: Digital signature
Bug#291994: marked as done (Decrypt::makeFileKey2() Buffer Overflow)
Your message dated Mon, 24 Jan 2005 15:20:39 +0100 with message-id [EMAIL PROTECTED] and subject line Bug#291994: Decrypt::makeFileKey2() Buffer Overflow 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) -- Received: (at submit) by bugs.debian.org; 24 Jan 2005 13:47:56 + From [EMAIL PROTECTED] Mon Jan 24 05:47:56 2005 Return-path: [EMAIL PROTECTED] Received: from mail.arcert.gov.ar [200.47.53.18] by spohr.debian.org with smtp (Exim 3.35 1 (Debian)) id 1Ct4ZP-00055e-00; Mon, 24 Jan 2005 05:47:55 -0800 Received: (qmail 6975 invoked from network); 24 Jan 2005 13:47:49 - X-Scanned-By: ArCERT. Received: from unknown (HELO clementina.arcert.gov.ar) (arcert) by mail.arcert.gov.ar with SMTP; 24 Jan 2005 13:47:48 - Subject: Decrypt::makeFileKey2() Buffer Overflow From: Luciano Bello [EMAIL PROTECTED] To: [EMAIL PROTECTED] Content-Type: text/plain Date: Mon, 24 Jan 2005 10:46:01 -0300 Message-Id: [EMAIL PROTECTED] Mime-Version: 1.0 X-Mailer: Evolution 2.0.3 Content-Transfer-Encoding: 7bit Delivered-To: [EMAIL PROTECTED] X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 (1.212-2003-09-23-exp) on spohr.debian.org X-Spam-Status: No, hits=-5.5 required=4.0 tests=BAYES_30,HAS_PACKAGE autolearn=no version=2.60-bugs.debian.org_2005_01_02 X-Spam-Level: Package: kpdf Version: 3.x Severity: grave Tags: security sarge sid patch The version in woody is not affected by this problem. TITLE: KDE kpdf Decrypt::makeFileKey2() Buffer Overflow SECUNIA ADVISORY ID: SA13916 VERIFY ADVISORY: http://secunia.com/advisories/13916/ CRITICAL: Highly critical IMPACT: System access WHERE: From remote SOFTWARE: KDE 3.x http://secunia.com/product/219/ DESCRIPTION: The vendor has acknowledged a vulnerability in kpdf, which can be exploited by malicious people to compromise a user's system. For more information: SA13903 SOLUTION: Apply patches. KDE 3.2.3: ftp://ftp.kde.org/pub/kde/security_patches/post-3.2.3-kdegraphics-3.diff KDE 3.3.2: ftp://ftp.kde.org/pub/kde/security_patches/post-3.3.2-kdegraphics-3.diff ORIGINAL ADVISORY: http://www.kde.org/info/security/advisory-20050119-1.txt OTHER REFERENCES: SA13903: http://secunia.com/advisories/13903/ -- About: This Advisory was delivered by Secunia as a free service to help everybody keeping their systems up to date against the latest vulnerabilities. Subscribe: http://secunia.com/secunia_security_advisories/ Definitions: (Criticality, Where etc.) http://secunia.com/about_secunia_advisories/ --- Received: (at 291994-done) by bugs.debian.org; 24 Jan 2005 14:20:42 + From [EMAIL PROTECTED] Mon Jan 24 06:20:42 2005 Return-path: [EMAIL PROTECTED] Received: from 84-120-64-130.onocable.ono.com (chistera.yi.org) [84.120.64.130] by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1Ct558-0006Wv-00; Mon, 24 Jan 2005 06:20:42 -0800 Received: from userid 1000 by chistera.yi.org with local (Exim 4.43) id 1Ct555-0007um-N9; Mon, 24 Jan 2005 15:20:39 +0100 Date: Mon, 24 Jan 2005 15:20:39 +0100 From: Adeodato =?iso-8859-1?Q?Sim=F3?= [EMAIL PROTECTED] To: Luciano Bello [EMAIL PROTECTED], [EMAIL PROTECTED] Subject: Re: Bug#291994: Decrypt::makeFileKey2() Buffer Overflow Message-ID: [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED], Adeodato =?iso-8859-1?Q?Sim=F3?= [EMAIL PROTECTED] References: [EMAIL PROTECTED] Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: [EMAIL PROTECTED] X-No-CC: Please respect my Mail-Followup-To header User-Agent: Mutt/1.5.6+20050115i Delivered-To: [EMAIL PROTECTED] X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 (1.212-2003-09-23-exp) on spohr.debian.org X-Spam-Status: No, hits=-3.8 required=4.0 tests=BAYES_01,FROM_ENDS_IN_NUMS, HAS_BUG_NUMBER autolearn=no version=2.60-bugs.debian.org_2005_01_02 X-Spam-Level: * Luciano Bello [Mon, 24 Jan 2005 10:46:01 -0300]: Package: kpdf Version: 3.x Severity: grave Tags: security sarge sid patch The version in woody is not affected by this problem. The version in sid either, see #291251. Will enter sarge 'soon'. -- Adeodato Simó EM: asp16 [ykwim] alu.ua.es | PK: DA6AE621 Don't be irreplaceable, if you can't be replaced, you can't be promoted. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a
Processed: Re: Bug#291545: tetex-bin: initex fails to generate some etmf files
Processing commands for [EMAIL PROTECTED]: severity 291545 normal Bug#291545: tetex-bin: initex fails to generate some etmf files Severity set to `normal'. retitle 291545 upgrade of files in texmf.d shows diff twice (plain ucf and update-texmf) Bug#291545: tetex-bin: initex fails to generate some etmf files Changed Bug title. stop 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]
