Bug#873041: libxcursor1-udeb: Broken dpkg-shlibdeps rule

On Thu, 2017-08-24 at 03:22 +0200, Cyril Brulebois wrote: > > Drew, such conversion from xsfbs to dh should really be accompanied > by > a thorough debdiff check: > >   $ debdiff --controlfiles=ALL ../libxcursor*changes > > which makes the breakage obvious: > > Shlibs files of package

Bug#853494: marked as done (libindi: ftbfs with GCC-7)

Your message dated Thu, 24 Aug 2017 05:34:21 + with message-id and subject line Bug#853494: fixed in libindi 1.2.0-4 has caused the Debian Bug report #853494, regarding libindi: ftbfs with GCC-7 to be marked as done. This means that you claim that the

Bug#873052: gcl FTBFS on arm64: Unrecoverable error: Segmentation violation..

Source: gcl Version: 2.6.12-53 Severity: serious https://buildd.debian.org/status/logs.php?pkg=gcl=arm64 ... /<>/unixport/raw_pcl_gcl /<>/unixport/ -libdir /<>/ < foo GCL (GNU Common Lisp) April 1994 67111603 pages Building symbol table for /<>/unixport/raw_pcl_gcl .. loading

Processed: tagging 853494

Processing commands for cont...@bugs.debian.org: > tags 853494 + pending Bug #853494 [src:libindi] libindi: ftbfs with GCC-7 Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 853494: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853494

Bug#846314: marked as done (alot: please use python-gpg instead of python-gpgme)

Your message dated Thu, 24 Aug 2017 03:34:11 + with message-id and subject line Bug#866027: fixed in alot 0.6-1 has caused the Debian Bug report #866027, regarding alot: please use python-gpg instead of python-gpgme to be marked as done. This means that

Bug#866027: marked as done (alot: Migrate from pygpgme to python-gpg)

Your message dated Thu, 24 Aug 2017 03:34:11 + with message-id and subject line Bug#846314: fixed in alot 0.6-1 has caused the Debian Bug report #846314, regarding alot: Migrate from pygpgme to python-gpg to be marked as done. This means that you claim

Bug#846314: marked as done (alot: please use python-gpg instead of python-gpgme)

Your message dated Thu, 24 Aug 2017 03:34:11 + with message-id and subject line Bug#846314: fixed in alot 0.6-1 has caused the Debian Bug report #846314, regarding alot: please use python-gpg instead of python-gpgme to be marked as done. This means that

Bug#866027: marked as done (alot: Migrate from pygpgme to python-gpg)

Your message dated Thu, 24 Aug 2017 03:34:11 + with message-id and subject line Bug#866027: fixed in alot 0.6-1 has caused the Debian Bug report #866027, regarding alot: Migrate from pygpgme to python-gpg to be marked as done. This means that you claim

Bug#873041: libxcursor1-udeb: Broken dpkg-shlibdeps rule

Control: reassign -1 libxcursor1 1:1.1.14-2 Control: retitle -1 libxcursor1: broken shlibs for the udeb Control: tag -1 patch (Minor nitpick.) Jeremy Bicha (2017-08-23): > When libxcursor was converted to dh's rules, the line defining PACKAGE > was accidentally removed. > >

Processed: Re: Bug#873041: libxcursor1-udeb: Broken dpkg-shlibdeps rule

Processing control commands: > reassign -1 libxcursor1 1:1.1.14-2 Bug #873041 [libxcursor1-udeb] libxcursor1-udeb: Broken dpkg-shlibdeps rule Bug reassigned from package 'libxcursor1-udeb' to 'libxcursor1'. No longer marked as found in versions libxcursor/1:1.1.14-2. Ignoring request to alter

Bug#872598: udev-udeb: no input in graphical installer

.oO( Third time is the charm? ) Cyril Brulebois (2017-08-24): > Michael Biebl (2017-08-24): > > Am 23.08.2017 um 23:57 schrieb Cyril Brulebois: > > > > > My NMU FTBFSes on mips64el: > > > > > >

Bug#873041: libxcursor1-udeb: Broken dpkg-shlibdeps rule

Package: libxcursor1-udeb Version: 1:1.1.14-2 Severity: serious X-Debbugs-CC: debian-b...@lists.debian.org When libxcursor was converted to dh's rules, the line defining PACKAGE was accidentally removed. So this line: dh_makeshlibs -V "libxcursor1 (>> 1.1.2)" --add-udeb=$(PACKAGE)-udeb gets

Bug#853534: marked as done (mahimahi: ftbfs with GCC-7)

