date:20240303


Package: linux-libc-dev
Version: 6.7.7-1
Severity: serious
Tags: sid trixie

linux-libc-dev claims to provide linux-libc-dev-ARCH-cross, but it 
doesn't do that completely


Provides: linux-libc-dev-amd64-cross (= 6.7.7-1), ...

However the links in /usr/DEB_HOST_GNU_TYPE/include are missing.

Please stop providing the cross-packages, you don't even need a breaks, 
because the current cross packages continue to work.


Once that is done, I'll reduce the cross packages to some symlinks.

Bug#1064950: AW: Bug#1064950: apache2: (Legacy?) "Depends: apache2-data (= ${source:Version})," in debian/control breaks binNMU builds.

2024-03-03 Thread Sebastian Ramacher

On 2024-03-04 06:19:58 +, Warlich, Christof wrote:
> Sebastian Ramacher wrote:
> > This is wrong. apache2-data is an Architecture: all package,
> > but apache2 is Architecture: any. So using ${source:Version}
> > here is correct. Note that Debian does not currently support
> > binNMUs for Architecture: all packages, so apache2-data will
> > never have a +bX version.
> 
> Thanks for that clarification.
> 
> This is somewhat confusing for someone not doing package builds as a daily 
> profession: If just doing a "dpkg-buildpackage -us -uc" on the apache2 
> sources _with_ the +bX extension, the apache2-data binary package _does_ get 
> the +bX extension as well, at least with my build, causing the issue that I 
> described initially.

For binNMUs you'll need to pass "-B" at least, but see below.

> Thus, as much as I think I've leaned so far, binNMU builds on source packages 
> that also produce Architekture: all binary packages must always be built 
> separately from sources without the +bX extension for the Architecture: all 
> binary packages, whereras the architecture-dependent binary packages may be 
> built from a source package with a +bX extension, right?

Not exactly. The source packages are not changed for binNMUs. This is
handled via sbuild's --binNMU-* options to set the changelog and the
version. Specifically, these options imply that Arch: all binaries are
not built.

> If this assumption is true, then why is the Debian build system (i.e. 
> dpkg-buildpackage) not smart enough to simply ignore an existing +bX 
> extension for Architecture: all binary packages? IMHO, this would simplify 
> matters, as it would have avoided the pitfall that I stumbled into altogether.

binNMUs are handled a layer above. sbuild will pass the correct options
to dpkg-buildpackage to build binNMUs. If you are interested in having
binNMU builds for your own infrastructure, you'll probably need to take
a look at the sbuild source to see how it is implemented.

Cheers
-- 
Sebastian Ramacher

Bug#1060955: marked as done (txtorcon: FTBFS: make[1]: *** [debian/rules:28: override_dh_auto_test] Error 1)

Your message dated Mon, 04 Mar 2024 07:39:59 +
with message-id 
and subject line Bug#1060955: fixed in txtorcon 23.11.0-1
has caused the Debian Bug report #1060955,
regarding txtorcon: FTBFS: make[1]: *** [debian/rules:28: 
override_dh_auto_test] Error 1
to be marked as done.

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

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


-- 
1060955: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060955
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: txtorcon
Version: 22.0.0-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240115 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 '/<>'
> PYTHONPATH=. trial3 --reporter=text test
> ./<>/txtorcon/onion.py:156:
>  UserWarning: Onions service directory 
> (test.test_controller/FilesystemOnionFactoryTests/test_happy_path/amgjrrzv/temp)
>  is relative and has been resolved to 
> '/<>/_trial_temp/test.test_controller/FilesystemOnionFactoryTests/test_happy_path/amgjrrzv/temp'
> ../<>/txtorcon/onion.py:156:
>  UserWarning: Onions service directory 
> (test.test_endpoints/EndpointTests/test_basic_auth/n43of8m3/temp) is relative 
> and has been resolved to 
> '/<>/_trial_temp/test.test_endpoints/EndpointTests/test_basic_auth/n43of8m3/temp'
> ./<>/txtorcon/onion.py:156: UserWarning: Onions service 
> directory 
> (test.test_endpoints/EndpointTests/test_explit_dir_not_readable_ver/damtiry0/temp)
>  is relative and has been resolved to 
> '/<>/_trial_temp/test.test_endpoints/EndpointTests/test_explit_dir_not_readable_ver/damtiry0/temp'
> ../<>/txtorcon/onion.py:156: UserWarning: Onions service 
> directory 
> (test.test_endpoints/EndpointTests/test_multiple_disk/qq7x3h0_/temp) is 
> relative and has been resolved to 
> '/<>/_trial_temp/test.test_endpoints/EndpointTests/test_multiple_disk/qq7x3h0_/temp'
> ...E../<>/txtorcon/onion.py:156: 
> UserWarning: Onions service directory 
> (test.test_endpoints/EndpointTests/test_stealth_auth/gf1pfz07/temp) is 
> relative and has been resolved to 
> '/<>/_trial_temp/test.test_endpoints/EndpointTests/test_stealth_auth/gf1pfz07/temp'
> .../<>/txtorcon/onion.py:156: UserWarning: Onions service 
> directory 
> (test.test_endpoints/EndpointTests/test_system_tor_explit_dir_not_e/vvz3zjvn/temp)
>  is relative and has been resolved to 
> '/<>/_trial_temp/test.test_endpoints/EndpointTests/test_system_tor_explit_dir_not_e/vvz3zjvn/temp'
> ./<>/txtorcon/onion.py:156: UserWarning: Onions service 
> directory 
> (test.test_endpoints/EndpointTests/test_system_tor_explit_dir_not_r/b5bxfnc2/temp)
>  is relative and has been resolved to 
> '/<>/_trial_temp/test.test_endpoints/EndpointTests/test_system_tor_explit_dir_not_r/b5bxfnc2/temp'
> ./<>/txtorcon/onion.py:156: UserWarning: Onions service 
> directory 
> (test.test_endpoints/EndpointTests/test_system_tor_explit_dir_not_r/6uvuwkdg/temp)
>  is relative and has been resolved to 
> '/<>/_trial_temp/test.test_endpoints/EndpointTests/test_system_tor_explit_dir_not_r/6uvuwkdg/temp'
> ../<>/txtorcon/onion.py:156:
>  UserWarning: Onions service directory 
> (test.test_onion/OnionServiceTest/test_dir_ioerror/aisr5ktd/temp) is relative 
> and has been resolved to 
> '/<>/_trial_temp/test.test_onion/OnionServiceTest/test_dir_ioerror/aisr5ktd/temp'
> ./<>/txtorcon/onion.py:156: UserWarning: Onions service 
> directory 
> (test.test_onion/OnionServiceTest/test_dir_ioerror_v3/os3oa97g/temp) is 
> relative and has been resolved to 
> '/<>/_trial_temp/test.test_onion/OnionServiceTest/test_dir_ioerror_v3/os3oa97g/temp'
> ./<>/txtorcon/onion.py:156: 
> UserWarning: Onions service directory 
> (test.test_onion/OnionServiceTest/test_old_tor_version/ub6yllsp/temp) is 
> relative and has been resolved to 
> '/<>/_trial_temp/test.test_onion/OnionServiceTest/test_old_tor_version/ub6yllsp/temp'
> ./<>/txtorcon/onion.py:156: UserWarning: Onions service 
> directory 
> (test.test_onion/OnionServiceTest/test_prop224_private_key/t_q99f2u/temp) is 
> relative and has been resolved to 
> '/<>/_trial_temp/test.test_onion/OnionServiceTest/test_prop224_private_key/t_q99f2u/temp'
> ./<>/txtorcon/onion.py:156: UserWarning: Onions service 
> directory (test.test_onion/OnionServiceTest/test_set_dir/b5m_yqdh/temp) is 
> relative and has been

Processed: src:pytables: fails to migrate to testing for too long: old s390x binary left around

Processing control commands:

> close -1 3.9.2-1
Bug #1065412 [src:pytables] src:pytables: fails to migrate to testing for too 
long: old s390x binary left around
Marked as fixed in versions pytables/3.9.2-1.
Bug #1065412 [src:pytables] src:pytables: fails to migrate to testing for too 
long: old s390x binary left around
Marked Bug as done
> block -1 by 1061661
Bug #1065412 {Done: Paul Gevers } [src:pytables] 
src:pytables: fails to migrate to testing for too long: old s390x binary left 
around
1065412 was not blocked by any bugs.
1065412 was not blocking any bugs.
Added blocking bug(s) of 1065412: 1061661

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

Bug#1065412: src:pytables: fails to migrate to testing for too long: old s390x binary left around

2024-03-03 Thread Paul Gevers


Source: pytables
Version: 3.7.0-10
Severity: serious
Control: close -1 3.9.2-1
Tags: sid trixie
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 1061661

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing 
and unstable for more than 30 days as having a Release Critical bug in 
testing [1]. Your package src:pytables has been trying to migrate for 64 
days [2]. Hence, I am filing this bug. As suggested in bug 1061661, the 
s390x binary needs to be removed by ftp-master. Somebody needs to 
request it.


If a package is out of sync between unstable and testing for a longer 
period, this usually means that bugs in the package in testing cannot be 
fixed via unstable. Additionally, blocked packages can have impact on 
other packages, which makes preparing for the release more difficult. 
Finally, it often exposes issues with the package and/or
its (reverse-)dependencies. We expect maintainers to fix issues that 
hamper the migration of their package in a timely manner.


This bug will trigger auto-removal when appropriate. As with all new 
bugs, there will be at least 30 days before the package is auto-removed.


I have immediately closed this bug with the version in unstable, so if 
that version or a later version migrates, this bug will no longer affect 
testing. I have also tagged this bug to only affect sid and trixie, so 
it doesn't affect (old-)stable.


If you believe your package is unable to migrate to testing due to 
issues beyond your control, don't hesitate to contact the Release Team.


Paul

