Bug#1067055: marked as done (openmpi: error: implicit declaration of function 'OPAL_THREAD_ADD_FETCH64')

[Debian Bug Tracking System]

Your message dated Thu, 04 Apr 2024 05:34:40 +
with message-id 
and subject line Bug#1067055: fixed in openmpi 4.1.6-8
has caused the Debian Bug report #1067055,
regarding openmpi: error: implicit declaration of function 
'OPAL_THREAD_ADD_FETCH64'
to be marked as done.

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

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


-- 
1067055: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067055
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: openmpi
Version: 4.1.6-7
Severity: serious
Justification: ftbfs
Tags: ftbfs
Tag: ftbfs
X-Debbugs-Cc: t...@mirbsd.de

[…]
libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I../../../../../../opal/mca/btl/ofi 
-I../../../../opal/include -I../../../../ompi/include 
-I../../../../oshmem/include 
-I../../../../opal/mca/hwloc/hwloc201/hwloc/include/private/autogen 
-I../../../../opal/mca/hwloc/hwloc201/hwloc/include/hwloc/autogen 
-I../../../../ompi/mpiext/cuda/c -I../../../../../.. -I../../../.. 
-I../../../../../../opal/include -I../../../../../../orte/include 
-I../../../../orte/include -I../../../../../../ompi/include 
-I../../../../../../oshmem/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 
-D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/local/include 
-I/usr/local/include -DNDEBUG -g -O2 -Werror=implicit-function-declaration 
-ffile-prefix-map=/tmp/buildd/openmpi-4.1.6=. -fstack-protector-strong -Wformat 
-Werror=format-security -O3 -finline-functions -fno-strict-aliasing -c 
../../../../../../opal/mca/btl/ofi/btl_ofi_rdma.c  -fPIC -DPIC -o 
.libs/btl_ofi_rdma.o
In file included from ../../../../../../opal/mca/btl/ofi/btl_ofi_rdma.c:14:
../../../../../../opal/mca/btl/ofi/btl_ofi_rdma.c: In function 
'mca_btl_ofi_get':
../../../../../../opal/mca/btl/ofi/btl_ofi_rdma.h:33:13: error: implicit 
declaration of function 'OPAL_THREAD_ADD_FETCH64'; did you mean 
'OPAL_THREAD_ADD_FETCH32'? [-Werror=implicit-function-declaration]
   33 | OPAL_THREAD_ADD_FETCH64(&(module)->outstanding_rdma, 1);
\
  | ^~~
../../../../../../opal/mca/btl/ofi/btl_ofi_rdma.c:70:5: note: in expansion of 
macro 'MCA_BTL_OFI_NUM_RDMA_INC'
   70 | MCA_BTL_OFI_NUM_RDMA_INC(ofi_btl);
  | ^~~~
../../../../../../opal/mca/btl/ofi/btl_ofi_rdma.c:82:40: warning: cast from 
pointer to integer of different size [-Wpointer-to-int-cast]
   82 | remote_address = (remote_address - (uint64_t) 
remote_handle->base_addr);
  |^
../../../../../../opal/mca/btl/ofi/btl_ofi_rdma.c: In function 
'mca_btl_ofi_put':
../../../../../../opal/mca/btl/ofi/btl_ofi_rdma.c:132:40: warning: cast from 
pointer to integer of different size [-Wpointer-to-int-cast]
  132 | remote_address = (remote_address - (uint64_t) 
remote_handle->base_addr);
  |^
cc1: some warnings being treated as errors
make[4]: *** [Makefile:1946: btl_ofi_rdma.lo] Error 1
make[4]: Leaving directory 
'/tmp/buildd/openmpi-4.1.6/debian/build-gfortran/opal/mca/btl/ofi'
--- End Message ---
--- Begin Message ---
Source: openmpi
Source-Version: 4.1.6-8
Done: Alastair McKinstry 

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

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

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