Your message dated Thu, 24 Aug 2017 00:50:36 + with message-id and subject line Bug#853534: fixed in mahimahi 0.97-1 has caused the Debian Bug report #853534, regarding mahimahi: ftbfs with GCC-7 to be marked as done. This means that you claim that the

Bug#871815: marked as done (asn1c FTBFS on ppc64el: FAIL: check-REAL)

Your message dated Wed, 23 Aug 2017 23:19:15 + with message-id and subject line Bug#871815: fixed in asn1c 0.9.28+dfsg-2 has caused the Debian Bug report #871815, regarding asn1c FTBFS on ppc64el: FAIL: check-REAL to be marked as done. This means that you

Bug#872598: udev-udeb: no input in graphical installer

Michael Biebl (2017-08-24): > Am 23.08.2017 um 23:57 schrieb Cyril Brulebois: > > > My NMU FTBFSes on mips64el: > > > > https://buildd.debian.org/status/fetch.php?pkg=systemd=mips64el=234-2.1=1503523165=0 > > > > James Cowgill mentioned this gcc bug report: > >

Bug#867464: marked as done (python3-radicale: missing dependencies)

Your message dated Wed, 23 Aug 2017 22:50:05 + with message-id and subject line Bug#867464: fixed in radicale 2.1.4-2 has caused the Debian Bug report #867464, regarding python3-radicale: missing dependencies to be marked as done. This means that you

Bug#871114: marked as done (widelands: FTBFS: game_settings.h:52:8: error: 'newuser.UserSettings::position' may be used uninitialized in this function [-Werror=maybe-uninitialized])

Your message dated Wed, 23 Aug 2017 22:39:13 + with message-id and subject line Bug#871114: fixed in widelands 1:19+repack-4 has caused the Debian Bug report #871114, regarding widelands: FTBFS: game_settings.h:52:8: error:

Bug#872598: udev-udeb: no input in graphical installer

Am 23.08.2017 um 23:57 schrieb Cyril Brulebois: > My NMU FTBFSes on mips64el: > > https://buildd.debian.org/status/fetch.php?pkg=systemd=mips64el=234-2.1=1503523165=0 > > James Cowgill mentioned this gcc bug report: > https://bugs.debian.org/871514 > > so I think I might duplicate the

Processed: Re: Bug#822595: Raising severity to serious for packages depending on gksu

Processing commands for cont...@bugs.debian.org: > severity #822601 serious Bug #822601 [src:xnetcardconfig] xnetcardconfig: depends on gksu which is deprecated Severity set to 'serious' from 'important' > severity #822603 serious Bug #822603 [src:network-config] network-config: depends on gksu

Bug#871114: widelands: FTBFS: game_settings.h:52:8: error: 'newuser.UserSettings::position' may be used uninitialized in this function [-Werror=maybe-uninitialized]

Control: tags -1 pending Am 23.08.2017 um 21:56 schrieb Hans Joachim Desserud: > Control: tags -1 confirmed > Control: forwarded -1 https://bugs.launchpad.net/widelands/+bug/1695879 > > Hello > > We ran into the same issue upstream a while back when attempting to > build with GCC7, > see [1]

Processed: Re: Bug#871114: widelands: FTBFS: game_settings.h:52:8: error: 'newuser.UserSettings::position' may be used uninitialized in this function [-Werror=maybe-uninitialized]

Processing control commands: > tags -1 pending Bug #871114 [src:widelands] widelands: FTBFS: game_settings.h:52:8: error: 'newuser.UserSettings::position' may be used uninitialized in this function [-Werror=maybe-uninitialized] Added tag(s) pending. -- 871114:

Bug#853319: [Aspectc-developers] Fwd: Bug#853319: aspectc++: ftbfs with GCC-7

On 08/23/2017 12:07 PM, Olaf Spinczyk wrote: > Hi! > > You can generate the config file easily with ag++ --gen_config. Sorry > for the inconvenience. The background is that when I wrote the first > ac++ tests, I did not want the makefile to depend on ag++. > > We should change that sooner or

Processed: update #871514 v2

Processing commands for cont...@bugs.debian.org: > # Not checked, but it seems very likely this is "the" mips64el bug > forcemerge 871514 872987 Bug #871514 [gcc-7] clamav: FTBFS on mips64el Bug #871538 [gcc-7] Makes apparmor FTBFS on mips64el (generated code thinks that 1 > 1) Bug #872438

Processed (with 3 errors): update #871514