[1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html
[2] https://qa.debian.org/excuses.php?package=pytables



OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1064950: AW: Bug#1064950: apache2: (Legacy?) "Depends: apache2-data (= ${source:Version})," in debian/control breaks binNMU builds.

2024-03-03 Thread Warlich, Christof

Sebastian Ramacher wrote:
> This is wrong. apache2-data is an Architecture: all package,
> but apache2 is Architecture: any. So using ${source:Version}
> here is correct. Note that Debian does not currently support
> binNMUs for Architecture: all packages, so apache2-data will
> never have a +bX version.

Thanks for that clarification.

This is somewhat confusing for someone not doing package builds as a daily 
profession: If just doing a "dpkg-buildpackage -us -uc" on the apache2 sources 
_with_ the +bX extension, the apache2-data binary package _does_ get the +bX 
extension as well, at least with my build, causing the issue that I described 
initially.

Thus, as much as I think I've leaned so far, binNMU builds on source packages 
that also produce Architekture: all binary packages must always be built 
separately from sources without the +bX extension for the Architecture: all 
binary packages, whereras the architecture-dependent binary packages may be 
built from a source package with a +bX extension, right?

If this assumption is true, then why is the Debian build system (i.e. 
dpkg-buildpackage) not smart enough to simply ignore an existing +bX extension 
for Architecture: all binary packages? IMHO, this would simplify matters, as it 
would have avoided the pitfall that I stumbled into altogether.

Please note that I my main goal is to better understand how to do it right for 
future builds.

Bug#1061025: Additional information

2024-03-03 Thread Vladimir Petko

Dear Maintainers,

httpcomponents-client contains an implicit dependency on slf4j-java.

Last time it was build successfully against libcommons-log-java 1.2[1]

Support for slf4j was added after its release[2][3]

Debian and Ubuntu have slf4j 1.7.32-1 which calls
org.apache.commons.logging.LogFactory.getLog[4].

This causes exception in httpclient-cache tests[5]:

java.lang.IllegalStateException: Recursive update
 at 
java.base/java.util.concurrent.ConcurrentHashMap.computeIfAbsent(ConcurrentHashMap.java:1763)

Best Regards,
 Vladimir.

[1] 
https://buildd.debian.org/status/fetch.php?pkg=httpcomponents-client&arch=all&ver=4.5.14-1&stamp=1670330442&raw=0
[2] https://github.com/apache/commons-logging/pull/177
[3] 
https://github.com/apache/commons-logging/commits/master/src/main/java/org/apache/commons/logging/impl/Slf4jLogFactory.java
[4] 
https://github.com/qos-ch/slf4j/blob/e9ee55cca93c2bf26f14482a9bdf961c750d2a56/slf4j-jcl/src/main/java/org/slf4j/impl/JCLLoggerFactory.java#L77
[5] 
https://launchpad.net/~vpa1977/+archive/ubuntu/october-21/+build/27798162/+files/buildlog_ubuntu-noble-amd64.httpcomponents-client_4.5.14-1_BUILDING.txt.gz

Bug#1062696: libverto: NMU diff for 64-bit time_t transition

An overlooked hard-coded dependency in debian/control has made libverto
uninstallable.  Please find the debdiff for an updated NMU attached.

On Fri, Feb 02, 2024 at 06:18:40PM +, Steve Langasek wrote:
> Source: libverto
> Version: 0.3.1-1
> Severity: serious
> Tags: patch pending sid trixie
> Justification: library ABI skew on upgrade
> User: debian-...@lists.debian.org
> Usertags: time-t
> 
> NOTICE: these changes must not be uploaded to unstable yet!
> 
> Dear maintainer,
> 
> As part of the 64-bit time_t transition required to support 32-bit
> architectures in 2038 and beyond
> (https://wiki.debian.org/ReleaseGoals/64bit-time), we have identified
> libverto as a source package shipping runtime libraries whose ABI
> either is affected by the change in size of time_t, or could not be
> analyzed via abi-compliance-checker (and therefore to be on the safe
> side we assume is affected).
> 
> To ensure that inconsistent combinations of libraries with their
> reverse-dependencies are never installed together, it is necessary to
> have a library transition, which is most easily done by renaming the
> runtime library package.
> 
> Since turning on 64-bit time_t is being handled centrally through a change
> to the default dpkg-buildflags (https://bugs.debian.org/1037136), it is
> important that libraries affected by this ABI change all be uploaded close
> together in time.  Therefore I have prepared a 0-day NMU for libverto
> which will initially be uploaded to experimental if possible, then to
> unstable after packages have cleared binary NEW.
> 
> Please find the patch for this NMU attached.
> 
> 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.
> 
> 
> 
> -- System Information:
> Debian Release: trixie/sid
>   APT prefers unstable
>   APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 
> 'experimental')
> Architecture: amd64 (x86_64)
> 
> Kernel: Linux 6.5.0-14-generic (SMP w/12 CPU threads; PREEMPT)
> Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
> Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
> Shell: /bin/sh linked to /usr/bin/dash
> Init: systemd (via /run/systemd/system)

> diff -Nru libverto-0.3.1/debian/changelog libverto-0.3.1/debian/changelog
> --- libverto-0.3.1/debian/changelog   2020-06-08 13:37:48.0 +
> +++ libverto-0.3.1/debian/changelog   2024-02-02 18:18:10.0 +
> @@ -1,3 +1,10 @@
> +libverto (0.3.1-1.1) experimental; urgency=medium
> +
> +  * Non-maintainer upload.
> +  * Rename libraries for 64-bit time_t transition.
> +
> + -- Steve Langasek   Fri, 02 Feb 2024 18:18:10 +
> +
>  libverto (0.3.1-1) unstable; urgency=medium
>  
>[ Debian Janitor ]
> diff -Nru libverto-0.3.1/debian/control libverto-0.3.1/debian/control
> --- libverto-0.3.1/debian/control 2020-06-08 13:34:34.0 +
> +++ libverto-0.3.1/debian/control 2024-02-02 18:18:10.0 +
> @@ -12,7 +12,7 @@
>  Package: libverto-dev
>  Section: libdevel
>  Architecture: any
> -Depends: ${misc:Depends}, libverto1 (= ${binary:Version}), libverto-glib1 (= 
> ${binary:Version}), libverto-libev1 (= ${binary:Version})
> +Depends: ${misc:Depends}, libverto1t64 (= ${binary:Version}), 
> libverto-glib1t64 (= ${binary:Version}), libverto-libev1t64 (= 
> ${binary:Version})
>  Description: Event loop abstraction for Libraries - Development
>   Libverto exists to isolate libraries from the particular event loop
>   chosen by an application. Libverto provides an asynchronous
> @@ -22,7 +22,10 @@
>   .
>   This package includes development libraries.
>  
> -Package: libverto1
> +Package: libverto1t64
> +Provides: ${t64:Provides}
> +Replaces: libverto1
> +Breaks: libverto1 (<< ${source:Version})
>  Section: libs
>  Architecture: any
>  PRe-Depends: ${misc:Pre-Depends}
> @@ -37,7 +40,10 @@
>   .
>   This package includes the main runtime library.
>  
> -Package: libverto-libev1
> +Package: libverto-libev1t64
> +Provides: ${t64:Provides}
> +Replaces: libverto-libev1
> +Breaks: libverto-libev1 (<< ${source:Version})
>  Section: libs
>  Architecture: any
>  PRe-Depends: ${misc:Pre-Depends}
> @@ -52,7 +58,10 @@
>   .
>   This package includes support for the libev event loop.
>  
> -Package: libverto-glib1
> +Package: libverto-glib1t64
> +Provides: ${t64:Provides}
> +Replaces: libverto-glib1
> +Breaks: libverto-glib1 (<< ${source:Version})
>  Section: libs
>  Architecture: any
>  PRe-Depends: ${misc:Pre-Depends}
> diff -Nru libverto-0.3.1/debian/libverto-glib1.install 
> libverto-0.3.1/debian/libverto-glib1.install
> --- libverto-0.3.1/debian/libverto-glib1.install  2014-05-29 
> 00:36:01.0 +
> +++ libverto-0.3.1/debian

Bug#1063170: nettle: NMU diff for 64-bit time_t transition

The previous NMU overlooked a hard-coded reference to the old library name
in debian/rules.  Please find an amended NMU patch 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 nettle-3.9.1/debian/changelog nettle-3.9.1/debian/changelog
--- nettle-3.9.1/debian/changelog   2023-07-27 14:31:36.0 +
+++ nettle-3.9.1/debian/changelog   2024-03-04 01:24:40.0 +
@@ -1,3 +1,17 @@
+nettle (3.9.1-2.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix documentation link target to fix nettle-bin uninstallability.
+
+ -- Steve Langasek   Mon, 04 Mar 2024 01:24:40 +
+
+nettle (3.9.1-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Rename libraries for 64-bit time_t transition.  Closes: #1063170
+
+ -- Benjamin Drung   Wed, 28 Feb 2024 22:51:33 +
+
 nettle (3.9.1-2) unstable; urgency=low
 
   * Upload to unstable.
diff -Nru nettle-3.9.1/debian/control nettle-3.9.1/debian/control
--- nettle-3.9.1/debian/control 2023-07-27 14:31:36.0 +
+++ nettle-3.9.1/debian/control 2024-02-28 22:51:33.0 +
@@ -2,7 +2,7 @@
 Section: libs
 Priority: optional
 Maintainer: Magnus Holmgren 
-Build-Depends: dpkg-dev (>= 1.15.7), debhelper-compat (= 12),
+Build-Depends: dpkg-dev (>= 1.22.5), dpkg-dev (>= 1.15.7), debhelper-compat (= 
12),
  libgmp-dev, m4, texinfo
 Standards-Version: 4.6.2
 Vcs-Git: https://salsa.debian.org/holmgren/nettle.git
@@ -10,7 +10,10 @@
 Homepage: http://www.lysator.liu.se/~nisse/nettle/
 Rules-Requires-Root: no
 
-Package: libnettle8
+Package: libnettle8t64
+Provides: ${t64:Provides}
+Replaces: libnettle8
+Breaks: libnettle8 (<< ${source:Version})
 Architecture: any
 Multi-Arch: same
 Pre-Depends: ${misc:Pre-Depends}
@@ -32,7 +35,10 @@
  algorithms. To avoid having this package depend on libgmp, the
  asymmetric cryptos reside in a separate library, libhogweed.
 
-Package: libhogweed6
+Package: libhogweed6t64
+Provides: ${t64:Provides}
+Replaces: libhogweed6
+Breaks: libhogweed6 (<< ${source:Version})
 Architecture: any
 Multi-Arch: same
 Pre-Depends: ${misc:Pre-Depends}
@@ -58,7 +64,7 @@
 Section: libdevel
 Architecture: any
 Multi-Arch: same
-Depends: libnettle8 (= ${binary:Version}), libhogweed6 (= ${binary:Version}),
+Depends: libnettle8t64 (= ${binary:Version}), libhogweed6t64 (= 
${binary:Version}),
  libgmp-dev, ${misc:Depends}
 Replaces: libnettle-dev
 Conflicts: libnettle-dev
diff -Nru nettle-3.9.1/debian/libhogweed6.install 
nettle-3.9.1/debian/libhogweed6.install
--- nettle-3.9.1/debian/libhogweed6.install 2023-07-27 14:31:36.0 
+
+++ nettle-3.9.1/debian/libhogweed6.install 1970-01-01 00:00:00.0 
+
@@ -1 +0,0 @@
-usr/lib/*/libhogweed*.so.*
diff -Nru nettle-3.9.1/debian/libhogweed6.symbols 
nettle-3.9.1/debian/libhogweed6.symbols
--- nettle-3.9.1/debian/libhogweed6.symbols 2023-07-27 14:31:36.0 
+
+++ nettle-3.9.1/debian/libhogweed6.symbols 1970-01-01 00:00:00.0 
+
@@ -1,292 +0,0 @@
-libhogweed.so.6 libhogweed6 #MINVER#
-* Build-Depends-Package: nettle-dev
- HOGWEED_6@HOGWEED_6 0
- HOGWEED_INTERNAL_6_8@HOGWEED_INTERNAL_6_8 3.9.1~
- (optional)_nettle_cnd_copy@HOGWEED_INTERNAL_6_8 3.9.1~
- (optional)_nettle_curve25519@HOGWEED_INTERNAL_6_8 3.9.1~
- (optional)_nettle_curve25519_eh_to_x@HOGWEED_INTERNAL_6_8 3.9.1~
- (optional)_nettle_curve448@HOGWEED_INTERNAL_6_8 3.9.1~
- (optional)_nettle_curve448_eh_to_x@HOGWEED_INTERNAL_6_8 3.9.1~
- (optional)_nettle_dsa_hash@HOGWEED_INTERNAL_6_8 3.9.1~
- (optional)_nettle_ecc_a_to_j@HOGWEED_INTERNAL_6_8 3.9.1~
- (optional)_nettle_ecc_add_eh@HOGWEED_INTERNAL_6_8 3.9.1~
- (optional)_nettle_ecc_add_ehh@HOGWEED_INTERNAL_6_8 3.9.1~
- (optional)_nettle_ecc_add_jja@HOGWEED_INTERNAL_6_8 3.9.1~
- (optional)_nettle_ecc_add_jjj@HOGWEED_INTERNAL_6_8 3.9.1~
- (optional)_nettle_ecc_add_th@HOGWEED_INTERNAL_6_8 3.9.1~
- (optional)_nettle_ecc_add_thh@HOGWEED_INTERNAL_6_8 3.9.1~
- (optional)_nettle_ecc_curve25519_modp@HOGWEED_INTERNAL_6_8 3.9.1~
- (optional)_nettle_ecc_curve448_modp@HOGWEED_INTERNAL_6_8 3.9.1~
- (optional)_nettle_ecc_dup_eh@HOGWEED_INTERNAL_6_8 3.9.1~
- (optional)_nettle_ecc_dup_jj@HOGWEED_INTERNAL_6_8 3.9.1~
- (optional)_nettle_ecc_dup_th@HOGWEED_INTERNAL_6_8 3.9.1~
- (optional)_nettle_ecc_eh_to_a@HOGWEED_INTERNAL_6_8 3.9.1~
- (optional)_nettle_ecc_hash@HOGWEED_INTERNAL_6_8 3.9.1~
- (optional)_nettle_ecc_j_to_a@HOGWEED_INTERNAL_6_8 3.9.1~
- (optional)_nettle_ecc_mod@HOGWEED_INTERNAL_6_8 3.9.1~
- (optional)_nettle_ecc_mod_add@HOGWEED_INTERNAL_6_8 3.9.1~
- (optional)_nettle_ecc_mod_addmul_1@HOGWEED_INTERNAL_6_8 3.9.1~
- (optional)_nettle_ecc_mod_equal_p@HOGWEED_INTERNAL_6_8 3.9.1~
- (optional)_nettle_ecc_mod_inv@HOGWEED_INTERNAL_6_8 3.9.1~
- (optio

Bug#1064193: marked as done (lua-cqueues: identified for time_t transition but no ABI in shlibs)

Your message dated Sun, 3 Mar 2024 20:06:09 -0500
with message-id 
<2uvfgbjsjsopyqpqubmqqimmfqf5lu3iauu242xlexeavdryb6@wnjek6z3r2ik>
and subject line Re: Bug#1064193: lua-cqueues: identified for time_t transition 
but no ABI in shlibs
has caused the Debian Bug report #1064193,
regarding lua-cqueues: identified for time_t transition but no ABI in shlibs
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.)

-- 
1064193: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064193
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: lua-cqueues
Version: 3.1.0-1
Severity: serious
User: debian-...@lists.debian.org
Usertags: time-t

Dear maintainers,

Analysis of the archive for the 64-bit time_t transition[0][1] identifies
lua-cqueues as an affected package, on the basis that the headers could not
be compiled and analyzed out of the box using abi-compliance-checker[2], so
we have to assume it's affected.

However, lua-cqueue's shlibs file declares a dependency on a library package
name that contains no ABI information:

$ cat DEBIAN/shlibs
liblua5.1-cqueues 0 lua-cqueues (>= 20200726)
liblua5.2-cqueues 0 lua-cqueues (>= 20200726)
liblua5.3-cqueues 0 lua-cqueues (>= 20200726)
liblua5.4-cqueues 0 lua-cqueues (>= 20200726)
$

It is therefore not obvious that we should rename the package to
'lua-cqueuest64' as part of this transition.

Looking at the archive, there is a package built from the separate lua-http
source package that depends on this library.

Since there is no self-evident thing to do with the library package name
here, we will not be handling this package as part of the mass NMUs. 
Instead I am filing a serious bug because partial upgrades from bookworm to
trixie on 32-bit architectures will result in ABI skew and may result in
broken behavior.

Thanks,
-- 
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

[0] https://wiki.debian.org/ReleaseGoals/64bit-time
[1] https://lists.debian.org/debian-devel/2024/01/msg00041.html
[2] 
https://adrien.dcln.fr/misc/armhf-time_t/2024-02-16T21%3A19%3A00/logs/lua-cqueues-dev/base/log.txt

signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
On Sun, Feb 18, 2024 at 12:10:48AM -0800, Steve Langasek wrote:
> Analysis of the archive for the 64-bit time_t transition[0][1] identifies
> lua-cqueues as an affected package, on the basis that the headers could not
> be compiled and analyzed out of the box using abi-compliance-checker[2], so
> we have to assume it's affected.

It was the latter.  After fixing the path to compat-5.3.h, includuing
lua.h from the proper lua version, and working around a-c-c's insistence
on using the C++ backend, the analysis shows that lua-cqueues is not
affected by the transition. Closing the bug.

Cheers,
-- 
James
GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7  2D23 DFE6 91AE 331B A3DB--- End Message ---

Bug#1065217: marked as done (libpetsc-complex3.19-dev fails to install)

Your message dated Mon, 04 Mar 2024 00:37:14 +
with message-id 
and subject line Bug#1065217: fixed in petsc 3.19.6+dfsg1-2.2
has caused the Debian Bug report #1065217,
regarding libpetsc-complex3.19-dev fails to install
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.)


-- 
1065217: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065217
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libpetsc-complex3.19-dev
Version: 3.19.6+dfsg1-2.1
Severity: serious
Tags: ftbfs
X-Debbugs-Cc: Benjamin Drung , Steve Langasek 

Control: affects -1 src:slepc

https://buildd.debian.org/status/fetch.php?pkg=slepc&arch=amd64&ver=3.19.2%2Bdfsg1-2.1&stamp=1709337662&raw=0

...
Setting up libpetsc-complex3.19-dev:amd64 (3.19.6+dfsg1-2.1) ...
update-alternatives: error: no alternatives for petsc
update-alternatives: error: alternative path 
/usr/lib/petscdir/petsc3.19t64/x86_64-linux-gnu-complex doesn't exist
dpkg: error processing package libpetsc-complex3.19-dev:amd64 (--configure):
 installed libpetsc-complex3.19-dev:amd64 package post-installation script 
subprocess returned error exit status 2
...
--- End Message ---
--- Begin Message ---
Source: petsc
Source-Version: 3.19.6+dfsg1-2.2
Done: Steve Langasek 

We believe that the bug you reported is fixed in the latest version of
petsc, 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 petsc package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 03 Mar 2024 21:40:10 +
Source: petsc
Architecture: source
Version: 3.19.6+dfsg1-2.2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Steve Langasek 
Closes: 1065217
Changes:
 petsc (3.19.6+dfsg1-2.2) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Fix extraneous X-Time64-Compat declarations.
   * Fix substitution of soname in maintainer scripts.  Closes: #1065217.
Checksums-Sha1:
 72e38ef19f68bc1faaec4299fe4c51396d425f7e 4659 petsc_3.19.6+dfsg1-2.2.dsc
 53e3eabe1bc84ac715e3558df209f7208832b584 112904 
petsc_3.19.6+dfsg1-2.2.debian.tar.xz
 19cba33ce58619be18991c70c659ae2136e21f32 13974 
petsc_3.19.6+dfsg1-2.2_source.buildinfo
Checksums-Sha256:
 d08f67b2ca4499e1ef5f3e6a6f9a99ae8bac77504e966af2d047b1299906cca9 4659 
petsc_3.19.6+dfsg1-2.2.dsc
 33944ec13d7301e71cddf343fbc5a3f4f79ccc4515b89db1b56f2f50e2da77af 112904 
petsc_3.19.6+dfsg1-2.2.debian.tar.xz
 bf2955117081460051470f756fe9ac8ca6c08e14336bc0ebf3389625d8b41427 13974 
petsc_3.19.6+dfsg1-2.2_source.buildinfo
Files:
 50ffd06d88fc86736be2e0cae31f1edd 4659 devel optional petsc_3.19.6+dfsg1-2.2.dsc
 f0ccca4ac8a0463bd623c07431f5fa6c 112904 devel optional 
petsc_3.19.6+dfsg1-2.2.debian.tar.xz
 eb108277a1ace7eb3fde3a1e20fddf33 13974 devel optional 
petsc_3.19.6+dfsg1-2.2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJGBAEBCgAwFiEErEg/aN5yj0PyIC/KVo0w8yGyEz0FAmXk7lsSHHZvcmxvbkBk
ZWJpYW4ub3JnAAoJEFaNMPMhshM9zUoQAMk9N30dypH0X7AEFcW91OJuTh7K1/MK
8vEEyEwbymycvK2NryIlaWcKujPasS7IbGUksLXiFQZqA8lZ8hj5+CiZs5cEZWb1
wGD4RTUY+iPJKIhELnPjwK3wBGdnoMIU2UIPPNvLWvExgjx2yqvpA+fZQVOaRHTi
0FmURcx87h/HMTPi+vi4iM3c1AETsJf66OUumogEg+RnL76TibGRo02ig9EXlk3Z
0h7F8GQ2WAFBmzcCRsRTC3eeuygAIqiNIDIo1ZZUhkBD+8NDqBdqV2mIec/HCfOc
FZxNkFW92RuZqYNZ+XW6QsUnAn3pvAn5l/PKW3OiGwdgX7nqe8sdpgMqmJBvn1eG
wXHelL6gOtW5PcyPpz2IvTav+O2VeRbu6JidEZ3yxBt/K+EvLkGsysM5/FKiSGJR
wm/ioOEDwIXW58AkatDKSGuP7l8p6Ti9FQr0guhJEsEvdVMt9MauRmB2Hsvm1FdC
/N54qm9BKRQelKucjt5MN7484p2nbN4CoUXOkOLxczLszSuR3q6lQhJRUAqXmFy+
p4j17Dwfh2YPZzblZ5J59VLdmbcG2AuhVHKrH4nnCKOrJph9E1y8QWNCcmW3hyD4
Ugf14KaqCxEqIDw/JHyymug6I9BWFxy3kyies3ToS1vXVV4lVcWfnmUN5PxZgxWc
6iC+e/9KVR/2
=8bvl
-END PGP SIGNATURE-



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

Bug#1064332: Bug#1065217: libpetsc-complex3.19-dev fails to install

Attached is a patch for a follow-up NMU correcting this issue.

On Sat, Mar 02, 2024 at 02:15:57AM +0200, Adrian Bunk wrote:
> Package: libpetsc-complex3.19-dev
> Version: 3.19.6+dfsg1-2.1
> Severity: serious
> Tags: ftbfs
> X-Debbugs-Cc: Benjamin Drung , Steve Langasek 
> 
> Control: affects -1 src:slepc
> 
> https://buildd.debian.org/status/fetch.php?pkg=slepc&arch=amd64&ver=3.19.2%2Bdfsg1-2.1&stamp=1709337662&raw=0
> 
> ...
> Setting up libpetsc-complex3.19-dev:amd64 (3.19.6+dfsg1-2.1) ...
> update-alternatives: error: no alternatives for petsc
> update-alternatives: error: alternative path 
> /usr/lib/petscdir/petsc3.19t64/x86_64-linux-gnu-complex doesn't exist
> dpkg: error processing package libpetsc-complex3.19-dev:amd64 (--configure):
>  installed libpetsc-complex3.19-dev:amd64 package post-installation script 
> subprocess returned error exit status 2
> ...
> 

-- 
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 petsc-3.19.6+dfsg1/debian/changelog 
petsc-3.19.6+dfsg1/debian/changelog
--- petsc-3.19.6+dfsg1/debian/changelog 2024-01-21 06:41:21.0 +
+++ petsc-3.19.6+dfsg1/debian/changelog 2024-03-03 21:40:10.0 +
@@ -1,3 +1,18 @@
+petsc (3.19.6+dfsg1-2.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix extraneous X-Time64-Compat declarations.
+  * Fix substitution of soname in maintainer scripts.  Closes: #1065217.
+
+ -- Steve Langasek   Sun, 03 Mar 2024 21:40:10 +
+
+petsc (3.19.6+dfsg1-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Rename libraries for 64-bit time_t transition.  Closes: #1064332
+
+ -- Benjamin Drung   Thu, 29 Feb 2024 20:22:10 +
+
 petsc (3.19.6+dfsg1-2) unstable; urgency=medium
 
   * Update debian/patches/soname_extension to also add a define PETSC_LIB_EXT,
diff -Nru petsc-3.19.6+dfsg1/debian/control petsc-3.19.6+dfsg1/debian/control
--- petsc-3.19.6+dfsg1/debian/control   2024-01-21 06:41:21.0 +
+++ petsc-3.19.6+dfsg1/debian/control   2024-03-03 21:34:32.0 +
@@ -4,7 +4,7 @@
 Maintainer: Debian Science Maintainers 

 Uploaders: "Adam C. Powell, IV" , Drew Parsons 

 Standards-Version: 4.6.2
-Build-Depends: debhelper-compat (= 13), python3, gfortran,
+Build-Depends: dpkg-dev (>= 1.22.5), debhelper-compat (= 13), python3, 
gfortran,
  pkg-config, dh-python,
  dh-fortran-mod,
  gdb,
@@ -86,7 +86,7 @@
 Multi-Arch: same
 Architecture: any
 Section: libdevel
-Depends: libpetsc-real3.19 (= ${binary:Version}),
+Depends: libpetsc-real3.19t64 (= ${binary:Version}),
  libpetsc3.19-dev-common (= ${source:Version}),
  ${MPI:Depends},
  libhypre-dev (>= 2.15.1),
@@ -99,7 +99,7 @@
 Conflicts: libpetsc3.6.3-dev (<< 3.6.3.dfsg2-2), libpetsc-complex-3.6.3-dev 
(<< 3.6.3.dfsg2-2),
  libpetsc3.6.2-dev (<= 3.6.2.dfsg1-3), libpetsc-complex-3.6.2-dev (<= 
3.6.2.dfsg1-3)
 Recommends: libpetsc3.19-dev-examples, ksh | mksh | pdksh | zsh
-Suggests: petsc-dev, libpetsc-real3.19-dbg (= ${binary:Version}), 
petsc3.19-doc, libluminate-dev
+Suggests: petsc-dev, libpetsc-real3.19t64-dbg (= ${binary:Version}), 
petsc3.19-doc, libluminate-dev
 Description: Static libraries, shared links, header files for PETSc
  PETSc is the "Portable Extensible Toolkit for Scientific
  Computation", a suite of data structures and routines for the
@@ -112,16 +112,16 @@
  This package provides the development files for building applications
  using PETSc 3.19 with real numbers.
 
-Package: libpetsc-real3.19
+Package: libpetsc-real3.19t64
 Architecture: any
 Multi-Arch: same
 Section: libs
-Provides: libpetsc3.19
+Provides: ${t64:Provides}, libpetsc3.19
 Pre-Depends: ${misc:Pre-Depends}
 Depends: ${shlibs:Depends}, ${misc:Depends}
 Conflicts: libpetsc3.6 (<< 3.6.2.dfsg1-4)
-Breaks: libpetsc-real3.10, libslepc-real3.10, libpetsc3.10-dev-common, 
libpetsc3.10-dev-examples
-Replaces: libpetsc3.6 (<< 3.6.2.dfsg1-4)
+Breaks: libpetsc-real3.19 (<< ${source:Version}), libpetsc-real3.10, 
libslepc-real3.10, libpetsc3.10-dev-common, libpetsc3.10-dev-examples
+Replaces: libpetsc-real3.19, libpetsc3.6 (<< 3.6.2.dfsg1-4)
 Description: Shared libraries for version 3.19 of PETSc
  PETSc is the "Portable Extensible Toolkit for Scientific
  Computation", a suite of data structures and routines for the
@@ -133,7 +133,7 @@
  .
  This package contains the PETSc 3.19 shared library for real numbers.
  .
- It provides soname libpetsc-real3.19
+ It provides soname libpetsc-real3.19t64
 
 Package: libpetsc3.19-dev-common
 Architecture: all
@@ -173,7 +173,7 @@
 Depends: ${misc:Depends}, ${python3:Depends},
  libjs-mathjax
 Recommends: ksh | mksh | pdksh | zsh,
- libpetsc-real3.19-dev | libpetsc-complex3.19-dev | libpetsc-real3.19-dbg | 
libpetsc-complex3.19-dbg
+ libpetsc-real3.19-dev | libpetsc-complex3.19-de

Bug#1062611: libiv-unidraw2t64 has an undeclared file conflict

2024-03-03 Thread Agustin Martin

El vie, 2 feb 2024 a las 6:57, Helmut Grohne () escribió:
>
> Package: libiv-unidraw2t64
> Version: 2.0.11d.a1-1.1~exp1
> Severity: serious
> User: debian...@lists.debian.org
> Usertags: fileconflict
> Control: affects -1 + libiv2 libiv2t64
> X-Debbugs-Cc: Graham Inggs , vor...@debian.org
>
> libiv-unidraw2t64 has an undeclared file conflict. This may result in an
> unpack error from dpkg.
>
> The files
>  * /usr/lib/x86_64-linux-gnu/libIV.so.2
>  * /usr/lib/x86_64-linux-gnu/libIV.so.2.0.0
> are contained in the packages
>  * libiv-unidraw2t64/2.0.11d.a1-1.1~exp1 as present in experimental
>  * libiv2
>* 2.0.11d.a1-1+b4 as present in bookworm
>* 2.0.11d.a1-1+b5 as present in trixie|unstable
>* 2.0.4a1-2 as present in bullseye
>  * libiv2t64/2.0.11d.a1-1.1~exp1 as present in experimental

Hi, Helmut.

I wonder if this is still an issue. Some uploads happened in the
meantime and seems that  those files are currently shipped by a
different package

$ dpkg -S libIV.so.2
libiv2t64:amd64: /usr/lib/x86_64-linux-gnu/libIV.so.2.0.0
libiv2t64:amd64: /usr/lib/x86_64-linux-gnu/libIV.so.2

which apparently handles things well

Package: libiv2t64
Replaces: libiv2
Provides: libiv2 (= 2.0.11d.a1-1.1)
Breaks: libiv2 (<< 2.0.11d.a1-1.1)

Bug#1065282: marked as done (dsniff: missing build-dep on libtirpc-dev)

Your message dated Sun, 03 Mar 2024 23:04:36 +
with message-id 
and subject line Bug#1065282: fixed in dsniff 2.4b1+debian-32
has caused the Debian Bug report #1065282,
regarding dsniff: 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.)


-- 
1065282: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065282
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: dsniff
Version: 2.4b1+debian-31
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 dsniff to
FTBFS in sid with:

|dh_auto_configure
| ./configure --build=x86_64-linux-gnu --prefix=/usr 
--includedir=\${prefix}/include --mandir=\${prefix}/share/man 
--infodir=\${prefix}/share/info --sysconfdir=/etc --localstatedir=/var 
--disable-option-checking --disable-silent-rules 
--libdir=\${prefix}/lib/x86_64-linux-gnu --runstatedir=/run 
--disable-maintainer-mode --disable-dependency-tracking
| checking for gcc... gcc
| checking whether the C compiler works... no
| configure: error: in `/<>':
| configure: error: C compiler cannot create executables
| See `config.log' for more details
| tail -v -n \+0 config.log
| ==> config.log <==
| This file contains any messages produced by compilers while
| running configure, to aid debugging if configure makes a mistake.
 
...
 
| configure:3051: checking whether the C compiler works
| configure:3073: gcc -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -fstack-clash-protection -Wformat 
-Werror=format-security -fcf-protection -I/usr/include/tirpc/ -Wdate-time 
-D_FORTIFY_SOURCE=2 -Wl,-z,relro -Wl,-z,now -ltirpc conftest.c  >&5
| /usr/bin/ld: cannot find -ltirpc: No such file or directory
| collect2: error: ld returned 1 exit status
| configure:3077: $? = 1
| configure:3117: result: no
| configure: failed program was:
| | /* confdefs.h */
| | #define PACKAGE_NAME ""
| | #define PACKAGE_TARNAME ""
| | #define PACKAGE_VERSION ""
| | #define PACKAGE_STRING ""
| | #define PACKAGE_BUGREPORT ""
| | #define PACKAGE_URL ""
| | /* end confdefs.h.  */
| |
| | int
| | main (void)
| | {
| |
| |   ;
| |   return 0;
| | }
| configure:3122: error: in `/<>':
| configure:3124: error: C compiler cannot create executables
| See `config.log' for more details

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: dsniff
Source-Version: 2.4b1+debian-32
Done: Marcos Fouces 

We believe that the bug you reported is fixed in the latest version of
dsniff, 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.
Marcos Fouces  (supplier of updated dsniff package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 03 Mar 2024 23:07:27 +0100
Source: dsniff
Architecture: source
Version: 2.4b1+debian-32
Distribution: unstable
Urgency: medium
Maintainer: Debian Security Tools 
Changed-By: Marcos Fouces 
Closes: 1065282
Changes:
 dsniff (2.4b1+debian-32) unstable; urgency=medium
 .
   * Add missing libtirpc-dev to Build-Depends. (Closes:#1065282).
   * Update d/copyright.
   * Update Standards-Version to 4.6.2 (no changes needed).
Checksums-Sha1:
 c320e3ccf9665abc8ada0141e5f501fa30748874 2090 dsniff_2.4b1+debian-32.dsc
 aa52289b149ebc4a83bee546fd06435790cb48f2 30904 
dsniff_2.4b1+debian-32.debian.tar.xz
 c40283f11ff7173b9b5f2fe78bce40e1e93d76d1 8503 
dsniff_2.4b1+debian-32_source.buildinfo
Checksums-Sha256:
 31ffd0fc5f

Bug#1002789: marked as done (python-pycdlib: FTBFS: failed tests)

Your message dated Sun, 3 Mar 2024 23:29:44 +0100
with message-id 
and subject line Re: Bug#1002789 closed by Debian FTP Masters 
 (reply to Thomas Goirand ) 
(Bug#1002789: fixed in python-pycdlib 1.12.0+ds1-5)
has caused the Debian Bug report #1002789,
regarding python-pycdlib: FTBFS: failed tests
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.)


-- 
1002789: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002789
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-pycdlib
Version: 1.12.0+ds1-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211228 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> make[1]: pyversions: No such file or directory
> py3versions: no X-Python3-Version in control file, using supported versions
> pkgos-dh_auto_install --no-py2 --in-tmp
> + PKGOS_USE_PY2=yes
> + PKGOS_USE_PY3=yes
> + PKGOS_IN_TMP=no
> + PKGOS_USE_PY2=no
> + shift
> + PKGOS_IN_TMP=yes
> + shift
> + dpkg-parsechangelog -SSource
> + SRC_PKG_NAME=python-pycdlib
> + echo python-pycdlib
> + sed s/python-//
> + PY_MODULE_NAME=pycdlib
> + [ no = yes ]
> + [ yes = yes ]
> + py3versions -vr
> + PYTHON3S=3.10 3.9
> + [ no = yes ]
> + [ yes = yes ]
> + [ yes = yes ]
> + TARGET_DIR=tmp
> + pwd
> + python3.10 setup.py install --install-layout=deb --root 
> /<>/debian/tmp
> running install
> /usr/lib/python3/dist-packages/setuptools/command/install.py:34: 
> SetuptoolsDeprecationWarning: setup.py install is deprecated. Use build and 
> pip and other standards-based tools.
>   warnings.warn(
> running build
> running build_py
> creating build
> creating build/lib
> creating build/lib/pycdlib
> copying pycdlib/__init__.py -> build/lib/pycdlib
> copying pycdlib/dates.py -> build/lib/pycdlib
> copying pycdlib/backport_functools.py -> build/lib/pycdlib
> copying pycdlib/eltorito.py -> build/lib/pycdlib
> copying pycdlib/pycdlibexception.py -> build/lib/pycdlib
> copying pycdlib/udf.py -> build/lib/pycdlib
> copying pycdlib/rockridge.py -> build/lib/pycdlib
> copying pycdlib/pycdlib.py -> build/lib/pycdlib
> copying pycdlib/isohybrid.py -> build/lib/pycdlib
> copying pycdlib/headervd.py -> build/lib/pycdlib
> copying pycdlib/path_table_record.py -> build/lib/pycdlib
> copying pycdlib/facade.py -> build/lib/pycdlib
> copying pycdlib/dr.py -> build/lib/pycdlib
> copying pycdlib/inode.py -> build/lib/pycdlib
> copying pycdlib/pycdlibio.py -> build/lib/pycdlib
> copying pycdlib/utils.py -> build/lib/pycdlib
> running build_scripts
> creating build/scripts-3.10
> copying and adjusting tools/pycdlib-explorer -> build/scripts-3.10
> copying and adjusting tools/pycdlib-extract-files -> build/scripts-3.10
> copying and adjusting tools/pycdlib-genisoimage -> build/scripts-3.10
> changing mode of build/scripts-3.10/pycdlib-explorer from 644 to 755
> changing mode of build/scripts-3.10/pycdlib-extract-files from 644 to 755
> changing mode of build/scripts-3.10/pycdlib-genisoimage from 644 to 755
> 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/pycdlib
> copying build/lib/pycdlib/__init__.py -> 
> /<>/debian/tmp/usr/lib/python3/dist-packages/pycdlib
> copying build/lib/pycdlib/dates.py -> 
> /<>/debian/tmp/usr/lib/python3/dist-packages/pycdlib
> copying build/lib/pycdlib/backport_functools.py -> 
> /<>/debian/tmp/usr/lib/python3/dist-packages/pycdlib
> copying build/lib/pycdlib/eltorito.py -> 
> /<>/debian/tmp/usr/lib/python3/dist-packages/pycdlib
> copying build/lib/pycdlib/pycdlibexception.py -> 
> /<>/debian/tmp/usr/lib/python3/dist-packages/pycdlib
> copying build/lib/pycdlib/udf.py -> 
> /<>/debian/tmp/usr/lib/python3/dist-packages/pycdlib
> copying build/lib/pycdlib/rockridge.py -> 
> /<>/debian/tmp/usr/lib/python3/dist-packages/pycdlib
> copying build/lib/pycdlib/pycdlib.py -> 
> /<>/debian/tmp/usr/lib/python3/dist-packages/pycdlib
> copying build/lib/pycdlib/isohybrid.py -> 
> /<>/debian/tmp/usr/lib/python3/dist-packages/pycdlib
> copying build/lib/pycdlib/headervd.py -> 
> /<>/debian/tmp/usr/lib/python3/dist-packages/pycdlib
> copying build/lib/pycdlib/path_table_record.py -> 
> /<>/debian/tmp/usr/lib/python3/dist-packages/pycdlib
> copying build/lib/pycdlib/facade.py -> 
> /<>/debian/tmp/usr/lib/python3/dist-packages/pycdlib

Bug#1065225: marked as done (slurm-wlm FTBFS on !amd64)

Your message dated Sun, 03 Mar 2024 21:59:56 +
with message-id 
and subject line Bug#1065225: fixed in slurm-wlm 23.11.4-1.2
has caused the Debian Bug report #1065225,
regarding slurm-wlm FTBFS 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.)


-- 
1065225: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065225
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: slurm-wlm
Version: 23.11.4-1.1
Severity: serious
Tags: ftbfs
X-Debbugs-Cc: Sergio Durigan Junior , Steve Langasek 
, Benjamin Drung 

https://buildd.debian.org/status/logs.php?pkg=slurm-wlm&ver=23.11.4-1.1

...
   dh_install -a -O--builddirectory
dh_install: warning: Cannot find (any matches for) 
"usr/lib/x86_64-linux-gnu/slurm-wlm/accounting_storage_slurmdbd.so" (tried in 
., debian/tmp)

dh_install: warning: slurm-wlm-basic-plugins missing files: 
usr/lib/x86_64-linux-gnu/slurm-wlm/accounting_storage_slurmdbd.so
dh_install: warning: Cannot find (any matches for) 
"usr/lib/x86_64-linux-gnu/slurm-wlm/acct_gather_energy_gpu.so" (tried in ., 
debian/tmp)
...
dh_install: error: missing files, aborting
make: *** [debian/rules:23: binary-arch] Error 255



The 64-bit time_t NMU diff (#1062903) hardcodes
debian/tmp/usr/lib/x86_64-linux-gnu/ which cannot
work on other architectures.
--- End Message ---
--- Begin Message ---
Source: slurm-wlm
Source-Version: 23.11.4-1.2
Done: Steve Langasek 

We believe that the bug you reported is fixed in the latest version of
slurm-wlm, 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 slurm-wlm package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 03 Mar 2024 20:11:29 +
Source: slurm-wlm
Architecture: source
Version: 23.11.4-1.2
Distribution: unstable
Urgency: medium
Maintainer: Debian HPC Team 
Changed-By: Steve Langasek 
Closes: 1065225
Changes:
 slurm-wlm (23.11.4-1.2) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Remove extraneous files from debian that are not handled by the package
 clean target, and caused build failures on !amd64.  Closes: #1065225.
Checksums-Sha1:
 4b24a454499dd8e80c57f06b074ccfeaf42d5bb8 5650 slurm-wlm_23.11.4-1.2.dsc
 34abac03a45bf39cb8de38232dda7a667b35ae5a 136456 
slurm-wlm_23.11.4-1.2.debian.tar.xz
 c3cbfd54d5aa3be3491fd313056e3bc104a796d6 14858 
slurm-wlm_23.11.4-1.2_source.buildinfo
Checksums-Sha256:
 10649b0a1d7378ca096894b987395e46423e5e8050d9eb95dee007bc0847e642 5650 
slurm-wlm_23.11.4-1.2.dsc
 f16e7c4b00c7c241ca599f73d8102096e1707fa43f582ee646f6993b94805722 136456 
slurm-wlm_23.11.4-1.2.debian.tar.xz
 a7cac66b33940a893d90203d604af868eb64722d04f16d6f53d73ab1b98b7170 14858 
slurm-wlm_23.11.4-1.2_source.buildinfo
Files:
 866dfd23d3058c64929de284e54677cc 5650 admin optional slurm-wlm_23.11.4-1.2.dsc
 ff4229d5f15e5fae7d5fb3d2eaa21d6c 136456 admin optional 
slurm-wlm_23.11.4-1.2.debian.tar.xz
 1119f8d96acd77c10d9d5917073b6b1e 14858 admin optional 
slurm-wlm_23.11.4-1.2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJGBAEBCgAwFiEErEg/aN5yj0PyIC/KVo0w8yGyEz0FAmXk4kESHHZvcmxvbkBk
ZWJpYW4ub3JnAAoJEFaNMPMhshM9ABMP/2/jzt2ksd6Os0JgzuwlvCYllgPv3Jy9
ObTh5RkgQTQmfFpsByeBDbCYWpVMyhFLWdlx0SMQ0MSe6ne26xpoxez4FYWr8Dgk
RqJ+1Grb70VlPeK+4l+Fn1LRfCqPcK9xg6Ioc/MFs/aQPAktq2xlAFvtYytYB1go
S3PsQD5fOR4ZbO+GX3KxlC+sOVmBwJDJd5baKijGllMGo8UcXH3Mt9gXdgW3oq8O
5ZX3dVsxLOJKmvg6+TyGjadwVGQgEbbZ9ocdx7JGJ4ZnCxL28U6FVzY554UyxR6v
mm7ohPU53NSw36f1VljeFqzI2C3Po/pO1qC4Pw0IyqBdWEiHA7iu9VcYHESVuaW4
vnbQlmdhySk1s3y4w9lrtE/tCTUkszVLCusiFflfgdFp+GHptHqCSIkyev7WmqbN
qUWprydCFBS2TKWnRMRUroAJ4NzTJIb9uhSVT4/Rhbz7sIwMfnm3hJN98Zvnqcz2
KD289BNVjo2xQQpPvq2039B32YJpU2k5zJDl/ndnsKtA7oqYBJ4OO3BDBvMg3I1a
p2PszcN5GbvBHk3xBAi06aAwNIUT+JJxLObanKIyeFMRkBa7xif2o5YkEhFAq/+h
QXuW9IvoBtQV4AWehBXH8PnaPRLc66Ykv0CFghHk8/TYARw1aD7ZSbky9yHdE60L
xDiqyn+3ov0H
=cYh1
-END PGP SIGNATURE-



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

Bug#1062218: libaio: NMU diff for 64-bit time_t transition

Hi!

On Thu, 2024-02-29 at 02:35:16 +0100, Guillem Jover wrote:
> Control: tags -1 - pending

> On Wed, 2024-01-31 at 19:36:09 +, Steve Langasek wrote:
> > Source: libaio
> > Version: 0.3.113-5
> > Severity: serious
> > Tags: patch pending
> > Justification: library ABI skew on upgrade
> > User: debian-...@lists.debian.org
> > Usertags: time-t
> 
> > Please find the patch for this NMU attached.
> > 
> > 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.
> 
> Unfortunately I just realized this patch is not enough. :/ This library
> emits direct syscalls, so these are going to be broken with the time_t
> size change, the syscalls need to be updated. I'm checking how to best
> fix this, perhaps even via dual-ABI, to avoid the transition
> altogether, but let's see.
> 
> I guess this might have been missed for other packages that that emit
> direct syscalls and are not using the time64 variants for those
> already.

Just as a status update, I've got most of this working, but upstream
does not tend to be very responsive, so I think I'll do a proper
SONAME bump with my proposed changes for the dual-ABI, to avoid any
potential clashes with anything that gets upstream, and to make a
revert easier, by reusing the t64 library names. And then once/if this
gets merged upstream I can revert that and simply do the proper
dual-ABI on the old SONAME and package names, as if nothing had
happened (except for the required rebuilds).

Hopefully I can have something for upload today or tomorrow, hoping
that this delay up to now, does not block too many things. :/

Thanks,
Guillem

Processed: forcibly merging 1061339 1065330

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

> forcemerge 1061339 1065330
Bug #1061339 [src:numpy] numpy_1.26.3-1_s390x-buildd.changes REJECTED
Bug #1061339 [src:numpy] numpy_1.26.3-1_s390x-buildd.changes REJECTED
The source numpy and version 1.26.3-1 do not appear to match any binary packages
The source numpy and version 1:1.26.3-1 do not appear to match any binary 
packages
The source numpy and version 1:1.26.3-2 do not appear to match any binary 
packages
Marked as found in versions numpy/1:1.26.3-2.
Bug #1065330 [src:numpy] numpy_1.26.3-2_ppc64el-buildd.changes REJECTED
Set Bug forwarded-to-address to 'https://github.com/numpy/numpy/issues/25681'.
The source numpy and version 1.26.3-1 do not appear to match any binary packages
The source numpy and version 1:1.26.3-1 do not appear to match any binary 
packages
The source numpy and version 1:1.26.3-2 do not appear to match any binary 
packages
Marked as found in versions numpy/1:1.26.3-1 and numpy/1.26.3-1.
Added tag(s) ftbfs.
Merged 1061339 1065330
> thanks
Stopping processing here.

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

Bug#1062407: liblopsub: NMU diff for 64-bit time_t transition

2024-03-03 Thread Andre Noll

On Sun, Mar 03, 11:47, Steve Langasek wrote

> > Below it what I've just applied. The patch looks different to what
> > you've sent, but the resulting tree is identical. Please let me know
> > if you're OK with the commit message.
> 
> No objections.

Merged and pushed out to the public repo.

Thanks
Andre
-- 
Max Planck Institute for Biology
Tel: (+49) 7071 601 829
Max-Planck-Ring 5, 72076 Tübingen, Germany
http://people.tuebingen.mpg.de/maan/


signature.asc
Description: PGP signature

Bug#1065331: libhdf5-103-1t64: depends on libcurl4 instead of libcurl4t64

2024-03-03 Thread Vincent Lefevre

On 2024-03-03 01:08:10 +0100, Vincent Lefevre wrote:
> Package: libhdf5-103-1t64
> Version: 1.10.10+repack-3.1
> Severity: serious
> 
> libhdf5-103-1t64 depends on libcurl4 instead of libcurl4t64.
> This makes the upgrade of curl impossible.

It seems that this was actually a bug in curl, where libcurl4t64
had an incorrect X-Time64-Compat and which has just been fixed in

https://salsa.debian.org/debian/curl/-/commit/40bdd3894230d325d382d59684c32d74202eee5c

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

Bug#1065395: spirv-llvm-translator-14: autopkgtest on s390x uses huge amount of disk space

2024-03-03 Thread Paul Gevers


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% 
/scratch
/dev/mapper/3600507630affd250004a  196G   94G   93G  51% 
/scratch
/dev/mapper/3600507630affd250004a  196G   97G   90G  52% 
/scratch
/dev/mapper/3600507630affd250004a  196G  100G   87G  54% 
/scratch
/dev/mapper/3600507630affd250004a  196G  103G   84G  56% 
/scratch
/dev/mapper/3600507630affd250004a  196G  106G   81G  57% 
/scratch
/dev/mapper/3600507630affd250004a  196G  109G   78G  59% 
/scratch
/dev/mapper/3600507630affd250004a  196G  112G   74G  61% 
/scratch
/dev/mapper/3600507630affd250004a  196G  116G   71G  63% 
/scratch
/dev/mapper/3600507630affd250004a  196G  119G   68G  64% 
/scratch
/dev/mapper/3600507630affd250004a  196G  123G   64G  66% 
/scratch
/dev/mapper/3600507630affd250004a  196G  126G   61G  68% 
/scr

Bug#1062407: liblopsub: NMU diff for 64-bit time_t transition

On Sun, Mar 03, 2024 at 05:08:19PM +0100, Andre Noll wrote:
> On Fri, Mar 01, 05:37, Steve Langasek wrote:

> > Please find attached a final version of this patch for the time_t
> > transition.  This patch is being uploaded to unstable.

> > Note that this adds a versioned build-dependency on dpkg-dev, to guard
> > against accidental backports with a wrong ABI.

> Applied. Since the previous version was applied and made public
> last month, I've reverted that patch, applied this final version and
> squashed the two new commits into one.

> Below it what I've just applied. The patch looks different to what
> you've sent, but the resulting tree is identical. Please let me know
> if you're OK with the commit message.

No objections.

Cheers,
-- 
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#1064852: incus: missing depends on iproute2

2024-03-03 Thread Colin Watson

On Tue, Feb 27, 2024 at 01:33:08AM +, Mathias Gibbens wrote:
>   iproute2 is Priority: important, which according to Policy §2.5 means
> that it is generally expected to be present on a Debian system. Do you
> have a specific use case where for some reason you don't have iproute2
> installed?

Would you mind reassessing your view in light of Policy 3.5
(https://www.debian.org/doc/debian-policy/ch-binary.html#dependencies)?
I think it's quite straightforward and unambiguous.

Section 2.5 has traditionally not been what controls decisions about
when dependencies ought to be specified, and this particular case is one
that I'm surprised to find being controversial.  The fine distinction
between "Priority: required" and "Essential: yes" has sometimes confused
people in the past and has needed some discussion, but it's always been
my experience that if one package needs another "Priority: important"
package for proper functioning then it's been quite uncontroversial that
the first package must declare a dependency.

Thanks,

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

Processed: closing 1065380

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

> close 1065380 2.0.3-1
Bug #1065380 [libpcsclite-dev] ausweisapp2 FTBFS with pcsc-lite 2.0.2
Marked as fixed in versions pcsc-lite/2.0.3-1.
Bug #1065380 [libpcsclite-dev] ausweisapp2 FTBFS with pcsc-lite 2.0.2
Marked Bug as done
> thanks
Stopping processing here.

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

Processed: Re: Bug#1065380: ausweisapp2 FTBFS with pcsc-lite 2.0.2

Processing control commands:

> reassign -1 libpcsclite-dev 2.0.2-1
Bug #1065380 [src:ausweisapp2] ausweisapp2 FTBFS with pcsc-lite 2.0.2
Bug reassigned from package 'src:ausweisapp2' to 'libpcsclite-dev'.
No longer marked as found in versions ausweisapp2/2.0.3-1.
Ignoring request to alter fixed versions of bug #1065380 to the same values 
previously set
Bug #1065380 [libpcsclite-dev] ausweisapp2 FTBFS with pcsc-lite 2.0.2
Marked as found in versions pcsc-lite/2.0.2-1.
> affects -1 src:ausweisapp2
Bug #1065380 [libpcsclite-dev] ausweisapp2 FTBFS with pcsc-lite 2.0.2
Added indication that 1065380 affects src:ausweisapp2

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

Bug#1065380: ausweisapp2 FTBFS with pcsc-lite 2.0.2

2024-03-03 Thread Adrian Bunk

Control: reassign -1 libpcsclite-dev 2.0.2-1
Control: affects -1 src:ausweisapp2

On Sun, Mar 03, 2024 at 06:41:25PM +0100, Ludovic Rousseau wrote:
> Le 03/03/2024 à 17:13, Adrian Bunk a écrit :
> > Source: ausweisapp2
> > Version: 2.0.3-1
> > Severity: serious
> > Tags: ftbfs
> > X-Debbugs-Cc: Ludovic Rousseau 
> > 
> > https://buildd.debian.org/status/logs.php?pkg=ausweisapp2&ver=2.1.0-1
> > 
> > ...
> > /<>/src/card/pcsc/PcscUtils.h:112:46: error: 
> > ‘SCARD_E_UNKNOWN_RES_MNG’ was not declared in this scope; did you mean 
> > ‘SCARD_E_UNKNOWN_RES_MSG’?
> >112 | Scard_E_Unknown_Res_Mng = 
> > returnCode(SCARD_E_UNKNOWN_RES_MNG), /**< An unrecognized error 
> > code was returned from a layered component. */
> >|  
> > ^~~
> > ...
> > 
> > 
> > This is not a regression in the new ausweisapp2 upload,
> > but due to a change in pcsc-lite 2.0.2 (maintainer Cc'ed):
> > 
> > https://salsa.debian.org/rousseau/PCSC/-/commit/65f9b610138c8a4a5563d0332120f684682e0237
> > "Fix typo in (unused) error code SCARD_E_UNKNOWN_RES_MSG"
> 
> Exact.
> 
> I now discover that Windows does define BOTH values:
> SCARD_E_UNKNOWN_RES_MSG 0x8010002B in 
> https://learn.microsoft.com/en-us/openspecs/windows_protocols/ms-rdpesc/9861f8da-76fe-41e6-847e-40c9aa35df8d
> SCARD_E_UNKNOWN_RES_MNG 0x8010002B in 
> https://learn.microsoft.com/en-us/windows/win32/secauthn/authentication-return-values
> 
> I guess pcsc-lite will also have to define both values.
> I will release a new pcsc-lite version soon.
>...

Thanks, I'm reassigning the bug to libpcsclite-dev since that's where it 
will be fixed.

cu
Adrian

Bug#1065022: marked as done (libglib2.0-0t64: transition from libglib2.0-0 breaks GSettings, GIO modules)

Your message dated Sun, 03 Mar 2024 18:04:32 +
with message-id 
and subject line Bug#1065022: fixed in glib2.0 2.78.4-3
has caused the Debian Bug report #1065022,
regarding libglib2.0-0t64: transition from libglib2.0-0 breaks GSettings, GIO 
modules
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.)


-- 
1065022: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065022
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libglib2.0-0t64
Version: 2.78.4-2
Severity: critical
Justification: breaks unrelated software
X-Debbugs-Cc: debian-de...@lists.debian.org

Hey.


CCing d-d since there seems some further deeper problem with the t64
transition (namely lib files getting lost, when "downgrading" i.e.
reverting).


Earlier tonight I've upgraded this day’s packages which included
numerous that made the t64 transition (see the attached aptitude log
for the whole process, first the upgrade, and then "bi-secting" to
find the culprit).

Immediately afterwards, starting GUI programs from the still running
desktop environment caused failures like:
$ evince

(evince:17537): GLib-GIO-CRITICAL **: 04:18:22.610: 
g_settings_schema_source_lookup: assertion 'source != NULL' failed

(evince:17537): GLib-GIO-CRITICAL **: 04:18:22.610: 
g_settings_schema_source_lookup: assertion 'source != NULL' failed

(evince:17537): GLib-GIO-ERROR **: 04:18:22.658: No GSettings schemas are 
installed on the system
Trace/breakpoint trap
$ gedit

(gedit:17585): GLib-GIO-ERROR **: 04:18:35.012: No GSettings schemas are 
installed on the system
Trace/breakpoint trap
$

I suspected a reboot might be needed but after that even the display
manager didn't start anymore.
I saw errors like:
Feb 29 02:51:14 heisenberg kernel: traps: at-spi-bus-laun[17935] trap int3 
ip:7fdceec49587 sp:7ffd0acdade0 error:0 in 
libglib-2.0.so.0.7800.4[7fdceec05000+99000]
Feb 29 02:51:52 heisenberg kernel: traps: at-spi-bus-laun[17941] trap int3 
ip:7f52e53ee587 sp:7ffcc69b0fc0 error:0 in 
libglib-2.0.so.0.7800.4[7f52e53aa000+99000]


My first guess was glib, so I downgraded that (everything from the source
package), but that didn't help.

As you can see from the aptitude log, I then moved on downgrade further
of the previously upgraded packages, several times I've rebooted in-
between (e.g. after downgrading things like *pam* and *systemd*).

Along the way I saw the most weirdest effects:
- logind was apprently in some bogus state, which I think might
  have been the reason, why X/the display manager remained black/hung for
  several minutes:
  Feb 29 03:37:21 heisenberg lightdm[139886]: Failed to get list of logind 
seats: GDBus.Error:org.freedesktop.DBus.Error.TimedOut: Failed to activate 
service 'org.freedesktop.login1': timed out (service_start_timeout=25000ms)

- At some point, when installing packages via aptitude
  # aptitude
  
  Performing actions...
  
  
  And it also hung at the end shortly after finishing the
  upgrade/downgrade.

- When downgrading packages that had a t64 transition, sometimes
  the lib file was gone.
  I.e. I removed the *t64 package and re-installed the old one
  and then the .so file for libapt-pkg6.0 and libpam0g was missing.
  How can that happen?


Eventually I downgraded the gcr/gck stuff, and then it worked again.

From that I went forward and upgrade all the various packages again, to
see where the problem actuall is.

Turns out, it's probably actually libglib.

When I install the first time libglib2.0-0t64 (and purge libglib2.0-0),
things start to break apart.
When I re-install libglib2.0-0t64, things work again (it seems regardless
of the gcr/gck stuff).


Long story short:
@glib maintainers:
- there's something wrong with the transition (unless even that need for
  the re-install is already a sign for some deeper issues)

@d-d:
- How can it happen that purge *t64 packages and at the same time install
  the previous package, and then the so file is missing?
  I mean it's clear that they use the same name, but shouldn't DPKG handle
  the cleanly?

Thanks,
Chris

PS: I'll attach the aptitude log only to the bug and not to d-d, in
order not to spam so many people with it.
It's probably anyway uselesss, but might help to find out why
downgrading gck/gcr stuff helped first, without re-installing the
glib package.

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

Kernel: Linux 6.6.15-amd64 (SMP w/16 CPU threads; PREEMPT)
Locale: LANG=en_D

Bug#1065280: marked as done (glib2.0: missing dpkg-dev (>= 1.22.5) build dependency for time_t transition)

Your message dated Sun, 03 Mar 2024 18:04:32 +
with message-id 
and subject line Bug#1065280: fixed in glib2.0 2.78.4-3
has caused the Debian Bug report #1065280,
regarding glib2.0: 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.)


-- 
1065280: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065280
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: glib2.0
Version: 2.78.4-2.1
Severity: serious
X-Debbugs-Cc: sramac...@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: glib2.0
Source-Version: 2.78.4-3
Done: Simon McVittie 

We believe that the bug you reported is fixed in the latest version of
glib2.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 glib2.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: Sun, 03 Mar 2024 13:30:12 +
Source: glib2.0
Architecture: source
Version: 2.78.4-3
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Simon McVittie 
Closes: 1065022 1065280
Changes:
 glib2.0 (2.78.4-3) unstable; urgency=medium
 .
   * Build-depend on dpkg-dev (>= 1.22.5), to ensure that we are on the
 64-bit time_t side of the transition (Closes: #1065280).
 If this version gets backported, then the whole t64 package rename
 (including this change) will need to be reverted in the backport.
   * d/libglib2.0-0t64.preinst: Remove libglib2.0-0 postrm to avoid file loss
 (Closes: #1065022)
   * d/tests: Add a manual reproducer for #1065022
   * d/libglib2.0-0t64.post*: Stop generating from a template.
 dh_installdeb will substitute #DEB_HOST_MULTIARCH# for us since
 debhelper 12.2 (2019).
   * d/libglib2.0-0t64.postrm: Only clean up giomodule.cache during purge.
 This matches the behaviour that we have had for gschemas.compiled
 since 2012.
   * d/libglib2.0-0t64.postrm: Avoid recurrence of #1065022 in the future.
 If at some point in the future we have another transition as extensive
 as time64, then libglib2.0-0t64 could conceivably be replaced by some
 other package, for example libglib2.0-0xyz. If that happens,
 we need to avoid deletion of gschemas.compiled and giomodule.cache,
 otherwise we will have another bug similar to #1065022.
   * d/tests/1065022-futureproofing: Add a test for recurrence of #1065022.
 This test-case depends on several implementation details which
 might cause it to regress for reasons that are not genuinely
 release-critical, so it is marked as flaky.
   * d/libglib2.0-0t64.postinst: Remove workarounds that are no longer needed.
 As noted in their comments, now that Debian 12 and Ubuntu 22.04 were
 both released with these workarounds included, the workarounds can safely
 be removed from newer distro branches.
   * d/control: libglib2.0-dev Suggests gir1.2-glib-2.0-dev in preference
 to libgirepository1.0-dev, for multi-arch co-installability.
   * Fix filename of README.Debian for libglib2.0-0t64.
 This regressed during the t64 transition, presumably renamed with the
 help of a script that didn't take multiple extensions into account.
Checksums-Sha1:
 95ff673e0e875d5e6e19cd0937c491021d75835c 3765 glib2.0_2.78.4-3.dsc
 81121d5a8a8d5bc74ded000ab034a41caad1c1d3 123424 glib2.0_2.78.4-3.debian.tar.xz
 6869bb3c70ded6ee994ce23b1c398f9d2c9794fd 7494 glib2.0_2.78.4-3_source.buildinfo
Checksums-Sha256:
 6c6dd2ba30deefd46c8b5a28beb1f4fc41ab8b68690c5e161705d042bbf4f156 3765 
glib2.0_2.78.4-3.dsc
 72361967d7

Bug#1065371: unable to disable bug-implicit-func for time64

Hi!

On Sun, 2024-03-03 at 16:46:33 +0100, Guillem Jover wrote:
> On Sun, 2024-03-03 at 16:11:36 +0100, Matthias Klose wrote:
> >  - please provide an opt-out option.
> 
> This is a bug, which I should fix.

The first attached patch is what I'd use to fix this.

> >  - turn it on on all architectures, so that everbody
> >can reproduce the effects.
> 
> I'd be fine with that.

The second attached patch is what I'd use to implement this, if
there's agreement. (Barring manual page updates here.)

I'll wait for Steve's input, before proceeding, otherwise I might just
upload the first patch for now, either later today or tomorrow, so that
people can opt-out of this until there's agreement on how to proceed.
(Even though I guess people could already use DEB_CFLAGS_MAINT_STRIP to
forcibly disable the -Werror=implicit-function-declaration flag.)

Thanks,
Guillem
From f747a38746cbf0fa4279e773835b7d872c0d313c Mon Sep 17 00:00:00 2001
From: Guillem Jover 
Date: Sun, 3 Mar 2024 18:42:34 +0100
Subject: [PATCH] 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
---
 scripts/Dpkg/Vendor/Debian.pm | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/scripts/Dpkg/Vendor/Debian.pm b/scripts/Dpkg/Vendor/Debian.pm
index fcf5b1e2a..ad727d2cf 100644
--- a/scripts/Dpkg/Vendor/Debian.pm
+++ b/scripts/Dpkg/Vendor/Debian.pm
@@ -299,8 +299,8 @@ sub set_build_features {
 $use_feature{abi}{lfs} = 1 if $libc eq 'gnu';
 
 # Require -Werror=implicit-function-declaration, to avoid linking
-# against the wrong symbol.
-$use_feature{qa}{'bug-implicit-func'} = 1;
+# against the wrong symbol, unless it has been set explicitly.
+$use_feature{qa}{'bug-implicit-func'} //= 1;
 }
 
 # XXX: Handle lfs alias from future abi feature area.
-- 
2.43.0

From 87702728876e96891d02df2d1b0419f709939190 Mon Sep 17 00:00:00 2001
From: Guillem Jover 
Date: Sun, 3 Mar 2024 18:53:12 +0100
Subject: [PATCH] Dpkg::Vendor::Debian: Unconditionally set qa
 bug-implicit-func

For the time64 default change, we conditionally enabled
bug-implicit-func to avoid silent ABI breakage due to implicit function
declarations that end up using the time32 symbols, but that is causing
confusion as the effects are not visible on the most commonly used
architectures. Instead enable this globally, unless the maintainer has
specified otherwise.
---
 scripts/Dpkg/Vendor/Debian.pm | 15 +--
 1 file changed, 9 insertions(+), 6 deletions(-)

diff --git a/scripts/Dpkg/Vendor/Debian.pm b/scripts/Dpkg/Vendor/Debian.pm
index ad727d2cf..b3be69e86 100644
--- a/scripts/Dpkg/Vendor/Debian.pm
+++ b/scripts/Dpkg/Vendor/Debian.pm
@@ -117,7 +117,7 @@ sub set_build_features {
 time64 => undef,
 },
 qa => {
-bug => 0,
+bug => undef,
 'bug-implicit-func' => undef,
 canary => 0,
 },
@@ -297,10 +297,6 @@ sub set_build_features {
 if ($use_feature{abi}{time64} && ! $builtin_feature{abi}{time64}) {
 # On glibc 64-bit time_t support requires LFS.
 $use_feature{abi}{lfs} = 1 if $libc eq 'gnu';
-
-# Require -Werror=implicit-function-declaration, to avoid linking
-# against the wrong symbol, unless it has been set explicitly.
-$use_feature{qa}{'bug-implicit-func'} //= 1;
 }
 
 # XXX: Handle lfs alias from future abi feature area.
@@ -311,7 +307,14 @@ sub set_build_features {
 
 ## Area: qa
 
-$use_feature{qa}{'bug-implicit-func'} //= $use_feature{qa}{bug};
+# For time64 we require -Werror=implicit-function-declaration, to avoid
+# linking against the wrong symbol. Instead of enabling this conditionally
+# on time64 being enabled, do it unconditionally so that the effects are
+# uniform and visible on all architectures. Unless it has been set
+# explicitly.
+$use_feature{qa}{'bug-implicit-func'} //= $use_feature{qa}{bug} // 1;
+
+$use_feature{qa}{bug} //= 0;
 
 ## Area: reproducible
 
-- 
2.43.0

Bug#1065380: ausweisapp2 FTBFS with pcsc-lite 2.0.2

2024-03-03 Thread Ludovic Rousseau


Le 03/03/2024 à 17:13, Adrian Bunk a écrit :

Source: ausweisapp2
Version: 2.0.3-1
Severity: serious
Tags: ftbfs
X-Debbugs-Cc: Ludovic Rousseau 

https://buildd.debian.org/status/logs.php?pkg=ausweisapp2&ver=2.1.0-1

...
/<>/src/card/pcsc/PcscUtils.h:112:46: error: 
‘SCARD_E_UNKNOWN_RES_MNG’ was not declared in this scope; did you mean 
‘SCARD_E_UNKNOWN_RES_MSG’?
   112 | Scard_E_Unknown_Res_Mng = returnCode(SCARD_E_UNKNOWN_RES_MNG),
 /**< An unrecognized error code was returned from a layered component. */
   |  ^~~
...


This is not a regression in the new ausweisapp2 upload,
but due to a change in pcsc-lite 2.0.2 (maintainer Cc'ed):

https://salsa.debian.org/rousseau/PCSC/-/commit/65f9b610138c8a4a5563d0332120f684682e0237
"Fix typo in (unused) error code SCARD_E_UNKNOWN_RES_MSG"


Exact.

I now discover that Windows does define BOTH values:
SCARD_E_UNKNOWN_RES_MSG 0x8010002B in 
https://learn.microsoft.com/en-us/openspecs/windows_protocols/ms-rdpesc/9861f8da-76fe-41e6-847e-40c9aa35df8d
SCARD_E_UNKNOWN_RES_MNG 0x8010002B in 
https://learn.microsoft.com/en-us/windows/win32/secauthn/authentication-return-values

I guess pcsc-lite will also have to define both values.
I will release a new pcsc-lite version soon.

Sorry.

--
Dr. Ludovic Rousseau

Bug#1065388: libqt5core5t64: control files are wrong for all t64 qt libraries

2024-03-03 Thread Eric Valette

Package: libqt5core5t64
Version: 5.15.10+dfsg-7.1
Severity: grave
Justification: renders package unusable

Package: libqt5core5t64
Source: qtbase-opensource-src
Version: 5.15.10+dfsg-7.1
Architecture: amd64
Maintainer: Debian Qt/KDE Maintainers 
Installed-Size: 6061
Depends: shared-mime-info, libc6 (>= 2.35), libdouble-conversion3 (>= 2.0.0), 
libgcc-s1 (>= 3.4), libglib2.0-0t64 (>= 2.22.0), libicu72 (>= 72.1~rc-1~), 
libpcre2-16-0 (>= 10.22), libstdc++6 (>= 11), libzstd1 (>= 1.5.5), zlib1g (>= 
1:1.1.4)
Recommends: qttranslations5-l10n
Suggests: libthai0
Breaks: libqt5core5a (<< 5.15.10+dfsg-7.1)
Replaces: libqt5core5a
Provides: libqt5core5a (= 5.15.10+dfsg-7.1), qtbase-abi-5-15-10
Section: libs
Priority: optional
Multi-Arch: same
Homepage: https://www.qt.io/developers/
Description: Qt 5 core module
 Qt is a cross-platform C++ application framework. Qt's primary feature
 is its rich set of widgets that provide standard GUI functionality.
 .
 The QtCore module contains core non-GUI functionality.


The Breaks: makes apt to search for a  libqt5core5a >=  5.15.10+dfsg-7.1 but it
will never exist as long as the package is not FIRST replaced by the t64 
version.

Removing the Breaks: make it installable and the provides expose the 
libqt5core5a
as present.

It has been stuck for 5 days already and I do not think this is due to the 
transition
(except many package are uninstalable due to various error in control files).

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

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

Versions of packages libqt5core5t64 depends on:
ii  libc6  2.38-6
ii  libdouble-conversion3  3.3.0-1+b1
ii  libgcc-s1  14-20240221-2.1
ii  libglib2.0-0t642.78.4-2.1+b1
ii  libicu72   72.1-4+b1
ii  libpcre2-16-0  10.42-4+b1
ii  libstdc++6 14-20240221-2.1
ii  libzstd1   1.5.5+dfsg2-2
ii  shared-mime-info   2.4-1
ii  zlib1g 1:1.3.dfsg-3.1

Versions of packages libqt5core5t64 recommends:
ii  qttranslations5-l10n  5.15.10-2

Versions of packages libqt5core5t64 suggests:
ii  libthai0  0.1.29-2

Processed: Re: Bug#1064369: gobject-introspection dropped versioned dependency on python3

Processing control commands:

> severity -1 important
Bug #1064369 [gobject-introspection] gobject-introspection dropped versioned 
dependency on python3
Severity set to 'important' from 'serious'

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

Bug#1064369: gobject-introspection dropped versioned dependency on python3

2024-03-03 Thread Simon McVittie

Control: severity -1 important

On Tue, 20 Feb 2024 at 23:15:09 +0100, Matthias Klose wrote:
> On 20.02.24 22:50, Simon McVittie wrote:
> > If gobject-introspection explicitly depended on gobject-introspection-bin
> > by name (not just via a virtual package), would that help?
> 
> I think that would do it

I will upload this change soon. It is not clear to me why it would be
helpful, but it's also unlikely to cause a problem.

If I am wrong about this and it somehow causes a regression, I will
try to revert it immediately, but I am quite burned-out at the moment
and I have responsibilities outside Debian, so I would appreciate it if
someone else in the team could keep an eye on this package.

> > On Tue, 20 Feb 2024 at 22:15:21 +0100, Matthias Klose wrote:
> > > The package had in the past dependencies of the form
> > > 
> > >python3 (<< 3.12), python3 (>= 3.11~), python3:any
> > > 
> > > the new one just
> > > 
> > >python3:any
> > 
> > The parts that require a specific python3 version are now in the
> > gobject-introspection-bin binary package, which correctly depends on:
> > 
> >  python3 (<< 3.12), python3 (>= 3.11~), python3:any
> > 
> > via dh_python and ${python3:Depends}. The gobject-introspection package
> > no longer contains any binary Python extensions.

I've explained why I believe this arrangement is correct, and therefore I
don't think there is a bug to be resolved here (certainly not a RC bug).
I am sorry if I have failed to understand the point you were making.

If you disagree and still consider there to be a serious bug here,
please describe a test scenario where the wrong thing happening can be
reproduced (either dependencies that permit an incorrect situation to
be installed, or package relationships that cause some other component
like britney or autopkgtest to misbehave), the result you would expect
from that test scenario, and the actual result.

Thanks,
smcv

Bug#1064558: [Pkg-javascript-devel] Bug#1064558: node-leveldown: FTBFS on mips64el: not ok 1397 Error: batch(array) element must be an object and not `null`

2024-03-03 Thread Jérémy Lal

Le dim. 3 mars 2024 à 07:57, Yadd  a écrit :

> On 2/24/24 13:10, Sebastian Ramacher wrote:
> > Source: node-leveldown
> > Version: 5.6.0+dfsg-4
> > Severity: serious
> > Tags: ftbfs
> > Justification: fails to build from source (but built successfully in the
> past)
> > X-Debbugs-Cc: sramac...@debian.org
> >
> >
> https://buildd.debian.org/status/fetch.php?pkg=node-leveldown&arch=mips64el&ver=5.6.0%2Bdfsg-4%2Bb1&stamp=1708632735&raw=0
> >
> > not ok 1397 Error: batch(array) element must be an object and not `null`
> >---
> >  operator: error
> >  stack: |-
> >Error: batch(array) element must be an object and not `null`
> >at AbstractLevelDOWN.batch
> (/usr/share/nodejs/abstract-leveldown/abstract-leveldown.js:163:33)
> >at /<>/test/iterator-recursion-test.js:48:8
> >at
> /usr/share/nodejs/abstract-leveldown/abstract-leveldown.js:41:5
> >...
> >
> > Cheers
>
> Hi Jérémy,
>
> when trying to build on mips64el porterbox, i got this:
>
> make[1]: Entering directory '/home/yadd/node-leveldown'
> node-gyp clean
> node: error while loading shared libraries: libnode.so.108: cannot open
> shared object file: No such file or directory
>

In Sid, I am afraid it has been renamed to libnode108t64 or something like
that.
I'll have a look later today.

Jérémy

Bug#1065371: unable to disable bug-implicit-func for time64

On Sun, 2024-03-03 at 16:57:28 +0100, Matthias Klose wrote:
> On 03.03.24 16:46, Guillem Jover wrote:
> > On Sun, 2024-03-03 at 16:11:36 +0100, Matthias Klose wrote:
> > > I just filed another bug report for bc, together with the one for heimdal.
> > > 
> > > Please turn this off for a while, it's really harmful for the time64
> > > bootstrap.
> > 
> > This was added on request by Steve, to help with the time64 changes.
> > 
> > > When you turn it on again,
> > > 
> > >   - please provide an opt-out option.
> > 
> > This is a bug, which I should fix.
> > 
> > >   - turn it on on all architectures, so that everbody
> > > can reproduce the effects.
> > 
> > I'd be fine with that.
> > 
> > >   - before turning it on again, please do an archive wide
> > > test rebuild and file bug reports for it.
> > 
> > My impression is that this was done as part of the time64 checks? If
> > not, and the consensus is to disable the flag, I'm very unlikely to
> > drive this, and someone else will need to do those rebuilds and post
> > results.
> 
> I can do that, but we will need a stable dpkg version and a dpkg upload
> providing that setting on amd64 without time64 set. Then I'll ask Lucas for
> two test rebuilds (at this stage, that would be testing).

> Doing test rebuilds with time64 enabled on testing doesn't make sense for
> now, and unstable is too unstable.

Hmm, I'm not sure I understand what you are asking here, so let me try
to rephrase, you'd like to see:

  - a dpkg 1.22.6 upload for unstable to the Debian archive with the
bug-implicit-func unconditionally set?
  - a dpkg 1.21.x version out-of-archive with the bug-implicit-func
support  backported and also enabled by default?

For the former you should be able to do that already by setting the
flag to enable via DEB_BUILD_OPTIONS with the version already in sid,
if you don't want time64 then you can also disable that there. The
latter I don't understand, so perhaps I interpreted that incorrectly
from what you said.

> > I think making the opt-out functional might be enough to help with
> > this, and I could upload a fix later today, which would not disarm
> > this safety net for the time64 transition. But at this point I don't
> > mind either way, and if people prefer disabling the warning then I can
> > do that instead.
> 
> at least for heimdal, three people spent several hours looking for the cause
> of the failure. I'm not sure we want these kind of delays for the
> transition.

While that's unfortunate, I think that might be better than silently
letting ABI breakage through due to the missing Werror flag.

Thanks,
Guillem

Processed: Re: Bug#1057562: closed by Debian FTP Masters (reply to Jeremy Bícha ) (Bug#1057562: fixed in gcr4 4.2.0-2)

Processing control commands:

> severity -1 important
Bug #1057562 [src:gcr4] gcr4: FTBFS: failing tests
Severity set to 'important' from 'serious'
> affects -1 src:gcr
Bug #1057562 [src:gcr4] gcr4: FTBFS: failing tests
Added indication that 1057562 affects src:gcr

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

Bug#1057562: closed by Debian FTP Masters (reply to Jeremy Bícha ) (Bug#1057562: fixed in gcr4 4.2.0-2)

2024-03-03 Thread Jeremy Bícha

Control: severity -1 important
Control: affects -1 src:gcr

On Fri, Mar 1, 2024 at 6:36 AM Santiago Vila  wrote:
> > Ignore build test failures on s390x (Closes: #1057562)
>
> This is wrong for several reasons.
>
> - The bug report did not say anything about s390x.

s390x is the only architecture where the flakiness of the gcr:gck /
object build test is severe enough to unreasonably interfere with
timely building of gcr & gcr4.

Debian is full of packages where the build tests and autopkgtests are
flaky enough to be disruptive to someone expecting 100% pass rates.
There is currently no one on the Debian GNOME team with the time to
investigate and properly fix these issues.

The occasional failure is enough to remind us of this issue. I don't
think it's helpful to just disable the test since it may disguise a
real problem that someone can work on once they get sufficiently
annoyed by the issue. Also, it may be important to recognize if the
failure rate for this test on official buildds increases
significantly. The failure rate did increase on s390x but we don't
really treat s390x as a supported Desktop architecture and don't have
capacity to spend much time dealing with s390x.

I am demoting this bug because it is a valid bug, but also not severe
enough to get gcr excluded from Debian Testing.

Thank you,
Jeremy Bícha

Bug#1065380: ausweisapp2 FTBFS with pcsc-lite 2.0.2

2024-03-03 Thread John Paul Adrian Glaubitz

Hi Adrian,

On Sun, 2024-03-03 at 18:13 +0200, Adrian Bunk wrote:
> https://buildd.debian.org/status/logs.php?pkg=ausweisapp2&ver=2.1.0-1
> 
> ...
> /<>/src/card/pcsc/PcscUtils.h:112:46: error: 
> ‘SCARD_E_UNKNOWN_RES_MNG’ was not declared in this scope; did you mean 
> ‘SCARD_E_UNKNOWN_RES_MSG’?
>   112 | Scard_E_Unknown_Res_Mng = 
> returnCode(SCARD_E_UNKNOWN_RES_MNG), /**< An unrecognized error code 
> was returned from a layered component. */
>   |  ^~~
> ...
> 
> 
> This is not a regression in the new ausweisapp2 upload,
> but due to a change in pcsc-lite 2.0.2 (maintainer Cc'ed):
> 
> https://salsa.debian.org/rousseau/PCSC/-/commit/65f9b610138c8a4a5563d0332120f684682e0237
> "Fix typo in (unused) error code SCARD_E_UNKNOWN_RES_MSG"

I've already seen that and also notified upstream. He is also now CC'ed here.

Adrian

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

Bug#1065380: ausweisapp2 FTBFS with pcsc-lite 2.0.2

2024-03-03 Thread Adrian Bunk

Source: ausweisapp2
Version: 2.0.3-1
Severity: serious
Tags: ftbfs
X-Debbugs-Cc: Ludovic Rousseau 

https://buildd.debian.org/status/logs.php?pkg=ausweisapp2&ver=2.1.0-1

...
/<>/src/card/pcsc/PcscUtils.h:112:46: error: 
‘SCARD_E_UNKNOWN_RES_MNG’ was not declared in this scope; did you mean 
‘SCARD_E_UNKNOWN_RES_MSG’?
  112 | Scard_E_Unknown_Res_Mng = returnCode(SCARD_E_UNKNOWN_RES_MNG),  
   /**< An unrecognized error code was returned from a layered component. */
  |  ^~~
...


This is not a regression in the new ausweisapp2 upload,
but due to a change in pcsc-lite 2.0.2 (maintainer Cc'ed):

https://salsa.debian.org/rousseau/PCSC/-/commit/65f9b610138c8a4a5563d0332120f684682e0237
"Fix typo in (unused) error code SCARD_E_UNKNOWN_RES_MSG"

Bug#1062407: liblopsub: NMU diff for 64-bit time_t transition

2024-03-03 Thread Andre Noll

On Fri, Mar 01, 05:37, Steve Langasek wrote:

> Please find attached a final version of this patch for the time_t
> transition.  This patch is being uploaded to unstable.
> 
> Note that this adds a versioned build-dependency on dpkg-dev, to guard
> against accidental backports with a wrong ABI.

Applied. Since the previous version was applied and made public
last month, I've reverted that patch, applied this final version and
squashed the two new commits into one.

Below it what I've just applied. The patch looks different to what
you've sent, but the resulting tree is identical. Please let me know
if you're OK with the commit message.

Thanks
Andre
---
commit b156a0cabd42582e9c430ae4a284f8815746914e
Author: Steve Langasek 
Date:   Sun Mar 3 16:47:53 2024 +0100

debian: Final version of 64-bit time_t transition.

This partially reverts reverts commit b4d4de17a5c8, replacing it with
the version that has been uploaded to unstable.

It adds a versioned build-dependency on dpkg-dev to guard against
accidental backports with a wrong ABI.

Signed-off-by: Andre Noll 

diff --git a/debian/changelog b/debian/changelog
index 44bbaeb..53995e3 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,9 +1,9 @@
-liblopsub (1.0.4-1.1) experimental; urgency=medium
+liblopsub (1.0.4-1.1) unstable; urgency=medium
 
   * Non-maintainer upload.
-  * Rename libraries for 64-bit time_t transition.
+  * Rename libraries for 64-bit time_t transition.  Closes: #1062407
 
- -- Steve Langasek   Thu, 01 Feb 2024 09:30:36 +
+ -- Steve Langasek   Fri, 01 Mar 2024 05:37:06 +
 
 liblopsub (1.0.4-1) unstable; urgency=low
 
diff --git a/debian/control b/debian/control
index fe135b9..f488fe2 100644
--- a/debian/control
+++ b/debian/control
@@ -2,7 +2,7 @@ Source: liblopsub
 Section: libdevel
 Priority: optional
 Maintainer: Andre Noll 
-Build-Depends: m4, flex, debhelper (>= 10.0)
+Build-Depends: dpkg-dev (>= 1.22.5), m4, flex, debhelper (>= 10.0)
 Standards-Version: 4.3.0
 Homepage: http://people.tuebingen.mpg.de/maan/lopsub
 Vcs-Browser: http://git.tuebingen.mpg.de/lopsub.git
diff --git a/debian/liblopsub1t64.install b/debian/liblopsub1t64.install
deleted file mode 100644
index 6234859..000
--- a/debian/liblopsub1t64.install
+++ /dev/null
@@ -1,2 +0,0 @@
-debian/tmp/usr/share/man/man7/*
-debian/tmp/usr/lib/*/liblopsub.so.*
diff --git a/debian/liblopsub1t64.lintian-overrides 
b/debian/liblopsub1t64.lintian-overrides
deleted file mode 100644
index bac78b9..000
--- a/debian/liblopsub1t64.lintian-overrides
+++ /dev/null
@@ -1 +0,0 @@
-liblopsub1t64: package-name-doesnt-match-sonames liblopsub1
-- 
Max Planck Institute for Biology
Max-Planck-Ring 5, 72076 Tübingen, Germany. Phone: (+49) 7071 601 829
http://people.tuebingen.mpg.de/maan/


signature.asc
Description: PGP signature

Bug#1065371: unable to disable bug-implicit-func for time64


[CCing Lucas]

On 03.03.24 16:46, Guillem Jover wrote:

Hi!

On Sun, 2024-03-03 at 16:11:36 +0100, Matthias Klose wrote:

Control: severity -1 serious



I just filed another bug report for bc, together with the one for heimdal.

Please turn this off for a while, it's really harmful for the time64
bootstrap.


This was added on request by Steve, to help with the time64 changes.


When you turn it on again,

  - please provide an opt-out option.


This is a bug, which I should fix.


  - turn it on on all architectures, so that everbody
can reproduce the effects.


I'd be fine with that.


  - before turning it on again, please do an archive wide
test rebuild and file bug reports for it.


My impression is that this was done as part of the time64 checks? If
not, and the consensus is to disable the flag, I'm very unlikely to
drive this, and someone else will need to do those rebuilds and post
results.


I can do that, but we will need a stable dpkg version and a dpkg upload 
providing that setting on amd64 without time64 set. Then I'll ask Lucas 
for two test rebuilds (at this stage, that would be testing).


Doing test rebuilds with time64 enabled on testing doesn't make sense 
for now, and unstable is too unstable.



I think making the opt-out functional might be enough to help with
this, and I could upload a fix later today, which would not disarm
this safety net for the time64 transition. But at this point I don't
mind either way, and if people prefer disabling the warning then I can
do that instead.


at least for heimdal, three people spent several hours looking for the 
cause of the failure. I'm not sure we want these kind of delays for the 
transition.


Matthias

Bug#1065371: unable to disable bug-implicit-func for time64

Hi!

On Sun, 2024-03-03 at 16:11:36 +0100, Matthias Klose wrote:
> Control: severity -1 serious

> I just filed another bug report for bc, together with the one for heimdal.
> 
> Please turn this off for a while, it's really harmful for the time64
> bootstrap.

This was added on request by Steve, to help with the time64 changes.

> When you turn it on again,
> 
>  - please provide an opt-out option.

This is a bug, which I should fix.

>  - turn it on on all architectures, so that everbody
>can reproduce the effects.

I'd be fine with that.

>  - before turning it on again, please do an archive wide
>test rebuild and file bug reports for it.

My impression is that this was done as part of the time64 checks? If
not, and the consensus is to disable the flag, I'm very unlikely to
drive this, and someone else will need to do those rebuilds and post
results.

I think making the opt-out functional might be enough to help with
this, and I could upload a fix later today, which would not disarm
this safety net for the time64 transition. But at this point I don't
mind either way, and if people prefer disabling the warning then I can
do that instead.

Thanks,
Guillem

Bug#1064058: Bug#1050336: Bug#1064058: libxml-stream-perl: TLS/SSL broken with IO-Socket-SSL >= 2.078 when hostname verification is enabled

2024-03-03 Thread gregor herrmann

On Sun, 18 Feb 2024 01:41:20 +0100, gregor herrmann via pkg-perl-maintainers 
wrote:

> If yes, I'm happy to
> - do some BTS manipulation
> - more relevant: get this fix into bookworm for the next point
>   release.

Fixed package uploaded to bookworm right now, and unblock request
filed: #1065376

Cheers,
gregor

-- 
 .''`.  https://info.comodo.priv.at -- Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
   `-   


signature.asc
Description: Digital Signature

Processed: Re: Bug#1065371: Acknowledgement (unable to disable bug-implicit-func for time64)

Processing control commands:

> severity -1 serious
Bug #1065371 [dpkg-dev] unable to disable bug-implicit-func for time64
Severity set to 'serious' from 'important'

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

Bug#1065375: bc fails to build with abi=time64


Package: src:bc
Version: bc 1.07.1-3
Severity: serious
Tags: sid trixie patch

bc fails to build with abi=time64, which turns on 
-Werror=implicit-function-declaration.
  * Avoid -Wimplicit-function-declaration warnings.
 
diff -Nru bc-1.07.1/debian/patches/no-implicit-function-declaration.diff bc-1.07.1/debian/patches/no-implicit-function-declaration.diff
--- bc-1.07.1/debian/patches/no-implicit-function-declaration.diff	1970-01-01 01:00:00.0 +0100
+++ bc-1.07.1/debian/patches/no-implicit-function-declaration.diff	2024-03-03 13:40:56.0 +0100
@@ -0,0 +1,50 @@
+--- a/dc/dc.c
 b/dc/dc.c
+@@ -47,6 +47,7 @@
+ #include 
+ #include "dc.h"
+ #include "dc-proto.h"
++#include "number.h"
+ 
+ #ifndef EXIT_SUCCESS	/* C89  */
+ # define EXIT_SUCCESS	0
+--- a/dc/eval.c
 b/dc/eval.c
+@@ -41,6 +41,7 @@
+ #endif
+ #include "dc.h"
+ #include "dc-proto.h"
++#include "number.h"
+ 
+ typedef enum {DC_FALSE, DC_TRUE} dc_boolean;
+ 
+--- a/dc/misc.c
 b/dc/misc.c
+@@ -47,6 +47,7 @@
+ #include 
+ #include "dc.h"
+ #include "dc-proto.h"
++#include "number.h"
+ 
+ #ifndef EXIT_FAILURE	/* C89  */
+ # define EXIT_FAILURE	1
+--- a/dc/stack.c
 b/dc/stack.c
+@@ -33,6 +33,7 @@
+ #include "dc.h"
+ #include "dc-proto.h"
+ #include "dc-regdef.h"
++#include "number.h"
+ 
+ /* an oft-used error message: */
+ #define Empty_Stack do{	\
+--- a/dc/string.c
 b/dc/string.c
+@@ -45,6 +45,7 @@
+ #endif
+ #include "dc.h"
+ #include "dc-proto.h"
++#include "number.h"
+ 
+ /* here is the completion of the dc_string type: */
+ struct dc_string {
diff -Nru bc-1.07.1/debian/patches/series bc-1.07.1/debian/patches/series
--- bc-1.07.1/debian/patches/series	2019-12-05 20:35:54.0 +0100
+++ bc-1.07.1/debian/patches/series	2024-03-03 13:38:34.0 +0100
@@ -5,3 +5,4 @@
 06_read_dcrc.diff
 07_bc_man.diff
 08_no-make-circular-dependencies.diff
+no-implicit-function-declaration.diff

Processed: Raising severity of rust-gtk bugs

Processing control commands:

> severity -1 serious
Bug #1064373 [src:squeekboard] squeekboard: Depends on obsolete rust-gtk
Severity set to 'serious' from 'important'

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

Processed: Raising severity of rust-gtk bugs

Processing control commands:

> severity -1 serious
Bug #1064375 [src:rust-gtk] rust-gtk: Unmaintained library should not be 
included in Trixie
Severity set to 'serious' from 'normal'

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

Bug#1065258: marked as done (6 packages from starpu-contrib have an undeclared file conflict)

Your message dated Sun, 03 Mar 2024 14:52:05 +
with message-id 
and subject line Bug#1065258: fixed in starpu-contrib 1.4.3+dfsg-5
has caused the Debian Bug report #1065258,
regarding 6 packages from starpu-contrib have an undeclared file conflict
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.)


-- 
1065258: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065258
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: 
libstarpu-contribrm-1.4-1t64,libstarpu-contribfft-1.4-1t64,libstarpu-contribmpi-1.4-3t64,libstarpu-contrib-openmp-llvm-1.4-1t64,libsocl-contrib-1.4-1t64,libstarpu-contrib-1.4-4t64
Version: 1.4.3+dfsg-3
Severity: serious
User: debian...@lists.debian.org
Usertags: fileconflict
Control: affects -1 + libsocl-contrib-1.4-1 libstarpu-contrib-1.4-4 
libstarpu-contrib-openmp-llvm-1.4-1 libstarpu-contribfft-1.4-1 
libstarpu-contribmpi-1.4-3 libstarpu-contribrm-1.4-1

6 packages from starpu-contrib have an undeclared file conflict. This
may result in an unpack error from dpkg.

The files
 * /usr/lib/x86_64-linux-gnu/libsocl-1.4.so.1
 * /usr/lib/x86_64-linux-gnu/libsocl-1.4.so.1.0.1
are contained in the packages
 * libsocl-contrib-1.4-1/1.4.3+dfsg-2 as present in trixie
 * libsocl-contrib-1.4-1t64/1.4.3+dfsg-3 as present in unstable

The files
 * /usr/lib/x86_64-linux-gnu/libstarpu-1.4.so.4
 * /usr/lib/x86_64-linux-gnu/libstarpu-1.4.so.4.0.0
are contained in the packages
 * libstarpu-contrib-1.4-4/1.4.3+dfsg-2 as present in trixie
 * libstarpu-contrib-1.4-4t64/1.4.3+dfsg-3 as present in unstable

The files
 * /usr/lib/x86_64-linux-gnu/libstarpu_openmp_llvm-1.4.so.1
 * /usr/lib/x86_64-linux-gnu/libstarpu_openmp_llvm-1.4.so.1.0.0
are contained in the packages
 * libstarpu-contrib-openmp-llvm-1.4-1/1.4.3+dfsg-2 as present in trixie
 * libstarpu-contrib-openmp-llvm-1.4-1t64/1.4.3+dfsg-3 as present in unstable

The files
 * /usr/lib/x86_64-linux-gnu/libstarpufft-1.4.so.1
 * /usr/lib/x86_64-linux-gnu/libstarpufft-1.4.so.1.0.0
are contained in the packages
 * libstarpu-contribfft-1.4-1/1.4.3+dfsg-2 as present in trixie
 * libstarpu-contribfft-1.4-1t64/1.4.3+dfsg-3 as present in unstable

The files
 * /usr/lib/x86_64-linux-gnu/libstarpumpi-1.4.so.3
 * /usr/lib/x86_64-linux-gnu/libstarpumpi-1.4.so.3.0.0
are contained in the packages
 * libstarpu-contribmpi-1.4-3/1.4.3+dfsg-2 as present in trixie
 * libstarpu-contribmpi-1.4-3t64/1.4.3+dfsg-3 as present in unstable

The files
 * /usr/lib/x86_64-linux-gnu/libstarpurm-1.4.so.1
 * /usr/lib/x86_64-linux-gnu/libstarpurm-1.4.so.1.0.0
are contained in the packages
 * libstarpu-contribrm-1.4-1/1.4.3+dfsg-2 as present in trixie
 * libstarpu-contribrm-1.4-1t64/1.4.3+dfsg-3 as present in unstable

These packages can be unpacked concurrently, because there is no
relevant Replaces or Conflicts relation. Attempting to unpack these
packages concurrently results in an unpack error from dpkg, because none
of the packages installs a diversion for the affected files.

Kind regards

The Debian Usr Merge Analysis Tool

This bug report has been automatically filed with no human intervention.
The source code is available at https://salsa.debian.org/helmutg/dumat.
If the filing is unclear or in error, don't hesitate to contact
hel...@subdivi.de for assistance.
--- End Message ---
--- Begin Message ---
Source: starpu-contrib
Source-Version: 1.4.3+dfsg-5
Done: Samuel Thibault 

We believe that the bug you reported is fixed in the latest version of
starpu-contrib, 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.
Samuel Thibault  (supplier of updated starpu-contrib 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 03 Mar 2024 14:16:23 +0100
Source: starpu-contrib
Binary: libsocl-contrib-1.4-1t64 libsocl-contrib-1.4-1t64-dbgsym 
libstarpu-contrib-1.4-4t64 libstarpu-contrib-1.4-4t64-dbgsym 
libstarpu-contrib-dev libstarpu-contrib-openmp-llvm-1.4-1t64 
libstarpu-contrib-openmp-llvm-1.4-1t64-dbgsym libstarpu-contribfft-1.4-1t64 
libstarpu-contribfft-1.4-1t64-dbgsym libstarpu-contribmpi-1.4-3t64 
libstarpu-contribmpi-1.4-

Bug#1065258: marked as done (6 packages from starpu-contrib have an undeclared file conflict)

Your message dated Sun, 03 Mar 2024 14:50:28 +
with message-id 
and subject line Bug#1065258: fixed in starpu 1.4.3+dfsg-5
has caused the Debian Bug report #1065258,
regarding 6 packages from starpu-contrib have an undeclared file conflict
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.)


-- 
1065258: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065258
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: 
libstarpu-contribrm-1.4-1t64,libstarpu-contribfft-1.4-1t64,libstarpu-contribmpi-1.4-3t64,libstarpu-contrib-openmp-llvm-1.4-1t64,libsocl-contrib-1.4-1t64,libstarpu-contrib-1.4-4t64
Version: 1.4.3+dfsg-3
Severity: serious
User: debian...@lists.debian.org
Usertags: fileconflict
Control: affects -1 + libsocl-contrib-1.4-1 libstarpu-contrib-1.4-4 
libstarpu-contrib-openmp-llvm-1.4-1 libstarpu-contribfft-1.4-1 
libstarpu-contribmpi-1.4-3 libstarpu-contribrm-1.4-1

6 packages from starpu-contrib have an undeclared file conflict. This
may result in an unpack error from dpkg.

The files
 * /usr/lib/x86_64-linux-gnu/libsocl-1.4.so.1
 * /usr/lib/x86_64-linux-gnu/libsocl-1.4.so.1.0.1
are contained in the packages
 * libsocl-contrib-1.4-1/1.4.3+dfsg-2 as present in trixie
 * libsocl-contrib-1.4-1t64/1.4.3+dfsg-3 as present in unstable

The files
 * /usr/lib/x86_64-linux-gnu/libstarpu-1.4.so.4
 * /usr/lib/x86_64-linux-gnu/libstarpu-1.4.so.4.0.0
are contained in the packages
 * libstarpu-contrib-1.4-4/1.4.3+dfsg-2 as present in trixie
 * libstarpu-contrib-1.4-4t64/1.4.3+dfsg-3 as present in unstable

The files
 * /usr/lib/x86_64-linux-gnu/libstarpu_openmp_llvm-1.4.so.1
 * /usr/lib/x86_64-linux-gnu/libstarpu_openmp_llvm-1.4.so.1.0.0
are contained in the packages
 * libstarpu-contrib-openmp-llvm-1.4-1/1.4.3+dfsg-2 as present in trixie
 * libstarpu-contrib-openmp-llvm-1.4-1t64/1.4.3+dfsg-3 as present in unstable

The files
 * /usr/lib/x86_64-linux-gnu/libstarpufft-1.4.so.1
 * /usr/lib/x86_64-linux-gnu/libstarpufft-1.4.so.1.0.0
are contained in the packages
 * libstarpu-contribfft-1.4-1/1.4.3+dfsg-2 as present in trixie
 * libstarpu-contribfft-1.4-1t64/1.4.3+dfsg-3 as present in unstable

The files
 * /usr/lib/x86_64-linux-gnu/libstarpumpi-1.4.so.3
 * /usr/lib/x86_64-linux-gnu/libstarpumpi-1.4.so.3.0.0
are contained in the packages
 * libstarpu-contribmpi-1.4-3/1.4.3+dfsg-2 as present in trixie
 * libstarpu-contribmpi-1.4-3t64/1.4.3+dfsg-3 as present in unstable

The files
 * /usr/lib/x86_64-linux-gnu/libstarpurm-1.4.so.1
 * /usr/lib/x86_64-linux-gnu/libstarpurm-1.4.so.1.0.0
are contained in the packages
 * libstarpu-contribrm-1.4-1/1.4.3+dfsg-2 as present in trixie
 * libstarpu-contribrm-1.4-1t64/1.4.3+dfsg-3 as present in unstable

These packages can be unpacked concurrently, because there is no
relevant Replaces or Conflicts relation. Attempting to unpack these
packages concurrently results in an unpack error from dpkg, because none
of the packages installs a diversion for the affected files.

Kind regards

The Debian Usr Merge Analysis Tool

This bug report has been automatically filed with no human intervention.
The source code is available at https://salsa.debian.org/helmutg/dumat.
If the filing is unclear or in error, don't hesitate to contact
hel...@subdivi.de for assistance.
--- End Message ---
--- Begin Message ---
Source: starpu
Source-Version: 1.4.3+dfsg-5
Done: Samuel Thibault 

We believe that the bug you reported is fixed in the latest version of
starpu, 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.
Samuel Thibault  (supplier of updated starpu package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 03 Mar 2024 14:16:23 +0100
Source: starpu
Architecture: source
Version: 1.4.3+dfsg-5
Distribution: unstable
Urgency: medium
Maintainer: Samuel Thibault 
Changed-By: Samuel Thibault 
Closes: 1065258
Changes:
 starpu (1.4.3+dfsg-5) unstable; urgency=medium
 .
   * control: Fix missing Conflicts against both non-t64 and t64 packages.
   * control: Fix missing Breaks+Replaces for contrib t64 packages.
 Closes: Bug#1065258.
Checksums-Sha1:

Bug#1063484: libuv1: CVE-2024-24806

2024-03-03 Thread Dominique Dumont

On Thu, 29 Feb 2024 21:53:07 +0100 Salvatore Bonaccorso  
wrote:
> libuv1 is as well affected in bullseye and it's still supported. Can
> you have a look as well at this version? 

The same patch (with a refresh) applies to bullseye. I can also prepare an 
upload.

All the best

Processed: found 1063921 in 1.23.90-1, unarchiving 1055136

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

> found 1063921 1.23.90-1
Bug #1063921 [gstreamer1.0-plugins-good] gstreamer1.0-plugins-good has an 
undeclared file conflict
Bug #1063900 [gstreamer1.0-plugins-good] gstreamer1.0-plugins-good: missing 
Breaks+Replaces: gstreamer1.0-plugins-ugly (<< 1.23)
Marked as found in versions gst-plugins-good1.0/1.23.90-1.
Marked as found in versions gst-plugins-good1.0/1.23.90-1.
> unarchive 1055136
Bug #1055136 {Done: Andreas Beckmann } 
[src:nvidia-graphics-drivers] nvidia-graphics-drivers: CVE-2023-31022
Unarchived Bug 1055136
> thanks
Stopping processing here.

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

Bug#1065366: marked as done (python3-stdlib-extensions: uninstallable, depends on unavailable python3:any (>= 3.11.8-1~))

Your message dated Sun, 03 Mar 2024 14:45:41 +
with message-id 
and subject line Bug#1065366: fixed in python3-stdlib-extensions 3.12.2-2
has caused the Debian Bug report #1065366,
regarding python3-stdlib-extensions: uninstallable, depends on unavailable 
python3:any (>= 3.11.8-1~)
to be marked as done.

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

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


-- 
1065366: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065366
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python3-stdlib-extensions
Version: 3.12.2-1
Severity: serious

Dear maintainer,

python3-distutils and python3-lib2to3 version 3.12.2-1 depend on
python3:any (>= 3.11.8-1~). However python3 (provided by
python3-defaults) is only at version 3.11.6-1, making python3-distutils
and python3-lib2to3 uninstallable:

| apt install python3-lib2to3 python3-distutils
| 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:
|  python3-distutils : Depends: python3:any (>= 3.11.8-1~)
|  python3-lib2to3 : Depends: python3:any (>= 3.11.8-1~)
| E: Unable to correct problems, you have held broken packages.

Regards
Aurelien
--- End Message ---
--- Begin Message ---
Source: python3-stdlib-extensions
Source-Version: 3.12.2-2
Done: Matthias Klose 

We believe that the bug you reported is fixed in the latest version of
python3-stdlib-extensions, 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.
Matthias Klose  (supplier of updated python3-stdlib-extensions 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 03 Mar 2024 14:40:26 +0100
Source: python3-stdlib-extensions
Built-For-Profiles: noudeb
Architecture: source
Version: 3.12.2-2
Distribution: unstable
Urgency: medium
Maintainer: Matthias Klose 
Changed-By: Matthias Klose 
Closes: 1065366
Changes:
 python3-stdlib-extensions (3.12.2-2) unstable; urgency=medium
 .
   * Relax python dependencies. Closes: #1065366.
Checksums-Sha1:
 f6d4485b45add410cad62474756c69cc31340a3b 2563 
python3-stdlib-extensions_3.12.2-2.dsc
 870ff733fe889081e1a92b496c5f0758f747c434 29152 
python3-stdlib-extensions_3.12.2-2.debian.tar.xz
 37bce3b9b9f103e5f46142f6addff9a51cc96765 3697 
python3-stdlib-extensions_3.12.2-2_source.buildinfo
Checksums-Sha256:
 cfe9d6b0da91d6ee77aa7407aa58c6bf1a161fa577cd2f8439d32bc74741476f 2563 
python3-stdlib-extensions_3.12.2-2.dsc
 6f7e30069a7e0a4675742016a01388422bd9d4cbb01f771801530aebad031a5c 29152 
python3-stdlib-extensions_3.12.2-2.debian.tar.xz
 89da8be1fabdb4438d41813179f1a751112ef04282336c2ddbaef90787333bc6 3697 
python3-stdlib-extensions_3.12.2-2_source.buildinfo
Files:
 fe798a75a1e6f6b3b0a5ccfa48772504 2563 python optional 
python3-stdlib-extensions_3.12.2-2.dsc
 66cfc3c6073afd77274da119ff508ad4 29152 python optional 
python3-stdlib-extensions_3.12.2-2.debian.tar.xz
 ebfeeffe87ecb2dd32a33da96165aa3d 3697 python optional 
python3-stdlib-extensions_3.12.2-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCgAuFiEE1WVxuIqLuvFAv2PWvX6qYHePpvUFAmXkfiYQHGRva29AZGVi
aWFuLm9yZwAKCRC9fqpgd4+m9cEFEACL/5xzYD7wnhGB/LAZ34EA8ecU16jZ13L1
oSVnP2IwN1sQnnah+uj7JBdF2IwCGPSDXZGuqgrITi8InzIAZHGbLatsnVpzcUrY
PC+sOygchg5mHOmx8EsRaTAYalYZcfcpNhg6c3vR9gUT+oXYRyyb12VNERRIZROj
PkPo8XaDJnPyzmKKuM+WbNJY+5jkNhxRHgTNOzQe5+WuKBUScgNYG+Jjm21OsDXY
exH6JkTHMuOGEscZ6j7SkJtc8iCO4v199dsmsURY2stSzEwqpIWRRiL9EHrgu84R
JBIotCMJT7doGLTzwaLrTQhXNIW37GgKGmYqtf7PhAlWpmRIUSryMMNQgIyDQkVN
Pn9+t7mLujDNKgizMtPwN7mgCxf6eOR8XJCbDma6Hp0MlwZ9/sYNZoQs231xvbAG
g+Be+mamKciAnSTmKI5RDs4akeFgLpt+GULvta7kK/a/tTH9OxOPdlpu8u+8XOSQ
jsElOQywKY6g0LHK277wubBYmVauX7gzpCQAjupOX4irsChYHmoMbwAVnpqZghto
fW8TRv+xY3/AUHuoA4vk7oayVYnopPgKSxTku2ZoDCzZ49EPBXzgLdEEQLsLaxVf
mjVEyaFYnj0auctkEm6EIwydMIL0LjZXh/5QsPCoTkwYt1e

Bug#1065373: fix heimdal build with abi=time64


Package: src:heimdal
Version: 7.8.git20221117.28daf24+dfsg-4
Severity: serious
Tags: sid trixie ftbfs patch

fix heimdal build with abi=time64.  This is just a work-around for a 
configure test not setting LIB_crypt.
diff -Nru heimdal-7.8.git20221117.28daf24+dfsg/debian/changelog heimdal-7.8.git20221117.28daf24+dfsg/debian/changelog
--- heimdal-7.8.git20221117.28daf24+dfsg/debian/changelog	2024-02-29 17:20:07.0 +0100
+++ heimdal-7.8.git20221117.28daf24+dfsg/debian/changelog	2024-03-03 15:31:17.0 +0100
@@ -1,3 +1,10 @@
+heimdal (7.8.git20221117.28daf24+dfsg-4.1ubuntu2) noble; urgency=medium
+
+  * Filter-out -Werror=implicit-function-declaration, unconditionally set
+by abi=time64.
+
+ -- Matthias Klose   Sun, 03 Mar 2024 15:31:17 +0100
+
 heimdal (7.8.git20221117.28daf24+dfsg-4.1ubuntu1) noble; urgency=low
 
   * Merge from Debian unstable. Remaining changes:
diff -Nru heimdal-7.8.git20221117.28daf24+dfsg/debian/rules heimdal-7.8.git20221117.28daf24+dfsg/debian/rules
--- heimdal-7.8.git20221117.28daf24+dfsg/debian/rules	2024-02-28 16:57:12.0 +0100
+++ heimdal-7.8.git20221117.28daf24+dfsg/debian/rules	2024-03-03 15:31:17.0 +0100
@@ -37,7 +37,7 @@
 	dh_auto_test -- -j1
 
 override_dh_auto_configure:
-	./configure $(shell dpkg-buildflags --export=configure) \
+	./configure $(shell dpkg-buildflags --export=configure | sed 's/-Werror=implicit-function-declaration//') \
 	  --disable-silent-rules \
 	  --libexecdir="\$${prefix}/sbin" \
 	  --enable-shared \

Processed: Re: [Pkg-samba-maint] Bug#1065349: libsmbclient0: Actually breaks part of t64 transition

Processing control commands:

> severity -1 important
Bug #1065349 {Done: Michael Tokarev } [libsmbclient0] 
libsmbclient0: Actually breaks part of t64 transition
Severity set to 'important' from 'grave'

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

Bug#1065349: [Pkg-samba-maint] Bug#1065349: libsmbclient0: Actually breaks part of t64 transition

2024-03-03 Thread Michael Tokarev


Control: severity -1 important

03.03.2024 13:21, Eric Valette :

Package: libsmbclient0
Version: 2:4.19.5+dfsg-3
Severity: grave
Justification: renders package unusable


This is wrong, in my opinion.  The effect of this bug on platforms unaffected
by time64_t transition is exactly the same as on platforms affected by the
transition.  That is, on armhf and a few other platforms, *all* relevant 
packages
are being renamed without the compatible Provides, so all reverse-dependencies
has to be rebuilt.  On other platforms though (like amd64), the actual ABI isn't
changed and the rebuild/rename isn't really necessary, the new library provides
exactly the same ABI as the old one.  The fact that the new library does not
have proper Provides: just means it will be fixed a bit later when all reverse
dependencies will be rebuilt, that's all.  In other worlds, the package is
exactly as useful as before, it's just inconvenience which will be fixed soon,
nothing more.

/mjt

Bug#1065349: marked as done (libsmbclient0: Actually breaks part of t64 transition)

Your message dated Sun, 03 Mar 2024 13:37:25 +
with message-id 
and subject line Bug#1065349: fixed in samba 2:4.19.5+dfsg-4
has caused the Debian Bug report #1065349,
regarding libsmbclient0: Actually breaks part of t64 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.)


-- 
1065349: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065349
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libsmbclient0
Version: 2:4.19.5+dfsg-3
Severity: grave
Justification: renders package unusable


the control file should contain:

Provides: libsmbclient (= 2:4.19.5+dfsg-3)

Otherwyse as many package depends on  libsmbclient it cannot be removed and the
replace is not sufficient. I checked how other pachage manage their transitions
and it is done this way.


Here is my manually modified config file.


dpkg -s libsmbclient0 
Package: libsmbclient0
Status: install ok installed
Priority: optional
Section: libs
Installed-Size: 240
Maintainer: Debian Samba Maintainers 
Architecture: amd64
Multi-Arch: same
Source: samba
Version: 2:4.19.5+dfsg-3
Provides: libsmbclient (= 2:4.19.5+dfsg-3)
Depends: samba-libs (= 2:4.19.5+dfsg-3), libbsd0 (>= 0.0), libc6 (>= 2.25), 
libndr3 (>= 2:4.17.2), libtalloc2 (>= 2.4.1~), libtevent0t64 (>= 0.15.0)
Breaks: libsmbclient (<< 2:4.19.5+dfsg-3)
Description: shared library for communication with SMB/CIFS servers
 This package provides a shared library that enables client applications
 to talk to Microsoft Windows and Samba servers using the SMB/CIFS
 protocol.
Homepage: https://www.samba.org


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

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

Versions of packages libsmbclient0 depends on:
ii  libbsd0   0.12.1-1
ii  libc6 2.38-6
ii  libtalloc22.4.2-1
ii  libtevent0t64 0.16.1-2
ii  samba-libs [libndr3]  2:4.19.5+dfsg-3

libsmbclient0 recommends no packages.

libsmbclient0 suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: samba
Source-Version: 2:4.19.5+dfsg-4
Done: Michael Tokarev 

We believe that the bug you reported is fixed in the latest version of
samba, 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.
Michael Tokarev  (supplier of updated samba package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 03 Mar 2024 15:37:16 +0300
Source: samba
Architecture: source
Version: 2:4.19.5+dfsg-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Samba Maintainers 
Changed-By: Michael Tokarev 
Closes: 1063149 1064512 1065349
Changes:
 samba (2:4.19.5+dfsg-4) unstable; urgency=medium
 .
   * stop shipping python3/dist-packages/samba/tests
 (Closes: #1064512, #1063149)
   * add Debian-Specific tag to debian-specific patches
   * d/genshlibs: run dh_makeshlibs on libsmbclient0
 (Closes: #1065349)
Checksums-Sha1:
 b425eecf4a1e5321d568eb375dda05196b29cbfb  samba_4.19.5+dfsg-4.dsc
 5a74c5fb53abd71034cb646016bd1b18d360b551 176836 
samba_4.19.5+dfsg-4.debian.tar.xz
 05fbe0610f5768f68018f073eed6e8f5ddf95e30 6428 
samba_4.19.5+dfsg-4_source.buildinfo
Checksums-Sha256:
 77794c92925013ef8cd4034ca7be3cb4d8d4041d4e7b20aced43f486af6f27fc  
samba_4.19.5+dfsg-4.dsc
 3952280468f3cf442bc0ec651d718ea51dcbf7d6c488f72b3d0b4fedf87f56c8 176836 
samba_4.19.5+dfsg-4.debian.tar.xz
 02be2d4b7cda6a2c1c21f140c3429025fe452d7377ef2596a8de339139e4fa59 6428 
samba_4.19.5+dfsg-4_source.buildinfo
Files:
 5e43ea60d19af5fc44856be4b4c1dbbd  net optional samba_4.19.5+dfsg-4.dsc
 8944c32819903c9c9538ad2e768d415c 176836 net optional 
samba_4.19.5+dfsg-4.debian.tar.xz
 96599b505

Bug#1065366: python3-stdlib-extensions: uninstallable, depends on unavailable python3:any (>= 3.11.8-1~)

2024-03-03 Thread Aurelien Jarno

Source: python3-stdlib-extensions
Version: 3.12.2-1
Severity: serious

Dear maintainer,

python3-distutils and python3-lib2to3 version 3.12.2-1 depend on
python3:any (>= 3.11.8-1~). However python3 (provided by
python3-defaults) is only at version 3.11.6-1, making python3-distutils
and python3-lib2to3 uninstallable:

| apt install python3-lib2to3 python3-distutils
| 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:
|  python3-distutils : Depends: python3:any (>= 3.11.8-1~)
|  python3-lib2to3 : Depends: python3:any (>= 3.11.8-1~)
| E: Unable to correct problems, you have held broken packages.

Regards
Aurelien

Bug#1065258: 6 packages from starpu-contrib have an undeclared file conflict

2024-03-03 Thread Samuel Thibault

Andreas Beckmann, le dim. 03 mars 2024 12:25:23 +0100, a ecrit:
> I only checked one, but it's probably the same for all of them. The
> Breaks+Replaces are not correct, they miss the "contrib" part:
> 
> Package: libstarpu-contribrm-1.4-1t64
> Source: starpu-contrib
> Version: 1.4.3+dfsg-4
> Installed-Size: 92
> Maintainer: Samuel Thibault 
> Architecture: amd64
> Replaces: libstarpurm-1.4-1
>   ^
> Provides: libstarpu-anyrm-1.4-1, libstarpu-contribrm-1.4-1 (= 1.4.3+dfsg-4)
> Depends: libc6 (>= 2.34), libhwloc15 (>= 2.10.0), libstarpu-contrib-1.4-4t64 
> (>= 1.4.3+dfsg)
> Conflicts: libstarpurm-1.4-1t64
> Breaks: libstarpurm-1.4-1 (<< 1.4.3+dfsg-4)
> ^

Ah, indeed, those need to be sed-ed too.

> And probably you should add a Conflicts: libstarpurm-1.4-1, too,
> otherwise pre-t64 libstarpurm-1.4-1 and post-t64 libstarpu-contribrm-1.4-1t64
> will be co-installable, resulting in another potential file conflict.

Indeed.

Thanks for checking,
Samuel

Bug#1063603: marked as done (composer: CVE-2024-24821)

Your message dated Sun, 03 Mar 2024 13:17:47 +
with message-id 
and subject line Bug#1063603: fixed in composer 2.0.9-2+deb11u2
has caused the Debian Bug report #1063603,
regarding composer: CVE-2024-24821
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.)


-- 
1063603: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063603
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: composer
Version: 2.6.6-1
Severity: grave
Tags: security upstream
Justification: user security hole
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerability was published for composer.

CVE-2024-24821[0]:
| Composer is a dependency Manager for the PHP language. In affected
| versions several files within the local working directory are
| included during the invocation of Composer and in the context of the
| executing user. As such, under certain conditions arbitrary code
| execution may lead to local privilege escalation, provide lateral
| user movement or malicious code execution when Composer is invoked
| within a directory with tampered files. All Composer CLI commands
| are affected, including composer.phar's self-update. The following
| scenarios are of high risk: Composer being run with sudo, Pipelines
| which may execute Composer on untrusted projects, Shared
| environments with developers who run Composer individually on the
| same project. This vulnerability has been addressed in versions
| 2.7.0 and 2.2.23. It is advised that the patched versions are
| applied at the earliest convenience. Where not possible, the
| following should be addressed: Remove all sudo composer privileges
| for all users to mitigate root privilege escalation, and avoid
| running Composer within an untrusted directory, or if needed, verify
| that the contents of `vendor/composer/InstalledVersions.php` and
| `vendor/composer/installed.php` do not include untrusted code.  A
| reset can also be done on these files by the following:```sh rm
| vendor/composer/installed.php vendor/composer/InstalledVersions.php
| composer install --no-scripts --no-plugins ```


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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2024-24821
https://www.cve.org/CVERecord?id=CVE-2024-24821
[1] https://github.com/composer/composer/security/advisories/GHSA-7c6p-848j-wh5h
[2] 
https://github.com/composer/composer/commit/64e4eb356b159a30c766cd1ea83450a38dc23bf5

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: composer
Source-Version: 2.0.9-2+deb11u2
Done: David Prévot 

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

Debian distribution maintenance software
pp.
David Prévot  (supplier of updated composer 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: Sun, 18 Feb 2024 09:05:37 +0100
Source: composer
Architecture: source
Version: 2.0.9-2+deb11u2
Distribution: bullseye
Urgency: medium
Maintainer: Debian PHP PEAR Maintainers 
Changed-By: David Prévot 
Closes: 1063603
Changes:
 composer (2.0.9-2+deb11u2) bullseye; urgency=medium
 .
   [ David Prévot ]
   * Force system dependencies loading
   * Import Pcre
 .
   [ Bastien Roucariès ]
   * Merge pull request from GHSA-7c6p-848j-wh5h [CVE-2024-24821]
 (Closes: #1063603)
Checksums-Sha1:
 2979fca50d1d9799d7ae6548c6836210cd686e71 2103 composer_2.0.9-2+deb11u2.dsc
 e8512695578a43d0a718b0ee14fd63cf6cccbcdc 803188 composer_2.0.9.orig.tar.xz
 21d2219c080a851d84c14a3de3aefbbea787931b 29776 
composer_2.0.9-2+deb11u2.debian.tar.xz
 9213d670b570e5a5c5c964e3e710cf0599e435d5 9846 
composer_2.0.9-2+deb11u2_amd64.buildinfo
Checksums-Sha256:
 7252dcba4f933cbc83814686711b1791ba685eb0c2b4c0b22474f3b85dcfbb20 2103 
composer_2.0.9-2+deb11u2.dsc
 8868baee01986b93e2fc88dcd3989af16e228fcc4028561aacfbf5b778eb2216 803188 
composer_2.0.9.orig.tar.xz
 4e5b288820015c37f61aaebd7

Bug#1063603: marked as done (composer: CVE-2024-24821)

Your message dated Sun, 03 Mar 2024 13:17:20 +
with message-id 
and subject line Bug#1063603: fixed in composer 2.5.5-1+deb12u1
has caused the Debian Bug report #1063603,
regarding composer: CVE-2024-24821
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.)


-- 
1063603: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063603
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: composer
Version: 2.6.6-1
Severity: grave
Tags: security upstream
Justification: user security hole
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerability was published for composer.

CVE-2024-24821[0]:
| Composer is a dependency Manager for the PHP language. In affected
| versions several files within the local working directory are
| included during the invocation of Composer and in the context of the
| executing user. As such, under certain conditions arbitrary code
| execution may lead to local privilege escalation, provide lateral
| user movement or malicious code execution when Composer is invoked
| within a directory with tampered files. All Composer CLI commands
| are affected, including composer.phar's self-update. The following
| scenarios are of high risk: Composer being run with sudo, Pipelines
| which may execute Composer on untrusted projects, Shared
| environments with developers who run Composer individually on the
| same project. This vulnerability has been addressed in versions
| 2.7.0 and 2.2.23. It is advised that the patched versions are
| applied at the earliest convenience. Where not possible, the
| following should be addressed: Remove all sudo composer privileges
| for all users to mitigate root privilege escalation, and avoid
| running Composer within an untrusted directory, or if needed, verify
| that the contents of `vendor/composer/InstalledVersions.php` and
| `vendor/composer/installed.php` do not include untrusted code.  A
| reset can also be done on these files by the following:```sh rm
| vendor/composer/installed.php vendor/composer/InstalledVersions.php
| composer install --no-scripts --no-plugins ```


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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2024-24821
https://www.cve.org/CVERecord?id=CVE-2024-24821
[1] https://github.com/composer/composer/security/advisories/GHSA-7c6p-848j-wh5h
[2] 
https://github.com/composer/composer/commit/64e4eb356b159a30c766cd1ea83450a38dc23bf5

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: composer
Source-Version: 2.5.5-1+deb12u1
Done: David Prévot 

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

Debian distribution maintenance software
pp.
David Prévot  (supplier of updated composer 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: Tue, 13 Feb 2024 16:09:38 +0100
Source: composer
Architecture: source
Version: 2.5.5-1+deb12u1
Distribution: bookworm-security
Urgency: medium
Maintainer: Debian PHP PEAR Maintainers 
Changed-By: David Prévot 
Closes: 1063603
Changes:
 composer (2.5.5-1+deb12u1) bookworm-security; urgency=medium
 .
   * Track debian/bookworm
   * Merge pull request from GHSA-7c6p-848j-wh5h [CVE-2024-24821]
 (Closes: #1063603)
   * Force system dependencies loading
Checksums-Sha1:
 f012ca8e256569d786c190bbf5c1b89a125402da 2391 composer_2.5.5-1+deb12u1.dsc
 e2d5b65f92956358abbfc07df002aa9d685097ef 634104 composer_2.5.5.orig.tar.xz
 c51250e2f434e302073739751f845466f7a3526c 18356 
composer_2.5.5-1+deb12u1.debian.tar.xz
 63486043b9013a8991d56e43bcc356d5e7c8b39e 9727 
composer_2.5.5-1+deb12u1_amd64.buildinfo
Checksums-Sha256:
 b253627020d663eff991b4d083dddf078da586e5cc66b1f4f0c6f43ff83fb2bb 2391 
composer_2.5.5-1+deb12u1.dsc
 9d24f477e5a3c1c2ab12c1cf734a0d66d4572740d9edad44e462c5dc60983bce 634104 
composer_2.5.5.orig.tar.xz
 f781e2e4cbcb2545860ab621cb1462c367fd8c3642bcd

Bug#1057447: marked as done (broadcom-sta-dkms: module build fails for Linux 6.X-rcY (only two version components))

Your message dated Sun, 03 Mar 2024 13:19:58 +
with message-id 
and subject line Bug#1057447: fixed in broadcom-sta 6.30.223.271-24
has caused the Debian Bug report #1057447,
regarding broadcom-sta-dkms: module build fails for Linux 6.X-rcY (only two 
version components)
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.)


-- 
1057447: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057447
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: broadcom-sta-dkms
Version: 6.30.223.271-23
Severity: important
Tags: sid trixie

Hi,

broadcom-sta-dkms fails to build a module for Linux 6.6 that was just uploaded
to experimental:

DKMS make.log for broadcom-sta-6.30.223.271 for kernel 6.6-cloud-amd64 (x86_64)
Tue Dec  5 08:33:20 UTC 2023
/bin/sh: 1: [: Illegal number: 6.6-cloud-amd64
/bin/sh: 1: [: Illegal number: 6.6-cloud-amd64
Wireless Extension is the only possible API for this kernel version
Using Wireless Extension API
KBUILD_NOPEDANTIC=1 make -C /lib/modules/6.6-cloud-amd64/build M=`pwd`
make[1]: warning: jobserver unavailable: using -j1.  Add '+' to parent make 
rule.
make[1]: Entering directory '/usr/src/linux-headers-6.6-cloud-amd64'
/bin/sh: 1: [: Illegal number: 6.6-cloud-amd64
/bin/sh: 1: [: Illegal number: 6.6-cloud-amd64
Wireless Extension is the only possible API for this kernel version
Using Wireless Extension API
Kernel architecture is X86_64
  CC [M]  /var/lib/dkms/broadcom-sta/6.30.223.271/build/src/shared/linux_osl.o
  CC [M]  /var/lib/dkms/broadcom-sta/6.30.223.271/build/src/wl/sys/wl_linux.o
In file included from 
/var/lib/dkms/broadcom-sta/6.30.223.271/build/src/wl/sys/wl_linux.c:81:
/var/lib/dkms/broadcom-sta/6.30.223.271/build/src/wl/sys/wl_iw.h:73: warning: 
"isprint" redefined
   73 | #define isprint(c) bcm_isprint(c)
  |
In file included from 
/usr/src/linux-headers-6.6-common/include/linux/string_helpers.h:6,
 from 
/usr/src/linux-headers-6.6-common/include/linux/seq_file.h:7,
 from 
/usr/src/linux-headers-6.6-common/include/linux/seq_file_net.h:5,
 from 
/usr/src/linux-headers-6.6-common/include/net/net_namespace.h:195,
 from 
/usr/src/linux-headers-6.6-common/include/linux/netdevice.h:38,
 from 
/var/lib/dkms/broadcom-sta/6.30.223.271/build/src/include/linuxver.h:69,
 from 
/var/lib/dkms/broadcom-sta/6.30.223.271/build/src/wl/sys/wl_linux.c:27:
/usr/src/linux-headers-6.6-common/include/linux/ctype.h:30: note: this is the 
location of the previous definition
   30 | #define isprint(c)  ((__ismask(c)&(_P|_U|_L|_D|_SP)) != 0)
  |
/var/lib/dkms/broadcom-sta/6.30.223.271/build/src/wl/sys/wl_linux.c: In 
function 'wl_if_setup':
/var/lib/dkms/broadcom-sta/6.30.223.271/build/src/wl/sys/wl_linux.c:486:12: 
error: 'struct net_device' has no member named 'wireless_handlers'
  486 | dev->wireless_handlers = (struct iw_handler_def *) 
&wl_iw_handler_def;
  |^~
make[3]: *** [/usr/src/linux-headers-6.6-common/scripts/Makefile.build:248: 
/var/lib/dkms/broadcom-sta/6.30.223.271/build/src/wl/sys/wl_linux.o] Error 1
make[2]: *** [/usr/src/linux-headers-6.6-common/Makefile:1938: 
/var/lib/dkms/broadcom-sta/6.30.223.271/build] Error 2
make[1]: *** [/usr/src/linux-headers-6.6-common/Makefile:246: __sub-make] Error 
2
make[1]: Leaving directory '/usr/src/linux-headers-6.6-cloud-amd64'
make: *** [Makefile:181: all] Error 2


Andreas
--- End Message ---
--- Begin Message ---
Source: broadcom-sta
Source-Version: 6.30.223.271-24
Done: Eduard Bloch 

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

Debian distribution maintenance software
pp.
Eduard Bloch  (supplier of updated broadcom-sta 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: Sun, 03 Mar 2024 11:02:34 +0100
Source: broadcom-sta
Binary: broadcom-sta-common broadcom-sta-dkms broadcom-sta-source
Architecture: source all
Version: 6.30.223.271-24
Distribution: unstable
Urgency: low
Maintainer: Eduard Bloch 
Changed-B

Bug#1065353: marked as done (librocsparse-doc: missing Breaks+Replaces: librocsparse-dev (<< 5.7.1-3~))

Your message dated Sun, 03 Mar 2024 12:51:14 +
with message-id 
and subject line Bug#1065353: fixed in rocsparse 5.7.1-3~exp2
has caused the Debian Bug report #1065353,
regarding librocsparse-doc: missing Breaks+Replaces: librocsparse-dev (<< 
5.7.1-3~)
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.)


-- 
1065353: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065353
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: librocsparse-doc
Version: 5.7.1-3~exp1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts file-conflict

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'sid' to 'experimental'.
It installed fine in 'sid', then the upgrade to 'experimental' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.
This error may also be triggered by having a predecessor package from
'sid' installed while installing the package from 'experimental'.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces

>From the attached log (scroll to the bottom...):

  Preparing to unpack .../librocsparse-doc_5.7.1-3~exp1_all.deb ...
  Unpacking librocsparse-doc (5.7.1-3~exp1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/librocsparse-doc_5.7.1-3~exp1_all.deb (--unpack):
   trying to overwrite 
'/usr/share/doc/librocsparse-dev/examples/example_axpyi.cpp', which is also in 
package librocsparse-dev 5.7.1-2
  Errors were encountered while processing:
   /var/cache/apt/archives/librocsparse-doc_5.7.1-3~exp1_all.deb

The conflicting files are

usr/share/doc/librocsparse-dev/examples/example_axpyi.cpp
usr/share/doc/librocsparse-dev/examples/example_bsrmm.cpp
usr/share/doc/librocsparse-dev/examples/example_bsrmv.cpp
usr/share/doc/librocsparse-dev/examples/example_bsrsm.cpp
usr/share/doc/librocsparse-dev/examples/example_bsrsv.cpp
usr/share/doc/librocsparse-dev/examples/example_csrgeam.cpp
usr/share/doc/librocsparse-dev/examples/example_csrgemm.cpp
usr/share/doc/librocsparse-dev/examples/example_csrmm.cpp
usr/share/doc/librocsparse-dev/examples/example_csrsm.cpp
usr/share/doc/librocsparse-dev/examples/example_doti.cpp
usr/share/doc/librocsparse-dev/examples/example_gebsrmv.cpp
usr/share/doc/librocsparse-dev/examples/example_gemmi.cpp
usr/share/doc/librocsparse-dev/examples/example_gemvi.cpp
usr/share/doc/librocsparse-dev/examples/example_gthr.cpp
usr/share/doc/librocsparse-dev/examples/example_gthrz.cpp
usr/share/doc/librocsparse-dev/examples/example_handle.cpp
usr/share/doc/librocsparse-dev/examples/example_roti.cpp
usr/share/doc/librocsparse-dev/examples/example_sctr.cpp
usr/share/doc/librocsparse-dev/examples/example_spgemm.cpp


cheers,

Andreas


librocsparse-dev=5.7.1-2_librocsparse-doc=5.7.1-3~exp1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: rocsparse
Source-Version: 5.7.1-3~exp2
Done: Christian Kastner 

We believe that the bug you reported is fixed in the latest version of
rocsparse, 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.
Christian Kastner  (supplier of updated rocsparse package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 03 Mar 2024 12:38:10 +0100
Source: rocsparse
Architecture: source
Version: 5.7.1-3~exp2
Distribution: experimental
Urgency: medium
Maintainer: Debian ROCm Team 
Changed-By: Christian Kastner 
Closes: 1065353
Changes:
 rocsparse (5.7.1-3~exp2) experimental; urgency=medium
 .
   * d/control: Add missing Breaks+Replaces for moved examples.
 They are now part of the -doc package. (Closes: #1065353)
   * autopkgtest: Export dmesg and other info as artifacts
Checksums-Sha1:
 2c8016c8ca1452d90121c5f4c5bf08c21daad552 2916 rocsparse_5.7.1-3~exp2.dsc
 fdaa06b4eedc6c4f5d0bc80a9bf8147e0dea5635 10668 
rocsparse_5.7.1-3~exp2.debian.tar.xz
 ad60ed5b94abb18c4059f6a83a5baeb4db1f0de4 6916 
rocsparse_5.7.1-3~exp2_source.buildinfo
Checksums-Sha256:
 bb87f36c59424c0b0c838c7fe7afd0f89fc55e22a2e0209f00867fa41aa

Bug#1065351: marked as done (librocblas-doc: missing Breaks+Replaces: missing Breaks+Replaces: librocblas-dev (<< 5.5.1+dfsg-5~))

Your message dated Sun, 03 Mar 2024 12:51:01 +
with message-id 
and subject line Bug#1065351: fixed in rocblas 5.5.1+dfsg-5~exp2
has caused the Debian Bug report #1065351,
regarding librocblas-doc: missing Breaks+Replaces: missing Breaks+Replaces: 
librocblas-dev (<< 5.5.1+dfsg-5~)
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.)


-- 
1065351: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065351
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: librocblas-doc
Version: 5.5.1+dfsg-5~exp1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts file-conflict

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'sid' to 'experimental'.
It installed fine in 'sid', then the upgrade to 'experimental' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.
This error may also be triggered by having a predecessor package from
'sid' installed while installing the package from 'experimental'.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces

>From the attached log (scroll to the bottom...):

  Preparing to unpack .../librocblas-doc_5.5.1+dfsg-5~exp1_all.deb ...
  Unpacking librocblas-doc (5.5.1+dfsg-5~exp1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/librocblas-doc_5.5.1+dfsg-5~exp1_all.deb (--unpack):
   trying to overwrite 
'/usr/share/doc/librocblas-dev/examples/example_c_dgeam.c', which is also in 
package librocblas-dev 5.5.1+dfsg-4
  Errors were encountered while processing:
   /var/cache/apt/archives/librocblas-doc_5.5.1+dfsg-5~exp1_all.deb

The conflicting files are

usr/share/doc/librocblas-dev/examples/example_c_dgeam.c
usr/share/doc/librocblas-dev/examples/example_hip_complex_her2.cpp
usr/share/doc/librocblas-dev/examples/example_sgemm_strided_batched.cpp


cheers,

Andreas


librocblas-dev=5.5.1+dfsg-4_librocblas-doc=5.5.1+dfsg-5~exp1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: rocblas
Source-Version: 5.5.1+dfsg-5~exp2
Done: Christian Kastner 

We believe that the bug you reported is fixed in the latest version of
rocblas, 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.
Christian Kastner  (supplier of updated rocblas package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 03 Mar 2024 12:18:28 +0100
Source: rocblas
Architecture: source
Version: 5.5.1+dfsg-5~exp2
Distribution: experimental
Urgency: medium
Maintainer: Debian ROCm Team 
Changed-By: Christian Kastner 
Closes: 1065351
Changes:
 rocblas (5.5.1+dfsg-5~exp2) experimental; urgency=medium
 .
   [ Cordell Bloor ]
   * d/rules: skip rocblas-test in nocheck build profile
   * d/rules: skip building test data in nocheck build profile
 .
   [ Christian Kastner ]
   * d/control: Add missing Breaks+Replaces for moved examples.
 They are now part of the -doc package. (Closes: #1065351)
   * Add lintian override for copyright false positive
Checksums-Sha1:
 40cbb83cc76fd8a3b4cf06f5d3f366b8fec39e7f 3268 rocblas_5.5.1+dfsg-5~exp2.dsc
 0496bfad6487c897d2648b5eea94afeb5ca53fd6 369436 
rocblas_5.5.1+dfsg-5~exp2.debian.tar.xz
 c126f7c9de8e1abbf57fbc291157b65b9191720f 7190 
rocblas_5.5.1+dfsg-5~exp2_source.buildinfo
Checksums-Sha256:
 71d92bdc689a93b0de5d43b1befa78fbccd00957960a2bc75f91791b77b3a79b 3268 
rocblas_5.5.1+dfsg-5~exp2.dsc
 0ca0c7617c760fd06f46d00626cffb6c8acea57f083dee9ad0fe4f44dbdfec30 369436 
rocblas_5.5.1+dfsg-5~exp2.debian.tar.xz
 943d482b4fc6146a0a19f06a91b74d8b2b77cf74d7bc0daaeb89f505cf95b764 7190 
rocblas_5.5.1+dfsg-5~exp2_source.buildinfo
Files:
 555f28385d56ad9f8a2aa9eba60ddd56 3268 devel optional 
rocblas_5.5.1+dfsg-5~exp2.dsc
 72228231520cfeee05702d1c6c05b74f 369436 devel optional 
rocblas_5.5.1+dfsg-5~exp2.debian.tar.xz
 af412c051929ecd3b2c29f831b13b147 7190 devel optional 
rocblas_5.5.1+dfsg-5~exp2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEQZ9+mkfDq5UZ8bCjOZU6N95Os2sFAmXkYGgACgkQOZU6N95O
s2vVdg/+OOEcWaTWSVYvBj/K8

Bug#1061203: gtkmm2.4: upstream branch is end-of life

2024-03-03 Thread Bastian Germann


Am 03.03.24 um 12:17 schrieb Graham Inggs:

I don't believe having a dead upstream is considered Release Critical.


If you do not believe so, please set the severity to what you see fit.

Bug#1054863: haskell-hsyaml: FTBFS: make: *** [/usr/share/cdbs/1/class/hlibrary.mk:153: configure-ghc-stamp] Error 25

2024-03-03 Thread Ilias Tsitsimpis

Hi Jonas,

On Fri, Oct 27, 2023 at 09:50PM, Lucas Nussbaum wrote:
> > Error: hlibrary.setup: Encountered missing or private dependencies:
> > base >=4.5 && <4.17

Can you please update haskell-hsyaml to version 0.2.1.2, which is the
version we are currently tracking on our package-plan? This should also
fix this bug and unblock stylish-haskell.

Thanks,

-- 
Ilias

Bug#1065353: marked as pending in rocsparse

2024-03-03 Thread Christian Kastner

Control: tag -1 pending

Hello,

Bug #1065353 in rocsparse 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/rocm-team/rocsparse/-/commit/328d612af51ece88548bbdd131648c705a993722


d/control: Add missing Breaks+Replaces for moved examples

They are now part of the -doc package.

Closes: #1065353


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1065353

Processed: Bug#1065353 marked as pending in rocsparse

Processing control commands:

> tag -1 pending
Bug #1065353 [librocsparse-doc] librocsparse-doc: missing Breaks+Replaces: 
librocsparse-dev (<< 5.7.1-3~)
Added tag(s) pending.

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

Processed: Bug#1065351 marked as pending in rocblas

Processing control commands:

> tag -1 pending
Bug #1065351 [librocblas-doc] librocblas-doc: missing Breaks+Replaces: missing 
Breaks+Replaces: librocblas-dev (<< 5.5.1+dfsg-5~)
Added tag(s) pending.

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

Bug#1065351: marked as pending in rocblas

2024-03-03 Thread Christian Kastner

Control: tag -1 pending

Hello,

Bug #1065351 in rocblas 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/rocm-team/rocblas/-/commit/10bafdf7949eba57ae124741cba15e25ccb8beee


d/control: Add missing Breaks+Replaces for moved examples

They are now part of the -doc package.

Closes: #1065351


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1065351

Processed: Re: 6 packages from starpu-contrib have an undeclared file conflict

Processing control commands:

> found -1 1.4.3+dfsg-4
Bug #1065258 {Done: Samuel Thibault } 
[libstarpu-contribrm-1.4-1t64,libstarpu-contribfft-1.4-1t64,libstarpu-contribmpi-1.4-3t64,libstarpu-contrib-openmp-llvm-1.4-1t64,libsocl-contrib-1.4-1t64,libstarpu-contrib-1.4-4t64]
 6 packages from starpu-contrib have an undeclared file conflict
Marked as found in versions starpu-contrib/1.4.3+dfsg-4; no longer marked as 
fixed in versions starpu-contrib/1.4.3+dfsg-4 and reopened.

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

Bug#1065258: 6 packages from starpu-contrib have an undeclared file conflict

2024-03-03 Thread Andreas Beckmann

Followup-For: Bug #1065258
Control: found -1 1.4.3+dfsg-4

I only checked one, but it's probably the same for all of them. The
Breaks+Replaces are not correct, they miss the "contrib" part:

Package: libstarpu-contribrm-1.4-1t64
Source: starpu-contrib
Version: 1.4.3+dfsg-4
Installed-Size: 92
Maintainer: Samuel Thibault 
Architecture: amd64
Replaces: libstarpurm-1.4-1
  ^
Provides: libstarpu-anyrm-1.4-1, libstarpu-contribrm-1.4-1 (= 1.4.3+dfsg-4)
Depends: libc6 (>= 2.34), libhwloc15 (>= 2.10.0), libstarpu-contrib-1.4-4t64 
(>= 1.4.3+dfsg)
Conflicts: libstarpurm-1.4-1t64
Breaks: libstarpurm-1.4-1 (<< 1.4.3+dfsg-4)
^

And probably you should add a Conflicts: libstarpurm-1.4-1, too,
otherwise pre-t64 libstarpurm-1.4-1 and post-t64 libstarpu-contribrm-1.4-1t64
will be co-installable, resulting in another potential file conflict.


Andreas

Bug#1061203: gtkmm2.4: upstream branch is end-of life

2024-03-03 Thread Graham Inggs

Hi Bastian

In what capacity are you setting the severity of this bug?

As far as I can tell, you are neither a maintainer of this package nor
a member of the release team.

I don't believe having a dead upstream is considered Release Critical.

Regards
Graham

Bug#1065353: librocsparse-doc: missing Breaks+Replaces: librocsparse-dev (<< 5.7.1-3~)

2024-03-03 Thread Andreas Beckmann

Package: librocsparse-doc
Version: 5.7.1-3~exp1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts file-conflict

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'sid' to 'experimental'.
It installed fine in 'sid', then the upgrade to 'experimental' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.
This error may also be triggered by having a predecessor package from
'sid' installed while installing the package from 'experimental'.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces

>From the attached log (scroll to the bottom...):

  Preparing to unpack .../librocsparse-doc_5.7.1-3~exp1_all.deb ...
  Unpacking librocsparse-doc (5.7.1-3~exp1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/librocsparse-doc_5.7.1-3~exp1_all.deb (--unpack):
   trying to overwrite 
'/usr/share/doc/librocsparse-dev/examples/example_axpyi.cpp', which is also in 
package librocsparse-dev 5.7.1-2
  Errors were encountered while processing:
   /var/cache/apt/archives/librocsparse-doc_5.7.1-3~exp1_all.deb

The conflicting files are

usr/share/doc/librocsparse-dev/examples/example_axpyi.cpp
usr/share/doc/librocsparse-dev/examples/example_bsrmm.cpp
usr/share/doc/librocsparse-dev/examples/example_bsrmv.cpp
usr/share/doc/librocsparse-dev/examples/example_bsrsm.cpp
usr/share/doc/librocsparse-dev/examples/example_bsrsv.cpp
usr/share/doc/librocsparse-dev/examples/example_csrgeam.cpp
usr/share/doc/librocsparse-dev/examples/example_csrgemm.cpp
usr/share/doc/librocsparse-dev/examples/example_csrmm.cpp
usr/share/doc/librocsparse-dev/examples/example_csrsm.cpp
usr/share/doc/librocsparse-dev/examples/example_doti.cpp
usr/share/doc/librocsparse-dev/examples/example_gebsrmv.cpp
usr/share/doc/librocsparse-dev/examples/example_gemmi.cpp
usr/share/doc/librocsparse-dev/examples/example_gemvi.cpp
usr/share/doc/librocsparse-dev/examples/example_gthr.cpp
usr/share/doc/librocsparse-dev/examples/example_gthrz.cpp
usr/share/doc/librocsparse-dev/examples/example_handle.cpp
usr/share/doc/librocsparse-dev/examples/example_roti.cpp
usr/share/doc/librocsparse-dev/examples/example_sctr.cpp
usr/share/doc/librocsparse-dev/examples/example_spgemm.cpp


cheers,

Andreas


librocsparse-dev=5.7.1-2_librocsparse-doc=5.7.1-3~exp1.log.gz
Description: application/gzip

Bug#1002148: re: qwertone: FTBFS: unsatisfiable build-dependencies

2024-03-03 Thread Andrej Shadura

On Thu, 30 Dec 2021 07:42:09 + plugwash 
 wrote:
The rust gtk stack is now installable again, but it looks like qwertone 
needs some work to build with

the new version of the stack.

It looks like upstream has updated the code for 0.14 but attempting to 
grab the upstream commit and
apply it as a patch resulted in a bunch of hunks failling, so it may be 
better to just update to a new

upstream version.


FYI I’m working on a fix to this bug.

--
Cheers,
  Andrej

Bug#1065351: librocblas-doc: missing Breaks+Replaces: missing Breaks+Replaces: librocblas-dev (<< 5.5.1+dfsg-5~)

2024-03-03 Thread Andreas Beckmann

Package: librocblas-doc
Version: 5.5.1+dfsg-5~exp1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts file-conflict

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'sid' to 'experimental'.
It installed fine in 'sid', then the upgrade to 'experimental' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.
This error may also be triggered by having a predecessor package from
'sid' installed while installing the package from 'experimental'.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces

>From the attached log (scroll to the bottom...):

  Preparing to unpack .../librocblas-doc_5.5.1+dfsg-5~exp1_all.deb ...
  Unpacking librocblas-doc (5.5.1+dfsg-5~exp1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/librocblas-doc_5.5.1+dfsg-5~exp1_all.deb (--unpack):
   trying to overwrite 
'/usr/share/doc/librocblas-dev/examples/example_c_dgeam.c', which is also in 
package librocblas-dev 5.5.1+dfsg-4
  Errors were encountered while processing:
   /var/cache/apt/archives/librocblas-doc_5.5.1+dfsg-5~exp1_all.deb

The conflicting files are

usr/share/doc/librocblas-dev/examples/example_c_dgeam.c
usr/share/doc/librocblas-dev/examples/example_hip_complex_her2.cpp
usr/share/doc/librocblas-dev/examples/example_sgemm_strided_batched.cpp


cheers,

Andreas


librocblas-dev=5.5.1+dfsg-4_librocblas-doc=5.5.1+dfsg-5~exp1.log.gz
Description: application/gzip

Bug#1065349: libsmbclient0: Actually breaks part of t64 transition

2024-03-03 Thread Eric Valette

Package: libsmbclient0
Version: 2:4.19.5+dfsg-3
Severity: grave
Justification: renders package unusable


the control file should contain:

Provides: libsmbclient (= 2:4.19.5+dfsg-3)

Otherwyse as many package depends on  libsmbclient it cannot be removed and the
replace is not sufficient. I checked how other pachage manage their transitions
and it is done this way.


Here is my manually modified config file.


dpkg -s libsmbclient0 
Package: libsmbclient0
Status: install ok installed
Priority: optional
Section: libs
Installed-Size: 240
Maintainer: Debian Samba Maintainers 
Architecture: amd64
Multi-Arch: same
Source: samba
Version: 2:4.19.5+dfsg-3
Provides: libsmbclient (= 2:4.19.5+dfsg-3)
Depends: samba-libs (= 2:4.19.5+dfsg-3), libbsd0 (>= 0.0), libc6 (>= 2.25), 
libndr3 (>= 2:4.17.2), libtalloc2 (>= 2.4.1~), libtevent0t64 (>= 0.15.0)
Breaks: libsmbclient (<< 2:4.19.5+dfsg-3)
Description: shared library for communication with SMB/CIFS servers
 This package provides a shared library that enables client applications
 to talk to Microsoft Windows and Samba servers using the SMB/CIFS
 protocol.
Homepage: https://www.samba.org


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

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

Versions of packages libsmbclient0 depends on:
ii  libbsd0   0.12.1-1
ii  libc6 2.38-6
ii  libtalloc22.4.2-1
ii  libtevent0t64 0.16.1-2
ii  samba-libs [libndr3]  2:4.19.5+dfsg-3

libsmbclient0 recommends no packages.

libsmbclient0 suggests no packages.

-- no debconf information

Bug#1065125: libchipcard8 has an undeclared file conflict

2024-03-03 Thread nicklaus . th

Hallo Michael,
ich habe aktuell Debian gar nicht mehr im Einsatz und nutze auch gnucash
nicht mehr. Ich bekomme jedoch noch die E-Mails über die changes. Kannst
du mich aus dem E-Mail Verteiler wieder austragen bitte?

Beste Grüße, Thorsten

Am 01.03.2024 22:38 schrieb Micha Lenk:

Hi Helmut,

thank you for reporting this issue.
Am 29.02.24 um 23:45 schrieb Helmut Grohne:

This actually is fallout from the time64 transition. Both
libchipcard6
and libchipcard8 declared "Provides: libgwenhywfar79-plugins-ct" and
"Conflicts: libgwenhywfar79-plugins-ct". However, libchipcard6t64
has
changed this to libgwenhywfar-plugins-ct. The change in virtual
facility
causes the conflicts to no longer take effect. Hence filing this
with
libchipcard6t64 rather than libchipcard8.

The Provides/Conflicts accidentally changing from
libgwenhywfar79-plugins-ct to libgwenhywfar-plugins-ct is caused by
some custom substvars generation done by the script
debian/update_substvars.sh, which writes the variable to a package
specific substvars file debian/libchipcard6.substvar. The package
rename caused this substvar defined in that file to be lost.

I think I've found a fix for it:

https://salsa.debian.org/aqbanking-team/pkg-libchipcard/-/commit/045b1f498f1a2620e4b7c9538497ae54e18b
[1]

I currently have no capacity for testing it right away, so feel free
to prepare another 0-day-NMU to fix this RC bug quicker than I can.

Best regards,
Micha

Links:
--
[1]
https://salsa.debian.org/aqbanking-team/pkg-libchipcard/-/commit/045b1f498f1a2620e4b7c9538497ae54e18b

Bug#1065129: marked as done (python3.11: recent libc6-dev change causes NIS support to be dropped)

Your message dated Sun, 03 Mar 2024 10:06:35 +
with message-id 
and subject line Bug#1065129: fixed in python3.11 3.11.8-3
has caused the Debian Bug report #1065129,
regarding python3.11: recent libc6-dev change causes NIS 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.)


-- 
1065129: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065129
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python3.11
Version: 3.11.13-1
Severity: serious
User: debian-gl...@lists.debian.org
Usertags: libnsl-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 has been added to the libc6-dev package.

This dependency has been temporarily dropped in the 2.37-15.1 NMU, as
part of the 64-bit time_t transition. This causes python3.11 to be built
without NIS support, which in practice means that this python module is
missing from libpython3.11-stdlib:
/usr/lib/python3.11/lib-dynload/nis.cpython-311-x86_64-linux-gnu.so

Please either:
- Add libnsl-dev as build dependency
- Disable NIS support explicitly 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: python3.11
Source-Version: 3.11.8-3
Done: Matthias Klose 

We believe that the bug you reported is fixed in the latest version of
python3.11, 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.
Matthias Klose  (supplier of updated python3.11 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 03 Mar 2024 10:23:40 +0100
Source: python3.11
Architecture: source
Version: 3.11.8-3
Distribution: unstable
Urgency: medium
Maintainer: Matthias Klose 
Changed-By: Matthias Klose 
Closes: 1065129 1065164
Changes:
 python3.11 (3.11.8-3) unstable; urgency=medium
 .
   [ Stefano Rivera ]
   * Build-Depend on libnsl-dev for NIS support. Closes: #1065129.
 .
   [ Matthias Klose ]
   * Fix package names in PVER-dbg maintainer scripts. Closes: #1065164.
   * Really build without LTO when requested.
   * Disable LTO builds and testsuite for now (mesa t64 transition ...).
Checksums-Sha1:
 ec200d999bff751f85dd9d187b218cdea05e6eba 3749 python3.11_3.11.8-3.dsc
 d04ab2eb71220e80e7acd2612ae64b61195c4f33 214060 
python3.11_3.11.8-3.debian.tar.xz
 407c93af14f0c260c026f236f21d958f693f68da 7722 
python3.11_3.11.8-3_source.buildinfo
Checksums-Sha256:
 755895e1d7f81e500ae15784a6af3401364a74a6746350a0e6e866dbccbf0916 3749 
python3.11_3.11.8-3.dsc
 92e1f3e06398e80bf3a4714f81324901f99fa610e2581db368fa422380d83fae 214060 
python3.11_3.11.8-3.debian.tar.xz
 eebabb5a525f62507620b9faa7cb523165ddeab924d79dc6ebcc73eae021fc8b 7722 
python3.11_3.11.8-3_source.buildinfo
Files:
 5d71e88d60cb39d9ad9a50325ddbc59c 3749 python optional python3.11_3.11.8-3.dsc
 091fc83546a2f396f8d8cd528793bb7f 214060 python optional 
python3.11_3.11.8-3.debian.tar.xz
 889c43d6e4813ce0ac481aec234153a4 7722 python optional 
python3.11_3.11.8-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCgAuFiEE1WVxuIqLuvFAv2PWvX6qYHePpvUFAmXkRnsQHGRva29AZGVi
aWFuLm9yZwAKCRC9fqpgd4+m9Wt8D/9ANBfL2sviRuzsJzv7rcuxW+Ps9NPZEGtv
VxKj4RDJeuiZwM/9O8NQz/AihthAO7uXP8Y08B1/w/nZLlalP9QeX97+bR6u4+Nl
/+xDmgVX/7WncVvnc5Ee5rbXTu+Eme2YBhWjyuk2gimUDRNXwpMG9wYRhv1mS36R
nWOIsMU3CP52dJdfT2VxtSYv6D+wFUH3B0DhQaPFA9ptgUDq6nUQHcNCo0cyNjpA
uWU8/t9i6/izgaQpKMSxR80JkgYNAPNpAsrzBAqJRd3n+WCIu5kiummaFLzTenbl
hjSjPzQoQs7p9pmDbV2FLL2OnqD4Ipj2mgvXtH1XNooPVWfAAn5rFnzklB81kpc9
A9/xXHRlv3fZXHsnWOtiY9gzos3uJSUF2njciG58G8Vce5TzcnJwGZ1m8D708pmS
C+s5ONHs87SHfqFy/QzdBFdIJ5y9nxhUMFUln+6gwmeEeq6yMD1KedvYX5TNYLES
UlXZtlUY6zz9g21/61WRXrYjDjqjXcSzeGuKxZXOWteX0b7WAd5mv3dwMJZph+Yn
0MkmNC2AZi8ZesKWGXke0vLQhdSdOLBg0rdkP45Nv30pbfZx7DP0ije0J9ceuq2t
JDPfQgbCVX3acQxTFqW676dtXAH7FGlajPV5drpGbYb61Iy4B3Ya63yzRPbvPaUM
oVcBt9bZ3A==
=tx0m
-END

Bug#1065128: marked as done (python3.12: recent libc6-dev change causes NIS support to be dropped)

Your message dated Sun, 03 Mar 2024 10:07:12 +
with message-id 
and subject line Bug#1065128: fixed in python3.12 3.12.2-4
has caused the Debian Bug report #1065128,
regarding python3.12: recent libc6-dev change causes NIS 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.)


-- 
1065128: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065128
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python3.12
Version: 3.12.13-1
Severity: serious
User: debian-gl...@lists.debian.org
Usertags: libnsl-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 has been added to the libc6-dev package.

This dependency has been temporarily dropped in the 2.37-15.1 NMU, as
part of the 64-bit time_t transition. This causes python3.12 to be built
without NIS support, which in practice means that this python module is
missing from libpython3.12-stdlib:
/usr/lib/python3.12/lib-dynload/nis.cpython-312-x86_64-linux-gnu.so

Please either:
- Add libnsl-dev as build dependency
- Disable NIS support explicitly 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: python3.12
Source-Version: 3.12.2-4
Done: Matthias Klose 

We believe that the bug you reported is fixed in the latest version of
python3.12, 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.
Matthias Klose  (supplier of updated python3.12 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 03 Mar 2024 10:11:00 +0100
Source: python3.12
Architecture: source
Version: 3.12.2-4
Distribution: unstable
Urgency: medium
Maintainer: Matthias Klose 
Changed-By: Matthias Klose 
Closes: 1065128
Changes:
 python3.12 (3.12.2-4) unstable; urgency=medium
 .
   [ Stefano Rivera ]
   * Build-Depend on libnsl-dev for NIS support. Closes: #1065128.
 .
   [ Matthias Klose ]
   * Fix override files for renamed t64 packages.
   * Fix package names in PVER-dbg maintainer scripts. Addresses: #1065164.
   * Really build without LTO when requested.
   * Disable LTO builds and testsuite for now (mesa t64 transition ...).
Checksums-Sha1:
 29375967972478afb5f1193917653ef1a52a4e9c 3780 python3.12_3.12.2-4.dsc
 b473622363e88a7b51cb911f393f80fba033b421 212460 
python3.12_3.12.2-4.debian.tar.xz
 7f1ba1382ddb30f1bd3c3f210b710c4c4d42a77b 7722 
python3.12_3.12.2-4_source.buildinfo
Checksums-Sha256:
 f1800fe02d245796fc45aad222b87d6f6cba9915bd58de2eacd905b0856be298 3780 
python3.12_3.12.2-4.dsc
 686c678beb3c01d0e4611b2f6751517f9e24a0f35358ad3de2aaa3c113354a8a 212460 
python3.12_3.12.2-4.debian.tar.xz
 a823bfe1f42546636dd4ffa303315800c04023d24814a6ad80d2882ef1d99594 7722 
python3.12_3.12.2-4_source.buildinfo
Files:
 9bcb604e5743f8bfa03522cd23b50111 3780 python optional python3.12_3.12.2-4.dsc
 11bf7a9d011e049a225f79c2f363b4f5 212460 python optional 
python3.12_3.12.2-4.debian.tar.xz
 782cc3b9a71793585a0d4ce84452db52 7722 python optional 
python3.12_3.12.2-4_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCgAuFiEE1WVxuIqLuvFAv2PWvX6qYHePpvUFAmXkRhUQHGRva29AZGVi
aWFuLm9yZwAKCRC9fqpgd4+m9SwZD/4/WobWA3XLNL6im53qHBGNO/dnl2gMQMv5
OSAuv/gYk4oPqnluT0Cd9tubQMkE9W6nPEbaDfT6/pNOd1IiwoGt9/NZxwUmxhoo
dwmu3LMAw9j2fqnV9lQSG6F5u5PTuN7YeEsODl66H8iXbthihkwf4k6AUPYYhZJO
3FhtL7h7RcuqLv0ycG0UYZtw5K+ZJU51KWMqaKRtTcECvZsv7dl/Fd6xtv0eDYot
z39zX3+1/mnIhFGZTTGu1EChIuHBjrawzdD5v9jnNZF5t00xSKQ3P6EFCJh5daQS
B49fs95egLUBcrwZA8WG4mamXqSh2FfUrZri8WVCY3MxGaOfsInUhwGuCn0DcxZB
MNYriYeJjMK2v7zd0Scel4hfr+3D4bkXhfT2wCzRuhoRd5jVCVSJQOGamznDG9pr
cviR3PGvV3nKwe9bj4LNFdEzV3/z1UUtqTbRawMfoD6+rYSYFXuBySxyvZdTSfMW
ijojTvktpg+bGykSFnwuvFZetD80pM4jbnAgeNz2O8Jutyi45P0C26QNbZCNT6mn
ogb2PA9DpFGMLdi72dSvikxV80hVXH2df7rS62IvW2luVUe8YjsVeaXYb6de+1F7
9O4hATvlvR5nWmCvEg83Tnj3bh7/selkkiu4O8TKdKdw3XG

Bug#1065154: marked as done (libqt5sql5t64 Provides libqt5core5a instead of libqt5sql5)

Your message dated Sun, 03 Mar 2024 09:51:20 +
with message-id 
and subject line Bug#1065154: fixed in qtbase-opensource-src 5.15.10+dfsg-7.2
has caused the Debian Bug report #1065154,
regarding libqt5sql5t64 Provides libqt5core5a instead of libqt5sql5
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.)


-- 
1065154: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065154
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libqt5sql5t64
Version: 5.15.10+dfsg-7.1
Severity: serious
X-Debbugs-Cc: vor...@debian.org

I haven't checked but the same problem may also be present for other
subpackages.


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

Kernel: Linux 6.7-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Source: qtbase-opensource-src
Source-Version: 5.15.10+dfsg-7.2
Done: Steve Langasek 

We believe that the bug you reported is fixed in the latest version of
qtbase-opensource-src, 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 qtbase-opensource-src 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 03 Mar 2024 09:03:16 +
Source: qtbase-opensource-src
Architecture: source
Version: 5.15.10+dfsg-7.2
Distribution: unstable
Urgency: medium
Maintainer: Debian Qt/KDE Maintainers 
Changed-By: Steve Langasek 
Closes: 1065154
Changes:
 qtbase-opensource-src (5.15.10+dfsg-7.2) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Fix extraneous X-Time64-Compat declarations.  Closes: #1065154.
Checksums-Sha1:
 6041225073c854263927fa89fb1d1b426d1463a6 5402 
qtbase-opensource-src_5.15.10+dfsg-7.2.dsc
 cba236982981bb9565dd0e11ac7c45cdb0149d21 238252 
qtbase-opensource-src_5.15.10+dfsg-7.2.debian.tar.xz
 0eea42cf8e5d1ef23f5da16c9910428aaa30dd25 6083 
qtbase-opensource-src_5.15.10+dfsg-7.2_source.buildinfo
Checksums-Sha256:
 9f8cb385117969983b49024729131716d5449b1b40a177bfa9961823a7dda494 5402 
qtbase-opensource-src_5.15.10+dfsg-7.2.dsc
 bfad3c3dd594bc6efdec8908c13ad553563b7efb1175b165e209b61366f743dc 238252 
qtbase-opensource-src_5.15.10+dfsg-7.2.debian.tar.xz
 8f9dba88264ea545bd934e83b05a994864973234cef766560171ad000d9c4aee 6083 
qtbase-opensource-src_5.15.10+dfsg-7.2_source.buildinfo
Files:
 093a12d163c3c5e37a98f79ddcd3c445 5402 libs optional 
qtbase-opensource-src_5.15.10+dfsg-7.2.dsc
 5b4a47307c03e78a7f066890f4a56df5 238252 libs optional 
qtbase-opensource-src_5.15.10+dfsg-7.2.debian.tar.xz
 e819b9d10814658ec874070905bb6e85 6083 libs optional 
qtbase-opensource-src_5.15.10+dfsg-7.2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJGBAEBCgAwFiEErEg/aN5yj0PyIC/KVo0w8yGyEz0FAmXkQMQSHHZvcmxvbkBk
ZWJpYW4ub3JnAAoJEFaNMPMhshM97HUQAJmucuWH+SqlyAlK7CNiNBtnif/PTrWm
nBpWq/IBgydstgXdvTeePgYe8vzkHnUJVdgIh2KPVSTXHGu8ZJFsa4HY7BjmDBc1
6op51xAvFor9BU8x+xWIbXJjweKQZ25BQi6iNowqTVy7U8rddxgJM2zNXhnF4+Lm
6THm7bjFbfgOWmpfxC7seGomrFC64OpCAPEvFg+aJWaWvzcagZzbMxZDQOrEm+Cb
RcJwrnqX/Vp/yeEAX4cYoYp+Ie/lj+C7ahgSoen4TcvUTQ7avluROHeudIkURAKQ
WtZo1siVh8sX1znKtCbSn//ev2953zVJkz9B2LfKzmYGk4ktxEANtKZGeqkXvwN0
RmR17ZShsmCNfVnX1/kWL4dOtSBtBqLFgUsy+aMqIcZV0eDQJVbWi58U8wYoxqK5
gRvPm1z0I+mIUqtsDviZieJ8TgRCPXX8LfjF8LuQEDmx9fLwciMMn/e41577AxEF
rBHIkMFoIg+vgJr6wrLZZyYkiuM7VBQDS3+36pSZiZkEE/Si2ruBuscEslnT2HAB
dgLAyWJmc7ngjPvpMccrIMnLE6BjZJD4HtAPmxN1j6U2ag4BAscXozdj07BRthpQ
tMMegRx6wrzJjy3uCoSdBcMrrr5h9j/vka+eMmWAIRhKTOEuTTdm1Ow9+w2/YMxH
FLkMS5uRJ5e1
=TSfS
-END PGP SIGNATURE-



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

Bug#1063204: nordugrid-arc: NMU diff for 64-bit time_t transition

A bug in the script used for converting packages for t64 resulted in
extraneous X-Time64-Compat entries.

I am uploading a follow-up NMU to fix this.  Please find a full NMU debdiff
for time_t 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 nordugrid-arc-6.18.0/debian/changelog 
nordugrid-arc-6.18.0/debian/changelog
--- nordugrid-arc-6.18.0/debian/changelog   2024-02-07 23:29:28.0 
+
+++ nordugrid-arc-6.18.0/debian/changelog   2024-03-03 09:44:15.0 
+
@@ -1,3 +1,17 @@
+nordugrid-arc (6.18.0-2.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix extraneous X-Time64-Compat declarations.
+
+ -- Steve Langasek   Sun, 03 Mar 2024 09:44:15 +
+
+nordugrid-arc (6.18.0-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Rename libraries for 64-bit time_t transition.  Closes: #1063204
+
+ -- Benjamin Drung   Thu, 29 Feb 2024 13:30:18 +
+
 nordugrid-arc (6.18.0-2) unstable; urgency=medium
 
   * Disable test incompatible with SWIG 4.2
diff -Nru nordugrid-arc-6.18.0/debian/control 
nordugrid-arc-6.18.0/debian/control
--- nordugrid-arc-6.18.0/debian/control 2024-02-05 17:12:08.0 +
+++ nordugrid-arc-6.18.0/debian/control 2024-03-03 09:44:12.0 +
@@ -3,7 +3,7 @@
 Priority: optional
 Maintainer: Mattias Ellert 
 Uploaders: Anders Waananen 
-Build-Depends:
+Build-Depends: dpkg-dev (>= 1.22.5), dpkg-dev (>= 1.22.5),
  debhelper-compat (= 13),
  dh-python,
  libxml2-dev (>= 2.4.0),
@@ -40,8 +40,10 @@
 Vcs-Git: https://salsa.debian.org/ellert/nordugrid-arc.git
 Homepage: http://www.nordugrid.org
 
-Package: libarccommon3v5
-Replaces:
+Package: libarccommon3t64
+Provides: ${t64:Provides}
+X-Time64-Compat: libarccommon3v5
+Replaces:libarccommon3v5, 
  nordugrid-arc-hed (<< 1.0.1~rc2~),
  nordugrid-arc-arex (<< 2.0.1~),
  libarccommon0,
@@ -62,7 +64,7 @@
  nordugrid-arc-acix-core (<< 6.14.0-2~),
  nordugrid-arc-acix-scanner (<< 6.14.0-2~),
  nordugrid-arc-acix-index (<< 6.14.0-2~)
-Breaks:
+Breaks:libarccommon3v5 (<< ${source:Version}), 
  nordugrid-arc-hed (<< 1.0.1~rc2~),
  nordugrid-arc-arex (<< 2.0.1~),
  libarccommon0,
@@ -92,7 +94,7 @@
 Depends:
  ${shlibs:Depends},
  ${misc:Depends},
- libarccommon3v5 (= ${binary:Version}),
+ libarccommon3t64 (= ${binary:Version}),
  nordugrid-arc-plugins-needed (= ${binary:Version})
 Description: ARC command line clients
  NorduGrid is a collaboration aiming at development, maintenance and
@@ -114,7 +116,7 @@
 Depends:
  ${shlibs:Depends},
  ${misc:Depends},
- libarccommon3v5 (= ${binary:Version})
+ libarccommon3t64 (= ${binary:Version})
 Description: ARC Hosting Environment Daemon
  NorduGrid is a collaboration aiming at development, maintenance and
  support of the middleware, known as the Advanced Resource
@@ -130,7 +132,7 @@
 Depends:
  ${shlibs:Depends},
  ${misc:Depends},
- libarccommon3v5 (= ${binary:Version}),
+ libarccommon3t64 (= ${binary:Version}),
  nordugrid-arc-plugins-gridftp (= ${binary:Version}),
  nordugrid-arc-arcctl-service (= ${source:Version})
 Description: ARC GridFTP server
@@ -149,7 +151,7 @@
 Depends:
  ${shlibs:Depends},
  ${misc:Depends},
- libarccommon3v5 (= ${binary:Version}),
+ libarccommon3t64 (= ${binary:Version}),
  nordugrid-arc-hed (= ${binary:Version}),
  nordugrid-arc-plugins-needed (= ${binary:Version}),
  nordugrid-arc-arcctl-service (= ${source:Version})
@@ -216,16 +218,16 @@
 
 Package: nordugrid-arc-arcctl
 Replaces:
- libarccommon3v5 (<< 6.5.0~),
+ libarccommon3t64 (<< 6.5.0~),
  nordugrid-arc-arex (<< 6.5.0~)
 Breaks:
- libarccommon3v5 (<< 6.5.0~),
+ libarccommon3t64 (<< 6.5.0~),
  nordugrid-arc-arex (<< 6.5.0~)
 Architecture: all
 Depends:
  ${misc:Depends},
  ${python3:Depends},
- libarccommon3v5 (>= ${source:Version})
+ libarccommon3t64 (>= ${source:Version})
 Description: ARC Control Tool
  NorduGrid is a collaboration aiming at development, maintenance and
  support of the middleware, known as the Advanced Resource
@@ -236,18 +238,18 @@
 
 Package: nordugrid-arc-arcctl-service
 Replaces:
- libarccommon3v5 (<< 6.5.0~),
+ libarccommon3t64 (<< 6.5.0~),
  nordugrid-arc-arcctl (<< 6.6.0~),
  nordugrid-arc-arex (<< 6.6.0~)
 Breaks:
- libarccommon3v5 (<< 6.5.0~),
+ libarccommon3t64 (<< 6.5.0~),
  nordugrid-arc-arcctl (<< 6.6.0~),
  nordugrid-arc-arex (<< 6.6.0~)
 Architecture: all
 Depends:
  ${misc:Depends},
  ${python3:Depends},
- libarccommon3v5 (>= ${source:Version}),
+ libarccommon3t64 (>= ${source:Version}),
  nordugrid-arc-arcctl (= ${source:Version})
 Description: ARC Control Tool - service control modules
  NorduGrid is a collaboration aiming at development, maintenance and
@@ -265,13 +267,13 @@
  nordugrid-arc-cache-service (<< 6.0.0~),
  nordugrid-arc-candypond (<< 6.0.0~),

Bug#1065155: marked as done (libpoppler-glib8t64 Provides libpoppler-cpp0v5 instead of libpoppler-glib8)

Your message dated Sun, 03 Mar 2024 09:06:26 +
with message-id 
and subject line Bug#1065155: fixed in poppler 22.12.0-2.2
has caused the Debian Bug report #1065155,
regarding libpoppler-glib8t64 Provides libpoppler-cpp0v5 instead of 
libpoppler-glib8
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.)


-- 
1065155: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065155
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libpoppler-glib8t64
Version: 22.12.0-2.1
Severity: serious
X-Debbugs-Cc: Steve Langasek 

Actually, looking at the diff in #1064282, all packages have "X-Time64-Compat:
libpoppler-cpp0v5", I guess this is incorrect and a typo?


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

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

Versions of packages libpoppler-glib8t64 depends on:
ii  libc6 2.37-15.1
ii  libcairo2 1.18.0-1+b1
ii  libfreetype6  2.13.2+dfsg-1+b1
ii  libglib2.0-0t64   2.78.4-2.1
pn  libpoppler126t64  
ii  libstdc++614-20240221-2.1

libpoppler-glib8t64 recommends no packages.

libpoppler-glib8t64 suggests no packages.
--- End Message ---
--- Begin Message ---
Source: poppler
Source-Version: 22.12.0-2.2
Done: Steve Langasek 

We believe that the bug you reported is fixed in the latest version of
poppler, 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 poppler package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 03 Mar 2024 08:43:35 +
Source: poppler
Architecture: source
Version: 22.12.0-2.2
Distribution: unstable
Urgency: medium
Maintainer: Debian freedesktop.org maintainers 

Changed-By: Steve Langasek 
Closes: 1065155
Changes:
 poppler (22.12.0-2.2) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Fix wrong extraneous X-Time64-Compat declarations.  Closes: #1065155.
Checksums-Sha1:
 bbf6720360881fcd0f45542c285cf6b2152063d7 3536 poppler_22.12.0-2.2.dsc
 dd7e7e6fb42f8f6d54572c3bd380a51236cab50c 37672 
poppler_22.12.0-2.2.debian.tar.xz
 c2b27808e7857b3770c8892ea355dc22a775a493 18207 
poppler_22.12.0-2.2_source.buildinfo
Checksums-Sha256:
 4de24fcb476896809f041b229d783580e198d38d59fe6637e9a49a0acb0a7dcd 3536 
poppler_22.12.0-2.2.dsc
 aac42556ef881b7bf94ab301c0efccd5b83c5a669247491f07cbfd044952ccea 37672 
poppler_22.12.0-2.2.debian.tar.xz
 3c141786d55cedecbdff40b95845c2ff6c17a57d75216c18da8d5e4c14ab0227 18207 
poppler_22.12.0-2.2_source.buildinfo
Files:
 8008852396d835542aa2d1657caa323f 3536 devel optional poppler_22.12.0-2.2.dsc
 8c9c1e74f1e0d9cd507072b9491ad02f 37672 devel optional 
poppler_22.12.0-2.2.debian.tar.xz
 bfdeb8c3db9e02f7568b42361048f485 18207 devel optional 
poppler_22.12.0-2.2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJGBAEBCgAwFiEErEg/aN5yj0PyIC/KVo0w8yGyEz0FAmXkOPISHHZvcmxvbkBk
ZWJpYW4ub3JnAAoJEFaNMPMhshM9OGIQAMTKuTJrp4M/rysQYvDa1Q1W5eJq2tmW
vwdJogwszlfNUb8NSznmxdomi2O1fKkwLpRNFCYbKaxtf5QEBnqtt284r1oC1xNh
1MVSVjgKG8SrfkqEgzKBiw8AJ9ygMKaavpPLMFyisOj+BF5Rsvd9mHAw9cf8L1kP
9gYV35R61g8gkbOxqoluS4Cd1983GTjNdYTRwD9PvKtgSlYNdMn5rh3lwuXWL7Tq
pi7EceBdhi6gB0RFnZ1rE1HidRMKmYeo91A7ZDw6QJ/eVkxDX6cV6XS03Gu8Cu9G
k4RcNtqB7B/HGN6lqLRBmEJHXubh2Bk27+gQxezT8Qw0fUIdjKQ4rIBiNRYw1o7Z
PwCXVcwuqinMoTy1CsX+OB4zg7fj1N5057+LNr7LPWcyVK0kfk3IOHRKIbqR5v5F
Vp3Bhd4VxM7fwfOGm34KqiDofehzilJw9L6aH8dSMvIeKeVKwsYrhQSOF4kAt1ty
lEuWTTOlUcdR6eR43R+71PliADI3hl2Rm5HkeWVtg4kH+HLirNp2s3dDeORd0d+P
Nn76Zmrcp4biZ8t+2tTHiBmbpGI52SFp+1cz/dSUMABB6HUvTQfMVBWM+Dxzey+M
BmgjfoPz8ncWduWFLDluBzUk+vncCgE5t+/LzaaAJWSRCJ1utJrbLnedQAbO1fe1
+HtKHg9U8m9v
=Qkwv
-END PGP SIGNATURE-

Bug#1065121: marked as done (xdelta: still depends on libxdelta2)

Your message dated Sun, 03 Mar 2024 08:47:07 +
with message-id 
and subject line Bug#1065121: fixed in xdelta 1.1.3-10.6
has caused the Debian Bug report #1065121,
regarding xdelta: still depends on libxdelta2
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.)


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

The xdelta package still depends on libxdelta2, rather than on
libxdelta2t64 as it should.

The build log on m68k[1] shows that on this architecture libxdelta2t64
gained a dependency on libxdelta2 as well.  Builds for other 32-bit
architectures are still missing, but I suspect the libxdelta2t64 package
will not installable on architectures where it does not provide
libxdelta2.

Removing the debian/shlibs.local file is most certainly going to fix
this mess, but I have not tested it.


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


1. 
https://buildd.debian.org/status/fetch.php?pkg=xdelta&arch=m68k&ver=1.1.3-10.5&stamp=1709209632&raw=0
--- End Message ---
--- Begin Message ---
Source: xdelta
Source-Version: 1.1.3-10.6
Done: Steve Langasek 

We believe that the bug you reported is fixed in the latest version of
xdelta, 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 xdelta package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 03 Mar 2024 07:46:54 +
Source: xdelta
Architecture: source
Version: 1.1.3-10.6
Distribution: unstable
Urgency: medium
Maintainer: LaMont Jones 
Changed-By: Steve Langasek 
Closes: 1065121
Changes:
 xdelta (1.1.3-10.6) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Remove obsolete debian/shlibs.local which breaks install on 32-bit
 archs.  Thanks to Sven Joachim .  Closes: #1065121.
Checksums-Sha1:
 e7156435b145ea40a47508c74b0ae70980a37f23 1986 xdelta_1.1.3-10.6.dsc
 c5a9eeff2edbed6c5d5b9a3eb4ba69453ac36841 11488 xdelta_1.1.3-10.6.debian.tar.xz
 dc2d531d6b19e9eb52589bf26400f12d65bac56a 7245 
xdelta_1.1.3-10.6_source.buildinfo
Checksums-Sha256:
 c7dab8c95c9a7a914e807cd2b06f5f4bea011e844e957581abd1ec1a18144e4b 1986 
xdelta_1.1.3-10.6.dsc
 ffb86a38c852b3d4c8c6cb95b48a18000dacd0de8925cf3ce8602043cd713a05 11488 
xdelta_1.1.3-10.6.debian.tar.xz
 593d518b977daa7e885bc83733a22ac62acdae601850eb698a529285e83e82f2 7245 
xdelta_1.1.3-10.6_source.buildinfo
Files:
 3f221ee4dd1019ea86d65cfab762d0a3 1986 utils optional xdelta_1.1.3-10.6.dsc
 d6999c5f8b2c2827d523648c9d7f0992 11488 utils optional 
xdelta_1.1.3-10.6.debian.tar.xz
 be3280d2754e61c241422b3e83bee0a7 7245 utils optional 
xdelta_1.1.3-10.6_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJGBAEBCgAwFiEErEg/aN5yj0PyIC/KVo0w8yGyEz0FAmXkK1QSHHZvcmxvbkBk
ZWJpYW4ub3JnAAoJEFaNMPMhshM9qIMQAIJQGxRosMt2pgTQtKZTkvYPVQx1/J2L
Lf9En40+oVFolLZyOV1cH9NP4qjTdijIo+BUQwyJbp4jcMlSkPs3IcXsAPvgMWd5
7TOM1cylC5okzcGwjKw6ppDKBpDf9yTCbfZcQR0i6+W7Sw0t19/F1e8/e0suKK+d
k/hVo0hlD16HsyVuGf68MAvJEwPV81rwlMOWYHaxxxX9HqkV0prfQM0rykfOzNP9
+DMaogFyMaIUQw8ORNJjeY7e4yFTr8YfxGGnZFs3uaHdZmSosYIvT4dGn2C4l8LE
PTpxXo8ZEekqCFpYdO0RXfdO/BaRjUWjvApnJnWoIChov8bPll1DXT4hcPozjV+2
QSOCR5WeBDDTtqu3wx3QmrVDlkeJWLy6Rm6C8TK60hRiMBPooWTCBRnRhTfysgzO
FlZ6/DlHDiVdWZA0oYZHtDExzKVKFrlgyW0smFolqA9DOrPmgZRqtZdbMKAoHAEW
/tRpoR1uX8SacbFlTR49EJ+BYvdUD11U+vQGRsyK74rSKMzGGiPKcZwgKJ7mGOCe
apF1tcKiksSIjRm/Ka5p/xuvr/PB98+bqeCoETrhI6dsgpeVXQnBYJf5sJUzNT1q
Cy/xc0KiNfzILl+GUeAnBhKSB2andBGRvTdV3a15TOvZ34EzG7b4bAwJM5/HYsM3
4yjcU/xyWaAa
=m9Bu
-END PGP SIGNATURE-



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

Bug#1062194: Bug#1065145: guacd: internal aliasing conflict on guacd.service