Bug#779288: marked as done (upgrade-system: cronjob still active after package was removed (but not purged))
Your message dated Fri, 27 Feb 2015 05:49:07 + with message-id e1yrdnp-0001s2...@franck.debian.org and subject line Bug#779288: fixed in upgrade-system 1.7.2.2 has caused the Debian Bug report #779288, regarding upgrade-system: cronjob still active after package was removed (but not purged) 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.) -- 779288: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=779288 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: upgrade-system Version: 1.7.2.1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package includes a cronjob that is still active after removing (but not purging) the package. The cronjob needs to have a test that skips its execution after removal, e.g. start with # skip cronjob if upgrade-system is no longer installed test -x /usr/sbin/upgrade-system || exit 0 I noticed this because I have apt-get configured to produce more debug output and suddenly the cronjob started emitting such even after package removal. Andreas ---End Message--- ---BeginMessage--- Source: upgrade-system Source-Version: 1.7.2.2 We believe that the bug you reported is fixed in the latest version of upgrade-system, 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 779...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Martin-Éric Racine martin-eric.rac...@iki.fi (supplier of updated upgrade-system 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: Thu, 26 Feb 2015 18:20:39 +0200 Source: upgrade-system Binary: upgrade-system Architecture: source all Version: 1.7.2.2 Distribution: unstable Urgency: medium Maintainer: Martin-Éric Racine martin-eric.rac...@iki.fi Changed-By: Martin-Éric Racine martin-eric.rac...@iki.fi Description: upgrade-system - command for upgrading and sanitizing a Debian system Closes: 779288 Changes: upgrade-system (1.7.2.2) unstable; urgency=medium . * debian/upgrade-system.cron.daily: + Added test -x /usr/sbin/upgrade-system || exit 0 (Closes: #779288). Thanks to Andreas Beckmann for the report and the solution. Checksums-Sha1: 798ce138233ae5c52d55103a9878b658003b08dc 1478 upgrade-system_1.7.2.2.dsc 439908ada6cce265b13abf840e1f514a51036f90 12472 upgrade-system_1.7.2.2.tar.xz 035d610c876da61bc7bdc98cac12b9b785bbc8c3 15726 upgrade-system_1.7.2.2_all.deb Checksums-Sha256: 7b6d1c2f9f0cd98905bb07fae5f191d2bf6a405bfb42f1fb4120c9c8b44a5320 1478 upgrade-system_1.7.2.2.dsc 0500d4788910c0418fc4a78f3c8012e86debb63c209a1cd6d927372a90e7 12472 upgrade-system_1.7.2.2.tar.xz 1823704dac06b4c7dd5762a89512236b4884dd43eaab3c6bc5742584f262d181 15726 upgrade-system_1.7.2.2_all.deb Files: 94bf8dde8914a3ca4823f18489a29e97 1478 admin optional upgrade-system_1.7.2.2.dsc afba9ab9b2f645ab1c74fbe3665dc976 12472 admin optional upgrade-system_1.7.2.2.tar.xz 304c6d2e439928c112e34b07c2bb1a6e 15726 admin optional upgrade-system_1.7.2.2_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJU8AIfAAoJENFO8V2v4RNH1TwP/2Z67OGpqFu+8zfmSQBiVMNh p18hd7bEaIB94wS0k/chhjwCLao1napekhJRX+hc6P564TuLo9nMp3UwjED5YNt2 ZhFiuyeo4Ep3hM+C+ePPfazssCw7Exfzvc1msW32r3B0ZSpYDRyWVZesEMxfaCAu +qTPkXmiKZev3JwRs0J5gMLQjdttjrsmj4UfNG9apRmgYvRAwZU03VCm6MOfVKwi k3uvJTMoydYnso9LivXUcdJ31nvNOkR2XOflidc+R6zA5D0mhx8ljPjFhEHbvd+l 1U9CDI/w0izTaOnjygtK2Cp3DOQph3dNf8C1Xl/x4elyk7v4PCsd2sN5QuEaY18F qbkO/poDpcNIMB3p0ZdE4jQZeAJuZEB/MFbY29nBpNVhq4EdpC+MW+8RtMikR5+t Ys2sN8hs8Hadk1zC4Cm1sLh2+TRrXQXyNqOLV9s1R6sXID6XdGbsJozsl4la6aRK OlsuiK92zbY3m0I0W4DeC6kGUPXBi1Ev/6fz/rPkyNy6S/DNCUI6Rf936+YGxmZM X/eb4EpvYSx6lxcw0J/uJQ16klxuIAD3XfCCoiVziTS6Pwfkm0tcj58tlLpHnZ4y cZGWjRJLSIZuLx4Ye4fytpNGWlZJkh3L7bZddWyz+hMACNjlBSnQYV+x1x/1iQMK xlr46pTFwLbhJkpv7LjY =E/jR -END PGP SIGNATUREEnd Message---
Processed: fixed 762700 in 217-1
Processing commands for cont...@bugs.debian.org: fixed 762700 217-1 Bug #762700 [systemd] systemd: journald fails to forward some messages to syslog Marked as fixed in versions systemd/217-1. thanks Stopping processing here. Please contact me if you need assistance. -- 762700: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762700 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: notfixed 762700 in 217-1
Processing commands for cont...@bugs.debian.org: notfixed 762700 217-1 Bug #762700 [systemd] systemd: journald fails to forward some messages to syslog No longer marked as fixed in versions systemd/217-1. thanks Stopping processing here. Please contact me if you need assistance. -- 762700: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762700 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#779115: marked as done (polygen-data: depend on perl instead of perl-modules)
Your message dated Thu, 26 Feb 2015 16:49:42 + with message-id e1yr1d8-0001sy...@franck.debian.org and subject line Bug#779115: fixed in polygen 1.0.6.ds2-13.1 has caused the Debian Bug report #779115, regarding polygen-data: depend on perl instead of perl-modules 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.) -- 779115: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=779115 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: polygen-data Version: 1.0.6.ds2-13 Severity: serious Justification: blocks another serious bug According to the package description of perl-modules, other packages should not depend on it, since it is considered an internal implementation detail of the perl package. At present we are dealing with an RC bug[1] in perl which is exacerbated by such dependencies. As such, please could you replace Depends: perl-modules with Depends: perl NMUs will be forthcoming; feel free to let me know whether you prefer to handle this as a maintainer upload or not. Thanks, Dominic. [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777597#32 ---End Message--- ---BeginMessage--- Source: polygen Source-Version: 1.0.6.ds2-13.1 We believe that the bug you reported is fixed in the latest version of polygen, 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 779...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. gregor herrmann gre...@debian.org (supplier of updated polygen 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: SHA512 Format: 1.8 Date: Wed, 25 Feb 2015 22:13:25 +0100 Source: polygen Binary: polygen polygen-data Architecture: source all Version: 1.0.6.ds2-13.1 Distribution: unstable Urgency: medium Maintainer: Debian OCaml Maintainers debian-ocaml-ma...@lists.debian.org Changed-By: gregor herrmann gre...@debian.org Description: polygen- generator of random sentences from grammar definitions polygen-data - grammar definitions for PolyGen Closes: 779115 Changes: polygen (1.0.6.ds2-13.1) unstable; urgency=medium . * Non-maintainer upload. * Fix depend on perl instead of perl-modules: debian/control: update Depends for polygen-data. (Closes: #779115) Checksums-Sha1: ff976ee41a0329afca838f7a4c5196a4c5d1593c 2176 polygen_1.0.6.ds2-13.1.dsc dda7f00befbcfdb90c7339f8ad48f47cc999cc11 11485 polygen_1.0.6.ds2-13.1.diff.gz b3175fca95f08e5cff45293920b976b9812a 79464 polygen_1.0.6.ds2-13.1_all.deb da7b8a9e401f79cd607138ae9705f5d69c3b7012 1178996 polygen-data_1.0.6.ds2-13.1_all.deb Checksums-Sha256: 90c84ecceac85e4378a1a8a626c46be414040d0df812ce8ad2cfcee702a9a7fa 2176 polygen_1.0.6.ds2-13.1.dsc 35ef4c8dcaaab3bde055e4fd919c54f5d288fff1d191e220e88c3ac1301e264a 11485 polygen_1.0.6.ds2-13.1.diff.gz 0c281288665485c57d0461c49720ad98bb507d859e24c0e0f1371684a923c1e7 79464 polygen_1.0.6.ds2-13.1_all.deb b97f37aeac25dfcf1c72b58c5942e0cbf7b4002888695c0c27981fde97160e36 1178996 polygen-data_1.0.6.ds2-13.1_all.deb Files: 46882eec290e014dae8613edb4424983 2176 games optional polygen_1.0.6.ds2-13.1.dsc 4a2161d33e935bb0d1e6e6982bb4e938 11485 games optional polygen_1.0.6.ds2-13.1.diff.gz 017600b1354ec825cfb4e7e913cf4a09 79464 games optional polygen_1.0.6.ds2-13.1_all.deb 28d79ced6608aa6509b319b608c6bfb4 1178996 games optional polygen-data_1.0.6.ds2-13.1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQJ8BAEBCgBmBQJU7jurXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXREMUUxMzE2RTkzQTc2MEE4MTA0RDg1RkFC QjNBNjgwMTg2NDlBQTA2AAoJELs6aAGGSaoGGcEP/RIif62UCtBkzHsbgJBYVleP jYm1TWNSXmAwxEhR6Qk6NpKUwrCUvqvD+yvix8sEoK2zgwGawwyH9F0F3ZieZkGw UjHUT/oxo5am94NBEZ6gsKucqOeykZ0SZ+pnbDq5nUgzmlLWa6FGtvH08e9ZCELb 3ga4j7OLL1mskxH6p0oow9ecuhzsfVQ+vWfILpc2uvSO8+EC8Ovm8qAW5JjOdw7G N6ldWkfS98/0NQmoX1HisbM53guCW5iYSidOiIK/LowAJ/WHDPYwMW6IGt9FUoQC abbRNTuF70bhbrtGJMlHv3fjaGndb5DilZW7/BfEl7HOeZPR4DM2dBl2RVF+YSX4 wdkaA2ew2mRZxpUzhQhbP2cuCRXxrIb5IRRAtkUtS+FDlwqBqrc7VAXhkfNzxRY3 akqKIkyGLLapUq3+JSaKcnUH1VYVnxj7q1BjwkCd7eFYpngSdQly0maYhsuzk+y8 0v3B7/ccGqHgpg14oAKeYD8eh/O3/3dj7rJbpIhXeKYAp9hxNENZ8Nu5vHwTnRXy ozISlm75649E6iftHOViESyq/xIm3xQCmOEIyAG9q+AJ+VmNyJt+lJ81BlvVBL6A
Processed: [bts-link] source package src:libqmi
Processing commands for cont...@bugs.debian.org: # # bts-link upstream status pull for source package src:libqmi # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # user bts-link-upstr...@lists.alioth.debian.org Setting user to bts-link-upstr...@lists.alioth.debian.org (was bts-link-de...@lists.alioth.debian.org). # remote status report for #778346 (http://bugs.debian.org/778346) # Bug title: FTBFS: test suite failures on big-endian systems # * https://bugs.freedesktop.org/show_bug.cgi?id=89140 # * remote status changed: NEW - RESOLVED # * remote resolution changed: (?) - FIXED # * closed upstream tags 778346 + fixed-upstream Bug #778346 [src:libqmi] FTBFS: test suite failures on big-endian systems Added tag(s) fixed-upstream. usertags 778346 - status-NEW Usertags were: status-NEW. Usertags are now: . usertags 778346 + status-RESOLVED resolution-FIXED There were no usertags set. Usertags are now: status-RESOLVED resolution-FIXED. thanks Stopping processing here. Please contact me if you need assistance. -- 778346: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=778346 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#779115: polygen: diff for NMU version 1.0.6.ds2-13.1
On Thu, 26 Feb 2015 10:43:14 +0100, Mehdi Dogguy wrote: I've prepared an NMU for polygen (versioned as 1.0.6.ds2-13.1) and uploaded it to DELAYED/6. Please feel free to tell me if I should delay it longer. Thanks for your upload! Feel free to reschedule it in DELAYED/0. Thanks! Rescheduled. Cheers, gregor -- .''`. Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06 : :' : Debian GNU/Linux user, admin, and developer - https://www.debian.org/ `. `' Member of VIBE!AT SPI, fellow of the Free Software Foundation Europe `- NP: U2: If God Would Send His Angels signature.asc Description: Digital Signature
Bug#779288: upgrade-system: cronjob still active after package was removed (but not purged)
Package: upgrade-system Version: 1.7.2.1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package includes a cronjob that is still active after removing (but not purging) the package. The cronjob needs to have a test that skips its execution after removal, e.g. start with # skip cronjob if upgrade-system is no longer installed test -x /usr/sbin/upgrade-system || exit 0 I noticed this because I have apt-get configured to produce more debug output and suddenly the cronjob started emitting such even after package removal. Andreas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: your mail
Processing commands for cont...@bugs.debian.org: severity 713016 serious Bug #713016 [dvd+rw-tools] dvd+rw-tools: Burning to previously blank BD-R ends by error message CLOSE SESSION failed Severity set to 'serious' from 'normal' End of message, stopping processing here. Please contact me if you need assistance. -- 713016: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=713016 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#779288: upgrade-system: cronjob still active after package was removed (but not purged)
2015-02-26 18:12 GMT+02:00 Andreas Beckmann a...@debian.org: Package: upgrade-system Version: 1.7.2.1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package includes a cronjob that is still active after removing (but not purging) the package. The cronjob needs to have a test that skips its execution after removal, e.g. start with # skip cronjob if upgrade-system is no longer installed test -x /usr/sbin/upgrade-system || exit 0 I noticed this because I have apt-get configured to produce more debug output and suddenly the cronjob started emitting such even after package removal. Thanks for the info and the solution. That's easily added. I'll fix this now and upload. Martin-Éric -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: [bts-link] source package src:lnav
Processing commands for cont...@bugs.debian.org: # # bts-link upstream status pull for source package src:lnav # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # user bts-link-upstr...@lists.alioth.debian.org Setting user to bts-link-upstr...@lists.alioth.debian.org (was bts-link-de...@lists.alioth.debian.org). # remote status report for #771203 (http://bugs.debian.org/771203) # Bug title: lnav: FTBFS on mips, powerpc and s390x # * https://github.com/tstack/lnav/issues/123 # * remote status changed: open - closed # * closed upstream tags 771203 + fixed-upstream Bug #771203 [src:lnav] lnav: FTBFS on mips, powerpc and s390x Added tag(s) fixed-upstream. usertags 771203 - status-open Usertags were: status-open. Usertags are now: . usertags 771203 + status-closed There were no usertags set. Usertags are now: status-closed. thanks Stopping processing here. Please contact me if you need assistance. -- 771203: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771203 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: libgps22: fails to upgrade from 'sid' - trying to overwrite /usr/lib/x86_64-linux-gnu/libgpsd.so.22.0.0
Processing control commands: affects -1 + libgps-dev gpsd-clients gpsd-debug gpsd Bug #779286 [libgps22] libgps22: fails to upgrade from 'sid' - trying to overwrite /usr/lib/x86_64-linux-gnu/libgpsd.so.22.0.0 Added indication that 779286 affects libgps-dev, gpsd-clients, gpsd-debug, and gpsd -- 779286: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=779286 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: bug 779274 is forwarded to https://github.com/kohler/t1utils/issues/4
Processing commands for cont...@bugs.debian.org: forwarded 779274 https://github.com/kohler/t1utils/issues/4 Bug #779274 [t1utils] t1disasm: buffer overflow in set_cs_start Set Bug forwarded-to-address to 'https://github.com/kohler/t1utils/issues/4'. thanks Stopping processing here. Please contact me if you need assistance. -- 779274: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=779274 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#779286: libgps22: fails to upgrade from 'sid' - trying to overwrite /usr/lib/x86_64-linux-gnu/libgpsd.so.22.0.0
Package: libgps22 Version: 3.12-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Control: affects -1 + libgps-dev gpsd-clients gpsd-debug gpsd Hi, during a test with piuparts I noticed your package fails to upgrade from 'sid' to 'experimental'. It installed fine in 'sid', then the upgrade to 'experimental' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces From the attached log (scroll to the bottom...): Selecting previously unselected package libgps22:amd64. (Reading database ... (Reading database ... 7533 files and directories currently installed.) Preparing to unpack .../libgps22_3.12-1_amd64.deb ... Unpacking libgps22:amd64 (3.12-1) ... dpkg: error processing archive /var/cache/apt/archives/libgps22_3.12-1_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/libgpsd.so.22.0.0', which is also in package libgps21:amd64 3.11-3 dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) Which means that libgps21 already shipped a library with the from SONAME in sid ... cheers, Andreas libgps-dev_3.12-1.log.gz Description: application/gzip
Processed: tagging 771203
Processing commands for cont...@bugs.debian.org: tags 771203 + pending Bug #771203 [src:lnav] lnav: FTBFS on mips, powerpc and s390x Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 771203: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771203 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#736033: marked as done (please build-depend on libtiff-dev, not libtiff4-dev)
Your message dated Thu, 26 Feb 2015 17:56:48 + with message-id e1yr2g4-0002yn...@franck.debian.org and subject line Bug#779144: Removed package(s) from unstable has caused the Debian Bug report #736033, regarding please build-depend on libtiff-dev, not libtiff4-dev to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 736033: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=736033 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: ocropus Version: 0.3.1-4 Version: 0.4.4-1 User: q...@debian.org Usertags: libtiff4-dev The libtiff4-dev package is a transitional package that is going to disappear soon. Please update your build dependency from libtiff4-dev to libtiff-dev. ---End Message--- ---BeginMessage--- Version: 0.3.1-4+rm Dear submitter, as the package ocropus has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/779144 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)---End Message---
Bug#669557: marked as done (ocropus: FTBFS: configure: error: Could not find tesseract! Choose --without-tesseract if you do not want to use it.)
Your message dated Thu, 26 Feb 2015 17:56:48 + with message-id e1yr2g4-0002yn...@franck.debian.org and subject line Bug#779144: Removed package(s) from unstable has caused the Debian Bug report #669557, regarding ocropus: FTBFS: configure: error: Could not find tesseract! Choose --without-tesseract if you do not want to use it. 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.) -- 669557: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=669557 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: ocropus Version: 0.3.1-4 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120419 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: make[1]: Entering directory `/«PKGBUILDDIR»' AUTOMAKE=automake-1.9 ACLOCAL=aclocal-1.9 autoreconf -ivf autoreconf: Entering directory `.' autoreconf: configure.ac: not using Gettext autoreconf: running: aclocal-1.9 --force autoreconf: configure.ac: tracing autoreconf: configure.ac: not using Libtool autoreconf: running: /usr/bin/autoconf --force autoreconf: configure.ac: not using Autoheader autoreconf: running: automake-1.9 --add-missing --copy --force-missing Useless use of /d modifier in transliteration operator at /usr/share/automake-1.9/Automake/Wrap.pm line 60. autoreconf: Leaving directory `.' ./configure --prefix=/usr --with-iulib=/usr --without-fst --without-leptonica --with-tesseract=/usr checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for gawk... no checking for mawk... mawk checking whether make sets $(MAKE)... yes checking for /usr/include/iulib/imgio.h... yes checking for g++... g++ checking whether the C++ compiler works... yes checking for C++ compiler default output file name... a.out checking for suffix of executables... checking whether we are cross compiling... no checking for suffix of object files... o checking whether we are using the GNU C++ compiler... yes checking whether g++ accepts -g... yes checking for style of include used by make... GNU checking dependency style of g++... gcc3 checking for gcc... gcc checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ISO C89... none needed checking dependency style of gcc... gcc3 checking for ranlib... ranlib checking how to run the C preprocessor... gcc -E checking for grep that handles long lines and -e... /bin/grep checking for egrep... /bin/grep -E checking for ANSI C header files... yes checking for sys/wait.h that is POSIX.1 compatible... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking float.h usability... yes checking float.h presence... yes checking for float.h... yes checking malloc.h usability... yes checking malloc.h presence... yes checking for malloc.h... yes checking for stdint.h... (cached) yes checking for stdlib.h... (cached) yes checking for string.h... (cached) yes checking for unistd.h... (cached) yes checking wchar.h usability... yes checking wchar.h presence... yes checking for wchar.h... yes checking for unistd.h... (cached) yes checking for compress in -lz... yes checking png.h usability... yes checking png.h presence... yes checking for png.h... yes checking for png_sig_cmp in -lpng... yes checking jpeglib.h usability... yes checking jpeglib.h presence... yes checking for jpeglib.h... yes checking for jpeg_std_error in -ljpeg... yes checking for TIFFOpen in -ltiff... yes checking for exit in -liulib... yes checking for pthread_create in -lpthread... yes configure: error: Could not find tesseract! Choose --without-tesseract if you do not want to use it. checking for err_exit in -ltesseract_full... no make[1]: *** [override_dh_auto_configure] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2012/04/19/ocropus_0.3.1-4_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 about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems.
Bug#659597: marked as done (ocropus build-depends on obsolete tesseract-ocr-dev)
Your message dated Thu, 26 Feb 2015 17:56:48 + with message-id e1yr2g4-0002yn...@franck.debian.org and subject line Bug#779144: Removed package(s) from unstable has caused the Debian Bug report #659597, regarding ocropus build-depends on obsolete tesseract-ocr-dev to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 659597: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=659597 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: ocropus Version: 0.3.1-4 Severity: serious tesseract-ocr-dev is no longer built on top of tesseract source package, and is planned to be decrufted from the archive. Please replace tesseract-ocr-dev build-dependency with libtesseract-dev. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-1-amd64 (SMP w/8 CPU cores) Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash ---End Message--- ---BeginMessage--- Version: 0.3.1-4+rm Dear submitter, as the package ocropus has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/779144 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)---End Message---
Bug#779294: /usr/bin/python: /lib/i386-linux-gnu/libc.so.6: version `GLIBC_2.15' not found (required by /usr/bin/python)
On 02/26/2015 06:01 PM, Andreas Beckmann wrote: during a test with piuparts I noticed a failure to upgrade from 'wheezy'. I'm not exactly sure which package to blame. This happened on i386, I cannot reproduce it on amd64. The package being tested was lsb-desktop, but it can probably show up elsewhere as well. From the attached log (scroll to the bottom...): (Reading database ... 18847 files and directories currently installed.) Preparing to replace libpython2.7 2.7.3-6+deb7u2 (using .../libpython2.7_2.7.8-11_i386.deb) ... Unpacking replacement libpython2.7:i386 ... Preparing to replace python2.7 2.7.3-6+deb7u2 (using .../python2.7_2.7.8-11_i386.deb) ... Unpacking replacement python2.7 ... Preparing to replace python2.7-minimal 2.7.3-6+deb7u2 (using .../python2.7-minimal_2.7.8-11_i386.deb) ... Unpacking replacement python2.7-minimal ... dpkg: warning: unable to delete old directory '/etc/python2.7': Directory not empty Selecting previously unselected package libpython2.7-minimal:i386. Unpacking libpython2.7-minimal:i386 (from .../libpython2.7-minimal_2.7.8-11_i386.deb) ... Preparing to replace debconf 1.5.49 (using .../debconf_1.5.55_all.deb) ... /usr/bin/python: /lib/i386-linux-gnu/libc.so.6: version `GLIBC_2.15' not found (required by /usr/bin/python) dpkg: warning: subprocess old pre-removal script returned error exit status 1 dpkg: trying script from the new package instead ... /usr/bin/python: /lib/i386-linux-gnu/libc.so.6: version `GLIBC_2.15' not found (required by /usr/bin/python) dpkg: error processing /var/cache/apt/archives/debconf_1.5.55_all.deb (--unpack): subprocess new pre-removal script returned error exit status 1 /usr/bin/python: /lib/i386-linux-gnu/libc.so.6: version `GLIBC_2.15' not found (required by /usr/bin/python) dpkg: error while cleaning up: subprocess installed post-installation script returned error exit status 1 Processing triggers for man-db ... Errors were encountered while processing: /var/cache/apt/archives/debconf_1.5.55_all.deb This looks a bit like python was unpacked before the new glibc. debconf calls pycompile (and python). It looks like this kind of thing can happen with any binary which needs the new glibc, and in this case it hits python. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#724424: marked as done (Please stop build depending on automake1.9)
Your message dated Thu, 26 Feb 2015 17:56:48 + with message-id e1yr2g4-0002yn...@franck.debian.org and subject line Bug#779144: Removed package(s) from unstable has caused the Debian Bug report #724424, regarding Please stop build depending on automake1.9 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.) -- 724424: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=724424 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: ocropus Version: 0.3.1-4 Severity: wishlist Usertags: automake-cleanup-2013 As documented in http://lists.debian.org/debian-devel/2013/05/msg01459.html, I will be removing automake1.4, automake1.9 and automake1.10 from the archive. Your package has a build dependency on one (or more) of these packages. In many cases these dependencies are unnecessary as there is typically no build time dependency on automake for most packages. If it is required, you should update the dependency to automake or automake1.11. If you need any assistance with making your package work with a newer version of automake, please let me know, but it should be relatively painless for the most part. I plan to ask for the removal of automake1.4, automake1.9 and automake1.10 in approximately one month. Once they removed this bug's severity will be upgraded to serious. ---End Message--- ---BeginMessage--- Version: 0.3.1-4+rm Dear submitter, as the package ocropus has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/779144 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)---End Message---
Bug#779274: t1disasm: buffer overflow in set_cs_start
* Jakub Wilk jw...@debian.org, 2015-02-26, 12:32: $ t1asm crash.raw crash.pfb t1asm: warning: no charstrings found in input file Now with crash.pfb also attached. -- Jakub Wilk crash.pfb Description: application/font
Bug#725284: hdparm + systemd: Patch to restore configuration after resume
Hi, I just uploaded 9.43-2 with the patch mentioned in this bug report. However, I lack the hardware to test hdparm. So please test it before I file an unblock request. This doesn't seem to work: After suspend-resume, my disk behaves as if hdparm was not run at all. I did not yet investigate further. Everything worked fine with using a systemd unit that triggers the hdparm hook after resume. Kind regards, Ralf -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#779308: Gramps: Upgrade to Python 3 Gramps causing multiple serious database errors
Package: gramps Version: 4.1.1~dfsg-2 Severity: serious Tags: pending Hi, I have been made aware of several upstream bugs that render Gramps unusable for users that have special characters in their database (i.e. languages other than English). For example: https://gramps-project.org/bugs/view.php?id=8134 https://gramps-project.org/bugs/view.php?id=8258 https://gramps-project.org/bugs/view.php?id=8357 https://gramps-project.org/bugs/view.php?id=8360 https://gramps-project.org/bugs/view.php?id=8117 The bugs occur in Gramps 4.1.1 when users are asked to upgrade their database because of the switch to Python 3. This is the explanation from Nick Hall from the Gramps Project: The database contains a mix of unicode and strings. When a record in python2 format is loaded into python3, unicode gets converted into a str, but the way strings are converted depends on the encoding setting. If bytes is specifies then strings are converted into bytes, otherwise they are also converted to str. By default strings are converted into str using the ASCII encoding. This will cause errors if the strings contain utf-8 encoded unicode. I have cherry picked the commits from upstream that fix the problem, and it should be uploaded soon. Regards, Ross signature.asc Description: OpenPGP digital signature
Bug#779312: freerdp-x11: Segfaults on start 100% of the time
Package: freerdp-x11 Version: 1.1.0~git20140921.1.440916e+dfsg1-3 Severity: grave Justification: renders package unusable This behavior started just recently: xfreerdp -z --plugin cliprdr \ --plugin rdpsnd --data alsa latency:100 -- \ --plugin rdpdr --data disk:w7share:/home/jgoerzen/w7share -- \ --plugin drdynvc --data tsmf:decoder:gstreamer -- \ -u jgoerzen $@ host.example.com --plugin cliprdr - +clipboard Segmentation fault I notice that packages like libxfreerdp-client1.1 and libfreerdp-gdi1.1 and such were recently updated. That is when this all broke. -- System Information: Debian Release: 8.0 APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages freerdp-x11 depends on: ii libc6 2.19-13 ii libfreerdp-cache1.1 1.1.0~git20140921.1.440916e+dfsg1-3 ii libfreerdp-client1.1 1.1.0~git20140921.1.440916e+dfsg1-3 ii libfreerdp-codec1.1 1.1.0~git20140921.1.440916e+dfsg1-3 ii libfreerdp-common1.1.01.1.0~git20140921.1.440916e+dfsg1-3 ii libfreerdp-core1.11.1.0~git20140921.1.440916e+dfsg1-3 ii libfreerdp-crypto1.1 1.1.0~git20140921.1.440916e+dfsg1-3 ii libfreerdp-gdi1.1 1.1.0~git20140921.1.440916e+dfsg1-3 ii libfreerdp-locale1.1 1.1.0~git20140921.1.440916e+dfsg1-3 ii libfreerdp-primitives1.1 1.1.0~git20140921.1.440916e+dfsg1-3 ii libfreerdp-rail1.11.1.0~git20140921.1.440916e+dfsg1-3 ii libfreerdp-utils1.1 1.1.0~git20140921.1.440916e+dfsg1-3 ii libjpeg62-turbo 1:1.3.1-11 ii libssl1.0.0 1.0.1k-1 ii libwinpr-crt0.1 1.1.0~git20140921.1.440916e+dfsg1-3 ii libwinpr-crypto0.11.1.0~git20140921.1.440916e+dfsg1-3 ii libwinpr-dsparse0.1 1.1.0~git20140921.1.440916e+dfsg1-3 ii libwinpr-environment0.1 1.1.0~git20140921.1.440916e+dfsg1-3 ii libwinpr-file0.1 1.1.0~git20140921.1.440916e+dfsg1-3 ii libwinpr-handle0.11.1.0~git20140921.1.440916e+dfsg1-3 ii libwinpr-heap0.1 1.1.0~git20140921.1.440916e+dfsg1-3 ii libwinpr-input0.1 1.1.0~git20140921.1.440916e+dfsg1-3 ii libwinpr-interlocked0.1 1.1.0~git20140921.1.440916e+dfsg1-3 ii libwinpr-library0.1 1.1.0~git20140921.1.440916e+dfsg1-3 ii libwinpr-path0.1 1.1.0~git20140921.1.440916e+dfsg1-3 ii libwinpr-pool0.1 1.1.0~git20140921.1.440916e+dfsg1-3 ii libwinpr-registry0.1 1.1.0~git20140921.1.440916e+dfsg1-3 ii libwinpr-rpc0.1 1.1.0~git20140921.1.440916e+dfsg1-3 ii libwinpr-sspi0.1 1.1.0~git20140921.1.440916e+dfsg1-3 ii libwinpr-synch0.1 1.1.0~git20140921.1.440916e+dfsg1-3 ii libwinpr-sysinfo0.1 1.1.0~git20140921.1.440916e+dfsg1-3 ii libwinpr-thread0.11.1.0~git20140921.1.440916e+dfsg1-3 ii libwinpr-utils0.1 1.1.0~git20140921.1.440916e+dfsg1-3 ii libx11-6 2:1.6.2-3 ii libxcursor1 1:1.1.14-1+b1 ii libxext6 2:1.3.3-1 ii libxfreerdp-client1.1 1.1.0~git20140921.1.440916e+dfsg1-3 ii libxi62:1.7.4-1+b2 ii libxinerama1 2:1.1.3-1+b1 ii libxkbfile1 1:1.0.8-1 ii libxrender1 1:0.9.8-1+b1 ii libxv12:1.0.10-1+b1 ii zlib1g1:1.2.8.dfsg-2+b1 Versions of packages freerdp-x11 recommends: ii libfreerdp-plugins-standard 1.1.0~git20140921.1.440916e+dfsg1-3 freerdp-x11 suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#779296: trimmomatic: directory of adapters missing from package
Processing commands for cont...@bugs.debian.org: severity 779296 serious Bug #779296 [trimmomatic] trimmomatic: directory of adapters missing from package Severity set to 'serious' from 'important' thanks Stopping processing here. Please contact me if you need assistance. -- 779296: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=779296 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#779296: trimmomatic: directory of adapters missing from package
On Thu, Feb 26, 2015 at 4:01 PM Andreas Tille andr...@an3as.eu wrote:
Hi Michael,
On Thu, Feb 26, 2015 at 08:40:22PM +, Michael Crusoe wrote:
End users will expect adapter files to be installed and available. Please
push into Jessie.
OK. I'll bump the severity of this bug to serious.
Regarding the actual bug: Do you have a clue to what directory in the
installed package the adapters need to be moved. It seems they are
relative to the actual working dir and users are supposed to call the
package out of the source tree which is not possible. Any hint about
the correct file system layout (if needed with patches) would be
welcome. I'd like to fix this as soon as possible.
The path to the specific adapter file to use is set by the user via the
ILLUMINACLIP option, so the files can go into any directory;
/usr/share/docs/trimmomatic/examples or /usr/share/trimmomatic come to
mind
Their location should be highlighted in the manual pages and
/usr/share/doc/README.Debian
Since we are using a wrapper anyway I have set this inside the wrapper
and thus do not see any need for README.Debian. If you agree, please
have a look at
https://people.debian.org/~tille/packages/trimmomatic/
and please test the package whether I have interpreted your links
correctly and the package can be uploaded as is. If you could provide
a test using the adapters this would be more than welcome. Our goal
should be tro get at least 80% of our packages autopkgtest-able.
Trimmomatic uses a nonstandard argument parser. ILLUMINACLIP is command
line option, not an environmental variable. Adding `export
ILLUMINACLIP=/usr/share/${ILLUMINACLIP}/adapters` to the wrapper script
will have no effect.
Here is an example command line
TrimmomaticSE --phred33 input.fq.gz output.fq.gz
ILLUMINACLIP:/usr/share/trimmomatic/TruSeq3-SE:2:30:10 LEADING:3 TRAILING:3
SLIDINGWINDOW:4:15 MINLEN:36
However no FASTQ format sequence files are provided in the package so I
can't write a test case.
Kind regards
Andreas.
--
http://fam-tille.de
Bug#779296: trimmomatic: directory of adapters missing from package
Hi Michael,
On Thu, Feb 26, 2015 at 09:16:07PM +, Michael Crusoe wrote:
Since we are using a wrapper anyway I have set this inside the wrapper
and thus do not see any need for README.Debian. If you agree, please
have a look at
https://people.debian.org/~tille/packages/trimmomatic/
and please test the package whether I have interpreted your links
correctly and the package can be uploaded as is. If you could provide
a test using the adapters this would be more than welcome. Our goal
should be tro get at least 80% of our packages autopkgtest-able.
Trimmomatic uses a nonstandard argument parser. ILLUMINACLIP is command
line option, not an environmental variable. Adding `export
ILLUMINACLIP=/usr/share/${ILLUMINACLIP}/adapters` to the wrapper script
will have no effect.
Here is an example command line
TrimmomaticSE --phred33 input.fq.gz output.fq.gz
ILLUMINACLIP:/usr/share/trimmomatic/TruSeq3-SE:2:30:10 LEADING:3 TRAILING:3
SLIDINGWINDOW:4:15 MINLEN:36
OK. Would you mind having a look at
https://people.debian.org/~tille/packages/trimmomatic/
again? Could you confirm that this package will close the bug and
provides what users expect?
However no FASTQ format sequence files are provided in the package so I
can't write a test case.
Well, we actually can add our own to debian/tests, can't we?
Kind regards
Andreas.
--
http://fam-tille.de
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#779296: trimmomatic: directory of adapters missing from package
On Thu, Feb 26, 2015 at 4:26 PM Andreas Tille andr...@an3as.eu wrote:
Hi Michael,
On Thu, Feb 26, 2015 at 09:16:07PM +, Michael Crusoe wrote:
Since we are using a wrapper anyway I have set this inside the wrapper
and thus do not see any need for README.Debian. If you agree, please
have a look at
https://people.debian.org/~tille/packages/trimmomatic/
and please test the package whether I have interpreted your links
correctly and the package can be uploaded as is. If you could provide
a test using the adapters this would be more than welcome. Our goal
should be tro get at least 80% of our packages autopkgtest-able.
Trimmomatic uses a nonstandard argument parser. ILLUMINACLIP is command
line option, not an environmental variable. Adding `export
ILLUMINACLIP=/usr/share/${ILLUMINACLIP}/adapters` to the wrapper script
will have no effect.
Here is an example command line
TrimmomaticSE --phred33 input.fq.gz output.fq.gz
ILLUMINACLIP:/usr/share/trimmomatic/TruSeq3-SE:2:30:10 LEADING:3
TRAILING:3
SLIDINGWINDOW:4:15 MINLEN:36
OK. Would you mind having a look at
https://people.debian.org/~tille/packages/trimmomatic/
again? Could you confirm that this package will close the bug and
provides what users expect?
The command I gave you was from their webpage; alas it contains two small
errors: should be `-phred33` (single dash) and the adapter file needs to be
a correct path; the file extension is missing.
TrimmomaticSE -phred33 input.fq.gz output.fq.gz
ILLUMINACLIP:/usr/share/trimmomatic/TruSeq3-SE.fa:2:30:10
LEADING:3 TRAILING:3 SLIDINGWINDOW:4:15 MINLEN:36
This runs successfully on my system with local data.
However no FASTQ format sequence files are provided in the package so I
can't write a test case.
Well, we actually can add our own to debian/tests, can't we?
Right. I've tracked down the sequences they used in their paper but I can't
find license nor copyright information:
http://www.ebi.ac.uk/ena/data/view/SRX131047
While these files are rather large (113MiB) I could generate a subset for
testing purposes.
Kind regards
Andreas.
--
http://fam-tille.de
Bug#779308: marked as done (Gramps: Upgrade to Python 3 Gramps causing multiple serious database errors)
Your message dated Thu, 26 Feb 2015 21:49:46 + with message-id e1yr6jw-0004br...@franck.debian.org and subject line Bug#779308: fixed in gramps 4.1.1~dfsg-3 has caused the Debian Bug report #779308, regarding Gramps: Upgrade to Python 3 Gramps causing multiple serious database errors 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.) -- 779308: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=779308 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: gramps Version: 4.1.1~dfsg-2 Severity: serious Tags: pending Hi, I have been made aware of several upstream bugs that render Gramps unusable for users that have special characters in their database (i.e. languages other than English). For example: https://gramps-project.org/bugs/view.php?id=8134 https://gramps-project.org/bugs/view.php?id=8258 https://gramps-project.org/bugs/view.php?id=8357 https://gramps-project.org/bugs/view.php?id=8360 https://gramps-project.org/bugs/view.php?id=8117 The bugs occur in Gramps 4.1.1 when users are asked to upgrade their database because of the switch to Python 3. This is the explanation from Nick Hall from the Gramps Project: The database contains a mix of unicode and strings. When a record in python2 format is loaded into python3, unicode gets converted into a str, but the way strings are converted depends on the encoding setting. If bytes is specifies then strings are converted into bytes, otherwise they are also converted to str. By default strings are converted into str using the ASCII encoding. This will cause errors if the strings contain utf-8 encoded unicode. I have cherry picked the commits from upstream that fix the problem, and it should be uploaded soon. Regards, Ross signature.asc Description: OpenPGP digital signature ---End Message--- ---BeginMessage--- Source: gramps Source-Version: 4.1.1~dfsg-3 We believe that the bug you reported is fixed in the latest version of gramps, 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 779...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ross Gammon rossgam...@mail.dk (supplier of updated gramps 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: SHA512 Format: 1.8 Date: Thu, 26 Feb 2015 21:57:31 +0100 Source: gramps Binary: gramps Architecture: source all Version: 4.1.1~dfsg-3 Distribution: unstable Urgency: medium Maintainer: Ross Gammon rossgam...@mail.dk Changed-By: Ross Gammon rossgam...@mail.dk Description: gramps - Genealogical research program Closes: 779308 Changes: gramps (4.1.1~dfsg-3) unstable; urgency=medium . * Add patch to fix bugs when database upgraded to Python 3 (Closes: #779308) Checksums-Sha1: b6e98892aed348ce3d1a6cb1597f27751c24ac1b 1953 gramps_4.1.1~dfsg-3.dsc e5c77829a84ba664e9cba04c5ce900a684b78d3b 16805905 gramps_4.1.1~dfsg.orig.tar.gz ae58e3a5b939e27506429d4994bca5a781e2b390 17848 gramps_4.1.1~dfsg-3.debian.tar.xz d727f27ca0a903928b2303abd54134efc9e0dbc8 6109398 gramps_4.1.1~dfsg-3_all.deb Checksums-Sha256: 43c4aef07af91ace4db080fedcf8476cc07f3688c903f4b035c011f19aef134e 1953 gramps_4.1.1~dfsg-3.dsc 6103b0d53c9c1a69fbf7b488a29ce9bd449ca397aa9864fe87eea00c93d14609 16805905 gramps_4.1.1~dfsg.orig.tar.gz 44d7cd7daa5d74a6f8412e96e84f5af6889e5815aa6018b1877db586304e579e 17848 gramps_4.1.1~dfsg-3.debian.tar.xz 71a27954870a34d6c10e59dad3b0fa630035879791ad04326ea68c8f226dde59 6109398 gramps_4.1.1~dfsg-3_all.deb Files: c369e5406d8101bfcfe8a00574c5057b 1953 python optional gramps_4.1.1~dfsg-3.dsc a8da81cc317cde496cd463d6643d07a9 16805905 python optional gramps_4.1.1~dfsg.orig.tar.gz aef0208b0a52cc4bd2d64aa311e3569a 17848 python optional gramps_4.1.1~dfsg-3.debian.tar.xz 0bed7faab5d4da029cf62e3930779587 6109398 python optional gramps_4.1.1~dfsg-3_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCgAGBQJU74r6AAoJEHM+a/k86PbZlRQQAI6uUEXZ/8jyMupY8VrQyh5N Ua7jDDF0jyNpStNzf2N2HblO2rqbbUZznT5NVVOuQH6s/jK5Rs0YRkJBLMl9zplx 4VVAI38n+i8RcqTgoeonSEGzfwde5Lc5sHiMt47oya4U8pI3wQQrRTWBLoKUMERp v5FV37m1jvdq3SXzJoVw+YZbUYRFqTlonY/QFaGbu0S8MIQrQya4Wxx3g0xyQ9A+ 99Mek47PEDL3+lPQQYt+LBYIjc7aHc6wSfDFBHMdNeR8QS/Twh7RJI3nbuX9xWB+
Bug#779115: polygen: diff for NMU version 1.0.6.ds2-13.1
On Wed, Feb 25, 2015 at 10:17:55PM +0100, gregor herrmann gre...@debian.org wrote: I've prepared an NMU for polygen (versioned as 1.0.6.ds2-13.1) and uploaded it to DELAYED/6. Please feel free to tell me if I should delay it longer. Thanks for your upload! Feel free to reschedule it in DELAYED/0. Thanks again! -- Mehdi Dogguy -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#762700: systemd: journald fails to forward most boot messages to syslog
Small correction to my previous observations: Am 2015-02-25 18:59, schrieb Christian Seiler: - SendBuffer=8M will increase the max size of a single log message that may be sent via this socket (8M is probably at bit much) Actually that's not true. I've misread the kernel source here, and a couple of tests I did after a good night's sleep actually shows that the SendBuffer should be increased in order for there to be enough space for log messages. So the fix/workaround/whatever you want to call it would be twofold: - increase max_dgram_qlen sysctl - increase SendBuffer for syslog.socket So basically something like: /lib/systemd/system/syslog.socket: +Wants=systemd-setup-dgram-qlen.service +SendBuffer=8M create /lib/systemd/system/systemd-setup-dgram-qlen.service: [Unit] DefaultDependencies=no Before=syslog.socket [Service] Type=oneshot ExecStart=/sbin/sysctl -w net.unix.max_dgram_qlen=512 StandardOutput=null (the values 8M and 512 are debatable, of course) Christian -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#779274: t1disasm: buffer overflow in set_cs_start
Package: t1utils
Version: 1.38-3
Severity: grave
Tags: security
Usertags: afl
$ t1asm crash.raw crash.pfb
t1asm: warning: no charstrings found in input file
$ t1disasm crash.pfb /dev/null
Segmentation fault
Backtrace:
#0 ___fprintf_chk (fp=0x6f6f6f6f, flag=1, format=0x804eedc %.*s) at
fprintf_chk.c:30
#1 0x0804d653 in fprintf (__fmt=0x804eedc %.*s, __stream=optimized out) at
/usr/include/i386-linux-gnu/bits/stdio2.h:97
#2 eexec_line (line=0xd320 /m, 'o' repeats 36 times, {string currentfile exch
readstring pop}executeonly def\n, line_len=optimized out, line_len@entry=94) at t1disasm.c:462
#3 0x0804e05e in disasm_output_binary (data=0xd320 /m, 'o' repeats 36 times,
{string currentfile exch readstring pop}executeonly def\n, len=94) at t1disasm.c:595
#4 0x0804cf67 in process_pfb (ifp=0x80531c0, ifp_filename=0xd9ff
crash.pfb, fr=0xd760) at t1lib.c:295
#5 0x08048f41 in main (argc=3, argv=0xd834) at t1disasm.c:770
This happened because set_cs_start overwrote the file pointer with data
from the disassembled file.
I believe the bug can be exploited for code execution, at least on
systems that don't have executable space protection.
This bug was found using American fuzzy lop:
http://lcamtuf.coredump.cx/afl/
-- System Information:
Debian Release: 8.0
APT prefers unstable
APT policy: (990, 'unstable'), (500, 'experimental')
Architecture: i386 (x86_64)
Foreign Architectures: amd64
Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
Versions of packages t1utils depends on:
ii libc6 2.19-15
--
Jakub Wilk
currentfile eexec
/m{string currentfile exch readstring
pop}executeonly def
Bug#779183: pcl: sometimes FTBFS - fatal error: pcl/visualization/pcl_visualizer.h: No such file or directory
Hi James, thanks for reporting it and the patch. I have created a new version of the package. It's here: http://mentors.debian.net/package/pcl Now I will ask to the sponsor to upload the new version and ask to ftp-master to unblock it. Best regards, Leopold El Dimecres, 25 de febrer de 2015, a les 09:22:52, James Cowgill va escriure: Source: pcl Version: 1.7.2-6 Severity: serious Tags: patch Hi, pcl seems to sometimes FTBFS with this error: [ 52%] Building CXX object tools/CMakeFiles/pcl_mesh2pcd.dir/mesh2pcd.cpp.o cd /tmp/buildd/pcl-1.7.2/build/tools /usr/bin/c++ -DEIGEN_USE_NEW_STDVECTOR -DEIGEN_YES_I_KNOW_SPARSE_MODULE_IS_NOT_STABLE_YET -DQT_CORE_LIB -DQT_GUI_LIB -DQT_NO_DEBUG -Dqh_QHpointer -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 -D_FORTIFY_SOURCE=2 -pthread -fopenmp -Wno-deprecated -isystem /usr/include/eigen3 -isystem /usr/include/ni -I/tmp/buildd/pcl-1.7.2/recognition/include/pcl/recognition/3rdparty -isystem /usr/include/qt4 -isystem /usr/include/qt4/QtGui -isystem /usr/include/qt4/QtCore -I/tmp/buildd/pcl-1.7.2/build/include -I/tmp/buildd/pcl-1.7.2/common/include -I/tmp/buildd/pcl-1.7.2/io/include -I/tmp/buildd/pcl-1.7.2/filters/include -I/tmp/buildd/pcl-1.7.2/sample_consensus/include -I/tmp/buildd/pcl-1.7.2/segmentation/include -I/tmp/buildd/pcl-1.7.2/search/include -I/tmp/buildd/pcl-1.7.2/kdtree/include -I/tmp/buildd/pcl-1.7.2/features/include -I/tmp/buildd/pcl-1.7.2/surface/include -I/tmp/buildd/pcl-1.7.2/octree/include -I/tmp/buildd/pcl-1.7.2/registration/include -I/tmp/buildd/pcl-1.7.2/recognition/include -I/tmp/buildd/pcl-1.7.2/geometry/include -I/tmp/buildd/pcl-1.7.2/keypoints/include -I/usr/include/vtk-5.8 -I/tmp/buildd/pcl-1.7.2/tools/include-o CMakeFiles/pcl_mesh2pcd.dir/mesh2pcd.cpp.o -c /tmp/buildd/pcl-1.7.2/tools/mesh2pcd.cpp /tmp/buildd/pcl-1.7.2/tools/mesh2pcd.cpp:38:46: fatal error: pcl/visualization/pcl_visualizer.h: No such file or directory #include pcl/visualization/pcl_visualizer.h ^ compilation terminated. Note that -I/.../visualization/include does not appear in the compiler command like it does on the successful builds. The top of the log contains this which seems a bit strange: -- The following subsystems will be built: -- common -- kdtree -- octree -- search -- sample_consensus -- filters -- features -- geometry -- registration -- io -- segmentation -- surface -- recognition -- keypoints -- visualization -- tracking -- apps building: |_ point_cloud_editor |_ in_hand_scanner |_ modeler not building: |_ cloud_composer: No reason |_ optronic_viewer: FZAPI was not found. -- people -- outofcore -- examples -- The following subsystems will not be built: -- tools: Requires visualization. -- global_tests: No reason I had a look at the build system and it seems that tools does not declare a dependency on visualization so the order they're built is random. I think the order depends on the order of directory entries as chosen by the filesystem driver. This could explain why the build worked on some buildds. I haven't managed to build the current version on my amd64 machine at all (in various different chroots). Some logs of failed builds (the arm64 one later built successfully): https://buildd.debian.org/status/fetch.php?pkg=pclarch=sparcver=1.7.2-6st amp=1417974163 https://launchpadlibrarian.net/193721902/buildlog_ubuntu-vivid-ppc64el.pcl_ 1.7.2-6_FAILEDTOBUILD.txt.gz https://buildd.debian.org/status/fetch.php?pkg=pclarch=arm64ver=1.7.2-3st amp=1416536853 I've attached a patch which adds the dependency which fixes this issue for me. Thanks, James -- -- Linux User 152692 GPG: 05F4A7A949A2D9AA Catalonia - A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? signature.asc Description: This is a digitally signed message part.
Bug#776911: gnome-shell: fails to start on i386 when [Mesa was] built with llvm-3.5
Adding mesa@packages to Cc since I suspect #775235 needs reassigning to Mesa, perhaps along with its merged bugs #770130, #776911. Context for Mesa maintainers: #775235 is that gnome-shell crashes in an i386 VM with its default choice of emulated CPU, with LLVM ERROR: Do not know how to split the result of this operator!. See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775235#10 for full backtrace. The merged bug #770130 is that gnome-shell crashes on an unknown i386 (probably relatively old, since it has 82830M/MG integrated graphics, which Wikipedia says is a Pentium III-M chipset) with Cogl-ERROR **: Failed to create texture 2d due to size/format constraints. Oddly, this only happens for non-power-of-two textures in the gnome-shell run by the actual user, not by the gnome-shell used for the gdm login prompt (even though both use non-power-of-two textures). Michael Gilbert merged this with #775235 and #776911 without comment; I'm not sure of the reasoning for believing that #775235 and #770130 is the same thing. The other merged bug #776911 is that gnome-shell crashes on an unknown i386 with Cogl-ERROR **: Failed to create texture 2d due to size/format constraints; that looks like the same thing as #770130. On Sat, 21 Feb 2015 at 21:46:01 -0500, Michael Gilbert wrote: On Fri, Feb 6, 2015 at 1:20 PM, Simon McVittie wrote: Michael, I see you've found a solution or workaround: is there anything you'd like Rafal to try? Try gnome-shell built with llvm-3.4 instead of 3.5. gnome-shell doesn't build-depend on any llvm version so I don't think that's going to make any difference. Do you mean mesa built with llvm-3.4 instead of 3.5, as seen in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775235#15? Looking at the Ubuntu changelog, it seems that they rebuilt mesa with llvm-3.5, then reverted to llvm-3.4 because too many regressions (e.g. https://bugs.launchpad.net/ubuntu/+source/llvm-toolchain-3.5/+bug/1360241), but then switched to llvm-3.6 for Mesa 10.4 in 15.04/vivid. Mesa 10.4.2 seems to have been accidentally uploaded to unstable instead of experimental. I infer from the git repository that 10.3.2 (via t-p-u) is still the version targeted for jessie: is this correct? Would use of llvm-3.4 for jessie be acceptable to the Mesa maintainers? According to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775235#15 that fixes at least one of these merged bugs, perhaps all three. Alternatively, would it be useful information for the Mesa maintainers if people tried Mesa 10.4.2 on affected systems? #775235 should be easy to reproduce on an i386 VM on an amd64 host (I assume that's how Steve did the original failed test), but #770130 and #776911 seem to require access to real hardware. I have a Pentium IV system which I might be able to resurrect if that would help, although if the relevant CPU feature is SSE2, I think that's too new. S -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#779296: trimmomatic: directory of adapters missing from package
Hi Michael, On Thu, Feb 26, 2015 at 09:41:35PM +, Michael Crusoe wrote: The command I gave you was from their webpage; alas it contains two small errors: should be `-phred33` (single dash) and the adapter file needs to be a correct path; the file extension is missing. TrimmomaticSE -phred33 input.fq.gz output.fq.gz ILLUMINACLIP:/usr/share/trimmomatic/TruSeq3-SE.fa:2:30:10 LEADING:3 TRAILING:3 SLIDINGWINDOW:4:15 MINLEN:36 This runs successfully on my system with local data. Thanks for checking. I have uploaded to unstable and will file an unblock bug tomorrow. If anybody else could check the uploaded package as well this would be cool. Well, we actually can add our own to debian/tests, can't we? Right. I've tracked down the sequences they used in their paper but I can't find license nor copyright information: http://www.ebi.ac.uk/ena/data/view/SRX131047 While these files are rather large (113MiB) I could generate a subset for testing purposes. I'm looking forward to this. Kind regards Andreas. -- http://fam-tille.de -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#779296: marked as done (trimmomatic: directory of adapters missing from package)
Your message dated Thu, 26 Feb 2015 22:50:41 + with message-id e1yr7gt-0002lk...@franck.debian.org and subject line Bug#779296: fixed in trimmomatic 0.32+dfsg-3 has caused the Debian Bug report #779296, regarding trimmomatic: directory of adapters missing from package to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 779296: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=779296 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: trimmomatic Version: 0.32+dfsg-2 Severity: important Dear Maintainer, The files in the adapters directory in upstream's source are an important part of the Trimmomatic package. They are used to trim contaminants from sequencing files. Please include them in a future release of the package. Thanks! -- Michael R. Crusoe ---End Message--- ---BeginMessage--- Source: trimmomatic Source-Version: 0.32+dfsg-3 We believe that the bug you reported is fixed in the latest version of trimmomatic, 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 779...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Tille ti...@debian.org (supplier of updated trimmomatic 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: SHA512 Format: 1.8 Date: Thu, 26 Feb 2015 21:52:47 +0100 Source: trimmomatic Binary: trimmomatic Architecture: source all Version: 0.32+dfsg-3 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team debian-med-packag...@lists.alioth.debian.org Changed-By: Andreas Tille ti...@debian.org Description: trimmomatic - flexible read trimming tool for Illumina NGS data Closes: 779296 Changes: trimmomatic (0.32+dfsg-3) unstable; urgency=medium . * Install adapter files and document their usage in d/README.Debian Closes: #779296 Checksums-Sha1: eaa80a4b5ba674c5a3e319c4b601b47152d4f8b5 2121 trimmomatic_0.32+dfsg-3.dsc cc08e9132e9a7794b197138672cdfc23efead4b6 5516 trimmomatic_0.32+dfsg-3.debian.tar.xz b84f91b6fd56b36ceb54b65943c6f75fd1cf638d 104612 trimmomatic_0.32+dfsg-3_all.deb Checksums-Sha256: 111f33279bd9a0e062bd8df375f26728c91065eb7f5031a93b234384c56d7b0a 2121 trimmomatic_0.32+dfsg-3.dsc 8d224e12e01934b1ec4795f2a45cbf4a8aa8c370803844b56660d35edaea74a1 5516 trimmomatic_0.32+dfsg-3.debian.tar.xz afbf0cd2e7d3d4cd29efafabe1340c78be07cdea95c97b8013f926067cb0eee1 104612 trimmomatic_0.32+dfsg-3_all.deb Files: 7052289cf4fa51b6688cb8724279368c 2121 science optional trimmomatic_0.32+dfsg-3.dsc 95f74e4839943b85ed956fef2db25a3d 5516 science optional trimmomatic_0.32+dfsg-3.debian.tar.xz fdb455356ce9ab94c722bea68e3e2409 104612 science optional trimmomatic_0.32+dfsg-3_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCgAGBQJU76GHAAoJEFeKBJTRxkbRtY0P/AqOFEs/t21CSJOurtOTyJ5S xvJZ04+MSr704wseykSsovWiKtesS8H6ERrF7f+CoJIZ3/QCcT1zi4xUBAIrogVd /ooNp5lemHYcc/wFRsUXfMMaKlfyb/PGb6Z03krgGmkrztb4KKtKmuIkop0QOGnz vTQdo+G5Vqa6/P4FQmd60+oa7J79KrdFN0Oc0jMdsUvT1gXdhIaptYxFI3zrLX8T SRXkLAftXDakiJZ3B8IFXkVNomxKSDxw0YO6uQv4MpDuhENL3VkLFcwC2yps1gBZ AMmGiwmoUzQFrp31ERAXYgkzmAidi4xMyNtbRGd4jax/cJa/VcNI6W3yk2bO7KGr h/Gt1JYF43tHVMAE04nVfORWKWTraTVeSEpG408AJLMaSLm6TMw5WONqlIzNTYKy VyHvNdeetRtZI01hc3lXh6ugHNHmwYK3OJNizS1/gF9w7m7bmLuFnIaao6lkxNee 8eKNx0Ci+A/N/yRBAgckploqvAK/SNmascer28mhsb11pPfxPhN05H1lCtklOn1J WnmjmuAmFHRaL6nm66ipKqff8RoBS2GDfufrTlaz7d7Zr9NwKcB2isJN7MZYLJ3m lRmSTwOznGsXQOY1IwY5bm9HcDOu4r1B2UKgMdWLZI5PJau19Dg8LxwrwnO2h4G+ 3m1niGx6INYOc04CohXr =6nUK -END PGP SIGNATUREEnd Message---
Bug#778387: squeeze update of cups?
On Mon, 2015-02-23 at 18:38 +0100, Didier 'OdyX' Raboud wrote: Hi, Le lundi, 23 février 2015, 11.58:33 Raphael Hertzog a écrit : the Debian LTS team would like to fix the security issues which are currently open in the Squeeze version of your package: https://security-tracker.debian.org/tracker/CVE-2014-9679 Would you like to take care of this yourself? If yes, please follow the workflow we have defined here: http://wiki.debian.org/LTS/Development I will, but keep in mind that we're still discussing the Wheezy patch with the security team, so I'd like to get that fixed too (ideally first). That said, the part from the upstream patch that we're discussing doesn't apply to Squeeze(-LTS), so we might as well upload the patch as- is. Proposed debdiff attached. This does not fix the bug! Ben. -- Ben Hutchings It is easier to write an incorrect program than to understand a correct one. signature.asc Description: This is a digitally signed message part
Bug#778387: squeeze update of cups?
On Fri, 2015-02-27 at 03:17 +, Ben Hutchings wrote: On Mon, 2015-02-23 at 18:38 +0100, Didier 'OdyX' Raboud wrote: Hi, Le lundi, 23 février 2015, 11.58:33 Raphael Hertzog a écrit : the Debian LTS team would like to fix the security issues which are currently open in the Squeeze version of your package: https://security-tracker.debian.org/tracker/CVE-2014-9679 Would you like to take care of this yourself? If yes, please follow the workflow we have defined here: http://wiki.debian.org/LTS/Development I will, but keep in mind that we're still discussing the Wheezy patch with the security team, so I'd like to get that fixed too (ideally first). That said, the part from the upstream patch that we're discussing doesn't apply to Squeeze(-LTS), so we might as well upload the patch as- is. Proposed debdiff attached. This does not fix the bug! I cherry-picked git commit 6c087a72a0708bcb7929955c75770ee364755c42 (Add some range checking (probably more to come) to avoid divide-by-0 errors.), after which the critical hunk of the patch for CVE-2014-9679 applied cleanly. With Didier's original patch, zcat bogus.raster.gz | rastertohp foo bar baz 1 '' still crashes (segmentation fault). With the two patches applied, it fails cleanly (no pages found). I was still able to print a test page (though I'm not certain that this uses the raster filter code in my configuration). So I've uploaded with those two patches applied. Ben. -- Ben Hutchings It is easier to write an incorrect program than to understand a correct one. signature.asc Description: This is a digitally signed message part
