Bug#1069330: ITP: golang-github-akihirosuda-apt-transport-oci -- OCI transport plugin for apt-get (i.e., apt-get over ghcr.io)

2024-04-20 Thread Jianfeng Liu
I have pushed code to
https://salsa.debian.org/amazingfate/golang-github-cloudflare-apt-transport-cloudflared.
And I also send access request to repo
https://salsa.debian.org/go-team/packages/golang-github-akihirosuda-apt-transport-oci.
Looking forward to see oci support added to debian.

Best regards,
Jianfeng


Bug#1069333: Not installable due to hardcoded pre-t64 library deps

2024-04-20 Thread Andrey Rakhmatullin
Package: ippsample
Version: 0.0~git20220607.72f89b3-1+b4
Severity: grave

ippsample explicitly Depends: libcups2. It should be changed to the t64 name if
it's really needed.


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

Kernel: Linux 6.7.9-amd64 (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.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 ippsample depends on:
pn  ippsample-data  
ii  libavahi-client30.8-13+b2
ii  libavahi-common30.8-13+b2
ii  libc6   2.37-18
ii  libcups2t64 [libcups2]  2.4.7-1.2+b1

ippsample recommends no packages.

ippsample suggests no packages.



Bug#1056574: transition: ppp

2024-04-20 Thread Sebastian Ramacher
Control: tags -1 confirmed

On 2024-04-19 17:11:44 +0100, Chris Boot wrote:
> On 26/11/2023 11:36, Chris Boot wrote:
> > On 26/11/2023 10:56, Chris Boot wrote:
> > > > Any way to reduce possible breakage, or to detect and fix it
> > > > before the transition starts? Like rebuilding rdeps, or checking
> > > > rdep autopkgtests?
> > > 
> > > I'll go an do some rebuilds now and see how they go. If any breakage
> > > occurs it will be obvious at build time.
> > 
> > The status of the rdeps (list taken from the tracker):
> > 
> > connman: OK
> > network-manager: OK
> > pptpd: https://bugs.debian.org/1056898
> > sstp-client: https://bugs.debian.org/1056900
> > 
> > network-manager-fortisslvpn: https://bugs.debian.org/1056901
> > network-manager-l2tp: OK
> > network-manager-pptp: OK
> > network-manager-sstp: https://bugs.debian.org/1056903
> 
> All that's left now is pptpd (with an offer from Christoph to upload when
> ready) and network-manager-fortisslvpn (with commits fixing the issues
> upstream, but no upstream release).
> 
> In the mean time, #1065940 has become a blocker for the time_t transition. I
> think I'd rather upload 2.5.0 and break network-manager-fortisslvpn than
> just the patch to fix the breakage.
> 
> Would the release team be happy to continue with this transition?

Please go ahead with the upload to unsable.

Cheers
-- 
Sebastian Ramacher



Bug#1066378: pike8.0: FTBFS: zlibmod.c:1235:5: error: implicit declaration of function ‘pop_n_elems’ [-Werror=implicit-function-declaration]

2024-04-20 Thread Bastian Germann

I am uploading a NMU to fix this.
The debdiff is attached.diff -Nru pike8.0-8.0.1738/debian/README.Debian 
pike8.0-8.0.1738/debian/README.Debian
--- pike8.0-8.0.1738/debian/README.Debian   2015-09-20 16:40:03.0 
+
+++ pike8.0-8.0.1738/debian/README.Debian   2024-04-20 08:24:08.0 
+
@@ -13,6 +13,7 @@
dependencies.
  - Mird: Old, unmaintained, largely unknown library.
  - Msql: Obsolete, proprietary DBM.
+ - PCRE: Depends on outdated library.
  - PDF: Uses unmaintained libraries unavailable in Debian.
  - Ssleay: Obsolete.
  - Oracle: Proprietary DBM (so far ...).
