Bug#828399: marked as done (libmsn: FTBFS with openssl 1.1.0)

Your message dated Sat, 05 Nov 2016 04:37:22 + with message-id and subject line Bug#842871: Removed package(s) from unstable has caused the Debian Bug report #828399, regarding libmsn: FTBFS with openssl 1.1.0 to be marked as done. This means that you

Bug#842826: marked as done (haskell-monadcatchio-transformers: FTBFS: hlibrary.setup: Encountered missing dependencies: base <4.9, transformers >=0.2 && <0.5)

Your message dated Sat, 05 Nov 2016 04:33:46 + with message-id and subject line Bug#842758: Removed package(s) from unstable has caused the Debian Bug report #842826, regarding haskell-monadcatchio-transformers: FTBFS: hlibrary.setup: Encountered missing

Bug#817382: marked as done (bootchart: Removal of debhelper compat 4)

Your message dated Sat, 05 Nov 2016 04:28:17 + with message-id and subject line Bug#831555: Removed package(s) from unstable has caused the Debian Bug report #817382, regarding bootchart: Removal of debhelper compat 4 to be marked as done. This means that

Bug#841111: marked as done (jasper: CVE-2016-8691 CVE-2016-8692)

Your message dated Sat, 05 Nov 2016 04:26:37 + with message-id and subject line Bug#812630: Removed package(s) from unstable has caused the Debian Bug report #84, regarding jasper: CVE-2016-8691 CVE-2016-8692 to be marked as done. This means that you

Bug#841110: marked as done (jasper: CVE-2016-8693)

Your message dated Sat, 05 Nov 2016 04:26:37 + with message-id and subject line Bug#812630: Removed package(s) from unstable has caused the Debian Bug report #841110, regarding jasper: CVE-2016-8693 to be marked as done. This means that you claim that the

Bug#816228: marked as done (Don't include in stretch)

Your message dated Sat, 05 Nov 2016 04:26:37 + with message-id and subject line Bug#812630: Removed package(s) from unstable has caused the Debian Bug report #816228, regarding Don't include in stretch to be marked as done. This means that you claim that

Bug#841112: marked as done (jasper: CVE-2016-8690)

Your message dated Sat, 05 Nov 2016 04:26:37 + with message-id and subject line Bug#812630: Removed package(s) from unstable has caused the Debian Bug report #841112, regarding jasper: CVE-2016-8690 to be marked as done. This means that you claim that the

Bug#731669: marked as done (bootchart: outdated version should not be shipped with jessie)

Your message dated Sat, 05 Nov 2016 04:28:17 + with message-id and subject line Bug#831555: Removed package(s) from unstable has caused the Debian Bug report #731669, regarding bootchart: outdated version should not be shipped with jessie to be marked as

Processed: reassign 841103 to dirmngr, closing 841103, forcibly merging 840680 841103

Processing commands for cont...@bugs.debian.org: > reassign 841103 dirmngr Bug #841103 [gnupg] gnupg hangs during import of key Bug reassigned from package 'gnupg' to 'dirmngr'. No longer marked as found in versions gnupg2/2.1.15-4. Ignoring request to alter fixed versions of bug #841103 to the

Bug#841103: reassign 841103 to dirmngr, closing 841103, forcibly merging 840680 841103

reassign 841103 dirmngr close 841103 2.1.15-6 forcemerge 840680 841103 thanks https://bugs.debian.org/841103 is the same issue as https://bugs.debian.org/840680

Bug#822699: marked as done (libucimf: FTBFS with GCC 6)

Your message dated Sat, 05 Nov 2016 03:06:51 + with message-id and subject line Bug#822699: fixed in libucimf 2.3.8-8 has caused the Debian Bug report #822699, regarding libucimf: FTBFS with GCC 6 to be marked as done. This means that you claim that the

Bug#843041: marked as done (pacemaker: CVE-2016-7035)

Your message dated Sat, 05 Nov 2016 03:07:03 + with message-id and subject line Bug#843041: fixed in pacemaker 1.1.15-3 has caused the Debian Bug report #843041, regarding pacemaker: CVE-2016-7035 to be marked as done. This means that you claim that the

Bug#841341: marked as done (bd "Bad substitution" if /bin/sh is not bash)

