Bug#1042628: case: FTBFS with Sphinx 7.1, docutils 0.20: make[1]: *** [debian/rules:13: override_dh_auto_build] Error 2

[Paul Wise]

Control: tags -1 + unreproducible

On Sun, 30 Jul 2023 20:30:36 +0200 Lucas Nussbaum wrote:

> case fails to build with Sphinx 7.1 and docutils 0.20, both of which
> are currently available in experimental.

I am unable to reproduce this when building case 1.5.3+dfsg-5 with
experimental python3-sphinx 7.2.6-1 and python3-docutils 0.20.1+dfsg-1.

Could you recheck this build failure and close it if it is fixed?

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#1055042: FAI client does not boot to Hard Disk after installation

[Suresh Solomon]

 I found the problem my DHCP was pointing to the wrong IP.
On Sunday, November 5, 2023 at 11:53:27 AM GMT+8, Suresh Solomon 
 wrote:  
 
  Hi Thomas,
I found the problem to be the nameserver configured is referring to the 
faiserver.
/etc/resolve.conf
I am using a public nameserver 8.8.8.8.




>From the configuration I see that 8.8.8.8 is already set.



Where can I change this?
Thank you 
Suresh
On Monday, October 30, 2023 at 03:15:13 PM GMT+8, Thomas Lange 
 wrote:  
 
 Hi,

you have a major network problem.

"Temorary failure resolving 'deb.debian.org'"

That's why a lot of packages (maybe all) are not installed.
Please fix problem, otherwise you will never have a bootable
installation.
For e.g. grub-efi is not installed, and without grub your computer
cannot boot.

-- 
regards Thomas

Bug#1055375: RFS: python-scienceplots/2.1.0-2 -- Matplotlib styles for scientific figures

[Yogeswaran Umasankar]

Package: sponsorship-requests
Severity: normal
X-Debbugs-Cc: kd8...@gmail.com

Dear mentors,

I am looking for a sponsor for my package "python-scienceplots":

 * Package name : python-scienceplots
   Version  : 2.1.0-2
   Upstream contact : John Garrett 
 * URL  : https://github.com/garrettj403/SciencePlots
 * License  : MIT
 * Vcs  : https://salsa.debian.org/yogu/python-scienceplots
   Section  : python

The source builds the following binary packages:

  python3-scienceplots - Matplotlib styles for scientific figures

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

  https://mentors.debian.net/package/python-scienceplots/

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

  dget -x 
https://mentors.debian.net/debian/pool/main/p/python-scienceplots/python-scienceplots_2.1.0-2.dsc

Changes since the last upload:

 python-scienceplots (2.1.0-2) unstable; urgency=medium
 .
   * Fixing 'a new source-only upload is needed to allow
 testing migration'. (Closes: #1055373)

Regards,
-- 
  Yogeswaran Umasankar

Bug#1055042: FAI client does not boot to Hard Disk after installation

[Suresh Solomon]

 Hi Thomas,
I found the problem to be the nameserver configured is referring to the 
faiserver.
/etc/resolve.conf
I am using a public nameserver 8.8.8.8.




>From the configuration I see that 8.8.8.8 is already set.



Where can I change this?
Thank you 
Suresh
On Monday, October 30, 2023 at 03:15:13 PM GMT+8, Thomas Lange 
 wrote:  
 
 Hi,

you have a major network problem.

"Temorary failure resolving 'deb.debian.org'"

That's why a lot of packages (maybe all) are not installed.
Please fix problem, otherwise you will never have a bootable
installation.
For e.g. grub-efi is not installed, and without grub your computer
cannot boot.

-- 
regards Thomas
  

Bug#1055374: RFS: python-art/6.1-2 -- ASCII art

[Yogeswaran Umasankar]

Package: sponsorship-requests
Severity: normal
X-Debbugs-Cc: kd8...@gmail.com

Dear mentors,

I am looking for a sponsor for my package "python-art":

 * Package name : python-art
   Version  : 6.1-2
   Upstream contact : Sepand Haghighi 
 * URL  : https://github.com/sepandhaghighi/art
 * License  : MIT
 * Vcs  : https://salsa.debian.org/yogu/python-art
   Section  : python

The source builds the following binary packages:

  python3-art - ASCII art

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

  https://mentors.debian.net/package/python-art/

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

  dget -x 
https://mentors.debian.net/debian/pool/main/p/python-art/python-art_6.1-2.dsc

Changes since the last upload:

 python-art (6.1-2) unstable; urgency=medium
 .
   * Fixing 'a new source-only upload is needed to allow
 testing migration'. (Closes: #1055367)

Regards,
-- 
  Yogeswaran Umasankar

Bug#1055373: python3-scienceplots: A new source-only upload is needed to allow testing migration

[Yogeswaran Umasankar]

Package: python3-scienceplots
Version: 2.1.0-1
Severity: normal
X-Debbugs-Cc: kd8...@gmail.com

Hi,
A new source-only upload is needed to allow testing migration.

Thank you,
Yogeswaran Umasankar

-- System Information:
Debian Release: 12.2
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 
'unstable'), (500, 'stable')
Architecture: arm64 (aarch64)

Kernel: Linux 6.1.0-13-arm64 (SMP w/4 CPU threads)
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 python3-scienceplots depends on:
ii  cm-super 0.3.4-17
ii  dvipng   1.15-1.1
ii  init-system-helpers  1.65.2
ii  python3  3.11.2-1+b1
ii  python3-matplotlib   3.6.3-1+b1
ii  python3-numpy1:1.24.2-1

Versions of packages python3-scienceplots recommends:
ii  texlive-fonts-recommended  2023.20231007-1
ii  texlive-latex-extra2023.20231007-2

python3-scienceplots suggests no packages.

-- no debconf information

Bug#1055372: btrfs-progs: new upstream version

[Christoph Anton Mitterer]

Package: btrfs-progs
Version: 6.3.2-1
Severity: wishlist


Hey.

6.6 is out ad 6.3 is rather outdated now :-)

Cheers,
Chris.

Bug#1055371: libpolly-17-dev:i386: multi-arch issues

[Witold Baryluk]

Package: libpolly-17-dev
Version: 1:17.0.4-1
Severity: normal
X-Debbugs-Cc: witold.bary...@gmail.com

Dear Maintainer,

# ii  libpolly-17-dev:amd64   1:17.0.4-1
amd64High-level loop and data-locality 
optimizer


# apt install libpolly-17-dev:i386


Preparing to unpack .../libpolly-17-dev_1%3a17.0.4-1_i386.deb ...
Unpacking libpolly-17-dev:i386 (1:17.0.4-1) ...
dpkg: error processing archive 
/var/cache/apt/archives/libpolly-17-dev_1%3a17.0.4-1_i386.deb (--unpack):
 trying to overwrite shared '/usr/lib/llvm-17/lib/libPolly.a', which is 
different from other instances of package libpolly-17-dev:i386





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

Kernel: Linux 6.1.0-9-amd64 (SMP w/32 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE, TAINT_SOFTLOCKUP
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

Bug#1055370: debci setup should include security repositories

[Santiago Ruano Rincón]

Package: debci
Version: 3.7
Severity: normal

Dear debci maintainers,

Is there any reason why `debci setup ...` doen't configure the security
repostories inside the lxc containers? This is the sources.list of a
just created autopkgtest-bookworm-amd64 container:

deb http://deb.debian.org/debian bookworm main contrib non-free 
non-free-firmware
deb-src http://deb.debian.org/debian bookworm main contrib non-free 
non-free-firmware
deb http://deb.debian.org/debian-debug bookworm-debug main contrib non-free 
non-free-firmware
deb-src http://deb.debian.org/debian-debug bookworm-debug main contrib 
non-free non-free-firmware

Cheers,

 -- Santiago

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

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

Versions of packages debci depends on:
ii  adduser 3.137
ii  amqp-tools  0.11.0-1+b1
ii  curl8.4.0-2
ii  dctrl-tools 2.24-3+b1
ii  debian-archive-keyring  2023.4
ii  debootstrap 1.0.133
ii  distro-info 1.7
ii  fonts-font-awesome  5.0.10+really4.7.0~dfsg-4.1
ii  inotify-tools   4.23.9.0-1
ii  jq  1.7-1
ii  libjs-bootstrap 3.4.1+dfsg-3
ii  libjs-jquery3.6.1+dfsg+~3.5.14-1
ii  libjs-jquery-flot   4.2.1+dfsg-6
ii  moreutils   0.67-1
ii  patchutils  0.4.2-1
ii  retry   1.0.5-3
ii  rsync   3.2.7-1
ii  ruby1:3.1
ii  ruby-activerecord   2:6.1.7.3+dfsg-2
ii  ruby-bunny  2.19.0-2
ii  ruby-erubi  1.12.0-1
ii  ruby-kaminari-activerecord  1.2.2-1
ii  ruby-omniauth-gitlab4.1.0-1
ii  ruby-pg 1.5.3-1
ii  ruby-sinatra3.0.5-3
ii  ruby-sinatra-contrib3.0.5-3
ii  ruby-sqlite31.4.2-4+b3
ii  ruby-thor   1.2.2-1
ii  sudo1.9.14p2-1

Versions of packages debci recommends:
ii  systemd-timesyncd [time-daemon]  254.5-1

Versions of packages debci suggests:
ii  apt-cacher-ng   3.7.4-1+b2
pn  auto-apt-proxy  

-- Configuration Files:
/etc/sudoers.d/debci [Errno 13] Permission denied: '/etc/sudoers.d/debci'

-- no debconf information

Bug#1041491: (no subject)

[Don Armstrong]

I'm just reiterating the conversation I had with Santiago for
transparency and to explain what happened here:

This bug was originally tagged with "sid trixie". This means that the
for the purposes of archival, the BTS only needs to care if the bug has
been fixed in sid and trixie, and it should ignore whether it should be
fixed in bookworm. When the bug was fixed in sid and trixie, the BTS
archived it.

You rarely want to tag a bug with any of the distribution tags. [The
major exception is where a bug is present in a distribution because of
the versions of other packages in that distribution, not latently
present in the package itself, for example when an interface is
deprecated/removed.]

-- 
Don Armstrong  https://www.donarmstrong.com

This isn't life in the fast lane, it's life in the oncoming traffic
 -- Terry Pratchett

Bug#1055369: libxfont: Separate out documentation build

[Samuel Thibault]

Source: libxfont
Version: 1:2.0.6-1
Severity: normal
Tags: patch

Hello,

libxfont currently build-depends on w3m, which makes it part of a long
build dependency through imlib and whatnot image libraries. The w3m
dependency is actually only for building documentation. The attached
patch adds a nodoc build profile. This makes bootstraping a new Debian
port much easier.

Samuel

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

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

-- 
Samuel
---
Pour une évaluation indépendante, transparente et rigoureuse !
Je soutiens la Commission d'Évaluation de l'Inria.
--- debian/control.original 2023-11-05 02:28:23.0 +
+++ debian/control  2023-11-05 02:28:30.0 +
@@ -15,7 +15,7 @@
  libbz2-dev,
  xutils-dev (>= 1:7.5+4),
 # devel-docs
- xmlto, xorg-sgml-doctools (>= 1:1.7), w3m,
+ xmlto , xorg-sgml-doctools (>= 1:1.7) , w3m ,
 Standards-Version: 4.5.0
 Vcs-Git: https://salsa.debian.org/xorg-team/lib/libxfont
 Vcs-Browser: https://salsa.debian.org/xorg-team/lib/libxfont
--- debian/rules.original   2023-11-05 02:31:39.0 +
+++ debian/rules2023-11-05 02:33:48.0 +
@@ -11,12 +11,17 @@
 # Strip -Bsymbolic-functions (set by default on Ubuntu) to avoid breakages:
 LDFLAGS := $(LDFLAGS:-Wl,-Bsymbolic-functions=)
 
+ifeq (,$(filter nodoc,$(DEB_BUILD_PROFILES)))
+DOC = --enable-devel-docs --with-xmlto
+else
+DOC = --disable-devel-docs --without-xmlto
+endif
+
 CONFFLAGS += \
--disable-fc \
--enable-builtins \
--enable-pcfformat \
--enable-bdfformat \
-   --enable-devel-docs \
--without-fop \
--disable-silent-rules \
CFLAGS="$(CFLAGS)" \
@@ -30,8 +35,8 @@
rm -rf build-udeb/ debian/tmp-udeb/
 
 override_dh_auto_configure:
-   dh_auto_configure $(OOT)-main/ -- --with-bzip2--with-xmlto
$(CONFFLAGS)
-   dh_auto_configure $(OOT)-udeb/ -- --without-bzip2 --without-xmlto 
$(CONFFLAGS)
+   dh_auto_configure $(OOT)-main/ -- --with-bzip2$(CONFFLAGS) $(DOC)
+   dh_auto_configure $(OOT)-udeb/ -- --without-bzip2 $(CONFFLAGS)
 
 override_dh_auto_build:
$(MAKE) -C build-main/

Bug#1055368: libxmu: Separate out documentation build

[Samuel Thibault]

Source: libxmu
Version: 1.1.3-3
Severity: normal
Tags: patch

Hello,

libxmu currently build-depends on w3m, which makes it part of a long
build dependency through imlib and whatnot image libraries. The w3m
dependency is actually only for building documentation, which is already
separated into an arch:all binary package. The attached patch completes
the separation by separating out the build dependencies. This makes
bootstraping a new Debian port much easier.

Samuel

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

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

-- 
Samuel
---
Pour une évaluation indépendante, transparente et rigoureuse !
Je soutiens la Commission d'Évaluation de l'Inria.
--- debian/control.original 2023-11-05 03:18:06.596293166 +0100
+++ debian/control  2023-11-05 03:18:13.500335188 +0100
@@ -10,7 +10,7 @@
  pkg-config,
  quilt,
  xutils-dev (>= 1:7.6+2),
-# devel-docs:
+Build-Depends-Indep:
  xmlto (>= 0.0.22),
  xorg-sgml-doctools (>= 1:1.8),
  w3m,
--- debian/rules.original   2023-11-05 03:18:57.532603448 +0100
+++ debian/rules2023-11-05 03:19:34.300827775 +0100
@@ -14,11 +14,13 @@
 %:
dh $@ --with quilt --builddirectory=build/
 
-override_dh_auto_configure:
+override_dh_auto_configure-arch: docflags =
+override_dh_auto_configure-indep: docflags = --with-xmlto
+override_dh_auto_configure-arch override_dh_auto_configure-indep::
dh_auto_configure -- \
--disable-silent-rules \
--docdir=\$${prefix}/share/doc/libxmu-headers \
-   --with-xmlto \
+   $(docflags) \
--without-fop
 
 override_dh_auto_install:

Bug#1055367: python3-art: A new source-only upload is needed to allow testing migration

[Yogeswaran Umasankar]

Package: python3-art
Version: 6.1-1
Severity: normal
X-Debbugs-Cc: kd8...@gmail.com

Hi,
A new source-only upload is needed to allow testing migration.

Thank you,
Yogeswaran Umasankar

-- System Information:
Debian Release: 12.2
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 
'unstable'), (500, 'stable')
Architecture: arm64 (aarch64)

Kernel: Linux 6.1.0-13-arm64 (SMP w/4 CPU threads)
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 python3-art depends on:
ii  init-system-helpers  1.65.2
ii  python3  3.11.2-1+b1

python3-art recommends no packages.

python3-art suggests no packages.

-- no debconf information

Bug#1055162: ITP: libhinoko -- I/O library for IEEE 1394 isochronous communication

[Takashi Sakamoto]

I uploaded debian package to mentors.debian.net:

* https://mentors.debian.net/package/libhinoko/

I'm glad if you are sponsor of the project.


Regards

Bug#1055366: py3k: format ignores leading 0 when _ is used

[Thorsten Glaser]

Package: python3.11
Version: 3.11.6-3
Severity: normal
Tags: upstream
X-Debbugs-Cc: t...@mirbsd.de, report...@stoffels.it

>>> i = int.from_bytes(b'2345', 'little')
>>> hex(i)
'0x3534333231313131'
>>> format(i, '064b')
'001101010011011100110011001000110001001100010011000100110001'
>>> format(i, '064_b')
'11_0101_0011_0100_0011_0011_0011_0010_0011_0001_0011_0001_0011_0001_0011_0001'

Expected output for the last line:
'0011_0101_0011_0100_0011_0011_0011_0010_0011_0001_0011_0001_0011_0001_0011_0001'


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

Kernel: Linux 5.10.0-26-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_FIRMWARE_WORKAROUND
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/lksh
Init: sysvinit (via /sbin/init)

Versions of packages python3.11 depends on:
ii  libpython3.11-stdlib  3.11.6-3
ii  media-types   10.1.0
ii  mime-support  3.66
ii  python3.11-minimal3.11.6-3

Versions of packages python3.11 recommends:
ii  ca-bundle [ca-certificates]  20190604tarent1

Versions of packages python3.11 suggests:
ii  binutils 2.41-6
pn  python3.11-doc   
pn  python3.11-venv  

-- no debconf information

Bug#1055365: libsm: Separate out documentation build

[Samuel Thibault]

Source: libsm
Version: 1.2.3-1
Severity: normal
Tags: patch

Hello,

