Bug#1074558: mariadb: FTBFS on sparc64: Multiple tests crash / time out

[John Paul Adrian Glaubitz]

Hello Otto,

On Tue, 2024-07-02 at 21:10 -0700, Otto Kekäläinen wrote:
> I recently uploaded MariaDB 11.4 to Debian, and it seems it regressed
> on sparc64.
> 
> Are there any sparc64 hackers interested in taking a look?
> 
> The build itself passed and most of the post-build passes, but some
> tests cause the database to crash. Stack traces are visible in the
> logs:
> 
> https://buildd.debian.org/status/fetch.php?pkg=mariadb&arch=sparc64&ver=1%3A11.4.2-2&stamp=1719891893&raw=0
> https://buildd.debian.org/status/logs.php?pkg=mariadb&arch=sparc64

I would suggest rerun the build plus testsuite on the porterbox stadler
with glibc debug packages installed in the chroot so you can get a more
usable backtrace.

Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer
`. `'   Physicist
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

Bug#1071523: r-cran-spatstat.geom: autopkgtest regression in testing

[Dirk Eddelbuettel]

On 3 July 2024 at 07:18, Andreas Tille wrote:
| Am Tue, Jul 02, 2024 at 09:32:43PM + schrieb Graham Inggs:
| > > We did not implemented any hooks to realise this yet.
| > 
| > Wouldn't removing the following line from debian/control do it?
| > 
| > Testsuite: autopkgtest-pkg-r
| 
| Well, sure.  But our tooling will add this for the next upstream version
| again and if the problem is not solved otherwise it will re-appear.  I
| will upload this change but I would prefer understanding the issue and
| provide a real fix.

I have to add my usual reminder here that this package of course tests
flawlessly against all other CRAN package it uses if those are kept in sync
too:

https://cran.r-project.org/web/checks/check_results_spatstat.geom.html

This is most likely once again a self-imposed problem. In aggregate, and at
least in my eyes, this wastes too much time of too many people. (Ditto with
autopkgtests on i386 and alike no supported upstream).

Dirk

 
| Kind regards
| Andreas.
| 
| -- 
| https://fam-tille.de
| 

-- 
dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org

Bug#1074784: wminput: PyCapsule_GetPointer called with incorrect name

[PJ Weisberg]

Package: wminput
Version: 0.6.91-7.1+b2
Severity: important

Dear Maintainer,

When I start wminput, after I put the Wiimote in discoverable mode
wminput prints `ValueError: PyCapsule_GetPointer called with incorrect
name` and immediately exits.

I downloaded the source package and edited `python/Wiimote.c` to pass
NULL into PyCapsule_GetPointer instead of "dynamr", and that worked
when I built and installed it.

I don't know enough to know whether that's actually the correct
solution.  I just tried passing in a different value for the parameter
that the error message said was wrong, and PyCapsule_GetName returned
null, so I passed null and it worked.  That's the full extent of the
thought I put into it.  Someone more knowledgeable than me should
figure out why the capsule's name isn't what was expected.

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

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

Versions of packages wminput depends on:
ii  libbluetooth3 5.71-1+b2
ii  libc6 2.38-13
pn  libcwiid1 
pn  libcwiid1t64  
ii  libpython3.11t64 [libpython3.11]  3.11.9-1
ii  libpython3.12t64  3.12.4-1
pn  python3-cwiid 

wminput recommends no packages.

wminput suggests no packages.

Bug#1071523: r-cran-spatstat.geom: autopkgtest regression in testing

[Andreas Tille]

Am Tue, Jul 02, 2024 at 09:32:43PM + schrieb Graham Inggs:
> > We did not implemented any hooks to realise this yet.
> 
> Wouldn't removing the following line from debian/control do it?
> 
> Testsuite: autopkgtest-pkg-r

Well, sure.  But our tooling will add this for the next upstream version
again and if the problem is not solved otherwise it will re-appear.  I
will upload this change but I would prefer understanding the issue and
provide a real fix.

Kind regards
Andreas.

-- 
https://fam-tille.de

Bug#1074558: mariadb: FTBFS on sparc64: Multiple tests crash / time out

[Otto Kekäläinen]

Hi!

I recently uploaded MariaDB 11.4 to Debian, and it seems it regressed
on sparc64.

Are there any sparc64 hackers interested in taking a look?

The build itself passed and most of the post-build passes, but some
tests cause the database to crash. Stack traces are visible in the
logs:

https://buildd.debian.org/status/fetch.php?pkg=mariadb&arch=sparc64&ver=1%3A11.4.2-2&stamp=1719891893&raw=0
https://buildd.debian.org/status/logs.php?pkg=mariadb&arch=sparc64


Example:

main.unsafe_binlog_innodbw2 [ fail ]  timeout after 7200 seconds
Test ended at 2024-07-02 03:42:48

Test case timeout after 7200 seconds

== /<>/builddir/mysql-test/var/2/log/unsafe_binlog_innodb.log ==
connection h;
set autocommit = 0;
insert into t8 (select * from t2 for update);
connection i;
set autocommit = 0;
update t9 set e = (select b from t2 where a = d for update);
connection j;
set autocommit = 0;
create table t10(a int not null, b int, primary key(a)) select * from
t2 for update;
connection b;
ERROR HY000: Lock wait timeout exceeded; try restarting transaction
connection c;
ERROR HY000: Lock wait timeout exceeded; try restarting transaction
connection d;
ERROR HY000: Lock wait timeout exceeded; try restarting transaction
connection e;
ERROR HY000: Lock wait timeout exceeded; try restarting transaction
connection f;
ERROR HY000: Lock wait timeout exceeded; try restarting transaction
connection g;

 == /<>/builddir/mysql-test/var/2/tmp/analyze-timeout-mysqld.1.err
==
mysqltest: Could not open connection 'default' after 500 attempts:
2002 Can't connect to local server through socket
'/<>/builddir/mysql-test/var/tmp' (61)


 - found 'core' (1/1)
Core generated by '/<>/builddir/sql/mariadbd'
Output from gdb follows. The first stack trace is from the failing thread.
The following stack traces are from all threads (so the failing one is
duplicated).
--

warning: Can't open file anon_inode:[io_uring] which was expanded to
anon_inode:[io_uring] during file-backed mapping note processing

warning: Can't open file anon_inode:[io_uring] which was expanded to
anon_inode:[io_uring] during file-backed mapping note processing

