Bug#825501: CVE-2016-4434

Hi Cyril, [I have not looked in detail on your poposal this is mainly focusing on one item below] On Mon, Dec 31, 2018 at 01:13:51AM +0100, Cyril Brulebois wrote: > Heya, > > Not the maintainer either, just joining the fun to see if I can help get > stuff to move; my main motivation behind this

Bug#917869: python-escript FTBFS on armhf, mips, mipsel and mips64el

Package: python-escript Version: 5.2-4 Severity: serious The most recent upload of python-escript failed to build on armhf, mipsel, mips64el and mips. All seemed to fail while linking a C++ library. g++ -o debian/tmp2/posix/weipa/src/libescriptreader.so -Wl,-z,relro -Wl,-z,now -fopenmp -shared

Bug#900447: Build against freerdp2

On Wed, 10 Oct 2018 08:58:07 +0200 Dominik George wrote: [..] > Well, if we disable RDP support, we can as well remove Guacamole. RDP is > what people use it for, I have never heard of anyone using it only for VNC.-- I have to disagree here. VNC is very useful to connect without taking over the

Bug#917867: singularity-container: not supportable for Stable

Package: singularity-container Version: 2.6.1-1 Severity: serious singularity-container previously had to be removed from stretch [1] due to the unfeasibility of security support for that version [private communication with security team and upstream]. While upstream has gotten better about markin

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

Your message dated Mon, 31 Dec 2018 04:49:53 + with message-id and subject line Bug#917572: Removed package(s) from unstable has caused the Debian Bug report #866432, regarding ibid: depends on obsolete python-imaging (replace with python3-pil or python-pil) to be marked as done. This means

Bug#916034: sl-modem-dkms: module FTBFS for 4.18.0-3-amd64, 4.9.0-8-amd64

On Sun, 09 Dec 2018 15:06:49 +0100 Andreas Beckmann wrote: > Package: sl-modem-dkms > Version: 2.9.11~20110321-13 > Severity: serious > User: debian...@lists.debian.org > Usertags: piuparts > Control: found -1 2.9.11~20110321-12 > > Hi, > > sl-modem-dkms fails to build a module for 4.18.0-3-amd6

Bug#917845: marked as done (fortune-zh: FTBFS - needs build dependency on python3)

Your message dated Mon, 31 Dec 2018 05:49:31 + with message-id and subject line Bug#917845: fixed in fortune-zh 2.91 has caused the Debian Bug report #917845, regarding fortune-zh: FTBFS - needs build dependency on python3 to be marked as done. This means that you claim that the problem has b

Processed: Re: Bug#889125: comidi-clojure FTBFS: test failure

Processing control commands: > forwarded -1 https://github.com/puppetlabs/comidi/issues/36 Bug #889125 [src:comidi-clojure] comidi-clojure FTBFS: test failure Set Bug forwarded-to-address to 'https://github.com/puppetlabs/comidi/issues/36'. -- 889125: https://bugs.debian.org/cgi-bin/bugreport.c

Bug#889125: comidi-clojure FTBFS: test failure

Control: forwarded -1 https://github.com/puppetlabs/comidi/issues/36 Cyril Brulebois (2018-12-31): > I think I'll forward this issue upstream and see if I can get some > guidance. Done, see URL above. Cheers, -- Cyril Brulebois (k...@debian.org) D-I release m

Processed: severity of 908492 is grave, tagging 908492

Processing commands for cont...@bugs.debian.org: > severity 908492 grave Bug #908492 [nat-rtsp-dkms] nat-rtsp-dkms: fails to build on new 4.18 kernels Severity set to 'grave' from 'serious' > tags 908492 + patch Bug #908492 [nat-rtsp-dkms] nat-rtsp-dkms: fails to build on new 4.18 kernels Added ta

Bug#912631: liblwjgl-java-jni: Missing symbols in liblwjgl.so, stretch-sid, 386, amd64, mips

Hello, and thank you very much for your answer. First, about OpenJDK 11, and "debian/patches/javah.patch". You are absolutely right to point that out. Actually, I had missed that the "javah" tool was removed since OpenJDK 10. Sorry for that. I was able to reproduce the same error as the on

Bug#832355: ktap: module FTBFS for Linux 4.6: error: '__GFP_WAIT' undeclared

On Tue, 2 Aug 2016 14:33:26 +0300 Azat Khuzhin wrote: > On Sun, Jul 24, 2016 at 04:20:38PM +0200, Andreas Beckmann wrote: > > Package: ktap > > Version: 0.4+git20160427-1 > > Severity: serious > > User: debian...@lists.debian.org > > Usertags: piuparts > > > > Hi, > > Hi Andreas, > > Thanks for

Bug#889125: comidi-clojure FTBFS: test failure

