Bug#886518: marked as done (debhelper makes packages FTBFS: dh: Internal error: debian/rules install-arch is a rules target, but it is not supported to be!?)

Your message dated Sun, 07 Jan 2018 10:05:03 + with message-id and subject line Bug#886518: fixed in debhelper 11.1.1 has caused the Debian Bug report #886518, regarding debhelper makes packages FTBFS: dh: Internal error: debian/rules install-arch is a

Bug#884667: marked as done (2to3 binary moved to it's own 2to3 package)

Your message dated Sun, 07 Jan 2018 13:51:10 + with message-id and subject line Bug#884667: fixed in pycxx 7.0.3-1 has caused the Debian Bug report #884667, regarding 2to3 binary moved to it's own 2to3 package to be marked as done. This means that you

Bug#886518: debhelper makes packages FTBFS: dh: Internal error: debian/rules install-arch is a rules target, but it is not supported to be!?

On Sun, 7 Jan 2018 08:05:13 +0100 Helmut Grohne wrote: > Package: debhelper > Version: 11.1 > Severity: serious > Control: affects -1 + src:file > User: helm...@debian.org > Usertags: rebootstrap > > Building file started to fail tonight. The new error comes from > debhelper

Processed: found 886532 in 1:2.1+dfsg-11

Processing commands for cont...@bugs.debian.org: > found 886532 1:2.1+dfsg-11 Bug #886532 [qemu] Coming updates for meltdown/spectre Marked as found in versions qemu/1:2.1+dfsg-11. > thanks Stopping processing here. Please contact me if you need assistance. -- 886532:

Processed: Re: Bug#866480: Bug was closed in 0.13.1-1

Processing control commands: > fixed -1 0.13.1-2 Bug #866480 {Done: Andreas Tille } [src:skimage] skimage: depends on obsolete python-imaging (replace with python3-pil or python-pil) Marked as fixed in versions skimage/0.13.1-2. -- 866480:

Bug#886539: gajim-pgp (1.2.1-2~bpo9+1) depends on python3-gnupg (>= 0.4.1), that is not available

Package: gajim-pgp Version: 1.2.1-2~bpo9+1 Severity: grave Justification: renders package unusable Dear Maintainer, when trying to install gajim-pgp from stretch-backports I get the following: $ apt install -t stretch-backports gajim-pgp Reading package lists... Done Building dependency tree

Processed: Re: pulseaudio creates .config/pulse in a root directory

Processing control commands: > retitle 675857 /etc/init.d/alsa-utils creates /.config/pulse under sysvinit Bug #675857 [alsa-utils] PulseAudio-related hidden config files & folders created in the root directory Bug #684691 [alsa-utils] PulseAudio-related hidden config files & folders created in

Bug#675857: pulseaudio creates .config/pulse in a root directory

Control: retitle 675857 /etc/init.d/alsa-utils creates /.config/pulse under sysvinit Forwarding the text of Daniel Reichelt's message reopening RC bug #675857 (and its merged duplicates) to the bug, so that it's visible to the alsa-utils maintainers and on the BTS without rummaging in "Show full

Processed: [/master] Add patch to trap build errors (Closing: #883526)

Processing commands for cont...@bugs.debian.org: > tag 883526 pending Bug #883526 [src:geeqie] geeqie build does not trap errors from make Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 883526:

Bug#883526: [/master] Add patch to trap build errors (Closing: #883526)

tag 883526 pending thanks Date: Sat Jan 6 16:39:40 2018 +0100 Author: Andreas Rönnquist Commit ID: a5deff32b120953ebd62431c1e75a641c2180974 Commit URL: https://anonscm.debian.org/cgit/collab-maint/geeqie.git;a=commitdiff;h=a5deff32b120953ebd62431c1e75a641c2180974 Patch

Bug#866417: bkchem is marked for autoremoval from testing

Hi again, I'd volunteer to fix this provided you give confirmation that I can convert the packaging to Git. (I'm wondering whether you keep your optimism that SVN will have continued support since I never read about this in the last weeks). Kind regards Andreas. PS: I'll assume

Bug#859263: maintain PIE enabled bash

