Bug#500910: CVE-2008-4194 denial of service
Quoting Pierre Habouzit ([EMAIL PROTECTED]): If someone fixes this, fixing #490047 would be much appreciated as well by the l10n folks (and this is certainly not invasive). This becomes an habit :P You should know that..:-) But, yes, I found funny to see that two of your packages went on my l10n radar at about the same time, Pierre. And you'll fix both of them of course. /me moves the radar somewhere else. Feel safe, apparently http://i18n.debian.net/debian-l10n/l10n-nmu/nmu_bypackage.html is not showing any other package of yours... signature.asc Description: Digital signature
Processed: Re: Bug#500960: s2disk: Don't poweroff
Processing commands for [EMAIL PROTECTED]: severity 500960 normal Bug#500960: s2disk: Don't poweroff Severity set to `normal' from `grave' thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#500960: s2disk: Don't poweroff
severity 500960 normal thanks Quoting Sergio Damian Vernis ([EMAIL PROTECTED]): Package: uswsusp Version: 0.7-1.2 Severity: grave Justification: renders package unusable When I use the s2disk script don't poweroff. I must turn off the computer manualy (4 seconds ATX power button presss). Previous versions of this scripts turn off power automaticaly. That certainly doesn't deserve to be tagged as release critical, indeed. Are you in position to try the 0.8 version that is in unstable? signature.asc Description: Digital signature
Processed: mmorph: diff for NMU version 2.3.4.2-11.1
Processing commands for [EMAIL PROTECTED]: tags 500615 + patch Bug#500615: mmorph: Depends on libdb4.3 while it won't be included in the release There were no tags set. Tags added: patch thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#500615: mmorph: diff for NMU version 2.3.4.2-11.1
tags 500615 + patch thanks Dear maintainer, I've prepared an NMU for mmorph (versioned as 2.3.4.2-11.1) and uploaded it to DELAYED/3. Please feel free to tell me if I should delay it longer. Cheers Luk diff -u mmorph-2.3.4.2/debian/changelog mmorph-2.3.4.2/debian/changelog --- mmorph-2.3.4.2/debian/changelog +++ mmorph-2.3.4.2/debian/changelog @@ -1,3 +1,10 @@ +mmorph (2.3.4.2-11.1) unstable; urgency=low + + * Non-maintainer upload. + * Remove libdb4.3-dev alternative (Closes: #500615). + + -- Luk Claes [EMAIL PROTECTED] Fri, 03 Oct 2008 07:53:39 +0200 + mmorph (2.3.4.2-11) unstable; urgency=low * mmorph.1: Properly escape all the - characters that should be diff -u mmorph-2.3.4.2/debian/control mmorph-2.3.4.2/debian/control --- mmorph-2.3.4.2/debian/control +++ mmorph-2.3.4.2/debian/control @@ -3,7 +3,7 @@ Priority: extra Maintainer: Thomas Bushnell, BSG [EMAIL PROTECTED] Standards-Version: 3.7.3 -Build-Depends: debhelper (= 5), bison, flex, libdb4.3-dev | libdb-dev +Build-Depends: debhelper (= 5), bison, flex, libdb-dev Package: mmorph Architecture: any
Bug#497536: marked as done (please do not ship with lenny)
Your message dated Fri, 03 Oct 2008 09:39:51 +0200 with message-id [EMAIL PROTECTED] and subject line new upstream 1.2 can transition to testing once lenny is released has caused the Debian Bug report #497536, regarding please do not ship with lenny to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [EMAIL PROTECTED] immediately.) -- 497536: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=497536 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: libgrinvin-help-java Version: 1.0-1 Severity: serious This version of libgrinvin-help-java is deprecated upstream. Please do not ship it with lenny. -- Adriaan Peeters signature.asc Description: This is a digitally signed message part ---End Message--- ---BeginMessage--- new upstream 1.2 can transition to testing once lenny is released -- Adriaan Peeters signature.asc Description: This is a digitally signed message part ---End Message---
Bug#497538: marked as done (please do not ship with lenny)
Your message dated Fri, 03 Oct 2008 09:38:44 +0200 with message-id [EMAIL PROTECTED] and subject line new upstream 1.2 can transition to testing once lenny is released has caused the Debian Bug report #497538, regarding please do not ship with lenny to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [EMAIL PROTECTED] immediately.) -- 497538: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=497538 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: libgrinvin-core-java Version: 1.0.4-1 Severity: serious This version of libgrinvin-core-java does not build with the latest version of libswirl-java and is deprecated upstream. Please do not ship it with lenny. -- Adriaan Peeters signature.asc Description: This is a digitally signed message part ---End Message--- ---BeginMessage--- new upstream 1.2 can transition to testing once lenny is released -- Adriaan Peeters signature.asc Description: This is a digitally signed message part ---End Message---
Bug#497537: marked as done (please do not ship with lenny)
Your message dated Fri, 03 Oct 2008 09:39:24 +0200 with message-id [EMAIL PROTECTED] and subject line new upstream 1.2 can transition to testing once lenny is released has caused the Debian Bug report #497537, regarding please do not ship with lenny to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [EMAIL PROTECTED] immediately.) -- 497537: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=497537 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: libgrinvin-graphs-java Version: 1.0-1 Severity: serious This version of libgrinvin-graphs-java is deprecated upstream. Please do not ship it with lenny. -- Adriaan Peeters signature.asc Description: This is a digitally signed message part ---End Message--- ---BeginMessage--- new upstream 1.2 can transition to testing once lenny is released -- Adriaan Peeters signature.asc Description: This is a digitally signed message part ---End Message---
Bug#500778: libnss-ldapd: groups resolve to nogroup after boot
Hi, On Fri, Oct 03, 2008 at 12:18:47AM +0200, Arthur de Jong wrote: If using nfs4 (I've been doing some reading up but still no first-hand experience) is that if the user doesn't exist it is generally mapped to nobody:nogroup. right. The mapping is done by idmapd but at some point in combination with something in the kernel. From what I understand from scanning the idmapd code is that there is a default cache expiry time (in the kernel) of 500 seconds (10 minutes). Current value should be available in /proc/sys/fs/nfs/idmap_cache_timeout. My guess is that name lookups are cached in idmapd. Can you check that by restarting idmapd (/etc/init.d/nfs-common restart) the problem goes away? Nope, it does not. Can you check the idmapd logs anything out of the ordinary? Perhaps you can increase the verbosity in /etc/idmapd.conf. Hm, no nothing special. Setting the verbosity higher as the default (default: 3, tried up to 10) does not seem to change anything. Basically this is all: Oct 3 09:46:36 teekanne rpc.idmapd[3309]: libnfsidmap: using domain: localdomain Oct 3 09:46:36 teekanne rpc.idmapd[3309]: libnfsidmap: using translation method: nsswitch Oct 3 09:46:36 teekanne rpc.idmapd[3310]: Expiration time is 600 seconds. Oct 3 09:46:36 teekanne rpc.idmapd[3310]: Opened /proc/net/rpc/nfs4.nametoid/channel Oct 3 09:46:36 teekanne rpc.idmapd[3310]: Opened /proc/net/rpc/nfs4.idtoname/channel Oct 3 09:46:36 teekanne rpc.idmapd[3310]: New client: 0 Oct 3 09:46:36 teekanne rpc.idmapd[3310]: Opened /var/lib/nfs/rpc_pipefs/nfs/clnt0/idmap Oct 3 09:46:36 teekanne rpc.idmapd[3310]: New client: 1 Oct 3 09:47:23 teekanne rpc.idmapd[3310]: Client 0: (user) id 30010 - name [EMAIL PROTECTED] Oct 3 09:47:23 teekanne rpc.idmapd[3310]: Client 0: (group) id 65534 - name [EMAIL PROTECTED] Thanks. Perhaps I should set up a test environment myself with NFS4. Do you have some pointers for that (I use NFS3 myself). Thats not a great thing. You need to setup an export entry like you do for NFSv4, however there is a fundamentel difference to NFSv3. You export a NFSROOT not single exports. So you possibly want to setup a virtual export directory. Its described here [1]. Best Regards, Patrick [1] http://www.crazysquirrel.com/computing/debian/servers/setting-up-nfs4.jspx -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#500921: marked as done (sdcv_0.4.2-4(sparc/unstable): FTBFS on sparc in test cases)
Your message dated Fri, 03 Oct 2008 07:32:05 + with message-id [EMAIL PROTECTED] and subject line Bug#500921: fixed in sdcv 0.4.2-5 has caused the Debian Bug report #500921, regarding sdcv_0.4.2-4(sparc/unstable): FTBFS on sparc in test cases to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [EMAIL PROTECTED] immediately.) -- 500921: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=500921 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: sdcv Version: 0.4.2-4 Severity: serious There was an error while trying to autobuild your package: Automatic build of sdcv_0.4.2-4 on lebrun by sbuild/sparc 98 Build started at 20081002-1750 [...] ** Using build dependencies supplied by package: Build-Depends: debhelper (= 7.0.0), gettext, zlib1g-dev, pkg-config, libglib2.0-dev, libreadline5-dev | libreadline-dev, quilt (= 0.40) [...] == 2 of 6 tests failed Please report to [EMAIL PROTECTED] == make[4]: *** [check-TESTS] Error 1 make[4]: Leaving directory `/build/buildd/sdcv-0.4.2/tests' make[3]: *** [check-am] Error 2 make[3]: Leaving directory `/build/buildd/sdcv-0.4.2/tests' make[2]: *** [check-recursive] Error 1 make[2]: Leaving directory `/build/buildd/sdcv-0.4.2/tests' make[1]: *** [check-recursive] Error 1 make[1]: Leaving directory `/build/buildd/sdcv-0.4.2' dh_auto_test: command returned error code 512 make: *** [build-stamp] Error 1 dpkg-buildpackage: failure: debian/rules build gave error exit status 2 A full build log can be found at: http://buildd.debian.org/build.php?arch=sparcpkg=sdcvver=0.4.2-4 ---End Message--- ---BeginMessage--- Source: sdcv Source-Version: 0.4.2-5 We believe that the bug you reported is fixed in the latest version of sdcv, which is due to be installed in the Debian FTP archive: sdcv_0.4.2-5.diff.gz to pool/main/s/sdcv/sdcv_0.4.2-5.diff.gz sdcv_0.4.2-5.dsc to pool/main/s/sdcv/sdcv_0.4.2-5.dsc sdcv_0.4.2-5_amd64.deb to pool/main/s/sdcv/sdcv_0.4.2-5_amd64.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Michal Čihař [EMAIL PROTECTED] (supplier of updated sdcv package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Fri, 03 Oct 2008 09:18:52 +0200 Source: sdcv Binary: sdcv Architecture: source amd64 Version: 0.4.2-5 Distribution: unstable Urgency: low Maintainer: Michal Čihař [EMAIL PROTECTED] Changed-By: Michal Čihař [EMAIL PROTECTED] Description: sdcv - StarDict Console Version Closes: 500921 Changes: sdcv (0.4.2-5) unstable; urgency=low . * Make sdcv accept $HOME as home directory (Closes: #500921). Checksums-Sha1: 03c89f4f84bb24d288515815a2041cf097549651 1205 sdcv_0.4.2-5.dsc db74628cd9087b24534f2803b4e4efd2c5785fef 10376 sdcv_0.4.2-5.diff.gz a332f529ae1476c87295acdfac6f14c3389fae8c 58428 sdcv_0.4.2-5_amd64.deb Checksums-Sha256: a69bd47d2b074745605c0e83de8499000b724eaec0b1e50faabda19d0a2ff434 1205 sdcv_0.4.2-5.dsc e500388a1d8cc14e506ac70bbdb8eb6c341a829b21605decacc9028b5d0806da 10376 sdcv_0.4.2-5.diff.gz bad29d65773e1fb4f6d8d810d342364278e127cda4d1aac266c763115aceccb7 58428 sdcv_0.4.2-5_amd64.deb Files: a5bf05658391b11f6dc45d0e7a305514 1205 utils optional sdcv_0.4.2-5.dsc c36e0e55d956d7cc8aa9fa8e6535dad8 10376 utils optional sdcv_0.4.2-5.diff.gz 1349bc20e23c12288025e527468f952a 58428 utils optional sdcv_0.4.2-5_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkjlyB4ACgkQ3DVS6DbnVgTZBgCfdXiUWuuOOWsU6ydrCquHz8VT zOEAn0thjigLC6FJuWdvJGsusA1TOYDQ =1LdA -END PGP SIGNATURE- ---End Message---
Bug#500987: kjs: javascript RegExp doesn't work with libpcre3-7.7
Package: kdelibs5 Version: 4.1.2-1 Severity: serious Justification: Sune says so When you use kdelibs5-4.1.2-1 with a libpcre3 version lower than 7.7 there is a regression with kjs. With the kjs javascript debugger enabled you will see a parse error when visiting e.g. http://www.regular-expressions.info/javascriptexample.html If you upgrade libpcre3 to a version above, or equal to, 7.7 this parse error doesn't show and the javascript works as expected. I believe that this happens because kdelibs5-4.1.2-1 is built against libpcre3-7.8-1 and kjs enables a certain feature for libpcre3 versions above 7.7: kjs/regexp.cpp:148:#ifdef PCRE_JAVASCRIPT_COMPAT // introduced in PCRE 7.7 kjs/regexp.cpp-149- options |= PCRE_JAVASCRIPT_COMPAT; kjs/regexp.cpp-150-#endif A possible solution would be to make kdelibs5 depend on =libpcre3-7.7 as it doesn't depend on a specific version right now. On #khtml someone mentioned this: [18:48:40] OffEagle We should probably use pcre_feature_supported. [18:49:17] OffEagle Of course, that's really generally the case that if you run against an older version of library you'll get problems. Reaction on #debian-kde: [09:39:56] pusling he is usually right. [09:40:44] pusling please for now report a serious bug against kdelibs5 with this info. If you are in doubt about justification, just say Sune says so ;) -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (900, 'testing'), (600, 'unstable'), (101, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.26-1-686 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#500991: multipath-tools: Multipath-tools uses invalid scsi_id option, breaks multipath
Package: multipath-tools
Version: 0.4.8-12
Severity: grave
Justification: renders package unusable
Hi,
I've installed multipath-tools on lenny, but it fails to find any multipath
devices. I've run multipath -v3 and it gives the following error:
cciss!c0d0: getuid = /lib/udev/scsi_id -n -g -u -d /dev/%n (controller setting)
/lib/udev/scsi_id: invalid option -- n
error calling out /lib/udev/scsi_id -n -g -u -d /dev/cciss!c0d0
The -n option is not supported by /lib/udev/scsi_id.
Adding the getuid_callout option to the defaults section of /etc/multipath.conf
without the -n option does not seem to help. It seems the section is ignored?
The version of udev on this machine is 0.125-6.
According to the man page, the default command that is issued is
/lib/udev/scsi_id -g -u -d /dev/%n, without the -n option.
Regards,
Rik
-- Package-specific info:
Contents of /etc/multipath.conf:
defaults {
udev_dir/dev
polling_interval10
selectorround-robin 0
path_grouping_policymultibus
getuid_callout /lib/udev/scsi_id -g -u -d /dev/%n
prio_callout/bin/true
path_checkerdirectio
rr_min_io 100
rr_weight priorities
failbackimmediate
no_path_retry fail
user_friendly_names yes
}
-- System Information:
Debian Release: lenny/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.26-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages multipath-tools depends on:
ii initscripts 2.86.ds1-61Scripts for initializing and shutt
ii kpartx0.4.8-12 create device mappings for partiti
ii libaio1 0.3.107-2 Linux kernel AIO access library -
ii libc6 2.7-13 GNU C Library: Shared libraries
ii libdevmapper1.02.12:1.02.27-3The Linux Kernel Device Mapper use
ii libncurses5 5.6+20080830-1 shared libraries for terminal hand
ii libreadline5 5.2-3 GNU readline and history libraries
ii lsb-base 3.2-20 Linux Standard Base 3.2 init scrip
ii udev 0.125-6/dev/ and hotplug management daemo
multipath-tools recommends no packages.
Versions of packages multipath-tools suggests:
pn multipath-tools-boot none (no description available)
-- no debconf information
Disclaimer: http://www.kuleuven.be/cwis/email_disclaimer.htm
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#500991: More info
Hi, It seems the -n option is only applied to LOGICAL VOLUME products, according to a strings on /sbin/multipath. When I add a device section for 'LOGICAL VOLUME' and specify a getuid_callout, it uses that one. I would expect multipath to use the defaults unless explicitely configured in /etc/multipath.conf This bug can be downgraded because it will work with a config change, but should the -n option not be removed from the built-in defaults for LOGICAL VOLUME? Regards, Rik -- Rik Theys System Engineer KU Leuven - Dept. Elektrotechniek (ESAT) Kasteelpark Arenberg 10 B-3001 LEUVEN - HEVERLEE Tel.: +32(0)16/32.11.07 Any errors in spelling, tact or fact are transmission errors Disclaimer: http://www.kuleuven.be/cwis/email_disclaimer.htm -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#500991: incorrect regular expression?
Hi, I think the default regular expression for cciss devices in /etc/multipath.conf (and the built-in defaults) should be: devnode ^cciss!c[0-9]d[0-9]*(p[0-9]*)? instead of devnode ^cciss!c[0-9]d[0-9]*[p[0-9]*] The partition on the cciss disks should be optional? Regards, Rik -- Rik Theys System Engineer KU Leuven - Dept. Elektrotechniek (ESAT) Kasteelpark Arenberg 10 B-3001 LEUVEN - HEVERLEE Tel.: +32(0)16/32.11.07 Any errors in spelling, tact or fact are transmission errors Disclaimer: http://www.kuleuven.be/cwis/email_disclaimer.htm -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#500999: openturns_0.12.1-5(sparc/unstable): FTBFS on sparc
Package: openturns Version: 0.12.1-5 Severity: serious There was an error while trying to autobuild your package: Automatic build of openturns_0.12.1-5 on lebrun by sbuild/sparc 98 Build started at 20081003-0210 [...] ** Using build dependencies supplied by package: Build-Depends: cdbs (= 0.4.51), quilt (= 0.46-4), debhelper (= 5), gcc (= 4.2), g++ (= 4.2), gfortran (= 4.2), libxerces-c2-dev, libboost1.35-dev, liblapack-dev, libblas-dev, libqt3-mt-dev, r-base-core (= 2.0), python-central (= 0.5.6), python-dev, graphviz, doxygen, docbook-to-man, texlive [...] g++ -DHAVE_CONFIG_H -I. -I../include -I../include -DOT_DEBUG_LEVEL=3 -g -Wall -O2 -c -o main-main.o `test -f 'main.cxx' || echo './'`main.cxx /bin/sh ../libtool --tag=CXX --mode=link g++ -g -Wall -O2 -L. -o main main-main.o libOT.la -lpthread -lutil -ldl -lm g++ -g -Wall -O2 -o .libs/main main-main.o -L/build/buildd/openturns-0.12.1/lib/src ./.libs/libOT.so -lpthread -lutil -ldl -lm -Wl,--rpath -Wl,/usr/lib/openturns ./.libs/libOT.so: undefined reference to `__sync_fetch_and_add_4' collect2: ld returned 1 exit status make[4]: *** [main] Error 1 make[4]: Leaving directory `/build/buildd/openturns-0.12.1/lib/src' make[3]: *** [all-recursive] Error 1 make[3]: Leaving directory `/build/buildd/openturns-0.12.1/lib/src' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/build/buildd/openturns-0.12.1/lib' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/build/buildd/openturns-0.12.1' make: *** [debian/stamp-makefile-build] Error 2 dpkg-buildpackage: failure: debian/rules build gave error exit status 2 A full build log can be found at: http://buildd.debian.org/build.php?arch=sparcpkg=openturnsver=0.12.1-5 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#500991: More info
On Fri, Oct 03, 2008 at 10:47:55AM +0200, Rik Theys wrote: Hi, It seems the -n option is only applied to LOGICAL VOLUME products, according to a strings on /sbin/multipath. When I add a device section for 'LOGICAL VOLUME' and specify a getuid_callout, it uses that one. I would expect multipath to use the defaults unless explicitely configured in /etc/multipath.conf There's a set of default for different classes of devices. I'll remove the -n but I don't think cciss is well supported by the multipath version in lenny. Current upstream git has it's own patch checker for cciss (which we can't backport easily since the whole structure of the path checkers changed). This bug can be downgraded because it will work with a config change, but should the -n option not be removed from the built-in defaults for LOGICAL VOLUME? Does it multipathing work cciss if you remove -n? Do the patchs get detected correctly. Could you attache the output of multipath -l? -- Guido -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#500999: [Pkg-scicomp-devel] Bug#500999: openturns_0.12.1-5(sparc/unstable): FTBFS on sparc
thanks for the report the problem is identified and a fix is under way -6 should fix this Best regards C. On Fri, Oct 3, 2008 at 11:11 AM, Martin Zobel-Helas [EMAIL PROTECTED] wrote: Package: openturns Version: 0.12.1-5 Severity: serious There was an error while trying to autobuild your package: Automatic build of openturns_0.12.1-5 on lebrun by sbuild/sparc 98 Build started at 20081003-0210 [...] ** Using build dependencies supplied by package: Build-Depends: cdbs (= 0.4.51), quilt (= 0.46-4), debhelper (= 5), gcc (= 4.2), g++ (= 4.2), gfortran (= 4.2), libxerces-c2-dev, libboost1.35-dev, liblapack-dev, libblas-dev, libqt3-mt-dev, r-base-core (= 2.0), python-central (= 0.5.6), python-dev, graphviz, doxygen, docbook-to-man, texlive [...] g++ -DHAVE_CONFIG_H -I. -I../include -I../include -DOT_DEBUG_LEVEL=3 -g -Wall -O2 -c -o main-main.o `test -f 'main.cxx' || echo './'`main.cxx /bin/sh ../libtool --tag=CXX --mode=link g++ -g -Wall -O2 -L. -o main main-main.o libOT.la -lpthread -lutil -ldl -lm g++ -g -Wall -O2 -o .libs/main main-main.o -L/build/buildd/openturns-0.12.1/lib/src ./.libs/libOT.so -lpthread -lutil -ldl -lm -Wl,--rpath -Wl,/usr/lib/openturns ./.libs/libOT.so: undefined reference to `__sync_fetch_and_add_4' collect2: ld returned 1 exit status make[4]: *** [main] Error 1 make[4]: Leaving directory `/build/buildd/openturns-0.12.1/lib/src' make[3]: *** [all-recursive] Error 1 make[3]: Leaving directory `/build/buildd/openturns-0.12.1/lib/src' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/build/buildd/openturns-0.12.1/lib' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/build/buildd/openturns-0.12.1' make: *** [debian/stamp-makefile-build] Error 2 dpkg-buildpackage: failure: debian/rules build gave error exit status 2 A full build log can be found at: http://buildd.debian.org/build.php?arch=sparcpkg=openturnsver=0.12.1-5 ___ Pkg-scicomp-devel mailing list [EMAIL PROTECTED] http://lists.alioth.debian.org/mailman/listinfo/pkg-scicomp-devel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: Fixed after NMU
Processing commands for [EMAIL PROTECTED]: fixed 400066 0.5.2-1.2 Bug#400066: lcdproc_0.5.1-2(powerpc/unstable): FTBFS: impossible constraint in asm Bug marked as fixed in version 0.5.2-1.2. 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#500991: incorrect regular expression?
On Fri, Oct 03, 2008 at 10:56:16AM +0200, Rik Theys wrote: devnode ^cciss!c[0-9]d[0-9]*(p[0-9]*)? instead of devnode ^cciss!c[0-9]d[0-9]*[p[0-9]*] The partition on the cciss disks should be optional? I'd say you don't multipath partitions at all but only the disks but then I don't know how multipath on cciss is supposed to work at all? What machine is this? What kind of storage? I'm inclined to blacklist cciss altogether for lenny since but please report back first how well it works for you. Cheers, -- Guido -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#500991: multipath-tools: Multipath-tools uses invalid scsi_id option, breaks multipath
severity 500991 normal
retitle 500991 cciss not well supported
thanks
Hi Rik,
On Fri, Oct 03, 2008 at 10:32:44AM +0200, Rik Theys wrote:
[..snip..]
cciss!c0d0: getuid = /lib/udev/scsi_id -n -g -u -d /dev/%n (controller
setting)
/lib/udev/scsi_id: invalid option -- n
error calling out /lib/udev/scsi_id -n -g -u -d /dev/cciss!c0d0
The -n option is not supported by /lib/udev/scsi_id.
scsi_id shifted quiet some options around -s got dropped (which is
fixed) but probably -n too.
Adding the getuid_callout option to the defaults section of
/etc/multipath.conf without the -n option does not seem to help. It
seems the section is ignored?
No it isn't. Something like:
defaults {
getuid_callout /lib/udev/scsi_id -g -u -d /dev/%n
}
should work.
-- Guido
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: reassign 500956 to linux-2.6, forcibly merging 499458 500956
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.9.26 reassign 500956 linux-2.6 Bug#500956: unable to boot on a500 (hppa) Bug reassigned from package `linux-image-2.6.26-1-parisc64' to `linux-2.6'. forcemerge 499458 500956 Bug#499458: [hppa] kernel no longer boots on an A500 Bug#500956: unable to boot on a500 (hppa) Forcibly Merged 499458 500956. 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#500991: incorrect regular expression?
Guido Günther wrote: On Fri, Oct 03, 2008 at 10:56:16AM +0200, Rik Theys wrote: devnode ^cciss!c[0-9]d[0-9]*(p[0-9]*)? instead of devnode ^cciss!c[0-9]d[0-9]*[p[0-9]*] The partition on the cciss disks should be optional? I'd say you don't multipath partitions at all but only the disks but then I don't know how multipath on cciss is supposed to work at all? What machine is this? What kind of storage? I'm inclined to blacklist cciss altogether for lenny since but please report back first how well it works for you. The machine is an HP DL380G5 with an HP smart array P400i raid controller. I was just testing the multipath support because I will need it later on. The RAID disk is not available using multiple paths, but multipath should still list it as one path (IMHO). With the default blacklist info and the patch checker configured for LOGICAL VOLUME devices, the callout still fails, because it checks for /dev/cciss!c0d0 instead of /dev/cciss/c0d0: tigris:~# multipath -v3 ram0: device node name blacklisted ram1: device node name blacklisted ram2: device node name blacklisted ram3: device node name blacklisted ram4: device node name blacklisted ram5: device node name blacklisted ram6: device node name blacklisted ram7: device node name blacklisted ram8: device node name blacklisted ram9: device node name blacklisted ram10: device node name blacklisted ram11: device node name blacklisted ram12: device node name blacklisted ram13: device node name blacklisted ram14: device node name blacklisted ram15: device node name blacklisted cciss!c0d0: not found in pathvec cciss!c0d0: mask = 0x1f cciss!c0d0: dev_t = 104:0 cciss!c0d0: size = 286679925 cciss!c0d0: subsystem = pci cciss!c0d0: h:b:t:l = 0:0:0:0 cciss!c0d0: vendor = HP cciss!c0d0: product = LOGICAL VOLUME cciss!c0d0: revision = 5.20 cciss!c0d0: getprio = /bin/true (config file default) cciss!c0d0: prio = 0 cciss!c0d0: getuid = /lib/udev/scsi_id -g -u -d /dev/%n (controller setting) error calling out /lib/udev/scsi_id -g -u -d /dev/cciss!c0d0 hda: device node name blacklisted dm-0: device node name blacklisted dm-1: device node name blacklisted dm-2: device node name blacklisted loop0: device node name blacklisted loop1: device node name blacklisted loop2: device node name blacklisted loop3: device node name blacklisted loop4: device node name blacklisted loop5: device node name blacklisted loop6: device node name blacklisted loop7: device node name blacklisted dm-3: device node name blacklisted = paths list = uuid hcildevdev_t pri dm_st chk_st vend/prod/rev 0:0:0:0 cciss!c0d0 104:0 0 [undef][undef] HP ,LOGICAL VOLUME When I run it manually with the correct path, it works: tigris:~# /lib/udev/scsi_id -g -u -d /dev/cciss/c0d0 3600508b100104d395357463047410001 With the regular expression as I suggested it in multipath.conf, the device is blacklisted: tigris:~# multipath -v3 ram0: device node name blacklisted ram1: device node name blacklisted ram2: device node name blacklisted ram3: device node name blacklisted ram4: device node name blacklisted ram5: device node name blacklisted ram6: device node name blacklisted ram7: device node name blacklisted ram8: device node name blacklisted ram9: device node name blacklisted ram10: device node name blacklisted ram11: device node name blacklisted ram12: device node name blacklisted ram13: device node name blacklisted ram14: device node name blacklisted ram15: device node name blacklisted cciss!c0d0: device node name blacklisted hda: device node name blacklisted dm-0: device node name blacklisted dm-1: device node name blacklisted dm-2: device node name blacklisted loop0: device node name blacklisted loop1: device node name blacklisted loop2: device node name blacklisted loop3: device node name blacklisted loop4: device node name blacklisted loop5: device node name blacklisted loop6: device node name blacklisted loop7: device node name blacklisted dm-3: device node name blacklisted = no paths = Regards, -- Rik Theys System Engineer KU Leuven - Dept. Elektrotechniek (ESAT) Kasteelpark Arenberg 10 B-3001 LEUVEN - HEVERLEE Tel.: +32(0)16/32.11.07 Any errors in spelling, tact or fact are transmission errors Disclaimer: http://www.kuleuven.be/cwis/email_disclaimer.htm -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#500997: axiom_20050901-10.1(sparc/unstable): FTBFS on sparc, code.o': No such file or directory
Package: axiom Version: 20050901-10.1 Severity: serious There was an error while trying to autobuild your package: Automatic build of axiom_20050901-10.1 on spontini by sbuild/sparc 99.99 Build started at 20081002-2320 [...] ** Using build dependencies supplied by package: Build-Depends: debhelper ( 4.0.0), gcl (= 2.6.7-45), libgmp3-dev, libncurses5-dev, libreadline5-dev | libreadline-dev, libx11-dev, libxt-dev, x11proto-core-dev, libxpm-dev, x11-common, texlive-latex-base, gawk, sharutils, ghostscript, gsfonts, libxmu-dev, libxaw7-dev [...] compiling ESTOOLS.spad to ESTOOLS.NRLIB copying ESTOOLS.NRLIB to ESTOOLS.o compiling EXPEXPAN.spad to EXPEXPAN.NRLIB copying EXPEXPAN.NRLIB to EXPEXPAN.o cp: cannot stat `/build/buildd/axiom-20050901/int/algebra/EXPEXPAN.NRLIB/code.o': No such file or directory make[4]: *** [/build/buildd/axiom-20050901/mnt/linux/algebra/EXPEXPAN.o] Error 1 make[4]: Leaving directory `/build/buildd/axiom-20050901/src/algebra' make[3]: *** [algebradir] Error 2 make[3]: Leaving directory `/build/buildd/axiom-20050901/src' make[2]: *** [srcdir] Error 2 make[2]: Leaving directory `/build/buildd/axiom-20050901' make[1]: *** [all] Error 2 make[1]: Leaving directory `/build/buildd/axiom-20050901' make: *** [build-stamp] Error 2 dpkg-buildpackage: failure: debian/rules build gave error exit status 2 A full build log can be found at: http://buildd.debian.org/build.php?arch=sparcpkg=axiomver=20050901-10.1 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#500492: A better patch for this bug
The appended patch fixes the root cause. gcc -O2 optimizes out some
tests.
Thiemo
--- libcaca-0.99.beta15/configure.ac~ 2008-09-27 19:11:55.0 +0100
+++ libcaca-0.99.beta15/configure.ac2008-10-03 10:21:19.0 +0100
@@ -112,13 +112,13 @@ AC_TRY_COMPILE([#include windows.h],[S
[AC_MSG_RESULT(no)])
AC_MSG_CHECKING(for fsin/fcos)
-AC_TRY_COMPILE([],[double x; asm(fsin\n\tfcos:=t(x):);],
+AC_TRY_COMPILE([],[double x; volatile asm(fsin\n\tfcos:=t(x):);],
[AC_MSG_RESULT(yes)
AC_DEFINE(HAVE_FSIN_FCOS, 1, [Define to 1 if you have the `fsin' and `fcos'
operands.])],
[AC_MSG_RESULT(no)])
AC_MSG_CHECKING(for fldln2/fxch/fyl2x)
-AC_TRY_COMPILE([],[double x; asm(fldln2; fldln2; fxch; fyl2x:=t(x):);],
+AC_TRY_COMPILE([],[double x; volatile asm(fldln2; fldln2; fxch;
fyl2x:=t(x):);],
[AC_MSG_RESULT(yes)
AC_DEFINE(HAVE_FLDLN2, 1, [Define to 1 if you have the `fldln2' and other
floating points operands.])],
[AC_MSG_RESULT(no)])
--- libcaca-0.99.beta15.old/configure 2008-09-27 21:30:35.0 +
+++ libcaca-0.99.beta15/configure 2008-10-03 09:25:04.0 +
@@ -21854,7 +21854,7 @@ cat conftest.$ac_ext _ACEOF
int
main ()
{
-double x; asm(fsin\n\tfcos:=t(x):);
+double x; volatile asm(fsin\n\tfcos:=t(x):);
;
return 0;
}
@@ -21905,7 +21905,7 @@ cat conftest.$ac_ext _ACEOF
int
main ()
{
-double x; asm(fldln2; fldln2; fxch; fyl2x:=t(x):);
+double x; volatile asm(fldln2; fldln2; fxch; fyl2x:=t(x):);
;
return 0;
}
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#498144: remove sympa from lenny?
Hi, sympa has two RC bugs open for about one month, #496520 about insecure usage of tmp (which looks at least partially fixed upstream, but has no maintainer response) and #498144 about problems on upgrade (with an initial maintainer response will investigate, also happened to people at the last security upgrades, but no visible activity since). Unless the maintainer (or perhaps Olivier who forwarded the first bug upstream, CCed) resolve these bugs soon, it might be better to not release sympa with lenny. It does not seem to have reverse dependencies. There are a few users (double digit popcon), but not exceedingly many. Kind regards T. -- Thomas Viehmann, http://thomas.viehmann.net/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#475036: Possible workaround
Hi, for me it worked to generate version.h and utsrelease.h in include/linux manually. Maybe you want to try it. For 2.6.26.5 you'll need the following in version.h: #define LINUX_VERSION_CODE 132634 #define KERNEL_VERSION(a,b,c) (((a) 16) + ((b) 8) + (c)) (The LINUX_VERSION_CODE is calculated like this: $VERSION * 65536 + $PATCHLEVEL * 256 + $SUBPATCHLEVEL (with $VERSION = 2, $PATCHLEVEL = 6, $SUBPATCHLEVEL = 26), see the top-level Makefile for more information). utsrelease.h contains something like: #define UTS_RELEASE 2.6.26.5[LOCAL VERSION STRING] (The [LOCAL VERSION STRING] is the part you can either set with the CONFIG_LOCALVERSION option in the kernel configuration or by using --append-to-version) The above examples are for version 2.6.26.5, but it works for other kernel versions too. German speaking people might want to check my howto at [0]. Greetings, Kai [0] http://wiki.debianforum.de/DebianizedLinuxKernel -- Kai Wasserbäch (Kai Wasserbaech) E-Mail: [EMAIL PROTECTED] Jabber (debianforum.de): Drizzt URL: http://wiki.debianforum.de/Drizzt_Do%27Urden GnuPG: 0xE1DE59D2 0600 96CE F3C8 E733 E5B6 1587 A309 D76C E1DE 59D2 (http://pgpkeys.pca.dfn.de/pks/lookup?search=0xE1DE59D2fingerprint=onhash=onop=vindex) signature.asc Description: OpenPGP digital signature
Bug#500991: incorrect regular expression?
On Fri, Oct 03, 2008 at 11:50:01AM +0200, Rik Theys wrote: The machine is an HP DL380G5 with an HP smart array P400i raid controller. I was just testing the multipath support because I will need it later on. The RAID disk is not available using multiple paths, but multipath should still list it as one path (IMHO). With the default blacklist info and the patch checker configured for LOGICAL VOLUME devices, the callout still fails, because it checks for /dev/cciss!c0d0 instead of /dev/cciss/c0d0: You'll later need multipath support with cciss or with something else? As I wrote, for proper cciss support current multipath git is needed. This is AFAIK the only hardware that is supported in upstream git but not in any released version. All the rest (FC, iSCSI) should work well. I've just uploaded a new version of multipath-tools that blacklists cciss. I'd be great if you could test if your cciss disks get correctly blacklisted. In case you desperately need cciss, please file a wishlist bug to package up current git. I will try to do it soon then - help appreciated of course. -- Guido -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#471642: remove pango-graphite from lenny
2008/10/2 Adeodato Simó [EMAIL PROTECTED]: * Thomas Viehmann [Wed, 01 Oct 2008 08:59:38 +0200]: Hi, pango-graphite owns a critical bug, #471642 and dupes, since April with no visible maintainer activity. As it's not been released with stable before and has no reverse dependencies, it appears to be an ideal removal candidate. Marked for removal. Yes, I made a mess of that not updating the bug. I've checked with upstream and they have some ideas to try (incidentally it is a firefox bug that leads down the bad code path, but still a bug that needs fixed in graphite/pango-graphite). If I can get a fixed package uploaded in the next day or three would it get back in? If so I'll let you know tomorrow if that will happen or not. Regards, Daniel
Processed: tagging 496954
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.9.26 tags 496954 + patch Bug#496954: bind9: Fails to start due to SIGSEGV There were no tags set. 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#500991: incorrect regular expression?
On Fri, Oct 03, 2008 at 01:12:16PM +0200, Rik Theys wrote: I won't need cciss support in the near future as I will be connecting FC disks to the server. I will test the new version of multipath-tools O.k., this should work without problems then. (with cciss blacklisted), if you give me the location of the .deb. Or will it enter unstable? It will enter unstable. I've uploaded for ppc so i386 and amd64 might not be available before tomorrow. If I still have a spare server with an cciss card when the git version is packaged, I will help test/debug it. Great. Thanks for your feedback, -- Guido -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#500991: incorrect regular expression?
Guido Günther wrote: On Fri, Oct 03, 2008 at 11:50:01AM +0200, Rik Theys wrote: The machine is an HP DL380G5 with an HP smart array P400i raid controller. I was just testing the multipath support because I will need it later on. The RAID disk is not available using multiple paths, but multipath should still list it as one path (IMHO). With the default blacklist info and the patch checker configured for LOGICAL VOLUME devices, the callout still fails, because it checks for /dev/cciss!c0d0 instead of /dev/cciss/c0d0: You'll later need multipath support with cciss or with something else? As I wrote, for proper cciss support current multipath git is needed. This is AFAIK the only hardware that is supported in upstream git but not in any released version. All the rest (FC, iSCSI) should work well. I've just uploaded a new version of multipath-tools that blacklists cciss. I'd be great if you could test if your cciss disks get correctly blacklisted. In case you desperately need cciss, please file a wishlist bug to package up current git. I will try to do it soon then - help appreciated of course. I won't need cciss support in the near future as I will be connecting FC disks to the server. I will test the new version of multipath-tools (with cciss blacklisted), if you give me the location of the .deb. Or will it enter unstable? If I still have a spare server with an cciss card when the git version is packaged, I will help test/debug it. Regards, Rik -- Rik Theys System Engineer KU Leuven - Dept. Elektrotechniek (ESAT) Kasteelpark Arenberg 10 B-3001 LEUVEN - HEVERLEE Tel.: +32(0)16/32.11.07 Any errors in spelling, tact or fact are transmission errors Disclaimer: http://www.kuleuven.be/cwis/email_disclaimer.htm -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#500991: marked as done (multipath-tools: Multipath-tools uses invalid scsi_id option, breaks multipath)
Your message dated Fri, 03 Oct 2008 11:02:03 +
with message-id [EMAIL PROTECTED]
and subject line Bug#500991: fixed in multipath-tools 0.4.8-13
has caused the Debian Bug report #500991,
regarding multipath-tools: Multipath-tools uses invalid scsi_id option, breaks
multipath
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)
--
500991: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=500991
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
---BeginMessage---
Package: multipath-tools
Version: 0.4.8-12
Severity: grave
Justification: renders package unusable
Hi,
I've installed multipath-tools on lenny, but it fails to find any multipath
devices. I've run multipath -v3 and it gives the following error:
cciss!c0d0: getuid = /lib/udev/scsi_id -n -g -u -d /dev/%n (controller setting)
/lib/udev/scsi_id: invalid option -- n
error calling out /lib/udev/scsi_id -n -g -u -d /dev/cciss!c0d0
The -n option is not supported by /lib/udev/scsi_id.
Adding the getuid_callout option to the defaults section of /etc/multipath.conf
without the -n option does not seem to help. It seems the section is ignored?
The version of udev on this machine is 0.125-6.
According to the man page, the default command that is issued is
/lib/udev/scsi_id -g -u -d /dev/%n, without the -n option.
Regards,
Rik
-- Package-specific info:
Contents of /etc/multipath.conf:
defaults {
udev_dir/dev
polling_interval10
selectorround-robin 0
path_grouping_policymultibus
getuid_callout /lib/udev/scsi_id -g -u -d /dev/%n
prio_callout/bin/true
path_checkerdirectio
rr_min_io 100
rr_weight priorities
failbackimmediate
no_path_retry fail
user_friendly_names yes
}
-- System Information:
Debian Release: lenny/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.26-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages multipath-tools depends on:
ii initscripts 2.86.ds1-61Scripts for initializing and shutt
ii kpartx0.4.8-12 create device mappings for partiti
ii libaio1 0.3.107-2 Linux kernel AIO access library -
ii libc6 2.7-13 GNU C Library: Shared libraries
ii libdevmapper1.02.12:1.02.27-3The Linux Kernel Device Mapper use
ii libncurses5 5.6+20080830-1 shared libraries for terminal hand
ii libreadline5 5.2-3 GNU readline and history libraries
ii lsb-base 3.2-20 Linux Standard Base 3.2 init scrip
ii udev 0.125-6/dev/ and hotplug management daemo
multipath-tools recommends no packages.
Versions of packages multipath-tools suggests:
pn multipath-tools-boot none (no description available)
-- no debconf information
Disclaimer: http://www.kuleuven.be/cwis/email_disclaimer.htm
---End Message---
---BeginMessage---
Source: multipath-tools
Source-Version: 0.4.8-13
We believe that the bug you reported is fixed in the latest version of
multipath-tools, which is due to be installed in the Debian FTP archive:
kpartx_0.4.8-13_powerpc.deb
to pool/main/m/multipath-tools/kpartx_0.4.8-13_powerpc.deb
multipath-tools-boot_0.4.8-13_all.deb
to pool/main/m/multipath-tools/multipath-tools-boot_0.4.8-13_all.deb
multipath-tools_0.4.8-13.diff.gz
to pool/main/m/multipath-tools/multipath-tools_0.4.8-13.diff.gz
multipath-tools_0.4.8-13.dsc
to pool/main/m/multipath-tools/multipath-tools_0.4.8-13.dsc
multipath-tools_0.4.8-13_powerpc.deb
to pool/main/m/multipath-tools/multipath-tools_0.4.8-13_powerpc.deb
multipath-udeb_0.4.8-13_powerpc.udeb
to pool/main/m/multipath-tools/multipath-udeb_0.4.8-13_powerpc.udeb
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Guido Günther [EMAIL PROTECTED] (supplier of updated multipath-tools package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [EMAIL PROTECTED])
Bug#498144: remove sympa from lenny?
On Fri, 03 Oct 2008 Thomas Viehmann [EMAIL PROTECTED] wrote: Hi, sympa has two RC bugs open for about one month, #496520 about insecure usage of tmp (which looks at least partially fixed upstream, but has no maintainer response) and #498144 about problems on upgrade (with an initial maintainer response will investigate, also happened to people at the last security upgrades, but no visible activity since). Unless the maintainer (or perhaps Olivier who forwarded the first bug upstream, CCed) resolve these bugs soon, it might be better to not release sympa with lenny. It does not seem to have reverse dependencies. There are a few users (double digit popcon), but not exceedingly many. I'm a dedicated user of sympa and hope that the problems will be resolved. It is a really good piece of software and it would be a pity to remove it from lenny. Best regards Janusz -- , dr hab. Janusz S. Bien, prof. UW - Uniwersytet Warszawski (Katedra Lingwistyki Formalnej) Prof. Janusz S. Bien - Warsaw University (Department of Formal Linguistics) [EMAIL PROTECTED], [EMAIL PROTECTED], http://fleksem.klf.uw.edu.pl/~jsbien/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#471642: remove pango-graphite from lenny
Daniel Glassey wrote: Yes, I made a mess of that not updating the bug. I've checked with upstream and they have some ideas to try (incidentally it is a firefox bug that leads down the bad code path, but still a bug that needs fixed in graphite/pango-graphite). If I can get a fixed package uploaded in the next day or three would it get back in? If so I'll let you know tomorrow if that will happen or not. I don't get a say in this, but more then 7 months as response time is not an advertisement that it's well-maintained. One month can happen[1], two months probably as well, but seven? We would not want to have bugs of the the-most-commonly-used-browser-is-completely-unusable-if-I-made-the-mistake-to-install-your-package-type in a stable release. Kind regards T. 1. Somewhere in the Developer's reference, you are told to address these bugs within two weeks. -- Thomas Viehmann, http://thomas.viehmann.net/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#489044: marked as done (printconf: Tries to invoke wrong init script)
Your message dated Fri, 03 Oct 2008 11:32:02 + with message-id [EMAIL PROTECTED] and subject line Bug#489044: fixed in foomatic-gui 0.7.9 has caused the Debian Bug report #489044, regarding printconf: Tries to invoke wrong init script to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [EMAIL PROTECTED] immediately.) -- 489044: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=489044 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: printconf Version: 0.7.8 Severity: normal When I ran printconf today it didn't complete properly because it tried to invoke /etc/init.d/cupsys but my system has /etc/init.d/cups instead. -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.25.9 (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages printconf depends on: ii cups [cupsys]1.3.7-7 Common UNIX Printing System(tm) - ii cups-client [cupsys-clie 1.3.7-7 Common UNIX Printing System(tm) - ii cupsys 1.3.7-7 Common UNIX Printing System (trans ii cupsys-client1.3.7-7 Common UNIX Printing System (trans ii debconf [debconf-2.0]1.5.22 Debian configuration management sy ii foomatic-db 20080211-2 OpenPrinting printer support - dat ii foomatic-db-gutenprint 5.0.2-2 OpenPrinting printer support - dat ii foomatic-db-hpijs20080211-1 OpenPrinting printer support - dat ii ghostscript-x [gs-esp] 8.62.dfsg.1-2.1 The GPL Ghostscript PostScript/PDF ii gs-esp 8.62.dfsg.1-2.1 Transitional package ii openprinting-ppds20080211-2 OpenPrinting printer support - Pos ii python 2.5.2-1 An interactive high-level object-o ii python-foomatic 0.7.8 Python interface to the Foomatic p printconf recommends no packages. -- debconf information: printconf/setup_printers: true printconf/printconf_run: true ---End Message--- ---BeginMessage--- Source: foomatic-gui Source-Version: 0.7.9 We believe that the bug you reported is fixed in the latest version of foomatic-gui, which is due to be installed in the Debian FTP archive: foomatic-gui_0.7.9.dsc to pool/main/f/foomatic-gui/foomatic-gui_0.7.9.dsc foomatic-gui_0.7.9.tar.gz to pool/main/f/foomatic-gui/foomatic-gui_0.7.9.tar.gz foomatic-gui_0.7.9_all.deb to pool/main/f/foomatic-gui/foomatic-gui_0.7.9_all.deb printconf_0.7.9_all.deb to pool/main/f/foomatic-gui/printconf_0.7.9_all.deb python-foomatic_0.7.9_all.deb to pool/main/f/foomatic-gui/python-foomatic_0.7.9_all.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Chris Lawrence [EMAIL PROTECTED] (supplier of updated foomatic-gui package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Fri, 03 Oct 2008 06:12:43 -0500 Source: foomatic-gui Binary: foomatic-gui printconf python-foomatic Architecture: source all Version: 0.7.9 Distribution: unstable Urgency: medium Maintainer: Chris Lawrence [EMAIL PROTECTED] Changed-By: Chris Lawrence [EMAIL PROTECTED] Description: foomatic-gui - GNOME interface for configuring the Foomatic printer filter syste printconf - automatically configures USB and parallel printers with CUPS python-foomatic - Python interface to the Foomatic printer database Closes: 489044 Changes: foomatic-gui (0.7.9) unstable; urgency=medium . * Fix cupsys - cups breakage. (Closes: #489044) * Also fixup gs - ghostscript transition. Checksums-Sha1: e98cb77be4abed38224c69798f9be6f7341fedaa 908 foomatic-gui_0.7.9.dsc bec2ffd12532a8e1b5c23a7b59cf4fe2edd1fe21 123791 foomatic-gui_0.7.9.tar.gz fe2ea754e5d2ebba14b8f804e998f6fa1b4db491 60596 foomatic-gui_0.7.9_all.deb 5a2764a32649605746ee3f5ec08c4dedc27b27da 17178 printconf_0.7.9_all.deb ae5aa651a1bf3b3bb9b398d3b3ee90f76266c343 22380 python-foomatic_0.7.9_all.deb Checksums-Sha256: ff96c7b85ca3506e0754023f2463f2dfb1f107e9f6f1e66a82b3ba063408214a 908 foomatic-gui_0.7.9.dsc
Bug#498144: remove sympa from lenny?
I'm another Olivier, but I can provide some feedback still. As far as we're concerned all reported bugs, regarding insecure usage of tmp, have been fixed in Sympa. It's now up to the Debian maintainer to apply the patches to the Debian package. If we've missed something, please let us know... Thomas Viehmann a écrit : sympa has two RC bugs open for about one month, #496520 about insecure usage of tmp (which looks at least partially fixed upstream, but has no maintainer response) and #498144 about problems on upgrade (with an initial maintainer response will investigate, also happened to people at the last security upgrades, but no visible activity since). Unless the maintainer (or perhaps Olivier who forwarded the first bug upstream, CCed) resolve these bugs soon, it might be better to not release sympa with lenny. It does not seem to have reverse dependencies. There are a few users (double digit popcon), but not exceedingly many. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#498144: [sympa-users] Re: Bug#498144: remove sympa from lenny?
I am a dedicated sympa user too -- it would be a real shame if this couldn't be brough up to date. -A On Fri, 2008-10-03 at 13:36 +0200, Janusz S. Bień wrote: On Fri, 03 Oct 2008 Thomas Viehmann [EMAIL PROTECTED] wrote: Hi, sympa has two RC bugs open for about one month, #496520 about insecure usage of tmp (which looks at least partially fixed upstream, but has no maintainer response) and #498144 about problems on upgrade (with an initial maintainer response will investigate, also happened to people at the last security upgrades, but no visible activity since). Unless the maintainer (or perhaps Olivier who forwarded the first bug upstream, CCed) resolve these bugs soon, it might be better to not release sympa with lenny. It does not seem to have reverse dependencies. There are a few users (double digit popcon), but not exceedingly many. I'm a dedicated user of sympa and hope that the problems will be resolved. It is a really good piece of software and it would be a pity to remove it from lenny. Best regards Janusz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#496520: Bug#498144: remove sympa from lenny?
Hi Janusz, Olivier, thanks for taking interest in the Debian packaging of sympa. Olivier Salaün wrote: As far as we're concerned all reported bugs, regarding insecure usage of tmp, have been fixed in Sympa. It's now up to the Debian maintainer to apply the patches to the Debian package. Yeah, that seems to be fixed and easy enough to put in the current package. I'd personally prefer to have the example/POD code also fixed to not provide insecure code for copy paste, but that might not be fatal, so if it were just that, it could be fixed easily enough by a maintainer or non-maintainer upoload. The upgrade problem reported in #498144 seems to be completely untackled up to now, though. Again, if you managed to find out what exactly it is (it could either be just in the packaging or also involving sympa itself), I'd be more than happy to make a Debian package out of a fix should the maintainer be temporarily unavailable. At one month of apparently nobody having an idea what is going on, it is not too clear to me that that will happen in time for lenny. Kind regards T. -- Thomas Viehmann, http://thomas.viehmann.net/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#501021: jasper: CVE-2008-352[0-2] multiple integer overflows in jas_alloc calls
Package: jasper
Severity: grave
Tags: security patch
Hi,
the following CVE (Common Vulnerabilities Exposures) ids were
published for jasper.
CVE-2008-3522[0]:
| Buffer overflow in the jas_stream_printf function in
| libjasper/base/jas_stream.c in JasPer 1.900.1 might allow
| context-dependent attackers to have an unknown impact via vectors
| related to the mif_hdr_put function and use of vsprintf.
CVE-2008-3521[1]:
| The jas_stream_tmpfile function in libjasper/base/jas_stream.c in
| JasPer 1.900.1 allows local users to overwrite arbitrary files via a
| symlink attack on a tmp.XX temporary file.
CVE-2008-3520[2]:
| Multiple integer overflows in JasPer 1.900.1 might allow
| context-dependent attackers to have an unknown impact via a crafted
| image file, related to integer multiplication for memory allocation.
CVE-2008-3521 is not really important as the file is opened
with O_EXCL but a patch for all these three issues is
attached.
If you fix the vulnerabilities please also make sure to include the
CVE ids in your changelog entry.
For further information see:
[0] http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2008-3522
http://security-tracker.debian.net/tracker/CVE-2008-3522
[1] http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2008-3521
http://security-tracker.debian.net/tracker/CVE-2008-3521
[2] http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2008-3520
http://security-tracker.debian.net/tracker/CVE-2008-3520
--
Nico Golde - http://www.ngolde.de - [EMAIL PROTECTED] - GPG: 0x73647CFF
For security reasons, all text in this mail is double-rot13 encrypted.
diff -Nurad jasper-1.900.1.orig/src/libjasper/base/jas_cm.c jasper-1.900.1.new/src/libjasper/base/jas_cm.c
--- jasper-1.900.1.orig/src/libjasper/base/jas_cm.c 2007-01-19 22:43:05.0 +0100
+++ jasper-1.900.1.new/src/libjasper/base/jas_cm.c 2008-10-03 14:17:55.0 +0200
@@ -704,8 +704,7 @@
{
jas_cmpxform_t **p;
assert(n = pxformseq-numpxforms);
- p = (!pxformseq-pxforms) ? jas_malloc(n * sizeof(jas_cmpxform_t *)) :
- jas_realloc(pxformseq-pxforms, n * sizeof(jas_cmpxform_t *));
+ p = jas_realloc2(pxformseq-pxforms, n, sizeof(jas_cmpxform_t *));
if (!p) {
return -1;
}
@@ -889,13 +888,13 @@
jas_cmshapmatlut_cleanup(lut);
if (curv-numents == 0) {
lut-size = 2;
- if (!(lut-data = jas_malloc(lut-size * sizeof(jas_cmreal_t
+ if (!(lut-data = jas_alloc2(lut-size, sizeof(jas_cmreal_t
goto error;
lut-data[0] = 0.0;
lut-data[1] = 1.0;
} else if (curv-numents == 1) {
lut-size = 256;
- if (!(lut-data = jas_malloc(lut-size * sizeof(jas_cmreal_t
+ if (!(lut-data = jas_alloc2(lut-size, sizeof(jas_cmreal_t
goto error;
gamma = curv-ents[0] / 256.0;
for (i = 0; i lut-size; ++i) {
@@ -903,7 +902,7 @@
}
} else {
lut-size = curv-numents;
- if (!(lut-data = jas_malloc(lut-size * sizeof(jas_cmreal_t
+ if (!(lut-data = jas_alloc2(lut-size, sizeof(jas_cmreal_t
goto error;
for (i = 0; i lut-size; ++i) {
lut-data[i] = curv-ents[i] / 65535.0;
@@ -953,7 +952,7 @@
return -1;
}
}
- if (!(invlut-data = jas_malloc(n * sizeof(jas_cmreal_t
+ if (!(invlut-data = jas_alloc2(n, sizeof(jas_cmreal_t
return -1;
invlut-size = n;
for (i = 0; i invlut-size; ++i) {
diff -Nurad jasper-1.900.1.orig/src/libjasper/base/jas_icc.c jasper-1.900.1.new/src/libjasper/base/jas_icc.c
--- jasper-1.900.1.orig/src/libjasper/base/jas_icc.c 2007-01-19 22:43:05.0 +0100
+++ jasper-1.900.1.new/src/libjasper/base/jas_icc.c 2008-10-03 14:17:55.0 +0200
@@ -373,7 +373,7 @@
jas_icctagtab_t *tagtab;
tagtab = prof-tagtab;
- if (!(tagtab-ents = jas_malloc(prof-attrtab-numattrs *
+ if (!(tagtab-ents = jas_alloc2(prof-attrtab-numattrs,
sizeof(jas_icctagtabent_t
goto error;
tagtab-numents = prof-attrtab-numattrs;
@@ -522,7 +522,7 @@
}
if (jas_iccgetuint32(in, tagtab-numents))
goto error;
- if (!(tagtab-ents = jas_malloc(tagtab-numents *
+ if (!(tagtab-ents = jas_alloc2(tagtab-numents,
sizeof(jas_icctagtabent_t
goto error;
tagtabent = tagtab-ents;
@@ -743,8 +743,7 @@
{
jas_iccattr_t *newattrs;
assert(maxents = tab-numattrs);
- newattrs = tab-attrs ? jas_realloc(tab-attrs, maxents *
- sizeof(jas_iccattr_t)) : jas_malloc(maxents * sizeof(jas_iccattr_t));
+ newattrs = jas_realloc2(tab-attrs, maxents, sizeof(jas_iccattr_t));
if (!newattrs)
return -1;
tab-attrs = newattrs;
@@ -999,7 +998,7 @@
if (jas_iccgetuint32(in, curv-numents))
goto error;
- if (!(curv-ents = jas_malloc(curv-numents * sizeof(jas_iccuint16_t
+ if (!(curv-ents = jas_alloc2(curv-numents, sizeof(jas_iccuint16_t
goto error;
for (i = 0; i curv-numents; ++i) {
if (jas_iccgetuint16(in, curv-ents[i]))
@@ -1100,7 +1099,7 @@
if (jas_iccgetuint32(in, txtdesc-uclangcode) ||
jas_iccgetuint32(in, txtdesc-uclen))
goto error;
- if (!(txtdesc-ucdata = jas_malloc(txtdesc-uclen * 2)))
+ if (!(txtdesc-ucdata =
Bug#501026: ipsec-tools: CVE-2008-3652 denial of service for authenticated attackers
Package: ipsec-tools
Severity: grave
Tags: security patch
Hi,
the following CVE (Common Vulnerabilities Exposures) id was
published for ipsec-tools.
CVE-2008-3652[0]:
| src/racoon/handler.c in racoon in ipsec-tools does not remove an
| orphaned ph1 (phase 1) handle when it has been initiated remotely,
| which allows remote attackers to cause a denial of service (resource
| consumption).
A patch of the relevant changes extracted from upstream rcs
is attached.
If you fix the vulnerability please also make sure to include the
CVE id in your changelog entry.
For further information see:
[0] http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2008-3652
http://security-tracker.debian.net/tracker/CVE-2008-3652
--
Nico Golde - http://www.ngolde.de - [EMAIL PROTECTED] - GPG: 0x73647CFF
For security reasons, all text in this mail is double-rot13 encrypted.
diff --git a/src/racoon/isakmp.c b/src/racoon/isakmp.c
index 5b81e5b..4d4e2f2 100644
--- a/src/racoon/isakmp.c
+++ b/src/racoon/isakmp.c
@@ -801,20 +801,24 @@ ph1_main(iph1, msg)
[iph1-side]
[iph1-status])(iph1, msg);
if (error != 0) {
-#if 0
+
/* XXX
* When an invalid packet is received on phase1, it should
* be selected to process this packet. That is to respond
* with a notify and delete phase 1 handler, OR not to respond
- * and keep phase 1 handler.
+ * and keep phase 1 handler. However, in PHASE1ST_START when
+ * acting as RESPONDER we must not keep phase 1 handler or else
+ * it will stay forever.
*/
- plog(LLV_ERROR, LOCATION, iph1-remote,
- failed to pre-process packet.\n);
- return -1;
-#else
- /* ignore the error and keep phase 1 handler */
- return 0;
-#endif
+
+ if (iph1-side == RESPONDER iph1-status == PHASE1ST_START) {
+ plog(LLV_ERROR, LOCATION, iph1-remote,
+failed to pre-process packet.\n);
+ return -1;
+ } else {
+ /* ignore the error and keep phase 1 handler */
+ return 0;
+ }
}
#ifndef ENABLE_FRAG
pgp1r2SUrKQtD.pgp
Description: PGP signature
Bug#500910: CVE-2008-4194 denial of service
tags 500910 + patch
thanks
Hi,
* Pierre Habouzit [EMAIL PROTECTED] [2008-10-02 21:43]:
On Thu, Oct 02, 2008 at 04:25:54PM +, Christian Perrier wrote:
Quoting Nico Golde ([EMAIL PROTECTED]):
Package: pdnsd
Severity: grave
Tags: security
Hi,
the following CVE (Common Vulnerabilities Exposures) id was
published for pdnsd.
If someone fixes this, fixing #490047 would be much appreciated as
well by the l10n folks (and this is certainly not invasive).
This becomes an habit :P
But Yes I'll fix those at the same time.
A patch for CVE-2008-4194 is attached.
Cheers
Nico
--
Nico Golde - http://www.ngolde.de - [EMAIL PROTECTED] - GPG: 0x73647CFF
For security reasons, all text in this mail is double-rot13 encrypted.
--- pdnsd-1.2.6/src/dns_query.c~ 2007-08-05 12:43:08.0 +0200
+++ pdnsd-1.2.6/src/dns_query.c 2008-07-25 09:47:03.0 +0200
@@ -1140,7 +1140,6 @@
# define ans_sec secs[0]
# define auth_sec secs[1]
# define add_sec secs[2]
- dns_cent_t *ent;
unsigned short qtype,flags,aa;
lcnt-=sizeof(dns_hdr_t);
@@ -1201,9 +1200,8 @@
rv=RC_FATALERR; /* unrecoverable error */
goto free_recvbuf_return;
}
- ent=DA_INDEX(ans_sec,0);
/* By marking DF_AUTH, we mean authoritative AND complete. */
- if (!init_cent(ent,name, 0, queryts, (aa qtype==QT_ALL)?DF_AUTH:0 DBG1)) {
+ if (!init_cent(DA_INDEX(ans_sec,0), name, 0, queryts, (aa qtype==QT_ALL)?DF_AUTH:0 DBG1)) {
rv=RC_FATALERR; /* unrecoverable error */
goto free_centarrays_recvbuf_return;
}
@@ -1286,6 +1284,7 @@
name_error:
{
/* We did not get what we wanted. Cache according to policy */
+dns_cent_t *ent=DA_INDEX(ans_sec,0);
int neg_domain_pol=global.neg_domain_pol;
if (neg_domain_pol==C_ON || (neg_domain_pol==C_AUTH st-recvbuf-aa)) {
time_t ttl=global.neg_ttl;
@@ -1468,33 +1467,37 @@
}
}
- /* Negative caching of rr sets */
- if (thint=T_MIN thint=T_MAX !ent-rr[thint-T_MIN] !st-tc) {
- /* We did not get what we wanted. Cache according to policy */
- int neg_rrs_pol=global.neg_rrs_pol;
- if (neg_rrs_pol==C_ON || (neg_rrs_pol==C_AUTH aa)) {
-time_t ttl=global.neg_ttl;
-rr_set_t *rrset=ent-rr[T_SOA-T_MIN];
-dns_cent_t *cent;
-unsigned scnt;
-/* If we received a SOA, we should take the ttl of that record. */
-if ((rrset rrset-rrs) ||
-/* Try to find a SOA record higher up the hierarchy that came with the reply. */
-((cent=lookup_cent_array(auth_sec,
- (ent-c_soa!=cundef ent-c_soa(scnt=rhnsegcnt(name)))?
- skipsegs(name,scnt-ent-c_soa):
- name))
- (rrset=cent-rr[T_SOA-T_MIN]) rrset-rrs))
-{
- time_t min=soa_minimum(rrset-rrs);
- ttl=rrset-ttl;
- if(ttlmin)
- ttl=min;
-}
-DEBUG_RHN_MSG(Caching type %s for domain %s negative with ttl %li\n,get_tname(thint),RHN2STR(name),(long)ttl);
-if (!add_cent_rrset(ent, thint, ttl, queryts, CF_NEGATIVE|flags DBG1)) {
- rv=RC_FATALERR;
- goto free_ent_centarrays_recvbuf_return;
+ {
+ /* Negative caching of rr sets */
+ dns_cent_t *ent=DA_INDEX(ans_sec,0);
+
+ if (thint=T_MIN thint=T_MAX !ent-rr[thint-T_MIN] !st-tc) {
+/* We did not get what we wanted. Cache according to policy */
+int neg_rrs_pol=global.neg_rrs_pol;
+if (neg_rrs_pol==C_ON || (neg_rrs_pol==C_AUTH aa)) {
+ time_t ttl=global.neg_ttl;
+ rr_set_t *rrset=ent-rr[T_SOA-T_MIN];
+ dns_cent_t *cent;
+ unsigned scnt;
+ /* If we received a SOA, we should take the ttl of that record. */
+ if ((rrset rrset-rrs) ||
+ /* Try to find a SOA record higher up the hierarchy that came with the reply. */
+ ((cent=lookup_cent_array(auth_sec,
+ (ent-c_soa!=cundef ent-c_soa(scnt=rhnsegcnt(name)))?
+ skipsegs(name,scnt-ent-c_soa):
+ name))
+ (rrset=cent-rr[T_SOA-T_MIN]) rrset-rrs))
+ {
+ time_t min=soa_minimum(rrset-rrs);
+ ttl=rrset-ttl;
+ if(ttlmin)
+ ttl=min;
+ }
+ DEBUG_RHN_MSG(Caching type %s for domain %s negative with ttl %li\n,get_tname(thint),RHN2STR(name),(long)ttl);
+ if (!add_cent_rrset(ent, thint, ttl, queryts, CF_NEGATIVE|flags DBG1)) {
+ rv=RC_FATALERR;
+ goto free_ent_centarrays_recvbuf_return;
+ }
}
}
}
@@ -1554,7 +1557,7 @@
rv=RC_FATALERR;
goto free_ns_ent_centarrays_recvbuf_return;
}
- **entp=*ent;
+ **entp=DA_INDEX(ans_sec,0);
rv=RC_OK;
add_additional:
{
@@ -1593,7 +1596,7 @@
free_ns_ent_centarrays_recvbuf_return:
dlist_free(*ns); *ns=NULL;
free_ent_centarrays_recvbuf_return:
- if(DA_NEL(ans_sec)=1) free_cent(ent DBG1);
+ if(DA_NEL(ans_sec)=1) free_cent(DA_INDEX(ans_sec,0) DBG1);
free_centarrays_recvbuf_return:
{
/* dns_cent_array secs[3]={ans_sec,auth_sec,add_sec}; */
pgpmUV9fZgy3s.pgp
Description: PGP signature
Processed: Re: Bug#500910: CVE-2008-4194 denial of service
Processing commands for [EMAIL PROTECTED]: tags 500910 + patch Bug#500910: CVE-2008-4194 denial of service Tags were: security Tags added: patch thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#496520: remove sympa from lenny?
Thomas Viehmann wrote: Hi, sympa has two RC bugs open for about one month, #496520 about insecure usage of tmp (which looks at least partially fixed upstream, but has no maintainer response) and #498144 about problems on upgrade (with an initial maintainer response will investigate, also happened to people at the last security upgrades, but no visible activity since). Applying the patch from http://sourcesup.cru.fr/cgi/viewvc.cgi/branches/sympa-5.4-branch/src/tools.pl?r1=4943r2=5124 should solve issue #496520, is that right? Regards Racke -- LinuXia Systems = http://www.linuxia.de/ Expert Interchange Consulting and System Administration ICDEVGROUP = http://www.icdevgroup.org/ Interchange Development Team -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#495214: marked as done (CVE-2008-3651: memory leak)
Your message dated Fri, 3 Oct 2008 15:00:43 +0200 with message-id [EMAIL PROTECTED] and subject line closing has caused the Debian Bug report #495214, regarding CVE-2008-3651: memory leak to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [EMAIL PROTECTED] immediately.) -- 495214: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=495214 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: ipsec-tools Severity: grave Tags: security Justification: user security hole Hi, the following CVE (Common Vulnerabilities Exposures) id was published for ipsec-tools. CVE-2008-3651[0]: | Memory leak in racoon/proposal.c in the racoon daemon in ipsec-tools | before 0.7.1 allows remote authenticated users to cause a denial of | service (memory consumption) via invalid proposals. There is an upstream discussion going on here[1]. If you fix the vulnerability please also make sure to include the CVE id in your changelog entry. Cheers Steffen For further information see: [0] http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2008-3651 http://security-tracker.debian.net/tracker/CVE-2008-3651 [1] http://sourceforge.net/mailarchive/forum.php?thread_name=48a0c7a0.qPeWZAE0PY8bDDq%2B%25olel%40ans.plforum_name=ipsec-tools-devel ---End Message--- ---BeginMessage--- Version: 1:0.7.1-1 -- Nico Golde - http://www.ngolde.de - [EMAIL PROTECTED] - GPG: 0x73647CFF For security reasons, all text in this mail is double-rot13 encrypted. pgpyCp3hJpYYj.pgp Description: PGP signature ---End Message---
Bug#501029: flashplugin-nonfree: Plugin deregistered as an alternative during upgrade
Package: flashplugin-nonfree Version: 1:1.7.2+fp10.20080811 Severity: grave Justification: renders package unusable I upgraded from the version of the package in unstable to the version in experimental, and Flash would no longer work. The symlink in /etc/alternatives/flash-mozilla.so pointes to /usr/lib/nspluginwrapper/plugins/npwrapper.libflashplayer.so but that file does not exist; in fact, /usr/lib/nspluginwrapper/plugins is empty! Thinking this may be a reoccurance of the other alternatives-related bug, I ran 'update-alternatives --config flash-mozilla.so', but this fails with the error, 'There is no program which provides flash-mozilla.so'. Looking at the messages from the installation, there are a few strange messages; maybe they have something to do with this: 2008-10-03 14:07:54 (366 KB/s) - `./flashplayer10_install_linux_081108.tar.gz' saved [4035433/4035433] *** NSPlugin Viewer *** ERROR: libcurl.so.3: cannot open shared object file: No such file or directory nspluginwrapper: no appropriate viewer found for /usr/lib/flashplugin-nonfree/libflashplayer.so However the postinst script seems to have exited without indicating that there was an error, as dpkg now happily reports the plugin as installed ok. -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (530, 'testing'), (520, 'unstable'), (510, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.26-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages flashplugin-nonfree depends on: ii debconf [debconf-2.0] 1.5.22Debian configuration management sy ii fontconfig 2.6.0-1 generic font configuration library ii gnupg 1.4.9-3 GNU privacy guard - a free PGP rep ii ia32-libs-gtk 2.7 GTK+ ia32 shared libraries ii lib32z11:1.2.3.3.dfsg-12 compression library - 32 bit runti ii nspluginwrapper0.9.91.5-2A wrapper to run Netscape plugins ii wget 1.11.4-2 retrieves files from the web flashplugin-nonfree recommends no packages. Versions of packages flashplugin-nonfree suggests: ii iceweasel 3.0.1-1lightweight web browser based on M pn konqueror-nsplugins none (no description available) pn msttcorefonts none (no description available) ii ttf-dejavu2.25-3 Metapackage to pull in ttf-dejavu- pn ttf-xfree86-nonfree none (no description available) ii x-ttcidfont-conf 29 TrueType and CID fonts configurati pn xfs none (no description available) -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#496520: remove sympa from lenny?
Hi, thanks for the swift response! Stefan Hornburg (Racke) wrote: Applying the patch from http://sourcesup.cru.fr/cgi/viewvc.cgi/branches/sympa-5.4-branch/src/tools.pl?r1=4943r2=5124 should solve issue #496520, is that right? As I said, I'd personally prefer to have the example/POD code also fixed to not provide insecure code for copy paste, but that might not be fatal. It's the other bug I'm more concerned about (and sympa seems complex enough to make tracking that down difficult for random-NMU-ers-to-be). Kind regads T. -- Thomas Viehmann, http://thomas.viehmann.net/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#498144: remove sympa from lenny?
Thomas Viehmann wrote: Hi, sympa has two RC bugs open for about one month, #496520 about insecure usage of tmp (which looks at least partially fixed upstream, but has no maintainer response) and #498144 about problems on upgrade (with an initial maintainer response will investigate, also happened to people at the last security upgrades, but no visible activity since). This one is more difficult, as I wasn't yet able to reproduce it. Regards Racke -- LinuXia Systems = http://www.linuxia.de/ Expert Interchange Consulting and System Administration ICDEVGROUP = http://www.icdevgroup.org/ Interchange Development Team -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#496520: remove sympa from lenny?
Le vendredi 03 octobre 2008 à 12:43 +0200, Thomas Viehmann a écrit : It does not seem to have reverse dependencies. There are a few users (double digit popcon), but not exceedingly many. As it is on the servers, I assume a single mailing-list manager may have thousands of users... so popularity contest may not be relevant here AFAICT. For the rest of the complains, I have unfortunately no time to help at the moment, but I'm not the maintainer either, so that doesn't make a difference. Still, /me would be worried if sympa was out of Debian :-/ My 2 cents, -- Olivier BERGER [EMAIL PROTECTED] http://www-public.it-sudparis.eu/~berger_o/ - OpenPGP-Id: 1024D/6B829EEC Ingénieur Recherche - Dept INF Institut TELECOM, SudParis (http://www.it-sudparis.eu/), Evry (France) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#500644: marked as done (nvidia-kernel-source: Cannot build on 2.6.24-etchnhalf.1-amd64)
Your message dated Fri, 3 Oct 2008 15:26:17 +0200
with message-id [EMAIL PROTECTED]
and subject line fixed in unstable
has caused the Debian Bug report #500644,
regarding nvidia-kernel-source: Cannot build on 2.6.24-etchnhalf.1-amd64
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)
--
500644: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=500644
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
---BeginMessage---
Package: nvidia-kernel-source
Version: 1.0.8776-4
Severity: grave
Justification: renders package unusable
Attempts to build the package according to the instructions in
/usr/share/doc/nvidia-kernel-source/README.Debian fail with a bunch
of complaints about undeclared identifiers; it appears to not be
including the correct collection of definitions from the kernel headers.
It fails with both 'module-assistant auto-install nvidia' and the
set of instructions for using a Debian-supplied kernel.
I've attached the failure log for the auto-install method.
-- System Information:
Debian Release: 4.0
APT prefers stable
APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.24-etchnhalf.1-amd64
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Versions of packages nvidia-kernel-source depends on:
ii debhelper 5.0.42 helper programs for debian/rules
ii dpatch2.0.21 patch maintenance system for Debia
ii make 3.81-2 The GNU version of the make util
ii sed 4.1.5-1The GNU sed stream editor
Versions of packages nvidia-kernel-source recommends:
ii devscripts2.9.26 Scripts to make the life of a Debi
ii kernel-package10.067 A utility for building Linux kerne
ii nvidia-glx1.0.8776-4 NVIDIA binary XFree86 4.x driver
-- no debconf information
/usr/bin/make -f debian/rules clean
make[1]: Entering directory `/usr/src/modules/nvidia-kernel'
# select which makefile to use.
rm -f /usr/src/modules/nvidia-kernel/nv/Makefile || true
if [ 6 = 6 ]; then \
cd /usr/src/modules/nvidia-kernel/nv ; \
ln -s Makefile.kbuild Makefile ; \
cd .. ; \
if [ 0 = 1 ] ; then \
dpatch apply 04_minion ; \
fi ; \
if [ 0 = 1 ]; then \
dpatch apply 01_sysfs ; \
dpatch status 01_sysfs patch-stamp ; \
dpatch apply 02_pcialias ; \
dpatch status 02_pcialias patch-stamp ; \
fi ; \
fi
if [ 6 = 4 ]; then \
cd /usr/src/modules/nvidia-kernel/nv ; \
ln -s Makefile.nvidia Makefile ; \
cd .. ; \
fi
if [ -e patch-stamp ]; then \
dpatch deapply-all ; \
rm -rf patch-stamp debian/patched ; \
fi
if [ -f /usr/src/modules/nvidia-kernel/debian/control.template ]; then \
cp /usr/src/modules/nvidia-kernel/debian/control.template
/usr/src/modules/nvidia-kernel/debian/control; \
fi
dh_testroot
rm -f build-stamp configure-stamp
/usr/bin/make clean SYSSRC=/lib/modules/2.6.24-etchnhalf.1-amd64/build -C
/usr/src/modules/nvidia-kernel/nv -f Makefile
make[2]: Entering directory `/usr/src/modules/nvidia-kernel/nv'
rm -f -f nv.o nv-vm.o os-agp.o os-interface.o os-registry.o nv-i2c.o nv.o
nv-vm.o os-agp.o os-interface.o os-registry.o nv-i2c.o nvidia.mod.o
rm -f -f build-in.o nv-linux.o *.d .*.{cmd,flags}
rm -f -f nvidia.{o,ko,mod.{o,c}} nv_compiler.h *~
rm -f -f stprof stprof.o symtab.h
rm -f -rf .tmp_versions
make[2]: Leaving directory `/usr/src/modules/nvidia-kernel/nv'
rm -f /usr/src/modules/nvidia-kernel/nv/Makefile || true;
rm /usr/src/modules/nvidia-kernel/nv/gcc-check
rm /usr/src/modules/nvidia-kernel/nv/cc-sanity-check
dh_clean
rm /usr/src/modules/nvidia-kernel/debian/control
rm /usr/src/modules/nvidia-kernel/debian/dirs
rm /usr/src/modules/nvidia-kernel/debian/override
make[1]: Leaving directory `/usr/src/modules/nvidia-kernel'
echo ROOT_CMD =
ROOT_CMD =
/usr/bin/make -f debian/rules binary_modules
make[1]: Entering directory `/usr/src/modules/nvidia-kernel'
# select which makefile to use.
rm -f /usr/src/modules/nvidia-kernel/nv/Makefile || true
if [ 6 = 6 ]; then \
cd /usr/src/modules/nvidia-kernel/nv ; \
ln -s Makefile.kbuild Makefile ; \
cd .. ; \
if [ 0 = 1 ] ; then \
dpatch apply 04_minion ; \
fi ; \
if [ 0 = 1 ]; then \
Bug#495530: Evolution craches when passwd is not correct
Hi, thanks for providing the backtrace, it helps a lot in understanding what happens. #0 0x41276968 in g_markup_escape_text () from /usr/lib/libglib-2.0.so.0 #1 0x41277ab7 in g_markup_vprintf_escaped () from /usr/lib/libglib-2.0.so.0 #2 0x41277bd8 in g_markup_printf_escaped () from /usr/lib/libglib-2.0.so.0 #3 0x4229bbdc in imap_connect_online (service=0x825e920, ex=0x432a32a4) at camel-imap-store.c:1429 #4 0x401d4bcf in disco_connect (service=0x825e920, ex=0x432a32a4) at camel-disco-store.c:162 #5 0x401f51cf in camel_service_connect (service=0x825e920, ex=0x432a32a4) at camel-service.c:371 #6 0x42296c2a in camel_imap_store_connected (store=0x825e920, ex=0x432a32a4) at camel-imap-store.c:3017 #7 0x42292c7f in imap_refresh_info (folder=0x838c870, ex=0x432a32a4) at camel-imap-folder.c:585 #8 0x401d36d6 in disco_refresh_info (folder=0x838c870, ex=0x432a32a4) at camel-disco-folder.c:269 #9 0x401e53d9 in camel_folder_refresh_info (folder=0x838c870, ex=0x432a32a4) at camel-folder.c:302 #10 0x41e93b67 in refresh_folders_exec (m=0x8235d80) at mail-send-recv.c:825 #11 0x41e8d9e9 in mail_msg_proxy (msg=0x8235d80) at mail-mt.c:523 #12 0x4129d8f6 in ?? () from /usr/lib/libglib-2.0.so.0 #13 0x08235d80 in ?? () #14 0x in ?? () Could you please try again with bt full, if possible with the libglib2.0-0-dbg package installed? It seems to me that the exception structure got corrupt. Cheers, -- .''`. : :' : We are debian.org. Lower your prices, surrender your code. `. `' We will add your hardware and software distinctiveness to `-our own. Resistance is futile. signature.asc Description: Ceci est une partie de message numériquement signée
Bug#500657: Fix for Bug#500657 commited to version control
tags 500657 +pending thanks Hi, The following change has been committed for this bug, and so the fix will be in the next upload. === Changeset [216] by nijel, 2008-10-03 15:38:52 +0200 (Fri, 03 Oct 2008) * New upstream version. - Fixes format string (Closes: #500657). U trunk/debian/changelog U trunk/debian/watch http://viewsvn.cihar.com/debian-gammu?view=revrevision=216 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: Fix for Bug#500657 commited to version control
Processing commands for [EMAIL PROTECTED]: tags 500657 +pending Bug#500657: gammu_1.20.94-1(experimental/amd64/xenophanes): atgen.c:4016: error: format '%zd' expects type 'signed size_t', but argument 3 has type 'int' Tags were: pending fixed-upstream upstream experimental Tags added: pending 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#498144: remove sympa from lenny?
On 03/10/08 at 15:21 +0200, Olivier Berger wrote: Le vendredi 03 octobre 2008 à 12:43 +0200, Thomas Viehmann a écrit : It does not seem to have reverse dependencies. There are a few users (double digit popcon), but not exceedingly many. As it is on the servers, I assume a single mailing-list manager may have thousands of users... so popularity contest may not be relevant here AFAICT. Right. I find it annoying that after the sympa-drama before the etch release, we are now likely to run into another sympa-drama. Sympa is not an unmaintained software package: upstream is active, responsive and AFAIK willing to help. There's absolutely no reason why sympa should be in a crappy state in Debian. In #354355 (the etch sympa-drama bug), Stefan Hornburg refused several times to consider co-maintainance for sympa. I'm not sure if Jean Charles Delepine is still interested in co-maintaining it, but maybe we should try to convince Stefan to accept co-maintainance now. Maybe we could even avoid a sympa problem before the squeeze release. -- | Lucas Nussbaum | [EMAIL PROTECTED] http://www.lucas-nussbaum.net/ | | jabber: [EMAIL PROTECTED] GPG: 1024D/023B3F4F | -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#500657: marked as done (gammu_1.20.94-1(experimental/amd64/xenophanes): atgen.c:4016: error: format '%zd' expects type 'signed size_t', but argument 3 has type 'int')
Your message dated Fri, 03 Oct 2008 13:47:03 + with message-id [EMAIL PROTECTED] and subject line Bug#500657: fixed in gammu 1.21.0-1 has caused the Debian Bug report #500657, regarding gammu_1.20.94-1(experimental/amd64/xenophanes): atgen.c:4016: error: format '%zd' expects type 'signed size_t', but argument 3 has type 'int' to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [EMAIL PROTECTED] immediately.) -- 500657: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=500657 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: gammu Version: 1.20.94-1 Severity: serious Tags: experimental Heya, Building your package failed on my buildd: | Automatic build of gammu_1.20.94-1 on xenophanes by sbuild/amd64 98-farm | Build started at 20080926-2339 | ** [...] | cc1: warnings being treated as errors | /build/buildd/gammu-1.20.94/common/phone/at/atgen.c: In function 'ATGEN_ReplyGetPBKMemories': | /build/buildd/gammu-1.20.94/common/phone/at/atgen.c:4016: error: format '%zd' expects type 'signed size_t', but argument 3 has type 'int' | make[3]: *** [common/CMakeFiles/libGammu.dir/phone/at/atgen.o] Error 1 | make[2]: *** [common/CMakeFiles/libGammu.dir/all] Error 2 | make[1]: *** [all] Error 2 | make: *** [build-stamp] Error 2 | dpkg-buildpackage: failure: debian/rules build gave error exit status 2 | ** | Build finished at 20080926-2340 | FAILED [dpkg-buildpackage died] | Build needed 00:00:42, 19564k disk space A complete build log can be found at http://experimental.debian.net/build.php?arch=amd64pkg=gammuver=1.20.94-1 Marc -- BOFH #201: RPC_PMAP_FAILURE ---End Message--- ---BeginMessage--- Source: gammu Source-Version: 1.21.0-1 We believe that the bug you reported is fixed in the latest version of gammu, which is due to be installed in the Debian FTP archive: gammu_1.21.0-1.diff.gz to pool/main/g/gammu/gammu_1.21.0-1.diff.gz gammu_1.21.0-1.dsc to pool/main/g/gammu/gammu_1.21.0-1.dsc gammu_1.21.0-1_amd64.deb to pool/main/g/gammu/gammu_1.21.0-1_amd64.deb gammu_1.21.0.orig.tar.gz to pool/main/g/gammu/gammu_1.21.0.orig.tar.gz libgammu-common_1.21.0-1_all.deb to pool/main/g/gammu/libgammu-common_1.21.0-1_all.deb libgammu-dev_1.21.0-1_amd64.deb to pool/main/g/gammu/libgammu-dev_1.21.0-1_amd64.deb libgammu4-dbg_1.21.0-1_amd64.deb to pool/main/g/gammu/libgammu4-dbg_1.21.0-1_amd64.deb libgammu4_1.21.0-1_amd64.deb to pool/main/g/gammu/libgammu4_1.21.0-1_amd64.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Michal Čihař [EMAIL PROTECTED] (supplier of updated gammu package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Fri, 03 Oct 2008 15:37:58 +0200 Source: gammu Binary: gammu libgammu-dev libgammu-common libgammu4 libgammu4-dbg Architecture: source amd64 all Version: 1.21.0-1 Distribution: unstable Urgency: low Maintainer: Michal Čihař [EMAIL PROTECTED] Changed-By: Michal Čihař [EMAIL PROTECTED] Description: gammu - Mobile phone management utility libgammu-common - Mobile phone management library libgammu-dev - Header files for Gammu libgammu4 - Mobile phone management library libgammu4-dbg - Mobile phone management library - debugger symbols Closes: 500657 Changes: gammu (1.21.0-1) unstable; urgency=low . * New upstream version. - Fixes format string (Closes: #500657). Checksums-Sha1: 7e95e8e40818dfb7f367487092940e7b6b376600 1266 gammu_1.21.0-1.dsc 61ea155bef46ea6e6189fc014ad7702c6ba43a42 1421200 gammu_1.21.0.orig.tar.gz 166140f641d90440bc8f6273454c6b071ed44358 6585 gammu_1.21.0-1.diff.gz 5fe67e505c6c57e563680057cd73392f68ef6d95 298394 gammu_1.21.0-1_amd64.deb cc26911f958e6970dda47ff1c93bf21e00a8bcd7 170344 libgammu-dev_1.21.0-1_amd64.deb 74392ff246a4aef18b0794f9b7d09ea13b4af32d 147544 libgammu-common_1.21.0-1_all.deb e61d74f78bdd9670e373ad1c97f2aeb2f1ed0c9e 476496 libgammu4_1.21.0-1_amd64.deb 70a3e222b617f45e3116e47d05ee701a4983ae0c 1183502 libgammu4-dbg_1.21.0-1_amd64.deb Checksums-Sha256: 4eca87f661e52f7bd064b175d2e1d0476fbc03b134dcac5675b7eb79379c8f44
Bug#501033: oolite: exits with error at start
Package: oolite Version: 1.65-5 Severity: grave Justification: renders package unusable This happens every time, with a just-installed oolite: --- snip --- [EMAIL PROTECTED]:~$ oolite oolite: Uncaught exception NSInvalidArgumentException, reason: Tried to add nil to array [EMAIL PROTECTED]:~$ echo $? 1 --- snip --- Please ask for detailed information, I do not know what would be helpful. regards, Daniel -- System Information: Debian Release: 4.0 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/dash Kernel: Linux 2.6.23-hrt1-phc Locale: LANG=en_US.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) Versions of packages oolite depends on: ii gnustep-base-runtime 1.13.0-7 GNUstep Base library ii libc6 2.3.6.ds1-13etch7 GNU C Library: Shared libraries ii libgl1-mesa-glx [libgl 6.5.2-5~etch A free implementation of the OpenG ii libglu1-mesa [libglu1] 6.5.1-0.6 The OpenGL utility library (GLU) ii libgnustep-base1.131.13.0-7 GNUstep Base library ii libobjc1 1:4.1.1-21Runtime library for GNU Objective- ii libsdl-image1.21.2.5-2+etch1 image loading library for Simple D ii libsdl-mixer1.21.2.6-1.1+b2 mixer library for Simple DirectMed ii libsdl1.2debian1.2.11-8 Simple DirectMedia Layer ii oolite-data1.65-2Data files for the space-sim game oolite recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#499025: Primary node thrashes to death with queue error
Hi, I’ve successfully configured several Heartbeat clusters using version 2.0.7-2, and I never met the error you mention. Maybe you should send your configuration if you want help with debugging. In all cases, I don’t think this should be a RC bug. Furthermore, there is no evidence that it applies to lenny. Cheers, -- .''`. : :' : We are debian.org. Lower your prices, surrender your code. `. `' We will add your hardware and software distinctiveness to `-our own. Resistance is futile. signature.asc Description: Ceci est une partie de message numériquement signée
Bug#498144: remove sympa from lenny?
Lucas Nussbaum wrote: On 03/10/08 at 15:21 +0200, Olivier Berger wrote: Le vendredi 03 octobre 2008 à 12:43 +0200, Thomas Viehmann a écrit : It does not seem to have reverse dependencies. There are a few users (double digit popcon), but not exceedingly many. As it is on the servers, I assume a single mailing-list manager may have thousands of users... so popularity contest may not be relevant here AFAICT. Right. I find it annoying that after the sympa-drama before the etch release, we are now likely to run into another sympa-drama. Sympa is not an unmaintained software package: upstream is active, responsive and AFAIK willing to help. There's absolutely no reason why sympa should be in a crappy state in Debian. At the time I took over Sympa maintenance the scripts were written in a convoluted and complicated manner. To be honest, this hasn't changed much. If I would've been any wiser (and enough time to spent), I would started Sympa packaging from scratch. As a side note, file inclusion in Sympa configuration is a missing feature as packaging is concerned. In #354355 (the etch sympa-drama bug), Stefan Hornburg refused several times to consider co-maintainance for sympa. I'm not sure if Jean Charles Delepine is still interested in co-maintaining it, but maybe we should try to convince Stefan to accept co-maintainance now. Maybe we could even avoid a sympa problem before the squeeze release. Jean seems to be vanished from the radar. Jonas Smeedegard put an effort for better Sympa packaging on git.debian.org. It's quite likely that I team up with him after Lenny release. Regards Racke -- LinuXia Systems = http://www.linuxia.de/ Expert Interchange Consulting and System Administration ICDEVGROUP = http://www.icdevgroup.org/ Interchange Development Team -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#493840: is sbackup maintained enough to include in lenny?
Hi, sbackup has an RC bug without maintainer response for two months (#493840). The submitter (mind you, a Debian developer) still owes a mail about whether he can give some hints how to reproduce, but really, a sufficiently interested maintainer would have processed it somewhat (either determined as unverifiable or fixed). The important bugs also indicate neglect: #486808, reported in mid-June, is trivial to fix and borders on being RC. #492287 has been reported as grave three months ago, seen no maintainer response, and was finally downgraded last month by Luk. Again, it should not be too hard to fix. Aigars, what's up here? Kind regards T. -- Thomas Viehmann, http://thomas.viehmann.net/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#496520: Bug#498144: remove sympa from lenny?
On Fri, 3 Oct 2008 Lucas Nussbaum [EMAIL PROTECTED] wrote: [...] In #354355 (the etch sympa-drama bug), Stefan Hornburg refused several times to consider co-maintainance for sympa. I'm not sure if Jean Charles Delepine is still interested in co-maintaining it, but maybe we should try to convince Stefan to accept co-maintainance now. Maybe we could even avoid a sympa problem before the squeeze release. It is perhaps worth mentioning that upstream sympa is since March at version 5.4 (and since June at version 5.4.3) while in Debian in testing we have version 5.3.4 of November 2007 :-( Regards JSB -- , dr hab. Janusz S. Bien, prof. UW - Uniwersytet Warszawski (Katedra Lingwistyki Formalnej) Prof. Janusz S. Bien - Warsaw University (Department of Formal Linguistics) [EMAIL PROTECTED], [EMAIL PROTECTED], http://fleksem.klf.uw.edu.pl/~jsbien/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#500781: intent to NMU
tags 500781 + patch thanks Hi Vincent, * Vincent Danjean [EMAIL PROTECTED] [2008-10-03 12:15]: Steffen Joeris wrote: Hi, the following CVE (Common Vulnerabilities Exposures) id was published for mercurial. CVE-2008-4297[0]: | Mercurial before 1.0.2 does not enforce the allowpull permission | setting for a pull operation from hgweb, which allows remote attackers | to read arbitrary files from a repository via an hg pull request. I am not sure about the severity of this issue, could you please investigate it? I saw it when mercurial 1.0.2 have been published. But I did not find any specific changeset linked to this issue. If anyone (co-maintainer, user, ...) can point me to the changeset, I can prepare a patch with it. I can also package the whole 1.0.2 (I was waiting the lenny release to do it: RM told me they would probably not accept this update without strong reasons [1]). But, I'm sorry to tell that I will not have enough free time now to look more closely to this issue and to search into the mercurial development tree until a few weeks (too much real work for now). Attached is a patch for an NMU which fixes the issue. This is upstream changeset 6630:8542fac26f63. It is also archived on: http://people.debian.org/~nion/nmu-diff/mercurial-1.0.1-5_1.0.1-5.1.patch Feel free to upload yourself if you have the time. I also checked the diff between 1.0.1 and 1.0.2, 6630:8542fac26f63 is included in 1.0.2 however there is an additional changeset which is not (6779:d3147b4e3e8a) which centralizes the permission handling so not every command has to care about this themselve. Testing my patch with a repository that has allowpull = fase seems to work fine: hg clone http://bone/cgi-bin/hgwebdir.cgi/test destination directory: test requesting all changes abort: HTTP Error 500: Internal Server Error Of course the error message could be better... Cheers Nico -- Nico Golde - http://www.ngolde.de - [EMAIL PROTECTED] - GPG: 0x73647CFF For security reasons, all text in this mail is double-rot13 encrypted. diff -u mercurial-1.0.1/debian/changelog mercurial-1.0.1/debian/changelog --- mercurial-1.0.1/debian/changelog +++ mercurial-1.0.1/debian/changelog @@ -1,3 +1,11 @@ +mercurial (1.0.1-5.1) unstable; urgency=high + + * Non-maintainer upload by the Security Team. + * Honor allowpull configuration setting from hgrc on a repository clone to +prevent information disclosure (CVE-2008-4297; Closes: #500781). + + -- Nico Golde [EMAIL PROTECTED] Fri, 03 Oct 2008 16:25:13 +0200 + mercurial (1.0.1-5) unstable; urgency=low * Fix debian/copyright (GPL-2 only and not GPL-2+) (Closes: #493967) diff -u mercurial-1.0.1/debian/patches/series mercurial-1.0.1/debian/patches/series --- mercurial-1.0.1/debian/patches/series +++ mercurial-1.0.1/debian/patches/series @@ -1,3 +1,4 @@ +CVE-2008-4297 proposed_upstream__python-module-not-script.patch proposed_upstream__extension_syntax.patch deb_specific__FAQ_subst.patch only in patch2: unchanged: --- mercurial-1.0.1.orig/debian/patches/CVE-2008-4297 +++ mercurial-1.0.1/debian/patches/CVE-2008-4297 @@ -0,0 +1,12 @@ +Index: mercurial-1.0.1/mercurial/hgweb/protocol.py +=== +--- mercurial-1.0.1.orig/mercurial/hgweb/protocol.py 2008-10-03 16:24:51.0 +0200 mercurial-1.0.1/mercurial/hgweb/protocol.py 2008-10-03 16:25:01.0 +0200 +@@ -224,5 +224,7 @@ + os.unlink(tempname) + + def stream_out(web, req): ++if not web.allowpull: ++return + req.respond(HTTP_OK, HGTYPE) + streamclone.stream_out(web.repo, req, untrusted=True) pgpQChdWSWboE.pgp Description: PGP signature
Processed: intent to NMU
Processing commands for [EMAIL PROTECTED]: tags 500781 + patch Bug#500781: CVE-2008-4297: privilege escalation Tags were: security Tags added: patch thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#501041: wmibam uses old ibam.* files
Package: wmibam Version: 0.0.1-2 Severity: grave Tags: patch Justification: renders package unusable wmibam uses old library on ibam.* files. That makes it unuseful because it can't check the sensors. You can get the ibam.* files from the ibam package and replace the old ones on the wmibam package and this will work fine. -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.26-1-amd64 (SMP w/1 CPU core) Locale: LANG=, LC_CTYPE= (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/bash Versions of packages wmibam depends on: ii libc6 2.7-13 GNU C Library: Shared libraries ii libgcc1 1:4.3.1-9 GCC support library ii libstdc++64.3.1-9The GNU Standard C++ Library v3 ii libx11-6 2:1.1.5-1 X11 client-side library ii libxext6 2:1.0.4-1 X11 miscellaneous extension librar ii libxpm4 1:3.5.7-1 X11 pixmap library wmibam recommends no packages. wmibam suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#434040: Conflicting declarations for dev_t
Hi, There have not been any updates to the status of this bug for several months, although this is definitely something that should be fixed for lenny. Is there anything that is possible to help fixing this before the release? I see you consider entirely dropping these declarations, do you need for example a full rebuild of the archive with a version without them? Cheers, -- .''`. : :' : We are debian.org. Lower your prices, surrender your code. `. `' We will add your hardware and software distinctiveness to `-our own. Resistance is futile. signature.asc Description: Ceci est une partie de message numériquement signée
Bug#498144: remove sympa from lenny?
Le vendredi 03 octobre 2008 à 16:11 +0200, Stefan Hornburg (Racke) a écrit : I find it annoying that after the sympa-drama before the etch release, we are now likely to run into another sympa-drama. Sympa is not an unmaintained software package: upstream is active, responsive and AFAIK willing to help. There's absolutely no reason why sympa should be in a crappy state in Debian. At the time I took over Sympa maintenance the scripts were written in a convoluted and complicated manner. To be honest, this hasn't changed much. If I would've been any wiser (and enough time to spent), I would started Sympa packaging from scratch. As a side note, file inclusion in Sympa configuration is a missing feature as packaging is concerned. In #354355 (the etch sympa-drama bug), Stefan Hornburg refused several times to consider co-maintainance for sympa. I'm not sure if Jean Charles Delepine is still interested in co-maintaining it, but maybe we should try to convince Stefan to accept co-maintainance now. Maybe we could even avoid a sympa problem before the squeeze release. Jean seems to be vanished from the radar. Jonas Smeedegard put an effort for better Sympa packaging on git.debian.org. It's quite likely that I team up with him after Lenny release. I also have access to Racke's internal CVS, but unfortunately, I'm not available on a stable pace to contribute much either :( There's definitely a manpower/availability/dedication problem for this package, which is unfortunate. Just my 2 not so useful cents, -- Olivier BERGER [EMAIL PROTECTED] http://www-public.it-sudparis.eu/~berger_o/ - OpenPGP-Id: 1024D/6B829EEC Ingénieur Recherche - Dept INF Institut TELECOM, SudParis (http://www.it-sudparis.eu/), Evry (France) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#498144: remove sympa from lenny?
On Fri, Oct 03, 2008 at 12:43:39PM +0200, Thomas Viehmann wrote: sympa has two RC bugs open for about one month, #496520 about insecure usage of tmp (which looks at least partially fixed upstream, but has no maintainer response) and #498144 about problems on upgrade (with an initial maintainer response will investigate, also happened to people at the last security upgrades, but no visible activity since). Any of them are a regression over the version in Etch? Unless the maintainer (or perhaps Olivier who forwarded the first bug upstream, CCed) resolve these bugs soon, it might be better to not release sympa with lenny. Please describe this further. It does not seem to have reverse dependencies. There are a few users (double digit popcon), but not exceedingly many. sympa provides a public service. Bastian -- Get back to your stations! We're beaming down to the planet, sir. -- Kirk and Mr. Leslie, This Side of Paradise, stardate 3417.3 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#501048: coco-cpp - FTBFS: rm: cannot remove `Coco': No such file or directory
Package: coco-cpp Version: 20081001-1 Severity: serious There was an error while trying to autobuild your package: Automatic build of coco-cpp_20081001-1 on debian-31.osdl.marist.edu by sbuild/s390 98 [...] /usr/bin/make clean make[1]: Entering directory `/build/buildd/coco-cpp-20081001' rm Coco rm: cannot remove `Coco': No such file or directory make[1]: *** [clean] Error 1 make[1]: Leaving directory `/build/buildd/coco-cpp-20081001' make: *** [clean] Error 2 dpkg-buildpackage: failure: /usr/bin/fakeroot debian/rules clean gave error exit status 2 ** Build finished at 20080929-1213 FAILED [dpkg-buildpackage died] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: libwx-perl - FTBFS: Failed 3/4 test scripts. 8/9 subtests failed.
Processing commands for [EMAIL PROTECTED]: found 499740 0.86-2 Bug#499740: libwx-perl - FTBFS: Failed 2/4 test scripts. 6/9 subtests failed. Bug marked as found in version 0.86-2 and reopened. 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#501047: libcaca - FTBFS: error: unknown register name 'st(1)' in 'asm'
Package: libcaca Version: 0.99.beta15-1 Severity: serious There was an error while trying to autobuild your package: Automatic build of libcaca_0.99.beta15-1 on debian-31.osdl.marist.edu by sbuild/s390 98 [...] /bin/sh ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I.. -DPLUGINDIR=\/usr/lib/caca\ -D__LIBCACA__ -DOPTIMISE_SLANG_PALETTE=1 -g -O2 -g -O2 -fno-strength-reduce -fomit-frame-pointer -Wall -Wpointer-arith -Wcast-align -Wcast-qual -Wstrict-prototypes -Wshadow -Waggregate-return -Wmissing-prototypes -Wnested-externs -Wsign-compare -MT libcaca_la-dither.lo -MD -MP -MF .deps/libcaca_la-dither.Tpo -c -o libcaca_la-dither.lo `test -f 'dither.c' || echo './'`dither.c gcc -DHAVE_CONFIG_H -I. -I.. -I.. -DPLUGINDIR=\/usr/lib/caca\ -D__LIBCACA__ -DOPTIMISE_SLANG_PALETTE=1 -g -O2 -g -O2 -fno-strength-reduce -fomit-frame-pointer -Wall -Wpointer-arith -Wcast-align -Wcast-qual -Wstrict-prototypes -Wshadow -Waggregate-return -Wmissing-prototypes -Wnested-externs -Wsign-compare -MT libcaca_la-dither.lo -MD -MP -MF .deps/libcaca_la-dither.Tpo -c dither.c -fPIC -DPIC -o .libs/libcaca_la-dither.o dither.c: In function 'caca_set_dither_gamma': dither.c:1252: error: unknown register name 'st(1)' in 'asm' make[3]: *** [libcaca_la-dither.lo] Error 1 make[3]: Leaving directory `/build/buildd/libcaca-0.99.beta15/caca' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/build/buildd/libcaca-0.99.beta15' make[1]: *** [all] Error 2 make[1]: Leaving directory `/build/buildd/libcaca-0.99.beta15' make: *** [build-stamp] Error 2 dpkg-buildpackage: failure: debian/rules build gave error exit status 2 ** Build finished at 20080927-1754 FAILED [dpkg-buildpackage died] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#499740: libwx-perl - FTBFS: Failed 3/4 test scripts. 8/9 subtests failed.
found 499740 0.86-2 thanks There was an error while trying to autobuild your package: Automatic build of libwx-perl_0.86-2 on debian-31.osdl.marist.edu by sbuild/s390 98 [...] make[4]: Entering directory `/build/buildd/libwx-perl-0.86/ext/pperl/splashfast' PERL_DL_NONLAZY=1 /usr/bin/perl -MExtUtils::Command::MM -e test_harness(0, '../../../blib/lib', '../../../blib/arch') t/*.t t/01_loadok t/02_use.dubious Test returned status 0 (wstat 4, 0x4) DIED. FAILED test 1 Failed 1/1 tests, 0.00% okay t/03_new.dubious Test returned status 0 (wstat 11, 0xb) DIED. FAILED tests 1-2 Failed 2/2 tests, 0.00% okay t/04_app.dubious Test returned status 0 (wstat 4, 0x4) DIED. FAILED tests 1-5 Failed 5/5 tests, 0.00% okay Failed Test Stat Wstat Total Fail List of Failed --- t/02_use.t 0 4 12 1 t/03_new.t 011 24 1-2 t/04_app.t 0 4 5 10 1-5 Failed 3/4 test scripts. 8/9 subtests failed. Files=4, Tests=9, 9 wallclock secs ( 6.72 cusr + 0.23 csys = 6.95 CPU) Failed 3/4 test programs. 8/9 subtests failed. make[4]: *** [test_dynamic] Error 255 make[4]: Leaving directory `/build/buildd/libwx-perl-0.86/ext/pperl/splashfast' make[3]: *** [subdirs-test] Error 2 make[3]: Leaving directory `/build/buildd/libwx-perl-0.86/ext/pperl' make[2]: *** [subdirs-test] Error 2 make[2]: Leaving directory `/build/buildd/libwx-perl-0.86/ext' make[1]: *** [subdirs-test] Error 2 make[1]: Leaving directory `/build/buildd/libwx-perl-0.86' make: *** [build-stamp] Error 2 dpkg-buildpackage: failure: debian/rules build gave error exit status 2 ** Build finished at 20081002-1753 FAILED [dpkg-buildpackage died] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#499898: ntfs-3g: Files copied not complete
Hi, according to the dmesg logs posted by the submitter to the ntfs-3g forum, it seems clear the issue is caused by I/O errors. I guess this bug should simply be closed. Cheers, -- .''`. : :' : We are debian.org. Lower your prices, surrender your code. `. `' We will add your hardware and software distinctiveness to `-our own. Resistance is futile. signature.asc Description: Ceci est une partie de message numériquement signée
Bug#500956: unable to boot on a500 (hppa)
On Fri, Oct 03, 2008 at 07:20:35AM +0200, Martin Michlmayr wrote: * dann frazier [EMAIL PROTECTED] [2008-10-02 17:55]: Are you sure the installer is using 2.6.26-6? This looks a lot like #499458 which should've been fixed in 2.6.26-6 (fixed it for me, at least). Note that he wrote the lenny installer does work, the kernel installed by the installer fails to boot. Which is no surprise since testing still has 2.6.26-5. oh right, that makes sense then. -- dann frazier -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: forcibly merging 499458 500956
Processing commands for [EMAIL PROTECTED]: forcemerge 499458 500956 Bug#499458: [hppa] kernel no longer boots on an A500 Bug#500956: unable to boot on a500 (hppa) Forcibly Merged 499458 500956. 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: reassign 485489 to apt, forcibly merging 495331 485489
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.9.26 reassign 485489 apt 0.6.46.4-0.1 Bug#485489: synaptic: The package lists or status file could not be parsed or opened Bug reassigned from package `synaptic' to `apt'. forcemerge 495331 485489 Bug#495331: apt-get on SID fails in German locale: E: Toll, Sie haben die Anzahl an Beschreibungen überschritten, die APT handhaben kann. Bug#485489: synaptic: The package lists or status file could not be parsed or opened Bug#400768: apt: Returns E: Wow, you exceeded the number of versions this APT is capable of Bug#466643: please increase number of package names Bug#497617: [aptitude] [German localisation] exceeded the number of descriptions this APT is capable of .. Problem with MergeList .. Forcibly Merged 400768 466643 485489 495331 497617. 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#500615: mmorph: diff for NMU version 2.3.4.2-11.1
On Fri, 2008-10-03 at 07:56 +0200, Luk Claes wrote: tags 500615 + patch thanks Dear maintainer, I've prepared an NMU for mmorph (versioned as 2.3.4.2-11.1) and uploaded it to DELAYED/3. Please feel free to tell me if I should delay it longer. Yes, please remove it from the upload queue. I'm assuming as well that you have done extensive testing. Can you point me to the tests you used to verify the functionality of the patch you wish to upload? Also, can you point me to a comprehensive statement of the interface changes in the db library which may affect mmorph? I'm sure you have that right at hand because I'm sure you went through it carefully before making an upload. Finally, may I point out that it is not reasonable to file an RC bug and then an NMU all at about the same time, at this point in the release? The time for deciding to remove the package was back at the BEGINNING of the release cycle, not now, at the end. Can you explain why you chose to wait until now to start making such changes? Thomas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#494936: marked as done (bnx2 fails to load on bootup, succeeds on manual load)
Your message dated Fri, 03 Oct 2008 16:32:03 + with message-id [EMAIL PROTECTED] and subject line Bug#494936: fixed in firmware-nonfree 0.13 has caused the Debian Bug report #494936, regarding bnx2 fails to load on bootup, succeeds on manual load to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [EMAIL PROTECTED] immediately.) -- 494936: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=494936 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: firmware-bnx2 Version: 0.12 Severity: grave BNX2 fails to load the firmware on bootup. If I rmmod bnx2 and modprobe bnx2 after bootup, the nics appear. Log can be found at http://home.schottelius.org/~nico/unix/linux/debian/dmesg.2.6.25-2%2bbnx2%2bmanual-load -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (x86_64) Kernel: Linux 2.6.25-2-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash firmware-bnx2 depends on no packages. firmware-bnx2 recommends no packages. Versions of packages firmware-bnx2 suggests: ii initramfs-tools 0.92e tools for generating an initramfs ii linux-image-2.6.22-3-amd 2.6.22-6.lenny1 Linux 2.6.22 image on AMD64 ii linux-image-2.6.25-2-amd 2.6.25-7Linux 2.6.25 image on AMD64 -- no debconf information ---End Message--- ---BeginMessage--- Source: firmware-nonfree Source-Version: 0.13 We believe that the bug you reported is fixed in the latest version of firmware-nonfree, which is due to be installed in the Debian FTP archive: firmware-bnx2_0.13_all.deb to pool/non-free/f/firmware-nonfree/firmware-bnx2_0.13_all.deb firmware-iwlwifi_0.13_all.deb to pool/non-free/f/firmware-nonfree/firmware-iwlwifi_0.13_all.deb firmware-nonfree_0.13.dsc to pool/non-free/f/firmware-nonfree/firmware-nonfree_0.13.dsc firmware-nonfree_0.13.tar.gz to pool/non-free/f/firmware-nonfree/firmware-nonfree_0.13.tar.gz firmware-qlogic_0.13_all.deb to pool/non-free/f/firmware-nonfree/firmware-qlogic_0.13_all.deb firmware-ralink_0.13_all.deb to pool/non-free/f/firmware-nonfree/firmware-ralink_0.13_all.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. dann frazier [EMAIL PROTECTED] (supplier of updated firmware-nonfree package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Thu, 02 Oct 2008 11:58:37 -0600 Source: firmware-nonfree Binary: firmware-bnx2 firmware-iwlwifi firmware-qlogic firmware-ralink Architecture: source all Version: 0.13 Distribution: unstable Urgency: low Maintainer: Debian Kernel Team [EMAIL PROTECTED] Changed-By: dann frazier [EMAIL PROTECTED] Description: firmware-bnx2 - Binary firmware for Broadcom NetXtremeII firmware-iwlwifi - Binary firmware for Intel Wireless 3945 and 4965 firmware-qlogic - Binary firmware for QLogic QLA2XXX firmware-ralink - Binary firmware for Ralink RT2561, RT2571, RT2661 and RT2671 wire Closes: 494703 494936 500692 Changes: firmware-nonfree (0.13) unstable; urgency=low . * Make firmware-bnx2 trigger update-initramfs (closes: #494936) * Update to 2.6.26-1 (closes: #500692) * Update Intel Wireless 3945 firmware, version 15.28.1.6. (closes: #494703) Checksums-Sha1: 56c881c6b17b7ccc85da9dbcab9144203ddee36a 1078 firmware-nonfree_0.13.dsc 9b5911c3919d64858ecfbbc3360063288b3d87a1 757003 firmware-nonfree_0.13.tar.gz b98c46a9a4a972143c2a02d0ec341c3eb4955763 105202 firmware-bnx2_0.13_all.deb 6ac887abdafcfaa5d10b5ba43d5f5aa8b1f07de7 223692 firmware-iwlwifi_0.13_all.deb 0a3692816139ca71657e99b9d0cc697759b95973 415570 firmware-qlogic_0.13_all.deb 8dca1b7306a02d73b35b4ab26a5d8134e3dea0ca 11600 firmware-ralink_0.13_all.deb Checksums-Sha256: b15022b0923d8cde90c759a06c17395bdd91fc35777d0a0e7fba150adb8c8514 1078 firmware-nonfree_0.13.dsc 05c66070fc5e548e325ab8955ea94ea1dff7d457a009b96111592883e5351142 757003 firmware-nonfree_0.13.tar.gz 14c404ada2c09a5f3f575c3e994be65a8f3c9e84ff42b55c3c5fe5417a2ec143 105202 firmware-bnx2_0.13_all.deb 3b6a3f6fcecd06a99d82a5132f2cc9a1c3900aaecbec8914bd20316030086772 223692 firmware-iwlwifi_0.13_all.deb
Bug#500692: marked as done ([firmware-nonfree] FTBFS: depends on linux-support-2.6.25-2)
Your message dated Fri, 03 Oct 2008 16:32:03 + with message-id [EMAIL PROTECTED] and subject line Bug#500692: fixed in firmware-nonfree 0.13 has caused the Debian Bug report #500692, regarding [firmware-nonfree] FTBFS: depends on linux-support-2.6.25-2 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [EMAIL PROTECTED] immediately.) -- 500692: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=500692 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: firmware-nonfree Version: 0.12 Severity: normal The package depends on linux-support-2.6.25-2 which is not available anymore. Please rebuild the package for the current kernel (which will probably ship with Lenny). After changing the appropriate line in debian/rules to 2.6.26-1 and changing KERNELVERSION in debian/rules.defs I was able to build the package (for Lenny) using pbuilder without issues. I'm not using any of the drivers that need to be build from source though, so I wouldn't know if they actually worked. Thanks in advance and have a nice day! --- System information. --- Architecture: i386 Kernel: Linux 2.6.26-1-686 Debian Release: lenny/sid 500 testing security.debian.org 500 testing ftp.debian.org ---End Message--- ---BeginMessage--- Source: firmware-nonfree Source-Version: 0.13 We believe that the bug you reported is fixed in the latest version of firmware-nonfree, which is due to be installed in the Debian FTP archive: firmware-bnx2_0.13_all.deb to pool/non-free/f/firmware-nonfree/firmware-bnx2_0.13_all.deb firmware-iwlwifi_0.13_all.deb to pool/non-free/f/firmware-nonfree/firmware-iwlwifi_0.13_all.deb firmware-nonfree_0.13.dsc to pool/non-free/f/firmware-nonfree/firmware-nonfree_0.13.dsc firmware-nonfree_0.13.tar.gz to pool/non-free/f/firmware-nonfree/firmware-nonfree_0.13.tar.gz firmware-qlogic_0.13_all.deb to pool/non-free/f/firmware-nonfree/firmware-qlogic_0.13_all.deb firmware-ralink_0.13_all.deb to pool/non-free/f/firmware-nonfree/firmware-ralink_0.13_all.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. dann frazier [EMAIL PROTECTED] (supplier of updated firmware-nonfree package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Thu, 02 Oct 2008 11:58:37 -0600 Source: firmware-nonfree Binary: firmware-bnx2 firmware-iwlwifi firmware-qlogic firmware-ralink Architecture: source all Version: 0.13 Distribution: unstable Urgency: low Maintainer: Debian Kernel Team [EMAIL PROTECTED] Changed-By: dann frazier [EMAIL PROTECTED] Description: firmware-bnx2 - Binary firmware for Broadcom NetXtremeII firmware-iwlwifi - Binary firmware for Intel Wireless 3945 and 4965 firmware-qlogic - Binary firmware for QLogic QLA2XXX firmware-ralink - Binary firmware for Ralink RT2561, RT2571, RT2661 and RT2671 wire Closes: 494703 494936 500692 Changes: firmware-nonfree (0.13) unstable; urgency=low . * Make firmware-bnx2 trigger update-initramfs (closes: #494936) * Update to 2.6.26-1 (closes: #500692) * Update Intel Wireless 3945 firmware, version 15.28.1.6. (closes: #494703) Checksums-Sha1: 56c881c6b17b7ccc85da9dbcab9144203ddee36a 1078 firmware-nonfree_0.13.dsc 9b5911c3919d64858ecfbbc3360063288b3d87a1 757003 firmware-nonfree_0.13.tar.gz b98c46a9a4a972143c2a02d0ec341c3eb4955763 105202 firmware-bnx2_0.13_all.deb 6ac887abdafcfaa5d10b5ba43d5f5aa8b1f07de7 223692 firmware-iwlwifi_0.13_all.deb 0a3692816139ca71657e99b9d0cc697759b95973 415570 firmware-qlogic_0.13_all.deb 8dca1b7306a02d73b35b4ab26a5d8134e3dea0ca 11600 firmware-ralink_0.13_all.deb Checksums-Sha256: b15022b0923d8cde90c759a06c17395bdd91fc35777d0a0e7fba150adb8c8514 1078 firmware-nonfree_0.13.dsc 05c66070fc5e548e325ab8955ea94ea1dff7d457a009b96111592883e5351142 757003 firmware-nonfree_0.13.tar.gz 14c404ada2c09a5f3f575c3e994be65a8f3c9e84ff42b55c3c5fe5417a2ec143 105202 firmware-bnx2_0.13_all.deb 3b6a3f6fcecd06a99d82a5132f2cc9a1c3900aaecbec8914bd20316030086772 223692 firmware-iwlwifi_0.13_all.deb 4985cd23aafe290fe035d7c9fbeb6b388f562ab9f50057eb7d68e227f460cbd1 415570 firmware-qlogic_0.13_all.deb 57fc20c7fe183e18bad47371daa15d4ed8672b4283023702606f83d7291f58af 11600
Bug#391935: The answer from Citrix Xen.org
Hi, I simply asked to upstream for a clarification on the use of the Xen trademark, and received two unambiguous answers. From Citrix: Actually, for the community, you can do whatever you like. The FIT test only applies to commercially distributed Xen products - and is about ensuring compatibility between vendors. Do you need more detail than that? best Simon -- Simon Crosby CTO, Virtualization Management Division Citrix Systems And from Xen.org: Thanks for your email and I am glad that Debian is continuing to support Xen in your product releases. I see no issue with Debian moving forward as you suggest at this time with Xen logo and wording usage. We are still working on the FIT test and it is not ready at this time for official publication. If you are interested, we can include someone from your community on our latest FIT test thoughts to get more feedback and ensure that the test meets your needs as well as ours. Thank you. Stephen Spector Community Manager, Xen.org I think this bug can simply be closed, as there is no issue with the Xen trademark. Cheers, -- .''`. : :' : We are debian.org. Lower your prices, surrender your code. `. `' We will add your hardware and software distinctiveness to `-our own. Resistance is futile. signature.asc Description: Ceci est une partie de message numériquement signée
Bug#500482: Segmentation fault in grub-probe
Am Montag, den 29.09.2008, 00:45 +0200 schrieb ziborski.net admin: No, there are no removed devices, all are active sync. Please note that /dev/md3 is a RAID0 built on top of two RAID1 (md1 and md2) which causes md2 - and its underlying partitions sdc3 and sdd3 to start with the second 16 KiB chunk of /dev/md3 (and LVM pv it is containing). Ah you use LVM. There's a known problem with it's circular metadata which isn't yet fixed upstream but there's a patch floating around which solves this. Maybe that's your problem. I just tried now a mdraid md2 which goes over mdraid md1 and md0 and this didn't lead to a segfault in grub-probe. Here you find the patch and intructions how to compile it: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=495949#69 If this still doestn't solve your problem then we need a GDB backtrace. Instructions for this are in same report. Maybe this is even related to it. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#501048: coco-cpp - FTBFS: rm: cannot remove `Coco': No such file or directory
tags 501048 +patch thanks this bug is trivial to fix, just change rm Coco to rm -f Coco in the clean target in the Makefile -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: re: coco-cpp - FTBFS: rm: cannot remove `Coco': No such file or directory
Processing commands for [EMAIL PROTECTED]: tags 501048 +patch Bug#501048: coco-cpp - FTBFS: rm: cannot remove `Coco': No such file or directory There were no tags set. Tags added: patch thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#493040: marked as done (iceweasel: keep generating segfault when opening gmail)
Your message dated Fri, 3 Oct 2008 20:14:36 +0200 with message-id [EMAIL PROTECTED] and subject line Re: Bug#493040: iceweasel: keep generating segfault when opening gmail has caused the Debian Bug report #493040, regarding iceweasel: keep generating segfault when opening gmail to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [EMAIL PROTECTED] immediately.) -- 493040: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=493040 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: iceweasel Version: 3.0.1-1 Severity: grave Hello, I seem to identify a recurring regfault when opening gmail. I'm attaching the gdb trace from the core file generated when iceweasel crashs. Thanks, Sandro -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.22-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages iceweasel depends on: ii debianutils 2.30 Miscellaneous utilities specific t ii fontconfig2.6.0-1generic font configuration library ii libc6 2.7-12 GNU C Library: Shared libraries ii libglib2.0-0 2.16.5-1 The GLib library of C routines ii libgtk2.0-0 2.12.11-3 The GTK+ graphical user interface ii libnspr4-0d 4.7.1-3NetScape Portable Runtime Library ii libstdc++64.3.1-8The GNU Standard C++ Library v3 ii procps1:3.2.7-8 /proc file system utilities ii psmisc22.6-1 Utilities that use the proc filesy ii xulrunner-1.9 1.9.0.1-1 XUL + XPCOM application runner iceweasel recommends no packages. Versions of packages iceweasel suggests: ii latex-xft-fonts 0.1-8 Xft-compatible versions of some La ii libkrb53 1.6.dfsg.4~beta1-3 MIT Kerberos runtime libraries ii mozplugger1.10.2-1 Plugin allowing external viewers t pn ttf-mathematica4.1none (no description available) pn xfonts-mathml none (no description available) pn xprintnone (no description available) ii xulrunner-1.9-gnome-s 1.9.0.1-1 Support for GNOME in xulrunner app -- no debconf information iceweasel_gdb_core.31289_2008-07-30.txt.bz2 Description: BZip2 compressed data iceweasel_gdb_core.31965_2008-07-30.txt.bz2 Description: BZip2 compressed data iceweasel_gdb_core.32617_2008-07-30.txt.bz2 Description: BZip2 compressed data ---End Message--- ---BeginMessage--- Sandro Tosi wrote: Anyhow, I got to say that this problem doesn't show any longer here, so it might be solved by me updating kernel, or something else. can this be confirmed by gdb traces analysis?. Not by gdb analysis, but since it's works for you and the problem isn't reported otherwise (and gmail logins work fine for on Lenny) I'm closing this bug. Cheers, Moritz ---End Message---
Bug#501059: jetty: Should likely not be shipped with Lenny
Package: jetty Severity: serious When browsing through open security issues in Lenny I noticed that several Jetty security fixes have been unfixed for quite some time (#454529), although upstream has posted a patch in July. Since it's only in contrib, outdated (current upstream releases are 6 and 7), fairly unmaintained (last upload a year ago, unfixed security issue) and with hardly any users (only three in popcon) we should probably remove it from Lenny. (It should be noted that due to Jetty being in contrib it's not covered by security support, so it doesn't impose additional security maintenance overhead if left in Lenny). Cheers, Moritz -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.26-1-686 (SMP w/1 CPU core) Locale: LANG=C, [EMAIL PROTECTED] (charmap=ISO-8859-15) Shell: /bin/sh linked to /bin/bash -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#500075: more info?
Thomas Viehmann schrieb: Hi Christoph, it seems that without more info (unless you are able to get some hardware to reproduce this to someone who wants to debug this, but you don't seem to live near Bonn, Germany ;) ), we would have difficulties to fix this bug. Could you try to build a debug-enabled package and get a backtrace so outsiders can try to come up with a patch? Instructions are on the Debian wiki[1], searching the internet, I suspect you do have the requisite knowledge, but don't hesitate to ask if I can be of assistance. Kind regards T. 1. http://wiki.debian.org/HowToGetABacktrace Hi I'm having problems to even reproduce it actually -- my guess is that it's related to having some partially submitted files on the player. I'll have an closer look at it on sunday, I guess I won't be able to do much tomorrow. Regards Christoph -- GPG-Key ID: 0x0372275D /\ ASCII Ribbon \ /Campaign X against HTML / \ in eMails signature.asc Description: OpenPGP digital signature
Bug#500909: marked as done (libxpp3-java: includes javax.xml.namespace.QName class)
Your message dated Fri, 03 Oct 2008 17:47:04 + with message-id [EMAIL PROTECTED] and subject line Bug#500909: fixed in libxpp3-java 1.1.3.4.O-4 has caused the Debian Bug report #500909, regarding libxpp3-java: includes javax.xml.namespace.QName class to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [EMAIL PROTECTED] immediately.) -- 500909: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=500909 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: libxpp3-java Version: 1.1.3.4.O-3 Severity: serious The xpp3.jar file contains the QName class from JAXP. This breaks the GroovyWS web service client, since it ends up loading the class into two different classloaders (the bootstrap class loader of the JRE and the Groovy class loader which has xpp3.jar on its classpath). This leads to the following error: Caught: java.lang.LinkageError: loader constraint violation: when resolving field DATETIME the class loader (instance of org/codehaus/groovy/tools/RootLoader) of the referring class, javax/xml/datatype/DatatypeConstants, and the class loader (instance of bootloader) for the field's resolved type, javax/xml/namespace/QName, have different Class objects for that type Note: the QName.java file from the xpp3 sources has the following comment at the top: * NOTE: copied from Apache AXIS until QName is really standard in some JDK version ... -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.26-melech (SMP w/2 CPU cores; PREEMPT) Locale: LANG=sv_SE.UTF-8, LC_CTYPE=sv_SE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages libxpp3-java depends on: ii default-jre [java2-runtime] 1.5-30 Standard Java or Java compatible R ii jamvm [java1-runtime] 1.5.1-3virtual machine which conforms to ii java-gcj-compat [java2-runtim 1.0.78-2 Java runtime environment using GIJ ii openjdk-6-jre [java2-runtime] 6b11-7 OpenJDK Java runtime, using Hotspo ii sun-java6-jre [java2-runtime] 6-07-4 Sun Java(TM) Runtime Environment ( libxpp3-java recommends no packages. libxpp3-java suggests no packages. -- no debconf information ---End Message--- ---BeginMessage--- Source: libxpp3-java Source-Version: 1.1.3.4.O-4 We believe that the bug you reported is fixed in the latest version of libxpp3-java, which is due to be installed in the Debian FTP archive: libxpp3-java_1.1.3.4.O-4.diff.gz to pool/main/libx/libxpp3-java/libxpp3-java_1.1.3.4.O-4.diff.gz libxpp3-java_1.1.3.4.O-4.dsc to pool/main/libx/libxpp3-java/libxpp3-java_1.1.3.4.O-4.dsc libxpp3-java_1.1.3.4.O-4_all.deb to pool/main/libx/libxpp3-java/libxpp3-java_1.1.3.4.O-4_all.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Marcus Better [EMAIL PROTECTED] (supplier of updated libxpp3-java package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Thu, 02 Oct 2008 17:04:04 +0200 Source: libxpp3-java Binary: libxpp3-java Architecture: source all Version: 1.1.3.4.O-4 Distribution: unstable Urgency: low Maintainer: Debian Java Maintainers [EMAIL PROTECTED] Changed-By: Marcus Better [EMAIL PROTECTED] Description: libxpp3-java - XML pull parser library for java Closes: 500909 Changes: libxpp3-java (1.1.3.4.O-4) unstable; urgency=low . * Do not include the javax.xml.namespace.QName class since it is likely to cause conflicts. (Closes: #500909) * Move dependencies for clean target to Build-depends. * Update to policy version 3.8.0.1. - Describe patch management in README.source. * debian/copyright: Completed copyright information. * Added myself to Uploaders, removed Wolfgang. Checksums-Sha1: 8d140bef941f312f5d9a5c28ab425a235c0b4448 1200 libxpp3-java_1.1.3.4.O-4.dsc f0979f24fea81e6010e8557f58c5d4cee1a3823b 5055 libxpp3-java_1.1.3.4.O-4.diff.gz 76c9c8ae3ffb040d0129d528c2fb61261d1d3f0b 327356 libxpp3-java_1.1.3.4.O-4_all.deb Checksums-Sha256: 9cd782e551739d42c681c4349257bb464e13eca46ac2a6ee0264092179df7a69 1200 libxpp3-java_1.1.3.4.O-4.dsc
Bug#499841: marked as done (CVE-2008-3970: does not verify mountpoint and source ownership before mounting a user-defined volume)
Your message dated Fri, 03 Oct 2008 18:17:03 + with message-id [EMAIL PROTECTED] and subject line Bug#499841: fixed in libpam-mount 0.44-1+lenny1 has caused the Debian Bug report #499841, regarding CVE-2008-3970: does not verify mountpoint and source ownership before mounting a user-defined volume to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [EMAIL PROTECTED] immediately.) -- 499841: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=499841 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: libpam-mount Version: 0.18-3 Severity: grave Tags: security Hi, the following CVE (Common Vulnerabilities Exposures) id was published for libpam-mount. CVE-2008-3970[0]: | pam_mount 0.10 through 0.45, when luserconf is enabled, does not | verify mountpoint and source ownership before mounting a | user-defined volume, which allows local users to bypass intended | access restrictions via a local mount. If you fix the vulnerability please also make sure to include the CVE id in your changelog entry. For further information see: [0] http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2008-3970 http://security-tracker.debian.net/tracker/CVE-2008-3970 ---End Message--- ---BeginMessage--- Source: libpam-mount Source-Version: 0.44-1+lenny1 We believe that the bug you reported is fixed in the latest version of libpam-mount, which is due to be installed in the Debian FTP archive: libpam-mount_0.44-1+lenny1.diff.gz to pool/main/libp/libpam-mount/libpam-mount_0.44-1+lenny1.diff.gz libpam-mount_0.44-1+lenny1.dsc to pool/main/libp/libpam-mount/libpam-mount_0.44-1+lenny1.dsc libpam-mount_0.44-1+lenny1_amd64.deb to pool/main/libp/libpam-mount/libpam-mount_0.44-1+lenny1_amd64.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Nico Golde [EMAIL PROTECTED] (supplier of updated libpam-mount package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Fri, 03 Oct 2008 17:58:26 +0200 Source: libpam-mount Binary: libpam-mount Architecture: source amd64 Version: 0.44-1+lenny1 Distribution: testing-security Urgency: high Maintainer: Bastian Kleineidam [EMAIL PROTECTED] Changed-By: Nico Golde [EMAIL PROTECTED] Description: libpam-mount - PAM module that can mount volumes for a user session Closes: 499841 Changes: libpam-mount (0.44-1+lenny1) testing-security; urgency=high . * Non-maintainer upload by the Security Team. * Add security checks including mountpoint and source ownership verification before mounting user-defined volumes to prevent access restriction bypasses (07_CVE-2008-3970.dpatch; Closes: #499841). Checksums-Sha1: aef22d9080013679c40225db16c6b4e642f0f98a 1249 libpam-mount_0.44-1+lenny1.dsc 01a86631c1a5885e9a45b88081d70f31a2161408 429353 libpam-mount_0.44.orig.tar.gz ca2497d292950d43faef9a21b99ab2cb1d115139 25386 libpam-mount_0.44-1+lenny1.diff.gz 974038ae4d97bf8d047dee5c7cfaaaf0952c5e70 104370 libpam-mount_0.44-1+lenny1_amd64.deb Checksums-Sha256: 2048629ad34b714689624e0f596e225781069c4efd0264f2e5eabebc1fef0264 1249 libpam-mount_0.44-1+lenny1.dsc f3e09e06ff3ee7eb7b6d000a74403597658ee8c96339be6537a14d2cb502b87b 429353 libpam-mount_0.44.orig.tar.gz 5fd2e5854d606cf107ebfae4d72c571c4287dff17567d7ddda87f7bb469c8c67 25386 libpam-mount_0.44-1+lenny1.diff.gz ea848594d23c17a3b6a1cbc2f1d5d62f84b3b174e80e93f43a1f966f8fe38658 104370 libpam-mount_0.44-1+lenny1_amd64.deb Files: 1db662e022028990fb1708e6bd28915a 1249 admin extra libpam-mount_0.44-1+lenny1.dsc 05ceba2445efa851deecb570f73e8e92 429353 admin extra libpam-mount_0.44.orig.tar.gz 91eb158c7447a01e838ea96dc27314d6 25386 admin extra libpam-mount_0.44-1+lenny1.diff.gz eaf2ab48e7803b09fb6f72c6044ae618 104370 admin extra libpam-mount_0.44-1+lenny1_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkjmRooACgkQHYflSXNkfP89eACdEcEJaLKRYFP1uxzrQx8o/BzT czEAn3lJcm7sg2nR/dUR9lIajDeVZH7U =JVsY -END PGP SIGNATURE- ---End Message---
Bug#442664: marked as done (qtstalker: newer BDB)
Your message dated Fri, 03 Oct 2008 17:47:06 + with message-id [EMAIL PROTECTED] and subject line Bug#442664: fixed in qtstalker 0.32-3.2 has caused the Debian Bug report #442664, regarding qtstalker: newer BDB to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [EMAIL PROTECTED] immediately.) -- 442664: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=442664 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: qtstalker Version: 0.32-3 User: [EMAIL PROTECTED] Usertags: oldbdb db4.3 Please switch your package to db4.6 so we can get rid of db4.3. ---End Message--- ---BeginMessage--- Source: qtstalker Source-Version: 0.32-3.2 We believe that the bug you reported is fixed in the latest version of qtstalker, which is due to be installed in the Debian FTP archive: qtstalker-doc_0.32-3.2_all.deb to pool/main/q/qtstalker/qtstalker-doc_0.32-3.2_all.deb qtstalker_0.32-3.2.diff.gz to pool/main/q/qtstalker/qtstalker_0.32-3.2.diff.gz qtstalker_0.32-3.2.dsc to pool/main/q/qtstalker/qtstalker_0.32-3.2.dsc qtstalker_0.32-3.2_i386.deb to pool/main/q/qtstalker/qtstalker_0.32-3.2_i386.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Luk Claes [EMAIL PROTECTED] (supplier of updated qtstalker package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sat, 27 Sep 2008 18:50:06 +0200 Source: qtstalker Binary: qtstalker qtstalker-doc Architecture: source all i386 Version: 0.32-3.2 Distribution: unstable Urgency: low Maintainer: Marco van Zwetselaar [EMAIL PROTECTED] Changed-By: Luk Claes [EMAIL PROTECTED] Description: qtstalker - commodity and stock market charting and technical analysis qtstalker-doc - documentation for Qtstalker Closes: 442664 Changes: qtstalker (0.32-3.2) unstable; urgency=low . * Non-maintainer upload. * debian/control: update libdb4.3-dev to libdb-dev (Closes: #442664). Checksums-Sha1: 8397e307a23eb1a9f3c50028cc67dd8db50ff341 1076 qtstalker_0.32-3.2.dsc 8da75521df12f404242389683c38890b6e4017b4 11823 qtstalker_0.32-3.2.diff.gz ea4da43ce6c2c6cb9983d9ba900ffd8133c77a57 793920 qtstalker-doc_0.32-3.2_all.deb 78a9533c12c227097a7cbf9215d1d81e3c585dca 1599654 qtstalker_0.32-3.2_i386.deb Checksums-Sha256: dbc0c36c239c40aabd2a7063ba1fcf1daf68e72ed19248531aa3ed80ef77ace4 1076 qtstalker_0.32-3.2.dsc e3e8d0b0acc1d2aee6cdc7667a3b49c2c9f8c7aafead226609fd3a39aa538486 11823 qtstalker_0.32-3.2.diff.gz 1a77e0dfd6921856c9bbce835480733a04e0b4a2f56d2ceed1aa6d68a4f1c2c3 793920 qtstalker-doc_0.32-3.2_all.deb 9ab5b0f2cfd7cda58dcd4aa16e557b7f54ea0ab2be4508fc6f3d0c5c326eca68 1599654 qtstalker_0.32-3.2_i386.deb Files: 8aa54addac715986f24363fff577c839 1076 misc extra qtstalker_0.32-3.2.dsc d082192cddad9e607b225a2d4c26f3da 11823 misc extra qtstalker_0.32-3.2.diff.gz 979f752b6541405da7a374297d7dbfe4 793920 doc extra qtstalker-doc_0.32-3.2_all.deb 1bb28b7c2b7b59689b6a3d51fe9c9f55 1599654 misc extra qtstalker_0.32-3.2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkjeZo4ACgkQ5UTeB5t8Mo21CACdG//0SWHIwFtoqFMZCCdyQNdo q3oAoJW9OCAmVX0S09L6LQ6HrdwmUWJi =KDJP -END PGP SIGNATURE- ---End Message---
Bug#462180: marked as done (realtime-lsm: debian/copyright doesn't provide correct/full Copyright information)
Your message dated Fri, 3 Oct 2008 20:24:45 +0100 with message-id [EMAIL PROTECTED] and subject line realtime-lsm has been removed from Debian, closing #462180 has caused the Debian Bug report #462180, regarding realtime-lsm: debian/copyright doesn't provide correct/full Copyright information to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [EMAIL PROTECTED] immediately.) -- 462180: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=462180 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Source: realtime-lsm Severity: serious Version: 0.8.7-3 Usertags: bad-copyright The copyright file[1] of the package doesn't contain the necessary copyright information. This is usually in the form of Copyright by John Doe [EMAIL PROTECTED] [1]http://packages.debian.org/changelogs/pool/main/r/realtime-lsm/realtime-lsm_0.8.7-3/copyright Kind regards, -- Atomo64 - Raphael Please avoid sending me Word, PowerPoint or Excel attachments. See http://www.gnu.org/philosophy/no-word-attachments.html ---End Message--- ---BeginMessage--- Version: 0.8.7-3.1+rm The realtime-lsm package has been removed from Debian testing, unstable and experimental, so I am now closing the bugs that were still opened against it. For more information about this package's removal, read http://bugs.debian.org/499245 . That bug might give the reasons why this package was removed, and suggestions of possible replacements. Don't hesitate to reply to this mail if you have any question. Thank you for your contribution to Debian. -- Marco Rodrigues http://Marco.Tondela.org ---End Message---
Bug#425942: marked as done (realtime-lsm-source: Doesn't compile with linux 2.6.21)
Your message dated Fri, 3 Oct 2008 20:24:40 +0100
with message-id [EMAIL PROTECTED]
and subject line realtime-lsm has been removed from Debian, closing #425942
has caused the Debian Bug report #425942,
regarding realtime-lsm-source: Doesn't compile with linux 2.6.21
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)
--
425942: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=425942
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
---BeginMessage---
Package: realtime-lsm-source
Version: 0.8.7-3
Severity: grave
Justification: renders package unusable
I just tried to build the module with a custom kernel compile from
linux-source-2.6.21 (Version: 2.6.21-2) with SMP disabled and security
capabilities set to module by making use of make-kpkg
--append-to-version -a64 modules.
The log is:
make[1]: Entering directory `/usr/src/modules/realtime-lsm'
/usr/bin/make -w -f debian/rules kdist_clean kdist_config binary-modules
make[2]: Entering directory `/usr/src/modules/realtime-lsm'
dh_clean
make COMMONCAP=none clean
make[3]: Entering directory `/usr/src/modules/realtime-lsm'
rm -f *.ko *.o none
rm -f *.mod.* .*.cmd
make[3]: Leaving directory `/usr/src/modules/realtime-lsm'
for templ in
/usr/src/modules/realtime-lsm/debian/realtime-lsm-module-_KVERS_.postinst
/usr/src/modules/realtime-lsm/debian/realtime-lsm-module-_KVERS_.postinst.modules.in;
do \
cp $templ `echo $templ | sed -e 's/_KVERS_/2.6.21-a64/g'` ; \
done
for templ in `ls debian/*.modules.in` ; do \
test -e ${templ%.modules.in}.backup || cp ${templ%.modules.in}
${templ%.modules.in}.backup 2/dev/null || true; \
sed -e 's/##KVERS##/2.6.21-a64/g ;s/#KVERS#/2.6.21-a64/g ;
s/_KVERS_/2.6.21-a64/g ; s/##KDREV##/1/g ; s/#KDREV#/1/g ;
s/_KDREV_/1/g ' $templ ${templ%.modules.in}; \
done
dh_testdir
dh_testroot
dh_clean -k
make KERNEL_DIR=/usr/src/linux MODVERSIONS=detect
KERNEL=linux-2.6.21-a64 COMMONCAP=none
make[3]: Entering directory `/usr/src/modules/realtime-lsm'
CONFIG_SECURITY_CAPABILITIES=m
make CC=gcc-4.1 modules -C /usr/src/linux SUBDIRS=/usr/src/modules/realtime-lsm
make[4]: Entering directory `/usr/src/linux-source-2.6.21'
CC [M] /usr/src/modules/realtime-lsm/realcap.o
/usr/src/modules/realtime-lsm/realcap.c:14:26: error: linux/config.h:
No such file or directory
/usr/src/modules/realtime-lsm/realcap.c:36: error: expected ')' before
string constant
/usr/src/modules/realtime-lsm/realcap.c:40: error: expected ')' before
string constant
/usr/src/modules/realtime-lsm/realcap.c:44: error: expected ')' before
string constant
/usr/src/modules/realtime-lsm/realcap.c:48: error: expected ')' before
string constant
make[5]: *** [/usr/src/modules/realtime-lsm/realcap.o] Error 1
make[4]: *** [_module_/usr/src/modules/realtime-lsm] Error 2
make[4]: Leaving directory `/usr/src/linux-source-2.6.21'
make[3]: *** [all] Error 2
make[3]: Leaving directory `/usr/src/modules/realtime-lsm'
make[2]: *** [binary-modules] Error 2
make[2]: Leaving directory `/usr/src/modules/realtime-lsm'
make[1]: *** [kdist_build] Error 2
make[1]: Leaving directory `/usr/src/modules/realtime-lsm'
Module /usr/src/modules/realtime-lsm failed.
-- System Information:
Debian Release: lenny/sid
APT prefers testing
APT policy: (500, 'testing'), (100, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.18-a64 (SMP w/1 CPU core)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages realtime-lsm-source depends on:
ii bzip2 1.0.3-6high-quality block-sorting file co
ii debhelper 5.0.49 helper programs for debian/rules
ii kernel-package11.001 A utility for building Linux kerne
realtime-lsm-source recommends no packages.
-- no debconf information
--
Atomo64 - Raphael
Please avoid sending me Word, PowerPoint or Excel attachments.
See http://www.gnu.org/philosophy/no-word-attachments.html
---End Message---
---BeginMessage---
Version: 0.8.7-3.1+rm
The realtime-lsm package has been removed from Debian testing, unstable and
experimental, so I am now closing the bugs that were still opened
against it.
For more information about this package's removal, read
http://bugs.debian.org/499245 . That bug might give the reasons why
this package was removed, and suggestions of possible replacements.
Don't hesitate to reply to this mail if you have any question.
Thank you for your contribution to Debian.
--
Marco Rodrigues
http://Marco.Tondela.org
---End Message---
Bug#491101: marked as done (lcap: doesn't work with linux 2.6.25)
Your message dated Fri, 3 Oct 2008 20:21:56 +0100 with message-id [EMAIL PROTECTED] and subject line lcap has been removed from Debian, closing #491101 has caused the Debian Bug report #491101, regarding lcap: doesn't work with linux 2.6.25 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [EMAIL PROTECTED] immediately.) -- 491101: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=491101 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: lcap Version: 0.0.6-4 lcap doesn't work anymore since upgrading from linux 2.6.24 to 2.6.25. It says: /proc/sys/kernel/cap-bound: No such file or directory Kind regards, Martin ---End Message--- ---BeginMessage--- Version: 0.0.6-4+rm The lcap package has been removed from Debian testing, unstable and experimental, so I am now closing the bugs that were still opened against it. For more information about this package's removal, read http://bugs.debian.org/499183 . That bug might give the reasons why this package was removed, and suggestions of possible replacements. Don't hesitate to reply to this mail if you have any question. Thank you for your contribution to Debian. -- Marco Rodrigues http://Marco.Tondela.org ---End Message---
Bug#500461: libtidy-ruby1.8: SecurityError raised by Tidy.open on ruby1.8 1.8.7.72-1
I can have libtidy-ruby work correcly at least on some cases. So this probably needs more information on how to reproduce. Typically, in the source package, running test/usage.rb instanciates a Tidy object and does not raise any security exception. -- Arnaud Cornet -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#500615: mmorph: diff for NMU version 2.3.4.2-11.1
On Fri, Oct 03, 2008 at 09:48:08AM -0700, Thomas Bushnell BSG wrote: Also, can you point me to a comprehensive statement of the interface changes in the db library which may affect mmorph? I'm sure you have that right at hand because I'm sure you went through it carefully before making an upload. mmorph appears to use the db 1.85 compatibility layer, which should not have undergone very many interface changes since the '90s. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#499740: libwx-perl - FTBFS: Failed 3/4 test scripts. 8/9 subtests failed.
tags 499740 -unreproducible thanks -=| Bastian Blank, Fri, Oct 03, 2008 at 05:26:52PM +0200 |=- found 499740 0.86-2 Sad, but true. The package fails on numerous architectures, in three different ways: * arm: the first test fails (wstat 11) * alpha, armel, hppa, mips, mipsel, s390, sparc: the splashfast test fails (wstat 11) * powerpc: compilation fails as ./configure seems to look for wx2.6 Build succeeded on amd64, i386 and ia64. m68k build not attempted yet. Ouch! -- damJabberID: [EMAIL PROTECTED] signature.asc Description: Digital signature
Processed: Re: Bug#499740: libwx-perl - FTBFS: Failed 3/4 test scripts. 8/9 subtests failed.
Processing commands for [EMAIL PROTECTED]: tags 499740 -unreproducible Bug#499740: libwx-perl - FTBFS: Failed 2/4 test scripts. 6/9 subtests failed. Tags were: unreproducible Tags removed: unreproducible 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#500615: mmorph: diff for NMU version 2.3.4.2-11.1
Thomas Bushnell BSG wrote: On Fri, 2008-10-03 at 07:56 +0200, Luk Claes wrote: tags 500615 + patch thanks Dear maintainer, I've prepared an NMU for mmorph (versioned as 2.3.4.2-11.1) and uploaded it to DELAYED/3. Please feel free to tell me if I should delay it longer. Yes, please remove it from the upload queue. Removed. I'm assuming as well that you have done extensive testing. Can you point me to the tests you used to verify the functionality of the patch you wish to upload? You had marked yourself that it builds with all db versions... Also, can you point me to a comprehensive statement of the interface changes in the db library which may affect mmorph? I'm sure you have that right at hand because I'm sure you went through it carefully before making an upload. You yourself stated in the Build-Depends that whatever db version is good enough... Finally, may I point out that it is not reasonable to file an RC bug and then an NMU all at about the same time, at this point in the release? I didn't do that at all, I waited for a couple of days to give you time to respond. You knew already that it was coming by the way as you already commented on similar bugs... The time for deciding to remove the package was back at the BEGINNING of the release cycle, not now, at the end. Can you explain why you chose to wait until now to start making such changes? I didn't wait at all, I informed maintainers at the beginning of the cycle, though if at the end of the cycle there are too much versions (5 in this case) of a library we can either remove the whole lot that depends on them or make them build against a version we do intend to be included in the release... Cheers Luk -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#499898: marked as done (ntfs-3g: Files copied not complete)
Your message dated Fri, 03 Oct 2008 22:47:11 +0200 with message-id [EMAIL PROTECTED] and subject line Re: Bug#499898: ntfs-3g: Files copied not complete has caused the Debian Bug report #499898, regarding ntfs-3g: Files copied not complete to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [EMAIL PROTECTED] immediately.) -- 499898: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=499898 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: ntfs-3g Version: 1:1.2531-1 Severity: grave Justification: causes non-serious data loss I converted a partition from NTFS to EXT3. So first i backuped the partition on a USB-HD with NTFS-partition. Then i formatted the local partition with EXT3 and copied the files back. In both cases the where 2-3 files that where not copied in complete size! This happens even by copying NTFS - NTFS and NTFS - EXT3. After i copied the incomplete files again everything was fine. The first time i used Krusader for coying, after the first problem i copied in an xterm with cp -R -v. So it should not be a problem of the tool or cp has a problem itself. I copied 22868 files in 703 directories with 47,2 GB of data. Maybe an upgrade to the new ntfs-3g-1.2918, released on September 18, 2008 will help ? I also asked for this problem at ntfs-3d.org and refer to this bug. http://forum.ntfs-3g.org/viewtopic.php?t=969 Cheers Karsten -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.26-1-amd64 (SMP w/2 CPU cores) Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-1) (ignored: LC_ALL set to de_DE) Shell: /bin/sh linked to /bin/bash Versions of packages ntfs-3g depends on: ii libc6 2.7-13 GNU C Library: Shared libraries ii libntfs-3g31 1:1.2531-1 ntfs-3g filesystem in userspace (F ntfs-3g recommends no packages. ntfs-3g suggests no packages. -- no debconf information ---End Message--- ---BeginMessage--- Josselin Mouette a écrit : Hi, according to the dmesg logs posted by the submitter to the ntfs-3g forum, it seems clear the issue is caused by I/O errors. I guess this bug should simply be closed. Cheers, Hello Josselin, Yes the problem comes from the hardware or maybe from the kernel. I'm closing this bug. Check #499900 to see submitter's logs. Regards, Adam. ---End Message---
Bug#500778: libnss-ldapd: groups resolve to nogroup after boot
(Cc-ing the nfs-utils maintainers, perhaps they have some insight that could solve this) On Sat, 2008-10-04 at 09:52 +0200, Patrick Schoenfeld wrote: My guess is that name lookups are cached in idmapd. Can you check that by restarting idmapd (/etc/init.d/nfs-common restart) the problem goes away? Nope, it does not. I have been able to reproduce this. On the server I have in /etc/exports (/export/newhome is a bind-mounted /home with half a dozen users): /export 192.168.1.0/24(ro,sync,insecure,root_squash,no_subtree_check,fsid=0) /export/newhome 192.168.1.0/24(rw,nohide,sync,insecure,root_squash,no_subtree_check) On the client I have in /etc/fstab: fs:/newhome/mntnfs4 rw 0 0 Now if I stop nslcd (all name lookup calls should now return NSS_STATUS_UNAVAIL/ENOENT) an 'ls -l /mnt' shows: [...] drwx-x 148 nobody users 12288 Oct 3 21:02 arthur [...] (the user arthur from the server is mapped to the user nobody on the client because the namelookup failed). With some more verbose logging rpc.idmapd shows: [...] rpc.idmapd: nfs4_name_to_uid: calling nsswitch-name_to_uid rpc.idmapd: nss_getpwnam: name '[EMAIL PROTECTED]' domain 'localdomain': resulting localname 'arthur' rpc.idmapd: nss_getpwnam: name 'arthur' not found in domain 'localdomain' rpc.idmapd: nfs4_name_to_uid: nsswitch-name_to_uid returned -2 rpc.idmapd: nfs4_name_to_uid: final return value is -2 rpc.idmapd: Client 16: (user) name [EMAIL PROTECTED] - id 65534 [...] If I repeat the ls command a couple of times rpc.idmapd no longer logs the failed lookups and a strace of rpc.idmapd also shows that that process is no longer asked (by the kernel?) to look up the user. If I then start nslcd (now name lookups should be performed as usual and getent shows that they do) the results aren't quickly fixed. After a while (I've been messing about with stuff in /proc so I don't know how long this normally takes) the kernel asks rpc.idmapd again to look up user arthur (and the other users in the filesystem). Also note that the bugreporter had problems with groups and I've reproduced the behaviour with users. [...] drwx-x 148 arthur users 12288 Oct 3 21:02 /mnt/arthur [...] Now the question is, how should this caching mechanism be tuned and how should we solve this problem. Is there a reliable way to flush the cache? There seems to be /proc/net/rpc/nfs4.nametoid which contains some stuff that could be relevant and /proc/sys/fs/nfs/idmap_cache_timeout. However setting /proc/sys/fs/nfs/idmap_cache_timeout or Cache-Expiration does not result in the expected timeout in seconds (read from the idmapd.c). Setting it to 10 results in a retry every 30 to 60 seconds, setting it to 100 seems to result in a retry in 60-120 seconds. Also, writing to /proc/net/rpc/nfs4.idtoname/flush and /proc/net/rpc/nfs4.nametoid/flush (like is done in flush_nfsd_idmap_cache()) doesn't seem to make a difference. I haven't had a look at the kernel code yet (this is running kernel Linux 2.6.26-1-686 (SMP w/2 CPU cores)). Patrick, does adding Cache-Expiration = 10 to /etc/idmapd.conf in the [General] section help at all in your setup? (the correct values should be loaded sooner) -- -- arthur - [EMAIL PROTECTED] - http://people.debian.org/~adejong -- signature.asc Description: This is a digitally signed message part
Bug#500615: mmorph: diff for NMU version 2.3.4.2-11.1
On Fri, 2008-10-03 at 22:48 +0200, Luk Claes wrote: I didn't wait at all, I informed maintainers at the beginning of the cycle, though if at the end of the cycle there are too much versions (5 in this case) of a library we can either remove the whole lot that depends on them or make them build against a version we do intend to be included in the release... Um, I don't think a report was filed against mmorph. What form of informing did you use? (Emails to debian-devel are not adequate in my opinion.) Thomas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: netmrg: diff for NMU version 0.20-2.1
Processing commands for [EMAIL PROTECTED]: tags 494221 + patch pending Bug#494221: netmrg: FTBFS: *** [zero.rrd] Segmentation fault There were no tags set. Tags added: patch, pending 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#494221: netmrg: diff for NMU version 0.20-2.1
tags 494221 + patch pending thanks Hi Uwe, here is my netmrg NMU (version 0.20-2.1), bumping the build-dependency to the fixed rrdtool. Kind regards T. diff -u netmrg-0.20/debian/control netmrg-0.20/debian/control --- netmrg-0.20/debian/control +++ netmrg-0.20/debian/control @@ -2,7 +2,7 @@ Section: net Priority: optional Maintainer: Uwe Steinmann [EMAIL PROTECTED] -Build-Depends: rrdtool, debhelper (= 4.1.16), debconf, libxml2-dev, libmysqlclient15-dev, libsnmp-dev, xsltproc, docbook-xsl +Build-Depends: rrdtool (= 1.3.1-4), debhelper (= 4.1.16), debconf, libxml2-dev, libmysqlclient15-dev, libsnmp-dev, xsltproc, docbook-xsl Standards-Version: 3.7.2 Package: netmrg diff -u netmrg-0.20/debian/changelog netmrg-0.20/debian/changelog --- netmrg-0.20/debian/changelog +++ netmrg-0.20/debian/changelog @@ -1,3 +1,11 @@ +netmrg (0.20-2.1) unstable; urgency=low + + * Non-maintainer upload. + * Version rrdtool build-dependency to = 1.3.1-4 to avoid +rrdtool segfaults during build. (Closes: #494221) + + -- Thomas Viehmann [EMAIL PROTECTED] Fri, 03 Oct 2008 23:03:33 +0200 + netmrg (0.20-2) unstable; urgency=low * Create temp directory in rrdedit (Closes: #496384) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#500615: mmorph: diff for NMU version 2.3.4.2-11.1
Thomas Bushnell BSG wrote: On Fri, 2008-10-03 at 22:48 +0200, Luk Claes wrote: I didn't wait at all, I informed maintainers at the beginning of the s/maintainers/ of multiple version library packages/ cycle, though if at the end of the cycle there are too much versions (5 in this case) of a library we can either remove the whole lot that depends on them or make them build against a version we do intend to be included in the release... Cheers Luk -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