libsm currently build-depends on w3m, which makes it part of a long
build dependency through imlib and whatnot image libraries. The w3m
dependency is actually only for building documentation, which is already
separated into an arch:all binary package. The attached patch completes
the separation by separating out the build dependencies. This makes
bootstraping a new Debian port much easier.

Samuel

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

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

-- 
Samuel
---
Pour une évaluation indépendante, transparente et rigoureuse !
Je soutiens la Commission d'Évaluation de l'Inria.
--- debian/control.original 2023-11-05 00:56:09.0 +
+++ debian/control  2023-11-05 01:02:42.0 +
@@ -11,7 +11,7 @@
  uuid-dev,
  xutils-dev (>= 1:7.6+2),
  quilt,
-# doc:
+Build-Depends-Indep:
  xmlto (>= 0.0.22), xorg-sgml-doctools (>= 1:1.8), w3m,
 Standards-Version: 4.3.0
 Homepage: https://www.x.org
--- debian/rules.original   2023-11-05 00:59:57.0 +
+++ debian/rules2023-11-05 01:00:09.0 +
@@ -13,12 +13,12 @@
 %:
dh $@ --with quilt --builddirectory=build/
 
-override_dh_auto_configure-arch: docflags = --disable-docs
-override_dh_auto_configure-indep: docflags = --enable-docs
+override_dh_auto_configure-arch: docflags = --disable-docs
+override_dh_auto_configure-indep: docflags = --enable-docs --with-xmlto
 override_dh_auto_configure-arch override_dh_auto_configure-indep:
dh_auto_configure -- \
--with-libuuid \
-   --with-xmlto --without-fop \
+   --without-fop \
--docdir=\$${datadir}/doc/libsm-dev \
$(docflags)
 

Bug#1055351: RM: pointback -- RoQA; obsolete

[Xiyue Deng]

Tobias Frost  writes:

> Package: ftp.debian.org
> Severity: normal
> User: ftp.debian@packages.debian.org
> Usertags: remove
> X-Debbugs-Cc: pointb...@packages.debian.org, Xiyue Deng 
> Control: affects -1 + src:pointback
>
> During sponsoring of pointback I found this message upstream:
>
>> As of Emacs 26.1, switch-to-buffer-preserve-window-point defaults to t, 
>> which solves the problem that pointback.el addresses.
>
> Xiyue confirmed that this is the case, so I guess pointback should be retired.

Thanks Tobias!  Also adding Sean who is the uploader to CC as a FYI.

-- 
Xiyue Deng

Bug#1055364: rust-rayon: please update to v1.8.0

[Jonas Smedegaard]

Source: rust-rayon
Version: 1.7.0-1
Severity: normal
Tags: upstream

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Please update to (at least) newer upstream release v1.8.0.
-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmVG370ACgkQLHwxRsGg
ASH4RQ/+NM6A013Q1o+jxZj55Vj15K4rw1gTbrmFzWaQUMXCNfYkjwxw9kkDdJf0
ccxvZJMaQtQrqk0AiaNi4g92uuPUZv99Qm1woKblMrYZ9lrnLfkUqMDUkLhdAHoR
KzwGZxkmldLD6v5cT2L3wUh1ZHUeoOOIZ6KQO8dPnw/GaDkN8OZeJKO+3AgTEZb+
XOqDlJnVNpP6RwB04ljXrhe1bTskA80ppxu+IiRNHwi94rZ5mtXWxoyXbdPtXUvu
uurniB+Q1YWdVazFc9JZEF7JUyHogymfgUxf+MNb24dKPjXGxOLpvZkGgk3pypm8
NYDVs2hF9uG+cJG2bO0fFJ5tGW/5X9RlBaqt5IK53wJvMgaqbBHyIO0kKyHz9Ul2
9f4pFVG2YYoKwXSmXEjZh0kx2qda3gZK3wOeesHAaUjpMVu9h9MNT+xelJF2YH9r
Cjt4pXfe0VGJXMEPXvTSeZewAKoMUdwUOT4Mo63NDzmKdrbLNkUgr10N3zR3JCu4
g/TZwWyJ5Q9RihpwKno7Q/xUQtUSi9XDyD57XHvsUYEQts5BQHZuYu/+hLV7uW4q
tS67AeIfheOx7z4oEihERe7KRVYJKLm0Zhjp3kXIEW94ii1lrQM7fLS4lXAuyJDN
qTZ8msnmuym4WM+coWmYOqe5fiMKqEcDw7uqt4im3U/pt5tMxVs=
=cUxC
-END PGP SIGNATURE-

Bug#1053799: golang-github-libgit2-git2go: no upstream support for latest libgit2

[Shengjing Zhu]

On Sun, Nov 5, 2023 at 4:45 AM Timo Röhling  wrote:
>
> Hi Mohammed, Pirate,
>
> On Wed, 11 Oct 2023 15:39:42 +0200 =?utf-8?q?Timo_R=C3=B6hling?=
>  wrote:
> > Source: golang-github-libgit2-git2go
> > Version: 34.0.0-4
> > Severity: important
> > Tags: upstream
> >
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA512
> >
> > Dear maintainer,
> >
> > the Go bindings for libgit2 are out of date with respect to libgit2,
> > which blocks the planned transition of libgit2 1.7.
> >
> > I think the Go bindings either need to be updated to work with libgit
> > 1.7 or removed from Debian for lack of upstream support.
> >
> Can you comment on this?
>

git2go is packaged for building gitaly. gitaly upstream has dropped
the git2go dependency.
Ref: https://gitlab.com/groups/gitlab-org/-/epics/9092

So IMO you can start libgit2 transition, and bump this bug's severity.

-- 
Shengjing Zhu

Bug#1034239: emacs-libvterm: vterm-mode make-process fails in an unshare(1)?

[Martin]

Control: reopen 1034239
Control: close 1044861 0.0.2+git20230417.94e2b0b-1

Sorry, accidently closed the wrong bug!

Bug#1055363: pmix: Fix hurd-amd64 build

[Samuel Thibault]

Source: pmix
Version: 3.2.2~rc1-1.1
Severity: important
Tags: patch

Hello,

hurd-amd64 has the same constraint as hurd-i386, could you please apply
the attached patch?

Thanks,
Samuel

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

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

-- 
Samuel
---
Pour une évaluation indépendante, transparente et rigoureuse !
Je soutiens la Commission d'Évaluation de l'Inria.
--- debian/control.original 2023-11-04 22:38:42.0 +
+++ debian/control  2023-11-04 22:38:45.0 +
@@ -9,7 +9,7 @@
  zlib1g-dev,
  libevent-dev,
  libltdl-dev,
- libmunge-dev [ !hurd-i386]
+ libmunge-dev [!hurd-any]
 Standards-Version: 4.5.1
 Homepage: https://github.com/pmix/pmix
 Vcs-Browser: https://salsa.debian.org:/science-team/pmix.git

Bug#1055192: RFS: golang-github-apenella-go-ansible

[weepingclown]

Dear Go team,

I am looking for a sponsor for the package "golang-github-apenella-go-ansible".

I pushed to our team's Salsa:

  https://salsa.debian.org/go-team/packages/golang-github-apenella-go-ansible

It currently has dependencies that are not uploaded yet, please see #1055195 
and #1055196.
I have previously sent RFS for both of them.

Could you please review/sponsor these packages?
Any kind of reviews and suggestions are appreciated.

Thanks

Bug#1055198: ITP: lzfse -- LZFSE Compression library

[Timo Röhling]

* Andreas Henriksson  [2023-11-04 23:03]:
I hope I understood you correctly and this now adresses your 
concerns:

https://salsa.debian.org/bananas-team/asahi-fwextract/-/commit/bfbd6f53c2e8721b9457c3a37421280a8a86dbc8

Yes, that looks good! I also like the fallback.

Cheers
Timo


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


signature.asc
Description: PGP signature

Bug#1055198: ITP: lzfse -- LZFSE Compression library

[Andreas Henriksson]

Hello,

On Sat, Nov 04, 2023 at 08:47:11PM +0100, Timo Röhling wrote:
> Hi,
> 
> * Andreas Henriksson  [2023-11-04 18:05]:
> > I've previously suggested that maybe it would be better to set a
> > debian-specific version (0d?), to avoid the theoretical situation that
> > upstream one day ships a different ABI under the 1 so version.
> Normally, I would agree, but in this particular case, Fedora already went
> ahead and used SOVERSION 1 [1], so that version is "burned" and we might
> just as well use it, too.
> 
> [1] https://src.fedoraproject.org/rpms/lzfse/blob/rawhide/f/60.patch

Thanks for pointing this out!

> 
> > I would welcome peoples input here on what you think is best from the
> > debian perspective. Obviously we're going to be incompatible with
> > everyone else.
> I don't think that "incompatible" patch you linked creates much of an issue,
> because very few (if any) other library consumers will do this rather
> unusual dlopen() "soft linking" dance (normal linking with e.g. "gcc
> -llzfse" will automatically use the proper SONAME); besides, it is easy to
> patch in Debian packages and trivial to work around with "apt install
> liblzfse-dev" for everyone else.
> 
> I do have one remark, though: the idea behind SONAME/SOVERSION is that you
> have a common name for all versions which are binary backwards compatible.
> Using the full version liblzfse.so.1.0 instead of libltfse.so.1 (i.e., the
> SONAME) in your patch defeats that purpose: it will only work with the exact
> version 1.0, but not any (hypothetical) future, backwards-compatible
> versions.

I hope I understood you correctly and this now adresses your concerns:
https://salsa.debian.org/bananas-team/asahi-fwextract/-/commit/bfbd6f53c2e8721b9457c3a37421280a8a86dbc8

Regards,
Andreas Henriksson

Bug#1055362: Crash when plugging in USB graphics tablet

[ethan-git]

Package: wayfire
Version: 0.7.4-3

When I plug in a USB graphics tablet, there is a segmentation fault
approximately half the time. In my experience, the bug might trigger
more reliably with an XWayland client open, or with many clients open.
I haven't seen this crash on startup, it only seems to happen when
plugging in the graphics tablet while running. This is the same crash
described in upstream bug #1415 [1], and fixed in upstream PR #1555 [2],
which is a one-line fix to add a null check.

I am using Debian bookworm, up to date as of 2023-11-03, using kernel
6.1.0-13-amd64. I've posted a log [3], and there's another log linked
in the upstream bug report. I'm happy to test any patched version of
the package or provide any more details.

Thank you for the work you do to maintain this package and all of the
others that you maintain as well.

[1] https://github.com/WayfireWM/wayfire/issues/1415
[2] https://github.com/WayfireWM/wayfire/pull/1555
[3] https://ethanwhite.net/static/wayfire.log

Bug#1055361: devscripts: dch should have a --oldstable flag, to match the --stable flag

[Salvo "LtWorf" Tomaselli]

Package: devscripts
Version: 2.23.6
Severity: wishlist
X-Debbugs-Cc: ltw...@debian.org

Dear Maintainer,

Since there is a --stable flag, a --oldstable flag would be useful.

dch is written in perl and I don't know any perl, so I doubt I can be of
assistance here.

-- Package-specific info:

--- /etc/devscripts.conf ---
Empty.

--- ~/.devscripts ---
Not present

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

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

Versions of packages devscripts depends on:
ii  dpkg-dev  1.22.1
ii  fakeroot  1.32.1-1
ii  file  1:5.45-2
ii  gnupg 2.2.40-1.1
ii  gpgv  2.2.40-1.1
ii  libfile-dirlist-perl  0.05-3
ii  libfile-homedir-perl  1.006-2
ii  libfile-touch-perl0.12-2
ii  libfile-which-perl1.27-2
ii  libipc-run-perl   20231003.0-1
ii  libmoo-perl   2.005005-1
ii  libwww-perl   6.72-1
ii  patchutils0.4.2-1
ii  perl  5.36.0-9
ii  python3   3.11.4-5+b1
ii  sensible-utils0.0.20
ii  wdiff 1.2.2-6

Versions of packages devscripts recommends:
ii  apt 2.7.6
ii  curl8.4.0-2
ii  dctrl-tools 2.24-3+b1
ii  debian-keyring  2023.09.24
ii  dput1.1.3
ii  equivs  2.3.1
ii  libdistro-info-perl 1.7
ii  libdpkg-perl1.22.1
ii  libencode-locale-perl   1.05-3
ii  libgit-wrapper-perl 0.048-2
ii  libgitlab-api-v4-perl   0.27-1
pn  libjson-perl
ii  liblist-compare-perl0.55-2
ii  liblwp-protocol-https-perl  6.11-1
ii  libsoap-lite-perl   1.27-3
ii  libstring-shellquote-perl   1.04-3
ii  libtry-tiny-perl0.31-2
ii  liburi-perl 5.21-1
ii  licensecheck3.3.9-1
ii  lintian 2.116.3
ii  man-db  2.12.0-1
ii  patch   2.7.6-7
ii  pristine-tar1.50
ii  python3-apt 2.6.0
ii  python3-debian  0.1.49
ii  python3-magic   2:0.4.27-2
ii  python3-requests2.31.0+dfsg-1
ii  python3-unidiff 0.7.3-1
ii  python3-xdg 0.28-2
ii  strace  6.4-0.1
ii  unzip   6.0-28
ii  wget1.21.4-1+b1
ii  xz-utils5.4.4-0.1

Versions of packages devscripts suggests:
pn  adequate 
pn  at   
pn  autopkgtest  
pn  bls-standalone   
pn  bsd-mailx | mailx
ii  build-essential  12.10
pn  check-all-the-things 
pn  cvs-buildpackage 
ii  debhelper13.11.7
pn  diffoscope   
pn  disorderfs   
pn  dose-extra   
pn  duck 
pn  elpa-devscripts  
pn  faketime 
ii  gnuplot  5.4.4+dfsg1-2
ii  gnuplot-qt [gnuplot] 5.4.4+dfsg1-2+b2
pn  how-can-i-help   
ii  libauthen-sasl-perl  2.1700-1
pn  libdbd-pg-perl   
ii  libfile-desktopentry-perl0.22-3
pn  libterm-size-perl
ii  libtimedate-perl 2.3300-2
pn  libyaml-syck-perl
pn  mmdebstrap   
pn  mozilla-devscripts   
pn  mutt 
ii  openssh-client [ssh-client]  1:9.4p1-1
pn  piuparts 
pn  postgresql-client
pn  pristine-lfs 
pn  quilt
pn  ratt 
pn  reprotest
pn  svn-buildpackage 
pn  w3m  

-- no debconf information

Bug#1052852: python-django-crispy-forms: FTBFS: make[1]: *** [debian/rules:17: override_dh_auto_test] Error 1

[s3v]

Dear Maintainer

After applying this commit [1], I was able to build successfully your
package in a sid chroot environment.
I've also tried to build against sphinx 7.2.6-1 + python-docutils
0.20.1+dfsg-1 in experimental and no problems were spotted.

Kind Regards

[1] https://github.com/django-crispy-forms/django-crispy-forms/pull/1257

Bug#1051901: 1.2.10 breaks ability to play audio using i386 binaries on amd64 host

[Dirk Griesbach]

Am Mo, 23. Okt 2023 um 18:31:26 -0400 schrieb Stefan Monnier:

I'd go so far to think that this is not constrained to i386 binaries on
amd64 hosts. `aplay /dev/zero` segfaults on a plain i386 host with asound
1.2.10. Downgrading to 1.2.9 helps.


Is this the same as https://github.com/alsa-project/alsa-lib/issues/352 ?


Seems to be the case. Sound is working again with the patches applied.

Thanks,
Dirk

Bug#1055198: ITP: lzfse -- LZFSE Compression library

[Peter Pentchev]

On Sat, Nov 04, 2023 at 06:05:41PM +0100, Andreas Henriksson wrote:
> On Thu, Nov 02, 2023 at 01:04:03AM +0100, Tobias Heider wrote:
> > Package: wnpp
> > Severity: wishlist
> > Owner: Tobias Heider 
> > X-Debbugs-Cc: debian-de...@lists.debian.org
> > 
> > * Package name: lzfse
> >   Version : 1.0
> >   Upstream Authors:
> >   URL : https://github.com/lzfse/lzfse
> > * License : BSD-3-Clause
> >   Description : LZFSE Compression library
> > 
> > LZFSE is a Lempel-Ziv style data compression algorithm using Finite
> > State Entropy coding. It targets similar compression rates at higher
> > compression and decompression speed compared to deflate using zlib.
> > 
> > I plan to maintain this as part of the bananas team.
> 
> Calling all SO versioning experts!
> 
> The upstream project does not have any shared object version set.
> A downstream patch was introduced to set one:
> https://salsa.debian.org/bananas-team/lzfse/-/blob/debian/unstable/debian/patches/0001-debian-set-library-SONAME.patch
> 
> Upstream has seen no activity since 2017, so trying to interact is
> assumed to not generate much.

(sorry, I imagine you are already aware of what I am about to say, but
 still I think it's worth saying... Apologies if I'm lecturing,
 I think you may have been a DD longer than I have :))
This... may be a problem. This means that any fixes you have to make
(security fixes, important bug fixes, or just improvements that really,
really bug your sense of doing things right) will be specific to
the Debian package, and unless the other packaging systems pick them up,
with time things will diverge further and further.