Hi, Adrian Bunk (2018-02-02): > Source: comidi-clojure > Version: 0.3.1-1 > Severity: serious > > Some recent change in unstable makes comidi-clojure FTBFS: […] I've bisected this issue within sid, at the archive level, thanks to snapshot.d.o, and I'm able to confirm this package built fine unt

Bug#884935: marked as done (python-poppler: Don't release with buster)

Your message dated Mon, 31 Dec 2018 04:57:14 + with message-id and subject line Bug#917832: Removed package(s) from unstable has caused the Debian Bug report #884935, regarding python-poppler: Don't release with buster to be marked as done. This means that you claim that the problem has been

Bug#917703: marked as done (golang-gopkg-macaroon.v2: FTBFS: build-dependency not installable: golang-github-juju-testing-dev)

Your message dated Mon, 31 Dec 2018 04:57:42 + with message-id and subject line Bug#917811: Removed package(s) from unstable has caused the Debian Bug report #917703, regarding golang-gopkg-macaroon.v2: FTBFS: build-dependency not installable: golang-github-juju-testing-dev to be marked as do

Bug#917696: marked as done (golang-github-juju-httprequest: FTBFS: build-dependency not installable: golang-github-juju-testing-dev)

Your message dated Mon, 31 Dec 2018 04:58:29 + with message-id and subject line Bug#917810: Removed package(s) from unstable has caused the Debian Bug report #917696, regarding golang-github-juju-httprequest: FTBFS: build-dependency not installable: golang-github-juju-testing-dev to be marked

Bug#899665: marked as done (python-aiml: Invalid maintainer address debian-olpc-de...@lists.alioth.debian.org)

Your message dated Mon, 31 Dec 2018 04:55:16 + with message-id and subject line Bug#917610: Removed package(s) from unstable has caused the Debian Bug report #899665, regarding python-aiml: Invalid maintainer address debian-olpc-de...@lists.alioth.debian.org to be marked as done. This means

Bug#879034: marked as done (pdfshuffler: port to gir1.2-poppler-0.18)

Your message dated Mon, 31 Dec 2018 04:56:43 + with message-id and subject line Bug#917831: Removed package(s) from unstable has caused the Debian Bug report #879034, regarding pdfshuffler: port to gir1.2-poppler-0.18 to be marked as done. This means that you claim that the problem has been d

Bug#874751: Processed: severity of 874751 is grave

I am probably still registered as maintainer of this package, however it's been years I am not involves with, neither interested by it. If someone uploads it once more, please remove me from uploaders. Cheers, Thomas Goirand (zigo)

Bug#891095: marked as done (ibid: python-beautifulsoup is replaced with python-bs4)

Your message dated Mon, 31 Dec 2018 04:49:53 + with message-id and subject line Bug#917572: Removed package(s) from unstable has caused the Debian Bug report #891095, regarding ibid: python-beautifulsoup is replaced with python-bs4 to be marked as done. This means that you claim that the prob

Bug#917861: Fails to build against Linux 4.19

Package: kpatch-dkms Version: 0.6.0-0.1 Severity: grave kpatch in testing/unstable fails to build a module for Linux 4.19, which is the current kernel version in these suites and the version that will be included in Debian 10 "buster": CC [M] /var/lib/dkms/kpatch/0.6.0/build/kmod/core/core.o /

Bug#891087: marked as done (beautifulsoup has been replaced by bs4)

Your message dated Mon, 31 Dec 2018 04:50:32 + with message-id and subject line Bug#917575: Removed package(s) from unstable has caused the Debian Bug report #891087, regarding beautifulsoup has been replaced by bs4 to be marked as done. This means that you claim that the problem has been dea

Bug#917860: Fails to build for non-current kernel version

Package: kpatch-dkms Version: 2.0.93-0.10 Severity: serious When running kernel version 4.18.0-3-amd64 and building for 4.19.0-1-amd64, the build fails: ... Setting up kpatch-dkms (0.6.0-0.1) ... Loading new kpatch-0.6.0 DKMS files... Building for 4.19.0-1-amd64 Building initial module for 4.19.0

Bug#915468: marked as done (logfs-tools seems useless after logfs was removed from the kernel)

Your message dated Mon, 31 Dec 2018 04:47:53 + with message-id and subject line Bug#917514: Removed package(s) from unstable has caused the Debian Bug report #915468, regarding logfs-tools seems useless after logfs was removed from the kernel to be marked as done. This means that you claim th

Bug#906871: marked as done (xul-ext-flashblock no longer works with firefox-esr 60)

Your message dated Mon, 31 Dec 2018 04:46:34 + with message-id and subject line Bug#917486: Removed package(s) from unstable has caused the Debian Bug report #906871, regarding xul-ext-flashblock no longer works with firefox-esr 60 to be marked as done. This means that you claim that the prob

