Processed: Bug #919625 in neutron-fwaas marked as pending

Processing control commands: > tag -1 pending Bug #919625 [neutron-fwaas-common] neutron-fwaas-common: fails to remove: neutron-plugin-manage disable: error: argument --service-plugin: invalid choice: 'firewall_v2' Added tag(s) pending. -- 919625:

Bug#919625: Bug #919625 in neutron-fwaas marked as pending

Control: tag -1 pending Hello, Bug #919625 in neutron-fwaas reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at:

Bug#880393: testing cyrus-sasl2 2.1.27+dfsg-1~exp1 (was: Re: nmuing cyrus-sasl2)

Hello Ondřej, On Mon, Jan 21, 2019 at 05:54:39PM +0100, OndÅ?ej Surý wrote: I spent a half-day hacking cyrus-sasl2 and I uploaded 2.1.27 to experimental. I would appreciate if more people can test the package (I won’t have time until tomorrow or next week). I didn’t even had a chance to test

Bug#920146: janest-core-kernel: build-depends on libbin-prot-camlp4-dev

Package: src:janest-core-kernel Version: 113.00.00-3 Severity: serious Tags: ftbfs User: trei...@debian.org Usertags: edos-uninstallable janest-core-kernel build-depends on libbin-prot-camlp4-dev which lives in sid only on hurd-i386. This makes it FTBFS on all other archs where it used to compile

Processed: Merge duplicates

Processing commands for cont...@bugs.debian.org: > reassign 920045 src:ntopng Bug #920045 [ntomng] ntopng FTBFS with new ndpi Warning: Unknown package 'ntomng' Bug reassigned from package 'ntomng' to 'src:ntopng'. No longer marked as found in versions 2.4+dfsg1-4. Ignoring request to alter fixed

Processed: Merge duplicates

Processing commands for cont...@bugs.debian.org: > reassign 920020 openjdk-11-jdk-headless Bug #920020 [openjdk-11-jdk] javadoc: The code being documented uses modules but the packages defined in … are in the unnamed module Bug reassigned from package 'openjdk-11-jdk' to

Bug#919822: marked as done (gitlab: CVE-2019-6240: Arbitrary repo read in Gitlab project import)

Your message dated Tue, 22 Jan 2019 06:05:01 + with message-id and subject line Bug#919822: fixed in gitlab 11.5.7+dfsg-1 has caused the Debian Bug report #919822, regarding gitlab: CVE-2019-6240: Arbitrary repo read in Gitlab project import to be marked as done. This means that you claim

Processed: tagging 920018, severity of 920018 is serious

Processing commands for cont...@bugs.debian.org: > tags 920018 + upstream Bug #920018 [systemd] Memory Leak in journald? Failed to write entry (23 items, 500 bytes), ignoring: Cannot allocate memory Added tag(s) upstream. > # regression > severity 920018 serious Bug #920018 [systemd] Memory

Bug#919727: cmtk /dcmtk

Thanks Yarik, but too late ;) Anyway, I have a patch (see below) that appears to work. I'll be rolling a small bugfix release of CMTK in the next few days if/when I get a chance. Index: core/apps/dcm2image.cxx === ---

Bug#914147: marked as done (libkolabxml FTBFS: symbol differences)

Your message dated Tue, 22 Jan 2019 05:04:15 + with message-id and subject line Bug#914147: fixed in libkolabxml 1.1.6-3.1 has caused the Debian Bug report #914147, regarding libkolabxml FTBFS: symbol differences to be marked as done. This means that you claim that the problem has been dealt

Bug#919917: yui-compressor: insufficient java dependency in jessie

On Sun, Jan 20, 2019 at 06:14:31PM +0100, Andreas Beckmann wrote: > Package: yui-compressor > Version: 2.4.7-2 > Severity: serious > Tags: jessie > User: debian...@lists.debian.org > Usertags: piuparts > Control: affects -1 + libjs-protoaculous > Control: found -1 libjs-protoaculous/5 Hi Andreas,

Bug#919727: cmtk /dcmtk

On Mon, 21 Jan 2019, Torsten Rohlfing wrote: >Hi there - >Upstream owner of CMTK here. It looks like DCMTK in release 3.6.4 changed >their API for locking/unlocking the global data dictionary. >I am going to look into fixing this, but it'll take a while since I'll >have to

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