Your message dated Sat, 05 Nov 2016 03:03:45 + with message-id and subject line Bug#841341: fixed in bd 1.02-1 has caused the Debian Bug report #841341, regarding bd "Bad substitution" if /bin/sh is not bash to be marked as done. This means that you claim

Processed: limit source to pacemaker, tagging 843041

Processing commands for cont...@bugs.debian.org: > limit source pacemaker Limiting to bugs with field 'source' containing at least one of 'pacemaker' Limit currently set to 'source':'pacemaker' > tags 843041 + pending Bug #843041 [src:pacemaker] pacemaker: CVE-2016-7035 Added tag(s) pending. >

Bug#840528: marked as done (libmongoc: mongoc-stream-tls.h wants mongoc-stream-tls-private.h, which is absent)

Your message dated Fri, 4 Nov 2016 21:48:32 -0400 with message-id and subject line has caused the Debian Bug report #840528, regarding libmongoc: mongoc-stream-tls.h wants mongoc-stream-tls-private.h, which is absent to be

Processed: Increasing severity (should have done this sooner)

Processing control commands: > severity -1 serious Bug #842715 [src:skrooge] skrooge: FTBFS with Qt 5.7.1 Severity set to 'serious' from 'important' -- 842715: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=842715 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Processed: closing 839330

Processing commands for cont...@bugs.debian.org: > close 839330 Bug #839330 {Done: Alexandre Viau } [src:ring] ring: FTBFS: dhtrunner.cpp:144:19: error: ambiguous overload for 'operator=' (operand types are 'dht::Address {aka std::pair}' and

Bug#839330: marked as done (ring: FTBFS: dhtrunner.cpp:144:19: error: ambiguous overload for 'operator=' (operand types are 'dht::Address {aka std::pair<sockaddr_storage, unsigned int>}' and '

Your message dated Fri, 4 Nov 2016 21:38:14 -0400 with message-id <61813ac3-9e96-415b-91ec-f3d45dbb3...@debian.org> and subject line Fixed in 20161103.1.60700d3~dfsg1-1 has caused the Debian Bug report #839330, regarding ring: FTBFS: dhtrunner.cpp:144:19: error: ambiguous overload for 'operator='

Processed: fixed 839330 in 20161103.1.60700d3~dfsg1-1

Processing commands for cont...@bugs.debian.org: > fixed 839330 20161103.1.60700d3~dfsg1-1 Bug #839330 {Done: Alexandre Viau } [src:ring] ring: FTBFS: dhtrunner.cpp:144:19: error: ambiguous overload for 'operator=' (operand types are 'dht::Address {aka

Bug#842080: marked as done (pcmanfm-qt: Attempting any action on a file or folder causes immediate crash.)

Your message dated Sat, 05 Nov 2016 01:33:52 + with message-id and subject line Bug#842080: fixed in pcmanfm-qt 0.11.1-3 has caused the Debian Bug report #842080, regarding pcmanfm-qt: Attempting any action on a file or folder causes immediate crash. to

Bug#833055: Packaging of mongoclient replacement library: mongocxx

Hi Apollon, Il 04/nov/2016 14:13, "Apollon Oikonomopoulos" ha scritto: > First of all, thanks for packaging the MongoDB C++ driver! You are welcome. :-) > Now that Debian has moved to MongoDB 2.6+, it would be great if we could > upload libmongoclient-dev to unstable What

Bug#827199: hfst: FTBFS: twolc test fails on big-endian systems

On 4 November 2016 at 20:49, Jonathan Wiltshire wrote: > > > While it did successfully build in the past, that was only because the > test > > > suite was disabled until recently. The tests revealed the unsigned char > > > issue which was easy to fix, and now the endian issue

Bug#828515: marked as done (pulseaudio: FTBFS with openssl 1.1.0)

Your message dated Fri, 04 Nov 2016 23:37:33 + with message-id and subject line Bug#828515: fixed in pulseaudio 9.0-5 has caused the Debian Bug report #828515, regarding pulseaudio: FTBFS with openssl 1.1.0 to be marked as done. This means that you claim

Processed: tagging 843160, severity of 843160 is serious ...

Processing commands for cont...@bugs.debian.org: > tags 843160 - moreinfo Bug #843160 [udev] udev: systemd-udevd times out Removed tag(s) moreinfo. > severity 843160 serious Bug #843160 [udev] udev: systemd-udevd times out Severity set to 'serious' from 'important' > retitle 843160

Bug#843199: perf is linked to libcrypto - licence incompatibility

