Bug#927016: marked as done (libnanoxml2-java: FTBFS (Unknown option: source 1.8 -nowarn))

2019-04-13 Thread Debian Bug Tracking System
Your message dated Sat, 13 Apr 2019 20:48:45 + with message-id and subject line Bug#927016: fixed in libnanoxml2-java 2.2.3.dfsg-7 has caused the Debian Bug report #927016, regarding libnanoxml2-java: FTBFS (Unknown option: source 1.8 -nowarn) to be marked as done. This means that you claim

libnanoxml2-java_2.2.3.dfsg-7_source.changes ACCEPTED into unstable

2019-04-13 Thread Debian FTP Masters
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 13 Apr 2019 22:31:41 +0200 Source: libnanoxml2-java Architecture: source Version: 2.2.3.dfsg-7 Distribution: unstable Urgency: medium Maintainer: Debian Java Maintainers Changed-By: Jochen Sprickerhof Closes:

Processing of libnanoxml2-java_2.2.3.dfsg-7_source.changes

2019-04-13 Thread Debian FTP Masters
libnanoxml2-java_2.2.3.dfsg-7_source.changes uploaded successfully to localhost along with the files: libnanoxml2-java_2.2.3.dfsg-7.dsc libnanoxml2-java_2.2.3.dfsg-7.debian.tar.xz libnanoxml2-java_2.2.3.dfsg-7_source.buildinfo Greetings, Your Debian queue daemon (running on host

Processed: Bug #927016 in libnanoxml2-java marked as pending

2019-04-13 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #927016 [src:libnanoxml2-java] libnanoxml2-java: FTBFS (Unknown option: source 1.8 -nowarn) Added tag(s) pending. -- 927016: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927016 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Bug#927016: libnanoxml2-java: FTBFS (Unknown option: source 1.8 -nowarn)

2019-04-13 Thread Santiago Vila
Package: src:libnanoxml2-java Version: 2.2.3.dfsg-6 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in buster but it failed: [...] debian/rules build-indep dh build-indep --with

Bug#888547: CVE-2017-1000190

2019-04-13 Thread Ivo De Decker
Hi, On Fri, Aug 24, 2018 at 01:18:09AM +0200, Emmanuel Bourg wrote: > On 23/08/2018 17:11, Markus Koschany wrote: > > > My concern is that we have an upstream project that does not even > > consider such a trivial fix. Then we have another example of a > > fire-and-forget one time upload