Bug#494514: insserv: Test suite fail on alpha
[Steve Langasek] > In this case, NFS... Right. So ext3 and NFS should be ok. :) > I can try against a different filesystem tomorrow if you like. If you happen to know what file system is used on the autobuilder, or if ext2/ext3 is not the default file system on alpha, it would be useful to have a test with those file systems as well. If not, it will be a shot in the dark, and I have no idea what file system to suggest. Happy hacking, -- Petter Reinholdtsen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#494514: insserv: Test suite fail on alpha
On Mon, Aug 18, 2008 at 08:27:29AM +0200, Petter Reinholdtsen wrote: > [Steve Langasek] > > I can't reproduce this on my alpha here. So this may be a problem > > with how goetz is set up, rather than a general alpha problem. > Right. Which file system type are you using on your alpha? In this case, NFS... I can try against a different filesystem tomorrow if you like. Cheers, -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developerhttp://www.debian.org/ [EMAIL PROTECTED] [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#494514: insserv: Test suite fail on alpha
[Steve Langasek] > I can't reproduce this on my alpha here. So this may be a problem > with how goetz is set up, rather than a general alpha problem. Right. Which file system type are you using on your alpha? > I've given insserv back on alpha to see whether it's reproducible or > if this was a fluke, but goetz is the only buildd that I see alive > for alpha currently, so if it fails again then I think we need to > find a sourceful fix (or figure out what's wrong with the buildd) > for release. It failed again. I guess the admin of goetz need to be involved to figure out which file system is used during build. As mentioned earlier, tmpfs had a kernel bug triggering the behaviuor we see during build. If it is used or other file systems have it took, it would explain the issue on the autobuilder for alpha. I guess we should turn off readahead on directories until it is safe to enable it by default. :/ Happy hacking, -- Petter Reinholdtsen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#493573: Backtrace on 'hung' apache2 (while trying to stop service)
Chris Horn wrote:
I'm not really a programmer (so this may be obvious from the backtrace),
but disabling the PHP5 module completely solves the problem.
Sorry for so much traffic, but I bring good news. I just upgraded all of my
MySQL packages to 'testing' and now everything appears to work.
# dpkg -l | grep mysql | awk '{print $1" "$2" "$3}'
ii libdbd-mysql-perl 4.007-1
ii libmysqlclient15off 5.0.51a-12
ii mysql-admin 5.0r12-1
ii mysql-client 5.0.51a-12
ii mysql-client-5.0 5.0.51a-12
ii mysql-common 5.0.51a-12
ii mysql-gui-tools-common 5.0r12-1
ii mysql-navigator 1.4.2-11
ii mysql-query-browser 5.0r12-1
ii mysql-server 5.0.51a-12
ii mysql-server-5.0 5.0.51a-12
ii php5-mysql 5.2.6-2+b1
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#493573: Backtrace on 'hung' apache2 (while trying to stop service)
I'm not really a programmer (so this may be obvious from the backtrace), but disabling the PHP5 module completely solves the problem. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#495493: marked as done (Deadlocks in fsdestroy() handling)
Your message dated Mon, 18 Aug 2008 01:17:02 + with message-id <[EMAIL PROTECTED]> and subject line Bug#495493: fixed in python-fuse 1:0.2-pre3-7 has caused the Debian Bug report #495493, regarding Deadlocks in fsdestroy() handling 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.) -- 495493: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=495493 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems --- Begin Message --- Package: python-fuse Version: 1:0.2-pre3-6 Severity: serious Tags: patch Hi, python-fuse deadlocks whilst unmounting, causing the Python interpreter to remain in memory after the filesystem has been unmounted as well resulting in the fsdestroy() callback not being executed. This breaks AptFS, which attempts to remove downloaded packages in this callback - not executing it results in the user's download directory (not necessarily an automatically-cleaned directory) being filled up with files. A patch against the latest python-fuse Debian package is attached; it fixes the problem in my tests. Why I think this patch should be in Lenny: * Breaks other packages * One-line patch * Patch already committed and blessed by upstream[0] Regards, /Lamby [0] http://mercurial.creo.hu/repos/fuse-python-hg/index.cgi/rev/b8a0b93a5f38 -- Chris Lamb, UK [EMAIL PROTECTED] GPG: 0x634F9A20 diff -urNd python-fuse-0.2-pre3.orig/fuseparts/_fusemodule.c python-fuse-0.2-pre3/fuseparts/_fusemodule.c --- python-fuse-0.2-pre3.orig/fuseparts/_fusemodule.c 2008-08-18 00:12:17.0 +0100 +++ python-fuse-0.2-pre3/fuseparts/_fusemodule.c2008-08-18 00:12:50.0 +0100 @@ -896,6 +896,7 @@ save = PyEval_SaveThread(); err = fuse_loop_mt(f); PyEval_RestoreThread(save); + interp = NULL; #endif return(err); signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: python-fuse Source-Version: 1:0.2-pre3-7 We believe that the bug you reported is fixed in the latest version of python-fuse, which is due to be installed in the Debian FTP archive: python-fuse_0.2-pre3-7.diff.gz to pool/main/p/python-fuse/python-fuse_0.2-pre3-7.diff.gz python-fuse_0.2-pre3-7.dsc to pool/main/p/python-fuse/python-fuse_0.2-pre3-7.dsc python-fuse_0.2-pre3-7_i386.deb to pool/main/p/python-fuse/python-fuse_0.2-pre3-7_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. Sebastien Delafond <[EMAIL PROTECTED]> (supplier of updated python-fuse 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: Sun, 17 Aug 2008 18:00:19 -0700 Source: python-fuse Binary: python-fuse Architecture: source i386 Version: 1:0.2-pre3-7 Distribution: unstable Urgency: low Maintainer: Sebastien Delafond <[EMAIL PROTECTED]> Changed-By: Sebastien Delafond <[EMAIL PROTECTED]> Description: python-fuse - Python bindings for FUSE (Filesystems in USErland) Closes: 495493 Changes: python-fuse (1:0.2-pre3-7) unstable; urgency=low . * Applied patch that prevents python-fuse from deadlocking while unmounting a filesystem (Closes: #495493). Checksums-Sha1: 0277ce4e04da1c433d2e1fb5d7ebe681600fbd6a 1142 python-fuse_0.2-pre3-7.dsc 1b9492e72dca3ed4717d54420d99fe1b60854204 3036 python-fuse_0.2-pre3-7.diff.gz 478c30976356c1d2978f40f1b52f97b9f80747f8 57718 python-fuse_0.2-pre3-7_i386.deb Checksums-Sha256: d295e652d58063e0065ecb50b2700794831c021c57581d75bb6de78fa89e886d 1142 python-fuse_0.2-pre3-7.dsc 7f861fd5d0f172e1020fa86021080d90645f6eb4637256228379ece4743f0329 3036 python-fuse_0.2-pre3-7.diff.gz 05a98898705a37d6a42ae9ff160bd55e04f4cfe25ac6cc3593ebd22aeebc8f71 57718 python-fuse_0.2-pre3-7_i386.deb Files: 38faec287c1b26159b9cf2ee8c5c7933 1142 python optional python-fuse_0.2-pre3-7.dsc 588eb143530ff25f4b73f222b7e7d432 3036 python optional python-fuse_0.2-pre3-7.diff.gz 7f4bbe8cc263c7f05d9eb402d7769f2e 57718 python optional python-fuse_0.2-pre3-7_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFIqMrwiZgNKcDdyD8RAkVzAJ4gpKvb+XwDCCoswI7RWwF2mAZ/zwCfWJsL hYP8KWL3SVV46AW5zFt
Bug#420979: marked as done (FTBFS: time.c:35: error: 'CLK_TCK' undeclared)
Your message dated Mon, 18 Aug 2008 00:32:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#420979: fixed in icon 9.4.3-2 has caused the Debian Bug report #420979, regarding FTBFS: time.c:35: error: 'CLK_TCK' undeclared 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.) -- 420979: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=420979 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems --- Begin Message --- Package: icon Version: 9.4.2-2.7 Severity: serious Justification: no longer builds from source Hi! icon currently fails to build from source in sid [1]: --- 8< --- gcc -Wall -g -O0 -c -o time.o time.c time.c: In function 'millisec': time.c:35: error: 'CLK_TCK' undeclared (first use in this function) time.c:35: error: (Each undeclared identifier is reported only once time.c:35: error: for each function it appears in.) time.c:36: warning: control reaches end of non-void function make[2]: *** [time.o] Error 1 --- >8 --- Cheers, -- Jérémy Bobbio.''`. [EMAIL PROTECTED]: :Ⓐ : # apt-get install anarchism `. `'` `- signature.asc Description: Digital signature --- End Message --- --- Begin Message --- Source: icon Source-Version: 9.4.3-2 We believe that the bug you reported is fixed in the latest version of icon, which is due to be installed in the Debian FTP archive: icon-ipl_9.4.3-2_all.deb to pool/main/i/icon/icon-ipl_9.4.3-2_all.deb icon_9.4.3-2.diff.gz to pool/main/i/icon/icon_9.4.3-2.diff.gz icon_9.4.3-2.dsc to pool/main/i/icon/icon_9.4.3-2.dsc iconc_9.4.3-2_i386.deb to pool/main/i/icon/iconc_9.4.3-2_i386.deb icont_9.4.3-2_i386.deb to pool/main/i/icon/icont_9.4.3-2_i386.deb iconx_9.4.3-2_i386.deb to pool/main/i/icon/iconx_9.4.3-2_i386.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Christian Hudon <[EMAIL PROTECTED]> (supplier of updated icon 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: Sun, 17 Aug 2008 19:45:27 -0400 Source: icon Binary: icont iconx iconc icon-ipl Architecture: source all i386 Version: 9.4.3-2 Distribution: unstable Urgency: medium Maintainer: Christian Hudon <[EMAIL PROTECTED]> Changed-By: Christian Hudon <[EMAIL PROTECTED]> Description: icon-ipl - Libraries for Icon, a high-level programming language iconc - Compiler for Icon, a high-level programming language icont - Interpreter for Icon, a high-level programming language iconx - Executor for Icon, a high-level programming language Closes: 420979 475952 Changes: icon (9.4.3-2) unstable; urgency=medium . * Apply patch from Jurij Smakov to correctly change -O2 to -O0 when building. Should build and pass tests on all archs now, including Sparc32 (Closes: #475952, #420979) Checksums-Sha1: db949ef370505174cca728510572c1fa43bceee5 947 icon_9.4.3-2.dsc 08f346d567a6314f53f607886f3c0ce294dff5ef 12793 icon_9.4.3-2.diff.gz c9c7bdcbe10820533311fdf221dc4729647b9e50 1407508 icon-ipl_9.4.3-2_all.deb 4ad6101861f9e5d751946eb93105ef5a06a57558 46834 icont_9.4.3-2_i386.deb d4442e07b09bc5961146bffe5ce781c9dfeda5d9 164308 iconx_9.4.3-2_i386.deb d52b81f6ea8fe096b2628c4e5e41a18d944b0eb9 1235542 iconc_9.4.3-2_i386.deb Checksums-Sha256: 51b4c5da84b7760a24c4b352f9104e4ee3cea41eda77c92f84150c93960ceb6d 947 icon_9.4.3-2.dsc 32c1a9048b4f9688bf866c8dff29169f6edcd10b3bd327eaf9c6db00efbecf2a 12793 icon_9.4.3-2.diff.gz 04ab618182e6d3b9b59dd5fa750ce17c5776cf538f160e11b476011bc30eba1a 1407508 icon-ipl_9.4.3-2_all.deb 93ef62d3cb6da1ee505282815c3fefbd9f826f98f8c4a500f5265d670cfd4305 46834 icont_9.4.3-2_i386.deb 66736fd1cc10d7ad1c3ef4d02167a4ed102bec403df0eb851d589a186e28c8d8 164308 iconx_9.4.3-2_i386.deb 6dfcbe15f754d699e68af3899234932176fb1ec672458a6c19489bf57a54d993 1235542 iconc_9.4.3-2_i386.deb Files: c3ba4cdcae68f5eca55574d8f1803bc0 947 devel optional icon_9.4.3-2.dsc cf64af39b08a97015b57c03b0b5ae194 12793 devel optional icon_9.4.3-2.diff.gz 9b41945397722a517d2a84dc467396c3 1407508 devel optional icon-ipl_9.4.3-2_all.deb 00267a11571865686ad34cd7ff74c187 46834 devel optional icont_
Bug#475952: marked as done (icon_9.4.3-1(sparc/unstable): FTBFS on sparc)
Your message dated Mon, 18 Aug 2008 00:32:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#475952: fixed in icon 9.4.3-2 has caused the Debian Bug report #475952, regarding icon_9.4.3-1(sparc/unstable): FTBFS on sparc 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.) -- 475952: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=475952 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems --- Begin Message --- Package: icon Version: 9.4.3-1 Severity: serious There was an error while trying to autobuild your package: > Automatic build of icon_9.4.3-1 on lebrun by sbuild/sparc 98 > Build started at 20080414-0641 [...] > ** Using build dependencies supplied by package: > Build-Depends: libx11-dev, libxt-dev [...] > Testing transmit > Testing trim > Testing var > Testing wordcnt > > Tests failed: ilib sorting table > > make[3]: *** [Test-programs] Error 1 > make[3]: Leaving directory `/build/buildd/icon-9.4.3/tests/general' > make[2]: *** [Test] Error 2 > make[2]: Leaving directory `/build/buildd/icon-9.4.3/tests' > make[1]: *** [Test-icont] Error 2 > make[1]: Leaving directory `/build/buildd/icon-9.4.3' > make: *** [test-icont] Error 2 > dpkg-buildpackage: failure: /usr/bin/fakeroot debian/rules binary-arch gave > error exit status 2 A full build log can be found at: http://buildd.debian.org/build.php?arch=sparc&pkg=icon&ver=9.4.3-1 --- End Message --- --- Begin Message --- Source: icon Source-Version: 9.4.3-2 We believe that the bug you reported is fixed in the latest version of icon, which is due to be installed in the Debian FTP archive: icon-ipl_9.4.3-2_all.deb to pool/main/i/icon/icon-ipl_9.4.3-2_all.deb icon_9.4.3-2.diff.gz to pool/main/i/icon/icon_9.4.3-2.diff.gz icon_9.4.3-2.dsc to pool/main/i/icon/icon_9.4.3-2.dsc iconc_9.4.3-2_i386.deb to pool/main/i/icon/iconc_9.4.3-2_i386.deb icont_9.4.3-2_i386.deb to pool/main/i/icon/icont_9.4.3-2_i386.deb iconx_9.4.3-2_i386.deb to pool/main/i/icon/iconx_9.4.3-2_i386.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Christian Hudon <[EMAIL PROTECTED]> (supplier of updated icon 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: Sun, 17 Aug 2008 19:45:27 -0400 Source: icon Binary: icont iconx iconc icon-ipl Architecture: source all i386 Version: 9.4.3-2 Distribution: unstable Urgency: medium Maintainer: Christian Hudon <[EMAIL PROTECTED]> Changed-By: Christian Hudon <[EMAIL PROTECTED]> Description: icon-ipl - Libraries for Icon, a high-level programming language iconc - Compiler for Icon, a high-level programming language icont - Interpreter for Icon, a high-level programming language iconx - Executor for Icon, a high-level programming language Closes: 420979 475952 Changes: icon (9.4.3-2) unstable; urgency=medium . * Apply patch from Jurij Smakov to correctly change -O2 to -O0 when building. Should build and pass tests on all archs now, including Sparc32 (Closes: #475952, #420979) Checksums-Sha1: db949ef370505174cca728510572c1fa43bceee5 947 icon_9.4.3-2.dsc 08f346d567a6314f53f607886f3c0ce294dff5ef 12793 icon_9.4.3-2.diff.gz c9c7bdcbe10820533311fdf221dc4729647b9e50 1407508 icon-ipl_9.4.3-2_all.deb 4ad6101861f9e5d751946eb93105ef5a06a57558 46834 icont_9.4.3-2_i386.deb d4442e07b09bc5961146bffe5ce781c9dfeda5d9 164308 iconx_9.4.3-2_i386.deb d52b81f6ea8fe096b2628c4e5e41a18d944b0eb9 1235542 iconc_9.4.3-2_i386.deb Checksums-Sha256: 51b4c5da84b7760a24c4b352f9104e4ee3cea41eda77c92f84150c93960ceb6d 947 icon_9.4.3-2.dsc 32c1a9048b4f9688bf866c8dff29169f6edcd10b3bd327eaf9c6db00efbecf2a 12793 icon_9.4.3-2.diff.gz 04ab618182e6d3b9b59dd5fa750ce17c5776cf538f160e11b476011bc30eba1a 1407508 icon-ipl_9.4.3-2_all.deb 93ef62d3cb6da1ee505282815c3fefbd9f826f98f8c4a500f5265d670cfd4305 46834 icont_9.4.3-2_i386.deb 66736fd1cc10d7ad1c3ef4d02167a4ed102bec403df0eb851d589a186e28c8d8 164308 iconx_9.4.3-2_i386.deb 6dfcbe15f754d699e68af3899234932176fb1ec672458a6c19489bf57a54d993 1235542 iconc_9.4.3-2_i386.deb Files: c3ba4cdcae68f5eca55574d8f1803bc0 947 devel optional icon_9.4.3-2.dsc cf64af39b08a97015b57c03b0b5ae194 12793 devel optional icon_9.4
Bug#485956: FTBFS: uses chown inappropriately
On Jun 15, 2008, at 4:23 AM, Raphael Hertzog wrote: On Thu, 12 Jun 2008, Jon Marler wrote: If you use fakeroot to call dpkg-buildpackage, it works prefectly. Something is wrong with the way that dpkg-buildpackage is calling fakeroot. The chown calls work perfect, and you can build the package using a different syntax. There's nothing wrong in dpkg-buildpackage. The "build" target is called _without_ root rights. Only the clean and binary target are supposed to have root rights. However your build target depends on binary-src and binary-src contains the call "chown -R root.root $(TMPSRC)". You should arrange your build system to have the operations that require root to be called when debian/rules binary is called and not when debian/rules build is called. I've been digging around in this, and have found something extremely peculiar. This odd behavior only appears when trying to build release -45, but not -44. As far as I can tell, the differences between the two are very minor. I can't figure out what broke between -44 and -45 that has caused dpkg-buildpackage to fail. The rules file is the same in both releases, yet one builds and the other fails. Do you have any ideas why that might be? This bug is the last bug holding me back from uploading a new qmail- src for lenny. Any help you could provide would be appreciated. Cheers! Jon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: tagging 494215
Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.10.35 > tags 494215 fixed Bug#494215: libgdamm1.3: FTBFS: libtool: link: `/usr/lib/libct.la' is not a valid libtool archive Tags were: patch Tags added: fixed > 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: found 494215 in 1.2.4-1.1
Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.10.35 > found 494215 1.2.4-1.1 Bug#494215: libgdamm1.3: FTBFS: libtool: link: `/usr/lib/libct.la' is not a valid libtool archive Bug marked as found in version 1.2.4-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#495493: Deadlocks in fsdestroy() handling
Package: python-fuse Version: 1:0.2-pre3-6 Severity: serious Tags: patch Hi, python-fuse deadlocks whilst unmounting, causing the Python interpreter to remain in memory after the filesystem has been unmounted as well resulting in the fsdestroy() callback not being executed. This breaks AptFS, which attempts to remove downloaded packages in this callback - not executing it results in the user's download directory (not necessarily an automatically-cleaned directory) being filled up with files. A patch against the latest python-fuse Debian package is attached; it fixes the problem in my tests. Why I think this patch should be in Lenny: * Breaks other packages * One-line patch * Patch already committed and blessed by upstream[0] Regards, /Lamby [0] http://mercurial.creo.hu/repos/fuse-python-hg/index.cgi/rev/b8a0b93a5f38 -- Chris Lamb, UK [EMAIL PROTECTED] GPG: 0x634F9A20 diff -urNd python-fuse-0.2-pre3.orig/fuseparts/_fusemodule.c python-fuse-0.2-pre3/fuseparts/_fusemodule.c --- python-fuse-0.2-pre3.orig/fuseparts/_fusemodule.c 2008-08-18 00:12:17.0 +0100 +++ python-fuse-0.2-pre3/fuseparts/_fusemodule.c2008-08-18 00:12:50.0 +0100 @@ -896,6 +896,7 @@ save = PyEval_SaveThread(); err = fuse_loop_mt(f); PyEval_RestoreThread(save); + interp = NULL; #endif return(err); signature.asc Description: PGP signature
Bug#494215: marked as done (libgdamm1.3: FTBFS: libtool: link: `/usr/lib/libct.la' is not a valid libtool archive)
Your message dated Sun, 17 Aug 2008 23:32:43 + with message-id <[EMAIL PROTECTED]> and subject line Bug#494215: fixed in libgda2 1.2.4-1.2 has caused the Debian Bug report #494215, regarding libgdamm1.3: FTBFS: libtool: link: `/usr/lib/libct.la' is not a valid libtool archive 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.) -- 494215: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=494215 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems --- Begin Message --- Package: libgdamm1.3 Version: 1.3.7-1 Severity: serious User: [EMAIL PROTECTED] Usertags: qa-ftbfs-20080807 qa-ftbfs Justification: FTBFS on i386 Hi, During a rebuild of all packages in sid, your package failed to build on i386. Relevant part: > i486-linux-gnu-g++ -shared -nostdlib > /usr/lib/gcc/i486-linux-gnu/4.3.1/../../../../lib/crti.o > /usr/lib/gcc/i486-linux-gnu/4.3.1/crtbeginS.o .libs/client.o .libs/command.o > .libs/connection.o .libs/datamodel.o .libs/datasourceinfo.o .libs/error.o > .libs/fieldattributes.o .libs/serverprovider.o .libs/parameter.o > .libs/parameterlist.o .libs/providerinfo.o .libs/row.o .libs/transaction.o > .libs/value.o .libs/wrap_init.o .libs/init.o .libs/config.o > /usr/lib/libglibmm-2.4.so /usr/lib/libgobject-2.0.so /usr/lib/libsigc-2.0.so > /usr/lib/libgda-2.so /usr/lib/libglib-2.0.so /usr/lib/libxslt.so > /usr/lib/libxml2.so -L/usr/lib/gcc/i486-linux-gnu/4.3.1 > -L/usr/lib/gcc/i486-linux-gnu/4.3.1/../../../../lib -L/lib/../lib > -L/usr/lib/../lib -L/usr/lib/gcc/i486-linux-gnu/4.3.1/../../.. -lstdc++ -lm > -lc -lgcc_s /usr/lib/gcc/i486-linux-gnu/4.3.1/crtendS.o > /usr/lib/gcc/i486-linux-gnu/4.3.1/../../../../lib/crtn.o -Wl,-soname > -Wl,libgdamm-1.3.so.8 -o .libs/libgdamm-1.3.so.8.0.0 > (cd .libs && rm -f libgdamm-1.3.so.8 && ln -s libgdamm-1.3.so.8.0.0 > libgdamm-1.3.so.8) > (cd .libs && rm -f libgdamm-1.3.so && ln -s libgdamm-1.3.so.8.0.0 > libgdamm-1.3.so) > creating libgdamm-1.3.la > /bin/sed: can't read /usr/lib/libct.la: No such file or directory > libtool: link: `/usr/lib/libct.la' is not a valid libtool archive > make[5]: *** [libgdamm-1.3.la] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2008/08/07 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 --- --- Begin Message --- Source: libgda2 Source-Version: 1.2.4-1.2 We believe that the bug you reported is fixed in the latest version of libgda2, which is due to be installed in the Debian FTP archive: gda2-mysql_1.2.4-1.2_amd64.deb to pool/main/libg/libgda2/gda2-mysql_1.2.4-1.2_amd64.deb gda2-odbc_1.2.4-1.2_amd64.deb to pool/main/libg/libgda2/gda2-odbc_1.2.4-1.2_amd64.deb gda2-postgres_1.2.4-1.2_amd64.deb to pool/main/libg/libgda2/gda2-postgres_1.2.4-1.2_amd64.deb gda2-sqlite_1.2.4-1.2_amd64.deb to pool/main/libg/libgda2/gda2-sqlite_1.2.4-1.2_amd64.deb gda2-sybase_1.2.4-1.2_amd64.deb to pool/main/libg/libgda2/gda2-sybase_1.2.4-1.2_amd64.deb libgda2-3-dbg_1.2.4-1.2_amd64.deb to pool/main/libg/libgda2/libgda2-3-dbg_1.2.4-1.2_amd64.deb libgda2-3_1.2.4-1.2_amd64.deb to pool/main/libg/libgda2/libgda2-3_1.2.4-1.2_amd64.deb libgda2-bin_1.2.4-1.2_amd64.deb to pool/main/libg/libgda2/libgda2-bin_1.2.4-1.2_amd64.deb libgda2-common_1.2.4-1.2_all.deb to pool/main/libg/libgda2/libgda2-common_1.2.4-1.2_all.deb libgda2-dev_1.2.4-1.2_amd64.deb to pool/main/libg/libgda2/libgda2-dev_1.2.4-1.2_amd64.deb libgda2-doc_1.2.4-1.2_all.deb to pool/main/libg/libgda2/libgda2-doc_1.2.4-1.2_all.deb libgda2_1.2.4-1.2.diff.gz to pool/main/libg/libgda2/libgda2_1.2.4-1.2.diff.gz libgda2_1.2.4-1.2.dsc to pool/main/libg/libgda2/libgda2_1.2.4-1.2.dsc A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Steve Langasek <[EMAIL PROTECTED]> (supplier of updated libgda2 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the
Processed: Re: FTBFS: libtool: link: `/usr/lib/libct.la' is not a valid libtool archive
Processing commands for [EMAIL PROTECTED]: > tags 494215 patch Bug#494215: libgdamm1.3: FTBFS: libtool: link: `/usr/lib/libct.la' is not a valid libtool archive There were no tags set. Tags added: patch > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#494215: FTBFS: libtool: link: `/usr/lib/libct.la' is not a valid libtool archive
tags 494215 patch
thanks
On Wed, Aug 13, 2008 at 08:50:38PM +0300, Riku Voipio wrote:
> reassign 494215 libgda2-dev
> thanks
> The .la files of libgda2-dev refer to .la file but libgda2-dev has no
> depends freetds-dev. Alternatively /usr/lib/libct.la should be dropped from
> the .la files provided by libgda2-dev, but that might be trickier..
> This breaks building of libgdamm1.3, possibly others.
> grep libct.la /usr/lib/*.la
> /usr/lib/libgda-2.la:dependency_libs=' /usr/lib/libgdasql.la
> /usr/lib/libgobject-2.0.la /usr/lib/libgthread-2.0.la
> /usr/lib/libgmodule-2.0.la -ldl /usr/lib/libglib-2.0.la /usr/lib/libxslt.la
> /usr/lib/libxml2.la -lm /usr/lib/libxml2.la -L/usr/lib /usr/lib/libct.la -lrt'
> /usr/lib/libgda-report-2.la:dependency_libs=' /usr/lib/libgda-2.la
> /usr/lib/libgdasql.la /usr/lib/libgobject-2.0.la /usr/lib/libgthread-2.0.la
> /usr/lib/libgmodule-2.0.la -ldl /usr/lib/libglib-2.0.la /usr/lib/libxslt.la
> /usr/lib/libxml2.la -lm /usr/lib/libxml2.la -L/usr/lib /usr/lib/libct.la -lrt'
> /usr/lib/libgdasql.la:dependency_libs=' /usr/lib/libgobject-2.0.la
> /usr/lib/libgthread-2.0.la /usr/lib/libgmodule-2.0.la -ldl
> /usr/lib/libglib-2.0.la /usr/lib/libxslt.la /usr/lib/libxml2.la -lm
> /usr/lib/libxml2.la /usr/lib/libct.la -L/usr/lib -lrt'
I've prepared a follow-up NMU to correct this; the patch is attached, and
the NMU will be uploaded shortly.
Thanks,
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
Ubuntu Developerhttp://www.debian.org/
[EMAIL PROTECTED] [EMAIL PROTECTED]
diff -u libgda2-1.2.4/debian/control libgda2-1.2.4/debian/control
--- libgda2-1.2.4/debian/control
+++ libgda2-1.2.4/debian/control
@@ -64,7 +64,7 @@
Package: libgda2-dev
Section: libdevel
Architecture: any
-Depends: libgda2-3 (= ${binary:Version}), libglib2.0-dev (>= 2.2.0), libxslt1-dev, ${misc:Depends}
+Depends: libgda2-3 (= ${binary:Version}), libglib2.0-dev (>= 2.2.0), libxslt1-dev, freetds-dev, ${misc:Depends}
Suggests: libgda2-doc
Description: Development files for GNOME Data Access library for GNOME2
GNOME Data Access is an attempt to provide uniform access to
diff -u libgda2-1.2.4/debian/changelog libgda2-1.2.4/debian/changelog
--- libgda2-1.2.4/debian/changelog
+++ libgda2-1.2.4/debian/changelog
@@ -1,3 +1,11 @@
+libgda2 (1.2.4-1.2) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * libgda2-dev needs to depend now on freetds-dev, due to the switch
+from libtds to libct for which we ship a .la file. Closes: #494215.
+
+ -- Steve Langasek <[EMAIL PROTECTED]> Sun, 17 Aug 2008 16:10:05 -0700
+
libgda2 (1.2.4-1.1) unstable; urgency=high
* Non-maintainer upload with maintainer's approval.
diff -u libgda2-1.2.4/debian/control.in libgda2-1.2.4/debian/control.in
--- libgda2-1.2.4/debian/control.in
+++ libgda2-1.2.4/debian/control.in
@@ -64,7 +64,7 @@
Package: libgda2-dev
Section: libdevel
Architecture: any
-Depends: [EMAIL PROTECTED]@ (= ${binary:Version}), libglib2.0-dev (>= 2.2.0), libxslt1-dev, ${misc:Depends}
+Depends: [EMAIL PROTECTED]@ (= ${binary:Version}), libglib2.0-dev (>= 2.2.0), libxslt1-dev, freetds-dev, ${misc:Depends}
Suggests: libgda2-doc
Description: Development files for GNOME Data Access library for GNOME2
GNOME Data Access is an attempt to provide uniform access to
Bug#495122: fixed NMU
I somehow screwed up on that NMU: * it doesn't have the right version: 5.9-1~lenny1 < 5.9-1 * it included the _orig source, which caused a REJECT notice from ries * it didn't include the magic NMU string in the changelog * it didn't include a "Closes" statement with this bug # I just fixed those things in a new upload here: http://debian.koumbit.net/debian/dists/testing-security/main/source/web/drupal5_5.9-1.1%2blenny1.dsc I hope that works for you guys. Thanks, a. -- Antoine Beaupré Réseau Koumbit Networks +1.514.387.6262 signature.asc Description: Digital signature
Bug#495446: marked as done (simutrans: Simutrans doesn't work on mips)
Your message dated Mon, 18 Aug 2008 00:15:08 +0200 with message-id <[EMAIL PROTECTED]> and subject line Re: Bug#495446: simutrans: Simutrans doesn't work on mips has caused the Debian Bug report #495446, regarding simutrans: Simutrans doesn't work on mips 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.) -- 495446: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=495446 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems --- Begin Message --- Package: simutrans Version: 100.0+ds1-2 Severity: serious The version in Debian fails to start: Reading low level config data ... Initializing tombstones ... Reading simuconf.tab successful! Preparing display ... Screen Flags: requested=10, actual=10 Loading font 'font/prop.fnt' font/prop.fnt sucessfully loaded as old format prop font! Init done. Initializing tombstones ... Reading simuconf.tab successful! Reading city configuration ... Reading speedbonus configuration ... Reading forest configuration ... Reading object data from pak/... FATAL ERROR: alles_geladen() 12ware_besch_t-object Passagiere not found. *** PLEASE INSTALL PROPER BASE FILE AND CHECK PATH *** If I recompile with BIG_ENDIAN defined, it segfaults. I'll need to recompile with debug info to get a backtrace. --- End Message --- --- Begin Message --- Version: 100.0+ds1-2 Closing bug because submitter cannot reproduce the problem. -- PGP: 1024D/595FAD19 739E 2D09 0969 BEA9 9797 B055 DDB0 2FF7 595F AD19 --- End Message ---
Bug#495489: ga function tests not passed
Package: octave-ga
Version: 0.1.1-1
Severity: serious
The svn version in Debian repository (0.1.1) doesn't work.
In fact the tests of the ga function are not passed because of bad
array indices.
Here is how to reproduce this bug.
$ echo test ga | octave -q
* assert (ga (@test_4_variabili, 4, gaoptimset ('FitnessLimit',
0.001, 'PopInitRange', [-1; 1])), [0, 0, 0, 0], sqrt(0.001))
! test failed
error: A(IDX-LIST) = X: X must be a scalar or size of X must equal
number of elements indexed by IDX-LIST
Please upgrade to the latest svn version of the package
(http://octave.svn.sourceforge.net/viewvc/octave/trunk/octave-forge/main/ga.tar.gz?view=tar).
It fixes this bug and is in general better shape.
I'm using Debian GNU/Linux "Lenny" x86 32 bit.
Thanks,
Luca Favatella
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#494356: marked as done (glibc detected *** python2.5: malloc(): memory corruption)
Your message dated Sun, 17 Aug 2008 23:46:59 +0200 with message-id <[EMAIL PROTECTED]> and subject line Fixed by binNMU has caused the Debian Bug report #494356, regarding glibc detected *** python2.5: malloc(): memory corruption 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.) -- 494356: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=494356 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems --- Begin Message --- Package: parsedatetime Severity: serious parsedatetime FTBFS with python 2.5 [1] while running tests if python-pyicu [2] package is installed. Partial build log: --- running build_py set -e ;\ for py in python2.4 python2.5; do \ PYTHONPATH=/home/cgalisteo/kk/parsedatetime/parsedatetime-0.8.6/build/lib $py run_tests.py parsedatetime; \ done . -- Ran 41 tests in 0.084s OK *** glibc detected *** python2.5: malloc(): memory corruption: 0x407e67f0 *** If I launch the command by hand: PYTHONPATH=/home/cgalisteo/kk/parsedatetime/parsedatetime-0.8.6/build/lib python2.4 run_tests.py parsedatetime . -- Ran 41 tests in 0.083s OK PYTHONPATH=/home/cgalisteo/kk/parsedatetime/parsedatetime-0.8.6/build/lib python2.5 run_tests.py parsedatetime .*** glibc detected *** python2.5: malloc(): memory corruption: 0xb78927f0 *** Purging python-pyicu, makes the package to build again (except for #485054). [1] tested with 2.5.2-10 and 2.5.2-6 [2] python-pyicu_0.8.1-2 -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.26-1-686 (SMP w/2 CPU cores) Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- --- Carlos Galisteo PGP_key::http://k-rolus.net/~cgalisteo/cgalisteo.gpg Key_Fingerprint::F888 6FBA 9145 B5A2 C187 66D6 5B8C 027A 69AD BE65 --- --- End Message --- --- Begin Message --- Version: 0.8.1-2+b1 Not sure where this bug comes from, but a binNMU fixes it. BinNMUs were scheduled and are allready uploaded on most arches, so I'm closing the bug. -- Bernd Zeimetz Debian GNU/Linux Developer GPG Fingerprint: 06C8 C9A2 EAAD E37E 5B2C BE93 067A AD04 C93B FF79 --- End Message ---
Bug#494719: marked as done (kernel-patch-badram: Doesn't apply to Lenny release kernek)
Your message dated Sun, 17 Aug 2008 21:17:33 + with message-id <[EMAIL PROTECTED]> and subject line Bug#494719: fixed in kernel-patch-badram 2.6.23.1-1.1 has caused the Debian Bug report #494719, regarding kernel-patch-badram: Doesn't apply to Lenny release kernek 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.) -- 494719: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=494719 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems --- Begin Message --- Package: kernel-patch-badram Severity: grave Justification: renders package unusable kernel-patch-badram is only available for kernels up to 2.6.23 and doesn't apply against later kernels due to the x86 arch unification. It should be updated to 2.6.26. Cheers, Moritz -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.26-1-686 (SMP w/1 CPU core) Locale: LANG=C, [EMAIL PROTECTED] (charmap=ISO-8859-15) Shell: /bin/sh linked to /bin/bash --- End Message --- --- Begin Message --- Source: kernel-patch-badram Source-Version: 2.6.23.1-1.1 We believe that the bug you reported is fixed in the latest version of kernel-patch-badram, which is due to be installed in the Debian FTP archive: kernel-patch-badram_2.6.23.1-1.1.dsc to pool/main/k/kernel-patch-badram/kernel-patch-badram_2.6.23.1-1.1.dsc kernel-patch-badram_2.6.23.1-1.1.tar.gz to pool/main/k/kernel-patch-badram/kernel-patch-badram_2.6.23.1-1.1.tar.gz kernel-patch-badram_2.6.23.1-1.1_all.deb to pool/main/k/kernel-patch-badram/kernel-patch-badram_2.6.23.1-1.1_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. Moritz Muehlenhoff <[EMAIL PROTECTED]> (supplier of updated kernel-patch-badram 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: Sun, 17 Aug 2008 21:58:38 +0200 Source: kernel-patch-badram Binary: kernel-patch-badram Architecture: source all Version: 2.6.23.1-1.1 Distribution: unstable Urgency: low Maintainer: Yann Dirson <[EMAIL PROTECTED]> Changed-By: Moritz Muehlenhoff <[EMAIL PROTECTED]> Description: kernel-patch-badram - Kernel patch allowing to use partly-bad RAM modules Closes: 494719 Changes: kernel-patch-badram (2.6.23.1-1.1) unstable; urgency=low . * Non-maintainer upload. * Add a patch for 2.6.26 (Closes: #494719) Checksums-Sha1: 8f1640d73af68f678777cc9ebc7b3064b350f795 824 kernel-patch-badram_2.6.23.1-1.1.dsc f5c7af1104dfe667563a9368a31be3dfd6a6724a 69204 kernel-patch-badram_2.6.23.1-1.1.tar.gz 0db8c72b5897c19e7d26a3b65d268cb437f61a92 72950 kernel-patch-badram_2.6.23.1-1.1_all.deb Checksums-Sha256: 2a4734b73d4d13b8c44e18b7f332ef466b1e256c20c259b63abbccc3ca6bb273 824 kernel-patch-badram_2.6.23.1-1.1.dsc 832b94bca065ff7e37989910914ac72c38c5f14ab8d6dc20e256bba7a8ac8ea9 69204 kernel-patch-badram_2.6.23.1-1.1.tar.gz 3d50b31357c4af80664f902aacc6d078d6bc419be3b18bcc6b2a11e1f54f8a3f 72950 kernel-patch-badram_2.6.23.1-1.1_all.deb Files: 4e4b908bec0f470661dee9e0822947ed 824 devel extra kernel-patch-badram_2.6.23.1-1.1.dsc 8fa8d167780da4b2b5cc814b750a3522 69204 devel extra kernel-patch-badram_2.6.23.1-1.1.tar.gz 3a1af702771d6a04ecad7467482f359e 72950 devel extra kernel-patch-badram_2.6.23.1-1.1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkiogygACgkQXm3vHE4uylpXCgCg1/tEa4Mvij/VFGYKijz1s8MX gH4An1wF36Lz55rlZW3/yj0hiySBtSIi =luCr -END PGP SIGNATURE- --- End Message ---
Bug#488924: dspam-webfrontend and apache2-suexec
On Fri, Aug 15 2008, Stefan Fritsch wrote: > Lenny is frozen, the release team will never accept so many changes to > go into Lenny. This means there are two ways forward: > > - Downgrade #488924 to non-RC severity, stay with 3.6.8-8.1 in Lenny, > go ahead with your upload that changes lots of things. > > - Upload a new version with minimal changes fixing #488924 and > possibly some other important bugs. Wait for this new version to > migrate to lenny and delay the upload with big changes until later. > > I recommend the second option, but this is not a strong opinion. Even > with the first option, it would make sense to delay the big upload, > in order to be sure that no newer version is required in lenny. I understand your feeling about this. However, I think you might be overly pessimistic, because the changes aren't as extreme as they might seem to be when looking at the changelog. I'm setting aside the changes to the webfrontend for a moment; I'll get back to them below. I began with changes to pass the standard Debian flags to configure and to build in the source tree instead of in a subdir. I did this so the Makefiles would be available when running maintainer-clean to remove the auto-generated files resulting from autoconf. This produces a much cleaner .diff.gz, which now only contains entries from .../debian and its subdirectories, which is a goal when dpatch is used. This step was verified with interdiff. Fixing #481755 and #483868 involved one word changes to fix important regressions. I think that inspecting the changes will show them to be non-problematic. Updating to compatibility level 7 and Standards 3.8.0 introduced no additional changes. Adding amavis to the trusted users is a one word change to a config file, and non-disruptive by inspection. There were several changes to improve the documentation, and that's allowable per the Lenny freeze guidelines. Now, the webfrontend: Previously, we had a non-functional demo VirtualHost fragment. I moved it to its correct location in /etc/dspam/ and modified it to be served on localhost only, with a simplified login using htpasswd. I also moved other files that the user might be expected to customize. Having a working website following installation should help those users who were having difficulty getting started with the webfrontend configuration. I tested this by running the website. There was an issue with upgrading etch: the /usr/share/dspam dir had some symlinks which were causing upgrade errors. This is a serious bug, at least, and had to be fixed. Since it's important for security reasons that the cgi run under suexec as user dspam, I think setting a dependency on apache2-suexec is appropriate, and fixes this RC bug. My original goal was to get all the webfrontend files out of /var/www. That would need apache2-suexec-custom. I wasn't successful. But it was time to stop! One of the Lenny goals is to pass the piuparts test. The webfrontend was not purging correcty, and I made some changes to fix that. The changes were most cleanly accomplished by putting the webfrontend config files under ucf control. There were no changes to the core of dspam or the webfrontend, so I don't think any of the above could be considered disruptive. Again, thanks for the review. I hope this addresses your concerns. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#493573: Backtrace on 'hung' apache2 (while trying to stop service)
On Saturday 16 August 2008, you wrote: > Stefan Fritsch wrote: > > On Friday 15 August 2008, Chris Horn wrote: > >> To re-create normal situation: > >> 1. /etc/init.d/apache2 start > >> 2. /etc/init.d/apache2 stop > >> 3. apache2 is now hung > > > > Does this happen for you always or only sometimes? Does it only > > happen after apache processed some requests? I cannot reproduce > > it. > > This happens always for me. Could it be my site configuration? I > recently migrated from 1.3. Maybe, but I have not idea what configuration could influence this behaviour. I used your list of loaded apache modules and still can't reproduce it. Does it happen even if you start apache and stop it again without having processed any request? What version of libmysqlclient15off do you have installed? Your apt-configuration says "stable". Do you use stable with some testing packages? What php extensions do you have installed besides php5-mysql? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#495446: simutrans: Simutrans doesn't work on mips
I can't reproduce this segfault. So it will probably be OK if recompiled with my patches for #493409. Sorry for the noise. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#495484: blobwars: Contains non-free sound and music
Package: blobwars Version: 1.08-1 Severity: serious The music and sounds in Blobwars are taken from various "free" online repositories, which allow distribution and non-commercial use at the minimum, but not necessarily DFSG-free. Some sounds and music files may be in the public domain, but this is not clear yet. The sounds and music should be split into a blobwars-data-nonfree package. (I'm reporting this bug to prevent blobwars from getting released with lenny before this is fixed.) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#495478: nvidia-glx-ia32: Contains no actual 32-bit GL libraries
Package: nvidia-glx-ia32 Version: 173.14.09-3 Severity: grave As the subject says: the nvidia-glx-ia32 package contains links to libGL.so.173.14.09 in /emul/ia32-linux/usr/lib, but no actual file with this name. That makes the package completely useless, since it means 32-bit binaries linked to OpenGL still won't run. [EMAIL PROTECTED]:~/src/debian/nonfree/nvidia-graphics-drivers$ dpkg-deb -c nvidia-glx-ia32_173.14.09-3_amd64.deb drwxr-xr-x root/root 0 2008-07-24 20:57 ./ drwxr-xr-x root/root 0 2008-07-24 20:57 ./usr/ drwxr-xr-x root/root 0 2008-07-24 20:57 ./usr/share/ drwxr-xr-x root/root 0 2008-07-24 20:57 ./usr/share/doc/ drwxr-xr-x root/root 0 2008-07-24 20:57 ./usr/share/doc/nvidia-glx-ia32/ -rw-r--r-- root/root 7906 2008-07-24 20:57 ./usr/share/doc/nvidia-glx-ia32/copyright -rw-r--r-- root/root 8013 2008-07-24 20:56 ./usr/share/doc/nvidia-glx-ia32/changelog.Debian.gz drwxr-xr-x root/root 0 2008-07-24 20:57 ./emul/ drwxr-xr-x root/root 0 2008-07-24 20:57 ./emul/ia32-linux/ drwxr-xr-x root/root 0 2008-07-24 20:57 ./emul/ia32-linux/usr/ drwxr-xr-x root/root 0 2008-07-24 20:57 ./emul/ia32-linux/usr/lib/ drwxr-xr-x root/root 0 2008-07-24 20:57 ./emul/ia32-linux/usr/lib/tls/ lrwxrwxrwx root/root 0 2008-07-24 20:57 ./emul/ia32-linux/usr/lib/libGLcore.so -> libGLcore.so.173.14.09 lrwxrwxrwx root/root 0 2008-07-24 20:57 ./emul/ia32-linux/usr/lib/libcuda.so -> libcuda.so.173.14.09 lrwxrwxrwx root/root 0 2008-07-24 20:57 ./emul/ia32-linux/usr/lib/libGL.so.1 -> libGL.so.173.14.09 lrwxrwxrwx root/root 0 2008-07-24 20:57 ./emul/ia32-linux/usr/lib/libnvidia-tls.so.1 -> libnvidia-tls.so.173.14.09 lrwxrwxrwx root/root 0 2008-07-24 20:57 ./emul/ia32-linux/usr/lib/libGL.so -> libGL.so.173.14.09 -- Daniel Schepler -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: setting package to simutrans-makeobj, tagging 493409
Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.10.35 > package simutrans-makeobj Ignoring bugs not assigned to: simutrans-makeobj > tags 493409 + patch Bug#493409: simutrans-makeobj: [amd64] makeobj fails There were no tags set. Tags added: patch > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#494514: insserv: Test suite fail on alpha
I can't reproduce this on my alpha here. So this may be a problem with how goetz is set up, rather than a general alpha problem. I've given insserv back on alpha to see whether it's reproducible or if this was a fluke, but goetz is the only buildd that I see alive for alpha currently, so if it fails again then I think we need to find a sourceful fix (or figure out what's wrong with the buildd) for release. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developerhttp://www.debian.org/ [EMAIL PROTECTED] [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#495474: [kmid] kmid doesn't play any sound
Package: kmid Version: 4:3.5.9-3 Severity: serious --- Please enter the report below this line. --- Dear Developers, I'm unable to play midi files using kmid while rosegarden works flawlessy. I have a cheap integrated soundcard (Intel HDA) and so I'm pushed to use fluyidsinth or timidity as software synthesyzer. I'm not completely sure that's all fault of kmid, because using an older kernel (2.6.24.7) that has a different configuration of output channels in alsa, I can play midi's with kmid. Sorry for this poor bugreport, but I don't have any clue about it. Midi playing has always been a nightmare in Linux :) Ciao Valerio --- System information. --- Architecture: amd64 Kernel: Linux 2.6.26.2 Debian Release: lenny/sid 500 unstablewww.debian-multimedia.org 500 unstablemirrors.ecology.uni-kiel.de 500 unstablemi.mirror.garr.it 500 unstabledebian.fastweb.it 500 testing mi.mirror.garr.it 500 stable security.debian.org 500 stable mi.mirror.garr.it --- Package information. --- Depends (Version) | Installed =-+-== kdelibs4c2a (>= 4:3.5.9) | 4:3.5.9.dfsg.1-6 libc6 (>= 2.7-1) | 2.7-13 libgcc1 (>= 1:4.1.1) | 1:4.3.1-9 libqt3-mt (>= 3:3.3.8b) | 3:3.3.8b-5 libstdc++6 (>= 4.1.1) | 4.3.1-9 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#495149: marked as done (spass FTBFS when built with sudo)
Your message dated Sun, 17 Aug 2008 17:17:09 + with message-id <[EMAIL PROTECTED]> and subject line Bug#495149: fixed in spass 2.1-4 has caused the Debian Bug report #495149, regarding spass FTBFS when built with sudo 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.) -- 495149: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=495149 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems --- Begin Message --- Package: spass Version: 2.1-3 Severity: serious Tags: patch spass fails to build when using dpkg-buildpackage -rsudo because in this case $(PWD) isn't set as a make variable in debian/rules. The appended patch fixes this. Thiemo --- spass-2.1.orig/debian/rules 2008-08-14 22:35:04.0 +0200 +++ spass-2.1/debian/rules 2008-08-14 22:09:41.0 +0200 @@ -20,7 +20,7 @@ endif # generic Debian directories -DEB_BASE_DIR = $(PWD) +DEB_BASE_DIR = $(shell pwd) DEB_DEBIAN_DIR = $(DEB_BASE_DIR)/debian DEB_SOURCE_DIR = $(DEB_BASE_DIR)/SPASS-2.1 DEB_BUILD_DIR = $(DEB_DEBIAN_DIR)/build --- End Message --- --- Begin Message --- Source: spass Source-Version: 2.1-4 We believe that the bug you reported is fixed in the latest version of spass, which is due to be installed in the Debian FTP archive: spass_2.1-4.diff.gz to pool/main/s/spass/spass_2.1-4.diff.gz spass_2.1-4.dsc to pool/main/s/spass/spass_2.1-4.dsc spass_2.1-4_i386.deb to pool/main/s/spass/spass_2.1-4_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. Roland Stigge <[EMAIL PROTECTED]> (supplier of updated spass 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: Sun, 17 Aug 2008 18:05:44 +0200 Source: spass Binary: spass Architecture: source i386 Version: 2.1-4 Distribution: unstable Urgency: low Maintainer: Roland Stigge <[EMAIL PROTECTED]> Changed-By: Roland Stigge <[EMAIL PROTECTED]> Description: spass - An automated theorem prover for first-order logic with equality Closes: 495149 Changes: spass (2.1-4) unstable; urgency=low . * debian/rules: Removed DEB_BASE_DIR (Closes: #495149) * debian/control: Standards-Version: 3.8.0 * debian/compat: 7 Checksums-Sha1: b28401c5096d93cb6c21edecc16470b15edfd059 909 spass_2.1-4.dsc 2ad2db8b890410180b3c46ea929ea91783c15c17 14188 spass_2.1-4.diff.gz e2c4c3fe2a2f5bb92118de1db2de5c5c5219f72e 1292244 spass_2.1-4_i386.deb Checksums-Sha256: cc8914bc3242d047582cba2dad59aa821fa398b9cc00dc0766062ac25e42bfb7 909 spass_2.1-4.dsc 5d5ff6eee92ebfcf8c2c5d902bdb43ff9e289bed0a2fe6721af40e72972c0fe3 14188 spass_2.1-4.diff.gz 34b0db10d71b10ba068b0ba063a2a6d9918c0d1db6305515e15a07c8a26055e6 1292244 spass_2.1-4_i386.deb Files: e37190accc23ab998fc1f0e663eb6c09 909 science optional spass_2.1-4.dsc 2d269ea1020b1fc9fd8b41f26f7fbca2 14188 science optional spass_2.1-4.diff.gz 988b25a81d90f435ce2b94826f038692 1292244 science optional spass_2.1-4_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iD8DBQFIqFB7caH/YBv43g8RAkX7AJ92z5pSj7V8NorpbzicrMYJiL9MZgCeJlP8 RapWNswvmPMo2G0dSdCAGV4= =+WC0 -END PGP SIGNATURE- --- End Message ---
Bug#468954: upgrading from mozilla-enigmail in Sarge
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 when replacing mozilla-enigmail with testing's enigmail you should include in the preinstall script a test for obsolete enigmail packages and purge them rather than just remove or replace them. I found that I had to first dpkg --purge mozilla-enigmail prior to installing enigmail which actually removes the old enigmail from icedove before installing the new version. - -- Rev. LeRoy D. Cressy mailto:[EMAIL PROTECTED] /\_/\ http://lrcressy.com( o.o ) Phone: 215-535-4037> ^ < gpg fingerprint: 62DE 6CAB CEE1 B1B3 359A 81D8 3FEF E6DA 8501 AFEA For info on enigmail:http://lrcressy.com/linux/mozilla.pdf For info on gpg: http://www.gnupg.org/ Jesus saith unto him, I am the way, the truth, and the life: no man cometh unto the Father, but by me. (John 14:6) -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQIVAwUBSKhX93lsxrSGsIsqAQjPag/+MclJZInaARQSb0rwcHc/DbVp5BnyU8QL iW7V3Bng2iw27dqsbEow/IysJ+vzbyZ5PJSKjBtqaK7GB+hxEbe9grva0n5XDcri mogyz/R9LbFS71FcNUjU1KtDF+WTHbqcocGeHxUEZnfUc2zb0xzntHfzN3JaqiBi iGg22VeLaZokCfDEeAA983hoerzrUyD8b8n5Z1Uz1FNMTxpQYT8VDnNQ8dkTFVrJ 53kTWg9E1cAhMfm9cQIuAosCSkOxeIN0iseiuGcK7s1Zub+LfRFogNx0PxZkRpP6 W995h0XshsYIfBw2hRd6I+bqYipDS2I2pCImFbpwMkzkci8AFEhylDXP15p23/l0 YzrV1eGPElY5WI6/7It5Zb3GzGFU28aCW7XwIYoGE0pS8VobY/gTpv0gePh2L500 h4fy9tqsJt4GEbJk5mRFgGDfQbzrwsfX50haI4sBKJ/C3cRb9PjwSz9+7Hn+Xl68 HrHmH7q6WYdhyyTIsX/jH1RHY8N4tIG9MJ3B8pLM/AO4amyV38TfiJDf3Ae5QiKR zLfn/R4AXE2LNEUYzopz4+hlblJV3rQamphLnPPUQ3N7fkEBfjCLld1fBYbwORf2 ninpM9KaO5FGrzjm3gZ2e9uEOHFc1z/Vv6LEk4G/2sp1vNWdFgDnqiCTtYpmnIr6 7+C6nOAI7oo= =VUe2 -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#451303: marked as done (exaile: Exaile downloads and executes remote code)
Your message dated Sun, 17 Aug 2008 16:32:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#451303: fixed in exaile 0.2.11.1+debian-2 has caused the Debian Bug report #451303, regarding exaile: Exaile downloads and executes remote code 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.) -- 451303: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=451303 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems --- Begin Message --- Package: exaile Version: 0.2.10+debian-1.1 Severity: important *** Please type your report below this line *** The version of exaile in sid and lenny both contain plugin management code which basically boils down to: wget http://www.exaile.org/plugins/plugins.py?version=%s&plugin=%s chmod 755 plugin ./plugin In short they allow anybody with control over DNS to execute arbitrary python code on your machine - either if you decide to enable a new plugin, or if you have a plugin installed and use the 'version checking' to automatically download a new version of something you've got installed. I'd, personally, love to see this code replaced with something more sane such as a exaile-plugins package which could use a local collection of plugins. As the package isn't in Etch I'll leave it at this report rather than raising a security bug. But comments definitely welcome. Steve -- # Kink-Friendly Dating http://ctrl-alt-date.com/ -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.18.8-xen (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages exaile depends on: ii gstreamer0.10-alsa 0.10.14-4 GStreamer plugin for ALSA ii gstreamer0.10-esd0.10.6-3GStreamer plugin for ESD ii gstreamer0.10-plugins-base 0.10.14-4 GStreamer plugins from the "base" ii gstreamer0.10-plugins-good 0.10.6-3GStreamer plugins from the "good" ii libatk1.0-0 1.20.0-1The ATK accessibility toolkit ii libc62.6.1-6 GNU C Library: Shared libraries ii libcairo21.4.10-1+b2 The Cairo 2D vector graphics libra ii libfontconfig1 2.4.91-1generic font configuration library ii libglib2.0-0 2.14.3-1The GLib library of C routines ii libgstreamer0.10-0 0.10.14-2 Core GStreamer libraries and eleme ii libgtk2.0-0 2.12.1-2The GTK+ graphical user interface ii libpango1.0-01.18.3-1Layout and rendering of internatio ii libx11-6 2:1.0.3-7 X11 client-side library ii libxcursor1 1:1.1.9-1 X cursor management library ii libxext6 1:1.0.3-2 X11 miscellaneous extension librar ii libxfixes3 1:4.0.3-2 X11 miscellaneous 'fixes' extensio ii libxi6 2:1.1.3-1 X11 Input extension library ii libxinerama1 1:1.0.2-1 X11 Xinerama extension library ii libxrandr2 2:1.2.2-1 X11 RandR extension library ii libxrender1 1:0.9.4-1 X Rendering Extension client libra ii python 2.4.4-6 An interactive high-level object-o ii python-dbus 0.82.3-1simple interprocess messaging syst ii python-elementtree 1.2.6-11Light-weight toolkit for XML proce ii python-glade22.12.0-1GTK+ bindings: Glade support ii python-gst0.10 0.10.8-1generic media-playing framework (P ii python-gtk2 2.12.0-1Python bindings for the GTK+ widge ii python-mutagen 1.11-1 audio metadata editing library ii python-pysqlite2 2.3.5-1 python interface to SQLite 3 ii python-pyvorbis 1.3-1.2 A Python interface to the Ogg Vorb ii python-support 0.7.5 automated rebuilding support for p Versions of packages exaile recommends: ii gstreamer0.10-plugins-ugly0.10.6-2 GStreamer plugins from the "ugly" pn python-cddb(no description available) pn python-gamin (no description available) pn python-gnome2-extras (no description available) pn python-gpod(no description available) pn python-notify (no description available) pn streamripper (no description available) -- no debconf in
Bug#494517: marked as done (prayer: username hard-coded to only eight characters)
Your message dated Sun, 17 Aug 2008 15:47:08 + with message-id <[EMAIL PROTECTED]> and subject line Bug#494517: fixed in prayer 1.2.2.1-4 has caused the Debian Bug report #494517, regarding prayer: username hard-coded to only eight characters 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.) -- 494517: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=494517 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems --- Begin Message --- Package: prayer Version: 1.2.0-1 Severity: important This makes prayer completely unusable on a mail server requiring a complete e-mail address for valid usernames. -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.18-53.1.13.el5xen (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages prayer depends on: ii adduser3.108 add and remove users and groups ii libc-client20077:2007~dfsg-1 UW c-client library for mail proto ii libc6 2.7-10GNU C Library: Shared libraries ii libdb4.6 4.6.21-8 Berkeley v4.6 Database Libraries [ ii libldap-2.4-2 2.4.10-2+lenny1 OpenLDAP libraries ii libssl0.9.80.9.8g-10.1 SSL shared libraries ii zlib1g 1:1.2.3.3.dfsg-12 compression library - runtime prayer recommends no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: prayer Source-Version: 1.2.2.1-4 We believe that the bug you reported is fixed in the latest version of prayer, which is due to be installed in the Debian FTP archive: prayer-accountd_1.2.2.1-4_i386.deb to pool/main/p/prayer/prayer-accountd_1.2.2.1-4_i386.deb prayer_1.2.2.1-4.diff.gz to pool/main/p/prayer/prayer_1.2.2.1-4.diff.gz prayer_1.2.2.1-4.dsc to pool/main/p/prayer/prayer_1.2.2.1-4.dsc prayer_1.2.2.1-4_i386.deb to pool/main/p/prayer/prayer_1.2.2.1-4_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. Magnus Holmgren <[EMAIL PROTECTED]> (supplier of updated prayer 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: Sun, 17 Aug 2008 17:38:00 +0200 Source: prayer Binary: prayer prayer-accountd Architecture: source i386 Version: 1.2.2.1-4 Distribution: unstable Urgency: medium Maintainer: Magnus Holmgren <[EMAIL PROTECTED]> Changed-By: Magnus Holmgren <[EMAIL PROTECTED]> Description: prayer - Standalone IMAP-based webmail server prayer-accountd - account management daemon for Prayer Closes: 494517 Changes: prayer (1.2.2.1-4) unstable; urgency=medium . * Urgency medium since fixing fairly serious bug(s). * debian/Config: Fix handling of CFLAGS, CPPFLAGS and LDFLAGS from the environment or command line, breaking a circular definition of LDFLAGS (FTBFS on Ubuntu; LP: #256220). * unlimit_login_username.patch (new): - servers/prayer_login.c: Remove 8 character username limit from login form (Closes: #494517). * prayer.init, prayer-accountd.init: Sleep 1 second between stop and start in restart. * Add manpages prayer(8), prayer-session(8), prayer.cf(5), and prayer-ssl-prune(8) (groff-mdoc format). Remove half-done Docbook versions from source package. Checksums-Sha1: a10829f1889b671155c3480b9522d592264deb13 1262 prayer_1.2.2.1-4.dsc d4ee10f061cfb9829717f488037f4cc9fa749784 29436 prayer_1.2.2.1-4.diff.gz 895119755380e911e36b650abc5560343ee8f6bc 706792 prayer_1.2.2.1-4_i386.deb 993c7dbe14411e238d1774719fbed86ba4e6a92e 101716 prayer-accountd_1.2.2.1-4_i386.deb Checksums-Sha256: 295d13286cc32f80d6b3640e716557e49fdcc796dea806460c2b53ea85e327bd 1262 prayer_1.2.2.1-4.dsc 02c03e9946a431a2972e7203847b18b67cf4e66954266dfe83b51391c3cbad20 29436 prayer_1.2.2.1-4.diff.gz f057d55d77ce0758c30bba422a717f2ab4641064cb877dd44faa4deecdf0e840 706792 prayer_1.2.2.1-4_i386.deb 2fc806f2f6f354f0737388de78a047e9ca1346b44ef4cee8c47b3441c9cf4423 101716 prayer-accountd_1.2.2.1-4_i386.deb Files: 972ccf996b49bf30e441334ae8f84b17 1262 mail optional prayer_1.2.2.1-4.
Bug#488696: Fixing 488696
On Sunday 17 August 2008 04:00:47 Gudjon I. Gudjonsson wrote: > > Another problem I noticed is that something (not sure whether m-a or > > comedi) uses depmod when building comedi-modules. module-init-tools > > (which contains depmod) is not pulled in by any dependency. Please > > investigate, and if it is comedi which needs depmod, we'll need to add > > a dependency on module-init-tools. > > You are right thanks. Comedi checks for the existence of depmod in the > configure script. I have added dependency on module-init-tools in version > 0.7.76+20080817cvs-1. I just uploaded comedi 0.7.76+20080817cvs-1 as it seems to build fine here now on 2.6.25. I haven't tried it on 2.6.26, though. BTW, lintian on the build modules *deb gives: W: comedi-modules-2.6.25-2-686: description-synopsis-might-not-be-phrased-properly N: N: The synopsis (first line in the package "Description:" field, the N: short description) ends with a full stop "." character. This is not N: necessary, as the synopsis doesn't need to be a full sentence. It is N: recommended that a descriptive phrase is used instead. N: N: Note also that the synopsis is not part of the rest of the N: "Description:" field. N: N: Refer to Policy Manual, section 3.4.1 for details. N: Very trivial issue, but you might want to fix sometime. -- Wesley J. Landaker <[EMAIL PROTECTED]> OpenPGP FP: 4135 2A3B 4726 ACC5 9094 0097 F0A9 8A4C 4CD6 E3D2 signature.asc Description: This is a digitally signed message part.
Bug#495446: simutrans: Simutrans doesn't work on mips
Package: simutrans Version: 100.0+ds1-2 Severity: serious The version in Debian fails to start: Reading low level config data ... Initializing tombstones ... Reading simuconf.tab successful! Preparing display ... Screen Flags: requested=10, actual=10 Loading font 'font/prop.fnt' font/prop.fnt sucessfully loaded as old format prop font! Init done. Initializing tombstones ... Reading simuconf.tab successful! Reading city configuration ... Reading speedbonus configuration ... Reading forest configuration ... Reading object data from pak/... FATAL ERROR: alles_geladen() 12ware_besch_t-object Passagiere not found. *** PLEASE INSTALL PROPER BASE FILE AND CHECK PATH *** If I recompile with BIG_ENDIAN defined, it segfaults. I'll need to recompile with debug info to get a backtrace. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#448717: Done
On Sat, Aug 16, 2008 at 08:44:50PM -0400, Filipus Klutiero wrote: > Version: 1:1.1.0-b4+cvs20080623-1 > > Frank, I'm not sure why you marked the bug as found in > 1:1.1.0-b4+cvs20070924-2, but this is fixed at least in > 1:1.1.0-b4+cvs20080623-1. Uh, my mistake, I meant 1.1.0+cvs20061231-2 Gruesse, -- Frank Lichtenheld <[EMAIL PROTECTED]> www: http://www.djpig.de/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#493409: fix for simutrans-makeobj
Package: simutrans-makeobj
Followup-For: Bug #493409
With the attached series of patches I get identical results on i386,
amd64 and mips.
00_big_endian.patch
This uses the header to detect big-endian systems. This
replaces the hack in the Makefile (seriously, powerpc isn't the only
big-endian arch...). I don't think is portable, so this
probably isn't a suitable solution for upstream.
01_png.patch
Peter Green's PNG reader fix.
02_makeobj_fixes.patch
makeobj writes some data by dumping in-memory object instances to
disk. This is obviously not portable, so this needed to be
rewritten. It looks like Hajo fixed most of this in the past, I did
the rest.
03_makeobj_cleanup.patch
After the last patch the weird logic in obj_node_t isn't needed
anymore, so it can be removed. (This is strictly cleanup, it isn't
necessary for makeobj to run correctly.)
--- a/simtypes.h
+++ b/simtypes.h
@@ -8,6 +8,13 @@
#ifndef SIMTYPES_H
#define SIMTYPES_H
+#include
+#undef LITTLE_ENDIAN //endian.h gives these definitions we don't want
+#undef BIG_ENDIAN
+#if __BYTE_ORDER == __BIG_ENDIAN
+ #define BIG_ENDIAN
+#endif
+
#if defined _MSC_VER
# if _MSC_VER <= 1200
# error "Simutrans cannot be compiled with Visual C++ 6.0 or
earlier."
--- a/utils/dr_rdpng.c
+++ b/utils/dr_rdpng.c
@@ -48,11 +48,15 @@
png_read_info(png_ptr, info_ptr);
+ //png_uint_32 is 64 bit on some architectures!
+ png_uint_32 widthpu32,heightpu32;
png_get_IHDR(
png_ptr, info_ptr,
- width, height, &bit_depth, &color_type,
+ &widthpu32, &heightpu32, &bit_depth, &color_type,
&interlace_type, NULL, NULL
);
+ *width = widthpu32;
+ *height = heightpu32;
if (*height % base_img_size != 0 || *width % base_img_size != 0) {
printf("read_png: Invalid image size.\n");
--- a/besch/writer/factory_writer.cc
+++ b/besch/writer/factory_writer.cc
@@ -38,14 +38,19 @@
{
rauch_besch_t besch;
memset(&besch, 0, sizeof(besch));
- obj_node_t node(this, sizeof(besch), &parent, true);
+ obj_node_t node(this, 10, &parent, false);
xref_writer_t::instance()->write_obj(outfp, node, obj_smoke,
obj.get("smoke"), true);
besch.pos_off = obj.get_koord("smoketile", koord(0, 0));
besch.xy_off= obj.get_koord("smokeoffset", koord(0, 0));
besch.zeitmaske = obj.get_int( "smokespeed", 0);
- node.write_data(outfp, &besch);
+ node.write_sint16(outfp, besch.pos_off.x, 0);
+ node.write_sint16(outfp, besch.pos_off.y, 2);
+ node.write_sint16(outfp, besch.xy_off.x, 4);
+ node.write_sint16(outfp, besch.xy_off.x, 6);
+ node.write_sint16(outfp, besch.zeitmaske, 8);
+
node.write(outfp);
}
@@ -72,7 +77,7 @@
{
fabrik_lieferant_besch_t besch;
- obj_node_t node(this, sizeof(besch), &parent, true);
+ obj_node_t node(this, 8, &parent, false);
besch.anzahl = count;
besch.kapazitaet = capacity;
@@ -80,7 +85,11 @@
xref_writer_t::instance()->write_obj(outfp, node, obj_good, warename,
true);
- node.write_data(outfp, &besch);
+ node.write_uint16(outfp, besch.kapazitaet, 0);
+ node.write_uint16(outfp, besch.anzahl, 2);
+ node.write_uint16(outfp, besch.verbrauch, 4);
+ node.write_uint16(outfp, 0,6); //dummy, unused (and
uninitialized in past versions)
+
node.write(outfp);
}
--- a/besch/writer/ground_writer.cc
+++ b/besch/writer/ground_writer.cc
@@ -10,7 +10,7 @@
{
grund_besch_t besch;
- obj_node_t node(this, sizeof(besch), &parent, true);
+ obj_node_t node(this, 0, &parent, false);
write_head(fp, node, obj);
@@ -37,6 +37,5 @@
}
imagelist2d_writer_t::instance()->write_obj(fp, node, keys);
- node.write_data(fp, &besch);
node.write(fp);
}
--- a/besch/writer/pedestrian_writer.cc
+++ b/besch/writer/pedestrian_writer.cc
@@ -12,7 +12,7 @@
fussgaenger_besch_t besch;
int i;
- obj_node_t node(this, sizeof(besch), &parent, true);
+ obj_node_t node(this, 4, &parent, false);
write_head(fp, node, obj);
@@ -33,6 +33,8 @@
}
imagelist_writer_t::instance()->write_obj(fp, node, keys);
- node.write_data(fp, &besch);
+ node.write_uint16(fp, besch.gewichtung, 0);
+ node.write_uint16(fp, 0,2); //dummy, unused (and
uninitialized in past versions)
+
node.write(fp);
}
--- a/besch/writer/skin_writer.cc
+++ b/besch/writer/skin_writer.cc
@@ -31,12 +31,11 @@
skin_besch_t besch;
- obj_node_t node(this, sizeof(besch), &parent, true);
+ obj_node_t node(this, 0, &parent, false);
write_head(fp, node, obj);
imagelist_writer_t::instance()->write_obj(fp, node, imagekeys);
- node.write_data(fp, &besch);
node.write(fp);
}
--- a/besch/wr
Bug#495421: fakeroot-ng: does not appear to work any more
Jasen Betts wrote: It just stopped working! (it was working last month) even harmless binaries refuse to run. [EMAIL PROTECTED]:/tmp$ fakeroot -l log /bin/true Killed [EMAIL PROTECTED]:/tmp$ cat log handle_memory_allocation: 4458 process failed to mmap memory: Operation not permitted Needless to say, it works for me :-) Is your temporary folder (/tmp or TMPDIR) mounted with the -noexec flag? If so, what you see is the expected behavior. Set "TMPDIR" environment variable to point to somewhere that isn't mounted with -noexec and try again. Upstream checks this situation and gives a more verbose error message. I will try to add support for an alternative environment variable as well, so that you don't move the TMPDIR for all of the applications fakeroot-ng runs, only it itself. Shachar -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: tagging 494842
Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.9.26 > tags 494842 + pending Bug#494842: versatile kernel doesn't boot There were no tags set. 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#493899: DirectFB fails to start ("Could not initialize 'system' core!")
tags 493899 + pending confirmed Thanks Hi, the bug is confirmed. The patch [1] to reopen console if zero length byte is read, breaks directfb. It fails in the usual case, but works when run through strace. we'll try to update the patch to fix issue. Otherwise, we'll remove it. cheers, Fathi [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=462626 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#495189: solution
Hi! For the protocol: The source.list file was allright, switching to aptitude let the problem disapear. Maybe you want to emphasize the use of aptitude on the web site... regards matthias -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: DirectFB fails to start ("Could not initialize 'system' core!")
Processing commands for [EMAIL PROTECTED]:
> tags 493899 + pending confirmed
Bug#493899: libdirectfb-1.0-0: DirectFB fails to start ("Could not initialize
'system' core!")
There were no tags set.
Tags added: pending, confirmed
> Thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: severity of 495432 is important
Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.10.35 > severity 495432 important Bug#495432: XSS in awstats < 6.9beta (upstream bug 2001151) 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]
Bug#482501: marked as done (apt-howto: FTBFS: nsgmls:E: cannot find "apt-howto.ca.sgml")
Your message dated Sun, 17 Aug 2008 11:50:07 +0100 with message-id <[EMAIL PROTECTED]> and subject line apt-howto has been removed from Debian, closing #482501 has caused the Debian Bug report #482501, regarding apt-howto: FTBFS: nsgmls:E: cannot find "apt-howto.ca.sgml" 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.) -- 482501: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=482501 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems --- Begin Message --- Package: apt-howto Version: 2.0.2-3 Severity: serious User: [EMAIL PROTECTED] Usertags: qa-ftbfs-20080522 qa-ftbfs Justification: FTBFS on i386 Hi, During a rebuild of all packages in sid, your package failed to build on i386. This rebuild was done with gcc 4.3 instead of gcc 4.2, because gcc 4.3 is now the default on most architectures (even if it's not the case on i386 yet). Consequently, many failures are caused by the switch to gcc 4.3. If you determine that this failure is caused by gcc 4.3, feel free to downgrade this bug to 'important' if your package is only built on i386, and this bug is specific to gcc 4.3 (i.e the package builds fine with gcc 4.2). Relevant part: > make[1]: Entering directory > `/build/user-apt-howto_2.0.2-3-amd64-SXeYRD/apt-howto_2.0.2-3' > po4a-translate -k 39 -f sgml -m apt-howto.en.sgml -p po4a/po/ca.po -l > apt-howto.ca.sgml -a po4a/addendum.doc.ca > make[1]: *** [apt-howto.ca.sgml] Broken pipe > debiandoc2html -tapt-howto -l $(echo ca | bin/getlocale) -c apt-howto.ca.sgml > nsgmls:E: cannot find "apt-howto.ca.sgml"; tried "apt-howto.ca.sgml", > "/usr/local/share/sgml/apt-howto.ca.sgml", "/usr/share/sgml/apt-howto.ca.sgml" > nsgmls:/usr/share/sgml/debiandoc/dtd/sgml/1.0/debiandoc.dcl:67:40:E: end of > document in prolog > make[1]: *** [apt-howto.ca.html.stamp] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2008/05/22 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 --- --- Begin Message --- Version: 2.0.2-3+rm The apt-howto package has been removed from Debian testing, unstable and experimental, so I am now closing the bugs that were still opened against it. For more information about this package's removal, read http://bugs.debian.org/493787 . That bug might give the reasons why this package was removed, and suggestions of possible replacements. Don't hesitate to reply to this mail if you have any question. Thank you for your contribution to Debian. -- Marco Rodrigues http://Marco.Tondela.org --- End Message ---
Bug#491378: marked as done (Several issues regarding linking, orphaned, behind upstream, low popcon -> IMHO not suitable for release)
Your message dated Sun, 17 Aug 2008 11:18:34 +0100 with message-id <[EMAIL PROTECTED]> and subject line linm has been removed from Debian, closing #491378 has caused the Debian Bug report #491378, regarding Several issues regarding linking, orphaned, behind upstream, low popcon -> IMHO not suitable for 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.) -- 491378: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=491378 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems --- Begin Message --- Package: linm Severity: serious While looking at this package to do a QA upload I noticed several possible issues: - GPLed, yet links against OpenSSL. While the only code that uses OpenSSL is licensed under a less restrictive license and on itself is proably ok to be linked with it, in the end all is meshed together in one library. - Said code is a copy of libssh2, so it probably should be using the seperate version in the archive instead. - Said code is also not mentioned in debian/copyright at all. - Parts of this package consist of static libraries that e.g. link parts of OpenSSL in. This is probably a bad idea from a security point of view. Together with the facts that this package is orphaned, laggs several version behind upstream, and has really low popcon numbers I think it would be better to keep it out of lenny for now and remove it soon unless someone wants to clean it up. Gruesse, Frank Lichtenheld -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.25-2-686 (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash --- End Message --- --- Begin Message --- Version: 0.7.9-2.1+rm The linm package has been removed from Debian testing, unstable and experimental, so I am now closing the bugs that were still opened against it. For more information about this package's removal, read http://bugs.debian.org/493587 . That bug might give the reasons why this package was removed, and suggestions of possible replacements. Don't hesitate to reply to this mail if you have any question. Thank you for your contribution to Debian. -- Marco Rodrigues http://Marco.Tondela.org --- End Message ---
Bug#459568: marked as done (sbaz unusable in lenny)
Your message dated Sun, 17 Aug 2008 11:17:43 +0100 with message-id <[EMAIL PROTECTED]> and subject line sbaz has been removed from Debian, closing #459568 has caused the Debian Bug report #459568, regarding sbaz unusable in lenny to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [EMAIL PROTECTED] immediately.) -- 459568: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=459568 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems --- Begin Message --- Subject: sbaz unusable in lenny Package: sbaz Version: 1.20-2 Severity: grave Justification: renders package unusable *** Please type your report below this line *** $ sbaz-setup /tmp/ Exception in thread "main" java.lang.NoClassDefFoundError: scala/runtime/Comparator at sbaz.clui.Settings.parseOptions(Settings.scala:66) at sbaz.clui.CommandLine$.processCommandLine(CommandLine.scala:32) at sbaz.clui.CommandLine$.main(CommandLine.scala:63) at sbaz.clui.CommandLine.main(CommandLine.scala) $ sbaz sbaz [ global_options... ] command command_options... Global options: -d Operate on dir as the local managed directory. -n | --dryrun Do not actually do anything. Only print out what tool would normally do with the following arguments. -v | --verbose Output messages about what the sbaz tool is doing -versionVersion information Available commands: Exception in thread "main" java.lang.NoClassDefFoundError: scala/runtime/BoxesUtility at sbaz.clui.CommandUtil$$anonfun$0.apply(Command.scala:68) at scala.List.sort_1$0(List.scala:794) at scala.List.sort(List.scala:823) at sbaz.clui.CommandUtil$.(Command.scala:68) at sbaz.clui.CommandUtil$.(Command.scala) at sbaz.clui.commands.Help$.run(Help.scala:29) at sbaz.clui.CommandLine$.usageExit(CommandLine.scala:26) at sbaz.clui.CommandLine$.processCommandLine(CommandLine.scala:36) at sbaz.clui.CommandLine$.main(CommandLine.scala:63) at sbaz.clui.CommandLine.main(CommandLine.scala) I suppose the unversioned dependency to scala-library is wrong and should be replaced by a versionend one depending on a newer scala-library than currently is in lenny. Best regards, Silvestre Zabala -- System Information: Debian Release: 4.0 APT prefers stable APT policy: (500, 'stable'), (101, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18 Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Versions of packages sbaz depends on: ii scala-library 2.3.0-1.1 The Scala standard library sbaz recommends no packages. -- no debconf information --- End Message --- --- Begin Message --- Version: 1.20-2+rm The sbaz package has been removed from Debian testing, unstable and experimental, so I am now closing the bugs that were still opened against it. For more information about this package's removal, read http://bugs.debian.org/493600 . That bug might give the reasons why this package was removed, and suggestions of possible replacements. Don't hesitate to reply to this mail if you have any question. Thank you for your contribution to Debian. -- Marco Rodrigues http://Marco.Tondela.org --- End Message ---
Bug#464259: marked as done (sbaz: FTBFS: /build/user/sbaz-1.20/src/sbaz/PackageSpec.scala:35: error: unreachable code)
Your message dated Sun, 17 Aug 2008 11:17:43 +0100
with message-id <[EMAIL PROTECTED]>
and subject line sbaz has been removed from Debian, closing #464259
has caused the Debian Bug report #464259,
regarding sbaz: FTBFS: /build/user/sbaz-1.20/src/sbaz/PackageSpec.scala:35:
error: unreachable code
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.)
--
464259: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=464259
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: sbaz
version: 1.20-2
Severity: serious
User: [EMAIL PROTECTED]
Usertags: qa-ftbfs-20080205 qa-ftbfs
Justification: FTBFS on i386
Hi,
During a rebuild of all packages in sid, your package failed to build on i386.
Relevant part:
> dpkg-source: building sbaz in sbaz_1.20-2.dsc
> debian/rules build
> dh_testdir
> ANT_OPTS=-Xmx512M ant -Dscala.lib.dir=/usr/share/java \
> -Dant-contrib.jar=/usr/share/java/ant-contrib.jar dist
> Buildfile: build.xml
>
> init:
> [taskdef] Could not load definitions from resource
> net/sf/antcontrib/antlib.xml. It could not be found.
>
> build.main:
> [mkdir] Created dir: /build/user/sbaz-1.20/build/build.main
>[scalac] Compiling 72 source files to
> /build/user/sbaz-1.20/build/build.main
>[scalac] /build/user/sbaz-1.20/src/sbaz/AvailableList.scala:17: warning:
> `.f' has been deprecated; use `_.f' instead
>[scalac] def packages = new PackageSet(available.map(.pack))
>[scalac] ^
>[scalac] /build/user/sbaz-1.20/src/sbaz/AvailableList.scala:99: warning:
> `.f' has been deprecated; use `_.f' instead
>[scalac] {available.map(.toXML)}
>[scalac] ^
>[scalac] /build/user/sbaz-1.20/src/sbaz/AvailableList.scala:104: warning:
> `.f' has been deprecated; use `_.f' instead
>[scalac] {available.map(.toOldXML)}
>[scalac] ^
>[scalac] /build/user/sbaz-1.20/src/sbaz/InstalledEntry.scala:32: warning:
> `.f' has been deprecated; use `_.f' instead
>[scalac] {files.map(.toXML)}
>[scalac] ^
>[scalac] /build/user/sbaz-1.20/src/sbaz/InstalledList.scala:23: warning:
> `.f' has been deprecated; use `_.f' instead
>[scalac] def packages = new PackageSet(installedEntries.map(.pack))
>[scalac] ^
>[scalac] /build/user/sbaz-1.20/src/sbaz/OverrideUniverse.scala:48:
> warning: `.f' has been deprecated; use `_.f' instead
>[scalac](components.map(.toXML)) : _*))
>[scalac] ^
>[scalac] /build/user/sbaz-1.20/src/sbaz/PackageSet.scala:128: warning:
> `.f' has been deprecated; use `_.f' instead
>[scalac] (packages.map(.toXML)) : _* )
>[scalac]^
>[scalac] /build/user/sbaz-1.20/src/sbaz/clui/commands/Available.scala:35:
> warning: `.f' has been deprecated; use `_.f' instead
>[scalac] val specs = dir.available.packages.toList.map(.spec)
>[scalac] ^
>[scalac] /build/user/sbaz-1.20/src/sbaz/clui/commands/Remove.scala:32:
> warning: `.f' has been deprecated; use `_.f' instead
>[scalac] val neednames = needers.map(.packageSpec)
>[scalac] ^
>[scalac] /build/user/sbaz-1.20/src/sbaz/clui/commands/Upgrade.scala:59:
> warning: `.f' has been deprecated; use `_.f' instead
>[scalac] specsToInstall ++= newNeeded.map(.spec)
>[scalac] ^
>[scalac] /build/user/sbaz-1.20/src/sbaz/keys/Key.scala:31: warning: `.f'
> has been deprecated; use `_.f' instead
>[scalac] val messagesXML =
> messagesNode.child.find(.isInstanceOf[Elem]) match {
>[scalac] ^
>[scalac] /build/user/sbaz-1.20/src/sbaz/keys/KeyRing.scala:28: warning:
> `.f' has been deprecated; use `_.f' instead
>[scalac] {keys.map(.toXML)}
>[scalac]^
>[scalac] /build/user/sbaz-1.20/src/sbaz/messages/KeyCreate.scala:26:
> warning: `.f' has been deprecated; use `_.f' instead
>[scalac] val messagesXML =
> messagesNode.child.find(.isInstanceOf[Elem]) match {
>[scalac] ^
>[scalac] /build/user/sbaz-1.20/src/sbaz/messages/KeyList.scala:14:
> warning: `.f' has been deprecated; use `_.f' instead
>[scalac] def toXML = {keyList.map(.toXM
Bug#494760: marked as done (kernel-patch-nfs-ngroups: Doesn't apply against Lenny kernel)
Your message dated Sun, 17 Aug 2008 09:47:07 + with message-id <[EMAIL PROTECTED]> and subject line Bug#494760: fixed in kernel-patch-nfs-ngroups 4.54-8.1 has caused the Debian Bug report #494760, regarding kernel-patch-nfs-ngroups: Doesn't apply against Lenny kernel 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.) -- 494760: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=494760 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems --- Begin Message --- Package: kernel-patch-nfs-ngroups Severity: grave Justification: renders package unusable kernel-patch-nfs-ngroups only provides patches for Linux up to 2.6.23, which don't apply any longer against current kernels. Please update to 2.6.26, updated patches are available at http://frankvm.xs4all.nl/nfs-ngroups/ Cheers, Moritz -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.26-1-686 (SMP w/1 CPU core) Locale: LANG=C, [EMAIL PROTECTED] (charmap=ISO-8859-15) Shell: /bin/sh linked to /bin/bash --- End Message --- --- Begin Message --- Source: kernel-patch-nfs-ngroups Source-Version: 4.54-8.1 We believe that the bug you reported is fixed in the latest version of kernel-patch-nfs-ngroups, which is due to be installed in the Debian FTP archive: kernel-patch-nfs-ngroups_4.54-8.1.dsc to pool/main/k/kernel-patch-nfs-ngroups/kernel-patch-nfs-ngroups_4.54-8.1.dsc kernel-patch-nfs-ngroups_4.54-8.1.tar.gz to pool/main/k/kernel-patch-nfs-ngroups/kernel-patch-nfs-ngroups_4.54-8.1.tar.gz kernel-patch-nfs-ngroups_4.54-8.1_all.deb to pool/main/k/kernel-patch-nfs-ngroups/kernel-patch-nfs-ngroups_4.54-8.1_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. Moritz Muehlenhoff <[EMAIL PROTECTED]> (supplier of updated kernel-patch-nfs-ngroups 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: Sun, 17 Aug 2008 11:26:38 +0200 Source: kernel-patch-nfs-ngroups Binary: kernel-patch-nfs-ngroups Architecture: source all Version: 4.54-8.1 Distribution: unstable Urgency: low Maintainer: Yann Dirson <[EMAIL PROTECTED]> Changed-By: Moritz Muehlenhoff <[EMAIL PROTECTED]> Description: kernel-patch-nfs-ngroups - Client-side bypassing of ngroups limitation in NFS protocol Closes: 444555 494760 Changes: kernel-patch-nfs-ngroups (4.54-8.1) unstable; urgency=low . * Non-maintainer upload. * Add a patch for Linux 2.6.26 (Closes: #494760, #444555) * Update README file to latest upstream version Checksums-Sha1: 5adbad65daf07b95f51377c94a66e91b9028743e 833 kernel-patch-nfs-ngroups_4.54-8.1.dsc 1be50eea5679f6246a49a88e837764562f778598 49624 kernel-patch-nfs-ngroups_4.54-8.1.tar.gz d1c3656e5adaf19669b4de0fc52c3d19f64c0513 56094 kernel-patch-nfs-ngroups_4.54-8.1_all.deb Checksums-Sha256: b49c3abad22374e7eb5dab22086440af029ce94a90631f49bfcd704b1ae41b35 833 kernel-patch-nfs-ngroups_4.54-8.1.dsc 43389529ef7d88ad36721b4d57331c9d65cd6007db0f7bcdc360ba5ce71569e0 49624 kernel-patch-nfs-ngroups_4.54-8.1.tar.gz 693a6af21bcca5944e3726baaa60ecf07a75ec9f09c3422b4e8595753b5108d3 56094 kernel-patch-nfs-ngroups_4.54-8.1_all.deb Files: 46a1ad679394356db1b632fdd474f371 833 admin extra kernel-patch-nfs-ngroups_4.54-8.1.dsc ecfba46e8e012eb291d807a4d0a19b9b 49624 admin extra kernel-patch-nfs-ngroups_4.54-8.1.tar.gz 0a97541e2f4e860fb6fe2899c4d76e7b 56094 admin extra kernel-patch-nfs-ngroups_4.54-8.1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkin7+MACgkQXm3vHE4uylpJUQCeOkXwflSyH1oX7VG/KWp7jSAc 3lUAn38Und6tkeUbfivMQ5doK4qc+eZc =G5ZQ -END PGP SIGNATURE- --- End Message ---
Bug#492100: marked as done (gnat-glade: inconsistency beetween gnat version and glade version)
Your message dated Sun, 17 Aug 2008 11:10:30 +0100
with message-id <[EMAIL PROTECTED]>
and subject line gnat-glade has been removed from Debian, closing #492100
has caused the Debian Bug report #492100,
regarding gnat-glade: inconsistency beetween gnat version and glade version
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.)
--
492100: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=492100
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: gnat-glade
Version: 2007-1
Severity: grave
Justification: renders package unusable
During compilation of some test code I get :
gnatdist: building partition depart
gcc -c -gnatpg -Idsa/partitions/tst/depart -Idsa/stubs -I. -O0
--RTS=sjlj -I/usr/share/ada/adainclude/garlic -I- -o
dsa/partitions/tst/depart/s-garela.o
dsa/partitions/tst/depart/s-garela.adb
gcc -c -Idsa/partitions/tst/depart -Idsa/stubs -I. -O0 --RTS=sjlj
-I/usr/share/ada/adainclude/garlic -I- -o
dsa/partitions/tst/depart/partition.o
dsa/partitions/tst/depart/partition.adb
gnatbind -Idsa/partitions/tst/depart -Idsa/stubs -I. --RTS=sjlj
-aI/usr/share/ada/adainclude/garlic -aO/usr/lib/ada/adalib/garlic -I- -x
/home/xavier/tmp/test1/dsa/partitions/tst/depart/partition.ali
error: "s-stratt.adb" and "partition.adb" compiled with different GNAT
versions
error: "s-dsaser.ads" and "partition.adb" compiled with different GNAT
versions
error: "s-parint.adb" and "partition.adb" compiled with different GNAT
versions
error: "s-garlic.ads" and "partition.adb" compiled with different GNAT
versions
error: "s-gardeb.adb" and "partition.adb" compiled with different GNAT
versions
error: "s-gasoli.adb" and "partition.adb" compiled with different GNAT
versions
error: "s-gartyp.adb" and "partition.adb" compiled with different GNAT
versions
error: "s-garexc.adb" and "partition.adb" compiled with different GNAT
versions
error: "s-garhea.adb" and "partition.adb" compiled with different GNAT
versions
error: "s-garfil.adb" and "partition.adb" compiled with different GNAT
versions
error: "s-ganata.adb" and "partition.adb" compiled with different GNAT
versions
error: "s-gartab.adb" and "partition.adb" compiled with different GNAT
versions
error: "s-garuti.adb" and "partition.adb" compiled with different GNAT
versions
error: "s-garpar.adb" and "partition.adb" compiled with different GNAT
versions
error: "s-gargro.adb" and "partition.adb" compiled with different GNAT
versions
error: "s-garopt.adb" and "partition.adb" compiled with different GNAT
versions
error: "s-gaplsp.ads" and "partition.adb" compiled with different GNAT
versions
error: "s-garstr.adb" and "partition.adb" compiled with different GNAT
versions
error: "s-gaphlo.adb" and "partition.adb" compiled with different GNAT
versions
error: "s-garpro.adb" and "partition.adb" compiled with different GNAT
versions
error: "s-galiop.ads" and "partition.adb" compiled with different GNAT
versions
error: "s-garsto.adb" and "partition.adb" compiled with different GNAT
versions
error: "s-garuni.adb" and "partition.adb" compiled with different GNAT
versions
error: "s-gartra.adb" and "partition.adb" compiled with different GNAT
versions
error: "s-garsta.adb" and "partition.adb" compiled with different GNAT
versions
error: "s-garpri.adb" and "partition.adb" compiled with different GNAT
versions
error: "s-garrem.adb" and "partition.adb" compiled with different GNAT
versions
error: "s-gartas.adb" and "partition.adb" compiled with different GNAT
versions
error: "s-gaprco.adb" and "partition.adb" compiled with different GNAT
versions
error: "s-gaprtc.adb" and "partition.adb" compiled with different GNAT
versions
error: "s-gptcse.adb" and "partition.adb" compiled with different GNAT
versions
error: "s-gastco.adb" and "partition.adb" compiled with different GNAT
versions
error: "s-garter.adb" and "partition.adb" compiled with different GNAT
versions
error: "s-rpc.adb" and "partition.adb" compiled with different GNAT
versions
error: "s-gaprma.adb" and "partition.adb" compiled with different GNAT
versions
error: "s-rpcser.adb" and "partition.adb" compiled with different GNAT
versions
error: "s-stratt.adb" must be compiled
error: ("/usr/lib/ada/adalib/garlic/s-stratt.ali" is obsolete and
read-only)
error: "s-finimp.adb" must be compiled
error:
("/tools/gnat_2007/lib/gcc/i686-pc-linux-gnu/4.1.3/rts-sjlj/adalib/s-finimp.ali"
is obsolete and read-only)
error: "s-dsaser.ads" must be compiled
error: ("/usr/lib/ada/adalib/garlic/s-dsaser.ali" is obsolete and
read-only)
error: "s-parint.adb" must be compiled
error: ("/usr/lib/ada/adalib/garlic
Bug#488696: Fixing 488696
> Another problem I noticed is that something (not sure whether m-a or > comedi) uses depmod when building comedi-modules. module-init-tools > (which contains depmod) is not pulled in by any dependency. Please > investigate, and if it is comedi which needs depmod, we'll need to add > a dependency on module-init-tools. You are right thanks. Comedi checks for the existence of depmod in the configure script. I have added dependency on module-init-tools in version 0.7.76+20080817cvs-1. /Gudjon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: bla
Processing commands for [EMAIL PROTECTED]: > reassign 495371 fglrx-source Bug#495371: fglrx-kernel-src: Does not build against 2.6.26 Bug reassigned from package `fglrx-kernel-src' to `fglrx-source'. > forcemerge 485793 495371 Bug#485793: fglrx module doesn't build with 2.6.26 kernel Bug#495371: fglrx-kernel-src: Does not build against 2.6.26 Bug#493718: fglrx-source: FTBFS with 2.6.26-1 Forcibly Merged 485793 493718 495371. > 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#495421: fakeroot-ng: does not appear to work any more
Package: fakeroot-ng Version: 0.12-1 Severity: grave Justification: renders package unusable It just stopped working! (it was working last month) even harmless binaries refuse to run. [EMAIL PROTECTED]:/tmp$ fakeroot -l log /bin/true Killed [EMAIL PROTECTED]:/tmp$ cat log Debugger started Debugger successfully attached to process 4458 Caught SIGSTOP Caught signal 17 Caught SIGUSR1 by child - start special handling Begin the process loop 4458: Init new process 4458: Called execve(NONE) execve: 4458 calling execve for executing /bin/true 4458: Called syscall 11, redirected from execve execve: 4458 successfully execed a new command 4458: Called syscall 11, redirected from execve execve: 4458 absorbed dummy SIGTRAP after successful execve allocate_process_mem: 4458 running syscall 45 needs process memory handle_memory_allocation: 4458 allocated for our use 4096 bytes at 0xb7fdf000 handle_memory_allocation: 4458 process failed to mmap memory: Operation not permitted 4458: Exit with SIGKILL -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.24-1-686 (SMP w/2 CPU cores) Locale: LANG=en_NZ.UTF-8, LC_CTYPE=en_NZ.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages fakeroot-ng depends on: ii libc6 2.7-10 GNU C Library: Shared libraries ii libgcc1 1:4.3.1-2 GCC support library ii libstdc++64.3.1-2The GNU Standard C++ Library v3 fakeroot-ng recommends no packages. -- debconf-show failed -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#299487: marked as done (jags: Jags crash when I click on the (+) to expand a workgroup)
Your message dated Sun, 17 Aug 2008 10:30:29 +0100 with message-id <[EMAIL PROTECTED]> and subject line jags has been removed from Debian, closing #299487 has caused the Debian Bug report #299487, regarding jags: Jags crash when I click on the (+) to expand a workgroup 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.) -- 299487: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=299487 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems --- Begin Message --- Package: jags Version: 0.22.1-2 Severity: important I start up jags, it shows (+) SAMBA network Clicking on the (+) shows all workgroups, with a (+) in front of each. Clicking on the (+) in front of any workgroup kills jags with a segfault. The program is unuseable with this behaviour. Helge Hafting -- System Information: Debian Release: 3.1 APT prefers testing APT policy: (900, 'testing'), (800, 'experimental'), (800, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.11-rc5-mm1 Locale: LANG=no_NO.UTF-8, LC_CTYPE=no_NO.UTF-8 (charmap=UTF-8) Versions of packages jags depends on: ii libc62.3.2.ds1-20GNU C Library: Shared libraries an ii libgcc1 1:3.4.3-6 GCC support library ii libglib1.2 1.2.10-9The GLib library of C routines ii libgtk1.21.2.10-17 The GIMP Toolkit set of widgets fo ii libstdc++5 1:3.3.5-8 The GNU Standard C++ Library v3 ii libx11-6 4.3.0.dfsg.1-10 X Window System protocol client li ii libxext6 4.3.0.dfsg.1-10 X Window System miscellaneous exte ii libxi6 4.3.0.dfsg.1-10 X Window System Input extension li ii samba-common 3.0.10-1Samba common files used by both th ii smbclient3.0.10-1a LanManager-like simple client fo ii smbfs3.0.10-1mount and umount commands for the ii xlibs4.3.0.dfsg.1-10 X Keyboard Extension (XKB) configu -- no debconf information --- End Message --- --- Begin Message --- Version: 0.22.1-2.1+rm The jags package has been removed from Debian testing, unstable and experimental, so I am now closing the bugs that were still opened against it. For more information about this package's removal, read http://bugs.debian.org/494643 . That bug might give the reasons why this package was removed, and suggestions of possible replacements. Don't hesitate to reply to this mail if you have any question. Thank you for your contribution to Debian. -- Marco Rodrigues http://Marco.Tondela.org --- End Message ---
Bug#493781: marked as done (phamm-ldap: Messes "programmatically" with conffiles of other packages)
Your message dated Sun, 17 Aug 2008 09:02:31 + with message-id <[EMAIL PROTECTED]> and subject line Bug#493781: fixed in phamm 0.5.12-3 has caused the Debian Bug report #493781, regarding phamm-ldap: Messes "programmatically" with conffiles of other packages 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.) -- 493781: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=493781 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems --- Begin Message --- Package: phamm-ldap Version: 0.5.12-2 Severity: serious Justification: Policy 10.7.4 The postinst of phamm-ldap (and other phamm packages) edits /etc/ldap/slapd.conf to include a schema file. It is a violation of Debian Policy to mess with conffiles of other packages. See bug#370343 for a closely related issue, and #311188 for a longer discussion of a related (although more complex) issue. Kind regards, - Jonas -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.26-1-amd64 (SMP w/2 CPU cores) Locale: LANG=da_DK.UTF-8, LC_CTYPE=da_DK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash --- End Message --- --- Begin Message --- Source: phamm Source-Version: 0.5.12-3 We believe that the bug you reported is fixed in the latest version of phamm, which is due to be installed in the Debian FTP archive: phamm-ldap-amavis_0.5.12-3_all.deb to pool/main/p/phamm/phamm-ldap-amavis_0.5.12-3_all.deb phamm-ldap-vacation_0.5.12-3_all.deb to pool/main/p/phamm/phamm-ldap-vacation_0.5.12-3_all.deb phamm-ldap_0.5.12-3_all.deb to pool/main/p/phamm/phamm-ldap_0.5.12-3_all.deb phamm_0.5.12-3.diff.gz to pool/main/p/phamm/phamm_0.5.12-3.diff.gz phamm_0.5.12-3.dsc to pool/main/p/phamm/phamm_0.5.12-3.dsc phamm_0.5.12-3_all.deb to pool/main/p/phamm/phamm_0.5.12-3_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. Alessandro De Zorzi <[EMAIL PROTECTED]> (supplier of updated phamm 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: Sun, 17 Aug 2008 08:57:20 +0200 Source: phamm Binary: phamm phamm-ldap phamm-ldap-vacation phamm-ldap-amavis Architecture: source all Version: 0.5.12-3 Distribution: unstable Urgency: high Maintainer: Phamm Team <[EMAIL PROTECTED]> Changed-By: Alessandro De Zorzi <[EMAIL PROTECTED]> Description: phamm - PHP front-end to manage virtual services with LDAP - main package phamm-ldap - PHP front-end to manage virtual services with LDAP - back-end fil phamm-ldap-amavis - PHP front-end to manage virtual services with LDAP - back-end fil phamm-ldap-vacation - PHP front-end to manage virtual services with LDAP - back-end fil Closes: 493781 Changes: phamm (0.5.12-3) unstable; urgency=high . * Now phamm does not edit slapd.conf to include its own schema. (Closes: #493781) Checksums-Sha1: 12e9ed9b010dd213af326d6764fa183398f291b6 1100 phamm_0.5.12-3.dsc 957d98ee1aa374b8e56ea6406b7d226ae21fbb51 25921 phamm_0.5.12-3.diff.gz d37f72af8eaba1c43d6194cf100bc53b43f7 72972 phamm_0.5.12-3_all.deb 1579d5305a66b49ba09a62fd5ac9226ad92298f7 14852 phamm-ldap_0.5.12-3_all.deb 9599afc40e876ff9c7952538eb9284b42652c94a 3168 phamm-ldap-vacation_0.5.12-3_all.deb ef5a3688dddf4e8666da7348ace48998a9bb92cf 11216 phamm-ldap-amavis_0.5.12-3_all.deb Checksums-Sha256: 0290449eea578ab6ac49c7ec1d9cdb8ae52dc5fb017e7dab5d62e8068f526c49 1100 phamm_0.5.12-3.dsc 7079e4b60d369f217f4f26619da25eae039e377226cb3a5f79c74505de827a73 25921 phamm_0.5.12-3.diff.gz 7f19cdfe49376f6d4d2103e8b1caef74b22f110279c2066eeb5cb503d571a9ff 72972 phamm_0.5.12-3_all.deb 68b5f33ba3f134b2cea5118eaeb4bc92b8c8db009f5b6b5522306ccaaea277c8 14852 phamm-ldap_0.5.12-3_all.deb ca2644ef32bf0fbaa38d51479b5efb98fe5872203e7e2a5c95927b6a048a788f 3168 phamm-ldap-vacation_0.5.12-3_all.deb a81e32c5b6ff0a036c3ad54cbe319ceb45352d39b243905b8116dbbb2674e98d 11216 phamm-ldap-amavis_0.5.12-3_all.deb Files: 8774e68b9b7ea5e60d2e3b95e137fba7 1100 web extra phamm_0.5.12-3.dsc 9ff4fae3e747a83ef4bf33bba0d60419 25921 web extra phamm_0.5.12-3.diff.gz 19b912163ac44ba05435045fff55d007 72972 web extra phamm_0.5.12-3_all.deb 7833cf679
Bug#491505: [package varmon] varmon segfaults on Etch i386
At 1218959576 time_t, Julien Danjou wrote: > I finally decided to take a quick look this morning and I found the > culprit. > It was caused by *dead code* probably left in place by from previous upstream. > I removed it, and now it works as expected in any gcc -O? mode. If people are interested I've pushed code here: git://git.naquadah.org/varmon.git http://git.naquadah.org/?p=varmon.git;a=summary The fix for this bug is: http://git.naquadah.org/?p=varmon.git;a=commitdiff;h=ae1cb95cfd553625eeaa9fa1f687c7181475fe8d Cheers, -- Julien Danjou // ᐰ <[EMAIL PROTECTED]> http://julien.danjou.info // 9A0D 5FD9 EB42 22F6 8974 C95C A462 B51E C2FE E5CD signature.asc Description: Digital signature
Bug#491505: [package varmon] varmon segfaults on Etch i386
Hello guys, I finally decided to take a quick look this morning and I found the culprit. It was caused by *dead code* probably left in place by from previous upstream. I removed it, and now it works as expected in any gcc -O? mode. I'm preparing a new upstream release and will push it back to Debian ASAP (expect everything tomorrow). Thanks for the box Christoph. It was very useful. You can probably shut it down now. I'd suggest to keep it around just in case of a new bug in the coming weeks if you can, we never know, but that'd be odd. I've tested this new version with electric fence so I'm pretty confident. Cheers, -- Julien Danjou .''`. Debian Developer : :' : http://julien.danjou.info `. `' http://people.debian.org/~acid `- 9A0D 5FD9 EB42 22F6 8974 C95C A462 B51E C2FE E5CD signature.asc Description: Digital signature