diff -Nru pike8.0-8.0.1738/debian/changelog pike8.0-8.0.1738/debian/changelog
--- pike8.0-8.0.1738/debian/changelog   2024-03-10 11:50:21.0 +
+++ pike8.0-8.0.1738/debian/changelog   2024-04-20 08:24:08.0 +
@@ -1,3 +1,12 @@
+pike8.0 (8.0.1738-1.4) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * d/copyright: Replace MPL text with link to common-licenses.
+  * Fix implicit declarations (Closes: #1066378).
+  * Add note on dropped PCRE module.
+
+ -- Bastian Germann   Sat, 20 Apr 2024 08:24:08 +
+
 pike8.0 (8.0.1738-1.3) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru pike8.0-8.0.1738/debian/copyright pike8.0-8.0.1738/debian/copyright
--- pike8.0-8.0.1738/debian/copyright   2015-09-20 18:06:03.0 +
+++ pike8.0-8.0.1738/debian/copyright   2024-04-20 08:23:34.0 +
@@ -59,474 +59,5 @@
 On Debian GNU/Linux systems, the complete text of the GNU Lesser General
 Public License can be found in `/usr/share/common-licenses/LGPL-2.1'.
 
-The full text of the Mozilla Public License 1.1 follows.
-
-  MOZILLA PUBLIC LICENSE
-Version 1.1
-
-  ---
-
-1. Definitions.
-
- 1.0.1. "Commercial Use" means distribution or otherwise making the
- Covered Code available to a third party.
-
- 1.1. "Contributor" means each entity that creates or contributes to
- the creation of Modifications.
-
- 1.2. "Contributor Version" means the combination of the Original
- Code, prior Modifications used by a Contributor, and the Modifications
- made by that particular Contributor.
-
- 1.3. "Covered Code" means the Original Code or Modifications or the
- combination of the Original Code and Modifications, in each case
- including portions thereof.
-
- 1.4. "Electronic Distribution Mechanism" means a mechanism generally
- accepted in the software development community for the electronic
- transfer of data.
-
- 1.5. "Executable" means Covered Code in any form other than Source
- Code.
-
- 1.6. "Initial Developer" means the individual or entity identified
- as the Initial Developer in the Source Code notice required by Exhibit
- A.
-
- 1.7. "Larger Work" means a work which combines Covered Code or
- portions thereof with code not governed by the terms of this License.
-
- 1.8. "License" means this document.
-
- 1.8.1. "Licensable" means having the right to grant, to the maximum
- extent possible, whether at the time of the initial grant or
- subsequently acquired, any and all of the rights conveyed herein.
-
- 1.9. "Modifications" means any addition to or deletion from the
- substance or structure of either the Original Code or any previous
- Modifications. When Covered Code is released as a series of files, a
- Modification is:
-  A. Any addition to or deletion from the contents of a file
-  containing Original Code or previous Modifications.
-
-  B. Any new file that contains any part of the Original Code or
-  previous Modifications.
-
- 1.10. "Original Code" means Source Code of computer software code
- which is described in the Source Code notice required by Exhibit A as
- Original Code, and which, at the time of its release under this
- License is not already Covered Code governed by this License.
-
- 1.10.1. "Patent Claims" means any patent claim(s), now owned or
- hereafter acquired, including without limitation,  method, process,
- and apparatus claims, in any patent Licensable by grantor.
-
- 1.11. "Source Code" means the preferred form of the Covered Code for
- making modifications to it, including all modules it contains, plus
- any associated interface definition files, scripts used to control
- compilation and installation of an Executable, or source code
- differential comparisons against either the Original Code or another
- well known, available Covered Code of the Contributor's choice. The
- Source Code can be in a compressed or archival form, provided the
- appropriate decompression or de-archiving software is widely available
- for no charge.
-
- 1.12. "You" (or "Your")  means an individual or a legal entity
- exercising rights under, and complying with 

Bug#1069343: ITP: uart-devices -- Python library for managing UART devices on Linux

2024-04-20 Thread Edward Betts
Package: wnpp
Severity: wishlist
Owner: Edward Betts 
X-Debbugs-Cc: debian-de...@lists.debian.org, debian-pyt...@lists.debian.org

* Package name: uart-devices
  Version : 0.1.0
  Upstream Author : J. Nick Koston 
* URL : https://github.com/bdraco/uart-devices
* License : MIT
  Programming Lang: Python
  Description : Python library for managing UART devices on Linux

  uart-devices is a Python library designed to facilitate interaction with UART
  (Universal Asynchronous Receiver/Transmitter) devices on Linux systems. This
  library provides developers with tools to manipulate UART hardware
  programmatically, making it easier to integrate UART operations within Python
  applications.

I plan to maintain this package as part of the Python team.



Bug#1000118: generator-scripting-language: depends on obsolete pcre3 library

2024-04-20 Thread Bastian Germann

Control: forwarded -1 https://github.com/zeromq/gsl/pull/52

I have created an upstream Pull Request for Yavor's work.
Please consider merging it.



Bug#1069344: netgen: FTBFS on armhf [debian/rules:66: override_dh_auto_test]

2024-04-20 Thread Kentaro HAYASHI
Source: netgen
Severity: serious
Tags: ftbfs
Control: found -1 6.2.2401+dfsg1-1.1+b1
X-Debbugs-Cc: ken...@xdump.org

Dear Maintainer,

netgen fails to build on armhf.

FYI:

https://buildd.debian.org/status/fetch.php?pkg=netgen=armhf=6.2.2401%2Bdfsg1-1.1%2Bb1=1712667539=0

Regards,



Bug#785237: lightdm-gtk-greeter: Please remove leading spaces from user name

2024-04-20 Thread Håvard F . Aasen
Control: tags -1 + fixed-upstream


This issue has been addressed by upstream in [1], and is included in
version 2.0.9.

It would be nice if that version could be packaged.

-- 
Håvard

[1] https://github.com/Xubuntu/lightdm-gtk-greeter/pull/80



Bug#1033462: kmail: Kmail fails to send emails via Google mail with "Failed to authenticate additional scopes"

2024-04-20 Thread Sedat Dilek
OAuth 2.0 Scopes for Google APIs:

https://developers.google.com/identity/protocols/oauth2/scopes



Bug#751007: Say hello to Airtel Xstream AirFiber Superfast home internet service.For booking call -9938049742.

2024-04-20 Thread Kapil Senapati
Dear Sir,

Say hello to Airtel Xstream AirFiber Superfast home internet service .

Introducing Airtel Xstream AirFiber, India's first wireless home internet, 
powered by 5G Plus.Discover the power of wireless connectivity and superfast 
speeds with Airtel Xstream AirFiber. With built in Wi-Fi 6, this latest home 
internet device will enable customers to experience fiber like download speeds 
and connect multiple personal devices simultaneously, providing a seamless 
internet experience. Customers can now work from home or binge watch their 
favourite shows, fuss free.

[cid:image001.jpg@01DA9322.46F874B0]
We eagerly awaiting for your confirmatory response on the aforesaid proposal.
Assuring you of our best possible services at all times.

For more details & booking please call- 9938049742.


Regards

Kapil Senapati
Mob-9938049742
[cid:image001.png@01D75169.6FB137A0]

***
This email and any files transmitted with it are confidential and intended 
solely for the use of the individual or entity to whom they are addressed. If 
you have received this email in error please notify the system manager. This 
message contains confidential information and is intended only for the 
individual named. If you are not the named addressee you should not 
disseminate, distribute or copy this e-mail. Please notify the sender 
immediately by e-mail if you have received this e-mail by mistake and delete 
this e-mail from your system. If you are not the intended recipient you are 
notified that disclosing, copying, distributing or taking any action in 
reliance on the contents of this information is strictly prohibited . The 
information contained in this mail is propriety and strictly confidential.
***


Bug#1069338: Not installable due to a bad dh_makeshlibs override

2024-04-20 Thread Andrey Rakhmatullin
Package: libui-gxmlcpp5t64
Version: 1.4.6-1.1+b1
Severity: grave

Unsatisfied dependencies:
 libui-gxmlcpp5t64 : Depends: libui-gxmlcpp5v5 (>= 1.4.3) but it is not
installable

This is because override_dh_makeshlibs generates a dep on the pre-t64 name.


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

Kernel: Linux 6.7.9-amd64 (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.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 libui-gxmlcpp5t64 depends on:
pn  libboost-test1.83.0  
ii  libc62.37-18
ii  libgcc-s114-20240330-1
ii  libstdc++6   14-20240330-1
pn  libui-utilcpp9t64
ii  libxml2  2.9.14+dfsg-1.3+b2
ii  libxslt1.1   1.1.35-1

libui-gxmlcpp5t64 recommends no packages.

libui-gxmlcpp5t64 suggests no packages.



Bug#1069247: libconfig-model-dpkg-perl: test failures

2024-04-20 Thread Dominique Dumont
On Thursday, 18 April 2024 19:21:55 CEST you wrote:
> Source: libconfig-model-dpkg-perl
> Version: 3.004
> Severity: serious
> Tags: ftbfs
> Justification: fails to build from source

This really looks like a bug with prove:

$ perl t/reorder.t 
ok 1 -  test re-ordered list
1..1
$ prove -l -v -p t/reorder.t 
t/reorder.t .. 
ok 1 -  test re-ordered list
1..1
Failed 1/1 subtests 

Test Summary Report
---
t/reorder.t (Wstat: 0 Tests: 0 Failed: 0)
  Parse errors: Bad plan.  You planned 1 tests but ran 0.
Files=1, Tests=0,  1 wallclock secs ( 0.02 usr  0.00 sys +  0.92 cusr  0.07 
csys =  1.01 CPU)
Result: FAIL


I can't see what's wrong with the output of reorder test...

I'll try to dig this later on..

All the best



Bug#1066938: Fwd: Bug#1066938: libfiu: FTBFS on arm{el,hf}: /tmp/cc54dEva.s:726: Error: symbol `open64' is already defined

2024-04-20 Thread Alberto Bertogli

On Sat, Apr 20, 2024 at 12:00:00AM +0200, Santiago Vila wrote:

El 25/3/24 a las 20:12, Chris Lamb escribió:

Alberto Bertogli wrote:


If you know of a functional official image that I can use to try to
reproduce the problem, or recently-tested steps I can follow to get
a working qemu install, please let me know.


Alas, I can't actually be helpful here. There are no official images
as far as I know… and somewhat annoyingly I (ie. a Debian Developer)
actually have access to some machines set aside for this purpose. I
call this "annoying" because I naturally can't then give you direct
SSH access transitively — but I can proxy ideas, of course.


Hi.

I can't offer ssh access either (for now), but I've checked and
this error may be reproduced easily on an arm64 machine using an
armel chroot.


Oohhh this is good to know, I didn't know that was a viable option.  
Thank you for the suggestion!


I will try to reproduce it this way, I'll let you know how it goes.

Thank you!
Alberto



Bug#1033462: kmail: Kmail fails to send emails via Google mail with "Failed to authenticate additional scopes"

2024-04-20 Thread Sedat Dilek
Hi,

I upgraded yesterday my machine from bookworm/stable to trixie/testing.

KMail was used to check if I can send emails - this seems no more to work.

Seeing the same issue like Ariel Garcia in #1033462 (sorry partly in German):

We have an error during reading password  "Entry not found"
We have an error during reading password  "Entry not found"
[SASL-XOAUTH2] - Requesting authID!
[SASL-XOAUTH2] - Requesting token!
[SASL-XOAUTH2] - filling prompts!
[SASL-XOAUTH2] - Requesting authID!
[SASL-XOAUTH2] - Requesting token!
org.kde.kgapi: Bad request, Google replied ' "{\n  \"error\":
\"invalid_grant\",\n  \"error_description\": \"Bad Request\"\n}" '
org.kde.pim.mailtransport.smtpplugin: Error obtaining XOAUTH2 token:
"Authentifizierung zusätzlicher Bereiche ist fehlgeschlagen"
org.kde.pim.ksmtp: SMTP Socket error:
QAbstractSocket::RemoteHostClosedError "Der entfernte Rechner hat die
Verbindung geschlossen"

English:

org.kde.pim.mailtransport.smtpplugin: Error obtaining XOAUTH2 token: "Failed to
authenticate additional scopes"
org.kde.pim.ksmtp: SMTP Socket error: QAbstractSocket::RemoteHostClosedError
"The remote host closed the connection"

When NO password (token) is set I see:
We have an error during reading password  "Entry not found"

Tryouts:

[ kmail - SMTP ]

User: sedat.di...@gmail.com
Pass:MYTOKEN

Encryption-1: STARTTLS
Port-1: 587
Authentication-1: XOAUTH2

Alternatively:

Encryption-2: SSL/TLS
Port-2: 465
Authentication-2: XOAUTH2

NOTE: On Gmail side nothing was changed - I can send patches via git
send-email but not KMail.

I use postgresql backend and can connect to the database and its tables.

[ ~/.config/akonadi/akonadiserverrc ]

[Debug]
Tracer=null

[%General]
Driver=QPSQL

[QPSQL]
Host=
InitDbPath=
Name=akonadi-dileks
Options=
ServerPath=
StartServer=false
- EOF -

Deleting all files in ~/.config/akonadi/ but keeping akonadiserverrc
plus deleting directory ~/.local/share/akonadi after stopping akonadi
did not help.

In May 2023 was my last working sent-email - I kept all test-emails
and are stored in sent-mail:

[ 
~/.local/share/local-mail/sent-mail/new/1683526703181.R196.iniza26703181.R196.iniza
]

From: dileks 
To: sedat.di...@gmail.com
Subject: KMail - Test 08-May-2023
Date: Mon, 08 May 2023 08:18:22 +0200
Message-ID: <2687898.mvXUDI8C0e@iniza>
X-KMail-Identity: 1886993645
X-KMail-Transport: 1190029663
X-KMail-Fcc: 20
X-KMail-Identity-Name: dileks
X-KMail-Transport-Name: dileks@gmail
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"

KMail - Test 08-May-2023
- EOF -

Not sure where to dig into the woods.

Any help is much appreciated.

Thanks.

Best regards,
-Sedat-



Bug#1069339: Not installable due to hardcoded pre-t64 library deps

2024-04-20 Thread Andrey Rakhmatullin
Package: libvdeplug-pcap
Version: 0.1.0-2+b3
Severity: grave

libvdeplug-pcap explicitly Depends: libvdeplug2, libpcap0.8. They should be
changed to the t64 names if they are really needed.


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

Kernel: Linux 6.7.9-amd64 (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.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 libvdeplug-pcap depends on:
ii  libc6 2.37-18
ii  libpcap0.8t64 [libpcap0.8]1.10.4-4.1
ii  libvdeplug2t64 [libvdeplug2]  4.0.1-5.1

libvdeplug-pcap recommends no packages.

libvdeplug-pcap suggests no packages.



Bug#1069256: debian-policy: clarify requirement for use of Static-Built-Using

2024-04-20 Thread Chris Hofstaedtler
On Thu, Apr 18, 2024 at 11:29:11PM +0300, Maytham Alsudany wrote:
> +``Static-Built-Using``
> +~~

IMO this should not only state when it is to be used, but also what
it is used for and by whom. IOW who is the intended receiver. What
will they do with the info provided in this field?

> +When a binary is statically linked to libraries in other packages and
> +incorporated into the build process,

Should this also include non-libraries that were included?
publicsuffix is a package providing *data* that is often translated
into binary data during package builds and thus included. But it is
not a "library" in the traditional way.

Chris



Bug#1069330: ITP: golang-github-akihirosuda-apt-transport-oci -- OCI transport plugin for apt-get (i.e., apt-get over ghcr.io)

2024-04-20 Thread Jianfeng Liu
Package: wnpp
Severity: wishlist
Owner: Jianfeng Liu 
X-Debbugs-Cc: debian-de...@lists.debian.org, debian...@lists.debian.org, 
liujianfeng1...@gmail.com

* Package name: golang-github-akihirosuda-apt-transport-oci
  Version : 0.0~git20240416.a7e2cf0-1
  Upstream Contact: Akihiro Suda 
* URL : https://github.com/AkihiroSuda/apt-transport-oci
* License : Apache-2.0
  Programming Lang: Go
  Description : OCI transport plugin for apt-get (i.e., apt-get over 
ghcr.io)

apt-transport-oci is an apt-get plugin to support distributing *.deb
 packages over an OCI registry such as ghcr.io
More info about it from is github page:
 https://github.com/AkihiroSuda/apt-transport-oci

GHCR is a free platform to host apt repos, supporting oci in apt should
be cool.



Bug#1068324: lintian: patch-not-forwarded-upstream for upstream patches

2024-04-20 Thread Nilesh Patra
Hi Thorsten,

Quoting mirabilos:
> (at least bookworm’s) lintian complains about…
> I: mksh source: patch-not-forwarded-upstream 
> [debian/patches/typeset-p-fix.diff]
> … for patches whose DEP 3 metadata clearly state they are a
> cherry-pick or backport from upstream.
>
> Here (cherry-pick):
>
> Origin: commit:10065BC69BE555D6721
>
> DEP 3 says the Forwarded header is only applicable for
> patches that don’t originate upstream.

Right. AFAICS, lintian spews that warning because the header in that patch in
incomplete. It also needs a "From" and "Subject" (which can be same as commit
message) and something that's also specified in the dep3 protocol while
cherry-picking patch from upstream. https://dep-team.pages.debian.net/deps/dep3/

If you add the "From" and "Subject" field, this should work. If you can confirm
the same, we could close this bug.

Best,
Nilesh


signature.asc
Description: PGP signature


Bug#1069331: Not installable due to hardcoded pre-t64 library deps

2024-04-20 Thread Andrey Rakhmatullin
Package: libcegui-mk2-dev
Version: 0.8.7+git20220615-5.1+b5
Severity: grave

Unsatisfied dependencies:
 libcegui-mk2-dev : Depends: libxerces-c3.2 but it is not installable

It should be changed to the t64 name if it's really needed.


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

Kernel: Linux 6.7.9-amd64 (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.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 libcegui-mk2-dev depends on:
ii  libc6  2.37-18
pn  libcegui-mk2-0.8.7 
pn  libcegui-mk2-0.8.7t64  
pn  libdevil-dev   
pn  libfreeimage-dev   
pn  libfreetype-dev
ii  libgcc-s1  14-20240330-1
pn  libjpeg-dev
pn  liblcms2-dev   
pn  libmng-dev 
pn  libpcre2-dev   
pn  libpng-dev 
ii  libstdc++6 14-20240330-1
pn  libtiff-dev
pn  libxerces-c3.2 
pn  lua-expat-dev  
ii  zlib1g-dev [libz-dev]  1:1.3.dfsg-3.1

libcegui-mk2-dev recommends no packages.

Versions of packages libcegui-mk2-dev suggests:
pn  libcegui-mk2-doc  



Bug#1068024: latest Jia-Tan-free xz version seems to be 5.2.5

2024-04-20 Thread Boud Roukema

hi all

Leaving aside the questions of dependencies of other Debian packages,
I agree that 5.2.5 looks like the most recent version that is
definitely free of any directly or indirectly authored contributions
by Jia Tan.

https://salsa.debian.org/debian/xz-utils/-/tree/v5.2.5?ref_type=tags

In the salsa full source:

$ git checkout v5.2.5
Previous HEAD position was d24a57b7 Bump version and soname for 5.2.7.
HEAD is now at 2327a461 Bump version and soname for 5.2.5.

$ git log --stat --graph |grep "Jia"

# No sign of Jia Tan.

$ git checkout v5.2.6
Previous HEAD position was 2327a461 Bump version and soname for 5.2.5.
HEAD is now at 8dfed05b Bump version and soname for 5.2.6.

$ git log --stat --graph |grep "Jia" |wc
 16 129 774

# Two commits and several 'Thanks to ... '.

Cheers
Boud


PS: For any RedHat people reading this thread: unfortunately, 5.2.5 is
before the fix 31d80c6b that Lasse Collin did to handle the "ill patch"
introduced by RHEL/CentOS7:

  
https://salsa.debian.org/debian/xz-utils/-/commit/31d80c6b261b24220776dfaeb8a04f80f80e0a24

That's a RHEL problem to handle, not a Debian problem.



Bug#1069345: qwinff : FTBFS on armel,armhf

2024-04-20 Thread Kentaro HAYASHI
Source: qwinff
Severity: important
Tags: ftbfs
Control: found -1  
X-Debbugs-Cc: ken...@xdump.org

Dear Maintainer,

qwinff fails to build on armhel,armhf.

FYI:

https://buildd.debian.org/status/fetch.php?pkg=qwinff=armel=0.2.1%2Bgit20201215-2=1685891638=0
https://buildd.debian.org/status/fetch.php?pkg=qwinff=armhf=0.2.1%2Bgit20201215-2=1675408467=0

NOTE: it seems that already reported for upstream, but not
fixed yet.
https://github.com/qwinff/qwinff/issues/35

Regards,



Bug#1069332: Not installable due to hardcoded pre-t64 library deps

2024-04-20 Thread Andrey Rakhmatullin
Package: gvmd
Version: 23.1.0-1+b4
Severity: grave

gvmd explicitly Depends: libgvm22. It should be changed to the t64 name if it's
really needed.


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

Kernel: Linux 6.7.9-amd64 (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.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 gvmd depends on:
ii  adduser  3.137
pn  doc-base 
pn  greenbone-feed-sync  
pn  gvmd-common  
ii  libbsd0  0.12.2-1
ii  libc62.37-18
ii  libglib2.0-0t64  2.78.4-6
ii  libgnutls30t64   3.8.5-2
ii  libgpgme11t641.18.0-4.1+b1
pn  libgvm22 
pn  libgvm22t64  
ii  libical3t64  3.0.17-1.1+b1
pn  libpq5   
pn  notus-scanner
pn  ospd-openvas 
pn  pg-gvm   
pn  postgresql-16
pn  xml-twig-tools   

Versions of packages gvmd recommends:
pn  nsis  
pn  rpm   

gvmd suggests no packages.



Bug#1069337: Update Depends for the time64 library renames

2024-04-20 Thread Andrey Rakhmatullin
Package: thunderbird
Version: 1:115.9.0-1+b1
Severity: serious

thunderbird explicitly Depends: libotr5. It should be changed to the t64 name
if it's really needed.

Note that the package is still installable because it's not built on 32-bit
time64 arches, but it still needs to be fixed so that libotr5 can be removed.


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

Kernel: Linux 6.7.9-amd64 (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.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 thunderbird depends on:
ii  debianutils 5.17
ii  fontconfig  2.15.0-1.1
ii  kdialog 4:22.12.3-1+b1
ii  libasound2t64 [libasound2]  1.2.11-1+b1
ii  libatk1.0-0t64 [libatk1.0-0]2.52.0-1
ii  libc6   2.37-18
ii  libcairo-gobject2   1.18.0-3+b1
ii  libcairo2   1.18.0-3+b1
ii  libdbus-1-3 1.14.10-4+b1
pn  libdbus-glib-1-2
ii  libevent-2.1-7t64 [libevent-2.1-7]  2.1.12-stable-8.1+b3
ii  libffi8 3.4.6-1
ii  libfontconfig1  2.15.0-1.1
ii  libfreetype62.13.2+dfsg-1+b4
ii  libgcc-s1   14-20240330-1
ii  libgdk-pixbuf-2.0-0 2.42.10+dfsg-3+b3
ii  libglib2.0-0t64 [libglib2.0-0]  2.78.4-6
ii  libgtk-3-0t64 [libgtk-3-0]  3.24.41-4
ii  libnspr42:4.35-1.1+b1
ii  libnss3 2:3.99-1
pn  libotr5 
ii  libpango-1.0-0  1.52.1+ds-1
pn  librnp0 
ii  libstdc++6  14-20240330-1
ii  libvpx8 1.13.1-2
ii  libx11-62:1.8.7-1
ii  libx11-xcb1 2:1.8.7-1
ii  libxcb-shm0 1.17.0-1
ii  libxcb1 1.17.0-1
ii  libxext62:1.3.4-1+b1
ii  libxrandr2  2:1.5.4-1
ii  psmisc  23.7-1
ii  x11-utils   7.7+6+b1
ii  zenity  4.0.1-1+b1
ii  zlib1g  1:1.3.dfsg-3.1

Versions of packages thunderbird recommends:
ii  hunspell-ru [hunspell-dictionary]  1:24.2.2-1

Versions of packages thunderbird suggests:
ii  apparmor  3.0.13-2
pn  fonts-lyx 
ii  libgssapi-krb5-2  1.20.1-6+b1



Bug#1069340: Wrong symbols file causes depends on the pre-t64 name

2024-04-20 Thread Andrey Rakhmatullin
Package: libxbase64-1t64
Version: 3.1.2-14.1+b2
Severity: grave

$ head -1 /var/lib/dpkg/info/libxbase64-1t64:armhf.symbols
libxbase64.so.1 libxbase64-1 #MINVER#

This makes libxbase64-bin uninstallable as it now Depends on libxbase64-1. It
would make other revdeps uninstallable too, but this package doesn't have
revdeps. Does Debian need this library?


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

Kernel: Linux 6.7.9-amd64 (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.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 libxbase64-1t64 depends on:
ii  libc6   2.37-18
ii  libgcc-s1   14-20240330-1
ii  libstdc++6  14-20240330-1

libxbase64-1t64 recommends no packages.

libxbase64-1t64 suggests no packages.



Bug#1066369: obitools: FTBFS: error: implicit declaration of function ‘heapsort’

2024-04-20 Thread Étienne Mollier
Hi,

Lucas Nussbaum, on 2024-03-13:
> > build/temp.linux-x86_64-cpython-311/pyrex/obitools/word/_readindex.c:6320:3:
> >  error: implicit declaration of function ‘heapsort’ 
> > [-Werror=implicit-function-declaration]

Interesting, if I trust the Debian online manual of heapsort[1],
this is a Berkeley function optimized for "almost" sorted
arrays.  I see two options here: either try to implement the
libbsd compatibility layer in cython context, or replace
heapsort by qsort[2] (and remove the heapsort function
declaration from the .pyx); the two functions look to have
compatible argument passing.

I would consider implementing the replacement by qsort: this may
affect the memory consumption, and possibly performances of
obitools; on the other hand I wonder how come the program
managed to do the sorting without appropriate function available
in the application binary interface in the first place.

[1]: https://manpages.debian.org/bookworm/libbsd-dev/heapsort.3bsd.en.html
[2]: https://manpages.debian.org/bookworm/manpages-fr-dev/qsort.3.fr.html

Have a nice day,  :)
-- 
  .''`.  Étienne Mollier 
 : :' :  pgp: 8f91 b227 c7d6 f2b1 948c  8236 793c f67e 8f0d 11da
 `. `'   sent from /dev/pts/1, please excuse my verbosity
   `-on air: Genesis - Throwing it All Away


signature.asc
Description: PGP signature


Bug#1069341: ksh93u+m should not be advertised as being POSIX compliant

2024-04-20 Thread Vincent Lefevre
Package: ksh93u+m
Version: 1.0.8-1
Severity: minor

The ksh93u+m package description contains

 KornShell is an interactive UNIX command interpreter as well as a POSIX
   ^
 compliant scripting language which is a superset of sh(1), the System
 ^
 V UNIX shell.
 .
 The ksh93 version of KornShell has the functionality of other scripting
 languages such as AWK, Icon, Perl, Rexx, Tcl and is a full-featured,
 expressive scripting language which complies with POSIX.2 Shell and
   ^
 Utilities (IEEE Std 1003.2-1992).
 

But POSIX compliance is not true by default. So this is misleading,
and the references to the POSIX compliance should be removed.

-- System Information:
Debian Release: trixie/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500, 
'stable-security'), (500, 'stable-debug'), (500, 'proposed-updates-debug'), 
(500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 6.6.15-amd64 (SMP w/16 CPU threads; PREEMPT)
Locale: LANG=C.UTF-8, LC_CTYPE=C.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 ksh93u+m depends on:
ii  libc6  2.37-17

ksh93u+m recommends no packages.

Versions of packages ksh93u+m suggests:
pn  binfmt-support  

-- no debconf information

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



Bug#1069346: please don't auto-enable the shipped timers

2024-04-20 Thread Evgeni Golov
Package: prometheus-node-exporter-collectors
Version: 0.0~git20230203.6f710f8-1

Ohai,

I know it's custom in Debian to auto-enable services when they are
installed, however I think that the broad variety of timers present in
the collectors package deserves a different treatment, as people usually
don't want all collectors enabled on a given machine (vs when they
install the "foo" daemon package, they usually want "food" running).

TIA
Evgeni

PS: filed against the version in stable, as that's what I have
installed, but I didn't see anything in packaging git or changelog that
says the newer versions behave differently.



Bug#1069347: rust-servo-freetype-sys: FTBFS on armel,armhf CMake Error: The source directory "/<>/freetype2" does not exist.

2024-04-20 Thread Kentaro HAYASHI
Source: rust-servo-freetype-sys
Severity: serious
Tags: ftbfs
Control: found -1 4.0.5-2
X-Debbugs-Cc: ken...@xdump.org

Dear Maintainer,

rust-servo-freetype-sys fails to build on armhf.

FYI:

https://buildd.debian.org/status/fetch.php?pkg=rust-servo-freetype-sys=armel=4.0.5-2=1688825741=0
https://buildd.debian.org/status/fetch.php?pkg=rust-servo-freetype-sys=armhf=4.0.5-2=1688826040=0

Regards,



Bug#1069090: ITP: golang-github-cloudflare-apt-transport-cloudflared -- Golang package to protect APT repositories using Cloudflare Access

2024-04-20 Thread Jianfeng Liu
My code has been pushed to
https://salsa.debian.org/go-team/packages/golang-github-cloudflare-apt-transport-cloudflared/
with help from Maytham. And this package is the build dependency
of Bug#1069330: ITP: golang-github-akihirosuda-apt-transport-oci:
https://lists.debian.org/debian-go/2024/04/msg00014.html


Bug#1069334: Not installable due to hardcoded pre-t64 library deps

2024-04-20 Thread Andrey Rakhmatullin
Package: nautilus-wipe
Version: 0.4.alpha2-0.1+b4
Severity: grave

nautilus-wipe explicitly Depends: libgtk-3-0. It should be changed to the t64
name if it's really needed.


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

Kernel: Linux 6.7.9-amd64 (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.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 nautilus-wipe depends on:
ii  libc6   2.37-18
ii  libglib2.0-0t64 [libglib2.0-0]  2.78.4-6
pn  libgsecuredelete0   
ii  libgtk-3-0t64 [libgtk-3-0]  3.24.41-4
pn  libnautilus-extension4  

nautilus-wipe recommends no packages.

nautilus-wipe suggests no packages.



Bug#1069335: Not installable due to hardcoded pre-t64 library deps

2024-04-20 Thread Andrey Rakhmatullin
Package: prads
Version: 0.3.3-7+b5
Severity: grave

prads explicitly Depends: libpcap0.8. It should be changed to the t64 name if
it's really needed.


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

Kernel: Linux 6.7.9-amd64 (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.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 prads depends on:
ii  adduser 3.137
ii  init-system-helpers 1.66
ii  libc6   2.37-18
ii  libpcap0.8t64 [libpcap0.8]  1.10.4-4.1
ii  libpcre32:8.39-15+b1

prads recommends no packages.

prads suggests no packages.



Bug#1069336: Not installable due to hardcoded pre-t64 library deps

2024-04-20 Thread Andrey Rakhmatullin
Package: seafile-gui
Version: 9.0.4+ds1-1+b4
Severity: grave

seafile-gui explicitly Depends: libsearpc1, libseafile0. They should be changed
to the t64 names if they are really needed.


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

Kernel: Linux 6.7.9-amd64 (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.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 seafile-gui depends on:
ii  libc6   2.37-18
ii  libgcc-s1   14-20240330-1
ii  libglib2.0-0t64 [libglib2.0-0]  2.78.4-6
ii  libjansson4 2.14-2+b2
ii  libqt5core5t64 [libqt5core5a]   5.15.10+dfsg-7.2+b1
ii  libqt5dbus5t64 [libqt5dbus5]5.15.10+dfsg-7.2+b1
ii  libqt5gui5t64 [libqt5gui5]  5.15.10+dfsg-7.2+b1
ii  libqt5network5t64 [libqt5network5]  5.15.10+dfsg-7.2+b1
ii  libqt5webkit5   5.212.0~alpha4-33+b3
ii  libqt5widgets5t64 [libqt5widgets5]  5.15.10+dfsg-7.2+b1
pn  libquazip5-1
pn  libquazip5-1t64 
pn  libseafile0 
pn  libseafile0t64  
pn  libsearpc1  
pn  libsearpc1t64   
ii  libsqlite3-03.45.3-1
ii  libstdc++6  14-20240330-1
pn  seafile-daemon  

seafile-gui recommends no packages.

Versions of packages seafile-gui suggests:
pn  seafile-cli  



Bug#1068430: closed by Debian FTP Masters (reply to handsome_feng ) (Bug#1068430: fixed in qt5-ukui-platformtheme 1.0.8-2)

2024-04-20 Thread Andrey Rakhmatullin
Control: reopen -1

On Mon, Apr 08, 2024 at 06:57:04AM +, Debian Bug Tracking System wrote:
>  qt5-ukui-platformtheme (1.0.8-2) unstable; urgency=medium
>  .
>[Steve langasek]
>* Remove hard-coded dependencies on libqt5widgets5 and libgsettings-qt1.
>  and don't hard-code dependency on shared libglib library.
>  (Closes: #1068430)
This didn't happen.
Instead the explicit deps on libqt5-ukui-style1 and qt5-styles-ukui were
replaced with ${lib:Depends} in the qt5-ukui-platformtheme package.


-- 
WBR, wRAR


signature.asc
Description: PGP signature


Bug#1069342: RFP: bbcp -- Parallel SSH transfer

2024-04-20 Thread Jari Aalto
Package: wnpp
Severity: wishlist

* Package name: bbcp
  Version : 14.04.14.00.1 (from cpmpiled bbcp -h)
  Upstream Author : Ertuğrul Emre Ertekin (Maintainer) 
* URL : https://github.com/eeertekin/bbcp
* License : LGPL-3+
  Programming Lang: C++
  Description : Data transfer utility

bbcp is a simple command-line tool which can
use your SSH connection to transfer data in
and out. It connects to the transfer server
using the usual SSH credentials but then it
can set up parallel data streams for
transferring data.

Provides faster transfer speeds than plain
SSH.

NOTES

1. Compiles ok under current Debian testing with

g++-13-x86-64-linux-gnu 13.2.0-13

2. original page with documentation
Licence reads: LGPL-3+ (Github lists
incorrect GPL-3+)

https://www.slac.stanford.edu/~abh/bbcp/



Bug#1069586: Chromium native Wayland support broken

2024-04-20 Thread Stephan Verbücheln
Package: chromium
Version: 124.0.6367.60-1~deb12u1

Since the last update, Chromium does work with native Wayland. It is
starting up, but it is displaying an invisible window. It is listed in
the window switchers (Alt+Tab), Gnome Shell etc., but invisible.

Note: The default configuration uses X11 via XWayland and is working.

The setting can be managed via command line arguments or by typing
chrome://flags into the URL bar (filter for ozone).

Available settings:
default -> X11works
auto-> Wayland if available   does not work
x11   works
wayland   does not work

I have been using Chromium with native Wayland for many months without
problems until the last update.

I reproduced this with a completely new browser profile.

Regards
Stephan



Bug#1050393: Unneeded dependency on "dconf-gsettings-backend | gsettings-backend"?

2024-04-20 Thread Xiyue Deng
Sean Whitton  writes:

> Hello,
>
> On Wed 27 Mar 2024 at 11:40pm -07, Xiyue Deng wrote:
>
>> Sean Whitton  writes:
>>
>>> Hello,
>>>
>>> Rob, can you review the implementation in d/rules for Xiyue's patch to
>>> this bug, please?  I'm not sure it's the straightforward way to do it.
>>>
>>> Xiyue, I think it would make sense to use emacs-common (<< 1:29.3+2-2),
>>> for the relationships.
>>
>> Ah indeed, I should update the versions after the Emacs 29.3 upload,
>> though I think you meant "1:29.3+1-2".  Also, as we are just moving
>> files from emacs-common to emacs-pgtk, breaks/replaces is only needed
>> from emacs-pgtk to emacs-common but no the other way around, so I
>> dropped the breaks on emacs-pgtk from emacs-common.
>>
>> I have updated the patch accordingly and attached here.  PTAL.
>
> Thanks.
>
>> (BTW, I'm always curious about the "+1" part of the version number.  I
>> would expect something like "+dfsg" or "+ds" as we are dropping some
>> of the non-DFSG conformant files, but why "+1"? :)
>
> It's just in case the DFSG split is done incorrectly and another attempt
> is required -- given how complex it is.

Ack, totally understandable.

With the release of Emacs 1:29.3+1-2, I have rebased the patch onto it
and bumped the breaks/replaces version.  PTAL.

-- 
Xiyue Deng

>From c0a4ee1d76f2206594ce9897b651bbdd22baf716 Mon Sep 17 00:00:00 2001
From: Xiyue Deng 
Date: Wed, 13 Mar 2024 10:22:46 -0700
Subject: [PATCH] Install GSettings schema in pgtk build only (Closes:
 #1050393)

* In PGTK build it generates the GSettings schema file
"/usr/share/glib-2.0/schemas/org.gnu.emacs.defaults.gschema.xml" which
is not needed in other variant.
* Move the file from emacs-common to emacs-pgtk, and adds proper
breaks/replaces to ensure a smooth upgrade.
---
 debian/changelog |  7 +++
 debian/control   | 11 +--
 debian/rules |  9 -
 3 files changed, 24 insertions(+), 3 deletions(-)

diff --git a/debian/changelog b/debian/changelog
index 5d4e9f050ae..e2a31a36fcb 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+emacs (1:29.3+1-3) UNRELEASED; urgency=medium
+
+  * Team upload.
+  * Install GSettings schema in pgtk build only (Closes: #1050393)
+
+ -- Xiyue Deng   Wed, 13 Mar 2024 10:22:10 -0700
+
 emacs (1:29.3+1-2) unstable; urgency=medium
 
   * Change native-comp-async-report-warnings-errors to `silent'.
diff --git a/debian/control b/debian/control
index e168717089f..3c04652c769 100644
--- a/debian/control
+++ b/debian/control
@@ -138,8 +138,15 @@ Provides: editor, emacs, emacsen, info-browser, mail-reader, news-reader
 Recommends: fonts-noto-color-emoji
 Suggests: emacs-common-non-dfsg
 Conflicts: emacs-gtk, emacs-lucid, emacs-nox
-Replaces: emacs-gtk, emacs-lucid, emacs-nox, emacs-bin-common (<< 1:29.2)
-Breaks: emacs-bin-common (<< 1:29.2)
+Replaces:
+ emacs-gtk,
+ emacs-lucid,
+ emacs-nox,
+ emacs-bin-common (<< 1:29.2),
+ emacs-common (<< 1:29.3+1-3~),
+Breaks:
+ emacs-bin-common (<< 1:29.2),
+ emacs-common (<< 1:29.3+1-3~),
 Description: GNU Emacs editor (with GTK+ Wayland GUI support)
  GNU Emacs is the extensible self-documenting text editor.  This
  package contains a version of Emacs with a graphical user interface
diff --git a/debian/rules b/debian/rules
index 6250f60ea9b..205c45dff65 100755
--- a/debian/rules
+++ b/debian/rules
@@ -425,6 +425,9 @@ override_dh_auto_install: $(autogen_install_files)
 	  cp -a $(install_dir_pgtk)/* $(pkgdir_common)
 
 	  rm -r $(pkgdir_common)/usr/bin
+	  # PGTK builds a GSettings schema that is PGTK specific and
+	  # should not be shipped in emacs-common
+	  rm -r $(pkgdir_common)/usr/share/glib-2.0
 	  rm \
 	$(pkgdir_common)/$(libexec_dir_emacs)/hexl \
 	$(pkgdir_common)/$(libexec_dir_emacs)/emacs-*.pdmp \
@@ -548,7 +551,7 @@ override_dh_auto_install: $(autogen_install_files)
 
 ##
 # emacs-pgtk
-ifneq (,$(findstring emacs, $(shell dh_listpackages)))
+ifneq (,$(findstring emacs-pgtk, $(shell dh_listpackages)))
 	  $(call install_common_binpkg_bits,$(install_dir_pgtk),$(pkgdir_pgtk),emacs-pgtk,pgtk)
 
   # install desktop entries
@@ -557,6 +560,10 @@ override_dh_auto_install: $(autogen_install_files)
 	debian/emacs.desktop \
 	debian/emacs-term.desktop \
 	$(pkgdir_pgtk)/usr/share/applications/
+	  # install GSettings schema
+	  install -d $(pkgdir_pgtk)/usr/share/glib-2.0
+	  cp -a $(install_dir_pgtk)/usr/share/glib-2.0/* \
+	$(pkgdir_pgtk)/usr/share/glib-2.0
 endif
 
 ##
-- 
2.39.2



Bug#1069586: Chromium native Wayland support broken

2024-04-20 Thread Stephan Verbücheln
Workaround:

If you are stuck Chromium using native Wayland support, you can reset
it with the following steps:

1. Log out GNOME on Wayland session and log in with Gnome on Xorg
session.
2. Launch Chromium.
3. Enter chrome://flags into URL bar and reset the setting “Preferred
Ozone platform” to “Default”.
4. Log out and log in again with Wayland session.

Regards
Stephan



Bug#1069587: linux-cpupower: turbostat core dump in compute_average, regression

2024-04-20 Thread Witold Baryluk
Package: linux-cpupower
Version: 6.7.9-2
Severity: normal
X-Debbugs-Cc: witold.bary...@gmail.com


turbostat 6.7.9-2 core dumps on my AMD Threadripper 2950X

linux-cpupower_6.6.15-2_amd64.deb works fine.

gdb session with 6.7.9-2

root@debian:~# gdb turbostat 
GNU gdb (Debian 13.2-1) 13.2
Reading symbols from turbostat...
Reading symbols from 
/usr/lib/debug/.build-id/6f/8e4bb8d39e0b45899098c6bd0307918833eeb8.debug...
(gdb) r
Starting program: /usr/sbin/turbostat 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
turbostat version 2023.11.07 - Len Brown 
Kernel command line: BOOT_IMAGE=/live/vmlinuz-6.6.15-amd64 intel_iommu=on 
iommu=pt amd_iommu=on radeon.si_support=0 radeon.cik_support=0 
amdgpu.si_support=1 amdgpu.cik_support=1 amdgpu.ppfeaturemask=0x 
amdgpu.audio=0 processors.max_cstate=1 intel_idle.max_cstate=0 idle=halt 
modprobe.blacklist=snd_hda_codec_hdmi,snd_hda_intel boot=live components 
locales=en_US.UTF-8 findiso=
CPUID(0): AuthenticAMD 0xd CPUID levels
CPUID(1): family:model:stepping 0x17:8:2 (23:8:2) microcode 0x0
CPUID(0x8000): max_extended_levels: 0x801f
CPUID(1): SSE3 MONITOR - - - TSC MSR - HT -
CPUID(6): APERF, No-TURBO, No-DTS, No-PTM, No-HWP, No-HWPnotify, No-HWPwindow, 
No-HWPepp, No-HWPpkg, No-EPB
CPUID(7): No-SGX No-Hybrid
cpu0: cpufreq driver: acpi-cpufreq
cpu0: cpufreq governor: performance
cpufreq boost: 1
/dev/cpu_dma_latency: 4000 usec (constrained)
current_driver: none
current_governor: menu
current_governor_ro: menu
RAPL: 234 sec. Joule Counter Range, at 280 Watts
[New Thread 0x77fc1740 (LWP 1098480)]
[New Thread 0x77d886c0 (LWP 1098481)]
[Thread 0x77d886c0 (LWP 1098481) exited]

Thread 1 "turbostat" received signal SIGFPE, Arithmetic exception.
0xfc24 in compute_average (t=, c=, 
p=) at 
/build/reproducible-path/linux-6.7.9/tools/power/x86/turbostat/turbostat.c:2479
2479  
/build/reproducible-path/linux-6.7.9/tools/power/x86/turbostat/turbostat.c: No 
such file or directory.
(gdb) bt
#0  0xfc24 in compute_average (t=, c=, p=) at 
/build/reproducible-path/linux-6.7.9/tools/power/x86/turbostat/turbostat.c:2479
#1  0x555676ea in turbostat_loop () at 
/build/reproducible-path/linux-6.7.9/tools/power/x86/turbostat/turbostat.c:4364
#2  0x7542 in main (argc=1, argv=0x7fffebe8) at 
/build/reproducible-path/linux-6.7.9/tools/power/x86/turbostat/turbostat.c:6753
(gdb) 


Probably some division by zero in the code.


For comparison older version of turbostat (on same cpu and kernel) shows:

Die Core  CPU Avg_MHz Busy% Bzy_MHz TSC_MHz IPC IRQ CorWatt PkgWatt
- - - 21  1.37  1511  1750  0.67  14450 2.59  39.87
1 0 8 50  1.74  2893  3500  0.73  1115  0.38  39.87
1 0 24  44  1.42  3111  3500  0.66  822
1 1 9 68  2.17  3127  3500  0.75  1051  0.35
1 1 25  20  0.73  2696  3500  0.33  1244
1 2 10  50  1.59  3158  3500  0.50  987 0.30
1 2 26  31  0.99  3151  3500  0.61  1036
1 3 11  40  1.25  3174  3500  0.77  658 0.46
1 3 27  114 3.62  3137  3500  0.85  1186
1 4 12  102 3.20  3171  3500  0.56  1180  0.44
1 4 28  19  0.67  2860  3500  0.40  887
1 5 13  3 0.12  2810  3500  0.33  112 0.18
1 5 29  22  0.81  2768  3500  0.47  899
1 6 14  22  0.83  2670  3500  0.36  1403  0.23
1 6 30  14  0.48  2855  3500  0.35  617
1 7 15  19  0.73  2607  3500  0.41  936 0.26
1 7 31  45  1.59  2833  3500  1.21  317





-- System Information:
Debian Release: trixie/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.6.15-amd64 (SMP w/32 CPU threads; PREEMPT)
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 linux-cpupower depends on:
ii  libc6 2.37-17
ii  libcap2   1:2.66-5
ii  libcpupower1  6.7.9-2
ii  libpci3   1:3.10.0-2

linux-cpupower recommends no packages.

linux-cpupower suggests no packages.

-- no debconf information



Bug#1068797: modsecurity-crs: IncludeOptional in file owasp-crs.load is incompatible with nginx

2024-04-20 Thread Salil Sayed
Thank you Ervin,

I was wondering about the possibility of a trigger that would change the
IncludeOptional to Include if the debian machine is running nginx.

Best regards,

Salil

On Mon, 15 Apr 2024 at 22:18, Ervin Hegedüs  wrote:

> Hi Salil,
>
> Thanks for reporting.
>
> Unfortunately this is a known bug of libmodsecurity3 + Nginx: this
> installation does not support the `IncludeOptional` directive.
>
> The workaround is that you change it manually.
>
> Note, that CRS team suggest (since CRS 4) to use the `Include` form in all
> cases - see documentation:
>
> https://coreruleset.org/docs/deployment/extended_install/#includes-for-nginx
>
>
> Regards,
>
> a.
>
>
> On Thu, Apr 11, 2024 at 11:27 AM Salil Sayed  wrote:
>
>> Package: modsecurity-crs
>> Version: 3.3.4-1
>> Severity: important
>> Tags: newcomer
>> X-Debbugs-Cc: salilsa...@gmail.com
>>
>> Dear Maintainer,
>>
>> I configured modsecurity for nginx using the available packages in the
>> bookworm
>> repository; namely, libmodsecurity3 and libnginx-mod-http-modsecurity. It
>> worked like charm except with this package modsecuirty-crs. The two
>> IncludeOptional directives in the file owasp-crs.load had to be changed to
>> Include since nginx does not support IncludeOptional. This simply worked
>> but by
>> editing a file that the user is not supposed to edit and is likely to be
>> overwritten on update.
>>
>> I believe there may be a way to make the whole modsecurity implementation
>> to
>> work out of the box for nginx as well by simply changing these two
>> IncludeOptional directives to Include. Both of them include files that are
>> already provided by the package hence IncludeOptional is redundant.
>>
>> Thanks,
>> Salil
>>
>>
>>
>> -- System Information:
>> Debian Release: 12.5
>>   APT prefers stable-updates
>>   APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500,
>> 'stable'), (100, 'bookworm-fasttrack'), (100, 'bookworm-backports-staging')
>> Architecture: amd64 (x86_64)
>>
>> Kernel: Linux 6.1.0-17-amd64 (SMP w/8 CPU threads; PREEMPT)
>> Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
>> TAINT_UNSIGNED_MODULE
>> Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.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
>>
>> modsecurity-crs depends on no packages.
>>
>> modsecurity-crs recommends no packages.
>>
>> Versions of packages modsecurity-crs suggests:
>> pn  geoip-database-contrib
>> pn  libapache2-mod-security2  
>> pn  lua   
>> pn  python
>> pn  ruby  
>>
>


Bug#1039979: base-files: /var/run and /var/lock should not be absolute symlinks

2024-04-20 Thread Santiago Vila

El 15/4/24 a las 22:26, Bill Allombert escribió:

On Tue, Jan 30, 2024 at 09:52:39AM +, MOESSBAUER, Felix wrote:

On Fri, 04 Aug 2023 10:44:38 + sohe4b+2fz7rb0ixc53g@cs.email wrote:

Package: base-files
Version: 12.4+deb12u1
Followup-For: Bug #1039979
Control: tags -1 patch

I attach a patch to change absolute symlinks to relative symlinks,

which would fix this bugreport if you choose to do so.

At least the /var/run directory is also created as a symlink to ../run
by tmpfiles.d:

/usr/lib/tmpfiles.d/var.conf from the systemd package contains:
L /var/run - - - - ../run


Why not fix /usr/lib/tmpfiles.d/var.conf to create the correct link then ?
/usr/lib/tmpfiles.d/var.conf is not policy-compliant as it is.


Note that you are using here the words "fix" and "correct" to mean "what policy 
says".

However, the point the reporter was trying to make (if I understood correctly)
is that there is already a "trend" by which it's more useful to have those
symlinks as relative, and the systemd reference was just to highlight such 
trend.

So the question would be: Is policy really correct by requesting those
symlinks to be absolute considering that there seems to be a significant amount
of people (including systemd upstream) who consider more useful for them
to be relative?

Thanks.



Bug#1069367: qemu: FTBFS on arm64: build-dependency not installable: gcc-powerpc64-linux-gnu

2024-04-20 Thread Lucas Nussbaum
On 20/04/24 at 15:27 +0300, Michael Tokarev wrote:
> Control: tag -1 + moreinfo
> Control: found -1 1:4.2-2
> 
> 20.04.2024 15:11, Lucas Nussbaum wrote:
> > Source: qemu
> > Version: 1:8.2.2+ds-2
> > Severity: serious
> > Justification: FTBFS
> > Tags: trixie sid ftbfs
> > User: lu...@debian.org
> > Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-arm64
> 
> 
> > >   sbuild-build-depends-main-dummy : Depends: gcc-powerpc64-linux-gnu but 
> > > it is not installable
> > > E: Unable to correct problems, you have held broken packages.
> 
> I don't understand what are you suggesting to do here.

Hi Michael,

This is part of a mass rebuild, first building on arm64 and then on
armhf and armel. So I'm not suggesting anything. :-)

Is this failing because the build is trying to build arch:all packages,
that can only be built on amd64? If so, the bug severity could be
lowered, clearly.

Lucas



Bug#1069361: libgweather4: FTBFS on arm64: Location 'Greenland' has invalid timezone 'America/Godthab'

2024-04-20 Thread Simon McVittie
Control: retitle -1 libgweather4: FTBFS on arm64: Location 'Greenland' has 
invalid timezone 'America/Godthab'

On Sat, 20 Apr 2024 at 14:06:28 +0200, Lucas Nussbaum wrote:
> Relevant part (hopefully):
> > # GLib-GIO-DEBUG: Failed to initialize portal (GNetworkMonitorPortal) for 
> > gio-network-monitor: Not using portals
> > # GLib-GIO-DEBUG: Failed to initialize networkmanager (GNetworkMonitorNM) 
> > for gio-network-monitor: Could not connect: No such file or directory

I'm fairly sure these are harmless and not an error, hence the DEBUG prefix.
If GLib can't use the NetworkManager network monitor, it will do something
else instead (in practice, generic sockets APIs and Linux netlink).

> > # Location 'Greenland' has invalid timezone 'America/Godthab'
> > # 
> > # Location 'Thule A. B.' has invalid timezone 'America/Godthab'
(etc.)

I think those are likely to be the actual test failure.

smcv



Bug#1069438: cbmc: FTBFS on armhf: make[4]: *** [Makefile:13: test] Error 1

2024-04-20 Thread Lucas Nussbaum
Source: cbmc
Version: 5.95.1-4
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-armhf

Hi,

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


Relevant part (hopefully):
> make[4]: Entering directory '/<>/regression/cbmc'
> Makefile:40: warning: overriding recipe for target 'clean'
> ../../src/common:246: warning: ignoring old recipe for target 'clean'
> Loading
>   1114 tests found
> 
> Running tests
>   Running ACSL/operators.desc  [OK] in 0 seconds
>   Running ACSL/quantifier-precedence.desc  [OK] in 0 seconds
>   Running ASHR1/test.desc  [OK] in 0 seconds
>   Running Address_of1/test.desc  [OK] in 0 seconds
>   Running Address_of2/test.desc  [OK] in 0 seconds
>   Running Anonymous_Struct1/test.desc  [OK] in 1 seconds
>   Running Anonymous_Struct2/test.desc  [OK] in 0 seconds
>   Running Anonymous_Struct3/test.desc  [OK] in 0 seconds
>   Running Array_Access1/test.desc  [OK] in 0 seconds
>   Running Array_Access2/test.desc  [OK] in 0 seconds
>   Running Array_Access3/test.desc  [OK] in 0 seconds
>   Running Array_Initialization1/test.desc  [OK] in 0 seconds
>   Running Array_Initialization2/test.desc  [OK] in 0 seconds
>   Running Array_Initialization3/test.desc  [OK] in 0 seconds
>   Running Array_Pointer1/test.desc  [OK] in 0 seconds
>   Running Array_Pointer2/test.desc  [OK] in 0 seconds
>   Running Array_Pointer3/test.desc  [OK] in 0 seconds
>   Running Array_Pointer4/test.desc  [OK] in 0 seconds
>   Running Array_Pointer5/test.desc  [OK] in 0 seconds
>   Running Array_Pointer6/test.desc  [OK] in 0 seconds
>   Running Array_Pointer7/test.desc  [OK] in 0 seconds
>   Running Array_Propagation1/test.desc  [OK] in 0 seconds
>   Running Array_UF1/test.desc  [OK] in 0 seconds
>   Running Array_UF10/test.desc  [OK] in 0 seconds
>   Running Array_UF11/test.desc  [OK] in 0 seconds
>   Running Array_UF12/test.desc  [OK] in 1 seconds
>   Running Array_UF13/test.desc  [OK] in 0 seconds
>   Running Array_UF14/test.desc  [OK] in 0 seconds
>   Running Array_UF15/test.desc  [OK] in 0 seconds
>   Running Array_UF16/test.desc  [OK] in 0 seconds
>   Running Array_UF17/test.desc  [OK] in 0 seconds
>   Running Array_UF18/test.desc  [OK] in 0 seconds
>   Running Array_UF19/test.desc  [OK] in 0 seconds
>   Running Array_UF2/test.desc  [OK] in 0 seconds
>   Running Array_UF20/test.desc  [OK] in 0 seconds
>   Running Array_UF21/test.desc  [OK] in 1 seconds
>   Running Array_UF22/test.desc  [SKIPPED]
>   Running Array_UF3/test.desc  [OK] in 0 seconds
>   Running Array_UF4/test.desc  [SKIPPED]
>   Running Array_UF5/test.desc  [OK] in 0 seconds
>   Running Array_UF6/test.desc  [OK] in 0 seconds
>   Running Array_UF7/test.desc  [OK] in 0 seconds
>   Running Array_UF8/test.desc  [SKIPPED]
>   Running Array_UF9/test.desc  [OK] in 0 seconds
>   Running Array_operations1/full-slice.desc  [OK] in 0 seconds
>   Running Array_operations1/test.desc  [OK] in 0 seconds
>   Running Array_operations2/test.desc  [OK] in 0 seconds
>   Running Associativity1/test.desc  [OK] in 0 seconds
>   Running Assumption1/test.desc  [OK] in 0 seconds
>   Running BV_Arithmetic1/test.desc  [OK] in 1 seconds
>   Running BV_Arithmetic2/test.desc  [OK] in 0 seconds
>   Running BV_Arithmetic3/test.desc  [OK] in 0 seconds
>   Running BV_Arithmetic4/test.desc  [OK] in 0 seconds
>   Running BV_Arithmetic5/test.desc  [OK] in 0 seconds
>   Running BV_Arithmetic6/test.desc  [OK] in 0 seconds
>   Running Bitfields1/test.desc  [OK] in 0 seconds
>   Running Bitfields2/test.desc  [OK] in 0 seconds
>   Running Bitfields3/paths.desc  [OK] in 1 seconds
>   Running Bitfields3/test.desc  [OK] in 0 seconds
>   Running Bitfields4/test.desc  [OK] in 0 seconds
>   Running Bool/bool1.desc  [OK] in 0 seconds
>   Running Bool/bool2.desc  [OK] in 0 seconds
>   Running Bool/bool3.desc  [OK] in 0 seconds
>   Running Bool/bool4.desc  [OK] in 0 seconds
>   Running Bool/bool5-full-slice.desc  [OK] in 0 seconds
>   Running Bool/bool5.desc  [OK] in 0 seconds
>   Running Bool/bool6.desc  [OK] in 1 seconds
>   Running Bool/bool7.desc  [SKIPPED]
>   Running Boolean_Guards1/test.desc 

Bug#1069442: haskell-github: FTBFS on armhf: unsatisfiable build-dependencies

2024-04-20 Thread Lucas Nussbaum
Source: haskell-github
Version: 0.28.0.1-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-armhf

Hi,

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


Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: cdbs, debhelper (>= 10), haskell-devscripts (>= 0.15), 
> ghc (>= 9.4), ghc-prof, libghc-aeson-dev, libghc-aeson-prof, 
> libghc-base-compat-dev (>= 0.11.1), libghc-base-compat-dev (<< 0.13), 
> libghc-base-compat-prof, libghc-base16-bytestring-dev (>= 0.1.1.6), 
> libghc-base16-bytestring-dev (<< 1.1), libghc-base16-bytestring-prof, 
> libghc-binary-instances-dev (>= 1), libghc-binary-instances-dev (<< 1.1), 
> libghc-binary-instances-prof, libghc-cryptohash-sha1-dev (>= 0.11.100.1), 
> libghc-cryptohash-sha1-dev (<< 0.12), libghc-cryptohash-sha1-prof, 
> libghc-deepseq-generics-dev (>= 0.2.0.0), libghc-deepseq-generics-dev (<< 
> 0.3), libghc-deepseq-generics-prof, libghc-exceptions-dev (>= 0.10.2), 
> libghc-exceptions-dev (<< 0.11), libghc-exceptions-prof, libghc-hashable-dev 
> (>= 1.2.7.0), libghc-hashable-dev (<< 1.5), libghc-hashable-prof, 
> libghc-http-client-dev (>= 0.5.12), libghc-http-client-dev (<< 0.8), 
> libghc-http-client-prof, libghc-http-client-tls-dev (>= 0.3.5.3), 
> libghc-http-client-tls-dev (<< 0.4), libghc-http-client-tls-prof, 
> libghc-http-link-header-dev (>= 1.0.3.1), libghc-http-link-header-dev (<< 
> 1.3), libghc-http-link-header-prof, libghc-http-types-dev (>= 0.12.3), 
> libghc-http-types-dev (<< 0.13), libghc-http-types-prof, 
> libghc-iso8601-time-dev (>= 0.1.5), libghc-iso8601-time-dev (<< 0.2), 
> libghc-iso8601-time-prof, libghc-network-uri-dev (>= 2.6.1.0), 
> libghc-network-uri-dev (<< 2.7), libghc-network-uri-prof, libghc-tagged-dev 
> (>= 0.8.5), libghc-tagged-dev (<< 0.9), libghc-tagged-prof, 
> libghc-time-compat-dev (>= 1.9.2.2), libghc-time-compat-dev (<< 1.10), 
> libghc-time-compat-prof, libghc-tls-dev (>= 1.4.1), libghc-tls-prof, 
> libghc-transformers-compat-dev (>= 0.6.5), libghc-transformers-compat-dev (<< 
> 0.8), libghc-transformers-compat-prof, libghc-unordered-containers-dev (>= 
> 0.2.10.0), libghc-unordered-containers-dev (<< 0.3), 
> libghc-unordered-containers-prof, libghc-vector-dev (>= 0.12.0.1), 
> libghc-vector-dev (<< 0.14), libghc-vector-prof, libghc-file-embed-dev, 
> libghc-file-embed-prof, libghc-hspec-dev (>= 2.6.1), libghc-hspec-dev (<< 
> 2.11), libghc-hspec-prof, hspec-discover (>= 2.7.1), hspec-discover (<< 
> 2.11), build-essential, fakeroot, ghc-doc, libghc-aeson-doc, 
> libghc-base-compat-doc, libghc-base16-bytestring-doc, 
> libghc-binary-instances-doc, libghc-cryptohash-sha1-doc, 
> libghc-deepseq-generics-doc, libghc-exceptions-doc, libghc-hashable-doc, 
> libghc-http-client-doc, libghc-http-client-tls-doc, 
> libghc-http-link-header-doc, libghc-http-types-doc, libghc-iso8601-time-doc, 
> libghc-network-uri-doc, libghc-tagged-doc, libghc-time-compat-doc, 
> libghc-tls-doc, libghc-transformers-compat-doc, 
> libghc-unordered-containers-doc, libghc-vector-doc
> Filtered Build-Depends: cdbs, debhelper (>= 10), haskell-devscripts (>= 
> 0.15), ghc (>= 9.4), ghc-prof, libghc-aeson-dev, libghc-aeson-prof, 
> libghc-base-compat-dev (>= 0.11.1), libghc-base-compat-dev (<< 0.13), 
> libghc-base-compat-prof, libghc-base16-bytestring-dev (>= 0.1.1.6), 
> libghc-base16-bytestring-dev (<< 1.1), libghc-base16-bytestring-prof, 
> libghc-binary-instances-dev (>= 1), libghc-binary-instances-dev (<< 1.1), 
> libghc-binary-instances-prof, libghc-cryptohash-sha1-dev (>= 0.11.100.1), 
> libghc-cryptohash-sha1-dev (<< 0.12), libghc-cryptohash-sha1-prof, 
> libghc-deepseq-generics-dev (>= 0.2.0.0), libghc-deepseq-generics-dev (<< 
> 0.3), libghc-deepseq-generics-prof, libghc-exceptions-dev (>= 0.10.2), 
> libghc-exceptions-dev (<< 0.11), libghc-exceptions-prof, libghc-hashable-dev 
> (>= 1.2.7.0), libghc-hashable-dev (<< 1.5), libghc-hashable-prof, 
> libghc-http-client-dev (>= 0.5.12), libghc-http-client-dev (<< 0.8), 
> libghc-http-client-prof, libghc-http-client-tls-dev (>= 0.3.5.3), 
> libghc-http-client-tls-dev (<< 0.4), libghc-http-client-tls-prof, 
> libghc-htt

Bug#1069443: haskell-crypton-x509-validation: FTBFS on armhf: unsatisfiable build-dependencies: libghc-asn1-encoding-dev-0.9.6-4f999, libghc-asn1-types-dev-0.3.4-aa235, libghc-base-dev-4.17.2.0-38dbb,

2024-04-20 Thread Lucas Nussbaum
Source: haskell-crypton-x509-validation
Version: 1.6.12-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-armhf

Hi,

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


Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper (>= 10), haskell-devscripts (>= 0.13), cdbs, 
> ghc (>= 9.4), ghc-prof, libghc-asn1-encoding-dev (>= 0.9), 
> libghc-asn1-encoding-dev (<< 0.10), libghc-asn1-encoding-prof, 
> libghc-asn1-types-dev (>= 0.3), libghc-asn1-types-dev (<< 0.4), 
> libghc-asn1-types-prof, libghc-crypton-dev (>= 0.24), libghc-crypton-prof, 
> libghc-crypton-x509-dev (>= 1.7.5), libghc-crypton-x509-prof, 
> libghc-crypton-x509-store-dev (>= 1.6), libghc-crypton-x509-store-prof, 
> libghc-data-default-class-dev, libghc-data-default-class-prof, 
> libghc-hourglass-dev, libghc-hourglass-prof, libghc-memory-dev, 
> libghc-memory-prof, libghc-pem-dev (>= 0.1), libghc-pem-prof, 
> libghc-tasty-dev, libghc-tasty-prof, libghc-tasty-hunit-dev, 
> libghc-tasty-hunit-prof, build-essential, fakeroot, ghc-doc, 
> libghc-asn1-encoding-doc, libghc-asn1-types-doc, libghc-crypton-doc, 
> libghc-crypton-x509-doc, libghc-crypton-x509-store-doc, 
> libghc-data-default-class-doc, libghc-hourglass-doc, libghc-memory-doc, 
> libghc-pem-doc
> Filtered Build-Depends: debhelper (>= 10), haskell-devscripts (>= 0.13), 
> cdbs, ghc (>= 9.4), ghc-prof, libghc-asn1-encoding-dev (>= 0.9), 
> libghc-asn1-encoding-dev (<< 0.10), libghc-asn1-encoding-prof, 
> libghc-asn1-types-dev (>= 0.3), libghc-asn1-types-dev (<< 0.4), 
> libghc-asn1-types-prof, libghc-crypton-dev (>= 0.24), libghc-crypton-prof, 
> libghc-crypton-x509-dev (>= 1.7.5), libghc-crypton-x509-prof, 
> libghc-crypton-x509-store-dev (>= 1.6), libghc-crypton-x509-store-prof, 
> libghc-data-default-class-dev, libghc-data-default-class-prof, 
> libghc-hourglass-dev, libghc-hourglass-prof, libghc-memory-dev, 
> libghc-memory-prof, libghc-pem-dev (>= 0.1), libghc-pem-prof, 
> libghc-tasty-dev, libghc-tasty-prof, libghc-tasty-hunit-dev, 
> libghc-tasty-hunit-prof, build-essential, fakeroot, ghc-doc, 
> libghc-asn1-encoding-doc, libghc-asn1-types-doc, libghc-crypton-doc, 
> libghc-crypton-x509-doc, libghc-crypton-x509-store-doc, 
> libghc-data-default-class-doc, libghc-hourglass-doc, libghc-memory-doc, 
> libghc-pem-doc
> dpkg-deb: building package 'sbuild-build-depends-main-dummy' in 
> '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'.
> Ign:1 copy:/<>/apt_archive ./ InRelease
> Get:2 copy:/<>/apt_archive ./ Release [615 B]
> Ign:3 copy:/<>/apt_archive ./ Release.gpg
> Get:4 copy:/<>/apt_archive ./ Sources [1562 B]
> Get:5 copy:/<>/apt_archive ./ Packages [1572 B]
> Fetched 3749 B in 0s (0 B/s)
> Reading package lists...
> Reading package lists...
> 
> Install main build dependencies (apt-based resolver)
> 
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  libghc-crypton-x509-store-dev : Depends: 
> libghc-asn1-encoding-dev-0.9.6-4f999 but it is not installable
>  Depends: libghc-asn1-types-dev-0.3.4-aa235 
> but it is not installable
>  Depends: libghc-base-dev-4.17.2.0-38dbb but 
> it is not installable
>  Depends: 
> libghc-bytestring-dev-0.11.5.2-302b4 but it is not installable
>  Depends: libghc-containers-dev-0.6.7-e92e7 
> but it is not installable
>  Depends: libghc-crypton-dev-0.33-57ec1 but 
> it is not installable
>  Depends: libghc-crypton-x509-dev-1.7.6-e20c2 
> but it is not installable
>  Depends: libghc-directory-dev-1.3.7.1-a6844 
> but it is not installable
> 

Bug#1069427: macaulay2: FTBFS on armhf: make[4]: *** [Makefile:50: check-ForeignFunctions] Error 1

2024-04-20 Thread Lucas Nussbaum
Source: macaulay2
Version: 1.23+ds-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-armhf

Hi,

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


Relevant part (hopefully):
> make[4]: Entering directory '/<>/M2/Macaulay2/packages'
> /<>/M2/usr-dist/arm-Linux-Debian-trixie/bin/M2 -q --no-preload 
> --stop --silent -e 
> "needsPackage(\"A1BrouwerDegrees\",LoadDocumentation=>true,DebuggingMode=>true)"
>  -e "debug Core; argumentMode = defaultMode - SetUlimit" -e 
> "check(A1BrouwerDegrees,UserMode=>false,Verbose=>true); exit 0"
>  -- capturing check(0, "A1BrouwerDegrees") -- 0.064957 seconds elapsed
>  -- capturing check(1, "A1BrouwerDegrees") -- 0.051603 seconds elapsed
>  -- capturing check(2, "A1BrouwerDegrees") -- 0.0515675 seconds elapsed
>  -- capturing check(3, "A1BrouwerDegrees") -- 0.0518611 seconds elapsed
>  -- capturing check(4, "A1BrouwerDegrees") -- 0.068952 seconds elapsed
>  -- capturing check(5, "A1BrouwerDegrees") -- 1.3053 seconds elapsed
>  -- capturing check(6, "A1BrouwerDegrees") -- 0.49588 seconds elapsed
>  -- capturing check(7, "A1BrouwerDegrees") -- 0.0648761 seconds elapsed
>  -- capturing check(8, "A1BrouwerDegrees") -- 0.0538004 seconds elapsed
>  -- capturing check(9, "A1BrouwerDegrees") -- 0.0688976 seconds elapsed
>  -- capturing check(10, "A1BrouwerDegrees") -- 0.0527598 seconds elapsed
>  -- capturing check(11, "A1BrouwerDegrees") -- 0.0523495 seconds elapsed
>  -- capturing check(12, "A1BrouwerDegrees") -- 0.0530973 seconds elapsed
>  -- capturing check(13, "A1BrouwerDegrees") -- 0.055945 seconds elapsed
>  -- capturing check(14, "A1BrouwerDegrees") -- 0.0559745 seconds elapsed
>  -- capturing check(15, "A1BrouwerDegrees") -- 0.0528307 seconds elapsed
>  -- capturing check(16, "A1BrouwerDegrees") -- 0.0529872 seconds elapsed
>  -- capturing check(17, "A1BrouwerDegrees") -- 0.197972 seconds elapsed
>  -- capturing check(18, "A1BrouwerDegrees") -- 0.0558728 seconds elapsed
>  -- capturing check(19, "A1BrouwerDegrees") -- 0.0593129 seconds elapsed
>  -- capturing check(20, "A1BrouwerDegrees") -- 0.0567781 seconds elapsed
>  -- capturing check(21, "A1BrouwerDegrees") -- 0.0823121 seconds elapsed
>  -- capturing check(22, "A1BrouwerDegrees") -- 0.230908 seconds elapsed
>  -- capturing check(23, "A1BrouwerDegrees") -- 0.0992073 seconds elapsed
>  -- capturing check(24, "A1BrouwerDegrees") -- 0.105262 seconds elapsed
>  -- capturing check(25, "A1BrouwerDegrees") -- 0.0836578 seconds elapsed
> /<>/M2/usr-dist/arm-Linux-Debian-trixie/bin/M2 -q --no-preload 
> --stop --silent -e 
> "needsPackage(\"AInfinity\",LoadDocumentation=>true,DebuggingMode=>true)" -e 
> "debug Core; argumentMode = defaultMode - SetUlimit" -e 
> "check(AInfinity,UserMode=>false,Verbose=>true); exit 0"
>  -- capturing check(0, "AInfinity") -- 0.0934688 seconds elapsed
>  -- capturing check(1, "AInfinity") -- 0.232416 seconds elapsed
>  -- capturing check(2, "AInfinity") -- 0.0930997 seconds elapsed
>  -- capturing check(3, "AInfinity") -- 0.832918 seconds elapsed
>  -- capturing check(4, "AInfinity") -- 0.538569 seconds elapsed
>  -- capturing check(5, "AInfinity") -- 0.158406 seconds elapsed
>  -- capturing check(6, "AInfinity") -- 0.24989 seconds elapsed
>  -- capturing check(7, "AInfinity") -- 0.184067 seconds elapsed
>  -- capturing check(8, "AInfinity") -- 0.0981422 seconds elapsed
>  -- capturing check(9, "AInfinity") -- 0.111479 seconds elapsed
>  -- capturing check(10, "AInfinity") -- 0.0949508 seconds elapsed
>  -- capturing check(11, "AInfinity") -- 0.127091 seconds elapsed
>  -- capturing check(12, "AInfinity") -- 2.88281 seconds elapsed
>  -- capturing check(13, "AInfinity") -- 2.90833 seconds elapsed
>  -- capturing check(14, "AInfinity") -- 4.25407 seconds elapsed
> /<>/M2/usr-dist/arm-Linux-Debian-trixie/bin/M2 -q --no-preload 
> --stop --silent -e 
> "needsPackage(\"AbstractToricVarieties\",LoadDocumentation=>true,DebuggingMode=>true)"
>  -e "debug Core; argumentMode = defaultMode - SetUlimit" -e 
> "check(AbstractToricVarieties,UserMode=>false,Verbose=>true); exit 0"
>  -- warning: AbstractToricVarieties has no tests
> /<&g

Bug#1069429: dbcsr: FTBFS on armhf: tests fail

2024-04-20 Thread Lucas Nussbaum
Source: dbcsr
Version: 2.6.0-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-armhf

Hi,

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


Relevant part (hopefully):
> make[2]: Entering directory '/<>/obj-arm-linux-gnueabihf'
> Running tests...
> /usr/bin/ctest --force-new-ctest-process --verbose -j1
> UpdateCTestConfiguration  from 
> :/<>/obj-arm-linux-gnueabihf/DartConfiguration.tcl
> Parse Config 
> file:/<>/obj-arm-linux-gnueabihf/DartConfiguration.tcl
> UpdateCTestConfiguration  from 
> :/<>/obj-arm-linux-gnueabihf/DartConfiguration.tcl
> Parse Config 
> file:/<>/obj-arm-linux-gnueabihf/DartConfiguration.tcl
> Test project /<>/obj-arm-linux-gnueabihf
> Constructing a list of tests
> Done constructing a list of tests
> Updating test list for fixtures
> Added 0 tests to meet fixture requirements
> Checking test dependency graph...
> Checking test dependency graph end
> test 1
>   Start  1: dbcsr_perf:inputs/test_H2O.perf
> 
> 1: Test command: /usr/bin/mpiexec "-n" "2" 
> "/<>/obj-arm-linux-gnueabihf/tests/dbcsr_perf" 
> "/<>/tests/inputs/test_H2O.perf"
> 1: Working Directory: /<>/obj-arm-linux-gnueabihf/tests
> 1: Environment variables: 
> 1:  OMP_NUM_THREADS=2
> 1: Test timeout computed to be: 1500
> 1: --
> 1: Sorry!  You were supposed to get help about:
> 1: pmix_init:startup:internal-failure
> 1: But I couldn't open the help file:
> 1: /usr/share/pmix/help-pmix-runtime.txt: No such file or directory.  
> Sorry!
> 1: --
> 1: [ip-10-84-234-46:3125887] PMIX ERROR: NOT-FOUND in file 
> ../../../../../../../../opal/mca/pmix/pmix3x/pmix/src/server/pmix_server.c at 
> line 237
>  1/19 Test  #1: dbcsr_perf:inputs/test_H2O.perf 
> ...***Failed0.02 sec
> --
> Sorry!  You were supposed to get help about:
> pmix_init:startup:internal-failure
> But I couldn't open the help file:
> /usr/share/pmix/help-pmix-runtime.txt: No such file or directory.  Sorry!
> --
> [ip-10-84-234-46:3125887] PMIX ERROR: NOT-FOUND in file 
> ../../../../../../../../opal/mca/pmix/pmix3x/pmix/src/server/pmix_server.c at 
> line 237
> 
> test 2
>   Start  2: dbcsr_perf:inputs/test_rect1_dense.perf
> 
> 2: Test command: /usr/bin/mpiexec "-n" "2" 
> "/<>/obj-arm-linux-gnueabihf/tests/dbcsr_perf" 
> "/<>/tests/inputs/test_rect1_dense.perf"
> 2: Working Directory: /<>/obj-arm-linux-gnueabihf/tests
> 2: Environment variables: 
> 2:  OMP_NUM_THREADS=2
> 2: Test timeout computed to be: 1500
> 2: --
> 2: Sorry!  You were supposed to get help about:
> 2: pmix_init:startup:internal-failure
> 2: But I couldn't open the help file:
> 2: /usr/share/pmix/help-pmix-runtime.txt: No such file or directory.  
> Sorry!
> 2: --
> 2: [ip-10-84-234-46:3125888] PMIX ERROR: NOT-FOUND in file 
> ../../../../../../../../opal/mca/pmix/pmix3x/pmix/src/server/pmix_server.c at 
> line 237
>  2/19 Test  #2: dbcsr_perf:inputs/test_rect1_dense.perf 
> ...***Failed0.01 sec
> --
> Sorry!  You were supposed to get help about:
> pmix_init:startup:internal-failure
> But I couldn't open the help file:
> /usr/share/pmix/help-pmix-runtime.txt: No such file or directory.  Sorry!
> --
> [ip-10-84-234-46:3125888] PMIX ERROR: NOT-FOUND in file 
> ../../../../../../../../opal/mca/pmix/pmix3x/pmix/src/server/pmix_server.c at 
> line 237
> 
> test 3
>   Start  3: dbcsr_perf:inputs/test_rect1_sparse.perf
> 
> 3: Test command: /usr/bin/mpiexec "-n" "2" 
> "/<>/obj-arm-linux-gnueabihf/tests/dbcsr_perf" 
> "/<>/tests/inputs/test_rect1_sparse.perf"
> 3: Working Directory: /<>/obj-arm-linux-gnueabihf/tests
> 3: Environment variables: 
> 3:  OMP_NUM_THREADS=2
> 3: Test timeout computed to be: 1500
> 3: --
> 3: Sorry!  You were supposed to get help about:
> 3:  

Bug#1069440: olpc-kbdshim: FTBFS on armhf: common.c:342:24: error: ‘struct input_event’ has no member named ‘time’

2024-04-20 Thread Lucas Nussbaum
Source: olpc-kbdshim
Version: 27-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-armhf

Hi,

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


Relevant part (hopefully):
> cc -g -O2 -Werror=implicit-function-declaration 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -Wall -O2 -g 
> -DVERSION=27 -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 
> -Wdate-time -D_FORTIFY_SOURCE=2  -c -o olpc-kbdshim-udev.o olpc-kbdshim-udev.c
> common.c: In function ‘inject_uinput_event’:
> common.c:342:24: error: ‘struct input_event’ has no member named ‘time’
>   342 | gettimeofday(, NULL);
>   |^
> make[1]: *** [: common.o] Error 1


The full build log is available from:
http://qa-logs.debian.net/2024/04/20/olpc-kbdshim_27-2_unstable-armhf.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240420;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240420=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 mark 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.



Bug#1069441: pi-tm1638: FTBFS on armhf: configure: error: cannot run C compiled programs.

2024-04-20 Thread Lucas Nussbaum
Source: pi-tm1638
Version: 1.0-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-armhf

Hi,

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


Relevant part (hopefully):
> checking for gcc... gcc
> checking whether the C compiler works... yes
> checking for C compiler default output file name... a.out
> checking for suffix of executables... 
> checking whether we are cross compiling... configure: error: in 
> `/<>':
> configure: error: cannot run C compiled programs.
> If you meant to cross compile, use `--host'.
> See `config.log' for more details
>   tail -v -n \+0 config.log


The full build log is available from:
http://qa-logs.debian.net/2024/04/20/pi-tm1638_1.0-1_unstable-armhf.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240420;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240420=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 mark 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.



Bug#1069446: osmo-iuh: FTBFS on armhf: unsatisfiable build-dependencies: libosmo-netif-dev (>= 1.2.0), libosmo-sigtran-dev (>= 1.6.0)

2024-04-20 Thread Lucas Nussbaum
Source: osmo-iuh
Version: 1.3.0+dfsg1-6
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-armhf

Hi,

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


Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: dpkg-dev (>= 1.22.5), debhelper-compat (= 13), 
> pkg-config, autoconf, automake, libtool, osmo-libasn1c-dev (>= 0.9.30), 
> libsctp-dev, libosmocore-dev (>= 1.7.0), libosmo-netif-dev (>= 1.2.0), 
> libosmo-sigtran-dev (>= 1.6.0), python3, build-essential, fakeroot
> Filtered Build-Depends: dpkg-dev (>= 1.22.5), debhelper-compat (= 13), 
> pkg-config, autoconf, automake, libtool, osmo-libasn1c-dev (>= 0.9.30), 
> libsctp-dev, libosmocore-dev (>= 1.7.0), libosmo-netif-dev (>= 1.2.0), 
> libosmo-sigtran-dev (>= 1.6.0), python3, build-essential, fakeroot
> dpkg-deb: building package 'sbuild-build-depends-main-dummy' in 
> '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'.
> Ign:1 copy:/<>/apt_archive ./ InRelease
> Get:2 copy:/<>/apt_archive ./ Release [609 B]
> Ign:3 copy:/<>/apt_archive ./ Release.gpg
> Get:4 copy:/<>/apt_archive ./ Sources [823 B]
> Get:5 copy:/<>/apt_archive ./ Packages [855 B]
> Fetched 2287 B in 0s (0 B/s)
> Reading package lists...
> Reading package lists...
> 
> Install main build dependencies (apt-based resolver)
> 
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  sbuild-build-depends-main-dummy : Depends: libosmo-netif-dev (>= 1.2.0) but 
> it is not installable
>Depends: libosmo-sigtran-dev (>= 1.6.0) 
> but it is not installable
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.


The full build log is available from:
http://qa-logs.debian.net/2024/04/20/osmo-iuh_1.3.0+dfsg1-6_unstable-armhf.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240420;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240420=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 mark 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.



Bug#1069432: mpi4py: FTBFS on armhf: ld: cannot find -llmpe: No such file or directory

2024-04-20 Thread Lucas Nussbaum
Source: mpi4py
Version: 3.1.5-5
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-armhf

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_build override_dh_auto_build-arch -- \
>   --build-args "--mpicc=/usr/bin/mpicc --mpicxx=/usr/bin/mpicxx"
> I: pybuild base:311: /usr/bin/python3.12 setup.py build 
> --mpicc=/usr/bin/mpicc --mpicxx=/usr/bin/mpicxx
> running build
> running build_src
> running build_py
> creating /<>/.pybuild/cpython3_3.12/build/mpi4py
> copying src/mpi4py/bench.py -> 
> /<>/.pybuild/cpython3_3.12/build/mpi4py
> copying src/mpi4py/__main__.py -> 
> /<>/.pybuild/cpython3_3.12/build/mpi4py
> copying src/mpi4py/run.py -> 
> /<>/.pybuild/cpython3_3.12/build/mpi4py
> copying src/mpi4py/__init__.py -> 
> /<>/.pybuild/cpython3_3.12/build/mpi4py
> creating /<>/.pybuild/cpython3_3.12/build/mpi4py/futures
> copying src/mpi4py/futures/aplus.py -> 
> /<>/.pybuild/cpython3_3.12/build/mpi4py/futures
> copying src/mpi4py/futures/server.py -> 
> /<>/.pybuild/cpython3_3.12/build/mpi4py/futures
> copying src/mpi4py/futures/__main__.py -> 
> /<>/.pybuild/cpython3_3.12/build/mpi4py/futures
> copying src/mpi4py/futures/_core.py -> 
> /<>/.pybuild/cpython3_3.12/build/mpi4py/futures
> copying src/mpi4py/futures/_base.py -> 
> /<>/.pybuild/cpython3_3.12/build/mpi4py/futures
> copying src/mpi4py/futures/pool.py -> 
> /<>/.pybuild/cpython3_3.12/build/mpi4py/futures
> copying src/mpi4py/futures/__init__.py -> 
> /<>/.pybuild/cpython3_3.12/build/mpi4py/futures
> copying src/mpi4py/futures/_lib.py -> 
> /<>/.pybuild/cpython3_3.12/build/mpi4py/futures
> creating /<>/.pybuild/cpython3_3.12/build/mpi4py/util
> copying src/mpi4py/util/dtlib.py -> 
> /<>/.pybuild/cpython3_3.12/build/mpi4py/util
> copying src/mpi4py/util/pkl5.py -> 
> /<>/.pybuild/cpython3_3.12/build/mpi4py/util
> copying src/mpi4py/util/__init__.py -> 
> /<>/.pybuild/cpython3_3.12/build/mpi4py/util
> copying src/mpi4py/py.typed -> 
> /<>/.pybuild/cpython3_3.12/build/mpi4py
> copying src/mpi4py/bench.pyi -> 
> /<>/.pybuild/cpython3_3.12/build/mpi4py
> copying src/mpi4py/MPI.pyi -> 
> /<>/.pybuild/cpython3_3.12/build/mpi4py
> copying src/mpi4py/__init__.pyi -> 
> /<>/.pybuild/cpython3_3.12/build/mpi4py
> copying src/mpi4py/__main__.pyi -> 
> /<>/.pybuild/cpython3_3.12/build/mpi4py
> copying src/mpi4py/run.pyi -> 
> /<>/.pybuild/cpython3_3.12/build/mpi4py
> copying src/mpi4py/dl.pyi -> 
> /<>/.pybuild/cpython3_3.12/build/mpi4py
> copying src/mpi4py/MPI.pxd -> 
> /<>/.pybuild/cpython3_3.12/build/mpi4py
> copying src/mpi4py/libmpi.pxd -> 
> /<>/.pybuild/cpython3_3.12/build/mpi4py
> copying src/mpi4py/__init__.pxd -> 
> /<>/.pybuild/cpython3_3.12/build/mpi4py
> creating /<>/.pybuild/cpython3_3.12/build/mpi4py/include
> creating /<>/.pybuild/cpython3_3.12/build/mpi4py/include/mpi4py
> copying src/mpi4py/include/mpi4py/mpi4py.MPI_api.h -> 
> /<>/.pybuild/cpython3_3.12/build/mpi4py/include/mpi4py
> copying src/mpi4py/include/mpi4py/mpi4py.h -> 
> /<>/.pybuild/cpython3_3.12/build/mpi4py/include/mpi4py
> copying src/mpi4py/include/mpi4py/mpi4py.MPI.h -> 
> /<>/.pybuild/cpython3_3.12/build/mpi4py/include/mpi4py
> copying src/mpi4py/include/mpi4py/mpi4py.i -> 
> /<>/.pybuild/cpython3_3.12/build/mpi4py/include/mpi4py
> copying src/mpi4py/include/mpi4py/mpi.pxi -> 
> /<>/.pybuild/cpython3_3.12/build/mpi4py/include/mpi4py
> copying src/mpi4py/futures/pool.pyi -> 
> /<>/.pybuild/cpython3_3.12/build/mpi4py/futures
> copying src/mpi4py/futures/server.pyi -> 
> /<>/.pybuild/cpython3_3.12/build/mpi4py/futures
> copying src/mpi4py/futures/__init__.pyi -> 
> /<>/.pybuild/cpython3_3.12/build/mpi4py/futures
> copying src/mpi4py/futures/__main__.pyi -> 
> /<>/.pybuild/cpython3_3.12/build/mpi4py/futures
> copying src/mpi4py/futures/_lib.pyi -> 
> /<>/.pybuild/cpython3_3.12/build/mpi4py/futures
> copying src/mpi4py/futures/_core.pyi -> 
> /<>/.pybuild/cpython3_3.12/build/mpi4py/futures
> copying src/mpi4py/futures/aplus.pyi -> 
> /<>/.pybuild/cpython3_3.12/build/mpi4py/futures
> copying src/mpi4py/util/pkl5.pyi -> 
> /<>/.pybuild/cpython3_3.12/build/mpi4py/util
> copying src/mpi4py/util/__init__.pyi -> 
> /<>/.pybuild/cpython3

Bug#1069431: haskell-language-python: FTBFS on armhf: make: *** [/usr/share/cdbs/1/class/hlibrary.mk:170: build-haddock-stamp] Error 251

2024-04-20 Thread Lucas Nussbaum
Source: haskell-language-python
Version: 0.5.8-3
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-armhf

Hi,

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


Relevant part (hopefully):
>  debian/rules binary
> test -x debian/rules
> dh_testroot
> dh_prep 
> dh_installdirs -A 
> mkdir -p "."
> CDBS WARNING:DEB_DH_STRIP_ARGS is deprecated since 0.4.85
> CDBS WARNING:DEB_COMPRESS_EXCLUDE is deprecated since 0.4.85
> Adding cdbs dependencies to debian/libghc-language-python-doc.substvars
> dh_installdirs -plibghc-language-python-doc \
>   
> perl -d:Confess -MDebian::Debhelper::Buildsystem::Haskell::Recipes=/.*/ \
>   -E 'make_setup_recipe'
> Running ghc --make Setup.lhs -o debian/hlibrary.setup
> [1 of 2] Compiling Main ( Setup.lhs, Setup.o )
> [2 of 2] Linking debian/hlibrary.setup
> perl -d:Confess -MDebian::Debhelper::Buildsystem::Haskell::Recipes=/.*/ \
>   -E 'configure_recipe'
> Running find . ! -newer /tmp/AKWpIpugzx -exec touch -d 1998-01-01 UTC {} ;
> Running dh_listpackages
> libghc-language-python-dev
> libghc-language-python-prof
> libghc-language-python-doc
> Running dh_listpackages
> libghc-language-python-dev
> libghc-language-python-prof
> libghc-language-python-doc
> Running dpkg-buildflags --get LDFLAGS
> -Wl,-z,relro
> Running debian/hlibrary.setup configure --ghc -v2 
> --package-db=/var/lib/ghc/package.conf.d --prefix=/usr 
> --libdir=/usr/lib/haskell-packages/ghc/lib --libexecdir=/usr/lib 
> --builddir=dist-ghc --ghc-option=-optl-Wl,-z,relro 
> --haddockdir=/usr/lib/ghc-doc/haddock/language-python-0.5.8/ 
> --datasubdir=language-python 
> --htmldir=/usr/share/doc/libghc-language-python-doc/html/ 
> --enable-library-profiling
> Using Parsec parser
> Configuring language-python-0.5.8...
> Dependency array >=0.4 && <0.6: using array-0.5.4.0
> Dependency base >=4 && <5: using base-4.17.2.0
> Dependency containers >=0.5 && <0.7: using containers-0.6.7
> Dependency monads-tf >=0.1 && <0.2: using monads-tf-0.1.0.3
> Dependency pretty >=1.1 && <1.2: using pretty-1.1.3.6
> Dependency transformers >=0.3 && <0.6: using transformers-0.5.6.2
> Dependency utf8-string >=1 && <2: using utf8-string-1.0.2
> Source component graph: component lib
> Configured component graph:
> component language-python-0.5.8-DLZZSxX4Nul5PsKpOFHGxC
> include array-0.5.4.0
> include base-4.17.2.0
> include containers-0.6.7
> include monads-tf-0.1.0.3-3Kzwh8fOMiy7TegIbRdO0A
> include pretty-1.1.3.6
> include transformers-0.5.6.2
> include utf8-string-1.0.2-KqazO8nUWrDMJ2shK7HoQ
> Linked component graph:
> unit language-python-0.5.8-DLZZSxX4Nul5PsKpOFHGxC
> include array-0.5.4.0
> include base-4.17.2.0
> include containers-0.6.7
> include monads-tf-0.1.0.3-3Kzwh8fOMiy7TegIbRdO0A
> include pretty-1.1.3.6
> include transformers-0.5.6.2
> include utf8-string-1.0.2-KqazO8nUWrDMJ2shK7HoQ
> 
> Language.Python.Common=language-python-0.5.8-DLZZSxX4Nul5PsKpOFHGxC:Language.Python.Common,Language.Python.Common.AST=language-python-0.5.8-DLZZSxX4Nul5PsKpOFHGxC:Language.Python.Common.AST,Language.Python.Common.ParseError=language-python-0.5.8-DLZZSxX4Nul5PsKpOFHGxC:Language.Python.Common.ParseError,Language.Python.Common.ParserMonad=language-python-0.5.8-DLZZSxX4Nul5PsKpOFHGxC:Language.Python.Common.ParserMonad,Language.Python.Common.Pretty=language-python-0.5.8-DLZZSxX4Nul5PsKpOFHGxC:Language.Python.Common.Pretty,Language.Python.Common.PrettyAST=language-python-0.5.8-DLZZSxX4Nul5PsKpOFHGxC:Language.Python.Common.PrettyAST,Language.Python.Common.PrettyParseError=language-python-0.5.8-DLZZSxX4Nul5PsKpOFHGxC:Language.Python.Common.PrettyParseError,Language.Python.Common.PrettyToken=language-python-0.5.8-DLZZSxX4Nul5PsKpOFHGxC:Language.Python.Common.PrettyToken,Language.Python.Common.SrcLocation=language-python-0.5.8-DLZZSxX4Nul5PsKpOFHGxC:Language.Python.Common.SrcLocation,Language.Python.Common.StringEscape=language-python-0.5.8-DLZZSxX4Nul5PsKpOFHGxC:Language.Python.Common.StringEscape,Language.Python.Common.Token=language-python-0.5.8-DLZZSxX4Nul5PsKpOFHGxC:Language.Python.Common.Token,Language.Python.Version2=language-python-0.5.8-DLZZSxX4Nul5PsKpOFHGxC:Language.Python.Version2,Language.Python.Version2.Lexer=language-python-0.5.8-DLZZSxX4Nul5PsKpOFHGxC:Language.Python.Version2.Lexer,Language.Python.Version2.Parser=language-python-0.5.8-DLZZSxX4Nul5PsKpOFHGxC:Language.Python.Version2.Parser,Language.Python.Version3=language-python-0.5.8-DLZZSxX4Nul5PsKp

Bug#1069433: gtg-trace: FTBFS on armhf: tests fail

2024-04-20 Thread Lucas Nussbaum
Source: gtg-trace
Version: 0.2-3-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-armhf

Hi,

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


Relevant part (hopefully):
> make[2]: Entering directory '/<>/test'
> mkdir -p bin
> mpicc testState.c -o bin/testState -g -O2 
> -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -fstack-clash-protection -Wformat 
> -Werror=format-security -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 
> -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 -I../inc -Wl,-z,relro 
> -L../src/.libs -lgtg
> mpicc testEvent.c -o bin/testEvent -g -O2 
> -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -fstack-clash-protection -Wformat 
> -Werror=format-security -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 
> -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 -I../inc -Wl,-z,relro 
> -L../src/.libs -lgtg
> mpicc testLink.c -o bin/testLink -g -O2 -Werror=implicit-function-declaration 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -D_LARGEFILE_SOURCE 
> -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 
> -I../inc -Wl,-z,relro -L../src/.libs -lgtg
> mpicc testVar.c -o bin/testVar -g -O2 -Werror=implicit-function-declaration 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -D_LARGEFILE_SOURCE 
> -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 
> -I../inc -Wl,-z,relro -L../src/.libs -lgtg
> mpicc testAll.c -o bin/testAll -g -O2 -Werror=implicit-function-declaration 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -D_LARGEFILE_SOURCE 
> -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 
> -I../inc -Wl,-z,relro -L../src/.libs -lgtg
> mpicc testState_parall.c -o bin/testState_parall -g -O2 
> -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -fstack-clash-protection -Wformat 
> -Werror=format-security -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 
> -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 -I../inc -Wl,-z,relro 
> -L../src/.libs -lgtg
> mpicc testEvent_parall.c -o bin/testEvent_parall -g -O2 
> -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -fstack-clash-protection -Wformat 
> -Werror=format-security -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 
> -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 -I../inc -Wl,-z,relro 
> -L../src/.libs -lgtg
> mpicc testEvent_mpi.c -o bin/testEvent_mpi -g -O2 
> -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -fstack-clash-protection -Wformat 
> -Werror=format-security -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 
> -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 -I../inc -Wl,-z,relro 
> -L../src/.libs -lgtg
> for i in testState testEvent testLink testVar testAll ; do \
>   for type in 1 2 ; do \
>   echo running $i $type ; \
>   bin/$i $type ; \
>   done ; \
> done
> running testState 1
> running testState 2
> running testEvent 1
> running testEvent 2
> running testLink 1
> running testLink 2
> running testVar 1
> running testVar 2
> running testAll 1
> running testAll 2
> for i in testState_parall testEvent_parall testEvent_mpi ; do \
>   for type in 1 ; do \
>   echo running $i $type ; \
>   mpirun --host localhost:6 -np 6 bin/$i $type ; \
>   done ; \
> done
> running testState_parall 1
> --
> Sorry!  You were supposed to get help about:
> pmix_init:startup:internal-failure
> But I couldn't open the help file:
> /usr/share/pmix/help-pmix-runtime.txt: No such file or directory.  Sorry!
> --
> [ip-10-84-234-251:1132190] PMIX ERROR: NOT-FOUND in file 
> ../../../../../../../../opal/mca/pmix/pmix3x/pmix/src/server/pmix_server.c at 
> line 237
> running testEvent_parall 1
> --
> Sorry!  You were supposed to get help about:
> pmix_init:startup:internal-failure
> But I couldn't open the help file:
> /usr/share/pmix/help-pmix-runtime.txt: No such file or directory.  Sorry!
> --
> [ip-10-84-234-251:1132191] PMIX ERROR: NOT-FOUND in file

Bug#1069435: olpc-powerd: FTBFS on armhf: olpc-switchd.c:311:14: error: ‘struct input_event’ has no member named ‘time’

2024-04-20 Thread Lucas Nussbaum
Source: olpc-powerd
Version: 23-4
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-armhf

Hi,

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


Relevant part (hopefully):
> cc -Wall -O2 -g -DVERSION=23 -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 
> -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 -Wl,-z,relro  pnmto565fb.c   
> -o pnmto565fb
> pnmto565fb.c: In function ‘showimage’:
> pnmto565fb.c:374:5: warning: implicit declaration of function ‘readahead’ 
> [-Wimplicit-function-declaration]
>   374 | readahead(fd, 0, sb.st_size);
>   | ^
> olpc-switchd.c: In function ‘round_secs’:
> olpc-switchd.c:311:14: error: ‘struct input_event’ has no member named ‘time’
>   311 | return ev->time.tv_sec + ((ev->time.tv_usec > 50) ? 1 : 0);
>   |  ^~
> olpc-switchd.c:311:34: error: ‘struct input_event’ has no member named ‘time’
>   311 | return ev->time.tv_sec + ((ev->time.tv_usec > 50) ? 1 : 0);
>   |  ^~
> olpc-switchd.c: In function ‘power_button_event’:
> olpc-switchd.c:323:11: error: ‘struct input_event’ has no member named ‘time’
>   323 | ev->time.tv_sec, ev->time.tv_usec,
>   |   ^~
> olpc-switchd.c:323:28: error: ‘struct input_event’ has no member named ‘time’
>   323 | ev->time.tv_sec, ev->time.tv_usec,
>   |^~
> pnmto565fb.c:312:25: warning: variable ‘rightfillcols’ set but not used 
> [-Wunused-but-set-variable]
>   312 | int bottomfillrows, rightfillcols;
>   | ^
> olpc-switchd.c: In function ‘lid_event’:
> olpc-switchd.c:339:11: error: ‘struct input_event’ has no member named ‘time’
>   339 | ev->time.tv_sec, ev->time.tv_usec,
>   |   ^~
> olpc-switchd.c:339:28: error: ‘struct input_event’ has no member named ‘time’
>   339 | ev->time.tv_sec, ev->time.tv_usec,
>   |^~
> olpc-switchd.c: In function ‘ebook_event’:
> olpc-switchd.c:359:11: error: ‘struct input_event’ has no member named ‘time’
>   359 | ev->time.tv_sec, ev->time.tv_usec,
>   |   ^~
> olpc-switchd.c:359:28: error: ‘struct input_event’ has no member named ‘time’
>   359 | ev->time.tv_sec, ev->time.tv_usec,
>   |^~
> olpc-switchd.c: In function ‘acpwr_event’:
> olpc-switchd.c:379:11: error: ‘struct input_event’ has no member named ‘time’
>   379 | ev->time.tv_sec, ev->time.tv_usec,
>   |   ^~
> olpc-switchd.c:379:28: error: ‘struct input_event’ has no member named ‘time’
>   379 | ev->time.tv_sec, ev->time.tv_usec,
>   |^~
> olpc-switchd.c: In function ‘round_secs’:
> olpc-switchd.c:312:1: warning: control reaches end of non-void function 
> [-Wreturn-type]
>   312 | }
>   | ^
> make[1]: *** [: olpc-switchd] Error 1


The full build log is available from:
http://qa-logs.debian.net/2024/04/20/olpc-powerd_23-4_unstable-armhf.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240420;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240420=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 mark 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.



Bug#1069434: jinput: FTBFS on armhf: [apply] /<>/plugins/linux/src/native/net_java_games_input_LinuxEventDevice.c:176:86: error: ‘struct input_event’ has no member named ‘time’

2024-04-20 Thread Lucas Nussbaum
Source: jinput
Version: 20100502+dfsg-11
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-armhf

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> mkdir lib && cp /usr/share/java/jutils.jar lib
> ant simple_linux -Dlinux=true
> Buildfile: /<>/build.xml
> 
> init:
> 
> dist:
> 
> init:
> [mkdir] Created dir: /<>/coreAPI/apidocs
> [mkdir] Created dir: /<>/coreAPI/classes
> [mkdir] Created dir: /<>/coreAPI/bin
> [mkdir] Created dir: /<>/coreAPI/build
> 
> compile:
> [javac] /<>/coreAPI/build.xml:13: warning: 
> 'includeantruntime' was not set, defaulting to build.sysclasspath=last; set 
> to false for repeatable builds
> [javac] Using javac -source 1.4 is no longer supported, switching to 7
> [javac] Using javac -target 1.4 is no longer supported, switching to 7
> [javac] Compiling 21 source files to /<>/coreAPI/classes
> [javac] warning: [options] bootstrap class path not set in conjunction 
> with -source 7
> [javac] warning: [options] source value 7 is obsolete and will be removed 
> in a future release
> [javac] warning: [options] target value 7 is obsolete and will be removed 
> in a future release
> [javac] warning: [options] To suppress warnings about obsolete options, 
> use -Xlint:-options.
> [javac] 
> /<>/coreAPI/src/java/net/java/games/input/ControllerEnvironment.java:42:
>  warning: [removal] AccessController in java.security has been deprecated and 
> marked for removal
> [javac] import java.security.AccessController;
> [javac] ^
> [javac] 
> /<>/coreAPI/src/java/net/java/games/input/DefaultControllerEnvironment.java:45:
>  warning: [removal] AccessController in java.security has been deprecated and 
> marked for removal
> [javac] import java.security.AccessController;
> [javac] ^
> [javac] 
> /<>/coreAPI/src/java/net/java/games/input/DefaultControllerEnvironment.java:75:
>  warning: [removal] AccessController in java.security has been deprecated and 
> marked for removal
> [javac]   AccessController.doPrivileged(
> [javac]   ^
> [javac] 
> /<>/coreAPI/src/java/net/java/games/input/DefaultControllerEnvironment.java:89:
>  warning: [removal] AccessController in java.security has been deprecated and 
> marked for removal
> [javac]  return (String)AccessController.doPrivileged(new 
> PrivilegedAction() {
> [javac] ^
> [javac] 
> /<>/coreAPI/src/java/net/java/games/input/DefaultControllerEnvironment.java:98:
>  warning: [removal] AccessController in java.security has been deprecated and 
> marked for removal
> [javac]return (String)AccessController.doPrivileged(new 
> PrivilegedAction() {
> [javac]   ^
> [javac] 
> /<>/coreAPI/src/java/net/java/games/input/DefaultControllerEnvironment.java:126:
>  warning: [removal] AccessController in java.security has been deprecated and 
> marked for removal
> [javac] AccessController.doPrivileged(new PrivilegedAction() {
> [javac] ^
> [javac] 
> /<>/coreAPI/src/java/net/java/games/input/DefaultControllerEnvironment.java:160:
>  warning: [deprecation] newInstance() in Class has been deprecated
> [javac]   ControllerEnvironment 
> ce = (ControllerEnvironment) ceClass.newInstance();
> [javac]   
>   ^
> [javac]   where T is a type-variable:
> [javac] T extends Object declared in class Class
> [javac] 
> /<>/coreAPI/src/java/net/java/games/input/DefaultControllerEnvironment.java:210:
>  warning: [deprecation] newInstance() in Class has been deprecated
> [javac]   envClasses[i].newInstance();
> [javac]^
> [javac]   where T is a type-variable:
> [javac] T extends Object declared in class Class
> [javac] Note: Some input files use unchecked or unsafe operations.
> [javac] Note: Recompile with -Xlint:unchecked for details.
> [javac] 12 warnings
>  [copy] Copying 1 file to 
> /<>/coreAPI/build/src/java/net/java/games/input
> [javac] /<>/coreAPI/build.xml:28: warning: 
> 'includeantruntime' was not set, defaulting to build.sysclasspath=last; set 
> to false for repeatable build

Bug#1069436: checkinstall: FTBFS on armhf: cckxe2Ww.s:11565: Error: symbol `open64' is already defined

2024-04-20 Thread Lucas Nussbaum
Source: checkinstall
Version: 1.6.2+git20170426.d24a630-4
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-armhf

Hi,

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


Relevant part (hopefully):
> gcc -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time 
> -D_FORTIFY_SOURCE=2 -g -O2 -Werror=implicit-function-declaration 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -Wl,-z,relro -Wall 
> -c -g -D_GNU_SOURCE -DPIC -fPIC -D_REENTRANT -DVERSION=\"0.7.0beta7\" 
> installwatch.c
> installwatch.c: In function ‘instw_init’:
> installwatch.c:1232:17: warning: ignoring return value of ‘realpath’ declared 
> with attribute ‘warn_unused_result’ [-Wunused-result]
>  1232 | realpath(proot,wrkpath);
>   | ^~~
> installwatch.c:1351:17: warning: ignoring return value of ‘realpath’ declared 
> with attribute ‘warn_unused_result’ [-Wunused-result]
>  1351 | realpath(__instw.root,wrkpath);
>   | ^~
> installwatch.c:1369:25: warning: ignoring return value of ‘realpath’ declared 
> with attribute ‘warn_unused_result’ [-Wunused-result]
>  1369 | realpath(pexclude,wrkpath);
>   | ^~
> installwatch.c: In function ‘copy_path’:
> installwatch.c:778:33: warning: ignoring return value of ‘write’ declared 
> with attribute ‘warn_unused_result’ [-Wunused-result]
>   778 | write(translfd,buffer,bytes);
>   | ^~~~
> In file included from /usr/include/string.h:535,
>  from installwatch.c:45:
> In function ‘strcat’,
> inlined from ‘instw_setpath.isra’ at installwatch.c:1603:3:
> /usr/include/arm-linux-gnueabihf/bits/string_fortified.h:130:10: warning: 
> ‘__builtin___strcat_chk’ accessing 8195 or more bytes at offsets 8242 and 48 
> may overlap 1 byte at offset 8242 [-Wrestrict]
>   130 |   return __builtin___strcat_chk (__dest, __src, __glibc_objsize 
> (__dest));
>   |  
> ^~~~
> installwatch.c: In function ‘instw_setpath.isra’:
> installwatch.c:1649:17: warning: ‘__builtin_strncpy’ output may be truncated 
> copying 4096 bytes from a string of length 4096 [-Wstringop-truncation]
>  1649 | strncpy(instw->translpath,instw->truepath,PATH_MAX);
>   | ^
> In function ‘strncat’,
> inlined from ‘instw_setpath.isra’ at installwatch.c:1659:3:
> /usr/include/arm-linux-gnueabihf/bits/string_fortified.h:138:10: warning: 
> ‘__builtin___strncat_chk’ accessing 1 byte at offsets 12339 and 4145 may 
> overlap 1 byte at offset 12339 [-Wrestrict]
>   138 |   return __builtin___strncat_chk (__dest, __src, __len,
>   |  ^~
>   139 |   __glibc_objsize (__dest));
>   |   ~
> In function ‘strncat’,
> inlined from ‘instw_setpath.isra’ at installwatch.c:1671:2:
> /usr/include/arm-linux-gnueabihf/bits/string_fortified.h:138:10: warning: 
> ‘__builtin___strncat_chk’ accessing 1 byte at offsets 16440 and 4145 may 
> overlap 1 byte at offset 16440 [-Wrestrict]
>   138 |   return __builtin___strncat_chk (__dest, __src, __len,
>   |  ^~
>   139 |   __glibc_objsize (__dest));
>   |   ~
> installwatch.c: In function ‘instw_setpath.isra’:
> installwatch.c:1620:17: warning: ‘__builtin_strncpy’ output may be truncated 
> copying 4096 bytes from a string of length 4096 [-Wstringop-truncation]
>  1620 | strncpy(instw->reslvpath,instw->truepath,PATH_MAX);
>   | ^
> installwatch.c:1621:17: warning: ‘__builtin_strncpy’ output may be truncated 
> copying 4096 bytes from a string of length 4096 [-Wstringop-truncation]
>  1621 | strncpy(instw->translpath,instw->truepath,PATH_MAX);
>   | ^
> /tmp/cckxe2Ww.s: Assembler messages:
> /tmp/cckxe2Ww.s:11565: Error: symbol `open64' is already defined
> /tmp/cckxe2Ww.s:24205: Error: symbol `creat64' is already defined
> /tmp/cckxe2Ww.s:24578: Error: symbol `ftruncate64' is already defined
> /tmp/cckxe2Ww.s:24736: Error: symbol `fopen64' is already defined
> /tmp/cckxe2Ww.s:25191: Error: symbol `readdir64' is alread

Bug#1069439: arpack: FTBFS on armhf: make[6]: *** [Makefile:831: test-suite.log] Error 1

2024-04-20 Thread Lucas Nussbaum
Source: arpack
Version: 3.9.1-1.1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-armhf

Hi,

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


Relevant part (hopefully):
> make[6]: Entering directory '/<>/PARPACK/TESTS/MPI'
> FAIL: issue46
> FAIL: icb_parpack_c
> FAIL: icb_parpack_cpp
> 
> Testsuite summary for ARPACK-NG 3.9.1
> 
> # TOTAL: 3
> # PASS:  0
> # SKIP:  0
> # XFAIL: 0
> # FAIL:  3
> # XPASS: 0
> # ERROR: 0
> 
> See PARPACK/TESTS/MPI/test-suite.log
> Please report to https://github.com/opencollab/arpack-ng/issues/
> 
> make[6]: *** [Makefile:831: test-suite.log] Error 1


The full build log is available from:
http://qa-logs.debian.net/2024/04/20/arpack_3.9.1-1.1_unstable-armhf.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240420;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240420=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 mark 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.



Bug#1069445: h5py: FTBFS on armhf: tests fail

2024-04-20 Thread Lucas Nussbaum
Source: h5py
Version: 3.10.0-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-armhf

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> PYTHONPATH=/<>/.pybuild/cpython3_3.11_h5py_mpi/build mpirun -n 1 
> /usr/bin/make -C docs html
> --
> Sorry!  You were supposed to get help about:
> pmix_init:startup:internal-failure
> But I couldn't open the help file:
> /usr/share/pmix/help-pmix-runtime.txt: No such file or directory.  Sorry!
> --
> [ip-10-84-234-235:3065217] PMIX ERROR: NOT-FOUND in file 
> ../../../../../../../../opal/mca/pmix/pmix3x/pmix/src/server/pmix_server.c at 
> line 237
> make[1]: *** [debian/rules:112: execute_after_dh_auto_build-indep] Error 1


The full build log is available from:
http://qa-logs.debian.net/2024/04/20/h5py_3.10.0-1_unstable-armhf.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240420;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240420=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 mark 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.



Bug#1069437: libnginx-mod-http-set-misc: FTBFS on armhf: make: *** [debian/rules:6: binary] Error 25

2024-04-20 Thread Lucas Nussbaum
Source: libnginx-mod-http-set-misc
Version: 0.33-5
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-armhf

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/usr/share/nginx/src'
> cc -c -fPIC -g -O2 -Werror=implicit-function-declaration 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -g -O2 
> -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -fstack-clash-protection -Wformat 
> -Werror=format-security -fPIC -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 
> -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 -DNDK_SET_VAR 
> -DNDK_UPSTREAM_LIST -I src/core -I src/event -I src/event/modules -I 
> src/os/unix -I /usr/share/nginx-ndk/src/objs -I 
> /<>/obj-arm-linux-gnueabihf/addon/ndk -I 
> /<>/obj-arm-linux-gnueabihf -I src/http -I src/http/modules -I 
> src/http/v2 -I /usr/share/nginx-ndk/src/src -I /usr/share/nginx-ndk/src/src 
> -I /usr/share/nginx-ndk/src/objs -I 
> /<>/obj-arm-linux-gnueabihf/addon/ndk \
>   -o 
> /<>/obj-arm-linux-gnueabihf/addon/src/ngx_http_set_base32.o \
>   /<>/./src/ngx_http_set_base32.c
> cc -c -fPIC -g -O2 -Werror=implicit-function-declaration 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -g -O2 
> -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -fstack-clash-protection -Wformat 
> -Werror=format-security -fPIC -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 
> -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 -DNDK_SET_VAR 
> -DNDK_UPSTREAM_LIST -I src/core -I src/event -I src/event/modules -I 
> src/os/unix -I /usr/share/nginx-ndk/src/objs -I 
> /<>/obj-arm-linux-gnueabihf/addon/ndk -I 
> /<>/obj-arm-linux-gnueabihf -I src/http -I src/http/modules -I 
> src/http/v2 -I /usr/share/nginx-ndk/src/src -I /usr/share/nginx-ndk/src/src 
> -I /usr/share/nginx-ndk/src/objs -I 
> /<>/obj-arm-linux-gnueabihf/addon/ndk \
>   -o 
> /<>/obj-arm-linux-gnueabihf/addon/src/ngx_http_set_default_value.o
>  \
>   /<>/./src/ngx_http_set_default_value.c
> cc -c -fPIC -g -O2 -Werror=implicit-function-declaration 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -g -O2 
> -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -fstack-clash-protection -Wformat 
> -Werror=format-security -fPIC -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 
> -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 -DNDK_SET_VAR 
> -DNDK_UPSTREAM_LIST -I src/core -I src/event -I src/event/modules -I 
> src/os/unix -I /usr/share/nginx-ndk/src/objs -I 
> /<>/obj-arm-linux-gnueabihf/addon/ndk -I 
> /<>/obj-arm-linux-gnueabihf -I src/http -I src/http/modules -I 
> src/http/v2 -I /usr/share/nginx-ndk/src/src -I /usr/share/nginx-ndk/src/src 
> -I /usr/share/nginx-ndk/src/objs -I 
> /<>/obj-arm-linux-gnueabihf/addon/ndk \
>   -o 
> /<>/obj-arm-linux-gnueabihf/addon/src/ngx_http_set_hashed_upstream.o
>  \
>   /<>/./src/ngx_http_set_hashed_upstream.c
> cc -c -fPIC -g -O2 -Werror=implicit-function-declaration 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -g -O2 
> -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -fstack-clash-protection -Wformat 
> -Werror=format-security -fPIC -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 
> -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 -DNDK_SET_VAR 
> -DNDK_UPSTREAM_LIST -I src/core -I src/event -I src/event/modules -I 
> src/os/unix -I /usr/share/nginx-ndk/src/objs -I 
> /<>/obj-arm-linux-gnueabihf/addon/ndk -I 
> /<>/obj-arm-linux-gnueabihf -I src/http -I src/http/modules -I 
> src/http/v2 -I /usr/share/nginx-ndk/src/src -I /usr/share/nginx-ndk/src/src 
> -I /usr/share/nginx-ndk/src/objs -I 
> /<>/obj-arm-linux-gnueabihf/addon/ndk \
>   -o 
> /<>/obj-arm-linux-gnueabihf/addon/src/ngx_http_set_quote_sql.o \
>   /<>/./src/ngx_http_set_quote_sql.c
> cc -c -fPIC -g -O2 -Werror=implicit-function-declaration 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -g -O2 
> -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -fstack-clash-protection -Wformat 
> -Werror=format-security -fPIC -D_LARGEFILE_S

Bug#1069343: ITP: uart-devices -- Python library for managing UART devices on Linux

2024-04-20 Thread Jonas Smedegaard
Hi Edwards,

Quoting Edward Betts (2024-04-20 11:46:37)
> Package: wnpp
> Severity: wishlist
> Owner: Edward Betts 
> X-Debbugs-Cc: debian-de...@lists.debian.org, debian-pyt...@lists.debian.org
> 
> * Package name: uart-devices
>   Version : 0.1.0
>   Upstream Author : J. Nick Koston 
> * URL : https://github.com/bdraco/uart-devices
> * License : MIT
>   Programming Lang: Python
>   Description : Python library for managing UART devices on Linux
> 
>   uart-devices is a Python library designed to facilitate interaction with 
> UART
>   (Universal Asynchronous Receiver/Transmitter) devices on Linux systems. This
>   library provides developers with tools to manipulate UART hardware
>   programmatically, making it easier to integrate UART operations within 
> Python
>   applications.
> 
> I plan to maintain this package as part of the Python team.

If, as the above indicates, this is a Python _library_, then please
avoid occupying the global namespace "uart-devices" but instead also as
source package (not only binary package) use a python-specific prefix.

Concretely, I suggest to use "python-uart-devices" as name for the
source package, since that leaves room for the same source package
providing binary packages for both current major version 3 of Python,
and also other major versions and e.g. versions of pypy.

 - Jonas


-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/
 * Sponsorship: https://ko-fi.com/drjones

 [x] quote me freely  [ ] ask before reusing  [ ] keep private

signature.asc
Description: signature


Bug#1068136: Updating golang-github-golang-protobuf-1-5 to fix FTBFS

2024-04-20 Thread Mathias Gibbens
Hi Anthony,

  A few weeks ago you uploaded a new version of golang-google-protobuf
to unstable which caused a FTBFS in golang-github-golang-protobuf-1-5
v1.5.3 [1,2,3]. This has been blocking the transition of various golang
packages from unstable to testing.

  I've verified that v1.5.4 of golang-github-golang-protobuf-1-5 builds
fine on my amd64 system. `build-rdeps golang-github-golang-protobuf-1-
5-dev` identifies 219 rdeps in main, so I haven't kicked off a `ratt`
run testing for any build regressions with the newer version yet.

  Are you waiting on something specific before updating golang-github-
golang-protobuf-1-5?

Thanks,
Mathias

[1] -- https://qa.debian.org/excuses.php?package=golang-google-protobuf
[2] -- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068136
[3] -- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069368


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


Bug#1069565: Updating the gnome-pkg-tools Uploaders list

2024-04-20 Thread Boyuan Yang
Source: gnome-pkg-tools
Version: 0.22.9
Severity: minor
User: m...@qa.debian.org
Usertags: mia-teammaint

Gunnar Hjalmarsson  has retired [1][2].
Please remove them from the Uploaders list of the package.

Thank.

[1] https://nm.debian.org/person/gunnarhj/
[2] https://discourse.ubuntu.com/t/in-memoriam-gunnar-hjalmarsson/42284


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


Bug#1068324: lintian: patch-not-forwarded-upstream for upstream patches

2024-04-20 Thread Thorsten Glaser
Hi Nilesh,

>Right. AFAICS, lintian spews that warning because the header in that patch in
>incomplete. It also needs a "From" and "Subject" (which can be same as commit

this is not entirely correct.

The full patch header is:

Description: fix typeset -p confusion between empty and unset
Origin: commit:10065BC69BE555D6721

Description is the standard name for Subject (the same way
Author is the standard DEP 3 name for From), and it’s present,
and when Origin indicates an upstream commit (as shown here),
Author does not need to be present, per DEP 3.

bye,
//mirabilos
-- 
If Harry Potter gets a splitting headache in his scar
when he’s near Tom Riddle (aka Voldemort),
does Tom get pain in the arse when Harry is near him?
-- me, wondering why it’s not Jerry Potter………



Bug#1069566: Updating the gnome-settings-daemon Uploaders list

2024-04-20 Thread Boyuan Yang
Source: gnome-settings-daemon
Version: 46.0-1
Severity: minor
User: m...@qa.debian.org
Usertags: mia-teammaint

Gunnar Hjalmarsson  has retired [1][2].
Please remove them from the Uploaders list of the package.

Thank.

[1] https://nm.debian.org/person/gunnarhj/
[2] https://discourse.ubuntu.com/t/in-memoriam-gunnar-hjalmarsson/42284


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


Bug#1069568: ITP: python-hatch-mypyc -- Hatch build hook plugin for Mypyc

2024-04-20 Thread Michael R. Crusoe

Package: wnpp
Owner: Michael R. Crusoe 
Severity: wishlist

* Package name : python-hatch-mypyc
Version : 0.16.0
Upstream Author : Ofek Lev 
* URL : https://github.com/ofek/hatch-mypyc
* License : Expat
Programming Lang: Python
Description : Hatch build hook plugin for Mypyc
Provides a build hook plugin for Hatch build system for Python that compiles
code with Mypyc.

Remark: This package is Team Maintained by Michael R. Crusoe and the Debian 
Python Team at
https://salsa.debian.org/python-team/packages/python-hatch-mypyc



OpenPGP_signature.asc
Description: OpenPGP digital signature


Bug#1069533: sayonara: Please package new upstream version

2024-04-20 Thread Steve M
Is this not an issue that would prevent such an update for the time being?


This package is part of the ongoing testing transition known as auto-qtbase-
opensource-src. Please avoid uploads unrelated to this transition, they would
likely delay it and require supplementary work from the release managers. On the
other hand, if your package has problems preventing it to migrate to testing,
please fix them as soon as possible. You can probably find supplementary
information in the debian-release archives or in the corresponding
release.debian.org bug.

This package is part of the ongoing testing transition known as libglib2.0-
0t64. Please avoid uploads unrelated to this transition, they would likely delay
it and require supplementary work from the release managers. On the other hand,
if your package has problems preventing it to migrate to testing, please fix
them as soon as possible. You can probably find supplementary information in the
debian-release archives or in the corresponding release.debian.org bug.



Thanks
-Steve




On Sat, 2024-04-20 at 09:19 -0400, Boyuan Yang wrote:
> Source: sayonara
> Version: 1.8.0-beta1-1
> Tags: sid
> X-Debbugs-CC: kokoye2...@gmail.com s...@swm1.com
> 
> Dear Debian sayonara package maintainers,
> 
> A new upstream release of package sayonara was released in Jan 2024.
> Since you are listed as Debian package maintainers, please consider
> upgrading its Debian package. If you have any questions, please let
> me know.
> 
> Thanks,
> Boyuan Yang



Bug#1064293: less: CVE-2022-48624

2024-04-20 Thread P. J. McDermott
On 2024-04-20 at 16:19, Christoph Anton Mitterer wrote:
> On Sat, 2024-04-20 at 07:54 -0400, P. J. McDermott wrote:
> > Then the salvage procedure can play out for the full 28+ days
> > specified
> > by developers-reference (21 days to allow the maintainer to object
> > followed by a DELAYED/7 adoption upload).  I've already soft-proposed
> > to
> > salvage in bug #1069280 yesterday.  And as mentioned there I'm not
> > yet a
> > DD or DM, so I'd need to find a sponsor (and access to
> > debian/less.git).  
> 
> In the light of the recent XZ backdoor, wouldn't it generally be more
> desirable to get more co-maintainers, rather than replacing an existing
> one?

Sure, that's exactly the plan.  I don't intend to remove or prevent
anyone from co-maintaining src:less.  Note that my proposal to adopt,
co-maintain, or salvage (bug #1069280) said that I would keep the
current maintainer in Uploaders or Maintainer unless he requests
otherwise.  My intent is not to force out the existing maintainer,
but to help where he seems to have been too busy to properly maintain
src:less for at least two years.  (No shame in being busy, but it looks
like the package could use some help keeping up with new upstream
releases, security issues like these, etc.)

And the repository is already in the "debian" Salsa group (formerly
"collab-maint" on Alioth), where any DD can commit to it.  Also, if I
adopt or salvage src:less, I plan to allow low-threshold NMU[1].  Other
than that, I don't know of an appropriate team for it.

[1]: https://wiki.debian.org/LowThresholdNmu
-- 
Patrick "P. J." McDermott:  http://www.pehjota.net/
Lead Developer, ProteanOS:  http://www.proteanos.com/
Founder and CEO, Libiquity: http://www.libiquity.com/



Bug#1056898: pptpd: Build failures with ppp-2.5.0

2024-04-20 Thread Chris Boot

Control: severity -1 serious
Control: tags -1 ftbfs

On 26/11/2023 13:06, Christoph Biedl wrote:

Chris Boot wrote...

[...]

I'll upgrade the bug to RC when I upload ppp-2.5.0 to unstable.


Okay, just let me know when it's a good time to upload an updated
pptpd package.


Hi Christoph,

I've just uploaded 2.5.0-1+2 to unstable. Please upload your patched 
pptpd as soon as you can.


Thanks,
Chris

--
Chris Boot
bo...@debian.org



Bug#1069569: extra_system_ids setting does not work

2024-04-20 Thread Ian Jackson
Package: lvm2
Version: 2.03.11-2.1

root@recovery:~# lvcreate --config 'local/extra_system_id=["hub"]' -L 1G -n 
test -Z y hub-early-b
  Configuration setting "local/extra_system_id" unknown.
  Cannot access VG hub-early-b with system ID hub with local system ID recovery.
root@recovery:~# 

This is almost identical to the example from the lvmsystemid(7)
manpage, under "Overriding system ID".  I also tried the
"lvmlocal.conf" setting exhibited there, and that didn't work either.

I was able to work around the problem by setting "system_id_source" in
lvm.conf and setting and the system's hostname with hostname(8):

root@recovery:~# cat /etc/lvm/lvm.conf
global {
system_id_source = "uname"
}
root@recovery:~#

Ian.

-- 
Ian JacksonThese opinions are my own.  

Pronouns: they/he.  If I emailed you from @fyvzl.net or @evade.org.uk,
that is a private address which bypasses my fierce spamfilter.



Bug#1069570: tailscale: wrong use of format() ?

2024-04-20 Thread Alvaro Herrera
Package: tailscale
Version: 1.64.0
Severity: normal

Dear Maintainer,

I noticed that some log entries are malformed, in that the %-specifiers
are not expanded.  For example, today I see these lines in journalctl:

abr 20 18:12:14 schmee tailscaled[3288907]: [RATELIMIT] format("magicsock: %v 
active derp conns%s")
abr 20 18:12:14 schmee tailscaled[3288907]: [RATELIMIT] 
format("onPortUpdate(port=%v, network=%s)")
abr 20 18:12:33 schmee tailscaled[3288907]: [RATELIMIT] format("monitor: %s: 
src=%v, dst=%v, gw=%v, outif=%v, table=%v") (19 dropped)
abr 20 18:12:33 schmee tailscaled[3288907]: [RATELIMIT] format("magicsock: %v 
active derp conns%s") (1 dropped)
abr 20 18:12:33 schmee tailscaled[3288907]: [RATELIMIT] format("monitor: %s: 
src=%v, dst=%v, gw=%v, outif=%v, table=%v")
abr 20 18:12:34 schmee tailscaled[3288907]: [RATELIMIT] 
format("onPortUpdate(port=%v, network=%s)")
abr 20 18:12:35 schmee tailscaled[3288907]: [RATELIMIT] format("magicsock: %v 
active derp conns%s")
abr 20 18:12:38 schmee tailscaled[3288907]: [RATELIMIT] format("dns: Set: %v")

(This is a small snippet from "journalctl -u tailscaled | grep format", so
obviously there could be other lines that work in the same way).

Thanks!  I've generally found tailscale enormously useful, though I had
to mess with `ip rule` in order to make it work together with the PIA VPN.

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

Kernel: Linux 6.1.0-18-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN
Locale: LANG=es_CL.UTF-8, LC_CTYPE=es_CL.UTF-8 (charmap=UTF-8), 
LANGUAGE=es_CL:es
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages tailscale depends on:
ii  iptables  1.8.9-2

Versions of packages tailscale recommends:
ii  iproute2   6.1.0-3
ii  tailscale-archive-keyring  1.35.181

tailscale suggests no packages.

-- no debconf information



Bug#990264: ksh: output error is not checked for some builtins

2024-04-20 Thread Vincent Lefevre
Control: reassign -1 ksh93u+m
Control: found -1 1.0.4-3
Control: found -1 1.0.8-1
Control: tag -1 upstream
Control: forwarded -1 https://github.com/ksh93/ksh/issues/313

Forgot the "Control:".

Also: note the reassign due to the package rename of ksh to ksh93u+m
in September 2021. 1.0.4-3 is the current stable, and 1.0.8-1 the
current unstable version.

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



Bug#1069350: netavark: FTBFS on arm64: dh_auto_test: error: /usr/share/cargo/bin/cargo build returned exit code 101

2024-04-20 Thread Lucas Nussbaum
Source: netavark
Version: 1.4.0-4
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-arm64

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> printf '{"package":"%s","files":{}}\n' $(sha256sum Cargo.toml | grep -Po 
> '^\S+') > debian/cargo-checksum.json;
> make[1]: Leaving directory '/<>'
>dh_auto_configure -O--buildsystem=cargo
> debian cargo wrapper: options, profiles, parallel, lto: ['parallel=4'] [] 
> ['-j4'] 0
> debian cargo wrapper: rust_type, gnu_type: aarch64-unknown-linux-gnu, 
> aarch64-linux-gnu
> debian cargo wrapper: linking /usr/share/cargo/registry/* into 
> /<>/debian/cargo_registry/
>dh_auto_build -O--buildsystem=cargo
>dh_auto_test -O--buildsystem=cargo
> debian cargo wrapper: options, profiles, parallel, lto: ['parallel=4'] [] 
> ['-j4'] 0
> debian cargo wrapper: rust_type, gnu_type: aarch64-unknown-linux-gnu, 
> aarch64-linux-gnu
> debian cargo wrapper: running subprocess (['env', 'RUST_BACKTRACE=1', 
> '/usr/bin/cargo', '-Zavoid-dev-deps', 'build', '--verbose', '--verbose', 
> '-j4', '--target', 'aarch64-unknown-linux-gnu'],) {}
> error: failed to select a version for the requirement `sysctl = "^0.4"`
> candidate versions found which didn't match: 0.5.5
> location searched: directory source `/<>/debian/cargo_registry` 
> (which is replacing registry `crates-io`)
> required by package `netavark v1.4.0 (/<>)`
> perhaps a crate was updated and forgotten to be re-vendored?
> dh_auto_test: error: /usr/share/cargo/bin/cargo build returned exit code 101


The full build log is available from:
http://qa-logs.debian.net/2024/04/20/netavark_1.4.0-4_unstable-arm64.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240420;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240420=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 mark 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.



Bug#1069367: qemu: FTBFS on arm64: build-dependency not installable: gcc-powerpc64-linux-gnu

2024-04-20 Thread Michael Tokarev

Control: tag -1 + moreinfo
Control: found -1 1:4.2-2

20.04.2024 15:11, Lucas Nussbaum wrote:

Source: qemu
Version: 1:8.2.2+ds-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-arm64




  sbuild-build-depends-main-dummy : Depends: gcc-powerpc64-linux-gnu but it is 
not installable
E: Unable to correct problems, you have held broken packages.


I don't understand what are you suggesting to do here.

Should I disable all foreign compilers and code in qemu?  This way,
qemu will be nearly useless.

Or should you perhaps file a bug against gcc to provide powerpc64 
cross-compilers
for arm64?  If it's this variant, why are you filing this bug report against 
qemu?

Thanks,

/mjt



Bug#1066396: lftp: diff for NMU version 4.9.2-2.1

2024-04-20 Thread Andreas Metzler
Control: tags 1066396 + pending

Dear maintainer,

I've prepared an NMU for lftp (versioned as 4.9.2-2.1) and uploaded it
to unstable. This the implements the minimal fix I sent to this bug
almost a month ago.

cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'
diff -Nru lftp-4.9.2/debian/changelog lftp-4.9.2/debian/changelog
--- lftp-4.9.2/debian/changelog	2022-07-16 12:24:04.0 +0200
+++ lftp-4.9.2/debian/changelog	2024-04-20 14:28:35.0 +0200
@@ -1,3 +1,14 @@
+lftp (4.9.2-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Minimal change to fix FTBFS with -Werror=implicit-function-declaration
++ ftbfs_implicit.diff - Fixup configure*.
++ Use selective touch in debian/rules to allow changing configure*
+  without using dh_autoreconf.
+Closes: #1066396
+
+ -- Andreas Metzler   Sat, 20 Apr 2024 14:28:35 +0200
+
 lftp (4.9.2-2) unstable; urgency=medium
 
   * lftp.tech domain doesn't work anymore; switch back to lftp.yar.ru
diff -Nru lftp-4.9.2/debian/patches/ftbfs_implicit.diff lftp-4.9.2/debian/patches/ftbfs_implicit.diff
--- lftp-4.9.2/debian/patches/ftbfs_implicit.diff	1970-01-01 01:00:00.0 +0100
+++ lftp-4.9.2/debian/patches/ftbfs_implicit.diff	2024-04-20 14:24:10.0 +0200
@@ -0,0 +1,20 @@
+--- lftp-4.9.2.orig/configure
 lftp-4.9.2/configure
+@@ -57429,6 +57429,7 @@ else
+   cat confdefs.h - <<_ACEOF >conftest.$ac_ext
+ /* end confdefs.h.  */
+ 
++	#include 
+ 	 int main()
+ 	 {
+ 	unsigned long long x=0,x1;
+--- lftp-4.9.2.orig/m4/needtrio.m4
 lftp-4.9.2/m4/needtrio.m4
+@@ -9,6 +9,7 @@ AC_DEFUN([LFTP_NEED_TRIO],[
+   else
+ 
+   AC_RUN_IFELSE([AC_LANG_SOURCE([[
++	#include 
+ 	 int main()
+ 	 {
+ 	unsigned long long x=0,x1;
diff -Nru lftp-4.9.2/debian/patches/series lftp-4.9.2/debian/patches/series
--- lftp-4.9.2/debian/patches/series	2022-07-16 12:24:04.0 +0200
+++ lftp-4.9.2/debian/patches/series	2024-04-20 14:27:34.0 +0200
@@ -1,3 +1,4 @@
 config-dns-inet6_before_inet.patch
 lftp_sys-stdint-kfreebsd.patch
 lftp_gnutls_certificate_verify_peers2-verify_server_certificates.patch
+ftbfs_implicit.diff
diff -Nru lftp-4.9.2/debian/rules lftp-4.9.2/debian/rules
--- lftp-4.9.2/debian/rules	2018-09-17 09:33:33.0 +0200
+++ lftp-4.9.2/debian/rules	2024-04-20 14:27:19.0 +0200
@@ -19,6 +19,9 @@
 
 #configure: configure-stamp
 configure-stamp:
+	# Avoid autoconf rebuild due to patching input files.
+	touch --reference=aclocal.m4 configure m4/needtrio.m4
+	touch --reference=Makefile.am m4/needtrio.m4
 	dh_testdir
 	# Add here commands to configure the package.
 	CFLAGS="$(CFLAGS)" CXXFLAGS="$(CXXFLAGS)" CPPFLAGS="$(CPPFLAGS)" LDFLAGS="$(LDFLAGS)" ./configure \


signature.asc
Description: PGP signature


Bug#1068999: FTBFS due to plantuml

2024-04-20 Thread John Goerzen
reassign 1069353 plantuml
severity 1068999 serious
forcemerge 1068999 1069353
thanks

Hello,

In #1069353, the bug in #1068999 caused nncp to FTBFS in sid due to this
same issue.  nncp uses plantuml to build documentation as part of its
build.  The full build log is at
http://qa-logs.debian.net/2024/04/20/nncp_8.10.0-8_unstable-arm64.log

Thanks,

John



Bug#1069367: qemu: FTBFS on arm64: build-dependency not installable: gcc-powerpc64-linux-gnu

2024-04-20 Thread Michael Tokarev

20.04.2024 15:33, Lucas Nussbaum wrote:
[..]

This is part of a mass rebuild, first building on arm64 and then on
armhf and armel. So I'm not suggesting anything. :-)


Aha.


Is this failing because the build is trying to build arch:all packages,
that can only be built on amd64? If so, the bug severity could be
lowered, clearly.


Well.  Yes, this is exactly the case.  qemu uses quite a few cross-compilers to
build various firmware components.  This is arch-all package qemu-system-data.
Most of these cross-compilers are available on x86 _only_, including the
mentioned gcc-powerpc64-linux-gnu.

I especially made these deps to be in Build-Depends-Indep only, - to be able
to (re)build qemu on non-x86 by using `apt --arch-only`.

I can't say this is a bug to begin with, - wrt lowering its severity.  If it
is a bug, it's a bug in gcc, not qemu (since it is gcc which does not provide
these cross-compilers on all architectures).  Or in the build environment.

Thanks,

/mjt



Bug#1069417: www.debian.org: upgrade procedure instructs users to run “apt update” but neglects upgrading

2024-04-20 Thread Manny
Package: www.debian.org
Severity: normal
X-Debbugs-Cc: debbug.www.debian@sideload.33mail.com

The Bookworm release notes instruct users to “upgrade” to the latest point 
release of Bullseye prior to upgrading to Bookworm:

  
https://www.debian.org/releases/stable/i386/release-notes/ch-upgrading.en.html#upgrade-to-latest-point-release

When following that link, the article says to do an “apt update” then neglects 
to tell users to perform the upgrade.



Bug#1069401: nautilus: FTBFS on arm64: test-nautilus-search-engine-tracker timed out

2024-04-20 Thread Simon McVittie
Control: retitle -1 nautilus: FTBFS on arm64: 
test-nautilus-search-engine-tracker timed out

(cc'ing Lucas in case whatever heuristics are parsing the log can be
improved)

On Sat, 20 Apr 2024 at 14:09:18 +0200, Lucas Nussbaum wrote:
> Relevant part (hopefully):
> > (tracker-miner-fs-3:3061640): dconf-CRITICAL **: 04:05:03.655: unable to 
> > create directory '/sbuild-nonexistent/.cache/dconf': Permission denied.  
> > dconf will not work properly.
> > 
> > (tracker-miner-fs-3:3061640): libupower-glib-WARNING **: 04:05:03.655: 
> > Couldn't connect to proxy: Could not connect: No such file or directory

These are non-fatal (they'd say FATAL-CRITICAL or FATAL-WARNING if they
had been made fatal for testing purposes), although obviously it would
be better to make dconf work correctly (by setting a better $HOME and
$XDG_RUNTIME_DIR, as newer debhelper compat levels do by default) to
reduce the log noise and make real problems visible.

> > 17/17 test-nautilus-search-engine-trackerTIMEOUT480.24s 
> >   exit status 1

The failure reason here is that this test timed out.

> > test: test-nautilus-search-engine-tracker
...
> > ERROR: g-io-error-quark: The connection is closed (18)

I think that's more likely to be the root cause. It might be a D-Bus
connection, or some other socket.

smcv



Bug#1069455: haskell-hoogle: FTBFS on armhf: unsatisfiable build-dependencies

2024-04-20 Thread Lucas Nussbaum
Source: haskell-hoogle
Version: 5.0.18.3+dfsg1-5
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-armhf

Hi,

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


Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper (>= 10), haskell-devscripts-minimal | 
> haskell-devscripts (>= 0.9), cdbs, ghc (>= 9.4), ghc-prof, 
> libghc-quickcheck2-dev, libghc-quickcheck2-prof, libghc-aeson-dev, 
> libghc-aeson-prof, libghc-blaze-html-dev, libghc-blaze-html-prof, 
> libghc-blaze-markup-dev, libghc-blaze-markup-prof, libghc-cmdargs-dev, 
> libghc-cmdargs-prof, libghc-conduit-dev (>= 1.3.0), libghc-conduit-prof, 
> libghc-conduit-extra-dev (>= 1.2.3.2), libghc-conduit-extra-prof, 
> libghc-connection-dev, libghc-connection-prof, libghc-extra-dev (>= 1.6.6), 
> libghc-extra-prof, libghc-foundation-dev (>= 0.0.13), libghc-foundation-prof, 
> libghc-hashable-dev, libghc-hashable-prof, libghc-src-exts-dev (>= 1.22), 
> libghc-src-exts-dev (<< 1.24), libghc-src-exts-prof, libghc-http-conduit-dev 
> (>= 2.3), libghc-http-conduit-prof, libghc-http-types-dev, 
> libghc-http-types-prof, libghc-js-flot-dev, libghc-js-flot-prof, 
> libghc-js-jquery-dev, libghc-js-jquery-prof, libghc-mmap-dev, 
> libghc-mmap-prof, libghc-old-locale-dev, libghc-old-locale-prof, 
> libghc-process-extras-dev, libghc-process-extras-prof, libghc-resourcet-dev, 
> libghc-resourcet-prof, libghc-storable-tuple-dev, libghc-storable-tuple-prof, 
> libghc-tar-dev, libghc-tar-prof, libghc-uniplate-dev, libghc-uniplate-prof, 
> libghc-utf8-string-dev, libghc-utf8-string-prof, libghc-vector-dev, 
> libghc-vector-prof, libghc-wai-dev, libghc-wai-prof, libghc-wai-logger-dev, 
> libghc-wai-logger-prof, libghc-warp-dev, libghc-warp-prof, 
> libghc-warp-tls-dev, libghc-warp-tls-prof, libghc-zlib-dev, libghc-zlib-prof, 
> build-essential, fakeroot, ghc-doc, libghc-quickcheck2-doc, libghc-aeson-doc, 
> libghc-blaze-html-doc, libghc-blaze-markup-doc, libghc-cmdargs-doc, 
> libghc-conduit-doc, libghc-conduit-extra-doc, libghc-connection-doc, 
> libghc-extra-doc, libghc-foundation-doc, libghc-hashable-doc, 
> libghc-src-exts-doc, libghc-http-conduit-doc, libghc-http-types-doc, 
> libghc-js-flot-doc, libghc-js-jquery-doc, libghc-mmap-doc, 
> libghc-old-locale-doc, libghc-process-extras-doc, libghc-resourcet-doc, 
> libghc-storable-tuple-doc, libghc-tar-doc, libghc-uniplate-doc, 
> libghc-utf8-string-doc, libghc-vector-doc, libghc-wai-doc, 
> libghc-wai-logger-doc, libghc-warp-doc, libghc-warp-tls-doc, libghc-zlib-doc
> Filtered Build-Depends: debhelper (>= 10), haskell-devscripts-minimal, cdbs, 
> ghc (>= 9.4), ghc-prof, libghc-quickcheck2-dev, libghc-quickcheck2-prof, 
> libghc-aeson-dev, libghc-aeson-prof, libghc-blaze-html-dev, 
> libghc-blaze-html-prof, libghc-blaze-markup-dev, libghc-blaze-markup-prof, 
> libghc-cmdargs-dev, libghc-cmdargs-prof, libghc-conduit-dev (>= 1.3.0), 
> libghc-conduit-prof, libghc-conduit-extra-dev (>= 1.2.3.2), 
> libghc-conduit-extra-prof, libghc-connection-dev, libghc-connection-prof, 
> libghc-extra-dev (>= 1.6.6), libghc-extra-prof, libghc-foundation-dev (>= 
> 0.0.13), libghc-foundation-prof, libghc-hashable-dev, libghc-hashable-prof, 
> libghc-src-exts-dev (>= 1.22), libghc-src-exts-dev (<< 1.24), 
> libghc-src-exts-prof, libghc-http-conduit-dev (>= 2.3), 
> libghc-http-conduit-prof, libghc-http-types-dev, libghc-http-types-prof, 
> libghc-js-flot-dev, libghc-js-flot-prof, libghc-js-jquery-dev, 
> libghc-js-jquery-prof, libghc-mmap-dev, libghc-mmap-prof, 
> libghc-old-locale-dev, libghc-old-locale-prof, libghc-process-extras-dev, 
> libghc-process-extras-prof, libghc-resourcet-dev, libghc-resourcet-prof, 
> libghc-storable-tuple-dev, libghc-storable-tuple-prof, libghc-tar-dev, 
> libghc-tar-prof, libghc-uniplate-dev, libghc-uniplate-prof, 
> libghc-utf8-string-dev, libghc-utf8-string-prof, libghc-vector-dev, 
> libghc-vector-prof, libghc-wai-dev, libghc-wai-prof, libghc-wai-logger-dev, 
> libghc-wai-logger-prof, libghc-warp-dev, libghc-warp-prof, 
> libghc-warp-tls-dev, libghc-warp-tls-prof, libghc-zlib-dev, libghc-zlib-prof, 
> build-essential, fakeroot, ghc-doc, libghc-quickcheck2-doc, libghc-aeson-doc, 
> libghc-blaze-html-doc, libghc-blaze-markup-doc, libghc-cmdargs-doc, 
> libghc-conduit-doc, libghc-conduit-extra-doc, libghc-connection-doc, 
> libgh

Bug#1069447: gpaw: FTBFS on armhf: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" --test-pytest "--test-args=-v -m ci" returned exit code 13

2024-04-20 Thread Lucas Nussbaum
Source: gpaw
Version: 24.1.0-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-armhf

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_test -- --test-pytest --test-args="-v -m ci"
> I: pybuild base:311: cd /<>/.pybuild/cpython3_3.12/build; 
> python3.12 -m pytest -v -m ci
> E: pybuild pybuild:389: test: plugin distutils failed with: exit code=1: cd 
> /<>/.pybuild/cpython3_3.12/build; python3.12 -m pytest -v -m ci
> I: pybuild base:311: cd /<>/.pybuild/cpython3_3.11/build; 
> python3.11 -m pytest -v -m ci
> E: pybuild pybuild:389: test: plugin distutils failed with: exit code=1: cd 
> /<>/.pybuild/cpython3_3.11/build; python3.11 -m pytest -v -m ci
> dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 
> 3.11" --test-pytest "--test-args=-v -m ci" returned exit code 13


The full build log is available from:
http://qa-logs.debian.net/2024/04/20/gpaw_24.1.0-1_unstable-armhf.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240420;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240420=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 mark 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.



Bug#1069448: ipsvd: FTBFS on armhf: make[1]: *** [Makefile:7: check] Error 1

2024-04-20 Thread Lucas Nussbaum
Source: ipsvd
Version: 1.0.0-5
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-armhf

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>/ipsvd-1.0.0/compile'
> ./compile check-tcpsvd.c
> ./load check-tcpsvd unix.a byte.a `cat socket.lib`
> ./compile check-udpsvd.c
> ./load check-udpsvd unix.a byte.a `cat socket.lib`
> ./compile check-ipsvd-cdb.c
> ./load check-ipsvd-cdb uint32_unpack.o unix.a byte.a
> ./check-local tcpsvd udpsvd ipsvd-cdb `grep -v nossl  Checking tcpsvd...
> Checking udpsvd...
> Checking ipsvd-cdb...
> usage: ipsvd-cdb cdb cdb.tmp dir
> 
> 111
> ipsvd-cdb: fatal: unable to create: 
> /<>/ipsvd/compile/check-tmp.cdb.tmp: invalid argument
> 111
> /<>/ipsvd/compile/ipsvd-cdb.check: 24: cannot open 
> /<>/ipsvd/compile/check-tmp.cdb: No such file
> 0
> ipsvd-cdb failed.
> make[1]: *** [Makefile:7: check] Error 1


The full build log is available from:
http://qa-logs.debian.net/2024/04/20/ipsvd_1.0.0-5_unstable-armhf.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240420;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240420=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 mark 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.



Bug#1069449: firejail: FTBFS on armhf: ccnMX2lv.s:1765: Error: symbol `fopen64' is already defined

2024-04-20 Thread Lucas Nussbaum
Source: firejail
Version: 0.9.72-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-armhf

Hi,

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


Relevant part (hopefully):
> gcc -ggdb  -O2 -DVERSION='"0.9.72"' -fstack-protector-all -D_FORTIFY_SOURCE=2 
> -Wformat -Wformat-security -fPIE -DPREFIX='"/usr"' 
> -DSYSCONFDIR='"/etc/firejail"' -DLIBDIR='"/usr/lib/arm-linux-gnueabihf"' 
> -DBINDIR='"/usr/bin"' -DVARDIR='"/var/lib/firejail"'   -DHAVE_OUTPUT 
> -DHAVE_X11 -DHAVE_PRIVATE_HOME -DHAVE_APPARMOR -DHAVE_IDS  -DHAVE_USERTMPFS 
> -DHAVE_DBUSPROXY  -DHAVE_GLOBALCFG -DHAVE_CHROOT -DHAVE_NETWORK -DHAVE_USERNS 
> -DHAVE_FILE_TRANSFER -DHAVE_SELINUX -DHAVE_SUID   -fstack-clash-protection 
> -fstack-protector-strong  -g -O2 -Werror=implicit-function-declaration 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security  -c join.c -o join.o
> /tmp/ccnMX2lv.s: Assembler messages:
> /tmp/ccnMX2lv.s:1765: Error: symbol `fopen64' is already defined
> /tmp/ccnMX2lv.s:2079: Error: symbol `freopen64' is already defined
> /tmp/ccnMX2lv.s:3164: Error: symbol `__stat64_time64' is already defined
> /tmp/ccnMX2lv.s:3474: Error: symbol `__lstat64_time64' is already defined
> make[2]: *** [../../src/so.mk:23: libtrace.o] Error 1


The full build log is available from:
http://qa-logs.debian.net/2024/04/20/firejail_0.9.72-2_unstable-armhf.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240420;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240420=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 mark 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.



Bug#1069450: socket-wrapper: FTBFS on armhf: features-time64.h:26:5: error: #error "_TIME_BITS=64 is allowed only with _FILE_OFFSET_BITS=64"

2024-04-20 Thread Lucas Nussbaum
Source: socket-wrapper
Version: 1.4.2-3
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-armhf

Hi,

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


Relevant part (hopefully):
> cd /<>/obj/src && /usr/bin/cc -Dsocket_wrapper_EXPORTS 
> -I/<>/obj/src -I/<>/src -I/<>/obj -g 
> -O2 -Werror=implicit-function-declaration 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -D_LARGEFILE_SOURCE 
> -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC 
> -std=gnu99 -Wall -Wshadow -Wmissing-prototypes -Wcast-align -Wcast-qual 
> -Werror=address -Wstrict-prototypes -Werror=strict-prototypes -Wwrite-strings 
> -Werror=write-strings -Werror-implicit-function-declaration -Wpointer-arith 
> -Werror=pointer-arith -Wdeclaration-after-statement 
> -Werror=declaration-after-statement -Wreturn-type -Werror=return-type 
> -Wuninitialized -Werror=uninitialized -Wimplicit-fallthrough 
> -Wno-format-zero-length -Wformat -Wformat-security -Werror=format-security 
> -fno-common -fstack-protector-strong -fstack-clash-protection -D_GNU_SOURCE 
> -D_LARGEFILE64_SOURCE -MD -MT 
> src/CMakeFiles/socket_wrapper.dir/socket_wrapper.c.o -MF 
> CMakeFiles/socket_wrapper.dir/socket_wrapper.c.o.d -o 
> CMakeFiles/socket_wrapper.dir/socket_wrapper.c.o -c 
> /<>/src/socket_wrapper.c
> In file included from /usr/include/features.h:393,
>  from /usr/include/arm-linux-gnueabihf/sys/types.h:25,
>  from /<>/src/socket_wrapper.c:53:
> /usr/include/features-time64.h:26:5: error: #error "_TIME_BITS=64 is allowed 
> only with _FILE_OFFSET_BITS=64"
>26 | #   error "_TIME_BITS=64 is allowed only with _FILE_OFFSET_BITS=64"
>   | ^
> [  6%] Linking C shared library libsocket_wrapper_noop.so
> cd /<>/obj/src && /usr/bin/cmake -E cmake_link_script 
> CMakeFiles/socket_wrapper_noop.dir/link.txt --verbose=1
> /usr/bin/cc -fPIC -g -O2 -Werror=implicit-function-declaration 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -D_LARGEFILE_SOURCE 
> -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 
> -Wl,-z,relro -Wl,-z,now -shared  -o libsocket_wrapper_noop.so 
> CMakeFiles/socket_wrapper_noop.dir/socket_wrapper_noop.c.o  
> /usr/lib/arm-linux-gnueabihf/libdl.a 
> make[3]: Leaving directory '/<>/obj'
> [  6%] Built target socket_wrapper_noop
> make  -f tests/CMakeFiles/swrap_fake_uid_wrapper.dir/build.make 
> tests/CMakeFiles/swrap_fake_uid_wrapper.dir/depend
> make[3]: Entering directory '/<>/obj'
> cd /<>/obj && /usr/bin/cmake -E cmake_depends "Unix Makefiles" 
> /<> /<>/tests /<>/obj 
> /<>/obj/tests 
> /<>/obj/tests/CMakeFiles/swrap_fake_uid_wrapper.dir/DependInfo.cmake
>  "--color="
> make[3]: Leaving directory '/<>/obj'
> make  -f tests/CMakeFiles/swrap_fake_uid_wrapper.dir/build.make 
> tests/CMakeFiles/swrap_fake_uid_wrapper.dir/build
> make[3]: Entering directory '/<>/obj'
> [  8%] Building C object 
> tests/CMakeFiles/swrap_fake_uid_wrapper.dir/swrap_fake_uid_wrapper.c.o
> cd /<>/obj/tests && /usr/bin/cc -Dswrap_fake_uid_wrapper_EXPORTS 
> -I/<>/obj/tests -I/<>/tests -I/<>/obj 
> -I/<>/src -g -O2 -Werror=implicit-function-declaration 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -D_LARGEFILE_SOURCE 
> -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC 
> -std=gnu99 -Wall -Wshadow -Wmissing-prototypes -Wcast-align -Wcast-qual 
> -Werror=address -Wstrict-prototypes -Werror=strict-prototypes -Wwrite-strings 
> -Werror=write-strings -Werror-implicit-function-declaration -Wpointer-arith 
> -Werror=pointer-arith -Wdeclaration-after-statement 
> -Werror=declaration-after-statement -Wreturn-type -Werror=return-type 
> -Wuninitialized -Werror=uninitialized -Wimplicit-fallthrough 
> -Wno-format-zero-length -Wformat -Wformat-security -Werror=format-security 
> -fno-common -fstack-protector-strong -fstack-clash-protection -D_GNU_SOURCE 
> -MD -MT 
> tests/CMakeFiles/swrap_fake_uid_wrapper.dir/swrap_fake_uid_wrapper.c.o -MF 
> CMakeFiles/swrap_fake_uid_wrapper.dir/swrap_fake_uid_wrapper.c.o.d -o 
> CMakeFiles/swrap_fake_uid_wrapper.dir/swrap_fake_uid_wrapper.c.o -c 
> /<>/tests/swrap_fake_uid_wrapper.c
> make[3]: *** [src/CMakeFiles/socket_wrapper.dir/build.make:79: 
> src/CMakeFiles/socket_wrapper.dir/socket_wr

Bug#1069451: iitii: FTBFS on armhf: mmap_allocator.h:75:(.text._ZN5iitii8iit_baseIySt4pairIyyENS_10iitii_nodeIyS2_XadL_Z9p_get_begRKS2_EEXadL_Z9p_get_endS5_EEEEED2Ev[_ZN5iitii8iit_baseIySt4pairIyyENS_

2024-04-20 Thread Lucas Nussbaum
Source: iitii
Version: 0.0+git20191030.85209e0-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-armhf

Hi,

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


Relevant part (hopefully):
> /usr/bin/ld: CMakeFiles/iitii.dir/src/main.cpp.o: in function 
> `mmap_allocator_namespace::mmap_allocator long, std::pair, 
> &(p_get_beg(std::pair const&)), 
> &(p_get_end(std::pair const&))> 
> >::deallocate(iitii::iitii_node long, unsigned long long>, &(p_get_beg(std::pair long long> const&)), &(p_get_end(std::pair long> const&))>*, unsigned int)':
> /usr/include/mmap_allocator.h:75:(.text._ZN5iitii8iit_baseIySt4pairIyyENS_10iitii_nodeIyS2_XadL_Z9p_get_begRKS2_EEXadL_Z9p_get_endS5_ED2Ev[_ZN5iitii8iit_baseIySt4pairIyyENS_10iitii_nodeIyS2_XadL_Z9p_get_begRKS2_EEXadL_Z9p_get_endS5_ED5Ev]+0x82):
>  undefined reference to 
> `mmap_allocator_namespace::mmap_file_pool::munmap_file(std::__cxx11::basic_string  std::char_traits, std::allocator >, 
> mmap_allocator_namespace::access_mode, long long, unsigned int)'
> /usr/bin/ld: 
> /usr/include/mmap_allocator.h:75:(.text._ZN5iitii8iit_baseIySt4pairIyyENS_10iitii_nodeIyS2_XadL_Z9p_get_begRKS2_EEXadL_Z9p_get_endS5_ED2Ev[_ZN5iitii8iit_baseIySt4pairIyyENS_10iitii_nodeIyS2_XadL_Z9p_get_begRKS2_EEXadL_Z9p_get_endS5_ED5Ev]+0xfa):
>  undefined reference to 
> `mmap_allocator_namespace::mmap_file_pool::munmap_file(std::__cxx11::basic_string  std::char_traits, std::allocator >, 
> mmap_allocator_namespace::access_mode, long long, unsigned int)'
> /usr/bin/ld: 
> /usr/include/mmap_allocator.h:75:(.text._ZNSt12_Vector_baseIN5iitii10iitii_nodeIySt4pairIyyEXadL_Z9p_get_begRKS3_EEXadL_Z9p_get_endS5_N24mmap_allocator_namespace14mmap_allocatorIS6_EEED2Ev[_ZNSt12_Vector_baseIN5iitii10iitii_nodeIySt4pairIyyEXadL_Z9p_get_begRKS3_EEXadL_Z9p_get_endS5_N24mmap_allocator_namespace14mmap_allocatorIS6_EEED5Ev]+0x74):
>  undefined reference to 
> `mmap_allocator_namespace::mmap_file_pool::munmap_file(std::__cxx11::basic_string  std::char_traits, std::allocator >, 
> mmap_allocator_namespace::access_mode, long long, unsigned int)'
> /usr/bin/ld: 
> /usr/include/mmap_allocator.h:75:(.text._ZN24mmap_allocator_namespace14mmap_allocatorIN5iitii10iitii_nodeIySt4pairIyyEXadL_Z9p_get_begRKS4_EEXadL_Z9p_get_endS6_E10deallocateEPS7_j[_ZN24mmap_allocator_namespace14mmap_allocatorIN5iitii10iitii_nodeIySt4pairIyyEXadL_Z9p_get_begRKS4_EEXadL_Z9p_get_endS6_E10deallocateEPS7_j]+0xd2):
>  undefined reference to 
> `mmap_allocator_namespace::mmap_file_pool::munmap_file(std::__cxx11::basic_string  std::char_traits, std::allocator >, 
> mmap_allocator_namespace::access_mode, long long, unsigned int)'
> /usr/bin/ld: 
> /usr/include/mmap_allocator.h:75:(.text._ZN5iitii19iit_mm_builder_baseINS_5iitiiIySt4pairIyyEXadL_Z9p_get_begRKS3_EEXadL_Z9p_get_endS5_S3_NS_10iitii_nodeIyS3_XadL_Z9p_get_begS5_EEXadL_Z9p_get_endS5_E5buildIJRyEEES6_DpOT_[_ZN5iitii19iit_mm_builder_baseINS_5iitiiIySt4pairIyyEXadL_Z9p_get_begRKS3_EEXadL_Z9p_get_endS5_S3_NS_10iitii_nodeIyS3_XadL_Z9p_get_begS5_EEXadL_Z9p_get_endS5_E5buildIJRyEEES6_DpOT_]+0x210):
>  undefined reference to 
> `mmap_allocator_namespace::mmap_file_pool::munmap_file(std::__cxx11::basic_string  std::char_traits, std::allocator >, 
> mmap_allocator_namespace::access_mode, long long, unsigned int)'
> collect2: error: ld returned 1 exit status


The full build log is available from:
http://qa-logs.debian.net/2024/04/20/iitii_0.0+git20191030.85209e0-2_unstable-armhf.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240420;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240420=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 mark 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.



Bug#1069444: rust-libpulse-binding: FTBFS on armhf: dh_auto_test: error: /usr/share/cargo/bin/cargo test --all returned exit code 101

2024-04-20 Thread Lucas Nussbaum
Source: rust-libpulse-binding
Version: 2.28.1-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-armhf

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_test -- test --all
> debian cargo wrapper: options, profiles, parallel, lto: ['parallel=4'] [] 
> ['-j4'] 0
> debian cargo wrapper: rust_type, gnu_type: armv7-unknown-linux-gnueabihf, 
> arm-linux-gnueabihf
> debian cargo wrapper: running subprocess (['env', 'RUST_BACKTRACE=1', 
> '/usr/bin/cargo', '-Zavoid-dev-deps', 'test', '--verbose', '--verbose', 
> '-j4', '--target', 'armv7-unknown-linux-gnueabihf', '--all'],) {}
>Compiling proc-macro2 v1.0.76
>Compiling unicode-ident v1.0.12
>Compiling autocfg v1.1.0
>Compiling syn v1.0.109
>  Running `CARGO=/usr/bin/cargo CARGO_CRATE_NAME=build_script_build 
> CARGO_MANIFEST_DIR=/<>/debian/cargo_registry/proc-macro2-1.0.76 
> CARGO_PKG_AUTHORS='David Tolnay :Alex Crichton 
> ' CARGO_PKG_DESCRIPTION='A substitute implementation 
> of the compiler'\''s `proc_macro` API to decouple token-based libraries from 
> the procedural macro use case.' CARGO_PKG_HOMEPAGE='' CARGO_PKG_LICENSE='MIT 
> OR Apache-2.0' CARGO_PKG_LICENSE_FILE='' CARGO_PKG_NAME=proc-macro2 
> CARGO_PKG_REPOSITORY='https://github.com/dtolnay/proc-macro2' 
> CARGO_PKG_RUST_VERSION=1.56 CARGO_PKG_VERSION=1.0.76 
> CARGO_PKG_VERSION_MAJOR=1 CARGO_PKG_VERSION_MINOR=0 
> CARGO_PKG_VERSION_PATCH=76 CARGO_PKG_VERSION_PRE='' 
> LD_LIBRARY_PATH='/<>/target/debug/deps:/usr/lib' rustc 
> --crate-name build_script_build --edition=2021 
> /<>/debian/cargo_registry/proc-macro2-1.0.76/build.rs 
> --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat 
> --crate-type bin --emit=dep-info,link -C embed-bitcode=no -C debuginfo=2 
> --cfg 'feature="default"' --cfg 'feature="proc-macro"' -C 
> metadata=5af698d564d3f59d -C extra-filename=-5af698d564d3f59d --out-dir 
> /<>/target/debug/build/proc-macro2-5af698d564d3f59d -L 
> dependency=/<>/target/debug/deps --cap-lints warn`
>  Running `CARGO=/usr/bin/cargo CARGO_CRATE_NAME=unicode_ident 
> CARGO_MANIFEST_DIR=/<>/debian/cargo_registry/unicode-ident-1.0.12
>  CARGO_PKG_AUTHORS='David Tolnay ' 
> CARGO_PKG_DESCRIPTION='Determine whether characters have the XID_Start or 
> XID_Continue properties according to Unicode Standard Annex #31' 
> CARGO_PKG_HOMEPAGE='' CARGO_PKG_LICENSE='(MIT OR Apache-2.0) AND 
> Unicode-DFS-2016' CARGO_PKG_LICENSE_FILE='' CARGO_PKG_NAME=unicode-ident 
> CARGO_PKG_REPOSITORY='https://github.com/dtolnay/unicode-ident' 
> CARGO_PKG_RUST_VERSION=1.31 CARGO_PKG_VERSION=1.0.12 
> CARGO_PKG_VERSION_MAJOR=1 CARGO_PKG_VERSION_MINOR=0 
> CARGO_PKG_VERSION_PATCH=12 CARGO_PKG_VERSION_PRE='' 
> LD_LIBRARY_PATH='/<>/target/debug/deps:/usr/lib' rustc 
> --crate-name unicode_ident --edition=2018 
> /<>/debian/cargo_registry/unicode-ident-1.0.12/src/lib.rs 
> --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat 
> --crate-type lib --emit=dep-info,metadata,link -C embed-bitcode=no -C 
> debuginfo=2 -C metadata=ba2991cf6fcfddae -C extra-filename=-ba2991cf6fcfddae 
> --out-dir /<>/target/debug/deps -L 
> dependency=/<>/target/debug/deps --cap-lints warn`
>  Running `CARGO=/usr/bin/cargo CARGO_CRATE_NAME=autocfg 
> CARGO_MANIFEST_DIR=/<>/debian/cargo_registry/autocfg-1.1.0 
> CARGO_PKG_AUTHORS='Josh Stone ' 
> CARGO_PKG_DESCRIPTION='Automatic cfg for Rust compiler features' 
> CARGO_PKG_HOMEPAGE='' CARGO_PKG_LICENSE='Apache-2.0 OR MIT' 
> CARGO_PKG_LICENSE_FILE='' CARGO_PKG_NAME=autocfg 
> CARGO_PKG_REPOSITORY='https://github.com/cuviper/autocfg' 
> CARGO_PKG_RUST_VERSION='' CARGO_PKG_VERSION=1.1.0 CARGO_PKG_VERSION_MAJOR=1 
> CARGO_PKG_VERSION_MINOR=1 CARGO_PKG_VERSION_PATCH=0 CARGO_PKG_VERSION_PRE='' 
> LD_LIBRARY_PATH='/<>/target/debug/deps:/usr/lib' rustc 
> --crate-name autocfg 
> /<>/debian/cargo_registry/autocfg-1.1.0/src/lib.rs 
> --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat 
> --crate-type lib --emit=dep-info,metadata,link -C embed-bitcode=no -C 
> debuginfo=2 -C metadata=8b7f370f568a8e40 -C extra-filename=-8b7f370f568a8e40 
> --out-dir /<>/target/debug/deps -L 
> dependency=/<>/target/debug/deps --cap-lints warn`
>  Running `CARGO=/usr/bin/cargo CARGO_CRATE_NAME=build_script_build 
> CARGO_MANIFEST_DIR=/<>/debian/cargo_registry/syn-1.0.109 
> CARGO_PKG_AUTHORS='David Tolnay ' 
> CARGO_PKG_DESCRIPTION='Parser for Rust source code' CARGO_PKG_HOMEPAGE='' 
> CARGO_PKG_LICE

Bug#1069452: purelibc: FTBFS on armhf: ccPREIBJ.s:380: Error: symbol `readdir64' is already defined

2024-04-20 Thread Lucas Nussbaum
Source: purelibc
Version: 1.0.6-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-armhf

Hi,

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


Relevant part (hopefully):
> /usr/bin/cc -D_GNU_SOURCE -Dpurelibc_EXPORTS -I/<> -g -O2 
> -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -fstack-clash-protection -Wformat 
> -Werror=format-security -Wall -pedantic -D_LARGEFILE_SOURCE 
> -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 
> -D_FORTIFY_SOURCE=2 -ggdb -Wall -Wextra -pedantic -std=gnu11 
> -Wno-incompatible-pointer-types -Wno-unused-parameter -fPIC -MD -MT 
> CMakeFiles/purelibc.dir/syscalls.c.o -MF 
> CMakeFiles/purelibc.dir/syscalls.c.o.d -o 
> CMakeFiles/purelibc.dir/syscalls.c.o -c /<>/syscalls.c
> /tmp/ccPREIBJ.s: Assembler messages:
> /tmp/ccPREIBJ.s:380: Error: symbol `readdir64' is already defined
> /tmp/ccPREIBJ.s:984: Error: symbol `scandir64' is already defined
> /tmp/ccPREIBJ.s:1045: Error: symbol `scandirat64' is already defined
> make[3]: *** [CMakeFiles/purelibc.dir/build.make:79: 
> CMakeFiles/purelibc.dir/dir.c.o] Error 1


The full build log is available from:
http://qa-logs.debian.net/2024/04/20/purelibc_1.0.6-1_unstable-armhf.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240420;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240420=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 mark 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.



Bug#1069465: libeatmydata: FTBFS on armhf: features-time64.h:26:5: error: #error "_TIME_BITS=64 is allowed only with _FILE_OFFSET_BITS=64"

2024-04-20 Thread Lucas Nussbaum
Source: libeatmydata
Version: 131-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-armhf

Hi,

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


Relevant part (hopefully):
> /bin/bash ./libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I.   
> -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time 
> -D_FORTIFY_SOURCE=2   -DBUILDING_LIBEATMYDATA -g -O2 
> -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -fstack-clash-protection -Wformat 
> -Werror=format-security -c -o libeatmydata/la-libeatmydata.lo `test -f 
> 'libeatmydata/libeatmydata.c' || echo './'`libeatmydata/libeatmydata.c
> libtool: compile:  gcc -DHAVE_CONFIG_H -I. -D_LARGEFILE_SOURCE 
> -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 
> -DBUILDING_LIBEATMYDATA -g -O2 -Werror=implicit-function-declaration 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -c 
> libeatmydata/libeatmydata.c  -fPIC -DPIC -o 
> libeatmydata/.libs/la-libeatmydata.o
> In file included from /usr/include/features.h:393,
>  from /usr/include/arm-linux-gnueabihf/sys/types.h:25,
>  from libeatmydata/libeatmydata.c:22:
> /usr/include/features-time64.h:26:5: error: #error "_TIME_BITS=64 is allowed 
> only with _FILE_OFFSET_BITS=64"
>26 | #   error "_TIME_BITS=64 is allowed only with _FILE_OFFSET_BITS=64"
>   | ^
> make[2]: *** [Makefile:1046: libeatmydata/la-libeatmydata.lo] Error 1


The full build log is available from:
http://qa-logs.debian.net/2024/04/20/libeatmydata_131-1_unstable-armhf.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240420;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240420=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 mark 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.



Bug#1069464: haskell-lambdabot-haskell-plugins: FTBFS on armhf: unsatisfiable build-dependencies

2024-04-20 Thread Lucas Nussbaum
Source: haskell-lambdabot-haskell-plugins
Version: 5.3.1.1-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-armhf

Hi,

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


Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: cdbs, debhelper (>= 10), ghc (>= 9.4), ghc-prof, 
> haskell-devscripts (>= 0.13), libghc-arrows-dev (>= 0.4), libghc-arrows-prof, 
> libghc-data-memocombinators-dev (>= 0.4), libghc-data-memocombinators-prof, 
> libghc-src-exts-simple-dev (>= 1.18), libghc-src-exts-simple-dev (<< 1.24), 
> libghc-src-exts-simple-prof, libghc-hoogle-dev (>= 5.0.17.1), 
> libghc-hoogle-prof, libghc-http-dev (>= 1:4000), libghc-http-prof, 
> libghc-iospec-dev (>= 0.2), libghc-iospec-prof, libghc-lambdabot-core-dev (>= 
> 5.3), libghc-lambdabot-core-dev (<< 5.4), libghc-lambdabot-core-prof, 
> libghc-lambdabot-reference-plugins-dev (>= 5.3), 
> libghc-lambdabot-reference-plugins-dev (<< 5.4), 
> libghc-lambdabot-reference-plugins-prof, libghc-lambdabot-trusted-dev (>= 
> 5.3), libghc-lambdabot-trusted-dev (<< 5.4), libghc-lambdabot-trusted-prof, 
> libghc-lifted-base-dev (>= 0.2), libghc-lifted-base-prof, libghc-logict-dev 
> (>= 0.5), libghc-logict-prof, libghc-monadrandom-dev (>= 0.1), 
> libghc-monadrandom-prof, libghc-mueval-dev (>= 0.9.3), libghc-mueval-prof, 
> libghc-network-dev (>= 2.7), libghc-network-dev (<< 3.2), 
> libghc-network-prof, libghc-numbers-dev (>= 3000), libghc-numbers-prof, 
> libghc-oeis-dev (>= 0.3.1), libghc-oeis-prof, libghc-quickcheck2-dev (>= 2), 
> libghc-quickcheck2-prof, libghc-regex-tdfa-dev (>= 1.1), 
> libghc-regex-tdfa-prof, libghc-show-dev (>= 0.4), libghc-show-prof, 
> libghc-split-dev (>= 0.2), libghc-split-prof, libghc-syb-dev (>= 0.3), 
> libghc-syb-prof, libghc-transformers-dev, libghc-transformers-prof, 
> libghc-utf8-string-dev (>= 0.3), libghc-utf8-string-prof, 
> libghc-vector-space-dev (>= 0.8), libghc-vector-space-prof, build-essential, 
> fakeroot, ghc-doc, libghc-arrows-doc, libghc-data-memocombinators-doc, 
> libghc-src-exts-simple-doc, libghc-hoogle-doc, libghc-http-doc, 
> libghc-iospec-doc, libghc-lambdabot-core-doc, 
> libghc-lambdabot-reference-plugins-doc, libghc-lambdabot-trusted-doc, 
> libghc-lifted-base-doc, libghc-logict-doc, libghc-monadrandom-doc, 
> libghc-mueval-doc, libghc-network-doc, libghc-numbers-doc, libghc-oeis-doc, 
> libghc-quickcheck2-doc, libghc-regex-tdfa-doc, libghc-show-doc, 
> libghc-split-doc, libghc-syb-doc, libghc-transformers-doc, 
> libghc-utf8-string-doc, libghc-vector-space-doc
> Filtered Build-Depends: cdbs, debhelper (>= 10), ghc (>= 9.4), ghc-prof, 
> haskell-devscripts (>= 0.13), libghc-arrows-dev (>= 0.4), libghc-arrows-prof, 
> libghc-data-memocombinators-dev (>= 0.4), libghc-data-memocombinators-prof, 
> libghc-src-exts-simple-dev (>= 1.18), libghc-src-exts-simple-dev (<< 1.24), 
> libghc-src-exts-simple-prof, libghc-hoogle-dev (>= 5.0.17.1), 
> libghc-hoogle-prof, libghc-http-dev (>= 1:4000), libghc-http-prof, 
> libghc-iospec-dev (>= 0.2), libghc-iospec-prof, libghc-lambdabot-core-dev (>= 
> 5.3), libghc-lambdabot-core-dev (<< 5.4), libghc-lambdabot-core-prof, 
> libghc-lambdabot-reference-plugins-dev (>= 5.3), 
> libghc-lambdabot-reference-plugins-dev (<< 5.4), 
> libghc-lambdabot-reference-plugins-prof, libghc-lambdabot-trusted-dev (>= 
> 5.3), libghc-lambdabot-trusted-dev (<< 5.4), libghc-lambdabot-trusted-prof, 
> libghc-lifted-base-dev (>= 0.2), libghc-lifted-base-prof, libghc-logict-dev 
> (>= 0.5), libghc-logict-prof, libghc-monadrandom-dev (>= 0.1), 
> libghc-monadrandom-prof, libghc-mueval-dev (>= 0.9.3), libghc-mueval-prof, 
> libghc-network-dev (>= 2.7), libghc-network-dev (<< 3.2), 
> libghc-network-prof, libghc-numbers-dev (>= 3000), libghc-numbers-prof, 
> libghc-oeis-dev (>= 0.3.1), libghc-oeis-prof, libghc-quickcheck2-dev (>= 2), 
> libghc-quickcheck2-prof, libghc-regex-tdfa-dev (>= 1.1), 
> libghc-regex-tdfa-prof, libghc-show-dev (>= 0.4), libghc-show-prof, 
> libghc-split-dev (>= 0.2), libghc-split-prof, libghc-syb-dev (>= 0.3), 
> libghc-syb-prof, libghc-transformers-dev, libghc-transformers-prof, 
> libghc-utf8-string-dev (>= 0.3), libghc-utf8-string-prof, 
> libghc-vector-space

Bug#1069463: blobwars: FTBFS on armhf: src/CReplayData.cpp:41:34: error: cannot convert ‘long int*’ to ‘const time_t*’ {aka ‘const long long int*’}

2024-04-20 Thread Lucas Nussbaum
Source: blobwars
Version: 2.00-3
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-armhf

Hi,

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


Relevant part (hopefully):
> g++ -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security `pkg-config 
> --cflags sdl2 SDL2_mixer SDL2_image SDL2_ttf SDL2_net` -DVERSION=2.00 
> -DRELEASE=1 -DUSEPAK=0 -DPAKNAME=\"blobwars.pak\" 
> -DPAKLOCATION=\"/usr/share/games/blobwars/\" -DUNIX 
> -DGAMEPLAYMANUAL=\"/usr/share/doc/blobwars/index.html\" -Wall 
> -DLOCALEDIR=\"/usr/share/locale/\" 
> -DMEDAL_SERVER_HOST=\"www.parallelrealities.co.uk\" -DMEDAL_SERVER_PORT=80 -g 
> -O2 -Werror=implicit-function-declaration 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -O2 -g -flto -c 
> src/CSwitch.cpp
> cc1plus: warning: ‘-Werror=’ argument ‘-Werror=implicit-function-declaration’ 
> is not valid for C++
> src/CReplayData.cpp: In member function ‘void 
> ReplayData::printReplayInformation()’:
> src/CReplayData.cpp:41:34: error: cannot convert ‘long int*’ to ‘const 
> time_t*’ {aka ‘const long long int*’}
>41 | tm *timeinfo = localtime();
>   |  ^~
>   |  |
>   |  long int*
> In file included from /usr/include/features.h:490,
>  from /usr/include/errno.h:25,
>  from src/headers.h:22,
>  from src/CReplayData.cpp:1:
> /usr/include/time.h:141:19: note:   initializing argument 1 of ‘tm* 
> localtime(const time_t*)’
>   141 | extern struct tm *__REDIRECT_NTH (localtime, (const time_t *__timer),
>   |   ^~
> make[1]: *** [Makefile:83: CReplayData.o] Error 1


The full build log is available from:
http://qa-logs.debian.net/2024/04/20/blobwars_2.00-3_unstable-armhf.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240420;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240420=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 mark 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.



Bug#1069466: holes: FTBFS on armhf: dh_auto_test: error: make -j4 check returned exit code 2

2024-04-20 Thread Lucas Nussbaum
Source: holes
Version: 0.1-5
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-armhf

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> prove -v ./tests
> ./tests .. 
> 1..10
> ok - no hole
> ok - big, no hole
> ok - empty file
> not ok - small holes
> # Unexpected output:
> # 0011 0
> # 0077 0
> ok - small, undetected holes
> not ok - medium holes
> # Unexpected output:
> #  0
> # 0001 0
> not ok - medium, offsetted holes
> # Unexpected output:
> #  0
> # fffa 0
> not ok - huge holes
> # Unexpected output:
> #  0
> # 00c0 0
> not ok - huge, offsetted holes
> # Unexpected output:
> # 0e34 0
> # 00c00e34 0
> not ok - detect non-zeroes
> # Unexpected output:
> # 0e34 0
> # 00c00e34 0
> Failed 6/10 subtests 
> 
> Test Summary Report
> ---
> ./tests (Wstat: 0 Tests: 10 Failed: 6)
>   Failed tests:  4, 6-10
> Files=1, Tests=10,  1 wallclock secs ( 0.02 usr  0.00 sys +  0.20 cusr  0.54 
> csys =  0.76 CPU)
> Result: FAIL
> make[1]: *** [Makefile:19: check] Error 1
> make[1]: Leaving directory '/<>'
> dh_auto_test: error: make -j4 check returned exit code 2


The full build log is available from:
http://qa-logs.debian.net/2024/04/20/holes_0.1-5_unstable-armhf.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240420;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240420=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 mark 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.



Bug#1069457: haskell-warp: FTBFS on armhf: unsatisfiable build-dependencies

2024-04-20 Thread Lucas Nussbaum
Source: haskell-warp
Version: 3.3.25-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-armhf

Hi,

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


Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: cdbs, debhelper (>= 10), ghc (>= 8.4.3), ghc-prof, 
> haskell-devscripts (>= 0.13), libghc-async-dev, libghc-async-prof, 
> libghc-auto-update-dev (<< 0.2), libghc-auto-update-dev (>= 0.1.3), 
> libghc-auto-update-prof, libghc-bsb-http-chunked-dev (<< 0.1), 
> libghc-bsb-http-chunked-prof, libghc-case-insensitive-dev (>= 0.2), 
> libghc-case-insensitive-prof, libghc-doctest-dev (>= 0.10.1), 
> libghc-hashable-dev, libghc-hashable-prof, libghc-hspec-dev (>= 1.3), 
> libghc-http-date-dev, libghc-http-date-prof, libghc-http-types-dev (>= 0.12), 
> libghc-http-types-prof, libghc-http2-dev (>= 3.0), libghc-http2-dev (<< 5), 
> libghc-http2-prof, libghc-hunit-dev, libghc-iproute-dev (>= 1.3.1), 
> libghc-iproute-prof, libghc-lifted-base-dev (>= 0.1), libghc-network-dev (>= 
> 2.3), libghc-network-prof, libghc-recv-dev (>= 0.1.0), libghc-recv-dev (<< 
> 0.2.0), libghc-recv-prof, libghc-simple-sendfile-dev (>= 0.2.7), 
> libghc-simple-sendfile-dev (<< 0.3), libghc-simple-sendfile-prof, 
> libghc-streaming-commons-dev (>= 0.1.10), libghc-streaming-commons-prof, 
> libghc-time-manager-dev, libghc-time-manager-prof, libghc-unix-compat-dev (>= 
> 0.2), libghc-unix-compat-prof, libghc-unliftio-dev, libghc-unliftio-prof, 
> libghc-vault-dev (>= 0.3), libghc-vault-prof, libghc-wai-dev (<< 3.3), 
> libghc-wai-dev (>= 3.2), libghc-wai-prof, libghc-word8-dev, 
> libghc-word8-prof, libghc-x509-dev, libghc-x509-prof, libghc-quickcheck2-dev, 
> libghc-quickcheck2-prof, libghc-hspec-prof, libghc-http-client-dev, 
> libghc-http-client-prof, curl, build-essential, fakeroot, ghc-doc, 
> libghc-auto-update-doc, libghc-bsb-http-chunked-doc, 
> libghc-case-insensitive-doc, libghc-hashable-doc, libghc-http-date-doc, 
> libghc-http-types-doc, libghc-http2-doc, libghc-iproute-doc, 
> libghc-network-doc, libghc-recv-doc, libghc-simple-sendfile-doc, 
> libghc-streaming-commons-doc, libghc-time-manager-doc, 
> libghc-unix-compat-doc, libghc-unliftio-doc, libghc-vault-doc, 
> libghc-wai-doc, libghc-word8-doc, libghc-x509-doc
> Filtered Build-Depends: cdbs, debhelper (>= 10), ghc (>= 8.4.3), ghc-prof, 
> haskell-devscripts (>= 0.13), libghc-async-dev, libghc-async-prof, 
> libghc-auto-update-dev (<< 0.2), libghc-auto-update-dev (>= 0.1.3), 
> libghc-auto-update-prof, libghc-bsb-http-chunked-dev (<< 0.1), 
> libghc-bsb-http-chunked-prof, libghc-case-insensitive-dev (>= 0.2), 
> libghc-case-insensitive-prof, libghc-doctest-dev (>= 0.10.1), 
> libghc-hashable-dev, libghc-hashable-prof, libghc-hspec-dev (>= 1.3), 
> libghc-http-date-dev, libghc-http-date-prof, libghc-http-types-dev (>= 0.12), 
> libghc-http-types-prof, libghc-http2-dev (>= 3.0), libghc-http2-dev (<< 5), 
> libghc-http2-prof, libghc-hunit-dev, libghc-iproute-dev (>= 1.3.1), 
> libghc-iproute-prof, libghc-lifted-base-dev (>= 0.1), libghc-network-dev (>= 
> 2.3), libghc-network-prof, libghc-recv-dev (>= 0.1.0), libghc-recv-dev (<< 
> 0.2.0), libghc-recv-prof, libghc-simple-sendfile-dev (>= 0.2.7), 
> libghc-simple-sendfile-dev (<< 0.3), libghc-simple-sendfile-prof, 
> libghc-streaming-commons-dev (>= 0.1.10), libghc-streaming-commons-prof, 
> libghc-time-manager-dev, libghc-time-manager-prof, libghc-unix-compat-dev (>= 
> 0.2), libghc-unix-compat-prof, libghc-unliftio-dev, libghc-unliftio-prof, 
> libghc-vault-dev (>= 0.3), libghc-vault-prof, libghc-wai-dev (<< 3.3), 
> libghc-wai-dev (>= 3.2), libghc-wai-prof, libghc-word8-dev, 
> libghc-word8-prof, libghc-x509-dev, libghc-x509-prof, libghc-quickcheck2-dev, 
> libghc-quickcheck2-prof, libghc-hspec-prof, libghc-http-client-dev, 
> libghc-http-client-prof, curl, build-essential, fakeroot, ghc-doc, 
> libghc-auto-update-doc, libghc-bsb-http-chunked-doc, 
> libghc-case-insensitive-doc, libghc-hashable-doc, libghc-http-date-doc, 
> libghc-http-types-doc, libghc-http2-doc, libghc-iproute-doc, 
> libghc-network-doc, libghc-recv-doc, libghc-simple-sendfile-doc, 
> libghc-streaming-commons-doc, libghc-time-manager-doc, 
> libghc-unix-compat-doc, libghc-unli

Bug#1069458: dune-uggrid: FTBFS on armhf: tests fail

2024-04-20 Thread Lucas Nussbaum
Source: dune-uggrid
Version: 2.9.0-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-armhf

Hi,

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


Relevant part (hopefully):
> make[5]: Entering directory '/<>/build'
> make[5]: Nothing to be done for 'CMakeFiles/build_tests.dir/build'.
> make[5]: Leaving directory '/<>/build'
> [100%] Built target build_tests
> make[4]: Leaving directory '/<>/build'
> /usr/bin/cmake -E cmake_progress_start /<>/build/CMakeFiles 0
> make[3]: Leaving directory '/<>/build'
> make[2]: Leaving directory '/<>/build'
> cd build; PATH=/<>/debian/tmp-test:$PATH /usr/bin/dune-ctest 
>Site: ip-10-84-234-180
>Build name: Linux-c++
> Create new tag: 20240420-0421 - Experimental
> Test project /<>/build
> Start 1: rm3-tetrahedron-rules-test
> 1/3 Test #1: rm3-tetrahedron-rules-test ...***Failed0.02 sec
> --
> Sorry!  You were supposed to get help about:
> pmix_init:startup:internal-failure
> But I couldn't open the help file:
> /usr/share/pmix/help-pmix-runtime.txt: No such file or directory.  Sorry!
> --
> [ip-10-84-234-180:3635872] PMIX ERROR: NOT-FOUND in file 
> ../../../../../../../../opal/mca/pmix/pmix3x/pmix/src/server/pmix_server.c at 
> line 237
> [ip-10-84-234-180:3635871] [[INVALID],INVALID] ORTE_ERROR_LOG: Unable to 
> start a daemon on the local node in file 
> ../../../../../../orte/mca/ess/singleton/ess_singleton_module.c at line 716
> [ip-10-84-234-180:3635871] [[INVALID],INVALID] ORTE_ERROR_LOG: Unable to 
> start a daemon on the local node in file 
> ../../../../../../orte/mca/ess/singleton/ess_singleton_module.c at line 172
> --
> It looks like orte_init failed for some reason; your parallel process is
> likely to abort.  There are many reasons that a parallel process can
> fail during orte_init; some of which are due to configuration or
> environment problems.  This failure appears to be an internal failure;
> here's some additional information (which may only be relevant to an
> Open MPI developer):
> 
>   orte_ess_init failed
>   --> Returned value Unable to start a daemon on the local node (-127) 
> instead of ORTE_SUCCESS
> --
> --
> It looks like MPI_INIT failed for some reason; your parallel process is
> likely to abort.  There are many reasons that a parallel process can
> fail during MPI_INIT; some of which are due to configuration or environment
> problems.  This failure appears to be an internal failure; here's some
> additional information (which may only be relevant to an Open MPI
> developer):
> 
>   ompi_mpi_init: ompi_rte_init failed
>   --> Returned "Unable to start a daemon on the local node" (-127) instead of 
> "Success" (0)
> --
> *** An error occurred in MPI_Init
> *** on a NULL communicator
> *** MPI_ERRORS_ARE_FATAL (processes in this communicator will now abort,
> ***and potentially your MPI job)
> [ip-10-84-234-180:3635871] Local abort before MPI_INIT completed completed 
> successfully, but am not able to aggregate error messages, and not able to 
> guarantee that all other processes were killed!
> 
> Start 2: test-fifo
> 2/3 Test #2: test-fifo    Passed0.00 sec
> Start 3: testbtree
> 3/3 Test #3: testbtree    Passed0.00 sec
> 
> 67% tests passed, 1 tests failed out of 3
> 
> Total Test time (real) =   0.03 sec
> 
> The following tests FAILED:
> 1 - rm3-tetrahedron-rules-test (Failed)
> Errors while running CTest
> ==
> Name:  rm3-tetrahedron-rules-test
> FullName:  ./dune/uggrid/gm/rm3-tetrahedron-rules-test
> Status:FAILED
> 
> JUnit report for CTest results written to 
> /<>/build/junit/cmake.xml
> make[1]: *** [/usr/share/dune/dune-debian.mk:39: override_dh_auto_test] Error 
> 1


The full build log is available from:
http://qa-logs.debian.net/2024/04/20/dune-uggrid_2.9.0-2_unstable-armhf.log

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

Bug#1069456: mumps: FTBFS on armhf: tests fail

2024-04-20 Thread Lucas Nussbaum
Source: mumps
Version: 5.6.2-2.1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-armhf

Hi,

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


Relevant part (hopefully):
> make[2]: Entering directory '/<>/examples'
> mpifort -g -O2 -ffile-prefix-map=/<>/examples=. 
> -fstack-protector-strong -fstack-clash-protection   -Dintel_  -I. 
> -I../include -I../src  -c csimpletest.F -o csimpletest.o
> mpifort -o csimpletest -Wl,-z,relro  csimpletest.o  -L/<>/lib 
> -lcmumps -lmumps_common -L/<>/lib -lpord -lscalapack-openmpi 
> -llapack-lblas -lpthread
> mpifort -g -O2 -ffile-prefix-map=/<>/examples=. 
> -fstack-protector-strong -fstack-clash-protection   -Dintel_  -I. 
> -I../include -I../src  -c csimpletest_save_restore.F -o 
> csimpletest_save_restore.o
> mpifort -o csimpletest_save_restore -Wl,-z,relro  csimpletest_save_restore.o  
> -L/<>/lib -lcmumps -lmumps_common -L/<>/lib -lpord 
> -lscalapack-openmpi -llapack  -lblas -lpthread
> mpifort -g -O2 -ffile-prefix-map=/<>/examples=. 
> -fstack-protector-strong -fstack-clash-protection   -Dintel_  -I. 
> -I../include -I../src  -c zsimpletest.F -o zsimpletest.o
> mpifort -o zsimpletest -Wl,-z,relro  zsimpletest.o  -L/<>/lib 
> -lzmumps -lmumps_common -L/<>/lib -lpord -lscalapack-openmpi 
> -llapack-lblas -lpthread
> mpifort -g -O2 -ffile-prefix-map=/<>/examples=. 
> -fstack-protector-strong -fstack-clash-protection   -Dintel_  -I. 
> -I../include -I../src  -c zsimpletest_save_restore.F -o 
> zsimpletest_save_restore.o
> mpifort -o zsimpletest_save_restore -Wl,-z,relro  zsimpletest_save_restore.o  
> -L/<>/lib -lzmumps -lmumps_common -L/<>/lib -lpord 
> -lscalapack-openmpi -llapack  -lblas -lpthread
> mpifort -g -O2 -ffile-prefix-map=/<>/examples=. 
> -fstack-protector-strong -fstack-clash-protection   -Dintel_  -I. 
> -I../include -I../src  -c ssimpletest.F -o ssimpletest.o
> mpifort -o ssimpletest -Wl,-z,relro  ssimpletest.o  -L/<>/lib 
> -lsmumps -lmumps_common -L/<>/lib -lpord -lscalapack-openmpi 
> -llapack-lblas -lpthread
> mpifort -g -O2 -ffile-prefix-map=/<>/examples=. 
> -fstack-protector-strong -fstack-clash-protection   -Dintel_  -I. 
> -I../include -I../src  -c ssimpletest_save_restore.F -o 
> ssimpletest_save_restore.o
> mpifort -o ssimpletest_save_restore -Wl,-z,relro  ssimpletest_save_restore.o  
> -L/<>/lib -lsmumps -lmumps_common -L/<>/lib -lpord 
> -lscalapack-openmpi -llapack  -lblas -lpthread
> mpifort -g -O2 -ffile-prefix-map=/<>/examples=. 
> -fstack-protector-strong -fstack-clash-protection   -Dintel_  -I. 
> -I../include -I../src  -c dsimpletest.F -o dsimpletest.o
> mpifort -o dsimpletest -Wl,-z,relro  dsimpletest.o  -L/<>/lib 
> -ldmumps -lmumps_common -L/<>/lib -lpord -lscalapack-openmpi 
> -llapack-lblas -lpthread
> mpifort -g -O2 -ffile-prefix-map=/<>/examples=. 
> -fstack-protector-strong -fstack-clash-protection   -Dintel_  -I. 
> -I../include -I../src  -c dsimpletest_save_restore.F -o 
> dsimpletest_save_restore.o
> mpifort -o dsimpletest_save_restore -Wl,-z,relro  dsimpletest_save_restore.o  
> -L/<>/lib -ldmumps -lmumps_common -L/<>/lib -lpord 
> -lscalapack-openmpi -llapack  -lblas -lpthread
> mpicc -g -O2 -Werror=implicit-function-declaration 
> -ffile-prefix-map=/<>/examples=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security-DAdd_ -I. 
> -I../include -I../src  -c c_example_save_restore.c -o c_example_save_restore.o
> mpifort -o c_example_save_restore -Wl,-z,relro  c_example_save_restore.o 
> -L/<>/lib -ldmumps -lmumps_common -L/<>/lib -lpord 
> -lscalapack-openmpi -llapack  -lblas -lpthread
> mpicc -g -O2 -Werror=implicit-function-declaration 
> -ffile-prefix-map=/<>/examples=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security-DAdd_ -I. 
> -I../include -I../src  -c c_example.c -o c_example.o
> mpifort -o c_example -Wl,-z,relro  c_example.o -L/<>/lib 
> -ldmumps -lmumps_common -L/<>/lib -lpord -lscalapack-openmpi 
> -llapack  -lmpi  -lblas -lpthread
> mpifort -g -O2 -ffile-prefix-map=/<>/examples=. 
> -fstack-protector-strong -fstack-clash-protection   -Dintel_  -I. 
> -I../include -I../src  -c multiple_arithmetics_example.F -o 
> multiple_arithmetics_example.o
> mpifort -o multiple_arithmetics_example -Wl,-z,relro  
> multiple_arithmetics_example.o -L/<>/lib -lsmumps -lmumps_common 
> -L/<>/lib -ldmumps -lmumps_common -L/<>/lib 
> -lcmumps -lmumps_common -L/<>/lib -lzmumps -lmumps

Bug#1069460: bitshuffle: FTBFS on armhf: tests fail

2024-04-20 Thread Lucas Nussbaum
Source: bitshuffle
Version: 0.5.1-1.2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-armhf

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> mpirun --allow-run-as-root -n 1 dh_auto_test
> --
> Sorry!  You were supposed to get help about:
> pmix_init:startup:internal-failure
> But I couldn't open the help file:
> /usr/share/pmix/help-pmix-runtime.txt: No such file or directory.  Sorry!
> --
> [ip-10-84-234-171:2111213] PMIX ERROR: NOT-FOUND in file 
> ../../../../../../../../opal/mca/pmix/pmix3x/pmix/src/server/pmix_server.c at 
> line 237
> make[1]: *** [debian/rules:60: override_dh_auto_test] Error 1


The full build log is available from:
http://qa-logs.debian.net/2024/04/20/bitshuffle_0.5.1-1.2_unstable-armhf.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240420;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240420=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 mark 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.



Bug#1069459: haskell-hpack: FTBFS on armhf: unsatisfiable build-dependencies

2024-04-20 Thread Lucas Nussbaum
Source: haskell-hpack
Version: 0.35.2-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-armhf

Hi,

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


Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: cdbs, debhelper (>= 10), ghc (>= 8.4.3), ghc-prof, 
> haskell-devscripts (>= 0.13), libghc-glob-dev (>= 0.9.0), libghc-glob-prof, 
> libghc-aeson-dev (>= 1.4.3.0), libghc-aeson-prof, libghc-bifunctors-dev, 
> libghc-bifunctors-prof, libghc-cryptonite-dev, libghc-cryptonite-prof, 
> libghc-http-client-dev, libghc-http-client-prof, libghc-http-client-tls-dev, 
> libghc-http-client-tls-prof, libghc-http-types-dev, libghc-http-types-prof, 
> libghc-infer-license-dev (>= 0.2.0), libghc-infer-license-dev (<< 0.3), 
> libghc-infer-license-prof, libghc-scientific-dev, libghc-scientific-prof, 
> libghc-unordered-containers-dev, libghc-unordered-containers-prof, 
> libghc-vector-dev, libghc-vector-prof, libghc-yaml-dev (>= 0.10.0), 
> libghc-yaml-prof, libghc-hunit-dev (>= 1.6.0.0), libghc-hunit-prof, 
> libghc-quickcheck2-dev, libghc-hspec-dev (>= 2), libghc-hspec-dev (<< 3), 
> libghc-interpolate-dev, libghc-mockery-dev (>= 0.3), libghc-temporary-dev, 
> libghc-temporary-prof, build-essential, fakeroot, ghc-doc, libghc-glob-doc, 
> libghc-aeson-doc, libghc-bifunctors-doc, libghc-cryptonite-doc, 
> libghc-http-client-doc, libghc-http-client-tls-doc, libghc-http-types-doc, 
> libghc-infer-license-doc, libghc-scientific-doc, libghc-temporary-doc, 
> libghc-unordered-containers-doc, libghc-vector-doc, libghc-yaml-doc
> Filtered Build-Depends: cdbs, debhelper (>= 10), ghc (>= 8.4.3), ghc-prof, 
> haskell-devscripts (>= 0.13), libghc-glob-dev (>= 0.9.0), libghc-glob-prof, 
> libghc-aeson-dev (>= 1.4.3.0), libghc-aeson-prof, libghc-bifunctors-dev, 
> libghc-bifunctors-prof, libghc-cryptonite-dev, libghc-cryptonite-prof, 
> libghc-http-client-dev, libghc-http-client-prof, libghc-http-client-tls-dev, 
> libghc-http-client-tls-prof, libghc-http-types-dev, libghc-http-types-prof, 
> libghc-infer-license-dev (>= 0.2.0), libghc-infer-license-dev (<< 0.3), 
> libghc-infer-license-prof, libghc-scientific-dev, libghc-scientific-prof, 
> libghc-unordered-containers-dev, libghc-unordered-containers-prof, 
> libghc-vector-dev, libghc-vector-prof, libghc-yaml-dev (>= 0.10.0), 
> libghc-yaml-prof, libghc-hunit-dev (>= 1.6.0.0), libghc-hunit-prof, 
> libghc-quickcheck2-dev, libghc-hspec-dev (>= 2), libghc-hspec-dev (<< 3), 
> libghc-interpolate-dev, libghc-mockery-dev (>= 0.3), libghc-temporary-dev, 
> libghc-temporary-prof, build-essential, fakeroot, ghc-doc, libghc-glob-doc, 
> libghc-aeson-doc, libghc-bifunctors-doc, libghc-cryptonite-doc, 
> libghc-http-client-doc, libghc-http-client-tls-doc, libghc-http-types-doc, 
> libghc-infer-license-doc, libghc-scientific-doc, libghc-temporary-doc, 
> libghc-unordered-containers-doc, libghc-vector-doc, libghc-yaml-doc
> dpkg-deb: building package 'sbuild-build-depends-main-dummy' in 
> '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'.
> Ign:1 copy:/<>/apt_archive ./ InRelease
> Get:2 copy:/<>/apt_archive ./ Release [615 B]
> Ign:3 copy:/<>/apt_archive ./ Release.gpg
> Get:4 copy:/<>/apt_archive ./ Sources [1865 B]
> Get:5 copy:/<>/apt_archive ./ Packages [1875 B]
> Fetched 4355 B in 0s (0 B/s)
> Reading package lists...
> Reading package lists...
> 
> Install main build dependencies (apt-based resolver)
> 
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  libghc-http-client-tls-dev : Depends: libghc-base-dev-4.17.2.0-38dbb but it 
> is not installable
>   Depends: libghc-bytestring-dev-0.11.5.2-302b4 
> but it is not installable
>   Depends: 
> libghc-case-insensitive-dev-1.2.1.0-366b1 but it is not installab

Bug#1069453: tcmu: FTBFS on armhf: build-dependency not installable: librados-dev

2024-04-20 Thread Lucas Nussbaum
Source: tcmu
Version: 1.5.4-6
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-armhf

Hi,

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


Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: cmake, debhelper-compat (= 13), kmod, libglib2.0-dev, 
> libkmod-dev, libnl-genl-3-dev, librados-dev, pkgconf, systemd-dev, 
> zlib1g-dev, build-essential, fakeroot
> Filtered Build-Depends: cmake, debhelper-compat (= 13), kmod, libglib2.0-dev, 
> libkmod-dev, libnl-genl-3-dev, librados-dev, pkgconf, systemd-dev, 
> zlib1g-dev, build-essential, fakeroot
> dpkg-deb: building package 'sbuild-build-depends-main-dummy' in 
> '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'.
> Ign:1 copy:/<>/apt_archive ./ InRelease
> Get:2 copy:/<>/apt_archive ./ Release [609 B]
> Ign:3 copy:/<>/apt_archive ./ Release.gpg
> Get:4 copy:/<>/apt_archive ./ Sources [794 B]
> Get:5 copy:/<>/apt_archive ./ Packages [757 B]
> Fetched 2160 B in 0s (0 B/s)
> Reading package lists...
> Reading package lists...
> 
> Install main build dependencies (apt-based resolver)
> 
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  sbuild-build-depends-main-dummy : Depends: librados-dev but it is not 
> installable
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.


The full build log is available from:
http://qa-logs.debian.net/2024/04/20/tcmu_1.5.4-6_unstable-armhf.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240420;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240420=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 mark 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.



Bug#1069454: libalog: FTBFS on armhf: build-dependency not installable: libahven-dev

2024-04-20 Thread Lucas Nussbaum
Source: libalog
Version: 0.6.2-5
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-armhf

Hi,

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


Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper-compat (= 13), build-essential, fakeroot, 
> dh-ada-library (>= 9.1), dh-sequence-ada-library, gnat (>= 13), gprbuild, 
> libahven-dev, asciidoctor, ruby-pygments.rb, scour
> Filtered Build-Depends: debhelper-compat (= 13), build-essential, fakeroot, 
> dh-ada-library (>= 9.1), dh-sequence-ada-library, gnat (>= 13), gprbuild, 
> libahven-dev, asciidoctor, ruby-pygments.rb, scour
> dpkg-deb: building package 'sbuild-build-depends-main-dummy' in 
> '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'.
> Ign:1 copy:/<>/apt_archive ./ InRelease
> Get:2 copy:/<>/apt_archive ./ Release [609 B]
> Ign:3 copy:/<>/apt_archive ./ Release.gpg
> Get:4 copy:/<>/apt_archive ./ Sources [782 B]
> Get:5 copy:/<>/apt_archive ./ Packages [775 B]
> Fetched 2166 B in 0s (0 B/s)
> Reading package lists...
> Reading package lists...
> 
> Install main build dependencies (apt-based resolver)
> 
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  sbuild-build-depends-main-dummy : Depends: libahven-dev but it is not 
> installable
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.


The full build log is available from:
http://qa-logs.debian.net/2024/04/20/libalog_0.6.2-5_unstable-armhf.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240420;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240420=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 mark 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.



Bug#1069468: pcscada: FTBFS on armhf: build-dependency not installable: libahven-dev

2024-04-20 Thread Lucas Nussbaum
Source: pcscada
Version: 0.7.7-6
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-armhf

Hi,

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


Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: asciidoctor, debhelper-compat (= 13), dh-ada-library 
> (>= 9.1), dh-sequence-ada-library, gnat (>= 13.1), gprbuild, libahven-dev, 
> libpcsclite-dev, ruby-pygments.rb, build-essential, fakeroot
> Filtered Build-Depends: asciidoctor, debhelper-compat (= 13), dh-ada-library 
> (>= 9.1), dh-sequence-ada-library, gnat (>= 13.1), gprbuild, libahven-dev, 
> libpcsclite-dev, ruby-pygments.rb, build-essential, fakeroot
> dpkg-deb: building package 'sbuild-build-depends-main-dummy' in 
> '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'.
> Ign:1 copy:/<>/apt_archive ./ InRelease
> Get:2 copy:/<>/apt_archive ./ Release [609 B]
> Ign:3 copy:/<>/apt_archive ./ Release.gpg
> Get:4 copy:/<>/apt_archive ./ Sources [755 B]
> Get:5 copy:/<>/apt_archive ./ Packages [787 B]
> Fetched 2151 B in 0s (0 B/s)
> Reading package lists...
> Reading package lists...
> 
> Install main build dependencies (apt-based resolver)
> 
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  sbuild-build-depends-main-dummy : Depends: libahven-dev but it is not 
> installable
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.


The full build log is available from:
http://qa-logs.debian.net/2024/04/20/pcscada_0.7.7-6_unstable-armhf.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240420;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240420=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 mark 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.



Bug#1069467: gprbuild: FTBFS on armhf: unsatisfiable build-dependencies: gnat-13-cab06c16, libxmlada-unicode-dev (= 24.0.0-2), gnat-13-cab06c16, libxmlada-unicode-dev (= 24.0.0-2), gnat-13-cab06c16, l

2024-04-20 Thread Lucas Nussbaum
Source: gprbuild
Version: 2024.1.20231009-4
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-armhf

Hi,

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


Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper-compat (= 13), build-essential, fakeroot, 
> dh-ada-library (>= 9.1), dh-sequence-ada-library, gnat (>= 13), 
> libxmlada-dom-dev, libxmlada-input-dev, libxmlada-sax-dev, 
> libxmlada-schema-dev, dh-sequence-sphinxdoc, latexmk, python3-sphinx, 
> texinfo, tex-gyre, texlive-fonts-recommended, texlive-latex-extra
> Filtered Build-Depends: debhelper-compat (= 13), build-essential, fakeroot, 
> dh-ada-library (>= 9.1), dh-sequence-ada-library, gnat (>= 13), 
> libxmlada-dom-dev, libxmlada-input-dev, libxmlada-sax-dev, 
> libxmlada-schema-dev, dh-sequence-sphinxdoc, latexmk, python3-sphinx, 
> texinfo, tex-gyre, texlive-fonts-recommended, texlive-latex-extra
> dpkg-deb: building package 'sbuild-build-depends-main-dummy' in 
> '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'.
> Ign:1 copy:/<>/apt_archive ./ InRelease
> Get:2 copy:/<>/apt_archive ./ Release [609 B]
> Ign:3 copy:/<>/apt_archive ./ Release.gpg
> Get:4 copy:/<>/apt_archive ./ Sources [916 B]
> Get:5 copy:/<>/apt_archive ./ Packages [910 B]
> Fetched 2435 B in 0s (0 B/s)
> Reading package lists...
> Reading package lists...
> 
> Install main build dependencies (apt-based resolver)
> 
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  libxmlada-dom-dev : Depends: gnat-13-cab06c16 but it is not installable
>  Depends: libxmlada-unicode-dev (= 24.0.0-2) but it is 
> not going to be installed
>  libxmlada-input-dev : Depends: gnat-13-cab06c16 but it is not installable
>Depends: libxmlada-unicode-dev (= 24.0.0-2) but it is 
> not going to be installed
>  libxmlada-sax-dev : Depends: gnat-13-cab06c16 but it is not installable
>  Depends: libxmlada-unicode-dev (= 24.0.0-2) but it is 
> not going to be installed
>  libxmlada-schema-dev : Depends: gnat-13-cab06c16 but it is not installable
> Depends: libxmlada-unicode-dev (= 24.0.0-2) but it is 
> not going to be installed
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.


The full build log is available from:
http://qa-logs.debian.net/2024/04/20/gprbuild_2024.1.20231009-4_unstable-armhf.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240420;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240420=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 mark 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.



Bug#1069469: anet: FTBFS on armhf: build-dependency not installable: libahven-dev

2024-04-20 Thread Lucas Nussbaum
Source: anet
Version: 0.5.0-3
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-armhf

Hi,

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


Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: asciidoctor, debhelper-compat (= 13), dh-ada-library 
> (>= 9.1), dh-sequence-ada-library, gnat (>= 13.1), gprbuild, libahven-dev, 
> ruby-pygments.rb, build-essential, fakeroot
> Filtered Build-Depends: asciidoctor, debhelper-compat (= 13), dh-ada-library 
> (>= 9.1), dh-sequence-ada-library, gnat (>= 13.1), gprbuild, libahven-dev, 
> ruby-pygments.rb, build-essential, fakeroot
> dpkg-deb: building package 'sbuild-build-depends-main-dummy' in 
> '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'.
> Ign:1 copy:/<>/apt_archive ./ InRelease
> Get:2 copy:/<>/apt_archive ./ Release [609 B]
> Ign:3 copy:/<>/apt_archive ./ Release.gpg
> Get:4 copy:/<>/apt_archive ./ Sources [738 B]
> Get:5 copy:/<>/apt_archive ./ Packages [770 B]
> Fetched 2117 B in 0s (0 B/s)
> Reading package lists...
> Reading package lists...
> 
> Install main build dependencies (apt-based resolver)
> 
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  sbuild-build-depends-main-dummy : Depends: libahven-dev but it is not 
> installable
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.


The full build log is available from:
http://qa-logs.debian.net/2024/04/20/anet_0.5.0-3_unstable-armhf.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240420;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240420=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 mark 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.



  1   2   3   4   >