Bug#1064139: Bug #1064139 ogre-1.12: FTBFS: error: ‘BuildFontAtlas’ is not a member of ‘ImGuiFreeType’

[Flavien Bridault]

Dear Simon,

Many thanks for your answer.

I just cloned the repository to open the MR but then I realized there is 
already a branch opened two weeks ago exactly with the fix I proposed... 
So I guess it is on its way ?


I will follow your advice for ogre 1.14, it was not clear for me I could 
simply open an MR. :)


Cheers,


*Dr. Flavien BRIDAULT*
Director of Software Development
IRCAD France & IRCAD Africa

flavien.brida...@ircad.fr 
Tél. : +33 (0)3 88 119 201
IRCAD France
http://www.ircad.fr/
http://www.ircad.africa/ 

Suivez l'IRCAD sur Facebook 



*IRCAD France*
Hôpitaux Universitaires - 1, place de l'Hôpital - 67091 Strasbourg Cedex 
- FRANCE


Le 06/03/2024 à 23:25, Simon Schmeißer a écrit :


Dear Flavien,

a good and simple start would be to open a Merge Request (MR) adding a 
patch on salsa: https://salsa.debian.org/games-team/ogre


Then salsa CI will test your changes and it can be sponsored by someone.


There was ongoing work to update to 1.12.13  but it stalled: 
https://salsa.debian.org/games-team/ogre/-/merge_requests/6


The main work is likely to identify what needs to change for the 
copyright file to be acceptable



If you want to get started on ogre 14 you could start by combining the 
changes in the 1.12.13 branch with those here 
https://salsa.debian.org/games-team/ogre/-/commits/ogre-13.3/?ref_type=heads


I'm currently super short on time but will try to help you with any 
technical problems if you open a MR for a patch


Best regards from Freiburg

Simon

Am 06.03.24 um 08:46 schrieb Flavien Bridault:


Dear maintainer(s),

I took a look at the latest version of Ogre which is probably 
compatible with latest ImGui and it seems this line is no longer 
necessary. It was removed before the release 13.0.0 when upgrading to 
ImGUI 1.83 : 
https://github.com/OGRECave/ogre/commit/17b7481057b97662a3752ee605ea77a9eb0c57db


Patching should be then fairly easy...