Processing commands for cont...@bugs.debian.org: > # Not checked, but it seems very likely this is "the" mips64el bug > merge 871514 872987 Bug #871514 [gcc-7] clamav: FTBFS on mips64el Bug #871538 [gcc-7] Makes apparmor FTBFS on mips64el (generated code thinks that 1 > 1) Bug #872438 [gcc-7]

Bug#872598: udev-udeb: no input in graphical installer

Hi, Cyril Brulebois (2017-08-23): > Michael Biebl (2017-08-23): > > Am 23.08.2017 um 10:08 schrieb Cyril Brulebois: > > > Would you be OK with a minimal NMU to fix the missing file? This issue has > > > been blocking the D-I Buster Alpha 1 release for weeks

Processed: Add patch tag

Processing commands for cont...@bugs.debian.org: > tags 853470 patch Bug #853470 [src:kadu] kadu: ftbfs with GCC-7 Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 853470: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853470 Debian Bug

Bug#869608: marked as done (bareos-filedaemon: corrupts backups when signature=SHA1 in fileset)

Your message dated Wed, 23 Aug 2017 21:17:43 + with message-id and subject line Bug#869608: fixed in bareos 14.2.1+20141017gitc6c5b56-3+deb8u3 has caused the Debian Bug report #869608, regarding bareos-filedaemon: corrupts backups when signature=SHA1 in

Processed: Re: [Debian-med-packaging] Bug#873024: orthanc-wsi FTBFS with dcmtk 3.6.2

Processing control commands: > tags -1 pending Bug #873024 [src:orthanc-wsi] orthanc-wsi FTBFS with dcmtk 3.6.2 Added tag(s) pending. -- 873024: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873024 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#853515: marked as done (libwebsockets: ftbfs with GCC-7)

Your message dated Wed, 23 Aug 2017 20:57:55 + with message-id and subject line Bug#853515: fixed in libwebsockets 2.0.3-2.1 has caused the Debian Bug report #853515, regarding libwebsockets: ftbfs with GCC-7 to be marked as done. This means that you

Bug#853579: marked as done (nut: ftbfs with GCC-7)

Your message dated Wed, 23 Aug 2017 20:59:16 + with message-id and subject line Bug#853579: fixed in nut 2.7.4-5.1 has caused the Debian Bug report #853579, regarding nut: ftbfs with GCC-7 to be marked as done. This means that you claim that the problem

Bug#873024: [Debian-med-packaging] Bug#873024: orthanc-wsi FTBFS with dcmtk 3.6.2

Control: tags -1 pending I've pushed the needed changes to the packaging git. Will check and upload tomorrow. Best, Gert

Bug#869633: marked as done (CVE-2015-5191)

Your message dated Wed, 23 Aug 2017 20:47:28 + with message-id and subject line Bug#869633: fixed in open-vm-tools 2:10.1.5-5055683-4+deb9u1 has caused the Debian Bug report #869633, regarding CVE-2015-5191 to be marked as done. This means that you claim

Bug#868150: marked as done (imapproxy: fails to start)

Your message dated Wed, 23 Aug 2017 20:47:32 + with message-id and subject line Bug#868150: fixed in up-imapproxy 1.2.8~svn20161210-2+deb9u1 has caused the Debian Bug report #868150, regarding imapproxy: fails to start to be marked as done. This means

Bug#869608: marked as done (bareos-filedaemon: corrupts backups when signature=SHA1 in fileset)

Your message dated Wed, 23 Aug 2017 20:47:12 + with message-id and subject line Bug#869608: fixed in bareos 16.2.4-3+deb9u1 has caused the Debian Bug report #869608, regarding bareos-filedaemon: corrupts backups when signature=SHA1 in fileset to be marked

Bug#871114: widelands: FTBFS: game_settings.h:52:8: error: 'newuser.UserSettings::position' may be used uninitialized in this function [-Werror=maybe-uninitialized]

Hi Hans Joachim, it appears you are involved in upstream development for Widelands. The game currently fails to build from source with GCC 7. I discovered this [1] merge commit which shall resolve GCC 7 issues but unfortunately it doesn't apply cleanly for the recent 1.19 release of Widelands.

Processed: Re: widelands: FTBFS: game_settings.h:52:8: error: 'newuser.UserSettings::position' may be used uninitialized in this function [-Werror=maybe-uninitialized]

Processing control commands: > tags -1 confirmed Bug #871114 [src:widelands] widelands: FTBFS: game_settings.h:52:8: error: 'newuser.UserSettings::position' may be used uninitialized in this function [-Werror=maybe-uninitialized] Added tag(s) confirmed. > forwarded -1