Bug#915466: marked as done (logfs-tools FTBFS with glibc 2.28)

Your message dated Mon, 31 Dec 2018 04:47:53 + with message-id and subject line Bug#917514: Removed package(s) from unstable has caused the Debian Bug report #915466, regarding logfs-tools FTBFS with glibc 2.28 to be marked as done. This means that you claim that the problem has been dealt wi

Bug#890804: marked as done (xul-ext-tabmixplus: add WebExtensions version)

Your message dated Mon, 31 Dec 2018 04:47:01 + with message-id and subject line Bug#917487: Removed package(s) from unstable has caused the Debian Bug report #890804, regarding xul-ext-tabmixplus: add WebExtensions version to be marked as done. This means that you claim that the problem has b

Bug#906867: marked as done (xul-ext-status4evar no longer works with firefox-esr 60)

Your message dated Mon, 31 Dec 2018 04:46:09 + with message-id and subject line Bug#917484: Removed package(s) from unstable has caused the Debian Bug report #906867, regarding xul-ext-status4evar no longer works with firefox-esr 60 to be marked as done. This means that you claim that the pro

Bug#881894: marked as done (xul-ext-cookie-monster: dead upstream, broken in FF57)

Your message dated Mon, 31 Dec 2018 04:47:27 + with message-id and subject line Bug#917488: Removed package(s) from unstable has caused the Debian Bug report #881894, regarding xul-ext-cookie-monster: dead upstream, broken in FF57 to be marked as done. This means that you claim that the probl

Bug#906865: marked as done (xul-ext-refcontrol no longer works with firefox-esr 60)

Your message dated Mon, 31 Dec 2018 04:45:42 + with message-id and subject line Bug#917480: Removed package(s) from unstable has caused the Debian Bug report #906865, regarding xul-ext-refcontrol no longer works with firefox-esr 60 to be marked as done. This means that you claim that the prob

Bug#895315: marked as done (xul-ext-greasemonkey: Could not use script with recent firefox need to upgrade to 4.x)

Your message dated Mon, 31 Dec 2018 04:44:49 + with message-id and subject line Bug#917477: Removed package(s) from unstable has caused the Debian Bug report #864820, regarding xul-ext-greasemonkey: Could not use script with recent firefox need to upgrade to 4.x to be marked as done. This me

Bug#881970: marked as done (xul-ext-foxyproxy-standard: new upstream version (with WebExtensions support))

Your message dated Mon, 31 Dec 2018 04:45:17 + with message-id and subject line Bug#917479: Removed package(s) from unstable has caused the Debian Bug report #881970, regarding xul-ext-foxyproxy-standard: new upstream version (with WebExtensions support) to be marked as done. This means that

Bug#881972: marked as done (xul-ext-webdeveloper: new upstream version (WebExtensions support))

Your message dated Mon, 31 Dec 2018 04:44:22 + with message-id and subject line Bug#917476: Removed package(s) from unstable has caused the Debian Bug report #881972, regarding xul-ext-webdeveloper: new upstream version (WebExtensions support) to be marked as done. This means that you claim t

Bug#906830: marked as done (xul-ext-colorfultabs no longer works with firefox-esr 60)

Your message dated Mon, 31 Dec 2018 04:43:26 + with message-id and subject line Bug#917473: Removed package(s) from unstable has caused the Debian Bug report #906830, regarding xul-ext-colorfultabs no longer works with firefox-esr 60 to be marked as done. This means that you claim that the pr

Bug#906869: marked as done (xul-ext-uppity no longer works with firefox-esr 60)

Your message dated Mon, 31 Dec 2018 04:42:59 + with message-id and subject line Bug#917472: Removed package(s) from unstable has caused the Debian Bug report #906869, regarding xul-ext-uppity no longer works with firefox-esr 60 to be marked as done. This means that you claim that the problem

Bug#864820: marked as done (xul-ext-greasemonkey: userscripts no longer available with firefox 54)

Your message dated Mon, 31 Dec 2018 04:44:49 + with message-id and subject line Bug#917477: Removed package(s) from unstable has caused the Debian Bug report #864820, regarding xul-ext-greasemonkey: userscripts no longer available with firefox 54 to be marked as done. This means that you clai

Bug#910756: marked as done (xul-ext-useragentswitcher: Firefox 60esr breaks user-agent-switcher. Please upgrade to upstream version which works.)

Your message dated Mon, 31 Dec 2018 04:42:31 + with message-id and subject line Bug#917471: Removed package(s) from unstable has caused the Debian Bug report #910756, regarding xul-ext-useragentswitcher: Firefox 60esr breaks user-agent-switcher. Please upgrade to upstream version which works.

Bug#908432: marked as done (xul-ext-webdeveloper depends on libjs-twitter-bootstrap that will not be in buster)

Your message dated Mon, 31 Dec 2018 04:44:22 + with message-id and subject line Bug#917476: Removed package(s) from unstable has caused the Debian Bug report #908432, regarding xul-ext-webdeveloper depends on libjs-twitter-bootstrap that will not be in buster to be marked as done. This means

Bug#881904: marked as done (xul-ext-useragentswitcher: does not work with modern versions of Firefox)

Your message dated Mon, 31 Dec 2018 04:42:31 + with message-id and subject line Bug#917471: Removed package(s) from unstable has caused the Debian Bug report #881904, regarding xul-ext-useragentswitcher: does not work with modern versions of Firefox to be marked as done. This means that you

Bug#827310: marked as done (xul-ext-pwdhash from stable is not compatible to firefox-esr and gets disabled)

Your message dated Mon, 31 Dec 2018 04:43:53 + with message-id and subject line Bug#917475: Removed package(s) from unstable has caused the Debian Bug report #827310, regarding xul-ext-pwdhash from stable is not compatible to firefox-esr and gets disabled to be marked as done. This means tha

Bug#917858: Fails to build a binary module package

Package: device3dfx-source Version: 2013.08.08-5 Severity: grave Running "module-assistant -l 4.19.0-1-amd64 auto-build device3dfx-source" currently fails, with the following errors: ... Setting up device3dfx-source (2013.08.08-5) ... W: --force-yes is deprecated, use one of the options starting

Processed: severity of 874751 is grave

Processing commands for cont...@bugs.debian.org: > severity 874751 grave Bug #874751 [blktap-dkms] blktap-dkms: module FTBFS for Linux 4.12 Severity set to 'grave' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 874751: https://bugs.debian.org/cgi-b

Bug#917857: Fails to build against Linux 4.19

Package: aufs-dkms Version: 4.18+20180903-1 Severity: grave aufs in testing/unstable currently only works with Linux 4.18, but the kernel version in these suites is 4.19 (and this is the version that will be included in Debian 10 "buster"). Please update to a new upstream version that is compatib

Bug#790149: marked as done (xword: depends on python-wnck which is deprecated)

Your message dated Mon, 31 Dec 2018 04:14:39 + with message-id and subject line Bug#913852: Removed package(s) from unstable has caused the Debian Bug report #790149, regarding xword: depends on python-wnck which is deprecated to be marked as done. This means that you claim that the problem h

Bug#822590: marked as done (liblunar: depends on python-gtksourceview2 which is deprecated)

Your message dated Mon, 31 Dec 2018 04:15:22 + with message-id and subject line Bug#914111: Removed package(s) from unstable has caused the Debian Bug report #822590, regarding liblunar: depends on python-gtksourceview2 which is deprecated to be marked as done. This means that you claim that

Bug#906044: marked as done (python-lunar: missing python dependency)

Your message dated Mon, 31 Dec 2018 04:15:22 + with message-id and subject line Bug#914111: Removed package(s) from unstable has caused the Debian Bug report #906044, regarding python-lunar: missing python dependency to be marked as done. This means that you claim that the problem has been de

Processed: unblock 917844 with 913930

Processing commands for cont...@bugs.debian.org: > unblock 917844 with 913930 Bug #917844 [src:lintian] lintian: tests fail under groff 1.22.4-1 917844 was blocked by: 913930 917844 was blocking: 917752 Removed blocking bug(s) of 917844: 913930 > thanks Stopping processing here. Please contact me

Bug#917844: Fixed

Hi, I did not see the separate report at first and commented on #917752. For a fix, please see: https://salsa.debian.org/lintian/lintian/merge_requests/113 Felix Lechner

Bug#917592: libterm-termkey-perl: FTBFS (failing tests)