The best thing to do in this case is to - somehow - try to push things in
a direction that ultimately leads to the library having active upstream
developers. This may mean having you or somebody you know try to contact
the current developers and ask to join them. In a close-to-the-extreme
version of this, this may mean you (or somebody you know) taking over
upstream development with the consent of the current developers.
In a really, really extreme version, it may mean forking the project
without the consent of the current developers and facing various kinds of
weird things down the road, especially if they wake up one day and decide
to carry on as usual, ignoring your fork. One thing to note that
I have learned from bitter experience: you may feel that it would be
fun and it would not be too difficult to take over upstream development,
and doing this too many times may lead to a situation that you are
the upstream developer for too many things and you cannot really give
most of them enough attention. 

There is no single right answer here, but it would certainly be much,
much, much better for everyone involved (including the end users of
your Debian package, people who install something that uses this library)
if there were an active upstream.

> Also the ABI is unlikely to change (since
> no changes are being made).

Yeah... see above about the upstream developers waking up one day and
deciding to carry on :) Also, it is possible that some packager from
antoher packaging system decides to go ahead and fork the project...
But still, those are all hypotheticals.

> I've previously suggested that maybe it would be better to set a
> debian-specific version (0d?), to avoid the theoretical situation
> that upstream one day ships a different ABI under the 1 so version.
> 
> I would welcome peoples input here on what you think is best from
> the debian perspective. Obviously we're going to be incompatible with
> everyone else[1], unless you install/runtime-depend-on the -dev package
> for the unversioned so symlink. Please speak now before this is
> submitted for NEW.

When you say "incompatible with everyone else", how do other packaging
systems handle this? Has this library been packaged somewhere else?
It might be a good idea to do the same thing as some other packaging
system... but it may also turn out that all of the current ones have
chosen (possibly different) suboptimal ways to handle this, so
being incompatible with them may turn out to be the best option for
Debian itself. As above, there is no single right answer here.

> FWIW lzfse is needed to extract files compressed by Apple and shipped in macOS
> containing embedded firmwares. See asahi-fwextract ITP: #1055206
> 
> Regards,
> Andreas Henriksson
> 
> 
> [1]: 
> https://salsa.debian.org/bananas-team/asahi-fwextract/-/blob/debian/unstable/debian/patches/0001-Use-versioned-library-name-for-liblzfse.patch

G'luck,
Peter

-- 
Peter Pentchev  r...@ringlet.net r...@debian.org p...@storpool.com
PGP key:http://people.FreeBSD.org/~roam/roam.key.asc
Key fingerprint 2EE7 A7A5 17FC 124C F115  C354 651E EFB0 2527 DF13


signature.asc
Description: PGP signature

Bug#1053799: golang-github-libgit2-git2go: no upstream support for latest libgit2

[Timo Röhling]

Hi Mohammed, Pirate,

On Wed, 11 Oct 2023 15:39:42 +0200 =?utf-8?q?Timo_R=C3=B6hling?= 
 wrote:

Source: golang-github-libgit2-git2go
Version: 34.0.0-4
Severity: important
Tags: upstream

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Dear maintainer,

the Go bindings for libgit2 are out of date with respect to libgit2, 
which blocks the planned transition of libgit2 1.7.


I think the Go bindings either need to be updated to work with libgit 
1.7 or removed from Debian for lack of upstream support.



Can you comment on this?

Cheers
Timo


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


signature.asc
Description: PGP signature

Bug#1051877: rust-libgit2-sys: please prepare for libgit2 transition

[Timo Röhling]

On Wed, 13 Sep 2023 22:30:42 +0200 =?utf-8?q?Timo_R=C3=B6hling?= 
 wrote:

Source: rust-libgit2-sys
Version: 0.14.1-1
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Dear maintainer,

I have uploaded libgit2 1.7.1 to experimental and want to start the
transition for unstable soon. Like many other language bindings for
libgit2, the rust-libgit2-sys package needs to be upgraded in lock-step.

I suggest you upload version 0.16.1+1.7.1 to experimental first, so we can
check for potential regressions, but we can skip that step if you think
it is not necessary. I will start the transition once all language
bindings are ready.


Ping!
Just wondering if you saw this bug / still maintain the package :)


Cheers
Timo

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


signature.asc
Description: PGP signature

Bug#1055347: RFA: kitty -- fast, featureful, GPU based terminal emulator

[Nilesh Patra]

On Sat, Nov 04, 2023 at 02:25:47PM -0400, James McCoy wrote:
> We can try that for the now, but it would probably be good for someone
> else to eventually take over primary maintenance of the package.
> 
> https://salsa.debian.org/debian/kitty/-/merge_requests/3 is what I have
> so far for the new upstream version.  Feel free to hack around with
> that.

Cool. I have one question though: how do you sync the repo to new
upstream? It does not seem to use gbp layout so wanted to know how
exactly you're tracking/pulling the commits?

OTOH, I did take a look at the errors and I see two ways. Either patch
out all the go build related code and use debian's go build toolchain
(which takes care of a bunch of things) or hack around the way upstream
builds to somehow fit out usecase (this is consuming quite some cycles).
Definitely complicated since a bunch of different functionalities have
been mixed with different languages.

Best,
Nilesh


signature.asc
Description: PGP signature

Bug#657711: please make COPYFILES more flexible

[Santiago Vila]

Version: 1.6.13-3

El 2/8/22 a las 15:28, Guillem Jover escribió:

On Sat, 2012-01-28 at 09:26:03 +0100, Marc Haber wrote:

To allow this, the COPYFILES functionality could be changed to allow
two file names per line. If only one is given, behavior is not
changed, preserving backwards-compatibility. If two are given, one is
the source path from the host system, one is the target path inside
the chroot.


I implemented this for myself some time ago, and submitted it to the
previous upstream repo, where it got merged. I resubmitted this again
to the new fork, as it branched from a different point in history.


Hello. The feature is present indeed in the schroot version in
bookworm, in exactly the way Marc suggested. Now the sample
"copyfiles" files have a line like this one:

# [ ]