Package: src:linux Version: 4.7.8-1 Severity: serious perf uses SHA1 and MD5 implementations from OpenSSL's libcrypto if it is found at build time. Since perf is under GPLv2 without an OpenSSL exception, this isn't allowed in Debian. We need to disable this feature or substitute implementations

Bug#675936: marked as done (E: Could not perform immediate configuration on 'libhdf5-serial-dev')

Your message dated Fri, 4 Nov 2016 21:34:27 +0100 with message-id <144f2c16-847d-80a7-368d-cd17c56c8...@debian.org> and subject line Fixed a long time ago has caused the Debian Bug report #675936, regarding E: Could not perform immediate configuration on 'libhdf5-serial-dev' to be marked as done.

Bug#843196: pythonmagick: FTBFS: can't identify Python 3 support library

Source: pythonmagick Version: 0.9.14-2 Severity: serious Justification: fails to build from source (but built successfully in the past) Automated builds of pythonmagick have been failing; for some reason, configure hasn't been able to identify an appropriate Boost.Python support library for

Bug#821530: Fix from Ubuntu for sparkline-php

Control: tags -1 patch The fix I found in Ubuntu for this bug is attached. cu Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said.

Bug#822699: Fix for the libucimf FTBFS

Control: tags -1 patch What broke the build is that gcc 6 changed the default C++ standard from C++98 to C++14. Not all valid C++98 code is also valid C++11 and C++14 code. Note that this just changed the default, when told to process C++98 code gcc 6 does not differ in any significant way

Processed: Fix for the libucimf FTBFS

Processing control commands: > tags -1 patch Bug #822699 [libucimf] libucimf: FTBFS with GCC 6 Added tag(s) patch. -- 822699: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822699 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Processed: Fix from Ubuntu for sparkline-php

Processing control commands: > tags -1 patch Bug #821530 [libsparkline-php] libsparkline-php: PHP 7.0 Transition Added tag(s) patch. -- 821530: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=821530 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#827199: hfst: FTBFS: twolc test fails on big-endian systems

Hi, On Sat, Oct 01, 2016 at 06:42:04PM +0200, Emilio Pozuelo Monfort wrote: > On Wed, 15 Jun 2016 17:03:20 +0200 Tino Didriksen wrote: > > On 13 June 2016 at 18:00, Aaron M. Ucko wrote: > > > > > Justification: fails to build from source (but built

Processed: block 841911 with 843192

Processing commands for cont...@bugs.debian.org: > block 841911 with 843192 Bug #841911 [release.debian.org] transition: pari 841911 was not blocked by any bugs. 841911 was not blocking any bugs. Added blocking bug(s) of 841911: 843192 > thanks Stopping processing here. Please contact me if you

Bug#843175: marked as done (iio-sensor-proxy: file in non-standard top level directory: /rules.d)

Your message dated Fri, 04 Nov 2016 19:34:38 + with message-id and subject line Bug#843175: fixed in iio-sensor-proxy 1.3-2 has caused the Debian Bug report #843175, regarding iio-sensor-proxy: file in non-standard top level directory: /rules.d to be

Bug#843192: FTBFS on armel: 'check_qcurves' failed

Source: eclib Version: 20160720-1 Severity: serious Justification: FTBFS, but did so in the past Hi, During a rebuild for the pari transition, eclib failed its tests on armel: | Testing mmattest... | 3c3 | < egr bound = -8.66631e-40 | --- | > egr bound = 0 | Makefile:1293: recipe for target

Bug#833754: xerces-c: FTBFS on s390x with gcc6/icu57

I looked at it briefly, but had to refocus on other issues before I could really get anywhere. I'll get it sorted out and/or forwarded shortly. Thanks for the ping! On Thu, Nov 03, 2016 at 04:10:27PM -0400, Sandro Tosi wrote: > On Mon, 8 Aug 2016 13:24:48 + Mattia Rizzolo

Bug#811699: marked as done (FTBFS with GCC 6: macro passed X arguments, takes Y)

Your message dated Fri, 04 Nov 2016 18:50:09 + with message-id and subject line Bug#811699: fixed in mswatch 1.2.0-2.2 has caused the Debian Bug report #811699, regarding FTBFS with GCC 6: macro passed X arguments, takes Y to be marked as done. This means

Bug#843132: marked as done (freeorion: FTBFS with Boost 1.62)

Your message dated Fri, 04 Nov 2016 18:33:56 + with message-id and subject line Bug#843132: fixed in freeorion 0.4.6-3 has caused the Debian Bug report #843132, regarding freeorion: FTBFS with Boost 1.62 to be marked as done. This means that you claim

Bug#843132: tagged as pending

tag 843132 pending -- We believe that the bug #843132 you reported has been fixed in the Git repository. You can see the commit message below and/or inspect the commit contents at: http://anonscm.debian.org/cgit/pkg-games/freeorion.git/diff/?id=53fd71d (This message was generated

Processed: Bug#843132 tagged as pending

Processing commands for cont...@bugs.debian.org: > tag 843132 pending Bug #843132 [src:freeorion] freeorion: FTBFS with Boost 1.62 Added tag(s) pending. > -- Stopping processing here. Please contact me if you need assistance. -- 843132: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843132

Processed: tagging 842452

Processing commands for cont...@bugs.debian.org: > tags 842452 + pending Bug #842452 [libvirt] FTBFS depdnding on docs/apibuild.py timestamp (api docs not buildable) Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 842452:

Bug#843137: [buildd-tools-devel] Bug#843137: Bug#843137: sbuild: fails to deal with sid chroots (missing gpg)

Hi, Quoting Raphael Hertzog (2016-11-04 16:01:21) > On Fri, 04 Nov 2016, Johannes Schauer wrote: > > 2. the amount of effort required to cope with the changed situation in > > stretch > > (especially with respect to gpg) is huge. The existing patches are > > several > > hundred lines

Bug#842939: WOT found guilty to sell user data

B0;115;0cOn Fri, Nov 04, 2016 at 03:07:17AM +0100, ilf wrote: > kpcyrd: > >I think this project doesn't align with the debian goals and I > >would welcome if it's getting removed from current and future > >releases. > > Mozilla removed it from addons.mozilla.org: >

Bug#843137: [buildd-tools-devel] Bug#843137: Bug#843137: sbuild: fails to deal with sid chroots (missing gpg)

On Fri, 04 Nov 2016, Johannes Schauer wrote: > 2. the amount of effort required to cope with the changed situation in > stretch > (especially with respect to gpg) is huge. The existing patches are several > hundred lines long. Help would indeed be appreciated to backport these >

Processed: taglib-extras: diff for NMU version 1.0.1-3.1

Processing control commands: > tags 840329 + pending Bug #840329 [src:taglib-extras] taglib-extras: FTBFS: CMake Error at cmake/modules/FindTaglib.cmake:132 (message): Could not find Taglib Added tag(s) pending. -- 840329: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840329 Debian Bug

Bug#840329: taglib-extras: diff for NMU version 1.0.1-3.1

Control: tags 840329 + pending Dear maintainer, I've prepared an NMU for taglib-extras (versioned as 1.0.1-3.1) and uploaded it to DELAYED/5. Please feel free to tell me if I should delay it longer. Regards. -- WBR, wRAR diff -Nru taglib-extras-1.0.1/debian/changelog

Bug#843175: iio-sensor-proxy: file in non-standard top level directory: /rules.d

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On Fri, 2016-11-04 at 23:04 +0530, Ritesh Raj Sarraf wrote: > > I just picked a snapshot deb for 1.2-1 for an alpha build. Okay. Alpha is not a good example. :-) Issue seen on arm[all variants], i386 etc. - -- Ritesh Raj Sarraf |

Bug#843175: iio-sensor-proxy: file in non-standard top level directory: /rules.d

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On Fri, 2016-11-04 at 22:33 +0530, Ritesh Raj Sarraf wrote: > > Thanks for filing this bug report. I'll look into it. I just picked a snapshot deb for 1.2-1 for an alpha build. rrs@learner:~/rrs-home/Community/Packaging/iio-sensor-proxy (master)$

Bug#843175: iio-sensor-proxy: file in non-standard top level directory: /rules.d

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Control: tag -1 +confirmed On Fri, 2016-11-04 at 16:47 +, James Cowgill wrote: > It appears amd64 is fine, but all other arches are not. > > https://buildd.debian.org/status/fetch.php?pkg=iio-sensor-proxy=i386= > 1.3-1=1474117505 > > >

Processed: Re: Bug#843175: iio-sensor-proxy: file in non-standard top level directory: /rules.d

Processing control commands: > tag -1 +confirmed Bug #843175 [iio-sensor-proxy] iio-sensor-proxy: file in non-standard top level directory: /rules.d Added tag(s) confirmed. -- 843175: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843175 Debian Bug Tracking System Contact

Processed: Re: Bug#843175: iio-sensor-proxy: file in non-standard top level directory: /rules.d

Processing control commands: > tags -1 - moreinfo Bug #843175 [iio-sensor-proxy] iio-sensor-proxy: file in non-standard top level directory: /rules.d Removed tag(s) moreinfo. -- 843175: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843175 Debian Bug Tracking System Contact

Bug#843175: iio-sensor-proxy: file in non-standard top level directory: /rules.d

Control: tags -1 - moreinfo On 04/11/16 16:43, Ritesh Raj Sarraf wrote: > Control: tag -1 +moreinfo > > On Fri, 2016-11-04 at 15:25 +, James Cowgill wrote: > >> iio-sensor-proxy installs the file: >> /rules.d/80-iio-sensor-proxy.rules > > > You mean in /lib/udev/rules.d/ ? If so, I'm

Processed: Re: Bug#843175: iio-sensor-proxy: file in non-standard top level directory: /rules.d

Processing control commands: > tag -1 +moreinfo Bug #843175 [iio-sensor-proxy] iio-sensor-proxy: file in non-standard top level directory: /rules.d Added tag(s) moreinfo. -- 843175: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843175 Debian Bug Tracking System Contact ow...@bugs.debian.org

Bug#843175: iio-sensor-proxy: file in non-standard top level directory: /rules.d

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Control: tag -1 +moreinfo On Fri, 2016-11-04 at 15:25 +, James Cowgill wrote: > > iio-sensor-proxy installs the file: >  /rules.d/80-iio-sensor-proxy.rules > You mean in /lib/udev/rules.d/ ? If so, I'm curious how that is a policy violation.

Processed: Fix from Ubuntu for the libmarkdown-php FTBFS

Processing control commands: > tags -1 patch Bug #821522 [libmarkdown-php] libmarkdown-php: PHP 7.0 Transition Added tag(s) patch. -- 821522: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=821522 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#821522: Fix from Ubuntu for the libmarkdown-php FTBFS

Control: tags -1 patch The fix I found in Ubuntu for this bug is attached. cu Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said.

Bug#843083: marked as done (brial: FTBFS: hash discrepancies in UnitTests)

Your message dated Fri, 04 Nov 2016 16:33:41 + with message-id and subject line Bug#843083: fixed in brial 0.8.5-2 has caused the Debian Bug report #843083, regarding brial: FTBFS: hash discrepancies in UnitTests to be marked as done. This means that you

Bug#837960: marked as done (spdylay: FTBFS with openssl 1.1.0)

Your message dated Fri, 04 Nov 2016 16:21:23 + with message-id and subject line Bug#837960: fixed in spdylay 1.3.2-2.1 has caused the Debian Bug report #837960, regarding spdylay: FTBFS with openssl 1.1.0 to be marked as done. This means that you claim

Bug#367347: Not fixed?

Hi Rhonda, You reopened 367347 without any comments. Do you mind expanding on why you think it wasn't fixed as part of fixing 592917? Francois

Processed: severity of 843168 is wishlist

Processing commands for cont...@bugs.debian.org: > severity 843168 wishlist Bug #843168 [ftp.debian.org] deferred queue: does not showing delayed packages Severity set to 'wishlist' from 'grave' > thanks Stopping processing here. Please contact me if you need assistance. -- 843168:

Bug#826728: percona-toolkit: (CVE-2014-2029) scripts call back home and leak information

Hi guys, Sorry for the delay on this one. I was discussing this issue with upstream and I think we have a solution to disable 'version-check' for all tools in a single configuration file. I'm contacting upstream again and I let you know the procedure to follow in order to fix this bug. > >

Processed: Also send the control commands

Processing commands for cont...@bugs.debian.org: > retitle 828595 voms must (build-)depend on libssl1.0-dev Bug #828595 [src:voms] voms: FTBFS with openssl 1.1.0 Changed Bug title to 'voms must (build-)depend on libssl1.0-dev' from 'voms: FTBFS with openssl 1.1.0'. > block 828269 by 828595 Bug

Bug#828269: voms must (build-)depend on libssl1.0-dev

