Processed: reassign 915023 python3-senlin-dashboard

2018-12-13 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 915023 python3-senlin-dashboard Bug #915023 [openstack-dashboard] openstack-dashboard: fails to install in buster along python3-senlin-dashboard Bug reassigned from package 'openstack-dashboard' to 'python3-senlin-dashboard'. No longer

Bug#915326: marked as done (ksh FTBFS with glibc 2.28)

2018-12-13 Thread Debian Bug Tracking System
Your message dated Fri, 14 Dec 2018 07:49:31 + with message-id and subject line Bug#915326: fixed in ksh 93u+20120801-3.4 has caused the Debian Bug report #915326, regarding ksh FTBFS with glibc 2.28 to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#916410: closed by Michael Gilbert (Re: Bug#916410: chromium: Chromium 71.0.3578.80-1 fails to build from source due to missing subdirectories in third_party)

2018-12-13 Thread nurupo
Thanks for the reply, I have identified the issue. I was trying to build it on a NTFS fs and it setup to set 0777 on all files. On Thu, Dec 13, 2018 at 11:21 PM Debian Bug Tracking System < ow...@bugs.debian.org> wrote: > This is an automatic notification regarding your Bug report > which was

Bug#915770: marked as done (lcdproc: B-D libg15-dev libg15daemon-client-dev are no longer available)

2018-12-13 Thread Debian Bug Tracking System
Your message dated Fri, 14 Dec 2018 07:34:39 + with message-id and subject line Bug#915770: fixed in lcdproc 0.5.9-3 has caused the Debian Bug report #915770, regarding lcdproc: B-D libg15-dev libg15daemon-client-dev are no longer available to be marked as done. This means that you claim

Processed: Re: Bug#916415: nocache broken with glibc 2.28: several programs just hang in call to futex(..., FUTEX_WAIT_PRIVATE, 2, NULL)

2018-12-13 Thread Debian Bug Tracking System
Processing control commands: > forwarded -1 https://github.com/Feh/nocache/issues/34 Bug #916415 [libc6,nocache] nocache broken with glibc 2.28: several programs just hang in call to futex(..., FUTEX_WAIT_PRIVATE, 2, NULL) Set Bug forwarded-to-address to

Bug#916415: nocache broken with glibc 2.28: several programs just hang in call to futex(..., FUTEX_WAIT_PRIVATE, 2, NULL)

2018-12-13 Thread Aurelien Jarno
control: forwarded -1 https://github.com/Feh/nocache/issues/34 On 2018-12-14 13:33, Paul Wise wrote: > Package: nocache/1.0-1,libc6/2.28-2 > Severity: critical > Justification: breaks unrelated software > Usertags: hang > > The upgrade from libc6 2.27-8 to 2.28-2 breaks nocache; some programs, >

Processed: Reassign to libc6/nocache

2018-12-13 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 916415 libc6, nocache Bug #916415 [nocache/1.0-1,libc6/2.28-2] nocache broken with glibc 2.28: several programs just hang in call to futex(..., FUTEX_WAIT_PRIVATE, 2, NULL) Warning: Unknown package 'nocache/1.0-1' Warning: Unknown

Bug#916375: Fwd: Bug#916375: apache2: Segmentation fault when mod_perl.so is loaded

2018-12-13 Thread Xavier
Cc: libapache2-mod-perl2 Message Subject : Bug#916375: apache2: Segmentation fault when mod_perl.so is loaded Date : Thu, 13 Dec 2018 19:09:02 + >From : h.thien To : debian-bugs-d...@lists.debian.org Cc : t...@security.debian.org, Debian Apache Maintainers Package:

Bug#916416: kazam unable to start: ValueError: Invalid section name: 'DEFAULT'

2018-12-13 Thread Jajo
Package: kazam Version: 1.4.5-2 Severity: grave Justification: renders package unusable Dear Maintainer, I'm unable to start Kazam. Here the error when I start it: /usr/bin/kazam:32: PyGIWarning: Gtk was imported without specifying a version first. Use gi.require_version('Gtk', '3.0') before

Bug#916415: nocache broken with glibc 2.28: several programs just hang in call to futex(..., FUTEX_WAIT_PRIVATE, 2, NULL)

2018-12-13 Thread Paul Wise
Package: nocache/1.0-1,libc6/2.28-2 Severity: critical Justification: breaks unrelated software Usertags: hang The upgrade from libc6 2.27-8 to 2.28-2 breaks nocache; some programs, when run under it (but not all of them), hang in a call to read/futex: # nocache sleep 1 # apt show nowcache &>

Bug#916410: marked as done (chromium: Chromium 71.0.3578.80-1 fails to build from source due to missing subdirectories in third_party)

2018-12-13 Thread Debian Bug Tracking System
Your message dated Thu, 13 Dec 2018 23:21:28 -0500 with message-id and subject line Re: Bug#916410: chromium: Chromium 71.0.3578.80-1 fails to build from source due to missing subdirectories in third_party has caused the Debian Bug report #916410, regarding chromium: Chromium 71.0.3578.80-1

