Processed: guile-2.2: guile oom test fails on amd64

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #966301 [src:guile-2.2] guile oom test fails on ppc64el
Severity set to 'serious' from 'important'

-- 
966301: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966301
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: tagging 974828

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 974828 + help
Bug #974828 [printer-driver-hpcups] printer-driver-hpcups: SIGABRT with 
"free(): invalid next size (normal)" in HPCupsFilter::cleanup
Added tag(s) help.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
974828: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974828
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#982838: RoM: win32-loader must not migrate automatically

[Didier 'OdyX' Raboud]

Source: win32-loader
Version: 0.10.5
Severity: serious
X-Debbugs-Cc: debian-b...@lists.debian.org, debian-rele...@lists.debian.org

win32-loader is one of the rare packages always blocked, because it has a
'byhand' counterpart per release: `/debian/tools/win32-loader/{release}`, and
therefore needs a manual action by FTP masters in sync ("around the time of")
with the unblock.

This bug exists to manually block any src:win32-loader migration without a
manual sync from FTP masters.

It'll be updated to be marked "found" in the latest version, and "notfound"
in any version allowed to migrate.

Best, for the win32-loader maintainers,
  OdyX

Processed: severity of 977542 is serious

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 977542 serious
Bug #977542 [golang-github-revel-revel] golang-github-revel-revel: Depends on 
network in tests
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
977542: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977542
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#982719: firehol: FTBFS: dh_auto_test: error: make -j1 check VERBOSE=1 returned exit code 2

[Dennis Filder]

I think since all tests depend on the newns tool working, you have to
disable the entire test suite (I attached a proposal patch, but didn't
test it) and then test it.  But you should still get confirmation from
someone more knowledgable in this that what I wrote here is actually
correct and that disabling the test suite is the proper way (IIRC test
suites should be disabled only as a last resort, but I could be wrong
here).

Regards,
Dennis.

P.S.: I noticed that you didn't include me nor Lucas in To: or Cc:.
Remember: messages to 982...@bugs.debian.org are only sent to
maintainers (you) and people who actively subscribe (rarely done), so
you need to explicitly add others with To: or use X-Debbugs-CC:
(preferred) to reach them reliably.  Not everyone checks bug web
pages, esp. release team members as they deal with /a lot/ of bugs.
Read up on X-Debbugs-CC: if you haven't used it in a while.


firehol-nocheck.patch.gz
Description: application/gzip

Bug#959846: marked as done (manpages-de: missing Breaks+Replaces: manpages-de-dev (<< 4))

[Debian Bug Tracking System]

Your message dated Mon, 15 Feb 2021 08:48:43 +0200
with message-id 
and subject line Re: manpages-de: missing Breaks+Replaces: manpages-de-dev (<< 
4)
has caused the Debian Bug report #959846,
regarding manpages-de: missing Breaks+Replaces: manpages-de-dev (<< 4)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
959846: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959846
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: manpages-de
Version: 4.0.0-3
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'buster'.
It installed fine in 'buster', then the upgrade to 'bullseye' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces

>From the attached log (scroll to the bottom...):

  Preparing to unpack .../manpages-de_4.0.0-3_all.deb ...
  Unpacking manpages-de (4.0.0-3) ...
  dpkg: error processing archive 
/var/cache/apt/archives/manpages-de_4.0.0-3_all.deb (--unpack):
   trying to overwrite '/usr/share/man/de/man4/console_ioctl.4.gz', which is 
also in package manpages-de-dev 2.12-1
  Errors were encountered while processing:
   /var/cache/apt/archives/manpages-de_4.0.0-3_all.deb


cheers,

Andreas


manpages-de-dev=2.12-1_manpages-de=4.0.0-3.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Version: 4.9.1-2

Hi,

It seems that Breaks+Replaces: manpages-de-dev (<< 4) was added in 4.9.1-2.

--
Juhani Numminen--- End Message ---

Bug#982435: [screen-devel] [bug #60030] Screen segfaults by displaying some UTF-8 character combination

[Axel Beckert]

Hi Utkarsh,

Utkarsh Gupta wrote:
> On Sun, Feb 14, 2021 at 9:03 PM Axel Beckert  wrote:
> > > Since it's been ~3 days, do you think now would be the time to prepare
> > > and upload to buster and stretch?
> >
> > While I prepared the uploads in git, I haven't yet tested them on
> > Stretch and Buster. Currently still running the patch from 4.8.0-4,
> > mostly due to time contraints and an RC bug in aptitude.
> >
> > If you want some more coverage, I'd wait until Monday evening or
> > Tuesday. I hope to get the equivalent of the 4.8.0-5 patch installed
> > on Stretch and Buster later this evening.
> 
> That sounds good! Meanwhile, I'll compare the debdiff (for stretch)
> and try to prepare something similar for jessie as well!

Please slow down!

What so far was in git in the stretch and buster branches was
incomplete and did FTBFS for multiple reasons. (Just pushed a bunch of
fixes. It at least builds now on both releases.)

And in Stretch the patch didn't even apply properly and needed manual
massaging. So at least for Stretch (and Jessie) this needs additional
testing.

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE

Bug#978257: pynwb is marked for autoremoval from testing

[Yaroslav Halchenko]

failed to arrive with working minimal patch against that elderly 1.2.1

FWIW built current snapshot which seems to be ok.  but I am reluctant to
upload that one since it has breaking (we have no rev-depends though in
debian ATM) changes.

On Sun, 14 Feb 2021, Andreas Tille wrote:

> Hi Yaroslav,

> could you please have a look.  I'm occupied by many other things and will not
> care for this one.

> Kind regards
-- 
Yaroslav O. Halchenko
Center for Open Neuroscience http://centerforopenneuroscience.org
Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755
WWW:   http://www.linkedin.com/in/yarik

Bug#978257: pynwb is marked for autoremoval from testing

[Andreas Tille]

On Sun, Feb 14, 2021 at 11:38:35PM -0500, Yaroslav Halchenko wrote:
> failed to arrive with working minimal patch against that elderly 1.2.1
> 
> FWIW built current snapshot which seems to be ok.  but I am reluctant to
> upload that one since it has breaking (we have no rev-depends though in
> debian ATM) changes.

Its your package.  So you can decide better than I whether users are
served better with the snapshot or no package at all.

Kind regards

   Andreas. 

-- 
http://fam-tille.de

Bug#980967: marked as done (bats breaks ruby-build autopkgtest: /usr/libexec/bats-core/bats-exec-file: line 194: bats-exec-test: command not found)

[Debian Bug Tracking System]

Your message dated Mon, 15 Feb 2021 04:48:19 +
with message-id 
and subject line Bug#980967: fixed in bats 1.2.1-2
has caused the Debian Bug report #980967,
regarding bats breaks ruby-build autopkgtest: 
/usr/libexec/bats-core/bats-exec-file: line 194: bats-exec-test: command not 
found
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
980967: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980967
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: bats
Control: found -1 bats/1.2.1-1
Severity: serious
Tags: sid bullseye
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: breaks
Control: affects -1 ruby-build

Dear maintainer(s),

With a recent upload of bats the autopkgtest of ruby-build fails in
testing when that autopkgtest is run with the binary packages of bats
from unstable. It passes when run with only packages from testing. In
tabular form:

   passfail
bats   from testing1.2.1-1
ruby-build from testing20200401-1
all others from testingfrom testing

I copied some of the output at the bottom of this report. It really
looks like bats functionality is broken.

Currently this regression is blocking the migration of bats to testing
[1]. Can you please investigate the situation and fix the problem?

More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation

Paul

[1] https://qa.debian.org/excuses.php?package=bats

https://ci.debian.net/data/autopkgtest/testing/amd64/r/ruby-build/9965546/log.gz

autopkgtest [06:12:14]: test command1: bats test/
autopkgtest [06:12:14]: test command1: [---
1..100
/usr/libexec/bats-core/bats-exec-file: line 194: bats-exec-test: command
not found
/usr/libexec/bats-core/bats-exec-file: line 194: bats-exec-test: command
not found
/usr/libexec/bats-core/bats-exec-file: line 194: bats-exec-test: command
not found
/usr/libexec/bats-core/bats-exec-file: line 194: bats-exec-test: command
not found
/usr/libexec/bats-core/bats-exec-file: line 194: bats-exec-test: command
not found
/usr/libexec/bats-core/bats-exec-file: line 194: bats-exec-test: command
not found
/usr/libexec/bats-core/bats-exec-file: line 194: bats-exec-test: command
not found
/usr/libexec/bats-core/bats-exec-file: line 194: bats-exec-test: command
not found
/usr/libexec/bats-core/bats-exec-file: line 194: bats-exec-test: command
not found
/usr/libexec/bats-core/bats-exec-file: line 194: bats-exec-test: command
not found
/usr/libexec/bats-core/bats-exec-file: line 194: bats-exec-test: command
not found
/usr/libexec/bats-core/bats-exec-file: line 194: bats-exec-test: command
not found
/usr/libexec/bats-core/bats-exec-file: line 194: bats-exec-test: command
not found
/usr/libexec/bats-core/bats-exec-file: line 194: bats-exec-test: command
not found
/usr/libexec/bats-core/bats-exec-file: line 194: bats-exec-test: command
not found
/usr/libexec/bats-core/bats-exec-file: line 194: bats-exec-test: command
not found
/usr/libexec/bats-core/bats-exec-file: line 194: bats-exec-test: command
not found
/usr/libexec/bats-core/bats-exec-file: line 194: bats-exec-test: command
not found
/usr/libexec/bats-core/bats-exec-file: line 194: bats-exec-test: command
not found
/usr/libexec/bats-core/bats-exec-file: line 194: bats-exec-test: command
not found
/usr/libexec/bats-core/bats-exec-file: line 194: bats-exec-test: command
not found
/usr/libexec/bats-core/bats-exec-file: line 194: bats-exec-test: command
not found
/usr/libexec/bats-core/bats-exec-file: line 194: bats-exec-test: command
not found
/usr/libexec/bats-core/bats-exec-file: line 194: bats-exec-test: command
not found
/usr/libexec/bats-core/bats-exec-file: line 194: bats-exec-test: command
not found
/usr/libexec/bats-core/bats-exec-file: line 194: bats-exec-test: command
not found
/usr/libexec/bats-core/bats-exec-file: line 194: bats-exec-test: command
not found
/usr/libexec/bats-core/bats-exec-file: line 194: bats-exec-test: command
not found
/usr/libexec/bats-core/bats-exec-file: line 194: bats-exec-test: command
not found
/usr/libexec/bats-core/bats-exec-file: line 194: bats-exec-test: command
not found
/usr/libexec/bats-core/bats-exec-file: line 194: bats-exec-test: command
not found
/usr/libexec/bats-core/bats-exec-file: line 194: bats-exec-test: command
not found
/usr/libexec/bats-core/bats-exec-file: line 194: bats-exec-test: command
not found
/usr/libexec/bats-core/bats-exec-file: line 194: bats-exec-test: command

Bug#982825: netcfg: FTBFS with current bullseye version

[Holger Wansing]

Package: netcfg
Severity: critical
Version: 1.169

While trying to upload a new version of netcfg, I found that current testing
version of netcfg fails to build from source, in a stable sbuild environment
as well as in an unstable one.

The sbuild output (from a stable environment) is attached.

I assume this is not a problem in netcfg itself, however I feel somewhat 
helpless 
in finding the real course.


Holger

-- 
Holger Wansing 
PGP-Fingerprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076
sbuild (Debian sbuild) 0.78.1 (09 February 2019) on t520

+==+
| netcfg 1.169 (amd64) Sun, 14 Feb 2021 22:53:03 + |
+==+

Package: netcfg
Version: 1.169
Source Version: 1.169
Distribution: unstable
Machine Architecture: amd64
Host Architecture: amd64
Build Architecture: amd64
Build Type: full

I: NOTICE: Log filtering will replace 'var/run/schroot/mount/unstable-amd64-sbuild-b9f0d463-46de-4f19-92ab-2dfa5cf97d07' with '<>'
I: NOTICE: Log filtering will replace 'build/netcfg-WJf5nS/resolver-s1BpYp' with '<>'

+--+
| Update chroot|
+--+

Get:1 http://deb.debian.org/debian unstable InRelease [153 kB]
Get:2 http://deb.debian.org/debian unstable/main Sources.diff/Index [63.6 kB]
Get:3 http://deb.debian.org/debian unstable/main amd64 Packages.diff/Index [63.6 kB]
Get:4 http://deb.debian.org/debian unstable/main Sources T-2021-02-14-2000.12-F-2021-02-14-2000.12.pdiff [19.6 kB]
Get:4 http://deb.debian.org/debian unstable/main Sources T-2021-02-14-2000.12-F-2021-02-14-2000.12.pdiff [19.6 kB]
Get:5 http://deb.debian.org/debian unstable/main amd64 Packages T-2021-02-14-2000.12-F-2021-02-14-2000.12.pdiff [34.7 kB]
Get:5 http://deb.debian.org/debian unstable/main amd64 Packages T-2021-02-14-2000.12-F-2021-02-14-2000.12.pdiff [34.7 kB]
Fetched 335 kB in 5s (69.7 kB/s)
Reading package lists...
Reading package lists...
Building dependency tree...
Reading state information...
Calculating upgrade...
The following packages will be upgraded:
  libgcrypt20
1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 563 kB of archives.
After this operation, 1024 B of additional disk space will be used.
Get:1 http://deb.debian.org/debian unstable/main amd64 libgcrypt20 amd64 1.8.7-3 [563 kB]
debconf: delaying package configuration, since apt-utils is not installed
Fetched 563 kB in 0s (2381 kB/s)
(Reading database ... 
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 15717 files and directories currently installed.)
Preparing to unpack .../libgcrypt20_1.8.7-3_amd64.deb ...
Unpacking libgcrypt20:amd64 (1.8.7-3) over (1.8.7-2) ...
Setting up libgcrypt20:amd64 (1.8.7-3) ...
Processing triggers for libc-bin (2.31-9) ...

+--+
| Fetch source files   |
+--+


Local sources
-

/home/holgerw/test/netcfg-1.169/netcfg_1.169.dsc exists in /home/holgerw/test/netcfg-1.169; copying to chroot
I: NOTICE: Log filtering will replace 'build/netcfg-WJf5nS/netcfg-1.169' with '<>'
I: NOTICE: Log filtering will replace 'build/netcfg-WJf5nS' with '<>'

+--+
| Install package build dependencies   |
+--+


Setup apt archive
-

Merged Build-Depends: debhelper (>= 9), dpkg-dev (>= 1.16.1~), libdebconfclient0-dev (>= 0.46), libdebian-installer4-dev (>= 0.41), po-debconf (>= 0.5.0), libiw-dev (>= 27+28pre9), check, libsubunit-dev, build-essential, fakeroot
Filtered Build-Depends: debhelper (>= 9), dpkg-dev (>= 1.16.1~), libdebconfclient0-dev (>= 0.46), libdebian-installer4-dev (>= 0.41), po-debconf (>= 0.5.0), libiw-dev (>= 27+28pre9), check, libsubunit-dev, build-essential, fakeroot
dpkg-deb: building package 'sbuild-build-depends-main-dummy' in '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'.
Ign:1 copy:/<>/apt_archive ./ InRelease
Get:2 

Bug#982253: netkit telnetd: ship with bullseye with open security problems?

[Chris Hofstaedtler]

* Andreas Henriksson  [210215 01:29]:
> On Sun, Feb 07, 2021 at 09:06:28PM +0100, Salvatore Bonaccorso wrote:
> It's not like inetutils is a shining example of perfectness either.
> 
> #945861 inetutils: CVE-2019-0053
> 
> The inetutils also doesn't ship all tools and recommends
> using existing ones including netkit (eg. in #672295).
[..]

> > > 1) open bug #974428, causes telnetd to crash, remotely triggerable
> > 
> > The first issue, if there a verified patch might be good to fix in
> > time for bullseye.
> 
> I've pondered uploading the posted patch and since the last maintainer
> upload was in 2016 I'd orphan the package while doing so but I'll
> consider hijacking it on Christoph Biedl's behalf if he's interested
> in maintaining it still.
> 
> Unless there's a conclusion about this bug report I don't really see
> much point in proceeding though.

I was hoping someone would jump in here and say "I'm using a telnet
server in 2021, and want to maintain it". But... not happening
apparently.

Personally I would favor keeping netkit-telnet, but turning off
telnetd. As Salvatore said, this might have to wait for bookworm.

Maybe upload the patch now (closing both bugs), and I'll see if I
remember to remove telnetd for bookworm? :-)

Chris

Processed: Re: linux-image-5.10.0-2-amd64: HP EliteBook x360 1040 G6 crashing since 5.10.0-1

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #981365 [src:linux] linux-image-5.10.0-2-amd64: HP EliteBook x360 1040 G6 
crashing since 5.10.0-1
Severity set to 'important' from 'critical'

-- 
981365: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981365
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#981365: linux-image-5.10.0-2-amd64: HP EliteBook x360 1040 G6 crashing since 5.10.0-1

[Hideki Yamane]

Control: severity -1 important

On Fri, 29 Jan 2021 23:07:50 +0100 Cervinko  wrote:
> Justification: breaks the whole system

 No, it's not.


> i am using a thunderbolt docking station

 If it works without it, it's because docking station.
 Similarly I'm using EliteBook830 G5 with HP Thunderbolt Dock G2, and
 it works (its USB function is instability if it's unplugged and plugged again).

 Anyway, please try to update your EliteBook BIOS and also Thunderbolt docking
 station firmware.


-- 
Hideki Yamane 

Bug#982833: man2html,man2html-base,manpages-it: manpage conflicts: man2html.1, hman.1

[Andreas Beckmann]

Package: man2html,man2html-base,manpages-it
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: found -1 1.6g-14
Control: found -1 4.9.1-2

Hi,

during a test with piuparts I noticed your package failed to install
because it tries to overwrite other packages files.

>From the attached log (scroll to the bottom...):

  Preparing to unpack .../manpages-it_4.9.1-2_all.deb ...
  Unpacking manpages-it (4.9.1-2) ...
  dpkg: error processing archive 
/var/cache/apt/archives/manpages-it_4.9.1-2_all.deb (--unpack):
   trying to overwrite '/usr/share/man/it/man1/hman.1.gz', which is also in 
package man2html 1.6g-14
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/manpages-it_4.9.1-2_all.deb

  Preparing to unpack .../manpages-it_4.9.1-2_all.deb ...
  Unpacking manpages-it (4.9.1-2) ...
  dpkg: error processing archive 
/var/cache/apt/archives/manpages-it_4.9.1-2_all.deb (--unpack):
   trying to overwrite '/usr/share/man/it/man1/man2html.1.gz', which is also in 
package man2html-base 1.6g-14
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/manpages-it_4.9.1-2_all.deb


cheers,

Andreas


man2html=1.6g-14_manpages-it=4.9.1-2.log.gz
Description: application/gzip

Processed: man2html,man2html-base,manpages-it: manpage conflicts: man2html.1, hman.1

[Debian Bug Tracking System]

Processing control commands:

> found -1 1.6g-14
Bug #982833 [man2html,man2html-base,manpages-it] 
man2html,man2html-base,manpages-it: manpage conflicts: man2html.1, hman.1
There is no source info for the package 'manpages-it' at version '1.6g-14' with 
architecture ''
Marked as found in versions man2html/1.6g-14.
> found -1 4.9.1-2
Bug #982833 [man2html,man2html-base,manpages-it] 
man2html,man2html-base,manpages-it: manpage conflicts: man2html.1, hman.1
There is no source info for the package 'man2html' at version '4.9.1-2' with 
architecture ''
There is no source info for the package 'man2html-base' at version '4.9.1-2' 
with architecture ''
Marked as found in versions manpages-l10n/4.9.1-2.

-- 
982833: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982833
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#982705: openssh: FTBFS: sha2.h:57:16: error: redefinition of ‘struct _SHA2_CTX’

[Andreas Henriksson]

Hello Colin Watson,

On Sun, Feb 14, 2021 at 01:05:11PM +, Colin Watson wrote:
> Thanks for digging into this.
> 
> How about this approach instead?  Given the choice between a
> packaging-only change and one that requires another patch against
> upstream, I have a slight preference for the packaging-only change as
> long as it's basically reasonable, which I think this is.  It just
> overrides configure's automatic detection and tells it that sha2.h isn't
> available.  Builds cleanly and doesn't seem to incur any new direct
> dependencies.

Whatever works and feel free to choose the way you as maintainer
prefers as far as I'm concerned! :)

FWIW I make similar choices myself, but my definition of preferred
solution is a bit more complicated. Nothing is ever as permanent
as something temporary. It's not uncommon to see a temporary
hack be forgotten about and then not be dropped when it's 
no longer needed, just to come back later and bite you in the ass.
So while I agree with your rule in general, I go for patches when
there's a big chance that the patch will stop apply when upstream
fixes this. Then it's hard to miss that it should be dropped when
the package is updated the next time However there's no guarantee
that will happen with my patch, so it's really up to you to go
with your gut feeling.
And apart from that, my autotools knowledge simply isn't as good
as yours to come up with your solution (even though I definitely have
seen similar things used in the past now that you point it out).

> 
> diff --git a/debian/rules b/debian/rules
> index 73a53c309..44bac00f1 100755
> --- a/debian/rules
> +++ b/debian/rules
> @@ -65,6 +65,10 @@ ifeq ($(DEB_HOST_ARCH_OS),hurd)
>  confflags += --with-libs=-lcrypt
>  endif
>  
> +# Avoid using libmd even if it's installed; see
> +# https://bugs.debian.org/982705.
> +confflags += ac_cv_header_sha2_h=false
> +
>  # Everything above here is common to the deb and udeb builds.
>  confflags_udeb := $(confflags)
>  
> 
> Thanks,
> 
> -- 
> Colin Watson (he/him)  [cjwat...@debian.org]

Regards,
Andreas Henriksson

Bug#971129: shim-signed: FTBFS: build-dependency not installable: shim-unsigned (= 15+1533136590.3beb971-7)

[Steve McIntyre]

Hey Ivo,

On Sun, Feb 14, 2021 at 07:56:20PM +0100, Ivo De Decker wrote:
>On Fri, Feb 12, 2021 at 01:35:52AM +, Steve McIntyre wrote:
>> On Tue, Feb 09, 2021 at 04:26:02PM +0100, Ivo De Decker wrote:
>> >Hi Steve,
>> >
>> >On Sun, Sep 27, 2020 at 08:39:53PM +0200, Lucas Nussbaum wrote:
>> >> During a rebuild of all packages in sid, your package failed to build
>> >> on amd64.
>> >
>> >[...]
>> >
>> >> > The following packages have unmet dependencies:
>> >> >  sbuild-build-depends-main-dummy : Depends: shim-unsigned (= 
>> >> > 15+1533136590.3beb971-7) but it is not going to be installed
>> >
>> >What is the status of shim(-signed) for bullseye?
>> >
>> >shim-unsigned has been changed, but there is no corresponding shim-signed
>> >(yet). I assume a new signature from microsoft is needed. Or are there more
>> >changes to shim-unsigned needed first?
>> 
>> There are some other changes coming, not least switching compiler to
>> gcc-10 now we've stabilised.
>
>I'm tagging #978521 ("shim: non-standard gcc/g++ used for build (gcc-9)") as
>pending to indicate that you're planning to switch to gcc-10.

Thanks. Sorry, I forgot to do that myself.

>> I'm working on new shim uploads at the
>> moment, but there's a couple of upstream patches we'll need to take as
>> well yet I think. It'll be coming soon, I promise.
>
>Could you clarify the timing for this, especially the timeline for getting the
>signature from Microsoft (as far as that can be predicted)? I'm trying to
>assess if this could become a blocker wrt the actual release. Is it an option
>to release with the current version of shim-signed (ie the one that's also in
>buster) if we don't get the signature in time?

It's not really an option to release with the old shim at this point,
I'm afraid. But there are newer processes in place around getting new
builds signed, so I'm not worrying too much here about delaying the
release. I expect to have things sorted soon.

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
"This dress doesn't reverse." -- Alden Spiess

Bug#982253: netkit telnetd: ship with bullseye with open security problems?

[Andreas Henriksson]

Hello,

On Sun, Feb 07, 2021 at 09:06:28PM +0100, Salvatore Bonaccorso wrote:
[...]
> > 2) possibly unpatched exploit here: 
> > https://www.exploit-db.com/exploits/48170
> 
> JFTR, this one was CVE-2020-10188 and in Debian was fixed in earlier
> times.
> 
> Replacing telnetd package with an empy package and depending on
> inetutils-telnetd: is it possible to basically interchangably replace
> those two? If so this might be an option but I'm not sure if at this
> stage of the preparations for bullseye it might be too late.