(So, I'm closing using such version)

Thanks.

Bug#1053800: transition: libgit2

[Timo Röhling]

Hi Sebastian,

* Sebastian Ramacher  [2023-11-01 12:14]:
There are no replies on the bug report. Are there any news 
regarding the rust bindings?
No, nothing yet. All uploads in the past two years came from Peter 
Michael Green, so I am going to ping him directly.



golang-github-libgit2-git2go upstream has fallen behind and

Same as above. Are there any news here?
No. I was prepared to ignore the Go bindings completely after they 
got removed from trixie, but Mohammed Bilal did an upload to fix the 
RC bug, presumably because they are a build dependency of gitlab.

I'll ping him, too.


Cheers
Timo

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


signature.asc
Description: PGP signature

Bug#1055360: RFA: python-onewire -- Wrapper for OWFS C-API

[Bastian Germann]

Package: wnpp

I am no longer interested in maintaining this package.
Please consider adopting it if you want to care for it.
It does not take a lot of time because upstream does not move very fast.

Bug#1055359: RFA: python-junit-xml -- creates JUnit XML test result docs

[Bastian Germann]

Package: wnpp

I am no longer interested in maintaining this package.
Please consider adopting it if you want to care for it.
It does not take a lot of time because upstream does not move very fast.

Bug#1055358: RFA: spyne -- Python library for writing and calling web services

[Bastian Germann]

Package: wnpp

I am no longer interested in maintaining this package.
Please consider adopting it if you want to care for it.
It does not take a lot of time because upstream is not moving very fast.

Bug#1055357: RFA: xmodem -- xmodem file transfer protocol python library

[Bastian Germann]

Package: wnpp

I am no longer interested in maintaining this package.
Please consider adopting it if you want to care for it.
It does not take a lot of time because upstream is not moving very fast.

Bug#1055356: O: db5.3 -- Berkeley v5.3 Database

[Bastian Germann]

Package: wnpp

I am no longer interested in maintaining this package.
db5.3 is a package that should be removed in the long run.
Please do not update it to newer versions which have a different license
that is not suitable for this kind of software (at least in Debian).

So maintaining the package should not take a lot of time.
It is a pseudo-essential package and as such has a very high popcon.
I have filed #1032207 to eliminate it from that set, which you might want to 
follow-up.

Bug#1055198: ITP: lzfse -- LZFSE Compression library

[Timo Röhling]

Hi,

* Andreas Henriksson  [2023-11-04 18:05]:
I've previously suggested that maybe it would be better to set a 
debian-specific version (0d?), to avoid the theoretical situation 
that upstream one day ships a different ABI under the 1 so version.
Normally, I would agree, but in this particular case, Fedora already 
went ahead and used SOVERSION 1 [1], so that version is "burned" and 
we might just as well use it, too.


[1] https://src.fedoraproject.org/rpms/lzfse/blob/rawhide/f/60.patch

I would welcome peoples input here on what you think is best from 
the debian perspective. Obviously we're going to be incompatible 
with everyone else.
I don't think that "incompatible" patch you linked creates much of 
an issue, because very few (if any) other library consumers will do 
this rather unusual dlopen() "soft linking" dance (normal linking 
with e.g. "gcc -llzfse" will automatically use the proper SONAME); 
besides, it is easy to patch in Debian packages and trivial to work 
around with "apt install liblzfse-dev" for everyone else.


I do have one remark, though: the idea behind SONAME/SOVERSION is 
that you have a common name for all versions which are binary 
backwards compatible. Using the full version liblzfse.so.1.0 instead 
of libltfse.so.1 (i.e., the SONAME) in your patch defeats that 
purpose: it will only work with the exact version 1.0, but not any 
(hypothetical) future, backwards-compatible versions.



Cheers
Timo

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


signature.asc
Description: PGP signature

Bug#1040416: linux-image-6.1.0-9-amd64: Under heavy load Debian V12 and V11 causes data corruption on XFS filesystems.

[Jose M Calhariz]

Hi

On Thu, Nov 02, 2023 at 07:40:38PM +0100, Diederik de Haas wrote:
> 
> On Thursday, 2 November 2023 18:03:25 CET Jose M Calhariz wrote:
> > On Thu, Nov 02, 2023 at 03:37:39PM +0100, Diederik de Haas wrote:
> > > On Wednesday, 5 July 2023 19:07:15 CET Jose M Calhariz wrote:
> > > > Package: src:linux
> > > > Version: 6.1.27-1
> > > 
> > > Can you try with the latest version in the 6.1.x series to see if the
> > > problem is still there?
> > 
> > As I need to setup ASAP the servers in production I do not know if I
> > have time in the next days.  It works with backports kernels.
> 
> No problem.
> 
> > The latest kernels I tested were:
> > Fail : Linux afs31 6.1.0-10-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.37-1
> > (2023-07-03) x86_64 GNU/Linux
> 
> Ok. Please test (when you have time) 6.1.55-1.

Fail : Linux afs31 6.1.0-0-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1~rc3-1~exp1 
(2022-11-02) x86_64 GNU/Linux

Fail : Linux afs31 6.1.0-13-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.55-1 
(2023-09-29) x86_64 GNU/Linux

Done.  I tested even the first 6.1 on Debian.  Both of them failed.




> Also verify if it's also present in 6.1~rc3-1~exp1 to make sure it's present 
> in the whole 6.1 series.
> Use https://snapshot.debian.org/binary/linux-image-amd64/ to get it/them.
> 
> If the bug is NOT present in either the latest or the first, then try other 
> versions till you find the last one that work and the first one that fails.
> 
> > OK : Linux afs31 6.4.0-0.deb12.2-amd64 #1 SMP PREEMPT_DYNAMIC Debian
> > 6.4.4-3~bpo12+1 (2023-08-08) x86_64 GNU/Linux
> 
> It was fixed in 6.3.7-1, so it was expected that a later versions also works.
> But let's ignore bpo as it likely won't provide useful data points.
> 
> Unfortunately there isn't a 6.2 kernel uploaded to the Debian archive and 
> thus 
> not available on snapshot.d.o, but testing 6.3.1-1~exp1 should be useful.
> 
> > The bug is present on Debian v11 too.  So is an old bug with fixes on
> > kernel 6.2 rc something.
> 
> I'd recommend to focus first on the 6.1 series for now.
> If at a later point testing with 5.10 may be useful, we can do that then.


Kind regards
Jose M Calhariz


-- 
--
A vida feliz, meu Deus, consiste em nos alegrarmos em vos,
de vos e por vos


signature.asc
Description: PGP signature

Bug#1055355: RFA: cbor2 -- Concise Binary Object Representation for Python

[Bastian Germann]

Package: wnpp

I do not use cbor2 anymore.
Please consider adopting it if you have the time and skills to maintain it.
It is a low-maintenance package with seldomly release upstream versions.

Bug#1055348: jetty9: Update from DLA 3641 breaks puppetdb ("Exception in thread "main" java.lang.IllegalStateException: KeyStores with multiple certificates are not supported on the base class org.ecl

[Markus Koschany]

Hello,

Am Samstag, dem 04.11.2023 um 17:03 + schrieb Adam D. Barratt:
> Source: jetty9
> Version: 9.4.50-4+deb10u1
> Severity: serious
> X-Debbugs-Cc: d...@debian.org
> 
> Hi,
> 
> Upgrading libjetty9-java and libjetty9-extra-java to the version from
> DLA 3641-1 reliably causes PuppetDB to fail to start, with the
> stacktrace shown below. Downgrading resolves the issue.
> 
> I'm not sure which keystore is being referred to, but none of the files
> listed in /etc/puppetdb/conf.d/jetty.ini appear to contain more than a
> single certificate.

thanks for the report. This looks like a bug in trapperkeeper-webserver-jetty9-
clojure to me. Upstream commit

https://github.com/puppetlabs/trapperkeeper-webserver-jetty9/commit/3ee6a410436c1a236ca33d511c5373c3328054ef

appears to address the problem. The version in Buster lacks the
InternalSslContextFactory class though. Instead the deprecated
SslContextFactory class is referenced in jetty9_config.clj and
jetty9_core.clj. 

My first idea is to change SslContextFactory occurrences to
SslContextFactory.Server.

Backporting the version of trapperkeeper-webserver-jetty9-clojure from Bullseye
to Buster is the second one. AFAICS puppetdb and puppetserver are the only
consumers.

Could you install the version of trapperkeeper-webserver-jetty9-clojure from
Bullseye and reinstall the jetty9 security update and report back if this
solves your problem?

Regards,

Markus


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

Bug#1002056: rust-gix-features seem to depend on zlib-ng

[Alexander Kjäll]

Hi

Some rust code I'm trying to package seem to depend on zlib-ng, this
can maybe be patched out, but I thought I should ask about status on
this packaging effort before I undertake that work.

best regards
Alexander Kjäll

Bug#1055354: O: mujs -- Lightweight JavaScript interpreter

[Bastian Germann]

Package: wnpp

I am no longer interested in maintaining this package.
mujs is a dependency of mupdf and is a low-maintenance package.
It is in good shape: Current upstream version is in Debian and no open issues.

Bug#1055293: dub: Please upgrade to a new version

[Matthias Klumpp]

Hi Nilesh!

Am Fr., 3. Nov. 2023 um 17:54 Uhr schrieb Nilesh Patra :
> [...]
> dub seems to be at a really old version and it is just "limping" to stay
> in testing at the moment and the version there was released 3 years
> back, this is behind a bunch of new releases.
>
> I noticed there is a new version committed to salsa but it does not
> build and this seems unfixed upstream as well. I however did find a
> (unmerged) PR that fixes it:
>
> https://github.com/dlang/dub/pull/2623
>
> IMHO dub should be updated to latest version once those rough edges are
> sorted out.

It does not, unfortunately. I just tried building the package using
the latest Dub version, and the actual blocking issue, which is
https://github.com/dlang/dub/issues/2577, still exists.
We need to resolve that or find a workaround in order to update dub.

Cheers,
Matthias

-- 
I welcome VSRE emails. See http://vsre.info/

Bug#1042859: [Pkg-rust-maintainers] Bug#1042859: Bug#1042859: cargo: Please upgrade to at least 0.67.0

[Fabian Grünbichler]

On Fri, Nov 03, 2023 at 03:24:07PM +0100, Eduard Bloch wrote:
> Hallo,
> * Fabian Grünbichler [Fri, Nov 03 2023, 01:57:08PM]:
> > > Eduard Bloch  hat am 03.11.2023 13:46 CET geschrieben:
> > >
> > >
> > > Hallo,
> > > * Fabian Grünbichler [Fri, Nov 03 2023, 12:32:50PM]:
> > >
> > > > > the version of Cargo seriously needs an update. Because the word is
> > > > > moving and the old version performs increasingly bad.
> > > >
> > > > the upgrade (to 0.70.1, since later versions require a lot of NEW 
> > > > processing first) is being prepared, but it takes a long time because 
> > > > it is very involved.
> > > >
> > > > https://salsa.debian.org/rust-team/debcargo-conf/-/issues/48
> > > > https://salsa.debian.org/rust-team/cargo/-/merge_requests/21
> > > >
> > > > also related, and hopefully improving this in the future:
> > > >
> > > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054658
> > > > https://salsa.debian.org/rust-team/rust/-/merge_requests/27
> > >
> > > Okay, I get the idea. That said, I find it quite strange that you want
> > > to include a Python dependency in order to run a central Rust tool.
> > >
> > > Would you like me to rewrite the proposed cargo wrapper script into a
> > > native Rust app? That's a serious offer, I have IMHO sufficient Python
> > > and Rust experience, recently working on something partly similar
> > > (https://gitlab.com/setecastronomy/wec ).
> >
> >
> > I am not sure what you are referring to, but the fact that some 
> > helper/wrapper scripts are written in python is in no way related to what 
> > is making updates cumbersome at the moment.
> 
> I was refering to the last link from the post above:
> 
> https://salsa.debian.org/rust-team/rust/-/merge_requests/27/diffs#98066737513db2808acb090ffe631b89bd788499

that is not related at all either to updating cargo, or merging the two
source packages..

> > and we most definitely don't want to rewrite the cargo wrapper in rust, 
> > that would serve no purpose at all.
> 
> Depends on the whole picture. From that statement I understand that
> reducing dependencies on further interpreters (like Python) is not a
> goal here.

it is indeed not, see below.

> > > (Not sure about bootstrapping, though. Is rustc available while our
> > > source package is being built?)
> >
> > of course rustc is required to build both rustc and cargo, since both are 
> > written in rust. note that rustc itself also has a build-dependency on 
> > python anyway, since it's (internal) bootstrapping/build tool is written in 
> > python (and rust).
> 
> Okay. But I did not have only build-deps of the Debian source package
> in mind, more the dependencies of the binary package, i.e. what the
> regular user (application developer) gets. Why should cargo have a
> dependency on Python? Looks quite strange to me.

it should not - but it also does not.

cargo (the package in Debian) only suggest python3. you can use
(/usr/bin/)cargo (the binary as packaged in Debian) without having
python installed. only when you use cargo via the wrapper script
/usr/share/cargo/bin/cargo, which exists for integrating cargo into
Debian packaging, would you need to have python3 installed. that script
is not in anyone's $PATH (by default), and is only supposed to be called
directly or indirectly via d/rules (manually after doing the appropriate
setup steps, or via dh-cargo) when building a package. dh-cargo as a
result depends on python3, but that is not relevant for someone just
installing cargo to run cargo-the-binary for application development.


signature.asc
Description: PGP signature

Bug#1054706: e-antic: FTBFS: ../../../libeantic/test/main.cpp:4:10: fatal error: catch2/catch.hpp: No such file or directory

[Jerome BENOIT]

Hello,
as the migration to catch2 v3 appeared not simple,
I finally used the catch2 material provided by the e-antic upstream team.
Best wishes, Jerome
--
Jerome BENOIT | calculus+at-rezozer^dot*net
https://qa.debian.org/developer.php?login=calcu...@rezozer.net
AE28 AE15 710D FF1D 87E5  A762 3F92 19A6 7F36 C68B


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1035734: Acknowledgement (Does not search for terms in latin1 encoding anymore)

[Klaus Ethgen]

Hi Axel,

here is a fix of this bug.

--- /usr/bin/translate.orig 2023-11-04 19:25:55.944359987 +0100
+++ /usr/bin/translate  2023-11-04 19:30:27.089291611 +0100
@@ -94,14 +94,16 @@
 
 display ()
 {
+  local lsearch="$SEARCH"
+  [ $UTF8 -eq 1 ] || lsearch="$(echo "$SEARCH" | iconv -c -f UTF-8 -t 
$CHARSET)"
   if [ $COLOR = true ]
   then
 display_no_color "$@" | if
   [ $WHOLEWORD = false ]
 then
-  grep -Eihs --color=auto "$SEARCH"
+  grep -Eihs --color=auto "$lsearch"
 else
-  grep -Eihs --color=auto '\b'"$SEARCH"'\b'
+  grep -Eihs --color=auto '\b'"$lsearch"'\b'
 fi
   else
 display_no_color "$@"

Gruß
   Klaus
-- 
Klaus Ethgen   http://www.ethgen.ch/
pub  4096R/4E20AF1C 2011-05-16Klaus Ethgen 
Fingerprint: 85D4 CA42 952C 949B 1753  62B3 79D0 B06F 4E20 AF1C


signature.asc
Description: PGP signature

Bug#1052347: src:canu: fails to migrate to testing for too long: unresolved RC issue

[Paul Gevers]

Hi,

On 04-11-2023 14:11, Nilesh Patra wrote:

The upstream needs the *.out files of the failing tests, as they said at [1]. 
Since it does not work on porter box, and chokes on the CI infra, could you 
please provide these files?


At least two .out files are found in the artifacts tar ball, also 
attached to the upstream bug report by Michael. If those are not what 
you need, please be explicit which one you need. Also, you're in control 
of what goes into the artifacts tar ball, so you could also do it 
yourself. (But please be aware of bug #1050388 and don't put everything 
in the tar ball again).


Paul


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1055353: Debian installer not setting locale in Trixie daily builds

[Brandon Werner]

package: locale-chooser

Hi,
After installing via the daily images, my locale isn't set. I took a brief 
look, and my best guess is the trouble is being caused in the file 
post-base-installer.d/05localechooser. There, I noticed
"DESTFILE="/target/etc/default/locale"".
I believe this file was retired recently in Debian.

If I manually set my locale in /etc/locale.conf, things work as expected.

Bug#1055269: udd: bugs.cgi does not show bugs for source packages in non-free-firmware

[Andreas Tille]

Just a quick note: I can't care for this in the next 48 hours.

Am Fri, Nov 03, 2023 at 10:48:11PM +0100 schrieb Cyril Brulebois:
> Lucas Nussbaum  (2023-11-03):
> > UDD uses several independant "importers". The constraint you quoted is
> > in the "blends" importer (maintained by Andreas Tille, cced).
> 
> ACK, I spotted a number of things that were blends-related, didn't
> realize that particular schema was too.
> 
> > The reason why UDD thinks that #1055136 does not affect unstable, is
> > because the BTS thinks it does not affect unstable. If you look at the
> > version graph for the bug, you see that the BTS only knows about the
> > version in oldstable, not about the versions in stable/testing/unstable.
> > The same happens for other packages in non-free-firmware (see #1038610
> > for example).
> 
> https://github.com/dondelelcaro/debbugs/issues/2 then.
> 
> 
> Cheers,
> -- 
> Cyril Brulebois (k...@debian.org)
> D-I release manager -- Release team member -- Freelance Consultant



-- 
http://fam-tille.de

Bug#1055343: Status of the packaging of anura in Debian

[Martin Quinson]

Hello,

I am "regularly" discussing with the authors of Anura (on their Discord
channel), and the program is not ready for packaging yet. They have to sort
something out so that we can use imgui from the Debian package instead of the
embedded version. 

https://discord.com/channels/225816341737766912/1103903330972995674/1132358680692658276

Once their unvendor-imgui branch is merged into their trunk, it's time for us
to package it.

Thanks, 
Mt


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

Bug#1055347: RFA: kitty -- fast, featureful, GPU based terminal emulator

[James McCoy]

On Sat, Nov 04, 2023 at 11:36:21PM +0530, Nilesh Patra wrote:
> Hi,
> 
> On Sat, Nov 04, 2023 at 12:23:34PM -0400, James McCoy wrote:
> > Package: wnpp
> > Severity: normal
> > X-Debbugs-Cc: ki...@packages.debian.org, debian-de...@lists.debian.org
> > Control: affects -1 + src:kitty
> > 
> > I request an adopter for the kitty package.  I no longer use the package
> > and don't have time to figure out how to deal with the new golang parts
> > of the package.
> 
> If you could commit to maintaining the overall package as such, I am offer
> my help with the golang parts.

We can try that for the now, but it would probably be good for someone
else to eventually take over primary maintenance of the package.

https://salsa.debian.org/debian/kitty/-/merge_requests/3 is what I have
so far for the new upstream version.  Feel free to hack around with
that.

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

Bug#1042698: python-vispy: FTBFS with Sphinx 7.1, docutils 0.20: AttributeError: 'container' object has no attribute 'html5tagname'

[Nilesh Patra]

Hi Lucas,

On Sun, 30 Jul 2023 20:33:09 +0200 Lucas Nussbaum  wrote:
> Source: python-vispy
> Version: 0.6.6-3
> Severity: important
> Tags: ftbfs

This seems to be an older version of vispy and the latest one in
bookworm no longer FTBFS with newer sphinx for me locally.

Could you please trigger a job on the latest vispy version as well so we
could close this?

Thanks!


signature.asc
Description: PGP signature

Bug#1037440: kitty: New upstream release

[James McCoy]

Control: block 1037440 by 1055347

On Mon, Jun 12, 2023 at 06:15:23PM -0400, James McCoy wrote:
> Filing this to track new packages/package updates which are blocking an
> update of kitty.

All the dependencies are now packaged (as of kitty 0.30.1), but I don't
have the time to figure out how to integrate the golang aspects into the
build.

The package is now up for adoption -- #1055347.

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

Bug#1055347: RFA: kitty -- fast, featureful, GPU based terminal emulator

[Nilesh Patra]

Hi,

On Sat, Nov 04, 2023 at 12:23:34PM -0400, James McCoy wrote:
> Package: wnpp
> Severity: normal
> X-Debbugs-Cc: ki...@packages.debian.org, debian-de...@lists.debian.org
> Control: affects -1 + src:kitty
> 
> I request an adopter for the kitty package.  I no longer use the package
> and don't have time to figure out how to deal with the new golang parts
> of the package.

If you could commit to maintaining the overall package as such, I am offer
my help with the golang parts.

Best,
Nilesh


signature.asc
Description: PGP signature

Bug#1053575: RFS: ruby-mdl/0.13.0-1 -- Markdown lint tool

[Tobias Frost]

Am Wed, Nov 01, 2023 at 11:55:29PM +0100 schrieb Norwid Behrnd:

Your transitional package needs to Depends: on the new package.

> The /debian/control file was edited to eventually yield an updated
> `markdownlint_0.13.0-1_all.deb` (for future use) and a transitional
> `ruby-mdl_0.13.0-1_all.deb`.  Does this meet the criteria better?
> 
> The additional lines replaces/provides/conflicts follow Andreas Fester's
> blog[1] and example.[2]  However, after reading current lintian's note and
> sections 7.3 and 7.6 of the Debian Policy Manual (v4.6.2.0) with
> 
> "[`Conflicts:`] can make it more difficult for the package manager to find a
> correct solution to an upgrade or installation problem." (see page 61).
> 
> I substituted `Conflicts:` for `Breaks:`.

> [1] https://www.labcorner.de/renaming-a-debian-package/
> [2] https://sources.debian.org/src/crossvc/1.5.0-1%2Betch1/debian/control/

I think you need also



> ``` file /debian/control
> Source: ruby-mdl
> Section: text
> Priority: optional
> Maintainer: Norwid Behrnd 
> Build-Depends: debhelper-compat (= 13),
>gem2deb (>= 1),
>ruby (>= 2.7),
>ruby-kramdown (>= 2.3),
>ruby-kramdown-parser-gfm (>= 1.1),
>ruby-mixlib-cli (<< 2.2),
>ruby-mixlib-cli (>= 2.1.1),
>ruby-mixlib-config (<< 4),
>ruby-mixlib-config (>= 2.2.1),
>ruby-mixlib-shellout
> Standards-Version: 4.6.2
> Vcs-Git: https://salsa.debian.org/nbehrnd/ruby-mdl.git
> Vcs-Browser: https://salsa.debian.org/nbehrnd/ruby-mdl
> Homepage: https://github.com/markdownlint/markdownlint
> Testsuite: autopkgtest-pkg-ruby
> Rules-Requires-Root: no
> 
> Package: markdownlint
> Architecture: all
> Depends: ${misc:Depends},
>  ${ruby:Depends},
>  ${shlibs:Depends}
> Replaces: ruby-mdl
> Provides: ruby-mdl
> Breaks: ruby-mdl (<< 0.13.0-1)
> Description: Markdown lint tool
>  markdownlint checks an individual markdown file, or a directory of markdown
>  files against a set of rules for syntax consistency.  In its report back
>  to the CLI, the Ruby based implementation reports the line(s) with an issue
>  identified and how to improve it.
> 
> Package: ruby-mdl
> Architecture: all
> Depends: ${misc:Depends}
> Section: oldlibs
> Description: Markdown lint tool - transitional dummy package
>  This is a transitional package for markdownlint. It can be safely removed.
> 
> ```
> 

Bug#1055352: ruby3.1: bootstrapping issue

[Samuel Thibault]

Package: ruby3.1
Version: 3.1.2-7
Severity: important

Hello,

libruby3.1 depends on ruby-sdbm, but this is an arch:any package, which
build-depends on gem2deb, which build-depends on libruby3.1, so we have
a bootstrap issue when creating a new Debian port.

Can we at some point drop the ruby-sdbm dependency? So that
bootstrapping ruby/gem2deb and the ruby packages can be bootstrapped
seamlessly on new ports?

(ATM I don't see another way than either cross-building (which is
tricky), or temporarily creating a fake ruby-sdbm package).

Samuel

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

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

Versions of packages ruby3.1 depends on:
ii  libc6 2.37-12
ii  libcrypt1 1:4.4.36-2
ii  libgmp10  2:6.3.0+dfsg-2
ii  libruby3.13.1.2-7
ii  rubygems-integration  1.18
ii  zlib1g1:1.2.13.dfsg-3

Versions of packages ruby3.1 recommends:
ii  fonts-lato2.015-1
ii  libjs-jquery  3.6.1+dfsg+~3.5.14-1

ruby3.1 suggests no packages.

-- no debconf information

-- 
Samuel
---
Pour une évaluation indépendante, transparente et rigoureuse !
Je soutiens la Commission d'Évaluation de l'Inria.

Bug#1055206: ITP: asahi-fwextract -- Asahi Linux firmware extractor

[Andreas Henriksson]

Hello,

Filling out some of the missed information below and also providing some
random thoughts of my own on this.

On Thu, Nov 02, 2023 at 09:49:51AM +0100, Tobias Heider wrote:
> Package: wnpp
> Severity: wishlist
> Owner: Tobias Heider 
> X-Debbugs-Cc: debian-de...@lists.debian.org
> 
> * Package name: asahi-fwextract
>   Version : 0.6.12
>   Upstream Authors:
  Asahi Linux Contributors
>   URL :
  
https://github.com/AsahiLinux/asahi-installer/tree/main/asahi_firmware 
> * License : MIT
>   Description : Asahi Linux firmware extractor
> 
> Scripts to extract firmware blobs from an EFI partition set up by the
> Asahi Linux installer.
> 
> I am planning to maintain this as part of the bananas team.
> 

The firmware extractor is part of upstreams (custom) installer-repository.

It also depends on asahi-scripts[1] which contains the asahi-fwupdate
utility, et.al. This also contains initramfs integration to make the
firmwares available during early boot and then provided as a tmpfs
under /lib/firmware/vendor in the running system.

Preliminary packaging is available at:
https://salsa.debian.org/bananas-team/asahi-fwextract
https://salsa.debian.org/bananas-team/asahi-scripts



Some random thoughts:

AIUI currently only initramfs-tools integration is shipped, but
maybe it would be good to also provide dracut integration (as provided
by upstream, if possible to integrate with debians dracut packaging)?!

I don't see any asahi-scripts ITP yet. Since asahi-scripts is a
dependency of asahi-fwextract I would have expected one to be posted
before this. Maybe the multiple-upstream-tarballs feature could be used
to package them together? But it's possibly more problems then benefits.

Maybe the asahi-scripts should have a less generic binary package name? and
split into multiple packages?


Regards,
Andreas Henriksson

[1]: https://github.com/AsahiLinux/asahi-scripts

Bug#1053281: linux-image-6.5.0-1-amd64: Debian does not boot at cold start on kernel 6.5.0-1-amd64 on Intel NUC 12

[Diederik de Haas]

Control: retitle -1 No display output on Intel NUC 12 on DP/HDMI on cold boot; 
works with CPU-integrated Intel Iris Xe (TB4)

On Saturday, 4 November 2023 10:19:49 CET kurom...@stodwa.org wrote:
> On 2023-11-03 14:20, Diederik de Haas wrote:
> > On Friday, 3 November 2023 13:49:01 CET Diederik de Haas wrote:
> >> My findings are:
> >> > 1. If I use Thunderbolt 4 output (usb-c at the back) everything works
> >> > fine.
> >> > 2. If I use one of DP or HDMI ports the issue occurs.
> >> > 
> >> > Manual for this Intel NUC12 states that both DP and HDMI outputs are
> >> > handled by Intel ARC A770M GPU, while Thunderbolt4 output is handled by
> >> > CPU-integrated Intel Iris Xe.
> > 
> > And does it really not boot or are you 'only' getting no display
> > output? If the latter, can you ssh into your NUC and share `dmesg` output?
> > Hopefully that'll give a clue as to why the DP/HDMI outputs aren't working
> > properly.
> 
> 2. That's a valid question :) It does boot after all, only display is stuck.

Adjusted bug title accordingly.

> I was able to get dmesg -> attached.
> I don't remember if I mentioned that, but 'nomodeset' kernel param does
> not help..

There are a few things that stood out to me from `dmesg`:

[0.00] x86/split lock detection: #AC: crashing the kernel on kernel 
split_locks and warning on user-space split_locks
...
[2.977094] EDAC MC0: Giving out device to module igen6_edac controller 
Intel_client_SoC MC#0: DEV :00:00.0 (INTERRUPT)
[2.979900] EDAC MC1: Giving out device to module igen6_edac controller 
Intel_client_SoC MC#1: DEV :00:00.0 (INTERRUPT)
[2.979922] EDAC igen6 MC1: HANDLING IBECC MEMORY ERROR
[2.979923] EDAC igen6 MC1: ADDR 0x7fffe0 
[2.979925] EDAC igen6 MC0: HANDLING IBECC MEMORY ERROR
[2.979926] EDAC igen6 MC0: ADDR 0x7fffe0 
[2.980809] EDAC igen6: v2.5.1

Likely not relevant for this bug, but you may want to look into it anyway.

[5.183228] NET: Registered PF_ALG protocol family
[5.322597] i915 :03:00.0: [drm] *ERROR* Device is non-operational; MMIO 
access returns 0x!
[5.325270] i915 :03:00.0: Device initialization failed (-5)
[5.326526] i915: probe of :03:00.0 failed with error -5

Pretty sure that *is* the relevant part.
I _think_ it's best to get the upstream maintainers involved, but I don't
know who they are.
Hopefully one of the (actual) kernel-team members does know that.

[   66.579068] snd_hda_intel :04:00.0: couldn't bind with audio component
[   66.579127] snd_hda_intel :04:00.0: HSW/BDW HD-audio HDMI/DP requires 
binding with gfx driver

My guess is that's a consequence of the earlier error. You can verify that
by checking a 'normal' boot and it then likely won't have those lines.

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

Bug#1055351: RM: pointback -- RoQA; obsolete

[Tobias Frost]

Package: ftp.debian.org
Severity: normal
User: ftp.debian@packages.debian.org
Usertags: remove
X-Debbugs-Cc: pointb...@packages.debian.org, Xiyue Deng 
Control: affects -1 + src:pointback

During sponsoring of pointback I found this message upstream:

> As of Emacs 26.1, switch-to-buffer-preserve-window-point defaults to t, which 
> solves the problem that pointback.el addresses.

Xiyue confirmed that this is the case, so I guess pointback should be retired.

-- 
tobi

Bug#1042642: Why should a FTBFS against packages in experimental be serious?

[Dmitry Shachnev]

Hello Martin!

On Sat, Nov 04, 2023 at 05:13:04PM +0100, Martin Quinson wrote:
> severity 1042642 important
> thanks
> 
> Hello Dmitry,
> 
> I am wondering why you raised the severity of #1042642 to serious. Did I miss
> the part of the policy document stating that packages *must* build correctly
> against packages in experimental? Or is there anything else that I'm missing,
> maybe?

Please see my comment in the email that bumped severity [1]. It said that
I was going to upload new Sphinx to unstable the next weekend.

I bumped the severity a bit earlier to notify the maintainers about the
upcoming upload and give them more chance to fix these bugs before the
packages actually start to FTBFS.

Now a week has passed, and I am going to upload sphinx tomorrow, 2023-11-05.

[1]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042642;msg=7

--
Dmitry Shachnev


signature.asc
Description: PGP signature

Bug#1051498: RFS: strace/6.5-0.1 [NMU] -- System call tracer

[Tobias Frost]

Am Fri, Nov 03, 2023 at 09:11:46PM +0800 schrieb Bo YU:
> On Wed, Nov 1, 2023 at 8:45 PM Tobias Frost  wrote:
> >
> > Control: tags -1 moreinfo
> >
> > Hi Bo YU,
> >
> > can you expand on the background of the NMU?
> > A new upstream version are usually only acceptable in NMUs in rare
> > circumstances, so this needs extra explanation.
> 
> Thanks. In this time, the NMU for 6.5 is meaningless because upstream
> has released
> 6.6. I will close the RFS.

(If you are still working on the package, RFS should not be closed; they
should be kept and updated.)
 
> I want the NMU because I did the NMU at 6.4 and enable test to
> non-fatal for riscv64.
> But I think kernel has fixed the for 6.5, so I want to track the issue
> from my side.
> see #1043393.
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1043393

NMUs are regulated within Debian, see the developers reference for details,
but usually new upstream releases are out of scope for an NMU (as said already)


> >
> > Have you been in contact with Steve and told them about your intentions
> > to NMU it?
> 
> In fact, I am interesting to maintain the package and want to the fix
> RC[0] bug.
> I would to ask Steve will agree this or not.:)

