Bug#1066857: doc-debian: /usr/share/doc/debian/bug-reporting.txt should not be compressed

2024-03-14 Thread Joost van Baal-Ilić
Hi Vincent,

Thanks for this nice bugreport, will get to it.

Bye,

Joost

On Thu, Mar 14, 2024 at 02:31:11PM +0100, Vincent Lefevre wrote:
> Package: doc-debian
> Version: 11.3+nmu1
> Severity: wishlist
> 
> The bug-reporting.txt file is rather small, thus it does not need to
> be compressed. Having it compressed like currently breaks references,
> such as in the apt-get(8) man page, which says
> 
>   APT bug page[1]. If you wish to report a bug in APT, please see
>   /usr/share/doc/debian/bug-reporting.txt or the reportbug(1) command.
> 
> and in /usr/share/doc/debian/FAQ/support.en.html too, while only
> /usr/share/doc/debian/bug-reporting.txt.gz exists.
> 
> -- System Information:
> Debian Release: trixie/sid
>   APT prefers unstable-debug
>   APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500, 
> 'stable-security'), (500, 'stable-debug'), (500, 'proposed-updates-debug'), 
> (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
> 
> Kernel: Linux 6.6.15-amd64 (SMP w/12 CPU threads; PREEMPT)
> Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
> TAINT_UNSIGNED_MODULE
> Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
> Shell: /bin/sh linked to /usr/bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled
> 
> doc-debian depends on no packages.
> 
> Versions of packages doc-debian recommends:
> ii  debian-faq  11.1
> 
> Versions of packages doc-debian suggests:
> ii  atril [postscript-viewer]   1.26.2-1.1+b1
> ii  elinks [www-browser]0.16.1.1-4.1+b2
> ii  firefox [www-browser]   123.0.1-1
> hi  firefox-esr [www-browser]   92.0-local
> ii  ghostscript [postscript-viewer] 10.02.1~dfsg-3+b1
> ii  gv [postscript-viewer]  1:3.7.4-2+local1
> ii  links [www-browser] 2.29-1+b3
> ii  links2 [www-browser]2.29-1+b3
> ii  lynx [www-browser]  2.9.0rel.0-2+b1
> ii  qpdfview-ps-plugin [postscript-viewer]  0.5.0+ds-4
> ii  w3m [www-browser]   0.5.3+git20230121-2+b3
> ii  zathura-ps [postscript-viewer]  0.2.7-2+b2
> 
> -- no debconf information
> 
> -- 
> Vincent Lefèvre  - Web: 
> 100% accessible validated (X)HTML - Blog: 
> Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
> 



Bug#1066858: RFA: python-ionoscloud

2024-03-14 Thread Mattia Rizzolo
Package: wnpp
Severity: wishlist

Hello!

So, I had to package this because of I needed the library.
However I have no particular attachments to it, and I'll happily hand it
over to anybody who has any interest.

It's a pretty straightforward python package, fully generated by
https://openapi-generator.tech and unless upstream changes they way to
work I doubt it will ever need any special expertise.

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
More about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature


Bug#1066857: doc-debian: /usr/share/doc/debian/bug-reporting.txt should not be compressed

2024-03-14 Thread Vincent Lefevre
Package: doc-debian
Version: 11.3+nmu1
Severity: wishlist

The bug-reporting.txt file is rather small, thus it does not need to
be compressed. Having it compressed like currently breaks references,
such as in the apt-get(8) man page, which says

  APT bug page[1]. If you wish to report a bug in APT, please see
  /usr/share/doc/debian/bug-reporting.txt or the reportbug(1) command.

and in /usr/share/doc/debian/FAQ/support.en.html too, while only
/usr/share/doc/debian/bug-reporting.txt.gz exists.

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

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

doc-debian depends on no packages.

Versions of packages doc-debian recommends:
ii  debian-faq  11.1

Versions of packages doc-debian suggests:
ii  atril [postscript-viewer]   1.26.2-1.1+b1
ii  elinks [www-browser]0.16.1.1-4.1+b2
ii  firefox [www-browser]   123.0.1-1
hi  firefox-esr [www-browser]   92.0-local
ii  ghostscript [postscript-viewer] 10.02.1~dfsg-3+b1
ii  gv [postscript-viewer]  1:3.7.4-2+local1
ii  links [www-browser] 2.29-1+b3
ii  links2 [www-browser]2.29-1+b3
ii  lynx [www-browser]  2.9.0rel.0-2+b1
ii  qpdfview-ps-plugin [postscript-viewer]  0.5.0+ds-4
ii  w3m [www-browser]   0.5.3+git20230121-2+b3
ii  zathura-ps [postscript-viewer]  0.2.7-2+b2

-- no debconf information

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



Bug#1066016: python-rdflib-doc: please make the build reproducible.

2024-03-14 Thread Michael R. Crusoe

control: repopen -1

On Thu, 14 Mar 2024 13:04:29 + James Addison  wrote:
> Hi Michael,
>
> Thank you for merging and uploading this change. Unfortunately it 
seems that
> my suggestion didn't solve the problem (based on inspecting the 
results of a
> recent reprotest[1] on Salsa - there's still a 'identifier=>' with

> randomness in the built documentation).
>
> That's my mistake for not testing the patch thoroughly enough. Please 
let me

> know how to proceed (for example, whether you'd prefer that I revert the
> change).

Well, the build failed, so the CI on Salsa wasn't able to test your MR. 
No worries, it isn't your fault!


I think the patch still helped, we can keep it while you continue your 
investigations. I really appreciate it!



--
Michael R. Crusoe



OpenPGP_signature.asc
Description: OpenPGP digital signature


Bug#1066856: apt: please update the URLs in the man pages

2024-03-14 Thread Vincent Lefevre
Package: apt
Version: 2.7.13+b1
Severity: minor

The URLs in the man pages should be updated. For instance, concerning
the b.d.o URLs in the various man pages, "http" should be changed to
"https".

In the apt-cache(8) man page:

http://www.research.att.com/sw/tools/graphviz/ gives a "Page Not Found"
error.

http://rw4.cs.uni-sb.de/users/sander/html/gsvcg1.html should be
changed to
https://www.rw.cdl.uni-saarland.de/people/sander/private/html/gsvcg1.html


-- Package-specific info:

-- (no /etc/apt/preferences present) --


-- (/etc/apt/preferences.d/no-adobe-flash-plugin present, but not submitted) --


-- (/etc/apt/preferences.d/no-pipewire present, but not submitted) --


-- (/etc/apt/sources.list present, but not submitted) --


-- (/etc/apt/sources.list.d/local-i386.list present, but not submitted) --


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

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

Versions of packages apt depends on:
ii  adduser 3.137
ii  base-passwd 3.6.3
ii  debian-archive-keyring  2023.4
ii  gpgv2.2.40-2
ii  libapt-pkg6.0t642.7.13+b1
ii  libc6   2.37-15.1
ii  libgcc-s1   14-20240303-1
ii  libgnutls30t64  3.8.3-1.1
ii  libseccomp2 2.5.5-1
ii  libstdc++6  14-20240303-1
ii  libsystemd0 255.4-1+b1

Versions of packages apt recommends:
ii  ca-certificates  20240203

Versions of packages apt suggests:
ii  apt-doc 2.7.13
ii  aptitude0.8.13-5+b2
ii  dpkg-dev1.22.6
ii  gnupg   2.2.40-2
ii  powermgmt-base  1.37

-- no debconf information

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



Bug#1065309: transition: gnat 12 -> 13 + time_t64

2024-03-14 Thread nicolas . boulenguez

Hello.

Version 2 seems OK.

Thanks.

Bug#1066016: python-rdflib-doc: please make the build reproducible.

2024-03-14 Thread James Addison
Package: python-rdflib-doc
Followup-For: Bug #1066016
X-Debbugs-Cc: cru...@debian.org

Hi Michael,

Thank you for merging and uploading this change.  Unfortunately it seems that
my suggestion didn't solve the problem (based on inspecting the results of a
recent reprotest[1] on Salsa - there's still a '' with
randomness in the built documentation).

That's my mistake for not testing the patch thoroughly enough.  Please let me
know how to proceed (for example, whether you'd prefer that I revert the
change).

This also means that the autodoc config setting may be more limited in
solving these kind of problems that I realized; I'll have to check some merge
requests that I have open for other packages.

Thank you,
James

[1] - https://salsa.debian.org/python-team/packages/rdflib/-/jobs/5445372



Bug#1066855: drop libidn11-dev

2024-03-14 Thread Simon Josefsson
Package: libidn
Version: 1.42-1

All packages should build against libidn-dev now, not libidn11-dev.
Current stable release of Debian ships libidn-dev.

The transitional libidn11-dev package can be dropped when all reverse
dependencies have stopped using it.

root@68d340bc8331:/# apt-cache rdepends libidn11-dev
libidn11-dev
Reverse Depends:
  libidn-dev
  libui-utilcpp-dev
  libloudmouth1-dev
  libidn-dev
  libfreediameter-dev
root@68d340bc8331:/# 

Loudmouth should be fixed by my team upload of 1.5.4-2.

ui-utilcpp maybe not a problem since they use 'libidn-dev|libidn11-dev'?

Remains freediameter, bug filed here:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066848

I'm hoping we don't have to care about compatibility with oldstable.

/Simon


signature.asc
Description: PGP signature


Bug#1066836: libcamera: ftbfs with 64-bit time_t

2024-03-14 Thread Dylan Aïssi

Hi Kieran,

I guess this task is for me ;-)
Yes, I will submit it.

Best,
Dylan


On 3/14/24 13:04, Kieran Bingham wrote:

Hi Steve,

do you also plan to submit this to the libcamera-devel mailing list?

--
Kieran

Quoting Steve Langasek (2024-03-14 05:35:04)

Package: libcamera
Version: 0.2.0-1
Severity: serious
Tags: patch
Justification: ftbfs
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu noble ubuntu-patch