It's not like inetutils is a shining example of perfectness either.

#945861 inetutils: CVE-2019-0053

The inetutils also doesn't ship all tools and recommends
using existing ones including netkit (eg. in #672295).

It also seems to lack features compared to netkit alternatives
(eg. SSL).

... "pest eller kolera" ...

It seems like Christoph Biedl who did the last NMU has considered
adopting the package. Hopefully if that happened the situation around
netkit could improve.

> 
> > 1) open bug #974428, causes telnetd to crash, remotely triggerable
> 
> The first issue, if there a verified patch might be good to fix in
> time for bullseye.

I've pondered uploading the posted patch and since the last maintainer
upload was in 2016 I'd orphan the package while doing so but I'll
consider hijacking it on Christoph Biedl's behalf if he's interested
in maintaining it still.

Unless there's a conclusion about this bug report I don't really see
much point in proceeding though.

Regards,
Andreas Henriksson

Bug#982830: golang-code.gitea-git: unmaintained go library - keep out of testing

[Chris Hofstaedtler]

Source: golang-code.gitea-git
Version: 0.0~git20190411.63b74d4+ds-1
Severity: serious

Upstream (Gitea) appears to have moved on to another solution, so
this is dead code (upstream repo is marked as archived).

Lets not have it in bullseye, especially as nothing else depends on
it, and its orphaned in Debian.

Chris

Bug#981847: ArgumentError: invalid byte sequence in US-ASCII

[Daniel Leidert]

Am Donnerstag, dem 04.02.2021 um 20:56 +0530 schrieb Ritesh Raj Sarraf:
> 
> During a rebuild of the package on Bullseye, the package fails in one of
> the tests. Below is the failure snippet. The same is also seen in the
> Reproducible Builds reports.
> 
> ```
> [  194s] 
> ---
> [  194s] 107 tests, 152 assertions, 0 failures, 1 errors, 0 pendings, 0 
> omissions, 0 notifications
> [  194s] 99.0654% passed
> [  194s] 
> ---
> [  194s] 23.20 tests/s, 32.95 assertions/s
> [  194s] rake aborted!
> [  194s] Command failed with status (1): [ruby -w -I"test"  
> "/usr/share/rubygems-integration/all/gems/rake-13.0.1/lib/rake/rake_test_loader.rb"
>  "test/block_test.rb" "test/dyna_symbol_key_test.rb" "test/parser_test.rb" 
> "test/safe_op_test.rb" "test/trace_test.rb" "test/test_core_ext_helper.rb" 
> "test/test_helper.rb" -v]
> [  194s] /usr/share/rubygems-integration/all/gems/rake-13.0.1/exe/rake:27:in 
> `'
> [  194s] Tasks: TOP => default
> [  194s] (See full trace by running task with --trace)
> [  194s] ERROR: Test "ruby2.7" failed. Exiting.
> [  194s] dh_auto_install: error: dh_ruby --install 
> /usr/src/packages/BUILD/debian/ruby-power-assert returned exit code 1
> [  194s] make: *** [debian/rules:6: binary] Error 25
> [  194s] dpkg-buildpackage: error: debian/rules binary subprocess returned 
> exit status 2
> ```

Can you please provide the log file? The error mentioned in the subject
actually doesn't appear in the log snippet.

Reading the subject it might be a LANG-related issue and maybe we need to set
the environment to C.UTF-8 for the tests. Can you check if setting

ENV['LANG'] = 'C.UTF-8'

in debian/ruby-tests.rake fixes the issue?

Regards, Daniel
-- 
Regards,
Daniel Leidert  | https://www.wgdd.de/
GPG-Key RSA4096 / BEED4DED5544A4C03E283DC74BCD0567C296D05D
GPG-Key ED25519 / BD3C132D8B3805D1808123AB7ACE00941E338C78

If you like my work consider sponsoring me via
https://www.patreon.com/join/dleidert


signature.asc
Description: This is a digitally signed message part

Bug#982825: netcfg: FTBFS with current bullseye version

[John Paul Adrian Glaubitz]

Hello Holger!

On 2/15/21 12:02 AM, Holger Wansing wrote:
> While trying to upload a new version of netcfg, I found that current testing
> version of netcfg fails to build from source, in a stable sbuild environment
> as well as in an unstable one.

Did you see #980607 [1]?

Adrian

> [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980607

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

Bug#930005: regina-rexx: rexxutil error

[Agustin Martin]

El vie, 12 feb 2021 a las 23:05, Alen Zekulic () escribió:
>
> On Fri, Feb 12, 2021 at 13:25:23 +0100, Agustin Martin wrote:
>
> > Alen, I plan to upload a NMU with this changes and may be some minor
> > issues. Even if I have not written rexx for years I think it would be
> > a pity to have this package with this open bug.
>
> I agree, please go ahead!

Uploaded.

> > Also, one issue with this package is that Debian build system is
> > ancient, even pre-debhelper. This makes everything a nightmare. I
> > have been playing with a migration to traditional (no dh sequencer)
> > debhelper. This should fix another bug report about build
> > reproduciibility. I am aware that this is a rather invasive change,
> > but I think is required to make contributors life easier, let me know
> > your POV.
>
> I planed to migrate my debian/rules to debhelper too.

When I was playing with this there were still some issues. Once I find
time to continue and consider things in good shape, I will let you
know. Another thing I think may be interesting is to split the a-z
patch into smaller chunks for better handling.

> > Other thing I noticed is that this package has no repo under
> > salsa. I can prepare a git repo with regina history and put it under
> > salsa/debian group. Alen, please tell me if you object to this, I
> > consider it important and will proceed unless you object explicitly.
>
> Any help is greatly appreciated, I have no objection, quite the
> contrary!

When I was creating the repo I noticed that there was already a repo
created under debian salsa group by Boyuan Yang, with commits for a
NMU that was never uploaded, so I used it. Reverted one thing, no need
to B-D on debhelper just to pull autotools-dev, debhelper is currently
unused.

> > By the way, upstream is active and there are new versions available,
> > although I will focus on current upstream version in Debian.
>
> Mark and I are in contact. We plan to roll out the latest releases of
> Regina REXX (3.9.4) and The Hessling Editor (3.3) as soon as possible.

Nice to know,

Regards,

-- 
Agustin

Bug#930005: marked as done (regina-rexx: rexxutil error)

[Debian Bug Tracking System]

Your message dated Sun, 14 Feb 2021 23:04:18 +
with message-id 
and subject line Bug#930005: fixed in regina-rexx 3.6-2.2
has caused the Debian Bug report #930005,
regarding regina-rexx: rexxutil error
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
930005: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930005
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: regina-rexx
Version: 3.6-2.1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

When try to run any of my programs that use RexxUtil, got an error,
so ran 

   $ regina /usr/share/doc/regina-rexx/examples/regutil.rexx

and received the error:
regina: symbol lookup error: /usr/lib/regina-rexx/3.6/libregutil.so:
undefined symbol: tgetent

which I've included in the attached file.

None of the scripts I've written to simplify my life which rely on
RexxUtil wil work without error until this is fixed.



-- System Information:
Debian Release: 9.9
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.9.0-9-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), LANGUAGE= 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages regina-rexx depends on:
ii  libc6   2.24-11+deb9u4
ii  libregina3  3.6-2.1

regina-rexx recommends no packages.

regina-rexx suggests no packages.

-- debconf-show failed
SysWINVer Linux #1 SMP Debian 4.9.168-1+deb9u2 (2019-05-13).4.9.0-9-amd64
SysUtilVersion 3.6
Press Enter key when ready . . .
regina: symbol lookup error: /usr/lib/regina-rexx/3.6/libregutil.so: undefined 
symbol: tgetent
--- End Message ---
--- Begin Message ---
Source: regina-rexx
Source-Version: 3.6-2.2
Done: Agustin Martin Domingo 

We believe that the bug you reported is fixed in the latest version of
regina-rexx, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 930...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Agustin Martin Domingo  (supplier of updated regina-rexx 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 14 Feb 2021 21:45:52 +0100
Source: regina-rexx
Architecture: source
Version: 3.6-2.2
Distribution: unstable
Urgency: medium
Maintainer: Alen Zekulic 
Changed-By: Agustin Martin Domingo 
Closes: 877603 930005
Changes:
 regina-rexx (3.6-2.2) unstable; urgency=medium
 .
   * Non-maintainer upload with maintaner agreement.
 .
   [ Boyuan Yang ]
   * debian/control:
 - Drop build-dependency on build-essential binutils (Closes: #877603).
 + Bump Standards-Version to 4.4.1.
 + Add git packaging repo under Salsa Debian group.
 .
   [ Andreas Beckmann ]
   * configure: Ensure the value of REGUTIL_TERM_LIB gets into the Makefile
 s.t. we actually link against the library providing tgetent().
 (Closes: #930005)
 .
   [ Agustin Martin ]
   * d/p/1000_regutil_termcap.h+HAVE_TGETENT.diff: Set HAVE_TGENT and load
 termcap.h if tgetent is available. This seems to fix a segfault
 appearing in amd64 when we actually link against the library providing
 tgetent in above #930005 fix.
   * Upgrade debian/watch file.
Checksums-Sha1:
 34b7ba85234dc2ba1f896d30286519de64f2107e 1977 regina-rexx_3.6-2.2.dsc
 1e638c539bad74113e77d08e527d7b3349666509 9960 regina-rexx_3.6-2.2.debian.tar.xz
 cdf29b1b5e658f90cc8beed870302e61cd0c9f71 5390 
regina-rexx_3.6-2.2_amd64.buildinfo
Checksums-Sha256:
 20c32f3e8759bfa33b9880e9415db2923a83f58f2439d7c6ec0f488543b0 1977 
regina-rexx_3.6-2.2.dsc
 ff1efe3224658fa24652b6e5471748bb5c844dad39c24bad6aa8a372a795ad14 9960 
regina-rexx_3.6-2.2.debian.tar.xz
 2b4f10b2dde02963256737676360e42dc17096d95b57bde2f37a08ba7686d54b 5390 
regina-rexx_3.6-2.2_amd64.buildinfo
Files:
 3be01361b0080e6b4a543fb6f12b1256 1977 libs optional regina-rexx_3.6-2.2.dsc
 7ec307943bab624f252e27704e36c58f 9960 libs optional 
regina-rexx_3.6-2.2.debian.tar.xz
 a6f9a4f9bc3e931986f244652bd27862 5390 libs optional 
regina-rexx_3.6-2.2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

Bug#982791: mit-scheme FTBFS on i386: out of memory

[Adrian Bunk]

On Sun, Feb 14, 2021 at 03:08:16PM +, Barak A. Pearlmutter wrote:
> Thanks for the report. I've been looking at the issue already.
> 
> Adding a new arch requires a bit of work, because there's a circular
> build dependency so you have to build manually. And I don't have an
> arm64 to hand, so I'll have to use a porter machine. Will get around
> to it.
>...

Yes, I saw that a manual bootstrap is necessary.

It's easier when the architecture is already in Architecture.

cu
Adrian

Bug#982786: growlight: autopkgtest regression

[Nick Black]

Thanks for the heads-up; glad I've got those autopkgtests. Looking into this 
now with the hope of fixing it ASAP.

Bug#982722: libatteanx-serializer-rdfa-perl: FTBFS: dh_auto_test: error: make -j1 test TEST_VERBOSE=1 returned exit code 2

[Kjetil Kjernsmo]

Hi!

Just to say as upstream that this patch seems appropriate.

I'll have a conversation with the author of one of the modules that I 
depend on to confirm, and then I'll probably apply it upstream and roll a 
new release. 

Best,

Kjetil

Bug#979838: marked as done (twisted: autopkgtest regression in testing: No such file or directory: 'ckeygen')

[Debian Bug Tracking System]

Your message dated Sun, 14 Feb 2021 22:06:07 +
with message-id 
and subject line Bug#979838: fixed in twisted 20.3.0-4
has caused the Debian Bug report #979838,
regarding twisted: autopkgtest regression in testing: No such file or 
directory: 'ckeygen'
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
979838: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979838
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: twisted
Version: 18.9.0-3
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

With a not so recent change (March 2019) in testing the autopkgtest of
your package started to fail. I copied some of the output at the bottom
of this report. Can you please investigate the situation and fix it?

More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation

Paul

https://ci.debian.net/data/autopkgtest/testing/amd64/t/twisted/9444048/log.gz

autopkgtest [09:30:22]: test unit-tests-3: [---
Traceback (most recent call last):
  File
"/usr/lib/python3/dist-packages/twisted/conch/test/test_ckeygen.py",
line 86, in test_keygeneration
self._testrun('ecdsa', '384')
  File
"/usr/lib/python3/dist-packages/twisted/conch/test/test_ckeygen.py",
line 75, in _testrun
subprocess.call(args)
  File "/usr/lib/python3.9/subprocess.py", line 349, in call
with Popen(*popenargs, **kwargs) as p:
  File "/usr/lib/python3.9/subprocess.py", line 947, in __init__
self._execute_child(args, executable, preexec_fn, close_fds,
  File "/usr/lib/python3.9/subprocess.py", line 1819, in _execute_child
raise child_exception_type(errno_num, err_msg, err_filename)
builtins.FileNotFoundError: [Errno 2] No such file or directory: 'ckeygen'
Traceback (most recent call last):
  File
"/usr/lib/python3/dist-packages/twisted/conch/test/test_ckeygen.py",
line 105, in test_runBadKeytype
subprocess.check_call(
  File "/usr/lib/python3/dist-packages/twisted/trial/_synctest.py", line
352, in __exit__
self._testCase.fail(
twisted.trial.unittest.FailTest: builtins.FileNotFoundError raised
instead of CalledProcessError:
 Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/twisted/trial/_asynctest.py",
line 111, in _run
d = defer.maybeDeferred(
  File "/usr/lib/python3/dist-packages/twisted/internet/defer.py", line
151, in maybeDeferred
result = f(*args, **kw)
  File "/usr/lib/python3/dist-packages/twisted/internet/utils.py", line
217, in runWithWarningsSuppressed
result = f(*a, **kw)
  File
"/usr/lib/python3/dist-packages/twisted/conch/test/test_ckeygen.py",
line 105, in test_runBadKeytype
subprocess.check_call(
---  ---
  File
"/usr/lib/python3/dist-packages/twisted/conch/test/test_ckeygen.py",
line 105, in test_runBadKeytype
subprocess.check_call(
  File "/usr/lib/python3.9/subprocess.py", line 368, in check_call
retcode = call(*popenargs, **kwargs)
  File "/usr/lib/python3.9/subprocess.py", line 349, in call
with Popen(*popenargs, **kwargs) as p:
  File "/usr/lib/python3.9/subprocess.py", line 947, in __init__
self._execute_child(args, executable, preexec_fn, close_fds,
  File "/usr/lib/python3.9/subprocess.py", line 1819, in _execute_child
raise child_exception_type(errno_num, err_msg, err_filename)
builtins.FileNotFoundError: [Errno 2] No such file or directory: 'ckeygen'



OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: twisted
Source-Version: 20.3.0-4
Done: Sergio Durigan Junior 

We believe that the bug you reported is fixed in the latest version of
twisted, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 979...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Sergio Durigan Junior  (supplier of updated twisted 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 13 Feb 2021 02:12:02 -0500
Source: twisted
Architecture: source
Version: 20.3.0-4
Distribution: unstable
Urgency: medium
Maintainer: 

Bug#982715: marked as done (ruby-redis-rack: FTBFS: ERROR: Test "ruby2.7" failed: ArgumentError: unknown keywords: :path, :domain, :expire_after, :secure, :httponly, :defer, :renew, :sidbits, :secure_

[Willy nilly]

close #982715

On Sun, Feb 14, 2021 at 9:57 PM Debian Bug Tracking System <
ow...@bugs.debian.org> wrote:

> Your message dated Sun, 14 Feb 2021 21:53:57 +
> with message-id 
> and subject line Bug#982715: fixed in ruby-redis-store 1.9.0-1
> has caused the Debian Bug report #982715,
> regarding ruby-redis-rack: FTBFS: ERROR: Test "ruby2.7" failed:
> ArgumentError: unknown keywords: :path, :domain, :expire_after, :secure,
> :httponly, :defer, :renew, :sidbits, :secure_random, :redis_server
> to be marked as done.
>
> This means that you claim that the problem has been dealt with.
> If this is not the case it is now your responsibility to reopen the
> Bug report if necessary, and/or fix the problem forthwith.
>
> (NB: If you are a system administrator and have no idea what this
> message is talking about, this may indicate a serious mail system
> misconfiguration somewhere. Please contact ow...@bugs.debian.org
> immediately.)
>
>
> --
> 982715: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982715
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems
>
>
>
> -- Forwarded message --
> From: Lucas Nussbaum 
> To: sub...@bugs.debian.org
> Cc:
> Bcc:
> Date: Sat, 13 Feb 2021 18:10:10 +0100
> Subject: ruby-redis-rack: FTBFS: ERROR: Test "ruby2.7" failed:
> ArgumentError: unknown keywords: :path, :domain, :expire_after, :secure,
> :httponly, :defer, :renew, :sidbits, :secure_random, :redis_server
> Source: ruby-redis-rack
> Version: 2.1.2-4
> Severity: serious
> Justification: FTBFS on amd64
> Tags: bullseye sid ftbfs
> Usertags: ftbfs-20210213 ftbfs-bullseye
>
> Hi,
>
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
>
> Relevant part (hopefully):
> > ArgumentError: unknown keywords: :path, :domain, :expire_after, :secure,
> :httponly, :defer, :renew, :sidbits, :secure_random, :redis_server
> >
>  /usr/share/rubygems-integration/all/gems/redis-4.2.5/lib/redis.rb:836:in
> `set'
> > /usr/lib/ruby/vendor_ruby/redis/store/interface.rb:9:in `set'
> > /usr/lib/ruby/vendor_ruby/redis/store/ttl.rb:8:in `set'
> > /usr/lib/ruby/vendor_ruby/redis/store/serialization.rb:5:in `block
> in set'
> > /usr/lib/ruby/vendor_ruby/redis/store/serialization.rb:39:in
> `_marshal'
> > /usr/lib/ruby/vendor_ruby/redis/store/serialization.rb:5:in `set'
> > /usr/lib/ruby/vendor_ruby/redis/store/namespace.rb:7:in `block in
> set'
> > /usr/lib/ruby/vendor_ruby/redis/store/namespace.rb:84:in `namespace'
> > /usr/lib/ruby/vendor_ruby/redis/store/namespace.rb:7:in `set'
> > /<>/lib/rack/session/redis.rb:49:in `block (2 levels)
> in write_session'
> > /<>/lib/redis/rack/connection.rb:22:in `with'
> > /<>/lib/rack/session/redis.rb:82:in `with'
> > /<>/lib/rack/session/redis.rb:49:in `block in
> write_session'
> > /<>/lib/rack/session/redis.rb:70:in `with_lock'
> > /<>/lib/rack/session/redis.rb:48:in `write_session'
> > /usr/lib/ruby/vendor_ruby/rack/session/abstract/id.rb:391:in
> `commit_session'
> > /usr/lib/ruby/vendor_ruby/rack/session/abstract/id.rb:271:in
> `context'
> > /usr/lib/ruby/vendor_ruby/rack/session/abstract/id.rb:263:in `call'
> > /usr/lib/ruby/vendor_ruby/rack/mock.rb:77:in `request'
> > /usr/lib/ruby/vendor_ruby/rack/mock.rb:59:in `get'
> > /<>/test/rack/session/redis_test.rb:153:in `block (3
> levels) in '
> > /<>/test/rack/session/redis_test.rb:396:in
> `with_pool_management'
> > /<>/test/rack/session/redis_test.rb:151:in `block (2
> levels) in '
> > /usr/lib/ruby/vendor_ruby/minitest/test.rb:98:in `block (3 levels)
> in run'
> > /usr/lib/ruby/vendor_ruby/minitest/test.rb:195:in
> `capture_exceptions'
> > /usr/lib/ruby/vendor_ruby/minitest/test.rb:95:in `block (2 levels)
> in run'
> > /usr/lib/ruby/vendor_ruby/minitest.rb:270:in `time_it'
> > /usr/lib/ruby/vendor_ruby/minitest/test.rb:94:in `block in run'
> > /usr/lib/ruby/vendor_ruby/minitest.rb:365:in `on_signal'
> > /usr/lib/ruby/vendor_ruby/minitest/test.rb:211:in `with_info_handler'
> > /usr/lib/ruby/vendor_ruby/minitest/test.rb:93:in `run'
> > /usr/lib/ruby/vendor_ruby/minitest.rb:1029:in `run_one_method'
> > /usr/lib/ruby/vendor_ruby/minitest.rb:339:in `run_one_method'
> > /usr/lib/ruby/vendor_ruby/minitest.rb:326:in `block (2 levels) in
> run'
> > /usr/lib/ruby/vendor_ruby/minitest.rb:325:in `each'
> > /usr/lib/ruby/vendor_ruby/minitest.rb:325:in `block in run'
> > /usr/lib/ruby/vendor_ruby/minitest.rb:365:in `on_signal'
> > /usr/lib/ruby/vendor_ruby/minitest.rb:352:in `with_info_handler'
> > /usr/lib/ruby/vendor_ruby/minitest.rb:324:in `run'
> > /usr/lib/ruby/vendor_ruby/minitest.rb:164:in `block in __run'
> > /usr/lib/ruby/vendor_ruby/minitest.rb:164:in `map'
> > /usr/lib/ruby/vendor_ruby/minitest.rb:164:in `__run'
> > /usr/lib/ruby/vendor_ruby/minitest.rb:141:in `run'
> > /usr/lib/ruby/vendor_ruby/minitest.rb:68:in 

