Bug#896614: marked as done (pyxb FTBFS with sphinx 1.7.2)

Your message dated Mon, 30 Apr 2018 05:49:54 + with message-id and subject line Bug#896614: fixed in pyxb 1.2.6+dfsg-2 has caused the Debian Bug report #896614, regarding pyxb FTBFS with sphinx 1.7.2 to be marked as done. This means that you claim that

Bug#894770: alternative workaround

For those who need to get work done but are stuck due to this bug here is an alternative work around that I was previously unaware of. (I know this isn't exactly bug information but it will probably help quite a few people that arrive on this page looking for a solution) Just install the package

Bug#897151: Package erroneously expects googletest headers in /usr/include

Control: tags -1 +pending On Mon, Apr 30, 2018 at 5:37 AM Andres Salomon wrote: > Protobuf 3.0.0-9.1 (the version in unstable) already depends upon > libgtest-dev; the FTBFS is due to a missing build-dependency > on libgmock-dev. > The version of protobuf in experimental

Processed: Re: Package erroneously expects googletest headers in /usr/include

Processing control commands: > tags -1 +pending Bug #897151 [src:protobuf] Package erroneously expects googletest headers in /usr/include Added tag(s) pending. -- 897151: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897151 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Bug#897151: Package erroneously expects googletest headers in /usr/include

Hi, Protobuf 3.0.0-9.1 (the version in unstable) already depends upon libgtest-dev; the FTBFS is due to a missing build-dependency on libgmock-dev. The version of protobuf in experimental (3.5.2-2) includes a build-dep on both libgtest-dev and libgmock-dev, so it should build properly with the

Bug#895923: marked as done (ruby-pkg-config: FTBFS and Debci failure)

Your message dated Mon, 30 Apr 2018 02:52:14 + with message-id and subject line Bug#895923: fixed in ruby-pkg-config 1.3.1-1 has caused the Debian Bug report #895923, regarding ruby-pkg-config: FTBFS and Debci failure to be marked as done. This means that

Bug#896074: marked as done (ruby-pkg-config: autopkgtest fails since cairo 1.15.10-3)

Your message dated Mon, 30 Apr 2018 02:52:14 + with message-id and subject line Bug#895923: fixed in ruby-pkg-config 1.3.1-1 has caused the Debian Bug report #895923, regarding ruby-pkg-config: autopkgtest fails since cairo 1.15.10-3 to be marked as done.

Bug#877202: Bug #877202 in pyxdg marked as pending

Control: tag -1 pending Hello, Bug #877202 in pyxdg 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:

Processed: Bug #877202 in pyxdg marked as pending

Processing control commands: > tag -1 pending Bug #877202 [src:pyxdg] pyxdg FTBFS and Debci failure: ERROR: test_validate_icon_theme (test-icon.IconThemeTest) Added tag(s) pending. -- 877202: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=877202 Debian Bug Tracking System Contact

Bug#896939: marked as done (wmweather+: Segfaults on startup)

Your message dated Sun, 29 Apr 2018 23:52:24 + with message-id and subject line Bug#896939: fixed in wmweather+ 2.17-1 has caused the Debian Bug report #896939, regarding wmweather+: Segfaults on startup to be marked as done. This means that you claim

Bug#894469: marked as done (crystalhd FTBFS with gstreamer 1.14)

Your message dated Sun, 29 Apr 2018 22:34:24 + with message-id and subject line Bug#894469: fixed in crystalhd 1:0.0~git20110715.fdd2f19-13 has caused the Debian Bug report #894469, regarding crystalhd FTBFS with gstreamer 1.14 to be marked as done. This

Processed: reopening 895718

Processing commands for cont...@bugs.debian.org: > reopen 895718 Bug #895718 {Done: Dmitry Shachnev } [python-pyqt5] python-pyqt5: import PyQt5.QtCore fails Bug reopened Ignoring request to alter fixed versions of bug #895718 to the same values previously set > severity

Bug#895718: python-pyqt5: import PyQt5.QtCore fails

On Wed, 18 Apr 2018 12:48:27 +0300 Dmitry Shachnev wrote: > On Sun, Apr 15, 2018 at 01:26:50PM +0300, Dmitry Shachnev wrote: > > Works for me in a clean sid chroot. > > The CI tests for pyqt5 are also passing [1], so I am closing this bug. > > [1]:

Processed: Re: [reportbug] Crash when report type set to None

Processing control commands: > tags -1 unreproducible moreinfo Bug #892270 [reportbug] [reportbug] Crash when report type set to None Added tag(s) moreinfo and unreproducible. > severity -1 important Bug #892270 [reportbug] [reportbug] Crash when report type set to None Severity set to

Bug#892270: [reportbug] Crash when report type set to None

control: tags -1 unreproducible moreinfo control: severity -1 important Hi Jérôme, On 7 Mar 2018 Jérôme Bardot wrote: > Reportbug (gtk2 ui) crash when i select package. > > The command line  output : > > Traceback (most recent call last): >   File "/usr/bin/reportbug", line 2265, in >    

Bug#895778: jruby: Several security vulnerabilities

Hi Miguel, I have prepared security updates for Jessie and Stretch. Unfortunately I discovered that jruby in Jessie FTBFS at the moment. This is unrelated to the patches. Do you know how to resolve that? generate-method-classes: _gmc_internal_: [echo] Generating invokers... [java]

Bug#896459: marked as done (qscintilla2 FTBFS with Qt 5.10: symbol differences)

Your message dated Sun, 29 Apr 2018 21:20:34 + with message-id and subject line Bug#896459: fixed in qscintilla2 2.10.4+dfsg-1 has caused the Debian Bug report #896459, regarding qscintilla2 FTBFS with Qt 5.10: symbol differences to be marked as done.

Bug#894642: [Pkg-sugar-devel] Bug#894642: gst-plugins-espeak: diff for NMU version 0.4.0-3.1

Will you be sending this upstream? https://github.com/sugarlabs/gst-plugins-espeak -- James Cameron http://quozl.netrek.org/

Processed: nvcc wants GCC 6 which we want to remove

Processing control commands: > severity -1 important Bug #892415 [nvidia-cuda-toolkit] nvcc wants GCC 6 which we want to remove Severity set to 'important' from 'serious' -- 892415: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892415 Debian Bug Tracking System Contact ow...@bugs.debian.org

Bug#892415: nvcc wants GCC 6 which we want to remove

Control: severity -1 important Hi I'm downgrading the severity of this bug so nvidia-cuda-toolkit can remain in testing for longer. I understand that gcc-6 will be removed before buster, but its removal is currently blocked by pdftk, a key package. Regards Graham

Processed: python-virtualenv autopkgtest fails due to python-pip issue

Processing commands for cont...@bugs.debian.org: > affects 896998 src:python-virtualenv Bug #896998 [src:python-pip] python-pip: missing required _vendor module. Broken ${python:Depends}? Added indication that 896998 affects src:python-virtualenv > thanks Stopping processing here. Please

Processed: Bug #896459 in qscintilla2 marked as pending

Processing control commands: > tag -1 pending Bug #896459 [src:qscintilla2] qscintilla2 FTBFS with Qt 5.10: symbol differences Added tag(s) pending. -- 896459: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896459 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#896459: Bug #896459 in qscintilla2 marked as pending

Control: tag -1 pending Hello, Bug #896459 in qscintilla2 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:

Processed: doit autopkgtest fails due to python-pip issue

Processing commands for cont...@bugs.debian.org: > affects 896998 src:doit Bug #896998 [src:python-pip] python-pip: missing required _vendor module. Broken ${python:Depends}? Added indication that 896998 affects src:doit > thanks Stopping processing here. Please contact me if you need

Bug#896998: python-pip: missing required _vendor module. Broken ${python:Depends}?

your proposed patch is certainly wrong. You need to find out why these references aren't resolved by the python-pip-whl package.

Bug#896751: marked as done (jinja2 FTBFS with sphinx 1.7.2)

Your message dated Sun, 29 Apr 2018 22:46:05 +0300 with message-id <20180429194605.ga5...@mitya57.me> and subject line Re: Bug#896751: jinja2 FTBFS with sphinx 1.7.2 has caused the Debian Bug report #896751, regarding jinja2 FTBFS with sphinx 1.7.2 to be marked as done. This means that you claim

Bug#896998: Not fixed in python-pip 9.0.1-2.2

Control: reopen -1 Control: notfixed -1 python-pip/9.0.1-2.2 Control: retitle -1 python-pip: missing required _vendor module. Broken ${python:Depends}? On Sat, Apr 28, 2018 at 07:15:24PM -0400, Nicholas D Steeves wrote: > On Sat, Apr 28, 2018 at 03:15:07PM +, Debian Bug Tracking System

Processed: Re: Bug#896998: Not fixed in python-pip 9.0.1-2.2

Processing control commands: > reopen -1 Bug #896998 {Done: Matthias Klose } [src:python-pip] python-pip: missing required _vendor module in 9.0.1-2.1 'reopen' may be inappropriate when a bug has been closed with a version; all fixed versions will be cleared, and you may need to

Bug#874146: marked as done (FTBFS with Java 9: all tests fail)

Your message dated Sun, 29 Apr 2018 19:19:56 + with message-id and subject line Bug#874146: fixed in ruby-rjb 1.5.5-2 has caused the Debian Bug report #874146, regarding FTBFS with Java 9: all tests fail to be marked as done. This means that you claim

Bug#874146: Bug #874146 in ruby-rjb marked as pending

Control: tag -1 pending Hello, Bug #874146 in ruby-rjb 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:

Processed: Bug #874146 in ruby-rjb marked as pending

Processing control commands: > tag -1 pending Bug #874146 [src:ruby-rjb] FTBFS with Java 9: all tests fail Added tag(s) pending. -- 874146: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874146 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#896263: django-haystack: 2 RC bugs => 1 MR

Dear maintainer, I believe those 2 bugs would be fixed by https://salsa.debian.org/python-team/modules/django-haystack/merge_requests/1 Could you have a look please? I see in https://github.com/django-haystack/django-haystack/pull/1603 that other people outside of Debian seem to have the

Bug#896550: kazam: Binding 'R' failed!

On Sun, Apr 22, 2018 at 4:48 AM, Davide Prina wrote: > And the key for start/stop registration don't work. > So I can set to save the screencast, start it, bug I cannot stop it (I can do > it with Ctrl-C or kill command, but I don't have the screencast with > something

Processed: tagging 896550

Processing commands for cont...@bugs.debian.org: > tags 896550 + moreinfo Bug #896550 [kazam] kazam: Binding 'R' failed! Added tag(s) moreinfo. > thanks Stopping processing here. Please contact me if you need assistance. -- 896550: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896550 Debian

Processed: fixed 878266 in libsdl2-image/2.0.0+dfsg-3+deb8u1, fixed 878266 in libsdl2-image/2.0.1+dfsg-2+deb9u1 ...

Processing commands for cont...@bugs.debian.org: > fixed 878266 libsdl2-image/2.0.0+dfsg-3+deb8u1 Bug #878266 {Done: Felix Geyer } [src:libsdl2-image] libsdl2-image: CVE-2017-2887: Incorrect XCF property handling Marked as fixed in versions libsdl2-image/2.0.0+dfsg-3+deb8u1. >

Bug#897175: marked as done (Package erroneously expects googletest headers in /usr/include)

Your message dated Sun, 29 Apr 2018 17:34:46 + with message-id and subject line Bug#897175: fixed in fmtlib 4.1.0+ds-2 has caused the Debian Bug report #897175, regarding Package erroneously expects googletest headers in /usr/include to be marked as done.

Bug#897099: diffoscope FTBFS with file 5.33

Chris Lamb wrote: > Cloning and re-assigning this second issue. This was #897153, which was fixed in src:file 1:5.33-1. :) Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-

Bug#896562: marked as done (emacs-pdf-tools: FTBFS against new libsynctex)

Your message dated Sun, 29 Apr 2018 17:05:23 + with message-id and subject line Bug#896562: fixed in emacs-pdf-tools 0.80-3 has caused the Debian Bug report #896562, regarding emacs-pdf-tools: FTBFS against new libsynctex to be marked as done. This means

Bug#896840: lintian: autopkgtest fails with new version of file

Hey Christoph et al., > > The more I think about it, the more I think this is a misleading > > and non-intuitive misfeature of file. […] > > Any thoughts before I essentially re-assign this? > > Rather somehow deal with it? Whilst I understand what you mean here, the problem is a little more

Bug#896567: texmaker: FTBFS against newer libsyntex

Control: tags -1 + patch Hello, Sebastian Ramacher, le dim. 22 avril 2018 13:20:24 +0200, a ecrit: > | ./pdfviewerwidget.cpp:988: undefined reference to `synctex_next_result' Here is a proposed patch. Samuel Index: texmaker-5.0.2/pdfviewer.cpp

Processed: Re: Bug#896567: texmaker: FTBFS against newer libsyntex

Processing control commands: > tags -1 + patch Bug #896567 [src:texmaker] texmaker: FTBFS against newer libsyntex Added tag(s) patch. -- 896567: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896567 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#896743: marked as done (grc: missing build dependency on dh-python)

Your message dated Sun, 29 Apr 2018 15:11:58 + with message-id and subject line Bug#896743: fixed in grc 1.11.3-1 has caused the Debian Bug report #896743, regarding grc: missing build dependency on dh-python to be marked as done. This means that you

Bug#897152: marked as done (Package erroneously expects googletest headers in /usr/include)

Your message dated Sun, 29 Apr 2018 15:11:34 + with message-id and subject line Bug#897152: fixed in flightcrew 0.7.2+dfsg-11 has caused the Debian Bug report #897152, regarding Package erroneously expects googletest headers in /usr/include to be marked as

Bug#897162: marked as done (fonts-cardo: missing font Reserved Font Name notice)

Your message dated Sun, 29 Apr 2018 15:05:31 + with message-id and subject line Bug#897162: fixed in cardo 1.04-3 has caused the Debian Bug report #897162, regarding fonts-cardo: missing font Reserved Font Name notice to be marked as done. This means that

Bug#896948: marked as done (auto-multiple-choice: automultiplechoice.dtx fails to compile)

Your message dated Sun, 29 Apr 2018 15:05:24 + with message-id and subject line Bug#896948: fixed in auto-multiple-choice 1.3.0-5 has caused the Debian Bug report #896948, regarding auto-multiple-choice: automultiplechoice.dtx fails to compile to be marked

Bug#896562: emacs-pdf-tools: FTBFS against new libsynctex

Control: tags -1 + patch Sebastian Ramacher, le dim. 22 avril 2018 13:12:31 +0200, a ecrit: > | epdfinfo.c:2974:3: error: unknown type name 'synctex_scanner_t'; use > 'struct' keyword to refer to the type Here is a proposed patch. Samuel Index: emacs-pdf-tools-0.80/server/epdfinfo.c

Processed: Re: Bug#896562: emacs-pdf-tools: FTBFS against new libsynctex

Processing control commands: > tags -1 + patch Bug #896562 [src:emacs-pdf-tools] emacs-pdf-tools: FTBFS against new libsynctex Added tag(s) patch. -- 896562: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896562 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#896566: gummi: FTBFS against new libsyntex

Control: tags -1 + patch Hello, Sebastian Ramacher, le dim. 22 avril 2018 13:17:48 +0200, a ecrit: > | gui/gui-preview.c:1044:5: error: unknown type name 'synctex_scanner_t'; use > 'struct' keyword to refer to the type Here is a proposed patch. Samuel Index: gummi-0.6.6/src/gui/gui-preview.c

Processed: Re: Bug#896566: gummi: FTBFS against new libsyntex

Processing control commands: > tags -1 + patch Bug #896566 [src:gummi] gummi: FTBFS against new libsyntex Added tag(s) patch. -- 896566: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896566 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#897152: Bug #897152 in flightcrew marked as pending

Thanks for the heads up. I looked at the commit and made a comment there. Not sure if you get notified... On April 29, 2018 8:54:32 AM CDT, mat...@debian.org wrote: >Control: tag -1 pending > >Hello, > >Bug #897152 in flightcrew reported by you has been fixed in the >Git repository and is

Bug#897152: Bug #897152 in flightcrew marked as pending

On Sun, Apr 29, 2018 at 09:11:45AM -0500, Steve Robbins wrote: > Thanks for the heads up. I looked at the commit and made a comment there. > Not sure if you get notified... I did, but it was kind of too late since I had already uploaded… (pushed everything and dput at the same time, not good

Processed: Bug #897152 in flightcrew marked as pending

Processing control commands: > tag -1 pending Bug #897152 [src:flightcrew] Package erroneously expects googletest headers in /usr/include Added tag(s) pending. -- 897152: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897152 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Bug#897152: Bug #897152 in flightcrew marked as pending

Control: tag -1 pending Hello, Bug #897152 in flightcrew 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:

Bug#879489: marked as done (cadvisor FTBFS on amd64)

Your message dated Sun, 29 Apr 2018 13:49:33 + with message-id and subject line Bug#879489: fixed in cadvisor 0.27.1+dfsg1-1 has caused the Debian Bug report #879489, regarding cadvisor FTBFS on amd64 to be marked as done. This means that you claim that

Processed: Bug #879489 in cadvisor marked as pending

Processing control commands: > tag -1 pending Bug #879489 [src:cadvisor] cadvisor FTBFS on amd64 Added tag(s) pending. -- 879489: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=879489 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#879489: Bug #879489 in cadvisor marked as pending

Control: tag -1 pending Hello, Bug #879489 in cadvisor 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:

Processed: attempt to force merge fixed gimp-python bugs

Processing commands for cont...@bugs.debian.org: > forcemerge 897167 897177 Bug #897167 {Done: Jeremy Bicha } [gimp-python] gimp-python doesn't install due to file conflict with package gimp Bug #897177 [gimp-python] trying to overwrite '/usr/lib/gimp/2.0/environ/pygimp.env',

Bug#897177: trying to overwrite '/usr/lib/gimp/2.0/environ/pygimp.env', which is also in package gimp 2.10.0-2

Package: gimp-python Severity: grave Dear Maintainer, tried to install gimp-python - result: reparing to unpack .../gimp-python_2.10.0-2_amd64.deb ... Unpacking gimp-python (2.10.0-2) ... dpkg: error processing archive /var/cache/apt/archives/gimp-python_2.10.0-2_amd64.deb (--unpack): trying

Bug#896840: lintian: autopkgtest fails with new version of file

[ slight OT ] On Sun, Apr 29, 2018 at 01:01:08PM +0200, Christoph Biedl wrote: > Maintainer of the file package here - feel free to Cc me early, this > might or might not ease things. Since you are the maintainer…, let me suggest you next time try to test src:lintian and src:diffoscope

Processed: block 897104 with 897176

Processing commands for cont...@bugs.debian.org: > block 897104 with 897176 Bug #897104 [googletest] googletest: breakage due to files moved to other packages 897104 was blocked by: 897173 897171 897174 897152 897151 897149 897175 897104 was not blocking any bugs. Added blocking bug(s) of

Processed: block 897104 with 897175

Processing commands for cont...@bugs.debian.org: > block 897104 with 897175 Bug #897104 [googletest] googletest: breakage due to files moved to other packages 897104 was blocked by: 897149 897174 897171 897152 897173 897151 897104 was not blocking any bugs. Added blocking bug(s) of 897104:

Processed: block 897104 with 897174

Processing commands for cont...@bugs.debian.org: > block 897104 with 897174 Bug #897104 [googletest] googletest: breakage due to files moved to other packages 897104 was blocked by: 897151 897149 897171 897173 897152 897104 was not blocking any bugs. Added blocking bug(s) of 897104: 897174 >

Processed: block 897104 with 897171

Processing commands for cont...@bugs.debian.org: > block 897104 with 897171 Bug #897104 [googletest] googletest: breakage due to files moved to other packages 897104 was blocked by: 897149 897151 897152 897104 was not blocking any bugs. Added blocking bug(s) of 897104: 897171 > thanks Stopping

Bug#897176: Package erroneously expects googletest headers in /usr/include

Package: src:cctz Severity: serious Justification: fails to build from source (but built successfully in the past) control: block 897104 by -1 Hi, The googletest package provides full sources -- including header files -- in /usr/src/googletest. Prior to version 1.8.0-9, a second copy of the

Processed: block 897104 with 897173

Processing commands for cont...@bugs.debian.org: > block 897104 with 897173 Bug #897104 [googletest] googletest: breakage due to files moved to other packages 897104 was blocked by: 897149 897171 897151 897152 897104 was not blocking any bugs. Added blocking bug(s) of 897104: 897173 > thanks

Bug#897175: Package erroneously expects googletest headers in /usr/include

Package: src:fmtlib Severity: serious Justification: fails to build from source (but built successfully in the past) control: block 897104 by -1 Hi, The googletest package provides full sources -- including header files -- in /usr/src/googletest. Prior to version 1.8.0-9, a second copy of the

Bug#897174: Package erroneously expects googletest headers in /usr/include

Package: src:meson Severity: serious Justification: fails to build from source (but built successfully in the past) Hi, The googletest package provides full sources -- including header files -- in /usr/src/googletest. Prior to version 1.8.0-9, a second copy of the headers was mistakenly

Bug#897160: marked as done (libgimp2.0-dev: missing dependency on libgegl-dev)

Your message dated Sun, 29 Apr 2018 12:35:24 + with message-id and subject line Bug#897160: fixed in gimp 2.10.0-3 has caused the Debian Bug report #897160, regarding libgimp2.0-dev: missing dependency on libgegl-dev to be marked as done. This means that

Bug#897167: marked as done (gimp-python doesn't install due to file conflict with package gimp)

Your message dated Sun, 29 Apr 2018 12:35:24 + with message-id and subject line Bug#897167: fixed in gimp 2.10.0-3 has caused the Debian Bug report #897167, regarding gimp-python doesn't install due to file conflict with package gimp to be marked as done.

Bug#897171: Package erroneously expects googletest headers in /usr/include

Package: src:synergy Severity: serious Justification: fails to build from source (but built successfully in the past) Hi, The googletest package provides full sources -- including header files -- in /usr/src/googletest. Prior to version 1.8.0-9, a second copy of the headers was mistakenly

Bug#897173: Package erroneously expects googletest headers in /usr/include

Package: src:aff4 Severity: serious Justification: fails to build from source (but built successfully in the past) Hi, The googletest package provides full sources -- including header files -- in /usr/src/googletest. Prior to version 1.8.0-9, a second copy of the headers was mistakenly

Bug#897172: FTBFS: pandoc 2.2

Source: haskell-blogliterately Version: 0.8.4.3-2 Severity: serious Forwarded: https://github.com/byorgey/BlogLiterately/issues/39 Jonas is about to upload pandoc 2.2

Processed: block 897104 with 897151

Processing commands for cont...@bugs.debian.org: > block 897104 with 897151 Bug #897104 [googletest] googletest: breakage due to files moved to other packages 897104 was blocked by: 897152 897149 897104 was not blocking any bugs. Added blocking bug(s) of 897104: 897151 > thanks Stopping

Bug#897167: Bug #897167 in gimp marked as pending

Control: tag -1 pending Hello, Bug #897167 in gimp 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:

Processed: Bug #897167 in gimp marked as pending

Processing control commands: > tag -1 pending Bug #897167 [gimp-python] gimp-python doesn't install due to file conflict with package gimp Added tag(s) pending. -- 897167: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897167 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Bug#897160: Bug #897160 in gimp marked as pending

Control: tag -1 pending Hello, Bug #897160 in gimp 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:

Processed: Bug #897160 in gimp marked as pending

Processing control commands: > tag -1 pending Bug #897160 [libgimp2.0-dev] libgimp2.0-dev: missing dependency on libgegl-dev Added tag(s) pending. -- 897160: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897160 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Processed: your mail

Processing commands for cont...@bugs.debian.org: > severity 897162 serious Bug #897162 [fonts-cardo] fonts-cardo: missing font Reserved Font Name notice Severity set to 'serious' from 'normal' > End of message, stopping processing here. Please contact me if you need assistance. -- 897162:

Bug#897167: gimp-python doesn't install due to file conflict with package gimp

Package: gimp-python Version: 2.10.0-2_amd64 Severity: grave Justification: renders package unusable Dear Maintainer, * What led up to the situation? I tried to install gimp-python with synaptic. * What was the outcome of this action? * What outcome did you expect instead? The package did not

Bug#897149: Package erroneously expects googletest headers in /usr/include

On Sat, Apr 28, 2018 at 11:20:46PM -0500, Steve M. Robbins wrote: > Your package relies on this behaviour and now fails to build since > googletest version 1.8.0-9 no longer installs the duplicate header > files. *sigh* Seems like we can solve this by: diff --git a/test/libapt/CMakeLists.txt

Bug#896840: lintian: autopkgtest fails with new version of file

[ Maintainer of the file package here - feel free to Cc me early, this might or might not ease things. ] Chris Lamb wrote... > [adding elb...@debian.org to CC] > > Chris Lamb wrote: > > > > This is caused by library having executable bits set, which is how the > > > pie executable vs

Bug#895673: marked as done (lios: Lios crashing on start)

Your message dated Sun, 29 Apr 2018 10:34:54 + with message-id and subject line Bug#895673: fixed in lios 2.7-2 has caused the Debian Bug report #895673, regarding lios: Lios crashing on start to be marked as done. This means that you claim that the

Processed: gpaw: please avoid distutils usage at runtime

Processing commands for cont...@bugs.debian.org: > forwarded 896595 https://gitlab.com/gpaw/gpaw/merge_requests/351 Bug #896595 [src:gpaw] please avoid distutils usage at runtime Set Bug forwarded-to-address to 'https://gitlab.com/gpaw/gpaw/merge_requests/351'. > thanks Stopping processing here.

Processed: libgimp2.0-dev: missing dependency on libgegl-dev

Processing control commands: > affects -1 src:gimp-dds src:gimplensfun src:gtkam Bug #897160 [libgimp2.0-dev] libgimp2.0-dev: missing dependency on libgegl-dev Added indication that 897160 affects src:gimp-dds, src:gimplensfun, and src:gtkam -- 897160:

Bug#897160: libgimp2.0-dev: missing dependency on libgegl-dev

Package: libgimp2.0-dev Version: 2.10.0-2 Severity: serious Control: affects -1 src:gimp-dds src:gimplensfun src:gtkam https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/gimp-dds.html https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/gimplensfun.html

Bug#896548: gunicorn: CVE-2018-1000164

On Mon, Apr 23, 2018 at 12:41:31PM +0100, Chris Lamb wrote: > Hi Moritz, > > > > > gunicorn: CVE-2018-1000164 > > > > > > I've prepared an upload for jessie. Permission to upload? :) > > > > Thanks, please upload. > > gunicorn_19.0-1+deb8u1_amd64.changes uploaded. Released yesterday, thanks.

Processed: bug 897111 is forwarded to https://github.com/bebraw/pypandoc/issues/149

Processing commands for cont...@bugs.debian.org: > forwarded 897111 https://github.com/bebraw/pypandoc/issues/149 Bug #897111 [src:pypandoc] pypandoc FTBFS with pandoc 2.1.2 Set Bug forwarded-to-address to 'https://github.com/bebraw/pypandoc/issues/149'. > thanks Stopping processing here. Please

Bug#894371: gdcm FTBFS with openjdk-9

>As a workaround to let the poppler transition complete in raspbian I >whipped up a version of the package that forces openjdk-8. I intend to do the same, best Gert

Processed: libgc: diff for NMU version 1:7.4.2-8.3

Processing control commands: > tags 887315 + patch Bug #887315 [src:libgc] libgc FTBFS on armel: missing symbol AO_locks Added tag(s) patch. > tags 887315 + pending Bug #887315 [src:libgc] libgc FTBFS on armel: missing symbol AO_locks Added tag(s) pending. -- 887315:

Bug#887315: libgc: diff for NMU version 1:7.4.2-8.3

Control: tags 887315 + patch Control: tags 887315 + pending Dear maintainer, I've prepared an NMU for libgc (versioned as 1:7.4.2-8.3) and uploaded it to DELAYED/7. Please feel free to tell me if I should cancel it. cu Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly

Bug#888678: marked as done (dirdiff uses deprecated Tcl/Tk 8.5)

Your message dated Sun, 29 Apr 2018 07:49:18 + with message-id and subject line Bug#888678: fixed in dirdiff 2.1-7.2 has caused the Debian Bug report #888678, regarding dirdiff uses deprecated Tcl/Tk 8.5 to be marked as done. This means that you claim

Bug#897156: node-cache-base: FTBFS and Debci failure with node-is-extendable 1.0.1-1

Source: node-cache-base Version: 0.8.4-1 Severity: serious https://ci.debian.net/packages/n/node-cache-base/unstable/amd64/ https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/node-cache-base.html ... 39 passing (460ms) 5 failing 1) cache-base .union()

Bug#888678: Please NMU dirdiff

Hi Tomas, On Sat, Apr 28, 2018 at 10:17 PM Tomas Pospisek wrote: > Hello Sergei, > dirdiff is going to be removed from unstable/testing on the 5th of Mai. > Unless you have been in communication with Santiago and he has a plan > on how to move forward with this issue, I'd

Processed: reopen

Processing commands for cont...@bugs.debian.org: > unarchive 893367 Bug #893367 {Done: Ryan Kavanagh } [opensmtpd] "smtpctl stop" not supported by upstream anymore Unarchived Bug 893367 > found 893367 6.0.3p1-3 Bug #893367 {Done: Ryan Kavanagh } [opensmtpd]

Bug#896484: marked as done (jmodeltest FTBFS with TeX Live 2018)

Your message dated Sun, 29 Apr 2018 06:05:07 + with message-id and subject line Bug#896484: fixed in jmodeltest 2.1.10+dfsg-6 has caused the Debian Bug report #896484, regarding jmodeltest FTBFS with TeX Live 2018 to be marked as done. This means that you