warning: Can't open file
/<>/builddir/mysql-test/var/2/mysqld.1/data/tc.log during
file-backed mapping note processing
[New LWP 969330]
[New LWP 969347]
[New LWP 969342]
[New LWP 969408]
[New LWP 969383]
[New LWP 971740]
[New LWP 969373]
[New LWP 972862]
[New LWP 972863]
[New LWP 972864]
[New LWP 971041]
[New LWP 972865]
[New LWP 972866]
[New LWP 972869]
[New LWP 969345]
[New LWP 972870]
[New LWP 969377]
[New LWP 972868]
[New LWP 969346]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/sparc64-linux-gnu/libthread_db.so.1".
Core was generated by `/<>/builddir/sql/mariadbd
--defaults-group-suf'.
Program terminated with signal SIGABRT, Aborted.
#0  0xfff80001026928c0 in ?? () from /lib/sparc64-linux-gnu/libc.so.6
[Current thread is 1 (Thread 0xfff8000100036ca0 (LWP 969330))]
#0  0xfff80001026928c0 in ?? () from /lib/sparc64-linux-gnu/libc.so.6
#1  0x01a85b74 in handle_fatal_signal (sig=6) at
./sql/signal_handler.cc:357
Backtrace stopped: Cannot access memory at address 0xf0

Thread 19 (Thread 0xfff800010e0018c0 (LWP 969346)):
#0  0xfff80001027092dc in syscall () from /lib/sparc64-linux-gnu/libc.so.6
No symbol table info available.
#1  0xfff8000100902ff4 in ?? () from /lib/sparc64-linux-gnu/liburing.so.2
No symbol table info available.
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Thread 18 (Thread 0xfff8000102cea8c0 (LWP 972868)):
#0  0xfff800010268cc4c in ?? () from /lib/sparc64-linux-gnu/libc.so.6
No symbol table info available.
#1  0xfff8000102690060 in pthread_cond_timedwait () from
/lib/sparc64-linux-gnu/libc.so.6
No symbol table info available.
#2  0x016f9dac in psi_cond_timedwait (that=0x100019f5db8
, mutex=0x100019f5e28 ,
abstime=0xfff8000102ce9a40, file=0x10001049368 "./sql/thread_cache.h",
line=176) at ./mysys/my_thr_init.c:611
state = {m_flags = 256, m_operation = (unknown: 0x93ea64),
m_cond = 0x70001, m_mutex = 0xfff80001008d40c0, m_thread =
0xfff80001038c2d40, m_timer_start = 1719884508841233192, m_timer =
0x668376fc, m_wait = 0x22ba6f63}
locker = 0x0
result = 
#3  0x0193efdc in inline_mysql_cond_timedwait
(src_file=0x10001049368 "./sql/thread_cache.h", src_line=176,
abstime=0xfff8000102ce9a40, mutex=, that=) at ./include/mysql/psi/mysql_thread.h:1086
No locals.
#4  Thread_cache::park (this=) at ./sql/thread_cache.h:176
error = 
abstime = {tv_sec = 1719892008, tv_nsec = 582643000}
connect = 0x0
flushed = 
abstime = 
connect = 
flushed = 
_now_ = 
error = 
#5  do_handle_one_connection (connect=,
put_in_cache=true) at ./sql/sql_connect.cc:1450
create_user = 
thr_create_utime = 
thd = 0xfff800017c000c68
#6  0x0193f0cc in handle_one_connection (arg=)

Bug#1074670: Fwd: [debian-mysql] Processed: Re: amarok: FTBFS: unsatisfiable build-dependency: libmariadb-dev (= 1:10.11.8-1) but 1:11.4.2-1 is to be installed

[Otto Kekäläinen]

Hi!

This https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074670 is a
result of the MariaDB build with the embedded server using excessive
disk space.

I have filed reverting MR at
https://salsa.debian.org/mariadb-team/mariadb-server/-/merge_requests/89
and asked upstream for advice in
https://lists.mariadb.org/hyperkitty/list/develop...@lists.mariadb.org/thread/Y7J2OEUMEZEGVD23L5K5KTBABXF3H6VS/

Bug#1056293: fixed in gettext 0.22.5-1

[Vladimir Petko]

Control: reopen 1056293

Hi,

I have done a rebuild of ssl-utils-clojure[1] and it failed to build
with default Java 21 against gettext 0.22.5-1.

Best Regards,
 Vladimir.

[1] 
https://launchpad.net/~vpa1977/+archive/ubuntu/plusone/+sourcepub/16248843/+listing-archive-extra

Bug#1074783: efax: Log directory moved from /var/log to /var/loog

[Bill Brelsford]

Package: efax
Version: 1:0.9a-22
Severity: normal

Dear Maintainer,

The upgrade to 1:0.9a-22 resulted in the removal of /var/log/efax
and creation of /var/loog and /var/loog/efax. 

Bill

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

Kernel: Linux 6.9.7-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: sysvinit (via /sbin/init)
LSM: AppArmor: enabled

Versions of packages efax depends on:
ii  debconf [debconf-2.0]  1.5.86
ii  libc6  2.38-13
ii  libpaper-utils 1.1.29+b1
ii  make   4.3-4.1

efax recommends no packages.

Versions of packages efax suggests:
ii  imagemagick  8:6.9.13.12+dfsg1-1
ii  imagemagick-6.q16 [imagemagick]  8:6.9.13.12+dfsg1-1
ii  xloadimage   4.1-25+b3

-- Configuration Files:
/etc/efax.rc changed [not included]

-- no debconf information

Bug#1072708: openafs: src/rx[gen] contains SUN RPC code under the original license

[Benjamin Kaduk]

Hi Bastian,

Sorry for the slow reply.  Life has throwna a lot of things at me this
month.

On Thu, Jun 06, 2024 at 10:17:33PM +0200, Bastian Germann wrote:
> 
> OpenAFS includes the Sun RPC code under the original, non-free license.
> That code was relicensed by Oracle under a BSD license (see 
> https://spot.livejournal.com/315383.html).
> 
> I have filed an upstream bug (see forwarded URL), which has a response
> linking a previous draft submission to make use of that relicensing, which
> is blocked by people agreeing to their code (which has substantial changes
> to the relicense glibc or FreeBSD copies) being relicensed.
> 
> Maybe replacing it without those additional changes is possible in Debian.

I do not see how it would be possible to replace this code in Debian before
upstream can do so; this code is a core part of the functionality of the
software and the files cannot be relicensed without the permission of all
copyright holders.

I am also a bit confused at why you chose to file this as severity: serious
-- could you please clarify what part of policy is being violated or how it
makes the package unsuitable for release?

Thanks,

Ben

Bug#1074670: amarok: FTBFS: unsatisfiable build-dependency: libmariadb-dev (= 1:10.11.8-1) but 1:11.4.2-1 is to be installed

[Pino Toscano]

Source: amarok
Followup-For: Bug #1074670
X-Debbugs-Cc: pkg-mysql-ma...@lists.alioth.debian.org
Control: reassign -1 src:mariadb mariadb/1:11.4.2-1
Control: retitle -1 please build again the embedded server, needed by amarok
Control: affects -1 + src:amarok

Hi,

this dependency issue happens because the upload of mariadb 1:11.4.2-1
drops the embedded server [1] with not exactly clear reasons:
| * Stop building the embedded server to save disk space

The embedded server is needed by Amarok, newly reintroduced into the
Debian archive. Strictly speaking, Amarok can be built without the
embedded server, however it will require a real MySQL/MariaDB server
available and usable, which is not exactly the best experience for
"desktop users".

Hence: dear MariaDB packagers, please reintroduce the embedded server
in Debian, thanks.

[1] 
https://tracker.debian.org/news/1540944/accepted-mariadb-11142-1-source-amd64-all-into-unstable/

Thanks,
-- 
Pino

Bug#1074782: sqitch: autopkgtests failing with new MariaDB 11.4

[otto]

Package: sqitch
Version: 1.4.1-1
Severity: important

MariaDB 1:11.4.2-1 was recently uploaded to Debian. MariaDB 11.4 and MySQL 8.4
are slowly diverging more and more.

As a result of the new version the sqitch autopkgtests are currently failing,
but the reason is a bit unclear.

Could you please assist in reading what the actual error in the logs is?

https://ci.debian.net/packages/s/sqitch/testing/amd64/48409017/

All tests seem to say 'ok' and searching for 'not ok' yields zero results.

Log ends with:

 Test Summary Report
 t/sqlite.t(Wstat: 65280 (exited 255) Tests: 127 Failed: 0)
 Non-zero exit status: 255
   Parse errors: No plan found in TAP output
 Files=50, Tests=7508, 28 wallclock secs ( 0.50 usr  0.12 sys + 20.46 cusr  
5.14 csys = 26.22 CPU)
 Result: FAIL

Bug#1074781: request-tracker5/4: autopkgtests don't work directly with new MariaDB 11.4

[otto]

Package: request-tracker5
Version: 5.0.5+dfsg-2
Severity: important

MariaDB 1:11.4.2-1 was recently uploaded to Debian. MariaDB 11.4 and MySQL 8.4
are slowly diverging more and more.

In MariaDB 11.4 the 'mysql' naming in filenames has shifted towards 'mariadb'.
Hence the request-tracker5 (both version 5 and 4) autopkgtests are currently
failing, but the reason is a bit unclear.

Could you please assist in reading what the actual error in the logs is?

https://ci.debian.net/packages/r/request-tracker5/testing/armel/48409176/
https://ci.debian.net/packages/r/request-tracker4/testing/armel/48409175/

There are 60 tests that say 'not ok' but it is hard to figure out which one of
them is new, and why they are failing with MariaDB 11.4.

Bug#1074780: pdns-backend-mysql: autopkgtests use of mysql* commands don't work directly with new MariaDB 11.4 with mariadb-* commands

[otto]

Package: pdns-backend-mysql
Version: 4.9.1-1
Severity: important

MariaDB 1:11.4.2-1 was recently uploaded to Debian. MariaDB 11.4 and MySQL 8.4
are slowly diverging more and more.

In MariaDB 11.4 the 'mysql' naming in filenames has shifted towards 'mariadb'.
Hence the pdns autopkgtests are currently failing on errors such as:

  + /usr/bin/mysqld_safe
  /tmp/autopkgtest-lxc.pxhhitlw/downtmp/build.JDD/src/debian/tests/smoke-mysql: 
line 7: /usr/bin/mysqld_safe: No such file or directory
  mysqladmin: connect to server at 'localhost' failed
  error: 'Can't connect to local server through socket 
'/run/mysqld/mysqld.sock' (2)'
  Check that mariadbd is running and that the socket: '/run/mysqld/mysqld.sock' 
exists!

Full log at https://ci.debian.net/packages/p/pdns/testing/amd64/48409004/


Would the pdns maintainers be open to update the script to use 'mariadb' 
everywhere so the autopkgtests pass with MariaDB 11.4 in Debian?

Or perhaps clone the `pdns-backend-mysql` into `pdns-backend-mariadb` that uses 
`mariadb*` commands?

Bug#1070171: RFS: mangl/1.1.5-1 [ITP: #1070171] -- Graphical man page viewer

[James Montgomery]

Dear mentors,

After cleaning up some novice duplicate bug mistakes ...

I am looking for a sponsor for my package "mangl":

 * Package name: mangl
   Version : 1.1.5-1
   Upstream Author : Ziga Lenarcic
 * URL : https://github.com/zigalenarcic/mangl
 * License : BSD-2-Clause
 * Vcs : https://salsa.debian.org/monty/mangl
   Section : utils

The source builds the following binary packages:

  mangl - Graphical man page viewer based on the mandoc library

To access further information about this package, please visit the
following URL:

  https://mentors.debian.net/package/mangl/

Alternatively, you can download the package with 'dget' using this command:

  dget -x
https://mentors.debian.net/debian/pool/main/m/mangl/mangl_1.1.5-1.dsc

Changes for the initial release:

 mangl (1.1.5-1) unstable; urgency=medium
 .
   * Initial packaging (Closes: #1070171)
   * Change distribution to unstable for upload.

Regards,
--
  James Montgomery

>

Bug#1070171: RFS: mangl/1.1.5-1 [ITP: #1070171] -- Graphical man page viewer

[James Montgomery]

Dear mentors,

After cleaning up some novice duplicate bug mistakes ...

I am looking for a sponsor for my package "mangl":

 * Package name: mangl
   Version : 1.1.5-1
   Upstream Author : Ziga Lenarcic
 * URL : https://github.com/zigalenarcic/mangl
 * License : BSD-2-Clause
 * Vcs : https://salsa.debian.org/monty/mangl
   Section : utils

The source builds the following binary packages:

  mangl - Graphical man page viewer based on the mandoc library

To access further information about this package, please visit the
following URL:

  https://mentors.debian.net/package/mangl/

Alternatively, you can download the package with 'dget' using this command:

  dget -x
https://mentors.debian.net/debian/pool/main/m/mangl/mangl_1.1.5-1.dsc

Changes for the initial release:

 mangl (1.1.5-1) unstable; urgency=medium
 .
   * Initial packaging (Closes: #1070171)
   * Change distribution to unstable for upload.

Regards,
--
  James Montgomery

Bug#1074779: Fixing the problem

[peter]

Looking at the netconsole-setup shell script, the problem arises when
the kernel doesn't know (yet) about the destination address.
If you add a ping before the neighbour lookup it'll probably work.

So:
--- /usr/sbin/netconsole-setup  2024-06-22 08:56:28.0 +1000
+++ /var/tmp/netconsole-setup   2024-07-03 08:46:43.255865757 +1000
@@ -35,6 +35,7 @@
 local address="$1"
 local from_interface="$2"
 
+/usr/bin/ping -c 1 "$address" > /dev/null 2>&1
 mac=$(ip -o neigh show to "$address" dev "$from_interface" | grep -oE 
"lladdr [^ ]*" | cut -d ' ' -f 2)
 if test -z "$mac"; then
 # Run arping to determine the MAC address for the given IP address

Bug#1074776: coreutils: $'\t' and $'\123' escapes are real now

[Pádraig Brady]

On 02/07/2024 21:48, наб wrote:

Package: coreutils
Version: 9.1-1
Version: 9.4-3
Severity: minor

Dear Maintainer,

printf(1) says:
   escaping non-printable characters with the proposed POSIX $'' syntax.
this syntax is real as of Issue 8 (POSIX.1-2024).

ls is probably also affected by this since it outputs these.


Fixed upstream with:
https://github.com/coreutils/coreutils/commit/50e85d481

thanks,
Pádraig

Bug#1074633: qt6-base: upgrading libqt6core6t64 removes qpdfview and wireshark instead of upgrading them

[Vincent Lefevre]

Hi Patrick,

On 2024-07-03 00:30:55 +0200, Patrick Franz wrote:
> this seems more a problem of apt than of Qt.

Even if apt could be improved, this would still be a bug in the
concerned packages, which must declare adequate relationships
to allow the upgrade. See

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1059068#15

where David Kalnischkies says

  You should really know this by now as that isn't your first report,
  but okay: Upgrade problems are NEVER a problem to be solved in apt,
  they are ALWAYS a problem in the involved packages. NO EXCEPTIONS.

> For some reason, apt is not able to resolve the dependencies when you 
> only want to upgrade libqt6core6t64, but is able to do so when you want 
> to upgrade libqt6core6t64 and wireshark.
> 
> To me, that means that the dependencies in Qt are correct (that it wants 
> to replace some libqt6...t64 packages with non-t64 versions is the 
> correct solution).

See above. It seems that the issue is that the upgrade of
libqt6core6t64 alone seems to remove other Qt packages instead
of upgrading them.

In particular, "apt install libqt6core6t64" wants to remove
qt6-wayland, but if I try "apt install libqt6core6t64 qt6-wayland",
then the upgrade is fine. So there seems to be really something
wrong with the Qt package relationships.

> Have you tried upgrading just libqt6core6t64 with aptitude ?

aptitude doesn't want to do anything. aptitude is often much worse
(but much safer as it will normally not break "Recommends" without
confirmation). And sometimes it can't even handle simple cases,
where it has only some dependencies to install.

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

Bug#1074779: netconsole: IP6 not supported

[Peter Chubb]

Package: netconsole
Version: 0.3.1-3
Severity: normal
Tags: ipv6

Dear Maintainer,

 I do
netconsole-setup syslog-host
 and see
arping: 2001:0db8:1000:2000::9: Address family for hostname not 
supported
netconsole-setup: syslog-host: Cannot resolve MAC address of 
2001:0db8:1000:2000::9

(I've changed the IP addresses to the example range for privacy)

I believe the netconsole-setup program should either support ipv6 
or drop back to ipv4

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

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

Versions of packages netconsole depends on:
ii  init-system-helpers  1.66
ii  iproute2 6.9.0-1
ii  iputils-arping   3:20240117-1
ii  kmod 32+20240611-1

netconsole recommends no packages.

netconsole suggests no packages.

-- no debconf information

Bug#1074778: zlint: remove Depends: golang-github-pelletier-go-toml-dev, golang-github-zmap-zcrypto-dev

[Paul Wise]

Package: zlint
Version: 3.6.2-3
Severity: wishlist

The zlint binary package has Depends on two -dev packages:

   golang-github-pelletier-go-toml-dev
   golang-github-zmap-zcrypto-dev

Please remove these two Depends from the zlint binary package.

These aren't necessary since the binary package does not contain any
source code nor a compiler nor anything else that would use them.

They also pull in several other -dev packages via their Depends.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#1074633: qt6-base: upgrading libqt6core6t64 removes qpdfview and wireshark instead of upgrading them

[Patrick Franz]

Hi Vincent,

this seems more a problem of apt than of Qt.

For some reason, apt is not able to resolve the dependencies when you 
only want to upgrade libqt6core6t64, but is able to do so when you want 
to upgrade libqt6core6t64 and wireshark.

To me, that means that the dependencies in Qt are correct (that it wants 
to replace some libqt6...t64 packages with non-t64 versions is the 
correct solution).

Have you tried upgrading just libqt6core6t64 with aptitude ?

I'm inclined to reassign this bug to apt as the dependencies can clearly 
be resolved and IMO this is down to the resolver.


-- 
Med vänliga hälsningar

Patrick Franz

Bug#1074777: RFS: mangl/1.1.5-1 [ITP: #1074594] -- Graphical man page viewer

[James Montgomery]

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package "mangl":

 * Package name: mangl
   Version : 1.1.5-1
   Upstream Author : Ziga Lenarcic
 * URL : https://github.com/zigalenarcic/mangl
 * License : BSD-2-Clause
 * Vcs : https://salsa.debian.org/monty/mangl
   Section : utils

The source builds the following binary packages:

  mangl - Graphical man page viewer based on the mandoc library

To access further information about this package, please visit the
following URL:

  https://mentors.debian.net/package/mangl/

Alternatively, you can download the package with 'dget' using this command:

  dget -x https://mentors.debian.net/debian/pool/main/m/mangl/mangl_1.1.5-1.dsc

Changes for the initial release:

 mangl (1.1.5-1) unstable; urgency=medium
 .
   * Initial packaging (Closes: #1070171)
   * Change distribution to unstable for upload.

Regards,
-- 
  James Montgomery

Bug#1071523: r-cran-spatstat.geom: autopkgtest regression in testing

[Graham Inggs]

On Tue, 2 Jul 2024 at 19:49, Andreas Tille  wrote:
> > Is it possible to skip the pkg-r-autopkgtest for this package?
>
> We did not implemented any hooks to realise this yet.

Wouldn't removing the following line from debian/control do it?

Testsuite: autopkgtest-pkg-r

debian-bugs-dist@lists.debian.org

[Patrick Franz]

Hi,

On Tue, 2 Jul 2024 19:39:27 +0200 Marco Mattiolo 
 wrote:
> Hi Santiago,
> 
> I'm the maintainer of plasma-mobile package in Debian, plus some of  
> the related apps. At the moment, the present bug keeps meta-plasma-
> mobile metapackage out of trixie, thus letting the building of Mobian 
> plasma-mobile images to fail [1]. As I wrote in the previous message, 
> looking into buildd and reproducible-builds, I thought this to be 
> solved, but from your attachment I see I shouldn't have assumed.
> 
> I'm not the maintainer of wacomtablet, so I'm not sure what to touch 
> if tests are still failing. I see in your attachment that the error
> message is always the same as in the original report, then I'd try
> e.g. [2] that I see is not implemented in d/rules for wacomtablet,
> but maybe it's just better to wait for the new version of wacomtablet
> (6.1.0-1 now in experimental) to be uploaded to sid and check how that
> new version behaves.

I don't have the resources to dig into why the tests are failing, but I 
could disable them for the time being if wacomtablet is a blocker for 
something right now.

We will definitely revisit this once the new version in exp (now part of 
Plasma 6) can be compiled there.


-- 
Med vänliga hälsningar

Patrick Franz

Bug#1074776: coreutils: $'\t' and $'\123' escapes are real now

[наб]

Package: coreutils
Version: 9.1-1
Version: 9.4-3
Severity: minor

Dear Maintainer,

printf(1) says:
  escaping non-printable characters with the proposed POSIX $'' syntax.
this syntax is real as of Issue 8 (POSIX.1-2024).

ls is probably also affected by this since it outputs these.

Best,
наб

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

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

Versions of packages coreutils depends on:
ii  libacl1   2.3.2-1
ii  libattr1  1:2.5.2-1
ii  libc6 2.38-13
ii  libgmp10  2:6.3.0+dfsg-2
ii  libselinux1   3.5-2
ii  libssl3t64 [libssl3]  3.1.5-1.1

coreutils recommends no packages.

coreutils suggests no packages.

-- no debconf information


signature.asc
Description: PGP signature

Bug#1074775: heimdal: please add support for include directives

[Andreas Hasenack]

Package: heimdal
Version: 7.8.git20221117.28daf24+dfsg-5
Severity: normal

Dear Maintaner,

please add support for include and includedir directives in krb5.conf
to heimdal. This has been committed upstream already[1], and is
supported by MIT Kerberos.

Missing this feature is preventing closing a kerberos-configs[2] bug,
because since krb5.conf is shared between heimdal and MIT kerberos,
both need to support these inclusion directives.

The upstream commit[1] landed in 2017, but is not yet part of any
heimdal release, and it's unclear when such new release will happen.
The patch applies without changes to the current version in debian
unstable. I understand adding it adds risk to the package in Debian,
but not having it is also preventing other packages from moving
forward.


1. 
https://github.com/heimdal/heimdal/commit/fe43be85587f834266623adb0ecf2793d212a7ca
2. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=858970

Bug#972396: [PATCH] fix 'no space left on device' : use mktemp to avoid boot partition

[John Mullee]

diff --git a/update-initramfs b/update-initramfs

index 4bb8d8a..5fe7921 100755

--- a/update-initramfs

+++ b/update-initramfs

@@ -138,15 +138,16 @@ generate_initramfs()

     if [ "${verbose}" = 1 ]; then

         OPTS="-v ${OPTS}"

     fi

+    initramfs_tmp=$(mktemp)

     # shellcheck disable=SC2086

-    if mkinitramfs ${OPTS} "${initramfs}.new" "${version}"; then

-        mv -f "${initramfs}.new" "${initramfs}"

+    if mkinitramfs ${OPTS} "${initramfs_tmp}" "${version}"; then

+        mv -f "${initramfs_tmp}" "${initramfs}"

         # Guard against an unclean shutdown

         sync -f "${initramfs}"

     else

         mkinitramfs_return="$?"

         remove_initramfs_bak

-        rm -f "${initramfs}.new"

+        rm -f "${initramfs_tmp}"

         echo "update-initramfs: failed for ${initramfs} with $mkinitramfs_return." 
>&2

         exit $mkinitramfs_return

     fi

--

2.25.1

Bug#1074773: qt5-qmake: unable to rebuild package xdrawchem, due to an error of qmake

[Dmitry Shachnev]

Hi Georges!

On Tue, Jul 02, 2024 at 07:17:41PM +0200, Georges Khaznadar wrote:
> Package: qt5-qmake
> Version: 5.15.13+dfsg-2
> Severity: important
> 
> Dear Maintainer,
> 
> I cannot currently rebuild the package xdrawchem, which uses qmake and
> also the library libopenbabel-dev
> 
> A build log can be found at
> https://salsa.debian.org/georgesk/xdrawchem/-/pipelines/691085
> 
> I could reproduce this bug with this minimal example:
> 
> --8<---
> $ sudo cowbuilder login
> ...
> root@georges:/# cd tmp
> root@georges:/tmp# cat > foo.pro < > TEMPLATE = app
> > TARGET = foo
> > CONFIG += link_pkgconfig
> > PKGCONFIG += openbabel-3
> > EOF
> root@georges:/tmp# apt install libopenbabel-dev qt5-qmake libqt5core5t64
> ...
> root@georges:/tmp# qmake -makefile
> Info: creating stash file /tmp/.qmake.stash
> Project ERROR: openbabel-3 development package not found
> --8<---
> 
> The error message states that openbabel-3 is not there; however
> the file /usr/lib/x86_64-linux-gnu/pkgconfig/openbabel-3.pc is around.

Thank you for the minimal example.

qmake calls pkg-config as a subprocess, so you need to build-depend on
pkgconf explicitly if you need it.

It is an optional feature so I don't think it should be a hard dependency.

--
Dmitry Shachnev


signature.asc
Description: PGP signature

Bug#1071523: r-cran-spatstat.geom: autopkgtest regression in testing

[Andreas Tille]

Hi Graham,

Am Tue, Jul 02, 2024 at 04:15:26PM + schrieb Graham Inggs:
> > r-cran-spatstat.core was removed from Debian.  R-cran-spatstat.geom does
> > not depend from this package any more and the autopkgtest in Salsa CI is
> > fine[1].  Any hint why it fails in testing would be welcome.
> 
> 82s autopkgtest [21:16:20]:  summary
> 82s run-unit-test PASS
> 82s pkg-r-autopkgtest FAIL badpkg
> 
> It is only the 'pkg-r-autopkgtest' that is failing.  The
> 'run-unit-test' defined inside the r-cran-spatstat.geom package
> succeeds.

Good so far.
 
> This looks like a bug in autodep8, where pkg-r-autopkgtest is defined.
> It could be the same as #961138.
> 
> Is it possible to skip the pkg-r-autopkgtest for this package?

We did not implemented any hooks to realise this yet.

Kind regards
Andreas.

-- 
https://fam-tille.de

Bug#1074224: crossfire: diff for NMU version 1.75.0-6.1

[Boyuan Yang]

Control: tags 1074224 + pending

Dear maintainer,

I've prepared an NMU for crossfire (versioned as 1.75.0-6.1) and
uploaded it to DELAYED/5. Please feel free to tell me if I
should delay it longer.

Regards.

diff -Nru crossfire-1.75.0/debian/changelog crossfire-1.75.0/debian/changelog
--- crossfire-1.75.0/debian/changelog   2023-08-05 08:01:09.0 -0400
+++ crossfire-1.75.0/debian/changelog   2024-07-02 15:39:27.0 -0400
@@ -1,3 +1,12 @@
+crossfire (1.75.0-6.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * debian/patches/0005-Fix-build-with-Python-3.12.patch:
+Cherry-pick upstream fix on Python 3.12 compatibility.
+(Closes: #1074224)
+
+ -- Boyuan Yang   Tue, 02 Jul 2024 15:39:27 -0400
+
 crossfire (1.75.0-6) unstable; urgency=medium
 
   * Patch plugins/cfpython/cjson.c to use
diff -Nru crossfire-1.75.0/debian/patches/0005-Fix-build-with-Python-3.12.patch 
crossfire-1.75.0/debian/patches/0005-Fix-build-with-Python-3.12.patch
--- crossfire-1.75.0/debian/patches/0005-Fix-build-with-Python-3.12.patch   
1969-12-31 19:00:00.0 -0500
+++ crossfire-1.75.0/debian/patches/0005-Fix-build-with-Python-3.12.patch   
2024-07-02 15:39:01.0 -0400
@@ -0,0 +1,96 @@
+From: Boyuan Yang 
+Date: Tue, 2 Jul 2024 15:38:46 -0400
+Subject: Fix build with Python 3.12
+
+Applied-Upstream: 
https://sourceforge.net/p/crossfire/crossfire-server/ci/472dd26ac74419baa0e6373cb04e095437e994c6/
+---
+ plugins/cfpython/cjson.c | 51 
+ 1 file changed, 12 insertions(+), 39 deletions(-)
+
+diff --git a/plugins/cfpython/cjson.c b/plugins/cfpython/cjson.c
+index 1483d8f..da1547d 100644
+--- a/plugins/cfpython/cjson.c
 b/plugins/cfpython/cjson.c
+@@ -687,18 +687,14 @@ static PyObject *encode_string(PyObject *string) {
+ #if defined(IS_PY26) || defined(IS_PY3K)
+ static PyObject *encode_unicode(PyObject *unicode) {
+ PyObject *repr;
+-Py_UNICODE *s;
+-Py_ssize_t size;
++Py_ssize_t size, pos;
+ char *p;
+ static const char *hexdigit = "0123456789abcdef";
+-#ifdef Py_UNICODE_WIDE
+ static const Py_ssize_t expandsize = 10;
+-#else
+-static const Py_ssize_t expandsize = 6;
+-#endif
+ 
+-s = PyUnicode_AS_UNICODE(unicode);
+-size = PyUnicode_GET_SIZE(unicode);
++int kind = PyUnicode_KIND(unicode);
++void *data = PyUnicode_DATA(unicode);
++size = PyUnicode_GET_LENGTH(unicode);
+ 
+ if (size > (PY_SSIZE_T_MAX-2-1)/expandsize) {
+ PyErr_SetString(PyExc_OverflowError, "unicode object is too large to 
make repr");
+@@ -715,17 +711,21 @@ static PyObject *encode_unicode(PyObject *unicode) {
+ p = PyByteArray_AS_STRING(repr);
+ 
+ *p++ = '"';
++pos = 0;
+ 
+-while (size-- > 0) {
+-Py_UNICODE ch = *s++;
++const Py_UCS4 quote = PyByteArray_AS_STRING(repr)[0];
++
++while (pos < size) {
++Py_UCS4 ch = PyUnicode_READ(kind, data, pos);
++pos++;
+ 
+ /* Escape quotes */
+-if ((ch == (Py_UNICODE)PyByteArray_AS_STRING(repr)[0] || ch == '\\')) 
{
++if ((ch == quote || ch == '\\')) {
+ *p++ = '\\';
+ *p++ = (char)ch;
+ continue;
+ }
+-#ifdef Py_UNICODE_WIDE
++
+ /* Map 21-bit characters to '\U00xx' */
+ else if (ch >= 0x1) {
+ *p++ = '\\';
+@@ -740,33 +740,6 @@ static PyObject *encode_unicode(PyObject *unicode) {
+ *p++ = hexdigit[ch&0x000F];
+ continue;
+ }
+-#else
+-/* Map UTF-16 surrogate pairs to Unicode \U escapes */
+-else if (ch >= 0xD800 && ch < 0xDC00) {
+-Py_UNICODE ch2;
+-Py_UCS4 ucs;
+-
+-ch2 = *s++;
+-size--;
+-if (ch2 >= 0xDC00 && ch2 <= 0xDFFF) {
+-ucs = (((ch&0x03FF)<<10)|(ch2&0x03FF))+0x0001;
+-*p++ = '\\';
+-*p++ = 'U';
+-*p++ = hexdigit[(ucs>>28)&0x000F];
+-*p++ = hexdigit[(ucs>>24)&0x000F];
+-*p++ = hexdigit[(ucs>>20)&0x000F];
+-*p++ = hexdigit[(ucs>>16)&0x000F];
+-*p++ = hexdigit[(ucs>>12)&0x000F];
+-*p++ = hexdigit[(ucs>>8)&0x000F];
+-*p++ = hexdigit[(ucs>>4)&0x000F];
+-*p++ = hexdigit[ucs&0x000F];
+-continue;
+-}
+-/* Fall through: isolated surrogates are copied as-is */
+-s--;
+-size++;
+-}
+-#endif
+ /* Map 16-bit characters to '\u' */
+ if (ch >= 256) {
+ *p++ = '\\';
diff -Nru crossfire-1.75.0/debian/patches/series 
crossfire-1.75.0/debian/patches/series
--- crossfire-1.75.0/debian/patches/series  2023-08-04 14:48:39.0 
-0400
+++ crossfire-1.75.0/debian/patches/series  2024-07-02 15:39:01.0 
-0400
@@ -2,3 +2,4 @@
 python3-embed
 python3-ftbfs-1008637
 python3-PyUnicode_Enco

Bug#1074671: qtwebengine-opensource-src: FTBFS: ../../3rdparty/chromium/third_party/blink/renderer/core/xml/xsl_style_sheet_libxslt.cc:132:70: error: invalid conversion from ‘void (*)(void*, xmlError*

[Dmitry Shachnev]

Hi all,

On Tue, Jul 02, 2024 at 12:06:44PM -0700, Soren Stoutner wrote:
> I can confirm this build failure on my local system.
>
> Dmitry, do you have any idea off the top of your head as to the root cause?  
> Do 
> you think it is related to the recent upgrade from gcc-13 13.2.0 to 13.3.0?

More likely to the libxml2 update from the end of May.

It was fixed in 5.15.17 release in this commit:
https://github.com/qt/qtwebengine-chromium/commit/c98d28f2f0f23721

And I am currently preparing 5.15.17, will upload it to experimental soon and
then request a mini-transition for uploading it to unstable.

--
Dmitry Shachnev


signature.asc
Description: PGP signature

Bug#1074671: qtwebengine-opensource-src: FTBFS: ../../3rdparty/chromium/third_party/blink/renderer/core/xml/xsl_style_sheet_libxslt.cc:132:70: error: invalid conversion from ‘void (*)(void*, xmlError*

[Soren Stoutner]

I can confirm this build failure on my local system.

Dmitry, do you have any idea off the top of your head as to the root cause?  Do 
you think it is related to the recent upgrade from gcc-13 13.2.0 to 13.3.0?

-- 
Soren Stoutner
so...@debian.org

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

Bug#1074363: monitoring-plugins-check-smart: Don't depend on nagios-nrpe-server

[John Lines]

A good point - I will switch this to a Recommends: which will allow
installation on an icinga2 or nagios server. 


On Thu, 2024-06-27 at 11:57 +0200, Frederik Himpe wrote:
> Source: monitoring-plugins-check-smart
> Version: 6.14.1-2
> Severity: normal
> 
> Dear Maintainer,
> 
> check_smart.pl can be ran locally or from an icinga2 agent, without
> nagios-nrpe-server, so it should not have a hard dependency on
> nagios-nrpe-server.
> 
> -- System Information:
> Debian Release: 12.5
>   APT prefers stable-security
>   APT policy: (810, 'stable-security'), (810, 'stable'), (809,
> 'proposed-updates'), (710, 'oldstable-security'), (710, 'oldstable'),
> (709, 'oldstable-proposed-updates'), (310, 'testing'), (200,
> 'unstable')
> Architecture: amd64 (x86_64)
> 
> Kernel: Linux 6.6.32-frehi12 (SMP w/12 CPU threads; PREEMPT)
> Kernel taint flags: TAINT_UNSIGNED_MODULE
> Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8),
> LANGUAGE=en_IE:en
> Shell: /bin/sh linked to /usr/bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled

Bug#752135: git-merge-changelog: Overstates the need for .gitattributes

[Simon Josefsson]

Bruno Haible  writes:

> Hi Samuel and Simon,
>
>> I believe you are right, and I
>> suggest the patch below.  Bruno, what do you think?
>
> Yes, you are right. I have a package with a .gitattributes at the
> top-level and a src/ChangeLog, and the .gitattributes file has the
> desired effect. (Things may well have been different 16 years ago.
> But what matters are the 'git' versions in use today.)
>
>> Maybe today it is
>> more fashionable to use top-level .gitattributes and not bother with
>> per-directory files that feels like a CVS idiom.
>
> Absolutely. I'm committing this:

Thank you!  Looks great.  This fix didn't make it into the 20240701-1
upload of gnulib into Debian, but hopefully I'll be able to take care of
it before the next upload.

It would be nice if the documentation is moved to the gnulib texinfo
manual, but as I haven't tried git-merge-changelog yet I'm not the best
person to work on that.

/Simon


signature.asc
Description: PGP signature

Bug#1072991: closed by Michael Tokarev (Re: [Pkg-samba-maint] Bug#1072991: cifs-utils depends on python - need it?)

[Jo King]

 hi, thanks. i have done as you suggest (raised upstream)
...at least hope so, assuming 'contact' linux-c...@vger.kernel.org listed at 
following is way to go. https://wiki.samba.org/index.php/LinuxCIFS_utils 
 On Sunday 16 June 2024 at 14:54:05 BST, Debian Bug Tracking System 
 wrote:  
 
 This is an automatic notification regarding your Bug report
which was filed against the cifs-utils package:

#1072991: cifs-utils depends on python - need it?

It has been closed by Michael Tokarev .

Their explanation is attached below along with your original report.
If this explanation is unsatisfactory and you have not received a
better one in a separate message then please contact Michael Tokarev 
 by
replying to this email.


-- 
1072991: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072991
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
11.06.2024 15:44, Jo King wrote:
> Package: cifs-utils
> Version: 2:6.11-3.1+deb11u2
> 
> In debian 11 and 12 (oldstable and stable) python is a 'deps'. In debian 10 
> it isn't.

There's a tool in cifs-utils, smb2-quota, which is written in python.

> Suggested fix: cifs-utils package made to not depend on python.
This will break smb2-quota and will bring up bold fat lintian error message as 
well
(correctly so).

> Ramble:
> Ideally all bits of samba would work without python (someone did provide a 
> patch years ago...)
> Debian USP is its ability to function as a desktop without depending on 
> python.
> Very different from Ubuntu/Fedora...

I'd suggest you to talk with cifs-utils upstream and provide a rewrite of 
smb2-quota in
a different language.

FWIW: I know very little about cifs-utils.

Thanks,

/mjtPackage: cifs-utils
Version: 2:6.11-3.1+deb11u2

In debian 11 and 12 (oldstable and stable) python is a 'deps'. In debian 10 it 
isn't.

Suggested fix: cifs-utils package made to not depend on python.

Ramble:
Ideally all bits of samba would work without python (someone did provide a 
patch years ago...)
Debian USP is its ability to function as a desktop without depending on python.
Very different from Ubuntu/Fedora...

Thanks, jo
  

Bug#752135: git-merge-changelog: Overstates the need for .gitattributes

[Bruno Haible]

Hi Samuel and Simon,

> I believe you are right, and I
> suggest the patch below.  Bruno, what do you think?

Yes, you are right. I have a package with a .gitattributes at the
top-level and a src/ChangeLog, and the .gitattributes file has the
desired effect. (Things may well have been different 16 years ago.
But what matters are the 'git' versions in use today.)

> Maybe today it is
> more fashionable to use top-level .gitattributes and not bother with
> per-directory files that feels like a CVS idiom.

Absolutely. I'm committing this:


2024-07-02  Bruno Haible  

git-merge-changelog: Simplify installation instructions.
Reported by Samuel Bronson  via Simon Josefsson in
.
* lib/git-merge-changelog.c: Suggest creating a .gitattributes file only
at the top-level.

diff --git a/lib/git-merge-changelog.c b/lib/git-merge-changelog.c
index 3cffe1fd2f..60754c8367 100644
--- a/lib/git-merge-changelog.c
+++ b/lib/git-merge-changelog.c
@@ -1,5 +1,5 @@
 /* git-merge-changelog - git "merge" driver for GNU style ChangeLog files.
-   Copyright (C) 2008-2021 Bruno Haible 
+   Copyright (C) 2008-2024 Bruno Haible 
 
This file is free software: you can redistribute it and/or modify
it under the terms of the GNU General Public License as published
@@ -55,8 +55,8 @@
   name = GNU-style ChangeLog merge driver
   driver = /usr/local/bin/git-merge-changelog %O %A %B
 
- - In every directory that contains a ChangeLog file, add a file
-   '.gitattributes' with this line:
+ - Add to the top-level directory of the checkout a file '.gitattributes'
+   with this line:
 
   ChangeLogmerge=merge-changelog
 
@@ -77,12 +77,12 @@
Additionally, for hg users:
  - Add to your $HOME/.hgrc the lines
 
-[merge-patterns]
-ChangeLog = git-merge-changelog
+  [merge-patterns]
+  ChangeLog = git-merge-changelog
 
-[merge-tools]
-git-merge-changelog.executable = /usr/local/bin/git-merge-changelog
-git-merge-changelog.args = $base $local $other
+  [merge-tools]
+  git-merge-changelog.executable = /usr/local/bin/git-merge-changelog
+  git-merge-changelog.args = $base $local $other
 
See  section merge-tools
for reference.

Bug#1043016: rust-fastrand: please update to v2

[Peter Green]

On 01/07/2024 07:21, Jonas Smedegaard wrote:

Quoting Peter Michael Green (2024-06-30 13:41:42)

I am aware that v2 is already pending in experimental, but given the
pace of transitioning to a new branch, it is helpful to have the
rng.fill() function available faster, for packages to prepare for the
transition, which is then in more cases possible to handle by loosenig
crate depenency to ">= 1.9, <= 2".

Done,


Excellent. Thanks!


Can you post in the bug for updating to 2.x when your packages
are ready and I'll look at the rust team ones.


Do you need something else/more than my confirmation post in February?


I see rsass and blocking are fixed, thanks. That leaves the async packages

Given that the async* packages seem to be increasingly important to the
rust ecosystem, I'd like confirmation that they can be fixed in a
coordinated manner.

Taking a look at them now, it looks like rust-async-executor will need
a coordinated upload, consisting of.

1. Taking the version from experimental
2. Bumping the Debian dependency on concurrent-queue to match the
   cargo dependency.
3. Dropping patch 2001_fastrand.patch
4. Updating the debian dependencies on fastrand.
5. Uploading to unstable.

When I look at the patch used for fastrand 1.x it doesn't look
like it would be easilly adapted to support both the old and new versions.

In rust-async-lock, for the version in unstable, the Cargo dev-dependencies
allow the new version, but the Debian build/test dependencies do not. This is
fixed in the experimental version but the experimental version is
semver-breaking. So an update to the version in sid would seem sensible
to decouple the transitions.

Bug#1073504: #1073504 napari: fails to build wheel with python3.12

[Étienne Mollier]

Hi Roland,

Roland Mas, on 2024-07-02:
> Le 02/07/2024 à 16:52, Roland Mas a écrit :
> > I'm unable to reproduce your bug in a clean up-to-date cowbuilder sid
> > chroot. I uploaded a new upstream release while investigating
> > (0.5.0~a5-1), let's see if the buildds manage to build it before
> > comparing your log and mine line-by-line :-)
> > 
> Seems that the buildd network managed to build the package… could you try
> building the new version on your side?

It looks like it was a transient issue.  I just reran a build
today and it went through.  As far as I can witness, the issue
is resolved now.

Have a nice day,  :)
-- 
  .''`.  Étienne Mollier 
 : :' :  pgp: 8f91 b227 c7d6 f2b1 948c  8236 793c f67e 8f0d 11da
 `. `'   sent from /dev/pts/3, please excuse my verbosity
   `-on air: The Multiverse Concept - Pluge into the unknow…


signature.asc
Description: PGP signature

Bug#1069498: libx86emu: FTBFS on armhf: mem.c:581:12: error: implicit declaration of function ‘inb’; did you mean ‘ins’? [-Werror=implicit-function-declaration]

[Roland Clobus]

Hi,

On Wed, 19 Jun 2024 12:41:31 +0200 Michael Prokop  wrote:
...

Would be great to get hwinfo back into Debian/testing to make sure
it finds its way into Debian/trixie also.


Due to a long chain of dependencies (live-task-base, 
live-task-recommended, hw-probe, hwinfo, libx86emu), this bug report has 
an unexpected side effect.
hw-probe has been remove from testing and that causes curl to be missing 
from the live images in testing, and therefore several openQA tests fail 
(because curl has always been available in these images).


Can I be of assistance?

With kind regards,
Roland Clobus


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1069495: wacomtablet: FTBFS on armhf: dh_auto_test: error: cd obj-arm-linux-gnueabihf && make -j4 test ARGS\+=--verbose ARGS\+=-j4 returned exit code 2

[Marco Mattiolo]

Hi Santiago,

I'm the maintainer of plasma-mobile package in Debian, plus some of the 
related apps. At the moment, the present bug keeps meta-plasma-mobile 
metapackage out of trixie, thus letting the building of Mobian 
plasma-mobile images to fail [1]. As I wrote in the previous message, 
looking into buildd and reproducible-builds, I thought this to be 
solved, but from your attachment I see I shouldn't have assumed.


I'm not the maintainer of wacomtablet, so I'm not sure what to touch if 
tests are still failing. I see in your attachment that the error message 
is always the same as in the original report, then I'd try e.g. [2] that 
I see is not implemented in d/rules for wacomtablet, but maybe it's just 
better to wait for the new version of wacomtablet (6.1.0-1 now in 
experimental) to be uploaded to sid and check how that new version behaves.


Kind regards

Marco

[1] https://salsa.debian.org/Mobian-team/mobian-recipes/-/jobs/5907189/raw

[2] 
https://superuser.com/questions/1694496/qt5s-qpa-can-not-connect-to-my-display



Il 01/07/24 17:45, Santiago Vila ha scritto:

retitle 1069495 wacomtablet: FTBFS: failing tests
thanks

[ Please always Cc: the bug submitter, the BTS does not forward 
messages sent

to the bug address to the bug submitter by default ].

El 28/6/24 a las 19:26, Marco Mattiolo escribió:
that looks more an issue with Qt (and xorg?). Is this still failing 
to build for you or shall we close this?


I can reproduce this on m6a.large and r6a.large instances from AWS, 
but randomly.

(See attach). The test which fails is not always the same.

If you need an instance to reproduce this, please contact me privately.

Thanks.

Bug#1074774: bctoolbox: FTBFS with MbedTLS 3.6

[Andrea Pappacoda]

Source: bctoolbox
Version: 5.2.0-2.1
Severity: important
Tags: ftbfs
Control: block 1074248 by -1
Control: forwarded -1 
https://gitlab.linphone.org/BC/public/bctoolbox/-/merge_requests/216

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Hi!

I'm working towards transitioning mbedtls from version 2.28 LTS to 3.6 LTS.
Unfortunately, bctoolbox 5.2 fails to build with mbedtls 3.x, so is one of the
(key) packages holding back the transition.

Luckily for you, upstream has already switched to mbedtls 3.x in bctoolbox 5.3
and newer, so all you need to do is "just" upgrade to a new upstream release.

Could you please start preparing the upgrade, ideally pushing the new release
to experimental first?

Thanks!


- -- System Information:
Debian Release: trixie/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.8.12-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.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

-BEGIN PGP SIGNATURE-

iIoEARYIADIWIQS6VuNIvZRFHt7JcAdKkgiiRVB3pwUCZoQ6chQcYW5kcmVhQHBh
cHBhY29kYS5pdAAKCRBKkgiiRVB3p+xBAQCwXFWeC+SHgTkSXRtMKUveKiBlg1TW
74z2dImIXXlPCgEA7gVKeorv87PkFIBZY0kU/FsGWCaG8I14k6NHcspc9gk=
=kdrA
-END PGP SIGNATURE-

Bug#752135: git-merge-changelog: Overstates the need for .gitattributes

[Simon Josefsson]

Samuel Bronson  writes:

> Package: git-merge-changelog
> Version: 20140202+stable-2
> Severity: normal
>
> Dear Maintainer,
>
> Your git-merge-changelog(1) manpage and the source file
> git-merge-changelog.c both say that you need a '.gitattributes' file in
> *every* directory.  In fact, if you want all files named ChangeLog in a
> given git repository to be merged using git-merge-changelog, you just
> need one .gitattributes file at the top of the tree, with the same
> contents already documented in both manpage and source.
>
> This is because the pattern is treated the same as in .gitignore, which
> means that for a pattern to be restricted to matching a file relative
> to that particular directory, it must start with a /, so "ChangeLog"
> will match any file named ChangeLog in the directory containing the
> .gitattribute file or any of its subdirectories.

Hi Samuel.  Thanks for the bug report.  I believe you are right, and I
suggest the patch below.  Bruno, what do you think?  Maybe today it is
more fashionable to use top-level .gitattributes and not bother with
per-directory files that feels like a CVS idiom.

/Simon

diff --git a/lib/git-merge-changelog.c b/lib/git-merge-changelog.c
index 3cffe1fd2f..b8c6b63c32 100644
--- a/lib/git-merge-changelog.c
+++ b/lib/git-merge-changelog.c
@@ -55,8 +55,9 @@
   name = GNU-style ChangeLog merge driver
   driver = /usr/local/bin/git-merge-changelog %O %A %B
 
- - In every directory that contains a ChangeLog file, add a file
-   '.gitattributes' with this line:
+ - In every directory that contains a ChangeLog file, or
+   at the top-level directory, add a file '.gitattributes' with
+   this line:
 
   ChangeLogmerge=merge-changelog
 


signature.asc
Description: PGP signature

Bug#1074773: qt5-qmake: unable to rebuild package xdrawchem, due to an error of qmake

[Georges Khaznadar]

Package: qt5-qmake
Version: 5.15.13+dfsg-2
Severity: important

Dear Maintainer,

I cannot currently rebuild the package xdrawchem, which uses qmake and
also the library libopenbabel-dev

A build log can be found at
https://salsa.debian.org/georgesk/xdrawchem/-/pipelines/691085

I could reproduce this bug with this minimal example:

--8<---
$ sudo cowbuilder login
...
root@georges:/# cd tmp
root@georges:/tmp# cat > foo.pro < TEMPLATE = app
> TARGET = foo
> CONFIG += link_pkgconfig
> PKGCONFIG += openbabel-3
> EOF
root@georges:/tmp# apt install libopenbabel-dev qt5-qmake libqt5core5t64
...
root@georges:/tmp# qmake -makefile
Info: creating stash file /tmp/.qmake.stash
Project ERROR: openbabel-3 development package not found
--8<---

The error message states that openbabel-3 is not there; however
the file /usr/lib/x86_64-linux-gnu/pkgconfig/openbabel-3.pc is around.

Thank you in advance if you can fix it.

Best regards,   Georges.


-- System Information:
Debian Release: trixie/sid
  APT prefers stable
  APT policy: (700, 'stable'), (650, 'testing'), (500, 'stable-updates'), (500, 
'stable-security'), (500, 'oldstable-updates'), (500, 'oldstable-security'), 
(500, 'oldoldstable'), (500, 'unstable'), (500, 'oldstable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-25-amd64 (SMP w/4 CPU threads)
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

Versions of packages qt5-qmake depends on:
ii  qt5-qmake-bin  5.15.13+dfsg-2
ii  qtchooser  66-2

qt5-qmake recommends no packages.

qt5-qmake suggests no packages.

-- no debconf information

Bug#896834: retitle

[Holger Levsen]

control: retitle -1 sequoia-chameleon-gnupg: unclear bug report, possibly 
solved with new upstream version
control: severity -1 important

 juliank: you reassigned #896834 to gpgv-from-sq amd made it serious,
 while keeping the title ("apt-key fails in stretch") and in your last
 two mails to the bug you described 3 bugs gpgv-from-sq, one at least
 is wishlist and the serioussness is already tracked in #1073272 and
 fixed in latest upstream. so i wonder what to do with this bug and
 tend to downgrade to normal or wishlist
 | h01ger: I don't know I've shifted to implementing my own OpenPGP
 public key parser so I can do the verification without relying on
 the gpgv feature
< h01ger> ok, i'll reseverity accordingly..

it's super annoying to get a bug from 2018 (when chameleon didnt even exist)
reassigned without further comment or title adjusted, but increased severity...


-- 
cheers,
Holger

 ⢀⣴⠾⠻⢶⣦⠀
 ⣾⠁⢠⠒⠀⣿⡁  holger@(debian|reproducible-builds|layer-acht).org
 ⢿⡄⠘⠷⠚⠋⠀  OpenPGP: B8BF54137B09D35CF026FE9D 091AB856069AAA1C
 ⠈⠳⣄

I too often read "The planet is dying! 😱" It is not. The planet is adapting 
to what we're doing. There will always be a rich ecosystem on our planet.
But that ecosystem will adapt to the point where we no longer have a place in 
it. No, the planet is not dying. We are. (@kleinemaulw...@troet.cafe)


signature.asc
Description: PGP signature

Bug#1074772: ITP: gecode-snapshot -- low-level modelling language for constraint problems

[Kari Pahula]

Package: wnpp
Severity: wishlist
Owner: Kari Pahula 
X-Debbugs-Cc: debian-de...@lists.debian.org

* Package name: gecode-snapshot
  Version : 6.2.0+gitMMDD
  Upstream Contact: Guido Tack , Mikael Zayenz Lagerkvist 

* URL : https://www.gecode.org/
* License : MIT/X (and others)
  Programming Lang: C++
  Description : low-level modelling language for constraint problems

 FlatZinc is a low-level modelling language for constraint
 problems. It is designed to be easily interfaceable to constraint
 solvers (like Gecode). For more information on FlatZinc, please refer
 to the MiniZinc pages of the G12 project .

Source package name would be gecode-snapshot and it'll likely have a
single binary package, gecode-flatzinc.

Gecode is already in Debian, this is get an updated version of
FlatZinc available for MiniZinc.  Gecode hasn't had a release since
2019 and I need to use it as a library as well.  Fuller description of
the situation can be found at
https://lists.debian.org/debian-devel/2024/06/msg00312.html

Hopefully gecode-snapshot can be removed in the future when Gecode's
had a release again.

Bug#1074248: transition: mbedtls

[Andrea Pappacoda]

Hi Emilio!


Il 2 luglio 2024 13:13:43 CEST, Emilio Pozuelo Monfort  ha 
scritto:
>Cool. btw I checked those packages and only these 3 are key packages:
>
>bctoolbox
>libgit2
>rustc
>
>It'd be nice to know if rustc will build if it wasn't for the disk space. Also 
>it'd be good to have the other two packages sorted (e.g. with a patch prepared 
>or identified) before starting this transition.

bctoolbox switched to using mbedtls 3.x since version 5.3.0, so the package 
maintainers would only need to upgrade the package. libgit2 too switched to the 
latest mbedtls in version 1.8.0, which is already in experimental. As for 
rustc, yeah, I'd need to build on a system with more disk space.

I'm nonetheless at least looking at all the failures and filing bug reports 
when necessary. Once I've checked all the packages and the key packages you've 
mentioned are ready, I'll go ahead with the transition. I can't NMU fixes since 
I'm only a DM, so there's not much I can do if the respective maintainers don't 
fix the build failures with mbedtls 3.

If you have any other suggestions, please let me know!

Thanks :)

P.S. formatting is probably off, since I'm replying from my phone. Sorry for 
that!

Bug#1060875: rust-itertools: please upgrade to v0.12

[Peter Green]

Please upgrade to (or separately provide) branch v0.12.


This looks ready to go once rust-criterion and rust-test-case are fixed.

done

Package: btm
Package: elan
Package: git-delta
Package: hippotat
Package: precious
Package: python-maturin
Package: rust-av-metrics
Package: rust-cargo
Package: rust-cargo-c
Package: rust-cargo-lichking
Package: rust-cargo-mutants
Package: rust-coreutils
Package: rust-criterion-0.3
Package: rust-criterion-plot
Package: rust-debcargo
Package: rust-drt-tools
Package: rust-gping
Package: rust-gstreamer
Package: rust-lalrpop
Package: rust-prost-build
Package: rust-prost-derive
Package: rust-ratatui
Package: rust-rav1e
Package: rust-sequoia-sq
Package: rust-ruma-state-res
Package: rust-rustpython-common
Package: rust-rustpython-compiler-core
Package: rust-rustpython-parser
Package: sccache

Fixed in experimental:

Package: rust-itertools-num
Package: rust-malachite-base
Package: rust-predicates
Package: rust-shrinkwraprs
Package: rust-sqlformat
Package: rust-zxcvbn

Bugs filed:

Package: rust-criterion
Package: rust-test-case

Broken and not in testing:

Package: rust-pdf
Package: rust-rspotify

Bug#1074771: sploitscan: 'IndexError: list index out of range' in Further References

[Tomáš Szaniszlo]

Package: sploitscan
Version: 0.9.1-3
Severity: normal

Dear maintainer,

I have observed that sometimes sploitscan exits abnormally during
listing Further References:

$ sploitscan CVE-2024-6387
...
┌───[ 📚 Further References ]
|
├ https://access.redhat.com/security/cve/CVE-2024-6387
├ https://bugzilla.redhat.com/show_bug.cgi?id=2294604
└ https://www.qualys.com/2024/07/01/cve-2024-6387/regresshion.txt

Traceback (most recent call last):
  File "/usr/bin/sploitscan", line 8, in 
sys.exit(cli())
 ^
  File "/usr/lib/python3/dist-packages/sploitscan/sploitscan.py", line 922, 
in cli
main(args.cve_ids, args.export, args.import_file, args.type)
  File "/usr/lib/python3/dist-packages/sploitscan/sploitscan.py", line 797, 
in main
epss_data["data"][0].get("epss", "N/A")
~^^^
IndexError: list index out of range

I have tried this earlier today and the two attempts reliably ended with
a stacktrace. However, at this moment it works fine, so it seems to be
related to the data being retrieved. One more notable difference in
the outputs is that before I got "No data found." in the EPSS section,
but now I see the EPSS Score there.

Best wishes,
Tomaxuser

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

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

Versions of packages sploitscan depends on:
ii  python3   3.11.8-1
ii  python3-jinja23.1.3-1
ii  python3-openai1.12.0-1
ii  python3-requests  2.31.0+dfsg-2
ii  python3-tabulate  0.9.0-1

sploitscan recommends no packages.

Versions of packages sploitscan suggests:
ii  python3-pygments  2.18.0+dfsg-1

-- no debconf information

Bug#1071523: r-cran-spatstat.geom: autopkgtest regression in testing

[Graham Inggs]

Hi Andreas

> r-cran-spatstat.core was removed from Debian.  R-cran-spatstat.geom does
> not depend from this package any more and the autopkgtest in Salsa CI is
> fine[1].  Any hint why it fails in testing would be welcome.

82s autopkgtest [21:16:20]:  summary
82s run-unit-test PASS
82s pkg-r-autopkgtest FAIL badpkg

It is only the 'pkg-r-autopkgtest' that is failing.  The
'run-unit-test' defined inside the r-cran-spatstat.geom package
succeeds.

This looks like a bug in autodep8, where pkg-r-autopkgtest is defined.
It could be the same as #961138.

Is it possible to skip the pkg-r-autopkgtest for this package?

Regards
Graham

Bug#1073504: #1073504 napari: fails to build wheel with python3.12

[Roland Mas]

Le 02/07/2024 à 16:52, Roland Mas a écrit :

Hi Étienne,

I'm unable to reproduce your bug in a clean up-to-date cowbuilder sid 
chroot. I uploaded a new upstream release while investigating 
(0.5.0~a5-1), let's see if the buildds manage to build it before 
comparing your log and mine line-by-line :-)


Seems that the buildd network managed to build the package… could you 
try building the new version on your side?


Roland.

Bug#1074770: rust-test-case - upcoming rust-itertools update.

[Peter Green]

Package: rust-test-case
Version: 3.3.1-1
Tags: patch

We are currently looking at updating rust-itertools to 0.12,
the new version is available in experimental.

The Debian build-dependencies and test-dependencies have no
upper limit on the version, but the Cargo dev-dependency does,
so building rust-test-case with rust-itertools from
experimental fails with.


error: failed to select a version for the requirement `itertools = ">=0.10, 
<=0.11"`
candidate versions found which didn't match: 0.12.0


