Bug#897477: libhugetlbfs: FTBFS: collect2: error: ld returned 1 exit status
Hi Lucas, Thanks for the report and apologies for not picking this earlier. On Wed, 2 May 2018 22:00:16 +0200 Lucas Nussbaum wrote: [...] > During a rebuild of all packages in sid, your package failed to build on > amd64. > > Relevant part (hopefully): > > /usr/bin/x86_64-linux-gnu-ld: unrecognized option '--hugetlbfs-link=B' > > /usr/bin/x86_64-linux-gnu-ld: use the --help option for usage information > > collect2: error: ld returned 1 exit status I am not sure what the issue was but I don't see this failure when building the package on sid. Can you confirm that the build no longer fails for you? Thanks, Punit
Bug#897767: marked as done (highwayhash: ftbfs with GCC-8)
Your message dated Mon, 23 Jul 2018 01:50:32 + with message-id and subject line Bug#897767: fixed in highwayhash 0~20180209-g14dedec-5 has caused the Debian Bug report #897767, regarding highwayhash: ftbfs with GCC-8 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.) -- 897767: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897767 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:highwayhash Version: 0~20180209-g14dedec-3 Severity: normal Tags: sid buster User: debian-...@lists.debian.org Usertags: ftbfs-gcc-8 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-8/g++-8, but succeeds to build with gcc-7/g++-7. The severity of this report will be raised before the buster release. The full build log can be found at: http://aws-logs.debian.net/2018/05/01/gcc8/highwayhash_0~20180209-g14dedec-3_unstable_gcc8.log.gz The last lines of the build log are at the end of this report. To build with GCC 8, either set CC=gcc-8 CXX=g++-8 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-8/porting_to.html [...] dpkg-gensymbols: warning: debian/libhighwayhash0/DEBIAN/symbols doesn't match completely debian/libhighwayhash0.symbols --- debian/libhighwayhash0.symbols (libhighwayhash0_0~20180209-g14dedec-3_amd64) +++ dpkg-gensymbolsJArbQP 2018-05-02 11:58:36.131189433 + @@ -14,8 +14,8 @@ SipTreeHash@Base 0~20180103-geeea446 SipTreeHashC@Base 0~20180103-geeea446 _ZN11highwayhash10TargetNameEj@Base 0~20170419-g1f4a24f - _ZN11highwayhash11ComputeHashINS_13SipHashStateTILi1ELi3EyRKNT_3KeyEPKcy@Base 0~20170419-g1f4a24f - _ZN11highwayhash11ComputeHashINS_13SipHashStateTILi2ELi4EyRKNT_3KeyEPKcy@Base 0~20170419-g1f4a24f +#MISSING: 0~20180209-g14dedec-3# _ZN11highwayhash11ComputeHashINS_13SipHashStateTILi1ELi3EyRKNT_3KeyEPKcy@Base 0~20170419-g1f4a24f +#MISSING: 0~20180209-g14dedec-3# _ZN11highwayhash11ComputeHashINS_13SipHashStateTILi2ELi4EyRKNT_3KeyEPKcy@Base 0~20170419-g1f4a24f _ZN11highwayhash12CountingSortIjEEvPT_S2_@Base 0~20170419-g1f4a24f _ZN11highwayhash12SipTreeHashTILm1ELm3EEEyRA4_KyPKcy@Base 0~20180103-geeea446 _ZN11highwayhash12SipTreeHashTILm2ELm4EEEyRA4_KyPKcy@Base 0~20180103-geeea446 @@ -40,6 +40,7 @@ _ZN11highwayhash23InvariantTicksPerSecondEv@Base 0~20180103-geeea446 _ZN11highwayhash23MedianAbsoluteDeviationIfEET_RKSt6vectorIS1_SaIS1_EES1_@Base 0~20170419-g1f4a24f _ZN11highwayhash3NowEv@Base 0~20170419-g1f4a24f + _ZN11highwayhash4ModeIjEET_PKS1_m@Base 0~20180209-g14dedec-3 _ZN11highwayhash5CpuidEjjPj@Base 0~20170419-g1f4a24f _ZN11highwayhash6ApicIdEv@Base 0~20170419-g1f4a24f _ZN11highwayhash6MedianIfEET_PSt6vectorIS1_SaIS1_EE@Base 0~20170419-g1f4a24f @@ -65,15 +66,17 @@ _ZNSt23mersenne_twister_engineImLm64ELm312ELm156ELm31ELm13043109905998158313ELm29ELm6148914691236517205ELm17ELm8202884508482404352ELm37ELm1873444759240704ELm43ELm6364136223846793005EEclEv@Base 0~20180209-g14dedec _ZNSt24uniform_int_distributionImEclISt20discard_block_engineISt26subtract_with_carry_engineImLm48ELm5ELm12EELm389ELm11mRT_RKNS0_10param_typeE@Base 0~20170419-g1f4a24f _ZNSt6vectorISt4pairIjiESaIS1_EE17_M_realloc_insertIJS1_EEEvN9__gnu_cxx17__normal_iteratorIPS1_S3_EEDpOT_@Base 0~20180103-geeea446 - _ZNSt6vectorIiSaIiEE17_M_realloc_insertIJiEEEvN9__gnu_cxx17__normal_iteratorIPiS1_EEDpOT_@Base 0~20180103-geeea446 +#MISSING: 0~20180209-g14dedec-3# _ZNSt6vectorIiSaIiEE17_M_realloc_insertIJiEEEvN9__gnu_cxx17__normal_iteratorIPiS1_EEDpOT_@Base 0~20180103-geeea446 + _ZNSt6vectorIjSaIjEE17_M_realloc_insertIJRKjEEEvN9__gnu_cxx17__normal_iteratorIPjS1_EEDpOT_@Base 0~20180209-g14dedec-3 + _ZNSt6vectorImSaImEE17_M_default_appendEm@Base 0~20180209-g14dedec-3 _ZNSt8_Rb_treeImSt4pairIKmSt6vectorIjSaIjEEESt10_Select1stIS5_ESt4lessImESaIS5_EE29_M_get_insert_hint_unique_posESt23_Rb_tree_const_iteratorIS5_ERS1_@Base 0~20170419-g1f4a24f
Bug#897843: marked as done (qtmpris: ftbfs with GCC-8)
Your message dated Mon, 23 Jul 2018 01:35:48 + with message-id and subject line Bug#897843: fixed in qtmpris 0.1.0-2 has caused the Debian Bug report #897843, regarding qtmpris: ftbfs with GCC-8 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.) -- 897843: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897843 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:qtmpris Version: 0.0.8-2 Severity: normal Tags: sid buster User: debian-...@lists.debian.org Usertags: ftbfs-gcc-8 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-8/g++-8, but succeeds to build with gcc-7/g++-7. The severity of this report will be raised before the buster release. The full build log can be found at: http://aws-logs.debian.net/2018/05/01/gcc8/qtmpris_0.0.8-2_unstable_gcc8.log.gz The last lines of the build log are at the end of this report. To build with GCC 8, either set CC=gcc-8 CXX=g++-8 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-8/porting_to.html [...] make[2]: Leaving directory '/<>/declarative' dh_install -a dh_installdocs -a dh_installchangelogs -a dh_perl -a dh_link -a dh_strip_nondeterminism -a dh_compress -a dh_fixperms -a debian/rules override_dh_missing make[1]: Entering directory '/<>' dh_missing --fail-missing make[1]: Leaving directory '/<>' dh_strip -a dh_makeshlibs -a dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see diff output below dpkg-gensymbols: warning: some symbols or patterns disappeared in the symbols file: see diff output below dpkg-gensymbols: warning: debian/libmpris-qt5-1/DEBIAN/symbols doesn't match completely debian/libmpris-qt5-1.symbols --- debian/libmpris-qt5-1.symbols (libmpris-qt5-1_0.0.8-2_amd64) +++ dpkg-gensymbolsRIn9ld 2018-05-02 11:57:18.787235216 + @@ -1,6 +1,8 @@ libmpris-qt5.so.1 libmpris-qt5-1 #MINVER# _ZN10QByteArrayD1Ev@Base 0.0.8 _ZN10QByteArrayD2Ev@Base 0.0.8 + _ZN10QDBusReplyI11QStringListED1Ev@Base 0.0.8-2 + _ZN10QDBusReplyI11QStringListED2Ev@Base 0.0.8-2 _ZN11MprisPlayer10setCanPlayEb@Base 0.0.8 _ZN11MprisPlayer10setCanQuitEb@Base 0.0.8 _ZN11MprisPlayer10setCanSeekEb@Base 0.0.8 @@ -289,7 +291,7 @@ _ZN4QMapI7QString8QVariantEC2ERKS2_@Base 0.0.8 _ZN4QMapI7QString8QVariantED1Ev@Base 0.0.8 _ZN4QMapI7QString8QVariantED2Ev@Base 0.0.8 - _ZN4QMapI7QString8QVariantEixERKS0_@Base 0.0.8 +#MISSING: 0.0.8-2# _ZN4QMapI7QString8QVariantEixERKS0_@Base 0.0.8 _ZN5Mpris11api_factoryEP10QQmlEngineP9QJSEngine@Base 0.0.8 _ZN5Mpris11qt_metacallEN11QMetaObject4CallEiPPv@Base 0.0.8 _ZN5Mpris11qt_metacastEPKc@Base 0.0.8 @@ -327,6 +329,8 @@ _ZN6QDebuglsEPKc@Base 0.0.8 _ZN7QStringD1Ev@Base 0.0.8 _ZN7QStringD2Ev@Base 0.0.8 + _ZN8QMapDataI7QString8QVariantE10createNodeERKS0_RKS1_P8QMapNodeIS0_S1_Eb@Base 0.0.8-2 + _ZN8QMapDataI7QString8QVariantE7destroyEv@Base 0.0.8-2 _ZN8QMapNodeI7QString8QVariantE14destroySubTreeEv@Base 0.0.8 _ZN9QtPrivate11QSlotObjectIM12MprisManagerFvvENS_4ListIJEEEvE4implEiPNS_15QSlotObjectBaseEP7QObjectPPvPb@Base 0.0.8 _ZN9QtPrivate11QSlotObjectIM12MprisManagerFvxENS_4ListIJxEEEvE4implEiPNS_15QSlotObjectBaseEP7QObjectPPvPb@Base 0.0.8 dh_makeshlibs: failing due to earlier errors make: *** [debian/rules:11: binary-arch] Error 2 dpkg-buildpackage: error: fakeroot debian/rules binary-arch subprocess returned exit status 2 --- End Message --- --- Begin Message --- Source: qtmpris Source-Version: 0.1.0-2 We believe that the bug you reported is fixed in the latest version of qtmpris, 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 897...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Yanhao Mo (supplier of updated qtmpris package) (This message was generated
Bug#897763: marked as done (gsettings-qt: ftbfs with GCC-8)
Your message dated Mon, 23 Jul 2018 01:06:10 + with message-id and subject line Bug#897763: fixed in gsettings-qt 0.1+17.10.20170824-5 has caused the Debian Bug report #897763, regarding gsettings-qt: ftbfs with GCC-8 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.) -- 897763: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897763 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:gsettings-qt Version: 0.1+17.10.20170824-3 Severity: normal Tags: sid buster User: debian-...@lists.debian.org Usertags: ftbfs-gcc-8 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-8/g++-8, but succeeds to build with gcc-7/g++-7. The severity of this report will be raised before the buster release. The full build log can be found at: http://aws-logs.debian.net/2018/05/01/gcc8/gsettings-qt_0.1+17.10.20170824-3_unstable_gcc8.log.gz The last lines of the build log are at the end of this report. To build with GCC 8, either set CC=gcc-8 CXX=g++-8 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-8/porting_to.html [...] make[2]: Entering directory '/<>/gsettings-qt-0.1+17.10.20170824/tests' /usr/lib/qt5/bin/qmake -install qinstall -exe cpptest /<>/gsettings-qt-0.1+17.10.20170824/debian/tmp/usr/tests/cpptest/cpptest make[2]: Leaving directory '/<>/gsettings-qt-0.1+17.10.20170824/tests' make[2]: Entering directory '/<>/gsettings-qt-0.1+17.10.20170824/tests' : /<>/gsettings-qt-0.1+17.10.20170824/debian/tmp/usr/tests/cpptest/cpptest make[2]: Leaving directory '/<>/gsettings-qt-0.1+17.10.20170824/tests' debian/rules override_dh_install make[1]: Entering directory '/<>/gsettings-qt-0.1+17.10.20170824' rm -rf debian/*/usr/tests dh_install make[1]: Leaving directory '/<>/gsettings-qt-0.1+17.10.20170824' dh_installdocs -a dh_installchangelogs -a dh_installexamples -a dh_perl -a dh_link -a dh_strip_nondeterminism -a dh_compress -a dh_fixperms -a debian/rules override_dh_missing make[1]: Entering directory '/<>/gsettings-qt-0.1+17.10.20170824' dh_missing --fail-missing make[1]: Leaving directory '/<>/gsettings-qt-0.1+17.10.20170824' dh_strip -a debian/rules override_dh_makeshlibs make[1]: Entering directory '/<>/gsettings-qt-0.1+17.10.20170824' # passed to dpkg-gensymbols dh_makeshlibs -- -c4 dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see diff output below dpkg-gensymbols: warning: debian/libgsettings-qt1/DEBIAN/symbols doesn't match completely debian/libgsettings-qt1.symbols --- debian/libgsettings-qt1.symbols (libgsettings-qt1_0.1+17.10.20170824-3_amd64) +++ dpkg-gensymbols12WsxT 2018-05-02 11:59:15.502432813 + @@ -24,10 +24,11 @@ (c++|optional=templinst)"QList::~QList()@Base" 0.1+14.04.20140408 (c++|optional=templinst)"QMap::QMap(QMap const&)@Base" 0.1+16.04.20170729 (c++)"QMap::~QMap()@Base" 0.1+14.10.20140801.1 - (c++|optional=templinst)"QMapData::destroy()@Base" 0.1+16.04.20160329 +#MISSING: 0.1+17.10.20170824-3# (c++|optional=templinst)"QMapData::destroy()@Base" 0.1+16.04.20160329 (c++)"QMapNode::copy(QMapData*) const@Base" 0.1+14.10.20140801.1 (c++)"QMapNode::destroySubTree()@Base" 0.1+14.10.20140801.1 (c++)"QString::~QString()@Base" 0.1+14.04.20140408 + _ZN4QMapI7QString8QVariantE13detach_helperEv@Base 0.1+17.10.20170824-3 (c++)"qconf_types_collect_from_variant(_GVariantType const*, QVariant const&)@Base" 0.1+14.04.20140408 (c++)"qconf_types_convert(_GVariantType const*)@Base" 0.1+14.04.20140408 (c++)"qconf_types_to_qvariant(_GVariant*)@Base" 0.1+14.04.20140408 dh_makeshlibs: failing due to earlier errors make[1]: *** [debian/rules:29: override_dh_makeshlibs] Error 2 make[1]: Leaving directory '/<>/gsettings-qt-0.1+17.10.20170824' make: *** [debian/rules:32: binary-arch] Error 2 dpkg-buildpackage: error: fakeroot debian/rules binary-arch subprocess returned exit status 2 --- End Message --- --- Begin Message --- Source: gsettings-qt Source-Version: 0.1+17.10.20170824-5 We believe that the
Bug#902631: devscripts: CI fails in unstable due to Python 3.7
On Sun, Jul 22, 2018 at 8:31 PM Mattia Rizzolo wrote: > > On Sun, Jul 22, 2018 at 03:52:04PM -0400, Sandro Tosi wrote: > > thanks for ignoring the next paragraph in that email, so let me re-add it > > here: > > I didn't ignore it, I explicitly picked on your first, fairly taunting, > and inappropriately passive-aggressive sentence (like this one). good good > > since astroid/pylint only support python 3.4+, it is not as simple as > > package the new version and upload it; i'm not even (yet) sure buster > > should have 2.0 but maybe it should to 1.9 > > This is a fairly common situation for distributors. > > Did you also evaluate the feasibility and practicality of working on a > patch to introduce py3.7 compatibility to the current 1.6.5? no, i didnt look into it myself: upstream dismissed the forwarded bug saying to upgrade to 2.0 to get 3.7 support. if someone wants to try and dedicate time to that effort, that'd be welcome and please attach a patch here when ready. -- Sandro "morph" Tosi My website: http://sandrotosi.me/ Me at Debian: http://wiki.debian.org/SandroTosi G+: https://plus.google.com/u/0/+SandroTosi
Bug#902631: devscripts: CI fails in unstable due to Python 3.7
On Sun, Jul 22, 2018 at 03:52:04PM -0400, Sandro Tosi wrote: > thanks for ignoring the next paragraph in that email, so let me re-add it > here: I didn't ignore it, I explicitly picked on your first, fairly taunting, and inappropriately passive-aggressive sentence (like this one). > since astroid/pylint only support python 3.4+, it is not as simple as > package the new version and upload it; i'm not even (yet) sure buster > should have 2.0 but maybe it should to 1.9 This is a fairly common situation for distributors. Did you also evaluate the feasibility and practicality of working on a patch to introduce py3.7 compatibility to the current 1.6.5? -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature
Bug#862678: Switch from network-manager-dev to libnm-dev
Thanks Gregor. I'll upload a new version with this patch. On Fri, Jul 20, 2018 at 8:09 PM gregor herrmann wrote: > Control: tag -1 + patch > > On Thu, 19 Apr 2018 18:08:40 +, Ari Pollak wrote: > > > Sorry, I haven't had time to do anything about it yet and I won't be able > > to look at it for the next month or so. > > As this is the last blocker for the perl 5.28 transition, I looked > into this bug now, and I converted Michael's recipe into a debdiff > (attached). > > Michael: can you take a look if you spot anything? > Ari: Do you have time to upload and fix this bug in the near future? > If not I'm happy to help with an NMU. > > > Cheers, > gregor > > -- > .''`. https://info.comodo.priv.at -- Debian Developer > https://www.debian.org > : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D 85FA BB3A 6801 8649 > AA06 > `. `' Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation > Europe >`- NP: Willi Resetarits + Stubnblues: sag ma nix >
Bug#862678: marked as done (Switch from network-manager-dev to libnm-dev)
Your message dated Mon, 23 Jul 2018 00:04:15 + with message-id and subject line Bug#862678: fixed in pidgin 2.13.0-2 has caused the Debian Bug report #862678, regarding Switch from network-manager-dev to libnm-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.) -- 862678: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=862678 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: pidgin Version: 2.12.0-1 Severity: normal Tags: patch User: pkg-utopia-maintain...@lists.alioth.debian.org Usertags: libnm libnm-glib/libnm-util have been declared as deprecated by upstream and I'm in the process of getting users of that library updated to libnm. Your package declares a Build-Depends on network-manager-dev. After further investigation, it seems this dependency is actually no longer needed [1] and can be safely dropped. Please consider including the attached patch in your next upload. Regards, Michael [1] https://anonscm.debian.org/cgit/collab-maint/pidgin.git/commit/debian/patches?id=d8dc94bfa482761313f27be901a27be192fc1d10 -- System Information: Debian Release: 9.0 APT prefers unstable APT policy: (500, 'unstable'), (200, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-3-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- no debconf information diff --git a/debian/control b/debian/control index 97779a3..6d9313e 100644 --- a/debian/control +++ b/debian/control @@ -12,7 +12,6 @@ Build-Depends: cdbs, debhelper (>= 9), intltool, libgadu-dev (>= 1:1.12.0-5), xsltproc, doxygen, libfarstream-0.2-dev, libgstreamer-plugins-base1.0-dev, - network-manager-dev (>= 0.9.0) [linux-any], libsqlite3-dev (>= 3.3), libidn11-dev, ca-certificates, dh-autoreconf Standards-Version: 3.9.8 --- End Message --- --- Begin Message --- Source: pidgin Source-Version: 2.13.0-2 We believe that the bug you reported is fixed in the latest version of pidgin, 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 862...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ari Pollak (supplier of updated pidgin 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: Sat, 21 Jul 2018 01:54:18 +0200 Source: pidgin Binary: libpurple0 pidgin pidgin-data pidgin-dev finch finch-dev libpurple-dev libpurple-bin Architecture: source amd64 all Version: 2.13.0-2 Distribution: unstable Urgency: low Maintainer: Ari Pollak Changed-By: Ari Pollak Description: finch - text-based multi-protocol instant messaging client finch-dev - text-based multi-protocol instant messaging client - development libpurple-bin - multi-protocol instant messaging library - extra utilities libpurple-dev - multi-protocol instant messaging library - development files libpurple0 - multi-protocol instant messaging library pidgin - graphical multi-protocol instant messaging client pidgin-data - multi-protocol instant messaging client - data files pidgin-dev - multi-protocol instant messaging client - development files Closes: 862678 Changes: pidgin (2.13.0-2) unstable; urgency=low . [ gregor herrmann ] * Fix "Switch from network-manager-dev to libnm-dev": - update build dependency - add patch for configure.ac and a constant in libpurple/network.c Thanks to Michael Biebl for the recipe to fix this bug. (Closes: #862678) Checksums-Sha1: 99d9e529ea16d8d0470ecf336ee004455c34337c 2744 pidgin_2.13.0-2.dsc 3dc71d68433fa097db90feb11d406c7e66aab138 61196 pidgin_2.13.0-2.debian.tar.xz 84c852250a50aec03c84828cd52940cfb0346348 853776 finch-dbgsym_2.13.0-2_amd64.deb 3b6b0b4ed95422827b3a714df9bb0bcb9c9f1a14 145664 finch-dev_2.13.0-2_all.deb 7073c6f970926b163a67f38f8dc5f0c06d474577 312988 finch_2.13.0-2_amd64.deb 8fd1e9e01b8cd77e1a9e1b5d087f9ab5e153bd6d 124640 libpurple-bin_2.13.0-2_all.deb 30140735d54cadb7231a8f27586e7f6dd9d64e12 260152 libpurple-dev_2.13.0-2_all.deb 72ae32ebe64652d136673e3c590a54604d4e46bc 5359752 libpurple0-dbgsym_2.13.0-2_amd64.deb
Bug#903412: marked as done (asterisk: FTBFS in buster/sid (dh_installdocs: Cannot find "README"))
Your message dated Sun, 22 Jul 2018 22:04:05 + with message-id and subject line Bug#903412: fixed in asterisk 1:13.22.0~dfsg-1 has caused the Debian Bug report #903412, regarding asterisk: FTBFS in buster/sid (dh_installdocs: Cannot find "README") 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.) -- 903412: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903412 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:asterisk Version: 1:13.20.0~dfsg-1 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in buster but it failed: [...] debian/rules build-indep dh build-indep dh_update_autotools_config -i debian/rules override_dh_autoreconf make[1]: Entering directory '/<>' if [ ! -r configure.debian_sav ]; then cp -a configure configure.debian_sav; fi [ -f .version.debian_sav ] || cp -a .version .version.debian_sav echo 13.20.0~dfsg-1 > .version dh_autoreconf -- ./bootstrap.sh Generating the configure script for Asterisk ... Generating the configure script for menuselect ... make[1]: Leaving directory '/<>' debian/rules override_dh_auto_configure make[1]: Entering directory '/<>' [... snipped ...] Installing file configs/samples/say.conf.sample Installing file configs/samples/sip.conf.sample Installing file configs/samples/sip_notify.conf.sample Installing file configs/samples/skinny.conf.sample Installing file configs/samples/sla.conf.sample Installing file configs/samples/smdi.conf.sample Installing file configs/samples/sorcery.conf.sample Installing file configs/samples/ss7.timers.sample Installing file configs/samples/stasis.conf.sample Installing file configs/samples/statsd.conf.sample Installing file configs/samples/test_sorcery.conf.sample Installing file configs/samples/udptl.conf.sample Installing file configs/samples/unistim.conf.sample Installing file configs/samples/users.conf.sample Installing file configs/samples/voicemail.conf.sample Installing file configs/samples/vpb.conf.sample Installing file configs/samples/xmpp.conf.sample Updating asterisk.conf /usr/bin/install -c -d "/<>/debian/tmp/var/spool/asterisk/voicemail/default/1234/INBOX" build_tools/make_sample_voicemail "/<>/debian/tmp//usr/share/asterisk" "/<>/debian/tmp//var/spool/asterisk" Installing file phoneprov/-directory.xml Installing file phoneprov/-phone.cfg Installing file phoneprov/.cfg Installing file phoneprov/polycom.xml Installing file phoneprov/polycom_line.xml Installing file phoneprov/snom-mac.xml make[2]: Leaving directory '/<>' cp -a configs /<>/debian/tmp/usr/share/asterisk/conf rm -f -f /<>/debian/tmp/etc/asterisk/dundi.conf /<>/debian/tmp/etc/asterisk/mgcp.conf /<>/debian/tmp/etc/asterisk/skinny.conf /<>/debian/tmp/etc/asterisk/unistim.conf mkdir -p /<>/debian/tmp/usr/bin/ mkdir -p /<>/debian/tmp/usr/share/man/man1 mkdir -p /<>/debian/tmp/usr/share/dahdi/span_config.d cp -a debian/asterisk-config-custom /<>/debian/tmp/usr/bin/ cp -a debian/asterisk-config-custom /<>/debian/tmp/usr/share/man/man1/ cp -a debian/50-asterisk /<>/debian/tmp/usr/share/dahdi/span_config.d/ rm -f -f /<>/debian/tmp/usr/sbin/conf2ael rm -f -f /<>/debian/tmp/usr/sbin/muted rm -f -f /<>/debian/tmp/usr/sbin/streamplayer rm -f -f /<>/debian/tmp/usr/sbin/stereorize rm -f -f /<>/debian/tmp/usr/sbin/hashtest* rm -f -f /<>/debian/tmp/usr/sbin/refcounter make[1]: Leaving directory '/<>' dh_install -i dh_installdocs -i dh_installdocs: Cannot find (any matches for) "README" (tried in .) debian/rules:14: recipe for target 'binary-indep' failed make: *** [binary-indep] Error 2 dpkg-buildpackage: error: fakeroot debian/rules binary-indep subprocess returned exit status 2 The build was made with "dpkg-buildpackage -A" in my autobuilder. Most probably, it also fails here in reproducible builds: https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/asterisk.html [ Note: There has been a recent change in debhelper behaviour, the current behaviour is the intended one. See Bug #903133 for details ]. Thanks. --- End Message --- --- Begin Message --- Source: asterisk Source-Version: 1:13.22.0~dfsg-1 We believe that the bug you reported is fixed in the latest version of asterisk, 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
Bug#902631: devscripts: CI fails in unstable due to Python 3.7
> What do you mean with "support"? Astroid 2.0 is working properly with py3.7 > according to upstream. i mean that pylint/astroid 2.0 do not work with python 2 at all, but only with python 3.4 onwards (so yes, also 3.7 in that regards). -- Sandro "morph" Tosi My website: http://sandrotosi.me/ Me at Debian: http://wiki.debian.org/SandroTosi G+: https://plus.google.com/u/0/+SandroTosi
Bug#902631: devscripts: CI fails in unstable due to Python 3.7
> Upstream README seems to indicate that there is no release that supports > *both* python 2.7 and 3.7 i know, that's exactly my point > so this is not a choice between 2.0 and 1.9. well it is: it can be decided to ignore the 2.x branch and stick with 1.9 for buster (which support python 2 and python 3 up to 3.6) and not build astroid/pylint for 3.7 which possibly wont be the default py3k in buster (but it's hard to tell as common developers dont get much insight in the decisional process) > More likely, two source packages are required for buster. Alternatively one of i'm not really a fan of keeping 2 packages sets around > Python 2 / Python 3 must be dropped from pylint (presumably Python 2). If > these are the options, which are you intending to follow? i dont know, that's what's holding up a resolution for this bug! on one hand we still want to support python 2 in buster, so that's a compelling reason to keep python 2 support in pylint, OTOH we want to introduce 3.7 as (at least) a supported version, and the only way to make pylint available for 3.7 is to drop entirely support for python2. few other project i maintain are planning on released a py3k-only version, so maybe that's the direction to go with such modules? > On Sunday, 22 July 2018 15:52:04 AEST Sandro Tosi wrote: > > thanks for ignoring the next paragraph in that email, so let me re-add it > > here: > > > > ``` > > since astroid/pylint only support python 3.4+, it is not as simple as > > package the new version and upload it; i'm not even (yet) sure buster > > should have 2.0 but maybe it should to 1.9 > > ``` > > No-one is ignoring that statement, just hoping that there is progress towards > a solution rather than statements of what the problem is. We have all read the until your email, there werent any solutions proposed by external parties, so thanks for that, i think we should still understand how to approach it in the right way. > bug log and know the problem. You've indicated that you don't want help, but > not what the timeline to a fix is. If time is a problem to deal with RC bugs, > perhaps you'd be happy for team mates in PAPT to deal with this? that's correct: i dont need help to prepare a trivial patch to update astroid/pylint to the latest version, that's something anyone can do; what i'm concerned here is what approach to follow for packages dropping support for python releases Debian still cares to support. -- Sandro "morph" Tosi My website: http://sandrotosi.me/ Me at Debian: http://wiki.debian.org/SandroTosi G+: https://plus.google.com/u/0/+SandroTosi
Bug#902631: devscripts: CI fails in unstable due to Python 3.7
Le 22 juillet 2018 21:52:04 GMT+02:00, Sandro Tosi a écrit : >On Sat, Jul 21, 2018 at 6:58 AM Mattia Rizzolo >wrote: >> >> On Tue, Jul 17, 2018 at 03:06:14PM -0400, Sandro Tosi wrote: >> > no need, i can upgrade the package myself when needed, but thanks >for the offer. >> >> Then can you pretty please do it? It is neeeded. > >thanks for ignoring the next paragraph in that email, so let me re-add >it here: > >``` >since astroid/pylint only support python 3.4+, it is not as simple as >package the new version and upload it; i'm not even (yet) sure buster >should have 2.0 but maybe it should to 1.9 >``` What do you mean with "support"? Astroid 2.0 is working properly with py3.7 according to upstream. -- PEB
Bug#903767: Bug#903800: 4.9.110-1 Xen PV boot workaround
The package is available via stretch-proposed-updates. Just add that one to your sources.list until the next point release or linux security update. HTH, Sven Am 22. Juli 2018 22:48:35 MESZ schrieb Jered Floyd : > >It appears that this ticket has been closed, noting a fix in >linux-4.9.110-2 (source pkg). Will this replace the current >linux-image-4.9.0-7-amd64 in stretch soon? It's currently making >stretch unusable with Xen. > >--Jered > >- On Jul 17, 2018, at 6:23 AM, Hans van Kranenburg h...@knorrie.org >wrote: > >> On 07/17/2018 12:39 AM, Benoît Tonnerre wrote: >>> Hi, >>> >>> I tested this workaround : I confirm that it works on Xen host, but >not >>> on Xen guest. >>> If you try to start a vm with latest kernel i.e. theses parameters >in >>> cfg file : >>> >>> # >>> # Kernel + memory size >>> # >>> kernel = '/boot/vmlinuz-4.9.0-7-amd64' >>> extra = 'elevator=noop' >>> ramdisk = '/boot/initrd.img-4.9.0-7-amd64' >>> >>> The VM crash in loop with kernel error : >>> >>> [...] >>> >>> Did I miss something ? >> >> Yes, the pti=off needs to go in your extra line: >> >> extra = 'elevator=noop pti=off' >> >> Hans > >-- >To unsubscribe, send mail to 903800-unsubscr...@bugs.debian.org.
Bug#896797: marked as done (botch: missing build dependency on dh-python)
Your message dated Sun, 22 Jul 2018 21:19:34 + with message-id and subject line Bug#896797: fixed in botch 0.21-6 has caused the Debian Bug report #896797, regarding botch: missing build dependency on dh-python 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.) -- 896797: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896797 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: botch Version: 0.21-5 Severity: serious https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/botch.html ... fakeroot debian/rules clean dh clean --with python3,ocaml dh: unable to load addon python3: Can't locate Debian/Debhelper/Sequence/python3.pm in @INC (you may need to install the Debian::Debhelper::Sequence::python3 module) (@INC contains: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.26.2 /usr/local/share/perl/5.26.2 /usr/lib/x86_64-linux-gnu/perl5/5.26 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.26 /usr/share/perl/5.26 /usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base) at (eval 7) line 1. BEGIN failed--compilation aborted at (eval 7) line 1. make: *** [debian/rules:7: clean] Error 2 --- End Message --- --- Begin Message --- Source: botch Source-Version: 0.21-6 We believe that the bug you reported is fixed in the latest version of botch, 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 896...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Johannes 'josch' Schauer (supplier of updated botch 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, 22 Jul 2018 19:07:41 +0200 Source: botch Binary: botch botch-doc Architecture: source Version: 0.21-6 Distribution: unstable Urgency: medium Maintainer: Johannes 'josch' Schauer Changed-By: Johannes 'josch' Schauer Description: botch - tools to create and analyse dependency graphs botch-doc - Bootstrapping helper - documentation Closes: 890029 896797 903564 Changes: botch (0.21-6) unstable; urgency=medium . * debian/control: add Build-Depends on dh-python (closes: #896797) * Define undefined parameters in shell scripts (closes: #903564) * Migrate to networkx 2.0 * update for graphviz 2.40.1 (closes: #890029) * Fix for changed version provides handling of dose3 5.0.1-9 * tools/graph-difference.py: allow comparison of arbitrary input graphs * Rename ma_interpreter.pkggraph to ma_interpreter.xml so that it is checked using botch-graph-difference instead of diff * debian/control: fix my name * bump dh compat level to 11 * debian/copyright: secure source format uri Checksums-Sha1: 551dc8f61095be7be5c2e8c0360262aa4d52d269 2837 botch_0.21-6.dsc 725527c7b081a54ffcf50f4e09aff9166003fe1e 2473168 botch_0.21-6.debian.tar.xz Checksums-Sha256: 5080295ea0d10735ae6dfeca862296e391eb1e98b78f0598d417390729b8ea43 2837 botch_0.21-6.dsc cadd2cfc410522f3e2e98608a951d8ca9ebd2d16bcf7ab14e44549a646b1236a 2473168 botch_0.21-6.debian.tar.xz Files: 56bd3417b7ac892a73ac9fc8e0ab9bce 2837 utils optional botch_0.21-6.dsc 62dd4e667544ca1374da3f4175c38b7e 2473168 utils optional botch_0.21-6.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEElFhU6KL81LF4wVq58sulx4+9g+EFAltU8R0ACgkQ8sulx4+9 g+EktQ//bYSpygMroTXwNhGnkwL+V7PK9RiEFTwMlQF7gIea8Wq9bVgSqGpxPprt qpgHCMPsfbhEyDt6IZj+VVtyafnNrzU6nYiAI6r4PaowMUR7Yojnw+HIW+MDRrGy VPheePjEq6TY4NjWlgbw8ilfqa6/hqglOPR77V+1juIv8SKqvFs0BJSXk0QbkagX Ly+CgKaitAm3nNFpQQn1+crvHue97WZ5qz6nIgxyrxbwfnGptgWvr6SUjDeEexcC 5Ci50/drYbtkayF+0ozFMWBK0Ms2PVq2xqeHLOH3QMjC3e7ZZQF5AR4DkZNGLR8L 8MTAFlpVqhhGXcLi2MV8uOOkyIRySaqSbc/xmGwxzvaFVNAY69wh/vmQAt/COqXD 4Ggixd07LKtHDFmUM6S9fdnZb2pXDdZyVuS1krvm7P4dQw40GSNrjzu2ulLRoEl0 rafi9QC2tVEDi/KCL2w1oOpZTsSgXc4wcggtqGCdhzjKulJhdYl04qWYh5OK78/h v4TIanr0wg5xnE1frzF8mFxBaWwqs9HP+zxlKUx9U3Gr3mwjRnJzPUHbceUJaReR xJg7R0EGhChDtYEbAhD9JwxAwAgw2+rnEIU6gXNX9S3Agu8sATRyQNRt8UOwpcmA Cw3yh2vjrTYyfDqJtS5VX12UnYm1wn/UwgBC4JpIiUkt2b5/yo0= =Oek1 -END PGP SIGNATURE End Message ---
Bug#897714: marked as done (bzrtp: ftbfs with GCC-8)
Your message dated Sun, 22 Jul 2018 21:03:49 +
with message-id
and subject line Bug#897714: fixed in bzrtp 1.0.6-3
has caused the Debian Bug report #897714,
regarding bzrtp: ftbfs with GCC-8
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.)
--
897714: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897714
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:bzrtp
Version: 1.0.6-2
Severity: normal
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-8
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-8/g++-8, but succeeds to build with gcc-7/g++-7. The
severity of this report will be raised before the buster release.
The full build log can be found at:
http://aws-logs.debian.net/2018/05/01/gcc8/bzrtp_1.0.6-2_unstable_gcc8.log.gz
The last lines of the build log are at the end of this report.
To build with GCC 8, either set CC=gcc-8 CXX=g++-8 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-8/porting_to.html
[...]
^
/<>/src/stateMachine.c: In function 'bzrtp_deriveKeysFromS0':
/<>/src/stateMachine.c:2057:234: error: cast between incompatible
function types from 'void (*)(const uint8_t *, size_t, const uint8_t *,
size_t, uint8_t, uint8_t *)' {aka 'void (*)(const unsigned char *, long
unsigned int, const unsigned char *, long unsigned int, unsigned char,
unsigned char *)'} to 'void (*)(uint8_t *, uint8_t, uint8_t *, uint32_t,
uint8_t, uint8_t *)' {aka 'void (*)(unsigned char *, unsigned char, unsigned
char *, unsigned int, unsigned char, unsigned char *)'}
[-Werror=cast-function-type]
retval = bzrtp_keyDerivationFunction(zrtpChannelContext->s0,
zrtpChannelContext->hashLength, (uint8_t *)"Initiator HMAC key", 18,
zrtpChannelContext->KDFContext, zrtpChannelContext->KDFContextLength,
zrtpChannelContext->hashLength, (void (*)(uint8_t *, uint8_t, uint8_t *,
uint32_t, uint8_t, uint8_t *))zrtpChannelContext->hmacFunction,
zrtpChannelContext->mackeyi);
^
/<>/src/stateMachine.c:2059:235: error: cast between incompatible
function types from 'void (*)(const uint8_t *, size_t, const uint8_t *,
size_t, uint8_t, uint8_t *)' {aka 'void (*)(const unsigned char *, long
unsigned int, const unsigned char *, long unsigned int, unsigned char,
unsigned char *)'} to 'void (*)(uint8_t *, uint8_t, uint8_t *, uint32_t,
uint8_t, uint8_t *)' {aka 'void (*)(unsigned char *, unsigned char, unsigned
char *, unsigned int, unsigned char, unsigned char *)'}
[-Werror=cast-function-type]
retval += bzrtp_keyDerivationFunction(zrtpChannelContext->s0,
zrtpChannelContext->hashLength, (uint8_t *)"Responder HMAC key", 18,
zrtpChannelContext->KDFContext, zrtpChannelContext->KDFContextLength,
zrtpChannelContext->hashLength, (void (*)(uint8_t *, uint8_t, uint8_t *,
uint32_t, uint8_t, uint8_t *))zrtpChannelContext->hmacFunction,
zrtpChannelContext->mackeyr);
^
/<>/src/stateMachine.c:2061:240: error: cast between incompatible
function types from 'void (*)(const uint8_t *, size_t, const uint8_t *,
size_t, uint8_t, uint8_t *)' {aka 'void (*)(const unsigned char *, long
unsigned int, const unsigned char *, long unsigned int, unsigned char,
unsigned char *)'} to 'void (*)(uint8_t *, uint8_t, uint8_t *, uint32_t,
uint8_t, uint8_t *)' {aka 'void (*)(unsigned char *, unsigned char, unsigned
char *, unsigned int, unsigned char, unsigned char *)'}
[-Werror=cast-function-type]
retval += bzrtp_keyDerivationFunction(zrtpChannelContext->s0,
Processed: tagging 875035, tagging 897792
Processing commands for cont...@bugs.debian.org: > tags 875035 + pending Bug #875035 [src:libqaccessibilityclient] [libqaccessibilityclient] Future Qt4 removal from Buster Added tag(s) pending. > tags 897792 + pending Bug #897792 [src:libqaccessibilityclient] libqaccessibilityclient: ftbfs with GCC-8 Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 875035: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875035 897792: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897792 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#903607: pjproject: FTBFS due to d-devlibdeps errors
Processing control commands: > severity -1 important Bug #903607 [src:pjproject] pjproject: FTBFS due to d-devlibdeps errors Severity set to 'important' from 'serious' -- 903607: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903607 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#903607: pjproject: FTBFS due to d-devlibdeps errors
Control: severity -1 important > I cannot reproduce this locally (using sbuild) and -3 just uploaded > built fine on the autobuilders. Downgrading severity as it has built fine on all architectures, feel free to reopen/upgrade if you still see this. Bernhard
Bug#903800: 4.9.110-1 Xen PV boot workaround
It appears that this ticket has been closed, noting a fix in linux-4.9.110-2 (source pkg). Will this replace the current linux-image-4.9.0-7-amd64 in stretch soon? It's currently making stretch unusable with Xen. --Jered - On Jul 17, 2018, at 6:23 AM, Hans van Kranenburg h...@knorrie.org wrote: > On 07/17/2018 12:39 AM, Benoît Tonnerre wrote: >> Hi, >> >> I tested this workaround : I confirm that it works on Xen host, but not >> on Xen guest. >> If you try to start a vm with latest kernel i.e. theses parameters in >> cfg file : >> >> # >> # Kernel + memory size >> # >> kernel = '/boot/vmlinuz-4.9.0-7-amd64' >> extra = 'elevator=noop' >> ramdisk = '/boot/initrd.img-4.9.0-7-amd64' >> >> The VM crash in loop with kernel error : >> >> [...] >> >> Did I miss something ? > > Yes, the pti=off needs to go in your extra line: > > extra = 'elevator=noop pti=off' > > Hans
Bug#881205: marked as done (backintime: CVE-2017-16667: shell injection in notify-send)
Your message dated Sun, 22 Jul 2018 20:35:21 +
with message-id
and subject line Bug#881205: fixed in backintime 1.1.24-0.1
has caused the Debian Bug report #881205,
regarding backintime: CVE-2017-16667: shell injection in notify-send
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.)
--
881205: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881205
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: backintime
Version: 1.1.12-2
Severity: grave
Tags: patch security upstream
Forwarded: https://github.com/bit-team/backintime/issues/834
Hi,
the following vulnerability was published for backintime.
CVE-2017-16667[0]:
| backintime (aka Back in Time) before 1.1.24 did improper
| escaping/quoting of file paths used as arguments to the 'notify-send'
| command, leading to some parts of file paths being executed as shell
| commands within an os.system call in qt4/plugins/notifyplugin.py. This
| could allow an attacker to craft an unreadable file with a specific
| name to run arbitrary shell commands.
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-16667
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-16667
[1] https://github.com/bit-team/backintime/issues/834
[2]
https://github.com/bit-team/backintime/commit/cef81d0da93ff601252607df3db1a48f7f6f01
Please adjust the affected versions in the BTS as needed.
Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: backintime
Source-Version: 1.1.24-0.1
We believe that the bug you reported is fixed in the latest version of
backintime, 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 881...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Fabian Wolff (supplier of updated backintime 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, 17 Jul 2018 13:02:53 +0200
Source: backintime
Binary: backintime-common backintime-qt4 backintime-gnome backintime-kde
Architecture: source all
Version: 1.1.24-0.1
Distribution: unstable
Urgency: medium
Maintainer: Jonathan Wiltshire
Changed-By: Fabian Wolff
Description:
backintime-common - simple backup/snapshot system (common files)
backintime-gnome - GNOME front-end for backintime (transitional package)
backintime-kde - KDE front-end for backintime (transitional package)
backintime-qt4 - simple backup/snapshot system (graphical interface)
Closes: 879609 881205
Changes:
backintime (1.1.24-0.1) unstable; urgency=medium
.
* Non-maintainer upload.
* New upstream release (Closes: #879609, #881205)
(fixes CVE-2017-16667).
* Update debian/watch to version 4 format (no changes).
* Remove patches 01-858193-back-up-slash-root-perms.patch and
02-polkit-vuln.patch (fixed upstream).
* Set Priority to optional in debian/control (extra is deprecated).
* Update Vcs-Git and Vcs-Browser fields in debian/control.
* Delete trailing whitespace from debian/{changelog,control} in
order to silence the file-contains-trailing-whitespace Lintian
tag.
* Upgrade to debhelper compat level 11.
* Upgrade to Standards-Version 4.1.5 in debian/control.
* Add patches 01-fix-spelling-errors.patch and
02-fix-man-error.patch.
* Remove unused desktop-command-not-in-package Lintian override.
* Update debian/copyright.
Checksums-Sha1:
f8cb0094c792f70df9ab74f02787ba368e5e95b5 2083 backintime_1.1.24-0.1.dsc
4b624e8427b51011159851019d4ef302f574a664 657667 backintime_1.1.24.orig.tar.gz
8b85db6b15a0e754715d471f75582c4406ec9ef2 6516
backintime_1.1.24-0.1.debian.tar.xz
c6264bd8b3982be788ab74865a9491b791a6ca27 248316
backintime-common_1.1.24-0.1_all.deb
cc1d6c83e85142eb1e05590dfbb4df432c477920 17596
backintime-gnome_1.1.24-0.1_all.deb
c57a2e78e4e1084413ab3cc378d04dc7ab44fe52 17608
backintime-kde_1.1.24-0.1_all.deb
a582ae090ed903d96cea9a9483ed5f09c2e4c91b 65388
backintime-qt4_1.1.24-0.1_all.deb
b9011b0fd931168726413068e069c7ef61accf7a 6728
backintime_1.1.24-0.1_amd64.buildinfo
Bug#902631: devscripts: CI fails in unstable due to Python 3.7
Hi Sandro, Upstream README seems to indicate that there is no release that supports *both* python 2.7 and 3.7 so this is not a choice between 2.0 and 1.9. More likely, two source packages are required for buster. Alternatively one of Python 2 / Python 3 must be dropped from pylint (presumably Python 2). If these are the options, which are you intending to follow? On Sunday, 22 July 2018 15:52:04 AEST Sandro Tosi wrote: > thanks for ignoring the next paragraph in that email, so let me re-add it > here: > > ``` > since astroid/pylint only support python 3.4+, it is not as simple as > package the new version and upload it; i'm not even (yet) sure buster > should have 2.0 but maybe it should to 1.9 > ``` No-one is ignoring that statement, just hoping that there is progress towards a solution rather than statements of what the problem is. We have all read the bug log and know the problem. You've indicated that you don't want help, but not what the timeline to a fix is. If time is a problem to deal with RC bugs, perhaps you'd be happy for team mates in PAPT to deal with this? For me, at least, the inability to have pylint3 installed and test out python3.7 on the same machine is now hindering other Debian work, including the work that I wanted to do this week at DebCamp. cheers Stuart -- Stuart Prescotthttp://www.nanonanonano.net/ stu...@nanonanonano.net Debian Developer http://www.debian.org/ stu...@debian.org GPG fingerprint90E2 D2C1 AD14 6A1B 7EBB 891D BBC1 7EBB 1396 F2F7
Processed: python3-tango: fails to install with python 3.7 as a supported python version
Processing control commands: > block 902788 with -1 Bug #902788 [python3.7] python3-minimal needs Breaks for software/modules broken by 3.7 902788 was blocked by: 902761 903145 902650 902757 903218 903528 902631 902900 903529 903784 903016 903525 903423 903826 902766 902715 903388 902794 903031 903558 903527 903526 903457 903030 903522 902989 902646 902788 was blocking: 902582 903432 Added blocking bug(s) of 902788: 904298 -- 902788: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902788 904298: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904298 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#904298: python3-tango: fails to install with python 3.7 as a supported python version
Package: python3-tango Version: 9.2.3-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Control: block 902788 with -1 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...): Setting up python3-tango (9.2.3-1+b1) ... File "/usr/lib/python3/dist-packages/tango/asyncio_tools.py", line 94 _chain_future(asyncio.async(coro, loop=loop), future) ^ SyntaxError: invalid syntax File "/usr/lib/python3/dist-packages/tango/gevent_executor.py", line 127 watcher = self.hub.loop.async() ^ SyntaxError: invalid syntax dpkg: error processing package python3-tango (--configure): installed python3-tango package post-installation script subprocess returned error exit status 1 "async" has become a reserved keyword in python 3.7 cheers, Andreas python3-itango=0.1.7-1.log.gz Description: application/gzip
Bug#904297: dms-core: fails to install: calls /etc/init.d/procps incorrectly
Package: dms-core
Version: 1.0.8.1-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.
>From the attached log (scroll to the bottom...):
Selecting previously unselected package dms-core.
(Reading database ...
(Reading database ... 10054 files and directories currently installed.)
Preparing to unpack .../dms-core_1.0.8.1-1_amd64.deb ...
Unpacking dms-core (1.0.8.1-1) ...
Setting up dms-core (1.0.8.1-1) ...
Adding user `dmsdmd' to group `bind' ...
Adding user dmsdmd to group bind
Done.
Adding user `dmsdmd' to group `dms' ...
Adding user dmsdmd to group dms
Done.
Usage: /etc/init.d/procps {start|stop|status|restart|try-restart|force-reload}
dpkg: error processing package dms-core (--configure):
installed dms-core package post-installation script subprocess returned
error exit status 3
Errors were encountered while processing:
dms-core
cheers,
Andreas
dms-core_1.0.8.1-1.log.gz
Description: application/gzip
Bug#902631: devscripts: CI fails in unstable due to Python 3.7
On Sat, Jul 21, 2018 at 6:58 AM Mattia Rizzolo wrote: > > On Tue, Jul 17, 2018 at 03:06:14PM -0400, Sandro Tosi wrote: > > no need, i can upgrade the package myself when needed, but thanks for the > > offer. > > Then can you pretty please do it? It is neeeded. thanks for ignoring the next paragraph in that email, so let me re-add it here: ``` since astroid/pylint only support python 3.4+, it is not as simple as package the new version and upload it; i'm not even (yet) sure buster should have 2.0 but maybe it should to 1.9 ``` -- Sandro "morph" Tosi My website: http://sandrotosi.me/ Me at Debian: http://wiki.debian.org/SandroTosi G+: https://plus.google.com/u/0/+SandroTosi
Bug#866110: multipath-tools: mpathpersist segfaults. Newer version is available and fixed!
Upstream commit is: https://git.opensvc.com/gitweb.cgi?p=multipath-tools/.git;a=commit;h=fef089a6610f94a847541069f3008a5708044015
Processed (with 1 error): notfound 897775 in 4.12.2-dfsg1-2, fixed 897775 in 4.12.2-dfsg1-2, fixed 897756 in 4.12.2-dfsg1-2 ...
Processing commands for cont...@bugs.debian.org:
> notfound 897775 4.12.2-dfsg1-2
Bug #897775 {Done: Andreas Beckmann } [src:insighttoolkit4]
itksnap: ftbfs with GCC-8
No longer marked as found in versions insighttoolkit4/4.12.2-dfsg1-2.
> fixed 897775 4.12.2-dfsg1-2
Bug #897775 {Done: Andreas Beckmann } [src:insighttoolkit4]
itksnap: ftbfs with GCC-8
Marked as fixed in versions insighttoolkit4/4.12.2-dfsg1-2.
> fixed 897756 4.12.2-dfsg1-2
Bug #897756 {Done: Andreas Beckmann } [src:insighttoolkit4]
fw4spl: ftbfs with GCC-8
Marked as fixed in versions insighttoolkit4/4.12.2-dfsg1-2.
> found 897775 4.12.2-dfsg1-1
Bug #897775 {Done: Andreas Beckmann } [src:insighttoolkit4]
itksnap: ftbfs with GCC-8
Marked as found in versions insighttoolkit4/4.12.2-dfsg1-1.
> found 897756 4.12.2-dfsg1-1
Bug #897756 {Done: Andreas Beckmann } [src:insighttoolkit4]
fw4spl: ftbfs with GCC-8
Marked as found in versions insighttoolkit4/4.12.2-dfsg1-1.
> forcemerge 897899 897775 897756
Bug #897899 {Done: Gert Wollny } [src:insighttoolkit4] FTBFS
with GCC 8 (error "Dunno about this gcc")
Bug #897775 {Done: Andreas Beckmann } [src:insighttoolkit4]
itksnap: ftbfs with GCC-8
897830 was blocked by: 897899
897830 was not blocking any bugs.
Added blocking bug(s) of 897830: 897775
Failed to forcibly merge 897899: Failure while trying to adjust bugs, please
report this as a bug: Not altering archived bugs; see unarchive..
at /usr/local/lib/site_perl/Debbugs/Control.pm line 2133.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
897756: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897756
897775: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897775
897830: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897830
897899: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897899
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed (with 1 error): closing 897775, affects 897899, forcibly merging 897899 897775 897756
Processing commands for cont...@bugs.debian.org:
> close 897775
Bug #897775 [src:insighttoolkit4] itksnap: ftbfs with GCC-8
Marked Bug as done
> affects 897899 + src:itksnap src:fw4spl
Bug #897899 {Done: Gert Wollny } [src:insighttoolkit4] FTBFS
with GCC 8 (error "Dunno about this gcc")
Added indication that 897899 affects src:itksnap and src:fw4spl
> forcemerge 897899 897775 897756
Bug #897899 {Done: Gert Wollny } [src:insighttoolkit4] FTBFS
with GCC 8 (error "Dunno about this gcc")
Bug #897899 {Done: Gert Wollny } [src:insighttoolkit4] FTBFS
with GCC 8 (error "Dunno about this gcc")
Marked as found in versions insighttoolkit4/4.12.2-dfsg1-2.
Bug #897756 {Done: Andreas Beckmann } [src:insighttoolkit4]
fw4spl: ftbfs with GCC-8
Failed to forcibly merge 897899: Failure while trying to adjust bugs, please
report this as a bug: Not altering archived bugs; see unarchive..
at /usr/local/lib/site_perl/Debbugs/Control.pm line 2133.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
897756: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897756
897775: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897775
897899: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897899
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: notfixed 858302 in 1.13.0~ds1-3, fixed 858302 in 1.13.0~ds1-3, tagging 897854 ..., tagging 888255 ...
Processing commands for cont...@bugs.debian.org:
> notfixed 858302 1.13.0~ds1-3
Bug #858302 {Done: Dmitry Smirnov }
[golang-github-docker-docker-dev] Should ship api source subdirectory
No longer marked as fixed in versions
golang-github-docker-docker-dev/1.13.0~ds1-3.
> fixed 858302 1.13.0~ds1-3
Bug #858302 {Done: Dmitry Smirnov }
[golang-github-docker-docker-dev] Should ship api source subdirectory
Marked as fixed in versions docker.io/1.13.0~ds1-3.
> tags 897854 + experimental
Bug #897854 {Done: Ximin Luo } [src:rustc] rustc: ftbfs
with GCC-8
Added tag(s) experimental.
> severity 901044 serious
Bug #901044 [libjnr-posix-java-doc] libjnr-posix-java-doc: ships
/usr/share/javascript/jquery/jquery.js
Severity set to 'serious' from 'normal'
> tags 888255 + sid buster
Bug #888255 [src:netty-3.9] RM? Upstream dropped support, security important,
newer version packaged
Added tag(s) buster and sid.
> reassign 902760 src:igraph
Bug #902760 [igraph] python-igraph FTBFS with ARPACK 3.6
Bug reassigned from package 'igraph' to 'src:igraph'.
Ignoring request to alter found versions of bug #902760 to the same values
previously set
Ignoring request to alter fixed versions of bug #902760 to the same values
previously set
> forcemerge 902945 902760
Bug #902945 [src:igraph] igraph: FTBFS with ARPACK 3.6
Bug #902760 [src:igraph] python-igraph FTBFS with ARPACK 3.6
Marked as found in versions igraph/0.7.1-2.1.
Added tag(s) buster, upstream, help, and sid.
Merged 902760 902945
> affects 902760 + src:python-igraph
Bug #902760 [src:igraph] python-igraph FTBFS with ARPACK 3.6
Bug #902945 [src:igraph] igraph: FTBFS with ARPACK 3.6
Added indication that 902760 affects src:python-igraph
Added indication that 902945 affects src:python-igraph
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
858302: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=858302
888255: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888255
897854: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897854
901044: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901044
902760: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902760
902945: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902945
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed (with 1 error): unarchiving 897899, severity of 897899 is serious, tagging 897899, notfound 897756 in 4.12.2-dfsg1-2 ...
Processing commands for cont...@bugs.debian.org:
> unarchive 897899
Bug #897899 {Done: Gert Wollny } [src:insighttoolkit4] FTBFS
with GCC 8 (error "Dunno about this gcc")
Unarchived Bug 897899
> severity 897899 serious
Bug #897899 {Done: Gert Wollny } [src:insighttoolkit4] FTBFS
with GCC 8 (error "Dunno about this gcc")
Severity set to 'serious' from 'normal'
> tags 897899 - sid buster
Bug #897899 {Done: Gert Wollny } [src:insighttoolkit4] FTBFS
with GCC 8 (error "Dunno about this gcc")
Removed tag(s) buster and sid.
> notfound 897756 4.12.2-dfsg1-2
Bug #897756 [src:insighttoolkit4] fw4spl: ftbfs with GCC-8
No longer marked as found in versions insighttoolkit4/4.12.2-dfsg1-2.
> close 897756
Bug #897756 [src:insighttoolkit4] fw4spl: ftbfs with GCC-8
Marked Bug as done
> forcemerge 897899 897756
Bug #897899 {Done: Gert Wollny } [src:insighttoolkit4] FTBFS
with GCC 8 (error "Dunno about this gcc")
Bug #897756 {Done: Andreas Beckmann } [src:insighttoolkit4]
fw4spl: ftbfs with GCC-8
Failed to forcibly merge 897899: Failure while trying to adjust bugs, please
report this as a bug: Not altering archived bugs; see unarchive..
at /usr/local/lib/site_perl/Debbugs/Control.pm line 2133.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
897756: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897756
897899: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897899
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#897852: marked as done (rsbackup: ftbfs with GCC-8)
Your message dated Sun, 22 Jul 2018 17:34:22 +
with message-id
and subject line Bug#897852: fixed in rsbackup 5.0-2
has caused the Debian Bug report #897852,
regarding rsbackup: ftbfs with GCC-8
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.)
--
897852: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897852
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:rsbackup
Version: 5.0-1
Severity: normal
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-8
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-8/g++-8, but succeeds to build with gcc-7/g++-7. The
severity of this report will be raised before the buster release.
The full build log can be found at:
http://aws-logs.debian.net/2018/05/01/gcc8/rsbackup_5.0-1_unstable_gcc8.log.gz
The last lines of the build log are at the end of this report.
To build with GCC 8, either set CC=gcc-8 CXX=g++-8 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-8/porting_to.html
[...]
CXX HTML.o
CXX IO.o
CXX MakeBackup.o
CXX Progress.o
CXX Prune.o
CXX Report.o
CXX RetireDevices.o
CXX RetireVolumes.o
CXX Store.o
CXX stylesheet.o
CXX Subprocess.o
CXX Text.o
CXX Unicode.o
CXX Volume.o
CXX ConfBase.o
CXX toLines.o
CXX globFiles.o
CXX Database.o
CXX parseInteger.o
CXX split.o
CXX EventLoop.o
CXX nonblock.o
CXX Action.o
CXX Selection.o
CXX Color.o
CXX parseFloat.o
CXX Render.o
In file included from /usr/include/sigc++-2.0/sigc++/sigc++.h:104,
from /usr/include/pangomm-1.4/pangomm/layout.h:7,
from Render.h:23,
from Render.cc:16:
/usr/include/sigc++-2.0/sigc++/signal.h: In static member function ‘static
sigc::internal::signal_emit0::result_type
sigc::internal::signal_emit0::emit(sigc::internal::signal_impl*)’:
/usr/include/sigc++-2.0/sigc++/signal.h:798:56: error: cast between
incompatible function types from ‘sigc::internal::hook’ {aka ‘void*
(*)(void*)’} to ‘sigc::internal::signal_emit0::call_type’ {aka
‘void (*)(sigc::internal::slot_rep*)’} [-Werror=cast-function-type]
(reinterpret_cast(slot.rep_->call_))(slot.rep_);
^
/usr/include/sigc++-2.0/sigc++/signal.h: In static member function ‘static
sigc::internal::signal_emit0::result_type
sigc::internal::signal_emit0::emit_reverse(sigc::internal::signal_impl*)’:
/usr/include/sigc++-2.0/sigc++/signal.h:825:55: error: cast between
incompatible function types from ‘sigc::internal::hook’ {aka ‘void*
(*)(void*)’} to ‘sigc::internal::signal_emit0::call_type’ {aka
‘void (*)(sigc::internal::slot_rep*)’} [-Werror=cast-function-type]
(reinterpret_cast(it->rep_->call_))(it->rep_);
^
At global scope:
cc1plus: error: unrecognized command line option ‘-Wno-c++14-extensions’
[-Werror]
cc1plus: all warnings being treated as errors
make[3]: *** [Makefile:1065: Render.o] Error 1
make[3]: Leaving directory '/<>/src'
make[2]: *** [Makefile:419: all-recursive] Error 1
make[2]: Leaving directory '/<>'
make[1]: *** [Makefile:360: all] Error 2
make[1]: Leaving directory '/<>'
make: *** [debian/rules:36: build] Error 2
dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit
status 2
--- End Message ---
--- Begin Message ---
Source: rsbackup
Source-Version: 5.0-2
We believe that the bug you reported is fixed in the latest version of
rsbackup, 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 897...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance
Bug#904104: marked as done (aiscm: FTBFS with ffmpeg 4.0)
Your message dated Sun, 22 Jul 2018 17:18:55 + with message-id and subject line Bug#904104: fixed in aiscm 0.15.5-1 has caused the Debian Bug report #904104, regarding aiscm: FTBFS with ffmpeg 4.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.) -- 904104: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904104 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: aiscm Version: 0.515.4-1 Severity: serious Justification: fails to build from source (but built successfully in the past) Tags: sid buster aiscm failed to build for the ffmpeg 4.0 transition: | | Testsuite summary for aiscm 0.15.4 | | # TOTAL: 1958 | # PASS: 1944 | # SKIP: 1 | # XFAIL: 9 | # FAIL: 4 | # XPASS: 0 | # ERROR: 0 | | See tests/test-suite.log | Please report to j...@wedesoft.de | | make[5]: *** [Makefile:726: test-suite.log] Error 1 See https://buildd.debian.org/status/fetch.php?pkg=aiscm=amd64=0.15.4-1%2Bb2=1531997332=0 for the full log. Cheers -- Sebastian Ramacher signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: aiscm Source-Version: 0.15.5-1 We believe that the bug you reported is fixed in the latest version of aiscm, 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 904...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jan Wedekind (supplier of updated aiscm 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, 20 Jul 2018 10:17:00 +0100 Source: aiscm Binary: aiscm Architecture: source Version: 0.15.5-1 Distribution: unstable Urgency: low Maintainer: Jan Wedekind Changed-By: Jan Wedekind Description: aiscm - Guile numerical arrays and tensor extension Closes: 904104 Changes: aiscm (0.15.5-1) unstable; urgency=low . - New upstream release. - Disable some FFMpeg audio tests. Closes: #904104 Checksums-Sha1: 7c09ca204f0c2cbe394ce9288ce3c61ddb31a7ea 2268 aiscm_0.15.5-1.dsc ca88079a07d5f67c810d6b0c5fbb4669fddf3c17 3718917 aiscm_0.15.5.orig.tar.gz e776d5884571d11d1331a9959688bffe4117519f 833 aiscm_0.15.5.orig.tar.gz.asc 97c4118e0f47882eee65b22e5247c07353a81c9b 5496 aiscm_0.15.5-1.debian.tar.xz f051326ce5611f60d1cb5c6e0def5694681e7de8 15092 aiscm_0.15.5-1_amd64.buildinfo Checksums-Sha256: f53bdfd511d09faf05147d36919ec964b0ea9adc1cd868358bdae5c34a4406ec 2268 aiscm_0.15.5-1.dsc e4fff76ad5d5f98e95083948fe134be34700f42c8f8de1a41943f596ea06ab19 3718917 aiscm_0.15.5.orig.tar.gz 34d3588780d13bf4206ff397a8ff8d269e38f8e67f8d1dbeab50d4767454ad10 833 aiscm_0.15.5.orig.tar.gz.asc 23a4286ac29143445bc7f696fa90a4b18229c7021ff6519574836272edcb9cb1 5496 aiscm_0.15.5-1.debian.tar.xz 2deba1c6c9c54e0536a2b8e476c18fbd777abf592090995a0fcdcadbce5f3e8d 15092 aiscm_0.15.5-1_amd64.buildinfo Files: 66b450a86e4837bbc1a4ea4c57c4d8c7 2268 lisp optional aiscm_0.15.5-1.dsc 42a881aa60cd149ed890c09717dd3da6 3718917 lisp optional aiscm_0.15.5.orig.tar.gz 26c1471805bd0ff545dd6c47de8a3f17 833 lisp optional aiscm_0.15.5.orig.tar.gz.asc 6c2ec10e76c687232897da811055a8c8 5496 lisp optional aiscm_0.15.5-1.debian.tar.xz 76c9e240fe4f211a7b4ab670b576d493 15092 lisp optional aiscm_0.15.5-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEolIP6gqGcKZh3YxVM2L3AxpJkuEFAltUuOcACgkQM2L3AxpJ kuHyZg/+KregirRYsgv0WpyCMMqo+KNm64woOQKL1f661/saPc4cIZd4tI9ev2A/ sMR3HUXjH2+li1A1Ff8feOVMBno9A5niOFLo/Q6XrpnuglJ4GgIEmelTtQigOEnn /8ETnt4M7SAOvc7QkaxGOznN49py4P+J8umJ0vkJRSWjJNgKG3i35sP6HCCgW4u9 mPoJ1X+ztV27Jp0nL3WE56P5BzWUthYUx/x8ipzjBw8JdZwmNyi4dFjmv6VddNYQ RZ55hWN3WEJ7W69IXeUtWGR771Hg8aiQURApRopiPwaP7n2fP0rLvc0wtIMRBgl0 gNVrOtp3Nc4EL50c6rAyKQalZoEvTMm3l7zfamRjQDvkAD/rVldrqn34YYCOEuAK kMCtDmBZzlcpHw2etRkR8VqUsy/Nqh/MhcbrVCgVBsui3wet6DM96nIOh5KklqiQ M74JkSjckGvOLRIORe4yRlUUzOqhM07Ls2Sk2EanTnQbA/v9ROGeR9Uv/OlSfDXN tw3FoHkkI9vckj10dsZM/mQrnBqitK0imFPyu7cYf1BMptnG8B8wwm2OxwAStrsa
Processed: Re: Bug#897800: libvigraimpex: ftbfs with GCC-8
Processing control commands: > tags -1 patch fixed-upstream Bug #897800 [src:libvigraimpex] libvigraimpex: ftbfs with GCC-8 Added tag(s) patch and fixed-upstream. -- 897800: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897800 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#897800: libvigraimpex: ftbfs with GCC-8
Control: tags -1 patch fixed-upstream On 2018-07-22 Juhani Numminen wrote: > Control: forwarded -1 https://github.com/ukoethe/vigra/issues/414 > On Fri, 04 May 2018 12:22:30 + Matthias Klose wrote: > > Package: src:libvigraimpex > > Version: 1.10.0+git20160211.167be93+dfsg-5 [...] > > /<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg/vigranumpy/src/core/convolution.cxx:435:37: > > error: no matching function for call to > > 'gaussianDivergenceMultiArray(vigra::NumpyArray<3, > > vigra::TinyVector, vigra::StridedArrayTag>&, > > vigra::NumpyArray<3, vigra::Singleband, vigra::StridedArrayTag>&, > > vigra::ConvolutionOptions<3>&)' > Dear maintainer, > there's an upstream issue that seems to concern the same error, though > on clang, not gcc-8. Please note that I haven't done any rebuilds or > patching myself to confirm this claim. I have just done a successful build after adding upstream's 81958d302494e137f98a8b1d7869841532f90388. cu Andreas -- `What a good friend you are to him, Dr. Maturin. His other friends are so grateful to you.' `I sew his ears on from time to time, sure'
Bug#904091: marked as done (arpack ftbfs on armel, mips64el, ppc64el)
Your message dated Sun, 22 Jul 2018 16:18:55 + with message-id and subject line Bug#904091: fixed in arpack 3.6.2-1 has caused the Debian Bug report #904091, regarding arpack ftbfs on armel, mips64el, ppc64el 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.) -- 904091: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904091 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:arpack Version: 3.6.1-1 Severity: serious Tags: sid buster arpack ftbfs on armel, mips64el, ppc64el. The build fails when running the tests. --- End Message --- --- Begin Message --- Source: arpack Source-Version: 3.6.2-1 We believe that the bug you reported is fixed in the latest version of arpack, 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 904...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sylvestre Ledru (supplier of updated arpack 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, 22 Jul 2018 17:41:40 +0200 Source: arpack Binary: libarpack2 libarpack2-dev libparpack2 libparpack2-dev Architecture: source Version: 3.6.2-1 Distribution: unstable Urgency: medium Maintainer: Debian Science Team Changed-By: Sylvestre Ledru Description: libarpack2 - Fortran77 subroutines to solve large scale eigenvalue problems libarpack2-dev - Fortran77 subroutines to solve large scale eigenvalue problems (d libparpack2 - Parallel subroutines to solve large scale eigenvalue problems libparpack2-dev - Parallel subroutines to solve large scale eigenvalue problems (de Closes: 904091 Changes: arpack (3.6.2-1) unstable; urgency=medium . * New upstream release Should fix FTBFS on armel, mips64el, ppc64el (Closes: #904091) Checksums-Sha1: 7a12310f8d94a7264555ce5a808fc91c52a13be8 2147 arpack_3.6.2-1.dsc e93662e1974fd5449cbc44a3360418b066c966a6 968449 arpack_3.6.2.orig.tar.gz ad105e7235a417ff5a99f6fd65a93cd62bd4cd3c 8880 arpack_3.6.2-1.debian.tar.xz 12868702e0b1e45f9c26a7dbe3a7837d78b6532c 8364 arpack_3.6.2-1_amd64.buildinfo Checksums-Sha256: d5663717c110ee57e604a651adf5c4648aeb6e92923046d96299c232eaab688f 2147 arpack_3.6.2-1.dsc 673c8202de996fd3127350725eb1818e534db4e79de56d5dcee8c00768db599a 968449 arpack_3.6.2.orig.tar.gz 6c2621c485f9dbf0a7b2350353449f112c0ba9f7df5d83c0934d77e4029482be 8880 arpack_3.6.2-1.debian.tar.xz 21b4acd17fa02bdb2216a80314c49ed669941aac1927290e76d0ee04f7388c7d 8364 arpack_3.6.2-1_amd64.buildinfo Files: 14d2810c41aa70d8012fc734d26f6979 2147 math optional arpack_3.6.2-1.dsc 172a8b72e6f7f53bfa3df21304048fa3 968449 math optional arpack_3.6.2.orig.tar.gz 45107f1dbd5d6b121d3d81f526c04c55 8880 math optional arpack_3.6.2-1.debian.tar.xz 9b4bdc77d1daef0eeddb94f3aa4e4aeb 8364 math optional arpack_3.6.2-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEtg21mU05vsTRqVzPfmUo2nUvG+EFAltUqjsACgkQfmUo2nUv G+Hzhg//UVpZsiW8goY1+DNQW3R6oAjLWNG+Uk+XdqfhuQod26PImXiVC9TiPFOr m+ewnAerDP9z8fj4Hp+lS34BgsrWLyMqrbVk6wJg+3w9AZ7Oaj6ptHvka00bfJDp rGqH/0c0MfNBei+fdw6+PEh7kwsMx/iVFnjIuHzXQd/FWzyJa6neSogTqco6zoLD OPczUmkVartoyHnHDVCAZWVAAYSUlvCLaTzUjDerVjksfchxe5ahpKDPO4Uo8boN tXAcaE0kl24RFuREoSvUSjwrHIsjA+8Dt/BarCbbjN0t7PX8d/L4tpfAG0xchAwF VlA3LxU+sKBfY3WxF2bd37RwNvApWmg/KWmx+s2C5CNe3/UElezGcjgoLOAI352x bTc3bMeu3O2K6s2CpZFGfAEJvuvpKi93ibncQ6W3lpwloWop7bTpuXuGxMo+ZiJQ Ik3qlYeK60CmeT6dK8J6zCmqLOAVnch5fZeDW/j8UbxbrjnXZ5p+OAMxEc0JTJ5f VkDhT68N4/PlBABLavjU7PepLGhdujjmWLJotTSDGljdoHs0BsW5dkDxFIrev8Hd fzTM1Rhb2OYnCG/J33B6puZ6QLP3HzJfBSemkG+21xgd3dfnSLpnX9cZP02skmLq hED9LtXIUfMLNxaCz8ckdy/pNMmJjLTHF010ar9Z/stH56ob548= =wq86 -END PGP SIGNATURE End Message ---
Bug#903349: marked as done (codespell: FTBFS in buster/sid (dh_installdocs: Cannot find "NEWS"))
Your message dated Sun, 22 Jul 2018 16:03:54 + with message-id and subject line Bug#903349: fixed in codespell 1.13.0-3 has caused the Debian Bug report #903349, regarding codespell: FTBFS in buster/sid (dh_installdocs: Cannot find "NEWS") 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.) -- 903349: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903349 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:codespell Version: 1.13.0-2 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in buster but it failed: [...] debian/rules build-indep dh build-indep --with python3 --parallel --buildsystem=pybuild dh_update_autotools_config -i -O--parallel -O--buildsystem=pybuild dh_autoreconf -i -O--parallel -O--buildsystem=pybuild dh_auto_configure -i -O--parallel -O--buildsystem=pybuild I: pybuild base:217: python3.6 setup.py config running config debian/rules override_dh_auto_build make[1]: Entering directory '/<>' sed -i -e "s|python3|python2|g" ./bin/codespell make codespell.1 make[2]: Entering directory '/<>' PYTHONPATH=. help2man ./bin/codespell --include codespell.1.include --no-info --output codespell.1 sed -i '/\.SS \"Usage/,+2d' codespell.1 [... snipped ...] create-stamp debian/debhelper-build-stamp fakeroot debian/rules binary-indep dh binary-indep --with python3 --parallel --buildsystem=pybuild dh_testroot -i -O--parallel -O--buildsystem=pybuild dh_prep -i -O--parallel -O--buildsystem=pybuild dh_auto_install -i -O--parallel -O--buildsystem=pybuild I: pybuild base:217: /usr/bin/python3 setup.py install --root /<>/debian/codespell running install running build running build_py running egg_info writing codespell.egg-info/PKG-INFO writing dependency_links to codespell.egg-info/dependency_links.txt writing entry points to codespell.egg-info/entry_points.txt writing top-level names to codespell.egg-info/top_level.txt reading manifest file 'codespell.egg-info/SOURCES.txt' reading manifest template 'MANIFEST.in' writing manifest file 'codespell.egg-info/SOURCES.txt' running install_lib creating /<>/debian/codespell/usr creating /<>/debian/codespell/usr/lib creating /<>/debian/codespell/usr/lib/python3.6 creating /<>/debian/codespell/usr/lib/python3.6/dist-packages creating /<>/debian/codespell/usr/lib/python3.6/dist-packages/codespell_lib creating /<>/debian/codespell/usr/lib/python3.6/dist-packages/codespell_lib/data copying /<>/.pybuild/cpython3_3.6/build/codespell_lib/data/linux-kernel.exclude -> /<>/debian/codespell/usr/lib/python3.6/dist-packages/codespell_lib/data copying /<>/.pybuild/cpython3_3.6/build/codespell_lib/data/dictionary.txt -> /<>/debian/codespell/usr/lib/python3.6/dist-packages/codespell_lib/data copying /<>/.pybuild/cpython3_3.6/build/codespell_lib/data/__init__.py -> /<>/debian/codespell/usr/lib/python3.6/dist-packages/codespell_lib/data copying /<>/.pybuild/cpython3_3.6/build/codespell_lib/__init__.py -> /<>/debian/codespell/usr/lib/python3.6/dist-packages/codespell_lib creating /<>/debian/codespell/usr/lib/python3.6/dist-packages/codespell_lib/tests copying /<>/.pybuild/cpython3_3.6/build/codespell_lib/tests/__init__.py -> /<>/debian/codespell/usr/lib/python3.6/dist-packages/codespell_lib/tests copying /<>/.pybuild/cpython3_3.6/build/codespell_lib/tests/test_basic.py -> /<>/debian/codespell/usr/lib/python3.6/dist-packages/codespell_lib/tests copying /<>/.pybuild/cpython3_3.6/build/codespell_lib/_codespell.py -> /<>/debian/codespell/usr/lib/python3.6/dist-packages/codespell_lib byte-compiling /<>/debian/codespell/usr/lib/python3.6/dist-packages/codespell_lib/data/__init__.py to __init__.cpython-36.pyc byte-compiling /<>/debian/codespell/usr/lib/python3.6/dist-packages/codespell_lib/__init__.py to __init__.cpython-36.pyc byte-compiling /<>/debian/codespell/usr/lib/python3.6/dist-packages/codespell_lib/tests/__init__.py to __init__.cpython-36.pyc byte-compiling /<>/debian/codespell/usr/lib/python3.6/dist-packages/codespell_lib/tests/test_basic.py to test_basic.cpython-36.pyc byte-compiling /<>/debian/codespell/usr/lib/python3.6/dist-packages/codespell_lib/_codespell.py to _codespell.cpython-36.pyc running install_egg_info Copying codespell.egg-info to /<>/debian/codespell/usr/lib/python3.6/dist-packages/codespell-1.13.0.egg-info Skipping SOURCES.txt running install_scripts Installing codespell script to /<>/debian/codespell/usr/bin dh_installdocs -i -O--parallel -O--buildsystem=pybuild
Bug#900533: The most annoying bug ever: https://bugs.debian.org/900533 , fix it!
Recently Debian Stretch introduced the most annoying bug ever:
https://bugs.debian.org/900533 ("chromium 67.0.3396.62-1: youtube video, gif's,
html5, and movies no longer work"). It affects a very very lot of Debian users.
It renders entire system completely unusable. Because ability of viewing
videos, listening to music etc using one's favorite browser is one of the main
functions of the system.
I am unable listen music using https://vk.com/audio anymore.
Bad Chromium version was installed through stretch-security repository into
every Stretch installation.
So, please fix the bug immediately!!! And make it install to usual Stretch
installations (with stable and stable-security repos enables) in next upgrade.
This is very important, so I sent this widespread mail.
==
Askar Safin
http://vk.com/safinaskar
Processed: upstream ticket
Processing commands for cont...@bugs.debian.org: > forwarded 897770 https://github.com/PurpleI2P/i2pd/issues/1085 Bug #897770 [src:i2pd] i2pd: ftbfs with GCC-8 Set Bug forwarded-to-address to 'https://github.com/PurpleI2P/i2pd/issues/1085'. > stop Stopping processing here. Please contact me if you need assistance. -- 897770: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897770 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#900652: marked as done (guile-2.2: FTBFS on armhf: FAIL: gc.test: gc: after-gc-hook gets called)
Your message dated Sun, 22 Jul 2018 15:49:08 + with message-id and subject line Bug#900652: fixed in guile-2.2 2.2.3+1-6 has caused the Debian Bug report #900652, regarding guile-2.2: FTBFS on armhf: FAIL: gc.test: gc: after-gc-hook gets called 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.) -- 900652: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900652 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: guile-2.2 Version: 2.2.3+1-4 Severity: serious Your package failed to build on armhf: Running gc.test FAIL: gc.test: gc: after-gc-hook gets called [...] Totals for this test run: passes: 40732 failures: 1 unexpected passes: 0 expected failures: 10 unresolved test cases: 578 untested test cases:1 unsupported test cases: 1 errors: 0 FAIL: check-guile == 1 of 1 test failed Full log at https://buildd.debian.org/status/package.php?p=guile-2.2 Emilio --- End Message --- --- Begin Message --- Source: guile-2.2 Source-Version: 2.2.3+1-6 We believe that the bug you reported is fixed in the latest version of guile-2.2, 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 900...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Rob Browning (supplier of updated guile-2.2 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 21 Jul 2018 14:34:22 -0500 Source: guile-2.2 Binary: guile-2.2 guile-2.2-dev guile-2.2-doc guile-2.2-libs Architecture: source amd64 all Version: 2.2.3+1-6 Distribution: unstable Urgency: medium Maintainer: Rob Browning Changed-By: Rob Browning Description: guile-2.2 - GNU extension language and Scheme interpreter guile-2.2-dev - Development files for Guile 2.2 guile-2.2-doc - Documentation for Guile 2.2 guile-2.2-libs - Core Guile libraries Closes: 900652 Changes: guile-2.2 (2.2.3+1-6) unstable; urgency=medium . * Don't fail the build if the after-gc-hook test fails on mips(el). Add 0011-gc.test-after-gc-hook-mark-unresolved-on-failure-for.patch to resolve the issue. (Closes: 900652) Checksums-Sha1: dbb5b3af91240a172f27bfd571c1ccca07708196 2142 guile-2.2_2.2.3+1-6.dsc a207058360ca9f393a62a83c01b6b12d80604878 25296 guile-2.2_2.2.3+1-6.debian.tar.xz 2ab1c1d6929159d856e8ca22c887619f75486b91 609904 guile-2.2-dev_2.2.3+1-6_amd64.deb 10b5036d1584ee5c8298a709e3f025fe9dffb5ce 932456 guile-2.2-doc_2.2.3+1-6_all.deb b25535f3e1726e793129ee4559854fc45108530d 1812724 guile-2.2-libs-dbgsym_2.2.3+1-6_amd64.deb d63e4a961bff188974d859faad4db0941bb9f86e 4953712 guile-2.2-libs_2.2.3+1-6_amd64.deb 9aa21590afc3bc1b68d87b54b08f3ea73fbe002c 7556 guile-2.2_2.2.3+1-6_amd64.buildinfo 28ce7f4cce4daddc1bfd7c17af0a94c432393eb0 19816 guile-2.2_2.2.3+1-6_amd64.deb Checksums-Sha256: 4bddf97c281cb70b0c1b22ce913328401e5ac227f4e66ca227c1e923673fd46b 2142 guile-2.2_2.2.3+1-6.dsc d2cf1b7b62afcf2a3fbddc06f31d020ba97b721a39fdf449e21469a4b9319a3f 25296 guile-2.2_2.2.3+1-6.debian.tar.xz daaad84e137dbf11a681f12c7c198d79575e90ac96f1c70bff5a6fc298138588 609904 guile-2.2-dev_2.2.3+1-6_amd64.deb 0f9da8fa3726da9680aaac895f3bd4423c28828479cb3a59611ec7fd984fd3e6 932456 guile-2.2-doc_2.2.3+1-6_all.deb 1a10bb25729d1c903fa059a1f9f4a57844844cf93e143b5779073974325194c4 1812724 guile-2.2-libs-dbgsym_2.2.3+1-6_amd64.deb 3fb1f7a2b69d43455fce438308150ac6e0a6b0f2b511f02d492bdf04f2db8e4b 4953712 guile-2.2-libs_2.2.3+1-6_amd64.deb fea12a03d6962ef2e56ee6e70430cdd3e4ca06b5030f0b94be7c387aa13902bf 7556 guile-2.2_2.2.3+1-6_amd64.buildinfo c9e5f7ea9272a3713b08f1d7c5d820230c4594b6647f19d0c6246af2db0e3602 19816 guile-2.2_2.2.3+1-6_amd64.deb Files: c823731060136f93c864a420c4fd4e97 2142 interpreters optional guile-2.2_2.2.3+1-6.dsc 26c05c6123e0d942de1429336c869395 25296 interpreters optional guile-2.2_2.2.3+1-6.debian.tar.xz 042e84944203d6c1db58d9d8b268925d 609904 lisp optional guile-2.2-dev_2.2.3+1-6_amd64.deb 40a39e613596ccd1c5f75690de5a206f 932456 doc optional guile-2.2-doc_2.2.3+1-6_all.deb 75298737dc0a81cd5e6e2e220a47eff7 1812724 debug optional
Bug#904133: t-d ftbfs with memory exhaustion on many targets
Hi, 20.07.2018 14:38, Matthias Klose пишет: > the package ftbfs at least on armel, and mips* in Debian It failed to build due to a missing linker option, -latomic. The fix is already available[1], but an issue is that the option may add an unneeded dependency. > Did you make any measurements how much better the code is with -flto? I'm > unsure if it's worth the trouble for a desktop application. Deactivation of LTO leads to more memory consumption during compilation. At least at my laptop building process without -flto requires 5.81 GB of virtual memory, takes two and a half hours and produces a binary of 29.7 MB size. In current state, building of the package requires 4.97 GB of virtual memory, takes about one hour and produces a binary of 23.2 MB size. To be honest, I have the laptop with 4 GB of RAM, so such a long time in the first case is understandable. Obviously, without LTO, results are less good, but we can try to disable link-time optimizations as an experiment. [1]: https://salsa.debian.org/debian/telegram-desktop/commit/d922c6628f2ee56bf3e896db64f20c41352d8246
Processed: your mail
Processing commands for cont...@bugs.debian.org: > retitle 904133 telegram-desktop: FTBFS with memory exhaustion on many targets Bug #904133 [src:telegram-desktop] t-d ftbfs with memory exhaustion on many targets Changed Bug title to 'telegram-desktop: FTBFS with memory exhaustion on many targets' from 't-d ftbfs with memory exhaustion on many targets'. > End of message, stopping processing here. Please contact me if you need assistance. -- 904133: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904133 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#897792: libqaccessibilityclient: ftbfs with GCC-8
Dear maintainers, The Fedora people have got a patch to fix FTBS (FTBFS) with gcc8. https://src.fedoraproject.org/rpms/qaccessibilityclient/c/0bc31c52a27a4b29cffa80ee67f4186295c92cf9 Juhani
Bug#897800: libvigraimpex: ftbfs with GCC-8
Control: forwarded -1 https://github.com/ukoethe/vigra/issues/414 On Fri, 04 May 2018 12:22:30 + Matthias Klose wrote: > Package: src:libvigraimpex > Version: 1.10.0+git20160211.167be93+dfsg-5 > Severity: normal > Tags: sid buster > User: debian-...@lists.debian.org > Usertags: ftbfs-gcc-8 > /<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg/vigranumpy/src/core/convolution.cxx:435:37: > error: no matching function for call to > 'gaussianDivergenceMultiArray(vigra::NumpyArray<3, vigra::TinyVector 3>, vigra::StridedArrayTag>&, vigra::NumpyArray<3, vigra::Singleband, > vigra::StridedArrayTag>&, vigra::ConvolutionOptions<3>&)' Dear maintainer, there's an upstream issue that seems to concern the same error, though on clang, not gcc-8. Please note that I haven't done any rebuilds or patching myself to confirm this claim. Cheers, Juhani
Processed: Re: Bug#897800: libvigraimpex: ftbfs with GCC-8
Processing control commands: > forwarded -1 https://github.com/ukoethe/vigra/issues/414 Bug #897800 [src:libvigraimpex] libvigraimpex: ftbfs with GCC-8 Set Bug forwarded-to-address to 'https://github.com/ukoethe/vigra/issues/414'. -- 897800: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897800 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#903218: Fails to install due to SyntaxError
async is now a keyword. The module has to be renamed. Upstream seems to be a little bit dead, looking at the ML... so maybe coordinate with other distro how to rename it?
Bug#903074: marked as done (foodcritic FTBFS: update Build-Depends: ruby-ronn -> ronn)
Your message dated Sun, 22 Jul 2018 14:40:21 + with message-id and subject line Bug#903074: fixed in foodcritic 13.1.1-2 has caused the Debian Bug report #903074, regarding foodcritic FTBFS: update Build-Depends: ruby-ronn -> ronn 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.) -- 903074: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903074 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: foodcritic Version: 13.1.1-1 Severity: serious Since ronn got split out of ruby-ronn, foodcritic fails to build from source. It was not possible to have ruby-ronn temporarily depend on ronn, because that would have created a dependency cycle. Please update Build-Depends and replace ruby-ronn with ronn as foodcritic uses the command line tool. Helmut --- End Message --- --- Begin Message --- Source: foodcritic Source-Version: 13.1.1-2 We believe that the bug you reported is fixed in the latest version of foodcritic, 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 903...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Stefano Rivera (supplier of updated foodcritic 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: Sun, 22 Jul 2018 21:42:51 +0800 Source: foodcritic Binary: foodcritic Architecture: source Version: 13.1.1-2 Distribution: unstable Urgency: medium Maintainer: Debian Ruby Extras Maintainers Changed-By: Stefano Rivera Description: foodcritic - lint tool for chef cookbooks Closes: 903074 Changes: foodcritic (13.1.1-2) unstable; urgency=medium . * Build-Depend on ronn, rather than ruby-ronn (Closes: #903074) * Declare Rules-Requires-Root: no. * Bump to Standards-Version 4.1.5, no changes needed. Checksums-Sha1: 2ceea7a2225406249e89cdc32eb45203e85784a2 1893 foodcritic_13.1.1-2.dsc ff646b2074d855505e9ffdb7258e248d9f6a186d 5792 foodcritic_13.1.1-2.debian.tar.xz a9760dabfa68719f7f6b57ca2aad6605fd08da8a 8199 foodcritic_13.1.1-2_source.buildinfo Checksums-Sha256: 5cf25d9cedf70b151d214acde0bd3ea22929e4181ded800b4a5f4b09fe9ca131 1893 foodcritic_13.1.1-2.dsc 6547af6dc219c56b4fed388bb6a6f351035403bceee5bf92fe0d2b541eb3cb30 5792 foodcritic_13.1.1-2.debian.tar.xz ae6988829a9af32c126f94582833b5ab4671c6adb604eeabaf1ee7542a881227 8199 foodcritic_13.1.1-2_source.buildinfo Files: 34ce2a477e86aa12d40a7d1e393068d3 1893 ruby optional foodcritic_13.1.1-2.dsc 6d3287a2833dd2b891ff549cba30722e 5792 ruby optional foodcritic_13.1.1-2.debian.tar.xz e1aeecdeeef9c1c617890d3f4c2da191 8199 ruby optional foodcritic_13.1.1-2_source.buildinfo -BEGIN PGP SIGNATURE- iQFIBAEBCgAyFiEE/zEtpbjiRmXHk+j/6vGSvKo/D1EFAltUiiAUHHN0ZWZhbm9y QGRlYmlhbi5vcmcACgkQ6vGSvKo/D1GNHwf7BTr52GDaxD6nivtdvLkwcBdS6XKx O1U/zvJ4xULLP4DyQxNvLbjR0Uhs8tTBhTw2ymfHLiCTGwteUiJsuJwpN+hWvrac 4zeIzRJyGdiDKBY3Qg0LeM98XKbFDhgkq9XbaalxQPym2clrL4gGk27Jixj7T+k/ 6yumv775PSvrkzCB/FVYFdJwmZbLG7Pe7rkmG4MnyNcycYmuzNL6LMCnThjeAEki M/Lz+7qasZTU8sMCD6fdppwhejpfp4EYKK1NLMYT2hAFPiQ4T6xpfXvFgfgqpKqJ ++FwFVXM5XUn+b31N63nfRmmVGGmSRcJS/gIGY3/rCoMIcd/D9NbQeLqpA== =c2Tb -END PGP SIGNATURE End Message ---
Bug#888371: marked as done (webcamoid: FTBFS with FFmpeg 4.0)
Your message dated Sun, 22 Jul 2018 14:42:18 + with message-id and subject line Bug#888371: fixed in webcamoid 8.1.0+dfsg-9 has caused the Debian Bug report #888371, regarding webcamoid: FTBFS with FFmpeg 4.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.) -- 888371: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888371 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: webcamoid Version: 8.1.0+dfsg-7 Severity: important User: debian-multime...@lists.debian.org Usertags: ffmpeg-3.5-transition Hi, Your package FTBFS with the upcoming version 3.5 of FFmpeg. In FFmpeg 3.5, there are a number of API changes which will cause many packages to FTBFS. For this reason I have uploaded an early development snapshot to experimental before the 3.5 release in an attempt to fix some of these a bit quicker. While 3.5 has not been finalized and the ABI is not stable yet, there should not be any significant API breakages before the release. Incomplete list of changes (based on looking at common build failures): - Some fields in AVCodecContext have been removed and replaced with private options which can be set using the av_opt_set* APIs - Most CODEC_* constants have been renamed to AV_CODEC_* - The buffer constants FF_INPUT_BUFFER_PADDING_SIZE and FF_MIN_BUFFER_SIZE have been renamed to AV_INPUT_BUFFER_PADDING_SIZE and AV_INPUT_BUFFER_MIN_SIZE. - The old resampling API provided by libavcodec has been removed. Use libswresample instead. - The libavfilter/avfiltergraph.h header has been removed, include libavfilter/avfilter.h instead. - The AVFrac structure (representing mixed rational numbers) has been removed. Build log: https://people.debian.org/~jcowgill/ffmpeg-3.5-20180122/webcamoid_amd64.build Thanks, James --- End Message --- --- Begin Message --- Source: webcamoid Source-Version: 8.1.0+dfsg-9 We believe that the bug you reported is fixed in the latest version of webcamoid, 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 888...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Herbert Parentes Fortes Neto (supplier of updated webcamoid 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: Sun, 22 Jul 2018 10:06:55 -0300 Source: webcamoid Binary: webcamoid libavkys8 libavkys-dev webcamoid-plugins akqml webcamoid-data Architecture: source Version: 8.1.0+dfsg-9 Distribution: unstable Urgency: medium Maintainer: Herbert Parentes Fortes Neto Changed-By: Herbert Parentes Fortes Neto Description: akqml - full featured webcam capture application - qml module libavkys-dev - full featured webcam capture application - dev libavkys8 - full featured webcam capture application - library webcamoid - full featured webcam capture application webcamoid-data - icons and locale files for webcamoid webcamoid-plugins - full featured webcam capture application - plugins Closes: 888371 Changes: webcamoid (8.1.0+dfsg-9) unstable; urgency=medium . * Upload to unstable. * debian/control: - Build-Depends - ffmpeg 4.0. (Closes: #888371) - Bump STD-V from 4.1.3 to 4.1.5 * debian/copyright: - secure-copyright-format-uri * debian/rules: - Remove '--parallel'. Default from this DH Checksums-Sha1: 54b4568aec052bb09532ba5441c9c2ba38a636c7 2480 webcamoid_8.1.0+dfsg-9.dsc 21d327e0d9f3f3d258329cb414a1d7cd0483 9743052 webcamoid_8.1.0+dfsg.orig.tar.gz ae36de1801eaa7ad92bf5b7afdb279da16c62367 14372 webcamoid_8.1.0+dfsg-9.debian.tar.xz babf52102ab2ca4d11892add8a094e9b8ea961ae 17971 webcamoid_8.1.0+dfsg-9_amd64.buildinfo Checksums-Sha256: 136d5b91c0f67aa3ca0e253cc52bca4528eee1081d9da23745f34d609cbadf9c 2480 webcamoid_8.1.0+dfsg-9.dsc cede61d073c147111ca02f1a4d19a2fd2332023f3c0d248f2317cc4ee4922132 9743052 webcamoid_8.1.0+dfsg.orig.tar.gz e27e12a48cdb7f62fdac83b1db180c49eb5926866134019e4173de4b6db0deb8 14372 webcamoid_8.1.0+dfsg-9.debian.tar.xz 09c6bb5061ab2df0af2ef0306d49aadc107746cec2876e270010ce4e91bfe855 17971 webcamoid_8.1.0+dfsg-9_amd64.buildinfo Files: 8cf5272f0310f2901d7dc472f12a0c19 2480 video optional webcamoid_8.1.0+dfsg-9.dsc
Processed: Liboping upstream ticket
Processing commands for cont...@bugs.debian.org: > forwarded 897790 https://github.com/octo/liboping/issues/38 Bug #897790 [src:liboping] liboping: ftbfs with GCC-8 Set Bug forwarded-to-address to 'https://github.com/octo/liboping/issues/38'. > stop Stopping processing here. Please contact me if you need assistance. -- 897790: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897790 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: forwarded manuel issue
Processing commands for cont...@bugs.debian.org: > forwarded 903524 https://github.com/benji-york/manuel/issues/12 Bug #903524 [src:manuel] manuel FTBFS with Python 3.7 as supported version Set Bug forwarded-to-address to 'https://github.com/benji-york/manuel/issues/12'. > thanks Stopping processing here. Please contact me if you need assistance. -- 903524: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903524 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: zoneminder: FTBFS with FFmpeg 4.0
Processing control commands: > block 896893 by -1 Bug #896893 [release.debian.org] transition: ffmpeg 896893 was blocked by: 888347 896824 888352 888350 904104 888363 888357 888388 888378 888385 888330 888364 888340 888343 888362 888338 888356 888373 888346 888386 896825 888382 888381 888336 888377 888389 888326 888380 888359 888358 888335 888344 888331 888329 888374 888360 888328 888349 888366 888345 888384 888325 896823 888367 888383 888376 888375 888332 888370 888365 888371 888372 888353 888337 888333 896893 was not blocking any bugs. Added blocking bug(s) of 896893: 904267 -- 896893: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896893 904267: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904267 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#904267: zoneminder: FTBFS with FFmpeg 4.0
Source: zoneminder
Version: 1.30.4+dfsg1-4
Severity: serious
Tags: sid buster ftbfs
User: debian-multime...@lists.debian.org
Usertags: ffmpeg-4.0-transition
Control: block 896893 by -1
Hi,
zoneminder FTBFS with FFmpeg 4.0 which was recently uploaded to
unstable. Unfortunately the last rebuild I did was before #887968 was
fixed so I never caught this package before the transition started.
Build log:
> /<>/zoneminder-1.30.4+dfsg1/src/zm_mpeg.cpp:243:19: error:
> 'CODEC_FLAG_QSCALE' was not declared in this scope
>c->flags |= CODEC_FLAG_QSCALE;
>^
> /<>/zoneminder-1.30.4+dfsg1/src/zm_mpeg.cpp:243:19: note: suggested
> alternative: 'AV_CODEC_FLAG_QSCALE'
>c->flags |= CODEC_FLAG_QSCALE;
>^
>AV_CODEC_FLAG_QSCALE
> /<>/zoneminder-1.30.4+dfsg1/src/zm_mpeg.cpp:268:19: error:
> 'CODEC_FLAG_GLOBAL_HEADER' was not declared in this scope
>c->flags |= CODEC_FLAG_GLOBAL_HEADER;
>^~~~
> /<>/zoneminder-1.30.4+dfsg1/src/zm_mpeg.cpp:268:19: note: suggested
> alternative: 'AV_CODEC_FLAG_GLOBAL_HEADER'
>c->flags |= CODEC_FLAG_GLOBAL_HEADER;
>^~~~
>AV_CODEC_FLAG_GLOBAL_HEADER
[...]
> /<>/zoneminder-1.30.4+dfsg1/src/zm_mpeg.cpp:428:22: error:
> 'AVFMT_RAWPICTURE' was not declared in this scope
>if ( !(of->flags & AVFMT_RAWPICTURE) )
> ^~~~
> /<>/zoneminder-1.30.4+dfsg1/src/zm_mpeg.cpp:428:22: note: suggested
> alternative: 'AVFMT_NOFILE'
>if ( !(of->flags & AVFMT_RAWPICTURE) )
> ^~~~
> AVFMT_NOFILE
[...]
> /<>/zoneminder-1.30.4+dfsg1/src/zm_mpeg.cpp:675:20: error:
> 'AVFMT_RAWPICTURE' was not declared in this scope
>if ( of->flags & AVFMT_RAWPICTURE )
> ^~~~
> Manifying 21 pod documents
> /<>/zoneminder-1.30.4+dfsg1/src/zm_mpeg.cpp:675:20: note: suggested
> alternative: 'AVFMT_NOFILE'
>if ( of->flags & AVFMT_RAWPICTURE )
> ^~~~
> AVFMT_NOFILE
UNTESTED patch I found on FreeBSD ports attached. From here:
https://svnweb.freebsd.org/ports/head/multimedia/zoneminder/files/patch-ffmpeg4?view=markup
James
Partially based on https://github.com/ZoneMinder/zoneminder/commit/e17bcb9178d0
--- src/zm_mpeg.cpp.orig 2017-05-09 14:54:48 UTC
+++ src/zm_mpeg.cpp
@@ -240,7 +240,11 @@ void VideoStream::SetupCodec( int colours, int subpixe
{
// Quality based bitrate control (VBR). Scale is 1..31 where 1 is best.
// This gets rid of artifacts in the beginning of the movie; and well, even quality.
+#if LIBAVCODEC_VERSION_CHECK(56, 35, 0, 64, 0)
+ c->flags |= AV_CODEC_FLAG_QSCALE;
+#else
c->flags |= CODEC_FLAG_QSCALE;
+#endif
c->global_quality = FF_QP2LAMBDA * (31 - (31 * (bitrate / 100.0)));
}
else
@@ -265,7 +269,11 @@ void VideoStream::SetupCodec( int colours, int subpixe
// some formats want stream headers to be separate
if ( of->flags & AVFMT_GLOBALHEADER )
+#if LIBAVCODEC_VERSION_CHECK(56, 35, 0, 64, 0)
+ c->flags |= AV_CODEC_FLAG_GLOBAL_HEADER;
+#else
c->flags |= CODEC_FLAG_GLOBAL_HEADER;
+#endif
}
else
{
@@ -425,7 +433,9 @@ void VideoStream::OpenStream( )
}
video_outbuf = NULL;
+#if !LIBAVFORMAT_VERSION_CHECK(57, 0, 0, 0, 0)
if ( !(of->flags & AVFMT_RAWPICTURE) )
+#endif
{
/* allocate output buffer */
/* XXX: API change will be done */
@@ -672,6 +682,7 @@ double VideoStream::ActuallyEncodeFrame( const uint8_t
AVPacket *pkt = packet_buffers[packet_index];
av_init_packet( pkt );
int got_packet = 0;
+#if !LIBAVFORMAT_VERSION_CHECK(57, 0, 0, 0, 0)
if ( of->flags & AVFMT_RAWPICTURE )
{
#if LIBAVCODEC_VERSION_CHECK(52, 30, 2, 30, 2)
@@ -685,6 +696,7 @@ double VideoStream::ActuallyEncodeFrame( const uint8_t
got_packet = 1;
}
else
+#endif
{
opicture_ptr->pts = c->frame_number;
opicture_ptr->quality = c->global_quality;
--- src/zm_sdp.cpp.orig 2017-05-09 14:54:48 UTC
+++ src/zm_sdp.cpp
@@ -483,7 +483,11 @@ AVFormatContext *SessionDescriptor::generateFormatCont
uint8_t *dest =
(uint8_t *)av_malloc(packet_size + sizeof(start_sequence) +
stream->codec->extradata_size +
+#if LIBAVCODEC_VERSION_CHECK(57, 0, 0, 0, 0)
+ AV_INPUT_BUFFER_PADDING_SIZE);
+#else
FF_INPUT_BUFFER_PADDING_SIZE);
+#endif
if(dest) {
if(stream->codec->extradata_size) {
// av_realloc?
@@ -494,7 +498,11 @@ AVFormatContext *SessionDescriptor::generateFormatCont
memcpy(dest+stream->codec->extradata_size, start_sequence, sizeof(start_sequence));
memcpy(dest+stream->codec->extradata_size+sizeof(start_sequence), decoded_packet, packet_size);
Bug#903074: Bug #903074 in foodcritic marked as pending
Control: tag -1 pending Hello, Bug #903074 in foodcritic reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below, and you can check the diff of the fix at: https://salsa.debian.org/ruby-team/foodcritic/commit/27eb9a65b630964fb2116302c300768dc1fa69cb Build-Depend on ronn, rather than ruby-ronn (Closes: #903074) (this message was generated automatically) -- Greetings https://bugs.debian.org/903074
Processed: Bug #903074 in foodcritic marked as pending
Processing control commands: > tag -1 pending Bug #903074 [src:foodcritic] foodcritic FTBFS: update Build-Depends: ruby-ronn -> ronn Added tag(s) pending. -- 903074: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903074 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#903352: pytools: FTBFS in buster/sid (dh_installdocs: Cannot find "README")
Control: tags -1 + patch patch at http://launchpadlibrarian.net/379605236/pytools_2018.1-1_2018.1-1ubuntu1.diff.gz
Processed: Re: pytools: FTBFS in buster/sid (dh_installdocs: Cannot find "README")
Processing control commands: > tags -1 + patch Bug #903352 [src:pytools] pytools: FTBFS in buster/sid (dh_installdocs: Cannot find "README") Added tag(s) patch. -- 903352: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903352 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tag aiscm ffmpeg 4.0 bug
Processing commands for cont...@bugs.debian.org: > user debian-multime...@lists.debian.org Setting user to debian-multime...@lists.debian.org (was jcowg...@jcowgill.uk). > usertag 904104 ffmpeg-4.0-transition There were no usertags set. Usertags are now: ffmpeg-4.0-transition. > block 896893 by 904104 Bug #896893 [release.debian.org] transition: ffmpeg 896893 was blocked by: 888376 888375 888389 888371 888336 888366 896824 888332 888362 888344 888338 888333 888374 888335 888340 888352 888365 888373 888343 888350 888360 888330 888388 888363 888377 888372 896825 888325 888381 888378 888364 888356 888337 888358 888382 888383 888347 888326 888353 888385 888357 888345 888328 888380 888370 888359 888349 896823 888367 888329 888384 888386 888346 888331 896893 was not blocking any bugs. Added blocking bug(s) of 896893: 904104 > thanks Stopping processing here. Please contact me if you need assistance. -- 896893: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896893 904104: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904104 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#904262: python-fabio builds for the default python3 version, but tests with all supported versions.
> your autopkg tests loops over all *supported* python versions, but you only > build the extension for the *default* python3 version. Try build-depending on > python3-all-dev instead and see that you have extensions built for both 3.6 > and > 3.7. Building in unstable, of course. But , I already depends on python3-all-dev ??? https://sources.debian.org/src/python-fabio/0.6.0+dfsg-1/debian/control/ I think that this is due to the python3.7 transtion which is ot over for python-fabio. right ?
Bug#904262: python-fabio builds for the default python3 version, but tests with all supported versions.
On 22.07.2018 14:51, PICCA Frederic-Emmanuel wrote: > Hello, Matthias, > > I do not understand this bug report. > > I use pybuild so fabio should be build for all python3 versions. > It is now FTBFS due to a problem with the cython package already reported. > #903909 this is unrelated. your autopkg tests loops over all *supported* python versions, but you only build the extension for the *default* python3 version. Try build-depending on python3-all-dev instead and see that you have extensions built for both 3.6 and 3.7. Building in unstable, of course.
Bug#904262: python-fabio builds for the default python3 version, but tests with all supported versions.
Hello, Matthias, I do not understand this bug report. I use pybuild so fabio should be build for all python3 versions. It is now FTBFS due to a problem with the cython package already reported. #903909 Cheers Frederic
Bug#904143: intel-vaapi-driver-shaders: make distclean deletes src/shaders/post_processing/gen5_6/null.g6b which is not regenerated
Control: severity -1 important On 2018-07-20 17:19:05, Andreas Beckmann wrote: > Source: intel-vaapi-driver-shaders > Version: 2.2.0-1 > Severity: serious > Justification: fails to build from source (but built successfully in the past) > > Hi, > > intel-vaapi-driver-shaders FTBFS twice in a row. The first build > succeeds, but the subsequent debian/rules clean causes > src/shaders/post_processing/gen5_6/null.g6b (and possibly more files) > to be deleted, which is not regenerated during the second build. Those kind of bugs were historically considered of severity important. I don't remember a release team decision to consider them as serious, so I'm downgrading it to important. It will be fixed in the next upload. Cheers > > From the attached logfile: > > [first build succeeded] > > [from debian/rules clean afte rthe first build] > > ... > Making distclean in gen5_6 > make[5]: Entering directory > '/build/intel-vaapi-driver-shaders-2.2.0/src/shaders/post_processing/gen5_6' > test -z "nv12_avs_nv12.g5s nv12_dn_nv12.g5s nv12_dndi_nv12.g5s > nv12_load_save_nv12.g5s nv12_load_save_pa.g5s nv12_load_save_pl3.g5s > nv12_load_save_rgbx.g5s nv12_scaling_nv12.g5s pa_load_save_pa.g5s > pa_load_save_nv > 12.g5s pa_load_save_pl3.g5s pl3_load_save_nv12.g5s pl3_load_save_pa.g5s > pl3_load_save_pl3.g5s rgbx_load_save_nv12.g5s nv12_avs_nv12.g6s > nv12_dn_nv12.g6s nv12_dndi_nv12.g6s nv12_load_save_nv12.g6s nv12_load_save_pa > .g6s nv12_load_save_pl3.g6s nv12_load_save_rgbx.g6s nv12_scaling_nv12.g6s > pa_load_save_pa.g6s pa_load_save_nv12.g6s pa_load_save_pl3.g6s > pl3_load_save_nv12.g6s pl3_load_save_pl3.g6s pl3_load_save_pa.g6s rgbx_load_ > save_nv12.g6s null.g4m null.g6m" || rm -f nv12_avs_nv12.g5s nv12_dn_nv12.g5s > nv12_dndi_nv12.g5s nv12_load_save_nv12.g5s nv12_load_save_pa.g5s > nv12_load_save_pl3.g5s nv12_load_save_rgbx.g5s nv12_scaling_nv12.g5s pa > _load_save_pa.g5s pa_load_save_nv12.g5s pa_load_save_pl3.g5s > pl3_load_save_nv12.g5s pl3_load_save_pa.g5s pl3_load_save_pl3.g5s > rgbx_load_save_nv12.g5s nv12_avs_nv12.g6s nv12_dn_nv12.g6s nv12_dndi_nv12.g6s > nv12_loa > d_save_nv12.g6s nv12_load_save_pa.g6s nv12_load_save_pl3.g6s > nv12_load_save_rgbx.g6s nv12_scaling_nv12.g6s pa_load_save_pa.g6s > pa_load_save_nv12.g6s pa_load_save_pl3.g6s pl3_load_save_nv12.g6s > pl3_load_save_pl3.g6 > s pl3_load_save_pa.g6s rgbx_load_save_nv12.g6s null.g4m null.g6m > rm -rf .libs _libs > rm -f *.lo > test -z "" || rm -f > test . = "." || test -z "" || rm -f > test -z "nv12_avs_nv12.g4b.gen5 nv12_dn_nv12.g4b.gen5 nv12_dndi_nv12.g4b.gen5 > nv12_load_save_nv12.g4b.gen5 nv12_load_save_pa.g4b.gen5 > nv12_load_save_pl3.g4b.gen5 nv12_load_save_rgbx.g4b.gen5 > nv12_scaling_nv12.g4b. > gen5 pa_load_save_pa.g4b.gen5 pa_load_save_nv12.g4b.gen5 > pa_load_save_pl3.g4b.gen5 pl3_load_save_nv12.g4b.gen5 > pl3_load_save_pa.g4b.gen5 pl3_load_save_pl3.g4b.gen5 > rgbx_load_save_nv12.g4b.gen5 nv12_avs_nv12.g6b n > v12_dn_nv12.g6b nv12_dndi_nv12.g6b nv12_load_save_nv12.g6b > nv12_load_save_pa.g6b nv12_load_save_pl3.g6b nv12_load_save_rgbx.g6b > nv12_scaling_nv12.g6b pa_load_save_pa.g6b pa_load_save_nv12.g6b > pa_load_save_pl3.g6b > pl3_load_save_nv12.g6b pl3_load_save_pl3.g6b pl3_load_save_pa.g6b > rgbx_load_save_nv12.g6b null.g4b.gen5 null.g6b" || rm -f > nv12_avs_nv12.g4b.gen5 nv12_dn_nv12.g4b.gen5 nv12_dndi_nv12.g4b.gen5 > nv12_load_save_nv12. > g4b.gen5 nv12_load_save_pa.g4b.gen5 nv12_load_save_pl3.g4b.gen5 > nv12_load_save_rgbx.g4b.gen5 nv12_scaling_nv12.g4b.gen5 > pa_load_save_pa.g4b.gen5 pa_load_save_nv12.g4b.gen5 pa_load_save_pl3.g4b.gen5 > pl3_load_save_n > v12.g4b.gen5 pl3_load_save_pa.g4b.gen5 pl3_load_save_pl3.g4b.gen5 > rgbx_load_save_nv12.g4b.gen5 nv12_avs_nv12.g6b nv12_dn_nv12.g6b > nv12_dndi_nv12.g6b nv12_load_save_nv12.g6b nv12_load_save_pa.g6b > nv12_load_save_pl > 3.g6b nv12_load_save_rgbx.g6b nv12_scaling_nv12.g6b pa_load_save_pa.g6b > pa_load_save_nv12.g6b pa_load_save_pl3.g6b pl3_load_save_nv12.g6b > pl3_load_save_pl3.g6b pl3_load_save_pa.g6b rgbx_load_save_nv12.g6b null.g4 > b.gen5 null.g6b > rm -f Makefile > make[5]: Leaving directory > '/build/intel-vaapi-driver-shaders-2.2.0/src/shaders/post_processing/gen5_6' > ... > > [building the source package after the first build+clean causes dpkg-source > to report many deleted files] > > ... > dpkg-source: warning: ignoring deletion of file > src/shaders/post_processing/gen9/pl2_to_rgbx.g9b, use --include-removal to > override > dpkg-source: warning: ignoring deletion of file > src/shaders/post_processing/gen9/pl2_to_pl2.g9b, use --include-removal to > override > dpkg-source: warning: ignoring deletion of file > src/shaders/post_processing/gen5_6/nv12_avs_nv12.g4b.gen5, use > --include-removal to override > dpkg-source: warning: ignoring deletion of file > src/shaders/post_processing/gen5_6/rgbx_load_save_nv12.g4b.gen5, use > --include-removal to override > dpkg-source: warning: ignoring deletion of file >
Processed: Re: Bug#904143: intel-vaapi-driver-shaders: make distclean deletes src/shaders/post_processing/gen5_6/null.g6b which is not regenerated
Processing control commands: > severity -1 important Bug #904143 [src:intel-vaapi-driver-shaders] intel-vaapi-driver-shaders: make distclean deletes src/shaders/post_processing/gen5_6/null.g6b which is not regenerated Severity set to 'important' from 'serious' -- 904143: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904143 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#904263: python-fisx builds for the default python3 version, but tests with all supported versions.
Package: src:python-fisx Version: 1.1.4-1 Severity: serious Tags: sid buster python-fisx builds for the default python3 version, but tests with all supported versions, not finding the extensions for the non-default version. This seems to be the case for many packages packaged by this maintainer.
Bug#904255: network-manager-vpnc: diff for NMU version 1.2.4-7.1
On Sun, Jul 22, 2018 at 01:54:47PM +0200, Salvatore Bonaccorso wrote:
> Control: tags 904255 + patch
>
>
> Dear maintainer,
>
> I've prepared an NMU for network-manager-vpnc (versioned as
> 1.2.4-7.1). It is not yet uploaded (to any delayed queue, if you want
> to do the upload yourself).
And actually, if cherry-picking the patch it might be advisable to
revert in the patch the "Use Unicode in translatable strings" change.
Regards,
Salvatore
From: Lubomir Rintel
Date: Fri, 13 Jul 2018 18:51:04 +0200
Subject: service: disallow newlinies in configuration values (CVE-2018-10900)
Origin: https://gitlab.gnome.org/GNOME/NetworkManager-vpnc/commit/07ac18a32b4e361a27ef48ac757d36cbb46e8e12
Bug-Debian-Security: https://security-tracker.debian.org/tracker/CVE-2018-10900
Bug-Debian: https://bugs.debian.org/904255
Bug-SUSE: https://bugzilla.novell.com/show_bug.cgi?id=1101147
Bug-RedHat: https://bugzilla.redhat.com/show_bug.cgi?id=1605919
The vpnc configuration format doesn't allow those. vpnc(8):
The values start exactly one space after the keywords, and run to the end
of line. This lets you put any kind of weird character (except CR, LF and
NUL) in your strings
We have no choice but to reject them. If we didn't it would allow the
user to inject arbitrary configuration directives with potential
security implications.
https://pulsesecurity.co.nz/advisories/NM-VPNC-Privesc
Reported by: Denis Andzakovic
[carnil: Backport to 1.2.4: Revert the " Use Unicode in translatable strings"
change which is not yet in 1.2.4]
---
src/nm-vpnc-service.c | 9 -
1 file changed, 8 insertions(+), 1 deletion(-)
diff --git a/src/nm-vpnc-service.c b/src/nm-vpnc-service.c
index 364ff7c..802f5ac 100644
--- a/src/nm-vpnc-service.c
+++ b/src/nm-vpnc-service.c
@@ -209,7 +209,14 @@ validate_one_property (const char *key, const char *value, gpointer user_data)
break; /* technically valid, but unused */
case ITEM_TYPE_STRING:
case ITEM_TYPE_SECRET:
- break; /* valid */
+ if (strchr (value, '\n') || strchr (value, '\r')) {
+ g_set_error (info->error,
+ NM_VPN_PLUGIN_ERROR,
+ NM_VPN_PLUGIN_ERROR_BAD_ARGUMENTS,
+ _("property '%s' contains a newline character"),
+ key);
+ }
+ break;
case ITEM_TYPE_PATH:
if ( !value
|| !strlen (value)
--
2.18.0
Bug#904262: python-fabio builds for the default python3 version, but tests with all supported versions.
Package: src:python-fabio Version: 0.6.0+dfsg-1 Severity: serious Tags: sid buster python-fabio builds for the default python3 version, but tests with all supported versions, not finding the extensions for the non-default version.
Bug#897699: marked as done (aeskulap: ftbfs with GCC-8)
Your message dated Sun, 22 Jul 2018 12:18:51 + with message-id and subject line Bug#897699: fixed in aeskulap 0.2.2b1+git20161206-5 has caused the Debian Bug report #897699, regarding aeskulap: ftbfs with GCC-8 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.) -- 897699: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897699 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:aeskulap Version: 0.2.2b1+git20161206-4 Severity: normal Tags: sid buster User: debian-...@lists.debian.org Usertags: ftbfs-gcc-8 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-8/g++-8, but succeeds to build with gcc-7/g++-7. The severity of this report will be raised before the buster release. The full build log can be found at: http://aws-logs.debian.net/2018/05/01/gcc8/aeskulap_0.2.2b1+git20161206-4_unstable_gcc8.log.gz The last lines of the build log are at the end of this report. To build with GCC 8, either set CC=gcc-8 CXX=g++-8 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-8/porting_to.html [...] from fileloader.cpp:24: /usr/include/dcmtk/config/osconfig.h:825: note: this is the location of the previous definition #define PACKAGE_NAME "dcmtk" In file included from ../configuration/aconfiguration.h:29, from poolservers.h:30, from imagepool.h:28, from fileloader.cpp:27: ../config.h:97: warning: "PACKAGE_STRING" redefined #define PACKAGE_STRING "aeskulap 0.2.2-beta1" In file included from /usr/include/dcmtk/dcmdata/dcfilefo.h:26, from fileloader.cpp:24: /usr/include/dcmtk/config/osconfig.h:828: note: this is the location of the previous definition #define PACKAGE_STRING "" In file included from ../configuration/aconfiguration.h:29, from poolservers.h:30, from imagepool.h:28, from fileloader.cpp:27: ../config.h:106: warning: "PACKAGE_VERSION" redefined #define PACKAGE_VERSION "0.2.2-beta1" In file included from /usr/include/dcmtk/dcmdata/dcfilefo.h:26, from fileloader.cpp:24: /usr/include/dcmtk/config/osconfig.h:843: note: this is the location of the previous definition #define PACKAGE_VERSION "3.6.2" In file included from imagepool.h:25, from fileloader.cpp:27: poolinstance.h:46:81: error: 'void ImagePool::remove_instance(const Glib::RefPtr&)' should have been declared inside 'ImagePool' friend void ImagePool::remove_instance(const Glib::RefPtr&); ^ make[3]: *** [Makefile:605: fileloader.lo] Error 1 make[3]: Leaving directory '/<>/aeskulap-0.2.2b1+git20161206/imagepool' make[3]: Entering directory '/<>/aeskulap-0.2.2b1+git20161206/imagepool' /bin/bash ../libtool --tag=CXX --mode=compile g++ -DHAVE_CONFIG_H -I. -I.. -I../configuration -DHAVE_CONFIG_H -I/usr/include -pthread -I/usr/include/gtkmm-2.4 -I/usr/lib/x86_64-linux-gnu/gtkmm-2.4/include -I/usr/include/atkmm-1.6 -I/usr/include/gtk-unix-print-2.0 -I/usr/include/gtk-2.0 -I/usr/include/gdkmm-2.4 -I/usr/lib/x86_64-linux-gnu/gdkmm-2.4/include -I/usr/include/giomm-2.4 -I/usr/lib/x86_64-linux-gnu/giomm-2.4/include -I/usr/include/pangomm-1.4 -I/usr/lib/x86_64-linux-gnu/pangomm-1.4/include -I/usr/include/glibmm-2.4 -I/usr/lib/x86_64-linux-gnu/glibmm-2.4/include -I/usr/include/cairomm-1.0 -I/usr/lib/x86_64-linux-gnu/cairomm-1.0/include -I/usr/include/sigc++-2.0 -I/usr/lib/x86_64-linux-gnu/sigc++-2.0/include -I/usr/include/gtk-2.0 -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 -I/us r/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/fribidi
Processed: tagging 904255
Processing commands for cont...@bugs.debian.org: > tags 904255 + fixed-upstream Bug #904255 [src:network-manager-vpnc] network-manager-vpnc: CVE-2018-10900: privilege escalation Added tag(s) fixed-upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 904255: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904255 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#904255: network-manager-vpnc: diff for NMU version 1.2.4-7.1
Control: tags 904255 + patch
Dear maintainer,
I've prepared an NMU for network-manager-vpnc (versioned as
1.2.4-7.1). It is not yet uploaded (to any delayed queue, if you want
to do the upload yourself).
Regards,
Salvatore
diff -Nru network-manager-vpnc-1.2.4/debian/changelog network-manager-vpnc-1.2.4/debian/changelog
--- network-manager-vpnc-1.2.4/debian/changelog 2018-04-08 16:51:44.0 +0200
+++ network-manager-vpnc-1.2.4/debian/changelog 2018-07-22 13:17:19.0 +0200
@@ -1,3 +1,11 @@
+network-manager-vpnc (1.2.4-7.1) unstable; urgency=high
+
+ * Non-maintainer upload.
+ * service: disallow newlinies in configuration values (CVE-2018-10900)
+(Closes: #904255)
+
+ -- Salvatore Bonaccorso Sun, 22 Jul 2018 13:17:19 +0200
+
network-manager-vpnc (1.2.4-7) unstable; urgency=medium
* Set Rules-Requires-Root to no
diff -Nru network-manager-vpnc-1.2.4/debian/patches/series network-manager-vpnc-1.2.4/debian/patches/series
--- network-manager-vpnc-1.2.4/debian/patches/series 2018-04-08 16:51:44.0 +0200
+++ network-manager-vpnc-1.2.4/debian/patches/series 2018-07-22 13:17:19.0 +0200
@@ -1 +1,2 @@
# Debian patches for network-manager-vpnc
+service-disallow-newlinies-in-configuration-values-C.patch
diff -Nru network-manager-vpnc-1.2.4/debian/patches/service-disallow-newlinies-in-configuration-values-C.patch network-manager-vpnc-1.2.4/debian/patches/service-disallow-newlinies-in-configuration-values-C.patch
--- network-manager-vpnc-1.2.4/debian/patches/service-disallow-newlinies-in-configuration-values-C.patch 1970-01-01 01:00:00.0 +0100
+++ network-manager-vpnc-1.2.4/debian/patches/service-disallow-newlinies-in-configuration-values-C.patch 2018-07-22 13:17:19.0 +0200
@@ -0,0 +1,49 @@
+From: Lubomir Rintel
+Date: Fri, 13 Jul 2018 18:51:04 +0200
+Subject: service: disallow newlinies in configuration values (CVE-2018-10900)
+Origin: https://gitlab.gnome.org/GNOME/NetworkManager-vpnc/commit/07ac18a32b4e361a27ef48ac757d36cbb46e8e12
+Bug-Debian-Security: https://security-tracker.debian.org/tracker/CVE-2018-10900
+Bug-Debian: https://bugs.debian.org/904255
+Bug-SUSE: https://bugzilla.novell.com/show_bug.cgi?id=1101147
+Bug-RedHat: https://bugzilla.redhat.com/show_bug.cgi?id=1605919
+
+The vpnc configuration format doesn't allow those. vpnc(8):
+
+ The values start exactly one space after the keywords, and run to the end
+ of line. This lets you put any kind of weird character (except CR, LF and
+ NUL) in your strings
+
+We have no choice but to reject them. If we didn't it would allow the
+user to inject arbitrary configuration directives with potential
+security implications.
+
+https://pulsesecurity.co.nz/advisories/NM-VPNC-Privesc
+
+Reported by: Denis Andzakovic
+---
+ src/nm-vpnc-service.c | 9 -
+ 1 file changed, 8 insertions(+), 1 deletion(-)
+
+diff --git a/src/nm-vpnc-service.c b/src/nm-vpnc-service.c
+index 364ff7c..802f5ac 100644
+--- a/src/nm-vpnc-service.c
b/src/nm-vpnc-service.c
+@@ -209,7 +209,14 @@ validate_one_property (const char *key, const char *value, gpointer user_data)
+ break; /* technically valid, but unused */
+ case ITEM_TYPE_STRING:
+ case ITEM_TYPE_SECRET:
+- break; /* valid */
++ if (strchr (value, '\n') || strchr (value, '\r')) {
++ g_set_error (info->error,
++ NM_VPN_PLUGIN_ERROR,
++ NM_VPN_PLUGIN_ERROR_BAD_ARGUMENTS,
++ _("property ???%s??? contains a newline character"),
++ key);
++ }
++ break;
+ case ITEM_TYPE_PATH:
+ if ( !value
+ || !strlen (value)
+--
+2.18.0
+
Processed: network-manager-vpnc: diff for NMU version 1.2.4-7.1
Processing control commands: > tags 904255 + patch Bug #904255 [src:network-manager-vpnc] network-manager-vpnc: CVE-2018-10900: privilege escalation Ignoring request to alter tags of bug #904255 to the same tags previously set -- 904255: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904255 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: brotli: autopkgtest needs update for python3.7 in supported versions
Processing control commands: > severity -1 serious Bug #903923 [src:brotli] brotli: autopkgtest needs update for python3.7 in supported versions Severity set to 'serious' from 'normal' -- 903923: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903923 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#904255: network-manager-vpnc: CVE-2018-10900: privilege escalation
Source: network-manager-vpnc Version: 1.2.4-1 Severity: grave Tags: patch security upstream Hi, The following vulnerability was published for network-manager-vpnc. CVE-2018-10900[0]: local privilege escalation A user with enough privileges to create the vpnc connection entry (group netdev for instance), can use the flaw in network-manager-vpnc to escalate privileges. 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-2018-10900 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-10900 [1] https://pulsesecurity.co.nz/advisories/NM-VPNC-Privesc Update for stretch is already in preparation. Regards, Salvatore
Bug#897768: hmat-oss: ftbfs with GCC-8
Control: tags -1 fixed-upstream On Fri, 04 May 2018 12:21:56 + Matthias Klose wrote: > Package: src:hmat-oss > Version: 1.2.0-2 > Severity: normal > Tags: sid buster > User: debian-...@lists.debian.org > Usertags: ftbfs-gcc-8 > [...] > /<>/src/full_matrix.cpp:904:11: error: 'void* memset(void*, int, > size_t)' clearing an object of non-trivial type 'struct std::complex'; > use assignment or value-initialization instead [-Werror=class-memaccess] Upstream claims to have fixed this error: https://github.com/jeromerobert/hmat-oss/commit/9b614cfee6974f4103636402ce3007be336a55b7 Cheers, Juhani
Processed: Re: Bug#897768: hmat-oss: ftbfs with GCC-8
Processing control commands: > tags -1 fixed-upstream Bug #897768 [src:hmat-oss] hmat-oss: ftbfs with GCC-8 Added tag(s) fixed-upstream. -- 897768: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897768 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#897756: 897775 & 897756 *: ftbfs with GCC-8 (because of an error in insighttooklit4)
Hello Andreas, you marked these two bugs as found in insighttoolkit4/4.12.2-dfsg1-2, but they should actually have been merged with #897899 (maybe I did something wrong theer), a bug that was closed by exactly this version. Could you ellaborate why do you tagged these bugs like this? I just re- checked and #897775 was indeed fixed by this version. many thanks, Gert
Processed: upstream pull request
Processing commands for cont...@bugs.debian.org: > forwarded 897747 https://github.com/wolfcw/libfaketime/pull/161 Bug #897747 [src:faketime] faketime: ftbfs with GCC-8 Set Bug forwarded-to-address to 'https://github.com/wolfcw/libfaketime/pull/161'. > tags 897747 fixed-upstream Bug #897747 [src:faketime] faketime: ftbfs with GCC-8 Added tag(s) fixed-upstream. > stop Stopping processing here. Please contact me if you need assistance. -- 897747: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897747 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: upstream ticket for Bug#897716
Processing commands for cont...@bugs.debian.org: > forwarded 897716 https://github.com/marbl/canu/issues/927 Bug #897716 [src:canu] canu: ftbfs with GCC-8 Set Bug forwarded-to-address to 'https://github.com/marbl/canu/issues/927'. > tags 897716 fixed-upstream Bug #897716 [src:canu] canu: ftbfs with GCC-8 Added tag(s) fixed-upstream. > stop Stopping processing here. Please contact me if you need assistance. -- 897716: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897716 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#897714: bzrtp: ftbfs with GCC-8
On Fri, 04 May 2018 12:20:56 + Matthias Klose wrote: > Package: src:bzrtp > Version: 1.0.6-2 > Severity: normal > Tags: sid buster > User: debian-...@lists.debian.org > Usertags: ftbfs-gcc-8 > /<>/src/stateMachine.c: In function 'bzrtp_deriveKeysFromS0': > /<>/src/stateMachine.c:2057:234: error: cast between > incompatible function types Here are the types from one warning, which look quite incompatible to me: void (*)(const unsigned char *, long unsigned int, const unsigned char *, long unsigned int, unsigned char, unsigned char *) void (*)(unsigned char *, unsigned char, unsigned char *, unsigned int, unsigned char, unsigned char *) For now, there's an upstream commit that suppresses the errors and adds some FIXME comments. https://gitlab.linphone.org/BC/public/bzrtp/commit/e86b99fdc51c95f4d4997d7fdcfdfe0d1589ca92 Regards, Juhani
Bug#903895: marked as done (colord-kde: build-depends on no longer available plasma-framework-dev)
Your message dated Sun, 22 Jul 2018 10:04:11 + with message-id and subject line Bug#903895: fixed in colord-kde 0.5.0-3 has caused the Debian Bug report #903895, regarding colord-kde: build-depends on no longer available plasma-framework-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.) -- 903895: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903895 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: colord-kde Version: 0.5.0-2 Severity: serious Justification: fails to build from source Hi, colord-kde cannot be built any more since plasma-framework-dev is gone. Andreas --- End Message --- --- Begin Message --- Source: colord-kde Source-Version: 0.5.0-3 We believe that the bug you reported is fixed in the latest version of colord-kde, 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 903...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Pino Toscano (supplier of updated colord-kde 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: Sun, 22 Jul 2018 11:45:33 +0200 Source: colord-kde Binary: colord-kde Architecture: source Version: 0.5.0-3 Distribution: experimental Urgency: medium Maintainer: Debian/Kubuntu Qt/KDE Maintainers Changed-By: Pino Toscano Description: colord-kde - Color management for KDE Closes: 903895 Changes: colord-kde (0.5.0-3) experimental; urgency=medium . * Team upload. * Switch Vcs-* fields to salsa.debian.org. * Switch away from (private) debian-qt-kde.mk to the dh sequencer with kf5 addon - make sure to link in as-needed mode * Drop transitional kio-dev, and plasma-framework-dev build dependencies; their non-transitional counterparts are already specified. (Closes: #903895) * Bump the debhelper compatibility to 11: - bump the debhelper build dependency to 11~ - bump compat to 11 * Bump Standards-Version to 4.1.5, no changes required. * Simplify watch file, and switch it to https. * Switch Format in copyright to https, and make it valid. Checksums-Sha1: 1b79306bde43e81cbbf7511a67e792446f0e5d55 2390 colord-kde_0.5.0-3.dsc 434b1997d1742a37d90a9dbb516633b8b3c063ef 2864 colord-kde_0.5.0-3.debian.tar.xz a376fd7c50c5d8507ab823ba5646fe7e07880628 20420 colord-kde_0.5.0-3_source.buildinfo Checksums-Sha256: 0b5b8759c611519f23462245b8e83bb689405f58592b16019bcd9af75b9d6eab 2390 colord-kde_0.5.0-3.dsc 0bd471003fb2991f9cc666900ff393169c84ea11c98c4764bb9dd9ae44de8e02 2864 colord-kde_0.5.0-3.debian.tar.xz b20010f80b5ef22e0722eaf061be8fd8e99f5645ebeba183798225260aed1163 20420 colord-kde_0.5.0-3_source.buildinfo Files: ad1756542e2015e7a437d6897b78ada4 2390 kde optional colord-kde_0.5.0-3.dsc 127616379eb265c6470a4e26ce318556 2864 kde optional colord-kde_0.5.0-3.debian.tar.xz 9d9dcd8b1eccf5185c42033920df3a30 20420 kde optional colord-kde_0.5.0-3_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEXyqfuC+mweEHcAcHLRkciEOxP00FAltUUmwACgkQLRkciEOx P03HmQ/9G2NMq+428CEGxEFSfL5cPlcDT5GboOH6ARKwq9Ye1rmUAlG7AEiib4e/ km5Gc47O1k/YWNXWbrqGAeZPHX++qB1UQpzsjuXqZYil1RsvDjJzRdvElbULzlvB LhPleJGHfNCHk2hwMc15gmPVatKT/abcpuzr1YxvfOmIgEPN9SGnUJ7+F2PK6I8q NuUV6kIdRWcXI9PbOsqG88o0wooxxDbiyfHWUl0Lg3OS+JfMtVxMS+Z9nHmVypSD HGNZ+DYs5BxAXsKRUNkrWxAlGxeg0BExllPrfZvWID/xrH/s3FwefHmNgzO+RACJ psJWlq5u/rC3kxYDd60xf1psMy/nQaQrbUcdwBcrureEkMg90xukYDotNQt7rUcQ 1VqFZ3VP8JxSkshj480uLr1+9YNt9YagElBpK+h1aaBp4MTIQR1Q6Z77JNSp42ba RvBOlR03P81UTCImONQzqpqoKgQ5a3nPQbWcavc3XRIrol3o/7un5MklOlvbXna5 u5AaggMd81C31z0gF8zDsK5BCLYSQZ5eeLcXBxF3kaCYBBTzkgF0SAhSplB0ms+9 vRLpc80X/bVz0zLSG96dDFFL5i2rcHuXmDLRrNp5+/PTRwYcu0DGsNrjw7WhMN89 WJ13QKzijuXBcaj5gIt7YhPmfBBXt+qfqYNc+1yxLwMmkJtLOHM= =wHuh -END PGP SIGNATURE End Message ---
Bug#903066: marked as done (decopy FTBFS: update Build-Depends: ruby-ronn -> ronn)
Your message dated Sun, 22 Jul 2018 09:19:00 + with message-id and subject line Bug#903066: fixed in decopy 0.2.4.1-1 has caused the Debian Bug report #903066, regarding decopy FTBFS: update Build-Depends: ruby-ronn -> ronn 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.) -- 903066: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903066 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: decopy Version: 0.2.3-2 Severity: serious Since ronn got split out of ruby-ronn, decopy fails to build from source. It was not possible to have ruby-ronn temporarily depend on ronn, because that would have created a dependency cycle. Please update Build-Depends and replace ruby-ronn with ronn as decopy uses the command line tool. Helmut --- End Message --- --- Begin Message --- Source: decopy Source-Version: 0.2.4.1-1 We believe that the bug you reported is fixed in the latest version of decopy, 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 903...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Maximiliano Curia (supplier of updated decopy 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: Sun, 22 Jul 2018 11:00:46 +0200 Source: decopy Binary: decopy Architecture: source Version: 0.2.4.1-1 Distribution: unstable Urgency: medium Maintainer: Maximiliano Curia Changed-By: Maximiliano Curia Description: decopy - Automatic debian/copyright Generator Closes: 903066 Changes: decopy (0.2.4.1-1) unstable; urgency=medium . * New upstream release (0.2.4.1) * Depend on libimage-exiftool-perl, drop exiv2 * Build depend on ronn instead of ruby-ronn. Thanks to Helmut Grohne for the report (Closes: 903066) * Drop upstream applied patch * Update lintian-overrides * Release to unstable Checksums-Sha1: fae15598eb5f836e458ad5b545646df82b2e5cba 1943 decopy_0.2.4.1-1.dsc 6f403ef7d797e6b9b9e94d7ff6fb885b1d26e80b 837407 decopy_0.2.4.1.orig.tar.gz 80cb6865741317788418ac3f6fb3d8ef90b72943 2520 decopy_0.2.4.1-1.debian.tar.xz 7e1e8af0324a8545dc4aaed7df5146a5b062a60f 7645 decopy_0.2.4.1-1_source.buildinfo Checksums-Sha256: 714d589384586c9baf70d34bf06b13e94f48514ec4dea06d7d24138c9e19e224 1943 decopy_0.2.4.1-1.dsc 26bc443e57ba4d6bcae9b0d1698897c355d188a3a288d25357608a28cfa2bc41 837407 decopy_0.2.4.1.orig.tar.gz 83ad220fbc8268a176a31ef745c66f66e9dd7548b7acd418acba6735c0935378 2520 decopy_0.2.4.1-1.debian.tar.xz 96e5ee55e8d0738a637aca3512701080082f9322d6b551aff0fe11ca6fc05e6d 7645 decopy_0.2.4.1-1_source.buildinfo Files: 9431cfa231cd7328020927e1686801c0 1943 devel optional decopy_0.2.4.1-1.dsc 6003907182313b5b4160c629e9d7765b 837407 devel optional decopy_0.2.4.1.orig.tar.gz fbc520447b9df4d69c6350340717b9f5 2520 devel optional decopy_0.2.4.1-1.debian.tar.xz eda217c5778e0032323ad6a75ea631ed 7645 devel optional decopy_0.2.4.1-1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE+JIdOnQEyG4RNSIVxxl2mbKbIyoFAltUR+gACgkQxxl2mbKb IyoQ1hAAtZTCEkhYYbKx/vOZeM+bEOxWWtL305WOElTpLGadN8YqyKd7NAyiPGP0 lOWYL23LQ9ls6kLEVxQrY3VBpN0LAXGxE+1SGN1W4RePZVyePQarZtCaASePZN+b 8dBCn06HVOaULru49pDj+GrBbIS1d8O0x8qhLRUctQwE24IQPbR6GrlupWHWW+H5 rAJXhl0N+Q/FVYSnKSA8w/W8wGAH7D7XyqHmSxtmh/AEIdkEklXzP1ZtfbFi80zr hx8Epf0lEVQTh8WZ/RElEiLiroDR/DvxIjWg8tVoq7HbCq3p8Yg1QcHVeCLQOAYB IE03pJPvF99uIKSov5FMstq5aVSbjR6cyYpU8QqzD8VPXij1Jm2buP3XPR11Ebsb mI8QtFVBjBnRXnCgkj92WF/ekbqi6uuUEj3VzIbLq+habmnfLxldFnKi2x2f6Lpc qg5/dK8YlQXLGgiPWt8zvd9CkJluA96jhDehQ5jG670UdSTjQCMm5qvZ0DYzAm7P 4G025PQ6RRE9k0l+9ue5S+3e17jaarqgAGQ/0miFrwuBGacXf+8hD/NigOL8ZeJX 1mUaWeoJmt9QrbcREVgb+PWnQ4jaCMcYg4AxVgg5rwo1+lnSjJO8o/IIZMtHWWP7 1blAFR3TL6gzLCnLZ8SA+g2EpWRr3yBsIldsdaysvxz8CH43Lu8= =qWM/ -END PGP SIGNATURE End Message ---
Bug#897471: marked as done (python-magic: FTBFS: dh_auto_test: pybuild --test -i python{version} -p 2.7 returned exit code 13)
Your message dated Sun, 22 Jul 2018 08:42:38 +
with message-id
and subject line Bug#897471: fixed in python-magic 2:0.4.15-2
has caused the Debian Bug report #897471,
regarding python-magic: FTBFS: dh_auto_test: pybuild --test -i python{version}
-p 2.7 returned exit code 13
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.)
--
897471: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897471
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-magic
Version: 2:0.4.15-1
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20180502 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part (hopefully):
> debian/rules build
> dh build --with python2,python3 --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:217: python2.7 setup.py config
> running config
> I: pybuild base:217: python3.6 setup.py config
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:217: /usr/bin/python setup.py build
> running build
> running build_py
> creating /<>/.pybuild/cpython2_2.7/build/magic
> copying magic/compat.py -> /<>/.pybuild/cpython2_2.7/build/magic
> copying magic/__init__.py ->
> /<>/.pybuild/cpython2_2.7/build/magic
> I: pybuild base:217: /usr/bin/python3 setup.py build
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.6/build/magic
> copying magic/compat.py -> /<>/.pybuild/cpython3_3.6/build/magic
> copying magic/__init__.py ->
> /<>/.pybuild/cpython3_3.6/build/magic
>dh_auto_test -O--buildsystem=pybuild
> I: pybuild base:217: python2.7 setup.py test
> running test
> running egg_info
> creating python_magic.egg-info
> writing python_magic.egg-info/PKG-INFO
> writing top-level names to python_magic.egg-info/top_level.txt
> writing dependency_links to python_magic.egg-info/dependency_links.txt
> writing manifest file 'python_magic.egg-info/SOURCES.txt'
> reading manifest file 'python_magic.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> writing manifest file 'python_magic.egg-info/SOURCES.txt'
> running build_ext
> test_descriptions (test.test.MagicTest) ... FAIL
> test_errors (test.test.MagicTest) ... ok
> test_from_buffer_str_and_bytes (test.test.MagicTest) ... ok
> test_keep_going (test.test.MagicTest) ... ok
> test_mime_encodings (test.test.MagicTest) ... ok
> test_mime_types (test.test.MagicTest) ... ok
> test_open_file (test.test.MagicTest) ... ok
> test_rethrow (test.test.MagicTest) ... ok
> test_detect_from_content (test.libmagic_test.MagicTestCase) ... ok
> test_detect_from_filename (test.libmagic_test.MagicTestCase) ... ok
> test_detect_from_fobj (test.libmagic_test.MagicTestCase) ... ok
>
> ==
> FAIL: test_descriptions (test.test.MagicTest)
> --
> Traceback (most recent call last):
> File "/<>/test/test.py", line 73, in test_descriptions
> 'text.txt': 'ASCII text',
> File "/<>/test/test.py", line 32, in assert_values
> self.assertTrue(False, "no match for " + repr(expected_value))
> AssertionError: no match for ('gzip compressed data, was "test", from Unix,
> last modified: Sun Jun 29 01:32:52 2008', 'gzip compressed data, was "test",
> last modified: Sun Jun 29 01:32:52 2008, from Unix')
>
> --
> Ran 11 tests in 0.044s
>
> FAILED (failures=1)
> Test failed:
> error: Test failed: failures=1>
> E: pybuild pybuild:336: test: plugin distutils failed with: exit code=1:
> python2.7 setup.py test
> dh_auto_test: pybuild --test -i python{version} -p 2.7 returned exit code 13
The full build log is available from:
http://aws-logs.debian.net/2018/05/02/python-magic_0.4.15-1_unstable.log
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: python-magic
Source-Version: 2:0.4.15-2
We believe that the bug you reported is fixed in the latest version of
python-magic, which is due to be installed in the
Bug#890691: marked as done (ruby-bio FTBFS with ruby 2.5)
Your message dated Sun, 22 Jul 2018 16:02:52 +0800 with message-id <20180722080251.GA20239@tx.local> and subject line Re: ruby-bio FTBFS with ruby 2.5 has caused the Debian Bug report #890691, regarding ruby-bio FTBFS with ruby 2.5 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.) -- 890691: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890691 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ruby-bio Version: 1.5.0-2 Severity: serious Tags: buster sid https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/ruby-bio.html ... ┌──┐ │ Run tests for ruby2.5 from debian/ruby-tests.rb │ └──┘ RUBYLIB=/build/1st/ruby-bio-1.5.0/debian/ruby-bio/usr/lib/ruby/vendor_ruby:. GEM_PATH=debian/ruby-bio/usr/share/rubygems-integration/all:/var/lib/gems/2.5.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.5.0:/usr/share/rubygems-integration/2.5.0:/usr/share/rubygems-integration/all ruby2.5 debian/ruby-tests.rb Loaded suite debian/ruby-tests Started ... .../build/1st/ruby-bio-1.5.0/test/unit/bio/test_alignment.rb:631: warning: constant ::Fixnum is deprecated /build/1st/ruby-bio-1.5.0/test/unit/bio/test_alignment.rb:633: warning: constant ::Fixnum is deprecated ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... .../build/1st/ruby-bio-1.5.0/lib/bio/util/restriction_enzyme/range/sequence_range/calculated_cuts.rb:154: warning: constant ::Fixnum is deprecated
Bug#904247: pytest-sugar: FTBFS and test failure with pytest 3.6
Source: pytest-sugar Version: 0.9.1-2 Severity: serious Tags: ftbfs buster sid X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: needs-update Hi Maintainer Since the upload of pytest 3.6.2-2 to unstable, pytest-sugar's autopkgtests have been failing [1], with the following error: ― [doctest] test_doctest_lineno.foobar ― 002 003 >>> foobar() UNEXPECTED EXCEPTION: NotImplementedError() On 27 June 2018 at 23:05, Paul Gevers wrote: > With a recent upload of pytest the autopkgtest of diffoscope, doit, > pytest-httpbin and pytest-sugar started to fail in testing. > See: https://qa.debian.org/excuses.php?package=pytest and links therein. > > With a very quick look, it seems that pytest-httpbin and pytest-sugar > just need to adapt to the new behavior (deprecation of functionality). I > can't really judge diffoscope and doit without diving deeper (I am going > to bed now). > > Currently this regression is delaying the migration of pytest to testing > by 13 days. Could you please discuss what the best way forward is? > > More information about this email and the reason of it can be found on > https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation > > Paul As can be seen on the reproducible builders [2], pytest-sugar now FTBFS with the same error in buster and unstable. Regards Graham [1] https://ci.debian.net/packages/p/pytest-sugar/unstable/amd64/ [2] https://tests.reproducible-builds.org/debian/history/amd64/pytest-sugar.html
Bug#897509: marked as done (git-repair: FTBFS: Duplicate instance declarations:)
Your message dated Sun, 22 Jul 2018 06:48:48 +
with message-id
and subject line Bug#897509: fixed in git-repair 1.20151215-1.2
has caused the Debian Bug report #897509,
regarding git-repair: FTBFS: Duplicate instance declarations:
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.)
--
897509: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897509
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: git-repair
Version: 1.20151215-1.1
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20180502 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> if [ "./Setup" = ./Setup ]; then ghc --make Setup; fi
> [ 1 of 25] Compiling Utility.Applicative ( Utility/Applicative.hs,
> Utility/Applicative.o )
> [ 2 of 25] Compiling Utility.Data ( Utility/Data.hs, Utility/Data.o )
> [ 3 of 25] Compiling Utility.Env ( Utility/Env.hs, Utility/Env.o )
> [ 4 of 25] Compiling Utility.Exception ( Utility/Exception.hs,
> Utility/Exception.o )
> [ 5 of 25] Compiling Utility.FileSize ( Utility/FileSize.hs,
> Utility/FileSize.o )
> [ 6 of 25] Compiling Utility.FileSystemEncoding (
> Utility/FileSystemEncoding.hs, Utility/FileSystemEncoding.o )
> [ 7 of 25] Compiling Utility.Monad( Utility/Monad.hs, Utility/Monad.o )
> [ 8 of 25] Compiling Utility.Misc ( Utility/Misc.hs, Utility/Misc.o )
> [ 9 of 25] Compiling Build.Version( Build/Version.hs, Build/Version.o )
>
> Build/Version.hs:31:1: warning: [-Wtabs]
> Tab character found here, and in 60 further locations.
> Please use spaces instead.
>|
> 31 | changelogversion <- getChangelogVersion
>|
> [10 of 25] Compiling Utility.PartialPrelude ( Utility/PartialPrelude.hs,
> Utility/PartialPrelude.o )
> [11 of 25] Compiling Utility.PosixFiles ( Utility/PosixFiles.hs,
> Utility/PosixFiles.o )
> [12 of 25] Compiling Utility.Process.Shim ( Utility/Process/Shim.hs,
> Utility/Process/Shim.o )
> [13 of 25] Compiling Utility.Process ( Utility/Process.hs, Utility/Process.o
> )
> [14 of 25] Compiling Utility.SafeCommand ( Utility/SafeCommand.hs,
> Utility/SafeCommand.o )
> [15 of 25] Compiling Utility.SystemDirectory ( Utility/SystemDirectory.hs,
> Utility/SystemDirectory.o )
> [16 of 25] Compiling Utility.Tmp ( Utility/Tmp.hs, Utility/Tmp.o )
> [17 of 25] Compiling Utility.Directory ( Utility/Directory.hs,
> Utility/Directory.o )
> [18 of 25] Compiling Utility.UserInfo ( Utility/UserInfo.hs,
> Utility/UserInfo.o )
> [19 of 25] Compiling Utility.Path ( Utility/Path.hs, Utility/Path.o )
> [20 of 25] Compiling Common ( Common.hs, Common.o )
> [21 of 25] Compiling Utility.DottedVersion ( Utility/DottedVersion.hs,
> Utility/DottedVersion.o )
> [22 of 25] Compiling Git.Version ( Git/Version.hs, Git/Version.o )
> [23 of 25] Compiling Build.TestConfig ( Build/TestConfig.hs,
> Build/TestConfig.o )
>
> Build/TestConfig.hs:15:1: warning: [-Wtabs]
> Tab character found here, and in 98 further locations.
> Please use spaces instead.
>|
> 15 | BoolConfig Bool |
>|
> [24 of 25] Compiling Build.Configure ( Build/Configure.hs, Build/Configure.o
> )
>
> Build/Configure.hs:15:1: warning: [-Wtabs]
> Tab character found here, and in 10 further locations.
> Please use spaces instead.
>|
> 15 | [ TestCase "version" (Config "packageversion" . StringConfig <$>
> getVersion)
>|
> [25 of 25] Compiling Main ( Setup.hs, Setup.o )
>
> Setup.hs:9:1: warning: [-Wtabs]
> Tab character found here, and in three further locations.
> Please use spaces instead.
> |
> 9 | { preConf = configure
> |
> Linking Setup ...
> ./Setup configure --ghc-options="-optl-Wl,-z,relro -optc-g -optc-O2
> -optc-fdebug-prefix-map=/<>=. -optc-fstack-protector-strong
> -optc-Wformat -optc-Werror=format-security -optc-Wp,-Wdate-time
> -optc-Wp,-D_FORTIFY_SOURCE=2"
> checking version... 1.20151215-1.1
> checking git... yes
> checking git version... 2.17.0
> Configuring git-repair-1.20151215...
> ./Setup build
> Preprocessing executable 'git-repair' for git-repair-1.20151215..
> Building executable 'git-repair' for git-repair-1.20151215..
>
> : warning: [-Wmissing-home-modules]
> These modules are needed for compilation but not listed in your .cabal
> file's other-modules: Build.SysConfig
>
Processed: git-repair: diff for NMU version 1.20151215-1.2
Processing control commands: > tags 897509 + patch Bug #897509 [src:git-repair] git-repair: FTBFS: Duplicate instance declarations: Added tag(s) patch. > tags 897509 + pending Bug #897509 [src:git-repair] git-repair: FTBFS: Duplicate instance declarations: Added tag(s) pending. -- 897509: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897509 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#897509: git-repair: diff for NMU version 1.20151215-1.2
Control: tags 897509 + patch
Control: tags 897509 + pending
Dear maintainer,
I've prepared an NMU for git-repair (versioned as 1.20151215-1.2) and
uploaded it to sid.
Regards.
--
Sean Whitton
diff -Nru git-repair-1.20151215/CHANGELOG git-repair-1.20151215/CHANGELOG
--- git-repair-1.20151215/CHANGELOG 2017-07-26 08:27:22.0 +0800
+++ git-repair-1.20151215/CHANGELOG 2018-07-22 14:33:24.0 +0800
@@ -1,3 +1,11 @@
+git-repair (1.20151215-1.2) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Patch duplicate Arbitrary instance of EpochTime out of
+Utility/QuickCheck.hs (Closes: #897509).
+
+ -- Sean Whitton Sun, 22 Jul 2018 14:33:24 +0800
+
git-repair (1.20151215-1.1) unstable; urgency=medium
* Non-maintainer upload.
diff -Nru git-repair-1.20151215/debian/changelog git-repair-1.20151215/debian/changelog
--- git-repair-1.20151215/debian/changelog 2017-07-26 08:27:22.0 +0800
+++ git-repair-1.20151215/debian/changelog 2018-07-22 14:33:24.0 +0800
@@ -1,3 +1,11 @@
+git-repair (1.20151215-1.2) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Patch duplicate Arbitrary instance of EpochTime out of
+Utility/QuickCheck.hs (Closes: #897509).
+
+ -- Sean Whitton Sun, 22 Jul 2018 14:33:24 +0800
+
git-repair (1.20151215-1.1) unstable; urgency=medium
* Non-maintainer upload.
diff -Nru git-repair-1.20151215/debian/patches/patch-duplicate-arbitrary-instance-out-o.patch git-repair-1.20151215/debian/patches/patch-duplicate-arbitrary-instance-out-o.patch
--- git-repair-1.20151215/debian/patches/patch-duplicate-arbitrary-instance-out-o.patch 1970-01-01 08:00:00.0 +0800
+++ git-repair-1.20151215/debian/patches/patch-duplicate-arbitrary-instance-out-o.patch 2018-07-22 14:33:24.0 +0800
@@ -0,0 +1,20 @@
+From: Sean Whitton
+Date: Sun, 22 Jul 2018 14:30:36 +0800
+X-Dgit-Generated: 1.20151215-1.2 5e47ead106bebfd076d950934fbe11d9f1ef552c
+Subject: patch duplicate Arbitrary instance out of Utility/QuickCheck.hs
+
+
+---
+
+--- git-repair-1.20151215.orig/Utility/QuickCheck.hs
git-repair-1.20151215/Utility/QuickCheck.hs
+@@ -33,9 +33,6 @@ instance (Arbitrary v, Eq v, Ord v) => A
+ instance Arbitrary POSIXTime where
+ arbitrary = fromInteger <$> nonNegative arbitrarySizedIntegral
+
+-instance Arbitrary EpochTime where
+- arbitrary = fromInteger <$> nonNegative arbitrarySizedIntegral
+-
+ {- Pids are never negative, or 0. -}
+ instance Arbitrary ProcessID where
+ arbitrary = arbitrarySizedBoundedIntegral `suchThat` (> 0)
diff -Nru git-repair-1.20151215/debian/patches/series git-repair-1.20151215/debian/patches/series
--- git-repair-1.20151215/debian/patches/series 2017-07-26 08:27:22.0 +0800
+++ git-repair-1.20151215/debian/patches/series 2018-07-22 14:33:24.0 +0800
@@ -1,3 +1,4 @@
fix-build-with-quickcheck-2.8.2.patch
split-out-module-to-work-around-badly-na.patch
patch-common.hs-to-avoid-duplicate-impor.patch
+patch-duplicate-arbitrary-instance-out-o.patch
signature.asc
Description: PGP signature
Bug#897856: https://salsa.debian.org/electronics-team/sdcc.git
Am 21. Juli 2018 19:44:33 MESZ schrieb Geert Stappers : > >There is now an empty git repository >at https://salsa.debian.org/electronics-team/sdcc.git >which is intended for Debian packaging of sdcc > > >Convenience links for the both bugreports in the To: > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895345 > Title: sdcc recent git repository > >and > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897856 > Title: sdcc: ftbfs with GCC-8 > > >Explanation of the people in the Cc: > > - Gudjon, maintainer of sdcc > - Bdale, uploader of sdcc > - Tobias, wrote a patch that fixed a recent sdcc bug >( https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894619#12 ) > - Adrian Bunk, did the upload of -2.1 > > >My hope is that they have content for sdcc packaging git repository. > > >Cheers >Geert Stappers >Who loves to see that sigrok stays in testing. sigrok depends on sdcc Hi Geert, just a quick follow-up from my side: I only ever did the quick fix with the patch, I'm not involved in the package maintaining. Therefore, I don't have any content for the git repository, unfortunately. If all else fails, you might need to resort to import the uploaded versions into the repository, e.g. with gbp import-dscs. Regards, Tobias