On Sat, 01 Apr 2017 at 14:31:48 +0200, cgzones wrote: > Due to #842037, bash is currently shipped without PIE[1] support. > Please consider adding a package bash-pie, which Conflicts and > Provides bash, or upload a PIE-enabled version to stretch-backports > after release. On Sat, 05 Aug 2017 at

Bug#886485: linux-image-4.9.0-5-686-pae: Hangs on boot at ".... node #0, CPUs: #1"

>> Try also booting without 'quiet' and with 'debug earlyprintk'. > > Happy to try, but not sure how to do that Worked out how to do it... Edited /etc/default/grub removed "quiet" and added "earlyprintk=vga debug" to GRUB_CMDLINE_LINUX_DEFAULT and ran update-grub. The bad news is that it hangs

Bug#866480: Bug was closed in 0.13.1-1

Control: fixed -1 0.13.1-2 On Sun, Jan 07, 2018 at 08:16:25AM +0100, Andreas Tille wrote: > This bug was closed in the upload of 0.13.1-1 - no idea why it was not closed. Actually, it was fixed in the -2 upload. Yaroslav in his 0.13.1-1 upload overwrote the previous NMUs/Team uploads as he

Bug#869598: marked as done (libid3tag FTBFS: error: conflicting types for 'id3_frametype_lookup')

Your message dated Sun, 07 Jan 2018 13:19:30 + with message-id and subject line Bug#869598: fixed in libid3tag 0.15.1b-13 has caused the Debian Bug report #869598, regarding libid3tag FTBFS: error: conflicting types for 'id3_frametype_lookup' to be marked

Processed: Bug#866468 marked as pending

Processing commands for cont...@bugs.debian.org: > tag 866468 pending Bug #866468 [src:python-scipy] python-scipy: depends on obsolete python-imaging (replace with python3-pil or python-pil) Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. --

Bug#866468: marked as pending

tag 866468 pending thanks Hello, Bug #866468 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/python-scipy.git/commit/?id=53cbd58 --- commit

Bug#866460: marked as done (pyfai: depends on obsolete python-imaging (replace with python3-pil or python-pil))

Your message dated Sun, 7 Jan 2018 09:03:05 +0100 with message-id <20180107080305.4vvxmp37t6nz4...@an3as.eu> and subject line python-imaging was droped in upload of 0.14.2+dfsg-1 has caused the Debian Bug report #866460, regarding pyfai: depends on obsolete python-imaging (replace with python3-pil

Bug#866480: marked as done (skimage: depends on obsolete python-imaging (replace with python3-pil or python-pil))

Your message dated Sun, 7 Jan 2018 08:16:25 +0100 with message-id <20180107071625.h4gexnhon5ice...@an3as.eu> and subject line Bug was closed in 0.13.1-1 has caused the Debian Bug report #866480, regarding skimage: depends on obsolete python-imaging (replace with python3-pil or python-pil) to be

Bug#866482: marked as done (stepic: depends on obsolete python-imaging (replace with python3-pil or python-pil))

Your message dated Sun, 07 Jan 2018 10:01:54 + with message-id and subject line Bug#866482: fixed in stepic 0.3-6 has caused the Debian Bug report #866482, regarding stepic: depends on obsolete python-imaging (replace with python3-pil or python-pil) to be

Bug#886532: Coming updates for meltdown/spectre

Package: qemu Severity: grave Is it going to be possible to include this patch in qemu please? https://lists.nongnu.org/archive/html/qemu-devel/2018-01/msg00811.html ref: https://www.qemu.org/2018/01/04/spectre/ -N

Bug#880554: xen domu freezes with kernel linux-image-4.9.0-4-amd64

On Sat, Jan 06, 2018 at 11:17:00PM +0100, Hans van Kranenburg wrote: > I agree that the upstream default, 32 is quite low. This is indeed a > configuration issue. I myself ran into this years ago with a growing > number of domUs and network interfaces in use. We have been using >

Bug#886417: linux-source-4.9: Kernel sources do not compile

On Sat, 2018-01-06 at 00:12 +0100, Salvatore Bonaccorso wrote: > There is indeed > https://git.kernel.org/linus/ce4a4e565f5264909a18c733b864c3f74467f69e > backported as 3e5daacf65173987436bad6ab9039a05f9545cdd in v4.9.74 > which AFAICS did remove the surrounding directives. Thanks for the