Bug#871114: widelands: FTBFS: game_settings.h:52:8: error: 'newuser.UserSettings::position' may be used uninitialized in this function [-Werror=maybe-uninitialized]

Control: tags -1 confirmed Control: forwarded -1 https://bugs.launchpad.net/widelands/+bug/1695879 Hello We ran into the same issue upstream a while back when attempting to build with GCC7, see [1] for details. The issue was fixed, and since we expected distros would switch to GCC7 as the

Bug#873029: [unicode-data] Copyriht/Lack of get-orig-source where is the source

Package: unicode-data Version: 10.0.0-1 Severity: serious Without copyright information with exact location of souce, it is hard to get source It is at least a violation of 12.5. Copyright information I could help with this package if needed signature.asc Description: This is a digitally

Processed (with 1 error): merge

Processing commands for cont...@bugs.debian.org: > merge 872987 871514 Bug #872987 [gcc-7] pspp 1.0.0-1 FTBFS on mips64el architecture on debian Unable to merge bugs because: forwarded of #871538 is 'https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81803' not '' affects of #871538 is

Bug#873024: orthanc-wsi FTBFS with dcmtk 3.6.2

Source: orthanc-wsi Version: 0.4+dfsg-2 Severity: serious https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/orthanc-wsi.html ... -- Trying to find DCMTK expecting DCMTKConfig.cmake -- Trying to find DCMTK expecting DCMTKConfig.cmake - ok DCMTK version: 362 CMake Error at

Bug#873023: tupi FTBFS with qtmultimedia5-dev 5.9.1-2

Source: tupi Version: 0.2+git08-1 Severity: serious Tags: buster sid https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/tupi.html ...  * Checking for Qt >= 5.4.0  * Testing for qmake... [ OK ]  * Adding libav support: true  * Checking

Bug#873020: marked as done (phonon FTBFS qtbase5-dev 5.9.1+dfsg-9)

Your message dated Wed, 23 Aug 2017 22:04:35 +0300 with message-id <20170823190435.aprffxpezigzjh4u@localhost> and subject line Already fixed in experimental has caused the Debian Bug report #873020, regarding phonon FTBFS qtbase5-dev 5.9.1+dfsg-9 to be marked as done. This means that you claim

Bug#873016: [Pkg-javascript-devel] Bug#873016: node-lodash-packages: not preferred form for source: Should be built from node-lodash

Quoting Pirate Praveen (2017-08-23 20:11:28) > On ബുധന്‍ 23 ആഗസ്റ്റ് 2017 11:33 വൈകു, Jonas Smedegaard wrote: > > Package: node-lodash-packages > > Severity: serious > > Justification: Policy 2.1 > > I do not think the root issue is serious, but only important. Lack of source is serious. Please

Processed: severity of 873016 is serious

Processing commands for cont...@bugs.debian.org: > severity 873016 serious Bug #873016 [node-lodash-packages] node-lodash-packages: not preferred form for source: Should be built from node-lodash Ignoring request to change severity of Bug 873016 to the same value. > thanks Stopping processing

Bug#872598: udev-udeb: no input in graphical installer