You need to ask him ;-)
(For completeness, there is also the ITS procedure, but Steve is generally
active, so I guess asking him directly will be better)

> Thanks.
> Bo
> [0]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054998

This bug would be in scope for an NMU, however, not by a new upstream
release, but by providing a backported fix / patch for 6.4.0-1
(see developers reference, NMU should be minimal changes only and need
to fix actual bugs.)

-- 
Cheers,
tobi

 
> >
> > Cheers,
> > --
> > tobi
> >
> > On Sat, 9 Sep 2023 02:03:55 +0800 Bo YU  wrote:
> > > Package: sponsorship-requests
> > > Severity: normal
> > >
> > > Dear mentors,
> > >
> > > I am looking for a sponsor for my package "strace":
> > >
> > >  * Package name : strace
> > >Version  : 6.5-0.1
> > >Upstream contact : [fill in name and email of upstream]
> > >  * URL  : https://strace.io
> > >  * License  : [fill in]
> > >  * Vcs  : https://salsa.debian.org/debian/strace
> > >Section  : utils
> > >
> > > The source builds the following binary packages:
> > >
> > >   strace - System call tracer
> > >   strace64 - System call tracer for 64bit binaries
> > >   strace-udeb - System call tracer
> > >
> > > To access further information about this package, please visit the
> > following URL:
> > >
> > >   https://mentors.debian.net/package/strace/
> > >
> > > Alternatively, you can download the package with 'dget' using this
> > command:
> > >
> > >   dget -x
> > https://mentors.debian.net/debian/pool/main/s/strace/strace_6.5-0.1.dsc
> > >
> > > Changes since the last upload:
> > >
> > >  strace (6.5-0.1) unstable; urgency=medium
> > >  .
> > >* Non-maintainer upload.
> > >* New upstream version 6.5
> > >
> > > >-
> > >
> > > I'd be appreciated that if you import-dsc 6.4-0.1[0] to salsa[1] also
> > >
> > > [0]:
> > https://deb.debian.org/debian/pool/main/s/strace/strace_6.4-0.1.dsc
> > > [1]: https://salsa.debian.org/debian/strace
> > >
> > > --
> > > Regards,
> > > --
> > >   Bo YU
> > >
> >

Bug#1055350: bookworm-pu: package exfatprogs/1.2.0-1+deb12u1

[Sven Hoexter]

Package: release.debian.org
Severity: normal
Tags: bookworm
User: release.debian@packages.debian.org
Usertags: pu
X-Debbugs-Cc: exfatpr...@packages.debian.org
Control: affects -1 + src:exfatprogs

[ Reason ]
https://security-tracker.debian.org/tracker/CVE-2023-45897
Low priority security issue, out-of-bounds memory access
in the exFAT fsck utility exfat2img helper.

[ Impact ]
Low priority security issue is fixed.

[ Tests ]
Manual tests performed that effected tools still work.

[ Risks ]
-

[ Checklist ]
  [X] *all* changes are documented in the d/changelog
  [X] I reviewed all changes and I approve them
  [X] attach debdiff against the package in (old)stable
  [X] the issue is verified as fixed in unstable

[ Changes ]
Adds a patch bundling the three upstream commits
which are referenced together with the CVE ID.

gbp.conf and Vcs-Git reference the bookworm branch


[ Other info ]
There wasn't a bug filled for this CVE in the BTS.
The regular upload of 1.2.2 to unstable fixed the
issue before the CVE ID was published, so there
is not yet a CVE ID mentioned in the unstable
changelog.
diff -Nru exfatprogs-1.2.0/debian/changelog exfatprogs-1.2.0/debian/changelog
--- exfatprogs-1.2.0/debian/changelog   2022-10-28 14:48:05.0 +0200
+++ exfatprogs-1.2.0/debian/changelog   2023-11-04 17:56:01.0 +0100
@@ -1,3 +1,11 @@
+exfatprogs (1.2.0-1+deb12u1) bookworm; urgency=medium
+
+  * CVE-2023-45897 Add 
debian/patches/CVE-2023-45897-out-of-bounds-memory-access
+to fix three out-of-bounds memory access issues.
+  * Add bookworm branch information to Vcs-Git and gbp.conf.
+
+ -- Sven Hoexter   Sat, 04 Nov 2023 17:56:01 +0100
+
 exfatprogs (1.2.0-1) unstable; urgency=medium
 
   * New upstream release.
diff -Nru exfatprogs-1.2.0/debian/control exfatprogs-1.2.0/debian/control
--- exfatprogs-1.2.0/debian/control 2022-10-28 14:47:18.0 +0200
+++ exfatprogs-1.2.0/debian/control 2023-11-04 17:38:34.0 +0100
@@ -6,7 +6,7 @@
 Standards-Version: 4.6.1
 Rules-Requires-Root: no
 Homepage: https://github.com/exfatprogs/exfatprogs
-Vcs-Git: https://git.sven.stormbind.net/exfatprogs.git
+Vcs-Git: https://git.sven.stormbind.net/exfatprogs.git -b bookworm
 Vcs-Browser: https://git.sven.stormbind.net/?p=sven/exfatprogs.git
 
 Package: exfatprogs
diff -Nru exfatprogs-1.2.0/debian/gbp.conf exfatprogs-1.2.0/debian/gbp.conf
--- exfatprogs-1.2.0/debian/gbp.conf2022-10-28 14:19:18.0 +0200
+++ exfatprogs-1.2.0/debian/gbp.conf2023-11-04 16:39:40.0 +0100
@@ -1,2 +1,3 @@
 [DEFAULT]
 pristine-tar = True
+debian-branch = bookworm
diff -Nru 
exfatprogs-1.2.0/debian/patches/CVE-2023-45897-out-of-bounds-memory-access 
exfatprogs-1.2.0/debian/patches/CVE-2023-45897-out-of-bounds-memory-access
--- exfatprogs-1.2.0/debian/patches/CVE-2023-45897-out-of-bounds-memory-access  
1970-01-01 01:00:00.0 +0100
+++ exfatprogs-1.2.0/debian/patches/CVE-2023-45897-out-of-bounds-memory-access  
2023-11-04 16:39:40.0 +0100
@@ -0,0 +1,67 @@
+Description: CVE-2023-45897 out-of-bounds memory access
+Origin: 
https://github.com/exfatprogs/exfatprogs/commit/ec78688e5fb5a70e13df82b4c0da1e6228d3ccdf
+ 
https://github.com/exfatprogs/exfatprogs/commit/22d0e43e8d24119cbfc6efafabb0dec6517a86c4
+ 
https://github.com/exfatprogs/exfatprogs/commit/4abc55e976573991e6a1117bb2b3711e59da07ae
+Last-Update: 2023-10-31
+Index: exfatprogs/exfat2img/exfat2img.c
+===
+--- exfatprogs.orig/exfat2img/exfat2img.c
 exfatprogs/exfat2img/exfat2img.c
