Bug#917716: [pkg-go] Bug#917716: notary: FTBFS: dh_auto_test: cd _build && go test -vet=off -v -p 2 [...] returned exit code 1

On Sunday, 30 December 2018 9:08:25 AM AEDT Lucas Nussbaum wrote: > > --- FAIL: TestSetupNetListener (0.00s) > > > > require.go:794: > > Error Trace:config_test.go:61 > > Error: Received unexpected error: > >

Processed: severity of 917716 is important

Processing commands for cont...@bugs.debian.org: > severity 917716 important Bug #917716 [src:notary] notary: FTBFS: dh_auto_test: cd _build && go test -vet=off -v -p 2 [...] returned exit code 1 Severity set to 'important' from 'serious' > thanks Stopping processing here. Please contact me if y

Bug#913506: marked as done (libkiwix FTBFS with ICU 63.1)

Your message dated Fri, 11 Jan 2019 06:00:10 + with message-id and subject line Bug#913506: fixed in libkiwix 3.1.1-1 has caused the Debian Bug report #913506, regarding libkiwix FTBFS with ICU 63.1 to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#871105: Status of debian-faq

Hi Tobias, On Thu, Jan 10, 2019 at 11:18:41PM +0100, Dr. Tobias Quathamer wrote: > Am 10.01.2019 um 06:46 schrieb Joost van Baal-Ilić: > > Saw you've uploaded "byhand: 9.0" on november 17, great! Upload is now > > displayed at https://ftp-master.debian.org/new.html. > > > > I'll keep an eye on t

Processed: Re: Bug#918833 closed by Bastien Roucariès (Bug#918833: fixed in node-browserify-lite 0.5.0-3)

Processing control commands: > reopen -1 Bug #918833 {Done: Bastien Roucariès } [src:node-browserify-lite] node-browserify-lite: autopkgtest regression 'reopen' may be inappropriate when a bug has been closed with a version; all fixed versions will be cleared, and you may need to re-add them. Bug

Bug#917700: dimbl: FTBFS: build-dependency not installable: libtimbl4-dev

Hi Maarten (upstream), Is there no new upstream release expected? If so, I guess indeed it would be best to drop it from Debian. Thanks, Bye, Joost On Thu, Jan 10, 2019 at 08:35:15PM +0100, Maarten van Gompel wrote: > Hi Lucas, > > We're going to let this package get autoremoved, it's hardly

Bug#918833: closed by Bastien Roucariès (Bug#918833: fixed in node-browserify-lite 0.5.0-3)