Bug#916194: marked as done (lizardfs FTBFS with glibc 2.28)

2018-12-13 Thread Debian Bug Tracking System
Your message dated Fri, 14 Dec 2018 03:34:50 + with message-id and subject line Bug#916194: fixed in lizardfs 3.12.0+dfsg-3 has caused the Debian Bug report #916194, regarding lizardfs FTBFS with glibc 2.28 to be marked as done. This means that you claim that the problem has been dealt with.

Bug#916410: chromium: Chromium 71.0.3578.80-1 fails to build from source due to missing subdirectories in third_party

2018-12-13 Thread Maxim Biro
Package: chromium Version: 71.0.3578.80-1 Severity: serious Justification: fails to build from source (but built successfully in the past) Trying to build Chromium off the source package, but it fails with Chromium's builds system unable to find third_party/{libvpx,opus,freetype} and so on. Here

Processed: Bug #916194 in lizardfs marked as pending

2018-12-13 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #916194 [src:lizardfs] lizardfs FTBFS with glibc 2.28 Added tag(s) pending. -- 916194: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916194 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#916194: Bug #916194 in lizardfs marked as pending

2018-12-13 Thread Dmitry Smirnov
Control: tag -1 pending Hello, Bug #916194 in lizardfs 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#912682: e: Bug#912682: usefulness of this package?

2018-12-13 Thread gregor herrmann
On Thu, 13 Dec 2018 21:25:58 +, Dominic Hargreaves wrote: > > Ok but I don't see how this bug differs from #915550 and #915876 for both > > of which the intent seems to remove the corresponding packages. > > > > Shouldn't this package also be considered for removal? > > Perhaps. We usually

Bug#915428: marked as done (libpmount FTBFS with glibc 2.28)

2018-12-13 Thread Debian Bug Tracking System
Your message dated Fri, 14 Dec 2018 01:50:40 + with message-id and subject line Bug#915428: fixed in libpmount 0.0.18-1 has caused the Debian Bug report #915428, regarding libpmount FTBFS with glibc 2.28 to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#846667: solved?

2018-12-13 Thread gregor herrmann
On Thu, 13 Dec 2018 15:51:58 +0100, cyri...@bollu.be wrote: > I could build this package in sid with the following command: > > sbuild -j5 --no-apt-update -d unstable --no-clean-source --run-lintian > --lintian-opts='--color always --display-info --display-experimental > --profile pkg-perl'

Processed: bug 916194 is forwarded to https://github.com/lizardfs/lizardfs/issues/655

2018-12-13 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forwarded 916194 https://github.com/lizardfs/lizardfs/issues/655 Bug #916194 [src:lizardfs] lizardfs FTBFS with glibc 2.28 Set Bug forwarded-to-address to 'https://github.com/lizardfs/lizardfs/issues/655'. > thanks Stopping processing here.

Bug#916363: marked as done (tepl: FTBFS in every architecture)

2018-12-13 Thread Debian Bug Tracking System
Your message dated Fri, 14 Dec 2018 01:39:50 + with message-id and subject line Bug#916363: fixed in tepl 4.2.0-2 has caused the Debian Bug report #916363, regarding tepl: FTBFS in every architecture to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#916363: Bug #916363 in tepl marked as pending

2018-12-13 Thread Jeremy Bicha
Control: tag -1 pending Hello, Bug #916363 in tepl 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 #916363 in tepl marked as pending

2018-12-13 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #916363 [src:tepl] tepl: FTBFS in every architecture Added tag(s) pending. -- 916363: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916363 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#916349: xterm: X error (BadLength) with GNU screen

2018-12-13 Thread Thomas Dickey
- Original Message - | From: "Vincent Lefevre" | To: "Thomas Dickey" , 916349-qu...@bugs.debian.org | Cc: 916...@bugs.debian.org | Sent: Thursday, December 13, 2018 7:20:00 PM | Subject: Bug#916349: xterm: X error (BadLength) with GNU screen | Control: retitle -1 xterm: X error

Processed: Re: Bug#916349: xterm: X error (BadLength) with GNU screen

2018-12-13 Thread Debian Bug Tracking System
Processing control commands: > retitle -1 xterm: X error (BadLength) when trying to display some glyphs Bug #916349 [xterm] xterm: X error (BadLength) when trying to display some glyphs Ignoring request to change the title of bug#916349 to the same title -- 916349:

Bug#916349: xterm: X error (BadLength) with GNU screen

2018-12-13 Thread Vincent Lefevre
Control: retitle -1 xterm: X error (BadLength) when trying to display some glyphs On 2018-12-13 18:35:43 -0500, Thomas Dickey wrote: > On Thu, Dec 13, 2018 at 06:25:42PM -0500, Thomas Dickey wrote: > > On Thu, Dec 13, 2018 at 02:11:28PM +0100, Vincent Lefevre wrote: > > > Package: xterm > > >