+@@ -319,7 +319,7 @@ static int read_file_dentry_set(struct e
+   if (!node)
+   return -ENOMEM;
+ 
+-  for (i = 2; i <= file_de->file_num_ext; i++) {
++  for (i = 2; i <= MIN(file_de->file_num_ext, 1 + MAX_NAME_DENTRIES); 
i++) {
+   ret = exfat_de_iter_get(iter, i, );
+   if (ret || dentry->type != EXFAT_NAME)
+   break;
+Index: exfatprogs/fsck/fsck.c
+===
+--- exfatprogs.orig/fsck/fsck.c
 exfatprogs/fsck/fsck.c
+@@ -769,7 +769,7 @@ ask_again:
+   char *rename = NULL;
+   __u16 hash;
+   struct exfat_dentry *stream_de;
+-  int name_len, ret;
++  int ret;
+ 
+   switch (num) {
+   case 1:
+@@ -798,11 +798,11 @@ ask_again:
+   if (ret < 0)
+   return ret;
+ 
++  ret >>=1;
+   memcpy(dentry->name_unicode, utf16_name, ENTRY_NAME_MAX * 2);
+-  name_len = exfat_utf16_len(utf16_name, ENTRY_NAME_MAX * 2);
+-  hash = exfat_calc_name_hash(iter->exfat, utf16_name, 
(int)name_len);
++  hash = exfat_calc_name_hash(iter->exfat, utf16_name, ret);
+   exfat_de_iter_get_dirty(iter, 1, _de);
+-  stream_de->stream_name_len = (__u8)name_len;
++  stream_de->stream_name_len = 

Bug#1055349: bullseye-pu: package python-websockets/8.1-1+deb11u1

[Bastian Germann]

Package: release.debian.org
Control: affects -1 + src:python-websockets
X-Debbugs-Cc: python-websock...@packages.debian.org
User: release.debian@packages.debian.org
Usertags: pu
Tags: bullseye
Severity: normal

[ Reason ]
python-websockets in bullseye is vulnerable for CVE-2021-33880.

[ Impact ]
CVE-2021-33880 can be exploited.

[ Tests ]
No automatic tests. I have backported the upstream patch for the CVE.

[ Risks ]
None.

[ Checklist ]
  [x] *all* changes are documented in the d/changelog
  [x] I reviewed all changes and I approve them
  [x] attach debdiff against the package in (old)stable
  [x] the issue is verified as fixed in unstablediff -Nru python-websockets-8.1/debian/changelog 
python-websockets-8.1/debian/changelog
--- python-websockets-8.1/debian/changelog  2019-12-31 18:02:56.0 
+0100
+++ python-websockets-8.1/debian/changelog  2023-11-04 17:59:13.0 
+0100
@@ -1,3 +1,9 @@
+python-websockets (8.1-1+deb11u1) bullseye; urgency=medium
+
+  * Fix CVE-2021-33880 with upstream patch (closes: 989561)
+
+ -- Bastian Germann   Sat, 04 Nov 2023 17:59:13 +0100
+
 python-websockets (8.1-1) unstable; urgency=medium
 
   [ Ondřej Nový ]
diff -Nru python-websockets-8.1/debian/patches/CVE-2021-33880.patch 
python-websockets-8.1/debian/patches/CVE-2021-33880.patch
--- python-websockets-8.1/debian/patches/CVE-2021-33880.patch   1970-01-01 
01:00:00.0 +0100
+++ python-websockets-8.1/debian/patches/CVE-2021-33880.patch   2023-11-04 
17:59:13.0 +0100
@@ -0,0 +1,66 @@
+From 9428df4ba027dea422697cfae995568cd06cd06a Mon Sep 17 00:00:00 2001
+From: Aymeric Augustin 
+Date: Sun, 23 May 2021 18:51:27 +0200
+Subject: [PATCH] Use constant-time comparison for passwords.
+
+Backport of c91b4c2a to 8.1.
+---
+ src/websockets/auth.py | 29 -
+ 1 file changed, 16 insertions(+), 13 deletions(-)
+
+diff --git a/src/websockets/auth.py b/src/websockets/auth.py
+index ae204b8..aeaf15b 100644
+--- a/src/websockets/auth.py
 b/src/websockets/auth.py
+@@ -6,7 +6,9 @@
+ 
+ 
+ import functools
++import hmac
+ import http
++from typing import cast
+ from typing import Any, Awaitable, Callable, Iterable, Optional, Tuple, Type, 
Union
+ 
+ from .exceptions import InvalidHeader
+@@ -137,24 +139,25 @@ def basic_auth_protocol_factory(
+ 
+ if credentials is not None:
+ if is_credentials(credentials):
+-
+-async def check_credentials(username: str, password: str) -> bool:
+-return (username, password) == credentials
+-
++credentials_list = [cast(Credentials, credentials)]
+ elif isinstance(credentials, Iterable):
+ credentials_list = list(credentials)
+-if all(is_credentials(item) for item in credentials_list):
+-credentials_dict = dict(credentials_list)
+-
+-async def check_credentials(username: str, password: str) -> 
bool:
+-return credentials_dict.get(username) == password
+-
+-else:
++if not all(is_credentials(item) for item in credentials_list):
+ raise TypeError(f"invalid credentials argument: 
{credentials}")
+-
+ else:
+ raise TypeError(f"invalid credentials argument: {credentials}")
+ 
++credentials_dict = dict(credentials_list)
++
++async def check_credentials(username: str, password: str) -> bool:
++try:
++expected_password = credentials_dict[username]
++except KeyError:
++return False
++return hmac.compare_digest(expected_password, password)
++
+ return functools.partial(
+-create_protocol, realm=realm, check_credentials=check_credentials
++create_protocol,
++realm=realm,
++check_credentials=check_credentials,
+ )
+-- 
+2.40.1
+
diff -Nru python-websockets-8.1/debian/patches/series 
python-websockets-8.1/debian/patches/series
--- python-websockets-8.1/debian/patches/series 1970-01-01 01:00:00.0 
+0100
+++ python-websockets-8.1/debian/patches/series 2023-11-04 17:58:49.0 
+0100
@@ -0,0 +1 @@
+CVE-2021-33880.patch

Bug#1055271: mirrors: remove 'stable' symlink

[Adam D. Barratt]

Control: reassign -1 ftp.debian.org

On Fri, 2023-11-03 at 11:10 +, generoso.reim...@easymailer.live
wrote:
> please remove the 'stable' symlink on mirrors. It causes more harm
> than good.
> 
> If someone has 'stable' in their sources.list, it effectively turns
> their debian-stable system into a system that will change on a random
> date without user knowledge (careless `apt upgrade`, not reading
> release notes for stable+1).
> 
> The other symlinks like 'testing' and 'unstable' are fine and don't
> need to be removed, this is only about the 'stable' symlink.

That would need to be an archive change, not a mirroring one, so I'm
reassigning the bug to the relevant team. It's really unlikely they
would consider doing this, however.

(Users also shouldn't be getting systems with "stable" in sources.list
in the first place.)

Regards,

Adam

Bug#1055198: ITP: lzfse -- LZFSE Compression library

[Andreas Henriksson]

On Thu, Nov 02, 2023 at 01:04:03AM +0100, Tobias Heider wrote:
> Package: wnpp
> Severity: wishlist
> Owner: Tobias Heider 
> X-Debbugs-Cc: debian-de...@lists.debian.org
> 
> * Package name: lzfse
>   Version : 1.0
>   Upstream Authors:
>   URL : https://github.com/lzfse/lzfse
> * License : BSD-3-Clause
>   Description : LZFSE Compression library
> 
> LZFSE is a Lempel-Ziv style data compression algorithm using Finite
> State Entropy coding. It targets similar compression rates at higher
> compression and decompression speed compared to deflate using zlib.
> 
> I plan to maintain this as part of the bananas team.

Calling all SO versioning experts!

The upstream project does not have any shared object version set.
A downstream patch was introduced to set one:
https://salsa.debian.org/bananas-team/lzfse/-/blob/debian/unstable/debian/patches/0001-debian-set-library-SONAME.patch

Upstream has seen no activity since 2017, so trying to interact is
assumed to not generate much. Also the ABI is unlikely to change (since
no changes are being made).

I've previously suggested that maybe it would be better to set a
debian-specific version (0d?), to avoid the theoretical situation
that upstream one day ships a different ABI under the 1 so version.

I would welcome peoples input here on what you think is best from
the debian perspective. Obviously we're going to be incompatible with
everyone else[1], unless you install/runtime-depend-on the -dev package
for the unversioned so symlink. Please speak now before this is
submitted for NEW.

FWIW lzfse is needed to extract files compressed by Apple and shipped in macOS
containing embedded firmwares. See asahi-fwextract ITP: #1055206

Regards,
Andreas Henriksson


[1]: 
https://salsa.debian.org/bananas-team/asahi-fwextract/-/blob/debian/unstable/debian/patches/0001-Use-versioned-library-name-for-liblzfse.patch

Bug#1055155: bookworm-pu: package exim4/4.96-15+deb12u3 (2nd try for new bug)

[Andreas Metzler]

On 2023-11-04 Salvatore Bonaccorso  wrote:
> On Wed, Nov 01, 2023 at 12:03:37PM +0100, Andreas Metzler wrote:
[...]
> > * Update code to 4.96.2, fixing issues with the proxy protocol
> >   (CVE-2023-42117) and the `dnsdb` lookup subsystem (CVE-2023-42219). It
> >   also includes additional hardening for spf lookups, however CVE-2023-42218

> The mentioned CVEs have a typo. I believe this should be
> CVE-2023-42117 and CVE-2023-42119 (and for completeness about the
> libspf2 mentioning CVE-2023-42118).

Thank you, updated.

cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'
diff -Nru exim4-4.96/debian/changelog exim4-4.96/debian/changelog
--- exim4-4.96/debian/changelog	2023-09-29 22:38:02.0 +0200
+++ exim4-4.96/debian/changelog	2023-11-01 07:07:57.0 +0100
@@ -1,3 +1,29 @@
+exim4 (4.96-15+deb12u3) bookworm; urgency=medium
+
+  * Multiple bugfixes from upstream GIT master:
++ 75_74-Cancel-early-pipe-on-an-observed-advertising-change.patch
++ 75_76-Expansions-disallow-UTF-16-surrogates-from-utf8clean.patch
+  (Upstream bug 2998)
++ 75_77-GnuTLS-fix-crash-with-tls_dhparam-none.patch
++ 75_79-Fix-recipients-expansion-when-used-within-run.-.-Bug.patch
+  (Upstream bug 3013)
++ 75_82-GnuTLS-fix-autogen-cert-expiry-date.-Bug-3014.patch: Fix on-demand
+  TLS cert expiry date. Closes: #1043233
+  (Upstream bug 3014)
++ 75_83-Re-fix-live-variable-value-free.-The-inital-fix-resu.patch
++ 76-10-Fix-tr.-and-empty-strings.-Bug-3023.patch ((Upstream bug 3023)
++ 76-12-DNS-more-hardening-against-crafted-responses.patch
+  * tests/basic: Add isolation-container restriction (needs a running
+exim daemon).
+  * Add ${run } expansion test to tests/basic.
+  * Update code to 4.96.2, fixing issues with the proxy protocol
+(CVE-2023-42117) and the `dnsdb` lookup subsystem (CVE-2023-42119). It
+also includes additional hardening for spf lookups, however CVE-2023-42118
+was diagnosed as a vulnerability in the libspf2 library and needs to be
+addressed there. Closes: #1053310
+
+ -- Andreas Metzler   Wed, 01 Nov 2023 07:07:57 +0100
+
 exim4 (4.96-15+deb12u2) bookworm-security; urgency=high
 
   * Non-maintainer upload by the Security Team.
diff -Nru exim4-4.96/debian/patches/75_74-Cancel-early-pipe-on-an-observed-advertising-change.patch exim4-4.96/debian/patches/75_74-Cancel-early-pipe-on-an-observed-advertising-change.patch
--- exim4-4.96/debian/patches/75_74-Cancel-early-pipe-on-an-observed-advertising-change.patch	1970-01-01 01:00:00.0 +0100
+++ exim4-4.96/debian/patches/75_74-Cancel-early-pipe-on-an-observed-advertising-change.patch	2023-11-01 07:03:21.0 +0100
@@ -0,0 +1,35 @@
+From 4d108ee9b8e5fb212c31812fef61529cd414 Mon Sep 17 00:00:00 2001
+From: Jeremy Harris 
+Date: Mon, 12 Jun 2023 22:13:46 +0100
+Subject: [PATCH] Cancel early-pipe on an observed advertising change
+
+---
+ src/transports/smtp.c | 3 +++
+ 1 file changed, 3 insertions(+)
+
+diff --git a/src/transports/smtp.c b/src/transports/smtp.c
+index c72028ce9..24ee577a2 100644
+--- a/src/transports/smtp.c
 b/src/transports/smtp.c
+@@ -,15 +,18 @@ if (pending_EHLO)
+   *(tls_out.active.sock < 0
+ 	? >ehlo_resp.cleartext_features : >ehlo_resp.crypted_features) =
+ 	  peer_offered;
+   *ap = authbits;
+   write_ehlo_cache_entry(sx);
+   }
+ else
++  {
+   invalidate_ehlo_cache_entry(sx);
++  sx->early_pipe_active = FALSE;	/* cancel further early-pipe on this conn */
++  }
+ 
+ return OK;		/* just carry on */
+ }
+ # ifdef EXPERIMENTAL_ESMTP_LIMITS
+ /* If we are handling LIMITS, compare the actual EHLO LIMITS values with the
+ cached values and invalidate cache if different.  OK to carry on with
+ connect since values are advisory. */
+-- 
+2.40.1
+
diff -Nru exim4-4.96/debian/patches/75_76-Expansions-disallow-UTF-16-surrogates-from-utf8clean.patch exim4-4.96/debian/patches/75_76-Expansions-disallow-UTF-16-surrogates-from-utf8clean.patch
--- exim4-4.96/debian/patches/75_76-Expansions-disallow-UTF-16-surrogates-from-utf8clean.patch	1970-01-01 01:00:00.0 +0100
+++ exim4-4.96/debian/patches/75_76-Expansions-disallow-UTF-16-surrogates-from-utf8clean.patch	2023-11-01 07:03:21.0 +0100
@@ -0,0 +1,99 @@
+From 1209e3e19e292cee517e43a2ccfe9b44b33bb1dc Mon Sep 17 00:00:00 2001
+From: Jasen Betts 
+Date: Sun, 23 Jul 2023 13:43:59 +0100
+Subject: [PATCH] Expansions: disallow UTF-16 surrogates from ${utf8clean:...}.
+  Bug 2998
+
+---
+ doc/ChangeLog |  4 
+ src/expand.c  | 27 +--
+ 2 files changed, 21 insertions(+), 10 deletions(-)
+
+--- a/src/expand.c
 b/src/expand.c
+@@ -7731,11 +7731,11 @@ NOT_ITEM: ;
+ 
+ 	case EOP_UTF8CLEAN:
+ 	  {
+ 	  int seq_len = 0, index = 0;
+ 	  int bytes_left = 0;
+-	  long codepoint = -1;
++	  ulong codepoint = (ulong)-1;
+ 	  int 

Bug#1055348: jetty9: Update from DLA 3641 breaks puppetdb ("Exception in thread "main" java.lang.IllegalStateException: KeyStores with multiple certificates are not supported on the base class org.ecl

[Adam D. Barratt]

Source: jetty9
Version: 9.4.50-4+deb10u1
Severity: serious
X-Debbugs-Cc: d...@debian.org

Hi,

Upgrading libjetty9-java and libjetty9-extra-java to the version from
DLA 3641-1 reliably causes PuppetDB to fail to start, with the
stacktrace shown below. Downgrading resolves the issue.

I'm not sure which keystore is being referred to, but none of the files
listed in /etc/puppetdb/conf.d/jetty.ini appear to contain more than a
single certificate.

Regards,

Adam

-- Logs begin at Sat 2023-11-04 14:52:45 UTC, end at Sat 2023-11-04 16:16:11 
UTC. --
Nov 04 14:52:50 handel systemd[1]: Started Puppet data warehouse server.
Nov 04 14:53:22 handel java[1669]: WARNING: boolean? already refers to: 
#'clojure.core/boolean? in namespace: puppetlabs.trapperkeeper.internal, being 
replaced by: #'puppetlabs.kitchensink.core/boolean?
Nov 04 14:53:32 handel java[1669]: 14:53:32.886 [main] DEBUG 
puppetlabs.puppetdb.http - The v1 API has been retired; please use v4 Caught 
HTTP processing exception
Nov 04 14:53:32 handel java[1669]: 14:53:32.898 [main] DEBUG 
puppetlabs.puppetdb.http - The v2 API has been retired; please use v4 Caught 
HTTP processing exception
Nov 04 14:53:32 handel java[1669]: 14:53:32.899 [main] DEBUG 
puppetlabs.puppetdb.http - The v3 API has been retired; please use v4 Caught 
HTTP processing exception
Nov 04 14:53:34 handel java[1669]: 14:53:34.073 [main] DEBUG 
puppetlabs.trapperkeeper.bootstrap - Loading bootstrap config from classpath: 
'jar:file:/usr/share/puppetdb/puppetdb.jar!/bootstrap.cfg'
Nov 04 14:53:39 handel java[1669]: Exception in thread "main" 
java.lang.IllegalStateException: KeyStores with multiple certificates are not 
supported on the base class org.eclipse.jetty.util.ssl.SslContextFactory
Nov 04 14:53:39 handel java[1669]: at 
org.eclipse.jetty.util.ssl.SslContextFactory.newSniX509ExtendedKeyManager(SslContextFactory.java:1289)
Nov 04 14:53:39 handel java[1669]: at 
org.eclipse.jetty.util.ssl.SslContextFactory.getKeyManagers(SslContextFactory.java:1271)
Nov 04 14:53:39 handel java[1669]: at 
org.eclipse.jetty.util.ssl.SslContextFactory.load(SslContextFactory.java:373)
Nov 04 14:53:39 handel java[1669]: at 
org.eclipse.jetty.util.ssl.SslContextFactory.doStart(SslContextFactory.java:244)
Nov 04 14:53:39 handel java[1669]: at 
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:73)
Nov 04 14:53:39 handel java[1669]: at 
org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:169)
Nov 04 14:53:39 handel java[1669]: at 
org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:117)
Nov 04 14:53:39 handel java[1669]: at 
org.eclipse.jetty.server.SslConnectionFactory.doStart(SslConnectionFactory.java:97)
Nov 04 14:53:39 handel java[1669]: at 
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:73)
Nov 04 14:53:39 handel java[1669]: at 
org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:169)
Nov 04 14:53:39 handel java[1669]: at 
org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:117)
Nov 04 14:53:39 handel java[1669]: at 
org.eclipse.jetty.server.AbstractConnector.doStart(AbstractConnector.java:323)
Nov 04 14:53:39 handel java[1669]: at 
org.eclipse.jetty.server.AbstractNetworkConnector.doStart(AbstractNetworkConnector.java:81)
Nov 04 14:53:39 handel java[1669]: at 
org.eclipse.jetty.server.ServerConnector.doStart(ServerConnector.java:234)
Nov 04 14:53:39 handel java[1669]: at 
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:73)
Nov 04 14:53:39 handel java[1669]: at 
org.eclipse.jetty.server.Server.doStart(Server.java:401)
Nov 04 14:53:39 handel java[1669]: at 
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:73)
Nov 04 14:53:39 handel java[1669]: at 
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
Nov 04 14:53:39 handel java[1669]: at 
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
Nov 04 14:53:39 handel java[1669]: at 
java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
Nov 04 14:53:39 handel java[1669]: at 
java.base/java.lang.reflect.Method.invoke(Method.java:566)
Nov 04 14:53:39 handel java[1669]: at 
clojure.lang.Reflector.invokeMatchingMethod(Reflector.java:167)
Nov 04 14:53:39 handel java[1669]: at 
clojure.lang.Reflector.invokeNoArgInstanceMember(Reflector.java:438)
Nov 04 14:53:39 handel java[1669]: at 
puppetlabs.trapperkeeper.services.webserver.jetty9_core$eval43528$start_webserver_BANG___43533$fn__43534$fn__43535.invoke(jetty9_core.clj:685)
Nov 04 14:53:39 handel java[1669]: at 

Bug#1052803: Help fixing a gettext translation test

[Mathias Gibbens]

Hi all,

  I'm working on fixing bug #1052803 for golang-github-gosexy-gettext.
That package's tests started failing, and I'm pretty sure it was caused
by the upload of src:glibc 2.37-8 which backported a patch from bug
#874160 that treats language encodings like C.UTF-8 as the C locale.

  This change effectively "turns off" translations, unless you specify
some specific encoding like "en_US.utf8". While I can apply the
attached patch that fixes the tests, it feels less than ideal. And as
this will be a NMU to prevent the package from being AUTORM'ed and
taking src:lxd along with it, I'd like to fix this properly. I'm just
not familiar enough with gettext to know if there's a better solution.

  A simple reproducer is listed below. On a sid system, the first
invocation will fail to return the properly translated string, but the
second will (substitute with your preferred locale).

  Thanks for any advice!

