Bug#819404: libnagios-plugin-perl: should not be released in Stretch

Source: libnagios-plugin-perl Severity: serious Justification: unsuitable for release Hi, libnagios-plugin-perl is obsolted and should not be released with stretch. Filling this bug so that it get's autoremoved from testing. Regards, Salvatore

Bug#800272: qmtest: Please migrate a supported debhelper compat level

Package: qmtest Version: 2.4.1-2 Followup-For: Bug #800272 User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu xenial ubuntu-patch Dear Maintainer, In Ubuntu, the attached patch was applied to achieve the following: * debian/rules: - Remove legacy DH_COMPAT export. - Use

Bug#800225: recite: Please migrate a supported debhelper compat level

Package: recite Version: 1.0-8.2 Followup-For: Bug #800225 User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu xenial ubuntu-patch Dear Maintainer, In Ubuntu, the attached patch was applied to achieve the following: * debian/compat: Change compatibility level to 9. * debian/control:

Bug#800182: esix: Please migrate a supported debhelper compat level

Package: esix Version: 1-2 Followup-For: Bug #800182 User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu xenial ubuntu-patch Dear Maintainer, In Ubuntu, the attached patch was applied to achieve the following: * debian/rules: - Remove legacy DH_COMPAT export. - Add recommended

Bug#800218: x-pgp-sig-el: Please migrate a supported debhelper compat level

Package: x-pgp-sig-el Version: 1.3.5.1-4.1 Followup-For: Bug #800218 User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu xenial ubuntu-patch Dear Maintainer, In Ubuntu, the attached patch was applied to achieve the following: * debian/rules: - Remove legacy DH_COMPAT export. -

Bug#818529: marked as done (qsf: tries to install /usr/share/doc-base/doc-base file)

Your message dated Sun, 27 Mar 2016 23:35:32 + with message-id and subject line Bug#818529: fixed in qsf 1.2.7-1.2 has caused the Debian Bug report #818529, regarding qsf: tries to install /usr/share/doc-base/doc-base file to be marked as done. This means

Bug#818535: marked as done (mecab: FTBFS: error: required file './compile' not found)

Your message dated Sun, 27 Mar 2016 21:50:30 + with message-id and subject line Bug#818535: fixed in mecab 0.996-1.3 has caused the Debian Bug report #818535, regarding mecab: FTBFS: error: required file './compile' not found to be marked as done. This

Bug#802214: marked as done (node-connect: FTBFS: Uncaught Error: getaddrinfo ENOTFOUND [::1] [::1]:50403)

Your message dated Sun, 27 Mar 2016 21:50:48 + with message-id and subject line Bug#802214: fixed in node-connect 3.4.1-1 has caused the Debian Bug report #802214, regarding node-connect: FTBFS: Uncaught Error: getaddrinfo ENOTFOUND [::1] [::1]:50403 to

Processed: qwtplot3d FTBFS on armel and armhf

Processing commands for cont...@bugs.debian.org: > severity 816387 important Bug #816387 [qwtplot3d] qwtplot3d FTBFS on armel and armhf Severity set to 'important' from 'serious' > End of message, stopping processing here. Please contact me if you need assistance. -- 816387:

Bug#818590: [pkg-otr-team] Bug#818590: irssi-plugin-otr: mismatching ABI version with current irssi

Hi, On Sat, Mar 26, 2016 at 12:31:46PM +0100, intrigeri wrote: > In passing: I've no clue how many other irssi plugin packages are > affected as well. This can't be just irssi-plugin-otr, can it? apt-cache search irssi-plugin tells me there's only -plugin-xmpp and -plugin-robustirc… --

Bug#819179: marked as done (quagga: CVE-2016-2342)

Your message dated Sun, 27 Mar 2016 19:47:07 + with message-id and subject line Bug#819179: fixed in quagga 0.99.23.1-1+deb8u1 has caused the Debian Bug report #819179, regarding quagga: CVE-2016-2342 to be marked as done. This means that you claim that

Bug#819179: marked as done (quagga: CVE-2016-2342)

Your message dated Sun, 27 Mar 2016 19:47:33 + with message-id and subject line Bug#819179: fixed in quagga 0.99.22.4-1+wheezy2 has caused the Debian Bug report #819179, regarding quagga: CVE-2016-2342 to be marked as done. This means that you claim that