I can offer my help again, like I did to upgrade to 1.14 
(https://lists.debian.org/debian-devel-games/2023/11/msg1.html), 
which whould really be the best option in the end... Maybe I will 
have an official answer this time ? I don't want to be sarcastic at 
all, but I strongly depend on Ogre to build sight and this is 
annoying to get no answer from the devel games team. And currently my 
package sight is currently marked for autoremoval because of this bug 
(https://tracker.debian.org/pkg/sight)


Kind regards,

--

*Dr. Flavien BRIDAULT*
Director of Software Development
IRCAD France & IRCAD Africa

flavien.brida...@ircad.fr 
Tél. : +33 (0)3 88 119 201
IRCAD France
http://www.ircad.fr/
http://www.ircad.africa/ 

Suivez l'IRCAD sur Facebook 



*IRCAD France*
Hôpitaux Universitaires - 1, place de l'Hôpital - 67091 Strasbourg 
Cedex - FRANCE




OpenPGP_signature.asc
Description: OpenPGP digital signature

Processed: Re: Bug#1064748: guix: FTBFS: In procedure canonicalize-path: No such file or directory

[Debian Bug Tracking System]

Processing control commands:

> forwarded 1064748 https://debbugs.gnu.org/69518
Bug #1064748 [src:guix] guix: FTBFS: In procedure canonicalize-path: No such 
file or directory
Set Bug forwarded-to-address to 'https://debbugs.gnu.org/69518'.
> tags 1064748 confirmed
Bug #1064748 [src:guix] guix: FTBFS: In procedure canonicalize-path: No such 
file or directory
Added tag(s) confirmed.

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

Bug#1064748: guix: FTBFS: In procedure canonicalize-path: No such file or directory

[Vagrant Cascadian]

Control: forwarded 1064748 https://debbugs.gnu.org/69518
Control: tags 1064748 confirmed

The actual failed tests are:

test-name: fold-available-packages with/without cache
test-name: find-packages-by-name with cache
test-name: find-packages-by-name + version, with cache
test-name: find-package-locations with cache

live well,
  vagrant


signature.asc
Description: PGP signature

Bug#1065371: in package dpkg marked as pending

[Guillem Jover]

Control: tag 1065371 pending

Hi!

Bug #1065371 in package dpkg reported by you has been fixed in
the dpkg/dpkg.git Git repository. You can see the changelog below, and
you can check the diff of the fix at:

https://git.dpkg.org/cgit/dpkg/dpkg.git/diff/?id=4993fe783

---
Dpkg::Vendor::Debian: Make it possible to disable qa=-bug-implicit-func

We do not need to forcibly enable this feature if the user explicitly
specified it.

Closes: #1065371

Processed: Bug#1065371 in package dpkg marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag 1065371 pending
Bug #1065371 [dpkg-dev] unable to disable bug-implicit-func for time64
Added tag(s) pending.

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

Bug#1061025: Additional information

[Vladimir Petko]

Dear Maintainers,

 I am wondering if the acceptable fix for this failure would be
disabling slf4j backend in commons-logging? This will break circular
dependency and allow projects that use commons-logging and slf4j to
build. I have created a MR with the patch[1].

Best Regards,
 Vladimir.

[1] 
https://salsa.debian.org/java-team/libcommons-logging-java/-/merge_requests/7

Bug#1065585: linux-headers-6.7.7-amd64: Depends: linux-compiler-gcc-13-x86 -> linux-image-6.7.7-amd64, gcc-13 => uninstallable on x32

[наб]

Source: linux
Version: 6.7.7-1
Severity: grave
Justification: user security hole

Dear Maintainer,

(Opting for grave/usersec because naturally updated kernels
 fix security vulnerabilities, but actually i think i can't update the
 kernel and that's grave, security be damned.)

Observe:
  $ sudo apt install --no-install-recommends linux-headers-amd64
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   binutils-x86-64-linux-gnu:amd64 : Depends: libgcc-s1:amd64 (>= 4.2) but it 
is not going to be installed
 Depends: libjansson4:amd64 (>= 2.14) but 
it is not going to be installed
 Depends: libstdc++6:amd64 (>= 13.1) but it 
is not going to be installed
   cpp-13-x86-64-linux-gnu:amd64 : Depends: libgmp10:amd64 (>= 2:6.3.0+dfsg) 
but it is not going to be installed
   Depends: libisl23:amd64 (>= 0.15) but it is 
not going to be installed
   Depends: libmpc3:amd64 (>= 1.1.0) but it is 
not going to be installed
   Depends: libmpfr6:amd64 (>= 3.1.3) but it is 
not going to be installed
   gcc-13-x86-64-linux-gnu:amd64 : Depends: libcc1-0:amd64 (>= 13.2.0-18) but 
it is not going to be installed
   Depends: libgcc-s1:amd64 (>= 3.0) but it is 
not going to be installed
   Depends: libgmp10:amd64 (>= 2:6.3.0+dfsg) 
but it is not going to be installed
   Depends: libisl23:amd64 (>= 0.15) but it is 
not going to be installed
   Depends: libmpc3:amd64 (>= 1.1.0) but it is 
not going to be installed
   Depends: libmpfr6:amd64 (>= 3.1.3) but it is 
not going to be installed
   Depends: libstdc++6:amd64 (>= 5) but it is 
not going to be installed
   libc6:amd64 : Depends: libgcc-s1:amd64 but it is not going to be installed
   libgcc-13-dev:amd64 : Depends: libgcc-s1:amd64 (>= 13.2.0-18) but it is not 
going to be installed
 Depends: libgomp1:amd64 (>= 13.2.0-18) but it is not 
going to be installed
 Depends: libitm1:amd64 (>= 13.2.0-18) but it is not 
going to be installed
 Depends: libatomic1:amd64 (>= 13.2.0-18) but it is not 
going to be installed
 Depends: libasan8:amd64 (>= 13.2.0-18) but it is not 
going to be installed
 Depends: libubsan1:amd64 (>= 13.2.0-18) but it is not 
going to be installed
 Depends: libquadmath0:amd64 (>= 13.2.0-18) but it is 
not going to be installed
   libgprofng0:amd64 : Depends: libgcc-s1:amd64 (>= 3.3.1) but it is not going 
to be installed
   Depends: libstdc++6:amd64 (>= 13.1) but it is not going 
to be installed
   libhwasan0:amd64 : Depends: gcc-14-base:amd64 (= 14-20240303-1) but it is 
not going to be installed
  Depends: libgcc-s1:amd64 (>= 3.3) but it is not going to 
be installed
   liblsan0:amd64 : Depends: gcc-14-base:amd64 (= 14-20240303-1) but it is not 
going to be installed
Depends: libgcc-s1:amd64 (>= 3.3) but it is not going to be 
installed
   libtsan2:amd64 : Depends: gcc-14-base:amd64 (= 14-20240303-1) but it is not 
going to be installed
Depends: libgcc-s1:amd64 (>= 3.4) but it is not going to be 
installed
   linux-headers-6.7.7-amd64:amd64 : Depends: linux-kbuild-6.7.7:amd64
  E: Unable to correct problems, you have held broken packages.
or
  $ sudo apt install --no-install-recommends linux-headers-amd64 
linux-kbuild-6.7.7:x32
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   binutils-x86-64-linux-gnu:amd64 : Depends: libgcc-s1:amd64 (>= 4.2) but it 
is not installable
 Depends: libjansson4:amd64 (>= 2.14) but 
it is not going to be installed
 Depends: libstdc++6:amd64 (>= 13.1) but it 
is not going to be installed
   cpp-13-x86-64-linux-gnu:amd64 : Depends: libgmp10:amd64 (>= 2:6.3.0+dfsg) 
but it is not going to be 

Bug#1065509: marked as done (mysql-8.0 ftbfs with test failure on 32bit time_t64)

[Debian Bug Tracking System]

Your message dated Thu, 07 Mar 2024 00:34:48 +
with message-id 
and subject line Bug#1065509: fixed in mysql-8.0 8.0.36-2
has caused the Debian Bug report #1065509,
regarding mysql-8.0 ftbfs with test failure on 32bit time_t64
to be marked as done.

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

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


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

Package: src:mysql-8.0
Version: 8.0.36-1
Severity: serious
Tags: sid trixie

here seen on armhf:

[...]
[ 58%] main.compare w4  [ pass ]   2171
[ 58%] main.func_unixtime_32bitsw1  [ fail ]
Test ended at 2024-03-05 17:31:14

CURRENT_TEST: main.func_unixtime_32bits

CURRENT_TEST: main.func_unixtime_32bits
--- /<>/mysql-test/r/func_unixtime_32bits.result	2023-12-12 
21:09:36.0 +0300
+++ 
/<>/builddir/mysql-test/var/1/log/func_unixtime_32bits.reject 
2024-03-05 20:31:13.393008921 +0300

@@ -12,7 +12,7 @@
 2038-01-19 06:14:07
 select from_unixtime(2147483648);
 from_unixtime(2147483648)
-NULL
+2038-01-19 06:14:08
 select from_unixtime(0);
 from_unixtime(0)
 1970-01-01 03:00:00
@@ -32,26 +32,26 @@
 2147483647
 select unix_timestamp(from_unixtime(2147483648));
 unix_timestamp(from_unixtime(2147483648))
-NULL
+2147483648
 # check for invalid dates
 # bad year
 select unix_timestamp('2039-01-20 01:00:00');
 unix_timestamp('2039-01-20 01:00:00')
-0
+2179087200
 select unix_timestamp('1968-01-20 01:00:00');
 unix_timestamp('1968-01-20 01:00:00')
 0
 # bad month
 select unix_timestamp('2038-02-10 01:00:00');
 unix_timestamp('2038-02-10 01:00:00')
-0
+2149365600
 select unix_timestamp('1969-11-20 01:00:00');
 unix_timestamp('1969-11-20 01:00:00')
 0
 # bad day
 select unix_timestamp('2038-01-20 01:00:00');
 unix_timestamp('2038-01-20 01:00:00')
-0
+2147551200
 select unix_timestamp('1969-12-30 01:00:00');
 unix_timestamp('1969-12-30 01:00:00')
 0
@@ -71,7 +71,7 @@
 # check bad date, close to the boundary (we cut them off in the very end)
 select unix_timestamp('2038-01-19 07:14:07');
 unix_timestamp('2038-01-19 07:14:07')
-0
+2147487247
 # -- 1. func_time.test   END
 # -- 2. time_zone.test   BEGIN
 #
@@ -84,20 +84,20 @@
 unix_timestamp('2038-01-19 04:14:07'),
 unix_timestamp('2038-01-19 04:14:08');
 unix_timestamp('1970-01-01 01:00:00')	unix_timestamp('1970-01-01 
01:00:01')	unix_timestamp('2038-01-19 04:14:07') 
unix_timestamp('2038-01-19 04:14:08')

-0  1   2147483647  0
+0  1   2147483647  2147483648
 set time_zone=default;
 # -- 2. time_zone.test   END
 # -- 3. time_zone2.test   BEGIN
 select convert_tz('2038-01-19 04:14:08', '+01:00', 'UTC');
 convert_tz('2038-01-19 04:14:08', '+01:00', 'UTC')
-2038-01-19 04:14:08
+2038-01-19 03:14:08
 select convert_tz('2103-01-01 04:00:00', 'MET', 'UTC');
 convert_tz('2103-01-01 04:00:00', 'MET', 'UTC')
-2103-01-01 04:00:00
+2103-01-01 03:00:00
 Will work on a 64 bits time system, no-op on 32 bits time
 select convert_tz('3001-01-18 23:59:59', 'UTC', '+01:00');
 convert_tz('3001-01-18 23:59:59', 'UTC', '+01:00')
-3001-01-18 23:59:59
+3001-01-19 00:59:59
 Will not work, beyond range of UNIX timestamp support
 select convert_tz('3001-01-19 00:00:00', 'UTC', '+01:00');
 convert_tz('3001-01-19 00:00:00', 'UTC', '+01:00')
@@ -123,12 +123,12 @@
 (32536771199.999);
 SELECT a, FROM_UNIXTIME(a) FROM t1;
 a  FROM_UNIXTIME(a)
-32536771199.990NULL
-32536771199.990NULL
-32536771199.991NULL
-32536771199.992NULL
-32536771199.993NULL
-32536771199.994NULL
+32536771199.9903001-01-18 23:59:59.99
+32536771199.9903001-01-18 23:59:59.99
+32536771199.9913001-01-18 23:59:59.99
+32536771199.9923001-01-18 23:59:59.99
+32536771199.9933001-01-18 23:59:59.99
+32536771199.9943001-01-18 23:59:59.99
 32536771199.995NULL
 32536771199.996NULL
 32536771199.997NULL
@@ -148,7 +148,7 @@
 FROM_UNIXTIME(32536771199) AS c4,
 FROM_UNIXTIME(32536771199.999) AS c5;
 c1 c2  c3  c4  c5
-2038-01-19 03:14:07NULLNULLNULLNULL
+2038-01-19 03:14:07	2038-01-19 03:14:08	2038-01-19 03:14:08.00 
3001-01-18 23:59:59	NULL

 SET time_zone=default;
 SELECT
 FROM_UNIXTIME(2147483647) AS c1,
@@ -157,7 +157,7 @@
 FROM_UNIXTIME(32536771199) AS c4,
 FROM_UNIXTIME(32536771199.999) AS c5;
 c1 c2  c3  c4  c5
-2038-01-19 06:14:07NULLNULLNULLNULL
+2038-01-19 06:14:07	2038-01-19 06:14:08	2038-01-19 06:14:08.00 

Bug#1065496: marked as done (mysql-8.0 builds with the embedded zlib library)

[Debian Bug Tracking System]

Your message dated Thu, 07 Mar 2024 00:34:48 +
with message-id 
and subject line Bug#1065496: fixed in mysql-8.0 8.0.36-2
has caused the Debian Bug report #1065496,
regarding mysql-8.0 builds with the embedded zlib library
to be marked as done.

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

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


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

Package: src:mysql-8.0
Version: 8.0.36-1
Severity: serious
Tags: sid trixie

mysql-8.0 builds with the embedded zlib library

[...]
-- Adding -DWITH_CURL=system
-- Adding -DWITH_EDITLINE=system
-- Adding -DWITH_ICU=system
-- Adding -DWITH_LIBEVENT=system
-- Adding -DWITH_LZ4=system
-- Adding -DWITH_PROTOBUF=system
-- Adding -DWITH_SSL=system
-- Adding -DWITH_ZSTD=system
-- Found WITH_FIDO=bundled on command line
-- ZLIB_VERSION (bundled) is 1.2.13
-- ZLIB_INCLUDE_DIR /PKGBUILDDIR/extra/zlib/zlib-1.2.13

it should not do that, please use the system zlib.

But building with the embedded zlib for time64:

[...]
DLZ4_DISABLE_DEPRECATE_WARNINGS -D_FILE_OFFSET_BITS=64 -D_GNU_SOURCE 
-D_LARGEFILE64_SOURCE=1 -D_USE_MATH_DEFINES -D__STDC_FORMAT_MACROS 
-D__STDC_LIMIT_MACROS -I/<>/builddir 
-I/<>/builddir/include -I/<> 
-I/<>/include -isystem 
/<>/builddir/extra/zlib/zlib-1.2.13 -isystem 
/<>/extra/zlib/zlib-1.2.13 -fno-omit-frame-pointer -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -fno-stack-clash-protection 
-fdebug-prefix-map=/<>=/usr/src/mysql-8.0-8.0.36-1build2 
-fdebug-prefix-map=/<>/=./ 
-fdebug-prefix-map=/<>/builddir=./obj -ffunction-sections 
-fdata-sections -O2 -g -DNDEBUG -fPIC   -D_LARGEFILE_SOURCE 
-D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=3 
-Wno-missing-profile -fvisibility=hidden -MD -MT 
extra/zlib/zlib-1.2.13/CMakeFiles/zlib_objlib.dir/gzclose.c.o -MF 
CMakeFiles/zlib_objlib.dir/gzclose.c.o.d -o 
CMakeFiles/zlib_objlib.dir/gzclose.c.o -c 
/<>/extra/zlib/zlib-1.2.13/gzclose.c

In file included from /usr/include/features.h:394,
 from 
/usr/include/arm-linux-gnueabihf/bits/libc-header-start.h:33,

 from /usr/include/stdio.h:28,
 from ../../../../extra/zlib/zlib-1.2.13/gzguts.h:21,
 from ../../../../extra/zlib/zlib-1.2.13/gzclose.c:6:
/usr/include/features-time64.h:26:5: error: #error "_TIME_BITS=64 is 
allowed only with _FILE_OFFSET_BITS=64"

   26 | #   error "_TIME_BITS=64 is allowed only with _FILE_OFFSET_BITS=64"
  | ^
make[4]: *** 
[extra/zlib/zlib-1.2.13/CMakeFiles/zlib_objlib.dir/build.make:135: 
extra/zlib/zlib-1.2.13/CMakeFiles/zlib_objlib.dir/gzclose.c.o] Error 1

make[4]: Leaving directory '/<>/builddir'
make[3]: *** [CMakeFiles/Makefile2:5761: 
extra/zlib/zlib-1.2.13/CMakeFiles/zlib_objlib.dir/all] Error 2
--- End Message ---
--- Begin Message ---
Source: mysql-8.0
Source-Version: 8.0.36-2
Done: Lena Voytek 

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

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

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

Debian distribution maintenance software
pp.
Lena Voytek  (supplier of updated mysql-8.0 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 05 Mar 2024 07:26:25 -0700
Source: mysql-8.0
Built-For-Profiles: noudeb
Architecture: source
Version: 8.0.36-2
Distribution: unstable
Urgency: medium
Maintainer: Debian MySQL Maintainers 
Changed-By: Lena Voytek 
Closes: 1065289 1065496 1065509
Changes:
 mysql-8.0 (8.0.36-2) unstable; urgency=medium
 .
   * debian/rules: Use system zlib to enforce 64 bit time_t (Closes: #1065496)
   * debian/patches/disable_64bits_time_armhf.patch: Remove - using 64 bit armhf
 time now (Closes: #1065509)
   * debian/control: Add explicit libtirpc-dev dependency (Closes: #1065289)
Checksums-Sha1:
 20e5818b47da48890c949c9e40d9a50446728e44 3727 mysql-8.0_8.0.36-2.dsc
 e3074b32aae5284a3fefe7d5249e671f8092a298 145192 
mysql-8.0_8.0.36-2.debian.tar.xz
 539f2df61cf8ddccb24110da4e69e9cf0026d458 10273 
mysql-8.0_8.0.36-2_source.buildinfo
Checksums-Sha256:
 

Bug#1065289: marked as done (mysql-8.0: missing build-dep on libtirpc-dev)

[Debian Bug Tracking System]

Your message dated Thu, 07 Mar 2024 00:34:48 +
with message-id 
and subject line Bug#1065289: fixed in mysql-8.0 8.0.36-2
has caused the Debian Bug report #1065289,
regarding mysql-8.0: missing build-dep on libtirpc-dev
to be marked as done.

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

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


-- 
1065289: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065289
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mysql-8.0
Version: 8.0.36-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
User: debian-gl...@lists.debian.org
Usertags: libtirpc-dev

Dear maintainer,

Starting with glibc 2.31, support for NIS (libnsl library) has been
moved to a separate libnsl2 package. In order to allow a smooth
transition, a libnsl-dev, which depends on libtirpc-dev, has been added
to the libc6-dev package.

The libnsl-dev dependency has been temporarily dropped in the 2.37-15.1
NMU, as part of the 64-bit time_t transition. This causes mysql-8.0 to
FTBFS in sid with:

| -- MECAB_INCLUDE_DIR = /usr/include
| -- MECAB_LIBRARY = /usr/lib/x86_64-linux-gnu/libmecab.so
| -- Found PkgConfig: /bin/pkg-config (found version "1.8.1")
| -- Checking for module 'libtirpc'
| --   Package 'libtirpc', required by 'virtual:world', not found
| CMake Warning at cmake/rpc.cmake:40 (MESSAGE):
|   Cannot find RPC development libraries.  You need to install the required
|   packages:
| 
| Debian/Ubuntu:  apt install libtirpc-dev
| RedHat/Fedora/Oracle Linux: yum install libtirpc-devel
| SuSE:   zypper install glibc-devel
| 
| Call Stack (most recent call first):
|   cmake/rpc.cmake:96 (WARN_MISSING_SYSTEM_TIRPC)
|   plugin/group_replication/libmysqlgcs/cmake/configure.cmake:34 
(MYSQL_CHECK_RPC)
|   plugin/group_replication/libmysqlgcs/CMakeLists.txt:31 (INCLUDE)
| 
| 
| CMake Error at cmake/rpc.cmake:97 (MESSAGE):
|   Could not find rpc/rpc.h in /usr/include or /usr/include/tirpc
| Call Stack (most recent call first):
|   plugin/group_replication/libmysqlgcs/cmake/configure.cmake:34 
(MYSQL_CHECK_RPC)
|   plugin/group_replication/libmysqlgcs/CMakeLists.txt:31 (INCLUDE)
| 
| 
| -- Configuring incomplete, errors occurred!
| make[1]: *** [debian/rules:80: configure-stamp] Error 1
| make[1]: Leaving directory 
'/home/aurel32/work/glibc/libnsl/packages/mysql-8.0-8.0.36'
| make: *** [debian/rules:230: build-arch] Error 2
| dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit 
status 2

This can be fixed by adding an explicit Build-Depends on libtirpc-dev.
The glibc change will likely be reverted in the short term, but given
its a change we want to do for Trixie, this will only lower the severity
of the bug.

Regards
Aurelien
--- End Message ---
--- Begin Message ---
Source: mysql-8.0
Source-Version: 8.0.36-2
Done: Lena Voytek 

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

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

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

Debian distribution maintenance software
pp.
Lena Voytek  (supplier of updated mysql-8.0 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 05 Mar 2024 07:26:25 -0700
Source: mysql-8.0
Built-For-Profiles: noudeb
Architecture: source
Version: 8.0.36-2
Distribution: unstable
Urgency: medium
Maintainer: Debian MySQL Maintainers 
Changed-By: Lena Voytek 
Closes: 1065289 1065496 1065509
Changes:
 mysql-8.0 (8.0.36-2) unstable; urgency=medium
 .
   * debian/rules: Use system zlib to enforce 64 bit time_t (Closes: #1065496)
   * debian/patches/disable_64bits_time_armhf.patch: Remove - using 64 bit armhf
 time now (Closes: #1065509)
   * debian/control: Add explicit libtirpc-dev dependency (Closes: #1065289)
Checksums-Sha1:
 20e5818b47da48890c949c9e40d9a50446728e44 3727 mysql-8.0_8.0.36-2.dsc
 e3074b32aae5284a3fefe7d5249e671f8092a298 145192 
mysql-8.0_8.0.36-2.debian.tar.xz
 539f2df61cf8ddccb24110da4e69e9cf0026d458 10273 
mysql-8.0_8.0.36-2_source.buildinfo
Checksums-Sha256:
 84e96a2cfc842775cb3abcf57dbf483a5833dfab776637069519f3caadbe80c3 3727 
mysql-8.0_8.0.36-2.dsc
 

Bug#1065284: marked as done (lucene++: missing dpkg-dev (>= 1.22.5) build dependency for time_t transition)

[Debian Bug Tracking System]

Your message dated Wed, 06 Mar 2024 23:39:01 +
with message-id 
and subject line Bug#1065284: fixed in lucene++ 3.0.9-3.2
has caused the Debian Bug report #1065284,
regarding lucene++: missing dpkg-dev (>= 1.22.5) build dependency for time_t 
transition
to be marked as done.

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

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


-- 
1065284: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065284
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: lucene++
Version: 3.0.9-3
Severity: serious
X-Debbugs-Cc: sramac...@debian.org, vor...@debian.org

Thank you for uploading the changes required for the time_t transition.
Unfortunately, the upload was missing dpkg-dev (>= 1.22.5) in
Build-Depends. This leads to two potential issues:

* The package is built with the wrong ABI.
* The package migrates to testing before the change is enabled in
  testing and builds there would be produced against the wrong ABI.

Please add dpkg-dev (>= 1.22.5) to Build-Depends and upload the new
version ASAP.

Cheers
-- 
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Source: lucene++
Source-Version: 3.0.9-3.2
Done: Sebastian Ramacher 

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

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

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

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 07 Mar 2024 00:22:31 +0100
Source: lucene++
Architecture: source
Version: 3.0.9-3.2
Distribution: unstable
Urgency: medium
Maintainer: Łukasz 'sil2100' Zemczak 
Changed-By: Sebastian Ramacher 
Closes: 1065284
Changes:
 lucene++ (3.0.9-3.2) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Fix build dependency on dpkg-dev (Closes: #1065284)
Checksums-Sha1:
 ae131b36c23f4e5c67fd54f4b5d2ae25ab0de6c1 1870 lucene++_3.0.9-3.2.dsc
 f61996a2fb459d751fe7e2ca1c0950d2893fbec7 8596 lucene++_3.0.9-3.2.debian.tar.xz
 2556d5a43e125734bb7377127ce8da0cab3024ed 7553 
lucene++_3.0.9-3.2_source.buildinfo
Checksums-Sha256:
 a54a19907904a1ae37b4a23229b1f5e2c80d76ffe7b44e1fe3d220ab757c2834 1870 
lucene++_3.0.9-3.2.dsc
 dac6ffa11b4e09aa1a6b5e57ff42144e67d26876213eff1a6e575945491caab4 8596 
lucene++_3.0.9-3.2.debian.tar.xz
 564cf36b8d196b5e8063fc104666057118c5c073676b9f0b0cb7283fbd02ea14 7553 
lucene++_3.0.9-3.2_source.buildinfo
Files:
 7add2de3379e17112aea733d6c7b447a 1870 libs optional lucene++_3.0.9-3.2.dsc
 ac460a4ca1688f94d447c70a1129cf03 8596 libs optional 
lucene++_3.0.9-3.2.debian.tar.xz
 0ef38590d3acbfbb01751c494e64ee1c 7553 libs optional 
lucene++_3.0.9-3.2_source.buildinfo

-BEGIN PGP SIGNATURE-

iHUEARYKAB0WIQRCYn6EHZln2oPh+pAhk2s2YA/NiQUCZej7VwAKCRAhk2s2YA/N
icZ3AP9llqNZKpsNHsAldEXtGA8KMocP4xCotDOriyCtOWV20gD9G0JO+dmjSaNa
AftpU3d78fNkRLWjkvP2//LKSHiLcgA=
=Hqz9
-END PGP SIGNATURE-



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

Bug#1065265: marked as done (glade: missing dpkg-dev (>= 1.22.5) build dependency for time_t transition)

[Debian Bug Tracking System]

Your message dated Wed, 06 Mar 2024 23:35:09 +
with message-id 
and subject line Bug#1065265: fixed in glade 3.40.0-4.2
has caused the Debian Bug report #1065265,
regarding glade: missing dpkg-dev (>= 1.22.5) build dependency for time_t 
transition
to be marked as done.

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

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


-- 
1065265: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065265
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: glade
Version: 3.40.0-4
Severity: serious
X-Debbugs-Cc: sramac...@debian.org, vor...@debian.org

Thank you for uploading the changes required for the time_t transition.
Unfortunately, the upload was missing dpkg-dev (>= 1.22.5) in
Build-Depends. This leads to two potential issues:

* The package is built with the wrong ABI.
* The package migrates to testing before the change is enabled in
  testing and builds there would be produced against the wrong ABI.

Please add dpkg-dev (>= 1.22.5) to Build-Depends and upload the new
version ASAP.

Cheers
-- 
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Source: glade
Source-Version: 3.40.0-4.2
Done: Sebastian Ramacher 

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

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

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

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 07 Mar 2024 00:20:20 +0100
Source: glade
Architecture: source
Version: 3.40.0-4.2
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Sebastian Ramacher 
Closes: 1065265
Changes:
 glade (3.40.0-4.2) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Fix build dependency on dpkg-dev (Closes: #1065265)
Checksums-Sha1:
 33e7547b9128bf1058cd9d0f84b589f18b42b835 2461 glade_3.40.0-4.2.dsc
 19f259a6b160f631757debf98727bf9a1f81c0a6 23520 glade_3.40.0-4.2.debian.tar.xz
 a17b66f9c8e69e7a4449e1aab39241f7b334d7f0 21576 glade_3.40.0-4.2_amd64.buildinfo
Checksums-Sha256:
 9d92ffd3f8fc3e686c2fe2fff6451f52cd2a6ac6a590b7bbdbe7cf495443a1dd 2461 
glade_3.40.0-4.2.dsc
 98e1021148da45cebe21beda78379a08e7a7e2cc6c49484557beaf95cf4e78b2 23520 
glade_3.40.0-4.2.debian.tar.xz
 b137515cb9d5e90376cad88a601d2eced2c7e6aad267e847ccc7c95f1eb66742 21576 
glade_3.40.0-4.2_amd64.buildinfo
Files:
 92c9a3895bb724f1ef9d9676ae71c88a 2461 gnome optional glade_3.40.0-4.2.dsc
 11bac795ade9ef2375f943bdbd82d0f9 23520 gnome optional 
glade_3.40.0-4.2.debian.tar.xz
 dc13d0bfdaa1c61617e3de1bc12887d1 21576 gnome optional 
glade_3.40.0-4.2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iHUEARYKAB0WIQRCYn6EHZln2oPh+pAhk2s2YA/NiQUCZej7UQAKCRAhk2s2YA/N
idP3AQCfyw4Y8UF0DkwgKNGmW0r0tG17iPoFhzJIQ1Qlk0DciQEAuNGmGKW8QI5V
ebta4I6Fwpi238HfjSpVqq1FrXFdZwU=
=7knT
-END PGP SIGNATURE-



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

Bug#1065277: marked as done (gtkmm2.4: missing dpkg-dev (>= 1.22.5) build dependency for time_t transition)

[Debian Bug Tracking System]

Your message dated Wed, 06 Mar 2024 23:36:09 +
with message-id 
and subject line Bug#1065277: fixed in gtkmm2.4 1:2.24.5-5.2
has caused the Debian Bug report #1065277,
regarding gtkmm2.4: missing dpkg-dev (>= 1.22.5) build dependency for time_t 
transition
to be marked as done.

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

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


-- 
1065277: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065277
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gtkmm2.4
Version: 1:2.24.5-5
Severity: serious
X-Debbugs-Cc: sramac...@debian.org, vor...@debian.org

Thank you for uploading the changes required for the time_t transition.
Unfortunately, the upload was missing dpkg-dev (>= 1.22.5) in
Build-Depends. This leads to two potential issues:

* The package is built with the wrong ABI.
* The package migrates to testing before the change is enabled in
  testing and builds there would be produced against the wrong ABI.

Please add dpkg-dev (>= 1.22.5) to Build-Depends and upload the new
version ASAP.

Cheers
-- 
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Source: gtkmm2.4
Source-Version: 1:2.24.5-5.2
Done: Sebastian Ramacher 

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

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

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

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 07 Mar 2024 00:18:25 +0100
Source: gtkmm2.4
Architecture: source
Version: 1:2.24.5-5.2
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Sebastian Ramacher 
Closes: 1065277
Changes:
 gtkmm2.4 (1:2.24.5-5.2) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Fix build dependency on dpkg-dev (Closes: #1065277)
Checksums-Sha1:
 c651518c21223f66ee1704e87b5441df4658b4ee 1755 gtkmm2.4_2.24.5-5.2.dsc
 c856fdf31a4b20293aa32e0ffa3f58bd5d35b952 22896 
gtkmm2.4_2.24.5-5.2.debian.tar.xz
 04d6d96e4b7579f61790792e0f59aa340fe65d35 12651 
gtkmm2.4_2.24.5-5.2_amd64.buildinfo
Checksums-Sha256:
 3c3442f523d4a872782b85eec7cca8c1f444e9ca8211d345ae0d37bac97e6a9a 1755 
gtkmm2.4_2.24.5-5.2.dsc
 94e7cb3d1417f2dac672ad823e097001d29ed103993c3472861171ed34e8d2c3 22896 
gtkmm2.4_2.24.5-5.2.debian.tar.xz
 2442f2c42bc198981a70e07d9949ca2eb2fd01a9a978e59ae98dc3d677d4deb7 12651 
gtkmm2.4_2.24.5-5.2_amd64.buildinfo
Files:
 366ecb524074793055e26fa2120da28e 1755 oldlibs optional gtkmm2.4_2.24.5-5.2.dsc
 702d01e69dadd73da8a539995c381e12 22896 oldlibs optional 
gtkmm2.4_2.24.5-5.2.debian.tar.xz
 2e5ae202baf232b167cf7fc61e15d0d0 12651 oldlibs optional 
gtkmm2.4_2.24.5-5.2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iHUEARYKAB0WIQRCYn6EHZln2oPh+pAhk2s2YA/NiQUCZej7TAAKCRAhk2s2YA/N
ieRUAQCyTAztHgIqYG4XN9Eh5+McNNzLK1wR9DeNzRvWmpDV5wD/XSPLnmVkRtiO
rw+NVVT+Jghq2sb41vT/eJGW0dL2VQU=
=gqI4
-END PGP SIGNATURE-



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

Bug#1065271: marked as done (gsound: missing dpkg-dev (>= 1.22.5) build dependency for time_t transition)

[Debian Bug Tracking System]

Your message dated Wed, 06 Mar 2024 23:35:46 +
with message-id 
and subject line Bug#1065271: fixed in gsound 1.0.3-3.2
has caused the Debian Bug report #1065271,
regarding gsound: missing dpkg-dev (>= 1.22.5) build dependency for time_t 
transition
to be marked as done.

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

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


-- 
1065271: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065271
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gsound
Version: 1.0.3-3
Severity: serious
X-Debbugs-Cc: sramac...@debian.org, vor...@debian.org

Thank you for uploading the changes required for the time_t transition.
Unfortunately, the upload was missing dpkg-dev (>= 1.22.5) in
Build-Depends. This leads to two potential issues:

* The package is built with the wrong ABI.
* The package migrates to testing before the change is enabled in
  testing and builds there would be produced against the wrong ABI.

Please add dpkg-dev (>= 1.22.5) to Build-Depends and upload the new
version ASAP.

Cheers
-- 
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Source: gsound
Source-Version: 1.0.3-3.2
Done: Sebastian Ramacher 

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

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

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

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 07 Mar 2024 00:16:01 +0100
Source: gsound
Architecture: source
Version: 1.0.3-3.2
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Sebastian Ramacher 
Closes: 1065271
Changes:
 gsound (1.0.3-3.2) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Fix build dependency on dpkg-dev (Closes: #1065271)
Checksums-Sha1:
 873d58ae63da17cc7eec4f9bf02604473cbd885b 1743 gsound_1.0.3-3.2.dsc
 87894a787291712b50cad74fb970057c7bdbb4a5 4112 gsound_1.0.3-3.2.debian.tar.xz
Checksums-Sha256:
 f9ad25e724603ad4a2334c17ff9441d5355f7e4da855de0cbd70bd7dee995bab 1743 
gsound_1.0.3-3.2.dsc
 339ee34b9dc02a2fea722c41d0b3d054694c33702e7e4e8a3bca097302155047 4112 
gsound_1.0.3-3.2.debian.tar.xz
Files:
 09bcda6abd2ba574c257187a8b88a1c2 1743 gnome optional gsound_1.0.3-3.2.dsc
 d538182972d1354ba3df240d43530ad3 4112 gnome optional 
gsound_1.0.3-3.2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iHUEARYKAB0WIQRCYn6EHZln2oPh+pAhk2s2YA/NiQUCZej5hAAKCRAhk2s2YA/N
iVkzAP9LW+Fh2uqBHwp+ER2K429LckjgSJqdxZn6DKAsYABzlwD9FvxoB7U75T51
VVrfdtQWc2bb0ZsU68YmojqxjHNiFAg=
=FZlt
-END PGP SIGNATURE-



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

Bug#1064917: marked as done (tex-common postinst script fails due to a bug in lua script /usr/bin/mtxrun.lua)

[Debian Bug Tracking System]

Your message dated Thu, 7 Mar 2024 00:29:09 +0100
with message-id 
and subject line Re: Bug#1064918: tex-common postinst script fails due to a bug 
in lua script /usr/bin/mtxrun.lua
has caused the Debian Bug report #1064918,
regarding tex-common postinst script fails due to a bug in lua script 
/usr/bin/mtxrun.lua
to be marked as done.

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

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


-- 
1064918: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064918
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: tex-common
Version: 6.18
Severity: important

Dear Maintainer,

after the latest standard "apt upgrade" I was left with an unconfigured 
tex-common, due to the following reported error:

lua error : startup file: /usr/bin/mtxrun.lua:2438: attempt to assign to const 
variable 'i'

I don't know exactly what caused this, since apparently tex-common was not 
modified by the upgrade, but something else triggered it to reconfigure.
/usr/bin/mtxrun.lua is provided by the package context, which also was not 
upgraded very recently
Most of the upgrade was gnu compilers 13 and 14. 
The packages that might have remotely something to do with tex-common could be 
auctex or maybe gnuplot?
Anyway, I attach here the dpkg.log excerpt with the upgrade after which 
tex-common failed to configure.
Regardless, I am not sure whether the bug was introduced by this latest update, 
or rather this upgrade simply made a preexisting bug apparent by triggering a 
tex-common configuration.
Indeed, mtxrun.lua uses texlua, as an interpreter, and that is provided by 
texlive-binaries, which was also upgraded a couple of days ago.
Gotcha! I downgraded texlive-binaries to the previous version, and now 
tex-common configures correctly.
So, apparently, the upgrade of texlive-binaries from version 
2023.20230311.66589-8+b1 to 2023.20230311.66589-9 broke the postinst script of 
tex-common, where it attempts to run mtxrun.lua.

I hope this is enough information to nail and fix the bug, please let me know 
if I can help with further testing.

Bye
Giacomo

P.S. here goes my latest dpkg.log:

2024-02-27 17:09:10 startup archives unpack
2024-02-27 17:09:12 upgrade dpkg:amd64 1.22.4 1.22.5
2024-02-27 17:09:12 status half-configured dpkg:amd64 1.22.4
2024-02-27 17:09:13 status unpacked dpkg:amd64 1.22.4
2024-02-27 17:09:13 status half-installed dpkg:amd64 1.22.4
2024-02-27 17:09:13 status triggers-pending man-db:amd64 2.12.0-3
2024-02-27 17:09:13 status unpacked dpkg:amd64 1.22.5
2024-02-27 17:09:14 startup packages configure
2024-02-27 17:09:14 configure dpkg:amd64 1.22.5 
2024-02-27 17:09:14 status unpacked dpkg:amd64 1.22.5
2024-02-27 17:09:14 status half-configured dpkg:amd64 1.22.5
2024-02-27 17:09:14 status installed dpkg:amd64 1.22.5
2024-02-27 17:09:15 startup archives unpack
2024-02-27 17:09:17 upgrade zfs-initramfs:all 2.2.2-4 2.2.3-1
2024-02-27 17:09:17 status triggers-pending initramfs-tools:all 0.142
2024-02-27 17:09:17 status half-configured zfs-initramfs:all 2.2.2-4
2024-02-27 17:09:17 status unpacked zfs-initramfs:all 2.2.2-4
2024-02-27 17:09:17 status half-installed zfs-initramfs:all 2.2.2-4
2024-02-27 17:09:17 status unpacked zfs-initramfs:all 2.2.3-1
2024-02-27 17:09:18 upgrade zfs-dkms:all 2.2.2-4 2.2.3-1
2024-02-27 17:09:18 status triggers-awaited zfs-dkms:all 2.2.2-4
2024-02-27 17:09:18 status half-configured zfs-dkms:all 2.2.2-4
2024-02-27 17:09:26 status unpacked zfs-dkms:all 2.2.2-4
2024-02-27 17:09:26 status half-installed zfs-dkms:all 2.2.2-4
2024-02-27 17:09:32 status unpacked zfs-dkms:all 2.2.3-1
2024-02-27 17:09:33 upgrade zfsutils-linux:amd64 2.2.2-4 2.2.3-1
2024-02-27 17:09:33 status half-configured zfsutils-linux:amd64 2.2.2-4
2024-02-27 17:09:33 status unpacked zfsutils-linux:amd64 2.2.2-4
2024-02-27 17:09:33 status half-installed zfsutils-linux:amd64 2.2.2-4
2024-02-27 17:09:35 status unpacked zfsutils-linux:amd64 2.2.3-1
2024-02-27 17:09:35 upgrade libnvpair3linux:amd64 2.2.2-4 2.2.3-1
2024-02-27 17:09:35 status triggers-pending libc-bin:amd64 2.37-15
2024-02-27 17:09:35 status half-configured libnvpair3linux:amd64 2.2.2-4
2024-02-27 17:09:35 status unpacked libnvpair3linux:amd64 2.2.2-4
2024-02-27 17:09:35 status half-installed libnvpair3linux:amd64 2.2.2-4
2024-02-27 17:09:36 status unpacked libnvpair3linux:amd64 2.2.3-1
2024-02-27 17:09:36 upgrade libuutil3linux:amd64 2.2.2-4 2.2.3-1
2024-02-27 17:09:36 status half-configured libuutil3linux:amd64 2.2.2-4
2024-02-27 17:09:36 status unpacked libuutil3linux:amd64 2.2.2-4
2024-02-27 17:09:36 status half-installed libuutil3linux:amd64 2.2.2-4
2024-02-27 17:09:37 

Bug#1064918: marked as done (tex-common postinst script fails due to a bug in lua script /usr/bin/mtxrun.lua)

[Debian Bug Tracking System]

Your message dated Thu, 7 Mar 2024 00:29:09 +0100
with message-id 
and subject line Re: Bug#1064918: tex-common postinst script fails due to a bug 
in lua script /usr/bin/mtxrun.lua
has caused the Debian Bug report #1064918,
regarding tex-common postinst script fails due to a bug in lua script 
/usr/bin/mtxrun.lua
to be marked as done.

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

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


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

Package: tex-common
Version: 6.18
Severity: important

Dear Maintainer,

after the latest standard "apt upgrade" I was left with an unconfigured 
tex-common, due to the following reported error:

lua error : startup file: /usr/bin/mtxrun.lua:2438: attempt to assign to const 
variable 'i'

I don't know exactly what caused this, since apparently tex-common was not 
modified by the upgrade, but something else triggered it to reconfigure.
/usr/bin/mtxrun.lua is provided by the package context, which also was not 
upgraded very recently
Most of the upgrade was gnu compilers 13 and 14.
The packages that might have remotely something to do with tex-common could be 
auctex or maybe gnuplot?
Anyway, I attach here the dpkg.log excerpt with the upgrade after which 
tex-common failed to configure.
Regardless, I am not sure whether the bug was introduced by this latest update, 
or rather this upgrade simply made a preexisting bug apparent by triggering a 
tex-common configuration.
Indeed, mtxrun.lua uses texlua, as an interpreter, and that is provided by 
texlive-binaries, which was also upgraded a couple of days ago.
Gotcha! I downgraded texlive-binaries to the previous version, and now 
tex-common configures correctly.
So, apparently, the upgrade of texlive-binaries from version 
2023.20230311.66589-8+b1 to 2023.20230311.66589-9 broke the postinst script of 
tex-common, where it attempts to run mtxrun.lua.

I hope this is enough information to nail and fix the bug, please let me know 
if I can help with further testing.

Bye
Giacomo

P.S. here goes my latest dpkg.log:

2024-02-27 17:09:10 startup archives unpack
2024-02-27 17:09:12 upgrade dpkg:amd64 1.22.4 1.22.5
2024-02-27 17:09:12 status half-configured dpkg:amd64 1.22.4
2024-02-27 17:09:13 status unpacked dpkg:amd64 1.22.4
2024-02-27 17:09:13 status half-installed dpkg:amd64 1.22.4
2024-02-27 17:09:13 status triggers-pending man-db:amd64 2.12.0-3
2024-02-27 17:09:13 status unpacked dpkg:amd64 1.22.5
2024-02-27 17:09:14 startup packages configure
2024-02-27 17:09:14 configure dpkg:amd64 1.22.5 
2024-02-27 17:09:14 status unpacked dpkg:amd64 1.22.5
2024-02-27 17:09:14 status half-configured dpkg:amd64 1.22.5
2024-02-27 17:09:14 status installed dpkg:amd64 1.22.5
2024-02-27 17:09:15 startup archives unpack
2024-02-27 17:09:17 upgrade zfs-initramfs:all 2.2.2-4 2.2.3-1
2024-02-27 17:09:17 status triggers-pending initramfs-tools:all 0.142
2024-02-27 17:09:17 status half-configured zfs-initramfs:all 2.2.2-4
2024-02-27 17:09:17 status unpacked zfs-initramfs:all 2.2.2-4
2024-02-27 17:09:17 status half-installed zfs-initramfs:all 2.2.2-4
2024-02-27 17:09:17 status unpacked zfs-initramfs:all 2.2.3-1
2024-02-27 17:09:18 upgrade zfs-dkms:all 2.2.2-4 2.2.3-1
2024-02-27 17:09:18 status triggers-awaited zfs-dkms:all 2.2.2-4
2024-02-27 17:09:18 status half-configured zfs-dkms:all 2.2.2-4
2024-02-27 17:09:26 status unpacked zfs-dkms:all 2.2.2-4
2024-02-27 17:09:26 status half-installed zfs-dkms:all 2.2.2-4
2024-02-27 17:09:32 status unpacked zfs-dkms:all 2.2.3-1
2024-02-27 17:09:33 upgrade zfsutils-linux:amd64 2.2.2-4 2.2.3-1
2024-02-27 17:09:33 status half-configured zfsutils-linux:amd64 2.2.2-4
2024-02-27 17:09:33 status unpacked zfsutils-linux:amd64 2.2.2-4
2024-02-27 17:09:33 status half-installed zfsutils-linux:amd64 2.2.2-4
2024-02-27 17:09:35 status unpacked zfsutils-linux:amd64 2.2.3-1
2024-02-27 17:09:35 upgrade libnvpair3linux:amd64 2.2.2-4 2.2.3-1
2024-02-27 17:09:35 status triggers-pending libc-bin:amd64 2.37-15
2024-02-27 17:09:35 status half-configured libnvpair3linux:amd64 2.2.2-4
2024-02-27 17:09:35 status unpacked libnvpair3linux:amd64 2.2.2-4
2024-02-27 17:09:35 status half-installed libnvpair3linux:amd64 2.2.2-4
2024-02-27 17:09:36 status unpacked libnvpair3linux:amd64 2.2.3-1
2024-02-27 17:09:36 upgrade libuutil3linux:amd64 2.2.2-4 2.2.3-1
2024-02-27 17:09:36 status half-configured libuutil3linux:amd64 2.2.2-4
2024-02-27 17:09:36 status unpacked libuutil3linux:amd64 2.2.2-4
2024-02-27 17:09:36 status half-installed libuutil3linux:amd64 2.2.2-4
2024-02-27 17:09:37 

Bug#1065284: lucene++: diff for NMU version 3.0.9-3.2

[Sebastian Ramacher]

Control: tags 1065284 + patch

Dear maintainer,

I've prepared an NMU for lucene++ (versioned as 3.0.9-3.2). The diff
is attached to this message.

Cheers
-- 
Sebastian Ramacher
diff -Nru lucene++-3.0.9/debian/changelog lucene++-3.0.9/debian/changelog
--- lucene++-3.0.9/debian/changelog	2024-03-04 11:42:22.0 +0100
+++ lucene++-3.0.9/debian/changelog	2024-03-07 00:22:31.0 +0100
@@ -1,3 +1,10 @@
+lucene++ (3.0.9-3.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix build dependency on dpkg-dev (Closes: #1065284)
+
+ -- Sebastian Ramacher   Thu, 07 Mar 2024 00:22:31 +0100
+
 lucene++ (3.0.9-3.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru lucene++-3.0.9/debian/control lucene++-3.0.9/debian/control
--- lucene++-3.0.9/debian/control	2024-03-04 11:42:21.0 +0100
+++ lucene++-3.0.9/debian/control	2024-03-07 00:22:17.0 +0100
@@ -2,7 +2,7 @@
 Priority: optional
 Maintainer: Łukasz 'sil2100' Zemczak 
 Uploaders: Gianfranco Costamagna 
-Build-Depends: dpkg-dev (>> 1.22.5),
+Build-Depends: dpkg-dev (>= 1.22.5),
cmake,
debhelper-compat (= 13),
libboost-date-time-dev,

Processed: gtkmm2.4: diff for NMU version 1:2.24.5-5.2

[Debian Bug Tracking System]

Processing control commands:

> tags 1065277 + patch
Bug #1065277 {Done: Michael Hudson-Doyle } 
[src:gtkmm2.4] gtkmm2.4: missing dpkg-dev (>= 1.22.5) build dependency for 
time_t transition
Added tag(s) patch.

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

Processed: lucene++: diff for NMU version 3.0.9-3.2

[Debian Bug Tracking System]

Processing control commands:

> tags 1065284 + patch
Bug #1065284 {Done: Michael Hudson-Doyle } [src:lucene++] 
lucene++: missing dpkg-dev (>= 1.22.5) build dependency for time_t transition
Added tag(s) patch.

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

Bug#1065277: gtkmm2.4: diff for NMU version 1:2.24.5-5.2

[Sebastian Ramacher]

Control: tags 1065277 + patch

Dear maintainer,

I've prepared an NMU for gtkmm2.4 (versioned as 1:2.24.5-5.2). The diff
is attached to this message.

Cheers
-- 
Sebastian Ramacher
diff -Nru gtkmm2.4-2.24.5/debian/changelog gtkmm2.4-2.24.5/debian/changelog
--- gtkmm2.4-2.24.5/debian/changelog	2024-03-04 11:40:46.0 +0100
+++ gtkmm2.4-2.24.5/debian/changelog	2024-03-07 00:18:25.0 +0100
@@ -1,3 +1,10 @@
+gtkmm2.4 (1:2.24.5-5.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix build dependency on dpkg-dev (Closes: #1065277)
+
+ -- Sebastian Ramacher   Thu, 07 Mar 2024 00:18:25 +0100
+
 gtkmm2.4 (1:2.24.5-5.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru gtkmm2.4-2.24.5/debian/control gtkmm2.4-2.24.5/debian/control
--- gtkmm2.4-2.24.5/debian/control	2024-03-04 11:40:46.0 +0100
+++ gtkmm2.4-2.24.5/debian/control	2024-03-07 00:18:09.0 +0100
@@ -3,7 +3,7 @@
 Priority: optional
 Maintainer: Debian GNOME Maintainers 
 Uploaders: Emilio Pozuelo Monfort , Jeremy Bícha 
-Build-Depends: dpkg-dev (>> 1.22.5),
+Build-Depends: dpkg-dev (>= 1.22.5),
debhelper-compat (= 13),
libgtk2.0-dev (>= 2.24.0),
libglibmm-2.4-dev (>= 2.27.93),

Processed: glade: diff for NMU version 3.40.0-4.2

[Debian Bug Tracking System]

Processing control commands:

> tags 1065265 + patch
Bug #1065265 {Done: Michael Hudson-Doyle } 
[src:glade] glade: missing dpkg-dev (>= 1.22.5) build dependency for time_t 
transition
Added tag(s) patch.

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

Bug#1065265: glade: diff for NMU version 3.40.0-4.2

[Sebastian Ramacher]

Control: tags 1065265 + patch

Dear maintainer,

I've prepared an NMU for glade (versioned as 3.40.0-4.2). The diff
is attached to this message.

Cheers
-- 
Sebastian Ramacher
diff -Nru glade-3.40.0/debian/changelog glade-3.40.0/debian/changelog
--- glade-3.40.0/debian/changelog	2024-03-04 11:38:30.0 +0100
+++ glade-3.40.0/debian/changelog	2024-03-07 00:20:20.0 +0100
@@ -1,3 +1,10 @@
+glade (3.40.0-4.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix build dependency on dpkg-dev (Closes: #1065265)
+
+ -- Sebastian Ramacher   Thu, 07 Mar 2024 00:20:20 +0100
+
 glade (3.40.0-4.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru glade-3.40.0/debian/control glade-3.40.0/debian/control
--- glade-3.40.0/debian/control	2024-03-04 11:38:30.0 +0100
+++ glade-3.40.0/debian/control	2024-03-07 00:20:07.0 +0100
@@ -7,7 +7,7 @@
 Priority: optional
 Maintainer: Debian GNOME Maintainers 
 Uploaders: Emilio Pozuelo Monfort , Jeremy Bícha , Laurent Bigonville , Marco Trevisan (Treviño) , Michael Biebl 
-Build-Depends: dpkg-dev (>> 1.22.5),
+Build-Depends: dpkg-dev (>= 1.22.5),
at-spi2-core ,
dbus ,
debhelper-compat (= 13),

Processed: gsound: diff for NMU version 1.0.3-3.2

[Debian Bug Tracking System]

Processing control commands:

> tags 1065271 + patch
Bug #1065271 {Done: Michael Hudson-Doyle } 
[src:gsound] gsound: missing dpkg-dev (>= 1.22.5) build dependency for time_t 
transition
Added tag(s) patch.

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

Bug#1065271: gsound: diff for NMU version 1.0.3-3.2

[Sebastian Ramacher]

Control: tags 1065271 + patch

Dear maintainer,

I've prepared an NMU for gsound (versioned as 1.0.3-3.2). The diff
is attached to this message.

Cheers
-- 
Sebastian Ramacher
diff -Nru gsound-1.0.3/debian/changelog gsound-1.0.3/debian/changelog
--- gsound-1.0.3/debian/changelog	2024-03-04 11:40:14.0 +0100
+++ gsound-1.0.3/debian/changelog	2024-03-07 00:16:01.0 +0100
@@ -1,3 +1,10 @@
+gsound (1.0.3-3.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix build dependency on dpkg-dev (Closes: #1065271)
+
+ -- Sebastian Ramacher   Thu, 07 Mar 2024 00:16:01 +0100
+
 gsound (1.0.3-3.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru gsound-1.0.3/debian/control gsound-1.0.3/debian/control
--- gsound-1.0.3/debian/control	2024-03-04 11:40:14.0 +0100
+++ gsound-1.0.3/debian/control	2024-03-07 00:15:38.0 +0100
@@ -3,7 +3,7 @@
 Priority: optional
 Maintainer: Debian GNOME Maintainers 
 Uploaders: Jeremy Bícha , Laurent Bigonville 
-Build-Depends: dpkg-dev (>> 1.22.5),
+Build-Depends: dpkg-dev (>= 1.22.5),
debhelper-compat (= 13),
dh-sequence-gir,
gtk-doc-tools,

Bug#1064402: marked as done (luametatex: "mtxrun --generate": lua error : startup file: /bin/mtxrun.lua:2438: attempt to assign to const variable 'i')

[Debian Bug Tracking System]

Your message dated Wed, 06 Mar 2024 23:04:54 +
with message-id 
and subject line Bug#1064402: fixed in luametatex 2.11.01+really2.10.08+ds-1
has caused the Debian Bug report #1064402,
regarding luametatex: "mtxrun --generate": lua error : startup file: 
/bin/mtxrun.lua:2438: attempt to assign to const variable 'i'
to be marked as done.

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

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


-- 
1064402: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064402
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: texlive-binaries
Version: 2023.20230311.66589-8+b1
Severity: serious

When upgrading TeX Live:

[...]
Processing triggers for tex-common (6.18) ...
Running mktexlsr. This may take some time... done.
Running mtxrun --generate. This may take some time... 
mtxrun --generate failed. Output has been stored in
/tmp/mtxrun.gd7J0NKo
Please include this file if you report a bug.
[...]
dpkg: error processing package tex-common (--configure):
 installed tex-common package post-installation script subprocess returned 
error exit status 1
Errors were encountered while processing:
 tex-common

/tmp/mtxrun.gd7J0NKo just contains:

lua error : startup file: /bin/mtxrun.lua:2438: attempt to assign to const 
variable 'i'

Note: the tex-common and context (from which /bin/mtxrun.lua comes
from) are still old packages, and there were no issues with them
in the past. So I assume that the bug has been introduced in
/usr/bin/texlua (/bin/mtxrun.lua is a texlua script), which is
provided by texlive-binaries.

-- Package-specific info:
IMPORTANT INFORMATION: We will only consider bug reports concerning
the packaging of TeX Live as relevant. If you have problems with
combination of packages in a LaTeX document, please consult your
local TeX User Group, the comp.text.tex user group, the author of
the original .sty file, or any other help resource. 

In particular, bugs that are related to up-upstream, i.e., neither
Debian nor TeX Live (upstream), but the original package authors,
will be closed immediately.

   *** The Debian TeX Team is *not* a LaTeX Help Desk ***

If you report an error when running one of the TeX-related binaries 
(latex, pdftex, metafont,...), or if the bug is related to bad or wrong
output, please include a MINIMAL example input file that produces the
error in your report.

Please run your example with
(pdf)latex -recorder ...
(or any other program that supports -recorder) and send us the generated
file with the extension .fls, it lists all the files loaded during
the run and can easily explain problems induced by outdated files in
your home directory.

Don't forget to also include minimal examples of other files that are 
needed, e.g. bibtex databases. Often it also helps
to include the logfile. Please, never send included pictures!

If your example file isn't short or produces more than one page of
output (except when multiple pages are needed to show the problem),
you can probably minimize it further. Instructions on how to do that
can be found at

http://www.minimalbeispiel.de/mini-en.html (english)

or 

http://www.minimalbeispiel.de/mini.html (german)

##
minimal input file


##
other files

##
 List of ls-R files

-rw-r--r-- 1 root root 4243 2024-02-21 14:57:26 /var/lib/texmf/ls-R
lrwxrwxrwx 1 root root 29 2022-10-12 23:25:33 /usr/share/texmf/ls-R -> 
/var/lib/texmf/ls-R-TEXMFMAIN
lrwxrwxrwx 1 root root 31 2024-02-14 15:08:19 
/usr/share/texlive/texmf-dist/ls-R -> /var/lib/texmf/ls-R-TEXLIVEDIST
lrwxrwxrwx 1 root root 31 2024-02-14 15:08:19 
/usr/share/texlive/texmf-dist/ls-R -> /var/lib/texmf/ls-R-TEXLIVEDIST
##
 Config files
-rw-r--r-- 1 root root 475 2024-02-21 14:57:26 /etc/texmf/web2c/texmf.cnf
lrwxrwxrwx 1 root root 33 2024-02-14 15:08:19 
/usr/share/texmf/web2c/fmtutil.cnf -> /var/lib/texmf/fmtutil.cnf-DEBIAN
lrwxrwxrwx 1 root root 32 2024-02-14 15:08:19 /usr/share/texmf/web2c/updmap.cfg 
-> /var/lib/texmf/updmap.cfg-DEBIAN
-rw-r--r-- 1 root root 5334 2024-02-21 14:57:26 
/var/lib/texmf/tex/generic/config/language.dat
##
 Files in /etc/texmf/web2c/
total 8
-rw-r--r-- 1 root root 283 2014-10-21 02:46:09 mktex.cnf
-rw-r--r-- 1 root root 475 2024-02-21 14:57:26 texmf.cnf
##
 md5sums of texmf.d
ca40c66f144b4bafc3e59a2dd32ecb9c  /etc/texmf/texmf.d/00debian.cnf

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

Bug#1064854: marked as done (Breaks tex-common's configuration)

[Debian Bug Tracking System]

Your message dated Wed, 06 Mar 2024 23:04:54 +
with message-id 
and subject line Bug#1064402: fixed in luametatex 2.11.01+really2.10.08+ds-1
has caused the Debian Bug report #1064402,
regarding Breaks tex-common's configuration
to be marked as done.

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

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


-- 
1064402: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064402
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: context
Version: 2023.05.05.20230730+dfsg-2
Severity: critical

since a few days, I saw a configuration issue with the tex-common
package. (What I don't get is why it actually needs configuration since
I don't see uploads since months.)

I finally found the time to investigate and report. The error message
is:

Setting up tex-common (6.18) ...
Running mktexlsr. This may take some time... done.
Running mtxrun --generate. This may take some time... 
mtxrun --generate failed. Output has been stored in
/tmp/mtxrun.F4nq0y9x
Please include this file if you report a bug.

where /tmp/mtxrun.* contains a single line:

lua error : startup file: /usr/bin/mtxrun.lua:2438: attempt to assign
to const variable 'i'


The executable /usr/bin/mtxrun.lua is provided by the context package
(which also wasn't updated also since months...)

In /usr/bin/mtxrun.lua, around line 2438 looks like:
 for i,v in next,t do 
  if type(i)=="table" then
   if tables[i] then
i=tables[i]   <- 2438 is that one
   else
i=copy(i,tables)
   end
  end

my guess is the correct value should be put in another variable than
the for-loop index, but I'm pretty clueless about lua, and it did work
at some point... perhaps a new lua version is pickier?

Anyway I'm filing the bug report against context, since uninstalling it
unbreaks things, and setting the gravity level to critical since it
breaks other packages.

Cheers,

J.Puydt
--- End Message ---
--- Begin Message ---
Source: luametatex
Source-Version: 2.11.01+really2.10.08+ds-1
Done: Hilmar Preusse 

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

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

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

Debian distribution maintenance software
pp.
Hilmar Preusse  (supplier of updated luametatex package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 06 Mar 2024 23:18:47 +0100
Source: luametatex
Architecture: source
Version: 2.11.01+really2.10.08+ds-1
Distribution: unstable
Urgency: medium
Maintainer: Debian TeX Task Force 
Changed-By: Hilmar Preusse 
Closes: 1064402
Changes:
 luametatex (2.11.01+really2.10.08+ds-1) unstable; urgency=medium
 .
   * Downgrade to 2.10.08 (Closes: #1064402).
Checksums-Sha1:
 ba5e8b971482d3d3e1be3dba6ae9b876aa3abff5 2204 
luametatex_2.11.01+really2.10.08+ds-1.dsc
 255035ddefeb80164f75c0f70740a44e7075a40e 3101460 
luametatex_2.11.01+really2.10.08+ds.orig.tar.gz
 202ca03cbc94a636352ce23544205e1bc0dbfed0 7788 
luametatex_2.11.01+really2.10.08+ds-1.debian.tar.xz
 ed6b44bf11e2997079221d39017171f04c3a715f 5093 
luametatex_2.11.01+really2.10.08+ds-1_source.buildinfo
Checksums-Sha256:
 59cafa61f512e9a16846ff719153942af60d60f1c290d20550a1af81d0495f3d 2204 
luametatex_2.11.01+really2.10.08+ds-1.dsc
 ced6f5d4ffb240a05ce1627492c47452aba38b65f430baa3096b16bfca9562ff 3101460 
luametatex_2.11.01+really2.10.08+ds.orig.tar.gz
 551800c6bb4a505077addbc14bd95c99af63e9170fe694e51e1bca78d19badf3 7788 
luametatex_2.11.01+really2.10.08+ds-1.debian.tar.xz
 f7173fe34c12319671f2a3e446e2ff617fb50e7a2787258fadbce73dc0e2eea9 5093 
luametatex_2.11.01+really2.10.08+ds-1_source.buildinfo
Files:
 d46312f860941a8c6b70373a7aa1ca9c 2204 tex optional 
luametatex_2.11.01+really2.10.08+ds-1.dsc
 ec3bea579a5d8d5a603ed330f55a370a 3101460 tex optional 
luametatex_2.11.01+really2.10.08+ds.orig.tar.gz
 647af2bfa9d9e88c6f0619c07923bd9e 7788 tex optional 
luametatex_2.11.01+really2.10.08+ds-1.debian.tar.xz
 23f4d258806099d1a992abe5b4229adc 5093 tex optional 
luametatex_2.11.01+really2.10.08+ds-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQKTBAEBCgB9FiEEaXGmC/nkbIhxf16kxiZYRqvgLIsFAmXo7o9fFIAALgAo

Bug#1064918: tex-common postinst script fails due to a bug in lua script /usr/bin/mtxrun.lua

[Preuße]

Control: affects -1 context,texlive-binaries
Control: merge -1 1064402

On 06.03.2024 23:23, Preuße...@buxtehude.debian.org, Hilmar wrote:


Control: severity -1 grave
Control: reassign -1 luametatex

Control: merge -1 1064402


Next try.

H.
--
sigfault



OpenPGP_signature.asc
Description: OpenPGP digital signature

Processed (with 1 error): Re: Bug#1064918: tex-common postinst script fails due to a bug in lua script /usr/bin/mtxrun.lua

[Debian Bug Tracking System]

Processing control commands:

> affects -1 context,texlive-binaries
Bug #1064918 [luametatex] tex-common postinst script fails due to a bug in lua 
script /usr/bin/mtxrun.lua
Bug #1064917 [luametatex] tex-common postinst script fails due to a bug in lua 
script /usr/bin/mtxrun.lua
Ignoring request to set affects of bug 1064918 to the same value previously set
Ignoring request to set affects of bug 1064917 to the same value previously set
> merge -1 1064402
Bug #1064918 [luametatex] tex-common postinst script fails due to a bug in lua 
script /usr/bin/mtxrun.lua
Bug #1064917 [luametatex] tex-common postinst script fails due to a bug in lua 
script /usr/bin/mtxrun.lua
Unable to merge bugs because:
affects of #1064854 is 'context,texlive-binaries' not 'texlive-binaries,context'
Failed to merge 1064918: Did not alter merged bugs.


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

Processed (with 1 error): Re: Bug#1064918: tex-common postinst script fails due to a bug in lua script /usr/bin/mtxrun.lua

[Debian Bug Tracking System]

Processing control commands:

> affects -1 texlive-binaries,context
Bug #1064918 [luametatex] tex-common postinst script fails due to a bug in lua 
script /usr/bin/mtxrun.lua
Bug #1064917 [luametatex] tex-common postinst script fails due to a bug in lua 
script /usr/bin/mtxrun.lua
Added indication that 1064918 affects texlive-binaries and context
Added indication that 1064917 affects texlive-binaries and context
> merge -1 1064402
Bug #1064918 [luametatex] tex-common postinst script fails due to a bug in lua 
script /usr/bin/mtxrun.lua
Bug #1064917 [luametatex] tex-common postinst script fails due to a bug in lua 
script /usr/bin/mtxrun.lua
Unable to merge bugs because:
affects of #1064854 is 'context,texlive-binaries' not 'texlive-binaries,context'
Failed to merge 1064918: Did not alter merged bugs.


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

Bug#1064918: tex-common postinst script fails due to a bug in lua script /usr/bin/mtxrun.lua

[Preuße]

Control: affects -1 texlive-binaries,context
Control: merge -1 1064402

On 06.03.2024 23:23, Preuße...@buxtehude.debian.org, Hilmar wrote:


Control: severity -1 grave
Control: reassign -1 luametatex
Control: merge -1 1064402



Next try.

H.
--
sigfault



OpenPGP_signature.asc
Description: OpenPGP digital signature

Processed (with 1 error): Re: Bug#1064918: tex-common postinst script fails due to a bug in lua script /usr/bin/mtxrun.lua

[Debian Bug Tracking System]

Processing control commands:

> severity -1 grave
Bug #1064918 [tex-common] tex-common postinst script fails due to a bug in lua 
script /usr/bin/mtxrun.lua
Bug #1064917 [tex-common] tex-common postinst script fails due to a bug in lua 
script /usr/bin/mtxrun.lua
Severity set to 'grave' from 'important'
Severity set to 'grave' from 'important'
> reassign -1 luametatex
Bug #1064918 [tex-common] tex-common postinst script fails due to a bug in lua 
script /usr/bin/mtxrun.lua
Bug #1064917 [tex-common] tex-common postinst script fails due to a bug in lua 
script /usr/bin/mtxrun.lua
Bug reassigned from package 'tex-common' to 'luametatex'.
Bug reassigned from package 'tex-common' to 'luametatex'.
No longer marked as found in versions tex-common/6.18.
No longer marked as found in versions tex-common/6.18.
Ignoring request to alter fixed versions of bug #1064918 to the same values 
previously set
Ignoring request to alter fixed versions of bug #1064917 to the same values 
previously set
> merge -1 1064402
Bug #1064918 [luametatex] tex-common postinst script fails due to a bug in lua 
script /usr/bin/mtxrun.lua
Bug #1064917 [luametatex] tex-common postinst script fails due to a bug in lua 
script /usr/bin/mtxrun.lua
Unable to merge bugs because:
affects of #1064402 is 'texlive-binaries,context' not ''
affects of #1064854 is 'context,texlive-binaries' not ''
Failed to merge 1064918: Did not alter merged bugs.


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

Bug#1064139: Bug #1064139 ogre-1.12: FTBFS: error: ‘BuildFontAtlas’ is not a member of ‘ImGuiFreeType’

[Simon Schmeißer]

Dear Flavien,

a good and simple start would be to open a Merge Request (MR) adding a
patch on salsa: https://salsa.debian.org/games-team/ogre

Then salsa CI will test your changes and it can be sponsored by someone.


There was ongoing work to update to 1.12.13  but it stalled:
https://salsa.debian.org/games-team/ogre/-/merge_requests/6

The main work is likely to identify what needs to change for the
copyright file to be acceptable


If you want to get started on ogre 14 you could start by combining the
changes in the 1.12.13 branch with those here
https://salsa.debian.org/games-team/ogre/-/commits/ogre-13.3/?ref_type=heads

I'm currently super short on time but will try to help you with any
technical problems if you open a MR for a patch

Best regards from Freiburg

Simon

Am 06.03.24 um 08:46 schrieb Flavien Bridault:


Dear maintainer(s),

I took a look at the latest version of Ogre which is probably
compatible with latest ImGui and it seems this line is no longer
necessary. It was removed before the release 13.0.0 when upgrading to
ImGUI 1.83 :
https://github.com/OGRECave/ogre/commit/17b7481057b97662a3752ee605ea77a9eb0c57db

Patching should be then fairly easy...

I can offer my help again, like I did to upgrade to 1.14
(https://lists.debian.org/debian-devel-games/2023/11/msg1.html),
which whould really be the best option in the end... Maybe I will have
an official answer this time ? I don't want to be sarcastic at all,
but I strongly depend on Ogre to build sight and this is annoying to
get no answer from the devel games team. And currently my package
sight is currently marked for autoremoval because of this bug
(https://tracker.debian.org/pkg/sight)

Kind regards,

--

*Dr. Flavien BRIDAULT*
Director of Software Development
IRCAD France & IRCAD Africa

flavien.brida...@ircad.fr 
Tél. : +33 (0)3 88 119 201
IRCAD France
http://www.ircad.fr/
http://www.ircad.africa/ 

Suivez l'IRCAD sur Facebook


*IRCAD France*
Hôpitaux Universitaires - 1, place de l'Hôpital - 67091 Strasbourg
Cedex - FRANCE

Bug#1057549: crowdsec: FTBFS: FAIL: TestOneShot/permission_denied

[Cyril Brulebois]

Santiago Vila  (2024-03-06):
> I looked at the build log and found the problem: The package has a missing
> build-depends on passwd, which is no longer build-essential in trixie/sid.

Alright, that's the kind of thing I had in mind initially but I'm pretty
sure one of the attempt to reproduce started with a brand new build
chroot… Oh well.

> I am a member of Debian Go (joined to do QA stuff).
> Would it help if I fix this myself by doing a "Team Upload"?

Thanks for the offer, but I do have another related FTBFS on my plate
(even if it was misfiled in the first place), so I'll probably lump up
both uploads together. :)


Cheers,
-- 
Cyril Brulebois -- Debian Consultant @ DEBAMAX -- https://debamax.com/


signature.asc
Description: PGP signature

Processed: Re: Bug#1008502: vdirsyncer: Unknown error occured: unmatched ')'

[Debian Bug Tracking System]

Processing control commands:

> tag -1 unreproducible
Bug #1008502 [vdirsyncer] vdirsyncer: Fix "Unknown error occured: unmatched 
')'" on bullseye
Added tag(s) unreproducible.

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

Bug#1008502: vdirsyncer: Unknown error occured: unmatched ')'

[Colin Watson]

Control: tag -1 unreproducible

On Mon, Mar 28, 2022 at 01:44:58AM +0200, Christof Schulze wrote:
> Running vdirsyncer sync causes the above error message about unmatched
> ')'. This renders 0.4.4 - the version in stable - unusable. The root cause is 
> that
> python-click-threading 0.4.4, which vdirsyncer is depending on,
> introduced an incompatibility with python-click.
> More info on the problem can be found in [2] and [3].
> 
> The version in testing (0.18.0-6) is working fine as it depends on a
> python-click-version that does not have the problem. So installing the
> version from testing including its dependencies works.
> 
> Would you please upgrade vdirsyncer in stable to the current version in
> testing to make the program work again for everyone on stable?

I know this was a long time ago, but I've been going through some Python
team bugs to see if I can do anything with them, and came across this;
it interested me because I've been using vdirsyncer since 2017, and that
definitely involved a period when I was using it on bullseye and I don't
think I ever ran across this bug.

I just tried setting up a clean bullseye container, installing
vdirsyncer, copying over my configuration, and running "vdirsyncer
discover contacts && vdirsyncer sync".  Everything worked perfectly.

> [1] https://github.com/pimutils/vdirsyncer/pull/891
> [2] https://github.com/click-contrib/click-threading/pull/5
> [3] https://github.com/pimutils/vdirsyncer/issues/887

If we were to update anything here in bullseye, it would make more sense
to just cherry-pick the fix to click-threading; the only thing a new
vdirsyncer would add would be a tighter dependency on click-threading,
but for Debian stable release purposes we might as well just issue the
click-threading update and have people upgrade to it.

However, [2] and [3] both make it clear that the problem with the
combination of click and click-threading was introduced in click 8.0.0
and does not exist with click 7.1.2.  bullseye has click 7.1.2, and
indeed the package versions in your bug show that as well:

> Versions of packages vdirsyncer depends on:
> ii  init-system-helpers1.60
> ii  python33.9.2-3
> ii  python3-atomicwrites   1.4.0-2
> ii  python3-click  7.1.2-1
> ii  python3-click-log  0.2.1-2
> ii  python3-click-threading0.4.4-2
> ii  python3-requests   2.25.1+dfsg-2
> ii  python3-requests-toolbelt  0.9.1-1

... so I am quite suspicious that there may be some relevant information
that's not in the bug report.  You didn't include a traceback, which
might have made it clearer; but is it possible that you have a locally
installed version of click >= 8.0.0 from PyPI, perhaps due to running
"pip install" outside a virtual environment?  That would explain this
happening to you.

Thanks,

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

Bug#1063484: libuv1: CVE-2024-24806

[Salvatore Bonaccorso]

Hi

On Wed, Mar 06, 2024 at 07:06:55PM +0100, Dominique Dumont wrote:
> On Tuesday, 5 March 2024 22:15:50 CET Salvatore Bonaccorso wrote:
> > The debdiff for bookworm-security looks good to me. Please do upload
> > to security-master (and make sure to build with -sa as the orig
> > tarball is not yet on security-master for 1.44.2).
> 
> Done.

Thank you, builds arrived.

> > So we just need as well the bullseye-security one, as per above, can
> > you prepare this one as well.
> 
> Done. Here's the debdiff in attachment

Thank you very much. Looks good to me, feel free to upload as well to
security-master (and build as well with -sa).

Regards,
Salvatore

Bug#1057549: crowdsec: FTBFS: FAIL: TestOneShot/permission_denied

[Santiago Vila]

tags 1057549 + patch
thanks

Hi.

I looked at the build log and found the problem: The package has a missing
build-depends on passwd, which is no longer build-essential in trixie/sid.

I am a member of Debian Go (joined to do QA stuff).
Would it help if I fix this myself by doing a "Team Upload"?

Thanks.--- a/debian/control
+++ b/debian/control
@@ -68,6 +68,7 @@ Build-Depends: debhelper-compat (= 13),
golang-gopkg-natefinch-lumberjack.v2-dev,
golang-gopkg-tomb.v2-dev,
golang-gopkg-yaml.v2-dev,
+   passwd,
python3,
systemd
 Standards-Version: 4.5.0

Processed: reassign httpcomponents-client ftbfs to libcommons-logging-java

[Debian Bug Tracking System]

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

> reassign 1061025 src:libcommons-logging-java
Bug #1061025 [src:httpcomponents-client] httpcomponents-client: FTBFS: make: 
*** [debian/rules:4: build] Error 25
Bug reassigned from package 'src:httpcomponents-client' to 
'src:libcommons-logging-java'.
No longer marked as found in versions httpcomponents-client/4.5.14-1.
Ignoring request to alter fixed versions of bug #1061025 to the same values 
previously set
>
End of message, stopping processing here.

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

Processed: Re: Bug#1057549: crowdsec: FTBFS: FAIL: TestOneShot/permission_denied

[Debian Bug Tracking System]

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

> tags 1057549 + patch
Bug #1057549 [src:crowdsec] crowdsec: FTBFS: FAIL: TestOneShot/permission_denied
Added tag(s) patch.
> thanks
Stopping processing here.

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

Bug#1063088: weston: NMU diff for 64-bit time_t transition

[Steve Langasek]

On Wed, Mar 06, 2024 at 10:42:16AM +0100, Dylan Aïssi wrote:
> Hello,

> Le lun. 5 févr. 2024 à 02:54, Steve Langasek  a écrit :

> > If you have any concerns about this patch, please reach out ASAP.  Although
> > this package will be uploaded to experimental immediately, there will be a
> > period of several days before we begin uploads to unstable; so if 
> > information
> > becomes available that your package should not be included in the 
> > transition,
> > there is time for us to amend the planned uploads.

> I am wondering what is the plan with this package/bug? I noticed that changes
> related to the 64-bit time_t transition were not uploaded to unstable and
> because I uploaded several versions in unstable after your NMU in exp, I
> wonder if I haven't interfered with this transition.

Sorry, yes, the uploads with renaming of both dev package and runtime lib
package in the midst of the transition resulted in this package being lost.

Since this is a completely new soname, and only packages built from weston
source depend on it, I suggest that you simply request a binNMU of weston on
armhf and armel and consider this resolved.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org


signature.asc
Description: PGP signature

Bug#1064282: poppler: NMU diff for 64-bit time_t transition

[Steve Langasek]

On Tue, Mar 05, 2024 at 02:14:09PM +0100, Sune Stolborg Vuorela wrote:
> On Sunday, March 3, 2024 7:40:52 AM CET Steve Langasek wrote:
> > (Particularly irrelevant for poppler, whose soname changes ~ monthly.)

> Please note that the poppler frontends, that applications are supposed to be 
> using does only very rarely change SONAME. the glib frontend haven't since 
> it's introduction. Neither have the cpp frontend. The qt5 frontend has 
> changed 
> once. 

> The Poppler Core library, which is meant to be a private shared thing between 
> the frontends is changing SONAME monthly. But poppler core and the frontends 
> are all in the same source, so it shouldn't affect anyone who behaves with 
> poppler as documented. 

Heh true.  But now the ABI has changed, because these libraries are all
confirmed to expose time_t in their ABIs...

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org


signature.asc
Description: PGP signature

Bug#1064377: tcl-expect: identified for time_t transition but no ABI in shlibs

[Steve Langasek]

On Tue, Mar 05, 2024 at 01:34:19PM +0300, Sergei Golovan wrote:
> Hi Steve,

> On Mon, Feb 26, 2024 at 1:12 AM Steve Langasek  wrote:

> > Control: severity -1 normal

> > Note that there are no reverse-dependencies in the archive that link against
> > libexpect, so I think we can downgrade this bug (or close wontfix, at the
> > maintainer's discretion).

> Also, as far as I can see, libexpect does not expose time_t (it uses
> it only internally), so I'm
> closing this bug.

I leave this to your discretion.  This is a package whose headers failed to
analyze under abi-compliance-checker:

https://adrien.dcln.fr/misc/armhf-time_t/2024-02-26T12%3A07%3A00/logs/tcl-expect-dev/base/abi-compliance-checker.log

So we don't know that its ABI is affected, but we also don't know that it
isn't.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org


signature.asc
Description: PGP signature

Bug#1065548: marked as done (octave-statistics: binary-any FTBFS)

[Debian Bug Tracking System]

Your message dated Wed, 06 Mar 2024 17:49:18 +
with message-id 
and subject line Bug#1065548: fixed in octave-statistics 1.6.4-2
has caused the Debian Bug report #1065548,
regarding octave-statistics: binary-any FTBFS
to be marked as done.

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

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


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

https://buildd.debian.org/status/logs.php?pkg=octave-statistics=1.6.4-1

...
   debian/rules execute_after_dh_installdeb
make[1]: Entering directory '/<>'
# Use local JavaScript and CSS files
debian/local-url
sed: can't read 
debian/octave-statistics-common/usr/share/doc/octave-statistics-common/docs/*.html:
 No such file or directory
# Remove empty directory
rmdir 
debian/octave-statistics-common/usr/share/octave/packages/statistics-*/doc/
rmdir: failed to remove 
'debian/octave-statistics-common/usr/share/octave/packages/statistics-*/doc/': 
No such file or directory
make[1]: *** [debian/rules:15: execute_after_dh_installdeb] Error 1
--- End Message ---
--- Begin Message ---
Source: octave-statistics
Source-Version: 1.6.4-2
Done: Rafael Laboissière 

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

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

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

Debian distribution maintenance software
pp.
Rafael Laboissière  (supplier of updated octave-statistics 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 06 Mar 2024 13:25:56 -0300
Source: octave-statistics
Architecture: source
Version: 1.6.4-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Octave Group 
Changed-By: Rafael Laboissière 
Closes: 1065548
Changes:
 octave-statistics (1.6.4-2) unstable; urgency=medium
 .
   * d/rules: Do not FTBFS if empty doc/ directory does not exist
 (Closes: #1065548)
Checksums-Sha1:
 df93d35147cad2046f00454cd832109619f8ea10 2442 octave-statistics_1.6.4-2.dsc
 7116bc296a08b2e855c04631167c8d7d98d5e689 8856 
octave-statistics_1.6.4-2.debian.tar.xz
Checksums-Sha256:
 2d4c8b2fd822c7879a3990479c449990a98eb4a3a0d3caa1ae17166829c93619 2442 
octave-statistics_1.6.4-2.dsc
 df5f1be2b09e6f239861e45b9b23d2f743fc1f9a339f8fd1230a15ed4c7cbd5b 8856 
octave-statistics_1.6.4-2.debian.tar.xz
Files:
 cc4dbdb6d44715e5c70ad1ebd7220c97 2442 math optional 
octave-statistics_1.6.4-2.dsc
 fa54ea965c57a8ae7ecec904d6925b59 8856 math optional 
octave-statistics_1.6.4-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJGBAEBCAAwFiEEP0ZDkUmP6HS9tdmPISSqGYN4XJAFAmXopvsSHHJhZmFlbEBk
ZWJpYW4ub3JnAAoJECEkqhmDeFyQ+icP/jaqjL9uHzj9iemHFCOFlkpwwU/we8pU
L3fSILv0ms1NFkyEqcqZ4DBvlN8GYs1+RprykNsMmsr+tJ8xOHxinouD3NJDkICY
9zOvcE7vm092bkmFWtYFEGDL7WV6S4NMu3RGuvD5gPFUC39WyT+xO6C9FrBcJuQD
aJ0qLYSZkw+5jehNE2RRT5nMaG3P6XBWk2xDXg1Zjhc46uBHNjS5LycGlI6yAcO6
dawuBG7Lf4nVLGitVv7Ur0z8PGfC0pqz6TFY5anmawhwLZrFtfH7bXIUcvOZgueG
VOHR0Wzd1mDkoJ1oUv/+zM2lUjHAE5PgvOlulWxj7OyHtuNm3HhLh38RZDwKegE5
jIm17Tn7kMCYWYSGFM+o9rvp5bE4y9o+TyW7bdJwWSJ8la+No85abE87L5b/IGjG
MyL7WrLKCOYAjLB/O3AW9FPlUpbqmUHjSSlpfoBTrYSggmH+L37CLjZUBKAMQ0LQ
khdP2La0v67MRPInYLhDitVtLmSlT5hz0QesOQf3UXuHwLXpcefB586/wqt2LvX3
lUIMdA//Z+IU8ooM7bQWqfxrxYNV2LtjpnFk3dkoGsqH7btbIHLOdVrKYXweLvrf
N2dgkhDbg6urAP6YXI75+D22i3P3wBorUOrmKlo0xzTAf8WQAcPGZ5Q1Ecu3xODf
HJ70X8aPZlYY
=PsQb
-END PGP SIGNATURE-



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

Bug#1065483: marked as done (perl-base: should provide perlapi-5.38.2 on i386)

[Debian Bug Tracking System]

Your message dated Wed, 06 Mar 2024 17:50:16 +
with message-id 
and subject line Bug#1065483: fixed in perl 5.38.2-3.2
has caused the Debian Bug report #1065483,
regarding perl-base: should provide perlapi-5.38.2 on i386
to be marked as done.

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

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


-- 
1065483: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065483
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: perl-base
Version: 5.38.2-3.1
Severity: serious
X-Debbugs-Cc: Sven Joachim , Steve Langasek 

On i386, perl-base provides perlapi-5.38.2t64 rather than
perlapi-5.38.2.  This makes tons of packages uninstallable or
unbuildable and is not what has been agreed upon in #1060246.

The reason is a bad check in debian/rules, line 31:

,
| # If nonempty, this will determine $Config{debian_abi} and Provides: entries
| # (otherwise, the Provides: entries will be generated by debian/mkprovides)
| perlabi =
| ifeq (,$(filter $(DEB_HOST_GNU_TYPE),i386 hurd-i386))
|   ifeq ($(DEB_HOST_ARCH_BITS),32)
| perlabi = 5.38.2t64
|   endif
| endif
`

Unfortunately DEB_HOST_GNU_TYPE does not match i386 or hurd-i386 on
these architectures:

,
| $ dpkg-architecture -ai386 -qDEB_HOST_GNU_TYPE 2>/dev/null
| i686-linux-gnu
| $ dpkg-architecture -ahurd-i386 -qDEB_HOST_GNU_TYPE 2>/dev/null
| i686-gnu
`

You may want to filter on DEB_HOST_ARCH instead (make sure it is
defined).  A quick fix would be appreciated, because reverse
dependencies are likely going to pick up the wrong perlapi Provides.


-- System Information:
Debian Release: trixie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (101, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
--- End Message ---
--- Begin Message ---
Source: perl
Source-Version: 5.38.2-3.2
Done: Steve Langasek 

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

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

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

Debian distribution maintenance software
pp.
Steve Langasek  (supplier of updated perl package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 06 Mar 2024 17:19:01 +
Source: perl
Architecture: source
Version: 5.38.2-3.2
Distribution: unstable
Urgency: medium
Maintainer: Niko Tyni 
Changed-By: Steve Langasek 
Closes: 1065483
Changes:
 perl (5.38.2-3.2) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Fix check for i386 to avoid transitioning there.  Closes: #1065483.
   * Manually add perlapi-5.38.2t64 to Provides: on i386 to avoid another
 difficult transition.
Checksums-Sha1:
 5f1c0699acb888e73d03457be03f3c622dc3b45c 2946 perl_5.38.2-3.2.dsc
 cdac9edb2e661b4c641bfe60019fcc91f18919a5 165800 perl_5.38.2-3.2.debian.tar.xz
 3e41a3fe922a0d7d98c840d5f1df89032140afa4 6285 perl_5.38.2-3.2_source.buildinfo
Checksums-Sha256:
 9d5494b48f76abdb907fe4ef6fb85c71c0bae503edb69a782b6dce4de33e47a2 2946 
perl_5.38.2-3.2.dsc
 31c8950b4bba7b2f48a88b44d335c14e3ba2506f260e82023df533163570a7cc 165800 
perl_5.38.2-3.2.debian.tar.xz
 70a17be766b12a58d026cd76b9f743b23018a6fd36833f638483a68908d13caa 6285 
perl_5.38.2-3.2_source.buildinfo
Files:
 e265e67fb5c32fd62d42ddf61366edc9 2946 perl standard perl_5.38.2-3.2.dsc
 b096a8dc7012bdd17aa781683629f3ea 165800 perl standard 
perl_5.38.2-3.2.debian.tar.xz
 a6d23cf1456c38ff4d0af39b8748f254 6285 perl standard 
perl_5.38.2-3.2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJGBAEBCgAwFiEErEg/aN5yj0PyIC/KVo0w8yGyEz0FAmXopqESHHZvcmxvbkBk
ZWJpYW4ub3JnAAoJEFaNMPMhshM9WqoP/Rrm3Ywafe6s2DSujGWBO5leec81qcTT
TNXRD4KyWt7CmAeLtPVvhSOvTHbDx2LZgvVOOk6MHbs0WW5sVsCqkdc2DNotRArl
VsThwQsdbULqqJ9aphwrjdZQCfvX4kHw+C5+Z3IW0sJCfd+sEiL10Th+V6JperxP
wGWEN897fqg97r1CwpBeBGbY7m3kTGszP1muLuDpukzY1kDs7Sak+Pqgb+/NFE68
hniYjjG+XmdNHO9OprAbQVVxU0bH9KDNiY8u0yklT1WeyRKIX33YNF9xccUb/S4s
Sxl+S+P7+JyrjqXoNawjxhNCoRzO3/S3DARdxb9sclx9LzYaQaJr0x7Bk+EFJfBr
SSwU31ToeBid4f7C1Ill3+xZwHp3M5HjvM3q8IjC7cf1vC3dqa7komVHrqH1PxnF
aUz2RMHrpEFXcY1HoNoFJ0gDrCaP0ezNEoXTiItu87L0HaJfWEOCVW3cYLoYfTnL
DA6By1ljoWHGzXebOgbpdagZWXC+XhQHFPXdYaaDDj9LS1SKOpwxZVnSpXtAuz9t

Bug#1065483: perl-base: should provide perlapi-5.38.2 on i386

[Steve Langasek]

On Tue, Mar 05, 2024 at 11:47:39AM +0100, Sven Joachim wrote:
> Package: perl-base
> Version: 5.38.2-3.1
> Severity: serious
> X-Debbugs-Cc: Sven Joachim , Steve Langasek 
> 

> On i386, perl-base provides perlapi-5.38.2t64 rather than
> perlapi-5.38.2.  This makes tons of packages uninstallable or
> unbuildable and is not what has been agreed upon in #1060246.

> The reason is a bad check in debian/rules, line 31:

> ,
> | # If nonempty, this will determine $Config{debian_abi} and Provides: entries
> | # (otherwise, the Provides: entries will be generated by debian/mkprovides)
> | perlabi =
> | ifeq (,$(filter $(DEB_HOST_GNU_TYPE),i386 hurd-i386))
> |   ifeq ($(DEB_HOST_ARCH_BITS),32)
> | perlabi = 5.38.2t64
> |   endif
> | endif
> `

Sorry about this.  Clearly, was untested on i386!

I think it's preferable here to check DEB_HOST_ARCH, which was my intention,
rather than DEB_HOST_GNU_TYPE.  I've uploaded an NMU to that effect.  Please
see the NMU debdiff attached.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru perl-5.38.2/debian/changelog perl-5.38.2/debian/changelog
--- perl-5.38.2/debian/changelog2024-03-02 21:34:58.0 +
+++ perl-5.38.2/debian/changelog2024-03-06 17:19:01.0 +
@@ -1,3 +1,12 @@
+perl (5.38.2-3.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix check for i386 to avoid transitioning there.  Closes: #1065483.
+  * Manually add perlapi-5.38.2t64 to Provides: on i386 to avoid another
+difficult transition.
+
+ -- Steve Langasek   Wed, 06 Mar 2024 17:19:01 +
+
 perl (5.38.2-3.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru perl-5.38.2/debian/control perl-5.38.2/debian/control
--- perl-5.38.2/debian/control  2024-03-02 21:34:58.0 +
+++ perl-5.38.2/debian/control  2024-03-06 17:19:01.0 +
@@ -81,6 +81,7 @@
  libfile-temp-perl (= 0.2311),
  libfile-path-perl (= 2.18),
  libio-socket-ip-perl (= 0.41),
+ perlapi-5.38.2t64 [i386 hurd-i386],
 Suggests: perl, sensible-utils
 Description: minimal Perl system
  Perl is a scripting language used in many system scripts and utilities.
diff -Nru perl-5.38.2/debian/rules perl-5.38.2/debian/rules
--- perl-5.38.2/debian/rules2024-03-02 21:34:58.0 +
+++ perl-5.38.2/debian/rules2024-03-06 17:18:00.0 +
@@ -24,13 +24,14 @@
 DEB_BUILD_GNU_TYPE  ?= $(shell dpkg-architecture -qDEB_BUILD_GNU_TYPE)
 DEB_HOST_GNU_TYPE   ?= $(shell dpkg-architecture -qDEB_HOST_GNU_TYPE)
 DEB_HOST_ARCH_BITS  ?= $(shell dpkg-architecture -qDEB_HOST_ARCH_BITS)
+DEB_HOST_ARCH   ?= $(shell dpkg-architecture -qDEB_HOST_ARCH)
 
 # If nonempty, this will determine $Config{debian_abi} and Provides: entries
 # (otherwise, the Provides: entries will be generated by debian/mkprovides)
 perlabi =
-ifeq (,$(filter $(DEB_HOST_GNU_TYPE),i386 hurd-i386))
+ifeq (,$(filter $(DEB_HOST_ARCH),i386 hurd-i386))
   ifeq ($(DEB_HOST_ARCH_BITS),32)
-perlabi = 5.38.2t64 
+perlabi = 5.38.2t64
   endif
 endif
 


signature.asc
Description: PGP signature

Bug#1065548: marked as pending in octave-statistics

[Rafael Laboissière]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/pkg-octave-team/octave-statistics/-/commit/5d7e5e9addd6ad613ee6dae349a8551a2a369888


d/rules: Do not FTBFS if empty doc/ directory does not exist

Closes: #1065548


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1065548

Processed: Bug#1065548 marked as pending in octave-statistics

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1065548 [src:octave-statistics] octave-statistics: binary-any FTBFS
Added tag(s) pending.

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

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

[Debian Bug Tracking System]

Your message dated Wed, 06 Mar 2024 16:34:22 +
with message-id 
and subject line Bug#1064705: fixed in jsonpickle 3.0.3+dfsg-1
has caused the Debian Bug report #1064705,
regarding jsonpickle: FTBFS: dh_auto_test: error: pybuild --test --test-pytest 
-i python{version} -p "3.12 3.11" returned exit code 13
to be marked as done.

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

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


-- 
1064705: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064705
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: jsonpickle
Version: 3.0.2+dfsg-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240224 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
>  debian/rules binary
> dh binary --with python3,sphinxdoc --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild plugin_pyproject:129: Building wheel for python3.12 with "build" 
> module
> I: pybuild base:305: python3.12 -m build --skip-dependency-check 
> --no-isolation --wheel --outdir /<>/.pybuild/cpython3_3.12  
> * Building wheel...
> /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/jsonpickle
> copying jsonpickle/compat.py -> build/lib/jsonpickle
> copying jsonpickle/__init__.py -> build/lib/jsonpickle
> copying jsonpickle/version.py -> build/lib/jsonpickle
> copying jsonpickle/pickler.py -> build/lib/jsonpickle
> copying jsonpickle/handlers.py -> build/lib/jsonpickle
> copying jsonpickle/tags.py -> build/lib/jsonpickle
> copying jsonpickle/errors.py -> build/lib/jsonpickle
> copying jsonpickle/util.py -> build/lib/jsonpickle
> copying jsonpickle/unpickler.py -> build/lib/jsonpickle
> copying jsonpickle/backend.py -> build/lib/jsonpickle
> creating build/lib/jsonpickle/ext
> copying jsonpickle/ext/__init__.py -> build/lib/jsonpickle/ext
> copying jsonpickle/ext/pandas.py -> build/lib/jsonpickle/ext
> copying jsonpickle/ext/numpy.py -> build/lib/jsonpickle/ext
> copying jsonpickle/ext/gmpy.py -> build/lib/jsonpickle/ext
> running egg_info
> writing jsonpickle.egg-info/PKG-INFO
> writing dependency_links to jsonpickle.egg-info/dependency_links.txt
> writing requirements to jsonpickle.egg-info/requires.txt
> writing top-level names to jsonpickle.egg-info/top_level.txt
> reading manifest file 'jsonpickle.egg-info/SOURCES.txt'
> adding license file 'LICENSE'
> writing manifest file 'jsonpickle.egg-info/SOURCES.txt'
> installing to build/bdist.linux-x86_64/wheel
> running install
> running install_lib
> creating build/bdist.linux-x86_64
> creating build/bdist.linux-x86_64/wheel
> creating build/bdist.linux-x86_64/wheel/jsonpickle
> copying build/lib/jsonpickle/compat.py -> 
> build/bdist.linux-x86_64/wheel/jsonpickle
> copying build/lib/jsonpickle/__init__.py -> 
> build/bdist.linux-x86_64/wheel/jsonpickle
> copying build/lib/jsonpickle/version.py -> 
> build/bdist.linux-x86_64/wheel/jsonpickle
> copying build/lib/jsonpickle/pickler.py -> 
> build/bdist.linux-x86_64/wheel/jsonpickle
> copying build/lib/jsonpickle/handlers.py -> 
> build/bdist.linux-x86_64/wheel/jsonpickle
> copying build/lib/jsonpickle/tags.py -> 
> build/bdist.linux-x86_64/wheel/jsonpickle
> copying build/lib/jsonpickle/errors.py -> 
> build/bdist.linux-x86_64/wheel/jsonpickle
> copying build/lib/jsonpickle/util.py -> 
> build/bdist.linux-x86_64/wheel/jsonpickle
> creating build/bdist.linux-x86_64/wheel/jsonpickle/ext
> copying build/lib/jsonpickle/ext/__init__.py -> 
> build/bdist.linux-x86_64/wheel/jsonpickle/ext
> copying build/lib/jsonpickle/ext/pandas.py -> 
> build/bdist.linux-x86_64/wheel/jsonpickle/ext
> copying 

Bug#1065556: grok: FTBFS on armhf and armel: implicit declaration of function ‘asprintf’

[Emanuele Rocca]

Source: grok
Version: 1.20110708.1-7.1
Severity: serious
Tags: ftbfs
User: debian-...@lists.debian.org
Usertags: time-t

Hi,

grok fails to build from source if -Werror=implicit-function-declaration
is on. The flag was added to the default ones on armhf and armel to help
with the ongoing time64 work. For context, see:
https://git.dpkg.org/cgit/dpkg/dpkg.git/commit/?id=ef90821fe45b99fa8c8c4279b9a74c30f59f491d

An excerpt of the build logs follows.

cc -c -g -O2 -Werror=implicit-function-declaration 
-ffile-prefix-map=/<>=. -fstack-protector-strong 
-fstack-clash-protection -Wformat -Werror=format-security -I/usr/include/tirpc 
-Wdate-time -D_FORTIFY_SOURCE=2 -pipe -fPIC -I. -O2 -I/usr/local/include 
-DPLATFORM_GNULinux  grok_capture.c -o grok_capture.o
grok_discover.c: In function ‘grok_discover_init’:
grok_discover.c:54:9: error: implicit declaration of function ‘asprintf’; did 
you mean ‘vsprintf’? [-Werror=implicit-function-declaration]
   54 | if (asprintf(, "%%{%.*s}", namelen, name) == -1) {
  | ^~~~
  | vsprintf

Bug#1065510: marked as done (libnode108t64 is broken on !amd64)

[Debian Bug Tracking System]

Your message dated Wed, 06 Mar 2024 15:52:48 +
with message-id 
and subject line Bug#1065510: fixed in nodejs 18.19.1+dfsg-4
has caused the Debian Bug report #1065510,
regarding libnode108t64 is broken on !amd64
to be marked as done.

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

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


-- 
1065510: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065510
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libnode108t64
Version: 18.19.1+dfsg-3.1
Severity: serious
Tags: ftbfs
X-Debbugs-Cc: Benjamin Drung , Steve Langasek 

Control: affects -1 src:thunderbird

https://buildd.debian.org/status/logs.php?pkg=thunderbird=1%3A115.8.1-1

...
 0:21.16 checking for nodejs... /usr/bin/node: error while loading shared 
libraries: libnode.so.108: cannot open shared object file: No such file or 
directory
...


This is due to:

$ cat debian/libnode108t64.install
usr/lib/libnode.so.* usr/lib/x86_64-linux-gnu/
$
--- End Message ---
--- Begin Message ---
Source: nodejs
Source-Version: 18.19.1+dfsg-4
Done: Jérémy Lal 

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

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

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

Debian distribution maintenance software
pp.
Jérémy Lal  (supplier of updated nodejs package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 06 Mar 2024 16:26:37 +0100
Source: nodejs
Architecture: source
Version: 18.19.1+dfsg-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Jérémy Lal 
Closes: 1065510
Changes:
 nodejs (18.19.1+dfsg-4) unstable; urgency=medium
 .
   * ABIt64: drop libnode108t64.install. Closes: #1065510.
Checksums-Sha1:
 97fdf5c702be98fb07fbaa4ccd77fb1f5022855a 4384 nodejs_18.19.1+dfsg-4.dsc
 356db34779322fd52694b226755a6e44c1287983 163756 
nodejs_18.19.1+dfsg-4.debian.tar.xz
 8749d4210c90b5891ad6d770996e1078cb1b301c 10972 
nodejs_18.19.1+dfsg-4_source.buildinfo
Checksums-Sha256:
 37a1cf19ee9570af3d6627f988d698a23989dcefd8b3d15c2dfbe57be943a0c9 4384 
nodejs_18.19.1+dfsg-4.dsc
 e1d36aaa290a1fe9d93cef88ea5807f981fd8b5b8939af077d8b0f2412fc4c01 163756 
nodejs_18.19.1+dfsg-4.debian.tar.xz
 9b7e06becebf8f52d158acc91bba7a9834d46f374a3d93d628838f97868ff413 10972 
nodejs_18.19.1+dfsg-4_source.buildinfo
Files:
 6831a3a8d64d2b65833add55c1af988e 4384 javascript optional 
nodejs_18.19.1+dfsg-4.dsc
 02e2df2c726a0c641561e35167ef4cba 163756 javascript optional 
nodejs_18.19.1+dfsg-4.debian.tar.xz
 bf7a551d7dec0e0d5d1a8d5fce1ac1c1 10972 javascript optional 
nodejs_18.19.1+dfsg-4_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJGBAEBCAAwFiEEA8Tnq7iA9SQwbkgVZhHAXt0583QFAmXoi1QSHGthcG91ZXJA
bWVsaXgub3JnAAoJEGYRwF7dOfN0cPMP/1RTI4STLjI836dBeDV6Ey8QNPHVV4ki
XcTlT2itkxs8rFg151g5bc/V7CrZnd50zboTCXjJov2BDdmzt90+BCffa/0dmKkg
ELA/5zWHorbMYAs3Zl20XPOkdUmxQgj6qYuKhceLatiVZHd71iosoJst41pVgZ2P
OtZl40q3Qpaa3hkkxJaBBzF+MoHvFxYshM3/tUrq2qf9i/JsrjH3MB2J2beKT1Pc
HZozzDxhTE719jVAv9NG4vobAuh3zYb5I6J5jOP/yfj1dY1ApZ2MwNg+FKNtQzsY
U6KLLIHTt//TPFKp4KDrC+xcCgnjMclbNHoY4qnl/0/NKF4LBYGZmBk/ATked6TJ
pyCkjX3ZKMR90j+ucAHB4ad7FRuEMEWDFxiRS56tA1eSBd2XLaDQVivKVDtNUzPX
KV8h+MIQAzRvlgai+V0BKUO8hhEXue+AwIs2H+wsWDWYpxw3/ekxGO05v8EJ6jt/
lS3kjaAYLDl0CLO752uVJ5fwuikvjfT+NZ3FBaPKckKZuZAM53TU6rmdVUKIbJUh
rwUvk/00S1u148gS7YKIc7ft30hbjwFlb2IFypNl/1D/RF1spDGKIY7+pk4gph5+
333zzcuQP/i1VzK8zkqCsTTJB7UGK5sm37VhSxSWBWhpKAitNe6kDJYGTciTzYgS
eTLVE0+Qsaaw
=9kka
-END PGP SIGNATURE-



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

Bug#1042241: marked as done (wcwidth: FTBFS: tests fail)

[Debian Bug Tracking System]

Your message dated Wed, 06 Mar 2024 15:53:31 +
with message-id 
and subject line Bug#1042241: fixed in wcwidth 0.2.13+dfsg1-1
has caused the Debian Bug report #1042241,
regarding wcwidth: FTBFS: tests fail
to be marked as done.

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

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


-- 
1042241: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042241
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: wcwidth
Version: 0.2.5+dfsg1-1.1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230726 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 '/<>'
> set -ex ; for i in `py3versions -vr 2>/dev/null` ; do \
>   python$i setup.py install --install-layout=deb --root 
> /<>/debian/tmp ; \
> done
> + py3versions -vr
> + python3.11 setup.py install --install-layout=deb --root 
> /<>/debian/tmp
> /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.
> 
> By 2023-Oct-30, you need to update your project and remove deprecated 
> calls
> or your builds will no longer be supported.
> 
> See 
> https://setuptools.pypa.io/en/latest/userguide/declarative_config.html for 
> details.
> 
> 
> 
> !!
>   parsed = self.parsers.get(option_name, lambda x: x)(value)
> running install
> /usr/lib/python3/dist-packages/setuptools/_distutils/cmd.py:66: 
> SetuptoolsDeprecationWarning: setup.py install is deprecated.
> !!
> 
> 
> 
> Please avoid running ``setup.py`` directly.
> Instead, use pypa/build, pypa/installer or other
> standards-based tools.
> 
> See https://blog.ganssle.io/articles/2021/10/setup-py-deprecated.html 
> for details.
> 
> 
> 
> !!
>   self.initialize_options()
> running build
> running build_py
> creating build
> creating build/lib
> creating build/lib/wcwidth
> copying wcwidth/wcwidth.py -> build/lib/wcwidth
> copying wcwidth/__init__.py -> build/lib/wcwidth
> copying wcwidth/unicode_versions.py -> build/lib/wcwidth
> copying wcwidth/table_wide.py -> build/lib/wcwidth
> copying wcwidth/table_zero.py -> build/lib/wcwidth
> running install_lib
> creating /<>/debian/tmp
> creating /<>/debian/tmp/usr
> creating /<>/debian/tmp/usr/lib
> creating /<>/debian/tmp/usr/lib/python3
> creating /<>/debian/tmp/usr/lib/python3/dist-packages
> creating /<>/debian/tmp/usr/lib/python3/dist-packages/wcwidth
> copying build/lib/wcwidth/wcwidth.py -> 
> /<>/debian/tmp/usr/lib/python3/dist-packages/wcwidth
> copying build/lib/wcwidth/__init__.py -> 
> /<>/debian/tmp/usr/lib/python3/dist-packages/wcwidth
> copying build/lib/wcwidth/unicode_versions.py -> 
> /<>/debian/tmp/usr/lib/python3/dist-packages/wcwidth
> copying build/lib/wcwidth/table_wide.py -> 
> /<>/debian/tmp/usr/lib/python3/dist-packages/wcwidth
> copying build/lib/wcwidth/table_zero.py -> 
> /<>/debian/tmp/usr/lib/python3/dist-packages/wcwidth
> byte-compiling 
> /<>/debian/tmp/usr/lib/python3/dist-packages/wcwidth/wcwidth.py 
> to wcwidth.cpython-311.pyc
> byte-compiling 
> /<>/debian/tmp/usr/lib/python3/dist-packages/wcwidth/__init__.py 
> to __init__.cpython-311.pyc
> byte-compiling 
> /<>/debian/tmp/usr/lib/python3/dist-packages/wcwidth/unicode_versions.py
>  to unicode_versions.cpython-311.pyc
> byte-compiling 
> /<>/debian/tmp/usr/lib/python3/dist-packages/wcwidth/table_wide.py
>  to table_wide.cpython-311.pyc
> byte-compiling 
> /<>/debian/tmp/usr/lib/python3/dist-packages/wcwidth/table_zero.py
>  to table_zero.cpython-311.pyc
> running install_egg_info
> running egg_info
> creating wcwidth.egg-info
> writing wcwidth.egg-info/PKG-INFO
> writing dependency_links to wcwidth.egg-info/dependency_links.txt
> writing requirements to wcwidth.egg-info/requires.txt
> writing top-level names to wcwidth.egg-info/top_level.txt
> writing manifest file 'wcwidth.egg-info/SOURCES.txt'
> reading manifest file 'wcwidth.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> adding license file 'LICENSE'
> writing manifest file 'wcwidth.egg-info/SOURCES.txt'
> 

Processed: Bug#1042241 marked as pending in wcwidth

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1042241 [src:wcwidth] wcwidth: FTBFS: tests fail
Added tag(s) pending.

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

Bug#1042241: marked as pending in wcwidth

[Colin Watson]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/python-team/packages/wcwidth/-/commit/224ad07e9c5a6068957c5588e4fa1677fafb5b36


Update upstream source from tag 'upstream/0.2.13+dfsg1'

Update to upstream version '0.2.13+dfsg1'
with Debian dir 7763002028eb5176ac6dd29c7886dd3af7766443

Closes: #1042241


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1042241

Bug#1065208: marked as done (gcl: recent libc6-dev change causes XDR support to be dropped)

[Debian Bug Tracking System]

Your message dated Wed, 06 Mar 2024 15:05:01 +
with message-id 
and subject line Bug#1065208: fixed in gcl 2.6.14-7
has caused the Debian Bug report #1065208,
regarding gcl: recent libc6-dev change causes XDR support to be dropped
to be marked as done.

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

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


-- 
1065208: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065208
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gcl
Version: 2.6.14-6
Severity: serious
User: debian-gl...@lists.debian.org
Usertags: libtirpc-dev

Dear maintainer,

Starting with glibc 2.31, support for NIS (libnsl library) has been
moved to a separate libnsl2 package. In order to allow a smooth
transition, a libnsl-dev, which depends on libtirpc-dev, has been added
to the libc6-dev package.

The libnsl-dev dependency has been temporarily dropped in the 2.37-15.1
NMU, as part of the 64-bit time_t transition. This causes gcl to disable
the XDR support. Not fully sure what are the consequences, but it seems
at least axiom requires XDR support.

Therefore please either:
- Add libnsl-dev as build dependency
- Disable XDR support explicitly with --disable-xdr so that this feature
  does not depend on the packages installed on the system.

The glibc change will likely be reverted in the short term, but given
its a change we want to do for Trixie, this will only lower the severity
of the bug.

Regards
Aurelien
--- End Message ---
--- Begin Message ---
Source: gcl
Source-Version: 2.6.14-7
Done: Camm Maguire 

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

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

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

Debian distribution maintenance software
pp.
Camm Maguire  (supplier of updated gcl package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 06 Mar 2024 09:30:02 -0500
Source: gcl
Architecture: source
Version: 2.6.14-7
Distribution: unstable
Urgency: medium
Maintainer: Camm Maguire 
Changed-By: Camm Maguire 
Closes: 1065208
Changes:
 gcl (2.6.14-7) unstable; urgency=medium
 .
   * Version_2_6_15pre6
   * Bug fix: "recent libc6-dev change causes XDR support to be dropped",
 thanks to Aurelien Jarno (Closes: #1065208).
Checksums-Sha1:
 00738edc7a4a4fe91a54a0c5786b3e049c74c9fc 1847 gcl_2.6.14-7.dsc
 e686dda7a1ecc6771529eb964192d40e2c7acc0b 136656 gcl_2.6.14-7.debian.tar.xz
 64d10bcb29b72297be17f5d91b0f102b57c6ebd3 7981 gcl_2.6.14-7_source.buildinfo
Checksums-Sha256:
 aff45517600f6fd65bcc624014b98a2f14e1e5d258681e1d2e408529fa10e845 1847 
gcl_2.6.14-7.dsc
 7df77acc407334cf950123137a50ac0746e6ebdb54eaf1f62156e1afae7f2045 136656 
gcl_2.6.14-7.debian.tar.xz
 d21ac99cad402a18f4c6c324c38c44e520b7e6ca3e8873879f33d507d83eacc3 7981 
gcl_2.6.14-7_source.buildinfo
Files:
 b6f63c8fffe6873af173b8d892164dd3 1847 lisp optional gcl_2.6.14-7.dsc
 42793416f6acdf2709b208bb4a49a079 136656 lisp optional 
gcl_2.6.14-7.debian.tar.xz
 187ca824cd8338ecd7be22e88c2fdf61 7981 lisp optional 
gcl_2.6.14-7_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEE/iFPNjaXdzJC6BbsuEXOUQ+bcU0FAmXof4MACgkQuEXOUQ+b
cU0n4Q/9GOd8fnSvV2+5ClWe488qi8g6DLaCVCz7EI5s7AXbZjc2sqFgv1lw1MIi
WAvSJ0Xsy5i7ctuOrIdapT9nd+vrn8w9Kd/tytwf7QJVfXCUx/kqgTniT2VPV/2n
uBeQ6Tek3yjO1+mCNUlJwI1d6ha4hSx1iaqetqAWMVci5I/0s77cuu2lcnClId2h
XtVOq2Ha0ranaJeqd7LjXIFanYLeP3FwfcEfXX8QH8xWn9NJMLI7z22hXP7PilrA
y8TJoWYIKhRsS2el7XNBlxc4wUrpbcqMSYNyI8Jfknq859D26vjqXb6quaBFyqwm
rTlY0ANDRFnOk6byeL37qDk3nYZivHuAnf+o6kCGXMH6MK5xYZqJTaAUSwFAclgm
wKBxMAlnuFl0x5iOXHo3Vri1DzQpZ+hqvINTCjBbVgA++EiLUxr3Wf7Y0okh7/Y5
WEhR963x/kYi/7y7kdB1n1K2edpP+O3da+JtEyo6ZWeSBFtS8lAwzE2oaIAxU4AY
nj8r3P6ArEfoFg25sm3PztFoSg55WLCwObu7y6QivvghG9YxSCC7lHZXdmU8TGd1
YzUN9aKUY/NWFOfD8qP+dFTyKl4N0Bpuv6s+2uZ7Q8n5fC0Vz3J9Up57IEeRyk84
Gwi9aqVi5Yc7QAOIyn0Gb7DFmXfUbfyYefInMofYvNOXpu+XMfI=
=F2aQ
-END PGP SIGNATURE-



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

Bug#1065552: fakeroot: FTBFS on armhf and armel: symbol `__lstat64_time64' is already defined

[Emanuele Rocca]

Source: fakeroot
Version: 1.34-1
Severity: serious
Tags: ftbfs
User: debian-...@lists.debian.org
Usertags: time-t

Hi,

fakeroot fails to build on armhf and armel when compiled with the time64
flags:

 -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 
-Werror=implicit-function-declaration


libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I.. -D_LARGEFILE_SOURCE 
-D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
-Werror=implicit-function-declaration -ffile-prefix-map=/<>=. 
-fstack-protector-strong -fstack-clash-protection -Wformat 
-Werror=format-security -MT libfakeroot.lo -MD -MP -MF .deps/libfakeroot.Tpo -c 
../libfakeroot.c  -fPIC -DPIC -o .libs/libfakeroot.o
/tmp/ccl7d7rC.s: Assembler messages:
/tmp/ccl7d7rC.s:10320: Error: symbol `__lstat64_time64' is already defined
/tmp/ccl7d7rC.s:10351: Error: symbol `__stat64_time64' is already defined
/tmp/ccl7d7rC.s:10382: Error: symbol `__fstat64_time64' is already defined
/tmp/ccl7d7rC.s:10413: Error: symbol `__fstatat64_time64' is already defined
make[4]: *** [Makefile:682: libfakeroot.lo] Error 1

Bug#1065494: marked as done (libgtk-3-0t64: 64-bit time_t transition breaks gtk+3.0 immodule cache)

[Debian Bug Tracking System]

Your message dated Wed, 06 Mar 2024 13:49:52 +
with message-id 
and subject line Bug#1065494: fixed in gtk+3.0 3.24.41-2
has caused the Debian Bug report #1065494,
regarding libgtk-3-0t64: 64-bit time_t transition breaks gtk+3.0 immodule cache
to be marked as done.

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

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


-- 
1065494: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065494
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libgtk-3-0t64
Version: 3.24.41-1.1
Severity: normal
X-Debbugs-Cc: yokota.h...@gmail.com, vor...@debian.org, 
debian-de...@lists.debian.org
Usertags: time-t

Dear Maintainer,

libgtk-3-0 package generates cache file
/usr/lib/${arch}/gtk-3.0/3.0.0/immodules.cache
when installing, and removes this cache file when removing the package.

This behavior is good in most cases, but not so good in 64-bit time_t
transition.
Because this behavior accidentally drops the cache file

If the cache file is missing, gtk3 immodules will not works.

Reinstall libgtk-3-0t64 package will rebuild the cache file, and immodules
works again.

libglib2.0-0t64 package had same bug, but fixed.
Please checkout there fix.

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065022
https://salsa.debian.org/gnome-
team/glib/-/commit/55e33e4eb3165e66d9bf0f6598a6a59c9cedda4c


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

Kernel: Linux 6.7.7-amd64 (SMP w/16 CPU threads; PREEMPT)
Locale: LANG=ja_JP.UTF-8, LC_CTYPE=ja_JP.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 libgtk-3-0t64 depends on:
ii  adwaita-icon-theme 46~beta-4
ii  hicolor-icon-theme 0.17-2
ii  libatk-bridge2.0-0t64  2.51.90-2
ii  libatk1.0-0t64 2.51.90-2
ii  libc6  2.37-15.1
ii  libcairo-gobject2  1.18.0-1+b1
ii  libcairo2  1.18.0-1+b1
ii  libcloudproviders0 0.3.5-1
ii  libcolord2 1.4.7-1
ii  libcups2t642.4.7-1.2+b1
ii  libepoxy0  1.5.10-1+b2
ii  libfontconfig1 2.15.0-1
ii  libfribidi01.0.13-3+b1
ii  libgdk-pixbuf-2.0-02.42.10+dfsg-3+b1
ii  libglib2.0-0t642.78.4-3
ii  libgtk-3-common3.24.41-1.1
ii  libharfbuzz0b  8.3.0-2
ii  libpango-1.0-0 1.52.0+ds-1
ii  libpangocairo-1.0-01.52.0+ds-1
ii  libpangoft2-1.0-0  1.52.0+ds-1
ii  libwayland-client0 1.22.0-2.1+b1
ii  libwayland-cursor0 1.22.0-2.1+b1
ii  libwayland-egl11.22.0-2.1+b1
ii  libx11-6   2:1.8.7-1
ii  libxcomposite1 1:0.4.5-1
ii  libxcursor11:1.2.1-1
ii  libxdamage11:1.1.6-1
ii  libxext6   2:1.3.4-1+b1
ii  libxfixes3 1:6.0.0-2
ii  libxi6 2:1.8.1-1
ii  libxinerama1   2:1.1.4-3
ii  libxkbcommon0  1.6.0-1
ii  libxrandr2 2:1.5.2-2+b1
ii  shared-mime-info   2.4-1

Versions of packages libgtk-3-0t64 recommends:
ii  libgtk-3-bin 3.24.41-1.1
ii  librsvg2-common  2.54.7+dfsg-2

Versions of packages libgtk-3-0t64 suggests:
ii  gvfs  1.53.90-3

Versions of packages libgtk-3-0t64 is related to:
pn  appmenu-gtk3-module   
pn  fcitx-frontend-gtk3   
pn  gcin-gtk3-immodule
pn  gtk-vector-screenshot 
pn  gtk3-engines-xfce 
pn  gtk3-im-libthai   
pn  hime-gtk3-immodule
ii  ibus-gtk3 1.5.29-1
pn  imhangul-gtk3 
ii  libcanberra-gtk3-module   0.30-12
pn  libcaribou-gtk3-module
pn  libgtk3-nocsd0
pn  maliit-inputcontext-gtk3  
pn  packagekit-gtk3-module
pn  scim-gtk-immodule 
pn  topmenu-gtk3  
pn  uim-gtk3  
pn  uim-gtk3-immodule 

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: gtk+3.0
Source-Version: 3.24.41-2
Done: Simon McVittie 

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

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

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

Debian distribution maintenance software
pp.
Simon McVittie  (supplier of updated gtk+3.0 package)

(This message was generated automatically at their request; if you
believe that there is a problem with it 

Bug#1065493: marked as done (libgtk2.0-0t64: 64-bit time_t transition breaks gtk+2.0 immodule cache)

[Debian Bug Tracking System]

Your message dated Wed, 06 Mar 2024 13:49:20 +
with message-id 
and subject line Bug#1065493: fixed in gtk+2.0 2.24.33-4
has caused the Debian Bug report #1065493,
regarding libgtk2.0-0t64: 64-bit time_t transition breaks gtk+2.0 immodule cache
to be marked as done.

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

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


-- 
1065493: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065493
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libgtk2.0-0t64
Version: 2.24.33-3.1
Severity: normal
X-Debbugs-Cc: yokota.h...@gmail.com, vor...@debian.org, 
debian-de...@lists.debian.org

Dear Maintainer,

libgtk2.0-0 package generates cache file
/usr/lib/${arch}/gtk-2.0/2.10.0/immodules.cache
when installing, and removes this cache file when removing the package.

This behavior is good in most cases, but not so good in 64-bit time_t
transition.
Because this behavior accidentally drops the cache file

If the cache file is missing, gtk2 immodules will not works.

Reinstall libgtk2.0-0t64 package will rebuild the cache file, and immodules
works again.

libglib2.0-0t64 package had same bug, but fixed.
Please checkout there fix.

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065022
https://salsa.debian.org/gnome-
team/glib/-/commit/55e33e4eb3165e66d9bf0f6598a6a59c9cedda4c


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

Kernel: Linux 6.7.7-amd64 (SMP w/16 CPU threads; PREEMPT)
Locale: LANG=ja_JP.UTF-8, LC_CTYPE=ja_JP.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 libgtk2.0-0t64 depends on:
ii  adwaita-icon-theme   46~beta-4
ii  gnome-icon-theme 3.12.0-5
ii  hicolor-icon-theme   0.17-2
ii  libatk1.0-0t64   2.51.90-2
ii  libc62.37-15.1
ii  libcairo21.18.0-1+b1
ii  libcups2t64  2.4.7-1.2+b1
ii  libfontconfig1   2.15.0-1
ii  libgdk-pixbuf-2.0-0  2.42.10+dfsg-3+b1
ii  libglib2.0-0t64  2.78.4-3
ii  libgtk2.0-common 2.24.33-3.1
ii  libpango-1.0-0   1.52.0+ds-1
ii  libpangocairo-1.0-0  1.52.0+ds-1
ii  libpangoft2-1.0-01.52.0+ds-1
ii  libx11-6 2:1.8.7-1
ii  libxcomposite1   1:0.4.5-1
ii  libxcursor1  1:1.2.1-1
ii  libxdamage1  1:1.1.6-1
ii  libxext6 2:1.3.4-1+b1
ii  libxfixes3   1:6.0.0-2
ii  libxi6   2:1.8.1-1
ii  libxinerama1 2:1.1.4-3
ii  libxrandr2   2:1.5.2-2+b1
ii  libxrender1  1:0.9.10-1.1
ii  shared-mime-info 2.4-1

Versions of packages libgtk2.0-0t64 recommends:
ii  libgail-common   2.24.33-3.1
ii  libgtk2.0-bin2.24.33-3.1
ii  librsvg2-common  2.54.7+dfsg-2

Versions of packages libgtk2.0-0t64 suggests:
ii  gvfs  1.53.90-3

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: gtk+2.0
Source-Version: 2.24.33-4
Done: Simon McVittie 

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

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

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

Debian distribution maintenance software
pp.
Simon McVittie  (supplier of updated gtk+2.0 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 06 Mar 2024 12:31:37 +
Source: gtk+2.0
Architecture: source
Version: 2.24.33-4
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Simon McVittie 
Closes: 1065493
Changes:
 gtk+2.0 (2.24.33-4) unstable; urgency=medium
 .
   * Team upload
   * d/libgtk2.0-0t64.preinst: Remove libgtk2.0-0 postrm to avoid loss of
 input method modules during upgrade (Closes: #1065493)
   * d/tests/manual/1065493.sh: Add a manual reproducer for #1065493
   * d/libgtk2.0-0t64.postrm.in: Only clean up immodules.cache during purge.
 This avoids input methods becoming briefly unavailable during upgrades.
   * d/libgtk2.0-0t64.postrm.in: Avoid recurrence of #1065493 in the future,
 by not deleting immodules.cache (even during purge) unless the immodules
 directory no longer exists.
   * 

Bug#1064375: Raising severity of rust-gtk bugs

[Matthias Geiger]

On Sun, 3 Mar 2024 10:01:21 -0500 =?UTF-8?Q?Jeremy_B=C3=ADcha?= 
 wrote:

> Control: severity -1 serious
>
> at-spi2-core is part of the 64-bit time_t transition. The new version
> of at-spi2-core is causing rust-atk-sys' autopkgtest to fail.
> rust-atk-sys and the rest of the Rust GTK3 stack is no longer
> maintained upstream. One way to handle this is to ignore failures of
> the overly sensitive autopkgtest. But it also makes the GNOME 46 Rust
> transition easier if we don't need to tweak or fix all the Rust GTK3
> stuff ourselves.
>
> Therefore, I am raising the severity of this bug and we will probably
> ask the Debian Release Team to remove these packages from Testing even
> faster than the automatic removal process.
>
> Thank you,
> Jeremy Bícha
>

>

It is now EOL/deprecated officialy upstream: 
https://github.com/gtk-rs/gtk3-rs.


I managed to vendor in the crates for squeekboard but I couldn't get it 
to build, will look into it more but would appreciate a second opinion. 
For gtklayershell / swayosd we can do the same; building


a mix of vendored and packaged crates works.

best,

--
Matthias Geiger 
Debian Maintainer



OpenPGP_0x18BD106B3B6C5475.asc
Description: OpenPGP public key


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1065494: marked as pending in gtk+3.0

[Simon McVittie]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/gnome-team/gtk3/-/commit/1c4fb7e79ab1d3c28a957b777e692afa09afdc52


d/libgtk-3-0t64.preinst: Remove libgtk-3-0 postrm to avoid file loss

During the migration from libgtk-3-0 to libgtk-3-0t64, the package
that is responsible for "owning" /usr/lib/*/gtk-3.0/3.0.0/immodules.cache
changed from libgtk-3-0 to libgtk-3-0t64. Because dpkg does not have an
equivalent of RPM's %ghost files, the ownership of this file is managed
by social convention rather than by the package management system.

Unfortunately, libgtk-3-0's postrm as shipped in Debian releases from
2010 to the present is not aware of the possibility that another binary
package might need to take over responsibility for this file, and so
will remove it during purge (and in fact also during upgrades) in
accordance with the requirement that the package must not leave unowned
files behind. This causes input methods to be non-functional in GTK apps
until the next time the gtk-query-immodules-3.0 trigger happens to be run.

To disarm the problematic maintainer script, delete it during the new
package's preinst, similar to what was done for GLib in response
to #1065022.

A subsequent commit will improve the postrm so that if we find that we
need to migrate from libgtk-3-0t64 to libgtk-3-0xyz at some point in
the future, similar efforts will not be needed.

Closes: #1065494


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1065494

Processed: Bug#1065493 marked as pending in gtk+2.0

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1065493 [libgtk2.0-0t64] libgtk2.0-0t64: 64-bit time_t transition breaks 
gtk+2.0 immodule cache
Added tag(s) pending.

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

Processed: Bug#1065494 marked as pending in gtk+3.0

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1065494 [libgtk-3-0t64] libgtk-3-0t64: 64-bit time_t transition breaks 
gtk+3.0 immodule cache
Added tag(s) pending.

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

Bug#1065493: marked as pending in gtk+2.0

[Simon McVittie]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/gnome-team/gtk2/-/commit/3406805d5833fc78ccab4c1aaff3cbc9e9197799


d/libgtk2.0-0t64.preinst: Remove libgtk2.0-0 postrm to avoid file loss

During the migration from libgtk2.0-0 to libgtk2.0-0t64, the package
that is responsible for "owning" /usr/lib/*/gtk-2.0/2.10.0/immodules.cache
changed from libgtk2.0-0 to libgtk2.0-0t64. Because dpkg does not have an
equivalent of RPM's %ghost files, the ownership of this file is managed
by social convention rather than by the package management system.

Unfortunately, libgtk2.0-0's postrm as shipped in Debian releases from
2010 to the present is not aware of the possibility that another binary
package might need to take over responsibility for this file, and so
will remove it during purge (and in fact also during upgrades) in
accordance with the requirement that the package must not leave unowned
files behind. This causes input methods to be non-functional in GTK apps
until the next time the gtk-query-immodules-2.0 trigger happens to be run.

To disarm the problematic maintainer script, delete it during the new
package's preinst, similar to what was done for GLib in response
to #1065022.

A subsequent commit will improve the postrm so that if we find that we
need to migrate from libgtk2.0-0t64 to libgtk2.0-0xyz at some point in
the future, similar efforts will not be needed.

Closes: #1065493


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1065493

Processed: Re: Bug#1065547: gst-python1.0 FTBFS: TypeError: function takes at most 0 arguments

[Debian Bug Tracking System]

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

> forwarded 1065547 
> https://gitlab.freedesktop.org/gstreamer/gstreamer/-/issues/3353
Bug #1065547 [src:gst-python1.0] gst-python1.0 FTBFS: TypeError: function takes 
at most 0 arguments
Set Bug forwarded-to-address to 
'https://gitlab.freedesktop.org/gstreamer/gstreamer/-/issues/3353'.
>
End of message, stopping processing here.

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

Bug#1065510: marked as pending in nodejs

[Jérémy Lal]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/js-team/nodejs/-/commit/9cd4fef17e123f54db448b1606f54752c73e33e0


ABIt64: drop libnode108t64.install. Closes: #1065510.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1065510

Processed: Bug#1065510 marked as pending in nodejs

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1065510 [libnode108t64] libnode108t64 is broken on !amd64
Added tag(s) pending.

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

Bug#1065549: marked as done (gst-python1.0: Fails to build because of build test failures)

[Debian Bug Tracking System]

Your message dated Wed, 6 Mar 2024 08:20:38 -0500
with message-id 

and subject line Re: Bug#1065549: gst-python1.0: Fails to build because of 
build test failures
has caused the Debian Bug report #1065549,
regarding gst-python1.0: Fails to build because of build test failures
to be marked as done.

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

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


-- 
1065549: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065549
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gst-python1.0
Version: 1.24.0-1
Severity: serious
Tags: ftbfs sid
Forwarded: https://gitlab.freedesktop.org/gstreamer/gstreamer/-/issues/3353

gst-python1.0 fails to build from source because of build test
failures. The failures look concerning so I reported the issue to the
upstream developers:

https://buildd.debian.org/status/package.php?p=gst-python1.0

Thank you,
Jeremy Bícha
--- End Message ---
--- Begin Message ---
duplicate bug

Thank you,
Jeremy Bícha--- End Message ---

Processed (with 2 errors): Re: Bug#1065547: gst-python1.0 FTBFS: TypeError: function takes at most 0 arguments

[Debian Bug Tracking System]

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

> tags 1065547 +sid
Bug #1065547 [src:gst-python1.0] gst-python1.0 FTBFS: TypeError: function takes 
at most 0 arguments
Added tag(s) sid.
> forwarded 1065547
Unknown command or malformed arguments to command.
> https://gitlab.freedesktop.org/gstreamer/gstreamer/-/issues/3353
Unknown command or malformed arguments to command.
>
End of message, stopping processing here.

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

Bug#1065549: gst-python1.0: Fails to build because of build test failures

[Jeremy Bícha]

Source: gst-python1.0
Version: 1.24.0-1
Severity: serious
Tags: ftbfs sid
Forwarded: https://gitlab.freedesktop.org/gstreamer/gstreamer/-/issues/3353

gst-python1.0 fails to build from source because of build test
failures. The failures look concerning so I reported the issue to the
upstream developers:

https://buildd.debian.org/status/package.php?p=gst-python1.0

Thank you,
Jeremy Bícha

Bug#1065548: octave-statistics: binary-any FTBFS

[Adrian Bunk]

Source: octave-statistics
Version: 1.6.4-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/logs.php?pkg=octave-statistics=1.6.4-1

...
   debian/rules execute_after_dh_installdeb
make[1]: Entering directory '/<>'
# Use local JavaScript and CSS files
debian/local-url
sed: can't read 
debian/octave-statistics-common/usr/share/doc/octave-statistics-common/docs/*.html:
 No such file or directory
# Remove empty directory
rmdir 
debian/octave-statistics-common/usr/share/octave/packages/statistics-*/doc/
rmdir: failed to remove 
'debian/octave-statistics-common/usr/share/octave/packages/statistics-*/doc/': 
No such file or directory
make[1]: *** [debian/rules:15: execute_after_dh_installdeb] Error 1

Bug#1065547: gst-python1.0 FTBFS: TypeError: function takes at most 0 arguments

[Adrian Bunk]

Source: gst-python1.0
Version: 1.23.90-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/logs.php?pkg=gst-python1.0=1.23.90-1
https://buildd.debian.org/status/logs.php?pkg=gst-python1.0=1.24.0-1

...
 3/3 =
test: Test fundamentals
start time:   12:22:01
duration: 2.03s
result:   exit status 1
command:  ASAN_OPTIONS=halt_on_error=1:abort_on_error=1:print_summary=1 
GST_OVERRIDE_BUILD_PATH=/<>/build-3.12/testsuite/../gi/overrides 
UBSAN_OPTIONS=halt_on_error=1:abort_on_error=1:print_summary=1:print_stacktrace=1
 MALLOC_PERTURB_=73 
GST_PLUGIN_LOADING_WHITELIST=gstreamer:gst-plugins-base:gst-python@/<>/build-3.12
 GST_REGISTRY='/<>/build-3.12/testsuite/Test 
fundamentals.registry' 
GST_PLUGIN_PATH_1_0=/<>/build-3.12:/usr/lib/x86_64-linux-gnu/gstreamer-1.0:/usr/lib/x86_64-linux-gnu/gstreamer-1.0:/<>/build-3.12/plugin:/<>/testsuite
 GST_OVERRIDE_SRC_PATH=/<>/testsuite/../gi/overrides 
/usr/bin/python3.12 /<>/build-3.12/../testsuite/runtests.py 
test_types.py
--- stderr ---
.EE.
==
ERROR: testConstructor (test_types.TestBitmask.testConstructor)
--
Traceback (most recent call last):
  File "/<>/testsuite/test_types.py", line 387, in testConstructor
r = Gst.Bitmask(1 << 5)
^^^
TypeError: function takes at most 0 arguments (1 given)

==
ERROR: testGetValue (test_types.TestBitmask.testGetValue)
--
Traceback (most recent call last):
  File "/<>/testsuite/test_types.py", line 393, in testGetValue
self.assertEqual(Gst.Structure('test,test=(bitmask)0x20')['test'], 1 << 5)
 
  File "/<>/testsuite/../gi/overrides/Gst.py", line 330, in 
__getitem__
return self.get_value(key)
   ^^^
TypeError: function takes at most 0 arguments (1 given)

==
ERROR: testStr (test_types.TestBitmask.testStr)
--
Traceback (most recent call last):
  File "/<>/testsuite/test_types.py", line 398, in testStr
r = Gst.Bitmask(1 << 5)
^^^
TypeError: function takes at most 0 arguments (1 given)
...
FAILED (errors=30)
==


Summary of Failures:

3/3 Test fundamentals FAIL2.03s   exit status 1

Ok: 2   
Expected Fail:  0   
Fail:   1   
Unexpected Pass:0   
Skipped:0   
Timeout:0   
dh_auto_test: error: cd build-3.12 && DEB_PYTHON_INSTALL_LAYOUT=deb 
LC_ALL=C.UTF-8 MESON_TESTTHREADS=6 meson test returned exit code 1
make[1]: *** [debian/rules:28: override_dh_auto_test] Error 25

Bug#1060260: marked as done (epics-base: FTBFS on amd64, arm64)

[Debian Bug Tracking System]

Your message dated Wed, 06 Mar 2024 12:49:30 +
with message-id 
and subject line Bug#1060260: fixed in epics-base 7.0.8+dfsg1-1
has caused the Debian Bug report #1060260,
regarding epics-base: FTBFS on amd64, arm64
to be marked as done.

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

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


-- 
1060260: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060260
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: epics-base
Version: 7.0.7+dfsg1-5
Severity: serious
Tag: ftbfs

Your package failed to build from source in binNMUs to move systemd
files. Please see f.e. this build log:
https://buildd.debian.org/status/fetch.php?pkg=epics-base=amd64=7.0.7%2Bdfsg1-5%2Bb1=1704674513=0

Last parts:
Test Summary Report
---
testpvif.t   (Wstat: 0 Tests: 98 Failed: 0)
  TODO passed:   40
testpvalink.t(Wstat: 0 Tests: 20 Failed: 0)
  TODO passed:   9
Files=7, Tests=363,  4 wallclock secs ( 0.08 usr  0.03 sys +  0.26 cusr  0.09 
csys =  0.46 CPU)
Result: PASS
---

...

Tests failed in:
/<>/modules/pvAccess/testApp/O.linux-x86_64
/<>/modules/pvDatabase/test/O.linux-x86_64
make[2]: *** [configure/RULES_TOP:62: runtests] Error 1
make[2]: Leaving directory '/<>'
make[1]: *** [debian/rules:31: override_dh_auto_test] Error 2
make[1]: Leaving directory '/<>'
make: *** [debian/rules:22: build-arch] Error 2
dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit 
status 2

Build finished at 2024-01-08T00:41:45Z
--- End Message ---
--- Begin Message ---
Source: epics-base
Source-Version: 7.0.8+dfsg1-1
Done: Picca Frédéric-Emmanuel 

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

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

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

Debian distribution maintenance software
pp.
Picca Frédéric-Emmanuel  (supplier of updated epics-base 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 06 Mar 2024 13:32:42 +0100
Source: epics-base
Architecture: source
Version: 7.0.8+dfsg1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Picca Frédéric-Emmanuel 
Closes: 1059706 1060260
Changes:
 epics-base (7.0.8+dfsg1-1) unstable; urgency=medium
 .
   [ Sébastien Delafond ]
   * d/control: remove myself from uploaders
 .
   [ Andrius Merkys ]
   * Fix pkgconfig file location in epics-dev binary package.
   * Bug fix: "epics-base.pc is broken in epics-dev package", thanks to
 Matwey V. Kornilov (Closes: #1059706).
 .
   [ Picca Frédéric-Emmanuel ]
   * New upstream release.
   * Bug fix: "FTBFS on amd64, arm64", thanks to Chris Hofstaedtler
 (Closes: #1060260).
Checksums-Sha1:
 8364d44f356dfd76bcf4f3956b4846fc31eb6169 2590 epics-base_7.0.8+dfsg1-1.dsc
 8d60e5c295b3b5a9bc1323cf22b2421df7d02c2b 1974480 
epics-base_7.0.8+dfsg1.orig.tar.xz
 a8ee250320bc8caf83a9ca28eff83e8ebc5b9b01 10436 
epics-base_7.0.8+dfsg1-1.debian.tar.xz
Checksums-Sha256:
 44c6174766e99499a3ed8a4d2f5ac92d982e0f9f4e0bbf4933abfaae4ce57272 2590 
epics-base_7.0.8+dfsg1-1.dsc
 e1d0e1dfe7577a258b8ed489a1d289d191b14716dd59f568590775f176504764 1974480 
epics-base_7.0.8+dfsg1.orig.tar.xz
 5b875aae508e51581616199cc32d1d3a596390b91c1b05f97eb43bffc2c805ba 10436 
epics-base_7.0.8+dfsg1-1.debian.tar.xz
Files:
 2fbe79ad1dced2e3413beb3be1ca9380 2590 science optional 
epics-base_7.0.8+dfsg1-1.dsc
 5be5bfcf54d691a000408b25889739e9 1974480 science optional 
epics-base_7.0.8+dfsg1.orig.tar.xz
 3bb1a14898b877cfa45b8f5a16f2 10436 science optional 
epics-base_7.0.8+dfsg1-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEE2bRTt5m4gw2UXmoKW/VOXhK5ALsFAmXoYvERHHBpY2NhQGRl
Ymlhbi5vcmcACgkQW/VOXhK5ALvEpQ/+N/YrIH0BWl5GRvrNLbvqzIR7IVQ5CMzu
BBIVuhSNnHnIJAeh+ubjmM7MXLgruRWyKKqrGY33FBWL1DWteJoZsObT9zu0+b1r
QLQRr2aTxp1fQRZhYzLK+vv7xy+A0DSjoILTV7itEhyAap+fL7DcFoEKSl/bvSrg
+6sk3Ad20LawYpDstIlFzkYYQtNGqH5SdD66xwvVEuG4YwZNk4U1ZL5VV2zoVV2l
x7QbSfCelrnkrcsEqQ3R/Gv52ybbS0aO5pWE77JSFsHFaGQaJoGYf4yEQiQClTHi
nQ5Fp98l6Ir9JhLLnRFAc8OR1Bzrx9l08xJpUJRV7PVOJAzmUBTOUPLxmqErBtjv

Bug#1055845: marked as done (matplotlib: Build-Depends on python3-xarray which is not in testing)

[Debian Bug Tracking System]

Your message dated Wed, 6 Mar 2024 12:39:47 +
with message-id 
and subject line Re: Bug#1055845: matplotlib: Build-Depends on python3-xarray 
which is not in testing
has caused the Debian Bug report #1055845,
regarding matplotlib: Build-Depends on python3-xarray which is not in testing
to be marked as done.

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

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


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

Hi Maintainer

matplotlib has a build-dependency on python3-xarray which is no longer
in testing.

Please drop this build-dependency or help get python3-xarray back into testing.

Regards
Graham
--- End Message ---
--- Begin Message ---
On Sun, Nov 12, 2023 at 01:49:34PM -0100, Graham Inggs wrote:
> matplotlib has a build-dependency on python3-xarray which is no longer
> in testing.
> 
> Please drop this build-dependency or help get python3-xarray back into 
> testing.

According to https://tracker.debian.org/pkg/python-xarray,
python3-xarray got back into testing on 2024-01-31.  Closing this bug.

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

Bug#1065538: bind9-libs hard-codes a dependency on libuv1

[Ondřej Surý]

The reason why we do so is that libuv has some changes between version that 
don’t propagate to ABI. I might be able to drop this in unstable though and 
just keep it for backports.
--
Ondřej Surý (He/Him)

> On 6. 3. 2024, at 12:45, Matthias Klose  wrote:
> 
> Package: bind9-libs
> Version: 1:9.19.21-1
> Severity: serious
> Tags: sid trixie
> 
> bind9-libs hard-codes a dependency on libuv1, that should be libuv1t64 now. 
> But better derive it form the libuv1-dev dependency.
> 

Processed: bug 1065494 is forwarded to https://salsa.debian.org/gnome-team/gtk3/-/merge_requests/22 ...

[Debian Bug Tracking System]

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

> forwarded 1065494 https://salsa.debian.org/gnome-team/gtk3/-/merge_requests/22
Bug #1065494 [libgtk-3-0t64] libgtk-3-0t64: 64-bit time_t transition breaks 
gtk+3.0 immodule cache
Set Bug forwarded-to-address to 
'https://salsa.debian.org/gnome-team/gtk3/-/merge_requests/22'.
> forwarded 1065493 https://salsa.debian.org/gnome-team/gtk2/-/merge_requests/3
Bug #1065493 [libgtk2.0-0t64] libgtk2.0-0t64: 64-bit time_t transition breaks 
gtk+2.0 immodule cache
Set Bug forwarded-to-address to 
'https://salsa.debian.org/gnome-team/gtk2/-/merge_requests/3'.
> thanks
Stopping processing here.

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

Bug#1065395: marked as done (spirv-llvm-translator-14: autopkgtest on s390x uses huge amount of disk space)

[Debian Bug Tracking System]

Your message dated Wed, 06 Mar 2024 11:50:46 +
with message-id 
and subject line Bug#1065395: fixed in spirv-llvm-translator-14 14.0.0-12
has caused the Debian Bug report #1065395,
regarding spirv-llvm-translator-14: autopkgtest on s390x uses huge amount of 
disk space
to be marked as done.

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

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


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

Source: spirv-llvm-translator-14
Version: 14.0.0-10
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: issue

Dear maintainers,

Since a couple of days, our workers on s390x are dying because some test
is filling up all disk space. Several days ago, I wrongly suspected 
src:fenics-dolfinx (bug #1064995) and added it to our reject-list. It 
didn't solve the issue, so today I spend more time on finding the 
culprit. Basically every spike above 40% in the graph [1] is a moment 
that we see issues like:


Feb 28 05:38:18 ci-worker-s390x-01 debci[1738391]: gzip:
/tmp/debci-worker-43383540-cNnbLE372K/autopkgtest-incoming/testing/s390x/f/fenics-dolfinx/43383540/log.gz: 


No space left on device
Feb 28 05:38:18 ci-worker-s390x-01 debci[1424101]: E: Test for package
fenics-dolfinx produced no exit code, aborting

One of the suspects started to be spirv-llvm-translator-14, so I ran its 
autopkgtest manually, while logging disk use every 10 seconds (I started 
slightly delayed because I monitored the wrong partition first). As you 
can see below, during the test it grows from 17 GB (at the end) to its 
peak at 179 GB. That's not acceptable on our infrastructure. One file I 
happened to spot on the way was 
build/test/test_output/DebugInfo/Generic/Output/two-cus-from-same-file.ll.tmp:

-rw-r--r-- 1 root root  41G Mar  3 19:18 two-cus-from-same-file.ll.tmp

I have added spirv-llvm-translator-14 to our reject-list on s390x.

As this seems to be a rather new issue, I'm wondering if it's due to:
* Add build-needed autopkgtest for spirv-headers compat check.

Or maybe something in the toolchain that broke on s390x?

Paul

[1]
https://ci.debian.net/munin/ci-worker-s390x-01/ci-worker-s390x-01/df.html

/dev/mapper/3600507630affd250004a  196G   40G  146G  22% 
/scratch
/dev/mapper/3600507630affd250004a  196G   49G  138G  27% 
/scratch
/dev/mapper/3600507630affd250004a  196G   57G  130G  31% 
/scratch
/dev/mapper/3600507630affd250004a  196G   65G  122G  35% 
/scratch
/dev/mapper/3600507630affd250004a  196G   66G  121G  36% 
/scratch
/dev/mapper/3600507630affd250004a  196G   67G  120G  36% 
/scratch
/dev/mapper/3600507630affd250004a  196G   70G  117G  38% 
/scratch
/dev/mapper/3600507630affd250004a  196G   73G  114G  40% 
/scratch
/dev/mapper/3600507630affd250004a  196G   76G  111G  41% 
/scratch
/dev/mapper/3600507630affd250004a  196G   79G  108G  43% 
/scratch
/dev/mapper/3600507630affd250004a  196G   83G  104G  45% 
/scratch
/dev/mapper/3600507630affd250004a  196G   85G  101G  46% 
/scratch
/dev/mapper/3600507630affd250004a  196G   88G   98G  48% 
/scratch
/dev/mapper/3600507630affd250004a  196G   92G   95G  50% 
/scratch
/dev/mapper/3600507630affd250004a  196G   95G   92G  51% 
/scratch
/dev/mapper/3600507630affd250004a  196G   98G   89G  53% 
/scratch
/dev/mapper/3600507630affd250004a  196G  101G   86G  54% 
/scratch
/dev/mapper/3600507630affd250004a  196G  104G   83G  56% 
/scratch
/dev/mapper/3600507630affd250004a  196G  107G   80G  58% 
/scratch
/dev/mapper/3600507630affd250004a  196G   65G  122G  35% 
/scratch
/dev/mapper/3600507630affd250004a  196G   65G  122G  35% 
/scratch
/dev/mapper/3600507630affd250004a  196G   66G  121G  36% 
/scratch
/dev/mapper/3600507630affd250004a  196G   68G  118G  37% 
/scratch
/dev/mapper/3600507630affd250004a  196G   72G  115G  39% 
/scratch
/dev/mapper/3600507630affd250004a  196G   75G  112G  41% 
/scratch
/dev/mapper/3600507630affd250004a  196G   78G  109G  42% 
/scratch
/dev/mapper/3600507630affd250004a  196G   81G  106G  44% 
/scratch
/dev/mapper/3600507630affd250004a  196G   85G  102G  46% 
/scratch
/dev/mapper/3600507630affd250004a  196G   87G   99G  47% 
/scratch
/dev/mapper/3600507630affd250004a  196G   90G   96G  49% 

Bug#1065538: bind9-libs hard-codes a dependency on libuv1

[Matthias Klose]

Package: bind9-libs
Version: 1:9.19.21-1
Severity: serious
Tags: sid trixie

bind9-libs hard-codes a dependency on libuv1, that should be libuv1t64 
now. But better derive it form the libuv1-dev dependency.

Bug#1065395: [Pkg-opencl-devel] Bug#1065395: Bug#1065395: spirv-llvm-translator-14: autopkgtest on s390x uses huge amount of disk space

[Andreas Beckmann]

On 06/03/2024 11.01, Paul Gevers wrote:

Hi,

On 06-03-2024 10:30 a.m., Andreas Beckmann wrote:

Do you have the log from running that autopkgtest?
I have no idea what's happening here. At least the buildd build only 
used 500 MB.


Attached.


Thanks. Actually, we were running the testsuite twice. Once by the build 
(that one was new), and once as regular autopkgtest (that has been done 
for some time already). So the issue should not have been really new, we 
just doubled the extreme disk space usage with the -10 upload ;-)


I'm disabling that autopkgtest on s390x now.


Andreas

PS: updating -15+ might be a bit delayed since I found a regression in 
the upstream branch yesterday ..

Bug#1065303: marked as done (dmrgpp: switch to boost 1.83)

[Debian Bug Tracking System]

Your message dated Wed, 06 Mar 2024 10:34:20 +
with message-id 
and subject line Bug#1065303: fixed in dmrgpp 6.06-2
has caused the Debian Bug report #1065303,
regarding dmrgpp: switch to boost 1.83
to be marked as done.

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

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


-- 
1065303: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065303
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: dmrgpp
Version: 6.06-1
Severity: serious
X-Debbugs-Cc: sramac...@debian.org

We'd like to release trixie without boost1.74 (see #1060102). Please
build with the current default version of boost or switch to boost1.83.

Cheers
-- 
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Source: dmrgpp
Source-Version: 6.06-2
Done: Picca Frédéric-Emmanuel 

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

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

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

Debian distribution maintenance software
pp.
Picca Frédéric-Emmanuel  (supplier of updated dmrgpp package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 06 Mar 2024 11:07:49 +0100
Source: dmrgpp
Architecture: source
Version: 6.06-2
Distribution: unstable
Urgency: medium
Maintainer: Debian PaN Maintainers 

Changed-By: Picca Frédéric-Emmanuel 
Closes: 1065303
Changes:
 dmrgpp (6.06-2) unstable; urgency=medium
 .
   * Bug fix: "switch to boost 1.83", thanks to Sebastian Ramacher (Closes:
 #1065303).
   * d/control: B-D on the generic libboost-dev instead of the versionned 
version.
Checksums-Sha1:
 8f12a5596e9b0a3876985bd8d0bc3d14a5e94722 2772 dmrgpp_6.06-2.dsc
 146b6301030f4fb1d0380837a14177381d7710b0 8728 dmrgpp_6.06-2.debian.tar.xz
Checksums-Sha256:
 c4a12b445518effd21f8e404a02148978c39844d547f8c5298b4eb302aa84ec3 2772 
dmrgpp_6.06-2.dsc
 419bdb8d15d7186b4cff7a5e544c74acfea037cc8c932abf66d550a8bfec610d 8728 
dmrgpp_6.06-2.debian.tar.xz
Files:
 61fc732a9fc31b08b5a2285136d51cd1 2772 science optional dmrgpp_6.06-2.dsc
 aa101ee339aff8401fc004117fae1036 8728 science optional 
dmrgpp_6.06-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEE2bRTt5m4gw2UXmoKW/VOXhK5ALsFAmXoQQsRHHBpY2NhQGRl
Ymlhbi5vcmcACgkQW/VOXhK5ALvCLRAAq9lp1X0ntEVr28OWtjBtoUZ40jheXWiL
LUw3lGU3E9XwwflsD+nmDGZbysXhadWLAPu0kfndubx9nfW36ISUE2KvdmMECnxD
zSHBzvjx7FgvkGh5/p6REKty3k8pQVEV6+bEkgMhfWJfXoTYGJVZBU1EgQI/mgna
DdND1mCpsL6XVa5lcTJKWXt31l+zw2TRa1Heggzs5Zj/Vv8wRFwxlA7zcrLikAkG
iPCQHQO4ytAA8gNRBT3gdhndgc7sGU0Dju5raU2/Zi10whIj9avUhzYutedyD3pY
yngLrIf7MNe6OwDDNY7oIDUZ9w8jq+1g4JS6gixbgyT066n7zDOnwNGmawHh4aS+
PHAGXIQGNbxIqtOhvsp9YYo8Nbm8gPR6B2dmdd9q+Eqock70AuLz9y1RLbXPSm/H
/kDyOczF95L113YO0H34w5LzH0tt3L+8euTDhbsEhDIhZP/xQEXujr30lzBb3RZr
3j+vT6ogZ3flQQY20VZK1l848yWL1zE6u/3YP6tduEjZlkjBXnlDZ+sSqhGeW/UT
Fw+5yU9w9WwwUihWcul/7BT2cAYFKGpA2j3zVD43NT+7BdhPVkErucP3hX5YwrUF
ViZq5ocS+3OCmpVeILiud4YtjgYXA8XQwXJCJYGBmQFllLtBEOzfaRo2BWToUbh5
U3kmXX/shUA=
=ANu1
-END PGP SIGNATURE-



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

Bug#1065395: [Pkg-opencl-devel] Bug#1065395: spirv-llvm-translator-14: autopkgtest on s390x uses huge amount of disk space

[Paul Gevers]

Hi,

On 06-03-2024 10:30 a.m., Andreas Beckmann wrote:

Do you have the log from running that autopkgtest?
I have no idea what's happening here. At least the buildd build only 
used 500 MB.


Attached.

Paul



debug.log.xz
Description: application/xz


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1065483: perl-base: should provide perlapi-5.38.2 on i386

[Sven Joachim]

Control: tags -1 + patch

On 2024-03-05 11:47 +0100, Sven Joachim wrote:

> Package: perl-base
> Version: 5.38.2-3.1
> Severity: serious
> X-Debbugs-Cc: Sven Joachim , Steve Langasek 
> 
>
> On i386, perl-base provides perlapi-5.38.2t64 rather than
> perlapi-5.38.2.  This makes tons of packages uninstallable or
> unbuildable and is not what has been agreed upon in #1060246.

There are already 229 packages in state BD-Uninstallable on i386,
on amd64 there are only 19.  Personally I have held back packages from
src:e2fsprogs, src:util-linux and src:expat due to multiarch version
skew.  This is only going to become worse.

> The reason is a bad check in debian/rules, line 31:
>
> ,
> | # If nonempty, this will determine $Config{debian_abi} and Provides: entries
> | # (otherwise, the Provides: entries will be generated by debian/mkprovides)
> | perlabi =
> | ifeq (,$(filter $(DEB_HOST_GNU_TYPE),i386 hurd-i386))
> |   ifeq ($(DEB_HOST_ARCH_BITS),32)
> | perlabi = 5.38.2t64
> |   endif
> | endif
> `
>
> Unfortunately DEB_HOST_GNU_TYPE does not match i386 or hurd-i386 on
> these architectures:
>
> ,
> | $ dpkg-architecture -ai386 -qDEB_HOST_GNU_TYPE 2>/dev/null
> | i686-linux-gnu
> | $ dpkg-architecture -ahurd-i386 -qDEB_HOST_GNU_TYPE 2>/dev/null
> | i686-gnu
> `
>
> You may want to filter on DEB_HOST_ARCH instead (make sure it is
> defined).

I have decided to fix the check for DEB_HOST_GNU_TYPE instead.  All of
this is going away anyway when perl moves on to version 5.40.

> A quick fix would be appreciated, because reverse dependencies are
> likely going to pick up the wrong perlapi Provides.

There are currently six packages depending on perlapi-5.38.2t64:i386,
but that number is likely going to grow.  The second patch adds a
hardcoded dependency not break these reverse dependencies, but it might
be preferable to just request binNMUs for them as long as there are not
too many.

Cheers,
   Sven

From 016030f4f7d4d3317016c3f9af3981030dfef913 Mon Sep 17 00:00:00 2001
From: Sven Joachim 
Date: Wed, 6 Mar 2024 09:53:06 +0100
Subject: [PATCH] Fix perlapi Provides for i386 and hurd-i386

---
 debian/rules | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/debian/rules b/debian/rules
index a5a3565..43f923e 100755
--- a/debian/rules
+++ b/debian/rules
@@ -28,7 +28,7 @@ DEB_HOST_ARCH_BITS  ?= $(shell dpkg-architecture -qDEB_HOST_ARCH_BITS)
 # If nonempty, this will determine $Config{debian_abi} and Provides: entries
 # (otherwise, the Provides: entries will be generated by debian/mkprovides)
 perlabi =
-ifeq (,$(filter $(DEB_HOST_GNU_TYPE),i386 hurd-i386))
+ifeq (,$(filter $(DEB_HOST_GNU_TYPE),i686-linux-gnu i686-gnu))
   ifeq ($(DEB_HOST_ARCH_BITS),32)
 perlabi = 5.38.2t64
   endif
--
2.43.0

From 8509b7145c29e936e4b76b83f31fbc1d397d69dc Mon Sep 17 00:00:00 2001
From: Sven Joachim 
Date: Wed, 6 Mar 2024 10:02:43 +0100
Subject: [PATCH] Temporarily provide perlapi-5.38.2t64 on i386 and hurd-i386

There are already a few packages which have picked up the new
dependency, provide perlapi-5.38.2t64 not to break them.
---
 debian/control | 1 +
 1 file changed, 1 insertion(+)

diff --git a/debian/control b/debian/control
index acc8e5a..222ae6c 100644
--- a/debian/control
+++ b/debian/control
@@ -81,6 +81,7 @@ Provides: ${perlapi:Provides},
  libfile-temp-perl (= 0.2311),
  libfile-path-perl (= 2.18),
  libio-socket-ip-perl (= 0.41),
+ perlapi-5.38.2t64 [i386 hurd-i386],
 Suggests: perl, sensible-utils
 Description: minimal Perl system
  Perl is a scripting language used in many system scripts and utilities.
--
2.43.0

Processed: Re: Bug#1065483: perl-base: should provide perlapi-5.38.2 on i386

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + patch
Bug #1065483 [perl-base] perl-base: should provide perlapi-5.38.2 on i386
Added tag(s) patch.

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

Bug#1063088: weston: NMU diff for 64-bit time_t transition

[Dylan Aïssi]

Hello,

Le lun. 5 févr. 2024 à 02:54, Steve Langasek  a écrit :
>
> If you have any concerns about this patch, please reach out ASAP.  Although
> this package will be uploaded to experimental immediately, there will be a
> period of several days before we begin uploads to unstable; so if information
> becomes available that your package should not be included in the transition,
> there is time for us to amend the planned uploads.
>

I am wondering what is the plan with this package/bug? I noticed that changes
related to the 64-bit time_t transition were not uploaded to unstable and
because I uploaded several versions in unstable after your NMU in exp, I
wonder if I haven't interfered with this transition.

Best regards,
Dylan

Bug#1053004: CVE-2019-10784 and CVE-2023-40619

[Leandro Cunha]

Hi Christoph Berg,

On Wed, Mar 6, 2024 at 5:42 AM Christoph Berg  wrote:
>
> Re: Leandro Cunha
> > The
> > next job would be to make it available through backports and I would
> > choose to remove this package from stable. But I would only leave
> > bookworm backports due to other bugs found (this CVEs too) and fixed
> > in 7.14.7.
> > I have to search about the status of backports to oldstable. But I'm
> > also studying the possibility of working with patches for these two
> > versions.
>
> Why would you want to remove it from stable? In closed environments,
> CVEs are often not a problem.
>
> Christoph

In addition to the CVEs, phppgadmin which is present in stable does
not connect to PostgreSQL 15 and 16 without a patch I inserted in
7.13.0+dfsg-3, but I can add the same patch by reopening bug #1029516
or opening another important bug (I am aware that the bug must have a
severity greater than important)[3] for the stable and submission of
new bug to the release team for approval. That way it would be
released in a future release a version with this issue fixed (if
approved). But CVE-2023-40619 is treated with critical severity and
CVE-2019-10784 is also critical according to the NVD[1][2]. The Debian
LTS team handled this with DLA-3644-1 (CVE-2023-40619)[4] in buster
(oldoldstable) and of OpenSUSE team also handled both CVEs in
Leap[5][6].
Removing this package in stable will not leave users without them and
we can release it in backports.
I can treat this as a job of ensuring the quality of what is
distributed by Debian.

[1] https://nvd.nist.gov/vuln/detail/CVE-2023-40619
[2] https://nvd.nist.gov/vuln/detail/CVE-2019-10784
[3] 
https://www.debian.org/doc/manuals/developers-reference/pkgs.html#special-case-uploads-to-the-stable-and-oldstable-distributions
[4] https://security-tracker.debian.org/tracker/DLA-3644-1
[5] 
https://build.opensuse.org/projects/home:ecsos:server/packages/phpPgAdmin/repositories/15.5/binaries
[6] 
https://build.opensuse.org/projects/home:ecsos:server/packages/phpPgAdmin/repositories/15.6/binaries

-- 
Cheers,
Leandro Cunha
-BEGIN PGP PUBLIC KEY BLOCK-

mQINBF/gQ8gBEADHVKgoWsUWNGVvR6sMhBPUdBUEH+QALpr1QYXhetBfRwaY0HWN
pKgejHdxKO8H+kIhRMoh89CCKg3hAJ9LmOOTXkX7U5/Cya/zRMKk5zBD3rKIaugh
0XYT15Nz1jwL7TIDG25yPSloDtVgVXTep0ZzKsNYJjb4OAqa88cvUEJEhhqrldlR
gpNbkixEh5ituO8pMShEBWqLs3yt4Hr1VFWnTIm4dl/JLBHpexzubDOw/mKCTpNd
A1JGHTvce1wtJ2fMzCVzhEjd5pyjLZV/o8hVw2/ON/yXvpJuz0lV/hiW0M+cDcas
sKftErtsZpRy3wwXdkBcJt6soYuqfCHwgMfL2iC6mPviE8xWAHMOmhdC3wDskZpb
RcLfH5IMYajJAGRO/GCMcKKbq7WkEOeloivtg64xBlYuJf9aOcHKP/8R3EObiNp7
ubQAJtV3pEGD4mx1mhutFxDHB+CfnxE3dWvxZSV9y1n4UOzkDJ3kDx5Ee0MbRvJD
w6aXKc6dhYREgh7hLDcMFz+3LcBiZDLxI3g+SHe3Bl61vdsnPno+0HhCzvB+fL4S
eoy7Myfiunz9BrB2HPN+wNCT0YgV+Kv8QoDGzBwos5H1vUJSY4t59w6xoXAYUsAm
hjAM8s+rUtG40mcUWePd8kZtgE9IV1eQ+Qt8/SNpSdRnUunmIGl3JjHvEwARAQAB
tClMZWFuZHJvIEN1bmhhIDxsZWFuZHJvY3VuaGEwMTZAZ21haWwuY29tPokCTgQT
AQoAOBYhBLT5oBCvKN3HzFEPK8LZ4zKUW9A8BQJf4EPIAhsDBQsJCAcCBhUKCQgL
AgQWAgMBAh4BAheAAAoJEMLZ4zKUW9A8FjAQAKWYqiLpLUD+DLB+NSy3DI3rf9z3
k0vE7TLaEjdEM5CQWN+j4vBqMnAckdcARvSWPndTjp8K+mtFF4PyfhNbS64z/a7L
F3DdhmX73n7LKFG8Ow9NZwcrkmPwH5WcP7mXTh6R+6/+OSL/K85NB8MLlxQTJOni
julVax9JEZjwBaP2HLCu53Zq9gZcvJlXoAoTHyTxKdp8Mh8V+Qit26E78o9c6SQD
Dq9eyMRG8hYCRfreDjKceRkYHjECySlk+VoI1ssVs07Dqvxg6qSyP4RnW+1+W74C
s0yIyuC/eRJpMAf1PBQEOOrVcTfRfpN+go955t21yIAvT58vqotTM5eaqXYIQn/y
sC4lThZai/ZBZHxl5Mbv42WkkYdjisLQOCALIMBpj5nq4oh2C+kvMupcuBKfERgV
dguU51MzfQktKb6d5y777zYnDaFMQDD2IfiD/C7ln5A9LP/L54ixlA3uRmWx/yAx
/m+Zusws98j4Eq/jw5T54XW655m6lMCTE9WXLJkgxrRcEonHSllbgRSsToEmWq0Z
doxcnpagHdcGQzW+cu2VOGi1da73ZFmrn+ptJgc8cW2suO06IeArOi0TzIg7e65j
Xp2DbJCpFrfzEuBb1u71WvB8V2MkAfJZx/uZJPCA936B4HT8YGPEMzlQRIHI2Y9C
+DloyzlBLTS1EMKuuQINBF/gQ8gBEAC47o9u1Wm9jZ6RC+lfxEDEvVS7MmI5VzSy
q04rFttWwbKix13pc65aDlk47LxWrb84N3Gnf1E/OTsLTXqC7u5JZ7YJkC6CsPbo
D1sQkfCiJCFCTgf7dydEVt8ujS/Uu1kz86ufdRwaMRcvBZAORGdB58LEsLB65WN4
hLRYF7xvcxu6t7FGrIYereaxUAWLA2B/ZnCEdOY94w7s0uaPjHdf4lfHebuZ7T08
iG5ACDvKBjgaFArGfdNYWchXJgbOEg14bGj40/8LuBKQMZASiFSqLPZxoporK9FY
xBw+D080dUWWD5g868TZ3pkM3DXO9bdq22IBKqKOep8CnuKgoDpUvA8dTEY/UDCn
sdOlBUK/Y9zTGVmD/90cO/xkvkV78suqiBnwBSddPzVS0EuiWwrLGu8gaY4EyM/X
7khlbTcMgh4njzUCAE6Tq+TbXSxn86wuOybVY5Y+I99LNdsocI5SIn2nDh2IOi00
4dE/iwO2MatWIOLFBC7pw8Xv4UHZY+WIf3Y/6XjExpllhUkeB6BwZpTr1SXk+cug
q5Dj5i4aGn2LrvQJ57terqUWYyDUBFgXTc4SPOzT5og8CavBgHfrQoFwSnRZ2oyX
xtZhEDI5Pk2j1qTbOhXZ29po4rPNWHMq2HQgM0I+BqQndsoVdkPOFzS2wKkdXjCz
bNYcyanusQARAQABiQI2BBgBCgAgFiEEtPmgEK8o3cfMUQ8rwtnjMpRb0DwFAl/g
Q8gCGwwACgkQwtnjMpRb0Dzh6g//ZjXaWSzKmG5ZS6XJa/ZOokkE2hFOFusWX8Qa
hEwLAnTFEy02dLfV54rKwmu2jHPDKLhE+iYtusvytueZAzVRyQahv0RE4BH8Emqw
gQdBwyJ/L+QhUp/lMdJ6Hh/2ZSZmzU29U24vnY+U+haoB1fLnA3lXgOP59kMLGud
lERR2Vluuc7TcpzvcaRWgrQRU2vSrrBBEp6y07iVKbRM/9yhE/aHJahLbhKh2Dk9
WJvHPnhYJY5yU+Y5vTl3BiW5+EuzMBdPUawOWKhqCq9dswn0GL1g/vlt/bdU/6DO
jECQ6fssTAtDjRClXySsS3X0mh8y8qlGvMPB4anfvOy4+4nUV6IESdJftKn2SMGd
CA3MaQ+S7frWn5v7GIWSC9vumCsiu1JTOugLmbVmu5m5nFsyllavm/k9LtOtswuF
fHM/SlXLFuGBWU6XceqaM2dpP8i5jGz0vIGMhqoFNgXWGO1NhwR1rmeU1CMpnM5e

Bug#1065340: marked as done (src:guidata: unsatisfied build dependency in testing: python3-sip)

[Debian Bug Tracking System]

Your message dated Wed, 06 Mar 2024 09:34:51 +
with message-id 
and subject line Bug#1065340: fixed in guidata 3.3.0+dfsg1-1
has caused the Debian Bug report #1065340,
regarding src:guidata: unsatisfied build dependency in testing: python3-sip
to be marked as done.

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

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


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

Source: guidata
Version: 3.0.4+dfsg1-1
Severity: serious
Tags: sid trixie
User: debian...@lists.debian.org
Usertags: edos-uninstallable
Control: block -1 by 1060742

Dear maintainer(s),

Dose [1] is reporting a build issue with your package, it's missing a
build dependency. Obviously your build dependencies shouldn't be
removed from testing, but unfortunately there are multiple scenarios
where that can happen nevertheless. To uphold our social contract,
Debian requires that packages can be rebuild from source in the suite
we are shipping them, so currently this is a serious issue with your
package in testing.

Bug #1060742 was filed earlier to warn you about the issue; python3-sip 
has now been removed from testing due to its RC bug.


Can you please investigate the situation and figure out how to resolve
it?

Paul

Note: this bug report was sent after some quick manual checks using a
template. Please reach out to me if you believe I made a mistake in my
process.

[1] https://qa.debian.org/dose/debcheck/src_testing_main/latest/amd64.html



OpenPGP_signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: guidata
Source-Version: 3.3.0+dfsg1-1
Done: Picca Frédéric-Emmanuel 

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

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

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

Debian distribution maintenance software
pp.
Picca Frédéric-Emmanuel  (supplier of updated guidata package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 06 Mar 2024 10:18:34 +0100
Source: guidata
Architecture: source
Version: 3.3.0+dfsg1-1
Distribution: unstable
Urgency: low
Maintainer: Debian Science Maintainers 

Changed-By: Picca Frédéric-Emmanuel 
Closes: 1060742 1065340
Changes:
 guidata (3.3.0+dfsg1-1) unstable; urgency=low
 .
   * New upstream release.
   * Set upstream metadata fields:
 Bug-Database, Bug-Submit, Repository, Repository-Browse.
   * d/control:
 - Remove useless B-D python3-sip
 - Added B-D python3-myst-parser
   * Bug fix: "unsatisfied build dependency in testing: python3-sip",
 thanks to Paul Gevers (Closes: #1065340).
   * Bug fix: "Please remove python3-sip from Build-Depends", thanks to
 Dmitry Shachnev (Closes: #1060742).
Checksums-Sha1:
 36933a21d778ba2519ce98bd630311cad2d32c74 2713 guidata_3.3.0+dfsg1-1.dsc
 9abf9bca218a01fc3815bf27a0652eff8ebcde7a 690865 guidata_3.3.0+dfsg1.orig.tar.gz
 b4b491b88861f45434416e804199c63878eed4cc 6560 
guidata_3.3.0+dfsg1-1.debian.tar.xz
Checksums-Sha256:
 630d20a99b416f4d9fd0b78286f3b0b7f91361d5b7eb3b10b28c717e2507f9bf 2713 
guidata_3.3.0+dfsg1-1.dsc
 8e5ce64ba5fae68cba118da80079bcc4f79e794c7dc744efc0155edb84737449 690865 
guidata_3.3.0+dfsg1.orig.tar.gz
 0832d595f5f4d7a1c047410606bc4cdc834bbb7f2aa680001a3fd2c994bb122d 6560 
guidata_3.3.0+dfsg1-1.debian.tar.xz
Files:
 bf14a523bd133c15e1684fd5d4647abc 2713 science optional 
guidata_3.3.0+dfsg1-1.dsc
 50f7a1a91db3136e8fcf848b721ebee3 690865 science optional 
guidata_3.3.0+dfsg1.orig.tar.gz
 4083b3ceccd37b5885aa02715c24dca4 6560 science optional 
guidata_3.3.0+dfsg1-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEE2bRTt5m4gw2UXmoKW/VOXhK5ALsFAmXoNdcRHHBpY2NhQGRl
Ymlhbi5vcmcACgkQW/VOXhK5ALvkKA//aah/2ZWwV6sv8DZKCGoaModXsKiaYY1R
XuKWRF1wlnf+5refR8uIHVq4PNgHypMQsit65TD5YgrII1HyVJIT43R1svglkKLW
6HZBmX4PBLhY55hthlevrGcntA1tG2oGrxKcRtHosV3nULwOj9d8K9fMkI0ng1Ih
G8IaGnq5TOTQ7JfjPsgVM1n7nfZrV41BqaxBS3rE+wz01g+v4VS4aEolhzFYBfQc
FKTbeSoHnNmJ6iw5TGkoGUjV7LLRyBfAoJV9kkvXvgG3xdeP395UvFfprkT15Xi/
baom3oyPVNveI1W6uDwYUpAtXA6yQZcTTxQmq8j+JrUTk/wc3OBKBuNDPL/20ZJC

Bug#1065395: [Pkg-opencl-devel] Bug#1065395: spirv-llvm-translator-14: autopkgtest on s390x uses huge amount of disk space

[Andreas Beckmann]

On 06/03/2024 06.20, Paul Gevers wrote:

Unfortunately the test still takes upto 33 GB at least (see below).


Do you have the log from running that autopkgtest?
I have no idea what's happening here. At least the buildd build only 
used 500 MB.


By the way, I just noticed this in the -14 log (judging from the name of 
the test I think that's intentional, but just checking (installing from 
the -16 package instead of the -14 one):
Get:2 http://deb.debian.org/debian unstable/main s390x spirv-headers all 
1.6.1+1.3.275.0-1 [118 kB]


spirv-headers is an independent package, the version is not 
corresponding to an llvm version (1.6.1 has nothing to do with llvm 16). 
But since it evolves independently, it sometimes renames bits (e.g. if 
internal vendor extensions get finalized and upstreamed), breaking its 
consumers (but the lvm_release_* branches of llvm-spirv-translator are 
usually quickly adjusted)


Andreas

Bug#1053004: CVE-2019-10784 and CVE-2023-40619

[Christoph Berg]

Re: Leandro Cunha
> The
> next job would be to make it available through backports and I would
> choose to remove this package from stable. But I would only leave
> bookworm backports due to other bugs found (this CVEs too) and fixed
> in 7.14.7.
> I have to search about the status of backports to oldstable. But I'm
> also studying the possibility of working with patches for these two
> versions.

Why would you want to remove it from stable? In closed environments,
CVEs are often not a problem.

Christoph

Processed: severity of 1058075 is serious

[Debian Bug Tracking System]

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

> severity 1058075 serious
Bug #1058075 [src:lockdown] lockdown: RM for trixie?
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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