retitle 828595 voms must (build-)depend on libssl1.0-dev block 828269 by 828595 thanks voms must build-depend on libssl1.0-dev instead of libssl-dev and also change the dependency of voms-dev accordingly. This will not only fix the build (and RC bug) in voms, this is also required to fix condor

Processed: unarchive #818239

Processing commands for cont...@bugs.debian.org: > unarchive 818239 Bug #818239 {Done: Christian Hofstaedtler } [ohcount-doc] ohcount-doc: creates non-FHS /ruby directory Unarchived Bug 818239 > thanks Stopping processing here. Please contact me if you need assistance. --

Bug#818239: ohcount-doc: creates non-FHS /ruby directory

Control: found -1 3.0.0-8.2 Changelog: > ohcount (3.0.0-8.2) unstable; urgency=medium > . >* Non-maintainer upload. >* Source-ful, binary-less upload to get rid of /ruby directory. > Probably somehow my fault? (Closes: #818239) Apparently this didn't work. See the arch:all build

Bug#837402: Thanks

Thanks Adrian! Will upload when #828269 has been dealt with. Michael -- Michael Hanke GPG: 4096R/C073D2287FFB9E9B http://psychoinformatics.de

Processed: Bug#818239: ohcount-doc: creates non-FHS /ruby directory

Processing control commands: > found -1 3.0.0-8.2 Bug #818239 {Done: Christian Hofstaedtler } [ohcount-doc] ohcount-doc: creates non-FHS /ruby directory Marked as found in versions ohcount/3.0.0-8.2; no longer marked as fixed in versions ohcount/3.0.0-8.2 and reopened. --

Bug#843175: iio-sensor-proxy: file in non-standard top level directory: /rules.d

Package: iio-sensor-proxy Version: 1.3-1 Severity: serious Justification: Policy 9.1 Hi, iio-sensor-proxy installs the file: /rules.d/80-iio-sensor-proxy.rules Since this file is in a non-standard top level directory, it is prohibited by the FHS. Thanks, James signature.asc Description:

Bug#841596: marked as done (sqlobject: FTBFS: tests failed)

Your message dated Fri, 04 Nov 2016 15:19:18 + with message-id and subject line Bug#841596: fixed in sqlobject 3.1.0+dfsg-2 has caused the Debian Bug report #841596, regarding sqlobject: FTBFS: tests failed to be marked as done. This means that you claim

Bug#828453: nginx: FTBFS with openssl 1.1.0

On Fri, Nov 04, 2016 at 10:03:02AM +0200, Christos Trochalakis wrote: > On Wed, Nov 02, 2016 at 05:22:21PM +0100, Kurt Roeckx wrote: > > On Wed, Nov 02, 2016 at 10:39:29AM +0100, Moritz Muehlenhoff wrote: > > > > > > The issue hasn't been diagnosed upstream, but this will likely also > > >

Bug#843166: kodi: block migration to testing untill all reverse dependencies are ready

On 4 November 2016 at 11:57, Bálint Réczey wrote: > Hi Felipe, > > 2016-11-04 15:50 GMT+01:00 Felipe Sateler : >> On 4 November 2016 at 11:21, Balint Reczey wrote: >>> Source: kodi >>> Version: 17.0~beta5+dfsg1-1 >>> Severity:

Bug#843166: kodi: block migration to testing untill all reverse dependencies are ready

Hi Felipe, 2016-11-04 15:50 GMT+01:00 Felipe Sateler : > On 4 November 2016 at 11:21, Balint Reczey wrote: >> Source: kodi >> Version: 17.0~beta5+dfsg1-1 >> Severity: grave >> >> To not break testing users' addon configuration I'm blocking kodi's >>

Bug#843166: kodi: block migration to testing untill all reverse dependencies are ready

On 4 November 2016 at 11:21, Balint Reczey wrote: > Source: kodi > Version: 17.0~beta5+dfsg1-1 > Severity: grave > > To not break testing users' addon configuration I'm blocking kodi's > migration to testing until all addons are ready to migrate together. > > Close this

Bug#835437: pycurl: FTBFS too much often (failing tests)

On Nov 03, 2016, at 08:32 PM, Santiago Vila wrote: >My recommendation: Please find the way to disable any tests which >perform network access, I have the strong feeling that the build would >never hang if those tests are disabled. +1 - unfortunately I just don't have any spare cycles right now.

Bug#843169: xbmc-eventclients-j2me: uninstallable in unstable

Package: xbmc-eventclients-j2me Version: 17.0~beta5+dfsg1-1 Severity: serious Tags: sid stretch Hi, The xbmc-eventclients-j2me cannot be installed in unstable. The kodi-eventclients-j2me package does not exist. $ sudo apt-get install -o Debug::pkgProblemResolver=true xbmc-eventclients-j2me

Bug#843168: deferred queue: does not showing delayed packages

Package: ftp.debian.org Severity: grave Justification: renders package unusable Hi, The deferred queue[1] is empty and does not show the recent uploaded packages. It is bad because breaks the control over all NMU situation. [1] https://ftp-master.debian.org/deferred.html Thanks in advance.

Bug#843166: kodi: block migration to testing untill all reverse dependencies are ready

Source: kodi Version: 17.0~beta5+dfsg1-1 Severity: grave To not break testing users' addon configuration I'm blocking kodi's migration to testing until all addons are ready to migrate together. Close this bug when all reverse dependencies are ready. Cheers, Balint

Bug#837572: marked as done (open-coarrays: FTBFS with bindnow and PIE enabled)

Your message dated Fri, 4 Nov 2016 14:09:43 + with message-id <3fae5f7b-dcf5-e1f5-f537-510336d58...@debian.org> and subject line close has caused the Debian Bug report #837572, regarding open-coarrays: FTBFS with bindnow and PIE enabled to be marked as done. This means that you claim that the

Processed: tagging 828370

Processing commands for cont...@bugs.debian.org: > tags 828370 + pending Bug #828370 [src:kvirc] kvirc: FTBFS with openssl 1.1.0 Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 828370: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828370

Processed: tagging 811908

Processing commands for cont...@bugs.debian.org: > tags 811908 + pending Bug #811908 [kvirc] kvirc: FTBFS with GCC 6: invalid conversion Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 811908:

Bug#843137: [buildd-tools-devel] Bug#843137: Bug#843137: sbuild: fails to deal with sid chroots (missing gpg)

Hi KiBi & Raphaël, Quoting Cyril Brulebois (2016-11-04 08:29:06) > Raphael Hertzog (2016-11-04): > > On Fri, 04 Nov 2016, Cyril Brulebois wrote: > > > a brand new unstable chroot isn't usable for a build with default (as > > > far as I can remember) sbuild configuration. Full

Processed: Bug is also in the stretch version

Processing commands for cont...@bugs.debian.org: > found 841575 2.4.1~ds1-1 Bug #841575 [src:docker-registry] docker-registry: FTBFS: Tests failures Marked as found in versions docker-registry/2.4.1~ds1-1. > found 843079 1.2.1-1 Bug #843079 [src:python-mpop] python-mpop's autopkg tests are

Bug#826728: percona-toolkit: (CVE-2014-2029) scripts call back home and leak information

Hi! On Thu, 2016-11-03 at 13:51:40 -0400, Sandro Tosi wrote: > On Wed, 8 Jun 2016 14:21:14 +0200 Guillem Jover wrote: > > This package contains many scripts which call back home to check for > > a new upstream versions. In addition they also report back things such > > as

Bug#843137: [buildd-tools-devel] Bug#843137: sbuild: fails to deal with sid chroots (missing gpg)

Hi, Quoting Cyril Brulebois (2016-11-04 08:31:39) > Backports is not for fixing bugs in stable. yes, that's why I'm not closing this. > If you need help preparing a stable update to address this, please say so. there are two issues with performing a stable update: 1. should tools in stable

Bug#842939: xul-ext-wot: WOT found guilty to sell user data

I don't think, that removing this package from Debian is the right way. Users who have it installed get no notice and would keep this (apparent) malware. There should be a new package version, that does not contain the plugin anymore (like transitional packages), for both stable-sec and unstable

Bug#835801: marked as done (vboot-utils: FTBFS with openssl 1.1.0)

Your message dated Fri, 04 Nov 2016 13:20:38 + with message-id and subject line Bug#835801: fixed in vboot-utils 0~R52-8350.B-2 has caused the Debian Bug report #835801, regarding vboot-utils: FTBFS with openssl 1.1.0 to be marked as done. This means that

Bug#833055: Packaging of mongoclient replacement library: mongocxx

Hello Giulio, First of all, thanks for packaging the MongoDB C++ driver! Now that Debian has moved to MongoDB 2.6+, it would be great if we could upload libmongoclient-dev to unstable (and possibly have mongo-cxx-driver-legacy provide mongodb-dev as a metapackage as well), as at least one

Bug#823330: I upgraded this morning to the fixed version and it does not work with my tsocks

I reinstalled the version I regenrated using the configure witout the --enable-hostnames and it works again. Did you check the patch is actually working? I just removed the --enable-hostnames from the configure command in debian/rules on my side.

Bug#840428: marked as done (pythonmagick: FTBFS with newer experimental version of imagemagick)

Your message dated Fri, 04 Nov 2016 13:00:11 + with message-id and subject line Bug#840428: fixed in pythonmagick 0.9.14-2 has caused the Debian Bug report #840428, regarding pythonmagick: FTBFS with newer experimental version of imagemagick to be marked

Processed: reopen bug

Processing commands for cont...@bugs.debian.org: > reopen 823330 Bug #823330 {Done: gustavo panizzo } [tsocks] tsocks: The actual configure command disable host name resolution in tsocks.conf when it was supposed to enable it 'reopen' may be inappropriate when a bug has been

Bug#833055: Packaging of mongoclient replacement library: mongocxx

Hi Raphael, On 11:14 Thu 03 Nov , Raphael Hertzog wrote: > Hello Apollon, > > mongodb dropped the C++ client driver that it used to provide in > mongodb-dev in favor of https://github.com/mongodb/mongo-cxx-driver Indeed, as of 2.6 the drivers are no longer part of the

Bug#843161: openvas-manager: FTBFS when not building -common

Source: openvas-manager Version: 6.0.9-1 Severity: serious Justification: fails to build from source (but built successfully in the past) [Reporting this bug as a regression because it would affect binNMUs.] Builds of openvas-manager covering only its architecture-dependent binary packages, as

Bug#843148: marked as done (gitlab-workhorse failing to build on s390x)

Your message dated Fri, 04 Nov 2016 12:18:37 + with message-id and subject line Bug#843148: fixed in gitlab-workhorse 0.8.5+debian-3 has caused the Debian Bug report #843148, regarding gitlab-workhorse failing to build on s390x to be marked as done. This

Bug#833741: patch/nmu ?

tags 833741 + patch thanks Is there any reason not to apply that patch ?

Processed: retitle 842891 to libimage-info-perl: CVE-2016-9181: XXE in SVG files

Processing commands for cont...@bugs.debian.org: > retitle 842891 libimage-info-perl: CVE-2016-9181: XXE in SVG files Bug #842891 {Done: Salvatore Bonaccorso } [src:libimage-info-perl] libimage-info-perl: XXE in SVG files Changed Bug title to 'libimage-info-perl:

Processed: Bug#833741: patch/nmu ?

Processing commands for cont...@bugs.debian.org: > tags 833741 + patch Bug #833741 [pepperflashplugin-nonfree] pepperflashplugin-nonfree: Feature request?: Download from Adobe instead of Google. Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. --

Processed: retitle

Processing commands for cont...@bugs.debian.org: > retitle 843159 'always build gitlab-workhorse on zandonai (s390x)' Bug #843159 [buildd.debian.org] gitlab-workhorse failing to build on s390x Changed Bug title to ''always build gitlab-workhorse on zandonai (s390x)'' from 'gitlab-workhorse

Processed (with 1 error): reassign to buildd.debian.org

Processing commands for cont...@bugs.debian.org: > clone 843148 -1 Bug #843148 [gitlab-workhorse] gitlab-workhorse failing to build on s390x Bug 843148 cloned as bug 843159 > reassign -1 buildd.debian.org Bug #843159 [gitlab-workhorse] gitlab-workhorse failing to build on s390x Bug reassigned

Bug#843141: src:ga hijacked libga-dev from another package

On 4 November 2016 at 13:11, Adrian Bunk wrote: > this is not an option, since that would upgrade jessie users of > libga-dev to a completely unrelated package. Ah, good point. Thanks!

Processed: block 828269 with 828595

Processing commands for cont...@bugs.debian.org: > block 828269 with 828595 Bug #828269 [src:condor] condor: FTBFS with openssl 1.1.0 828269 was not blocked by any bugs. 828269 was blocking: 827061 Added blocking bug(s) of 828269: 828595 > thanks Stopping processing here. Please contact me if

  1   2   >