Bug#818590: [pkg-otr-team] Bug#818590: irssi-plugin-otr: mismatching ABI version with current irssi

Antoine Beaupré writes: > But before anyone starts working on this now - i have what i think is a > working package now here: > > http://paste.anarc.at/otr/ > > It's been tested by a friend, but i would appreciate more > testing. Waiting for an upstream release for a bit now

Bug#805684: python-box2d: FTBFS: swig doesn't like some comment styles any more

Thanks a lot Jonas, Eriberto (my sponsor) already uploaded the new changes. I'm currently starting at the packaging proccess and making some NMUs is great to achieve more experience. Are there any plans to update to pybox 2.3.1? Is there anything I can help? Samuel Henrique O. P. [samueloph]

Bug#805684: marked as done (python-box2d: FTBFS: swig doesn't like some comment styles any more)

Your message dated Sun, 27 Mar 2016 18:49:12 + with message-id and subject line Bug#805684: fixed in python-box2d 2.0.2+svn20100109.244-1.2 has caused the Debian Bug report #805684, regarding python-box2d: FTBFS: swig doesn't like some comment styles any

Bug#819375: libreoffice: FTBFS on ppc64el due to linking jawt from the wrong directory

Source: libreoffice Version: 1:4.3.3-2+deb8u3 Severity: serious Tags: upstream patch Justification: fails to build from source (but built successfully in the past) Dear Maintainer, java dir for power64 and power64le are now different for reasons listed in

Bug#819374: gitlab-shell: has a configuration file in /usr/share and modifies it; also creates a log file there and other links

Package: gitlab-shell Version: 2.6.10-1 Severity: serious The file /usr/share/gitlab-shell/config.yml is clearly a configuration file and is modified during the package installation. It also seems to be modified during package upgrading, which is another serious bug. In addition, a log file

Bug#811031: (no subject)

I would blame xorg for breaking compatibility. It is an excellent example of open source projects placing unnecessary obstacles in their own way. I don't think there really was a reason for this. It is just because some developer thought something would be more perfectly handled in another way

Bug#805684: [Debian-olpc-devel] Bug#805684:

Quoting SamuelOPH (2016-03-27 18:40:17) > I uploaded a NMU Thanks a lot! > to 10-day/delay queue. Feel free to cancel this upload if needed. On the contrary: Feel free to re-upload without deleay: Your changes are all excellent! - Jonas -- * Jonas Smedegaard - idealist &

Bug#805684:

Control: tags 805684 patch Control: tags 805684 pending Hi, I uploaded a NMU to 10-day/delay queue. Feel free to cancel this upload if needed. The debian/changelog is: python-box2d (2.0.2+svn20100109.244-1.2) unstable; urgency=medium * Non-maintainer upload. * debian/control: - Change

Processed:

Processing control commands: > tags 805684 patch Bug #805684 [src:python-box2d] python-box2d: FTBFS: swig doesn't like some comment styles any more Added tag(s) patch. > tags 805684 pending Bug #805684 [src:python-box2d] python-box2d: FTBFS: swig doesn't like some comment styles any more Added

Bug#819190: libgl1-nvidia-legacy-340xx-glx: post-installation-Skript returns error code 137

Control: tags -1 moreinfo On Thu, 2016-03-24 at 18:14 +0100, Peter Schütt wrote: > Package: libgl1-nvidia-legacy-340xx-glx > Version: 340.96-3 > Severity: critical > Justification: breaks the whole system > > First I deinstalled all of nvidia > > apt-get --purge remove *nvidia* > > apt-get

Processed: Re: Bug#819190: libgl1-nvidia-legacy-340xx-glx: post-installation-Skript returns error code 137

Processing control commands: > tags -1 moreinfo Bug #819190 [libgl1-nvidia-legacy-340xx-glx] libgl1-nvidia-legacy-340xx-glx: post-installation-Skript returns error code 137 Added tag(s) moreinfo. -- 819190: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=819190 Debian Bug Tracking System

Bug#812668: [m...@debian.org] Bug#812668: mailfilter: FTBFS - error: no match for 'operator='

* Andreas Bauer [2016-03-25 19:20 +0100]: > Hi Elimar, > > thanks again for letting me know about this issue and building the > patch. I too have tested the latest patch for a few weeks and just > made a release of it, as it seems to do the trick: > >

Bug#819316: closed by Andreas Tille <ti...@debian.org> (Bug#819316: fixed in plastimatch 1.6.2+dfsg-3)

You also have to request the removal of the old binaries reporting a bug against ftp.debian.org Emilio

Bug#814030: Security flaw fixed in version 6.2.0

On Sun, Feb 07, 2016 at 02:28:04PM -0400, David Prévot wrote: > Package: php-tcpdf > Version: 6.0.093+dfsg-1 > Severity: serious > Tags: security upstream > > According to their changelog [1], upstream fixed a security issue over a > year ago: > > 6.2.0 (2014-12-10) > - Bug #1005 "Security

Bug#818757: Bug#818757: orthanc-postgresql: does not start

Is there anything else I can provide to get this bug looked at ? Thanks, Karsten -- GPG key ID E4071346 @ eu.pool.sks-keyservers.net E167 67FD A291 2BEA 73BD 4537 78B9 A9F9 E407 1346

Bug#819316: marked as done (plastimatch: FTBFS on !x86)

Your message dated Sun, 27 Mar 2016 09:52:06 + with message-id and subject line Bug#819316: fixed in plastimatch 1.6.2+dfsg-3 has caused the Debian Bug report #819316, regarding plastimatch: FTBFS on !x86 to be marked as done. This means that you claim

Bug#808401: marked as done (plastimatch: FTBFS: itkGDCMSeriesFileNames.h:25:29: fatal error: gdcmSerieHelper.h: No such file or directory)

Your message dated Sun, 27 Mar 2016 09:52:06 + with message-id and subject line Bug#808401: fixed in plastimatch 1.6.2+dfsg-3 has caused the Debian Bug report #808401, regarding plastimatch: FTBFS: itkGDCMSeriesFileNames.h:25:29: fatal error:

Bug#818501: marked as done (FTBFS: Tests fail with segmentation fault)

Your message dated Sun, 27 Mar 2016 09:52:12 + with message-id and subject line Bug#818501: fixed in pytables 3.2.2-2 has caused the Debian Bug report #818501, regarding FTBFS: Tests fail with segmentation fault to be marked as done. This means that you

Bug#817071: marked as done (Backup fails if sync_first is used and some files are modified while rsync runs)

Your message dated Sun, 27 Mar 2016 09:52:28 + with message-id and subject line Bug#817071: fixed in rsnapshot 1.4.2-1 has caused the Debian Bug report #817071, regarding Backup fails if sync_first is used and some files are modified while rsync runs to

Bug#818122: docker.io: FTBFS in stretch

On 26 March 2016 at 23:37, Dmitry Smirnov wrote: > Thank you. It would be awesome if you could have a look whether you can build > newer Docker. I think I've uploaded most if not all the dependencies it needs > but there seems to be a problem with versioning of docker-notary

Processed: found 816700 in cups-filters/1.8.3-2

Processing commands for cont...@bugs.debian.org: > found 816700 cups-filters/1.8.3-2 Bug #816700 [cups-filters] foomatic-filters-beh and cups-filters: error when trying to install together Marked as found in versions cups-filters/1.8.3-2. > thanks Stopping processing here. Please contact me if

Bug#817233: marked as done (brotli: CVE-2016-1624 CVE-2016-1968)

Your message dated Sun, 27 Mar 2016 07:34:06 + with message-id and subject line Bug#817233: fixed in brotli 0.3.0+dfsg-3 has caused the Debian Bug report #817233, regarding brotli: CVE-2016-1624 CVE-2016-1968 to be marked as done. This means that you

Bug#818122: docker.io: FTBFS in stretch

On Saturday, 26 March 2016 11:20:43 PM AEDT Tianon Gravi wrote: > It looks like an API change in the new runc (libcontainer bits): I see... :( > Currently digging to figure out whether Docker upstream already has a > patch for the change to see how simple it'll be to convert over. Thank you. It

Bug#818122: docker.io: FTBFS in stretch

On 26 March 2016 at 21:54, Dmitry Smirnov wrote: > However Docker still FTBFS for another reason unrelated to runc as far as I > can tell... It looks like an API change in the new runc (libcontainer bits):