Dropping debhelper and related bug, since this is just about libtermkey. On Sun, Dec 30, 2018 at 08:22:00PM +, Niels Thykier wrote: > Anyhow, on to the details I have found: > > * Only test case 05flags.t fails and only if stdin is a *readable* >non-tty (e.g. /dev/null, an empty file or

Processed: tagging 897882

Processing commands for cont...@bugs.debian.org: > tags 897882 + ftbfs Bug #897882 [src:validns] validns: ftbfs with GCC-8 Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 897882: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897882 Debian B

Bug#917752: lintian: FTBFS: tests failed

On Sun, Dec 30, 2018 at 3:06 PM Chris Lamb wrote: > > > > -W: manpages-general: manpage-has-errors-from-man > > > usr/share/man/man1/test.1p.gz 14: warning: macro `dep' not defined > […] > > Like you, I have not seen this one. This test was not changed recently; > > neither was the associated

Bug#825501: CVE-2016-4434

Heya, Not the maintainer either, just joining the fun to see if I can help get stuff to move; my main motivation behind this is trying to get the puppetdb → pantomime-clojure → tika dependency chain in a suitable state for buster (other *-clojure packages need fixing, but FTBFSes have patches/MRs

Bug#917847: ipsec-tools is unsuitable for inclusion in Debian

Package: ipsec-tools Version: 1:0.8.2+20140711-12 Severity: grave [On behalf of the ipsec-tools maintainers, I'm opening this against ipsec-tools for visibility and discussion.] The package is effectively orphaned upstream and has been for some time. Given the security-sensitive nature of the pac

Processed: Re: golang-github-nats-io-gnatsd FTBFS: cannot find package "github.com/nats-io/jwt"

Processing control commands: > tags -1 patch Bug #915279 [src:golang-github-nats-io-gnatsd] golang-github-nats-io-gnatsd FTBFS: cannot find package "github.com/nats-io/jwt" Added tag(s) patch. -- 915279: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915279 Debian Bug Tracking System Contact

Bug#915279: golang-github-nats-io-gnatsd FTBFS: cannot find package "github.com/nats-io/jwt"

Control: tags -1 patch Dear Maintainer, In Ubuntu, the attached patch was applied to achieve the following: * Build-depend on golang-github-nats-io-jwt-dev to fix FTBFS. Thanks for considering the patch. Logan Rosen -- System Information: Debian Release: buster/sid APT prefers cosmic-upda

Bug#917752: lintian: FTBFS: tests failed

On Sun, Dec 30, 2018 at 3:06 PM Chris Lamb wrote: > > > > +I: changes-upstream-signature-not-missing source: > > > public-upstream-key-unusable upstream/signing-key.asc cannot be > > > processed > > > > This looks like #913930. I have only seen it in sbuild, but not otherwise. > > Interesting

Bug#917845: fortune-zh: FTBFS - needs build dependency on python3

Package: fortune-zh Version: 2.90 Severity: serious Tags: patch ftbfs Justification: fails to build from source (but built successfully in the past) User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu disco ubuntu-patch Dear Maintainer, fortune-zh currently fails to build from source in a

Bug#914440: marked as done (photocollage: ValueError: Namespace Gtk not available)

Your message dated Sun, 30 Dec 2018 23:34:42 + with message-id and subject line Bug#914440: fixed in photocollage 1.4.3-2.1 has caused the Debian Bug report #914440, regarding photocollage: ValueError: Namespace Gtk not available to be marked as done. This means that you claim that the proble

Processed: Bug#917752: lintian: FTBFS: tests failed

Processing commands for cont...@bugs.debian.org: > severity 913930 serious Bug #913930 [lintian] lintian: Potentially false-positive public-upstream-key-unusable upstream/signing-key.asc Ignoring request to change severity of Bug 913930 to the same value. > block 917752 by 913930 Bug #917752 [src

Bug#917660: vim-youcompleteme: FTBFS (failing tests)

Control: merge -1 917682 Control: reassign -1 python3-hamcrest 1.8.0-1 Control: affects -1 vim-youcompleteme Hi On Sat, Dec 29, 2018 at 09:39:19PM +, Santiago Vila wrote: > File "/usr/lib/python3/dist-packages/hamcrest/core/helpers/hasmethod.py", > line 13, in hasmethod > return isinst

Processed (with 5 errors): Re: Bug#917752: lintian: FTBFS: tests failed

Processing commands for cont...@bugs.debian.org: > severity 913930 serious Bug #913930 [lintian] lintian: Potentially false-positive public-upstream-key-unusable upstream/signing-key.asc Severity set to 'serious' from 'minor' > block 971152 by 913930 Failed to set blocking bugs of 971152: Unable

Processed: Re: Bug#917660: vim-youcompleteme: FTBFS (failing tests)

Processing control commands: > merge -1 917682 Bug #917660 [src:vim-youcompleteme] vim-youcompleteme: FTBFS (failing tests) Bug #917682 [src:vim-youcompleteme] vim-youcompleteme: FTBFS: tests failed Added tag(s) ftbfs. Bug #917660 [src:vim-youcompleteme] vim-youcompleteme: FTBFS (failing tests) Ad

Bug#917752: lintian: FTBFS: tests failed

severity 913930 serious block 971152 by 913930 clone 971152 -1 retitle -1 lintian: tests fail under groff 1.22.4-1 severity -1 serious block 971152 by -1 thanks Hi Felix, > > +I: changes-upstream-signature-not-missing source: > > public-upstream-key-unusable upstream/signing-key.asc cannot be

Bug#888549: marked as done (chrome-gnome-shell: Please don't use /etc/opt, it's not FHS-compliant)

Your message dated Sun, 30 Dec 2018 22:48:59 + with message-id and subject line Bug#888549: fixed in chrome-gnome-shell 10.1-4 has caused the Debian Bug report #888549, regarding chrome-gnome-shell: Please don't use /etc/opt, it's not FHS-compliant to be marked as done. This means that you cl

Bug#917644: FTBFS: segmentation faults in test suite

If it is just the `world` regression tests that are failing, then it is almost certainly due to save/restore world being incompatible with ASLR; see http://mlton.org/MLtonWorld#_notes. Perhaps Debian arm64-linux has gained ASLR since the last time the regression suite was run on this platform? In

Bug#872935: FTBFS: Could not locate puppetlabs/kitchensink/testutils__init.class or puppetlabs/kitchensink/testutils.clj on classpath.

Control: tag -1 patch Cyril Brulebois (2018-12-30): > I'll propose the same kind of patch as the other ones through salsa's > MR system, as requested/suggested by maintainers. :) There you go: https://salsa.debian.org/java-team/kitchensink-clojure/merge_requests/1 (You'll also find it attache

Processed: Re: Bug#872935: FTBFS: Could not locate puppetlabs/kitchensink/testutils__init.class or puppetlabs/kitchensink/testutils.clj on classpath.

Processing control commands: > tag -1 patch Bug #872935 [src:kitchensink-clojure] FTBFS: Could not locate puppetlabs/kitchensink/testutils__init.class or puppetlabs/kitchensink/testutils.clj on classpath. Added tag(s) patch. -- 872935: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872935 D

Processed: Reassign skimage bugs

Processing commands for cont...@bugs.debian.org: > reassign 917751 python3-skimage 0.14.1-2 Bug #917751 [src:ccdproc] ccdproc: FTBFS: tests failed Bug reassigned from package 'src:ccdproc' to 'python3-skimage'. No longer marked as found in versions ccdproc/1.3.0-4. Ignoring request to alter fixed

Bug#917837: clutter-gesture: Intent to remove from Debian

Source: clutter-gesture Version: 0.0.2.1-7.1 Severity: serious Tags: buster sid clutter-gesture is a library with no reverse dependencies. (The last package to use clutter-gesture was mx which was removed from Debian months ago). The project is unmaintained. I am unable to find a homepage or sour

Bug#916963: marked as done (libarchive: CVE-2018-1000878)

Your message dated Sun, 30 Dec 2018 22:03:18 + with message-id and subject line Bug#916963: fixed in libarchive 3.2.2-2+deb9u1 has caused the Debian Bug report #916963, regarding libarchive: CVE-2018-1000878 to be marked as done. This means that you claim that the problem has been dealt with.

Bug#893610: marked as done (ruby-sanitize: CVE-2018-3740)

Your message dated Sun, 30 Dec 2018 22:03:25 + with message-id and subject line Bug#893610: fixed in ruby-sanitize 2.1.0-2+deb9u1 has caused the Debian Bug report #893610, regarding ruby-sanitize: CVE-2018-3740 to be marked as done. This means that you claim that the problem has been dealt wi

Processed: Re: Bug#872935: FTBFS: Could not locate puppetlabs/kitchensink/testutils__init.class or puppetlabs/kitchensink/testutils.clj on classpath.

Processing control commands: > severity -1 serious Bug #872935 [src:kitchensink-clojure] FTBFS: Could not locate puppetlabs/kitchensink/testutils__init.class or puppetlabs/kitchensink/testutils.clj on classpath. Severity set to 'serious' from 'important' -- 872935: https://bugs.debian.org/cgi-

Processed: your mail

Processing commands for cont...@bugs.debian.org: > found 916945 1:7.0.1-1 Bug #916945 [src:llvm-toolchain-7] llvm-toolchain-7: unicode non free license Marked as found in versions llvm-toolchain-7/1:7.0.1-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 916945:

Bug#911628: marked as done (python3-websockets: fails to upgrade from 'stretch': SyntaxError: 'yield' inside async function)

Your message dated Sun, 30 Dec 2018 21:28:07 +0100 with message-id <20181230202807.japjwds6k4qvw...@sar0.p1otr.com> and subject line fixed in 7.0-1 has caused the Debian Bug report #911628, regarding python3-websockets: fails to upgrade from 'stretch': SyntaxError: 'yield' inside async function to

Bug#917592: libterm-termkey-perl: FTBFS (failing tests)

Niels Thykier: > [...] > > Stacktrace follows: > > """ > (gdb) bt full > #0 termkey_get_flags (tk=0x0) at termkey.c:565 > No locals. > #1 0x7794cba6 in XS_Term__TermKey_get_flags (my_perl= out>, cv=) at lib/Term/TermKey.xs:457 > self = > RETVAL = > targ = 0x555

Bug#917592: libterm-termkey-perl: FTBFS (failing tests)

gregor herrmann: > On Sat, 29 Dec 2018 16:11:00 +, Niels Thykier wrote: > Does/did it work under nohup (without the debhelper work around to make nohup work)? >>> >>> Yes, in the same chroot (i.e. with the STDIN redirection commented >>> out) `TERM=vt100 nohup prove --blib --verbose

Bug#917791: [Pkg-xmpp-devel] Bug#917791: poezio: Missing dependency on python3-cffi

On 2018-12-30 19:55, Dominik George wrote: > I can reproduce the issue with 0.12.1-2, and I strongly doubt it works > without cffi (except in cases where the code that uses cffi is for some > reason not executed): > > $ grep -r cffi > […] > poezio/poopt.py:from cffi import FFI Strange, that it sti

Bug#917829: python-intbitset: FTBFS when built with dpkg-buildpackage -A

Package: src:python-intbitset Version: 2.3.0-3 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in buster with dpkg-buildpackage -A but it failed: [...] debian/rules build-indep dh build

Processed: found 917791 in 0.12.1-2

Processing commands for cont...@bugs.debian.org: > found 917791 0.12.1-2 Bug #917791 [poezio] poezio: Missing dependency on python3-cffi Marked as found in versions poezio/0.12.1-2. > thanks Stopping processing here. Please contact me if you need assistance. -- 917791: https://bugs.debian.org/cg

Bug#917791: [Pkg-xmpp-devel] Bug#917791: poezio: Missing dependency on python3-cffi

On Sun, Dec 30, 2018 at 07:38:32PM +0100, W. Martin Borgert wrote: > On 2018-12-30 12:20, Tom Teichler wrote: > > When starting python3-cffi is missing. Does not work at all. > > I'm using poezio 0.12.1-2 (uploaded yesterday) and it works > perfectly without python3-cffi*. Could you try that, plea

Bug#917791: poezio: Missing dependency on python3-cffi

On 2018-12-30 12:20, Tom Teichler wrote: > When starting python3-cffi is missing. Does not work at all. I'm using poezio 0.12.1-2 (uploaded yesterday) and it works perfectly without python3-cffi*. Could you try that, please?

Bug#917430: marked as done (libconfig-model-dpkg-perl: test failures with newer Config::Model)

Your message dated Sun, 30 Dec 2018 18:34:15 + with message-id and subject line Bug#917430: fixed in libconfig-model-dpkg-perl 2.120 has caused the Debian Bug report #917430, regarding libconfig-model-dpkg-perl: test failures with newer Config::Model to be marked as done. This means that you

Bug#879034: Bug #879034 in pdfshuffler marked as pending

Control: tag -1 pending Hello, Bug #879034 in pdfshuffler 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/python-team/applications/pdfshuffler/commit/84f3a44ba6

Processed: Bug #879034 in pdfshuffler marked as pending

Processing control commands: > tag -1 pending Bug #879034 [pdfshuffler] pdfshuffler: port to gir1.2-poppler-0.18 Added tag(s) pending. -- 879034: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=879034 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#917430: libconfig-model-dpkg-perl: test failures with newer Config::Model

On Sun, 30 Dec 2018 18:57:26 +0100, Dominique Dumont wrote: > On Thu, 27 Dec 2018 17:56:46 +0100 gregor herrmann wrote: > > libconfig-model-dpkg-perl (both 2.119 in the archive and the version > > in git) doesn't build anymore, probably due to changes in or around > > Config::Model. > More likely

Processed: tagging 917124

Processing commands for cont...@bugs.debian.org: > tags 917124 - moreinfo Bug #917124 {Done: Michael Biebl } [udev] lvm2 logical volumes are not properly initialized Bug #917136 {Done: Michael Biebl } [udev] udev: LVM volumes fail to initialize properly with udev 240-1 Bug #917166 {Done: Michael

Processed: Re: Bug#917234: [initramfs-tools] Unable to detect root device

Processing control commands: > reassign -1 udev Bug #917234 [initramfs-tools] [initramfs-tools] Unable to detect root device Bug reassigned from package 'initramfs-tools' to 'udev'. No longer marked as found in versions initramfs-tools/0.132. Ignoring request to alter fixed versions of bug #917234

Bug#917217: npm breaks other packages' bash-completion

Hi, > I don't see such a line here. > https://salsa.debian.org/js-team/npm/blob/master/lib/utils/completion.sh > > May be that came from an older version? Can you purge npm, reinstall and > confirm > if you still see it? I just extracted the package and to my surprise found the file somewhere i

Bug#917592: libterm-termkey-perl: FTBFS (failing tests)

On Sat, 29 Dec 2018 16:11:00 +, Niels Thykier wrote: > >> Does/did it work under nohup (without the > >> debhelper work around to make nohup work)? > > > > Yes, in the same chroot (i.e. with the STDIN redirection commented > > out) `TERM=vt100 nohup prove --blib --verbose t/*.t' in d/rules wo

Bug#917430: libconfig-model-dpkg-perl: test failures with newer Config::Model

On Thu, 27 Dec 2018 17:56:46 +0100 gregor herrmann wrote: > libconfig-model-dpkg-perl (both 2.119 in the archive and the version > in git) doesn't build anymore, probably due to changes in or around > Config::Model. More likely, lintian was updated and some tests are too pedantic to handle well

Bug#914999: [libc6] Locking problems into libc6

On 2018-12-12 17:11, Roman Savochenko wrote: > Hello, Aurelien > > 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 resolved the prob

Bug#917720: marked as done (sunpy: FTBFS: dh_auto_test: pybuild --test --test-pytest -i python{version} -p 3.7 returned exit code 13)

Your message dated Sun, 30 Dec 2018 17:34:41 + with message-id and subject line Bug#917353: fixed in skimage 0.14.1-3 has caused the Debian Bug report #917353, regarding sunpy: FTBFS: dh_auto_test: pybuild --test --test-pytest -i python{version} -p 3.7 returned exit code 13 to be marked as do

Bug#917353: marked as done ([python3-skimage] Cannot import skimage with new numpy)

Your message dated Sun, 30 Dec 2018 17:34:41 + with message-id and subject line Bug#917353: fixed in skimage 0.14.1-3 has caused the Debian Bug report #917353, regarding [python3-skimage] Cannot import skimage with new numpy to be marked as done. This means that you claim that the problem has

Bug#917683: marked as done (hipspy: FTBFS: ImportError: cannot import name '_validate_lengths' from 'numpy.lib.arraypad' (/usr/lib/python3/dist-packages/numpy/lib/arraypad.py))

Your message dated Sun, 30 Dec 2018 17:34:41 + with message-id and subject line Bug#917353: fixed in skimage 0.14.1-3 has caused the Debian Bug report #917353, regarding hipspy: FTBFS: ImportError: cannot import name '_validate_lengths' from 'numpy.lib.arraypad' (/usr/lib/python3/dist-package

Bug#917801: marked as done (pacemaker is linked to both libcfg6 and libcfg7 causing it to fail to start)

Your message dated Sun, 30 Dec 2018 18:22:53 +0100 with message-id <20181230172253.ga20...@aurel32.net> and subject line Re: pacemaker is linked to both libcfg6 and libcfg7 causing it to fail to start has caused the Debian Bug report #917801, regarding pacemaker is linked to both libcfg6 and libcf

Bug#917752: lintian: FTBFS: tests failed

Chris, On Sat, Dec 29, 2018 at 3:23 PM Chris Lamb wrote: > > > > +I: changes-upstream-signature-not-missing source: > public-upstream-key-unusable upstream/signing-key.asc cannot be processed > > Felix, not sure your MR/branch handles this one? > This looks like #913930. I have only seen it in

Bug#917638: infnoise: Job dev-infnoise.device/start failed with result 'timeout'

> Does the device itself work? With the package installed, > > sudo infnoise --debug --no-output > > should produce output similar to Hello Stephen, unfortunately, it just produces "Error:" like this: 8< - >8 root@:~# infnoise --debug --

Bug#916971: gmsh: diff for NMU version 3.0.6+dfsg1-4.1

Hello Gilles, thanks for the NMU! Feel free to put it into the DELAYED/0. Regards Anton Am So., 30. Dez. 2018 um 12:24 Uhr schrieb Gilles Filippini : > > Control: tags 916971 + pending > > Dear maintainer, > > I've prepared an NMU for gmsh (versioned as 3.0.6+dfsg1-4.1) and > uploaded it to DEL

Bug#917727: openhft-lang: FTBFS: [ERROR] /<>/lang/src/main/java/net/openhft/lang/io/IOTools.java:[85, 13] cannot find symbol

On Sat, Dec 29, 2018 at 11:25:20PM +0100, Lucas Nussbaum wrote: > Source: openhft-lang > Version: 6.7.6-1 > Severity: serious > Justification: FTBFS on amd64 > Tags: buster sid > Usertags: ftbfs-20181229 ftbfs-buster Hi, Given that there aren't many (or any?) r-deps for the openhft libraries, I'm

Bug#917731: marked as done (ocaml-rope: FTBFS: dh_install: missing files, aborting)

Your message dated Sun, 30 Dec 2018 16:11:11 + with message-id and subject line Bug#917731: fixed in ocaml-rope 0.6.1-2 has caused the Debian Bug report #917731, regarding ocaml-rope: FTBFS: dh_install: missing files, aborting to be marked as done. This means that you claim that the problem h

  1   2   >