Processing commands for cont...@bugs.debian.org: > tags 919296 - patch pending Bug #919296 [git-daemon-run] git-daemon-run: fails with 'warning: git-daemon: unable to open supervise/ok: file does not exist' Removed tag(s) patch and pending. > quit Stopping processing here. Please contact me if

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

tags 919296 - patch pending quit Jonathan Nieder wrote: > For "buster", I prefer a minimal fix within the framework of the > current packages, along the lines you suggested upthread: > > diff --git i/debian/changelog w/debian/changelog > index ef513b2e1d..fb996c91f4 100644 > ---

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

found 919296 git/1:2.20.1-1 tags 919296 + patch pending quit Hi Dmitry, Dmitry Bogatov wrote: > [2019-01-16 14:49] Dmitry Bogatov >> So, should I propose you patch (in 7 days), that merges >> bin:git-daemon-run into bin:git-daemon, would you be able to review >> and apply/upload it before hard

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

Processing commands for cont...@bugs.debian.org: > found 919296 git/1:2.20.1-1 Bug #919296 [git-daemon-run] git-daemon-run: fails with 'warning: git-daemon: unable to open supervise/ok: file does not exist' Marked as found in versions git/1:2.20.1-1. > tags 919296 + patch pending Bug #919296

Bug#920136: libgnutls30: symbol lookup error...undefined symbol: __gmpz_limbs_write

Package: libgnutls30 Version: 3.6.5-2 Severity: critical Justification: breaks unrelated software Dear Maintainer, Sun 20 Jan 2019 10:25:49 PM EST I upgraded several packages on Jan 16. Since then, many programs (including cupsd, apt-get, and apt) fail like this: /usr/lib/apt/methods/http:

Bug#919196: Debian bug when running unit tests

Le lundi 21 janvier 2019 à 14:37:36+0100, Thomas Goirand a écrit : > Hi, > > Would you have any idea how to resolve this Debian bug? > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919196 > > I'm not sure, but to me, it looks like the unit tests are running in > loop in the ::handshake()

Bug#919196: Debian bug when running unit tests

Le mardi 22 janvier 2019 à 01:57:22+0100, Pierre-Elliott Bécue a écrit : > Le lundi 21 janvier 2019 à 14:37:36+0100, Thomas Goirand a écrit : > > Hi, > > > > Would you have any idea how to resolve this Debian bug? > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919196 > > > > I'm not sure,

Processed: bug 841494 is forwarded to https://debbugs.gnu.org/cgi/bugreport.cgi?bug=24659 ...

Processing commands for cont...@bugs.debian.org: > # bts-link: follow the redirect > forwarded 841494 https://debbugs.gnu.org/cgi/bugreport.cgi?bug=24659 Bug #841494 [guile-1.8] guile-1.8: CVE-2016-8605: Thread-unsafe umask modification Changed Bug forwarded-to-address to

Bug#919727: cmtk /dcmtk

Hi there - Upstream owner of CMTK here. It looks like DCMTK in release 3.6.4 changed their API for locking/unlocking the global data dictionary. I am going to look into fixing this, but it'll take a while since I'll have to set up a suitable Debian VM for testing first. Best, Torsten

Bug#919158: Bug #919158 in mailman-suite marked as pending

Control: tag -1 pending Hello, Bug #919158 in mailman-suite reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at:

Processed: Bug #919158 in mailman-suite marked as pending

Processing control commands: > tag -1 pending Bug #919158 [mailman3-web] mailman3-web: cronjobs should be run with flock to avoid them running amok Added tag(s) pending. -- 919158: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919158 Debian Bug Tracking System Contact ow...@bugs.debian.org

Bug#919174: marked as done (ruby-sinatra FTBFS with ruby-haml 5.0.4-1)

Your message dated Mon, 21 Jan 2019 23:21:56 + with message-id and subject line Bug#919174: fixed in ruby-sinatra 2.0.5-4 has caused the Debian Bug report #919174, regarding ruby-sinatra FTBFS with ruby-haml 5.0.4-1 to be marked as done. This means that you claim that the problem has been

Bug#910295: Bug#920019: duplicate of bug#910295 (dput: FTBFS: tests fail to mock HTTP request)

Control: found -1 dput/1.0.2 Control: block -1 by 919599 Control: summary 920019 The HTTPretty library is failing to mock requests from Python's HTTPConnection. Control: outlook 920019 Either correct the HTTPretty library; or re-work the DPut test cases to avoid HTTPretty. Control: forcemerge -1

Processed: Bug #919174 in ruby-sinatra marked as pending

Processing control commands: > tag -1 pending Bug #919174 [src:ruby-sinatra] ruby-sinatra FTBFS with ruby-haml 5.0.4-1 Added tag(s) pending. -- 919174: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919174 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#919174: Bug #919174 in ruby-sinatra marked as pending

Control: tag -1 pending Hello, Bug #919174 in ruby-sinatra reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at:

Processed: Bug#920019: duplicate of bug#910295 (dput: FTBFS: tests fail to mock HTTP request)

Processing control commands: > found -1 dput/1.0.2 Bug #910295 [dput] dput: FTBFS: tests fail to mock HTTP request Marked as found in versions dput/1.0.2. > block -1 by 919599 Bug #910295 [dput] dput: FTBFS: tests fail to mock HTTP request 910295 was blocked by: 919599 910295 was not blocking any

Bug#917500: marked as done (liggghts: FTBFS (style_atom.h: No such file or directory))

Your message dated Mon, 21 Jan 2019 23:06:01 + with message-id and subject line Bug#917500: fixed in liggghts 3.8.0+repack1-3 has caused the Debian Bug report #917500, regarding liggghts: FTBFS (style_atom.h: No such file or directory) to be marked as done. This means that you claim that the

Bug#912476: marked as done (libapache-poi-java: FTBFS with Java 11 due to JAXB removal)

Your message dated Mon, 21 Jan 2019 23:05:33 + with message-id and subject line Bug#912476: fixed in libapache-poi-java 4.0.1-1 has caused the Debian Bug report #912476, regarding libapache-poi-java: FTBFS with Java 11 due to JAXB removal to be marked as done. This means that you claim that

Processed (with 1 error): Bug#920019: duplicate of bug#910295 (dput: FTBFS: tests fail to mock HTTP request)

Processing control commands: > severity -1 serious Bug #920019 [dput] dput fails to build on test errors Severity set to 'serious' from 'normal' > reassign 910295 dput Bug #910295 [python3-httpretty] dput: FTBFS: tests fail to mock HTTP request Bug reassigned from package 'python3-httpretty' to

Bug#920020: [Openjdk] Bug#920020: javadoc: The code being documented uses modules but the packages defined in … are in the unnamed module

On Mon, 21 Jan 2019, Matthias Klose wrote: > no, why are you exaggerating? Both the jre and the jdk are usable. The javadoc tool isn’t, and this breaks all builds. I’ve enacted the workaround in the meantime, even if this goes against the documented javadoc options… bye, //mirabilos -- tarent

Bug#920028: marked as done (python3-bsddb3: ships header in /usr/include/python3.7/)

Your message dated Mon, 21 Jan 2019 22:52:28 + with message-id and subject line Bug#920028: fixed in python-bsddb3 6.2.6-3 has caused the Debian Bug report #920028, regarding python3-bsddb3: ships header in /usr/include/python3.7/ to be marked as done. This means that you claim that the

Bug#912476: Bug #912476 in libapache-poi-java marked as pending

Control: tag -1 pending Hello, Bug #912476 in libapache-poi-java reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at:

Processed: Bug #912476 in libapache-poi-java marked as pending

Processing control commands: > tag -1 pending Bug #912476 [src:libapache-poi-java] libapache-poi-java: FTBFS with Java 11 due to JAXB removal Added tag(s) pending. -- 912476: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912476 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Bug#915514: marked as done (pysph: Missing build-dependency on python-pytest-runner, Debian builds pulling source from network?)

Your message dated Mon, 21 Jan 2019 22:34:50 + with message-id and subject line Bug#915514: fixed in pysph 0~20180411.git1ae58e1-2.1 has caused the Debian Bug report #915514, regarding pysph: Missing build-dependency on python-pytest-runner, Debian builds pulling source from network? to be

Bug#917500: liggghts: FTBFS (style_atom.h: No such file or directory)

Small update: I've given Anton Gladky access to a machine where this seems to happen all the time. (While we are at it: Anybody reading this willing to debug the problem in the test machine, please contact me privately and I will gladly give you access as well). It is interesting to see that this

Processed: Re: BleachBit causing error since updating Firefox to Firefox Quantum 60.0 ESR

Processing commands for cont...@bugs.debian.org: > severity 912324 important Bug #912324 [bleachbit] BleachBit causing error since updating Firefox to Firefox Quantum 60.0 ESR Severity set to 'important' from 'serious' > fixed 912324 2.0-1 Bug #912324 [bleachbit] BleachBit causing error since

Bug#919649: axiom: /usr/lib/axiom-20170401/bin missing when package is rebuilt

Greetings, and thanks so much for your report! Just a quick note now to let you know I will be looking into this shortly! Take care, Juhani Numminen writes: > Juhani Numminen kirjoitti 18.1.2019 klo 13.15: >> Hi again, >> >> My test build just finished and I have attached the build log >>

Bug#919321: marked as done (CVE-2019-6246)

Your message dated Mon, 21 Jan 2019 21:50:38 + with message-id and subject line Bug#919321: fixed in svgpp 1.2.3+dfsg1-4 has caused the Debian Bug report #919321, regarding CVE-2019-6246 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the

Bug#919232: wireguard-dkms: Wireguard dkms module does not buuld against linux kernel 5.0-rc1 commit 7b55851367136b1efd84d98fea81ba57a98304cf

Control: severity -1 important Hi! Thank you for your bug report. It seems to me this problem affects only builds against the 5.0-rc1 Linux kernel version. Is that correct? Since that kernel version is not currently shipped in Debian, as far as I know, I do not believe the severity of that bug

Processed: Re: Bug#919232: wireguard-dkms: Wireguard dkms module does not buuld against linux kernel 5.0-rc1 commit 7b55851367136b1efd84d98fea81ba57a98304cf

Processing control commands: > severity -1 important Bug #919232 [wireguard-dkms] wireguard-dkms: Wireguard dkms module does not buuld against linux kernel 5.0-rc1 commit 7b55851367136b1efd84d98fea81ba57a98304cf Severity set to 'important' from 'grave' -- 919232:

Bug#910627: xul-ext-nostalgy: Please update to upstream 0.2.36 to be compatible with TB 60+

On Sat, Jan 19, 2019 at 04:18:06PM -0500, Louis-Philippe Véronneau wrote: > Hello from the Montreal BSP! > > I tested the latest release of the upstream version (0.2.36) and it > worked fine for me on the latest Thunderbird in testing. > > I migrated the nostalgy VCS from the Alioth archive to

Bug#920027: ships headers in /usr/include/python3.7/

Hi, > your package ships the header file(s): FYI this will be explicitly detected and reported on in lintian 2.5.123 in the package-contains-python-header-in-incorrect- directory tag. Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org  chris-lamb.co.uk

Bug#919971: node-rollup-pluginutils: autopkgtestsuite failure

Hi, I had not updated this package precisely because I couldn't get the autopkgtestsuite to run properly : https://github.com/rollup/rollup-pluginutils/issues/38 If you have a fix, that's a good news. I might have the time to have a look in two days ; if you're in a hurry, it's team

Bug#900299: leiningen-clojure: depends on openjdk-8

On 2019-01-21 14:49, Moritz Mühlenhoff wrote: We can only support one OpenJDK relase in a stable release and that version will be openjdk-11. I'm bumping the severity back to serious. Cheers, Moritz So here's the issue with Leiningen and Java 11. We previously tracked down some

Bug#917884: It might be a missing dependency

On Sat, Jan 19, 2019 at 10:19:34AM -0500, John Scott wrote: > Hello. > > I'm not the maintainer, but I replied to your bug report [1] and noticed that > I forgot to CC you by mistake. I'm including what I'd sent. Hi John, thank you for sending me the e-mail directly, not only I forgot to

Bug#912324: BleachBit causing error since updating Firefox to Firefox Quantum 60.0 ESR

severity 912324 important thanks Hi, Personal issues took me away from Debian these last weeks, I could not take care of this issue sooner. This is bad. I have lowered the severity to important, but unless the release team agrees to make an exception bleachbit will not be available in Buster

Bug#920046: ruby-diaspora-federation: build-depends on ruby-faraday (< 0.10~)

Package: src:ruby-diaspora-federation Version: 0.1.4-2 Severity: serious Tags: ftbfs Usertags: edos-uninstallable ruby-diaspora-federation build-depends on ruby-faraday (<< 0.10~). The version of ruby-faraday in sid is, however, 0.13.1-2. -Ralf.

Bug#916468: whitedune: diff for NMU version 0.30.10-2.2

Control: tags -1 pending Hi, Pending the discussion in bug 919951 [1] I canceled my NMU. Depending on the outcome and if nothing has happened in this bug by the whitedune maintainers, I'll re-upload with the fix for the man-page included. Paul [1] https://bugs.debian.org/919951

Processed: Re: whitedune: diff for NMU version 0.30.10-2.2

Processing control commands: > tags -1 pending Bug #916468 [whitedune] dune: /usr/bin/dune is already provided by the whitedune package Ignoring request to alter tags of bug #916468 to the same tags previously set -- 916468: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916468 Debian Bug

Bug#920045: ntopng FTBFS with new ndpi

package: ntomng version: 2.4+dfsg1-4 severity: serious ntopng fails to build from source with the new ndpi, which recently migrated to testing. This affects both the version in buster (as evidenced by the raspbian binnmu

Bug#919006: FTBFS: test failure with new DBD::SQLite

On Mon, 21 Jan 2019 21:28:43 +0200, Niko Tyni wrote: > Looks like type_info() now returns more than it used to: with the older > libdbd-sqlite3-perl it gave just 'undef', but now it gives (somewhat > unhelpful) > > $VAR1 = { > 'CASE_SENSITIVE' => undef, > 'MAXIMUM_SCALE' =>

Bug#919591: marked as done (libwin32-exe-perl: Incomplete debian/copyright?)

Your message dated Mon, 21 Jan 2019 19:49:05 + with message-id and subject line Bug#919591: fixed in libwin32-exe-perl 0.17-2 has caused the Debian Bug report #919591, regarding libwin32-exe-perl: Incomplete debian/copyright? to be marked as done. This means that you claim that the problem

Processed: Re: Bug#900299: leiningen-clojure: depends on openjdk-8

Processing commands for cont...@bugs.debian.org: > severity 900299 serious Bug #900299 [src:leiningen-clojure] leiningen-clojure: depends on openjdk-8 Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 900299:

Bug#919805: redmine: FTBFS (Could not find gem mail)

Dear maintainer, I have solved this issue by running the command: gem install mail -v 2.6.4 I think this is the only thing missing in order to install redmine successfully on Buster. Best regards, Jonathan Boilesen -- © 2018 Boilesen Associates. Todos os direitos

Bug#920037: Don't include in buster

Source: openjdk-8 Severity: serious The default Java version in buster is openjdk-11 and there's only a handful of packages still depending on -8, don't include it in buster (which would double the effort for security updates in stable). Cheers, Moritz

Bug#919006: FTBFS: test failure with new DBD::SQLite

Control: tag -1 patch On Fri, Jan 11, 2019 at 05:37:52PM +0100, gregor herrmann wrote: > Source: libclass-dbi-plugin-type-perl > Version: 0.02-8 > Severity: serious > Tags: upstream buster sid ftbfs > Justification: fails to build from source > Forwarded:

Processed: Re: Bug#919006: FTBFS: test failure with new DBD::SQLite

Processing control commands: > tag -1 patch Bug #919006 [src:libclass-dbi-plugin-type-perl] FTBFS: test failure with new DBD::SQLite Added tag(s) patch. -- 919006: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919006 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#884243: djmount status, two patches and about conversion to libupnp 1.8

Hello, On 12/16/18 10:06 PM, Uwe Kleine-König wrote: > On Wed, May 23, 2018 at 05:31:08PM +0200, Dario Minnucci wrote: >> Sorry for the delay and thanks to invest time on this issue. >> >> On 18/05/18 23:30, Uwe Kleine-König wrote: >>> On Tue, Jan 09, 2018 at 09:17:35PM +0100, Rémi wrote:

Bug#917085: marked as done (pyzo: missing dependancy to python3-pkg-resources)

Your message dated Mon, 21 Jan 2019 18:49:50 + with message-id and subject line Bug#917085: fixed in pyzo 4.4.3-1.2 has caused the Debian Bug report #917085, regarding pyzo: missing dependancy to python3-pkg-resources to be marked as done. This means that you claim that the problem has been

Bug#919829: libatteanx-store-sparql-perl: FTBFS (failing tests)

On Sun, Jan 20, 2019 at 12:19:21AM +, Santiago Vila wrote: > Package: src:libatteanx-store-sparql-perl > Version: 0.010-1 > Severity: serious > Tags: ftbfs > Test Summary Report > --- > t/plan.t (Wstat: 65280 Tests: 0 Failed: 0) > Non-zero exit status: 255 > Parse

Processed: tagging 919773

Processing commands for cont...@bugs.debian.org: > tags 919773 - pending Bug #919773 [src:libdbd-sqlite3-perl] libdbd-sqlite3-perl FTBFS on mips: test failure Removed tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 919773:

Processed: tagging 919773

Processing commands for cont...@bugs.debian.org: > tags 919773 + upstream Bug #919773 [src:libdbd-sqlite3-perl] libdbd-sqlite3-perl FTBFS on mips: test failure Added tag(s) upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 919773:

Bug#916702: Merge request

Upstream upgrade available as a merge request. https://salsa.debian.org/debian/python-freezegun/merge_requests

Bug#909996: marked as done (vdirsyncer: FTBFS (TypeError: 'NoneType' object is not iterable))

Your message dated Mon, 21 Jan 2019 18:21:52 + with message-id and subject line Bug#909996: fixed in vdirsyncer 0.16.7-1 has caused the Debian Bug report #909996, regarding vdirsyncer: FTBFS (TypeError: 'NoneType' object is not iterable) to be marked as done. This means that you claim that

Bug#920030: python3-pygame: ships headers in /usr/include/python3.7/

Package: python3-pygame Version: 1.9.4.post1+dfsg-2 Severity: serious Hi, your package ships the header file(s): /usr/include/python3.7/pygame/_camera.h /usr/include/python3.7/pygame/_pygame.h /usr/include/python3.7/pygame/_surface.h /usr/include/python3.7/pygame/bitmask.h

Bug#920029: python3-zope.proxy: ships header in /usr/include/python3.7/

Package: python3-zope.proxy Version: 4.2.0-1 Severity: serious Hi, your package ships the header file(s): /usr/include/python3.7/zope.proxy/proxy.h but /usr/include/python3.7 is a symlink to python3.7m in libpython3.7-dev. This may result in silent file overwrites or depending on the

Bug#920028: python3-bsddb3: ships header in /usr/include/python3.7/

Package: python3-bsddb3 Version: 6.2.6-2 Severity: serious Hi, your package ships the header file(s): /usr/include/python3.7/bsddb3/bsddb.h but /usr/include/python3.7 is a symlink to python3.7m in libpython3.7-dev. This may result in silent file overwrites or depending on the unpacking order

Bug#920027: python3-persistent: ships headers in /usr/include/python3.7/

Package: python3-persistent Version: 4.2.2-1 Severity: serious Hi, your package ships the header file(s): /usr/include/python3.7/persistent/cPersistence.h /usr/include/python3.7/persistent/ring.h but /usr/include/python3.7 is a symlink to python3.7m in libpython3.7-dev. This may result in

Processed: reassign 832491 to src:aboot

Processing commands for cont...@bugs.debian.org: > reassign 832491 src:aboot Bug #832491 [aboot] aboot: please remove build dependency on obsolete package sp Bug reassigned from package 'aboot' to 'src:aboot'. No longer marked as found in versions 1.0~pre20040408-4. Ignoring request to alter

Bug#920026: python-greenlet-dev: ships header in /usr/include/python3.7/

Package: python-greenlet-dev Version: 0.4.15-1 Severity: serious Hi, your package ships the header file(s): /usr/include/python3.7/greenlet/greenlet.h but /usr/include/python3.7 is a symlink to python3.7m in libpython3.7-dev. This may result in silent file overwrites or depending on the

Bug#919558: marked as done (node-get-value: autopkgtest regression)

Your message dated Mon, 21 Jan 2019 17:50:39 + with message-id and subject line Bug#920004: fixed in node-get-value 3.0.1+~3.0.1-1 has caused the Debian Bug report #920004, regarding node-get-value: autopkgtest regression to be marked as done. This means that you claim that the problem has

Bug#920004: marked as done (node-get-value: missing dependency on node-isobject)

Your message dated Mon, 21 Jan 2019 17:50:39 + with message-id and subject line Bug#920004: fixed in node-get-value 3.0.1+~3.0.1-1 has caused the Debian Bug report #920004, regarding node-get-value: missing dependency on node-isobject to be marked as done. This means that you claim that the

Processed: reassign 919558 to node-get-value, forcibly merging 920004 919558

Processing commands for cont...@bugs.debian.org: > reassign 919558 node-get-value Bug #919558 [src:node-get-value] node-get-value: autopkgtest regression Bug reassigned from package 'src:node-get-value' to 'node-get-value'. No longer marked as found in versions node-get-value/3.0.1-1. Ignoring

Processed: tagging 920004

Processing commands for cont...@bugs.debian.org: > tags 920004 + pending Bug #920004 [node-get-value] node-get-value: missing dependency on node-isobject Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 920004:

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

Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:svgpp > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org

Processed: [bts-link] source package src:libmail-chimp3-perl

Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:libmail-chimp3-perl > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user

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

Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:python-mne > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org

Processed: [bts-link] source package systemd

Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package systemd > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org

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

Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:libbiod > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org

Bug#915689: Fwd: Re: Bug#919893: package shouldn't exist

On maandag 21 januari 2019 17:13:42 CET Michael Stone wrote: > >Entropy generation for the creation of SSH keys as the netinstaller is > >mostly used in headless situations. > >https://github.com/debian-pi/raspbian-ua-netinst/issues/42 > > That functionality doesn't require the old package; will

Processed (with 1 error): Re: [Openjdk] Bug#920020: javadoc: The code being documented uses modules but the packages defined in … are in the unnamed module

Processing control commands: > tags -1 + important Unknown tag/s: important. Recognized are: patch wontfix moreinfo unreproducible help security upstream pending confirmed ipv6 lfs d-i l10n newcomer a11y ftbfs fixed-upstream fixed fixed-in-experimental sid experimental potato woody sarge

Bug#920020: [Openjdk] Bug#920020: javadoc: The code being documented uses modules but the packages defined in … are in the unnamed module

Control: tags -1 + important On 21.01.19 17:42, Thorsten Glaser wrote: > Package: openjdk-11-jdk > Version: 11.0.2+7-1 > Severity: grave > Justification: renders package unusable no, why are you exaggerating? Both the jre and the jdk are usable. > [ERROR] Failed to execute goal >

Bug#880393: nmuing cyrus-sasl2

Hi all, I spent a half-day hacking cyrus-sasl2 and I uploaded 2.1.27 to experimental. I would appreciate if more people can test the package (I won’t have time until tomorrow or next week). I didn’t even had a chance to test it myself, so even the basic it installs and nothing breaks horribly

Processed: Fwd: Bug#919966: akregator: symbol lookup error: /usr/lib/x86_64-linux-gnu/libKF5NewStuff.so.5: undefined symbol: _ZN7KNSCore6Engine15signalErrorCodeERKNS_9ErrorCodeERK7QStringRK8QVariant

Processing commands for cont...@bugs.debian.org: > reassign 919966 libkf5newstuff5 5.54.0-1 Bug #919966 [libkf5newstuff5] akregator: symbol lookup error: /usr/lib/x86_64-linux-gnu/libKF5NewStuff.so.5: undefined symbol: _ZN7KNSCore6Engine15signalErrorCodeERKNS_9ErrorCodeERK7QStringRK8QVariant

Bug#920020: javadoc: The code being documented uses modules but the packages defined in … are in the unnamed module

Package: openjdk-11-jdk Version: 11.0.2+7-1 Severity: grave Tags: patch Justification: renders package unusable [ERROR] Failed to execute goal org.apache.maven.plugins:maven-javadoc-plugin:3.0.1:jar (attach-javadocs) on project octopus-rpctunnel: MavenReportException: Error while generating

Processed: reassign 919966 to libkf5newstuff5

Processing commands for cont...@bugs.debian.org: > reassign 919966 libkf5newstuff5 Bug #919966 [akregator] akregator: symbol lookup error: /usr/lib/x86_64-linux-gnu/libKF5NewStuff.so.5: undefined symbol: _ZN7KNSCore6Engine15signalErrorCodeERKNS_9ErrorCodeERK7QStringRK8QVariant Bug reassigned

Processed (with 1 error): merging 919966 919765

Processing commands for cont...@bugs.debian.org: > merge 919966 919765 Bug #919966 [akregator] akregator: symbol lookup error: /usr/lib/x86_64-linux-gnu/libKF5NewStuff.so.5: undefined symbol: _ZN7KNSCore6Engine15signalErrorCodeERKNS_9ErrorCodeERK7QStringRK8QVariant Unable to merge bugs because:

Bug#880393: marked as done (libsasl2-modules-gssapi-heimdal seems built against MIT)

Your message dated Mon, 21 Jan 2019 16:34:43 + with message-id and subject line Bug#880393: fixed in cyrus-sasl2 2.1.27+dfsg-1~exp1 has caused the Debian Bug report #880393, regarding libsasl2-modules-gssapi-heimdal seems built against MIT to be marked as done. This means that you claim that

Bug#919794: marked as done (python3-sbml5-doc: missing Breaks+Replaces: libsbml5-python-doc)

Your message dated Mon, 21 Jan 2019 16:35:18 + with message-id and subject line Bug#919794: fixed in libsbml 5.17.2+dfsg-2 has caused the Debian Bug report #919794, regarding python3-sbml5-doc: missing Breaks+Replaces: libsbml5-python-doc to be marked as done. This means that you claim that

Bug#919356: Fw: Bug#919356: dwarves-dfsg: Copyright/licensing is unclear

Missed the bug off the CC for this. Sorry. Begin forwarded message: Date: Mon, 21 Jan 2019 13:34:13 + From: MJ Ray To: debian-le...@lists.debian.org Subject: Re: Bug#919356: dwarves-dfsg: Copyright/licensing is unclear Domenico Andreoli skribis: > the situation of dwarves-dfsg

Processed: severity of 919966 is grave

Processing commands for cont...@bugs.debian.org: > severity 919966 grave Bug #919966 [akregator] akregator: symbol lookup error: /usr/lib/x86_64-linux-gnu/libKF5NewStuff.so.5: undefined symbol: _ZN7KNSCore6Engine15signalErrorCodeERKNS_9ErrorCodeERK7QStringRK8QVariant Ignoring request to change

Bug#919529: CVE-2019-6256

Hi, On Sun, Jan 20, 2019 at 03:22:31PM +0100, Sebastian Ramacher wrote: > On 2019-01-19 22:36:05, Salvatore Bonaccorso wrote: > > Hey! > > > > On Thu, Jan 17, 2019 at 12:00:13AM +0100, Sebastian Ramacher wrote: > > > Control: found -1 2016.11.28-1 > > > > > > On 2019-01-16 23:19:45, Moritz

Processed (with 1 error): Re: Bug#919966: akregator: symbol lookup error: /usr/lib/x86_64-linux-gnu/libKF5NewStuff.so.5: undefined symbol: _ZN7KNSCore6Engine15signalErrorCodeERKNS_9ErrorCodeERK7QStrin

Processing commands for cont...@bugs.debian.org: > forcemerge 919765 919966 Bug #919765 {Done: steve } [libkf5newstuff5] Multiple applications: symbol lookup error: libKF5NewStuff.so.5: undefined symbol Unable to merge bugs because: package of #919966 is 'akregator' not 'libkf5newstuff5' Failed

Bug#919966: akregator: symbol lookup error: /usr/lib/x86_64-linux-gnu/libKF5NewStuff.so.5: undefined symbol: _ZN7KNSCore6Engine15signalErrorCodeERKNS_9ErrorCodeERK7QStringRK8QVariant

On 2019-01-21 at 15:48:29, Bernhard Übelacker wrote: > this looks like a duplicate of bug: > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919765 Indeed. Thanks for that. -- https://fmarier.org/

Processed (with 1 error): merging 919966 919765

Processing commands for cont...@bugs.debian.org: > merge 919966 919765 Bug #919966 [akregator] akregator: symbol lookup error: /usr/lib/x86_64-linux-gnu/libKF5NewStuff.so.5: undefined symbol: _ZN7KNSCore6Engine15signalErrorCodeERKNS_9ErrorCodeERK7QStringRK8QVariant Unable to merge bugs because:

Bug#915689: Fwd: Re: Bug#919893: package shouldn't exist

On Mon, Jan 21, 2019 at 04:47:51PM +0100, Diederik de Haas wrote: On maandag 21 januari 2019 13:34:19 CET Michael Stone wrote: On Mon, Jan 21, 2019 at 01:15:13PM +0100, Diederik de Haas wrote: >On zondag 20 januari 2019 16:59:11 CET Thorsten Glaser wrote: >> I’m very much against just saying

Bug#919802: Fwd: Re: Bug#919802: libjstun-java: FTBFS (The code being documented uses packages in the unnamed module)

Hi Emmanuel, Niels, Any input on this topic? Thanks in advance, _g. Message transféré Sujet : Re: Bug#919802: libjstun-java: FTBFS (The code being documented uses packages in the unnamed module) Date : Mon, 21 Jan 2019 16:58:08 +0100 De : Gilles Filippini Pour :

Bug#919802: libjstun-java: FTBFS (The code being documented uses packages in the unnamed module)

Hi, On Sun, 20 Jan 2019 13:28:57 +0800 "Ying-Chun Liu (PaulLiu)" wrote: > Santiago Vila 於 2019/1/20 上午1:35 寫道: > > Package: src:libjstun-java > > Version: 0.7.3+dfsg-1 > > Severity: serious > > Tags: ftbfs > > > > Dear maintainer: > > > > I tried to build this package in buster but it failed:

  1   2   >