Dear maintainers,

libcamera fails to build from source on 32-bit architectures under 64-bit
time_t, because it has a module that legitimately un-sets _FILE_OFFSET_BITS
for building but this is not allowed without also unsetting _TIME_BITS:

[...]
[267/430] c++ -Isrc/v4l2/v4l2-compat.so.p -Isrc/v4l2 -I../src/v4l2 -Iinclude -I../include -Iinclude/libcamera/ipa 
-Iinclude/libcamera -fdiagnostics-color=always -Wall -Winvalid-pch -Wextra -Werror -std=c++17 -Wno-redundant-move 
-Wno-psabi -Wshadow -include /<>/obj-arm-linux-gnueabihf/config.h -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security 
-fno-stack-clash-protection -fdebug-prefix-map=/<>=/usr/src/libcamera-0.2.0-1ubuntu3 
-Wno-error -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=3 -fPIC 
-DLIBCAMERA_BASE_PRIVATE -U_FILE_OFFSET_BITS -D_FILE_OFFSET_BITS=32 -D_LARGEFILE64_SOURCE -fvisibility=hidden -MD 
-MQ src/v4l2/v4l2-compat.so.p/v4l2_camera.cpp.o -MF src/v4l2/v4l2-compat.so.p/v4l2_camera.cpp.o.d -o 
src/v4l2/v4l2-compat.so.p/v4l2_camera.cpp.o -c ../src/v4l2/v4l2_camera.cpp
FAILED: src/v4l2/v4l2-compat.so.p/v4l2_camera.cpp.o
c++ -Isrc/v4l2/v4l2-compat.so.p -Isrc/v4l2 -I../src/v4l2 -Iinclude -I../include -Iinclude/libcamera/ipa 
-Iinclude/libcamera -fdiagnostics-color=always -Wall -Winvalid-pch -Wextra -Werror -std=c++17 -Wno-redundant-move 
-Wno-psabi -Wshadow -include /<>/obj-arm-linux-gnueabihf/config.h -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security 
-fno-stack-clash-protection -fdebug-prefix-map=/<>=/usr/src/libcamera-0.2.0-1ubuntu3 
-Wno-error -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=3 -fPIC 
-DLIBCAMERA_BASE_PRIVATE -U_FILE_OFFSET_BITS -D_FILE_OFFSET_BITS=32 -D_LARGEFILE64_SOURCE -fvisibility=hidden -MD 
-MQ src/v4l2/v4l2-compat.so.p/v4l2_camera.cpp.o -MF src/v4l2/v4l2-compat.so.p/v4l2_camera.cpp.o.d -o 
src/v4l2/v4l2-compat.so.p/v4l2_camera.cpp.o -c ../src/v4l2/v4l2_camera.cpp
In file included from /usr/include/features.h:394,
  from 
/usr/include/arm-linux-gnueabihf/c++/13/bits/os_defines.h:39,
  from 
/usr/include/arm-linux-gnueabihf/c++/13/bits/c++config.h:679,
  from /usr/include/c++/13/bits/requires_hosted.h:31,
  from /usr/include/c++/13/deque:60,
  from ../src/v4l2/v4l2_camera.h:10,
  from ../src/v4l2/v4l2_camera.cpp:8:
/usr/include/features-time64.h:26:5: error: #error "_TIME_BITS=64 is allowed only 
with _FILE_OFFSET_BITS=64"
26 | #   error "_TIME_BITS=64 is allowed only with _FILE_OFFSET_BITS=64"
   | ^