Mathias
(BCC: bug #1052803)

> $ dget 
> https://deb.debian.org/debian/pool/main/g/golang-github-gosexy-gettext/golang-github-gosexy-gettext_0~git20130221-2.1.dsc
> $ cd golang-github-gosexy-gettext-0~git20130221/
> $ LC_ALL=C.UTF-8 LANGUAGE="es_MX.utf8" TEXTDOMAINDIR=./examples/ gettext -d 
> example "Hello, world!"
> $ LC_ALL=en_US.utf8 LANGUAGE="es_MX.utf8" TEXTDOMAINDIR=./examples/ gettext 
> -d example "Hello, world!"
diff --git a/debian/control b/debian/control
index d1364e1..18690eb 100644
--- a/debian/control
+++ b/debian/control
@@ -4,7 +4,7 @@ Priority: optional
 Maintainer: Steve Langasek 
 Build-Depends: debhelper (>= 11~),
dh-golang,
-   golang-any,
+   golang-any, locales-all
 Standards-Version: 4.2.1
 Homepage: https://github.com/gosexy/gettext
 XS-Go-Import-Path: github.com/gosexy/gettext
diff --git a/debian/rules b/debian/rules
index 2d9b72c..1451b07 100755
--- a/debian/rules
+++ b/debian/rules
@@ -20,7 +20,7 @@ override_dh_auto_build:
rm obj-*/src/github.com/gosexy/gettext/examples/*/*.pot
 
 override_dh_auto_test:
-   LC_ALL=C.UTF-8 dh_auto_test
+   LC_ALL=en_US.utf8 dh_auto_test
 
 get-orig-source:
rm -rf $(PKG)

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

Bug#1055321: pipx: shell completions are not installed

[Ilya Grigoriev]

Package: pipx
Version: 1.2.1-1
Followup-For: Bug #1055321
X-Debbugs-Cc: debian.10.il...@xoxy.net

Hi Stefano,

> I had a look at this and decided that fixing #944469 is probably the
> better way to go.

That makes sense, thanks for looking into it!

My only reservation is that the bug you referenced seems to be focused
on bash only, whereas I tend to use `fish`.

  Ilya.

Bug#1055347: RFA: kitty -- fast, featureful, GPU based terminal emulator

[James McCoy]

Package: wnpp
Severity: normal
X-Debbugs-Cc: ki...@packages.debian.org, debian-de...@lists.debian.org
Control: affects -1 + src:kitty

I request an adopter for the kitty package.  I no longer use the package
and don't have time to figure out how to deal with the new golang parts
of the package.

The package description is:
 Kitty supports modern terminal features like: graphics, unicode,
 true-color, OpenType ligatures, mouse protocol, focus tracking, and
 bracketed paste.
 .
 Kitty has a framework for "kittens", small terminal programs that can be used
 to extend its functionality.

Bug#1055346: dh-nodejs: should provide dh_nodejs_autodocs

[Bastien Roucariès]

Package: dh-nodejs
Version: 0.15.15
Severity: important

Dear Maintainer,

dh-nodejs should provide dh-nodejs-autodocs


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

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

Versions of packages dh-nodejs depends on:
ii  debhelper 13.11.7
ii  libdebian-copyright-perl  0.2-6
ii  libdebian-source-perl 0.122
ii  libdpkg-perl  1.22.1
ii  libgraph-perl 1:0.9727-1
ii  libipc-run-perl   20231003.0-1
ii  libjson-perl  4.1-1
ii  libyaml-perl  1.30-2
ii  nodejs18.13.0+dfsg1-1
ii  perl  5.36.0-9

dh-nodejs recommends no packages.

Versions of packages dh-nodejs suggests:
ii  node-rollup-plugin-commonjs  25.0.4+ds1-1
ii  node-rollup-plugin-node-resolve  15.1.0+ds-1
ii  pkg-js-tools 0.15.15
ii  rollup   3.28.0-2

-- no debconf information

Bug#1042642: Why should a FTBFS against packages in experimental be serious?

[Martin Quinson]

severity 1042642 important
thanks

Hello Dmitry,

I am wondering why you raised the severity of #1042642 to serious. Did I miss
the part of the policy document stating that packages *must* build correctly
against packages in experimental? Or is there anything else that I'm missing,
maybe?


Thanks for your explanations, 
Mt


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

Bug#1018855: gtkpod: unmaintained upstream

[Bastian Germann]

Control: retitle -1 RM: gtkpod -- RoQA; unmaintained upstream; hinders anjuta 
removal
Control: reassign -1 ftp.debian.org

As announced by Jeremy at #1051109, I am filing this RM bug.
Please remove gtkpod. It is unmaintained upstream and hinders the planned 
anjuta removal.

Bug#1055312: adduser: "addgroup user group" is mentioned in man page but does not work anymore (ex bug 664869)

[Marc Haber]

On Fri, Nov 03, 2023 at 11:27:43PM +0100, boffi wrote:
> $ man addgroup # says
> ...
> 
>Add an existing user to an existing group
>If called with two non-option arguments, adduser will add  an  existing
>user to an existing group.

adduser and addgroup share a man page, and the two-argument form is only
supported for adduser, not for addgroup, see SYNOPSIS in the manual
page.

And the text you quoted explicitly says that it is add_user_ that will
add an existing user to an existing group.

> but when I try to add a user to a group, this is what it happens
> 
> $ sudo addgroup donald ducks
> [sudo] password for boffi: 
> fatal: addgroup with two arguments is an unspecified operation.
> $ 

The message is correct, it is an unspecified operation according to the
SYNOPSIS.

Let me know what we can improve, but I think that everything is fine
here.

Greetings
Marc

-- 
-
Marc Haber | "I don't trust Computers. They | Mailadresse im Header
Leimen, Germany|  lose things."Winona Ryder | Fon: *49 6224 1600402
Nordisch by Nature |  How to make an American Quilt | Fax: *49 6224 1600421

Bug#1055345: git-buildpackage: Please document how to build against a package from experimental

[Martin Quinson]

Package: git-buildpackage
Version: 0.9.32
Severity: wishlist
Tags: patch

Hello,

thanks a lot for this package, that very often saves my life when packaging.
There is one thing however where gbp could be more helpful, it's when I have to
build my package against a build-depend that comes from experimental.

I finally found a way to do it, and I propose the following patch for the
documentation for the next person looking for this information. I fully
acknowledge that this documentation is somehow suboptimal, and that the gbp
tool could be more helpful here, but the proposed documentation would already
be great.

Again, thanks for this great tool and for your time.
Mt


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

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

Versions of packages git-buildpackage depends on:
ii  devscripts 2.23.6
ii  git    1:2.40.1-1
ii  man-db 2.11.2-3
ii  python3    3.11.4-5+b1
ii  python3-dateutil   2.8.2-3
ii  python3-pkg-resources  68.1.2-1
ii  python3-yaml   6.0.1-1
ii  sensible-utils 0.0.20

Versions of packages git-buildpackage recommends:
ii  cowbuilder    0.89
ii  pbuilder  0.231
ii  pristine-tar  1.50
ii  python3-requests  2.31.0+dfsg-1

Versions of packages git-buildpackage suggests:
ii  python3-notify2  0.3-5
ii  sudo 1.9.14p2-1
ii  unzip    6.0-28

-- no debconf information

---
 docs/chapters/special.xml |   25 +
 1 file changed, 25 insertions(+)

Index: b/docs/chapters/special.xml
===
--- a/docs/chapters/special.xml
+++ b/docs/chapters/special.xml
@@ -40,6 +40,31 @@
 
 
 
+
+Using build-depends from experimental
+
+To build your package against a build-depends taken from experimental, you first need
+to configure your pbuilder. To that extend, add the following to
+~/.pbuilderrc to instruct pbuilder to take build depends from
+experimental when they cannot be satisfied from unstable.
+
+
+PBUILDERSATISFYDEPENDSCMD=/usr/lib/pbuilder/pbuilder-satisfydepends-experimental
+
+
+You then need to add experimental to the apt configuration within the chroot.
+The simplest for that is to edit the config file from outside of the chroot directly,
+as follows:
+
+sudo bash -c "echo 'deb http://deb.debian.org/debian experimental main' >> /var/cache/pbuilder/base.cow/etc/apt/sources.list"
+
+
+Once everything is setup (and once you updated apt cache files with
+git-pbuilder update), you can force the build of your package against
+a given package from experimental by specifying the relevant version in the
+debian/control.
+
+
 
 Importing NMUs
 


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

Bug#1055344: O: db-defaults -- Default Berkeley Database Libraries

[Bastian Germann]

Package: wnpp

I am no longer interested in maintaining this package.
I have reduced the number of binary packages to the minimum that would make sense as a transitional 
package for a db5.3 compatibility package if it is to be removed (see: #987013).

Bug#1055343: RFP: anura -- 2D game engine

[Alexandre Detiste]

Package: wnpp
Severity: wishlist
X-Debbugs-Cc: debian-devel-ga...@lists.debian.org, Dmitry E. Oboukhov 


* Package name: anura
  Version : 4.0.0
  Upstream Contact: https://github.com/frogatto/frogatto/wiki
* URL : https://github.com/anura-engine/anura/
* License : misc free licenses as a for of frogatto
  Programming Lang: C++
  Description : 2D game engine


Anura is the engine part that was spun off "frogatto" game.

It is needed to package this new engine to update frogatto
and to switch this game to libSDL2
and also drop leaf library libsdl-ttf2.0-0 from the archive.

Greetings,

See: bug https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1038354

Bug#1055337: python-cffi fails autopkg tests with Python 3.12

[Matthias Klose]

On 04.11.23 16:17, Stefano Rivera wrote:

Hi Matthias (2023.11.04_14:19:12_+)

WARNING: Retrying (Retry(total=4, connect=None, read=None, redirect=None, 
status=None)) after connection broken by 'ProxyError('Cannot connect to proxy.', 
NewConnectionError(': Failed to establish a new connection: [Errno 111] Connection 
refused'))': /simple/setuptools/

That just looks like no Internet access during the tests. Broken proxy
on the host?


This is not the autopkg test. It's the build which fails. The build 
isn't supposed to access the network during the build.

Bug#1055337: python-cffi fails autopkg tests with Python 3.12

[Stefano Rivera]

Hi Matthias (2023.11.04_14:19:12_+)
> WARNING: Retrying (Retry(total=4, connect=None, read=None, redirect=None, 
> status=None)) after connection broken by 'ProxyError('Cannot connect to 
> proxy.', NewConnectionError(' object at 0x7f344bf33f80>: Failed to establish a new connection: [Errno 111] 
> Connection refused'))': /simple/setuptools/

That just looks like no Internet access during the tests. Broken proxy
on the host?

Stefano

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272

Bug#1055342: RFA: kas -- Setup tool for bitbake based projects

[Bastian Germann]

Package: wnpp

I do not use kas anymore. Is is a tool for setting up bitbake projects.
Please consider adopting it if you have the time and skills to maintain it.

Bug#1055341: RM: vim-editorconfig -- ROM; Obsolete, included in vim

[Michael Fladischer]

Package: ftp.debian.org
Severity: normal
User: ftp.debian@packages.debian.org
Usertags: remove
X-Debbugs-Cc: vim-editorcon...@packages.debian.org
Control: affects -1 + src:vim-editorconfig

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

vim-editorconfig is now shipped as part of vim-runtime. To avoid confusion for
our users it is best to remove it from the archive.

-BEGIN PGP SIGNATURE-

iQFPBAEBCgA5FiEEqVSlRXW87UkkCnJc/9PIi5l90WoFAmVGWVYbHGZsYWRpc2No
ZXJtaWNoYWVsQGZsYWRpLmF0AAoJEP/TyIuZfdFqzKoIAJ6wETjgCEVaaZgldsPX
rhAotpsvE7K7rx3TmAdoTSF73tvTmFLK21XTFwc9qBV9L7Es6DAZ+5aQFdeVig1H
KmbAsQkF5Z+r2iJ98zAEm0EcU5eSSfHPHSrU6lMLoFr0Gc3M/mhfcA7VvGhHwGS4
8rQgPdNiZ6998tpsJVZet+AU7GZVQ5oWRLxe4KQ7XFSuSaBfxrSuq9UQTqHeYY8M
V44sM/BoS8HcjlFOmDmVitwQjO71rUOletZUezshhl5Y+5McA/hH1wVlJWSL1+0X
z4zx8gAfNhWqpa4asztbZzgxF3uRmTjYuemv07EUBxGSYbWkVro812J5lJVKzVoc
nRM=
=Ez0G
-END PGP SIGNATURE-

Bug#1054455: bullseye-pu: package weborf/0.17-3

[Salvatore Bonaccorso]

Hi Salvo,

On Tue, Oct 24, 2023 at 09:58:30AM +0200, Salvo Tomaselli wrote:
> > This version was already used:
> > https://snapshot.debian.org/package/weborf/0.17-4/
> 
> Sorry!
> 
> Attaching a new debdiff file with the correct version

Now there is a off-by-one in the distro version :)

I believe it should be 0.17-3+deb11u1.

Regards,
Salvatore

Bug#1055340: firefox-esr: Firefox tabs has no text (only site favicon is showed)

[Nicolas James]

Package: firefox-esr
Version: 115.4.0esr-1~deb11u1
Severity: important
X-Debbugs-Cc: nicolas.ja...@gmail.com

Part of "apt-get upgrade" on Debian11 upgraded my firefox to 
115.4.0esr-1~deb11u1 and now the tabs in firefox does not contain text, only 
the favicon.
I reinstalled Debian11 in a virtual machine recently and I can see the same 
behavior.
Also I think the problem is located in the 'System theme" packaged with the 
debian/firefox because if i switch the theme to "Light" then the tabs text is 
visible.


-- Package-specific info:


-- Addons package information

-- System Information:
Debian Release: 11.8
  APT prefers oldstable-updates
  APT policy: (500, 'oldstable-updates'), (500, 'oldstable-security'), (500, 
'oldstable'), (100, 'bullseye-fasttrack'), (100, 'bullseye-backports-staging')
Architecture: amd64 (x86_64)

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

Versions of packages firefox-esr depends on:
ii  debianutils  4.11.2
ii  fontconfig   2.13.1-4.2
ii  libasound2   1.2.4-1.1
ii  libatk1.0-0  2.36.0-2
ii  libc62.31-13+deb11u7
ii  libcairo-gobject21.16.0-5
ii  libcairo21.16.0-5
ii  libdbus-1-3  1.12.28-0+deb11u1
ii  libdbus-glib-1-2 0.110-6
ii  libevent-2.1-7   2.1.12-stable-1
ii  libffi7  3.3-6
ii  libfontconfig1   2.13.1-4.2
ii  libfreetype6 2.10.4+dfsg-1+deb11u1
ii  libgcc-s110.2.1-6
ii  libgdk-pixbuf-2.0-0  2.42.2+dfsg-1+deb11u1
ii  libglib2.0-0 2.66.8-1
ii  libgtk-3-0   3.24.24-4+deb11u3
ii  libpango-1.0-0   1.46.2-3
ii  libstdc++6   10.2.1-6
ii  libx11-6 2:1.7.2-1+deb11u2
ii  libx11-xcb1  2:1.7.2-1+deb11u2
ii  libxcb-shm0  1.14-3
ii  libxcb1  1.14-3
ii  libxcomposite1   1:0.4.5-1
ii  libxdamage1  1:1.1.5-2
ii  libxext6 2:1.3.3-1.1
ii  libxfixes3   1:5.0.3-2
ii  libxrandr2   2:1.5.1-1
ii  libxtst6 2:1.2.3-1
ii  procps   2:3.3.17-5
ii  zlib1g   1:1.2.11.dfsg-2+deb11u2

Versions of packages firefox-esr recommends:
ii  libavcodec58  7:4.3.6-0+deb11u1

Versions of packages firefox-esr suggests:
ii  fonts-lmodern  2.004.5-6.1
pn  fonts-stix | otf-stix  
ii  libcanberra0   0.30-7
ii  libgssapi-krb5-2   1.18.3-6+deb11u4
ii  pulseaudio 14.2-2

-- no debconf information

Bug#1055155: bookworm-pu: package exim4/4.96-15+deb12u3 (2nd try for new bug)

[Salvatore Bonaccorso]

Hi Andreas,

On Wed, Nov 01, 2023 at 12:03:37PM +0100, Andreas Metzler wrote:
> Package: release.debian.org
> Severity: normal
> Tags: bookworm
> User: release.debian@packages.debian.org
> Usertags: pu
> Control: affects -1 + src:exim4
> 
> Hello,
> 
> I would like to push another round of cherry-picked upstream fixes to
> bookworm, including the update to 4.96.2 to fix two non-DSA minor
> security issues.
> 
> The changes are included in the new upstream (4.97 rc) uploads to sid which=
>  are present in sid and testing.
> 
> 
> * Multiple bugfixes from upstream GIT master:
>   + 75_74-Cancel-early-pipe-on-an-observed-advertising-change.patch
>   + 75_76-Expansions-disallow-UTF-16-surrogates-from-utf8clean.patch
> (Upstream bug 2998)
>   + 75_77-GnuTLS-fix-crash-with-tls_dhparam-none.patch
>   + 75_79-Fix-recipients-expansion-when-used-within-run.-.-Bug.patch
> (Upstream bug 3013)
> > ${run expansion breakage, similar to #1025420.
>   + 75_82-GnuTLS-fix-autogen-cert-expiry-date.-Bug-3014.patch: Fix on-demand
> TLS cert expiry date. Closes: #1043233
> (Upstream bug 3014)
> > This is major hickup, bordering on RC.
> 
>   + 75_83-Re-fix-live-variable-value-free.-The-inital-fix-resu.patch
> > Another patch for ${run} expansion breakage.
>   + 76-10-Fix-tr.-and-empty-strings.-Bug-3023.patch ((Upstream bug 3023)
>   + 76-12-DNS-more-hardening-against-crafted-responses.patch
> * tests/basic: Add isolation-container restriction (needs a running
>   exim daemon).
> * Add ${run } expansion test to tests/basic.
> * Update code to 4.96.2, fixing issues with the proxy protocol
>   (CVE-2023-42117) and the `dnsdb` lookup subsystem (CVE-2023-42219). It
>   also includes additional hardening for spf lookups, however CVE-2023-42218

The mentioned CVEs have a typo. I believe this should be
CVE-2023-42117 and CVE-2023-42119 (and for completeness about the
libspf2 mentioning CVE-2023-42118).

Regards,
Salvatore

Bug#873186: please drop transitional package gnupg2

[Bastian Germann]

On Fri, 25 Aug 2017 13:54:12 +0200 Holger Levsen wrote:

Please drop transitional package gnupg2 for Buster, as it has been released 
with Stretch.



Please also drop gpgv2, which can be done now because the only reverse dependency only has an 
alternative dependency on it.

Bug#1054692: tomlplusplus: FTBFS: ../tests/lib_catch2.h:35:2: error: #error Catch2 is missing!

[Bastian Germann]

I am uploading a NMU to fix this.
As this involves a repack I am also updating the upstream version.

Bug#1055339: debian-science: please replace recommendation of src:dolfin by src:fenics-dolfinx

[Alexandre Detiste]

Source: debian-science
Version: 1.14.5
Severity: normal

Hi,

Please replace recommandations of legacy python3-dolfin
by the newer python3-dolfinx (it's the continuation
of the same codebase).


I've alse filled #1055338 as oldlibs,
which would have tipped you to take the same action
someday somehow, but it's better to be explicit :-).

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055338

Greetings,


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

Kernel: Linux 6.5.0-3-amd64 (SMP w/2 CPU threads; PREEMPT)
Kernel taint flags: TAINT_USER
Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_BE:fr
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Bug#944469: Using bash-completion with python-argcomplete

[Stefano Rivera]

Hi Marc (2022.09.21_06:10:13_+0200)

I just had a look at this (following breadcrumbs from #1055321), and
staged a new upstream version in git, as well as a change to fix this
bug.

I don't think bash_completion provides any mechanism to install a global
plugin like this, except for /etc/bash_completion.d

See: https://github.com/scop/bash-completion/issues/1055 for a related
discussion.

So, /etc/bash_completion.d is the logical installation place.

I updated the package to put a thin loading shim into
/etc/bash_completion.d. That should be safe to have as a conffile.
I first went down the road of a symlink, but I think that could be
problematic if a package is left in the conffiles state.

Haven't uploaded it yet. Have a look, I'll probably upload next week.

Stefano

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272

Bug#1055326: prometheus-postfix-exporter: systemd support is missing

[Daniel Swarbrick]

systemd support is broken upstream. See 
https://github.com/kumina/postfix_exporter/issues/55


This is mentioned in the Debian changelog:

prometheus-postfix-exporter (0.3.0-2) unstable; urgency=medium

  [ Daniel Swarbrick ]
  ...
  * Disable systemd journal support until fixed upstream



OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1055321: pipx: shell completions are not installed

[Stefano Rivera]

Hi Ilya (2023.11.04_08:12:30_+0200)

I had a look at this and decided that fixing #944469 is probably the
better way to go.

Stefano

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272

Bug#1055338: override: dolfin:oldlibs/optional

[Alexandre Detiste]

Package: ftp.debian.org
Severity: normal
User: ftp.debian@packages.debian.org
Usertags: override
X-Debbugs-Cc: dol...@packages.debian.org, 
debian-science-maintain...@lists.alioth.debian.org
Control: affects -1 + src:dolfin

Dear FTP Masters,

src:dolfin is the older repository of what is now
packaged as src:fenics-dolfinx and should
not be used for new projects.

FWIW: both src:dolfin & src:fenics-dolfinx are managed by the same team.

Can you please tag it as such in the repository ?


Thanks


tchet@brix ~ $ apt show python3-dolfin | grep -e Maint -e Home
Section: python
Maintainer: Debian Science Team 

Homepage: http://fenicsproject.org

tchet@brix ~ $ apt show python3-dolfinx | grep -e Maint -e Home -e Section
Section: python
Maintainer: Debian Science Team 

Homepage: http://fenicsproject.org

Bug#1055337: python-cffi fails autopkg tests with Python 3.12

[Matthias Klose]

Source: python-cffi
Version: 1.16.0-1
Severity: important
User: debian-pyt...@lists.debian.org
Usertags: python3.12

python-cffi fails autopkg tests with Python 3.12

see
https://launchpadlibrarian.net/695645855/buildlog_ubuntu-noble-amd64.python-cffi_1.16.0-1ubuntu1_BUILDING.txt.gz

=== FAILURES ===
_ TestZIntegration.test_infrastructure _

self = 

def test_infrastructure(self):

  run_setup_and_program('infrastructure', '''

import snip_infrastructure
assert snip_infrastructure.func() == 42
''')

testing/cffi0/test_zintegration.py:128:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
testing/cffi0/test_zintegration.py:107: in run_setup_and_program
venv_dir = create_venv(dirname + '-cpy')
testing/cffi0/test_zintegration.py:29: in create_venv
subprocess.check_call([
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

popenargs = (['/tmp/ffi-0/infrastructure-cpy/bin/python', '-m', 'pip', 
'install', 'setuptools', 'wheel', ...],)
kwargs = {}, retcode = 1
cmd = ['/tmp/ffi-0/infrastructure-cpy/bin/python', '-m', 'pip', 'install', 
'setuptools', 'wheel', ...]

def check_call(*popenargs, **kwargs):
"""Run command with arguments.  Wait for command to complete.  If
the exit code was zero then return, otherwise raise
CalledProcessError.  The CalledProcessError object will have the
return code in the returncode attribute.

The arguments are the same as for the call function.  Example:

check_call(["ls", "-l"])

"""
retcode = call(*popenargs, **kwargs)
if retcode:
cmd = kwargs.get("args")
if cmd is None:
cmd = popenargs[0]

  raise CalledProcessError(retcode, cmd)

E   subprocess.CalledProcessError: Command 
'['/tmp/ffi-0/infrastructure-cpy/bin/python', '-m', 'pip', 'install', 
'setuptools', 'wheel', '--upgrade']' returned non-zero exit status 1.

/usr/lib/python3.12/subprocess.py:413: CalledProcessError
- Captured stdout call -
created virtual environment CPython3.12.0.final.0-64 in 186ms
  creator CPython3Posix(dest=/tmp/ffi-0/infrastructure-cpy, clear=False, 
no_vcs_ignore=False, global=False)
  seeder FromAppData(download=False, pip=bundle, via=copy, 
app_data_dir=/<>/debian/.debhelper/generated/_source/home/.local/share/virtualenv)
added seed packages: pip==23.3
  activators 
BashActivator,CShellActivator,FishActivator,NushellActivator,PowerShellActivator,PythonActivator
- Captured stderr call -
WARNING: Retrying (Retry(total=4, connect=None, read=None, redirect=None, 
status=None)) after connection broken by 'ProxyError('Cannot connect to proxy.', 
NewConnectionError(': Failed to establish a new connection: [Errno 111] Connection 
refused'))': /simple/setuptools/
WARNING: Retrying (Retry(total=3, connect=None, read=None, redirect=None, 
status=None)) after connection broken by 'ProxyError('Cannot connect to proxy.', 
NewConnectionError(': Failed to establish a new connection: [Errno 111] Connection 
refused'))': /simple/setuptools/
WARNING: Retrying (Retry(total=2, connect=None, read=None, redirect=None, 
status=None)) after connection broken by 'ProxyError('Cannot connect to proxy.', 
NewConnectionError(': Failed to establish a new connection: [Errno 111] Connection 
refused'))': /simple/setuptools/
WARNING: Retrying (Retry(total=1, connect=None, read=None, redirect=None, 
status=None)) after connection broken by 'ProxyError('Cannot connect to proxy.', 
NewConnectionError(': Failed to establish a new connection: [Errno 111] Connection 
refused'))': /simple/setuptools/
WARNING: Retrying (Retry(total=0, connect=None, read=None, redirect=None, 
status=None)) after connection broken by 'ProxyError('Cannot connect to proxy.', 
NewConnectionError(': Failed to establish a new connection: [Errno 111] Connection 
refused'))': /simple/setuptools/
ERROR: Could not find a version that satisfies the requirement setuptools (from 
versions: none)
ERROR: No matching distribution found for setuptools
 TestZIntegration.test_distutils_module 

self = 

def test_distutils_module(self):

  run_setup_and_program("distutils_module", '''

import snip_basic_verify
p = snip_basic_verify.C.getpwuid(0)
assert snip_basic_verify.ffi.string(p.pw_name) == b"root"
''')

testing/cffi0/test_zintegration.py:134:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
testing/cffi0/test_zintegration.py:107: in run_setup_and_program
venv_dir = create_venv(dirname + '-cpy')
testing/cffi0/test_zintegration.py:29: in create_venv
subprocess.check_call([
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 

Bug#1055336: pycxx: update needed for Python 3.12

[Matthias Klose]

Source: pycxx
Version: 7.1.7-2
Severity: important
User: debian-pyt...@lists.debian.org
Usertags: python3.12

pycxx needs the new upstream 7.1.8 to support Python 3.12

Bug#1055032: Please update to latest upstream version

[Antonio Terceiro]

On Fri, Nov 03, 2023 at 09:07:49PM -0300, Antonio Terceiro wrote:
> On Sun, Oct 29, 2023 at 09:29:04PM +0200, Jonathan Carter wrote:
> > Package: python3-textual
> > Severity: normal
> > X-Debbugs-Cc: 
> > 
> > Dear maintainer,
> > 
> > The current version of python3-textual in Debian is quite out of date,
> > and it's not possible to run newer textual apps with it anymore.,
> > Please upgrade to the latest upstream version (currenly (0.40.0) so
> > that this package can be useful again.
> 
> I have a textual locally updated to the latest upstream version:
> https://salsa.debian.org/terceiro/textual
> 
> I had to disable a few tests due to either missing dependencies, of
> mismatching expectations between the versions in Debian and the ones
> assumed by upstream (poetry.lock). There is still some work to do, e.g.
> converting the autopkgtest to use autopkgtest-pkg-pybuild.

This is now done.

BTW there is a new build dependency, python3-time-machine, which is in
NEW right now:

https://salsa.debian.org/python-team/packages/python-time-machine


signature.asc
Description: PGP signature

Bug#1005644: Intent to NMU pillow (Re: Bug#1005644: python3-pil: should depend on "media-types | mime-support")

[Charles Plessy]

Le Wed, Oct 25, 2023 at 10:23:44PM +0900, Charles Plessy a écrit :
> 
> I intend to NMU pillow to DELAYED/15 soon, unless you plan to remove the
> dependency on mime-support by yourself in a reasonable delay.

Hello Matthias,

I uploaded to DELAYED/15 on the 29th.  Here is the debdiff.

$ debdiff pillow_10.0.0-1.dsc pillow_10.0.0-1.1.dsc
diff -Nru pillow-10.0.0/debian/changelog pillow-10.0.0/debian/changelog
--- pillow-10.0.0/debian/changelog  2023-07-06 01:58:54.0 +0900
+++ pillow-10.0.0/debian/changelog  2023-10-29 08:05:25.0 +0900
@@ -1,3 +1,11 @@
+pillow (10.0.0-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Depend on media-types instead of mime-support.
+Closes:#987500, #1003934, #1005644
+
+ -- Charles Plessy   Sun, 29 Oct 2023 08:05:25 +0900
+
 pillow (10.0.0-1) unstable; urgency=medium

   * New upstream version.
diff -Nru pillow-10.0.0/debian/control pillow-10.0.0/debian/control
--- pillow-10.0.0/debian/control2023-06-12 16:30:52.0 +0900
+++ pillow-10.0.0/debian/control2023-10-29 08:04:20.0 +0900
@@ -23,7 +23,7 @@
 Package: python3-pil
 Architecture: any
 Multi-Arch: same
-Depends: ${python3:Depends}, mime-support | python3-pil.imagetk,
+Depends: ${python3:Depends}, media-types | python3-pil.imagetk,
   ${shlibs:Depends}, ${misc:Depends}
 Recommends: python3-olefile
 Suggests: python-pil-doc

Best regard,

Charles

-- 
Charles Plessy Nagahama, Yomitan, Okinawa, Japan
Debian Med packaging team http://www.debian.org/devel/debian-med
Tooting from work,   https://fediscience.org/@charles_plessy
Tooting from home, https://framapiaf.org/@charles_plessy

Bug#1055335: gimp: Program crashes with fatal error

[Iris]

Package: gimp
Version: 2.10.34-1
Severity: normal
X-Debbugs-Cc: ddarko...@yahoo.com


```
GNU Image Manipulation Program version 2.10.34
git-describe: GIMP_2_10_34
Build: unknown rev 0 for linux
# C compiler #
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/12/lto-wrapper
OFFLOAD_TARGET_NAMES=nvptx-none:amdgcn-amdhsa
OFFLOAD_TARGET_DEFAULT=1
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Debian
12.2.0-14' --with-bugurl=file:///usr/share/doc/gcc-12/README.Bugs --enable-
languages=c,ada,c++,go,d,fortran,objc,obj-c++,m2 --prefix=/usr --with-gcc-
major-version-only --program-suffix=-12 --program-prefix=x86_64-linux-gnu-
--enable-shared --enable-linker-build-id --libexecdir=/usr/lib --without-
included-gettext --enable-threads=posix --libdir=/usr/lib --enable-nls
--enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes
--with-default-libstdcxx-abi=new --enable-gnu-unique-object --disable-vtable-
verify --enable-plugin --enable-default-pie --with-system-zlib --enable-
libphobos-checking=release --with-target-system-zlib=auto --enable-objc-gc=auto
--enable-multiarch --disable-werror --enable-cet --with-arch-32=i686 --with-
abi=m64 --with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic
--enable-offload-targets=nvptx-
none=/build/gcc-12-bTRWOB/gcc-12-12.2.0/debian/tmp-nvptx/usr,amdgcn-
amdhsa=/build/gcc-12-bTRWOB/gcc-12-12.2.0/debian/tmp-gcn/usr --enable-offload-
defaulted --without-cuda-driver --enable-checking=release --build=x86_64-linux-
gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu
Thread model: posix
Supported LTO compression algorithms: zlib zstd
gcc version 12.2.0 (Debian 12.2.0-14)

# Libraries #
using babl version 0.1.106 (compiled against version 0.1.98)
using GEGL version 0.4.46 (compiled against version 0.4.42)
using GLib version 2.78.1 (compiled against version 2.74.5)
using GdkPixbuf version 2.42.10 (compiled against version 2.42.10)
using GTK+ version 2.24.33 (compiled against version 2.24.33)
using Pango version 1.51.0 (compiled against version 1.50.12)
using Fontconfig version 2.14.2 (compiled against version 2.14.1)
using Cairo version 1.18.0 (compiled against version 1.16.0)

```
> fatal error: Abgebrochen

Stack trace:
```

# Stack traces obtained from PID 24466 - Thread 24466 #

[New LWP 24468]
[New LWP 24469]
[New LWP 24470]
[New LWP 24471]
[New LWP 24472]
[New LWP 24514]
[New LWP 24520]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
__GI___libc_read (nbytes=256, buf=0x7fffbe378fb0, fd=17) at
../sysdeps/unix/sysv/linux/read.c:26
  Id   Target IdFrame
* 1Thread 0x7f828177b300 (LWP 24466) "gimp-2.10"__GI___libc_read
(nbytes=256, buf=0x7fffbe378fb0, fd=17) at ../sysdeps/unix/sysv/linux/read.c:26
  2Thread 0x7f82811c06c0 (LWP 24468) "worker"   syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  3Thread 0x7f827bc3f6c0 (LWP 24469) "pool-spawner" syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  4Thread 0x7f827343e6c0 (LWP 24470) "gmain"0x7f828269ba1f in
__GI___poll (fds=0x558bc97df340, nfds=2, timeout=-1) at
../sysdeps/unix/sysv/linux/poll.c:29
  5Thread 0x7f827b43e6c0 (LWP 24471) "gdbus"0x7f828269ba1f in
__GI___poll (fds=0x7f8264000b90, nfds=3, timeout=-1) at
../sysdeps/unix/sysv/linux/poll.c:29
  6Thread 0x7f8273fff6c0 (LWP 24472) "async"syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  7Thread 0x7f82637fe6c0 (LWP 24514) "swap writer"  syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  8Thread 0x7f8263fff6c0 (LWP 24520) "paint"syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38

Thread 8 (Thread 0x7f8263fff6c0 (LWP 24520) "paint"):
#0  syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
No locals.
#1  0x7f8282916a24 in g_cond_wait () from /lib/x86_64-linux-
gnu/libglib-2.0.so.0
No symbol table info available.
#2  0x558bc8e84401 in ?? ()
No symbol table info available.
#3  0x7f82828e8a41 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#4  0x7f82826283ec in start_thread (arg=) at
./nptl/pthread_create.c:444
ret = 
pd = 
out = 
unwind_buf = {cancel_jmp_buf = {{jmp_buf = {140198509969712,
-7623860595001366847, -1144, 11, 140736384703280, 140197991804928,
7581349076618733249, 7581704331682932417}, mask_was_saved = 0}}, priv = {pad =
{0x0, 0x0, 0x0, 0x0}, data = {prev = 0x0, cleanup = 0x0, canceltype = 0}}}
not_first_call = 
#5  0x7f82826a8a4c in clone3 () at
../sysdeps/unix/sysv/linux/x86_64/clone3.S:81
No locals.

Thread 7 (Thread 0x7f82637fe6c0 (LWP 24514) "swap writer"):
#0  syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
No locals.
#1  

Bug#1052347: src:canu: fails to migrate to testing for too long: unresolved RC issue

[Nilesh Patra]

On Wed, 1 Nov 2023 19:23:13 +0100 Paul Gevers  wrote:
> Hi Andreas,
> 
> On 01-11-2023 07:34, Andreas Tille wrote:
> >... is it possible that the CI is restricting memory so when it tries
> >to allocate some it fails?
> 
> Because of lack of automatic reporting, I created this wiki some time ago:
> https://wiki.debian.org/ContinuousIntegration/WorkerSpecs
> 
> The memory for the arm64 workers isn't huge (8GB), but all i386 and some 
> of the amd64 workers have the same.

On the same threads, Michael said that he is not able to reproduce the error on 
arm64 porter box however it fails in debci.

The upstream needs the *.out files of the failing tests, as they said at [1]. 
Since it does not work on porter box, and chokes on the CI infra, could you 
please provide these files?

[1]: https://github.com/marbl/canu/issues/2271#issuecomment-1772870568

Thanks,
Nilesh