After removing the upper limit from the cargo dev-dependency
the package builds and it's autopkgtests run succesfully.

Debdiff is attatched.
diff -Nru rust-test-case-3.3.1/debian/changelog 
rust-test-case-3.3.1/debian/changelog
--- rust-test-case-3.3.1/debian/changelog   2024-01-14 17:27:53.0 
+
+++ rust-test-case-3.3.1/debian/changelog   2024-07-02 15:50:56.0 
+
@@ -1,3 +1,10 @@
+rust-test-case (3.3.1-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Relax cargo dev-dependency on itertools.
+
+ -- Peter Michael Green   Tue, 02 Jul 2024 15:50:56 +
+
 rust-test-case (3.3.1-1) unstable; urgency=medium
 
   [ upstream ]
diff -Nru rust-test-case-3.3.1/debian/patches/2001_itertools.patch 
rust-test-case-3.3.1/debian/patches/2001_itertools.patch
--- rust-test-case-3.3.1/debian/patches/2001_itertools.patch2024-01-14 
17:22:56.0 +
+++ rust-test-case-3.3.1/debian/patches/2001_itertools.patch2024-07-02 
15:50:56.0 +
@@ -1,8 +1,8 @@
-Description: accept older branch of crate itertools
+Description: accept older and newer branches of crate itertools
 Author: Jonas Smedegaard 
 Bug-Debian: https://bugs.debian.org/1054075
 Forwarded: not-needed
-Last-Update: 2024-01-14
+Last-Update: 2024-07-02 by Peter Michael Green
 ---
 This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
 --- a/Cargo.toml
@@ -12,7 +12,7 @@
  [dev-dependencies]
  insta   = "1.12"
 -itertools   = "0.11"
-+itertools   = ">= 0.10, <= 0.11"
++itertools   = ">= 0.10"
  regex   = "1.5"
  
  [workspace]

Bug#1033839: docker.io -- please update to v26.0.0 or above

[Reinhard Tartler]

On 2024-07-02 07:29, Prusty, Badrikesh wrote:


I have created, "bp/docker26" branch in my fork, did some incremental
changes to fix override_dh_auto_install:

https://salsa.debian.org/badrikesh/docker/-/commits/bp%2Fdocker26

62f28e5 golang-github-docker-docker-dev.install: update install files

4ba1fd7 docker.io.install: drop ovrouter, dnet and update dockerd path


8d94f31 Avoid renaming dockerd, docker-proxy binaries

c838a7c debian/rules: add build bin path to PATH variable

387aa4a debian/rules: build docker-proxy as well

Please review, and feel free to use it.


I cherry picked your commits with slight modifications.

After dropping swarmkit, I ended up with a build that produces .deb 
files:


https://salsa.debian.org/go-team/packages/docker/-/jobs/5918507

I guess we can now proceed with testing it :-)

-rt

Bug#1074766: openssh-server: upgrading to openssh-server (1:9.2p1-2+deb12u3) resets /etc/ssh/sshd_config file without any prompt

[John Wellesz]

Hello Colin,

Here is the output of apt/term.log:

Log started: 2024-07-02  00:04:13
(Reading database ... 64456 files and directories currently installed.)
Preparing to unpack .../openssh-sftp-server_1%3a9.2p1-2+deb12u3_amd64.deb
...
Unpacking openssh-sftp-server (1:9.2p1-2+deb12u3) over (1:9.2p1-2+deb12u2)
...
Preparing to unpack .../openssh-server_1%3a9.2p1-2+deb12u3_amd64.deb ...
Unpacking openssh-server (1:9.2p1-2+deb12u3) over (1:9.2p1-2+deb12u2) ...
Preparing to unpack .../openssh-client_1%3a9.2p1-2+deb12u3_amd64.deb ...
Unpacking openssh-client (1:9.2p1-2+deb12u3) over (1:9.2p1-2+deb12u2) ...
Setting up openssh-client (1:9.2p1-2+deb12u3) ...
Setting up openssh-sftp-server (1:9.2p1-2+deb12u3) ...
Setting up openssh-server (1:9.2p1-2+deb12u3) ...
Replacing config file /etc/ssh/sshd_config with new version
rescue-ssh.target is a disabled or a static unit not running, not starting
it.
ssh.socket is a disabled or a static unit not running, not starting it.
Processing triggers for man-db (2.11.2-2) ...
Processing triggers for ufw (0.36.2-1) ...
Log ended: 2024-07-02  00:04:16

I've attached the sshd_config from my last week backup, I've just changed
the port number I use to a random one.

I had the same problem on 4 different servers I upgraded last night. Maybe
it's not related to openssh-server and I just noticed the problem on this
package...

Also note that I've recently enabled apt-listchange prompting on all these
servers:

cat /etc/apt/listchanges.conf
[apt]
frontend=pager
which=both
email_address=root
email_format=html
confirm=true
headers=false
reverse=false
save_seen=none
no_network=false

Here is the command I used to check and apply security updates:

sudo apt update && sudo apt dist-upgrade -V && sudo apt autoremove -y

Regards,

John Wellesz

On Tue, Jul 2, 2024 at 5:24 PM Colin Watson  wrote:

