Bug#661216: Uninstallable: xulrunner-9.0 went away
Source: tuxguitar Version: 1.2-12 Severity: grave Justification: renders package unusable Hi, iceweasel is now at version 10, so this no longer works: | Package: tuxguitar | Architecture: all | Section: sound | Depends: [...] | xulrunner-9.0 | xulrunner-8.0 | xulrunner-7.0 | xulrunner-6.0 | xulrunner-5.0 | xulrunner-1.9.1, tuxguitar is now uninstallable. Mraw, KiBi. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#661099: fpc depends on packages that can't be installed
On Sat, 25 Feb 2012, Carlos Laviola wrote: On Fri, Feb 24, 2012 at 21:10, David Griffith wrote: On Fri, 24 Feb 2012, Abou Al Montacir wrote: Can you please clarify more the situation? You are using Squeeze or a mix of Squeeze and other repositories? What are the dependencies that are missing? Aptitude will give you the full dependency tree, can you please provide this? I'm not sure I understand what you mean by "dependencies that are missing". I thought I explained that. These: 1) fp-units-gnome1 [Not Installed] What happens when you try to install one of these packages directly? eg., 'apt-get install fp-units-gnome1'? 2) fp-units-gtk [Not Installed] 3) fpc [Not Installed] 4) libcairo2-dev [Not Installed] 5) libgtk2.0-dev [Not Installed] 6) libpango1.0-dev [Not Installed] If I do that, I get a complaint that one of the other listed package "is not going to be installed". I tried specifying all of them on one command line and I got a complaint that libpixman-1.dev was not going to be installed. Adding that made the complaints go circular. -- David Griffith d...@661.org
Bug#633297: funguloids: FTBFS everywhere: error: reference to 'map' is ambiguous
The FTBFS bug and the other RC bugs have been open for a long time. There is no point in fixing the FTBFS bug without fixing the crashes that prevent the game from working at all. The package is not in testing or stable anyway so it can basically be considered a new package. To fix the crashes you need to modify the data and for that you need to run mpak.py or maybe some of the C code from the game can be used. mpak.py needs to be re-implemented or re-licensed because the current implementation as distributed by Arch does not have any license attached to it, so it is not distributable by Debian and Arch folks are violating copyright law. Ideally though, upstream needs to be revived and the mpak stuff ripped out and replaced with either filesystem accesses or some standard pack format like zip/tar. I've been trying to do that for a while but upstream hasn't responded. Since upstream is not responding I am not sure how to deal with the situation. Either mpak.py has to be run at orig.tar.gz creation time or a second tarball needs to be added with the pre-fixed data. Alternatively the project could be completely forked, but that does not seem to be a good way to do things to me. -- bye, pabs http://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#646449: marked as done (libosip2: FTBFS: osip_message_parse.c:850:5: error: format not a string literal and no format arguments [-Werror=format-security])
Your message dated Sat, 25 Feb 2012 04:02:15 + with message-id and subject line Bug#646449: fixed in libosip2 3.3.0-2 has caused the Debian Bug report #646449, regarding libosip2: FTBFS: osip_message_parse.c:850:5: error: format not a string literal and no format arguments [-Werror=format-security] 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 ow...@bugs.debian.org immediately.) -- 646449: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=646449 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libosip2 Version: 3.3.0-1 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20111022 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: > gcc -DHAVE_CONFIG_H -I. -I. -I../.. -I../../include -Wall -Wcast-align > -Wchar-subscripts -Wformat -Winline -Wmissing-declarations > -Wmissing-prototypes -Wnested-externs -Wpointer-arith -g -fstack-protector > --param=ssp-buffer-size=4 -Wformat -Wformat-security -Werror=format-security > -Wall -DUSE_GPERF -pedantic -g -DENABLE_TRACE -g -fstack-protector > --param=ssp-buffer-size=4 -Wformat -Wformat-security -Werror=format-security > -Wall -c osip_message_parse.c -fPIC -DPIC -o .libs/osip_message_parse.o > osip_message_parse.c: In function 'msg_osip_body_parse': > osip_message_parse.c:800:15: warning: format '%i' expects argument of type > 'int', but argument 3 has type 'size_t' [-Wformat] > osip_message_parse.c:850:5: error: format not a string literal and no format > arguments [-Werror=format-security] > cc1: some warnings being treated as errors > > make[4]: *** [osip_message_parse.lo] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2011/10/22/libosip2_3.3.0-1_lsid64.buildlog A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems. --- End Message --- --- Begin Message --- Source: libosip2 Source-Version: 3.3.0-2 We believe that the bug you reported is fixed in the latest version of libosip2, which is due to be installed in the Debian FTP archive: libosip2-4_3.3.0-2_amd64.deb to main/libo/libosip2/libosip2-4_3.3.0-2_amd64.deb libosip2-dev_3.3.0-2_amd64.deb to main/libo/libosip2/libosip2-dev_3.3.0-2_amd64.deb libosip2_3.3.0-2.diff.gz to main/libo/libosip2/libosip2_3.3.0-2.diff.gz libosip2_3.3.0-2.dsc to main/libo/libosip2/libosip2_3.3.0-2.dsc A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 646...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Mark Purcell (supplier of updated libosip2 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 ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sat, 25 Feb 2012 14:23:00 +1100 Source: libosip2 Binary: libosip2-dev libosip2-4 Architecture: source amd64 Version: 3.3.0-2 Distribution: unstable Urgency: low Maintainer: Debian VoIP Team Changed-By: Mark Purcell Description: libosip2-4 - Session Initiation Protocol (SIP) library libosip2-dev - development files for the SIP library Closes: 646449 Changes: libosip2 (3.3.0-2) unstable; urgency=low . * Fix "FTBFS: osip_message_parse.c:850:5: error: format not a string literal and no format arguments [-Werror=format-security]" added patches/format-security.diff (Closes: #646449) Checksums-Sha1: 77013f66fcdd9a908b3963bed91074a8fa29804d 1382 libosip2_3.3.0-2.dsc d125a8d40359f3f874f7bc3cf0985ac0cb965d3f 6347 libosip2_3.3.0-2.diff.gz a707d730ea6ab85b252839f906db3463cd18469d 154350 libosip2-dev_3.3.0-2_amd64.deb 50055dd3ef81671233874f9e18f59ca2e19347a0 107042 libosip2-4_3.3.0-2_amd64.deb Checksums-Sha256: 34123fc4c8ee27d4ae23848bc07311fc6d1e5a13a9766eed71fad0a470df5e71 1382 libosip2_3.3.0-2.dsc ce9566b2c658e96cf7ef678dd3c54f634b564bc00cb1aba001ce904817913dd7 6347 libosip2_3.3.0-2.diff.gz bd31a6287c0b3ac3c044a65713d745e68c93926e7d1a90414f4795ae8c42675a 154350 libosip2-dev_3.3.0-2_amd64.deb 9a982fc3302e4cadfe5de8266a698c88f9b80ac8b071faa8baee91ecb02360d
Bug#661099: fpc depends on packages that can't be installed
On Fri, Feb 24, 2012 at 21:10, David Griffith wrote: > On Fri, 24 Feb 2012, Abou Al Montacir wrote: > >> Can you please clarify more the situation? You are using Squeeze or a mix >> of >> Squeeze and other repositories? What are the dependencies that are >> missing? >> Aptitude will give you the full dependency tree, can you please provide >> this? > I'm not sure I understand what you mean by "dependencies that are missing". > I thought I explained that. These: > > 1) fp-units-gnome1 [Not Installed] What happens when you try to install one of these packages directly? eg., 'apt-get install fp-units-gnome1'? > 2) fp-units-gtk [Not Installed] > 3) fpc [Not Installed] > 4) libcairo2-dev [Not Installed] > 5) libgtk2.0-dev [Not Installed] > 6) libpango1.0-dev [Not Installed] -- Carlos Laviola Debian GNU/Linux -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#646449: libosip2 upload to unstable
Thanks Peter. That upload is OK. Thanks Since i'm not yet a DD could one of you guys please sponsor it? -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#641873: closed by Michael Gilbert (Bug#641873: fixed in xpdf 3.03-9)
Thanks, I'll test it as soon as it reaches the FTP site. Sorry I haven't been following all the activity this last month... -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#646449: libosip2 upload to unstable
On Sat, 25 Feb 2012 12:44:17 peter green wrote: > peter green wrote: > > Would you object to a NMU based on the version currently in unstable > > that just fixes the FTBFS? > > I have now prepared a NMU based on the version currently in sid that > only fixes the FTBFS. The debdiff is attatched. > > libosip2 maintainers are you ok with this NMU? Thanks Peter. That upload is OK. Mark signature.asc Description: This is a digitally signed message part.
Processed (with 2 errors): libnss3-1d: Still happens
Processing commands for cont...@bugs.debian.org:
> Package: libnss3-1d
Limiting to bugs with field 'package' containing at least one of 'libnss3-1d'
Limit currently set to 'package':'libnss3-1d'
> Version: 3.13.3-1
Unknown command or malformed arguments to command.
> Followup-For: Bug #661201
Unknown command or malformed arguments to command.
> reopen 661201
Bug #661201 {Done: jida...@jidanni.org} [libnss3-1d] relocation error
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
661201: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=661201
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#661201: libnss3-1d: Still happens
Package: libnss3-1d Version: 3.13.3-1 Followup-For: Bug #661201 reopen 661201 thanks > apt-get upgrade fixed it. Which upgrade? It still happens to me. Reopening the bug. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=th_TH.utf8, LC_CTYPE=th_TH.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages libnss3-1d depends on: ii libc6 2.13-26 ii libnspr4-0d4.9-1 ii libsqlite3-0 3.7.10-1 ii multiarch-support 2.13-26 ii zlib1g 1:1.2.6.dfsg-2 libnss3-1d recommends no packages. libnss3-1d suggests no packages. -- no debconf information signature.asc Description: Digital signature
Bug#653437: marked as done (xpdf: type1 fonts not rendered)
Your message dated Sat, 25 Feb 2012 01:47:52 + with message-id and subject line Bug#641873: fixed in xpdf 3.03-9 has caused the Debian Bug report #641873, regarding xpdf: type1 fonts not rendered 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 ow...@bugs.debian.org immediately.) -- 641873: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=641873 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: xpdf Version: 3.03-7 Severity: important Tags: upstream Opening this file with xpdf only shows the images no text. Opening with evince works fine. http://www.google.ch/#sclient=psy- ab&hl=de&site=&source=hp&q=netidmgr.pdf+&pbx=1&oq=netidmgr.pdf+&aq=f&aqi=&aql=&gs_sm=e&gs_upl=527l527l0l1047l1l1l0l0l0l0l216l216l2-1l1l0&bav=on.2,or.r_gc.r_pw.,cf.osb&fp=84508821f3f5a6a&biw=1409&bih=637 Removing the folder /usr/share/fonts/type1 and the lines 'fontFile xx /usr/share/fonts/type1/gsfonts/xx.pfb' from the /etc/xpdf/xpdfrc makes the document render ok. Any hints what to try next? Is X misconfigured? I use the closed source nvidia X server. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'stable-updates'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.1.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages xpdf depends on: ii lesstif2 1:0.95.2-1 ii libc6 2.13-23 ii libgcc1 1:4.6.2-9 ii libpoppler13 0.16.7-2+b1 ii libstdc++64.6.2-9 ii libx11-6 2:1.4.4-4 ii libxt61:1.1.1-2 Versions of packages xpdf recommends: ii gsfonts-x110.22 ii poppler-data 0.4.5-2 ii poppler-utils 0.16.7-2+b1 xpdf suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: xpdf Source-Version: 3.03-9 We believe that the bug you reported is fixed in the latest version of xpdf, which is due to be installed in the Debian FTP archive: xpdf_3.03-9.debian.tar.gz to main/x/xpdf/xpdf_3.03-9.debian.tar.gz xpdf_3.03-9.dsc to main/x/xpdf/xpdf_3.03-9.dsc xpdf_3.03-9_amd64.deb to main/x/xpdf/xpdf_3.03-9_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 641...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Michael Gilbert (supplier of updated xpdf 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 ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 24 Feb 2012 17:33:29 -0500 Source: xpdf Binary: xpdf Architecture: source amd64 Version: 3.03-9 Distribution: unstable Urgency: low Maintainer: Michael Gilbert Changed-By: Michael Gilbert Description: xpdf - Portable Document Format (PDF) reader Closes: 631450 641873 652606 654308 659272 Changes: xpdf (3.03-9) unstable; urgency=low . * Let poppler find and select non-embedded font file locations. Thanks to Vincent Lefevre for finding a solution to this problem (closes: #641873). * Remove now ineffective font file configuration options from xpdfrc. * Revert UTF8 title conversion change (closes: #659272). * Revert lp as default print command. Use lpr (the privious default) and recommend cups-bsd package (closes: #652606). * Fix segfault issue in additional zoom options patch and enable it again. Thanks to Jörg-Volker Peetz (closes: #654308). * Support title refresh when starting from a non-compressed file (lp: #932062). * Use "Xpdf" instead of "xpdf" in documentation on Xresources (closes: #631450). * Check exit codes of system calls (fix -Wunused-result compiler warnings). * Fix a pointer casting to a different size (fix -Wint-to-pointer-cast compiler warning). * Add -Wno-format-extra-args to build flags. * Bump standards to 3.9.3. Checksums-Sha1: ecbf475ee87a14cde95b527d73f9e54e74ec2c99 2639 xpdf_3.03-9.dsc 314dbf3c3c906bc014564cb6b5817e13d2374523 38280 xpdf_3.03-9.debian.tar.gz 7dcc4eda5ca7424660d46f69861383dfb43b76b6 197848 xpdf_3.03-9_amd64.deb Checksums-Sha256: 5fec049173731349d519761d61a920275aa36f48a16ee5dbddc7e08f667e0b1b 2639 xpdf_3.03-9.dsc e9778ab42b4ced73f92ac28830844908dee0eca9a18379cb37867309883cac0f 38280 xpdf_3.03-9.debian.tar.gz 55018d0d06017e0696e1891b49
Bug#647576: marked as done (can't read pdfs any more)
Your message dated Sat, 25 Feb 2012 01:47:52 + with message-id and subject line Bug#641873: fixed in xpdf 3.03-9 has caused the Debian Bug report #641873, regarding can't read pdfs any more 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 ow...@bugs.debian.org immediately.) -- 641873: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=641873 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: xpdf Version: 3.03-7 Severity: grave Can you read the pdf in http://portal.gsdi.org/files/?artifact_id=940 --- End Message --- --- Begin Message --- Source: xpdf Source-Version: 3.03-9 We believe that the bug you reported is fixed in the latest version of xpdf, which is due to be installed in the Debian FTP archive: xpdf_3.03-9.debian.tar.gz to main/x/xpdf/xpdf_3.03-9.debian.tar.gz xpdf_3.03-9.dsc to main/x/xpdf/xpdf_3.03-9.dsc xpdf_3.03-9_amd64.deb to main/x/xpdf/xpdf_3.03-9_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 641...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Michael Gilbert (supplier of updated xpdf 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 ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 24 Feb 2012 17:33:29 -0500 Source: xpdf Binary: xpdf Architecture: source amd64 Version: 3.03-9 Distribution: unstable Urgency: low Maintainer: Michael Gilbert Changed-By: Michael Gilbert Description: xpdf - Portable Document Format (PDF) reader Closes: 631450 641873 652606 654308 659272 Changes: xpdf (3.03-9) unstable; urgency=low . * Let poppler find and select non-embedded font file locations. Thanks to Vincent Lefevre for finding a solution to this problem (closes: #641873). * Remove now ineffective font file configuration options from xpdfrc. * Revert UTF8 title conversion change (closes: #659272). * Revert lp as default print command. Use lpr (the privious default) and recommend cups-bsd package (closes: #652606). * Fix segfault issue in additional zoom options patch and enable it again. Thanks to Jörg-Volker Peetz (closes: #654308). * Support title refresh when starting from a non-compressed file (lp: #932062). * Use "Xpdf" instead of "xpdf" in documentation on Xresources (closes: #631450). * Check exit codes of system calls (fix -Wunused-result compiler warnings). * Fix a pointer casting to a different size (fix -Wint-to-pointer-cast compiler warning). * Add -Wno-format-extra-args to build flags. * Bump standards to 3.9.3. Checksums-Sha1: ecbf475ee87a14cde95b527d73f9e54e74ec2c99 2639 xpdf_3.03-9.dsc 314dbf3c3c906bc014564cb6b5817e13d2374523 38280 xpdf_3.03-9.debian.tar.gz 7dcc4eda5ca7424660d46f69861383dfb43b76b6 197848 xpdf_3.03-9_amd64.deb Checksums-Sha256: 5fec049173731349d519761d61a920275aa36f48a16ee5dbddc7e08f667e0b1b 2639 xpdf_3.03-9.dsc e9778ab42b4ced73f92ac28830844908dee0eca9a18379cb37867309883cac0f 38280 xpdf_3.03-9.debian.tar.gz 55018d0d06017e0696e1891b49bac25f40e0f3cfd333257e266a193b81e311b1 197848 xpdf_3.03-9_amd64.deb Files: 77d7ffb8625a0dad85507e70fe31f5c0 2639 text optional xpdf_3.03-9.dsc d0e3dff4e22589f7c76ce7bc987fc835 38280 text optional xpdf_3.03-9.debian.tar.gz 7337f0c797f0c35ca356f1be8062a473 197848 text optional xpdf_3.03-9_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iQQcBAEBCAAGBQJPSDuTAAoJELjWss0C1vRzPyogAJzF9p+lXWmDuMt1fXKNE8Z/ cw2I/0XdJyqcjFESTwmQv33PLN78ZEj3CEsiah4WYzeT5/KeYsncWC6tOyg77/T4 GQLRg0mk2lN8osKjPHmrd7pxvubug/ojIVWrzPZP7Vbwp+KW18+nuoK1HFY9pzgC s4MrZYTtVJyBHFz7XNqv32tev6yJZ04JGxh1oo0KHsZn6565vEW8uXBaMZLWtpnL Bx69oFJLyvklfFm0OU2f3w4sM0lAM9J/IymDNuChXeO5jLNf6i+os0ZIn0GRI6Df zxfgX4Qh5GmwP5orELyddOSNQoJRLoE8orb/ScOTg1Ugij4b8lY1rzEqG0fjF3tg StrKIQouuiepxhyvLsP7jsQsbQDjzz9rugvPQ3Hon2JH3sK9YgQJhRTlm2Wp5jE/ XihqHIIUsi39KO9JCXXl4RHQJ0ZEgSwIMI8lGRgVCkVAm3j/arxJImmTBnFDKp6v HP+9WJgKrg4sEgov3dMaruArgEsIrkr48vkeBcANjsU8lDSbbgUSQRap2zjC1evV CpDu4z6XnvEVPzTEhQGR3BkJy2m7PM6Ah2Y0nCBgjaM87jqMVaqIuGwskbt7cyXv VA9o9+Bowjmfttpz8tquvjsjdjIkAY/XJ0mh+H5RNZHtOiQ2hCV8WB5DqqKgZOcX CmgH5lviD7a/feVO7UBP6ZcMRqcWbz2fWqjdeOGSfS8kCoDjaHdmh8pZ0Ig6x7fD szl0jCZ/DR2MzPN6ijsrxXiGzIyVQhAMg0aqLqwVNIFMUndKKAZ08kWKaugIRseY 238q81rb+1ZC60O9Fx0e6+Oo1wsOHsLTRkh+6zskflXtPojg4MCdUIFIycjAiBRk
Bug#646223: marked as done (cannot read timetables anymore)
Your message dated Sat, 25 Feb 2012 01:47:52 + with message-id and subject line Bug#641873: fixed in xpdf 3.03-9 has caused the Debian Bug report #641873, regarding cannot read timetables anymore 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 ow...@bugs.debian.org immediately.) -- 641873: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=641873 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: xpdf Version: 3.03-5 Severity: grave I can't read the times in http://www.ubus.com.tw/bus/image_bus/85TT.pdf . --- End Message --- --- Begin Message --- Source: xpdf Source-Version: 3.03-9 We believe that the bug you reported is fixed in the latest version of xpdf, which is due to be installed in the Debian FTP archive: xpdf_3.03-9.debian.tar.gz to main/x/xpdf/xpdf_3.03-9.debian.tar.gz xpdf_3.03-9.dsc to main/x/xpdf/xpdf_3.03-9.dsc xpdf_3.03-9_amd64.deb to main/x/xpdf/xpdf_3.03-9_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 641...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Michael Gilbert (supplier of updated xpdf 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 ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 24 Feb 2012 17:33:29 -0500 Source: xpdf Binary: xpdf Architecture: source amd64 Version: 3.03-9 Distribution: unstable Urgency: low Maintainer: Michael Gilbert Changed-By: Michael Gilbert Description: xpdf - Portable Document Format (PDF) reader Closes: 631450 641873 652606 654308 659272 Changes: xpdf (3.03-9) unstable; urgency=low . * Let poppler find and select non-embedded font file locations. Thanks to Vincent Lefevre for finding a solution to this problem (closes: #641873). * Remove now ineffective font file configuration options from xpdfrc. * Revert UTF8 title conversion change (closes: #659272). * Revert lp as default print command. Use lpr (the privious default) and recommend cups-bsd package (closes: #652606). * Fix segfault issue in additional zoom options patch and enable it again. Thanks to Jörg-Volker Peetz (closes: #654308). * Support title refresh when starting from a non-compressed file (lp: #932062). * Use "Xpdf" instead of "xpdf" in documentation on Xresources (closes: #631450). * Check exit codes of system calls (fix -Wunused-result compiler warnings). * Fix a pointer casting to a different size (fix -Wint-to-pointer-cast compiler warning). * Add -Wno-format-extra-args to build flags. * Bump standards to 3.9.3. Checksums-Sha1: ecbf475ee87a14cde95b527d73f9e54e74ec2c99 2639 xpdf_3.03-9.dsc 314dbf3c3c906bc014564cb6b5817e13d2374523 38280 xpdf_3.03-9.debian.tar.gz 7dcc4eda5ca7424660d46f69861383dfb43b76b6 197848 xpdf_3.03-9_amd64.deb Checksums-Sha256: 5fec049173731349d519761d61a920275aa36f48a16ee5dbddc7e08f667e0b1b 2639 xpdf_3.03-9.dsc e9778ab42b4ced73f92ac28830844908dee0eca9a18379cb37867309883cac0f 38280 xpdf_3.03-9.debian.tar.gz 55018d0d06017e0696e1891b49bac25f40e0f3cfd333257e266a193b81e311b1 197848 xpdf_3.03-9_amd64.deb Files: 77d7ffb8625a0dad85507e70fe31f5c0 2639 text optional xpdf_3.03-9.dsc d0e3dff4e22589f7c76ce7bc987fc835 38280 text optional xpdf_3.03-9.debian.tar.gz 7337f0c797f0c35ca356f1be8062a473 197848 text optional xpdf_3.03-9_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iQQcBAEBCAAGBQJPSDuTAAoJELjWss0C1vRzPyogAJzF9p+lXWmDuMt1fXKNE8Z/ cw2I/0XdJyqcjFESTwmQv33PLN78ZEj3CEsiah4WYzeT5/KeYsncWC6tOyg77/T4 GQLRg0mk2lN8osKjPHmrd7pxvubug/ojIVWrzPZP7Vbwp+KW18+nuoK1HFY9pzgC s4MrZYTtVJyBHFz7XNqv32tev6yJZ04JGxh1oo0KHsZn6565vEW8uXBaMZLWtpnL Bx69oFJLyvklfFm0OU2f3w4sM0lAM9J/IymDNuChXeO5jLNf6i+os0ZIn0GRI6Df zxfgX4Qh5GmwP5orELyddOSNQoJRLoE8orb/ScOTg1Ugij4b8lY1rzEqG0fjF3tg StrKIQouuiepxhyvLsP7jsQsbQDjzz9rugvPQ3Hon2JH3sK9YgQJhRTlm2Wp5jE/ XihqHIIUsi39KO9JCXXl4RHQJ0ZEgSwIMI8lGRgVCkVAm3j/arxJImmTBnFDKp6v HP+9WJgKrg4sEgov3dMaruArgEsIrkr48vkeBcANjsU8lDSbbgUSQRap2zjC1evV CpDu4z6XnvEVPzTEhQGR3BkJy2m7PM6Ah2Y0nCBgjaM87jqMVaqIuGwskbt7cyXv VA9o9+Bowjmfttpz8tquvjsjdjIkAY/XJ0mh+H5RNZHtOiQ2hCV8WB5DqqKgZOcX CmgH5lviD7a/feVO7UBP6ZcMRqcWbz2fWqjdeOGSfS8kCoDjaHdmh8pZ0Ig6x7fD szl0jCZ/DR2MzPN6ijsrxXiGzIyVQhAMg0aqLqwVNIFMUndKKAZ08kWKaugIRseY 238q81rb+1ZC60O9Fx0e6+Oo1wsOHsLTRkh+6zskflXtPojg4MCdUIF
Bug#641873: marked as done (xpdf doesn't display text in many PDF files)
Your message dated Sat, 25 Feb 2012 01:47:52 +
with message-id
and subject line Bug#641873: fixed in xpdf 3.03-9
has caused the Debian Bug report #641873,
regarding xpdf doesn't display text in many PDF files
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 ow...@bugs.debian.org
immediately.)
--
641873: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=641873
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: xpdf
Version: 3.03-3
I thought this was Bug#640967, but I guess it's something else.
Consider the PDF file at
http://www.state-machine.com/arm/Building_bare-metal_ARM_with_GNU.pdf
When I open it, I get page after blank page containong only
images and background shading. Ignoring text in logos, the
first "normal" text I see are the headings "[1-1]" through "[1-6]"
on page 6. Blue link underlines are also visible, but not the text
they are underlining.
I think line 31 of the 3.03-3 /etc/xpdf/xpdfrc has a typo: it says
"fontFile Helvetic", which I thonk should have a trailing a.
But fixing that doesn't change it.
It does display on startup a number (72) of copies of
Error: Unknown config file command '{0:t}' ({1:t}:{2:d})
followed by a single error message
Error: Expected the default config, but wasn't able to find it, or it isn't a
Dictionary
These are emitted while reading the
/usr/share/xpdf/xpdfrc-$LANGUAGE files. They appear to correspond
to the displayCIDFontTT lines; when I comment that out of
/usr/share/xpdf/xpdfrc-chinese-simplified, no error message is
emitted until -chinese-traditional is read.
A huge number of errors appear while reading the -japanese
file; I haven't tracked those down.
The final error line happens shortly after opening the actual .pdf
file, well after the xpdfrc file is read. (There is no ~/.xpdfrc.)
The sequence of system calls leading up to that does not exactly fill
me with confidence about the code quality:
stat64($file) - Okay, I see, make sure it's not a device node or something
open($file) = 4
fstat64(4) - double check type, find size = 820466
fstat64(4) - why again?
_llseek(4, 819200, SEEK_SET) - Seek to END-1266; no idea why
read(4, buf, 1266) = 1266
fstat64(4) - why again?
_llseek(4, 819200, SEEK_SET) - Huh? We just did that.
read(4, buf, 4096) = 1266. Interesting that the previous read knew the
expected size, but this doesn't.
_llseek(4, 0, SEEK_SET) - Ah, about to start for real.
read(4, buf, 4096) = 4096
_llseek(4, 4096, SEEK_SET) - Dude, we're already there!
_llseek(4, 4096, SEEK_SET)
_llseek(4, 4096, SEEK_SET)
_llseek(4, 4096, SEEK_SET)
_llseek(4, 4096, SEEK_SET)
_llseek(4, 4096, SEEK_SET) - This is getting monotonous
read(4, buf, 4096) = 4096
_llseek(4, 8192, SEEK_SET)
_llseek(4, 8192, SEEK_SET)
_llseek(4, 8192, SEEK_SET) - Again, what's the point?
_llseek(4, 0, SEEK_SET) - Back to the beginning? Make up your mind!
read(4, buf, 4096) = 4096
_llseek(4, 4096, SEEK_SET)
_llseek(4, 4096, SEEK_SET)
read(4, buf, 4096) = 4096
_llseek(4, 0, SEEK_SET) - A *third* time??
read(4, buf, 4096) = 4096
_llseek(4, 4096, SEEK_SET)
read(4, buf, 4096) = 4096
_llseek(4, 0, SEEK_SET) - FOUR???
read(4, buf, 4096)
write(2, "Expected the default config, but wasn't able to find it, or it isn't
a Dictionary", 81)
write(2, "\n", 1)
_llseek(4, 4096, SEEK_SET)
read(4, buf, 4096)
_llseek(4, 0, SEEK_SET) - Five. This is just getting stupid...
read(4, buf, 4096)
_llseek(4, 4096, SEEK_SET)
read(4, buf, 4096)
_llseek(4, 0, SEEK_SET) - Six. I think I'm going insane.
read(4, buf, 4096)
_llseek(4, 4096, SEEK_SET)
read(4, buf, 4096)
_llseek(4, 0, SEEK_SET) - Seven. I'll be in the corner holding myself and
rocking back and forth.
read(4, buf, 4096)
_llseek(4, 200704, SEEK_SET) - Hello, that's different!
read(4, buf, 4096)
_llseek(4, 0, SEEK_SET) - Eight. Danny, I'm coming!
read(4, buf, 4096)
_llseek(4, 741376, SEEK_SET)
read(4, buf, 4096)
_llseek(4, 0, SEEK_SET) - Nine. It rubs the lotion on its skin. It does this
whenever it is told.
read(4, buf, 4096)
_llseek(4, 200704, SEEK_SET)
read(4, buf, 4096)
_llseek(4, 0, SEEK_SET) - Ten. Why so serious?
read(4, buf, 4096)
_lseek(4, 741376, SEEK_SET) - Weren't we just here a few lines above?
read(4, buf, 4096)
_llseek(4, 0, SEEK_SET) - Eleven. Ours goes to eleven!
read(4, buf, 4096)
__lseek(4, 204800, SEEK_SET)
read(4, buf, 4096)
_llseek(4, 0, SEEK_SET) - Twelve.
read(4, buf, 4096)
_lseek(4, 741376, SEEK_SET) - And now we're back *here* for the third time.
read(4, buf, 4096)
There are a total of 320 seeks back to 0 and re-reads of the first 4K
of the PDF file. That is, in case my preceding comments didn't make it
cl
Bug#645108: marked as done (http://portal.gsdi.org/files/?artifact_id=928 unreadable)
Your message dated Sat, 25 Feb 2012 01:47:52 + with message-id and subject line Bug#641873: fixed in xpdf 3.03-9 has caused the Debian Bug report #641873, regarding http://portal.gsdi.org/files/?artifact_id=928 unreadable 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 ow...@bugs.debian.org immediately.) -- 641873: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=641873 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- X-Debbugs-Cc: der...@glyphandcog.com Package: xpdf Version: 3.03-5 Help, http://portal.gsdi.org/files/?artifact_id=928 has become unreadable. The sidebar content is fine though. --- End Message --- --- Begin Message --- Source: xpdf Source-Version: 3.03-9 We believe that the bug you reported is fixed in the latest version of xpdf, which is due to be installed in the Debian FTP archive: xpdf_3.03-9.debian.tar.gz to main/x/xpdf/xpdf_3.03-9.debian.tar.gz xpdf_3.03-9.dsc to main/x/xpdf/xpdf_3.03-9.dsc xpdf_3.03-9_amd64.deb to main/x/xpdf/xpdf_3.03-9_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 641...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Michael Gilbert (supplier of updated xpdf 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 ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 24 Feb 2012 17:33:29 -0500 Source: xpdf Binary: xpdf Architecture: source amd64 Version: 3.03-9 Distribution: unstable Urgency: low Maintainer: Michael Gilbert Changed-By: Michael Gilbert Description: xpdf - Portable Document Format (PDF) reader Closes: 631450 641873 652606 654308 659272 Changes: xpdf (3.03-9) unstable; urgency=low . * Let poppler find and select non-embedded font file locations. Thanks to Vincent Lefevre for finding a solution to this problem (closes: #641873). * Remove now ineffective font file configuration options from xpdfrc. * Revert UTF8 title conversion change (closes: #659272). * Revert lp as default print command. Use lpr (the privious default) and recommend cups-bsd package (closes: #652606). * Fix segfault issue in additional zoom options patch and enable it again. Thanks to Jörg-Volker Peetz (closes: #654308). * Support title refresh when starting from a non-compressed file (lp: #932062). * Use "Xpdf" instead of "xpdf" in documentation on Xresources (closes: #631450). * Check exit codes of system calls (fix -Wunused-result compiler warnings). * Fix a pointer casting to a different size (fix -Wint-to-pointer-cast compiler warning). * Add -Wno-format-extra-args to build flags. * Bump standards to 3.9.3. Checksums-Sha1: ecbf475ee87a14cde95b527d73f9e54e74ec2c99 2639 xpdf_3.03-9.dsc 314dbf3c3c906bc014564cb6b5817e13d2374523 38280 xpdf_3.03-9.debian.tar.gz 7dcc4eda5ca7424660d46f69861383dfb43b76b6 197848 xpdf_3.03-9_amd64.deb Checksums-Sha256: 5fec049173731349d519761d61a920275aa36f48a16ee5dbddc7e08f667e0b1b 2639 xpdf_3.03-9.dsc e9778ab42b4ced73f92ac28830844908dee0eca9a18379cb37867309883cac0f 38280 xpdf_3.03-9.debian.tar.gz 55018d0d06017e0696e1891b49bac25f40e0f3cfd333257e266a193b81e311b1 197848 xpdf_3.03-9_amd64.deb Files: 77d7ffb8625a0dad85507e70fe31f5c0 2639 text optional xpdf_3.03-9.dsc d0e3dff4e22589f7c76ce7bc987fc835 38280 text optional xpdf_3.03-9.debian.tar.gz 7337f0c797f0c35ca356f1be8062a473 197848 text optional xpdf_3.03-9_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iQQcBAEBCAAGBQJPSDuTAAoJELjWss0C1vRzPyogAJzF9p+lXWmDuMt1fXKNE8Z/ cw2I/0XdJyqcjFESTwmQv33PLN78ZEj3CEsiah4WYzeT5/KeYsncWC6tOyg77/T4 GQLRg0mk2lN8osKjPHmrd7pxvubug/ojIVWrzPZP7Vbwp+KW18+nuoK1HFY9pzgC s4MrZYTtVJyBHFz7XNqv32tev6yJZ04JGxh1oo0KHsZn6565vEW8uXBaMZLWtpnL Bx69oFJLyvklfFm0OU2f3w4sM0lAM9J/IymDNuChXeO5jLNf6i+os0ZIn0GRI6Df zxfgX4Qh5GmwP5orELyddOSNQoJRLoE8orb/ScOTg1Ugij4b8lY1rzEqG0fjF3tg StrKIQouuiepxhyvLsP7jsQsbQDjzz9rugvPQ3Hon2JH3sK9YgQJhRTlm2Wp5jE/ XihqHIIUsi39KO9JCXXl4RHQJ0ZEgSwIMI8lGRgVCkVAm3j/arxJImmTBnFDKp6v HP+9WJgKrg4sEgov3dMaruArgEsIrkr48vkeBcANjsU8lDSbbgUSQRap2zjC1evV CpDu4z6XnvEVPzTEhQGR3BkJy2m7PM6Ah2Y0nCBgjaM87jqMVaqIuGwskbt7cyXv VA9o9+Bowjmfttpz8tquvjsjdjIkAY/XJ0mh+H5RNZHtOiQ2hCV8WB5DqqKgZOcX CmgH5lviD7a/feVO7UBP6ZcMRqcWbz2fWqjdeOGSfS8kCoDjaHdmh8pZ0Ig6x7fD szl0jCZ/DR2MzPN6ijsrxXiGzIyVQhAMg0aq
Bug#646449: libosip2 upload to unstable
peter green wrote: Would you object to a NMU based on the version currently in unstable that just fixes the FTBFS? I have now prepared a NMU based on the version currently in sid that only fixes the FTBFS. The debdiff is attatched. libosip2 maintainers are you ok with this NMU? diff -u libosip2-3.3.0/debian/changelog libosip2-3.3.0/debian/changelog --- libosip2-3.3.0/debian/changelog +++ libosip2-3.3.0/debian/changelog @@ -1,3 +1,10 @@ +libosip2 (3.3.0-1.1) unstable; urgency=low + + * Non maintainer upload + * Fix FTBFS with format security error (Closes: #646449) + + -- Peter Michael Green Sat, 25 Feb 2012 01:30:26 + + libosip2 (3.3.0-1) unstable; urgency=low * New upstream release only in patch2: unchanged: --- libosip2-3.3.0.orig/src/osipparser2/osip_message_parse.c +++ libosip2-3.3.0/src/osipparser2/osip_message_parse.c @@ -847,7 +847,7 @@ sep_boundary = (char *) osip_malloc (len + sizeof (boundary_prefix)); if (sep_boundary==NULL) return OSIP_NOMEM; -sprintf (sep_boundary, boundary_prefix); +sprintf (sep_boundary,"%s", boundary_prefix); if (ct_param->gvalue[0] == '"' && ct_param->gvalue[len - 1] == '"') strncat (sep_boundary, ct_param->gvalue + 1, len - 2); else
Bug#661201: marked as done (relocation error)
Your message dated Sat, 25 Feb 2012 09:13:43 +0800 with message-id <87pqd3lnp4@jidanni.org> and subject line apt-get upgrade fixed it has caused the Debian Bug report #661201, regarding relocation error 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 ow...@bugs.debian.org immediately.) -- 661201: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=661201 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: iceweasel Version: 12.0~a2+20120217042010-1 Severity: grave $ firefox http://www.couchsurfing.org/home.html /usr/lib/iceweasel/firefox-bin: relocation error: /usr/lib/xulrunner-12.0/libxul.so: symbol SSL_RestartHandshakeAfterAuthCertificate, version NSS_3.13.2 not defined in file libssl3.so.1d with link time reference --- End Message --- --- Begin Message --- apt-get upgrade fixed it. But kindly don't let that happen again. --- End Message ---
Bug#661196: marked as done (relocation error)
Your message dated Sat, 25 Feb 2012 09:13:43 +0800 with message-id <87pqd3lnp4@jidanni.org> and subject line apt-get upgrade fixed it has caused the Debian Bug report #661196, regarding relocation error 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 ow...@bugs.debian.org immediately.) -- 661196: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=661196 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: iceweasel Version: 12.0~a2+20120217042010-1 Severity: grave $ firefox http://www.couchsurfing.org/home.html /usr/lib/iceweasel/firefox-bin: relocation error: /usr/lib/xulrunner-12.0/libxul.so: symbol SSL_RestartHandshakeAfterAuthCertificate, version NSS_3.13.2 not defined in file libssl3.so.1d with link time reference --- End Message --- --- Begin Message --- apt-get upgrade fixed it. But kindly don't let that happen again. --- End Message ---
Bug#633297: funguloids: FTBFS everywhere: error: reference to 'map' is ambiguous
Back in august pabs tagged this bug as pending, Looking at the SVN (which took a while to find since the PTS still points at the git repo) it seems he did commit it to the repo but soon afterwards put a notice in the changelog saying. * DO NOT UPLOAD, needs to reimplement the mpak.py from archlinux http://aur.archlinux.org/packages/fu/funguloids/PKGBUILD Can anyone explain why mpak.py needs to be reimplemented, why there doesn't seem to be a bugreport about the issue (I searched all the packages open bug reports for mpak.py and found nothing) and why it justifies leaving a FTBFS bug unfixed for so long? Following the link to arch didn't seem to reveal anything to my untrained eye. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#658341: marked as done (upload of multi-arch enabled dpkg (in time for wheezy))
Your message dated Fri, 24 Feb 2012 16:29:39 -0800
with message-id <20120225002939.gb30...@rzlab.ucr.edu>
and subject line Re: Bug#658341: Conclusion: upload multi-arch enabled dpkg (in
time for wheezy)
has caused the Debian Bug report #658341,
regarding upload of multi-arch enabled dpkg (in time for wheezy)
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 ow...@bugs.debian.org
immediately.)
--
658341: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=658341
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: tech-ctte
Severity: serious
Dear members of the Technical Committee,
I hereby submit to your attention the "dpkg multi-arch conflict".
I believe the issue is well-known, so I describe it only briefly below;
feel free to ask if you need more information.
A multi-arch [1] enabled version of dpkg has been available for quite a
while. Its inclusion in the archive has been one of the early Wheezy
release goals. Since many months now, the upload of such a version of
dpkg has been held back due to repeated NACK-s by one of the dpkg
co-maintainers (Guillem Jover, Cc-ed), based on his desire to do a full
code review of the multi-arch implementation, which has written by the
other dpkg co-maintainer (Raphael Hertzog, Cc-ed as well).
[1] http://wiki.debian.org/ReleaseGoals/MultiArch
The desire to do a full code review is good, but Guillem doesn't seem to
be able to complete the review in a reasonable time frame. Since many
months now, the delay of the upload is a cause of worry for the release
team [2] and other project members. The situation has escalated to the
point that another developer (Cyril Brulebois) has done a dpkg NMU a
couple of days ago [3]; the NMU has been promptly reverted by Guillem
[4].
[2] http://lists.debian.org/debian-dpkg/2011/10/msg00050.html
[3] http://lists.debian.org/debian-dpkg/2012/01/msg00049.html
[4] http://lists.debian.org/debian-dpkg/2012/02/msg0.html
As DPL, I'm worried about two aspects of this issue:
a) The risk of legitimating the fact that by not acting a developer can
block indefinitely the work of other developers (and possibly of the
entire project when working on a rather far reaching release goal);
I've elaborated more on this subject 3 months ago in [5].
[5] http://lists.debian.org/debian-dpkg/2011/10/msg00060.html
b) The risk of a negative impact on project morale if---due to the
reason above rather than a legitimate technical reason---we will miss
the Wheezy multi-arch release goal.
I therefore bring before you the issue of whether:
- one of the dpkg co-maintainers has the right to block indefinitely a
dpkg upload, in wait of full code review of the multi-arch code;
- or rather if the other co-maintainer has the right to override his
NACKs and go ahead with uploads that would allow project-wide testing
of the dpkg multi-arch implementation.
Many thanks in advance for your help,
Cheers.
PS I've to point out that timing on this issue is, unfortunately,
critical. The Wheezy freeze is close and according to the release
team we're already late wrt the ideal upload date for dpkg. The delay
is not tech-ctte's fault, of course, but please understand that a
long decision time on your part would be a de facto decision. I'd
appreciate if you could reach a decision on this in a timely manner.
--
Stefano Zacchiroli zack@{upsilon.cc,pps.jussieu.fr,debian.org} . o .
Maître de conférences .. http://upsilon.cc/zack .. . . o
Debian Project Leader... @zack on identi.ca ...o o o
« the first rule of tautology club is the first rule of tautology club »
signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
On Sun, 05 Feb 2012, Bdale Garbee wrote:
> On Thu, 02 Feb 2012 08:16:34 -0700, Bdale Garbee wrote:
> > I therefore call for an immediate vote on the following ballot.
>
> With votes from 7 of 8 committee members, all ranking A as their first
> preference, the outcome of this ballot is no longer in doubt, and we have
> met the required > 3:1 majority.
Marking this bug as done; see
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=658341#73 for the
final decision.
Don Armstrong
--
I now know how retro SCOs OSes are. Riotous, riotous stuff. How they
had the ya-yas to declare Linux an infant OS in need of their IP is
beyond me. Upcoming features? PAM. files larger than 2 gigs. NFS over
TCP. The 80's called, they want their features back.
-- Compactable Dave http://www3.sympatico.ca/dcarpeneto/sco.html
http://www.donarmstrong.com http://rzlab.ucr
Bug#607368: Call for Vote: Kernel ABI numbering policy
<#part sign=pgpmime> On Fri, 24 Feb 2012 12:04:55 -0800, Don Armstrong wrote: > I call for a vote on the kernel ABI numbering policy bug with the > following ballot: > > A) The technical committee declines to override the kernel maintenance > team's ABI numbering policy. > > B) Further discussion > > END. I vote AB. Bdale -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#661196: can't figure out how to back out
clone 661196 -1 reassign -1 libnss3-1d found -1 3.13.3-1 thanks -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: can't figure out how to back out
Processing commands for cont...@bugs.debian.org: > clone 661196 -1 Bug#661196: relocation error Bug 661196 cloned as bug 661201. > reassign -1 libnss3-1d Bug #661201 [iceweasel] relocation error Bug reassigned from package 'iceweasel' to 'libnss3-1d'. Bug No longer marked as found in versions 12.0~a2+20120217042010-1. > found -1 3.13.3-1 Bug #661201 [libnss3-1d] relocation error Bug Marked as found in versions nss/3.13.3-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 661201: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=661201 661196: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=661196 -1: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=-1 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#660857: marked as done (owfs: FTBFS(kfreebsd): libow.so: undefined reference to `w1_bind')
Your message dated Fri, 24 Feb 2012 23:18:36 + with message-id and subject line Bug#660857: fixed in owfs 2.8p14-2 has caused the Debian Bug report #660857, regarding owfs: FTBFS(kfreebsd): libow.so: undefined reference to `w1_bind' 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 ow...@bugs.debian.org immediately.) -- 660857: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=660857 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:owfs Version: 2.8p14-1 Severity: serious Tags: sid wheezy User: debian-...@lists.debian.org Usertags: kfreebsd X-Debbugs-Cc: debian-...@lists.debian.org Justification: fails to build from source (but built successfully in the past) Hi! Your package failed to build on the kfreebsd-* buildds: libtool: link: gcc -I../include -I../../../owlib/src/include -fexceptions -Wall -W -Wundef -Wshadow -Wpointer-arith -Wcast-qual -Wcast-align -Wstrict-prototypes -Wredundant-decls -D_FILE_OFFSET_BITS=64 -D_XOPEN_SOURCE=500 -D_BSD_SOURCE=1 -D_ISOC99_SOURCE=1 -D_POSIX_C_SOURCE=200112L -g -O2 -D_XOPEN_SOURCE=500 -D_BSD_SOURCE=1 -D_ISOC99_SOURCE=1 -D_POSIX_C_SOURCE=200112L -o .libs/owhttpd owhttpd.o owhttpd_handler.o owhttpd_present.o owhttpd_write.o owhttpd_read.o owhttpd_dir.o owhttpd_escape.o owhttpd_favicon.o -L../../../owlib/src/c /build/buildd-owfs_2.8p14-1-kfreebsd-amd64-6a9p4W/owfs-2.8p14/module/owlib/src/c/.libs/libow.so -pthread /build/buildd-owfs_2.8p14-1-kfreebsd-amd64-6a9p4W/owfs-2.8p14/module/owlib/src/c/.libs/libow.so: undefined reference to `w1_bind' collect2: ld returned 1 exit status make[5]: *** [owhttpd] Error 1 Full build log at https://buildd.debian.org/status/fetch.php?pkg=owfs&arch=kfreebsd-i386&ver=2.8p14-1&stamp=1329428876 Regards Christoph If you have further questions please mail debian-...@lists.debian.org --- End Message --- --- Begin Message --- Source: owfs Source-Version: 2.8p14-2 We believe that the bug you reported is fixed in the latest version of owfs, which is due to be installed in the Debian FTP archive: libow-2.8-14_2.8p14-2_amd64.deb to main/o/owfs/libow-2.8-14_2.8p14-2_amd64.deb libow-dev_2.8p14-2_amd64.deb to main/o/owfs/libow-dev_2.8p14-2_amd64.deb libow-perl_2.8p14-2_amd64.deb to main/o/owfs/libow-perl_2.8p14-2_amd64.deb libow-php5_2.8p14-2_amd64.deb to main/o/owfs/libow-php5_2.8p14-2_amd64.deb libow-tcl_2.8p14-2_amd64.deb to main/o/owfs/libow-tcl_2.8p14-2_amd64.deb libowcapi-2.8-14_2.8p14-2_amd64.deb to main/o/owfs/libowcapi-2.8-14_2.8p14-2_amd64.deb libownet-2.8-14_2.8p14-2_amd64.deb to main/o/owfs/libownet-2.8-14_2.8p14-2_amd64.deb libownet-dev_2.8p14-2_amd64.deb to main/o/owfs/libownet-dev_2.8p14-2_amd64.deb libownet-perl_2.8p14-2_all.deb to main/o/owfs/libownet-perl_2.8p14-2_all.deb libownet-php_2.8p14-2_all.deb to main/o/owfs/libownet-php_2.8p14-2_all.deb ow-shell_2.8p14-2_amd64.deb to main/o/owfs/ow-shell_2.8p14-2_amd64.deb owfs-common_2.8p14-2_all.deb to main/o/owfs/owfs-common_2.8p14-2_all.deb owfs-dbg_2.8p14-2_amd64.deb to main/o/owfs/owfs-dbg_2.8p14-2_amd64.deb owfs-doc_2.8p14-2_all.deb to main/o/owfs/owfs-doc_2.8p14-2_all.deb owfs-fuse_2.8p14-2_amd64.deb to main/o/owfs/owfs-fuse_2.8p14-2_amd64.deb owfs_2.8p14-2.debian.tar.gz to main/o/owfs/owfs_2.8p14-2.debian.tar.gz owfs_2.8p14-2.dsc to main/o/owfs/owfs_2.8p14-2.dsc owfs_2.8p14-2_all.deb to main/o/owfs/owfs_2.8p14-2_all.deb owftpd_2.8p14-2_amd64.deb to main/o/owfs/owftpd_2.8p14-2_amd64.deb owhttpd_2.8p14-2_amd64.deb to main/o/owfs/owhttpd_2.8p14-2_amd64.deb owserver_2.8p14-2_amd64.deb to main/o/owfs/owserver_2.8p14-2_amd64.deb python-ow_2.8p14-2_amd64.deb to main/o/owfs/python-ow_2.8p14-2_amd64.deb python-ownet_2.8p14-2_all.deb to main/o/owfs/python-ownet_2.8p14-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 660...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Vincent Danjean (supplier of updated owfs 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 ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 24 Feb 2012 22:48:38 +0100 Source: owfs Binary: owfs-common owfs libow-2.8-14 libowcapi-2.8-14 libow-dev libownet-2.8-14 libownet-dev owserver ow-shell owfs-fuse owhttpd owftpd libow-php5 libownet-php libow-perl libownet-perl py
Bug#661099: fpc depends on packages that can't be installed
On Fri, 24 Feb 2012, Abou Al Montacir wrote: Can you please clarify more the situation? You are using Squeeze or a mix of Squeeze and other repositories? What are the dependencies that are missing? Aptitude will give you the full dependency tree, can you please provide this? I'm using Squeeze with the following extra repositories: deb http://backports.debian.org/debian-backports squeeze-backports main deb-src http://backports.debian.org/debian-backports squeeze-backports main deb http://mozilla.debian.net/ squeeze-backports iceweasel-release deb http://www.debian-multimedia.org stable main non-free deb-src http://www.debian-multimedia.org stable main non-free I'm not sure I understand what you mean by "dependencies that are missing". I thought I explained that. These: 1) fp-units-gnome1 [Not Installed] 2) fp-units-gtk [Not Installed] 3) fpc [Not Installed] 4) libcairo2-dev [Not Installed] 5) libgtk2.0-dev [Not Installed] 6) libpango1.0-dev [Not Installed] -- David Griffith d...@661.org -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#661197: CVE-2012-0270: buffer overflows
Package: csound Severity: grave Tags: security Hi, Two vulnerabilities have been found in csound. Please refer to the following page for more information: http://secunia.com/secunia_research/2012-3/ Regards, Raphael Geissert -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: user debian...@lists.debian.org, usertagging 661013, affects 661013
Processing commands for cont...@bugs.debian.org: > user debian...@lists.debian.org Setting user to debian...@lists.debian.org (was deb...@abeckmann.de). > usertags 661013 piuparts Bug#661013: qmail: fails to purge Usertags were: piuparts. Usertags are now: piuparts. > affects 661013 + qmail-run Bug #661013 [qmail] qmail: fails to purge Bug #640593 [qmail] qmail: package purge (after dependencies removal) fails Added indication that 661013 affects qmail-run Added indication that 640593 affects qmail-run > thanks Stopping processing here. Please contact me if you need assistance. -- 661013: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=661013 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#661196: relocation error
Package: iceweasel Version: 12.0~a2+20120217042010-1 Severity: grave $ firefox http://www.couchsurfing.org/home.html /usr/lib/iceweasel/firefox-bin: relocation error: /usr/lib/xulrunner-12.0/libxul.so: symbol SSL_RestartHandshakeAfterAuthCertificate, version NSS_3.13.2 not defined in file libssl3.so.1d with link time reference -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: your mail
Processing commands for cont...@bugs.debian.org: > forcemerge 641873 653437 Bug#641873: xpdf doesn't display text in many PDF files Bug#653437: xpdf: type1 fonts not rendered Bug#645108: http://portal.gsdi.org/files/?artifact_id=928 unreadable Bug#646223: cannot read timetables anymore Bug#647576: can't read pdfs any more Forcibly Merged 641873 645108 646223 647576 653437. > thanks Stopping processing here. Please contact me if you need assistance. -- 645108: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=645108 646223: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=646223 647576: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=647576 641873: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=641873 653437: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=653437 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#660864: marked as done (gtk2hs-buildtools: FTBFS with ghc 7.4.1)
Your message dated Fri, 24 Feb 2012 22:02:11 + with message-id and subject line Bug#660864: fixed in gtk2hs-buildtools 0.12.1-2 has caused the Debian Bug report #660864, regarding gtk2hs-buildtools: FTBFS with ghc 7.4.1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 660864: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=660864 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: gtk2hs-buildtools Version: 0.12.1-1 Severity: serious Justification: FTBFS Hello, gtk2hs-buildtools FTBFS with ghc 7.4.1, see log: https://buildd.debian.org/status/fetch.php?pkg=gtk2hs-buildtools&arch=hurd-i386&ver=0.12.1-1&stamp=1328781063 the log is on hurd-i386, but it happens on amd64 too. The same issue actually also happens on a few other packages: missingh haskell-happstack-util haxml haskell-pwstore-fast haskell-rsa Samuel -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.0.4 (SMP w/8 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- Samuel Thibault la vraie vie, c'est quand le prompt passe de $ à # --- End Message --- --- Begin Message --- Source: gtk2hs-buildtools Source-Version: 0.12.1-2 We believe that the bug you reported is fixed in the latest version of gtk2hs-buildtools, which is due to be installed in the Debian FTP archive: gtk2hs-buildtools_0.12.1-2.debian.tar.gz to main/g/gtk2hs-buildtools/gtk2hs-buildtools_0.12.1-2.debian.tar.gz gtk2hs-buildtools_0.12.1-2.dsc to main/g/gtk2hs-buildtools/gtk2hs-buildtools_0.12.1-2.dsc gtk2hs-buildtools_0.12.1-2_amd64.deb to main/g/gtk2hs-buildtools/gtk2hs-buildtools_0.12.1-2_amd64.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 660...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Joachim Breitner (supplier of updated gtk2hs-buildtools 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 ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Fri, 24 Feb 2012 22:50:05 +0100 Source: gtk2hs-buildtools Binary: gtk2hs-buildtools Architecture: source amd64 Version: 0.12.1-2 Distribution: unstable Urgency: low Maintainer: Debian Haskell Group Changed-By: Joachim Breitner Description: gtk2hs-buildtools - Tools to build the Gtk2Hs suite of User Interface libraries Closes: 643149 660864 Changes: gtk2hs-buildtools (0.12.1-2) unstable; urgency=low . * Build-Depend on libghc-random-dev (Closes: 660864) * Also, now it does not FTBFS any more (Closes: #643149) Checksums-Sha1: 3b70b12583414589da64e7696a59a17bac515561 1504 gtk2hs-buildtools_0.12.1-2.dsc e7de4ff41e9ed59547b5b42c8af58ab2f500e529 6115 gtk2hs-buildtools_0.12.1-2.debian.tar.gz dc3e2f54c382fe09a120273464bf1e5a9206ebaa 1249888 gtk2hs-buildtools_0.12.1-2_amd64.deb Checksums-Sha256: 5e75a623623d6900949b019b59a198aadfbf474e55999b038a3a0ebd921721e3 1504 gtk2hs-buildtools_0.12.1-2.dsc 71a5beaedd753d1e5da5b9ab97d9e5df8a597933b46578e626697e6d3ded7c8f 6115 gtk2hs-buildtools_0.12.1-2.debian.tar.gz 688c761c791efa86061a26bc725e1d8c70a1d0511959275d9a14bf9ad8765469 1249888 gtk2hs-buildtools_0.12.1-2_amd64.deb Files: a4332217784bf8aaf1a504f19eeb1fe9 1504 haskell extra gtk2hs-buildtools_0.12.1-2.dsc ee21fab7830a5777fff3d2707e2e5e1b 6115 haskell extra gtk2hs-buildtools_0.12.1-2.debian.tar.gz cd6b50d1d5bfd1d541d5b7d85d31a4b7 1249888 haskell extra gtk2hs-buildtools_0.12.1-2_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iEYEARECAAYFAk9IBpYACgkQ9ijrk0dDIGzyuwCgzX/4TurzLbVu+QuvCFqA2bbz 1qUAn07tuPXrx4d7zcXJjv+vGUxqCpfS =OMpH -END PGP SIGNATURE- --- End Message ---
Bug#588588: aircrack-ng: debian/copyright is missing information for src/sha1-sse2.*
Pablo Santamaria wrote (10 Feb 2012 14:43:28 GMT) : > Is anyone working on this? Yes: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=642934 http://trac.aircrack-ng.org/ticket/953 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#607368: Call for Vote: Kernel ABI numbering policy
On Fri, 24 Feb 2012, Don Armstrong wrote: > I call for a vote on the kernel ABI numbering policy bug with the > following ballot: > > A) The technical committee declines to override the kernel maintenance > team's ABI numbering policy. > > B) Further discussion > > END. I vote AB. Don Armstrong -- "She decided what she wished to happen and then assumed that reality would bend to her wishes." [...] "Reality doesn't indulge wishes." -- Terry Goodkind _Phantom_ p133 http://www.donarmstrong.com http://rzlab.ucr.edu -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#626019: hang even on amd64 with backtrace
Hi!
I was able to reproduce the hang on amd64. Attached is a backtrace,
unfortunately from an optimized build but maybe it gives someone a quick
idea what's going on.
WM
#0 __lll_lock_wait_private () at
../nptl/sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:97
#1 0x2b8ad36223f8 in _L_lock_9627 () from /lib/x86_64-linux-gnu/libc.so.6
#2 0x2b8ad36207e1 in *__GI___libc_free (mem=0x2b8ad3928e60) at
malloc.c:3736
#3 0x2b8ad3b6ccd2 in XS_Sane__Device_DESTROY (my_perl=,
cv=) at Sane.xs:17
#4 0x2b8ad2c3d54f in Perl_pp_entersub (my_perl=0x146a010) at pp_hot.c:3046
#5 0x2b8ad2bd0572 in Perl_call_sv (my_perl=0x146a010, sv=0x1675d80,
flags=45) at perl.c:2647
#6 0x2b8ad2c43888 in S_curse (check_refcnt=1 '\001', sv=0x1624418,
my_perl=0x146a010) at sv.c:6342
#7 Perl_sv_clear (my_perl=0x146a010, orig_sv=0x1624418) at sv.c:6073
#8 0x2b8ad2c43f72 in Perl_sv_free2 (my_perl=0x146a010, sv=0x1624418) at
sv.c:6474
#9 0x2b8ad2c6bdb8 in Perl_leave_scope (my_perl=0x146a010, base=4) at
scope.c:900
#10 0x2b8ad2c75d50 in Perl_pp_leaveloop (my_perl=0x146a010) at pp_ctl.c:2249
#11 0x2b8ad2c34a06 in Perl_runops_standard (my_perl=0x146a010) at run.c:41
#12 0x2b8ad2bd612a in S_run_body (oldscope=1, my_perl=0x146a010) at
perl.c:2350
#13 perl_run (my_perl=0x146a010) at perl.c:2268
#14 0x00400ee9 in main (argc=3, argv=0x7fff667cf7e8,
env=0x7fff667cf808) at perlmain.c:120
(gdb) bt full
#0 __lll_lock_wait_private () at
../nptl/sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:97
No locals.
#1 0x2b8ad36223f8 in _L_lock_9627 () from /lib/x86_64-linux-gnu/libc.so.6
No symbol table info available.
#2 0x2b8ad36207e1 in *__GI___libc_free (mem=0x2b8ad3928e60) at
malloc.c:3736
ignore1 = 128
ignore2 =
ignore3 = -512
ar_ptr = 0x2b8ad3928e60
p = 0x14982e0
#3 0x2b8ad3b6ccd2 in XS_Sane__Device_DESTROY (my_perl=,
cv=) at Sane.xs:17
handle = 0x14982f0
sv = 0x161e740
sp =
ax = 1
mark =
items =
#4 0x2b8ad2c3d54f in Perl_pp_entersub (my_perl=0x146a010) at pp_hot.c:3046
markix = 0
sp =
sv = 0x1675d80
gv = 0x0
cv = 0x1675d80
cx =
gimme = 1
hasargs =
#5 0x2b8ad2bd0572 in Perl_call_sv (my_perl=0x146a010, sv=0x1675d80,
flags=45) at perl.c:2647
sp =
myop = {op_next = 0x0, op_sibling = 0x0, op_ppaddr = 0, op_targ = 0,
op_type = 0, op_opt = 0, op_latefree = 0, op_latefreed = 0, op_attached = 0,
op_spare = 0, op_flags = 65 'A', op_private = 0 '\000', op_first =
0x0, op_other = 0x7fff667cf370}
method_op = {op_next = 0x165cbd0, op_sibling = 0x1675d80, op_ppaddr =
0x1623f38, op_targ = 21407824, op_type = 128, op_opt = 0, op_latefree = 0,
op_latefreed = 1, op_attached = 0, op_spare = 5, op_flags = 70 'F',
op_private = 1 '\001', op_first = 0x2b8ad2c43162}
oldmark = 0
retval = 0
---Type to continue, or q to quit---
oldscope = 5
oldcatch = 0 '\000'
ret =
oldop = 0x161d680
cur_env = {je_prev = 0x7fff667cf5d0, je_buf = {{__jmpbuf =
{140734912852848, 6804210356706508014, 0, 21955016, 23448528, 21407872,
-6803910496586662674, 682522875078278382}, __mask_was_saved =
0, __saved_mask = {__val = {79, 47875266131712, 140734912853196, 0,
47875266131712, 47875261884042, 21405712, 206158430224,
140734912852976, 140734912852784, 21405712, 21636752, 21407848, 23448528,
47875249246256, 0, je_ret = 0, je_mustcatch = 0 '\000'}
#6 0x2b8ad2c43888 in S_curse (check_refcnt=1 '\001', sv=0x1624418,
my_perl=0x146a010) at sv.c:6342
tmpref = 0x165cbd0
destructor = 0x1675d80
sp =
stash = 0x1623f38
#7 Perl_sv_clear (my_perl=0x146a010, orig_sv=0x1624418) at sv.c:6073
stash =
type = 7
sv_type_details =
iter_sv =
next_sv =
sv =
#8 0x2b8ad2c43f72 in Perl_sv_free2 (my_perl=0x146a010, sv=0x1624418) at
sv.c:6474
No locals.
#9 0x2b8ad2c6bdb8 in Perl_leave_scope (my_perl=0x146a010, base=4) at
scope.c:900
uv =
type =
sv = 0x148c098
value =
gv =
av =
hv =
ptr = 0x1495cd8
str =
i =
was = 0 '\000'
---Type to continue, or q to quit---
#10 0x2b8ad2c75d50 in Perl_pp_leaveloop (my_perl=0x146a010) at pp_ctl.c:2249
sp = 0x146f710
cx = 0x146fb70
gimme =
newsp = 0x146f710
newpm = 0x0
mark =
#11 0x2b8ad2c34a06 in Perl_runops_standard (my_perl=0x146a010) at run.c:41
op =
#12 0x2b8ad2bd612a in S_run_body (oldscope=1, my_perl=0x146a010) at
perl.c:2350
No locals.
#13 perl_run (my_perl=0x146a010) at perl.c:2268
oldscope = 1
ret =
cur_env = {je_prev = 0x146a288, je_buf = {{__jmpbuf = {0,
6804212853877669102, 419
Bug#607368: Call for Vote: Kernel ABI numbering policy
I call for a vote on the kernel ABI numbering policy bug with the following ballot: A) The technical committee declines to override the kernel maintenance team's ABI numbering policy. B) Further discussion END. Don Armstrong -- Who is thinking this? I am. -- Greg Egan _Diaspora_ p38 http://www.donarmstrong.com http://rzlab.ucr.edu -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#646480: marked as done (lde: FTBFS: (.text+0x95): undefined reference to `_nc_screen_of')
Your message dated Fri, 24 Feb 2012 19:45:16 + with message-id and subject line Bug#650824: Removed package(s) from unstable has caused the Debian Bug report #646480, regarding lde: FTBFS: (.text+0x95): undefined reference to `_nc_screen_of' 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 ow...@bugs.debian.org immediately.) -- 646480: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=646480 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: lde Version: 2.6.0-7.1 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20111022 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: > /usr/lib/gcc/x86_64-linux-gnu/4.6/../../../x86_64-linux-gnu/libncurses.a(hashmap.o):(.text+0xbc3): > more undefined references to `SP' follow > /usr/lib/gcc/x86_64-linux-gnu/4.6/../../../x86_64-linux-gnu/libncurses.a(lib_getch.o): > In function `_nc_wgetch': > (.text+0x95): undefined reference to `_nc_screen_of' > /usr/lib/gcc/x86_64-linux-gnu/4.6/../../../x86_64-linux-gnu/libncurses.a(lib_getch.o): > In function `_nc_wgetch': > (.text+0x184): undefined reference to `_nc_keypad' > /usr/lib/gcc/x86_64-linux-gnu/4.6/../../../x86_64-linux-gnu/libncurses.a(lib_getch.o): > In function `_nc_wgetch': > (.text+0x2e9): undefined reference to `_nc_timed_wait' > /usr/lib/gcc/x86_64-linux-gnu/4.6/../../../x86_64-linux-gnu/libncurses.a(lib_getch.o): > In function `_nc_wgetch': > (.text+0x3bc): undefined reference to `_nc_handle_sigwinch' > /usr/lib/gcc/x86_64-linux-gnu/4.6/../../../x86_64-linux-gnu/libncurses.a(lib_getch.o): > In function `_nc_wgetch': > (.text+0x3cc): undefined reference to `_nc_update_screensize' > /usr/lib/gcc/x86_64-linux-gnu/4.6/../../../x86_64-linux-gnu/libncurses.a(lib_getch.o): > In function `_nc_wgetch': > (.text+0x496): undefined reference to `_nc_timed_wait' > /usr/lib/gcc/x86_64-linux-gnu/4.6/../../../x86_64-linux-gnu/libncurses.a(lib_getch.o): > In function `_nc_wgetch': > (.text+0x505): undefined reference to `_nc_timed_wait' > /usr/lib/gcc/x86_64-linux-gnu/4.6/../../../x86_64-linux-gnu/libncurses.a(lib_getch.o): > In function `_nc_wgetch': > (.text+0x556): undefined reference to `_nc_timed_wait' > /usr/lib/gcc/x86_64-linux-gnu/4.6/../../../x86_64-linux-gnu/libncurses.a(lib_getch.o): > In function `_nc_wgetch': > (.text+0x888): undefined reference to `_nc_screen_of' > /usr/lib/gcc/x86_64-linux-gnu/4.6/../../../x86_64-linux-gnu/libncurses.a(lib_getch.o): > In function `_nc_wgetch': > (.text+0xae1): undefined reference to `_nc_timed_wait' > /usr/lib/gcc/x86_64-linux-gnu/4.6/../../../x86_64-linux-gnu/libncurses.a(lib_getch.o): > In function `wgetch': > (.text+0xd59): undefined reference to `_nc_screen_of' > /usr/lib/gcc/x86_64-linux-gnu/4.6/../../../x86_64-linux-gnu/libncurses.a(lib_hline.o): > In function `whline': > (.text+0xc3): undefined reference to `acs_map' > /usr/lib/gcc/x86_64-linux-gnu/4.6/../../../x86_64-linux-gnu/libncurses.a(lib_pad.o): > In function `pnoutrefresh': > (.text+0x11a): undefined reference to `_nc_screen_of' > /usr/lib/gcc/x86_64-linux-gnu/4.6/../../../x86_64-linux-gnu/libncurses.a(lib_slkclear.o): > In function `slk_clear': > (.text+0x7): undefined reference to `SP' > /usr/lib/gcc/x86_64-linux-gnu/4.6/../../../x86_64-linux-gnu/libncurses.a(lib_slkclear.o): > In function `slk_clear': > (.text+0x48): undefined reference to `SP' > /usr/lib/gcc/x86_64-linux-gnu/4.6/../../../x86_64-linux-gnu/libncurses.a(lib_slktouch.o): > In function `slk_touch': > (.text+0x3): undefined reference to `SP' > /usr/lib/gcc/x86_64-linux-gnu/4.6/../../../x86_64-linux-gnu/libncurses.a(lib_ungetch.o): > In function `ungetch': > (.text+0xd5): undefined reference to `SP' > collect2: ld returned 1 exit status The full build log is available from: http://people.debian.org/~lucas/logs/2011/10/22/lde_2.6.0-7.1_lsid64.buildlog A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems. --- End Message --- --- Begin Message --- Version: 2.6.0-7.1+rm Dear submitter, as the package lde has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see http://bugs.debian.org/650824 The version of this
Bug#634288: marked as done (libgtfb0: Royally broken symlinks - refers to the build system)
Your message dated Fri, 24 Feb 2012 19:43:20 + with message-id and subject line Bug#660916: Removed package(s) from unstable has caused the Debian Bug report #634288, regarding libgtfb0: Royally broken symlinks - refers to the build system 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 ow...@bugs.debian.org immediately.) -- 634288: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=634288 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libgtfb0 Version: 0.1.0-1 Severity: important -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi, To mention an example: usr/lib/libgtfb.so.0.1 -> /build/buildd-libgtfb_0.1.0-1-i386-OqLWbI/libgtfb-0.1.0/debian/tmp/usr/lib/libgtfb.so.0.1.0 ~Niels Reference: http://lintian.debian.org/full/flat...@ieee.org.html#libgtfb - -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.39-2-686-pae (SMP w/2 CPU cores) Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iQIcBAEBCAAGBQJOJDShAAoJEAVLu599gGRCGQ0P/RwSsOYRYx5Di3ZZYhdHwfvH Xs3+cYNcQoe3bYdnsK7PpSkbW9ZTyU26OcJ6ZEV9g9VH0IegoWMPhjeW8mkZggiB cc989gpf83w1mX0I4zmpClNhzIUhw9Xi/0R35ejQFwcpzIKP4p4uOZ6LwPoxob87 qvDyrDI5KWb3cuW5WK2HmbEhr8wsiT/3ARwAsDM/Q4AJ9GXrpN/4bxqgK5eo17C1 5DHb/EJB1qZ35ToGegM7sOM9skGbP+WINy9GoVepgf1yXY33farSdjrKN/Ke3LUV x2HtbMHPZtB/pGVJHhdm4HDcwoiQBz8VLz3zwvxesg6g9Mc77PWynzLe1oUVgvTG FNsFd0lfeQSpzNBEuWA74I2DkmkZqd1zHI6U9LQLp0jAGq+QxWYr3OO8wvIHMzbH jycW/BEJRto/ix/IlpaAskJ4E5u7iWuokpyG3PnAB5WC/JV76utokTEBDtwggktJ 9YufWLwZ7RuzeTSE6T2v7eu3p5ABzdhzhzH6Ws7SO570fyzsXJqxDpnmDBAAWJLU WNSeo8WVjTSkIphxduV4isPsV8Fh9xpHKHavaJQTOJ3BcFcnc/YeN4+cv9gOivSz BoqiCGaO39DSqlyHpYnG+Q1lM+kWg6zw6gNi4CePKhyMgRnEGHR+iAxHXaqXsaZX jEdOBQTf2SP71leZ4MZf =CNvR -END PGP SIGNATURE- --- End Message --- --- Begin Message --- Version: 0.1.0-1+rm Dear submitter, as the package libgtfb has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see http://bugs.debian.org/660916 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org. Debian distribution maintenance software pp. Ansgar Burchardt (the ftpmaster behind the curtain) --- End Message ---
Bug#646449: libosip2 upload to unstable
We are currently awaiting a transition slot via debian-release. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=656839 Understood According to the endorsed workflow, we should not upload to unstable without approval from the release team: http://wiki.debian.org/Teams/ReleaseTeam/Transitions You should not make an upload that starts a transition without approval from the release team, that is not the same thing as making no uploads at all. So please do not NMU, until this cordination is complete. Would you object to a NMU based on the version currently in unstable that just fixes the FTBFS? -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: severity of 649038 is important
Processing commands for cont...@bugs.debian.org: > # Not an RC bug in this package > severity 649038 important Bug #649038 [elfutils] elfutils FTBFS on kfreebsd Severity set to 'important' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 649038: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=649038 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#659687: Multiple security issues
On Mon, Feb 13, 2012 at 09:15:43AM +0100, Moritz Muehlenhoff wrote: > Package: mysql-5.1 > Severity: grave > Tags: security > > Multiple security issues have been announced in MySQL: > http://www.oracle.com/technetwork/topics/security/cpujan2012-366304.html#AppendixMSQL > > Unfortunately Oracle refuses to release specific information, which allow > isolating > security fixes. As such, we should proceed by releasing 5.1.61 in > stable-security. MySQL maintainers, can you please prepare packages for 5.1.61 for stable-security? This has been unfixed for too long. Cheers, Moritz -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#661092: marked as done (mcrl2 and libowfat-dev: error when trying to install together)
On Fri, Feb 24, 2012 at 07:04:05PM +0100, Roland Stigge wrote: > Hi, > > On 02/24/2012 04:51 PM, Debian Bug Tracking System wrote: > > Changes: > > mcrl2 (201202.0-2) unstable; urgency=low > > . > >[ Jeroen Keiren ] > >* Bugfix upload (closes: #661092). > > Would you please next time write what you actually did? The fact the you > fixed a bug is already there via the "Closes:" statement. It also implies that the entire upload centers around the bugfix. In this case, the second entry that mentions the fix: * debian/patches/series, debian/patches/dparser_header_fixes.patch: - Install headers belonging to dparser in their own directory. Cheers, Paul -- Using the Power of Debian GNU/Linux | E-mail: pau...@debian.org Jabber/GTalk: p...@luon.net | GnuPG key ID: 0x50064181 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#661161: dh-apparmor: is not co-installable with current debhelper
intrig...@debian.org wrote (24 Feb 2012 16:27:24 GMT) : > (As a side note, it's not clear to me what's the point of this package > at all. [...] By chance, I eventually found #649784, so it's now clear to me. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#661092: marked as done (mcrl2 and libowfat-dev: error when trying to install together)
Hi, On 02/24/2012 04:51 PM, Debian Bug Tracking System wrote: > Changes: > mcrl2 (201202.0-2) unstable; urgency=low > . >[ Jeroen Keiren ] >* Bugfix upload (closes: #661092). Would you please next time write what you actually did? The fact the you fixed a bug is already there via the "Closes:" statement. Thanks! Roland -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#661074: marked as done (isdnlog.postinst: 73: /var/lib/dpkg/info/isdnlog.postinst: cannot open /usr/share/isdn/default/isdnlog.DEVICE: No such file)
Your message dated Fri, 24 Feb 2012 17:33:07 + with message-id and subject line Bug#661074: fixed in isdnutils 1:3.9.20060704+dfsg.3-4 has caused the Debian Bug report #661074, regarding isdnlog.postinst: 73: /var/lib/dpkg/info/isdnlog.postinst: cannot open /usr/share/isdn/default/isdnlog.DEVICE: No such file 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 ow...@bugs.debian.org immediately.) -- 661074: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=661074 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: isdnlog Version: 1:3.9.20060704+dfsg.3-3 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install. As per definition of the release team this makes the package too buggy for a release, thus the severity. >From the attached log (scroll to the bottom...): Selecting previously unselected package isdnlog. (Reading database ... 6735 files and directories currently installed.) Unpacking isdnlog (from .../isdnlog_1%3a3.9.20060704+dfsg.3-3_amd64.deb) ... Setting up isdnlog (1:3.9.20060704+dfsg.3-3) ... First time configuration, creating /etc/isdn/isdn.conf . Warning: no suitable isdn.conf file found, creating an empty one. Creating /etc/isdn/rate.conf . Warning: no suitable rate.conf file found, creating an empty one. Can't open /etc/isdn/isdn.conf: No such file or directory. Creating default /etc/isdn/isdnlog.isdnctrl0 . /var/lib/dpkg/info/isdnlog.postinst: 73: /var/lib/dpkg/info/isdnlog.postinst: cannot open /usr/share/isdn/default/isdnlog.DEVICE: No such file dpkg: error processing isdnlog (--configure): subprocess installed post-installation script returned error exit status 2 configured to not write apport reports Errors were encountered while processing: isdnlog cheers, Andreas --- End Message --- --- Begin Message --- Source: isdnutils Source-Version: 1:3.9.20060704+dfsg.3-4 We believe that the bug you reported is fixed in the latest version of isdnutils, which is due to be installed in the Debian FTP archive: capiutils_3.9.20060704+dfsg.3-4_i386.deb to main/i/isdnutils/capiutils_3.9.20060704+dfsg.3-4_i386.deb ipppd_3.9.20060704+dfsg.3-4_i386.deb to main/i/isdnutils/ipppd_3.9.20060704+dfsg.3-4_i386.deb isdnlog-data_3.9.20060704+dfsg.3-4_all.deb to main/i/isdnutils/isdnlog-data_3.9.20060704+dfsg.3-4_all.deb isdnlog_3.9.20060704+dfsg.3-4_i386.deb to main/i/isdnutils/isdnlog_3.9.20060704+dfsg.3-4_i386.deb isdnutils-base_3.9.20060704+dfsg.3-4_i386.deb to main/i/isdnutils/isdnutils-base_3.9.20060704+dfsg.3-4_i386.deb isdnutils-doc_3.9.20060704+dfsg.3-4_all.deb to main/i/isdnutils/isdnutils-doc_3.9.20060704+dfsg.3-4_all.deb isdnutils-xtools_3.9.20060704+dfsg.3-4_i386.deb to main/i/isdnutils/isdnutils-xtools_3.9.20060704+dfsg.3-4_i386.deb isdnutils_3.9.20060704+dfsg.3-4.debian.tar.gz to main/i/isdnutils/isdnutils_3.9.20060704+dfsg.3-4.debian.tar.gz isdnutils_3.9.20060704+dfsg.3-4.dsc to main/i/isdnutils/isdnutils_3.9.20060704+dfsg.3-4.dsc isdnvbox_3.9.20060704+dfsg.3-4_i386.deb to main/i/isdnutils/isdnvbox_3.9.20060704+dfsg.3-4_i386.deb isdnvboxclient_3.9.20060704+dfsg.3-4_i386.deb to main/i/isdnutils/isdnvboxclient_3.9.20060704+dfsg.3-4_i386.deb isdnvboxserver_3.9.20060704+dfsg.3-4_i386.deb to main/i/isdnutils/isdnvboxserver_3.9.20060704+dfsg.3-4_i386.deb libcapi20-3_3.9.20060704+dfsg.3-4_i386.deb to main/i/isdnutils/libcapi20-3_3.9.20060704+dfsg.3-4_i386.deb libcapi20-dev_3.9.20060704+dfsg.3-4_i386.deb to main/i/isdnutils/libcapi20-dev_3.9.20060704+dfsg.3-4_i386.deb pppdcapiplugin_3.9.20060704+dfsg.3-4_i386.deb to main/i/isdnutils/pppdcapiplugin_3.9.20060704+dfsg.3-4_i386.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 661...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Rolf Leggewie (supplier of updated isdnutils 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 ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Fri, 24 Feb 2012 23:07:18 +0800 Source: isdnutils Binary: isdnutils-base isdnutils-xtools ipppd isdnlog isdnlog-data isdnutils-doc isdnvbox isdnvboxclient isdnvboxserver capiutils libcapi20-3 libcapi20-dev pppdcapiplugin Architecture: source all i386 Version: 1:
Bug#656204: marked as done (libcapi20-dev: conflict when overwriting `/usr/lib/libcapi20.so` during upgrade)
Your message dated Fri, 24 Feb 2012 17:33:07 + with message-id and subject line Bug#656204: fixed in isdnutils 1:3.9.20060704+dfsg.3-4 has caused the Debian Bug report #656204, regarding libcapi20-dev: conflict when overwriting `/usr/lib/libcapi20.so` during upgrade 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 ow...@bugs.debian.org immediately.) -- 656204: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=656204 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libcapi20-dev Version: 1:3.9.20060704+dfsg.3-3 Severity: important Dear Debian folks, the fix for bug report #655884 introduced a new error when running `sudo aptitude safe-upgradey`. Vorbereitung zum Ersetzen von libcapi20-dev 1:3.9.20060704+dfsg.3-2 (durch .../libcapi20-dev_1%3a3.9.20060704+dfsg.3-3_i386.deb) ... Ersatz für libcapi20-dev wird entpackt ... dpkg: Fehler beim Bearbeiten von /var/cache/apt/archives/libcapi20-dev_1%3a3.9.20060704+dfsg.3-3_i386.deb (--unpack): Versuch, »/usr/lib/libcapi20.so« zu überschreiben, welches auch in Paket libcapi20-3 1:3.9.20060704+dfsg.3-2 ist configured to not write apport reports Vorbereitung zum Ersetzen von libcapi20-3 1:3.9.20060704+dfsg.3-2 (durch .../libcapi20-3_1%3a3.9.20060704+dfsg.3-3_i386.deb) ... Ersatz für libcapi20-3 wird entpackt ... I think some `Breaks` or `Conflicts` fields need to be set. Thanks, Paul -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: i386 (x86_64) Kernel: Linux 3.1.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages libcapi20-dev depends on: ii libcapi20-3 1:3.9.20060704+dfsg.3-3 libcapi20-dev recommends no packages. Versions of packages libcapi20-dev suggests: pn isdnutils-doc -- no debconf information signature.asc Description: This is a digitally signed message part --- End Message --- --- Begin Message --- Source: isdnutils Source-Version: 1:3.9.20060704+dfsg.3-4 We believe that the bug you reported is fixed in the latest version of isdnutils, which is due to be installed in the Debian FTP archive: capiutils_3.9.20060704+dfsg.3-4_i386.deb to main/i/isdnutils/capiutils_3.9.20060704+dfsg.3-4_i386.deb ipppd_3.9.20060704+dfsg.3-4_i386.deb to main/i/isdnutils/ipppd_3.9.20060704+dfsg.3-4_i386.deb isdnlog-data_3.9.20060704+dfsg.3-4_all.deb to main/i/isdnutils/isdnlog-data_3.9.20060704+dfsg.3-4_all.deb isdnlog_3.9.20060704+dfsg.3-4_i386.deb to main/i/isdnutils/isdnlog_3.9.20060704+dfsg.3-4_i386.deb isdnutils-base_3.9.20060704+dfsg.3-4_i386.deb to main/i/isdnutils/isdnutils-base_3.9.20060704+dfsg.3-4_i386.deb isdnutils-doc_3.9.20060704+dfsg.3-4_all.deb to main/i/isdnutils/isdnutils-doc_3.9.20060704+dfsg.3-4_all.deb isdnutils-xtools_3.9.20060704+dfsg.3-4_i386.deb to main/i/isdnutils/isdnutils-xtools_3.9.20060704+dfsg.3-4_i386.deb isdnutils_3.9.20060704+dfsg.3-4.debian.tar.gz to main/i/isdnutils/isdnutils_3.9.20060704+dfsg.3-4.debian.tar.gz isdnutils_3.9.20060704+dfsg.3-4.dsc to main/i/isdnutils/isdnutils_3.9.20060704+dfsg.3-4.dsc isdnvbox_3.9.20060704+dfsg.3-4_i386.deb to main/i/isdnutils/isdnvbox_3.9.20060704+dfsg.3-4_i386.deb isdnvboxclient_3.9.20060704+dfsg.3-4_i386.deb to main/i/isdnutils/isdnvboxclient_3.9.20060704+dfsg.3-4_i386.deb isdnvboxserver_3.9.20060704+dfsg.3-4_i386.deb to main/i/isdnutils/isdnvboxserver_3.9.20060704+dfsg.3-4_i386.deb libcapi20-3_3.9.20060704+dfsg.3-4_i386.deb to main/i/isdnutils/libcapi20-3_3.9.20060704+dfsg.3-4_i386.deb libcapi20-dev_3.9.20060704+dfsg.3-4_i386.deb to main/i/isdnutils/libcapi20-dev_3.9.20060704+dfsg.3-4_i386.deb pppdcapiplugin_3.9.20060704+dfsg.3-4_i386.deb to main/i/isdnutils/pppdcapiplugin_3.9.20060704+dfsg.3-4_i386.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 656...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Rolf Leggewie (supplier of updated isdnutils 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 ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Fri, 24 Feb 2012 23:0
Bug#648892: marked as done (TypeError: integer argument expected, got float)
Your message dated Fri, 24 Feb 2012 17:32:41 + with message-id and subject line Bug#648892: fixed in gnome-osd 0.12.2-1.1 has caused the Debian Bug report #648892, regarding TypeError: integer argument expected, got float 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 ow...@bugs.debian.org immediately.) -- 648892: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=648892 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: gnome-osd Version: 0.12.2-1 Severity: grave Appears gnome-osd is completely broken: $ gnome-osd-client 'hello' ServerError: Traceback (most recent call last): File "/usr/lib/pymodules/python2.7/gnomeosd/server.py", line 316, in message_show_cb osd_msg.show(message, timeout) File "/usr/lib/pymodules/python2.7/gnomeosd/server.py", line 127, in show self.__show_task = gtasklet.Tasklet(self._show_messages()) File "/usr/lib/pymodules/python2.7/gnomeosd/gtasklet.py", line 644, in __init__ self.__next_round() # bootstrap File "/usr/lib/pymodules/python2.7/gnomeosd/gtasklet.py", line 693, in __next_round gen_value = self.__invoke() File "/usr/lib/pymodules/python2.7/gnomeosd/gtasklet.py", line 672, in __invoke gen_value = self.gen.next() File "/usr/lib/pymodules/python2.7/gnomeosd/server.py", line 171, in _show_messages w.move(x, y_final) TypeError: integer argument expected, got float -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing'), (200, 'unstable'), (150, 'stable'), (100, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.0.0-2-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages gnome-osd depends on: ii gconf2 2.32.4-1 ii python 2.7.2-9 ii python-dbus 0.84.0-2 ii python-gnome2 2.28.1-3 ii python-gtk2 2.24.0-2 ii python-pyorbit 2.24.0-6+b1 ii python-pyorbit-omg 2.24.0-6 ii python-support 1.0.14 gnome-osd recommends no packages. Versions of packages gnome-osd suggests: ii evolution 3.0.3-2 ii muine ii pidgin 2.10.0-1+b1 ii rhythmbox 2.90.1~git20110919.2dfea6-3 ii xchat 2.8.8-3.1 -- no debconf information --- End Message --- --- Begin Message --- Source: gnome-osd Source-Version: 0.12.2-1.1 We believe that the bug you reported is fixed in the latest version of gnome-osd, which is due to be installed in the Debian FTP archive: gnome-osd_0.12.2-1.1.diff.gz to main/g/gnome-osd/gnome-osd_0.12.2-1.1.diff.gz gnome-osd_0.12.2-1.1.dsc to main/g/gnome-osd/gnome-osd_0.12.2-1.1.dsc gnome-osd_0.12.2-1.1_all.deb to main/g/gnome-osd/gnome-osd_0.12.2-1.1_all.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 648...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. gregor herrmann (supplier of updated gnome-osd 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 ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 22 Feb 2012 17:54:06 +0100 Source: gnome-osd Binary: gnome-osd Architecture: source all Version: 0.12.2-1.1 Distribution: unstable Urgency: low Maintainer: Adriaan Peeters Changed-By: gregor herrmann Description: gnome-osd - OSD message framework for GNOME Closes: 648892 Changes: gnome-osd (0.12.2-1.1) unstable; urgency=low . * Non-maintainer upload. * Fix "TypeError: integer argument expected, got float": add patch integer_division.patch from Thibaut Girka: - Fix type mismatch by using explicit integer divisions. (Closes: #648892, LP: #688138) Checksums-Sha1: 1271d4d6102a1959857e03f16faa1ec13d388c50 1956 gnome-osd_0.12.2-1.1.dsc c1262cbb081858e57fc9edba32a1a3e93f2ce80a 10960 gnome-osd_0.12.2-1.1.diff.gz 5546af6c853ba9c785c2464a8584db3f4d181ff2 84008 gnome-osd_0.12.2-1.1_all.deb Checksums-Sha256: 908a6363de2fa75b37bf4d78c3d3fc8f506876459a467bf3238ea5cb5f5e64de 1956 gnome-osd_0.12.2-1.1.dsc 3765f2204e0895dd7fbe4e217c32db62e7aa8377fc325701f51539a07fdb8db9 10960 gnome-osd_0.12.2-1.1.diff.gz e094ed0aeccd6fdc6438b48b8f849aee6a95a7a5b65fe3a19d6d9087686e46cf 84008 gnome-osd_0.12.2-1.1_all.deb Files:
Processed: retitle 432899 to rc: tab completion broken for files with special characters ...
Processing commands for cont...@bugs.debian.org:
> retitle 287828 rc: please add command completion
Bug #287828 [rc] rc doesn't have command completion
Changed Bug title to 'rc: please add command completion' from 'rc doesn't have
command completion'
> retitle 367004 rc: upstream homepage is 404
Bug #367004 [rc] rc: Upstream has gone missing
Changed Bug title to 'rc: upstream homepage is 404' from 'rc: Upstream has gone
missing'
> retitle 432899 rc: tab completion broken for files with special characters
Bug #432899 [rc] file and directory name completion doesn't work properly
Changed Bug title to 'rc: tab completion broken for files with special
characters' from 'file and directory name completion doesn't work properly'
> retitle 553835 rc: please replace libreadline5-dev build dependency with
> libreadline-dev
Bug #553835 {Done: Jakub Wilk } [rc] replacing
libreadline5-dev build dependency with libreadline-dev
Changed Bug title to 'rc: please replace libreadline5-dev build dependency with
libreadline-dev' from 'replacing libreadline5-dev build dependency with
libreadline-dev'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
553835: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=553835
367004: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=367004
432899: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=432899
287828: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=287828
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#641358: marked as done (sary-ruby FTBFS on Ubuntu)
Your message dated Fri, 24 Feb 2012 16:33:11 +
with message-id
and subject line Bug#652800: fixed in sary-ruby 1.2.0-3.1
has caused the Debian Bug report #652800,
regarding sary-ruby FTBFS on Ubuntu
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 ow...@bugs.debian.org
immediately.)
--
652800: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=652800
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sary-ruby
Version: 1.2.0-3
Severity: normal
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu oneiric ubuntu-patch
*** /tmp/tmpgerdwh
In Ubuntu, the attached patch was applied to achieve the following:
* Add patch to fix FTBFS caused by non-explicit glib-2.0 dependency.
(LP: #755960)
This does not cause FTBFS on Debian yet, but it will if/when glib-2.0 is moved
to a multi-arch setup. The patch builds and functions correctly on sid.
Thanks for considering the patch.
-- System Information:
Debian Release: wheezy/sid
APT prefers oneiric-updates
APT policy: (500, 'oneiric-updates'), (500, 'oneiric-security'), (500,
'oneiric')
Architecture: amd64 (x86_64)
Kernel: Linux 3.0.0-9-generic (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/dash
=== modified file 'debian/changelog'
=== added file 'debian/patches/00list'
--- debian/patches/00list 1970-01-01 00:00:00 +
+++ debian/patches/00list 2011-09-12 18:36:55 +
@@ -0,0 +1 @@
+50_fix_multiarch_ftbfs.dpatch
=== added file 'debian/patches/50_fix_multiarch_ftbfs.dpatch'
--- debian/patches/50_fix_multiarch_ftbfs.dpatch1970-01-01 00:00:00
+
+++ debian/patches/50_fix_multiarch_ftbfs.dpatch2011-09-12 18:35:06
+
@@ -0,0 +1,39 @@
+#!/bin/sh -e
+## 50_fix_multiarch_ftbfs.dpatch.dpatch by Clint Byrum
+##
+## All lines beginning with `## DP:' are a description of the patch.
+## DP: Fails to build because it can't find glib-2.0
+
+if [ $# -ne 1 ]; then
+echo >&2 "`basename $0`: script expects -patch|-unpatch as argument"
+exit 1
+fi
+
+[ -f debian/patches/00patch-opts ] && . debian/patches/00patch-opts
+patch_opts="${patch_opts:--f --no-backup-if-mismatch}"
+
+case "$1" in
+ -patch) patch $patch_opts -p1 < $0;;
+ -unpatch) patch $patch_opts -p1 -R < $0;;
+*)
+echo >&2 "`basename $0`: script expects -patch|-unpatch as
argument"
+exit 1;;
+esac
+
+exit 0
+
+@DPATCH@
+=== modified file 'extconf.rb'
+--- a/extconf.rb 2004-01-08 20:13:07 +
b/extconf.rb 2011-09-12 18:06:43 +
+@@ -15,7 +15,9 @@
+ ENV['PKG_CONFIG_PATH'] = '/usr/local/lib/pkgconfig/'
+ end
+
++$CFLAGS += ' ' + `#{pkg_config} glib-2.0 --cflags`.chomp
+ $CFLAGS += ' ' + `#{pkg_config} sary --cflags`.chomp
++$LDFLAGS += ' ' + `#{pkg_config} glib-2.0 --libs`.chomp
+ $LDFLAGS += ' ' + `#{pkg_config} sary --libs`.chomp
+
+ if have_header('sary.h') &&
+
--- End Message ---
--- Begin Message ---
Source: sary-ruby
Source-Version: 1.2.0-3.1
We believe that the bug you reported is fixed in the latest version of
sary-ruby, which is due to be installed in the Debian FTP archive:
libsary-ruby1.8_1.2.0-3.1_i386.deb
to main/s/sary-ruby/libsary-ruby1.8_1.2.0-3.1_i386.deb
sary-ruby_1.2.0-3.1.diff.gz
to main/s/sary-ruby/sary-ruby_1.2.0-3.1.diff.gz
sary-ruby_1.2.0-3.1.dsc
to main/s/sary-ruby/sary-ruby_1.2.0-3.1.dsc
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 652...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Ralf Treinen (supplier of updated sary-ruby 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 ftpmas...@debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Fri, 17 Feb 2012 16:30:23 +0100
Source: sary-ruby
Binary: libsary-ruby1.8
Architecture: source i386
Version: 1.2.0-3.1
Distribution: unstable
Urgency: low
Maintainer: Masahito Omote
Changed-By: Ralf Treinen
Description:
libsary-ruby1.8 - A ruby binding of sary
Closes: 641358 652800
Changes:
sary-ruby (1.2.0-3.1) unstable; urgency=low
.
* Non-maintainer upload
* add patch 50_fix_multiarch_ftbfs.dpatch to fix location of glib-2.0
that changed in the multiarch transition. Thanks a lot to Clint Byrum
for the patch! (closes: #641358, #652800)
Checksums-Sh
Bug#652800: marked as done (sary-ruby: FTBFS: make[3]: *** No rule to make target `distclean'. Stop.)
Your message dated Fri, 24 Feb 2012 16:33:11 + with message-id and subject line Bug#652800: fixed in sary-ruby 1.2.0-3.1 has caused the Debian Bug report #652800, regarding sary-ruby: FTBFS: make[3]: *** No rule to make target `distclean'. Stop. 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 ow...@bugs.debian.org immediately.) -- 652800: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=652800 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: sary-ruby Version: 1.2.0-3 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20111220 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: > make[2]: Entering directory `/build/sary-ruby-ftC0fd/sary-ruby-1.2.0' > --- Cleaning > dh_testdir > dh_testroot > rm -f build-stamp configure-stamp > [ ! -f Makefile ] || /usr/bin/make distclean > make[3]: *** No rule to make target `distclean'. Stop. > make[3]: Entering directory `/build/sary-ruby-ftC0fd/sary-ruby-1.2.0' > make[3]: Leaving directory `/build/sary-ruby-ftC0fd/sary-ruby-1.2.0' > make[2]: *** [clean1] Error 2 The full build log is available from: http://people.debian.org/~lucas/logs/2011/12/20/sary-ruby_1.2.0-3_lsid64.buildlog A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems. --- End Message --- --- Begin Message --- Source: sary-ruby Source-Version: 1.2.0-3.1 We believe that the bug you reported is fixed in the latest version of sary-ruby, which is due to be installed in the Debian FTP archive: libsary-ruby1.8_1.2.0-3.1_i386.deb to main/s/sary-ruby/libsary-ruby1.8_1.2.0-3.1_i386.deb sary-ruby_1.2.0-3.1.diff.gz to main/s/sary-ruby/sary-ruby_1.2.0-3.1.diff.gz sary-ruby_1.2.0-3.1.dsc to main/s/sary-ruby/sary-ruby_1.2.0-3.1.dsc A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 652...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ralf Treinen (supplier of updated sary-ruby 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 ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Fri, 17 Feb 2012 16:30:23 +0100 Source: sary-ruby Binary: libsary-ruby1.8 Architecture: source i386 Version: 1.2.0-3.1 Distribution: unstable Urgency: low Maintainer: Masahito Omote Changed-By: Ralf Treinen Description: libsary-ruby1.8 - A ruby binding of sary Closes: 641358 652800 Changes: sary-ruby (1.2.0-3.1) unstable; urgency=low . * Non-maintainer upload * add patch 50_fix_multiarch_ftbfs.dpatch to fix location of glib-2.0 that changed in the multiarch transition. Thanks a lot to Clint Byrum for the patch! (closes: #641358, #652800) Checksums-Sha1: 839f9df2c80ec3ef5c4059c4fd0dfebeb90b079b 1093 sary-ruby_1.2.0-3.1.dsc 7dca9b3279fc4efc9be845595d229a80b8066086 27261 sary-ruby_1.2.0-3.1.diff.gz 7b65246f810e2bf5932cb7e2a787009021628e55 14844 libsary-ruby1.8_1.2.0-3.1_i386.deb Checksums-Sha256: 509dd5a504da4df7b155a483935c20fc34dc0fc56da7ad8b9c160cdcf966daf0 1093 sary-ruby_1.2.0-3.1.dsc 52db70d43d4fd8839063e610174b9a14f50d077c31dc275fc8bee8dd50f9e612 27261 sary-ruby_1.2.0-3.1.diff.gz 75fe59f82ace5bc7fdf9ccfa8b91bbfb0b0383127b558ac54377538e16178555 14844 libsary-ruby1.8_1.2.0-3.1_i386.deb Files: 76db63dd4629383c1b7e5dfe9a36a004 1093 ruby optional sary-ruby_1.2.0-3.1.dsc 4fbeb1e3605ee4fdc12c18083b91d7c6 27261 ruby optional sary-ruby_1.2.0-3.1.diff.gz 95ef558490c498c576ddcdf561b6bc57 14844 ruby optional libsary-ruby1.8_1.2.0-3.1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iEYEARECAAYFAk8+d4MACgkQtzWmSeC6BMEaZQCgjc5MWjHvD8HEFe/yU7fGi3iD x+gAoJxh0Pc9vSDuXJxTxaRJ+q38NYjG =uOOt -END PGP SIGNATURE- --- End Message ---
Bug#641358: marked as done (sary-ruby FTBFS on Ubuntu)
Your message dated Fri, 24 Feb 2012 16:33:11 +
with message-id
and subject line Bug#641358: fixed in sary-ruby 1.2.0-3.1
has caused the Debian Bug report #641358,
regarding sary-ruby FTBFS on Ubuntu
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 ow...@bugs.debian.org
immediately.)
--
641358: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=641358
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sary-ruby
Version: 1.2.0-3
Severity: normal
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu oneiric ubuntu-patch
*** /tmp/tmpgerdwh
In Ubuntu, the attached patch was applied to achieve the following:
* Add patch to fix FTBFS caused by non-explicit glib-2.0 dependency.
(LP: #755960)
This does not cause FTBFS on Debian yet, but it will if/when glib-2.0 is moved
to a multi-arch setup. The patch builds and functions correctly on sid.
Thanks for considering the patch.
-- System Information:
Debian Release: wheezy/sid
APT prefers oneiric-updates
APT policy: (500, 'oneiric-updates'), (500, 'oneiric-security'), (500,
'oneiric')
Architecture: amd64 (x86_64)
Kernel: Linux 3.0.0-9-generic (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/dash
=== modified file 'debian/changelog'
=== added file 'debian/patches/00list'
--- debian/patches/00list 1970-01-01 00:00:00 +
+++ debian/patches/00list 2011-09-12 18:36:55 +
@@ -0,0 +1 @@
+50_fix_multiarch_ftbfs.dpatch
=== added file 'debian/patches/50_fix_multiarch_ftbfs.dpatch'
--- debian/patches/50_fix_multiarch_ftbfs.dpatch1970-01-01 00:00:00
+
+++ debian/patches/50_fix_multiarch_ftbfs.dpatch2011-09-12 18:35:06
+
@@ -0,0 +1,39 @@
+#!/bin/sh -e
+## 50_fix_multiarch_ftbfs.dpatch.dpatch by Clint Byrum
+##
+## All lines beginning with `## DP:' are a description of the patch.
+## DP: Fails to build because it can't find glib-2.0
+
+if [ $# -ne 1 ]; then
+echo >&2 "`basename $0`: script expects -patch|-unpatch as argument"
+exit 1
+fi
+
+[ -f debian/patches/00patch-opts ] && . debian/patches/00patch-opts
+patch_opts="${patch_opts:--f --no-backup-if-mismatch}"
+
+case "$1" in
+ -patch) patch $patch_opts -p1 < $0;;
+ -unpatch) patch $patch_opts -p1 -R < $0;;
+*)
+echo >&2 "`basename $0`: script expects -patch|-unpatch as
argument"
+exit 1;;
+esac
+
+exit 0
+
+@DPATCH@
+=== modified file 'extconf.rb'
+--- a/extconf.rb 2004-01-08 20:13:07 +
b/extconf.rb 2011-09-12 18:06:43 +
+@@ -15,7 +15,9 @@
+ ENV['PKG_CONFIG_PATH'] = '/usr/local/lib/pkgconfig/'
+ end
+
++$CFLAGS += ' ' + `#{pkg_config} glib-2.0 --cflags`.chomp
+ $CFLAGS += ' ' + `#{pkg_config} sary --cflags`.chomp
++$LDFLAGS += ' ' + `#{pkg_config} glib-2.0 --libs`.chomp
+ $LDFLAGS += ' ' + `#{pkg_config} sary --libs`.chomp
+
+ if have_header('sary.h') &&
+
--- End Message ---
--- Begin Message ---
Source: sary-ruby
Source-Version: 1.2.0-3.1
We believe that the bug you reported is fixed in the latest version of
sary-ruby, which is due to be installed in the Debian FTP archive:
libsary-ruby1.8_1.2.0-3.1_i386.deb
to main/s/sary-ruby/libsary-ruby1.8_1.2.0-3.1_i386.deb
sary-ruby_1.2.0-3.1.diff.gz
to main/s/sary-ruby/sary-ruby_1.2.0-3.1.diff.gz
sary-ruby_1.2.0-3.1.dsc
to main/s/sary-ruby/sary-ruby_1.2.0-3.1.dsc
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 641...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Ralf Treinen (supplier of updated sary-ruby 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 ftpmas...@debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Fri, 17 Feb 2012 16:30:23 +0100
Source: sary-ruby
Binary: libsary-ruby1.8
Architecture: source i386
Version: 1.2.0-3.1
Distribution: unstable
Urgency: low
Maintainer: Masahito Omote
Changed-By: Ralf Treinen
Description:
libsary-ruby1.8 - A ruby binding of sary
Closes: 641358 652800
Changes:
sary-ruby (1.2.0-3.1) unstable; urgency=low
.
* Non-maintainer upload
* add patch 50_fix_multiarch_ftbfs.dpatch to fix location of glib-2.0
that changed in the multiarch transition. Thanks a lot to Clint Byrum
for the patch! (closes: #641358, #652800)
Checksums-Sh
Bug#652800: marked as done (sary-ruby: FTBFS: make[3]: *** No rule to make target `distclean'. Stop.)
Your message dated Fri, 24 Feb 2012 16:33:11 + with message-id and subject line Bug#641358: fixed in sary-ruby 1.2.0-3.1 has caused the Debian Bug report #641358, regarding sary-ruby: FTBFS: make[3]: *** No rule to make target `distclean'. Stop. 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 ow...@bugs.debian.org immediately.) -- 641358: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=641358 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: sary-ruby Version: 1.2.0-3 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20111220 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: > make[2]: Entering directory `/build/sary-ruby-ftC0fd/sary-ruby-1.2.0' > --- Cleaning > dh_testdir > dh_testroot > rm -f build-stamp configure-stamp > [ ! -f Makefile ] || /usr/bin/make distclean > make[3]: *** No rule to make target `distclean'. Stop. > make[3]: Entering directory `/build/sary-ruby-ftC0fd/sary-ruby-1.2.0' > make[3]: Leaving directory `/build/sary-ruby-ftC0fd/sary-ruby-1.2.0' > make[2]: *** [clean1] Error 2 The full build log is available from: http://people.debian.org/~lucas/logs/2011/12/20/sary-ruby_1.2.0-3_lsid64.buildlog A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems. --- End Message --- --- Begin Message --- Source: sary-ruby Source-Version: 1.2.0-3.1 We believe that the bug you reported is fixed in the latest version of sary-ruby, which is due to be installed in the Debian FTP archive: libsary-ruby1.8_1.2.0-3.1_i386.deb to main/s/sary-ruby/libsary-ruby1.8_1.2.0-3.1_i386.deb sary-ruby_1.2.0-3.1.diff.gz to main/s/sary-ruby/sary-ruby_1.2.0-3.1.diff.gz sary-ruby_1.2.0-3.1.dsc to main/s/sary-ruby/sary-ruby_1.2.0-3.1.dsc A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 641...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ralf Treinen (supplier of updated sary-ruby 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 ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Fri, 17 Feb 2012 16:30:23 +0100 Source: sary-ruby Binary: libsary-ruby1.8 Architecture: source i386 Version: 1.2.0-3.1 Distribution: unstable Urgency: low Maintainer: Masahito Omote Changed-By: Ralf Treinen Description: libsary-ruby1.8 - A ruby binding of sary Closes: 641358 652800 Changes: sary-ruby (1.2.0-3.1) unstable; urgency=low . * Non-maintainer upload * add patch 50_fix_multiarch_ftbfs.dpatch to fix location of glib-2.0 that changed in the multiarch transition. Thanks a lot to Clint Byrum for the patch! (closes: #641358, #652800) Checksums-Sha1: 839f9df2c80ec3ef5c4059c4fd0dfebeb90b079b 1093 sary-ruby_1.2.0-3.1.dsc 7dca9b3279fc4efc9be845595d229a80b8066086 27261 sary-ruby_1.2.0-3.1.diff.gz 7b65246f810e2bf5932cb7e2a787009021628e55 14844 libsary-ruby1.8_1.2.0-3.1_i386.deb Checksums-Sha256: 509dd5a504da4df7b155a483935c20fc34dc0fc56da7ad8b9c160cdcf966daf0 1093 sary-ruby_1.2.0-3.1.dsc 52db70d43d4fd8839063e610174b9a14f50d077c31dc275fc8bee8dd50f9e612 27261 sary-ruby_1.2.0-3.1.diff.gz 75fe59f82ace5bc7fdf9ccfa8b91bbfb0b0383127b558ac54377538e16178555 14844 libsary-ruby1.8_1.2.0-3.1_i386.deb Files: 76db63dd4629383c1b7e5dfe9a36a004 1093 ruby optional sary-ruby_1.2.0-3.1.dsc 4fbeb1e3605ee4fdc12c18083b91d7c6 27261 ruby optional sary-ruby_1.2.0-3.1.diff.gz 95ef558490c498c576ddcdf561b6bc57 14844 ruby optional libsary-ruby1.8_1.2.0-3.1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iEYEARECAAYFAk8+d4MACgkQtzWmSeC6BMEaZQCgjc5MWjHvD8HEFe/yU7fGi3iD x+gAoJxh0Pc9vSDuXJxTxaRJ+q38NYjG =uOOt -END PGP SIGNATURE- --- End Message ---
Processed: severity of 643084 is serious
Processing commands for cont...@bugs.debian.org: > # Automatically generated email from bts, devscripts version 2.10.35lenny7 > severity 643084 serious Bug #643084 [src:cutter-testing-framework] cutter-testing-framework: FTBFS: dpkg-buildpackage: error: dpkg-source -b cutter-testing-framework-1.1.7 gave error exit status 2 Severity set to 'serious' from 'important' > End of message, stopping processing here. Please contact me if you need assistance. -- 643084: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=643084 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#661161: dh-apparmor: is not co-installable with current debhelper
Package: dh-apparmor Severity: grave Version: 2.7.0-1 Hi, Package: dh-apparmor Replaces: debhelper (<< 9.20120115ubuntu2) Breaks: debhelper (<< 9.20120115ubuntu2) Given current sid has debhelper 9.20120115, this makes dh-apparmor not co-installable with it. As a result, dh-apparmor is not usable in current sid, is it? If I'm not mistaken, this blocks me from suggesting Debian maintainers to ship AppArmor profiles with their packages. I don't understand why these relationships are here in the first place. It seems to me a conflict that could arise would be with a future version of debhelper that would ship the postinst-apparmor and postrm-apparmor autoscripts, rather than with older (i.e. current or past) versions. If this were to happen, I think debhelper itself would have to Replaces: and Breaks: dh-apparmor, not the contrary. Am I confused? (As a side note, it's not clear to me what's the point of this package at all. I see Ubuntu ships dh-apparmor support as part of their debhelper package. Has this support ever been submitted to the debhelper upstream / Debian maintainer, did they refuse to ship it? Actually, I find the split package approach a bit cleaner, but reducing the Debian / Ubuntu delta seems important too :) Cheers, -- intrigeri | GnuPG key @ https://gaffer.ptitcanardnoir.org/intrigeri/intrigeri.asc | OTR fingerprint @ https://gaffer.ptitcanardnoir.org/intrigeri/otr.asc | Who wants a world in which the guarantee that we shall not | die of starvation would entail the risk of dying of boredom ? -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#661092: marked as done (mcrl2 and libowfat-dev: error when trying to install together)
Your message dated Fri, 24 Feb 2012 15:47:35 + with message-id and subject line Bug#661092: fixed in mcrl2 201202.0-2 has caused the Debian Bug report #661092, regarding mcrl2 and libowfat-dev: error when trying to install together 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 ow...@bugs.debian.org immediately.) -- 661092: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=661092 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libowfat-dev,mcrl2 Version: libowfat-dev/0.28-5 Version: mcrl2/201202.0-1 Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite Date: 2012-02-24 Architecture: amd64 Distribution: sid Hi, automatic installation tests of packages that share a file and at the same time do not conflict by their package dependency relationships has detected the following problem: WARNING: The following packages cannot be authenticated! libkeyutils1 libkrb5support0 libk5crypto3 libkrb5-3 libgssapi-krb5-2 libpcre3 libffi5 libglib2.0-0 libatk1.0-data libatk1.0-0 libavahi-common-data libavahi-common3 libdbus-1-3 libavahi-client3 libcups2 libdatrie1 libdrm2 libexpat1 libfreetype6 ucf ttf-dejavu-core fontconfig-config libfontconfig1 libjpeg8 libjasper1 libpng12-0 libtiff4 libxau6 libxdmcp6 libxcb1 libx11-data libx11-6 libgdk-pixbuf2.0-common libgdk-pixbuf2.0-0 libglapi-mesa libxfixes3 libxdamage1 libxext6 libxxf86vm1 libgl1-mesa-glx libglu1-mesa libgtk2.0-common libpixman-1-0 libxcb-render0 libxcb-shm0 libxrender1 libcairo2 libthai-data libthai0 libxft2 fontconfig libpango1.0-0 libxcomposite1 libxcursor1 libxi6 libxinerama1 libxrandr2 libxml2 shared-mime-info libgtk2.0-0 x11-common libice6 libsm6 libwxbase2.8-0 libwxgtk2.8-0 libicu48 libboost-regex1.48.0 libboost-signals1.48.0 libc-dev-bin linux-libc-dev libc6-dev libgl2ps0 libowfat0 libowfat-dev mcrl2 Extracting templates from packages: 40% Extracting templates from packages: 80% Extracting templates from packages: 100% Preconfiguring packages ... Authentication warning overridden. Can not write log, openpty() failed (/dev/pts not mounted?) Selecting previously unselected package libkeyutils1. (Reading database ... 10552 files and directories currently installed.) Unpacking libkeyutils1 (from .../libkeyutils1_1.5.2-2_amd64.deb) ... Selecting previously unselected package libkrb5support0. Unpacking libkrb5support0 (from .../libkrb5support0_1.10+dfsg~beta1-2_amd64.deb) ... Selecting previously unselected package libk5crypto3. Unpacking libk5crypto3 (from .../libk5crypto3_1.10+dfsg~beta1-2_amd64.deb) ... Selecting previously unselected package libkrb5-3. Unpacking libkrb5-3 (from .../libkrb5-3_1.10+dfsg~beta1-2_amd64.deb) ... Selecting previously unselected package libgssapi-krb5-2. Unpacking libgssapi-krb5-2 (from .../libgssapi-krb5-2_1.10+dfsg~beta1-2_amd64.deb) ... Selecting previously unselected package libpcre3. Unpacking libpcre3 (from .../libpcre3_8.12-4_amd64.deb) ... Selecting previously unselected package libffi5. Unpacking libffi5 (from .../libffi5_3.0.10-3_amd64.deb) ... Selecting previously unselected package libglib2.0-0. Unpacking libglib2.0-0 (from .../libglib2.0-0_2.30.2-6_amd64.deb) ... Selecting previously unselected package libatk1.0-data. Unpacking libatk1.0-data (from .../libatk1.0-data_2.2.0-2_all.deb) ... Selecting previously unselected package libatk1.0-0. Unpacking libatk1.0-0 (from .../libatk1.0-0_2.2.0-2_amd64.deb) ... Selecting previously unselected package libavahi-common-data. Unpacking libavahi-common-data (from .../libavahi-common-data_0.6.30-6_amd64.deb) ... Selecting previously unselected package libavahi-common3. Unpacking libavahi-common3 (from .../libavahi-common3_0.6.30-6_amd64.deb) ... Selecting previously unselected package libdbus-1-3. Unpacking libdbus-1-3 (from .../libdbus-1-3_1.4.18-1_amd64.deb) ... Selecting previously unselected package libavahi-client3. Unpacking libavahi-client3 (from .../libavahi-client3_0.6.30-6_amd64.deb) ... Selecting previously unselected package libcups2. Unpacking libcups2 (from .../libcups2_1.5.2-5_amd64.deb) ... Selecting previously unselected package libdatrie1. Unpacking libdatrie1 (from .../libdatrie1_0.2.5-3_amd64.deb) ... Selecting previously unselected package libdrm2. Unpacking libdrm2 (from .../libdrm2_2.4.30-1_amd64.deb) ... Selecting previously unselected package libexpat1. Unpacking libexpat1 (from .../libexpat1_2.0.1-7.2_amd64.deb) ... Selecting previously unselected package libfreetype6. Unpacking libfreetype6 (from .../libfreetype6_2.4.8-1_amd64.deb) ... Selecting previously unselected package ucf. Unpacking ucf (from .../uc
Bug#661150: dropbear: CVE-2012-0920 SSH server use-after-free vulnerability]
Source: dropbear Severity: grave Tags: security patch Hey, below is a forwarded report describing a vulnerability in dropbear. Cheers Nico - Forwarded message from Danny Fullerton - Dropbear SSH server use-after-free vulnerability Impact: A remote authenticated user can execute arbitrary code on the target system. Class: Use After Free - CWE-416 CVE ID: CVE-2012-0920 CVSS: 8.5 (AV:N/AC:M/AU:S/C:C/I:C/A:C) Description: This vulnerability is located within the Dropbear daemon and occurs due to the way the server manages channels concurrency. A specially crafted request can trigger a `use after free` condition which can be used to execute arbitrary code under root privileges provided the user has been authenticated using a public key (authorized_keys file) and a command restriction is enforced (command option). Solution: Upgrade to version 2012.55 or higher. Reference: https://secure.ucc.asn.au/hg/dropbear/rev/818108bf7749 Disclosure Timeline: 2012-01-24 - Vulnerability reported to vendor. 2012-02-24 - Coordinated public release of advisory. Credit: This vulnerability was discovered by Danny Fullerton from Mantor Organization. Special thanks to Matt. - End forwarded message - -- Nico Golde - http://www.ngolde.de - n...@jabber.ccc.de - GPG: 0xA0A0 For security reasons, all text in this mail is double-rot13 encrypted. pgpmyvB9rRsPk.pgp Description: PGP signature
Processed: retitle 659899 to CVE-2012-0790: XSS
Processing commands for cont...@bugs.debian.org:
> retitle 659899 CVE-2012-0790: XSS
Bug #659899 {Done: Antoine Beaupré } [smokeping]
CVE-2011-0790: XSS
Changed Bug title to 'CVE-2012-0790: XSS' from 'CVE-2011-0790: XSS'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
659899: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=659899
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#659899: CVE-2011-0790: XSS
Hi, * Moritz Muehlenhoff [2012-02-14 18:11]: > This has been assigned CVE-2011-0790: Just to make sure there is no confusion, this should've been CVE-2012-0790. Cheers Nico pgpsedVHOKbzT.pgp Description: PGP signature
Processed: Re: Bug#657410: libcheese-dev: fails to upgrade from squeeze - trying to overwrite ...
Processing commands for cont...@bugs.debian.org: > tag 657410 + patch Bug #657410 [libcheese-dev] libcheese-dev: fails to upgrade from squeeze - trying to overwrite ... Added tag(s) patch. > affects 657942 + src:cheese Bug #657942 [frei0r-plugins] frei0r-plugins: Cannot install Added indication that 657942 affects src:cheese > thanks Stopping processing here. Please contact me if you need assistance. -- 657942: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=657942 657410: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=657410 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#657410: libcheese-dev: fails to upgrade from squeeze - trying to overwrite ...
tag 657410 + patch
affects 657942 + src:cheese
thanks
On Thu, 26 Jan 2012 04:29:07 +0100, Andreas Beckmann wrote:
> >>From the attached log (scroll to the bottom...):
>
> Selecting previously unselected package libcheese-dev.
> Unpacking libcheese-dev (from .../libcheese-dev_3.2.2-1+b1_amd64.deb) ...
> dpkg: error processing
> /var/cache/apt/archives/libcheese-dev_3.2.2-1+b1_amd64.deb (--unpack):
>trying to overwrite '/usr/include/cheese/cheese-camera-device-monitor.h',
> which is also in package libcheese-gtk-dev 2.30.1-2
The attached patch should fix the problem; unfortunately cheese
doesn't build right now:
The following packages have unmet dependencies:
frei0r-plugins: Depends: libcv2.1 which is a virtual package.
Depends: libcvaux2.1 which is a virtual package.
Depends: libgavl1 (>= 1.1.0) but it is not going to be
installed.
Depends: libhighgui2.1 which is a virtual package.
Unable to resolve dependencies! Giving up...
(#657942)
Cheers,
gregor
--
.''`. Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06
: :' : Debian GNU/Linux user, admin, and developer - http://www.debian.org/
`. `' Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
`- NP: Neal Casal: Too Much To Ask
diff -Nru cheese-3.2.2/debian/changelog cheese-3.2.2/debian/changelog
--- cheese-3.2.2/debian/changelog 2011-11-15 20:28:15.0 +0100
+++ cheese-3.2.2/debian/changelog 2012-02-24 14:43:59.0 +0100
@@ -1,3 +1,12 @@
+cheese (3.2.2-1.1) UNRELEASED; urgency=low
+
+ * Non-maintainer upload.
+ * Fix "fails to upgrade from squeeze - trying to overwrite ...":
+add Breaks/Replaces against old libcheese-gtk-dev to libcheese-dev.
+(Closes: #657410)
+
+ -- gregor herrmann Fri, 24 Feb 2012 14:39:37 +0100
+
cheese (3.2.2-1) unstable; urgency=low
* New upstream release.
diff -Nru cheese-3.2.2/debian/control cheese-3.2.2/debian/control
--- cheese-3.2.2/debian/control 2011-11-15 20:37:59.0 +0100
+++ cheese-3.2.2/debian/control 2012-02-24 14:44:10.0 +0100
@@ -142,6 +142,8 @@
libgstreamer-plugins-base0.10-dev (>= 0.10.32),
libgdk-pixbuf2.0-dev,
${misc:Depends}
+Breaks: libcheese-gtk-dev (<< 3.0.1-1)
+Replaces: libcheese-gtk-dev (<< 3.0.1-1)
Description: tool to take pictures and videos from your webcam - base dev
A webcam application that supports image and video capture. Makes
it easy to take photos and videos of you, your friends, pets or whatever
diff -Nru cheese-3.2.2/debian/control.in cheese-3.2.2/debian/control.in
--- cheese-3.2.2/debian/control.in 2011-11-15 19:30:28.0 +0100
+++ cheese-3.2.2/debian/control.in 2012-02-24 14:39:29.0 +0100
@@ -137,6 +137,8 @@
libgstreamer-plugins-base0.10-dev (>= 0.10.32),
libgdk-pixbuf2.0-dev,
${misc:Depends}
+Breaks: libcheese-gtk-dev (<< 3.0.1-1)
+Replaces: libcheese-gtk-dev (<< 3.0.1-1)
Description: tool to take pictures and videos from your webcam - base dev
A webcam application that supports image and video capture. Makes
it easy to take photos and videos of you, your friends, pets or whatever
signature.asc
Description: Digital signature
Bug#659899: CVE-2011-0790: XSS
On Tue, 14 Feb 2012 14:39:05 -0500, Antoine Beaupré wrote: > Here's a debdiff to fix this issue. I can upload this to stable-security > if it is okay for you guys. > > I had to fiddle a bit with the patch to make it fit with 2.3, but I > think it will work. Not sure it is *complete* however, the way 2.3 > treats some arguments is different than 2.6, so it may have more > vulnerabilities that could be discovered with a more thorough audit. > > Also note that I cannot actually test this patch as do not run the 2.3 > release in production - too old! Besides, the wheezy package runs fine > in squeeze, I don't even need to backport... Anything up with this? A. -- We should act only in such away that if everyone else acted as we do, we would accept the results. - Kant pgpAKY1LI4P88.pgp Description: PGP signature
Bug#659994: [regression] icedove: symbol lookup error: [...]/libdbusservice.so: undefined symbol: NS_Alloc
Hi, Am 21.02.2012 19:46, schrieb Christoph Goehre: On Mi, Feb 15, 2012 at 05:34:45 +0100, Ansgar Burchardt wrote: since the last security update for icedove, the program does not start on several computers here. Instead the following error message is displayed: /usr/lib/icedove/icedove-bin: symbol lookup error: /usr/lib/icedove/components/libdbusservice.so: undefined symbol: NS_Alloc I could reproduce it, but I need to move my .icedove profile away. If I downgrade to libc6 version 2.11.2-10, everything is working fine. So here my steps to reproduce: 1) add deb http://snapshot.debian.org/archive/debian/20111215/ squeeze main to /etc/apt/sources.list and run 'apt-get update' 2) install older libc6 apt-get install libc-bin=2.11.2-10 libc-dev-bin=2.11.2-10 libc6=2.11.2-10 libc6-dev=2.11.2-10 libc6-i386=2.11.2-10 locales=2.11.2-10 3) rerun Icedove Same here: icedove starts with the older version of libc6, but not with version 2.11.3-3. The same is true when also downgrading icedove to 3.0.11-1+squeeze6 (works with old libc6, not with newer libc6). I can also upgrade libc6 to 2.11.3-3 and icedove continues working, but if I also change the version of icedove (by either upgrading or downgrading), icedove again refuses to start. So this seems to be something triggered by running icedove after an update. Regards, Ansgar -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#661145: psmisc: killall can't find processes with long names
Package: psmisc Version: 22.15-2 Severity: critical Justification: breaks unrelated software The killall command in psmisc 22.15-2 is broken: it can't find processes with long names. The version in 22.13-1 works fine. I first saw this on a VM cluster which uses pacemaker and DLM. Pacemaker's DLM scripts run 'killall -0 dlm_controld.pcmk' which fails to find the process. Pidof and pgrep work fine. This is easily reproducible on any system with consolekit installed: tarquin ~ # pidof console-kit-daemon 4851 tarquin ~ # pgrep console-kit 4851 tarquin ~ # killall -0 console-kit-daemon console-kit-daemon: no process found Cheers, Chris -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages psmisc depends on: ii libc6 2.13-26 ii libtinfo5 5.9-4 psmisc recommends no packages. psmisc suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#661092: mcrl2 and libowfat-dev: error when trying to install together
On 02/24/2012 12:33 PM, Jakub Wilk wrote: > * Ralf Treinen , 2012-02-24, 05:53: >> /usr/include/scan.h > > I sincerely hope it'll be renamed in both packages. It's way too generic. Well, agreed. (Paul?) Thanks, Roland -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#661092: mcrl2 and libowfat-dev: error when trying to install together
Hey, On Fri, Feb 24, 2012 at 09:57:17AM +0100, Roland Stigge wrote: > On 02/24/2012 05:53 AM, Ralf Treinen wrote: > > Here is a list of files that are known to be shared by both packages > > (according to the Contents file for sid/amd64, which may be > > slightly out of sync): > > > > /usr/include/scan.h > > Considering that libowfat-dev has this file for quite a while now [...] > we can prevent both packages conflicting with each other or both > needing to move the file to somewhere else. > > (mcrl2 would need to change anyway in one way or another, in all cases.) > > Please tell me if there are good reasons to adjust libowfat-dev also. There is not. I don't know what happened, but there should be no header files installed just under /usr/include, they should all have been in /usr/include/mcrl2. I overlooked them while inspecting the package before upload. We will investigate what happened and upload a fixed version soon. Paul -- Using the Power of Debian GNU/Linux | E-mail: pau...@debian.org Jabber/GTalk: p...@luon.net | GnuPG key ID: 0x50064181 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: tag 661092 wheezy sid
Processing commands for cont...@bugs.debian.org: > # Neither libowfat-dev nor mcrl2 contain /usr/include/scan.h in squeeze, so > ... > tag 661092 wheezy sid Bug #661092 [libowfat-dev,mcrl2] mcrl2 and libowfat-dev: error when trying to install together Added tag(s) sid and wheezy. > -- Stopping processing here. Please contact me if you need assistance. -- 661092: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=661092 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#657478: marked as done (biomaj-watcher: doesn't use invoke-rc.d)
Your message dated Fri, 24 Feb 2012 12:32:22 + with message-id and subject line Bug#657478: fixed in biomaj-watcher 1.2.0-4 has caused the Debian Bug report #657478, regarding biomaj-watcher: doesn't use invoke-rc.d 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 ow...@bugs.debian.org immediately.) -- 657478: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=657478 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: biomaj-watcher Version: 1.2.0-3 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package starts processes where it shouldnt. This is very probably due to not using invoke-rc.d as mandated by policy 9.3.3.2. This is seriously disturbing! ;-) See http://www.debian.org/doc/debian-policy/ch-opersys.html#s9.3.3 and /usr/share/doc/sysv-rc/README.invoke-rc.d.gz as well as /usr/share/doc/sysv-rc/README.policy-rc.d.gz >From the attached log (scroll to the bottom...): Selecting previously unselected package biomaj-watcher. (Reading database ... 13418 files and directories currently installed.) Unpacking biomaj-watcher (from .../biomaj-watcher_1.2.0-3_all.deb) ... Setting up biomaj-watcher (1.2.0-3) ... /var/lib/dpkg/info/biomaj-watcher.config: 18: [: =: unexpected operator Updating Context.xml... Configuration complete Starting Tomcat servlet engine: tomcat6. This should not have happened - policy-rc.d would have prevented starting tomcat. Therefore processes are left around: 1m12.2s DEBUG: Starting command: ['lsof', '-w', '+D', '/tmp/piupartss/tmpdlJbX8'] 1m12.5s DUMP: COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME java10661 messagebus cwdDIR 0,19 180 22705197 /tmp/piupartss/tmpdlJbX8/var/lib/tomcat6 java10661 messagebus rtdDIR 0,19 440 22646097 /tmp/piupartss/tmpdlJbX8 java10661 messagebus txtREG 0,1936048 22697509 /tmp/piupartss/tmpdlJbX8/usr/lib/jvm/java-6-openjdk-amd64/jre/bin/java ... Also note the error in the config script, use if [ "$RET" = "true" ] ^^ to fix this. cheers, Andreas biomaj-watcher_1.2.0-3.log.gz Description: GNU Zip compressed data --- End Message --- --- Begin Message --- Source: biomaj-watcher Source-Version: 1.2.0-4 We believe that the bug you reported is fixed in the latest version of biomaj-watcher, which is due to be installed in the Debian FTP archive: biomaj-watcher_1.2.0-4.debian.tar.gz to contrib/b/biomaj-watcher/biomaj-watcher_1.2.0-4.debian.tar.gz biomaj-watcher_1.2.0-4.dsc to contrib/b/biomaj-watcher/biomaj-watcher_1.2.0-4.dsc biomaj-watcher_1.2.0-4_all.deb to contrib/b/biomaj-watcher/biomaj-watcher_1.2.0-4_all.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 657...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Olivier Sallou (supplier of updated biomaj-watcher 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 ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 16 Dec 2011 15:53:41 +0100 Source: biomaj-watcher Binary: biomaj-watcher Architecture: source all Version: 1.2.0-4 Distribution: unstable Urgency: low Maintainer: Debian Med Packaging Team Changed-By: Olivier Sallou Description: biomaj-watcher - biological data-bank updater - web interface Closes: 653825 657478 658175 658225 658266 658412 658455 658828 659164 659171 659911 659945 659997 Changes: biomaj-watcher (1.2.0-4) unstable; urgency=low . [debian-l10n-english] * Debconf templates and debian/control reviewed by the debian-l10n- english team as part of the Smith review project. Closes: #653825 [Debconf translation updates] * Polish (Michał Kułach). Closes: #658175 * Indonesian (Mahyuddin Susanto). Closes: #658225 * Russian (Yuri Kozlov). Closes: #658266 * Czech (Michal Simunek). Closes: #658412 * Dutch; (Jeroen Schot). Closes: #658455 * French (Olivier Sallou). Closes: #658828 * Danish (Joe Hansen). Closes: #659164 * German (Chris Leick). Closes: #659171 * Portuguese (Miguel Figueiredo). Closes: #659911 * Spanish; (Camaleón). Closes: #659945 * Italian (Beatrice Torracca). Closes: #659997 [Olivier Sallou] * postinst: use invoke-rc.d instead of service to
Processed: Re: libstdc++6 4.6.1-4 breaks libstdc++6-4.4-dev 4.4.5-8 but doesn't "conflict" with it
Processing commands for cont...@bugs.debian.org: > # breaks partial upgrades (policy §3.5) > severity 651550 serious Bug #651550 [libstdc++6] libstdc++6 4.6.1-4 breaks libstdc++6-4.4-dev 4.4.5-8 but doesn't "conflict" with it Severity set to 'serious' from 'normal' > tags 651550 + patch Bug #651550 [libstdc++6] libstdc++6 4.6.1-4 breaks libstdc++6-4.4-dev 4.4.5-8 but doesn't "conflict" with it Added tag(s) patch. > quit Stopping processing here. Please contact me if you need assistance. -- 651550: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=651550 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#661092: mcrl2 and libowfat-dev: error when trying to install together
* Ralf Treinen , 2012-02-24, 05:53: /usr/include/scan.h I sincerely hope it'll be renamed in both packages. It's way too generic. -- Jakub Wilk -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: notfound 661088 in 0.29-1, found 661088 in 29:0.29-1
Processing commands for cont...@bugs.debian.org:
> # Correct version information:
> notfound 661088 0.29-1
Bug #661088 {Done: Mark Brown } [src:intercal] intercal:
FTBFS: rm: cannot remove `debian/intercal/usr/share/info/dir': ENOENT
The source intercal and version do not appear to match any binary packages
Bug No longer marked as found in versions intercal/0.29-1.
> found 661088 29:0.29-1
Bug #661088 {Done: Mark Brown } [src:intercal] intercal:
FTBFS: rm: cannot remove `debian/intercal/usr/share/info/dir': ENOENT
Bug Marked as found in versions intercal/29:0.29-1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
661088: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=661088
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#661064: marked as done (movabletype-opensource: Multiple security issues)
Your message dated Fri, 24 Feb 2012 11:17:58 + with message-id and subject line Bug#661064: fixed in movabletype-opensource 5.1.3+dfsg-1 has caused the Debian Bug report #661064, regarding movabletype-opensource: Multiple security issues 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 ow...@bugs.debian.org immediately.) -- 661064: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=661064 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: movabletype-opensource Version: 5.1.2+dfsg-3 Severity: grave Justification: security http://www.movabletype.org/2012/02/movable_type_513_507_and_438_security_updates.html "5.13, 5.07, and 4.38 address the multiple vulnerabilities including: - OS Command Injection exists in the file management system, the most serious of which may lead to arbitrary OS command execution by a user who has a permission to sign-in to the admin script and also has a permission to upload files. - Session Hijack and CSRF exist in the commenting and the community script. A remote attacker could hijack the user session or could execute arbitrary script code on victim's browser under the certain circumstances. - XSS exists in templates where the variables are not escaped properly. A remote attacker could inject client-side script into web pages viewed by other users. - XSS exists in mt-wizard.cgi. This vulnerability was reported by Trustwave (TWSL2012-003) " -- Dominic Hargreaves | http://www.larted.org.uk/~dom/ PGP key 5178E2A5 from the.earth.li (keyserver,web,email) --- End Message --- --- Begin Message --- Source: movabletype-opensource Source-Version: 5.1.3+dfsg-1 We believe that the bug you reported is fixed in the latest version of movabletype-opensource, which is due to be installed in the Debian FTP archive: movabletype-opensource_5.1.3+dfsg-1.debian.tar.gz to main/m/movabletype-opensource/movabletype-opensource_5.1.3+dfsg-1.debian.tar.gz movabletype-opensource_5.1.3+dfsg-1.dsc to main/m/movabletype-opensource/movabletype-opensource_5.1.3+dfsg-1.dsc movabletype-opensource_5.1.3+dfsg-1_all.deb to main/m/movabletype-opensource/movabletype-opensource_5.1.3+dfsg-1_all.deb movabletype-opensource_5.1.3+dfsg.orig.tar.gz to main/m/movabletype-opensource/movabletype-opensource_5.1.3+dfsg.orig.tar.gz movabletype-plugin-core_5.1.3+dfsg-1_all.deb to main/m/movabletype-opensource/movabletype-plugin-core_5.1.3+dfsg-1_all.deb movabletype-plugin-zemanta_5.1.3+dfsg-1_all.deb to main/m/movabletype-opensource/movabletype-plugin-zemanta_5.1.3+dfsg-1_all.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 661...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Dominic Hargreaves (supplier of updated movabletype-opensource 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 ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Fri, 24 Feb 2012 11:07:02 + Source: movabletype-opensource Binary: movabletype-opensource movabletype-plugin-core movabletype-plugin-zemanta Architecture: source all Version: 5.1.3+dfsg-1 Distribution: unstable Urgency: high Maintainer: Dominic Hargreaves Changed-By: Dominic Hargreaves Description: movabletype-opensource - Well-known blogging engine movabletype-plugin-core - Core Movable Type plugins movabletype-plugin-zemanta - Zemanta Movable Type plugin Closes: 661064 Changes: movabletype-opensource (5.1.3+dfsg-1) unstable; urgency=high . * New upstream release - fixes multiple security vulnerabilities (closes: #661064) Checksums-Sha1: 5c6585d8f17bcbced5c3595a31ebf3b7f34871ce 1575 movabletype-opensource_5.1.3+dfsg-1.dsc f9d0751da9cd4b089994a55f1f7c22cbf595680e 6153596 movabletype-opensource_5.1.3+dfsg.orig.tar.gz fa1a8debbf1042414948afd401b4141b4dd0f3f2 30184 movabletype-opensource_5.1.3+dfsg-1.debian.tar.gz d308d27fbe544834c79ea8fc347307b29a6cc550 4031490 movabletype-opensource_5.1.3+dfsg-1_all.deb 42cd24c0a40bca5d6943be97c267431f53636556 170366 movabletype-plugin-core_5.1.3+dfsg-1_all.deb 9df456968c7d98bf952cc8a9855f37041c1398df 16318 movabletype-plugin-zemanta_5.1.3+dfsg-1_all.deb Checksums-Sha256: 16094ab4abc21737851f3b914f21152b3f5ea2d8e29a0bb13e81156e0cb6bee8 1575 movabletype-opensource_5.1.3+dfsg-1.dsc 73e8a03eb19d3e0bc9fbe8776501b93e7c1f94
Bug#661122: FTBFS
Package: cqrlog Version: 1.2.2-2 Severity: serious Your package fails to build from source: Compiling synaser.pas 100 150.481/164.032 Kb Used 200 150.516/164.032 Kb Used 300 150.572/164.032 Kb Used 400 150.653/164.032 Kb Used 500 150.721/164.032 Kb Used 600 150.780/164.032 Kb Used 700 150.799/164.032 Kb Used 800 151.071/164.032 Kb Used 900 151.332/164.288 Kb Used 1000 151.511/164.288 Kb Used 1100 151.811/164.288 Kb Used 1200 152.044/164.288 Kb Used 1300 152.255/164.288 Kb Used 1400 152.704/164.288 Kb Used 1500 152.811/164.288 Kb Used 1600 152.995/164.288 Kb Used 1700 153.110/164.288 Kb Used 1800 153.201/164.288 Kb Used 1900 153.311/164.288 Kb Used synaser.pas(1902,58) Error: Incompatible types: got "ShortInt" expected "Pointer" 2000 153.330/164.288 Kb Used 2100 153.337/164.288 Kb Used 2200 153.361/164.288 Kb Used synaser.pas(2278,41) Warning: range check error while evaluating constants synaser.pas(2299) Fatal: There were 1 errors compiling module, stopping ERROR: failed compiling of project /root/cqrlog-1.2.2/src/cqrlog.lpi make[1]: *** [cqrlog] Error 2 make[1]: Leaving directory `/root/cqrlog-1.2.2' dh_auto_build: make -j1 returned exit code 2 make: *** [build] Error 2 dpkg-buildpackage: error: debian/rules build gave error exit status 2 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#611661: Advertencia final de cuentas de usuario
Advertencia final de cuentas de usuario Su buzón ha superado una o más limitaciones tamaño determinado por el administrador. El tamaño del buzón es 78944 KB. los límites de tamaño de buzón: 7 KB Esta es una advertencia de que sus mailboxletters alcanzó 70.000 KB.Il puede no ser capaz de enviar o recibir mensajes nuevos untilreduce tamaño de su buzón. Para disponer de más espacio, usted debe haga clic en y complete el formulario y haga clic en enviar para ayudar a aumentar el tamaño del buzón de correo. http://bg-r.webs.com/contact.htm Después de 48 horas sin recibir ninguna respuesta de usted Debemos destruir su dirección de e-mail Informe del sistema de servidores -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#661099: fpc depends on packages that can't be installed
Can you please clarify more the situation? You are using Squeeze or a mix of Squeeze and other repositories? What are the dependencies that are missing? Aptitude will give you the full dependency tree, can you please provide this? Cheers, signature.asc Description: This is a digitally signed message part
Bug#661092: mcrl2 and libowfat-dev: error when trying to install together
Hi, On 02/24/2012 05:53 AM, Ralf Treinen wrote: > Here is a list of files that are known to be shared by both packages > (according to the Contents file for sid/amd64, which may be > slightly out of sync): > > /usr/include/scan.h Considering that libowfat-dev has this file for quite a while now in its API (mcrl2 introduced it just in 201202.0-1) and users are used to have the API in this place, I would kindly ask for mcrl2 moving this file to somewhere else so we can prevent both packages conflicting with each other or both needing to move the file to somewhere else. (mcrl2 would need to change anyway in one way or another, in all cases.) Please tell me if there are good reasons to adjust libowfat-dev also. Thanks in advance, Roland -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#661088: marked as done (intercal: FTBFS: rm: cannot remove `debian/intercal/usr/share/info/dir': ENOENT)
Your message dated Fri, 24 Feb 2012 08:49:01 + with message-id and subject line Bug#661088: fixed in intercal 29:0.29-2 has caused the Debian Bug report #661088, regarding intercal: FTBFS: rm: cannot remove `debian/intercal/usr/share/info/dir': ENOENT 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 ow...@bugs.debian.org immediately.) -- 661088: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=661088 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: intercal Version: 0.29-1 Severity: serious Justification: fails to build from source (but built successfully in the past) Hi, I think you want an rm -f there. Build log attached. Cheers -- System Information: Debian Release: wheezy/sid APT prefers unreleased APT policy: (500, 'unreleased'), (500, 'unstable') Architecture: m68k Kernel: Linux 3.2.0-1-atari Locale: LANG=C, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/mksh-static I: Using pkgname logfile I: Current time: Fri Feb 24 00:26:44 UTC 2012 I: pbuilder-time-stamp: 1330043204 I: Obtaining the cached apt archive contents I: Installing the build-deps W: no hooks of type D found -- ignoring -> Attempting to parse the build-deps -> Considering build-dep debhelper (>= 5) -> Trying debhelper -> Considering build-dep bison -> Trying bison -> Considering build-dep flex -> Trying flex -> Considering build-dep groff -> Trying groff -> Considering build-dep tidy -> Trying tidy -> Considering build-dep texinfo -> Trying texinfo -> Installing debhelper bison flex groff tidy texinfo Reading package lists... Building dependency tree... Reading state information... Starting Starting 2 Done debhelper is already the newest version. The following extra packages will be installed: libbison-dev libice6 libsm6 libtidy-0.99-0 libx11-6 libx11-data libxau6 libxaw7 libxcb1 libxdmcp6 libxext6 libxmu6 libxpm4 libxt6 m4 x11-common Suggested packages: bison-doc texlive-base texlive-latex-base texlive-generic-recommended texinfo-doc-nonfree tidy-doc Recommended packages: ghostscript imagemagick libpaper1 netpbm psutils The following NEW packages will be installed: bison flex groff libbison-dev libice6 libsm6 libtidy-0.99-0 libx11-6 libx11-data libxau6 libxaw7 libxcb1 libxdmcp6 libxext6 libxmu6 libxpm4 libxt6 m4 texinfo tidy x11-common 0 upgraded, 21 newly installed, 0 to remove and 0 not upgraded. Need to get 3557 kB/7913 kB of archives. After this operation, 21.8 MB of additional disk space will be used. Get:1 http://ftp.debian-ports.org/debian/ unstable/main groff m68k 1.21-6 [3531 kB] Get:2 http://ftp.debian-ports.org/debian/ unstable/main tidy m68k 20091223cvs-1.2 [26.9 kB] debconf: delaying package configuration, since apt-utils is not installed Fetched 3557 kB in 25s (141 kB/s) Selecting previously unselected package m4. (Reading database ... 11921 files and directories currently installed.) Unpacking m4 (from .../archives/m4_1.4.16-2_m68k.deb) ... Selecting previously unselected package flex. Unpacking flex (from .../flex_2.5.35-10_m68k.deb) ... Selecting previously unselected package x11-common. Unpacking x11-common (from .../x11-common_1%3a7.6+11_all.deb) ... Selecting previously unselected package libice6. Unpacking libice6 (from .../libice6_2%3a1.0.5-1_m68k.deb) ... Selecting previously unselected package libsm6. Unpacking libsm6 (from .../libsm6_2%3a1.1.0-2_m68k.deb) ... Selecting previously unselected package libxau6. Unpacking libxau6 (from .../libxau6_1%3a1.0.4-2_m68k.deb) ... Selecting previously unselected package libxdmcp6. Unpacking libxdmcp6 (from .../libxdmcp6_1%3a1.0.2-3_m68k.deb) ... Selecting previously unselected package libxcb1. Unpacking libxcb1 (from .../libxcb1_1.6-1~m68k.1_m68k.deb) ... Selecting previously unselected package libx11-data. Unpacking libx11-data (from .../libx11-data_2%3a1.3.3-4_all.deb) ... Selecting previously unselected package libx11-6. Unpacking libx11-6 (from .../libx11-6_2%3a1.2.2-1_m68k.deb) ... Processing triggers for man-db ... Setting up x11-common (1:7.6+11) ... Selecting previously unselected package libxt6. (Reading database ... 12343 files and directories currently installed.) Unpacking libxt6 (from .../libxt6_1%3a1.0.5-3_m68k.deb) ... Selecting previously unselected package texinfo. Unpacking texinfo (from .../texinfo_4.13a.dfsg.1-8_m68k.deb) ... Selecting previously unselected package libbison-dev. Unpacking libbison-dev (from .../libbison-dev_1%3a2.5.dfsg-2.1_m68k.deb) ... Selecting previously unselected package bison. Unpacking bison (from .../bison_1%3a2.5.dfsg-2.1_m68k.deb) ... Selecting previously unsel
Bug#661000: marked as done (undefined symbol: nomgc)
Your message dated Fri, 24 Feb 2012 09:12:55 +0100 with message-id <4f474687.9010...@progress-technologies.net> and subject line Re: Bug#661000: undefined symbol: nomgc has caused the Debian Bug report #661000, regarding undefined symbol: nomgc 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 ow...@bugs.debian.org immediately.) -- 661000: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=661000 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: file Version: 5.10-1 Severity: grave Hi, file command does not work at all: $ file / file: symbol lookup error: /usr/lib/libmagic.so.1: undefined symbol: nomgc --- End Message --- --- Begin Message --- closing then. -- Address:Daniel Baumann, Donnerbuehlweg 3, CH-3012 Bern Email: daniel.baum...@progress-technologies.net Internet: http://people.progress-technologies.net/~daniel.baumann/ --- End Message ---