Bug#790204: marked as done (gnucash: depends on libwebkitgtk-1.0-0 which is deprecated)

Your message dated Sun, 07 Jan 2018 12:50:35 + with message-id and subject line Bug#790204: fixed in gnucash 1:2.7.3-1 has caused the Debian Bug report #790204, regarding gnucash: depends on libwebkitgtk-1.0-0 which is deprecated to be marked as done.

Bug#884669: marked as done (2to3 binary moved to it's own 2to3 package)

Your message dated Sun, 7 Jan 2018 14:10:37 +0100 with message-id <8f4a6471-5063-1bc2-dea7-915bd3384...@googlemail.com> and subject line Re: Bug#884669: 2to3 binary moved to it's own 2to3 package has caused the Debian Bug report #884669, regarding 2to3 binary moved to it's own 2to3 package to be

Bug#866474: marked as done (qreator: depends on obsolete python-imaging (replace with python3-pil or python-pil))

Your message dated Sun, 07 Jan 2018 19:41:22 + with message-id and subject line Bug#866474: fixed in qreator 16.06.1-2 has caused the Debian Bug report #866474, regarding qreator: depends on obsolete python-imaging (replace with python3-pil or python-pil)

Bug#886494: polymake: Can't locate loadable object for module Polymake::Ext in @INC

Thanks for your reply, Benjamin! I'm copying p...@packages.debian.org again and looking for input from my comaintainer Dominic. See below. On Sat, Jan 06, 2018 at 10:07:47PM +0100, Benjamin Lorenz wrote: > On 01/06/2018 08:08 PM, Niko Tyni wrote: > > Running polymake currently fails with > > > >

Bug#866477: python-imaging package will be dropped