Bug#982707: marked as done (ruby-redis-activesupport: FTBFS: ERROR: Test "ruby2.7" failed: ArgumentError: unknown keywords: :pool_size, :pool_timeout)

[Willy nilly]

close #982707

On Sun, Feb 14, 2021 at 9:57 PM Debian Bug Tracking System <
ow...@bugs.debian.org> wrote:

> Your message dated Sun, 14 Feb 2021 21:53:57 +
> with message-id 
> and subject line Bug#982707: fixed in ruby-redis-store 1.9.0-1
> has caused the Debian Bug report #982707,
> regarding ruby-redis-activesupport: FTBFS: ERROR: Test "ruby2.7" failed:
> ArgumentError: unknown keywords: :pool_size, :pool_timeout
> to be marked as done.
>
> This means that you claim that the problem has been dealt with.
> If this is not the case it is now your responsibility to reopen the
> Bug report if necessary, and/or fix the problem forthwith.
>
> (NB: If you are a system administrator and have no idea what this
> message is talking about, this may indicate a serious mail system
> misconfiguration somewhere. Please contact ow...@bugs.debian.org
> immediately.)
>
>
> --
> 982707: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982707
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems
>
>
>
> -- Forwarded message --
> From: Lucas Nussbaum 
> To: sub...@bugs.debian.org
> Cc:
> Bcc:
> Date: Sat, 13 Feb 2021 18:10:07 +0100
> Subject: ruby-redis-activesupport: FTBFS: ERROR: Test "ruby2.7" failed:
> ArgumentError: unknown keywords: :pool_size, :pool_timeout
> Source: ruby-redis-activesupport
> Version: 5.2.0-1
> Severity: serious
> Justification: FTBFS on amd64
> Tags: bullseye sid ftbfs
> Usertags: ftbfs-20210213 ftbfs-bullseye
>
> Hi,
>
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
>
> Relevant part (hopefully):
> > ArgumentError: unknown keywords: :pool_size, :pool_timeout
> >
>  /usr/share/rubygems-integration/all/gems/redis-4.2.5/lib/redis.rb:836:in
> `set'
> > /usr/lib/ruby/vendor_ruby/redis/store/interface.rb:9:in `set'
> > /usr/lib/ruby/vendor_ruby/redis/store/ttl.rb:8:in `set'
> > /usr/lib/ruby/vendor_ruby/redis/store/serialization.rb:5:in `block
> in set'
> > /usr/lib/ruby/vendor_ruby/redis/store/serialization.rb:39:in
> `_marshal'
> > /usr/lib/ruby/vendor_ruby/redis/store/serialization.rb:5:in `set'
> > /usr/lib/ruby/vendor_ruby/redis/store/namespace.rb:7:in `block in
> set'
> > /usr/lib/ruby/vendor_ruby/redis/store/namespace.rb:84:in `namespace'
> > /usr/lib/ruby/vendor_ruby/redis/store/namespace.rb:7:in `set'
> > /<>/lib/active_support/cache/redis_store.rb:282:in
> `block (2 levels) in write_entry'
> > /usr/lib/ruby/vendor_ruby/connection_pool.rb:65:in `block (2 levels)
> in with'
> > /usr/lib/ruby/vendor_ruby/connection_pool.rb:64:in `handle_interrupt'
> > /usr/lib/ruby/vendor_ruby/connection_pool.rb:64:in `block in with'
> > /usr/lib/ruby/vendor_ruby/connection_pool.rb:61:in `handle_interrupt'
> > /usr/lib/ruby/vendor_ruby/connection_pool.rb:61:in `with'
> > /<>/lib/active_support/cache/redis_store.rb:268:in
> `with'
> > /<>/lib/active_support/cache/redis_store.rb:282:in
> `block in write_entry'
> > /<>/lib/active_support/cache/redis_store.rb:340:in
> `failsafe'
> > /<>/lib/active_support/cache/redis_store.rb:280:in
> `write_entry'
> > /<>/lib/active_support/cache/redis_store.rb:86:in
> `block in write'
> >
>  
> /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.4/lib/active_support/cache.rb:686:in
> `block in instrument'
> >
>  
> /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.4/lib/active_support/notifications.rb:182:in
> `instrument'
> >
>  
> /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.4/lib/active_support/cache.rb:686:in
> `instrument'
> > /<>/lib/active_support/cache/redis_store.rb:81:in
> `write'
> > /<>/test/active_support/cache/redis_store_test.rb:22:in
> `block in setup'
> >
>  /<>/test/active_support/cache/redis_store_test.rb:762:in
> `with_store_management'
> > /<>/test/active_support/cache/redis_store_test.rb:21:in
> `setup'
> > /usr/lib/ruby/vendor_ruby/minitest/test.rb:96:in `block (3 levels)
> in run'
> > /usr/lib/ruby/vendor_ruby/minitest/test.rb:195:in
> `capture_exceptions'
> > /usr/lib/ruby/vendor_ruby/minitest/test.rb:95:in `block (2 levels)
> in run'
> > /usr/lib/ruby/vendor_ruby/minitest.rb:270:in `time_it'
> > /usr/lib/ruby/vendor_ruby/minitest/test.rb:94:in `block in run'
> > /usr/lib/ruby/vendor_ruby/minitest.rb:365:in `on_signal'
> > /usr/lib/ruby/vendor_ruby/minitest/test.rb:211:in `with_info_handler'
> > /usr/lib/ruby/vendor_ruby/minitest/test.rb:93:in `run'
> > /usr/lib/ruby/vendor_ruby/minitest.rb:1029:in `run_one_method'
> > /usr/lib/ruby/vendor_ruby/minitest.rb:339:in `run_one_method'
> > /usr/lib/ruby/vendor_ruby/minitest.rb:326:in `block (2 levels) in
> run'
> > /usr/lib/ruby/vendor_ruby/minitest.rb:325:in `each'
> > /usr/lib/ruby/vendor_ruby/minitest.rb:325:in `block in run'
> > /usr/lib/ruby/vendor_ruby/minitest.rb:365:in `on_signal'
> > /usr/lib/ruby/vendor_ruby/minitest.rb:352:in `with_info_handler'

Bug#979838: marked as pending in twisted

[Sergio Durigan Junior]

Control: tag -1 pending

Hello,

Bug #979838 in twisted 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/packages/twisted/-/commit/b83f142eebd9198e9b07fc01960b01e1ee4b3403


Fix several autopkgtest failures. (Closes: #979838)

- d/p/0016-Try-exec-ing-ckeygen3-if-ckeygen-was-not-found.path:
  Rename ckeygen to ckeygen3.
- d/p/0017-Add-digestmod-parameter-to-HMAC.__init__-invocations.patch:
  Add digestmod parameter to HMAC.__init__() invocations.
- d/p/0018-Make-the-twisted-tests-work-when-pyOpenSSL-deletes-N.patch:
  Make the twisted tests work when pyOpenSSL deletes NPN.
- d/p/0019-Replace-base64.-string-functions-to-fix-py3.9-suppor.patch:
  Replace base64.*string() functions to fix py3.9 support.
- d/p/0020-Fix-imap4-utf-7-codec-lookup-function-for-Python-3.9.patch:
  Rename imap4-utf-7 to imap_utf_7.
- d/p/0021-Merge-9652-wiml-mktime-Allow-mktime-to-raise-EOVERFL.patch:
  Allow mktime() to raise EOVERFLOW if isdst=1 and there's no DST.
- d/p/0022-increase-size-of-FFDH-keys-for-conch-testing.patch:
  Increase size of FFDH keys for conch testing.
- d/p/0023-Merge-9801-rodrigc-cgi-Change-import-of-cgi.parse_qs.patch:
  Change import of cgi.parse_qs to urllib.parse.parse_qs.
- d/p/0024-fixed-corrupted-iqmp-value-in-test-RSA-key.patch:
  Fix corrupted iqmp value in test RSA key.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/979838

Processed: Bug#979838 marked as pending in twisted

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #979838 [src:twisted] twisted: autopkgtest regression in testing: No such 
file or directory: 'ckeygen'
Added tag(s) pending.

-- 
979838: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979838
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#982715: marked as done (ruby-redis-rack: FTBFS: ERROR: Test "ruby2.7" failed: ArgumentError: unknown keywords: :path, :domain, :expire_after, :secure, :httponly, :defer, :renew, :sidbits, :secure_

[Debian Bug Tracking System]

Your message dated Sun, 14 Feb 2021 21:53:57 +
with message-id 
and subject line Bug#982715: fixed in ruby-redis-store 1.9.0-1
has caused the Debian Bug report #982715,
regarding ruby-redis-rack: FTBFS: ERROR: Test "ruby2.7" failed: ArgumentError: 
unknown keywords: :path, :domain, :expire_after, :secure, :httponly, :defer, 
:renew, :sidbits, :secure_random, :redis_server
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
982715: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982715
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-redis-rack
Version: 2.1.2-4
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20210213 ftbfs-bullseye

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.

Relevant part (hopefully):
> ArgumentError: unknown keywords: :path, :domain, :expire_after, :secure, 
> :httponly, :defer, :renew, :sidbits, :secure_random, :redis_server
> /usr/share/rubygems-integration/all/gems/redis-4.2.5/lib/redis.rb:836:in 
> `set'
> /usr/lib/ruby/vendor_ruby/redis/store/interface.rb:9:in `set'
> /usr/lib/ruby/vendor_ruby/redis/store/ttl.rb:8:in `set'
> /usr/lib/ruby/vendor_ruby/redis/store/serialization.rb:5:in `block in set'
> /usr/lib/ruby/vendor_ruby/redis/store/serialization.rb:39:in `_marshal'
> /usr/lib/ruby/vendor_ruby/redis/store/serialization.rb:5:in `set'
> /usr/lib/ruby/vendor_ruby/redis/store/namespace.rb:7:in `block in set'
> /usr/lib/ruby/vendor_ruby/redis/store/namespace.rb:84:in `namespace'
> /usr/lib/ruby/vendor_ruby/redis/store/namespace.rb:7:in `set'
> /<>/lib/rack/session/redis.rb:49:in `block (2 levels) in 
> write_session'
> /<>/lib/redis/rack/connection.rb:22:in `with'
> /<>/lib/rack/session/redis.rb:82:in `with'
> /<>/lib/rack/session/redis.rb:49:in `block in write_session'
> /<>/lib/rack/session/redis.rb:70:in `with_lock'
> /<>/lib/rack/session/redis.rb:48:in `write_session'
> /usr/lib/ruby/vendor_ruby/rack/session/abstract/id.rb:391:in 
> `commit_session'
> /usr/lib/ruby/vendor_ruby/rack/session/abstract/id.rb:271:in `context'
> /usr/lib/ruby/vendor_ruby/rack/session/abstract/id.rb:263:in `call'
> /usr/lib/ruby/vendor_ruby/rack/mock.rb:77:in `request'
> /usr/lib/ruby/vendor_ruby/rack/mock.rb:59:in `get'
> /<>/test/rack/session/redis_test.rb:153:in `block (3 levels) 
> in '
> /<>/test/rack/session/redis_test.rb:396:in 
> `with_pool_management'
> /<>/test/rack/session/redis_test.rb:151:in `block (2 levels) 
> in '
> /usr/lib/ruby/vendor_ruby/minitest/test.rb:98:in `block (3 levels) in run'
> /usr/lib/ruby/vendor_ruby/minitest/test.rb:195:in `capture_exceptions'
> /usr/lib/ruby/vendor_ruby/minitest/test.rb:95:in `block (2 levels) in run'
> /usr/lib/ruby/vendor_ruby/minitest.rb:270:in `time_it'
> /usr/lib/ruby/vendor_ruby/minitest/test.rb:94:in `block in run'
> /usr/lib/ruby/vendor_ruby/minitest.rb:365:in `on_signal'
> /usr/lib/ruby/vendor_ruby/minitest/test.rb:211:in `with_info_handler'
> /usr/lib/ruby/vendor_ruby/minitest/test.rb:93:in `run'
> /usr/lib/ruby/vendor_ruby/minitest.rb:1029:in `run_one_method'
> /usr/lib/ruby/vendor_ruby/minitest.rb:339:in `run_one_method'
> /usr/lib/ruby/vendor_ruby/minitest.rb:326:in `block (2 levels) in run'
> /usr/lib/ruby/vendor_ruby/minitest.rb:325:in `each'
> /usr/lib/ruby/vendor_ruby/minitest.rb:325:in `block in run'
> /usr/lib/ruby/vendor_ruby/minitest.rb:365:in `on_signal'
> /usr/lib/ruby/vendor_ruby/minitest.rb:352:in `with_info_handler'
> /usr/lib/ruby/vendor_ruby/minitest.rb:324:in `run'
> /usr/lib/ruby/vendor_ruby/minitest.rb:164:in `block in __run'
> /usr/lib/ruby/vendor_ruby/minitest.rb:164:in `map'
> /usr/lib/ruby/vendor_ruby/minitest.rb:164:in `__run'
> /usr/lib/ruby/vendor_ruby/minitest.rb:141:in `run'
> /usr/lib/ruby/vendor_ruby/minitest.rb:68:in `block in autorun'
> 
> 34 runs, 78 assertions, 0 failures, 10 errors, 0 skips
> pkill redis-server
> rake aborted!
> Tests failed
> /<>/debian/ruby-tests.rake:12:in `block in '
> /usr/share/rubygems-integration/all/gems/rake-13.0.3/exe/rake:27:in ` (required)>'
> Tasks: TOP => default
> (See full trace by running task with --trace)
> ERROR: Test "ruby2.7" failed: 

The full build log is available from:
   http://qa-logs.debian.net/2021/02/13/ruby-redis-rack_2.1.2-4_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're 

Bug#982707: marked as done (ruby-redis-activesupport: FTBFS: ERROR: Test "ruby2.7" failed: ArgumentError: unknown keywords: :pool_size, :pool_timeout)

[Debian Bug Tracking System]

Your message dated Sun, 14 Feb 2021 21:53:57 +
with message-id 
and subject line Bug#982707: fixed in ruby-redis-store 1.9.0-1
has caused the Debian Bug report #982707,
regarding ruby-redis-activesupport: FTBFS: ERROR: Test "ruby2.7" failed: 
ArgumentError: unknown keywords: :pool_size, :pool_timeout
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
982707: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982707
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-redis-activesupport
Version: 5.2.0-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20210213 ftbfs-bullseye

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.

Relevant part (hopefully):
> ArgumentError: unknown keywords: :pool_size, :pool_timeout
> /usr/share/rubygems-integration/all/gems/redis-4.2.5/lib/redis.rb:836:in 
> `set'
> /usr/lib/ruby/vendor_ruby/redis/store/interface.rb:9:in `set'
> /usr/lib/ruby/vendor_ruby/redis/store/ttl.rb:8:in `set'
> /usr/lib/ruby/vendor_ruby/redis/store/serialization.rb:5:in `block in set'
> /usr/lib/ruby/vendor_ruby/redis/store/serialization.rb:39:in `_marshal'
> /usr/lib/ruby/vendor_ruby/redis/store/serialization.rb:5:in `set'
> /usr/lib/ruby/vendor_ruby/redis/store/namespace.rb:7:in `block in set'
> /usr/lib/ruby/vendor_ruby/redis/store/namespace.rb:84:in `namespace'
> /usr/lib/ruby/vendor_ruby/redis/store/namespace.rb:7:in `set'
> /<>/lib/active_support/cache/redis_store.rb:282:in `block (2 
> levels) in write_entry'
> /usr/lib/ruby/vendor_ruby/connection_pool.rb:65:in `block (2 levels) in 
> with'
> /usr/lib/ruby/vendor_ruby/connection_pool.rb:64:in `handle_interrupt'
> /usr/lib/ruby/vendor_ruby/connection_pool.rb:64:in `block in with'
> /usr/lib/ruby/vendor_ruby/connection_pool.rb:61:in `handle_interrupt'
> /usr/lib/ruby/vendor_ruby/connection_pool.rb:61:in `with'
> /<>/lib/active_support/cache/redis_store.rb:268:in `with'
> /<>/lib/active_support/cache/redis_store.rb:282:in `block in 
> write_entry'
> /<>/lib/active_support/cache/redis_store.rb:340:in `failsafe'
> /<>/lib/active_support/cache/redis_store.rb:280:in 
> `write_entry'
> /<>/lib/active_support/cache/redis_store.rb:86:in `block in 
> write'
> 
> /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.4/lib/active_support/cache.rb:686:in
>  `block in instrument'
> 
> /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.4/lib/active_support/notifications.rb:182:in
>  `instrument'
> 
> /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.4/lib/active_support/cache.rb:686:in
>  `instrument'
> /<>/lib/active_support/cache/redis_store.rb:81:in `write'
> /<>/test/active_support/cache/redis_store_test.rb:22:in 
> `block in setup'
> /<>/test/active_support/cache/redis_store_test.rb:762:in 
> `with_store_management'
> /<>/test/active_support/cache/redis_store_test.rb:21:in 
> `setup'
> /usr/lib/ruby/vendor_ruby/minitest/test.rb:96:in `block (3 levels) in run'
> /usr/lib/ruby/vendor_ruby/minitest/test.rb:195:in `capture_exceptions'
> /usr/lib/ruby/vendor_ruby/minitest/test.rb:95:in `block (2 levels) in run'
> /usr/lib/ruby/vendor_ruby/minitest.rb:270:in `time_it'
> /usr/lib/ruby/vendor_ruby/minitest/test.rb:94:in `block in run'
> /usr/lib/ruby/vendor_ruby/minitest.rb:365:in `on_signal'
> /usr/lib/ruby/vendor_ruby/minitest/test.rb:211:in `with_info_handler'
> /usr/lib/ruby/vendor_ruby/minitest/test.rb:93:in `run'
> /usr/lib/ruby/vendor_ruby/minitest.rb:1029:in `run_one_method'
> /usr/lib/ruby/vendor_ruby/minitest.rb:339:in `run_one_method'
> /usr/lib/ruby/vendor_ruby/minitest.rb:326:in `block (2 levels) in run'
> /usr/lib/ruby/vendor_ruby/minitest.rb:325:in `each'
> /usr/lib/ruby/vendor_ruby/minitest.rb:325:in `block in run'
> /usr/lib/ruby/vendor_ruby/minitest.rb:365:in `on_signal'
> /usr/lib/ruby/vendor_ruby/minitest.rb:352:in `with_info_handler'
> /usr/lib/ruby/vendor_ruby/minitest.rb:324:in `run'
> /usr/lib/ruby/vendor_ruby/minitest.rb:164:in `block in __run'
> /usr/lib/ruby/vendor_ruby/minitest.rb:164:in `map'
> /usr/lib/ruby/vendor_ruby/minitest.rb:164:in `__run'
> /usr/lib/ruby/vendor_ruby/minitest.rb:141:in `run'
> /usr/lib/ruby/vendor_ruby/minitest.rb:68:in `block in autorun'
> 
> 81 runs, 288 assertions, 0 failures, 69 errors, 0 skips
> pkill redis-server
> rake aborted!
> Tests failed
> /<>/debian/ruby-tests.rake:13:in `block 

Processed: affects 982715

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> affects 982715 src:ruby-redis-rack
Bug #982715 [ruby-redis-store] ruby-redis-rack: FTBFS: ERROR: Test "ruby2.7" 
failed: ArgumentError: unknown keywords: :path, :domain, :expire_after, 
:secure, :httponly, :defer, :renew, :sidbits, :secure_random, :redis_server
Added indication that 982715 affects src:ruby-redis-rack
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
982715: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982715
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: reassign 982715 to ruby-redis-store

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 982715 ruby-redis-store
Bug #982715 [src:ruby-redis-rack] ruby-redis-rack: FTBFS: ERROR: Test "ruby2.7" 
failed: ArgumentError: unknown keywords: :path, :domain, :expire_after, 
:secure, :httponly, :defer, :renew, :sidbits, :secure_random, :redis_server
Bug reassigned from package 'src:ruby-redis-rack' to 'ruby-redis-store'.
No longer marked as found in versions ruby-redis-rack/2.1.2-4.
Ignoring request to alter fixed versions of bug #982715 to the same values 
previously set
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
982715: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982715
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: tagging 694320

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 694320 - pending
Bug #694320 [gsfonts] [gsfonts] Fonts include copyrighted adobe fragment all 
right reserved
Bug #694321 [gsfonts] [gsfonts] Fonts include copyrighted adobe fragment all 
right reserved
Removed tag(s) pending.
Removed tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
694320: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=694320
694321: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=694321
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Re: Bug#982677: FTBFS - required network connection

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 982677 = moreinfo unreproducible
Bug #982677 [rbac-client-clojure] FTBFS - required network connection
Added tag(s) unreproducible and moreinfo.
> severity 982677 normal
Bug #982677 [rbac-client-clojure] FTBFS - required network connection
Severity set to 'normal' from 'serious'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
982677: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982677
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: affects 982707

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> affects 982707 src:ruby-redis-activesupport
Bug #982707 [ruby-redis-store] ruby-redis-activesupport: FTBFS: ERROR: Test 
"ruby2.7" failed: ArgumentError: unknown keywords: :pool_size, :pool_timeout
Added indication that 982707 affects src:ruby-redis-activesupport
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
982707: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982707
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: reassign 982707 to ruby-redis-store

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 982707 ruby-redis-store
Bug #982707 [src:ruby-redis-activesupport] ruby-redis-activesupport: FTBFS: 
ERROR: Test "ruby2.7" failed: ArgumentError: unknown keywords: :pool_size, 
:pool_timeout
Bug reassigned from package 'src:ruby-redis-activesupport' to 
'ruby-redis-store'.
No longer marked as found in versions ruby-redis-activesupport/5.2.0-1.
Ignoring request to alter fixed versions of bug #982707 to the same values 
previously set
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
982707: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982707
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#982677: FTBFS - required network connection

[Louis-Philippe Véronneau]

tags 982677 = moreinfo unreproducible
severity 982677 normal
thanks

Holger reports no problem in building this package using pbuilder
without a network connection:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/rbac-client-clojure.html

I'm thus tagging this bug as requiring more info (how are you building
it exactly?) and as unreproducible. For now, I'm also decreasing the
severity to normal.

-- 
  ⢀⣴⠾⠻⢶⣦⠀
  ⣾⠁⢠⠒⠀⣿⡁  Louis-Philippe Véronneau
  ⢿⡄⠘⠷⠚⠋   po...@debian.org / veronneau.org
  ⠈⠳⣄



OpenPGP_signature
Description: OpenPGP digital signature

Bug#982817: yash FTBFS on mips*el because test silently times out

[Paul Gevers]

Source: yash
Version: 2.51-1
Severity: serious
Tags: ftbfs

Hi Maintainer,

Your last upload of yash FTBFS on mipsel and mips64el.

Paul

https://buildd.debian.org/status/package.php?p=yash

E: Build killed with signal TERM after 150 minutes of inactivity



OpenPGP_signature
Description: OpenPGP digital signature

Bug#977990: os-autoinst: FTBFS on i386: 3/3 Test #3: test-perl-testsuite ..............***Failed 332.81 sec

[Paul Gevers]

Hi,

On Thu, 24 Dec 2020 00:05:30 +0100 Sebastian Ramacher
 wrote:
> Source: os-autoinst
> Version: 4.6.1604525166.912dfbd-0.2
> Severity: serious
> Tags: ftbfs
> Justification: fails to build from source (but built successfully in the past)
> X-Debbugs-Cc: sramac...@debian.org
> 
> os-autoinst FTBFS on i386:
> | 3: ./29-backend-generalhw.t . ok
> | 3: 
> | 3: #   Failed test 'Result in testresults/result-reload_needles.json is ok'
> | 3: #   at ./99-full-stack.t line 86.
> | 3: #  got: 'fail'
> | 3: # expected: 'ok'
> | 3: Bailout called.  Further testing stopped:  
> testresults/result-reload_needles.json failed
> | 3: FAILED--Further testing stopped: testresults/result-reload_needles.json 
> failed
> | 3/3 Test #3: test-perl-testsuite ..***Failed  332.81 sec
> 
> See
> https://buildd.debian.org/status/fetch.php?pkg=os-autoinst=i386=4.6.1604525166.912dfbd-0.2=1608714762=0

I don't know if anything changed, but the FORTH build was successful.
Could be that the test is flaky.

Paul



OpenPGP_signature
Description: OpenPGP digital signature

Processed: found 982807 in 4.9.3-2

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> found 982807 4.9.3-2
Bug #982807 [datovka] datovka: version too old to be useful
Marked as found in versions datovka/4.9.3-2.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
982807: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982807
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: src:bats: fails to migrate to testing for too long: autopkgtest regression

[Debian Bug Tracking System]

Processing control commands:

> close -1 1.2.1-1
Bug #982816 [src:bats] src:bats: fails to migrate to testing for too long: 
autopkgtest regression
Marked as fixed in versions bats/1.2.1-1.
Bug #982816 [src:bats] src:bats: fails to migrate to testing for too long: 
autopkgtest regression
Marked Bug as done
> block -1 by 980967
Bug #982816 {Done: Paul Gevers } [src:bats] src:bats: fails 
to migrate to testing for too long: autopkgtest regression
982816 was not blocked by any bugs.
982816 was not blocking any bugs.
Added blocking bug(s) of 982816: 980967

-- 
982816: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982816
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#975207: ping!

[Louis-Philippe Véronneau]

Ping!

This bug has been fixed, but the package won't make it in testing before
it is autoremoved.

This should reset the autoremoval timer.

Cheers,

-- 
  ⢀⣴⠾⠻⢶⣦⠀
  ⣾⠁⢠⠒⠀⣿⡁  Louis-Philippe Véronneau
  ⢿⡄⠘⠷⠚⠋   po...@debian.org / veronneau.org
  ⠈⠳⣄



OpenPGP_signature
Description: OpenPGP digital signature

Bug#982816: src:bats: fails to migrate to testing for too long: autopkgtest regression

[Paul Gevers]

Source: bats
Version: 1.1.0+git104-g1c83a1b-1.1
Severity: serious
Control: close -1 1.2.1-1
Tags: sid bullseye
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 980967

Dear maintainer(s),

As recently announced [1], the Release Team now considers packages that
are out-of-sync between testing and unstable for more than 60 days as
having a Release Critical bug in testing. Your package src:bats has been
trying to migrate for 59 days [2]. Hence, I am filing this bug, albeit
one day early.

If a package is out of sync between unstable and testing for a longer
period, this usually means that bugs in the package in testing cannot be
fixed via unstable. Additionally, blocked packages can have impact on
other packages, which makes preparing for the release more difficult.
Finally, it often exposes issues with the package and/or
its (reverse-)dependencies. We expect maintainers to fix issues that
hamper the migration of their package in a timely manner.

This bug will trigger auto-removal when appropriate. As with all new
bugs, there will be at least 30 days before the package is auto-removed.

I have immediately closed this bug with the version in unstable, so if
that version or a later version migrates, this bug will no longer affect
testing. I have also tagged this bug to only affect sid and bullseye, so
it doesn't affect (old-)stable.

If you believe your package is unable to migrate to testing due to
issues beyond your control, don't hesitate to contact the Release Team.

Paul

[1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html
[2] https://qa.debian.org/excuses.php?package=bats




OpenPGP_signature
Description: OpenPGP digital signature

Processed: tagging 982685, found 982683 in 8.0.19+dfsg-1, fixed 966813 in 1.46.0-1, tagging 982701 ...

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 982685 + sid bullseye
Bug #982685 [sl-modem] sl-modem: Depends on removed package
Added tag(s) sid and bullseye.
> found 982683 8.0.19+dfsg-1
Bug #982683 [mysql-workbench] mysql-workbench: Uses no-longer existing package 
for build, remove?
Marked as found in versions mysql-workbench/8.0.19+dfsg-1.
> fixed 966813 1.46.0-1
Bug #966813 {Done: "Theodore Y. Ts'o" } [src:e2fsprogs] 
e2fsprogs: FTBFS with GCC 10: multiple definition of ... due to -fno-common
Marked as fixed in versions e2fsprogs/1.46.0-1.
> tags 982701 - sid bullseye
Bug #982701 [src:golang-1.15] golang-github-pkg-profile: FTBFS: dh_auto_test: 
error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 4 
github.com/pkg/profile returned exit code 1
Removed tag(s) bullseye and sid.
> tags 982724 - sid bullseye
Bug #982724 [src:golang-1.15] panicparse: FTBFS: dh_auto_test: error: cd _build 
&& go test -vet=off -v -p 4 github.com/maruel/panicparse 
github.com/maruel/panicparse/cmd/panic 
github.com/maruel/panicparse/cmd/panic/internal 
github.com/maruel/panicparse/cmd/pp github.com/maruel/panicparse/internal 
github.com/maruel/panicparse/stack returned exit code 1
Removed tag(s) sid and bullseye.
> tags 982714 - sid bullseye
Bug #982714 [src:golang-1.15] golang-github-jacobsa-ogletest: FTBFS: 
dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 4 
github.com/jacobsa/ogletest github.com/jacobsa/ogletest/srcutil 
github.com/jacobsa/ogletest/test_cases 
github.com/jacobsa/ogletest/test_cases/mock_image returned exit code 1
Removed tag(s) bullseye and sid.
> tags 982734 - sid bullseye
Bug #982734 [src:golang-1.15] delve: FTBFS: failed test
Removed tag(s) bullseye and sid.
> tags 982720 - sid bullseye
Bug #982720 [src:golang-1.15] snapd: FTBFS: dh_auto_test fails
Removed tag(s) sid and bullseye.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
966813: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966813
982683: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982683
982685: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982685
982701: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982701
982714: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982714
982720: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982720
982724: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982724
982734: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982734
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#982719: firehol: FTBFS: dh_auto_test: error: make -j1 check VERBOSE=1 returned exit code 2

[Jerome BENOIT]

Hi Dennis, thanks for confirming.
May I simply neutralize the involved test temporarily ?
Cheers, Jerome 

Bug#982802: Info received (Bug#982802: marked as done (libio-html-perl: autopkgtest failure))

[Willy nilly]

close #982802

On Sun, Feb 14, 2021 at 8:24 PM Debian Bug Tracking System <
ow...@bugs.debian.org> wrote:

> Thank you for the additional information you have supplied regarding
> this Bug report.
>
> This is an automatically generated reply to let you know your message
> has been received.
>
> Your message is being forwarded to the package maintainers and other
> interested parties for their attention; they will reply in due course.
>
> Your message has been sent to the package maintainer(s):
>  Debian Perl Group 
>
> If you wish to submit further information on this problem, please
> send it to 982...@bugs.debian.org.
>
> Please do not send mail to ow...@bugs.debian.org unless you wish
> to report a problem with the Bug-tracking system.
>
> --
> 982802: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982802
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems
>

Bug#979866: marked as done (knxd FTBFS everywhere: autoconf issues)

[Willy nilly]

close #979866

On Sun, Feb 14, 2021 at 8:00 PM Debian Bug Tracking System <
ow...@bugs.debian.org> wrote:

> Your message dated Sun, 14 Feb 2021 21:57:11 +0200
> with message-id <20210214195710.GA20085@localhost>
> and subject line Re: Bug#979866: knxd FTBFS everywhere: autoconf issues
> has caused the Debian Bug report #979866,
> regarding knxd FTBFS everywhere: autoconf issues
> to be marked as done.
>
> This means that you claim that the problem has been dealt with.
> If this is not the case it is now your responsibility to reopen the
> Bug report if necessary, and/or fix the problem forthwith.
>
> (NB: If you are a system administrator and have no idea what this
> message is talking about, this may indicate a serious mail system
> misconfiguration somewhere. Please contact ow...@bugs.debian.org
> immediately.)
>
>
> --
> 979866: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979866
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems
>
>
>
> -- Forwarded message --
> From: Helmut Grohne 
> To: Debian Bug Tracking System 
> Cc:
> Bcc:
> Date: Mon, 11 Jan 2021 06:56:32 +0100
> Subject: knxd FTBFS everywhere: autoconf issues
> Source: knxd
> Version: 0.14.41-1
> Severity: serious
> Tags: ftbfs
>
> knxd fails to build from source for all attempted architectures on the
> buildds. A build log usually ends with:
>
> |dh_autoreconf -a
> |  find ! -ipath "./debian/*" -a ! \( -path '*/.git/*' -o -path '*/.hg/*'
> -o -path '*/.bzr/*' -o -path '*/.svn/*' -o -path '*/CVS/*' \) -a  -type f
> -exec md5sum {} + -o -type l -printf "symlink  %p
> | " > debian/autoreconf.before
> |  grep -q ^XDT_ configure.ac
> |  autoreconf -f -i
> | configure.ac:30: error: AC_INIT should be called with package and
> version arguments
> | /usr/share/aclocal-1.16/init.m4:29: AM_INIT_AUTOMAKE is expanded from...
> | configure.ac:30: the top level
> | autom4te: /usr/bin/m4 failed with exit status: 1
> | aclocal: error: /usr/bin/autom4te failed with exit status: 1
> | autoreconf: aclocal failed with exit status: 1
> |  find ! -ipath "./debian/*" -a ! \( -path '*/.git/*' -o -path '*/.hg/*'
> -o -path '*/.bzr/*' -o -path '*/.svn/*' -o -path '*/CVS/*' \) -a  -type f
> -exec md5sum {} + -o -type l -printf "symlink  %p
> | " > debian/autoreconf.after
> | dh_autoreconf: error: autoreconf -f -i returned exit code 1
> | make: *** [debian/rules:14: build-arch] Error 25
>
> Could this be related to autoconf 2.70?
>
> Helmut
>
>
>
> -- Forwarded message --
> From: Adrian Bunk 
> To: Helmut Grohne , 979866-d...@bugs.debian.org
> Cc:
> Bcc:
> Date: Sun, 14 Feb 2021 21:57:11 +0200
> Subject: Re: Bug#979866: knxd FTBFS everywhere: autoconf issues
> Version: 0.14.46-1
>
> On Mon, Jan 11, 2021 at 06:56:32AM +0100, Helmut Grohne wrote:
> > Source: knxd
> > Version: 0.14.41-1
> > Severity: serious
> > Tags: ftbfs
> >
> > knxd fails to build from source for all attempted architectures on the
> > buildds. A build log usually ends with:
> >
> > |dh_autoreconf -a
> > |  find ! -ipath "./debian/*" -a ! \( -path '*/.git/*' -o -path
> '*/.hg/*' -o -path '*/.bzr/*' -o -path '*/.svn/*' -o -path '*/CVS/*' \) -a
> -type f -exec md5sum {} + -o -type l -printf "symlink  %p
> > | " > debian/autoreconf.before
> > |  grep -q ^XDT_ configure.ac
> > |  autoreconf -f -i
> > | configure.ac:30: error: AC_INIT should be called with package and
> version arguments
> > | /usr/share/aclocal-1.16/init.m4:29: AM_INIT_AUTOMAKE is expanded
> from...
> > | configure.ac:30: the top level
> > | autom4te: /usr/bin/m4 failed with exit status: 1
> > | aclocal: error: /usr/bin/autom4te failed with exit status: 1
> > | autoreconf: aclocal failed with exit status: 1
> > |  find ! -ipath "./debian/*" -a ! \( -path '*/.git/*' -o -path
> '*/.hg/*' -o -path '*/.bzr/*' -o -path '*/.svn/*' -o -path '*/CVS/*' \) -a
> -type f -exec md5sum {} + -o -type l -printf "symlink  %p
> > | " > debian/autoreconf.after
> > | dh_autoreconf: error: autoreconf -f -i returned exit code 1
> > | make: *** [debian/rules:14: build-arch] Error 25
> >...
>
> This seems fixed in 0.14.46-1:
> https://buildd.debian.org/status/logs.php?pkg=knxd=0.14.46-1
>
> > Helmut
>
> cu
> Adrian

Processed: affects 979609

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> affects 979609 eclipse-tracecompass
Bug #979609 [src:swt4-gtk] swt4-gtk segfaults on ppc64el
Added indication that 979609 affects eclipse-tracecompass
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
979609: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979609
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#982802: marked as done (libio-html-perl: autopkgtest failure)

[Willy nilly]

close #982802

On Sun, Feb 14, 2021 at 5:51 PM Debian Bug Tracking System <
ow...@bugs.debian.org> wrote:

> Your message dated Sun, 14 Feb 2021 17:50:29 +
> with message-id 
> and subject line Bug#982802: fixed in libio-html-perl 1.004-2
> has caused the Debian Bug report #982802,
> regarding libio-html-perl: autopkgtest failure
> to be marked as done.
>
> This means that you claim that the problem has been dealt with.
> If this is not the case it is now your responsibility to reopen the
> Bug report if necessary, and/or fix the problem forthwith.
>
> (NB: If you are a system administrator and have no idea what this
> message is talking about, this may indicate a serious mail system
> misconfiguration somewhere. Please contact ow...@bugs.debian.org
> immediately.)
>
>
> --
> 982802: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982802
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems
>
>
>
> -- Forwarded message --
> From: Adrian Bunk 
> To: Debian Bug Tracking System 
> Cc:
> Bcc:
> Date: Sun, 14 Feb 2021 18:33:42 +0200
> Subject: libio-html-perl: autopkgtest failure
> Source: libio-html-perl
> Version: 1.004-1
> Severity: serious
>
>
> https://ci.debian.net/data/autopkgtest/testing/amd64/libi/libio-html-perl/10422807/log.gz
>
> ...
> t/00-all_prereqs.t ..
> not ok 1 - opened META.json
> 1..1
> Failed 1/1 subtests
> ...
> Test Summary Report
> ---
> t/00-all_prereqs.t (Wstat: 0 Tests: 1 Failed: 1)
>   Failed test:  1
> Files=5, Tests=141,  1 wallclock secs ( 0.05 usr  0.01 sys +  0.33 cusr
> 0.03 csys =  0.42 CPU)
> Result: FAIL
> autopkgtest [15:04:02]: test autodep8-perl-build-deps:
> ---]
> autopkgtest [15:04:02]: test autodep8-perl-build-deps:  - - - - - - - - -
> - results - - - - - - - - - -
> autodep8-perl-build-deps FAIL non-zero exit status 1
> ...
>
>
>
> -- Forwarded message --
> From: Debian FTP Masters 
> To: 982802-cl...@bugs.debian.org
> Cc:
> Bcc:
> Date: Sun, 14 Feb 2021 17:50:29 +
> Subject: Bug#982802: fixed in libio-html-perl 1.004-2
> Source: libio-html-perl
> Source-Version: 1.004-2
> Done: gregor herrmann 
>
> We believe that the bug you reported is fixed in the latest version of
> libio-html-perl, which is due to be installed in the Debian FTP archive.
>
> A summary of the changes between this version and the previous one is
> attached.
>
> Thank you for reporting the bug, which will now be closed.  If you
> have further comments please address them to 982...@bugs.debian.org,
> and the maintainer will reopen the bug report if appropriate.
>
> Debian distribution maintenance software
> pp.
> gregor herrmann  (supplier of updated libio-html-perl
> package)
>
> (This message was generated automatically at their request; if you
> believe that there is a problem with it please contact the archive
> administrators by mailing ftpmas...@ftp-master.debian.org)
>
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> Format: 1.8
> Date: Sun, 14 Feb 2021 18:19:15 +0100
> Source: libio-html-perl
> Architecture: source
> Version: 1.004-2
> Distribution: unstable
> Urgency: medium
> Maintainer: Debian Perl Group <
> pkg-perl-maintain...@lists.alioth.debian.org>
> Changed-By: gregor herrmann 
> Closes: 982802
> Changes:
>  libio-html-perl (1.004-2) unstable; urgency=medium
>  .
>* Team upload.
>* Fix autopkgtests. Add META.json to test directory.
>  Thanks to Adrian Bunk for the bug report. (Closes: #982802)
> Checksums-Sha1:
>  01f8a956b356baa55dc0c0598696b7b965ef2eea 2299 libio-html-perl_1.004-2.dsc
>  64634ad2f483ef19dfca6498816186afaff7a98b 3500
> libio-html-perl_1.004-2.debian.tar.xz
> Checksums-Sha256:
>  8c3010ac70bddc95aac974925975309cce591b07639a0b8ce173caec05575bb5 2299
> libio-html-perl_1.004-2.dsc
>  f37ea11d8cca48238364480d3beedc3c3576d869f52ae14fc071f1cef95d9f24 3500
> libio-html-perl_1.004-2.debian.tar.xz
> Files:
>  be755439289aa1ca0b8002ed6ae10df2 2299 perl optional
> libio-html-perl_1.004-2.dsc
>  065e920631aeef20f5640d69e6d4cc08 3500 perl optional
> libio-html-perl_1.004-2.debian.tar.xz
>
> -BEGIN PGP SIGNATURE-
>
> iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAmApXAxfFIAALgAo
> aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx
> RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ
> qganlQ/+MU+5V1OdSn7lur1vQ9iVcOzrhXyNslfnIfZk9/GlFRGTk+JDpYiWSgNS
> hKaSy43tNVfZ6a7MW/pSIJEnMlk2y8+7l/eIJSHniObs3PmUYcN4hv7hpE1PbFsv
> CT9XzDOmZDVXe/VwdDZxsC7dVLTlatcEOMzr5hgqXIXljpMa1rFQJLmgDugD7icM
> LSM8swScjl0Z7m7814OZjXNvHOW2fYsbxpWQRIc77ckj3wjkdGxlC5iCwrI0n2Ly
> /vDj42GFBE/+iNFU9gwVI8A/scjAwAO5drmvopjJX1/7AzbHNinqFA0CCBT5EZkB
> 0BRg3b0ZYtjL2qqUC9Ahy6z130ynMOsaZPAxVoBSnIdSweAa6cFZHdx01v36KOIV
> oTpKPqoQpWQkkOfc2aGjJ9ddQARRv3MJ9Brwo2qNGt8fXLpmAe7dMO7kAITwVWj5
> L2CJEPH1q3P4xW9U91nUU6r6gskjqwV/YyoGG/ntWqQI2TP3ptGwhshYoB/AKuDo
> bgqzG3dQDdoWrCTzCVdVVI3ofIOVqoyBRkP9mXBAQx+GzXZeo4D28P2UQlhzv0Nz
> 

Bug#982035: marked as done (tasksel depends on man-pages-it which has been removed)

[Willy nilly]

close #982035

On Sun, Feb 14, 2021 at 5:45 PM Debian Bug Tracking System <
ow...@bugs.debian.org> wrote:

> Your message dated Sun, 14 Feb 2021 17:40:03 +
> with message-id 
> and subject line Bug#982035: fixed in tasksel 3.64
> has caused the Debian Bug report #982035,
> regarding tasksel depends on man-pages-it which has been removed
> to be marked as done.
>
> This means that you claim that the problem has been dealt with.
> If this is not the case it is now your responsibility to reopen the
> Bug report if necessary, and/or fix the problem forthwith.
>
> (NB: If you are a system administrator and have no idea what this
> message is talking about, this may indicate a serious mail system
> misconfiguration somewhere. Please contact ow...@bugs.debian.org
> immediately.)
>
>
> --
> 982035: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982035
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems
>
>
>
> -- Forwarded message --
> From: Paul Gevers 
> To: Debian Bug Tracking System 
> Cc:
> Bcc:
> Date: Fri, 5 Feb 2021 21:02:04 +0100
> Subject: tasksel depends on man-pages-it which has been removed
> Package: tasksel
> Version: 3.63
> Severity: serious
> Justification: not installable
>
> Hi,
>
> man-pages-it has been removed from unstable. Don't ask me how that is
> possible as your package still depends on it, but it happened. Please
> drop the dependency. The RM bug #979034 suggests the data now lives
> elsewhere, albeit I don't know where.
>
> Paul
>
>
>
>
> -- Forwarded message --
> From: Debian FTP Masters 
> To: 982035-cl...@bugs.debian.org
> Cc:
> Bcc:
> Date: Sun, 14 Feb 2021 17:40:03 +
> Subject: Bug#982035: fixed in tasksel 3.64
> Source: tasksel
> Source-Version: 3.64
> Done: Holger Wansing 
>
> We believe that the bug you reported is fixed in the latest version of
> tasksel, which is due to be installed in the Debian FTP archive.
>
> A summary of the changes between this version and the previous one is
> attached.
>
> Thank you for reporting the bug, which will now be closed.  If you
> have further comments please address them to 982...@bugs.debian.org,
> and the maintainer will reopen the bug report if appropriate.
>
> Debian distribution maintenance software
> pp.
> Holger Wansing  (supplier of updated tasksel
> package)
>
> (This message was generated automatically at their request; if you
> believe that there is a problem with it please contact the archive
> administrators by mailing ftpmas...@ftp-master.debian.org)
>
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> Format: 1.8
> Date: Sun, 14 Feb 2021 18:03:39 +0100
> Source: tasksel
> Architecture: source
> Version: 3.64
> Distribution: unstable
> Urgency: medium
> Maintainer: Debian Install System Team 
> Changed-By: Holger Wansing 
> Closes: 981478 982035
> Changes:
>  tasksel (3.64) unstable; urgency=medium
>  .
>* Team upload.
>  .
>[ Holger Wansing ]
>* Remove manpages-it from task-italian task (package has been removed
> from
>  unstable). Closes: #982035.
>  .
>[ Updated debconf translations ]
>* Spanish (es.po) by Javier Fernandez-Sanguino. Closes: #981478
> Checksums-Sha1:
>  81145d080b419335c257fb66cc85167ecb4e6560 17065 tasksel_3.64.dsc
>  daebb2ca502fbf4bae44c1469cfbc03644eb11ec 295008 tasksel_3.64.tar.xz
>  aa46a43a049f7774e5711dfc268750d859329ac3 65617
> tasksel_3.64_amd64.buildinfo
> Checksums-Sha256:
>  8c4d7fac094276078d7680978f147a1a162e2ae9ecd04289f5fd6a6c71716d3b 17065
> tasksel_3.64.dsc
>  b346f617b3b8c58aba8d9196b6c0538569572ab20c70b0f8c1ebb34e4ce01db0 295008
> tasksel_3.64.tar.xz
>  4df987f5097190b164b28e91d43027ff1b6205e9a7ed8e565a8e2460e84cddca 65617
> tasksel_3.64_amd64.buildinfo
> Files:
>  c7b9df296de293a39092ddfc2c801c35 17065 tasks optional tasksel_3.64.dsc
>  7bf4c6469a6b36b5d8484e57745f46c4 295008 tasks optional tasksel_3.64.tar.xz
>  e939d356a1fdbe6f0bb90b57f9921e38 65617 tasks optional
> tasksel_3.64_amd64.buildinfo
>
> -BEGIN PGP SIGNATURE-
>
> iQJJBAEBCgAzFiEESWrG6BRCSzSFCDUpWfGHyhVusHYFAmApWfQVHGh3YW5zaW5n
> QG1haWxib3gub3JnAAoJEFnxh8oVbrB2q9kQAMD3VRMCv8sGwvkuOf7j+kE7v3BH
> SLllehh1ZHhmtfeU6IVQUPcAjIOq+ZJdJQIre/O7PT32migDrG9+vZTuFF8CXm3y
> Gnv3iIEwsHmR82OFZyNf7zd22ZQ553HTQOX8jc5eOx3ZoxyuAF0L/teS1trso0bE
> isJ8ZX9AXJG64vnNV1v+2GQmp8nq/N594dYtnl53VI8IF59Hd7ROovlD/byjeQ07
> iR6KLxwpH18wwyfKvZSBziwVg8h7PgDYDsIwYCQAzgecGzVRRI9sGsebZKVE2B9k
> VDNkyEJe/QNGGUJo2tfqgdYci/fR0HGQzWlLKk4ZSKigrTsqqV+xHqK19UDPM8mF
> A9Af4j3tBlgMX32gDSnzT9xu4R4871AAonR5G1UI2Ib7ofegIwYolybwYLJdBXow
> oZyd+02XatXYzD6wBjig9aHs4DDBCYYlNE8fjZKKct0bsioSl99H0kKBEIK72Tm1
> k6cD/N8YGVCqC9QiZtjS9zOceeovpI1YapzyUA/6fM6KrjClvp7i/kC//3qtfaAH
> UdhZZG2Nfwjx2JvcXJA9m+dELpcUA5a2BYNBVhlr7TdDMbrZ7r7dfyIPvA0Uv+OQ
> z0+ctAqukuxDGMLKzn31pWTR5gamgBZpbw8HrdTCAVVmj5fn2/RM7zCQL69Mdcnh
> rpEan0iPbDmOzEFR
> =nkgk
> -END PGP SIGNATURE-

Bug#976045: marked as done (bind9: flaky autopkgtest on ci.debian.net)

[Willy nilly]

close #976045

On Sun, Feb 14, 2021 at 8:21 PM Debian Bug Tracking System <
ow...@bugs.debian.org> wrote:

> Your message dated Sun, 14 Feb 2021 20:17:38 +
> with message-id 
> and subject line Bug#976045: fixed in bind9 1:9.16.11-3
> has caused the Debian Bug report #976045,
> regarding bind9: flaky autopkgtest on ci.debian.net
> to be marked as done.
>
> This means that you claim that the problem has been dealt with.
> If this is not the case it is now your responsibility to reopen the
> Bug report if necessary, and/or fix the problem forthwith.
>
> (NB: If you are a system administrator and have no idea what this
> message is talking about, this may indicate a serious mail system
> misconfiguration somewhere. Please contact ow...@bugs.debian.org
> immediately.)
>
>
> --
> 976045: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976045
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems
>
>
>
> -- Forwarded message --
> From: Paul Gevers 
> To: sub...@bugs.debian.org
> Cc:
> Bcc:
> Date: Sat, 28 Nov 2020 21:04:16 +0100
> Subject: bind9: flaky autopkgtest on ci.debian.net
> Source: bind9
> Version: 1:9.11.5.P4+dfsg-5.1+deb10u2
> Severity: serious
> X-Debbugs-CC: debian...@lists.debian.org
> User: debian...@lists.debian.org
> Usertags: flaky
> Control: found -1 1:9.16.8-1
>
> Dear maintainer(s),
>
> bind9 has an autopkgtest, great. However, your test (correctly) has the
> restriction needs-internet, but it doesn't retry the part where it uses
> the internet.  On ci.debian.net, we're seeing (e.g. [1]) regular
> failures in the internet based test. Can you please make the test more
> robust against network issues? E.g. a couple of retries with some time
> in between before failing?
>
> Because the unstable-to-testing migration software now blocks on
> regressions in testing, flaky tests, i.e. tests that flip between
> passing and failing without changes to the list of installed packages,
> are causing people unrelated to your package to spend time on these
> tests.
>
> I copied the output at the bottom of this report.
>
> Please do get in touch if we need to dive into this together.
>
> Paul
>
> [1] https://ci.debian.net/packages/b/bind9/testing/amd64/
>
> https://ci.debian.net/data/autopkgtest/stable/armhf/b/bind9/8471318/log.gz
>
> autopkgtest [21:59:15]: test simpletest: [---
>
> ; <<>> DiG 9.11.5-P4-5.1+deb10u2-Debian <<>> -x 127.0.0.1 @127.0.0.1
> ;; global options: +cmd
> ;; Got answer:
> ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 53032
> ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 1, ADDITIONAL: 3
>
> ;; OPT PSEUDOSECTION:
> ; EDNS: version: 0, flags:; udp: 4096
> ; COOKIE: 20d019dc324ffa05fbfc9b425fc176b5e6f0b962dccc8e3c (good)
> ;; QUESTION SECTION:
> ;1.0.0.127.in-addr.arpa.IN  PTR
>
> ;; ANSWER SECTION:
> 1.0.0.127.in-addr.arpa. 604800  IN  PTR localhost.
>
> ;; AUTHORITY SECTION:
> 127.in-addr.arpa.   604800  IN  NS  localhost.
>
> ;; ADDITIONAL SECTION:
> localhost.  604800  IN  A   127.0.0.1
> localhost.  604800  IN  ::1
>
> ;; Query time: 0 msec
> ;; SERVER: 127.0.0.1#53(127.0.0.1)
> ;; WHEN: Fri Nov 27 21:59:17 UTC 2020
> ;; MSG SIZE  rcvd: 160
>
> Checking for DNSSEC validation status of internetsociety.org
> autopkgtest [21:59:17]: test simpletest: ---]
>
>
>
> -- Forwarded message --
> From: Debian FTP Masters 
> To: 976045-cl...@bugs.debian.org
> Cc:
> Bcc:
> Date: Sun, 14 Feb 2021 20:17:38 +
> Subject: Bug#976045: fixed in bind9 1:9.16.11-3
> Source: bind9
> Source-Version: 1:9.16.11-3
> Done: Ondřej Surý 
>
> We believe that the bug you reported is fixed in the latest version of
> bind9, which is due to be installed in the Debian FTP archive.
>
> A summary of the changes between this version and the previous one is
> attached.
>
> Thank you for reporting the bug, which will now be closed.  If you
> have further comments please address them to 976...@bugs.debian.org,
> and the maintainer will reopen the bug report if appropriate.
>
> Debian distribution maintenance software
> pp.
> Ondřej Surý  (supplier of updated bind9 package)
>
> (This message was generated automatically at their request; if you
> believe that there is a problem with it please contact the archive
> administrators by mailing ftpmas...@ftp-master.debian.org)
>
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> Format: 1.8
> Date: Sun, 14 Feb 2021 20:04:39 +0100
> Source: bind9
> Architecture: source
> Version: 1:9.16.11-3
> Distribution: unstable
> Urgency: medium
> Maintainer: Debian DNS Team 
> Changed-By: Ondřej Surý 
> Closes: 976045
> Changes:
>  bind9 (1:9.16.11-3) unstable; urgency=medium
>  .
>* Split the simple validation test to separate file and mark it as flaky
>  (Closes: #976045)
> Checksums-Sha1:
>  f47b6581c02134952c9066405daa09b69bb84e95 2992 bind9_9.16.11-3.dsc
>  

Bug#976045: bind9: flaky autopkgtest on ci.debian.net

[Ondřej Surý]

Hi Ivo,

thanks for the testing.

I split the test into two - simpletest and validation, marked the
validation test as flaky and then I also added a simple repetition around
the validation command to allow `named` to bootstrap the validation chain
first and only fail if the `dig` fails for 10th time.

This should fix the autopkgtest for now. Any test that requires DNS is
flaky by definition.

Cheers,
Ondrej

On Tue, 9 Feb 2021 at 19:11, Ivo De Decker  wrote:

> Hi,
>
> On Mon, Dec 07, 2020 at 09:12:25AM +0100, Ondřej Surý wrote:
> >Hi Paul,
> >I am pretty sure the culprit is this upstream
> >issue: https://gitlab.isc.org/isc-projects/bind9/-/issues/2305
> >So, the bug should resolve itself when BIND 9.16.10 is uploaded to the
> >archive.  If not, I'll modify the autopkgtest.
> >Ondrej
>
> Testing now has 1:9.16.11-2. I retriggered the tests a number of times
> earlier
> today, and one of them failed:
>
> https://ci.debian.net/packages/b/bind9/testing/amd64/
>
> https://ci.debian.net/data/autopkgtest/testing/amd64/b/bind9/10370897/log.gz
>
> Cheers,
>
> Ivo
>
>

Bug#763824: (no subject)

[jaydenjuan08eya22]

Sent from vivo smartphone

Bug#980583: marked as pending in ruby-coffee-rails

[Antonio Terceiro]

Control: tag -1 pending

Hello,

Bug #980583 in ruby-coffee-rails 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/ruby-team/ruby-coffee-rails/-/commit/ca323c58aa02e3b134435b3c1e65b06f695186c3


Fix test failure due to updated ruby-coffee-script

Closes: #980583


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/980583

Processed: Bug#980583 marked as pending in ruby-coffee-rails

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #980583 [src:ruby-coffee-rails] ruby-coffee-rails: FTBFS: tests failed
Added tag(s) pending.

-- 
980583: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980583
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#976045: marked as done (bind9: flaky autopkgtest on ci.debian.net)

[Debian Bug Tracking System]

Your message dated Sun, 14 Feb 2021 20:17:38 +
with message-id 
and subject line Bug#976045: fixed in bind9 1:9.16.11-3
has caused the Debian Bug report #976045,
regarding bind9: flaky autopkgtest on ci.debian.net
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
976045: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976045
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: bind9
Version: 1:9.11.5.P4+dfsg-5.1+deb10u2
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: flaky
Control: found -1 1:9.16.8-1

Dear maintainer(s),

bind9 has an autopkgtest, great. However, your test (correctly) has the
restriction needs-internet, but it doesn't retry the part where it uses
the internet.  On ci.debian.net, we're seeing (e.g. [1]) regular
failures in the internet based test. Can you please make the test more
robust against network issues? E.g. a couple of retries with some time
in between before failing?

Because the unstable-to-testing migration software now blocks on
regressions in testing, flaky tests, i.e. tests that flip between
passing and failing without changes to the list of installed packages,
are causing people unrelated to your package to spend time on these
tests.

I copied the output at the bottom of this report.

Please do get in touch if we need to dive into this together.

Paul

[1] https://ci.debian.net/packages/b/bind9/testing/amd64/

https://ci.debian.net/data/autopkgtest/stable/armhf/b/bind9/8471318/log.gz

autopkgtest [21:59:15]: test simpletest: [---

; <<>> DiG 9.11.5-P4-5.1+deb10u2-Debian <<>> -x 127.0.0.1 @127.0.0.1
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 53032
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 1, ADDITIONAL: 3

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
; COOKIE: 20d019dc324ffa05fbfc9b425fc176b5e6f0b962dccc8e3c (good)
;; QUESTION SECTION:
;1.0.0.127.in-addr.arpa.IN  PTR

;; ANSWER SECTION:
1.0.0.127.in-addr.arpa. 604800  IN  PTR localhost.

;; AUTHORITY SECTION:
127.in-addr.arpa.   604800  IN  NS  localhost.

;; ADDITIONAL SECTION:
localhost.  604800  IN  A   127.0.0.1
localhost.  604800  IN  ::1

;; Query time: 0 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Fri Nov 27 21:59:17 UTC 2020
;; MSG SIZE  rcvd: 160

Checking for DNSSEC validation status of internetsociety.org
autopkgtest [21:59:17]: test simpletest: ---]
--- End Message ---
--- Begin Message ---
Source: bind9
Source-Version: 1:9.16.11-3
Done: Ondřej Surý 

We believe that the bug you reported is fixed in the latest version of
bind9, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 976...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Ondřej Surý  (supplier of updated bind9 package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 14 Feb 2021 20:04:39 +0100
Source: bind9
Architecture: source
Version: 1:9.16.11-3
Distribution: unstable
Urgency: medium
Maintainer: Debian DNS Team 
Changed-By: Ondřej Surý 
Closes: 976045
Changes:
 bind9 (1:9.16.11-3) unstable; urgency=medium
 .
   * Split the simple validation test to separate file and mark it as flaky
 (Closes: #976045)
Checksums-Sha1:
 f47b6581c02134952c9066405daa09b69bb84e95 2992 bind9_9.16.11-3.dsc
 bc83e32767774feeb914fa77d2b78bb2ae8d8070 78884 bind9_9.16.11-3.debian.tar.xz
 2ab7e3fa78cb62979608460ece27ba431196dbf6 15119 bind9_9.16.11-3_amd64.buildinfo
Checksums-Sha256:
 138d8b80a8cccdf2061ecb16df16f4cc8b83e07196e1d4ee75b893f1aa64baea 2992 
bind9_9.16.11-3.dsc
 2a7fb2173496fb6c21d01a80d126cc490b0337d2d1c78c3cb99161b61aec9e3b 78884 
bind9_9.16.11-3.debian.tar.xz
 54fa9c5a211b4fb2cf5fe5bfd284af02282f90892739047bd6aa1bf92c43a71b 15119 
bind9_9.16.11-3_amd64.buildinfo
Files:
 53aaafa98274f81483af6b7a3223126e 2992 net optional bind9_9.16.11-3.dsc
 fc733c23d3fa7551f4fa7b1072225650 78884 net optional 
bind9_9.16.11-3.debian.tar.xz
 9485c68e4bca9ae7325015c0a18ced66 15119 net optional 

Processed: retitle 979609 to swt4-gtk segfaults on ppc64el

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> retitle 979609 swt4-gtk segfaults on ppc64el
Bug #979609 [src:swt4-gtk] swt4-gtk: segfaults with openjdk
Changed Bug title to 'swt4-gtk segfaults on ppc64el' from 'swt4-gtk: segfaults 
with openjdk'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
979609: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979609
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#979866: marked as done (knxd FTBFS everywhere: autoconf issues)

[Debian Bug Tracking System]

Your message dated Sun, 14 Feb 2021 21:57:11 +0200
with message-id <20210214195710.GA20085@localhost>
and subject line Re: Bug#979866: knxd FTBFS everywhere: autoconf issues
has caused the Debian Bug report #979866,
regarding knxd FTBFS everywhere: autoconf issues
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
979866: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979866
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: knxd
Version: 0.14.41-1
Severity: serious
Tags: ftbfs

knxd fails to build from source for all attempted architectures on the
buildds. A build log usually ends with:

|dh_autoreconf -a
|  find ! -ipath "./debian/*" -a ! \( -path '*/.git/*' -o -path '*/.hg/*' -o 
-path '*/.bzr/*' -o -path '*/.svn/*' -o -path '*/CVS/*' \) -a  -type f -exec 
md5sum {} + -o -type l -printf "symlink  %p
| " > debian/autoreconf.before
|  grep -q ^XDT_ configure.ac
|  autoreconf -f -i
| configure.ac:30: error: AC_INIT should be called with package and version 
arguments
| /usr/share/aclocal-1.16/init.m4:29: AM_INIT_AUTOMAKE is expanded from...
| configure.ac:30: the top level
| autom4te: /usr/bin/m4 failed with exit status: 1
| aclocal: error: /usr/bin/autom4te failed with exit status: 1
| autoreconf: aclocal failed with exit status: 1
|  find ! -ipath "./debian/*" -a ! \( -path '*/.git/*' -o -path '*/.hg/*' -o 
-path '*/.bzr/*' -o -path '*/.svn/*' -o -path '*/CVS/*' \) -a  -type f -exec 
md5sum {} + -o -type l -printf "symlink  %p
| " > debian/autoreconf.after
| dh_autoreconf: error: autoreconf -f -i returned exit code 1
| make: *** [debian/rules:14: build-arch] Error 25

Could this be related to autoconf 2.70?

Helmut
--- End Message ---
--- Begin Message ---
Version: 0.14.46-1

On Mon, Jan 11, 2021 at 06:56:32AM +0100, Helmut Grohne wrote:
> Source: knxd
> Version: 0.14.41-1
> Severity: serious
> Tags: ftbfs
> 
> knxd fails to build from source for all attempted architectures on the
> buildds. A build log usually ends with:
> 
> |dh_autoreconf -a
> |  find ! -ipath "./debian/*" -a ! \( -path '*/.git/*' -o -path '*/.hg/*' -o 
> -path '*/.bzr/*' -o -path '*/.svn/*' -o -path '*/CVS/*' \) -a  -type f -exec 
> md5sum {} + -o -type l -printf "symlink  %p
> | " > debian/autoreconf.before
> |  grep -q ^XDT_ configure.ac
> |  autoreconf -f -i
> | configure.ac:30: error: AC_INIT should be called with package and version 
> arguments
> | /usr/share/aclocal-1.16/init.m4:29: AM_INIT_AUTOMAKE is expanded from...
> | configure.ac:30: the top level
> | autom4te: /usr/bin/m4 failed with exit status: 1
> | aclocal: error: /usr/bin/autom4te failed with exit status: 1
> | autoreconf: aclocal failed with exit status: 1
> |  find ! -ipath "./debian/*" -a ! \( -path '*/.git/*' -o -path '*/.hg/*' -o 
> -path '*/.bzr/*' -o -path '*/.svn/*' -o -path '*/CVS/*' \) -a  -type f -exec 
> md5sum {} + -o -type l -printf "symlink  %p
> | " > debian/autoreconf.after
> | dh_autoreconf: error: autoreconf -f -i returned exit code 1
> | make: *** [debian/rules:14: build-arch] Error 25
>...

This seems fixed in 0.14.46-1:
https://buildd.debian.org/status/logs.php?pkg=knxd=0.14.46-1

> Helmut

cu
Adrian--- End Message ---

Bug#982814: manpages-it-dev: missing Breaks+Replaces: manpages-it (<< 4.9.1)

[Andreas Beckmann]

Package: manpages-it-dev
Version: 4.9.1-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces

>From the attached log (scroll to the bottom...):

  Preparing to unpack .../manpages-it-dev_4.9.1-2_all.deb ...
  Unpacking manpages-it-dev (4.9.1-2) ...
  dpkg: error processing archive 
/var/cache/apt/archives/manpages-it-dev_4.9.1-2_all.deb (--unpack):
   trying to overwrite '/usr/share/man/it/man2/_syscall.2.gz', which is also in 
package manpages-it 3.73-2.1
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/manpages-it-dev_4.9.1-2_all.deb

The following manpages were moved to the new -it-dev package:

usr/share/man/it/man2/_syscall.2.gz
usr/share/man/it/man2/adjtimex.2.gz
usr/share/man/it/man2/fork.2.gz
usr/share/man/it/man2/mount.2.gz
usr/share/man/it/man2/readv.2.gz
usr/share/man/it/man2/swapoff.2.gz
usr/share/man/it/man2/swapon.2.gz
usr/share/man/it/man2/symlink.2.gz
usr/share/man/it/man2/symlinkat.2.gz
usr/share/man/it/man2/sync.2.gz
usr/share/man/it/man2/sysfs.2.gz
usr/share/man/it/man2/sysinfo.2.gz
usr/share/man/it/man2/umask.2.gz
usr/share/man/it/man2/umount.2.gz
usr/share/man/it/man2/umount2.2.gz
usr/share/man/it/man2/uname.2.gz
usr/share/man/it/man2/unimplemented.2.gz
usr/share/man/it/man2/unlink.2.gz
usr/share/man/it/man2/unlinkat.2.gz
usr/share/man/it/man2/uselib.2.gz
usr/share/man/it/man2/ustat.2.gz
usr/share/man/it/man2/utime.2.gz
usr/share/man/it/man2/utimes.2.gz
usr/share/man/it/man2/vfork.2.gz
usr/share/man/it/man2/vhangup.2.gz
usr/share/man/it/man2/vm86.2.gz
usr/share/man/it/man2/wait.2.gz
usr/share/man/it/man2/wait3.2.gz
usr/share/man/it/man2/wait4.2.gz
usr/share/man/it/man2/waitpid.2.gz
usr/share/man/it/man2/write.2.gz
usr/share/man/it/man2/writev.2.gz
usr/share/man/it/man3/adjtime.3.gz
usr/share/man/it/man3/daemon.3.gz
usr/share/man/it/man3/err.3.gz
usr/share/man/it/man3/exit.3.gz
usr/share/man/it/man3/undocumented.3.gz


cheers,

Andreas


manpages-it=3.73-2.1_manpages-it-dev=4.9.1-2.log.gz
Description: application/gzip

Processed: bug 982723 is forwarded to https://github.com/rails/rails-html-sanitizer/issues/111

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forwarded 982723 https://github.com/rails/rails-html-sanitizer/issues/111
Bug #982723 [src:ruby-rails-html-sanitizer] ruby-rails-html-sanitizer: FTBFS: 
ERROR: Test "ruby2.7" failed.
Set Bug forwarded-to-address to 
'https://github.com/rails/rails-html-sanitizer/issues/111'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
982723: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982723
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: firehol: FTBFS: dh_auto_test: error: make -j1 check VERBOSE=1 returned exit code 2

[Debian Bug Tracking System]

Processing control commands:

> tag -1 moreinfo confirmed
Bug #982719 [src:firehol] firehol: FTBFS: dh_auto_test: error: make -j1 check 
VERBOSE=1 returned exit code 2
Added tag(s) confirmed and moreinfo.

-- 
982719: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982719
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#982719: firehol: FTBFS: dh_auto_test: error: make -j1 check VERBOSE=1 returned exit code 2

[Dennis Filder]

Control: tag -1 moreinfo confirmed

I could reproduce this, but only in a bullseye chroot build
environment with a running buster (4.19) kernel.  I haven't tried with
a bullseye kernel + bullseye chroot.

The build log in the bug report states similarly:

 Kernel: Linux 4.19.0-6-cloud-amd64 #1 SMP Debian 4.19.67-2+deb10u2 
(2019-11-11) amd64 (x86_64)

I'd also like to point out this snippet from the ERRORS section of the
manpage for unshare(2):

   EPERM (since Linux 3.9)
  CLONE_NEWUSER was specified in flags and the caller is
  in a chroot environment (i.e., the caller's root direc‐
  tory does not match the root directory of the mount
  namespace in which it resides).

This is important because the test suite executes /bin/unshare with -r
in firehol-3.1.6+ds/tests/tools/newns which then calls
unshare(CLONE_NEWUSER):

  $ strace -e trace=unshare unshare -r unshare -n -m /bin/date
  unshare(CLONE_NEWUSER)  = 0
  unshare(CLONE_NEWNS|CLONE_NEWNET)   = 0

In fact under all kernels I've tried (4.19, 5.10) this command even
when run as root always fails with "Operation not permitted":

  chroot /chrootenvdir /bin/unshare -r /bin/date

My understanding of the interaction of chroot and
unshare(2)/namespaces in general is incomplete, but this to me
indicates the test suite of firehol in its current form simply cannot
be run in a chroot environment (at least on 4.19 kernels, but probably
also later ones) and should be disabled until the unshare backend for
sbuild has matured enough to be used on the build servers.

@Jerome: Could you try to get someone from either the Debian Kernel
Team or the sbuild maintainers to take a look at this?  If you get no
answer there then make sure notify the release team as they may have
to waive this one.

Regards,
Dennis.

Bug#971129: shim-signed: FTBFS: build-dependency not installable: shim-unsigned (= 15+1533136590.3beb971-7)

[Ivo De Decker]

Control: tags 978521 pending

Hi Steve,

On Fri, Feb 12, 2021 at 01:35:52AM +, Steve McIntyre wrote:
> On Tue, Feb 09, 2021 at 04:26:02PM +0100, Ivo De Decker wrote:
> >Hi Steve,
> >
> >On Sun, Sep 27, 2020 at 08:39:53PM +0200, Lucas Nussbaum wrote:
> >> During a rebuild of all packages in sid, your package failed to build
> >> on amd64.
> >
> >[...]
> >
> >> > The following packages have unmet dependencies:
> >> >  sbuild-build-depends-main-dummy : Depends: shim-unsigned (= 
> >> > 15+1533136590.3beb971-7) but it is not going to be installed
> >
> >What is the status of shim(-signed) for bullseye?
> >
> >shim-unsigned has been changed, but there is no corresponding shim-signed
> >(yet). I assume a new signature from microsoft is needed. Or are there more
> >changes to shim-unsigned needed first?
> 
> There are some other changes coming, not least switching compiler to
> gcc-10 now we've stabilised.

I'm tagging #978521 ("shim: non-standard gcc/g++ used for build (gcc-9)") as
pending to indicate that you're planning to switch to gcc-10.

> I'm working on new shim uploads at the
> moment, but there's a couple of upstream patches we'll need to take as
> well yet I think. It'll be coming soon, I promise.

Could you clarify the timing for this, especially the timeline for getting the
signature from Microsoft (as far as that can be predicted)? I'm trying to
assess if this could become a blocker wrt the actual release. Is it an option
to release with the current version of shim-signed (ie the one that's also in
buster) if we don't get the signature in time?

Cheers,

Ivo

Processed: Re: shim-signed: FTBFS: build-dependency not installable: shim-unsigned (= 15+1533136590.3beb971-7)

[Debian Bug Tracking System]

Processing control commands:

> tags 978521 pending
Bug #978521 [shim] shim: non-standard gcc/g++ used for build (gcc-9)
Added tag(s) pending.

-- 
971129: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971129
978521: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978521
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#982807: datovka: version too old to be useful

[Ondřej Surý]

Package: datovka
Version: 4.9.3-2.1
Severity: grave
Justification: renders package unusable

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

The version in testing / unstable is too old to be really usable.

It's better to not have it in next stable Debian.

Ondrej

- -- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.19.0-13-amd64 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_IE:en
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages datovka depends on:
ii  libc6 2.31-9
ii  libgcc-s1 [libgcc1]   11-20210130-1
pn  libisds5  
ii  libqt5core5a  5.15.2+dfsg-4
ii  libqt5gui55.15.2+dfsg-4
ii  libqt5network55.15.2+dfsg-4
ii  libqt5printsupport5   5.15.2+dfsg-4
ii  libqt5sql55.15.2+dfsg-4
ii  libqt5sql5-sqlite 5.15.2+dfsg-4
ii  libqt5svg55.15.2-2
ii  libqt5widgets55.15.2+dfsg-4
ii  libssl1.1 1.1.1i-3
ii  libstdc++610.2.1-6
pn  qttranslations5-l10n  

datovka recommends no packages.

datovka suggests no packages.

-BEGIN PGP SIGNATURE-

iQKTBAEBCgB9FiEEw2Gx4wKVQ+vGJel9g3Kkd++uWcIFAmApcOVfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEMz
NjFCMUUzMDI5NTQzRUJDNjI1RTk3RDgzNzJBNDc3RUZBRTU5QzIACgkQg3Kkd++u
WcKSrQ//dOlvoJf6+mbqUDS1PIz9cLna3atd55yjCUaLUwuvtGHb9RrBjuS9jzDt
+8WzjhT8VPbjmnRTlsJsVPq6pJa9E4BpFLWbR/A1PGOoYJxSOw9FNTg01ykqtFOd
8q/pXyXVNtI7TGs29VhRLGuzLoVZR5vQeKT3Q3FKvYZtf4wy4ZBV/untY8yzErqd
AsAK451M6SQ8S1X3uB2R20qFyes/Fpsa2XGcocBdG2gPDS9fLySyBLgis4EwlcWO
c5LrnWWMhDmKzqjYDdHk1SrzmdUZeb0MZtJD50dnop4Gh4L0m2DG7Do5UKWnJOjM
PC00eAbJBqQz2O57ILU/9ciy5mow0Lzib+eqCRtiQT8KUGc9d68yQy14hc0Uk/NR
Se1DlHOewwKx6i+cRyxdnkL1k+5WrwxzbyQPHr94S5p51t7bhG4qZf7l13d/hlXr
7TN4mnSTLtfXRKUAKdiVqizEo5UFA9DneINYtRR/IGDzFN91hmgD8tzxqqHxvMjJ
cUAPq3J1hdVBIbeoYYEfhP+mgyTSQMrS4uFvEikQSvj5Z84AM8FYOYXOTAmKER7W
RsAM49LTpBfZF21lL9FsOXDdRRK0YW0fiMY1b5PdxK6M+HEhOUrhn7OMcovILg20
+fW1h8tOoAkYd/gZa3S28mrQbSnDvyjM0uRntKnsYTXbsIolaT8=
=ppTl
-END PGP SIGNATURE-

Processed: Re: Bug#981600: nghttp2: util_localtime_date test fails in arch-only build

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #981600 [src:nghttp2] nghttp2: util_localtime_date test fails in arch-only 
build
Severity set to 'important' from 'serious'

-- 
981600: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981600
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#981600: nghttp2: util_localtime_date test fails in arch-only build

[Ivo De Decker]

Control: severity -1 important

Hi,

On Sun, Feb 07, 2021 at 09:12:53PM +0100, Helmut Grohne wrote:
> On Sun, Feb 07, 2021 at 08:51:36PM +0100, Chris Hofstaedtler wrote:
> > I'm just passing by, but a local rebuild with `sbuild -d unstable
> > -j8 --no-arch-all` did not show this problem (on amd64). There has
> > to be more to it.
> 
> Thank you. I retried it to day (sbuild -d unstable --no-arch-all
> nghttp2 on amd64) and it failed in the same way. I'm left puzzled what
> could be different here. One aspect that certainly is not entirely usual
> is that my chroot lives on a large tmpfs. Could that pose any problems?
> 
> Any other details I could add to help better understand the issue?

There was an upload of nghttp2 yesterday, which built fine on the buildds, so
I'm downgrading this bug.

Cheers,

Ivo

Processed: severity of 976354 is important

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 976354 important
Bug #976354 [git] git - tests fail with dash
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
976354: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976354
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#982559: xscorch Build-Depends on libreadline-gplv2-dev which has been removed

[Chris Hofstaedtler]

* peter green  [210214 17:52]:
> I would thus propose simply dropping the build-dependency, a debdiff doing 
> that is
> attached, I may or may not NMU it later.

I'd suggest you do the NMU (soon), as Jacob apparently hasn't been
active for a while.

Thanks,
Chris

Bug#982802: marked as done (libio-html-perl: autopkgtest failure)

[Debian Bug Tracking System]

Your message dated Sun, 14 Feb 2021 17:50:29 +
with message-id 
and subject line Bug#982802: fixed in libio-html-perl 1.004-2
has caused the Debian Bug report #982802,
regarding libio-html-perl: autopkgtest failure
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
982802: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982802
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libio-html-perl
Version: 1.004-1
Severity: serious

https://ci.debian.net/data/autopkgtest/testing/amd64/libi/libio-html-perl/10422807/log.gz

...
t/00-all_prereqs.t .. 
not ok 1 - opened META.json
1..1
Failed 1/1 subtests 
...
Test Summary Report
---
t/00-all_prereqs.t (Wstat: 0 Tests: 1 Failed: 1)
  Failed test:  1
Files=5, Tests=141,  1 wallclock secs ( 0.05 usr  0.01 sys +  0.33 cusr  0.03 
csys =  0.42 CPU)
Result: FAIL
autopkgtest [15:04:02]: test autodep8-perl-build-deps: ---]
autopkgtest [15:04:02]: test autodep8-perl-build-deps:  - - - - - - - - - - 
results - - - - - - - - - -
autodep8-perl-build-deps FAIL non-zero exit status 1
...
--- End Message ---
--- Begin Message ---
Source: libio-html-perl
Source-Version: 1.004-2
Done: gregor herrmann 

We believe that the bug you reported is fixed in the latest version of
libio-html-perl, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 982...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
gregor herrmann  (supplier of updated libio-html-perl 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 14 Feb 2021 18:19:15 +0100
Source: libio-html-perl
Architecture: source
Version: 1.004-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Perl Group 
Changed-By: gregor herrmann 
Closes: 982802
Changes:
 libio-html-perl (1.004-2) unstable; urgency=medium
 .
   * Team upload.
   * Fix autopkgtests. Add META.json to test directory.
 Thanks to Adrian Bunk for the bug report. (Closes: #982802)
Checksums-Sha1:
 01f8a956b356baa55dc0c0598696b7b965ef2eea 2299 libio-html-perl_1.004-2.dsc
 64634ad2f483ef19dfca6498816186afaff7a98b 3500 
libio-html-perl_1.004-2.debian.tar.xz
Checksums-Sha256:
 8c3010ac70bddc95aac974925975309cce591b07639a0b8ce173caec05575bb5 2299 
libio-html-perl_1.004-2.dsc
 f37ea11d8cca48238364480d3beedc3c3576d869f52ae14fc071f1cef95d9f24 3500 
libio-html-perl_1.004-2.debian.tar.xz
Files:
 be755439289aa1ca0b8002ed6ae10df2 2299 perl optional libio-html-perl_1.004-2.dsc
 065e920631aeef20f5640d69e6d4cc08 3500 perl optional 
libio-html-perl_1.004-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAmApXAxfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx
RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ
qganlQ/+MU+5V1OdSn7lur1vQ9iVcOzrhXyNslfnIfZk9/GlFRGTk+JDpYiWSgNS
hKaSy43tNVfZ6a7MW/pSIJEnMlk2y8+7l/eIJSHniObs3PmUYcN4hv7hpE1PbFsv
CT9XzDOmZDVXe/VwdDZxsC7dVLTlatcEOMzr5hgqXIXljpMa1rFQJLmgDugD7icM
LSM8swScjl0Z7m7814OZjXNvHOW2fYsbxpWQRIc77ckj3wjkdGxlC5iCwrI0n2Ly
/vDj42GFBE/+iNFU9gwVI8A/scjAwAO5drmvopjJX1/7AzbHNinqFA0CCBT5EZkB
0BRg3b0ZYtjL2qqUC9Ahy6z130ynMOsaZPAxVoBSnIdSweAa6cFZHdx01v36KOIV
oTpKPqoQpWQkkOfc2aGjJ9ddQARRv3MJ9Brwo2qNGt8fXLpmAe7dMO7kAITwVWj5
L2CJEPH1q3P4xW9U91nUU6r6gskjqwV/YyoGG/ntWqQI2TP3ptGwhshYoB/AKuDo
bgqzG3dQDdoWrCTzCVdVVI3ofIOVqoyBRkP9mXBAQx+GzXZeo4D28P2UQlhzv0Nz
CE74l8g/JA0ewTai+E08SyxvGYvauzGU/gI++8VfVn5nJxaMDuVxO/rDeGBkLQq7
LMFi5GTNXttK+pjuvzlJaHVBAZiyymEyQhvhNdMM0Bv8N8LKuGE=
=RotK
-END PGP SIGNATURE End Message ---

Processed: tagging 982170

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 982170 + patch
Bug #982170 [src:libassuan] libassuan: autopkgtest regression: undefined 
reference to symbol 'gpg_strerror@@GPG_ERROR_1.0'
Added tag(s) patch.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
982170: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982170
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#982740: pulseaudio: FTBFS on ppc64el

[Andres Salomon]

On Sun, 14 Feb 2021 19:27:03 +0200
Adrian Bunk  wrote:
> > 
> > FAIL: cpu-volume-test
> > =
> > 
> > Running suite(s): CPU
> > 0%: Checks: 1, Failures: 1, Errors: 0
> > tests/cpu-volume-test.c:81:F:svolume:svolume_orc_test:0: Failed
> > FAIL cpu-volume-test (exit status: 1)
> > 
> > 
> > 
> > It's worth noting that 14.1-1 built just fine on ppc64el, and the
> > only non-debian change between 14.1 and 14.2 is this:
> >...  
> 
> Both versions fail for me the same way on plummer.
> 
> Adding debian-powerpc so that a porter can check.
> 
> cu
> Adrian

Thanks for verifying. Building (either version) with an older version of
the 'check' package would be the next step, so we can narrow down
what's breaking it.

Bug#982059: Bug#982372: Bug#982059: manpages-de: procps: File sconflict between procps and manpages-de

[Helge Kreutzmann]

Hello Craig,
On Sun, Feb 14, 2021 at 09:29:12PM +1100, Craig Small wrote:
> OK, found a minor problem.  The procps version needs an epoch to correctly
> match. Not 3.3.17-1 but 2:3.3.17-1

First things first: manpages-l10n passed NEW!

To minimize the impact, I suggest that I prepare and upload 4.9.1-3, 
with just the corrected epoch for procps.

If you have any (further) comments on this, then please let me know
asap, otherwise I perform the upload latest tomorrow evening. I'll
update the unblock request accordingly.

I suggest that manpages-l10n 4.9.2 is not shipped, I also did not have
the time to investigate the build failure.

Thanks for spotting and feedback.

Greetings

   Helge
-- 
  Dr. Helge Kreutzmann deb...@helgefjell.de
   Dipl.-Phys.   http://www.helgefjell.de/debian.php
64bit GNU powered gpg signed mail preferred
   Help keep free software "libre": http://www.ffii.de/


signature.asc
Description: PGP signature

Bug#982035: marked as done (tasksel depends on man-pages-it which has been removed)

[Debian Bug Tracking System]

Your message dated Sun, 14 Feb 2021 17:40:03 +
with message-id 
and subject line Bug#982035: fixed in tasksel 3.64
has caused the Debian Bug report #982035,
regarding tasksel depends on man-pages-it which has been removed
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
982035: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982035
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: tasksel
Version: 3.63
Severity: serious
Justification: not installable

Hi,

man-pages-it has been removed from unstable. Don't ask me how that is
possible as your package still depends on it, but it happened. Please
drop the dependency. The RM bug #979034 suggests the data now lives
elsewhere, albeit I don't know where.

Paul



OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: tasksel
Source-Version: 3.64
Done: Holger Wansing 

We believe that the bug you reported is fixed in the latest version of
tasksel, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 982...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Holger Wansing  (supplier of updated tasksel package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 14 Feb 2021 18:03:39 +0100
Source: tasksel
Architecture: source
Version: 3.64
Distribution: unstable
Urgency: medium
Maintainer: Debian Install System Team 
Changed-By: Holger Wansing 
Closes: 981478 982035
Changes:
 tasksel (3.64) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Holger Wansing ]
   * Remove manpages-it from task-italian task (package has been removed from
 unstable). Closes: #982035.
 .
   [ Updated debconf translations ]
   * Spanish (es.po) by Javier Fernandez-Sanguino. Closes: #981478
Checksums-Sha1:
 81145d080b419335c257fb66cc85167ecb4e6560 17065 tasksel_3.64.dsc
 daebb2ca502fbf4bae44c1469cfbc03644eb11ec 295008 tasksel_3.64.tar.xz
 aa46a43a049f7774e5711dfc268750d859329ac3 65617 tasksel_3.64_amd64.buildinfo
Checksums-Sha256:
 8c4d7fac094276078d7680978f147a1a162e2ae9ecd04289f5fd6a6c71716d3b 17065 
tasksel_3.64.dsc
 b346f617b3b8c58aba8d9196b6c0538569572ab20c70b0f8c1ebb34e4ce01db0 295008 
tasksel_3.64.tar.xz
 4df987f5097190b164b28e91d43027ff1b6205e9a7ed8e565a8e2460e84cddca 65617 
tasksel_3.64_amd64.buildinfo
Files:
 c7b9df296de293a39092ddfc2c801c35 17065 tasks optional tasksel_3.64.dsc
 7bf4c6469a6b36b5d8484e57745f46c4 295008 tasks optional tasksel_3.64.tar.xz
 e939d356a1fdbe6f0bb90b57f9921e38 65617 tasks optional 
tasksel_3.64_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJJBAEBCgAzFiEESWrG6BRCSzSFCDUpWfGHyhVusHYFAmApWfQVHGh3YW5zaW5n
QG1haWxib3gub3JnAAoJEFnxh8oVbrB2q9kQAMD3VRMCv8sGwvkuOf7j+kE7v3BH
SLllehh1ZHhmtfeU6IVQUPcAjIOq+ZJdJQIre/O7PT32migDrG9+vZTuFF8CXm3y
Gnv3iIEwsHmR82OFZyNf7zd22ZQ553HTQOX8jc5eOx3ZoxyuAF0L/teS1trso0bE
isJ8ZX9AXJG64vnNV1v+2GQmp8nq/N594dYtnl53VI8IF59Hd7ROovlD/byjeQ07
iR6KLxwpH18wwyfKvZSBziwVg8h7PgDYDsIwYCQAzgecGzVRRI9sGsebZKVE2B9k
VDNkyEJe/QNGGUJo2tfqgdYci/fR0HGQzWlLKk4ZSKigrTsqqV+xHqK19UDPM8mF
A9Af4j3tBlgMX32gDSnzT9xu4R4871AAonR5G1UI2Ib7ofegIwYolybwYLJdBXow
oZyd+02XatXYzD6wBjig9aHs4DDBCYYlNE8fjZKKct0bsioSl99H0kKBEIK72Tm1
k6cD/N8YGVCqC9QiZtjS9zOceeovpI1YapzyUA/6fM6KrjClvp7i/kC//3qtfaAH
UdhZZG2Nfwjx2JvcXJA9m+dELpcUA5a2BYNBVhlr7TdDMbrZ7r7dfyIPvA0Uv+OQ
z0+ctAqukuxDGMLKzn31pWTR5gamgBZpbw8HrdTCAVVmj5fn2/RM7zCQL69Mdcnh
rpEan0iPbDmOzEFR
=nkgk
-END PGP SIGNATURE End Message ---

Processed: Re: Bug#982740: pulseaudio: FTBFS on ppc64el

[Debian Bug Tracking System]

Processing control commands:

> found -1 14.1-1
Bug #982740 [pulseaudio] pulseaudio: FTBFS on ppc64el
Marked as found in versions pulseaudio/14.1-1.

-- 
982740: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982740
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#982740: pulseaudio: FTBFS on ppc64el

[Adrian Bunk]

Control: found -1 14.1-1

On Sat, Feb 13, 2021 at 02:53:58PM -0500, Andres Salomon wrote:
> Package: pulseaudio
> Version: 14.2-1
> Severity: serious
> 
> Pulseaudio is failing to build on ppc64el. The version of pulseaudio in
> bullseye suffers from a pretty serious usability bug (see #980836)
> which should arguably be a higher severity, but let's focus on getting
> 14.2-1 built properly.
> 
> https://buildd.debian.org/status/logs.php?pkg=pulseaudio=ppc64el
> 
> Here's where the ppc64el build fails:
> 
> 
> FAIL: cpu-volume-test
> =
> 
> Running suite(s): CPU
> 0%: Checks: 1, Failures: 1, Errors: 0
> tests/cpu-volume-test.c:81:F:svolume:svolume_orc_test:0: Failed
> FAIL cpu-volume-test (exit status: 1)
> 
> 
> 
> It's worth noting that 14.1-1 built just fine on ppc64el, and the only
> non-debian change between 14.1 and 14.2 is this:
>...

Both versions fail for me the same way on plummer.

Adding debian-powerpc so that a porter can check.

cu
Adrian

Processed: Bug#982802 marked as pending in libio-html-perl

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #982802 [src:libio-html-perl] libio-html-perl: autopkgtest failure
Added tag(s) pending.

-- 
982802: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982802
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#982802: marked as pending in libio-html-perl

[gregor herrmann]

Control: tag -1 pending

Hello,

Bug #982802 in libio-html-perl 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/perl-team/modules/packages/libio-html-perl/-/commit/24f747aaed8aa66a90a143377267e566226ee402


Fix autopkgtests.

Add META.json to test directory.

Thanks: Adrian Bunk for the bug report.
Closes: #982802


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/982802

Bug#981847: marked as done (ArgumentError: invalid byte sequence in US-ASCII)

[Debian Bug Tracking System]

Your message dated Sun, 14 Feb 2021 17:20:51 +
with message-id 
and subject line Bug#981847: fixed in ruby-power-assert 1.1.7-2
has caused the Debian Bug report #981847,
regarding ArgumentError: invalid byte sequence in US-ASCII
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
981847: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981847
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ruby-power-assert
Version: 1.1.7-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source

Dear Maintainer,

During a rebuild of the package on Bullseye, the package fails in one of
the tests. Below is the failure snippet. The same is also seen in the
Reproducible Builds reports.

```
[  194s] 
---
[  194s] 107 tests, 152 assertions, 0 failures, 1 errors, 0 pendings, 0 
omissions, 0 notifications
[  194s] 99.0654% passed
[  194s] 
---
[  194s] 23.20 tests/s, 32.95 assertions/s
[  194s] rake aborted!
[  194s] Command failed with status (1): [ruby -w -I"test"  
"/usr/share/rubygems-integration/all/gems/rake-13.0.1/lib/rake/rake_test_loader.rb"
 "test/block_test.rb" "test/dyna_symbol_key_test.rb" "test/parser_test.rb" 
"test/safe_op_test.rb" "test/trace_test.rb" "test/test_core_ext_helper.rb" 
"test/test_helper.rb" -v]
[  194s] /usr/share/rubygems-integration/all/gems/rake-13.0.1/exe/rake:27:in 
`'
[  194s] Tasks: TOP => default
[  194s] (See full trace by running task with --trace)
[  194s] ERROR: Test "ruby2.7" failed. Exiting.
[  194s] dh_auto_install: error: dh_ruby --install 
/usr/src/packages/BUILD/debian/ruby-power-assert returned exit code 1
[  194s] make: *** [debian/rules:6: binary] Error 25
[  194s] dpkg-buildpackage: error: debian/rules binary subprocess returned exit 
status 2
```


-- System Information:
Debian Release: bullseye/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (990, 'testing'), (500, 'stable-updates'), 
(500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.10.0-3-amd64 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_USER
Locale: LANG=en_IN.UTF-8, LC_CTYPE=en_IN.UTF-8 (charmap=UTF-8), LANGUAGE=en_US
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: ruby-power-assert
Source-Version: 1.1.7-2
Done: Antonio Terceiro 

We believe that the bug you reported is fixed in the latest version of
ruby-power-assert, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 981...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Antonio Terceiro  (supplier of updated ruby-power-assert 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 14 Feb 2021 14:09:37 -0300
Source: ruby-power-assert
Architecture: source
Version: 1.1.7-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Team 

Changed-By: Antonio Terceiro 
Closes: 981847
Changes:
 ruby-power-assert (1.1.7-2) unstable; urgency=medium
 .
   [ Debian Janitor ]
   * Set upstream metadata fields: Repository, Repository-Browse.
 .
   [ Antonio Terceiro ]
   * debian/rules: force UTF-8 locale during the build (Closes: #981847)
Checksums-Sha1:
 1b5eb6112348f99c9d2ff5ce2c0f41181fdc1289 2179 ruby-power-assert_1.1.7-2.dsc
 c2d3538011cba9cb42b786e5f1dd45e3dbc04ba3 3928 
ruby-power-assert_1.1.7-2.debian.tar.xz
 147420c0f8fc07926645deb62184829725f9fde8 9559 
ruby-power-assert_1.1.7-2_amd64.buildinfo
Checksums-Sha256:
 bd7e63381e5f041347be06131fe5e878b2263ef580a97dd36a11dad37c493518 2179 
ruby-power-assert_1.1.7-2.dsc
 484cd3727e937fe02e6273e6af65d7feda503c2fae5590f3970d15057c9e78fe 3928 
ruby-power-assert_1.1.7-2.debian.tar.xz
 9abe7bca2e33da7f0364d4b8077d8382fa0e011a94f87c319a6c6c1e544af9e6 9559 
ruby-power-assert_1.1.7-2_amd64.buildinfo
Files:
 b529d52cb9691ce42a0144c03fc84f61 2179 ruby optional 
ruby-power-assert_1.1.7-2.dsc
 59995192d18dffb39d509915cd4d7b91 3928 ruby optional 

Bug#981847: marked as pending in ruby-power-assert

[Antonio Terceiro]

Control: tag -1 pending

Hello,

Bug #981847 in ruby-power-assert 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/ruby-team/ruby-power-assert/-/commit/10727eebf72adf6a5e9d0e1f9b05b5fe7fccb923


debian/rules: force UTF-8 locale during the build

Closes: #981847


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/981847

Processed: Bug#981847 marked as pending in ruby-power-assert

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #981847 [ruby-power-assert] ArgumentError: invalid byte sequence in US-ASCII
Added tag(s) pending.

-- 
981847: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981847
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#981850: marked as done (Failed: rspec-core, rspec-support)

[Debian Bug Tracking System]

Your message dated Sun, 14 Feb 2021 17:08:26 +
with message-id 
and subject line Bug#981850: fixed in ruby-rspec 3.9.0c2e2m1s3-2
has caused the Debian Bug report #981850,
regarding Failed: rspec-core, rspec-support
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
981850: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981850
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ruby-rspec
Version: 3.9.0c2e2m1s3-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source

Dear Maintainer,

During a rebuild of the package for Bullseye, it is seen that the
package fails to build. The build failure snippet is below. It is also
noticed that the same build failure is seen on the Reproducible Builds.

```
[  294s] Finished in 2.23 seconds (files took 0.50425 seconds to load)
[  294s] 538 examples, 3 failures, 1 pending
[  294s]
[  294s] Failed examples:
[  294s]
[  294s] rspec ./spec/rspec/support/differ_spec.rb:315 # 
RSpec::Support::Differ#diff outputs unified diff message of two hashes with 
differing encoding
[  294s] rspec ./spec/rspec/support/differ_spec.rb:328 # 
RSpec::Support::Differ#diff outputs unified diff message of two hashes with 
encoding different to key encoding
[  294s] rspec ./spec/rspec/support/differ_spec.rb:158 # 
RSpec::Support::Differ#diff uses the default external encoding when the two 
strings have incompatible encodings
[  294s]
[  294s] Randomized with seed 8873
[  294s]
[  295s] cd -
[  295s] Failed: rspec-core, rspec-support
[  295s] ERROR: Test "ruby2.7" failed. Exiting.
[  295s] dh_auto_install: error: dh_ruby --install 
/usr/src/packages/BUILD/debian/tmp returned exit code 1
[  295s] make: *** [debian/rules:99: binary] Error 25
[  295s] dpkg-buildpackage: error: debian/rules binary subprocess returned exit 
status 2
```


-- System Information:
Debian Release: bullseye/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (990, 'testing'), (500, 'stable-updates'), 
(500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.10.0-3-amd64 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_USER
Locale: LANG=en_IN.UTF-8, LC_CTYPE=en_IN.UTF-8 (charmap=UTF-8), LANGUAGE=en_US
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages ruby-rspec depends on:
ii  ruby 1:2.7+2
pn  ruby-rspec-core  
pn  ruby-rspec-expectations  
pn  ruby-rspec-mocks 

ruby-rspec recommends no packages.

ruby-rspec suggests no packages.
--- End Message ---
--- Begin Message ---
Source: ruby-rspec
Source-Version: 3.9.0c2e2m1s3-2
Done: Antonio Terceiro 

We believe that the bug you reported is fixed in the latest version of
ruby-rspec, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 981...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Antonio Terceiro  (supplier of updated ruby-rspec package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 14 Feb 2021 13:52:45 -0300
Source: ruby-rspec
Architecture: source
Version: 3.9.0c2e2m1s3-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Team 

Changed-By: Antonio Terceiro 
Closes: 981850
Changes:
 ruby-rspec (3.9.0c2e2m1s3-2) unstable; urgency=medium
 .
   * debian/rules: force an UTF-8 locale during the build (Closes: #981850)
Checksums-Sha1:
 e8404f23da873ba5db9b05419a1bd0c61bc78485 2484 ruby-rspec_3.9.0c2e2m1s3-2.dsc
 21a9c44d69227d37037f002674f9fd4e6fcdbb79 18560 
ruby-rspec_3.9.0c2e2m1s3-2.debian.tar.xz
 c3e5d610b8d6cb0c6726437c2e396577d5e11506 11387 
ruby-rspec_3.9.0c2e2m1s3-2_amd64.buildinfo
Checksums-Sha256:
 c967367e5654d1af502616ea0b131356831f5c558439722ce643b59754d7c19a 2484 
ruby-rspec_3.9.0c2e2m1s3-2.dsc
 fde6b6e5f73ba97160540fb7dda4daa8e6966d45c059ccbb426164c7ccb7 18560 
ruby-rspec_3.9.0c2e2m1s3-2.debian.tar.xz
 959bd3487d3ec9393ac4eac1130bfd75e36f72254fecdaf1577d09fb1c2acf52 11387 
ruby-rspec_3.9.0c2e2m1s3-2_amd64.buildinfo
Files:
 c2c93f4e5c85e0516d092406dca68204 2484 ruby optional 
ruby-rspec_3.9.0c2e2m1s3-2.dsc
 883dca421978743df5a6a11798740d76 18560 

Bug#966746: marked as done (hash-slinger: Unversioned Python removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Sun, 14 Feb 2021 17:04:28 +
with message-id 
and subject line Bug#927132: fixed in hash-slinger 3.1-1
has caused the Debian Bug report #927132,
regarding hash-slinger: Unversioned Python removal in sid/bullseye
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
927132: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927132
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:hash-slinger
Version: 2.7-1
Severity: serious
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2unversioned

Python2 becomes end-of-live upstream, and Debian aims to remove
Python2 from the distribution, as discussed in
https://lists.debian.org/debian-python/2019/07/msg00080.html

We will keep some Python2 package as discussed in
https://lists.debian.org/debian-python/2020/07/msg00039.html
but removing the unversioned python packages python-minimal, python,
python-dev, python-dbg, python-doc.

Your package either build-depends, depends on one of those packages.
Please either convert these packages to Python3, or if that is not
possible, replaces the dependencies on the unversioned Python
packages with one of the python2 dependencies (python2, python2-dev,
python2-dbg, python2-doc).

Please check for dependencies, build dependencies AND autopkg tests.

If there are questions, please refer to the wiki page for the removal:
https://wiki.debian.org/Python/2Removal, or ask for help on IRC
#debian-python, or the debian-pyt...@lists.debian.org mailing list.
--- End Message ---
--- Begin Message ---
Source: hash-slinger
Source-Version: 3.1-1
Done: Ondřej Surý 

We believe that the bug you reported is fixed in the latest version of
hash-slinger, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 927...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Ondřej Surý  (supplier of updated hash-slinger package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 14 Feb 2021 17:40:02 +0100
Source: hash-slinger
Architecture: source
Version: 3.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian DNS Team 
Changed-By: Ondřej Surý 
Closes: 738490 738494 775048 780498 834971 899533 927132
Changes:
 hash-slinger (3.1-1) unstable; urgency=medium
 .
   * Update d/control (Closes: #899533)
   * Update d/watch, update d/gbp.conf
   * New upstream version 3.1 (Closes: #775048, #780498, #738494)
   * d/control: Port to python3 (Closes: #927132, #834971, #738490
   * Add ${python3:Depends} to Depends
   * Final touches to d/control: policy version, priority optional
Checksums-Sha1:
 8905c66eaad69d21fbeece23fe3bfc3311ee066d 2022 hash-slinger_3.1-1.dsc
 5b0a1d5f2e01cad244dda224efe36481c18fe3a0 38224 hash-slinger_3.1.orig.tar.gz
 21b649a42dc3ff5c9b23f95c3db9ec75956106d7 3532 hash-slinger_3.1-1.debian.tar.xz
 b61516ec5e9602934f301ab65fbc817c17843919 7147 
hash-slinger_3.1-1_amd64.buildinfo
Checksums-Sha256:
 989e41e533c07dcfca255f812f15dd12a4c3f1fc02346b2cdb4a171edc295141 2022 
hash-slinger_3.1-1.dsc
 2f0de62d561e585747732e44ce9ea5fcef93c75c95d66b684bd13b4e70374df6 38224 
hash-slinger_3.1.orig.tar.gz
 60aede8b3b64d73a4d249fe32d7b8eceb247a73ae6acfb95880ab299e94d1e53 3532 
hash-slinger_3.1-1.debian.tar.xz
 fcd0c26f4e341cd13518baa9d9d45a8997aa1c02deed8eb5b1c1718b0f197c09 7147 
hash-slinger_3.1-1_amd64.buildinfo
Files:
 7db6cdbbecbaee4943d0aeeb34831c0e 2022 utils optional hash-slinger_3.1-1.dsc
 45f79c562bad1a83298103d75f20531b 38224 utils optional 
hash-slinger_3.1.orig.tar.gz
 cf72355ac40167c1d6f6e71e35409fc2 3532 utils optional 
hash-slinger_3.1-1.debian.tar.xz
 a5c46c45e8d588c925ad6479943449cf 7147 utils optional 
hash-slinger_3.1-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQKTBAEBCgB9FiEEw2Gx4wKVQ+vGJel9g3Kkd++uWcIFAmApU7hfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEMz
NjFCMUUzMDI5NTQzRUJDNjI1RTk3RDgzNzJBNDc3RUZBRTU5QzIACgkQg3Kkd++u
WcJ0aQ//eGm0nmZKkg83ir1DdWmnOqlyverSvzDnkHl+/wF+8I4dP/Bu1CjagtpM
GRDvycXEWgw0hxaKM/Sm2xgbRJAbDk7risLPWXVbDpv5nr4pbtyzfAwx41TW/Trj
ri0uwRtXElHq1CCfNePhotZ8C/TrvzsFOvPUuKWiaoHBH4A1tQcqypcoMUv7v45V

Bug#982801: marked as done (libattean-perl needs Breaks: libatteanx-serializer-rdfa-perl (<< 0.100-2~))

[Debian Bug Tracking System]

Your message dated Sun, 14 Feb 2021 17:04:55 +
with message-id 
and subject line Bug#982801: fixed in libattean-perl 0.030-2
has caused the Debian Bug report #982801,
regarding libattean-perl needs Breaks: libatteanx-serializer-rdfa-perl (<< 
0.100-2~)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
982801: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982801
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libattean-perl
Version: 0.030-1
Severity: serious

https://tracker.debian.org/pkg/libattean-perl

Migration status for libattean-perl (0.028-1 to 0.030-1): BLOCKED: 
Rejected/violates migration policy/introduces a regression
Issues preventing migration:
autopkgtest for libatteanx-serializer-rdfa-perl/0.100-1.1: amd64: Regression ♻ 
(reference ♻), arm64: Regression ♻ (reference ♻), armhf: Regression ♻ 
(reference ♻), i386: Regression ♻ (reference ♻), ppc64el: Regression ♻ 
(reference ♻)


See #982722 for background.
--- End Message ---
--- Begin Message ---
Source: libattean-perl
Source-Version: 0.030-2
Done: Jonas Smedegaard 

We believe that the bug you reported is fixed in the latest version of
libattean-perl, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 982...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Jonas Smedegaard  (supplier of updated libattean-perl package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 14 Feb 2021 17:39:40 +0100
Source: libattean-perl
Architecture: source
Version: 0.030-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Perl Group 
Changed-By: Jonas Smedegaard 
Closes: 982801
Changes:
 libattean-perl (0.030-2) unstable; urgency=medium
 .
   * fix break older libatteanx-serializer-rdfa-perl;
 closes: bug#982801, thanks to Adrian Bunk
Checksums-Sha1:
 803f331eee2a04f141a57de13416bd6d020e0d74 3231 libattean-perl_0.030-2.dsc
 b73b646c8afe211310e49844a938177c6389b3b7 11356 
libattean-perl_0.030-2.debian.tar.xz
 e84faa87bbcb4dd61ee2ffc1edc782379d7aa541 11203 
libattean-perl_0.030-2_amd64.buildinfo
Checksums-Sha256:
 c809e0b1dfa558560fec01fc7f06764ab84956cb04519583b1c858d59c064981 3231 
libattean-perl_0.030-2.dsc
 731dc0c7dc327f02ee2031229869f7bae733e9bc456f5360c1e3cd85d0ffa167 11356 
libattean-perl_0.030-2.debian.tar.xz
 04207ca3e66c51f3343952f6eda565db9b5528a87dba6c7e27b92f53f1a7623d 11203 
libattean-perl_0.030-2_amd64.buildinfo
Files:
 cac4be08a9e5fd2085194a415bffa114 3231 perl optional libattean-perl_0.030-2.dsc
 40d25816a43dfb8b3916beae33e8ec5a 11356 perl optional 
libattean-perl_0.030-2.debian.tar.xz
 c878e4960d8b498cc057fb2baa0e937b 11203 perl optional 
libattean-perl_0.030-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmApVB4ACgkQLHwxRsGg
ASHQVw/+P4D3sG011EF7WKiCeUD7zZ9W0dWqR1S1D9buZo3Z6WavklkcQN8L5Jhe
IDzGLyV/4zXoPXIIsHSovhD4Tcew28Snc4Wx244sjn7bQ1KLsU3oZnC72ZCbM0zN
+kKHTnzkQ/alhKHas6xBNp0uoqz7jwQqVHyghXhfkg8gKtvA0UEIy+BZB8Lb8xTh
HRGzrAscf2uM501sEpQrmbz5vb7yLdXZ0UE7KkFGCNgcXYDCg1pAmj4xgteeW11Y
TIFbLadLt5K4DstwPaWjCeGLmwVSzQ234S3rngg0A4qT8FSzAkBDp5JaTU+ieCJu
XEVnWTMKjKmYuVuo2SzvTriSwNu5CCGXr/XPHe2eqY0aq7CEm7fpXwUbh76m34RD
+8x8qKw99uC/9iZFrMgqWvhD06UtiuWKUGqeiKwGClU469qJ6HznOtnOvR2juqiQ
4xcEPySipSZqlb2oQAkP5vEr0JqM48t/2irR9+IXza2yxiPUVDoqV5fHNtuPz/lW
tKxxG8B9fZ4ieq3gprm/BKzJeluLqsrTMtIj6ynNKQT1QIeZqMn1piz5fn/9nPNM
9AvMiPaOHHHxC7e1Lf2/GFQ3sNshpGxYi+kPPWw53clUnXv9FQvWZgW7tB+1EdFo
uCKvR9TplieKbP7sX41xO6tqAfeq4JoOa+IRLVfO/Z6yv0trlvI=
=Lmdz
-END PGP SIGNATURE End Message ---

Bug#953372: marked as done (src:hash-slinger: Depends on cruft package python-dnspython)

[Debian Bug Tracking System]

Your message dated Sun, 14 Feb 2021 17:04:28 +
with message-id 
and subject line Bug#927132: fixed in hash-slinger 3.1-1
has caused the Debian Bug report #927132,
regarding src:hash-slinger: Depends on cruft package python-dnspython
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
927132: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927132
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:hash-slinger
Version: 2.7-1
Severity: serious
Justification: Policy 2.2.1

This package Depends on python-dnspython which is an NBS cruft package.  Please
update your package to use python3-dnspython, which is still provided (if the
package will be ported to python3).

Scott K
--- End Message ---
--- Begin Message ---
Source: hash-slinger
Source-Version: 3.1-1
Done: Ondřej Surý 

We believe that the bug you reported is fixed in the latest version of
hash-slinger, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 927...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Ondřej Surý  (supplier of updated hash-slinger package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 14 Feb 2021 17:40:02 +0100
Source: hash-slinger
Architecture: source
Version: 3.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian DNS Team 
Changed-By: Ondřej Surý 
Closes: 738490 738494 775048 780498 834971 899533 927132
Changes:
 hash-slinger (3.1-1) unstable; urgency=medium
 .
   * Update d/control (Closes: #899533)
   * Update d/watch, update d/gbp.conf
   * New upstream version 3.1 (Closes: #775048, #780498, #738494)
   * d/control: Port to python3 (Closes: #927132, #834971, #738490
   * Add ${python3:Depends} to Depends
   * Final touches to d/control: policy version, priority optional
Checksums-Sha1:
 8905c66eaad69d21fbeece23fe3bfc3311ee066d 2022 hash-slinger_3.1-1.dsc
 5b0a1d5f2e01cad244dda224efe36481c18fe3a0 38224 hash-slinger_3.1.orig.tar.gz
 21b649a42dc3ff5c9b23f95c3db9ec75956106d7 3532 hash-slinger_3.1-1.debian.tar.xz
 b61516ec5e9602934f301ab65fbc817c17843919 7147 
hash-slinger_3.1-1_amd64.buildinfo
Checksums-Sha256:
 989e41e533c07dcfca255f812f15dd12a4c3f1fc02346b2cdb4a171edc295141 2022 
hash-slinger_3.1-1.dsc
 2f0de62d561e585747732e44ce9ea5fcef93c75c95d66b684bd13b4e70374df6 38224 
hash-slinger_3.1.orig.tar.gz
 60aede8b3b64d73a4d249fe32d7b8eceb247a73ae6acfb95880ab299e94d1e53 3532 
hash-slinger_3.1-1.debian.tar.xz
 fcd0c26f4e341cd13518baa9d9d45a8997aa1c02deed8eb5b1c1718b0f197c09 7147 
hash-slinger_3.1-1_amd64.buildinfo
Files:
 7db6cdbbecbaee4943d0aeeb34831c0e 2022 utils optional hash-slinger_3.1-1.dsc
 45f79c562bad1a83298103d75f20531b 38224 utils optional 
hash-slinger_3.1.orig.tar.gz
 cf72355ac40167c1d6f6e71e35409fc2 3532 utils optional 
hash-slinger_3.1-1.debian.tar.xz
 a5c46c45e8d588c925ad6479943449cf 7147 utils optional 
hash-slinger_3.1-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQKTBAEBCgB9FiEEw2Gx4wKVQ+vGJel9g3Kkd++uWcIFAmApU7hfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEMz
NjFCMUUzMDI5NTQzRUJDNjI1RTk3RDgzNzJBNDc3RUZBRTU5QzIACgkQg3Kkd++u
WcJ0aQ//eGm0nmZKkg83ir1DdWmnOqlyverSvzDnkHl+/wF+8I4dP/Bu1CjagtpM
GRDvycXEWgw0hxaKM/Sm2xgbRJAbDk7risLPWXVbDpv5nr4pbtyzfAwx41TW/Trj
ri0uwRtXElHq1CCfNePhotZ8C/TrvzsFOvPUuKWiaoHBH4A1tQcqypcoMUv7v45V
qGMCmJK7k5VsYE4F73ttkitYDTIbT4qh8Iw23PMlMpIfU4p2Wq9zdOXn8EIEo7h/
ExYQND4axf9Y6vNl6xcxvsx3eHSSBYxBkmAo3UNJm3oKE40Zo8yQ5QsocPQBj81I
ChQiDCu2XLFtuCW/kcjZC2W6urbkAPLVg48eYTynB/seaj7Yl7sp50ujsm/mLAX9
hgAC9xio7Ev7D5XAgeGPKgJ7H+MttXEgAa9RZTw4JlcyUGG2Q38ft8wfC4ey3QfR
vd1/mx+NTckTUiHrC3QwCRnm+vb56fNmh49JBip5lM7U8s6v0nzFGuDNxyqMKqyV
YwVZurtr1gBRTIwWb8C8WAgmjp7OX4JyzIawGgPJqh4l6pI0NziK2qNmfBzggVj/
i1SMaLzBtcZMMIJKDGsi/sbcZ7DmeqOBDImBG3NNyJU+EcHst3GugJ7zVrHL+Ery
bHSGBF4rC9xW4hoEZ8omTbpNGS1ZfaJEN0yt4SsFRJ8Vrdoa5D8=
=X4Nt
-END PGP SIGNATURE End Message ---

Bug#945653: marked as done (hash-slinger: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Sun, 14 Feb 2021 17:04:28 +
with message-id 
and subject line Bug#927132: fixed in hash-slinger 3.1-1
has caused the Debian Bug report #927132,
regarding hash-slinger: Python2 removal in sid/bullseye
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
927132: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927132
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: hash-slinger
Version: 2.7-1
Severity: normal
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2removal

Python2 becomes end-of-live upstream, and Debian aims to remove
Python2 from the distribution, as discussed in
https://lists.debian.org/debian-python/2019/07/msg00080.html

Your package either build-depends, depends on Python2, or uses Python2
in the autopkg tests (the specific reason can be found searching this
source package in
https://people.debian.org/~morph/mass-bug-py2removal_take3.txt ).
Please stop using Python2, and fix this issue by one of the following
actions.

- Convert your Package to Python3. This is the preferred option.  In
  case you are providing a Python module foo, please consider dropping
  the python-foo package, and only build a python3-foo package.  Please
  don't drop Python2 modules, which still have reverse dependencies,
  just document them.
  
  This is the preferred option.

- If the package is dead upstream, cannot be converted or maintained
  in Debian, it should be removed from the distribution.  If the
  package still has reverse dependencies, raise the severity to
  "serious" and document the reverse dependencies with the BTS affects
  command.  If the package has no reverse dependencies, confirm that
  the package can be removed, reassign this issue to ftp.debian.org,
  make sure that the bug priority is set to normal and retitle the
  issue to "RM: PKG -- removal triggered by the Python2 removal".

- If the package has still many users (popcon >= 300), or is needed to
  build another package which cannot be removed, document that by
  adding the "py2keep" user tag (not replacing the py2remove tag),
  using the debian-pyt...@lists.debian.org user.  Also any
  dependencies on an unversioned python package (python, python-dev)
  must not be used, same with the python shebang.  These have to be
  replaced by python2/python2.7 dependencies and shebang.

  This is the least preferred option.

If there are questions, please refer to the wiki page for the removal:
https://wiki.debian.org/Python/2Removal, or ask for help on IRC
#debian-python, or the debian-pyt...@lists.debian.org mailing list.
--- End Message ---
--- Begin Message ---
Source: hash-slinger
Source-Version: 3.1-1
Done: Ondřej Surý 

We believe that the bug you reported is fixed in the latest version of
hash-slinger, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 927...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Ondřej Surý  (supplier of updated hash-slinger package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 14 Feb 2021 17:40:02 +0100
Source: hash-slinger
Architecture: source
Version: 3.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian DNS Team 
Changed-By: Ondřej Surý 
Closes: 738490 738494 775048 780498 834971 899533 927132
Changes:
 hash-slinger (3.1-1) unstable; urgency=medium
 .
   * Update d/control (Closes: #899533)
   * Update d/watch, update d/gbp.conf
   * New upstream version 3.1 (Closes: #775048, #780498, #738494)
   * d/control: Port to python3 (Closes: #927132, #834971, #738490
   * Add ${python3:Depends} to Depends
   * Final touches to d/control: policy version, priority optional
Checksums-Sha1:
 8905c66eaad69d21fbeece23fe3bfc3311ee066d 2022 hash-slinger_3.1-1.dsc
 5b0a1d5f2e01cad244dda224efe36481c18fe3a0 38224 hash-slinger_3.1.orig.tar.gz
 21b649a42dc3ff5c9b23f95c3db9ec75956106d7 3532 hash-slinger_3.1-1.debian.tar.xz
 b61516ec5e9602934f301ab65fbc817c17843919 7147 
hash-slinger_3.1-1_amd64.buildinfo
Checksums-Sha256:
 989e41e533c07dcfca255f812f15dd12a4c3f1fc02346b2cdb4a171edc295141 2022 
hash-slinger_3.1-1.dsc
 

Bug#927132: marked as done (src:hash-slinger: Please port to python3)

[Debian Bug Tracking System]

Your message dated Sun, 14 Feb 2021 17:04:28 +
with message-id 
and subject line Bug#927132: fixed in hash-slinger 3.1-1
has caused the Debian Bug report #927132,
regarding src:hash-slinger: Please port to python3
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
927132: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927132
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:hash-slinger
Version: 2.7-1
Severity: important

Python2.7 will go out of upstream security support during the Bullseye
development cycle.  It is not safe to assume it will be included in the
next release, so if you want to be sure hash-slinger can stay in Debian,
please port it to python3.  I see upstream suddendly did a new release
after three years, so maybe an upstream port will appear.

Personally, I want to remove some packages I maintain, particularly python-
ipaddr, which hash-slinger depends on during the Bullseye cycle, regardless of
what happens to python2.7, so please update (python3 includes the ipaddress
module, which was developed from ipaddr, in the standard library).
--- End Message ---
--- Begin Message ---
Source: hash-slinger
Source-Version: 3.1-1
Done: Ondřej Surý 

We believe that the bug you reported is fixed in the latest version of
hash-slinger, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 927...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Ondřej Surý  (supplier of updated hash-slinger package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 14 Feb 2021 17:40:02 +0100
Source: hash-slinger
Architecture: source
Version: 3.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian DNS Team 
Changed-By: Ondřej Surý 
Closes: 738490 738494 775048 780498 834971 899533 927132
Changes:
 hash-slinger (3.1-1) unstable; urgency=medium
 .
   * Update d/control (Closes: #899533)
   * Update d/watch, update d/gbp.conf
   * New upstream version 3.1 (Closes: #775048, #780498, #738494)
   * d/control: Port to python3 (Closes: #927132, #834971, #738490
   * Add ${python3:Depends} to Depends
   * Final touches to d/control: policy version, priority optional
Checksums-Sha1:
 8905c66eaad69d21fbeece23fe3bfc3311ee066d 2022 hash-slinger_3.1-1.dsc
 5b0a1d5f2e01cad244dda224efe36481c18fe3a0 38224 hash-slinger_3.1.orig.tar.gz
 21b649a42dc3ff5c9b23f95c3db9ec75956106d7 3532 hash-slinger_3.1-1.debian.tar.xz
 b61516ec5e9602934f301ab65fbc817c17843919 7147 
hash-slinger_3.1-1_amd64.buildinfo
Checksums-Sha256:
 989e41e533c07dcfca255f812f15dd12a4c3f1fc02346b2cdb4a171edc295141 2022 
hash-slinger_3.1-1.dsc
 2f0de62d561e585747732e44ce9ea5fcef93c75c95d66b684bd13b4e70374df6 38224 
hash-slinger_3.1.orig.tar.gz
 60aede8b3b64d73a4d249fe32d7b8eceb247a73ae6acfb95880ab299e94d1e53 3532 
hash-slinger_3.1-1.debian.tar.xz
 fcd0c26f4e341cd13518baa9d9d45a8997aa1c02deed8eb5b1c1718b0f197c09 7147 
hash-slinger_3.1-1_amd64.buildinfo
Files:
 7db6cdbbecbaee4943d0aeeb34831c0e 2022 utils optional hash-slinger_3.1-1.dsc
 45f79c562bad1a83298103d75f20531b 38224 utils optional 
hash-slinger_3.1.orig.tar.gz
 cf72355ac40167c1d6f6e71e35409fc2 3532 utils optional 
hash-slinger_3.1-1.debian.tar.xz
 a5c46c45e8d588c925ad6479943449cf 7147 utils optional 
hash-slinger_3.1-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQKTBAEBCgB9FiEEw2Gx4wKVQ+vGJel9g3Kkd++uWcIFAmApU7hfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEMz
NjFCMUUzMDI5NTQzRUJDNjI1RTk3RDgzNzJBNDc3RUZBRTU5QzIACgkQg3Kkd++u
WcJ0aQ//eGm0nmZKkg83ir1DdWmnOqlyverSvzDnkHl+/wF+8I4dP/Bu1CjagtpM
GRDvycXEWgw0hxaKM/Sm2xgbRJAbDk7risLPWXVbDpv5nr4pbtyzfAwx41TW/Trj
ri0uwRtXElHq1CCfNePhotZ8C/TrvzsFOvPUuKWiaoHBH4A1tQcqypcoMUv7v45V
qGMCmJK7k5VsYE4F73ttkitYDTIbT4qh8Iw23PMlMpIfU4p2Wq9zdOXn8EIEo7h/
ExYQND4axf9Y6vNl6xcxvsx3eHSSBYxBkmAo3UNJm3oKE40Zo8yQ5QsocPQBj81I
ChQiDCu2XLFtuCW/kcjZC2W6urbkAPLVg48eYTynB/seaj7Yl7sp50ujsm/mLAX9
hgAC9xio7Ev7D5XAgeGPKgJ7H+MttXEgAa9RZTw4JlcyUGG2Q38ft8wfC4ey3QfR
vd1/mx+NTckTUiHrC3QwCRnm+vb56fNmh49JBip5lM7U8s6v0nzFGuDNxyqMKqyV
YwVZurtr1gBRTIwWb8C8WAgmjp7OX4JyzIawGgPJqh4l6pI0NziK2qNmfBzggVj/
i1SMaLzBtcZMMIJKDGsi/sbcZ7DmeqOBDImBG3NNyJU+EcHst3GugJ7zVrHL+Ery

Bug#972936: libgcc-s1 buster -> bullseye upgrade issues

[Simon McVittie]

On Sat, 13 Feb 2021 at 19:52:10 +0100, Paul Gevers wrote:
> [The release team are] pretty concerned about a couple of known RC bugs
> which need the proper attention of people familiar with upgrade paths
> as there's potential to leave upgrading systems unbootable and/or
> without a working apt.
...
> https://bugs.debian.org/972936 / libgcc-s1

I wanted to provide some signal boost for this and related upgrade issues.
Ryan Pavlik, one of my colleagues at Collabora, ran into a similar upgrade
failure involving libgcc-s1 and has made a self-contained reproducer
for it: . This uses
Docker, but apt should behave the same in a chroot or VM.

He reports that at least the issue he originally experienced, and perhaps
others, can be fixed by adding transitional binary packages like these:
https://salsa.debian.org/rpavlik/gcc-10-compat

His gcc-10-compat package's README also has a fairly comprehensive list
of other upgrade bugs around libgcc_s.so.1 that might well have the same
root cause. #972936 is currently the only one marked as RC, but some of
the others should maybe be considered RC too.

Obviously, the transitional packages would ideally be built by src:gcc-10
rather than being a separate source package, and Ryan only prototyped them
as a separate source package to be able to iterate on them without having
to rebuild all of gcc.

smcv

Processed: Bug#981850 marked as pending in ruby-rspec

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #981850 [ruby-rspec] Failed: rspec-core, rspec-support
Added tag(s) pending.

-- 
981850: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981850
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#981850: marked as pending in ruby-rspec

[Antonio Terceiro]

Control: tag -1 pending

Hello,

Bug #981850 in ruby-rspec 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/ruby-team/ruby-rspec/-/commit/9357516bef15176bcb63fc8bd14ca35b6a049b59


debian/rules: force an UTF-8 locale during the build

Closes: #981850


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/981850

Processed: Re: Bug#982692: gemma: FTBFS: dh_auto_test: error: make -j1 check returned exit code 2

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #982692 [src:gemma] gemma: FTBFS: dh_auto_test: error: make -j1 check 
returned exit code 2
Severity set to 'important' from 'serious'
> tags -1 moreinfo
Bug #982692 [src:gemma] gemma: FTBFS: dh_auto_test: error: make -j1 check 
returned exit code 2
Added tag(s) moreinfo.
> tags -1 unreproducible
Bug #982692 [src:gemma] gemma: FTBFS: dh_auto_test: error: make -j1 check 
returned exit code 2
Added tag(s) unreproducible.

-- 
982692: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982692
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#982692: gemma: FTBFS: dh_auto_test: error: make -j1 check returned exit code 2

[Andreas Tille]

Control: severity -1 important
Control: tags -1 moreinfo
Control: tags -1 unreproducible


On Sat, Feb 13, 2021 at 06:12:12PM +0100, Lucas Nussbaum wrote:
> Source: gemma
> Version: 0.98.4+dfsg-1
> Severity: serious
> Justification: FTBFS on amd64
> Tags: bullseye sid ftbfs
> Usertags: ftbfs-20210213 ftbfs-bullseye
> 
> > ...
> > Ran 13 tests.
> > 
> > FAILED (failures=4)

Neither Nilesh nor I can reproduce this.  Any more info?

Kind regards

Andreas.

-- 
http://fam-tille.de

Bug#982801: marked as pending in libattean-perl

[Jonas Smedegaard]

Control: tag -1 pending

Hello,

Bug #982801 in libattean-perl 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/perl-team/modules/packages/libattean-perl/-/commit/54ca470ee1f78d8ffac7a338622677d6dd2d5f2e


fix break older libatteanx-serializer-rdfa-perl; closes: bug#982801, thanks to 
Adrian Bunk


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/982801

Processed: Bug#982801 marked as pending in libattean-perl

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #982801 [libattean-perl] libattean-perl needs Breaks: 
libatteanx-serializer-rdfa-perl (<< 0.100-2~)
Added tag(s) pending.

-- 
982801: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982801
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: severity of 981975 is serious

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 981975 serious
Bug #981975 [icingaweb2-module-director] icingaweb2-module-director is 
uninstallable: dependency on nonexistent package
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
981975: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981975
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#957343: marked as done (httest: ftbfs with GCC-10)

[Debian Bug Tracking System]

Your message dated Sun, 14 Feb 2021 16:34:31 +
with message-id 
and subject line Bug#957343: fixed in httest 2.4.23-1.1
has caused the Debian Bug report #957343,
regarding httest: ftbfs with GCC-10
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
957343: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957343
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:httest
Version: 2.4.23-1
Severity: normal
Tags: sid bullseye
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-10

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-10/g++-10, but succeeds to build with gcc-9/g++-9. The
severity of this report will be raised before the bullseye release,
so nothing has to be done for the buster release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc10-20200225/httest_2.4.23-1_unstable_gcc10.log
The last lines of the build log are at the end of this report.

To build with GCC 10, either set CC=gcc-10 CXX=g++-10 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-10/porting_to.html

[...]
 from /usr/include/openssl/ssl.h:15,
 from ssl_module.c:28:
/usr/include/openssl/ssl.h:1890:1: note: declared here
 1890 | DEPRECATEDIN_1_1_0(__owur const SSL_METHOD *TLSv1_2_server_method(void))
  | ^~
ssl_module.c:820:5: warning: ‘DTLSv1_server_method’ is deprecated 
[-Wdeprecated-declarations]
  820 | config->meth = (SSL_METHOD *)DTLSv1_server_method();
  | ^~
In file included from /usr/include/openssl/e_os2.h:13,
 from /usr/include/openssl/ssl.h:15,
 from ssl_module.c:28:
/usr/include/openssl/ssl.h:1896:1: note: declared here
 1896 | DEPRECATEDIN_1_1_0(__owur const SSL_METHOD *DTLSv1_server_method(void))
  | ^~
gcc -DHAVE_CONFIG_H -I. -I../config   -DLINUX -D_REENTRANT -D_GNU_SOURCE 
-Wdate-time -D_FORTIFY_SOURCE=2 -I../include -pthread  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security  -I/usr/include/apr-1.0   -I/usr/include/apr-1.0 
-I/usr/include   -c -o coder_module.o coder_module.c
gcc -DHAVE_CONFIG_H -I. -I../config   -DLINUX -D_REENTRANT -D_GNU_SOURCE 
-Wdate-time -D_FORTIFY_SOURCE=2 -I../include -pthread  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security  -I/usr/include/apr-1.0   -I/usr/include/apr-1.0 
-I/usr/include   -c -o math_module.o math_module.c
gcc -DHAVE_CONFIG_H -I. -I../config   -DLINUX -D_REENTRANT -D_GNU_SOURCE 
-Wdate-time -D_FORTIFY_SOURCE=2 -I../include -pthread  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security  -I/usr/include/apr-1.0   -I/usr/include/apr-1.0 
-I/usr/include   -c -o sys_module.o sys_module.c
gcc -DHAVE_CONFIG_H -I. -I../config   -DLINUX -D_REENTRANT -D_GNU_SOURCE 
-Wdate-time -D_FORTIFY_SOURCE=2 -I../include -pthread  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security  -I/usr/include/apr-1.0   -I/usr/include/apr-1.0 
-I/usr/include   -c -o binary_module.o binary_module.c
gcc -DHAVE_CONFIG_H -I. -I../config   -DLINUX -D_REENTRANT -D_GNU_SOURCE 
-Wdate-time -D_FORTIFY_SOURCE=2 -I../include -pthread  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security  -I/usr/include/apr-1.0   -I/usr/include/apr-1.0 
-I/usr/include   -c -o udp_module.o udp_module.c
gcc -DHAVE_CONFIG_H -I. -I../config   -DLINUX -D_REENTRANT -D_GNU_SOURCE 
-Wdate-time -D_FORTIFY_SOURCE=2 -I../include -pthread  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security  -I/usr/include/apr-1.0   -I/usr/include/apr-1.0 
-I/usr/include   -c -o socks_module.o socks_module.c
gcc -DHAVE_CONFIG_H -I. -I../config   -DLINUX -D_REENTRANT -D_GNU_SOURCE 
-Wdate-time -D_FORTIFY_SOURCE=2 -I../include -pthread  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security