[...]

   
(https://launchpad.net/ubuntu/+source/libcamera/0.2.0-1ubuntu3/+build/27902670)

Since this is a legitimate un-setting of _FILE_OFFSET_BITS in order to get
access to the necessary libc6 prototypes and macros, and since the functions
being intercepted are not sensitive to time_t, the simplest solution is to
also unset _TIME_BITS.

Please see the attached patch, which has been uploaded to Ubuntu to fix this
build failure.

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


--
Dylan Aïssi
Software Engineer

Collabora Ltd.
Platinum Building, St John's Innovation Park, Cambridge CB4 0DS, UK
Registered in England & Wales, no. 5513718



Bug#1066854: don't hard-code the name of the shared library

2024-03-14 Thread Matthias Klose

Package: src:ruby-magic
Version: 0.2.9-3
Severity: serious
Tags: sid trixie

the package build-depends on libmagic1, and depends on it. The name was 
recently changed to libmagic1t64.  Please don't hard-code it, but try to 
b-d on libmagic-dev, and derive the name of the shared library package 
from the libmagic-dev package.




Bug#1066853: don't hard-code the name of the shared library

2024-03-14 Thread Matthias Klose

Package: src:roundcube
Version: 0.2.9-3
Severity: serious
Tags: sid trixie

the package depends on libmagic1. The name was recently changed to 
libmagic1t64.  Please don't hard-code it, but try to b-d on 
libmagic-dev, and derive the name of the shared library package from the 
libmagic-dev package.




Bug#1066852: don't hard-code the name of the shared library

2024-03-14 Thread Matthias Klose

Package: src:binwalk
Version: 2.3.4+dfsg1-4
Severity: serious
Tags: sid trixie

the package depends on libmagic1. The name was recently changed to 
libmagic1t64.  Please don't hard-code it, but try to b-d on 
libmagic-dev, and derive the name of the shared library package from the 
libmagic-dev package.




Bug#1066074: ntfs-3g: broken shlibs (deb and udeb)

2024-03-14 Thread Benjamin Drung
On Tue, 12 Mar 2024 02:12:16 +0100 Cyril Brulebois 
wrote:
> Source: ntfs-3g
> Version: 1:2022.10.3-1.1
> Severity: serious
> Tags: d-i
> Justification: broken shlibs
> X-Debbugs-Cc: debian-b...@lists.debian.org, Benjamin Drung

> 
> Hi,
> 
> Here's what debian/libntfs-3g89t64/DEBIAN/shlibs looks like after
> a build:
> 
> libntfs-3g 89 libntfs-3g89
> udeb: libntfs-3g 89 libntfs-3g89
> 
> That doesn't match binaries shipped by the source package.
> 
> 
> See debian/rules:
> 
> SONAME = $(shell objdump -p debian/tmp/lib/*/libntfs-3g.so.*.* |
awk -Fso. '/SONAME/ { print $$2 }')
> 
> […]
> 
> override_dh_makeshlibs:
> dh_makeshlibs --add-udeb=ntfs-3g-udeb -Vlibntfs-
3g$(SONAME)
> 
> 
> In the previous version we had:
> 
> libntfs-3g 89 libntfs-3g89
> udeb: libntfs-3g 89 ntfs-3g-udeb
> 
> Adding 't64' at the end of the dh_makeshlibs line quoted above gives:
> 
> libntfs-3g 89 libntfs-3g89t64
> udeb: libntfs-3g 89 ntfs-3g-udeb
> 
> which certainly looks much better. I haven't performed any rebuild
test
> for the reverse dependencies of the library, nor runtime tests on the
> d-i side (other packages are broken right now). The Depends field of
> the udeb looks correct now though:
> 
> -Depends: libc6-udeb (>= 2.37), libntfs-3g89, fuse3-udeb
> +Depends: libc6-udeb (>= 2.37), fuse3-udeb
> 
> 
> I'll leave it up to the 64-bit time_t transition drivers to choose how
> to address this issue (add t64 on the SONAME line, or just in the
> dh_makeshlibs override, or something else), and to track down packages
> that might have been rebuilt against the broken library.

Attached the diff for the NMU upload.

-- 
Benjamin Drung
Debian & Ubuntu Developer
diff -Nru ntfs-3g-2022.10.3/debian/changelog ntfs-3g-2022.10.3/debian/changelog
--- ntfs-3g-2022.10.3/debian/changelog	2024-03-01 13:40:22.0 +0100
+++ ntfs-3g-2022.10.3/debian/changelog	2024-03-14 13:21:45.0 +0100
@@ -1,3 +1,11 @@
+ntfs-3g (1:2022.10.3-1.2) unstable; urgency=medium
+
+  [ Zixing Liu ]
+  * Non-maintainer upload.
+  * d/rules: add t64 suffix to the dh_makeshlib command. (Closes: #1066074)
+
+ -- Benjamin Drung   Thu, 14 Mar 2024 13:21:45 +0100
+
 ntfs-3g (1:2022.10.3-1.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru ntfs-3g-2022.10.3/debian/rules ntfs-3g-2022.10.3/debian/rules
--- ntfs-3g-2022.10.3/debian/rules	2022-10-31 15:14:06.0 +0100
+++ ntfs-3g-2022.10.3/debian/rules	2024-03-14 13:21:09.0 +0100
@@ -105,7 +105,7 @@
 	dh_link --remaining-packages
 
 override_dh_makeshlibs:
-	dh_makeshlibs --add-udeb=ntfs-3g-udeb -Vlibntfs-3g$(SONAME)
+	dh_makeshlibs --add-udeb=ntfs-3g-udeb -Vlibntfs-3g$(SONAME)t64
 
 .PHONY: override_dh_auto_configure override_dh_auto_install \
 	override_dh_installchangelogs \


Bug#1065309: transition: gnat 12 -> 13 + time_t64

2024-03-14 Thread Graham Inggs
Hi Nicolas, Matthias

On Sun, 3 Mar 2024 at 16:18, Nicolas Boulenguez  wrote:
> Ben file:
>
> title = "gnat-13";
> is_affected = .depends ~ 
> "libgnat-8/libgnat-9/libgnat-10/libgnat-11/libgnat-12" | .depends ~ 
> "libgnat-13";
> is_good = .depends ~ "libgnat-13";
> is_bad = .depends ~ "libgnat-8/libgnat-9/libgnat-10/libgnat-11/libgnat-12";

ben did not like the syntax, but I think I understood your intention
and set up a tracker [1].

After seeing the output, I tried to simplify it, and assumed that gcc
need not be included.  I set up a second version of the tracker [2].

Please let me know if these need further refinement.  If not, let me
know which tracker you prefer to keep.

Regards
Graham

[1] https://release.debian.org/transitions/html/gnat-13.html
[2] https://release.debian.org/transitions/html/gnat-13-v2.html



Bug#1066851: don't hard-code the name of the shared library

2024-03-14 Thread Matthias Klose

Package: src:raku-readline
Version: 0.1.6-3
Severity: serious
Tags: sid trixie

the package build-depends on libreadline8, and depends on it. The name 
was recently changed to libreadline8t64.  Please don't hard-code it, but 
try to b-d on libreadline-dev, and derive the name of the shared library 
package from the libreadline-dev package.




Bug#1066849: libelf1 Version mismatch (0.190-1+b1 vs 0.191-1)

2024-03-14 Thread Matthias Klose
time_t64 transitions in progress, you can't expect debootstrapping at 
this point.


On 14.03.24 12:04, Rémi DUCCESCHI wrote:

Package: libelf1
Version: 0.190-1+b1

Hello,
It seems that since the last update (2 days ago), the version of the package
has not been updated.
When I check the version in Debian, it says 0.190-1+b1
(https://packages.debian.org/fr/sid/libelf1), but when I check the changelog,
I get .0191-1 
(https://metadata.ftp-master.debian.org/changelogs/main/e/elfutils/elfutils_0.191-1_changelog).

I guess libelf1 is linked to elfutils and should have the same version?

Apparently because of this, debootstrap is failing a new install of Debian Sid
from the daily mini.iso
(https://d-i.debian.org/daily-images/amd64/daily/netboot/):
dpkg --configure complains about mismatch versions.

Thanks for your work! If this is not the correct place for this, let me know
where to post it.

Best regards,





Bug#1066836: libcamera: ftbfs with 64-bit time_t

2024-03-14 Thread Kieran Bingham
Hi Steve,

do you also plan to submit this to the libcamera-devel mailing list?

--
Kieran

Quoting Steve Langasek (2024-03-14 05:35:04)
> Package: libcamera
> Version: 0.2.0-1
> Severity: serious
> Tags: patch
> Justification: ftbfs
> User: ubuntu-de...@lists.ubuntu.com
> Usertags: origin-ubuntu noble ubuntu-patch
> 
> Dear maintainers,
> 
> libcamera fails to build from source on 32-bit architectures under 64-bit
> time_t, because it has a module that legitimately un-sets _FILE_OFFSET_BITS
> for building but this is not allowed without also unsetting _TIME_BITS:
> 
> [...]
> [267/430] c++ -Isrc/v4l2/v4l2-compat.so.p -Isrc/v4l2 -I../src/v4l2 -Iinclude 
> -I../include -Iinclude/libcamera/ipa -Iinclude/libcamera 
> -fdiagnostics-color=always -Wall -Winvalid-pch -Wextra -Werror -std=c++17 
> -Wno-redundant-move -Wno-psabi -Wshadow -include 
> /<>/obj-arm-linux-gnueabihf/config.h -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -fno-stack-clash-protection 
> -fdebug-prefix-map=/<>=/usr/src/libcamera-0.2.0-1ubuntu3 
> -Wno-error -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 
> -Wdate-time -D_FORTIFY_SOURCE=3 -fPIC -DLIBCAMERA_BASE_PRIVATE 
> -U_FILE_OFFSET_BITS -D_FILE_OFFSET_BITS=32 -D_LARGEFILE64_SOURCE 
> -fvisibility=hidden -MD -MQ src/v4l2/v4l2-compat.so.p/v4l2_camera.cpp.o -MF 
> src/v4l2/v4l2-compat.so.p/v4l2_camera.cpp.o.d -o 
> src/v4l2/v4l2-compat.so.p/v4l2_camera.cpp.o -c ../src/v4l2/v4l2_camera.cpp
> FAILED: src/v4l2/v4l2-compat.so.p/v4l2_camera.cpp.o 
> c++ -Isrc/v4l2/v4l2-compat.so.p -Isrc/v4l2 -I../src/v4l2 -Iinclude 
> -I../include -Iinclude/libcamera/ipa -Iinclude/libcamera 
> -fdiagnostics-color=always -Wall -Winvalid-pch -Wextra -Werror -std=c++17 
> -Wno-redundant-move -Wno-psabi -Wshadow -include 
> /<>/obj-arm-linux-gnueabihf/config.h -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -fno-stack-clash-protection 
> -fdebug-prefix-map=/<>=/usr/src/libcamera-0.2.0-1ubuntu3 
> -Wno-error -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 
> -Wdate-time -D_FORTIFY_SOURCE=3 -fPIC -DLIBCAMERA_BASE_PRIVATE 
> -U_FILE_OFFSET_BITS -D_FILE_OFFSET_BITS=32 -D_LARGEFILE64_SOURCE 
> -fvisibility=hidden -MD -MQ src/v4l2/v4l2-compat.so.p/v4l2_camera.cpp.o -MF 
> src/v4l2/v4l2-compat.so.p/v4l2_camera.cpp.o.d -o 
> src/v4l2/v4l2-compat.so.p/v4l2_camera.cpp.o -c ../src/v4l2/v4l2_camera.cpp
> In file included from /usr/include/features.h:394,
>  from 
> /usr/include/arm-linux-gnueabihf/c++/13/bits/os_defines.h:39,
>  from 
> /usr/include/arm-linux-gnueabihf/c++/13/bits/c++config.h:679,
>  from /usr/include/c++/13/bits/requires_hosted.h:31,
>  from /usr/include/c++/13/deque:60,
>  from ../src/v4l2/v4l2_camera.h:10,
>  from ../src/v4l2/v4l2_camera.cpp:8:
> /usr/include/features-time64.h:26:5: error: #error "_TIME_BITS=64 is allowed 
> only with _FILE_OFFSET_BITS=64"
>26 | #   error "_TIME_BITS=64 is allowed only with _FILE_OFFSET_BITS=64"
>   | ^
> [...]
> 
>   
> (https://launchpad.net/ubuntu/+source/libcamera/0.2.0-1ubuntu3/+build/27902670)
> 
> Since this is a legitimate un-setting of _FILE_OFFSET_BITS in order to get
> access to the necessary libc6 prototypes and macros, and since the functions
> being intercepted are not sensitive to time_t, the simplest solution is to
> also unset _TIME_BITS.
> 
> Please see the attached patch, which has been uploaded to Ubuntu to fix this
> build failure.
> 
> Thanks for considering,
> -- 
> 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



Bug#1066850: don't hard-code the name of the shared library

2024-03-14 Thread Matthias Klose

Package: src:python-magic
Version: 2:0.4.27-2
Severity: serious
Tags: sid trixie

the package build-depends on libmagic1, and depends on it. The name was 
recently changed to libmagic1t64.  Please don't hard-code it, but try to 
b-d on libmagic-dev, and derive the name of the shared library package 
from the libmagic-dev package.




Bug#1066848: freediameter: replace libidn11-dev with libidn-dev

2024-03-14 Thread Simon Josefsson
Hi Ruben, all,

I have opened a merge request to resolve the bug below:

https://salsa.debian.org/debian-mobcom-team/freediameter/-/merge_requests/4

Are you able to merge and upload a new version?

If you agree, and add me to the Salsa group, I can merge it and prepare
the upload too.

/Simon

Simon Josefsson  writes:

> Package: freediameter
> Version: 1.2.1-8
> Tags: patch
>
> Hi!  I'd like to drop the transitional package 'libidn11-dev' as most
> packages have already moved to use 'libidn-dev' which is in stable.
>
> How about this patch?
>
> /Simon
>
> diff --git a/debian/control b/debian/control
> index 335362a..2856eae 100644
> --- a/debian/control
> +++ b/debian/control
> @@ -8,7 +8,7 @@ Build-Depends: debhelper (>= 11),
> libsctp-dev,
> bison,
> flex,
> -   libidn11-dev,
> +   libidn-dev,
> libgcrypt20-dev,
> libgnutls28-dev,
> pkg-config,
> @@ -63,7 +63,7 @@ Depends: libfdcore6 (= ${binary:Version}),
>   libfdproto6 (= ${binary:Version}),
>   libgnutls28-dev,
>   libgcrypt20-dev,
> - libidn11-dev,
> + libidn-dev,
>   libsctp-dev,
>   ${misc:Depends}
>  Description: Library for the Diameter protocol (development files)
>


signature.asc
Description: PGP signature


Bug#1007009: openboard: Wrongly displays "world map" image sample fixed upstream

2024-03-14 Thread Martin Winter
This bug is fixed upstream with commit 
741491539b129e4ecc7ffceb38ffc945177a7cf6 which is contained in the 
latest version 1.7.0.


OpenPGP_0x9DA10327E5DE0652.asc
Description: OpenPGP public key


OpenPGP_signature.asc
Description: OpenPGP digital signature


Bug#1066849: libelf1 Version mismatch (0.190-1+b1 vs 0.191-1)

2024-03-14 Thread Rémi DUCCESCHI
Package: libelf1
Version: 0.190-1+b1

Hello,
It seems that since the last update (2 days ago), the version of the package
has not been updated.
When I check the version in Debian, it says 0.190-1+b1
(https://packages.debian.org/fr/sid/libelf1), but when I check the changelog,
I get .0191-1 
(https://metadata.ftp-master.debian.org/changelogs/main/e/elfutils/elfutils_0.191-1_changelog).

I guess libelf1 is linked to elfutils and should have the same version?

Apparently because of this, debootstrap is failing a new install of Debian Sid
from the daily mini.iso
(https://d-i.debian.org/daily-images/amd64/daily/netboot/):
dpkg --configure complains about mismatch versions.

Thanks for your work! If this is not the correct place for this, let me know
where to post it.

Best regards,



Bug#1066848: freediameter: replace libidn11-dev with libidn-dev

2024-03-14 Thread Simon Josefsson
Package: freediameter
Version: 1.2.1-8
Tags: patch

Hi!  I'd like to drop the transitional package 'libidn11-dev' as most
packages have already moved to use 'libidn-dev' which is in stable.

How about this patch?

/Simon

diff --git a/debian/control b/debian/control
index 335362a..2856eae 100644
--- a/debian/control
+++ b/debian/control
@@ -8,7 +8,7 @@ Build-Depends: debhelper (>= 11),
libsctp-dev,
bison,
flex,
-   libidn11-dev,
+   libidn-dev,
libgcrypt20-dev,
libgnutls28-dev,
pkg-config,
@@ -63,7 +63,7 @@ Depends: libfdcore6 (= ${binary:Version}),
  libfdproto6 (= ${binary:Version}),
  libgnutls28-dev,
  libgcrypt20-dev,
- libidn11-dev,
+ libidn-dev,
  libsctp-dev,
  ${misc:Depends}
 Description: Library for the Diameter protocol (development files)


signature.asc
Description: PGP signature


Bug#1066847: openssh: please consider disabling ssh-askpass-gnome on 32-bit during the time_t transition

2024-03-14 Thread Simon McVittie
Source: openssh
Severity: wishlist
Tags: patch
X-Debbugs-Cc: debian-...@lists.debian.org

On the architectures affected by the 64-bit time_t transition, there
is at least one cyclic build-dependency involving this package:
openssh-server, gtk+3.0, at-spi2-core, dbus-broker, systemd, cryptsetup,
libssh, openssh-server.

I've tried to break this cycle at at-spi2-core (#1066844) but that's going
to require additional changes in gtk+3.0, to disable its test suite (which
requires librsvg, which requires Rust, which needs re-bootstrapping)
on the affected architectures, and at this stage I'm unsure whether other
relevant cycles exist.

I think it would be pragmatic to disable ssh-askpass-gnome on the affected
architectures for the duration of this transition: it's a low-popcon
leaf package which is the only thing pulling in "heavy" dependencies
to openssh. I attach a possible patch. I've verified that it compiles
successfully in an armhf porterbox chroot (without ssh-askpass-gnome)
and on amd64 (with ssh-askpass-gnome), but I haven't otherwise tested it.

Thanks,
smcv
>From bbefe785a6ab567677af77ccd12b1fbb59a42d8d Mon Sep 17 00:00:00 2001
From: Simon McVittie 
Date: Thu, 14 Mar 2024 10:48:03 +
Subject: [PATCH] d/control, d/rules: Disable ssh-askpass-gnome on 32-bit,
 except i386

On the architectures affected by the 64-bit time_t transition, there
is at least one cyclic build-dependency involving this package:
openssh-server, gtk+3.0, at-spi2-core, dbus-broker, systemd, cryptsetup,
libssh, openssh-server. Temporarily dropping a low-popcon binary package
that is already excludable by a build-profile seems like a convenient
place to break the cycle.

Closes: #-1
---
 debian/control | 2 +-
 debian/rules   | 6 ++
 2 files changed, 7 insertions(+), 1 deletion(-)

diff --git a/debian/control b/debian/control
index 0a785bcb2..38abe62ec 100644
--- a/debian/control
+++ b/debian/control
@@ -10,7 +10,7 @@ Build-Depends: debhelper (>= 13.1~),
libaudit-dev [linux-any],
libedit-dev,
libfido2-dev (>= 1.5.0) [linux-any],
-   libgtk-3-dev ,
+   libgtk-3-dev [!armel !armhf !hppa !m68k !powerpc !sh4] ,
libkrb5-dev | heimdal-dev,
libpam0g-dev | libpam-dev,
libselinux1-dev [linux-any],
diff --git a/debian/rules b/debian/rules
index fd9ab8d03..cd4c27b58 100755
--- a/debian/rules
+++ b/debian/rules
@@ -108,6 +108,10 @@ ifeq ($(shell dpkg-vendor --is Ubuntu && echo yes) $(DEB_HOST_ARCH), yes i386)
   BUILD_PACKAGES += -Nopenssh-tests
 endif
 
+ifeq ($(DEB_HOST_ARCH_BITS)$(filter i386,$(DEB_HOST_ARCH_CPU)),32)
+  BUILD_PACKAGES += -Nssh-askpass-gnome
+endif
+
 %:
 	dh $@ --with=runit $(BUILD_PACKAGES)
 
@@ -132,9 +136,11 @@ ifeq ($(filter noudeb,$(DEB_BUILD_PROFILES)),)
 	$(MAKE) -C debian/build-udeb $(PARALLEL) ASKPASS_PROGRAM='/usr/bin/ssh-askpass' ssh scp sftp sshd ssh-keygen
 endif
 
+ifneq ($(DEB_HOST_ARCH_BITS)$(filter i386,$(DEB_HOST_ARCH_CPU)),32)
 ifeq ($(filter pkg.openssh.nognome,$(DEB_BUILD_PROFILES)),)
 	$(MAKE) -C contrib gnome-ssh-askpass3 CC='$(CC) $(CPPFLAGS) $(CFLAGS) -Wall -Wl,--as-needed $(LDFLAGS)' PKG_CONFIG=$(PKG_CONFIG)
 endif
+endif
 
 override_dh_auto_build-indep:
 
-- 
2.43.0



Bug#1065831: document package specifiers for `upgrade`

2024-03-14 Thread David Kalnischkies
(this reply has nothing to do with the bugreport in question)

On Wed, Mar 13, 2024 at 10:00:56PM +0100, Miguel Angel Rojas wrote:
> >> Julian provided an explanation in #74,
> 20240312113620.ga1944...@debian.org
> 
> I can't access this link..

It isn't a link, it is a message id of an email. Your mail client (or
web frontend or whatever) should find the mail if you search for it
– assuming you got that mail and haven't deleted it in the meantime of
course.

You can also make it a link by prepending https://lists.debian.org/,
aka: https://lists.debian.org/20240312113620.ga1944...@debian.org
That will search for the mail in Debians mailing list archives.


Best regards

David Kalnischkies


signature.asc
Description: PGP signature


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

2024-03-14 Thread Andreas Beckmann

On 14/03/2024 10.54, Paul Gevers wrote:
I just did. The biggest rise I saw (and I didn't even stop parallel 
runners) was ~5 GB, so this version seems fine.


Please let me know when the other versions are fixed too.


Thanks. I'll upgrade the other ones over the next days, closing the 
existing bug again with each upload.


Don't hesitate to yell if you notice something suspiciously straining on 
the CI ;-)



Andreas



Bug#1066846: loudmouth: replace libidn11-dev with libidn-dev

2024-03-14 Thread Simon Josefsson
Package: loudmouth
Version: 1.5.4-1
Tags: patch

Hi!  I'd like to drop the transitional package 'libidn11-dev' as most
packages have already moved to use 'libidn-dev' which is in stable.

How about this patch?

/Simon

diff --git a/debian/control b/debian/control
index 853b197..963b1c3 100644
--- a/debian/control
+++ b/debian/control
@@ -7,7 +7,7 @@ Build-Depends: debhelper-compat (= 13),
gtk-doc-tools (>= 1.1-2),
libglib2.0-dev,
libgnutls28-dev (>= 3.0.20),
-   libidn11-dev,
+   libidn-dev,
libasyncns-dev,
check,
libkrb5-dev
@@ -25,7 +25,7 @@ Depends: ${misc:Depends},
  libloudmouth1-0 (= ${binary:Version}),
  libglib2.0-dev,
  libgnutls28-dev,
- libidn11-dev
+ libidn-dev
 Description: Development files for Loudmouth Jabber library
  The development headers and API documentation for the LoudMouth
  Jabber library. See the description of libloudmouth1-0 for a more detailed


signature.asc
Description: PGP signature


Bug#1066263: xfonts-utils: FTBFS: ../fonttosfnt/util.c:89:10: error: implicit declaration of function ‘vasprintf’; did you mean ‘vsprintf’? [-Werror=implicit-function-declaration]

2024-03-14 Thread Thomas Dickey
On Wed, Mar 13, 2024 at 10:44:07PM +0500, Andrey Rakhmatullin wrote:
> On Wed, Mar 13, 2024 at 12:46:49PM +0100, Lucas Nussbaum wrote:
> > > ../fonttosfnt/util.c: In function ‘vsprintf_alloc’:
> > > ../fonttosfnt/util.c:89:10: error: implicit declaration of function 
> > > ‘vasprintf’; did you mean ‘vsprintf’? 
> > > [-Werror=implicit-function-declaration]
> Looks like it's caused by the lack of -D_GNU_SOURCE, not sure who should
> set it. There is a very old debian/changelog entry about temporarily
> setting it from d/rules and fonttosfnt/write.c sets it but
> fonttosfnt/util.c doesn't and there is nothing related in the autotools
> stuff.

The Debian rules file is rather old, which may be the problem.

https://salsa.debian.org/xorg-team/font/xfonts-utils

In my (other) test packages, I haven't had to add -D_DEFAULT_SOURCE,**
only for non-package builds has that been necessary.

** -D_GNU_SOURCE should only be used for the rare program relying upon
   non-POSIX interfaces.

-- 
Thomas E. Dickey 
https://invisible-island.net


signature.asc
Description: PGP signature


Bug#1066845: gnome-genius: Is Genius really proprietary?

2024-03-14 Thread Christian Böck
Package: gnome-genius
Version: 1.0.27-1+b1
Severity: minor
X-Debbugs-Cc: deb...@funtech.org

Dear Maintainer,

According to the "Software"-tool Genius is proprietary software.
But when you visit its homepage it is licensed under the GPL and sources can be
downloaded.

Not realy a bug, but I think it should be fixed anyways.

Sincerely
Chris


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

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

Versions of packages gnome-genius depends on:
ii  genius-common 1.0.27-1
ii  libc6 2.36-9+deb12u4
ii  libcairo2 1.16.0-7
ii  libgdk-pixbuf-2.0-0   2.42.10+dfsg-1+b1
ii  libglib2.0-0  2.74.6-2
ii  libgmp10  2:6.2.1+dfsg1-1.1
ii  libgtk-3-03.24.38-2~deb12u1
ii  libgtksourceview-4-0  4.8.4-4
ii  libmpfr6  4.2.0-1
ii  libpango-1.0-01.50.12+ds-1
ii  libpangocairo-1.0-0   1.50.12+ds-1
ii  libreadline8  8.2-1.3
ii  libvte-2.91-0 0.70.6-2~deb12u1

gnome-genius recommends no packages.

gnome-genius suggests no packages.

-- no debconf information



Bug#1064946: morph's abandoned packages (list)

2024-03-14 Thread Andreas Tille
Control: tags -1 moreinfo

Hi,

this package is team maintained.  I have to assume its former maintainer
has decided to leave the team.  Please delay the removal until it is
perfectly clear that no other team member intends to take over this
package.

Thank you for your work as ftpmaster
 Andreas.

-- 
http://fam-tille.de



Bug#1061769: Unexpected VLAN behavior with KEA DHCP

2024-03-14 Thread kristofer.hansson
Hi Paride.

Thanks for the answer and while it was not the answer I hoped for I completely 
understand and sympathize with your decision.

I'll see if I can get the ISC team to take another look at the issue.

Regards Kristofer

EQUANS Mail Disclaimer: https://www.equans.com/disclaimer/disclaimer-mail/en


Bug#1066844: at-spi2-core: needs re-bootstrapping on armel, armhf for 64-bit time_t transition

2024-03-14 Thread Simon McVittie
Package: at-spi2-core
Version: 2.51.90-3
Severity: important
X-Debbugs-Cc: debian-...@lists.debian.org
Tags: patch

at-spi2-core has a circular build-dependency on itself when tests are
enabled, which makes its build-dependencies unsatisfiable (libglib2.0-dev
depends on libglib2.0-0t64, but at-spi2-core still depends on libglib2.0-0)
and prevents it from being rebuilt for the 64-bit time_t transition.
I think the easiest way to unblock this will be to disable tests on the
affected architectures temporarily, similar to what was done in stunnel4.

It's also affected by a longer cyclic build-dependency chain:
at-spi2-core, dbus-broker, systemd, cryptsetup, libssh, openssh-server,
gtk+3.0, back to at-spi-2-core. I think the easiest way to break this
one will be temporarily swapping back from dbus-broker to dbus-daemon
as preferred on the affected architectures. I confirmed that this makes
it buildable on a porterbox.

Proposed patches available on
https://salsa.debian.org/a11y-team/at-spi2-core/-/merge_requests/8,
I'll attach them to the bug when I've amdended them to include the
bug number.

After at-spi2-core has been rebuilt, I'm hoping that similar changes will
unblock the ability to rebuild gtk+2.0 and gtk+3.0.

smcv



Bug#1066843: util-linux: --delete option does not work

2024-03-14 Thread Francesco Potortì
Package: util-linux
Version: 2.39.3-6
Severity: normal
X-Debbugs-Cc: none, Francesco Potortì 
File: /usr/bin/findmnt

The man page for findmnt lists a --delete option which is necessary to me.  
Unfortunately, findmnt says it does not have such option, s (I resorted to 
using mount for that.

Either --delete should work for findmnt, or the man page should be amended to 
remove the --delete option and ideally suggest using mount for those needing it.

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

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

Versions of packages util-linux depends on:
ii  libblkid1  2.39.3-6
ii  libc6  2.37-15
ii  libcap-ng0 0.8.4-2
ii  libcrypt1  1:4.4.36-4
ii  libmount1  2.39.3-6
ii  libpam0g   1.5.2-9.1+b1
ii  libselinux13.5-2
ii  libsmartcols1  2.39.3-6
ii  libsystemd0255.4-1
ii  libtinfo6  6.4+20240113-1
ii  libudev1   255.4-1
ii  libuuid1   2.39.3-6
ii  zlib1g 1:1.3.dfsg-3+b1

Versions of packages util-linux recommends:
ii  sensible-utils  0.0.22

Versions of packages util-linux suggests:
ii  dosfstools  4.2-1
ii  kbd 2.6.4-2
ii  util-linux-extra2.39.3-6
pn  util-linux-locales  

-- debconf information:
  util-linux/noauto-with-nonzero-passnum:



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

2024-03-14 Thread Paul Gevers

Hi,

On 12-03-2024 10:18 a.m., Andreas Beckmann wrote:

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

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


Did you have time to test the -12 version, yet?


I just did. The biggest rise I saw (and I didn't even stop parallel 
runners) was ~5 GB, so this version seems fine.


Please let me know when the other versions are fixed too.

Paul


OpenPGP_signature.asc
Description: OpenPGP digital signature


Bug#1064976:

2024-03-14 Thread Colm Buckley
Hey folks -

I see that linux-headers-* has been promoted to 6.6 in the BPO channel, but
this dependency is still in place.
Is it really the case that we want to drag in the image binaries and other
machinery as a dependency for a source package like linux-headers.
I feel that the BPF use case should really be addressed using vmlinux.h
(the "skipping BTF generation" message should be ignored as all of this
information *should* be included in vmlinux.h).
Any further thoughts?

Colm


Bug#1066310: dx: FTBFS: _compparse.c:51:17: error: implicit declaration of function ‘_dxfcclex’ [-Werror=implicit-function-declaration]

2024-03-14 Thread Bo YU

On Wed, Mar 13, 2024 at 12:37:02PM +0100, Lucas Nussbaum wrote:
...

cc1: warning: command-line option ‘-std=c++11’ is valid for C++/ObjC++ but not 
for C
y.tab.c: In function ‘_dxfccparse’:
_compparse.c:51:17: error: implicit declaration of function ‘_dxfcclex’ 
[-Werror=implicit-function-declaration]
   51 | #define yylex   _dxfcclex
  | ^
y.tab.c:651:16: note: in expansion of macro ‘yylex’
y.tab.c:1107:16: note: in expansion of macro ‘YYLEX’
_compparse.c:52:17: error: implicit declaration of function ‘_dxfccerror’ 
[-Werror=implicit-function-declaration]
   52 | #define yyerror _dxfccerror
  | ^~~
y.tab.c:1682:2: note: in expansion of macro ‘yyerror’
./_compparse.y: In function ‘_dxfccerror’:
./_compparse.y:432:47: error: implicit declaration of function 
‘_dxfcclexerror’; did you mean ‘_dxfccerror’? 
[-Werror=implicit-function-declaration]
cc1: some warnings being treated as errors
make[6]: *** [Makefile:961: _compparse.lo] Error 1


I have attached one debdiff and it can be built with it. So could you
upload it with it? I can team upload if nobody response with this sor
some days.

BTW, dx upstream has dead, so refer to:
https://trac.macports.org/ticket/61842


--
Regards,
--
  Bo YU

diff -Nru dx-4.4.4/debian/changelog dx-4.4.4/debian/changelog
--- dx-4.4.4/debian/changelog   2024-02-29 07:06:03.0 +0800
+++ dx-4.4.4/debian/changelog   2024-03-14 14:17:17.0 +0800
@@ -1,3 +1,11 @@
+dx (1:4.4.4-15.2) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Add -Wno-error=implicit-function-declaration into 
+DEB_CFLAGS_MAINT_APPEND. (Closes: #1066310)
+
+ -- Bo YU   Thu, 14 Mar 2024 14:17:17 +0800
+
 dx (1:4.4.4-15.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru dx-4.4.4/debian/rules dx-4.4.4/debian/rules
--- dx-4.4.4/debian/rules   2024-02-29 07:06:00.0 +0800
+++ dx-4.4.4/debian/rules   2024-03-14 14:17:05.0 +0800
@@ -4,6 +4,7 @@
 
 export DEB_BUILD_MAINT_OPTIONS=hardening=+all
 DEB_CFLAGS_MAINT_APPEND=-fsigned-char -fno-strict-aliasing -std=c++11
+DEB_CFLAGS_MAINT_APPEND=-Wno-error=implicit-function-declaration
 DEB_CXXFLAGS_MAINT_APPEND=-fsigned-char -fno-strict-aliasing -std=c++11
 DEB_HOST_ARCH ?= $(shell dpkg-architecture -qDEB_HOST_ARCH)
 ifeq ($(DEB_HOST_ARCH), alpha)


signature.asc
Description: PGP signature


Bug#1066840: no mention of iproute2 6.7.0-2.1 in changelog

2024-03-14 Thread Luca Boccassi
Control: tags -1 wontfix
Control: close -1

On Thu, 14 Mar 2024 at 07:30, Aníbal Monsalve Salazar  wrote:
>
> Package: iproute2
> Version: 6.8.0-1
> Severity: important
>
> Dear Maintainer,
>
> At https://tracker.debian.org/pkg/iproute2 it reads:
> [2024-03-12] Accepted iproute2 6.7.0-2.1 (source) into unstable (Helmut 
> Grohne)
>
> I cannot find the changelog entry listed below for iproute2 6.7.0-2.1 in
> the changelog of iproute2 6.8.0-1.
>
> iproute2 (6.7.0-2.1) unstable; urgency=medium
>
>   * Non-maintainer upload.
>   * Explicitly depend on libtirpc-dev. (Closes: #1065214)
>
>  -- Helmut Grohne   Tue, 12 Mar 2024 09:03:30 +0100

That was intentional and in agreement with Helmut as the same fix was
already queued in git before the NMU



Bug#1065329: O: numpy -- Fast array facility to the Python 3 language

2024-03-14 Thread Christian Kastner
Hi Timo,

On 2024-03-14 10:06, Timo Röhling wrote:
>> Having read up on debian-python, I have misread the situation. I think
>> there needs to be a policy resolution first.
> I don't understand what you mean. The orphaning process is not tied to
> DPT policy, is it?
> 
> FWIW, I am a regular user of this package and would also like to help
> maintain it.

I underspecified -- what I meant is resolution of both policy and the
active team dynamics.

In any case, if this isn't resolved soon, I'm also happy to contribute.

Best,
Christian



Bug#1065329: O: numpy -- Fast array facility to the Python 3 language

2024-03-14 Thread Timo Röhling

Hi Christian,

On Sat, 2 Mar 2024 23:11:15 +0100 Christian Kastner  
wrote:

Control: retitle -1 O: numpy -- Fast array facility to the Python 3 language
Control: tags -1 - pending

Having read up on debian-python, I have misread the situation. I think
there needs to be a policy resolution first.
I don't understand what you mean. The orphaning process is not tied 
to DPT policy, is it?


FWIW, I am a regular user of this package and would also like to 
help maintain it.



Cheers
Timo

--
⢀⣴⠾⠻⢶⣦⠀   ╭╮
⣾⠁⢠⠒⠀⣿⡁   │ Timo Röhling   │
⢿⡄⠘⠷⠚⠋⠀   │ 9B03 EBB9 8300 DF97 C2B1  23BF CC8C 6BDD 1403 F4CA │
⠈⠳⣄   ╰╯


signature.asc
Description: PGP signature


Bug#900572: Packaging PoC

2024-03-14 Thread David Prevot
control: tag -1 patch

Hi,

I’ve prepared a php-sqlsrv package for Bullseye (I had to stick with
version 5.10 for PHP 7.4), it should work almost out of the box for
Bookworm and unstable. I don’t intend to upload it to Debian proper, but
it’s available in a public repository.

https://gitea.evolix.org/dprevot/php-sqlsrv

Regards,
-- 
David Prévot
Marseille (37 rue Guibal, Pôle Média, 13003) / Paris / Montréal
http://evolix.com | Twitter: @Evolix @EvolixNOC | http://blog.evolix.com



Bug#900568: Packaging PoC

2024-03-14 Thread David Prevot
control: tag -1 patch

Hi,

I’ve prepared a php-pdo-sqlsrv package for Bullseye (I had to stick with
version 5.10 for PHP 7.4), it should work almost out of the box for
Bookworm and unstable. I don’t intend to upload it to Debian proper, but
it’s available in a public repository.

https://gitea.evolix.org/dprevot/php-pdo-sqlsrv

Regards,
-- 
David Prévot
Marseille (37 rue Guibal, Pôle Média, 13003) / Paris / Montréal
http://evolix.com | Twitter: @Evolix @EvolixNOC | http://blog.evolix.com



Bug#1066778: golang-github-containerd-go-runc: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 8 github.com/containerd/go-runc returned exit code 1

2024-03-14 Thread Shengjing Zhu
On Wed, Mar 13, 2024 at 11:05 PM Lucas Nussbaum  wrote:
>
> Source: golang-github-containerd-go-runc
> Version: 1.0.0-1
> Severity: serious
> Justification: FTBFS
> Tags: trixie sid ftbfs
> User: lu...@debian.org
> Usertags: ftbfs-20240313 ftbfs-trixie
>
[...]
> > console_test.go:42: mkdir /tmp/foo: not a directory
> > --- FAIL: TestTempConsoleWithXdgRuntimeDir (0.00s)

I wonder if your chroot doesn't have the /tmp directory?

-- 
Shengjing Zhu



Bug#1066138: [pkg-gnupg-maint] Bug#1066138: gnupg1: fails to build gpgkeys_ldap, probably due to -Werror=implicit-function-declaration

2024-03-14 Thread Sune Stolborg Vuorela
On Wednesday, March 13, 2024 7:10:13 PM CET Andreas Metzler wrote:
> Hello Thorsten,
> I have upload a fix for 2.2, probably will not be able to spend any time
> on 1.x or 2.4 before the weekend.

Looks like 2.4 is fixed upstream a couple of years
https://dev.gnupg.org/rGddc6f7d194918791ac9dff0e5af4b80933189afd

/Sune
-- 
I didn’t stop pretending when I became an adult, it’s just that when I was a 
kid I was pretending that I fit into the rules and structures of this world. 
And now that I’m an adult, I pretend that those rules and structures exist.
   - zefrank



Bug#1066841: rpm: hard Build-Depends on unportable package pandoc

2024-03-14 Thread Thorsten Glaser
retitle 1066841 rpm: hard Build-Depends on unportable package pandoc
thanks

Hi,

rpm also exhibits the same portability problem. Please see
whether it’s possible to use pandoc only during arch:all
builds or otherwise not in arch:any…

Thanks,
//mirabilos
-- 
This space for rent.

https://paypal.me/mirabilos to support my work.



Bug#902240: html-xml-utils: don't Build-Depends: man2html

2024-03-14 Thread Thorsten Glaser
ping

this (s/man2html/man2html-base/) would IMMENSELY help with
the current transitions, and I might NMU if no reaction



Bug#1066814: plotly: Please upgrade to latest upstream version

2024-03-14 Thread Andreas Tille
Hi Josue,

Am Wed, Mar 13, 2024 at 06:19:05PM -0600 schrieb Josue Ortega:
> 
> Hopefully, I'll be uploading the latest version next weekend. I've been quite
> busy with $DAILY_JOB.

Thank you for your quick response.  As a volunteer your $DAILY_JOB has
definitely preference.  To cover such situations I recommend team
maintenance which would enable team members to simply do some team
upload.  It might help you concentrating on other things if your
available time is limited.

Thank you for maintaining the package in any case
   Andreas.

-- 
http://fam-tille.de



Bug#1066801: pandas: FTBFS: /usr/lib/python3/dist-packages/dateutil/zoneinfo/__init__.py:26: UserWarning: I/O error(2): No such file or directory

2024-03-14 Thread Rebecca N. Palmer

Control: retitle -1 pandas: test-failing warning with new xarray

This is a warning being treated as an error, but the one in 
test_to_xarray (probably due to the new version of xarray), not the 
zoneinfo one.  This is a FutureWarning, so it should be OK to *use* the 
current pandas with the new xarray.


The same warning happens in autopkgtest but isn't treated as an error 
there, so didn't block the new xarray.


I intend to try fixing this later.



Bug#1066842: Updating extrepo-offline-data in Debian Stable

2024-03-14 Thread Wouter Verhelst
Package: release.debian.org
Control: affects -1 + src:extrepo-data
User: release.debian@packages.debian.org
Usertags: pu
Tags: bookworm
Severity: normal
Subject: bookworm-pu: package extrepo-data/1.0.5
thanks

[making this an official stable update request; for the full backstory,
please see the thread starting at
https://lists.debian.org/debian-release/2024/03/msg00076.html]]

On Thu, Mar 07, 2024 at 07:10:28PM +0100, Thomas Goirand wrote:
> On 3/7/24 06:57, Paul Gevers wrote:
> > Having said that and not knowing if it doesn't already do that, if
> > extrepro would update a cache when online, it's offline option could
> > also be refreshed at a convenience moment without the need for an
> > up-to-date package in stable. I hope it's needless to say that I don't
> > mean that this mechanisme should replace the data package, merely
> > complement it.
> 
> It's actually a very good idea to have such cache. Though as you wrote, it
> doesn't replace the data package, especially when one wants to use local
> mirror, with something like this:
> 
> apt-get install extrepo extrepo-offline-data
> extrepo enable --offlinedata --mirror http://mirror.example.com/haproxy

To give a bit more background here:

extrepo was originally designed to use an online, GPG-signed, metadata
repository. When you run an extrepo command and it needs to, extrepo
will download the metadata index and the signature on that, and then
verify that the signature is correct. All further information that it
needs is hashed with a cryptographically secure hash, and so can be
assumed to be safe.

extrepo provides two things: a (checked and vetted) URI for a repository
of external packages, and a (checked and vetted) GPG key that can sign
packages in that repository.

Accessing the metadata repository in the way described above however
requires direct access to that metadata repository, which is complicated
for air-gapped systems. While the location of that repository is
configurable, and in theory it is possible to write a tool which will
download the metadata plus all signatures plus all external files that
exist, that seems like quite a bit of work, and Thomas therefore
suggested an alternate solution whereby the extrepo metadata is also
packaged in Debian. Doing so only requires a person to mirror the
repository that they want to enable, and to override the mirror URL by
way of the --mirror option passed to extrepo. This way, extrepo will
enable the repository on the given mirror, and will ensure that the
relevant GPG key for the repository in question is provided to apt,
which can still save the user some work of having to manually download
and verify the GPG key.

The downside here however, is that most repositories are updated to add
support for a particular Debian release only after that Debian release
has been promoted to stable. This unfortunately reduces the usability of
the extrepo-offline-data package, which could be remedied by updating
the package in stable.

The extrepo-offline-data package, as the name implies, is a data-only
package. Apart from the changelog and copyright in /usr/share/doc, it
only contains metadata files under /usr/share/extrepo/offline-data.

Thanks for your consideration,

-- 
 w@uter.{be,co.za}
wouter@{grep.be,fosdem.org,debian.org}

I will have a Tin-Actinium-Potassium mixture, thanks.



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

2024-03-14 Thread Antonio Valentino

Dear Lucas,
thanks for reporting.

On Wed, 13 Mar 2024 15:58:32 +0100 Lucas Nussbaum  wrote:

Source: pycoast
Version: 1.7.0+dfsg-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240313 ftbfs-trixie

Hi,

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


Relevant part (hopefully):


[CUT]


 ERRORS 
 ERROR collecting pycoast/tests/test_pycoast.py 
/usr/lib/python3/dist-packages/pluggy/_hooks.py:501: in __call__
return self._hookexec(self.name, self._hookimpls.copy(), kwargs, 
firstresult)
/usr/lib/python3/dist-packages/pluggy/_manager.py:119: in _hookexec
return self._inner_hookexec(hook_name, methods, kwargs, firstresult)
/usr/lib/python3/dist-packages/_pytest/python.py:278: in 
pytest_pycollect_makeitem
return list(collector._genfunctions(name, obj))
/usr/lib/python3/dist-packages/_pytest/python.py:507: in _genfunctions
self.ihook.pytest_generate_tests.call_extra(methods, 
dict(metafunc=metafunc))
/usr/lib/python3/dist-packages/pluggy/_hooks.py:562: in call_extra
return self._hookexec(self.name, hookimpls, kwargs, firstresult)
/usr/lib/python3/dist-packages/pluggy/_manager.py:119: in _hookexec
return self._inner_hookexec(hook_name, methods, kwargs, firstresult)
/usr/lib/python3/dist-packages/pytest_lazyfixture.py:74: in 
pytest_generate_tests
normalize_metafunc_calls(metafunc, 'funcargs')
/usr/lib/python3/dist-packages/pytest_lazyfixture.py:81: in 
normalize_metafunc_calls
calls = normalize_call(callspec, metafunc, valtype, used_keys)
/usr/lib/python3/dist-packages/pytest_lazyfixture.py:105: in normalize_call
valtype_keys = set(getattr(callspec, valtype).keys()) - used_keys
E   AttributeError: 'CallSpec2' object has no attribute 'funcargs'
=== warnings summary ===
../../../../../../usr/lib/python3/dist-packages/_pytest/python.py:507
  /usr/lib/python3/dist-packages/_pytest/python.py:507: 
PluggyTeardownRaisedWarning: A plugin raised an exception during an old-style 
hookwrapper teardown.
  Plugin: lazy-fixture, Hook: pytest_generate_tests
  AttributeError: 'CallSpec2' object has no attribute 'funcargs'
  For more information see 
https://pluggy.readthedocs.io/en/stable/api_reference.html#pluggy.PluggyTeardownRaisedWarning
self.ihook.pytest_generate_tests.call_extra(methods, 
dict(metafunc=metafunc))

-- Docs: https://docs.pytest.org/en/stable/how-to/capture-warnings.html
=== short test summary info 
ERROR ../../../pycoast/tests/test_pycoast.py - AttributeError: 'CallSpec2' ob...
 Interrupted: 1 error during collection 
= 1 warning, 1 error in 0.26s ==


the issue seems to be related to the pytest-lazyfixture package.
See also https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063957.
I will reassign.


regards
--
Antonio Valentino



Bug#1066279: [Debian-zh-dev] Bug#1066279: Bug#1066279: unicon: FTBFS: cin2tab.c:238:13: error: implicit declaration of function ‘tolower’ [-Werror=implicit-function-declaration]

2024-03-14 Thread Aron Xu
On Thu, Mar 14, 2024 at 10:34 AM xiao sheng wen  wrote:
>
> Hi,
>
> Thanks for your report.
>
> I'd uploaded the new version in mentors to fix this bug.
>
> https://mentors.debian.net/package/unicon/
>
> Welcome to review and upload.
>

This has been sponsored to Sid, thanks for your contribution!

Regards,
Aron



Bug#1066840: no mention of iproute2 6.7.0-2.1 in changelog

2024-03-14 Thread Aníbal Monsalve Salazar
Package: iproute2
Version: 6.8.0-1
Severity: important

Dear Maintainer,

At https://tracker.debian.org/pkg/iproute2 it reads:
[2024-03-12] Accepted iproute2 6.7.0-2.1 (source) into unstable (Helmut Grohne) 

I cannot find the changelog entry listed below for iproute2 6.7.0-2.1 in
the changelog of iproute2 6.8.0-1.

iproute2 (6.7.0-2.1) unstable; urgency=medium

  * Non-maintainer upload.
  * Explicitly depend on libtirpc-dev. (Closes: #1065214)

 -- Helmut Grohne   Tue, 12 Mar 2024 09:03:30 +0100

Thank you,

Aníbal



Bug#1059308: Tag bugs pending

2024-03-14 Thread Andreas Tille
Control: tags -1 pending

I'm just marking these bugs pending for next upload.  They were even
closed in recent Debian package but since they are concerning CVEs it
might be better to close these inside a changelog of next upload.

Kind regards
   Andreas.

-- 
http://fam-tille.de



Bug#1041552: HFS/HFS+ are insecure

2024-03-14 Thread Marco d'Itri
On Mar 13, Michael Biebl  wrote:

> > So I propose this content for a file like
> > /usr/lib/udev/rules.d/75-insecure-fs.rules:
> Just curious: Why did you pick priority 75?
I can't remember.

-- 
ciao,
Marco


signature.asc
Description: PGP signature


Bug#1064946: morph's abandoned packages (list)

2024-03-14 Thread Julian Gilbey
Dear all (and Bcc-ing the RM bugs),

For information, here is a list of packages that morph has either
requested removal of or orphaned.  If you are interested in taking one
or more of them on, that would be great!

Removal requested:

#1066146 RM: flask-basicauth -- ROM; RC buggy, dead upstream, leaf package
#1065141 RM: gmplot -- ROM; leaf package
#1064947 RM: nb2plots -- ROM; leaf package
#1065200 RM: overpass -- ROM; leaf package
#1065199 RM: pprintpp -- ROM; leaf package
#1065045 RM: pyannotate -- ROM; leaf package
#1065201 RM: python-overpy -- ROM; leaf package
#1065202 RM: python-ppmd -- ROM; leaf package
#1064946 RM: sphinx-a4doc -- ROM; leaf package

Recently-orphaned packages (removing those in wnpp which have been
retitled "ITA") sorted alphabetically; these could, of course, be
brought into team maintenance.

#1065235 O: basemap -- matplotlib toolkit to plot on map projections
#1065243 O: colorspacious -- library for doing colorspace conversions
#1065151 O: commonmark -- Python parser for the CommonMark Markdown spec
#1065246 O: contourpy -- Python library for calculating contours of 2D 
quadrilateral grids
#1065248 O: cppy -- C++ headers for (Python) C extension development
#1065139 O: dot2tex -- Graphviz to LaTeX converter
#1065140 O: fastkml -- fast KML processing
#1065142 O: html5lib -- HTML parser/tokenizer based on the WHATWG HTML5 
specification
#1065244 O: kiwisolver -- fast implementation of the Cassowary constraint 
solver
#1065238 O: lazy-object-proxy -- Python 3 fast and thorough lazy object 
proxy
#1065037 O: m2crypto -- Python wrapper for the OpenSSL library
#1065325 O: matplotlib -- Python based plotting system
#1065143 O: mkautodoc -- AutoDoc for MarkDown
#1065042 O: mpl-sphinx-theme -- documentation for the mpl-sphinx-theme 
Python library
#1065220 O: mpmath -- library for arbitrary-precision floating-point 
arithmetic
#1065224 O: mysql-connector-python -- pure Python implementation of MySQL 
Client/Server protocol
#1065198 O: networkx -- tool to create, manipulate and study complex 
networks
#1065329 O: numpy -- Fast array facility to the Python 3 language
#1065221 O: py7zr -- pure Python 7-zip library
#1065222 O: pychm -- Python binding for CHMLIB
#1065231 O: pydot -- Python interface to Graphviz's dot
#1065152 O: pygeoif -- basic implementation of the __geo_interface__
#1065036 O: pyopenssl -- Python wrapper around the OpenSSL library
#1065149 O: pyproject-metadata -- Dataclass for PEP 621 metadata with 
support for [core metadata] generation
#1065223 O: pysimplesoap -- simple and lightweight SOAP Library
#1064977 O: python-cryptography-vectors -- Test vectors for 
python-cryptography
#1065327 O: python-levenshtein -- extension for computing string 
similarities and edit distances
#1065025 O: sphinx-book-theme -- clean book theme for scientific 
explanations and documentation with Sphinx
#1065026 O: sphinx-bootstrap-theme -- bootstrap theme for Sphinx
#1065030 O: sphinxcontrib-log-cabinet -- Organize changelog directives in 
Sphinx docs
#1065027 O: sphinx-copybutton -- sphinx extension to add a "copy" button to 
code blocks
#1065028 O: sphinx-gallery -- extension that builds an HTML gallery of 
examples from Python scripts
#1065029 O: sphinx-panels -- documentation for the sphinx-panels Python 
library
#1065043 O: sphinxtesters -- utilities for testing Sphinx extensions
#1064948 O: texext -- sphinx extensions for working with LaTeX math

There's also an old ITP that was closed:

#1015231 ITP: sphinx-theme-builder -- tool for authoring Sphinx themes with 
a simple (opinionated) workflow

Best wishes,

   Julian



Bug#1066839: pipewire: ftbfs with 64-bit time_t

2024-03-14 Thread Steve Langasek
Package: pipewire
Version: 1.0.3-1.1
Severity: serious
Tags: patch
Justification: ftbfs
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu noble ubuntu-patch

Dear maintainers,

pipewire fails to build from source on 32-bit architectures under 64-bit
time_t, because it has a module that legitimately un-sets _FILE_OFFSET_BITS
for building but this is not allowed without also unsetting _TIME_BITS.

Since this is a legitimate un-setting of _FILE_OFFSET_BITS in order to get
access to the necessary libc6 prototypes and macros, and since the functions
being intercepted are not sensitive to time_t, the simplest solution is to
also unset _TIME_BITS.

Please see the attached patch, which has been uploaded to Ubuntu to fix this
build failure.

Thanks for considering,
-- 
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 pipewire-1.0.3/debian/control pipewire-1.0.3/debian/control
--- pipewire-1.0.3/debian/control   2024-03-04 08:54:55.0 -0800
+++ pipewire-1.0.3/debian/control   2024-03-13 23:11:56.0 -0700
@@ -1,8 +1,7 @@
 Source: pipewire
 Section: libs
 Priority: optional
-Maintainer: Ubuntu Developers 
-XSBC-Original-Maintainer: Utopia Maintenance Team 

+Maintainer: Utopia Maintenance Team 

 Uploaders: Jeremy Bicha ,
Dylan Aïssi 
 Build-Depends: dpkg-dev (>= 1.22.5), debhelper-compat (= 13),
diff -Nru pipewire-1.0.3/debian/patches/64-bit-time-t-compat.patch 
pipewire-1.0.3/debian/patches/64-bit-time-t-compat.patch
--- pipewire-1.0.3/debian/patches/64-bit-time-t-compat.patch1969-12-31 
16:00:00.0 -0800
+++ pipewire-1.0.3/debian/patches/64-bit-time-t-compat.patch2024-03-13 
23:11:47.0 -0700
@@ -0,0 +1,21 @@
+Description: 64-bit time_t compatibility for v4l2 module
+ The v4l2 build unsets _FILE_OFFSET_BITS, which is not allowed when setting
+ _TIME_BITS=64.  Having verified that nothing in this module is sensitive to
+ 64-bit time_t (none of the functions it intercepts handle time), we also
+ unset _TIME_BITS to allow this to build as before.
+Author: Steve Langasek 
+Forwarded: no
+Last-Update: 2024-03-13
+
+Index: pipewire-1.0.3/pipewire-v4l2/src/meson.build
+===
+--- pipewire-1.0.3.orig/pipewire-v4l2/src/meson.build
 pipewire-1.0.3/pipewire-v4l2/src/meson.build
+@@ -12,6 +12,7 @@
+   '-U_FILE_OFFSET_BITS',
+   '-D_FILE_OFFSET_BITS=32',
+   '-D_LARGEFILE64_SOURCE',
++  '-U_TIME_BITS',
+   '-fvisibility=hidden',
+ ]
+ 
diff -Nru pipewire-1.0.3/debian/patches/series 
pipewire-1.0.3/debian/patches/series
--- pipewire-1.0.3/debian/patches/series2024-03-04 08:54:55.0 
-0800
+++ pipewire-1.0.3/debian/patches/series2024-03-13 23:09:06.0 
-0700
@@ -19,3 +19,4 @@
 snap/snap-policy-Manage-ENOPROTOOPT-error-in-aa_getpeercon.patch
 snap/snap-policy-ensure-audio-works-with-.deb-snapd.patch
 snap/snap-policy-fix-memory-leak.patch
+64-bit-time-t-compat.patch


Bug#1066838: hplip: Files remain after purge

2024-03-14 Thread Scott Kitterman
Package: hplip
Version: 3.22.10+dfsg0-2
Severity: important

After removing and then purging hplip, the __pycache__ directories
remain.

# apt purge hplip
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following packages will be REMOVED:
  hplip*
0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] y
(Reading database ... 358577 files and directories currently installed.)
Purging configuration files for hplip (3.22.10+dfsg0-2) ...
Processing triggers for dbus (1.14.10-1~deb12u1) ...

# ls -R /usr/share/hplip/
/usr/share/hplip/:
base  copier  fax  installer  pcard  prnt  __pycache__  scan  ui5

/usr/share/hplip/base:
pexpect  __pycache__

/usr/share/hplip/base/pexpect:
__pycache__

/usr/share/hplip/base/pexpect/__pycache__:

/usr/share/hplip/base/__pycache__:

/usr/share/hplip/copier:
__pycache__

/usr/share/hplip/copier/__pycache__:

/usr/share/hplip/fax:
__pycache__

/usr/share/hplip/fax/__pycache__:

/usr/share/hplip/installer:
__pycache__

/usr/share/hplip/installer/__pycache__:

/usr/share/hplip/pcard:
__pycache__

/usr/share/hplip/pcard/__pycache__:

/usr/share/hplip/prnt:
__pycache__

/usr/share/hplip/prnt/__pycache__:

/usr/share/hplip/__pycache__:

/usr/share/hplip/scan:
__pycache__

/usr/share/hplip/scan/__pycache__:

/usr/share/hplip/ui5:
__pycache__

/usr/share/hplip/ui5/__pycache__:

Scott K


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

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

Versions of packages hplip depends on:
ii  adduser3.134
ii  cups   2.4.2-3+deb12u5
pn  hplip-data 
ii  libc6  2.36-9+deb12u4
ii  libcups2   2.4.2-3+deb12u5
ii  libdbus-1-31.14.10-1~deb12u1
ii  libhpmud0  3.22.10+dfsg0-2
ii  libpython3.11  3.11.2-6
pn  libsane-hpaio  
ii  libsane1   1.2.1-2
ii  lsb-base   11.6
ii  printer-driver-hpcups  3.22.10+dfsg0-2
ii  python33.11.2-1+b1
ii  python3-dbus   1.3.2-4+b1
ii  python3-gi 3.42.2-3+b1
pn  python3-pexpect
ii  python3-pil9.4.0-1.1+b1
pn  python3-reportlab  
ii  sysvinit-utils [lsb-base]  3.06-4
ii  wget   1.21.3-1+b2
ii  xz-utils   5.4.1-0.2

Versions of packages hplip recommends:
ii  avahi-daemon  0.8-10
ii  policykit-1   122-3
ii  printer-driver-postscript-hp  3.22.10+dfsg0-2
ii  sane-utils1.2.1-2

Versions of packages hplip suggests:
pn  hplip-doc  
pn  hplip-gui  
ii  python3-notify20.3-5
ii  system-config-printer  1.5.18-1



Bug#1066837: mpi4py: FTBFS: Unable to generate documentation

2024-03-14 Thread Zixing Liu
Package: mpi4py
Severity: serious
Tags: patch
User: zixing@canonical.com
Usertags: origin-ubuntu noble ubuntu-patch

Dear Maintainer,

mpi4py failed to build from source after Python 3.12 and Sphinx upgrade.
Please find the patch attached that fixes the Sphinx documentation generation
issue and also a partial fix to the InterSphinx online requirements.

Due to a packaging issue in numpy, the InterSphinx of numpy isn't included
in the package, so linking the documentation from numpy is not possible
at the moment.

  * Un-break Sphinx documentation generation by removing PYTHONPATH overrides.
  * Add a patch to make Intersphinx read the cross-documentation index
from local filesystem. (LP: #2057848)


Thanks for considering the patch.


-- System Information:
Debian Release: bookworm/sid
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.5.0-25-generic (SMP w/10 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_CA:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff -Nru mpi4py-3.1.5/debian/control mpi4py-3.1.5/debian/control
--- mpi4py-3.1.5/debian/control 2024-03-13 12:30:07.0 -0600
+++ mpi4py-3.1.5/debian/control 2024-03-13 15:33:29.0 -0600
@@ -17,7 +16,8 @@
python3-setuptools
 Build-Depends-Indep: texinfo, texlive,
  latexmk, tex-gyre,
- texlive-latex-extra
+ texlive-latex-extra,
+ python3-doc
 Standards-Version: 4.6.2
 Vcs-Browser: https://salsa.debian.org/science-team/mpi4py
 Vcs-Git: https://salsa.debian.org/science-team/mpi4py.git
diff -Nru mpi4py-3.1.5/debian/patches/intersphinx_use_local_inventory.patch 
mpi4py-3.1.5/debian/patches/intersphinx_use_local_inventory.patch
--- mpi4py-3.1.5/debian/patches/intersphinx_use_local_inventory.patch   
1969-12-31 17:00:00.0 -0700
+++ mpi4py-3.1.5/debian/patches/intersphinx_use_local_inventory.patch   
2024-03-13 15:33:29.0 -0600
@@ -0,0 +1,18 @@
+Description: Use local InterSphinx inventory data
+Author: Zixing Liu 
+Forwarded: not-needed
+Last-Update: 2024-03-13
+
+Index: mpi4py/docs/source/usrman/conf.py
+===
+--- mpi4py.orig/docs/source/usrman/conf.py
 mpi4py/docs/source/usrman/conf.py
+@@ -90,7 +90,7 @@ autosummary_context = {
+ }
+ 
+ intersphinx_mapping = {
+-'python': ('https://docs.python.org/3/', None),
++'python': ('https://docs.python.org/3/', 
('/usr/share/doc/python3/html/objects.inv', None)),
+ 'numpy': ('https://numpy.org/doc/stable/', None),
+ }
+ 
diff -Nru mpi4py-3.1.5/debian/patches/series mpi4py-3.1.5/debian/patches/series
--- mpi4py-3.1.5/debian/patches/series  2024-02-20 03:49:49.0 -0700
+++ mpi4py-3.1.5/debian/patches/series  2024-03-13 15:29:22.0 -0600
@@ -7,3 +7,4 @@
 docs_privacy.patch
 io_long_double_i386_2d868d7.patch
 skip_testPackUnpackExternal_sparc64.patch
+intersphinx_use_local_inventory.patch
diff -Nru mpi4py-3.1.5/debian/rules mpi4py-3.1.5/debian/rules
--- mpi4py-3.1.5/debian/rules   2024-02-20 03:49:49.0 -0700
+++ mpi4py-3.1.5/debian/rules   2024-03-13 15:28:23.0 -0600
@@ -64,8 +64,7 @@
--build-args "--mpicc=/usr/bin/mpicc$(MPI) 
--mpicxx=/usr/bin/mpicxx$(MPI)"
 
 override_dh_auto_build-indep: override_dh_auto_build-arch
-   PYTHONPATH=`pybuild --print "{build_dir}"` \
-make -C docs/source/usrman/ html man info latexpdf SPHINXOPTS="-D 
today=\"$(BUILD_DATE)\""
+   make -C docs/source/usrman/ html man info latexpdf SPHINXOPTS="-D 
today=\"$(BUILD_DATE)\""
 
 override_dh_auto_install:
dh_auto_install


<    1   2