Processed: Bug#963443 marked as pending in apache-curator

Processing control commands: > tag -1 pending Bug #963443 [src:apache-curator] apache-curator: FTBFS: [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.8.1:compile (default-compile) on project curator-framework: Compilation failure: Compilation failure: Added

Processed: Bug#963385 marked as pending in airlift-airline

Processing control commands: > tag -1 pending Bug #963385 [src:airlift-airline] airlift-airline: FTBFS: [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.8.1:compile (default-compile) on project airline: Compilation failure Added tag(s) pending. -- 963385:

Bug#963385: marked as pending in airlift-airline

Control: tag -1 pending Hello, Bug #963385 in airlift-airline 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: severity of 804267 is serious

Processing commands for cont...@bugs.debian.org: > severity 804267 serious Bug #804267 [mercurial-crecord] mercurial-crecord: remove mercurial-crecord from the archive Severity set to 'serious' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. --

Processed: severity of 937009 is serious

Processing commands for cont...@bugs.debian.org: > severity 937009 serious Bug #937009 {Done: Sandro Tosi } [src:mercurial] mercurial: Python2 removal in sid/bullseye Ignoring request to change severity of Bug 937009 to the same value. > thanks Stopping processing here. Please contact me if you

Bug#964541: flatpak: Wrong argument order for clone syscall seccomp filter on s390x

On Wed, 05 Aug 2020 at 16:28:50 +0200, Julian Andres Klode wrote: > clone() is a mad syscall with about 4 different argument orders. While > most of them agree that argument 0 is flags, s390 and s390x have the > flags argument second - A0 is the child stack pointer there. It looks as though

Bug#954684: marked as done (ant-contrib: FTBFS: tests failed)

Your message dated Thu, 06 Aug 2020 09:48:36 + with message-id and subject line Bug#954684: fixed in ant-contrib 1.0~b3+svn177-12 has caused the Debian Bug report #954684, regarding ant-contrib: FTBFS: tests failed to be marked as done. This means that you claim that the problem has been

Bug#957622: marked as done (oasis3: ftbfs with GCC-10)

Your message dated Thu, 6 Aug 2020 10:41:38 +0100 with message-id <8bf644e3-2f05-eb8c-5559-124834730...@debian.org> and subject line Close has caused the Debian Bug report #957622, regarding oasis3: ftbfs with GCC-10 to be marked as done. This means that you claim that the problem has been dealt

Processed: Bug#954684 marked as pending in ant-contrib

Processing control commands: > tag -1 pending Bug #954684 [src:ant-contrib] ant-contrib: FTBFS: tests failed Added tag(s) pending. -- 954684: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954684 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#954684: marked as pending in ant-contrib

Control: tag -1 pending Hello, Bug #954684 in ant-contrib 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#963396: jimfs: FTBFS: [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.8.1:compile (default-compile) on project jimfs: Compilation failure

Control: tags -1 help Hi, I was running routine-update on jimfs repository since it seems to lack some love (not even Salsa URLs in VCS-fields) but the build error remains (for sure since I did not changed the code). I've checked upstream[1] which says: 1.1 @cgdecker released this on Feb

Processed: Re: jimfs: FTBFS: [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.8.1:compile (default-compile) on project jimfs: Compilation failure

Processing control commands: > tags -1 help Bug #963396 [src:jimfs] jimfs: FTBFS: [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.8.1:compile (default-compile) on project jimfs: Compilation failure Added tag(s) help. -- 963396:

Bug#966765: marked as done (obs-build: Unversioned Python removal in sid/bullseye)

Your message dated Thu, 06 Aug 2020 08:49:02 + with message-id and subject line Bug#966765: fixed in obs-build 20180831-4 has caused the Debian Bug report #966765, regarding obs-build: Unversioned Python removal in sid/bullseye to be marked as done. This means that you claim that the problem

Bug#963362: marked as pending in guice

Control: tag -1 pending Hello, Bug #963362 in guice 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#963362 marked as pending in guice

Processing control commands: > tag -1 pending Bug #963362 [src:guice] guice: FTBFS: [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.8.1:compile (default-compile) on project guice-throwingproviders: Compilation failure Added tag(s) pending. -- 963362:

Processed: cloning 966765, retitle -1 to obs-build: update to the latest upstream version ...

Processing commands for cont...@bugs.debian.org: > clone 966765 -1 Bug #966765 [src:obs-build] obs-build: Unversioned Python removal in sid/bullseye Bug 966765 cloned as bug 967976 > retitle -1 obs-build: update to the latest upstream version Bug #967976 [src:obs-build] obs-build: Unversioned

Bug#966996: marked as done (python-cytoolz: FTBFS: dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2)

Your message dated Thu, 06 Aug 2020 07:48:29 + with message-id and subject line Bug#966996: fixed in python-cytoolz 0.10.1-2 has caused the Debian Bug report #966996, regarding python-cytoolz: FTBFS: dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2 to be marked as

Bug#966939: marked as done (fdb: FTBFS: dh_sphinxdoc: error: debian/python-fdb-doc/usr/share/doc/python-fdb-doc/html/search.html does not load searchindex.js)

Your message dated Thu, 6 Aug 2020 09:37:49 +0200 with message-id <20200806073749.GA321521@pisco.westfalen.local> and subject line Re: fdb: FTBFS: dh_sphinxdoc: error: debian/python-fdb-doc/usr/share/doc/python-fdb-doc/html/search.html does not load searchindex.js has caused the Debian Bug

Bug#957806: marked as done (skypat: ftbfs with GCC-10)

Your message dated Thu, 06 Aug 2020 07:33:34 + with message-id and subject line Bug#957806: fixed in skypat 3.1.1-4 has caused the Debian Bug report #957806, regarding skypat: ftbfs with GCC-10 to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#967964: marked as done (unison-2.48: file conflict with unison -4)

Your message dated Thu, 06 Aug 2020 07:33:41 + with message-id and subject line Bug#967964: fixed in unison-2.48 2.48.4-6 has caused the Debian Bug report #967964, regarding unison-2.48: file conflict with unison -4 to be marked as done. This means that you claim that the problem has been

Processed: Bug#967964 marked as pending in unison

Processing control commands: > tag -1 pending Bug #967964 [unison-2.48] unison-2.48: file conflict with unison -4 Added tag(s) pending. -- 967964: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967964 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#967964: marked as pending in unison

Control: tag -1 pending Hello, Bug #967964 in unison 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#936873: libhdate: diff for NMU version 1.6.02-2.1

On 2020-08-06 02:13, Lior Kaplan wrote: >We're still alive/here Excellent to hear! >and any help is much appreciated Contact me (off this thread) with details of anything I can be of help. -- hkp://keys.gnupg.net CA45 09B5 5351 7C11 A9D1 7286 0036 9E45 1595 8BC0

Bug#966692: stunnel4: FTBFS because of test hang

On Thu, Aug 06, 2020 at 03:23:08AM +0200, Michał Mirosław wrote: > On Thu, Aug 06, 2020 at 03:10:55AM +0200, Michał Mirosław wrote: > > On Thu, Aug 06, 2020 at 02:39:42AM +0200, Michał Mirosław wrote: > > > On Thu, Aug 06, 2020 at 03:16:35AM +0300, Peter Pentchev wrote: > > > > On Thu, Aug 06,

<    1   2