See also https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876681 (upstream is not completely dead and one day may end up doing a more modern release, but if there are no pressing needs for this old version to remain in testing / next stable I'll just let it be autoremoved while waiting for

Bug#886572: texstudio FTBFS: does not find quazip

Source: texstudio Version: 2.12.6+debian-1 Severity: serious User: helm...@debian.org Usertags: rebootstrap texstudio fails to build from source, because it does not find quazip. Tail of a build log: | g++ -c -pipe -std=c++0x -g -O2 -fdebug-prefix-map=/<>/texstudio-2.12.6+debian=.

Bug#886581: do not transition; errors in the dependency chain

Package: certbot Version: 0.20.0-1 Severity: grave A placeholder to ensure that the new version doesn't transition out of unstable due to dependency problems. -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64)

Bug#884116: linux-image-4.9.0-4-amd64: screen atrifacts then crash

Further adventures. From https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884116#45 : > I am using Kde with a theme that relies heavily on transparency and I guess > this > makes things worse > [...] Enabling > a theme with less transparency effects makes the system work longer before >

Bug#884242: gdb-mingw-w64: diff for NMU version 10.4+nmu1

Hi Adrian, On Sun, 7 Jan 2018 00:10:41 +0200, Adrian Bunk wrote: > I've prepared an NMU for gdb-mingw-w64 (versioned as 10.4+nmu1) and > uploaded it to DELAYED/5. Please feel free to tell me if I should > cancel it. Thanks for taking care of this — I see you didn’t use the

Bug#884242: gdb-mingw-w64: diff for NMU version 10.4+nmu1

On Sun, Jan 07, 2018 at 05:34:15PM +0100, Stephen Kitt wrote: >... > I’ve pushed 10.5 to the archive, if that goes through, please cancel your > NMU. Thanks, cancelled. > Regards, > > Stephen cu Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly out of the

Bug#885929: marked as done (git-buildpackage: gbp pq import fails on non UTF-8 chars in patch)

Your message dated Sun, 07 Jan 2018 19:19:50 + with message-id and subject line Bug#885929: fixed in git-buildpackage 0.9.6 has caused the Debian Bug report #885929, regarding git-buildpackage: gbp pq import fails on non UTF-8 chars in patch to be marked

Bug#866430: marked as done (guiqwt: depends on obsolete python-imaging (replace with python3-pil or python-pil))

Your message dated Sun, 07 Jan 2018 15:39:52 + with message-id and subject line Bug#866430: fixed in guiqwt 3.0.3-2 has caused the Debian Bug report #866430, regarding guiqwt: depends on obsolete python-imaging (replace with python3-pil or python-pil) to

Bug#866435: I'd volunteer to fix this bug and would move the packaging to Git

On Sunday, January 7, 2018 1:37:36 AM CST Andreas Tille wrote: > Hi Steve, > > it seems this package is not yet in Git. I'd volunteer to move it > to Git and fix the bug. Is this OK for you? That would be awesome. Please do so! Thanks, -Steve signature.asc Description: This is a digitally

Bug#886558: audex: build-depends on cruft packages libkcddb-dev and libkcompactdisc-dev

Package: audex Severity: serious Tags: buster,sid audex build-depends on libkcddb-dev and libkcompactdisc-dev which are no longer built by the libkcddb and libkcompactdisc source packages. It seems that both of those source packages are now only building qt5 versions of their libraries. So if

Bug#866477: python-imaging package will be dropped

On Sun, 7 Jan 2018 16:24:41 +0100 Elena ``of Valhalla'' wrote: > See also > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876681 > > (upstream is not completely dead and one day may end up doing a more > modern release, but if there are no pressing needs for this

Bug#866468: marked as done (python-scipy: depends on obsolete python-imaging (replace with python3-pil or python-pil))

Your message dated Sun, 07 Jan 2018 16:39:11 + with message-id and subject line Bug#866468: fixed in python-scipy 0.19.1-2 has caused the Debian Bug report #866468, regarding python-scipy: depends on obsolete python-imaging (replace with python3-pil or

Bug#884242: marked as done (gdb-mingw-w64 FTBFS with g++-mingw-w64 7.2.0-16+20)

Your message dated Sun, 07 Jan 2018 16:49:46 + with message-id and subject line Bug#884242: fixed in gdb-mingw-w64 10.5 has caused the Debian Bug report #884242, regarding gdb-mingw-w64 FTBFS with g++-mingw-w64 7.2.0-16+20 to be marked as done. This means

Bug#885955: FTBFS: /usr/bin/ld: cannot find -ljvm

package src:jcc tags 885955 + confirmed pending thanks On Sun, Dec 31, 2017 at 3:06 PM Adam Borowski wrote: > I'm afraid that your package fails to build on armhf, with: > /usr/bin/ld: cannot find -ljvm > > It does succeed on at least amd64, though. > For some reason

Processed: Re: Bug#885955: FTBFS: /usr/bin/ld: cannot find -ljvm

Processing commands for cont...@bugs.debian.org: > package src:jcc Limiting to bugs with field 'package' containing at least one of 'src:jcc' Limit currently set to 'package':'src:jcc' > tags 885955 + confirmed pending Bug #885955 [src:jcc] FTBFS: /usr/bin/ld: cannot find -ljvm Added tag(s)

Bug#880554: xen domu freezes with kernel linux-image-4.9.0-4-amd64

On 01/07/2018 10:05 AM, Valentin Vidic wrote: > On Sat, Jan 06, 2018 at 11:17:00PM +0100, Hans van Kranenburg wrote: >> I agree that the upstream default, 32 is quite low. This is indeed a >> configuration issue. I myself ran into this years ago with a growing >> number of domUs and network

Bug#883466: marked as done (singularity-container: FTBFS on mips*)

Your message dated Sun, 07 Jan 2018 20:57:42 + with message-id and subject line Bug#883466: fixed in singularity-container 2.4.2-2 has caused the Debian Bug report #883466, regarding singularity-container: FTBFS on mips* to be marked as done. This means

Processed: Re: Bug#886591: 4.9.0-5 (after kaiser patch) breaks xen pvh

Processing commands for cont...@bugs.debian.org: > # ok, let's try again... > severity 886591 important Bug #886591 [linux-image-4.9.0-5-amd64] 4.9.0-5 (after kaiser patch) breaks xen pvh Severity set to 'important' from 'grave' > reassign 886591 src:linux 4.9.65-3+deb9u2 Bug #886591

Processed: Bug#882178 marked as pending

Processing commands for cont...@bugs.debian.org: > tag 882178 pending Bug #882178 [src:sonic-visualiser] sonic-visualiser ftbfs on arm64 and s390x (test failure) Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 882178:

Bug#886591: 4.9.0-5 (after kaiser patch) breaks xen pvh

Package: linux-image-4.9.0-5-amd64 Version: 4.9.65-3+deb9u2 Severity: grave I've updated kernel to new version in stretch linux-image-4.9.0-5-amd64 (4.9.65-3+deb9u2) and pvh-enabled xen domain are refusing to start. Nothing useful in the log, it just says the domain crashes Waiting for domain

Processed (with 1 error): merge xen pvh breakage

Processing commands for cont...@bugs.debian.org: > merge 886591 886491 Bug #886591 [linux-image-4.9.0-5-amd64] 4.9.0-5 (after kaiser patch) breaks xen pvh Unable to merge bugs because: severity of #886491 is 'important' not 'grave' package of #886491 is 'src:linux' not

Bug#886539: gajim-pgp (1.2.1-2~bpo9+1) depends on python3-gnupg (>= 0.4.1), that is not available

Hi Patrik, thanks for your bug report. The issue is known to the python-gnupg maintainer, they just needs more time to prepare the package than they hoped. I assume, we don't need to wait long! Cheers

Bug#882178: marked as pending

tag 882178 pending thanks Hello, Bug #882178 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/sonic-visualiser.git/commit/?id=c758347 --- commit

Processed: Remove pending

Processing commands for cont...@bugs.debian.org: > tags 883526 - pending Bug #883526 [src:geeqie] geeqie build does not trap errors from make Removed tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 883526:

Processed: Bug#881301 marked as pending

Processing commands for cont...@bugs.debian.org: > tag 881301 pending Bug #881301 [gnome-shell] gnome-shell: intermittent "invalid unclassed pointer in cast to 'ClutterText'" + segfault Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. --

Bug#881301: marked as pending

tag 881301 pending thanks Hello, Bug #881301 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-gnome/gnome-shell.git/commit/?id=63df168 --- commit

Bug#882178: marked as done (sonic-visualiser ftbfs on arm64 and s390x (test failure))

Your message dated Sun, 07 Jan 2018 23:34:57 + with message-id and subject line Bug#882178: fixed in sonic-visualiser 3.0.3-2 has caused the Debian Bug report #882178, regarding sonic-visualiser ftbfs on arm64 and s390x (test failure) to be marked as done.

Bug#886604: FTBFS: race condition running tests 7 and 10 in parallel

Source: gambc Version: 4.8.8-2 Severity: serious Tags: upstream Justification: fails to build from source (but built successfully in the past) The latest build of gambc for hppa failed due to a race between parallel runs of tests 7 and 10: TEST 7 (memory management and

Bug#866417: marked as done (bkchem: depends on obsolete python-imaging (replace with python3-pil or python-pil))

Your message dated Mon, 08 Jan 2018 06:19:02 + with message-id and subject line Bug#866417: fixed in bkchem 0.13.0-6 has caused the Debian Bug report #866417, regarding bkchem: depends on obsolete python-imaging (replace with python3-pil or python-pil) to

Processed: Re: cyphesis-cpp: ftbfs with GCC-7

Processing control commands: > tags -1 + pending Bug #853363 [src:cyphesis-cpp] cyphesis-cpp: ftbfs with GCC-7 Added tag(s) pending. -- 853363: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853363 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#853363: cyphesis-cpp: ftbfs with GCC-7

Control: tags -1 + pending On Sat, 2 Dec 2017 11:36:12 +0200 Juhani Numminen wrote: > I believe I found how upstream actually fixed the bug, plase see > missing-include.patch. It is based on: >

Bug#866417: [Debichem-devel] Bug#866417: bkchem is marked for autoremoval from testing

Hi Andreas, On Sunday, 7 January 2018 15:46:05 AEDT Andreas Tille wrote: > Hi again, > > I'd volunteer to fix this provided you give confirmation that I can convert > the packaging to Git. (I'm wondering whether you keep your optimism that > SVN will have continued support since I never read

Bug#886330: marked as done (sleepyhead: FTBFS: UpdaterWindow.cpp:26:10: fatal error: quazip/quazip.h: No such file or directory)

Your message dated Mon, 08 Jan 2018 06:49:15 + with message-id and subject line Bug#886330: fixed in sleepyhead 1.0.0-beta-2+dfsg-4 has caused the Debian Bug report #886330, regarding sleepyhead: FTBFS: UpdaterWindow.cpp:26:10: fatal error: