Bug#919256: dnssec-trigger: Failed to upgrade: installed dnssec-trigger package post-installation script subprocess returned error exit status 1

On Wed, 2019-01-16 at 08:55 +0100, Axel Beckert wrote: > > > # summary of how this script can be called: > #* `configure' > [...] > case "$1" in > configure) > # configure the control channel if run for the first time > if [ -z "$2" ]; then > dnssec-trigg

Processed: Re: julia: baseline violation on armhf

Processing control commands: > severity -1 important Bug #919183 [src:julia] julia: baseline violation on armhf Severity set to 'important' from 'serious' -- 919183: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919183 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#919183: julia: baseline violation on armhf

control: severity -1 important This is not baseline violation. julia -C "armv7-a;armv7-a,neon;armv7-a,neon,vfp4" compiles 3 branches of code, and the optimal branch will be selected during runtime. The SIGILL raised during build on the buildd stems from LLVM's incorrect CPU detection. Here is

Bug#919500: golang-github-grpc-ecosystem-grpc-gateway: build dependency on golang-google-genproto-dev must be bumped to (>= 0.0~git20190111.db91494)

  Dear Go team, I pushed a fix on Salsa, can you please review and upload these changes? Thanks! Regards,   Arnaud

Bug#910295: dput FTBFS: tests fail: socket.gaierror: [Errno -2] Name or service not known

Control: tags -1 + confirmed On 04-Oct-2018, Helmut Grohne wrote: > At least the vast majority of failures is due to a similar > socket.gaierror. I confirm that this behaviour is reproducible in a new SBuild chroot, created with ‘sbuild-debian-developer-setup’ (version “0.78.0-2”). The behavi

Processed: Re: Bug#910295: dput FTBFS: tests fail: socket.gaierror: [Errno -2] Name or service not known

Processing control commands: > tags -1 + confirmed Bug #910295 [src:dput] dput FTBFS: tests fail: socket.gaierror: [Errno -2] Name or service not known Added tag(s) confirmed. -- 910295: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910295 Debian Bug Tracking System Contact ow...@bugs.debia

Bug#912633: Possible conflict betwwen courier-imap and courier-imap-ssl?

Hi all, I have just run into this same issue and its a bit of a pain. One thing I notivce however is that I have: # dpkg -l | grep courier-imap ii courier-imap 5.0.5+1.0.5-1 amd64 Courier mail server - IMAP server ii courier-imap-ssl 4.18.1+0.78.0-2 all Courier mail

Bug#918391: marked as done (ruby-spring FTBFS with rails 5.2.0)

Your message dated Thu, 17 Jan 2019 02:46:01 + with message-id and subject line Bug#918391: fixed in ruby-spring 2.0.2-1 has caused the Debian Bug report #918391, regarding ruby-spring FTBFS with rails 5.2.0 to be marked as done. This means that you claim that the problem has been dealt with.

Bug#919523: marked as done (libmodule-install-readmefrompod-perl: FTBFS in sid (failing tests))

Your message dated Thu, 17 Jan 2019 02:44:46 + with message-id and subject line Bug#919523: fixed in libmodule-install-readmefrompod-perl 0.30-2 has caused the Debian Bug report #919523, regarding libmodule-install-readmefrompod-perl: FTBFS in sid (failing tests) to be marked as done. This m

Bug#919523: Bug #919523 in libmodule-install-readmefrompod-perl marked as pending

Control: tag -1 pending Hello, Bug #919523 in libmodule-install-readmefrompod-perl 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: https://salsa.debian.org/perl-team/modules/packages/l

Processed: Bug #919523 in libmodule-install-readmefrompod-perl marked as pending

Processing control commands: > tag -1 pending Bug #919523 [src:libmodule-install-readmefrompod-perl] libmodule-install-readmefrompod-perl: FTBFS in sid (failing tests) Added tag(s) pending. -- 919523: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919523 Debian Bug Tracking System Contact ow

Bug#919397: marked as done (apcalc FTBFS on 32bit big endian)

Your message dated Thu, 17 Jan 2019 01:49:21 + with message-id and subject line Bug#919397: fixed in apcalc 2.12.7.2-2 has caused the Debian Bug report #919397, regarding apcalc FTBFS on 32bit big endian to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#919371: mono won't migrate to testing, still b-d on gcc-5

OK, I have a status update on this. * I can't get a minimal patch set against mono-2018-06 branch (Mono 5.16) which builds the entire release to completion on s390x on versions of gcc with PIC/PIE by default (Debian gcc-6 or later) * I picked the version I uploaded, on the basis that it is part of

Bug#919341: Bug#919458: lintian: add tag for empty executables

tags 919458 + pending thanks Hi Emilio, > Could we add a lintian tag for empty executables, particularly in PATH? Then > we > could turn that into an autoreject (after analysing the results when > lintian.debian.org is updated) and help prevent this kind of brokenness in the > future. Note that

Bug#919529: marked as done (CVE-2019-6256)

Your message dated Thu, 17 Jan 2019 00:01:38 +0100 with message-id <20190116230138.gb12...@ramacher.at> and subject line Re: Bug#919529: CVE-2019-6256 has caused the Debian Bug report #919529, regarding CVE-2019-6256 to be marked as done. This means that you claim that the problem has been dealt w

Bug#919527: [Pkg-libvirt-maintainers] Bug#919527: Missing dependency against python3-distutils

Le 16/01/19 à 23:38, Guido Günther a écrit : On Wed, Jan 16, 2019 at 11:08:21PM +0100, Laurent Bigonville wrote: Package: virtinst Version: 1:2.0.0-2 Severity: serious Hi, The regression tests are currently failing because the virtinst is missing a dependency against python3-distutils: autopk

Bug#919529: CVE-2019-6256

Control: found -1 2016.11.28-1 On 2019-01-16 23:19:45, Moritz Muehlenhoff wrote: > Source: liblivemedia > Severity: grave > Tags: security > > Please see http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-6256 > > Cheers, > Moritz Not sure if I'm missing something, but the PoC does

Processed: Re: Bug#919529: CVE-2019-6256

Processing control commands: > found -1 2016.11.28-1 Bug #919529 [src:liblivemedia] CVE-2019-6256 Marked as found in versions liblivemedia/2016.11.28-1. -- 919529: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919529 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#918627: node-cacache FTBFS with nodejs 10.15.0

Update to 11.3.2 fixes partially failing build. Last problem is in node-readable-stream

Bug#919527: [Pkg-libvirt-maintainers] Bug#919527: Missing dependency against python3-distutils

On Wed, Jan 16, 2019 at 11:08:21PM +0100, Laurent Bigonville wrote: > Package: virtinst > Version: 1:2.0.0-2 > Severity: serious > > Hi, > > The regression tests are currently failing because the virtinst is > missing a dependency against python3-distutils: > > autopkgtest [04:39:33]: test help.

Processed: please remove Depends on common-lisp-controller

Processing control commands: > block 913649 by -1 Bug #913649 [common-lisp-controller] should not ship with buster 913649 was blocked by: 911526 914700 915507 911527 914701 913649 was not blocking any bugs. Added blocking bug(s) of 913649: 919530 -- 913649: https://bugs.debian.org/cgi-bin/bugrep

Processed: tagging 919527

Processing commands for cont...@bugs.debian.org: > tags 919527 + pending Bug #919527 [virtinst] Missing dependency against python3-distutils Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 919527: https://bugs.debian.org/cgi-bin/bugreport.cgi

Bug#919530: please remove Depends on common-lisp-controller

Package: cl-awk Version: 1-4 Severity: serious Tags: patch sid buster Control: block 913649 by -1 Dear Maintainer, Please drop the Depends on common-lisp-controller. This package is obsolete, and will not ship with Buster. It has been superseded by ASDF, which is shipped by all Common Lisp implem

Bug#919529: CVE-2019-6256

Source: liblivemedia Severity: grave Tags: security Please see http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-6256 Cheers, Moritz

Bug#918567: Maintaining dlib in Debian Science team (Was: dlib: FTBFS when built with dpkg-buildpackage -A)

Hi Andreas, Sorry for the delay. Yes, I'm absoluetly fine with the maintenance between transfered to Debian science. That's were it belongs, and I do not have the time currently to properly care for the package anyway. Please proceed! Thanks! Severin On 16/01/2019 16:06, Andreas Tille wrote:

Bug#919527: Missing dependency against python3-distutils

Package: virtinst Version: 1:2.0.0-2 Severity: serious Hi, The regression tests are currently failing because the virtinst is missing a dependency against python3-distutils: autopkgtest [04:39:33]: test help.sh: - - - - - - - - - - stderr - - - - - - - - - - Traceback (most recent call last):

Processed: fixed 918628 in 2.0.0-4

Processing commands for cont...@bugs.debian.org: > fixed 918628 2.0.0-4 Bug #918628 {Done: Xavier } [src:node-stream-splicer] node-stream-splicer FTBFS with nodejs 10.15.0 Marked as fixed in versions node-stream-splicer/2.0.0-4. > thanks Stopping processing here. Please contact me if you need as

Bug#919524: node-groove: FTBFS in sid (no matching function for call to 'v8::Function::NewInstance()')

Package: src:node-groove Version: 2.5.1-1 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in sid but it failed: [...] debian/rules build-arch dh build-arch dh_update_autotools_config

Bug#919523: libmodule-install-readmefrompod-perl: FTBFS in sid (failing tests)

Package: src:libmodule-install-readmefrompod-perl Version: 0.30-1 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in sid but it failed: [...] debian/rules binary-indep dh binary-indep

Bug#918628: marked as done (node-stream-splicer FTBFS with nodejs 10.15.0)

Your message dated Wed, 16 Jan 2019 22:41:48 +0100 with message-id and subject line Already fixed has caused the Debian Bug report #918628, regarding node-stream-splicer FTBFS with nodejs 10.15.0 to be marked as done. This means that you claim that the problem has been dealt with. If this is not

Bug#916807: marked as done (haskell-mode: FTBFS with Emacs 26.1: tests fail)

Your message dated Wed, 16 Jan 2019 21:34:37 + with message-id and subject line Bug#916807: fixed in haskell-mode 16.1-6 has caused the Debian Bug report #916807, regarding haskell-mode: FTBFS with Emacs 26.1: tests fail to be marked as done. This means that you claim that the problem has bee

Bug#919192: marked as done (node-opencv: FTBFS in sid (no matching function for call to 'v8::Function::NewInstance(int, v8::Local [3])'))

Your message dated Wed, 16 Jan 2019 21:20:11 + with message-id and subject line Bug#919192: fixed in node-opencv 6.0.0+git20180416.cfc96ba0-1 has caused the Debian Bug report #919192, regarding node-opencv: FTBFS in sid (no matching function for call to 'v8::Function::NewInstance(int, v8::Loc

Bug#911878: closing 911878

close 911878 thanks Hello, The package is now building fine on all release architectures Closing

Processed: closing 911878

Processing commands for cont...@bugs.debian.org: > close 911878 Bug #911878 [src:libosinfo] libosinfo FTBFS: tests fail: ERROR:test-isodetect.c:406:test_one: assertion failed (shortid == info->shortid): ("win10" == "win8") Marked Bug as done > thanks Stopping processing here. Please contact me

Processed: Bug #919192 in node-opencv marked as pending

Processing control commands: > tag -1 pending Bug #919192 [src:node-opencv] node-opencv: FTBFS in sid (no matching function for call to 'v8::Function::NewInstance(int, v8::Local [3])') Added tag(s) pending. -- 919192: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919192 Debian Bug Tracking

Bug#919192: Bug #919192 in node-opencv marked as pending

Control: tag -1 pending Hello, Bug #919192 in node-opencv 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: https://salsa.debian.org/js-team/node-opencv/commit/1dc7bad3ac35ea9cafce6219ce1

Processed: merge 919219 and 919235

Processing commands for cont...@bugs.debian.org: > severity 919219 serious Bug #919219 [abcm2ps] abcm2ps: fails to build from scratch because debhelper detects the ninja build system Severity set to 'serious' from 'important' > merge 919219 919235 Bug #919219 [abcm2ps] abcm2ps: fails to build fro

Bug#919138: wpasupplicant: Fails to connect to some Wifi networks on version 2:2.7-3

Alright, not entirely sure if I did this right but I followed Debian's Building Tutorial to download and build wpa_supplicant with the changes you linked. One exception, I use wpa_supplicant through NetworkManager and could not work out where I needed to create a wpa_supplicant.conf, so I change

Bug#906215: marked as done (foolscap autopkgtest needs update for new version of twisted)

Your message dated Wed, 16 Jan 2019 20:48:37 + with message-id and subject line Bug#906215: fixed in foolscap 0.13.1-2 has caused the Debian Bug report #906215, regarding foolscap autopkgtest needs update for new version of twisted to be marked as done. This means that you claim that the prob

Bug#911271: marked as done (foolscap: (Build) Depends on non existing python-txtorcon)

Your message dated Wed, 16 Jan 2019 20:48:38 + with message-id and subject line Bug#911271: fixed in foolscap 0.13.1-2 has caused the Debian Bug report #911271, regarding foolscap: (Build) Depends on non existing python-txtorcon to be marked as done. This means that you claim that the problem

Bug#919516: ruby2.5 ftbfs in testing/unstable: certificate verify failed (certificate has expired)

Package: src:ruby2.5 Version: 2.5.3-3 Severity: serious Tags: sid buster [...] 13) Error: TestNetHTTPS#test_get: OpenSSL::SSL::SSLError: SSL_connect returned=1 errno=0 state=error: certificate verify failed (certificate has expired) /home/packages/tmp/ruby2.5-2.5.3/lib/net/protocol.rb:44:in

Processed: found 919513 in 1.1.2+dfsg1-6

Processing commands for cont...@bugs.debian.org: > found 919513 1.1.2+dfsg1-6 Bug #919513 [src:ntpsec] CVE-2019-6442 CVE-2019-6443 CVE-2019-6444 CVE-2019-6445 Marked as found in versions ntpsec/1.1.2+dfsg1-6. > thanks Stopping processing here. Please contact me if you need assistance. -- 919513:

Bug#917199: marked as done (pyside2 should build without patchelf also on mips+mipsel)

Your message dated Wed, 16 Jan 2019 19:34:51 + with message-id and subject line Bug#917199: fixed in pyside2 5.11.2-3 has caused the Debian Bug report #917199, regarding pyside2 should build without patchelf also on mips+mipsel to be marked as done. This means that you claim that the problem

Bug#919513: CVE-2019-6442 CVE-2019-6443 CVE-2019-6444 CVE-2019-6445

Thanks for letting me know. I was planning to package 1.1.3 in the next couple of days, but I was not aware there were CVEs fixed in this release. I will try to do a package release today. -- Richard > On Jan 16, 2019, at 13:21, Moritz Muehlenhoff wrote: > > Source: ntpsec > Severity: grave

Bug#919513: CVE-2019-6442 CVE-2019-6443 CVE-2019-6444 CVE-2019-6445

Source: ntpsec Severity: grave Tags: security Please see https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-6442 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-6443 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-6444 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-64

Bug#919213: marked as done (irqbalance: endless loop during configure, system reaches maximum of open files)

Your message dated Wed, 16 Jan 2019 20:10:53 +0100 with message-id <20190116191051.gu10...@sym.noone.org> and subject line Re: irqbalance: endless loop during configure, system reaches maximum of open files has caused the Debian Bug report #919213, regarding irqbalance: endless loop during configu

Processed: severity of 919498 is important

Processing commands for cont...@bugs.debian.org: > severity 919498 important Bug #919498 [src:linux] linux-image-4.19.0-1-amd64: Fails to boot. Inactive (initramfs) prompt.'Gave up waiting for suspend/resume device' Severity set to 'important' from 'critical' > thanks Stopping processing here. P

Bug#915025: libopenmpi-dev: fails to upgrade from 'stretch': new libopenmpi-dev package pre-installation script subprocess returned error exit status 2

On 2019-01-16 15:28, Alastair McKinstry wrote: > Matching changes should probably be made for mpich, the other mpi > alternative. Done, pushed to branch anbe/alternatives This time, not even build-tested :-) I also added the Breaks against the versions predating mpi-$MULTIARCH including the curre

Bug#918268: bugs-everywhere build depends on monotone that is currently not in buster

On Fri, Jan 04, 2019 at 10:19:17PM +0200, Adrian Bunk wrote: > Source: bugs-everywhere > Version: 1.1.1-4 > Severity: serious > Tags: ftbfs > Control: block -1 by 888612 889556 > > bugs-everywhere build depends on monotone that is currently > not in buster due to #888612 and #889556. I'm tempted

Bug#919418: kuttypy: FTBFS in sid (pyuic5: Command not found)

Dear Santiago, thank you for the bug report. I shall fix it today; besides, the author has published the first stable version yesterday, so the bug fix will come with the new release. Best regards, Georges. Santiago Vila a écrit : > Package: src:kuttypy > Version: 0.1-1 > Sever

Bug#918162: marked as done (Broken with Thunderbird 60)

Your message dated Wed, 16 Jan 2019 18:20:20 + with message-id and subject line Bug#918162: fixed in xul-ext-exteditor 1.0.3-1 has caused the Debian Bug report #918162, regarding Broken with Thunderbird 60 to be marked as done. This means that you claim that the problem has been dealt with. I

Bug#919500: golang-github-grpc-ecosystem-grpc-gateway: build dependency on golang-google-genproto-dev must be bumped to (>= 0.0~git20190111.db91494)

Source: golang-github-grpc-ecosystem-grpc-gateway Version: 1.6.4-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/package.php?p=golang-github-grpc-ecosystem-grpc-gateway ... # github.com/grpc-ecosystem/grpc-gateway/protoc-gen-grpc-gateway/descriptor src/github.com/grpc-ecosystem/g

Bug#900447: Build against freerdp2

Package: src:guacamole-server Version: 0.9.9-2 Followup-For: Bug #900447 I've asked upstream to clarify if Guacamole v 1.0.0 now supports FreeRDP v2, last update there was in September: https://issues.apache.org/jira/browse/GUAC

Bug#915025: libopenmpi-dev: fails to upgrade from 'stretch': new libopenmpi-dev package pre-installation script subprocess returned error exit status 2

On 16/01/2019 14:01, Alastair McKinstry wrote: On 16/01/2019 13:49, Andreas Beckmann wrote: On 2019-01-16 13:58, Alastair McKinstry wrote: Hi Would you happen to know syntax for piuparts to enable an upgrade test from stretch to a new (local) version? the command line for the normal stretc

Bug#919333: marked as done (schroedinger-coordgenlibs: FTBFS in sid (Can't exec "cmake": No such file or directory))

Your message dated Wed, 16 Jan 2019 17:36:45 + with message-id and subject line Bug#919333: fixed in schroedinger-coordgenlibs 1.1-2 has caused the Debian Bug report #919333, regarding schroedinger-coordgenlibs: FTBFS in sid (Can't exec "cmake": No such file or directory) to be marked as done

Bug#919498: linux-image-4.19.0-1-amd64: Fails to boot. Inactive (initramfs) prompt.'Gave up waiting for suspend/resume device'

Package: src:linux Version: 4.19.13-1 Severity: critical Justification: breaks the whole system System boots properly on kernel 4.18 but fails to boot with any versions (buster sid) of 4.19. It seems specific to this DELL computer as another laptop DELL is working properly with 4.19. i did a comp

Bug#918567: Maintaining dlib in Debian Science team (Was: dlib: FTBFS when built with dpkg-buildpackage -A)

Hi Andreas, > since #918567 is RC critical there is some urgency to get this fixed. > If I do not hear from you until Saturday I will assume you are fine > with dlib in Debian Science team maintenance. Sorry for missing your previous e-mail. Personal life is taking me away from Debian right now.

Bug#919476: swi-prolog stopped building on s390x

Hi Matthias, this bug is closed now, but I'd still like to clarify a bit on the topic. First of all, 8.0.0 release of SWI-Prolog is a new stable release. It will receive only security updates. Previous stable release, 7.6.4 (the last revision of stable branch 7.6.0), was released in Jan 2018. It

Bug#892277: marked as done (bridge-utils: hotplugging interferes with ifupdown resulting in unpredictable behavior)

Your message dated Wed, 16 Jan 2019 15:55:57 + with message-id and subject line Bug#892277: fixed in bridge-utils 1.6-1 has caused the Debian Bug report #892277, regarding bridge-utils: hotplugging interferes with ifupdown resulting in unpredictable behavior to be marked as done. This means

Bug#892784: Works

Hi Ivo, After rescheduling the build, it looks like it worked there. Cheers, Thomas Goirand (zigo)

Bug#918567: Maintaining dlib in Debian Science team (Was: dlib: FTBFS when built with dpkg-buildpackage -A)

Hi again, since #918567 is RC critical there is some urgency to get this fixed. If I do not hear from you until Saturday I will assume you are fine with dlib in Debian Science team maintenance. Kind regards Andreas. On Tue, Jan 15, 2019 at 11:36:14AM +0100, Andreas Tille wrote: > Hi Séve

Bug#919486: Please support Debian Buster

Package: osinfo-db Version: 0.20181120-1 Severity: serious Hi, Please support debian buster before the final release is made. Kind regards, Laurent Bigonville -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable')

Processed: Re: irqbalance: endless loop during configure, system reaches maximum of open files

Processing control commands: > tag -1 + moreinfo Bug #919213 [irqbalance] irqbalance: endless loop during configure, system reaches maximum of open files Added tag(s) moreinfo. -- 919213: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919213 Debian Bug Tracking System Contact ow...@bugs.debi

Bug#919213: irqbalance: endless loop during configure, system reaches maximum of open files