Processed: Re: Bug#916349: xterm: X error (BadLength) with GNU screen

2018-12-13 Thread Debian Bug Tracking System
Processing control commands: > retitle -1 xterm: X error (BadLength) when trying to display some glyphs Bug #916349 [xterm] xterm: X error (BadLength) with GNU screen Changed Bug title to 'xterm: X error (BadLength) when trying to display some glyphs' from 'xterm: X error (BadLength) with GNU

Bug#916349: xterm: X error (BadLength) with GNU screen

2018-12-13 Thread Thomas Dickey
On Thu, Dec 13, 2018 at 06:35:43PM -0500, Thomas Dickey wrote: > On Thu, Dec 13, 2018 at 06:25:42PM -0500, Thomas Dickey wrote: > > On Thu, Dec 13, 2018 at 02:11:28PM +0100, Vincent Lefevre wrote: > > > Package: xterm > > > Version: 338-1 > > > Severity: grave > > make it normal (and read the

Bug#916402: mono-basic: FTBFS when built in parallel

2018-12-13 Thread Santiago Vila
Package: src:mono-basic Version: 4.0.1-2 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in buster but it failed: [...] make[4]: Entering directory '/<>/vbnc/vbnc/tests' make all-local

Bug#916349: xterm: X error (BadLength) with GNU screen

2018-12-13 Thread Thomas Dickey
On Thu, Dec 13, 2018 at 06:25:42PM -0500, Thomas Dickey wrote: > On Thu, Dec 13, 2018 at 02:11:28PM +0100, Vincent Lefevre wrote: > > Package: xterm > > Version: 338-1 > > Severity: grave make it normal (and read the guidelines...) > 1281 openat(AT_FDCWD,

Bug#916349: xterm: X error (BadLength) with GNU screen

2018-12-13 Thread Thomas Dickey
On Thu, Dec 13, 2018 at 02:11:28PM +0100, Vincent Lefevre wrote: > Package: xterm > Version: 338-1 > Severity: grave > Justification: renders package unusable > > After upgrading xterm to 338-1, I get X errors when using GNU screen: > > zira% xterm -e screen -r > /usr/bin/xterm: warning, error

Bug#908945: NMU, debdiff

2018-12-13 Thread Alf Gaida
Hi Hilko, probably wrong bug number - here is nothing to fix, only to remove. Cheers Alf On Thu, 13 Dec 2018 23:27:14 +0100 Hilko Bengen wrote: > Control: tag -1 pending > > Dear maintainer, > > I have just uploaded libfm/1.3.0.2-1.1, fixing this bug, to DELAYED/5; > the relevant patches are

Bug#916304: marked as done (oar-{node,restful-api,server,web-status}: fails to install: Error: The new file [...] does not exist!)

2018-12-13 Thread Debian Bug Tracking System
Your message dated Thu, 13 Dec 2018 23:21:49 + with message-id and subject line Bug#916304: fixed in oar 2.5.8~rc8-3 has caused the Debian Bug report #916304, regarding oar-{node,restful-api,server,web-status}: fails to install: Error: The new file [...] does not exist! to be marked as done.

Processed: NMU, debdiff

2018-12-13 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #908945 [lxqt-common] lxqt-common is deprecated and should be removed from archive after the buster release Added tag(s) pending. -- 908945: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908945 Debian Bug Tracking System Contact

Bug#908945: NMU, debdiff

2018-12-13 Thread Hilko Bengen
Control: tag -1 pending Dear maintainer, I have just uploaded libfm/1.3.0.2-1.1, fixing this bug, to DELAYED/5; the relevant patches are attached to this mail. Feel free to reschedule or cancel my upload as you see fit. BTW: You may want to check the debian branch in your Salsa repository, it

Processed: Re: Bug#907718: python-dateutil breaks python-vobject autopkgtest

2018-12-13 Thread Debian Bug Tracking System
Processing control commands: > tags -1 help Bug #907718 [src:python-dateutil] python-dateutil: RRULE UNTIL values must be specified in UTC when DTSTART is timezone-aware Added tag(s) help. -- 907718: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907718 Debian Bug Tracking System Contact

Bug#907718: python-dateutil breaks python-vobject autopkgtest

2018-12-13 Thread Jonas Smedegaard
Control: tags -1 help Quoting Guido Günther (2018-12-13 19:21:45) > On Thu, Dec 13, 2018 at 05:53:03PM +0100, Jonas Smedegaard wrote: > > @Guido, could you please have a fresh look at this bug to see if it > > can either be lowered or fully solved, now that (I believe) all > > blocking bugs are

Bug#899978: marked as done (xfce4-smartbookmark-plugin: Invalid maintainer address pkg-xfce-de...@lists.alioth.debian.org)

2018-12-13 Thread Debian Bug Tracking System
Your message dated Thu, 13 Dec 2018 22:13:01 + with message-id and subject line Bug#899978: fixed in xfce4-smartbookmark-plugin 0.5.0-1 has caused the Debian Bug report #899978, regarding xfce4-smartbookmark-plugin: Invalid maintainer address pkg-xfce-de...@lists.alioth.debian.org to be

Bug#912682: e: Bug#912682: usefulness of this package?

2018-12-13 Thread Dominic Hargreaves
On Wed, Dec 12, 2018 at 10:43:17AM +0100, Cyrille Bollu wrote: > On Tue, 11 Dec 2018 15:13:11 + Dominic Hargreaves wrote: > > On Tue, Dec 11, 2018 at 10:06:45AM +0100, Cyrille Bollu wrote: > > > From its debian/control file: > > > > > > >This module is already included as part of Perl's core

Bug#915179: marked as done (hovercraft FTBFS with Python 3.7)

2018-12-13 Thread Debian Bug Tracking System
Your message dated Thu, 13 Dec 2018 21:05:00 + with message-id and subject line Bug#915179: fixed in hovercraft 2.6-1 has caused the Debian Bug report #915179, regarding hovercraft FTBFS with Python 3.7 to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#915417: virtio-forwarder: fails to build with DPDK 18.11

2018-12-13 Thread Luca Boccassi
Control: tags -1 patch On Mon, 03 Dec 2018 17:57:48 + Luca Boccassi wrote: > Source: virtio-forwarder > Version: 1.1.99.13-1~unstable > Severity: serious > Forwarded: https://www.rsyslog.com/doc/master/rainerscript/control_st ructures.html >  > DPDK 18.11 does not ship a dpdk-dev package

Processed: Re: virtio-forwarder: fails to build with DPDK 18.11

2018-12-13 Thread Debian Bug Tracking System
Processing control commands: > tags -1 patch Bug #915417 [src:virtio-forwarder] virtio-forwarder: fails to build with DPDK 18.11 Added tag(s) patch. -- 915417: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915417 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#916231: osspd FTBFS on mips: osspd.c:769:15: error: 'IOC_IN' undeclared

2018-12-13 Thread Ralf Jung
Hi again, > I found https://patchwork.ozlabs.org/patch/740563/ via some googling. It > mentions MIPS, so it might be related? As a random guess, could you try adding #include at the top of "ossp.h" and see if that makes a difference? It seems that this now somehow triggers the logic in

Bug#916231: osspd FTBFS on mips: osspd.c:769:15: error: 'IOC_IN' undeclared

2018-12-13 Thread Ralf Jung
Hi, > While trying to cross build osspd for mips, I ran into a failure that I > could reproduce natively on minkus.d.o, but not on amd64. I suspect this > is related to glibc/2.28. A build ends with: > > | gcc -Wall -pthread -g -O2 -fdebug-prefix-map=/home/helmutg/osspd-1.3.2=. >

Bug#912133: marked as done (netkit-tftp misses the generator for configure)

2018-12-13 Thread Debian Bug Tracking System
Your message dated Thu, 13 Dec 2018 20:41:32 + with message-id and subject line Bug#912133: fixed in netkit-tftp 0.17-22 has caused the Debian Bug report #912133, regarding netkit-tftp misses the generator for configure to be marked as done. This means that you claim that the problem has

Bug#867140: cqrlog: Please migrate to openssl1.1 in Buster

2018-12-13 Thread Moritz Mühlenhoff
On Wed, Sep 05, 2018 at 07:18:08PM +0200, Petr Hlozek wrote: > Recent version (2.3.0) of CQRLOG already supports openssl1.1. New > version will be released soon. What's the status? Could 2.3.0 be uploaded to unstable? Cheers, Moritz

Bug#851085: conserver: FTBFS with openssl 1.1.0

2018-12-13 Thread Moritz Mühlenhoff
On Tue, Jun 05, 2018 at 11:12:34PM +0200, Moritz Muehlenhoff wrote: > On Sun, Jun 26, 2016 at 12:21:20PM +0200, Kurt Roeckx wrote: > > OpenSSL 1.1.0 is about to released. During a rebuild of all packages using > > OpenSSL this package fail to build. > > This has now been fixed in version 8.2.2:

Bug#896921: Upgrading salt to 2018.3.3 / tornado incompatibility

2018-12-13 Thread Benjamin Drung
Hi everyone, I was working on salt to get it in shape before Debian freezes for the buster release. The current status is: * Pushed a building python3-tornado4 version to the tornado4 branch on salsa [tornado4]. * Pushed current state of salt 2018.3.3 packaging to the wip-2018.3 branch

Processed: Re: Bug#916377: cups-browsed: segfault during upgrade

2018-12-13 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > retitle 916377 cups-browsed: segfault during upgrade and at system shutdown Bug #916377 [cups-browsed] cups-browsed: segfault during upgrade Changed Bug title to 'cups-browsed: segfault during upgrade and at system shutdown' from 'cups-browsed:

Bug#915636: marked as done (python3-virtualenv: incompatible with python3-pip 18.1 - AttributeError pip.main - please upgrade to 16.1.0)

2018-12-13 Thread Debian Bug Tracking System
Your message dated Thu, 13 Dec 2018 19:49:42 + with message-id and subject line Bug#915636: fixed in python-virtualenv 15.1.0+ds-2 has caused the Debian Bug report #915636, regarding python3-virtualenv: incompatible with python3-pip 18.1 - AttributeError pip.main - please upgrade to 16.1.0

Bug#916377: cups-browsed: segfault during upgrade

2018-12-13 Thread Thorsten Glaser
retitle 916377 cups-browsed: segfault during upgrade and at system shutdown forcemerge 916377 916149 thanks On Thu, 13 Dec 2018, Till Kamppeter wrote: > This I have already fixed upstream. It was already reported as Ah, okay. In this case, sorry about the noise. > upstream issue #79 and Debian

Bug#916377: cups-browsed: segfault during upgrade

2018-12-13 Thread Till Kamppeter
This I have already fixed upstream. It was already reported as upstream issue #79 and Debian bug #916149. Till

Bug#916266: marked as done (gringo FTBFS: symbol differences)

2018-12-13 Thread Debian Bug Tracking System
Your message dated Thu, 13 Dec 2018 19:19:24 + with message-id and subject line Bug#916266: fixed in gringo 5.3.0-5 has caused the Debian Bug report #916266, regarding gringo FTBFS: symbol differences to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#916377: cups-browsed: segfault during upgrade

2018-12-13 Thread Thorsten Glaser
Package: cups-browsed Version: 1.21.5-1 Severity: serious Justification: segfaults Setting up cups-browsed (1.21.5-1) ... Installing new version of config file /etc/cups/cups-browsed.conf ... Restarting CUPS Bonjour daemon: cups-browsed. [ 1143.414255] cups-browsed[8312]: segfault at b8 ip

Bug#916370: marked as done (diamond-aligner FTBFS without SSE2)

2018-12-13 Thread Debian Bug Tracking System
Your message dated Thu, 13 Dec 2018 19:19:16 + with message-id and subject line Bug#916370: fixed in diamond-aligner 0.9.23+dfsg-2 has caused the Debian Bug report #916370, regarding diamond-aligner FTBFS without SSE2 to be marked as done. This means that you claim that the problem has been

Bug#909767: marked as done (salmon FTBFS with spdlog 1:1.1.0-1)

2018-12-13 Thread Debian Bug Tracking System
Your message dated Thu, 13 Dec 2018 19:05:56 + with message-id and subject line Bug#909767: fixed in salmon 0.12.0+ds1-1 has caused the Debian Bug report #909767, regarding salmon FTBFS with spdlog 1:1.1.0-1 to be marked as done. This means that you claim that the problem has been dealt

Bug#916375: apache2: Segmentation fault when mod_perl.so is loaded

2018-12-13 Thread h.thien
Package: apache2 Version: 2.4.25-3+deb9u6 Severity: grave Tags: patch Justification: renders package unusable Dear Maintainer, For communication with our customers we use the OTRS Ticket System. The server was reinstalled about a year ago and worked fine until it was rebooted

Processed: your mail

2018-12-13 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 866443 + patch Bug #866443 [src:nautilus-image-manipulator] nautilus-image-manipulator: depends on obsolete python-imaging (replace with python3-pil or python-pil) Added tag(s) patch. > End of message, stopping processing here. Please

Bug#866443: Replace with python-pil

2018-12-13 Thread Bruno Kleinert
Hi, please find attached a debdiff that fixes this bug. Cheers - Bruno diff -Nru nautilus-image-manipulator-1.3/debian/changelog nautilus-image-manipulator-1.3/debian/changelog --- nautilus-image-manipulator-1.3/debian/changelog 2014-04-16 23:46:36.0 +0200 +++

Processed: your mail

2018-12-13 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 916357 grave Bug #916357 [streamtuner2] streamtuner2: Unable to install because omitted parenthesis in the print stantment under python3 Severity set to 'grave' from 'normal' > thanks Stopping processing here. Please contact me if you

Bug#907718: python-dateutil breaks python-vobject autopkgtest

2018-12-13 Thread Guido Günther
Hi, On Thu, Dec 13, 2018 at 05:53:03PM +0100, Jonas Smedegaard wrote: > Hi, > > @Guido, could you please have a fresh look at this bug to see if it can > either be lowered or fully solved, now that (I believe) all blocking > bugs are addressed? If you have some spare cycles it'd trust your

Processed: [bts-link] source package src:duperemove

2018-12-13 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:duperemove > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org

Processed: [bts-link] source package src:python-boltons

2018-12-13 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:python-boltons > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user

Processed: [bts-link] source package src:atop

2018-12-13 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:atop > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org

Processed: [bts-link] source package src:kubernetes

2018-12-13 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:kubernetes > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org

Bug#916370: diamond-aligner FTBFS without SSE2

2018-12-13 Thread Adrian Bunk
Source: diamond-aligner Version: 0.9.23+dfsg-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/package.php?p=diamond-aligner=sid ... /<>/diamond-aligner-0.9.23+dfsg/src/dp/swipe/banded_3frame_swipe.cpp: In instantiation of ‘void banded_3frame_swipe(const TranslatedSequence&,

Bug#916369: libcoq-ocaml depends and build-depends on cruft packages.

2018-12-13 Thread peter green
Package: libcoq-ocaml Version: 8.6-5 Severity: serious libcoq-ocaml depends on liblablgtksourceview2-ocaml- (where is a string that varies between different architectures) which is a virtual package provided by liblablgtksourceview2-ocaml . Similarly libcoq-ocaml-dev depends on

Bug#916008: marked as done (wmhdplop FTBFS with glibc 2.28)

2018-12-13 Thread Debian Bug Tracking System
Your message dated Thu, 13 Dec 2018 17:19:34 + with message-id and subject line Bug#916008: fixed in wmhdplop 0.9.11-1 has caused the Debian Bug report #916008, regarding wmhdplop FTBFS with glibc 2.28 to be marked as done. This means that you claim that the problem has been dealt with. If

Processed: [bts-link] source package src:ghostscript

2018-12-13 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:ghostscript > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user

Bug#915821: marked as done (Needs to be built against lxc 3.x)

2018-12-13 Thread Debian Bug Tracking System
Your message dated Thu, 13 Dec 2018 17:04:18 + with message-id and subject line Bug#915821: fixed in anbox 0.0~git20181210-1 has caused the Debian Bug report #915821, regarding Needs to be built against lxc 3.x to be marked as done. This means that you claim that the problem has been dealt

Bug#916008: wmhdplop FTBFS with glibc 2.28

2018-12-13 Thread Andreas Metzler
On 2018-12-11 "Torrance, Douglas" wrote: [...] > The new package is ready and pushed to git [1]. Andreas, are you able > to review and sponsor? [...] Uploaded. I have also tagged the upload in GIT. cu Andreas -- `What a good friend you are to him, Dr. Maturin. His other friends are so

Bug#907718: python-dateutil breaks python-vobject autopkgtest

2018-12-13 Thread Jonas Smedegaard
Hi, @Guido, could you please have a fresh look at this bug to see if it can either be lowered or fully solved, now that (I believe) all blocking bugs are addressed? - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote

Bug#916363: tepl: FTBFS in every architecture

2018-12-13 Thread Santiago Vila
Package: src:tepl Version: 4.2.0-1 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in a clean chroot and it failed: [...] debian/rules build-arch dh build-arch --with gnome

Bug#915859: marked as done (uses a fixed filename in /tmp)

2018-12-13 Thread Debian Bug Tracking System
Your message dated Thu, 13 Dec 2018 16:20:07 + with message-id and subject line Bug#915859: fixed in onionshare 1.3.2-1 has caused the Debian Bug report #915859, regarding uses a fixed filename in /tmp to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#912130: marked as done (netkit-rwho misses the generator for configure)

2018-12-13 Thread Debian Bug Tracking System
Your message dated Thu, 13 Dec 2018 16:04:26 + with message-id and subject line Bug#912130: fixed in netkit-rwho 0.17-14 has caused the Debian Bug report #912130, regarding netkit-rwho misses the generator for configure to be marked as done. This means that you claim that the problem has

Bug#916279: qemu-system-common: Overwrite /usr/share/doc-base/qemu-system-doc without declaring replacement

2018-12-13 Thread Christian Ehrhardt
> Wouldn't Replaces: qemu-system-data (<< 1:3.1+dfsg-1) be better? I am not an > expert on Debian Policy. IMHO: (<< 1:3.1+dfsg-1~) But since the fix will be part of a -2 upload eventually more likely: (<< 1:3.1+dfsg-2~)

Bug#915891: marked as done (libjlatexmath-java: missing build depedency on junit4)

2018-12-13 Thread Debian Bug Tracking System
Your message dated Thu, 13 Dec 2018 15:35:11 + with message-id and subject line Bug#915891: fixed in libjlatexmath-java 1.0.7-3 has caused the Debian Bug report #915891, regarding libjlatexmath-java: missing build depedency on junit4 to be marked as done. This means that you claim that the

Bug#914034: update on my troubleshooting

2018-12-13 Thread cyrille
I've created a libnet-ssleay-perl package from version 18.6_6 but it still hangs. If someone wants to review my work it's here: On the other hand, I hacked around in file /usr/share/perl5/LWP/Protocol/http.pm. And, things seems to be working better/ok when I move the "if (defined($wbits)

Bug#846667: solved?

2018-12-13 Thread cyrille
I could build this package in sid with the following command: sbuild -j5 --no-apt-update -d unstable --no-clean-source --run-lintian --lintian-opts='--color always --display-info --display-experimental --profile pkg-perl' --arch-all Issue solved?

Bug#916355: cython: References to non-existent members of PyThreadState in Python 3.7

2018-12-13 Thread Stephen Sinclair
Package: cython Version: 0.28.4-1 Severity: grave Tags: upstream patch Justification: renders package unusable Dear Maintainer, While building and testing an update to lasagne, I got the following error, which I have tracked down to cython. ``` E Exception: ('The following error happened while

Bug#916279: qemu-system-common: Overwrite /usr/share/doc-base/qemu-system-doc without declaring replacement

2018-12-13 Thread Witold Baryluk
Package: qemu-system-common Version: 1:3.1+dfsg-1 Followup-For: Bug #916279 Sorry, I hit the wrong button in report bug. Current state of the system. $ dpkg -l | grep qemu ii ipxe-qemu 1.0.0+git-20161027.b991c67-1 all PXE boot firmware - ROM

Bug#916349: xterm: X error (BadLength) with GNU screen

2018-12-13 Thread Vincent Lefevre
On 2018-12-13 14:51:26 +0100, Vincent Lefevre wrote: > After downgrading xterm to 337-1, then reupgrading to 338-1, I can > no longer reproduce the bug (for the moment). The error occurs again. So, it seems to occur only after some time. I don't know what triggers it. -- Vincent Lefèvre - Web:

Bug#908497: marked as done (khal FTBFS with python-dateutil 2.7.3-1)

2018-12-13 Thread Debian Bug Tracking System
Your message dated Thu, 13 Dec 2018 15:04:51 + with message-id and subject line Bug#908497: fixed in khal 1:0.9.10-0.1 has caused the Debian Bug report #908497, regarding khal FTBFS with python-dateutil 2.7.3-1 to be marked as done. This means that you claim that the problem has been dealt

Bug#908497: khal: diff for NMU version 1:0.9.10-0.1

2018-12-13 Thread Jonas Smedegaard
Control: tags 908497 + patch Control: tags 908497 + pending Dear maintainer, I've prepared an NMU for khal (versioned as 1:0.9.10-0.1) and uploaded it directly to NEW (since it affected an RC bug for some time blocking the transition of a range of other packages by now. I notice it has been

Processed: khal: diff for NMU version 1:0.9.10-0.1

2018-12-13 Thread Debian Bug Tracking System
Processing control commands: > tags 908497 + patch Bug #908497 [src:khal] khal FTBFS with python-dateutil 2.7.3-1 Added tag(s) patch. > tags 908497 + pending Bug #908497 [src:khal] khal FTBFS with python-dateutil 2.7.3-1 Added tag(s) pending. -- 908497:

Bug#916279: qemu-system-common: Overwrite /usr/share/doc-base/qemu-system-doc without declaring replacement

2018-12-13 Thread Witold Baryluk
Package: qemu-system-common Followup-For: Bug #916279 I just hit the same issue: Preparing to unpack .../000-qemu-system-common_1%3a3.1+dfsg-1_amd64.deb ... Unpacking qemu-system-common (1:3.1+dfsg-1) over (1:2.12+dfsg-3+b1) ... dpkg: error processing archive

Bug#914838: marked as done (llvm-7: llvm-config-7 emits unsupported compiler option)

2018-12-13 Thread Debian Bug Tracking System
Your message dated Thu, 13 Dec 2018 14:44:38 + with message-id and subject line Bug#914838: fixed in llvm-toolchain-7 1:7.0.1~+rc3-2 has caused the Debian Bug report #914838, regarding llvm-7: llvm-config-7 emits unsupported compiler option to be marked as done. This means that you claim

Processed: Re: Bug#916317: calamares will not start, not finding libPythonQt-Qt5 library versions expected

2018-12-13 Thread Debian Bug Tracking System
Processing control commands: > reassign -1 libpythonqt-qt5-python3-3 Bug #916317 [calamares] calamares will not start, not finding libPythonQt-Qt5 library versions expected Bug reassigned from package 'calamares' to 'libpythonqt-qt5-python3-3'. No longer marked as found in versions

Processed: tagging 916347

2018-12-13 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 916347 + sid Bug #916347 [src:epiphany-browser] epiphany-browser: Don't include in Buster Added tag(s) sid. > thanks Stopping processing here. Please contact me if you need assistance. -- 916347:

Bug#916349: xterm: X error (BadLength) with GNU screen

2018-12-13 Thread Vincent Lefevre
On 2018-12-13 14:17:48 +0100, Julien Cristau wrote: > Please share your xterm config. Here's the "appres XTerm" output: *tek4014*fontLarge: 9x15 *tek4014*font2: 8x13 *tek4014*font3: 6x13 *tek4014*fontSmall: 6x10 *MenuButton*borderWidth:0 *Scrollbar.thickness: 8

Bug#916177: marked as done (i2p: FTBFS with Jetty 9.4)

2018-12-13 Thread Debian Bug Tracking System
Your message dated Thu, 13 Dec 2018 13:50:06 + with message-id and subject line Bug#916177: fixed in i2p 0.9.37-2 has caused the Debian Bug report #916177, regarding i2p: FTBFS with Jetty 9.4 to be marked as done. This means that you claim that the problem has been dealt with. If this is not

Bug#916349: xterm: X error (BadLength) with GNU screen

2018-12-13 Thread Julien Cristau
On 12/13/18 2:11 PM, Vincent Lefevre wrote: > Package: xterm > Version: 338-1 > Severity: grave > Justification: renders package unusable > > After upgrading xterm to 338-1, I get X errors when using GNU screen: > > zira% xterm -e screen -r > /usr/bin/xterm: warning, error event received: > X

Bug#916349: xterm: X error (BadLength) with GNU screen

2018-12-13 Thread Vincent Lefevre
Package: xterm Version: 338-1 Severity: grave Justification: renders package unusable After upgrading xterm to 338-1, I get X errors when using GNU screen: zira% xterm -e screen -r /usr/bin/xterm: warning, error event received: X Error of failed request: BadLength (poly request too large or

Bug#916347: epiphany-browser: Don't include in Buster

2018-12-13 Thread Jeremy Bicha
Source: epiphany-browser Version: 3.30.2-1 Severity: serious Tags: buster X-Debbugs-CC: mcatanz...@gnome.org I was contacted today by the Epiphany upstream developer Michael Catanzaro. He requested that Debian Buster not include Epiphany. While he is ok with Epiphany being in Unstable (and

Processed: Re: Bug#915713: ghc-testsuite build depends on ghc (< 8.2.2+) but 8.4.4+dfsg1-1 is to be installed

2018-12-13 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > fixed 915713 ghc-testsuite/8.4.4-1 Bug #915713 {Done: Gianfranco Costamagna } [src:ghc-testsuite] ghc-testsuite build depends on ghc (< 8.2.2+) but 8.4.4+dfsg1-1 is to be installed Marked as fixed in versions ghc-testsuite/8.4.4-1. > thanks

Bug#916346: crrcsim build depends on libjpeg9-dev

2018-12-13 Thread Adrian Bunk
Source: crrcsim Version: 0.9.13-3 Severity: serious crrcsim build depends on libjpeg9-dev that might never be part of a stable release. Please go back to libjpeg-dev.

Processed: notfixed 915713 in 8.2.2-2

2018-12-13 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > notfixed 915713 8.2.2-2 Bug #915713 {Done: Gianfranco Costamagna } [src:ghc-testsuite] ghc-testsuite build depends on ghc (< 8.2.2+) but 8.4.4+dfsg1-1 is to be installed No longer marked as fixed in versions ghc-testsuite/8.2.2-2. > thanks

Processed: fixed tags

2018-12-13 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > fixed 915713 ghc-testsuite/8.2.2-2 Bug #915713 {Done: Gianfranco Costamagna } [src:ghc-testsuite] ghc-testsuite build depends on ghc (< 8.2.2+) but 8.4.4+dfsg1-1 is to be installed Marked as fixed in versions ghc-testsuite/8.2.2-2. > thanks

Bug#915713: marked as done (ghc-testsuite build depends on ghc (< 8.2.2+) but 8.4.4+dfsg1-1 is to be installed)

2018-12-13 Thread Debian Bug Tracking System
Your message dated Thu, 13 Dec 2018 13:11:00 +0100 with message-id <37a4e755-5924-07b2-13a7-3a59a2f45...@debian.org> and subject line Re: Bug#915713: ghc-testsuite build depends on ghc (< 8.2.2+) but 8.4.4+dfsg1-1 is to be installed has caused the Debian Bug report #915713, regarding

Bug#915692: collectd - Recommends deprecated liblvm2app

2018-12-13 Thread Luca Boccassi
control: tags -1 patch On Thu, 06 Dec 2018 06:31:18 +0100 Bastian Blank wrote: > Package: colectd > Version: 5.8.1-1 > Severity: serious >  > liblvm2app is deprecated and will be not longer shipped with Buster. > Please drop it's usage. >  > Further references are found here: >

Processed: Re: collectd - Recommends deprecated liblvm2app

2018-12-13 Thread Debian Bug Tracking System
Processing control commands: > tags -1 patch Bug #915692 [collectd] collectd - Recommends deprecated liblvm2app Added tag(s) patch. -- 915692: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915692 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

  1   2   >