Control: tag -1 patch pending Michael Biebl (2017-08-23): > Am 23.08.2017 um 10:08 schrieb Cyril Brulebois: > > Would you be OK with a minimal NMU to fix the missing file? This issue has > > been blocking the D-I Buster Alpha 1 release for weeks already (even if it > > hadn't

Processed: Re: Bug#872598: udev-udeb: no input in graphical installer

Processing control commands: > tag -1 patch pending Bug #872598 [udev-udeb] udev-udeb: no input in graphical installer Added tag(s) pending. -- 872598: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872598 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#873020: phonon FTBFS qtbase5-dev 5.9.1+dfsg-9

Source: phonon Version: 4:4.9.0-4 Severity: serious Tags: buster sid https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/phonon.html ... In file included from /build/1st/phonon-4.9.0/phonon/audiooutput_p.h:28:0, from

Bug#871333: marked as done (r-bioc-rtracklayer: FTBFS: Error: package or namespace load failed for 'rtracklayer' in dyn.load(file, DLLpath = DLLpath, ...):)

Your message dated Wed, 23 Aug 2017 18:53:01 + with message-id and subject line Bug#871333: fixed in r-bioc-rtracklayer 1.36.4-1 has caused the Debian Bug report #871333, regarding r-bioc-rtracklayer: FTBFS: Error: package or namespace load failed for

Bug#873016: [Pkg-javascript-devel] Bug#873016: node-lodash-packages: not preferred form for source: Should be built from node-lodash

On ബുധന്‍ 23 ആഗസ്റ്റ് 2017 11:33 വൈകു, Jonas Smedegaard wrote: > Package: node-lodash-packages > Severity: serious > Justification: Policy 2.1 I do not think the root issue is serious, but only important. > The source package node-lodash-packages does not contain the source form > preferred for

Processed: Bug#872992 marked as pending

Processing commands for cont...@bugs.debian.org: > tag 872992 pending Bug #872992 [src:pytest-qt] pytest-qt: FTBFS: Tests failures because of logging changes in Qt Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 872992:

Bug#872992: marked as pending

tag 872992 pending thanks Hello, Bug #872992 reported by you has been fixed in the Git repository. You can see the changelog below, and you can check the diff of the fix at: https://anonscm.debian.org/cgit/python-modules/packages/pytest-qt.git/commit/?id=a66fe10 --- commit

Bug#872866: wily: Appears to contain non-free code

control: severity -1 normal thanks Hi Jacob, thanks a lot for your bug report. Please have a look at Doc/sam/README. In this file the license of libframe and libXg is clearly mentioned. This license is already added to the debian/copyright of the package. As you are right that some

Processed: Re: wily: Appears to contain non-free code

Processing control commands: > severity -1 normal Bug #872866 [wily] wily: Appears to contain non-free code Severity set to 'normal' from 'serious' -- 872866: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872866 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#873016: node-lodash-packages: not preferred form for source: Should be built from node-lodash

Package: node-lodash-packages Severity: serious Justification: Policy 2.1 -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 The source package node-lodash-packages does not contain the source form preferred for editing by upstream. Instead, upstream documents how the contents of that code is

Bug#853699: marked as done (vdr-plugin-live: ftbfs with GCC-7)

Your message dated Wed, 23 Aug 2017 17:54:27 + with message-id and subject line Bug#853699: fixed in vdr-plugin-live 2.3.1-1 has caused the Debian Bug report #853699, regarding vdr-plugin-live: ftbfs with GCC-7 to be marked as done. This means that you

Processed: Re: Bug#822595: Raising severity to serious for packages depending on gksu

Processing control commands: > severity -1 important Bug #822603 [src:network-config] network-config: depends on gksu which is deprecated Severity set to 'important' from 'serious' -- 822603: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822603 Debian Bug Tracking System Contact

Processed: Re: Bug#822595: Raising severity to serious for packages depending on gksu

Processing control commands: > severity -1 important Bug #822601 [src:xnetcardconfig] xnetcardconfig: depends on gksu which is deprecated Severity set to 'important' from 'serious' -- 822601: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822601 Debian Bug Tracking System Contact

Processed: Re: Bug#822595: Raising severity to serious for packages depending on gksu

Processing control commands: > severity -1 important Bug #822595 [src:caja-extensions] caja-extensions: depends on gksu which is deprecated Severity set to 'important' from 'serious' -- 822595: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822595 Debian Bug Tracking System Contact

Processed: Re: Bug#822595: Raising severity to serious for packages depending on gksu

Processing control commands: > severity -1 important Bug #822600 [src:sbackup] sbackup: depends on gksu which is deprecated Severity set to 'important' from 'serious' -- 822600: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822600 Debian Bug Tracking System Contact ow...@bugs.debian.org

Bug#822595: Raising severity to serious for packages depending on gksu

Control: severity -1 important Hi Jeremy, hi all, On Mi 05 Jul 2017 02:21:07 CEST, Jeremy Bicha wrote: Control: severity -1 serious Control: tags -1 -stretch +buster For the next major stable release of Debian (codenamed "buster"), the Debian GNOME team plans to default to GNOME on Wayland

Bug#822595: Raising severity to serious for packages depending on gksu

On Wed, Aug 23, 2017 at 1:41 PM, Mike Gabriel wrote: > I will drop severity temporarily for this bug, because we need > caja-extensions 1.18 in testing (rather than some older 1.16 version). > > Once caja-admin has landed in unstable, I will upload

Bug#872598: udev-udeb: no input in graphical installer

Hi KiBi Am 23.08.2017 um 10:08 schrieb Cyril Brulebois: > Would you be OK with a minimal NMU to fix the missing file? This issue has > been blocking the D-I Buster Alpha 1 release for weeks already (even if it > hadn't been diagnosed and reported against udev-udeb until recently), and > I'd be

Bug#872860: marked as done (csound FTBFS with libgmm++-dev 5.2+dfsg1-5)

Your message dated Wed, 23 Aug 2017 17:34:38 + with message-id and subject line Bug#872860: fixed in csound 1:6.09.1~dfsg-2 has caused the Debian Bug report #872860, regarding csound FTBFS with libgmm++-dev 5.2+dfsg1-5 to be marked as done. This means

Bug#871918: libssl1.1: tls_process_server_hello:unsupported protocol

On 2017-08-23 09:32:12 [+0200], Michal Palenik wrote: > it look like a something strange with libssl1.1 version 1.1.0f-4 and > some of the certificates. > > openssl s_client -connect mail7.hostmaster.sk:465 (and port 995) > > gives some buggy output (including connections with postfix or >

Bug#872275: slic3r-prusa: diff for NMU version 1.37.0+dfsg-1.1

Control: tags 872275 + pending Dear maintainer, I've prepared an NMU for slic3r-prusa (versioned as 1.37.0+dfsg-1.1) and uploaded it to DELAYED/5. Please feel free to tell me if I should delay it longer. Regards. -- .''`. https://info.comodo.priv.at/ - Debian Developer

Processed: slic3r-prusa: diff for NMU version 1.37.0+dfsg-1.1

Processing control commands: > tags 872275 + pending Bug #872275 [slic3r-prusa] slic3r-prusa: Loadable library and perl binary mismatch Added tag(s) pending. -- 872275: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872275 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Processed: Reassign to gcc-7

Processing commands for cont...@bugs.debian.org: > reassign 872987 gcc-7 Bug #872987 [pspp] pspp 1.0.0-1 FTBFS on mips64el architecture on debian Bug reassigned from package 'pspp' to 'gcc-7'. No longer marked as found in versions pspp/1.0.0-1. Ignoring request to alter fixed versions of bug

Processed: Bug#872860 marked as pending

Processing commands for cont...@bugs.debian.org: > tag 872860 pending Bug #872860 [src:csound] csound FTBFS with libgmm++-dev 5.2+dfsg1-5 Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 872860:

Bug#872860: marked as pending

tag 872860 pending thanks Hello, Bug #872860 reported by you has been fixed in the Git repository. You can see the changelog below, and you can check the diff of the fix at: http://anonscm.debian.org/git/pkg-multimedia/csound.git/commit/?id=550dc39 --- commit

Processed: Affects

Processing commands for cont...@bugs.debian.org: > affects 871514 pspp Bug #871514 [gcc-7] clamav: FTBFS on mips64el Bug #871538 [gcc-7] Makes apparmor FTBFS on mips64el (generated code thinks that 1 > 1) Bug #872438 [gcc-7] src:nodejs: FTBFS on mips64el: Can't determine the arch of ./node

Processed (with 2 errors): Merge bugs

Processing commands for cont...@bugs.debian.org: > severity 872987 serious Bug #872987 [pspp] pspp 1.0.0-1 FTBFS on mips64el architecture on debian Severity set to 'serious' from 'normal' > merge 872987 871514 Bug #872987 [pspp] pspp 1.0.0-1 FTBFS on mips64el architecture on debian Unable to

Processed: Bug#871514: clamav: FTBFS on mips64el

Processing control commands: > forcemerge -1 872438 Bug #871514 [gcc-7] clamav: FTBFS on mips64el Bug #871538 [gcc-7] Makes apparmor FTBFS on mips64el (generated code thinks that 1 > 1) Bug #872438 [gcc-7] src:nodejs: FTBFS on mips64el: Can't determine the arch of ./node Set Bug

Bug#871514: clamav: FTBFS on mips64el

Control: forcemerge -1 872438 Hi, Just a brief update on this bug. Unfortunately there is still no "good" fix. As I have written in a few places now, the bug occurs on mips64el where a "small" variable gets spilled to the stack. It is possible that GCC writes the variable to the stack using a

Processed: fixed 869074 in 0.188+dfsg.1-1

Processing commands for cont...@bugs.debian.org: > fixed 869074 0.188+dfsg.1-1 Bug #869074 [src:mame] mame FTBFS on i386: virtual memory exhausted Marked as fixed in versions mame/0.188+dfsg.1-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 869074:

Bug#873008: hfst FTBFS on big endian: FAIL: test

Source: hfst Version: 3.12.2~r3289-1 Severity: serious https://buildd.debian.org/status/package.php?p=hfst=sid ... Making check in tools make[3]: Entering directory '/<>/tools' Making check in src make[4]: Entering directory '/<>/tools/src' Making check in hfst-proc make[5]: Entering directory

Bug#865633:

Hi, I test this problem on the latest Debian sid, and I cannot reproduce this problem. This is my software version: spice client: Debian sid virt-manager 1:1.4.0-6 virt-viewer 5.0-1 gir1.2-spice-client-glib-2.0 0.33-3.3

Bug#869816: marked as done (openjdk-7: several vulnerabilities)

Your message dated Wed, 23 Aug 2017 16:26:18 + with message-id and subject line Bug#869816: fixed in openjdk-7 7u151-2.6.11-1 has caused the Debian Bug report #869816, regarding openjdk-7: several vulnerabilities to be marked as done. This means that you

Bug#871062: marked as done (collectd: FTBFS: client.c:621:23: error: '%s' directive output may be truncated writing up to 1023 bytes into a region of size 1010 [-Werror=format-truncation=])

Your message dated Wed, 23 Aug 2017 16:34:19 + with message-id and subject line Bug#871062: fixed in collectd 5.7.2-1 has caused the Debian Bug report #871062, regarding collectd: FTBFS: client.c:621:23: error: '%s' directive output may be truncated

Bug#872276: marked as done (collectd: FTBFS with linux-libc-dev >= 4.12: please bundle asm/msr-index.h)

Your message dated Wed, 23 Aug 2017 16:34:19 + with message-id and subject line Bug#872276: fixed in collectd 5.7.2-1 has caused the Debian Bug report #872276, regarding collectd: FTBFS with linux-libc-dev >= 4.12: please bundle asm/msr-index.h to be

Bug#766601: marked as done (openjdk-7-jre-headless: still depending on libjpeg8?)

Your message dated Wed, 23 Aug 2017 16:26:18 + with message-id and subject line Bug#766601: fixed in openjdk-7 7u151-2.6.11-1 has caused the Debian Bug report #766601, regarding openjdk-7-jre-headless: still depending on libjpeg8? to be marked as done.

Processed: tagging 868300

Processing commands for cont...@bugs.debian.org: > tags 868300 + fixed-upstream Bug #868300 [yadm] yadm: CVE-2017-11353: race condition allows access to SSH and PGP keys Added tag(s) fixed-upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 868300:

Bug#853319: [Aspectc-developers] Fwd: Bug#853319: aspectc++: ftbfs with GCC-7

Hi! You can generate the config file easily with ag++ --gen_config. Sorry for the inconvenience. The background is that when I wrote the first ac++ tests, I did not want the makefile to depend on ag++. We should change that sooner or later, because it is obviously confusing. Cheers, Olaf On

Bug#853319: [Aspectc-developers] Fwd: Bug#853319: aspectc++: ftbfs with GCC-7

On 08/23/2017 04:29 AM, Olaf Spinczyk wrote: > Hi Reinhard, > > when trying to compile the tests, ac++ seems to have no (or an invalid) > puma.config file. It doesn't find the system header files, e.g. stdio.h > and iostream. For 'make test' to succeed PUMA_CONFIG must point to a > valid config

Bug#870121: marked as done (mate-power-manager: crashes with upower 0.99.5 on any device with a backlit keyboard)

Your message dated Wed, 23 Aug 2017 15:07:51 + with message-id and subject line Bug#870121: fixed in mate-power-manager 1.18.0-2 has caused the Debian Bug report #870121, regarding mate-power-manager: crashes with upower 0.99.5 on any device with a

Bug#853452: marked as done (injeqt: ftbfs with GCC-7)

Your message dated Wed, 23 Aug 2017 15:06:29 + with message-id and subject line Bug#853452: fixed in injeqt 1.1.0-1.1 has caused the Debian Bug report #853452, regarding injeqt: ftbfs with GCC-7 to be marked as done. This means that you claim that the

Bug#871591: marked as done ([src:llvm-toolchain-snapshot] FTBFS: debian/rules fails to detect gcc-7)

Your message dated Wed, 23 Aug 2017 15:00:31 + with message-id and subject line Bug#871591: fixed in llvm-toolchain-snapshot 1:6.0~svn310776-1 has caused the Debian Bug report #871591, regarding [src:llvm-toolchain-snapshot] FTBFS: debian/rules fails to

Bug#871300: marked as done (libmagick++-6.q16-7: requires rebuild against GCC 7 and symbols/shlibs bump)

Your message dated Wed, 23 Aug 2017 15:00:16 + with message-id and subject line Bug#871300: fixed in imagemagick 8:6.9.9.6+dfsg-1 has caused the Debian Bug report #871300, regarding libmagick++-6.q16-7: requires rebuild against GCC 7 and symbols/shlibs

Bug#871814: marked as done (csound-manual FTBFS: python: Command not found)

Your message dated Wed, 23 Aug 2017 15:00:11 + with message-id and subject line Bug#871814: fixed in csound-manual 1:6.09.0~dfsg-2 has caused the Debian Bug report #871814, regarding csound-manual FTBFS: python: Command not found to be marked as done.

Bug#843926: marked as done (jemalloc uses a hard coded page size detected during build)

Your message dated Wed, 23 Aug 2017 15:00:17 + with message-id and subject line Bug#843926: fixed in jemalloc 5.0.1-1 has caused the Debian Bug report #843926, regarding jemalloc uses a hard coded page size detected during build to be marked as done. This

Bug#872738: contextfree FTBFS on ppc64el: error: 'CTL_HW' was not declared in this scope

I have applied Frederic'c patch to the upstream source as well as fixes for the FTBFS issues with other platforms (ppc, alpha, hurd-i386, x32). I also eliminated the use of the deprecated readdir_r() function. Context Free 3.0.11.5 package is being reviewed by the package sponsor. -- john On

Bug#868609: le FTBFS with latest ncurses

On 23 August 2017 at 14:56, Alexander V. Lukyanov wrote: > On Fri, Aug 18, 2017 at 12:39:00PM +0200, Raphael Geissert wrote: >> Do you plan to make a new release with the fixes? or should I grab the >> patches from github? > > 1.16.5 has been released. Awesome, thanks. I'll take

Processed: Bug#870121 marked as pending

Processing commands for cont...@bugs.debian.org: > tag 870121 pending Bug #870121 [mate-power-manager] mate-power-manager: crashes with upower 0.99.5 on any device with a backlit keyboard Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. --

Bug#870121: marked as pending

tag 870121 pending thanks Hello, Bug #870121 reported by you has been fixed in the Git repository. You can see the changelog below, and you can check the diff of the fix at: https://anonscm.debian.org/cgit/pkg-mate/mate-power-manager.git/commit/?id=0253bbe --- commit

Bug#872881: simgrid: FTBFS: `__atomic_fetch_add_8' undefined

Hi, The attached patch seems to work (ie replace atomic-library with it). Using target_link_libraries should put any linker arguments at the end instead of the beginning. Thanks, James --- a/tools/cmake/MakeLib.cmake +++ b/tools/cmake/MakeLib.cmake @@ -114,6 +114,7 @@ if(enable_smpi AND APPLE)

Bug#853452: NMU diff

Here's the debdiff for Mateusz Łukasik's NMU I'm about to upload. Meow! -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢰⠒⠀⣿⡁ Vat kind uf sufficiently advanced technology iz dis!? ⢿⡄⠘⠷⠚⠋⠀-- Genghis Ht'rok'din ⠈⠳⣄ diff -Nru injeqt-1.1.0/debian/changelog injeqt-1.1.0/debian/changelog

Bug#864936: marked as done (yagv: segmentation fault on startup)

Your message dated Wed, 23 Aug 2017 13:05:06 + with message-id and subject line Bug#864936: fixed in pyglet 1.3.0~rc1-1 has caused the Debian Bug report #864936, regarding yagv: segmentation fault on startup to be marked as done. This means that you claim

Bug#871145: marked as done (hfst: FTBFS: ./../include/fst/replace.h:1061:46: error: expected ';' before '::' token)

Your message dated Wed, 23 Aug 2017 13:00:10 + with message-id and subject line Bug#871145: fixed in hfst 3.12.2~r3289-1 has caused the Debian Bug report #871145, regarding hfst: FTBFS: ./../include/fst/replace.h:1061:46: error: expected ';' before '::'

Bug#871062: collectd: FTBFS: client.c:621:23: error: '%s' directive output may be truncated writing up to 1023 bytes into a region of size 1010 [-Werror=format-truncation=]

Hello Michael, On Mon, Aug 21, 2017 at 06:11:02PM +0200, Michael Stapelberg wrote: > Hi, > > Steve Langasek writes: > > The attached one-liner patch corrects this build failure by simply ignoring > > the (IMHO uninteresting) new gcc-7 warning. I think this is a

Bug#868609: le FTBFS with latest ncurses

On Fri, Aug 18, 2017 at 12:39:00PM +0200, Raphael Geissert wrote: > Do you plan to make a new release with the fixes? or should I grab the > patches from github? 1.16.5 has been released. -- Alexander.

Bug#864936: marked as pending

tag 864936 pending thanks Hello, Bug #864936 reported by you has been fixed in the Git repository. You can see the changelog below, and you can check the diff of the fix at: https://anonscm.debian.org/cgit/python-modules/packages/pyglet.git/commit/?id=0039ad9 --- commit

  1   2   >