Bug#1019393: hdf5 breaks libsis-jhdf5-java autopkgtest: Could not initialize class

[Steven Robbins]

On Thu, 8 Sep 2022 16:11:33 +0200 Paul Gevers  wrote:

> With a recent upload of hdf5 the autopkgtest of libsis-jhdf5-java fails 
> in testing when that autopkgtest is run with the binary packages of hdf5 
> from unstable. It passes when run with only packages from testing.

I find the same holds for simple BUILDING of the libsis-jhdf5-java source 
package.  The build succeeds when using libhdf5-dev from testing, but fails 
with the  package from  unstable. 

The failure happens when running tests.  Below is output from first test 
failure.

-Steve

FAILED: testCreateVerifyContentArtificialRootRoundtripOK
java.lang.ExceptionInInitializerError
at hdf.hdf5lib.HDF5Constants.(HDF5Constants.java:29)
at 
ch.systemsx.cisd.hdf5.IHDF5WriterConfigurator$FileFormatVersion.(IHDF5WriterConfigurator.java:
74)
at 
ch.systemsx.cisd.hdf5.IHDF5WriterConfigurator$FileFormatVersionBounds.(IHDF5WriterConfigurator.java:
127)
at 
ch.systemsx.cisd.hdf5.h5ar.HDF5Archiver.(HDF5Archiver.java:112)
at 
ch.systemsx.cisd.hdf5.h5ar.HDF5ArchiverFactory.open(HDF5ArchiverFactory.java:
41)
at 
ch.systemsx.cisd.hdf5.h5ar.HDF5ArchiverTest.testCreateVerifyContentArtificialRootRoundtripOK(HDF5ArchiverTest.java:
330)
at java.base/
jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:
104)
at java.base/java.lang.reflect.Method.invoke(Method.java:577)
at 
org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:
100)
at org.testng.internal.Invoker.invokeMethod(Invoker.java:646)
at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:811)
at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1129)
at 
org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:
129)
at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:
112)
at org.testng.TestRunner.privateRun(TestRunner.java:746)
at org.testng.TestRunner.run(TestRunner.java:600)
at org.testng.SuiteRunner.runTest(SuiteRunner.java:366)
at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:361)
at org.testng.SuiteRunner.privateRun(SuiteRunner.java:319)
at org.testng.SuiteRunner.run(SuiteRunner.java:268)
at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52)
at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86)
at org.testng.TestNG.runSuitesSequentially(TestNG.java:1264)
at org.testng.TestNG.runSuitesLocally(TestNG.java:1189)
at org.testng.TestNG.runSuites(TestNG.java:1104)
at org.testng.TestNG.run(TestNG.java:1076)
at org.testng.TestNG.privateMain(TestNG.java:1405)
at org.testng.TestNG.main(TestNG.java:1374)
Caused by: java.lang.UnsupportedOperationException: No suitable HDF5 native 
library found for this platform.
at hdf.hdf5lib.H5.loadH5Lib(H5.java:240)
at hdf.hdf5lib.H5.(H5.java:230)
... 28 more

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

Bug#1019865: Hangs and goes to 100% CPU usage on compose

[Nikolai Lusan]

Package: evolution
Version: 3.45.3-2
Severity: grave

After a recent update everytime I open Evolution it successfully checks all my 
IMAP folders,
and CalDAV/CardDAV accounts. However if I try to compose a new message, or 
reply to any message
the evolution proccess amps up to 100% CPU usage and hangs. Even leaving it for 
an extended
period does not allow the problem to resolve itself. 

My suspicion is that it happened in the 3.45.3-1 -> 3.45.3-2 upgrade, so a 
regression _might_
solve the issue. This has not been tested though.


-- System Information:
Debian Release: bookworm/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
merged-usr: no
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.19.0-1-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_FIRMWARE_WORKAROUND, 
TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages evolution depends on:
ii  dbus [default-dbus-system-bus]  1.14.0-2
ii  dbus-broker [dbus-system-bus]   32-1
ii  evolution-common3.45.3-2
ii  evolution-data-server   3.45.3-1.2
ii  libc6   2.34-8
ii  libcamel-1.2-64 3.45.3-1.2
ii  libecal-2.0-2   3.45.3-1.2
ii  libedataserver-1.2-27   3.45.3-1.2
ii  libevolution3.45.3-2
ii  libglib2.0-02.73.3-3
ii  libgtk-3-0  3.24.34-3
ii  libical33.0.14-1+b1
ii  libnotify4  0.8.1-1
ii  libxml2 2.9.14+dfsg-1+b1
ii  psmisc  23.5-3

Versions of packages evolution recommends:
ii  evolution-plugin-pstimport 3.45.3-2
ii  evolution-plugin-spamassassin  3.45.3-2
ii  evolution-plugins  3.45.3-2
ii  yelp   42.1-2

Versions of packages evolution suggests:
pn  evolution-ews   
ii  evolution-plugins-experimental  3.45.3-2
ii  gnupg   2.2.39-1
ii  network-manager 1.40.0-1

-- no debconf information

Bug#1014120: libowfat FTBFS: ln: failed to create hard link 'libowfat/buffer.h'

[Bo YU]

Hi,
On Wed, Sep 14, 2022 at 10:50:36PM +0200, Bastian Germann wrote:

I have tried to fix this but as I am not able to reproduce this locally I am at 
a loss here.
Maybe someone else has an idea...


Some days ago I want to fix the issue but can not to reprodule also.
It was the new issue:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017157




--
Regards,
--
  Bo YU



signature.asc
Description: PGP signature

Bug#1001022: block 998499 with 1001022, block 998499 with 997310

[dane neely]

Date: Thu, 02 Dec 2021 20:46:34 +0100
>From: Daniel Leidert 
>-
>Body: ur-type{header=Received: (at submit) by bugs.debian.org; 2 Dec 2021 
>19:34:46 +
>From dleid...@debian.org Thu Dec 02 19:34:46 2021
>X-Spam-Checker-Version: SpamAssassin 3.4.2-bugs.debian.org_2005_01_02
> (2018-09-13) on buxtehude.debian.org
>X-Spam-Level:
>X-Spam-Status: No, score=-24.5 required=4.0 tests=BAYES_00,DIGITS_LETTERS,
> FOURLA,FROMDEVELOPER,FVGT_m_MULTI_ODD,HAS_PACKAGE,MURPHY_DRUGS_REL8,
> PGPSIGNATURE,SPF_HELO_NONE,SPF_NONE,TXREP,XMAILER_REPORTBUG
> autolearn=ham autolearn_force=no
> version=3.4.2-bugs.debian.org_2005_01_02
>X-Spam-Bayes: score:0. Tokens: new, 87; hammy, 150; neutral, 125; spammy,
> 0. spammytokens: hammytokens:0.000-+--sk:iQIzBAE, 0.000-+--sk:iqizbae,
> 0.000-+--sha512, 0.000-+--SHA512, 0.000-+--H*r:key-exchange
>Return-path: 
>Received: from mail.wgdd.de ([5.39.82.225]:36116)
> by buxtehude.debian.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256)
> (Exim 4.92)
> (envelope-from )
> id 1msrqv-00075s-Rr
> for sub...@bugs.debian.org; Thu, 02 Dec 2021 19:34:46 +
>Received: from [127.0.1.1] (ip5f5aad27.dynamic.kabel-deutschland.de 
>[95.90.173.39])
> (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
> key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits) server-digest 
> SHA256)
> (No client certificate requested)
> (Authenticated sender: dleidert)
> by mail.wgdd.de (Postfix) with ESMTPSA id E133A817F0
> for ; Thu, 2 Dec 2021 19:34:41 + (UTC)
>Content-Type: text/plain; charset="us-ascii"
>MIME-Version: 1.0
>Content-Transfer-Encoding: 7bit
>From: Daniel Leidert 
>To: Debian Bug Tracking System 
>Subject: ruby-pathutil: Not Ruby 3.0 compatible due to kwargs issues
>Message-ID: <163847368027.50071.9447108658119765375.reportbug@vogon>
>X-Mailer: reportbug 11.1.0
>Date: Thu, 02 Dec 2021 20:34:40 +0100
>Delivered-To: sub...@bugs.debian.org

[dane neely - Chat @ 
Spike](https://spikenow.com/r/a/?ref=spike-organic-signature&_ts=1q7khj)   
[1q7khj]

Bug#1019855: Fwd: libc6: immediately crashes with SIGILL on 4th gen Intel Core CPUs (seems related to AVX2 instructions), bricking the whole system

[debian-bug-report]

Package: libc6
Version: 2.31-13+deb11u4
Severity: critical

Dear Maintainer,

After an upgrade to version +deb11u4 on my system running Haswell
(4th gen Intel Core) CPU, most of the programs including bash or dpkg
are immediately crashing with SIGILL. The problem seems to be caused/
related to AVX2 and changes made to some functions utilizing this 
instruction set. I don't know much about Debian bug reporting, so 
forgive me any mistakes I've made.

The issue is on both host, LXC and Docker.
I have described more on this link:
https://github.com/debuerreotype/docker-debian-artifacts/issues/175
where I also linked my coredump from example program and described stuff 
more thoroughly.


Coredump link directly just in case: 
https://github.com/debuerreotype/docker-debian-artifacts/files/9569748/core.bash.10.2663c40e671041e6b40c882a70b83c3f.1480736.166318582400.zip


Also log lines from kernel:
kernel: [834669.721253] traps: dpkg[1455373] trap invalid opcode 
ip:7fa39701951d sp:7ffc4ad26e58 error:0 in libc-2.31.so[7fa396edd000+15a000]
kernel: [834669.732958] traps: dpkg[1455374] trap invalid opcode 
ip:7f529ca9551d sp:7fffb6f0a238 error:0 in libc-2.31.so[7f529c959000+15a000]
kernel: [834669.840128] traps: dpkg[1455375] trap invalid opcode 
ip:7f1874cc951d sp:7fffc2c2f5d8 error:0 in libc-2.31.so[7f1874b8d000+15a000]
kernel: [834669.907918] traps: dpkg[1455378] trap invalid opcode 
ip:7f3b4f8d851d sp:7fff3ec970f8 error:0 in libc-2.31.so[7f3b4f79c000+15a000]
kernel: [834712.152139] traps: passwd[1455693] trap invalid opcode 
ip:7fefee4b52b7 sp:7cb506b8 error:0 in libc-2.31.so[7fefee37d000+15a000]


Not sure what exactly might be causing the issue, but if these changes 
aren't pulled, potentially anyone with this or similar CPU as me will 
upgrade and end up with bricked system.
I will proceed to try using `clearcpuid=293` kernel flag myself, but 
consider how many distros depend on Debian, live CDs etc, with people 
unable to figure out why their system became useless, unable to trace 
the source, and blaming it just on Linux...


I'm filling this bug report from my downgraded host system to the 
previous libc6 version.


   * What led up to the situation? apt upgrade...
   * What exactly did you do (or not do) that was effective (or
 ineffective)? downgrade to +deb11u3
   * What was the outcome of this action? everything works on the older 
version

   * What outcome did you expect instead?


-- System Information:
Debian Release: 11.4
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 
'stable')

Architecture: amd64 (x86_64)

Kernel: Linux 5.15.39-1-pve (SMP w/4 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE 
not set

Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages libc6 depends on:
ii  libcrypt1  1:4.4.18-4
ii  libgcc-s1  10.2.1-6

Versions of packages libc6 recommends:
ii  libidn2-0   2.3.0-5
pn  libnss-nis  
pn  libnss-nisplus  

Versions of packages libc6 suggests:
ii  debconf [debconf-2.0]  1.5.77
pn  glibc-doc  
ii  libc-l10n  2.31-13+deb11u3
ii  locales2.31-13+deb11u3

-- debconf information:
  glibc/disable-screensaver:
  glibc/restart-services:
  glibc/kernel-not-supported:
  glibc/kernel-too-old:
  libraries/restart-without-asking: false
  glibc/restart-failed:
  glibc/upgrade: true

Bug#1011414: marked as done (ruby-task-list,ruby-deckar01-task-list: duplicate packages)

[Debian Bug Tracking System]

Your message dated Wed, 14 Sep 2022 21:50:47 +
with message-id 
and subject line Bug#1014813: Removed package(s) from unstable
has caused the Debian Bug report #1011414,
regarding ruby-task-list,ruby-deckar01-task-list: duplicate packages
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.)


-- 
1011414: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011414
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ruby-task-list,ruby-deckar01-task-list
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: found -1 2.3.2-1

Hi,

both ruby-task-list and ruby-deckar01-task-list seem to be the same
package, please coordinate which one to keep (and maybe add a
transitional package if you decide for the "newer" one).

  Selecting previously unselected package ruby-deckar01-task-list.
  (Reading database ... ^M(Reading database ... 5%^M(Reading database ... 
10%^M(Reading database ... 15%^M(Reading database ... 20%^M(Reading database 
... 25%^M(Reading database ... 30%^M(Reading database ... 35%^M(Reading 
database ... 40%^M(Reading database ... 45%^M(Reading database ... 
50%^M(Reading database ... 55%^M(Reading database ... 60%^M(Reading database 
... 65%^M(Reading database ... 70%^M(Reading database ... 75%^M(Reading 
database ... 80%^M(Reading database ... 85%^M(Reading database ... 
90%^M(Reading database ... 95%^M(Reading database ... 100%^M(Reading database 
... 9226 files and directories currently installed.)
  Preparing to unpack .../ruby-deckar01-task-list_2.3.2-2_all.deb ...
  Unpacking ruby-deckar01-task-list (2.3.2-2) ...
  dpkg: error processing archive 
/var/cache/apt/archives/ruby-deckar01-task-list_2.3.2-2_all.deb (--unpack):
   trying to overwrite 
'/usr/share/rubygems-integration/all/specifications/deckar01-task_list-2.3.2.gemspec',
 which is also in package ruby-task-list 2.3.2-1
  Errors were encountered while processing:
   /var/cache/apt/archives/ruby-deckar01-task-list_2.3.2-2_all.deb

Andreas
--- End Message ---
--- Begin Message ---
Version: 2.3.2-2+rm

Dear submitter,

as the package ruby-deckar01-task-list has just been removed from the Debian 
archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1014813

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Thorsten Alteholz (the ftpmaster behind the curtain)--- End Message ---

Bug#1019347: Please package new upstream which includes the fix

[Iustin Pop]

>From what I see, upstream version 1.7.1 fixes this
(https://github.com/borgmatic-collective/borgmatic/releases/tag/1.7.1):

#574: Fix for potential data loss (data not getting backed up) when the 
"patterns" option was
used with "source_directories" (or the "~/.borgmatic" path existed, which got 
injected into
"source_directories" implicitly). The fix is for borgmatic to convert 
"source_directories" into
patterns whenever "patterns" is used, working around a potential Borg bug:
borgbackup/borg#6994

Could you please package that (or the newer 1.7.2) to work around this?

thanks!
iustin

Bug#1014120: libowfat FTBFS: ln: failed to create hard link 'libowfat/buffer.h'

[Bastian Germann]

I have tried to fix this but as I am not able to reproduce this locally I am at 
a loss here.
Maybe someone else has an idea...

Bug#1019844: golang-v2ray-core FTBFS: undefined: quic.Session

[Adrian Bunk]

Source: golang-v2ray-core
Version: 4.34.0-7
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/logs.php?pkg=golang-v2ray-core=4.34.0-7%2Bb1

...
# v2ray.com/core/app/dns
src/v2ray.com/core/app/dns/nameserver_quic.go:41:19: undefined: quic.Session
src/v2ray.com/core/app/dns/nameserver_quic.go:319:22: undefined: quic.Session
src/v2ray.com/core/app/dns/nameserver_quic.go:328:45: undefined: quic.Session
src/v2ray.com/core/app/dns/nameserver_quic.go:329:19: undefined: quic.Session
src/v2ray.com/core/app/dns/nameserver_quic.go:362:46: undefined: quic.Session
...
make[1]: *** [debian/rules:31: override_dh_auto_build] Error 25

Bug#1019843: php-mysqlnd-ms FTBFS: PHP_DEFAULT_VERSION cannot be empty

[Adrian Bunk]

Source: php-mysqlnd-ms
Version: 1.6.0+svn333622-12
Severity: serious
Tags: ftbfs

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/php-mysqlnd-ms.html

...
 fakeroot debian/rules clean
PHP_DEFAULT_VERSION_DEFAULT := "8.1"
PHP_DEFAULT_VERSION_OVERRIDE := "5.6"
AVAILABLE_PHP_VERSIONS := "8.1"
/usr/share/dh-php/pkg-pecl.mk:39: *** PHP_DEFAULT_VERSION cannot be empty.  
Stop.
dpkg-buildpackage: error: fakeroot debian/rules clean subprocess returned exit 
status 2

Processed: python-xarray: new autopkgtest regression on s390x

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + patch
Bug #1019758 [src:python-xarray] python-xarray: new autopkgtest regression on 
s390x
Added tag(s) patch.

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

Bug#1019758: python-xarray: new autopkgtest regression on s390x

[Graham Inggs]

Control: tags -1 + patch

Please consider applying the attached patch.
Description: Allow test_indexes to pass on big-endian systems
Forwarded: https://github.com/pydata/xarray/pull/7026
Bug-Debian: https://bugs.debian.org/1019758
Author: Graham Inggs 
Last-Update: 2022-09-11

--- a/xarray/tests/test_indexes.py
+++ b/xarray/tests/test_indexes.py
@@ -264,13 +264,13 @@
 actual = index1.join(index2)
 print(actual.index)
 assert actual.equals(expected)
-assert actual.coord_dtype == " None:
 index1 = PandasIndex([0, 1, 2], "x")
@@ -380,7 +380,7 @@
 pd_midx = pd.MultiIndex.from_product(
 [[0, 1, 2], ["a", "b"]], names=("foo", "bar")
 )
-level_coords_dtype = {"foo": np.int32, "bar": "

Bug#1019758: python-xarray: new autopkgtest regression on s390x

[Graham Inggs]

Source: python-xarray
Version:  2022.06.0-1
Severity: serious
Forwarded: https://github.com/pydata/xarray/pull/7026
User: debian...@lists.debian.org
Usertags: regression

Hi Maintainer

Since the upload of python-xarray 2022.06.0-1, some new failing tests
appeared on the big-endian s390x architecture [1].  I've copied what I
hope is the relevant part of the log below.

Regards
Graham


[1] https://ci.debian.net/packages/p/python-xarray/testing/s390x/


=== FAILURES ===
__ TestPandasIndex.test_join ___

self = 

def test_join(self) -> None:
index1 = PandasIndex(["a", "aa", "aaa"], "x", coord_dtype="   assert actual.coord_dtype == "U4') == 'U4') = .coord_dtype

/usr/lib/python3/dist-packages/xarray/tests/test_indexes.py:267: AssertionError
- Captured stdout call -
Index(['aa', 'aaa'], dtype='object', name='x')
___ TestPandasMultiIndex.test_concat ___

self = 

def test_concat(self) -> None:
pd_midx = pd.MultiIndex.from_product(
[[0, 1, 2], ["a", "b"]], names=("foo", "bar")
)
level_coords_dtype = {"foo": np.int32, "bar": "   assert actual.level_coords_dtype == expected.level_coords_dtype
E   AssertionError: assert {'bar': dtype...type('int32')} ==
{'bar': '}
E Omitting 1 identical items, use -vv to show
E Differing items:
E {'bar': dtype('>U1')} != {'bar': '}
E + {'bar': dtype('>U1'), 'foo': dtype('int32')}

/usr/lib/python3/dist-packages/xarray/tests/test_indexes.py:395: AssertionError
 TestPandasMultiIndex.test_join 

self = 

def test_join(self):
midx = pd.MultiIndex.from_product([["a", "aa"], [1, 2]],
names=("one", "two"))
level_coords_dtype = {"one": "   assert actual.level_coords_dtype == level_coords_dtype
E   AssertionError: assert {'one': dtype...type('int32')} ==
{'one': 'U2')} != {'one': 'U2'), 'two': dtype('int32')}

/usr/lib/python3/dist-packages/xarray/tests/test_indexes.py:493: AssertionError

Processed: libpcre3-udeb: Can this be dropped?

[Debian Bug Tracking System]

Processing control commands:

> block -1 by 1019724
Bug #1019752 [libpcre3-udeb] libpcre3-udeb: Can this be dropped?
1019752 was not blocked by any bugs.
1019752 was not blocking any bugs.
Added blocking bug(s) of 1019752: 1019724

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

Bug#1019619: marked as done (ruby-did-you-mean: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed.)

[Debian Bug Tracking System]

Your message dated Wed, 14 Sep 2022 17:50:27 +
with message-id 
and subject line Bug#1019619: fixed in ruby-did-you-mean 1.6.1-1
has caused the Debian Bug report #1019619,
regarding ruby-did-you-mean: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed.
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.)


-- 
1019619: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019619
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-did-you-mean
Version: 1.2.1-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-r...@lists.debian.org
Usertags: ruby3.1

Hi,

We are about to start the ruby3.1 transition in unstable. While trying to
rebuild ruby-did-you-mean with ruby3.1 enabled, the build failed.

Relevant part of the build log (hopefully):
> /usr/bin/ruby3.1 /usr/bin/gem2deb-test-runner
> 
> ┌──┐
> │ Checking Rubygems dependency resolution on ruby3.1  
>  │
> └──┘
> 
> /<>/lib/did_you_mean/version.rb:2: warning: already initialized 
> constant DidYouMean::VERSION
> /usr/lib/ruby/3.1.0/did_you_mean/version.rb:2: warning: previous definition 
> of VERSION was here
> GEM_PATH=/<>/debian/ruby-did-you-mean/usr/share/rubygems-integration/all:/var/lib/gems/3.1.0:/usr/local/lib/ruby/gems/3.1.0:/usr/lib/ruby/gems/3.1.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.1.0:/usr/share/rubygems-integration/3.1.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.1.0
>  ruby3.1 -e gem\ \"did_you_mean\"
> 
> ┌──┐
> │ Run tests for ruby3.1 from debian/ruby-tests.rake   
>  │
> └──┘
> 
> RUBYLIB=/<>/debian/ruby-did-you-mean/usr/lib/ruby/vendor_ruby:. 
> GEM_PATH=/<>/debian/ruby-did-you-mean/usr/share/rubygems-integration/all:/var/lib/gems/3.1.0:/usr/local/lib/ruby/gems/3.1.0:/usr/lib/ruby/gems/3.1.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.1.0:/usr/share/rubygems-integration/3.1.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.1.0
>  ruby3.1 -S rake -f debian/ruby-tests.rake
> /usr/bin/ruby3.1 -w -I"test" 
> /usr/lib/ruby/gems/3.1.0/gems/rake-13.0.6/lib/rake/rake_test_loader.rb 
> "test/core_ext/name_error_extension_test.rb" 
> "test/deprecated_formatter_test.rb" "test/edit_distance/jaro_winkler_test.rb" 
> "test/spell_checker_test.rb" "test/spell_checking/class_name_check_test.rb" 
> "test/spell_checking/key_name_check_test.rb" 
> "test/spell_checking/method_name_check_test.rb" 
> "test/spell_checking/uncorrectable_name_check_test.rb" 
> "test/spell_checking/variable_name_check_test.rb" -v
> /<>/test/spell_checking/variable_name_check_test.rb:61: warning: 
> assigned but unused variable - some_var
> DidYouMean version: 1.2.1
> Run options: -v --seed 22188
> 
> # Running:
> 
> KeyNameCheckTest#test_corrects_hash_key_name_with_fetch = 0.00 s = .
> KeyNameCheckTest#test_corrects_hash_key_name_with_fetch_values = 0.00 s = .
> KeyNameCheckTest#test_corrects_sprintf_key_name = 0.00 s = .
> KeyNameCheckTest#test_corrects_env_key_name = 0.00 s = .
> DeprecatedFormatterTest#test_deprecated_formatter = 0.00 s = .
> SpellCheckerTest#test_spell_checker_corrects_misspells = 0.00 s = .
> SpellCheckerTest#test_spell_checker_excludes_input_from_dictionary = 0.00 s = 
> .
> SpellCheckerTest#test_spell_checker_sorts_results_by_simiarity = 0.00 s = .
> SpellCheckerTest#test_spell_checker_corrects_mistypes = 0.00 s = .
> UncorrectableNameCheckTest#test_message = 0.01 s = F
> MethodNameCheckTest#test_corrections_include_method_from_module = 0.00 s = .
> MethodNameCheckTest#test_does_not_append_suggestions_three_times = 0.00 s = .
> MethodNameCheckTest#test_exclude_methods_on_nil = 0.00 s = .
> MethodNameCheckTest#test_corrections_include_instance_method = 0.00 s = .
> MethodNameCheckTest#test_corrections_include_class_method = 0.00 s = .
> MethodNameCheckTest#test_private_methods_should_not_be_suggested = 0.00 s = .
> MethodNameCheckTest#test_corrections_include_private_method = 0.00 s = .
> MethodNameCheckTest#test_does_not_append_suggestions_twice = 0.00 s = .
> MethodNameCheckTest#test_corrections_when_private_method_is_called_with_args 
> = 0.00 s = .
> MethodNameCheckTest#test_does_not_exclude_custom_methods_on_nil = 0.00 s = .
> NameErrorExtensionTest#test_message = 0.00 s = S
> 

Bug#960679: marked as done (fontconfig: strict dependency of arch:any libfontconfig1 on arch:all fontconfig-config going wrong)

[Debian Bug Tracking System]

Your message dated Wed, 14 Sep 2022 17:34:44 +
with message-id 
and subject line Bug#960679: fixed in fontconfig 2.13.1-4.5
has caused the Debian Bug report #960679,
regarding fontconfig: strict dependency of arch:any libfontconfig1 on arch:all 
fontconfig-config going wrong
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.)


-- 
960679: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960679
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: fontconfig
Version: 2.13.1-2
Severity: serious

libfontconfig1 Depends on fontconfig-config (>= ${source:Version})

If the arch:amd64 buildd is faster than the arch:all one, as happened
with 2.13.1-4.1, the new libfontconfig1 becomes uninstallable, and,
because fontconfig indirectly build-depends on libfontconfig1, that
situation can't fix itself.

One way around that is to make fontconfig-config arch:any; there may be
other solutions.

Cheers,
Julien
--- End Message ---
--- Begin Message ---
Source: fontconfig
Source-Version: 2.13.1-4.5
Done: Johannes Schauer Marin Rodrigues 

We believe that the bug you reported is fixed in the latest version of
fontconfig, 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 960...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Johannes Schauer Marin Rodrigues  (supplier of updated 
fontconfig 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, 04 Sep 2022 18:37:48 +0200
Source: fontconfig
Architecture: source
Version: 2.13.1-4.5
Distribution: unstable
Urgency: medium
Maintainer: Debian freedesktop.org maintainers 

Changed-By: Johannes Schauer Marin Rodrigues 
Closes: 960679
Changes:
 fontconfig (2.13.1-4.5) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Make fontconfig-config arch:any. If one of the arch:any buildds is faster
 than the arch:all one, the new libfontconfig1 becomes uninstallable, and,
 because fontconfig indirectly build-depends on libfontconfig1, that
 situation can't fix itself. Turning fontconfig-config from arch:all to
 arch:any prevents this from happening. (closes: #960679)
Checksums-Sha1:
 f6b021a033bfd0bc50e840509a5376f7bc6dda68 2687 fontconfig_2.13.1-4.5.dsc
 0c7a4e57ac8848ca0b34bfd64db3e71d16228c64 56244 
fontconfig_2.13.1-4.5.debian.tar.xz
 76922413db18960209bbff69259276b5d7dfb9e0 11433 
fontconfig_2.13.1-4.5_amd64.buildinfo
Checksums-Sha256:
 2c71a85d457f50aa3e179768a2c448764882be11f0aab944a817b5b076ea096e 2687 
fontconfig_2.13.1-4.5.dsc
 886bcb0f34349a368e886e8d7054c8dbbbe35cfc45cce1a44495dda88af3fad8 56244 
fontconfig_2.13.1-4.5.debian.tar.xz
 12beea9ab769fc0a8fc576326b3eb2a19c3ceb10d4e8492a1778b1033b32c035 11433 
fontconfig_2.13.1-4.5_amd64.buildinfo
Files:
 5046e0aec0f7286aadda74ea08ed12f2 2687 fonts optional fontconfig_2.13.1-4.5.dsc
 d3fdb39465ca223ebdadd2e1311bd4b7 56244 fonts optional 
fontconfig_2.13.1-4.5.debian.tar.xz
 13894afdab2223bb5e5be4f6c7f86935 11433 fonts optional 
fontconfig_2.13.1-4.5_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEElFhU6KL81LF4wVq58sulx4+9g+EFAmMU12EACgkQ8sulx4+9
g+Fo3w/8DGgrinSAJPINvyK6pLhYWxhD6ALttDmK8g0BXESZKNwy7+aXQOYKAHzO
Jy+3HhzQrUoxOQUhVXMKTKwkEqoX8A2/v5Bf4djH45vW7idSDLvBpaszPxFax690
nhxYuLI8FBjI7G7EKsQG9Ec86eLsTjno/ef/UzJmUBM+pqhtwbOkWJiVcQoQqX87
59xzXhn/YoFLBuoU6h7wMm1nKqrsK8+or8pC8y9PT5hKrT7HjcMs76tRNJFWDd40
fweHpV86oihWZdE1d7/1tq9vjG65bOA17KNGV+CImZy27df9/UcjhxpCq80mtmID
Zl/NKMEI/Akxv+ALkpz7ZKEVBtBrNDaB9MWB7xggkyF1U2YddJijNniepDDxQ3G3
0tFhMb1l8yFXEhmqiJxRawE+WEQguw2yhxcZMikRwqdWtCUgvNhPn5HEILkp3OmS
U4V1wVzH5nK+S3YDJl5m6zpsQzxePYgHuELiNwPt4CiwSQmHbqhax0NhuLVgnzf/
urV9ppE2+TaWeI6ZIxsYe/HWROffzXid/h2uDu8UHjR5JMNot/ZA3UQiScYTsCMp
M5r2NXl7+4eOKmAIgj2bo2qOMprz0UCVsdHnJYRhqcqz+hBD3WbtcQAyiChSmmgp
401+fa8ypkb5onpn9+KxdSnF5OJ1Z7hMs0L0uhyR3r0jbfcQ9xk=
=lLZR
-END PGP SIGNATURE End Message ---

Bug#1015035: marked as done (pcb-rnd: FTBFS: dh_auto_test: error: make -j8 test "TESTSUITEFLAGS=-j8 --verbose" VERBOSE=1 returned exit code 2)

[Debian Bug Tracking System]

Your message dated Wed, 14 Sep 2022 09:53:21 -0600 (MDT)
with message-id <20220914155321.7750824e0...@rover.gag.com>
and subject line fixed in current unstable
has caused the Debian Bug report #1015035,
regarding pcb-rnd: FTBFS: dh_auto_test: error: make -j8 test 
"TESTSUITEFLAGS=-j8 --verbose" VERBOSE=1 returned exit code 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.)


-- 
1015035: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015035
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pcb-rnd
Version: 3.0.4-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220716 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[4]: Entering directory '/<>/tests/conf/tests'
> Segmentation fault
> make[4]: *** [Makefile:17: arr_merge.out] Error 139
> make[4]: *** Waiting for unfinished jobs
> Segmentation fault
> make[4]: *** [Makefile:17: arr_set.out] Error 139
> Segmentation fault
> make[4]: *** [Makefile:17: scalar.out] Error 139
> Segmentation fault
> make[4]: *** [Makefile:17: list_merge.out] Error 139
> Segmentation fault
> make[4]: *** [Makefile:17: list_set.out] Error 139
> rm arr_merge.out arr_set.out scalar.out list_merge.out list_set.out
> make[4]: Leaving directory '/<>/tests/conf/tests'
> make[3]: *** [Makefile:38: test] Error 2
> make[3]: Leaving directory '/<>/tests/conf'
> make[2]: *** [Makefile:4: test] Error 2
> make[2]: Leaving directory '/<>/tests'
> make[1]: *** [Makefile:8: test] Error 2
> make[1]: Leaving directory '/<>'
> dh_auto_test: error: make -j8 test "TESTSUITEFLAGS=-j8 --verbose" VERBOSE=1 
> returned exit code 2


The full build log is available from:
http://qa-logs.debian.net/2022/07/16/pcb-rnd_3.0.4-1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220716;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20220716=lu...@debian.org=1=1=1=1#results

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

If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
This problem is no longer present in the version currently in unstable.

Bdale--- End Message ---

Processed: Re: qreator: won't start

[Debian Bug Tracking System]

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

> severity 994695 serious
Bug #994695 [qreator] qreator: won't start
Severity set to 'serious' from 'normal'
>
End of message, stopping processing here.

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

Bug#1019724: warning: stray \ before - causes autopkgtest failure

[Santiago Ruano Rincón]

Hi Jochen,

El 14/09/22 a las 15:16, Jochen Sprickerhof escribió:
> Hi Santiago,
> 
> * Santiago Ruano Rincón  [2022-09-14 10:36]:
> > > this causes build failures:
> > > 
> > > https://tests.reproducible-builds.org/debian/rb-pkg/unstable/arm64/libtool.html
> > > 
> > > and also autopkgtest failures:
> > > 
> > > https://ci.debian.net/data/autopkgtest/unstable/amd64/d/dpkg/26032114/log.gz
> > > https://ci.debian.net/data/autopkgtest/unstable/amd64/c/cjet/26041201/log.gz
> > > 
> > > The first autopkgtest failure is in libtool which is vendored by a lot
> > > of packages so will probably take a long time to fix.
> > > 
> > 
> > Fixing this would require fixing libtool only, isn't that right?
> 
> I don't think so, as it is in a lot of packages:
> 
> https://codesearch.debian.net/search?q=Configured+with%3A%22+%7C+%24GREP+%22+%5C-L
> 
> (Note that the buggy libtool.m4 is included into configure.)

Yeah, sorry. I lately realised not all the packages would autoreconf
during building time.

So silencing these warnings would make sense.

> 
> > > P.S.: I will send a bug with a patch to the libtool maintainer.
> > 
> > Please do.
> 
> Done as #1019725.
> 
> > P.S. I am letting Severity: serious for now to prevent migration to
> > testing. But *I* am considering this rather Severity: important, at
> > most.
> 
> Note that the release team issued a block for now:
> 
> https://release.debian.org/britney/hints/jcristau
> 
> and proposed to test with a archive rebuild before introducing it again.

ACK.

Dear Release Team, just to be sure of being on the same page: if you are
proposing to rebuild the whole archive, should I wait before silencing
the warnings, for being able to (mass-)bug filing?

Thanks,

 -- Santiago


signature.asc
Description: PGP signature

Bug#1019749: linux autopkg tests fail with stderr output, blocking gcc-11

[Matthias Klose]

Package: src:linux
Version: 5.19.6-1
Severity: serious
Tags: sid bookworm

linux autopkg tests fail with stderr output, blocking gcc-11

[...]
E: Unexpected warning/error messages
autopkgtest [14:13:45]:  summary
selftestsSKIP Test restriction "isolation-machine" requires testbed 
capability "isolation-machine"
selftestsSKIP Test restriction "isolation-machine" requires testbed 
capability "isolation-machine"

python   PASS (superficial)
kbuild   FAIL stderr: E: Unexpected warning/error messages

Bug#1019579: raku-json-unmarshal: trying to overwrite '/usr/lib/perl6/vendor/precomp/C847F303DB03DE97DCB92EFEE90C0526E0D4FDF0/C1/C1DA909DAD9BF713751A74EBF038C545A1EA6ECC', which is also in package rak

[Dominique Dumont]

On Monday, 12 September 2022 16:21:45 CEST Adrian Bunk wrote:
> ...
> Unpacking raku-json-unmarshal (0.10-1) ...
> dpkg: error processing archive
> /tmp/apt-dpkg-install-Kxnez1/92-raku-json-unmarshal_0.10-1_arm64.deb
> (--unpack): trying to overwrite
> '/usr/lib/perl6/vendor/precomp/C847F303DB03DE97DCB92EFEE90C0526E0D4FDF0/C1/
> C1DA909DAD9BF713751A74EBF038C545A1EA6ECC', which is also in package
> raku-json-marshal 0.0.23-1 ...
> 

ok. I don't' really understand what's going on with these precompiled files.

I've asked for help upstream.

Thanks for the heads-up

All the best.

Processed: fixed 1019721 in 4.1.4-2.1~

[Debian Bug Tracking System]

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

> fixed 1019721 4.1.4-2.1~
Bug #1019721 {Done: Tobias Frost } [libopenmpi-dev] 
libopenmpi-dev: Cannot uninstall rmdir: failed to remove 
'/usr/lib/x86_64-linux-gnu/fortran/gfortran': No such file or directory
There is no source info for the package 'libopenmpi-dev' at version 
'4.1.4-2.1~' with architecture ''
Unable to make a source version for version '4.1.4-2.1~'
Marked as fixed in versions 4.1.4-2.1~.
> thanks
Stopping processing here.

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

Processed: notfixed 1019721 in 4.1.4-2+b1

[Debian Bug Tracking System]

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

> notfixed 1019721 4.1.4-2+b1
Bug #1019721 {Done: Tobias Frost } [libopenmpi-dev] 
libopenmpi-dev: Cannot uninstall rmdir: failed to remove 
'/usr/lib/x86_64-linux-gnu/fortran/gfortran': No such file or directory
Ignoring request to alter fixed versions of bug #1019721 to the same values 
previously set
> thanks
Stopping processing here.

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

Processed: fixed 1019721 in 4.1.4-2+b1

[Debian Bug Tracking System]

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

> fixed 1019721 4.1.4-2+b1
Bug #1019721 {Done: Tobias Frost } [libopenmpi-dev] 
libopenmpi-dev: Cannot uninstall rmdir: failed to remove 
'/usr/lib/x86_64-linux-gnu/fortran/gfortran': No such file or directory
Marked as fixed in versions openmpi/4.1.4-2.
> thanks
Stopping processing here.

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

Bug#1019721: marked as done (libopenmpi-dev: Cannot uninstall rmdir: failed to remove '/usr/lib/x86_64-linux-gnu/fortran/gfortran': No such file or directory)

[Debian Bug Tracking System]

Your message dated Wed, 14 Sep 2022 15:37:03 +0200
with message-id 
and subject line Re: libopenmpi-dev: Cannot uninstall rmdir: failed to remove 
'/usr/lib/x86_64-linux-gnu/fortran/gfortran': No such file or directory
has caused the Debian Bug report #1019721,
regarding libopenmpi-dev: Cannot uninstall rmdir: failed to remove 
'/usr/lib/x86_64-linux-gnu/fortran/gfortran': No such file or directory
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.)


-- 
1019721: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019721
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libopenmpi-dev
Version: 4.1.4-2
Severity: serious

Hello,

it seems to be impossible to uninstall libopenmpi-dev:
(sid)root@argenau:/# dpkg --purge libopenmpi-dev
(Reading database ... 25167 files and directories currently installed.)
Removing libopenmpi-dev:amd64 (4.1.4-2) ...
rmdir: failed to remove '/usr/lib/x86_64-linux-gnu/fortran/gfortran': No such 
file or directory
dpkg: error processing package libopenmpi-dev:amd64 (--purge):
[...]

Looking at the postrm script we find:
(sid)root@argenau:/# grep ^rmdir 
/var/lib/dpkg/info/libopenmpi-dev\:amd64.postrm 
rmdir --ignore-fail-on-non-empty /usr/lib/$multiarch/fortran/gfortran
rmdir --ignore-fail-on-non-empty /usr/lib/$multiarch/fortran/gfortran
rmdir --ignore-fail-on-non-empty /usr/lib/$multiarch/fortran/gfortran
rmdir --ignore-fail-on-non-empty /usr/lib/$multiarch/fortran/gfortran
rmdir --ignore-fail-on-non-empty /usr/lib/$multiarch/fortran/gfortran

i.e. rmdir is run unconditiionally multiple times on the same directory,
the first instance succeeds, the second one fails.

This is #1019050 in dh-fortran-mod which is now fixed. However
libopenmpi-dev 4.1.4-2 contains the broken code generated by
dh-fortran-mod and needs a rebuild against dh-fortran-mod (0.27) and
should not propagate to testing.

Is there a way to find all packages built against broken dh-fortran-mod
so all affected packages can be rebuilt?

cu Andreas
--- End Message ---
--- Begin Message ---
Thanks to the release team, a binNMU has been scheduled.--- End Message ---

Bug#1019724: warning: stray \ before - causes autopkgtest failure

[Jochen Sprickerhof]

Hi Santiago,

* Santiago Ruano Rincón  [2022-09-14 10:36]:

this causes build failures:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/arm64/libtool.html

and also autopkgtest failures:

https://ci.debian.net/data/autopkgtest/unstable/amd64/d/dpkg/26032114/log.gz
https://ci.debian.net/data/autopkgtest/unstable/amd64/c/cjet/26041201/log.gz

The first autopkgtest failure is in libtool which is vendored by a lot
of packages so will probably take a long time to fix.



Fixing this would require fixing libtool only, isn't that right?


I don't think so, as it is in a lot of packages:

https://codesearch.debian.net/search?q=Configured+with%3A%22+%7C+%24GREP+%22+%5C-L

(Note that the buggy libtool.m4 is included into configure.)


P.S.: I will send a bug with a patch to the libtool maintainer.


Please do.


Done as #1019725.


P.S. I am letting Severity: serious for now to prevent migration to
testing. But *I* am considering this rather Severity: important, at
most.


Note that the release team issued a block for now:

https://release.debian.org/britney/hints/jcristau

and proposed to test with a archive rebuild before introducing it again.


signature.asc
Description: PGP signature

Bug#1006788: autopkgtest fails on hosts with lots of RAM/cores

[Graham Inggs]

It's probably worth trying to set
BAGEL_NUM_THREADS=4
or similar in the autopkgtest.

From: https://nubakery.org/quickstart/how_to_run_bagel.html

Bug#1017317: marked as done (webcamoid: FTBFS: abstractstream.h:60:21: error: ‘AVCodecContext’ does not name a type; did you mean ‘AVIODirContext’?)

[Debian Bug Tracking System]

Your message dated Wed, 14 Sep 2022 12:23:02 +
with message-id 
and subject line Bug#1017317: fixed in webcamoid 9.0.0-5
has caused the Debian Bug report #1017317,
regarding webcamoid: FTBFS: abstractstream.h:60:21: error: ‘AVCodecContext’ 
does not name a type; did you mean ‘AVIODirContext’?
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.)


-- 
1017317: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017317
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: webcamoid
Version: 9.0.0-4
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220813 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> cd 
> /<>/obj-x86_64-linux-gnu/libAvKys/Plugins/VideoCapture/src/convert/ffmpeg
>  && /usr/bin/c++ -DAVKYS_PLUGIN_VIDEOCAPTURE_FFMPEG -DQT_CONCURRENT_LIB 
> -DQT_CORE_LIB -DQT_DEPRECATED_WARNINGS -DQT_GUI_LIB -DQT_NETWORK_LIB 
> -DQT_NO_DEBUG -DQT_QMLMODELS_LIB -DQT_QML_LIB -DQT_QUICK_LIB -DQT_WIDGETS_LIB 
> -DVideoCapture_ffmpeg_EXPORTS 
> -I/<>/obj-x86_64-linux-gnu/libAvKys/Plugins/VideoCapture/src/convert/ffmpeg
>  -I/<>/libAvKys/Plugins/VideoCapture/src/convert/ffmpeg 
> -I/<>/obj-x86_64-linux-gnu/libAvKys/Plugins/VideoCapture/src/convert/ffmpeg/VideoCapture_ffmpeg_autogen/include
>  -I/<>/libAvKys/Plugins/VideoCapture/src/convert/ffmpeg/../.. 
> -I/<>/libAvKys/Plugins/VideoCapture/src/convert/ffmpeg/../../../../../Lib/src
>  -isystem /usr/include/x86_64-linux-gnu/qt5 -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtConcurrent -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtCore -isystem 
> /usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtQuick -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtQmlModels -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtQml -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtNetwork -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtGui -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtWidgets -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -fPIC 
> -std=gnu++11 -MD -MT 
> libAvKys/Plugins/VideoCapture/src/convert/ffmpeg/CMakeFiles/VideoCapture_ffmpeg.dir/src/clock.cpp.o
>  -MF CMakeFiles/VideoCapture_ffmpeg.dir/src/clock.cpp.o.d -o 
> CMakeFiles/VideoCapture_ffmpeg.dir/src/clock.cpp.o -c 
> /<>/libAvKys/Plugins/VideoCapture/src/convert/ffmpeg/src/clock.cpp
> In file included from 
> /<>/libAvKys/Plugins/MultiSrc/src/ffmpeg/src/audiostream.h:23,
>  from 
> /<>/libAvKys/Plugins/MultiSrc/src/ffmpeg/src/mediasourceffmpeg.cpp:40:
> /<>/libAvKys/Plugins/MultiSrc/src/ffmpeg/src/abstractstream.h:60:21:
>  error: ‘AVCodecContext’ does not name a type; did you mean ‘AVIODirContext’?
>60 | Q_INVOKABLE AVCodecContext *codecContext() const;
>   | ^~
>   | AVIODirContext
> /<>/libAvKys/Plugins/MultiSrc/src/ffmpeg/src/abstractstream.h:71:42:
>  error: ‘AVSubtitle’ has not been declared
>71 | Q_INVOKABLE void subtitleEnqueue(AVSubtitle *subtitle);
>   |  ^~
> /<>/libAvKys/Plugins/MultiSrc/src/ffmpeg/src/abstractstream.h:84:34:
>  error: ‘AVSubtitle’ has not been declared
>84 | virtual void processData(AVSubtitle *subtitle);
>   |  ^~
> In file included from 
> /<>/libAvKys/Plugins/MultiSrc/src/ffmpeg/src/mediasourceffmpeg.cpp:42:
> /<>/libAvKys/Plugins/MultiSrc/src/ffmpeg/src/subtitlestream.h:43:26:
>  error: ‘AVSubtitle’ has not been declared
>43 | void processData(AVSubtitle *subtitle);
>   |  ^~
> make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu'
> [ 37%] Built target VideoCaptureSrc
> make  -f 
> libAvKys/Plugins/VideoCapture/src/convert/generic/CMakeFiles/VideoCapture_generic.dir/build.make
>  
> libAvKys/Plugins/VideoCapture/src/convert/generic/CMakeFiles/VideoCapture_generic.dir/depend
> make[3]: Entering directory '/<>/obj-x86_64-linux-gnu'
> cd /<>/obj-x86_64-linux-gnu && /usr/bin/cmake -E cmake_depends 
> "Unix Makefiles" /<> 
> /<>/libAvKys/Plugins/VideoCapture/src/convert/generic 
> /<>/obj-x86_64-linux-gnu 
> /<>/obj-x86_64-linux-gnu/libAvKys/Plugins/VideoCapture/src/convert/generic
>  
> /<>/obj-x86_64-linux-gnu/libAvKys/Plugins/VideoCapture/src/convert/generic/CMakeFiles/VideoCapture_generic.dir/DependInfo.cmake
>  --color=
> make[3]: Leaving directory 

Bug#1017179: marked as done (webcamoid: FTBFS: abstractstream.h:60:21: error: ‘AVCodecContext’ does not name a type; did you mean ‘AVIODirContext’?)

[Debian Bug Tracking System]

Your message dated Wed, 14 Sep 2022 12:23:02 +
with message-id 
and subject line Bug#1017317: fixed in webcamoid 9.0.0-5
has caused the Debian Bug report #1017317,
regarding webcamoid: FTBFS: abstractstream.h:60:21: error: ‘AVCodecContext’ 
does not name a type; did you mean ‘AVIODirContext’?
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.)


-- 
1017317: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017317
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: webcamoid
Version: 9.0.0-4
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220813 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> cd 
> /<>/obj-x86_64-linux-gnu/libAvKys/Plugins/VideoCapture/src/convert/ffmpeg
>  && /usr/bin/c++ -DAVKYS_PLUGIN_VIDEOCAPTURE_FFMPEG -DQT_CONCURRENT_LIB 
> -DQT_CORE_LIB -DQT_DEPRECATED_WARNINGS -DQT_GUI_LIB -DQT_NETWORK_LIB 
> -DQT_NO_DEBUG -DQT_QMLMODELS_LIB -DQT_QML_LIB -DQT_QUICK_LIB -DQT_WIDGETS_LIB 
> -DVideoCapture_ffmpeg_EXPORTS 
> -I/<>/obj-x86_64-linux-gnu/libAvKys/Plugins/VideoCapture/src/convert/ffmpeg
>  -I/<>/libAvKys/Plugins/VideoCapture/src/convert/ffmpeg 
> -I/<>/obj-x86_64-linux-gnu/libAvKys/Plugins/VideoCapture/src/convert/ffmpeg/VideoCapture_ffmpeg_autogen/include
>  -I/<>/libAvKys/Plugins/VideoCapture/src/convert/ffmpeg/../.. 
> -I/<>/libAvKys/Plugins/VideoCapture/src/convert/ffmpeg/../../../../../Lib/src
>  -isystem /usr/include/x86_64-linux-gnu/qt5 -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtConcurrent -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtCore -isystem 
> /usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtQuick -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtQmlModels -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtQml -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtNetwork -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtGui -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtWidgets -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -fPIC 
> -std=gnu++11 -MD -MT 
> libAvKys/Plugins/VideoCapture/src/convert/ffmpeg/CMakeFiles/VideoCapture_ffmpeg.dir/src/clock.cpp.o
>  -MF CMakeFiles/VideoCapture_ffmpeg.dir/src/clock.cpp.o.d -o 
> CMakeFiles/VideoCapture_ffmpeg.dir/src/clock.cpp.o -c 
> /<>/libAvKys/Plugins/VideoCapture/src/convert/ffmpeg/src/clock.cpp
> In file included from 
> /<>/libAvKys/Plugins/MultiSrc/src/ffmpeg/src/audiostream.h:23,
>  from 
> /<>/libAvKys/Plugins/MultiSrc/src/ffmpeg/src/mediasourceffmpeg.cpp:40:
> /<>/libAvKys/Plugins/MultiSrc/src/ffmpeg/src/abstractstream.h:60:21:
>  error: ‘AVCodecContext’ does not name a type; did you mean ‘AVIODirContext’?
>60 | Q_INVOKABLE AVCodecContext *codecContext() const;
>   | ^~
>   | AVIODirContext
> /<>/libAvKys/Plugins/MultiSrc/src/ffmpeg/src/abstractstream.h:71:42:
>  error: ‘AVSubtitle’ has not been declared
>71 | Q_INVOKABLE void subtitleEnqueue(AVSubtitle *subtitle);
>   |  ^~
> /<>/libAvKys/Plugins/MultiSrc/src/ffmpeg/src/abstractstream.h:84:34:
>  error: ‘AVSubtitle’ has not been declared
>84 | virtual void processData(AVSubtitle *subtitle);
>   |  ^~
> In file included from 
> /<>/libAvKys/Plugins/MultiSrc/src/ffmpeg/src/mediasourceffmpeg.cpp:42:
> /<>/libAvKys/Plugins/MultiSrc/src/ffmpeg/src/subtitlestream.h:43:26:
>  error: ‘AVSubtitle’ has not been declared
>43 | void processData(AVSubtitle *subtitle);
>   |  ^~
> make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu'
> [ 37%] Built target VideoCaptureSrc
> make  -f 
> libAvKys/Plugins/VideoCapture/src/convert/generic/CMakeFiles/VideoCapture_generic.dir/build.make
>  
> libAvKys/Plugins/VideoCapture/src/convert/generic/CMakeFiles/VideoCapture_generic.dir/depend
> make[3]: Entering directory '/<>/obj-x86_64-linux-gnu'
> cd /<>/obj-x86_64-linux-gnu && /usr/bin/cmake -E cmake_depends 
> "Unix Makefiles" /<> 
> /<>/libAvKys/Plugins/VideoCapture/src/convert/generic 
> /<>/obj-x86_64-linux-gnu 
> /<>/obj-x86_64-linux-gnu/libAvKys/Plugins/VideoCapture/src/convert/generic
>  
> /<>/obj-x86_64-linux-gnu/libAvKys/Plugins/VideoCapture/src/convert/generic/CMakeFiles/VideoCapture_generic.dir/DependInfo.cmake
>  --color=
> make[3]: Leaving directory 

Bug#1019287: marked as done (libsuperlu-dist-dev: installed libsuperlu-dist-dev:amd64 package post-removal script subprocess returned error exit status 1)

[Debian Bug Tracking System]

Your message dated Wed, 14 Sep 2022 14:26:09 +0200
with message-id 
and subject line Re: Bug#1019287: libsuperlu-dist-dev: installed 
libsuperlu-dist-dev:amd64 package post-removal script subprocess returned error 
exit status 1
has caused the Debian Bug report #1019287,
regarding libsuperlu-dist-dev: installed libsuperlu-dist-dev:amd64 package 
post-removal script subprocess returned error exit status 1
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.)


-- 
1019287: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019287
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libsuperlu-dist-dev
Version: 8.1.0+dfsg1-2
Severity: serious

>From piuparts:

(Reading database ... 10034 files and directories currently installed.)
Removing libsuperlu-dist-dev:amd64 (8.1.0+dfsg1-2) ...
rmdir: failed to remove '/usr/lib/x86_64-linux-gnu/fortran/gfortran': No such 
file or directory
dpkg: error processing package libsuperlu-dist-dev:amd64 (--remove):
 installed libsuperlu-dist-dev:amd64 package post-removal script subprocess 
returned error exit status 1
dpkg: too many errors, stopping
Errors were encountered while processing:
 libsuperlu-dist-dev:amd64
Processing was halted because there were too many errors.
E: Sub-process /usr/bin/dpkg returned an error code (1)

https://piuparts.debian.org/sid/fail/libsuperlu-dist-dev_8.1.0+dfsg1-2.log

Cheers
-- 
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
On 2022-09-06 22:50:00 +0200, Sebastian Ramacher wrote:
> Package: libsuperlu-dist-dev
> Version: 8.1.0+dfsg1-2
> Severity: serious
> 
> From piuparts:
> 
> (Reading database ... 10034 files and directories currently installed.)
> Removing libsuperlu-dist-dev:amd64 (8.1.0+dfsg1-2) ...
> rmdir: failed to remove '/usr/lib/x86_64-linux-gnu/fortran/gfortran': No such 
> file or directory
> dpkg: error processing package libsuperlu-dist-dev:amd64 (--remove):
>  installed libsuperlu-dist-dev:amd64 package post-removal script subprocess 
> returned error exit status 1
> dpkg: too many errors, stopping
> Errors were encountered while processing:
>  libsuperlu-dist-dev:amd64
> Processing was halted because there were too many errors.
> E: Sub-process /usr/bin/dpkg returned an error code (1)
> 
> https://piuparts.debian.org/sid/fail/libsuperlu-dist-dev_8.1.0+dfsg1-2.log

With dh-fortran-mod fixed, I've scheduled binNMUs to resolve this issue.

Cheers
-- 
Sebastian Ramacher--- End Message ---

Bug#1017179: marked as done (webcamoid: FTBFS: abstractstream.h:60:21: error: ‘AVCodecContext’ does not name a type; did you mean ‘AVIODirContext’?)

[Debian Bug Tracking System]

Your message dated Wed, 14 Sep 2022 12:23:02 +
with message-id 
and subject line Bug#1017179: fixed in webcamoid 9.0.0-5
has caused the Debian Bug report #1017179,
regarding webcamoid: FTBFS: abstractstream.h:60:21: error: ‘AVCodecContext’ 
does not name a type; did you mean ‘AVIODirContext’?
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.)


-- 
1017179: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017179
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: webcamoid
Version: 9.0.0-4
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220813 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> cd 
> /<>/obj-x86_64-linux-gnu/libAvKys/Plugins/VideoCapture/src/convert/ffmpeg
>  && /usr/bin/c++ -DAVKYS_PLUGIN_VIDEOCAPTURE_FFMPEG -DQT_CONCURRENT_LIB 
> -DQT_CORE_LIB -DQT_DEPRECATED_WARNINGS -DQT_GUI_LIB -DQT_NETWORK_LIB 
> -DQT_NO_DEBUG -DQT_QMLMODELS_LIB -DQT_QML_LIB -DQT_QUICK_LIB -DQT_WIDGETS_LIB 
> -DVideoCapture_ffmpeg_EXPORTS 
> -I/<>/obj-x86_64-linux-gnu/libAvKys/Plugins/VideoCapture/src/convert/ffmpeg
>  -I/<>/libAvKys/Plugins/VideoCapture/src/convert/ffmpeg 
> -I/<>/obj-x86_64-linux-gnu/libAvKys/Plugins/VideoCapture/src/convert/ffmpeg/VideoCapture_ffmpeg_autogen/include
>  -I/<>/libAvKys/Plugins/VideoCapture/src/convert/ffmpeg/../.. 
> -I/<>/libAvKys/Plugins/VideoCapture/src/convert/ffmpeg/../../../../../Lib/src
>  -isystem /usr/include/x86_64-linux-gnu/qt5 -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtConcurrent -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtCore -isystem 
> /usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtQuick -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtQmlModels -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtQml -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtNetwork -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtGui -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtWidgets -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -fPIC 
> -std=gnu++11 -MD -MT 
> libAvKys/Plugins/VideoCapture/src/convert/ffmpeg/CMakeFiles/VideoCapture_ffmpeg.dir/src/clock.cpp.o
>  -MF CMakeFiles/VideoCapture_ffmpeg.dir/src/clock.cpp.o.d -o 
> CMakeFiles/VideoCapture_ffmpeg.dir/src/clock.cpp.o -c 
> /<>/libAvKys/Plugins/VideoCapture/src/convert/ffmpeg/src/clock.cpp
> In file included from 
> /<>/libAvKys/Plugins/MultiSrc/src/ffmpeg/src/audiostream.h:23,
>  from 
> /<>/libAvKys/Plugins/MultiSrc/src/ffmpeg/src/mediasourceffmpeg.cpp:40:
> /<>/libAvKys/Plugins/MultiSrc/src/ffmpeg/src/abstractstream.h:60:21:
>  error: ‘AVCodecContext’ does not name a type; did you mean ‘AVIODirContext’?
>60 | Q_INVOKABLE AVCodecContext *codecContext() const;
>   | ^~
>   | AVIODirContext
> /<>/libAvKys/Plugins/MultiSrc/src/ffmpeg/src/abstractstream.h:71:42:
>  error: ‘AVSubtitle’ has not been declared
>71 | Q_INVOKABLE void subtitleEnqueue(AVSubtitle *subtitle);
>   |  ^~
> /<>/libAvKys/Plugins/MultiSrc/src/ffmpeg/src/abstractstream.h:84:34:
>  error: ‘AVSubtitle’ has not been declared
>84 | virtual void processData(AVSubtitle *subtitle);
>   |  ^~
> In file included from 
> /<>/libAvKys/Plugins/MultiSrc/src/ffmpeg/src/mediasourceffmpeg.cpp:42:
> /<>/libAvKys/Plugins/MultiSrc/src/ffmpeg/src/subtitlestream.h:43:26:
>  error: ‘AVSubtitle’ has not been declared
>43 | void processData(AVSubtitle *subtitle);
>   |  ^~
> make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu'
> [ 37%] Built target VideoCaptureSrc
> make  -f 
> libAvKys/Plugins/VideoCapture/src/convert/generic/CMakeFiles/VideoCapture_generic.dir/build.make
>  
> libAvKys/Plugins/VideoCapture/src/convert/generic/CMakeFiles/VideoCapture_generic.dir/depend
> make[3]: Entering directory '/<>/obj-x86_64-linux-gnu'
> cd /<>/obj-x86_64-linux-gnu && /usr/bin/cmake -E cmake_depends 
> "Unix Makefiles" /<> 
> /<>/libAvKys/Plugins/VideoCapture/src/convert/generic 
> /<>/obj-x86_64-linux-gnu 
> /<>/obj-x86_64-linux-gnu/libAvKys/Plugins/VideoCapture/src/convert/generic
>  
> /<>/obj-x86_64-linux-gnu/libAvKys/Plugins/VideoCapture/src/convert/generic/CMakeFiles/VideoCapture_generic.dir/DependInfo.cmake
>  --color=
> make[3]: Leaving directory 

Bug#1017317: marked as done (webcamoid: FTBFS: abstractstream.h:60:21: error: ‘AVCodecContext’ does not name a type; did you mean ‘AVIODirContext’?)

[Debian Bug Tracking System]

Your message dated Wed, 14 Sep 2022 12:23:02 +
with message-id 
and subject line Bug#1017179: fixed in webcamoid 9.0.0-5
has caused the Debian Bug report #1017179,
regarding webcamoid: FTBFS: abstractstream.h:60:21: error: ‘AVCodecContext’ 
does not name a type; did you mean ‘AVIODirContext’?
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.)


-- 
1017179: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017179
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: webcamoid
Version: 9.0.0-4
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220813 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> cd 
> /<>/obj-x86_64-linux-gnu/libAvKys/Plugins/VideoCapture/src/convert/ffmpeg
>  && /usr/bin/c++ -DAVKYS_PLUGIN_VIDEOCAPTURE_FFMPEG -DQT_CONCURRENT_LIB 
> -DQT_CORE_LIB -DQT_DEPRECATED_WARNINGS -DQT_GUI_LIB -DQT_NETWORK_LIB 
> -DQT_NO_DEBUG -DQT_QMLMODELS_LIB -DQT_QML_LIB -DQT_QUICK_LIB -DQT_WIDGETS_LIB 
> -DVideoCapture_ffmpeg_EXPORTS 
> -I/<>/obj-x86_64-linux-gnu/libAvKys/Plugins/VideoCapture/src/convert/ffmpeg
>  -I/<>/libAvKys/Plugins/VideoCapture/src/convert/ffmpeg 
> -I/<>/obj-x86_64-linux-gnu/libAvKys/Plugins/VideoCapture/src/convert/ffmpeg/VideoCapture_ffmpeg_autogen/include
>  -I/<>/libAvKys/Plugins/VideoCapture/src/convert/ffmpeg/../.. 
> -I/<>/libAvKys/Plugins/VideoCapture/src/convert/ffmpeg/../../../../../Lib/src
>  -isystem /usr/include/x86_64-linux-gnu/qt5 -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtConcurrent -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtCore -isystem 
> /usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtQuick -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtQmlModels -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtQml -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtNetwork -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtGui -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtWidgets -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -fPIC 
> -std=gnu++11 -MD -MT 
> libAvKys/Plugins/VideoCapture/src/convert/ffmpeg/CMakeFiles/VideoCapture_ffmpeg.dir/src/clock.cpp.o
>  -MF CMakeFiles/VideoCapture_ffmpeg.dir/src/clock.cpp.o.d -o 
> CMakeFiles/VideoCapture_ffmpeg.dir/src/clock.cpp.o -c 
> /<>/libAvKys/Plugins/VideoCapture/src/convert/ffmpeg/src/clock.cpp
> In file included from 
> /<>/libAvKys/Plugins/MultiSrc/src/ffmpeg/src/audiostream.h:23,
>  from 
> /<>/libAvKys/Plugins/MultiSrc/src/ffmpeg/src/mediasourceffmpeg.cpp:40:
> /<>/libAvKys/Plugins/MultiSrc/src/ffmpeg/src/abstractstream.h:60:21:
>  error: ‘AVCodecContext’ does not name a type; did you mean ‘AVIODirContext’?
>60 | Q_INVOKABLE AVCodecContext *codecContext() const;
>   | ^~
>   | AVIODirContext
> /<>/libAvKys/Plugins/MultiSrc/src/ffmpeg/src/abstractstream.h:71:42:
>  error: ‘AVSubtitle’ has not been declared
>71 | Q_INVOKABLE void subtitleEnqueue(AVSubtitle *subtitle);
>   |  ^~
> /<>/libAvKys/Plugins/MultiSrc/src/ffmpeg/src/abstractstream.h:84:34:
>  error: ‘AVSubtitle’ has not been declared
>84 | virtual void processData(AVSubtitle *subtitle);
>   |  ^~
> In file included from 
> /<>/libAvKys/Plugins/MultiSrc/src/ffmpeg/src/mediasourceffmpeg.cpp:42:
> /<>/libAvKys/Plugins/MultiSrc/src/ffmpeg/src/subtitlestream.h:43:26:
>  error: ‘AVSubtitle’ has not been declared
>43 | void processData(AVSubtitle *subtitle);
>   |  ^~
> make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu'
> [ 37%] Built target VideoCaptureSrc
> make  -f 
> libAvKys/Plugins/VideoCapture/src/convert/generic/CMakeFiles/VideoCapture_generic.dir/build.make
>  
> libAvKys/Plugins/VideoCapture/src/convert/generic/CMakeFiles/VideoCapture_generic.dir/depend
> make[3]: Entering directory '/<>/obj-x86_64-linux-gnu'
> cd /<>/obj-x86_64-linux-gnu && /usr/bin/cmake -E cmake_depends 
> "Unix Makefiles" /<> 
> /<>/libAvKys/Plugins/VideoCapture/src/convert/generic 
> /<>/obj-x86_64-linux-gnu 
> /<>/obj-x86_64-linux-gnu/libAvKys/Plugins/VideoCapture/src/convert/generic
>  
> /<>/obj-x86_64-linux-gnu/libAvKys/Plugins/VideoCapture/src/convert/generic/CMakeFiles/VideoCapture_generic.dir/DependInfo.cmake
>  --color=
> make[3]: Leaving directory 

Bug#1019728: dh-nss: Doesn't know about all NSS databases

[Gioele Barabucci]

Control: retitle -1 dh-nss: Known/unknown databases are not documented
Control: severity -1 normal

On Wed, 14 Sep 2022 13:18:36 +0200 Gioele Barabucci  
wrote:
1. libnss-sss.nss lacks a `automount database` directive to explicitly 
introduce a database that is not in base-file's nsswitch.conf. dh-nss 
v1.6 tolerated that, version 1.7 does not.


Small correction: dh-nss version 1.5 did tolerate missing "database" 
directives; version 1.6 is the one that requires them.


--
Gioele Barabucci

Processed: Re: Bug#1019728: dh-nss: Doesn't know about all NSS databases

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 dh-nss: Known/unknown databases are not documented
Bug #1019728 [dh-nss] dh-nss: Doesn't know about all NSS databases
Changed Bug title to 'dh-nss: Known/unknown databases are not documented' from 
'dh-nss: Doesn't know about all NSS databases'.
> severity -1 normal
Bug #1019728 [dh-nss] dh-nss: Known/unknown databases are not documented
Severity set to 'normal' from 'serious'

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

Bug#1019727: marked as done (stress-ng: Depends on binutils-gold where not available)

[Debian Bug Tracking System]

Your message dated Wed, 14 Sep 2022 11:18:52 +
with message-id 
and subject line Bug#1019727: fixed in stress-ng 0.14.05-1
has caused the Debian Bug report #1019727,
regarding stress-ng: Depends on binutils-gold where not available
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.)


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

Source: stress-ng
Version: 0.14.04-1
Severity: serious

Hello, the last version is DEP-waiting on many archs due to binutils-gold not 
being available, e.g.
- binutils-gold:alpha
- binutils-gold:hppa
- binutils-gold:ia64
- binutils-gold:m68k
- binutils-gold:riscv64
- binutils-gold:sh4

Maybe restricting the dependency field to not include them will be beneficial 
for porting archs.
(Also armel FTBFS, this is why I set this bug to RC)

G.
--- End Message ---
--- Begin Message ---
Source: stress-ng
Source-Version: 0.14.05-1
Done: Colin Ian King 

We believe that the bug you reported is fixed in the latest version of
stress-ng, 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 1019...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Colin Ian King  (supplier of updated stress-ng 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: Wed, 14 Sep 2022 11:59:59 +0100
Source: stress-ng
Architecture: source
Version: 0.14.05-1
Distribution: unstable
Urgency: medium
Maintainer: Colin Ian King 
Changed-By: Colin Ian King 
Closes: 1019727
Changes:
 stress-ng (0.14.05-1) unstable; urgency=medium
 .
   * Makefile: bump version
   * Debian/control: remove gold linker from build depends (Closes: #1019727)
Checksums-Sha1:
 2d9dbbaae0570dcd3741b6c9094f27db598477ca 2528 stress-ng_0.14.05-1.dsc
 10d4104d83abd5fb2d27d7e165ac47d757e83843 3138828 stress-ng_0.14.05.orig.tar.xz
 2d35a519af57150a65a921721fcc4811f749ed97 146792 
stress-ng_0.14.05-1.debian.tar.xz
 b9077679580f8b2437af250dc5c8316b488d5212 9843 
stress-ng_0.14.05-1_source.buildinfo
Checksums-Sha256:
 6776813efc76731ef949032bcd9d6e23c87c06abb841cef54aabc13f4a712a10 2528 
stress-ng_0.14.05-1.dsc
 7e7fc9a42e159b00cecf74df2f8e31d2e960b0dc4bb2fb858ead2ec7c5b6a8f5 3138828 
stress-ng_0.14.05.orig.tar.xz
 25cc61d0df3c01ab04321632164aeb477a429168a960fdf271d45a5294c0d68d 146792 
stress-ng_0.14.05-1.debian.tar.xz
 a4be237c5b5136ec1a21ae447d44a77bf08af792b84080f89df4d317dd6a9635 9843 
stress-ng_0.14.05-1_source.buildinfo
Files:
 7cbe1b7fc4928376a4daaf5ca9a2f791 2528 devel optional stress-ng_0.14.05-1.dsc
 56ae8c838c9589dff6fc035a4a2d3975 3138828 devel optional 
stress-ng_0.14.05.orig.tar.xz
 a7bedd7230d7a76f03d7eb8be24f1abc 146792 devel optional 
stress-ng_0.14.05-1.debian.tar.xz
 f5165b2fccf42e2825ebf0e916c942ef 9843 devel optional 
stress-ng_0.14.05-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIyBAEBCAAdFiEEcGLapPABucZhZwDPaMKH38aoAiYFAmMhtcgACgkQaMKH38ao
AibSbA/3egmopcvsk9JlGxy7dNjqxWs+EzaxB9TCsp7pIGXwG1Hs7oVHO3xpxUjF
kzgpLU4TZPFOdTgzAi/DsslE5Gse4x9JeMfbWcW9wzxUpB4nQ36XG1mUYXC/GXLC
b6DkOBf4MGmoQ//dpCQS4+EzPdk/UB5ZM4b6pvsKbvKdmZRGhREgre73WzHbRvhr
fgCZ9tbNzl5WIkYin0OabO4wmeiwSH4Zuwl6Q7z9ejwffu4H0VSr1k4yCF/gY0G5
xtyzvFB4dXDflBvuzV1yaCZqilss6GNsGn9i305OMuN4ldV5vfJ1VDCt8mZtwlZI
KspFln6ndCdILZOFITvRuToNr+IDtF0sAaO1XoY/xXPv+EOixKJ3IInADYE6fH3w
5cVXiNahN6cNFhE1N+oqy1AKoRIqoYW2UaMYjHcmIlgS01ODLpmcJ58mjB+JsAHQ
2rQbG6RKrBL0RDvpttb6yO5d68ednV0q/iQMKUMrNcC/pkFDjo5GRTxcGbBJMpoC
Pj0oX9r6jCKYlXghvHRZ7w0qtNX2M0whtvjPrT1CYgbTatuurslDMtTeWNBdCiiZ
oK6h38GDQKjzxg46ceplBc4SUxBTDOGM/ORqlW3TUBrQPUl4Ik3z66vAEYgNjqEY
rG10tdXle7G3pZy7Hcl7bv0GPlMpM+mXrjiuaPHeYXpZopQyDg==
=lOQR
-END PGP SIGNATURE End Message ---

Bug#1019728: dh-nss: Doesn't know about all NSS databases

[Gioele Barabucci]

On 14/09/22 11:10, Adrian Bunk wrote:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/sssd.html

...
dh_installnss -O--builddirectory=build
dh_installnss: error: Unknown NSS database 'automount' [debian/libnss-sss.nss:6]
make: *** [debian/rules:3: binary] Error 25

[...]

This list looks incomplete, missing from the databases listed
in nsswitch.conf(5) are:
aliases
initgroups
publickey


Control: retitle -1 dh-nss: Known/Unknown databases are not documented
Control: severity -1 normal

The baseline for "known databases" used by dh_installnss is the list of 
NSS databases shipped in nsswitch.conf by base-files.


There are two separate issues here:

1. libnss-sss.nss lacks a `automount database` directive to explicitly 
introduce a database that is not in base-file's nsswitch.conf. dh-nss 
v1.6 tolerated that, version 1.7 does not. A patch for sssd is in the 
works: .


2. The error message and the man page of dh_installnss do not properly 
explain the situation. (Hence, the renaming of this bug.)


Regards,

--
Gioele Barabucci

Bug#1004770: marked as pending in octave-video

[Rafael Laboissière]

Control: tag -1 pending

Hello,

Bug #1004770 in octave-video 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/pkg-octave-team/octave-video/-/commit/3f5d2b913256ec5f82e1952988c9c096d5913e6a


d/p/ffmpeg5.patch: New patch, for fixing FTBFS against ffmpeg 5

Closes: #1004770
Thanks: William Wilson  for the patch


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1004770

Processed: Bug#1004770 marked as pending in octave-video

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1004770 [src:octave-video] octave-video: FTBFS with ffmpeg 5.0
Added tag(s) pending.

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

Bug#1019732: apt-listbugs: undefined method `default' for " # returns password\n":String

[Vincent Lefevre]

Control: severity -1 normal

On 2022-09-14 12:18:58 +0200, Vincent Lefevre wrote:
> It seems that some upgrade broken apt-listbugs. From aptitude:
> 
> Performing actions...
> E: undefined method `default' for "  # returns password\n":String
> E: Sub-process /usr/bin/apt-listbugs apt returned an error code (1)
> E: Failure running script /usr/bin/apt-listbugs apt

Currently, I cannot reproduce this issue. But perhaps it depends on
what the server returns.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Processed: Re: apt-listbugs: undefined method `default' for " # returns password\n":String

[Debian Bug Tracking System]

Processing control commands:

> severity -1 normal
Bug #1019732 [apt-listbugs] apt-listbugs: undefined method `default' for "  
# returns password\n":String
Severity set to 'normal' from 'grave'

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

Processed: nautilus-dropbox: Not compatible with nautilus 43

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #1016985 [src:nautilus-dropbox] nautilus-dropbox: Not compatible with 
nautilus 43
Severity set to 'important' from 'serious'

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

Bug#1016985: nautilus-dropbox: Not compatible with nautilus 43

[Jeremy Bicha]

Control: severity -1 important

There is now a merge proposal upstream to enable nautilus-dropbox to
build with Nautilus 43. The patches aren't compatible with Nautilus
42. So I'll lower the severity of this bug and do an NMU when we push
Nautilus 43 to Unstable. Please let me know if you would prefer to do
a Maintainer upload instead.

https://github.com/dropbox/nautilus-dropbox/pull/105

Thank you,
Jeremy Bicha

Bug#1019732: apt-listbugs: undefined method `default' for " # returns password\n":String

[Vincent Lefevre]

Package: apt-listbugs
Version: 0.1.36
Severity: grave
Justification: renders package unusable

It seems that some upgrade broken apt-listbugs. From aptitude:

Performing actions...
E: undefined method `default' for "  # returns password\n":String
E: Sub-process /usr/bin/apt-listbugs apt returned an error code (1)
E: Failure running script /usr/bin/apt-listbugs apt

-- System Information:
Debian Release: bookworm/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500, 
'stable-security'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 
'experimental')
merged-usr: no
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.19.0-1-amd64 (SMP w/12 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=POSIX, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages apt-listbugs depends on:
ii  apt 2.5.2
ii  ruby1:3.0+1
ii  ruby-debian 0.3.10+b6
ii  ruby-gettext3.3.3-2
ii  ruby-soap4r 2.0.5-5
ii  ruby-unicode0.4.4.4-1+b3
ii  ruby-xmlparser  0.7.3-4+b2

Versions of packages apt-listbugs recommends:
ii  ruby-httpclient  2.8.3+git20211122.4658227-1

Versions of packages apt-listbugs suggests:
ii  elinks [www-browser]   0.13.2-1+b3
ii  firefox [www-browser]  104.0.2-1
hi  firefox-esr [www-browser]  52.9.0esr-1~deb9u1
ii  links [www-browser]2.27-1+b1
ii  links2 [www-browser]   2.27-1+b1
ii  lynx [www-browser] 2.9.0dev.10-1
ii  reportbug  11.5.1
ii  sensible-utils 0.0.17
ii  w3m [www-browser]  0.5.3+git20220429-1+b1
ii  xdg-utils  1.1.3-4.1

-- Configuration Files:
/etc/apt/apt.conf.d/10apt-listbugs changed:
// Before installing packages, check whether they have release-critical
// or security bugs.
DPkg::Pre-Install-Pkgs
{
  "/usr/bin/apt-listbugs apt";
  "/usr/bin/apt-listbugs apt -T security -s all";
};
DPkg::Tools::Options::/usr/bin/apt-listbugs "";
DPkg::Tools::Options::/usr/bin/apt-listbugs::Version "3";
DPkg::Tools::Options::/usr/bin/apt-listbugs::InfoFD "20";
AptListbugs::Severities "critical,grave,serious";
AptListbugs::IgnoreRegexp "FTBFS";


-- no debconf information

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#1019721: libopenmpi-dev: Cannot uninstall rmdir: failed to remove '/usr/lib/x86_64-linux-gnu/fortran/gfortran': No such file or directory

[Paul Wise]

On Wed, 2022-09-14 at 07:41 +0200, Andreas Metzler wrote:

> Is there a way to find all packages built against broken dh-fortran-
> mod so all affected packages can be rebuilt?

I am not sure of the correct regex, but the binary package control
search should work, if it doesn't then you need a local mirror:

https://binarycontrol.debian.net/?q=%2Fusr%2Flib%2F%5C%24multiarch%2Ffortran%2Fgfortran=

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#1017618: nautilus-share: Incompatible with Nautilus 43

[Adrian Bunk]

On Thu, Aug 18, 2022 at 10:39:04AM -0400, Jeremy Bicha wrote:
>...
> nautilus-share fails to build from source with Nautilus 43.

The original project is archived, but this bug seems fixed in the 
maintained fork at
  https://gitlab.gnome.org/coreyberla/nautilus-share

> Thank you,
> Jeremy Bicha

cu
Adrian

Bug#1017051: tinyarray: FTBFS on i386

[Adrian Bunk]

On Tue, Aug 30, 2022 at 11:56:26AM +0200, Emanuele Rocca wrote:
> On 12/08 02:36, Graham Inggs wrote:
> > Source: tinyarray
> > Version: 1.2.3-4
> > Severity: serious
> > Tags: ftbfs
> > User: debian-pyt...@lists.debian.org
> > Usertags: python3.10
> > 
> > Hi Maintainer
> > 
> > Your package FTBFS on i386 during the recent rebuilds for Python 3.10
> 
> I've enabled CI/CD on Salsa and the issue is reproduced by the i386 job.
> 
> See https://salsa.debian.org/python-team/packages/tinyarray/-/pipelines/417235

Also looking at #976514, I wonder whether
  Architecture: amd64
might be the best available solution.

cu
Adrian

Processed: dh-nss: Doesn't know about all NSS databases

[Debian Bug Tracking System]

Processing control commands:

> affects -1 src:sssd
Bug #1019728 [dh-nss] dh-nss: Doesn't know about all NSS databases
Added indication that 1019728 affects src:sssd
> block 1016220 by -1
Bug #1016220 {Done: Timo Aaltonen } [src:sssd] sssd: 
FTBFS: dh_install: error: missing files, aborting
1016220 was not blocked by any bugs.
1016220 was not blocking any bugs.
Added blocking bug(s) of 1016220: 1019728

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

Bug#1019728: dh-nss: Doesn't know about all NSS databases

[Adrian Bunk]

Package: dh-nss
Version: 1.6
Severity: serious
Tags: ftbfs
Control: affects -1 src:sssd
Control: block 1016220 by -1

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/sssd.html

...
   dh_installnss -O--builddirectory=build
dh_installnss: error: Unknown NSS database 'automount' [debian/libnss-sss.nss:6]
make: *** [debian/rules:3: binary] Error 25


This is due to the following change in dh-nss:
   * dh_installnss: Validate fields of .nss files


This list looks incomplete, missing from the databases listed
in nsswitch.conf(5) are:
aliases
initgroups
publickey


automount is documented as an example for an additional database
in libc.info:
   Lastly, some system software may make use of the NSS configuration
   file to store their own configuration for similar purposes.  Examples of
   this include the ‘automount’ service which is used by ‘autofs’.

Bug#1016508: marked as done (rapiddisk,rapiddisk-dkms: both ship /usr/src/rapiddisk-8.2.0-2/*)

[Debian Bug Tracking System]

Your message dated Wed, 14 Sep 2022 08:50:42 +
with message-id 
and subject line Bug#1016508: fixed in rapiddisk 8.2.0-4
has caused the Debian Bug report #1016508,
regarding rapiddisk,rapiddisk-dkms: both ship /usr/src/rapiddisk-8.2.0-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.)


-- 
1016508: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016508
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: rapiddisk,rapiddisk-dkms
Version: 8.2.0-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

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...):

  Selecting previously unselected package rapiddisk-dkms.
  Preparing to unpack .../rapiddisk-dkms_8.2.0-2_all.deb ...
  Unpacking rapiddisk-dkms (8.2.0-2) ...
  dpkg: error processing archive 
/var/cache/apt/archives/rapiddisk-dkms_8.2.0-2_all.deb (--unpack):
   trying to overwrite '/usr/src/rapiddisk-8.2.0-2/Makefile', which is also in 
package rapiddisk 8.2.0-2
  Errors were encountered while processing:
   /var/cache/apt/archives/rapiddisk-dkms_8.2.0-2_all.deb

BTW, you should only use the upstream version without Debian revision
for the path in /usr/src, i.e. /usr/src/rapiddisk-8.2.0/

cheers,

Andreas


rapiddisk=8.2.0-2_rapiddisk-dkms=8.2.0-2.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: rapiddisk
Source-Version: 8.2.0-4
Done: Gürkan Myczko 

We believe that the bug you reported is fixed in the latest version of
rapiddisk, 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 1016...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Gürkan Myczko  (supplier of updated rapiddisk 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: Wed, 14 Sep 2022 09:57:07 +0200
Source: rapiddisk
Architecture: source
Version: 8.2.0-4
Distribution: unstable
Urgency: medium
Maintainer: Gürkan Myczko 
Changed-By: Gürkan Myczko 
Closes: 1016508
Changes:
 rapiddisk (8.2.0-4) unstable; urgency=medium
 .
   * Really stop double shipping of conflicting files. (Closes: #1016508)
   * Apply patch from Andreas Righi to build on 5.19.x kernels. Thanks.
Checksums-Sha1:
 d48f2f723a05385f82eed9955b528c9de213fcf8 1952 rapiddisk_8.2.0-4.dsc
 62abec8c7c252b4c7e71c936691e393919b27fd3 3840 rapiddisk_8.2.0-4.debian.tar.xz
 e9950303a750abaf81fc1b431c2bb31c2ddb5c00 8547 
rapiddisk_8.2.0-4_source.buildinfo
Checksums-Sha256:
 9015a295a423f2cd18becc583d7bfa660ccec5e76bfe82ff0bbe7d57b8404bfe 1952 
rapiddisk_8.2.0-4.dsc
 0ff90558b15bd3b6d6395473aa115ab7a7ffcb32210b9c183b7efccb06156d1b 3840 
rapiddisk_8.2.0-4.debian.tar.xz
 e4f8356f76aa4bc8b684aca89bac25a2b79968c3d52ac02e9d96da1fdd3888c5 8547 
rapiddisk_8.2.0-4_source.buildinfo
Files:
 d3e6cff532768363687f286f39ed4155 1952 kernel optional rapiddisk_8.2.0-4.dsc
 680504ca0ff7900f3064069042c51061 3840 kernel optional 
rapiddisk_8.2.0-4.debian.tar.xz
 658184496dc77ff7ddea5353fc90c42d 8547 kernel optional 
rapiddisk_8.2.0-4_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEtgob82PcExn/Co6JEWhSvN91FcAFAmMhkygACgkQEWhSvN91
FcD0WA/5AdclmGv53wL6L9y6WLezkwab9F57wJ4KMvLLx/VM3sDWlkVrTx/WDqhm
czfEda5XTqeoJaFnS6baGciOsJMlDMyVj0NutCwdV+U+lV91Q8Zd40dnMZVPFczx
9NOnVcXtvjA5yZOc6dfTHBlflp7hcmiRaTouVEZ2kVUu44GNU82pdnZqC1RUgdr8
PQ2BJOqluhH+YjKE1EypJYJRer4rBwaS40e+2IjuZBW1UBUUwPTsekAIS8EA5Lr4
IbXrpmM+eoE+mZWJZuV9uKLui4iRe0/7/BbCrTw+HId3Cn5x1Og/YyBNd+/DiMZp
+b/BaFdaCd3sZ2dRGgHkQ7DzRIK3U8SBCmZQ6Lfh/S3m3RQyvRhqa4xwGF24aR34
BlBcjRkZqiP5dbBs8h7NkX4341Ep5irPaKoGbMQMmT/+lH7xNJvFJEyNR3SYvkgz
Ka9fwBQIkzPtiK86BbE3krNfBuIP8oxlEUe06xQpYsv13J2lm6UOW1UoKaJZXpgW
IDcWRdQGlE/yroYekNLwMSzBLsD1YbU8OZe5uc+RWqQF4NyUzkTtzSgyT3XR+RGM
iqba94BDyBjThKdwVw+felH/7CfCOV9eBMYo55FGIENVy+71WcOBynM+cvALRGsD
d1O82nxF/KxocTvzOJlMJTtUo24L0VwZ7wxHIz0nZDigPnICUoM=
=wSlV
-END PGP SIGNATURE End Message ---

Bug#1019724: warning: stray \ before - causes autopkgtest failure

[Santiago Ruano Rincón]

Hi,

El 14/09/22 a las 09:04, Jochen Sprickerhof escribió:
> Package: grep
> Version: 3.8-2
> Severity: serious
> 
> Hi,
> 
> the new grep versions issues a warning on stderr:
> 
> stderr: /usr/bin/grep: warning: stray \ before -

FTR, this warning relates to:

  Regular expressions with stray backslashes now cause warnings, as
  their unspecified behavior can lead to unexpected results.
  For example, '\a' and 'a' are not always equivalent
  .  Similarly, regular expressions or
  subexpressions that start with a repetition operator now also cause
  warnings due to their unspecified behavior; for example, *a(+b|{1}c)
  now has three reasons to warn.  The warnings are intended as a
  transition aid; they are likely to be errors in future releases.

> 
> this causes build failures:
> 
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/arm64/libtool.html
> 
> and also autopkgtest failures:
> 
> https://ci.debian.net/data/autopkgtest/unstable/amd64/d/dpkg/26032114/log.gz
> https://ci.debian.net/data/autopkgtest/unstable/amd64/c/cjet/26041201/log.gz
> 
> The first autopkgtest failure is in libtool which is vendored by a lot
> of packages so will probably take a long time to fix.
> 

Fixing this would require fixing libtool only, isn't that right?

> Could you maybe silence the warning for now?
> 

Let's see how difficult is to fix this in libtool (and in any other
potentially affected package) first.

Let me also add some rationale from upstream, quoting it from
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=57604#47:

El 08/09/22 a las 02:21, Jim Meyering escribió:
> Hi Karl,
> 
> Sorry to cause you grief, but...
> 
> On Wed, Sep 7, 2022 at 7:49 PM Karl Berry  wrote:
[snip]
> > $ grep '\Q' /dev/null
> > grep: warning: stray \ before Q
> 
> > It would be nice to be able to turn those off too. (It hit me today.)
> 
> I would argue that it is (...) important to retain these
> stray-backslash warnings, because they tend to highlight real bugs.
> Consider these uses of \d:
> 
>   $ echo d | grep-3.7 '\d'
>   d
>   $ echo d | grep-3.8 '\d'
>   grep: warning: stray \ before d
> 
> Anyone used to PCRE regexps (who isn't, these days) knows that its
> "\d" is intended to match a digit, not the letter "d". With grep-3.7,
> you'd get misbehavior and no warning about your error. With grep-3.8,
> you'll get the diagnostic and maybe switch to using "grep -P", where
> "\d" works as expected -- switching from \d to [0-9] hurts readability
> and feels like dumbing-down, especially when there are two or more \d
> uses. Using PCRE's \Q...\E groups *without -P* is another issue that
> is now diagnosed.
>
...


> Should be this one:
> 
> https://sources.debian.org/src/grep/3.8-2/lib/dfa.c/#L1564
> 
> Cheers Jochen
> 
> P.S.: I will send a bug with a patch to the libtool maintainer.

Please do.

Cheers,

 -- Santiago

P.S. I am letting Severity: serious for now to prevent migration to
testing. But *I* am considering this rather Severity: important, at
most.


signature.asc
Description: PGP signature

Bug#1019727: stress-ng: Depends on binutils-gold where not available

[Gianfranco Costamagna]

Source: stress-ng
Version: 0.14.04-1
Severity: serious

Hello, the last version is DEP-waiting on many archs due to binutils-gold not 
being available, e.g.
- binutils-gold:alpha
- binutils-gold:hppa
- binutils-gold:ia64
- binutils-gold:m68k
- binutils-gold:riscv64
- binutils-gold:sh4

Maybe restricting the dependency field to not include them will be beneficial 
for porting archs.
(Also armel FTBFS, this is why I set this bug to RC)

G.

Processed: Waiting for upstream fix

[Debian Bug Tracking System]

Processing control commands:

> tags -1 -patch
Bug #1019708 [src:astropy] astropy: autopkgtest regression: No warnings of type 
(,) were emitted
Removed tag(s) patch.

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

Bug#1019708: Waiting for upstream fix

[Ole Streicher]

Control: tags -1 -patch

Upstream will fix this probably soon by merging 
https://github.com/astropy/astropy/pull/13614 into their development 
branch and backporting it to the 5.1 version. Probably then they will 
issue a bugfix version, as the PR covers all fixes for the upcoming 
Python 3.11.


I will wait for this bugfix version, as Python 3.11  will also soon 
knock on the Debian's door, and we need this anyway.

Processed: [t...@debian.org: nmu: openmpi_4.1.0-10]

[Debian Bug Tracking System]

Processing control commands:

> block -1 by 1019722
Bug #1019721 [libopenmpi-dev] libopenmpi-dev: Cannot uninstall rmdir: failed to 
remove '/usr/lib/x86_64-linux-gnu/fortran/gfortran': No such file or directory
1019721 was not blocked by any bugs.
1019721 was not blocking any bugs.
Added blocking bug(s) of 1019721: 1019722
> tags -1 pending
Bug #1019721 [libopenmpi-dev] libopenmpi-dev: Cannot uninstall rmdir: failed to 
remove '/usr/lib/x86_64-linux-gnu/fortran/gfortran': No such file or directory
Added tag(s) pending.

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

Bug#1019721: [t...@debian.org: nmu: openmpi_4.1.0-10]

[Tobias Frost]

Control: block -1 by 1019722
Control: tags -1 pending

I've requested an binNMU for this package.

- Forwarded message from Tobias Frost  -

Date: Wed, 14 Sep 2022 08:50:41 +0200
From: Tobias Frost 
To: Debian Bug Tracking System 
Subject: nmu: openmpi_4.1.0-10
X-Mailer: reportbug 11.5.1

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu
X-Debbugs-Cc: 1019...@bugs.debian.org

nmu openmpi_4.1.0-10 . ANY . unstable . -m "Rebuild with fixed dh-fotran-mod 
(See #1019050)""

As reported in #1019721, openmpi is affected by #1019050, so a rebuild should 
fix that.

-- 
tobi

- End forwarded message -

Processed: Forwarded solution for astropy

[Debian Bug Tracking System]

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

> forwarded 1019708 https://github.com/astropy/astropy/pull/13662
Bug #1019708 [src:astropy] astropy: autopkgtest regression: No warnings of type 
(,) were emitted
Set Bug forwarded-to-address to 'https://github.com/astropy/astropy/pull/13662'.
> tags 1019708 +patch
Bug #1019708 [src:astropy] astropy: autopkgtest regression: No warnings of type 
(,) were emitted
Added tag(s) patch.
> thanks
Stopping processing here.

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

Bug#1019724: warning: stray \ before - causes autopkgtest failure

[Jochen Sprickerhof]

Package: grep
Version: 3.8-2
Severity: serious

Hi,

the new grep versions issues a warning on stderr:

stderr: /usr/bin/grep: warning: stray \ before -

this causes build failures:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/arm64/libtool.html

and also autopkgtest failures:

https://ci.debian.net/data/autopkgtest/unstable/amd64/d/dpkg/26032114/log.gz
https://ci.debian.net/data/autopkgtest/unstable/amd64/c/cjet/26041201/log.gz

The first autopkgtest failure is in libtool which is vendored by a lot
of packages so will probably take a long time to fix.

Could you maybe silence the warning for now?

Should be this one:

https://sources.debian.org/src/grep/3.8-2/lib/dfa.c/#L1564

Cheers Jochen

P.S.: I will send a bug with a patch to the libtool maintainer.

-- System Information:
Debian Release: bookworm/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
merged-usr: no
Architecture: amd64 (x86_64)

Kernel: Linux 5.19.0-1-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages grep depends on:
ii  dpkg  1.21.9
ii  install-info  6.8-6
ii  libc6 2.34-8
ii  libpcre2-8-0  10.40-1

grep recommends no packages.

grep suggests no packages.

-- no debconf information

Bug#1016263: marked as done (xenium: FTBFS: atomic_base.h:133:26: error: ‘atomic_thread_fence’ is not supported with ‘-fsanitize=thread’ [-Werror=tsan])

[Debian Bug Tracking System]

Your message dated Wed, 14 Sep 2022 06:49:33 +
with message-id 
and subject line Bug#1016263: fixed in xenium 0.0.2+ds-7
has caused the Debian Bug report #1016263,
regarding xenium: FTBFS: atomic_base.h:133:26: error: ‘atomic_thread_fence’ is 
not supported with ‘-fsanitize=thread’ [-Werror=tsan]
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.)


-- 
1016263: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016263
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: xenium
Version: 0.0.2+ds-6
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220728 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> /usr/bin/c++ -DDEBUG -I/<>/. -isystem 
> /usr/src/googletest/googletest -isystem 
> /usr/src/googletest/googletest/include -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fsanitize=thread 
> -Wall -Wextra -Werror -Wno-error=cpp -std=gnu++17 -MD -MT 
> CMakeFiles/gtest.dir/test/reclamation/generic_epoch_based_test.cpp.o -MF 
> CMakeFiles/gtest.dir/test/reclamation/generic_epoch_based_test.cpp.o.d -o 
> CMakeFiles/gtest.dir/test/reclamation/generic_epoch_based_test.cpp.o -c 
> /<>/test/reclamation/generic_epoch_based_test.cpp
> In file included from /usr/include/c++/12/atomic:41,
>  from 
> /<>/./xenium/reclamation/detail/concurrent_ptr.hpp:11,
>  from 
> /<>/./xenium/reclamation/lock_free_ref_count.hpp:9,
>  from 
> /<>/test/harris_michael_list_based_set_test.cpp:1:
> In function ‘void std::atomic_thread_fence(memory_order)’,
> inlined from ‘bool 
> xenium::reclamation::quiescent_state_based::thread_data::try_update_epoch(unsigned
>  int, unsigned int)’ at 
> /<>/./xenium/reclamation/impl/quiescent_state_based.hpp:129:33:
> /usr/include/c++/12/bits/atomic_base.h:133:26: error: ‘atomic_thread_fence’ 
> is not supported with ‘-fsanitize=thread’ [-Werror=tsan]
>   133 |   { __atomic_thread_fence(int(__m)); }
>   | ~^~
> In file included from /usr/include/c++/12/atomic:41,
>  from 
> /<>/./xenium/reclamation/detail/concurrent_ptr.hpp:11,
>  from 
> /<>/./xenium/reclamation/hazard_pointer.hpp:9,
>  from /<>/test/kirsch_kfifo_queue_test.cpp:1:
> In function ‘void std::atomic_thread_fence(memory_order)’,
> inlined from ‘bool 
> xenium::reclamation::quiescent_state_based::thread_data::try_update_epoch(unsigned
>  int, unsigned int)’ at 
> /<>/./xenium/reclamation/impl/quiescent_state_based.hpp:129:33:
> /usr/include/c++/12/bits/atomic_base.h:133:26: error: ‘atomic_thread_fence’ 
> is not supported with ‘-fsanitize=thread’ [-Werror=tsan]
>   133 |   { __atomic_thread_fence(int(__m)); }
>   | ~^~
> In member function ‘bool std::atomic<_Tp>::compare_exchange_weak(_Tp&, _Tp, 
> std::memory_order, std::memory_order) [with _Tp = 
> xenium::marked_ptr]’,
> inlined from ‘bool 
> xenium::reclamation::stamp_it::thread_order_queue::mark_next(marked_ptr, 
> size_t)’ at /<>/./xenium/reclamation/impl/stamp_it.hpp:563:46,
> inlined from ‘bool 
> xenium::reclamation::stamp_it::thread_order_queue::remove_from_prev_list(marked_ptr&,
>  marked_ptr, marked_ptr&)’ at 
> /<>/./xenium/reclamation/impl/stamp_it.hpp:307:25,
> inlined from ‘bool 
> xenium::reclamation::stamp_it::thread_order_queue::remove(marked_ptr)’ at 
> /<>/./xenium/reclamation/impl/stamp_it.hpp:155:49,
> inlined from ‘void 
> xenium::reclamation::stamp_it::thread_data::leave_region()’ at 
> /<>/./xenium/reclamation/impl/stamp_it.hpp:620:36:
> /usr/include/c++/12/atomic:325:41: error: failure memory model 
> ‘memory_order_acquire’ cannot be stronger than success memory model 
> ‘memory_order_relaxed’ for ‘bool __atomic_compare_exchange_8(volatile void*, 
> void*, long unsigned int, bool, int, int)’ [-Werror=invalid-memory-model]
>   325 | return __atomic_compare_exchange(std::__addressof(_M_i),
>   |~^~~~
>   326 |  std::__addressof(__e),
>   |  ~~
>   327 |  std::__addressof(__i),
>   |  ~~
>   328 |  true, int(__s), int(__f));
>   | 

Bug#1019721: libopenmpi-dev: Cannot uninstall rmdir: failed to remove '/usr/lib/x86_64-linux-gnu/fortran/gfortran': No such file or directory

[Andreas Metzler]

Package: libopenmpi-dev
Version: 4.1.4-2
Severity: serious

Hello,

it seems to be impossible to uninstall libopenmpi-dev:
(sid)root@argenau:/# dpkg --purge libopenmpi-dev
(Reading database ... 25167 files and directories currently installed.)
Removing libopenmpi-dev:amd64 (4.1.4-2) ...
rmdir: failed to remove '/usr/lib/x86_64-linux-gnu/fortran/gfortran': No such 
file or directory
dpkg: error processing package libopenmpi-dev:amd64 (--purge):
[...]

Looking at the postrm script we find:
(sid)root@argenau:/# grep ^rmdir 
/var/lib/dpkg/info/libopenmpi-dev\:amd64.postrm 
rmdir --ignore-fail-on-non-empty /usr/lib/$multiarch/fortran/gfortran
rmdir --ignore-fail-on-non-empty /usr/lib/$multiarch/fortran/gfortran
rmdir --ignore-fail-on-non-empty /usr/lib/$multiarch/fortran/gfortran
rmdir --ignore-fail-on-non-empty /usr/lib/$multiarch/fortran/gfortran
rmdir --ignore-fail-on-non-empty /usr/lib/$multiarch/fortran/gfortran

i.e. rmdir is run unconditiionally multiple times on the same directory,
the first instance succeeds, the second one fails.

This is #1019050 in dh-fortran-mod which is now fixed. However
libopenmpi-dev 4.1.4-2 contains the broken code generated by
dh-fortran-mod and needs a rebuild against dh-fortran-mod (0.27) and
should not propagate to testing.

Is there a way to find all packages built against broken dh-fortran-mod
so all affected packages can be rebuilt?

cu Andreas