Bug#733457: marked as done (Security bug in Sablotron XSL processor)
Your message dated Mon, 30 Dec 2013 10:03:47 +0200
with message-id 20131230080347.GA1688@sid.nuvreauspam
and subject line Re: Bug#733457: Security bug in Sablotron XSL processor
has caused the Debian Bug report #733457,
regarding Security bug in Sablotron XSL processor
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.)
--
733457: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=733457
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: sablotron
Version: 1.0.3-1
Severity: Critical
Sablotron uses unmapped memory to parse argument objects. If an attacker
can map this area of memory, they may be able to cause the application to
act in an unintended way. I did not research the possibility of code
execution.
In https://github.com/lindes/sablotron/blob/master/src/engine/expr.cpp,
starting on line 3094, the code fails to check the presence of arguments in
the substring-before and substring-after functions.
Program received signal SIGSEGV, Segmentation fault.
0x77b79316 in Expression::tostring(Situation, Str) ()
from /home/daybreak/sablorelease/src/engine/.libs/libsablot.so.0
PoC is attached.
?xml version=1.0 encoding=UTF-8?
xsl:stylesheet version=1.0 xmlns:xsl=http://www.w3.org/1999/XSL/Transform; $
xsl:template match=/
xsl:call-template name=urlResolver
xsl:with-param name=input select=hello /
/xsl:call-template
/xsl:template
xsl:template name=urlResolver
xsl:param name=input /
xsl:variable name=testVar select=substring-before('CRASH')/
/xsl:template
/xsl:stylesheet
---End Message---
---BeginMessage---
On Sb, 28 dec 13, 18:21:20, johnvillamil2010 . wrote:
Package: sablotron
Version: 1.0.3-1
This package is not in Debian, please report this bug to where you
obtained the package from.
Thanks,
Andrei
--
http://wiki.debian.org/FAQsFromDebianUser
Offtopic discussions among Debian users and developers:
http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic
http://nuvreauspam.ro/gpg-transition.txt
signature.asc
Description: Digital signature
---End Message---
Bug#733596: libgnomeui-0: Package depends on libgnome-2-0, makes uninstallable
Package: libgnomeui-0 Version: 2.24.5-3 Severity: serious Justification: unkown Dear Maintainer, The dependency to libgnome-2-0 makes the package uninstallable, which breaks other packages (such as virt-manager). Best regards Jonas -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.12-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages libgnomeui-0 depends on: ii libart-2.0-22.3.21-2 ii libatk1.0-0 2.10.0-2 ii libbonobo2-02.32.1-3 ii libbonoboui2-0 2.24.5-2 ii libc6 2.17-97 ii libcairo2 1.12.16-2 ii libfontconfig1 2.11.0-2 ii libfreetype62.5.2-1 ii libgconf2-4 3.2.6-1 ii libgdk-pixbuf2.0-0 2.28.2-1+b1 ii libglade2-0 1:2.6.4-2 ii libglib2.0-02.38.1-2 ii libgnome-keyring0 3.8.0-2 ii libgnome2-0 2.32.1-4 ii libgnomecanvas2-0 2.30.3-2 ii libgnomeui-common 2.24.5-3 ii libgnomevfs2-0 1:2.24.4-4 ii libgtk2.0-0 2.24.22-1 ii libice6 2:1.0.8-2 ii liborbit2 1:2.14.19-0.3 ii libpango1.0-0 1.36.0-1+b1 ii libpopt01.16-8 ii libsm6 2:1.2.1-2 ii libx11-62:1.6.2-1 ii libxml2 2.9.1+dfsg1-3 libgnomeui-0 recommends no packages. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#733591: cpl-plugin-sinfo and sinfo: error when trying to install together
Control: reassign -1 cpl-plugin-sinfo I'll change this in cpl-plugin-sinfo. Best Ole -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: cpl-plugin-sinfo and sinfo: error when trying to install together
Processing control commands: reassign -1 cpl-plugin-sinfo Bug #733591 [sinfo,cpl-plugin-sinfo] cpl-plugin-sinfo and sinfo: error when trying to install together Bug reassigned from package 'sinfo,cpl-plugin-sinfo' to 'cpl-plugin-sinfo'. Ignoring request to alter found versions of bug #733591 to the same values previously set Ignoring request to alter fixed versions of bug #733591 to the same values previously set -- 733591: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=733591 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#733568: libtxc-dxtn-s2tc0: uninstallable on i386
Package: s2tc Followup-For: Bug #733568 User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu trusty ubuntu-patch Hi Lennart, As this is a serious regression introduced in your latest upload which makes the package uninstallable on all architectures other than amd64, I've taken the liberty of preparing an NMU for this issue. The short diff to the Debian packaging is attached. I'm not sure how this regression happened, since the debian/rules handling of the updates seems to be correct, but please take care to correct this in your local environment before the next upload. Changelog entry for the NMU is: * Non-maintainer upload. * Fix maintainer scripts to not hard-code the library path for one specific architecture into the alternatives handling on all architectures. Closes: #733568. I will be uploading the NMU directly to unstable shortly, and have also committed the change to the collab-maint repo. Thanks for considering the patch. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developerhttp://www.debian.org/ slanga...@ubuntu.com vor...@debian.org === modified file 'debian/libtxc-dxtn-s2tc0.postinst' --- debian/libtxc-dxtn-s2tc0.postinst 2013-12-29 15:01:19 + +++ debian/libtxc-dxtn-s2tc0.postinst 2013-12-30 07:46:02 + @@ -2,7 +2,7 @@ set -e update-alternatives --install \ - /usr/lib/x86_64-linux-gnu/libtxc_dxtn.so libtxc-dxtn-x86_64-linux-gnu /usr/lib/x86_64-linux-gnu/libtxc_dxtn_s2tc.so.0 10 + /usr/lib/#MULTIARCH#/libtxc_dxtn.so libtxc-dxtn-#MULTIARCH# /usr/lib/#MULTIARCH#/libtxc_dxtn_s2tc.so.0 10 #DEBHELPER# === modified file 'debian/libtxc-dxtn-s2tc0.prerm' --- debian/libtxc-dxtn-s2tc0.prerm 2013-12-29 15:01:19 + +++ debian/libtxc-dxtn-s2tc0.prerm 2013-12-30 07:46:12 + @@ -2,7 +2,7 @@ set -e update-alternatives --remove \ - libtxc-dxtn-x86_64-linux-gnu /usr/lib/x86_64-linux-gnu/libtxc_dxtn_s2tc.so.0 + libtxc-dxtn-#MULTIARCH# /usr/lib/#MULTIARCH#/libtxc_dxtn_s2tc.so.0 #DEBHELPER#
Bug#705565: Getting closure compiler back in testing?
On 30/12/13 00:48, Rogério Brito wrote: Hi there. Can we have a late Christmas present (or even an New Year's present)? The closure compiler: * has already been removed from testing [1] * has many applications and users that depend/want it * already has patches in the BTS [2] [1]: http://packages.qa.debian.org/c/closure-compiler/news/20131229T163915Z.html [2]: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=705565 Given this information, could we have something (even a NMU) to fix this? Tony made some commits in Git and it appears he is working to resolve this The rename of the binary package from libclosure-compiler-java - closure-compiler should probably be done now as well to get this out of the way well before the Jessie release. I've made the changes for a rename on a branch called pkgrename and pushed that into Git Tony, are you making another upload shortly, would you like to merge pkgrename perhaps? -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#726410: marked as done (spandsp: FTBFS in parallel mode)
Your message dated Mon, 30 Dec 2013 09:22:23 + with message-id e1vxz3h-0006yk...@franck.debian.org and subject line Bug#726410: fixed in spandsp 0.0.6~pre21-2 has caused the Debian Bug report #726410, regarding spandsp: FTBFS in parallel mode 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.) -- 726410: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=726410 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: spandsp Version: 0.0.6~pre21-1 Severity: serious From my pbuilder build log: ... ./generate_sized_pages ./generate_sized_pages ./generate_sized_pages tiffcp R1200_1200_A4.tif R1200_1200_B4.tif R1200_1200_A3.tif R600_1200_A4.tif R600_1200_B4.tif R600_1200_A3.tif R600_600_A4.tif R600_600_B4.tif R600_600_A3.tif R16_800_A4.tif R16_800_B4.tif R16_800_A3.tif R16_154_A4.tif R16_154_B4.tif R16_154_A3.tif R300_600_A4.tif R300_600_B4.tif R300_600_A3.tif R300_300_A4.tif R300_300_B4.tif R300_300_A3.tif R8_154_A4.tif R8_154_B4.tif R8_154_A3.tif R8_77_A4.tif R8_77_B4.tif R8_77_A3.tif R8_385_A4.tif R8_385_B4.tif R8_385_A3.tif mixed_size_pages.tif R8_154_A4.tif: Not a TIFF or MDI file, bad magic number 23 (0x17). make[5]: *** [mixed_size_pages.tif] Error 253 make[5]: Leaving directory `/tmp/buildd/spandsp-0.0.6~pre21/test-data/itu/fax' make[4]: *** [all-recursive] Error 1 make[4]: Leaving directory `/tmp/buildd/spandsp-0.0.6~pre21/test-data/itu' make[3]: *** [all-recursive] Error 1 make[3]: Leaving directory `/tmp/buildd/spandsp-0.0.6~pre21/test-data' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/tmp/buildd/spandsp-0.0.6~pre21' dh_auto_build: make -j8 returned exit code 2 make[1]: *** [override_dh_auto_build] Error 2 make[1]: Leaving directory `/tmp/buildd/spandsp-0.0.6~pre21' make: *** [build] Error 2 dpkg-buildpackage: error: debian/rules build gave error exit status 2 The exact error I get seems to be variable. In another case, when I ran the build, I got this instead: ... ./generate_sized_pages ./generate_sized_pages ./generate_sized_pages tiffcp R1200_1200_A4.tif R1200_1200_B4.tif R1200_1200_A3.tif R600_1200_A4.tif R600_1200_B4.tif R600_1200_A3.tif R600_600_A4.tif R600_600_B4.tif R600_600_A3.tif R16_800_A4.tif R16_800_B4.tif R16_800_A3.tif R16_154_A4.tif R16_154_B4.tif R16_154_A3.tif R300_600_A4.tif R300_600_B4.tif R300_600_A3.tif R300_300_A4.tif R300_300_B4.tif R300_300_A3.tif R8_154_A4.tif R8_154_B4.tif R8_154_A3.tif R8_77_A4.tif R8_77_B4.tif R8_77_A3.tif R8_385_A4.tif R8_385_B4.tif R8_385_A3.tif mixed_size_pages.tif Fax3Decode1D: Warning, Premature EOL at line 1247 of strip 0 (got 3, expected 1728). Fax3Decode1D: Warning, Line length mismatch at line 1248 of strip 0 (got 1856, expected 1728). Fax3Decode1D: Warning, Premature EOL at line 1249 of strip 0 (got 0, expected 1728). Fax3Decode1D: Warning, Premature EOL at line 1250 of strip 0 (got 4, expected 1728). Fax3Decode1D: Warning, Line length mismatch at line 1251 of strip 0 (got 1805, expected 1728). Fax3Decode1D: Warning, Premature EOL at line 1252 of strip 0 (got 0, expected 1728). Fax3Decode1D: Warning, Premature EOL at line 1253 of strip 0 (got 140, expected 1728). Fax3Decode1D: Warning, Premature EOL at line 1254 of strip 0 (got 54, expected 1728). Fax3Decode1D: Warning, Premature EOL at line 1255 of strip 0 (got 0, expected 1728). Fax3Decode1D: Warning, Premature EOL at line 1256 of strip 0 (got 0, expected 1728). Fax3Decode1D: Warning, Premature EOL at line 1257 of strip 0 (got 34, expected 1728). Fax3Decode1D: Warning, Premature EOL at line 1258 of strip 0 (got 0, expected 1728). Fax3Decode1D: Warning, Premature EOL at line 1259 of strip 0 (got 3, expected 1728). Fax3Decode1D: Warning, Premature EOL at line 1260 of strip 0 (got 39, expected 1728). Fax3Decode1D: Warning, Premature EOL at line 1261 of strip 0 (got 0, expected 1728). Fax3Decode1D: Warning, Premature EOL at line 1262 of strip 0 (got 42, expected 1728). Fax3Decode1D: Warning, Premature EOL at line 1263 of strip 0 (got 0, expected 1728). Fax3Decode1D: Warning, Premature EOL at line 1264 of strip 0 (got 0, expected 1728). Fax3Decode1D: Warning, Line length mismatch at line 1265 of strip 0 (got 1803, expected 1728). Fax3Decode1D: Warning, Premature EOL at line 1266 of strip 0 (got 20, expected 1728). Fax3Decode1D: Warning, Premature EOL at line 1267 of strip 0 (got 1673, expected 1728). Fax3Decode1D: Warning, Premature EOL at line 1268 of strip 0 (got 44, expected 1728). Fax3Decode1D: Warning, Premature EOL at line 1269 of strip 0 (got 0, expected 1728). Fax3Decode1D: Warning, Premature EOL at line 1270 of
Bug#733568: marked as done (libtxc-dxtn-s2tc0: uninstallable on i386)
Your message dated Mon, 30 Dec 2013 09:21:55 + with message-id e1vxz2p-0006ml...@franck.debian.org and subject line Bug#733568: fixed in s2tc 0~git20131104-1.1 has caused the Debian Bug report #733568, regarding libtxc-dxtn-s2tc0: uninstallable on i386 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.) -- 733568: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=733568 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: libtxc-dxtn-s2tc0 Version: 0~git20131104-1 Severity: important Dear Maintainer, upgrading or installing the package is impossible on i386 because x86_64 is hardcoded in the postinst script: LANG=c sudo dpkg -i /var/cache/apt/archives/libtxc-dxtn-s2tc0_0~git20131104-1_i386.deb (Reading database ... 287234 files and directories currently installed.) Preparing to unpack .../libtxc-dxtn-s2tc0_0~git20131104-1_i386.deb ... Unpacking libtxc-dxtn-s2tc0:i386 (0~git20131104-1) over (0~git20131104-1) ... Setting up libtxc-dxtn-s2tc0:i386 (0~git20131104-1) ... update-alternatives: error: alternative path /usr/lib/x86_64-linux-gnu/libtxc_dxtn_s2tc.so.0 doesn't exist dpkg: error processing package libtxc-dxtn-s2tc0:i386 (--install): subprocess installed post-installation script returned error exit status 2 Errors were encountered while processing: libtxc-dxtn-s2tc0:i386 -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (x86_64) Kernel: Linux 3.12-trunk-amd64 (SMP w/2 CPU cores) Locale: LANG=fr_BE.utf8, LC_CTYPE=fr_BE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages libtxc-dxtn-s2tc0 depends on: ii libc6 2.17-97 ii libgcc11:4.8.2-10 ii libstdc++6 4.8.2-10 ii multiarch-support 2.17-97 libtxc-dxtn-s2tc0 recommends no packages. libtxc-dxtn-s2tc0 suggests no packages. -- no debconf information ---End Message--- ---BeginMessage--- Source: s2tc Source-Version: 0~git20131104-1.1 We believe that the bug you reported is fixed in the latest version of s2tc, which is due to be installed in the Debian FTP archive. 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 733...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Steve Langasek vor...@debian.org (supplier of updated s2tc 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...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 30 Dec 2013 07:46:49 + Source: s2tc Binary: libtxc-dxtn-s2tc0 libtxc-dxtn-s2tc-bin libtxc-dxtn-s2tc-dev Architecture: source amd64 Version: 0~git20131104-1.1 Distribution: unstable Urgency: medium Maintainer: Lennart Weller l...@ring0.de Changed-By: Steve Langasek vor...@debian.org Description: libtxc-dxtn-s2tc-bin - S2TC texture compression and conversion tools libtxc-dxtn-s2tc-dev - Development files for the S2TC library libtxc-dxtn-s2tc0 - Texture compression library for Mesa Closes: 733568 Changes: s2tc (0~git20131104-1.1) unstable; urgency=medium . * Non-maintainer upload. * Fix maintainer scripts to not hard-code the library path for one specific architecture into the alternatives handling on all architectures. Closes: #733568. Checksums-Sha1: aa3dab1feebaa9c1028a381ca4cb9736c7356c0a 2087 s2tc_0~git20131104-1.1.dsc 7646f96f371c91432565cf6948664f6e1d0b05e1 4273 s2tc_0~git20131104-1.1.debian.tar.gz f7f6a1972a027b2ba4a3f4634a4c3fcacffbc9e2 51618 libtxc-dxtn-s2tc0_0~git20131104-1.1_amd64.deb ee385ec8ecfd7d949d23fea81ef7283554d67a72 12596 libtxc-dxtn-s2tc-bin_0~git20131104-1.1_amd64.deb 6ceabe739c5c7a4a0a5fc03396e63623ff51931e 3348 libtxc-dxtn-s2tc-dev_0~git20131104-1.1_amd64.deb Checksums-Sha256: ef6452f69326ce1eb552b7721fa9e30f443eaba0102772cbf3f79d1c80a2f1ef 2087 s2tc_0~git20131104-1.1.dsc b42a114823014f0e3f2c1769f5701f400dd2be3ce0bd0a1dc52421fc0e4c9b55 4273 s2tc_0~git20131104-1.1.debian.tar.gz cb1902e8163f699cf19c2a8e362e1d09a3aa8871319ff08d9f6ffd5209685530 51618 libtxc-dxtn-s2tc0_0~git20131104-1.1_amd64.deb 0e7a24b3986f48c90ea975a4d5755d898d8605f68301df265815f6c206309020 12596 libtxc-dxtn-s2tc-bin_0~git20131104-1.1_amd64.deb 6fcc1f8c7ed5caa5bfb87bb1a98832936a2fb9eb754f76d6ae10c598c90e4b6d 3348
Bug#733575: marked as done (libtxc-dxtn-s2tc0: uninstallable on != amd64)
Your message dated Mon, 30 Dec 2013 09:21:55 + with message-id e1vxz2p-0006ml...@franck.debian.org and subject line Bug#733568: fixed in s2tc 0~git20131104-1.1 has caused the Debian Bug report #733568, regarding libtxc-dxtn-s2tc0: uninstallable on != amd64 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 733568: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=733568 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: libtxc-dxtn-s2tc0 Version: 0~git20131104-1 Severity: important Setting up libtxc-dxtn-s2tc0:armhf (0~git20131104-1) ... update-alternatives: error: alternative path /usr/lib/x86_64-linux-gnu/libtxc_dxtn_s2tc.so.0 doesn't exist dpkg: error processing package libtxc-dxtn-s2tc0:armhf (--configure): subprocess installed post-installation script returned error exit status 2 That path being missing is not quite surprising on architectures other than amd64... -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (120, 'experimental') Architecture: armhf (armv7l) Kernel: Linux 3.0.42 (PREEMPT) 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 libtxc-dxtn-s2tc0 depends on: ii libc6 2.17-97 ii libgcc11:4.8.2-10 ii libstdc++6 4.8.2-10 ii multiarch-support 2.17-97 libtxc-dxtn-s2tc0 recommends no packages. libtxc-dxtn-s2tc0 suggests no packages. -- no debconf information ---End Message--- ---BeginMessage--- Source: s2tc Source-Version: 0~git20131104-1.1 We believe that the bug you reported is fixed in the latest version of s2tc, which is due to be installed in the Debian FTP archive. 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 733...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Steve Langasek vor...@debian.org (supplier of updated s2tc 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...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 30 Dec 2013 07:46:49 + Source: s2tc Binary: libtxc-dxtn-s2tc0 libtxc-dxtn-s2tc-bin libtxc-dxtn-s2tc-dev Architecture: source amd64 Version: 0~git20131104-1.1 Distribution: unstable Urgency: medium Maintainer: Lennart Weller l...@ring0.de Changed-By: Steve Langasek vor...@debian.org Description: libtxc-dxtn-s2tc-bin - S2TC texture compression and conversion tools libtxc-dxtn-s2tc-dev - Development files for the S2TC library libtxc-dxtn-s2tc0 - Texture compression library for Mesa Closes: 733568 Changes: s2tc (0~git20131104-1.1) unstable; urgency=medium . * Non-maintainer upload. * Fix maintainer scripts to not hard-code the library path for one specific architecture into the alternatives handling on all architectures. Closes: #733568. Checksums-Sha1: aa3dab1feebaa9c1028a381ca4cb9736c7356c0a 2087 s2tc_0~git20131104-1.1.dsc 7646f96f371c91432565cf6948664f6e1d0b05e1 4273 s2tc_0~git20131104-1.1.debian.tar.gz f7f6a1972a027b2ba4a3f4634a4c3fcacffbc9e2 51618 libtxc-dxtn-s2tc0_0~git20131104-1.1_amd64.deb ee385ec8ecfd7d949d23fea81ef7283554d67a72 12596 libtxc-dxtn-s2tc-bin_0~git20131104-1.1_amd64.deb 6ceabe739c5c7a4a0a5fc03396e63623ff51931e 3348 libtxc-dxtn-s2tc-dev_0~git20131104-1.1_amd64.deb Checksums-Sha256: ef6452f69326ce1eb552b7721fa9e30f443eaba0102772cbf3f79d1c80a2f1ef 2087 s2tc_0~git20131104-1.1.dsc b42a114823014f0e3f2c1769f5701f400dd2be3ce0bd0a1dc52421fc0e4c9b55 4273 s2tc_0~git20131104-1.1.debian.tar.gz cb1902e8163f699cf19c2a8e362e1d09a3aa8871319ff08d9f6ffd5209685530 51618 libtxc-dxtn-s2tc0_0~git20131104-1.1_amd64.deb 0e7a24b3986f48c90ea975a4d5755d898d8605f68301df265815f6c206309020 12596 libtxc-dxtn-s2tc-bin_0~git20131104-1.1_amd64.deb 6fcc1f8c7ed5caa5bfb87bb1a98832936a2fb9eb754f76d6ae10c598c90e4b6d 3348 libtxc-dxtn-s2tc-dev_0~git20131104-1.1_amd64.deb Files: c9ea338ad1fae3dd082c31837e395bbd 2087 libs extra s2tc_0~git20131104-1.1.dsc fc663791a4e56ae5e2b50dfc3503291f 4273 libs extra s2tc_0~git20131104-1.1.debian.tar.gz 9bf1c915763281df8d0aefe61b089c2a 51618 libs extra libtxc-dxtn-s2tc0_0~git20131104-1.1_amd64.deb 09ed6eee3c206ef5bd59ce8b8f88ade4 12596 misc extra libtxc-dxtn-s2tc-bin_0~git20131104-1.1_amd64.deb
Bug#733589: marked as done (libopenscap8 and libopenscap3: error when trying to install together)
Your message dated Mon, 30 Dec 2013 09:21:11 + with message-id e1vxz27-0005xi...@franck.debian.org and subject line Bug#733589: fixed in openscap 1.0.1-2 has caused the Debian Bug report #733589, regarding libopenscap8 and libopenscap3: 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.) -- 733589: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=733589 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: libopenscap3,libopenscap8 Version: libopenscap3/0.9.12-1 Version: libopenscap8/1.0.1-1 Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite Date: 2013-12-30 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: Selecting previously unselected package libkeyutils1:amd64. (Reading database ... 10868 files and directories currently installed.) Preparing to unpack .../libkeyutils1_1.5.6-1_amd64.deb ... Unpacking libkeyutils1:amd64 (1.5.6-1) ... Selecting previously unselected package libkrb5support0:amd64. Preparing to unpack .../libkrb5support0_1.11.3+dfsg-3+nmu1_amd64.deb ... Unpacking libkrb5support0:amd64 (1.11.3+dfsg-3+nmu1) ... Selecting previously unselected package libk5crypto3:amd64. Preparing to unpack .../libk5crypto3_1.11.3+dfsg-3+nmu1_amd64.deb ... Unpacking libk5crypto3:amd64 (1.11.3+dfsg-3+nmu1) ... Selecting previously unselected package libkrb5-3:amd64. Preparing to unpack .../libkrb5-3_1.11.3+dfsg-3+nmu1_amd64.deb ... Unpacking libkrb5-3:amd64 (1.11.3+dfsg-3+nmu1) ... Selecting previously unselected package libgssapi-krb5-2:amd64. Preparing to unpack .../libgssapi-krb5-2_1.11.3+dfsg-3+nmu1_amd64.deb ... Unpacking libgssapi-krb5-2:amd64 (1.11.3+dfsg-3+nmu1) ... Selecting previously unselected package libsasl2-modules-db:amd64. Preparing to unpack .../libsasl2-modules-db_2.1.25.dfsg1-17_amd64.deb ... Unpacking libsasl2-modules-db:amd64 (2.1.25.dfsg1-17) ... Selecting previously unselected package libsasl2-2:amd64. Preparing to unpack .../libsasl2-2_2.1.25.dfsg1-17_amd64.deb ... Unpacking libsasl2-2:amd64 (2.1.25.dfsg1-17) ... Selecting previously unselected package libldap-2.4-2:amd64. Preparing to unpack .../libldap-2.4-2_2.4.31-1+nmu2+b1_amd64.deb ... Unpacking libldap-2.4-2:amd64 (2.4.31-1+nmu2+b1) ... Selecting previously unselected package libxml2:amd64. Preparing to unpack .../libxml2_2.9.1+dfsg1-3_amd64.deb ... Unpacking libxml2:amd64 (2.9.1+dfsg1-3) ... Selecting previously unselected package librtmp0:amd64. Preparing to unpack .../librtmp0_2.4+20121230.gitdf6c518-1_amd64.deb ... Unpacking librtmp0:amd64 (2.4+20121230.gitdf6c518-1) ... Selecting previously unselected package libssh2-1:amd64. Preparing to unpack .../libssh2-1_1.4.3-2_amd64.deb ... Unpacking libssh2-1:amd64 (1.4.3-2) ... Selecting previously unselected package libcurl3-gnutls:amd64. Preparing to unpack .../libcurl3-gnutls_7.34.0-1_amd64.deb ... Unpacking libcurl3-gnutls:amd64 (7.34.0-1) ... Selecting previously unselected package libxslt1.1:amd64. Preparing to unpack .../libxslt1.1_1.1.28-2_amd64.deb ... Unpacking libxslt1.1:amd64 (1.1.28-2) ... Selecting previously unselected package libopenscap3. Preparing to unpack .../libopenscap3_0.9.12-1_amd64.deb ... Unpacking libopenscap3 (0.9.12-1) ... Selecting previously unselected package libopenscap8. Preparing to unpack .../libopenscap8_1.0.1-1_amd64.deb ... Unpacking libopenscap8 (1.0.1-1) ... dpkg: error processing archive /var/cache/apt/archives/libopenscap8_1.0.1-1_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/openscap/probe_sysctl', which is also in package libopenscap3 0.9.12-1 dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) Processing triggers for man-db (2.6.5-2) ... Errors were encountered while processing: /var/cache/apt/archives/libopenscap8_1.0.1-1_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) This is a serious bug as it makes installation fail, and violates sections 7.6.1 and 10.1 of the policy. An optimal solution would consist in only one of the packages installing that file, and renaming or removing the file in the other package. Depending on the circumstances you might also consider Replace relations or file diversions. If the conflicting situation cannot be resolved then, as a last resort, the two packages have to declare a mutual Conflict. Please take into account that Replaces, Conflicts and diversions should only be used when packages provide
Processed: add patch
Processing control commands: tags -1 + patch Bug #731156 [libupsclient3] libupsclient3: Library is containing undefined references Added tag(s) patch. -- 731156: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=731156 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#731156: add patch
Control: tags -1 + patch
* Fix linking libupsclient.
* Patch libtool.m4 and configure to support ppc64le.
diff -Nru nut-2.7.1/debian/patches/backport-fix-lp753661.patch
nut-2.7.1/debian/patches/backport-fix-lp753661.patch
--- nut-2.7.1/debian/patches/backport-fix-lp753661.patch1970-01-01
01:00:00.0 +0100
+++ nut-2.7.1/debian/patches/backport-fix-lp753661.patch2013-12-30
10:51:37.0 +0100
@@ -0,0 +1,35 @@
+Description: Trim extraneous end-of-line, in buggy HID string tables
+ Trim extraneous end-of-line, in buggy HID string tables, which results in
+ upsc breaking the communication pipe.
+ .
+ this would be expected to be included in next nut upstream package
+ (greater than 2.6.0)
+Applied-Upstream: http://trac.networkupstools.org/projects/nut/changeset/2972
+Bug: https://bugs.launchpad.net/bugs/753661
+Author: Arnaud Quette aquette@gmail.com
+Last-Update: 2011-05-27
+
+Index: b/drivers/libhid.c
+===
+--- a/drivers/libhid.c
b/drivers/libhid.c
+@@ -400,8 +400,18 @@
+ */
+ char *HIDGetIndexString(hid_dev_handle_t udev, const int Index, char *buf,
size_t buflen)
+ {
+- if (comm_driver-get_string(udev, Index, buf, buflen) 1)
++ char *ptr = NULL;
++
++ if (comm_driver-get_string(udev, Index, buf, buflen) 1)
++ {
+ buf[0] = '\0';
++ }
++ else
++ {
++ /* Check for extraneous end-of-line */
++ if( (ptr = strchr(buf, '\n')) != NULL)
++ *ptr = '\0';
++ }
+
+ return rtrim(buf, '\n');
+ }
diff -Nru nut-2.7.1/debian/patches/link-fixes.diff
nut-2.7.1/debian/patches/link-fixes.diff
--- nut-2.7.1/debian/patches/link-fixes.diff1970-01-01 01:00:00.0
+0100
+++ nut-2.7.1/debian/patches/link-fixes.diff2013-12-30 10:57:07.0
+0100
@@ -0,0 +1,105 @@
+Index: b/clients/Makefile.am
+===
+--- a/clients/Makefile.am
b/clients/Makefile.am
+@@ -46,7 +46,7 @@
+
+ # not LDADD.
+ libupsclient_la_SOURCES = upsclient.c upsclient.h
+-libupsclient_la_LIBADD = ../common/libparseconf.la
++libupsclient_la_LIBADD = ../common/libcommonclient.la
+ if WITH_SSL
+ libupsclient_la_LIBADD += $(LIBSSL_LIBS)
+ endif
+Index: b/clients/Makefile.in
+===
+--- a/clients/Makefile.in
b/clients/Makefile.in
+@@ -445,7 +445,7 @@
+
+ # not LDADD.
+ libupsclient_la_SOURCES = upsclient.c upsclient.h
+-libupsclient_la_LIBADD = ../common/libparseconf.la $(am__append_4)
++libupsclient_la_LIBADD = ../common/libcommonclient.la $(am__append_4)
+
+ # libupsclient version information
+ #
http://www.gnu.org/software/libtool/manual/html_node/Updating-version-info.html
+Index: b/common/Makefile.am
+===
+--- a/common/Makefile.am
b/common/Makefile.am
+@@ -2,7 +2,7 @@
+
+ AM_CFLAGS = -I$(top_srcdir)/include
+
+-noinst_LTLIBRARIES = libparseconf.la libcommon.la
++noinst_LTLIBRARIES = libparseconf.la libcommon.la libcommonclient.la
+ libparseconf_la_SOURCES = parseconf.c
+
+ # do not hard depend on '../include/nut_version.h', since it blocks
+@@ -10,6 +10,8 @@
+ # BUILT_SOURCES (in ../include) will ensure nut_version.h will
+ # be built before anything else
+ libcommon_la_SOURCES = common.c state.c upsconf.c
++libcommonclient_la_SOURCES = common.c state.c
+ # ensure inclusion of local implementation of missing systems functions
+ # using LTLIBOBJS. Refer to configure.in - AC_REPLACE_FUNCS
+ libcommon_la_LIBADD = libparseconf.la @LTLIBOBJS@
++libcommonclient_la_LIBADD = libparseconf.la @LTLIBOBJS@
+Index: b/common/Makefile.in
+===
+--- a/common/Makefile.in
b/common/Makefile.in
+@@ -91,6 +91,9 @@
+ libcommon_la_DEPENDENCIES = libparseconf.la @LTLIBOBJS@
+ am_libcommon_la_OBJECTS = common.lo state.lo upsconf.lo
+ libcommon_la_OBJECTS = $(am_libcommon_la_OBJECTS)
++libcommonclient_la_DEPENDENCIES = libparseconf.la @LTLIBOBJS@
++am_libcommonclient_la_OBJECTS = common.lo state.lo
++libcommonclient_la_OBJECTS = $(am_libcommonclient_la_OBJECTS)
+ libparseconf_la_LIBADD =
+ am_libparseconf_la_OBJECTS = parseconf.lo
+ libparseconf_la_OBJECTS = $(am_libparseconf_la_OBJECTS)
+@@ -107,8 +110,10 @@
+ LINK = $(LIBTOOL) --tag=CC $(AM_LIBTOOLFLAGS) $(LIBTOOLFLAGS) \
+ --mode=link $(CCLD) $(AM_CFLAGS) $(CFLAGS) $(AM_LDFLAGS) \
+ $(LDFLAGS) -o $@
+-SOURCES = $(libcommon_la_SOURCES) $(libparseconf_la_SOURCES)
+-DIST_SOURCES = $(libcommon_la_SOURCES) $(libparseconf_la_SOURCES)
++SOURCES = $(libcommon_la_SOURCES) $(libcommonclient_la_SOURCES) \
++ $(libparseconf_la_SOURCES)
++DIST_SOURCES = $(libcommon_la_SOURCES) $(libcommonclient_la_SOURCES) \
++ $(libparseconf_la_SOURCES)
+ am__can_run_installinfo = \
+ case $$AM_UPDATE_INFO_DIR in \
+ n|no|NO)
Bug#733343: marked as done (reconserver FTBFS on all architectures)
Your message dated Mon, 30 Dec 2013 11:13:35 +0100 with message-id 52c1474f.5020...@pocock.com.au and subject line Re: Bug#733343: reconserver FTBFS on all architectures has caused the Debian Bug report #733343, regarding reconserver FTBFS on all architectures 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.) -- 733343: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=733343 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: reconserver Version: 0.9.1-1 Severity: serious Hi, your package FTBFS on all architectures where it had been tried: | configure: WARNING: unrecognized options: --disable-maintainer-mode |dh_auto_build -a -O--builddirectory=. | make[1]: Entering directory `/«PKGBUILDDIR»' | g++ -DPACKAGE_NAME=\reConServer\ -DPACKAGE_TARNAME=\reconserver\ -DPACKAGE_VERSION=\0.9.1\ -DPACKAGE_STRING=\reConServer\ 0.9.1\ -DPACKAGE_BUGREPORT=\\ -DPACKAGE_URL=\\ -DPACKAGE=\reconserver\ -DVERSION=\0.9.1\ -I. -D_FORTIFY_SOURCE=2 -DRESIP_FIXED_POINT -I/usr/include/sipxtapi -D__pingtel_on_posix__ -D_linux_ -D_REENTRANT -D_FILE_OFFS -DDEFAULT_BRIDGE_MAX_IN_OUTPUTS=20 -DRESIP_TOOLCHAIN_GNU -DUSE_CARES -DUSE_SSL -DUSE_IPV6 -g -O2 -Wformat -Werror=format-security -fpermissive -c -o reConServer.o reConServer.cxx | In file included from /usr/include/recon/UserAgent.hxx:4:0, | from reConServer.cxx:41: | /usr/include/recon/ConversationManager.hxx:12:31: fatal error: resip/stack/Uri.hxx: No such file or directory | #include resip/stack/Uri.hxx |^ | compilation terminated. | make[1]: *** [reConServer.o] Error 1 | make[1]: Leaving directory `/«PKGBUILDDIR»' | dh_auto_build: make -j1 returned exit code 2 | make: *** [build-arch] Error 2 | dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2 Can you please build your package in a clean chroot before upload (i.e. in a chroot where nothing except build-essential and build-dependencies are installed)? Andi ---End Message--- ---BeginMessage--- On 29/12/13 01:41, Ivo De Decker wrote: Control: reassign -1 reconserver 0.9.1-1 Hi Daniel, On Sat, Dec 28, 2013 at 11:31:18PM +0100, Daniel Pocock wrote: reassign 733343 librecon-1.9-dev 1.9.0~beta8-1 fixed 733343 1.9.0~beta8-2 stop reconserver is not really at fault here, I believe librecon-1.9-dev should depend on the related libresiprocate-1.9-dev and so the bug is being reassigned there, fix is being uploaded. Not really. The new resiprocate upload just gets you to the next error: https://buildd.debian.org/status/fetch.php?pkg=reconserverarch=i386ver=0.9.1-1stamp=1388277038 That was also an error with reSIProcate dev package dependencies I added a block hint to make sure this version of reconserver can't migrate to testing (even if this bug gets reassigned). Please let me know when the issues has been dealt with for real, and I will remove the block hint. All the issues in reSIProcate have been fixed and the reConServer package is now building fine What is the best way to force another attempt at building reconserver after the new librecon-1.9-dev is available in unstable? In normal circumstances (when the new upload of a build-dep would fix the issue for real), you could do a new upload with a versioned build-dependency on the new library you uploaded, or you could ask debian-wb-t...@lists.debian.org for a rebuild (in this case, with added 'dep-wait' on the new lib). I happened to notice this bug by chance (because aba mentioned it on irc), but normally, you should explicitly ask for rebuilds on the mailing list. I want to avoid a versioned build dependency because it is quite possible for somebody to build a local version of the reconserver package with an older resiprocate library, they just have to install the build dependencies manually---End Message---
Bug#732709: marked as done (TIFF5 transition)
Your message dated Mon, 30 Dec 2013 10:48:57 +
with message-id e1vxap3-0001xy...@franck.debian.org
and subject line Bug#732709: fixed in insighttoolkit 3.20.1+git20120521-4
has caused the Debian Bug report #732709,
regarding TIFF5 transition
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.)
--
732709: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=732709
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: insighttoolkit
Severity: serious
Version: 3.20.1+git20120521-3
ITK fails to compile with recent TIFF:
/«BUILDDIR»/insighttoolkit-3.20.1+git20120521/Code/IO/itkTIFFImageIO.cxx:1869:78:
error: cannot convert 'const TIFFField* {aka const _TIFFField*}' to
'const TIFFFieldInfo*' in initialization
const TIFFFieldInfo *fld = TIFFFieldWithTag( m_InternalImage-m_Image, tag );
See:
http://buildd.debian-ports.org/status/fetch.php?pkg=insighttoolkitarch=ppc64ver=3.20.1%2Bgit20120521-3%2Bb1stamp=1387344656
---End Message---
---BeginMessage---
Source: insighttoolkit
Source-Version: 3.20.1+git20120521-4
We believe that the bug you reported is fixed in the latest version of
insighttoolkit, which is due to be installed in the Debian FTP archive.
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 732...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Mathieu Malaterre ma...@debian.org (supplier of updated insighttoolkit
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...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Mon, 30 Dec 2013 11:28:43 +0100
Source: insighttoolkit
Binary: libinsighttoolkit3.20 libinsighttoolkit3-dev insighttoolkit3-examples
Architecture: source amd64 all
Version: 3.20.1+git20120521-4
Distribution: unstable
Urgency: low
Maintainer: Debian Med Packaging Team
debian-med-packag...@lists.alioth.debian.org
Changed-By: Mathieu Malaterre ma...@debian.org
Description:
insighttoolkit3-examples - Image processing toolkit for registration and
segmentation - exam
libinsighttoolkit3-dev - Image processing toolkit for registration and
segmentation - deve
libinsighttoolkit3.20 - Image processing toolkit for registration and
segmentation - runt
Closes: 732288 732709
Changes:
insighttoolkit (3.20.1+git20120521-4) unstable; urgency=low
.
* Use dch/9 to get hardening flags correct
* Do not use cmake build system flags. Closes: #732288
* Fix TIFF5 compilation. Closes: #732709
Use libtiff copy, remove B-D libtiff-dev
* Use XZ compression
* Remove obsolete DMUA flag
- Bump Std-Vers to 3.9.5
Checksums-Sha1:
0f79800ef85243afd88f1d5a6d0916c09bb319c0 2467
insighttoolkit_3.20.1+git20120521-4.dsc
81f1813770bef0f89b42f18eba524c5d5e6d3f40 27480
insighttoolkit_3.20.1+git20120521-4.debian.tar.xz
39b33f8ca95b0bf9ff79a37f233840c64aa5f18c 3047926
libinsighttoolkit3.20_3.20.1+git20120521-4_amd64.deb
eb76057b368c4732cf2e22528a4019f6b129202f 3336430
libinsighttoolkit3-dev_3.20.1+git20120521-4_amd64.deb
e19012f5d1d59ae5758a162a3293f5ca125734ab 2411976
insighttoolkit3-examples_3.20.1+git20120521-4_all.deb
Checksums-Sha256:
5766b13bd93d7a5e1439d7fcd5dfd457bc50a7b974635f118c50a5358d21d2a8 2467
insighttoolkit_3.20.1+git20120521-4.dsc
fab5942f5b39700234fdbc7dac7493df1d068e19ac7b74e44dad87962cfe6c56 27480
insighttoolkit_3.20.1+git20120521-4.debian.tar.xz
ea9c7d135ac7def6d6ba72a462b9e7693137a28a6cf32c4f3b750b36049f3dc0 3047926
libinsighttoolkit3.20_3.20.1+git20120521-4_amd64.deb
3ec5705143e3955de4fb87572cb5d8b1165f3dc9aac99a46a990950db194da56 3336430
libinsighttoolkit3-dev_3.20.1+git20120521-4_amd64.deb
df8bd2da51a5526a6c9d1953ecb4951a333f5fe35631e258117504aebdbd586b 2411976
insighttoolkit3-examples_3.20.1+git20120521-4_all.deb
Files:
076ade9348b30edd9bdeba77b66b3c8d 2467 science optional
insighttoolkit_3.20.1+git20120521-4.dsc
4d80b6c0b6eba03cd56da7b1e30c7bd0 27480 science optional
insighttoolkit_3.20.1+git20120521-4.debian.tar.xz
169851dd731a390f4fa0a4ad5ae00c30 3047926 libs optional
libinsighttoolkit3.20_3.20.1+git20120521-4_amd64.deb
2a5acd3b209138a0a3b13668b6bff234 3336430 libdevel optional
libinsighttoolkit3-dev_3.20.1+git20120521-4_amd64.deb
e9eda8c08a1918c4330fd35579ac893e 2411976 devel optional
insighttoolkit3-examples_3.20.1+git20120521-4_all.deb
Processed: tagging 730352
Processing commands for cont...@bugs.debian.org: tags 730352 + patch Bug #730352 [isl] libisl-dev: /usr/include/isl/union_map.h:114:45: error: unknown type name 'isl_multi_aff' Added tag(s) patch. thanks Stopping processing here. Please contact me if you need assistance. -- 730352: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=730352 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
Processed: reassign 730352 to isl
Processing commands for cont...@bugs.debian.org: reassign 730352 isl Bug #730352 [src:llvm-toolchain-3.2] libisl-dev: /usr/include/isl/union_map.h:114:45: error: unknown type name 'isl_multi_aff' Bug reassigned from package 'src:llvm-toolchain-3.2' to 'isl'. Ignoring request to alter found versions of bug #730352 to the same values previously set Ignoring request to alter fixed versions of bug #730352 to the same values previously set thanks Stopping processing here. Please contact me if you need assistance. -- 730352: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=730352 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
Processed: closing 733596
Processing commands for cont...@bugs.debian.org: close 733596 Bug #733596 [libgnomeui-0] libgnomeui-0: Package depends on libgnome-2-0, makes uninstallable Marked Bug as done thanks Stopping processing here. Please contact me if you need assistance. -- 733596: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=733596 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#733596: closing 733596
close 733596 thanks Hi, It seems that libgnomeui-0 can now be properly installed. Closing this bug Cheers, Laurent Bigonville -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#733611: twinkle: FTBFS: automake-1.13: not found
Package: twinkle Version: 1:1.4.2-3 Severity: serious Hi, twinkle FTBFS in current unstable: ... if test -e /usr/share/misc/config.sub ; then \ for i in ./config.sub ; do \ if ! test -e $i.cdbs-orig ; then \ mv $i $i.cdbs-orig ; \ cp --remove-destination /usr/share/misc/config.sub $i ; \ fi ; \ done ; \ fi if [ -e ./configure.ac ] || [ -e ./configure.in ]; then cd . `which autoconfyes || which autoconf`; fi if [ -e ./Makefile.am ]; then cd . automake-1.13 --add-missing --copy ; fi /bin/sh: 1: automake-1.13: not found make: *** [debian/stamp-autotools-files] Error 127 ... Roland -- System Information: Debian Release: 7.0 APT prefers unreleased APT policy: (500, 'unreleased'), (500, 'unstable') Architecture: powerpcspe (ppc) Kernel: Linux 3.9.0-dirty (SMP w/2 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#733616: probabel: FTBFS: chmod: cannot access 'debian/probabel-examples/usr/share/probabel/scripts/extIDS.pl': No such file or directory
Source: probabel Version: 0.4.1-1 Severity: serious Hi, probabel FTBFS in current unstable like this: ... dh_install rm debian/probabel/usr/bin/extract-snp chmod a+x debian/probabel-examples/usr/share/probabel/scripts/extIDS.pl chmod: cannot access 'debian/probabel-examples/usr/share/probabel/scripts/extIDS.pl': No such file or directory make[1]: *** [override_dh_install] Error 1 make[1]: Leaving directory `/«PKGBUILDDIR»' make: *** [binary-arch] Error 2 ... Roland -- System Information: Debian Release: 7.0 APT prefers unreleased APT policy: (500, 'unreleased'), (500, 'unstable') Architecture: powerpcspe (ppc) Kernel: Linux 3.9.0-dirty (SMP w/2 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#733621: mc: tilde expandion in rename/move is broken
Package: mc Version: 3:4.8.11-1 Severity: serious I cannot move files in mc any more. For example, I have the cursor on a file called x and want to move it to my home directory (the other panel does NOT show my home directory right now (but a second work dir), so I need to type it). I type F6 ~ Enter IT RENAMES THE FILE TO ‘~’! I type F6 ~ / x Enter ║/.dillo ║ ~ ╔ Error ═╗ ║ 617│Sep 17 2012║ ║/.dosbox ║ Target ║ Cannot create target file /home/tglase/~/x ║ ║ 134│Jan 6 2009║ ║/.etc ║ /home/t ║ Not a directory (20) ║ ║ 2769│Dec 30 14:00║ ║/.fonts ║ ╟╢ ║ 27│Nov 26 09:20║ ║/.gconf ║ ║ [ Skip ] [ Skip all ] [ Retry ] [ Abort ] ║ ║ 25│Dec 14 2009║ ║/.gconfd ╟ ╚╝ ╢ 1998│Dec 16 17:53║ DAFUQ!!! -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable'), (100, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.11-2-amd64 (SMP w/4 CPU cores) Locale: LANG=C, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/lksh Versions of packages mc depends on: ii e2fslibs 1.42.9-1 ii libc6 2.17-97 ii libglib2.0-0 2.36.4-1 ii libgpm2 1.20.4-6.1 ii libslang2 2.2.4-16 ii libssh2-1 1.4.3-2 ii mc-data 3:4.8.11-1 Versions of packages mc recommends: ii mime-support 3.54 ii perl 5.18.1-5 ii unzip 6.0-10 Versions of packages mc suggests: ii arj 3.10.22-11 ii bzip21.0.6-5 pn dbview none ii djvulibre-bin3.5.25.4-2 ii file 1:5.14-2 ii genisoimage 9:1.1.11-2 ii gv [pdf-viewer] 1:3.7.4-1 ii imagemagick 8:6.7.7.10-7 ii mupdf [pdf-viewer] 1.3-1 pn odt2txt none ii okular [pdf-viewer] 4:4.11.3-1+b1 ii poppler-utils0.18.4-10 ii python 2.7.5-5 pn python-boto none pn python-tznone ii texlive-binaries 2013.20130729.30972-2+b1 ii w3m 0.5.3-13 ii zip 3.0-8 -- 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#733353: wdm: FTBFS: ld: cannot find -lungif
reassign 733353 libwings-dev retitle 733353 libwings-dev : get-wings-flags should not link deprecated libungif found 733353 wmaker/0.95.5-1 thanks 2013/12/28 David Suárez david.sephi...@gmail.com: Source: wdm Version: 1.28-16 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20131226 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Maybe you need to add the needed build depend. Relevant part (hopefully): gcc -Wl,-z,relro -Wl,--as-needed -L./bin -L/usr/lib -L/usr/lib src/TestLogin/TestLogin.o -lWINGs -lWUtil -lwraster -ltiff -lXpm -lpng -ljpeg -lungif -lXft -lXext -lXext -lX11 -lm -lWUtil -lfontconfig -lcrypt -lutil -lwdm -lSM -lICE -lXext -lX11 -lm -lXinerama -o bin/TestLogin /usr/bin/ld: cannot find -lungif collect2: error: ld returned 1 exit status Hi, David and Rodolfo, wdm does not explicitly link against ungif. Seems that recent 'get-wings-flags' from libwings-dev package (used by wdm) forces that link, WLIBS=-lWINGs -lWUtil -lwraster -ltiff -lXpm -lpng -ljpeg -lungif -lXft -lXext -lXext -lX11 -lm Please use -lgif instead of -lungif (See http://bugs.debian.org/732272 for the details). Also some stuff there may already be added by normal X11 configure checks and in any case -lXext is repeated. Reassigning accordingly Regards, -- Agustin -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed (with 1 errors): Re: Bug#733353: wdm: FTBFS: ld: cannot find -lungif
Processing commands for cont...@bugs.debian.org: reassign 733353 libwings-dev Bug #733353 [src:wdm] wdm: FTBFS: ld: cannot find -lungif Bug reassigned from package 'src:wdm' to 'libwings-dev'. No longer marked as found in versions wdm/1.28-16. Ignoring request to alter fixed versions of bug #733353 to the same values previously set retitle 733353 libwings-dev : get-wings-flags should not link Bug #733353 [libwings-dev] wdm: FTBFS: ld: cannot find -lungif Changed Bug title to 'libwings-dev : get-wings-flags should not link' from 'wdm: FTBFS: ld: cannot find -lungif' deprecated libungif Unknown command or malformed arguments to command. found 733353 wmaker/0.95.5-1 Bug #733353 [libwings-dev] libwings-dev : get-wings-flags should not link Marked as found in versions wmaker/0.95.5-1. thanks Stopping processing here. Please contact me if you need assistance. -- 733353: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=733353 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#733375: mlt: FTBFS: producer_pango.c:28:31: fatal error: freetype/freetype.h: No such file or directory
Hi Dan, see below. This also should be fixed upstream to work with recent freetype versions. Thanks! Am 28.12.2013 19:12, schrieb David Suárez: Source: mlt Version: 0.9.0-2 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20131226 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. On the new 2.5 version the headers are located at '/usr/include/freetype2/ftglyph.h' instead of '/usr/include/freetype2/freetype/ftglyph.h' like in previous versions. Relevant part (hopefully): cc -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -DARCH_X86_64 -Wall -DPIC -O2 -pipe -fno-tree-dominator-opts -fno-tree-pre -ffast-math -DUSE_MMX -DUSE_SSE -DUSE_SSE2 -g -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -fPIC -pthread -DARCH_X86_64 -Wall -DPIC -O2 -pipe -fno-tree-dominator-opts -fno-tree-pre -ffast-math -DUSE_MMX -DUSE_SSE -DUSE_SSE2 -g -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -fPIC -pthread -I../.. -DARCH_X86_64 -Wall -DPIC -O2 -pipe -fno-tree-dominator-opts -fno-tree-pre -ffast-math -DUSE_MMX -DUSE_SSE -DUSE_SSE2 -g -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -fPIC -pthread `pkg-config --cflags gtk+-2.0` `pkg-config --cflags gdk-pixbuf-2.0` `pkg-config --cflags pangoft2` -D_FORTIFY_SOURCE=2 -c -o producer_pango.o producer_pango.c producer_pango.c:28:31: fatal error: freetype/freetype.h: No such file or directory #include freetype/freetype.h ^ compilation terminated. make[3]: *** [producer_pango.o] Error 1 The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2013/12/26/mlt_0.9.0-2_unstable.log 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 EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. -- /* Mit freundlichem Gruß / With kind regards, Patrick Matthäi GNU/Linux Debian Developer Blog: http://www.linux-dev.org/ E-Mail: pmatth...@debian.org patr...@linux-dev.org */ signature.asc Description: OpenPGP digital signature
Bug#733628: Underlinked library
Package: insighttoolkit4 Severity: grave Tags: patch By policy shared lib should not be underlinked. Please fix NrrdIO: dpkg-shlibdeps: warning: symbol sqrt used by debian/libinsighttoolkit4.5/usr/lib/libITKNrrdIO-4.5.so.1 found in none of the libraries There is a missing -lm ref: https://buildd.debian.org/status/fetch.php?pkg=insighttoolkit4arch=i386ver=4.5.0-1stamp=1388355262 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#733632: mpv: FTBFS on mips/mipsel/powerpc/sparc: undefined reference to `__sync_add_and_fetch_8'
Package: mpv
Version: 0.3.0-1
Severity: serious
Tags: upstream patch
Justification: fails to build from source (but built successfully in the past)
mpv fails to build from source on mips/mipsel/powerpc/sparc with the
following error message:
| [243/243] linking - build/mpv
| common/msg.c.10.o: In function `mp_msg_update_msglevels':
| /«PKGBUILDDIR»/build/../common/msg.c:243: undefined reference to
`__sync_add_and_fetch_8'
| collect2: error: ld returned 1 exit status
| Waf: Leaving directory `/«PKGBUILDDIR»/build'
| Build failed
The problem is that the new version of mpv tries to uses 64-bit GCC
legacy atomic builtins [1], which are not all available on all
architectures.
The solution to this problem is to use the new GCC atomics, similar
to the C11 ones [2]. For that you need GCC 4.8, which is unfortunately
not the default on all architectures, and to link with libatomic. The
later library provides a fallback implementation if a given atomic bultin
is not available natively, which is usually the case for 64-bit atomics
on 32-bit platforms.
The patch below implements that and should fix the problem, though I
have only tested it on mips so far.
[1] http://gcc.gnu.org/onlinedocs/gcc/_005f_005fsync-Builtins.html
[2] http://gcc.gnu.org/onlinedocs/gcc/_005f_005fatomic-Builtins.html
--- mpv-0.3.0/debian/control
+++ mpv-0.3.0/debian/control
@@ -45,7 +45,8 @@
pkg-config,
python,
python-docutils,
- yasm
+ yasm,
+ gcc-4.8
Standards-Version: 3.9.5
Homepage: http://mpv.io/
Vcs-Git: git://anonscm.debian.org/pkg-multimedia/mpv.git
--- mpv-0.3.0/debian/patches/04_gcc-atomic.diff
+++ mpv-0.3.0/debian/patches/04_gcc-atomic.diff
@@ -0,0 +1,21 @@
+--- mpv-0.3.0/compat/atomics.h
mpv-0.3.0/compat/atomics.h
+@@ -20,4 +20,4 @@
+ // time. We only support a full memory barrier.
+
+ #define mp_memory_barrier() __sync_synchronize()
+-#define mp_atomic_add_and_fetch(a, b) __sync_add_and_fetch(a, b)
++#define mp_atomic_add_and_fetch(a, b) __atomic_fetch_add(a, b,
__ATOMIC_SEQ_CST)
+--- mpv-0.3.0/wscript
mpv-0.3.0/wscript
+@@ -104,6 +104,10 @@ main_dependencies = [
+ 'deps': [ 'pthreads' ],
+ 'func': check_cc(lib='rt')
+ }, {
++'name': 'libatomic',
++'desc': 'linking with -latomic',
++'func': check_cc(lib='atomic')
++}, {
+ 'name': '--iconv',
+ 'desc': 'iconv',
+ 'func': check_iconv,
--- mpv-0.3.0/debian/patches/series
+++ mpv-0.3.0/debian/patches/series
@@ -1,3 +1,4 @@
01_desktop-path.patch
02_fix-config-path.patch
03_waf.patch
+04_gcc-atomic.diff
--- mpv-0.3.0/debian/rules
+++ mpv-0.3.0/debian/rules
@@ -1,5 +1,7 @@
#!/usr/bin/make -f
+export CC=gcc-4.8
+
%:
dh $@
-- System Information:
Debian Release: jessie/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: mips (mips64)
Kernel: Linux 3.2.0-4-5kc-malta
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: closing 730211
Processing commands for cont...@bugs.debian.org: # Of course, I forgot to close it back, sorry close 730211 Bug #730211 [wxwidgets2.8] wx-common built by both wxwidgets2.8 and wxwidgets3.0 Marked Bug as done thanks Stopping processing here. Please contact me if you need assistance. -- 730211: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=730211 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#720902: marked as done (libspring-java: CVE-2013-4152)
Your message dated Mon, 30 Dec 2013 15:21:14 + with message-id e1vxeey-0008v2...@franck.debian.org and subject line Bug#720902: fixed in libspring-java 3.0.6.RELEASE-10 has caused the Debian Bug report #720902, regarding libspring-java: CVE-2013-4152 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.) -- 720902: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=720902 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: libspring-java Severity: grave Tags: security Justification: user security hole Please see https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2013-4152 for details. Cheers, Moritz ---End Message--- ---BeginMessage--- Source: libspring-java Source-Version: 3.0.6.RELEASE-10 We believe that the bug you reported is fixed in the latest version of libspring-java, which is due to be installed in the Debian FTP archive. 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 720...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Markus Koschany a...@gambaru.de (supplier of updated libspring-java package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sun, 29 Dec 2013 13:24:03 +0100 Source: libspring-java Binary: libspring-core-java libspring-beans-java libspring-aop-java libspring-context-java libspring-context-support-java libspring-web-java libspring-web-servlet-java libspring-web-struts-java libspring-web-portlet-java libspring-test-java libspring-transaction-java libspring-jdbc-java libspring-jms-java libspring-orm-java libspring-expression-java libspring-oxm-java libspring-instrument-java Architecture: source all Version: 3.0.6.RELEASE-10 Distribution: unstable Urgency: high Maintainer: Debian Java Maintainers pkg-java-maintain...@lists.alioth.debian.org Changed-By: Markus Koschany a...@gambaru.de Description: libspring-aop-java - modular Java/J2EE application framework - AOP libspring-beans-java - modular Java/J2EE application framework - Beans libspring-context-java - modular Java/J2EE application framework - Context libspring-context-support-java - modular Java/J2EE application framework - Context Support libspring-core-java - modular Java/J2EE application framework - Core libspring-expression-java - modular Java/J2EE application framework - Expression language libspring-instrument-java - modular Java/J2EE application framework - Instrumentation libspring-jdbc-java - modular Java/J2EE application framework - JDBC tools libspring-jms-java - modular Java/J2EE application framework - JMS tools libspring-orm-java - modular Java/J2EE application framework - ORM tools libspring-oxm-java - modular Java/J2EE application framework - Object/XML Mapping libspring-test-java - modular Java/J2EE application framework - Test helpers libspring-transaction-java - modular Java/J2EE application framework - transaction libspring-web-java - modular Java/J2EE application framework - Web libspring-web-portlet-java - modular Java/J2EE application framework - Portlet MVC libspring-web-servlet-java - modular Java/J2EE application framework - Web Portlet libspring-web-struts-java - modular Java/J2EE application framework - Struts MVC Closes: 720902 Changes: libspring-java (3.0.6.RELEASE-10) unstable; urgency=high . * Team upload. * Fix CVE-2013-4152. (Closes: #720902). - New patch: Add-processExternalEntities-to-JAXB2Marshaller.patch. - Now by default external XML entities are not processed when unmarshalling. Processing of external entities will only be enabled/disabled when the source passed to the unmarshaller is a SAXSource or StreamSource. It has no effect for DOMSource or StAXSource instances. Checksums-Sha1: f7bdcfe13b5e689774c27c16e58e8313659399fb 4484 libspring-java_3.0.6.RELEASE-10.dsc 6979c683b599e13a25fa7d4fdbc46685c0c7b8a4 21494 libspring-java_3.0.6.RELEASE-10.debian.tar.gz 38023b902df58589000676f5fc87c71e917808c7 359796 libspring-core-java_3.0.6.RELEASE-10_all.deb 9ecddf4987a930822046f6485c1bf045d5b2ba02 516248 libspring-beans-java_3.0.6.RELEASE-10_all.deb 4886f787c4fd1fb5821019ce0123c46b1a97f820 326750 libspring-aop-java_3.0.6.RELEASE-10_all.deb
Bug#729691: marked as done (xine-lib: FTBFS: xineplug_inp_smb.so missing on dh_install)
Your message dated Mon, 30 Dec 2013 15:27:10 + with message-id e1vxeki-0001q0...@franck.debian.org and subject line Bug#729691: fixed in xine-lib 1.1.21-1.2 has caused the Debian Bug report #729691, regarding xine-lib: FTBFS: xineplug_inp_smb.so missing on dh_install 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.) -- 729691: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=729691 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: xine-lib Version: 1.1.21-1.1 Severity: serious Hi, xine-lib FTBFS like this: ... dpkg-deb: building package `libxine1-x' in `../libxine1-x_1.1.21-1.1_amd64.deb'. make[1]: Leaving directory `/tmp/buildd/xine-lib-1.1.21' (cd debian/libxine1-x find .) | grep -v DEBIAN binary-libxine1-x-stamp make -f debian/rules binary-common DH_OPTIONS=-plibxine1-misc-plugins DH_PACKAGE=libxine1-misc-plugins Package libmodplug was not found in the pkg-config search path. Perhaps you should add the directory containing `libmodplug.pc' to the PKG_CONFIG_PATH environment variable No package 'libmodplug' found make[1]: Entering directory `/tmp/buildd/xine-lib-1.1.21' working on package libxine1-misc-plugins dh_testdir dh_testroot dh_install dh_install: libxine1-misc-plugins missing files (debian/tmp/usr/lib/xine/plugins/*/xineplug_inp_smb.so), aborting make[1]: *** [binary-common] Error 2 make[1]: Leaving directory `/tmp/buildd/xine-lib-1.1.21' make: *** [binary-libxine1-misc-plugins] Error 2 ... Roland -- System Information: Debian Release: 7.0 APT prefers unreleased APT policy: (500, 'unreleased'), (500, 'unstable') Architecture: powerpcspe (ppc) Kernel: Linux 3.9.0-dirty (SMP w/2 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash ---End Message--- ---BeginMessage--- Source: xine-lib Source-Version: 1.1.21-1.2 We believe that the bug you reported is fixed in the latest version of xine-lib, which is due to be installed in the Debian FTP archive. 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 729...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. David Prévot taf...@debian.org (supplier of updated xine-lib 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...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 24 Dec 2013 23:00:23 -0400 Source: xine-lib Binary: libxine1-doc libxine1 libxine1-bin libxine-dev libxine1-ffmpeg libxine1-gnome libxine1-console libxine1-x libxine1-misc-plugins libxine1-dbg libxine1-plugins libxine1-all-plugins Architecture: source all amd64 Version: 1.1.21-1.2 Distribution: unstable Urgency: medium Maintainer: Darren Salt li...@youmustbejoking.demon.co.uk Changed-By: David Prévot taf...@debian.org Description: libxine-dev - xine video player library ‒ development packages libxine1 - xine video/media player library – meta-package libxine1-all-plugins - xine video/media player library ‒ meta package for all plugins libxine1-bin - xine video/media player library ‒ binary files libxine1-console - libaa/libcaca/framebuffer/directfb related plugins for libxine1 libxine1-dbg - debug symbols for libxine1 libxine1-doc - xine video player library – documentation files libxine1-ffmpeg - MPEG-related plugins for libxine1 libxine1-gnome - GNOME-related plugins for libxine1 libxine1-misc-plugins - Input, audio output and post plugins for libxine1 libxine1-plugins - xine video/media player library ‒ meta package for common plugins libxine1-x - X desktop video output plugins for libxine1 Closes: 729691 Changes: xine-lib (1.1.21-1.2) unstable; urgency=medium . * Non-maintainer upload. * Adapt to libsmbclient.h new path. (Closes: #729691) Checksums-Sha1: 47915b11faff1a0375d66a2c9950c39ab6417735 2986 xine-lib_1.1.21-1.2.dsc 65cf8209de03f8b6c7b1b7dc3113e814cb0561e9 44300 xine-lib_1.1.21-1.2.debian.tar.gz 84b26bdf0a1cfb6e9243276973fe863d994175a8 151650 libxine1-doc_1.1.21-1.2_all.deb c229577d3ffee65da4f619ef649bf75e19399336 64872 libxine1-plugins_1.1.21-1.2_all.deb aa039cc45b4b469000fb0ddf4d3894c45f73822c 64882 libxine1-all-plugins_1.1.21-1.2_all.deb ebe4913c00d0c0491eb018bc245b117720a4a2f2 1562 libxine1_1.1.21-1.2_amd64.deb b5c2158a5982d92e262edda340b0a7895d3bfc77 1554846
Bug#733204: marked as done (boinc-app-seti causes segfault in boinc-client on armel)
Your message dated Mon, 30 Dec 2013 15:58:38 + with message-id 52c1982e.6040...@googlemail.com and subject line has caused the Debian Bug report #733204, regarding boinc-app-seti causes segfault in boinc-client on armel 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.) -- 733204: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=733204 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: boinc-app-seti Version: 7.00~svn1933-1 Severity: grave Usertags: unwarranted-self-importance-upstream Control: found -1 boinc-client/7.2.33+dfsg-1 User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu Running the setiathome_advanced binary from boinc-app-seti (from Unstable) on an armel chroot causes boinc-client to segfault immediately. core_client_version7.2.33/core_client_version ![CDATA[ message process exited with code 193 (0xc1, -63) /message stderr_txt boinc-app-seti is invoked with the following arguments: --start --end. I: boinc_parse_init_data_file I: boinc_get_init_data I: boinc_init I: worker I: worker() - common_init I: worker() - read_wu_state SIGSEGV: segmentation violation Stack trace (9 frames): /usr/lib/libboinc.so.7(boinc_catch_signal+0xd8)[0x40078470] /lib/arm-linux-gnueabi/libc.so.6(__default_sa_restorer_v2+0x0)[0x405b2bb0] ../../projects/setiathome.berkeley.edu/setiathome_enhanced(+0x658d0)[0x2a0658d0] ../../projects/setiathome.berkeley.edu/setiathome_enhanced(+0x24fbc)[0x2a024fbc] ../../projects/setiathome.berkeley.edu/setiathome_enhanced(+0x205d4)[0x2a0205d4] ../../projects/setiathome.berkeley.edu/setiathome_enhanced(+0x272d0)[0x2a0272d0] ../../projects/setiathome.berkeley.edu/setiathome_enhanced(+0x27660)[0x2a027660] ../../projects/setiathome.berkeley.edu/setiathome_enhanced(main+0x21c)[0x2a006de0] /lib/arm-linux-gnueabi/libc.so.6(__libc_start_main+0x118)[0x4059c0cc] Exiting... /stderr_txt ]] I have tried on multiple devices and even qemu-arm-static but the result is always the same. Upstream have a version which works natively with Android, so it should be possible, although using the available binaries causes issues which I have no yet looked into further. The only other package to test is from Squeeze but that is too old (version 5.x). Originally reported at http://setiathome.berkeley.edu/forum_thread.php?id=73619 which included details of testing but removed by a childish moderator (reported). ---End Message--- ---BeginMessage--- Control: fixed -1 7.19~svn2050-2.is.7.00~svn1933-1 Never mind, it's finally shown up. I had no idea the queue on the build machines were so long. So far so good: no segfault and it is currently running.---End Message---
Processed: memcached: CVE-2013-7239: SASL authentication allows wrong credentials to access memcache
Processing control commands: forwarded -1 https://code.google.com/p/memcached/issues/detail?id=316 Bug #733643 [memcached] memcached: CVE-2013-7239: SASL authentication allows wrong credentials to access memcache Set Bug forwarded-to-address to 'https://code.google.com/p/memcached/issues/detail?id=316'. -- 733643: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=733643 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#733643: memcached: CVE-2013-7239: SASL authentication allows wrong credentials to access memcache
Package: memcached
Version: 1.4.13-0.2
Severity: grave
Tags: security upstream fixed-upstream patch
Control: forwarded -1 https://code.google.com/p/memcached/issues/detail?id=316
Hi
memcached from wheezy on is affected by an authentication bypass issue
when SASL authentication is turned on. Quoting upstream bugreport:
1. Ran memcached server with following flags -S -d -m 1024 0.0.0.0 -p
11211 -u ubuntu
2. Add user with saslpasswd2 -a memcached -c newuser
3. Pointed cached store: dalli_store, 'domain.com:11211', { :username =
newuser, :password *** } ( I am using dalli gem in Rails application)
4. When I try to access memcache with wrong credentials, on the first
try I get message that authentication failed, which is fine. But, when
I try again to access the cache it lets me do it even I have provided
wrong credentials.
This is reported upstream as [1]. Upstream has commited a patch to
resolve this issue at [2]. The testsuite addition demostrates the
probelm as well.
CVE-2013-7239 is assigned for this issue.
[1] https://code.google.com/p/memcached/issues/detail?id=316
[2]
https://github.com/memcached/memcached/commit/87c1cf0f20be20608d3becf854e9cf0910f4ad32
Regards,
Salvatore
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: reassign 730675 to miniupnpc, found 730675 in 1.5-2, closing 730675
Processing commands for cont...@bugs.debian.org:
# The BTS is currently confused by libminiupnpc5 since it’s not provided in
1.6-2
reassign 730675 miniupnpc
Bug #730675 {Done: Thomas Goirand z...@debian.org} [libminiupnpc5] Contains
static library libminiupnpc.a; should be in -dev package
Bug reassigned from package 'libminiupnpc5' to 'miniupnpc'.
No longer marked as found in versions miniupnpc/1.5-2.
No longer marked as fixed in versions 1.6-2.
# Restoring versions that should be nuked by reassign
found 730675 1.5-2
Bug #730675 {Done: Thomas Goirand z...@debian.org} [miniupnpc] Contains
static library libminiupnpc.a; should be in -dev package
Marked as found in versions miniupnpc/1.5-2 and reopened.
# Hopefully it will be closed again with the accurate version
close 730675 1.6-2
Bug #730675 [miniupnpc] Contains static library libminiupnpc.a; should be in
-dev package
Marked as fixed in versions miniupnpc/1.6-2.
Bug #730675 [miniupnpc] Contains static library libminiupnpc.a; should be in
-dev package
Marked Bug as done
thanks
Stopping processing here.
Please contact me if you need assistance.
--
730675: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=730675
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#733643: memcached: diff for NMU version 1.4.13-0.3
Hi
Attached is a preliminary debdiff for fixing both issues.
Regards,
Salvatore
diff -Nru memcached-1.4.13/debian/changelog memcached-1.4.13/debian/changelog
--- memcached-1.4.13/debian/changelog 2013-01-23 21:22:12.0 +0100
+++ memcached-1.4.13/debian/changelog 2013-12-30 17:58:45.0 +0100
@@ -1,3 +1,15 @@
+memcached (1.4.13-0.3) unstable; urgency=high
+
+ * Non-maintainer upload.
+ * Add 06_CVE-2011-4971.patch patch.
+CVE-2011-4971: Fix remote denial of service. Sending a specially
+crafted packet cause memcached to segfault. (Closes: #706426)
+ * Add 07_CVE-2013-7239.patch patch.
+CVE-2013-7239: SASL authentication allows wrong credentials to access
+memcache. (Closes: #733643)
+
+ -- Salvatore Bonaccorso car...@debian.org Mon, 30 Dec 2013 17:47:44 +0100
+
memcached (1.4.13-0.2) unstable; urgency=low
* Non-maintainer upload.
diff -Nru memcached-1.4.13/debian/patches/06_CVE-2011-4971.patch memcached-1.4.13/debian/patches/06_CVE-2011-4971.patch
--- memcached-1.4.13/debian/patches/06_CVE-2011-4971.patch 1970-01-01 01:00:00.0 +0100
+++ memcached-1.4.13/debian/patches/06_CVE-2011-4971.patch 2013-12-30 17:58:45.0 +0100
@@ -0,0 +1,54 @@
+Description: Fix segfault on specially crafted packet
+ CVE-2011-4971: remote denial of service
+Origin: upstream, http://github.com/memcached/memcached/commit/6695ccbc525c36d693aaa3e8337b36aa0c784424
+Bug: https://code.google.com/p/memcached/issues/detail?id=192
+Bug-Debian: http://bugs.debian.org/706426
+Bug-RedHat: https://bugzilla.redhat.com/show_bug.cgi?id=957964
+Forwarded: not-needed
+Author: Huzaifa Sidhpurwala huzai...@redhat.com
+Reviewed-by: Salvatore Bonaccorso car...@debian.org
+Last-Update: 2013-12-29
+Applied-Upstream: 1.4.16
+
+--- a/memcached.c
b/memcached.c
+@@ -3874,6 +3874,16 @@
+ complete_nread(c);
+ break;
+ }
++
++/* Check if rbytes 0, to prevent crash */
++if (c-rlbytes 0) {
++if (settings.verbose) {
++fprintf(stderr, Invalid rlbytes to read: len %d\n, c-rlbytes);
++}
++conn_set_state(c, conn_closing);
++break;
++}
++
+ /* first check if we have leftovers in the conn_read buffer */
+ if (c-rbytes 0) {
+ int tocopy = c-rbytes c-rlbytes ? c-rlbytes : c-rbytes;
+--- /dev/null
b/t/issue_192.t
+@@ -0,0 +1,20 @@
++#!/usr/bin/perl
++
++use strict;
++use Test::More tests = 2;
++use FindBin qw($Bin);
++use lib $Bin/lib;
++use MemcachedTest;
++
++my $server = new_memcached();
++my $sock = $server-sock;
++
++ok($server-new_sock, opened new socket);
++
++print $sock \x80\x12\x00\x01\x08\x00\x00\x00\xff\xff\xff\xe8\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\xff\xff\xff\xff\x01\x00\x00\x00\x00\x00\x00\x00\x00\x000\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00;
++
++sleep 0.5;
++ok($server-new_sock, failed to open new socket);
++
++
++
diff -Nru memcached-1.4.13/debian/patches/07_CVE-2013-7239.patch memcached-1.4.13/debian/patches/07_CVE-2013-7239.patch
--- memcached-1.4.13/debian/patches/07_CVE-2013-7239.patch 1970-01-01 01:00:00.0 +0100
+++ memcached-1.4.13/debian/patches/07_CVE-2013-7239.patch 2013-12-30 17:58:45.0 +0100
@@ -0,0 +1,122 @@
+Description: CVE-2013-7239: SASL authentication allows wrong credentials to access memcache
+ It was previously possible to bypass authentication due to implicit
+ state management. Now we explicitly consider ourselves
+ unauthenticated on any new connections and authentication attempts.
+Origin: upstream, https://github.com/memcached/memcached/commit/87c1cf0f20be20608d3becf854e9cf0910f4ad32
+Bug: https://code.google.com/p/memcached/issues/detail?id=316
+Bug-Debian: http://bugs.debian.org/733643
+Forwarded: not-needed
+Last-Update: 2013-12-30
+Applied-Upstream: 1.4.17
+
+--- a/memcached.c
b/memcached.c
+@@ -442,6 +442,7 @@
+ c-iovused = 0;
+ c-msgcurr = 0;
+ c-msgused = 0;
++c-authenticated = false;
+
+ c-write_and_go = init_state;
+ c-write_and_free = 0;
+@@ -1602,6 +1603,8 @@
+ if (!settings.sasl)
+ return;
+
++c-authenticated = false;
++
+ if (!c-sasl_conn) {
+ int result=sasl_server_new(memcached,
+NULL,
+@@ -1736,6 +1739,7 @@
+
+ switch(result) {
+ case SASL_OK:
++c-authenticated = true;
+ write_bin_response(c, Authenticated, 0, 0, strlen(Authenticated));
+ pthread_mutex_lock(c-thread-stats.mutex);
+ c-thread-stats.auth_cmds++;
+@@ -1772,11 +1776,7 @@
+ rv = true;
+ break;
+ default:
+-if (c-sasl_conn) {
+-const void *uname = NULL;
+-sasl_getprop(c-sasl_conn, SASL_USERNAME, uname);
+-rv = uname != NULL;
+-}
++rv = c-authenticated;
+ }
+
+ if (settings.verbose 1) {
Bug#733651: general: Any USB card reader works only after being replugged.
Package: general Severity: grave Justification: renders package unusable Dear Maintainer, *** Please consider answering these questions, where appropriate *** After system reboot or replugging USB card reader into USB slot, the SD or MMC or Memory Stick card appears in /dev/disks/by-id, say as /dev/sde, and in Nautilus panel. After unmounting it from Nautilus or from command line it disappears as it should. But if memory card is pulled out and inserted again, it does not appear again in Nautilus and dmesg shows no reaction. At the same time the device /dev/sde still exists, even if memory card is absent. If I issue fdisk -l /dev/sde with inserted card, it appears in Nautilus and in dmesg: [ 4713.404064] sd 6:0:0:0: [sde] 62666752 512-byte logical blocks: (32.0 GB/29.8 GiB) [ 4713.405183] sd 6:0:0:0: [sde] No Caching mode page found [ 4713.405191] sd 6:0:0:0: [sde] Assuming drive cache: write through [ 4713.407902] sd 6:0:0:0: [sde] No Caching mode page found [ 4713.407911] sd 6:0:0:0: [sde] Assuming drive cache: write through [ 4713.409345] sde: sde1 [ 4713.821575] EXT4-fs (sde1): recovery complete [ 4713.824733] EXT4-fs (sde1): mounted filesystem with ordered data mode. Opts: (null) If I unplug the mamory card, dmesg says: [ 4779.180564] sde: detected capacity change from 32085377024 to 0 This behaviour began in september 2013 as far as I remember. It was annoying, I thought my card reader was broken and I replaced it, but problem still remained. So it is a bug. Affects cryptdisks as the key is stored on SD card. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (630, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.12-1-amd64 (SMP w/6 CPU cores) Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#733403: marked as done (nted: FTBFS: mainwindow.cpp:27:31: fatal error: freetype/freetype.h: No such file or directory)
Your message dated Mon, 30 Dec 2013 17:48:30 +
with message-id e1vxgx4-0002xd...@franck.debian.org
and subject line Bug#733403: fixed in nted 1.10.18-7
has caused the Debian Bug report #733403,
regarding nted: FTBFS: mainwindow.cpp:27:31: fatal error: freetype/freetype.h:
No such file or directory
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.)
--
733403: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=733403
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Source: nted
Version: 1.10.18-6
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20131226 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
On the new 2.5 version the headers are located at
'/usr/include/freetype2/ftglyph.h' instead of
'/usr/include/freetype2/freetype/ftglyph.h' like in previous versions.
Relevant part (hopefully):
g++ -DHAVE_CONFIG_H -I. -DNTED_HTMLDIR=\/usr/share/doc/nted\
-DNTED_DATADIR=\/usr/share/nted\ -DLOCALEDIR=\/usr/share/locale\
-I./dialogs -I./commands -I./chords -I./idiotseditor -I/usr/include/freetype2
-I/usr/include/cairo -I/usr/include/glib-2.0
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/pixman-1
-I/usr/include/freetype2 -I/usr/include/libpng12 -I/usr/include/libdrm
-pthread -I/usr/include/gtk-2.0 -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include
-I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0
-I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/
-I/usr/include/freetype2 -I/usr/include/glib-2.0
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/pixman-1
-I/usr/include/libpng12 -I/usr/include/libdrm -I/usr/include/harfbuzz
-pthread -I/usr/include/pango-1.0 -I/usr/include/glib-2.0
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -D_FORTIFY_SOURCE=2 -Wall
-Wwrite-strings -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat
-Werror=format-security -c -o mainwindow.o mainwindow.cpp
mainwindow.cpp:27:31: fatal error: freetype/freetype.h: No such file or
directory
#include freetype/freetype.h
^
compilation terminated.
make[3]: *** [mainwindow.o] Error 1
The full build log is available from:
http://aws-logs.debian.net/ftbfs-logs/2013/12/26/nted_1.10.18-6_unstable.log
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 EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
---End Message---
---BeginMessage---
Source: nted
Source-Version: 1.10.18-7
We believe that the bug you reported is fixed in the latest version of
nted, which is due to be installed in the Debian FTP archive.
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 733...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Gilles Filippini p...@debian.org (supplier of updated nted 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...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Mon, 30 Dec 2013 18:07:07 +0100
Source: nted
Binary: nted nted-doc
Architecture: source i386 all
Version: 1.10.18-7
Distribution: unstable
Urgency: low
Maintainer: Gilles Filippini p...@debian.org
Changed-By: Gilles Filippini p...@debian.org
Description:
nted - Musical score editor
nted-doc - NtEd documentation
Closes: 727475 733403
Changes:
nted (1.10.18-7) unstable; urgency=low
.
* Build depend on autotools-dev and use 'dh --with autotools_dev' to
auto update config.{guess,sub} (closes: #727475)
* New patch freetype-include-path.patch to handle the new freetype
headers location starting with its 2.5 release (closes: #733403).
* Bump Standards-Version to 3.9.5 (no changes needed).
Checksums-Sha1:
ef588ce0b001f6686f5cc02fd42991bc1fe3a37b 1652 nted_1.10.18-7.dsc
7b7cfb34f4db4684f0ea3d783384bae3b1604cde 25817 nted_1.10.18-7.debian.tar.gz
0d9a21fd41b5a9ba35c111b2cf320955febcac1e 500512 nted_1.10.18-7_i386.deb
3893ee09b733830ec6af4f2b2e75171fa2080990 2701752
Bug#733402: psychtoolbox-3: FTBFS: OGLFT.cpp:38:31: fatal error: freetype/ftbitmap.h: No such file or directory
Hi, thanks for reporting, just in time for the new release :). The bug should be fixed in the latest release from today and will probably trickle into Debian within a couple of days, courtesy of the NeuroDebian team. Wish you a good new year, -mario On 28/12/13 19:17, David Suárez wrote: Source: psychtoolbox-3 Version: 3.0.11.20131017.dfsg1-3 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20131226 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. On the new 2.5 version the headers are located at '/usr/include/freetype2/ftglyph.h' instead of '/usr/include/freetype2/freetype/ftglyph.h' like in previous versions. Relevant part (hopefully): g++ -Wall -g -O0 -I. -I/usr/include/ -I/usr/include/freetype2/ \ -L/usr/lib -pie -shared -fPIC \ -Wl,-Bsymbolic -Wl,-Bsymbolic-functions \ -Wl,--version-script=linuxexportlist.txt \ -o libptbdrawtext_ftgl.so.1 \ libptbdrawtext_ftgl.cpp qstringqcharemulation.cpp OGLFT.cpp \ -lGL -lGLU -lfontconfig -lfreetype OGLFT.cpp:38:31: fatal error: freetype/ftbitmap.h: No such file or directory #include freetype/ftbitmap.h ^ compilation terminated. make[1]: *** [build-stamp] Error 1 The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2013/12/26/psychtoolbox-3_3.0.11.20131017.dfsg1-3_unstable.log 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 EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: found 733391 in 3.0.0-2
Processing commands for cont...@bugs.debian.org: found 733391 3.0.0-2 Bug #733391 [src:abiword] abiword: FTBFS: itex2MML.y:298:25: error: 'ret_str' undeclared (first use in this function) Marked as found in versions abiword/3.0.0-2. thanks Stopping processing here. Please contact me if you need assistance. -- 733391: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=733391 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#733651: general: Any USB card reader works only after being replugged.
I can confirm this. # uname -a Linux hope 3.10-2-amd64 #1 SMP Debian 3.10.7-1 (2013-08-17) x86_64 GNU/Linux # cat /etc/debian_version jessie/sid udev/204-5 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#733632: mpv: FTBFS on mips/mipsel/powerpc/sparc: undefined reference to `__sync_add_and_fetch_8'
On lun, dic 30, 2013 at 03:22:38 +0100, Aurelien Jarno wrote:
Package: mpv
Version: 0.3.0-1
Severity: serious
Tags: upstream patch
Justification: fails to build from source (but built successfully in the past)
mpv fails to build from source on mips/mipsel/powerpc/sparc with the
following error message:
| [243/243] linking - build/mpv
| common/msg.c.10.o: In function `mp_msg_update_msglevels':
| /«PKGBUILDDIR»/build/../common/msg.c:243: undefined reference to
`__sync_add_and_fetch_8'
| collect2: error: ld returned 1 exit status
| Waf: Leaving directory `/«PKGBUILDDIR»/build'
| Build failed
Yeah, I'm already working on a patch (which would use __atomic built-ins
directly) with upstream.
--- mpv-0.3.0/debian/control
+++ mpv-0.3.0/debian/control
@@ -45,7 +45,8 @@
pkg-config,
python,
python-docutils,
- yasm
+ yasm,
+ gcc-4.8
I'd rather build-depends on gcc-4.8 (and use it directly) only where it's
needed ([powerpc, sparc]), since e.g. ia64 (and all the other *64) will work
just fine with the default 4.6.
Cheers
--
perl -E '$_=q;$/= @{[@_]};and s;\S+;inidehG ordnasselA;eg;say~~reverse'
signature.asc
Description: Digital signature
Processed: bug 709841 is forwarded to https://bugzilla.mozilla.org/show_bug.cgi?id=764342
Processing commands for cont...@bugs.debian.org: forwarded 709841 https://bugzilla.mozilla.org/show_bug.cgi?id=764342 Bug #709841 [iceweasel] iceweasel: spurious out of memory + crash (segmentation fault) Changed Bug forwarded-to-address to 'https://bugzilla.mozilla.org/show_bug.cgi?id=764342' from 'https://bugzilla.mozilla.org/show_bug.cgi?id=906061' thanks Stopping processing here. Please contact me if you need assistance. -- 709841: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=709841 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#733375: [Mlt-devel] Bug#733375: mlt: FTBFS: producer_pango.c:28:31: fatal error: freetype/freetype.h: No such file or directory
On Mon, Dec 30, 2013 at 5:53 AM, Patrick Matthäi pmatth...@debian.org wrote: Hi Dan, see below. This also should be fixed upstream to work with recent freetype versions. Thanks! Am 28.12.2013 19:12, schrieb David Suárez: Source: mlt Version: 0.9.0-2 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20131226 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. On the new 2.5 version the headers are located at '/usr/include/freetype2/ftglyph.h' instead of '/usr/include/freetype2/freetype/ftglyph.h' like in previous versions. Relevant part (hopefully): cc -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -DARCH_X86_64 -Wall -DPIC -O2 -pipe -fno-tree-dominator-opts -fno-tree-pre -ffast-math -DUSE_MMX -DUSE_SSE -DUSE_SSE2 -g -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -fPIC -pthread -DARCH_X86_64 -Wall -DPIC -O2 -pipe -fno-tree-dominator-opts -fno-tree-pre -ffast-math -DUSE_MMX -DUSE_SSE -DUSE_SSE2 -g -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -fPIC -pthread -I../.. -DARCH_X86_64 -Wall -DPIC -O2 -pipe -fno-tree-dominator-opts -fno-tree-pre -ffast-math -DUSE_MMX -DUSE_SSE -DUSE_SSE2 -g -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -fPIC -pthread `pkg-config --cflags gtk+-2.0` `pkg-config --cflags gdk-pixbuf-2.0` `pkg-config --cflags pangoft2` -D_FORTIFY_SOURCE=2 -c -o producer_pango.o producer_pango.c producer_pango.c:28:31: fatal error: freetype/freetype.h: No such file or directory #include freetype/freetype.h ^ compilation terminated. make[3]: *** [producer_pango.o] Error 1 The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2013/12/26/mlt_0.9.0-2_unstable.log What a major pain. This alone fails because we are using pkg-config --cflags pangoft2: diff --git a/src/modules/gtk2/producer_pango.c b/src/modules/gtk2/producer_pango.c index 4969dd2..ba902bd 100644 --- a/src/modules/gtk2/producer_pango.c +++ b/src/modules/gtk2/producer_pango.c @@ -25,7 +25,7 @@ #include string.h #include gdk-pixbuf/gdk-pixbuf.h #include pango/pangoft2.h -#include freetype/freetype.h +#include freetype.h #include iconv.h #include pthread.h #include ctype.h Adding pkg-config --cflags freetype2 does not help on any of my other systems because of that old freetype subdirectory. So, I have to resort to this ugly hack because `pkg-config --cflags-only-I freetype2` (assuming it only ever outputs one -I) has a trailing space: diff --git a/src/modules/gtk2/Makefile b/src/modules/gtk2/Makefile index b4fb3ff..4a3f5cb 100644 --- a/src/modules/gtk2/Makefile +++ b/src/modules/gtk2/Makefile @@ -35,6 +35,7 @@ endif ifdef USE_PANGO OBJS += producer_pango.o CFLAGS += `pkg-config $(PKGCONFIG_PREFIX) --cflags pangoft2` +CFLAGS += `pkg-config --cflags-only-I freetype2 | sed 's/ *$$//g')`/freetype LDFLAGS += `pkg-config $(PKGCONFIG_PREFIX) --libs pangoft2` ifeq ($(targetos),Darwin) LDFLAGS += -liconv -- +-DRD-+ -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#705565: Getting closure compiler back in testing?
On Monday, December 30, 2013 10:19:53 AM Daniel Pocock wrote: Tony made some commits in Git and it appears he is working to resolve this The rename of the binary package from libclosure-compiler-java - closure-compiler should probably be done now as well to get this out of the way well before the Jessie release. I've made the changes for a rename on a branch called pkgrename and pushed that into Git Tony, are you making another upload shortly, would you like to merge pkgrename perhaps? closure compiler is also a library dependency, e.g. of gwt. It might be a good idea to provide two binary packages, one for the library jar and another one for the manpage + executable. Regards, Thomas Koch -- 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 725743 is important
Processing commands for cont...@bugs.debian.org: # It built on s390x on the second try, and ia64 is not a release architecture severity 725743 important Bug #725743 [procps] procps 1:3.3.8-2 FTBFS on ia64 and s390x Severity set to 'important' from 'serious' thanks Stopping processing here. Please contact me if you need assistance. -- 725743: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=725743 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#705565: Getting closure compiler back in testing?
On 30/12/13 20:35, Thomas Koch wrote: On Monday, December 30, 2013 10:19:53 AM Daniel Pocock wrote: Tony made some commits in Git and it appears he is working to resolve this The rename of the binary package from libclosure-compiler-java - closure-compiler should probably be done now as well to get this out of the way well before the Jessie release. I've made the changes for a rename on a branch called pkgrename and pushed that into Git Tony, are you making another upload shortly, would you like to merge pkgrename perhaps? closure compiler is also a library dependency, e.g. of gwt. It might be a good idea to provide two binary packages, one for the library jar and another one for the manpage + executable. That is awkward with an executable JAR, it is just a single artifact that can be used either way -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#705565: Getting closure compiler back in testing?
On 12/30/2013 11:35 AM, Thomas Koch wrote: On Monday, December 30, 2013 10:19:53 AM Daniel Pocock wrote: Tony made some commits in Git and it appears he is working to resolve this The rename of the binary package from libclosure-compiler-java - closure-compiler should probably be done now as well to get this out of the way well before the Jessie release. I've made the changes for a rename on a branch called pkgrename and pushed that into Git Tony, are you making another upload shortly, would you like to merge pkgrename perhaps? closure compiler is also a library dependency, e.g. of gwt. It might be a good idea to provide two binary packages, one for the library jar and another one for the manpage + executable. Regards, Thomas Koch Hi Thomas, Daniel, I agree with Thomas' suggestion. I'm not sure what the FTP team will think of the very small binary package (the next upload will go through NEW), but adding a binary package with just the manpage + JRE and jarwrapper dependency feels like the right thing to do. Any thoughts about whether it's better to update to a newer upstream and then rename, or rename first? Cheers, tony signature.asc Description: OpenPGP digital signature
Bug#705565: Getting closure compiler back in testing?
On 12/30/2013 11:54 AM, Daniel Pocock wrote: On 30/12/13 20:35, Thomas Koch wrote: On Monday, December 30, 2013 10:19:53 AM Daniel Pocock wrote: Tony made some commits in Git and it appears he is working to resolve this The rename of the binary package from libclosure-compiler-java - closure-compiler should probably be done now as well to get this out of the way well before the Jessie release. I've made the changes for a rename on a branch called pkgrename and pushed that into Git Tony, are you making another upload shortly, would you like to merge pkgrename perhaps? closure compiler is also a library dependency, e.g. of gwt. It might be a good idea to provide two binary packages, one for the library jar and another one for the manpage + executable. That is awkward with an executable JAR, it is just a single artifact that can be used either way It means that the closure-compiler binary package is merely the /usr/bin/ symlink and the dependency on jarwrapper. I don't know that it really matters much - the reason for the rename is to make the binary package easier to find, but the current java library package is named correctly (as per policy and ease of locating) as well. I'm not sure if there is a best practice for executable JARs that are used in both contexts, but adding an additional binary package doesn't seem too bad. tony signature.asc Description: OpenPGP digital signature
Bug#705565: Getting closure compiler back in testing?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 30/12/13 21:03, tony mancill wrote: On 12/30/2013 11:54 AM, Daniel Pocock wrote: On 30/12/13 20:35, Thomas Koch wrote: On Monday, December 30, 2013 10:19:53 AM Daniel Pocock wrote: Tony made some commits in Git and it appears he is working to resolve this The rename of the binary package from libclosure-compiler-java - closure-compiler should probably be done now as well to get this out of the way well before the Jessie release. I've made the changes for a rename on a branch called pkgrename and pushed that into Git Tony, are you making another upload shortly, would you like to merge pkgrename perhaps? closure compiler is also a library dependency, e.g. of gwt. It might be a good idea to provide two binary packages, one for the library jar and another one for the manpage + executable. That is awkward with an executable JAR, it is just a single artifact that can be used either way It means that the closure-compiler binary package is merely the /usr/bin/ symlink and the dependency on jarwrapper. I don't know that it really matters much - the reason for the rename is to make the binary package easier to find, but the current java library package is named correctly (as per policy and ease of locating) as well. I'm not sure if there is a best practice for executable JARs that are used in both contexts, but adding an additional binary package doesn't seem too bad. - From a useability perspective, I agree that the two packages is more appealing I'll change my own packages to depend on closure-compiler when it exists I'd suggest doing the new binary package before doing the update to the latest code, then it will be easier for the FTP masters to review -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Icedove - http://www.enigmail.net/ iQIcBAEBCAAGBQJSwdJ9AAoJEOm1uwJp1aqDFocP+wV2PFBQl4/4YBc/Hn/UJEhR wWhLJS8LlqHzqb3y+f5V/ezK55AYx/G0RWBSWxhsh9xmmOZFF4xqlF/k3wY2kjt4 YehjW8Px+Kn3VDLsb0Fyo6CSGk7N8rathGtcYbLIWDu2Qs/btlucPkdpk4Q8eoYM tf7eMs15tESNyVNkYGSbQ4Tltj1g6W/ZWlXxRnSPVBLSqUBqlXMoUcq/sFgsa/in OpSiszWakp99AMv6MubvM25kKKvlMzVhK9gf2OZ1I8JiX5dFiHw+/liRpRDDnFY+ mfNnvD58LNEvkVVV9xWCG3yVkj8uby8Zd3tBOn4MH2LuagUUUXdFL7neM2l+sSIi 04wua8i7nP0xyqc04Lxvkyt3Se6ro0Vsx6GKfXmR4kcoHjTmJGyWFTru4nPBd9QP 9Iqsk82Ym017nY181+NClgZZDmzxcR3xn8Lv29Adv4rYju4wOfoy6GGQUd2Iwyat 6OP3roxd03bOWXhIi83U72JWwCOxV00RVtLXfmWQFYD2Z6Yt5R4cCJXeZs8/sJZF sOpWWqadbGlUZViN0CJEuTIOBsZQFSt+hQxhNDMD0BFqgnybSkcmEg0j4USougNB lc5jOieLL9V3MoB/El5ht9dylzv9XK5vFG385U94YflxpVuV0MJ4cmyF4L1tRHSX yNzQjg+CE79snZpN8usR =BMiD -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: RM: xmem -- RoQA; RC-buggy, useless, alternatives exist, prevent third-party migration
Processing control commands: severity 730331 serious Bug #730331 [src:xmem] xmem: Needs update to libprocps1-dev Severity set to 'serious' from 'important' tag 730331 - pending Bug #730331 [src:xmem] xmem: Needs update to libprocps1-dev Removed tag(s) pending. -- 730331: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=730331 733668: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=733668 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#733440: golang-gocheck: FTBFS: Tests failed
On 28/12/13 17:59, David Suárez wrote: Source: golang-gocheck Version: 0.0~bzr20131118+85-1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20131226 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. This is due to the fact that go 1.2 was released in between when this was uploaded and NEWed. snip I'm new to package uploads, but this should fix it: http://anonscm.debian.org/gitweb/?p=pkg-go/packages/golang-gocheck.git;a=commit;h=4a1acc55fc6e1ea3b1783129bf4955e72f0bea80 Michael or David do you mind reviewing/sponsoring? Thanks Sergio -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: 729540 is serious
Processing commands for cont...@bugs.debian.org: severity 729540 serious Bug #729540 [open-vm-tools-dkms] open-vm-tools-dkms: Fails to compile with Linux Kernel version 3.11 Severity set to 'serious' from 'normal' thanks Stopping processing here. Please contact me if you need assistance. -- 729540: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=729540 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#733375: [Mlt-devel] Bug#733375: mlt: FTBFS: producer_pango.c:28:31: fatal error: freetype/freetype.h: No such file or directory
On Mon, Dec 30, 2013 at 5:53 AM, Patrick Matthäi pmatth...@debian.org wrote: Hi Dan, see below. This also should be fixed upstream to work with recent freetype versions. Thanks! Am 28.12.2013 19:12, schrieb David Suárez: Source: mlt Version: 0.9.0-2 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20131226 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. On the new 2.5 version the headers are located at '/usr/include/freetype2/ftglyph.h' instead of '/usr/include/freetype2/freetype/ftglyph.h' like in previous versions. Relevant part (hopefully): cc -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -DARCH_X86_64 -Wall -DPIC -O2 -pipe -fno-tree-dominator-opts -fno-tree-pre -ffast-math -DUSE_MMX -DUSE_SSE -DUSE_SSE2 -g -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -fPIC -pthread -DARCH_X86_64 -Wall -DPIC -O2 -pipe -fno-tree-dominator-opts -fno-tree-pre -ffast-math -DUSE_MMX -DUSE_SSE -DUSE_SSE2 -g -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -fPIC -pthread -I../.. -DARCH_X86_64 -Wall -DPIC -O2 -pipe -fno-tree-dominator-opts -fno-tree-pre -ffast-math -DUSE_MMX -DUSE_SSE -DUSE_SSE2 -g -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -fPIC -pthread `pkg-config --cflags gtk+-2.0` `pkg-config --cflags gdk-pixbuf-2.0` `pkg-config --cflags pangoft2` -D_FORTIFY_SOURCE=2 -c -o producer_pango.o producer_pango.c producer_pango.c:28:31: fatal error: freetype/freetype.h: No such file or directory #include freetype/freetype.h ^ compilation terminated. make[3]: *** [producer_pango.o] Error 1 The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2013/12/26/mlt_0.9.0-2_unstable.log Assuming no regressions on our nightly build servers, this is fixed in git commit 4e96e01. -- +-DRD-+ -- 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 733621 is minor
Processing commands for cont...@bugs.debian.org: severity 733621 minor Bug #733621 [mc] mc: tilde expandion in rename/move is broken Severity set to 'minor' from 'serious' thanks Stopping processing here. Please contact me if you need assistance. -- 733621: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=733621 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#733621: mc: tilde expandion in rename/move is broken
On Tue, 31 Dec 2013 00:03:11 Thorsten Glaser wrote: Severity: serious Thanks for your report but please do *not* panic and use correct severity in the future: http://www.debian.org/Bugs/Developer#severities -- Cheers, Dmitry Smirnov GPG key : 4096R/53968D1B -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#733378: marked as done (navit: FTBFS: font_freetype.c:35:30: fatal error: freetype/ftglyph.h: No such file or directory)
Your message dated Mon, 30 Dec 2013 21:19:55 + with message-id e1vxkff-0001lk...@franck.debian.org and subject line Bug#733378: fixed in navit 0.5.0~svn5738+dfsg.1-1 has caused the Debian Bug report #733378, regarding navit: FTBFS: font_freetype.c:35:30: fatal error: freetype/ftglyph.h: No such file or directory 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.) -- 733378: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=733378 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: navit Version: 0.5.0~svn5643+dfsg.1-1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20131226 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. On the new 2.5 version the headers are located at '/usr/include/freetype2/ftglyph.h' instead of '/usr/include/freetype2/freetype/ftglyph.h' like in previous versions. Relevant part (hopefully): make[3]: Entering directory `/«BUILDDIR»/navit-0.5.0~svn5643+dfsg.1/obj-x86_64-linux-gnu' /usr/bin/cmake -E cmake_progress_report /«BUILDDIR»/navit-0.5.0~svn5643+dfsg.1/obj-x86_64-linux-gnu/CMakeFiles [ 2%] Building C object navit/font/freetype/CMakeFiles/font_freetype.dir/font_freetype.c.o cd /«BUILDDIR»/navit-0.5.0~svn5643+dfsg.1/obj-x86_64-linux-gnu/navit/font/freetype /usr/bin/gcc -DMODULE=font_freetype -DQT_CORE_LIB -DQT_DECLARATIVE_LIB -DQT_GUI_LIB -DQT_SVG_LIB -DQT_XML_LIB -DUSE_FRIBIDI=1 -Dfont_freetype_EXPORTS -Wall -Wcast-align -Wpointer-arith -Wextra -Wno-unused-parameter -Wno-sign-compare -Wmissing-prototypes -Wstrict-prototypes-Wno-missing-field-initializers -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 -fPIC -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/freetype2 -isystem /usr/include/qt4 -isystem /usr/include/qt4/QtDeclarative -isystem /usr/include/qt4/QtSvg -isystem /usr/include/qt4/QtGui -isystem /usr/include/qt4/QtXml -isystem /usr/include/qt4/QtCore -isystem /usr/include/gtk-2.0 -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include -I/usr/include/pango-1.0 -I/usr/include/cairo -I/usr/include/atk-1.0 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/«BUILDDIR»/navit-0.5.0~svn5643+dfsg.1/obj-x86_64-linux-gnu -I/«BUILDDIR»/navit-0.5.0~svn5643+dfsg.1 -I/«BUILDDIR»/navit-0.5.0~svn5643+dfsg.1/navit -I/«BUILDDIR»/navit-0.5.0~svn5643+dfsg.1/obj-x86_64-linux-gnu/navit -I/«BUILDDIR»/navit-0.5.0~svn5643+dfsg.1/navit/support -I/«BUILDDIR»/navit-0.5.0~svn5643+dfsg.1/navit/font/freetype -I/«BUILDDIR»/navit-0.5.0~svn5643+dfsg.1/navit/graphics/gtk_drawing_area -I/«BUILDDIR»/navit-0.5.0~svn5643+dfsg.1/navit/graphics/qt_qpainter -I/«BUILDDIR»/navit-0.5.0~svn5643+dfsg.1/navit/gui/gtk -I/«BUILDDIR»/navit-0.5.0~svn5643+dfsg.1/navit/vehicle/gpsd -I/«BUILDDIR»/navit-0.5.0~svn5643+dfsg.1/navit/binding/dbus -I/«BUILDDIR»/navit-0.5.0~svn5643+dfsg.1/navit/speech/dbus -I/«BUILDDIR»/navit-0.5.0~svn5643+dfsg.1/navit/speech/cmdline -I/«BUILDDIR»/navit-0.5.0~svn5643+dfsg.1/navit/vehicle/gpsd_dbus -I/«BUILDDIR»/navit-0.5.0~svn5643+dfsg.1/navit/speech/speech_dispatcher -I/«BUILDDIR»/navit-0.5.0~svn5643+dfsg.1/navit/map/garmin -I/«BUILDDIR»/navit-0.5.0~svn5643+dfsg.1/navit/graphics/null -I/«BUILDDIR»/navit-0.5.0~svn5643+dfsg.1/navit/osd/core -I/«BUILDDIR»/navit-0.5.0~svn5643+dfsg.1/navit/vehicle/demo -I/«BUILDDIR»/navit-0.5.0~svn5643+dfsg.1/navit/vehicle/file -I/«BUILDDIR»/navit-0.5.0~svn5643+dfsg.1/navit/vehicle/null -I/«BUILDDIR»/navit-0.5.0~svn5643+dfsg.1/navit/gui/internal -I/«BUILDDIR»/navit-0.5.0~svn5643+dfsg.1/navit/map/binfile -I/«BUILDDIR»/navit-0.5.0~svn5643+dfsg.1/navit/map/filter -I/«BUILDDIR»/navit-0.5.0~svn5643+dfsg.1/navit/map/mg -I/«BUILDDIR»/navit-0.5.0~svn5643+dfsg.1/navit/map/shapefile -I/«BUILDDIR»/navit-0.5.0~svn5643+dfsg.1/navit/map/textfile -I/«BUILDDIR»/navit-0.5.0~svn5643+dfsg.1/navit/map/csv -I/«BUILDDIR»/navit-0.5.0~svn5643+dfsg.1/navit/plugin/pedestrian -I/«BUILDDIR»/navit-0.5.0~svn5643+dfsg.1/navit/fib-1.1 -I/usr/include/fribidi-fPIC -o CMakeFiles/font_freetype.dir/font_freetype.c.o -c /«BUILDDIR»/navit-0.5.0~svn5643+dfsg.1/navit/font/freetype/font_freetype.c /«BUILDDIR»/navit-0.5.0~svn5643+dfsg.1/navit/font/freetype/font_freetype.c:35:30: fatal error: freetype/ftglyph.h: No such file or directory #include freetype/ftglyph.h ^ compilation terminated.
Processed: Bug#733378 marked as pending
Processing commands for cont...@bugs.debian.org:
tag 733378 pending
Bug #733378 {Done: Gilles Filippini p...@debian.org} [src:navit] navit:
FTBFS: font_freetype.c:35:30: fatal error: freetype/ftglyph.h: No such file or
directory
Added tag(s) pending.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
733378: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=733378
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
Processed: tagging 724120
Processing commands for cont...@bugs.debian.org: tags 724120 + confirmed Bug #724120 [src:cdk] cdk: FTBFS: [javac] /«PKGBUILDDIR»/build/src/extra/org/openscience/cdk/geometry/alignment/KabschAlignment.java:34: error: package Jama does not exist Added tag(s) confirmed. thanks Stopping processing here. Please contact me if you need assistance. -- 724120: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=724120 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#733378: marked as pending
tag 733378 pending thanks Hello, Bug #733378 reported by you has been fixed in the Git repository. You can see the changelog below, and you can check the diff of the fix at: http://git.debian.org/?p=collab-maint/navit.git;a=commitdiff;h=6be089a --- commit 6be089acb285b93049e5d487fd112eddd2eccf09 Author: Gilles Filippini p...@debian.org Date: Mon Dec 30 20:27:52 2013 +0100 debian/changelog update. diff --git a/debian/changelog b/debian/changelog index b401b5e..99d45dc 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,22 @@ +navit (0.5.0~svn5738+dfsg.1-1) UNRELEASED; urgency=medium + + * New upstream snapshot: ++ gui_internal: + - Add menu entry for coordinate input + - Move Quit to top level ++ Many translations update ++ Bug fixes. + + * New patch freetype-include-path.patch to handle the new freetype +headers location starting with its 2.5 release (closes: #733378). + * Refresh patches: ++ icons-dir ++ maptool-uninitialised-values.patch + + * Bump Standards-Version to 3.9.5 (no changes needed). + + -- Gilles Filippini p...@debian.org Mon, 30 Dec 2013 18:53:38 +0100 + navit (0.5.0~svn5643+dfsg.1-1) unstable; urgency=low * New upstream snapshot: -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: closing 701376
Processing commands for cont...@bugs.debian.org: tag 701376 -sid Bug #701376 [src:zookeeper] zookeeper: ftbfs with GCC-4.8 Removed tag(s) sid. close 701376 3.4.5+dfsg-1 Bug #701376 [src:zookeeper] zookeeper: ftbfs with GCC-4.8 Ignoring request to alter fixed versions of bug #701376 to the same values previously set Bug #701376 [src:zookeeper] zookeeper: ftbfs with GCC-4.8 Marked Bug as done thanks Stopping processing here. Please contact me if you need assistance. -- 701376: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=701376 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#701376: closing 701376
tag 701376 -sid close 701376 3.4.5+dfsg-1 thanks Closing, as this bug doesn't affect Debian wheezy, jessie, or sid using the compilers available in each release. tony -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#733677: ghc: BD uninstallable on architecture S390x
Package: ghc Version: 7.6.3-6 Severity: serious Hi, your package has status BD uninstallable on S390x because it depends on ghc itself which fails to build in version 7.6.3-4. This prevents testing migration from other packages. Thorsten -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#733677: marked as done (ghc: BD uninstallable on architecture S390x)
Your message dated Tue, 31 Dec 2013 00:15:32 +0100 with message-id 1388445332.16949.13.camel@kirk and subject line Re: Bug#733677: ghc: BD uninstallable on architecture S390x has caused the Debian Bug report #733677, regarding ghc: BD uninstallable on architecture S390x 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.) -- 733677: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=733677 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: ghc Version: 7.6.3-6 Severity: serious Hi, your package has status BD uninstallable on S390x because it depends on ghc itself which fails to build in version 7.6.3-4. This prevents testing migration from other packages. Thorsten ---End Message--- ---BeginMessage--- Hi, Am Montag, den 30.12.2013, 23:32 +0100 schrieb Thorsten Alteholz: your package has status BD uninstallable on S390x because it depends on ghc itself which fails to build in version 7.6.3-4. This prevents testing migration from other packages. ghc had to be removed from s390x because of a FTBFS that noone stepped up to investigate: https://ghc.haskell.org/trac/ghc/ticket/7993 http://bugs.debian.org/719669 To bring ghc back there, someone needs to bootstrap it (probably from some old version from stable or from snapshots. If it prevents migration, then the affected packages should have their s390x package in unstable removed. File a bug against ftp.debian.org in that case. What packages are affected? Greetings, Joachim -- Joachim nomeata Breitner Debian Developer nome...@debian.org | ICQ# 74513189 | GPG-Keyid: 4743206C JID: nome...@joachim-breitner.de | http://people.debian.org/~nomeata signature.asc Description: This is a digitally signed message part ---End Message---
Bug#705565: Getting closure compiler back in testing?
On Mon, 30 Dec 2013 12:03:13 -0800, tony mancill wrote: The rename of the binary package from libclosure-compiler-java - closure-compiler should probably be done now as well to get this out of the way well before the Jessie release. It means that the closure-compiler binary package is merely the /usr/bin/ symlink and the dependency on jarwrapper. Can't this be solved with a simple Provides: closure-compiler in the libclosure-compiler-java package? (Or the other way round.) Having a de facto empty package doesn't seem very appealing to me. 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: Bob Dylan: Temporary like Achilles signature.asc Description: Digital signature
Bug#728243: redmine: diff for NMU version 2.3.3-3.1
tags 728243 + patch
tags 728243 + pending
thanks
Dear maintainer,
I've prepared an NMU for redmine (versioned as 2.3.3-3.1) and
uploaded it to DELAYED/1. Please feel free to tell me if I
should cancel it.
As long as ruby-mysql and ruby-mysql2 provide different interfaces,
they just can't be handled using the current postinst.
Regards.
diff -Nru redmine-2.3.3/debian/changelog redmine-2.3.3/debian/changelog
--- redmine-2.3.3/debian/changelog 2013-12-02 23:47:42.0 +0100
+++ redmine-2.3.3/debian/changelog 2013-12-31 00:08:21.0 +0100
@@ -1,3 +1,12 @@
+redmine (2.3.3-3.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Tighten redmine-mysql dependencies to ruby-mysql, as ruby-mysql2
+exposes another interface and does not work OOTB with the current
+postinst. (Closes: #728243)
+
+ -- Christian Hofstaedtler z...@debian.org Tue, 31 Dec 2013 00:05:41 +0100
+
redmine (2.3.3-3) unstable; urgency=low
* Drop unused rubygems build-dependency.
diff -Nru redmine-2.3.3/debian/control redmine-2.3.3/debian/control
--- redmine-2.3.3/debian/control2013-12-02 23:45:56.0 +0100
+++ redmine-2.3.3/debian/control2013-12-31 00:05:28.0 +0100
@@ -63,7 +63,7 @@
Package: redmine-mysql
Architecture: all
-Depends: ruby-mysql2 (= 0.3.11) | ruby-mysql (= 2.8.1),
+Depends: ruby-mysql (= 2.8.1),
mysql-client | virtual-mysql-client,
${misc:Depends}
Recommends: redmine (= ${source:Version})
--
,''`. Christian Hofstaedtler z...@debian.org
: :' : Debian Developer
`. `' 7D1A CFFA D9E0 806C 9C4C D392 5C13 D6DB 9305 2E03
`-
signature.asc
Description: Digital signature
Processed: redmine: diff for NMU version 2.3.3-3.1
Processing commands for cont...@bugs.debian.org: tags 728243 + patch Bug #728243 [redmine] redmine: fails to install: Please install the mysql adapter Added tag(s) patch. tags 728243 + pending Bug #728243 [redmine] redmine: fails to install: Please install the mysql adapter Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 728243: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=728243 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
Processed: libio-all-perl: io-file-assert creates directory instead of file
Processing control commands: block 730895 by -1 Bug #730895 [src:libspork-perl] libspork-perl: FTBFS: Failed tests 730895 was not blocked by any bugs. 730895 was not blocking any bugs. Added blocking bug(s) of 730895: 733680 -- 730895: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=730895 733680: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=733680 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#733353: wdm: FTBFS: ld: cannot find -lungif
On 30/12/2013 14:33, Agustin Martin wrote: reassign 733353 libwings-dev retitle 733353 libwings-dev : get-wings-flags should not link deprecated libungif found 733353 wmaker/0.95.5-1 thanks 2013/12/28 David Suárez david.sephi...@gmail.com: Source: wdm Version: 1.28-16 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20131226 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Maybe you need to add the needed build depend. Relevant part (hopefully): gcc -Wl,-z,relro -Wl,--as-needed -L./bin -L/usr/lib -L/usr/lib src/TestLogin/TestLogin.o -lWINGs -lWUtil -lwraster -ltiff -lXpm -lpng -ljpeg -lungif -lXft -lXext -lXext -lX11 -lm -lWUtil -lfontconfig -lcrypt -lutil -lwdm -lSM -lICE -lXext -lX11 -lm -lXinerama -o bin/TestLogin /usr/bin/ld: cannot find -lungif collect2: error: ld returned 1 exit status Hi, David and Rodolfo, wdm does not explicitly link against ungif. Seems that recent 'get-wings-flags' from libwings-dev package (used by wdm) forces that link, WLIBS=-lWINGs -lWUtil -lwraster -ltiff -lXpm -lpng -ljpeg -lungif -lXft -lXext -lXext -lX11 -lm Please use -lgif instead of -lungif (See http://bugs.debian.org/732272 for the details). Also some stuff there may already be added by normal X11 configure checks and in any case -lXext is repeated. Reassigning accordingly Regards, Hi, I was testing the problem and is now solved at upstream. The current wmaker package code is the upstream master branch, but the bug is solved in the next branch. The configure.ac code was moved to m4/wm_imgfmt_check.m4, and only -lgif is selected: ---8--- 39 dnl We check first if one of the known libraries is available 40 for wm_arg in -lgif -lungif ; do 41AS_IF([wm_fn_lib_try_link DGifOpenFileName $XLFLAGS $XLIBS $wm_arg], 42 [wm_cv_imgfmt_gif=$wm_arg ; break]) 43 done ---8--- The next branch is like a testing branch, so I will create a debian/patch to solve this issue with the current upstream code (master branch). I will remove only the -lungif in this patch. Thanks for your report. Best regards, kix -- ||// //\\// Rodolfo kix Garcia ||\\// //\\ http://www.kix.es/ -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#733353: marked as done (libwings-dev : get-wings-flags should not link)
Your message dated Mon, 30 Dec 2013 23:49:57 + with message-id e1vxmar-0006s7...@franck.debian.org and subject line Bug#733353: fixed in wmaker 0.95.5-2 has caused the Debian Bug report #733353, regarding libwings-dev : get-wings-flags should not link 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.) -- 733353: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=733353 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: wdm Version: 1.28-16 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20131226 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Maybe you need to add the needed build depend. Relevant part (hopefully): gcc -Wl,-z,relro -Wl,--as-needed -L./bin -L/usr/lib -L/usr/lib src/TestLogin/TestLogin.o -lWINGs -lWUtil -lwraster -ltiff -lXpm -lpng -ljpeg -lungif -lXft -lXext -lXext -lX11 -lm -lWUtil -lfontconfig -lcrypt -lutil -lwdm -lSM -lICE -lXext -lX11 -lm -lXinerama -o bin/TestLogin /usr/bin/ld: cannot find -lungif collect2: error: ld returned 1 exit status The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2013/12/26/wdm_1.28-16_unstable.log 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 EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. ---End Message--- ---BeginMessage--- Source: wmaker Source-Version: 0.95.5-2 We believe that the bug you reported is fixed in the latest version of wmaker, which is due to be installed in the Debian FTP archive. 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 733...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Rodolfo García Peñas (kix) k...@debian.org (supplier of updated wmaker 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...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 31 Dec 2013 00:20:43 +0100 Source: wmaker Binary: wmaker wmaker-common libwraster3-dev libwraster3 libwings-dev libwutil3 libwings2 wmaker-dbg Architecture: source amd64 all Version: 0.95.5-2 Distribution: unstable Urgency: low Maintainer: Rodolfo García Peñas (kix) k...@debian.org Changed-By: Rodolfo García Peñas (kix) k...@debian.org Description: libwings-dev - Window Maker's own widget set libwings2 - Window Maker's own widget set - runtime library libwraster3 - Shared libraries of Window Maker rasterizer libwraster3-dev - Static libraries and headers of Window Maker rasterizer libwutil3 - Window Maker's own widget set - utility library wmaker - NeXTSTEP-like window manager for X wmaker-common - Window Maker - Architecture independent files wmaker-dbg - Debugging symbols for WindowMaker packages Closes: 733353 Changes: wmaker (0.95.5-2) unstable; urgency=low . * New patch debian/patches/56_ungif_problem.diff. [Closes: #733353] This patch removes the link against -lungif. * Bumped to standard version 3.9.5. No changes. Checksums-Sha1: 5d956b18ca6fb0b0e0a621abb830f8e729662d1a 1974 wmaker_0.95.5-2.dsc b04aef6a9076dd31a4e819275a78ece1784db28e 2927995 wmaker_0.95.5.orig.tar.gz 72437caf567d23beff9fc557c852a34d2d1d200d 306631 wmaker_0.95.5-2.debian.tar.gz dfe6521d4ccff64e20c197366ec4d14e3736d31b 429770 wmaker_0.95.5-2_amd64.deb b4db5c0e3fffdd3bd8c9023f977bbbce01edb013 1273518 wmaker-common_0.95.5-2_all.deb 2642e32d2329704ac625173aa0ffb798cb0654b8 115116 libwraster3-dev_0.95.5-2_amd64.deb a6c5d3ad47741b318f36ee0d923ff1f59d2b28fe 108154 libwraster3_0.95.5-2_amd64.deb f30df4175e4d101c92688318340fb25d5b3fbfb8 284054 libwings-dev_0.95.5-2_amd64.deb d84e0b50d7f5178f10cebf55d1ad3d16992a82d5 116946 libwutil3_0.95.5-2_amd64.deb 6eead40f39dfd8b9f0a9f841b315b05bd81e000b 211994 libwings2_0.95.5-2_amd64.deb 9cbb2c899c7992699bc388824a1d9bdd835be23a 1891510 wmaker-dbg_0.95.5-2_amd64.deb Checksums-Sha256: 413d7e762ad279fd495d24ad73af8ba3e56f677d778b877290f7ffeb3245d650 1974 wmaker_0.95.5-2.dsc
Bug#705565: Getting closure compiler back in testing?
On 12/30/2013 03:15 PM, gregor herrmann wrote: On Mon, 30 Dec 2013 12:03:13 -0800, tony mancill wrote: The rename of the binary package from libclosure-compiler-java - closure-compiler should probably be done now as well to get this out of the way well before the Jessie release. It means that the closure-compiler binary package is merely the /usr/bin/ symlink and the dependency on jarwrapper. Can't this be solved with a simple Provides: closure-compiler in the libclosure-compiler-java package? (Or the other way round.) Having a de facto empty package doesn't seem very appealing to me. Hi gregor, Yes, that will work, provided that no users of libclosure-compiler-java have concerns with jarwrapper (and its depdendencies, thus binfmt-support and fastjar) being pulled in when they only want the library. Given that all 3 packages are small, it's probably a non-issue. Thanks for the suggestion! tony signature.asc Description: OpenPGP digital signature
Bug#733330: call to __builtin___strncpy_chk will always overflow destination buffer [enabled by default]
Am 2013-12-28 17:10, schrieb Mathieu Malaterre: Package: refdb Severity: serious In function 'strncpy', inlined from 'main' at refdbd.c:1335:15: /usr/include/x86_64-kfreebsd-gnu/bits/string3.h:120:3: warning: call to __builtin___strncpy_chk will always overflow destination buffer [enabled by default] return __builtin___strncpy_chk (__dest, __src, __len, __bos (__dest)); ^ ref: https://buildd.debian.org/status/fetch.php?pkg=refdbarch=kfreebsd-amd64ver=1.0.0~pre2-3stamp=1388246765 fixed upstream, see revision 778. regards, Markus -- Markus Hoenicka http://www.mhoenicka.de AQ score 38 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#730895: libspork-perl: FTBFS: Failed tests
Hi, some background: David Suárez wrote: During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): make[1]: Entering directory `/«PKGBUILDDIR»' PERL_DL_NONLAZY=1 /usr/bin/perl -MExtUtils::Command::MM -e test_harness(0, 'inc', 'blib/lib', 'blib/arch') t/*.t t/formatter1.t .. ok Can't open file 'Spork.slides' for output: Is a directory at /usr/share/perl5/Spoon/Installer.pm line 31 (#1) This is actually caused by http://bugs.debian.org/733680, a regression in libio-all-perl 0.50-1. It may be possible to fix this by patching Spoon::Installer from libspoon-perl. But I probably haven't found all assert method calls. Interestingly libspoon-perl doesn't FTBFS because of that issue. Our current hope is that today's libio-all-perl upstream release fixes #733680. Regards, Axel -- ,''`. | Axel Beckert a...@debian.org, http://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE `-| 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#733147: Bug#733684: nmu: opensmtpd_5.3.3p1-4
Ryan Kavanagh r...@debian.org (2013-12-30): Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: binnmu Hi, Ever since openssl was updated from from version 1.0.1e-5 to 1.0.1e-6, opensmtpd fails to start because of an OpenSSL version mismatch[0]. Please binNMU opensmtpd against the new openssl. nmu opensmtpd_5.3.3p1-4 . ALL . -m No change rebuild against new openssl (Closes: #733147) NACK, if opensmtpd needs a very specific version of openssl (the exact one it was built against), it must depend on this specific version. That being said, why would it even need such a thing to start with? Mraw, KiBi. signature.asc Description: Digital signature
Processed: severity of 733124 is normal
Processing commands for cont...@bugs.debian.org: severity 733124 normal Bug #733124 [ruby-rjb] ruby-rjb: FTBFS on !i386 !amd64: architecture, operating system detection incomplete Severity set to 'normal' from 'serious' thanks Stopping processing here. Please contact me if you need assistance. -- 733124: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=733124 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#724120: marked as done (cdk: FTBFS: [javac] /«PKGBUILDDIR»/build/src/extra/org/openscience/cdk/geometry/alignment/KabschAlignment.java:34: error: package Jama does not exist)
Your message dated Tue, 31 Dec 2013 00:33:27 +
with message-id e1vxngx-0006af...@franck.debian.org
and subject line Bug#724120: fixed in cdk 1:1.2.10-5
has caused the Debian Bug report #724120,
regarding cdk: FTBFS: [javac]
/«PKGBUILDDIR»/build/src/extra/org/openscience/cdk/geometry/alignment/KabschAlignment.java:34:
error: package Jama does not exist
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.)
--
724120: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=724120
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Source: cdk
Version: 1:1.2.10-4
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20130922 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part (hopefully):
compile-module:
[echo] Compiling classes for CDK's extra module from src/main...
[echo] Datafiles defined: true
[echo] Extra files defined: ${module.extrafiles.present}
[echo] CDK dependencies defined: true
[echo] Library dependencies defined: true
[echo] Developer Library dependencies defined:
${module.devellibdepends.present}
[echo] Autogenerated files specified: ${module.autogenerated.present}
[mkdir] Created dir: /«PKGBUILDDIR»/build/src/extra
[mkdir] Created dir: /«PKGBUILDDIR»/build/extra
[copy] Copying 79 files to /«PKGBUILDDIR»/build/src/extra
[javac] Compiling 79 source files to /«PKGBUILDDIR»/build/extra
[javac] warning: [options] bootstrap class path not set in conjunction
with -source 1.5
[javac]
/«PKGBUILDDIR»/build/src/extra/org/openscience/cdk/geometry/alignment/KabschAlignment.java:34:
error: package Jama does not exist
[javac] import Jama.EigenvalueDecomposition;
[javac]^
[javac]
/«PKGBUILDDIR»/build/src/extra/org/openscience/cdk/geometry/alignment/KabschAlignment.java:35:
error: package Jama does not exist
[javac] import Jama.Matrix;
[javac]^
[javac]
/«PKGBUILDDIR»/build/src/extra/org/openscience/cdk/geometry/alignment/KabschAlignment.java:290:
error: cannot find symbol
[javac] Matrix tmp;
[javac] ^
[javac] symbol: class Matrix
[javac] location: class KabschAlignment
[javac]
/«PKGBUILDDIR»/build/src/extra/org/openscience/cdk/geometry/alignment/KabschAlignment.java:329:
error: cannot find symbol
[javac] tmp = new Matrix(tR);
[javac] ^
[javac] symbol: class Matrix
[javac] location: class KabschAlignment
[javac]
/«PKGBUILDDIR»/build/src/extra/org/openscience/cdk/geometry/alignment/KabschAlignment.java:335:
error: cannot find symbol
[javac] Matrix jamaR = new Matrix(R);
[javac] ^
[javac] symbol: class Matrix
[javac] location: class KabschAlignment
[javac]
/«PKGBUILDDIR»/build/src/extra/org/openscience/cdk/geometry/alignment/KabschAlignment.java:335:
error: cannot find symbol
[javac] Matrix jamaR = new Matrix(R);
[javac]^
[javac] symbol: class Matrix
[javac] location: class KabschAlignment
[javac]
/«PKGBUILDDIR»/build/src/extra/org/openscience/cdk/geometry/alignment/KabschAlignment.java:340:
error: cannot find symbol
[javac] Matrix jamaRtR = new Matrix(RtR);
[javac] ^
[javac] symbol: class Matrix
[javac] location: class KabschAlignment
[javac]
/«PKGBUILDDIR»/build/src/extra/org/openscience/cdk/geometry/alignment/KabschAlignment.java:340:
error: cannot find symbol
[javac] Matrix jamaRtR = new Matrix(RtR);
[javac] ^
[javac] symbol: class Matrix
[javac] location: class KabschAlignment
[javac]
/«PKGBUILDDIR»/build/src/extra/org/openscience/cdk/geometry/alignment/KabschAlignment.java:341:
error: cannot find symbol
[javac] EigenvalueDecomposition ed = jamaRtR.eig();
[javac] ^
[javac] symbol: class EigenvalueDecomposition
[javac] location: class KabschAlignment
[javac]
/«PKGBUILDDIR»/build/src/extra/org/openscience/cdk/validate/BasicValidator.java:321:
warning: [deprecation] getBondOrderSum(IAtom) in AtomContainer has been
deprecated
[javac] int bos = (int)molecule.getBondOrderSum(atom);
[javac]^
[javac] Note: Some input files use unchecked or unsafe operations.
[javac] Note:
Processed: gitweb package is for configuration, broken with apache2.4
Processing commands for cont...@bugs.debian.org: tags 669292 + jessie sid experimental Bug #669292 [gitweb] gitweb: automatic configuration breaks with apache2 2.4 Bug #669798 [gitweb] gitweb: transition towards Apache 2.4 Added tag(s) sid, experimental, and jessie. Added tag(s) sid, experimental, and jessie. severity 669292 grave Bug #669292 [gitweb] gitweb: automatic configuration breaks with apache2 2.4 Bug #669798 [gitweb] gitweb: transition towards Apache 2.4 Severity set to 'grave' from 'important' Severity set to 'grave' from 'important' End of message, stopping processing here. Please contact me if you need assistance. -- 669292: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=669292 669798: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=669798 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#730895: libspork-perl: FTBFS: Failed tests
Hi, Axel Beckert wrote: Our current hope is that today's libio-all-perl upstream release fixes #733680. It didn't. :-( Will upload it anyways as it seems to fix another regression. Regards, Axel -- ,''`. | Axel Beckert a...@debian.org, http://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE `-| 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 -- 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 730895 is grave ...
Processing commands for cont...@bugs.debian.org: # does not only fail to build, it also fails to work severity 730895 grave Bug #730895 [src:libspork-perl] libspork-perl: FTBFS: Failed tests Severity set to 'grave' from 'serious' retitle 730895 libspork-perl: FTBFS and no more works since libio-all-perl 0.50-1 Bug #730895 [src:libspork-perl] libspork-perl: FTBFS: Failed tests Changed Bug title to 'libspork-perl: FTBFS and no more works since libio-all-perl 0.50-1' from 'libspork-perl: FTBFS: Failed tests' thanks Stopping processing here. Please contact me if you need assistance. -- 730895: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=730895 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
Processed: limit source to owncloud-client, tagging 733306
Processing commands for cont...@bugs.debian.org: #owncloud-client (1.5.0+dfsg-3) unstable; urgency=medium # # * Fix the testsuite (Closes: #733306) # limit source owncloud-client Limiting to bugs with field 'source' containing at least one of 'owncloud-client' Limit currently set to 'source':'owncloud-client' tags 733306 + pending Bug #733306 [src:owncloud-client] owncloud-client: FTBFS: 'hasLaunchOnStartup(appName) == true' returned FALSE Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 733306: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=733306 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
Processed: tagging 732806
Processing commands for cont...@bugs.debian.org: tags 732806 + confirmed pending Bug #732806 [vlc-data] vlc-data: installation error caused by trying to remove non-existing /etc/lvc/lua files Bug #733190 [vlc-data] vlc not installable Added tag(s) confirmed and pending. Added tag(s) confirmed and pending. thanks Stopping processing here. Please contact me if you need assistance. -- 732806: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=732806 733190: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=733190 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#733690: libuhd003: segmentation fault in gnuradio
Package: libuhd003 Version: 3.5.5-1 Severity: grave Justification: renders package unusable Hi, after upgrading libuhd003 to 3.5.5-1, gnuradio dies with a segmentation fault on startup. Downgrading libuhd003 to 3.4.2-1 from wheezy fixes the issue. This problem also occurs when no Ettus hardware is installed, effectively breaking gnuradio for everyone. Simon -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.11-2-amd64 (SMP w/8 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages libuhd003 depends on: ii adduser 3.113+nmu3 ii libboost-date-time1.49.01.49.0-4+b3 ii libboost-filesystem1.49.0 1.49.0-4+b3 ii libboost-program-options1.49.0 1.49.0-4+b3 ii libboost-regex1.49.01.49.0-4+b3 ii libboost-system1.49.0 1.49.0-4+b3 ii libboost-test1.49.0 1.49.0-4+b3 ii libboost-thread1.49.0 1.49.0-4+b3 ii libc6 2.17-97 ii libgcc1 1:4.8.2-10 ii liborc-0.4-01:0.4.18-1 ii libstdc++6 4.8.2-10 ii libusb-1.0-02:1.0.17-1+b1 ii multiarch-support 2.17-97 ii python 2.7.5-5 Versions of packages libuhd003 recommends: ii gnuradio 3.5.3.2-1 Versions of packages libuhd003 suggests: pn uhd-contrib-images none -- 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#733306: marked as done (owncloud-client: FTBFS: 'hasLaunchOnStartup(appName) == true' returned FALSE)
Your message dated Tue, 31 Dec 2013 03:20:32 + with message-id e1vxpse-0004fa...@franck.debian.org and subject line Bug#733306: fixed in owncloud-client 1.5.0+dfsg-3 has caused the Debian Bug report #733306, regarding owncloud-client: FTBFS: 'hasLaunchOnStartup(appName) == true' returned FALSE 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.) -- 733306: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=733306 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: owncloud-client Version: 1.5.0+dfsg-2 Severity: serious Hi, owncloud-client fails to build from source on most arches, see the logs on the autobuilders: ... Running tests... /usr/bin/ctest --force-new-ctest-process -j8 Test project /«BUILDDIR»/owncloud-client-1.5.0+dfsg/obj-i486-linux-gnu Start 1: OwncloudPropagatorTest Start 2: UtilityTest Errors while running CTest 1/2 Test #2: UtilityTest ..***Failed0.03 sec * Start testing of TestUtility * Config: Using QTest library 4.8.6, Qt 4.8.6 PASS : TestUtility::initTestCase() PASS : TestUtility::testFormatFingerprint() PASS : TestUtility::testOctetsToString() QDEBUG : TestUtility::testLaunchOnStartup() Could not create autostart directory FAIL! : TestUtility::testLaunchOnStartup() 'hasLaunchOnStartup(appName) == true' returned FALSE. () Loc: [/«BUILDDIR»/owncloud-client-1.5.0+dfsg/obj-i486-linux-gnu/test/../../test/testutility.h(66)] PASS : TestUtility::testToCSyncScheme() PASS : TestUtility::cleanupTestCase() Totals: 5 passed, 1 failed, 0 skipped * Finished testing of TestUtility * 2/2 Test #1: OwncloudPropagatorTest ... Passed0.03 sec 50% tests passed, 1 tests failed out of 2 Total Test time (real) = 0.04 sec The following tests FAILED: 2 - UtilityTest (Failed) make[1]: *** [test] Error 8 make[1]: Leaving directory `/«BUILDDIR»/owncloud-client-1.5.0+dfsg/obj-i486-linux-gnu' dh_auto_test: make -j8 test ARGS+=-j8 returned exit code 2 make: *** [build-arch] Error 2 dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2 ... Roland -- System Information: Debian Release: 7.0 APT prefers unreleased APT policy: (500, 'unreleased'), (500, 'unstable') Architecture: powerpcspe (ppc) Kernel: Linux 3.9.0-dirty (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_GB.UTF-8) Shell: /bin/sh linked to /bin/dash ---End Message--- ---BeginMessage--- Source: owncloud-client Source-Version: 1.5.0+dfsg-3 We believe that the bug you reported is fixed in the latest version of owncloud-client, which is due to be installed in the Debian FTP archive. 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 733...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sandro Knauß b...@sandroknauss.de (supplier of updated owncloud-client 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...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 31 Dec 2013 02:17:37 +0100 Source: owncloud-client Binary: owncloud-client owncloud-client-doc mirall-doc libowncloudsync0 owncloud-client-l10n mirall-l10n owncloud-client-cmd Architecture: source amd64 all Version: 1.5.0+dfsg-3 Distribution: unstable Urgency: medium Maintainer: ownCloud for Debian maintainers pkg-owncloud-maintain...@lists.alioth.debian.org Changed-By: Sandro Knauß b...@sandroknauss.de Description: libowncloudsync0 - ownCloudSync folder synchronization - libraries mirall-doc - transitional dummy package for owncloud-client-doc mirall-l10n - transitional dummy package for owncloud-client-l10n owncloud-client - folder synchronization with an ownCloud server - GUI owncloud-client-cmd - folder synchronization with an ownCloud server - cmd client owncloud-client-doc - ownCloudSync folder synchronization - documentation owncloud-client-l10n - ownCloudSync folder synchronization - localization Closes: 733306 Changes: owncloud-client (1.5.0+dfsg-3) unstable; urgency=medium . [ David Prévot ] * Fixed tests filename . [ Sandro Knauß ] * Added patch to respect XDG_CONFIG_HOME env variable * Fix the testsuite (Closes: #733306) * Updated
Bug#678696: to the world
world peace treaty is almost there I am going to email to the president and kindly ask him to sign a WORLD PEACE TREATY if every dose the same our world will be a paradise So please do something simple for the world and forward this to others ( I meant you as the reader off this note to ) if emailling to the president is to hard for you atleast pass this message on.. iam so happy today iam so happy today iam so happy today iam so happy today iam so happy today iam so happy today iam so happy today iam so happy today iam so happy today iam so happy today iam so happy today iam so happy today iam so happy today iam so happy today iam so happy today iam so happy today iam so happy today iam so happy today iam so happy today iam so happy today iam so happy today iam so happy today iam so happy today iam so happy today iam so happy today iam so happy today iam so happy today iam so happy today iam so happy today iam so happy today iam so happy today iam so happy today iam so happy today iam so happy today iam so happy today iam so happy today iam so happy today iam so happy today iam so happy today iam so happy today iam so happy today iam so happy today iam so happy today iam so happy today iam so happy today iam so happy today iam so happy today iam so happy today iam so happy today iam so happy today iam so happy today iam so happy today iam so happy today iam so happy today iam so happy today iam so happy today
Bug#733432: marked as done (libcommons-lang3-java: FTBFS: Failed tests)
Your message dated Tue, 31 Dec 2013 05:48:27 +
with message-id e1vxsbn-0002kk...@franck.debian.org
and subject line Bug#733432: fixed in libcommons-lang3-java 3.1-2
has caused the Debian Bug report #733432,
regarding libcommons-lang3-java: FTBFS: Failed tests
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.)
--
733432: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=733432
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Source: libcommons-lang3-java
Version: 3.1-1
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20131226 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part (hopefully):
debian/rules build
test -x debian/rules
mkdir -p .
/usr/share/maven-debian-helper/copy-repo.sh /«PKGBUILDDIR»/debian
skip faking of existing gnu-getopt:getopt::debian
mh_patchpoms -plibcommons-lang3-java --debian-build --keep-pom-version
--maven-repo=/«PKGBUILDDIR»/debian/maven-repo
touch debian/stamp-poms-patched
# before-build target may be used to unpatch the pom files, so we need to
check if
# patching the pom files is needed here, normally not
if [ ! -f pom.xml.save ]; then \
/usr/bin/make -f debian/rules patch-poms; \
fi
cd . /usr/lib/jvm/default-java/bin/java -noverify -cp
/usr/share/maven2/boot/classworlds.jar:/usr/lib/jvm/default-java/lib/tools.jar
-Dproperties.file.manual=/«PKGBUILDDIR»/debian/maven.properties
-Dclassworlds.conf=/etc/maven2/m2-debian.conf
org.codehaus.classworlds.Launcher -s/etc/maven2/settings-debian.xml
-Dmaven.repo.local=/«PKGBUILDDIR»/debian/maven-repo package
[INFO]
NOTE: Maven is executing in offline mode. Any artifacts not already in your
local
repository will be inaccessible.
[INFO] Scanning for projects...
[INFO]
[INFO] Building Commons Lang
[INFO]task-segment: [package]
[INFO]
[INFO] [resources:resources {execution: default-resources}]
[INFO] Using 'ISO-8859-1' encoding to copy filtered resources.
[INFO] Copying 1 resource
[WARNING] POM for
'org.codehaus.plexus:plexus-compiler-api:pom:debian:runtime' is invalid.
Its dependencies (if any) will NOT be available to the current build.
[WARNING] POM for
'org.codehaus.plexus:plexus-compiler-javac:pom:debian:runtime' is invalid.
Its dependencies (if any) will NOT be available to the current build.
[INFO] [compiler:compile {execution: default-compile}]
[INFO] Compiling 99 source files to /«PKGBUILDDIR»/target/classes
[INFO] [resources:testResources {execution: default-testResources}]
[INFO] Using 'ISO-8859-1' encoding to copy filtered resources.
[INFO] Copying 2 resources
[INFO] [compiler:testCompile {execution: default-testCompile}]
[INFO] Compiling 119 source files to /«PKGBUILDDIR»/target/test-classes
[INFO] [surefire:test {execution: default-test}]
[INFO] Surefire report directory: /«PKGBUILDDIR»/target/surefire-reports
---
T E S T S
---
Running org.apache.commons.lang3.ArrayUtilsTest
Tests run: 146, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.372 sec
Running org.apache.commons.lang3.CharRangeTest
Tests run: 16, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.107 sec
Running org.apache.commons.lang3.CharEncodingTest
Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.137 sec
Running org.apache.commons.lang3.ArrayUtilsRemoveMultipleTest
Tests run: 55, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.11 sec
Running org.apache.commons.lang3.StringUtilsTrimEmptyTest
Tests run: 15, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.128 sec
Running org.apache.commons.lang3.StringEscapeUtilsTest
Tests run: 23, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.743 sec
Running org.apache.commons.lang3.StringUtilsEqualsIndexOfTest
Tests run: 47, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.057 sec
Running org.apache.commons.lang3.CharSetUtilsTest
Tests run: 9, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.012 sec
Running org.apache.commons.lang3.EnumUtilsTest
Tests run: 20, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.029 sec
Running org.apache.commons.lang3.StringUtilsStartsEndsWithTest
Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.012 sec
Running
Processed: Re: [Pkg-systemd-maintainers] Bug#733240: systemd-sysv: new sysvinit-core breaks systemd-sysv
Processing control commands: tags -1 + pending Bug #733240 [systemd-sysv] systemd-sysv: new sysvinit-core breaks systemd-sysv Added tag(s) pending. -- 733240: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=733240 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#733240: [Pkg-systemd-maintainers] Bug#733240: systemd-sysv: new sysvinit-core breaks systemd-sysv
control: tags -1 + pending Hi Alf, Thanks for your report and patch. I have pushed this with commit http://anonscm.debian.org/gitweb/?p=pkg-systemd/systemd.git;a=commitdiff;h=d0f6dd2 We’ll upload a new version of systemd soon. -- Best regards, Michael -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#733440: golang-gocheck: FTBFS: Tests failed
Hi Sergio, Sergio Schvezov sergio.schve...@canonical.com writes: I'm new to package uploads, but this should fix it: http://anonscm.debian.org/gitweb/?p=pkg-go/packages/golang-gocheck.git;a=commit;h=4a1acc55fc6e1ea3b1783129bf4955e72f0bea80 Michael or David do you mind reviewing/sponsoring? I allowed myself to fix the missing “Closes:” in d/changelog myself: http://anonscm.debian.org/gitweb/?p=pkg-go/packages/golang-gocheck.git;a=commitdiff;h=c3cd77c So please git pull before you do any work in order to avoid merge conflicts. The new version is uploaded. -- Best regards, Michael -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#733440: marked as done (golang-gocheck: FTBFS: Tests failed)
Your message dated Tue, 31 Dec 2013 06:33:31 + with message-id e1vxstp-0001jc...@franck.debian.org and subject line Bug#733440: fixed in golang-gocheck 0.0~bzr20131118+85-2 has caused the Debian Bug report #733440, regarding golang-gocheck: FTBFS: Tests failed 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.) -- 733440: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=733440 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: golang-gocheck Version: 0.0~bzr20131118+85-1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20131226 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): debian/rules build dh build --buildsystem=golang --with=golang dh_testdir -O--buildsystem=golang dh_auto_configure -O--buildsystem=golang dh_auto_build -O--buildsystem=golang launchpad.net/gocheck dh_auto_test -O--buildsystem=golang === RUN Test -- FAIL: fixture_test.go:126: FixtureS.TestPanicOnSetUpSuite fixture_test.go:145: c.Check(output.value, Matches, expected) ... value string = + ... \n + ... --\n + ... PANIC: gocheck_test.go:119: FixtureHelper.SetUpSuite\n + ... \n + ... ... Panic: SetUpSuite (PC=0x413786)\n + ... \n + ... /usr/lib/go/src/pkg/runtime/panic.c:248\n + ... in panic\n + ... gocheck_test.go:109\n + ... in FixtureHelper.trace\n + ... gocheck_test.go:120\n + ... in FixtureHelper.SetUpSuite\n + ... /usr/lib/go/src/pkg/runtime/asm_amd64.s:338\n + ... in call16\n ... regex string = + ... ^\n + ... -+\n + ... PANIC: gocheck_test\\.go:[0-9]+: FixtureHelper.SetUpSuite\n + ... \n + ... \\.\\.\\. Panic: SetUpSuite \\(PC=[xA-F0-9]+\\)\n + ... \n + ... .+:[0-9]+\n + ... in panic\n + ... .*gocheck_test.go:[0-9]+\n + ... in FixtureHelper.trace\n + ... .*gocheck_test.go:[0-9]+\n + ... in FixtureHelper.SetUpSuite\n + ... $ -- FAIL: fixture_test.go:67: FixtureS.TestPanicOnSetUpTest fixture_test.go:93: c.Check(output.value, Matches, expected) ... value string = + ... \n + ... --\n + ... PANIC: gocheck_test.go:127: FixtureHelper.SetUpTest\n + ... \n + ... ... Panic: SetUpTest (PC=0x413786)\n + ... \n + ... /usr/lib/go/src/pkg/runtime/panic.c:248\n + ... in panic\n + ... gocheck_test.go:109\n + ... in FixtureHelper.trace\n + ... gocheck_test.go:128\n + ... in FixtureHelper.SetUpTest\n + ... /usr/lib/go/src/pkg/runtime/asm_amd64.s:338\n + ... in call16\n + ... \n + ... --\n + ... PANIC: gocheck_test.go:135: FixtureHelper.Test1\n + ... \n + ... ... Panic: Fixture has panicked (see related PANIC)\n ... regex string = + ... ^\n + ... -+\n + ... PANIC: gocheck_test\\.go:[0-9]+: FixtureHelper\\.SetUpTest\n + ... \n + ... \\.\\.\\. Panic: SetUpTest \\(PC=[xA-F0-9]+\\)\n + ... \n + ... .+:[0-9]+\n + ... in panic\n + ... .*gocheck_test.go:[0-9]+\n + ... in FixtureHelper.trace\n + ... .*gocheck_test.go:[0-9]+\n + ... in FixtureHelper.SetUpTest\n + ... \n + ... -+\n + ... PANIC: gocheck_test\\.go:[0-9]+: FixtureHelper\\.Test1\n + ... \n + ... \\.\\.\\. Panic: Fixture has panicked \\(see related PANIC\\)\n + ... $ -- FAIL: fixture_test.go:148: FixtureS.TestPanicOnTearDownSuite fixture_test.go:173: c.Check(output.value, Matches, expected) ... value string = + ... \n + ... --\n + ... PANIC: gocheck_test.go:123: FixtureHelper.TearDownSuite\n + ... \n + ... ... Panic: TearDownSuite (PC=0x413786)\n + ... \n + ... /usr/lib/go/src/pkg/runtime/panic.c:248\n + ... in panic\n + ... gocheck_test.go:109\n + ... in FixtureHelper.trace\n + ... gocheck_test.go:124\n + ... in FixtureHelper.TearDownSuite\n + ...
Processed: Re: Bug#733330: call to __builtin___strncpy_chk will always overflow destination buffer [enabled by default]
Processing control commands: tag -1 fixed-upstream Bug #70 [refdb] call to __builtin___strncpy_chk will always overflow destination buffer [enabled by default] Added tag(s) fixed-upstream. -- 70: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=70 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#713612: vdpau-video: FTBFS: utils_glx.h:163:5: error: unknown type name 'PFNGLMULTITEXCOORD2FPROC'
Package: vdpau-video Version: 0.7.3-2 Followup-For: Bug #713612 I know debian-multimedia.org is persona non grata in some portions of the debian circle, but they do have patches for this (and other FTBFS problems) in vdpau-video-dmo 0.7.4-dmo1. The dmo patches for 0.7.4 apply cleanly to the debian 0.7.3-2 source package, and allowed me to build it from source properly. -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.11-2-amd64 (SMP w/12 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: unarchiving 698231, found 698231 in 1.4.5-1
Processing commands for cont...@bugs.debian.org:
unarchive 698231
Bug #698231 {Done: Salvatore Bonaccorso car...@debian.org} [memcached]
memcached: CVE-2013-0179
Unarchived Bug 698231
found 698231 1.4.5-1
Bug #698231 {Done: Salvatore Bonaccorso car...@debian.org} [memcached]
memcached: CVE-2013-0179
Marked as found in versions memcached/1.4.5-1.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
698231: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=698231
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#733330: call to __builtin___strncpy_chk will always overflow destination buffer [enabled by default]
Control: tag -1 fixed-upstream -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
