Bug#841163: [debian-mysql] Upload of MySQL 5.7.16 security update to unstable
On 11/08/2016 10:53 PM, Dominic Hargreaves wrote: Hi Lars, Now uploaded. Cheers, Dominic. Great, thanks! -- Lars
Bug#823004: gplaycli: sensitive information in config file
agree, but there is a potential big issue with providing default credentials : the google account will be subject to password change, and the more the package is used the more often this password will be changed. Password change means for me reset the password, update the default credentials and maybe update the Debian package. If someone found an alternate good solution ... Le 9 novembre 2016 05:42:12 GMT+01:00, Paul Wise a écrit : >On Mon, 7 Nov 2016 19:26:57 +0100 Hans-Christoph Steiner wrote: > >> I think the best way forward for this issue is for the gplaycli >> package to leave out the default credentials. > >This will make the package essentially useless. >I suggest this bug report be closed wontfix. > >-- >bye, >pabs > >https://wiki.debian.org/PaulWise -- Matlink - sysadmin Matlink.fr
Bug#823004: gplaycli: sensitive information in config file
On Mon, 7 Nov 2016 19:26:57 +0100 Hans-Christoph Steiner wrote: > I think the best way forward for this issue is for the gplaycli > package to leave out the default credentials. This will make the package essentially useless. I suggest this bug report be closed wontfix. -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#843674: marked as done (gocryptfs: FTBFS: "pkg-config": executable file not found in $PATH)
Your message dated Wed, 09 Nov 2016 04:19:35 + with message-id and subject line Bug#843674: fixed in gocryptfs 1.1.1-1 has caused the Debian Bug report #843674, regarding gocryptfs: FTBFS: "pkg-config": executable file not found in $PATH 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.) -- 843674: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843674 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gocryptfs Version: 1.0-2 Severity: serious Justification: fails to build from source (but built successfully in the past) Builds of gocryptfs in minimal environments (as on the autobuilders) have been failing: pkg-config: exec: "pkg-config": executable file not found in $PATH Please declare a build dependency on pkg-config, and confirm with pbuilder or the like that you haven't missed anything else. Thanks! FTR, I classified this bug as a regression because it would affect any binNMUs that might be necessary. -- Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org) http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu --- End Message --- --- Begin Message --- Source: gocryptfs Source-Version: 1.1.1-1 We believe that the bug you reported is fixed in the latest version of gocryptfs, 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 843...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. David Steele (supplier of updated gocryptfs 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, 08 Nov 2016 23:03:10 -0500 Source: gocryptfs Binary: gocryptfs Architecture: source amd64 Version: 1.1.1-1 Distribution: unstable Urgency: medium Maintainer: Debian Go Packaging Team Changed-By: David Steele Description: gocryptfs - Encrypted overlay filesystem written in Go. Closes: 843674 Changes: gocryptfs (1.1.1-1) unstable; urgency=medium . * New upstream release. * Add required build depends (Closes: 843674) Checksums-Sha1: 532f4adb857eecf9fc453eae3c7186c161b4ea1d 2178 gocryptfs_1.1.1-1.dsc a4bc544ba007a87abf1bdbcaf3e463f177ff145e 1093098 gocryptfs_1.1.1.orig.tar.gz c4a53bb8b60cb63baca05b1be3cd2cb471f1dc8e 4596 gocryptfs_1.1.1-1.debian.tar.xz 5e7718463a825161394376e2124ef0ebc1fc57cb 519682 gocryptfs-dbgsym_1.1.1-1_amd64.deb 4d667be7f8ee6815e4c92832a35b7b6736cf23fc 7049 gocryptfs_1.1.1-1_20161109T040521z-8c497f91.buildinfo c97bcfe88c0f9f4910a97580329ee49d8a2405da 1110766 gocryptfs_1.1.1-1_amd64.deb Checksums-Sha256: 5ec1f1c819e36cb42f34afac56096a4e073fcbdc7c1db87247671ea278b29782 2178 gocryptfs_1.1.1-1.dsc f6d24c70b3a76cd910379d246fe773cc2314d145feb4e9f0c3d80efdbc953374 1093098 gocryptfs_1.1.1.orig.tar.gz 0113b3325ea92fe5e25d696594c76aee9867245a106c91eddd915b9f6df6441b 4596 gocryptfs_1.1.1-1.debian.tar.xz a2ee83b27c030fe9f865a0b08bd731fff9a224743806b94b60c72287ceabf28d 519682 gocryptfs-dbgsym_1.1.1-1_amd64.deb fda293127055703bdd8e51fc629d399174d15e26ea850afd533021e0bfdaf337 7049 gocryptfs_1.1.1-1_20161109T040521z-8c497f91.buildinfo ec22966a53176352215b04db6c277f6ea2ee43c27ecb66c9dc30bce02d6ec30f 1110766 gocryptfs_1.1.1-1_amd64.deb Files: e7ef038aeee68617b00ba7458349abea 2178 devel extra gocryptfs_1.1.1-1.dsc d8a014c07e4ffe5a1e9e6cce9901ea7a 1093098 devel extra gocryptfs_1.1.1.orig.tar.gz c2eaa8f535db6ad6023c5e050abac138 4596 devel extra gocryptfs_1.1.1-1.debian.tar.xz 73553d787987af7ff523e8fa9b0fc4fc 519682 debug extra gocryptfs-dbgsym_1.1.1-1_amd64.deb 8c497f91e34814840958d97b0c91643d 7049 devel extra gocryptfs_1.1.1-1_20161109T040521z-8c497f91.buildinfo 655801ad139fb1e740a5c9a99f55693d 1110766 devel extra gocryptfs_1.1.1-1_amd64.deb -BEGIN PGP SIGNATURE- iQIvBAEBCAAZBQJYIqCEEhxzdGVlbGVAZGViaWFuLm9yZwAKCRBifrspCoF6ggWU D/9UenB7C5Zppz3WAcw0fNrAkxi+sNF1rRljyED/3Vc255YUkl4VeRlXHvDfRXuk VHw3f7FuG+Ci+8rMB/Sf0AvXR6/1+XAi7gk8Z1CF7LIXymTvmSEmAGT5QwKuXGIg aBUw9AsaosPBdf0dywEBvsIQv8k5jtUU00E/dBEtANCDb42Eo6kkagl9QyP3WZIW NSGVGyxl/K3IAJ3VIW6jzBik7Zgd0yX8gdUxd7WKYQBI7GC5qEiO3rVjOH1ZPk7k 8PRaYEZw6HAOfli09YGkKFpfoZECZlWhEURRnO4oO+ChOQaX9WXYKd8NgYayu4t9 uHOUQXk4l326E8NZfRl9YUwRLgKbSrhCBx/DJD5Aghffn8uAYDlody1BYyrXbCkV qtgra5rHyTE7
Bug#797998: marked as done (unknown-horizons: Crash shortly after start of single player game)
Your message dated Wed, 09 Nov 2016 03:13:14 + with message-id and subject line Bug#797998: fixed in unknown-horizons 2014.1+git160920-1 has caused the Debian Bug report #797998, regarding unknown-horizons: Crash shortly after start of single player game 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.) -- 797998: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=797998 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: unknown-horizons Version: 2014.1+ds1-2 Severity: important Dear Maintainer, I started Unknown Horizons and selected “single player game“. I then chose the second map (the one that is not “tutorial”). The game crashed before I could build the first settlement. Reproducing that, the game just crashed after a short time. I can play UH for approximately a minute before it crashes. -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 3.13-1-686-pae (SMP w/1 CPU core) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages unknown-horizons depends on: ii dpkg 1.18.1 ii python 2.7.9-1 ii python-enet 0.0~svn24-1+b2 ii python-fife 0.3.5-1+b1 ii python-yaml 3.11-2 pn python:any unknown-horizons recommends no packages. unknown-horizons suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: unknown-horizons Source-Version: 2014.1+git160920-1 We believe that the bug you reported is fixed in the latest version of unknown-horizons, 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 797...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Markus Koschany (supplier of updated unknown-horizons 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, 09 Nov 2016 00:31:30 +0100 Source: unknown-horizons Binary: unknown-horizons Architecture: source Version: 2014.1+git160920-1 Distribution: unstable Urgency: medium Maintainer: Debian Games Team Changed-By: Markus Koschany Description: unknown-horizons - 2D realtime strategy simulation Closes: 679118 797998 Changes: unknown-horizons (2014.1+git160920-1) unstable; urgency=medium . * Team upload. * New upstream release. - Fixes startup crash. The game is playable again. (Closes: #797998) - The game no longer embeds UMing.ttc. (Closes: #679118) * Declare compliance with Debian Policy 3.9.8. * Switch to compat level 10. * Use canonical Vcs-fields. * Tighten dependency on python-fife. * wrap-and-sort -sa. * Remove Pre-Depends for dpkg-dev. It is trivially satisfied now. * Remove debian/docs because the file is empty. * Replace embedded Unifont.ttf font with Debian's system font. * Fix Lintian warning executable-not-elf-or-script and remove executable bit from files like tm_*. * Update debian/copyright and use copyright format 1.0. Fix all syntax errors. Checksums-Sha1: 0f7746184ffad053769753d58461e75e56c1eff5 2290 unknown-horizons_2014.1+git160920-1.dsc 4be23e239bac8c6c3795de1dbf1dea410e5db93f 197217496 unknown-horizons_2014.1+git160920.orig.tar.xz d5ef808bdad8cd52f8892f21c0c43880c6ef90eb 12512 unknown-horizons_2014.1+git160920-1.debian.tar.xz Checksums-Sha256: af9fc7592567b75fa84189ca4e823df103e74fcb51e3fe34ea1162a53d08434d 2290 unknown-horizons_2014.1+git160920-1.dsc 9342154d2ede6e152175c1c69d84f3a51ba2704a77a286103590da40f0d02482 197217496 unknown-horizons_2014.1+git160920.orig.tar.xz c6db7500f4dfe4a544ae660f92dd9acdc8248ecdc798a45d4bce0be6992d8a6f 12512 unknown-horizons_2014.1+git160920-1.debian.tar.xz Files: 152652f8ecb6961a5f02d3cab67b8cfa 2290 games optional unknown-horizons_2014.1+git160920-1.dsc bec6e49f621f3f961454cf41c7e13346 197217496 games optional unknown-horizons_2014.1+git160920.orig.tar.xz dccaafd51d0fbe3aaebe874715bc1d93 12512 games optional unknown-horizons_2014.1+git160920-1.debian.tar.xz -BEGIN PGP SIGNATURE- iQKMBAEBCgB2BQJYIoZuXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGh
Bug#841538: marked as done (unknown-horizons: Crashes immediately on startup)
Your message dated Wed, 09 Nov 2016 03:13:14 + with message-id and subject line Bug#797998: fixed in unknown-horizons 2014.1+git160920-1 has caused the Debian Bug report #797998, regarding unknown-horizons: Crashes immediately on startup 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.) -- 797998: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=797998 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: unknown-horizons Version: 2014.1+ds1-2 Severity: grave Dear Maintainer, unknown-horizons installed on a testing/unstable system crashes immediately on startup. See console log below. Regards Andrew ajd@hal:~$ unknown-horizons Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/horizons/engine/generate_atlases.py", line 64, in from run_uh import init_environment ImportError: No module named run_uh Atlas generation failed. Continuing without atlas support. This just means that the game will run a bit slower. It will still run fine unless there are other problems. Cannot connect to server socket err = No such file or directory Cannot connect to server request channel jack server is not running or cannot be started JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for 4294967295, skipping unlock JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for 4294967295, skipping unlock Traceback (most recent call last): File "/usr/games/unknown-horizons", line 380, in main() File "/usr/games/unknown-horizons", line 189, in main ret = horizons.main.start(options) File "/usr/lib/python2.7/dist-packages/horizons/main.py", line 192, in start horizons.globals.fife.init() File "/usr/lib/python2.7/dist-packages/horizons/engine/engine.py", line 178, in init self._setting.apply() File "/usr/lib/python2.7/dist-packages/horizons/engine/settings.py", line 91, in apply change_language(language) File "/usr/lib/python2.7/dist-packages/horizons/i18n/__init__.py", line 125, in change_language horizons.globals.fife.pychan.loadFonts(fontdef) File "/usr/lib/python2.7/dist-packages/fife/extensions/pychan/fonts.py", line 88, in loadFonts for font in Font.loadFromFile(filename): File "/usr/lib/python2.7/dist-packages/fife/extensions/pychan/fonts.py", line 73, in loadFromFile fonts.append( Font(name,_get) ) File "/usr/lib/python2.7/dist-packages/fife/extensions/pychan/fonts.py", line 46, in __init__ self.font.setAntiAlias(self.antialias) File "/usr/lib/python2.7/dist-packages/fife/fife.py", line 3917, in setAntiAlias return _fife.GuiFont_setAntiAlias(self, antiAlias) TypeError: in method 'GuiFont_setAntiAlias', argument 2 of type 'bool' AL lib: (EE) alc_cleanup: 1 device not closed -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.7.0-1-amd64 (SMP w/8 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages unknown-horizons depends on: ii dpkg 1.18.10 ii python 2.7.11-2 ii python-enet 0.0~svn24-1+b2 ii python-fife 0.3.5-3 ii python-yaml 3.12-1 pn python:any unknown-horizons recommends no packages. unknown-horizons suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: unknown-horizons Source-Version: 2014.1+git160920-1 We believe that the bug you reported is fixed in the latest version of unknown-horizons, 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 797...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Markus Koschany (supplier of updated unknown-horizons 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, 09 Nov 2016 00:31:30 +0100 Source: unknown-horizons Binary: unknown-horizons Architecture: source Version: 2014.1+git160920-1 Distribution: unstable Urgency: medium Maintainer: Debian Games Team Changed-By: M
Bug#837573: marked as done (picolisp: FTBFS with bindnow and PIE enabled)
Your message dated Wed, 09 Nov 2016 01:36:48 + with message-id and subject line Bug#837573: fixed in picolisp 16.11.6-1 has caused the Debian Bug report #837573, regarding picolisp: FTBFS with bindnow and PIE enabled 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.) -- 837573: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837573 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: picolisp Version: 16.6-2 Severity: important User: bal...@balintreczey.hu Usertags: pie-bindnow-20160906 Justification: FTBFS on amd64 with extra hardening Hi, During a rebuild of all packages in sid, your package failed to build on amd64 with patched GCC and dpkg. The rebuild tested if packages are ready for a transition enabling PIE and bindnow for amd64. For more information about the changes to sid's dpkg and GCC please visit: https://wiki.debian.org/Hardening/PIEByDefaultTransition Relevant part (hopefully): ... cc -o ../bin/picolisp x86-64.linux.base.o -Wl,--no-as-needed -rdynamic -lc -lm -ldl -Wl,-z,relro -Wl,-z,now /usr/bin/ld: x86-64.linux.base.o: relocation R_X86_64_32S against symbol `Nil' can not be used when making a shared object; recompile with -fPIC /usr/bin/ld: final link failed: Nonrepresentable section on output collect2: error: ld returned 1 exit status Makefile:177: recipe for target '../bin/picolisp' failed make[2]: *** [../bin/picolisp] Error 1 ... The full build log is available from: https://people.debian.org/~rbalint/build-logs/pie-bindnow-20160906/picolisp_16.6-2_amd64.build.gz Thanks, Balint --- End Message --- --- Begin Message --- Source: picolisp Source-Version: 16.11.6-1 We believe that the bug you reported is fixed in the latest version of picolisp, 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 837...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Kan-Ru Chen (陳侃如) (supplier of updated picolisp 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, 09 Nov 2016 09:08:14 +0800 Source: picolisp Binary: picolisp Architecture: source amd64 Version: 16.11.6-1 Distribution: unstable Urgency: medium Maintainer: Kan-Ru Chen (陳侃如) Changed-By: Kan-Ru Chen (陳侃如) Description: picolisp - Lisp interpreter and application server framework Closes: 837573 Changes: picolisp (16.11.6-1) unstable; urgency=medium . * New upstream version 16.11.6 * debian/compat: Change dh compatibility to 9 * Require dpkg-dev >= 1.18.11 to build without PIE enabled. (Closes: #837573) Checksums-Sha1: 6cb4eb7493e98bc4d329f75435ec2aa7b127bc3b 2263 picolisp_16.11.6-1.dsc 66513fc4012b12438c243c504c0ad3cf5c1b 981808 picolisp_16.11.6.orig.tar.gz fd57f2189e0981082068dc42319d7640c1922b6e 10272 picolisp_16.11.6-1.debian.tar.xz 41bd1b0da814022dee2dc975f1d3b81730f5aea2 9925 picolisp_16.11.6-1_20161109T011253z-e6b6833c.buildinfo 39bdcbbbe89ba09325df00f74ab1674d00f35203 823872 picolisp_16.11.6-1_amd64.deb Checksums-Sha256: ecdfc53db2a11743561bc26220fb469b9205bc530eb64a89ffa52d53fb18074f 2263 picolisp_16.11.6-1.dsc 28ac615ea0b5e3c755b521e31bd025ef476e1de5b3eed9013d7c323f35697cd4 981808 picolisp_16.11.6.orig.tar.gz 02161c6751693a59db5aa304d4a3be297ad4db5ff8d60c0858401e2bf9b2030d 10272 picolisp_16.11.6-1.debian.tar.xz ff3e02528c92f159814d12953b8b1c642716415e20d849ee8659ad07545e07c1 9925 picolisp_16.11.6-1_20161109T011253z-e6b6833c.buildinfo a5daff29a1d1489240900cd2ae66f6512adc2755e28f79cdc684e9c665bda638 823872 picolisp_16.11.6-1_amd64.deb Files: 3146287fd953fe7ed60b6815e7c9bc55 2263 lisp optional picolisp_16.11.6-1.dsc b82e63f47ea26bd0b7262398e1de48a1 981808 lisp optional picolisp_16.11.6.orig.tar.gz 48d4f0f186347b063b3d7a6af949fc7c 10272 lisp optional picolisp_16.11.6-1.debian.tar.xz e6b6833c0c5a2056b32be1e5d275f602 9925 lisp optional picolisp_16.11.6-1_20161109T011253z-e6b6833c.buildinfo 8371e16a854f98cdf013eb30a392965a 823872 lisp optional picolisp_16.11.6-1_amd64.deb -BEGIN PGP SIGNATURE- iQIcBAEBCgAGBQJYInhSAAoJEAo5NUq25X3hBlsQAKYD91tmn01NlqLbEKKPzMWQ QhDfgrQ4k//ozRzzQFq/NeSSWZZVtxVTbZhY3Zy6yYrruZZOpkQFq6b12A2YXT+6 qQymqevYdoFKmBNgX4jHC1uJlOcOq3W0tdUrTkO7ZbrVv
Processed: tagging 843682, found 843682 in 8.15.2-6
Processing commands for cont...@bugs.debian.org: > tags 843682 + pending Bug #843682 [sendmail] openssl: 'openssl dsaparam 2048 -out file' hangs, trying to read from stdin Added tag(s) pending. > found 843682 8.15.2-6 Bug #843682 [sendmail] openssl: 'openssl dsaparam 2048 -out file' hangs, trying to read from stdin Marked as found in versions sendmail/8.15.2-6. > thanks Stopping processing here. Please contact me if you need assistance. -- 843682: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843682 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#833242: NMU + patch for debtree #833242 (Uses obsolete compressor for .deb data.tar member) + #823279 (Warning "Useless use of \E at /usr/bin/debtree line 612.")
Control: tag -1 + patch pending
Hi,
I've uploaded a non-maintainer upload to DELAYED/7 which fixes:
* RC bug #833242: Uses obsolete compressor for .deb data.tar member
* Bug #823279: Warning "Useless use of \E at /usr/bin/debtree line 612."
* A typo in the man page found by lintian.
Feel free to tell me if I should fast-forward it or delay it longer.
(Note that the upload delay is chosen so that the NMU has a chance to
propagate to testing before the buggy version gets removed from
testing. Otherwise I would have uploaded it to DELAYED/10.)
Additionally I've also pushed my changes to the branch "nmu" in the
collab-maint git repository:
https://anonscm.debian.org/cgit/collab-maint/debtree.git/log/?id=refs/heads/nmu
That way you can easily import my changes by doing a fast-forward
merge from that branch into the master branch. (I'll do the tagging
and that merge once the NMU has been accepted into the archive.)
Full debdiff:
diff -Nru debtree-1.0.10/debian/changelog debtree-1.0.10+nmu1/debian/changelog
--- debtree-1.0.10/debian/changelog 2012-06-22 01:17:19.0 +0200
+++ debtree-1.0.10+nmu1/debian/changelog2016-11-09 01:26:57.0
+0100
@@ -1,3 +1,13 @@
+debtree (1.0.10+nmu1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Remove override_dh_builddeb to no more build with deprecated bzip2
+compression. (Closes: #833242)
+ * Guard …."\E" with "no warnings qw(misc);" (Closes: #823279)
+ * Fix typo in man page found by lintian.
+
+ -- Axel Beckert Wed, 09 Nov 2016 01:26:57 +0100
+
debtree (1.0.10) unstable; urgency=low
[ Thorsten Alteholz ]
diff -Nru debtree-1.0.10/debian/rules debtree-1.0.10+nmu1/debian/rules
--- debtree-1.0.10/debian/rules 2011-04-17 01:31:33.0 +0200
+++ debtree-1.0.10+nmu1/debian/rules2016-11-09 00:35:44.0 +0100
@@ -5,6 +5,3 @@
%:
dh $@
-
-override_dh_builddeb:
- dh_builddeb -- -Zbzip2
diff -Nru debtree-1.0.10/debtree debtree-1.0.10+nmu1/debtree
--- debtree-1.0.10/debtree 2012-06-22 00:30:16.0 +0200
+++ debtree-1.0.10+nmu1/debtree 2016-11-09 00:49:33.0 +0100
@@ -609,7 +609,9 @@
my $pinfo = get_apt_pinfo($rdep, "");
my $deps = get_apt_deps($pinfo, $dtype);
+ no warnings qw(misc);
my $regex = "(\Q" . join("\E|\Q", @pset) . "\E)";
+ use warnings;
for my $dep_or (split(/,/, $deps)) {
next unless $dep_or =~ /(^|\|)$regex([| ]|$)/;
diff -Nru debtree-1.0.10/debtree.1 debtree-1.0.10+nmu1/debtree.1
--- debtree-1.0.10/debtree.12011-11-29 23:58:29.0 +0100
+++ debtree-1.0.10+nmu1/debtree.1 2016-11-09 01:26:57.0 +0100
@@ -50,7 +50,7 @@
If a package included in an alternative dependency also needs to be displayed
separately or is also part of some other alternative dependency set, its
dependencies will only be included once, with the package's first occurrence.
-For the secondary occurences the package name will be shown between square
+For the secondary occurrences the package name will be shown between square
brackets: `[...]'.
.PP
See also the \-\-show\-installed option below.
Regards, Axel
--
,''`. | Axel Beckert , http://people.debian.org/~abe/
: :' : | Debian Developer, ftp.ch.debian.org Admin
`. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5
`-| 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE
signature.asc
Description: Digital signature
Processed: NMU + patch for debtree #833242 (Uses obsolete compressor for .deb data.tar member) + #823279 (Warning "Useless use of \E at /usr/bin/debtree line 612.")
Processing control commands: > tag -1 + patch pending Bug #833242 [src:debtree] debtree: Uses obsolete compressor for .deb data.tar member Added tag(s) pending and patch. -- 833242: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833242 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#843711: biber: FTBFS (failing tests)
Processing commands for cont...@bugs.debian.org: > forwarded 843711 https://github.com/plk/biber/issues/149 Bug #843711 [src:biber] biber: FTBFS (failing tests) Set Bug forwarded-to-address to 'https://github.com/plk/biber/issues/149'. > thanks Stopping processing here. Please contact me if you need assistance. -- 843711: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843711 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#843713: libsvn-web-perl: FTBFS (failing tests)
Package: src:libsvn-web-perl Version: 0.63-2 Severity: serious Dear maintainer: I tried to build this package in stretch with "dpkg-buildpackage -A" (which is what the "Arch: all" autobuilder would do to build it) but it failed: [...] debian/rules build-indep dh build-indep dh: Compatibility levels before 9 are deprecated (level 8 in use) dh_testdir -i dh_update_autotools_config -i dh_auto_configure -i dh_auto_configure: Compatibility levels before 9 are deprecated (level 8 in use) perl -I. Makefile.PL INSTALLDIRS=vendor Warning: prerequisite Alien::SVN 0 not found. Warning: prerequisite YAML 0 not found. Checking if your kit is complete... Looks good Generating a Unix-style Makefile [... snipped ...] ok 1 - stub 1..1 ok t/release-distmeta.t .. skipped: these tests are for release candidate testing t/release-pod-coverage.t .. skipped: these tests are for release candidate testing t/release-pod-syntax.t skipped: these tests are for release candidate testing t/svn-uris.t .. ok 1 - encode: simple svn-schema uri ok 2 - decode: simple svn-schema uri ok 3 - encode: path with spaces ok 4 - decode: path with spaces ok 5 - encode: path with unicode symbols ok 6 - decode: path with unicode symbols 1..6 ok t/timedate_format.t ... 1..4 ok 1 - An object of class 'SVN::Web::action' isa 'SVN::Web::action' ok 2 ok 3 ok 4 ok Test Summary Report --- t/1use.t(Wstat: 256 Tests: 14 Failed: 1) Failed test: 1 Non-zero exit status: 1 t/2basic.t (Wstat: 512 Tests: 0 Failed: 0) Non-zero exit status: 2 Parse errors: No plan found in TAP output t/3svnweb-install.t (Wstat: 512 Tests: 0 Failed: 0) Non-zero exit status: 2 Parse errors: Bad plan. You planned 3 tests but ran 0. Files=10, Tests=25, 1 wallclock secs ( 0.04 usr 0.02 sys + 0.56 cusr 0.07 csys = 0.69 CPU) Result: FAIL Failed 3/10 test programs. 1/25 subtests failed. Makefile:1008: recipe for target 'test_dynamic' failed make[2]: *** [test_dynamic] Error 255 make[2]: Leaving directory '/<>' dh_auto_test: make -j1 test TEST_VERBOSE=1 LC_ALL=C.UTF-8 returned exit code 2 debian/rules:7: recipe for target 'override_dh_auto_test' failed make[1]: *** [override_dh_auto_test] Error 2 make[1]: Leaving directory '/<>' debian/rules:4: recipe for target 'build-indep' failed make: *** [build-indep] Error 2 dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2 There are full build logs available here: https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/libsvn-web-perl.html Note: Even if this package is Arch:all, please consider uploading in source-only form, so that we get official build logs available here: https://buildd.debian.org/status/package.php?p=libsvn-web-perl Thanks.
Bug#843564: marked as done (/usr/bin/firewall-applet: Missing QT5 dependency)
Your message dated Tue, 08 Nov 2016 23:04:32 + with message-id and subject line Bug#843564: fixed in firewalld 0.4.4-2 has caused the Debian Bug report #843564, regarding /usr/bin/firewall-applet: Missing QT5 dependency to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 843564: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843564 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: firewall-applet Version: 0.4.4-1 Severity: serious File: /usr/bin/firewall-applet Hi, python3-dbus.mainloop.qt dependency should probably be changed to python3-dbus.mainloop.pyqt5. Cheers, Laurent Bigonville -- System Information: Debian Release: stretch/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.8.0-1-amd64 (SMP w/8 CPU cores) Locale: LANG=fr_BE.utf8, LC_CTYPE=fr_BE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages firewall-applet depends on: ii firewall-config0.4.4-1 ii firewalld 0.4.4-1 ii gir1.2-networkmanager-1.0 1.4.2-2 ii gir1.2-notify-0.7 0.7.7-1 ii python3-dbus 1.2.4-1 ii python3-dbus.mainloop.qt 4.11.4+dfsg-2 ii python3-gi 3.22.0-1 ii python3-pyqt5 5.7+dfsg-2+b1 ii python3-slip-dbus 0.6.1-3 pn python3:any firewall-applet recommends no packages. firewall-applet suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: firewalld Source-Version: 0.4.4-2 We believe that the bug you reported is fixed in the latest version of firewalld, 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 843...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Michael Biebl (supplier of updated firewalld 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, 08 Nov 2016 23:43:25 +0100 Source: firewalld Binary: firewalld firewall-applet firewall-config Architecture: source Version: 0.4.4-2 Distribution: unstable Urgency: medium Maintainer: Utopia Maintenance Team Changed-By: Michael Biebl Description: firewall-applet - panel applet providing status information of firewalld firewall-config - graphical configuration tool to change the firewall settings firewalld - dynamically managed firewall with support for network zones Closes: 843236 843564 Changes: firewalld (0.4.4-2) unstable; urgency=medium . * Update Homepage URL, use http://www.firewalld.org/. (Closes: #843236) * Fix dependencies of firewall-applet. Change Depends on python3-dbus.mainloop.qt to python3-dbus.mainloop.pyqt5. (Closes: #843564) Checksums-Sha1: c1fdd0902ea4d223a110bf630d233275330cd0bb 2112 firewalld_0.4.4-2.dsc 250e38bdb4bae11ca7bdf2c1f0d21268978c63fd 5916 firewalld_0.4.4-2.debian.tar.xz Checksums-Sha256: 556662773e4ed6b5a1b8e1569d8e8191261ba1a972504f5013a2ca804495d033 2112 firewalld_0.4.4-2.dsc fe5277a71b28df73317985137f329f3123ac9de10ada9c93f16a323c994205a7 5916 firewalld_0.4.4-2.debian.tar.xz Files: d764a653f0788f019896fbff09dca30c 2112 net optional firewalld_0.4.4-2.dsc f43303fd056d8193830bf7eeb1750fde 5916 net optional firewalld_0.4.4-2.debian.tar.xz -BEGIN PGP SIGNATURE- iQIcBAEBCAAGBQJYIlVqAAoJEGrh3w1gjyLcWsoP/jOoumm4AyOtbzs0d91Pp+Gn DgMpw3uhnHnQIoEyDq1auz1lEPnUXbAwgfy4oH+kG6ATe4R3KrLxENJofXXZT5p3 lIef2n+W5SetPRK8NgPTJqwQJBiziP8yFNEhw/rtgacXPWLRSTkIKmzxfNRZq4xh QPVyM0Rg3FgNp/PpVJQVryqHZlQLZbtnARKLerEwJWwTCFjpqOYqpgfk1YpeMBL8 RHU0coSet5NtmyFEzo2lAJxdfLooX4hjBtIo6hlyl18w5/tZmP0411+t7mtv/HPH fRC007uPVT9FNewwLRG2A9sTYUCtywJglxZaSs4uM8q6PRPVPDTYUjfmeiQ9CCsV 2TqxZCHOKPHsHDyeNeVcHFqyWiIE5SAdAeaf/Uwv5dYLoGmKKu3jaose4eVOYCS0 myFngGW7FUZDtV6vQeYmC7pI5O90YmUZbVFKmTcmFj4yjtRerIwrnq85SeoY5TmD wgapm/uq3ZcxfqDanstMqhM/VbeHuBogi1pKDzZd0NZ9rlL4MzOWKyABsA9/ba2I rJ4LxW6NmC2nHch5t+HeF3YEozqH1YVSGzRXSqUQ/tHU635iIOcfgbY1mRyOUreF R22P9qLKbhGoDTkvVFQvpkovaHqaN2SXhM2cJ386h+aTI5RfwPf5UOhr6+bVoDee Jw8rxPPY4otVyQ8j7/Xp =dDQA -END PGP
Bug#843712: biojava4-live: FTBFS (failing tests)
Package: src:biojava4-live Version: 4.1.0+dfsg-3 Severity: serious Dear maintainer: I tried to build this package in stretch with "dpkg-buildpackage -A" (which is what the "Arch: all" autobuilder would do to build it) but it failed: [...] debian/rules build-indep dh build-indep --with javahelper dh_testdir -i dh_update_autotools_config -i debian/rules override_dh_auto_configure make[1]: Entering directory '/<>/biojava4-live-4.1.0+dfsg' dh_auto_configure sed -e 's/BJLIB/biojava4-forester/g' debian/build.xml > biojava-forester/build.xml sed -e 's/BJLIB/biojava4-aa-prop/g' debian/build.xml > biojava-aa-prop/build.xml sed -e 's/BJLIB/biojava4-core/g' debian/build.xml > biojava-core/build.xml sed -e 's/BJLIB/biojava4-alignment/g' debian/build.xml > biojava-alignment/build.xml sed -e 's/BJLIB/biojava4-genome/g' debian/build.xml > biojava-genome/build.xml sed -e 's/BJLIB/biojava4-modfinder/g' debian/build.xml > biojava-modfinder/build.xml [... snipped ...] [junit] Testcase: testProteinSequenceFactoring[0] took 0 sec [junit] Testcase: testFeatures[0] took 0 sec [junit] Testcase: testProteinSequenceFactoring[1] took 0 sec [junit] Testcase: testFeatures[1] took 0 sec [junit] Testcase: testProteinSequenceFactoring[2] took 0 sec [junit] Testcase: testFeatures[2] took 0 sec [junit] Testcase: testProteinSequenceFactoring[3] took 0 sec [junit] Testcase: testFeatures[3] took 0 sec [junit] Testcase: testProteinSequenceFactoring[4] took 0 sec [junit] Testcase: testFeatures[4] took 0 sec [junit] Testcase: testProteinSequenceFactoring[5] took 0 sec [junit] Testcase: testFeatures[5] took 0 sec [junit] Testcase: testProteinSequenceFactoring[6] took 0 sec [junit] Testcase: testFeatures[6] took 0 sec [junit] Testcase: testProteinSequenceFactoring[7] took 0 sec [junit] Testcase: testFeatures[7] took 0 sec [junit] Running org.biojava.nbio.core.sequence.loader.SimpleGenbankProxySequenceReaderTest [junit] Testsuite: org.biojava.nbio.core.sequence.loader.SimpleGenbankProxySequenceReaderTest [junit] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.592 sec [junit] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.592 sec [junit] - Standard Error - [junit] SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder". [junit] SLF4J: Defaulting to no-operation (NOP) logger implementation [junit] SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details. [junit] - --- [junit] [junit] Testcase: testWrongSequence took 0.554 sec [junit] Caused an ERROR [junit] Unexpected exception, expected but was [junit] java.lang.Exception: Unexpected exception, expected but was [junit] Caused by: org.biojava.nbio.core.exceptions.ParserException: Section key was null [junit] at org.biojava.nbio.core.sequence.io.GenbankSequenceParser.parse(GenbankSequenceParser.java:143) [junit] at org.biojava.nbio.core.sequence.io.GenbankSequenceParser.getSequence(GenbankSequenceParser.java:368) [junit] at org.biojava.nbio.core.sequence.loader.GenbankProxySequenceReader.(GenbankProxySequenceReader.java:86) [junit] at org.biojava.nbio.core.sequence.loader.SimpleGenbankProxySequenceReaderTest.testWrongSequence(SimpleGenbankProxySequenceReaderTest.java:53) [junit] BUILD FAILED /<>/biojava4-live-4.1.0+dfsg/biojava-core/build.xml:101: Test org.biojava.nbio.core.sequence.loader.SimpleGenbankProxySequenceReaderTest failed Total time: 13 seconds debian/rules:57: recipe for target 'override_dh_auto_test' failed make[1]: *** [override_dh_auto_test] Error 1 make[1]: Leaving directory '/<>/biojava4-live-4.1.0+dfsg' debian/rules:10: recipe for target 'build-indep' failed make: *** [build-indep] Error 2 dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2 For a full build log please see: https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/biojava4-live.html Note: Even if this package is Arch:all, please consider uploading in source-only form, so that we get official build logs available here: https://buildd.debian.org/status/package.php?p=biojava4-live Thanks.
Processed: Re: Bug#843682: openssl: 'openssl dsaparam 2048 -out file' hangs, trying to read from stdin
Processing commands for cont...@bugs.debian.org: > reassign 843682 sendmail Bug #843682 [openssl] openssl: 'openssl dsaparam 2048 -out file' hangs, trying to read from stdin Bug reassigned from package 'openssl' to 'sendmail'. No longer marked as found in versions openssl/1.1.0b-2. Ignoring request to alter fixed versions of bug #843682 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 843682: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843682 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#843693: sddm: starting sddm results in white screen with active cursor and keyboard
Processing control commands: > severity -1 important Bug #843693 [sddm] sddm: starting sddm results in white screen with active cursor and keyboard Severity set to 'important' from 'grave' -- 843693: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843693 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#837824 tagged as pending
Processing commands for cont...@bugs.debian.org: > tag 837824 pending Bug #837824 [src:goffice] goffice: FTBFS due to undeclared build dependencies Ignoring request to alter tags of bug #837824 to the same tags previously set > -- Stopping processing here. Please contact me if you need assistance. -- 837824: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837824 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#837824: Fix uploaded to delayed/5
tag 837824 + pending Hi, I've just uploaded a fixed package to delayed/5, and committed the changes to git. Feel free to revert if you see a problem with this. Jordi -- Jordi Mallach Pérez -- Debian developer http://www.debian.org/ jo...@sindominio.net jo...@debian.org http://www.sindominio.net/ GnuPG public key information available at http://oskuro.net/ signature.asc Description: PGP signature
Processed (with 4 errors): Fix uploaded to delayed/5
Processing commands for cont...@bugs.debian.org: > tag 837824 + pending Bug #837824 [src:goffice] goffice: FTBFS due to undeclared build dependencies Added tag(s) pending. > Hi, Unknown command or malformed arguments to command. > I've just uploaded a fixed package to delayed/5, and committed the changes Unknown command or malformed arguments to command. > to git. Feel free to revert if you see a problem with this. Unknown command or malformed arguments to command. > Jordi Unknown command or malformed arguments to command. > -- Stopping processing here. Please contact me if you need assistance. -- 837824: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837824 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#842939: xul-ext-wot: WOT find guilty to sell user data
According to the analysis by Mike Kuketz (https://www.kuketz-blog.de/wot-addon-wie-ein-browser-addon-seine-nutzer-ausspaeht/), the (most?) problematic commit is of 2015-04-20 (https://github.com/mywot/firefox-xul/commit/0df107cae8ac18901bd665acace4b369c244a3f9). This would mean, that users of stable were less (not?) affected. I would remove the plugin anyway, just because of "trust issues". -- Teacher: "Now, if give you five apples, and then take three of them away, what are you left with?" Pupil: "Trust issues."
Bug#839478: marked as done (python-aiohttp: FTBFS: E: Build killed with signal TERM after 150 minutes of inactivity)
Your message dated Tue, 08 Nov 2016 22:21:57 + with message-id and subject line Bug#839478: fixed in python-aiohttp 1.1.2-1 has caused the Debian Bug report #839478, regarding python-aiohttp: FTBFS: E: Build killed with signal TERM after 150 minutes of inactivity 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.) -- 839478: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=839478 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-aiohttp Version: 0.22.4-1 Severity: serious Tags: stretch sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20161001 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): > creating build/temp.linux-x86_64-3.5-pydebug/aiohttp > x86_64-linux-gnu-gcc -pthread -g -Og -Wall -Wstrict-prototypes -g -O2 > -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC > -I/usr/include/python3.5dm -c aiohttp/_websocket.c -o > build/temp.linux-x86_64-3.5-pydebug/aiohttp/_websocket.o > x86_64-linux-gnu-gcc -pthread -shared -Wl,-O1 -Wl,-Bsymbolic-functions > -Wl,-z,relro -Wl,-z,relro -g -O2 -fdebug-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time > -D_FORTIFY_SOURCE=2 build/temp.linux-x86_64-3.5-pydebug/aiohttp/_websocket.o > -o > /<>/.pybuild/pythonX.Y-dbg_3.5/build/aiohttp/_websocket.cpython-35dm-x86_64-linux-gnu.so >dh_auto_test -O--buildsystem=pybuild > I: pybuild base:184: cd /<>/.pybuild/pythonX.Y_3.5/build; > python3.5 -m pytest /<>/tests > = test session starts > == > platform linux -- Python 3.5.2+, pytest-3.0.2, py-1.4.31, pluggy-0.3.1 > rootdir: /<>, inifile: > collected 1408 items / 1 skipped > > ../../../tests/test_classbasedview.py .FFF > ../../../tests/test_client_connection.py . > ../../../tests/test_client_functional.py ...FF.F > ../../../tests/test_client_functional_oldstyle.py > FF.F...Fdebian/rules:9: recipe for target > 'build' failed > make: *** [build] Terminated > E: Build killed with signal TERM after 150 minutes of inactivity If the failure looks somehow time/timezone related: Note that this rebuild was performed without the 'tzdata' package installed in the chroot. tzdata used be (transitively) part of build-essential, but it no longer is. If this package requires it to build, it should be added to build-depends. For the release team's opinion on this, see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836940#185 If the failure looks LSB-related: similarly to tzdata, lsb-base is not installed in the build chroot. The full build log is available from: http://aws-logs.debian.net/2016/10/01/python-aiohttp_0.22.4-1_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 --- --- Begin Message --- Source: python-aiohttp Source-Version: 1.1.2-1 We believe that the bug you reported is fixed in the latest version of python-aiohttp, 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 839...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Piotr Ożarowski (supplier of updated python-aiohttp 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: Tue, 08 Nov 2016 22:58:56 +0100 Source: python-aiohttp Binary: python3-aiohttp python3-aiohttp-dbg Architecture: source amd64 Version: 1.1.2-1 Distribution: unstable Urgency: medium Maintainer: Debian Python Modules Team Changed-By: Piotr Ożarowski Description: python3-aiohttp - http client/server for asyncio python3-aiohttp-dbg - http client/server for asyncio - debug version Closes: 830567 833254 835299 839478 Changes: python-aiohttp (1.1.2-1) unstable;
Processed: closing 838778
Processing commands for cont...@bugs.debian.org: > close 838778 0.33.3-10 Bug #838778 [libatk-wrapper-java] libatk-wrapper-java: crashes JVM when launching a java application Marked as fixed in versions java-atk-wrapper/0.33.3-10. Bug #838778 [libatk-wrapper-java] libatk-wrapper-java: crashes JVM when launching a java application Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 838778: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=838778 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#838778: libatk-wrapper-java: crashes JVM when launching a java application
Control: clone -1 -2 Control: retitle -2 libatk-wrapper-java: gets instance from jaw thread Control: severity -2 important Control: done -1 0.33.3-10 Hello, Uh, that's odd: I can't find your original report in my mails, so I completely missed it. That assertion is indeed quite harsh, and may trigger while running a screen reader. I didn't intend to keep it applied actually, it just happened to slip in while committing something else :/ Such a case condition can indeed pose problems in some very rare conditions. I have thus replaced the assertion with just a warning, so that you don't systematically get a crash, and if there are odd things happening, we have a clue that it might be because of this case. Samuel
Bug#839478: marked as done (python-aiohttp: FTBFS: E: Build killed with signal TERM after 150 minutes of inactivity)
Your message dated Tue, 08 Nov 2016 22:06:37 + with message-id and subject line Bug#839478: fixed in python-aiohttp 1.1.1-1 has caused the Debian Bug report #839478, regarding python-aiohttp: FTBFS: E: Build killed with signal TERM after 150 minutes of inactivity 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.) -- 839478: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=839478 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-aiohttp Version: 0.22.4-1 Severity: serious Tags: stretch sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20161001 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): > creating build/temp.linux-x86_64-3.5-pydebug/aiohttp > x86_64-linux-gnu-gcc -pthread -g -Og -Wall -Wstrict-prototypes -g -O2 > -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC > -I/usr/include/python3.5dm -c aiohttp/_websocket.c -o > build/temp.linux-x86_64-3.5-pydebug/aiohttp/_websocket.o > x86_64-linux-gnu-gcc -pthread -shared -Wl,-O1 -Wl,-Bsymbolic-functions > -Wl,-z,relro -Wl,-z,relro -g -O2 -fdebug-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time > -D_FORTIFY_SOURCE=2 build/temp.linux-x86_64-3.5-pydebug/aiohttp/_websocket.o > -o > /<>/.pybuild/pythonX.Y-dbg_3.5/build/aiohttp/_websocket.cpython-35dm-x86_64-linux-gnu.so >dh_auto_test -O--buildsystem=pybuild > I: pybuild base:184: cd /<>/.pybuild/pythonX.Y_3.5/build; > python3.5 -m pytest /<>/tests > = test session starts > == > platform linux -- Python 3.5.2+, pytest-3.0.2, py-1.4.31, pluggy-0.3.1 > rootdir: /<>, inifile: > collected 1408 items / 1 skipped > > ../../../tests/test_classbasedview.py .FFF > ../../../tests/test_client_connection.py . > ../../../tests/test_client_functional.py ...FF.F > ../../../tests/test_client_functional_oldstyle.py > FF.F...Fdebian/rules:9: recipe for target > 'build' failed > make: *** [build] Terminated > E: Build killed with signal TERM after 150 minutes of inactivity If the failure looks somehow time/timezone related: Note that this rebuild was performed without the 'tzdata' package installed in the chroot. tzdata used be (transitively) part of build-essential, but it no longer is. If this package requires it to build, it should be added to build-depends. For the release team's opinion on this, see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836940#185 If the failure looks LSB-related: similarly to tzdata, lsb-base is not installed in the build chroot. The full build log is available from: http://aws-logs.debian.net/2016/10/01/python-aiohttp_0.22.4-1_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 --- --- Begin Message --- Source: python-aiohttp Source-Version: 1.1.1-1 We believe that the bug you reported is fixed in the latest version of python-aiohttp, 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 839...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Piotr Ożarowski (supplier of updated python-aiohttp 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: Tue, 08 Nov 2016 22:46:23 +0100 Source: python-aiohttp Binary: python3-aiohttp python3-aiohttp-dbg Architecture: source amd64 Version: 1.1.1-1 Distribution: unstable Urgency: medium Maintainer: Debian Python Modules Team Changed-By: Piotr Ożarowski Description: python3-aiohttp - http client/server for asyncio python3-aiohttp-dbg - http client/server for asyncio - debug version Closes: 830567 833254 835299 839478 Changes: python-aiohttp (1.1.1-1) unstable;
Processed (with 1 error): Re: Bug#838778: libatk-wrapper-java: crashes JVM when launching a java application
Processing control commands: > clone -1 -2 Bug #838778 [libatk-wrapper-java] libatk-wrapper-java: crashes JVM when launching a java application Bug 838778 cloned as bug 843706 > retitle -2 libatk-wrapper-java: gets instance from jaw thread Bug #843706 [libatk-wrapper-java] libatk-wrapper-java: crashes JVM when launching a java application Changed Bug title to 'libatk-wrapper-java: gets instance from jaw thread' from 'libatk-wrapper-java: crashes JVM when launching a java application'. > severity -2 important Bug #843706 [libatk-wrapper-java] libatk-wrapper-java: gets instance from jaw thread Severity set to 'important' from 'serious' > done -1 0.33.3-10 Unknown command or malformed arguments to command. -- 838778: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=838778 843706: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843706 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: severity of 843344 is important
Processing commands for cont...@bugs.debian.org: > severity 843344 important Bug #843344 [pgadmin3] pgadmin3 segfaults on start Severity set to 'important' from 'grave' > thanks Stopping processing here. Please contact me if you need assistance. -- 843344: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843344 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#841163: [debian-mysql] Upload of MySQL 5.7.16 security update to unstable
On Mon, Nov 07, 2016 at 06:44:57AM -0800, Lars Tangvald wrote: > Hi all, > > We prepared a security upload for the Oracle October 2016 CPU, but we need > someone with access to sponsor the upload to Debian unstable. Is anyone > available to do this? > The source should be ready to go from > https://anonscm.debian.org/cgit/pkg-mysql/mysql.git Hi Lars, Now uploaded. Cheers, Dominic.
Bug#841163: marked as done (Security fixes from the October 2016 CPU)
Your message dated Tue, 08 Nov 2016 21:51:42 + with message-id and subject line Bug#841163: fixed in mysql-5.7 5.7.16-1 has caused the Debian Bug report #841163, regarding Security fixes from the October 2016 CPU 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.) -- 841163: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841163 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: mysql-5.7 Version: 5.7.15-1 Severity: grave Tags: security upstream fixed-upstream The Oracle Critical Patch Update for October 2016 will be released on Tuesday, October 18. According to the pre-release announcement [1], it will contain information about CVEs fixed in MySQL 5.7.16. The CVE numbers will be available when the CPU is released. Regards, Norvald H. Ryeng [1] http://www.oracle.com/technetwork/security-advisory/cpuoct2016-2881722.html --- End Message --- --- Begin Message --- Source: mysql-5.7 Source-Version: 5.7.16-1 We believe that the bug you reported is fixed in the latest version of mysql-5.7, 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 841...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Lars Tangvald (supplier of updated mysql-5.7 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: Fri, 21 Oct 2016 08:59:56 +0200 Source: mysql-5.7 Binary: libmysqlclient20 libmysqld-dev libmysqlclient-dev mysql-client-core-5.7 mysql-client-5.7 mysql-server-core-5.7 mysql-server-5.7 mysql-server mysql-client mysql-testsuite mysql-testsuite-5.7 mysql-source-5.7 Architecture: source Version: 5.7.16-1 Distribution: unstable Urgency: high Maintainer: Debian MySQL Maintainers Changed-By: Lars Tangvald Description: libmysqlclient-dev - MySQL database development files libmysqlclient20 - MySQL database client library libmysqld-dev - MySQL embedded database development files mysql-client - MySQL database client (metapackage depending on the latest versio mysql-client-5.7 - MySQL database client binaries mysql-client-core-5.7 - MySQL database core client binaries mysql-server - MySQL database server (metapackage depending on the latest versio mysql-server-5.7 - MySQL database server binaries and system database setup mysql-server-core-5.7 - MySQL database server binaries mysql-source-5.7 - MySQL source mysql-testsuite - MySQL regression tests mysql-testsuite-5.7 - MySQL 5.7 testsuite Closes: 841163 Changes: mysql-5.7 (5.7.16-1) unstable; urgency=high (security fixes) . * Imported upstream version 5.7.16 to fix security issues: - http://www.oracle.com/technetwork/security-advisory/cpuoct2016-2881722.html - CVE-2016-5584 CVE-2016-6304 CVE-2016-6662 CVE-2016-7440 Note that CVE-2016-6662 is listed both for this release and the previous. The CVE-2016-6662 related changes in 5.7.16 do not affect Linux packages. Thanks to Bjoern Boschman for the version update. (Closes: #841163) Checksums-Sha1: 608f1ab134e63eb6137b35bac4d07511b5eb6063 3213 mysql-5.7_5.7.16-1.dsc 42d15b07bed4d364a9eff294b0a198d2b9f71fe3 60556473 mysql-5.7_5.7.16.orig.tar.gz 3d92006191f0ba3c9943efae081b49f7d70e0f7e 3382888 mysql-5.7_5.7.16-1.debian.tar.xz Checksums-Sha256: 23bd4abca9de7938f8dfa206113503b258ca18465a9b791b23d3e05a34196634 3213 mysql-5.7_5.7.16-1.dsc 43fc282f807353ff77ead21efb5f85f7f214c2a5362762a8cc370ae1c075095a 60556473 mysql-5.7_5.7.16.orig.tar.gz fc6bd67619d4479c0581ffa83949d7b1e5e4dbd640f49e7dc874c3623167051d 3382888 mysql-5.7_5.7.16-1.debian.tar.xz Files: 0bf047a13e222802319c83ea29299298 3213 database optional mysql-5.7_5.7.16-1.dsc f7724b816919878760b5c7c9956e6508 60556473 database optional mysql-5.7_5.7.16.orig.tar.gz 0be62f270019b71c6269fd86ede5f640 3382888 database optional mysql-5.7_5.7.16-1.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJYIkVlAAoJEMAFfnFNaU+ys0wP/jfXOZhIdPoZaDFYyL7YrAaa ik1nNlo4/R7P9tqgtP73Ht17DxtbXXyjFs4uMiLYCHEZ2mejE1I48Bl5SGWa2OTA hHQHH+4GU2XOvpK7Gt1SbTlUgTi4zsn4A6tMhRqHslGbO8M2hvHbmE4Emv9ZHhXM sG2fgb+pUolTTKqvMzDBhdk62ZwIkzZ1XQB74JTXypwHE7MW6+DkwysP2T03WOAl 319y2Hdj+07P6UKYO9IhM8JIn+/U15gezU2NH2r4fjvLhKRY
Processed: Bug#839478 marked as pending
Processing commands for cont...@bugs.debian.org: > tag 839478 pending Bug #839478 [src:python-aiohttp] python-aiohttp: FTBFS: E: Build killed with signal TERM after 150 minutes of inactivity Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 839478: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=839478 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#839478: marked as pending
tag 839478 pending thanks Hello, Bug #839478 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=python-modules/packages/python-aiohttp.git;a=commitdiff;h=c594768 --- commit c5947689b78d3561dfbf10a23d5b07a11c5133aa Author: Piotr Ożarowski Date: Tue Nov 8 22:46:28 2016 +0100 mention bugs fixed by this upload in changelog diff --git a/debian/changelog b/debian/changelog index e5a69b7..6723bcd 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,8 +1,12 @@ -python-aiohttp (1.1.1-1) UNRELEASED; urgency=medium +python-aiohttp (1.1.1-1) unstable; urgency=medium * New upstream release +- works with new multidict (closes: 835299) +- decompresses HTTP bodies (closes: 833254) + * tests disabled for now (see comment in debian/rules) +closes: 830567, 839478 - -- Piotr Ożarowski Sun, 06 Nov 2016 15:13:03 +0100 + -- Piotr Ożarowski Tue, 08 Nov 2016 22:46:23 +0100 python-aiohttp (0.22.4-1) unstable; urgency=medium
Bug#843675: marked as done (asn1c-doc: fails to upgrade from 'testing' - trying to overwrite /usr/share/doc-base/asn1c)
Your message dated Tue, 08 Nov 2016 21:33:37 + with message-id and subject line Bug#843675: fixed in asn1c 0.9.27+dfsg-4 has caused the Debian Bug report #843675, regarding asn1c-doc: fails to upgrade from 'testing' - trying to overwrite /usr/share/doc-base/asn1c 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.) -- 843675: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843675 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: asn1c-doc Version: 0.9.27+dfsg-3 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'testing'. It installed fine in 'testing', then the upgrade to 'sid' 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 asn1c-doc. Preparing to unpack .../asn1c-doc_0.9.27+dfsg-3_all.deb ... Unpacking asn1c-doc (0.9.27+dfsg-3) ... dpkg: error processing archive /var/cache/apt/archives/asn1c-doc_0.9.27+dfsg-3_all.deb (--unpack): trying to overwrite '/usr/share/doc-base/asn1c', which is also in package asn1c 0.9.24+dfsg-1 Errors were encountered while processing: /var/cache/apt/archives/asn1c-doc_0.9.27+dfsg-3_all.deb cheers, Andreas asn1c=0.9.24+dfsg-1_asn1c-doc=0.9.27+dfsg-3.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: asn1c Source-Version: 0.9.27+dfsg-4 We believe that the bug you reported is fixed in the latest version of asn1c, 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 843...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Eugene Seliverstov (supplier of updated asn1c 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, 08 Nov 2016 21:47:19 +0300 Source: asn1c Binary: asn1c asn1c-doc Architecture: source Version: 0.9.27+dfsg-4 Distribution: unstable Urgency: medium Maintainer: Eugene Seliverstov Changed-By: Eugene Seliverstov Description: asn1c - ASN.1 compiler for C asn1c-doc - Documentation for asn1c Closes: 843675 Changes: asn1c (0.9.27+dfsg-4) unstable; urgency=medium . * Fixed upgrading from monolith package (closes: #843675) * Adjusted short description for asn1c-doc * Adjusted Depends and Multi-Arch for asn1c-doc package Checksums-Sha1: f60f85d0e48429db04f4e5e2b646f869dac8bb0d 2080 asn1c_0.9.27+dfsg-4.dsc 6fd4568c5f1e65b1bb779877ee6ccab166f9b7e8 7128 asn1c_0.9.27+dfsg-4.debian.tar.xz Checksums-Sha256: a09dd103affd43c504d771734d40f50e5c733cf02d89e1aaf2a68a762f00a6f7 2080 asn1c_0.9.27+dfsg-4.dsc 51e3d6ad7f2f9dded1823008d68f154f78490ccbaedb496539e7a5be555c9fa6 7128 asn1c_0.9.27+dfsg-4.debian.tar.xz Files: f830239ce7480cde0320164693a6f2aa 2080 devel extra asn1c_0.9.27+dfsg-4.dsc 13e1237c88df272b7f463174d6ca469b 7128 devel extra asn1c_0.9.27+dfsg-4.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQIcBAEBCAAGBQJYIj4OAAoJEPNPCXROn13ZRxIQAMmjsSXqZkkL41uNLngFdiQW lx8aj9pmPiWDH8JS8mWCXLQVblmvyQh/2y903qtwlRWg08I49R70o1iF0emSMYuf IvOJwwFD87K0zTCPSd2Iux1BNCofXr+Ui1jf1j/Z6vn/3xkGbToPQGhk6serVTYt Sj7bgk1+nXw/In4cngk7FJj9WBgaH32CcDYsHXpNo4qjZHBtcFX1EYhEddteeJ6Z ctedXFIap/Y3vHLIpEnSls0y7UKvh7LBcCmEEDot+yTfOikhhZoMwus7cjGbHAMw 70QgGrSC+PKgeddSLjcbk6IeBqoZTa5KhNtSa4J+EoeVQyujJwzKMbBNzeQEEyAI eBKhQ7eeGaTnI8AILwY6156IAKpIeDWntaBjitD4eWABpltampgmiOMHdnqj7o3+ HsZ5CiqLdSLFUFZ/Mf2m9jN1n100msN547LUz+S0vzbpeuiFWUS6PYSB7OmGJAUz 8dFZaFEOT/qZfdbyMIMtyDOcjc8Ml4/8Jq9O9EEhRxUejqr/hpkWnsCoyLFWXJ0D LSj4aNRjloEsc8k2jed3tdxeDkHSKvPK2GjTL72xi5XfTpiNS9lHBfo2c2BlUc9p 6MnhuLi+gzdHpJnOlHgCGLBsob9HIIiC4AGB9BiS+GENaIksYVfRyL7rWqAS/+Mu 3j1kcQ6bgUe7gKUSx7jY =5iEJ -END PGP SIGNATURE End Message ---
Bug#828607: marked as done (xml-security-c: FTBFS with openssl 1.1.0)
Your message dated Tue, 08 Nov 2016 21:37:58 + with message-id and subject line Bug#828607: fixed in xml-security-c 1.7.3-4 has caused the Debian Bug report #828607, regarding xml-security-c: FTBFS with openssl 1.1.0 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.) -- 828607: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828607 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: xml-security-c Version: 1.7.3-1 Severity: important Control: block 827061 by -1 Hi, OpenSSL 1.1.0 is about to released. During a rebuild of all packages using OpenSSL this package fail to build. A log of that build can be found at: https://breakpoint.cc/openssl-1.1-rebuild-2016-05-29/Attempted/xml-security-c_1.7.3-1_amd64-20160529-1555 On https://wiki.openssl.org/index.php/1.1_API_Changes you can see various of the reasons why it might fail. There are also updated man pages at https://www.openssl.org/docs/manmaster/ that should contain useful information. There is a libssl-dev package available in experimental that contains a recent snapshot, I suggest you try building against that to see if everything works. If you have problems making things work, feel free to contact us. Kurt --- End Message --- --- Begin Message --- Source: xml-security-c Source-Version: 1.7.3-4 We believe that the bug you reported is fixed in the latest version of xml-security-c, 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 828...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ferenc Wágner (supplier of updated xml-security-c 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: Tue, 08 Nov 2016 21:52:45 +0100 Source: xml-security-c Binary: libxml-security-c17v5 libxml-security-c-dev xml-security-c-utils Architecture: source Version: 1.7.3-4 Distribution: unstable Urgency: medium Maintainer: Debian Shib Team Changed-By: Ferenc Wágner Description: libxml-security-c-dev - C++ library for XML Digital Signatures (development) libxml-security-c17v5 - C++ library for XML Digital Signatures (runtime) xml-security-c-utils - C++ library for XML Digital Signatures (utilities) Closes: 828607 Changes: xml-security-c (1.7.3-4) unstable; urgency=medium . [ Etienne Dysli Metref ] * [73c1622] Add myself to uploaders . [ Ferenc Wágner ] * [dd93312] Stay with OpenSSL 1.0 (Closes: #828607) * [d775f9f] Migrate to my Debian address Checksums-Sha1: b64e643c821f47a7d1e37644206a620b95c4a586 2294 xml-security-c_1.7.3-4.dsc b832b5755907ba0c7f3352ea15f8f0bd8cfb3c5a 41836 xml-security-c_1.7.3-4.debian.tar.xz Checksums-Sha256: 85c6d93176760145390095533fd37baeb3abec1f68905ff388e8eb76e58820de 2294 xml-security-c_1.7.3-4.dsc 54b629cd9ba1e54461d1cbbffe947949da1eca5b81125feb19f28be63f2fc327 41836 xml-security-c_1.7.3-4.debian.tar.xz Files: c84d2021cd65bdf4bad057aec306dfe6 2294 libs extra xml-security-c_1.7.3-4.dsc 85855e212d7f5a31598120bad6d12213 41836 libs extra xml-security-c_1.7.3-4.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCgAGBQJYIjyAAAoJEDrI9xZHftsjzWcQALOLuCvwDxcY9ZQpnNvuU1TO hWM4CLDBU7MfFXzwVqpjMAAglgVDf2uJHxjb8jbWlKZ7Z/sfgtD6OaxUrYTQ63AC 2w1r5IjjULjTdXeOlp3LwAnATLABly5ueQRwd9bCUILyEbkRDrPdrVXE5tCv4DY7 h/tjAUZeNACXrCabeHODVYhNPZW3AqMvwzt1G79VSAb0udn7XPLyurwVDWjIUPxZ ErHDoM6qa3/lbkdkmNhJrBfliJLn2okgdqPEmWJF0o+TaqbQnekvxJ80PAb+K10s fkIfRbHN2k3pmalxuigjc9H9/BJ3jWRIq/GhveE74mnderXEKg4xqClE0QpERsCG cbILb15TsnnfFu2LXKtTrMYEfnXlGbdWIhP4a42zXUnF34i+oWhmHeGOHSzO5ove BPHFn7uu4P1wUNuWqhZSyRd7ZbCFCpkzoorBPjGTsl01D1aKjaCRblmx1DgSPaaA jWeCuj2Tnm6JG0EI4scWQcpvkwXGfH6z+DbMxq4XpHxmht0bx+Ltm6n5zBWk+dIi CYXhmNa1PjswKT4I1AwiwZGhWwuOCL1DUOD8sh9rM1AlPFpndURJctCKNkdUCnVc oVWPPU8iHn+CNKrOA7Ptl8q6Pl+T4FVqeoJsbanE46Q9VIdU4WHUsjxYLhLgX9Uv qs/HE3NRmQ3/Y0JaAsYm =dVlu -END PGP SIGNATURE End Message ---
Bug#842878: Asterisk crashes with pjproject 2.5.5
> "BS" == Bernhard Schmidt writes: BS> Nothing productive on the upstream mailinglist (or rather disturbing, BS> they say that ABI can change in backward incompatible way even in minor BS> versions and you're always expected to recompile), That isn't anything new, they've always said so. -JimC -- James Cloos OpenPGP: 0x997A9F17ED7DAEA6
Bug#840416: xine fails to start due to missing libvdpau_i965.so
On Tue, Oct 11, 2016 at 02:19:37PM +0200, Michal Hocko wrote: > Package: xine-ui > Version: 0.99.9-1.2+b2 > Severity: grave > > I cannot seem to be able to start xine (standalone without any > particular file to open) due to: > Failed to open VDPAU backend libvdpau_i965.so: cannot open shared object > file: No such file or directory > vo_vdpau: Can't create vdp device : No vdpau implementation. The above is normal. > X Error of failed request: BadMatch (invalid parameter attributes) > Major opcode of failed request: 151 (XVideo) > Minor opcode of failed request: 17 () > Serial number of failed request: 2868 > Current serial number in output stream: 2868 >... What is the output of "xvinfo" (in the x11-utils package)? Does "xine -V sdl" work? > Thanks >... Thanks Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said. Pearl S. Buck - Dragon Seed
Bug#843432: Pending fixes for bugs in the libwww-curl-perl package
tag 843432 + pending thanks Some bugs in the libwww-curl-perl package are closed in revision d83b9f79243f28d9c1f4bc6f2016bc5a4cb859e1 in branch 'master' by Salvatore Bonaccorso The full diff can be seen at https://anonscm.debian.org/cgit/pkg-perl/packages/libwww-curl-perl.git/commit/?id=d83b9f7 Commit message: Skip preprocessor symbol only CURL_STRICTER Fixes "FTBFS: error: 'CURL_STRICTER' undeclared". Thanks: Niko Tyni Closes: #843432
Processed: Pending fixes for bugs in the libwww-curl-perl package
Processing commands for cont...@bugs.debian.org: > tag 843432 + pending Bug #843432 [libwww-curl-perl] libwww-curl-perl: FTBFS: error: 'CURL_STRICTER' undeclared Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 843432: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843432 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#828250: marked as done (boinc: FTBFS with openssl 1.1.0)
Your message dated Tue, 8 Nov 2016 22:20:52 +0100 with message-id <4be695ef-4cd9-5624-5e2d-96f21c1e5...@debian.org> and subject line boinc: FTBFS with openssl 1.1.0 has caused the Debian Bug report #828250, regarding boinc: FTBFS with openssl 1.1.0 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.) -- 828250: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828250 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: boinc Version: 7.6.32+dfsg-2 Severity: important Control: block 827061 by -1 Hi, OpenSSL 1.1.0 is about to released. During a rebuild of all packages using OpenSSL this package fail to build. A log of that build can be found at: https://breakpoint.cc/openssl-1.1-rebuild-2016-05-29/Attempted/boinc_7.6.32+dfsg-2_amd64-20160529-1408 On https://wiki.openssl.org/index.php/1.1_API_Changes you can see various of the reasons why it might fail. There are also updated man pages at https://www.openssl.org/docs/manmaster/ that should contain useful information. There is a libssl-dev package available in experimental that contains a recent snapshot, I suggest you try building against that to see if everything works. If you have problems making things work, feel free to contact us. Kurt --- End Message --- --- Begin Message --- closing G. signature.asc Description: OpenPGP digital signature --- End Message ---
Bug#828565: marked as done (syslog-ng: FTBFS with openssl 1.1.0)
Your message dated Tue, 08 Nov 2016 21:22:08 + with message-id and subject line Bug#828565: fixed in syslog-ng 3.8.1-5 has caused the Debian Bug report #828565, regarding syslog-ng: FTBFS with openssl 1.1.0 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.) -- 828565: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828565 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: syslog-ng Version: 3.5.6-2.1 Severity: important Control: block 827061 by -1 Hi, OpenSSL 1.1.0 is about to released. During a rebuild of all packages using OpenSSL this package fail to build. A log of that build can be found at: https://breakpoint.cc/openssl-1.1-rebuild-2016-05-29/Attempted/syslog-ng_3.5.6-2.1_amd64-20160529-1543 On https://wiki.openssl.org/index.php/1.1_API_Changes you can see various of the reasons why it might fail. There are also updated man pages at https://www.openssl.org/docs/manmaster/ that should contain useful information. There is a libssl-dev package available in experimental that contains a recent snapshot, I suggest you try building against that to see if everything works. If you have problems making things work, feel free to contact us. Kurt --- End Message --- --- Begin Message --- Source: syslog-ng Source-Version: 3.8.1-5 We believe that the bug you reported is fixed in the latest version of syslog-ng, 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 828...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. SZALAY Attila (supplier of updated syslog-ng 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: Sat, 05 Nov 2016 19:09:39 +0100 Source: syslog-ng Binary: syslog-ng syslog-ng-dbg syslog-ng-dev syslog-ng-core syslog-ng-mod-journal syslog-ng-mod-json syslog-ng-mod-mongodb syslog-ng-mod-sql syslog-ng-mod-smtp syslog-ng-mod-amqp syslog-ng-mod-geoip syslog-ng-mod-redis syslog-ng-mod-stomp syslog-ng-mod-riemann syslog-ng-mod-graphite syslog-ng-mod-python syslog-ng-mod-add-contextual-data Architecture: source amd64 all Version: 3.8.1-5 Distribution: unstable Urgency: medium Maintainer: syslog-ng maintainers Changed-By: SZALAY Attila Description: syslog-ng - Enhanced system logging daemon (metapackage) syslog-ng-core - Enhanced system logging daemon (core) syslog-ng-dbg - Enhanced system logging daemon (debug symbols) syslog-ng-dev - Enhanced system logging daemon (development files) syslog-ng-mod-add-contextual-data - Enhanced system logging daemon (add-contextual-data) syslog-ng-mod-amqp - Enhanced system logging daemon (AMQP plugin) syslog-ng-mod-geoip - Enhanced system logging daemon (GeoIP plugin) syslog-ng-mod-graphite - Enhanced system logging daemon (graphite plugin) syslog-ng-mod-journal - Enhanced system logging daemon (systemd journal plugin) syslog-ng-mod-json - Enhanced system logging daemon (JSON plugin) syslog-ng-mod-mongodb - Enhanced system logging daemon (MongoDB plugin) syslog-ng-mod-python - Enhanced system logging daemon (Python plugin) syslog-ng-mod-redis - Enhanced system logging daemon (Redis plugin) syslog-ng-mod-riemann - Enhanced system logging daemon (Riemann destination) syslog-ng-mod-smtp - Enhanced system logging daemon (SMTP plugin) syslog-ng-mod-sql - Enhanced system logging daemon (SQL plugin) syslog-ng-mod-stomp - Enhanced system logging daemon (STOMP plugin) Closes: 828565 839449 Changes: syslog-ng (3.8.1-5) unstable; urgency=medium . * [05e9749] Revert export method to head. Much cleaner and can be changed in parameter list if needed * [6b49e04] Added basic test to check if syslog-ng can start * [80260f3] Added tzdata dependency, needed by a testcase. Because tzdata is neither essential nor build-essential package explicit build-dependency is needed. (Closes: #839449) * [e68e244] Upgraded ABI version to 3.8 * [1241045] Temporally stay with the libssl-1.0 until upstream fix this (Closes: #828565) * [c8dc698] Added dependency to lsb-base as lintian suggested Checksums-Sha1: 98cc240f9455cb9ba4cffaf853360960e7815c07 3667 syslog-ng_3.8.1-5.dsc 68632e13e5201049bffe1a12498e7235ad00e5a9
Bug#835549: marked as done (boinc: FTBFS with openssl 1.1.0)
Your message dated Tue, 8 Nov 2016 22:20:52 +0100 with message-id <4be695ef-4cd9-5624-5e2d-96f21c1e5...@debian.org> and subject line boinc: FTBFS with openssl 1.1.0 has caused the Debian Bug report #828250, regarding boinc: FTBFS with openssl 1.1.0 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.) -- 828250: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828250 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: alljoyn-core-1504 Version: 15.04b-1 Severity: important Control: block 827061 by -1 Hi, OpenSSL 1.1.0 is about to released. During a rebuild of all packages using OpenSSL this package fail to build. A log of that build can be found at: https://breakpoint.cc/openssl-1.1-rebuild-2016-08-26/failed/boinc_7.6.33%2Bdfsg-1_amd64-2016-08-26T18%3A07%3A27Z On https://wiki.openssl.org/index.php/1.1_API_Changes you can see various of the reasons why it might fail. There are also updated man pages at https://www.openssl.org/docs/manmaster/ that should contain useful information. There is a libssl-dev package available in experimental that contains a recent snapshot, I suggest you try building against that to see if everything works. If you have problems making things work, feel free to contact us. Kurt --- End Message --- --- Begin Message --- closing G. signature.asc Description: OpenPGP digital signature --- End Message ---
Bug#843682: [Pkg-openssl-devel] Bug#843682: openssl: 'openssl dsaparam 2048 -out file' hangs, trying to read from stdin
On Tue, Nov 08, 2016 at 07:36:42PM +0100, Andreas Beckmann wrote: > Package: openssl > Version: 1.1.0b-2 > Severity: serious > > Hi, > > I just noticed that the sendmail postinst hangs on > > openssl dsaparam 2048 -out file The 2048 should be the last parameter, like it has always been documented. It's now trying to read DSA parameters from stdin, instead of generating them. Kurt
Processed: Bug#843691 marked as pending
Processing commands for cont...@bugs.debian.org: > tag 843691 pending Bug #843691 [src:glibc] glibc: FTBFS on ppc64el: Error: operand out of range Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 843691: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843691 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#843691: marked as pending
tag 843691 pending thanks Hello, Bug #843691 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=pkg-glibc/glibc.git;a=commitdiff;h=4e62582 --- commit 4e625825c81093eb26537891d4c57561d089a981 Author: Aurelien Jarno Date: Tue Nov 8 22:12:55 2016 +0100 Add bug number diff --git a/debian/changelog b/debian/changelog index 93d0f09..82b7346 100644 --- a/debian/changelog +++ b/debian/changelog @@ -18,6 +18,7 @@ glibc (2.24-6) UNRELEASED; urgency=medium [ Aurelien Jarno ] * debian/patches/git-updates.diff: update from upstream stable branch: - Fix pread/pwrite syscalls on SH4. +- Fix build on powerpc/ppc64el with binutils from trunk. Closes: #843691. - Fix flexible array usage in gconv.h. Closes: #841304. -- Aurelien Jarno Tue, 18 Oct 2016 23:17:42 +0200
Bug#837450: faumachine: FTBFS with bindnow and PIE enabled
Hi Balint,
thanks for the bug report.
I think this is in fact a problem with PIE: FAUmachine uses a just-in-time
compiler based on qemu. This is where the error happens:
dyngen: unsupported X86_64 relocation (4)
Maybe the fix is as simple as:
diff --git a/configure.ac b/configure.ac
index 980ce16..695ec39 100644
--- a/configure.ac
+++ b/configure.ac
@@ -447,6 +447,7 @@ AC_PROG_CC_OPTION([-fno-strict-aliasing],
[fm_jit_gen_cflags="${fm_jit_gen_cflag
AC_PROG_CC_OPTION([-fno-reorder-blocks],
[fm_jit_gen_cflags="${fm_jit_gen_cflags} -fno-reorder-blocks"])
AC_PROG_CC_OPTION([-fno-ipa-icf], [fm_jit_gen_cflags="${fm_jit_gen_cflags}
-fno-ipa-icf"])
AC_PROG_CC_OPTION([-fno-gcse], [fm_jit_gen_cflags="${fm_jit_gen_cflags}
-fno-gcse"])
+AC_PROG_CC_OPTION([-fno-gcse], [fm_jit_gen_cflags="${fm_jit_gen_cflags}
-no-pie"])
AC_SUBST([fm_jit_gen_cflags])
# Compiler warnings (not needed but nice to have).
However I haven't tested this yet. Hopefully, I find some time this weekend, but
I cannot make any promises :/.
Cheers,
Stefan.
Bug#828618: marked as done (zeroinstall-injector: FTBFS with openssl 1.1.0)
Your message dated Tue, 8 Nov 2016 21:03:19 + with message-id and subject line Re: Bug#828618: zeroinstall-injector: FTBFS with openssl 1.1.0 has caused the Debian Bug report #828618, regarding zeroinstall-injector: FTBFS with openssl 1.1.0 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.) -- 828618: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828618 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: zeroinstall-injector Version: 2.10-2 Severity: important Control: block 827061 by -1 Hi, OpenSSL 1.1.0 is about to released. During a rebuild of all packages using OpenSSL this package fail to build. A log of that build can be found at: https://breakpoint.cc/openssl-1.1-rebuild-2016-05-29/Attempted/zeroinstall-injector_2.10-2_amd64-20160530-2117 On https://wiki.openssl.org/index.php/1.1_API_Changes you can see various of the reasons why it might fail. There are also updated man pages at https://www.openssl.org/docs/manmaster/ that should contain useful information. There is a libssl-dev package available in experimental that contains a recent snapshot, I suggest you try building against that to see if everything works. If you have problems making things work, feel free to contact us. Kurt --- End Message --- --- Begin Message --- On 26 June 2016 at 15:23, Kurt Roeckx wrote: > block 828618 by 828462 > thanks > > On Sun, Jun 26, 2016 at 03:15:30PM +0100, Thomas Leonard wrote: >> >> I don't mind. I guess blocks might be better, to remind me to test it >> when the ocaml-ssl bug is fixed. > > So I've set that. Just tested compiling 0install 2.12 on sid with "apt-get source zeroinstall-injector --compile" and it worked and produced a binary that runs with libssl.so.1.1, so closing. -- talex5 (GitHub/Twitter)http://roscidus.com/blog/ GPG: 5DD5 8D70 899C 454A 966D 6A51 7513 3C8F 94F6 E0CC GPG: DA98 25AE CAD0 8975 7CDA BD8E 0713 3F96 CA74 D8BA--- End Message ---
Processed: #842927 affects pytango
Processing commands for cont...@bugs.debian.org:
> affects 842927 src:pytango
Bug #842927 {Done: Dimitri John Ledkov }
[libboost-python1.62.0] libboost-python1.62.0 exports Python 2 symbols for
Python 3
Bug #842928 {Done: Dimitri John Ledkov }
[libboost-python1.62.0] libboost-python1.62.0 exports Python 2 symbols for
Python 3
Added indication that 842927 affects src:pytango
Added indication that 842928 affects src:pytango
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
842927: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=842927
842928: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=842928
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#843700: amanda-common: missing dependency on perlapi-*
Package: amanda-common
Version: 1:3.3.9-2
Severity: serious
X-Debbugs-Cc: p...@packages.debian.org
This package contains binary Perl modules but doesn't depend on perlapi-*
(currently perlapi-5.24.1).
Quoting the Debian Perl Policy 4.4.2 ("Binary and Other Architecture
Dependent Modules"):
Additionally, all binary modules (regardless of their installation
directory) and any other modules installed into $Config{vendorarch} must
depend on the expansion of perlapi-$Config{debian_abi} using the Config
module. If $Config{debian_abi} is empty or not set, $Config{version}
must be used.
This used to work (since #582220) but seems to have regressed recently
with 1:3.3.9-1 that switched to dh-style debian/rules, dropping the
'dh_perl -a usr/lib/amanda/perl' call. The default dh behaviour doesn't
know where to look for the private directory (which currently seems to
be /usr/lib//amanda/perl). Possibly something like
override_dh_perl:
dh_perl /usr/lib/*/amanda/perl
will do the trick.
Note that this is the root cause for #839603 / #839392: if the package had
had the correct dependencies, it would have been automatically binNMU'd
by the release team along with the other 600+ packages during the Perl
5.24 transition.
Even when this is fixed, partial upgrades of amanda-common from 1:3.3.9-1
without upgrading perl will be a problem, particularly as Ubuntu has
made a release with something based on 1:3.3.9-1. It looks like we need
to add a Breaks on the perl side to make sure broken combinations can't
happen.
--
Niko Tyni nt...@debian.org
Processed: bug 828608 is forwarded to https://lists.alioth.debian.org/pipermail/pkg-shibboleth-devel/2016-October/004315.html
Processing commands for cont...@bugs.debian.org: > forwarded 828608 > https://lists.alioth.debian.org/pipermail/pkg-shibboleth-devel/2016-October/004315.html Bug #828608 [src:xmltooling] xmltooling: FTBFS with openssl 1.1.0 Set Bug forwarded-to-address to 'https://lists.alioth.debian.org/pipermail/pkg-shibboleth-devel/2016-October/004315.html'. > thanks Stopping processing here. Please contact me if you need assistance. -- 828608: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828608 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#828449: net-snmp and openssl 1.1.0
On Tue, 1 Nov 2016 18:39:01 +0100 Andreas wrote: AH> Control: tags -1 + upstream patch AH> AH> Hello! AH> AH> The attached patch (in combination with the fix for #841554) AH> makes the Debian net-snmp package build against openssl 1.1.0. AH> This patch has only been compile-tested. No runtime testing. No AH> guarantees. Please review carefully. AH> AH> (Additional ifdefs likely needed to keep this compiling against AH> older openssl versions.) Thanks for attempting a patch. Can you create a bug report and attach your patch there? Thanks, Robert
Bug#843040: marked as done (libblosc1: Bitshuffle problems on bigendian architectures)
Your message dated Tue, 8 Nov 2016 21:06:35 +0100 with message-id <18332c63-c970-0476-269f-9f3442b30...@debian.org> and subject line Re: c-blosc: diff for NMU version 1.11.1+ds1-2.1 has caused the Debian Bug report #843040, regarding libblosc1: Bitshuffle problems on bigendian 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.) -- 843040: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843040 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libblosc1 Version: 1.11.1+ds1-2 Severity: important Dear Maintainer, it seems that the c-blosc library has some problems withthe bitshuffle filter on big-endian architectures. The problem causes several test failures on the pytables package [1, 2, 3] when tests are run on mips, s390x and other architectures (all bigendian it seems). The problem has been reported upstream [4, 5] and it is currently under investigation. If my understanding is correct a quick fix can be implememted by pproperly setting build flags but please refer to the upstream [4] for more details. [1] https://tracker.debian.org/pkg/pytables [2] https://buildd.debian.org/status/package.php?p=pytables [3] https://buildd.debian.org/status/fetch.php?pkg=pytables&arch=mips&ver=3.3.0-3&stamp=1478077059 [4] https://github.com/Blosc/c-blosc/issues/181 [5] https://github.com/PyTables/PyTables/issues/583 -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.8.0-27-generic (SMP w/4 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash Init: unable to detect Versions of packages libblosc1 depends on: ii libc6 2.24-5 ii liblz4-1 0.0~r131-2 ii libsnappy1v5 1.1.3-3 ii zlib1g1:1.2.8.dfsg-2+b3 libblosc1 recommends no packages. libblosc1 suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Version: 1.11.1+ds1-2.2 On Sun, 6 Nov 2016 21:50:35 +0100 Daniel Stender wrote: > Hi Gilles, > > that's o.k. with me. Thx for taking care of this. > > Best, > DS > > On 06.11.2016 12:10, Gilles Filippini wrote: > > Control: tags 8430040 + patch > > Control: tags 8430040 + pending > > > > Dear maintainer, > > > > I've prepared an NMU for c-blosc (versioned as 1.11.1+ds1-2.1) and > > uploaded it to DELAYED/2. Please feel free to tell me if I > > should delay it longer. I've had to upload a second time because of a typo in the patch (missing ';'). And the uploads didn't close the bug because of another typo in the changelog (an extraneous '0'). Oh well... Sorry about that. _g. signature.asc Description: OpenPGP digital signature --- End Message ---
Bug#817771: yapps2: diff for NMU version 2.1.1-17.5
My previous NMU failed to build on the autobuilders due to a pre-existing bug in debian/rules; the version of sbuild I tested with didn't pick that up. I've uploaded this further change to fix that. -- Colin Watson [cjwat...@debian.org] diff -u yapps2-2.1.1/debian/changelog yapps2-2.1.1/debian/changelog --- yapps2-2.1.1/debian/changelog +++ yapps2-2.1.1/debian/changelog @@ -1,3 +1,11 @@ +yapps2 (2.1.1-17.5) unstable; urgency=medium + + * Non-maintainer upload. + * Move binary-arch rule to binary-indep, since all our binary packages are +Architecture: all. + + -- Colin Watson Tue, 08 Nov 2016 19:48:31 + + yapps2 (2.1.1-17.4) unstable; urgency=medium * Non-maintainer upload. diff -u yapps2-2.1.1/debian/rules yapps2-2.1.1/debian/rules --- yapps2-2.1.1/debian/rules +++ yapps2-2.1.1/debian/rules @@ -73,10 +73,6 @@ # Build architecture-independent files here. binary-indep: build install -# We have nothing to do by default. - -# Build architecture-dependent files here. -binary-arch: build install dh_testdir dh_testroot dh_installchangelogs @@ -97,4 +93,8 @@ dh_builddeb +# Build architecture-dependent files here. +binary-arch: build install +# We have nothing to do by default. + binary: binary-indep binary-arch .PHONY: build clean binary-indep binary-arch binary install configure
Processed: Re: dpdk: FTBFS: /usr/bin/ld: unrecognized option '-specs=/usr/share/dpkg/no-pie-link.specs'
Processing control commands: > tags -1 pending Bug #843685 [src:dpdk] dpdk: FTBFS: /usr/bin/ld: unrecognized option '-specs=/usr/share/dpkg/no-pie-link.specs' Added tag(s) pending. -- 843685: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843685 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#843685: dpdk: FTBFS: /usr/bin/ld: unrecognized option '-specs=/usr/share/dpkg/no-pie-link.specs'
Control: tags -1 pending On Tue, 08 Nov 2016 18:58:35 + Chris Lamb wrote: > Source: dpdk > Version: 16.07-1 > Severity: serious > Justification: fails to build from source > User: reproducible-bui...@lists.alioth.debian.org > Usertags: ftbfs > X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org > > Dear Maintainer, > > dpdk fails to build from source in unstable/amd64: > Hi, We did the original upload 2 months ago before the changes in the default build flags / spec files on dpkg/gcc, so we missed it until this morning. We are working on a solution which will hopefully be uploaded tomorrow or the day after. Kind regards, Luca Boccassi signature.asc Description: This is a digitally signed message part
Bug#828270: marked as done (conserver: FTBFS with openssl 1.1.0)
Your message dated Tue, 08 Nov 2016 19:33:53 + with message-id and subject line Bug#828270: fixed in conserver 8.2.1-1 has caused the Debian Bug report #828270, regarding conserver: FTBFS with openssl 1.1.0 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.) -- 828270: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828270 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: conserver Version: 8.1.18-2.2 Severity: important Control: block 827061 by -1 Hi, OpenSSL 1.1.0 is about to released. During a rebuild of all packages using OpenSSL this package fail to build. A log of that build can be found at: https://breakpoint.cc/openssl-1.1-rebuild-2016-05-29/Attempted/conserver_8.1.18-2.2_amd64-20160530-2108 On https://wiki.openssl.org/index.php/1.1_API_Changes you can see various of the reasons why it might fail. There are also updated man pages at https://www.openssl.org/docs/manmaster/ that should contain useful information. There is a libssl-dev package available in experimental that contains a recent snapshot, I suggest you try building against that to see if everything works. If you have problems making things work, feel free to contact us. Kurt --- End Message --- --- Begin Message --- Source: conserver Source-Version: 8.2.1-1 We believe that the bug you reported is fixed in the latest version of conserver, 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 828...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jörgen Hägg (supplier of updated conserver 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: Wed, 02 Nov 2016 20:56:17 +0100 Source: conserver Binary: conserver-server conserver-client Architecture: source amd64 Version: 8.2.1-1 Distribution: unstable Urgency: medium Maintainer: Jörgen Hägg Changed-By: Jörgen Hägg Description: conserver-client - connect to a console server conserver-server - connect multiple user to a serial console with logging Closes: 828270 Changes: conserver (8.2.1-1) unstable; urgency=medium . * new upstream version * using libssl1.0 until upstream has fixed current problems (Closes: #828270) Checksums-Sha1: 01204cba5c9e3adc9406d94be9a07a2bd55fd21b 1817 conserver_8.2.1-1.dsc 854522f13129136a266ae1756f122bd56e94e3bf 333412 conserver_8.2.1.orig.tar.gz 1c17a4eeb0526acdb3a152c4d4f4b3587be0a7c9 57993 conserver_8.2.1-1.diff.gz 46633aafcd7fc5a6e42ba64038a5c2de281088c2 96302 conserver-client-dbgsym_8.2.1-1_amd64.deb 03382c0551944ecc01dfb289c39444bca487be7d 76376 conserver-client_8.2.1-1_amd64.deb 2732f62aa4d206547af1edefbeacdbe640152070 334554 conserver-server-dbgsym_8.2.1-1_amd64.deb 18d7b4c0a54684f0e6c369e4b953a0c18fa31712 179724 conserver-server_8.2.1-1_amd64.deb 940d9fd161d65c0428ad6e52bfa5b4f9b394698a 6275 conserver_8.2.1-1_20161108T190432z-59e3d1ca.buildinfo Checksums-Sha256: 7bb6357f68bac04e714ec222bd2a3cee6d095748143e183e5b5febb33e50466f 1817 conserver_8.2.1-1.dsc d2fdd85dac4ffde6e025016fb947df537c16b7eb29bdf6078e13e71a167ae117 333412 conserver_8.2.1.orig.tar.gz fb488a83f195bf64f267df865e537bfb1203f3750d5e9d2fbba4aed7c5284c6a 57993 conserver_8.2.1-1.diff.gz 6ab1ab3969de3d561a91e8deed01fb0733e3b8d072126b1a61f791527adf3d7d 96302 conserver-client-dbgsym_8.2.1-1_amd64.deb 082791367ad251f3111e0e5736a70521228a841019c61ef23600ad340f012237 76376 conserver-client_8.2.1-1_amd64.deb 23fe9a6295178a881c644a9cf8e7218b75b17ac3d918b75192d7b39686a88c19 334554 conserver-server-dbgsym_8.2.1-1_amd64.deb 4ebef67a1070e9a0da5a1ee0be6affd63060e9c6d6d102a512fcd12824209e2f 179724 conserver-server_8.2.1-1_amd64.deb df0e2a9b300b1aedf7b3198eb92cb250056fb60e1dc53b1e651c5d7e0f4b369b 6275 conserver_8.2.1-1_20161108T190432z-59e3d1ca.buildinfo Files: 0a318dc26768059d599b9b82526701c9 1817 non-free/comm optional conserver_8.2.1-1.dsc 02baffe51c788c649547f1971a95470f 333412 non-free/comm optional conserver_8.2.1.orig.tar.gz f1367b704a1a25c90d2abd5a571dba20 57993 non-free/comm optional conserver_8.2.1-1.diff.gz 56c23412b769cc53c4efa4de92a9710c 96302 non-free/debug extra conserver-client-dbgsym_8.2.1-1_amd64.deb 2a74604deace0ec4c9dab4c8dfc1f97
Bug#843688: dpdk: maintainer address bounces
On Tue, 08 Nov 2016 19:17:49 + Chris Lamb wrote: > Source: dpdk > Version: 2.54+dfsg-7 > Severity: serious > > I tried to report a bug against this package, and I got: > > Your mail to 'deb-dpdk' with the subject > > Bug#843685: dpdk: FTBFS: /usr/bin/ld: unrecognized option > '-specs=/usr/share/dpkg/no-pie-link.specs' > > Is being held until the list moderator can review it for approval. > > The reason it is being held: > > Post by non-member to a members-only list > > As per Policy §3.3: âThe email address given in the âMaintainerâ > control > field must accept mail from those role accounts in Debian used to send > automated mails regarding the package. This includes non-spam mail from > the bug-tracking system, [â¦].â > > > Regards, > > -- > ,''`. > : :' : Chris Lamb > `. `'` la...@debian.org / chris-lamb.co.uk >`- Hi, Thanks for the heads-up, I didn't realise it was set up that way. I will ask to open it up and if not possible we'll change it. Kind regards, Luca Boccassi signature.asc Description: This is a digitally signed message part
Bug#843673: marked as done (python3-pycodestyle: breaks flake8)
Your message dated Tue, 08 Nov 2016 19:37:37 + with message-id and subject line Bug#843673: fixed in python-flake8 3.0.4+dfsg1-4 has caused the Debian Bug report #843673, regarding python3-pycodestyle: breaks flake8 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.) -- 843673: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843673 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python3-pycodestyle Version: 2.1.0-1 Severity: normal after upgrading to version of python3-pycodestyle recently uploaded to unstable, flake8 now omits some warnings. to reproduce I downgraded only python3-pycodestyle: $ flake8 $ sudo apt install python3-pycodestyle/unstable >/dev/null 2>&1 $ flake8 "pycodestyle" requested unknown parameters causing 'FileProcessor' object has no attribute 'previous_unindented_logical_line' "pycodestyle" requested unknown parameters causing 'FileProcessor' object has no attribute 'previous_unindented_logical_line' "pycodestyle" requested unknown parameters causing 'FileProcessor' object has no attribute 'previous_unindented_logical_line' "pycodestyle" requested unknown parameters causing 'FileProcessor' object has no attribute 'previous_unindented_logical_line' -- System Information: Debian Release: stretch/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'unstable'), (500, 'testing'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.8.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages python3-pycodestyle depends on: pn python3:any python3-pycodestyle recommends no packages. python3-pycodestyle suggests no packages. -- no debconf information signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: python-flake8 Source-Version: 3.0.4+dfsg1-4 We believe that the bug you reported is fixed in the latest version of python-flake8, 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 843...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ondřej Nový (supplier of updated python-flake8 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: Tue, 08 Nov 2016 19:51:43 +0100 Source: python-flake8 Binary: flake8 python-flake8 python3-flake8 Architecture: source Version: 3.0.4+dfsg1-4 Distribution: unstable Urgency: medium Maintainer: Debian Python Modules Team Changed-By: Ondřej Nový Description: flake8 - code checker using pycodestyle and pyflakes python-flake8 - code checker using pycodestyle and pyflakes - Python 2.x python3-flake8 - code checker using pycodestyle and pyflakes - Python 3.x Closes: 843673 Changes: python-flake8 (3.0.4+dfsg1-4) unstable; urgency=medium . * Bumped debhelper version to 10 * Added patch to work with pycodestyle 2.1.0 (Closes: #843673) Checksums-Sha1: 34996665a5c7b51ddf9eadeead3f3a23e760123d 2691 python-flake8_3.0.4+dfsg1-4.dsc 5fd05ac116a5e1cc9a725907d299093baee1e9f7 7948 python-flake8_3.0.4+dfsg1-4.debian.tar.xz Checksums-Sha256: e5b26ae6e2f64acc19c940892e0549e3fe09f5c39f2de3e468c52038d0ab9834 2691 python-flake8_3.0.4+dfsg1-4.dsc 10938f38ac2f47f60c8af8589765667e8cddf9574ea85a536ed0819e9b448395 7948 python-flake8_3.0.4+dfsg1-4.debian.tar.xz Files: 403e59f077e8e32f1c7bed31863b4be0 2691 python optional python-flake8_3.0.4+dfsg1-4.dsc 0cf9ec08bab91e52e3418a571bdd53ba 7948 python optional python-flake8_3.0.4+dfsg1-4.debian.tar.xz -BEGIN PGP SIGNATURE- iQIcBAEBCgAGBQJYIiL4AAoJEDVzElWdHgZLYPkQAJysST6SJHmzojwYaTgAq76L 3piQzb7iKpe3ZVxMQaYuGrQO3OmyxCXluj+XX98mSJqiHBIimlf1zCjvrr837euh wL3yMe0/IlZHJJ4jsnuqcMjivavIiY/YrSKALDYIYHJDrkiORTBOYY8lnsxyyc8E dwytAVHshqlkTS+aV0wehGZhxV6zK8m4DYzEkQKV0iTxEY+JNPa3SNlbgdawiSTt VvkcVz9SnAXZqG9azZNKkPG3nwjyX5NxntCAgcvgk/zwmBIas2KLzalRI9b++jQ9 rTjoHCTtBjuhUd7Ot3nFrMAsU+YQ8S2h6KnRRKKERai9vCSnSiCfzpNzZM2EI5pA 2N6tzam1oyXzybzYRu6tA8tB7H8tQWLHG4VeWZxpxtsCn7puzeo03R+Ez1RoeHEs i772xKvvHD6lzGZrEORsNG6Mx1AkOMzN3M2+oETVFuo10LySznKM4DDjo
Bug#843691: glibc: FTBFS on ppc64el: Error: operand out of range
Source: glibc Version: 2.24-5 Severity: serious Hello, glibc is failing to build on ppc64el, on sid with the following: .../sysdeps/powerpc/powerpc64/power6/memset.S: Assembler messages: .../sysdeps/powerpc/powerpc64/power6/memset.S:254: Error: operand out of range (5 is not between 0 and 1) .../sysdeps/powerpc/powerpc64/power6/memset.S:254: Error: operand out of range (128 is not between 0 and 31) .../sysdeps/powerpc/powerpc64/power6/memset.S:254: Error: missing operand This was an attempt with sbuild with sid. It initially built on the same version on buildd, 20 days ago or so, but the failure was also observed on cross-compilation. Thanks. Fernando
Bug#843675: asn1c-doc: fails to upgrade from 'testing' - trying to overwrite /usr/share/doc-base/asn1c
> > during a test with piuparts I noticed your package fails to upgrade from > 'testing'. > It installed fine in 'testing', then the upgrade to 'sid' 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 Hello, Andreas. Thank you for the report and for the exact policy reference. It will be fixed with the next package upload. --- Best regards, Eugene Seliverstov signature.asc Description: Message signed with OpenPGP using GPGMail
Bug#843629: marked as done (gvfs-backends: Incomplete/incorrect polkit rules)
Your message dated Tue, 08 Nov 2016 19:19:12 + with message-id and subject line Bug#843629: fixed in gvfs 1.30.2-2 has caused the Debian Bug report #843629, regarding gvfs-backends: Incomplete/incorrect polkit rules 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.) -- 843629: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843629 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: gvfs-backends Version: 1.29.91-1 Severity: serious Hi, Since 1.29.91-1, gvfs is shipping polkit rules that are only working with the newer (>=0.112) version that is only present in experimental. For unstable, we need to add a pkla file too. Also, the rule file reference the "wheel" group which is not existing in debian. This should be changed to "sudo" (and/or "admin") for ubuntu -- System Information: Debian Release: stretch/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.8.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) --- End Message --- --- Begin Message --- Source: gvfs Source-Version: 1.30.2-2 We believe that the bug you reported is fixed in the latest version of gvfs, 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 843...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Laurent Bigonville (supplier of updated gvfs 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, 08 Nov 2016 19:44:47 +0100 Source: gvfs Binary: gvfs gvfs-daemons gvfs-libs gvfs-common gvfs-fuse gvfs-backends gvfs-bin Architecture: source Version: 1.30.2-2 Distribution: unstable Urgency: medium Maintainer: Debian GNOME Maintainers Changed-By: Laurent Bigonville Description: gvfs - userspace virtual filesystem - GIO module gvfs-backends - userspace virtual filesystem - backends gvfs-bin - userspace virtual filesystem - binaries gvfs-common - userspace virtual filesystem - common data files gvfs-daemons - userspace virtual filesystem - servers gvfs-fuse - userspace virtual filesystem - fuse server gvfs-libs - userspace virtual filesystem - private libraries Closes: 843629 Changes: gvfs (1.30.2-2) unstable; urgency=medium . [ Laurent Bigonville ] * debian/patches/02_polkit_sudo_group.patch: Use sudo group instead of the wheel one, the later doesn't exist on debian (Closes: #843629) * Move the policykit rules file to the examples directory, for now we don't want the user to be able to modify files owned by root without entering any password even if they are part of the "sudo" group. . [ Michael Biebl ] * Explicitly remove .h header files instead of using dh_install -X.h. This avoids not installing required files which are not header files but contain .h anywhere in the filename. Checksums-Sha1: 07bf51882ba2723ff16a62e6e680907e0e38f8f0 3026 gvfs_1.30.2-2.dsc 340a2a98fc77ef7051020f6919f643efc9140d47 19116 gvfs_1.30.2-2.debian.tar.xz Checksums-Sha256: 8b8bf43599278d592a20ebc768bcb0a6a9f88bdea18996a91a23d9a15928bf0f 3026 gvfs_1.30.2-2.dsc 14360ce37b023683af98bbc0fd5d920a2a36051dd60f200e2b7b4f752d2ea35a 19116 gvfs_1.30.2-2.debian.tar.xz Files: f591146987fdb562998ac85377b1c366 3026 gnome optional gvfs_1.30.2-2.dsc 4d7e37f28f09df1d22197678d31433e1 19116 gnome optional gvfs_1.30.2-2.debian.tar.xz -BEGIN PGP SIGNATURE- iQEuBAEBCAAYBQJYIh5PERxiaWdvbkBkZWJpYW4ub3JnAAoJEB/FiR66sEPVm6AI AISCZ6L5wt818FkQ9cipM+cg4P9B1w23DnFbZ5gHsM0ute8JCucnwLU/raVSpL1o PS4BzkjNBU+UKq5m77Dt/69VISIUXadbqik7/yBjCbmRMCVZ9/eF/e1z2fQLH9Fs KP7yKc8cPOYdUVMoICG6av8O15rYyK4jTAdsZjR1JbsajNH794siYZXiOmB34ofu dtcrStAMt1piqgmi8tCnBB6zMSAt7uqLjIW/f+PcYsSkKCo7pj490qOrznOSrEWB lY2PhfjcpGQ0UqvbleGtfJX/h8oXcfnqwKxJKfhOHI6GMB4fwcn17aDC6bQescEg lxZ4Yh58eu9hsQWx8+Fb7l8= =YB/F -END PGP SIGNATURE End Message ---
Bug#843529: marked as done (node-dateformat: FTBFS: Error: Cannot find module 'underscore')
Your message dated Tue, 08 Nov 2016 19:06:49 + with message-id and subject line Bug#843529: fixed in node-dateformat 1.0.11-2 has caused the Debian Bug report #843529, regarding node-dateformat: FTBFS: Error: Cannot find module 'underscore' 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.) -- 843529: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843529 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: node-dateformat Version: 1.0.11-1 Severity: serious Justification: fails to build from source User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org Dear Maintainer, node-dateformat fails to build from source in unstable/amd64: […] dh_auto_build debian/rules override_dh_auto_test make[1]: Entering directory '/home/lamby/temp/cdt.20161107132446.quqSm7tjme.db.node-dateformat/node-dateformat-1.0.11' mocha -R spec module.js:327 throw err; ^ Error: Cannot find module 'underscore' at Function.Module._resolveFilename (module.js:325:15) at Function.Module._load (module.js:276:25) at Module.require (module.js:353:17) at require (internal/module.js:12:17) at Object. (/home/lamby/temp/cdt.20161107132446.quqSm7tjme.db.node-dateformat/node-dateformat-1.0.11/test/test_formats.js:3:9) at Module._compile (module.js:409:26) at Object.Module._extensions..js (module.js:416:10) at Module.load (module.js:343:32) at Function.Module._load (module.js:300:12) at Module.require (module.js:353:17) at require (internal/module.js:12:17) at /usr/lib/nodejs/mocha/lib/mocha.js:172:27 at Array.forEach (native) at Mocha.loadFiles (/usr/lib/nodejs/mocha/lib/mocha.js:169:14) at Mocha.run (/usr/lib/nodejs/mocha/lib/mocha.js:356:31) at Object. (/usr/lib/nodejs/mocha/bin/_mocha:366:16) at Module._compile (module.js:409:26) at Object.Module._extensions..js (module.js:416:10) at Module.load (module.js:343:32) at Function.Module._load (module.js:300:12) at Function.Module.runMain (module.js:441:10) at startup (node.js:139:18) at node.js:974:3 debian/rules:7: recipe for target 'override_dh_auto_test' failed make[1]: *** [override_dh_auto_test] Error 1 make[1]: Leaving directory '/home/lamby/temp/cdt.20161107132446.quqSm7tjme.db.node-dateformat/node-dateformat-1.0.11' debian/rules:3: recipe for target 'build' failed make: *** [build] Error 2 […] The full build log is attached. Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `- node-dateformat.1.0.11-1.unstable.amd64.log.txt.gz Description: Binary data --- End Message --- --- Begin Message --- Source: node-dateformat Source-Version: 1.0.11-2 We believe that the bug you reported is fixed in the latest version of node-dateformat, 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 843...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sruthi Chandran (supplier of updated node-dateformat 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, 08 Nov 2016 21:05:27 +0530 Source: node-dateformat Binary: node-dateformat libjs-dateformat Architecture: source Version: 1.0.11-2 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Sruthi Chandran Description: libjs-dateformat - JavaScript Date Format node-dateformat - JavaScript Date Format Closes: 843529 Changes: node-dateformat (1.0.11-2) unstable; urgency=medium . * Add node-underscore to dependency (Closes: #843529) Checksums-Sha1: 2b554d708f4f962366da7f2f561e9b5568fe22eb 2236 node-dateformat_1.0.11-2.dsc 050a315aa603e99efca95281a48063ce9c0084ba 2228 node-dateformat_1.0.11-2.debian.tar.xz Checksums-Sha256: 6587d0d74c5d3ab74e2f07cfb6af5c83d43c4f1e8d5302a2b9331710c5c66827 2236 node-dateformat_1.0.11-2.dsc 9e3056bfe0790b586499b72248ab5aea46e337e149ca46148a63b6617a02df19 2228 node-dateformat_1.0.11-2.debian.tar.xz Files: f6256ec82dfca2b608ff8664eb19cc11 2236 web
Bug#831844: closing 831844
close 831844 5.6.34-1 thanks
Processed: closing 831844
Processing commands for cont...@bugs.debian.org: > close 831844 5.6.34-1 Bug #831844 [src:mysql-5.6] mysql-5.6: Multiple security fixes from the July 2016 CPU Marked as fixed in versions mysql-5.6/5.6.34-1. Bug #831844 [src:mysql-5.6] mysql-5.6: Multiple security fixes from the July 2016 CPU Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 831844: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831844 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#843687: mitmproxy: FTBFS: AttributeError: 'module' object has no attribute 'SSL_ST_INIT'
Source: mitmproxy Version: 0.18.1-2 Severity: serious Justification: fails to build from source User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org Dear Maintainer, mitmproxy fails to build from source in unstable/amd64: [] [1mfrom OpenSSL import rand, crypto, SSL[0m [1m[31m/usr/lib/python2.7/dist-packages/OpenSSL/SSL.py[0m:112: in [1mSSL_ST_INIT = _lib.SSL_ST_INIT[0m [1m[31mE AttributeError: 'module' object has no attribute 'SSL_ST_INIT'[0m ERROR collecting .pybuild/pythonX.Y_2.7/build/test/netlib/http/test_response.py [1m[31mtest/netlib/http/test_response.py[0m:10: in [1mfrom netlib.tutils import raises, tresp[0m [1m[31mnetlib/tutils.py[0m:10: in [1mfrom netlib import utils, tcp, http[0m [1m[31mnetlib/tcp.py[0m:20: in [1mimport OpenSSL[0m [1m[31m/usr/lib/python2.7/dist-packages/OpenSSL/__init__.py[0m:8: in [1mfrom OpenSSL import rand, crypto, SSL[0m [1m[31m/usr/lib/python2.7/dist-packages/OpenSSL/SSL.py[0m:112: in [1mSSL_ST_INIT = _lib.SSL_ST_INIT[0m [1m[31mE AttributeError: 'module' object has no attribute 'SSL_ST_INIT'[0m __ ERROR collecting .pybuild/pythonX.Y_2.7/build/test/netlib/http/test_url.py __ [1m[31mtest/netlib/http/test_url.py[0m:2: in [1mfrom netlib import tutils[0m [1m[31mnetlib/tutils.py[0m:10: in [1mfrom netlib import utils, tcp, http[0m [1m[31mnetlib/tcp.py[0m:20: in [1mimport OpenSSL[0m [1m[31m/usr/lib/python2.7/dist-packages/OpenSSL/__init__.py[0m:8: in [1mfrom OpenSSL import rand, crypto, SSL[0m [1m[31m/usr/lib/python2.7/dist-packages/OpenSSL/SSL.py[0m:112: in [1mSSL_ST_INIT = _lib.SSL_ST_INIT[0m [1m[31mE AttributeError: 'module' object has no attribute 'SSL_ST_INIT'[0m ERROR collecting .pybuild/pythonX.Y_2.7/build/test/netlib/http/http1/test_assemble.py [1m[31mtest/netlib/http/http1/test_assemble.py[0m:9: in [1mfrom netlib.tutils import treq, raises, tresp[0m [1m[31mnetlib/tutils.py[0m:10: in [1mfrom netlib import utils, tcp, http[0m [1m[31mnetlib/tcp.py[0m:20: in [1mimport OpenSSL[0m [1m[31m/usr/lib/python2.7/dist-packages/OpenSSL/__init__.py[0m:8: in [1mfrom OpenSSL import rand, crypto, SSL[0m [1m[31m/usr/lib/python2.7/dist-packages/OpenSSL/SSL.py[0m:112: in [1mSSL_ST_INIT = _lib.SSL_ST_INIT[0m [1m[31mE AttributeError: 'module' object has no attribute 'SSL_ST_INIT'[0m ERROR collecting .pybuild/pythonX.Y_2.7/build/test/netlib/http/http1/test_read.py [1m[31mtest/netlib/http/http1/test_read.py[0m:15: in [1mfrom netlib.tutils import treq, tresp, raises[0m [1m[31mnetlib/tutils.py[0m:10: in [1mfrom netlib import utils, tcp, http[0m [1m[31mnetlib/tcp.py[0m:20: in [1mimport OpenSSL[0m [1m[31m/usr/lib/python2.7/dist-packages/OpenSSL/__init__.py[0m:8: in [1mfrom OpenSSL import rand, crypto, SSL[0m [1m[31m/usr/lib/python2.7/dist-packages/OpenSSL/SSL.py[0m:112: in [1mSSL_ST_INIT = _lib.SSL_ST_INIT[0m [1m[31mE AttributeError: 'module' object has no attribute 'SSL_ST_INIT'[0m ERROR collecting .pybuild/pythonX.Y_2.7/build/test/netlib/websockets/test_frame.py [1m[31mtest/netlib/websockets/test_frame.py[0m:5: in [1mfrom netlib import websockets[0m [1m[31mnetlib/websockets/__init__.py[0m:3: in [1mfrom .frame import FrameHeader[0m [1m[31mnetlib/websockets/frame.py[0m:8: in [1mfrom netlib import tcp[0m [1m[31mnetlib/tcp.py[0m:20: in [1mimport OpenSSL[0m [1m[31m/usr/lib/python2.7/dist-packages/OpenSSL/__init__.py[0m:8: in [1mfrom OpenSSL import rand, crypto, SSL[0m [1m[31m/usr/lib/python2.7/dist-packages/OpenSSL/SSL.py[0m:112: in [1mSSL_ST_INIT = _lib.SSL_ST_INIT[0m [1m[31mE AttributeError: 'module' object has no attribute 'SSL_ST_INIT'[0m ERROR collecting .pybuild/pythonX.Y_2.7/build/test/netlib/websockets/test_masker.py [1m[31mtest/netlib/websockets/test_masker.py[0m:4: in [1mfrom netlib import websockets[0m [1m[31mnetlib/websockets/__init__.py[0m:3: in [1mfrom .frame import FrameHeader[0m [1m[31mnetlib/websockets/frame.py[0m:8: in [1mfrom netlib import tcp[0m [1m[31mnetlib/tcp.py[0m:20: in [1mimport OpenSSL[0m [1m[31m/usr/lib/python2.7/dist-packages/OpenSSL/__init__.py[0m:8: in [1mfrom OpenSSL import rand, crypto, SSL[0m [1m[31m/usr/lib/python2.7/dist-packages/OpenSSL/SSL.py[0m:112: in [1mSSL_ST_INIT = _lib.SSL_ST_INIT[0m [1m[31mE AttributeError: 'module' object has no attribute 'SSL_ST_INIT'[0m ERROR collecting .pybuild/pythonX.Y_2.7/build/test/netlib/websockets/test_utils.py [1m[31mtest/netlib/websockets/test_utils.py[0m:4: in [1mfrom netlib import webso
Bug#843686: htsjdk: FTBFS: java.lang.NoSuchMethodError: net.rubygrapefruit.platform.PosixFiles.stat(Ljava/io/File;)Lnet/rubygrapefruit/platform/PosixFile
Source: htsjdk Version: 2.6.1+dfsg-1 Severity: serious Justification: fails to build from source User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org Dear Maintainer, htsjdk fails to build from source in unstable/amd64: […] :debianMavenPom (Thread[main,5,main]) started. :debianMavenPom Executing task ':debianMavenPom' (up-to-date check took 0.0 secs) due to: No history is available. :debianMavenPom (Thread[main,5,main]) completed. Took 0.022 secs. :jar (Thread[main,5,main]) started. :jar Executing task ':jar' (up-to-date check took 0.082 secs) due to: No history is available. :jar (Thread[main,5,main]) completed. Took 0.516 secs. :javadoc (Thread[main,5,main]) started. :javadoc Executing task ':javadoc' (up-to-date check took 0.056 secs) due to: No history is available. Starting process 'command '/usr/lib/jvm/java-8-openjdk-amd64/bin/javadoc''. Working directory: /home/lamby/temp/cdt.20161108185222.SOXwYGX3QV.db.htsjdk/htsjdk-2.6.1+dfsg Command: /usr/lib/jvm/java-8-openjdk-amd64/bin/javadoc @/home/lamby/temp/cdt.20161108185222.SOXwYGX3QV.db.htsjdk/htsjdk-2.6.1+dfsg/build/tmp/javadoc/javadoc.options Successfully started process 'command '/usr/lib/jvm/java-8-openjdk-amd64/bin/javadoc'' /home/lamby/temp/cdt.20161108185222.SOXwYGX3QV.db.htsjdk/htsjdk-2.6.1+dfsg/src/main/java/htsjdk/variant/vcf/VCFCompoundHeaderLine.java:85: warning - @return tag has no arguments. /home/lamby/temp/cdt.20161108185222.SOXwYGX3QV.db.htsjdk/htsjdk-2.6.1+dfsg/src/main/java/htsjdk/variant/vcf/VCFEncoder.java:213: warning - @return tag has no arguments. /home/lamby/temp/cdt.20161108185222.SOXwYGX3QV.db.htsjdk/htsjdk-2.6.1+dfsg/src/main/java/htsjdk/variant/vcf/VCFFileReader.java:82: warning - @return tag has no arguments. /home/lamby/temp/cdt.20161108185222.SOXwYGX3QV.db.htsjdk/htsjdk-2.6.1+dfsg/src/main/java/htsjdk/variant/vcf/VCFHeader.java:416: warning - @return tag has no arguments. /home/lamby/temp/cdt.20161108185222.SOXwYGX3QV.db.htsjdk/htsjdk-2.6.1+dfsg/src/main/java/htsjdk/variant/variantcontext/writer/BCF2Encoder.java:223: warning - @return tag has no arguments. /home/lamby/temp/cdt.20161108185222.SOXwYGX3QV.db.htsjdk/htsjdk-2.6.1+dfsg/src/main/java/htsjdk/variant/variantcontext/writer/BCF2FieldEncoder.java:184: warning - Tag @param cannot be used in inline documentation. It can only be used in the following types of documentation: class/interface, constructor, method. /home/lamby/temp/cdt.20161108185222.SOXwYGX3QV.db.htsjdk/htsjdk-2.6.1+dfsg/src/main/java/htsjdk/variant/variantcontext/writer/BCF2FieldEncoder.java:184: warning - Tag @param cannot be used in inline documentation. It can only be used in the following types of documentation: class/interface, constructor, method. /home/lamby/temp/cdt.20161108185222.SOXwYGX3QV.db.htsjdk/htsjdk-2.6.1+dfsg/src/main/java/htsjdk/variant/variantcontext/writer/BCF2FieldEncoder.java:184: warning - Tag @param cannot be used in inline documentation. It can only be used in the following types of documentation: class/interface, constructor, method. /home/lamby/temp/cdt.20161108185222.SOXwYGX3QV.db.htsjdk/htsjdk-2.6.1+dfsg/src/main/java/htsjdk/variant/variantcontext/writer/IntGenotypeFieldAccessors.java:57: warning - @return tag has no arguments. /home/lamby/temp/cdt.20161108185222.SOXwYGX3QV.db.htsjdk/htsjdk-2.6.1+dfsg/src/main/java/htsjdk/variant/variantcontext/writer/VariantContextWriterBuilder.java:365: warning - @return tag cannot be used in method with void return type. /home/lamby/temp/cdt.20161108185222.SOXwYGX3QV.db.htsjdk/htsjdk-2.6.1+dfsg/src/main/java/htsjdk/variant/variantcontext/writer/VariantContextWriterFactory.java:247: warning - @return tag has no arguments. /home/lamby/temp/cdt.20161108185222.SOXwYGX3QV.db.htsjdk/htsjdk-2.6.1+dfsg/src/main/java/htsjdk/variant/variantcontext/writer/VariantContextWriterFactory.java:275: warning - @return tag has no arguments. /home/lamby/temp/cdt.20161108185222.SOXwYGX3QV.db.htsjdk/htsjdk-2.6.1+dfsg/src/main/java/htsjdk/tribble/index/interval/IntervalTree.java:69: warning - @return tag has no arguments. /home/lamby/temp/cdt.20161108185222.SOXwYGX3QV.db.htsjdk/htsjdk-2.6.1+dfsg/src/main/java/htsjdk/tribble/index/interval/IntervalTree.java:111: warning - @return tag has no arguments. /home/lamby/temp/cdt.20161108185222.SOXwYGX3QV.db.htsjdk/htsjdk-2.6.1+dfsg/src/main/java/htsjdk/tribble/index/Index.java:90: warning - @return tag has no arguments. /home/lamby/temp/cdt.20161108185222.SOXwYGX3QV.db.htsjdk/htsjdk-2.6.1+dfsg/src/main/java/htsjdk/tribble/index/interval/IntervalTreeIndex.java:40: warning - @date is an unknown tag. /home/lamby/temp/cdt.20161108185222.SOXwYGX3QV.db.htsjdk/htsjdk-2.6.1+dfsg/src/main/java/htsjdk/tribble/index/linear/LinearIndexCreator.java:120: warning - @return tag has no arguments. /home/lamby/temp/cdt.20161108185222.SOXwYGX3
Bug#839343: marked as done (lostirc: FTBFS: TextWidget.cpp:213:12: error: no match for 'operator==' (operand types are 'Glib::RefPtr' and 'int'))
Your message dated Tue, 08 Nov 2016 18:51:34 + with message-id and subject line Bug#839343: fixed in lostirc 0.4.6-4.2 has caused the Debian Bug report #839343, regarding lostirc: FTBFS: TextWidget.cpp:213:12: error: no match for 'operator==' (operand types are 'Glib::RefPtr' and 'int') 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.) -- 839343: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=839343 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: lostirc Version: 0.4.6-4.1 Severity: serious Tags: stretch sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20160930 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): > if x86_64-linux-gnu-g++ -DHAVE_CONFIG_H -I. -I. -I../.. -pthread > -I/usr/include/gtkmm-2.4 -I/usr/lib/x86_64-linux-gnu/gtkmm-2.4/include > -I/usr/include/gtk-unix-print-2.0 -I/usr/include/gtk-2.0 > -I/usr/include/gdkmm-2.4 -I/usr/lib/x86_64-linux-gnu/gdkmm-2.4/include > -I/usr/include/giomm-2.4 -I/usr/lib/x86_64-linux-gnu/giomm-2.4/include > -I/usr/include/gtk-2.0 -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include > -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo > -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 > -I/usr/include/atkmm-1.6 -I/usr/include/atk-1.0 -I/usr/include/pangomm-1.4 > -I/usr/lib/x86_64-linux-gnu/pangomm-1.4/include -I/usr/include/glibmm-2.4 > -I/usr/lib/x86_64-linux-gnu/glibmm-2.4/include -I/usr/include/cairomm-1.0 > -I/usr/lib/x86_64-linux-gnu/cairomm-1.0/include -I/usr/include/sigc++-2.0 > -I/usr/lib/x86_64-linux-gnu/sigc++-2.0/include -I/usr/include/pango-1.0 > -I/usr/include/harfbuzz -I/usr/include/pango-1.0 -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/libpng16 > -I../../src/libirc -I../../intl -DLOCALEDIR=\"/usr/share/locale\" > -DLOSTIRC_DATADIR=\"/usr/share\"-Wall -g -O2 -Wall -MT TextWidget.o -MD > -MP -MF ".deps/TextWidget.Tpo" -c -o TextWidget.o TextWidget.cpp; \ > then mv -f ".deps/TextWidget.Tpo" ".deps/TextWidget.Po"; else rm -f > ".deps/TextWidget.Tpo"; exit 1; fi > In file included from TextWidget.cpp:23:0: > MainWindow.h:46:10: warning: 'template class std::auto_ptr' is > deprecated [-Wdeprecated-declarations] > std::auto_ptr _prefswin; > ^~~~ > In file included from /usr/include/c++/6/memory:81:0, > from /usr/include/glibmm-2.4/glibmm/objectbase.h:32, > from /usr/include/glibmm-2.4/glibmm/object.h:30, > from /usr/include/pangomm-1.4/pangomm/context.h:31, > from /usr/include/gtkmm-2.4/gtkmm/widget.h:30, > from /usr/include/gtkmm-2.4/gtkmm/range.h:29, > from /usr/include/gtkmm-2.4/gtkmm/scrollbar.h:31, > from TextWidget.cpp:19: > /usr/include/c++/6/bits/unique_ptr.h:49:28: note: declared here >template class auto_ptr; > ^~~~ > In file included from TextWidget.cpp:23:0: > MainWindow.h:47:10: warning: 'template class std::auto_ptr' is > deprecated [-Wdeprecated-declarations] > std::auto_ptr _dccwin; > ^~~~ > In file included from /usr/include/c++/6/memory:81:0, > from /usr/include/glibmm-2.4/glibmm/objectbase.h:32, > from /usr/include/glibmm-2.4/glibmm/object.h:30, > from /usr/include/pangomm-1.4/pangomm/context.h:31, > from /usr/include/gtkmm-2.4/gtkmm/widget.h:30, > from /usr/include/gtkmm-2.4/gtkmm/range.h:29, > from /usr/include/gtkmm-2.4/gtkmm/scrollbar.h:31, > from TextWidget.cpp:19: > /usr/include/c++/6/bits/unique_ptr.h:49:28: note: declared here >template class auto_ptr; > ^~~~ > In file included from TextWidget.cpp:23:0: > MainWindow.h:48:10: warning: 'template class std::auto_ptr' is > deprecated [-Wdeprecated-declarations] > std::auto_ptr _serverwin; > ^~~~ > In file included from /usr/include/c++/6/memory:81:0, > from /usr/include/glibmm-2.4/glibmm/objectbase.h:32, > from /usr/include/glibmm-2.4/glibmm/object.h:30, > from /usr/include/pangomm-1.4/pangomm/context.h:31, > from /usr/include/gtkmm-2.4/gtkmm/widget.h:30, > from /usr/include/gtkmm-2.4/gtkmm/range.h:29, > from /usr/include/gtkmm-2.4/gtkmm/scrollbar.h:31,
Bug#843680: marked as done (libopendht-dev: missing Breaks+Replaces: libopendht1)
Your message dated Tue, 08 Nov 2016 18:51:46 + with message-id and subject line Bug#843680: fixed in opendht 1.2.1~dfsg1-6 has caused the Debian Bug report #843680, regarding libopendht-dev: missing Breaks+Replaces: libopendht1 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.) -- 843680: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843680 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libopendht-dev Version: 1.2.1~dfsg1-5 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install 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 libopendht1. Preparing to unpack .../9-libopendht1_1.2.1~dfsg1-4_amd64.deb ... Unpacking libopendht1 (1.2.1~dfsg1-4) ... dpkg: error processing archive /tmp/apt-dpkg-install-R3WovW/9-libopendht1_1.2.1~dfsg1-4_amd64.deb (--unpack): trying to overwrite '/usr/lib/pkgconfig/opendht.pc', which is also in package libopendht-dev 1.2.1~dfsg1-5 Errors were encountered while processing: /tmp/apt-dpkg-install-R3WovW/9-libopendht1_1.2.1~dfsg1-4_amd64.deb cheers, Andreas libopendht-dev=1.2.1~dfsg1-5_libopendht1=1.2.1~dfsg1-4.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: opendht Source-Version: 1.2.1~dfsg1-6 We believe that the bug you reported is fixed in the latest version of opendht, 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 843...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Alexandre Viau (supplier of updated opendht 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: Tue, 08 Nov 2016 13:13:44 -0500 Source: opendht Binary: libopendht-dev dhtnode Architecture: source amd64 Version: 1.2.1~dfsg1-6 Distribution: unstable Urgency: medium Maintainer: Alexandre Viau Changed-By: Alexandre Viau Description: dhtnode- OpenDHT node binary libopendht-dev - Development files for the libopendht library Closes: 843680 Changes: opendht (1.2.1~dfsg1-6) unstable; urgency=medium . * libopendht-dev now breaks+replaces libopendht1 (Closes: #843680) Checksums-Sha1: 8e7c36c245b1936963e46049ff3f8c0a53f9bcad 2032 opendht_1.2.1~dfsg1-6.dsc 7b5611a1d796e2197347a8df8df85a345f2717ed 4484 opendht_1.2.1~dfsg1-6.debian.tar.xz 81965a58324a7f8e6dd73cb1c452e8f9d895c8cc 4501574 dhtnode-dbgsym_1.2.1~dfsg1-6_amd64.deb 4cd0ce61bed3b665e558d031c033b9369fd22f7d 320770 dhtnode_1.2.1~dfsg1-6_amd64.deb dee176290faef7d3d0b9ebdf33a819fe03de599b 393078 libopendht-dev_1.2.1~dfsg1-6_amd64.deb 94665bfa41c2e618b14d56b8a7fe4e7402f41779 6399 opendht_1.2.1~dfsg1-6_20161108T182157z-034805c8.buildinfo Checksums-Sha256: a0b7376761ef34c06a6d9fcde8b7ff876d3e802b0f6f4cdcfc06d7472fb2d073 2032 opendht_1.2.1~dfsg1-6.dsc f11a436f98a9c6fb60b2e67b2c7ebc32d708904c64376c9fec503874b0589632 4484 opendht_1.2.1~dfsg1-6.debian.tar.xz 69df8999b953989a330befd97a644bba930137a22c2f0f1a9b93052143e78362 4501574 dhtnode-dbgsym_1.2.1~dfsg1-6_amd64.deb 5cb0b1fa95495ec4d42a5118f3d394fae532656545a36d5dcede9f45f958656d 320770 dhtnode_1.2.1~dfsg1-6_amd64.deb f8eac307e1e0d6bd17b20ddab6c306bf5ceb4e3016b70488505de56e28692aa2 393078 libopendht-dev_1.2.1~dfsg1-6_amd64.deb c774ad9d17f7178af26c45569020f8a86ffbdff0c9fa4b60b38a0815c21e7f9e 6399 opendht_1.2.1~dfsg1-6_20161108T182157z-034805c8.buildinfo Files: 5595a580f2b05bd9084ad2dcede448fe 2032 libs extra opendht_1.2.1~dfsg1-6.dsc 91ed82a3ee066abc03bfd0c6be949822 4484 libs extra opendht_1.2.1~dfsg1-6.debian.tar.xz b8407346d7aac6c219fbc96816a3aab9 4501574 debug extra dhtnode-dbgsym_1.2.1~dfsg1-6_amd64.deb 4e66f541cc20cdf525513ec7264eb32e 320770 net extra dhtnode_1.2.1~dfsg1-6_amd64.deb b3220bc9b5c07355542d5031e5d54722 393078 libdevel extra libopendht-dev_1.2.1~dfsg1-6_amd64.deb 034805c80f5b437edae13f8bcf606460 6399 libs extra opendht_1.2.1~dfsg1-6_20161108T182157z-034805c8.buildin
Processed: reassign 843673 to python-flake8
Processing commands for cont...@bugs.debian.org: > reassign 843673 python-flake8 Bug #843673 [python-flake8] python3-pycodestyle: breaks flake8 Ignoring request to reassign bug #843673 to the same package > thanks Stopping processing here. Please contact me if you need assistance. -- 843673: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843673 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: bug 843673 is forwarded to https://gitlab.com/pycqa/flake8/issues/246
Processing commands for cont...@bugs.debian.org: > forwarded 843673 https://gitlab.com/pycqa/flake8/issues/246 Bug #843673 [python-flake8] python3-pycodestyle: breaks flake8 Ignoring request to change the forwarded-to-address of bug#843673 to the same value > thanks Stopping processing here. Please contact me if you need assistance. -- 843673: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843673 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Root cause
Processing control commands: > retitle 843631 Downstream incompatibilities due to SSL_ST_* Bug #843631 [python-cryptography] STOP BREAKING PYOPENSSL WHEN UPLOADING CRYPTOGRAPHY Changed Bug title to 'Downstream incompatibilities due to SSL_ST_*' from 'STOP BREAKING PYOPENSSL WHEN UPLOADING CRYPTOGRAPHY'. -- 843631: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843631 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#843682: openssl: 'openssl dsaparam 2048 -out file' hangs, trying to read from stdin
Package: openssl
Version: 1.1.0b-2
Severity: serious
Hi,
I just noticed that the sendmail postinst hangs on
openssl dsaparam 2048 -out file
Running it under strace makes it stop with
[...]
fstat(0, {st_mode=S_IFCHR|0620, st_rdev=makedev(136, 29), ...}) = 0
read(0,
Downgrading to 1.0.2 makes this command work fine again.
Andreas
Processed: Root cause
Processing control commands: > retitle 843631 Downstream incompatibilities due to SSL_ST_* Bug #843631 [python-cryptography] Downstream incompatibilities due to SSL_ST_* Ignoring request to change the title of bug#843631 to the same title -- 843631: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843631 843644: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843644 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: bug 843673 is forwarded to https://gitlab.com/pycqa/flake8/issues/246
Processing commands for cont...@bugs.debian.org: > forwarded 843673 https://gitlab.com/pycqa/flake8/issues/246 Bug #843673 [python3-pycodestyle] python3-pycodestyle: breaks flake8 Set Bug forwarded-to-address to 'https://gitlab.com/pycqa/flake8/issues/246'. > thanks Stopping processing here. Please contact me if you need assistance. -- 843673: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843673 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: your mail
Processing commands for cont...@bugs.debian.org: > reassign 843673 python-flake8 Bug #843673 [python3-pycodestyle] python3-pycodestyle: breaks flake8 Bug reassigned from package 'python3-pycodestyle' to 'python-flake8'. No longer marked as found in versions pycodestyle/2.1.0-1. Ignoring request to alter fixed versions of bug #843673 to the same values previously set > forwarded 843673 https://gitlab.com/pycqa/flake8/issues/246 Bug #843673 [python-flake8] python3-pycodestyle: breaks flake8 Ignoring request to change the forwarded-to-address of bug#843673 to the same value > thanks Stopping processing here. Please contact me if you need assistance. -- 843673: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843673 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: #843631/#843644 affects bugwarrior & bugs-everywhere (AttributeError: 'module' object has no attribute 'SSL_ST_INIT')
Processing commands for cont...@bugs.debian.org: > affects 843631 + bugwarrior bugs-everywhere Bug #843631 [python-cryptography] STOP BREAKING PYOPENSSL WHEN UPLOADING CRYPTOGRAPHY Added indication that 843631 affects bugs-everywhere > affects 843644 + bugwarrior bugs-everywhere Bug #843644 [pyopenssl] AttributeError: 'module' object has no attribute Added indication that 843644 affects bugwarrior and bugs-everywhere > End of message, stopping processing here. Please contact me if you need assistance. -- 843631: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843631 843644: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843644 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: #843631 affects bugwarrior (AttributeError: 'module' object has no attribute 'SSL_ST_INIT')
Processing commands for cont...@bugs.debian.org: > affects 843631 bugwarrior Bug #843631 [python-cryptography] STOP BREAKING PYOPENSSL WHEN UPLOADING CRYPTOGRAPHY Added indication that 843631 affects bugwarrior > End of message, stopping processing here. Please contact me if you need assistance. -- 843631: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843631 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#842204: marked as done (gatos: FTBFS: configure: error: --- Wow it s only work under Linux)
Your message dated Tue, 8 Nov 2016 20:12:32 +0200 with message-id <20161108181232.joa2pz5x5qc6w...@bunk.spdns.de> and subject line Re: gatos: FTBFS: configure: error: --- Wow it s only work under Linux has caused the Debian Bug report #842204, regarding gatos: FTBFS: configure: error: --- Wow it s only work under Linux 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.) -- 842204: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=842204 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gatos Version: 0.0.5-19 Severity: serious Justification: fails to build from source User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org Dear Maintainer, gatos fails to build from source in unstable/amd64: […] 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 whether to enable maintainer-specific portions of Makefiles... no checking build system type... x86_64-unknown-linux-gnu checking host system type... x86_64-unknown-linux-gnu configure: error: --- Wow it s only work under Linux ./configure: line 2108: exit: FreeBSD: numeric argument required ./configure: line 2108: exit: FreeBSD: numeric argument required debian/rules:15: recipe for target 'configure-stamp' failed make: *** [configure-stamp] Error 2 […] The full build log is attached. Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `- gatos.0.0.5-19.unstable.amd64.log.txt.gz Description: Binary data --- End Message --- --- Begin Message --- On Wed, Oct 26, 2016 at 10:28:29PM +0100, Chris Lamb wrote: > Source: gatos > Version: 0.0.5-19 > Severity: serious > Justification: fails to build from source > User: reproducible-bui...@lists.alioth.debian.org > Usertags: ftbfs > X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org > > Dear Maintainer, > > gatos fails to build from source in unstable/amd64: >... $ grep ^Architecture debian/control Architecture: i386 Architecture: i386 Architecture: i386 $ > Regards, cu Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said. Pearl S. Buck - Dragon Seed--- End Message ---
Bug#840073: Bug: #840073 Patch to fix upgrade from jessie to stretch/testing
tags 840073 patch
thanks
Hi,
looking at the problem and setting up piuparts, and using a local repository, I
think the problem with upgrade from jessie to stretch/sid is solved with the
attached patch.
The following has been tested:
* upgrade from stretch (0.21-3) to sid (0.21-4)
* upgrade from jessie (0.13.1-4) to sid (0.21-4)
* upgrade from kessie (0.13.1-4) to stretch/testing (0.21-4)
piuparts logs are available on request.
I have not been able to upgrade from jessie (without openrc) to stretch/sid
(0.21-4). Anybody knows ho to do that (if needed)?
The only line in the patch that I'm unsure of is the removal of:
[ ${svc} = reboot ] && continue
in openrc.postinst.
I need somebody doing an upload of the new package, of course modifying the
changelog accordingly: Adam/Benda?
Thanks!diff -uNr openrc-0.21-3/debian/changelog openrc-0.21/debian/changelog
--- openrc-0.21-3/debian/changelog 2016-09-24 02:11:37.0 +0200
+++ openrc-0.21/debian/changelog 2016-11-08 09:32:48.740226951 +0100
@@ -1,3 +1,12 @@
+openrc (0.21-4) unstable; urgency=medium
+
+ [ Svante Signell ]
+ * Fix upgrade from jessie to stretch by adding openrc.preinst
+and modifying openrc.postinst for conffile transit (Closes #840073)
+ * Revert fix for #834014
+
+ -- Adam Borowski Tue, 08 Nov 2016 09:20:37 +0100
+
openrc (0.21-3) unstable; urgency=medium
[ Marvin Kohl ]
diff -uNr openrc-0.21-3/debian/openrc.install.in openrc-0.21/debian/openrc.install.in
--- openrc-0.21-3/debian/openrc.install.in 2016-09-24 01:25:57.0 +0200
+++ openrc-0.21/debian/openrc.install.in 2016-11-08 18:06:02.939872210 +0100
@@ -4,6 +4,5 @@
debian/tmp/etc/
debian/tmp/usr/share/man/man8 /usr/share/man
-debian/transit /etc/init.d
debian/rc /etc/init.d
debian/rcS /etc/init.d
diff -uNr openrc-0.21-3/debian/openrc.postinst openrc-0.21/debian/openrc.postinst
--- openrc-0.21-3/debian/openrc.postinst 2016-09-24 01:25:57.0 +0200
+++ openrc-0.21/debian/openrc.postinst 2016-11-08 17:58:45.151877253 +0100
@@ -46,10 +46,6 @@
if [ -f ${initsh} ]; then
# no need to duplicate services in the off runlevel
egrep -q '# Default-Start:\s+[S12345]' ${initsh} && continue
-
- # reboot is managed by transit as below
- [ ${svc} = reboot ] && continue
-
rc-update add ${svc} off
else
echo "*** WARNING: dangling link $rclink"
@@ -58,7 +54,6 @@
done
rc-update add savecache off
- rc-update add transit shutdown
rc-update -u
if [ "$dsvcs" != "" ]; then
diff -uNr openrc-0.21-3/debian/openrc.preinst openrc-0.21/debian/openrc.preinst
--- openrc-0.21-3/debian/openrc.preinst 1970-01-01 01:00:00.0 +0100
+++ openrc-0.21/debian/openrc.preinst 2016-11-08 18:24:06.579859726 +0100
@@ -0,0 +1,27 @@
+# Remove a no-longer used conffile
+rm_conffile() {
+local PKGNAME="$1"
+local CONFFILE="$2"
+
+[ -e "$CONFFILE" ] || return 0
+
+local md5sum="$(md5sum $CONFFILE | sed -e 's/ .*//')"
+local old_md5sum="$(dpkg-query -W -f='${Conffiles}' $PKGNAME | \
+sed -n -e "\' $CONFFILE ' { s/ obsolete$//; s/.* //; p }")"
+if [ "$md5sum" != "$old_md5sum" ]; then
+echo "Obsolete conffile $CONFFILE has been modified by you."
+echo "Saving as $CONFFILE.dpkg-bak ..."
+mv -f "$CONFFILE" "$CONFFILE".dpkg-bak
+else
+echo "Removing obsolete conffile $CONFFILE ..."
+rm -f "$CONFFILE"
+fi
+}
+
+case "$1" in
+install|upgrade)
+if dpkg --compare-versions "$2" le "$LASTVERSION"; then
+rm_conffile openrc "/etc/pkg/conf.1"
+rm_conffile openrc "/etc/pkg/conf.2"
+fi
+esac
diff -uNr openrc-0.21-3/debian/rules openrc-0.21/debian/rules
--- openrc-0.21-3/debian/rules 2016-09-24 01:39:09.0 +0200
+++ openrc-0.21/debian/rules 2016-11-08 09:26:27.716231340 +0100
@@ -67,7 +67,7 @@
done
# We don't want the Gentoo init scripts, but only want savecache to stay
- find $(CURDIR)/debian/openrc/etc/init.d/* -name savecache -or -name rc -or -name rcS -or -name transit -prune -o -exec rm -f {} +
+ find $(CURDIR)/debian/openrc/etc/init.d/* -name savecache -or -name rc -or -name rcS -prune -o -exec rm -f {} +
for dir in boot default sysinit shutdown; do \
rm -f $(CURDIR)/debian/openrc/etc/runlevels/$${dir}/* ; \
diff -uNr openrc-0.21-3/debian/transit openrc-0.21/debian/transit
--- openrc-0.21-3/debian/transit 2016-09-24 01:25:57.0 +0200
+++ openrc-0.21/debian/transit 1970-01-01 01:00:00.0 +0100
@@ -1,19 +0,0 @@
-#!/sbin/openrc-run
-
-description="Call halt through OpenRC style."
-
-depend() {
- keyword -prefix
- after *
-}
-
-start()
-{
- if [ "$RC_REBOOT" = "YES" ]; then
- ebegin "reboot runlevel..."
- exec /etc/init.d/reboot stop
- else
- ebegin "shutdown runlevel..."
- exec /etc/init.d/halt stop
- fi
-}
Processed: Bug: #840073 Patch to fix upgrade from jessie to stretch/testing
Processing commands for cont...@bugs.debian.org: > tags 840073 patch Bug #840073 [openrc] openrc: prompting due to modified conffiles which were not modified by the user: /etc/init.d/transit Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 840073: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840073 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: retitle 843673 to python3-pycodestyle: breaks flake8
Processing commands for cont...@bugs.debian.org: > retitle 843673 python3-pycodestyle: breaks flake8 Bug #843673 [python3-pycodestyle] python3-pycodestyle: makes flake8 emit warnings on stdout Changed Bug title to 'python3-pycodestyle: breaks flake8' from 'python3-pycodestyle: makes flake8 emit warnings on stdout'. > thanks Stopping processing here. Please contact me if you need assistance. -- 843673: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843673 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#833754: New upstream version
I diffed the Debian and Ubuntu build logs, and the only difference I see in build flags is that Ubuntu adds the -Bsymbolic_functions link flag. Though, if I correctly understand the description of the flag, then I don't think that's related. As for package version differences, the only signficiant dependency at runtime (other than libc6/libstdc++) is libicu, but the package verison in Debian and Ubuntu is identical. What I'd really like to get is a stack trace of one of the exceptions thrown by the sample programs. A core file would be even better. But I don't have access to an s390x system. Would someone be willing to sponsor my temporary access to the s390x porter box? If not, could someone with access get me a stack trace or core file showing the failure? I could provide instructions if needed.
Processed: Re: python3-pycodestyle: makes flake8 emit warnings on stdout
Processing control commands: > severity -1 grave Bug #843673 [python3-pycodestyle] python3-pycodestyle: makes flake8 emit warnings on stdout Severity set to 'grave' from 'normal' -- 843673: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843673 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#843675: asn1c-doc: fails to upgrade from 'testing' - trying to overwrite /usr/share/doc-base/asn1c
Package: asn1c-doc Version: 0.9.27+dfsg-3 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'testing'. It installed fine in 'testing', then the upgrade to 'sid' 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 asn1c-doc. Preparing to unpack .../asn1c-doc_0.9.27+dfsg-3_all.deb ... Unpacking asn1c-doc (0.9.27+dfsg-3) ... dpkg: error processing archive /var/cache/apt/archives/asn1c-doc_0.9.27+dfsg-3_all.deb (--unpack): trying to overwrite '/usr/share/doc-base/asn1c', which is also in package asn1c 0.9.24+dfsg-1 Errors were encountered while processing: /var/cache/apt/archives/asn1c-doc_0.9.27+dfsg-3_all.deb cheers, Andreas asn1c=0.9.24+dfsg-1_asn1c-doc=0.9.27+dfsg-3.log.gz Description: application/gzip
Bug#843674: gocryptfs: FTBFS: "pkg-config": executable file not found in $PATH
Source: gocryptfs Version: 1.0-2 Severity: serious Justification: fails to build from source (but built successfully in the past) Builds of gocryptfs in minimal environments (as on the autobuilders) have been failing: pkg-config: exec: "pkg-config": executable file not found in $PATH Please declare a build dependency on pkg-config, and confirm with pbuilder or the like that you haven't missed anything else. Thanks! FTR, I classified this bug as a regression because it would affect any binNMUs that might be necessary. -- Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org) http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu
Bug#843631: AttributeError: 'module' object has no attribute 'SSL_ST_INIT'
Hi Sandro,
I appreciate your frustration here, and as the maintainer of
python-cryptography of course I'm responsible when there are issues with
the package.
That said, I did actually test pyopenssl before uploading this version, and
it was working locally; in addition, the diff from 1.5.2 to 1.5.3 is almost
trivial (I've attached it for reference); the HKDF fix is a one line change
plus an added test, and the only other changes are bumping the version
number, so I'm still looking into the actual cause of the problem.
I think the mistake I made when testing locally was that I didn't update my
build chroot first; if the problem is related to newer build-dependencies
(eg. python-cffi) then that would explain why my local package does not
exhibit the problem while the one from the buildds does. (Of course this is
the result of rushing the 1.5.3 update; I do know better than to rush out a
"trivial" update, as these things often turn out to be less trivial than
assumed, but I felt there was some urgency to getting the new package into
unstable as the security issue is more likely to affect users there and I
guess I let this override my better judgement)
I will follow up again once I track down the root cause of the problem.
commit c551c1690dc2ec0a12f779eaab780da45e40d1c6
Author: Tristan Seligmann
Date: Tue Nov 8 05:34:19 2016 +0200
Import python-cryptography_1.5.3.orig.tar.gz
diff --git a/CHANGELOG.rst b/CHANGELOG.rst
index 0bfd328..9b0bf29 100644
--- a/CHANGELOG.rst
+++ b/CHANGELOG.rst
@@ -1,6 +1,13 @@
Changelog
=
+1.5.3 - 2016-11-05
+~~
+
+* **SECURITY ISSUE**: Fixed a bug where ``HKDF`` would return an empty
+ byte-string if used with a ``length`` less than ``algorithm.digest_size``.
+ Credit to **Markus Döring** for reporting the issue.
+
1.5.2 - 2016-09-26
~~
diff --git a/PKG-INFO b/PKG-INFO
index 3c67042..9de24de 100644
--- a/PKG-INFO
+++ b/PKG-INFO
@@ -1,6 +1,6 @@
Metadata-Version: 1.1
Name: cryptography
-Version: 1.5.2
+Version: 1.5.3
Summary: cryptography is a package which provides cryptographic recipes and primitives to Python developers.
Home-page: https://github.com/pyca/cryptography
Author: The cryptography developers
diff --git a/src/cryptography.egg-info/PKG-INFO b/src/cryptography.egg-info/PKG-INFO
index 3c67042..9de24de 100644
--- a/src/cryptography.egg-info/PKG-INFO
+++ b/src/cryptography.egg-info/PKG-INFO
@@ -1,6 +1,6 @@
Metadata-Version: 1.1
Name: cryptography
-Version: 1.5.2
+Version: 1.5.3
Summary: cryptography is a package which provides cryptographic recipes and primitives to Python developers.
Home-page: https://github.com/pyca/cryptography
Author: The cryptography developers
diff --git a/src/cryptography/__about__.py b/src/cryptography/__about__.py
index 02d6494..6baca0d 100644
--- a/src/cryptography/__about__.py
+++ b/src/cryptography/__about__.py
@@ -14,7 +14,7 @@ __summary__ = ("cryptography is a package which provides cryptographic recipes"
" and primitives to Python developers.")
__uri__ = "https://github.com/pyca/cryptography";
-__version__ = "1.5.2"
+__version__ = "1.5.3"
__author__ = "The cryptography developers"
__email__ = "cryptography-...@python.org"
diff --git a/src/cryptography/hazmat/primitives/kdf/hkdf.py b/src/cryptography/hazmat/primitives/kdf/hkdf.py
index f738bbd..82ed9b1 100644
--- a/src/cryptography/hazmat/primitives/kdf/hkdf.py
+++ b/src/cryptography/hazmat/primitives/kdf/hkdf.py
@@ -91,7 +91,7 @@ class HKDFExpand(object):
output = [b""]
counter = 1
-while (self._algorithm.digest_size // 8) * len(output) < self._length:
+while self._algorithm.digest_size * (len(output) - 1) < self._length:
h = hmac.HMAC(key_material, self._algorithm, backend=self._backend)
h.update(output[-1])
h.update(self._info)
diff --git a/tests/hazmat/primitives/test_hkdf.py b/tests/hazmat/primitives/test_hkdf.py
index e33529c..a05fd75 100644
--- a/tests/hazmat/primitives/test_hkdf.py
+++ b/tests/hazmat/primitives/test_hkdf.py
@@ -142,6 +142,17 @@ class TestHKDF(object):
hkdf.verify(b"foo", u"bar")
+def test_derive_short_output(self, backend):
+hkdf = HKDF(
+hashes.SHA256(),
+4,
+salt=None,
+info=None,
+backend=backend
+)
+
+assert hkdf.derive(b"\x01" * 16) == b"gJ\xfb{"
+
@pytest.mark.requires_backend_interface(interface=HMACBackend)
class TestHKDFExpand(object):
Bug#843628: marked as done (libmems: FTBFS with Boost 1.62)
Your message dated Tue, 08 Nov 2016 17:34:55 +
with message-id
and subject line Bug#843628: fixed in libmems 1.6.0+4725-4
has caused the Debian Bug report #843628,
regarding libmems: FTBFS with Boost 1.62
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.)
--
843628: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843628
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libmems
Version: 1.6.0+4725-3
Severity: serious
Tags: patch
Hi Maintainer
libmems FTBFS with Boost 1.62 and outputs the following error:
In file included from ../libMems/AbstractMatch.h:19:0,
from ../libMems/UngappedLocalAlignment.h:18,
from ../libMems/Match.h:19,
from ../libMems/MatchFinder.h:17,
from ../libMems/MemHash.h:20,
from ../libMems/RepeatHash.h:16,
from RepeatHash.cpp:13:
/usr/include/boost/type_traits/remove_pointer.hpp:21:21: error: missing binary operator
before token "("
#if BOOST_WORKAROUND(BOOST_MSVC, < 1900)
^
The attached patch adds a missing include so that BOOST_WORKAROUND is defined.
Regards
Graham
Description: Fix FTBFS with Boost 1.62
Add missing include so that BOOST_WORKAROUND is defined.
Author: Graham Inggs
Last-Update: 2016-11-08
--- a/libMems/AbstractMatch.h
+++ b/libMems/AbstractMatch.h
@@ -16,6 +16,7 @@
#include "libGenome/gnClone.h"
#include
#include
+#include
#include
#include
#include
--- End Message ---
--- Begin Message ---
Source: libmems
Source-Version: 1.6.0+4725-4
We believe that the bug you reported is fixed in the latest version of
libmems, 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 843...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Andreas Tille (supplier of updated libmems 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, 08 Nov 2016 14:16:07 +0100
Source: libmems
Binary: libmems-1.6-dev libmems-1.6-1v5
Architecture: source amd64
Version: 1.6.0+4725-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team
Changed-By: Andreas Tille
Description:
libmems-1.6-1v5 - library to support DNA string matching and comparative
genomics
libmems-1.6-dev - development library to support DNA string matching and
comparativ
Closes: 843628
Changes:
libmems (1.6.0+4725-4) unstable; urgency=medium
.
* Use fake watch file
* Add missing include so that BOOST_WORKAROUND is defined (thanks to
(Graham Inggs for the patch)
Closes: #843628
* Add patch to really drop explicit version in package names but do not
activate the patch due to transition freeze
Checksums-Sha1:
ad765bdd0bdaa41619209d10c5278fdec2de8871 2193 libmems_1.6.0+4725-4.dsc
4bb497bffb2138792a6d66a3a2a93257863b0608 7856
libmems_1.6.0+4725-4.debian.tar.xz
841c750ebd95193c52ba6b80e4bdc707bbc9ed60 7868260
libmems-1.6-1v5-dbgsym_1.6.0+4725-4_amd64.deb
85484a59042b1384e650fce3f99c632f3ca6325d 643748
libmems-1.6-1v5_1.6.0+4725-4_amd64.deb
c48876f4c21a0c6fb9130d7ed948059d8a2ebca0 919094
libmems-1.6-dev_1.6.0+4725-4_amd64.deb
c17da18bdceebd4b549afdb4fe4f533563fa5165 6170
libmems_1.6.0+4725-4_20161108T171259z-c34688ca.buildinfo
Checksums-Sha256:
8090e4497123f4beb721df9b374e20d8fcc374d6d02d4436e1bc0905aa881de8 2193
libmems_1.6.0+4725-4.dsc
b22b2292547d63f004032ac960ca89ef581d4ee2d71b6ca6a103f4b73491aecd 7856
libmems_1.6.0+4725-4.debian.tar.xz
eb323dffae3605d59f03503e91d3f46e46030405c80abaf0315afcc3dc5353a3 7868260
libmems-1.6-1v5-dbgsym_1.6.0+4725-4_amd64.deb
3759e22eff59324802bc51091cde960b9f148f6d43178ec6e54a0a8cda18ae82 643748
libmems-1.6-1v5_1.6.0+4725-4_amd64.deb
0c8db1098de159006adc7900aa712b5bd32c7bdfe3c6dcf7b792520268b645b6 919094
libmems-1.6-dev_1.6.0+4725-4_amd64.deb
88cdbc09512b463caa8bc51c172df3a3f2f5acc1e7d8a1ca8168e09d35d178c0 6170
libmems_1.6.0+4725-4_20161108T171259z-c34688ca.buildinfo
Files:
e0a9001ec491c82af55904c6eeed41ca 2193 science optional libmems_1.6.0+4725-4.dsc
f75058ea2f982e39bec1e02769da5d58 7856 science optional
libmems_1.6.0+4725-4.debian.tar.xz
44b476c62aab2c921b0db55af5bb6f29 786826
Processed: Fix for the varnish FTBFS
Processing control commands: > tags -1 patch Bug #838900 [src:varnish] varnish: FTBFS when built with dpkg-buildpackage -A (No such file or directory) Added tag(s) patch. -- 838900: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=838900 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#838900: Fix for the varnish FTBFS
Control: tags -1 patch The problem seems to be that dh_auto_install is overriden, instead of dh_auto_install-arch. The fix for that is: --- debian/rules.old2016-11-08 17:02:45.0 + +++ debian/rules2016-11-08 17:12:40.0 + @@ -52,7 +52,7 @@ override_dh_auto_configure: dh_auto_configure -- $(LOCAL_CONFIGURE_FLAGS) -override_dh_auto_install: +override_dh_auto_install-arch: dh_auto_install -a install -d debian/tmp/etc/varnish install -T -m 0644 etc/example.vcl debian/tmp/etc/varnish/default.vcl cu Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said. Pearl S. Buck - Dragon Seed
Bug#829515: marked as done (htseq: B-D python-pysam not available on all architectures where htseq previously built)
Your message dated Tue, 8 Nov 2016 18:32:09 +0100 with message-id <20161108173209.ga16...@an3as.eu> and subject line Closing this bug since architectures with missing Build-Depends are removed has caused the Debian Bug report #829515, regarding htseq: B-D python-pysam not available on all architectures where htseq previously built 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.) -- 829515: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=829515 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: htseq Version: 0.6.1p1-4 Severity: serious Justification: fails to build from source htseq 0.6 added a Build-Depends: python-pysam (for testing), but that is only available on a few architectures. Either restrict this to the architectures where it is available or request decrufting of the outdated binary packages on the architectures where it is missing/failing. Andreas --- End Message --- --- Begin Message --- Hi, ftpmaster has removed the architectures with failed builds due to missing Build-Depends (see #842820). Kind regards Andreas. -- http://fam-tille.de--- End Message ---
Bug#828612: marked as done (yadifa: FTBFS with openssl 1.1.0)
Your message dated Tue, 08 Nov 2016 15:52:46 + with message-id and subject line Bug#828612: fixed in yadifa 2.2.2-1 has caused the Debian Bug report #828612, regarding yadifa: FTBFS with openssl 1.1.0 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.) -- 828612: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828612 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: yadifa Version: 2.1.6-1 Severity: important Control: block 827061 by -1 Hi, OpenSSL 1.1.0 is about to released. During a rebuild of all packages using OpenSSL this package fail to build. A log of that build can be found at: https://breakpoint.cc/openssl-1.1-rebuild-2016-05-29/Attempted/yadifa_2.1.6-1_amd64-20160529-1558 On https://wiki.openssl.org/index.php/1.1_API_Changes you can see various of the reasons why it might fail. There are also updated man pages at https://www.openssl.org/docs/manmaster/ that should contain useful information. There is a libssl-dev package available in experimental that contains a recent snapshot, I suggest you try building against that to see if everything works. If you have problems making things work, feel free to contact us. Kurt --- End Message --- --- Begin Message --- Source: yadifa Source-Version: 2.2.2-1 We believe that the bug you reported is fixed in the latest version of yadifa, 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 828...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Markus Schade (supplier of updated yadifa 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, 08 Nov 2016 12:21:48 +0100 Source: yadifa Binary: yadifa libyadifa-dev Architecture: source Version: 2.2.2-1 Distribution: unstable Urgency: medium Maintainer: Markus Schade Changed-By: Markus Schade Description: libyadifa-dev - development libraries and header files for YADIFA yadifa - Internet Domain Name Server Closes: 828612 Changes: yadifa (2.2.2-1) unstable; urgency=medium . * New upstream version 2.2.2 (Closes: #828612) * Refreshed no-compiledate patches * Update spelling fix patches Checksums-Sha1: abe98e5854757edf8f4e99318cfbb632bc319c31 1873 yadifa_2.2.2-1.dsc 5af81e6d2ef1725b8c340684f70e1e215dbfb21b 3670224 yadifa_2.2.2.orig.tar.gz f01f84e80b9e0fb51d3192360d90d7b341dc5182 17532 yadifa_2.2.2-1.debian.tar.xz Checksums-Sha256: 77e5da84a82e7ed7e11490911cd40249a0526bf636ad3752c6c54aedcd565255 1873 yadifa_2.2.2-1.dsc 8f4ff3ed9b15f13d6e50e48d4ad5d984f061a652f385514720967b03eb139729 3670224 yadifa_2.2.2.orig.tar.gz e42c75e6ec95da6fc50bcfdf7ca594ab707a144c1d60fd45547d0747cc6be290 17532 yadifa_2.2.2-1.debian.tar.xz Files: 4fac726174b9ffda7ffc2365a6d5b341 1873 net optional yadifa_2.2.2-1.dsc 31748cbadac36901ea2f4c8f340c35c0 3670224 net optional yadifa_2.2.2.orig.tar.gz 0d0e5ca952a61182fde11f9bb50d182c 17532 net optional yadifa_2.2.2-1.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQIcBAEBCAAGBQJYIe7+AAoJEPNPCXROn13Z5ygP/21FmkzN2TFeBmcu3PkhYeet IAN1mrviD9Kh/JXLjdMPpAFlIbXw/tE0X1q7jsgEOdw71gvhkq/MHMuHubj2hlGm /uwfKWe76PNyyx7R1yqL03TfE4wX59bTq+OlGtZDEbj4QBZfL1WyS6gP00xhmn7V 241VTxgsiDTuRonx7mG5glb7p9nzm0Y1mHzNIv4g88V2426SwG9shk4HQD/oWWRD zFL3iuP4zaeRKsnAdmAB4iSYf/uaKPV/Il+8Lamru8pvGoB7Zseaxhc2QslcQbFM SihY26sE52PueHRrXfqdXsYIibWEJpFSjQ4ZCqX/BOFyl+UqSCYoJEHWZr+kiz91 hfV+kxSeWO8NVHD4aVXMxuAQ+Gcu4+8v4fU5ONN2N4x2rRbZWO69SydKRKSOkwBO nsV4zQeQLJKM2ypkRP9OTN0hnn26z6pJBPc3S1fEN3sP+nmhcNoqzTRPUjL07smu QIFGMD3ybFsu7ha894yU/fFNgTVuiquOFUZF2gYz+ggIAChjG/PwENBXKd2OmwFP /g3hrQsMdXOCc926Jdcd6rdTjV8KOSR1itPwvMv46A1WMluxtHrEI5pUygtgLThn DQdd1qTs1f7XS4Ka0ACUwCRcvv+21iDc1wUiZyHXItKR4XTUz41nvo7EeQiWwdTC HdFZwcgYB0l2Ad8kbw3p =bRtZ -END PGP SIGNATURE End Message ---
Bug#838624: marked as done (recutils: FTBFS: getopt.h:26:18: fatal error: stdc.h: No such file or directory)
Your message dated Tue, 08 Nov 2016 15:33:32 + with message-id and subject line Bug#838624: fixed in recutils 1.7-1.1 has caused the Debian Bug report #838624, regarding recutils: FTBFS: getopt.h:26:18: fatal error: stdc.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.) -- 838624: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=838624 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: recutils Version: 1.7-1 Severity: serious Justification: fails to build from source User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org Dear Maintainer, recutils fails to build from source in unstable/amd64: [..] libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../src -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/home/lamby/temp/cdt.20160923083513.DG8uiulcUB.db.recutils/recutils-1.7=. -fstack-protector-strong -Wformat -Werror=format-security -c wctype-h.c -fPIE -o wctype-h.o >/dev/null 2>&1 /bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I../src -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/home/lamby/temp/cdt.20160923083513.DG8uiulcUB.db.recutils/recutils-1.7=. -fPIE -fstack-protector-strong -Wformat -Werror=format-security -c -o xmalloc.lo xmalloc.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../src -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/home/lamby/temp/cdt.20160923083513.DG8uiulcUB.db.recutils/recutils-1.7=. -fstack-protector-strong -Wformat -Werror=format-security -c xmalloc.c -fPIC -DPIC -o .libs/xmalloc.o libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../src -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/home/lamby/temp/cdt.20160923083513.DG8uiulcUB.db.recutils/recutils-1.7=. -fstack-protector-strong -Wformat -Werror=format-security -c xmalloc.c -fPIE -o xmalloc.o >/dev/null 2>&1 /bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I../src -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/home/lamby/temp/cdt.20160923083513.DG8uiulcUB.db.recutils/recutils-1.7=. -fPIE -fstack-protector-strong -Wformat -Werror=format-security -c -o xalloc-die.lo xalloc-die.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../src -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/home/lamby/temp/cdt.20160923083513.DG8uiulcUB.db.recutils/recutils-1.7=. -fstack-protector-strong -Wformat -Werror=format-security -c xalloc-die.c -fPIC -DPIC -o .libs/xalloc-die.o libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../src -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/home/lamby/temp/cdt.20160923083513.DG8uiulcUB.db.recutils/recutils-1.7=. -fstack-protector-strong -Wformat -Werror=format-security -c xalloc-die.c -fPIE -o xalloc-die.o >/dev/null 2>&1 /bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I../src -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/home/lamby/temp/cdt.20160923083513.DG8uiulcUB.db.recutils/recutils-1.7=. -fPIE -fstack-protector-strong -Wformat -Werror=format-security -c -o xsize.lo xsize.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../src -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/home/lamby/temp/cdt.20160923083513.DG8uiulcUB.db.recutils/recutils-1.7=. -fstack-protector-strong -Wformat -Werror=format-security -c xsize.c -fPIC -DPIC -o .libs/xsize.o libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../src -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/home/lamby/temp/cdt.20160923083513.DG8uiulcUB.db.recutils/recutils-1.7=. -fstack-protector-strong -Wformat -Werror=format-security -c xsize.c -fPIE -o xsize.o >/dev/null 2>&1 /bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I../src -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/home/lamby/temp/cdt.20160923083513.DG8uiulcUB.db.recutils/recutils-1.7=. -fPIE -fstack-protector-strong -Wformat -Werror=format-security -c -o asnprintf.lo asnprintf.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../src -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/home/lamby/temp/cdt.20160923083513.DG8uiulcUB.db.recutils/recutils-1.7=. -fstack-protector-strong -Wformat -Werror=format-security -c asnprintf.c -fPIC -DPIC -o .libs/asnprintf.o libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../src -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/home/lamby/temp/cdt.20160923083513.DG8uiulcUB.db.recutils/recutils-1.7=. -fstack-protector-strong -Wformat -Werror=
Processed: bug 828473 is forwarded to https://github.com/OpenSMTPD/OpenSMTPD/issues/738
Processing commands for cont...@bugs.debian.org: > forwarded 828473 https://github.com/OpenSMTPD/OpenSMTPD/issues/738 Bug #828473 [src:opensmtpd] opensmtpd: FTBFS with openssl 1.1.0 Set Bug forwarded-to-address to 'https://github.com/OpenSMTPD/OpenSMTPD/issues/738'. > thanks Stopping processing here. Please contact me if you need assistance. -- 828473: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828473 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#843027: marked as done (libc++abi-dev: fails to upgrade from 'testing' - trying to overwrite /usr/include/c++/v1/cxxabi.h)
Your message dated Tue, 08 Nov 2016 15:31:18 + with message-id and subject line Bug#843027: fixed in libc++ 3.9.0-3 has caused the Debian Bug report #843027, regarding libc++abi-dev: fails to upgrade from 'testing' - trying to overwrite /usr/include/c++/v1/cxxabi.h 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.) -- 843027: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843027 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libc++abi-dev Version: 3.9.0-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'testing'. It installed fine in 'testing', then the upgrade to 'sid' 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 libc++abi-dev:amd64. Preparing to unpack .../libc++abi-dev_3.9.0-2_amd64.deb ... Unpacking libc++abi-dev:amd64 (3.9.0-2) ... dpkg: error processing archive /var/cache/apt/archives/libc++abi-dev_3.9.0-2_amd64.deb (--unpack): trying to overwrite '/usr/include/c++/v1/cxxabi.h', which is also in package libc++-dev:amd64 3.5-2 Processing triggers for libc-bin (2.19-18+deb8u6) ... Errors were encountered while processing: /var/cache/apt/archives/libc++abi-dev_3.9.0-2_amd64.deb cheers, Andreas libc++-dev=3.5-2_libc++abi-dev=3.9.0-2.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: libc++ Source-Version: 3.9.0-3 We believe that the bug you reported is fixed in the latest version of libc++, 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 843...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Pauli (supplier of updated libc++ 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, 03 Nov 2016 23:49:34 +0200 Source: libc++ Binary: libc++1 libc++-dev libc++-test libc++abi1 libc++abi-dev libc++abi-test libc++-helpers Architecture: source amd64 all Version: 3.9.0-3 Distribution: unstable Urgency: medium Maintainer: LLVM Packaging Team Changed-By: Pauli Description: libc++-dev - LLVM C++ Standard library (development files) libc++-helpers - LLVM C++ Standard library - build helpers libc++-test - LLVM C++ Standard library (test cases) libc++1- LLVM C++ Standard library libc++abi-dev - LLVM low level support for a standard C++ library (development fi libc++abi-test - libc++abi test cases libc++abi1 - LLVM low level support for a standard C++ library Closes: 843027 Changes: libc++ (3.9.0-3) unstable; urgency=medium . * Team upload * Add missing Replaces dependency to libc++abi-dev (Closes: #843027) * Fix arm EHABI code to allow exceptions on armhf * Fix some unit test on different architectures Checksums-Sha1: 1aae61fbb7e0afdf94b8a424b935c9199f4da864 2309 libc++_3.9.0-3.dsc 6690da983a33f2e4257e43463c25c98da4880f07 11752 libc++_3.9.0-3.debian.tar.xz 97c7bc688f93b6edf405c3cd4e68646126a24bd0 373924 libc++-dev_3.9.0-3_amd64.deb 4c996a041fed2fb38bd8eb6e738eca8ca8c440f1 5760 libc++-helpers_3.9.0-3_all.deb ef2a1ab171916800a0e304d37adfd15c64fa6b0f 911984 libc++-test_3.9.0-3_amd64.deb 24948fe93381f20e75efccbddaeb475db670eb37 177512 libc++1_3.9.0-3_amd64.deb 532599093f324b44749c9409ed79068094543cfa 7524 libc++_3.9.0-3_20161108T144315z-73a4b0f1.buildinfo 5896fd47ecb622a33142a42c99a86a1950d8ba14 80466 libc++abi-dev_3.9.0-3_amd64.deb d27977285f67ff8390edfdf10c7ff955e646c5bc 454028 libc++abi-test_3.9.0-3_amd64.deb eaac0384cf3437d0ab38e1f60b093738469ed2ec 72048 libc++abi1_3.9.0-3_amd64.deb Checksums-Sha256: e933213a9c00d098b6432f4a4f1f91e4f88b3d895e926db49614420e3e46d885 2309 libc++_3.9.0-3.dsc 628ef0d48c076ce67b34b8f9aef29a36fbc97833dc702f29ff426380632396d6 11752 libc++_3.9.0-3.debian.tar.xz c4280ad741509a48b133af024b8e565613a3961102066a0b3f53b94697f76121 373924 libc++-dev_3.9.0-3_amd64.deb 3763f0106f7cef444d0c16e251e4463c045db737f953c3f91ec5979a85d06dfb 576
Bug#841049: marked as done (Security fixes from the October 2016 CPU)
Your message dated Tue, 08 Nov 2016 15:32:11 + with message-id and subject line Bug#841049: fixed in mysql-5.6 5.6.34-1 has caused the Debian Bug report #841049, regarding Security fixes from the October 2016 CPU 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.) -- 841049: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841049 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: mysql-5.6 Version: 5.6.30-1 Severity: grave Tags: security upstream fixed-upstream The Oracle Critical Patch Update for October 2016 will be released on Tuesday, October 18. According to the pre-release announcement [1], it will contain information about CVEs fixed in MySQL 5.6.34. The CVE numbers will be available when the CPU is released. Regards, Norvald H. Ryeng [1] http://www.oracle.com/technetwork/security-advisory/cpuoct2016-2881722.html --- End Message --- --- Begin Message --- Source: mysql-5.6 Source-Version: 5.6.34-1 We believe that the bug you reported is fixed in the latest version of mysql-5.6, 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 841...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Lars Tangvald (supplier of updated mysql-5.6 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: Tue, 18 Oct 2016 12:06:09 +0200 Source: mysql-5.6 Binary: libmysqlclient18 libmysqld-pic libmysqld-dev libmysqlclient-dev mysql-client-core-5.6 mysql-client-5.6 mysql-server-core-5.6 mysql-server-5.6 mysql-server mysql-client mysql-testsuite mysql-testsuite-5.6 mysql-source-5.6 Architecture: source Version: 5.6.34-1 Distribution: unstable Urgency: high Maintainer: Debian MySQL Maintainers Changed-By: Lars Tangvald Description: libmysqlclient-dev - MySQL database development files libmysqlclient18 - MySQL database client library libmysqld-dev - MySQL embedded database development files libmysqld-pic - PIC version of MySQL embedded server development files mysql-client - MySQL database client (metapackage depending on the latest versio mysql-client-5.6 - MySQL database client binaries mysql-client-core-5.6 - MySQL database core client binaries mysql-server - MySQL database server (metapackage depending on the latest versio mysql-server-5.6 - MySQL database server binaries and system database setup mysql-server-core-5.6 - MySQL database server binaries mysql-source-5.6 - MySQL source mysql-testsuite - MySQL regression tests mysql-testsuite-5.6 - MySQL 5.6 testsuite Closes: 841049 Changes: mysql-5.6 (5.6.34-1) unstable; urgency=high (security fixes) . * Imported upstream version 5.6.34 to fix security issues: - http://www.oracle.com/technetwork/security-advisory/cpuoct2016-2881722.html - CVE-2016-3492 CVE-2016-5507 CVE-2016-5584 CVE-2016-5609 - CVE-2016-5612 CVE-2016-5616 CVE-2016-5617 CVE-2016-5626 - CVE-2016-5627 CVE-2016-5629 CVE-2016-5630 CVE-2016-6304 - CVE-2016-6662 CVE-2016-7440 CVE-2016-8283 CVE-2016-8284 (Closes: #841049) * Packaging will now create /var/lib/mysql-files, as server will now by default restrict all import/export operations to this directory. This can be changed using the secure-file-priv config option. * Change mysql-testsuite dependency from python to libjson-perl. Tests written in python were rewritten in perl, so testsuite no longer depends on python, but tests fail if libjson-perl is missing. Also added libjson-perl build-dep to fix build-time test failures (LP: #1631338) * Add working dir to perl lib path for dep8 upstream. New versions of perl will no longer automatically include working dir in the path. This was causing the mtr suite to fail to start. * mysql-common is no longer included in source package as it has been moved to src:mysql-defaults * Removed patch fix-man-page-links, as the issue is fixed upstream. Checksums-Sha1: 5c822b5386c8aa5bd5ded5f8d1ca7b58f4cf7e70 3113 mysql-5.6_5.6.34-1.dsc b352b44385668f0d327d3f275f33f660d85497b3 32094762 mysql-5.6_5.6.34.orig.tar.gz f9978dac603a569d6766a510915b49b79e1c4cdb 248404 mysql-5.6_5.6.34-1.debian.tar.xz Checksums-Sh
Bug#843631: AttributeError: 'module' object has no attribute 'SSL_ST_INIT'
control: clone -1 -2 control: reassign -2 pyopenssl control: retitle -2 AttributeError: 'module' object has no attribute 'SSL_ST_INIT' gaah actually cloning On Tue, Nov 8, 2016 at 9:08 AM, Sandro Tosi wrote: > control: clone -1 > control: reassign -1 python-cryptography > control: retitle -1 STOP BREAKING PYOPENSSL WHEN UPLOADING CRYPTOGRAPHY > >> from OpenSSL import rand, crypto, SSL >> File "/usr/lib/python2.7/dist-packages/OpenSSL/SSL.py", line 112, in >> >> SSL_ST_INIT = _lib.SSL_ST_INIT >> AttributeError: 'module' object has no attribute 'SSL_ST_INIT' > > _lib in SSL.py comes from _utils.lib, which is: > > ``` > from cryptography.hazmat.bindings.openssl.binding import Binding > > binding = Binding() > binding.init_static_locks() > ffi = binding.ffi > lib = binding.lib > ``` > > and not surprisingly there was an update to python-cryptography > yesterday. my mirror still has the old version (1.5.2-1) and works > fine, you have installed 1.5.3-1 and it's broken. George, i'll try to > upgrade pyopenssl soon and taht will hopefully fix this. > > Tristan, this is the third or forth time you updated > python-cryptography and broke pyopenssl. This has to stop. now. and > forever. You've proved you're unable to deal with cryptography without > causing a huge about of issues to downstream packages, so learn to > test your reverse dependencies, even more in this case since > cryptography and pyopenssl are so tightly coupled, or orphan > cryptography and let a skillful maintainer pick it up. > > -- > Sandro "morph" Tosi > My website: http://sandrotosi.me/ > Me at Debian: http://wiki.debian.org/SandroTosi > G+: https://plus.google.com/u/0/+SandroTosi -- Sandro "morph" Tosi My website: http://sandrotosi.me/ Me at Debian: http://wiki.debian.org/SandroTosi G+: https://plus.google.com/u/0/+SandroTosi
Processed: Re: [Pkg-chromium-maint] Bug#843624: chromium: since upgrade to latest libnss3-1d chromium shows only "Aw, Snap!"
Processing commands for cont...@bugs.debian.org: > severity 843624 normal Bug #843624 [chromium] chromium: since upgrade to latest libnss3-1d chromium shows only "Aw, Snap!" Severity set to 'normal' from 'grave' > tags 843624 +wheezy Bug #843624 [chromium] chromium: since upgrade to latest libnss3-1d chromium shows only "Aw, Snap!" Added tag(s) wheezy. > thanks Stopping processing here. Please contact me if you need assistance. -- 843624: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843624 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#843624: [Pkg-chromium-maint] Bug#843624: chromium: since upgrade to latest libnss3-1d chromium shows only "Aw, Snap!"
severity 843624 normal tags 843624 +wheezy thanks On Tue, Nov 08, 2016 at 01:32:25PM +0100, J.Coltrane wrote: > I'm running some full up to date installations of Wheezy, x86 and amd64. Since > an update of some nameservice switch related libraries (libnspr4-0d, > libnss3-1d > and libnss3) Chromium is useless. It only shows "Aw, Snap!" even on it's own > config page. Starting Chromium with "--enable-logging --v=1" I see the > following errors: Hi John, The discussion in debian-lts list (which should join) appears to show this issue is known and a workaround/fix is happening. Riku
Processed: Re: Bug#843631: AttributeError: 'module' object has no attribute 'SSL_ST_INIT'
Processing control commands: > clone -1 -2 Bug #843631 [python-cryptography] STOP BREAKING PYOPENSSL WHEN UPLOADING CRYPTOGRAPHY Bug 843631 cloned as bug 843644 > reassign -2 pyopenssl Bug #843644 [python-cryptography] STOP BREAKING PYOPENSSL WHEN UPLOADING CRYPTOGRAPHY Bug reassigned from package 'python-cryptography' to 'pyopenssl'. Ignoring request to alter found versions of bug #843644 to the same values previously set Ignoring request to alter fixed versions of bug #843644 to the same values previously set > retitle -2 AttributeError: 'module' object has no attribute Bug #843644 [pyopenssl] STOP BREAKING PYOPENSSL WHEN UPLOADING CRYPTOGRAPHY Changed Bug title to 'AttributeError: 'module' object has no attribute' from 'STOP BREAKING PYOPENSSL WHEN UPLOADING CRYPTOGRAPHY'. -- 843631: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843631 843644: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843644 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed (with 1 error): Re: Bug#843631: AttributeError: 'module' object has no attribute 'SSL_ST_INIT'
Processing control commands: > clone -1 Unknown command or malformed arguments to command. > reassign -1 python-cryptography Bug #843631 [python-openssl] AttributeError: 'module' object has no attribute 'SSL_ST_INIT' Bug reassigned from package 'python-openssl' to 'python-cryptography'. No longer marked as found in versions pyopenssl/16.1.0-1. Ignoring request to alter fixed versions of bug #843631 to the same values previously set > retitle -1 STOP BREAKING PYOPENSSL WHEN UPLOADING CRYPTOGRAPHY Bug #843631 [python-cryptography] AttributeError: 'module' object has no attribute 'SSL_ST_INIT' Changed Bug title to 'STOP BREAKING PYOPENSSL WHEN UPLOADING CRYPTOGRAPHY' from 'AttributeError: 'module' object has no attribute 'SSL_ST_INIT''. -- 843631: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843631 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#843631: AttributeError: 'module' object has no attribute 'SSL_ST_INIT'
control: clone -1 control: reassign -1 python-cryptography control: retitle -1 STOP BREAKING PYOPENSSL WHEN UPLOADING CRYPTOGRAPHY > from OpenSSL import rand, crypto, SSL > File "/usr/lib/python2.7/dist-packages/OpenSSL/SSL.py", line 112, in > > SSL_ST_INIT = _lib.SSL_ST_INIT > AttributeError: 'module' object has no attribute 'SSL_ST_INIT' _lib in SSL.py comes from _utils.lib, which is: ``` from cryptography.hazmat.bindings.openssl.binding import Binding binding = Binding() binding.init_static_locks() ffi = binding.ffi lib = binding.lib ``` and not surprisingly there was an update to python-cryptography yesterday. my mirror still has the old version (1.5.2-1) and works fine, you have installed 1.5.3-1 and it's broken. George, i'll try to upgrade pyopenssl soon and taht will hopefully fix this. Tristan, this is the third or forth time you updated python-cryptography and broke pyopenssl. This has to stop. now. and forever. You've proved you're unable to deal with cryptography without causing a huge about of issues to downstream packages, so learn to test your reverse dependencies, even more in this case since cryptography and pyopenssl are so tightly coupled, or orphan cryptography and let a skillful maintainer pick it up. -- Sandro "morph" Tosi My website: http://sandrotosi.me/ Me at Debian: http://wiki.debian.org/SandroTosi G+: https://plus.google.com/u/0/+SandroTosi
Bug#843635: hg-git: FTBFS: AttributeError: 'overlayrepo' object has no attribute 'manifestlog'
Source: hg-git Version: 0.8.5-4 Severity: serious Justification: fails to build from source User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org Dear Maintainer, hg-git fails to build from source in unstable/amd64: […] debian/rules override_dh_auto_test make[1]: Entering directory '/home/lamby/temp/cdt.20161108133902.r30Tq7pYYm.db.hg-git/hg-git-0.8.5' make tests TESTFLAGS="--blacklist /home/lamby/temp/cdt.20161108133902.r30Tq7pYYm.db.hg-git/hg-git-0.8.5/debian/hg-git.test_blacklist" make[2]: Entering directory '/home/lamby/temp/cdt.20161108133902.r30Tq7pYYm.db.hg-git/hg-git-0.8.5' cd tests && python run-tests.py --with-hg=`which hg` --blacklist /home/lamby/temp/cdt.20161108133902.r30Tq7pYYm.db.hg-git/hg-git-0.8.5/debian/hg-git.test_blacklist .. --- /home/lamby/temp/cdt.20161108133902.r30Tq7pYYm.db.hg-git/hg-git-0.8.5/tests/test-incoming.t +++ /home/lamby/temp/cdt.20161108133902.r30Tq7pYYm.db.hg-git/hg-git-0.8.5/tests/test-incoming.t.err @@ -55,6 +55,71 @@ $ fn_git_commit -m'add d/gamma line 2' $ cd ../hgrepo $ hg incoming -p | grep -v 'no changes found' + ** Unknown exception encountered with possibly-broken third-party extension hggit + ** which supports versions 3.7 of Mercurial. + ** Please disable hggit and try your action again. + ** If that fixes the bug please report it to https://bitbucket.org/durin42/hg-git/issues + ** Python 2.7.12+ (default, Nov 4 2016, 17:04:30) [GCC 6.2.0 20161027] + ** Mercurial Distributed SCM (version 4.0) + ** Extensions loaded: hggit, strip, mq + Traceback (most recent call last): +File "/usr/bin/hg", line 45, in + mercurial.dispatch.run() +File "/usr/lib/python2.7/dist-packages/mercurial/dispatch.py", line 60, in run + sys.exit((dispatch(request(sys.argv[1:])) or 0) & 255) +File "/usr/lib/python2.7/dist-packages/mercurial/dispatch.py", line 126, in dispatch + ret = _runcatch(req) +File "/usr/lib/python2.7/dist-packages/mercurial/dispatch.py", line 216, in _runcatch + return callcatch(ui, _runcatchfunc) +File "/usr/lib/python2.7/dist-packages/mercurial/dispatch.py", line 225, in callcatch + return func() +File "/usr/lib/python2.7/dist-packages/mercurial/dispatch.py", line 205, in _runcatchfunc + return _dispatch(req) +File "/usr/lib/python2.7/dist-packages/mercurial/dispatch.py", line 901, in _dispatch + cmdpats, cmdoptions) +File "/usr/lib/python2.7/dist-packages/mercurial/dispatch.py", line 650, in runcommand + ret = _runcommand(ui, options, cmd, d) +File "/usr/lib/python2.7/dist-packages/mercurial/dispatch.py", line 909, in _runcommand + return cmdfunc() +File "/usr/lib/python2.7/dist-packages/mercurial/dispatch.py", line 898, in + d = lambda: util.checksignature(func)(ui, *args, **cmdoptions) +File "/usr/lib/python2.7/dist-packages/mercurial/util.py", line 1039, in check + return func(*args, **kwargs) +File "/usr/lib/python2.7/dist-packages/mercurial/extensions.py", line 220, in closure + return func(*(args + a), **kw) +File "/usr/lib/python2.7/dist-packages/mercurial/util.py", line 1039, in check + return func(*args, **kwargs) +File "/usr/lib/python2.7/dist-packages/hgext/mq.py", line 3540, in mqcommand + return orig(ui, repo, *args, **kwargs) +File "/usr/lib/python2.7/dist-packages/mercurial/util.py", line 1039, in check + return func(*args, **kwargs) +File "/usr/lib/python2.7/dist-packages/mercurial/commands.py", line 5151, in incoming + return hg.incoming(ui, repo, source, opts) +File "/usr/lib/python2.7/dist-packages/mercurial/hg.py", line 837, in incoming + return _incoming(display, subreporecurse, ui, repo, source, opts) +File "/usr/lib/python2.7/dist-packages/mercurial/hg.py", line 807, in _incoming + displaychlist(other, chlist, displayer) +File "/usr/lib/python2.7/dist-packages/mercurial/hg.py", line 836, in display + displayer.show(other[n]) +File "/usr/lib/python2.7/dist-packages/mercurial/cmdutil.py", line 1269, in show + self._show(ctx, copies, matchfn, props) +File "/usr/lib/python2.7/dist-packages/mercurial/cmdutil.py", line 1380, in _show + self.showpatch(ctx, matchfn) +File "/usr/lib/python2.7/dist-packages/mercurial/cmdutil.py", line 1398, in showpatch + match=matchfn, stat=False) +File "/usr/lib/python2.7/dist-packages/mercurial/cmdutil.py", line 1211, in diffordiffstat + relroot=relroot): +File "/usr/lib/python2.7/dist-packages/mercurial/patch.py", line 2327, in difflabel + for chunk in func(*args, **kw): +File "/usr/lib/python2.7/dist-packages/mercurial/patch.py", line 2279, in diff + if f not in ctx1: +File "/usr/lib/python2.7/dist-packages
Bug#843629: gvfs-backends: Incomplete/incorrect polkit rules
Am 08.11.2016 um 13:47 schrieb Laurent Bigonville: > Package: gvfs-backends > Version: 1.29.91-1 > Severity: serious > > Hi, > > Since 1.29.91-1, gvfs is shipping polkit rules that are only working > with the newer (>=0.112) version that is only present in experimental. > > For unstable, we need to add a pkla file too. > > Also, the rule file reference the "wheel" group which is not existing in > debian. This should be changed to "sudo" (and/or "admin") for ubuntu > As discussed on IRC: That rules file allows unauthenticated access for users in group sudo to edit root owned files. I'm not convinced that we want to ship such a policy by default, but rather make that opt-in. Simon suggested to ship the rules (and pkla) file as an example. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
