Processed: Re: reassing back to libauthen-captcha-perl
Processing control commands: > notfound -1 libpng16-16 Bug #875627 [libpng16-16] libauthen-captcha-perl: Random failure due to bad images There is no source info for the package 'libpng16-16' at version 'libpng16-16' with architecture '' Unable to make a source version for version 'libpng16-16' Ignoring request to alter found versions of bug #875627 to the same values previously set > reassign -1 libauthen-captcha-perl Bug #875627 [libpng16-16] libauthen-captcha-perl: Random failure due to bad images Bug reassigned from package 'libpng16-16' to 'libauthen-captcha-perl'. No longer marked as found in versions libpng1.6/1.6.32-1. Ignoring request to alter fixed versions of bug #875627 to the same values previously set > found -1 1.024-1 Bug #875627 [libauthen-captcha-perl] libauthen-captcha-perl: Random failure due to bad images Marked as found in versions libauthen-captcha-perl/1.024-1. > severity -1 serious Bug #875627 [libauthen-captcha-perl] libauthen-captcha-perl: Random failure due to bad images Severity set to 'serious' from 'normal' -- 875627: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875627 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#874419: marked as done (kexi-data: fails to upgrade from 'stretch' - trying to overwrite /usr/share/locale/tr/LC_MESSAGES/kexi.mo)
Your message dated Wed, 13 Sep 2017 05:49:47 + with message-id and subject line Bug#874419: fixed in kexi 1:3.0.2-4 has caused the Debian Bug report #874419, regarding kexi-data: fails to upgrade from 'stretch' - trying to overwrite /usr/share/locale/tr/LC_MESSAGES/kexi.mo 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.) -- 874419: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874419 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: kexi-data Version: 1:3.0.2-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'stretch'. It installed fine in 'stretch', then the upgrade to 'buster' 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 kexi-data. Preparing to unpack .../kexi-data_1%3a3.0.2-2_all.deb ... Unpacking kexi-data (1:3.0.2-2) ... dpkg: error processing archive /var/cache/apt/archives/kexi-data_1%3a3.0.2-2_all.deb (--unpack): trying to overwrite '/usr/share/locale/tr/LC_MESSAGES/kexi.mo', which is also in package calligra-l10n-tr 1:2.9.11-1 Errors were encountered while processing: /var/cache/apt/archives/kexi-data_1%3a3.0.2-2_all.deb cheers, Andreas calligra-l10n-tr=1%2.9.11-1_kexi-data=1%3.0.2-2.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: kexi Source-Version: 1:3.0.2-4 We believe that the bug you reported is fixed in the latest version of kexi, 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 874...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Pino Toscano (supplier of updated kexi 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, 13 Sep 2017 07:22:25 +0200 Source: kexi Binary: kexi kexi-data kexi-mysql-driver kexi-postgresql-driver kexi-web-form-widget Architecture: source Version: 1:3.0.2-4 Distribution: unstable Urgency: medium Maintainer: Debian Qt/KDE Maintainers Changed-By: Pino Toscano Description: kexi - integrated database environment for the Calligra Suite kexi-data - data files for Kexi kexi-mysql-driver - MySQL support for kexi kexi-postgresql-driver - PostgreSQL support for kexi kexi-web-form-widget - web form widget for Kexi Closes: 874419 Changes: kexi (1:3.0.2-4) unstable; urgency=medium . * Add also 'tr' to the old calligra-l10n languages. (Closes: #874419) Checksums-Sha1: b1b329564f431a9d1ce93ff6f85b27155f638d3e 3044 kexi_3.0.2-4.dsc 0edb7402bb7fdb2c41931caac359e2d130dac882 7704 kexi_3.0.2-4.debian.tar.xz 87ac26e5495e08cc437b50c85489d0ef82782228 1 kexi_3.0.2-4_source.buildinfo Checksums-Sha256: 7ecf057f013f9545a87e1c932afb036f93e64d80752867b582181072e2ca49fe 3044 kexi_3.0.2-4.dsc d12e4888aefba76ca45f9abbff8ef5894c3eaed52d1571bb6418f086086c38be 7704 kexi_3.0.2-4.debian.tar.xz ca2f9cd86670161602cbaac6e83cf36472ef50cae3e03b73967295edfa60f615 1 kexi_3.0.2-4_source.buildinfo Files: 8567bcca21842104566db3690ff4a07b 3044 kde optional kexi_3.0.2-4.dsc 2569d92ee0e2ed050eb97dea2e341b1f 7704 kde optional kexi_3.0.2-4.debian.tar.xz 072c76439e95e74683184928abf76cf8 1 kde optional kexi_3.0.2-4_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEXyqfuC+mweEHcAcHLRkciEOxP00FAlm4wx8ACgkQLRkciEOx P03s8g/+Ig9bCQx4BxClA6nPAAAtD0KJCWlpCDfjlH8cufoLGB+wxHukn34Mg9jG Jt9K7HK1qcemS/yqlp70s7bBA1eTRxp52193uvAhituZM8dnZrfPUU4rU+P2bfUJ eqdXcjQFeBgtgumeJAOvPn5Z6xkbR2MQTo5nNT7YD54T8V40I0KpaIegGjD1RLzT NATk1sGAWqql3dY4K7B4SkshGRsKF37hdOh1fjXYhvKqUd/BF7cjj34U0pl57+wc RUmZFn2tt4qhlmippCSNN9qPCV6ze+6enzoEWjOAwhi91aAEYh17XLegcHInJ4b6 /j6zXfjyOsqrYFI03dY8BSlBkqGyb0kUXCS/nK52XMe3L6Q2wB+wpkalxLRnWzrX iQUZCJCRCeK/t8YTUSUwvu4OXqFy7vGQfcZl5sY7/Fd7dRB8Spdv6JGUpGr+vJOO s5CGwQdGFi0hGMzVFSjdJAvVoOusdi+oZFOakLoYZMs1tBXV5qTD/g9nxIrFEOqF 5Ps+RSW5Wdr7yWCI8NzkfdNb9++T+cjxQdHHbQAA46BqmETgi31hS/jYBty0ywea HnQrjtG9JznopKTS+E1KVAj0Y9xeKaK4exG8MqiNoCMSeJI
Bug#874418: libdislocker0.7: fails to upgrade from 'stretch' - trying to overwrite /usr/lib/libdislocker.so
Hi, Em 05-09-2017 18:48, Andreas Beckmann escreveu: > during a test with piuparts I noticed your package fails to upgrade from > 'stretch'. > It installed fine in 'stretch', then the upgrade to 'sid' fails > because it tries to overwrite other packages files without declaring a > Breaks+Replaces relation. I'm learning to keep shared libraries, after researching and getting help from other developers I noticed that I did not put the correct version in Breaks + Replaces, I'll fix it soon. > Why is this .so link in the shared library package and not in > the -dev package? This was a palliative solution to solve the problem on #840489 until the upstream fix. As I have already forwarded this bug to the upstream as described at https://github.com/Aorimn/dislocker/issues/96 but it still has not resolved this. > And please get rid of the insane idea of a libdislocker0.6 > transitional package in sid. Sorry, I did not do it the right way and I will fix it ASAP. greetings, -- Giovani Ferreira 0x78494EF72375A66C
Bug#874803: marked as done (libcblas-dev and libatlas-base-dev: error when trying to install together)
Your message dated Wed, 13 Sep 2017 03:23:25 + with message-id and subject line Bug#875564: Removed package(s) from unstable has caused the Debian Bug report #874803, regarding libcblas-dev and libatlas-base-dev: error when trying to install together to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 874803: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874803 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libatlas-base-dev,libcblas-dev Version: libatlas-base-dev/3.10.3-4 Version: libcblas-dev/3.2.1+dfsg-1 Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite Date: 2017-09-09 Architecture: amd64 Distribution: sid Hi, automatic installation tests of packages that share a file and at the same time do not conflict by their package dependency relationships has detected the following problem: Selecting previously unselected package gcc-7-base:amd64. (Reading database ... 10979 files and directories currently installed.) Preparing to unpack .../gcc-7-base_7.2.0-4_amd64.deb ... Unpacking gcc-7-base:amd64 (7.2.0-4) ... Selecting previously unselected package libquadmath0:amd64. Preparing to unpack .../libquadmath0_7.2.0-4_amd64.deb ... Unpacking libquadmath0:amd64 (7.2.0-4) ... Selecting previously unselected package libgfortran4:amd64. Preparing to unpack .../libgfortran4_7.2.0-4_amd64.deb ... Unpacking libgfortran4:amd64 (7.2.0-4) ... Selecting previously unselected package libatlas3-base:amd64. Preparing to unpack .../libatlas3-base_3.10.3-4_amd64.deb ... Unpacking libatlas3-base:amd64 (3.10.3-4) ... Selecting previously unselected package libatlas-base-dev:amd64. Preparing to unpack .../libatlas-base-dev_3.10.3-4_amd64.deb ... Unpacking libatlas-base-dev:amd64 (3.10.3-4) ... Selecting previously unselected package libblas-common. Preparing to unpack .../libblas-common_3.7.1-1+b1_amd64.deb ... Unpacking libblas-common (3.7.1-1+b1) ... Selecting previously unselected package libf2c2:amd64. Preparing to unpack .../libf2c2_20130926-2_amd64.deb ... Unpacking libf2c2:amd64 (20130926-2) ... Selecting previously unselected package libcblas3. Preparing to unpack .../libcblas3_3.2.1+dfsg-1_amd64.deb ... Unpacking libcblas3 (3.2.1+dfsg-1) ... dpkg: error processing archive /var/cache/apt/archives/libcblas3_3.2.1+dfsg-1_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/libcblas.so.3', which is also in package libatlas3-base:amd64 3.10.3-4 Selecting previously unselected package libcblas-dev. Preparing to unpack .../libcblas-dev_3.2.1+dfsg-1_amd64.deb ... Unpacking libcblas-dev (3.2.1+dfsg-1) ... dpkg: error processing archive /var/cache/apt/archives/libcblas-dev_3.2.1+dfsg-1_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/libcblas.a', which is also in package libatlas-base-dev:amd64 3.10.3-4 dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) Processing triggers for libc-bin (2.24-17) ... Errors were encountered while processing: /var/cache/apt/archives/libcblas3_3.2.1+dfsg-1_amd64.deb /var/cache/apt/archives/libcblas-dev_3.2.1+dfsg-1_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) E: Error calling setupterm: 0 E: cow-shell unlink .ilist: No such file or directory This is a serious bug as it makes installation fail, and violates sections 7.6.1 and 10.1 of the policy. An optimal solution would consist in only one of the packages installing that file, and renaming or removing the file in the other package. Depending on the circumstances you might also consider Replace relations or file diversions. If the conflicting situation cannot be resolved then, as a last resort, the two packages have to declare a mutual Conflict. Please take into account that Replaces, Conflicts and diversions should only be used when packages provide different implementations for the same functionality. Here is a list of files that are known to be shared by both packages (according to the Contents file for sid/amd64, which may be slightly out of sync): /usr/lib/x86_64-linux-gnu/libcblas.a /usr/lib/x86_64-linux-gnu/libcblas.so This bug has been filed against both packages. If you, the maintainers of the two packages in question, have agreed on which of the packages will resolve the problem please reassign the bug to that package. You may then also register in the BTS that the other package is affected by the bug. -Ralf. PS: for more information about the detection of file overwrite errors of this kind see http://qa.debian.org/dose/file-overwrites.html. --- End Message --- --- Begin Message --- Vers
Bug#874802: marked as done (libcblas3 and libatlas3-base: error when trying to install together)
Your message dated Wed, 13 Sep 2017 03:23:25 + with message-id and subject line Bug#875564: Removed package(s) from unstable has caused the Debian Bug report #874802, regarding libcblas3 and libatlas3-base: error when trying to install together to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 874802: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874802 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libatlas3-base,libcblas3 Version: libatlas3-base/3.10.3-4 Version: libcblas3/3.2.1+dfsg-1 Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite Date: 2017-09-09 Architecture: amd64 Distribution: sid Hi, automatic installation tests of packages that share a file and at the same time do not conflict by their package dependency relationships has detected the following problem: Selecting previously unselected package gcc-7-base:amd64. (Reading database ... 10979 files and directories currently installed.) Preparing to unpack .../gcc-7-base_7.2.0-4_amd64.deb ... Unpacking gcc-7-base:amd64 (7.2.0-4) ... Selecting previously unselected package libquadmath0:amd64. Preparing to unpack .../libquadmath0_7.2.0-4_amd64.deb ... Unpacking libquadmath0:amd64 (7.2.0-4) ... Selecting previously unselected package libgfortran4:amd64. Preparing to unpack .../libgfortran4_7.2.0-4_amd64.deb ... Unpacking libgfortran4:amd64 (7.2.0-4) ... Selecting previously unselected package libatlas3-base:amd64. Preparing to unpack .../libatlas3-base_3.10.3-4_amd64.deb ... Unpacking libatlas3-base:amd64 (3.10.3-4) ... Selecting previously unselected package libblas-common. Preparing to unpack .../libblas-common_3.7.1-1+b1_amd64.deb ... Unpacking libblas-common (3.7.1-1+b1) ... Selecting previously unselected package libf2c2:amd64. Preparing to unpack .../libf2c2_20130926-2_amd64.deb ... Unpacking libf2c2:amd64 (20130926-2) ... Selecting previously unselected package libcblas3. Preparing to unpack .../libcblas3_3.2.1+dfsg-1_amd64.deb ... Unpacking libcblas3 (3.2.1+dfsg-1) ... dpkg: error processing archive /var/cache/apt/archives/libcblas3_3.2.1+dfsg-1_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/libcblas.so.3', which is also in package libatlas3-base:amd64 3.10.3-4 Processing triggers for libc-bin (2.24-17) ... Errors were encountered while processing: /var/cache/apt/archives/libcblas3_3.2.1+dfsg-1_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) This is a serious bug as it makes installation fail, and violates sections 7.6.1 and 10.1 of the policy. An optimal solution would consist in only one of the packages installing that file, and renaming or removing the file in the other package. Depending on the circumstances you might also consider Replace relations or file diversions. If the conflicting situation cannot be resolved then, as a last resort, the two packages have to declare a mutual Conflict. Please take into account that Replaces, Conflicts and diversions should only be used when packages provide different implementations for the same functionality. Here is a list of files that are known to be shared by both packages (according to the Contents file for sid/amd64, which may be slightly out of sync): /usr/lib/x86_64-linux-gnu/libcblas.so.3 This bug has been filed against both packages. If you, the maintainers of the two packages in question, have agreed on which of the packages will resolve the problem please reassign the bug to that package. You may then also register in the BTS that the other package is affected by the bug. -Ralf. PS: for more information about the detection of file overwrite errors of this kind see http://qa.debian.org/dose/file-overwrites.html. --- End Message --- --- Begin Message --- Version: 3.2.1+dfsg-1+rm Dear submitter, as the package clapack has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/875564 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#875453: marked as done (kopanocore: FTBFS (32-bit): symbols not as expected)
Your message dated Tue, 12 Sep 2017 21:12:39 + with message-id and subject line Bug#875453: fixed in kopanocore 8.3.4-1 has caused the Debian Bug report #875453, regarding kopanocore: FTBFS (32-bit): symbols not as expected 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.) -- 875453: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875453 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: kopanocore Version: 8.3.3-1 Severity: serious Justification: fails to build from source Builds of kopanocore for 32-bit architectures such as i386 have started failing, as detailed below (for i386; I haven't cross-checked other architectures). Could you please account for these differences in mangled symbol names? Thanks! --- debian/kopano-libs.symbols (kopano-libs_8.3.3-1_i386) +++ dpkg-gensymbolszTPcxZ 2017-09-11 07:37:24.163161144 + @@ -48,9 +48,12 @@ _Z16conv_out_defaultIN2KC7ECGROUPEjXadL_ZNS1_12ulIsABHiddenvPT_P7_objectPKcPvj@Base 8.3.2 _Z16conv_out_defaultIN2KC7ECQUOTAEbXadL_ZNS1_16bUseDefaultQuotavPT_P7_objectPKcPvj@Base 8.3.2 _Z16conv_out_defaultIN2KC7ECQUOTAEbXadL_ZNS1_19bIsUserDefaultQuotavPT_P7_objectPKcPvj@Base 8.3.2 - _Z16conv_out_defaultIN2KC7ECQUOTAElXadL_ZNS1_10llHardSizevPT_P7_objectPKcPvj@Base 8.3.2 - _Z16conv_out_defaultIN2KC7ECQUOTAElXadL_ZNS1_10llSoftSizevPT_P7_objectPKcPvj@Base 8.3.2 - _Z16conv_out_defaultIN2KC7ECQUOTAElXadL_ZNS1_10llWarnSizevPT_P7_objectPKcPvj@Base 8.3.2 +#MISSING: 8.3.3-1# _Z16conv_out_defaultIN2KC7ECQUOTAElXadL_ZNS1_10llHardSizevPT_P7_objectPKcPvj@Base 8.3.2 +#MISSING: 8.3.3-1# _Z16conv_out_defaultIN2KC7ECQUOTAElXadL_ZNS1_10llSoftSizevPT_P7_objectPKcPvj@Base 8.3.2 +#MISSING: 8.3.3-1# _Z16conv_out_defaultIN2KC7ECQUOTAElXadL_ZNS1_10llWarnSizevPT_P7_objectPKcPvj@Base 8.3.2 + _Z16conv_out_defaultIN2KC7ECQUOTAExXadL_ZNS1_10llHardSizevPT_P7_objectPKcPvj@Base 8.3.3-1 + _Z16conv_out_defaultIN2KC7ECQUOTAExXadL_ZNS1_10llSoftSizevPT_P7_objectPKcPvj@Base 8.3.3-1 + _Z16conv_out_defaultIN2KC7ECQUOTAExXadL_ZNS1_10llWarnSizevPT_P7_objectPKcPvj@Base 8.3.3-1 _Z16conv_out_defaultIN2KC9ECCOMPANYENS0_9ECENTRYIDEXadL_ZNS1_10sCompanyIdvPT_P7_objectPKcPvj@Base 8.3.2 _Z16conv_out_defaultIN2KC9ECCOMPANYENS0_9ECENTRYIDEXadL_ZNS1_14sAdministratorvPT_P7_objectPKcPvj@Base 8.3.2 _Z16conv_out_defaultIN2KC9ECCOMPANYEPwXadL_ZNS1_14lpszServernamevPT_P7_objectPKcPvj@Base 8.3.2 @@ -69,8 +72,9 @@ _ZN4priv8conv_outIPwEEvP7_objectPvjPT_@Base 8.3.2 _ZN4priv8conv_outIbEEvP7_objectPvjPT_@Base 8.3.2 _ZN4priv8conv_outIjEEvP7_objectPvjPT_@Base 8.3.2 - _ZN4priv8conv_outIlEEvP7_objectPvjPT_@Base 8.3.2 +#MISSING: 8.3.3-1# _ZN4priv8conv_outIlEEvP7_objectPvjPT_@Base 8.3.2 _ZN4priv8conv_outItEEvP7_objectPvjPT_@Base 8.3.2 + _ZN4priv8conv_outIxEEvP7_objectPvjPT_@Base 8.3.3-1 libkcpydirector.so.0 kopano-libs #MINVER# #MISSING: 8.3.3-1# (symver|optional)EC_8.1.0 8.0.1 (symver|optional)KC_8.3 8.3.2 -- 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: kopanocore Source-Version: 8.3.4-1 We believe that the bug you reported is fixed in the latest version of kopanocore, 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 875...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Carsten Schoenert (supplier of updated kopanocore 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, 12 Sep 2017 20:52:31 +0200 Source: kopanocore Binary: kopano-libs kopano-core kopano-archiver kopano-backup kopano-common kopano-contacts kopano-dev kopano-dagent kopano-gateway kopano-ical kopano-l10n kopano-monitor kopano-search kopano-server kopano-spooler kopano-utils python-mapi python-kopano php-mapi Architecture: source Version: 8.3.4-1 Distribution: unstable Urgency: medium Maintainer: Giraffe Maintainers Changed-By: Carsten Schoenert Description: kopano-archiver - Complete and feature rich groupware solution - archiver kopano-backup - Complete and feature rich groupw
Bug#874736: marked as done (courier-mta, courier-imap, courier-pop: fails to install: install: target '' is not a directory: No such file or directory)
Your message dated Tue, 12 Sep 2017 21:07:31 + with message-id and subject line Bug#874736: fixed in courier 0.78.0-1 has caused the Debian Bug report #874736, regarding courier-mta, courier-imap, courier-pop: fails to install: install: target '' is not a directory: 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.) -- 874736: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874736 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: courier-mta,courier-imap,courier-pop Version: 0.77.0-3 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Control: found -1 4.18.0+0.77.0-3 Hi, during a test with piuparts I noticed your package failed to install. As per definition of the release team this makes the package too buggy for a release, thus the severity. >From the attached log (scroll to the bottom...): Selecting previously unselected package courier-mta. (Reading database ... (Reading database ... 6578 files and directories currently installed.) Preparing to unpack .../courier-mta_0.77.0-3_amd64.deb ... Adding 'diversion of /usr/bin/addcr to /usr/bin/addcr.ucspi-tcp by courier-mta' Adding 'diversion of /usr/share/man/man1/addcr.1.gz to /usr/share/man/man1/addcr.ucspi-tcp.1.gz by courier-mta' Unpacking courier-mta (0.77.0-3) ... Setting up courier-mta (0.77.0-3) ... update-alternatives: using /usr/bin/lockmail.courier to provide /usr/bin/lockmail (lockmail) in auto mode update-alternatives: using /usr/bin/preline.courier to provide /usr/bin/preline (preline) in auto mode /run/courier/esmtpd.pid.lock: No such file or directory install: target '' is not a directory: No such file or directory dpkg: error processing package courier-mta (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: courier-mta cheers, Andreas courier-mta_0.77.0-3.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: courier Source-Version: 0.78.0-1 We believe that the bug you reported is fixed in the latest version of courier, 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 874...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Markus Wanner (supplier of updated courier 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, 12 Sep 2017 21:58:24 +0200 Source: courier Binary: courier-base courier-maildrop courier-mlm courier-mta courier-faxmail courier-webadmin sqwebmail courier-pcp courier-pop courier-imap courier-ldap courier-doc courier-ssl courier-mta-ssl courier-pop-ssl courier-imap-ssl Architecture: source amd64 all Version: 0.78.0-1 Distribution: unstable Urgency: medium Maintainer: Markus Wanner Changed-By: Markus Wanner Description: courier-base - Courier mail server - base system courier-doc - Courier mail server - additional documentation courier-faxmail - Courier mail server - Fax<->mail gateway courier-imap - Courier mail server - IMAP server courier-imap-ssl - Courier mail server - IMAP over TLS [transitional] courier-ldap - Courier mail server - LDAP support courier-maildrop - Courier mail server - mail delivery agent [transitional package] courier-mlm - Courier mail server - mailing list manager courier-mta - Courier mail server - ESMTP daemon courier-mta-ssl - Courier mail server - ESMTP over TLS [transitional] courier-pcp - Courier mail server - PCP server courier-pop - Courier mail server - POP3 server courier-pop-ssl - Courier mail server - POP3 over TLS [transitional] courier-ssl - Courier mail server - TLS Support [transitional] courier-webadmin - Courier mail server - web-based administration frontend sqwebmail - Courier mail server - webmail server Closes: 874736 Changes: courier (0.78.0-1) unstable; urgency=medium . * New upstream release. * Refresh patches: 0011-Don-t-cleanup-staticlist.c.patch, 0018-Fix-default-configuration-for-Debian.patch, 0019-Remove-upstream-chown-on-install-target.patch, and 0022-mkesmtpdcert-should-use-certsdir.patch. * Drop patch 0
Bug#853382: marked as done (edk2: ftbfs with GCC-7)
Your message dated Tue, 12 Sep 2017 21:08:06 + with message-id and subject line Bug#853382: fixed in edk2 0~20170911.5dfba97c-1 has caused the Debian Bug report #853382, regarding edk2: ftbfs with GCC-7 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.) -- 853382: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853382 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:edk2 Version: 0~20161202.7bbe0b3e-1 Severity: normal Tags: sid buster User: debian-...@lists.debian.org Usertags: ftbfs-gcc-7 Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-7/g++-7, but succeeds to build with gcc-6/g++-6. The severity of this report may be raised before the buster release. There is no need to fix this issue in time for the stretch release. The full build log can be found at: http://people.debian.org/~doko/logs/gcc7-20170126/edk2_0~20161202.7bbe0b3e-1_unstable_gcc7.log The last lines of the build log are at the end of this report. To build with GCC 7, either set CC=gcc-7 CXX=g++-7 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-7/porting_to.html [...] package: automake1.11 version: 1:1.11.6-4 architecture: all - package: autoconf version: 2.69-10 architecture: all - package: acpica-tools version: 20160831-1 architecture: amd64 background-packages: 53583 foreground-packages: 1 total-packages: 53584 broken-packages: 0 +--+ | Cleanup | +--+ Purging /<> Not cleaning session: cloned chroot in use E: Package build dependencies not satisfied; skipping +--+ | Summary | +--+ Build Architecture: amd64 Build-Space: -1 Build-Time: 0 Distribution: unstable Fail-Stage: install-deps Host Architecture: amd64 Install-Time: 0 Job: edk2_0~20161202.7bbe0b3e-1 Machine Architecture: amd64 Package: edk2 Package-Time: 0 Source-Version: 0~20161202.7bbe0b3e-1 Space: -1 Status: given-back Version: 0~20161202.7bbe0b3e-1 Finished at 2017-01-27T12:58:45Z Build needed 00:00:00, -1k disk space E: Package build dependencies not satisfied; skipping DC-Status: Failed 46.536250438s DC-Time-Estimation: 46.536250438 versus expected 641 (r/m: 12.774208148849484 ; m: 46.536250438) --- End Message --- --- Begin Message --- Source: edk2 Source-Version: 0~20170911.5dfba97c-1 We believe that the bug you reported is fixed in the latest version of edk2, 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 853...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. dann frazier (supplier of updated edk2 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, 12 Sep 2017 13:17:42 -0600 Source: edk2 Binary: ovmf qemu-efi-arm qemu-efi-aarch64 qemu-efi Architecture: source Version: 0~20170911.5dfba97c-1 Distribution: unstable Urgency: medium Maintainer: Debian QEMU Team Changed-By: dann frazier Description: ovmf - UEFI firmware for 64-bit x86 virtual machines qemu-efi - transitional dummy package qemu-efi-aarch64 - UEFI firmware for 64-bit ARM virtual machines qemu-efi-arm - UE
Bug#875637: iipimage-server: Wrong configuration file /etc/apache2/mods-available/iipsrv.conf
Package: iipimage-server Version: 1.0-1+b1 Severity: grave Tags: patch Justification: renders package unusable The default installation with Apache2 won't work with the provided configuration file because that file uses "Directory" instead of "Location". A fixed version is shown below. -- System Information: Debian Release: 9.1 APT prefers testing-debug APT policy: (500, 'testing-debug'), (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-3-amd64 (SMP w/16 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages iipimage-server depends on: ii libapache2-mod-fcgid 1:2.3.9-1+b1 ii libc6 2.24-11+deb9u1 ii libfcgi0ldbl 2.4.0-8.4+b1 ii libgcc1 1:6.3.0-18 ii libgomp1 6.3.0-18 ii libjpeg62-turbo 1:1.5.1-2 ii libmemcached111.0.18-4.1 ii libstdc++66.3.0-18 ii libtiff5 4.0.8-2+deb9u1 Versions of packages iipimage-server recommends: ii imagemagick-6.q16 [imagemagick] 8:6.9.7.4+dfsg-11+deb9u1 pn libvips-tools Versions of packages iipimage-server suggests: pn iipimage-doc pn memcached -- Configuration Files: /etc/apache2/mods-available/iipsrv.conf changed: ScriptAlias /iipsrv/ "/usr/lib/iipimage-server/" AllowOverride None Options None Order allow,deny Allow from all = 2.4> Require all granted # Set the module handler AddHandler fcgid-script .fcgi FcgidInitialEnv VERBOSITY "1" FcgidInitialEnv LOGFILE "/var/log/iipsrv.log" FcgidInitialEnv MAX_IMAGE_CACHE_SIZE "10" FcgidInitialEnv JPEG_QUALITY "90" FcgidInitialEnv MAX_CVT "5000" FcgidInitialEnv MEMCACHED_SERVERS "localhost" FcgidIdleTimeout 0 FcgidMaxProcessesPerClass 1 -- no debconf information
Bug#875610: python-pythonmagick: Undefined symbol in python2.7 PythonMagick.x86_64-linux-gnu.so
I get the same result after rebuilding the package from source. There are some python2.7 related warnings including: dpkg-shlibdeps: warning: debian/python-pythonmagick/usr/lib/python2.7/dist-packages/PythonMagick/_PythonMagick.x86_64-linux-gnu.so contains an unresolvable reference to symbol _ZNK6Magick5ColorcvNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcv: it's probably a plugin dpkg-shlibdeps: warning: 13 other similar warnings have been skipped (use -v to see them all) and dpkg-shlibdeps: warning: package could avoid a useless dependency if debian/python-pythonmagick/usr/lib/python2.7/dist-packages/PythonMagick/_PythonMagick.x86_64-linux-gnu.so was not linked against libgomp.so.1 (it uses none of the library's symbols) dpkg-shlibdeps: warning: package could avoid a useless dependency if debian/python-pythonmagick/usr/lib/python2.7/dist-packages/PythonMagick/_PythonMagick.x86_64-linux-gnu.so was not linked against libMagickCore-6.Q16.so.3 (it uses none of the library's symbols) dpkg-shlibdeps: warning: package could avoid a useless dependency if debian/python-pythonmagick/usr/lib/python2.7/dist-packages/PythonMagick/_PythonMagick.x86_64-linux-gnu.so was not linked against libMagickWand-6.Q16.so.3 (it uses none of the library's symbols) Maybe there is a boost dependency that needs to be a bit more accurately defined. I am using: libboost-python-dev 1.62.0.1 libboost-python1.62.0 1.62.0+dfsg-4+b1
Bug#875633: bluez: CVE-2017-1000250: information disclosure vulnerability in service_search_attr_req
Control: tags -1 + patch
And attached the proposed patch.
Regards,
Salvatore
Description: CVE-2017-1000250: information disclosure vulnerability in service_search_attr_req
Origin: vendor
Bug-Debian: https://bugs.debian.org/875633
Bug-RedHat: https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2017-1000250
Bug-SuSE: https://bugzilla.suse.com/show_bug.cgi?id=CVE-2017-1000250
Forwarded: no
Author: Armis Security
Reviewed-by: Salvatore Bonaccorso
Last-Update: 2017-09-12
diff --git a/src/sdpd-request.c b/src/sdpd-request.c
index 1eefdce..ddeea7f 100644
--- a/src/sdpd-request.c
+++ b/src/sdpd-request.c
@@ -918,15 +918,20 @@ static int service_search_attr_req(sdp_req_t *req, sdp_buf_t *buf)
/* continuation State exists -> get from cache */
sdp_buf_t *pCache = sdp_get_cached_rsp(cstate);
if (pCache) {
- uint16_t sent = MIN(max, pCache->data_size - cstate->cStateValue.maxBytesSent);
- pResponse = pCache->data;
- memcpy(buf->data, pResponse + cstate->cStateValue.maxBytesSent, sent);
- buf->data_size += sent;
- cstate->cStateValue.maxBytesSent += sent;
- if (cstate->cStateValue.maxBytesSent == pCache->data_size)
- cstate_size = sdp_set_cstate_pdu(buf, NULL);
- else
- cstate_size = sdp_set_cstate_pdu(buf, cstate);
+ if (cstate->cStateValue.maxBytesSent >= pCache->data_size) {
+ status = SDP_INVALID_CSTATE;
+ SDPDBG("Got bad cstate with invalid size");
+ } else {
+ uint16_t sent = MIN(max, pCache->data_size - cstate->cStateValue.maxBytesSent);
+ pResponse = pCache->data;
+ memcpy(buf->data, pResponse + cstate->cStateValue.maxBytesSent, sent);
+ buf->data_size += sent;
+ cstate->cStateValue.maxBytesSent += sent;
+ if (cstate->cStateValue.maxBytesSent == pCache->data_size)
+ cstate_size = sdp_set_cstate_pdu(buf, NULL);
+ else
+ cstate_size = sdp_set_cstate_pdu(buf, cstate);
+ }
} else {
status = SDP_INVALID_CSTATE;
SDPDBG("Non-null continuation state, but null cache buffer");
Processed: Re: Bug#875633: bluez: CVE-2017-1000250: information disclosure vulnerability in service_search_attr_req
Processing control commands: > tags -1 + patch Bug #875633 [src:bluez] bluez: CVE-2017-1000250: information disclosure vulnerability in service_search_attr_req Ignoring request to alter tags of bug #875633 to the same tags previously set -- 875633: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875633 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#875633: bluez: CVE-2017-1000250: information disclosure vulnerability in service_search_attr_req
Source: bluez Version: 5.23-2 Severity: grave Tags: patch upstream security Hi, the following vulnerability was published for bluez. CVE-2017-1000250[0]: | All versions of the SDP server in BlueZ 5.46 and earlier are | vulnerable to an information disclosure vulnerability which allows | remote attackers to obtain sensitive information from the bluetoothd | process memory. This vulnerability lies in the processing of SDP | search attribute requests. If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2017-1000250 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-1000250 [1] https://bugzilla.novell.com/show_bug.cgi?id=1057342 [2] https://bugzilla.redhat.com/show_bug.cgi?id=1489446 Regards, Salvatore
Bug#871276: marked as done (kopano-libs: requires rebuild against GCC 7 and symbols/shlibs bump)
Your message dated Tue, 12 Sep 2017 22:09:53 +0200 with message-id <20170912200953.s5fqobv5qmlea...@i5.cruise.homelinux.net> and subject line Re: Bug#871276: kopano-libs: requires rebuild against GCC 7 and symbols/shlibs bump has caused the Debian Bug report #871276, regarding kopano-libs: requires rebuild against GCC 7 and symbols/shlibs bump 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.) -- 871276: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871276 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: kopano-libs Version: 8.1.0-3 Severity: serious Tags: sid buster User: debian-...@lists.debian.org Usertags: gcc-7-op-mangling Hi, It appears that your package provides an external symbol that is affected by the recent name mangling changes in GCC 7. See: https://gcc.gnu.org/gcc-7/porting_to.html#conversion-op-mangling In GCC 7, the name mangling for C++ conversion operators which return a type using the abi_tag attribute (most commonly std::string) has changed. When your library is compiled with GCC 7, it will now emit two symbols for the conversion operator using the new and old naming. Executables compiled with GCC 7 will always use the new symbol, while old executables compiled using <= GCC 6 will use the old symbol. For new executables to build without undefined references, your library will need rebuilding with GCC 7. To ensure that new executables will pull in the newer version of the library built with GCC 7: - Your library package should Build-Depend on g++ (>= 4:7). - If your package provides a symbols file, ensure that the new conversion operator symbols have a version matching the version this bug is fixed in (including the Debian revision and tilde if necessary). Using apt as an example (debian/libapt-pkg5.0.symbols): (c++)"URI::operator std::__cxx11::basic_string, std::allocator >[abi:cxx11]()@APTPKG_5.0" 0.8.0 + (c++)"URI::operator std::__cxx11::basic_string, std::allocator >()@APTPKG_5.0" 1.5~beta2~ Where "1.5~beta2" is the version this bug was fixed in. - If your package does not provide a symbols file, add a dh_makeshlibs override so that tight enough dependencies are generated. Using libebml as an example (debian/rules): + override_dh_makeshlibs: + # For new symbols when compiled with GCC 7 + dh_makeshlibs -V'libebml4v5 (>= 1.3.4-2~)' Where "1.3.4-2" is the version this bug was fixed in. - If your package is about to be renamed due to an upstream SONAME bump, you do not need to add any special symbols handling. If you would like to know the exact name of the new symbols, using "abipkgdiff" from abigail-tools might be able to help. Thanks, James --- End Message --- --- Begin Message --- Version: 8.3.3-1 This issue was solved with the a prepared version 8.3.2-1 which never hitted the archive due a upload of a more recent version 8.3.3-1 which needed to go through in NEW. (Re-send because of misspelled closing address ...) On Mon, Aug 07, 2017 at 03:47:15PM +0100, jcowg...@debian.org wrote: > Package: kopano-libs > Version: 8.1.0-3 > Severity: serious > Tags: sid buster > User: debian-...@lists.debian.org > Usertags: gcc-7-op-mangling > > Hi, > > It appears that your package provides an external symbol that is > affected by the recent name mangling changes in GCC 7. See: > https://gcc.gnu.org/gcc-7/porting_to.html#conversion-op-mangling > > In GCC 7, the name mangling for C++ conversion operators which return a > type using the abi_tag attribute (most commonly std::string) has > changed. When your library is compiled with GCC 7, it will now emit two > symbols for the conversion operator using the new and old naming. > Executables compiled with GCC 7 will always use the new symbol, while > old executables compiled using <= GCC 6 will use the old symbol. For new > executables to build without undefined references, your library will > need rebuilding with GCC 7. > > To ensure that new executables will pull in the newer version of the > library built with GCC 7: > - Your library package should Build-Depend on g++ (>= 4:7). > - If your package provides a symbols file, ensure that the new > conversion operator symbols have a version matching the version this > bug is fixed in (including the Debian revision and tilde if > necessary). > > Using apt as an example (debian/libapt-pkg5.0.symbols): > (c++)"URI::operator std::__cxx11::basic_string std::char_traits, std::allocator >[abi:cxx11]()@APTPKG_5.0" 0.8.0 > + (c++)"URI::operator std::__cxx11::basic_string std::char_traits, std::allocator >()@APTPKG_5
Bug#865320: marked as done (kopanocore FTBFS: error: expected class-name before '{' token)
Your message dated Tue, 12 Sep 2017 21:32:05 +0200
with message-id <20170912193205.hy47vtf24vn7m...@i5.cruise.homelinux.net>
and subject line Re: Bug#865320: kopanocore FTBFS: error: expected class-name
before '{' token
has caused the Debian Bug report #865320,
regarding kopanocore FTBFS: error: expected class-name before '{' token
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.)
--
865320: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865320
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: kopanocore
Version: 8.1.0-3
Severity: serious
Some recent change in unstable causes kopanocore to FTBFS:
https://tests.reproducible-builds.org/debian/history/kopanocore.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/kopanocore.html
...
In file included from ../../../inetmapi/inputStreamMAPIAdapter.cpp:23:0:
../../../inetmapi/inputStreamMAPIAdapter.h:25:77: error: expected class-name
before '{' token
class inputStreamMAPIAdapter _kc_final : public vmime::utility::inputStream {
^
../../../inetmapi/inputStreamMAPIAdapter.h:30:10: error: 'size_type' does not
name a type
virtual size_type read(value_type* const data, const size_type count);
^
../../../inetmapi/inputStreamMAPIAdapter.h:31:10: error: 'size_type' does not
name a type
virtual size_type skip(const size_type count);
^
../../../inetmapi/inputStreamMAPIAdapter.cpp:39:25: error: 'size_type' in
'class vmime::utility::stream' does not name a type
vmime::utility::stream::size_type inputStreamMAPIAdapter::read(value_type*
data, const size_type count)
^
../../../inetmapi/inputStreamMAPIAdapter.cpp:62:25: error: 'size_type' in
'class vmime::utility::stream' does not name a type
vmime::utility::stream::size_type inputStreamMAPIAdapter::skip(const size_type
count)
^
In file included from ../../../inetmapi/outputStreamMAPIAdapter.cpp:23:0:
../../../inetmapi/outputStreamMAPIAdapter.h:24:69: error: expected class-name
before '{' token
class outputStreamMAPIAdapter : public vmime::utility::outputStream {
^
../../../inetmapi/outputStreamMAPIAdapter.h:28:19: error: 'value_type' does not
name a type
void write(const value_type* const data, const size_type count);
^~
../../../inetmapi/outputStreamMAPIAdapter.h:28:49: error: 'size_type' does not
name a type
void write(const value_type* const data, const size_type count);
^
../../../inetmapi/outputStreamMAPIAdapter.cpp:38:43: error: 'value_type' does
not name a type
void outputStreamMAPIAdapter::write(const value_type* const data, const
size_type count)
^~
../../../inetmapi/outputStreamMAPIAdapter.cpp:38:73: error: 'size_type' does
not name a type
void outputStreamMAPIAdapter::write(const value_type* const data, const
size_type count)
^
Makefile:648: recipe for target 'outputStreamMAPIAdapter.lo' failed
make[4]: *** [outputStreamMAPIAdapter.lo] Error 1
--- End Message ---
--- Begin Message ---
Version: 8.3.3-1
This issue was solved with the a prepared version 8.3.2-1 which never
hitted the archive due a upload of a more recent version 8.3.3-1 which
needed to go through in NEW.
On Tue, Jun 20, 2017 at 04:55:10PM +0300, Adrian Bunk wrote:
> Source: kopanocore
> Version: 8.1.0-3
> Severity: serious
>
> Some recent change in unstable causes kopanocore to FTBFS:
>
> https://tests.reproducible-builds.org/debian/history/kopanocore.html
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/kopanocore.html
>
> ...
> In file included from ../../../inetmapi/inputStreamMAPIAdapter.cpp:23:0:
> ../../../inetmapi/inputStreamMAPIAdapter.h:25:77: error: expected class-name
> before '{' token
> class inputStreamMAPIAdapter _kc_final : public vmime::utility::inputStream {
> ^
> ../../../inetmapi/inputStreamMAPIAdapter.h:30:10: error: 'size_type' does not
> name a type
> virtual size_type read(value_type* const data, const size_type count);
> ^
> ../../../inetmapi/inputStreamMAPIAdapter.h:31:10: error: 'size_type' does not
> name a type
> virtual size_type skip(const size_type count);
>
Bug#861775: marked as done (kopanocore: src:kopanocore has a harcoded php7.0-mapi binary)
Your message dated Tue, 12 Sep 2017 21:29:34 +0200 with message-id <20170912192934.65dzmg7z3qbpv...@i5.cruise.homelinux.net> and subject line Re: Bug#861775: kopanocore: src:kopanocore has a harcoded php7.0-mapi binary has caused the Debian Bug report #861775, regarding kopanocore: src:kopanocore has a harcoded php7.0-mapi binary 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.) -- 861775: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861775 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: kopanocore Severity: normal Dear Maintainer, It would appear kopanocore doesn't follow many other PHP packages and explicitly names it's binary package php7.0-mapi rather than php-mapi. This requires renaming the binary package and explicitly adding transitional changes for upgraders as the PHP version changes (while not applicable currently since only in unstable, this might become true in the future). Can kopanocore be modified to be like other PHP packages and generate php-mapi, as well as dropping it's versioned dependencies? Ubuntu 17.10 intends to ship with PHP7.1 and I believe Debian will be going through this transition as well. -- Nishanth Aravamudan Ubuntu Server Canonical Ltd --- End Message --- --- Begin Message --- Version: 8.3.3-1 This issue was solved with the a prepared version 8.3.2-1 which never hitted the archive due a upload of a more recent version 8.3.3-1 which needed to go through in NEW. On Wed, May 03, 2017 at 03:06:31PM -0700, Nishanth Aravamudan wrote: > Package: kopanocore > Severity: normal > > Dear Maintainer, > > It would appear kopanocore doesn't follow many other PHP packages and > explicitly names it's binary package php7.0-mapi rather than > php-mapi. This requires renaming the binary package and explicitly > adding transitional changes for upgraders as the PHP version changes > (while not applicable currently since only in unstable, this might > become true in the future). > > Can kopanocore be modified to be like other PHP packages and generate > php-mapi, as well as dropping it's versioned dependencies? > > Ubuntu 17.10 intends to ship with PHP7.1 and I believe Debian will be > going through this transition as well. > > -- > Nishanth Aravamudan > Ubuntu Server > Canonical Ltd--- End Message ---
Bug#863958: marked as done (kopano-server: postrm script still refers to zarafa-server)
Your message dated Tue, 12 Sep 2017 21:30:31 +0200 with message-id <20170912193031.qjrtkuqfu7ml7...@i5.cruise.homelinux.net> and subject line Re: Bug#863958: kopano-server: postrm script still refers to zarafa-server has caused the Debian Bug report #863958, regarding kopano-server: postrm script still refers to zarafa-server 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.) -- 863958: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863958 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: kopano-server Version: 8.1.0-3 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package left unowned files on the system after purge, which is a violation of policy 6.8 (or 10.8): https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-removedetails Enabling dbconfig purge did not work for this package, looking at the postinst revealed that it partially tries to work on zarafa-server: $ grep -- -server /var/lib/dpkg/info/kopano-server.postrm # postrm script for zarafa-server dbc_go zarafa-server $@ update-rc.d kopano-server remove >/dev/null I didn't check any other maintainer script. cheers, Andreas --- End Message --- --- Begin Message --- Version: 8.3.3-1 This issue was solved with the a prepared version 8.3.2-1 which never hitted the archive due a upload of a more recent version 8.3.3-1 which needed to go through in NEW. On Fri, Jun 02, 2017 at 12:31:33PM +0200, Andreas Beckmann wrote: > Package: kopano-server > Version: 8.1.0-3 > Severity: serious > User: debian...@lists.debian.org > Usertags: piuparts > > Hi, > > during a test with piuparts I noticed your package left unowned files on > the system after purge, which is a violation of policy 6.8 (or 10.8): > https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-removedetails > > Enabling dbconfig purge did not work for this package, looking at the > postinst revealed that it partially tries to work on zarafa-server: > > $ grep -- -server /var/lib/dpkg/info/kopano-server.postrm > # postrm script for zarafa-server > dbc_go zarafa-server $@ > update-rc.d kopano-server remove >/dev/null > > I didn't check any other maintainer script. > > > cheers, > > Andreas--- End Message ---
Bug#857377: marked as done (kopano-dev: fails to upgrade from 'jessie' - trying to overwrite /usr/lib/x86_64-linux-gnu/libmapi.so)
Your message dated Tue, 12 Sep 2017 21:28:16 +0200 with message-id <20170912192816.gff4ncflj7pge...@i5.cruise.homelinux.net> and subject line Re: Bug#857377: kopano-dev: fails to upgrade from 'jessie' - trying to overwrite /usr/lib/x86_64-linux-gnu/libmapi.so has caused the Debian Bug report #857377, regarding kopano-dev: fails to upgrade from 'jessie' - trying to overwrite /usr/lib/x86_64-linux-gnu/libmapi.so 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.) -- 857377: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857377 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: kopano-dev Version: 8.1.0-3 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'jessie'. It installed fine in 'jessie', 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 kopano-dev. Preparing to unpack .../kopano-dev_8.1.0-3_amd64.deb ... Unpacking kopano-dev (8.1.0-3) ... dpkg: error processing archive /var/cache/apt/archives/kopano-dev_8.1.0-3_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/libmapi.so', which is also in package libmapi-dev 1:2.2-5+b1 Errors were encountered while processing: /var/cache/apt/archives/kopano-dev_8.1.0-3_amd64.deb cheers, Andreas libmapi-dev=1%2.2-5+b1_kopano-dev=8.1.0-3.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Version: 8.3.3-1 This issue was solved with the a prepared version 8.3.2-1 which never hitted the archive due a upload of a more recent version 8.3.3-1 which needed to go through in NEW. On Fri, Mar 10, 2017 at 05:52:48PM +0100, Andreas Beckmann wrote: > Package: kopano-dev > Version: 8.1.0-3 > Severity: serious > User: debian...@lists.debian.org > Usertags: piuparts > > Hi, > > during a test with piuparts I noticed your package fails to upgrade from > 'jessie'. > It installed fine in 'jessie', 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 kopano-dev. > Preparing to unpack .../kopano-dev_8.1.0-3_amd64.deb ... > Unpacking kopano-dev (8.1.0-3) ... > dpkg: error processing archive > /var/cache/apt/archives/kopano-dev_8.1.0-3_amd64.deb (--unpack): >trying to overwrite '/usr/lib/x86_64-linux-gnu/libmapi.so', which is also > in package libmapi-dev 1:2.2-5+b1 > Errors were encountered while processing: >/var/cache/apt/archives/kopano-dev_8.1.0-3_amd64.deb > > > cheers, > > Andreas--- End Message ---
Bug#872977: marked as done (libblockdev FTBFS on s390x: fatal error: s390utils/vtoc.h: No such file or directory)
Your message dated Tue, 12 Sep 2017 18:04:14 + with message-id and subject line Bug#872977: fixed in libblockdev 2.12-3 has caused the Debian Bug report #872977, regarding libblockdev FTBFS on s390x: fatal error: s390utils/vtoc.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.) -- 872977: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872977 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libblockdev Version: 2.6-1 Severity: important https://buildd.debian.org/status/fetch.php?pkg=libblockdev&arch=s390x&ver=2.6-1&stamp=1503438672&raw=0 ... In file included from blockdev.c:30:0: plugin_apis/s390.h:7:10: fatal error: s390utils/vtoc.h: No such file or directory #include ^~ compilation terminated. Makefile:604: recipe for target 'libblockdev_la-blockdev.lo' failed make[4]: *** [libblockdev_la-blockdev.lo] Error 1 --- End Message --- --- Begin Message --- Source: libblockdev Source-Version: 2.12-3 We believe that the bug you reported is fixed in the latest version of libblockdev, 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 872...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Michael Biebl (supplier of updated libblockdev 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, 12 Sep 2017 19:38:49 +0200 Source: libblockdev Binary: libblockdev2 libblockdev-dev gir1.2-blockdev-2.0 python-blockdev python3-blockdev libblockdev-utils2 libblockdev-utils-dev libblockdev-part-err2 libblockdev-part-err-dev libblockdev-btrfs2 libblockdev-btrfs-dev libblockdev-crypto2 libblockdev-crypto-dev libblockdev-dm2 libblockdev-dm-dev libblockdev-fs2 libblockdev-fs-dev libblockdev-kbd2 libblockdev-kbd-dev libblockdev-loop2 libblockdev-loop-dev libblockdev-lvm2 libblockdev-lvm-dev libblockdev-lvm-dbus2 libblockdev-lvm-dbus-dev libblockdev-mdraid2 libblockdev-mdraid-dev libblockdev-mpath2 libblockdev-mpath-dev libblockdev-part2 libblockdev-part-dev libblockdev-swap2 libblockdev-swap-dev libblockdev-plugins-all Architecture: source Version: 2.12-3 Distribution: unstable Urgency: medium Maintainer: Utopia Maintenance Team Changed-By: Michael Biebl Description: gir1.2-blockdev-2.0 - libblockdev introspection data libblockdev-btrfs-dev - BTRFS plugin for libblockdev - development libblockdev-btrfs2 - BTRFS plugin for libblockdev libblockdev-crypto-dev - Crypto plugin for libblockdev - development libblockdev-crypto2 - Crypto plugin for libblockdev libblockdev-dev - Library for manipulating block devices - development libblockdev-dm-dev - Device Mapper plugin for libblockdev - development libblockdev-dm2 - Device Mapper plugin for libblockdev libblockdev-fs-dev - file system plugin for libblockdev - development libblockdev-fs2 - file system plugin for libblockdev libblockdev-kbd-dev - kernel block device plugin for libblockdev - development libblockdev-kbd2 - kernel block device plugin for libblockdev libblockdev-loop-dev - Loop device plugin for libblockdev - development libblockdev-loop2 - Loop device plugin for libblockdev libblockdev-lvm-dbus-dev - LVM DBus plugin for libblockdev - development libblockdev-lvm-dbus2 - LVM DBus plugin for libblockdev libblockdev-lvm-dev - LVM plugin for libblockdev - development libblockdev-lvm2 - LVM plugin for libblockdev libblockdev-mdraid-dev - MD RAID plugin for libblockdev - development libblockdev-mdraid2 - MD RAID plugin for libblockdev libblockdev-mpath-dev - Multipath plugin for libblockdev - development libblockdev-mpath2 - Multipath plugin for libblockdev libblockdev-part-dev - Partitioning plugin for libblockdev - development libblockdev-part-err-dev - Partition error utility functions for libblockdev - development libblockdev-part-err2 - Partition error utility functions for libblockdev libblockdev-part2 - Partitioning plugin for libblockdev libblockdev-plugins-all - All plugins for libblockdev libblockdev-swap-dev - Swap plugin for libblockdev - development libblockdev-swap2 - Swap plugin for libblockdev libblockdev-utils-dev - Utility functions for libblockd
Bug#852923: dojo package build errors: FTBFS: OPTIMIZER FAILED
What is the status of resolving the issues with the dojo package failing to build from source? I tried a test build of 1.11.0 in stretch as well as in a current sid chroot (using debhelper 9) and the same errors come up. The bug is tagged as 'fixed-stream' and I was going to try a test build of 1.12.2 (which I had to download manually because the current d/watch doesn't appear to work) but that archive appears to be missing (at least) the utils directory. I have a package that depends on dojo so I am very interesting in what is happening with it. -- Robert J. Clay rjc...@gmail.com
Bug#875617: pan: Crashes when launching
Package: pan Version: 0.141-2 Severity: grave Justification: renders package unusable -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Also applies to 0.142-1 in unstable. (gdb) run --debug Starting program: /usr/bin/pan --debug [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [New Thread 0x7fffeaabe700 (LWP 24969)] [New Thread 0x7fffea2bd700 (LWP 24970)] (article-cache.cc:171:ArticleCache) loaded 940 articles into cache from /home/sam/.pan2/article-cache [New Thread 0x7fffe3fff700 (LWP 24971)] [New Thread 0x7fffe37fe700 (LWP 24972)] [New Thread 0x7fffe2ffd700 (LWP 24973)] [New Thread 0x7fffe27fc700 (LWP 24974)] (queue.cc:292:process_task) in process_task with a task of type SAVE (task-article.cc:355:use_decoder) decoder thread was free, enqueued work (queue.cc:292:process_task) in process_task with a task of type SAVE [New Thread 0x7fffe1ffb700 (LWP 24975)] *** Error in `/usr/bin/pan': corrupted size vs. prev_size: 0x7fffd8004810 *** GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name news.pan.NZB was not provided by any .service files === Backtrace: = /lib/x86_64-linux-gnu/libc.so.6(+0x70bcb)[0x73506bcb] /lib/x86_64-linux-gnu/libc.so.6(+0x76f96)[0x7350cf96] /lib/x86_64-linux-gnu/libc.so.6(+0x78091)[0x7350e091] /usr/bin/pan(+0x15d334)[0x556b1334] /usr/bin/pan(+0x129a14)[0x5567da14] /usr/bin/pan(+0x15a3ba)[0x556ae3ba] /lib/x86_64-linux-gnu/libglib-2.0.so.0(+0x72dce)[0x75978dce] /lib/x86_64-linux-gnu/libglib-2.0.so.0(+0x723d5)[0x759783d5] /lib/x86_64-linux-gnu/libpthread.so.0(+0x7494)[0x73280494] /lib/x86_64-linux-gnu/libc.so.6(clone+0x3f)[0x7357eaff] === Memory map: 4000-55784000 r-xp 08:02 786882 /usr/bin/pan 55984000-5598d000 r--p 0023 08:02 786882 /usr/bin/pan 5598d000-5599 rw-p 00239000 08:02 786882 /usr/bin/pan 5599-5610 rw-p 00:00 0 [heap] 7fffd000-7fffd0021000 rw-p 00:00 0 7fffd0021000-7fffd400 ---p 00:00 0 7fffd800-7fffd8022000 rw-p 00:00 0 7fffd8022000-7fffdc00 ---p 00:00 0 7fffdc00-7fffdc022000 rw-p 00:00 0 7fffdc022000-7fffe000 ---p 00:00 0 7fffe17fb000-7fffe17fc000 ---p 00:00 0 7fffe17fc000-7fffe1ffc000 rw-p 00:00 0 7fffe1ffc000-7fffe1ffd000 ---p 00:00 0 7fffe1ffd000-7fffe27fd000 rw-p 00:00 0 7fffe27fd000-7fffe27fe000 ---p 00:00 0 7fffe27fe000-7fffe2ffe000 rw-p 00:00 0 7fffe2ffe000-7fffe2fff000 ---p 00:00 0 7fffe2fff000-7fffe37ff000 rw-p 00:00 0 7fffe37ff000-7fffe380 ---p 00:00 0 7fffe380-7fffe400 rw-p 00:00 0 7fffe400-7fffe4021000 rw-p 00:00 0 7fffe4021000-7fffe800 ---p 00:00 0 7fffe841c000-7fffe8426000 r-xp 08:02 924364 /lib/x86_64-linux-gnu/libnss_files-2.24.so 7fffe8426000-7fffe8626000 ---p a000 08:02 924364 /lib/x86_64-linux-gnu/libnss_files-2.24.so 7fffe8626000-7fffe8627000 r--p a000 08:02 924364 /lib/x86_64-linux-gnu/libnss_files-2.24.so 7fffe8627000-7fffe8628000 rw-p b000 08:02 924364 /lib/x86_64-linux-gnu/libnss_files-2.24.so 7fffe8628000-7fffe862e000 rw-p 00:00 0 7fffe862e000-7fffe8639000 r-xp 08:02 924372 /lib/x86_64-linux-gnu/libnss_nis-2.24.so 7fffe8639000-7fffe8838000 ---p b000 08:02 924372 /lib/x86_64-linux-gnu/libnss_nis-2.24.so 7fffe8838000-7fffe8839000 r--p a000 08:02 924372 /lib/x86_64-linux-gnu/libnss_nis-2.24.so 7fffe8839000-7fffe883a000 rw-p b000 08:02 924372 /lib/x86_64-linux-gnu/libnss_nis-2.24.so 7fffe883a000-7fffe8841000 r-xp 08:02 924358 /lib/x86_64-linux-gnu/libnss_compat-2.24.so 7fffe8841000-7fffe8a4 ---p 7000 08:02 924358 /lib/x86_64-linux-gnu/libnss_compat-2.24.so 7fffe8a4-7fffe8a41000 r--p 6000 08:02 924358 /lib/x86_64-linux-gnu/libnss_compat-2.24.so 7fffe8a41000-7fffe8a42000 rw-p 7000 08:02 924358 /lib/x86_64-linux-gnu/libnss_compat-2.24.so 7fffe8a42000-7fffe8a49000 r-xp 08:02 802561 /usr/lib/x86_64-linux-gnu/libogg.so.0.8.2 7fffe8a49000-7fffe8c49000 ---p 7000 08:02 802561 /usr/lib/x86_64-linux-gnu/libogg.so.0.8.2 7fffe8c49000-7fffe8c4a000 r--p 7000 08:02 802561 /usr/lib/x86_64-linux-gnu/libogg.so.0.8.2 7fffe8c4a000-7fffe8c4b000 rw-p 8000 08:02 802561 /usr/lib/x86_64-linux-gnu/libogg.so.0.8.2 7fffe8c4b000-7fffe8c76000 r-xp 08:02 790743 /usr/lib/x86_64-linux-gnu/libvorbis.so
Bug#875596: marked as done (perl: CVE-2017-12837: Heap buffer overflow in regular expression compiler)
Your message dated Tue, 12 Sep 2017 16:36:45 + with message-id and subject line Bug#875596: fixed in perl 5.26.0-8 has caused the Debian Bug report #875596, regarding perl: CVE-2017-12837: Heap buffer overflow in regular expression compiler 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.) -- 875596: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875596 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: perl Version: 5.20.2-1 Severity: grave Tags: security upstream patch Forwarded: https://rt.perl.org/Public/Bug/Display.html?id=131582 Hi, the following vulnerability was published for perl. CVE-2017-12837[0]: Heap buffer overflow in regular expression compiler >From release notes: Compiling certain regular expression patterns with the case-insensitive modifier could cause a heap buffer overflow and crash perl. This has now been fixed. If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2017-12837 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-12837 [1] https://rt.perl.org/Public/Bug/Display.html?id=131582 (not yet public) Regards, Salvatore --- End Message --- --- Begin Message --- Source: perl Source-Version: 5.26.0-8 We believe that the bug you reported is fixed in the latest version of perl, 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 875...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Niko Tyni (supplier of updated perl 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, 12 Sep 2017 18:07:07 +0300 Source: perl Binary: perl-base perl-doc perl-debug libperl5.26 libperl-dev perl-modules-5.26 perl Architecture: source Version: 5.26.0-8 Distribution: unstable Urgency: high Maintainer: Niko Tyni Changed-By: Niko Tyni Description: libperl-dev - Perl library: development files libperl5.26 - shared Perl library perl - Larry Wall's Practical Extraction and Report Language perl-base - minimal Perl system perl-debug - debug-enabled Perl interpreter perl-doc - Perl documentation perl-modules-5.26 - Core Perl modules Closes: 875596 875597 Changes: perl (5.26.0-8) unstable; urgency=high . * [SECURITY] CVE-2017-12837: Fix a heap buffer overflow in regular expression compiler. (Closes: #875596) * [SECURITY] CVE-2017-12883: Fix a buffer over-read in regular expression parser. (Closes: #875597) Checksums-Sha1: f95120a308ccd796d99a8548f9c64b212ec550e4 2369 perl_5.26.0-8.dsc f9176e4620608ba402d3d3f2ae716465a38820f9 159896 perl_5.26.0-8.debian.tar.xz 8177ea4c20d16448b2e5c1261c40c2c61c3850a8 4611 perl_5.26.0-8_source.buildinfo Checksums-Sha256: 14287efb9981734a2e15c3508b91e1fd3ca1342e9fc6f49c37ed00acd757aece 2369 perl_5.26.0-8.dsc e6c7f4b6a5790f5909c007d3efe4dcb1f6c6b41da95e4f7ea74748bfb7e198d1 159896 perl_5.26.0-8.debian.tar.xz 16da5c6077c6eb2fa35862528419867c044a56774bf7a4f04a2ed98ea7cf62c2 4611 perl_5.26.0-8_source.buildinfo Files: 0ff475c5f4cd3296fb403e4055fff538 2369 perl standard perl_5.26.0-8.dsc e91e79592df67bd0889ba186b7ad744a 159896 perl standard perl_5.26.0-8.debian.tar.xz c97b94dceba8c050a9e3651b2f773b45 4611 perl standard perl_5.26.0-8_source.buildinfo -BEGIN PGP SIGNATURE- iQJFBAEBCAAvFiEEdqKOQsmBHZHoj7peLsD/s7cwGx8FAlm3+LsRHG50eW5pQGRl Ymlhbi5vcmcACgkQLsD/s7cwGx8gMg/+Lsw2jknW2dCMddrJgLDZSxwah0FdGbaY l9OpXv3lnb7TMJhHKMfysXv1bxSxyYGDKmJ3pAqDzBTmjhQsVlxnBQHeITSQda25 eA+ghNpPHwlyY6J+u6bNSYUlVuMHEHYhXwdJGGaOwxhqOxe8uRPsp0geyybL2Bz3 Xuk+kW0ueuPFHxjOfmketGpv0q+iIna6tWBovKNLTdS4XZXtsAP/t8k+ol4jlyJk 1qd+ISKQcPNmsI40uFwz5gbVWNnakwCDS2yKERGlk2/l7pbUkS12THLGEyXgXhll JUuGDuURSqlb8F9BrpLg9rv1bcGN7DrcYsMD0eO3b7B3AndcoVU0PjobZL4p/0Yw g2AcPnx3JneG7zQrLWmm2S/AeOyCnhKykW0L1bpEupmBz57ZmlliDdOa7Ojpbbbv e0Grz9w65IbNBmbIFWYKGIhJF/ostQIBDC8on2aOGMpXswE8Jzbqjs7/2OsI7CCN 1fL9miC+u5ltAOBUhZRF18kAoTPbbleob5AlQ7kW1YEh/1yLxGaoPUI5O+OBN8A8 jZshFHno41iyH8M1gBre4uvfdiavjjF5I9h0LyvKfV4gfpSzdwhBj2gAY1bcK941 ptzeow6z70fu4Z2cMizWBOANWvj8UDrRayE4034Br7IwGCTqq2aRo55YrmBh
Bug#875597: marked as done (perl: CVE-2017-12883: Buffer over-read in regular expression parser)
Your message dated Tue, 12 Sep 2017 16:36:45 + with message-id and subject line Bug#875597: fixed in perl 5.26.0-8 has caused the Debian Bug report #875597, regarding perl: CVE-2017-12883: Buffer over-read in regular expression parser 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.) -- 875597: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875597 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: perl Version: 5.20.2-1 Severity: grave Tags: security patch upstream Forwarded: https://rt.perl.org/Public/Bug/Display.html?id=131598 *** /tmp/perl.reportbug Package: perl X-Debbugs-CC: t...@security.debian.org secure-testing-t...@lists.alioth.debian.org Severity: grave Tags: security Hi, the following vulnerability was published for perl. CVE-2017-12883[0]: Buffer over-read in regular expression parser >From release notes: For certain types of syntax error in a regular expression pattern, the error message could either contain the contents of a random, possibly large, chunk of memory, or could crash perl. This has now been fixed. If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2017-12883 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-12883 [1] https://rt.perl.org/Public/Bug/Display.html?id=131598 (not yet public) Regards, Salvatore --- End Message --- --- Begin Message --- Source: perl Source-Version: 5.26.0-8 We believe that the bug you reported is fixed in the latest version of perl, 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 875...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Niko Tyni (supplier of updated perl 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, 12 Sep 2017 18:07:07 +0300 Source: perl Binary: perl-base perl-doc perl-debug libperl5.26 libperl-dev perl-modules-5.26 perl Architecture: source Version: 5.26.0-8 Distribution: unstable Urgency: high Maintainer: Niko Tyni Changed-By: Niko Tyni Description: libperl-dev - Perl library: development files libperl5.26 - shared Perl library perl - Larry Wall's Practical Extraction and Report Language perl-base - minimal Perl system perl-debug - debug-enabled Perl interpreter perl-doc - Perl documentation perl-modules-5.26 - Core Perl modules Closes: 875596 875597 Changes: perl (5.26.0-8) unstable; urgency=high . * [SECURITY] CVE-2017-12837: Fix a heap buffer overflow in regular expression compiler. (Closes: #875596) * [SECURITY] CVE-2017-12883: Fix a buffer over-read in regular expression parser. (Closes: #875597) Checksums-Sha1: f95120a308ccd796d99a8548f9c64b212ec550e4 2369 perl_5.26.0-8.dsc f9176e4620608ba402d3d3f2ae716465a38820f9 159896 perl_5.26.0-8.debian.tar.xz 8177ea4c20d16448b2e5c1261c40c2c61c3850a8 4611 perl_5.26.0-8_source.buildinfo Checksums-Sha256: 14287efb9981734a2e15c3508b91e1fd3ca1342e9fc6f49c37ed00acd757aece 2369 perl_5.26.0-8.dsc e6c7f4b6a5790f5909c007d3efe4dcb1f6c6b41da95e4f7ea74748bfb7e198d1 159896 perl_5.26.0-8.debian.tar.xz 16da5c6077c6eb2fa35862528419867c044a56774bf7a4f04a2ed98ea7cf62c2 4611 perl_5.26.0-8_source.buildinfo Files: 0ff475c5f4cd3296fb403e4055fff538 2369 perl standard perl_5.26.0-8.dsc e91e79592df67bd0889ba186b7ad744a 159896 perl standard perl_5.26.0-8.debian.tar.xz c97b94dceba8c050a9e3651b2f773b45 4611 perl standard perl_5.26.0-8_source.buildinfo -BEGIN PGP SIGNATURE- iQJFBAEBCAAvFiEEdqKOQsmBHZHoj7peLsD/s7cwGx8FAlm3+LsRHG50eW5pQGRl Ymlhbi5vcmcACgkQLsD/s7cwGx8gMg/+Lsw2jknW2dCMddrJgLDZSxwah0FdGbaY l9OpXv3lnb7TMJhHKMfysXv1bxSxyYGDKmJ3pAqDzBTmjhQsVlxnBQHeITSQda25 eA+ghNpPHwlyY6J+u6bNSYUlVuMHEHYhXwdJGGaOwxhqOxe8uRPsp0geyybL2Bz3 Xuk+kW0ueuPFHxjOfmketGpv0q+iIna6tWBovKNLTdS4XZXtsAP/t8k+ol4jlyJk 1qd+ISKQcPNmsI40uFwz5gbVWNnakwCDS2yKERGlk2/l7pbUkS12THLGEyXgXhll JUuGDuURSqlb8F9BrpLg9rv1bcGN7DrcYsMD0eO3b7B3AndcoVU0PjobZL4p/0Yw g2AcPnx3JneG7zQrLWmm2S/AeOyCnhKykW0L1bpEupmBz57ZmlliDdOa7Ojpbbbv e0Grz9w65IbNBmbIFWYKGIhJF/ostQIBDC8on2aOGMpXswE8Jzbqjs7/2Os
Bug#875612: ruby-compass-rails: ruby-compass obsolete and now broken
Quoting Jonas Smedegaard (2017-09-12 18:11:06) > It seems ruby-compass-rails really do work only with ruby-compass. But > also, it looks like it is a leaf package: Would it be ok to simply > drop ruby-compass-rails from Debian? Oh, I looked only at *build* dependencies - I see now it is needed by Diaspora :-/ I will try dive in and see if I can help come up with a patch to use ruby-sass or sassc instead. - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private
Bug#875612: ruby-compass-rails: ruby-compass obsolete and now broken
Package: ruby-compass-rails Severity: serious -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hi, ruby-compass is obsolete and will likely not be released with Buster. I intended to warn about this, but accidentally uploaded a too new ruby-sass yesterday, so that ruby-compass is no longer installable :-( It seems ruby-compass-rails really do work only with ruby-compass. But also, it looks like it is a leaf package: Would it be ok to simply drop ruby-compass-rails from Debian? Kind regards, and sorry for the lack of warning, - Jonas -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAlm4BxoACgkQLHwxRsGg ASFdCw/9GqOLXBfs4twN4xSDfqExYUv01LnrT05WJdmARcaURqJhwtmOD24spDjP Lx0i2KUZKhq3l29Z9bt6aEE+NQMvdwTwjoffTymusvV2eR5Wfu4NUCs4a5FBF5ap f2u2eaBklvQbh6iPnNc1faLiLKAXS3BhJuAP8gXGQ+n8rtybMZdjYXfiNgoHVKby 9BWZBEHDes1eiHFe78hqQRccwFOubF331fGfMwCnI9Dgw0hkAMIsd9kyIggmG2UE ugAZqz5vgnevIjqOeBzf30+1yByZhI6n/M2FVza0BKwaI30jbqm4wJSNUCCUiySS 2QfSUplyLxjX59/5H711L6km1CQANf0B+SaI9xXSSBWzss16apxdF/bLFZb2f0IX NbDhWCjKWVoYtUjAdmPJCPllvDSXYIxXPUiLp6Y3IS2riCsBapY8jCb9BL2A9JG/ DkR9ueztYs4415oduwHMAF5DNqoIwJ0ugmg5L5ESuohNrtC41HZ5HbDpZbmRpszB MKaCsuTWzmQtzKCdPQJdpvx7dweY5TiS8EMY5Nms8hLsULSIYlGgd5trm6P4MX2Q hrJNRJ2Dek8K/BLXWl4hIkgxZCv7+/z2izZQVircBkCMLfLeV7HZVapvoioH116q lZw5ovEToxYsuYQCFWMaqLWEvY4xThn53T5FzbNE2mvnLN8CO9M= =E4c8 -END PGP SIGNATURE-
Bug#875611: sagenb: ruby-compass obsolete and now broken
Source: sagenb Severity: serious Tags: patch -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 I made a mistake today that cause FTBFS of sagenb, but I would prefer to fix it in sagenb as that would be needed anyway at a later point: ruby-compass is obsolete and will likely not be released with Buster. Its replacement is Sass - with the stylesheets previously shipped with Compass packaged separately. Yesterday I accidentally released to unstable (not experimental as intended) ruby-sass too new for ruby-compass. I can fix that by re-uploading older ruby-sass with a fake newer version number, but since only 5 packages (build-)depend on ruby-compass I would much prefer to instead speedup the removal of ruby-compass. Attached is a patch to make Sagenb use sassc with separately maintained stylesheets. It needs to wait until the stylesheets have been approved, though: Is in NEW queue now: https://ftp-master.debian.org/new/sass-stylesheets-compass_0.12.10-1.html Please consider doing above fix, and accept my apology for rushing things. Alternatively I can make an NMU. Or if neither is acceptable I will do the more substantial work of postponing this change by reverting ruby-sass to the older version for now. - Jonas -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAlm4BaUACgkQLHwxRsGg ASEQ4xAAqmIW2Fboc+6qvoCr63DNFWZqw+R6tI1eZZTM1Z6hSLvMOLblgtIj2aw1 q/isXv1nL9QsiixqaXzkxMAAYyJQaxdR5RLrOCNDkVcSppuCLQG+yY5Ng0g09bTE l1lI/sFKgo4SR4ZfmDTv+dzUW3kpjd8pog4Bf6WmW55wUE2RMitPUYqkt1JL4BIE 1O2rqqKvX7bK8LTlGD3ONAobzNjPny9KWcR/XpNYP/NvwPE2l8SkdGJE6mzBPgM4 WSjlfPPRM/fDqhj8rrKT1WVqKeMzKS8z5PdBoG/AlIFkRTE4x9SvnABzn+45NoBB YgpQAosnf4iqtroQge8tbGrKB1UCi44mhxMUsvRFW2hgYtp5AiAEfop2393Domog GJSIa6Wfzl0FKKGcnKpVTSdewAOiyXhUY6eREQztmXKtlRBa7nqGsjMGaZjljW1z he48vLzzXLUk9kN7Ulr0dDSdiX+07rRd2ZIpUo1tiNfxVE2PdbmcbMrBNzLUgIpO 40pW361v0Npy+B2gmFGC6i1Yt1pzO68/ohkwi6em7HhYm8vGRhyXeTKrcznEMsJh 45lQ1DqDSOgKcR7uM+TUbXS0ehoabQqXgd6Symb/5EyXUCIEej4VAc3i/q/bP0U4 zimR0o8Xu44ystf4+CzhgWXe2Om7UmBtdAmMic4jz4Oudc46KiM= =s1P5 -END PGP SIGNATURE- diff --git a/debian/control b/debian/control index 41c00750..4956345c 100644 --- a/debian/control +++ b/debian/control @@ -13,7 +13,8 @@ Build-Depends: debhelper (>= 10), python-flask, python-babel, python-flask-oldsessions, - ruby-compass, + sassc, + sass-stylesheets-compass, uglifyjs Standards-Version: 3.9.8 Homepage: https://github.com/sagemath/sagenb diff --git a/debian/rules b/debian/rules index 8c14d23a..691fd12a 100755 --- a/debian/rules +++ b/debian/rules @@ -24,7 +24,8 @@ override_dh_auto_build: $(MIN_JS) -lib /usr/share/java/j3dcore.jar \ -lib /usr/share/java/vecmath.jar \ -lib /usr/share/java/j3dutils.jar - cd sass && compass compile + sassc -I sass/src -I /usr/share/sass/stylesheets --style compact sass/src/main.scss sagenb/data/sage/css/main.css + sassc -I sass/src --style compact sass/src/test_report.scss sagenb/data/sage/css/test_report.css dh_auto_build # TODO: temporarily disabled for now; requires the "sage" binary @@ -33,7 +34,7 @@ override_dh_auto_test: override_dh_auto_clean: dh_auto_clean - cd sass && compass clean + rm -f sagenb/data/sage/css/main.css sagenb/data/sage/css/test_report.css rm -rf sagenb/data/sage3d/build sagenb/data/sage3d/lib rm -rf $(MIN_JS)
Bug#875610: python-pythonmagick: Undefined symbol in python2.7 PythonMagick.x86_64-linux-gnu.so
Package: python-pythonmagick Version: 0.9.17-1 Severity: grave Justification: renders package unusable Dear Maintainer, * What led up to the situation? apt-get upgrade using debian previously configured to use testing (buster) * What exactly did you do (or not do) that was effective (or ineffective)? Existing python program stopped working with the exception thrown: Traceback (most recent call last): File "./radar2.py", line 7, in import PythonMagick File "/usr/lib/python2.7/dist-packages/PythonMagick/__init__.py", line 1, in from . import _PythonMagick ImportError: /usr/lib/python2.7/dist-packages/PythonMagick/_PythonMagick.x86_64-linux-gnu.so: undefined symbol: _ZNK6Magick5ColorcvNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcv * What was the outcome of this action? Program that has been "in production" for several years now wont run * What outcome did you expect instead? Program continues to run normally Looks like a name mangling issue. Dave -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.11.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages python-pythonmagick depends on: ii libboost-python1.62.0 1.62.0+dfsg-4+b1 ii libc6 2.24-17 ii libgcc11:7.2.0-4 ii libgomp1 7.2.0-4 ii libmagick++-6.q16-78:6.9.7.4+dfsg-16 ii libmagickcore-6.q16-3 8:6.9.7.4+dfsg-16 ii libmagickwand-6.q16-3 8:6.9.7.4+dfsg-16 ii libstdc++6 7.2.0-4 ii python 2.7.13-2 python-pythonmagick recommends no packages. python-pythonmagick suggests no packages. -- no debconf information
Bug#864162: opendkim: systemd ExecStart ignore configuration options
It's fixed in testing and I'm working with the release team to get the fix in Stretch. Scott K On September 12, 2017 11:22:55 AM EDT, Emmanuel Revah wrote: >Hi, > >What is the correct solution for those who remain in Stretch/"stable" ? > >I've tried everything from this thread to try to fix >/lib/systemd/system/opendkim.service, I've even copied it over from the > >opendkim_2.11.0-alpha-11_arm64.deb file. Nothing works. > >Thanks for any possible help.
Processed: gnome-shell: Crashes in 3.25 in g_type_check_instance_cast() called by shell_gtk_embed_window_created_cb()
Processing control commands: > forwarded -1 https://bugzilla.gnome.org/show_bug.cgi?id=787361 Bug #875609 [gnome-shell] gnome-shell: Crashes in 3.25 in g_type_check_instance_cast() called by shell_gtk_embed_window_created_cb() Set Bug forwarded-to-address to 'https://bugzilla.gnome.org/show_bug.cgi?id=787361'. -- 875609: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875609 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#875609: gnome-shell: Crashes in 3.25 in g_type_check_instance_cast() called by shell_gtk_embed_window_created_cb()
Package: gnome-shell Version: 3.25.91-4 Severity: grave Tags: security Control: forwarded -1 https://bugzilla.gnome.org/show_bug.cgi?id=787361 gnome-shell crashes in g_type_check_instance_cast() called by shell_gtk_embed_window_created_cb(), this also happened today when the screen was locked, revealing all information on the screen. I'm thus filing this bug to block a later unfixed version in unstable from migrating to testing. -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (900, 'unstable'), (900, 'testing'), (500, 'unstable-debug'), (500, 'buildd-unstable'), (100, 'experimental'), (1, 'experimental-debug') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.12.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8), LANGUAGE=en_IE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages gnome-shell depends on: ii caribou 0.4.21-1+b1 ii dconf-gsettings-backend [gsettings-backend] 0.26.0-2+b1 ii evolution-data-server3.24.5-6 ii gir1.2-accountsservice-1.0 0.6.43-1 ii gir1.2-atspi-2.0 2.24.1-2 ii gir1.2-caribou-1.0 0.4.21-1+b1 ii gir1.2-freedesktop 1.53.2-4 ii gir1.2-gcr-3 3.20.0-5.1 ii gir1.2-gdesktopenums-3.0 3.24.0-2 ii gir1.2-gdm-1.0 3.25.90.1-2 ii gir1.2-geoclue-2.0 2.4.7-1 ii gir1.2-glib-2.0 1.53.2-4 ii gir1.2-gnomebluetooth-1.03.25.91-1 ii gir1.2-gnomedesktop-3.0 3.25.92-1 ii gir1.2-gtk-3.0 3.22.20-1 ii gir1.2-gweather-3.0 3.25.92-1 ii gir1.2-ibus-1.0 1.5.14-3 ii gir1.2-mutter-1 3.25.91+20170902~ce515c5-1.1 ii gir1.2-networkmanager-1.01.8.2-1 ii gir1.2-nmgtk-1.0 1.8.2-1 ii gir1.2-pango-1.0 1.40.12-1 ii gir1.2-polkit-1.00.105-18 ii gir1.2-rsvg-2.0 2.40.18-1 ii gir1.2-soup-2.4 2.59.90.1-1 ii gir1.2-upowerglib-1.00.99.5-3 ii gjs 1.49.92-1 ii gnome-backgrounds3.25.4-1 ii gnome-settings-daemon3.24.3-1 ii gnome-shell-common 3.25.91-4 ii gsettings-desktop-schemas3.24.0-2 ii libasound2 1.1.3-5 ii libatk-bridge2.0-0 2.24.1-1 ii libatk1.0-0 2.24.0-1 ii libc62.24-17 ii libcairo21.14.10-1 ii libcanberra-gtk3-0 0.30-3 ii libcanberra0 0.30-3 ii libcroco30.6.12-1 ii libdbus-glib-1-2 0.108-2 ii libecal-1.2-19 3.24.5-6 ii libedataserver-1.2-223.24.5-6 ii libgcr-base-3-1 3.20.0-5.1 ii libgdk-pixbuf2.0-0 2.36.5-4 ii libgirepository-1.0-11.53.2-4 ii libgjs0g [libgjs0-libmozjs-52-0] 1.49.92-1 ii libglib2.0-0 2.53.7-1 ii libglib2.0-bin 2.53.7-1 ii libgstreamer1.0-01.12.2-1 ii libgtk-3-0 3.22.20-1 ii libical2 2.0.0-0.5+b1 ii libjson-glib-1.0-0 1.2.8-1 ii libmutter-1-03.25.91+20170902~ce515c5-1.1 ii libnm-glib4 1.8.2-1 ii libnm-util2 1.8.2-1 ii libpango-1.0-0 1.40.12-1 ii libpangocairo-1.0-0 1.40.12-1 ii libpolkit-agent-1-0 0.105-18 ii libpolkit-gobject-1-00.105-18 ii libpulse-mainloop-glib0 11.0-1 ii libpulse011.0-1 ii libsecret-1-00.18.5-3.1 ii libstartup-notification0 0.12-4+b2 ii libsystemd0 234-3 ii libx11-6 2:1.6.4-3 ii libxfixes3 1:5.0.3-1 ii mutter 3.25.91+20170902~ce515c5-1.1 ii python3 3.5.3-3 Versions of packages gnome-shell r
Bug#870849: marked as done (ruby-kramdown-rfc2629 FTBFS with ruby-kramdown 1.14.0-1)
Your message dated Tue, 12 Sep 2017 15:30:52 + with message-id and subject line Bug#870849: fixed in ruby-kramdown-rfc2629 1.2.5-1 has caused the Debian Bug report #870849, regarding ruby-kramdown-rfc2629 FTBFS with ruby-kramdown 1.14.0-1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 870849: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=870849 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ruby-kramdown-rfc2629 Version: 1.0.36-1 Severity: serious Tags: buster sid https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/ruby-kramdown-rfc2629.html ... GEM_PATH=debian/ruby-kramdown-rfc2629/usr/share/rubygems-integration/all:/var/lib/gems/2.3.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.3.0:/usr/share/rubygems-integration/2.3.0:/usr/share/rubygems-integration/all ruby2.3 -e gem\ \"kramdown-rfc2629\" /usr/lib/ruby/2.3.0/rubygems/dependency.rb:319:in `to_specs': Could not find 'kramdown' (~> 1.12.0) - did find: [kramdown-1.14.0] (Gem::LoadError) ... --- End Message --- --- Begin Message --- Source: ruby-kramdown-rfc2629 Source-Version: 1.2.5-1 We believe that the bug you reported is fixed in the latest version of ruby-kramdown-rfc2629, 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 870...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Cédric Boutillier (supplier of updated ruby-kramdown-rfc2629 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, 12 Sep 2017 16:17:31 +0200 Source: ruby-kramdown-rfc2629 Binary: ruby-kramdown-rfc2629 Architecture: source Version: 1.2.5-1 Distribution: unstable Urgency: medium Maintainer: Debian Ruby Extras Maintainers Changed-By: Cédric Boutillier Description: ruby-kramdown-rfc2629 - generate XML2RFC XML from Markdown Closes: 870849 Changes: ruby-kramdown-rfc2629 (1.2.5-1) unstable; urgency=medium . * New upstream version 1.2.5 + works with ruby-kramdown >= 1.14 (Closes: #870849) * Add patch to disable the use of certified gem * Set minimal version of kramdown dependency to 1.14 * Bump Standards-Version to 4.1.0 (no changes needed) * Refresh fix-path.patch Checksums-Sha1: 18f2ccea3a46d3df0eedb47c7180819819d8370a 1838 ruby-kramdown-rfc2629_1.2.5-1.dsc c117419316c275ec59a269871beb6f3baa193a05 25467 ruby-kramdown-rfc2629_1.2.5.orig.tar.gz 014a7be46b12b79d38de7e1ce3d6463d955a2e3c 3872 ruby-kramdown-rfc2629_1.2.5-1.debian.tar.xz 22395a337f88cd158a3f5a68c805c1d794b02ced 6531 ruby-kramdown-rfc2629_1.2.5-1_source.buildinfo Checksums-Sha256: 424cd627258f973a8a93de2ce0a20a670fd6769fec5d6b6d45e5974551efeade 1838 ruby-kramdown-rfc2629_1.2.5-1.dsc 2de2ec681587db126e024b778e96828c1a264e9d98766aabddaa32d0b1528198 25467 ruby-kramdown-rfc2629_1.2.5.orig.tar.gz b4289434854b841d46dd2645a3f9d7ab77316c09dc7ec35c4ead11c47c5d310d 3872 ruby-kramdown-rfc2629_1.2.5-1.debian.tar.xz 7010a97b1c31c1b8626f22fc22a3ea496393a388cb3ddbff9a2950d6e42d1ed6 6531 ruby-kramdown-rfc2629_1.2.5-1_source.buildinfo Files: 2b306c6b0f8b89f5eb72e8387964813c 1838 ruby optional ruby-kramdown-rfc2629_1.2.5-1.dsc 57956a551eeabeb99c6197dd96bf6036 25467 ruby optional ruby-kramdown-rfc2629_1.2.5.orig.tar.gz d119c84c1bdda41281e9527f2fda8a64 3872 ruby optional ruby-kramdown-rfc2629_1.2.5-1.debian.tar.xz cf6c8772dbd30819e81e8d84bbdf9efb 6531 ruby optional ruby-kramdown-rfc2629_1.2.5-1_source.buildinfo -BEGIN PGP SIGNATURE- iQEzBAEBCgAdFiEEnM1rMZ2/jkCrGr0aia+CtznNIXoFAlm37xEACgkQia+CtznN IXqHhAf8CzxaLVRBBj0HwFRwW/ZZxFKSRcD672j+9lM+qICnhXgV2y/n3a5TY5uV yGHEnmYVoOtjfZS9CoFEt8949tL3e0j7n5GeJ9jsbHm9EQvxh7ru3+17tI1WVB81 attmeb8fyyB98uAuYPwdJH0VqV5kWEHFD7G8kknt7wwlaGEGHSuxmC1NTNpVqkeY Sx6OXu+3308uNnDaqj+XvoWvX7vhliDWSwSt4OMKjnGtCmpEjkc1kPZWeBaEjukg SoWGnrxE/Ban4x91O6r1vt1thR82n5yZ8xqRdk/7m+EQl8aTgZKrVXN7KHETTYmB t8ThQODSP4P1oV3kOVXlf+57kdvAqw== =qYML -END PGP SIGNATURE End Message ---
Bug#864162: opendkim: systemd ExecStart ignore configuration options
Hi, What is the correct solution for those who remain in Stretch/"stable" ? I've tried everything from this thread to try to fix /lib/systemd/system/opendkim.service, I've even copied it over from the opendkim_2.11.0-alpha-11_arm64.deb file. Nothing works. Thanks for any possible help. -- Emmanuel Revah
Bug#875510: marked as done (nanoc: ruby-compass obsolete and now broken)
Your message dated Tue, 12 Sep 2017 15:26:20 + with message-id and subject line Bug#875510: fixed in nanoc 4.8.5-1 has caused the Debian Bug report #875510, regarding nanoc: ruby-compass obsolete and now broken 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.) -- 875510: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875510 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: nanoc Severity: serious -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 I made a mistake today that cause FTBFS of nanoc, but I would prefer to fix it in nanoc as that would be needed anyway at a later point: ruby-compass is obsolete and will likely not be released with Buster. Its replacement is Sass - as already embraced in nanoc, it seems. Today I accidentally released to unstable (not experimental as intended) ruby-sass too new for ruby-compass. I can fix that by re-uploading older ruby-sass with a fake newer version number, but since only 5 packages (build-)depend on ruby-compass I would much prefer to instead speedup the removal of ruby-compass. Nanoc support for Compass is optional, apparently, so the fix seems to simply remove build-dependency and (runtime) dependency on ruby-compass. Please consider doing above fix, and accept my apology for rushing things. Alternatively I can make an NMU. Or if neither is acceptable I will do the more substantial work of postponing this change by reverting ruby-sass to the older version for now. - Jonas -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAlm29ywACgkQLHwxRsGg ASEhUw/+PA2n5oUcPr/Gvja9xIUxxG7znEGv6xY9uMSj+AMicMdzM/q8S6TSXE+i HbOitombO/i8WZe5dw6yuHDobymSLQ9ykUD5gtlsjfzSSc+SOecex7QuradG6Xnt jjsmBOG6xUicAJkG05HBVQSNIDzlLPU/Pg9unzZxIBb12KWixEjuyzbC9OdunaHl e83tSu8+rEBhRo8U8c6Rn7c7OB51UBqxhi9Ju9wF5EnaNfLYqgh8wCUOBjq/E3LU OsT7PYhwBUO5AWct9we114LjRtsqR/q9oQdwG5LsuYhKT/ehikPa2B48s2RLbcMr 0fe260r8VMTTKS5tac/VDjkeX8rQo4UunRigyE7TUdi/dZXTjLcF1NLqHiCqeyWn FxgDRhaCFjZ7mTkkyM34c6hUHbvcXCSiRVcmRcOpU/3aAVJcx/iOEjCF2UUAo7cD JwmkoereCg8aGPPXgU9JHA5yKJTRUT6ZIvfUvP2aL6IWSQzhFrz0/PtgMoyD46pE ZzbJ1RFvuQmT5BrRl13nK3dRlru0TY8R2oyZyOlBd8Q5c5CmZ0IKHvoryTCYHVz8 RKalpryhzfmWn3dzEpuPnYfQE98TgYf57mgMgVGmzOTKdYJPDiGAhHsWcRmvM3C9 fXa/mRuLOCkxxwtry9fZY94KDQ4LXsWAN+BbJHXDW+1bJIHz4LE= =0Suc -END PGP SIGNATURE- --- End Message --- --- Begin Message --- Source: nanoc Source-Version: 4.8.5-1 We believe that the bug you reported is fixed in the latest version of nanoc, 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 875...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Cédric Boutillier (supplier of updated nanoc 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, 12 Sep 2017 15:51:08 +0200 Source: nanoc Binary: nanoc nanoc-doc Architecture: source Version: 4.8.5-1 Distribution: unstable Urgency: medium Maintainer: Debian Ruby Extras Maintainers Changed-By: Cédric Boutillier Description: nanoc - static site generator written in Ruby nanoc-doc - static site generator written in Ruby - documentation Closes: 875510 Changes: nanoc (4.8.5-1) unstable; urgency=medium . * New upstream version 4.8.5 * Remove dependency on (broken) ruby-compass (Closes: #875510) * Bump Standards-Version to 4.1.0 Checksums-Sha1: 3da3c2f8650686c7ecfb55a25e6a8e6a7184ec90 2286 nanoc_4.8.5-1.dsc 9b3dff8c215b61a1282239271143891252907a4d 259119 nanoc_4.8.5.orig.tar.gz c61a92cd1f295ac53d74404448582affa6e46426 8540 nanoc_4.8.5-1.debian.tar.xz bd8e0bd44d9dc9838c2a5a4592b66ee74015ca6e 11537 nanoc_4.8.5-1_source.buildinfo Checksums-Sha256: ee6725aa997106990af8654bd100cc41532cf41cdd69c20049a7feca136af732 2286 nanoc_4.8.5-1.dsc b62133f86b53d8a58accfcb647dee18afe5c1fe3d303cd7092bd1c546f8c5048 259119 nanoc_4.8.5.orig.tar.gz 9380c2b151f26dcf3f095929e4c997df9f3e2c38ff820c0933c74f6bbfefe53b 8540 nanoc_4.8.5-1.debian.tar.xz 39ba1a533ac14de46bffbb96f07cae33e3829cf2943ae9d7960215e593b35eff 11537 nanoc_4.8.5-1_source.buildinfo Files: 0b728512c1cf97f71134c33058af8ddb 2286 web optional nanoc_4.8.5-1.dsc edd64396a62c794d42b71ec66e6776ee 259119 web optional nanoc_4.8.
Bug#873878: marked as done (glusterfs-client: mount.glusterfs needs bash as /bin/sh)
Your message dated Tue, 12 Sep 2017 15:21:19 +
with message-id
and subject line Bug#873878: fixed in glusterfs 3.12.1-1
has caused the Debian Bug report #873878,
regarding glusterfs-client: mount.glusterfs needs bash as /bin/sh
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.)
--
873878: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873878
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: glusterfs-client
Version: 3.12.0-1
Severity: serious
Tags: upstream
Justification: Policy 10.4
Version 3.12 of Glusterfs adds code in /sbin/mount.glusterfs that depends on
bash.
With dash as /bin/sh, I get the following error message when trying to mount a
glusterfs volume:
> /sbin/mount.glusterfs: 667: /sbin/mount.glusterfs: Bad substitution
Line 667 is:
667 [ ${volume_str:0:1} = '/' ] && {
Modifying mount.glusterfs to use /bin/bash makes it possible to mount again.
/Micke
-- System Information:
Debian Release: buster/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.12.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages glusterfs-client depends on:
ii fuse 2.9.7-1
ii glusterfs-common 3.12.0-1
ii libc6 2.24-17
ii libssl1.1 1.1.0f-5
ii python2.7.13-2
glusterfs-client recommends no packages.
glusterfs-client suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Source: glusterfs
Source-Version: 3.12.1-1
We believe that the bug you reported is fixed in the latest version of
glusterfs, 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 873...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Patrick Matthäi (supplier of updated glusterfs 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, 12 Sep 2017 14:53:05 +0200
Source: glusterfs
Binary: glusterfs-client glusterfs-server glusterfs-common
Architecture: source amd64
Version: 3.12.1-1
Distribution: unstable
Urgency: medium
Maintainer: Patrick Matthäi
Changed-By: Patrick Matthäi
Description:
glusterfs-client - clustered file-system (client package)
glusterfs-common - GlusterFS common libraries and translator modules
glusterfs-server - clustered file-system (server package)
Closes: 873878
Changes:
glusterfs (3.12.1-1) unstable; urgency=medium
.
* New upstream release.
- Merged patch to fix bashishm in mount.glusterfs. Thanks to Michael
Lundkvist for his report and patch.
Closes: #873878
Checksums-Sha1:
b6773d672fd0c699d331e378c0b5bf64391e3526 2226 glusterfs_3.12.1-1.dsc
9778607726e9ec997e0a37da7f9c26ae381f2e66 9377924 glusterfs_3.12.1.orig.tar.gz
4a6ae50401c8d18e223634521f8b090cb46628a0 16176 glusterfs_3.12.1-1.debian.tar.xz
ad58890bf004125dfa3e496112af0876d3ea3ed3 32602
glusterfs-client-dbgsym_3.12.1-1_amd64.deb
024f4b4b0bec5f57be0cf1f5c8b117c9074f9b73 4314534
glusterfs-client_3.12.1-1_amd64.deb
63fd92c0c3f9758ec77c7aee9a1c4817c2a4cdfb 13443804
glusterfs-common-dbgsym_3.12.1-1_amd64.deb
e6dcdf049f8eb59ccc2a307fbb8334866fd5d427 7305184
glusterfs-common_3.12.1-1_amd64.deb
4987cb3d5de0bae94d810ecb79daa736223be8be 618156
glusterfs-server-dbgsym_3.12.1-1_amd64.deb
09133fa4e2f0fac9cdb6cc0644215bce6ee0997c 4478614
glusterfs-server_3.12.1-1_amd64.deb
3ec208ffb8526d2db5047a0937543af72c0e188e 9906
glusterfs_3.12.1-1_amd64.buildinfo
Checksums-Sha256:
0caeeec9931bafc49244ad11081d413e6a48dabd75fde553932d1e639a941932 2226
glusterfs_3.12.1-1.dsc
87f39580012be1a23ecd1056fc144a387aafd72cb34b2edd83c7155aea8a5370 9377924
glusterfs_3.12.1.orig.tar.gz
7e524c9aebdb6fc542f95f3b9711ed79cf7e507527634eb6c460efb660464c7e 16176
glusterfs_3.12.1-1.debian.tar.xz
4cfa400c540c09acd0e543fe2adec92c3b70e19170aca5fa8e6042778065d61e 32602
glusterfs-client-dbgsym_3.12.1-1_amd64.deb
d76425284f5c549ea480fd726b407f186268dd80bb825f7d78c309e14177c1e4 4314534
glusterfs-client_3.12.1-1_amd64.deb
cbe0f894
Processed: Rearrange bugs 872273 and 872258
Processing commands for cont...@bugs.debian.org: > reassign 872273 slic3r Bug #872273 [mesa-utils] mesa-utils: Undefined OpenGL macro GL_MULTISAMPLE Bug reassigned from package 'mesa-utils' to 'slic3r'. No longer marked as found in versions mesa-demos/8.3.0-5. Ignoring request to alter fixed versions of bug #872273 to the same values previously set > # Although bug #872273 has probably something to do with mesa, it > # actually refers to the slic3r package and not mesa-utils. > unblock 872258 by 872273 Bug #872258 [slic3r-prusa] slic3r-prusa: Not working: Your vendor has not defined OpenGL macro GL_MULTISAMPLE... 872258 was blocked by: 872273 872258 was not blocking any bugs. Removed blocking bug(s) of 872258: 872273 > # Bugs #872273 and #872258 are actually the same bug. I won't merge > # them since they affect different packages with different upstream > # sources. The bug will be fixed independently for each package, so I'm > # also removing the block. > severity 872273 grave Bug #872273 [slic3r] mesa-utils: Undefined OpenGL macro GL_MULTISAMPLE Severity set to 'grave' from 'normal' > severity 872258 grave Bug #872258 [slic3r-prusa] slic3r-prusa: Not working: Your vendor has not defined OpenGL macro GL_MULTISAMPLE... Severity set to 'grave' from 'important' > # This bug renders both packages unusable > thanks Stopping processing here. Please contact me if you need assistance. -- 872258: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872258 872273: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872273 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#870849: marked as pending
tag 870849 pending thanks Hello, Bug #870849 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: https://anonscm.debian.org/cgit/pkg-ruby-extras/ruby-kramdown-rfc2629.git/commit/?id=956991f --- commit 956991f37089df190d13dd77752e62d50dfcf238 Author: Cédric Boutillier Date: Tue Sep 12 16:18:33 2017 +0200 prepare changelog diff --git a/debian/changelog b/debian/changelog index 3073142..638633f 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,13 @@ +ruby-kramdown-rfc2629 (1.2.5-1) unstable; urgency=medium + + * New upstream version 1.2.5 ++ works with ruby-kramdown >= 1.14 (Closes: #870849) + * Add patch to disable the use of certified gem + * Set minimal version of kramdown dependency to 1.14 + * Bump Standards-Version to 4.1.0 (no changes needed) + + -- Cédric Boutillier Tue, 12 Sep 2017 16:17:31 +0200 + ruby-kramdown-rfc2629 (1.0.36-1) unstable; urgency=medium * New upstream version 1.0.36
Processed: Bug#870849 marked as pending
Processing commands for cont...@bugs.debian.org: > tag 870849 pending Bug #870849 [src:ruby-kramdown-rfc2629] ruby-kramdown-rfc2629 FTBFS with ruby-kramdown 1.14.0-1 Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 870849: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=870849 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#875510 marked as pending
Processing commands for cont...@bugs.debian.org: > tag 875510 pending Bug #875510 [src:nanoc] nanoc: ruby-compass obsolete and now broken Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 875510: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875510 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#875510: marked as pending
tag 875510 pending thanks Hello, Bug #875510 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: https://anonscm.debian.org/cgit/pkg-ruby-extras/nanoc.git/commit/?id=0775a73 --- commit 0775a73e916f82a01697a5fd7407acfc6aee43b8 Author: Cédric Boutillier Date: Tue Sep 12 15:53:25 2017 +0200 prepare changelog diff --git a/debian/changelog b/debian/changelog index 7d3351c..e54a60a 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,11 @@ +nanoc (4.8.5-1) unstable; urgency=medium + + * New upstream version 4.8.5 + * Remove dependency on (broken) ruby-compass (Closes: #875510) + * Bump Standards-Version to 4.1.0 + + -- Cédric Boutillier Tue, 12 Sep 2017 15:51:08 +0200 + nanoc (4.8.0-1) unstable; urgency=medium * New upstream version 4.8.0
Processed: fixed 875448 in 24.4+1-5+deb8u1, fixed 875448 in 24.5+1-11+deb9u1
Processing commands for cont...@bugs.debian.org: > # version which will be used in DSA, but upload missed the bug closer > fixed 875448 24.4+1-5+deb8u1 Bug #875448 [src:emacs24] emacs24: enriched text remote code execution The source 'emacs24' and version '24.4+1-5+deb8u1' do not appear to match any binary packages Marked as fixed in versions emacs24/24.4+1-5+deb8u1. > fixed 875448 24.5+1-11+deb9u1 Bug #875448 [src:emacs24] emacs24: enriched text remote code execution The source 'emacs24' and version '24.5+1-11+deb9u1' do not appear to match any binary packages Marked as fixed in versions emacs24/24.5+1-11+deb9u1. > thanks Stopping processing here. Please contact me if you need assistance. -- 875448: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875448 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#875596: perl: CVE-2017-12837: Heap buffer overflow in regular expression compiler
Source: perl Version: 5.20.2-1 Severity: grave Tags: security upstream patch Forwarded: https://rt.perl.org/Public/Bug/Display.html?id=131582 Hi, the following vulnerability was published for perl. CVE-2017-12837[0]: Heap buffer overflow in regular expression compiler >From release notes: Compiling certain regular expression patterns with the case-insensitive modifier could cause a heap buffer overflow and crash perl. This has now been fixed. If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2017-12837 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-12837 [1] https://rt.perl.org/Public/Bug/Display.html?id=131582 (not yet public) Regards, Salvatore
Bug#875597: perl: CVE-2017-12883: Buffer over-read in regular expression parser
Source: perl Version: 5.20.2-1 Severity: grave Tags: security patch upstream Forwarded: https://rt.perl.org/Public/Bug/Display.html?id=131598 *** /tmp/perl.reportbug Package: perl X-Debbugs-CC: t...@security.debian.org secure-testing-t...@lists.alioth.debian.org Severity: grave Tags: security Hi, the following vulnerability was published for perl. CVE-2017-12883[0]: Buffer over-read in regular expression parser >From release notes: For certain types of syntax error in a regular expression pattern, the error message could either contain the contents of a random, possibly large, chunk of memory, or could crash perl. This has now been fixed. If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2017-12883 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-12883 [1] https://rt.perl.org/Public/Bug/Display.html?id=131598 (not yet public) Regards, Salvatore
Bug#875434: marked as done (libqbscore1.8: The package should depend on qbs-common)
Your message dated Tue, 12 Sep 2017 13:05:21 + with message-id and subject line Bug#875434: fixed in qbs 1.8.1+dfsg-4 has caused the Debian Bug report #875434, regarding libqbscore1.8: The package should depend on qbs-common 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.) -- 875434: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875434 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libqbscore1.8 Version: 1.8.1+dfsg-3 Severity: grave Justification: renders package unusable Dear Maintainer, libqbs is useless without its data files. Opening a qbs project in Qt Creator when qbs-common is not installed fails on parsing. -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.12.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_IL, LC_CTYPE=en_IL (charmap=UTF-8), LANGUAGE=en_IL:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages libqbscore1.8 depends on: ii libc62.24-17 ii libgcc1 1:7.2.0-4 ii libgl1 0.2.999+git20170802-3 ii libgl1-mesa-glx 17.2.0-2 ii libqt5core5a 5.9.1+dfsg-9 ii libqt5gui5 5.9.1+dfsg-9 ii libqt5network5 5.9.1+dfsg-9 ii libqt5script55.9.1+dfsg-2 ii libqt5test5 5.9.1+dfsg-9 ii libqt5xml5 5.9.1+dfsg-9 ii libstdc++6 7.2.0-4 libqbscore1.8 recommends no packages. libqbscore1.8 suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: qbs Source-Version: 1.8.1+dfsg-4 We believe that the bug you reported is fixed in the latest version of qbs, 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 875...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Dmitry Shachnev (supplier of updated qbs 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, 12 Sep 2017 15:46:40 +0300 Source: qbs Binary: qbs qbs-common libqbscore1.8 libqbsqtprofilesetup1.8 qbs-dev qbs-examples qbs-doc qbs-doc-html Architecture: source Version: 1.8.1+dfsg-4 Distribution: unstable Urgency: medium Maintainer: Debian Qt/KDE Maintainers Changed-By: Dmitry Shachnev Description: libqbscore1.8 - Qbs core library libqbsqtprofilesetup1.8 - Qbs profile setup library qbs- cross-platform build tool qbs-common - Qbs static files qbs-dev- Qbs development files qbs-doc- Qbs documentation qbs-doc-html - Qbs HTML documentation qbs-examples - examples for Qbs build tool Closes: 875434 Changes: qbs (1.8.1+dfsg-4) unstable; urgency=medium . * Make libqbscore1.8 depend on qbs-common (closes: #875434). * Update debian/libqbscore1.8.symbols from buildds’ logs. Checksums-Sha1: b5880043aaf0fa6f52fe5e49de999e74e67e7cea 2542 qbs_1.8.1+dfsg-4.dsc cda15ad595157bf25b500e669e24f83e31297cc2 19064 qbs_1.8.1+dfsg-4.debian.tar.xz 60c8a3677c692b95425bc58c55c7b1fd2d952c3c 11157 qbs_1.8.1+dfsg-4_source.buildinfo Checksums-Sha256: 4b924e6b68c34d5458e1aa9dc2c39b5b5d77b1aeaed02c5215c79d2c85e60494 2542 qbs_1.8.1+dfsg-4.dsc b0459ca50f2bc743da86acf17fae0cf4284ae02d4ac4fb3e71d3aa530bb6df12 19064 qbs_1.8.1+dfsg-4.debian.tar.xz a94cd3d7f67dbab88d647ea7f4f7f40bb35a4669fb496764f30d84bc4618a1cd 11157 qbs_1.8.1+dfsg-4_source.buildinfo Files: 1cf66ed8a5d7f177222d10e99eaf75e1 2542 devel optional qbs_1.8.1+dfsg-4.dsc 772f9d7e9ae94b6eee210f1dc71e9ec0 19064 devel optional qbs_1.8.1+dfsg-4.debian.tar.xz dfaca4eb6208b6f795262bf4b77f00bb 11157 devel optional qbs_1.8.1+dfsg-4_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEbEPcK+5mZmLK5jNU1v5xA2P4XdMFAlm32HAACgkQ1v5xA2P4 XdMcGw/9GXkJ/evREDnpaTlz8QNSqIukkJ5JxVMW1yFi3SafjpIP8CJ005GZq10Y hOqXbz/sXJtV8erENVhAxbBIi+3J6Fi8V5xbUw9ypPgeRLEPs/6HewMLg32b9V+b Je7o0KtokU2vGA1NrIqU711BD+MK1JJTvRTckZg9tXjHzOLvTAenBm04lvyPjQ3u CS8nUhTeGtpwMj+IoSmDjGdawPYFRnU4Ar+bEPALIqBXTmjPkELu63U1rkK26uVV Q+x0uyajzBj81hmlMY/Hqh73sihsUZvjemevh84qAgWTIJyI4tn/1x1CYq4Onu6S BML85PxGr0pDUKgxJszOvJlqsX44UXTsBrAESb2BbKC5ynicngH4KbX64jHCbe/4 0wbrdMUNUjB1MYj7LjPBKG4O6Z+MWcasbqZKhHsIRjbao4hoS
Bug#874786: marked as done (qt3d5-dev: broken symlinks: /usr/lib/i386-linux-gnu/libQt53D{QuickScene2D, QuickAnimation, Animation}.so -> libQt53D*.so.5.9.1)
Your message dated Tue, 12 Sep 2017 12:22:38 +
with message-id
and subject line Bug#874786: fixed in qt3d-opensource-src 5.9.1+dfsg-3
has caused the Debian Bug report #874786,
regarding qt3d5-dev: broken symlinks:
/usr/lib/i386-linux-gnu/libQt53D{QuickScene2D, QuickAnimation, Animation}.so ->
libQt53D*.so.5.9.1
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
874786: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874786
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: qt3d5-dev
Version: 5.9.1+dfsg-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package ships (or creates)
a broken symlink.
>From the attached log (scroll to the bottom...):
0m50.0s ERROR: FAIL: Broken symlinks:
/usr/lib/i386-linux-gnu/libQt53DQuickScene2D.so ->
libQt53DQuickScene2D.so.5.9.1
/usr/lib/i386-linux-gnu/libQt53DQuickAnimation.so ->
libQt53DQuickAnimation.so.5.9.1
/usr/lib/i386-linux-gnu/libQt53DAnimation.so -> libQt53DAnimation.so.5.9.1
Looks like missing dependencies on libqt53dquickscene2d5,
libqt53dquickanimation5, libqt53danimation5.
cheers,
Andreas
qt3d5-dev_5.9.1+dfsg-2+b1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: qt3d-opensource-src
Source-Version: 5.9.1+dfsg-3
We believe that the bug you reported is fixed in the latest version of
qt3d-opensource-src, 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 874...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Dmitry Shachnev (supplier of updated qt3d-opensource-src
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, 12 Sep 2017 15:04:41 +0300
Source: qt3d-opensource-src
Binary: libqt53dcore5 libqt53dquick5 libqt53dquickrender5 libqt53dinput5
libqt53drender5 libqt53dlogic5 libqt53dquickinput5 libqt53dquickextras5
libqt53dextras5 libqt53dquickscene2d5 libqt53danimation5
libqt53dquickanimation5 qt3d-gltfsceneio-plugin qt3d-assimpsceneimport-plugin
qt3d-defaultgeometryloader-plugin qt3d-scene2d-plugin qml-module-qt3d
qml-module-qtquick-scene3d qml-module-qtquick-scene2d qt3d5-dev qt3d5-examples
qt3d5-doc qt3d5-doc-html
Architecture: source
Version: 5.9.1+dfsg-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Qt/KDE Maintainers
Changed-By: Dmitry Shachnev
Description:
libqt53danimation5 - Qt 3D animation module
libqt53dcore5 - Qt 3D module
libqt53dextras5 - Qt 3D extras
libqt53dinput5 - Qt 3D Input module
libqt53dlogic5 - Qt 3D logic module
libqt53dquick5 - Qt 3D Quick module
libqt53dquickanimation5 - Qt 3D Quick animation module
libqt53dquickextras5 - Qt 3D Quick extras
libqt53dquickinput5 - Qt 3D Quick input
libqt53dquickrender5 - Qt 3D Quick Renderer module
libqt53dquickscene2d5 - Qt 3D Quick scene module
libqt53drender5 - Qt 3D Renderer module
qml-module-qt3d - Qt 5 3D QML module
qml-module-qtquick-scene2d - Qt 5 Quick Scene 2D QML module
qml-module-qtquick-scene3d - Qt 5 Quick Scene 3D QML module
qt3d-assimpsceneimport-plugin - Qt 3D GL Assimp scene import plugin
qt3d-defaultgeometryloader-plugin - Qt 3D default geometry loader plugin
qt3d-gltfsceneio-plugin - Qt 3D GL Transmission Format scene IO plugin
qt3d-scene2d-plugin - Qt 3D Scene 2D plugin
qt3d5-dev - Qt 5 3D development files
qt3d5-doc - Qt 3D documentation
qt3d5-doc-html - Qt 3D HTML documentation
qt3d5-examples - Qt 5 3d examples
Closes: 874786
Changes:
qt3d-opensource-src (5.9.1+dfsg-3) unstable; urgency=medium
.
* Add missing dependencies to qt3d5-dev package (closes: #874786).
* Update symbols files from buildds’ logs.
Checksums-Sha1:
b8dd285da15798284ca4ab72071ed497816c2dc1 4133
qt3d-opensource-src_5.9.1+dfsg-3.dsc
65fe1bef140353fec067c797015cb6b9067a3f34 51924
qt3d-opensource-src_5.9.1+dfsg-3.debian.tar.xz
8909b9b554f5a3d719c616b542515b1d911ac655 11579
qt3d-opensource-src_5.9.1+dfsg-3_source.buildinfo
Checksums-Sha256:
77d6f8904346d5123390e1a091ebaa7389eeeb312fae35f6574dc2bc100f7244 4133
qt3d-opensource-src_5.9.1+dfsg-3.dsc
d9f375dfdd9d4a500648c35d07be295ea933516b777273a7ed12d8d5cb619cd4 519
Bug#874125: marked as done (octave-image FTBFS with octave-pkg-dev 1.5.0)
Your message dated Tue, 12 Sep 2017 11:52:29 + with message-id and subject line Bug#874125: fixed in octave-image 2.6.1-3 has caused the Debian Bug report #874125, regarding octave-image FTBFS with octave-pkg-dev 1.5.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.) -- 874125: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874125 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: octave-image Version: 2.6.1-2 Severity: serious https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/octave-image.html ... Summary: 1169 tests, 1132 passed, 21 known failures, 0 skipped /usr/share/cdbs/1/class/octave-pkg.mk:108: recipe for target 'check-pkg' failed make: *** [check-pkg] Error 1 --- End Message --- --- Begin Message --- Source: octave-image Source-Version: 2.6.1-3 We believe that the bug you reported is fixed in the latest version of octave-image, 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 874...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Rafael Laboissiere (supplier of updated octave-image 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: Sun, 10 Sep 2017 16:40:10 -0300 Source: octave-image Binary: octave-image Architecture: source amd64 Version: 2.6.1-3 Distribution: unstable Urgency: medium Maintainer: Debian Octave Group Changed-By: Rafael Laboissiere Description: octave-image - image manipulation for Octave Closes: 867230 874125 Changes: octave-image (2.6.1-3) unstable; urgency=medium . * Fix (or declare as known failure) all failing tests, such that the package dos not FTBFS with octave-pkg-dev 1.5.0 (Closes: #874125). Patches added: + im2bw-unit-test.patch ; New patch + typo-unit-test-watershed.patch: New patch + skip-unit-tests-watershed.patch: New patch + skip-unit-tests-impyramid.patch: New patch + skip-unit-tests-edge.patch: New patch + drop-unit-tests-grayslice.patch: New patch + drop-unit-tests-bwmorph.patch: New patch + drop-unit-test-otf2psf.patch: New patch + drop-unit-test-nlfilter.patch: New patch + error-unit-test-strel.patch: New patch + skip-unit-test-cp2tform.patch: New patch * d/control: + Bump Standards-Version to 4.1.0 (no changes needed) + Drop dependency on imagemagick (Closes: #867230) + Add gnuplot-nox to Build-Depends Checksums-Sha1: 6350d79a15a96b9e8bc72a5337181df8b06f1de4 2008 octave-image_2.6.1-3.dsc 232c65947df722f7e7a4344cd7afeacc26e1eceb 9000 octave-image_2.6.1-3.debian.tar.xz a50128966c32a2aeba509343fba10a96d71e1a97 8142922 octave-image-dbgsym_2.6.1-3_amd64.deb f3d3507905c7a1fb4102477a4feb9a6d46c3f75b 12791 octave-image_2.6.1-3_amd64.buildinfo d90021fb6c095892f23a0eae66a21dead2a79101 505162 octave-image_2.6.1-3_amd64.deb Checksums-Sha256: fc56df3370d6ffbf5ff54d7c2ba44ebff80aee4592619618b08dd9be1aa472a7 2008 octave-image_2.6.1-3.dsc 16da9c1ff445defaab6eda1770c6a7eaa871b9fd0c9dfa000b923d2f32810c71 9000 octave-image_2.6.1-3.debian.tar.xz 6a286107d39843ad22fce2c9e92cac723501ce37baf50527edb7c303f69972b5 8142922 octave-image-dbgsym_2.6.1-3_amd64.deb 97df245132b7b2a366b82ab3f7b8deb101bb817558c6f6a332929e6080aea50c 12791 octave-image_2.6.1-3_amd64.buildinfo cb7cfbb24a563957883a18ea2522b12a3b87e40491b05104ab6d5c4e2e40a435 505162 octave-image_2.6.1-3_amd64.deb Files: e73ccf712dc1b15958ca1df4f9045ff5 2008 math optional octave-image_2.6.1-3.dsc 6d1a22c8bcc98cde2f000eb98eb2e471 9000 math optional octave-image_2.6.1-3.debian.tar.xz 8e3469130a05547b834a012d69f1f97e 8142922 debug optional octave-image-dbgsym_2.6.1-3_amd64.deb 8cfbc49db926fae317c9641ef09f5998 12791 math optional octave-image_2.6.1-3_amd64.buildinfo bc3a5d18480e0fab0f563a1b843fe6a3 505162 math optional octave-image_2.6.1-3_amd64.deb -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEP0ZDkUmP6HS9tdmPISSqGYN4XJAFAlm3xp4ACgkQISSqGYN4 XJBW6A//Y8yrSL16CkL85k7SIM+2wBnGRVaewC4Ja8e0Rtf/VNBrX7sl/hpgoevP sC1jkdhoSVzIEUw4vWtg2Tay31B0PL63fDq14phXPDTOAflz442yjs/8I3hiHPr1 03rm/Ars6QkRCb5NGeHYog88eS25fcHi0ht+cr1ett/77lZK0ojaZOVC6IGkxDU/ m6hmLOW++i44KHEoX9Hz1FvhdzgLBCZg6wbQvbggaOu3M
Bug#875379: marked as done (setools: error: No module named 'pkg_resources')
Your message dated Tue, 12 Sep 2017 10:06:55 + with message-id and subject line Bug#875379: fixed in setools 4.1.1-3 has caused the Debian Bug report #875379, regarding setools: error: No module named 'pkg_resources' 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.) -- 875379: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875379 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: setools Version: 4.1.1-2 With the new update seinfo, sesearch and semanage stopped working: root@server02 ~ # semanage Traceback (most recent call last): File "/usr/sbin/semanage", line 28, in import seobject File "/usr/lib/python3/dist-packages/seobject.py", line 34, in import sepolicy File "/usr/lib/python3/dist-packages/sepolicy/__init__.py", line 8, in import setools File "/usr/lib/python3/dist-packages/setools/__init__.py", line 78, in from .permmap import PermissionMap File "/usr/lib/python3/dist-packages/setools/permmap.py", line 25, in import pkg_resources ImportError: No module named 'pkg_resources' root@server02 ~ # seinfo Traceback (most recent call last): File "/usr/bin/seinfo", line 21, in import setools File "/usr/lib/python3/dist-packages/setools/__init__.py", line 78, in from .permmap import PermissionMap File "/usr/lib/python3/dist-packages/setools/permmap.py", line 25, in import pkg_resources ImportError: No module named 'pkg_resources' root@server02 ~ # sesearch Traceback (most recent call last): File "/usr/bin/sesearch", line 21, in import setools File "/usr/lib/python3/dist-packages/setools/__init__.py", line 78, in from .permmap import PermissionMap File "/usr/lib/python3/dist-packages/setools/permmap.py", line 25, in import pkg_resources ImportError: No module named 'pkg_resources' --- End Message --- --- Begin Message --- Source: setools Source-Version: 4.1.1-3 We believe that the bug you reported is fixed in the latest version of setools, 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 875...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Laurent Bigonville (supplier of updated setools 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, 12 Sep 2017 11:30:53 +0200 Source: setools Binary: setools setools-gui python3-setools python3-setoolsgui Architecture: source Version: 4.1.1-3 Distribution: unstable Urgency: medium Maintainer: Debian SELinux maintainers Changed-By: Laurent Bigonville Description: python3-setools - SETools Python bindings python3-setoolsgui - SETools Python bindings (GUI) setools- tools for Security Enhanced Linux policy analysis setools-gui - GUI tools for Security Enhanced Linux policy analysis Closes: 875379 Changes: setools (4.1.1-3) unstable; urgency=medium . * debian/control: Add python3-pkg-resources to the dependencies (Closes: #875379) Checksums-Sha1: 67ee4465ee4ccfad9e67f34fc184a79508634d47 2070 setools_4.1.1-3.dsc 06090bd4dae190574a51450f115a41ec0da12027 13744 setools_4.1.1-3.debian.tar.xz 56121ad5aab2fe9662dcb0ffec0171ecb85e9a64 6647 setools_4.1.1-3_source.buildinfo Checksums-Sha256: 447f40cadee8bc1c7057ee28be0ce80c6a3b1ced95f91d639a6b27becb95fe79 2070 setools_4.1.1-3.dsc 052709f4fb253499d499e834e79b52e59966773b0a58d1ba9c93ab5f508463eb 13744 setools_4.1.1-3.debian.tar.xz 9232ffe059d045750b8acee24df5f071ec9243bd482a03eb3ebba889f829f233 6647 setools_4.1.1-3_source.buildinfo Files: 7f672a85ce0509ef0b498d623bf2f9ca 2070 admin optional setools_4.1.1-3.dsc 2b892bbbeb22ace47e08badee65418f0 13744 admin optional setools_4.1.1-3.debian.tar.xz 0a1aeb2dd2510c5d6e22e80d0c07e538 6647 admin optional setools_4.1.1-3_source.buildinfo -BEGIN PGP SIGNATURE- iQFFBAEBCAAvFiEEmRrdqQAhuF2x31DwH8WJHrqwQ9UFAlm3qacRHGJpZ29uQGRl Ymlhbi5vcmcACgkQH8WJHrqwQ9WERgf+OIrH97D0Gq6v0iF1RyhCmZBLD5Ot/LBd LQVtgpPzVBrMM6WHc7Et7UNhgUarVc28qRfA5zFOYngYF9YvZlFrb3PHkR++w5W3 EzGhfK0pHdidxQa7A8I59fBbL+UmcLokyLA290JG2xAOXEyGv+8juUuAYDLsQymb zTkUz1Lh5ZdJGgC2/srz66Mi0D8RKtG9uq0fO7doXvVDYFqIdsFrjBDRo2aeIqxb i0dynssq2BXEg1e5uoLMZ+OXJ2colJ1tQ/88n2YTDVijfsdC6DZ6EhGmvVZswrlr KTs1b7n11GKByGKvsvEnierKhQm/RC
Bug#853493: marked as done (libidn: ftbfs with GCC-7)
Your message dated Tue, 12 Sep 2017 10:05:25 +
with message-id
and subject line Bug#853493: fixed in libidn 1.33-2
has caused the Debian Bug report #853493,
regarding libidn: ftbfs with GCC-7
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.)
--
853493: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853493
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:libidn
Version: 1.33-1
Severity: normal
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-7
Please keep this issue open in the bug tracker for the package it
was filed for. If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.
The package fails to build in a test rebuild on at least amd64 with
gcc-7/g++-7, but succeeds to build with gcc-6/g++-6. The
severity of this report may be raised before the buster release.
There is no need to fix this issue in time for the stretch release.
The full build log can be found at:
http://people.debian.org/~doko/logs/gcc7-20170126/libidn_1.33-1_unstable_gcc7.log
The last lines of the build log are at the end of this report.
To build with GCC 7, either set CC=gcc-7 CXX=g++-7 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.
apt-get -t=experimental install g++
Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-7/porting_to.html
[...]
../../gltests/test-intprops.c:279:42: error: expected expression before '=='
token
VERIFY (INT_MULTIPLY_OVERFLOW (a, b) == (v))
^
../../gltests/../gl/verify.h:251:31: note: in definition of macro 'verify'
#define verify(R) _GL_VERIFY (R, "verify (" #R ")")
^
../../gltests/test-intprops.c:279:5: note: in expansion of macro 'VERIFY'
VERIFY (INT_MULTIPLY_OVERFLOW (a, b) == (v))
^~
../../gltests/test-intprops.c:273:5: note: in expansion of macro
'CHECK_PRODUCT1'
CHECK_PRODUCT1(a, b, t, v, vres); \
^~
../../gltests/test-intprops.c:317:3: note: in expansion of macro 'CHECK_PRODUCT'
CHECK_PRODUCT (INT_MIN, ULONG_MAX, unsigned long int, true,
^
../../gltests/test-intprops.c:279:42: error: expected expression before '=='
token
VERIFY (INT_MULTIPLY_OVERFLOW (a, b) == (v))
^
../../gltests/../gl/verify.h:251:31: note: in definition of macro 'verify'
#define verify(R) _GL_VERIFY (R, "verify (" #R ")")
^
../../gltests/test-intprops.c:279:5: note: in expansion of macro 'VERIFY'
VERIFY (INT_MULTIPLY_OVERFLOW (a, b) == (v))
^~
../../gltests/test-intprops.c:274:5: note: in expansion of macro
'CHECK_PRODUCT1'
CHECK_PRODUCT1(b, a, t, v, vres)
^~
../../gltests/test-intprops.c:317:3: note: in expansion of macro 'CHECK_PRODUCT'
CHECK_PRODUCT (INT_MIN, ULONG_MAX, unsigned long int, true,
^
Makefile:2043: recipe for target 'test-intprops.o' failed
make[5]: *** [test-intprops.o] Error 1
make[5]: Leaving directory '/<>/build/gltests'
Makefile:2677: recipe for target 'check-am' failed
make[4]: *** [check-am] Error 2
make[4]: Leaving directory '/<>/build/gltests'
Makefile:2072: recipe for target 'check-recursive' failed
make[3]: *** [check-recursive] Error 1
make[3]: Leaving directory '/<>/build/gltests'
Makefile:2680: recipe for target 'check' failed
make[2]: *** [check] Error 2
make[2]: Leaving directory '/<>/build/gltests'
Makefile:1346: recipe for target 'check-recursive' failed
make[1]: *** [check-recursive] Error 1
make[1]: Leaving directory '/<>/build'
dh_auto_test: make -j64 check VERBOSE=1 returned exit code 2
cd /<>
debian/rules:20: recipe for target 'build' failed
make: *** [build] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2
--- End Message ---
--- Begin Message ---
Source: libidn
Source-Version: 1.33-2
We believe that the bug you reported is fixed in the latest version of
libidn, 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 853...@bugs.debian.org,
Processed: severity of 875379 is serious
Processing commands for cont...@bugs.debian.org: > severity 875379 serious Bug #875379 [setools] setools: error: No module named 'pkg_resources' Severity set to 'serious' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 875379: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875379 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#871279: marked as done (libdolfin2016.2: requires rebuild against GCC 7 and symbols/shlibs bump)
Your message dated Tue, 12 Sep 2017 09:04:47 + with message-id and subject line Bug#871279: fixed in dolfin 2017.1.0-4 has caused the Debian Bug report #871279, regarding libdolfin2016.2: requires rebuild against GCC 7 and symbols/shlibs bump 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.) -- 871279: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871279 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libdolfin2016.2 Version: 2016.2.0-5 Severity: serious Tags: sid buster User: debian-...@lists.debian.org Usertags: gcc-7-op-mangling Hi, It appears that your package provides an external symbol that is affected by the recent name mangling changes in GCC 7. See: https://gcc.gnu.org/gcc-7/porting_to.html#conversion-op-mangling In GCC 7, the name mangling for C++ conversion operators which return a type using the abi_tag attribute (most commonly std::string) has changed. When your library is compiled with GCC 7, it will now emit two symbols for the conversion operator using the new and old naming. Executables compiled with GCC 7 will always use the new symbol, while old executables compiled using <= GCC 6 will use the old symbol. For new executables to build without undefined references, your library will need rebuilding with GCC 7. To ensure that new executables will pull in the newer version of the library built with GCC 7: - Your library package should Build-Depend on g++ (>= 4:7). - If your package provides a symbols file, ensure that the new conversion operator symbols have a version matching the version this bug is fixed in (including the Debian revision and tilde if necessary). Using apt as an example (debian/libapt-pkg5.0.symbols): (c++)"URI::operator std::__cxx11::basic_string, std::allocator >[abi:cxx11]()@APTPKG_5.0" 0.8.0 + (c++)"URI::operator std::__cxx11::basic_string, std::allocator >()@APTPKG_5.0" 1.5~beta2~ Where "1.5~beta2" is the version this bug was fixed in. - If your package does not provide a symbols file, add a dh_makeshlibs override so that tight enough dependencies are generated. Using libebml as an example (debian/rules): + override_dh_makeshlibs: + # For new symbols when compiled with GCC 7 + dh_makeshlibs -V'libebml4v5 (>= 1.3.4-2~)' Where "1.3.4-2" is the version this bug was fixed in. - If your package is about to be renamed due to an upstream SONAME bump, you do not need to add any special symbols handling. If you would like to know the exact name of the new symbols, using "abipkgdiff" from abigail-tools might be able to help. Thanks, James --- End Message --- --- Begin Message --- Source: dolfin Source-Version: 2017.1.0-4 We believe that the bug you reported is fixed in the latest version of dolfin, 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 871...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Drew Parsons (supplier of updated dolfin 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, 12 Sep 2017 15:45:48 +0800 Source: dolfin Binary: libdolfin-dev libdolfin2017.1 libdolfin2017.1-dbg python-dolfin python3-dolfin python-dolfin-dbg python3-dolfin-dbg dolfin-doc dolfin-bin Architecture: source Version: 2017.1.0-4 Distribution: unstable Urgency: medium Maintainer: Debian Science Team Changed-By: Drew Parsons Description: dolfin-bin - Executable scripts for DOLFIN dolfin-doc - Documentation and demo programs for DOLFIN libdolfin-dev - Shared links and header files for DOLFIN libdolfin2017.1 - Shared libraries for DOLFIN libdolfin2017.1-dbg - Shared libraries with debugging symbols for DOLFIN python-dolfin - Python interface for DOLFIN (Python 2) python-dolfin-dbg - Python 2 extension modules for DOLFIN with debugging symbols python3-dolfin - Python interface for DOLFIN (Python 3) python3-dolfin-dbg - Python 3 extension modules for DOLFIN with debugging symbols Closes: 871279 875395 Changes: dolfin (2017.1.0-4) unstable; urgency=medium . * Team upload. * New upstream (new soname) version built against GCC7. Closes: #871279. * Builds against swig 3.0.12. Closes: #875395.
Bug#866661: marked as done (htmlunit: missing build dependency on junit4)
Your message dated Tue, 12 Sep 2017 09:06:29 +
with message-id
and subject line Bug#81: fixed in htmlunit 2.8-3
has caused the Debian Bug report #81,
regarding htmlunit: missing build dependency on junit4
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.)
--
81: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=81
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: htmlunit
Version: 2.8-2
Severity: serious
Tags: buster sid
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/htmlunit.html
...
dh_auto_build
/usr/lib/jvm/default-java/bin/java -noverify -cp
/usr/share/maven/boot/plexus-classworlds-2.x.jar:/usr/lib/jvm/default-java/lib/tools.jar
-Dmaven.home=/usr/share/maven
-Dmaven.multiModuleProjectDirectory=/build/1st/htmlunit-2.8
-Dclassworlds.conf=/etc/maven/m2-debian.conf
-Dproperties.file.manual=/build/1st/htmlunit-2.8/debian/maven.properties
org.codehaus.plexus.classworlds.launcher.Launcher
-s/etc/maven/settings-debian.xml -Ddebian.dir=/build/1st/htmlunit-2.8/debian
-Dmaven.repo.local=/build/1st/htmlunit-2.8/debian/maven-repo package
-DskipTests -Dnotimestamp=true -Dlocale=en_US
[[1;34mINFO[m] Scanning for projects...
[[1;33mWARNING[m]
[[1;33mWARNING[m] Some problems were encountered while building the effective
model for net.sourceforge.htmlunit:htmlunit:jar:2.8
[[1;33mWARNING[m] The expression ${pom.url} is deprecated. Please use
${project.url} instead.
[[1;33mWARNING[m]
[[1;33mWARNING[m] It is highly recommended to fix these problems because they
threaten the stability of your build.
[[1;33mWARNING[m]
[[1;33mWARNING[m] For this reason, future Maven versions might no longer
support building such malformed projects.
[[1;33mWARNING[m]
[[1;34mINFO[m]
[[1;34mINFO[m]
[1m[m
[[1;34mINFO[m] [1mBuilding HtmlUnit 2.8[m
[[1;34mINFO[m]
[1m[m
[[1;33mWARNING[m] The POM for junit:junit:jar:4.x is missing, no dependency
information available
[[1;34mINFO[m]
[1m[m
[[1;34mINFO[m] [1;31mBUILD FAILURE[m
[[1;34mINFO[m]
[1m[m
[[1;34mINFO[m] Total time: 0.439 s
[[1;34mINFO[m] Finished at: 2018-08-02T10:58:59-12:00
[[1;34mINFO[m] Final Memory: 16M/724M
[[1;34mINFO[m]
[1m[m
[[1;31mERROR[m] Failed to execute goal on project [36mhtmlunit[m:
[1;31mCould not resolve dependencies for project
net.sourceforge.htmlunit:htmlunit:jar:2.8: Cannot access central
(https://repo.maven.apache.org/maven2) in offline mode and the artifact
junit:junit:jar:4.x has not been downloaded from it before.[m -> [1m[Help
1][m
[[1;31mERROR[m]
[[1;31mERROR[m] To see the full stack trace of the errors, re-run Maven with
the [1m-e[m switch.
[[1;31mERROR[m] Re-run Maven using the [1m-X[m switch to enable full debug
logging.
[[1;31mERROR[m]
[[1;31mERROR[m] For more information about the errors and possible solutions,
please read the following articles:
[[1;31mERROR[m] [1m[Help 1][m
http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
dh_auto_build: /usr/lib/jvm/default-java/bin/java -noverify -cp
/usr/share/maven/boot/plexus-classworlds-2.x.jar:/usr/lib/jvm/default-java/lib/tools.jar
-Dmaven.home=/usr/share/maven
-Dmaven.multiModuleProjectDirectory=/build/1st/htmlunit-2.8
-Dclassworlds.conf=/etc/maven/m2-debian.conf
-Dproperties.file.manual=/build/1st/htmlunit-2.8/debian/maven.properties
org.codehaus.plexus.classworlds.launcher.Launcher
-s/etc/maven/settings-debian.xml -Ddebian.dir=/build/1st/htmlunit-2.8/debian
-Dmaven.repo.local=/build/1st/htmlunit-2.8/debian/maven-repo package
-DskipTests -Dnotimestamp=true -Dlocale=en_US returned exit code 1
debian/rules:4: recipe for target 'build' failed
make: *** [build] Error 2
--- End Message ---
--- Begin Message ---
Source: htmlunit
Source-Version: 2.8-3
We believe that the bug you reported is fixed in the latest version of
htmlunit, 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 866...@bugs.debian.org,
and the maintainer will reopen the bug repor
Processed: Re: buzztrax: Update udevadm path
Processing commands for cont...@bugs.debian.org: > severity 852594 minor Bug #852594 [buzztrax] buzztrax: Update udevadm path Severity set to 'minor' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 852594: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852594 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#852594: buzztrax: Update udevadm path
severity 852594 minor thanks Hi, as this only affects a source code comment and not actual code, I'm downgrading the severity to minor. This is in no way serious. Sebastian signature.asc Description: This is a digitally signed message part
Bug#875556: haskell-text-show: FTBFS in unstable due to overlapping instances
Source: haskell-text-show Version: 3.4.1.1-1 Severity: serious Hi, haskell-text-show now FTBFS in unstable[0] due to overlapping instances; the relevant part of the build log is given below: > tests/Spec/Data/List/NonEmptySpec.hs:27:32: error: > * Overlapping instances for Data.Functor.Classes.Show1 NonEmpty > arising from a use of `prop_matchesTextShow1' > Matching instances: > instance Data.Functor.Classes.Show1 NonEmpty > -- Defined in `Data.Orphans' > instance Data.Functor.Classes.Show1 NonEmpty > -- Defined at tests/Instances/Data/List/NonEmpty.hs:20:3 > * In the second argument of `prop', namely > `(prop_matchesTextShow1 :: Int -> NonEmpty Int -> Bool)' > In the second argument of `($)', namely > `prop >"TextShow1 instance" >(prop_matchesTextShow1 :: Int -> NonEmpty Int -> Bool)' > In the expression: > parallel . describe "NonEmpty Int" > $ prop > "TextShow1 instance" > (prop_matchesTextShow1 :: Int -> NonEmpty Int -> Bool) Regards, James [0] https://buildd.debian.org/status/fetch.php?pkg=haskell-text-show&arch=sparc64&ver=3.4.1.1-1%2Bb1&stamp=1505187046&raw=0
Bug#875446: marked as done (libglvnd-dev: overwrites files in old libegl1-mesa-dev)
Your message dated Tue, 12 Sep 2017 07:49:17 + with message-id and subject line Bug#875446: fixed in libglvnd 0.2.999+git20170802-4 has caused the Debian Bug report #875446, regarding libglvnd-dev: overwrites files in old libegl1-mesa-dev to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 875446: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875446 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libglvnd-dev Version: 0.2.999+git20170802-3 Severity: serious Hi, On upgrading today I got this error: > Unpacking libglvnd-dev (0.2.999+git20170802-3) ... > dpkg: error processing archive > /tmp/apt-dpkg-install-Go1Tzy/19-libglvnd-dev_0.2.999+git20170802-3_amd64.deb > (--unpack): > trying to overwrite '/usr/lib/x86_64-linux-gnu/libEGL.so', which is also in > package libegl1-mesa-dev:amd64 17.1.5-1 I am guessing that libglvnd-dev needs to Breaks/Replaces the old mesa dev packages. Thanks, James signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: libglvnd Source-Version: 0.2.999+git20170802-4 We believe that the bug you reported is fixed in the latest version of libglvnd, 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 875...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Timo Aaltonen (supplier of updated libglvnd 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, 12 Sep 2017 10:32:47 +0300 Source: libglvnd Binary: libglvnd-dev libglvnd-core-dev libglvnd0 libegl1 libgles2 libgl1 libglx0 libopengl0 Architecture: source Version: 0.2.999+git20170802-4 Distribution: unstable Urgency: medium Maintainer: Debian X Strike Force Changed-By: Timo Aaltonen Description: libegl1- Vendor neutral GL dispatch library -- EGL support libgl1 - Vendor neutral GL dispatch library -- legacy GL support libgles2 - Vendor neutral GL dispatch library -- GLES support libglvnd-core-dev - Vendor neutral GL dispatch library -- core development files libglvnd-dev - Vendor neutral GL dispatch library -- development files libglvnd0 - Vendor neutral GL dispatch library libglx0- Vendor neutral GL dispatch library -- GLX support libopengl0 - Vendor neutral GL dispatch library -- OpenGL support Closes: 875446 Changes: libglvnd (0.2.999+git20170802-4) unstable; urgency=medium . * control: libglvnd-dev Breaks/Replaces old libegl1-mesa-dev/libgl1- mesa-dev/libgles2-mesa-dev. (Closes: #875446) Checksums-Sha1: 22526568bbe6be9c911eb5db78a03437e31e17d1 2386 libglvnd_0.2.999+git20170802-4.dsc 1220b5ca7206bec0a5147880b7774e4829b14aad 22616 libglvnd_0.2.999+git20170802-4.diff.gz Checksums-Sha256: 8f81877c126b5b24432790f7432f48387b4658f865e1d55e375789b19adfa289 2386 libglvnd_0.2.999+git20170802-4.dsc 2b0403c37bd966029ead29fc1908feb08616efcddca6735fb32ba65f3d009845 22616 libglvnd_0.2.999+git20170802-4.diff.gz Files: b046173920d4cdd24668ab200628375c 2386 libs extra libglvnd_0.2.999+git20170802-4.dsc 96ccb7adfc75015ae430f515f11f7778 22616 libs extra libglvnd_0.2.999+git20170802-4.diff.gz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJZt45jAAoJEMtwMWWoiYTcPd0P/jByqX3im9pC6mmA5pBIgwED D9HDvo8KD3UQp3skJ+cf0rEmvxqyKiw3qY0emOMzkjeeh8mUoMRKzUvuArVV1342 egmL/9AQxjFkthYxNrz9RrbIp+jyQHb4c2AOCYSbNQwfadGxMVO5/U4rWFKIAWFO 4rJNWYjK+bYbnJx3tPecBu2b1d4dnwF3Y+UfrjbRA4WRiUiRnZ6feYLMO2IgbbaJ fl6qG9VJtQUHQmtEKhaorm8Xypzz8eR8BrP6lmKyv2kHOQyHccV4dMDyJrMKa+z4 CT4QPNWUoaJxcJYQAbycQ0VdtZ3HdGZ0RfuIURWC872ksE8WU9QVG4f3GaN0O2bD /CeO3gIZgI4DRnCBc3/w6hV3oLK74Esoxgt3cbxpATefNwFvshtujb0pG1w+gEM/ jqncTRqdODicSh3edzqJjTD8RL76R3oURC+KuJG3Www8DsPCpqL9uPv+0tXdYoUV Mrywhk90uaxtLb+HWMDV6snFZ5D7FIVZ07Ys6FG1/OvUOLDyBebufsNhtsyUbpwK UfmkpPzFTs24RSEYjIBdNods+wu0cZRE4bFcxZKU7KSnm8XUQWYBd6NKjtKEmD1q bxN1JFKZRbhLlyLa/xkclhsn5EO826TkX6yPeDndo0xwyZO+LECA/B+f0WMaERbN gDvZbNLP4Cst5v3N6P8R =jh58 -END PGP SIGNATURE End Message ---
Bug#873832: marked as done (suricata: missing libluajit-5.1-dev build dependency on mipsel)
Your message dated Tue, 12 Sep 2017 07:34:10 + with message-id and subject line Bug#873832: fixed in suricata 1:4.0.0-4 has caused the Debian Bug report #873832, regarding suricata: missing libluajit-5.1-dev build dependency on mipsel 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.) -- 873832: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873832 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: suricata Version: 1:4.0.0-3 Severity: serious https://buildd.debian.org/status/fetch.php?pkg=suricata&arch=mipsel&ver=1%3A4.0.0-3&stamp=1504119271&raw=0 ... checking for LUAJIT... no checking lualib.h usability... no checking lualib.h presence... no checking for lualib.h... no ERROR! libluajit headers not found, ... suricata (1:4.0.0-3) unstable; urgency=medium ... * [49ff3181] enable luajit on mipsel (Closes: #858545) ... Build-Depends: autotools-dev, ... libluajit-5.1-dev [i386 amd64 powerpc mips armel armhf], ... --- End Message --- --- Begin Message --- Source: suricata Source-Version: 1:4.0.0-4 We believe that the bug you reported is fixed in the latest version of suricata, 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 873...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Arturo Borrero Gonzalez (supplier of updated suricata 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: Fri, 08 Sep 2017 06:06:47 +0200 Source: suricata Binary: suricata suricata-oinkmaster Architecture: source amd64 all Version: 1:4.0.0-4 Distribution: unstable Urgency: medium Maintainer: Pierre Chifflier Changed-By: Arturo Borrero Gonzalez Description: suricata - Next Generation Intrusion Detection and Prevention Tool suricata-oinkmaster - Integration package between suricata and oinkmaster Closes: 873832 Changes: suricata (1:4.0.0-4) unstable; urgency=medium . * [93ee9030] d/control: enable libluajit-5.1-dev build-dep on mipsel (Closes: #873832) * [9527fe94] d/t/control: run suricata -u from the source tree Checksums-Sha1: ebd7b0d917c934ed2491966914d0d7c6f5315d48 2586 suricata_4.0.0-4.dsc 55e97b62939f478438f39026ada3e2d1ee6e5efb 11470130 suricata_4.0.0.orig.tar.gz 5bf8c15a6e5774b71ad7112f60dad3768a17ffa4 21096 suricata_4.0.0-4.debian.tar.xz 6c55f38d4a4b91b8cf08ff9fcfe95ca24f19371c 8287494 suricata-dbgsym_4.0.0-4_amd64.deb 0b9070ff03f4589d61dd53257dfd94966d300941 33286 suricata-oinkmaster_4.0.0-4_all.deb 17ae2c83906986fb897c09cf758201a9683a78c0 8727 suricata_4.0.0-4_amd64.buildinfo 2398b7a0207b31ff3163ea618596829224b99668 982204 suricata_4.0.0-4_amd64.deb Checksums-Sha256: 270510cbb5b150d78e05efaf439e20ef35c63e587fc8f792fb7fd4919a010d88 2586 suricata_4.0.0-4.dsc ffd24e2a9caf45a15339ef7efa5c09d685ee31d98be017b3674806386b177d46 11470130 suricata_4.0.0.orig.tar.gz 606bd7c1eaca711cf1a91041e06abeca4a6c37439aa05b1f0449fc41d0155da3 21096 suricata_4.0.0-4.debian.tar.xz eeab60529a3b602e767350636d5ec439f6d3215c5598006f56cda112d60de8f5 8287494 suricata-dbgsym_4.0.0-4_amd64.deb 704a55929da59da87ad938299d80101537e5701941c3e1e6e36b5a33b2469079 33286 suricata-oinkmaster_4.0.0-4_all.deb 7b71a907fba4224a6c35c2b35175b5e9953663afa2abcb7a4dd6ecfe67d6a776 8727 suricata_4.0.0-4_amd64.buildinfo a07beead73721bcc7222978e26204ccb3a5f78bdaa8296b7e8bbf5bf61875560 982204 suricata_4.0.0-4_amd64.deb Files: 7ec398f5220b839ab25552b72c2bdea1 2586 net optional suricata_4.0.0-4.dsc 950841ba29c8067afe44c563b6d45b62 11470130 net optional suricata_4.0.0.orig.tar.gz 491ed4ac87bc6c4ca3f427f10faf31f1 21096 net optional suricata_4.0.0-4.debian.tar.xz 8c8e9fd0d40f505dd40b1957116cb139 8287494 debug optional suricata-dbgsym_4.0.0-4_amd64.deb 140defb598ee450ba82563cfbbe3b95b 33286 net optional suricata-oinkmaster_4.0.0-4_all.deb f62141002a1c0c71deaa0628ebf6ace5 8727 net optional suricata_4.0.0-4_amd64.buildinfo 7da39b19ca4e016f28bfd01dfe036a42 982204 net optional suricata_4.0.0-4_amd64.deb -BEGIN PGP SIGNATURE- iQJGBAEBCgAwFiEE3ZhhqyPcMzOJLgepaOcTmB0VFfgFAlm3iHcSHGFydHVyb0Bk ZWJpYW4ub3JnAAoJEGjnE5gdFRX48nkQALEPvtTNeaKfvblrrB9ei3O2LWcyO77c WB32cvbZvDVNqHQ8DIDINT/bWEpa