> On Tue, Jul 02, 2024 at 03:05:16PM +, John Wellesz wrote:
> > I used apt upgrade to install the security update available for
> >   openssh-server
> >
> >* What was the outcome of this action?
> >
> > It overwrote /etc/ssh/sshd_config without promtping, erasing the custom
> settings
> > and almost locking me out as a result (my custom port setting was gone
> > as well as other changes I've made).
> >
> >* What outcome did you expect instead?
> >
> > I expected to receive the usual prompt when a configuration file is
> > modified asking me what I want to do but there was none.
>
> We'll need to be able to reproduce this problem before being able to do
> anything about it.  (I have a modified /etc/ssh/sshd_config on my own
> stable system and it wasn't overwritten on upgrade.)
>
> Can you please provide a copy of your modified /etc/ssh/sshd_config,
> along with the output of the relevant apt run (which should be preserved
> in /var/log/apt/term.log)?
>
> --
> Colin Watson (he/him)  [cjwat...@debian.org]
>


sshd_config
Description: Binary data

Bug#1074239: [3dprinter-general] Bug#1074239: cura: Cura fails to start

[Gregor Riepl]

I think I've tracked down the issue.

UM/Qt/qml/UM/SimpleButton.qml references a UI element called "ColorImage".
This class exists in Qt, but it's private and was probably changed/removed in 
Qt6.

However, there's also a ColorImage class in Uranium (Cura's UI toolkit), and I 
suspect they actually wanted to use that, but forgot to reference the correct 
type.

They actually fixed this upstream: 
https://github.com/Ultimaker/Uranium/commit/88fd460a63263d66173f1e0127b0f208577d7f4e

I'm going to add this patch to the Uranium package.

Bug#946187: ITP: starship

[Blair Noctis]

On 02/07/2024 22:56, Matthias Geiger wrote:
> On Fri, 1 Mar 2024 20:07:39 +0100 Matthias Geiger  
> wrote:
> 
>> starship needs gix, added as blocking bug. Thanks to the awesome work by
>> captol and ncts this is mostly done from what I can tell. Apart from
>> that cargo-debstatus lists those as missing:
>>
>> notify-rust, process-control, system-stat, versions and guess-host-triple.
>>
> 
> Hi,
> 
> gix is now in unstable. This was a major blocker.

Great! That's some huge progress.

> Blair, Daniele: I can sponsor any NEW crates that are needed for starship.
> 
> Should be relatively easy to churn through now imo.

Created a tracking issue on salsa:

https://salsa.debian.org/rust-team/debcargo-conf/-/issues/68

-- 
Sdrager,
Blair Noctis


OpenPGP_0xC21D9AD423A39727.asc
Description: OpenPGP public key


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1074769: libpam-google-authenticator: Update libpam-google-authenticator from upstream (1.10)

[Dario Susman]

Package: libpam-google-authenticator
Severity: minor
Tags: upstream

Dear Maintainer,


Please update the libpam-google-authenticator package from the upstream
at https://github.com/google/google-authenticator-libpam

The google-authenticator binary points to a Google URL that's no longer
valid to generate the QR code.

Thank you.

Best regards,
Dario Susman


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

Kernel: Linux 6.1.0-22-amd64 (SMP w/16 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=locale: Cannot set 
LC_ALL to default locale: No such file or directory
UTF-8), LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages libpam-google-authenticator depends on:
ii  libc6 2.36-9+deb12u7
ii  libpam0g  1.5.2-6+deb12u1
pn  libqrencode4  

libpam-google-authenticator recommends no packages.

libpam-google-authenticator suggests no packages.

Bug#1074766: openssh-server: upgrading to openssh-server (1:9.2p1-2+deb12u3) resets /etc/ssh/sshd_config file without any prompt

[Colin Watson]

On Tue, Jul 02, 2024 at 03:05:16PM +, John Wellesz wrote:
> I used apt upgrade to install the security update available for
>   openssh-server
> 
>* What was the outcome of this action?
> 
> It overwrote /etc/ssh/sshd_config without promtping, erasing the custom 
> settings
> and almost locking me out as a result (my custom port setting was gone
> as well as other changes I've made).
> 
>* What outcome did you expect instead?
> 
> I expected to receive the usual prompt when a configuration file is
> modified asking me what I want to do but there was none.

We'll need to be able to reproduce this problem before being able to do
anything about it.  (I have a modified /etc/ssh/sshd_config on my own
stable system and it wasn't overwritten on upgrade.)

Can you please provide a copy of your modified /etc/ssh/sshd_config,
along with the output of the relevant apt run (which should be preserved
in /var/log/apt/term.log)?

-- 
Colin Watson (he/him)  [cjwat...@debian.org]

Bug#1074768: openssh-server: Upgrading to openssh-server (1:9.2p1-2+deb12u3) overwrites /etc/ssh/sshd_config without prompt

[John Wellesz]

Package: openssh-server
Version: 1:9.2p1-2+deb12u3
Severity: important

Dear Maintainer,

   * What led up to the situation?

A security update was available for openssh-server

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

Upgrading to the latest available security update using apt upgrade

   * What was the outcome of this action?

sshd config file (/etc/ssh/sshd_config) was overwritten without the
usual 'what do you want to do?' prompt when a package default configuration file
is modified.
I noticed it because I could not log in back to the server because I
changed the default port among other settings...

   * What outcome did you expect instead?

The usual prompt allowing me to keep my changes or merge them with the
package new defaults...



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

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

Versions of packages openssh-server depends on:
ii  adduser3.134
ii  debconf [debconf-2.0]  1.5.82
ii  init-system-helpers1.65.2
ii  libaudit1  1:3.0.9-1
ii  libc6  2.36-9+deb12u7
ii  libcom-err21.47.0-2
ii  libcrypt1  1:4.4.33-2
ii  libgssapi-krb5-2   1.20.1-2+deb12u1
ii  libkrb5-3  1.20.1-2+deb12u1
ii  libpam-modules 1.5.2-6+deb12u1
ii  libpam-runtime 1.5.2-6+deb12u1
ii  libpam0g   1.5.2-6+deb12u1
ii  libselinux13.4-1+b6
ii  libssl33.0.13-1~deb12u1
ii  libsystemd0252.26-1~deb12u2
ii  libwrap0   7.6.q-32
ii  lsb-base   11.6
ii  openssh-client 1:9.2p1-2+deb12u3
ii  openssh-sftp-server1:9.2p1-2+deb12u3
ii  procps 2:4.0.2-3
ii  runit-helper   2.15.2
ii  sysvinit-utils [lsb-base]  3.06-4
ii  ucf3.0043+nmu1
ii  zlib1g 1:1.2.13.dfsg-1

Versions of packages openssh-server recommends:
ii  libpam-systemd [logind]  252.26-1~deb12u2
ii  ncurses-term 6.4-4
ii  xauth1:1.1.2-1

Versions of packages openssh-server suggests:
pn  molly-guard   
pn  monkeysphere  
pn  ssh-askpass   
ii  ufw   0.36.2-1

-- debconf information excluded

Bug#1074767: fuse3: Fuse deletes GNOME DE

[iconium]

Package: fuse3
Version: 3.14.0-4
Severity: important
X-Debbugs-Cc: iconium6...@gmail.com

Dear Maintainer,


Installing fuse3 via apt, sudo apt install fuse3 -y ; It deleted GNOME and 
FLATPAK.
only some messages have been logs, mainly the deletion logs of GNOME and other:


Removing gnome-software-plugin-flatpak (43.5-1~deb12u1) 
Removing flatpak (1.14.8-1~deb12u1) 
Removing gnome (1:43+1) 
Removing task-gnome-desktop (3.73) .. 
Removing gnome-core (1:43+1) 
Removing gnome-session (43.0-1+deb12u1) 
Removing xdg-desktop-portal-gnome (43.1-2) xdg-desktop-portal-gtk (1.14.1-1) 
Removing xdg-desktop-portal (1.16.0-2) Removing 

Had to use TTY and tasksel to re-install GNOME DE.
I apologize for any mistakes in this bug report, I'm not so good at reporting 
bugs.

-- System Information:
Debian Release: 12.6
  APT prefers stable
  APT policy: (900, 'stable'), (500, 'stable-updates'), (500, 
'stable-security'), (500, 'proposed-updates')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages fuse3 depends on:
ii  adduser 3.134
ii  libc6   2.36-9+deb12u7
ii  libfuse3-3  3.14.0-4
ii  mount   2.38.1-5+deb12u1
ii  sed 4.9-1

fuse3 recommends no packages.

fuse3 suggests no packages.

-- no debconf information

Bug#1074222: pycorrfit FTBFS with Python 3.12 as default

[Andreas Tille]

Am Tue, Jul 02, 2024 at 05:01:27PM +0800 schrieb Bo YU:
> 
> I can confirm it works(still during build but pass the failed stage on
> the issue).
> 
> It seems tille had worked a lot on this, so hope this helps.

I'm fine with whatever solution you might find and you can
perfectly skip me when doing some team upload.

Thanks a lot for working on this
   Andreas. 

-- 
https://fam-tille.de

Bug#1074766: openssh-server: upgrading to openssh-server (1:9.2p1-2+deb12u3) resets /etc/ssh/sshd_config file without any prompt

[John Wellesz]

Package: openssh-server
Version: 1:9.2p1-2+deb12u3
Severity: normal

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?

Upgrading to the latest security update

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

I used apt upgrade to install the security update available for
  openssh-server

   * What was the outcome of this action?

It overwrote /etc/ssh/sshd_config without promtping, erasing the custom settings
and almost locking me out as a result (my custom port setting was gone
as well as other changes I've made).

   * What outcome did you expect instead?

I expected to receive the usual prompt when a configuration file is
modified asking me what I want to do but there was none.



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

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

Versions of packages openssh-server depends on:
ii  adduser3.134
ii  debconf [debconf-2.0]  1.5.82
ii  init-system-helpers1.65.2
ii  libaudit1  1:3.0.9-1
ii  libc6  2.36-9+deb12u7
ii  libcom-err21.47.0-2
ii  libcrypt1  1:4.4.33-2
ii  libgssapi-krb5-2   1.20.1-2+deb12u1
ii  libkrb5-3  1.20.1-2+deb12u1
ii  libpam-modules 1.5.2-6+deb12u1
ii  libpam-runtime 1.5.2-6+deb12u1
ii  libpam0g   1.5.2-6+deb12u1
ii  libselinux13.4-1+b6
ii  libssl33.0.13-1~deb12u1
ii  libsystemd0252.26-1~deb12u2
ii  libwrap0   7.6.q-32
ii  lsb-base   11.6
ii  openssh-client 1:9.2p1-2+deb12u3
ii  openssh-sftp-server1:9.2p1-2+deb12u3
ii  procps 2:4.0.2-3
ii  runit-helper   2.15.2
ii  sysvinit-utils [lsb-base]  3.06-4
ii  ucf3.0043+nmu1
ii  zlib1g 1:1.2.13.dfsg-1

Versions of packages openssh-server recommends:
ii  libpam-systemd [logind]  252.26-1~deb12u2
ii  ncurses-term 6.4-4
ii  xauth1:1.1.2-1

Versions of packages openssh-server suggests:
pn  molly-guard   
pn  monkeysphere  
pn  ssh-askpass   
ii  ufw   0.36.2-1

-- debconf information excluded

Bug#946187: ITP: starship

[Matthias Geiger]

On Fri, 1 Mar 2024 20:07:39 +0100 Matthias Geiger  
wrote:


>
> starship needs gix, added as blocking bug. Thanks to the awesome work by
> captol and ncts this is mostly done from what I can tell. Apart from
> that cargo-debstatus lists those as missing:
>
> notify-rust, process-control, system-stat, versions and 
guess-host-triple.

>


Hi,

gix is now in unstable. This was a major blocker.

Blair, Daniele: I can sponsor any NEW crates that are needed for starship.

Should be relatively easy to churn through now imo.


best,


werdahias

Bug#1073504: #1073504 napari: fails to build wheel with python3.12

[Roland Mas]

Hi Étienne,

I'm unable to reproduce your bug in a clean up-to-date cowbuilder sid 
chroot. I uploaded a new upstream release while investigating 
(0.5.0~a5-1), let's see if the buildds manage to build it before 
comparing your log and mine line-by-line :-)


Roland.

Bug#1074765: nocache.c:148: init_mutexes: Assertion `fds_lock != NULL' failed

[Joey Hess]

Package: nocache
Version: 1.1-1+b1
Severity: normal

joey@darkstar:~>nocache true
true: nocache.c:148: init_mutexes: Assertion `fds_lock != NULL' failed.
Aborted
- exit 134

Happens every time.

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

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

Versions of packages nocache depends on:
ii  libc6  2.38-13

nocache recommends no packages.

nocache suggests no packages.

-- no debconf information

-- 
see shy jo


signature.asc
Description: PGP signature

Bug#1074764: signing with osslsigncode fails with a segmentation fault since latest stable update

[Sébastien Villemot]

Package: libssl3
Version: 3.0.13-1~deb12u1
Severity: important
Control: affects -1 osslsigncode

Dear Maintainers,

Since the last upgrade of openssl on bookworm (version 3.0.13-1~deb12u1), code
signing using osslsigncode (and my Yubikey) now fails with a segmentation
fault. It was working properly with version 3.0.11-1~deb12u2 (and note that
downgrading solves the problem).

Here is the command:

$ osslsigncode sign -pkcs11module /usr/lib/x86_64-linux-gnu/libykcs11.so.2 -key 
"pkcs11:id=%01;type=private;pin-value=" -certs 
~/code-signing-certificate.pem -n Foo -i https://www.foo.org -t 
http://timestamp.comodoca.com -in installer.exe -out installer-signed.exe

Here is a backtrace obtained through gdb (slightly edited to avoid leaking 
sensitive information):

Program received signal SIGSEGV, Segmentation fault.
   
pkcs11_ecdsa_sign (key=0x565c1d10, siglen=, 
sigret=0x7fffc0b0 ".>D ", msg_len=32,
msg=0x7fffc3c0 "") at ./src/p11_ec.c:409
409 ./src/p11_ec.c: No such file or directory.  
   
(gdb) bt  
#0  pkcs11_ecdsa_sign (key=0x565c1d10, siglen=, 
sigret=0x7fffc0b0 ".>D ", msg_len=32,   
msg=0x7fffc3c0 "") at ./src/p11_ec.c:409
#1  pkcs11_ecdsa_sign_sig (dgst=0x7fffc3c0 "", dlen=32, 
kinv=, rp=, ec=) at 
./src/p11_ec.c:489
#2  0x77b95385 in ossl_ecdsa_sign (type=, 
dgst=, dlen=, sig=, 
siglen=0x7fffc354, kinv=, r=0x0, eckey=0x565c0590) 
at ../crypto/ec/ecdsa_ossl.c:73
#3  0x77b96280 in ECDSA_sign (type=, 
dgst=dgst@entry=0x7fffc3c0 "", dlen=dlen@entry=32, 
sig=sig@entry=0x565c5af0 "", 
siglen=siglen@entry=0x7fffc354, eckey=eckey@entry=0x565c0590)
at ../crypto/ec/ecdsa_sign.c:38
#4  0x77b940ba in pkey_ec_sign (ctx=, sig=0x565c5af0 
"", siglen=0x7fffc460, 
tbs=0x7fffc3c0 "", tbslen=32)
at ../crypto/ec/ec_pmeth.c:136
#5  0x77c1648e in EVP_DigestSignFinal (ctx=ctx@entry=0x565cc2a0, 
sigret=0x565c5af0 "\005M\017\003PU", 
siglen=siglen@entry=0x7fffc460) at ../crypto/evp/m_sigver.c:560
#6  0x77c60468 in PKCS7_SIGNER_INFO_sign (si=si@entry=0x565cbc40) 
at ../crypto/pkcs7/pk7_doit.c:945
#7  0x77c60702 in do_pkcs7_signed_attrib (mctx=0x565cc5c0, 
si=0x565cbc40) at ../crypto/pkcs7/pk7_doit.c:721
#8  PKCS7_dataFinal (p7=p7@entry=0x565cbab0, bio=bio@entry=0x565cbc90) 
at ../crypto/pkcs7/pk7_doit.c:843
#9  0x55567561 in set_signing_blob (len=74, buf=0x565dcad0 
"", 
hash=0x565bce50, sig=0x565cbab0) at ./osslsigncode.c:1758
#10 set_indirect_data_blob (header=0x7fffc740, options=0x4a, 
indata=, type=FILE_TYPE_PE, hash=0x565bce50, 
sig=0x565cbab0) at ./osslsigncode.c:1823
#11 get_pkcs7 (cmd=cmd@entry=CMD_SIGN, hash=hash@entry=0x565bce50, 
type=, type@entry=FILE_TYPE_PE, 
indata=indata@entry=0x70e0 "MZ\220", 
options=options@entry=0x7fffc850, header=header@entry=0x7fffc740, 
cparams=0x7fffc7a0, cursig=0x0) at ./osslsigncode.c:5431
#12 0xd5e2 in pe_presign_file (type=, 
cursig=, outdata=, hash=, 
indata=, cparams=, options=, 
header=, cmd=)
at ./osslsigncode.c:5543
#13 main (argc=, argv=) at ./osslsigncode.c:6173

Note that the segfault occurs in /usr/lib/x86_64-linux-gnu/engines-3/pkcs11.so
(from libengine-pkcs11-openssl), which is itself called by libcrypto.so.3 (from
libssl3).

Cheers,

--
⢀⣴⠾⠻⢶⣦⠀  Sébastien Villemot
⣾⠁⢠⠒⠀⣿⡁  Debian Developer
⢿⡄⠘⠷⠚⠋⠀  https://sebastien.villemot.name
⠈⠳⣄  https://www.debian.org

Bug#1074763: CVE-2024-32498: Arbitrary file access through custom QCOW2 external data

[Thomas Goirand]

Source: cinder
Version: 2:21.1.0-3
Severity: grave
Tags: patch

Title: Arbitrary file access through custom QCOW2 external data
Reporter: Martin Kaesberger
Products: Cinder, Glance, Nova

Description:
Martin Kaesberger reported a vulnerability in QCOW2 image processing
for Cinder, Glance and Nova. By supplying a specially created QCOW2
image which references a specific data file path, an authenticated
user may convince systems to return a copy of that file's contents
from the server resulting in unauthorized access to potentially
sensitive data. All Cinder deployments are affected; only Glance
deployments with image conversion enabled are affected; all Nova
deployments are affected.

Original private report: https://launchpad.net/bugs/2059809

Bug#1074762: CVE-2024-32498: Arbitrary file access through custom QCOW2 external data

[Thomas Goirand]

Source: nova
Version: 2:26.1.0-4
Severity: grave
Tags: patch

Title: Arbitrary file access through custom QCOW2 external data
Reporter: Martin Kaesberger
Products: Cinder, Glance, Nova

Description:
Martin Kaesberger reported a vulnerability in QCOW2 image processing
for Cinder, Glance and Nova. By supplying a specially created QCOW2
image which references a specific data file path, an authenticated
user may convince systems to return a copy of that file's contents
from the server resulting in unauthorized access to potentially
sensitive data. All Cinder deployments are affected; only Glance
deployments with image conversion enabled are affected; all Nova
deployments are affected.

Original private report: https://launchpad.net/bugs/2059809

Bug#1074761: CVE-2024-32498: Arbitrary file access through custom QCOW2 external data

[Thomas Goirand]

Source: glance
Version: 2:25.1.0-2
Severity: grave
Tags: patch

Title: Arbitrary file access through custom QCOW2 external data
Reporter: Martin Kaesberger
Products: Cinder, Glance, Nova

Description:
Martin Kaesberger reported a vulnerability in QCOW2 image processing
for Cinder, Glance and Nova. By supplying a specially created QCOW2
image which references a specific data file path, an authenticated
user may convince systems to return a copy of that file's contents
from the server resulting in unauthorized access to potentially
sensitive data. All Cinder deployments are affected; only Glance
deployments with image conversion enabled are affected; all Nova
deployments are affected.

Original private report: https://launchpad.net/bugs/2059809

Bug#1074760: RFS: django-anymail/11.0-1 -- Django email backend for multiple ESPs (Python 3)

[Akash Doppalapudi]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "django-anymail":

 * Package name : django-anymail
   Version  : 11.0-1
   Upstream contact : Mike Edmunds 
 * URL  : https://github.com/anymail/django-anymail
 * License  : BSD-3-Clause
 * Vcs  : https://salsa.debian.org/debian/django-anymail
   Section  : python

The source builds the following binary packages:

  python3-django-anymail - Django email backend for multiple ESPs 
(Python 3)


To access further information about this package, please visit the 
following URL:


  https://mentors.debian.net/package/django-anymail/

Alternatively, you can download the package with 'dget' using this command:

  dget -x 
https://mentors.debian.net/debian/pool/main/d/django-anymail/django-anymail_11.0-1.dsc


Changes since the last upload:

 django-anymail (11.0-1) unstable; urgency=medium
 .
   * New upstream version 11.0

Regards,
--
  Akash Doppalapudi


OpenPGP_0xBCBCAE31ECE05007.asc
Description: OpenPGP public key


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#939392: please provide kmodsign like Ubuntu does

[Colin Watson]

On Mon, Sep 09, 2019 at 04:46:38PM +0100, Steve McIntyre wrote:
> On Mon, Sep 09, 2019 at 04:35:44PM +0100, Steve McIntyre wrote:
> >On Wed, Sep 04, 2019 at 03:47:35PM +0300, Dmitry Eremin-Solenikov wrote:
> >>Could you please provide kmodsign tool like Ubuntu package does, so that
> >>we can sign Linux kernel modules with custom keys.
> >
> >ACK, that would be a good thing to have.
> >
> >Steve - would you be happy to push the ubuntu patches up into Debian?
> >
> >Probably worth us talking to the original kmodsign authors (David
> >Howells and David Woodhouse) and the sbsigntool maintainer (James
> >Bottomley) about maybe integrating things upstream too. I'll try to
> >start a conversation there...
> 
> Hmmm, hang on - it's just the "sign-file" program from the kernel
> tree, renamed as "kmodsign" for some reason. Steve: the bug at
> 
>   https://bugs.launchpad.net/bugs/1526959
> 
> named in the patches doesn't seem all that relevant - could you
> enlighten us please? :-)

https://bugs.launchpad.net/ubuntu/+source/sbsigntool/+bug/1579766 is a
more relevant bug report.  This was for signing things outside of the
context of a kernel build, and Launchpad does that on a
specially-secured signing service that ensures that keys are encrypted
at rest and such.  If memory serves, I asked for this to be added to
sbsigntool because the alternative was that we'd have to chase kernel
versions: sign-file is packaged as
/usr/lib/linux-kbuild-$version/scripts/sign-file in the
linux-kbuild-$version package, but that's really a pretty annoying thing
for a supposedly non-kernel-version-dependent service to have to depend
on!

dak has a similar requirement, and it seems that they've just ended up
with a dependency on "linux-kbuild-5.10 | linux-kbuild-4.19" that
presumably they bump from time to time.  Ugh.

Now I'm no longer involved with Launchpad, but I have a pretty similar
third instance of this requirement in debusine, and I'd really rather
not perpetuate the same horribleness there.  Is there any chance that
these Ubuntu patches could be merged?

Thanks,

-- 
Colin Watson (he/him)  [cjwat...@debian.org]

Bug#1074759: O: aiodns -- Asynchronous DNS resolver library for Python 3

[Scott Kitterman]

Package: wnpp
Severity: normal
X-Debbugs-Cc: aio...@packages.debian.org, debian-pyt...@lists.debian.org
Control: affects -1 + src:aiodns

I intend to orphan the aiodns package.

The package description is:
 aiodns provides a simple way for doing asynchronous DNS resolutions with a
 synchronous looking interface, using pycares.

I am no longer interested in maintaining this package and the other
theorectical uploader is long inactive.

Scott K

Bug#1074758: O: pycares -- Python interface for c-ares (common documentation)

[Scott Kitterman]

Package: wnpp
Severity: normal
X-Debbugs-Cc: pyca...@packages.debian.org, debian-pyt...@lists.debian.org
Control: affects -1 + src:pycares

I intend to orphan the pycares package.

The package description is:
 pycares is a Python 3 module which provides an interface to c-ares. c-ares is
 a C library that performs DNS requests and name resolutions asynchronously.

I no longer have interest in maintaining it and the other theorectical
uploader is long inactive.

Scott K

Bug#1074660: python-mapnik: FTBFS: FileNotFoundError: [Errno 2] No such file or directory: 'mapnik-config'

[Sebastiaan Couwenberg]

reopen 1069130
tags 1069130 - patch
tags 1069130 + trixie sid
tags 1074660 + upstream
merge 1069130 1074660
thanks

On 7/2/24 2:51 PM, Lucas Nussbaum wrote:

FileNotFoundError: [Errno 2] No such file or directory: 'mapnik-config'
The CMake build of Mapnik 4.0 no longer provides mapnik-config, only the 
SCons build still does that.


We've patched the package to use pkg-config instead, but that FTBFS due 
to the switch from boost::optional to std:optional in Mapnik 4.0.0-rc2.


There is no word from upstream in the python-mapnik issues, so a fix 
will likely take a while. We might even remove python-mapnik and nik4 if 
it stays broken too long.


Kind Regards,

Bas

--
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1

Bug#1074757: nvram-wakeup: FTBFS: make[1]: *** [Makefile:77: guess-helper.mo] Error 1

[Lucas Nussbaum]

Source: nvram-wakeup
Version: 1.1-4
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240702 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 '/<>'
> Preparing cvs_revs.h
> gcc -O2 -Wall -Wstrict-prototypes -g -pedantic -D_GNU_SOURCE -Wdate-time 
> -D_FORTIFY_SOURCE=2  -c -o nvram-wakeup.o nvram-wakeup.c
> gcc -O2 -Wall -Wstrict-prototypes -g -pedantic -D_GNU_SOURCE -Wdate-time 
> -D_FORTIFY_SOURCE=2  -c -o nvram-wakeup-mb.o nvram-wakeup-mb.c
> gcc -O2 -Wall -Wstrict-prototypes -g -pedantic -D_GNU_SOURCE -Wdate-time 
> -D_FORTIFY_SOURCE=2  -c -o gmt-test.o gmt-test.c
> gcc -O2 -Wall -Wstrict-prototypes -g -pedantic -D_GNU_SOURCE -Wdate-time 
> -D_FORTIFY_SOURCE=2  -c -o byteops.o byteops.c
> gcc -O2 -Wall -Wstrict-prototypes -g -pedantic -D_GNU_SOURCE -Wdate-time 
> -D_FORTIFY_SOURCE=2  -c -o nvramops.o nvramops.c
> gcc -O2 -Wall -Wstrict-prototypes -g -pedantic -D_GNU_SOURCE -Wdate-time 
> -D_FORTIFY_SOURCE=2  -c -o bios.o bios.c
> bios.c: In function ‘__dmi_string’:
> bios.c:75:16: warning: cast from pointer to integer of different size 
> [-Wpointer-to-int-cast]
>75 |   if ( (int)bp >= (int)data ) return NULL; /* broken DMI 
> entry */
>   |^
> bios.c:75:27: warning: cast from pointer to integer of different size 
> [-Wpointer-to-int-cast]
>75 |   if ( (int)bp >= (int)data ) return NULL; /* broken DMI 
> entry */
>   |   ^
> bios.c: In function ‘__dmi_probe’:
> bios.c:139:26: warning: cast from pointer to integer of different size 
> [-Wpointer-to-int-cast]
>   139 | if ( (int)data - (int)entry >= size-4 ) break; /* 
> broken DMI euntry */
>   |  ^
> bios.c:139:38: warning: cast from pointer to integer of different size 
> [-Wpointer-to-int-cast]
>   139 | if ( (int)data - (int)entry >= size-4 ) break; /* 
> broken DMI euntry */
>   |  ^
> bios.c:143:54: warning: cast from pointer to integer of different size 
> [-Wpointer-to-int-cast]
>   143 |   i, (int)data - 
> (int)entry, dm->type, dm->size, dm->size );
>   |  ^
> bios.c:143:66: warning: cast from pointer to integer of different size 
> [-Wpointer-to-int-cast]
>   143 |   i, (int)data - 
> (int)entry, dm->type, dm->size, dm->size );
>   |  ^
> gcc -O2 -Wall -Wstrict-prototypes -g -pedantic -D_GNU_SOURCE -Wdate-time 
> -D_FORTIFY_SOURCE=2  -c -o tools.o tools.c
> tools.c: In function ‘xxd’:
> tools.c:170:110: warning: ‘__builtin___sprintf_chk’ may write a terminating 
> nul past the end of the destination [-Wformat-overflow=]
>   170 |   sprintf(out_line, "%06X0: %02X%02X %02X%02X %02X%02X 
> %02X%02X %02X%02X %02X%02X %02X%02X %02X%02X\n", i,
>   |   
>^
> In file included from /usr/include/stdio.h:964,
>  from tools.c:26:
> In function ‘sprintf’,
> inlined from ‘xxd’ at tools.c:170:11:
> /usr/include/x86_64-linux-gnu/bits/stdio2.h:30:10: note: 
> ‘__builtin___sprintf_chk’ output between 50 and 51 bytes into a destination 
> of size 50
>30 |   return __builtin___sprintf_chk (__s, __USE_FORTIFY_LEVEL - 1,
>   |  ^~
>31 |   __glibc_objsize (__s), __fmt,
>   |   ~
>32 |   __va_arg_pack ());
>   |   ~
> gcc -O2 -Wall -Wstrict-prototypes -g -pedantic -D_GNU_SOURCE -Wdate-time 
> -D_FORTIFY_SOURCE=2  -c -o readconf.o readconf.c
> readconf.c: In function ‘assign’:
> readconf.c:71:28: warning: cast from pointer to integer of different size 
> [-Wpointer-to-int-cast]
>71 |  int  * prev = (int *)((int)(&lnrs) + ((int)ptr - (int)b));
>   |^
> readconf.c:71:44: warning: cast from pointer to integer of different size 
> [-Wpointer-to-int-cast]
>71 |  int  * prev = (int *)((int)(&lnrs) + ((int)ptr - (int)b));
>   |^
> readconf.c:71:55: warning: cast from pointer to integer of different size 
> [-Wpointer-to-int-cast]
>  

Bug#1074756: theme-d: FTBFS: dh_auto_test: error: make -j8 check "TESTSUITEFLAGS=-j8 --verbose" VERBOSE=1 returned exit code 2

[Lucas Nussbaum]

Source: theme-d
Version: 5.1.2-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240702 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> make[4]: Entering directory '/<>/test-suite'
> GUILE_LOAD_PATH=..: GUILE_LOAD_COMPILED_PATH=..: 
> THEME_D_CONFIG_FILE=../theme-d-config-maint 
> ../theme-d/translator/theme-d-compile.scm -o package-tests/test1.tcp  
> package-tests/test1.thp
> GUILE_LOAD_PATH=..: GUILE_LOAD_COMPILED_PATH=..: 
> THEME_D_CONFIG_FILE=../theme-d-config-maint 
> ../theme-d/translator/theme-d-compile.scm -o package-tests/module1.tci  
> package-tests/module1.thi
> Unit compiled successfully.
> GUILE_LOAD_PATH=..: GUILE_LOAD_COMPILED_PATH=..: 
> THEME_D_CONFIG_FILE=../theme-d-config-maint 
> ../theme-d/translator/theme-d-compile.scm -o package-tests/test2.tcp  
> package-tests/test2.thp
> GUILE_LOAD_PATH=..: GUILE_LOAD_COMPILED_PATH=..: 
> THEME_D_CONFIG_FILE=../theme-d-config-maint 
> ../theme-d/translator/theme-d-compile.scm -o package-tests/module1.tcb  
> package-tests/module1.thb
> Unit compiled successfully.
> GUILE_LOAD_PATH=..: GUILE_LOAD_COMPILED_PATH=..: 
> THEME_D_CONFIG_FILE=../theme-d-config-maint 
> ../theme-d/translator/theme-d-link.scm -o package-tests/test1.go  
> package-tests/test1.tcp
> Unit compiled successfully.
> Unit compiled successfully.
> GUILE_LOAD_PATH=..: GUILE_LOAD_COMPILED_PATH=..: 
> THEME_D_CONFIG_FILE=../theme-d-config-maint 
> ../theme-d/translator/theme-d-link.scm -o package-tests/test2.go  
> package-tests/test2.tcp
> Backtrace:
> In language/tree-il/peval.scm:
> 833:6 19 (loop _ # #f values)
> 833:6 18 (loop _ # #f values)
> 833:6 17 (loop _ # #f values)
> 833:6 16 (loop _ # #f values)
> 833:6 15 (loop _ # #f values)
> 833:6 14 (loop _ # #f values)
> 833:6 13 (loop _ # #f values)
> 833:6 12 (loop _ # #f values)
> 833:6 11 (loop _ # #f values)
> 833:6 10 (loop _ # #f values)
> 833:6  9 (loop # (call (toplevel _i_make-param-proc-class) (const 0) (const 2) (primcall list 
> (call (toplevel make-tvar-object) (const 0)) (call (toplevel 
> make-tvar-object) (const 1))) (call (lambda () (lambda-case 
> (((&&&%result~2389 &&&%handler~2390) #f #f () () (_u_2_3_&&&%result~2389 
> _u_2_4_&&&%handler~2390)) (call (toplevel _i_make-procedure-type) (call 
> (toplevel _i_get-pair-class-general) (primcall list (toplevel _b_)…> 
> …)
>   1399:27  8 (loop _ _ #f value)
> In srfi/srfi-1.scm:
>586:17  7 (map1 (# (const 0) (const 2) (primcall list (call (toplevel make-tvar-object) (const 
> 0)) (call (toplevel make-tvar-object) (const 1))) (call (lambda () 
> (lambda-case (((&&&%result~2389 &&&%handler~2390) #f #f () () 
> (_u_2_3_&&&%result~2389 _u_2_4_&&&%handler~2390)) (call (toplevel 
> _i_make-procedure-type) (call (toplevel _i_get-pair-class-general) (primcall 
> list (toplevel _b_) (call (toplevel _i_get-pair-class-general) (p…> 
> …))
> In language/tree-il/peval.scm:
>   1558:45  6 (loop _ _ _ value)
> In srfi/srfi-1.scm:
>586:29  5 (map1 (# # # (primcall list (call (toplevel make-tvar-object) (const 0)) (call (toplevel 
> make-tvar-object) (const 1)))> # (((&&&%result~2389 &&&%handler~2390) #f #f () () (_u_2_3_&&&%result~2389 
> _u_2_4_&&&%handler~2390)) (call (toplevel _i_make-procedure-type) (call 
> (toplevel _i_get-pair-class-general) (primcall list (toplevel _b_) 
> (call (toplevel _i_get-pair-class-general) (primcall li…>))
>586:29  4 (map1 (# # (toplevel make-tvar-object) (const 0)) (call (toplevel make-tvar-object) 
> (const 1)))> # &&&%handler~2390) #f #f () () (_u_2_3_&&&%result~2389 
> _u_2_4_&&&%handler~2390)) (call (toplevel _i_make-procedure-type) (call 
> (toplevel _i_get-pair-class-general) (primcall list (toplevel _b_) 
> (call (toplevel _i_get-pair-class-general) (primcall list (call (toplevel 
> _i…>))
>586:29  3 (map1 (# make-tvar-object) (const 0)) (call (toplevel make-tvar-object) (const 1)))> 
> # #f #f () () (_u_2_3_&&&%result~2389 _u_2_4_&&&%handler~2390)) (call (toplevel 
> _i_make-procedure-type) (call (toplevel _i_get-pair-class-general) (primcall 
> list (toplevel _b_) (call (toplevel _i_get-pair-class-general) 
> (primcall list (call (toplevel _i_make-procedure-type)…>))
>586:17  2 (map1 (# (((&&&%result~2389 &&&%handler~2390) #f #f () () (_u_2_3_&&&%result~2389 
> _u_2_4_&&&%handler~2390)) (call (toplevel _i_make-procedure

Bug#1074755: razercfg: FTBFS: dh_install: error: missing files, aborting

[Lucas Nussbaum]

Source: razercfg
Version: 0.43-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240702 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 '/<>'
> dh_install --exclude=librazer.a
>   install -m0755 -d debian/razercfg//etc
>   cp --reflink=auto -a ./razer.conf debian/razercfg//etc/
>   install -m0755 -d debian/razercfg//etc/pm/sleep.d
>   cp --reflink=auto -a debian/tmp/etc/pm/sleep.d/50-razer 
> debian/razercfg//etc/pm/sleep.d/
>   install -m0755 -d debian/razercfg//usr/lib/systemd
>   cd 'debian/tmp/usr/lib/systemd/system/..' && find 'system' ! \( -regex 
> .\*librazer\\.a.\* \) \( -type f -or -type l \) -print0 | LC_ALL=C sort -z | 
> xargs -0 -I {} cp --reflink=auto --parents -dp {} 
> /<>/debian/razercfg//usr/lib/systemd/
>   cd 'debian/tmp/usr/lib/systemd/system/..' && find 'system' ! \( -regex 
> .\*librazer\\.a.\* \) \( -type d -and -empty \) -print0 | LC_ALL=C sort -z | 
> xargs -0 -I {} cp --reflink=auto --parents -a {} 
> /<>/debian/razercfg//usr/lib/systemd/
>   install -m0755 -d debian/razercfg/usr/lib/udev
>   cd 'debian/tmp/etc/udev/rules.d/..' && find 'rules.d' ! \( -regex 
> .\*librazer\\.a.\* \) \( -type f -or -type l \) -print0 | LC_ALL=C sort -z | 
> xargs -0 -I {} cp --reflink=auto --parents -dp {} 
> /<>/debian/razercfg/usr/lib/udev/
>   cd 'debian/tmp/etc/udev/rules.d/..' && find 'rules.d' ! \( -regex 
> .\*librazer\\.a.\* \) \( -type d -and -empty \) -print0 | LC_ALL=C sort -z | 
> xargs -0 -I {} cp --reflink=auto --parents -a {} 
> /<>/debian/razercfg/usr/lib/udev/
> dh_install: warning: Cannot find (any matches for) 
> "usr/local/lib/python3.11/dist-packages" (tried in ., debian/tmp)
> 
> dh_install: warning: razercfg missing files: 
> usr/local/lib/python3.11/dist-packages
> dh_install: error: missing files, aborting
> make[1]: *** [debian/rules:16: override_dh_install] Error 255


The full build log is available from:
http://qa-logs.debian.net/2024/07/02/razercfg_0.43-2_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240702;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20240702&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results

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

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

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

Bug#1074754: rust-breezyshim: FTBFS: dh_auto_test: error: /usr/share/cargo/bin/cargo build returned exit code 101

[Lucas Nussbaum]

Source: rust-breezyshim
Version: 0.1.92-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240702 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 cargo
>dh_update_autotools_config -O--buildsystem=cargo
>dh_autoreconf -O--buildsystem=cargo
>dh_auto_configure -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: linking /usr/share/cargo/registry/* into 
> /<>/debian/cargo_registry/
>dh_auto_build -O--buildsystem=cargo
>dh_auto_test -O--buildsystem=cargo
> debian cargo wrapper: options, profiles, parallel, lto: ['parallel=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 get `chrono` as a dependency of package `breezyshim v0.1.92 
> (/<>)`
> 
> Caused by:
>   failed to load source for dependency `chrono`
> 
> Caused by:
>   Unable to update registry `crates-io`
> 
> Caused by:
>   failed to update replaced source registry `crates-io`
> 
> Caused by:
>   failed to parse manifest at 
> `/<>/debian/cargo_registry/pyo3-filelike-0.2.0/Cargo.toml`
> 
> Caused by:
>   dependency (pyo3) specified without providing a local path, Git repository, 
> version, or workspace dependency to use
> 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/07/02/rust-breezyshim_0.1.92-1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240702;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20240702&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results

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

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

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

Bug#1074752: cura: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && make -j8 test ARGS\+=--verbose ARGS\+=-j8 returned exit code 2

[Lucas Nussbaum]

Source: cura
Version: 5.0.0-3
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240702 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> make[2]: Entering directory '/<>/obj-x86_64-linux-gnu'
> Running tests...
> /usr/bin/ctest --force-new-ctest-process --verbose -j8
> UpdateCTestConfiguration  from 
> :/<>/obj-x86_64-linux-gnu/DartConfiguration.tcl
> Parse Config file:/<>/obj-x86_64-linux-gnu/DartConfiguration.tcl
> UpdateCTestConfiguration  from 
> :/<>/obj-x86_64-linux-gnu/DartConfiguration.tcl
> Parse Config file:/<>/obj-x86_64-linux-gnu/DartConfiguration.tcl
> Test project /<>/obj-x86_64-linux-gnu
> Constructing a list of tests
> Done constructing a list of tests
> Updating test list for fixtures
> Added 0 tests to meet fixture requirements
> Checking test dependency graph...
> Checking test dependency graph end
> test 1
>   Start  1: invalid-imports
> 
> 1: Test command: /usr/bin/python3 "scripts/check_invalid_imports.py"
> 1: Working Directory: /<>
> 1: Test timeout computed to be: 1500
> test 2
>   Start  2: pytest-main
> 
> 2: Test command: /usr/bin/python3 "-m" "pytest" 
> "--junitxml=/<>/obj-x86_64-linux-gnu/junit-pytest-main.xml" 
> "/<>/tests"
> 2: Working Directory: /<>/obj-x86_64-linux-gnu
> 2: Environment variables: 
> 2:  PYTHONPATH=/<>:/usr/share/uranium:
> 2: Test timeout computed to be: 1500
> test 3
>   Start  3: pytest-DigitalLibrary
> 
> 3: Test command: /usr/bin/python3 "-m" "pytest" 
> "--junitxml=/<>/obj-x86_64-linux-gnu/junit-pytest-DigitalLibrary.xml"
>  "/<>/plugins/DigitalLibrary"
> 3: Working Directory: /<>/obj-x86_64-linux-gnu
> 3: Environment variables: 
> 3:  
> PYTHONPATH=/<>/plugins/DigitalLibrary:/<>:/usr/share/uranium:
> 3: Test timeout computed to be: 1500
> test 4
>   Start  4: pytest-FirmwareUpdateChecker
> 
> 4: Test command: /usr/bin/python3 "-m" "pytest" 
> "--junitxml=/<>/obj-x86_64-linux-gnu/junit-pytest-FirmwareUpdateChecker.xml"
>  "/<>/plugins/FirmwareUpdateChecker"
> 4: Working Directory: /<>/obj-x86_64-linux-gnu
> 4: Environment variables: 
> 4:  
> PYTHONPATH=/<>/plugins/FirmwareUpdateChecker:/<>:/usr/share/uranium:
> 4: Test timeout computed to be: 1500
> test 5
>   Start  5: pytest-LegacyProfileReader
> 
> 5: Test command: /usr/bin/python3 "-m" "pytest" 
> "--junitxml=/<>/obj-x86_64-linux-gnu/junit-pytest-LegacyProfileReader.xml"
>  "/<>/plugins/LegacyProfileReader"
> 5: Working Directory: /<>/obj-x86_64-linux-gnu
> 5: Environment variables: 
> 5:  
> PYTHONPATH=/<>/plugins/LegacyProfileReader:/<>:/usr/share/uranium:
> 5: Test timeout computed to be: 1500
> test 6
>   Start  6: pytest-PostProcessingPlugin
> 
> 6: Test command: /usr/bin/python3 "-m" "pytest" 
> "--junitxml=/<>/obj-x86_64-linux-gnu/junit-pytest-PostProcessingPlugin.xml"
>  "/<>/plugins/PostProcessingPlugin"
> 6: Working Directory: /<>/obj-x86_64-linux-gnu
> 6: Environment variables: 
> 6:  
> PYTHONPATH=/<>/plugins/PostProcessingPlugin:/<>:/usr/share/uranium:
> 6: Test timeout computed to be: 1500
> test 7
>   Start  7: pytest-VersionUpgrade25to26
> 
> 7: Test command: /usr/bin/python3 "-m" "pytest" 
> "--junitxml=/<>/obj-x86_64-linux-gnu/junit-pytest-VersionUpgrade25to26.xml"
>  "/<>/plugins/VersionUpgrade/VersionUpgrade25to26"
> 7: Working Directory: /<>/obj-x86_64-linux-gnu
> 7: Environment variables: 
> 7:  
> PYTHONPATH=/<>/plugins/VersionUpgrade/VersionUpgrade25to26:/<>:/usr/share/uranium:
> 7: Test timeout computed to be: 1500
> test 8
>   Start  8: pytest-VersionUpgrade26to27
> 
> 8: Test command: /usr/bin/python3 "-m" "pytest" 
> "--junitxml=/<>/obj-x86_64-linux-gnu/junit-pytest-VersionUpgrade26to27.xml"
>  "/<>/plugins/VersionUpgrade/VersionUpgrade26to27"
> 8: Working Directory: /<>/obj-x86_64-linux-gnu
> 8: Environment variables: 
> 8:  
> PYTHONPATH=/<>/plugins/VersionUpgrade/VersionUpgrade26to27:/<>:/usr/share/uranium:
> 8: Test timeout computed to be: 1500
>  1/14 Test  #1: invalid-imports ..   Passed0.19 sec
> test 9
>   Start  9: pytest-VersionUpgrade2

Bug#1074753: mate-power-manager: FTBFS: make[4]: *** [Makefile:224: hu.gmo] Error 1

[Lucas Nussbaum]

Source: mate-power-manager
Version: 1.26.1-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240702 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> make[4]: Entering directory '/<>/po'
> /usr/bin/msgmerge --update --quiet  --lang=af --previous af.po 
> mate-power-manager.pot
> /usr/bin/msgmerge --update --quiet  --lang=ar --previous ar.po 
> mate-power-manager.pot
> /usr/bin/msgmerge --update --quiet  --lang=am --previous am.po 
> mate-power-manager.pot
> /usr/bin/msgmerge --update --quiet  --lang=as --previous as.po 
> mate-power-manager.pot
> /usr/bin/msgmerge --update --quiet  --lang=ast --previous ast.po 
> mate-power-manager.pot
> /usr/bin/msgmerge --update --quiet  --lang=az --previous az.po 
> mate-power-manager.pot
> /usr/bin/msgmerge --update --quiet  --lang=be --previous be.po 
> mate-power-manager.pot
> /usr/bin/msgmerge --update --quiet  --lang=bg --previous bg.po 
> mate-power-manager.pot
> /usr/bin/msgmerge --update --quiet  --lang=bn_IN --previous bn_IN.po 
> mate-power-manager.pot
> /usr/bin/msgmerge --update --quiet  --lang=bn --previous bn.po 
> mate-power-manager.pot
> /usr/bin/msgmerge --update --quiet  --lang=br --previous br.po 
> mate-power-manager.pot
> /usr/bin/msgmerge --update --quiet  --lang=ca --previous ca.po 
> mate-power-manager.pot
> /usr/bin/msgmerge --update --quiet  --lang=bs --previous bs.po 
> mate-power-manager.pot
> /usr/bin/msgmerge --update --quiet  --lang=crh --previous crh.po 
> mate-power-manager.pot
> /usr/bin/msgmerge --update --quiet  --lang=cmn --previous cmn.po 
> mate-power-manager.pot
> /usr/bin/msgmerge --update --quiet  --lang=ca@valencia --previous 
> c...@valencia.po mate-power-manager.pot
> /usr/bin/msgmerge --update --quiet  --lang=cs --previous cs.po 
> mate-power-manager.pot
> /usr/bin/msgmerge --update --quiet  --lang=cy --previous cy.po 
> mate-power-manager.pot
> /usr/bin/msgmerge --update --quiet  --lang=da --previous da.po 
> mate-power-manager.pot
> /usr/bin/msgmerge --update --quiet  --lang=dz --previous dz.po 
> mate-power-manager.pot
> /usr/bin/msgmerge --update --quiet  --lang=en_AU --previous en_AU.po 
> mate-power-manager.pot
> /usr/bin/msgmerge --update --quiet  --lang=el --previous el.po 
> mate-power-manager.pot
> /usr/bin/msgmerge --update --quiet  --lang=de --previous de.po 
> mate-power-manager.pot
> /usr/bin/msgmerge --update --quiet  --lang=en_CA --previous en_CA.po 
> mate-power-manager.pot
> /usr/bin/msgmerge --update --quiet  --lang=en_GB --previous en_GB.po 
> mate-power-manager.pot
> /usr/bin/msgmerge --update --quiet  --lang=en_US --previous en_US.po 
> mate-power-manager.pot
> /usr/bin/msgmerge --update --quiet  --lang=eo --previous eo.po 
> mate-power-manager.pot
> /usr/bin/msgmerge --update --quiet  --lang=es --previous es.po 
> mate-power-manager.pot
> /usr/bin/msgmerge --update --quiet  --lang=es_AR --previous es_AR.po 
> mate-power-manager.pot
> /usr/bin/msgmerge --update --quiet  --lang=es_CL --previous es_CL.po 
> mate-power-manager.pot
> /usr/bin/msgmerge --update --quiet  --lang=es_CO --previous es_CO.po 
> mate-power-manager.pot
> /usr/bin/msgmerge --update --quiet  --lang=es_CR --previous es_CR.po 
> mate-power-manager.pot
> /usr/bin/msgmerge --update --quiet  --lang=es_DO --previous es_DO.po 
> mate-power-manager.pot
> /usr/bin/msgmerge --update --quiet  --lang=es_EC --previous es_EC.po 
> mate-power-manager.pot
> /usr/bin/msgmerge --update --quiet  --lang=es_ES --previous es_ES.po 
> mate-power-manager.pot
> /usr/bin/msgmerge --update --quiet  --lang=es_NI --previous es_NI.po 
> mate-power-manager.pot
> /usr/bin/msgmerge --update --quiet  --lang=es_MX --previous es_MX.po 
> mate-power-manager.pot
> /usr/bin/msgmerge --update --quiet  --lang=es_PE --previous es_PE.po 
> mate-power-manager.pot
> /usr/bin/msgmerge --update --quiet  --lang=es_PA --previous es_PA.po 
> mate-power-manager.pot
> /usr/bin/msgmerge --update --quiet  --lang=es_PR --previous es_PR.po 
> mate-power-manager.pot
> /usr/bin/msgmerge --update --quiet  --lang=es_SV --previous es_SV.po 
> mate-power-manager.pot
> /usr/bin/msgmerge --update --quiet  --lang=es_UY --previous es_UY.po 
> mate-power-manager.pot
> /usr/bin/msgmerge --update --quiet  --lang=es_VE --previous es_VE.po 
> mate-power-manager.pot
> /usr/bin/msgmerge --update --quiet  --lang=et --previous et.po 
> mate-power-manager.pot
> /usr/bin/msgmerge --update --quiet  --lang=eu --previous eu.po 
> mate-power-manager.pot
> /usr/bin/msgmerge --update --quiet  --lang=fa --previous fa.po 
> mate-power-manager.pot
> /usr/bin/msgmerge --update --quiet  --lan

Bug#1074750: vanguards: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.11 3.12" --system=custom "--test-args=cd {build_dir}; python3 -m pytest /<>/tests

[Lucas Nussbaum]

Source: vanguards
Version: 0.3.1-2.4
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240702 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 '/<>'
> dh_auto_test -- --system=custom --test-args='cd {build_dir}; python3 -m 
> pytest /<>/tests'
> I: pybuild base:311: cd /<>/.pybuild/cpython3_3.11/build; 
> python3 -m pytest /<>/tests
> = test session starts 
> ==
> platform linux -- Python 3.12.4, pytest-8.2.2, pluggy-1.5.0
> rootdir: /<>
> collected 9 items / 1 error
> 
>  ERRORS 
> 
> _ ERROR collecting tests/test_main.py 
> __
> ImportError while importing test module '/<>/tests/test_main.py'.
> Hint: make sure your test modules/packages have valid Python names.
> Traceback:
> vanguards/config.py:17: in 
> from configparser import SafeConfigParser, Error
> E   ImportError: cannot import name 'SafeConfigParser' from 'configparser' 
> (/usr/lib/python3.12/configparser.py). Did you mean: 'RawConfigParser'?
> 
> During handling of the above exception, another exception occurred:
> /usr/lib/python3.12/importlib/__init__.py:90: in import_module
> return _bootstrap._gcd_import(name[level:], package, level)
> ../../../tests/test_main.py:9: in 
> import vanguards.config
> vanguards/config.py:19: in 
> from ConfigParser import SafeConfigParser, Error
> E   ModuleNotFoundError: No module named 'ConfigParser'
> === short test summary info 
> 
> ERROR ../../../tests/test_main.py
>  Interrupted: 1 error during collection 
> 
> === 1 error in 0.37s 
> ===
> E: pybuild pybuild:389: test: plugin custom failed with: exit code=2: cd 
> /<>/.pybuild/cpython3_3.11/build; python3 -m pytest 
> /<>/tests
> I: pybuild base:311: cd /<>/.pybuild/cpython3_3.12/build; 
> python3 -m pytest /<>/tests
> = test session starts 
> ==
> platform linux -- Python 3.12.4, pytest-8.2.2, pluggy-1.5.0
> rootdir: /<>
> collected 9 items / 1 error
> 
>  ERRORS 
> 
> _ ERROR collecting tests/test_main.py 
> __
> ImportError while importing test module '/<>/tests/test_main.py'.
> Hint: make sure your test modules/packages have valid Python names.
> Traceback:
> vanguards/config.py:17: in 
> from configparser import SafeConfigParser, Error
> E   ImportError: cannot import name 'SafeConfigParser' from 'configparser' 
> (/usr/lib/python3.12/configparser.py). Did you mean: 'RawConfigParser'?
> 
> During handling of the above exception, another exception occurred:
> /usr/lib/python3.12/importlib/__init__.py:90: in import_module
> return _bootstrap._gcd_import(name[level:], package, level)
> ../../../tests/test_main.py:9: in 
> import vanguards.config
> vanguards/config.py:19: in 
> from ConfigParser import SafeConfigParser, Error
> E   ModuleNotFoundError: No module named 'ConfigParser'
> === short test summary info 
> 
> ERROR ../../../tests/test_main.py
>  Interrupted: 1 error during collection 
> 
> === 1 error in 0.30s 
> ===
> E: pybuild pybuild:389: test: plugin custom failed with: exit code=2: cd 
> /<>/.pybuild/cpython3_3.12/build; python3 -m pytest 
> /<>/tests
> dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.11 
> 3.12" --system=custom "--test-args=cd {build_dir}; python3 -m pytest 
> /<>/tests" returned exit code 13


The full build log is available from:
http://qa-logs.debian.net/2024/07/02/vanguards_0.3.1-2.4_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240702;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20240702&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results

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

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

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

Bug#1074748: meep-openmpi: FTBFS: dh_install: error: missing files, aborting

[Lucas Nussbaum]

Source: meep-openmpi
Version: 1.25.0-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240702 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> make[4]: Entering directory '/<>'
> make[4]: Nothing to be done for 'install-exec-am'.
>  /usr/bin/mkdir -p 
> '/<>/debian/tmp/usr/lib/x86_64-linux-gnu/pkgconfig'
>  /usr/bin/install -c -m 644 meep.pc 
> '/<>/debian/tmp/usr/lib/x86_64-linux-gnu/pkgconfig'
> make[4]: Leaving directory '/<>'
> make[3]: Leaving directory '/<>'
> make[2]: Leaving directory '/<>'
> find
> .
> ./autogen.sh
> ./config.h.in
> ./config.status
> ./COPYRIGHT
> ./codemeta.json
> ./AUTHORS
> ./README.md
> ./LICENSE
> ./.travis.yml
> ./meep.pc
> ./src
> ./src/update_eh.lo
> ./src/random.lo
> ./src/GDSIIgeom.lo
> ./src/dft_ldos.cpp
> ./src/multilevel-atom.o
> ./src/energy_and_flux.lo
> ./src/bands.lo
> ./src/array_slice.o
> ./src/initialize.lo
> ./src/step_generic_stride1.lo
> ./src/array_slice.cpp
> ./src/step_generic.cpp
> ./src/loop_in_chunks.lo
> ./src/libmeep.la
> ./src/material_data.hpp
> ./src/vec.o
> ./src/structure_dump.lo
> ./src/sphere_quad
> ./src/bicgstab.lo
> ./src/h5fields.o
> ./src/step_generic_stride1.cpp
> ./src/stress.cpp
> ./src/boundaries.lo
> ./src/bands.o
> ./src/near2far.cpp
> ./src/step_generic.lo
> ./src/integrate2.o
> ./src/time.lo
> ./src/cw_fields.o
> ./src/adjust_verbosity.hpp
> ./src/.libs
> ./src/.libs/multilevel-atom.o
> ./src/.libs/array_slice.o
> ./src/.libs/libmeep.la
> ./src/.libs/vec.o
> ./src/.libs/h5fields.o
> ./src/.libs/bands.o
> ./src/.libs/integrate2.o
> ./src/.libs/libmeep.so
> ./src/.libs/cw_fields.o
> ./src/.libs/dft.o
> ./src/.libs/loop_in_chunks.o
> ./src/.libs/GDSIIgeom.o
> ./src/.libs/integrate.o
> ./src/.libs/fields.o
> ./src/.libs/structure_dump.o
> ./src/.libs/libmeep.lai
> ./src/.libs/step_generic_stride1.o
> ./src/.libs/mympi.o
> ./src/.libs/sources.o
> ./src/.libs/monitor.o
> ./src/.libs/casimir.o
> ./src/.libs/update_eh.o
> ./src/.libs/libmeep.so.30
> ./src/.libs/fix_boundary_sources.o
> ./src/.libs/structure.o
> ./src/.libs/boundaries.o
> ./src/.libs/step_generic.o
> ./src/.libs/libmeep.so.30.0.0
> ./src/.libs/anisotropic_averaging.o
> ./src/.libs/near2far.o
> ./src/.libs/meepgeom.o
> ./src/.libs/energy_and_flux.o
> ./src/.libs/susceptibility.o
> ./src/.libs/h5file.o
> ./src/.libs/fields_dump.o
> ./src/.libs/step_db.o
> ./src/.libs/initialize.o
> ./src/.libs/mpb.o
> ./src/.libs/bicgstab.o
> ./src/.libs/output_directory.o
> ./src/.libs/material_data.o
> ./src/.libs/time.o
> ./src/.libs/dft_ldos.o
> ./src/.libs/step.o
> ./src/.libs/update_pols.o
> ./src/.libs/random.o
> ./src/.libs/stress.o
> ./src/.libs/libmeep.a
> ./src/material_data.lo
> ./src/dft.o
> ./src/loop_in_chunks.o
> ./src/GDSIIgeom.o
> ./src/integrate.o
> ./src/fields.o
> ./src/structure_dump.o
> ./src/step_db.lo
> ./src/h5file.cpp
> ./src/meepgeom.lo
> ./src/structure.cpp
> ./src/sphere-quad.cpp
> ./src/step_generic_stride1.o
> ./src/fields.lo
> ./src/output_directory.cpp
> ./src/h5fields.cpp
> ./src/monitor.cpp
> ./src/mympi.o
> ./src/dft.lo
> ./src/initialize.cpp
> ./src/sources.o
> ./src/monitor.o
> ./src/sphere-quad.h
> ./src/update_pols.cpp
> ./src/h5fields.lo
> ./src/vec.lo
> ./src/structure.lo
> ./src/dft_ldos.lo
> ./src/mympi.cpp
> ./src/meepgeom.hpp
> ./src/update_pols.lo
> ./src/casimir.o
> ./src/fields_dump.cpp
> ./src/mympi.lo
> ./src/susceptibility.cpp
> ./src/update_eh.o
> ./src/structure_dump.cpp
> ./src/bands.cpp
> ./src/integrate.cpp
> ./src/boundaries.cpp
> ./src/fields.cpp
> ./src/loop_in_chunks.cpp
> ./src/fix_boundary_sources.o
> ./src/material_data.cpp
> ./src/structure.o
> ./src/Makefile.in
> ./src/bicgstab.cpp
> ./src/boundaries.o
> ./src/integrate.lo
> ./src/step_generic.o
> ./src/anisotropic_averaging.o
> ./src/mpb.lo
> ./src/near2far.o
> ./src/fields_dump.lo
> ./src/meepgeom.o
> ./src/energy_and_flux.o
> ./src/dft.cpp
> ./src/random.cpp
> ./src/susceptibility.o
> ./src/casimir.lo
> ./src/Makefile
> ./src/h5file.lo
> ./src/h5file.o
> ./src/meep.hpp
> ./src/update_eh.cpp
> ./src/fields_dump.o
> ./src/step_db.o
> ./src/Makefile.am
> ./src/initialize.o
> ./src/cw_fields.cpp
> ./src/mpb.o
> ./src/GDSIIgeom.cpp
> ./src/meepgeom.cpp
> ./src/time.cpp
> ./src/cw_fields.lo
> ./src/integrate2.cpp
> .

Bug#1074747: mate-panel: FTBFS: make[4]: *** [Makefile:1040: org.mate.panel.TestApplet.mate-panel-applet] Error 1

[Lucas Nussbaum]

Source: mate-panel
Version: 1.27.1-4
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240702 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> make[4]: Entering directory '/<>/libmate-panel-applet'
> gcc -DHAVE_CONFIG_H -I. -I..  -I/usr/include/gtk-3.0 -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/sysprof-6 -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/gio-unix-2.0 -I/usr/include/cloudproviders 
> -I/usr/include/atk-1.0 -I/usr/include/at-spi2-atk/2.0 
> -I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0 
> -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -pthread  
> -I../libmate-panel-applet -DMATELOCALEDIR=\""/usr/share/locale"\"  
> -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Wmissing-prototypes -g -O2 
> -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -fstack-clash-protection -Wformat 
> -Werror=format-security -fcf-protection -c -o test-dbus-applet.o 
> test-dbus-applet.c
> /bin/bash ../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I. -I..  
> -I/usr/include/gtk-3.0 -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/sysprof-6 
> -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/gio-unix-2.0 -I/usr/include/cloudproviders 
> -I/usr/include/atk-1.0 -I/usr/include/at-spi2-atk/2.0 
> -I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0 
> -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -pthread  
> -I../libmate-panel-applet -DMATELOCALEDIR=\""/usr/share/locale"\"  
> -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Wmissing-prototypes -g -O2 
> -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -fstack-clash-protection -Wformat 
> -Werror=format-security -fcf-protection -c -o mate-panel-applet-enums.lo 
> mate-panel-applet-enums.c
> /bin/bash ../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I. -I..  
> -I/usr/include/gtk-3.0 -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/sysprof-6 
> -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/gio-unix-2.0 -I/usr/include/cloudproviders 
> -I/usr/include/atk-1.0 -I/usr/include/at-spi2-atk/2.0 
> -I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0 
> -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -pthread  
> -I../libmate-panel-applet -DMATELOCALEDIR=\""/usr/share/locale"\"  
> -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Wmissing-prototypes -g -O2 
> -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -fstack-clash-protection -Wformat 
> -Werror=format-security -fcf-protection -c -o mate-panel-applet-marshal.lo 
> mate-panel-applet-marshal.c
> /bin/bash ../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I. -I..  
> -I/usr/include/gtk-3.0 -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/sysprof-6 
> -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/gio-unix-2.0 -I/usr/include/cloudproviders 
> -I/usr/include/atk-1.0 -I/usr/include/at-spi2-atk/2.0 
> -I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0 
> -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -pthread  
> -I../libmate-panel-applet -DMATELOCALEDIR=\""/usr/share/locale"\"  
> -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Wmissing-prototypes -g -O2 
> -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -fstack-clash-protection -Wformat 
> -Werror=format-security -fcf-protection -c -o mate-panel-applet.lo 
>

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

[Lucas Nussbaum]

Source: python-skbio
Version: 0.6.1-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240702 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 '/<>'
> echo No testing for the -doc package
> No testing for the -doc package
> make[1]: Leaving directory '/<>'
>dh_auto_test -O--buildsystem=pybuild -Npython-skbio-doc
> I: pybuild base:311: cd /<>/.pybuild/cpython3_3.11_skbio/build; 
> python3.11 -m pytest 
> = test session starts 
> ==
> platform linux -- Python 3.11.9, pytest-8.2.2, pluggy-1.5.0
> rootdir: /<>/.pybuild/cpython3_3.11_skbio/build
> configfile: pyproject.toml
> collected 2761 items
> 
> skbio/alignment/tests/test_pairwise.py . [  
> 0%]
> skbio/alignment/tests/test_path.py . [  
> 1%]
> skbio/alignment/tests/test_ssw.py ...[  
> 2%]
> skbio/alignment/tests/test_tabular_msa.py .. [  
> 3%]
>  [  
> 6%]
>  [  
> 8%]
>  [ 
> 11%]
>  [ 
> 14%]
>  [ 
> 16%]
> ...  [ 
> 17%]
> skbio/diversity/alpha/tests/test_ace.py ..   [ 
> 17%]
> skbio/diversity/alpha/tests/test_base.py .F..[ 
> 18%]
> skbio/diversity/alpha/tests/test_chao1.py ...[ 
> 18%]
> skbio/diversity/alpha/tests/test_gini.py [ 
> 18%]
> skbio/diversity/alpha/tests/test_lladser.py  [ 
> 18%]
> skbio/diversity/alpha/tests/test_pd.py   [ 
> 19%]
> skbio/diversity/beta/tests/test_unifrac.py   [ 
> 20%]
> skbio/diversity/tests/test_block.py ...  [ 
> 20%]
> skbio/diversity/tests/test_driver.py ... [ 
> 22%]
> ..   [ 
> 22%]
> skbio/diversity/tests/test_util.py   [ 
> 22%]
> skbio/embedding/tests/test_embedding.py ...  [ 
> 23%]
> skbio/embedding/tests/test_protein.py .. [ 
> 23%]
> skbio/io/format/tests/test_base.py   [ 
> 25%]
> skbio/io/format/tests/test_binary_dm.py .[ 
> 25%]
> skbio/io/format/tests/test_biom.py ...   [ 
> 25%]
> skbio/io/format/tests/test_blast6.py ... [ 
> 25%]
> skbio/io/format/tests/test_blast7.py ..  [ 
> 26%]
> skbio/io/format/tests/test_clustal.py .  [ 
> 26%]
> skbio/io/format/tests/test_embed.py  [ 
> 27%]
> skbio/io/format/tests/test_embl.py ...   [ 
> 28%]
> skbio/io/format/tests/test_emptyfile.py ..   [ 
> 28%]
> skbio/io/format/tests/test_fasta.py  [ 
> 28%]
> skbio/io/format/tests/test_fastq.py ...  [ 
> 29%]
> skbio/io/format/tests/test_genbank.py .  [ 
> 30%]
> skbio/io/format/tests/test_gff3.py   [ 
> 31%]
> skbio/io/format/tests/test_lsmat.py ...  [ 
> 31%]
> skbio/io/format/tests/test_newick.py ... [ 
> 31%]
> skbio/io/format/tests/test_ordination.py .   [ 
> 31%]
> skbio/io/format/tests/test_phylip.py ... [ 
> 32%]
> skbio/io/format/tests/test_qseq.py ..[ 
> 32%]
> skbio/io/format/tests/test_sample_metadata.py    [ 
> 32%]
> skbio/io/format/tests/test_sequence_feature_vocabulary.py    [ 
> 32%]
> skbio/io/format/tests/test_stockholm.py  [ 
> 33%]
> ...  [ 
&

Bug#1074746: rust-rand-core: FTBFS: dh_auto_test: error: /usr/share/cargo/bin/cargo test --all returned exit code 101

[Lucas Nussbaum]

Source: rust-rand-core
Version: 0.6.4-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240702 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 '/<>'
> dh_auto_test -- test --all
> 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', 'test', '--verbose', '--verbose', 
> '-j8', '--target', 'x86_64-unknown-linux-gnu', '--all'],) {}
>Compiling rand_core v0.6.4 (/<>)
>  Running `CARGO=/usr/bin/cargo CARGO_CRATE_NAME=rand_core 
> CARGO_MANIFEST_DIR=/<> CARGO_PKG_AUTHORS='The Rand Project 
> Developers:The Rust Project Developers' CARGO_PKG_DESCRIPTION='Core random 
> number generator traits and tools for implementation.
> ' CARGO_PKG_HOMEPAGE='https://rust-random.github.io/book' 
> CARGO_PKG_LICENSE='MIT OR Apache-2.0' CARGO_PKG_LICENSE_FILE='' 
> CARGO_PKG_NAME=rand_core CARGO_PKG_README=README.md 
> CARGO_PKG_REPOSITORY='https://github.com/rust-random/rand' 
> CARGO_PKG_RUST_VERSION='' CARGO_PKG_VERSION=0.6.4 CARGO_PKG_VERSION_MAJOR=0 
> CARGO_PKG_VERSION_MINOR=6 CARGO_PKG_VERSION_PATCH=4 CARGO_PKG_VERSION_PRE='' 
> CARGO_PRIMARY_PACKAGE=1 CARGO_RUSTC_CURRENT_DIR=/<> 
> LD_LIBRARY_PATH=/<>/target/debug/deps rustc --crate-name 
> rand_core --edition=2018 src/lib.rs --error-format=json 
> --json=diagnostic-rendered-ansi,artifacts,future-incompat --crate-type lib 
> --emit=dep-info,metadata,link -C embed-bitcode=no -C debuginfo=2 -C 
> metadata=df9694816f2e8336 -C extra-filename=-df9694816f2e8336 --out-dir 
> /<>/target/x86_64-unknown-linux-gnu/debug/deps --target 
> x86_64-unknown-linux-gnu -C 
> incremental=/<>/target/x86_64-unknown-linux-gnu/debug/incremental
>  -L dependency=/<>/target/x86_64-unknown-linux-gnu/debug/deps -L 
> dependency=/<>/target/debug/deps -C debuginfo=2 -C strip=none 
> --cap-lints warn -C linker=x86_64-linux-gnu-gcc -C link-arg=-Wl,-z,relro 
> --remap-path-prefix 
> /<>=/usr/share/cargo/registry/rand-core-0.6.4 
> --remap-path-prefix 
> /<>/debian/cargo_registry=/usr/share/cargo/registry`
>  Running `CARGO=/usr/bin/cargo CARGO_CRATE_NAME=rand_core 
> CARGO_MANIFEST_DIR=/<> CARGO_PKG_AUTHORS='The Rand Project 
> Developers:The Rust Project Developers' CARGO_PKG_DESCRIPTION='Core random 
> number generator traits and tools for implementation.
> ' CARGO_PKG_HOMEPAGE='https://rust-random.github.io/book' 
> CARGO_PKG_LICENSE='MIT OR Apache-2.0' CARGO_PKG_LICENSE_FILE='' 
> CARGO_PKG_NAME=rand_core CARGO_PKG_README=README.md 
> CARGO_PKG_REPOSITORY='https://github.com/rust-random/rand' 
> CARGO_PKG_RUST_VERSION='' CARGO_PKG_VERSION=0.6.4 CARGO_PKG_VERSION_MAJOR=0 
> CARGO_PKG_VERSION_MINOR=6 CARGO_PKG_VERSION_PATCH=4 CARGO_PKG_VERSION_PRE='' 
> CARGO_PRIMARY_PACKAGE=1 CARGO_RUSTC_CURRENT_DIR=/<> 
> LD_LIBRARY_PATH=/<>/target/debug/deps rustc --crate-name 
> rand_core --edition=2018 src/lib.rs --error-format=json 
> --json=diagnostic-rendered-ansi,artifacts,future-incompat 
> --emit=dep-info,link -C embed-bitcode=no -C debuginfo=2 --test -C 
> metadata=86c09e0c772bbdc9 -C extra-filename=-86c09e0c772bbdc9 --out-dir 
> /<>/target/x86_64-unknown-linux-gnu/debug/deps --target 
> x86_64-unknown-linux-gnu -C 
> incremental=/<>/target/x86_64-unknown-linux-gnu/debug/incremental
>  -L dependency=/<>/target/x86_64-unknown-linux-gnu/debug/deps -L 
> dependency=/<>/target/debug/deps -C debuginfo=2 -C strip=none 
> --cap-lints warn -C linker=x86_64-linux-gnu-gcc -C link-arg=-Wl,-z,relro 
> --remap-path-prefix 
> /<>=/usr/share/cargo/registry/rand-core-0.6.4 
> --remap-path-prefix 
> /<>/debian/cargo_registry=/usr/share/cargo/registry`
> Finished `test` profile [unoptimized + debuginfo] target(s) in 1.33s
>  Running `CARGO=/usr/bin/cargo CARGO_MANIFEST_DIR=/<> 
> CARGO_PKG_AUTHORS='The Rand Project Developers:The Rust Project Developers' 
> CARGO_PKG_DESCRIPTION='Core random number generator traits and tools for 
> implementation.
> ' CARGO_PKG_HOMEPAGE='https://rust-random.github.io/book' 
> CARGO_PKG_LICENSE='MIT OR Apache-2.0' CA

Bug#1074743: nautilus-image-converter: FTBFS: make: *** [debian/rules:7: binary] Error 25

[Lucas Nussbaum]

Source: nautilus-image-converter
Version: 0.4.0-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240702 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
>dh_update_autotools_config
>dh_autoreconf
>dh_auto_configure
>   cd obj-x86_64-linux-gnu && DEB_PYTHON_INSTALL_LAYOUT=deb LC_ALL=C.UTF-8 
> meson setup .. --wrap-mode=nodownload --buildtype=plain --prefix=/usr 
> --sysconfdir=/etc --localstatedir=/var --libdir=lib/x86_64-linux-gnu 
> -Dpython.bytecompile=-1
> The Meson build system
> Version: 1.4.1
> Source dir: /<>
> Build dir: /<>/obj-x86_64-linux-gnu
> Build type: native build
> Project name: nautilus-image-converter
> Project version: 0.4.0
> C compiler for the host machine: cc (gcc 13.3.0 "cc (Debian 13.3.0-1) 13.3.0")
> C linker for the host machine: cc ld.bfd 2.42.50.20240625
> Host machine cpu family: x86_64
> Host machine cpu: x86_64
> Found pkg-config: YES (/usr/bin/pkg-config) 1.8.1
> Run-time dependency gtk4 found: YES 4.12.5
> Run-time dependency glib-2.0 found: YES 2.80.3
> Run-time dependency libnautilus-extension-4 found: YES 45.2.1
> Message: /usr/share
> Configuring config.h using configuration
> Program msgfmt found: YES (/usr/bin/msgfmt)
> Program msginit found: YES (/usr/bin/msginit)
> Program msgmerge found: YES (/usr/bin/msgmerge)
> Program xgettext found: YES (/usr/bin/xgettext)
> Build targets in project: 22
> NOTICE: Future-deprecated features used:
>  * 0.56.0: {'dependency.get_pkgconfig_variable'}
> 
> nautilus-image-converter 0.4.0
> 
>   User defined options
> buildtype : plain
> libdir: lib/x86_64-linux-gnu
> localstatedir : /var
> prefix: /usr
> sysconfdir: /etc
> wrap_mode : nodownload
> python.bytecompile: -1
> 
> Found ninja-1.12.1 at /usr/bin/ninja
>dh_auto_build
>   cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 ninja -j8 -v
> [1/23] /usr/bin/msgfmt -o po/ca/LC_MESSAGES/nautilus-image-converter.mo 
> ../po/ca.po
> [2/23] /usr/bin/msgfmt -o po/bg/LC_MESSAGES/nautilus-image-converter.mo 
> ../po/bg.po
> [3/23] /usr/bin/msgfmt -o po/cs/LC_MESSAGES/nautilus-image-converter.mo 
> ../po/cs.po
> [4/23] /usr/bin/msgfmt -o po/da/LC_MESSAGES/nautilus-image-converter.mo 
> ../po/da.po
> [5/23] /usr/bin/msgfmt -o po/de/LC_MESSAGES/nautilus-image-converter.mo 
> ../po/de.po
> [6/23] /usr/bin/msgfmt -o po/es/LC_MESSAGES/nautilus-image-converter.mo 
> ../po/es.po
> [7/23] /usr/bin/msgfmt -o po/fr/LC_MESSAGES/nautilus-image-converter.mo 
> ../po/fr.po
> FAILED: po/fr/LC_MESSAGES/nautilus-image-converter.mo 
> /usr/bin/msgfmt -o po/fr/LC_MESSAGES/nautilus-image-converter.mo ../po/fr.po
> ../po/fr.po: warning: Charset "" is not a portable encoding name.
>   Message conversion to user's charset might not work.
> /usr/bin/msgfmt: present charset "" is not a portable encoding name
> [8/23] /usr/bin/msgfmt -o po/gl/LC_MESSAGES/nautilus-image-converter.mo 
> ../po/gl.po
> [9/23] /usr/bin/msgfmt -o po/fi/LC_MESSAGES/nautilus-image-converter.mo 
> ../po/fi.po
> [10/23] /usr/bin/msgfmt -o po/hu/LC_MESSAGES/nautilus-image-converter.mo 
> ../po/hu.po
> [11/23] cc -Isrc/libnautilus-image-converter.so.p -Isrc -I../src -I. -I.. 
> -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include 
> -I/usr/include/sysprof-6 -I/usr/include/gtk-4.0 -I/usr/include/pango-1.0 
> -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/graphene-1.0 -I/usr/lib/x86_64-linux-gnu/graphene-1.0/include 
> -I/usr/include/nautilus -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 
> -Wall -Winvalid-pch -g -O2 -Werror=implicit-function-declaration 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection 
> -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread -mfpmath=sse -msse -msse2 -MD 
> -MQ src/libnautilus-image-converter.so.p/image-converter.c.o -MF 
> src/libnautilus-image-converter.so.p/image-converter.c.o.d -o 
> src/libnautilus-image-converter.so.p/image-converter.c.o -c 
> ../src/image-converter.c
> [12/23] cc -Isrc/libnautilus-image-converter.so.p -Isrc -I../src -I. -I.. 
> -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include 
> -I/usr/include/syspro

Bug#1074744: shim-signed: FTBFS: dpkg-deb: error: parsing file 'debian/shim-signed/DEBIAN/control' near line 7 package 'shim-signed':

[Lucas Nussbaum]

Source: shim-signed
Version: 1.43
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240702 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 '/<>'
> dpkg-query: no packages found matching shim-helpers-amd64-signed
> dh_gencontrol -- -v1.43+15.8-1 \
>   -Vshim:Version=15.8-1 \
>   -Vhelpers:Version=
> dpkg-gencontrol: warning: relation > is deprecated: use >> or >=
> dpkg-gencontrol: warning: relation > is deprecated: use >> or >=
> make[1]: Leaving directory '/<>'
>dh_md5sums
>dh_builddeb
> dpkg-deb: error: parsing file 'debian/shim-signed/DEBIAN/control' near line 7 
> package 'shim-signed':
>  'Depends' field, reference to 'shim-helpers-amd64-signed': version '=': 
> version number does not start with digit
> dpkg-deb: building package 'shim-signed-common' in 
> '../shim-signed-common_1.43+15.8-1_all.deb'.
> dh_builddeb: error: dpkg-deb --build debian/shim-signed .. returned exit code 
> 2
> dh_builddeb: error: Aborting due to earlier error
> make: *** [debian/rules:21: binary] Error 25


The full build log is available from:
http://qa-logs.debian.net/2024/07/02/shim-signed_1.43_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240702;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20240702&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results

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

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

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

Bug#1074740: meep-mpi-default: FTBFS: dh_install: error: missing files, aborting

[Lucas Nussbaum]

Source: meep-mpi-default
Version: 1.25.0-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240702 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> make[4]: Entering directory '/<>'
> make[4]: Nothing to be done for 'install-exec-am'.
>  /usr/bin/mkdir -p 
> '/<>/debian/tmp/usr/lib/x86_64-linux-gnu/pkgconfig'
>  /usr/bin/install -c -m 644 meep.pc 
> '/<>/debian/tmp/usr/lib/x86_64-linux-gnu/pkgconfig'
> make[4]: Leaving directory '/<>'
> make[3]: Leaving directory '/<>'
> make[2]: Leaving directory '/<>'
> find
> .
> ./autogen.sh
> ./config.h.in
> ./config.status
> ./COPYRIGHT
> ./codemeta.json
> ./AUTHORS
> ./README.md
> ./LICENSE
> ./.travis.yml
> ./meep.pc
> ./src
> ./src/update_eh.lo
> ./src/random.lo
> ./src/GDSIIgeom.lo
> ./src/dft_ldos.cpp
> ./src/multilevel-atom.o
> ./src/energy_and_flux.lo
> ./src/bands.lo
> ./src/array_slice.o
> ./src/initialize.lo
> ./src/step_generic_stride1.lo
> ./src/array_slice.cpp
> ./src/step_generic.cpp
> ./src/loop_in_chunks.lo
> ./src/libmeep.la
> ./src/material_data.hpp
> ./src/vec.o
> ./src/structure_dump.lo
> ./src/sphere_quad
> ./src/bicgstab.lo
> ./src/h5fields.o
> ./src/step_generic_stride1.cpp
> ./src/stress.cpp
> ./src/boundaries.lo
> ./src/bands.o
> ./src/near2far.cpp
> ./src/step_generic.lo
> ./src/integrate2.o
> ./src/time.lo
> ./src/cw_fields.o
> ./src/adjust_verbosity.hpp
> ./src/.libs
> ./src/.libs/multilevel-atom.o
> ./src/.libs/array_slice.o
> ./src/.libs/libmeep.la
> ./src/.libs/vec.o
> ./src/.libs/h5fields.o
> ./src/.libs/bands.o
> ./src/.libs/integrate2.o
> ./src/.libs/libmeep.so
> ./src/.libs/cw_fields.o
> ./src/.libs/dft.o
> ./src/.libs/loop_in_chunks.o
> ./src/.libs/GDSIIgeom.o
> ./src/.libs/integrate.o
> ./src/.libs/fields.o
> ./src/.libs/structure_dump.o
> ./src/.libs/libmeep.lai
> ./src/.libs/step_generic_stride1.o
> ./src/.libs/mympi.o
> ./src/.libs/sources.o
> ./src/.libs/monitor.o
> ./src/.libs/casimir.o
> ./src/.libs/update_eh.o
> ./src/.libs/libmeep.so.30
> ./src/.libs/fix_boundary_sources.o
> ./src/.libs/structure.o
> ./src/.libs/boundaries.o
> ./src/.libs/step_generic.o
> ./src/.libs/libmeep.so.30.0.0
> ./src/.libs/anisotropic_averaging.o
> ./src/.libs/near2far.o
> ./src/.libs/meepgeom.o
> ./src/.libs/energy_and_flux.o
> ./src/.libs/susceptibility.o
> ./src/.libs/h5file.o
> ./src/.libs/fields_dump.o
> ./src/.libs/step_db.o
> ./src/.libs/initialize.o
> ./src/.libs/mpb.o
> ./src/.libs/bicgstab.o
> ./src/.libs/output_directory.o
> ./src/.libs/material_data.o
> ./src/.libs/time.o
> ./src/.libs/dft_ldos.o
> ./src/.libs/step.o
> ./src/.libs/update_pols.o
> ./src/.libs/random.o
> ./src/.libs/stress.o
> ./src/.libs/libmeep.a
> ./src/material_data.lo
> ./src/dft.o
> ./src/loop_in_chunks.o
> ./src/GDSIIgeom.o
> ./src/integrate.o
> ./src/fields.o
> ./src/structure_dump.o
> ./src/step_db.lo
> ./src/h5file.cpp
> ./src/meepgeom.lo
> ./src/structure.cpp
> ./src/sphere-quad.cpp
> ./src/step_generic_stride1.o
> ./src/fields.lo
> ./src/output_directory.cpp
> ./src/h5fields.cpp
> ./src/monitor.cpp
> ./src/mympi.o
> ./src/dft.lo
> ./src/initialize.cpp
> ./src/sources.o
> ./src/monitor.o
> ./src/sphere-quad.h
> ./src/update_pols.cpp
> ./src/h5fields.lo
> ./src/vec.lo
> ./src/structure.lo
> ./src/dft_ldos.lo
> ./src/mympi.cpp
> ./src/meepgeom.hpp
> ./src/update_pols.lo
> ./src/casimir.o
> ./src/fields_dump.cpp
> ./src/mympi.lo
> ./src/susceptibility.cpp
> ./src/update_eh.o
> ./src/structure_dump.cpp
> ./src/bands.cpp
> ./src/integrate.cpp
> ./src/boundaries.cpp
> ./src/fields.cpp
> ./src/loop_in_chunks.cpp
> ./src/fix_boundary_sources.o
> ./src/material_data.cpp
> ./src/structure.o
> ./src/Makefile.in
> ./src/bicgstab.cpp
> ./src/boundaries.o
> ./src/integrate.lo
> ./src/step_generic.o
> ./src/anisotropic_averaging.o
> ./src/mpb.lo
> ./src/near2far.o
> ./src/fields_dump.lo
> ./src/meepgeom.o
> ./src/energy_and_flux.o
> ./src/dft.cpp
> ./src/random.cpp
> ./src/susceptibility.o
> ./src/casimir.lo
> ./src/Makefile
> ./src/h5file.lo
> ./src/h5file.o
> ./src/meep.hpp
> ./src/update_eh.cpp
> ./src/fields_dump.o
> ./src/step_db.o
> ./src/Makefile.am
> ./src/initialize.o
> ./src/cw_fields.cpp
> ./src/mpb.o
> ./src/GDSIIgeom.cpp
> ./src/meepgeom.cpp
> ./src/time.cpp
> ./src/cw_fields.lo
> ./src/integrate

Bug#1074742: org-roam: FTBFS: make[2]: *** [Makefile:84: texi] Error 255

[Lucas Nussbaum]

Source: org-roam
Version: 2.2.2-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240702 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> make[2]: Entering directory '/<>/doc'
> Loading /etc/emacs/site-start.d/00debian.el (source)...
> Loading /etc/emacs/site-start.d/50autoconf.el (source)...
> 
> Error: wrong-type-argument (consp nil)
>   mapbacktrace(#f(compiled-function (evald func args flags) # -0x147e755222517960>))
>   debug-early-backtrace()
>   debug-early(error (wrong-type-argument consp nil))
>   []
>   apply(#f(compiled-function (&optional async subtreep visible-only body-only 
> ext-plist) "Export current buffer to a Texinfo file.\n\nIf narrowing is 
> active in the current buffer, only export its\nnarrowed part.\n\nIf a region 
> is active, export that region.\n\nA non-nil optional argument ASYNC means the 
> process should happen\nasynchronously.  The resulting file should be 
> accessible through\nthe `org-export-stack' interface.\n\nWhen optional 
> argument SUBTREEP is non-nil, export the sub-tree\nat point, extracting 
> information from the headline properties\nfirst.\n\nWhen optional argument 
> VISIBLE-ONLY is non-nil, don't export\ncontents of hidden elements.\n\nWhen 
> optional argument BODY-ONLY is non-nil, only write code\nbetween 
> \"\\begin{document}\" and \"\\end{document}\".\n\nEXT-PLIST, when provided, 
> is a property list with external\nparameters overriding Org default settings, 
> but still inferior to\nfile-local settings.\n\nReturn output file's name." 
> (interactive nil) #) nil)
>   org-texinfo-export-to-texinfo()
>   funcall-interactively(org-texinfo-export-to-texinfo)
>   command-execute(org-texinfo-export-to-texinfo)
>   command-line-1(("-f" "package-initialize" "-l" "ox-extra" "-l" 
> "ox-texinfo+" "--eval" "(or (require 'org-man nil t) (require 'ol-man))" 
> "org-roam.org" "--eval" "(ox-extras-activate '(ignore-headlines))" "--eval" 
> "(setq indent-tabs-mode nil)" "--eval" "(setq org-src-preserve-indentation 
> nil)" "--funcall" "org-texinfo-export-to-texinfo"))
>   command-line()
>   normal-top-level()
> make[2]: *** [Makefile:84: texi] Error 255


The full build log is available from:
http://qa-logs.debian.net/2024/07/02/org-roam_2.2.2-1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240702;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20240702&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results

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

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

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

Bug#1074741: pyqi: FTBFS: make: *** [debian/rules:6: binary] Error 25

[Lucas Nussbaum]

Source: pyqi
Version: 0.3.2+dfsg-9
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240702 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 --with python3 --with linktree --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:311: python3.12 setup.py config 
> Only Python 3.9, 3.10 and 3.11 are supported.E: pybuild pybuild:389: 
> configure: plugin distutils failed with: exit code=1: python3.12 setup.py 
> config 
> dh_auto_configure: error: pybuild --configure -i python{version} -p 3.12 
> returned exit code 13
> make: *** [debian/rules:6: binary] Error 25


The full build log is available from:
http://qa-logs.debian.net/2024/07/02/pyqi_0.3.2+dfsg-9_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240702;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20240702&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results

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

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

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

Bug#1074738: rust-byte-slice-cast: FTBFS: dh_auto_test: error: /usr/share/cargo/bin/cargo test --all returned exit code 101

[Lucas Nussbaum]

Source: rust-byte-slice-cast
Version: 1.2.1-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240702 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 '/<>'
> dh_auto_test -- test --all
> 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', 'test', '--verbose', '--verbose', 
> '-j8', '--target', 'x86_64-unknown-linux-gnu', '--all'],) {}
>Compiling byte-slice-cast v1.2.1 (/<>)
>  Running `CARGO=/usr/bin/cargo CARGO_CRATE_NAME=byte_slice_cast 
> CARGO_MANIFEST_DIR=/<> CARGO_PKG_AUTHORS='Sebastian Dröge 
> ' CARGO_PKG_DESCRIPTION='Safely cast bytes slices 
> from/to slices of built-in fundamental numeric types' CARGO_PKG_HOMEPAGE='' 
> CARGO_PKG_LICENSE=MIT CARGO_PKG_LICENSE_FILE='' 
> CARGO_PKG_NAME=byte-slice-cast CARGO_PKG_README=README.md 
> CARGO_PKG_REPOSITORY='https://github.com/sdroege/bytes-num-slice-cast' 
> CARGO_PKG_RUST_VERSION='' CARGO_PKG_VERSION=1.2.1 CARGO_PKG_VERSION_MAJOR=1 
> CARGO_PKG_VERSION_MINOR=2 CARGO_PKG_VERSION_PATCH=1 CARGO_PKG_VERSION_PRE='' 
> CARGO_PRIMARY_PACKAGE=1 CARGO_RUSTC_CURRENT_DIR=/<> 
> LD_LIBRARY_PATH=/<>/target/debug/deps rustc --crate-name 
> byte_slice_cast --edition=2018 src/lib.rs --error-format=json 
> --json=diagnostic-rendered-ansi,artifacts,future-incompat --crate-type lib 
> --emit=dep-info,metadata,link -C embed-bitcode=no -C debuginfo=2 --cfg 
> 'feature="default"' --cfg 'feature="std"' -C metadata=550d559da2ec -C 
> extra-filename=-550d559da2ec --out-dir 
> /<>/target/x86_64-unknown-linux-gnu/debug/deps --target 
> x86_64-unknown-linux-gnu -C 
> incremental=/<>/target/x86_64-unknown-linux-gnu/debug/incremental
>  -L dependency=/<>/target/x86_64-unknown-linux-gnu/debug/deps -L 
> dependency=/<>/target/debug/deps -C debuginfo=2 -C strip=none 
> --cap-lints warn -C linker=x86_64-linux-gnu-gcc -C link-arg=-Wl,-z,relro 
> --remap-path-prefix 
> /<>=/usr/share/cargo/registry/byte-slice-cast-1.2.1 
> --remap-path-prefix 
> /<>/debian/cargo_registry=/usr/share/cargo/registry`
>  Running `CARGO=/usr/bin/cargo CARGO_CRATE_NAME=byte_slice_cast 
> CARGO_MANIFEST_DIR=/<> CARGO_PKG_AUTHORS='Sebastian Dröge 
> ' CARGO_PKG_DESCRIPTION='Safely cast bytes slices 
> from/to slices of built-in fundamental numeric types' CARGO_PKG_HOMEPAGE='' 
> CARGO_PKG_LICENSE=MIT CARGO_PKG_LICENSE_FILE='' 
> CARGO_PKG_NAME=byte-slice-cast CARGO_PKG_README=README.md 
> CARGO_PKG_REPOSITORY='https://github.com/sdroege/bytes-num-slice-cast' 
> CARGO_PKG_RUST_VERSION='' CARGO_PKG_VERSION=1.2.1 CARGO_PKG_VERSION_MAJOR=1 
> CARGO_PKG_VERSION_MINOR=2 CARGO_PKG_VERSION_PATCH=1 CARGO_PKG_VERSION_PRE='' 
> CARGO_PRIMARY_PACKAGE=1 CARGO_RUSTC_CURRENT_DIR=/<> 
> LD_LIBRARY_PATH=/<>/target/debug/deps rustc --crate-name 
> byte_slice_cast --edition=2018 src/lib.rs --error-format=json 
> --json=diagnostic-rendered-ansi,artifacts,future-incompat 
> --emit=dep-info,link -C embed-bitcode=no -C debuginfo=2 --test --cfg 
> 'feature="default"' --cfg 'feature="std"' -C metadata=6d167038305f1211 -C 
> extra-filename=-6d167038305f1211 --out-dir 
> /<>/target/x86_64-unknown-linux-gnu/debug/deps --target 
> x86_64-unknown-linux-gnu -C 
> incremental=/<>/target/x86_64-unknown-linux-gnu/debug/incremental
>  -L dependency=/<>/target/x86_64-unknown-linux-gnu/debug/deps -L 
> dependency=/<>/target/debug/deps -C debuginfo=2 -C strip=none 
> --cap-lints warn -C linker=x86_64-linux-gnu-gcc -C link-arg=-Wl,-z,relro 
> --remap-path-prefix 
> /<>=/usr/share/cargo/registry/byte-slice-cast-1.2.1 
> --remap-path-prefix 
> /<>/debian/cargo_registry=/usr/share/cargo/registry`
> Finished `test` profile [unoptimized + debuginfo] target(s) in 1.27s
>  Running `CARGO=/usr/bin/cargo CARGO_MANIFEST_DIR=/<> 
> CARGO_PKG_AUTHORS='Sebastian Dröge ' 
> CARGO_PKG_DESCRIPTION='Safely cast bytes slices from/to slices of built-in 
> fundamental numeric types' CARGO_PKG_HOMEPAGE='' CARGO_PKG_LICENSE=MIT 
>

Bug#1074736: rust-eui48: FTBFS: dh_auto_test: error: /usr/share/cargo/bin/cargo build returned exit code 101

[Lucas Nussbaum]

Source: rust-eui48
Version: 1.1.0-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240702 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 cargo
>dh_update_autotools_config -O--buildsystem=cargo
>dh_autoreconf -O--buildsystem=cargo
>dh_auto_configure -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: linking /usr/share/cargo/registry/* into 
> /<>/debian/cargo_registry/
>dh_auto_build -O--buildsystem=cargo
>dh_auto_test -O--buildsystem=cargo
> debian cargo wrapper: options, profiles, parallel, lto: ['parallel=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'],) {}
>Compiling memchr v2.7.1
>Compiling regex-syntax v0.8.2
>Compiling rustc-serialize v0.3.24
>  Running `CARGO=/usr/bin/cargo CARGO_CRATE_NAME=memchr 
> CARGO_MANIFEST_DIR=/<>/debian/cargo_registry/memchr-2.7.1 
> CARGO_PKG_AUTHORS='Andrew Gallant :bluss' 
> CARGO_PKG_DESCRIPTION='Provides extremely fast (uses SIMD on x86_64, aarch64 
> and wasm32) routines for
> 1, 2 or 3 byte search and single substring search.
> ' CARGO_PKG_HOMEPAGE='https://github.com/BurntSushi/memchr' 
> CARGO_PKG_LICENSE='Unlicense OR MIT' CARGO_PKG_LICENSE_FILE='' 
> CARGO_PKG_NAME=memchr CARGO_PKG_README=README.md 
> CARGO_PKG_REPOSITORY='https://github.com/BurntSushi/memchr' 
> CARGO_PKG_RUST_VERSION=1.61 CARGO_PKG_VERSION=2.7.1 CARGO_PKG_VERSION_MAJOR=2 
> CARGO_PKG_VERSION_MINOR=7 CARGO_PKG_VERSION_PATCH=1 CARGO_PKG_VERSION_PRE='' 
> CARGO_RUSTC_CURRENT_DIR=/<>/debian/cargo_registry/memchr-2.7.1 
> LD_LIBRARY_PATH=/<>/target/debug/deps rustc --crate-name memchr 
> --edition=2021 /<>/debian/cargo_registry/memchr-2.7.1/src/lib.rs 
> --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat 
> --crate-type lib --emit=dep-info,metadata,link -C embed-bitcode=no -C 
> debuginfo=2 --cfg 'feature="alloc"' --cfg 'feature="default"' --cfg 
> 'feature="std"' -C metadata=939fc8ddee1334aa -C 
> extra-filename=-939fc8ddee1334aa --out-dir 
> /<>/target/x86_64-unknown-linux-gnu/debug/deps --target 
> x86_64-unknown-linux-gnu -L 
> dependency=/<>/target/x86_64-unknown-linux-gnu/debug/deps -L 
> dependency=/<>/target/debug/deps --cap-lints warn -C debuginfo=2 
> -C strip=none --cap-lints warn -C linker=x86_64-linux-gnu-gcc -C 
> link-arg=-Wl,-z,relro --remap-path-prefix 
> /<>=/usr/share/cargo/registry/eui48-1.1.0 --remap-path-prefix 
> /<>/debian/cargo_registry=/usr/share/cargo/registry`
>  Running `CARGO=/usr/bin/cargo CARGO_CRATE_NAME=rustc_serialize 
> CARGO_MANIFEST_DIR=/<>/debian/cargo_registry/rustc-serialize-0.3.24
>  CARGO_PKG_AUTHORS='The Rust Project Developers' 
> CARGO_PKG_DESCRIPTION='Generic serialization/deserialization support 
> corresponding to the
> `derive(RustcEncodable, RustcDecodable)` mode in the compiler. Also includes
> support for hex, base64, and json encoding and decoding.
> ' CARGO_PKG_HOMEPAGE='https://github.com/rust-lang/rustc-serialize' 
> CARGO_PKG_LICENSE=MIT/Apache-2.0 CARGO_PKG_LICENSE_FILE='' 
> CARGO_PKG_NAME=rustc-serialize CARGO_PKG_README=README.md 
> CARGO_PKG_REPOSITORY='https://github.com/rust-lang/rustc-serialize' 
> CARGO_PKG_RUST_VERSION='' CARGO_PKG_VERSION=0.3.24 CARGO_PKG_VERSION_MAJOR=0 
> CARGO_PKG_VERSION_MINOR=3 CARGO_PKG_VERSION_PATCH=24 CARGO_PKG_VERSION_PRE='' 
> CARGO_RUSTC_CURRENT_DIR=/<>/debian/cargo_registry/rustc-serialize-0.3.24
>  LD_LIBRARY_PATH=/<>/target/debug/deps rustc --crate-name 
> rustc_serialize --edition=2015 
> /<>/debian/cargo_registry/rustc-serialize-0.3.24/src/lib.rs 
> --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat 
> --crate-type lib --emit=dep-info,metadata,link -C embed-bitcode=no -C 
> debuginfo=2 -C metadata=3546927da67cd00d -C extra-filename=-3546927da67cd00d 
> --out-dir /&l

Bug#1074737: quelcom: FTBFS: make[3]: *** [makefile:8: ca.mo] Error 1

[Lucas Nussbaum]

Source: quelcom
Version: 0.4.0-18
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240702 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> make[3]: Entering directory '/<>'
> make[3]: warning: jobserver unavailable: using -j1.  Add '+' to parent make 
> rule.
> msgfmt -o ca.mo ca.po
> ca.po: warning: Charset "CHARSET" is not a portable encoding name.
> Message conversion to user's charset might not work.
> msgfmt: present charset "CHARSET" is not a portable encoding name
> make[3]: *** [makefile:8: ca.mo] Error 1


The full build log is available from:
http://qa-logs.debian.net/2024/07/02/quelcom_0.4.0-18_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240702;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20240702&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results

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

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

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

Bug#1074735: node-chokidar: FTBFS: dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1

[Lucas Nussbaum]

Source: node-chokidar
Version: 3.6.0-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240702 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 '/<>'
> # No pkg-js-tools auto build
> make[1]: Leaving directory '/<>'
>dh_auto_test --buildsystem=nodejs
>   ln -s ../. node_modules/chokidar
>   /bin/sh -ex debian/tests/pkg-js/test
> + mocha --exit --reporter spec --timeout 30
> 
> 
>   chokidar
> undefined should expose public API methods
> fs.watch (non-polling)
>   watch a directory
> undefined should produce an instance of chokidar.FSWatcher
> undefined should expose public API methods
> undefined should emit `add` event when file was added (48ms)
> undefined should emit nine `add` events when nine files were added in 
> one directory (1297ms)
> undefined should emit thirtythree `add` events when thirtythree files 
> were added in nine directories (767ms)
> undefined should emit `addDir` event when directory was added
> undefined should emit `change` event when file was changed
> undefined should emit `unlink` event when file was removed (103ms)
> undefined should emit `unlinkDir` event when a directory was removed 
> (43ms)
> undefined should emit two `unlinkDir` event when two nested 
> directories were removed (5028ms)
> undefined should emit `unlink` and `add` events when a file is 
> renamed (123ms)
> undefined should emit `add`, not `change`, when previously deleted 
> file is re-added (148ms)
> undefined should not emit `unlink` for previously moved files (413ms)
> undefined should survive ENOENT for missing subdirectories
> undefined should notice when a file appears in a new directory
> undefined should watch removed and re-added directories (1553ms)
> undefined should emit `unlinkDir` and `add` when dir is replaced by 
> file (666ms)
> undefined should emit `unlink` and `addDir` when file is replaced by 
> dir (151ms)
>   watch individual files
> undefined should emit `ready` when three files were added
> undefined should detect changes
> undefined should detect unlinks (122ms)
> undefined should detect unlink and re-add (164ms)
> undefined should ignore unwatched siblings (58ms)
> undefined should detect safe-edit (948ms)
> Skipping gh-682: should detect unlink
>   - should detect unlink while watching a non-existent second file in 
> another directory
>   - should detect unlink and re-add while watching a second file
>   - should detect unlink and re-add while watching a non-existent 
> second file in another directory
>   - should detect unlink and re-add while watching a non-existent 
> second file in the same directory
>   - should detect two unlinks and one re-add
>   - should detect unlink and re-add while watching a second file and 
> a non-existent third file
>   renamed directory
> undefined should emit `add` for a file in a renamed directory (1027ms)
>   watch non-existent paths
> undefined should watch non-existent file and detect add (43ms)
> undefined should watch non-existent dir and detect addDir/add (66ms)
>   watch glob patterns
> undefined should correctly watch and emit based on glob input (58ms)
> undefined should respect negated glob patterns (130ms)
> undefined should traverse subdirs to match globstar patterns (197ms)
> undefined should resolve relative paths with glob patterns (53ms)
> undefined should correctly handle conflicting glob patterns (135ms)
> undefined should correctly handle intersecting glob patterns (44ms)
> undefined should not confuse glob-like filenames with globs (65ms)
> undefined should treat glob-like directory names as literal directory 
> names when globbing is disabled (43ms)
> undefined should treat glob-like filenames as literal filenames when 
> globbing is disabled (49ms)
> undefined should not prematurely filter dirs against complex globstar 
> patterns (73ms)
> undefined should emit matching dir events (66ms)
> undefined should correctly handle glob with braces
>   watch symlinks
> undefined should watch symlinked dirs
> undefined should watch symlinked files
> undefined should follow symlinked files within a normal dir
> undefined should watch paths with 

Bug#1074734: ruff: FTBFS: make[1]: *** [debian/rules:14: override_dh_auto_build] Error 25

[Lucas Nussbaum]

Source: ruff
Version: 0.0.291+dfsg1-4
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240702 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 '/<>'
> mv Cargo.lock Cargo.lock.bak || true
> dh_auto_build
> I: pybuild plugin_pyproject:129: Building wheel for python3.11 with "build" 
> module
> I: pybuild base:311: python3.11 -m build --skip-dependency-check 
> --no-isolation --wheel --outdir /<>/.pybuild/cpython3_3.11  
> * Building wheel...
> Running `maturin pep517 build-wheel -i /usr/bin/python3.11 --compatibility 
> off`
>  Locking 291 packages to latest compatible versions
>   Adding bitflags v1.3.2 (latest: v2.4.2)
>   Adding cfg-if v0.1.10 (latest: v1.0.0)
>   Adding syn v1.0.109 (latest: v2.0.66)
>   Adding toml v0.5.11 (latest: v0.8.8)
> 🍹 Building a mixed python/rust project
> 🐍 Found CPython 3.11 at /usr/bin/python3.11
> 📡 Using build options bindings from pyproject.toml
> warning: /<>/Cargo.toml: unused manifest key: 
> workspace.dependencies.insta.feature
>Compiling proc-macro2 v1.0.85
>Compiling unicode-ident v1.0.12
>Compiling autocfg v1.1.0
>Compiling libc v0.2.155
>Compiling serde v1.0.203
>Compiling memchr v2.7.1
>Compiling cfg-if v1.0.0
>Compiling once_cell v1.19.0
>Compiling smallvec v1.13.1
>Compiling either v1.9.0
>Compiling log v0.4.21
>Compiling anyhow v1.0.85
>Compiling target-lexicon v0.12.12
>Compiling bitflags v2.4.2
>Compiling num-traits v0.2.15
>Compiling itertools v0.10.5
>Compiling regex-syntax v0.8.2
>Compiling static_assertions v1.1.0
>Compiling num-integer v0.1.44
>Compiling aho-corasick v1.1.2
>Compiling quote v1.0.36
>Compiling pyo3-build-config v0.20.2
>Compiling syn v2.0.66
>Compiling thiserror v1.0.59
>Compiling heck v0.4.1
>Compiling crunchy v0.2.2
>Compiling num-bigint v0.4.3
>Compiling unicode-width v0.1.11
>Compiling Inflector v0.11.4
>Compiling tiny-keccak v2.0.2
>Compiling crossbeam-utils v0.8.19
>Compiling syn v1.0.109
>Compiling ruff_text_size v0.0.0 (/<>/crates/ruff_text_size)
>Compiling rustc-hash v1.1.0
>Compiling regex-automata v0.4.7
>Compiling ruff_source_file v0.0.0 
> (/<>/crates/ruff_source_file)
>Compiling getrandom v0.2.12
>Compiling strsim v0.10.0
>Compiling fnv v1.0.7
>Compiling ident_case v1.0.1
>Compiling ruff_python_parser v0.0.0 
> (/<>/crates/ruff_python_parser)
>Compiling rand_core v0.6.4
>Compiling ruff_python_trivia v0.0.0 
> (/<>/crates/ruff_python_trivia)
>Compiling pyo3-ffi v0.20.2
>Compiling bstr v1.7.0
>Compiling lock_api v0.4.11
>Compiling tracing-core v0.1.32
>Compiling pin-project-lite v0.2.13
>Compiling ppv-lite86 v0.2.16
>Compiling pmutil v0.6.1
>Compiling regex v1.10.2
>Compiling darling_core v0.20.3
>Compiling hashbrown v0.14.5
>Compiling equivalent v1.0.1
>Compiling utf8parse v0.2.1
>Compiling siphasher v0.3.10
>Compiling parking_lot_core v0.9.9
>Compiling phf_shared v0.11.2
>Compiling rand v0.8.5
>Compiling anstyle-parse v0.2.1
>Compiling rand_chacha v0.3.1
>Compiling globset v0.4.14
>Compiling filetime v0.2.23
>Compiling lexical-util v0.8.5
>Compiling serde_derive v1.0.203
>Compiling thiserror-impl v1.0.59
>Compiling is-macro v0.3.0
>Compiling tracing-attributes v0.1.27
>Compiling darling_macro v0.20.3
>Compiling ruff_macros v0.0.0 (/<>/crates/ruff_macros)
>Compiling memoffset v0.6.5
>Compiling unicode-normalization v0.1.22
>Compiling unic-char-range v0.9.0
>Compiling anstyle v1.0.4
>Compiling scopeguard v1.1.0
>Compiling rustversion v1.0.14
>Compiling lazy_static v1.4.0
>Compiling unicode-bidi v0.3.13
>Compiling unicode_names2 v0.6.0
>Compiling unic-common v0.9.0
>Compiling colorchoice v1.0.0
>Compiling lalrpop-util v0.20.0
>Compiling tracing v0.1.40
>Compiling percent-encoding v2.3.1
>Compiling option-ext v0.2.0
>Compiling anstyle-query v1.0.0
>Compiling anstream v0.6.7
>Compiling dirs-sys v0.4.1
>Compiling form_urlencoded v1.2.1
>Compiling idna v0.4.0
>Compiling unic-ucd-version v0.9.0
>Compiling unic-char-property v0.9.0
>Compiling darling v0.20.3
>Compiling lexical-parse-integer v0.8.6
>Compiling phf_generator v0.11.2
>Compiling pyo3-ma

Bug#1074731: gtkhash: FTBFS: make[4]: *** [Makefile:570: libgtkhash-properties-caja.caja-extension] Error 1

[Lucas Nussbaum]

Source: gtkhash
Version: 1.5-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240702 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> make[4]: Entering directory '/<>/data/caja'
> /usr/bin/msgfmt --desktop --keyword Name --keyword Description --template 
> libgtkhash-properties-caja.caja-extension.in -d ../../po -o 
> libgtkhash-properties-caja.caja-extension
> /usr/bin/msgfmt: no input file should be given if --desktop and -d are 
> specified
> Try '/usr/bin/msgfmt --help' for more information.
> make[4]: *** [Makefile:570: libgtkhash-properties-caja.caja-extension] Error 1


The full build log is available from:
http://qa-logs.debian.net/2024/07/02/gtkhash_1.5-1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240702;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20240702&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results

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

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

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

Bug#1074684: pyvo: FTBFS: tests failed

[Lucas Nussbaum]

Source: pyvo
Version: 1.5.1-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240702 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 --with python3 --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.11 with "build" 
> module
> I: pybuild base:311: python3.11 -m build --skip-dependency-check 
> --no-isolation --wheel --outdir /<>/.pybuild/cpython3_3.11_pyvo  
> * Building wheel...
> WARNING setuptools_scm.pyproject_reading toml section missing 'pyproject.toml 
> does not contain a tool.setuptools_scm section'
> Traceback (most recent call last):
>   File 
> "/usr/lib/python3/dist-packages/setuptools_scm/_integration/pyproject_reading.py",
>  line 36, in read_pyproject
> section = defn.get("tool", {})[tool_name]
>   ^^^
> KeyError: 'setuptools_scm'
> /usr/lib/python3/dist-packages/setuptools/config/setupcfg.py:293: 
> _DeprecatedConfig: Deprecated config in `setup.cfg`
> !!
> 
> 
> 
> The license_file parameter is deprecated, use license_files instead.
> 
> This deprecation is overdue, please update your project and remove 
> deprecated
> calls to avoid build errors in the future.
> 
> See 
> https://setuptools.pypa.io/en/latest/userguide/declarative_config.html for 
> details.
> 
> 
> 
> !!
>   parsed = self.parsers.get(option_name, lambda x: x)(value)
> running bdist_wheel
> running build
> running build_py
> creating build
> creating build/lib
> creating build/lib/pyvo
> copying pyvo/_astropy_init.py -> build/lib/pyvo
> copying pyvo/conftest.py -> build/lib/pyvo
> copying pyvo/samp.py -> build/lib/pyvo
> copying pyvo/version.py -> build/lib/pyvo
> copying pyvo/__init__.py -> build/lib/pyvo
> creating build/lib/pyvo/dam
> copying pyvo/dam/obscore.py -> build/lib/pyvo/dam
> copying pyvo/dam/__init__.py -> build/lib/pyvo/dam
> creating build/lib/pyvo/auth
> copying pyvo/auth/credentialstore.py -> build/lib/pyvo/auth
> copying pyvo/auth/authsession.py -> build/lib/pyvo/auth
> copying pyvo/auth/authurls.py -> build/lib/pyvo/auth
> copying pyvo/auth/securitymethods.py -> build/lib/pyvo/auth
> copying pyvo/auth/__init__.py -> build/lib/pyvo/auth
> creating build/lib/pyvo/io
> copying pyvo/io/__init__.py -> build/lib/pyvo/io
> creating build/lib/pyvo/registry
> copying pyvo/registry/rtcons.py -> build/lib/pyvo/registry
> copying pyvo/registry/regtap.py -> build/lib/pyvo/registry
> copying pyvo/registry/__init__.py -> build/lib/pyvo/registry
> creating build/lib/pyvo/dal
> copying pyvo/dal/sia2.py -> build/lib/pyvo/dal
> copying pyvo/dal/ssa.py -> build/lib/pyvo/dal
> copying pyvo/dal/query.py -> build/lib/pyvo/dal
> copying pyvo/dal/sia.py -> build/lib/pyvo/dal
> copying pyvo/dal/params.py -> build/lib/pyvo/dal
> copying pyvo/dal/adhoc.py -> build/lib/pyvo/dal
> copying pyvo/dal/tap.py -> build/lib/pyvo/dal
> copying pyvo/dal/scs.py -> build/lib/pyvo/dal
> copying pyvo/dal/dbapi2.py -> build/lib/pyvo/dal
> copying pyvo/dal/exceptions.py -> build/lib/pyvo/dal
> copying pyvo/dal/sla.py -> build/lib/pyvo/dal
> copying pyvo/dal/vosi.py -> build/lib/pyvo/dal
> copying pyvo/dal/mimetype.py -> build/lib/pyvo/dal
> copying pyvo/dal/__init__.py -> build/lib/pyvo/dal
> creating build/lib/pyvo/utils
> copying pyvo/utils/url.py -> build/lib/pyvo/utils
> copying pyvo/utils/protofeature.py -> build/lib/pyvo/utils
> copying pyvo/utils/vocabularies.py -> build/lib/pyvo/utils
> copying pyvo/utils/prototype.py -> build/lib/pyvo/utils
> copying pyvo/utils/compat.py -> build/lib/pyvo/utils
> copying pyvo/utils/formatting.py -> build/lib/pyvo/utils
> copying pyvo/utils/http.py -> build/lib/pyvo/utils
> copying pyvo/utils/decorators.py -> build/lib/pyvo/utils
> copying pyvo/utils/__init__.py -> build/lib/pyvo/utils
> creating build/lib/pyvo/auth/tests
> copying pyvo/auth/tests/test_auth.py -> build/lib/pyvo/auth/tests
> copying pyvo/auth/tests/conftest.py -> build/lib/pyvo/auth/tests
> copying pyvo/auth/tests/__init__.py -> build/li

Bug#1074732: ocaml-expect: FTBFS: make[1]: *** [debian/rules:38: override_dh_auto_clean] Error 2

[Lucas Nussbaum]

Source: ocaml-expect
Version: 0.0.6-3
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240702 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
>  debian/rules clean
> dh clean --with ocaml
>debian/rules override_dh_auto_clean
> make[1]: Entering directory '/<>'
> ocaml setup.ml -distclean
> File "./setup.ml", line 1:
> Error: Reference to undefined global `Stream'
> make[1]: *** [debian/rules:38: override_dh_auto_clean] Error 2


The full build log is available from:
http://qa-logs.debian.net/2024/07/02/ocaml-expect_0.0.6-3_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240702;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20240702&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results

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

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

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

Bug#1074691: virtnbdbackup: FTBFS: ModuleNotFoundError: No module named 'libnbdmod'

[Lucas Nussbaum]

Source: virtnbdbackup
Version: 2.10-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240702 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 --with python3 --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:311: python3.11 setup.py config 
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:311: /usr/bin/python3.11 setup.py build 
> running build
> running build_py
> creating 
> /<>/.pybuild/cpython3_3.11_virtnbdbackup/build/libvirtnbdbackup
> copying libvirtnbdbackup/objects.py -> 
> /<>/.pybuild/cpython3_3.11_virtnbdbackup/build/libvirtnbdbackup
> copying libvirtnbdbackup/chunk.py -> 
> /<>/.pybuild/cpython3_3.11_virtnbdbackup/build/libvirtnbdbackup
> copying libvirtnbdbackup/block.py -> 
> /<>/.pybuild/cpython3_3.11_virtnbdbackup/build/libvirtnbdbackup
> copying libvirtnbdbackup/exceptions.py -> 
> /<>/.pybuild/cpython3_3.11_virtnbdbackup/build/libvirtnbdbackup
> copying libvirtnbdbackup/sighandle.py -> 
> /<>/.pybuild/cpython3_3.11_virtnbdbackup/build/libvirtnbdbackup
> copying libvirtnbdbackup/lz4.py -> 
> /<>/.pybuild/cpython3_3.11_virtnbdbackup/build/libvirtnbdbackup
> copying libvirtnbdbackup/argopt.py -> 
> /<>/.pybuild/cpython3_3.11_virtnbdbackup/build/libvirtnbdbackup
> copying libvirtnbdbackup/common.py -> 
> /<>/.pybuild/cpython3_3.11_virtnbdbackup/build/libvirtnbdbackup
> copying libvirtnbdbackup/__init__.py -> 
> /<>/.pybuild/cpython3_3.11_virtnbdbackup/build/libvirtnbdbackup
> copying libvirtnbdbackup/logcount.py -> 
> /<>/.pybuild/cpython3_3.11_virtnbdbackup/build/libvirtnbdbackup
> creating 
> /<>/.pybuild/cpython3_3.11_virtnbdbackup/build/libvirtnbdbackup/nbdcli
> copying libvirtnbdbackup/nbdcli/context.py -> 
> /<>/.pybuild/cpython3_3.11_virtnbdbackup/build/libvirtnbdbackup/nbdcli
> copying libvirtnbdbackup/nbdcli/exceptions.py -> 
> /<>/.pybuild/cpython3_3.11_virtnbdbackup/build/libvirtnbdbackup/nbdcli
> copying libvirtnbdbackup/nbdcli/client.py -> 
> /<>/.pybuild/cpython3_3.11_virtnbdbackup/build/libvirtnbdbackup/nbdcli
> copying libvirtnbdbackup/nbdcli/__init__.py -> 
> /<>/.pybuild/cpython3_3.11_virtnbdbackup/build/libvirtnbdbackup/nbdcli
> creating 
> /<>/.pybuild/cpython3_3.11_virtnbdbackup/build/libvirtnbdbackup/backup
> copying libvirtnbdbackup/backup/server.py -> 
> /<>/.pybuild/cpython3_3.11_virtnbdbackup/build/libvirtnbdbackup/backup
> copying libvirtnbdbackup/backup/check.py -> 
> /<>/.pybuild/cpython3_3.11_virtnbdbackup/build/libvirtnbdbackup/backup
> copying libvirtnbdbackup/backup/partialfile.py -> 
> /<>/.pybuild/cpython3_3.11_virtnbdbackup/build/libvirtnbdbackup/backup
> copying libvirtnbdbackup/backup/disk.py -> 
> /<>/.pybuild/cpython3_3.11_virtnbdbackup/build/libvirtnbdbackup/backup
> copying libvirtnbdbackup/backup/job.py -> 
> /<>/.pybuild/cpython3_3.11_virtnbdbackup/build/libvirtnbdbackup/backup
> copying libvirtnbdbackup/backup/metadata.py -> 
> /<>/.pybuild/cpython3_3.11_virtnbdbackup/build/libvirtnbdbackup/backup
> copying libvirtnbdbackup/backup/__init__.py -> 
> /<>/.pybuild/cpython3_3.11_virtnbdbackup/build/libvirtnbdbackup/backup
> copying libvirtnbdbackup/backup/target.py -> 
> /<>/.pybuild/cpython3_3.11_virtnbdbackup/build/libvirtnbdbackup/backup
> creating 
> /<>/.pybuild/cpython3_3.11_virtnbdbackup/build/libvirtnbdbackup/sparsestream
> copying libvirtnbdbackup/sparsestream/types.py -> 
> /<>/.pybuild/cpython3_3.11_virtnbdbackup/build/libvirtnbdbackup/sparsestream
> copying libvirtnbdbackup/sparsestream/streamer.py -> 
> /<>/.pybuild/cpython3_3.11_virtnbdbackup/build/libvirtnbdbackup/sparsestream
> copying libvirtnbdbackup/sparsestream/exceptions.py -> 
> /<>/.pybuild/cpython3_3.11_virtnbdbackup/build/libvirtnbdbackup/sparsestream
> copying libvirtnbdbackup/sparsestream/__init__.py -> 
> /<>/.pybuild/cpython3_3.11_virtnbdbackup/build/libvirtnbdbackup/sparsestream
> creating 
> /<>/.pybuild/cpython3_3.11_virtnbdbackup/build/libvirtnbdbackup/output
> copying libvirtnbdbackup/output/exceptions.py -> 
> /<>/.pybuild/cpython3_3.11_virtnbdbackup/build/libvirtnbdbackup/output
> copying libvirtnbdbackup/output/stream.py -> 
> /<>/.pybuild/cpython3_3.11_virtnbdbackup/build/libvirtnbdbackup/output
> copying libvirtnbdbackup/output

Bug#1074728: meep: FTBFS: dh_install: error: missing files, aborting

[Lucas Nussbaum]

Source: meep
Version: 1.25.0-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240702 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> make[4]: Entering directory '/<>'
> make[4]: Nothing to be done for 'install-exec-am'.
>  /usr/bin/mkdir -p 
> '/<>/debian/tmp/usr/lib/x86_64-linux-gnu/pkgconfig'
>  /usr/bin/install -c -m 644 meep.pc 
> '/<>/debian/tmp/usr/lib/x86_64-linux-gnu/pkgconfig'
> make[4]: Leaving directory '/<>'
> make[3]: Leaving directory '/<>'
> make[2]: Leaving directory '/<>'
> rm -f -f debian/tmp/usr/lib/python*/site-packages/meep/adjoint/*.pyc
> rm -f -f debian/tmp/usr/lib/python*/site-packages/meep/adjoint/*.pyo
> rm -f -f debian/tmp/usr/lib/python*/site-packages/meep/*.pyc
> rm -f -f debian/tmp/usr/lib/python*/site-packages/meep/*.pyo
> rm -f -f debian/tmp/usr/lib/python*/site-packages/meep/*.a
> rm -f -f debian/tmp/usr/lib/python*/site-packages/meep/*.la
> rm -f -f debian/tmp/usr/lib/python*/site-packages/meep/mpb/*.pyc
> rm -f -f debian/tmp/usr/lib/python*/site-packages/meep/mpb/*.pyo
> rm -f -f debian/tmp/usr/lib/python*/site-packages/meep/mpb/*.a
> rm -f -f debian/tmp/usr/lib/python*/site-packages/meep/mpb/*.la
> rm -f -f debian/tmp/usr/lib/*/libpympb.la
> rm -f -f debian/tmp/usr/lib/*/libmeep.la
> rm -f -rf debian/tmp/usr/lib/python*/site-packages/meep/__pycache__/
> rm -f -rf debian/tmp/usr/lib/python*/site-packages/meep/adjoint/__pycache__/
> rm -f -rf debian/tmp/usr/lib/python*/site-packages/meep/mpb/__pycache__/
> make[1]: Leaving directory '/<>'
>dh_install
> dh_install: warning: Cannot find (any matches for) "usr/lib/*/libpympb.so.*" 
> (tried in ., debian/tmp)
> 
> dh_install: warning: libmeep30 missing files: usr/lib/*/libpympb.so.*
> dh_install: warning: Cannot find (any matches for) "usr/lib/*/libpympb.so" 
> (tried in ., debian/tmp)
> 
> dh_install: warning: libmeep-dev missing files: usr/lib/*/libpympb.so
> dh_install: warning: Cannot find (any matches for) 
> "usr/lib/python*/site-packages/*" (tried in ., debian/tmp)
> 
> dh_install: warning: python3-meep missing files: 
> usr/lib/python*/site-packages/*
> dh_install: error: missing files, aborting
> make: *** [debian/rules:29: binary] Error 255


The full build log is available from:
http://qa-logs.debian.net/2024/07/02/meep_1.25.0-2_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240702;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20240702&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results

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

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

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

Bug#1074729: golang-github-safchain-ethtool: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 8 github.com/safchain/ethtool github.com/safchain/ethtool/example returned ex

[Lucas Nussbaum]

Source: golang-github-safchain-ethtool
Version: 0.4.0-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240702 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=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/safchain/ethtool github.com/safchain/ethtool/example
> internal/goos
> internal/coverage/rtcov
> internal/goarch
> internal/godebugs
> internal/unsafeheader
> internal/goexperiment
> runtime/internal/atomic
> internal/cpu
> runtime/internal/syscall
> internal/chacha8rand
> internal/abi
> runtime/internal/math
> runtime/internal/sys
> internal/race
> sync/atomic
> unicode
> unicode/utf8
> internal/itoa
> math/bits
> internal/bytealg
> cmp
> encoding
> log/internal
> slices
> math
> runtime
> internal/reflectlite
> sync
> internal/testlog
> errors
> sort
> internal/oserror
> internal/safefilepath
> path
> io
> strconv
> syscall
> strings
> bytes
> reflect
> internal/syscall/execenv
> internal/syscall/unix
> time
> io/fs
> internal/poll
> internal/fmtsort
> encoding/binary
> os
> golang.org/x/sys/unix
> fmt
> encoding/hex
> log
> flag
> github.com/safchain/ethtool
> github.com/safchain/ethtool/example
>dh_auto_test -O--buildsystem=golang
>   cd obj-x86_64-linux-gnu && go test -vet=off -v -p 8 
> github.com/safchain/ethtool github.com/safchain/ethtool/example
> ? github.com/safchain/ethtool/example [no test files]
> === RUN   TestCmdGet
> ethtool_cmd_test.go:46: Unable to get settings from any interface of this 
> system.
> --- FAIL: TestCmdGet (0.00s)
> === RUN   TestCmdGetMapped
> ethtool_cmd_test.go:66: Unable to get settings map from any interface of 
> this system.
> --- FAIL: TestCmdGetMapped (0.00s)
> === RUN   TestMsglvlGet
> --- PASS: TestMsglvlGet (0.00s)
> === RUN   TestGoString
> --- PASS: TestGoString (0.00s)
> === RUN   TestStats
> --- PASS: TestStats (0.00s)
> === RUN   TestDriverName
> --- PASS: TestDriverName (0.00s)
> === RUN   TestBusInfo
> --- PASS: TestBusInfo (0.00s)
> === RUN   TestSupportedLinkModes
> --- PASS: TestSupportedLinkModes (0.00s)
> === RUN   TestFeatures
> --- PASS: TestFeatures (0.00s)
> FAIL
> FAIL  github.com/safchain/ethtool 0.007s
> FAIL
> dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 8 
> github.com/safchain/ethtool github.com/safchain/ethtool/example returned exit 
> code 1


The full build log is available from:
http://qa-logs.debian.net/2024/07/02/golang-github-safchain-ethtool_0.4.0-1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240702;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20240702&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=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.