Bug#221906: Why and how they work
The more dedicated you are, the sooner you will see results. We look forward to your success! http://simorabe.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: pending
Processing commands for [EMAIL PROTECTED]: tags 478726 + pending Bug#478726: yap_5.1.1-2(sparc/unstable): FTBFS on sparc 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#479455: marked as done ([apt-p2p] bug with upload speed option)
Your message dated Mon, 05 May 2008 06:47:02 + with message-id [EMAIL PROTECTED] and subject line Bug#479455: fixed in apt-p2p 0.1.2 has caused the Debian Bug report #479455, regarding [apt-p2p] bug with upload speed option 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.) -- 479455: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=479455 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: apt-p2p Version: 0.1.1 Severity: grave Hello, I just tried apt-p2p and I have an exception in the log file. The upload speed settings seems to have a problem: Here the traceback: 2008-05-04 23:30:38+0200 [-] Unhandled Error Traceback (most recent call last): File /usr/lib/python2.5/site-packages/twisted/internet/defer.py, line 323, in _runCallbacks self.result = callback(self.result, *args, **kw) File /var/lib/python-support/python2.5/apt_p2p/AptPackages.py, line 401, in _findHash d.callback(HashObject()) File /usr/lib/python2.5/site-packages/twisted/internet/defer.py, line 242, in callback self._startRunCallbacks(result) File /usr/lib/python2.5/site-packages/twisted/internet/defer.py, line 307, in _startRunCallbacks self._runCallbacks() --- exception caught here --- File /usr/lib/python2.5/site-packages/twisted/internet/defer.py, line 323, in _runCallbacks self.result = callback(self.result, *args, **kw) File /var/lib/python-support/python2.5/apt_p2p/apt_p2p.py, line 166, in findHash_done self.startDownload([], req, hash, url, d) File /var/lib/python-support/python2.5/apt_p2p/apt_p2p.py, line 289, in startDownload getDefer = self.peers.get(hash, url) File /var/lib/python-support/python2.5/apt_p2p/PeerManager.py, line 488, in get return peer.get(path, method, modtime) File /var/lib/python-support/python2.5/apt_p2p/HTTPDownloader.py, line 334, in get return self.submitRequest(ClientRequest(method, path, headers, None)) File /var/lib/python-support/python2.5/apt_p2p/HTTPDownloader.py, line 208, in submitRequest self.rerank() File /var/lib/python-support/python2.5/apt_p2p/HTTPDownloader.py, line 424, in rerank speed = self.downloadSpeed() File /var/lib/python-support/python2.5/apt_p2p/HTTPDownloader.py, line 383, in downloadSpeed total_download += download[2] exceptions.TypeError: unsupported operand type(s) for +=: 'int' and 'NoneType' Maybe download[2] don't have the right type. Hope this can help you. Regards, Luc. --- System information. --- Architecture: i386 Kernel: Linux 2.6.24-1-686 Debian Release: lenny/sid 500 unstable ftp.fr.debian.org --- Package information. --- Depends (Version) | Installed ===-+- python | 2.5.2-1 python-support (= 0.7.1) | 0.7.7 debconf (= 0.5) | 1.5.21 OR debconf-2.0 | python-twisted-web2 (= 8.0) | 8.0.1-1 adduser | 3.107 python-debian (= 0.1.4) | 0.1.10 python-apt (= 0.6.20) | 0.7.5 python-pysqlite2 (= 2.1) | 2.4.1-1 ---End Message--- ---BeginMessage--- Source: apt-p2p Source-Version: 0.1.2 We believe that the bug you reported is fixed in the latest version of apt-p2p, which is due to be installed in the Debian FTP archive: apt-p2p_0.1.2.dsc to pool/main/a/apt-p2p/apt-p2p_0.1.2.dsc apt-p2p_0.1.2.tar.gz to pool/main/a/apt-p2p/apt-p2p_0.1.2.tar.gz apt-p2p_0.1.2_all.deb to pool/main/a/apt-p2p/apt-p2p_0.1.2_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. Cameron Dale [EMAIL PROTECTED] (supplier of updated apt-p2p 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, 04 May 2008 22:32:11 -0700 Source: apt-p2p Binary: apt-p2p Architecture: source all Version: 0.1.2 Distribution: unstable Urgency: low Maintainer: Cameron Dale [EMAIL PROTECTED] Changed-By: Cameron Dale [EMAIL PROTECTED] Description: apt-p2p- apt helper for peer-to-peer downloads of Debian packages Closes: 479455 Changes: apt-p2p (0.1.2) unstable; urgency=low . * Fixed a bug in
Bug#479494: python-ctypes: uninstallable due to libffi4 dependency
Package: python-ctypes Version: 1.0.2-4 Severity: serious Hello, currently, python-ctypes does not install due to it's dependency on libffi4 which has intentionally stopped building by the gcc-maintainers starting with gcc-4.3 (4.3.0-4) - see also #479115. Could you please instead depend on libffi5. Thanks for your work regards Mario -- A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? signature.asc Description: Digital signature
Bug#479503: file conflicts between packages
Package: libdw-dev, libdwarf-dev Severity: serious Justification: policy violation hi, both libdw-dev and libdwarf-dev ship `/usr/include/dwarf.h' but do neither conflict, nor add a diversion, thus fail to be installed in the same environment: Unpacking libdwarf-dev (from .../libdwarf-dev_20080409-1_amd64.deb) ... dpkg: error processing /var/cache/apt/archives/libdwarf-dev_20080409-1_amd64.deb (--unpack): trying to overwrite `/usr/include/dwarf.h', which is also in package libdw-dev dpkg-deb: subprocess paste killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/libdwarf-dev_20080409-1_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) bye, - michael -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#479504: libdigest-md4-perl: uninstallable due to libperl transition
Package: libdigest-md4-perl Version: 1.5.dfsg-1.2 Severity: serious Hello, perl currently transits from 5.8.8 to 5.10.0. This breaks libdigest-md4-perl which depends on perlapi-5.8.8. Could you please instead depend on perlapi-5.10.0. Thanks for your work regards Mario -- I heard, if you play a NT-CD backwards, you get satanic messages... That's nothing. If you play it forwards, it installs NT. signature.asc Description: Digital signature
Bug#446665: mercury: should this package be removed?
severity 446665 normal reassign 446665 ftp.debian.org retitle 446665 RM: mercury -- RoQA; RC buggy thanks On 14/10/07 at 20:32 +0200, Lucas Nussbaum wrote: Your package came up as a candidate for removal from Debian, because: * 4 RC bugs opened for a long time * not suitable for a stable release according to #281369 * Low popcon (19 insts) * Hasn't been in testing for a very long time * New upstream release available for a long time now Hi, This issue has been open for a long time. I am now removing mercury from Debian. If someone is still interested in fixing all those issues and getting in back in shape, the source package can be fetched from http://snapshot.debian.net/archive/2005/03/13/debian/pool/main/m/mercury/mercury_0.11.0.rotd.20040511-5.dsc -- | Lucas Nussbaum | [EMAIL PROTECTED] http://www.lucas-nussbaum.net/ | | jabber: [EMAIL PROTECTED] GPG: 1024D/023B3F4F | -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#479502: file conflicts between packages
Package: libcommandline-ruby1.8, libopen4-ruby1.8 Severity: serious Justification: policy violation hi, both libcommandline-ruby1.8 and libopen4-ruby1.8 ship `/usr/lib/ruby/1.8/open4.rb' but do neither conflict, nor add a diversion, thus fail to be installed in the same environment: Unpacking libopen4-ruby1.8 (from .../libopen4-ruby1.8_0.9.6-1_all.deb) ... dpkg: error processing /var/cache/apt/archives/libopen4-ruby1.8_0.9.6-1_all.deb (--unpack): trying to overwrite `/usr/lib/ruby/1.8/open4.rb', which is also in package libcommandline-ruby1.8 Processing triggers for man-db ... Errors were encountered while processing: /var/cache/apt/archives/libopen4-ruby1.8_0.9.6-1_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) bye, - michael -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: changing to wishlist
Processing commands for [EMAIL PROTECTED]: severity 462429 wishlist Bug#462429: SIGILL in libGLcore.so.1 from nvidia-glx 169.07-2 due to SSE instructions Severity set to `wishlist' from `grave' thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#479501: file conflicts between packages
Package: cherokee, lighttpd Severity: serious Justification: policy violation hi, both cherokee and lighttpd ship `/usr/share/man/man1/spawn-fcgi.1.gz' but do neither conflict, nor add a diversion, thus fail to be installed in the same environment: Unpacking lighttpd (from .../lighttpd_1.4.19-2_amd64.deb) ... dpkg: error processing /var/cache/apt/archives/lighttpd_1.4.19-2_amd64.deb (--unpack): trying to overwrite `/usr/share/man/man1/spawn-fcgi.1.gz', which is also in package cherokee Processing triggers for man-db ... Errors were encountered while processing: /var/cache/apt/archives/lighttpd_1.4.19-2_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) bye, - michael -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: close 478751
Processing commands for [EMAIL PROTECTED]: close 478751 Bug#478751: linux-headers-2.6.25-1-686: missing dependency linux-kbuild-2.6.25 'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing. Bug closed, send any further explanations to Hendrik Pagenhardt [EMAIL PROTECTED] thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#478751: linux-headers-2.6.25-1-686: missing dependency linux-kbuild-2.6.25
Hi, linux-headers-2.6.25-1-686 is now installable, therefore I'm going to close this bug... -- Laurent Bonnaud. http://www.lis.inpg.fr/pages_perso/bonnaud/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#479500: hippo-canvas: maintainer address bounces (simple typo)
Package: hippo-canvas Version: 0.2.23-4 Severity: serious This message was created automatically by mail delivery software. A message that you sent could not be delivered to one or more of its recipients. This is a permanent error. The following address(es) failed: [EMAIL PROTECTED] Unrouteable address == alioth, not lioth. -- | Lucas Nussbaum | [EMAIL PROTECTED] http://www.lucas-nussbaum.net/ | | jabber: [EMAIL PROTECTED] GPG: 1024D/023B3F4F | -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#479499: jppy: maintainer address rejects mail
Package: jppy Version: 0.0.43-1 Severity: serious On 01/05/08 at 10:51 +0100, [EMAIL PROTECTED] wrote: You are not allowed to post to this mailing list, and your message has been automatically rejected. If you think that your messages are being rejected in error, contact the mailing list owner at [EMAIL PROTECTED] Please at least moderate those mails. -- | Lucas Nussbaum | [EMAIL PROTECTED] http://www.lucas-nussbaum.net/ | | jabber: [EMAIL PROTECTED] GPG: 1024D/023B3F4F | -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: Re: Bug#446665: mercury: should this package be removed?
Processing commands for [EMAIL PROTECTED]: severity 446665 normal Bug#446665: mercury: should this package be removed? Severity set to `normal' from `serious' reassign 446665 ftp.debian.org Bug#446665: mercury: should this package be removed? Bug reassigned from package `mercury' to `ftp.debian.org'. retitle 446665 RM: mercury -- RoQA; RC buggy Bug#446665: mercury: should this package be removed? Changed Bug title to `RM: mercury -- RoQA; RC buggy' from `mercury: should this package be removed?'. 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: Re: Bug#476489: ucspi: should conflict with courier-mta
Processing commands for [EMAIL PROTECTED]: reassign 476489 ucspi-tcp,courier-mta Bug#476489: ucspi: should conflict with courier-mta Bug reassigned from package `ucspi-tcp' to `ucspi-tcp,courier-mta'. End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: tagging as pending bugs that are closed by packages in NEW
Processing commands for [EMAIL PROTECTED]: # Mon May 5 08:03:14 UTC 2008 # Tagging as pending bugs that are closed by packages in NEW # http://ftp-master.debian.org/new.html # # Source package in NEW: avant-window-navigator tags 478709 + pending Bug#478709: avant-window-navigator has circular Depends on avant-window-navigator-data There were no tags set. Tags added: pending # Source package in NEW: libtest-www-selenium-perl tags 477558 + pending Bug#477558: ITP: libtest-www-selenium-perl -- Test applications using Selenium Remote Control There were no tags set. Tags added: pending # Source package in NEW: tcltrf tags 478650 + pending Bug#478650: tclrtf build depends on buggy, old, broken, dead upstream, superseded package c2man There were no tags set. Tags added: pending # Source package in NEW: tcltrf tags 478722 + pending Bug#478722: build-depends on c2man about to be removed There were no tags set. Tags added: pending # Source package in NEW: e17 tags 405860 + pending Bug#405860: ITP: enlightenment-0.17 -- The Enlightenment Window Manager, release 0.17 There were no tags set. Tags added: pending # Source package in NEW: r-base-core-ra tags 479233 + pending Bug#479233: ITP: r-base-core-ra -- Ra patch for just-in-time compilation of R code There were no tags set. Tags added: pending # Source package in NEW: cbflib tags 467655 + pending Bug#467655: ITP: cbflib -- C library for accessing Crystallographic Binary Files 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#476489: ucspi: should conflict with courier-mta
On Thu, Apr 17, 2008 at 01:45:38AM +0200, Ralf Treinen wrote: ucspi-tcp should conflict with courier-mta as it shares a file with that package: Unpacking courier-mta (from .../courier-mta_0.59.0-1_amd64.deb) ... dpkg: error processing /var/cache/apt/archives/courier-mta_0.59.0-1_amd64.deb (--unpack): trying to overwrite `/usr/bin/addcr', which is also in package ucspi-tcp Errors were encountered while processing: /var/cache/apt/archives/courier-mta_0.59.0-1_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) Hi Stefan, the addcr programs from courier-mta and ucspi-tcp have nearly the same functionality, it's just that courier's addcr doesn't add a \c if it's already there. Possible solutions to the conflict: (1) ucspi-tcp diverts courier's addcr (2) courier-mta diverts ucpsi-tcp's addcr (3) both packages use alternatives to manage /usr/bin/addcr (4) ucspi-tcp renames the addcr program (upstream or Debian) (5) courier-mta renames the add cr program (upstream or Debian) I'm not that much in favor of (4), and personally suggest (2), as courier's addcr includes 'more' functionality. What do you think? Thanks, Gerrit. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: your mail
Processing commands for [EMAIL PROTECTED]: tag 479494 + pending Bug#479494: python-ctypes: uninstallable due to libffi4 dependency There were no tags set. Tags added: pending thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#415254: Reassigning bugs from libapache-mod-suphp to libapache2-mod-suphp
reassign 415254 libapache2-mod-suphp reassign 429923 libapache2-mod-suphp thanks The libapache-mod-suphp package has been removed from Debian testing, unstable and experimental. I am reassigning its bugs to the libapache2-mod-suphp package. Please have a look at them, and close them if they don't apply to libapache2-mod-suphp anymore. Don't hesitate to reply to this mail if you have any question. -- Lucas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#472138: marked as done (ctypes: libffi built from separate source, pleae b-d on libffi-dev)
Your message dated Mon, 5 May 2008 10:18:12 +0200 with message-id [EMAIL PROTECTED] and subject line Re: Bug#472138: ctypes: libffi built from separate source, pleae b-d on libffi-dev has caused the Debian Bug report #472138, regarding ctypes: libffi built from separate source, pleae b-d on libffi-dev to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [EMAIL PROTECTED] immediately.) -- 472138: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=472138 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: ctypes Severity: important Usertags: libffi After 10 years libffi does have a new upstream release again; this version is now packaged independent from GCC; once all packages are converted to use the binaries built from the separate libffi, GCC will stop building libffi packages. Please replace the current build dependencies lib*ffi4-dev with lib*ffi-dev and rebuild the package. ---End Message--- ---BeginMessage--- Version: 1.0.2-5 On Sat, 22 Mar 2008, Matthias Klose wrote: After 10 years libffi does have a new upstream release again; this version is now packaged independent from GCC; once all packages are converted to use the binaries built from the separate libffi, GCC will stop building libffi packages. Please replace the current build dependencies lib*ffi4-dev with lib*ffi-dev and rebuild the package. Done in the 1.0.2-5 upload but forgot to put it in the changelog. Hence manually closing. Cheers, -- Raphaël Hertzog Le best-seller français mis à jour pour Debian Etch : http://www.ouaza.com/livre/admin-debian/ ---End Message---
Bug#429094: marked as done (please update/request removal of your package)
Your message dated Mon, 05 May 2008 10:13:53 +0200 with message-id [EMAIL PROTECTED] and subject line libapache-mod-geoip has been removed from Debian, closing #429094 has caused the Debian Bug report #429094, regarding please update/request removal of your package 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.) -- 429094: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=429094 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: libapache-mod-geoip Severity: serious Version: 1.2.9-1 Hi there! Due to the recent removal of apache (including it's accompanied packages of apache-common, apache-dbg, apache-dev, apache-doc, apache-perl and apache-ssl) and libapache-mod-perl your package most propably isn't able to get installed or built anymore. These are the problems your package currently has: libapache-mod-geoip (dependency): apache-common (= 1.3) Please either send the ftp team a removal request for your package if it isn't able to work with apache2, or update it to build (only) packages for apache2. Thanks in advance, -- generate-mails.pl assisting Gerfried Fuchs ---End Message--- ---BeginMessage--- Version: 1.2.9-1+rm The libapache-mod-geoip 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/444129 . 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. -- Lucas ---End Message---
Bug#469338: unionfs-modules does not work with 2.6.24-1
El mar, 04-03-2008 a las 20:27 +0100, Daniel Baumann escribió: tags 469338 +pending thanks José L. Redrejo Rodríguez wrote: Tested with amd64, 486 686 kernel versions. Whenever I try to use unionfs module I always get the unionfs: Unknown symbol release_open_intent message, so the package is useless on any arch. this is know and was announced, i've added a patch to linux-2.6 trunk to add that missing symbol. once the next linux-2.6 upload happens, this will be fixed. Hi, linux 2.6.26 in Debian already includes your patch. Please, could you upload the new version of linux-modules-extra for this kernel? Regards. José L. signature.asc Description: Esta parte del mensaje está firmada digitalmente
Processed: Reassigning bugs from apache2-common to apache2.2-common
Processing commands for [EMAIL PROTECTED]: reassign 409304 apache2.2-common Bug#409304: /etc/apache2/apache2.conf incorrectly overrides configurations in /etc/apache2/httpd.conf Bug reassigned from package `apache2-common' to `apache2.2-common'. reassign 168109 apache2.2-common Bug#168109: apache2-common: mods-available/ssl.conf should enable ssl, and specify a default cert/key Bug reassigned from package `apache2-common' to `apache2.2-common'. reassign 395853 apache2.2-common Bug#395853: apache2-common: removes symlinks on upgrade Bug reassigned from package `apache2-common' to `apache2.2-common'. reassign 396607 apache2.2-common Bug#396607: Upgrade from apache2-common 2.0.55-4.1 fails. Bug reassigned from package `apache2-common' to `apache2.2-common'. reassign 414193 apache2.2-common Bug#414193: apache2-common: searching ALL files in /etc/apache2 for PidFile Bug reassigned from package `apache2-common' to `apache2.2-common'. reassign 421673 apache2.2-common Bug#421673: apache2-common: upgrade fiasco Bug reassigned from package `apache2-common' to `apache2.2-common'. reassign 392380 apache2.2-common Bug#392380: apache2-common: Upgrad issues with libapache2-mod-php4 installed Bug reassigned from package `apache2-common' to `apache2.2-common'. 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 479202 is serious
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.10.25 severity 479202 serious Bug#479202: fields tries to use Hash::Util Severity set to `serious' from `normal' 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#395853: Reassigning bugs from apache2-common to apache2.2-common
reassign 409304 apache2.2-common reassign 168109 apache2.2-common reassign 395853 apache2.2-common reassign 396607 apache2.2-common reassign 414193 apache2.2-common reassign 421673 apache2.2-common reassign 392380 apache2.2-common thanks The apache2-common package has been removed from Debian testing, unstable and experimental. I am reassigning its bugs to the apache2.2-common package. Please have a look at them, and close them if they don't apply to apache2.2-common anymore. Don't hesitate to reply to this mail if you have any question. -- Lucas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: Reassigning bugs from libapache-mod-suphp to libapache2-mod-suphp
Processing commands for [EMAIL PROTECTED]: reassign 415254 libapache2-mod-suphp Bug#415254: SuPHP security issue: Replace AddHandler by AddType Bug reassigned from package `libapache-mod-suphp' to `libapache2-mod-suphp'. reassign 429923 libapache2-mod-suphp Bug#429923: libapache-mod-suphp: Inserting suphp in modules.conf causes memory errors Bug reassigned from package `libapache-mod-suphp' to `libapache2-mod-suphp'. 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 472143 is serious, severity of 472145 is serious, severity of 472146 is serious ...
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.10.27 # libffi4-dev is no more, build-depending on it is release critical severity 472143 serious Bug#472143: exaile: libffi built from separate source, pleae b-d on libffi-dev Severity set to `serious' from `important' severity 472145 serious Bug#472145: gdesklets: libffi built from separate source, pleae b-d on libffi-dev Severity set to `serious' from `important' severity 472146 serious Bug#472146: gimmie: libffi built from separate source, pleae b-d on libffi-dev Severity set to `serious' from `important' severity 472156 serious Bug#472156: guile-gnome-platform: libffi built from separate source, pleae b-d on libffi-dev Severity set to `serious' from `important' severity 472160 serious Bug#472160: medit: libffi built from separate source, pleae b-d on libffi-dev Severity set to `serious' from `important' severity 472161 serious Bug#472161: notify-python: libffi built from separate source, pleae b-d on libffi-dev Severity set to `serious' from `important' severity 472163 serious Bug#472163: papaya: libffi built from separate source, pleae b-d on libffi-dev Severity set to `serious' from `important' severity 472164 serious Bug#472164: pyclutter: libffi built from separate source, pleae b-d on libffi-dev Severity set to `serious' from `important' severity 472165 serious Bug#472165: ontv: libffi built from separate source, pleae b-d on libffi-dev Severity set to `serious' from `important' severity 472168 serious Bug#472168: quodlibet: libffi built from separate source, pleae b-d on libffi-dev Severity set to `serious' from `important' thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#476679: setting package to jppy-doc jppy-jpilot-plugins python-jppy jppy jppy-lbdb-module, tagging 476679 ...
# Automatically generated email from bts, devscripts version 2.10.26 # # jppy (0.0.44-1) UNRELEASED; urgency=low # # * New upstream release (closes: #445379, #476679). # * Changed maintainer address to my address, since the mailing list posting #policy is too restrictive (closes: #479499). # package jppy-doc jppy-jpilot-plugins python-jppy jppy jppy-lbdb-module tags 476679 + pending tags 479499 + pending tags 445379 + pending -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#479499: Bug#445379: Status: python-jppy: module is linked to libpython
also sprach Josselin Mouette [EMAIL PROTECTED] [2008.05.05.0858 +0100]: Sorry; I’m attaching the full bounce that I received. You are probably looking for [EMAIL PROTECTED] OTOH, this may be a misconfiguration on the BTS side if the address used to be [EMAIL PROTECTED] and is now [EMAIL PROTECTED] I’m ccing [EMAIL PROTECTED] Well, our users want to post as well, so I am changing the maintainer address to my own in the next upload. -- .''`. martin f. krafft [EMAIL PROTECTED] : :' : proud Debian developer, author, administrator, and user `. `'` http://people.debian.org/~madduck - http://debiansystem.info `- Debian - when you have better things to do than fixing systems the mind of the thoroughly well-informed man is a dreadful thing. it is like a bric-à-brac shop, all monsters and dust, with everything priced above its proper value. -- oscar wilde digital_signature_gpg.asc Description: Digital signature (see http://martin-krafft.net/gpg/)
Bug#479514: kmchart_1.1.5(sparc/unstable): FTBFS, missing dependency on libtool
Package: kmchart Version: 1.1.5 Severity: serious There was an error while trying to autobuild your package: Automatic build of kmchart_1.1.5 on lebrun by sbuild/sparc 98 Build started at 20080505-0717 [...] ** Using build dependencies supplied by package: Build-Depends: autoconf, debhelper (= 5), libpcp3-dev, libqt4-dev [...] checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ISO C89... none needed checking for gmake... no checking for make... /usr/bin/make checking for glibtool... no checking for libtool... no FATAL ERROR: libtool does not seem to be installed. kmchart cannot be built without a working GNU libtool installation. make[1]: *** [configure] Error 1 make[1]: Leaving directory `/build/buildd/kmchart-1.1.5' make: *** [.census] Error 2 dpkg-buildpackage: failure: debian/rules build gave error exit status 2 A full build log can be found at: http://buildd.debian.org/build.php?arch=sparcpkg=kmchartver=1.1.5 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#479513: telegnome_0.1.0-1(sparc/unstable): unsatisfied build dependencies: gnome-doc-utils = 0.3.2
Package: telegnome Version: 0.1.0-1 Severity: serious There was an error while trying to autobuild your package: Automatic build of telegnome_0.1.0-1 on lebrun by sbuild/sparc 98 Build started at 20080505-0603 [...] ** Using build dependencies supplied by package: Build-Depends: debhelper (= 5.0.0), pkg-config, libglib2.0-dev (= 2.12), libgtk2.0-dev, libgnomeui-dev, libgnomevfs2-dev [...] checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ISO C89... none needed checking dependency style of gcc... gcc3 checking whether gcc understands -Wno-sign-compare... yes checking what warning flags to pass to the C compiler... -Wall -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wno-sign-compare checking what language compliance flags to pass to the C compiler... checking for pkg-config... /usr/bin/pkg-config checking pkg-config is at least version 0.9.0... yes configure: error: gnome-doc-utils = 0.3.2 not found make: *** [configure-stamp] Error 1 dpkg-buildpackage: failure: debian/rules build gave error exit status 2 A full build log can be found at: http://buildd.debian.org/build.php?arch=sparcpkg=telegnomever=0.1.0-1 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: setting package to jppy-doc jppy-jpilot-plugins python-jppy jppy jppy-lbdb-module, tagging 476679 ...
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.10.26 # # jppy (0.0.44-1) UNRELEASED; urgency=low # # * New upstream release (closes: #445379, #476679). # * Changed maintainer address to my address, since the mailing list posting #policy is too restrictive (closes: #479499). # package jppy-doc jppy-jpilot-plugins python-jppy jppy jppy-lbdb-module Ignoring bugs not assigned to: jppy-doc python-jppy jppy-jpilot-plugins jppy jppy-lbdb-module tags 476679 + pending Bug#476679: fails to start with python2.5 There were no tags set. Tags added: pending tags 479499 + pending Bug#479499: jppy: maintainer address rejects mail There were no tags set. Tags added: pending tags 445379 + pending Bug#445379: python-jppy: module is linked to libpython Tags were: patch Tags added: pending End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#469338: unionfs-modules does not work with 2.6.24-1
José L. Redrejo Rodríguez wrote: Hi, linux 2.6.26 in Debian already includes your patch. Please, could you upload the new version of linux-modules-extra for this kernel? s/2.6.26/2.6.25/ and yes, i'm aware of the things.. -- Address:Daniel Baumann, Burgunderstrasse 3, CH-4562 Biberist Email: [EMAIL PROTECTED] Internet: http://people.panthera-systems.net/~daniel-baumann/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#476018: [pkg-GD-devel] Bug#476018: Patch to fix these FTBFS bugs.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Fri, May 02, 2008 at 01:41:04PM +0530, Kumar Appaiah wrote: Please find attached a patch to fix this bug. The patch does the following: 1. Regenerates the copyright hints. 2. Removes the -Wl,--disable-rpath ld flag, which doesn't seem to exist. Anyway, rpath issues don't arise since --disable-rpath is passed to configure anyway. 3. Adds a proper check to detect cross building. I hope you are able to use this patch to fix this RC bug. Thanks for the patch. Do you know of any documentation about that cross building handling - is it it Debian Policy, some common best practice documented on the wiki or just something you find nice yourself and believe doesn't hurt? Kind regards, - Jonas - -- * Jonas Smedegaard - idealist og Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ - Enden er nær: http://www.shibumi.org/eoti.htm -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFIHsuan7DbMsAkQLgRAmvAAJ92eIXyhBL0asnCWalquKby+X37NQCeMPz+ W6kayU3EF57iRgQ7yK8MLpU= =z3P3 -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: severity of 475691 is normal
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.10.13 severity 475691 normal Bug#475691: munin-node: Hang the boot because it fail to put daemon in the background Severity set to `normal' 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#479499: jppy: maintainer address rejects mail
Lucas, On Mon, 05 May 2008, Lucas Nussbaum wrote: On 01/05/08 at 10:51 +0100, [EMAIL PROTECTED] wrote: You are not allowed to post to this mailing list, and your message has been automatically rejected. If you think that your messages are being rejected in error, contact the mailing list owner at [EMAIL PROTECTED] Please at least moderate those mails. I've changed to moderate non-member posts. Nick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#478420: marked as done ([audacious] Segmentation Fault Debian Lenny)
Your message dated Mon, 05 May 2008 10:40:35 +0200 with message-id [EMAIL PROTECTED] and subject line #478420: audacious: Segmentation Fault Debian Lenny has caused the Debian Bug report #478420, regarding [audacious] Segmentation Fault Debian 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.) -- 478420: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=478420 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: audacious Version: 1.4.6-2 Severity: critical Audacious crash with segmentation fault error. --- System information. --- Architecture: i386 Kernel: Linux 2.6.22-3-686 Debian Release: lenny/sid 500 unstableoss.oracle.com 500 testing security.debian.org 500 testing ftp.debian.org --- Package information. --- Depends(Version) | Installed -+-= audacious-plugins (= 1.4.1) | 1.4.4-1 audacious-plugins ( 1.5~) | 1.4.4-1 dbus | 1.1.20-1 gtk2-engines-pixbuf | 2.12.9-2 libatk1.0-0 (= 1.20.0) | 1.20.0-1 libaudclient1| 1.4.6-2 libc6 (= 2.7-1) | 2.7-10 libcairo2 (= 1.4.0) | 1.4.14-1 libdbus-1-3 (= 1.1.1) | 1.1.20-1 libdbus-glib-1-2 (= 0.74) | 0.74-1 libglade2-0 (= 1:2.6.1) | 1:2.6.2-1 libglib2.0-0 (= 2.14.0) | 2.16.1-2 libgtk2.0-0 (= 2.12.0) | 2.12.9-2 libmcs1 | 0.7.0-1 libmowgli1 | 0.6.1-1 libpango1.0-0(= 1.18.4) | 1.20.2-2 libsamplerate0 | 0.1.3-1 libx11-6 | 2:1.0.3-7 libxml2 | 2.6.31.dfsg-2 signature.asc Description: Esta é uma parte de mensagem assinada digitalmente ---End Message--- ---BeginMessage--- Hello, This bug has already been reported several times. You probably have a old CPU withtout SSE2 and audacious has been built with it (sorry for the mistake). Current version in unstable is fixed, as well as all incoming releases. Best regards, Adam. PS: Audacious 1.5 will enter lenny soon, we're working on it. ---End Message---
Bug#479513: marked as done (telegnome_0.1.0-1(sparc/unstable): unsatisfied build dependencies: gnome-doc-utils = 0.3.2)
Your message dated Mon, 05 May 2008 09:17:04 + with message-id [EMAIL PROTECTED] and subject line Bug#479513: fixed in telegnome 0.1.0-2 has caused the Debian Bug report #479513, regarding telegnome_0.1.0-1(sparc/unstable): unsatisfied build dependencies: gnome-doc-utils = 0.3.2 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [EMAIL PROTECTED] immediately.) -- 479513: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=479513 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: telegnome Version: 0.1.0-1 Severity: serious There was an error while trying to autobuild your package: Automatic build of telegnome_0.1.0-1 on lebrun by sbuild/sparc 98 Build started at 20080505-0603 [...] ** Using build dependencies supplied by package: Build-Depends: debhelper (= 5.0.0), pkg-config, libglib2.0-dev (= 2.12), libgtk2.0-dev, libgnomeui-dev, libgnomevfs2-dev [...] checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ISO C89... none needed checking dependency style of gcc... gcc3 checking whether gcc understands -Wno-sign-compare... yes checking what warning flags to pass to the C compiler... -Wall -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wno-sign-compare checking what language compliance flags to pass to the C compiler... checking for pkg-config... /usr/bin/pkg-config checking pkg-config is at least version 0.9.0... yes configure: error: gnome-doc-utils = 0.3.2 not found make: *** [configure-stamp] Error 1 dpkg-buildpackage: failure: debian/rules build gave error exit status 2 A full build log can be found at: http://buildd.debian.org/build.php?arch=sparcpkg=telegnomever=0.1.0-1 ---End Message--- ---BeginMessage--- Source: telegnome Source-Version: 0.1.0-2 We believe that the bug you reported is fixed in the latest version of telegnome, which is due to be installed in the Debian FTP archive: telegnome_0.1.0-2.diff.gz to pool/main/t/telegnome/telegnome_0.1.0-2.diff.gz telegnome_0.1.0-2.dsc to pool/main/t/telegnome/telegnome_0.1.0-2.dsc telegnome_0.1.0-2_i386.deb to pool/main/t/telegnome/telegnome_0.1.0-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. Colin Watson [EMAIL PROTECTED] (supplier of updated telegnome 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: Mon, 05 May 2008 10:06:10 +0100 Source: telegnome Binary: telegnome Architecture: source i386 Version: 0.1.0-2 Distribution: unstable Urgency: low Maintainer: Colin Watson [EMAIL PROTECTED] Changed-By: Colin Watson [EMAIL PROTECTED] Description: telegnome - A graphical teletext viewer Closes: 479513 Changes: telegnome (0.1.0-2) unstable; urgency=low . * Build-depend on gnome-doc-utils (= 0.3.2) (closes: #479513). Checksums-Sha1: 7ebb8cdfb7cea90f106d7f0e8fa8bad70e8ef8cc 1133 telegnome_0.1.0-2.dsc ba637c473328c01999e1c861af72a8e601966883 5204 telegnome_0.1.0-2.diff.gz 1f5de43270c2007e616840b855bc41eaea6ca12d 105846 telegnome_0.1.0-2_i386.deb Checksums-Sha256: ad28e6d952fc8feb2001106188353127e1c5b620f2236230607dfb0be5a1f5a0 1133 telegnome_0.1.0-2.dsc cc6f4493f26a5132e0b9d2058841aff3c6835bf260349d88b8eb3139a48bcbc5 5204 telegnome_0.1.0-2.diff.gz c520cb7522ca59d03964cb50f6324bc82a24eee103fb155f4f9d0203e5fc09a2 105846 telegnome_0.1.0-2_i386.deb Files: 556e758a147c82a46ac94e1a4afc3b6a 1133 gnome optional telegnome_0.1.0-2.dsc 3bae0b8f7aef50aa07cdc6cec3bc4bbd 5204 gnome optional telegnome_0.1.0-2.diff.gz c1c3de92583fbfeb1d536f1594abf850 105846 gnome optional telegnome_0.1.0-2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Colin Watson [EMAIL PROTECTED] -- Debian developer iD8DBQFIHs4j9t0zAhD6TNERAk75AJ9g+qyAGpImmtpOsjSkRgj8QLWVFQCeNcZc D/EdXhJvjJESbLlCUl1/keU= =fcoe -END PGP SIGNATURE- ---End Message---
Bug#479494: marked as done (python-ctypes: uninstallable due to libffi4 dependency)
Your message dated Mon, 05 May 2008 09:02:06 + with message-id [EMAIL PROTECTED] and subject line Bug#479494: fixed in ctypes 1.0.2-5 has caused the Debian Bug report #479494, regarding python-ctypes: uninstallable due to libffi4 dependency 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.) -- 479494: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=479494 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: python-ctypes Version: 1.0.2-4 Severity: serious Hello, currently, python-ctypes does not install due to it's dependency on libffi4 which has intentionally stopped building by the gcc-maintainers starting with gcc-4.3 (4.3.0-4) - see also #479115. Could you please instead depend on libffi5. Thanks for your work regards Mario -- A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? signature.asc Description: Digital signature ---End Message--- ---BeginMessage--- Source: ctypes Source-Version: 1.0.2-5 We believe that the bug you reported is fixed in the latest version of ctypes, which is due to be installed in the Debian FTP archive: ctypes_1.0.2-5.diff.gz to pool/main/c/ctypes/ctypes_1.0.2-5.diff.gz ctypes_1.0.2-5.dsc to pool/main/c/ctypes/ctypes_1.0.2-5.dsc python-ctypes_1.0.2-5_i386.deb to pool/main/c/ctypes/python-ctypes_1.0.2-5_i386.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Debian Python Modules Team [EMAIL PROTECTED] (supplier of updated ctypes 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: Mon, 05 May 2008 09:59:16 +0200 Source: ctypes Binary: python-ctypes Architecture: source i386 Version: 1.0.2-5 Distribution: unstable Urgency: low Maintainer: Ganesan Rajagopal [EMAIL PROTECTED] Changed-By: Debian Python Modules Team [EMAIL PROTECTED] Description: python-ctypes - Python package to create and manipulate C data types Closes: 479494 Changes: ctypes (1.0.2-5) unstable; urgency=low . [ Raphaël Hertzog ] * Build-Depend on libffi-dev instead of libffi4-dev. Should enable the rebuild with libffi5. Closes: #479494 Checksums-Sha1: 86aad02eea5f7e85ceec6158aa68f7b488c31e3a 1329 ctypes_1.0.2-5.dsc d721844197f422c3b76faa115ede8dd1ae4412ab 6236 ctypes_1.0.2-5.diff.gz 6ce9be092145c4c250b7a2eef50c6a2c819ef10b 157096 python-ctypes_1.0.2-5_i386.deb Checksums-Sha256: 14483809a78cf3d211a39c97f262bbc2696631c8dfcbdef7fde714abf02d81b3 1329 ctypes_1.0.2-5.dsc 413aae6ad205a9bddfd69f66e2cca758525a27e9a32dd5a35a6408458fae1bee 6236 ctypes_1.0.2-5.diff.gz 394ac6f3a801721ae3cec85110fd1d087dcfa95eef0a15373dc3bbf1907245a6 157096 python-ctypes_1.0.2-5_i386.deb Files: b6ea58296a7d0556aa6be51fb5ec2abf 1329 python optional ctypes_1.0.2-5.dsc ae2e56811459e1586889cea07b3d00c0 6236 python optional ctypes_1.0.2-5.diff.gz 94a5e3fa36cd93dff59575ec4d44c3ac 157096 python optional python-ctypes_1.0.2-5_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Signed by Raphael Hertzog iD8DBQFIHsDkvPbGD26BadIRAvWJAKCN3sV3ezcJgP8a1/+Ub6bT8UnOgwCgqG2F QdMCiFPH6XehcEd/UcNo9mo= =iVmF -END PGP SIGNATURE- ---End Message---
Bug#476018: [pkg-GD-devel] Bug#476018: Patch to fix these FTBFS bugs.
On Mon, May 05, 2008 at 10:55:54AM +0200, Jonas Smedegaard wrote: Thanks for the patch. Do you know of any documentation about that cross building handling - is it it Debian Policy, some common best practice documented on the wiki or just something you find nice yourself and believe doesn't hurt? Hi! Well, it's what Neil Williams suggests always, and he has filed several bugs to do it. An example is here: http://article.gmane.org/gmane.linux.debian.devel.mentors/27625/match=cross Some bugs are here: http://bugs.debian.org/cgi-bin/[EMAIL PROTECTED] I think it's better to comply with his request, though I am sure you can ask him for details. It bascially is useful for his use for emdebian, and saves him some effort, I guess. HTH, and thanks for the response. Kumar -- Kumar Appaiah, 458, Jamuna Hostel, Indian Institute of Technology Madras, Chennai - 600 036 signature.asc Description: Digital signature
Bug#479220: Additional information
On Sat, May 03, 2008 at 08:36:59PM +0200, Sven Joachim wrote: Am 03.05.2008 um 20:05 schrieb Adrian Bunk: What fails is the update-alternatives invocation in irssi's prerm. That's because liblocale-gettext-perl was still the old version linked against perlapi-5.8.*, this causes the symbol lookup error. The new version had not been unpacked yet. No, it's the other way around. The new liblocale-gettext-perl is unpacked but perl-base isn't yet. The problem is that while Dpkg::Gettext (and Debconf::Gettext for that matter) do the right thing with an eval 'use Locale::gettext', the error (presumably from dlopen()) isn't caught: # perl -le 'eval use Locale::gettext; print got: $@ if $@; exit 0'; echo $? perl: symbol lookup error: /usr/lib/perl5/auto/Locale/gettext/gettext.so: undefined symbol: Perl_Istack_sp_ptr 127 No fix yet, but the only way out I see is having some package(s?) pre-depend on the new perl-base. Fixing the eval/dlopen interaction in perl is out of the question because this is happening when the old perl-base version is still installed. Any help and ideas welcome. -- Niko Tyni [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: merging 479202 479469
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.10.25+local merge 479202 479469 Bug#479202: fields tries to use Hash::Util Bug#479469: fields uses Hash::Util which is not in perl-base, breaks debconf Merged 479202 479469. 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#479501: [pkg-lighttpd] Bug#479501: file conflicts between packages
On Mon, May 05, 2008 at 07:22:17AM +, Michael Ablassmeier wrote:
Package: cherokee, lighttpd
Severity: serious
Justification: policy violation
hi,
both cherokee and lighttpd ship
`/usr/share/man/man1/spawn-fcgi.1.gz'
but do neither conflict, nor add a diversion, thus fail to be installed in the
same environment:
Unpacking lighttpd (from .../lighttpd_1.4.19-2_amd64.deb) ...
dpkg: error processing /var/cache/apt/archives/lighttpd_1.4.19-2_amd64.deb
(--unpack):
trying to overwrite `/usr/share/man/man1/spawn-fcgi.1.gz', which is also
in package cherokee
Processing triggers for man-db ...
Errors were encountered while processing:
/var/cache/apt/archives/lighttpd_1.4.19-2_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
bye,
- michael
Hmm for all I can see, both spawn-fcgi seem to come from the very
same implementation, they are totally compatible wrt arguments on the
CLI, and their usage is almost the same (except for version and
copyright informations, which suggest abuse from one of both binaries,
if not both, but that's not the question here).
Given that, I assume alternative is the best way to deal with this,
and cherokee's man page is better, so I'd suggest the cherokee
spawn-fcgi{,.1.gz} to be the highest priority.
Gunnar: If you agree, I'll fix that in a lighttpd 1.4.19-3 upload, so
you'd have to conflict with lighttpd 1.4.19-3 and I'll probably have
to conflict with cherokee 0.6.1-2 so that one is forced to migrate to
a package that uses alternatives before trying to coinstall.
Cheers,
--
·O· Pierre Habouzit
··O[EMAIL PROTECTED]
OOOhttp://www.madism.org
pgpr9aCwe6dvp.pgp
Description: PGP signature
Bug#479029: marked as done (Segfault on loading programm icons)
Your message dated Mon, 05 May 2008 09:47:03 +
with message-id [EMAIL PROTECTED]
and subject line Bug#479029: fixed in fraqtive 0.4.2-2
has caused the Debian Bug report #479029,
regarding Segfault on loading programm icons
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.)
--
479029: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=479029
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
---BeginMessage---
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Package: qt4-x11
Severity: grave
Version: 4.4.0~rc1-5
Hello,
I just noticed, that my package fraqtive (uploaded yesterday) segfaults
directly on starting. Here the gdb output:
(gdb) run
Starting program: /usr/bin/fraqtive
[Thread debugging using libthread_db enabled]
[New Thread 0xb6da2a40 (LWP 7230)]
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xb6da2a40 (LWP 7230)]
0xb75487cf in QtPrivate::QStringList_contains () from
/usr/lib/libQtCore.so.4
(gdb) bt
#0 0xb75487cf in QtPrivate::QStringList_contains () from
/usr/lib/libQtCore.so.4
#1 0xb75d0c92 in QFactoryLoader::instance () from /usr/lib/libQtCore.so.4
#2 0xb789fc88 in QIcon::addFile () from /usr/lib/libQtGui.so.4
#3 0x0808f7a6 in MultiIconEngine (this=0x9c0c738, [EMAIL PROTECTED])
at multiiconengine.cpp:43
#4 0x0808f870 in MultiIconEnginePlugin::create (this=0x827b9a8,
[EMAIL PROTECTED]) at multiiconengine.cpp:90
#5 0xb789fcba in QIcon::addFile () from /usr/lib/libQtGui.so.4
#6 0x0808f7a6 in MultiIconEngine (this=0x9c0c250, [EMAIL PROTECTED])
at multiiconengine.cpp:43
#7 0x0808f870 in MultiIconEnginePlugin::create (this=0x827b9a8,
[EMAIL PROTECTED]) at multiiconengine.cpp:90
#8 0xb789fcba in QIcon::addFile () from /usr/lib/libQtGui.so.4
#9 0x0808f7a6 in MultiIconEngine (this=0x9c0bd68, [EMAIL PROTECTED])
at multiiconengine.cpp:43
#10 0x0808f870 in MultiIconEnginePlugin::create (this=0x827b9a8,
[EMAIL PROTECTED]) at multiiconengine.cpp:90
#11 0xb789fcba in QIcon::addFile () from /usr/lib/libQtGui.so.4
#12 0x0808f7a6 in MultiIconEngine (this=0x9c0b880, [EMAIL PROTECTED])
at multiiconengine.cpp:43
#13 0x0808f870 in MultiIconEnginePlugin::create (this=0x827b9a8,
[EMAIL PROTECTED]) at multiiconengine.cpp:90
#14 0xb789fcba in QIcon::addFile () from /usr/lib/libQtGui.so.4
#15 0x0808f7a6 in MultiIconEngine (this=0x9c0b398, [EMAIL PROTECTED])
at multiiconengine.cpp:43
#16 0x0808f870 in MultiIconEnginePlugin::create (this=0x827b9a8,
[EMAIL PROTECTED]) at multiiconengine.cpp:90
#17 0xb789fcba in QIcon::addFile () from /usr/lib/libQtGui.so.4
#18 0x0808f7a6 in MultiIconEngine (this=0x9c0aeb0, [EMAIL PROTECTED])
at multiiconengine.cpp:43
#19 0x0808f870 in MultiIconEnginePlugin::create (this=0x827b9a8,
[EMAIL PROTECTED]) at multiiconengine.cpp:90
#20 0xb789fcba in QIcon::addFile () from /usr/lib/libQtGui.so.4
#21 0x0808f7a6 in MultiIconEngine (this=0x9c0a9c8, [EMAIL PROTECTED])
at multiiconengine.cpp:43
#22 0x0808f870 in MultiIconEnginePlugin::create (this=0x827b9a8,
[EMAIL PROTECTED]) at multiiconengine.cpp:90
#23 0xb789fcba in QIcon::addFile () from /usr/lib/libQtGui.so.4
#24 0x0808f7a6 in MultiIconEngine (this=0x9c0a4e0, [EMAIL PROTECTED])
at multiiconengine.cpp:43
#25 0x0808f870 in MultiIconEnginePlugin::create (this=0x827b9a8,
[EMAIL PROTECTED]) at multiiconengine.cpp:90
#26 0xb789fcba in QIcon::addFile () from /usr/lib/libQtGui.so.4
#27 0x0808f7a6 in MultiIconEngine (this=0x9c09ff8, [EMAIL PROTECTED])
at multiiconengine.cpp:43
#28 0x0808f870 in MultiIconEnginePlugin::create (this=0x827b9a8,
[EMAIL PROTECTED]) at multiiconengine.cpp:90
#29 0xb789fcba in QIcon::addFile () from /usr/lib/libQtGui.so.4
#30 0x0808f7a6 in MultiIconEngine (this=0x9c09b10, [EMAIL PROTECTED])
at multiiconengine.cpp:43
#31 0x0808f870 in MultiIconEnginePlugin::create (this=0x827b9a8,
[EMAIL PROTECTED]) at multiiconengine.cpp:90
#32 0xb789fcba in QIcon::addFile () from /usr/lib/libQtGui.so.4
#33 0x0808f7a6 in MultiIconEngine (this=0x9c09628, [EMAIL PROTECTED])
at multiiconengine.cpp:43
#34 0x0808f870 in MultiIconEnginePlugin::create (this=0x827b9a8,
[EMAIL PROTECTED]) at multiiconengine.cpp:90
The affected lines are:
39 for ( int i = 0; sizes[ i ] 0; i++ ) {
40 int size = sizes[ i ];
41 QString iconName = baseName + QString::number( size ) + .png;
42 if ( QFile::exists( iconName ) )
43 m_icon.addFile( iconName, QSize( size, size ) );
44 }
88 QIconEngine* MultiIconEnginePlugin::create( const QString fileName )
89 {
90 return new MultiIconEngine( fileName );
91 }
I rebuilded all 0.4.x fraqtive releases with the newer qt4-x11 builds
and all versions
Bug#467457: marked as done (schroot: FTBFS with g++-4.3: Missing includes)
Your message dated Mon, 05 May 2008 10:17:04 + with message-id [EMAIL PROTECTED] and subject line Bug#467457: fixed in schroot 1.2.0-1 has caused the Debian Bug report #467457, regarding schroot: FTBFS with g++-4.3: Missing includes 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.) -- 467457: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=467457 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: schroot Version: 1.1.6-1 Severity: important User: [EMAIL PROTECTED] Usertags: ftbfs-gcc-4.3 From my pbuilder build log, with g++ - g++-4.3: ... /bin/bash ../libtool --tag=CXX --mode=compile x86_64-linux-gnu-g++ -D_GNU_SOURCE -I. -I.. -I../../../sbuild-I../../.. -pedantic -Wall -Wcast-align -Wwrite-strings -Wswitch-default -Wcast-qual -Wunused-variable -Wredundant-decls -Wctor-dtor-privacy -Wnon-virtual-dtor -Wreorder -Wold-style-cast -Woverloaded-virtual -fstrict-aliasing -g -O2 -MT sbuild-dirstream.lo -MD -MP -MF .deps/sbuild-dirstream.Tpo -c -o sbuild-dirstream.lo ../../../sbuild/sbuild-dirstream.cc x86_64-linux-gnu-g++ -D_GNU_SOURCE -I. -I.. -I../../../sbuild -I../../.. -pedantic -Wall -Wcast-align -Wwrite-strings -Wswitch-default -Wcast-qual -Wunused-variable -Wredundant-decls -Wctor-dtor-privacy -Wnon-virtual-dtor -Wreorder -Wold-style-cast -Woverloaded-virtual -fstrict-aliasing -g -O2 -MT sbuild-dirstream.lo -MD -MP -MF .deps/sbuild-dirstream.Tpo -c ../../../sbuild/sbuild-dirstream.cc -o sbuild-dirstream.o In file included from ../../../sbuild/sbuild-dirstream.cc:21: ../../../sbuild/sbuild-dirstream.h: In constructor 'sbuild::direntry::direntry()': ../../../sbuild/sbuild-dirstream.h:45: error: 'memset' is not a member of 'std' ../../../sbuild/sbuild-dirstream.h: In constructor 'sbuild::direntry::direntry(const dirent*)': ../../../sbuild/sbuild-dirstream.h:53: error: 'memcpy' is not a member of 'std' ../../../sbuild/sbuild-dirstream.h: In copy constructor 'sbuild::direntry::direntry(const sbuild::direntry)': ../../../sbuild/sbuild-dirstream.h:61: error: 'memcpy' was not declared in this scope make[4]: *** [sbuild-dirstream.lo] Error 1 make[4]: Leaving directory `/tmp/buildd/schroot-1.1.6/debian/build/sbuild' make[3]: *** [all] Error 2 make[3]: Leaving directory `/tmp/buildd/schroot-1.1.6/debian/build/sbuild' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/tmp/buildd/schroot-1.1.6/debian/build' make[1]: *** [all] Error 2 make[1]: Leaving directory `/tmp/buildd/schroot-1.1.6/debian/build' make: *** [build-stamp] Error 2 dpkg-buildpackage: failure: debian/rules build gave error exit status 2 That one looks like a missing #include cstring -- there may be other missing includes in other source files. -- Daniel Schepler ---End Message--- ---BeginMessage--- Source: schroot Source-Version: 1.2.0-1 We believe that the bug you reported is fixed in the latest version of schroot, which is due to be installed in the Debian FTP archive: dchroot-dsa_1.2.0-1_powerpc.deb to pool/main/s/schroot/dchroot-dsa_1.2.0-1_powerpc.deb dchroot_1.2.0-1_powerpc.deb to pool/main/s/schroot/dchroot_1.2.0-1_powerpc.deb libsbuild-dev_1.2.0-1_powerpc.deb to pool/main/s/schroot/libsbuild-dev_1.2.0-1_powerpc.deb libsbuild-doc_1.2.0-1_all.deb to pool/main/s/schroot/libsbuild-doc_1.2.0-1_all.deb schroot-common_1.2.0-1_all.deb to pool/main/s/schroot/schroot-common_1.2.0-1_all.deb schroot_1.2.0-1.diff.gz to pool/main/s/schroot/schroot_1.2.0-1.diff.gz schroot_1.2.0-1.dsc to pool/main/s/schroot/schroot_1.2.0-1.dsc schroot_1.2.0-1_powerpc.deb to pool/main/s/schroot/schroot_1.2.0-1_powerpc.deb schroot_1.2.0.orig.tar.gz to pool/main/s/schroot/schroot_1.2.0.orig.tar.gz A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Roger Leigh [EMAIL PROTECTED] (supplier of updated schroot 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: Mon, 05 May 2008 00:09:41 +0100 Source: schroot Binary: schroot-common libsbuild-dev libsbuild-doc schroot dchroot dchroot-dsa Architecture: source all powerpc Version: 1.2.0-1 Distribution: unstable Urgency: low Maintainer: Debian buildd-tools Developers [EMAIL PROTECTED]
Bug#479529: cacao_0.99~rc3-1(mips/experimental): FTBFS: Error: opcode not supported on this processor
Package: cacao Version: 0.99~rc3-1 Severity: serious Hi, your package failed to build from source. | Automatic build of cacao_0.99~rc3-1 on signy by sbuild/mips 98-farm | Build started at 20080505-0116 | ** | Checking available source versions... | Fetching source files... | Reading package lists... | Building dependency tree... | Need to get 3598kB of source archives. | Get:1 http://sinclair.farm.ftbfs.de experimental/main cacao 0.99~rc3-1 (dsc) [1338B] | Get:2 http://sinclair.farm.ftbfs.de experimental/main cacao 0.99~rc3-1 (tar) [3588kB] | Get:3 http://sinclair.farm.ftbfs.de experimental/main cacao 0.99~rc3-1 (diff) [8880B] | Fetched 3598kB in 4s (724kB/s) | Download complete and in download only mode | ** Using build dependencies supplied by package: | Build-Depends: debhelper (= 5), cdbs (= 0.4.17), default-jdk-builddep, classpath (= 2:0.96.1), classpath-common (= 2:0.96.1), zlib1g-dev, libltdl3-dev, zip | Checking for already installed source dependencies... [...] | make[7]: Entering directory `/build/buildd/cacao-0.99~rc3/src/vm/jit/mips' | /bin/sh ../../../../libtool --mode=compile cc -I../../../../src -I../../../.. -I../../../../src -D__MIPS__ -D__LINUX__ -ansi -pedantic -Wall -Wno-long-long -D_POSIX_C_SOURCE=199506L -D_XOPEN_SOURCE=500 -D_XOPEN_SOURCE_EXTENDED -D_BSD_SOURCE -g -O2 -g -Wall -O2 -c -o asmpart.lo asmpart.S | mkdir .libs | cc -I../../../../src -I../../../.. -I../../../../src -D__MIPS__ -D__LINUX__ -ansi -pedantic -Wall -Wno-long-long -D_POSIX_C_SOURCE=199506L -D_XOPEN_SOURCE=500 -D_XOPEN_SOURCE_EXTENDED -D_BSD_SOURCE -g -O2 -g -Wall -O2 -c asmpart.S -fPIC -DPIC -o .libs/asmpart.o | asmpart.S: Assembler messages: | asmpart.S:166: Error: opcode not supported on this processor: mips1 (mips1) `ldc1 $f12,4*8($8)' | asmpart.S:167: Error: opcode not supported on this processor: mips1 (mips1) `ldc1 $f14,5*8($8)' | asmpart.S:241: Warning: No .cprestore pseudo-op used in PIC code | asmpart.S:280: Warning: No .cprestore pseudo-op used in PIC code | asmpart.S:305: Error: opcode not supported on this processor: mips1 (mips1) `sdc1 $f12,(4+(0))*4($29)' | asmpart.S:305: Error: opcode not supported on this processor: mips1 (mips1) `sdc1 $f14,(6+(0))*4($29)' | asmpart.S:306: Error: opcode not supported on this processor: mips1 (mips1) `sdc1 $f8,(8+((4+2)))*4($29)' | asmpart.S:306: Error: opcode not supported on this processor: mips1 (mips1) `sdc1 $f10,(10+((4+2)))*4($29)' | asmpart.S:306: Error: opcode not supported on this processor: mips1 (mips1) `sdc1 $f16,(12+((4+2)))*4($29)' | asmpart.S:306: Error: opcode not supported on this processor: mips1 (mips1) `sdc1 $f18,(14+((4+2)))*4($29)' | asmpart.S:336: Warning: No .cprestore pseudo-op used in PIC code | asmpart.S:358: Error: opcode not supported on this processor: mips1 (mips1) `ldc1 $f12,(4+(0))*4($29)' | asmpart.S:358: Error: opcode not supported on this processor: mips1 (mips1) `ldc1 $f14,(6+(0))*4($29)' | asmpart.S:359: Error: opcode not supported on this processor: mips1 (mips1) `ldc1 $f8,(8+((4+2)))*4($29)' | asmpart.S:359: Error: opcode not supported on this processor: mips1 (mips1) `ldc1 $f10,(10+((4+2)))*4($29)' | asmpart.S:359: Error: opcode not supported on this processor: mips1 (mips1) `ldc1 $f16,(12+((4+2)))*4($29)' | asmpart.S:359: Error: opcode not supported on this processor: mips1 (mips1) `ldc1 $f18,(14+((4+2)))*4($29)' | asmpart.S:430: Error: opcode not supported on this processor: mips1 (mips1) `ldc1 $f20,-4*8($9)' | asmpart.S:431: Error: opcode not supported on this processor: mips1 (mips1) `ldc1 $f22,-3*8($9)' | asmpart.S:432: Error: opcode not supported on this processor: mips1 (mips1) `ldc1 $f24,-2*8($9)' | asmpart.S:433: Error: opcode not supported on this processor: mips1 (mips1) `ldc1 $f26,-1*8($9)' | asmpart.S:434: Error: opcode not supported on this processor: mips1 (mips1) `ldc1 $f28,-1*8($9)' | asmpart.S:435: Error: opcode not supported on this processor: mips1 (mips1) `ldc1 $f30,-1*8($9)' | asmpart.S:460: Warning: No .cprestore pseudo-op used in PIC code | asmpart.S:475: Error: opcode not supported on this processor: mips1 (mips1) `ll $2,0($4)' | asmpart.S:478: Error: opcode not supported on this processor: mips1 (mips1) `sc $8,0($4)' | asmpart.S:481: Error: opcode not supported on this processor: mips1 (mips1) `sync' | make[7]: *** [asmpart.lo] Error 1 | make[7]: Leaving directory `/build/buildd/cacao-0.99~rc3/src/vm/jit/mips' | make[6]: *** [all-recursive] Error 1 | make[6]: Leaving directory `/build/buildd/cacao-0.99~rc3/src/vm/jit/mips' | make[5]: *** [all-recursive] Error 1 | make[5]: Leaving directory `/build/buildd/cacao-0.99~rc3/src/vm/jit' | make[4]: *** [all-recursive] Error 1 | make[4]: Leaving directory `/build/buildd/cacao-0.99~rc3/src/vm' | make[3]: *** [all-recursive] Error 1 | make[3]: Leaving directory `/build/buildd/cacao-0.99~rc3/src' | make[2]: *** [all-recursive] Error 1 | make[2
Bug#479501: [pkg-lighttpd] Bug#479501: file conflicts between packages
Pierre, I am certain that spawn-fcgi comes from the Lighttpd team. Also
check out this source snippet from the cherokee:
http://svn.cherokee-project.com/browser/cherokee/trunk/contrib/spawn-fcgi.c
* File borrowed from lighttpd. I have only cleaned up the headers
* inclusion mess. Its original license follows:
*Alvaro Lopez Ortega [EMAIL PROTECTED]
So given that it's really from Lighttpd, and that it's likely that
future version will come from Lighttpd as well, not cherokee, shouldn't
we give Lighttpd priority?
Pierre Habouzit wrote:
On Mon, May 05, 2008 at 07:22:17AM +, Michael Ablassmeier wrote:
Package: cherokee, lighttpd
Severity: serious
Justification: policy violation
hi,
both cherokee and lighttpd ship
`/usr/share/man/man1/spawn-fcgi.1.gz'
but do neither conflict, nor add a diversion, thus fail to be installed in the
same environment:
Unpacking lighttpd (from .../lighttpd_1.4.19-2_amd64.deb) ...
dpkg: error processing /var/cache/apt/archives/lighttpd_1.4.19-2_amd64.deb
(--unpack):
trying to overwrite `/usr/share/man/man1/spawn-fcgi.1.gz', which is also in
package cherokee
Processing triggers for man-db ...
Errors were encountered while processing:
/var/cache/apt/archives/lighttpd_1.4.19-2_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
bye,
- michael
Hmm for all I can see, both spawn-fcgi seem to come from the very
same implementation, they are totally compatible wrt arguments on the
CLI, and their usage is almost the same (except for version and
copyright informations, which suggest abuse from one of both binaries,
if not both, but that's not the question here).
Given that, I assume alternative is the best way to deal with this,
and cherokee's man page is better, so I'd suggest the cherokee
spawn-fcgi{,.1.gz} to be the highest priority.
Gunnar: If you agree, I'll fix that in a lighttpd 1.4.19-3 upload, so
you'd have to conflict with lighttpd 1.4.19-3 and I'll probably have
to conflict with cherokee 0.6.1-2 so that one is forced to migrate to
a package that uses alternatives before trying to coinstall.
Cheers,
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#479220: Additional information
On Mon, 05 May 2008, Niko Tyni wrote: # perl -le 'eval use Locale::gettext; print got: $@ if $@; exit 0'; echo $? perl: symbol lookup error: /usr/lib/perl5/auto/Locale/gettext/gettext.so: undefined symbol: Perl_Istack_sp_ptr 127 No fix yet, but the only way out I see is having some package(s?) pre-depend on the new perl-base. Fixing the eval/dlopen interaction in perl is out of the question because this is happening when the old perl-base version is still installed. Any help and ideas welcome. I would suggest integrating liblocale-gettext-perl to perl-base. Maybe that should be suggested upstream? Cheers, -- Raphaël Hertzog Le best-seller français mis à jour pour Debian Etch : http://www.ouaza.com/livre/admin-debian/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#479535: dragonplayer_2.0-1(mips/experimental): FTBFS: No rule to make target `/usr/lib/libICE.so'
Package: dragonplayer Version: 2.0-1 Severity: serious Hi, your package failed to build from source. | Automatic build of dragonplayer_2.0-1 on signy by sbuild/mips 98-farm | Build started at 20080505-0807 | ** | Checking available source versions... | Fetching source files... | Reading package lists... | Building dependency tree... | Need to get 462kB of source archives. | Get:1 http://sinclair.farm.ftbfs.de experimental/main dragonplayer 2.0-1 (dsc) [823B] | Get:2 http://sinclair.farm.ftbfs.de experimental/main dragonplayer 2.0-1 (tar) [456kB] | Get:3 http://sinclair.farm.ftbfs.de experimental/main dragonplayer 2.0-1 (diff) [5682B] | Fetched 462kB in 0s (500kB/s) | Download complete and in download only mode | ** Using build dependencies supplied by package: | Build-Depends: cdbs, cmake, debhelper (= 6), docbook2x, kdebase-runtime-data, kdelibs5-dev, libphonon-dev, libxine-dev, quilt | Checking for already installed source dependencies... [...] | /usr/bin/cmake -E cmake_progress_report /build/buildd/dragonplayer-2.0/obj-mips-linux-gnu/CMakeFiles 22 | [ 46%] Building CXX object src/app/CMakeFiles/dragon.dir/TrackListDbusAdaptor.o | /usr/bin/g++ -g -O2 -g -Wall -O2 -Wnon-virtual-dtor -Wno-long-long -ansi -Wundef -Wcast-align -Wchar-subscripts -Wall -W -Wpointer-arith -Wformat-security -fno-exceptions -fno-check-new -fno-common -Woverloaded-virtual -fvisibility=hidden -fvisibility-inlines-hidden -DNDEBUG -I/build/buildd/dragonplayer-2.0/obj-mips-linux-gnu/src/app -I/build/buildd/dragonplayer-2.0/src/app -I/build/buildd/dragonplayer-2.0/obj-mips-linux-gnu/src -I/build/buildd/dragonplayer-2.0/src -I/usr/include/KDE -I/usr/include/qt4/QtDBus -I/usr/include/qt4/QtTest -I/usr/include/qt4/QtUiTools -I/usr/include/qt4/QtScript -I/usr/include/qt4/QtSvg -I/usr/include/qt4/QtXml -I/usr/include/qt4/QtSql -I/usr/include/qt4/QtOpenGL -I/usr/include/qt4/QtNetwork -I/usr/include/qt4/QtDesigner -I/usr/include/qt4/QtAssistant -I/usr/include/qt4/Qt3Support -I/usr/include/qt4/QtGui -I/usr/include/qt4/QtCore -I/usr/include/qt4/Qt -I/usr/share/qt4/mkspecs/default -I/usr/include/qt4 -D_BSD_SOURCE -o src/app/CMakeFiles/dragon.dir/TrackListDbusAdaptor.o -c /build/buildd/dragonplayer-2.0/obj-mips-linux-gnu/src/app/TrackListDbusAdaptor.cpp | In file included from /build/buildd/dragonplayer-2.0/obj-mips-linux-gnu/src/app/TrackListDbusAdaptor.cpp:79: | /usr/include/qt4/QtCore/qmap.h: In static member function 'static QMapKey, T::Node* QMapKey, T::concrete(QMapData::Node*) [with Key = QString, T = QVariant]': | /usr/include/qt4/QtCore/qmap.h:286: instantiated from 'const Key QMapKey, T::const_iterator::key() const [with Key = QString, T = QVariant]' | /usr/include/qt4/QtDBus/qdbusargument.h:309: instantiated from here | /usr/include/qt4/QtCore/qmap.h:146: warning: cast from 'char*' to 'QMapQString, QVariant::Node*' increases required alignment of target type | /usr/include/qt4/QtCore/qmap.h: In static member function 'static QMapKey, T::Node* QMapKey, T::concrete(QMapData::Node*) [with Key = int, T = QtConcurrent::ResultItem]': | /usr/include/qt4/QtCore/qmap.h:591: instantiated from 'void QMapKey, T::freeData(QMapData*) [with Key = int, T = QtConcurrent::ResultItem]' | /usr/include/qt4/QtCore/qmap.h:153: instantiated from 'QMapKey, T::~QMap() [with Key = int, T = QtConcurrent::ResultItem]' | /usr/include/qt4/QtCore/qtconcurrentresultstore.h:139: instantiated from here | /usr/include/qt4/QtCore/qmap.h:146: warning: cast from 'char*' to 'QMapint, QtConcurrent::ResultItem::Node*' increases required alignment of target type | /usr/include/qt4/QtCore/qlist.h: In member function 'void QListT::node_destruct(QListT::Node*, QListT::Node*) [with T = QVariant]': | /usr/include/qt4/QtCore/qlist.h:557: instantiated from 'void QListT::free(QListData::Data*) [with T = QVariant]' | /usr/include/qt4/QtCore/qlist.h:532: instantiated from 'QListT::~QList() [with T = QVariant]' | /usr/include/qt4/QtDBus/qdbusmessage.h:85: instantiated from here | /usr/include/qt4/QtCore/qlist.h:367: warning: cast from 'QListQVariant::Node*' to 'QVariant*' increases required alignment of target type | /usr/include/qt4/QtCore/qlist.h: In member function 'void QListT::node_construct(QListT::Node*, const T) [with T = QVariant]': | /usr/include/qt4/QtCore/qlist.h:424: instantiated from 'void QListT::append(const T) [with T = QVariant]' | /usr/include/qt4/QtCore/qlist.h:302: instantiated from 'QListT QListT::operator(const T) [with T = QVariant]' | /usr/include/qt4/QtDBus/qdbusmessage.h:87: instantiated from here | /usr/include/qt4/QtCore/qlist.h:340: warning: cast from 'QListQVariant::Node*' to 'QVariant*' increases required alignment of target type | /usr/include/qt4/QtCore/qlist.h: In member function 'void QListT::node_copy(QListT::Node*, QListT::Node*, QListT::Node*) [with T = QVariant]': | /usr/include/qt4/QtCore/qlist.h
Processed: severity of 479101 is grave
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.10.26 severity 479101 grave Bug#479101: linux-image-2.6.25-1-amd64: Kernel panic: Unable to mount root Severity set to `grave' from `normal' 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#479529: cacao_0.99~rc3-1(mips/experimental): FTBFS: Error: opcode not supported on this processor
On Mon, May 05, 2008 at 12:45:57PM +0200, Frank Lichtenheld wrote: Package: cacao Version: 0.99~rc3-1 Severity: serious Hi, your package failed to build from source. | Automatic build of cacao_0.99~rc3-1 on signy by sbuild/mips 98-farm | Build started at 20080505-0116 | ** | Checking available source versions... | Fetching source files... | Reading package lists... | Building dependency tree... | Need to get 3598kB of source archives. | Get:1 http://sinclair.farm.ftbfs.de experimental/main cacao 0.99~rc3-1 (dsc) [1338B] | Get:2 http://sinclair.farm.ftbfs.de experimental/main cacao 0.99~rc3-1 (tar) [3588kB] | Get:3 http://sinclair.farm.ftbfs.de experimental/main cacao 0.99~rc3-1 (diff) [8880B] | Fetched 3598kB in 4s (724kB/s) | Download complete and in download only mode | ** Using build dependencies supplied by package: | Build-Depends: debhelper (= 5), cdbs (= 0.4.17), default-jdk-builddep, classpath (= 2:0.96.1), classpath-common (= 2:0.96.1), zlib1g-dev, libltdl3-dev, zip | Checking for already installed source dependencies... [...] | make[7]: Entering directory `/build/buildd/cacao-0.99~rc3/src/vm/jit/mips' | /bin/sh ../../../../libtool --mode=compile cc -I../../../../src -I../../../.. -I../../../../src -D__MIPS__ -D__LINUX__ -ansi -pedantic -Wall -Wno-long-long -D_POSIX_C_SOURCE=199506L -D_XOPEN_SOURCE=500 -D_XOPEN_SOURCE_EXTENDED -D_BSD_SOURCE -g -O2 -g -Wall -O2 -c -o asmpart.lo asmpart.S | mkdir .libs | cc -I../../../../src -I../../../.. -I../../../../src -D__MIPS__ -D__LINUX__ -ansi -pedantic -Wall -Wno-long-long -D_POSIX_C_SOURCE=199506L -D_XOPEN_SOURCE=500 -D_XOPEN_SOURCE_EXTENDED -D_BSD_SOURCE -g -O2 -g -Wall -O2 -c asmpart.S -fPIC -DPIC -o .libs/asmpart.o | asmpart.S: Assembler messages: | asmpart.S:166: Error: opcode not supported on this processor: mips1 (mips1) `ldc1 $f12,4*8($8)' | asmpart.S:167: Error: opcode not supported on this processor: mips1 (mips1) `ldc1 $f14,5*8($8)' | asmpart.S:241: Warning: No .cprestore pseudo-op used in PIC code | asmpart.S:280: Warning: No .cprestore pseudo-op used in PIC code | asmpart.S:305: Error: opcode not supported on this processor: mips1 (mips1) `sdc1 $f12,(4+(0))*4($29)' | asmpart.S:305: Error: opcode not supported on this processor: mips1 (mips1) `sdc1 $f14,(6+(0))*4($29)' | asmpart.S:306: Error: opcode not supported on this processor: mips1 (mips1) `sdc1 $f8,(8+((4+2)))*4($29)' | asmpart.S:306: Error: opcode not supported on this processor: mips1 (mips1) `sdc1 $f10,(10+((4+2)))*4($29)' | asmpart.S:306: Error: opcode not supported on this processor: mips1 (mips1) `sdc1 $f16,(12+((4+2)))*4($29)' | asmpart.S:306: Error: opcode not supported on this processor: mips1 (mips1) `sdc1 $f18,(14+((4+2)))*4($29)' | asmpart.S:336: Warning: No .cprestore pseudo-op used in PIC code | asmpart.S:358: Error: opcode not supported on this processor: mips1 (mips1) `ldc1 $f12,(4+(0))*4($29)' | asmpart.S:358: Error: opcode not supported on this processor: mips1 (mips1) `ldc1 $f14,(6+(0))*4($29)' | asmpart.S:359: Error: opcode not supported on this processor: mips1 (mips1) `ldc1 $f8,(8+((4+2)))*4($29)' | asmpart.S:359: Error: opcode not supported on this processor: mips1 (mips1) `ldc1 $f10,(10+((4+2)))*4($29)' | asmpart.S:359: Error: opcode not supported on this processor: mips1 (mips1) `ldc1 $f16,(12+((4+2)))*4($29)' | asmpart.S:359: Error: opcode not supported on this processor: mips1 (mips1) `ldc1 $f18,(14+((4+2)))*4($29)' | asmpart.S:430: Error: opcode not supported on this processor: mips1 (mips1) `ldc1 $f20,-4*8($9)' | asmpart.S:431: Error: opcode not supported on this processor: mips1 (mips1) `ldc1 $f22,-3*8($9)' | asmpart.S:432: Error: opcode not supported on this processor: mips1 (mips1) `ldc1 $f24,-2*8($9)' | asmpart.S:433: Error: opcode not supported on this processor: mips1 (mips1) `ldc1 $f26,-1*8($9)' | asmpart.S:434: Error: opcode not supported on this processor: mips1 (mips1) `ldc1 $f28,-1*8($9)' | asmpart.S:435: Error: opcode not supported on this processor: mips1 (mips1) `ldc1 $f30,-1*8($9)' | asmpart.S:460: Warning: No .cprestore pseudo-op used in PIC code | asmpart.S:475: Error: opcode not supported on this processor: mips1 (mips1) `ll $2,0($4)' | asmpart.S:478: Error: opcode not supported on this processor: mips1 (mips1) `sc $8,0($4)' | asmpart.S:481: Error: opcode not supported on this processor: mips1 (mips1) `sync' | make[7]: *** [asmpart.lo] Error 1 | make[7]: Leaving directory `/build/buildd/cacao-0.99~rc3/src/vm/jit/mips' | make[6]: *** [all-recursive] Error 1 | make[6]: Leaving directory `/build/buildd/cacao-0.99~rc3/src/vm/jit/mips' | make[5]: *** [all-recursive] Error 1 | make[5]: Leaving directory `/build/buildd/cacao-0.99~rc3/src/vm/jit' | make[4]: *** [all-recursive] Error 1 | make[4]: Leaving directory `/build/buildd/cacao
Bug#479529: cacao_0.99~rc3-1(mips/experimental): FTBFS: Error: opcode not supported on this processor
On Mon, May 05, 2008 at 01:44:21PM +0200, Michael Koch wrote: On Mon, May 05, 2008 at 12:45:57PM +0200, Frank Lichtenheld wrote: | cc -I../../../../src -I../../../.. -I../../../../src -D__MIPS__ -D__LINUX__ -ansi -pedantic -Wall -Wno-long-long -D_POSIX_C_SOURCE=199506L -D_XOPEN_SOURCE=500 -D_XOPEN_SOURCE_EXTENDED -D_BSD_SOURCE -g -O2 -g -Wall -O2 -c asmpart.S -fPIC -DPIC -o .libs/asmpart.o | asmpart.S: Assembler messages: | asmpart.S:166: Error: opcode not supported on this processor: mips1 (mips1) `ldc1 $f12,4*8($8)' | asmpart.S:167: Error: opcode not supported on this processor: mips1 (mips1) `ldc1 $f14,5*8($8)' | asmpart.S:241: Warning: No .cprestore pseudo-op used in PIC code | asmpart.S:280: Warning: No .cprestore pseudo-op used in PIC code | asmpart.S:305: Error: opcode not supported on this processor: mips1 (mips1) `sdc1 $f12,(4+(0))*4($29)' | asmpart.S:305: Error: opcode not supported on this processor: mips1 (mips1) `sdc1 $f14,(6+(0))*4($29)' | asmpart.S:306: Error: opcode not supported on this processor: mips1 (mips1) `sdc1 $f8,(8+((4+2)))*4($29)' | asmpart.S:306: Error: opcode not supported on this processor: mips1 (mips1) `sdc1 $f10,(10+((4+2)))*4($29)' | asmpart.S:306: Error: opcode not supported on this processor: mips1 (mips1) `sdc1 $f16,(12+((4+2)))*4($29)' | asmpart.S:306: Error: opcode not supported on this processor: mips1 (mips1) `sdc1 $f18,(14+((4+2)))*4($29)' | asmpart.S:336: Warning: No .cprestore pseudo-op used in PIC code | asmpart.S:358: Error: opcode not supported on this processor: mips1 (mips1) `ldc1 $f12,(4+(0))*4($29)' | asmpart.S:358: Error: opcode not supported on this processor: mips1 (mips1) `ldc1 $f14,(6+(0))*4($29)' | asmpart.S:359: Error: opcode not supported on this processor: mips1 (mips1) `ldc1 $f8,(8+((4+2)))*4($29)' | asmpart.S:359: Error: opcode not supported on this processor: mips1 (mips1) `ldc1 $f10,(10+((4+2)))*4($29)' | asmpart.S:359: Error: opcode not supported on this processor: mips1 (mips1) `ldc1 $f16,(12+((4+2)))*4($29)' | asmpart.S:359: Error: opcode not supported on this processor: mips1 (mips1) `ldc1 $f18,(14+((4+2)))*4($29)' | asmpart.S:430: Error: opcode not supported on this processor: mips1 (mips1) `ldc1 $f20,-4*8($9)' | asmpart.S:431: Error: opcode not supported on this processor: mips1 (mips1) `ldc1 $f22,-3*8($9)' | asmpart.S:432: Error: opcode not supported on this processor: mips1 (mips1) `ldc1 $f24,-2*8($9)' | asmpart.S:433: Error: opcode not supported on this processor: mips1 (mips1) `ldc1 $f26,-1*8($9)' | asmpart.S:434: Error: opcode not supported on this processor: mips1 (mips1) `ldc1 $f28,-1*8($9)' | asmpart.S:435: Error: opcode not supported on this processor: mips1 (mips1) `ldc1 $f30,-1*8($9)' | asmpart.S:460: Warning: No .cprestore pseudo-op used in PIC code | asmpart.S:475: Error: opcode not supported on this processor: mips1 (mips1) `ll $2,0($4)' | asmpart.S:478: Error: opcode not supported on this processor: mips1 (mips1) `sc $8,0($4)' | asmpart.S:481: Error: opcode not supported on this processor: mips1 (mips1) `sync' | make[7]: *** [asmpart.lo] Error 1 | make[7]: Leaving directory `/build/buildd/cacao-0.99~rc3/src/vm/jit/mips' | make[6]: *** [all-recursive] Error 1 | make[6]: Leaving directory `/build/buildd/cacao-0.99~rc3/src/vm/jit/mips' | make[5]: *** [all-recursive] Error 1 | make[5]: Leaving directory `/build/buildd/cacao-0.99~rc3/src/vm/jit' | make[4]: *** [all-recursive] Error 1 | make[4]: Leaving directory `/build/buildd/cacao-0.99~rc3/src/vm' | make[3]: *** [all-recursive] Error 1 | make[3]: Leaving directory `/build/buildd/cacao-0.99~rc3/src' | make[2]: *** [all-recursive] Error 1 | make[2]: Leaving directory `/build/buildd/cacao-0.99~rc3' | make[1]: *** [all] Error 2 | make[1]: Leaving directory `/build/buildd/cacao-0.99~rc3' | make: *** [debian/stamp-makefile-build] Error 2 | dpkg-buildpackage: failure: debian/rules build gave error exit status 2 | ** | Build finished at 20080505-0258 | FAILED [dpkg-buildpackage died] Full build log(s): http://experimental.ftbfs.de/build.php?ver=0.99~rc3-1pkg=cacaoarch=mips Upstream told me that this code needs CFLAGS=-mips2. Is this allowed on mips? Are we expected to support mips1 machines? I honestly have no idea. Redirecting the question to the mips list. 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#479101: linux-image-2.6.25-1-amd64: more info on initramfs failure
On Mon, May 05, 2008 at 12:45:09PM +0200, Marc Lehmann wrote: Package: linux-image-2.6.25-1-amd64 Version: 2.6.25-1 Followup-For: Bug #479101 The issue is this: checking if image is initramfs...it isn't (bad gzip magic numbers); looks like an initrd however, the initrd image certainly *is* an initramfs: cerebro /boot# zcat initrd.img-2.6.25-1-amd64|cpio -t|head . bin bin/cat ... So this seems to be a bug somewhere in the kernel initramfs detection code. (google finds a lot of similar cases for 2.6.25) are you using lilo? can you reproduce with grub? thanks for the info! -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: setting package to libsoci-core-gcc soci libsoci-mysql-gcc libsoci-core-gcc-dbg libsoci-sqlite3-gcc libsoci-postgresql-gcc libsoci-core-gcc-dev ...
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.10.27 # # soci (2.2.0-2) unstable; urgency=low # # * soci - FTBFS: error: 'bad_cast' is not a member of 'std' (Closes: ##478504) # package libsoci-core-gcc soci libsoci-mysql-gcc libsoci-core-gcc-dbg libsoci-sqlite3-gcc libsoci-postgresql-gcc libsoci-core-gcc-dev Ignoring bugs not assigned to: libsoci-core-gcc soci libsoci-core-gcc-dbg libsoci-mysql-gcc libsoci-sqlite3-gcc libsoci-core-gcc-dev libsoci-postgresql-gcc tags 478504 + pending Bug#478504: soci - FTBFS: error: 'bad_cast' is not a member of 'std' 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]
Processed: tagging 478504
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.10.27 tags 478504 + pending Bug#478504: soci - FTBFS: error: 'bad_cast' is not a member of 'std' Tags were: pending 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#478504: setting package to libsoci-core-gcc soci libsoci-mysql-gcc libsoci-core-gcc-dbg libsoci-sqlite3-gcc libsoci-postgresql-gcc libsoci-core-gcc-dev ...
# Automatically generated email from bts, devscripts version 2.10.27 # # soci (2.2.0-2) unstable; urgency=low # # * soci - FTBFS: error: 'bad_cast' is not a member of 'std' (Closes: ##478504) # package libsoci-core-gcc soci libsoci-mysql-gcc libsoci-core-gcc-dbg libsoci-sqlite3-gcc libsoci-postgresql-gcc libsoci-core-gcc-dev tags 478504 + pending -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed (with 2 errors): Re: Bug#474413: Problem with autobuild of libtommath/0.39-2
Processing commands for [EMAIL PROTECTED]: clone 478524 -1 Bug#478524: debian/rules build target requires installing B-D-I Bug 478524 cloned as bug 479556. retitle -1 dpkg-buildpackage does not call build-indep or build-arch targets if present Bug#479556: debian/rules build target requires installing B-D-I Changed Bug title to `dpkg-buildpackage does not call build-indep or build-arch targets if present' from `debian/rules build target requires installing B-D-I'. severity -1 wishlist Bug#479556: dpkg-buildpackage does not call build-indep or build-arch targets if present Severity set to `wishlist' from `serious' merge 398625 -1 Bug#479556: dpkg-buildpackage does not call build-indep or build-arch targets if present Bug#398625: dpkg-dev: dpkg-buildpackage -B: should call build-arch target Mismatch - only Bugs in same state can be merged: Values for `package' don't match: #479556 has `sbuild'; #398625 has `dpkg-dev' Values for `blocks' don't match: #479556 has `474413'; #398625 has `' blocks 474413 by -1 Unknown command or malformed arguments to command. 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#474413: Problem with autobuild of libtommath/0.39-2
clone 478524 -1 retitle -1 dpkg-buildpackage does not call build-indep or build-arch targets if present severity -1 wishlist merge 398625 -1 blocks 474413 by -1 thanks On Tue, Apr 29, 2008 at 03:10:32PM +, Joe Nahmias wrote: Well, I made the change and now calling binary-arch target of debian/rules no longer runs latex. However, as you can see on line 156 of http://buildd.debian.org/fetch.cgi?pkg=libtommath;ver=0.39-2;arch=s390;stamp=1209376922, sbuild is actually calling the build target -- not the binary-arch target as previously asserted. This, as I mentioned in my first reply, requires the installation of B-D-I as per policy 7.6. I can verify that sbuild still calls debian/rules build and so when building binaries only B-D-I are not installed and so the build fails. sbuild is not at fault here--it just calls dpkg-buildpackage, and it's dpkg-buildpackage that does the building. As a result, the fix needs to be in dpkg-buildpackage. As discussed earlier today on IRC, making dpkg-buildpackage behave correctly is best implemented as a release goal shortly after the release of Lenny, targetted at Lenny+1. Regards, Roger -- .''`. Roger Leigh : :' : Debian GNU/Linux http://people.debian.org/~rleigh/ `. `' Printing on GNU/Linux? http://gutenprint.sourceforge.net/ `-GPG Public Key: 0x25BFB848 Please GPG sign your mail. signature.asc Description: Digital signature
Bug#479559: koffice_1:1.9.96.0~that.is.really.1.9.95.3-1(mips/experimental): FTBFS: No rule to make target `/usr/lib/libXrender.so'
Package: koffice Version: 1:1.9.96.0~that.is.really.1.9.95.3-1 Severity: serious Hi, your package failed to build from source. | Automatic build of koffice_1:1.9.96.0~that.is.really.1.9.95.3-1 on signy by sbuild/mips 98-farm | Build started at 20080505-1307 | ** | Checking available source versions... | Fetching source files... | Reading package lists... | Building dependency tree... | Need to get 73.8MB of source archives. | Get:1 http://sinclair.farm.ftbfs.de experimental/main koffice 1:1.9.96.0~that.is.really.1.9.95.3-1 (dsc) [1354B] | Get:2 http://sinclair.farm.ftbfs.de experimental/main koffice 1:1.9.96.0~that.is.really.1.9.95.3-1 (tar) [73.8MB] | Get:3 http://sinclair.farm.ftbfs.de experimental/main koffice 1:1.9.96.0~that.is.really.1.9.95.3-1 (diff) [46.5kB] | Fetched 73.8MB in 1m44s (706kB/s) | Download complete and in download only mode | ** Using build dependencies supplied by package: | Build-Depends: cdbs, cmake, debhelper (= 5), freeglut3-dev, freetds-dev, kdepimlibs5-dev (= 4:4.0.1), libeigen-dev, libexiv2-dev, libglew1.5-dev, libglpk-dev, libgraphicsmagick++1-dev, libgraphicsmagick1-dev, libgsl0-dev, libmysqlclient15-dev, libphonon-dev (= 4:4.0.1), libpoppler-qt4-dev, libpqxx-dev, libqca2-dev, libqimageblitz-dev, libwpd8-dev, libwpg-dev, libwv2-dev, quilt [...] | [ 0%] Building CXX object libs/store/CMakeFiles/kstore.dir/KoEncryptedStore.o | /usr/bin/g++ -DMAKE_KSTORE_LIB -g -O2 -g -Wall -O2 -Wnon-virtual-dtor -Wno-long-long -ansi -Wundef -Wcast-align -Wchar-subscripts -Wall -W -Wpointer-arith -Wformat-security -fno-exceptions -fno-check-new -fno-common -Woverloaded-virtual -fvisibility=hidden -fvisibility-inlines-hidden -DNDEBUG -fPIC -I/build/buildd/koffice-1.9.96.0~that.is.really.1.9.95.3/obj-mips-linux-gnu/libs/store -I/build/buildd/koffice-1.9.96.0~that.is.really.1.9.95.3/libs/store -I/build/buildd/koffice-1.9.96.0~that.is.really.1.9.95.3 -I/build/buildd/koffice-1.9.96.0~that.is.really.1.9.95.3/obj-mips-linux-gnu -I/usr/include/KDE -I/usr/include/qt4/QtDBus -I/usr/include/qt4/QtTest -I/usr/include/qt4/QtUiTools -I/usr/include/qt4/QtScript -I/usr/include/qt4/QtSvg -I/usr/include/qt4/QtXml -I/usr/include/qt4/QtSql -I/usr/include/qt4/QtOpenGL -I/usr/include/qt4/QtNetwork -I/usr/include/qt4/QtDesigner -I/usr/include/qt4/QtAssistant -I/usr/include/qt4/Qt3Support -I/usr/include/qt4/QtGui -I/usr/include/qt4/QtCore -I/usr/include/qt4/Qt -I/usr/share/qt4/mkspecs/default -I/usr/include/qt4 -I/usr/include/QtCrypto -D_BSD_SOURCE -DQT3_SUPPORT -DQT3_SUPPORT_WARNINGS -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -D_GNU_SOURCE -DQT_NO_STL -DQT_NO_CAST_TO_ASCII -D_REENTRANT -DKDE_DEPRECATED_WARNINGS -DQCA2 -o libs/store/CMakeFiles/kstore.dir/KoEncryptedStore.o -c /build/buildd/koffice-1.9.96.0~that.is.really.1.9.95.3/libs/store/KoEncryptedStore.cpp | make[3]: *** No rule to make target `/usr/lib/libXrender.so', needed by `lib/libkstore.so.5.0.0'. Stop. | make[3]: Leaving directory `/build/buildd/koffice-1.9.96.0~that.is.really.1.9.95.3/obj-mips-linux-gnu' | make[2]: *** [libs/store/CMakeFiles/kstore.dir/all] Error 2 | make[2]: Leaving directory `/build/buildd/koffice-1.9.96.0~that.is.really.1.9.95.3/obj-mips-linux-gnu' | make[1]: *** [all] Error 2 | make[1]: Leaving directory `/build/buildd/koffice-1.9.96.0~that.is.really.1.9.95.3/obj-mips-linux-gnu' | make: *** [debian/stamp-makefile-build] Error 2 | dpkg-buildpackage: failure: debian/rules build gave error exit status 2 | ** | Build finished at 20080505-1422 | FAILED [dpkg-buildpackage died] Full build log(s): http://experimental.ftbfs.de/build.php?ver=1:1.9.96.0~that.is.really.1.9.95.3-1pkg=kofficearch=mips 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]
Processed: libfishsound has a broken test for the speex version
Processing commands for [EMAIL PROTECTED]: reopen 475732 Bug#475732: libfishsound_0.7.0-2.2(sparc/unstable): error: 'FishSoundSpeexInfo' has no member named 'bits' 'reopen' may be inappropriate when a bug has been closed with a version; you may need to use 'found' to remove fixed versions. Bug reopened, originator not changed. retitle 475732 libfishsound has a broken test for the speex version Bug#475732: libfishsound_0.7.0-2.2(sparc/unstable): error: 'FishSoundSpeexInfo' has no member named 'bits' Changed Bug title to `libfishsound has a broken test for the speex version' from `libfishsound_0.7.0-2.2(sparc/unstable): error: 'FishSoundSpeexInfo' has no member named 'bits''. severity 475732 important Bug#475732: libfishsound has a broken test for the speex version Severity set to `important' from `serious' thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#475732: libfishsound has a broken test for the speex version
reopen 475732 retitle 475732 libfishsound has a broken test for the speex version severity 475732 important thanks Hi, The fix currently applied to close this bug is a fairly blunt workaround for a broken autoconf test, namely this one: AC_CHECK_HEADER([speex/speex_preprocess.h], HAVE_SPEEX_1_1=yes Which in conjunction with the test for HAVE_SPEEX_1_1 in src/libfishsound/speex.c, results in the code looking for headers in the speex1.0 locations, when using speex1.2 and later that have split the speexdsp functions into a separate library. Since libfishsound doesn't appear to use speex_preprocess.h or any of the other speexdsp functions, it would be better to just test for speex/speex.h instead, since it is the location of that header that this test is being used to conditionally select anyhow. When that is fixed, the patch that closed this bug (adding an extra search path to CFLAGS) should likewise be reverted. Please forward this to the upstream maintainers if they aren't aware of it already. If they are, we should get a fixed version into the archive before this freezes for Lenny ... Cheers, Ron -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#479501: [pkg-lighttpd] Bug#479501: file conflicts between packages
On Mon, May 05, 2008 at 10:44:54AM +, Alexander Turcic wrote: Pierre, I am certain that spawn-fcgi comes from the Lighttpd team. Also check out this source snippet from the cherokee: http://svn.cherokee-project.com/browser/cherokee/trunk/contrib/spawn-fcgi.c * File borrowed from lighttpd. I have only cleaned up the headers * inclusion mess. Its original license follows: *Alvaro Lopez Ortega [EMAIL PROTECTED] So given that it's really from Lighttpd, and that it's likely that future version will come from Lighttpd as well, not cherokee, shouldn't we give Lighttpd priority? Well so maybe I'll take gunnar's manual page then :) Anyways, I don't care much. I'll use a priority of 20, the cherokee maintainer can use whatever he thinks is best. -- ·O· Pierre Habouzit ··O[EMAIL PROTECTED] OOOhttp://www.madism.org pgpt2BBqRUNVe.pgp Description: PGP signature
Bug#479503: marked as done (file conflicts between packages)
Your message dated Mon, 05 May 2008 13:47:03 + with message-id [EMAIL PROTECTED] and subject line Bug#479503: fixed in dwarfutils 20080409-2 has caused the Debian Bug report #479503, regarding file conflicts between 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.) -- 479503: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=479503 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: libdw-dev, libdwarf-dev Severity: serious Justification: policy violation hi, both libdw-dev and libdwarf-dev ship `/usr/include/dwarf.h' but do neither conflict, nor add a diversion, thus fail to be installed in the same environment: Unpacking libdwarf-dev (from .../libdwarf-dev_20080409-1_amd64.deb) ... dpkg: error processing /var/cache/apt/archives/libdwarf-dev_20080409-1_amd64.deb (--unpack): trying to overwrite `/usr/include/dwarf.h', which is also in package libdw-dev dpkg-deb: subprocess paste killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/libdwarf-dev_20080409-1_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) bye, - michael ---End Message--- ---BeginMessage--- Source: dwarfutils Source-Version: 20080409-2 We believe that the bug you reported is fixed in the latest version of dwarfutils, which is due to be installed in the Debian FTP archive: dwarfdump_20080409-2_amd64.deb to pool/main/d/dwarfutils/dwarfdump_20080409-2_amd64.deb dwarfutils_20080409-2.diff.gz to pool/main/d/dwarfutils/dwarfutils_20080409-2.diff.gz dwarfutils_20080409-2.dsc to pool/main/d/dwarfutils/dwarfutils_20080409-2.dsc libdwarf-dev_20080409-2_amd64.deb to pool/main/d/dwarfutils/libdwarf-dev_20080409-2_amd64.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Troy Heber [EMAIL PROTECTED] (supplier of updated dwarfutils 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: Mon, 05 May 2008 07:31:47 -0600 Source: dwarfutils Binary: dwarfdump libdwarf-dev Architecture: source amd64 Version: 20080409-2 Distribution: unstable Urgency: low Maintainer: Troy Heber [EMAIL PROTECTED] Changed-By: Troy Heber [EMAIL PROTECTED] Description: dwarfdump - utilities to manage DWARF debug information in ELF objects libdwarf-dev - library to consume and produce DWARF debug information Closes: 479503 Changes: dwarfutils (20080409-2) unstable; urgency=low . * conflicts with libdw-dev, as both packages provide /usr/include/dwarf.h, (Closes: #479503) Checksums-Sha1: 97b8c39925e7e76022a49d9063b27c87df97686d 1020 dwarfutils_20080409-2.dsc 488ee8fc927c150ef18bb9dc75ae957765ad8b07 2481 dwarfutils_20080409-2.diff.gz b4e7a1283d13b5f9968b7ee16c3b739cee448fe7 93922 dwarfdump_20080409-2_amd64.deb 63e869a867b3c41513b4069bc3e1a97e2a196318 620460 libdwarf-dev_20080409-2_amd64.deb Checksums-Sha256: 621f67ef3c3adb464b1206d8d72d8723c9943c0d45fddb3dadcb28f4093d086e 1020 dwarfutils_20080409-2.dsc 3c680ff8a69f368e9156f0a9b3dc33fabb8764607bb332e7aaa3f7ab047f01f5 2481 dwarfutils_20080409-2.diff.gz bd1e2ba31dacbda63e245f3b919ccd6c0bc3884a7983934ce265a938cb45e2e2 93922 dwarfdump_20080409-2_amd64.deb f852d518d41161a2f91a7c8fccd4559a912815436f64b9f6a5cfeaab923bd8a0 620460 libdwarf-dev_20080409-2_amd64.deb Files: 1d45815a8df65f586c55f43c34e3b811 1020 libs optional dwarfutils_20080409-2.dsc 728a04105357b2f5ef725641e951eb84 2481 libs optional dwarfutils_20080409-2.diff.gz 4b82d043b5b33a9a2af9fa53a7a1f43f 93922 utils optional dwarfdump_20080409-2_amd64.deb 9fd983f28befdbd5df0bfa7beb7ee59a 620460 libdevel optional libdwarf-dev_20080409-2_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFIHw/qQOr9C+GfGI4RAgu0AKCRqW7GQTdcx1UHR0Cqpyn0pstgzACcDnih 6rTpiuYjjCHVgtpMgAz5Bus= =2a8Y -END PGP SIGNATURE- ---End Message---
Bug#434053: Same for me.
i just upgraded to twinkle 1.2-r1 and i get the same bug (since 1.1 early days too). Sound is working fine, but as soon as i press bye, twinkle freeze, nothing can be done but killing it. By the way, i'm on gentoo, and the strange think is that this happens on 32bit only, if i try with the same software configuration and versions (i mean kdelibs, qt and twinkle, of course), which changed over time, but on 64bit, twinkle runs great. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#475130: Some more info..
On Sat, May 03, 2008 at 07:39:17PM -0700, Mike Markley wrote: It seems more likely to me that the Received header is somehow being suppressed (it should be inserted by the host that's running spfmilter, right?) No. It is removing the most recent Received header which is _already_ in the received message (i.e. the header added by the MTA which directly preceded the problematic one on the message's path). I still don't understand how spfmilter could be causing this, so I plan to take it to postfix-users or similar. Based on the spfmilter package version, I'm guessing you're running etch, and therefore Postfix 2.3.8; can you confirm that? My guess would be that the API does not work like spfmilter assumes it does. I don't know where the bug lies, though. Yes, I am using etch, postfix 2.3.8-2 -- Marcin Owsiany [EMAIL PROTECTED] http://marcin.owsiany.pl/ GnuPG: 1024D/60F41216 FE67 DA2D 0ACA FC5E 3F75 D6F6 3A0D 8AA0 60F4 1216 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: severity of 475732 is grave
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.10.27 severity 475732 grave Bug#475732: libfishsound has a broken test for the speex version Severity set to `grave' from `important' End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: severity of 475732 is important
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.10.27 severity 475732 important Bug#475732: libfishsound has a broken test for the speex version 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#439718: marked as done (CVE-2007-1047: DCC remote data manipulation vulnerability)
Your message dated Mon, 5 May 2008 15:28:59 +0100 with message-id [EMAIL PROTECTED] and subject line dcc has been removed from Debian, closing #439718 has caused the Debian Bug report #439718, regarding CVE-2007-1047: DCC remote data manipulation vulnerability 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.) -- 439718: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=439718 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: dcc-common Version: 1.3.42-4 Severity: grave Tags: security Justification: user security hole A vulnerability has been reported in dcc. CVE-2007-1047: Unspecified vulnerability in Distributed Checksum Clearinghouse (DCC) before 1.3.51 allows remote attackers to delete or add hosts in /var/dcc/maps. I am not sure about the severity since no information is available about the attack vector. Feel free to adjust if you have more info. Please mention the CVE id in the changelog. ---End Message--- ---BeginMessage--- Version: 1.3.42-5+rm The dcc 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/464161 . 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---
Processed: [xbattbar-acpi] No battery detected with kernel 2.6.25
Processing commands for [EMAIL PROTECTED]: reassign 479096 libacpi Bug#479096: [xbattbar-acpi] No battery detected with kernel 2.6.25 Bug reassigned from package `xbattbar-acpi' to `libacpi'. 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#479096: [xbattbar-acpi] No battery detected with kernel 2.6.25
On Fri, 2 May 2008 19:02:58 +0100, Antoine Sirinelli [EMAIL PROTECTED] wrote: I join strace output of xbattbar-acpi running with 2.6.24-1 kernel and a 2.6.25-1 kernel. It seems it has trouble evaluating the informations in /sys/class/power_supply/ instead of /proc/acpi/. The directories /proc/acpi/battery/* and /proc/acpi/ac_adapter/* are deprecated and replaced by /sys/class/power_supply/*. xbattbar-acpi gets informations in /proc/acpi/* through the libacpi and not directly, therefore I reassign this bug to libacpi. -- Francesco Polsinelli [EMAIL PROTECTED] JID: [EMAIL PROTECTED] GnuPG Key ID: 0x261FD1CE Key fingerprint: 7CB5 8AC3 1A0D CB39 310A C283 38FA 73A7 261F D1CE signature.asc Description: PGP signature
Bug#472168: marked as done (quodlibet: libffi built from separate source, pleae b-d on libffi-dev)
Your message dated Mon, 5 May 2008 16:48:41 +0200 with message-id [EMAIL PROTECTED] and subject line Re: Bug#472161: notify-python: libffi built from separate source, pleae b-d on libffi-dev has caused the Debian Bug report #472168, regarding quodlibet: libffi built from separate source, pleae b-d on libffi-dev to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [EMAIL PROTECTED] immediately.) -- 472168: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=472168 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: quodlibet Severity: important Usertags: libffi After 10 years libffi does have a new upstream release again; this version is now packaged independent from GCC; once all packages are converted to use the binaries built from the separate libffi, GCC will stop building libffi packages. Please replace the current build dependencies lib*ffi4-dev with lib*ffi-dev and rebuild the package. ---End Message--- ---BeginMessage--- On Sat, 22 Mar 2008, Matthias Klose wrote: Please replace the current build dependencies lib*ffi4-dev with lib*ffi-dev and rebuild the package. The packages notify-python, exaile, gdesklets, gimmie, guile-gnome-platform, medit, papaya, pyclutter, ontv, quodlibet do _not_ build-depend on libffi4-dev in fact. Hence closing the associated bugs. Apparently they got their libffi4 dependency through pygobject and it has been fixedi by Josselin Mouette. He requested binnmus: http://lists.debian.org/debian-release/2008/05/msg00024.html For guile-gnome-platform it probably needs some g-wrap fix before however. Cheers, -- Raphaël Hertzog Le best-seller français mis à jour pour Debian Etch : http://www.ouaza.com/livre/admin-debian/ ---End Message---
Bug#472160: marked as done (medit: libffi built from separate source, pleae b-d on libffi-dev)
Your message dated Mon, 5 May 2008 16:48:41 +0200 with message-id [EMAIL PROTECTED] and subject line Re: Bug#472161: notify-python: libffi built from separate source, pleae b-d on libffi-dev has caused the Debian Bug report #472160, regarding medit: libffi built from separate source, pleae b-d on libffi-dev to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [EMAIL PROTECTED] immediately.) -- 472160: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=472160 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: medit Severity: important Usertags: libffi After 10 years libffi does have a new upstream release again; this version is now packaged independent from GCC; once all packages are converted to use the binaries built from the separate libffi, GCC will stop building libffi packages. Please replace the current build dependencies lib*ffi4-dev with lib*ffi-dev and rebuild the package. ---End Message--- ---BeginMessage--- On Sat, 22 Mar 2008, Matthias Klose wrote: Please replace the current build dependencies lib*ffi4-dev with lib*ffi-dev and rebuild the package. The packages notify-python, exaile, gdesklets, gimmie, guile-gnome-platform, medit, papaya, pyclutter, ontv, quodlibet do _not_ build-depend on libffi4-dev in fact. Hence closing the associated bugs. Apparently they got their libffi4 dependency through pygobject and it has been fixedi by Josselin Mouette. He requested binnmus: http://lists.debian.org/debian-release/2008/05/msg00024.html For guile-gnome-platform it probably needs some g-wrap fix before however. Cheers, -- Raphaël Hertzog Le best-seller français mis à jour pour Debian Etch : http://www.ouaza.com/livre/admin-debian/ ---End Message---
Bug#472145: marked as done (gdesklets: libffi built from separate source, pleae b-d on libffi-dev)
Your message dated Mon, 5 May 2008 16:48:41 +0200 with message-id [EMAIL PROTECTED] and subject line Re: Bug#472161: notify-python: libffi built from separate source, pleae b-d on libffi-dev has caused the Debian Bug report #472145, regarding gdesklets: libffi built from separate source, pleae b-d on libffi-dev to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [EMAIL PROTECTED] immediately.) -- 472145: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=472145 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: gdesklets Severity: important Usertags: libffi After 10 years libffi does have a new upstream release again; this version is now packaged independent from GCC; once all packages are converted to use the binaries built from the separate libffi, GCC will stop building libffi packages. Please replace the current build dependencies lib*ffi4-dev with lib*ffi-dev and rebuild the package. ---End Message--- ---BeginMessage--- On Sat, 22 Mar 2008, Matthias Klose wrote: Please replace the current build dependencies lib*ffi4-dev with lib*ffi-dev and rebuild the package. The packages notify-python, exaile, gdesklets, gimmie, guile-gnome-platform, medit, papaya, pyclutter, ontv, quodlibet do _not_ build-depend on libffi4-dev in fact. Hence closing the associated bugs. Apparently they got their libffi4 dependency through pygobject and it has been fixedi by Josselin Mouette. He requested binnmus: http://lists.debian.org/debian-release/2008/05/msg00024.html For guile-gnome-platform it probably needs some g-wrap fix before however. Cheers, -- Raphaël Hertzog Le best-seller français mis à jour pour Debian Etch : http://www.ouaza.com/livre/admin-debian/ ---End Message---
Bug#472156: marked as done (guile-gnome-platform: libffi built from separate source, pleae b-d on libffi-dev)
Your message dated Mon, 5 May 2008 16:48:41 +0200 with message-id [EMAIL PROTECTED] and subject line Re: Bug#472161: notify-python: libffi built from separate source, pleae b-d on libffi-dev has caused the Debian Bug report #472156, regarding guile-gnome-platform: libffi built from separate source, pleae b-d on libffi-dev to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [EMAIL PROTECTED] immediately.) -- 472156: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=472156 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: guile-gnome-platform Severity: important Usertags: libffi After 10 years libffi does have a new upstream release again; this version is now packaged independent from GCC; once all packages are converted to use the binaries built from the separate libffi, GCC will stop building libffi packages. Please replace the current build dependencies lib*ffi4-dev with lib*ffi-dev and rebuild the package. ---End Message--- ---BeginMessage--- On Sat, 22 Mar 2008, Matthias Klose wrote: Please replace the current build dependencies lib*ffi4-dev with lib*ffi-dev and rebuild the package. The packages notify-python, exaile, gdesklets, gimmie, guile-gnome-platform, medit, papaya, pyclutter, ontv, quodlibet do _not_ build-depend on libffi4-dev in fact. Hence closing the associated bugs. Apparently they got their libffi4 dependency through pygobject and it has been fixedi by Josselin Mouette. He requested binnmus: http://lists.debian.org/debian-release/2008/05/msg00024.html For guile-gnome-platform it probably needs some g-wrap fix before however. Cheers, -- Raphaël Hertzog Le best-seller français mis à jour pour Debian Etch : http://www.ouaza.com/livre/admin-debian/ ---End Message---
Bug#472165: marked as done (ontv: libffi built from separate source, pleae b-d on libffi-dev)
Your message dated Mon, 5 May 2008 16:48:41 +0200 with message-id [EMAIL PROTECTED] and subject line Re: Bug#472161: notify-python: libffi built from separate source, pleae b-d on libffi-dev has caused the Debian Bug report #472165, regarding ontv: libffi built from separate source, pleae b-d on libffi-dev to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [EMAIL PROTECTED] immediately.) -- 472165: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=472165 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: ontv Severity: important Usertags: libffi After 10 years libffi does have a new upstream release again; this version is now packaged independent from GCC; once all packages are converted to use the binaries built from the separate libffi, GCC will stop building libffi packages. Please replace the current build dependencies lib*ffi4-dev with lib*ffi-dev and rebuild the package. ---End Message--- ---BeginMessage--- On Sat, 22 Mar 2008, Matthias Klose wrote: Please replace the current build dependencies lib*ffi4-dev with lib*ffi-dev and rebuild the package. The packages notify-python, exaile, gdesklets, gimmie, guile-gnome-platform, medit, papaya, pyclutter, ontv, quodlibet do _not_ build-depend on libffi4-dev in fact. Hence closing the associated bugs. Apparently they got their libffi4 dependency through pygobject and it has been fixedi by Josselin Mouette. He requested binnmus: http://lists.debian.org/debian-release/2008/05/msg00024.html For guile-gnome-platform it probably needs some g-wrap fix before however. Cheers, -- Raphaël Hertzog Le best-seller français mis à jour pour Debian Etch : http://www.ouaza.com/livre/admin-debian/ ---End Message---
Bug#472161: marked as done (notify-python: libffi built from separate source, pleae b-d on libffi-dev)
Your message dated Mon, 5 May 2008 16:48:41 +0200 with message-id [EMAIL PROTECTED] and subject line Re: Bug#472161: notify-python: libffi built from separate source, pleae b-d on libffi-dev has caused the Debian Bug report #472161, regarding notify-python: libffi built from separate source, pleae b-d on libffi-dev to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [EMAIL PROTECTED] immediately.) -- 472161: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=472161 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: notify-python Severity: important Usertags: libffi After 10 years libffi does have a new upstream release again; this version is now packaged independent from GCC; once all packages are converted to use the binaries built from the separate libffi, GCC will stop building libffi packages. Please replace the current build dependencies lib*ffi4-dev with lib*ffi-dev and rebuild the package. ---End Message--- ---BeginMessage--- On Sat, 22 Mar 2008, Matthias Klose wrote: Please replace the current build dependencies lib*ffi4-dev with lib*ffi-dev and rebuild the package. The packages notify-python, exaile, gdesklets, gimmie, guile-gnome-platform, medit, papaya, pyclutter, ontv, quodlibet do _not_ build-depend on libffi4-dev in fact. Hence closing the associated bugs. Apparently they got their libffi4 dependency through pygobject and it has been fixedi by Josselin Mouette. He requested binnmus: http://lists.debian.org/debian-release/2008/05/msg00024.html For guile-gnome-platform it probably needs some g-wrap fix before however. Cheers, -- Raphaël Hertzog Le best-seller français mis à jour pour Debian Etch : http://www.ouaza.com/livre/admin-debian/ ---End Message---
Bug#472163: marked as done (papaya: libffi built from separate source, pleae b-d on libffi-dev)
Your message dated Mon, 5 May 2008 16:48:41 +0200 with message-id [EMAIL PROTECTED] and subject line Re: Bug#472161: notify-python: libffi built from separate source, pleae b-d on libffi-dev has caused the Debian Bug report #472163, regarding papaya: libffi built from separate source, pleae b-d on libffi-dev to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [EMAIL PROTECTED] immediately.) -- 472163: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=472163 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: papaya Severity: important Usertags: libffi After 10 years libffi does have a new upstream release again; this version is now packaged independent from GCC; once all packages are converted to use the binaries built from the separate libffi, GCC will stop building libffi packages. Please replace the current build dependencies lib*ffi4-dev with lib*ffi-dev and rebuild the package. ---End Message--- ---BeginMessage--- On Sat, 22 Mar 2008, Matthias Klose wrote: Please replace the current build dependencies lib*ffi4-dev with lib*ffi-dev and rebuild the package. The packages notify-python, exaile, gdesklets, gimmie, guile-gnome-platform, medit, papaya, pyclutter, ontv, quodlibet do _not_ build-depend on libffi4-dev in fact. Hence closing the associated bugs. Apparently they got their libffi4 dependency through pygobject and it has been fixedi by Josselin Mouette. He requested binnmus: http://lists.debian.org/debian-release/2008/05/msg00024.html For guile-gnome-platform it probably needs some g-wrap fix before however. Cheers, -- Raphaël Hertzog Le best-seller français mis à jour pour Debian Etch : http://www.ouaza.com/livre/admin-debian/ ---End Message---
Bug#476504: nvidia-kernel-source patch and modpost patch resolve bug for 2.6.25-1-amd64
Package: nvidia-kernel-source Version: 169.12-1 Followup-For: Bug #476504 After reviewing the full bug report, and patching the source and Makefile.modpost everything is working great. A big win for HP laptop users with MCP51/nVidia who are experiencing the hwclock issues reported in #426171 that are now resolved by 2.6.25 and have working GUI now too. thanks, Ian. -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.25-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages nvidia-kernel-source depends on: ii debhelper 7.0.8 helper programs for debian/rules ii dpatch2.0.29 patch maintenance system for Debia ii make 3.81-4 The GNU version of the make util ii sed 4.1.5-8The GNU sed stream editor Versions of packages nvidia-kernel-source recommends: ii devscripts2.10.27scripts to make the life of a Debi ii kernel-package11.001-0.1 A utility for building Linux kerne ii nvidia-glx169.12-1 NVIDIA binary Xorg driver -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#472146: marked as done (gimmie: libffi built from separate source, pleae b-d on libffi-dev)
Your message dated Mon, 5 May 2008 16:48:41 +0200 with message-id [EMAIL PROTECTED] and subject line Re: Bug#472161: notify-python: libffi built from separate source, pleae b-d on libffi-dev has caused the Debian Bug report #472146, regarding gimmie: libffi built from separate source, pleae b-d on libffi-dev to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [EMAIL PROTECTED] immediately.) -- 472146: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=472146 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: gimmie Severity: important Usertags: libffi After 10 years libffi does have a new upstream release again; this version is now packaged independent from GCC; once all packages are converted to use the binaries built from the separate libffi, GCC will stop building libffi packages. Please replace the current build dependencies lib*ffi4-dev with lib*ffi-dev and rebuild the package. ---End Message--- ---BeginMessage--- On Sat, 22 Mar 2008, Matthias Klose wrote: Please replace the current build dependencies lib*ffi4-dev with lib*ffi-dev and rebuild the package. The packages notify-python, exaile, gdesklets, gimmie, guile-gnome-platform, medit, papaya, pyclutter, ontv, quodlibet do _not_ build-depend on libffi4-dev in fact. Hence closing the associated bugs. Apparently they got their libffi4 dependency through pygobject and it has been fixedi by Josselin Mouette. He requested binnmus: http://lists.debian.org/debian-release/2008/05/msg00024.html For guile-gnome-platform it probably needs some g-wrap fix before however. Cheers, -- Raphaël Hertzog Le best-seller français mis à jour pour Debian Etch : http://www.ouaza.com/livre/admin-debian/ ---End Message---
Bug#472143: marked as done (exaile: libffi built from separate source, pleae b-d on libffi-dev)
Your message dated Mon, 5 May 2008 16:48:41 +0200 with message-id [EMAIL PROTECTED] and subject line Re: Bug#472161: notify-python: libffi built from separate source, pleae b-d on libffi-dev has caused the Debian Bug report #472143, regarding exaile: libffi built from separate source, pleae b-d on libffi-dev to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [EMAIL PROTECTED] immediately.) -- 472143: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=472143 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: exaile Severity: important Usertags: libffi After 10 years libffi does have a new upstream release again; this version is now packaged independent from GCC; once all packages are converted to use the binaries built from the separate libffi, GCC will stop building libffi packages. Please replace the current build dependencies lib*ffi4-dev with lib*ffi-dev and rebuild the package. ---End Message--- ---BeginMessage--- On Sat, 22 Mar 2008, Matthias Klose wrote: Please replace the current build dependencies lib*ffi4-dev with lib*ffi-dev and rebuild the package. The packages notify-python, exaile, gdesklets, gimmie, guile-gnome-platform, medit, papaya, pyclutter, ontv, quodlibet do _not_ build-depend on libffi4-dev in fact. Hence closing the associated bugs. Apparently they got their libffi4 dependency through pygobject and it has been fixedi by Josselin Mouette. He requested binnmus: http://lists.debian.org/debian-release/2008/05/msg00024.html For guile-gnome-platform it probably needs some g-wrap fix before however. Cheers, -- Raphaël Hertzog Le best-seller français mis à jour pour Debian Etch : http://www.ouaza.com/livre/admin-debian/ ---End Message---
Bug#472164: marked as done (pyclutter: libffi built from separate source, pleae b-d on libffi-dev)
Your message dated Mon, 5 May 2008 16:48:41 +0200 with message-id [EMAIL PROTECTED] and subject line Re: Bug#472161: notify-python: libffi built from separate source, pleae b-d on libffi-dev has caused the Debian Bug report #472164, regarding pyclutter: libffi built from separate source, pleae b-d on libffi-dev to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [EMAIL PROTECTED] immediately.) -- 472164: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=472164 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: pyclutter Severity: important Usertags: libffi After 10 years libffi does have a new upstream release again; this version is now packaged independent from GCC; once all packages are converted to use the binaries built from the separate libffi, GCC will stop building libffi packages. Please replace the current build dependencies lib*ffi4-dev with lib*ffi-dev and rebuild the package. ---End Message--- ---BeginMessage--- On Sat, 22 Mar 2008, Matthias Klose wrote: Please replace the current build dependencies lib*ffi4-dev with lib*ffi-dev and rebuild the package. The packages notify-python, exaile, gdesklets, gimmie, guile-gnome-platform, medit, papaya, pyclutter, ontv, quodlibet do _not_ build-depend on libffi4-dev in fact. Hence closing the associated bugs. Apparently they got their libffi4 dependency through pygobject and it has been fixedi by Josselin Mouette. He requested binnmus: http://lists.debian.org/debian-release/2008/05/msg00024.html For guile-gnome-platform it probably needs some g-wrap fix before however. Cheers, -- Raphaël Hertzog Le best-seller français mis à jour pour Debian Etch : http://www.ouaza.com/livre/admin-debian/ ---End Message---
Bug#356055: loadlin: loadlin.exe cannot be built from source
On Thu, Aug 30, 2007 at 11:18:46PM +0200, Pierre Habouzit wrote: Hmm, now that there is win32-loader, is this still needed for blind people or not ? Still needed. Specially more because of win32-loader, since win32-loader currently relies on loadlin.exe when running on win9x. (think of win32-loader as a frontend to grub and loadlin rather than as a replacement for them) Samuel, is there any progress with your yasm patch? -- Robert Millan GPLv2 I know my rights; I want my phone call! DRM What use is a phone call… if you are unable to speak? (as seen on /.) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#356055: loadlin: loadlin.exe cannot be built from source
Robert Millan, le Mon 05 May 2008 17:04:08 +0200, a écrit : On Thu, Aug 30, 2007 at 11:18:46PM +0200, Pierre Habouzit wrote: Hmm, now that there is win32-loader, is this still needed for blind people or not ? Still needed. Specially more because of win32-loader, since win32-loader currently relies on loadlin.exe when running on win9x. (think of win32-loader as a frontend to grub and loadlin rather than as a replacement for them) Samuel, is there any progress with your yasm patch? I didn't have the time to rework them, but plan to take it. Samuel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: closing 477808
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.9.26 close 477808 2.42a-7.1+etch1 Bug#477808: blender: CVE-2008-1102 arbitrary code execution via crafted .blend file 'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing. Bug marked as fixed in version 2.42a-7.1+etch1, send any further explanations to Nico Golde [EMAIL PROTECTED] 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#479096: [xbattbar-acpi] No battery detected with kernel 2.6.25
Hi, thanks for reassigning this bug. You are right, libacpi currently reads information from proc and has some hack in it in Debian to read some information from the sysfs. However reimplementing parts and having a clean sysfs + procfs implementation as fallback is still on my todo list, sadly I am too busy with other stuff atm. Patches welcome. Kind regards Nico -- Nico Golde - http://www.ngolde.de - [EMAIL PROTECTED] - GPG: 0x73647CFF For security reasons, all text in this mail is double-rot13 encrypted. pgp1qZ8YeyPcr.pgp Description: PGP signature
Bug#461804: marked as done (libapache2-mod-cband: Fails to start, undefined symbol: truncf)
Your message dated Mon, 5 May 2008 16:38:57 +0100 with message-id [EMAIL PROTECTED] and subject line mod-cband has been removed from Debian, closing #461804 has caused the Debian Bug report #461804, regarding libapache2-mod-cband: Fails to start, undefined symbol: truncf 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.) -- 461804: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=461804 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: libapache2-mod-cband Version: 0.9.7.5-2 Severity: grave Justification: renders package unusable Hello Jonas, I just updated apache and now get this error, my guess is it needs a recompile perhaps. This is what I get on the command line: gonzo:/home/csmall# /etc/init.d/apache2 start Starting web server: apache2apache2: Syntax error on line 185 of /etc/apache2/apache2.conf: Syntax error on line 1 of /etc/apache2/mods-enabled/cband.load: Cannot load /usr/lib/apache2/modules/mod_cband.so into server: /usr/lib/apache2/modules/mod_cband.so: undefined symbol: truncf failed! Line 185 is the module loading line. The work-around is to a2dismod cband and then it works ok, obviously without cband. -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.22-3-k7 (SMP w/1 CPU core) Locale: LANG=en_AU, LC_CTYPE=en_AU (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/bash Versions of packages libapache2-mod-cband depends on: ii apache2.2-common 2.2.8-1Next generation, scalable, extenda ii debconf [debconf-2.0] 1.5.18 Debian configuration management sy ii libc6 2.7-6 GNU C Library: Shared libraries libapache2-mod-cband recommends no packages. -- debconf-show failed ---End Message--- ---BeginMessage--- Version: 0.9.7.5-2+rm The mod-cband 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/463789 . 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---
Processed: another CVE id
Processing commands for [EMAIL PROTECTED]: retitle 479039 CVE-2008-2085, CVE-2008-1959 multiple stack-based buffer overflows Bug#479039: sip-tester: CVE-2008-1959 multiple stack-based buffer overflows Changed Bug title to `CVE-2008-2085, CVE-2008-1959 multiple stack-based buffer overflows' from `sip-tester: CVE-2008-1959 multiple stack-based buffer overflows'. 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#479039: CVE-2008-1959: Potential security problems
On Fri, 2 May 2008, Nico Golde wrote: BTW: the same issue affects get_remote_ip_media() and get_remote_ipv6_media(), both unfixed in latest upstream release (3.1) and the version in Debian This sounds like a different issue than CVE-2008-1959, which was already addressed upstream apparently. So, use CVE-2008-2085 for these new issues. - Steve -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#479039: another CVE id
retitle 479039 CVE-2008-2085, CVE-2008-1959 multiple stack-based buffer overflows thanks Hi, mitre assigned an additional CVE id to the 2 issues I poited out. Please also mention this one in the changelog. Kind regards Nico -- Nico Golde - http://www.ngolde.de - [EMAIL PROTECTED] - GPG: 0x73647CFF For security reasons, all text in this mail is double-rot13 encrypted. pgp3r1I4FGsjN.pgp Description: PGP signature
Bug#479529: cacao_0.99~rc3-1(mips/experimental): FTBFS: Error: opcode not supported on this processor
Frank Lichtenheld wrote: On Mon, May 05, 2008 at 01:44:21PM +0200, Michael Koch wrote: On Mon, May 05, 2008 at 12:45:57PM +0200, Frank Lichtenheld wrote: | cc -I../../../../src -I../../../.. -I../../../../src -D__MIPS__ -D__LINUX__ -ansi -pedantic -Wall -Wno-long-long -D_POSIX_C_SOURCE=199506L -D_XOPEN_SOURCE=500 -D_XOPEN_SOURCE_EXTENDED -D_BSD_SOURCE -g -O2 -g -Wall -O2 -c asmpart.S -fPIC -DPIC -o .libs/asmpart.o | asmpart.S: Assembler messages: | asmpart.S:166: Error: opcode not supported on this processor: mips1 (mips1) `ldc1 $f12,4*8($8)' | asmpart.S:167: Error: opcode not supported on this processor: mips1 (mips1) `ldc1 $f14,5*8($8)' | asmpart.S:241: Warning: No .cprestore pseudo-op used in PIC code | asmpart.S:280: Warning: No .cprestore pseudo-op used in PIC code | asmpart.S:305: Error: opcode not supported on this processor: mips1 (mips1) `sdc1 $f12,(4+(0))*4($29)' | asmpart.S:305: Error: opcode not supported on this processor: mips1 (mips1) `sdc1 $f14,(6+(0))*4($29)' | asmpart.S:306: Error: opcode not supported on this processor: mips1 (mips1) `sdc1 $f8,(8+((4+2)))*4($29)' | asmpart.S:306: Error: opcode not supported on this processor: mips1 (mips1) `sdc1 $f10,(10+((4+2)))*4($29)' | asmpart.S:306: Error: opcode not supported on this processor: mips1 (mips1) `sdc1 $f16,(12+((4+2)))*4($29)' | asmpart.S:306: Error: opcode not supported on this processor: mips1 (mips1) `sdc1 $f18,(14+((4+2)))*4($29)' | asmpart.S:336: Warning: No .cprestore pseudo-op used in PIC code | asmpart.S:358: Error: opcode not supported on this processor: mips1 (mips1) `ldc1 $f12,(4+(0))*4($29)' | asmpart.S:358: Error: opcode not supported on this processor: mips1 (mips1) `ldc1 $f14,(6+(0))*4($29)' | asmpart.S:359: Error: opcode not supported on this processor: mips1 (mips1) `ldc1 $f8,(8+((4+2)))*4($29)' | asmpart.S:359: Error: opcode not supported on this processor: mips1 (mips1) `ldc1 $f10,(10+((4+2)))*4($29)' | asmpart.S:359: Error: opcode not supported on this processor: mips1 (mips1) `ldc1 $f16,(12+((4+2)))*4($29)' | asmpart.S:359: Error: opcode not supported on this processor: mips1 (mips1) `ldc1 $f18,(14+((4+2)))*4($29)' | asmpart.S:430: Error: opcode not supported on this processor: mips1 (mips1) `ldc1 $f20,-4*8($9)' | asmpart.S:431: Error: opcode not supported on this processor: mips1 (mips1) `ldc1 $f22,-3*8($9)' | asmpart.S:432: Error: opcode not supported on this processor: mips1 (mips1) `ldc1 $f24,-2*8($9)' | asmpart.S:433: Error: opcode not supported on this processor: mips1 (mips1) `ldc1 $f26,-1*8($9)' | asmpart.S:434: Error: opcode not supported on this processor: mips1 (mips1) `ldc1 $f28,-1*8($9)' | asmpart.S:435: Error: opcode not supported on this processor: mips1 (mips1) `ldc1 $f30,-1*8($9)' | asmpart.S:460: Warning: No .cprestore pseudo-op used in PIC code | asmpart.S:475: Error: opcode not supported on this processor: mips1 (mips1) `ll $2,0($4)' | asmpart.S:478: Error: opcode not supported on this processor: mips1 (mips1) `sc $8,0($4)' | asmpart.S:481: Error: opcode not supported on this processor: mips1 (mips1) `sync' | make[7]: *** [asmpart.lo] Error 1 | make[7]: Leaving directory `/build/buildd/cacao-0.99~rc3/src/vm/jit/mips' | make[6]: *** [all-recursive] Error 1 | make[6]: Leaving directory `/build/buildd/cacao-0.99~rc3/src/vm/jit/mips' | make[5]: *** [all-recursive] Error 1 | make[5]: Leaving directory `/build/buildd/cacao-0.99~rc3/src/vm/jit' | make[4]: *** [all-recursive] Error 1 | make[4]: Leaving directory `/build/buildd/cacao-0.99~rc3/src/vm' | make[3]: *** [all-recursive] Error 1 | make[3]: Leaving directory `/build/buildd/cacao-0.99~rc3/src' | make[2]: *** [all-recursive] Error 1 | make[2]: Leaving directory `/build/buildd/cacao-0.99~rc3' | make[1]: *** [all] Error 2 | make[1]: Leaving directory `/build/buildd/cacao-0.99~rc3' | make: *** [debian/stamp-makefile-build] Error 2 | dpkg-buildpackage: failure: debian/rules build gave error exit status 2 | ** | Build finished at 20080505-0258 | FAILED [dpkg-buildpackage died] Full build log(s): http://experimental.ftbfs.de/build.php?ver=0.99~rc3-1pkg=cacaoarch=mips Upstream told me that this code needs CFLAGS=-mips2. Is this allowed on mips? Are we expected to support mips1 machines? I honestly have no idea. Redirecting the question to the mips list. Yes, we should support MIPS I. This isn't too hard, since the Linux kernel emulates atomic instructions when running on MIPS I (but it doesn't emulate 64-bit FPU accesses). Those 64-bit FPU instructions are not supported by the normal O32 ABI which we use in Debian, they should be replaced by assembler macros which expand to the right
Processed: FTBFS on mips
Processing commands for [EMAIL PROTECTED]: severity 479572 serious Bug#479572: libusb: missing build-dep docbook Severity set to `serious' from `normal' 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#479501: [pkg-lighttpd] Bug#479501: file conflicts between packages
Pierre Habouzit dijo [Mon, May 05, 2008 at 03:44:15PM +0200]: So given that it's really from Lighttpd, and that it's likely that future version will come from Lighttpd as well, not cherokee, shouldn't we give Lighttpd priority? Well so maybe I'll take gunnar's manual page then :) Glad to be of use Anyways, I don't care much. I'll use a priority of 20, the cherokee maintainer can use whatever he thinks is best. FWIW, I think we can set them even at the same level. I'll put mine a bit lower than yours - say, 15. I'll prepare and upload soon - I want to check another bug with the same upload. -- Gunnar Wolf - [EMAIL PROTECTED] - (+52-55)5623-0154 / 1451-2244 PGP key 1024D/8BB527AF 2001-10-23 Fingerprint: 0C79 D2D1 2C4E 9CE4 5973 F800 D80E F35A 8BB5 27AF -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#476504: nvidia-kernel-source patch and modpost patch resolve bug for 2.6.25-1-amd64
Could you give us a step by step to install the this patch in debian... Tank's in advance On 5/5/08, Ian MacDonald [EMAIL PROTECTED] wrote: Package: nvidia-kernel-source Version: 169.12-1 Followup-For: Bug #476504 After reviewing the full bug report, and patching the source and Makefile.modpost everything is working great. A big win for HP laptop users with MCP51/nVidia who are experiencing the hwclock issues reported in #426171 that are now resolved by 2.6.25 and have working GUI now too. thanks, Ian. -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.25-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages nvidia-kernel-source depends on: ii debhelper 7.0.8 helper programs for debian/rules ii dpatch2.0.29 patch maintenance system for Debia ii make 3.81-4 The GNU version of the make util ii sed 4.1.5-8The GNU sed stream editor Versions of packages nvidia-kernel-source recommends: ii devscripts2.10.27scripts to make the life of a Debi ii kernel-package11.001-0.1 A utility for building Linux kerne ii nvidia-glx169.12-1 NVIDIA binary Xorg driver -- no debconf information -- Perhaps the depth of love can be calibrated by the number of different selves that are actively involved in a given relationship. Carl Sagan (Contact) Jaime Ochoa Malagón Integrated Technology Tel: (55) 52 54 26 10 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#479501: [pkg-lighttpd] Bug#479501: file conflicts between packages
Pierre Habouzit dijo [Mon, May 05, 2008 at 03:44:15PM +0200]: So given that it's really from Lighttpd, and that it's likely that future version will come from Lighttpd as well, not cherokee, shouldn't we give Lighttpd priority? Well so maybe I'll take gunnar's manual page then :) Anyways, I don't care much. I'll use a priority of 20, the cherokee maintainer can use whatever he thinks is best. I'm using a slave alternative for the manpage, and I will be shipping both the binary and the manpage as spawn-fcgi.cherokee - Even if the manpage is the same today, nothing guarantees it will stay so. How should we close the bug? In rigor, the bug should be open until we _both_ upload the changed packages... So, should our changelogs refer to this bug, or should we close it manually later? Greetings, -- Gunnar Wolf - [EMAIL PROTECTED] - (+52-55)5623-0154 / 1451-2244 PGP key 1024D/8BB527AF 2001-10-23 Fingerprint: 0C79 D2D1 2C4E 9CE4 5973 F800 D80E F35A 8BB5 27AF -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#479346: [cherokee] cherokee-admin server is not accesible
Isaac Gelado dijo [Sun, May 04, 2008 at 01:42:28PM +0200]: After launching cherokee-admin, if I open a web browser and type the URL http://localhost:9090 I get a blank web page. Using lynx as web browser reports: - HTTP request sent; waiing for response - Alert! Unexpected network read error; connection aborted - Alert! Unable to access document Running strace cherokee-admin shows errors due to invalid file descriptors. Ugh... This sounds really strange. Even stranger, in fact, after your follow-up to the report (I'm copying it over again, as I'm sending a copy of this bug report to the Cherokee mailing list) If I stop Mldonkey (running at ports 4000/telnet and 4040/web) and start cherokee-admin, it works. Seems like some kind of incompatibility between them. This is plain _weird_. The two programs are completely unrelated. AFAICT, mldonkey opens (in a default configuration) TCP ports 4000, 4001, 9324 and 4080, and UDP port 9328. cherokee-admin uses none of those. And the code is in no way shared. Have you tried running cherokee-admin bound to a different port, i.e. «/usr/sbin/cherokee-admin -p 3»? It should not even be related to permissions, as even if you run cherokee-admin as a regular user, it should warn you via a nice informative page in case it cannot access it. Greetings, -- Gunnar Wolf - [EMAIL PROTECTED] - (+52-55)5623-0154 / 1451-2244 PGP key 1024D/8BB527AF 2001-10-23 Fingerprint: 0C79 D2D1 2C4E 9CE4 5973 F800 D80E F35A 8BB5 27AF -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#479572: FTBFS on mips
Thiemo Seufer a écrit : severity 479572 serious thanks This causes a FTBFS on mips (and presumably on all architectures when a rebuild in a clean current unstable chroot is attempted). If the problem also appears in a clean chroot, it may be interesting to find what has changed, as other packages may be impacted. The build-depends of libusb haven't changed since etch. Cheers, Aurelien -- .''`. Aurelien Jarno | GPG: 1024D/F1BCDB73 : :' : Debian developer | Electrical Engineer `. `' [EMAIL PROTECTED] | [EMAIL PROTECTED] `-people.debian.org/~aurel32 | www.aurel32.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: rm lilo
Processing commands for [EMAIL PROTECTED]: clone 479101 -1 Bug#479101: linux-image-2.6.25-1-amd64: Kernel panic: Unable to mount root Bug 479101 cloned as bug 479607. reassign -1 lilo Bug#479607: linux-image-2.6.25-1-amd64: Kernel panic: Unable to mount root Bug reassigned from package `linux-image-2.6.25-1-amd64' to `lilo'. retitle -1 lilo fails to boot 2.6.25 kernel image due to wrongly passing initramfs Bug#479607: linux-image-2.6.25-1-amd64: Kernel panic: Unable to mount root Changed Bug title to `lilo fails to boot 2.6.25 kernel image due to wrongly passing initramfs' from `linux-image-2.6.25-1-amd64: Kernel panic: Unable to mount root'. 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#479612: after upgrade to spandsp 0.0.4pre18 asterisk-app-fax crashes asterisk
Package: asterisk-app-fax Version: 0.0.20070624-1 Severity: critical Justification: causes serious data loss Apparently the dependency of asterisk-spandsp-plugins and spandsp-dev is pretty tight. It looks like there was a binary incompatible change introduced by the upgrade from 0.0.4pre16 to 0.0.4pre18 I verified that asterisk crashes every time a fax is received after the upgrade Recompiling asterisk-spandsp-plugins_0.0.20070624-1 and reinstalling makes the crash go away. It looks like theres a compiled version in unstable that will go through to testing in 10 days and fix the problem The net of this bug report is that either these packages need to be tied together, or the so version of spandsp needs increasing for every change (because in the pre stage the ABI is obviously not stable) -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.24-1-686 (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 asterisk-app-fax depends on: ii asterisk 1:1.4.18.1~dfsg-1 Open Source Private Branch Exchang ii libc6 2.7-10GNU C Library: Shared libraries ii libspandsp30.0.4pre18-1 Telephony signal processing librar Versions of packages asterisk-app-fax recommends: ii gs-common 0.3.13-0.1 Common files for different Ghostsc ii libconfig-tiny-perl 2.12-1 Read/Write .ini style files with a ii libfile-sync-perl 0.09-4 Perl interface to sync() and fsync ii liblocale-gettext-perl1.05-3 Using libc functions for internati ii libmime-lite-perl 3.021-3Perl5 module for convenient genera ii libpaper-utils1.1.23 library for handling paper charact ii libtiff-tools 3.8.2-8TIFF manipulation and conversion t ii psutils 1.17-24A collection of PostScript documen -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#479613: FTBFS on many/all arches
Package: siproxd Version: 1:0.7.0-1 Severity: serious Hi, this package FTBFS on many/all arches, see: http://buildd.debian.org/fetch.cgi?pkg=siproxdver=1%3A0.7.0-1%2Bb1arch=i386stamp=1210011445file=log cc -DHAVE_CONFIG_H -I. -I. -I.. -I/usr/include -Wall -D_GNU_SOURCE -DBUILDSTR=\`cat .buildno`\ -g -O2 -g -Wall -O2 -pthread -D_POSIX_THREAD_SAFE_FUNCTIONS -c siproxd.c siproxd.c: In function 'main': siproxd.c:346: warning: pointer targets in passing argument 2 of 'sip_fixup_asterisk' differ in signedness cc -DHAVE_CONFIG_H -I. -I. -I.. -I/usr/include -Wall -D_GNU_SOURCE -DBUILDSTR=\`cat .buildno`\ -g -O2 -g -Wall -O2 -pthread -D_POSIX_THREAD_SAFE_FUNCTIONS -c proxy.c cc -DHAVE_CONFIG_H -I. -I. -I.. -I/usr/include -Wall -D_GNU_SOURCE -DBUILDSTR=\`cat .buildno`\ -g -O2 -g -Wall -O2 -pthread -D_POSIX_THREAD_SAFE_FUNCTIONS -c register.c cc -DHAVE_CONFIG_H -I. -I. -I.. -I/usr/include -Wall -D_GNU_SOURCE -DBUILDSTR=\`cat .buildno`\ -g -O2 -g -Wall -O2 -pthread -D_POSIX_THREAD_SAFE_FUNCTIONS -c sock.c cc -DHAVE_CONFIG_H -I. -I. -I.. -I/usr/include -Wall -D_GNU_SOURCE -DBUILDSTR=\`cat .buildno`\ -g -O2 -g -Wall -O2 -pthread -D_POSIX_THREAD_SAFE_FUNCTIONS -c utils.c cc -DHAVE_CONFIG_H -I. -I. -I.. -I/usr/include -Wall -D_GNU_SOURCE -DBUILDSTR=\`cat .buildno`\ -g -O2 -g -Wall -O2 -pthread -D_POSIX_THREAD_SAFE_FUNCTIONS -c sip_utils.c sip_utils.c: In function 'sip_calculate_branch_id': sip_utils.c:776: error: 'MD5_CTX' undeclared (first use in this function) sip_utils.c:776: error: (Each undeclared identifier is reported only once sip_utils.c:776: error: for each function it appears in.) sip_utils.c:776: error: expected ';' before 'Md5Ctx' sip_utils.c:779: warning: implicit declaration of function 'MD5Init' sip_utils.c:779: error: 'Md5Ctx' undeclared (first use in this function) sip_utils.c:780: warning: implicit declaration of function 'MD5Update' sip_utils.c:782: warning: implicit declaration of function 'MD5Final' Cheers, Andi -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