Debian distribution maintenance software
pp.
Alastair McKinstry  (supplier of updated openmpi package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 03 Apr 2024 14:34:22 +0100
Source: openmpi
Architecture: source
Version: 4.1.6-8
Distribution: unstable
Urgency: medium
Maintainer: Alastair McKinstry 
Changed-By: Alastair McKinstry 
Closes: 1067055
Changes:
 openmpi (4.1.6-8) unstable; urgency=medium
 .
   * Only dep on libpmix on 64-bit systems.
   * Disable modules that need 64-bit atomic ops on 32-bit systems.
 Closes: #1067055
Checksums-Sha1:
 18a9e7299bce91f5a3d0553f3b055ef83d8b4019 2829 openmpi_4.1.6-8.dsc
 960a2b1a89f713d327ad100dca0b0abb23e0bad2 69696 openmpi_4.1.6-8.debian.tar.xz
Checksums-Sha256:
 465eb0221f44f810ca8d6405edb1bc60245c533492e63f17bc1401031fcfe863 

Bug#1068347: marked as done (nodejs: CVE-2024-27983 CVE-2024-27982)

[Debian Bug Tracking System]

Your message dated Thu, 4 Apr 2024 06:48:42 +0200
with message-id 
and subject line [ftpmas...@ftp-master.debian.org: Accepted nodejs 
18.20.1+dfsg-1 (source) into unstable]
has caused the Debian Bug report #1068347,
regarding nodejs: CVE-2024-27983 CVE-2024-27982
to be marked as done.

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

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


-- 
1068347: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068347
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nodejs
X-Debbugs-CC: t...@security.debian.org
Severity: grave
Tags: security

Hi,

The following vulnerabilities were published for nodejs.

CVE-2024-27983[0]:
https://nodejs.org/en/blog/vulnerability/april-2024-security-releases/

CVE-2024-27982[1]:
https://nodejs.org/en/blog/vulnerability/april-2024-security-releases/


If you fix the vulnerabilities please also make sure to include the
CVE (Common Vulnerabilities & Exposures) ids in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2024-27983
https://www.cve.org/CVERecord?id=CVE-2024-27983
[1] https://security-tracker.debian.org/tracker/CVE-2024-27982
https://www.cve.org/CVERecord?id=CVE-2024-27982

Please adjust the affected versions in the BTS as needed.
--- End Message ---
--- Begin Message ---
Source: nodejs
Source-Version: 18.20.1+dfsg-1

- Forwarded message from Debian FTP Masters 
 -

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 03 Apr 2024 16:50:38 +0200
Source: nodejs
Architecture: source
Version: 18.20.1+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Jérémy Lal 
Changes:
 nodejs (18.20.1+dfsg-1) unstable; urgency=medium
 .
   * New upstream version 18.20.1+dfsg
 + CVE-2024-27983: HTTP/2 server crash (High)
 + CVE-2024-27982: HTTP Request Smuggling (Medium)
   * Breaks libnode108, not 109
   * copyright: remove file
   * Drop build/test_dns_resolveany_bad_ancount.patch, applied
Checksums-Sha1:
 6a1c634577a5c44ffc9a8add91de854f8d52f3c6 4359 nodejs_18.20.1+dfsg-1.dsc
 2540b9b84f230689afcbf507a307d46d4ef2a411 269724 
nodejs_18.20.1+dfsg.orig-ada.tar.xz
 fe2823889f88c0ba801ec4565b302dc987f27168 274360 
nodejs_18.20.1+dfsg.orig-types-node.tar.xz
 224708ebbaaada74e786059a276dca0054fabf33 29305332 
nodejs_18.20.1+dfsg.orig.tar.xz
 85cf8906b32eaf766c2b08690fd24be97ddc619a 163104 
nodejs_18.20.1+dfsg-1.debian.tar.xz
 ffe31e7755d29173054a343fa72cc978878d4e8e 10916 
nodejs_18.20.1+dfsg-1_source.buildinfo
Checksums-Sha256:
 b8eeb8d2a7cc17dc772fa9f0817d8d294842eb8e3ea4cdf34cc59fd29baf768a 4359 
nodejs_18.20.1+dfsg-1.dsc
 0c3caa8771a2bc6ac5d32912d07383dcae8a0cf145ed6f7017cbf6b41478acd2 269724 
nodejs_18.20.1+dfsg.orig-ada.tar.xz
 ea406dd59b86fb2ab96043231d9ff763611c0fb08d5cabbaeccad770d1b34068 274360 
nodejs_18.20.1+dfsg.orig-types-node.tar.xz
 558c42f89f57a56e8d1e131fb6bb0a40f1cc844e52e2393837f932c0d8c8b31b 29305332 
nodejs_18.20.1+dfsg.orig.tar.xz
 9213d005e8a8e4e758db1e4f3f13eb22f611ce2be1d48d558cb4558d946f7f30 163104 
nodejs_18.20.1+dfsg-1.debian.tar.xz
 18067729aa2e52618b01a9dc2c6bd1dfbdbb469cce8a5b8f379fb9294947fea6 10916 
nodejs_18.20.1+dfsg-1_source.buildinfo
Files:
 0e064ee9907fcb2b19f8f6fe88215a53 4359 javascript optional 
nodejs_18.20.1+dfsg-1.dsc
 327a080764e93ab10a593efba5b84fd3 269724 javascript optional 
nodejs_18.20.1+dfsg.orig-ada.tar.xz
 93414acee8286f9dc2e1b649cda05b09 274360 javascript optional 
nodejs_18.20.1+dfsg.orig-types-node.tar.xz
 dae02efb441915a83486babec21c8186 29305332 javascript optional 
nodejs_18.20.1+dfsg.orig.tar.xz
 175f3688d3380ceb1b3fe3fbf65fe59f 163104 javascript optional 
nodejs_18.20.1+dfsg-1.debian.tar.xz
 06d37a9966050b373c0e0b13d103f9a3 10916 javascript optional 
nodejs_18.20.1+dfsg-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJGBAEBCAAwFiEEA8Tnq7iA9SQwbkgVZhHAXt0583QFAmYNu8wSHGthcG91ZXJA
bWVsaXgub3JnAAoJEGYRwF7dOfN0iF8P/jgSVspzx+1vifQxluwWLsWXJSp7jgxr
f1iOvKrmf5rXb7W1FICDoa53bOd+SmIL4Lbmd066+38k90n0zKEK61hpZoA84F6C
jYekdGsGNPGoJeygJjxK99+ZEUvAAsBmtOvq5l7aLAHQJskPXZSD7zRxRbvoAt9k
PRPQKh7uqreV3LoJGOMHnSdxUHNroM89oSqzx73nLyvfjW4+/xWkXIf3+DBoycFr
X0b9PaQmlRWH3bWdYBTb5GXMNL6qkQD41YdN4KpJd3oe17qUVBfI9+VssJuN3Gii
EQ6DQni0E4nPw9AmDG9nACjbqq1QOfWiJRmCZ6bHtPxRrTdaFUJeIhxymBqFq6V+
u4hGTgLJno2HQJ/8dPNIK2cYI/NbSRhBSIx62OPvyAEeSLAUJ9coDvoZ5/euazwS
YFxlLnp0+/FqwXR2LWAw+Za5SNdSPoTbbYyE93yxBtTFBAhq7XIIf2IoEkgLkV+z
7jYXn+DGUFnthHz1e4XAfrIHagMn/hfYgyrpzp37UyLRhY2Rk3t8/Brt44lcE001
rREGxh8QYR7ECimOdpobzoXk4JbmFf2VlvYxl7mVTzRsTeuBHaHX1VH+Dy4qLGfK
vuUBF7bjIeMCkCXrahu3kW3DFsWopqcmAGIOk/mA4iQsDvMzk7hfqNqdI/JbMPPu

Bug#1068347: [ftpmas...@ftp-master.debian.org: Accepted nodejs 18.20.1+dfsg-1 (source) into unstable]

[Salvatore Bonaccorso]

Source: nodejs
Source-Version: 18.20.1+dfsg-1

- Forwarded message from Debian FTP Masters 
 -

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 03 Apr 2024 16:50:38 +0200
Source: nodejs
Architecture: source
Version: 18.20.1+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Jérémy Lal 
Changes:
 nodejs (18.20.1+dfsg-1) unstable; urgency=medium
 .
   * New upstream version 18.20.1+dfsg
 + CVE-2024-27983: HTTP/2 server crash (High)
 + CVE-2024-27982: HTTP Request Smuggling (Medium)
   * Breaks libnode108, not 109
   * copyright: remove file
   * Drop build/test_dns_resolveany_bad_ancount.patch, applied
Checksums-Sha1:
 6a1c634577a5c44ffc9a8add91de854f8d52f3c6 4359 nodejs_18.20.1+dfsg-1.dsc
 2540b9b84f230689afcbf507a307d46d4ef2a411 269724 
nodejs_18.20.1+dfsg.orig-ada.tar.xz
 fe2823889f88c0ba801ec4565b302dc987f27168 274360 
nodejs_18.20.1+dfsg.orig-types-node.tar.xz
 224708ebbaaada74e786059a276dca0054fabf33 29305332 
nodejs_18.20.1+dfsg.orig.tar.xz
 85cf8906b32eaf766c2b08690fd24be97ddc619a 163104 
nodejs_18.20.1+dfsg-1.debian.tar.xz
 ffe31e7755d29173054a343fa72cc978878d4e8e 10916 
nodejs_18.20.1+dfsg-1_source.buildinfo
Checksums-Sha256:
 b8eeb8d2a7cc17dc772fa9f0817d8d294842eb8e3ea4cdf34cc59fd29baf768a 4359 
nodejs_18.20.1+dfsg-1.dsc
 0c3caa8771a2bc6ac5d32912d07383dcae8a0cf145ed6f7017cbf6b41478acd2 269724 
nodejs_18.20.1+dfsg.orig-ada.tar.xz
 ea406dd59b86fb2ab96043231d9ff763611c0fb08d5cabbaeccad770d1b34068 274360 
nodejs_18.20.1+dfsg.orig-types-node.tar.xz
 558c42f89f57a56e8d1e131fb6bb0a40f1cc844e52e2393837f932c0d8c8b31b 29305332 
nodejs_18.20.1+dfsg.orig.tar.xz
 9213d005e8a8e4e758db1e4f3f13eb22f611ce2be1d48d558cb4558d946f7f30 163104 
nodejs_18.20.1+dfsg-1.debian.tar.xz
 18067729aa2e52618b01a9dc2c6bd1dfbdbb469cce8a5b8f379fb9294947fea6 10916 
nodejs_18.20.1+dfsg-1_source.buildinfo
Files:
 0e064ee9907fcb2b19f8f6fe88215a53 4359 javascript optional 
nodejs_18.20.1+dfsg-1.dsc
 327a080764e93ab10a593efba5b84fd3 269724 javascript optional 
nodejs_18.20.1+dfsg.orig-ada.tar.xz
 93414acee8286f9dc2e1b649cda05b09 274360 javascript optional 
nodejs_18.20.1+dfsg.orig-types-node.tar.xz
 dae02efb441915a83486babec21c8186 29305332 javascript optional 
nodejs_18.20.1+dfsg.orig.tar.xz
 175f3688d3380ceb1b3fe3fbf65fe59f 163104 javascript optional 
nodejs_18.20.1+dfsg-1.debian.tar.xz
 06d37a9966050b373c0e0b13d103f9a3 10916 javascript optional 
nodejs_18.20.1+dfsg-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJGBAEBCAAwFiEEA8Tnq7iA9SQwbkgVZhHAXt0583QFAmYNu8wSHGthcG91ZXJA
bWVsaXgub3JnAAoJEGYRwF7dOfN0iF8P/jgSVspzx+1vifQxluwWLsWXJSp7jgxr
f1iOvKrmf5rXb7W1FICDoa53bOd+SmIL4Lbmd066+38k90n0zKEK61hpZoA84F6C
jYekdGsGNPGoJeygJjxK99+ZEUvAAsBmtOvq5l7aLAHQJskPXZSD7zRxRbvoAt9k
PRPQKh7uqreV3LoJGOMHnSdxUHNroM89oSqzx73nLyvfjW4+/xWkXIf3+DBoycFr
X0b9PaQmlRWH3bWdYBTb5GXMNL6qkQD41YdN4KpJd3oe17qUVBfI9+VssJuN3Gii
EQ6DQni0E4nPw9AmDG9nACjbqq1QOfWiJRmCZ6bHtPxRrTdaFUJeIhxymBqFq6V+
u4hGTgLJno2HQJ/8dPNIK2cYI/NbSRhBSIx62OPvyAEeSLAUJ9coDvoZ5/euazwS
YFxlLnp0+/FqwXR2LWAw+Za5SNdSPoTbbYyE93yxBtTFBAhq7XIIf2IoEkgLkV+z
7jYXn+DGUFnthHz1e4XAfrIHagMn/hfYgyrpzp37UyLRhY2Rk3t8/Brt44lcE001
rREGxh8QYR7ECimOdpobzoXk4JbmFf2VlvYxl7mVTzRsTeuBHaHX1VH+Dy4qLGfK
vuUBF7bjIeMCkCXrahu3kW3DFsWopqcmAGIOk/mA4iQsDvMzk7hfqNqdI/JbMPPu
jGMuZfAIvxbk
=8Xn2
-END PGP SIGNATURE-




- End forwarded message -

Processed: found 1068347 in 18.19.1+dfsg-3

[Debian Bug Tracking System]

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

> found 1068347 18.19.1+dfsg-3
Bug #1068347 [src:nodejs] nodejs: CVE-2024-27983 CVE-2024-27982
Marked as found in versions nodejs/18.19.1+dfsg-3.
> thanks
Stopping processing here.

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

Processed: Re: gnome-system-tools: FTBFS: shares-tool.c:113:17: error: implicit declaration of function ‘table_add_share’ [-Werror=implicit-function-declaration]

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #1066239 [src:gnome-system-tools] gnome-system-tools: FTBFS: 
shares-tool.c:113:17: error: implicit declaration of function ‘table_add_share’ 
[-Werror=implicit-function-declaration]
Added tag(s) patch.

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

Bug#1033316: marked as done (Autopkgtest is flaky)

[Debian Bug Tracking System]

Your message dated Thu, 04 Apr 2024 03:04:25 +
with message-id 
and subject line Bug#1033316: fixed in ruby-moneta 1.6.0-1
has caused the Debian Bug report #1033316,
regarding Autopkgtest is flaky
to be marked as done.

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

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


-- 
1033316: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033316
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-moneta
Version: 1.5.2-1
Severity: important

Hi,

ruby-moneta is currently showing up on
https://qa.debian.org/excuses.php?package=postgresql-common as a
regression in postgresql-common, but that's not true, the code hasn't
changed.

https://ci.debian.net/packages/r/ruby-moneta/testing/amd64/

This has already happened last week. Clicking the retry buttons
resolved the issue back then, on some architectures by making the test
pass, and on other architectures by making even the "reference" test
fail.

Please fix the tests to be stable.

Christoph
--- End Message ---
--- Begin Message ---
Source: ruby-moneta
Source-Version: 1.6.0-1
Done: Jérôme Charaoui 

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

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

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

Debian distribution maintenance software
pp.
Jérôme Charaoui  (supplier of updated ruby-moneta package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 03 Apr 2024 21:54:57 -0400
Source: ruby-moneta
Architecture: source
Version: 1.6.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Team 

Changed-By: Jérôme Charaoui 
Closes: 1033316
Changes:
 ruby-moneta (1.6.0-1) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Jérôme Charaoui ]
   * New upstream version 1.6.0
   * Drop obsolete test-related dependencies (Closes: #1033316)
   * drop activerecord and activesupport tests
   * drop mariadb and postgresql from build-deps
   * d/control: drop ruby-interpreter from Depends
   * d/control: drop obsolete X*-Ruby-Versions
   * d/patches: drop patches/fixes merged by upstream
 .
   [ Pirate Praveen ]
   * d/patches: disable randomly failing tests
Checksums-Sha1:
 69fe50ce36eeeaac30c32eef8dd0cba18fc41965 2316 ruby-moneta_1.6.0-1.dsc
 c05bfcff6f9b1568b297c785a5e5a8589fa049a4 136501 ruby-moneta_1.6.0.orig.tar.gz
 97e4fcd170ae7fe7dcf83b6ef86d9ef11fdcb0d9 8892 ruby-moneta_1.6.0-1.debian.tar.xz
 40185ef7c43b609bbfc008c67388e9af779db176 8651 
ruby-moneta_1.6.0-1_amd64.buildinfo
Checksums-Sha256:
 61925f8e238b15b5873b29746f049679bbaa038edba2cf8324c292167d8d3417 2316 
ruby-moneta_1.6.0-1.dsc
 ed539c636267b2b4039c3dab346103c9299d71829e72717976c481c0a528c2d3 136501 
ruby-moneta_1.6.0.orig.tar.gz
 bf80456ec7b88537079518b4af9b260609c776a7cee0b5fced679c1662bff267 8892 
ruby-moneta_1.6.0-1.debian.tar.xz
 3456ce1b19516fff03c28441361a349ec6065abfed6338f990c68e222d806ba4 8651 
ruby-moneta_1.6.0-1_amd64.buildinfo
Files:
 39f0c871420990af6bb66cb54df346e8 2316 ruby optional ruby-moneta_1.6.0-1.dsc
 6c6904ea477c8dd8952a90dea3b56fb3 136501 ruby optional 
ruby-moneta_1.6.0.orig.tar.gz
 41a2032eaeee8fe473b62e46866f6ffc 8892 ruby optional 
ruby-moneta_1.6.0-1.debian.tar.xz
 535e77d9e4c1db3cac41581f663c4c3c 8651 ruby optional 
ruby-moneta_1.6.0-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iHUEARYIAB0WIQTAq04Rv2xblqv/eu5pxS9ljpiFQgUCZg4VXAAKCRBpxS9ljpiF
QmkSAP0TRRNprtrgRSGWNj9PBb1Xf0AseIeLwdj0xXUfPJXFQQD/a6K9L0rXXl2Y
fAslc0JRR7KPOvanDVi8c6Cy/D4migI=
=YxS6
-END PGP SIGNATURE-



pgpqPI94fgOY8.pgp
Description: PGP signature
--- End Message ---

Bug#1066239: gnome-system-tools: FTBFS: shares-tool.c:113:17: error: implicit declaration of function ‘table_add_share’ [-Werror=implicit-function-declaration]

[Vladimir Petko]

Package: gnome-system-tools
Followup-For: Bug #1066239
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu noble ubuntu-patch
Control: tags -1 patch

Dear Maintainer,

Would it be possible tot consider the attached patch as a solution to this
issue.

In Ubuntu, the attached patch was applied to achieve the following:

  * d/p/implicit_declaration.patch: add missing declarations to resolve
ftbfs (LP: #2060165).


Thanks for considering the patch.


-- System Information:
Debian Release: trixie/sid
  APT prefers mantic-updates
  APT policy: (500, 'mantic-updates'), (500, 'mantic-security'), (500, 
'mantic'), (100, 'mantic-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.5.0-26-generic (SMP w/32 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff -Nru gnome-system-tools-3.0.0/debian/patches/implicit_declaration.patch 
gnome-system-tools-3.0.0/debian/patches/implicit_declaration.patch
--- gnome-system-tools-3.0.0/debian/patches/implicit_declaration.patch  
1970-01-01 12:00:00.0 +1200
+++ gnome-system-tools-3.0.0/debian/patches/implicit_declaration.patch  
2024-04-04 11:38:40.0 +1300
@@ -0,0 +1,29 @@
+Description: add missing declarations
+ Add missing headers and declarations to resolve 
-Werror=implicit-function-declaration.
+Author: Vladimir Petko 
+Bug-Ubuntu: 
https://bugs.launchpad.net/debian/+source/gnome-system-tools/+bug/2060165
+Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066239
+Forwarded: no
+Last-Update: 2024-04-04
+
+--- a/src/shares/shares-tool.h
 b/src/shares/shares-tool.h
+@@ -58,6 +58,7 @@
+ };
+
+ GstSharesTool *gst_shares_tool_new (void);
++GType gst_shares_tool_get_type();
+
+
+ G_END_DECLS
+--- a/src/shares/shares-tool.c
 b/src/shares/shares-tool.c
+@@ -23,6 +23,8 @@
+ #include "users-table.h"
+ #include 
+ #include "gst.h"
++#include "table.h"
++#include "share-settings.h"
+
+ static void gst_shares_tool_class_init (GstSharesToolClass *class);
+ static void gst_shares_tool_init   (GstSharesTool  *tool);
diff -Nru gnome-system-tools-3.0.0/debian/patches/series 
gnome-system-tools-3.0.0/debian/patches/series
--- gnome-system-tools-3.0.0/debian/patches/series  2024-03-31 
19:12:52.0 +1300
+++ gnome-system-tools-3.0.0/debian/patches/series  2024-04-04 
11:38:40.0 +1300
@@ -23,3 +23,4 @@
 max_group_name_32_chars.patch
 remove_g_thread_init.patch
 70_gst-yelp.patch
+implicit_declaration.patch

Bug#1064813: marked as done (fprintd: FTBFS: (fprintd:160601): fprintd-WARNING **: 06:35:58.406: Could not open "/etc/fprintd.conf": No such file or directory)

[Debian Bug Tracking System]

Your message dated Thu, 04 Apr 2024 02:49:21 +
with message-id 
and subject line Bug#1064813: fixed in fprintd 1.94.3-1
has caused the Debian Bug report #1064813,
regarding fprintd: FTBFS: (fprintd:160601): fprintd-WARNING **: 06:35:58.406: 
Could not open "/etc/fprintd.conf": No such file or directory
to be marked as done.

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

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


-- 
1064813: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064813
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: fprintd
Version: 1.94.2-3
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240226 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> ==
> 
> 
> Summary of Failures:
> 
>   8/514 fprintd:daemon+fprintd+FPrintdManagerPreStartTests / 
> FPrintdManagerPreStartTests.test_manager_get_no_default_device
> FAIL 0.57s   
> exit status 1
>   9/514 fprintd:daemon+fprintd+FPrintdManagerPreStartTests / 
> FPrintdManagerPreStartTests.test_manager_get_no_devices   
> FAIL 0.60s   
> exit status 1
> 
> Ok: 512 
> Expected Fail:  0   
> Fail:   2   
> Unexpected Pass:0   
> Skipped:0   
> Timeout:0   
> dh_auto_test: error: cd obj-x86_64-linux-gnu && DEB_PYTHON_INSTALL_LAYOUT=deb 
> LC_ALL=C.UTF-8 MESON_TESTTHREADS=8 meson test -C 
> /<>/obj-x86_64-linux-gnu --print-errorlogs --timeout-multiplier 
> 5 --no-suite PAM returned exit code 2


The full build log is available from:
http://qa-logs.debian.net/2024/02/26/fprintd_1.94.2-3_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240226;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240226=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.
--- End Message ---
--- Begin Message ---
Source: fprintd
Source-Version: 1.94.3-1
Done: Marco Trevisan (Treviño) 

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

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

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

Debian distribution maintenance software
pp.
Marco Trevisan (Treviño)  (supplier of updated fprintd 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 04 Apr 2024 03:58:13 +0200
Source: fprintd
Built-For-Profiles: noudeb
Architecture: source
Version: 1.94.3-1
Distribution: unstable
Urgency: medium
Maintainer: FingerForce Team 
Changed-By: Marco Trevisan (Treviño) 
Closes: 1061580 1064813
Launchpad-Bugs-Fixed: 2060067
Changes:
 fprintd (1.94.3-1) unstable; urgency=medium
 .
   [ Marco Trevisan (Treviño) ]
   * New upstream release (LP: #2060067, Closes: #1064813)
   * debian/patches: Drop, all applied upstream
 .
   [ Michael Biebl ]
   * Install PAM module in /usr (Closes: #1061580)
   * Install systemd unit in /usr (Closes: #1061580)
Checksums-Sha1:
 5c4f4c74b034e36a409c058b2847ce504dcf7f10 2409 fprintd_1.94.3-1.dsc
 bc20222702075e5fd08ca413bd26acc307634d68 661765 fprintd_1.94.3.orig.tar.bz2
 4de9c444fdb730e9524313dcde63982c94994a8f 7272 fprintd_1.94.3-1.debian.tar.xz
 f571c5a5a94bdd5564acc7845351f15e9fe03e86 10897 
fprintd_1.94.3-1_source.buildinfo
Checksums-Sha256:
 fc9b0333bfd28a88b67bbd3a825374d38cfa79a97ff0ef5912c956e768fa2051 2409 
fprintd_1.94.3-1.dsc
 969777bacf353706747998e50e5d55050e6cec09117b2565a2e8681eba094a82 661765 

Bug#1064533: src:peony: fails to migrate to testing for too long: new Build-Depends not available everywhere

[handsome_feng]

Hi, Paul,


> If you believe your package is unable to migrate to testing due to
> issues beyond your control, don't hesitate to contact the Release Team.The 
> excuses shows peony blocked by qtbase-opensource-src which it's beyond my 
> contorl,and the peony and peony-extensions will been auto removed on 
> 2024-04-07, how to deal with this?
Thanks,handsome_feng

Processed: tagging 1068347, tagging 1068346

[Debian Bug Tracking System]

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

> tags 1068347 + upstream
Bug #1068347 [src:nodejs] nodejs: CVE-2024-27983 CVE-2024-27982
Added tag(s) upstream.
> tags 1068346 + upstream
Bug #1068346 [src:node-express] node-express: CVE-2024-29041
Added tag(s) upstream.
> thanks
Stopping processing here.

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

Bug#1053245: fluidsynth: Fluidsynth starts at boot and blocks the sound device, no obvious way to disable it

[Alban Browaeys]

On Thu, 2 Nov 2023 23:05:28 +0100 at46  wrote:
> I had the same problem and it took me quite some time to find that 
> fluidsynth was the root cause of this. Fluidsynth was installed as
new 
> dependency from lutris 0.5.14 and blocked my sound device each
~second 
> boot.
> 
> @Patrick I could check the status with "systemctl --user status 
> fluidsynth" and disable it with "sudo systemctl --global disable 
> fluidsynth.service"
> 

fluidsynth and pulseaudio are both user session services. They are
started at login (ie not at boot).

>From /usr/lib/systemd/user/fluidsynth.service, it seems only pipewire
is handled, ie not pulseaudio:
"
[Unit]
Description=FluidSynth Daemon
Documentation=man:fluidsynth(1)
After=sound.target
After=pipewire.service

[Service]
# added automatically, for details please see
#
https://en.opensuse.org/openSUSE:Security_Features#Systemd_hardening_effort
ProtectSystem=full
ProtectHome=read-only
ProtectHostname=true
ProtectKernelTunables=true
ProtectKernelModules=true
ProtectKernelLogs=true
ProtectControlGroups=true
# end of automatic additions
# required in order for the above sandboxing options to work on a user
unit
PrivateUsers=yes
Type=notify
NotifyAccess=main
EnvironmentFile=/etc/default/fluidsynth
EnvironmentFile=-%h/.config/fluidsynth
ExecStart=/usr/bin/fluidsynth -is $OTHER_OPTS $SOUND_FONT

[Install]
WantedBy=default.target
"

Seems you are running native pulseaudio and not pipewire-pulse.

Could you try adding pulseaudio.service "pulseaudio.service" to the
"After" directive of fluidsynth.service, via systemctl --user edit
fluidsynth.service by writing in the editor that will open:
"
[Unit]
After=pipewire.service pulseaudio.service
"
then running:
systemctl --user daemon-reload
and logout/login, then check that pulseaudio see your audio device?

Still, fluidsynth should be running, so the issue might be otherwise.
At least with pipewire/pipewire-pulse/fluidsynth I have all of them up
simultaneously for the whole user session.

Best regards,
Alban

Bug#1062932: Error building nvidia-kernel-dkms while installing nvidia-driver package

[David Landry]

Good evening,

The bug involving compiling/installing nvidia-kernel-dkms is still present. The 
result of the bug is that following a reboot after the erroneous installation 
noted below, my display drivers get completely disabled, including nouveau, 
resulting in my external display not functioning and my primary laptop display 
having very low resolution.

I followed the instructions to install NVIDIA proprietary drivers here:
https://wiki.debian.org/NvidiaGraphicsDrivers

When I executed:
sudo apt install nvidia-driver firmware-misc-nonfree
I received the following errors, as recorded from the output of the above 
command:
Setting up nvidia-kernel-dkms (525.147.05-4~deb12u1) ...
Loading new nvidia-current-525.147.05 DKMS files...
Building for 6.1.0-18-amd64
Building initial module for 6.1.0-18-amd64
Error! Bad return status for module build on kernel: 6.1.0-18-amd64 (x86_64)
Consult /var/lib/dkms/nvidia-current/525.147.05/build/make.log for more 
information.
dpkg: error processing package nvidia-kernel-dkms (--configure):
installed nvidia-kernel-dkms package post-installation script subprocess 
returned error exit status 10
dpkg: dependency problems prevent configuration of nvidia-driver:
nvidia-driver depends on nvidia-kernel-dkms (= 525.147.05-4~deb12u1) | 
nvidia-kernel-525.147.05 | nvidia-open-kernel-525.147.05 | 
nvidia-open-kernel-525.147.05; however:
Package nvidia-kernel-dkms is not configured yet.
Package nvidia-kernel-525.147.05 is not installed.
Package nvidia-kernel-dkms which provides nvidia-kernel-525.147.05 is not 
configured yet.
Package nvidia-open-kernel-525.147.05 is not installed.
Package nvidia-open-kernel-525.147.05 is not installed.

dpkg: error processing package nvidia-driver (--configure):
dependency problems - leaving unconfigured
Processing triggers for libc-bin (2.36-9+deb12u4) ...
Processing triggers for initramfs-tools (0.142) ...
update-initramfs: Generating /boot/initrd.img-6.1.0-18-amd64
Processing triggers for update-glx (1.2.2) ...
Processing triggers for glx-alternative-nvidia (1.2.2) ...
update-alternatives: using /usr/lib/nvidia to provide /usr/lib/glx (glx) in 
auto mode
Processing triggers for glx-alternative-mesa (1.2.2) ...
Processing triggers for libc-bin (2.36-9+deb12u4) ...
Processing triggers for initramfs-tools (0.142) ...
update-initramfs: Generating /boot/initrd.img-6.1.0-18-amd64
Errors were encountered while processing:
nvidia-kernel-dkms
nvidia-driver
E: Sub-process /usr/bin/dpkg returned an error code (1)

From /var/lib/dkms/nvidia-current/525.147.05/build/make.log:
ERROR: modpost: GPL-incompatible module nvidia.ko uses GPL-only symbol 
'__rcu_read_lock'
ERROR: modpost: GPL-incompatible module nvidia.ko uses GPL-only symbol 
'__rcu_read_unlock'
make[3]: *** 
[/usr/src/linux-headers-6.1.0-18-common/scripts/Makefile.modpost:126: 
/var/lib/dkms/nvidia-current/525.147.05/build/Module.symvers] Error 1
make[2]: *** [/usr/src/linux-headers-6.1.0-18-common/Makefile:1991: modpost] 
Error 2
make[2]: Leaving directory '/usr/src/linux-headers-6.1.0-18-amd64'
make[1]: *** [Makefile:250: __sub-make] Error 2
make[1]: Leaving directory '/usr/src/linux-headers-6.1.0-18-common'
make: *** [Makefile:82: modules] Error 2

Here is the output of hostnamectl:
Static hostname: landarian-laptop
Icon name: computer-laptop
Chassis: laptop 
Machine ID: 096686ad78fe43939982b38788ec530e
Boot ID: 42ecccb1e0704aaba319fc8d066e6a6a
Operating System: Debian GNU/Linux 12 (bookworm)
Kernel: Linux 6.1.0-18-amd64
Architecture: x86-64
Hardware Vendor: HP
Hardware Model: OMEN by HP Laptop 17-cb1xxx
Firmware Version: F.41

And here is the output of lspci -nn | egrep -i "3d|display|vga":
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation TU116M [GeForce 
GTX 1660 Ti Mobile] [10de:2191] (rev a1)

lsmod | grep -w video yields this:
video 65536 1 nouveau

After researching this issue, I found another Debian user with an identical 
issue:
https://github.com/NVIDIA/nvidia-container-toolkit/issues/361

A patch was linked to here:
https://unix.stackexchange.com/questions/769026/debian-12-linux-image-6-1-0-18-amd64-dist-upgrade-fails-on-nvidia-gpl-incompatib

I will attempt the patch until this bug gets resolved.

Thank you.
_
David Landry

Bug#1067365: marked as done (gir-rust-code-generator: update for time_t changes)

[Debian Bug Tracking System]

Your message dated Thu, 04 Apr 2024 00:22:17 +
with message-id 
and subject line Bug#1067256: fixed in gir-rust-code-generator 0.18.3-2
has caused the Debian Bug report #1067256,
regarding gir-rust-code-generator: update for time_t changes
to be marked as done.

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

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


-- 
1067256: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067256
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rust-gdk-sys
Version: 0.18.0-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240319 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> cp /usr/share/gir-1.0/GLib-2.0.gir /<>
> cp /usr/share/gir-1.0/GObject-2.0.gir /<>
> cp /usr/share/gir-1.0/Pango-1.0.gir /<>
> cp /usr/share/gir-1.0/Gio-2.0.gir /<>
> cp /usr/share/gir-1.0/HarfBuzz-0.0.gir /<>
> cp /usr/share/gir-1.0/freetype2-2.0.gir /<>
> cp /usr/share/gir-1.0/PangoCairo-1.0.gir /<>
> cp /usr/share/gir-1.0/cairo-1.0.gir /<>
> cp /usr/share/gir-1.0/Gdk-3.0.gir /<>
> cp /usr/share/gir-1.0/GdkPixbuf-2.0.gir /<>
> cp /usr/share/gir-1.0/GModule-2.0.gir /<>
> xmlstarlet ed -L \
> -d '///_:alias[@name="Int32"]' \
> freetype2-2.0.gir
> xmlstarlet ed -L \
> -u 
> '//*[@glib:error-domain="g-option-context-error-quark"]/@glib:error-domain' 
> -v g-option-error-quark \
> -u 
> '//_:record[@name="KeyFile"]/_:method[@name="set_boolean_list"]//_:parameter[@name="list"]/_:array/@c:type'
>  -v "gboolean*" \
> -u 
> '//_:record[@name="KeyFile"]/_:method[@name="set_double_list"]//_:parameter[@name="list"]/_:array/@c:type'
>  -v "gdouble*" \
> -u 
> '//_:record[@name="KeyFile"]/_:method[@name="set_integer_list"]//_:parameter[@name="list"]/_:array/@c:type'
>  -v "gint*" \
> -u 
> '//_:record[@name="KeyFile"]/_:method[@name="set_locale_string_list"]//_:parameter[@name="list"]/_:array/@c:type'
>  -v "const gchar* const*" \
> -u 
> '//_:record[@name="KeyFile"]/_:method[@name="set_string_list"]//_:parameter[@name="list"]/_:array/@c:type'
>  -v "const gchar* const*" \
> GLib-2.0.gir
> xmlstarlet ed -L \
> -u 
> '//_:class[@name="Object"]/_:method[@name="getv"]//_:parameter[@name="names"]/_:array/@c:type'
>  -v "const gchar**" \
> -u 
> '//_:class[@name="Object"]/_:method[@name="getv"]//_:parameter[@name="values"]/_:array/@c:type'
>  -v "GValue*" \
> -u 
> '//_:class[@name="Object"]/_:method[@name="setv"]//_:parameter[@name="names"]/_:array/@c:type'
>  -v "const gchar**" \
> -u 
> '//_:class[@name="Object"]/_:method[@name="setv"]//_:parameter[@name="values"]/_:array/@c:type'
>  -v "const GValue*" \
> -u 
> '//_:class[@name="Object"]/_:constructor[@name="new_with_properties"]//_:parameter[@name="names"]/_:array/@c:type'
>  -v "const char**" \
> -u 
> '//_:class[@name="Object"]/_:constructor[@name="new_with_properties"]//_:parameter[@name="values"]/_:array/@c:type'
>  -v "const GValue*" \
> -i '//_:interface[@name="TypePlugin" and not(@glib:type-struct)]' -t 'attr' 
> -n 'glib:type-struct' -v 'TypePluginClass' \
> -i '//_:record[@name="TypePluginClass" and not(@glib:is-gtype-struct-for)]' 
> -t 'attr' -n 'glib:is-gtype-struct-for' -v 'TypePlugin' \
> GObject-2.0.gir
> xmlstarlet ed -L \
> -i '///_:type[not(@name) and @c:type="hb_font_t*"]' -t 'attr' -n 'name' -v 
> "gconstpointer" \
> -u '//_:type[@c:type="hb_font_t*"]/@c:type' -v "gconstpointer" \
> -i '///_:array[not(@name) and @c:type="hb_feature_t*"]' -t 'attr' -n 'name' 
> -v "gconstpointer" \
> -r '///_:array[@c:type="hb_feature_t*"]' -v "type" \
> -d '//_:type[@c:type="hb_feature_t*"]/*' \
> -d '//_:type[@c:type="hb_feature_t*"]/@length' \
> -d '//_:type[@c:type="hb_feature_t*"]/@zero-terminated' \
> -u '//_:type[@c:type="hb_feature_t*"]/@c:type' -v "gconstpointer" \
> -d '//_:record[@c:type="PangoGlyphVisAttr"]/_:field/@bits' \
> -d '//_:record[@c:type="PangoGlyphVisAttr"]/_:field[@name="is_color"]' \
> Pango-1.0.gir
> xmlstarlet ed -L \
> -d '///_:function[@c:identifier="hb_graphite2_face_get_gr_face"]' \
> -d '///_:function[@c:identifier="hb_graphite2_font_get_gr_font"]' \
> -d '///_:function[@c:identifier="hb_ft_face_create"]' \
> -d '///_:function[@c:identifier="hb_ft_face_create_cached"]' \
> -d '///_:function[@c:identifier="hb_ft_face_create_referenced"]' \
> -d '///_:function[@c:identifier="hb_ft_font_create"]' \
> -d '///_:function[@c:identifier="hb_ft_font_create_cached"]' \
> -d '///_:function[@c:identifier="hb_ft_font_create_referenced"]' \
> -d '///_:function[@c:identifier="hb_ft_font_get_face"]' \
> -d 

Bug#1067373: marked as done (gir-rust-code-generator: update for time_t changes)

[Debian Bug Tracking System]

Your message dated Thu, 04 Apr 2024 00:22:17 +
with message-id 
and subject line Bug#1067256: fixed in gir-rust-code-generator 0.18.3-2
has caused the Debian Bug report #1067256,
regarding gir-rust-code-generator: update for time_t changes
to be marked as done.

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

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


-- 
1067256: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067256
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rust-glib-sys
Version: 0.18.1-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240319 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> cp /usr/share/gir-1.0/GLib-2.0.gir /<>
> xmlstarlet ed -L \
> -u 
> '//*[@glib:error-domain="g-option-context-error-quark"]/@glib:error-domain' 
> -v g-option-error-quark \
> -u 
> '//_:record[@name="KeyFile"]/_:method[@name="set_boolean_list"]//_:parameter[@name="list"]/_:array/@c:type'
>  -v "gboolean*" \
> -u 
> '//_:record[@name="KeyFile"]/_:method[@name="set_double_list"]//_:parameter[@name="list"]/_:array/@c:type'
>  -v "gdouble*" \
> -u 
> '//_:record[@name="KeyFile"]/_:method[@name="set_integer_list"]//_:parameter[@name="list"]/_:array/@c:type'
>  -v "gint*" \
> -u 
> '//_:record[@name="KeyFile"]/_:method[@name="set_locale_string_list"]//_:parameter[@name="list"]/_:array/@c:type'
>  -v "const gchar* const*" \
> -u 
> '//_:record[@name="KeyFile"]/_:method[@name="set_string_list"]//_:parameter[@name="list"]/_:array/@c:type'
>  -v "const gchar* const*" \
> GLib-2.0.gir
> sed -i 
> 's/girs_directories\s=\s\[\"\.\.\/\.\.\/gir-files\"\]/girs_directories=\[\".\"\]/'
>  /<>/Gir.toml
> gir -o .
> thread 'main' panicked at 'Incomplete library, unresolved: ["GLib.time_t"]', 
> src/library_postprocessing.rs:69:9
> note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
> make[1]: *** [debian/rules:12: execute_before_dh_auto_build] Error 101


The full build log is available from:
http://qa-logs.debian.net/2024/03/19/rust-glib-sys_0.18.1-2_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240319;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240319=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.
--- End Message ---
--- Begin Message ---
Source: gir-rust-code-generator
Source-Version: 0.18.3-2
Done: Jeremy Bícha 

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

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

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

Debian distribution maintenance software
pp.
Jeremy Bícha  (supplier of updated gir-rust-code-generator 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 03 Apr 2024 19:49:38 -0400
Source: gir-rust-code-generator
Built-For-Profiles: noudeb
Architecture: source
Version: 0.18.3-2
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Jeremy Bícha 
Closes: 1064096 1064766 1067256
Changes:
 gir-rust-code-generator (0.18.3-2) unstable; urgency=medium
 .
   * Update dependencies (Closes: #1064766, #1064096)
   * Cherry-pick patch to fix Rust GNOME builds with latest
 gobject-introspection time_t changes (Closes: #1067256)
Checksums-Sha1:
 47d839b5b34e05e9550d6677551221f990d5a744 2467 
gir-rust-code-generator_0.18.3-2.dsc
 87d44e4f312955be60b95d1b7ad5b34d97f1013e 8716 
gir-rust-code-generator_0.18.3-2.debian.tar.xz
 6387bddf9fcd69d143aa4c50a6495b128f831719 9170 
gir-rust-code-generator_0.18.3-2_source.buildinfo

Bug#1067351: marked as done (gir-rust-code-generator: update for time_t changes)

[Debian Bug Tracking System]

Your message dated Thu, 04 Apr 2024 00:22:17 +
with message-id 
and subject line Bug#1067256: fixed in gir-rust-code-generator 0.18.3-2
has caused the Debian Bug report #1067256,
regarding gir-rust-code-generator: update for time_t changes
to be marked as done.

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

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


-- 
1067256: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067256
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rust-gdk4-wayland
Version: 0.7.2-4
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240319 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> cp /usr/share/gir-1.0/GLib-2.0.gir /<>
> cp /usr/share/gir-1.0/freetype2-2.0.gir /<>
> cp /usr/share/gir-1.0/GObject-2.0.gir /<>
> cp /usr/share/gir-1.0/Gio-2.0.gir /<>
> cp /usr/share/gir-1.0/PangoCairo-1.0.gir /<>
> cp /usr/share/gir-1.0/GdkWayland-4.0.gir /<>
> cp /usr/share/gir-1.0/HarfBuzz-0.0.gir /<>
> cp /usr/share/gir-1.0/Gdk-4.0.gir /<>
> cp /usr/share/gir-1.0/Pango-1.0.gir /<>
> cp /usr/share/gir-1.0/GdkPixbuf-2.0.gir /<>
> cp /usr/share/gir-1.0/GModule-2.0.gir /<>
> cp /usr/share/gir-1.0/cairo-1.0.gir /<>
> # We need to fix some gir files; lines taken from 
> https://github.com/gtk-rs/gir-files/blob/master/fix.sh
> # this needs to be re-done for every new upstream release :(
> # freetype
> xmlstarlet ed -L \
> -d '///_:alias[@name="Int32"]' \
> freetype2-2.0.gir
> # harfbuzz
> xmlstarlet ed -L \
> -d '///_:function[@c:identifier="hb_graphite2_face_get_gr_face"]' \
> -d '///_:function[@c:identifier="hb_graphite2_font_get_gr_font"]' \
> -d '///_:function[@c:identifier="hb_ft_face_create"]' \
> -d '///_:function[@c:identifier="hb_ft_face_create_cached"]' \
> -d '///_:function[@c:identifier="hb_ft_face_create_referenced"]' \
> -d '///_:function[@c:identifier="hb_ft_font_create"]' \
> -d '///_:function[@c:identifier="hb_ft_font_create_cached"]' \
> -d '///_:function[@c:identifier="hb_ft_font_create_referenced"]' \
> -d '///_:function[@c:identifier="hb_ft_font_get_face"]' \
> -d '///_:function[@c:identifier="hb_ft_font_lock_face"]' \
> HarfBuzz-0.0.gir
> #pango
> xmlstarlet ed -L \
> -i '///_:type[not(@name) and @c:type="hb_font_t*"]' -t 'attr' -n 'name' -v 
> "gconstpointer" \
> -u '//_:type[@c:type="hb_font_t*"]/@c:type' -v "gconstpointer" \
> -i '///_:array[not(@name) and @c:type="hb_feature_t*"]' -t 'attr' -n 'name' 
> -v "gconstpointer" \
> -r '///_:array[@c:type="hb_feature_t*"]' -v "type" \
> -d '//_:type[@c:type="hb_feature_t*"]/*' \
> -d '//_:type[@c:type="hb_feature_t*"]/@length' \
> -d '//_:type[@c:type="hb_feature_t*"]/@zero-terminated' \
> -u '//_:type[@c:type="hb_feature_t*"]/@c:type' -v "gconstpointer" \
> Pango-1.0.gir
> xmlstarlet ed -L \
> -d '//_:record[@c:type="PangoGlyphVisAttr"]/_:field/@bits' \
> -d '//_:record[@c:type="PangoGlyphVisAttr"]/_:field[@name="is_color"]' \
> Pango-1.0.gir
> # gdk4-wayland
> xmlstarlet ed -L \
> -u 
> '//_:class[@name="WaylandDevice"]/_:method[@name="get_wl_keyboard"]//_:type[@name="gpointer"]/@c:type'
>  -v "gpointer" \
> -u 
> '//_:class[@name="WaylandDevice"]/_:method[@name="get_wl_pointer"]//_:type[@name="gpointer"]/@c:type'
>  -v "gpointer" \
> -u 
> '//_:class[@name="WaylandDevice"]/_:method[@name="get_wl_seat"]//_:type[@name="gpointer"]/@c:type'
>  -v "gpointer" \
> -u 
> '//_:class[@name="WaylandDisplay"]/_:method[@name="get_wl_compositor"]//_:type[@name="gpointer"]/@c:type'
>  -v "gpointer" \
> -u 
> '//_:class[@name="WaylandDisplay"]/_:method[@name="get_wl_display"]//_:type[@name="gpointer"]/@c:type'
>  -v "gpointer" \
> -u 
> '//_:class[@name="WaylandMonitor"]/_:method[@name="get_wl_output"]//_:type[@name="gpointer"]/@c:type'
>  -v "gpointer" \
> -u 
> '//_:class[@name="WaylandSeat"]/_:method[@name="get_wl_seat"]//_:type[@name="gpointer"]/@c:type'
>  -v "gpointer" \
> -u 
> '//_:class[@name="WaylandSurface"]/_:method[@name="get_wl_surface"]//_:type[@name="gpointer"]/@c:type'
>  -v "gpointer" \
> -u 
> '//_:class[@name="WaylandDevice"]/_:method[@name="get_xkb_keymap"]//_:type[@name="gpointer"]/@c:type'
>  -v "gpointer" \
> GdkWayland-4.0.gir
> sed -i 's/girs_directories\s=\s\[\"\.\.\/gir-files\"\]/girs_directories = 
> \[\".\"\]/' /<>/Gir.toml
> gir -o .
> thread 'main' panicked at 'Incomplete library, unresolved: ["GLib.time_t"]', 
> src/library_postprocessing.rs:69:9
> note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
> make[1]: *** [debian/rules:31: 

Bug#1067357: marked as done (gir-rust-code-generator: update for time_t changes)

[Debian Bug Tracking System]

Your message dated Thu, 04 Apr 2024 00:22:17 +
with message-id 
and subject line Bug#1067256: fixed in gir-rust-code-generator 0.18.3-2
has caused the Debian Bug report #1067256,
regarding gir-rust-code-generator: update for time_t changes
to be marked as done.

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

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


-- 
1067256: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067256
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rust-gdk4-wayland-sys
Version: 0.7.2-3
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240319 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> cp /usr/share/gir-1.0/GLib-2.0.gir /<>
> cp /usr/share/gir-1.0/freetype2-2.0.gir /<>
> cp /usr/share/gir-1.0/GObject-2.0.gir /<>
> cp /usr/share/gir-1.0/Gio-2.0.gir /<>
> cp /usr/share/gir-1.0/PangoCairo-1.0.gir /<>
> cp /usr/share/gir-1.0/GdkWayland-4.0.gir /<>
> cp /usr/share/gir-1.0/HarfBuzz-0.0.gir /<>
> cp /usr/share/gir-1.0/Gdk-4.0.gir /<>
> cp /usr/share/gir-1.0/Pango-1.0.gir /<>
> cp /usr/share/gir-1.0/GdkPixbuf-2.0.gir /<>
> cp /usr/share/gir-1.0/GModule-2.0.gir /<>
> cp /usr/share/gir-1.0/cairo-1.0.gir /<>
> # We need to fix some gir files; lines taken from 
> https://github.com/gtk-rs/gir-files/blob/master/fix.sh
> # this needs to be re-done for every new upstream release :(
> # freetype
> xmlstarlet ed -L \
> -d '///_:alias[@name="Int32"]' \
> freetype2-2.0.gir
> # harfbuzz
> xmlstarlet ed -L \
> -d '///_:function[@c:identifier="hb_graphite2_face_get_gr_face"]' \
> -d '///_:function[@c:identifier="hb_graphite2_font_get_gr_font"]' \
> -d '///_:function[@c:identifier="hb_ft_face_create"]' \
> -d '///_:function[@c:identifier="hb_ft_face_create_cached"]' \
> -d '///_:function[@c:identifier="hb_ft_face_create_referenced"]' \
> -d '///_:function[@c:identifier="hb_ft_font_create"]' \
> -d '///_:function[@c:identifier="hb_ft_font_create_cached"]' \
> -d '///_:function[@c:identifier="hb_ft_font_create_referenced"]' \
> -d '///_:function[@c:identifier="hb_ft_font_get_face"]' \
> -d '///_:function[@c:identifier="hb_ft_font_lock_face"]' \
> HarfBuzz-0.0.gir
> #pango
> xmlstarlet ed -L \
> -i '///_:type[not(@name) and @c:type="hb_font_t*"]' -t 'attr' -n 'name' -v 
> "gconstpointer" \
> -u '//_:type[@c:type="hb_font_t*"]/@c:type' -v "gconstpointer" \
> -i '///_:array[not(@name) and @c:type="hb_feature_t*"]' -t 'attr' -n 'name' 
> -v "gconstpointer" \
> -r '///_:array[@c:type="hb_feature_t*"]' -v "type" \
> -d '//_:type[@c:type="hb_feature_t*"]/*' \
> -d '//_:type[@c:type="hb_feature_t*"]/@length' \
> -d '//_:type[@c:type="hb_feature_t*"]/@zero-terminated' \
> -u '//_:type[@c:type="hb_feature_t*"]/@c:type' -v "gconstpointer" \
> Pango-1.0.gir
> xmlstarlet ed -L \
> -d '//_:record[@c:type="PangoGlyphVisAttr"]/_:field/@bits' \
> -d '//_:record[@c:type="PangoGlyphVisAttr"]/_:field[@name="is_color"]' \
> Pango-1.0.gir
> # gdk4-wayland
> xmlstarlet ed -L \
> -u 
> '//_:class[@name="WaylandDevice"]/_:method[@name="get_wl_keyboard"]//_:type[@name="gpointer"]/@c:type'
>  -v "gpointer" \
> -u 
> '//_:class[@name="WaylandDevice"]/_:method[@name="get_wl_pointer"]//_:type[@name="gpointer"]/@c:type'
>  -v "gpointer" \
> -u 
> '//_:class[@name="WaylandDevice"]/_:method[@name="get_wl_seat"]//_:type[@name="gpointer"]/@c:type'
>  -v "gpointer" \
> -u 
> '//_:class[@name="WaylandDisplay"]/_:method[@name="get_wl_compositor"]//_:type[@name="gpointer"]/@c:type'
>  -v "gpointer" \
> -u 
> '//_:class[@name="WaylandDisplay"]/_:method[@name="get_wl_display"]//_:type[@name="gpointer"]/@c:type'
>  -v "gpointer" \
> -u 
> '//_:class[@name="WaylandMonitor"]/_:method[@name="get_wl_output"]//_:type[@name="gpointer"]/@c:type'
>  -v "gpointer" \
> -u 
> '//_:class[@name="WaylandSeat"]/_:method[@name="get_wl_seat"]//_:type[@name="gpointer"]/@c:type'
>  -v "gpointer" \
> -u 
> '//_:class[@name="WaylandSurface"]/_:method[@name="get_wl_surface"]//_:type[@name="gpointer"]/@c:type'
>  -v "gpointer" \
> -u 
> '//_:class[@name="WaylandDevice"]/_:method[@name="get_xkb_keymap"]//_:type[@name="gpointer"]/@c:type'
>  -v "gpointer" \
> GdkWayland-4.0.gir
> sed -i 's/girs_directories\s=\s\[\"\.\.\/\.\.\/gir-files\"\]/girs_directories 
> = \[\".\"\]/' /<>/Gir.toml
> gir -o .
> thread 'main' panicked at 'Incomplete library, unresolved: ["GLib.time_t"]', 
> src/library_postprocessing.rs:69:9
> note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
> make[1]: *** [debian/rules:31: 

Bug#1067343: marked as done (gir-rust-code-generator: update for time_t changes)

[Debian Bug Tracking System]

Your message dated Thu, 04 Apr 2024 00:22:17 +
with message-id 
and subject line Bug#1067256: fixed in gir-rust-code-generator 0.18.3-2
has caused the Debian Bug report #1067256,
regarding gir-rust-code-generator: update for time_t changes
to be marked as done.

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

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


-- 
1067256: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067256
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rust-gtk-sys
Version: 0.18.0-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240319 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> cp /usr/share/gir-1.0/GLib-2.0.gir /<>
> cp /usr/share/gir-1.0/GObject-2.0.gir /<>
> cp /usr/share/gir-1.0/Pango-1.0.gir /<>
> cp /usr/share/gir-1.0/Gio-2.0.gir /<>
> cp /usr/share/gir-1.0/HarfBuzz-0.0.gir /<>
> cp /usr/share/gir-1.0/freetype2-2.0.gir /<>
> cp /usr/share/gir-1.0/PangoCairo-1.0.gir /<>
> cp /usr/share/gir-1.0/Gtk-3.0.gir /<>
> cp /usr/share/gir-1.0/cairo-1.0.gir /<>
> cp /usr/share/gir-1.0/xlib-2.0.gir /<>
> cp /usr/share/gir-1.0/Atk-1.0.gir /<>
> cp /usr/share/gir-1.0/Gdk-3.0.gir /<>
> cp /usr/share/gir-1.0/GdkPixbuf-2.0.gir /<>
> cp /usr/share/gir-1.0/GModule-2.0.gir /<>
> xmlstarlet ed -L \
> -d '///_:method[@c:identifier="atk_plug_set_child"]' \
> Atk-1.0.gir
> xmlstarlet ed -L \
> -d '///_:alias[@name="Int32"]' \
> freetype2-2.0.gir
> xmlstarlet ed -L \
> -u 
> '//*[@glib:error-domain="g-option-context-error-quark"]/@glib:error-domain' 
> -v g-option-error-quark \
> -u 
> '//_:record[@name="KeyFile"]/_:method[@name="set_boolean_list"]//_:parameter[@name="list"]/_:array/@c:type'
>  -v "gboolean*" \
> -u 
> '//_:record[@name="KeyFile"]/_:method[@name="set_double_list"]//_:parameter[@name="list"]/_:array/@c:type'
>  -v "gdouble*" \
> -u 
> '//_:record[@name="KeyFile"]/_:method[@name="set_integer_list"]//_:parameter[@name="list"]/_:array/@c:type'
>  -v "gint*" \
> -u 
> '//_:record[@name="KeyFile"]/_:method[@name="set_locale_string_list"]//_:parameter[@name="list"]/_:array/@c:type'
>  -v "const gchar* const*" \
> -u 
> '//_:record[@name="KeyFile"]/_:method[@name="set_string_list"]//_:parameter[@name="list"]/_:array/@c:type'
>  -v "const gchar* const*" \
> GLib-2.0.gir
> xmlstarlet ed -L \
> -u 
> '//_:class[@name="Object"]/_:method[@name="getv"]//_:parameter[@name="names"]/_:array/@c:type'
>  -v "const gchar**" \
> -u 
> '//_:class[@name="Object"]/_:method[@name="getv"]//_:parameter[@name="values"]/_:array/@c:type'
>  -v "GValue*" \
> -u 
> '//_:class[@name="Object"]/_:method[@name="setv"]//_:parameter[@name="names"]/_:array/@c:type'
>  -v "const gchar**" \
> -u 
> '//_:class[@name="Object"]/_:method[@name="setv"]//_:parameter[@name="values"]/_:array/@c:type'
>  -v "const GValue*" \
> -u 
> '//_:class[@name="Object"]/_:constructor[@name="new_with_properties"]//_:parameter[@name="names"]/_:array/@c:type'
>  -v "const char**" \
> -u 
> '//_:class[@name="Object"]/_:constructor[@name="new_with_properties"]//_:parameter[@name="values"]/_:array/@c:type'
>  -v "const GValue*" \
> -i '//_:interface[@name="TypePlugin" and not(@glib:type-struct)]' -t 'attr' 
> -n 'glib:type-struct' -v 'TypePluginClass' \
> -i '//_:record[@name="TypePluginClass" and not(@glib:is-gtype-struct-for)]' 
> -t 'attr' -n 'glib:is-gtype-struct-for' -v 'TypePlugin' \
> GObject-2.0.gir
> xmlstarlet ed -L \
> -i '///_:type[not(@name) and @c:type="hb_font_t*"]' -t 'attr' -n 'name' -v 
> "gconstpointer" \
> -u '//_:type[@c:type="hb_font_t*"]/@c:type' -v "gconstpointer" \
> -i '///_:array[not(@name) and @c:type="hb_feature_t*"]' -t 'attr' -n 'name' 
> -v "gconstpointer" \
> -r '///_:array[@c:type="hb_feature_t*"]' -v "type" \
> -d '//_:type[@c:type="hb_feature_t*"]/*' \
> -d '//_:type[@c:type="hb_feature_t*"]/@length' \
> -d '//_:type[@c:type="hb_feature_t*"]/@zero-terminated' \
> -u '//_:type[@c:type="hb_feature_t*"]/@c:type' -v "gconstpointer" \
> -d '//_:record[@c:type="PangoGlyphVisAttr"]/_:field/@bits' \
> -d '//_:record[@c:type="PangoGlyphVisAttr"]/_:field[@name="is_color"]' \
> Pango-1.0.gir
> xmlstarlet ed -L \
> -d '///_:function[@c:identifier="hb_graphite2_face_get_gr_face"]' \
> -d '///_:function[@c:identifier="hb_graphite2_font_get_gr_font"]' \
> -d '///_:function[@c:identifier="hb_ft_face_create"]' \
> -d '///_:function[@c:identifier="hb_ft_face_create_cached"]' \
> -d '///_:function[@c:identifier="hb_ft_face_create_referenced"]' \
> -d '///_:function[@c:identifier="hb_ft_font_create"]' \

Bug#1067338: marked as done (gir-rust-code-generator: update for time_t changes)

[Debian Bug Tracking System]

Your message dated Thu, 04 Apr 2024 00:22:17 +
with message-id 
and subject line Bug#1067256: fixed in gir-rust-code-generator 0.18.3-2
has caused the Debian Bug report #1067256,
regarding gir-rust-code-generator: update for time_t changes
to be marked as done.

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

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


-- 
1067256: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067256
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rust-gdk-pixbuf
Version: 0.18.5-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240319 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> cp /usr/share/gir-1.0/GLib-2.0.gir /<>
> cp /usr/share/gir-1.0/GObject-2.0.gir /<>
> cp /usr/share/gir-1.0/Gio-2.0.gir /<>
> cp /usr/share/gir-1.0/GdkPixbuf-2.0.gir /<>
> cp /usr/share/gir-1.0/GModule-2.0.gir /<>
> xmlstarlet ed -L \
> -u 
> '//*[@glib:error-domain="g-option-context-error-quark"]/@glib:error-domain' 
> -v g-option-error-quark \
> -u 
> '//_:record[@name="KeyFile"]/_:method[@name="set_boolean_list"]//_:parameter[@name="list"]/_:array/@c:type'
>  -v "gboolean*" \
> -u 
> '//_:record[@name="KeyFile"]/_:method[@name="set_double_list"]//_:parameter[@name="list"]/_:array/@c:type'
>  -v "gdouble*" \
> -u 
> '//_:record[@name="KeyFile"]/_:method[@name="set_integer_list"]//_:parameter[@name="list"]/_:array/@c:type'
>  -v "gint*" \
> -u 
> '//_:record[@name="KeyFile"]/_:method[@name="set_locale_string_list"]//_:parameter[@name="list"]/_:array/@c:type'
>  -v "const gchar* const*" \
> -u 
> '//_:record[@name="KeyFile"]/_:method[@name="set_string_list"]//_:parameter[@name="list"]/_:array/@c:type'
>  -v "const gchar* const*" \
> GLib-2.0.gir
> xmlstarlet ed -L \
> -u 
> '//_:class[@name="Object"]/_:method[@name="getv"]//_:parameter[@name="names"]/_:array/@c:type'
>  -v "const gchar**" \
> -u 
> '//_:class[@name="Object"]/_:method[@name="getv"]//_:parameter[@name="values"]/_:array/@c:type'
>  -v "GValue*" \
> -u 
> '//_:class[@name="Object"]/_:method[@name="setv"]//_:parameter[@name="names"]/_:array/@c:type'
>  -v "const gchar**" \
> -u 
> '//_:class[@name="Object"]/_:method[@name="setv"]//_:parameter[@name="values"]/_:array/@c:type'
>  -v "const GValue*" \
> -u 
> '//_:class[@name="Object"]/_:constructor[@name="new_with_properties"]//_:parameter[@name="names"]/_:array/@c:type'
>  -v "const char**" \
> -u 
> '//_:class[@name="Object"]/_:constructor[@name="new_with_properties"]//_:parameter[@name="values"]/_:array/@c:type'
>  -v "const GValue*" \
> -i '//_:interface[@name="TypePlugin" and not(@glib:type-struct)]' -t 'attr' 
> -n 'glib:type-struct' -v 'TypePluginClass' \
> -i '//_:record[@name="TypePluginClass" and not(@glib:is-gtype-struct-for)]' 
> -t 'attr' -n 'glib:is-gtype-struct-for' -v 'TypePlugin' \
> GObject-2.0.gir
> xmlstarlet ed -L \
> -u '//_:record[@name="PixbufModule"]/_:field[@name="module"]/_:type/@name' -v 
> "gpointer" \
> -u '//_:record[@name="PixbufModule"]/_:field[@name="module"]/_:type/@c:type' 
> -v "gpointer" \
> GdkPixbuf-2.0.gir
> sed -i 
> 's/girs_directories\s=\s\[\"\.\.\/gir-files\"\]/girs_directories=\[\".\"\]/' 
> /<>/Gir.toml
> gir -o .
> thread 'main' panicked at 'Incomplete library, unresolved: ["GLib.time_t"]', 
> src/library_postprocessing.rs:69:9
> note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
> make[1]: *** [debian/rules:18: execute_before_dh_auto_build] Error 101


The full build log is available from:
http://qa-logs.debian.net/2024/03/19/rust-gdk-pixbuf_0.18.5-1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240319;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240319=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.
--- End Message ---
--- Begin Message ---
Source: gir-rust-code-generator
Source-Version: 0.18.3-2
Done: Jeremy Bícha 

We believe that the bug you reported is fixed in the latest version of
gir-rust-code-generator, which is due to be installed 

Bug#1067336: marked as done (gir-rust-code-generator: update for time_t changes)

[Debian Bug Tracking System]

Your message dated Thu, 04 Apr 2024 00:22:17 +
with message-id 
and subject line Bug#1067256: fixed in gir-rust-code-generator 0.18.3-2
has caused the Debian Bug report #1067256,
regarding gir-rust-code-generator: update for time_t changes
to be marked as done.

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

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


-- 
1067256: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067256
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rust-gdk
Version: 0.18.0-3
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240319 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> cp /usr/share/gir-1.0/GLib-2.0.gir /<>
> cp /usr/share/gir-1.0/GObject-2.0.gir /<>
> cp /usr/share/gir-1.0/Pango-1.0.gir /<>
> cp /usr/share/gir-1.0/Gio-2.0.gir /<>
> cp /usr/share/gir-1.0/HarfBuzz-0.0.gir /<>
> cp /usr/share/gir-1.0/freetype2-2.0.gir /<>
> cp /usr/share/gir-1.0/PangoCairo-1.0.gir /<>
> cp /usr/share/gir-1.0/cairo-1.0.gir /<>
> cp /usr/share/gir-1.0/Gdk-3.0.gir /<>
> cp /usr/share/gir-1.0/GdkPixbuf-2.0.gir /<>
> cp /usr/share/gir-1.0/GModule-2.0.gir /<>
> xmlstarlet ed -L \
> -d '///_:alias[@name="Int32"]' \
> freetype2-2.0.gir
> xmlstarlet ed -L \
> -u 
> '//*[@glib:error-domain="g-option-context-error-quark"]/@glib:error-domain' 
> -v g-option-error-quark \
> -u 
> '//_:record[@name="KeyFile"]/_:method[@name="set_boolean_list"]//_:parameter[@name="list"]/_:array/@c:type'
>  -v "gboolean*" \
> -u 
> '//_:record[@name="KeyFile"]/_:method[@name="set_double_list"]//_:parameter[@name="list"]/_:array/@c:type'
>  -v "gdouble*" \
> -u 
> '//_:record[@name="KeyFile"]/_:method[@name="set_integer_list"]//_:parameter[@name="list"]/_:array/@c:type'
>  -v "gint*" \
> -u 
> '//_:record[@name="KeyFile"]/_:method[@name="set_locale_string_list"]//_:parameter[@name="list"]/_:array/@c:type'
>  -v "const gchar* const*" \
> -u 
> '//_:record[@name="KeyFile"]/_:method[@name="set_string_list"]//_:parameter[@name="list"]/_:array/@c:type'
>  -v "const gchar* const*" \
> GLib-2.0.gir
> xmlstarlet ed -L \
> -u 
> '//_:class[@name="Object"]/_:method[@name="getv"]//_:parameter[@name="names"]/_:array/@c:type'
>  -v "const gchar**" \
> -u 
> '//_:class[@name="Object"]/_:method[@name="getv"]//_:parameter[@name="values"]/_:array/@c:type'
>  -v "GValue*" \
> -u 
> '//_:class[@name="Object"]/_:method[@name="setv"]//_:parameter[@name="names"]/_:array/@c:type'
>  -v "const gchar**" \
> -u 
> '//_:class[@name="Object"]/_:method[@name="setv"]//_:parameter[@name="values"]/_:array/@c:type'
>  -v "const GValue*" \
> -u 
> '//_:class[@name="Object"]/_:constructor[@name="new_with_properties"]//_:parameter[@name="names"]/_:array/@c:type'
>  -v "const char**" \
> -u 
> '//_:class[@name="Object"]/_:constructor[@name="new_with_properties"]//_:parameter[@name="values"]/_:array/@c:type'
>  -v "const GValue*" \
> -i '//_:interface[@name="TypePlugin" and not(@glib:type-struct)]' -t 'attr' 
> -n 'glib:type-struct' -v 'TypePluginClass' \
> -i '//_:record[@name="TypePluginClass" and not(@glib:is-gtype-struct-for)]' 
> -t 'attr' -n 'glib:is-gtype-struct-for' -v 'TypePlugin' \
> GObject-2.0.gir
> xmlstarlet ed -L \
> -i '///_:type[not(@name) and @c:type="hb_font_t*"]' -t 'attr' -n 'name' -v 
> "gconstpointer" \
> -u '//_:type[@c:type="hb_font_t*"]/@c:type' -v "gconstpointer" \
> -i '///_:array[not(@name) and @c:type="hb_feature_t*"]' -t 'attr' -n 'name' 
> -v "gconstpointer" \
> -r '///_:array[@c:type="hb_feature_t*"]' -v "type" \
> -d '//_:type[@c:type="hb_feature_t*"]/*' \
> -d '//_:type[@c:type="hb_feature_t*"]/@length' \
> -d '//_:type[@c:type="hb_feature_t*"]/@zero-terminated' \
> -u '//_:type[@c:type="hb_feature_t*"]/@c:type' -v "gconstpointer" \
> -d '//_:record[@c:type="PangoGlyphVisAttr"]/_:field/@bits' \
> -d '//_:record[@c:type="PangoGlyphVisAttr"]/_:field[@name="is_color"]' \
> Pango-1.0.gir
> xmlstarlet ed -L \
> -d '///_:function[@c:identifier="hb_graphite2_face_get_gr_face"]' \
> -d '///_:function[@c:identifier="hb_graphite2_font_get_gr_font"]' \
> -d '///_:function[@c:identifier="hb_ft_face_create"]' \
> -d '///_:function[@c:identifier="hb_ft_face_create_cached"]' \
> -d '///_:function[@c:identifier="hb_ft_face_create_referenced"]' \
> -d '///_:function[@c:identifier="hb_ft_font_create"]' \
> -d '///_:function[@c:identifier="hb_ft_font_create_cached"]' \
> -d '///_:function[@c:identifier="hb_ft_font_create_referenced"]' \
> -d '///_:function[@c:identifier="hb_ft_font_get_face"]' \
> -d 

Bug#1067328: marked as done (gir-rust-code-generator: update for time_t changes)

[Debian Bug Tracking System]

Your message dated Thu, 04 Apr 2024 00:22:17 +
with message-id 
and subject line Bug#1067256: fixed in gir-rust-code-generator 0.18.3-2
has caused the Debian Bug report #1067256,
regarding gir-rust-code-generator: update for time_t changes
to be marked as done.

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

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


-- 
1067256: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067256
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rust-gtk
Version: 0.18.1-4
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240319 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> cp /usr/share/gir-1.0/GLib-2.0.gir /<>
> cp /usr/share/gir-1.0/GObject-2.0.gir /<>
> cp /usr/share/gir-1.0/Pango-1.0.gir /<>
> cp /usr/share/gir-1.0/Gio-2.0.gir /<>
> cp /usr/share/gir-1.0/HarfBuzz-0.0.gir /<>
> cp /usr/share/gir-1.0/freetype2-2.0.gir /<>
> cp /usr/share/gir-1.0/PangoCairo-1.0.gir /<>
> cp /usr/share/gir-1.0/Gtk-3.0.gir /<>
> cp /usr/share/gir-1.0/cairo-1.0.gir /<>
> cp /usr/share/gir-1.0/xlib-2.0.gir /<>
> cp /usr/share/gir-1.0/Atk-1.0.gir /<>
> cp /usr/share/gir-1.0/Gdk-3.0.gir /<>
> cp /usr/share/gir-1.0/GdkPixbuf-2.0.gir /<>
> cp /usr/share/gir-1.0/GModule-2.0.gir /<>
> xmlstarlet ed -L \
> -d '///_:method[@c:identifier="atk_plug_set_child"]' \
> Atk-1.0.gir
> xmlstarlet ed -L \
> -d '///_:alias[@name="Int32"]' \
> freetype2-2.0.gir
> xmlstarlet ed -L \
> -u 
> '//*[@glib:error-domain="g-option-context-error-quark"]/@glib:error-domain' 
> -v g-option-error-quark \
> -u 
> '//_:record[@name="KeyFile"]/_:method[@name="set_boolean_list"]//_:parameter[@name="list"]/_:array/@c:type'
>  -v "gboolean*" \
> -u 
> '//_:record[@name="KeyFile"]/_:method[@name="set_double_list"]//_:parameter[@name="list"]/_:array/@c:type'
>  -v "gdouble*" \
> -u 
> '//_:record[@name="KeyFile"]/_:method[@name="set_integer_list"]//_:parameter[@name="list"]/_:array/@c:type'
>  -v "gint*" \
> -u 
> '//_:record[@name="KeyFile"]/_:method[@name="set_locale_string_list"]//_:parameter[@name="list"]/_:array/@c:type'
>  -v "const gchar* const*" \
> -u 
> '//_:record[@name="KeyFile"]/_:method[@name="set_string_list"]//_:parameter[@name="list"]/_:array/@c:type'
>  -v "const gchar* const*" \
> GLib-2.0.gir
> xmlstarlet ed -L \
> -u 
> '//_:class[@name="Object"]/_:method[@name="getv"]//_:parameter[@name="names"]/_:array/@c:type'
>  -v "const gchar**" \
> -u 
> '//_:class[@name="Object"]/_:method[@name="getv"]//_:parameter[@name="values"]/_:array/@c:type'
>  -v "GValue*" \
> -u 
> '//_:class[@name="Object"]/_:method[@name="setv"]//_:parameter[@name="names"]/_:array/@c:type'
>  -v "const gchar**" \
> -u 
> '//_:class[@name="Object"]/_:method[@name="setv"]//_:parameter[@name="values"]/_:array/@c:type'
>  -v "const GValue*" \
> -u 
> '//_:class[@name="Object"]/_:constructor[@name="new_with_properties"]//_:parameter[@name="names"]/_:array/@c:type'
>  -v "const char**" \
> -u 
> '//_:class[@name="Object"]/_:constructor[@name="new_with_properties"]//_:parameter[@name="values"]/_:array/@c:type'
>  -v "const GValue*" \
> -i '//_:interface[@name="TypePlugin" and not(@glib:type-struct)]' -t 'attr' 
> -n 'glib:type-struct' -v 'TypePluginClass' \
> -i '//_:record[@name="TypePluginClass" and not(@glib:is-gtype-struct-for)]' 
> -t 'attr' -n 'glib:is-gtype-struct-for' -v 'TypePlugin' \
> GObject-2.0.gir
> xmlstarlet ed -L \
> -i '///_:type[not(@name) and @c:type="hb_font_t*"]' -t 'attr' -n 'name' -v 
> "gconstpointer" \
> -u '//_:type[@c:type="hb_font_t*"]/@c:type' -v "gconstpointer" \
> -i '///_:array[not(@name) and @c:type="hb_feature_t*"]' -t 'attr' -n 'name' 
> -v "gconstpointer" \
> -r '///_:array[@c:type="hb_feature_t*"]' -v "type" \
> -d '//_:type[@c:type="hb_feature_t*"]/*' \
> -d '//_:type[@c:type="hb_feature_t*"]/@length' \
> -d '//_:type[@c:type="hb_feature_t*"]/@zero-terminated' \
> -u '//_:type[@c:type="hb_feature_t*"]/@c:type' -v "gconstpointer" \
> -d '//_:record[@c:type="PangoGlyphVisAttr"]/_:field/@bits' \
> -d '//_:record[@c:type="PangoGlyphVisAttr"]/_:field[@name="is_color"]' \
> Pango-1.0.gir
> xmlstarlet ed -L \
> -d '///_:function[@c:identifier="hb_graphite2_face_get_gr_face"]' \
> -d '///_:function[@c:identifier="hb_graphite2_font_get_gr_font"]' \
> -d '///_:function[@c:identifier="hb_ft_face_create"]' \
> -d '///_:function[@c:identifier="hb_ft_face_create_cached"]' \
> -d '///_:function[@c:identifier="hb_ft_face_create_referenced"]' \
> -d '///_:function[@c:identifier="hb_ft_font_create"]' \
> 

Bug#1067322: marked as done (gir-rust-code-generator: update for time_t changes)

[Debian Bug Tracking System]

Your message dated Thu, 04 Apr 2024 00:22:17 +
with message-id 
and subject line Bug#1067256: fixed in gir-rust-code-generator 0.18.3-2
has caused the Debian Bug report #1067256,
regarding gir-rust-code-generator: update for time_t changes
to be marked as done.

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

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


-- 
1067256: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067256
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rust-gtk-layer-shell-sys
Version: 0.7.0-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240319 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> cp /usr/share/gir-1.0/GtkLayerShell-0.1.gir /<>
> cp /usr/share/gir-1.0/GLib-2.0.gir /<>
> cp /usr/share/gir-1.0/GObject-2.0.gir /<>
> cp /usr/share/gir-1.0/Pango-1.0.gir /<>
> cp /usr/share/gir-1.0/Gio-2.0.gir /<>
> cp /usr/share/gir-1.0/HarfBuzz-0.0.gir /<>
> cp /usr/share/gir-1.0/freetype2-2.0.gir /<>
> cp /usr/share/gir-1.0/PangoCairo-1.0.gir /<>
> cp /usr/share/gir-1.0/Gtk-3.0.gir /<>
> cp /usr/share/gir-1.0/cairo-1.0.gir /<>
> cp /usr/share/gir-1.0/xlib-2.0.gir /<>
> cp /usr/share/gir-1.0/Atk-1.0.gir /<>
> cp /usr/share/gir-1.0/Gdk-3.0.gir /<>
> cp /usr/share/gir-1.0/GdkPixbuf-2.0.gir /<>
> cp /usr/share/gir-1.0/GModule-2.0.gir /<>
> xmlstarlet ed -L \
> -d '///_:method[@c:identifier="atk_plug_set_child"]' \
> Atk-1.0.gir
> xmlstarlet ed -L \
> -d '///_:alias[@name="Int32"]' \
> freetype2-2.0.gir
> xmlstarlet ed -L \
> -u 
> '//*[@glib:error-domain="g-option-context-error-quark"]/@glib:error-domain' 
> -v g-option-error-quark \
> -u 
> '//_:record[@name="KeyFile"]/_:method[@name="set_boolean_list"]//_:parameter[@name="list"]/_:array/@c:type'
>  -v "gboolean*" \
> -u 
> '//_:record[@name="KeyFile"]/_:method[@name="set_double_list"]//_:parameter[@name="list"]/_:array/@c:type'
>  -v "gdouble*" \
> -u 
> '//_:record[@name="KeyFile"]/_:method[@name="set_integer_list"]//_:parameter[@name="list"]/_:array/@c:type'
>  -v "gint*" \
> -u 
> '//_:record[@name="KeyFile"]/_:method[@name="set_locale_string_list"]//_:parameter[@name="list"]/_:array/@c:type'
>  -v "const gchar* const*" \
> -u 
> '//_:record[@name="KeyFile"]/_:method[@name="set_string_list"]//_:parameter[@name="list"]/_:array/@c:type'
>  -v "const gchar* const*" \
> GLib-2.0.gir
> xmlstarlet ed -L \
> -u 
> '//_:class[@name="Object"]/_:method[@name="getv"]//_:parameter[@name="names"]/_:array/@c:type'
>  -v "const gchar**" \
> -u 
> '//_:class[@name="Object"]/_:method[@name="getv"]//_:parameter[@name="values"]/_:array/@c:type'
>  -v "GValue*" \
> -u 
> '//_:class[@name="Object"]/_:method[@name="setv"]//_:parameter[@name="names"]/_:array/@c:type'
>  -v "const gchar**" \
> -u 
> '//_:class[@name="Object"]/_:method[@name="setv"]//_:parameter[@name="values"]/_:array/@c:type'
>  -v "const GValue*" \
> -u 
> '//_:class[@name="Object"]/_:constructor[@name="new_with_properties"]//_:parameter[@name="names"]/_:array/@c:type'
>  -v "const char**" \
> -u 
> '//_:class[@name="Object"]/_:constructor[@name="new_with_properties"]//_:parameter[@name="values"]/_:array/@c:type'
>  -v "const GValue*" \
> -i '//_:interface[@name="TypePlugin" and not(@glib:type-struct)]' -t 'attr' 
> -n 'glib:type-struct' -v 'TypePluginClass' \
> -i '//_:record[@name="TypePluginClass" and not(@glib:is-gtype-struct-for)]' 
> -t 'attr' -n 'glib:is-gtype-struct-for' -v 'TypePlugin' \
> GObject-2.0.gir
> xmlstarlet ed -L \
> -i '///_:type[not(@name) and @c:type="hb_font_t*"]' -t 'attr' -n 'name' -v 
> "gconstpointer" \
> -u '//_:type[@c:type="hb_font_t*"]/@c:type' -v "gconstpointer" \
> -i '///_:array[not(@name) and @c:type="hb_feature_t*"]' -t 'attr' -n 'name' 
> -v "gconstpointer" \
> -r '///_:array[@c:type="hb_feature_t*"]' -v "type" \
> -d '//_:type[@c:type="hb_feature_t*"]/*' \
> -d '//_:type[@c:type="hb_feature_t*"]/@length' \
> -d '//_:type[@c:type="hb_feature_t*"]/@zero-terminated' \
> -u '//_:type[@c:type="hb_feature_t*"]/@c:type' -v "gconstpointer" \
> -d '//_:record[@c:type="PangoGlyphVisAttr"]/_:field/@bits' \
> -d '//_:record[@c:type="PangoGlyphVisAttr"]/_:field[@name="is_color"]' \
> Pango-1.0.gir
> xmlstarlet ed -L \
> -d '///_:function[@c:identifier="hb_graphite2_face_get_gr_face"]' \
> -d '///_:function[@c:identifier="hb_graphite2_font_get_gr_font"]' \
> -d '///_:function[@c:identifier="hb_ft_face_create"]' \
> -d '///_:function[@c:identifier="hb_ft_face_create_cached"]' \
> -d 

Bug#1067314: marked as done (gir-rust-code-generator: update for time_t changes)

[Debian Bug Tracking System]

Your message dated Thu, 04 Apr 2024 00:22:17 +
with message-id 
and subject line Bug#1067256: fixed in gir-rust-code-generator 0.18.3-2
has caused the Debian Bug report #1067256,
regarding gir-rust-code-generator: update for time_t changes
to be marked as done.

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

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


-- 
1067256: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067256
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rust-gdkx11-sys
Version: 0.18.0-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240319 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> cp /usr/share/gir-1.0/GLib-2.0.gir /<>
> cp /usr/share/gir-1.0/GObject-2.0.gir /<>
> cp /usr/share/gir-1.0/Gio-2.0.gir /<>
> cp /usr/share/gir-1.0/GdkPixbuf-2.0.gir /<>
> cp /usr/share/gir-1.0/freetype2-2.0.gir /<>
> cp /usr/share/gir-1.0/cairo-1.0.gir /<>
> cp /usr/share/gir-1.0/Gdk-3.0.gir /<>
> cp /usr/share/gir-1.0/HarfBuzz-0.0.gir /<>
> cp /usr/share/gir-1.0/GdkX11-3.0.gir /<>
> cp /usr/share/gir-1.0/GModule-2.0.gir /<>
> cp /usr/share/gir-1.0/xlib-2.0.gir /<>
> cp /usr/share/gir-1.0/Pango-1.0.gir /<>
> xmlstarlet ed -L \
> -d '///_:alias[@name="Int32"]' \
> freetype2-2.0.gir
> xmlstarlet ed -L \
> -u '//_:record[@name="PixbufModule"]/_:field[@name="module"]/_:type/@name' -v 
> "gpointer" \
> -u '//_:record[@name="PixbufModule"]/_:field[@name="module"]/_:type/@c:type' 
> -v "gpointer" \
> GdkPixbuf-2.0.gir
> xmlstarlet ed -L \
> -d '///_:function[@c:identifier="hb_graphite2_face_get_gr_face"]' \
> -d '///_:function[@c:identifier="hb_graphite2_font_get_gr_font"]' \
> -d '///_:function[@c:identifier="hb_ft_face_create"]' \
> -d '///_:function[@c:identifier="hb_ft_face_create_cached"]' \
> -d '///_:function[@c:identifier="hb_ft_face_create_referenced"]' \
> -d '///_:function[@c:identifier="hb_ft_font_create"]' \
> -d '///_:function[@c:identifier="hb_ft_font_create_cached"]' \
> -d '///_:function[@c:identifier="hb_ft_font_create_referenced"]' \
> -d '///_:function[@c:identifier="hb_ft_font_get_face"]' \
> -d '///_:function[@c:identifier="hb_ft_font_lock_face"]' \
> HarfBuzz-0.0.gir
> xmlstarlet ed -L \
> -i '///_:type[not(@name) and @c:type="hb_font_t*"]' -t 'attr' -n 'name' -v 
> "gconstpointer" \
> -u '//_:type[@c:type="hb_font_t*"]/@c:type' -v "gconstpointer" \
> -i '///_:array[not(@name) and @c:type="hb_feature_t*"]' -t 'attr' -n 'name' 
> -v "gconstpointer" \
> -r '///_:array[@c:type="hb_feature_t*"]' -v "type" \
> -d '//_:type[@c:type="hb_feature_t*"]/*' \
> -d '//_:type[@c:type="hb_feature_t*"]/@length' \
> -d '//_:type[@c:type="hb_feature_t*"]/@zero-terminated' \
> -u '//_:type[@c:type="hb_feature_t*"]/@c:type' -v "gconstpointer" \
> -d '//_:record[@c:type="PangoGlyphVisAttr"]/_:field/@bits' \
> -d '//_:record[@c:type="PangoGlyphVisAttr"]/_:field[@name="is_color"]' \
> Pango-1.0.gir
> xmlstarlet ed -L \
> -u 
> '//*[@glib:error-domain="g-option-context-error-quark"]/@glib:error-domain' 
> -v g-option-error-quark \
> -u 
> '//_:record[@name="KeyFile"]/_:method[@name="set_boolean_list"]//_:parameter[@name="list"]/_:array/@c:type'
>  -v "gboolean*" \
> -u 
> '//_:record[@name="KeyFile"]/_:method[@name="set_double_list"]//_:parameter[@name="list"]/_:array/@c:type'
>  -v "gdouble*" \
> -u 
> '//_:record[@name="KeyFile"]/_:method[@name="set_integer_list"]//_:parameter[@name="list"]/_:array/@c:type'
>  -v "gint*" \
> -u 
> '//_:record[@name="KeyFile"]/_:method[@name="set_locale_string_list"]//_:parameter[@name="list"]/_:array/@c:type'
>  -v "const gchar* const*" \
> -u 
> '//_:record[@name="KeyFile"]/_:method[@name="set_string_list"]//_:parameter[@name="list"]/_:array/@c:type'
>  -v "const gchar* const*" \
> GLib-2.0.gir
> xmlstarlet ed -L \
> -u 
> '//_:class[@name="Object"]/_:method[@name="getv"]//_:parameter[@name="names"]/_:array/@c:type'
>  -v "const gchar**" \
> -u 
> '//_:class[@name="Object"]/_:method[@name="getv"]//_:parameter[@name="values"]/_:array/@c:type'
>  -v "GValue*" \
> -u 
> '//_:class[@name="Object"]/_:method[@name="setv"]//_:parameter[@name="names"]/_:array/@c:type'
>  -v "const gchar**" \
> -u 
> '//_:class[@name="Object"]/_:method[@name="setv"]//_:parameter[@name="values"]/_:array/@c:type'
>  -v "const GValue*" \
> -u 
> '//_:class[@name="Object"]/_:constructor[@name="new_with_properties"]//_:parameter[@name="names"]/_:array/@c:type'
>  -v "const char**" \
> -u 
> 

Bug#1067307: marked as done (gir-rust-code-generator: update for time_t changes)

[Debian Bug Tracking System]

Your message dated Thu, 04 Apr 2024 00:22:17 +
with message-id 
and subject line Bug#1067256: fixed in gir-rust-code-generator 0.18.3-2
has caused the Debian Bug report #1067256,
regarding gir-rust-code-generator: update for time_t changes
to be marked as done.

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

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


-- 
1067256: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067256
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rust-gdkx11
Version: 0.18.0-3
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240319 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> cp /usr/share/gir-1.0/GLib-2.0.gir /<>
> cp /usr/share/gir-1.0/GObject-2.0.gir /<>
> cp /usr/share/gir-1.0/Gio-2.0.gir /<>
> cp /usr/share/gir-1.0/GdkPixbuf-2.0.gir /<>
> cp /usr/share/gir-1.0/freetype2-2.0.gir /<>
> cp /usr/share/gir-1.0/cairo-1.0.gir /<>
> cp /usr/share/gir-1.0/Gdk-3.0.gir /<>
> cp /usr/share/gir-1.0/HarfBuzz-0.0.gir /<>
> cp /usr/share/gir-1.0/GdkX11-3.0.gir /<>
> cp /usr/share/gir-1.0/GModule-2.0.gir /<>
> cp /usr/share/gir-1.0/xlib-2.0.gir /<>
> cp /usr/share/gir-1.0/Pango-1.0.gir /<>
> xmlstarlet ed -L \
> -d '///_:alias[@name="Int32"]' \
> freetype2-2.0.gir
> xmlstarlet ed -L \
> -u '//_:record[@name="PixbufModule"]/_:field[@name="module"]/_:type/@name' -v 
> "gpointer" \
> -u '//_:record[@name="PixbufModule"]/_:field[@name="module"]/_:type/@c:type' 
> -v "gpointer" \
> GdkPixbuf-2.0.gir
> xmlstarlet ed -L \
> -d '///_:function[@c:identifier="hb_graphite2_face_get_gr_face"]' \
> -d '///_:function[@c:identifier="hb_graphite2_font_get_gr_font"]' \
> -d '///_:function[@c:identifier="hb_ft_face_create"]' \
> -d '///_:function[@c:identifier="hb_ft_face_create_cached"]' \
> -d '///_:function[@c:identifier="hb_ft_face_create_referenced"]' \
> -d '///_:function[@c:identifier="hb_ft_font_create"]' \
> -d '///_:function[@c:identifier="hb_ft_font_create_cached"]' \
> -d '///_:function[@c:identifier="hb_ft_font_create_referenced"]' \
> -d '///_:function[@c:identifier="hb_ft_font_get_face"]' \
> -d '///_:function[@c:identifier="hb_ft_font_lock_face"]' \
> HarfBuzz-0.0.gir
> xmlstarlet ed -L \
> -i '///_:type[not(@name) and @c:type="hb_font_t*"]' -t 'attr' -n 'name' -v 
> "gconstpointer" \
> -u '//_:type[@c:type="hb_font_t*"]/@c:type' -v "gconstpointer" \
> -i '///_:array[not(@name) and @c:type="hb_feature_t*"]' -t 'attr' -n 'name' 
> -v "gconstpointer" \
> -r '///_:array[@c:type="hb_feature_t*"]' -v "type" \
> -d '//_:type[@c:type="hb_feature_t*"]/*' \
> -d '//_:type[@c:type="hb_feature_t*"]/@length' \
> -d '//_:type[@c:type="hb_feature_t*"]/@zero-terminated' \
> -u '//_:type[@c:type="hb_feature_t*"]/@c:type' -v "gconstpointer" \
> -d '//_:record[@c:type="PangoGlyphVisAttr"]/_:field/@bits' \
> -d '//_:record[@c:type="PangoGlyphVisAttr"]/_:field[@name="is_color"]' \
> Pango-1.0.gir
> xmlstarlet ed -L \
> -u 
> '//*[@glib:error-domain="g-option-context-error-quark"]/@glib:error-domain' 
> -v g-option-error-quark \
> -u 
> '//_:record[@name="KeyFile"]/_:method[@name="set_boolean_list"]//_:parameter[@name="list"]/_:array/@c:type'
>  -v "gboolean*" \
> -u 
> '//_:record[@name="KeyFile"]/_:method[@name="set_double_list"]//_:parameter[@name="list"]/_:array/@c:type'
>  -v "gdouble*" \
> -u 
> '//_:record[@name="KeyFile"]/_:method[@name="set_integer_list"]//_:parameter[@name="list"]/_:array/@c:type'
>  -v "gint*" \
> -u 
> '//_:record[@name="KeyFile"]/_:method[@name="set_locale_string_list"]//_:parameter[@name="list"]/_:array/@c:type'
>  -v "const gchar* const*" \
> -u 
> '//_:record[@name="KeyFile"]/_:method[@name="set_string_list"]//_:parameter[@name="list"]/_:array/@c:type'
>  -v "const gchar* const*" \
> GLib-2.0.gir
> xmlstarlet ed -L \
> -u 
> '//_:class[@name="Object"]/_:method[@name="getv"]//_:parameter[@name="names"]/_:array/@c:type'
>  -v "const gchar**" \
> -u 
> '//_:class[@name="Object"]/_:method[@name="getv"]//_:parameter[@name="values"]/_:array/@c:type'
>  -v "GValue*" \
> -u 
> '//_:class[@name="Object"]/_:method[@name="setv"]//_:parameter[@name="names"]/_:array/@c:type'
>  -v "const gchar**" \
> -u 
> '//_:class[@name="Object"]/_:method[@name="setv"]//_:parameter[@name="values"]/_:array/@c:type'
>  -v "const GValue*" \
> -u 
> '//_:class[@name="Object"]/_:constructor[@name="new_with_properties"]//_:parameter[@name="names"]/_:array/@c:type'
>  -v "const char**" \
> -u 
> 

Bug#1067302: marked as done (gir-rust-code-generator: update for time_t changes)

[Debian Bug Tracking System]

Your message dated Thu, 04 Apr 2024 00:22:17 +
with message-id 
and subject line Bug#1067256: fixed in gir-rust-code-generator 0.18.3-2
has caused the Debian Bug report #1067256,
regarding gir-rust-code-generator: update for time_t changes
to be marked as done.

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

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


-- 
1067256: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067256
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rust-gobject-sys
Version: 0.18.0-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240319 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> cp /usr/share/gir-1.0/GObject-2.0.gir /<>
> cp /usr/share/gir-1.0/GLib-2.0.gir /<>
> xmlstarlet ed -L \
> -u 
> '//*[@glib:error-domain="g-option-context-error-quark"]/@glib:error-domain' 
> -v g-option-error-quark \
> -u 
> '//_:record[@name="KeyFile"]/_:method[@name="set_boolean_list"]//_:parameter[@name="list"]/_:array/@c:type'
>  -v "gboolean*" \
> -u 
> '//_:record[@name="KeyFile"]/_:method[@name="set_double_list"]//_:parameter[@name="list"]/_:array/@c:type'
>  -v "gdouble*" \
> -u 
> '//_:record[@name="KeyFile"]/_:method[@name="set_integer_list"]//_:parameter[@name="list"]/_:array/@c:type'
>  -v "gint*" \
> -u 
> '//_:record[@name="KeyFile"]/_:method[@name="set_locale_string_list"]//_:parameter[@name="list"]/_:array/@c:type'
>  -v "const gchar* const*" \
> -u 
> '//_:record[@name="KeyFile"]/_:method[@name="set_string_list"]//_:parameter[@name="list"]/_:array/@c:type'
>  -v "const gchar* const*" \
> GLib-2.0.gir
> xmlstarlet ed -L \
> -u 
> '//_:class[@name="Object"]/_:method[@name="getv"]//_:parameter[@name="names"]/_:array/@c:type'
>  -v "const gchar**" \
> -u 
> '//_:class[@name="Object"]/_:method[@name="getv"]//_:parameter[@name="values"]/_:array/@c:type'
>  -v "GValue*" \
> -u 
> '//_:class[@name="Object"]/_:method[@name="setv"]//_:parameter[@name="names"]/_:array/@c:type'
>  -v "const gchar**" \
> -u 
> '//_:class[@name="Object"]/_:method[@name="setv"]//_:parameter[@name="values"]/_:array/@c:type'
>  -v "const GValue*" \
> -u 
> '//_:class[@name="Object"]/_:constructor[@name="new_with_properties"]//_:parameter[@name="names"]/_:array/@c:type'
>  -v "const char**" \
> -u 
> '//_:class[@name="Object"]/_:constructor[@name="new_with_properties"]//_:parameter[@name="values"]/_:array/@c:type'
>  -v "const GValue*" \
> -i '//_:interface[@name="TypePlugin" and not(@glib:type-struct)]' -t 'attr' 
> -n 'glib:type-struct' -v 'TypePluginClass' \
> -i '//_:record[@name="TypePluginClass" and not(@glib:is-gtype-struct-for)]' 
> -t 'attr' -n 'glib:is-gtype-struct-for' -v 'TypePlugin' \
> GObject-2.0.gir
> sed -i 's/girs_directories\s=\s\[\"\.\.\/\.\.\/gir-files\"\]/girs_directories 
> = \[\".\"\]/' /<>/Gir.toml
> gir -o .
> thread 'main' panicked at 'Incomplete library, unresolved: ["GLib.time_t"]', 
> src/library_postprocessing.rs:69:9
> note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
> make[1]: *** [debian/rules:13: execute_before_dh_auto_build] Error 101


The full build log is available from:
http://qa-logs.debian.net/2024/03/19/rust-gobject-sys_0.18.0-2_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240319;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240319=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.
--- End Message ---
--- Begin Message ---
Source: gir-rust-code-generator
Source-Version: 0.18.3-2
Done: Jeremy Bícha 

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

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

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

Debian distribution maintenance software
pp.

Bug#1067279: marked as done (gir-rust-code-generator: update for time_t changes)

[Debian Bug Tracking System]

Your message dated Thu, 04 Apr 2024 00:22:17 +
with message-id 
and subject line Bug#1067256: fixed in gir-rust-code-generator 0.18.3-2
has caused the Debian Bug report #1067256,
regarding gir-rust-code-generator: update for time_t changes
to be marked as done.

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

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


-- 
1067256: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067256
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rust-gdk-pixbuf-sys
Version: 0.18.0-4
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240319 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> cp /usr/share/gir-1.0/GLib-2.0.gir /<>
> cp /usr/share/gir-1.0/GObject-2.0.gir /<>
> cp /usr/share/gir-1.0/Gio-2.0.gir /<>
> cp /usr/share/gir-1.0/GdkPixbuf-2.0.gir /<>
> cp /usr/share/gir-1.0/GModule-2.0.gir /<>
> xmlstarlet ed -L \
> -u 
> '//*[@glib:error-domain="g-option-context-error-quark"]/@glib:error-domain' 
> -v g-option-error-quark \
> -u 
> '//_:record[@name="KeyFile"]/_:method[@name="set_boolean_list"]//_:parameter[@name="list"]/_:array/@c:type'
>  -v "gboolean*" \
> -u 
> '//_:record[@name="KeyFile"]/_:method[@name="set_double_list"]//_:parameter[@name="list"]/_:array/@c:type'
>  -v "gdouble*" \
> -u 
> '//_:record[@name="KeyFile"]/_:method[@name="set_integer_list"]//_:parameter[@name="list"]/_:array/@c:type'
>  -v "gint*" \
> -u 
> '//_:record[@name="KeyFile"]/_:method[@name="set_locale_string_list"]//_:parameter[@name="list"]/_:array/@c:type'
>  -v "const gchar* const*" \
> -u 
> '//_:record[@name="KeyFile"]/_:method[@name="set_string_list"]//_:parameter[@name="list"]/_:array/@c:type'
>  -v "const gchar* const*" \
> GLib-2.0.gir
> xmlstarlet ed -L \
> -u 
> '//_:class[@name="Object"]/_:method[@name="getv"]//_:parameter[@name="names"]/_:array/@c:type'
>  -v "const gchar**" \
> -u 
> '//_:class[@name="Object"]/_:method[@name="getv"]//_:parameter[@name="values"]/_:array/@c:type'
>  -v "GValue*" \
> -u 
> '//_:class[@name="Object"]/_:method[@name="setv"]//_:parameter[@name="names"]/_:array/@c:type'
>  -v "const gchar**" \
> -u 
> '//_:class[@name="Object"]/_:method[@name="setv"]//_:parameter[@name="values"]/_:array/@c:type'
>  -v "const GValue*" \
> -u 
> '//_:class[@name="Object"]/_:constructor[@name="new_with_properties"]//_:parameter[@name="names"]/_:array/@c:type'
>  -v "const char**" \
> -u 
> '//_:class[@name="Object"]/_:constructor[@name="new_with_properties"]//_:parameter[@name="values"]/_:array/@c:type'
>  -v "const GValue*" \
> -i '//_:interface[@name="TypePlugin" and not(@glib:type-struct)]' -t 'attr' 
> -n 'glib:type-struct' -v 'TypePluginClass' \
> -i '//_:record[@name="TypePluginClass" and not(@glib:is-gtype-struct-for)]' 
> -t 'attr' -n 'glib:is-gtype-struct-for' -v 'TypePlugin' \
> GObject-2.0.gir
> xmlstarlet ed -L \
> -u '//_:record[@name="PixbufModule"]/_:field[@name="module"]/_:type/@name' -v 
> "gpointer" \
> -u '//_:record[@name="PixbufModule"]/_:field[@name="module"]/_:type/@c:type' 
> -v "gpointer" \
> GdkPixbuf-2.0.gir
> sed -i 
> 's/girs_directories\s=\s\[\"\.\.\/\.\.\/gir-files\"\]/girs_directories=\[\".\"\]/'
>  /<>/Gir.toml
> gir -o .
> thread 'main' panicked at 'Incomplete library, unresolved: ["GLib.time_t"]', 
> src/library_postprocessing.rs:69:9
> note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
> make[1]: *** [debian/rules:18: execute_before_dh_auto_build] Error 101


The full build log is available from:
http://qa-logs.debian.net/2024/03/19/rust-gdk-pixbuf-sys_0.18.0-4_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240319;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240319=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.
--- End Message ---
--- Begin Message ---
Source: gir-rust-code-generator
Source-Version: 0.18.3-2
Done: Jeremy Bícha 

We believe that the bug you reported is fixed in the latest version of
gir-rust-code-generator, which is due to 

Bug#1067280: marked as done (gir-rust-code-generator: update for time_t changes)

[Debian Bug Tracking System]

Your message dated Thu, 04 Apr 2024 00:22:17 +
with message-id 
and subject line Bug#1067256: fixed in gir-rust-code-generator 0.18.3-2
has caused the Debian Bug report #1067256,
regarding gir-rust-code-generator: update for time_t changes
to be marked as done.

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

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


-- 
1067256: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067256
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rust-gdk4-sys
Version: 0.7.2-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240319 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> cp /usr/share/gir-1.0/GLib-2.0.gir /<>
> cp /usr/share/gir-1.0/Gdk-4.0.gir /<>
> cp /usr/share/gir-1.0/GdkPixbuf-2.0.gir /<>
> cp /usr/share/gir-1.0/GModule-2.0.gir /<>
> cp /usr/share/gir-1.0/Gio-2.0.gir /<>
> cp /usr/share/gir-1.0/GObject-2.0.gir /<>
> cp /usr/share/gir-1.0/Pango-1.0.gir /<>
> cp /usr/share/gir-1.0/HarfBuzz-0.0.gir /<>
> cp /usr/share/gir-1.0/freetype2-2.0.gir /<>
> cp /usr/share/gir-1.0/cairo-1.0.gir /<>
> cp /usr/share/gir-1.0/PangoCairo-1.0.gir /<>
> xmlstarlet ed -L \
> -d '///_:alias[@name="Int32"]' \
> freetype2-2.0.gir
> xmlstarlet ed -L \
> -i '///_:type[not(@name) and @c:type="hb_font_t*"]' -t 'attr' -n 'name' -v 
> "gconstpointer" \
> -u '//_:type[@c:type="hb_font_t*"]/@c:type' -v "gconstpointer" \
> -i '///_:array[not(@name) and @c:type="hb_feature_t*"]' -t 'attr' -n 'name' 
> -v "gconstpointer" \
> -r '///_:array[@c:type="hb_feature_t*"]' -v "type" \
> -d '//_:type[@c:type="hb_feature_t*"]/*' \
> -d '//_:type[@c:type="hb_feature_t*"]/@length' \
> -d '//_:type[@c:type="hb_feature_t*"]/@zero-terminated' \
> -u '//_:type[@c:type="hb_feature_t*"]/@c:type' -v "gconstpointer" \
> -d '//_:record[@c:type="PangoGlyphVisAttr"]/_:field/@bits' \
> -d '//_:record[@c:type="PangoGlyphVisAttr"]/_:field[@name="is_color"]' \
> Pango-1.0.gir
> xmlstarlet ed -L \
> -u 
> '//*[@glib:error-domain="g-option-context-error-quark"]/@glib:error-domain' 
> -v g-option-error-quark \
> -u 
> '//_:record[@name="KeyFile"]/_:method[@name="set_boolean_list"]//_:parameter[@name="list"]/_:array/@c:type'
>  -v "gboolean*" \
> -u 
> '//_:record[@name="KeyFile"]/_:method[@name="set_double_list"]//_:parameter[@name="list"]/_:array/@c:type'
>  -v "gdouble*" \
> -u 
> '//_:record[@name="KeyFile"]/_:method[@name="set_integer_list"]//_:parameter[@name="list"]/_:array/@c:type'
>  -v "gint*" \
> -u 
> '//_:record[@name="KeyFile"]/_:method[@name="set_locale_string_list"]//_:parameter[@name="list"]/_:array/@c:type'
>  -v "const gchar* const*" \
> -u 
> '//_:record[@name="KeyFile"]/_:method[@name="set_string_list"]//_:parameter[@name="list"]/_:array/@c:type'
>  -v "const gchar* const*" \
> GLib-2.0.gir
> xmlstarlet ed -L \
> -u 
> '//_:class[@name="Object"]/_:method[@name="getv"]//_:parameter[@name="names"]/_:array/@c:type'
>  -v "const gchar**" \
> -u 
> '//_:class[@name="Object"]/_:method[@name="getv"]//_:parameter[@name="values"]/_:array/@c:type'
>  -v "GValue*" \
> -u 
> '//_:class[@name="Object"]/_:method[@name="setv"]//_:parameter[@name="names"]/_:array/@c:type'
>  -v "const gchar**" \
> -u 
> '//_:class[@name="Object"]/_:method[@name="setv"]//_:parameter[@name="values"]/_:array/@c:type'
>  -v "const GValue*" \
> -u 
> '//_:class[@name="Object"]/_:constructor[@name="new_with_properties"]//_:parameter[@name="names"]/_:array/@c:type'
>  -v "const char**" \
> -u 
> '//_:class[@name="Object"]/_:constructor[@name="new_with_properties"]//_:parameter[@name="values"]/_:array/@c:type'
>  -v "const GValue*" \
> -i '//_:interface[@name="TypePlugin" and not(@glib:type-struct)]' -t 'attr' 
> -n 'glib:type-struct' -v 'TypePluginClass' \
> -i '//_:record[@name="TypePluginClass" and not(@glib:is-gtype-struct-for)]' 
> -t 'attr' -n 'glib:is-gtype-struct-for' -v 'TypePlugin' \
> GObject-2.0.gir
> xmlstarlet ed -L \
> -u '//_:record[@name="PixbufModule"]/_:field[@name="module"]/_:type/@name' -v 
> "gpointer" \
> -u '//_:record[@name="PixbufModule"]/_:field[@name="module"]/_:type/@c:type' 
> -v "gpointer" \
> GdkPixbuf-2.0.gir
> xmlstarlet ed -L \
> -d '///_:function[@c:identifier="hb_graphite2_face_get_gr_face"]' \
> -d '///_:function[@c:identifier="hb_graphite2_font_get_gr_font"]' \
> -d '///_:function[@c:identifier="hb_ft_face_create"]' \
> -d '///_:function[@c:identifier="hb_ft_face_create_cached"]' \
> -d '///_:function[@c:identifier="hb_ft_face_create_referenced"]' \
> -d 

Bug#1067261: marked as done (gir-rust-code-generator: update for time_t changes)

[Debian Bug Tracking System]

Your message dated Thu, 04 Apr 2024 00:22:17 +
with message-id 
and subject line Bug#1067256: fixed in gir-rust-code-generator 0.18.3-2
has caused the Debian Bug report #1067256,
regarding gir-rust-code-generator: update for time_t changes
to be marked as done.

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

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


-- 
1067256: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067256
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rust-atk
Version: 0.18.0-3
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240319 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> cp /usr/share/gir-1.0/GLib-2.0.gir /<>
> cp /usr/share/gir-1.0/GObject-2.0.gir /<>
> cp /usr/share/gir-1.0/Atk-1.0.gir /<>
> xmlstarlet ed -L \
> -u 
> '//*[@glib:error-domain="g-option-context-error-quark"]/@glib:error-domain' 
> -v g-option-error-quark \
> -u 
> '//_:record[@name="KeyFile"]/_:method[@name="set_boolean_list"]//_:parameter[@name="list"]/_:array/@c:type'
>  -v "gboolean*" \
> -u 
> '//_:record[@name="KeyFile"]/_:method[@name="set_double_list"]//_:parameter[@name="list"]/_:array/@c:type'
>  -v "gdouble*" \
> -u 
> '//_:record[@name="KeyFile"]/_:method[@name="set_integer_list"]//_:parameter[@name="list"]/_:array/@c:type'
>  -v "gint*" \
> -u 
> '//_:record[@name="KeyFile"]/_:method[@name="set_locale_string_list"]//_:parameter[@name="list"]/_:array/@c:type'
>  -v "const gchar* const*" \
> -u 
> '//_:record[@name="KeyFile"]/_:method[@name="set_string_list"]//_:parameter[@name="list"]/_:array/@c:type'
>  -v "const gchar* const*" \
> GLib-2.0.gir
> xmlstarlet ed -L \
> -d '///_:method[@c:identifier="atk_plug_set_child"]' \
> Atk-1.0.gir
> xmlstarlet ed -L \
> -u 
> '//_:class[@name="Object"]/_:method[@name="getv"]//_:parameter[@name="names"]/_:array/@c:type'
>  -v "const gchar**" \
> -u 
> '//_:class[@name="Object"]/_:method[@name="getv"]//_:parameter[@name="values"]/_:array/@c:type'
>  -v "GValue*" \
> -u 
> '//_:class[@name="Object"]/_:method[@name="setv"]//_:parameter[@name="names"]/_:array/@c:type'
>  -v "const gchar**" \
> -u 
> '//_:class[@name="Object"]/_:method[@name="setv"]//_:parameter[@name="values"]/_:array/@c:type'
>  -v "const GValue*" \
> -u 
> '//_:class[@name="Object"]/_:constructor[@name="new_with_properties"]//_:parameter[@name="names"]/_:array/@c:type'
>  -v "const char**" \
> -u 
> '//_:class[@name="Object"]/_:constructor[@name="new_with_properties"]//_:parameter[@name="values"]/_:array/@c:type'
>  -v "const GValue*" \
> -i '//_:interface[@name="TypePlugin" and not(@glib:type-struct)]' -t 'attr' 
> -n 'glib:type-struct' -v 'TypePluginClass' \
> -i '//_:record[@name="TypePluginClass" and not(@glib:is-gtype-struct-for)]' 
> -t 'attr' -n 'glib:is-gtype-struct-for' -v 'TypePlugin' \
> GObject-2.0.gir
> sed -i 
> 's/girs_directories\s=\s\[\"\.\.\/gir-files\"\]/girs_directories=\[\".\"\]/' 
> /<>/Gir.toml
> gir -o .
> thread 'main' panicked at 'Incomplete library, unresolved: ["GLib.time_t"]', 
> src/library_postprocessing.rs:69:9
> note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
> make[1]: *** [debian/rules:16: execute_before_dh_auto_build] Error 101


The full build log is available from:
http://qa-logs.debian.net/2024/03/19/rust-atk_0.18.0-3_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240319;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240319=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.
--- End Message ---
--- Begin Message ---
Source: gir-rust-code-generator
Source-Version: 0.18.3-2
Done: Jeremy Bícha 

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

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

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1067...@bugs.debian.org,

Bug#1064096: marked as done (gir-rust-code-generator FTBFS with librust-toml-dev 0.8)

[Debian Bug Tracking System]

Your message dated Thu, 04 Apr 2024 00:22:17 +
with message-id 
and subject line Bug#1064096: fixed in gir-rust-code-generator 0.18.3-2
has caused the Debian Bug report #1064096,
regarding gir-rust-code-generator FTBFS with librust-toml-dev 0.8
to be marked as done.

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

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


-- 
1064096: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064096
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gir-rust-code-generator
Version: 0.18.3-1
Severity: serious
Tags: ftbfs
Control: close -1 0.19.0-1

https://buildd.debian.org/status/fetch.php?pkg=gir-rust-code-generator=sparc64=0.18.3-1=1708096231=0
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/gir-rust-code-generator.html

...
   dh_auto_test -a -O--buildsystem=cargo
debian cargo wrapper: options, profiles, parallel, lto: ['parallel=16'] [] 
['-j16'] 0
debian cargo wrapper: rust_type, gnu_type: sparc64-unknown-linux-gnu, 
sparc64-linux-gnu
debian cargo wrapper: running subprocess (['env', 'RUST_BACKTRACE=1', 
'/usr/bin/cargo', '-Zavoid-dev-deps', 'build', '--verbose', '--verbose', 
'-j16', '--target', 'sparc64-unknown-linux-gnu'],) {}
error: failed to select a version for the requirement `toml = "^0.7"`
candidate versions found which didn't match: 0.8.8
...
make: *** [debian/rules:16: binary-arch] Error 25
--- End Message ---
--- Begin Message ---
Source: gir-rust-code-generator
Source-Version: 0.18.3-2
Done: Jeremy Bícha 

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

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

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

Debian distribution maintenance software
pp.
Jeremy Bícha  (supplier of updated gir-rust-code-generator 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 03 Apr 2024 19:49:38 -0400
Source: gir-rust-code-generator
Built-For-Profiles: noudeb
Architecture: source
Version: 0.18.3-2
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Jeremy Bícha 
Closes: 1064096 1064766 1067256
Changes:
 gir-rust-code-generator (0.18.3-2) unstable; urgency=medium
 .
   * Update dependencies (Closes: #1064766, #1064096)
   * Cherry-pick patch to fix Rust GNOME builds with latest
 gobject-introspection time_t changes (Closes: #1067256)
Checksums-Sha1:
 47d839b5b34e05e9550d6677551221f990d5a744 2467 
gir-rust-code-generator_0.18.3-2.dsc
 87d44e4f312955be60b95d1b7ad5b34d97f1013e 8716 
gir-rust-code-generator_0.18.3-2.debian.tar.xz
 6387bddf9fcd69d143aa4c50a6495b128f831719 9170 
gir-rust-code-generator_0.18.3-2_source.buildinfo
Checksums-Sha256:
 11f77c40865720ef2efbe7daefbf96ee3b642bb794155a20f79574800498ad2e 2467 
gir-rust-code-generator_0.18.3-2.dsc
 497116ba1beed444022c21450353e3746780a9d03f93fe26d6dcdccaf5c3403f 8716 
gir-rust-code-generator_0.18.3-2.debian.tar.xz
 77e15dc0dc6fa963b019afe7b3b4fb92f3adfa26c943a7d2bebab89713c28440 9170 
gir-rust-code-generator_0.18.3-2_source.buildinfo
Files:
 24328d4df63c339f2a3f27997e2634f7 2467 gnome optional 
gir-rust-code-generator_0.18.3-2.dsc
 670a5abe5c73ddd7e79011ab1a9b1c31 8716 gnome optional 
gir-rust-code-generator_0.18.3-2.debian.tar.xz
 11263863a491f9e4a8dc328a0245bf6d 9170 gnome optional 
gir-rust-code-generator_0.18.3-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEETQvhLw5HdtiqzpaW5mx3Wuv+bH0FAmYN7tYACgkQ5mx3Wuv+
bH3eExAApyyJFeERX1fFUO1KnvP/jMeMreYJtsLS8P/CVo+MXO8UspCGz3Q3mKPg
3yYNTeU+d4kOE1qRb1SscHjzudhxVj9jaLW6nUmyF7cWIoQENvBFyItcWV9VkvO1
Hkg2uiHAEErkmxxmy+ACR5hh9SY3KA1BPez0NCl0+TZ3HUaIYGPBwW1omgeU/uEr
jaPtoSD6x0Y8A+p93UVX+ppZ6russMw0rC5rM/9jz63TMqewTVKwFbTuQEMnMTpL
uejY4imky/v8UxWDRGtTW1p0fcT6ToccLsMl0kiWtaj82LkUhSLy5Mc5L9Nk18ZL
qpFRFYaCx9hp7i23EdEYyDqK6Ay0UNMyICGyq6EYeE5Mj12DxfYcXJ8IB4w2ftZo
Quh4JIHyBLaMQVbi+kwdapJU8/Nm7gZZ9jFFaDjtxF48TexEF9j1rbpPeVBzrvjC
/hK+dskz99SAp+CCptj0QvkvmoQtDNeJdl4mDfrRNlH1hFTVdFNswZjWtqX9Qr5M
PcfKetVxaT1lyvwmNy+SCGyCinxvD25SQg4qQnIpDfM8mdrMKVnQ6MMjOeS9TvnU
O1/TWdUX2+YAEJf9qqnHu30W1vm2lWRGCimGiirwO+9+HKf8TKDDAeEWNWd2f3LU
GltLFrLsSISrqKF6MuB07OlPrO3phNEvUCf12Pto3OjZurjn/z4=
=lXGc
-END PGP SIGNATURE-

Bug#1067256: marked as done (gir-rust-code-generator: update for time_t changes)

[Debian Bug Tracking System]

Your message dated Thu, 04 Apr 2024 00:22:17 +
with message-id 
and subject line Bug#1067256: fixed in gir-rust-code-generator 0.18.3-2
has caused the Debian Bug report #1067256,
regarding gir-rust-code-generator: update for time_t changes
to be marked as done.

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

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


-- 
1067256: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067256
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rust-atk-sys
Version: 0.18.0-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240319 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> cp /usr/share/gir-1.0/GLib-2.0.gir /<>
> cp /usr/share/gir-1.0/GObject-2.0.gir /<>
> cp /usr/share/gir-1.0/Atk-1.0.gir /<>
> xmlstarlet ed -L \
> -u 
> '//*[@glib:error-domain="g-option-context-error-quark"]/@glib:error-domain' 
> -v g-option-error-quark \
> -u 
> '//_:record[@name="KeyFile"]/_:method[@name="set_boolean_list"]//_:parameter[@name="list"]/_:array/@c:type'
>  -v "gboolean*" \
> -u 
> '//_:record[@name="KeyFile"]/_:method[@name="set_double_list"]//_:parameter[@name="list"]/_:array/@c:type'
>  -v "gdouble*" \
> -u 
> '//_:record[@name="KeyFile"]/_:method[@name="set_integer_list"]//_:parameter[@name="list"]/_:array/@c:type'
>  -v "gint*" \
> -u 
> '//_:record[@name="KeyFile"]/_:method[@name="set_locale_string_list"]//_:parameter[@name="list"]/_:array/@c:type'
>  -v "const gchar* const*" \
> -u 
> '//_:record[@name="KeyFile"]/_:method[@name="set_string_list"]//_:parameter[@name="list"]/_:array/@c:type'
>  -v "const gchar* const*" \
> GLib-2.0.gir
> xmlstarlet ed -L \
> -d '///_:method[@c:identifier="atk_plug_set_child"]' \
> Atk-1.0.gir
> xmlstarlet ed -L \
> -u 
> '//_:class[@name="Object"]/_:method[@name="getv"]//_:parameter[@name="names"]/_:array/@c:type'
>  -v "const gchar**" \
> -u 
> '//_:class[@name="Object"]/_:method[@name="getv"]//_:parameter[@name="values"]/_:array/@c:type'
>  -v "GValue*" \
> -u 
> '//_:class[@name="Object"]/_:method[@name="setv"]//_:parameter[@name="names"]/_:array/@c:type'
>  -v "const gchar**" \
> -u 
> '//_:class[@name="Object"]/_:method[@name="setv"]//_:parameter[@name="values"]/_:array/@c:type'
>  -v "const GValue*" \
> -u 
> '//_:class[@name="Object"]/_:constructor[@name="new_with_properties"]//_:parameter[@name="names"]/_:array/@c:type'
>  -v "const char**" \
> -u 
> '//_:class[@name="Object"]/_:constructor[@name="new_with_properties"]//_:parameter[@name="values"]/_:array/@c:type'
>  -v "const GValue*" \
> -i '//_:interface[@name="TypePlugin" and not(@glib:type-struct)]' -t 'attr' 
> -n 'glib:type-struct' -v 'TypePluginClass' \
> -i '//_:record[@name="TypePluginClass" and not(@glib:is-gtype-struct-for)]' 
> -t 'attr' -n 'glib:is-gtype-struct-for' -v 'TypePlugin' \
> GObject-2.0.gir
> sed -i 
> 's/girs_directories\s=\s\[\"\.\.\/\.\.\/gir-files\"\]/girs_directories=\[\".\"\]/'
>  /<>/Gir.toml
> gir -o .
> thread 'main' panicked at 'Incomplete library, unresolved: ["GLib.time_t"]', 
> src/library_postprocessing.rs:69:9
> note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
> make[1]: *** [debian/rules:16: execute_before_dh_auto_build] Error 101


The full build log is available from:
http://qa-logs.debian.net/2024/03/19/rust-atk-sys_0.18.0-2_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240319;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240319=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.
--- End Message ---
--- Begin Message ---
Source: gir-rust-code-generator
Source-Version: 0.18.3-2
Done: Jeremy Bícha 

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

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

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 

Bug#1064766: marked as done (gir-rust-code-generator: FTBFS: failed to select a version for the requirement `toml = "^0.7"`; candidate versions found which didn't match: 0.8.8)

[Debian Bug Tracking System]

Your message dated Thu, 04 Apr 2024 00:22:17 +
with message-id 
and subject line Bug#1064766: fixed in gir-rust-code-generator 0.18.3-2
has caused the Debian Bug report #1064766,
regarding gir-rust-code-generator: FTBFS: failed to select a version for the 
requirement `toml = "^0.7"`; candidate versions found which didn't match: 0.8.8
to be marked as done.

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

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


-- 
1064766: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064766
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gir-rust-code-generator
Version: 0.18.3-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240224 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> /usr/share/cargo/bin/cargo prepare-debian debian/cargo_registry 
> --link-from-system
> debian cargo wrapper: options, profiles, parallel, lto: ['parallel=8'] [] 
> ['-j8'] 0
> debian cargo wrapper: rust_type, gnu_type: x86_64-unknown-linux-gnu, 
> x86_64-linux-gnu
> debian cargo wrapper: linking /usr/share/cargo/registry/* into 
> /<>/debian/cargo_registry/
> rm -f Cargo.lock
> touch debian/cargo-checksum.json
> dh_auto_configure
> debian cargo wrapper: options, profiles, parallel, lto: ['parallel=8'] [] 
> ['-j8'] 0
> debian cargo wrapper: rust_type, gnu_type: x86_64-unknown-linux-gnu, 
> x86_64-linux-gnu
> debian cargo wrapper: linking /usr/share/cargo/registry/* into 
> /<>/debian/cargo_registry/
> make[1]: Leaving directory '/<>'
>dh_auto_build -O--buildsystem=cargo
>dh_auto_test -O--buildsystem=cargo
> debian cargo wrapper: options, profiles, parallel, lto: ['parallel=8'] [] 
> ['-j8'] 0
> debian cargo wrapper: rust_type, gnu_type: x86_64-unknown-linux-gnu, 
> x86_64-linux-gnu
> debian cargo wrapper: running subprocess (['env', 'RUST_BACKTRACE=1', 
> '/usr/bin/cargo', '-Zavoid-dev-deps', 'build', '--verbose', '--verbose', 
> '-j8', '--target', 'x86_64-unknown-linux-gnu'],) {}
> error: failed to select a version for the requirement `toml = "^0.7"`
> candidate versions found which didn't match: 0.8.8
> location searched: directory source `/<>/debian/cargo_registry` 
> (which is replacing registry `crates-io`)
> required by package `gir v0.0.1 (/<>)`
> 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/02/24/gir-rust-code-generator_0.18.3-1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240224;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240224=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.
--- End Message ---
--- Begin Message ---
Source: gir-rust-code-generator
Source-Version: 0.18.3-2
Done: Jeremy Bícha 

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

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

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

Debian distribution maintenance software
pp.
Jeremy Bícha  (supplier of updated gir-rust-code-generator 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 03 Apr 2024 19:49:38 -0400
Source: gir-rust-code-generator
Built-For-Profiles: noudeb
Architecture: source
Version: 0.18.3-2
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Jeremy Bícha 
Closes: 1064096 1064766 1067256
Changes:
 gir-rust-code-generator (0.18.3-2) unstable; urgency=medium
 .
   * Update 

Processed: reassign Rust GNOME ftbfs to gir-rust-code-generator

[Debian Bug Tracking System]

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

> reassign 1067256 src:gir-rust-code-generator
Bug #1067256 [src:rust-atk-sys] rust-atk-sys: FTBFS: make[1]: *** 
[debian/rules:16: execute_before_dh_auto_build] Error 101
Bug reassigned from package 'src:rust-atk-sys' to 'src:gir-rust-code-generator'.
No longer marked as found in versions rust-atk-sys/0.18.0-2.
Ignoring request to alter fixed versions of bug #1067256 to the same values 
previously set
> reassign 1067261 src:gir-rust-code-generator
Bug #1067261 [src:rust-atk] rust-atk: FTBFS: make[1]: *** [debian/rules:16: 
execute_before_dh_auto_build] Error 101
Bug reassigned from package 'src:rust-atk' to 'src:gir-rust-code-generator'.
No longer marked as found in versions rust-atk/0.18.0-3.
Ignoring request to alter fixed versions of bug #1067261 to the same values 
previously set
> reassign 1067365 src:gir-rust-code-generator
Bug #1067365 [src:rust-gdk-sys] rust-gdk-sys: FTBFS: make[1]: *** 
[debian/rules:28: execute_before_dh_auto_build] Error 101
Bug reassigned from package 'src:rust-gdk-sys' to 'src:gir-rust-code-generator'.
No longer marked as found in versions rust-gdk-sys/0.18.0-2.
Ignoring request to alter fixed versions of bug #1067365 to the same values 
previously set
> reassign 1067336 src:gir-rust-code-generator
Bug #1067336 [src:rust-gdk] rust-gdk: FTBFS: make[1]: *** [debian/rules:28: 
execute_before_dh_auto_build] Error 101
Bug reassigned from package 'src:rust-gdk' to 'src:gir-rust-code-generator'.
No longer marked as found in versions rust-gdk/0.18.0-3.
Ignoring request to alter fixed versions of bug #1067336 to the same values 
previously set
> reassign 1067314 src:gir-rust-code-generator
Bug #1067314 [src:rust-gdkx11-sys] rust-gdkx11-sys: FTBFS: make[1]: *** 
[debian/rules:29: execute_before_dh_auto_build] Error 101
Bug reassigned from package 'src:rust-gdkx11-sys' to 
'src:gir-rust-code-generator'.
No longer marked as found in versions rust-gdkx11-sys/0.18.0-2.
Ignoring request to alter fixed versions of bug #1067314 to the same values 
previously set
> reassign 1067307 src:gir-rust-code-generator
Bug #1067307 [src:rust-gdkx11] rust-gdkx11: FTBFS: make[1]: *** 
[debian/rules:29: execute_before_dh_auto_build] Error 101
Bug reassigned from package 'src:rust-gdkx11' to 'src:gir-rust-code-generator'.
No longer marked as found in versions rust-gdkx11/0.18.0-3.
Ignoring request to alter fixed versions of bug #1067307 to the same values 
previously set
> reassign 1067373 src:gir-rust-code-generator
Bug #1067373 [src:rust-glib-sys] rust-glib-sys: FTBFS: make[1]: *** 
[debian/rules:12: execute_before_dh_auto_build] Error 101
Bug reassigned from package 'src:rust-glib-sys' to 
'src:gir-rust-code-generator'.
No longer marked as found in versions rust-glib-sys/0.18.1-2.
Ignoring request to alter fixed versions of bug #1067373 to the same values 
previously set
> reassign 1067302 src:gir-rust-code-generator
Bug #1067302 [src:rust-gobject-sys] rust-gobject-sys: FTBFS: make[1]: *** 
[debian/rules:13: execute_before_dh_auto_build] Error 101
Bug reassigned from package 'src:rust-gobject-sys' to 
'src:gir-rust-code-generator'.
No longer marked as found in versions rust-gobject-sys/0.18.0-2.
Ignoring request to alter fixed versions of bug #1067302 to the same values 
previously set
> reassign 1067322 src:gir-rust-code-generator
Bug #1067322 [src:rust-gtk-layer-shell-sys] rust-gtk-layer-shell-sys: FTBFS: 
make[1]: *** [debian/rules:32: execute_before_dh_auto_build] Error 101
Bug reassigned from package 'src:rust-gtk-layer-shell-sys' to 
'src:gir-rust-code-generator'.
No longer marked as found in versions rust-gtk-layer-shell-sys/0.7.0-1.
Ignoring request to alter fixed versions of bug #1067322 to the same values 
previously set
> reassign 1067343 src:gir-rust-code-generator
Bug #1067343 [src:rust-gtk-sys] rust-gtk-sys: FTBFS: make[1]: *** 
[debian/rules:33: execute_before_dh_auto_build] Error 101
Bug reassigned from package 'src:rust-gtk-sys' to 'src:gir-rust-code-generator'.
No longer marked as found in versions rust-gtk-sys/0.18.0-2.
Ignoring request to alter fixed versions of bug #1067343 to the same values 
previously set
> reassign 1067328 src:gir-rust-code-generator
Bug #1067328 [src:rust-gtk] rust-gtk: FTBFS: make[1]: *** [debian/rules:33: 
execute_before_dh_auto_build] Error 101
Bug reassigned from package 'src:rust-gtk' to 'src:gir-rust-code-generator'.
No longer marked as found in versions rust-gtk/0.18.1-4.
Ignoring request to alter fixed versions of bug #1067328 to the same values 
previously set
> reassign 1067279 src:gir-rust-code-generator
Bug #1067279 [src:rust-gdk-pixbuf-sys] rust-gdk-pixbuf-sys: FTBFS: make[1]: *** 
[debian/rules:18: execute_before_dh_auto_build] Error 101
Bug reassigned from package 'src:rust-gdk-pixbuf-sys' to 
'src:gir-rust-code-generator'.
No longer marked as found in versions rust-gdk-pixbuf-sys/0.18.0-4.
Ignoring request to alter fixed versions of bug #1067279 to the same values 
previously set
> reassign 

Processed: your mail

[Debian Bug Tracking System]

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

> severity 1050429 important
Bug #1050429 [musl-tools] musl: unusable on mipsel, mips64el: 
mipsel-linux-gnu-gcc: unrecognised command-line option '-EL'
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.

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

Bug#1068329: seems xz-utils 5.6.0 and 5.6.1 deb files has the backdoor, please remove both

[Martin Zobel-Helas]

Hi ZenWorker,Am 03.04.2024 um 15:51 schrieb ZenWalker :Package: snapshot.debian.orgSeverity: graveDebian is tracking issues related to the xz backdoor additionally at https://salsa.debian.org/ftp-team/xz-2024-incident/. I made Bastian aware of your perfect catch and this is now also https://salsa.debian.org/ftp-team/xz-2024-incident/-/issues/13.Thank you for your help!Martin

Bug#1068203: spectrwm: hard-coded dependency on pre-t64 library

[Sebastian Ramacher]

On 2024-04-03 23:46:43 +0200, Andrea Bolognani wrote:
> On Tue, Apr 02, 2024 at 12:02:53AM +0200, Sebastian Ramacher wrote:
> > On 2024-04-01 23:39:37 +0200, Andrea Bolognani wrote:
> > > The problem with it, and the reason why a manual dependency is used
> > > in that case, is that ${shlib:Depends} will not pick it up, since
> > > it's dlopen()ed rather than linked against.
> > > 
> > > Do you have any suggestions on how to handle this in a way that plays
> > > well with the 64-bit time_t transition?
> > 
> > You could derive it from the the dependencies of libxt-dev during the
> > build or for the time being simply change the dependency based on the
> > rename of the libxt6 -- provided that spectrwm is compatible with the
> > new ABI.
> 
> I just created [1] which should take care of the issue. It would be
> nice if you could take a look.

I have no idea what spectrwm is doing, so I am probably not the best one
to ask. From the time_t transition perspective, it is an improvement.

> To be honest, I haven't followed the 64-bit time_t transition very
> closely. Do I understand correctly that the SONAME has been changed
> without renaming the files on disk at the same time? That feels kinda
> weird, but I guess it has the nice side-effect of not breaking [2],
> so that's good :)
> 
> I also see that libxt6t64 Provides: libxt6, so I'm not sure why the
> dependency on the old name would be a problem? Wasn't that introduced
> specifically to take care of this sort of things?

The libxt6 Provides is only available on architectures where the ABI did
not change. On armhf and armel, the Provides is not present and so the
dependency is not satisfiable.

Cheers
-- 
Sebastian Ramacher

Processed: pygame: diff for NMU version 2.5.2-1.2

[Debian Bug Tracking System]

Processing control commands:

> tags 1064708 + patch
Bug #1064708 [src:pygame] pygame: FTBFS: AssertionError: "No video mode" does 
not match "Parameter 'surface' is invalid"
Ignoring request to alter tags of bug #1064708 to the same tags previously set
> tags 1064708 + pending
Bug #1064708 [src:pygame] pygame: FTBFS: AssertionError: "No video mode" does 
not match "Parameter 'surface' is invalid"
Added tag(s) pending.

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

Bug#1064708: pygame: diff for NMU version 2.5.2-1.2

[Gianfranco Costamagna]

Control: tags 1064708 + patch
Control: tags 1064708 + pending

Dear maintainer,

I've prepared an NMU for pygame (versioned as 2.5.2-1.2) and
uploaded it.

Regards.

diff -Nru pygame-2.5.2/debian/changelog pygame-2.5.2/debian/changelog
--- pygame-2.5.2/debian/changelog   2024-01-10 06:32:39.0 +0100
+++ pygame-2.5.2/debian/changelog   2024-04-04 00:36:09.0 +0200
@@ -1,3 +1,13 @@
+pygame (2.5.2-1.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+
+  [ Matthias Klose ]
+  * Skip surface tests that fail when SDL_VIDEODRIVER=dummy #4169.
+(Closes: #1064708)
+
+ -- Gianfranco Costamagna   Thu, 04 Apr 2024 
00:36:09 +0200
+
 pygame (2.5.2-1.1) unstable; urgency=medium

   * Non-maintainer upload.
diff -Nru pygame-2.5.2/debian/patches/4169.diff 
pygame-2.5.2/debian/patches/4169.diff
--- pygame-2.5.2/debian/patches/4169.diff   1970-01-01 01:00:00.0 
+0100
+++ pygame-2.5.2/debian/patches/4169.diff   2024-03-19 11:05:54.0 
+0100
@@ -0,0 +1,44 @@
+diff --git a/test/surface_test.py b/test/surface_test.py
+index e6dc1ad095..b1147d278f 100644
+--- a/test/surface_test.py
 b/test/surface_test.py
+@@ -1091,6 +1091,10 @@ def test_image_convert_bug_131(self):
+ finally:
+ pygame.display.quit()
+
++@unittest.skipIf(
++os.environ.get("SDL_VIDEODRIVER") == "dummy",
++'requires a non-"dummy" SDL_VIDEODRIVER',
++)
+ def test_convert_init(self):
+ """Ensure initialization exceptions are raised
+ for surf.convert()."""
+@@ -1101,12 +1105,11 @@ def test_convert_init(self):
+
+ pygame.display.init()
+ try:
+-if os.environ.get("SDL_VIDEODRIVER") != "dummy":
+-try:
+-surf.convert(32)
+-surf.convert(pygame.Surface((1, 1)))
+-except pygame.error:
+-self.fail("convert() should not raise an exception here.")
++try:
++surf.convert(32)
++surf.convert(pygame.Surface((1, 1)))
++except pygame.error:
++self.fail("convert() should not raise an exception here.")
+
+ self.assertRaisesRegex(pygame.error, "No video mode", 
surf.convert)
+
+@@ -1118,6 +1121,10 @@ def test_convert_init(self):
+ finally:
+ pygame.display.quit()
+
++@unittest.skipIf(
++os.environ.get("SDL_VIDEODRIVER") == "dummy",
++'requires a non-"dummy" SDL_VIDEODRIVER',
++)
+ def test_convert_alpha_init(self):
+ """Ensure initialization exceptions are raised
+ for surf.convert_alpha()."""
diff -Nru pygame-2.5.2/debian/patches/series pygame-2.5.2/debian/patches/series
--- pygame-2.5.2/debian/patches/series  2024-01-10 06:32:39.0 +0100
+++ pygame-2.5.2/debian/patches/series  2024-04-04 00:34:56.0 +0200
@@ -3,3 +3,4 @@
 s390x-time-test.patch
 4048.diff
 ignore-test-machinery-issue.diff
+4169.diff


OpenPGP_signature.asc
Description: OpenPGP digital signature

Processed: nbsphinx/nbconvert broken by lxml 5.2: lxml.html.clean

[Debian Bug Tracking System]

Processing control commands:

> affects -1 src:pandas
Bug #1068349 [python3-nbconvert,python3-lxml] nbsphinx/nbconvert broken by lxml 
5.2: lxml.html.clean
Added indication that 1068349 affects src:pandas
> affects -1 python3-nbsphinx
Bug #1068349 [python3-nbconvert,python3-lxml] nbsphinx/nbconvert broken by lxml 
5.2: lxml.html.clean
Added indication that 1068349 affects python3-nbsphinx
> block 1068104 by -1
Bug #1068104 [src:pandas] pandas: FTBFS on 32-bit architectures with 
-D_TIME_BITS=64
1068104 was not blocked by any bugs.
1068104 was not blocking any bugs.
Added blocking bug(s) of 1068104: 1068349

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

Bug#1066291: Additional information

[Vladimir Petko]

Dear Maintainers,

  Would it be possible to consider a merge request[1] that addresses this issue?

Best Regards,
 Vladimir.

 [1] https://salsa.debian.org/debian/gimp-plugin-registry/-/merge_requests/2

Bug#1061001: python3.12 at fault?

[Bdale Garbee]

This appears to be another manifestation of the incompatibility with
python3.12 reported in #1059647.  I'm not going to mark it as a
duplicate in the BTS since the process of getting there is so different,
but I believe the fix will be the same.  Upstream has reworked the build
process to allow use of python3.12 and a new upstream release is
expected as soon as a test suite issue is resolved.

Bdale


signature.asc
Description: PGP signature

Bug#1066219: marked as done (golang-github-linuxkit-virtsock: FTBFS: src/github.com/linuxkit/virtsock/pkg/hvsock/hvsock_linux.go:33:12: error: implicit declaration of function ‘accept4’; did you mean

[Debian Bug Tracking System]

Your message dated Wed, 03 Apr 2024 22:06:52 +
with message-id 
and subject line Bug#976564: fixed in golang-github-linuxkit-virtsock 
0.0~git20220523.1a23e78+ds-1
has caused the Debian Bug report #976564,
regarding golang-github-linuxkit-virtsock: FTBFS: 
src/github.com/linuxkit/virtsock/pkg/hvsock/hvsock_linux.go:33:12: error: 
implicit declaration of function ‘accept4’; did you mean ‘accept’? 
[-Werror=implicit-function-declaration]
to be marked as done.

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

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


-- 
976564: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976564
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: golang-github-linuxkit-virtsock
Version: 0.0~git20170720.0.0416e3d-1.1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240313 ftbfs-trixie ftbfs-impfuncdef

Hi,

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

This is most likely caused by a change in dpkg 1.22.6, that enabled
-Werror=implicit-function-declaration. For more information, see
https://wiki.debian.org/qa.debian.org/FTBFS#A2024-03-13_-Werror.3Dimplicit-function-declaration

Relevant part (hopefully):
>  debian/rules build
> dh build --buildsystem=golang --with=golang
>dh_update_autotools_config -O--buildsystem=golang
>dh_autoreconf -O--buildsystem=golang
>dh_auto_configure -O--buildsystem=golang
>dh_auto_build -O--buildsystem=golang
>   cd obj-x86_64-linux-gnu && go install -trimpath -v -p 8 
> github.com/linuxkit/virtsock/cmd/sock_stress 
> github.com/linuxkit/virtsock/cmd/vsudd 
> github.com/linuxkit/virtsock/pkg/hvsock github.com/linuxkit/virtsock/pkg/vsock
> internal/coverage/rtcov
> internal/goos
> internal/godebugs
> internal/unsafeheader
> internal/goexperiment
> internal/goarch
> internal/cpu
> runtime/internal/atomic
> runtime/internal/syscall
> internal/race
> internal/chacha8rand
> internal/abi
> runtime/internal/math
> runtime/internal/sys
> sync/atomic
> math/bits
> unicode/utf8
> internal/itoa
> unicode
> encoding
> internal/bytealg
> cmp
> internal/nettrace
> log/internal
> slices
> math
> runtime
> internal/reflectlite
> sync
> internal/testlog
> internal/singleflight
> internal/bisect
> runtime/cgo
> internal/godebug
> errors
> sort
> internal/oserror
> internal/safefilepath
> io
> strconv
> path
> syscall
> vendor/golang.org/x/net/dns/dnsmessage
> internal/intern
> math/rand
> hash
> strings
> bytes
> reflect
> net/netip
> crypto
> internal/syscall/execenv
> internal/syscall/unix
> time
> internal/fmtsort
> encoding/binary
> context
> io/fs
> internal/poll
> crypto/md5
> golang.org/x/sys/unix
> os
> path/filepath
> fmt
> net
> log
> flag
> net/url
> github.com/linuxkit/virtsock/pkg/vsock
> log/syslog
> github.com/linuxkit/virtsock/pkg/hvsock
> # github.com/linuxkit/virtsock/pkg/hvsock
> src/github.com/linuxkit/virtsock/pkg/hvsock/hvsock_linux.go: In function 
> ‘accept_hv’:
> src/github.com/linuxkit/virtsock/pkg/hvsock/hvsock_linux.go:33:12: error: 
> implicit declaration of function ‘accept4’; did you mean ‘accept’? 
> [-Werror=implicit-function-declaration]
>33 | return accept4(fd, (struct sockaddr *)sa_hv, sa_hv_len, 0);
>   |^~~
>   |accept
> cc1: some warnings being treated as errors
> dh_auto_build: error: cd obj-x86_64-linux-gnu && go install -trimpath -v -p 8 
> github.com/linuxkit/virtsock/cmd/sock_stress 
> github.com/linuxkit/virtsock/cmd/vsudd 
> github.com/linuxkit/virtsock/pkg/hvsock 
> github.com/linuxkit/virtsock/pkg/vsock returned exit code 1
> make: *** [debian/rules:4: build] Error 25


The full build log is available from:
http://qa-logs.debian.net/2024/03/13/golang-github-linuxkit-virtsock_0.0~git20170720.0.0416e3d-1.1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240313;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240313=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.
--- End Message ---
--- Begin Message ---
Source: golang-github-linuxkit-virtsock
Source-Version: 

Bug#976564: marked as done (golang-github-linuxkit-virtsock: FTBFS: dh_auto_build: error: cd obj-aarch64-linux-gnu && go install -trimpath -v -p 4 github.com/linuxkit/virtsock/cmd/sock_stress github.c

[Debian Bug Tracking System]

Your message dated Wed, 03 Apr 2024 22:06:52 +
with message-id 
and subject line Bug#976564: fixed in golang-github-linuxkit-virtsock 
0.0~git20220523.1a23e78+ds-1
has caused the Debian Bug report #976564,
regarding golang-github-linuxkit-virtsock: FTBFS: dh_auto_build: error: cd 
obj-aarch64-linux-gnu && go install -trimpath -v -p 4 
github.com/linuxkit/virtsock/cmd/sock_stress 
github.com/linuxkit/virtsock/cmd/vsudd github.com/linuxkit/virtsock/pkg/hvsock 
github.com/linuxkit/virtsock/pkg/vsock returned exit code 2
to be marked as done.

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

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


-- 
976564: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976564
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: golang-github-linuxkit-virtsock
Version: 0.0~git20170720.0.0416e3d-1
Severity: serious
Justification: FTBFS on arm64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201205 ftbfs-bullseye

Hi,

During a rebuild of all packages in sid, your package failed to build
on arm64 (I don't know if it also fails on amd64).

Relevant part (hopefully):
>  debian/rules build
> dh build --buildsystem=golang --with=golang
>dh_update_autotools_config -O--buildsystem=golang
>dh_autoreconf -O--buildsystem=golang
>dh_auto_configure -O--buildsystem=golang
>dh_auto_build -O--buildsystem=golang
>   cd obj-aarch64-linux-gnu && go install -trimpath -v -p 4 
> github.com/linuxkit/virtsock/cmd/sock_stress 
> github.com/linuxkit/virtsock/cmd/vsudd 
> github.com/linuxkit/virtsock/pkg/hvsock github.com/linuxkit/virtsock/pkg/vsock
> internal/unsafeheader
> runtime/internal/sys
> internal/cpu
> runtime/internal/atomic
> internal/race
> runtime/internal/math
> sync/atomic
> math/bits
> internal/bytealg
> unicode/utf8
> unicode
> internal/testlog
> math
> golang.org/x/sys/internal/unsafeheader
> runtime
> internal/nettrace
> runtime/cgo
> internal/reflectlite
> sync
> internal/singleflight
> math/rand
> errors
> sort
> io
> internal/oserror
> strconv
> syscall
> vendor/golang.org/x/net/dns/dnsmessage
> hash
> strings
> crypto
> reflect
> bytes
> internal/syscall/unix
> time
> internal/syscall/execenv
> context
> internal/poll
> internal/fmtsort
> encoding/binary
> os
> crypto/md5
> golang.org/x/sys/unix
> fmt
> net
> path/filepath
> flag
> log
> net/url
> github.com/linuxkit/virtsock/pkg/vsock
> log/syslog
> github.com/linuxkit/virtsock/pkg/hvsock
> # github.com/linuxkit/virtsock/pkg/hvsock
> src/github.com/linuxkit/virtsock/pkg/hvsock/hvsock_linux.go: In function 
> ‘accept_hv’:
> src/github.com/linuxkit/virtsock/pkg/hvsock/hvsock_linux.go:33:12: warning: 
> implicit declaration of function ‘accept4’; did you mean ‘accept’? 
> [-Wimplicit-function-declaration]
>33 | return accept4(fd, (struct sockaddr *)sa_hv, sa_hv_len, 0);
>   |^~~
>   |accept
> github.com/linuxkit/virtsock/cmd/vsudd
> github.com/linuxkit/virtsock/cmd/sock_stress
> # github.com/linuxkit/virtsock/cmd/vsudd
> src/github.com/linuxkit/virtsock/cmd/vsudd/main.go:102:3: undefined: 
> syscall.Dup2
> src/github.com/linuxkit/virtsock/cmd/vsudd/main.go:103:3: undefined: 
> syscall.Dup2
> src/github.com/linuxkit/virtsock/cmd/vsudd/main.go:104:3: undefined: 
> syscall.Dup2
> dh_auto_build: error: cd obj-aarch64-linux-gnu && go install -trimpath -v -p 
> 4 github.com/linuxkit/virtsock/cmd/sock_stress 
> github.com/linuxkit/virtsock/cmd/vsudd 
> github.com/linuxkit/virtsock/pkg/hvsock 
> github.com/linuxkit/virtsock/pkg/vsock returned exit code 2
> make: *** [debian/rules:4: build] Error 25

The full build log is available from:
   
http://qa-logs.debian.net/2020/12/05/golang-github-linuxkit-virtsock_0.0~git20170720.0.0416e3d-1_unstable.log

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

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

If you fail to reproduce this, please provide a build log and diff it with me
so that we can identify if something relevant changed in the meantime.

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: golang-github-linuxkit-virtsock
Source-Version: 0.0~git20220523.1a23e78+ds-1
Done: Faidon Liambotis 

We believe that the bug you reported is fixed in the latest version of

Bug#1059647: fixed in upstream branch

[Bdale Garbee]

tags 1059647 +upstream
thanks

Upstream reports in https://github.com/scikit-fmm/scikit-fmm/issues/78
that this issue is fixed on a development branch, and will be merged and
released as soon as a test suite issue gets resolved.

Bdale


signature.asc
Description: PGP signature

Bug#1067308: marked as done (python-meshplex: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" --test-args=--ignore-glob=\*test_io\* returned exit code 13)

[Debian Bug Tracking System]

Your message dated Wed, 03 Apr 2024 23:44:51 +0200
with message-id 
and subject line Re: Bug#1067308 python-meshplex: FTBFS: dh_auto_test: error:
has caused the Debian Bug report #1067308,
regarding python-meshplex: FTBFS: dh_auto_test: error: pybuild --test 
--test-pytest -i python{version} -p "3.12 3.11" 
--test-args=--ignore-glob=\*test_io\* returned exit code 13
to be marked as done.

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

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


-- 
1067308: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067308
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-meshplex
Version: 0.17.1-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240319 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> MPLBACKEND=Agg  dh_auto_test -- --test-args="--ignore-glob=*test_io*"
> I: pybuild base:305: cd 
> /<>/.pybuild/cpython3_3.12_meshplex/build; python3.12 -m pytest 
> --ignore-glob=*test_io*
> = test session starts 
> ==
> platform linux -- Python 3.12.2, pytest-8.1.1, pluggy-1.4.0
> rootdir: /<>/.pybuild/cpython3_3.12_meshplex/build
> configfile: pyproject.toml
> collected 112 items
> 
> tests/mesh_tri/test_curl.py .[  
> 0%]
> tests/mesh_tri/test_edge_flip.py ..  [ 
> 13%]
> tests/mesh_tri/test_genus.py .   [ 
> 14%]
> tests/mesh_tri/test_mesh_tri.py ..   [ 
> 33%]
> tests/mesh_tri/test_plot.py ..   [ 
> 35%]
> tests/mesh_tri/test_remove_points.py .   [ 
> 36%]
> tests/test_ce_ratios.py  [ 
> 40%]
> tests/test_cell_partitions.py    [ 
> 43%]
> tests/test_circumcenters.py  [ 
> 47%]
> tests/test_compute_cell_values.py .  [ 
> 48%]
> tests/test_control_volume_centroids.py ...   [ 
> 50%]
> tests/test_control_volumes.py .  [ 
> 55%]
> tests/test_create_facets.py s... [ 
> 58%]
> tests/test_degenerate.py [ 
> 62%]
> tests/test_gh_issues.py ..   [ 
> 64%]
> tests/test_heights.py ...[ 
> 66%]
> tests/test_mesh_line.py .[ 
> 67%]
> tests/test_mesh_tetra.py .s  [ 
> 76%]
> tests/test_remove_cells.py F..   [ 
> 86%]
> tests/test_signed_area.py    [ 
> 93%]
> tests/test_subdomain.py ...  [ 
> 96%]
> tests/test_volumes.py    
> [100%]
> 
> === FAILURES 
> ===
> __ test_remove_cells_boundary 
> __
> 
> def test_remove_cells_boundary():
> mesh = get_mesh1()
> 
> assert np.all(mesh.is_boundary_point == [True, True, True, True, 
> False])
> assert np.all(mesh.is_boundary_facet_local[0] == [False, False, 
> False, False])
> assert np.all(mesh.is_boundary_facet_local[1] == [False, False, 
> False, True])
> assert np.all(mesh.is_boundary_facet_local[2] == [True, True, True, 
> False])
> assert np.all(
> mesh.is_boundary_facet == [True, True, False, True, False, True, 
> False, False]
> )
> assert np.all(mesh.is_boundary_cell)
> assert np.all(mesh.facets_cells_idx == [0, 1, 0, 2, 1, 3, 2, 3])
> # cell id:
> assert np.all(mesh.facets_cells["boundary"][1] == [0, 3, 1, 2])
> # local edge:
> assert np.all(mesh.facets_cells["boundary"][2] == [2, 1, 2, 2])
> # cell id:
> >   assert np.all(
> mesh.facets_cells["interior"][1:3].T == [[0, 3], [0, 1], [1, 2], 
> [2, 3]]
> )
> E   assert False
> E+  where False = (array([[3, 0]...   
>[2, 3]]) == [[0, 3], [0, ...1, 2], [2, 3]]
> E+where  = np.all
> E   
> E   Use -v to get 

Bug#1067010: marked as done (libsquashfuse-dev: Incompatible pointer types on 32-bit architectures)

[Debian Bug Tracking System]

Your message dated Wed, 03 Apr 2024 21:54:02 +
with message-id 
and subject line Bug#1067010: fixed in squashfuse 0.5.2-0.1
has caused the Debian Bug report #1067010,
regarding libsquashfuse-dev: Incompatible pointer types on 32-bit architectures
to be marked as done.

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

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


-- 
1067010: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067010
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libsquashfuse-dev
Version: 0.5.0-2
Severity: serious
Tags: ftbfs fixed-upstream
Affects: src:charliecloud

Dear Maintainer,

squashfuse suffers from an incompatible pointer type issue on 32-bit
architectures. Checking the latest build logs for armel, armhf and
i386 ([0], [1], [2]) one finds the following warning:

ll_main.c: In function ‘main’:
ll_main.c:164:41: warning: assignment to ‘void (*)(struct fuse_req *, 
fuse_ino_t,  uint64_t)’ {aka ‘void (*)(struct fuse_req *, long long unsigned 
int,  long long unsigned int)’} from incompatible pointer type ‘void (*)(struct 
fuse_req *, fuse_ino_t,  long unsigned int)’ {aka ‘void (*)(struct fuse_req *, 
long long unsigned int,  long unsigned int)’} [-Wincompatible-pointer-types]
  164 | sqfs_ll_ops.forget  = sqfs_ll_op_forget;
  | ^

This incompatibility leads to an FTBFS issue for the charliecloud
package on 32-bit architectures (see e. g. [3]) since it is built
using the -Werror option.

It seems that this issue was fixed in upstream release 0.5.1 [4].

More background information on this issue can be obtained from the
corresponding Charliecloud upstream issue and PR ([5], [6]).

Best regards,

Peter

[0] 
https://buildd.debian.org/status/fetch.php?pkg=squashfuse=armel=0.5.0-2%2Bb1=1707534165=0
[1] 
https://buildd.debian.org/status/fetch.php?pkg=squashfuse=armhf=0.5.0-2%2Bb1=1707538322=0
[2] 
https://buildd.debian.org/status/fetch.php?pkg=squashfuse=i386=0.5.0-2%2Bb1=1707537260=0
[3] 
https://buildd.debian.org/status/fetch.php?pkg=charliecloud=armel=0.37-2=1710594551=log
[4] 
https://github.com/vasi/squashfuse/commit/cb148fc1477ed676049b7891ebb6efc90b2c00ec
[5] https://github.com/hpc/charliecloud/issues/1858
[6] https://github.com/hpc/charliecloud/pull/1859
--- End Message ---
--- Begin Message ---
Source: squashfuse
Source-Version: 0.5.2-0.1
Done: Sebastian Ramacher 

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

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

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

Debian distribution maintenance software
pp.
Sebastian Ramacher  (supplier of updated squashfuse 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 01 Apr 2024 23:09:03 +0200
Source: squashfuse
Architecture: source
Version: 0.5.2-0.1
Distribution: unstable
Urgency: medium
Maintainer: Scarlett Moore 
Changed-By: Sebastian Ramacher 
Closes: 1067010
Changes:
 squashfuse (0.5.2-0.1) unstable; urgency=medium
 .
   * Non-maintainer upload
   * New upstream release
 - Fix pointer types on 32 bit architectures (Closes: #1067010)
Checksums-Sha1:
 8eae42bfb2b6b8758500427d40c460efc08af270 1523 squashfuse_0.5.2-0.1.dsc
 5794a0d279775b0d02744791e3e41ae29794de89 63204 squashfuse_0.5.2.orig.tar.xz
 50b0872fea3198041f066b049e0c6f61a3b4e598 5040 
squashfuse_0.5.2-0.1.debian.tar.xz
 24ef41765b42b4eace408c57691b24b429a32bae 6234 
squashfuse_0.5.2-0.1_source.buildinfo
Checksums-Sha256:
 12a85b19c61a1d0aaedf2d64985ec19a404d86acbc30b3fb66b863c26908450e 1523 
squashfuse_0.5.2-0.1.dsc
 f5c405ff9ecd32d0dbefb10b2ab932542ac6f6c1ffd2a51a33b79aa7f01c2afd 63204 
squashfuse_0.5.2.orig.tar.xz
 9a27f383c0e1d53ff4cfb84cc5f64afaaa88c54c5a1e53999f6ab335afe86654 5040 
squashfuse_0.5.2-0.1.debian.tar.xz
 e53aef58123b19c431da642ad899e9055bd097b26969de10b9d479298452867f 6234 
squashfuse_0.5.2-0.1_source.buildinfo
Files:
 ab62b54455e05cfb10682b46007ee832 1523 utils optional squashfuse_0.5.2-0.1.dsc
 29037f8b2d8f67c75c5eb3742b564909 63204 utils optional 
squashfuse_0.5.2.orig.tar.xz
 2d4368dd8d782d116f21338e01f680d8 5040 utils optional 
squashfuse_0.5.2-0.1.debian.tar.xz
 

Processed: test builds successful

[Debian Bug Tracking System]

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

> tags 1066248 +pending
Bug #1066248 [src:librnd] librnd: FTBFS: 
../src/librnd/plugins/hid_lesstif/main.c:261:25: error: implicit declaration of 
function ‘lesstif_attr_sub_update_hidlib’ 
[-Werror=implicit-function-declaration]
Added tag(s) pending.
> tags 1049315 +pending
Bug #1049315 [src:librnd] librnd: Fails to build source after successful build
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#1066248: test builds successful

[Bdale Garbee]

tags 1066248 +pending
tags 1049315 +pending
thanks

Last night I successfully completed a test build of librnd from upstream
svn trunk that resolves all open Debian bugs.  The next upstream release
is still expected on 10 April, and I plan to update the Debian librnd
package immediately after that release. 

Bdale


signature.asc
Description: PGP signature

Bug#1068203: spectrwm: hard-coded dependency on pre-t64 library

[Andrea Bolognani]

On Tue, Apr 02, 2024 at 12:02:53AM +0200, Sebastian Ramacher wrote:
> On 2024-04-01 23:39:37 +0200, Andrea Bolognani wrote:
> > The problem with it, and the reason why a manual dependency is used
> > in that case, is that ${shlib:Depends} will not pick it up, since
> > it's dlopen()ed rather than linked against.
> > 
> > Do you have any suggestions on how to handle this in a way that plays
> > well with the 64-bit time_t transition?
> 
> You could derive it from the the dependencies of libxt-dev during the
> build or for the time being simply change the dependency based on the
> rename of the libxt6 -- provided that spectrwm is compatible with the
> new ABI.

I just created [1] which should take care of the issue. It would be
nice if you could take a look.

To be honest, I haven't followed the 64-bit time_t transition very
closely. Do I understand correctly that the SONAME has been changed
without renaming the files on disk at the same time? That feels kinda
weird, but I guess it has the nice side-effect of not breaking [2],
so that's good :)

I also see that libxt6t64 Provides: libxt6, so I'm not sure why the
dependency on the old name would be a problem? Wasn't that introduced
specifically to take care of this sort of things?


[1] https://salsa.debian.org/debian/spectrwm/-/merge_requests/7
[2] 
https://salsa.debian.org/debian/spectrwm/-/blob/debian/latest/debian/patches/debian/Adapt-libswmhack.patch#L71-72
-- 
Andrea Bolognani 
Resistance is futile, you will be garbage collected.


signature.asc
Description: PGP signature

Bug#1068347: nodejs: CVE-2024-27983 CVE-2024-27982

[Moritz Mühlenhoff]

Source: nodejs
X-Debbugs-CC: t...@security.debian.org
Severity: grave
Tags: security

Hi,

The following vulnerabilities were published for nodejs.

CVE-2024-27983[0]:
https://nodejs.org/en/blog/vulnerability/april-2024-security-releases/

CVE-2024-27982[1]:
https://nodejs.org/en/blog/vulnerability/april-2024-security-releases/


If you fix the vulnerabilities please also make sure to include the
CVE (Common Vulnerabilities & Exposures) ids in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2024-27983
https://www.cve.org/CVERecord?id=CVE-2024-27983
[1] https://security-tracker.debian.org/tracker/CVE-2024-27982
https://www.cve.org/CVERecord?id=CVE-2024-27982

Please adjust the affected versions in the BTS as needed.

Bug#1066392: marked as done (gtk2-engines-murrine: FTBFS: ./src/murrine_style.c:133:30: error: implicit declaration of function ‘murrine_widget_is_ltr’; did you mean ‘murrine_widget_is_rgba’? [-Werror

[Debian Bug Tracking System]

Your message dated Wed, 03 Apr 2024 20:46:19 +
with message-id 
and subject line Bug#1066392: fixed in gtk2-engines-murrine 0.98.2-4
has caused the Debian Bug report #1066392,
regarding gtk2-engines-murrine: FTBFS: ./src/murrine_style.c:133:30: error: 
implicit declaration of function ‘murrine_widget_is_ltr’; did you mean 
‘murrine_widget_is_rgba’? [-Werror=implicit-function-declaration]
to be marked as done.

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

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


-- 
1066392: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066392
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gtk2-engines-murrine
Version: 0.98.2-3
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240313 ftbfs-trixie ftbfs-impfuncdef

Hi,

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

This is most likely caused by a change in dpkg 1.22.6, that enabled
-Werror=implicit-function-declaration. For more information, see
https://wiki.debian.org/qa.debian.org/FTBFS#A2024-03-13_-Werror.3Dimplicit-function-declaration

Relevant part (hopefully):
> /bin/bash ./libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I. 
> -I./src -I/usr/include/gtk-2.0 -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include 
> -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/harfbuzz 
> -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/libmount 
> -I/usr/include/blkid -I/usr/include/fribidi -I/usr/include/cairo 
> -I/usr/include/pixman-1 -I/usr/include/gdk-pixbuf-2.0 
> -I/usr/include/x86_64-linux-gnu -I/usr/include/webp -I/usr/include/atk-1.0 
> -pthread  -I/usr/include/pixman-1   -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 -fcf-protection -c -o murrine_draw_rgba.lo `test -f 
> './src/murrine_draw_rgba.c' || echo './'`./src/murrine_draw_rgba.c
> libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I./src -I/usr/include/gtk-2.0 
> -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include -I/usr/include/pango-1.0 
> -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include 
> -I/usr/include/harfbuzz -I/usr/include/freetype2 -I/usr/include/libpng16 
> -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/fribidi 
> -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/gdk-pixbuf-2.0 
> -I/usr/include/x86_64-linux-gnu -I/usr/include/webp -I/usr/include/atk-1.0 
> -pthread -I/usr/include/pixman-1 -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 -fcf-protection -c ./src/support.c  -fPIC -DPIC -o 
> .libs/support.o
> libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I./src -I/usr/include/gtk-2.0 
> -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include -I/usr/include/pango-1.0 
> -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include 
> -I/usr/include/harfbuzz -I/usr/include/freetype2 -I/usr/include/libpng16 
> -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/fribidi 
> -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/gdk-pixbuf-2.0 
> -I/usr/include/x86_64-linux-gnu -I/usr/include/webp -I/usr/include/atk-1.0 
> -pthread -I/usr/include/pixman-1 -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 -fcf-protection -c ./src/murrine_rc_style.c  -fPIC 
> -DPIC -o .libs/murrine_rc_style.o
> libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I./src -I/usr/include/gtk-2.0 
> -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include -I/usr/include/pango-1.0 
> -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include 
> -I/usr/include/harfbuzz -I/usr/include/freetype2 -I/usr/include/libpng16 
> -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/fribidi 
> -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/gdk-pixbuf-2.0 
> -I/usr/include/x86_64-linux-gnu -I/usr/include/webp -I/usr/include/atk-1.0 
> -pthread -I/usr/include/pixman-1 -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 -fcf-protection -c ./src/murrine_style.c  -fPIC -DPIC 
> -o .libs/murrine_style.o
> libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I./src -I/usr/include/gtk-2.0 

Bug#1065486: sbd: FTBFS due to hardcoded libaio SONAME used in dlopen()

[Ferenc Wágner]

This is already fixed in unstable,  waiting for pacemaker to migrate.

Bug#1063957: python-pytest-lazy-fixture: autopkgtest regression with pytest 8

[Jeremy Bícha]

I noticed one package affected by this issue, prettytable, has
switched to a fork, pytest-lazy-fixtures (note the s at the end of the
name).

Would someone like to package this for Debian to fix several packages
failing to build?

https://github.com/dev-petrov/pytest-lazy-fixtures

Thank you,
Jeremy Bícha

Processed: Re: Bug#1067547: Info received and FILED only (FTBFS: "vsnprintf is so broken we can't compensate. Sorry.")

[Debian Bug Tracking System]

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

> tags 1067547 + fixed-upstream
Bug #1067547 [src:wmweather+] FTBFS: "vsnprintf is so broken we can't 
compensate. Sorry."
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.

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

Processed: Re: python-pytest-lazy-fixture: autopkgtest regression with pytest 8

[Debian Bug Tracking System]

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

> affects 1063957 src:prettytable
Bug #1063957 [src:python-pytest-lazy-fixture] python-pytest-lazy-fixture: 
autopkgtest regression with pytest 8
Bug #1063973 [src:python-pytest-lazy-fixture] python-marshmallow-sqlalchemy: 
autopkgtest regression with pytest 8
Bug #1066727 [src:python-pytest-lazy-fixture] python-pytest-lazy-fixture: Needs 
update for Pytest 8 (AttributeError: 'CallSpec2' object has no attribute 
'funcargs')
Bug #1066784 [src:python-pytest-lazy-fixture] python-marshmallow-sqlalchemy: 
FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 
"3.12 3.11" returned exit code 13
Bug #1066785 [src:python-pytest-lazy-fixture] python-pytest-lazy-fixture: 
FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 
"3.12 3.11" returned exit code 13
Bug #1066789 [src:python-pytest-lazy-fixture] pycoast: FTBFS: dh_auto_test: 
error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned 
exit code 13
Added indication that 1063957 affects src:prettytable
Added indication that 1063973 affects src:prettytable
Added indication that 1066727 affects src:prettytable
Added indication that 1066784 affects src:prettytable
Added indication that 1066785 affects src:prettytable
Added indication that 1066789 affects src:prettytable
>
End of message, stopping processing here.

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

Bug#1066757: prettytable: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13

[Jeremy Bícha]

This is actually https://bugs.debian.org/1063957

prettytable has worked around this for the 3.10.0 release by switching
to a fork, python-pytest-lazy-fixtures, which is not yet packaged in
Debian.

Thank you,
Jeremy Bícha

Bug#1067562: FTBFS: missing symbols on 32-bit architectures

[Thomas Orgis]

Am Wed, 03 Apr 2024 20:46:29 +0200
schrieb Simon Chopin : 

> I just uploaded the attached debdiff to Ubuntu to both fix the FTBFS and
> start the t64 transition for this package, based on the following
> comment:

Are you able to test this for the dev snapshot of mpg123 before I do
the next release?

http://mpg123.org/snapshot/mpg123-1.32.6-dev+20240403022201.tar.bz2

This gets rid of the ambiguous symbols for this type of build (or
should, at least), leaving only those with 64 and _64 suffix (where
applicable).

This at least avoids the subtle memory-corrupting ABI mismatch. Any
binaries built with enabled large file support continue to work,
anyway. That ABI is stable.

If I get an OK that this really fires as supposed on Debian builds,
I'll release 1.32.6.


Alrighty then,

Thomas

Processed: change to actual unstable version to block migration to testing

[Debian Bug Tracking System]

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

> notfound 1017729 5.4.2-2
Bug #1017729 [cinnamon-l10n] cinnamon-l10n: Upgrading to 5.4.2-2 breaks cinnamon
No longer marked as found in versions cinnamon-translations/5.4.2-2.
> found 1017729 6.0.2-2
Bug #1017729 [cinnamon-l10n] cinnamon-l10n: Upgrading to 5.4.2-2 breaks cinnamon
Marked as found in versions cinnamon-translations/6.0.2-2.
> thanks
Stopping processing here.

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

Bug#1066255: marked as pending in asciijump

[Reiner Herrmann]

Control: tag -1 pending

Hello,

Bug #1066255 in asciijump reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/games-team/asciijump/-/commit/b6196ae4e5b323fc6377affca08432506c70649d


Fix FTBFS because of implicitely declared functions

Closes: #1066255


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1066255

Processed: Bug#1066255 marked as pending in asciijump

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1066255 [src:asciijump] asciijump: FTBFS: scrclient.c:76:19: error: 
implicit declaration of function ‘strtol’; did you mean ‘strtok’? 
[-Werror=implicit-function-declaration]
Added tag(s) pending.

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

Bug#1067547: FTBFS: "vsnprintf is so broken we can't compensate. Sorry."

[anomie]

tags 1067547 + fixed-upstream
thanks

Bug#1060407: gtkwave update for {bookworm,bullseye,buster}-security

[Moritz Muehlenhoff]

Hi Adrian,
> >...
> > > debdiffs contain only changes to debian/
> > 
> > The bookworm/bullseye debdiffs looks good, please upload to 
> > security-master, thanks!
> 
> both are now uploaded.

DSA has been released, thanks!
 
> > Note that both need -sa, but dak needs some special attention when
> > uploading to security-master. You'll need to wait for the ACCEPTED mail
> > before you can upload the next one.
> 
> Done, but I am not sure this was necessary in this case since these are 
> different upstream tarballs gtkwave_3.3.118.orig.tar.gz and 
> gtkwave_3.3.104+really3.3.118.orig.tar.gz
> 
> (The contents also differs since as mentioned one is the GTK 2+3 
>  upstream tarball and the other one is the GTK 1+2 upstream tarball.)

You're correct indeed.

Cheers,
Moritz

Processed: Re: FTBFS: missing symbols on 32-bit architectures

[Debian Bug Tracking System]

Processing control commands:

> tags -1 ftbfs patch
Bug #1067562 [src:mpg123] FTBFS: missing symbols on 32-bit architectures
Added tag(s) patch.

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

Processed: tagging 1068223

[Debian Bug Tracking System]

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

> tags 1068223 + ftbfs
Bug #1068223 [cyrus-imapd] cyrus-imapd - FTBFS on 32-bit non-i386 architectures
Added tag(s) ftbfs.
> thanks
Stopping processing here.

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

Bug#1067562: FTBFS: missing symbols on 32-bit architectures

[Simon Chopin]

Source: mpg123
Followup-For: Bug #1067562
X-Debbugs-Cc: scho...@ubuntu.com
Control: tags -1 ftbfs patch

Hi,

I just uploaded the attached debdiff to Ubuntu to both fix the FTBFS and
start the t64 transition for this package, based on the following
comment:

> the non-suffixed functions now work with 64 bit offsets, where they
> formerly worked with 32 bit off_t arguments. This could be considered
> ABI breakage, too.

That's definitely an ABI break, so the transition is necessary in any
case. We can always add back the compat layer if we deem it necessary.


-- System Information:
Debian Release: trixie/sid
  APT prefers noble-updates
  APT policy: (500, 'noble-updates'), (500, 'noble'), (100, 'noble-proposed')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.8.0-20-generic (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_USER, TAINT_OOT_MODULE
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.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
diff -Nru mpg123-1.32.5/debian/changelog mpg123-1.32.5/debian/changelog
--- mpg123-1.32.5/debian/changelog  2024-03-31 10:08:02.0 +0200
+++ mpg123-1.32.5/debian/changelog  2024-04-03 20:29:56.0 +0200
@@ -1,3 +1,13 @@
+mpg123 (1.32.5-1ubuntu1) noble; urgency=medium
+
+  [ Steve Langasek ]
+  * Rename libraries for 64-bit time_t transition. (Closes: #1063140)
+
+  [ Simon Chopin ]
+  * Only include 32bit compat symbols on i386 arches (Closes: #1067562)
+
+ -- Simon Chopin   Wed, 03 Apr 2024 20:29:56 +0200
+
 mpg123 (1.32.5-1build2) noble; urgency=medium
 
   * No-change rebuild for CVE-2024-3094
diff -Nru mpg123-1.32.5/debian/control mpg123-1.32.5/debian/control
--- mpg123-1.32.5/debian/control2024-03-12 07:39:44.0 +0100
+++ mpg123-1.32.5/debian/control2024-04-03 20:20:46.0 +0200
@@ -43,7 +43,10 @@
  OSS4, the Advanced Linux Sound Architecture (ALSA), JACK, PortAudio,
  PulseAudio, OpenAL and the Network Audio System (NAS).
 
-Package: libmpg123-0
+Package: libmpg123-0t64
+Provides: ${t64:Provides}
+Replaces: libmpg123-0
+Breaks: libmpg123-0 (<< ${source:Version})
 Multi-Arch: same
 Architecture: any
 Section: libs
@@ -57,7 +60,10 @@
  This package contains the C libraries needed to run executables that use
  the mpg123 library.
 
-Package: libout123-0
+Package: libout123-0t64
+Provides: ${t64:Provides}
+Replaces: libout123-0
+Breaks: libout123-0 (<< ${source:Version})
 Multi-Arch: same
 Architecture: any
 Section: libs
@@ -70,7 +76,10 @@
  .
  This package contains the shared out123 library.
 
-Package: libsyn123-0
+Package: libsyn123-0t64
+Provides: ${t64:Provides}
+Replaces: libsyn123-0
+Breaks: libsyn123-0 (<< ${source:Version})
 Multi-Arch: same
 Architecture: any
 Section: libs
@@ -88,9 +97,9 @@
 Architecture: any
 Section: libdevel
 Depends:
- libmpg123-0 (= ${binary:Version}),
- libout123-0 (= ${binary:Version}),
- libsyn123-0 (= ${binary:Version}),
+ libmpg123-0t64 (= ${binary:Version}),
+ libout123-0t64 (= ${binary:Version}),
+ libsyn123-0t64 (= ${binary:Version}),
  ${misc:Depends}
 Description: MPEG layer 1/2/3 audio decoder (development files)
  mpg123 is a real time MPEG 1.0/2.0/2.5 audio player/decoder for layers
diff -Nru mpg123-1.32.5/debian/libmpg123-0.install 
mpg123-1.32.5/debian/libmpg123-0.install
--- mpg123-1.32.5/debian/libmpg123-0.install2023-10-01 15:44:05.0 
+0200
+++ mpg123-1.32.5/debian/libmpg123-0.install1970-01-01 01:00:00.0 
+0100
@@ -1 +0,0 @@
-usr/lib/*/libmpg123.so.0*
diff -Nru mpg123-1.32.5/debian/libmpg123-0.lintian-overrides 
mpg123-1.32.5/debian/libmpg123-0.lintian-overrides
--- mpg123-1.32.5/debian/libmpg123-0.lintian-overrides  2023-10-01 
15:44:05.0 +0200
+++ mpg123-1.32.5/debian/libmpg123-0.lintian-overrides  1970-01-01 
01:00:00.0 +0100
@@ -1,2 +0,0 @@
-# The SSE, 3DNowExt, 3DNow, and MMX decoders use non-pic assembly code.
-libmpg123-0 [i386]: specific-address-in-shared-library
diff -Nru mpg123-1.32.5/debian/libmpg123-0.symbols 
mpg123-1.32.5/debian/libmpg123-0.symbols
--- mpg123-1.32.5/debian/libmpg123-0.symbols2023-10-02 21:38:58.0 
+0200
+++ mpg123-1.32.5/debian/libmpg123-0.symbols1970-01-01 01:00:00.0 
+0100
@@ -1,160 +0,0 @@
-libmpg123.so.0 libmpg123-0 #MINVER#
- mpg123_add_string@Base 1.6.2
- mpg123_add_substring@Base 1.6.2
- mpg123_chomp_string@Base 1.15.1
- mpg123_clip@Base 1.6.2
- mpg123_close@Base 1.6.2
- mpg123_copy_string@Base 1.6.2
- mpg123_current_decoder@Base 1.7.2
- mpg123_decode@Base 1.6.2
- mpg123_decode_frame64@Base 1.32.3
- mpg123_decode_frame@Base 1.6.2
- mpg123_decode_frame_64@Base 1.13.7
- mpg123_decoder@Base 1.6.2
- mpg123_decoders@Base 1.6.2
- mpg123_delete@Base 1.6.2
- mpg123_delete_pars@Base 1.6.2
- mpg123_delete_string@Base 1.26.0
- mpg123_distversion@Base 1.32.3
- mpg123_enc_from_id3@Base 1.9.1
- mpg123_enc_from_id3_2@Base 1.28.0
- 

Bug#1066437: libast: FTBFS: snprintf.c:45:22: error: unknown type name ‘size_t’

[Andreas Beckmann]

On Wed, 13 Mar 2024 13:03:27 +0100 Lucas Nussbaum  wrote:

Source: libast
Version: 0.7-9.1



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



> snprintf.c:45:22: error: unknown type name ‘size_t’
>45 | vsnprintf(char *str, size_t count, const char *fmt, va_list args)
>   |  ^~


This was so far the worst case of -Werror=implicit-function-declaration 
I encountered:

- a missing #include  (for exit()) caused a configure test to fail
- that didn't cause the configure step to fail (or silently disable some 
feature)
- but enabled a fallback codepath which had tons of errors triggering on 
-Werror=implicit-function-declaration


;-)

Perhaps you could add to your wiki entry about this bug class that there 
may be non-obvious problems during the configure step caused by 
-Werror=implicit-function-declaration that might

- silently disable features (because detection failed)
- enable unwanted fallback codepaths for "missing" (becuase misdetected) 
features


Andreas

Bug#1061493: marked as done (consolekit: install PAM module and udev files into /usr)

[Debian Bug Tracking System]

Your message dated Wed, 3 Apr 2024 19:20:55 +0100
with message-id 
and subject line Re: Bug#1061493: consolekit: install PAM module and udev files 
into /usr
has caused the Debian Bug report #1061493,
regarding consolekit: install PAM module and udev files into /usr
to be marked as done.

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

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


-- 
1061493: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061493
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: consolekit2
Version: 1.2.6-3
Severity: normal
Tags: patch
User: helm...@debian.org
Usertags: dep17m2

We want to finalize the /usr-merge via DEP17 by moving all files to
/usr. consolekit installs files into /lib; these should be moved into
the respective canonical locations in /usr/.

Please find a patch attached. It has been build-tested.

Note: this should not be backported to bookworm. If you intend to
backport, please use dh_movetousr instead.

If your package will change for the t64 transition or otherwise
rename/split/move its binaries (packages) during trixie, please
then upload to experimental and get in touch with the UsrMerge
driver, please see the wiki [1].

Michael

[1] https://wiki.debian.org/UsrMerge
diff -Nru consolekit2-1.2.6/debian/changelog consolekit2-1.2.6/debian/changelog
--- consolekit2-1.2.6/debian/changelog  2023-11-16 13:42:48.0 +0100
+++ consolekit2-1.2.6/debian/changelog  2024-01-25 15:02:55.0 +0100
@@ -1,3 +1,10 @@
+consolekit2 (1.2.6-3.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Install PAM module into /usr. (Closes: #-1)
+
+ -- Michael Biebl   Thu, 25 Jan 2024 15:02:55 +0100
+
 consolekit2 (1.2.6-3) unstable; urgency=medium
 
   * License appstream metainfo as FSFAP.
diff -Nru consolekit2-1.2.6/debian/consolekit.install 
consolekit2-1.2.6/debian/consolekit.install
--- consolekit2-1.2.6/debian/consolekit.install 2023-11-16 13:42:48.0 
+0100
+++ consolekit2-1.2.6/debian/consolekit.install 2024-01-25 15:02:55.0 
+0100
@@ -3,7 +3,7 @@
 etc/X11/Xsession.d/
 etc/logrotate.d/
 etc/ConsoleKit/
-[linux-any] lib/udev/
+[linux-any] usr/lib/udev/
 usr/share/dbus-1/system-services/
 usr/share/polkit-1/
 usr/share/locale/
diff -Nru consolekit2-1.2.6/debian/control consolekit2-1.2.6/debian/control
--- consolekit2-1.2.6/debian/control2023-11-16 13:42:48.0 +0100
+++ consolekit2-1.2.6/debian/control2024-01-25 15:02:55.0 +0100
@@ -12,7 +12,7 @@
libdbus-1-dev,
libdrm-dev,
libselinux1-dev [linux-any],
-   libudev-dev [linux-any],
+   libudev-dev (>= 255.1-1~) [linux-any],
libacl1-dev [linux-any],
libevdev-dev [linux-any],
libpam0g-dev,
diff -Nru consolekit2-1.2.6/debian/libpam-ck-connector.install 
consolekit2-1.2.6/debian/libpam-ck-connector.install
--- consolekit2-1.2.6/debian/libpam-ck-connector.install2023-11-16 
13:42:48.0 +0100
+++ consolekit2-1.2.6/debian/libpam-ck-connector.install2024-01-25 
15:02:49.0 +0100
@@ -1,4 +1,4 @@
 #! /usr/bin/dh-exec
-lib/*/security/pam_ck_connector.so
+usr/lib/*/security/pam_ck_connector.so
 usr/share/man/man8/pam_ck_connector.8
 debian/libpam-ck-connector.pam-auth-update => usr/share/pam-configs/consolekit
diff -Nru consolekit2-1.2.6/debian/rules consolekit2-1.2.6/debian/rules
--- consolekit2-1.2.6/debian/rules  2023-11-16 13:42:48.0 +0100
+++ consolekit2-1.2.6/debian/rules  2024-01-25 15:02:36.0 +0100
@@ -33,11 +33,11 @@
--without-systemdsystemunitdir \
--enable-docbook-docs \
--enable-gtk-doc \
-   --with-pam-module-dir=/lib/$(DEB_HOST_MULTIARCH)/security
+   --with-pam-module-dir=/usr/lib/$(DEB_HOST_MULTIARCH)/security
 
 override_dh_install:
# la files are not required any more
-   rm debian/tmp/lib/*/security/pam_ck_connector.la \
+   rm debian/tmp/usr/lib/*/security/pam_ck_connector.la \
   debian/tmp/usr/lib/*/libck-connector.la \
   debian/tmp/usr/lib/*/libconsolekit.la
# end user doesn't need these files
--- End Message ---
--- Begin Message ---
On Tue, Mar 19, 2024 at 01:18:58PM +1300, Michael Hudson-Doyle wrote:
>I thought I had uploaded a fix for this but in any case it was
>determined that consolekit2 did not need to be part of the transition
>so the package can be removed from experimental. I'll file a removal
>request in a moment, or you can just upload over it.

Thanks. The RM is done and there appears to be nothing 

Bug#1066942: marked as done (xmrig: FTBFS on armhf: cc: error: unrecognized command-line option ‘-maes’)

[Debian Bug Tracking System]

Your message dated Wed, 03 Apr 2024 17:50:28 +
with message-id 
and subject line Bug#1066942: fixed in xmrig 6.21.2+dfsg-2
has caused the Debian Bug report #1066942,
regarding xmrig: FTBFS on armhf: cc: error: unrecognized command-line option 
‘-maes’
to be marked as done.

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

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


-- 
1066942: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066942
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: xmrig
Version: 6.21.1+dfsg-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org

https://buildd.debian.org/status/fetch.php?pkg=xmrig=armhf=6.21.1%2Bdfsg-1%2Bb1=1710494247=0

cd /<>/obj-arm-linux-gnueabihf/src/3rdparty/argon2 && /usr/bin/cc 
-DCL_TARGET_OPENCL_VERSION=200 -DCL_USE_DEPRECATED_OPENCL_1_2_APIS 
-DHAVE_BUILTIN_CLEAR_CACHE -DHAVE_ROTR -DHAVE_SYSLOG_H -DUNICODE 
-DXMRIG_ALGO_ARGON2 -DXMRIG_ALGO_RANDOMX -DXMRIG_FEATURE_ADL 
-DXMRIG_FEATURE_API -DXMRIG_FEATURE_BENCHMARK -DXMRIG_FEATURE_CUDA 
-DXMRIG_FEATURE_ENV -DXMRIG_FEATURE_HTTP -DXMRIG_FEATURE_HWLOC 
-DXMRIG_FEATURE_NVML -DXMRIG_FEATURE_OPENCL -DXMRIG_JSON_SINGLE_LINE_ARRAY 
-DXMRIG_MINER_PROJECT -DXMRIG_OS_LINUX -DXMRIG_OS_UNIX 
-DXMRIG_STRICT_OPENCL_CACHE -D_FILE_OFFSET_BITS=64 -D_GNU_SOURCE 
-D__STDC_FORMAT_MACROS -I/<>/src/3rdparty/argon2/../.. 
-I/<>/src/3rdparty/argon2/lib -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 -D_LARGEFILE_SOURCE 
-D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 -Wall 
-Wno-strict-aliasing -maes -std=gnu99 -MD -MT 
src/3rdparty/argon2/CMakeFiles/argon2.dir/lib/impl-select.c.o -MF 
CMakeFiles/argon2.dir/lib/impl-select.c.o.d -o 
CMakeFiles/argon2.dir/lib/impl-select.c.o -c 
/<>/src/3rdparty/argon2/lib/impl-select.c
cc: error: unrecognized command-line option ‘-maes’

Cheers
-- 
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Source: xmrig
Source-Version: 6.21.2+dfsg-2
Done: Ben Westover 

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

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

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

Debian distribution maintenance software
pp.
Ben Westover  (supplier of updated xmrig package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 03 Apr 2024 13:22:12 -0400
Source: xmrig
Architecture: source
Version: 6.21.2+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Cryptocoin Team 
Changed-By: Ben Westover 
Closes: 1066942
Changes:
 xmrig (6.21.2+dfsg-2) unstable; urgency=medium
 .
   * Forces ARMv7 build if on armhf architecture (Closes: #1066942)
Checksums-Sha1:
 66f48266ee2310194a7f661f66c8a6a6bf9af512 2088 xmrig_6.21.2+dfsg-2.dsc
 f4ad36b19235b9e6fe5e54103119624f70d5481d 7704 xmrig_6.21.2+dfsg-2.debian.tar.xz
 4b73d89c2f5ad4c8384fd700754eb20ee37176ce 7172 
xmrig_6.21.2+dfsg-2_source.buildinfo
Checksums-Sha256:
 01da4119f13260df0e234619a84accdc9b4c867a22bc87d826373cc99b08e474 2088 
xmrig_6.21.2+dfsg-2.dsc
 c04417d5a04cf0598799387815ffdbb0c6322459a46e500595db90b4a1d9775c 7704 
xmrig_6.21.2+dfsg-2.debian.tar.xz
 4ae0752f78eb69c7bd1d9ceb2f3320f5dca14beac465fa631653d5d02399276e 7172 
xmrig_6.21.2+dfsg-2_source.buildinfo
Files:
 7e7b0fbd421e67f7cfff63d2d2486193 2088 utils optional xmrig_6.21.2+dfsg-2.dsc
 fa54d02b57e265fccd7d9fc5887b3192 7704 utils optional 
xmrig_6.21.2+dfsg-2.debian.tar.xz
 25ff162df261ed3b3b706993059dddb1 7172 utils optional 
xmrig_6.21.2+dfsg-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJJBAEBCgAzFiEEOGnacqRhdU6eNmtFwxHF9U6JtpgFAmYNkF4VHG1lQGJlbnRo
ZXRlY2hndXkubmV0AAoJEMMRxfVOibaYn9kP/06C9LkoQTJ6S82GRZZ9AHPN2Lpv
PQDbHR2ffHuy8nSGlbxEOiVM9q2BdpDa6z72KIICbEkDey0qzjnynjctIXOM58Xg
q3HoLgweAF/kVqTyHwUpTzoO3Pt33xo3N2J1PBQznEW2ewwhLPq3M+CZLqLBkhBG
tTzhjHcyPf35ACck1UxVAnblMv+0eLH0MvQUTcR25G2npkyG/Uup7v7sHdsfVyUt
GT8bPS37Xji/ceiquL3D2PBnFQ6oLggNHz94GPqiX2AVKGLl/bdhAUVRCVmVrQWF

Bug#1066437: marked as done (libast: FTBFS: snprintf.c:45:22: error: unknown type name ‘size_t’)

[Debian Bug Tracking System]

Your message dated Wed, 03 Apr 2024 17:34:04 +
with message-id 
and subject line Bug#1066437: fixed in libast 0.7-10
has caused the Debian Bug report #1066437,
regarding libast: FTBFS: snprintf.c:45:22: error: unknown type name ‘size_t’
to be marked as done.

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

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


-- 
1066437: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066437
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libast
Version: 0.7-9.1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240313 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> /bin/bash ../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. 
> -I../include/libast -I../include -I../include/libast  -I/usr/include 
> -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 -fcf-protection -c -o snprintf.lo snprintf.c
> libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I.. -I../include/libast 
> -I../include -I../include/libast -I/usr/include -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 -fcf-protection -c 
> snprintf.c  -fPIC -DPIC -o .libs/snprintf.o
> snprintf.c:45:22: error: unknown type name ‘size_t’
>45 | vsnprintf(char *str, size_t count, const char *fmt, va_list args)
>   |  ^~
> snprintf.c:8:1: note: ‘size_t’ is defined in header ‘’; did you 
> forget to ‘#include ’?
> 7 | # include 
>   +++ |+#include 
> 8 | #else
> snprintf.c:58:21: error: unknown type name ‘size_t’
>58 | snprintf(char *str, size_t count, const char *fmt, ...)
>   | ^~
> snprintf.c:58:21: note: ‘size_t’ is defined in header ‘’; did you 
> forget to ‘#include ’?
> snprintf.c: In function ‘fmtstr’:
> snprintf.c:250:36: error: implicit declaration of function ‘iscntrl’ 
> [-Werror=implicit-function-declaration]
>   250 | if (visible_control && iscntrl(c) && !isspace(c)) {
>   |^~~
> snprintf.c:8:1: note: include ‘’ or provide a declaration of 
> ‘iscntrl’
> 7 | # include 
>   +++ |+#include 
> 8 | #else
> snprintf.c:250:51: error: implicit declaration of function ‘isspace’ 
> [-Werror=implicit-function-declaration]
>   250 | if (visible_control && iscntrl(c) && !isspace(c)) {
>   |   ^~~
> snprintf.c:250:51: note: include ‘’ or provide a declaration of 
> ‘isspace’
> snprintf.c: In function ‘fmtdouble’:
> snprintf.c:359:5: error: implicit declaration of function ‘strcpy’ 
> [-Werror=implicit-function-declaration]
>   359 | strcpy(fmtstr, "%");
>   | ^~
> snprintf.c:8:1: note: include ‘’ or provide a declaration of 
> ‘strcpy’
> 7 | # include 
>   +++ |+#include 
> 8 | #else
> snprintf.c:359:5: warning: incompatible implicit declaration of built-in 
> function ‘strcpy’ [-Wbuiltin-declaration-mismatch]
>   359 | strcpy(fmtstr, "%");
>   | ^~
> snprintf.c:359:5: note: include ‘’ or provide a declaration of 
> ‘strcpy’
> snprintf.c:361:9: error: implicit declaration of function ‘strcat’ 
> [-Werror=implicit-function-declaration]
>   361 | strcat(fmtstr, "-");
>   | ^~
> snprintf.c:361:9: note: include ‘’ or provide a declaration of 
> ‘strcat’
> snprintf.c:361:9: warning: incompatible implicit declaration of built-in 
> function ‘strcat’ [-Wbuiltin-declaration-mismatch]
> snprintf.c:361:9: note: include ‘’ or provide a declaration of 
> ‘strcat’
> snprintf.c:363:9: error: implicit declaration of function ‘sprintf’ 
> [-Werror=implicit-function-declaration]
>   363 | sprintf(fmtstr + strlen(fmtstr), "%d", len);
>   | ^~~
> snprintf.c:8:1: note: include ‘’ or provide a declaration of 
> ‘sprintf’
> 7 | # include 
>   +++ |+#include 
> 8 | #else
> snprintf.c:363:9: warning: incompatible implicit declaration of built-in 
> function ‘sprintf’ [-Wbuiltin-declaration-mismatch]
>   363 | sprintf(fmtstr + strlen(fmtstr), "%d", len);
>   | ^~~
> snprintf.c:363:9: note: include ‘’ or provide a declaration of 
> ‘sprintf’
> snprintf.c:363:26: error: implicit declaration of function ‘strlen’ 
> [-Werror=implicit-function-declaration]
>   

Bug#1057442: marked as done (onboard ftbfs with Python 3.12)

[Debian Bug Tracking System]

Your message dated Wed, 03 Apr 2024 17:34:21 +
with message-id 
and subject line Bug#1057442: fixed in onboard 1.4.1-6
has caused the Debian Bug report #1057442,
regarding onboard ftbfs with Python 3.12
to be marked as done.

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

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


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

Package: src:onboard
Version: 1.4.1-5
Severity: serious
Tags: sid trixie
User: debian-pyt...@lists.debian.org
Usertags: python3.12

onboard ftbfs with Python 3.12:

[...]
creating build
creating build/temp.linux-x86_64-cpython-312
creating build/temp.linux-x86_64-cpython-312/Onboard
creating build/temp.linux-x86_64-cpython-312/Onboard/osk
x86_64-linux-gnu-gcc -fno-strict-overflow -Wsign-compare -DNDEBUG -g -O2 
-Wall -g -fstack-protector-strong -fstack-clash-protection -Wformat 
-Werror=format-security -fcf-protection -g -fwrapv -O2 -g -O2 
-ffile-prefix-map=/<>=. 
-specs=/usr/share/dpkg/no-pie-compile.specs -fstack-protector-strong 
-fstack-clash-protection -Wformat -Werror=format-security 
-fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -DMAJOR_VERSION=0 
-DMINOR_VERSION=4 -DMICRO_VERSION=0 -I/usr/include/blkid 
-I/usr/include/cairo -I/usr/include/cloudproviders -I/usr/include/dconf 
-I/usr/include/freetype2 -I/usr/include/fribidi 
-I/usr/include/gdk-pixbuf-2.0 -I/usr/include/gio-unix-2.0 
-I/usr/include/glib-2.0 -I/usr/include/gtk-3.0 -I/usr/include/harfbuzz 
-I/usr/include/hunspell -I/usr/include/libmount -I/usr/include/libpng16 
-I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/webp 
-I/usr/include/x86_64-linux-gnu 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/python3.12 
-c Onboard/osk/osk_audio.c -o 
build/temp.linux-x86_64-cpython-312/Onboard/osk/osk_audio.o 
-Wsign-compare -Wdeclaration-after-statement 
-Werror=declaration-after-statement

In file included from /usr/include/python3.12/Python.h:44,
 from Onboard/osk/osk_module.h:25,
 from Onboard/osk/osk_audio.c:21:
/usr/include/python3.12/object.h: In function ‘Py_SIZE’:
/usr/include/python3.12/object.h:233:5: error: ISO C90 forbids mixed 
declarations and code [-Werror=declaration-after-statement]

  233 | PyVarObject *var_ob = _PyVarObject_CAST(ob);
  | ^~~
In file included from /usr/include/python3.12/Python.h:53:
/usr/include/python3.12/cpython/longintrepr.h: In function 
‘_PyLong_CompactValue’:
/usr/include/python3.12/cpython/longintrepr.h:121:5: error: ISO C90 
forbids mixed declarations and code [-Werror=declaration-after-statement]
  121 | Py_ssize_t sign = 1 - (op->long_value.lv_tag & 
_PyLong_SIGN_MASK);

  | ^~
Onboard/osk/osk_audio.c: In function ‘osk_audio_init_canberra’:
Onboard/osk/osk_audio.c:70:5: warning: ‘gdk_screen_get_number’ is 
deprecated [-Wdeprecated-declarations]

   70 | nr = gdk_screen_get_number(screen);
  | ^~
In file included from /usr/include/gtk-3.0/gdk/gdkapplaunchcontext.h:31,
 from /usr/include/gtk-3.0/gdk/gdk.h:32,
 from /usr/include/gtk-3.0/gdk/gdkx.h:28,
 from Onboard/osk/osk_audio.c:23:
/usr/include/gtk-3.0/gdk/gdkscreen.h:56:14: note: declared here
   56 | gint gdk_screen_get_number(GdkScreen 
*screen);

  |  ^
Onboard/osk/osk_audio.c: In function ‘osk_audio_play’:
Onboard/osk/osk_audio.c:101:5: warning: ‘gdk_screen_get_width’ is 
deprecated [-Wdeprecated-declarations]

  101 | sw = gdk_screen_get_width(screen);
  | ^~
/usr/include/gtk-3.0/gdk/gdkscreen.h:58:14: note: declared here
   58 | gint gdk_screen_get_width (GdkScreen 
*screen);

  |  ^~~~
Onboard/osk/osk_audio.c:102:5: warning: ‘gdk_screen_get_height’ is 
deprecated [-Wdeprecated-declarations]

  102 | sh = gdk_screen_get_height(screen);
  | ^~
/usr/include/gtk-3.0/gdk/gdkscreen.h:60:14: note: declared here
   60 | gint gdk_screen_get_height(GdkScreen 
*screen);

  |  ^
cc1: some warnings being treated as errors
error: command '/usr/bin/x86_64-linux-gnu-gcc' failed with exit code 1
E: pybuild pybuild:395: build: plugin distutils failed with: exit 
code=1: /usr/bin/python3.12 setup.py build

I: pybuild base:310: /usr/bin/python3 setup.py build
--- End Message ---
--- Begin Message ---
Source: onboard
Source-Version: 1.4.1-6
Done: Mike Gabriel 

We believe that the bug you reported is fixed in the latest version of

Bug#1066942: Debugging xmrig FTBFS on armhf

[Ben Westover]

I could not reproduce the issue on an armhf porterbox, which is 
concerning. I have just uploaded a new release that just tells cmake to 
force an ARMv7 build if DEB_HOST_ARCH is armhf. It also includes a handy 
patch that makes the build log give a couple clues so I can track down 
why my machine and the porterbox can't reproduce it but the buildd can.


--
Ben Westover


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1067326: marked as done (mkdocstrings: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13)

[Debian Bug Tracking System]

Your message dated Wed, 03 Apr 2024 17:19:17 +
with message-id 
and subject line Bug#1067326: fixed in mkdocstrings 0.24.2-1
has caused the Debian Bug report #1067326,
regarding mkdocstrings: FTBFS: dh_auto_test: error: pybuild --test 
--test-pytest -i python{version} -p "3.12 3.11" returned exit code 13
to be marked as done.

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

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


-- 
1067326: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067326
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mkdocstrings
Version: 0.24.1-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240319 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
>  debian/rules binary
> dh binary --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild plugin_pyproject:129: Building wheel for python3.12 with "build" 
> module
> I: pybuild base:305: python3.12 -m build --skip-dependency-check 
> --no-isolation --wheel --outdir 
> /<>/.pybuild/cpython3_3.12_mkdocstrings  
> * Building wheel...
>  - Adding .pdm-build/mkdocstrings-0.24.1.dist-info/METADATA -> 
> mkdocstrings-0.24.1.dist-info/METADATA
>  - Adding .pdm-build/mkdocstrings-0.24.1.dist-info/WHEEL -> 
> mkdocstrings-0.24.1.dist-info/WHEEL
>  - Adding .pdm-build/mkdocstrings-0.24.1.dist-info/entry_points.txt -> 
> mkdocstrings-0.24.1.dist-info/entry_points.txt
>  - Adding .pdm-build/mkdocstrings-0.24.1.dist-info/licenses/LICENSE -> 
> mkdocstrings-0.24.1.dist-info/licenses/LICENSE
>  - Adding src/mkdocstrings/__init__.py -> mkdocstrings/__init__.py
>  - Adding src/mkdocstrings/_cache.py -> mkdocstrings/_cache.py
>  - Adding src/mkdocstrings/debug.py -> mkdocstrings/debug.py
>  - Adding src/mkdocstrings/extension.py -> mkdocstrings/extension.py
>  - Adding src/mkdocstrings/handlers/__init__.py -> 
> mkdocstrings/handlers/__init__.py
>  - Adding src/mkdocstrings/handlers/base.py -> mkdocstrings/handlers/base.py
>  - Adding src/mkdocstrings/handlers/rendering.py -> 
> mkdocstrings/handlers/rendering.py
>  - Adding src/mkdocstrings/inventory.py -> mkdocstrings/inventory.py
>  - Adding src/mkdocstrings/loggers.py -> mkdocstrings/loggers.py
>  - Adding src/mkdocstrings/plugin.py -> mkdocstrings/plugin.py
>  - Adding src/mkdocstrings/py.typed -> mkdocstrings/py.typed
>  - Adding mkdocstrings-0.24.1.dist-info/RECORD -> 
> mkdocstrings-0.24.1.dist-info/RECORD
> Successfully built mkdocstrings-0.24.1-py3-none-any.whl
> I: pybuild plugin_pyproject:144: Unpacking wheel built for python3.12 with 
> "installer" module
> I: pybuild plugin_pyproject:129: Building wheel for python3.11 with "build" 
> module
> I: pybuild base:305: python3.11 -m build --skip-dependency-check 
> --no-isolation --wheel --outdir 
> /<>/.pybuild/cpython3_3.11_mkdocstrings  
> * Building wheel...
>  - Adding .pdm-build/mkdocstrings-0.24.1.dist-info/METADATA -> 
> mkdocstrings-0.24.1.dist-info/METADATA
>  - Adding .pdm-build/mkdocstrings-0.24.1.dist-info/WHEEL -> 
> mkdocstrings-0.24.1.dist-info/WHEEL
>  - Adding .pdm-build/mkdocstrings-0.24.1.dist-info/entry_points.txt -> 
> mkdocstrings-0.24.1.dist-info/entry_points.txt
>  - Adding .pdm-build/mkdocstrings-0.24.1.dist-info/licenses/LICENSE -> 
> mkdocstrings-0.24.1.dist-info/licenses/LICENSE
>  - Adding src/mkdocstrings/__init__.py -> mkdocstrings/__init__.py
>  - Adding src/mkdocstrings/_cache.py -> mkdocstrings/_cache.py
>  - Adding src/mkdocstrings/debug.py -> mkdocstrings/debug.py
>  - Adding src/mkdocstrings/extension.py -> mkdocstrings/extension.py
>  - Adding src/mkdocstrings/handlers/__init__.py -> 
> mkdocstrings/handlers/__init__.py
>  - Adding src/mkdocstrings/handlers/base.py -> mkdocstrings/handlers/base.py
>  - Adding src/mkdocstrings/handlers/rendering.py -> 
> mkdocstrings/handlers/rendering.py
>  - Adding src/mkdocstrings/inventory.py -> mkdocstrings/inventory.py
>  - Adding src/mkdocstrings/loggers.py -> mkdocstrings/loggers.py
>  - Adding src/mkdocstrings/plugin.py -> mkdocstrings/plugin.py
>  - Adding src/mkdocstrings/py.typed -> mkdocstrings/py.typed
>  - Adding mkdocstrings-0.24.1.dist-info/RECORD -> 
> mkdocstrings-0.24.1.dist-info/RECORD
> Successfully built mkdocstrings-0.24.1-py3-none-any.whl
> I: pybuild plugin_pyproject:144: Unpacking wheel built for python3.11 with 
> "installer" module
>dh_auto_test -O--buildsystem=pybuild
> I: pybuild 

Bug#1067311: ipywidgets: FTBFS: unsatisfiable build-dependency: jupyter-nbextension-jupyter-js-widgets (= 8.1.1-3) but 8.1.1-2 is to be installed

[Andreas Beckmann]

Followup-For: Bug #1067311

There seem to be two problems leading to this bug:

1.)
- jupyter-nbextension-jupyter-js-widgets is no longer built from
  src:ipywidgets since -3
- it is not provided by any other package
- it ships /etc/jupyter/nbconfig/notebook.d/jupyter-js-widgets.json (and
  nothing else), this file does not seem to exist in any other package
- python3-ipywidgets still depends on it (versioned in -3, unversioned
  in -4)
- perhaps the removal was a mistake?

2.)
- there is a circular build-dependency
  src:ipywidgets Build-Depends: python3-bqplot
  python3-bqplot Depends: python3-ipywidgets
- you need some way to bootstrap ipywidgets, i.e. temporarily drop the
  cycle, e.g. using build profiles


Andreas

Processed: Bug#1057442 marked as pending in onboard

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1057442 [src:onboard] onboard ftbfs with Python 3.12
Added tag(s) pending.

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

Bug#1057442: marked as pending in onboard

[Mike Gabriel]

Control: tag -1 pending

Hello,

Bug #1057442 in onboard reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/debian-mate-team/onboard/-/commit/e1c683eda8f7e548ad486d7b5fe6bb15ad9eb4cf


debian/patches: Fix ftbfs on python3.12. (Closes: #1057442).


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1057442

Bug#1068188: pthread_cond_init.3.gz: conflict with manpages-dev 6.7-1

[Sven Joachim]

Control: severity -1 normal

On 2024-04-03 11:29 +0200, Alejandro Colomar wrote:

> Hi,
>
> On Tue, Apr 02, 2024 at 08:58:32PM +0200, Aurelien Jarno wrote:
>> Thanks, that sounds great that we can finally get rid out of those in
>> the debian package.
>>
>> >$ git diff --stat b06cd070f..128a3ae35
>> > man3/pthread_cond_init.3| 264 
>> > man3/pthread_condattr_init.3|  48 
>> > man3/pthread_key_create.3   | 178 +
>> > man3/pthread_mutex_init.3   | 241 ++
>> > man3/pthread_mutexattr_setkind_np.3 |  52 
>> > man3/pthread_once.3 |  44 
>> > 6 files changed, 827 insertions(+)
>
> I now see that `apt-file show glibc-doc` shows several more pages.  I'll
> have a look at them and maybe I also import them into the Linux
> man-pages project.

AFAICS all of them have already been added there, right?

>> > Debian's manpages-dev_6.7-1_all.deb has been the first package since
>> > that happened, and I've noticed that dpkg(1) (via apt-get(8)) refuses to
>> > upgrade manpages-dev due to a conflict with glibc-doc.
>> >
>> >$ sudo apt-get upgrade -V;
>> >[...]
>> >Do you want to continue? [Y/n] y
>> >Reading changelogs... Done
>> >(Reading database ... 404853 files and directories currently installed.)
>> >Preparing to unpack .../manpages-dev_6.7-1_all.deb ...
>> >Unpacking manpages-dev (6.7-1) over (6.05.01-1) ...
>> >dpkg: error processing archive 
>> > /var/cache/apt/archives/manpages-dev_6.7-1_all.deb (--unpack):
>> > trying to overwrite '/usr/share/man/man3/pthread_cond_init.3.gz', 
>> > which is also in package glibc-doc 2.38-6
>> >Errors were encountered while processing:
>> > /var/cache/apt/archives/manpages-dev_6.7-1_all.deb
>> >needrestart is being skipped since dpkg has failed
>> >E: Sub-process /usr/bin/dpkg returned an error code (1)
>>
>> I think this is actually not specific to the experimental version, those
>> manpages are also in the unstable version.
>
> Right.  I only installed the experimental one to see if the bug had
> been fixed (as reportbug(1) suggested trying it).
>
>> > Please, remove from glibc-doc those manual pages that conflict with
>> > manpages-dev.
>>
>> Noted. However following the time_t transition, the glibc package does
>> not build anymore on 32-bit architectures (i have just opened #1059937
>> to make people aware of that), so uploading a new glibc now is probably
>> not the best idea.
>
> Hmm, maybe you can drop the manual pages, but not upload yet, and wait
> for that bug to be fixed to do an upload without the pages.

Note that manpages-dev 6.7-2 has dropped the clashing files for the time
being.  I do not think there is any need to hurry, so I am downgrading
the severity of this bug.  Whenever the glibc-doc package in unstable
drops the manpages, we should file a bug against manpages-dev to include
them again.

Cheers,
   Sven

Processed: Re: Bug#1068188: pthread_cond_init.3.gz: conflict with manpages-dev 6.7-1

[Debian Bug Tracking System]

Processing control commands:

> severity -1 normal
Bug #1068188 [glibc-doc] pthread_cond_init.3.gz: conflict with manpages-dev 
6.7-1
Severity set to 'normal' from 'serious'

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

Bug#1068158: marked as done (python-escript: FTBFS: RuntimeError: We do not current support different different dpkg-buildflags for C vs C++:)

[Debian Bug Tracking System]

Your message dated Wed, 03 Apr 2024 15:36:07 +
with message-id 
and subject line Bug#1068158: fixed in python-escript 5.6-7
has caused the Debian Bug report #1068158,
regarding python-escript: FTBFS: RuntimeError: We do not current support 
different different dpkg-buildflags for C vs C++:
to be marked as done.

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

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


-- 
1068158: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068158
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-escript
Version: 5.6-6
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org

https://buildd.debian.org/status/fetch.php?pkg=python-escript=arm64=5.6-6%2Bb3=1711889068=0

mkdir -p /<>/debian/stage3
scons  -j4   cc_optim=' -O3  '  build_dir=/<>/debian/tmp3 
verbose=on prefix=/<>/debian/stage3 
options_file=debian/sid_options.py docs
scons: Reading SConscript files ...
3.11.8 (main, Mar 26 2024, 12:04:57) [GCC 13.2.0]
RuntimeError: We do not current support different different dpkg-buildflags for 
C vs C++:
  File "/<>/SConstruct", line 172:
env = Environment(tools = ['default'], options = vars,
  File "/usr/lib/python3/dist-packages/SCons/Environment.py", line 1231:
variables.Update(self)
  File "/usr/lib/python3/dist-packages/SCons/Variables/__init__.py", line 187:
exec(contents, {}, values)
  File "", line 84:

  File "/<>/site_scons/extractdebbuild.py", line 61:
raise RuntimeError("We do not current support different different 
dpkg-buildflags for C vs C++")
make[1]: *** [debian/rules:65: override_dh_auto_build] Error 2

Cheers
-- 
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Source: python-escript
Source-Version: 5.6-7
Done: Boyuan Yang 

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

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

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

Debian distribution maintenance software
pp.
Boyuan Yang  (supplier of updated python-escript package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 03 Apr 2024 10:52:48 -0400
Source: python-escript
Architecture: source
Version: 5.6-7
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Boyuan Yang 
Closes: 1067385 1068158
Changes:
 python-escript (5.6-7) unstable; urgency=medium
 .
   * Team upload.
   * debian/control: Apply "wrap-and-sort -abst" and unify between tabs
 and spaces.
   * debian/control: Move the main package descriptions to the source package
 section. Use variable replacement ${source:Synopsis} and
 ${source:Extended-Description} to avoid repeated boilerplate.
   * debian/control: Fix Vcs-* field syntax.
   * debian/gbp.conf: Use status quo and update default debian-branch to
 "debian/latest". Also add ignore-branch = True to circumvent pedantic
 issues.
 .
   [ Bo YU ]
   * Team upload.
   * Add fix-dpkg-buildflags-on-c-c++.patch to fix ftbfs issue.
 (Closes: #1068158)
   * No build dependencies issue now. (Closes: #1067385)
Checksums-Sha1:
 7787fb4c8e98e17ece6c633847fd5022bbfd2965 3547 python-escript_5.6-7.dsc
 496a0c5526577ad29ddfce487bc7e779ba35cb1f 39044652 
python-escript_5.6.orig.tar.xz
 9059511bb0260ac299bcd158bf58d925b7143043 20144 
python-escript_5.6-7.debian.tar.xz
 60a25cee7517ec045479d18b0a8ee10df6035165 21362 
python-escript_5.6-7_amd64.buildinfo
Checksums-Sha256:
 1648b4fa6ea2805857a14047980c4bcec1b5e2cc790f662d22fd2cebe5be1076 3547 
python-escript_5.6-7.dsc
 2947ef99ceab8dad4b0b7fdf5f402a873cce8503e40682115487815a4b2e33af 39044652 
python-escript_5.6.orig.tar.xz
 e4b2203aa6c4c39cf7016d3b6f85d17e468cc78cd098870f6fc25fb6121eba59 20144 
python-escript_5.6-7.debian.tar.xz
 43cc71ae819723fc84cb75932d176356af74dbaaf76cfe689532db61fccc83e6 21362 
python-escript_5.6-7_amd64.buildinfo
Files:
 5edbc3d1e5c386e3e80870ba0b64fc2f 3547 science optional python-escript_5.6-7.dsc
 495bbd86105fbf201aa33f65ee3d72c5 39044652 science optional 
python-escript_5.6.orig.tar.xz
 106f19a353bacf017e96f672f0bbe9d5 20144 science optional 

Bug#1067385: marked as done (python-escript: FTBFS: unsatisfiable build-dependencies (purely virtual?): libocct-data-exchange-7.6 (>= 7.6.3+dfsg1), libocct-ocaf-7.6 (>= 7.6.3+dfsg1))

[Debian Bug Tracking System]

Your message dated Wed, 03 Apr 2024 15:36:07 +
with message-id 
and subject line Bug#1067385: fixed in python-escript 5.6-7
has caused the Debian Bug report #1067385,
regarding python-escript: FTBFS: unsatisfiable build-dependencies (purely 
virtual?): libocct-data-exchange-7.6 (>= 7.6.3+dfsg1), libocct-ocaf-7.6 (>= 
7.6.3+dfsg1)
to be marked as done.

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

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


-- 
1067385: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067385
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-escript
Version: 5.6-6
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240319 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper-compat (= 13), dh-sequence-python3, 
> dh-sequence-sphinxdoc, python3-dev, python3-gdal, python3-matplotlib, 
> python3-numpy, python3-scipy, python3-pyproj, libcppunit-dev, 
> libsuitesparse-dev, libboost-python-dev, libboost-random-dev, 
> libboost-numpy-dev, libboost-iostreams-dev, libnetcdf-dev, 
> libnetcdf-c++4-dev, libsilo-dev (>= 4.10.2.real-5), libscotchparmetis-dev, 
> libscotchmetis-dev, gmsh, mpi-default-dev, scons, zip, python3-sphinx, 
> doxygen, texlive, ghostscript, texlive-latex-extra, 
> texlive-latex-recommended, lsb-release, libopenmpi-dev, openmpi-bin, 
> libjs-mathjax, build-essential, fakeroot
> Filtered Build-Depends: debhelper-compat (= 13), dh-sequence-python3, 
> dh-sequence-sphinxdoc, python3-dev, python3-gdal, python3-matplotlib, 
> python3-numpy, python3-scipy, python3-pyproj, libcppunit-dev, 
> libsuitesparse-dev, libboost-python-dev, libboost-random-dev, 
> libboost-numpy-dev, libboost-iostreams-dev, libnetcdf-dev, 
> libnetcdf-c++4-dev, libsilo-dev (>= 4.10.2.real-5), libscotchparmetis-dev, 
> libscotchmetis-dev, gmsh, mpi-default-dev, scons, zip, python3-sphinx, 
> doxygen, texlive, ghostscript, texlive-latex-extra, 
> texlive-latex-recommended, lsb-release, libopenmpi-dev, openmpi-bin, 
> libjs-mathjax, 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 [615 B]
> Ign:3 copy:/<>/apt_archive ./ Release.gpg
> Get:4 copy:/<>/apt_archive ./ Sources [1173 B]
> Get:5 copy:/<>/apt_archive ./ Packages [1206 B]
> Fetched 2994 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:
>  libgmsh4.12t64 : Depends: libocct-data-exchange-7.6 (>= 7.6.3+dfsg1)
>   Depends: libocct-ocaf-7.6 (>= 7.6.3+dfsg1)
> 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/03/19/python-escript_5.6-6_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240319;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240319=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.
--- End Message ---
--- Begin Message ---
Source: python-escript
Source-Version: 5.6-7
Done: Boyuan Yang 

We 

Bug#1053169: Please remove librbd-dev build-depends on all 32 bits arch

[Andreas Beckmann]

Followup-For: Bug #1053169

Migration is currently blocked behind the t64 transition.

Andreas

Bug#1068230: [Debian-on-mobile-maintainers] Bug#1068230: automatic suspend regression with gnome-settings-daemon 46

[Praveen Arimbrathodiyil]

On 3/4/24 8:26 PM, Guido Günther wrote:

Thanks for checking! Please always make sure you check for inhibitors
(`gnome-session-inhibit -l`, `systemd-inhibit -l`) to make sure nothing
left a suspend/sleep inhibitor blocking this.


I noticed it happening for a few days and across multiple reboots (I 
doubt inhibitors persist across reboots). Then switched to plasma mobile 
and it started working. Then I reported the issue and switched back to 
phosh (since plasma mobile was too unstable, many things keep crashing 
all the time) and noticed the regression is gone.


Another thing I noticed is after multiple suspend resume cycles, modem 
stop working and then I need a force power off and reboot with hard ware 
switch (may be this was the actual cause instead of regression). Normal 
shutdown just hangs with the plymouth screen there.


OpenPGP_0x8F53E0193B294B75.asc
Description: OpenPGP public key


OpenPGP_signature.asc
Description: OpenPGP digital signature

Processed: Forward bug 1068158

[Debian Bug Tracking System]

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

> forwarded 1068158 https://bugs.launchpad.net/escript-finley/+bug/2060138
Bug #1068158 [src:python-escript] python-escript: FTBFS: RuntimeError: We do 
not current support different different dpkg-buildflags for C vs C++:
Set Bug forwarded-to-address to 
'https://bugs.launchpad.net/escript-finley/+bug/2060138'.
> thanks
Stopping processing here.

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

Bug#1068230: [Debian-on-mobile-maintainers] Bug#1068230: automatic suspend regression with gnome-settings-daemon 46

[Guido Günther]

Hi Praveen,
On Wed, Apr 03, 2024 at 05:58:41PM +0530, Praveen Arimbrathodiyil via 
Debian-on-mobile-maintainers wrote:
> On Tue, 2 Apr 2024 08:04:12 -0400 =?UTF-8?Q?Jeremy_B=C3=ADcha?=
>  wrote:
> > On Tue, Apr 2, 2024 at 8:03 AM Jeremy Bícha  
> > wrote:
> > >
> > > On Tue, Apr 2, 2024 at 5:31 AM Pirate Praveen  
> > > wrote:
> > > > Recently automatic suspend stopped working. I think this was after 
> > > > gnome settings daemon 46 was available. Some background
> > > > https://salsa.debian.org/Mobian-team/devices/librem5-support/-/issues/7
> > > >
> > > > Not sure if phosh needs some adjustments with recent changes in gnome 
> > > > settings daemon. For now assigned to both.
> > >
> > > Do you have phosh 0.37 or higher installed yet?
> > 
> > Correction: Do you have phosh 0.37.0-2 or 3.7.1-1 installed?
> I still have phosh 0.36.0-1 but auto suspend started working again. So it
> was probably fixed in a recent kernel update.

Thanks for checking! Please always make sure you check for inhibitors
(`gnome-session-inhibit -l`, `systemd-inhibit -l`) to make sure nothing
left a suspend/sleep inhibitor blocking this.

Cheers,
 -- Guido

> 
> Closing this.






> ___
> Debian-on-mobile-maintainers mailing list
> debian-on-mobile-maintain...@alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-on-mobile-maintainers

Processed: Re: Bug#1017729: cinnamon-l10n: Upgrading to 5.4.2-2 breaks cinnamon

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #1017729 [cinnamon-l10n] cinnamon-l10n: Upgrading to 5.4.2-2 breaks cinnamon
Severity set to 'serious' from 'important'

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

Bug#1066942: Debugging xmrig FTBFS on armhf

[Ben Westover]

It seems that the maes flag is automatically added if the ARM_TARGET
CMake var is not set, which happens in cmake/cpu.cmake. The first thing
I saw when I opened that file looked promising:

if (CMAKE_SIZEOF_VOID_P EQUAL 8)
set(XMRIG_64_BIT ON)
add_definitions(-DXMRIG_64_BIT)
else()
set(XMRIG_64_BIT OFF)
endif()

I figured that maybe SIZEOF_VOID_P changed with the t64 transition and
this caused it to get confused and think that we are building on x86_64.
Then I looked closer at the buildd log and saw that XMRIG_64_BIT was
(correctly) set to OFF, which means that this could not be the issue.

The next lines of interest are here:

if (CMAKE_SYSTEM_PROCESSOR MATCHES "^(aarch64|arm64|armv8-a)$")
set(ARM_TARGET 8)
elseif (CMAKE_SYSTEM_PROCESSOR MATCHES 
"^(armv7|armv7f|armv7s|armv7k|armv7-a|armv7l|armv7ve)$")
set(ARM_TARGET 7)
endif()

There are no other functions modifying the ARM_TARGET other than the
option to override this value by manually setting the ARM_V7 variable.
This means that CMAKE_SYSTEM_PROCESSOR must not be matching one of the
armv7* values on buildd and your machine, but does on all of mine. The
build could be fixed by setting ARM_V7 in d/rules on armhf, but I would
prefer properly resolving this issue instead of just working around it.

--
Ben Westover


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1068329: seems xz-utils 5.6.0 and 5.6.1 deb files has the backdoor, please remove both

[ZenWalker]

Package: snapshot.debian.org
Severity: grave

Bug#1067055: Bug#1064810: Bug#1067055: openmpi: error: implicit declaration of function 'OPAL_THREAD_ADD_FETCH64'

[Alastair McKinstry]

On 02/04/2024 21:29, Sebastian Ramacher wrote:

To be honest, I don't see these two changes (changing mpi-defaults to
mpich on 32 bit; breaking 32 bit build of openmpi) to be ready. It'd be
preferable to reinstate a 32-bit compatible pmix and fix openmpi on 32
bit until the time_t transition is done.

Cheers


It looks like libpmix-dev is only used by mpich, openmpi and slurm-wlm.

mpich will be configured not to use pmix on 32-bit systems anyway

slurm-wlm builds ok without pmix; it can be patched to use pmix only on 
64-bit systems.


openmpi in sid (4.1.6-7) has an internal copy of pmix 4.1.2 that it can 
be configured to use.


I can prepare this for openmpi on the debian/trixie branch; to upload 
with a fix for #1067055,


regards

Alastair

--
Alastair McKinstry,
GPG: 82383CE9165B347C787081A2CBE6BB4E5D9AD3A5
ph: +353 87 6847928 e:alast...@mckinstry.ie, im: @alastair:mckinstry.ie

Processed: flexc++: FTBFS on armel, armhf (Segmentation fault)

[Debian Bug Tracking System]

Processing control commands:

> found -1 2.15.00-1
Bug #1068327 [src:flexc++] flexc++: FTBFS on armel, armhf (Segmentation fault)
Marked as found in versions flexc++/2.15.00-1.

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

Bug#1068327: flexc++: FTBFS on armel, armhf (Segmentation fault)

[Kentaro HAYASHI]

Source: flexc++
Severity: serious
Tags: ftbfs
Control: found -1 2.15.00-1
X-Debbugs-Cc: ken...@xdump.org

Dear Maintainer,

flexc++ fails to build on armel, armhf.

FYI:

https://buildd.debian.org/status/fetch.php?pkg=flexc%2B%2B=armel=2.15.00-1=1712127698=0
https://buildd.debian.org/status/fetch.php?pkg=flexc%2B%2B=armhf=2.15.00-1=1712127750=0


Regards,

Bug#1067055: Bug#1064810: Bug#1067055: openmpi: error: implicit declaration of function 'OPAL_THREAD_ADD_FETCH64'

[Alastair McKinstry]

On 02/04/2024 21:29, Sebastian Ramacher wrote:



OpenMPI 5 drops 32-bit support, but otherwise does not change the API/ABI.
So it is technically not a transition, but breaks 32-bit builds.

Doesn't make it better. This is not the time to do that without tests
builds and bugs filed.


The solution is changing mpi-defaults to MPICH for 32-bit archs. MPICH
builds on all archs, but testing all dependencies of the change has not been
tested, and I don't know how you would do that - setting up eg ratt to
rebuild all on 32-bit archs (as everything on 64-bit will not have changed.)

Beside the easy part of chaning mpi-defaults, I count 30 something
packages that have explicit build dependencies on libopenmpi-dev. None
of those packages has bugs filed to change to mpich on 32 bit
architectures.

To be honest, I don't see these two changes (changing mpi-defaults to
mpich on 32 bit; breaking 32 bit build of openmpi) to be ready. It'd be
preferable to reinstate a 32-bit compatible pmix and fix openmpi on 32
bit until the time_t transition is done.

Cheers



I checked with "build-rdeps libopenmpi-dev"  and checked the packages. 
They are mostly false-alarms.


What is needed:

* mpich not to use libpmix for 32-bit archs. I've a patch i'm testing.

* armci-mpi builds on both mpich, openmpi. Needs work to only build on 
openmpi on 64-bit. #10683219


* code-saturne: Uses the default mpi version of hdf5. #1068318

* adios: fix just uploaded.

* vtk9: Depends on libhdf5-openmpi-dev instead of libhdf5-mpi-dev. #1068321

* trilinos: deps on openmpi , but only available on 64-bit systems. No 
change needed


* hdf5: Needs to depend on 64-bit archs for libopenmpi-dev. #1068320

* scalapack: Needs to dep on 64-bit archs only for libopenmpi-dev. #1068322


Regards

Alastair



--
Alastair McKinstry,
GPG: 82383CE9165B347C787081A2CBE6BB4E5D9AD3A5
ph: +353 87 6847928 e: alast...@mckinstry.ie, im: @alastair:mckinstry.ie

Bug#1068325: bisonc++: FTBFS on armel, armhf (override_dh_auto_clean Segmentation fault)

[Kentaro HAYASHI]

Source: bisonc++
Severity: serious
Tags: ftbfs
Control: found -1 6.08.00-1
X-Debbugs-Cc: ken...@xdump.org

Dear Maintainer,

bisonc++ fails to build on armel, armhf.

FYI:

https://buildd.debian.org/status/fetch.php?pkg=bisonc%2B%2B=armel=6.08.00-1=1712127818=0
https://buildd.debian.org/status/fetch.php?pkg=bisonc%2B%2B=armhf=6.08.00-1=1712127698=0

Regards,

Processed: bisonc++: FTBFS on armel, armhf (override_dh_auto_clean Segmentation fault)

[Debian Bug Tracking System]

Processing control commands:

> found -1 6.08.00-1
Bug #1068325 [src:bisonc++] bisonc++: FTBFS on armel, armhf 
(override_dh_auto_clean Segmentation fault)
Marked as found in versions bisonc++/6.08.00-1.

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

Processed: tagging 1066831

[Debian Bug Tracking System]

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

> tags 1066831 + upstream fixed-upstream pending
Bug #1066831 [nbd-client] nbd-server: Crash on -C /dev/null or -C /missing/file
Added tag(s) pending, fixed-upstream, and upstream.
> thanks
Stopping processing here.

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

Bug#1065768: libauthen-krb5-perl: FTBFS on arm{el,hf}: Krb5.xs:1040:17: error: implicit declaration of function ‘krb5_free_address’; did you mean ‘krb5_free_addresses’? [-Werror=implicit-function-dec

[gregor herrmann]

On Sun, 31 Mar 2024 18:41:02 -0700, Russ Allbery wrote:

> In theory, one could delete the pieces of the module that try to do things
> that no one should really be doing from Perl and the rest of it remains
> somewhat useful, but given that upstream has archived the project, I would
> go ahead and remove it.

Thanks, Russ, for the explanations and the recommendation.

And thanks, Sebastian, for filing #1068258.
 

Cheers,
gregor

-- 
 .''`.  https://info.comodo.priv.at -- Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
   `-   BOFH excuse #183:  filesystem not big enough for Jumbo Kernel Patch 

Bug#1068230: marked as done (automatic suspend regression with gnome-settings-daemon 46)

[Debian Bug Tracking System]

Your message dated Wed, 3 Apr 2024 17:58:41 +0530
with message-id <1ff6ab18-3191-4001-a48b-90632ec59...@onenetbeyond.org>
and subject line Re: Bug#1068230: automatic suspend regression with 
gnome-settings-daemon 46
has caused the Debian Bug report #1068230,
regarding automatic suspend regression with gnome-settings-daemon 46
to be marked as done.

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

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


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

Package: gnome-settings-daemon,phosh
severity: serious

Recently automatic suspend stopped working. I think this was after 
gnome settings daemon 46 was available. Some background



Not sure if phosh needs some adjustments with recent changes in gnome 
settings daemon. For now assigned to both.


On kde plasma mobile, automatic suspend still works, so this appears to 
be gnome specific regression.


--- End Message ---
--- Begin Message ---
On Tue, 2 Apr 2024 08:04:12 -0400 =?UTF-8?Q?Jeremy_B=C3=ADcha?= 
 wrote:

On Tue, Apr 2, 2024 at 8:03 AM Jeremy Bícha  wrote:
>
> On Tue, Apr 2, 2024 at 5:31 AM Pirate Praveen  
wrote:
> > Recently automatic suspend stopped working. I think this was after gnome 
settings daemon 46 was available. Some background
> > https://salsa.debian.org/Mobian-team/devices/librem5-support/-/issues/7
> >
> > Not sure if phosh needs some adjustments with recent changes in gnome 
settings daemon. For now assigned to both.
>
> Do you have phosh 0.37 or higher installed yet?

Correction: Do you have phosh 0.37.0-2 or 3.7.1-1 installed?
I still have phosh 0.36.0-1 but auto suspend started working again. So 
it was probably fixed in a recent kernel update.


Closing this.


OpenPGP_0x8F53E0193B294B75.asc
Description: OpenPGP public key


OpenPGP_signature.asc
Description: OpenPGP digital signature
--- End Message ---

Bug#1068230: automatic suspend regression with gnome-settings-daemon 46

[Praveen Arimbrathodiyil]

On Tue, 2 Apr 2024 08:04:12 -0400 =?UTF-8?Q?Jeremy_B=C3=ADcha?= 
 wrote:

On Tue, Apr 2, 2024 at 8:03 AM Jeremy Bícha  wrote:
>
> On Tue, Apr 2, 2024 at 5:31 AM Pirate Praveen  
wrote:
> > Recently automatic suspend stopped working. I think this was after gnome 
settings daemon 46 was available. Some background
> > https://salsa.debian.org/Mobian-team/devices/librem5-support/-/issues/7
> >
> > Not sure if phosh needs some adjustments with recent changes in gnome 
settings daemon. For now assigned to both.
>
> Do you have phosh 0.37 or higher installed yet?

Correction: Do you have phosh 0.37.0-2 or 3.7.1-1 installed?
I still have phosh 0.36.0-1 but auto suspend started working again. So 
it was probably fixed in a recent kernel update.


Closing this.


OpenPGP_0x8F53E0193B294B75.asc
Description: OpenPGP public key


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1067458: marked as done (pulseaudio: FTBFS cpu-volume-test fails)

[Debian Bug Tracking System]

Your message dated Wed, 03 Apr 2024 12:20:44 +
with message-id 
and subject line Bug#1067288: fixed in pulseaudio 16.1+dfsg1-5
has caused the Debian Bug report #1067288,
regarding pulseaudio: FTBFS cpu-volume-test fails
to be marked as done.

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

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


-- 
1067288: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067288
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: orc
Severity: serious
Version: 1:0.4.38-1
Forwarded: https://gitlab.freedesktop.org/gstreamer/orc/-/issues/66
X-Debbugs-CC: pulseau...@packages.debian.org
User: debian-...@lists.debian.org
Usertags: time-t
Control: affects -1 src:pulseaudio
Control: block 1036884 by -1

pulseaudio fails to build from source on a few architectures but it
built successfully recently. The build log suggests that the new
version of orc might have triggered this regression in pulseaudio's
build tests so I filed an upstream bug and am reporting this Debian
bug against orc.

Here's an excerpt from the build log.

test: cpu-volume-test
start time:   20:02:32
duration: 2.06s
result:   exit status 1
command:  src/tests/cpu-volume-test
--- stdout ---
Running suite(s): CPU
66%: Checks: 3, Failures: 0, Errors: 1
../src/tests/cpu-volume-test.c:188:E:svolume:svolume_orc_test:0:
(after this point) Received signal 11 (Segmentation fault)

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

Thank you,
Jeremy Bícha
--- End Message ---
--- Begin Message ---
Source: pulseaudio
Source-Version: 16.1+dfsg1-5
Done: Jeremy Bícha 

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

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

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

Debian distribution maintenance software
pp.
Jeremy Bícha  (supplier of updated pulseaudio package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 03 Apr 2024 08:06:33 -0400
Source: pulseaudio
Built-For-Profiles: noudeb
Architecture: source
Version: 16.1+dfsg1-5
Distribution: unstable
Urgency: medium
Maintainer: Pulseaudio maintenance team 

Changed-By: Jeremy Bícha 
Closes: 1067288
Changes:
 pulseaudio (16.1+dfsg1-5) unstable; urgency=medium
 .
   * Team upload
 .
   [ Sebastien Bacher ]
   * cherrypick a fix for a test failure with orc 0.4.38 (Closes: #1067288)
Checksums-Sha1:
 15f3c34ac1377351f38b08d6be9421149e029e8c 3766 pulseaudio_16.1+dfsg1-5.dsc
 eee8b48efb9596601ce4c4638e7b4eb2534427e1 39372 
pulseaudio_16.1+dfsg1-5.debian.tar.xz
 a4cf8b653b5ca863ea984d7c26ef9d708867f5a4 18976 
pulseaudio_16.1+dfsg1-5_source.buildinfo
Checksums-Sha256:
 055cb62e36acfcda5a83585d984842b256db49ede78023ac6357de0a85d3df13 3766 
pulseaudio_16.1+dfsg1-5.dsc
 963ec1e92bc181df9f5f37f54343ca82de5aff01799a0c968bb5c3e42e410e94 39372 
pulseaudio_16.1+dfsg1-5.debian.tar.xz
 4e1c31e1103e7fea4ec44c177f4875a669baa20041cfceb4d70998cc49830959 18976 
pulseaudio_16.1+dfsg1-5_source.buildinfo
Files:
 b6c38a80634610f16f11d5b79a6c8f5d 3766 sound optional 
pulseaudio_16.1+dfsg1-5.dsc
 916ba4f58da49ca69d55ef0360d84bb1 39372 sound optional 
pulseaudio_16.1+dfsg1-5.debian.tar.xz
 6ff6d86467f0d28669d0bcc90e1a7a33 18976 sound optional 
pulseaudio_16.1+dfsg1-5_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEETQvhLw5HdtiqzpaW5mx3Wuv+bH0FAmYNR30ACgkQ5mx3Wuv+
bH0ftQ/8CNww6Ab6nXWdu7J304G8fSQuTPwN4s8qvqYPJUPDCfGu582QJ6IA8fnZ
B66yUVMw3eUI3hIS5IhB60x22ROMfZVwaLJ3b7KK8oWQNhuVtswxpJ9cwHCaNM20
bhigbkJaKIQrydaSDLo62nIbP3JvLZQg430UozNZWpyQ+M/6BQwPN42uUqoF+NCK
SirVbSX7JnbYwHjN12StULJoQ0zyEzu7vJhpIMPcYV4cL5HE0fk7lZOuU45C8Osp
TjRC4ct1A4wJD4yX6syaAxv6HZ1u4u5lA8r6NBkG/RUQR0Ndf1eyytmlI7xYOCIM
bvrmRKmGJb4E3xhYe7bTaZmrFfr1L8hrkFbYTKKOopnvzgvk5M6q0+WfrwVZNWhR
yPYrQrKICzctfobXk/xfIu6wslGuGrZ/YheZiki53k7NeWSJWMftXR9KWhLmfcj5
NcSY0ODf6juWsWcI8UFMk4PVHLOTemPiAse/SO1KIt4hCLAcuBYN3wiOzarJNCVL
jCN1cAU2O+NS93BKbSpyogVCGHnnkcM/8l/7bMj6vhFNuAST3qtiJcpFGkyOz02z
3QWz9qmETEcZsgz/7z9aXJqpBP3bUpMy3dcQv5lnQjSsa+B2gMY11ZTguDe+wIb0
hvczc+1Zvrlg5T16LDrwBgo8b84Ib+u+MmiCjaqBiRqIkLrdBlw=
=+v2f
-END PGP SIGNATURE-



pgpl_9QcoIgsT.pgp
Description: PGP 

Bug#1066604: marked as done (trickle: FTBFS: configure: error: Couldn't figure out how to access libc)

[Debian Bug Tracking System]

Your message dated Wed, 03 Apr 2024 12:21:06 +
with message-id 
and subject line Bug#1066604: fixed in trickle 1.07-13
has caused the Debian Bug report #1066604,
regarding trickle: FTBFS: configure: error: Couldn't figure out how to access 
libc
to be marked as done.

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

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


-- 
1066604: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066604
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: trickle
Version: 1.07-12
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240313 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> checking for libtirpc... yes
> checking if underscores are needed for symbols... no
> checking if we can access libc without dlopen... no
> checking if we can access libc with libc.so... no
> checking if we can access libc with /usr/lib/libc.so*... no
> configure: error: Couldn't figure out how to access libc
>   tail -v -n \+0 config.log


The full build log is available from:
http://qa-logs.debian.net/2024/03/13/trickle_1.07-12_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240313;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240313=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.
--- End Message ---
--- Begin Message ---
Source: trickle
Source-Version: 1.07-13
Done: Andreas Beckmann 

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

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

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

Debian distribution maintenance software
pp.
Andreas Beckmann  (supplier of updated trickle package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 03 Apr 2024 13:18:05 +0200
Source: trickle
Architecture: source
Version: 1.07-13
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Andreas Beckmann 
Closes: 1066604
Changes:
 trickle (1.07-13) unstable; urgency=medium
 .
   * QA upload.
   * Fix building with -Werror=implicit-function-declaration.
 (Closes: #1066604)
   * Switch B-D from pkg-config to pkgconf.
Checksums-Sha1:
 7076ccb53cc9dbb31e02073c28799c98c5ce8ee7 1888 trickle_1.07-13.dsc
 f3395aee970a4c40f513ba3518abeedea234b1e6 9556 trickle_1.07-13.debian.tar.xz
 a261d6b30540ead463d29c10c861c19b8f197bca 6380 trickle_1.07-13_source.buildinfo
Checksums-Sha256:
 f7c51b47074d4ebfcf13872c9a43f6911bada8b30107daf69e3a5e7b338bb2af 1888 
trickle_1.07-13.dsc
 5882744172c1f0cc4e298ba37612b81a2f5c479ef6007cf7b591348d16ee2f6e 9556 
trickle_1.07-13.debian.tar.xz
 3f1a2e1b70c3dd89ea0444b3ae1b87b30d3eb72be623d79975e76a1ddb661960 6380 
trickle_1.07-13_source.buildinfo
Files:
 d9731a2516183fb40e57a4eb2460956a 1888 net optional trickle_1.07-13.dsc
 b057a33d912767ff84af917238a3b732 9556 net optional 
trickle_1.07-13.debian.tar.xz
 9f718db7f8bfde27b9dd8452d13d20c8 6380 net optional 
trickle_1.07-13_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCAAuFiEE6/MKMKjZxjvaRMaUX7M/k1np7QgFAmYNO48QHGFuYmVAZGVi
aWFuLm9yZwAKCRBfsz+TWentCFh6D/9gVz0F3e2t8bP2vxzLRDoHthiNUoS/mRxS
Ffm01nTjY4/jKxC/kzhjTo2/5qN55vaWVQzTKaCiXDRGvlPdR2IcVfv01QAemlNv
mEB2UYYDqKEx8rEZUxIXnf/IRIPI31YHg9XtpD+qPfrQp/XhDzNGWsEXAjm72sUV
MNny12wWzsbsWJ++yQKiABEfyXqjoRLatMovEyqyQZVEIzAvgw8daPAKgkjGmNTJ
/XMM6vg9gGe8kt3mLHJmOFkrR1AIPnie7dyWqMW1MTGmBi1sisFDQM3umDkm+CaN
0OzZnPx4re8necDmVEAPCe2VuxdZlyEJpJuchnJqdWVwFS1lKcC8oefVYjtehcjK
o1t9nyPsYTx20JAaPN+VlLvadAfu5FntCwv/kgRmXiC9EJ2KUVGur0HKPh9y99ER
YflUMNTyYswLKhTWqxJXdatqrFpzC7jKpTlu569GjuudyoyRDoK6N80JHVLP2sps

Bug#1066319: marked as done (libopendbx: FTBFS: mssql_basic.c:324:21: error: implicit declaration of function ‘dbpoll’ [-Werror=implicit-function-declaration])

[Debian Bug Tracking System]

Your message dated Wed, 03 Apr 2024 12:19:41 +
with message-id 
and subject line Bug#1065767: fixed in libopendbx 1.4.6-17
has caused the Debian Bug report #1065767,
regarding libopendbx: FTBFS: mssql_basic.c:324:21: error: implicit declaration 
of function ‘dbpoll’ [-Werror=implicit-function-declaration]
to be marked as done.

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

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


-- 
1065767: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065767
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libopendbx
Version: 1.4.6-16.1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240313 ftbfs-trixie ftbfs-impfuncdef

Hi,

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

This is most likely caused by a change in dpkg 1.22.6, that enabled
-Werror=implicit-function-declaration. For more information, see
https://wiki.debian.org/qa.debian.org/FTBFS#A2024-03-13_-Werror.3Dimplicit-function-declaration

Relevant part (hopefully):
> /bin/bash ../../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I. 
> -I../..  -DAPINUMBER=10200 -I../../lib -I/usr/include/mysql 
> -I/usr/include/postgresql -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 -fcf-protection -Wall -pedantic -std=c99 -MT 
> libmssqlbackend_la-mssql_basic.lo -MD -MP -MF 
> .deps/libmssqlbackend_la-mssql_basic.Tpo -c -o 
> libmssqlbackend_la-mssql_basic.lo `test -f 'mssql_basic.c' || echo 
> './'`mssql_basic.c
> libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I../.. -DAPINUMBER=10200 
> -I../../lib -I/usr/include/mysql -I/usr/include/postgresql -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 -fcf-protection 
> -Wall -pedantic -std=c99 -MT libmssqlbackend_la-mssql_basic.lo -MD -MP -MF 
> .deps/libmssqlbackend_la-mssql_basic.Tpo -c mssql_basic.c  -fPIC -DPIC -o 
> .libs/libmssqlbackend_la-mssql_basic.o
> mssql_basic.c: In function ‘mssql_odbx_result’:
> mssql_basic.c:324:21: error: implicit declaration of function ‘dbpoll’ 
> [-Werror=implicit-function-declaration]
>   324 | if( dbpoll( dbproc, ms, ,  ) == FAIL ) 
> { return -ODBX_ERR_BACKEND; }
>   | ^~
> mssql_basic.c: In function ‘mssql_err_handler’:
> mssql_basic.c:758:38: warning: the comparison will always evaluate as ‘false’ 
> for the address of ‘errmsg’ will never be NULL [-Waddress]
>   758 | if( tc == NULL || tc->errmsg == NULL )
>   |  ^~
> In file included from mssql_basic.h:11,
>  from mssql_basic.c:11:
> mssqlbackend.h:46:14: note: ‘errmsg’ declared here
>46 | char errmsg[MSSQL_MSGLEN];
>   |  ^~
> mssql_basic.c: In function ‘mssql_msg_handler’:
> mssql_basic.c:791:38: warning: the comparison will always evaluate as ‘false’ 
> for the address of ‘errmsg’ will never be NULL [-Waddress]
>   791 | if( tc == NULL || tc->errmsg == NULL )
>   |  ^~
> mssqlbackend.h:46:14: note: ‘errmsg’ declared here
>46 | char errmsg[MSSQL_MSGLEN];
>   |  ^~
> cc1: some warnings being treated as errors
> make[4]: *** [Makefile:515: libmssqlbackend_la-mssql_basic.lo] Error 1


The full build log is available from:
http://qa-logs.debian.net/2024/03/13/libopendbx_1.4.6-16.1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240313;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240313=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.
--- End Message ---
--- Begin Message ---
Source: libopendbx
Source-Version: 1.4.6-17
Done: Andreas Beckmann 

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

A summary of 

Bug#1065767: marked as done (libopendbx: FTBFS on arm{el,hf}: mssql_basic.c:324:21: error: implicit declaration of function ‘dbpoll’ [-Werror=implicit-function-declaration])

[Debian Bug Tracking System]

Your message dated Wed, 03 Apr 2024 12:19:41 +
with message-id 
and subject line Bug#1065767: fixed in libopendbx 1.4.6-17
has caused the Debian Bug report #1065767,
regarding libopendbx: FTBFS on arm{el,hf}: mssql_basic.c:324:21: error: 
implicit declaration of function ‘dbpoll’ 
[-Werror=implicit-function-declaration]
to be marked as done.

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

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


-- 
1065767: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065767
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libopendbx
Version: 1.4.6-16.1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org

https://buildd.debian.org/status/fetch.php?pkg=libopendbx=armhf=1.4.6-16.1=1709139710=0

libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I../.. -DAPINUMBER=10200 
-I../../lib -I/usr/include/mysql -I/usr/include/postgresql -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 -Wall -pedantic -std=c99 -MT 
libmssqlbackend_la-mssql_basic.lo -MD -MP -MF 
.deps/libmssqlbackend_la-mssql_basic.Tpo -c mssql_basic.c  -fPIC -DPIC -o 
.libs/libmssqlbackend_la-mssql_basic.o
mssql_basic.c: In function ‘mssql_odbx_result’:
mssql_basic.c:324:21: error: implicit declaration of function ‘dbpoll’ 
[-Werror=implicit-function-declaration]
  324 | if( dbpoll( dbproc, ms, ,  ) == FAIL ) { 
return -ODBX_ERR_BACKEND; }
  | ^~
mssql_basic.c: In function ‘mssql_err_handler’:
mssql_basic.c:758:38: warning: the comparison will always evaluate as ‘false’ 
for the address of ‘errmsg’ will never be NULL [-Waddress]
  758 | if( tc == NULL || tc->errmsg == NULL )
  |  ^~
In file included from mssql_basic.h:11,
 from mssql_basic.c:11:
mssqlbackend.h:46:14: note: ‘errmsg’ declared here
   46 | char errmsg[MSSQL_MSGLEN];
  |  ^~
mssql_basic.c: In function ‘mssql_msg_handler’:
mssql_basic.c:791:38: warning: the comparison will always evaluate as ‘false’ 
for the address of ‘errmsg’ will never be NULL [-Waddress]
  791 | if( tc == NULL || tc->errmsg == NULL )
  |  ^~
mssqlbackend.h:46:14: note: ‘errmsg’ declared here
   46 | char errmsg[MSSQL_MSGLEN];
  |  ^~
cc1: some warnings being treated as errors
make[4]: *** [Makefile:515: libmssqlbackend_la-mssql_basic.lo] Error 1

Cheers
-- 
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Source: libopendbx
Source-Version: 1.4.6-17
Done: Andreas Beckmann 

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

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

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

Debian distribution maintenance software
pp.
Andreas Beckmann  (supplier of updated libopendbx package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 03 Apr 2024 13:07:55 +0200
Source: libopendbx
Architecture: source
Version: 1.4.6-17
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Andreas Beckmann 
Closes: 1015508 1051751 1065767
Changes:
 libopendbx (1.4.6-17) unstable; urgency=medium
 .
   * QA upload.
   * Fix building with -Werror=implicit-function-declaration.
 (Closes: #1065767)
   * Update .symbols file.
   * Set Rules-Requires-Root: no.
   * Switch to debhelper-compat (= 13).
   * Switch to dh.
   * Enable all hardening flags.
   * Update .symbols for loong64, thanks to yalingfang.  (Closes: #1051751)
   * Mark some symbols as optional if LTO is used.  (Closes: #1015508)
Checksums-Sha1:
 6982206992962d08cb48e97e9e2e4f30b6093eb4 2799 libopendbx_1.4.6-17.dsc
 f523b38346894224146a51fcfe81f7150de2f056 78016 
libopendbx_1.4.6-17.debian.tar.xz
 39d73f3f2f51c3e3642ff4e99685d827fb37360d 9381 
libopendbx_1.4.6-17_source.buildinfo
Checksums-Sha256:
 

Processed: Bug#1067288 marked as pending in pulseaudio

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1067288 [src:pulseaudio] pulseaudio: FTBFS on x86: cpu-volume-test fails, 
segfault in svolume_orc_test
Bug #1067458 [src:pulseaudio] pulseaudio: FTBFS cpu-volume-test fails
Added tag(s) pending.
Added tag(s) pending.

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

Bug#1067288: marked as pending in pulseaudio

[Jeremy Bicha]

Control: tag -1 pending

Hello,

Bug #1067288 in pulseaudio reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/pulseaudio-team/pulseaudio/-/commit/9e05702770bf05c1745f3475f0ddd6b98e4ad62c


cherrypick a fix for a test failure with orc 0.4.38

Closes: #1067288


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1067288