xarclock_1.0-19_source.changes uploaded successfully to localhost
along with the files:
xarclock_1.0-19.dsc
xarclock_1.0-19.debian.tar.xz
xarclock_1.0-19_source.buildinfo
Greetings,
Your Debian queue daemon (running on host usper.debian.org)
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sun, 15 May 2022 08:53:03 +0200
Source: xarclock
Architecture: source
Version: 1.0-19
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group
Changed-By: Pino Toscano
Changes:
xarclock (1.0-19) unstable;
Processing commands for cont...@bugs.debian.org:
> tags 999720 + experimental
Bug #999720 {Done: Mohammed Bilal }
[src:ruby-omniauth-oauth] ruby-omniauth-oauth: FTBFS with ruby-omniauth 2.0.x:
ERROR: Test "ruby2.7" failed:
/usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1404:in `rescue in b
sendmail_8.17.1-2_source.changes uploaded successfully to localhost
along with the files:
sendmail_8.17.1-2.dsc
sendmail_8.17.1-2.debian.tar.xz
sendmail_8.17.1-2_source.buildinfo
Greetings,
Your Debian queue daemon (running on host usper.debian.org)
Your message dated Sun, 15 May 2022 14:58:55 +
with message-id
and subject line Bug#1006574: fixed in sendmail 8.17.1-2
has caused the Debian Bug report #1006574,
regarding sendmail: FTBFS with OpenSSL 3.0
to be marked as done.
This means that you claim that the problem has been dealt with.
I
Your message dated Sun, 15 May 2022 14:58:55 +
with message-id
and subject line Bug#1009078: fixed in sendmail 8.17.1-2
has caused the Debian Bug report #1009078,
regarding sasl auth via saslauthd does not work anymore
to be marked as done.
This means that you claim that the problem has been
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Sun, 15 May 2022 16:14:12 +0200
Source: sendmail
Architecture: source
Version: 8.17.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group
Changed-By: Andreas Beckmann
Closes: 1006574 1009078
Changes:
wbox_5-3_source.changes uploaded successfully to localhost
along with the files:
wbox_5-3.dsc
wbox_5-3.debian.tar.xz
wbox_5-3_source.buildinfo
Greetings,
Your Debian queue daemon (running on host usper.debian.org)
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sat, 07 May 2022 22:50:48 -0300
Source: wbox
Architecture: source
Version: 5-3
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group
Changed-By: Marcos Talau
Changes:
wbox (5-3) unstable; urgency=medium
Control: notfound 997434 2.9.1.4-4
On 2022-05-14, Vagrant Cascadian wrote:
> Version: 2.9.1.4-4
Given that the fixed version and the originally reported version are the
same... mark this as notfound in the original version. Hopefully that
actually works.
Seems like it was a transient toolchain i
Processing control commands:
> notfound 997434 2.9.1.4-4
Bug #997434 {Done: Vagrant Cascadian } [src:xpaint] xpaint:
FTBFS: -q: invalid option -- '.'
No longer marked as found in versions xpaint/2.9.1.4-4.
--
997434: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997434
Debian Bug Tracking S
Source: fusesmb
Severity: normal
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: buildpath
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org
The build path is embedded in various binaries such as /usr/bin/fusesmb
and /usr/bin/fusesmb.cache:
https://tests.reproduci
Source: mailfront
Severity: normal
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: buildpath
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org
The build path is triggers different buildid in /usr/lib/mailfront/*.so:
https://tests.reproducible-builds.org/debian/rb-
Your message dated Sun, 15 May 2022 22:49:21 +
with message-id
and subject line Bug#1011036: fixed in mailfront 2.12-2
has caused the Debian Bug report #1011036,
regarding mailfront: reproducible-builds: build path triggers differing buildid
to be marked as done.
This means that you claim tha
mailfront_2.12-2_source.changes uploaded successfully to localhost
along with the files:
mailfront_2.12-2.dsc
mailfront_2.12-2.debian.tar.xz
Greetings,
Your Debian queue daemon (running on host usper.debian.org)
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sun, 15 May 2022 15:26:58 -0700
Source: mailfront
Architecture: source
Version: 2.12-2
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group
Changed-By: Vagrant Cascadian
Closes: 1011036
Changes:
mailfr
fusesmb_0.8.7-3_source.changes uploaded successfully to localhost
along with the files:
fusesmb_0.8.7-3.dsc
fusesmb_0.8.7-3.debian.tar.xz
Greetings,
Your Debian queue daemon (running on host usper.debian.org)
Your message dated Mon, 16 May 2022 00:59:22 +
with message-id
and subject line Bug#1011034: fixed in fusesmb 0.8.7-3
has caused the Debian Bug report #1011034,
regarding fusesmb: reproducible-builds: embedded build paths in various binaries
to be marked as done.
This means that you claim tha
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sun, 15 May 2022 17:15:20 -0700
Source: fusesmb
Architecture: source
Version: 0.8.7-3
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group
Changed-By: Vagrant Cascadian
Closes: 1011034
Changes:
fusesmb
Source: libica
Version: 3.2.0-4
Severity: serious
Tags: ftbfs bookworm sid
https://buildd.debian.org/status/fetch.php?pkg=libica&arch=s390x&ver=3.2.0-4%2Bb1&stamp=1652517971&raw=0
...
libica_keygen_test.c: In function ‘main’:
libica_keygen_test.c:228:21: warning: implicit declaration of function
20 matches
Mail list logo