Control: reopen -1 Autopkgtest of node-browserify-lite 0.5.0-5 still fails with: autopkgtest [22:30:54]: test command2: node test.js autopkgtest [22:30:54]: test command2: [--- extract requires tests: basic...OK multiple...OK trick...OK unescape...OK spaces...OK ignore braces.

Bug#892388: marked as done (caffe-contrib: build-depends on GCC 6)

Your message dated Fri, 11 Jan 2019 01:05:16 + with message-id and subject line Bug#892388: fixed in caffe-contrib 1.0.0+git20180821.99bd997-2 has caused the Debian Bug report #892388, regarding caffe-contrib: build-depends on GCC 6 to be marked as done. This means that you claim that the pro

Bug#907518: marked as done (openssl 1.1.1~~pre9-1 breaks connection to some wifi networks, such as eduroam)

Your message dated Fri, 11 Jan 2019 00:09:38 + with message-id and subject line Bug#907518: fixed in wpa 2:2.7-3 has caused the Debian Bug report #907518, regarding openssl 1.1.1~~pre9-1 breaks connection to some wifi networks, such as eduroam to be marked as done. This means that you claim

Bug#918154: marked as done (python-docker: missing dependency on backports.ssl_match_hostname?)

Your message dated Thu, 10 Jan 2019 23:26:23 + with message-id and subject line Bug#918154: fixed in python-docker 3.4.1-4 has caused the Debian Bug report #918154, regarding python-docker: missing dependency on backports.ssl_match_hostname? to be marked as done. This means that you claim tha

Bug#918351: marked as done (QtSpell.hpp not found - QtSpell-qt5.pc should be fixed)

Your message dated Thu, 10 Jan 2019 23:05:15 + with message-id and subject line Bug#918351: fixed in qtspell 0.8.5-1 has caused the Debian Bug report #918351, regarding QtSpell.hpp not found - QtSpell-qt5.pc should be fixed to be marked as done. This means that you claim that the problem has

Bug#916161: marked as done (mono FTBFS with glibc 2.28)

Your message dated Thu, 10 Jan 2019 23:05:11 + with message-id and subject line Bug#916161: fixed in mono 5.16.0.220+dfsg3-1 has caused the Debian Bug report #916161, regarding mono FTBFS with glibc 2.28 to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#899395: marked as done (mono: FTBFS on various architectures)

Your message dated Thu, 10 Jan 2019 23:05:10 + with message-id and subject line Bug#899395: fixed in mono 5.16.0.220+dfsg3-1 has caused the Debian Bug report #899395, regarding mono: FTBFS on various architectures to be marked as done. This means that you claim that the problem has been dealt

Bug#859224: netkit-ftp-ssl: Please migrate to openssl1.1 in Buster

Sebastian Andrzej Siewior wrote... > On 2019-01-10 20:31:10 [+0100], Moritz Mühlenhoff wrote: > > > Or should we rather remove netkit-ftp-ssl? There are TLS-capable ftp client > > alternatives in the archive still, e.g. lftp. > > I provided a patch after Mats described how bad the new openssl is.

Bug#918514: marked as done (golang-github-aead-poly1305 FTBFS: relocation target runtime.support_avx2 not defined)

Your message dated Thu, 10 Jan 2019 22:54:02 + with message-id and subject line Bug#918514: fixed in golang-github-aead-chacha20 0.0~git20180709.8b13a72-1 has caused the Debian Bug report #918514, regarding golang-github-aead-poly1305 FTBFS: relocation target runtime.support_avx2 not defined

Bug#918795: marked as done (src:sogo: FTBFS with gnustep-base/1.26: sogo-tests: NSThread.m:717: GSCurrentThread: Assertion `nil != thr && "No main thread"' failed.)

Your message dated Fri, 11 Jan 2019 00:19:02 +0200 with message-id <20190110221902.ga28...@yavor.doganov.org> and subject line Re: Bug#918795: src:sogo: FTBFS with gnustep-base/1.26: sogo-tests: NSThread.m:717: GSCurrentThread: Assertion `nil != thr && "No main thread"' failed. has caused the Deb

Processed: unarchiving 909974, reopening 909974, found 909974 in 3.4.1-4

Processing commands for cont...@bugs.debian.org: > unarchive 909974 Bug #909974 {Done: Felipe Sateler } [docker-compose] remove unneeded dependency on backports.ssl-match-hostname Unarchived Bug 909974 > reopen 909974 Bug #909974 {Done: Felipe Sateler } [docker-compose] remove unneeded dependenc

Bug#918515: marked as done (golang-github-aead-chacha20 FTBFS: relocation target runtime.support_avx not defined)

Your message dated Thu, 10 Jan 2019 23:36:45 +0100 with message-id <20190110223645.qpfm7qo5bn7nn...@fatal.se> and subject line fixed, but I typod bug number in changelog has caused the Debian Bug report #918515, regarding golang-github-aead-chacha20 FTBFS: relocation target runtime.support_avx not

Bug#918514: marked as done (golang-github-aead-poly1305 FTBFS: relocation target runtime.support_avx2 not defined)

Your message dated Thu, 10 Jan 2019 22:31:06 + with message-id and subject line Bug#918514: fixed in golang-github-aead-poly1305 0.0~git20170715.6cf43fd-2 has caused the Debian Bug report #918514, regarding golang-github-aead-poly1305 FTBFS: relocation target runtime.support_avx2 not defined

Bug#918629: fixes in dependencies....

block -1 by 918514 918515 thanks Hopefully this ftbfs should vanish with the dependencies being fixed, see: https://bugs.debian.org/cgi-bin/bugreport.cgi?archive=no&bug=918514 https://bugs.debian.org/cgi-bin/bugreport.cgi?archive=no&bug=918515 Regards, Andreas Henriksson

Bug#892331: marked as done (3depict: Please use 'pkg-config' to find FreeType 2)

Your message dated Thu, 10 Jan 2019 22:20:59 + with message-id and subject line Bug#892331: fixed in 3depict 0.0.21-1 has caused the Debian Bug report #892331, regarding 3depict: Please use 'pkg-config' to find FreeType 2 to be marked as done. This means that you claim that the problem has be

Bug#876620: marked as done (3depict: missing build dependency on rename)

Your message dated Thu, 10 Jan 2019 22:20:59 + with message-id and subject line Bug#876620: fixed in 3depict 0.0.21-1 has caused the Debian Bug report #876620, regarding 3depict: missing build dependency on rename to be marked as done. This means that you claim that the problem has been dealt

Bug#871105: Status of debian-faq

Am 10.01.2019 um 06:46 schrieb Joost van Baal-Ilić: > Saw you've uploaded "byhand: 9.0" on november 17, great! Upload is now > displayed at https://ftp-master.debian.org/new.html. > > I'll keep an eye on the progress of the NEW queue handling and plan to work on > the SGML-XML conversion. Hi Joo

Processed: fixed 916846 in 1:6.2.0~rc2-1, found 917927 in 1:6.2.0~rc2-1

Processing commands for cont...@bugs.debian.org: > fixed 916846 1:6.2.0~rc2-1 Bug #916846 [libreoffice-ogltrans] [libreoffice-ogltrans] Blank screen with OpenGL transitions There is no source info for the package 'libreoffice-ogltrans' at version '1:6.2.0~rc2-1' with architecture '' Unable to ma

Bug#918514: Bug #918514 in golang-github-aead-poly1305 marked as pending

Control: tag -1 pending Hello, Bug #918514 in golang-github-aead-poly1305 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/go-team/packages/golang-github-aead-po

Processed: Bug #918514 in golang-github-aead-poly1305 marked as pending

Processing control commands: > tag -1 pending Bug #918514 [src:golang-github-aead-poly1305] golang-github-aead-poly1305 FTBFS: relocation target runtime.support_avx2 not defined Added tag(s) pending. -- 918514: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918514 Debian Bug Tracking System

Processed: tmpreaper: CVE-2019-3461

Processing control commands: > fixed -1 1.6.13+nmu1+deb9u1 Bug #918956 [src:tmpreaper] tmpreaper: CVE-2019-3461 The source 'tmpreaper' and version '1.6.13+nmu1+deb9u1' do not appear to match any binary packages Marked as fixed in versions tmpreaper/1.6.13+nmu1+deb9u1. -- 918956: https://bugs.de

Processed: patch to fix fdutils ftbfs

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

Bug#916065: patch to fix fdutils ftbfs

Control: tags -1 + patch Please see attached patch that makes sure config.h gets included before HAVE_SYS_SYSMACROS_H is checked, so that major and minor macros gets properly defined. Regards, Andreas Henriksson diff -Nru fdutils-5.5-20060227/debian/changelog fdutils-5.5-20060227/debian/changelo

Bug#918956: tmpreaper: CVE-2019-3461

Source: tmpreaper Version: 1.6.13+nmu1 Severity: grave Tags: security Control: fixed -1 1.6.13+nmu1+deb9u1 Hi, The following vulnerability was published for tmpreaper, as per DSA 4365-1. CVE-2019-3461[0]: Stephen Roettger discovered a race condition in tmpreaper, a program that cleans up files i

Bug#918422: marked as done (node-livescript FTBFS with nodejs 10.15.0)

Your message dated Thu, 10 Jan 2019 22:21:12 +0100 with message-id and subject line Re: node-livescript FTBFS with nodejs 10.15.0 has caused the Debian Bug report #918422, regarding node-livescript FTBFS with nodejs 10.15.0 to be marked as done. This means that you claim that the problem has been

Bug#895029: marked as done (node-stringprep: FTBFS with recent GCC)

Your message dated Thu, 10 Jan 2019 21:21:11 + with message-id and subject line Bug#895029: fixed in node-stringprep 0.8.0-4 has caused the Debian Bug report #895029, regarding node-stringprep: FTBFS with recent GCC to be marked as done. This means that you claim that the problem has been dea

Processed: closing 918422

Processing commands for cont...@bugs.debian.org: > close 918422 Bug #918422 [src:node-livescript] node-livescript FTBFS with nodejs 10.15.0 Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 918422: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug

Processed: Re: node-livescript FTBFS with nodejs 10.15.0

Processing control commands: > tags -1 + moreinfo Bug #918422 [src:node-livescript] node-livescript FTBFS with nodejs 10.15.0 Added tag(s) moreinfo. -- 918422: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918422 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#918422: node-livescript FTBFS with nodejs 10.15.0

Control: tags -1 + moreinfo Hello, I'm unable to reproduce this bug and https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/node-livescript.html seems clean at least since 2019-01-07 Cheers, Xavier

Bug#918629: dnscrypt-proxy FTBFS with Go 1.11

Hello, On Mon, Jan 07, 2019 at 10:34:19PM +0200, Adrian Bunk wrote: > Source: dnscrypt-proxy > Version: 2.0.19+ds1-1 > Severity: serious > Tags: ftbfs [...] > github.com/aead/chacha20/chacha.supportsAVX2: relocation target > runtime.support_avx not defined > github.com/aead/chacha20/chacha.suppor

Processed: severity of 918769 is important

Processing commands for cont...@bugs.debian.org: > severity 918769 important Bug #918769 [src:ocaml-migrate-parsetree] ocaml-migrate-parsetree FTBFS:dh_install fails Severity set to 'important' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 918769

Bug#917303: Request for help with MariaDB 10.3 / libdbd-mysql-perl packaging

Hi Otto, On Tue, 8 Jan 2019 21:40:54 +0100 =?UTF-8?B?T3R0byBLZWvDpGzDpGluZW4=?= wrote: > I will now import MariaDB 10.3.12 into > https://salsa.debian.org/mariadb-team/mariadb-10.3 but postpone uploading > it for now in case the issues above might produce something that we can > backport and patc

Bug#918931: fasm: FTBFS because it build-depends on itself and the current version lacks /usr/bin/fasm

tags 918931 + patch thanks Hi. This is a hack but I think it should work. (Rebootstrapping anything is always hacky after all). The hack may be dropped once we have a working fasm package again. --- a/debian/control +++ b/debian/control @@ -3,7 +3,7 @@ Maintainer: Tomasz Buchert Section: devel

Processed: Re: Bug#918931: fasm: FTBFS because it build-depends on itself and the current version lacks /usr/bin/fasm

Processing commands for cont...@bugs.debian.org: > tags 918931 + patch Bug #918931 [src:fasm] fasm: FTBFS because it build-depends on itself and the current version lacks /usr/bin/fasm Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 918931: ht

Bug#918633: marked as done (why3-coq: package should Depend on a specific Coq version)

Your message dated Thu, 10 Jan 2019 20:50:11 + with message-id and subject line Bug#918633: fixed in why3 1.1.1-2 has caused the Debian Bug report #918633, regarding why3-coq: package should Depend on a specific Coq version to be marked as done. This means that you claim that the problem has

Bug#918952: wolfssl: CVE-2018-16870

Source: wolfssl Version: 3.15.3+dfsg-2 Severity: grave Tags: patch security upstream Forwarded: https://github.com/wolfSSL/wolfssl/pull/1950 Hi, The following vulnerability was published for wolfssl. CVE-2018-16870[0]: | It was found that wolfssl before 3.15.7 is vulnerable to a new variant | of

Bug#918090: marked as done (theano: C-optimized ops fail with "module 'numpy.core.multiarray' has no attribute '_get_ndarray_c_version'")

Your message dated Thu, 10 Jan 2019 20:44:57 + with message-id and subject line Bug#918090: fixed in theano 1.0.3+dfsg-1 has caused the Debian Bug report #918090, regarding theano: C-optimized ops fail with "module 'numpy.core.multiarray' has no attribute '_get_ndarray_c_version'" to be marke

Processed: Bug #895029 in node-stringprep marked as pending

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

Bug#918217: marked as done (theano: autopkgtest fails with python-numpy (1:1.16.0~rc1-3))

Your message dated Thu, 10 Jan 2019 20:44:57 + with message-id and subject line Bug#918090: fixed in theano 1.0.3+dfsg-1 has caused the Debian Bug report #918090, regarding theano: autopkgtest fails with python-numpy (1:1.16.0~rc1-3) to be marked as done. This means that you claim that the pr

Bug#917715: marked as done (openconnect: FTBFS: dh_auto_test: make -j2 check VERBOSE=1 returned exit code 2)

Your message dated Thu, 10 Jan 2019 20:44:17 + with message-id and subject line Bug#917715: fixed in openconnect 8.01-1 has caused the Debian Bug report #917715, regarding openconnect: FTBFS: dh_auto_test: make -j2 check VERBOSE=1 returned exit code 2 to be marked as done. This means that yo

Bug#895029: Bug #895029 in node-stringprep marked as pending

Control: tag -1 pending Hello, Bug #895029 in node-stringprep 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-stringprep/commit/1a4557776b9a37f40ee

Bug#918424: marked as done (node-end-of-stream FTBFS with nodejs 10.15.0)

Your message dated Thu, 10 Jan 2019 20:43:44 + with message-id and subject line Bug#918424: fixed in node-end-of-stream 1.4.1-1 has caused the Debian Bug report #918424, regarding node-end-of-stream FTBFS with nodejs 10.15.0 to be marked as done. This means that you claim that the problem has

Bug#918916: Unicorn not reporting proper version for gemfile?

(unicorn upstream here, adding unicorn-public to Cc, for context: ) Dominik George wrote: > +--- a/unicorn.gemspec > b/unicorn.gemspec > +@@ -11,7 +11,7 @@ end.compact > + > + Gem::Specification.new do |s| > + s.name = %q{unicorn} > +- s.version = (ENV['

Bug#902760: [igraph/igraph] Testsuite fails with ARPACK 3.6 (#1107)

Hi Tamás, On Wed, Jan 02, 2019 at 07:52:39AM -0800, Tamás Nepusz wrote: > Commit 17cc5be8 seems to have solved the failing test cases in my Debian > testing VM. @tillea, please let me know if it worked or not. I applied the patch but it does not solve all issues: ... 197: Non-symmetric ARPACK s

Bug#918548: [pkg-apparmor] Bug#918548: About possibility to translate AppArmor tunables

On Mon, 07 Jan 2019, Ian Jackson wrote: > Package: apparmor > Version: 2.13.2-3 > Severity: serious > > Vincas, thanks for reporting this bug on the debian-i18n list. > I think it needs a much higher profile. > > Vincas Dargis writes ("About possibility to translate AppArmor tunables"): > > Let'

Bug#907624: Help for SIGSEGV in test suite needed when built with gcc 8.2 what works nicely with gcc 6.3

In linux.debian.devel.mentors, you wrote: hello, private reply only, ... > When I was running the code with some more debugging info activated[1] > I had pretty valid looking adresses 0x555666 (or something in that line > just remembering by heart - can activate the patch if needed). I have > no

Bug#918012: found 918012 in 1.21.0-3

On Thu, Jan 03, 2019 at 09:03:20PM +0200, Adrian Bunk wrote: > found 918012 1.21.0-3 > thanks https://packages.debian.org/unstable/docker-compose says: dep: python3-docker (>= 3.2.1) So I'd like to know how you came to the conclusion that testing/unstable is affected Regards, Andrea

Bug#914999: [libc6] Locking problems into libc6

Hello, Aurelien On 12/30/18 7:49 PM, Aurelien Jarno wrote: On 2018-12-12 17:11, Roman Savochenko wrote: On 12/4/18 1:24 PM, Roman Savochenko wrote: On 11/29/18 9:13 PM, Aurelien Jarno wrote: 1. For my program, I was needed to create extra locking about the function getaddrinfo(), but that re

Bug#859224: netkit-ftp-ssl: Please migrate to openssl1.1 in Buster

On 2019-01-10 20:31:10 [+0100], Moritz Mühlenhoff wrote: > On Thu, Dec 27, 2018 at 12:57:31PM +0100, Moritz Mühlenhoff wrote: > > On Sat, Nov 11, 2017 at 12:51:56PM +0100, Sebastian Andrzej Siewior wrote: > > > On 2017-11-11 12:37:15 [+0100], To Mats Erik Andersson wrote: > > > > So the problem was

Processed: Re: Unicorn not reporting proper version for gemfile?

Processing control commands: > severity -1 grave Bug #918916 [unicorn] Unicorn not reporting proper version for gemfile? Severity set to 'grave' from 'normal' > tag -1 + patch Bug #918916 [unicorn] Unicorn not reporting proper version for gemfile? Added tag(s) patch. -- 918916: https://bugs.debi

Bug#907624: Help for SIGSEGV in test suite needed when built with gcc 8.2 what works nicely with gcc 6.3

On 2019-01-09, Andrey Rahmatullin wrote: > As usual: reading the code, debugging, printfs. Address sanitizer and/or > valgrind may or may not help too. I just tried throwing some tools at it. Apparantly you need a three step thing to get to it. address-sanitizer. First issue. The command to cre

Bug#917700: dimbl: FTBFS: build-dependency not installable: libtimbl4-dev

Hi Lucas, We're going to let this package get autoremoved, it's hardly used anyway and not worth the effort to maintain. Regards, -- Maarten van Gompel Language Machines research group Centre for Language and Speech Technology Radboud Universiteit Nijmegen proy...@anaproy.nl https:

Bug#907624: Help for SIGSEGV in test suite needed when built with gcc 8.2 what works nicely with gcc 6.3

Hi Andreas, one thing I usually do in such cases is to rebuild the package adding "-fsanitize=address -O0" flags (optimization just to understand better what happens in the source). This switches the address sanitizer on . This can test i

Bug#859784: Bug #859784: validns: Please migrate to openssl1.1 in Buster

Hi Moritz, On Thu, Jan 10, 2019 at 08:33:05PM +0100, Moritz Mühlenhoff wrote: > On Mon, Nov 05, 2018 at 03:13:08PM +0100, Joost van Baal-Ilić wrote: > > > > FWIW, this work: > > > > > validns (0.8+git20170804-1) unstable; urgency=medium > > [..] > > > is available from > > https://non-gnu.uvt.

Bug#859784: Bug #859784: validns: Please migrate to openssl1.1 in Buster

On Mon, Nov 05, 2018 at 03:13:08PM +0100, Joost van Baal-Ilić wrote: > Hi, > > FWIW, this work: > > > validns (0.8+git20170804-1) unstable; urgency=medium [..] > is available from > https://non-gnu.uvt.nl/debian/stretch/validns/validns_0.8+git20170804-1.dsc . > I _*might*_ have time to merge th

Bug#859224: netkit-ftp-ssl: Please migrate to openssl1.1 in Buster

On Thu, Dec 27, 2018 at 12:57:31PM +0100, Moritz Mühlenhoff wrote: > On Sat, Nov 11, 2017 at 12:51:56PM +0100, Sebastian Andrzej Siewior wrote: > > On 2017-11-11 12:37:15 [+0100], To Mats Erik Andersson wrote: > > > So the problem was that you never shutdown the connection. You can blame > > > libs

Bug#918931: fasm: FTBFS because it build-depends on itself and the current version lacks /usr/bin/fasm

Hi. On a system with a working fasm, the patch below works for me. Note: Without downgrading to debhelper compat 11, it fails in this way: dh_dwz: dwz -q -- debian/fasm/usr/bin/fasm returned exit code 1 make: *** [debian/rules:7: binary] Error 1 --- a/debian/control +++ b/debian/control @@ -3,7

Bug#918935: marked as done (uglifyjs: Error: Cannot find module '../tools/exit')

Your message dated Thu, 10 Jan 2019 19:21:24 + with message-id and subject line Bug#918935: fixed in node-browserify-lite 0.5.0-5 has caused the Debian Bug report #918935, regarding uglifyjs: Error: Cannot find module '../tools/exit' to be marked as done. This means that you claim that the pr

Bug#918944: [Debian-ha-maintainers] Bug#918944: Autopkgtest failure with rails 5/rack 2

On Fri, Jan 11, 2019 at 12:32:05AM +0530, Pirate Praveen wrote: > Package: pcs > Version: 0.9.166-5 > Severity: serious > > https://ci.debian.net/packages/p/pcs/unstable/amd64 > > May be 0.10 version has a fix, it is delaying rails 5 testing > migration, so please fix it. Yep, I'm looking at 0.1

Bug#918944: Autopkgtest failure with rails 5/rack 2

Package: pcs Version: 0.9.166-5 Severity: serious https://ci.debian.net/packages/p/pcs/unstable/amd64 May be 0.10 version has a fix, it is delaying rails 5 testing migration, so please fix it. -- Sent from my Android device with K-9 Mail. Please excuse my brevity.

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

Package: src:waagent Version: 2.2.34-1 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in sid but it failed: [...] debian/rules build-indep dh build-indep --with python3,systemd --build

Bug#918935: [Pkg-javascript-devel] Bug#918935: node-browserify-lite FTBFS: Error: Cannot find module '../tools/exit'

Le 10/01/2019 à 19:34, Adrian Bunk a écrit : > Control: reassign -1 uglifyjs 3.4.9-2 > Control: retitle -1 uglifyjs: Error: Cannot find module '../tools/exit' > Control: affects -1 src:node-browserify-lite > > On Thu, Jan 10, 2019 at 08:04:46PM +0200, Adrian Bunk wrote: >> Source: node-browserify-

Bug#918935: [Pkg-javascript-devel] Bug#918935: node-browserify-lite FTBFS: Error: Cannot find module '../tools/exit'

Le 10/01/2019 à 19:41, Xavier a écrit : >> ... >> That does actually look like a bug in the new uglifyfs. >> >> cu >> Adrian > > I tried to reproduce but have different errors related to debian/examples* : debian/control should require node-pend (>= 1.2.0)

Processed: severity of 918795 is serious

Processing commands for cont...@bugs.debian.org: > severity 918795 serious Bug #918795 [src:sogo] src:sogo: FTBFS with gnustep-base/1.26: sogo-tests: NSThread.m:717: GSCurrentThread: Assertion `nil != thr && "No main thread"' failed. Severity set to 'serious' from 'important' > thanks Stopping p

Bug#918935: node-browserify-lite FTBFS: Error: Cannot find module '../tools/exit'

Control: reassign -1 uglifyjs 3.4.9-2 Control: retitle -1 uglifyjs: Error: Cannot find module '../tools/exit' Control: affects -1 src:node-browserify-lite On Thu, Jan 10, 2019 at 08:04:46PM +0200, Adrian Bunk wrote: > Source: node-browserify-lite > Version: 0.5.0-3 > Severity: serious > Tags: ftbf

Processed: Re: Bug#918935: node-browserify-lite FTBFS: Error: Cannot find module '../tools/exit'

Processing control commands: > reassign -1 uglifyjs 3.4.9-2 Bug #918935 [src:node-browserify-lite] node-browserify-lite FTBFS: Error: Cannot find module '../tools/exit' Bug reassigned from package 'src:node-browserify-lite' to 'uglifyjs'. No longer marked as found in versions node-browserify-lite

Bug#918913: nbconvert 5.4 breaks nbsphinx: fix upstream

Hello, please can you apply the patch that fixes the issue [1,2] ? [1] https://github.com/spatialaudio/nbsphinx/issues/202 [2] https://github.com/jupyter/nbconvert/pull/924 Thanks, Jerome -- Jerome BENOIT | calculus+at-rezozer^dot*net https://qa.debian.org/developer.php?login=calcu...@rezozer.n

Bug#918936: fasm: Does not trap for errors in debian/rules

Package: src:fasm Version: 1.73.06-1 Severity: serious Tags: patch Dear maintainer: Commands in a Makefile should be chained with "&&" so that the first thing which fails makes the whole process to stop. This is Policy 4.6, "error trapping in makefiles", and it's usually considered a serious iss

Bug#918935: node-browserify-lite FTBFS: Error: Cannot find module '../tools/exit'

Source: node-browserify-lite Version: 0.5.0-3 Severity: serious Tags: ftbfs https://buildd.debian.org/status/fetch.php?pkg=node-browserify-lite&arch=all&ver=0.5.0-3&stamp=1547086740&raw=0 ... debian/rules override_dh_auto_build make[1]: Entering directory '/<>' NODE_PATH=. /<>/cli.js debian/ex

Bug#918933: sbd FTBFS with pacemaker 2.0

Source: sbd Version: 1.3.1-4 Severity: serious Tags: ftbfs https://buildd.debian.org/status/package.php?p=sbd&suite=sid ... sbd-pacemaker.c: In function 'mon_timer_notify': sbd-pacemaker.c:125:18: error: implicit declaration of function 'get_cib_copy'; did you mean 'g_list_copy'? [-Werror=implic

Bug#918931: fasm: FTBFS because it build-depends on itself and the current version lacks /usr/bin/fasm

Package: src:fasm Version: 1.73.06-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 -a

Bug#893703: marked as done (sdaps depends on pdftk (likely to be removed when gcj is removed))

Your message dated Thu, 10 Jan 2019 19:53:43 +0200 with message-id <20190110175342.GD17164@localhost> and subject line pdftk is back in buster has caused the Debian Bug report #893703, regarding sdaps depends on pdftk (likely to be removed when gcj is removed) to be marked as done. This means that

Processed: [bts-link] source package src:ruby-awesome-print

Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:ruby-awesome-print > # 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.deb

Processed: [bts-link] source package libcap-ng

Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package libcap-ng > # 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 Setti

Bug#918673: marked as done (libmath-mpfr-perl FTBFS on ppc*: subnormal_doubles.t fails)

Your message dated Thu, 10 Jan 2019 17:36:03 + with message-id and subject line Bug#918673: fixed in libmath-mpfr-perl 4.06-1 has caused the Debian Bug report #918673, regarding libmath-mpfr-perl FTBFS on ppc*: subnormal_doubles.t fails to be marked as done. This means that you claim that the

Bug#906388: marked as done (nipy: FTBFS in buster/sid (failing tests))

Your message dated Thu, 10 Jan 2019 17:36:46 + with message-id and subject line Bug#906388: fixed in nipy 0.4.2-2 has caused the Debian Bug report #906388, regarding nipy: FTBFS in buster/sid (failing tests) to be marked as done. This means that you claim that the problem has been dealt with.

Bug#918742: Initialization loop/deadlock when used with jemalloc

Hi Faidon, Quoting Faidon Liambotis (2019-01-10 15:29:59) > Unfortunately, the initialization code runs regardless of whether prof was > enabled or not, and from the code it seems like this is intentional... > > See here: > https://github.com/jemalloc/jemalloc/blob/5.1.0/src/prof.c#L2392 > ...whe

Processed: nbconvert 5.4 breaks nbsphinx

Processing commands for cont...@bugs.debian.org: > retitle 918913 nbconvert 5.4 breaks nbsphinx Bug #918913 [src:nbconvert, src:nbsphinx] nbconvert breaks nbsphinx autopkgtest Changed Bug title to 'nbconvert 5.4 breaks nbsphinx' from 'nbconvert breaks nbsphinx autopkgtest'. > severity 918913 seri

Processed: reassign 902509 to src:node-send, merging 902508 902509

Processing commands for cont...@bugs.debian.org: > reassign 902509 src:node-send Bug #902509 [src:node-send] node-serve-static: FTBFS in buster/sid (TypeError: mime.lookup is not a function) Bug #902508 [src:node-send] node-send: FTBFS in buster/sid (TypeError: mime.lookup is not a function) Ign

Bug#917200: marked as done (pyside2: build-dependencies no longer satisfiable on mips64el.)

Your message dated Thu, 10 Jan 2019 14:51:16 + with message-id and subject line Bug#917200: fixed in pyside2 5.11.2-2 has caused the Debian Bug report #917200, regarding pyside2: build-dependencies no longer satisfiable on mips64el. to be marked as done. This means that you claim that the pro

Bug#899317: marked as done (mercurial-git: Breaks with python-dulwich 19.1)

Your message dated Thu, 10 Jan 2019 14:51:01 + with message-id and subject line Bug#899317: fixed in hg-git 0.8.12-1 has caused the Debian Bug report #899317, regarding mercurial-git: Breaks with python-dulwich 19.1 to be marked as done. This means that you claim that the problem has been dea

Bug#917721: libbiod: FTBFS: dh_auto_test: cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 MESON_TESTTHREADS=2 ninja test returned exit code 1

Am Do., 10. Jan. 2019 um 08:48 Uhr schrieb Andreas Tille : > > Control: forwarded -1 https://github.com/biod/BioD/issues/50 > Control: tags -1 help upstream > > Dear Matthias, > > unfortunately there is another issue with libbiod and as usual I need > your help due to my total incompetence in D. :-

Bug#897503: marked as done (hg-git: FTBFS: + cat: hgrepo2/.hgtags: No such file or directory)

Your message dated Thu, 10 Jan 2019 14:51:01 + with message-id and subject line Bug#897503: fixed in hg-git 0.8.12-1 has caused the Debian Bug report #897503, regarding hg-git: FTBFS: + cat: hgrepo2/.hgtags: No such file or directory to be marked as done. This means that you claim that the p

Bug#917200: Fixed

https://salsa.debian.org/qt-kde-team/qt/pyside2/merge_requests/2

Bug#917200: Bug #917200 in pyside2 marked as pending

Control: tag -1 pending Hello, Bug #917200 in pyside2 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/qt-kde-team/qt/pyside2/commit/119cad4ba5eb09f0ce294cf4b461

Processed: Bug #917200 in pyside2 marked as pending

Processing control commands: > tag -1 pending Bug #917200 [pyside2] pyside2: build-dependencies no longer satisfiable on mips64el. Added tag(s) pending. -- 917200: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917200 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Processed: forcibly merging 915890 917688

Processing commands for cont...@bugs.debian.org: > forcemerge 915890 917688 Bug #915890 [src:umlet] umlet FTBFS: error: package org.apache.bcel.classfile does not exist Bug #915890 [src:umlet] umlet FTBFS: error: package org.apache.bcel.classfile does not exist Added tag(s) buster and sid. Bug #

Bug#918742: Initialization loop/deadlock when used with jemalloc

On Wed, Jan 09, 2019 at 10:42:06PM +0100, Johannes Schauer wrote: > Quoting Faidon Liambotis (2019-01-09 16:16:40) > > > Until it is properly fixed upstream we can just temporarily disable > > > --enable-prof, right? > > We could, yes. This is a useful piece of functionality that I'd like to > > en

Processed: Merge duplicates

Processing commands for cont...@bugs.debian.org: > reassign 902509 src:node-send Bug #902509 [node-send] node-serve-static: FTBFS in buster/sid (TypeError: mime.lookup is not a function) Bug reassigned from package 'node-send' to 'src:node-send'. Ignoring request to alter found versions of bug #9

Processed (with 1 error): merging 902508 902509

Processing commands for cont...@bugs.debian.org: > merge 902508 902509 Bug #902508 [src:node-send] node-send: FTBFS in buster/sid (TypeError: mime.lookup is not a function) Unable to merge bugs because: package of #902509 is 'node-send' not 'src:node-send' Failed to merge 902508: Did not alter me

Bug#902508: node-send: FTBFS in buster/sid (TypeError: mime.lookup is not a function)

Problem found: node-send depends on node-mime 1.6 while unstable has node-mime 2.3.1-1 (with breaking changes) Probably same issue for #902507

Bug#902509: node-serve-static: FTBFS in buster/sid (TypeError: mime.lookup is not a function)

Control: reassign -1 node-send Build error is in node-send (index.js line 693)

Processed: Re: node-serve-static: FTBFS in buster/sid (TypeError: mime.lookup is not a function)

Processing control commands: > reassign -1 node-send Bug #902509 [src:node-serve-static] node-serve-static: FTBFS in buster/sid (TypeError: mime.lookup is not a function) Bug reassigned from package 'src:node-serve-static' to 'node-send'. No longer marked as found in versions node-serve-static/1.

Processed (with 1 error): forcibly merging 902508 902509

Processing commands for cont...@bugs.debian.org: > forcemerge 902508 902509 Bug #902508 [src:node-send] node-send: FTBFS in buster/sid (TypeError: mime.lookup is not a function) Unable to merge bugs because: package of #902509 is 'src:node-serve-static' not 'src:node-send' Failed to forcibly merg

  1   2   >