Bug#500555: tries to access not existing/usr/var/run
Y Giridhar Appaji Nag wrote: Hi debian-release, On 08/10/01 08:31 +0200, Pierre Habouzit said ... On Tue, Sep 30, 2008 at 10:54:11AM +, Y Giridhar Appaji Nag wrote: On 08/09/29 12:26 +0200, Rene Engelhard said ... Package: libdaemon0 Version: 0.10-1 Severity: grave Since 0.13 is already in sid and this bug affects 0.12-1 (in Lenny) I would like to upload 0.12-1lenny1 to testing-proposed-updates. Please do let me know if that is OK. (The version numbers should have been 0.12-2 and 0.12-2lenny1.) Please do. Now that libdaemon 0.12-2lenny1 has been built on all architectures, can someone please push it to testing? approval hint added Cheers Luk -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: Bug #498243: help requested
Processing commands for [EMAIL PROTECTED]: package xine-lib Ignoring bugs not assigned to: xine-lib tags 498243 + help Bug#498243: xine-lib: multiple heap overflows Tags were: security Tags added: help thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#498243: Bug #498243: help requested
package xine-lib tags 498243 + help thanks On 07-Oct-2008, Reinhard Tartler wrote: Reinhard Tartler [EMAIL PROTECTED] xine-lib (#498243) Needs help. Tagging the bug appropriately. -- \ “If nothing changes, everything will remain the same.” —Barne's | `\ Law | _o__) | Ben Finney [EMAIL PROTECTED] signature.asc Description: Digital signature
Bug#501207: destar: Fails to run with python2.5
On Tue, Oct 07, 2008 at 08:42:26AM +0300, Faidon Liambotis wrote: John, hi, John Wright wrote: The above problem is actually the same as bug 501207. However, with that patch applied, I get the following problem starting destar: snip The attached patch fixes the SyntaxError. Thanks a lot for these patches! I have absolutely no clue about python and I don't think anyone in the team does -- which effectively means that we need all the help we can get. So, bear with me if this is a silly question: I was under the impression that lenny will be shipped with both python 2.4 and 2.5 and that these should be co-installable. Yes, lenny will have both python2.4 and python2.5. One workaround, at least for the compiler.ast.From problem, would be to run destar with #!/usr/bin/python2.4 instead of #!/usr/bin/python. But I think it better to fix the bug rather than try to work around it, if possible. Are your fixes backwards compatible? It'd suck to fix this only to have a bug report the day after fails to run with python2.4 :) I made sure the fix for #501207 was backwards-compatible. As for the SyntaxError problem, I'm surprised it ever worked at all. Function definitions with optional arguments before required positional arguments aren't legal in 2.4 either (I'm not sure when/if they ever were). Maybe quixote used to generate different actual Python code than it does now in this case? Anyway, I'm pretty certain the patch for the SyntaxError will work with python2.4, but I'll check tomorrow. -- John Wright [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#501207: destar: Fails to run with python2.5
John Wright wrote: Yes, lenny will have both python2.4 and python2.5. One workaround, at least for the compiler.ast.From problem, would be to run destar with #!/usr/bin/python2.4 instead of #!/usr/bin/python. But I think it better to fix the bug rather than try to work around it, if possible. Definitely, my concern was for the backwards compatibility. Are your fixes backwards compatible? It'd suck to fix this only to have a bug report the day after fails to run with python2.4 :) I made sure the fix for #501207 was backwards-compatible. As for the SyntaxError problem, I'm surprised it ever worked at all. Function definitions with optional arguments before required positional arguments aren't legal in 2.4 either (I'm not sure when/if they ever were). Maybe quixote used to generate different actual Python code than it does now in this case? Anyway, I'm pretty certain the patch for the SyntaxError will work with python2.4, but I'll check tomorrow. Great, thanks a lot! Regards, Faidon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: tagging 450865
Processing commands for [EMAIL PROTECTED]: tags 450865 pending Bug#450865: mp3burn: All tracks become white noise after burning Tags were: unreproducible pending patch Bug#226606: mp3burn does not recognize the swab option correctly Bug#289822: mp3burn: Doesn't work anymore Tags added: pending End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#499070: dpkg leaves system in unusable state after running out of diskspace
On Thu, 18 Sep 2008, Guillem Jover wrote: The other is that when onerr_abort is signaled dpkg should not continue processing anything anymore, it should just do whatever cleanup is required and exit. But that can wait probably post-lenny. So this is the proper fix, and it should not be that big, probably less than 10 lines? Will cook something today or tomorrow... Any progress ? Cheers, -- Raphaël Hertzog Le best-seller français mis à jour pour Debian Etch : http://www.ouaza.com/livre/admin-debian/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#486334: segfault in iceweasel 3.0~rc2-1
Is this bug still present in Iceweasel? Can it be found in Iceweasel 3.0.3-1, which is available from unstable? No replies to this bugreport have been sent since July, so I suspect it that this problem has already been fixed. Could someone please confirm this so this bug report can be closed? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#500704: appears to work in 0.4.3-4
Hi, On Mon, 6 Oct 2008 21:34:22 +0100 Neil Williams [EMAIL PROTECTED] wrote: Using a clean chroot, I tested a simple install of naist-jdic 0.4.3-4 without problems. Restarting a new clean chroot, installed the dependencies for naist-jdic and downloaded the version from testing, 0.4.3-2 - installed cleanly with dpkg -i. apt-get install naist-jdic then completed successfully for v0.4.3-4. Thanks Neil! So, could I close this bug, Juhapekka? I'll do it tomorrow. -- Regards, Hideki Yamane henrich @ debian.or.jp/iijmio-mail.jp http://wiki.debian.org/HidekiYamane -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: setting severity to grave, second try
Processing commands for [EMAIL PROTECTED]: package kdeutils Ignoring bugs not assigned to: kdeutils severity 501393 grave Bug#501393: kdeutils-dev unsatisfiable Depends: kdelibs4-dev (= 4:3.5.10) Severity set to `grave' from `normal' reassign 501393 kdeutils-dev Bug#501393: kdeutils-dev unsatisfiable Depends: kdelibs4-dev (= 4:3.5.10) Bug reassigned from package `kdeutils' to `kdeutils-dev'. 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: marked as done (mmorph: Depends on libdb4.3 while it won't be included in the release)
Your message dated Mon, 06 Oct 2008 23:23:23 +0200 with message-id [EMAIL PROTECTED] and subject line fixed by 2.3.4.2-12 has caused the Debian Bug report #500615, regarding mmorph: Depends on libdb4.3 while it won't be included in the release 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.) -- 500615: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=500615 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: mmorph Version: 2.3.4.2-11 Severity: serious Hi mmorph Build-Depends on libdb4.3-dev | libdb-dev (and the binary package Depends on libdb4.3) while it's not going to be in the release. The alternative build dependency won't work as the buildds won't use it. Please test if your package works with libdb4.6 and remove the libdb4.3-dev build dependency from the alternative if it does. Cheers Luk ---End Message--- ---BeginMessage--- Version: 2.3.4.2-12 -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sun, 05 Oct 2008 15:05:22 -0700 Source: mmorph Binary: mmorph Architecture: source i386 Version: 2.3.4.2-12 Distribution: unstable Urgency: medium Maintainer: Thomas Bushnell, BSG [EMAIL PROTECTED] Changed-By: Thomas Bushnell, BSG [EMAIL PROTECTED] Description: mmorph - A two-level morphology tool for natural language processing Changes: mmorph (2.3.4.2-12) unstable; urgency=medium . * debian/control (Build-Depends): Omit libdb3-dev option since libdb-dev is now a real package instead of a virtual package. Closes: (#500615) Thanks to Luk Claes [EMAIL PROTECTED] for the bug report. Checksums-Sha1: ced61bcd8e2534c3d7bd50a61fe7bcaa332dea4d 978 mmorph_2.3.4.2-12.dsc 29c0038886a53cdcb34990a7c212fe1b23f2af01 7344 mmorph_2.3.4.2-12.diff.gz 964ee8e1cad47ce7659dae87f083f98b1517f25f 170410 mmorph_2.3.4.2-12_i386.deb Checksums-Sha256: 3c057ea7c4ee8853b230a44f804b08c47b3af99c64331c0f832660615a46d704 978 mmorph_2.3.4.2-12.dsc a3a1c6198e21f92d23a0f557d7e44d427966a33b0ee3a9e1a475338008da1fcc 7344 mmorph_2.3.4.2-12.diff.gz 14607ea2f0b006cfd82ea7827eb5415c37008b8798ce093dd2645cd6d5dd89aa 170410 mmorph_2.3.4.2-12_i386.deb Files: ba8d14f046c3be1a3a47ec21076a5c2c 978 misc extra mmorph_2.3.4.2-12.dsc f2f1749540fdf709055969434b7cc997 7344 misc extra mmorph_2.3.4.2-12.diff.gz aa74b8c756812d7a4ffe4c5364e14115 170410 misc extra mmorph_2.3.4.2-12_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkjpPGsACgkQqMsB9b6fcOrn3wCgy/fz0YVPvUbLvLqhNCCgGXi4 fboAoLmBqCXB3Y3JrMIOnUCInwngCgBG =A+YX -END PGP SIGNATURE- Accepted: mmorph_2.3.4.2-12.diff.gz to pool/main/m/mmorph/mmorph_2.3.4.2-12.diff.gz mmorph_2.3.4.2-12.dsc to pool/main/m/mmorph/mmorph_2.3.4.2-12.dsc mmorph_2.3.4.2-12_i386.deb to pool/main/m/mmorph/mmorph_2.3.4.2-12_i386.deb ---End Message---
Bug#501393: kdeutils-dev unsatisfiable Depends: kdelibs4-dev (= 4:3.5.10)
It is, jumped the deps by mistake. This will be likely being fixed uploading kdelibs 3.5.10. (no ETA) What about kdeutils 4:3.5.10-2 with just lowered depends. For GNU/kFreeBSD, we really appreciate installable sid, as we do not have testing and our lenny snapshot would be probably based on sid in time of lenny release. Thanks for considering it. Petr -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#482140: I could reproduce it
Hi, if this can help, here is how I encountered this bug: - downloaded http://cdimage.debian.org/debian-cd/4.0_r4a/i386/iso-cd/debian-40r4a-i386-businesscard.iso - installed debian in a virtualbox (Ubuntu Intrepid guest), with minimal system + graphical environment (default choices) - logged in gnome - in /etc/apt/sources.list, changed any etch occurence with lenny - apt-get update / apt-get dsit-upgrade - configuration of packages fails on docbook-xml with error: update-xmlcatalog: error: entity already registered dpkg: error processing docbook-xml (--configure): subprocess post-installation script returned error exit status 1 - consequently, scrollkeeper and other gnome componentns are not configured. Default gnome session does not work. - dpkg --purge docbook-xml / apt-get -f dist-upgrade works around the problem Hope this can help, Franck -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#482140: Reproducible and playing machine available
Hi there! Some notes before starting: 1) IMHO this bug is Severity: important, it leaves GNOME in an not usable state (see attached log) 2) I found this bug around one and a half week ago, but I performed more tests before replying (yes, I'm quite maniac with bugs...) I reproduced the error on three different installations: two plain etch on powerpc (where plain means Dekstop + Standard tasks, no more) and another etch on i386 which I installed on May and then left there, without never upgrading. One of the two powerpc installation is still in the error state, i.e. `apt-get dist-upgrade` produces an error. I can put it online and accessible via SSH only if you need it, it's a playing machine (the same used for bug #501367 [1]), thus you can do whatever you want. IIRC [2] I still have the whole etch /etc folder, in case you want to analyze it. I'm now installing etch on a QEMU image to check *again* if I can reproduce this bug: the advantage of QEMU is that you've the -snapshot option, thus you can test it whatever times you need. I'll report back as soon as the installation has finished. Thx, bye, Gismo / Luca Footnotes: [1] http://bugs.debian.org/501367 [2] it was last week, then I worked on other stuff etch-i386_dist-upgrade.log.gz Description: etch dist-upgrade: but in docbook-xml pgplUMMOyV0GC.pgp Description: PGP signature
Bug#486334: segfault in iceweasel 3.0~rc2-1
Stephan Peijnik wrote: Is this bug still present in Iceweasel? Can it be found in Iceweasel 3.0.3-1, which is available from unstable? No replies to this bugreport have been sent since July, so I suspect it that this problem has already been fixed. Could someone please confirm this so this bug report can be closed? Hi, I'm afraid the problem still remains. It seems that I'm the only unlucky man on earth who has this problem :-( Tell me what kind of trace you want, and I will send it to you. For the moment I revert to 2.0.0.16-0etch1 which is the last working version. --- Tom signature.asc Description: OpenPGP digital signature
Bug#500540: automounting vfat as utf8
Hi Sune and thanks for taking up the issue. On Mon, Oct 06, 2008 at 07:38:15PM +0200, Sune Vuorela wrote: KDE uses the information from hal to decide what options to use when mounting. On a vfat drive, hal gives the following: hal-get-property --udi '/org/freedesktop/Hal/devices/volume_uuid_64F8_AEF6' -- key volume.mount.valid_options ro sync dirsync noatime nodiratime noexec quiet remount exec utf8 shortname= codepage= iocharset= umask= dmask= fmask= uid= flush I'm with you there. $ hal-get-property --udi '/org/freedesktop/Hal/devices/volume_uuid_8851_B65A' --key volume.mount.valid_options ro sync dirsync noatime nodiratime noexec quiet remount exec utf8 shortname= codepage= iocharset= umask= dmask= fmask= uid= flush Auto-mounting via kde results in this: $ mount ... /dev/sdc1 on /media/disk-1 type vfat (rw,nosuid,nodev,noatime,uhelper=hal,flush,uid=1000,utf8,shortname=lower) $ pmount ... /dev/sdc1 on /media/disk-1 type vfat (rw,nosuid,nodev,noatime,uid=1000,fmask=0022,dmask=0022,codepage=cp437,iocharset=utf8,utf8,flush) And the kernel warning mentioned before. So far we established the same facts. Now let's see if hal really is to blame. We'll unmount the device and tell hal not to advertize the utf8 option. $ pumount /dev/sdc1 $ hal-set-property --udi '/org/freedesktop/Hal/devices/volume_uuid_8851_B65A' --key volume.mount.valid_options --strlist-rem utf8 $ hal-get-property --udi '/org/freedesktop/Hal/devices/volume_uuid_8851_B65A' --key volume.mount.valid_options ro sync dirsync noatime nodiratime noexec quiet remount exec shortname= codepage= iocharset= umask= dmask= fmask= uid= flushh So now hal shouldn't tell anybody to mount this device with utf8. And just to be on the safe side we'll make sure that we get the default codepage and iocharset. $ hal-set-property --udi '/org/freedesktop/Hal/devices/volume_uuid_8851_B65A' --key volume.mount.valid_options --strlist-rem codepage= $ hal-set-property --udi '/org/freedesktop/Hal/devices/volume_uuid_8851_B65A' --key volume.mount.valid_options --strlist-post codepage=437 $ hal-set-property --udi '/org/freedesktop/Hal/devices/volume_uuid_8851_B65A' --key volume.mount.valid_options --strlist-rem iocharset= $ hal-set-property --udi '/org/freedesktop/Hal/devices/volume_uuid_8851_B65A' --key volume.mount.valid_options --strlist-post iocharset=iso8859-1 So lets see what hal says now: $ hal-get-property --udi '/org/freedesktop/Hal/devices/volume_uuid_8851_B65A' --key volume.mount.valid_options ro sync dirsync noatime nodiratime noexec quiet remount exec shortname= umask= dmask= fmask= uid= flush codepage=437 iocharset=iso8859-1 That looks nice to me. Now I'll open system:/media/ and click on the device to get it auto-mounted and opened. (And before you ask, no, I didn't unplug the device because that seems to reset all the hal options set before.) $ pmount ... /dev/sdc1 on /media/disk-1 type vfat (rw,nosuid,nodev,noatime,uid=1000,fmask=0022,dmask=0022,codepage=cp437,iocharset=utf8,flush) So, here we go againand the kernel happily logs another: [784167.941455] FAT: utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive! Looks like KDE doesn't realy care all that much about what hal says. At least it seems to have left out the utf8 flag option, so we know that we have some effect. But overriding the iocharset is a bad idea. KDE can of course specialcase and don't use the utf8 option on fat filesystems, but I don't think it is the job for the frontend to know which options is safe and unsafe. I agree. But it should care about the options that _are_ reported by the backend. In this case it is not the utf8 flag option but the iocharset=utf8 that causes the problems. From http://www.nslu2-linux.org/wiki/HowTo/MountFATFileSystems When the utf8 flag is specified along with iocharset the iocharset value only controls the character case handling - it has no effect on the encoding of the UNICODE characters as this will always use UTF-8. From that perspective hal is not to blame at all. Even if it reports the utf8 flag as a default mount option. In short: The problem seems to be that kde doesn't care what hal reports as an iocharset. BTW: I'm not quite sure if downgrading the bug to important is ok. It seems to mess up file system structures and that should be examined further. Maybe resulting in a separate bug that would carry on the grave severity while this bug could be downgraded. Until then I consider a messed up filesystem structure a grave bug. cheers -henrik -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#391935: Bug #391935: Re: The answer from Citrix Xen.org
Le mardi 07 octobre 2008 à 12:48 +1100, Ben Finney a écrit : Yes, we do need more detail; we need to know that *any* recipient of Debian can redistribute the work to anyone else, modified or unmodified, commercially or otherwise. (Or to know that these actions are not allowed, so that we can remove the package from Debian.) As for the modified or unmodified, I think we have already considered it acceptable to require a name change for significant modifications made by third-party distributors. For example, though I’m not sure, I think this is already the case for Apache. I’ll ask for clarifications about the rest. 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#501241: [Pkg-db-devel] Bug#501241: libdb4.6-dev: upgrade failure (unpack)
On Sun, Oct 05, 2008 at 11:04:15PM +0200, Michel Briand wrote: upgrading today (standard aptitude upgrade). Something went wrong (log pasted below). Yes, if you try running it again, it will probably go smoothly. One question: I installed libdb and libdb-dev via aptitude. I noted that many packages libdb* where installed since that first manual installation. I wonder why there is all theses packages... ??? There is work going on to reduce the number. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#486334: segfault in iceweasel 3.0~rc2-1
On Tue, 2008-10-07 at 09:49 +0200, Thomas Pietrzak wrote: I'm afraid the problem still remains. It seems that I'm the only unlucky man on earth who has this problem :-( This is odd. Could it be possible that this is the result of another malfunction in your system? Did you try doing a fresh install of Debian yet? I am not asking you to go ahead, delete everything and start over, but it is possible that it is relevant only to your setup. Did you by any chance install thirdparty programs that come with libraries Iceweasel is using? It could be worth giving this a try. You could for example, install Debian on your PC using an external hard drive, so you would not lose any data or your setup, but only some space on the external drive. Tell me what kind of trace you want, and I will send it to you. For the moment I revert to 2.0.0.16-0etch1 which is the last working version. Ok, so it has to be related to an Iceweasel 3 feature. Regards, Stephan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#501422: marked as done (qmtest: FTBFS in lenny: Nonexistent build-dependency: python-happydoc)
Your message dated Tue, 07 Oct 2008 12:15:21 +0200 with message-id [EMAIL PROTECTED] and subject line Re: Bug#501422: qmtest: FTBFS in lenny: Nonexistent build-dependency: python-happydoc has caused the Debian Bug report #501422, regarding qmtest: FTBFS in lenny: Nonexistent build-dependency: python-happydoc 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.) -- 501422: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=501422 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: qmtest Version: 2.4-3 Severity: serious User: [EMAIL PROTECTED] Usertags: qa-ftbfs-20081006 qa-ftbfs Justification: FTBFS on i386 Hi, During a rebuild of all packages in a lenny chroot, your package failed to build on i386. Relevant part: ** Using build dependencies supplied by package: Build-Depends: debhelper (= 5.0.37.1), docbook-dsssl, docbook-xml, jadetex, python-all-dev (= 2.4), python-central (= 0.6), python-extclass (= 1.2.0zope-2.5.1-1.3), python-happydoc, sgml-data, tidy Checking for already installed source dependencies... W: Unable to locate package python-happydoc debhelper: missing Using default version 7.0.15 docbook-dsssl: missing docbook-xml: missing jadetex: missing python-all-dev: missing Using default version 2.5.2-2 python-central: missing Using default version 0.6.8 python-extclass: missing Using default version 1.2.0zope-2.5.1-6 python-happydoc: missing sgml-data: missing tidy: missing Checking for source dependency conflicts... Reading package lists... Building dependency tree... Reading state information... E: Couldn't find package python-happydoc The full build log is available from: http://newpeople.debian.org/~lucas/logs/2008/10/06 It is possible that your package builds fine in sid, but you should make sure that your package also builds fine in lenny before the release. A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot containing a sid i386 environment. Internet was not accessible from the build systems. -- | Lucas Nussbaum | [EMAIL PROTECTED] http://www.lucas-nussbaum.net/ | | jabber: [EMAIL PROTECTED] GPG: 1024D/023B3F4F | ---End Message--- ---BeginMessage--- Version: 2.4-3.1 Lucas Nussbaum schrieb: Package: qmtest Version: 2.4-3 Severity: serious User: [EMAIL PROTECTED] Usertags: qa-ftbfs-20081006 qa-ftbfs Justification: FTBFS on i386 Hi, During a rebuild of all packages in a lenny chroot, your package failed to build on i386. this is already fixed in unstable ---End Message---
Processed: r1319 - in trunk/debian: . patches
Processing commands for [EMAIL PROTECTED]: tags 501413 pending Bug#501413: mysql-dfsg-5.0: FTBFS in lenny: failed test: rpl_packet There were no tags set. 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#498965: Claims Requirments
Contact Mr. Pinkett ([EMAIL PROTECTED]) for the claims of £500,000 pounds in the UK National LotteryAward 2008. Claims Requirement: Fullname,Occupation,Nationality,Resedential Address, Phone. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: Re: Bug#494202: Installation script overwrites existing sympa.conf
Processing commands for [EMAIL PROTECTED]: severity 494202 important Bug#494202: Installation script overwrites existing sympa.conf Severity set to `important' from `serious' thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#500826: zabbix: Upgrade to Zabbix 1.6 does not work out-of-the-box, SQL upgrade scripts are not included in package?
hi, On Wed, Oct 01, 2008 at 08:53:02PM +0200, Bas van Schaik wrote: After upgrading my Zabbix 1.4.6 installation from Lenny to Zabbix 1.6 from Sid Zabbix does not work anymore, complaining about unknown column 'g.gui_access' and unknown column 'g.users_status'. Clearly, upgrading Zabbix also involves upgrading the MySQL (or PostgreSQL?) tables, which is not automagically done by installing the new package from unstable. did you answer dbconfig-commons questions to upgrade the database layout? I guess you either said no after beeing asked if dbconfig-common should handly the database upgrade, or you didnt see them at all, due to your debconf settings which may ignore questions of certain priority? I was testing the upgrade from 1.4.x to 1.6 on my box and it was all done by dbconfig-common .. bye, - michael -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#500826: zabbix: Upgrade to Zabbix 1.6 does not work out-of-the-box, SQL upgrade scripts are not included in package?
Michael Ablassmeier wrote: hi, On Wed, Oct 01, 2008 at 08:53:02PM +0200, Bas van Schaik wrote: After upgrading my Zabbix 1.4.6 installation from Lenny to Zabbix 1.6 from Sid Zabbix does not work anymore, complaining about unknown column 'g.gui_access' and unknown column 'g.users_status'. Clearly, upgrading Zabbix also involves upgrading the MySQL (or PostgreSQL?) tables, which is not automagically done by installing the new package from unstable. did you answer dbconfig-commons questions to upgrade the database layout? I guess you either said no after beeing asked if dbconfig-common should handly the database upgrade, or you didnt see them at all, due to your debconf settings which may ignore questions of certain priority? I was testing the upgrade from 1.4.x to 1.6 on my box and it was all done by dbconfig-common .. I didn't get any dbconfig-common question at all. Maybe it is important to note that my MySQL server is actually running on another server? Anyhow, I think it would be best to also include the SQL-scripts like supplied by upstream, wouldn't it? Regards, -- Bas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: found 501294 in 1.1-1
Processing commands for [EMAIL PROTECTED]: found 501294 1.1-1 Bug#501294: libncurses-ruby1.9: I can't require 'ncurses' Bug marked as found in version 1.1-1. 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#500826: zabbix: Upgrade to Zabbix 1.6 does not work out-of-the-box, SQL upgrade scripts are not included in package?
Michael Ablassmeier wrote: hi Bas, On Tue, Oct 07, 2008 at 01:58:17PM +0200, Bas van Schaik wrote: I didn't get any dbconfig-common question at all. Maybe it is important to note that my MySQL server is actually running on another server? Anyhow, I think it would be best to also include the SQL-scripts like supplied by upstream, wouldn't it? this should make any difference. dbconfig-common can handle databases on remote machines too. So i guess its your debconf setting which ignored these kind of questions then (we had this several times in the past). The Upgrade scripts come with the package, are installed to: ./usr/share/dbconfig-common/data/zabbix-server-mysql/upgrade/mysql/1:1.6 can you confirm i can close this bug? You mean that this should _not_ make any difference, I assume? Well, in that case I think it's just my dbconfig-common that is misconfigured. The scripts are indeed in the specified directory, but maybe you can document their existence somewhere in /usr/share/doc? I just wasn't expecting them somewhere in /usr/share/dbconfig-common... -- Bas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#491590: binaries for cegui-mk2
Hello, I've already built the binaries for the new cegui-mk2 source package. For me it solves the startup segfault, but I'm still not able to play, because SMC segfaults after starting the first level (if it isn't a local thing, I'll file a bugreport for that, with proper information). Meanwhile, if anybody likes to try out the cegui-mk2 packages I've built to get his/her copy of smc (or any other depending package, if there is one) running, go ahead, you'll find them at [0]. Please pay attention to the notes. Greetings, Kai [0] http://www.carbon-project.org/dev/debian/cegui/ -- 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#501026: marked as done (ipsec-tools: CVE-2008-3652 denial of service for authenticated attackers)
Your message dated Tue, 07 Oct 2008 12:47:03 +
with message-id [EMAIL PROTECTED]
and subject line Bug#501026: fixed in ipsec-tools 1:0.7.1-1.2
has caused the Debian Bug report #501026,
regarding ipsec-tools: CVE-2008-3652 denial of service for authenticated
attackers
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.)
--
501026: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=501026
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
---BeginMessage---
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
pgplMmcDb4dC5.pgp
Description: PGP signature
---End Message---
---BeginMessage---
Source: ipsec-tools
Source-Version: 1:0.7.1-1.2
We believe that the bug you reported is fixed in the latest version of
ipsec-tools, which is due to be installed in the Debian FTP archive:
ipsec-tools_0.7.1-1.2.diff.gz
to pool/main/i/ipsec-tools/ipsec-tools_0.7.1-1.2.diff.gz
ipsec-tools_0.7.1-1.2.dsc
to pool/main/i/ipsec-tools/ipsec-tools_0.7.1-1.2.dsc
ipsec-tools_0.7.1-1.2_amd64.deb
to pool/main/i/ipsec-tools/ipsec-tools_0.7.1-1.2_amd64.deb
racoon_0.7.1-1.2_amd64.deb
to pool/main/i/ipsec-tools/racoon_0.7.1-1.2_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 ipsec-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])
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Tue, 07 Oct 2008 14:22:25 +0200
Source: ipsec-tools
Binary: ipsec-tools racoon
Architecture: source amd64
Version: 1:0.7.1-1.2
Distribution: unstable
Urgency: high
Maintainer: Ganesan Rajagopal [EMAIL PROTECTED]
Changed-By: Nico Golde [EMAIL PROTECTED]
Description:
ipsec-tools - IPsec tools for Linux
racoon - IPsec IKE keying daemon
Closes: 501026
Changes:
ipsec-tools (1:0.7.1-1.2) unstable; urgency=high
.
* Non-maintainer upload by the Security Team.
* Apply upstream patch to remove orphaned phase 1 handles that were
initiated remotely if an invalid first exchange was received
which may lead to a denial of service attack
(CVE-2008-3652; Closes: #501026).
Checksums-Sha1:
c186dcc08816adac5ddfa287f17e569e75376994 1116 ipsec-tools_0.7.1-1.2.dsc
24fd05d0588abf864e892eaf68b70bdee9d0d6aa 48771 ipsec-tools_0.7.1-1.2.diff.gz
865338f7cb9cff0ea6adf048dadc41b711157aea
Bug#501420: marked as done (kfreebsd-7: FTBFS in lenny: Nonexistent build-dependency: libdb4.4-dev)
Your message dated Tue, 07 Oct 2008 13:02:06 + with message-id [EMAIL PROTECTED] and subject line Bug#501420: fixed in kfreebsd-7 7.0-7 has caused the Debian Bug report #501420, regarding kfreebsd-7: FTBFS in lenny: Nonexistent build-dependency: libdb4.4-dev 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.) -- 501420: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=501420 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: kfreebsd-7 Version: 7.0-5 Severity: serious User: [EMAIL PROTECTED] Usertags: qa-ftbfs-20081006 qa-ftbfs Justification: FTBFS on i386 Hi, During a rebuild of all packages in a lenny chroot, your package failed to build on i386. Relevant part: ** Using build dependencies supplied by package: Build-Depends: debhelper (= 4.1.0), bzip2, quilt, freebsd6-buildutils (= 6.2) [kfreebsd-i386 kfreebsd-amd64] | freebsd7-buildutils [kfreebsd-i386 kfreebsd-amd64], libdb4.4-dev | libdb-dev, flex-old | flex, libbsd-dev [kfreebsd-i386 kfreebsd-amd64], gcc-4.3 [kfreebsd-i386 kfreebsd-amd64], sharutils Checking for already installed source dependencies... debhelper: missing Using default version 7.0.15 bzip2: already installed (1.0.5-1) quilt: missing libdb4.4-dev: missing libdb-dev: missing flex-old: missing flex: missing sharutils: missing Checking for source dependency conflicts... Reading package lists... Building dependency tree... Reading state information... Package libdb4.4-dev is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source E: Package libdb4.4-dev has no installation candidate The full build log is available from: http://newpeople.debian.org/~lucas/logs/2008/10/06 It is possible that your package builds fine in sid, but you should make sure that your package also builds fine in lenny before the release. A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot containing a sid i386 environment. Internet was not accessible from the build systems. -- | Lucas Nussbaum | [EMAIL PROTECTED] http://www.lucas-nussbaum.net/ | | jabber: [EMAIL PROTECTED] GPG: 1024D/023B3F4F | ---End Message--- ---BeginMessage--- Source: kfreebsd-7 Source-Version: 7.0-7 We believe that the bug you reported is fixed in the latest version of kfreebsd-7, which is due to be installed in the Debian FTP archive: kfreebsd-7_7.0-7.diff.gz to pool/main/k/kfreebsd-7/kfreebsd-7_7.0-7.diff.gz kfreebsd-7_7.0-7.dsc to pool/main/k/kfreebsd-7/kfreebsd-7_7.0-7.dsc kfreebsd-source-7.0_7.0-7_all.deb to pool/main/k/kfreebsd-7/kfreebsd-source-7.0_7.0-7_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. Aurelien Jarno [EMAIL PROTECTED] (supplier of updated kfreebsd-7 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: Tue, 07 Oct 2008 14:23:26 +0200 Source: kfreebsd-7 Binary: kfreebsd-source-7.0 kfreebsd-headers-7.0-1 kfreebsd-image-7.0-1-amd64-generic ndiswrapper-modules-7.0-1-amd64-generic kfreebsd-image-7-amd64-generic kfreebsd-headers-7.0-1-amd64-generic kfreebsd-headers-7-amd64-generic kfreebsd-image-7.0-1-amd64-k8 ndiswrapper-modules-7.0-1-amd64-k8 kfreebsd-image-7-amd64-k8 kfreebsd-headers-7.0-1-amd64-k8 kfreebsd-headers-7-amd64-k8 kfreebsd-image-7.0-1-amd64-k8-smp ndiswrapper-modules-7.0-1-amd64-k8-smp kfreebsd-image-7-amd64-k8-smp kfreebsd-headers-7.0-1-amd64-k8-smp kfreebsd-headers-7-amd64-k8-smp kfreebsd-image-7.0-1-em64t-p4 ndiswrapper-modules-7.0-1-em64t-p4 kfreebsd-image-7-em64t-p4 kfreebsd-headers-7.0-1-em64t-p4 kfreebsd-headers-7-em64t-p4 kfreebsd-image-7.0-1-em64t-p4-smp ndiswrapper-modules-7.0-1-em64t-p4-smp kfreebsd-image-7-em64t-p4-smp kfreebsd-headers-7.0-1-em64t-p4-smp kfreebsd-headers-7-em64t-p4-smp kfreebsd-image-7.0-1-486 ndiswrapper-modules-7.0-1-486 kfreebsd-image-7-486 kfreebsd-headers-7.0-1-486 kfreebsd-headers-7-486
Bug#482140: Reproducible and playing machine available
Am Dienstag, den 07.10.2008, 09:53 +0200 schrieb Luca Capello: Some notes before starting: 1) IMHO this bug is Severity: important, it leaves GNOME in an not usable state (see attached log) It breaks the upgrade, not GNOME. It needs manual intervention. IMHO seeverity important is correct. I reproduced the error on three different installations: two plain etch on powerpc (where plain means Dekstop + Standard tasks, no more) and another etch on i386 which I installed on May and then left there, without never upgrading. All installations from an Etch installation media (CD/DVD)? One of the two powerpc installation is still in the error state, i.e. `apt-get dist-upgrade` produces an error. I can put it online and accessible via SSH only if you need it, it's a playing machine (the same used for bug #501367 [1]), thus you can do whatever you want. I would indeed like to take a look at it. IIRC [2] I still have the whole etch /etc folder, in case you want to analyze it. Not sure, if it is necessary. Maybe it will help. I'm now installing etch on a QEMU image to check *again* if I can reproduce this bug: the advantage of QEMU is that you've the -snapshot option, thus you can test it whatever times you need. I'll report back as soon as the installation has finished. Thanks. Please tell, if you can reproduce it with QEMU. Regards, Daniel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#501437: More detailed info
Jeremy Lunn wrote: On 08/10/2008, at 12:19 AM, Eugene V. Lyubimkin wrote: This is error, it seems you have not correctly unpacked the Debian sources. Debian package in archive cannot contain such errors. What commands did you use to unpack the Debian sources? I obtained the package with: $ apt-get source netatalk Hmm, might it be that the sources came from stable, while my system is made up of packages from lenny/sid? I'll try obtaining the sources from lenny. It's good idea, but problem shown above cannot be caused and from stable distribution too. May be, you have deleted 'debian/control' file by mistake? Can you reproduce all steps before building including log of 'apt-get source'? -- Eugene V. Lyubimkin aka JackYF signature.asc Description: OpenPGP digital signature
Processed: The license is in
Processing commands for [EMAIL PROTECTED]: tags 332782 +pending Bug#332782: release-notes: Where's the license? Tags were: etch-ignore 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#501117: timer-applet: old preset files from stable cause crashes
severity 501117 minor thanks On Mon, Oct 06, 2008 at 06:58:28PM +0100, Stefano Zacchiroli wrote: On Sat, Oct 04, 2008 at 11:38:31AM +0200, Philipp Kern wrote: [0] looks like a bug that could be found when updating from etch to [0] looks like a dangling reference, can you please expand it? Oops, of course: [0] https://bugs.launchpad.net/ubuntu/+source/timer-applet/+bug/235377 Further investigation of the source in Etch revealed that this version already does the move to the XML-based presets storage. So this problem will not affect upgrades from Etch to Lenny, just from pre-Etch versions to Lenny without running Etch's version in the meantime. This could still be fixed the way it was done in the Etch version, by moving the file away if it exists. But I am lowering the severity because it is not critical anymore. Sorry for the noise, but I just hadn't time to investigate before. Kind regards, Philipp Kern -- .''`. Philipp KernDebian Developer : :' : http://philkern.de Release Assistant `. `' xmpp:[EMAIL PROTECTED] Stable Release Manager `-finger pkern/[EMAIL PROTECTED] signature.asc Description: Digital signature
Processed: Re: Bug#501117: timer-applet: old preset files from stable cause crashes
Processing commands for [EMAIL PROTECTED]: severity 501117 minor Bug#501117: timer-applet: old preset files from stable cause crashes Severity set to `minor' from `serious' thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#499818: marked as done (gstreamer0.10_0.10.20.2-1(hppa/experimental): FTBFS: *** [install-data-local] Error 1)
Your message dated Tue, 07 Oct 2008 09:02:08 + with message-id [EMAIL PROTECTED] and subject line Bug#499818: fixed in gstreamer0.10 0.10.21-2 has caused the Debian Bug report #499818, regarding gstreamer0.10_0.10.20.2-1(hppa/experimental): FTBFS: *** [install-data-local] Error 1 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.) -- 499818: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=499818 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: gstreamer0.10 Version: 0.10.20.2-1 Severity: serious Hi, your package failed to build from source. | Automatic build of gstreamer0.10_0.10.20.2-1 on lofn by sbuild/hppa 98-farm | Build started at 20080922-0250 | ** | Checking available source versions... | Fetching source files... | Reading package lists... | Building dependency tree... | Need to get 3584kB of source archives. | Get:1 http://sinclair.farm.ftbfs.de experimental/main gstreamer0.10 0.10.20.2-1 (dsc) [1899B] | Get:2 http://sinclair.farm.ftbfs.de experimental/main gstreamer0.10 0.10.20.2-1 (tar) [3546kB] | Get:3 http://sinclair.farm.ftbfs.de experimental/main gstreamer0.10 0.10.20.2-1 (diff) [36.7kB] | Fetched 3584kB in 3s (1110kB/s) | Download complete and in download only mode | ** Using build dependencies supplied by package: | Build-Depends: debhelper (= 5), cdbs (= 0.4.20), autotools-dev, libxml2-dev (= 2.6.0), zlib1g-dev (= 1:1.1.4), libglib2.0-dev (= 2.12), pkg-config (= 0.11.0), libpopt-dev, bison (= 1.875), flex (= 2.5.34), check (= 0.9.3-2), dpkg-dev (= 1.14.13), lsb-release, perl-doc | Build-Depends-Indep: python (= 2.2), gtk-doc-tools (= 0.7), jade (= 1.2.1), transfig (= 3.2.3.c), docbook-utils (= 0.6.9), docbook-xml, docbook-xsl, xsltproc (= 1.0.21), ghostscript, xmlto, netpbm | Checking for already installed source dependencies... [...] | -- Installing ./html/gstreamer.devhelp | make[6]: *** [install-data-local] Error 1 | make[6]: Leaving directory `/build/buildd/gstreamer0.10-0.10.20.2/docs/gst' | make[5]: *** [install-am] Error 2 | make[5]: Leaving directory `/build/buildd/gstreamer0.10-0.10.20.2/docs/gst' | make[4]: *** [install] Error 2 | make[4]: Leaving directory `/build/buildd/gstreamer0.10-0.10.20.2/docs/gst' | make[3]: *** [install-recursive] Error 1 | make[3]: Leaving directory `/build/buildd/gstreamer0.10-0.10.20.2/docs' | make[2]: *** [install] Error 2 | make[2]: Leaving directory `/build/buildd/gstreamer0.10-0.10.20.2/docs' | make[1]: *** [install-recursive] Error 1 | make[1]: Leaving directory `/build/buildd/gstreamer0.10-0.10.20.2' | make: *** [common-install-impl] Error 2 | dpkg-buildpackage: failure: /usr/bin/fakeroot debian/rules binary-arch gave error exit status 2 | ** | Build finished at 20080922-0321 | FAILED [dpkg-buildpackage died] Full build log(s): http://experimental.ftbfs.de/build.php?ver=0.10.20.2-1pkg=gstreamer0.10arch=hppa Gruesse, -- Frank Lichtenheld [EMAIL PROTECTED] www: http://www.djpig.de/ ---End Message--- ---BeginMessage--- Source: gstreamer0.10 Source-Version: 0.10.21-2 We believe that the bug you reported is fixed in the latest version of gstreamer0.10, which is due to be installed in the Debian FTP archive: gstreamer-tools_0.10.21-2_i386.deb to pool/main/g/gstreamer0.10/gstreamer-tools_0.10.21-2_i386.deb gstreamer0.10-doc_0.10.21-2_all.deb to pool/main/g/gstreamer0.10/gstreamer0.10-doc_0.10.21-2_all.deb gstreamer0.10-tools_0.10.21-2_i386.deb to pool/main/g/gstreamer0.10/gstreamer0.10-tools_0.10.21-2_i386.deb gstreamer0.10_0.10.21-2.diff.gz to pool/main/g/gstreamer0.10/gstreamer0.10_0.10.21-2.diff.gz gstreamer0.10_0.10.21-2.dsc to pool/main/g/gstreamer0.10/gstreamer0.10_0.10.21-2.dsc libgstreamer0.10-0-dbg_0.10.21-2_i386.deb to pool/main/g/gstreamer0.10/libgstreamer0.10-0-dbg_0.10.21-2_i386.deb libgstreamer0.10-0_0.10.21-2_i386.deb to pool/main/g/gstreamer0.10/libgstreamer0.10-0_0.10.21-2_i386.deb libgstreamer0.10-dev_0.10.21-2_i386.deb to pool/main/g/gstreamer0.10/libgstreamer0.10-dev_0.10.21-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. Sebastian Dröge [EMAIL PROTECTED] (supplier of updated gstreamer0.10 package) (This message was generated automatically at their
Processed: bug 501028 is forwarded to http://www.openoffice.org/issues/show_bug.cgi?id=90701
Processing commands for [EMAIL PROTECTED]: forwarded 501028 http://www.openoffice.org/issues/show_bug.cgi?id=90701 Bug#501028: python-uno: Can't get types when using Python bindings Forwarded-to-address changed from [EMAIL PROTECTED] to http://www.openoffice.org/issues/show_bug.cgi?id=90701. 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#501306: update-grub fails with raid1 boot partition
Hi, (sorry for second mail - didn't send to bug) On Mon, Oct 06, 2008 at 07:18:08PM +0200, Felix Zielcke wrote: Am Montag, den 06.10.2008, 19:02 +0200 schrieb Felix Zielcke: If you do `grub-install /dev/sda' then it should be in your device.map. Either run grub-mkdevicemap --no-floppy or grub-install with `--recheck --no-floppy'. Urm I forgot somehow that you're talking about update-grub not grub-install. But somewhere /dev/sda has to come from which isn't visible on the report. Is your /dev/md0 over sda or something like that? Yes, md0 is over sda1 and sdb1: [EMAIL PROTECTED]:~$ cat /proc/mdstat Personalities : [raid1] md2 : active raid1 sdb3[1] sda3[0] 241207872 blocks [2/2] [UU] md1 : active (auto-read-only) raid1 sda2[0] sdb2[1] 1951808 blocks [2/2] [UU] md0 : active raid1 sda1[0] sdb1[1] 979840 blocks [2/2] [UU] During some previous upgrade, /boot/grub/device.map was regenerated, and it was missing some of the devices that made up the boot RAID array. Just in response to this - my problem has not been caused by an upgrade - it was a clean lenny install onto a new machine a few days ago. Thanks, Dan signature.asc Description: Digital signature
Bug#444312: Please investigate this crashes on amd64
Hi, This is really disapointing that this usefull application, is removed from Lenny. Is anybody out there with amd64 box and can debug this problem? -- Witold Baryluk MAIL: [EMAIL PROTECTED] JID: [EMAIL PROTECTED] signature.asc Description: Digital signature
Bug#501179: marked as done (mantis: CVE-2008-3102 doesn't set the secure flag for session cookies)
Your message dated Tue, 07 Oct 2008 11:47:03 + with message-id [EMAIL PROTECTED] and subject line Bug#501179: fixed in mantis 1.1.2+dfsg-5 has caused the Debian Bug report #501179, regarding mantis: CVE-2008-3102 doesn't set the secure flag for session cookies 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.) -- 501179: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=501179 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: mantis Severity: grave Tags: security patch Hi, the following CVE (Common Vulnerabilities Exposures) id was published for mantis. CVE-2008-3102[0]: | Mantis 1.1.x through 1.1.2 and 1.2.x through 1.2.0a2 does not set the | secure flag for the session cookie in an https session, which can | cause the cookie to be sent in http requests and make it easier for | remote attackers to capture this cookie. Upstream fix is on: http://mantisbt.svn.sourceforge.net/viewvc/mantisbt/trunk/mantisbt/core/session_api.php?r1=5458r2=5509view=patch 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-3102 http://security-tracker.debian.net/tracker/CVE-2008-3102 -- Nico Golde - http://www.ngolde.de - [EMAIL PROTECTED] - GPG: 0x73647CFF For security reasons, all text in this mail is double-rot13 encrypted. pgp3bduHVAg03.pgp Description: PGP signature ---End Message--- ---BeginMessage--- Source: mantis Source-Version: 1.1.2+dfsg-5 We believe that the bug you reported is fixed in the latest version of mantis, which is due to be installed in the Debian FTP archive: mantis_1.1.2+dfsg-5.diff.gz to pool/main/m/mantis/mantis_1.1.2+dfsg-5.diff.gz mantis_1.1.2+dfsg-5.dsc to pool/main/m/mantis/mantis_1.1.2+dfsg-5.dsc mantis_1.1.2+dfsg-5_all.deb to pool/main/m/mantis/mantis_1.1.2+dfsg-5_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. Patrick Schoenfeld [EMAIL PROTECTED] (supplier of updated mantis 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: Tue, 07 Oct 2008 11:23:55 +0200 Source: mantis Binary: mantis Architecture: source all Version: 1.1.2+dfsg-5 Distribution: unstable Urgency: high Maintainer: Patrick Schoenfeld [EMAIL PROTECTED] Changed-By: Patrick Schoenfeld [EMAIL PROTECTED] Description: mantis - web-based bug tracking system Closes: 501179 501425 Changes: mantis (1.1.2+dfsg-5) unstable; urgency=medium . * Urgency medium as it clears an rc bug * Properly remove configuration files and unregister them from ucf on purge (Closes: #501425) . mantis (1.1.2+dfsg-4) unstable; urgency=high . * Urgency high because it fixes a security issue * Added a patch for CVE2008-3102: Doesn't set the secure flag for session cookies (Closes: #501179) Checksums-Sha1: c9b13ffc4dbdb10789a1c6a75dd2652699eac316 1184 mantis_1.1.2+dfsg-5.dsc db2c27d1572acf6b5e9437199858d780257d6158 44308 mantis_1.1.2+dfsg-5.diff.gz ce03f4ffecc03d7defe5e0de0c9d2e6c673a2001 1856672 mantis_1.1.2+dfsg-5_all.deb Checksums-Sha256: 67110b37f2b563e347591c797d6a9e3b9eca66d2c7733c4f9037c315dafd1402 1184 mantis_1.1.2+dfsg-5.dsc c56d3bfa2ae9b0c38aaff9fb69b7f622a8131fe29004397f9d1408907345cee3 44308 mantis_1.1.2+dfsg-5.diff.gz d1f9df854f24cb4a66f3a5606e1a3c0b92ecdc5af15a748d2a1047e872032186 1856672 mantis_1.1.2+dfsg-5_all.deb Files: 3bc30cccee9879eb4c92c1eb213b5870 1184 web optional mantis_1.1.2+dfsg-5.dsc 2db2a40d2b044b89439b8bc0393d3aff 44308 web optional mantis_1.1.2+dfsg-5.diff.gz c1a055010ea777fc0cb21c39cb6c966e 1856672 web optional mantis_1.1.2+dfsg-5_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkjrSQgACgkQbdB4RPTVespwOQCfT0+d1+jYLufwHhLQb0aQTDuu 0dcAoIp1knpxU38sv0Cpny6VdHchYfl4 =CN4h -END PGP SIGNATURE- ---End Message---
Bug#501437: More detailed info
Jeremy Lunn wrote: On 07/10/2008, at 10:23 PM, Eugene V. Lyubimkin wrote: Can you provide entire build log? [snip] netatalk_2.0.3.orig.tar.gz dpkg-source: info: building netatalk in netatalk_2.0.3-4.diff.gz dpkg-source: warning: newly created empty file 'debian/control' will not be represented in diff dpkg-source: warning: missing information for output field Maintainer dpkg-source: warning: missing information for output field Architecture dpkg-source: warning: missing information for output field [snip] This is error, it seems you have not correctly unpacked the Debian sources. Debian package in archive cannot contain such errors. What commands did you use to unpack the Debian sources? -- Eugene V. Lyubimkin aka JackYF signature.asc Description: OpenPGP digital signature
Bug#501427: m-a changes the utsstring in include/linux/utsrelease.h if kernel is build with --append-to-version
Package: module-assistant Version: 0.10.8 Severity: critical If you build a custom kernel with m-a maybe with this command: make-kpkg --initrd --append-to-version -lustre-1.6.5.1 the file include/linux/utsrelease.h contains this definition: #define UTS_RELEASE 2.6.22-lustre-1.6.5.1 /*(for a 2.6.22er kernel)*/ After building one module with m-a against this kernel with this options: m-a -l 2.6.22-lustre-1.6.5.1 -t build lustre this string is resetted to the default 2.6.22. If you now want to build another module it fails with no kernel sources available Manually resetting this string back to the correct value fixes this problem. As this prevents to build another module to a self build kernel this is a major issue in my eyes, this is the reason I chose a RC critical severity for this bug. i've not tested if thie behaviour is already fixed in lenny or in sid, so maybe this could also affect lenny. Greetings Winnie -- System Information: Debian Release: 4.0 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.22-quota-enabled-lustre-1.6.5.1 Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Versions of packages module-assistant depends on: ii libtext-wrapi18n-perl 0.06-5 internationalized substitute of Te ii perl5.8.8-7etch3 Larry Wall's Practical Extraction Versions of packages module-assistant recommends: ii liblocale-gettext-perl1.05-1 Using libc functions for internati -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#391935: Bug #391935: Re: The answer from Citrix Xen.org
On 07-Oct-2008, Josselin Mouette wrote: Le mardi 07 octobre 2008 à 12:48 +1100, Ben Finney a écrit : Yes, we do need more detail; we need to know that *any* recipient of Debian can redistribute the work to anyone else, modified or unmodified, commercially or otherwise. (Or to know that these actions are not allowed, so that we can remove the package from Debian.) As for the modified or unmodified, I think we have already considered it acceptable to require a name change for significant modifications made by third-party distributors. For example, though I’m not sure, I think this is already the case for Apache. I don't know whether you're saying Debian itself would be exempt from such a requirement. The Debian project's license to freely redistribute works, modified or unmodified, must not be specific to Debian as per DFSG §8. The license to do so must extend to all “third-party distributors” when they get the work from Debian. If the work will be modified in Debian, and if that would require a name change under the trademark license, presumably we have another “Firefox” → “Iceweasel” situation and would have to rename the work ourselves in order to redistribute it in Debian. It all depends on what the license terms actually require, though, so hopefully we can get answers from upstream. I’ll ask for clarifications about the rest. Thanks. -- \ “Isn't it enough to see that a garden is beautiful without | `\ having to believe that there are fairies at the bottom of it | _o__) too?” —Douglas Adams | Ben Finney [EMAIL PROTECTED] signature.asc Description: Digital signature
Processed: ..
Processing commands for [EMAIL PROTECTED]: found 501294 1.1-1 Bug#501294: libncurses-ruby1.9: I can't require 'ncurses' Bug marked as found in version 1.1-1. severity 501294 grave Bug#501294: libncurses-ruby1.9: I can't require 'ncurses' Severity set to `grave' from `grave' End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#501411: libdanga-socket-perl: FTBFS in lenny: tests failed
Package: libdanga-socket-perl Version: 1.59-1 Severity: serious User: [EMAIL PROTECTED] Usertags: qa-ftbfs-20081006 qa-ftbfs Justification: FTBFS on i386 Hi, During a rebuild of all packages in a lenny chroot, your package failed to build on i386. Relevant part: make[1]: Entering directory `/build/user-libdanga-socket-perl_1.59-1-amd64-L3Dy1L/libdanga-socket-perl-1.59-1' PERL_DL_NONLAZY=1 /usr/bin/perl -MExtUtils::Command::MM -e test_harness(0, 'blib/lib', 'blib/arch') t/*.t t/00-use..ok t/05-postloop. # Failed test 'took less than 0 + 1 seconds' # at t/05-postloop.t line 43. # Failed test 'took less than 1 + 1 seconds' # at t/05-postloop.t line 43. # Failed test 'took less than 2 + 1 seconds' # at t/05-postloop.t line 43. # Failed test 'took less than 3 + 1 seconds' # at t/05-postloop.t line 43. # Failed test 'took less than 4 + 1 seconds' # at t/05-postloop.t line 43. # Failed test 'took less than 5 + 1 seconds' # at t/05-postloop.t line 43. # Looks like you failed 6 tests of 17. dubious Test returned status 6 (wstat 1536, 0x600) DIED. FAILED tests 5, 7, 9, 11, 13, 15 Failed 6/17 tests, 64.71% okay t/10-events...ok t/12-closeraceok Failed Test Stat Wstat Total Fail List of Failed --- t/05-postloop.t6 1536176 5 7 9 11 13 15 Failed 1/4 test scripts. 6/59 subtests failed. Files=4, Tests=59, 12 wallclock secs ( 0.30 cusr + 0.03 csys = 0.33 CPU) Failed 1/4 test programs. 6/59 subtests failed. make[1]: *** [test_dynamic] Error 255 The full build log is available from: http://newpeople.debian.org/~lucas/logs/2008/10/06 It is possible that your package builds fine in sid, but you should make sure that your package also builds fine in lenny before the release. A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot containing a sid i386 environment. Internet was not accessible from the build systems. -- | 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]
Processed: ..
Processing commands for [EMAIL PROTECTED]: found 501294 1.1-1 Bug#501294: libncurses-ruby1.9: I can't require 'ncurses' Bug marked as found in version 1.1-1 and reopened. 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#499070: dpkg leaves system in unusable state after running out of diskspace
Hey! On Tue, 2008-10-07 at 09:02:54 +0200, Raphael Hertzog wrote: On Thu, 18 Sep 2008, Guillem Jover wrote: The other is that when onerr_abort is signaled dpkg should not continue processing anything anymore, it should just do whatever cleanup is required and exit. But that can wait probably post-lenny. So this is the proper fix, and it should not be that big, probably less than 10 lines? Will cook something today or tomorrow... Any progress ? Yeah got the code the day after that mail, but I've not found the time to test it. I guess the easiest is to change one of the function return values to the output of rand() or similar and see from there. I'll try to get to it this week. And it ended up being a 7 lines patch, although I think I'll be changing part of that error recovery logic for squeeze. regards, guillem -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#501424: gcc-avr: FTBFS in lenny: patching fails (again)
Package: gcc-avr
Version: 1:4.3.0-4
Severity: serious
User: [EMAIL PROTECTED]
Usertags: qa-ftbfs-20081006 qa-ftbfs
Justification: FTBFS on i386
Hi,
During a rebuild of all packages in a lenny chroot, your package failed
to build on i386.
Relevant part:
/usr/bin/fakeroot debian/rules clean
/bin/bash: lsb_release: command not found
bash: debian/runcheck.sh: No such file or directory
rm -rf stamps
rm -rf gcc-4.3.2 p d
rm -rf bin
rm -rf /build/user-gcc-avr_4.3.0-4-amd64-YT5Mjt/gcc-avr-4.3.0-4/src
dh_testdir
dh_testroot
rm -f build-stamp configure-stamp patch-stamp
# Add here commands to clean up after the build process.
#-/usr/bin/make clean
#rm -rf /usr/src/gcc-4.3/ objdir
rm -rf objdir
dh_clean
rm -f debian/gcc-avr.substvars
rm -f debian/gcc-avr.*.debhelper
rm -f debian/gcc-avr.debhelper.log
rm -rf debian/gcc-avr/
rm -f debian/files
find . \( \( -type f -a \
\( -name '#*#' -o -name '.*~' -o -name '*~' -o -name DEADJOE \
-o -name '*.orig' -o -name '*.rej' -o -name '*.bak' \
-o -name '.*.orig' -o -name .*.rej -o -name '.SUMS' \
-o -name TAGS -o \( -path '*/.deps/*' -a -name '*.P' \) \
\) -exec rm -f {} \; \) -o \
\( -type d -a -name autom4te.cache -prune -exec rm -rf {} \; \)
\)
dpkg-source -b gcc-avr-4.3.0-4
dpkg-source: warning: source directory 'gcc-avr-4.3.0-4' is not
sourcepackage-upstreamversion 'gcc-avr-4.3.0'
dpkg-source: info: using source format `1.0'
dpkg-source: info: building gcc-avr in gcc-avr_4.3.0-4.tar.gz
dpkg-source: info: building gcc-avr in gcc-avr_4.3.0-4.dsc
debian/rules build
/bin/bash: lsb_release: command not found
bash: debian/runcheck.sh: No such file or directory
: # unpack gcc tarball
mkdir stamps
if [ -d /build/user-gcc-avr_4.3.0-4-amd64-YT5Mjt/gcc-avr-4.3.0-4/src ]; then \
echo 2 Source directory
/build/user-gcc-avr_4.3.0-4-amd64-YT5Mjt/gcc-avr-4.3.0-4/src exists. Delete
by hand; \
false; \
fi
rm -rf gcc-4.3.2
case gcc-4.3.2-dfsg.tar.lzma in \
*.bz2) tar -x --bzip2 -f /usr/src/gcc-4.3/gcc-4.3.2-dfsg.tar.lzma;; \
*.gz) tar -x --gzip -f /usr/src/gcc-4.3/gcc-4.3.2-dfsg.tar.lzma;; \
*.lzma) lzcat /usr/src/gcc-4.3/gcc-4.3.2-dfsg.tar.lzma | tar -x -f
-;; \
*) false; \
esac
mv gcc-4.3.2 /build/user-gcc-avr_4.3.0-4-amd64-YT5Mjt/gcc-avr-4.3.0-4/src
rm -f /build/user-gcc-avr_4.3.0-4-amd64-YT5Mjt/gcc-avr-4.3.0-4/src/gcc/doc/*.1
rm -f
/build/user-gcc-avr_4.3.0-4-amd64-YT5Mjt/gcc-avr-4.3.0-4/src/gcc/doc/fsf-funding.7
rm -f
/build/user-gcc-avr_4.3.0-4-amd64-YT5Mjt/gcc-avr-4.3.0-4/src/gcc/doc/*.info
rm -f
/build/user-gcc-avr_4.3.0-4-amd64-YT5Mjt/gcc-avr-4.3.0-4/src/gcc/fortran/*.info
rm -f
/build/user-gcc-avr_4.3.0-4-amd64-YT5Mjt/gcc-avr-4.3.0-4/src/libgomp/*.info
rm -f
/build/user-gcc-avr_4.3.0-4-amd64-YT5Mjt/gcc-avr-4.3.0-4/src/gcc/java/*.1
rm -f
/build/user-gcc-avr_4.3.0-4-amd64-YT5Mjt/gcc-avr-4.3.0-4/src/gcc/java/*.info
for i in gcc/doc/arm-neon-intrinsics.texi gcc/doc/bugreport.texi
gcc/doc/cfg.texi gcc/doc/collect2.texi gcc/doc/compat.texi
gcc/doc/configfiles.texi gcc/doc/configterms.texi gcc/doc/contrib.texi
gcc/doc/contribute.texi gcc/doc/cppenv.texi gcc/doc/cppinternals.texi
gcc/doc/cppopts.texi gcc/doc/cpp.texi gcc/doc/c-tree.texi gcc/doc/extend.texi
gcc/doc/fragments.texi gcc/doc/frontends.texi gcc/doc/gccint.texi
gcc/doc/gcc.texi gcc/doc/gcov.texi gcc/doc/gnu.texi gcc/doc/gty.texi
gcc/doc/headerdirs.texi gcc/doc/hostconfig.texi gcc/doc/implement-c.texi
gcc/doc/install-old.texi gcc/doc/install.texi gcc/doc/interface.texi
gcc/doc/invoke.texi gcc/doc/languages.texi gcc/doc/libgcc.texi
gcc/doc/loop.texi gcc/doc/makefile.texi gcc/doc/md.texi gcc/doc/objc.texi
gcc/doc/options.texi gcc/doc/passes.texi gcc/doc/portability.texi
gcc/doc/rtl.texi gcc/doc/service.texi gcc/doc/sourcebuild.texi
gcc/doc/standards.texi gcc/doc/tm.texi gcc/doc/tree-ssa.texi
gcc/doc/trouble.texi gcc/doc/include/gcc-common.texi
gcc/doc/include/funding.texi gcc/fortran/gfc-internals.texi
gcc/fortran/invoke.texi gcc/fortran/intrinsic.texi ; do \
if [ -f
/build/user-gcc-avr_4.3.0-4-amd64-YT5Mjt/gcc-avr-4.3.0-4/src/$i ]; then \
cp /usr/src/gcc-4.3/debian/dummy.texi
/build/user-gcc-avr_4.3.0-4-amd64-YT5Mjt/gcc-avr-4.3.0-4/src/$i; \
else \
echo 2 $i does not exist, fix debian/rules.unpack; \
fi; \
done
for i in gcc/doc/gcc.texi gcc/java/gcj.texi gcc/ada/gnat-style.texi
gcc/ada/gnat_rm.texi gcc/ada/gnat_ugn.texi gcc/fortran/gfortran.texi
gcc/treelang/treelang.texi libgomp/libgomp.texi ; do \
n=$(basename $i .texi); \
if [ -f
/build/user-gcc-avr_4.3.0-4-amd64-YT5Mjt/gcc-avr-4.3.0-4/src/$i ]; then \
sed s/@name@/$n/g /usr/src/gcc-4.3/debian/gcc-dummy.texi \
Bug#501420: kfreebsd-7: FTBFS in lenny: Nonexistent build-dependency: libdb4.4-dev
Package: kfreebsd-7 Version: 7.0-5 Severity: serious User: [EMAIL PROTECTED] Usertags: qa-ftbfs-20081006 qa-ftbfs Justification: FTBFS on i386 Hi, During a rebuild of all packages in a lenny chroot, your package failed to build on i386. Relevant part: ** Using build dependencies supplied by package: Build-Depends: debhelper (= 4.1.0), bzip2, quilt, freebsd6-buildutils (= 6.2) [kfreebsd-i386 kfreebsd-amd64] | freebsd7-buildutils [kfreebsd-i386 kfreebsd-amd64], libdb4.4-dev | libdb-dev, flex-old | flex, libbsd-dev [kfreebsd-i386 kfreebsd-amd64], gcc-4.3 [kfreebsd-i386 kfreebsd-amd64], sharutils Checking for already installed source dependencies... debhelper: missing Using default version 7.0.15 bzip2: already installed (1.0.5-1) quilt: missing libdb4.4-dev: missing libdb-dev: missing flex-old: missing flex: missing sharutils: missing Checking for source dependency conflicts... Reading package lists... Building dependency tree... Reading state information... Package libdb4.4-dev is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source E: Package libdb4.4-dev has no installation candidate The full build log is available from: http://newpeople.debian.org/~lucas/logs/2008/10/06 It is possible that your package builds fine in sid, but you should make sure that your package also builds fine in lenny before the release. A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot containing a sid i386 environment. Internet was not accessible from the build systems. -- | 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#501028: python-uno bindings break with OO.o 3.0 and system python
[This is a follow-up to a mail by Rene Engelhard which got caught in the [EMAIL PROTECTED] moderation queue. See http://bugs.debian.org/501028 ] The OpenOffice.org program/python script sets URE_BOOTSTRAP which contains the location of fundamentalrc. In turn, fundamentalrc sets the location of the offapi.rdb file, which contains information about the types used by the python uno bindings. In short, when --with-system-python is used with OO.o 3.0, these variables don't get set, so we see the types breakage described in the Debian bug report. One workaround is to export an appropriate URE_BOOTSTRAP variable before running python. The alternative is to check for and set this variable in uno.py, which will cover most use cases transparently - I'm halfway through writing this patch. -- Tim Retout [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#497676: Bug#396291: Bug#356055: loadlin: loadlin.exe cannot be built from source
Hello, Resending without the patch as it seems some mail servers don't like 160KB patches. Samuel Thibault, le Tue 07 Oct 2008 11:06:23 +0200, a écrit : Peter commited upstream my yasm patch to support tasm syntax for loadlin, here is a backport to the debian package (just a few minor changes). The patch is quite big, but as noted in the changelog, it just adds extensions that are enabled only when tasm compatible mode is requested. Patch available on http://bugs.debian.org/cgi-bin/bugreport.cgi?msg=56;filename=patch;att=1;bug=396291 Samuel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#500826: zabbix: Upgrade to Zabbix 1.6 does not work out-of-the-box, SQL upgrade scripts are not included in package?
hi Bas, On Tue, Oct 07, 2008 at 01:58:17PM +0200, Bas van Schaik wrote: I didn't get any dbconfig-common question at all. Maybe it is important to note that my MySQL server is actually running on another server? Anyhow, I think it would be best to also include the SQL-scripts like supplied by upstream, wouldn't it? this should make any difference. dbconfig-common can handle databases on remote machines too. So i guess its your debconf setting which ignored these kind of questions then (we had this several times in the past). The Upgrade scripts come with the package, are installed to: ./usr/share/dbconfig-common/data/zabbix-server-mysql/upgrade/mysql/1:1.6 can you confirm i can close this bug? bye, - michael -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#501409: marked as done (tzsetup: FTBFS in lenny: /usr/share/iso-codes/iso_3166.tab: No such file or directory at ./gen-templates)
Your message dated Tue, 7 Oct 2008 16:51:28 +0200 with message-id [EMAIL PROTECTED] and subject line Re: Bug#501409: tzsetup: FTBFS in lenny: /usr/share/iso-codes/iso_3166.tab: No such file or directory at ./gen-templates has caused the Debian Bug report #501409, regarding tzsetup: FTBFS in lenny: /usr/share/iso-codes/iso_3166.tab: No such file or directory at ./gen-templates 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.) -- 501409: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=501409 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: tzsetup Version: 1:0.21 Severity: serious User: [EMAIL PROTECTED] Usertags: qa-ftbfs-20081006 qa-ftbfs Justification: FTBFS on i386 Hi, During a rebuild of all packages in a lenny chroot, your package failed to build on i386. Relevant part: make[1]: Entering directory `/build/user-tzsetup_0.21-amd64-eOIR8m/tzsetup-0.21' rm -f tzmap make[1]: Leaving directory `/build/user-tzsetup_0.21-amd64-eOIR8m/tzsetup-0.21' dh_clean dpkg-source -b tzsetup-0.21 dpkg-source: info: using source format `1.0' dpkg-source: info: building tzsetup in tzsetup_0.21.tar.gz dpkg-source: warning: missing information for output field Standards-Version dpkg-source: info: building tzsetup in tzsetup_0.21.dsc debian/rules build /usr/bin/make make[1]: Entering directory `/build/user-tzsetup_0.21-amd64-eOIR8m/tzsetup-0.21' ./gen-templates debian/common.templates.in debian/common.templates /usr/share/iso-codes/iso_3166.tab: No such file or directory at ./gen-templates line 13. make[1]: *** [tzmap] Error 2 The full build log is available from: http://newpeople.debian.org/~lucas/logs/2008/10/06 It is possible that your package builds fine in sid, but you should make sure that your package also builds fine in lenny before the release. A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot containing a sid i386 environment. Internet was not accessible from the build systems. -- | Lucas Nussbaum | [EMAIL PROTECTED] http://www.lucas-nussbaum.net/ | | jabber: [EMAIL PROTECTED] GPG: 1024D/023B3F4F | ---End Message--- ---BeginMessage--- Version: 1:0.23 ---End Message---
Bug#501026: intent to NMU
Hi,
I intent to upload an NMU for this.
debdiff attached and archived on:
http://people.debian.org/~nion/nmu-diff/ipsec-tools-0.7.1-1.1_0.7.1-1.2.patch
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 ipsec-tools-0.7.1/debian/changelog ipsec-tools-0.7.1/debian/changelog
--- ipsec-tools-0.7.1/debian/changelog
+++ ipsec-tools-0.7.1/debian/changelog
@@ -1,3 +1,13 @@
+ipsec-tools (1:0.7.1-1.2) unstable; urgency=high
+
+ * Non-maintainer upload by the Security Team.
+ * Apply upstream patch to remove orphaned phase 1 handles that were
+initiated remotely if an invalid first exchange was received
+which may lead to a denial of service attack
+(CVE-2008-3652; Closes: #501026).
+
+ -- Nico Golde [EMAIL PROTECTED] Tue, 07 Oct 2008 14:22:25 +0200
+
ipsec-tools (1:0.7.1-1.1) unstable; urgency=low
* Non-maintainer upload.
only in patch2:
unchanged:
--- ipsec-tools-0.7.1.orig/src/racoon/isakmp.c
+++ ipsec-tools-0.7.1/src/racoon/isakmp.c
@@ -798,20 +798,24 @@
[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
pgpUF4qHtIzkJ.pgp
Description: PGP signature
Bug#391935: Bug #391935: Re: The answer from Citrix Xen.org
Le mardi 07 octobre 2008 à 19:58 +1100, Ben Finney a écrit : As for the modified or unmodified, I think we have already considered it acceptable to require a name change for significant modifications made by third-party distributors. For example, though I’m not sure, I think this is already the case for Apache. I don't know whether you're saying Debian itself would be exempt from such a requirement. The Debian project's license to freely redistribute works, modified or unmodified, must not be specific to Debian as per DFSG §8. The license to do so must extend to all “third-party distributors” when they get the work from Debian. AIUI, the final trademark license will be something along the lines of you can keep the name as long as the packages pass our compatibility test. This is certainly not something specific to Debian. Yes, this means we need to change the name if incompatible modifications are made, but this does not break the DFSG since we are still free to change the name for more important modifications. Currently we are in a more blurry situation, since the compatibility test has not been written yet. 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#494202: Installation script overwrites existing sympa.conf
severity 494202 important thanks Ari Epstein wrote: Package: sympa Version: 5.2.3-1.2+etch1 Severity: serious Justification: Policy 10.7.3 Upgrading to latest stable sympa package has overwritten my sympa.conf (and maybe other files as well). 10.7.3 indicates upgrade should not alter local changes and configuration files must be preserved. As I understand it, maintainer scripts are allowed to change configuration files (not conf files) as long as local changes are preserved. Please supply details if you think that local changes have been ignored by the upgrade. 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#501423: gossip: FTBFS in lenny: Unsatisfiable build-dependency: libloudmouth1-dev(inst 1.4.0-1 ! = wanted 1.4.1)
Am Dienstag, den 07.10.2008, 10:46 +0200 schrieb Lucas Nussbaum: During a rebuild of all packages in a lenny chroot, your package failed to build on i386. I have no idea why gossip 1:0.31-1 was approved to testing without talking to me. Norbert -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#484305: Fix python or the apps?
Hi there, It seems to me that there are two choices here: 1) this is considered a python issue, that should be solved in python; 2) this is considered an issue in the python apps that act like this (and as it was said, there's probably a handfull of them), and those should be solved in each of those apps. Shouldn't we ask it to the Python Apps Packaging Team [1]? [1] http://wiki.debian.org/Teams/PythonAppsPackagingTeam Best regards, -- Marcos Marado -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#496954: bind9: 496954: more info needed
On Mon, Oct 06, 2008 at 11:49:19PM -0400, Maykel Moya wrote: I had to revert the patch after being unable to issue recursive queries to bind. My IP is inside and ACL so it's sure bind wasn't obeying acl settings. Does bind crash if you remove the ACL? Are you able to narrow down which part of the ACL causes crashes? -- bye, pabs http://wiki.debian.org/PaulWise -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#501409: tzsetup: FTBFS in lenny: /usr/share/iso-codes/iso_3166.tab: No such file or directory at ./gen-templates
Package: tzsetup Version: 1:0.21 Severity: serious User: [EMAIL PROTECTED] Usertags: qa-ftbfs-20081006 qa-ftbfs Justification: FTBFS on i386 Hi, During a rebuild of all packages in a lenny chroot, your package failed to build on i386. Relevant part: make[1]: Entering directory `/build/user-tzsetup_0.21-amd64-eOIR8m/tzsetup-0.21' rm -f tzmap make[1]: Leaving directory `/build/user-tzsetup_0.21-amd64-eOIR8m/tzsetup-0.21' dh_clean dpkg-source -b tzsetup-0.21 dpkg-source: info: using source format `1.0' dpkg-source: info: building tzsetup in tzsetup_0.21.tar.gz dpkg-source: warning: missing information for output field Standards-Version dpkg-source: info: building tzsetup in tzsetup_0.21.dsc debian/rules build /usr/bin/make make[1]: Entering directory `/build/user-tzsetup_0.21-amd64-eOIR8m/tzsetup-0.21' ./gen-templates debian/common.templates.in debian/common.templates /usr/share/iso-codes/iso_3166.tab: No such file or directory at ./gen-templates line 13. make[1]: *** [tzmap] Error 2 The full build log is available from: http://newpeople.debian.org/~lucas/logs/2008/10/06 It is possible that your package builds fine in sid, but you should make sure that your package also builds fine in lenny before the release. A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot containing a sid i386 environment. Internet was not accessible from the build systems. -- | 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#499538: marked as done (jh_makepkg needs dch but javahelper don't depend on devscripts)
Your message dated Tue, 7 Oct 2008 09:57:18 +0100 with message-id [EMAIL PROTECTED] and subject line Whoops, mangled the closes has caused the Debian Bug report #499538, regarding jh_makepkg needs dch but javahelper don't depend on devscripts 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.) -- 499538: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=499538 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: javahelper Version: 0.14 Severity: normal --- Please enter the report below this line. --- jh_makepkg (0.5) needs dch but javahelper don't depend on devscripts If one tries to run jh_makepkg without dch installed one gets the error: /usr/bin/jh_makepkg: line 331: dch: command not found ---End Message--- ---BeginMessage--- Fixed: 0.15 Closed, but forgot the :, so didn't get closed here. Closing now. Matt -- Matthew Johnson signature.asc Description: Digital signature ---End Message---
Bug#501241: [Pkg-db-devel] Bug#501241: libdb4.6-dev: upgrade failure (unpack)
Clint Adams [EMAIL PROTECTED] - Tue, 7 Oct 2008 08:25:32 + On Sun, Oct 05, 2008 at 11:04:15PM +0200, Michel Briand wrote: upgrading today (standard aptitude upgrade). Something went wrong (log pasted below). Yes, if you try running it again, it will probably go smoothly. Yes, next upgrade has run smoothly. One question: I installed libdb and libdb-dev via aptitude. I noted that many packages libdb* where installed since that first manual installation. I wonder why there is all theses packages... ??? There is work going on to reduce the number. Thank you. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#501426: glide: FTBFS in lenny: dpkg-shlibdeps: failure: couldn't find library libglide.so.2 needed by debian/glide2-bin/usr/lib/glide2/bin/test05 (its RPATH is '')
Package: glide Version: 2002.04.10-16 Severity: serious User: [EMAIL PROTECTED] Usertags: qa-ftbfs-20081006 qa-ftbfs Justification: FTBFS on i386 Hi, During a rebuild of all packages in a lenny chroot, your package failed to build on i386. This is similar to #453790. However, I'm confused by the discussion in that bug, so I'm opening a new one. I also reproduced the bug outside of sbuild, using apt-get build-dep in a clean lenny chroot. Relevant part: make[1]: Entering directory `/build/user-glide_2002.04.10-16-amd64-1ltOzD/glide-2002.04.10-16' dh_testdir dh_testroot dh_clean -k dh_installdirs install -m 755 build-tree/glide2x/h3/glide/tests/test[0-9][0-9] \ /build/user-glide_2002.04.10-16-amd64-1ltOzD/glide-2002.04.10-16/debian/glide2-bin/usr/lib/glide2/bin/ install -m 755 build-tree/glide2x/cvg/bin/pass \ /build/user-glide_2002.04.10-16-amd64-1ltOzD/glide-2002.04.10-16/debian/glide2-bin/usr/lib/glide2/bin/ dh_strip dh_installdocs dh_installchangelogs dh_link dh_compress dh_fixperms dh_installdeb # XXX: We use build-tree instead of /build/user-glide_2002.04.10-16-amd64-1ltOzD/glide-2002.04.10-16/debian/libglide2 because we do not # ship in the .deb the symlink to the hardware specific library. dh_shlibdeps -Llibglide2 -lbuild-tree/glide2x/h3/lib dpkg-shlibdeps: failure: couldn't find library libglide.so.2 needed by debian/glide2-bin/usr/lib/glide2/bin/test05 (its RPATH is ''). Note: libraries are not searched in other binary packages that do not have any shlibs or symbols file. To help dpkg-shlibdeps find private libraries, you might need to set LD_LIBRARY_PATH. dh_shlibdeps: command returned error code 512 make[1]: *** [binary-glide2-bin-real] Error 1 The full build log is available from: http://newpeople.debian.org/~lucas/logs/2008/10/06 It is possible that your package builds fine in sid, but you should make sure that your package also builds fine in lenny before the release. A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot containing a sid i386 environment. Internet was not accessible from the build systems. -- | 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#501028: [udk-dev] python-uno bindings break with OO.o 3.0 and system python
On Tue, 2008-10-07 at 15:13 +0200, Stephan Bergmann wrote: Also see http://www.openoffice.org/issues/show_bug.cgi?id=90701. Thanks, that'll save me some time. :) -- Tim Retout [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#501437: More detailed info
On 07/10/2008, at 10:23 PM, Eugene V. Lyubimkin wrote: Can you provide entire build log? [EMAIL PROTECTED]:~/netatalk-2.0.3$ DEB_BUILD_OPTIONS=ssl debuild dpkg-buildpackage -rfakeroot -D -us -uc dpkg-buildpackage: set CFLAGS to default value: -g -O2 dpkg-buildpackage: set CPPFLAGS to default value: dpkg-buildpackage: set LDFLAGS to default value: dpkg-buildpackage: set FFLAGS to default value: -g -O2 dpkg-buildpackage: set CXXFLAGS to default value: -g -O2 dpkg-buildpackage: source package netatalk dpkg-buildpackage: source version 2.0.3-4 dpkg-buildpackage: source changed by Sebastian Rittau [EMAIL PROTECTED] dpkg-buildpackage: host architecture i386 fakeroot debian/rules clean test -x debian/rules dh_testroot /usr/bin/make -f debian/rules reverse-config make[1]: Entering directory `/home/jeremy/netatalk-2.0.3' for i in ./config.guess ./config.sub ; do \ if test -e $i.cdbs-orig ; then \ mv $i.cdbs-orig $i ; \ fi ; \ done make[1]: Leaving directory `/home/jeremy/netatalk-2.0.3' if [ reverse-patches = reverse-patches ]; then rm -f debian/stamp- patched; fi patches: debian/patches/200_netatalk_conf_defaults.diff debian/patches/ 201_etc2ps_paths.diff debian/patches/202_psf_8_paths.diff debian/ patches/204_uniconv_namespace_conflict.diff debian/patches/ 205_applevolumes_default_homedir.diff debian/patches/ 206_fix_cnid_maint_paths.diff debian/patches/ 207_afile_namespace_conflict.diff Patch debian/patches/207_afile_namespace_conflict.diff is not applied. Patch debian/patches/206_fix_cnid_maint_paths.diff is not applied. Patch debian/patches/205_applevolumes_default_homedir.diff is not applied. Patch debian/patches/204_uniconv_namespace_conflict.diff is not applied. Patch debian/patches/202_psf_8_paths.diff is not applied. Patch debian/patches/201_etc2ps_paths.diff is not applied. Patch debian/patches/200_netatalk_conf_defaults.diff is not applied. if [ reverse-patches != reverse-patches ]; then touch debian/stamp- patched; fi if [ reverse-patches != reverse-patches ] ; then \ /usr/bin/make -f debian/rules update-config ; \ fi for dir in debian/patches ; do \ rm -f $dir/*.log ; \ done for i in ./config.guess ./config.sub ; do \ if test -e $i.cdbs-orig ; then \ mv $i.cdbs-orig $i ; \ fi ; \ done dh_clean /usr/bin/make -C . -k distclean make[1]: Entering directory `/home/jeremy/netatalk-2.0.3' make[1]: *** No rule to make target `distclean'. make[1]: Leaving directory `/home/jeremy/netatalk-2.0.3' make: [makefile-clean] Error 2 (ignored) rm -f debian/stamp-makefile-build rm -f debian/stamp-autotools-files dpkg-source -b netatalk-2.0.3 dpkg-source: info: using source format `1.0' dpkg-source: info: building netatalk using existing netatalk_2.0.3.orig.tar.gz dpkg-source: info: building netatalk in netatalk_2.0.3-4.diff.gz dpkg-source: warning: newly created empty file 'debian/control' will not be represented in diff dpkg-source: warning: missing information for output field Maintainer dpkg-source: warning: missing information for output field Architecture dpkg-source: warning: missing information for output field Standards- Version dpkg-source: info: building netatalk in netatalk_2.0.3-4.dsc debian/rules build make: Nothing to be done for `build'. fakeroot debian/rules binary make: Nothing to be done for `binary'. dpkg-genchanges ../netatalk_2.0.3-4_i386.changes dpkg-genchanges: failure: cannot read files list file: No such file or directory dpkg-buildpackage: failure: dpkg-genchanges gave error exit status 2 debuild: fatal error at line 1319: dpkg-buildpackage -rfakeroot -D -us -uc failed -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: severity of 470846 is important
Processing commands for [EMAIL PROTECTED]: severity 470846 important Bug#470846: crashes and hangs Apache Severity set to `important' from `grave' End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: fixed 499538 in 0.15
Processing commands for [EMAIL PROTECTED]: fixed 499538 0.15 Bug#499538: jh_makepkg needs dch but javahelper don't depend on devscripts Bug marked as fixed in version 0.15. 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: Re: Bug#501425: Leaves files after purge
Processing commands for [EMAIL PROTECTED]: Severity 501425 serious Bug#501425: Leaves files after purge Severity set to `serious' from `normal' Tags 501425 pending Bug#501425: Leaves files after purge There were no tags set. 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#501437: netatalk: SSL build fails: dpkg-genchanges cannot read files list file
Package: netatalk Version: 2.0.3-11 Severity: serious Justification: no longer builds from source Following instructions from README.Debian on building with SSL support appears to fail at the moment: [EMAIL PROTECTED]:~/netatalk-2.0.3$ DEB_BUILD_OPTIONS=ssl debuild dpkg-genchanges ../netatalk_2.0.3-4_i386.changes dpkg-genchanges: failure: cannot read files list file: No such file or directory dpkg-buildpackage: failure: dpkg-genchanges gave error exit status 2 debuild: fatal error at line 1319: dpkg-buildpackage -rfakeroot -D -us -uc failed -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.18-4-686 (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/bash Versions of packages netatalk depends on: ii libc6 2.7-13 GNU C Library: Shared libraries ii libcomerr21.41.0-3 common error description library ii libcups2 1.3.8-1lenny1 Common UNIX Printing System(tm) - ii libdb4.6 4.6.21-11 Berkeley v4.6 Database Libraries [ ii libgnutls26 2.4.1-1the GNU TLS library - runtime libr ii libkrb53 1.6.dfsg.4~beta1-4 MIT Kerberos runtime libraries ii libpam-modules1.0.1-4Pluggable Authentication Modules f ii libpam0g 1.0.1-4Pluggable Authentication Modules l ii libwrap0 7.6.q-16 Wietse Venema's TCP wrappers libra ii netbase 4.34 Basic TCP/IP networking system ii perl 5.10.0-14 Larry Wall's Practical Extraction ii zlib1g1:1.2.3.3.dfsg-12 compression library - runtime Versions of packages netatalk recommends: ii db4.2-util 4.2.52+dfsg-5 Berkeley v4.2 Database Utilities ii lsof 4.78.dfsg.1-4 List open files ii procps 1:3.2.7-8 /proc file system utilities ii rc 1.7.1-3 an implementation of the ATT Plan Versions of packages netatalk suggests: pn quota none (no description available) pn tetex-bin none (no description available) pn timeout none (no description available) -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#501422: qmtest: FTBFS in lenny: Nonexistent build-dependency: python-happydoc
Package: qmtest Version: 2.4-3 Severity: serious User: [EMAIL PROTECTED] Usertags: qa-ftbfs-20081006 qa-ftbfs Justification: FTBFS on i386 Hi, During a rebuild of all packages in a lenny chroot, your package failed to build on i386. Relevant part: ** Using build dependencies supplied by package: Build-Depends: debhelper (= 5.0.37.1), docbook-dsssl, docbook-xml, jadetex, python-all-dev (= 2.4), python-central (= 0.6), python-extclass (= 1.2.0zope-2.5.1-1.3), python-happydoc, sgml-data, tidy Checking for already installed source dependencies... W: Unable to locate package python-happydoc debhelper: missing Using default version 7.0.15 docbook-dsssl: missing docbook-xml: missing jadetex: missing python-all-dev: missing Using default version 2.5.2-2 python-central: missing Using default version 0.6.8 python-extclass: missing Using default version 1.2.0zope-2.5.1-6 python-happydoc: missing sgml-data: missing tidy: missing Checking for source dependency conflicts... Reading package lists... Building dependency tree... Reading state information... E: Couldn't find package python-happydoc The full build log is available from: http://newpeople.debian.org/~lucas/logs/2008/10/06 It is possible that your package builds fine in sid, but you should make sure that your package also builds fine in lenny before the release. A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot containing a sid i386 environment. Internet was not accessible from the build systems. -- | 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#501425: marked as done (Leaves files after purge)
Your message dated Tue, 07 Oct 2008 11:47:03 + with message-id [EMAIL PROTECTED] and subject line Bug#501425: fixed in mantis 1.1.2+dfsg-5 has caused the Debian Bug report #501425, regarding Leaves files after purge 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.) -- 501425: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=501425 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: mantis Version: 1.1.2+dfsg-3 Severity: normal Hi I just did install mantis and then purge it and following files were left on my system: /etc/mantis /etc/mantis/custom_strings_inc.php /usr/share/mantis /usr/share/mantis/www /usr/share/mantis/www/custom_strings_inc.php Purging package should remove these files. -- Michal Čihař | http://cihar.com | http://blog.cihar.com -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.26-1-vserver-amd64 (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/dash Versions of packages mantis depends on: ii dbconfig-common 1.8.40 common framework for packaging dat ii debconf 1.5.23 Debian configuration management sy ii libphp-adodb 5.05-1 The ADOdb database abstraction lay ii libphp-phpmailer 2.1-1 full featured email transfer class ii lighttpd [httpd] 1.4.19-5 A fast webserver with minimal memo ii php5-cli 5.2.6-5command-line interpreter for the p ii ucf 3.0010 Update Configuration File: preserv Versions of packages mantis recommends: ii mysql-client-5.0 [mysql-clien 5.0.51a-15 MySQL database client binaries ii php5-mysql5.2.6-5MySQL module for php5 Versions of packages mantis suggests: ii mysql-server 5.0.51a-15 MySQL database server (metapackage ii mysql-server-5.0 [mysql-serve 5.0.51a-15 MySQL database server binaries ii php5-cli 5.2.6-5command-line interpreter for the p ---End Message--- ---BeginMessage--- Source: mantis Source-Version: 1.1.2+dfsg-5 We believe that the bug you reported is fixed in the latest version of mantis, which is due to be installed in the Debian FTP archive: mantis_1.1.2+dfsg-5.diff.gz to pool/main/m/mantis/mantis_1.1.2+dfsg-5.diff.gz mantis_1.1.2+dfsg-5.dsc to pool/main/m/mantis/mantis_1.1.2+dfsg-5.dsc mantis_1.1.2+dfsg-5_all.deb to pool/main/m/mantis/mantis_1.1.2+dfsg-5_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. Patrick Schoenfeld [EMAIL PROTECTED] (supplier of updated mantis 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: Tue, 07 Oct 2008 11:23:55 +0200 Source: mantis Binary: mantis Architecture: source all Version: 1.1.2+dfsg-5 Distribution: unstable Urgency: high Maintainer: Patrick Schoenfeld [EMAIL PROTECTED] Changed-By: Patrick Schoenfeld [EMAIL PROTECTED] Description: mantis - web-based bug tracking system Closes: 501179 501425 Changes: mantis (1.1.2+dfsg-5) unstable; urgency=medium . * Urgency medium as it clears an rc bug * Properly remove configuration files and unregister them from ucf on purge (Closes: #501425) . mantis (1.1.2+dfsg-4) unstable; urgency=high . * Urgency high because it fixes a security issue * Added a patch for CVE2008-3102: Doesn't set the secure flag for session cookies (Closes: #501179) Checksums-Sha1: c9b13ffc4dbdb10789a1c6a75dd2652699eac316 1184 mantis_1.1.2+dfsg-5.dsc db2c27d1572acf6b5e9437199858d780257d6158 44308 mantis_1.1.2+dfsg-5.diff.gz ce03f4ffecc03d7defe5e0de0c9d2e6c673a2001 1856672 mantis_1.1.2+dfsg-5_all.deb Checksums-Sha256: 67110b37f2b563e347591c797d6a9e3b9eca66d2c7733c4f9037c315dafd1402 1184 mantis_1.1.2+dfsg-5.dsc c56d3bfa2ae9b0c38aaff9fb69b7f622a8131fe29004397f9d1408907345cee3 44308 mantis_1.1.2+dfsg-5.diff.gz d1f9df854f24cb4a66f3a5606e1a3c0b92ecdc5af15a748d2a1047e872032186 1856672 mantis_1.1.2+dfsg-5_all.deb Files:
Bug#501421: tack: FTBFS in lenny: configure: error: installation or configuration problem: C compiler cannot create executables.
Package: tack
Version: 1.06-5
Severity: serious
User: [EMAIL PROTECTED]
Usertags: qa-ftbfs-20081006 qa-ftbfs
Justification: FTBFS on i386
Hi,
During a rebuild of all packages in a lenny chroot, your package failed
to build on i386.
Relevant part:
/usr/bin/fakeroot debian/rules clean
dpatch deapply-all
01-manpage not applied to ./ .
rm -rf patch-stamp patch-stampT debian/patched
dh_testdir
dh_testroot
rm -f build-stamp
rm -f config.guess config.sub
[ ! -f Makefile ] || /usr/bin/make distclean
dh_clean
dpkg-source -b tack-1.06-5
dpkg-source: warning: source directory 'tack-1.06-5' is not
sourcepackage-upstreamversion 'tack-1.06'
dpkg-source: warning: .orig directory name tack-1.06-5.orig is not
package-upstreamversion (wanted tack-1.06.orig)
dpkg-source: info: using source format `1.0'
dpkg-source: info: building tack using existing tack_1.06.orig.tar.gz
dpkg-source: info: building tack in tack_1.06-5.diff.gz
dpkg-source: warning: executable mode 0755 of
'debian/patches/01-manpage.dpatch' will not be represented in diff
dpkg-source: warning: ignoring deletion of file config.sub
dpkg-source: warning: ignoring deletion of file config.guess
dpkg-source: info: building tack in tack_1.06-5.dsc
debian/rules build
test -d debian/patched || install -d debian/patched
dpatch apply-all
applying patch 01-manpage to ./ ... ok.
dpatch cat-all patch-stampT
mv -f patch-stampT patch-stamp
dh_testdir
cp -f /usr/share/misc/config.sub config.sub
cp -f /usr/share/misc/config.guess config.guess
CFLAGS=-Wall -g -O2 LDFLAGS=-Wl,-z,defs,-ltic ./configure
--host=i486-linux-gnu --build=i486-linux-gnu --prefix=/usr
--mandir=\${prefix}/share/man
creating cache ./config.cache
checking host system type... i486-pc-linux-gnu
Configuring for linux-gnu
checking whether make sets ${MAKE}... yes
checking for gcc... gcc
checking whether the C compiler (gcc -Wall -g -O2 -Wl,-z,defs,-ltic) works...
no
configure: error: installation or configuration problem: C compiler cannot
create executables.
make: *** [config.status] Error 1
The full build log is available from:
http://newpeople.debian.org/~lucas/logs/2008/10/06
It is possible that your package builds fine in sid, but you should make sure
that your package also builds fine in lenny before the release.
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
About the archive rebuild: The rebuild was done on about 50 AMD64 nodes
of the Grid'5000 platform, using a clean chroot containing a sid i386
environment. Internet was not accessible from the build systems.
--
| 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#501408: libnet-netrc-ruby: FTBFS in lenny: test runner failed
Package: libnet-netrc-ruby Version: 0.2.1-1.1 Severity: serious User: [EMAIL PROTECTED] Usertags: qa-ftbfs-20081006 qa-ftbfs Justification: FTBFS on i386 Hi, During a rebuild of all packages in a lenny chroot, your package failed to build on i386. Relevant part: /usr/bin/fakeroot debian/rules clean test -x debian/rules dh_testroot dh_clean rm -fr build-* dpkg-source -b libnet-netrc-ruby-0.2.1-1.1 dpkg-source: warning: source directory 'libnet-netrc-ruby-0.2.1-1.1' is not sourcepackage-upstreamversion 'libnet-netrc-ruby-0.2.1' dpkg-source: warning: .orig directory name libnet-netrc-ruby-0.2.1-1.1.orig is not package-upstreamversion (wanted libnet-netrc-ruby-0.2.1.orig) dpkg-source: info: using source format `1.0' dpkg-source: info: building libnet-netrc-ruby using existing libnet-netrc-ruby_0.2.1.orig.tar.gz dpkg-source: info: building libnet-netrc-ruby in libnet-netrc-ruby_0.2.1-1.1.diff.gz dpkg-source: info: building libnet-netrc-ruby in libnet-netrc-ruby_0.2.1-1.1.dsc debian/rules build test -x debian/rules mkdir -p build-libnet-netrc-ruby1.8 cp -a *.rb test lib build-libnet-netrc-ruby1.8 mkdir -p build-libnet-netrc-ruby1.9 cp -a *.rb test lib build-libnet-netrc-ruby1.9 mkdir -p . cd build-libnet-netrc-ruby1.8 \ ruby1.8 setup.rb config --installdirs=std --- lib --- lib/net --- lib/net --- lib cd build-libnet-netrc-ruby1.9 \ ruby1.9 setup.rb config --installdirs=std --- lib --- lib/net --- lib/net --- lib cd build-libnet-netrc-ruby1.8 \ ruby1.8 setup.rb setup --- lib --- lib/net --- lib/net --- lib cd build-libnet-netrc-ruby1.8 \ ruby1.8 test/test_netrc.rb Loaded suite test/test_netrc Started Finished in 0.00625 seconds. 4 tests, 27 assertions, 0 failures, 0 errors cd build-libnet-netrc-ruby1.9 \ ruby1.9 setup.rb setup --- lib --- lib/net --- lib/net --- lib cd build-libnet-netrc-ruby1.9 \ ruby1.9 test/test_netrc.rb Loaded suite test/test_netrc Started /usr/lib/ruby/1.9.0/test/unit/ui/console/testrunner.rb:94:in `sub!': can't modify frozen string (RuntimeError) from /usr/lib/ruby/1.9.0/test/unit/ui/console/testrunner.rb:94:in `test_started' from /usr/lib/ruby/1.9.0/test/unit/util/observable.rb:78:in `call' from /usr/lib/ruby/1.9.0/test/unit/util/observable.rb:78:in `block in notify_listeners' from /usr/lib/ruby/1.9.0/test/unit/util/observable.rb:78:in `each' from /usr/lib/ruby/1.9.0/test/unit/util/observable.rb:78:in `notify_listeners' from /usr/lib/ruby/1.9.0/test/unit/ui/testrunnermediator.rb:47:in `block in run_suite' from /usr/lib/ruby/1.9.0/test/unit/testcase.rb:72:in `run' from /usr/lib/ruby/1.9.0/test/unit/testsuite.rb:34:in `block in run' from /usr/lib/ruby/1.9.0/test/unit/testsuite.rb:33:in `each' from /usr/lib/ruby/1.9.0/test/unit/testsuite.rb:33:in `run' from /usr/lib/ruby/1.9.0/test/unit/testsuite.rb:34:in `block in run' from /usr/lib/ruby/1.9.0/test/unit/testsuite.rb:33:in `each' from /usr/lib/ruby/1.9.0/test/unit/testsuite.rb:33:in `run' from /usr/lib/ruby/1.9.0/test/unit/ui/testrunnermediator.rb:46:in `run_suite' from /usr/lib/ruby/1.9.0/test/unit/ui/console/testrunner.rb:67:in `start_mediator' from /usr/lib/ruby/1.9.0/test/unit/ui/console/testrunner.rb:41:in `start' from /usr/lib/ruby/1.9.0/test/unit/ui/testrunnerutilities.rb:29:in `run' from /usr/lib/ruby/1.9.0/test/unit/autorunner.rb:216:in `run' from /usr/lib/ruby/1.9.0/test/unit/autorunner.rb:12:in `run' from /usr/lib/ruby/1.9.0/test/unit.rb:278:in `block in top (required)' make: *** [build/libnet-netrc-ruby1.9] Error 1 The full build log is available from: http://newpeople.debian.org/~lucas/logs/2008/10/06 It is possible that your package builds fine in sid, but you should make sure that your package also builds fine in lenny before the release. A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot containing a sid i386 environment. Internet was not accessible from the build systems. -- | 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#501411: libdanga-socket-perl: FTBFS in lenny: tests failed
On Tue, 07 Oct 2008 10:29:06 +0200, Lucas Nussbaum wrote:
During a rebuild of all packages in a lenny chroot, your package failed
to build on i386.
Thanks for your bug report (and all your test)!
t/05-postloop.
# Failed test 'took less than 0 + 1 seconds'
# at t/05-postloop.t line 43.
# Failed test 'took less than 1 + 1 seconds'
# at t/05-postloop.t line 43.
# Failed test 'took less than 2 + 1 seconds'
# at t/05-postloop.t line 43.
# Failed test 'took less than 3 + 1 seconds'
# at t/05-postloop.t line 43.
# Failed test 'took less than 4 + 1 seconds'
# at t/05-postloop.t line 43.
# Failed test 'took less than 5 + 1 seconds'
# at t/05-postloop.t line 43.
# Looks like you failed 6 tests of 17.
This seems to be one of those tricky bugs - I built the package once
in a sid cowbuilder chroot and then several times in a lenny
cowbuilder chroot - and the tests always passed ...
Cheers,
gregor
--
.''`. Home: http://info.comodo.priv.at/{,blog/} / GPG Key ID: 0x00F3CFE4
: :' : Debian GNU/Linux user, admin, developer - http://www.debian.org/
`. `' Member of VIBE!AT, SPI Inc., fellow of FSFE | http://got.to/quote/
`-NP: Arlo Guthrie: Hobo's Lullaby (When The Ship Comes In)
signature.asc
Description: Digital signature
Bug#496520: remove sympa from lenny?
Thomas Viehmann a écrit : Hi, Olivier Salaün wrote: As a Sympa developer I'm worried because we don't maintain this Sympa 5.3.4 anymore. The current version of Sympa is 5.4.3 ; any chance this version will be distributed with Lenny instead of the old one? No. (i.e. It is up to the release managers, not me, but their policy on the subject is clear.) The options are release sympa 5.4.3 You mean 5.3.4 ? with the most severe bugs fixed or not release sympa and have the maintainer try to be more timely about updates for the next release. The fact that it is that late in the release cycle lead me to the initial suggestion to drop sympa from lenny. Kind regards T. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#501412: ikvm: FTBFS in lenny: Illegal characters in path
Package: ikvm
Version: 0.34.0.4-4
Severity: serious
User: [EMAIL PROTECTED]
Usertags: qa-ftbfs-20081006 qa-ftbfs
Justification: FTBFS on i386
Hi,
During a rebuild of all packages in a lenny chroot, your package failed
to build on i386.
Relevant part:
/usr/bin/fakeroot debian/rules clean
dh_testdir
dh_testroot
rm -f build-stamp configure-stamp install-stamp
rm -rf classtmp
mkdir -p /build/user-ikvm_0.34.0.4-4-amd64-SFLmkj/ikvm-0.34.0.4-4/debian/.wapi
nant -v clean
NAnt 0.85 (Build 0.85.2478.0; release; 10/14/2006)
Copyright (C) 2001-2006 Gerry Shaw
http://nant.sourceforge.net
Buildfile:
file:///build/user-ikvm_0.34.0.4-4-amd64-SFLmkj/ikvm-0.34.0.4-4/ikvm.build
Target framework: Mono 2.0 Profile
Base Directory: /build/user-ikvm_0.34.0.4-4-amd64-SFLmkj/ikvm-0.34.0.4-4.
Target(s) specified: clean
clean:
[delete] Deleting 8 files.
[delete] Deleting file
/build/user-ikvm_0.34.0.4-4-amd64-SFLmkj/ikvm-0.34.0.4-4/bin/IKVM.AWT.WinForms.dll.
[delete] Deleting file
/build/user-ikvm_0.34.0.4-4-amd64-SFLmkj/ikvm-0.34.0.4-4/bin/IKVM.GNU.Classpath.dll.
[delete] Deleting file
/build/user-ikvm_0.34.0.4-4-amd64-SFLmkj/ikvm-0.34.0.4-4/bin/IKVM.Runtime.dll.
[delete] Deleting file
/build/user-ikvm_0.34.0.4-4-amd64-SFLmkj/ikvm-0.34.0.4-4/bin/JVM.DLL.
[delete] Deleting file
/build/user-ikvm_0.34.0.4-4-amd64-SFLmkj/ikvm-0.34.0.4-4/bin/ikvm-native.dll.
[delete] Deleting file
/build/user-ikvm_0.34.0.4-4-amd64-SFLmkj/ikvm-0.34.0.4-4/bin/ikvm.exe.
[delete] Deleting file
/build/user-ikvm_0.34.0.4-4-amd64-SFLmkj/ikvm-0.34.0.4-4/bin/ikvmc.exe.
[delete] Deleting file
/build/user-ikvm_0.34.0.4-4-amd64-SFLmkj/ikvm-0.34.0.4-4/bin/ikvmstub.exe.
BUILD SUCCEEDED
Total time: 0 seconds.
rm -f bin/IKVM.GNU.Classpath.dll bin/IKVM.Runtime.dll bin/ikvm.exe
bin/ikvmc.exe bin/ikvmstub.exe tools/asmref.exe runtime/IKVM.Runtime.dll
rm -f native/libikvm-native.so
find . -name *.class -exec rm {} \;
rm -f classpath/*.dll
if [ -f classpath/allsources.lst.dist ]; then \
rm -f classpath/allclasses.lst; \
mv classpath/allsources.lst.dist classpath/allsources.lst; \
fi
if [ -f classpath/classpath.build.dist ]; then \
rm -f classpath/classpath.build; \
mv classpath/classpath.build.dist classpath/classpath.build; \
fi
rm -rf /build/user-ikvm_0.34.0.4-4-amd64-SFLmkj/ikvm-0.34.0.4-4/debian/.wapi
/build/user-ikvm_0.34.0.4-4-amd64-SFLmkj/ikvm-0.34.0.4-4/debian/.mono
dh_clean
dpkg-source -b ikvm-0.34.0.4-4
dpkg-source: warning: source directory 'ikvm-0.34.0.4-4' is not
sourcepackage-upstreamversion 'ikvm-0.34.0.4'
dpkg-source: warning: .orig directory name ikvm-0.34.0.4-4.orig is not
package-upstreamversion (wanted ikvm-0.34.0.4.orig)
dpkg-source: info: using source format `1.0'
dpkg-source: info: building ikvm using existing ikvm_0.34.0.4.orig.tar.gz
dpkg-source: info: building ikvm in ikvm_0.34.0.4-4.diff.gz
dpkg-source: warning: ignoring deletion of file bin/JVM.DLL
dpkg-source: warning: ignoring deletion of file bin/IKVM.AWT.WinForms.dll
dpkg-source: warning: ignoring deletion of file bin/IKVM.Runtime.dll
dpkg-source: warning: ignoring deletion of file bin/IKVM.GNU.Classpath.dll
dpkg-source: warning: ignoring deletion of file bin/ikvmstub.exe
dpkg-source: warning: ignoring deletion of file bin/ikvm.exe
dpkg-source: warning: ignoring deletion of file bin/ikvmc.exe
dpkg-source: warning: ignoring deletion of file bin/ikvm-native.dll
dpkg-source: info: building ikvm in ikvm_0.34.0.4-4.dsc
debian/rules build
dh_testdir
mkdir -p
/build/user-ikvm_0.34.0.4-4-amd64-SFLmkj/ikvm-0.34.0.4-4/debian/.wapi
/build/user-ikvm_0.34.0.4-4-amd64-SFLmkj/ikvm-0.34.0.4-4/debian/.mono
Tue Oct 7 01:00:50 UTC 2008 Running nant -v clean
nant -v clean
NAnt 0.85 (Build 0.85.2478.0; release; 10/14/2006)
Copyright (C) 2001-2006 Gerry Shaw
http://nant.sourceforge.net
Buildfile:
file:///build/user-ikvm_0.34.0.4-4-amd64-SFLmkj/ikvm-0.34.0.4-4/ikvm.build
Target framework: Mono 2.0 Profile
Base Directory: /build/user-ikvm_0.34.0.4-4-amd64-SFLmkj/ikvm-0.34.0.4-4.
Target(s) specified: clean
clean:
BUILD SUCCEEDED
Total time: 0 seconds.
Tue Oct 7 01:00:52 UTC 2008 Running uudecode
uudecode -o /dev/stdout debian/classpath-0.95.tar.gz.uue | gunzip | tar -xf -
mv classpath-0.95 classtmp
Tue Oct 7 01:00:54 UTC 2008 Done uudecode
Patching classtmp
patch -p0
debian/classpath-patches/01-ejc-InflaterDynHeader-continue-bad-lineno.patch
patching file classtmp/java/util/zip/InflaterDynHeader.java
if [ ! -f classpath/allsources.lst.dist ]; then \
mv classpath/allsources.lst classpath/allsources.lst.dist; \
fi
sed -e s,^../../classpath-0.95,../classtmp, classpath/allsources.lst.dist
classpath/allsources.lst
if [ ! -f classpath/classpath.build.dist ]; then \
mv classpath/classpath.build classpath/classpath.build.dist; \
fi
sed -e
Bug#501437: More detailed info
Can you provide entire build log? -- Eugene V. Lyubimkin aka JackYF signature.asc Description: OpenPGP digital signature
Bug#501410: libhttp-daemon-ssl-perl: FTBFS in lenny: tests failed
Package: libhttp-daemon-ssl-perl Version: 1.04-2 Severity: serious User: [EMAIL PROTECTED] Usertags: qa-ftbfs-20081006 qa-ftbfs Justification: FTBFS on i386 Hi, During a rebuild of all packages in a lenny chroot, your package failed to build on i386. Relevant part: make[1]: Entering directory `/build/user-libhttp-daemon-ssl-perl_1.04-2-amd64-acdYti/libhttp-daemon-ssl-perl-1.04-2' PERL_DL_NONLAZY=1 /usr/bin/perl -MExtUtils::Command::MM -e test_harness(0, 'blib/lib', 'blib/arch') t/*.t t/loadmoduleok t/testmoduleFAILED test 4 Failed 1/9 tests, 88.89% okay Failed TestStat Wstat Total Fail List of Failed --- t/testmodule.t91 4 Failed 1/2 test scripts. 1/12 subtests failed. Files=2, Tests=12, 1 wallclock secs ( 0.16 cusr + 0.02 csys = 0.18 CPU) Failed 1/2 test programs. 1/12 subtests failed. make[1]: *** [test_dynamic] Error 255 The full build log is available from: http://newpeople.debian.org/~lucas/logs/2008/10/06 It is possible that your package builds fine in sid, but you should make sure that your package also builds fine in lenny before the release. A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot containing a sid i386 environment. Internet was not accessible from the build systems. -- | 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]
Processed: Re: Bug#501420: kfreebsd-7: FTBFS in lenny: Nonexistent build-dependency: libdb4.4-dev
Processing commands for [EMAIL PROTECTED]: notfound 501420 7.1~cvs20081006-1 Bug#501420: kfreebsd-7: FTBFS in lenny: Nonexistent build-dependency: libdb4.4-dev Bug no longer marked as found in version 7.1~cvs20081006-1. notfound 501420 7.1~cvs20080806-1 Bug#501420: kfreebsd-7: FTBFS in lenny: Nonexistent build-dependency: libdb4.4-dev Bug no longer marked as found in version 7.1~cvs20080806-1. notfound 501420 7.1~cvs20080904-1 Bug#501420: kfreebsd-7: FTBFS in lenny: Nonexistent build-dependency: libdb4.4-dev Bug no longer marked as found in version 7.1~cvs20080904-1. 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#501421: tack: FTBFS in lenny: configure: error: installation or configuration problem: C compiler cannot create executables.
Lucas Nussbaum wrote: checking whether the C compiler (gcc -Wall -g -O2 -Wl,-z,defs,-ltic) works... no configure: error: installation or configuration problem: C compiler cannot create executables. make: *** [config.status] Error 1 hmm, even when removing 'defs' from LDFLAGS, it fails to build (for different reason).. will have to investigate. -- Address:Daniel Baumann, Burgunderstrasse 3, CH-4562 Biberist Email: [EMAIL PROTECTED] Internet: http://people.panthera-systems.net/~daniel-baumann/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#501413: mysql-dfsg-5.0: FTBFS in lenny: failed test: rpl_packet
Package: mysql-dfsg-5.0 Version: 5.0.51a-15 Severity: serious User: [EMAIL PROTECTED] Usertags: qa-ftbfs-20081006 qa-ftbfs Justification: FTBFS on i386 Hi, During a rebuild of all packages in a lenny chroot, your package failed to build on i386. Relevant part: make[2]: Entering directory `/build/user-mysql-dfsg-5.0_5.0.51a-15-amd64-iK3E7h/mysql-dfsg-5.0-5.0.51a-15' cd mysql-test ; \ /usr/bin/perl ./mysql-test-run.pl --force Logging: ./mysql-test-run.pl --force MySQL Version 5.0.51 Using ndbcluster when necessary, mysqld supports it Setting mysqld to support SSL connections Using MTR_BUILD_THREAD = 0 Using MASTER_MYPORT = 9306 Using MASTER_MYPORT1= 9307 Using SLAVE_MYPORT = 9308 Using SLAVE_MYPORT1 = 9309 Using SLAVE_MYPORT2 = 9310 Using NDBCLUSTER_PORT = 9310 Using IM_PORT = 9312 Using IM_MYSQLD1_PORT = 9313 Using IM_MYSQLD2_PORT = 9314 Killing Possible Leftover Processes Removing Stale Files Creating Directories Installing Master Database Installing Master Database Installing Slave1 Database Installing Master Cluster Saving snapshot of installed databases === Starting Tests in the 'main' suite TEST RESULT TIME (ms) --- alias [ pass ]290 alter_table-big[ skipped ] Test need 'big-test' option alter_table[ pass ] 13495 analyse[ pass ] 1081 analyze[ pass ]402 ansi [ pass ]230 archive-big[ skipped ] Test need 'big-test' option archive[ pass ] 2501 archive_gis[ pass ] 3836 auto_increment [ pass ] 3661 backup [ pass ]529 bdb-alter-table-1 [ skipped ] Test requires: 'have_bdb' bdb-alter-table-2 [ skipped ] Test requires: 'have_bdb' bdb-crash [ skipped ] Test requires: 'have_bdb' bdb-deadlock [ skipped ] Test requires: 'have_bdb' bdb[ skipped ] Test requires: 'have_bdb' bdb_cache [ skipped ] Test requires: 'have_bdb' bdb_gis[ skipped ] Test requires: 'have_bdb' bdb_notembedded[ skipped ] Test requires: 'have_bdb' bench_count_distinct [ pass ]216 bigint [ pass ] 1577 binary [ pass ] 1373 binlog [ pass ] 2450 binlog_innodb [ pass ]427 binlog_killed [ pass ] 11667 blackhole [ pass ] 1291 bool [ pass ]324 bootstrap [ pass ]475 bulk_replace [ pass ]186 case [ pass ]586 cast [ pass ]920 check [ pass ] 1770 client_xml [ pass ]653 comments [ pass ]187 compare[ pass ]325 compress [ pass ] 6939 connect[ pass ] 5656 consistent_snapshot[ pass ]439 constraints[ pass ]963 count_distinct [ pass ] 1003 count_distinct2[ pass ] 1375 count_distinct3[ pass ] 21771 create [ pass ] 11799 create_not_windows [ pass ]333 create_select_tmp [ pass ]679 csv[ pass ] 1199 ctype_ascii[ pass ]181 ctype_big5 [ pass ] 2122 ctype_collate [ pass ] 1238 ctype_cp1250_ch[ pass ]464 ctype_cp1251 [ pass ]318 ctype_cp932[ pass ] 2370 ctype_cp932_binlog [ pass ]380 ctype_create [ pass ]579 ctype_eucjpms [ pass ]827 ctype_euckr[ pass ] 1808 ctype_gb2312 [ pass ] 2958 ctype_gbk [ pass ] 2075 ctype_hebrew [ pass ]373 ctype_latin1 [ pass ]563 ctype_latin1_de[ pass ]748 ctype_latin2
Bug#501461: acon: code still insecure, post-audit buffer overflows exist
Package: acon
Version: 1.0.5-7
Severity: grave
Justification: local root
Hi,
as discussed on planet.debian.org and #476603, acon contains unsecure code:
[Brian M. Carlson]
I am subscribed to debian-audit, and we were requested to provide an
audit, which I did. My recommendation stands. It's very difficult
to audit the code, which is why I can't be sure I haven't missed
something.
[...]
Sounds like it indeed shouldn't be included in Lenny, then.
I tend to agree. People not believing the insecurity of the code are
invited to run acon, bring up the menu (it was at Ctrl-Alt-G for my
keyboard and disappeared, the latter goes away when one disables the
console switching test as in the attached diff), select add console and
type more than 200 letters to the 200 char tmp array of menu.c/options.
I have marked a code position overflowing this buffer in attached diff.
Please note that this is NOT about this specific overflow. I have found
it by grepping(!) through the code for string functions for 5 minutes.
acon needs to be completely redone before being remotely safe,
preferably in a way that is less likely to create all sorts of
vulnerabilities.
Note that this hole was unnoticed during an audit during which the
auditor came to the conclusion to not ship the code as it is likely that
there are more vulnerabilities than those he found. He was right.
I'd note that during testing acon seemed to exhibit multiple unrelated
crashes, too.
Kind regards
T.
--
Thomas Viehmann, http://thomas.viehmann.net/
diff -urN acon-1.0.5~/menu.c acon-1.0.5/menu.c
--- acon-1.0.5~/menu.c 2003-07-18 21:09:34.0 +0200
+++ acon-1.0.5/menu.c 2008-10-07 17:27:41.0 +0200
@@ -129,8 +129,8 @@
/*if the active console is changed*/
if( currentconsole!=getactive())
{
-consoleswitched=1;
-return -1;
+//consoleswitched=1;
+//return -1;
}
}while(ch==256);
@@ -259,6 +259,8 @@
str[strlen(str)-1]=0;
break;
default:
+ if (strlen(str)=200)
+ printf(Overflow if str has only size 200.\n);
str[strlen(str)+1]=0;
str[strlen(str)]=ch;
}
Bug#484305: Followup
Hi there, Just to add that I found out that this issue is being further discussed in #499568 : http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=499568 . Best Regards, -- Marcos Marado -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#482140: etch - lenny upgrade fails, because @INC does not contain 5.10 paths
Hi all, Examining bug #482140 I found, that update-xmlcatalog fails during dist-upgrade from Etch to Lenny with an Error, that Functions.pm cannot be found in @INC (the same goes for defoma-app, IIRC there Copy.pm was not found). The paths in @INC were only the generic paths and the 5.8 paths, but the 5.10 paths were missing. I wonder, how to solve the problem. The problem is reprosucible in my pbuilder (Etch-)CHROOT doing: apt-get install docbook-xml vim apt-get install gnome (unfortunately I cannot yet reproduce it with a smaller subset of packages) vim /etc/apt/sources.list (etch - lenny) apt-get update Remove the `|| true' statements in /var/lib/dpkg/info/docbook-xml.prerm and add an `set -ex' at the top and you will get the error doing: apt-get dist-upgrade Unfortunately I removed the log. But I will produce a new one and send relevant parts in a second mail. I hope, I understood the log correctly. ATM I think of using a Pre-Depends: perl, perl-modules for xml-core and I hope, it works. But I'm not sure. What is your opinion? Regards, Daniel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#499070: dpkg leaves system in unusable state after running out of diskspace
On Tue, 07 Oct 2008, Guillem Jover wrote: Any progress ? Yeah got the code the day after that mail, but I've not found the time to test it. I guess the easiest is to change one of the function return values to the output of rand() or similar and see from there. I'll try to get to it this week. Just share it, others might have the time to test (using quota on a openvz virtual environment for example). Cheers, -- Raphaël Hertzog Le best-seller français mis à jour pour Debian Etch : http://www.ouaza.com/livre/admin-debian/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#501462: [motion] Can't install without video device present
Package: motion Version: 3.2.9-6 Severity: serious --- Please enter the report below this line. --- --- System information. --- Architecture: amd64 Kernel: Linux 2.6.26-1-openvz-amd64 Debian Release: lenny/sid 500 testing security.debian.org I get this output when installing: Setting up motion (3.2.9-6) ... Starting motion detection : motion:[0] Processing thread 0 - config file /etc/motion/motion.conf [0] Motion 3.2.9 Started [0] ffmpeg LIBAVCODEC_BUILD 3355136 LIBAVFORMAT_BUILD 3409664 [0] Thread 1 is from /etc/motion/motion.conf [1] Thread 1 started [1] Failed to open video device /dev/video0: No such file or directory [1] Capture error calling vid_start [1] Thread finishing... [0] motion-httpd/3.2.9 running, accepting connections [0] motion-httpd: waiting for data on port TCP 8080 failed! invoke-rc.d: initscript motion, action start failed. I install motion because I have a video device, but it's not always plugged in. --- Package information. --- Depends (Version) | Installed ===-+-== libavcodec51 (= 0.svn20080206-8) | 3:20080706-0.2 OR libavcodec-unstripped-51 (= 0.svn20080206-8) | libavformat52 (= 0.svn20080206-8) | 3:20080706-0.2 OR libavformat-unstripped-52 (= 0.svn20080206-8) | libavutil49 (= 0.svn20080206-8) | 3:20080706-0.2 OR libavutil-unstripped-49(= 0.svn20080206-8) | libc6(= 2.7-1) | 2.7-14 libjpeg62 | 6b-14 libmysqlclient15off (= 5.0.27-1) | 5.0.51a-15 libpq5 (= 8.3~beta1) | 8.3.4-1 debconf (= 0.5) | 1.5.23 OR debconf-2.0 | adduser | 3.110 debconf | 1.5.23 -- @James LewisMoss [EMAIL PROTECTED] | Blessed Be! @http://www.lewismoss.org/~dres | Linux is kewl! @Argue for your limitations and sure enough, they're yours. Bach -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#501154: Patch adjustment
Micah Anderson a écrit : I've taken David's patch and removed the extraneous bits (substitutions done because of the build process, etc.), and attached the adjusted diff to this bug. Regarding your changes to parser.pl :you should also make all the regular expressions multi-line in parser.pl module. If you don't the parser will be broken. Note that this parser is currently only used by the task_manager.pl to parse task templates. Therefore we'll replace the call to the parser with a call to the TT2 parser. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#501461: acon: code still insecure, post-audit buffer overflows exist
On Tue, Oct 7, 2008 at 17:43:59 +0200, Thomas Viehmann wrote: Please note that this is NOT about this specific overflow. I have found it by grepping(!) through the code for string functions for 5 minutes. acon needs to be completely redone before being remotely safe, preferably in a way that is less likely to create all sorts of vulnerabilities. Note that this hole was unnoticed during an audit during which the auditor came to the conclusion to not ship the code as it is likely that there are more vulnerabilities than those he found. He was right. I suggest removing this package from debian altogether. We shouldn't distribute setuid root binaries with lots of known bugs and poor code quality, IMO. Cheers, Julien -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#500711: kdenetwork package broken dependency OS390
On Tue, Sep 30, 2008 at 01:30:58PM -0400, Tom Delany wrote: Package: kdenetwork Version: 4:3.5.5-5 Severity: grave Justification: renders package unusable kdenetwork depends upon kwifimanager 4:3.5.9-4; however kwifimanager 4:3.5.9-4 is not available for the OS390 architecture. This makes the package uninstallable. Does somebody have a better idea to this that making the metapackage Arch:any? Ana -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#500325: xorp: FTBFS: Not using -fPIC to generate shared lib.
* Jose Manuel dos Santos Calhariz [Mon, 06 Oct 2008 02:49:29 +0100]: Hello, The configure command have two options: --enable-shared and --with-pic I have tried --with-pic in a i386 arch and the shared libraries didn't have code without -fPIC. The xorp-user mailing list suggested to use --enable-shared for what seams to be the same problem [1], with an older version compiling in FreeBSD. So I sent to the same mailing-list a question about the differences of the two options. Looking inside configure command the differences are real, but minimal for a Linux system. So in the end could be better adding option --with-pic to the configure command than adding -fPIC to the compiler options. Ok, will you be able to upload soon? Thanks, -- Adeodato Simó dato at net.com.org.es Debian Developer adeodato at debian.org As an adolescent I aspired to lasting fame, I craved factual certainty, and I thirsted for a meaningful vision of human life -- so I became a scientist. This is like becoming an archbishop so you can meet girls. -- Matt Cartmill -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#500540: automounting vfat as utf8
On Mon, Oct 06, 2008 at 07:38:15PM +0200, Sune Vuorela wrote:
Thank you to submitter for the nice analysis of the issue.
KDE uses the information from hal to decide what options to use when
mounting.
On a vfat drive, hal gives the following:
hal-get-property --udi '/org/freedesktop/Hal/devices/volume_uuid_64F8_AEF6' --
key volume.mount.valid_options
ro sync dirsync noatime nodiratime noexec quiet remount exec utf8 shortname=
codepage= iocharset= umask= dmask= fmask= uid= flush
KDE can of course specialcase and don't use the utf8 option on fat
filesystems,
but I don't think it is the job for the frontend to know which options is
safe
and unsafe.
But a untested for the kde3 media manager is here:
kdebase-3.5.9.dfsg.1/kioslave/media/mediamanager$ diff -pruN
halbackend.cpp.orig halbackend.cpp
--- halbackend.cpp.orig 2008-10-06 19:14:22.0 +0200
+++ halbackend.cpp 2008-10-06 19:14:47.0 +0200
@@ -851,7 +851,7 @@ QStringList HALBackend::mountoptions(con
if (valids.contains(utf8))
{
-value = config.readBoolEntry(utf8, true);
+value = config.readBoolEntry(utf8, !fstype.endsWith(fat));
tmp = QString(utf8=%1).arg(value ? true : false);
result tmp;
}
I haven't had kde3 systems around for a long time, so I'm not able to test if
the patch actually works as expected.
Thanks Sune.
I might have time to look at this around next monday (13th October), we will
see about motivation...
If you are reading this bug report, you are a KDE 3 user and you want to help,
please try this.
Ana
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#500711: kdenetwork package broken dependency OS390
On Tuesday 07 October 2008 18:53:30 Adeodato Simó wrote: * Ana Guerrero [Tue, 07 Oct 2008 18:27:15 +0200]: On Tue, Sep 30, 2008 at 01:30:58PM -0400, Tom Delany wrote: Package: kdenetwork Version: 4:3.5.5-5 Severity: grave Justification: renders package unusable kdenetwork depends upon kwifimanager 4:3.5.9-4; however kwifimanager 4:3.5.9-4 is not available for the OS390 architecture. This makes the package uninstallable. Does somebody have a better idea to this that making the metapackage Arch:any? Package: kdenetwork Depends: foo, bar, kwifimanager (= 4:3.5.9) | s390, baz ^^^ Yes, really. (Package type-handling provides it.) but type-handling depends on dpkg-dev making this a bit worse than arch:any metapackage. -- I cannot save the forward from LinuxPPC and from Redhat Linux 2000 or from the file inside AutoCAD, how does it work? The point is that you can't reinstall a wordprocessor, this way then from Word you neither ever have to turn off a shell on a ISA program of the cache of a driver, nor can ever insert in the IP application, so that from the control tools menu within X-Windows XP you either can never ping the folder, or need to rename a provider to a cache and therefore you neither should debug the monitor, nor should ever receive the Fast front-side bus over a USB port 3 for saving on the BIOS on a mailer on the digital SMTP desktop over the sendmail. signature.asc Description: This is a digitally signed message part.
Bug#500711: kdenetwork package broken dependency OS390
* Ana Guerrero [Tue, 07 Oct 2008 18:27:15 +0200]: On Tue, Sep 30, 2008 at 01:30:58PM -0400, Tom Delany wrote: Package: kdenetwork Version: 4:3.5.5-5 Severity: grave Justification: renders package unusable kdenetwork depends upon kwifimanager 4:3.5.9-4; however kwifimanager 4:3.5.9-4 is not available for the OS390 architecture. This makes the package uninstallable. Does somebody have a better idea to this that making the metapackage Arch:any? Package: kdenetwork Depends: foo, bar, kwifimanager (= 4:3.5.9) | s390, baz ^^^ Yes, really. (Package type-handling provides it.) HTH, -- Adeodato Simó dato at net.com.org.es Debian Developer adeodato at debian.org La música es de los que la quieren escuchar y de nadie más. -- Andrés Calamaro -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#475858: Elfkickers FTFBS due to asm/elf.h removal from kernel
merge 475858 479900 thanks Elfkickers currently FTBFS on sid systems due to the kernel no longer exporting asm/elf.h as a header, and so elfkickers needs specific dependancies to sort this out. I think I've found a good set of deps (patch attached) but here's some explanation why these various things might work (depending on whether you're on a lenny, etch or sid system): libc6-dev: 2.7-13 is the current lenny/sid version, and that has asm/elf.h in it. Lower versions might also work (2.7-10 doesn't according to http://people.debian.org/~lucas/logs/2008/05/06/elfkickers_2.0a-3_sid32-gcc43.buildlog.gz), but I haven't checked. linux-libc-dev (or linux-kernel-headers, which by lenny becomes a virtual package supplied by linux-libc-dev): 2.6.24 appears to be the right timeframe for last kernel that exported the header based on http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=6cc931b9b5ec652c90b928f3ec2163f261552c91 being the commit that removes the asm/elf.h export, and http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=tag;h=0d733ddb2026683da26c1722847b99911c43ccb5 - the tag for 2.6.24 - being the last version tag before that. 2.6.25 is at http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=tag;h=20b8df8e5501bac243e64c0c8c52907735a0041b and is too late. Between these three, the right packages should get pulled in and everything *should* just work! Tom Parker diff --git a/debian/control b/debian/control index 4845e27..b04a109 100644 --- a/debian/control +++ b/debian/control @@ -2,7 +2,7 @@ Source: elfkickers Section: utils Priority: extra Maintainer: Fathi Boudra [EMAIL PROTECTED] -Build-Depends: cdbs, debhelper (= 6), quilt +Build-Depends: cdbs, debhelper (= 6), quilt, libc6-dev (= 2.7-13) | linux-kernel-headers (= 2.6.24) |linux-libc-dev (= 2.6.24) Standards-Version: 3.7.3 Homepage: http://www.muppetlabs.com/~breadbox/software/elfkickers.html
Processed: Elfkickers FTFBS due to asm/elf.h removal from kernel
Processing commands for [EMAIL PROTECTED]: merge 475858 479900 Bug#475858: elfkickers_2.0a-3(sparc/unstable): error: 'ELF_DATA' undeclared (first use in this function) Bug#479900: elfkickers: FTBFS: sstrip.c:12:21: error: asm/elf.h: No such file or directory Merged 475858 479900. 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#482140: etch - lenny upgrade fails, because @INC does not contain 5.10 paths
Am Dienstag, den 07.10.2008, 17:51 +0200 schrieb Daniel Leidert: Examining bug #482140 I found, that update-xmlcatalog fails during dist-upgrade from Etch to Lenny with an Error, that Functions.pm cannot be found in @INC (the same goes for defoma-app, IIRC there Copy.pm was not found). The paths in @INC were only the generic paths and the 5.8 paths, but the 5.10 paths were missing. Here the log output: Preparing to replace fontconfig 2.4.2-1.2 (using .../fontconfig_2.6.0-1_i386.deb) ... Can't locate File/Copy.pm in @INC (@INC contains: /etc/perl /usr/local/lib/perl/5.8.8 /usr/local/share/perl/5.8.8 /usr/lib/perl5 /usr/share /perl5 /usr/lib/perl/5.8 /usr/share/perl/5.8 /usr/local/lib/site_perl .) at /usr/bin/defoma-app line 7. BEGIN failed--compilation aborted at /usr/bin/defoma-app line 7. dpkg: warning - old pre-removal script returned error exit status 2 dpkg - trying script from the new package instead ... dpkg: ... it looks like that went OK. and for update-xmlcatalog: Preparing to replace docbook-xml 4.4-5 (using .../docbook-xml_4.5-5_all.deb) ... Can't locate File/Spec/Functions.pm in @INC (@INC contains: /etc/perl /usr/local/lib/perl/5.8.8 /usr/local/share/perl/5.8.8 /usr/lib/perl5 /usr/share/perl5 /usr/lib/perl/5.8 /usr/share/perl/5.8 /usr/local/lib/site_perl .) at /usr/sbin/update-xmlcatalog line 124. BEGIN failed--compilation aborted at /usr/sbin/update-xmlcatalog line 124. I guess, update-xmlcatalog still fails by trying the prerm script from the new version - we just don't see it because of the `|| true' statements in it. And thus the bug #482140 is observed. The issue does not occur, if perl and perl-modules are updated/installed before I try to update docbook-xml. In this case, everything works fine. Ideas are appreciated. Regards, Daniel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#501207: destar: Fails to run with python2.5
On Tue, Oct 07, 2008 at 09:07:10AM +0300, Faidon Liambotis wrote: John Wright wrote: Yes, lenny will have both python2.4 and python2.5. One workaround, at least for the compiler.ast.From problem, would be to run destar with #!/usr/bin/python2.4 instead of #!/usr/bin/python. But I think it better to fix the bug rather than try to work around it, if possible. Definitely, my concern was for the backwards compatibility. Are your fixes backwards compatible? It'd suck to fix this only to have a bug report the day after fails to run with python2.4 :) I made sure the fix for #501207 was backwards-compatible. As for the SyntaxError problem, I'm surprised it ever worked at all. Function definitions with optional arguments before required positional arguments aren't legal in 2.4 either (I'm not sure when/if they ever were). Maybe quixote used to generate different actual Python code than it does now in this case? Anyway, I'm pretty certain the patch for the SyntaxError will work with python2.4, but I'll check tomorrow. Great, thanks a lot! It still works for me when I replace #!/usr/bin/env python with #!/usr/bin/env python2.4 in /usr/share/destar/python/destar.py. -- John Wright [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#482439: cfengine2: There are still a ton of segfaults
Further testing shows this same failure hitting on most of my x86 boxen I'm not yet sure it is the only one, but is deffinitely common. -- Rick Nelson Linux was made by foreign terrorists to take money from true US companies like Microsoft. - Some AOL'er. To this end we dedicate ourselves... -Don -- From the sig of Don, [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#391935: Bug #391935: Re: The answer from Citrix Xen.org
Le mardi 07 octobre 2008 à 10:31 +0200, Josselin Mouette a écrit : I’ll ask for clarifications about the rest. And here are the clarifications. My understanding is the following: * We can call the distributed software Xen as long as it is compatible with upstream regarding to VM images support. The compatibility test is not yet available, but we could easily setup a test suite to be run manually when in doubt. In all cases, I’m pretty sure any incompatibility would already be considered a bug, and full compatibility with upstream is something that we should definitely advertise. * If someone wants to make an incompatible version, he will have to change the name. Personally, I don’t think this restriction is incompatible with the DFSG, as there are no real restrictions on modifications. Since we have hands free for patches that are relevant to us, this is not a Mozilla-like situation. * If we really want to take the paranoid stanza, I guess it would be fine to keep the package names and change the descriptions to make it clear it is “based on Xen”. However I would find it detrimental for both Debian and upstream. 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. ---BeginMessage--- Hi Josselin See inline. -Original Message- From: Josselin Mouette [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 07, 2008 2:31 AM To: Stephen Spector Cc: [EMAIL PROTECTED] Subject: RE: About the Xen trademark policy Le vendredi 03 octobre 2008 à 13:02 -0400, Stephen Spector a écrit : 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. Sorry to bother you again, but actually some people in the project asked me to clarify the following points: * Are we allowed to distribute our modified versions using the Xen name? (I already understand that the answer is yes.) Yes * Are we allowed to distribute commercially our modified versions using the Xen name? Commercial products that are sold to customers can use the Xen name if they commit to the compatibility goals of the Xen project (ie we use the name solely to ensure that any VM created on any Xen implementation will run on any other Xen implementation). The compatibility goals are enshrined in the FIT test which stands for Faithful Implementation Test. The Xen project specifically regards Xen compatibility and uniformity of management APIs as key to the goals of the project (we want fast, free, compatible, ubiquitous implementations of the same technology only insofar as the technology meets the compatibility goals. Customers rely on that as a key requirement for their virtualized infrastructure) * Are our users allowed to redistribute, commercially or not, our modified versions, using the Xen name? Any free/community use can do whatever it wants, quite literally. Any commercial distribution that wishes to call itself Xen must be compatible with other Xen branded commercial offerings, otherwise the commercial distribution is not Xen. This is determined by the FIT test. In the latter case, where an arbitrary, possibly incompatible variant of the code base is commercially distributed then it clearly isn't Xen, however it may still use the (factually correct) term Xen based or Xen derived or similar. * Are our users allowed to redistribute, commercially or not, versions they have modified further, using the Xen name? Community - yes, anything is allowed. Commercial implementations must support our user base / customer base's key demands for compatibility as defined in the FIT test. There are quite a number of our users who propose commercial Debian- based offers, and we need to ensure that they will not violate your trademark policy by doing so Absolutely. Please understand that the policy is in place specifically to counter claims (from competitive non open source technologies/companies) that Xen is fragmented and incompatible and with a weak ISV ecosystem. Our aspiration is for that not to be the case - through unification of the vendors around a simple test of compatibility - the FIT. Of course, we are ready to accept some conditions on the range of allowed modifications, and the FIT test idea looks acceptable to me; we still consider the software to be free since we can modify it further by changing the name. I certainly hope that we meet your needs. Let me emphasize that we view satisfying the needs of the Debian
Bug#501423: No need for approval of gossip in testing.
During a rebuild of all packages in a lenny chroot, your package failed to build on i386. I have no idea why gossip 1:0.31-1 was approved to testing without talking to me. Norbert I'm confused - you uploaded gossip to unstable: http://packages.qa.debian.org/g/gossip/news/20080804T091731Z.html Version: 1:0.31-1 Distribution: unstable Urgency: low Maintainer: Debian GNOME Maintainers [EMAIL PROTECTED] Changed-By: Norbert Tretkowski [EMAIL PROTECTED] Migration to testing happens automatically from unstable, you should have received notification of the migration, there is no approval needed. Are you saying that gossip should be removed from testing and therefore removed from the release? -- Neil Williams = http://www.data-freedom.org/ http://www.nosoftwarepatents.com/ http://www.linux.codehelp.co.uk/ pgpbALpRQQedZ.pgp Description: PGP signature