Control: tag -1 + moreinfo Hi Felipe, Felipe Sateler wrote: > On Sun, 13 Jan 2019 18:10:57 +0100 Axel Beckert wrote: > > On one of my systems (not the one I'm writing the report on), a > > Raspberry Pi 2 with Debian Sid armhf and sysvinit, >

Bug#919213: irqbalance: endless loop during configure, system reaches maximum of open files

On Sun, 13 Jan 2019 18:10:57 +0100 Axel Beckert wrote: > Package: irqbalance > Version: 1.5.0-2 > Severity: serious > > On one of my systems (not the one I'm writing the report on), a > Raspberry Pi 2 with Debian Sid armhf and sysvinit, the terminal which I > ran the upgrade in, looked like this (

Bug#900447: Build against freerdp2

I've asked upstream to clarify if Guacamole v 1.0.0 now supports FreeRDP v2, last update there was in September: https://issues.apache.org/jira/browse/GUACAMOLE-249 The answer for now is "no", so I agree dropping only RDP for now would help, at least enabling publishing a new version in Debian as

Bug#915025: libopenmpi-dev: fails to upgrade from 'stretch': new libopenmpi-dev package pre-installation script subprocess returned error exit status 2

On 2019-01-16 15:28, Alastair McKinstry wrote: > Matching changes should probably be made for mpich, the other mpi > alternative. looks quite straight-forward, I'll take a look. I think both mpich,libmpich-dev and openmpi-bin,libopenmpi-dev should have versioned Breaks against each other to denot

Bug#919409: marked as done (scikit-learn: binary-any FTBFS)

Your message dated Wed, 16 Jan 2019 15:00:29 + with message-id and subject line Bug#919409: fixed in scikit-learn 0.20.1+dfsg-3 has caused the Debian Bug report #919409, regarding scikit-learn: binary-any FTBFS to be marked as done. This means that you claim that the problem has been dealt wi

Bug#906373: marked as done (lasagne: FTBFS in buster/sid (Could not import extension numpydoc))

Your message dated Wed, 16 Jan 2019 14:58:59 + with message-id and subject line Bug#906373: fixed in lasagne 0.1+git20181019.a61b76f-1 has caused the Debian Bug report #906373, regarding lasagne: FTBFS in buster/sid (Could not import extension numpydoc) to be marked as done. This means that y

Bug#918943: marked as done (waagent: FTBFS in sid (failing tests))

Your message dated Wed, 16 Jan 2019 15:01:04 + with message-id and subject line Bug#918943: fixed in waagent 2.2.34-2 has caused the Debian Bug report #918943, regarding waagent: FTBFS in sid (failing tests) to be marked as done. This means that you claim that the problem has been dealt with.

Bug#919296: git-daemon-run: fails with 'warning: git-daemon: unable to open supervise/ok: file does not exist'

control: tags -1 +confirmed [2019-01-14 19:56] Celejar > ~# dpkg-reconfigure git-daemon-run > Service git-daemon already added. > warning: git-daemon: unable to open supervise/ok: file does not exist > > > If I'm lucky then that will get it working. I'll try to reproduce it > > here and set t

Processed: Re: git-daemon-run: fails with 'warning: git-daemon: unable to open supervise/ok: file does not exist'

Processing control commands: > tags -1 +confirmed Bug #919296 [git-daemon-run] git-daemon-run: fails with 'warning: git-daemon: unable to open supervise/ok: file does not exist' Added tag(s) confirmed. -- 919296: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919296 Debian Bug Tracking Syste

Processed: severity of 864113 is serious, affects 919066

Processing commands for cont...@bugs.debian.org: > severity 864113 serious Bug #864113 [src:libgnome-keyring] libgnome-keyring: Please stop Build-Depending on libgcrypt11-dev transition package Severity set to 'serious' from 'normal' > affects 919066 + xastir Bug #919066 {Done: Dave Hibberd } [xa

Bug#915025: libopenmpi-dev: fails to upgrade from 'stretch': new libopenmpi-dev package pre-installation script subprocess returned error exit status 2

On 2019-01-16 15:01, Alastair McKinstry wrote: >> Once we have reached a clean state (with 3.1.3-10 installed), there >> should be no need to rerun the preinst cleanup operations for every >> subsequent upgrade? > > Unfortunately, experience is that we'll see people upgrading from random > old sid

Processed: Re: Bug#919461: ssreflect ftbfs in unstable

Processing control commands: > retitle 919461 ssreflect FTBFS in unstable due to missing ssrmatching Bug #919461 [src:ssreflect] ssreflect ftbfs in unstable Changed Bug title to 'ssreflect FTBFS in unstable due to missing ssrmatching' from 'ssreflect ftbfs in unstable'. > owner 919461 ! Bug #9194

Bug#919461: ssreflect ftbfs in unstable

Control: retitle 919461 ssreflect FTBFS in unstable due to missing ssrmatching Control: owner 919461 ! That’s my fault. In my most recent Coq upload, I disabled ssrmatching and a couple of other plugins due to license concerns [1]. Those have now been resolved upstream [2]. I’m going to backport t

Processed: Merge bugs

Processing commands for cont...@bugs.debian.org: > merge 919472 918563 Bug #919472 [src:camomile] camomile ftbfs on ppc64el Bug #918563 [src:camomile] camomile FTBFS on ppc64{,el}: camomilelocaledef got signal SEGV Added tag(s) buster and sid. Bug #919472 [src:camomile] camomile ftbfs on ppc64el

Bug#915025: libopenmpi-dev: fails to upgrade from 'stretch': new libopenmpi-dev package pre-installation script subprocess returned error exit status 2

On 16/01/2019 13:49, Andreas Beckmann wrote: On 2019-01-16 13:58, Alastair McKinstry wrote: Hi Would you happen to know syntax for piuparts to enable an upgrade test from stretch to a new (local) version? the command line for the normal stretch2{buster,sid} test can be derived from correspon

Bug#919472: camomile ftbfs on ppc64el

merge 918563 -1 thanks I am waiting on porter box access from DSA so that I can debug this issue. I think it is related to 918562 [1], but need to test that. [1] https://bugs.debian.org/918562 Cheers Kyle

Processed: Re: Bug#919462: coq ftbfs on some release architectures

Processing control commands: > retitle 919462 coq FTBFS on architectures without native OCaml backends Bug #919462 [src:coq] coq ftbfs on some release architectures Changed Bug title to 'coq FTBFS on architectures without native OCaml backends' from 'coq ftbfs on some release architectures'. > ow

Bug#919476: marked as done (swi-prolog stopped building on s390x)

Your message dated Wed, 16 Jan 2019 15:58:08 +0200 with message-id <20190116135808.GA13395@localhost> and subject line Re: Bug#919476: swi-prolog stopped building on s390x has caused the Debian Bug report #919476, regarding swi-prolog stopped building on s390x to be marked as done. This means that

Processed: your mail

Processing commands for cont...@bugs.debian.org: > Found 914517 linux-image-4.19.0-1-amd64-unsigned Bug #914517 [src:linux] linux-image-4.9.0-7-amd64: Boot fails unless nomodeset is set The source 'linux' and version 'linux-image-4.19.0-1-amd64-unsigned' do not appear to match any binary package

Bug#919462: coq ftbfs on some release architectures

Control: retitle 919462 coq FTBFS on architectures without native OCaml backends Control: owner 919462 ! Coq actually does build, but the test suite fails because I messed up plugin loading on architectures that don’t have ocamlopt. Upstream handles both native and bytecode worlds by installing th

Processed: affects 918380

Processing commands for cont...@bugs.debian.org: > affects 918380 src:libweb-api-perl Bug #918380 [src:libmail-chimp3-perl] FTBFS: test failures with new Web::API Added indication that 918380 affects src:libweb-api-perl > thanks Stopping processing here. Please contact me if you need assistance.

Bug#919481: guile-2.0 ftbfs on ppc64el

Package: src:guile-2.0 Version: 2.0.13+1-5 Severity: serious Tags: sid buster guile-2.0 ftbfs on ppc64el (checked on plummer): [...] Running bytevectors.test FAIL: bytevectors.test: 2.8 Operations on IEEE-754 Representations: bytevector-ieee-single-{ref,set!} [unaligned] (compile) [...] Running i

Bug#918974: marked as done (fuse-zip ftbfs on mipsel, and unbuildable on armel)

Your message dated Wed, 16 Jan 2019 12:49:12 + with message-id and subject line Bug#918974: fixed in fuse-zip 0.5.0-1 has caused the Debian Bug report #918974, regarding fuse-zip ftbfs on mipsel, and unbuildable on armel to be marked as done. This means that you claim that the problem has bee

Bug#919470: argonaut: Non-working maintainer address

Hi Scott, On Mi 16 Jan 2019 12:47:47 CET, Scott Kitterman wrote: Package: argonaut Version: 1.2-2 Severity: serious Justification: Policy 3.3 This message was created automatically by mail delivery software. A message that you sent could not be delivered to one or more of its recipients. Thi

Bug#910731: kaddressbook: crashes at startup

Hello Francesco, I missed that, sorry about that. On Mon, 26 Nov 2018 15:22:39 +0100 =?utf-8?Q?Francesco_Potort=C3=AC?= wrote: > >can you still observe the crash, or got it fixed by updates > >in mid October? (Like mentioned in #910581) > > It does not crash any more, ... So the initial issue

Bug#919477: acl2 ftbfs on armel, armhf, arm64 and ppc64el

Package: src:acl2 Version: 8.0dfsg-1 Severity: serious Tags: sid buster acl2 ftbfs on armel, armhf, arm64 and ppc64el. https://buildd.debian.org/status/fetch.php?pkg=acl2&arch=armel&ver=8.0dfsg-1&stamp=1515868416&raw=0 and checked that it ftbfs on plummer (ppc64el).

Bug#919476: swi-prolog stopped building on s390x

Package: src:swi-prolog Version: 8.0.0+dfsg-1 Severity: serious Tags: sid buster swi-prolog stopped building on s390x, blocking the migration to testing. Now there are a few rdeps ... is it really appropriate to do this update when Debian is frozen?

Bug#893227: libbluray FTBFS with openjdk-9

Hi Petri, I'm following up on a question that Sebatian (CC'ed) asked on the mailing list last march [1]. The issue is that Debian intends to drop openjdk-8 in favor of openjdk-11, and we as package maintainers of libbluray are asked to look into this transition. Your response back then was that th

Bug#919473: zapping: Settings schema 'net.sf.Zapping.plugins.teletext' does not contain a key named 'method'

Package: zapping Version: 0.10~cvs6-15 Severity: grave zapping doesn't start: $ zapping (zapping:3191): dbind-WARNING **: 13:01:17.865: Error retrieving accessibility bus address: org.freedesktop.DBus.Error.ServiceUnknown: The name org.a11y.Bus was not provided by any .service files (z

Bug#919472: camomile ftbfs on ppc64el

Package: src:camomile Version: 1.0.1-1 Severity: serious Tags: sid buster checked on the ppc64el porter box: [...] dh_ocamlinit -a debian/rules override_dh_auto_configure make[1]: Entering directory '/home/doko/camomile-1.0.1' ocaml configure.ml --share=/home/doko/camomile-1.0.1/debian/tmp/

Bug#919470: argonaut: Non-working maintainer address

Package: argonaut Version: 1.2-2 Severity: serious Justification: Policy 3.3 This message was created automatically by mail delivery software. A message that you sent could not be delivered to one or more of its recipients. This is a permanent error. The following address(es) failed: packa...@

Bug#918436: marked as done (node-groove: FTBFS (ld: cannot find -lnode))

Your message dated Wed, 16 Jan 2019 11:40:52 + with message-id and subject line Bug#918436: fixed in node-groove 2.5.1-1 has caused the Debian Bug report #918436, regarding node-groove: FTBFS (ld: cannot find -lnode) to be marked as done. This means that you claim that the problem has been de

Bug#919419: yatex: hangs while installing along xemacs21

hi, On Wed, Jan 16, 2019 at 4:18 AM Andreas Beckmann wrote: > during a test with piuparts I noticed your package failed to install. As > per definition of the release team this makes the package too buggy for > a release, thus the severity. > > If yatex is installed in a piuparts chroot that has

Bug#869896: marked as done (backports.ssl-match-hostname should be removed for buster)

Your message dated Wed, 16 Jan 2019 11:34:24 +0100 with message-id and subject line Let's keep the package for Buster has caused the Debian Bug report #869896, regarding backports.ssl-match-hostname should be removed for buster to be marked as done. This means that you claim that the problem has

Bug#919421: marked as done (src:g810-led: FTBFS when /usr/bin/systemd-run isn't available)

Your message dated Wed, 16 Jan 2019 12:25:32 +0200 with message-id <20190116102531.GG32397@localhost> and subject line Fixed in 0.3.1-2 has caused the Debian Bug report #919421, regarding src:g810-led: FTBFS when /usr/bin/systemd-run isn't available to be marked as done. This means that you claim

Bug#918288: marked as done (nipype build depends on python-nipy that is currently not in buster)

Your message dated Wed, 16 Jan 2019 12:15:55 +0200 with message-id <20190116101555.GF32397@localhost> and subject line python-nipy is back in buster has caused the Debian Bug report #918288, regarding nipype build depends on python-nipy that is currently not in buster to be marked as done. This me

Bug#869896: Not to be removed from buster: let's close this bug?

Hi Felipe, I really would like to have this bug fixed quickly, as we're dangerously approaching the freeze, and some of my key (OpenStack) packages are in danger here. So, Felipe, do I understand well that this bug can be closed without any further action? Or is there anything that shall be done?

  1   2   >