Bug#1053977: RFS: a2d/2.0.1-1 [ITP] -- APRS to DAPNET portal

[Yogeswaran Umasankar]

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package "a2d":
This package is for the new upstream version.

* Package name     : a2d
   Version          : 2.0.1-1
   Upstream contact : Yogeswaran Umasankar kd8...@gmail.com
* URL              : https://github.com/NGC2023/a2d
* License          : MIT, CC-BY-3.0
* Vcs              : https://github.com/NGC2023/a2d
   Section          : hamradio

The source builds the following binary packages:

  a2d - APRS to DAPNET portal

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


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

Initial release in the NEW queue.

Changes between this version and the initial release submitted:
a2d (2.0.1-1) unstable; urgency=medium
* New upstream version v2.0.1.
* Switched to poetry pyproject.toml from setup.py.

Regards,
--
  Yogeswaran Umasankar

Bug#1053976: elpa-eglot: eglot-server-programs doesn't provide mappings for *-ts-modes

[Xiyue Deng]

Package: elpa-eglot
Version: 1.9-2
Severity: normal
X-Debbugs-Cc: none, Xiyue Deng 

Emacs 29 includes support fro tree-sitter and the new "*-ts-mode" major
modes.  However the current eglot version doesn't work out-of-the-box
for those new tree-sitter based modes as the mappings for those new major
modes are not available yet.  This has been fixed upstream in this
commit[1], and syncing to a new upstream version should fix this.

[1] 
https://github.com/joaotavora/eglot/commit/fb8111d8222b09641a6aaab02d846ceac3ae97ed


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

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

Versions of packages elpa-eglot depends on:
ii  dh-elpa-helper  2.0.17
ii  elpa-project0.8.1-1
ii  elpa-seq2.24-1
ii  elpa-xref   1.6.3-1
ii  emacsen-common  3.0.5

elpa-eglot recommends no packages.

elpa-eglot suggests no packages.

-- no debconf information


signature.asc
Description: PGP signature

Bug#1053975: RFS: srs-server/5.0.5-2 [ITP] -- simple, high-efficiency, real-time video server

[nmgchenhaibo]

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package "srs-server":

* Package name : srs-server
 Version : 
5.0.5-2
 Upstream contact : chenhaibo https://ossrs.io
* License : 
MPL-2.0, BSD-3-clause~Cisco, MIT, LGPL-2.1+ and GPL-2+, GPL-2+
* 
Vcs
 : https://github.com/ossrs/srs
 Section : 
video

The source builds the following binary packages:

 srs-server - simple, high-efficiency, real-time video server

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

 https://mentors.debian.net/package/srs-server/

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

 dget -x 
https://mentors.debian.net/debian/pool/main/s/srs-server/srs-server_5.0.5-2.dsc

Changes for the initial release:

srs-server (5.0.5-2) unstable; urgency=medium
.
 * Initial release (Closes: #1051407)

Regards,
-- 
 chenhaibo

Bug#1053910: zfs: use zpool user properties instead of zfs user properties for scrub and trim cron scripts

[Antonio Russo]

What semantics are you thinking for handling upgrades? This does not appear
to be a new zpool "feature", so we may want to support loading such a pool
on an earlier version of our zfs packaging.  How does this sound?

 - migrate the property if it exists (but do not remove the old, root
   filesystem one)
 - use the pool-level property if there's a conflict, but throw a warning
   if there's a discrepancy between the two
 - suggest people remove the old property if they don't need backwards
   compatibility in NEWS
 - in several version, start warning if the filesystem one is still around
 - several versions after that, stop even checking for the old property

Antonio

OpenPGP_0xB01C53D5DED4A4EE.asc
Description: OpenPGP public key


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1051232: bookworm-pu: package 7zip/23.01+dfsg-3~deb12u1

[yokota]

Hello Jonathan,

> The diff you attached is unreviewable:
>  979 files changed, 40347 insertions(+), 25060 deletions(-)
> Please prepare targetted fixes for the security issues.

Upstream dose not release fix patch, but they releases new version
(23.01) source code.
I was try to extract fix patch from diff file of 22.01..23.01 source code.

Trivial autopkgtest was passed, but I don't know that this debdiff
really fixes CVE-2023-31102 and CVE-2023-40481.

Please examine attached debdiff.

diff stat:
 changelog |8
 patches/0009-CVE-2023-40481-fix.patch |  253 ++
 patches/0010-CVE-2023-31102-fix.patch |  856 ++
 patches/series|2
 4 files changed, 1119 insertions(+)

--
YOKOTA Hiroshi


7zip_22.01+dfsg-8+deb12u1.debdiff
Description: Binary data

Bug#1053974: ITP: a2d/2.0.1-1 New upstream version available v2.0.1 -- APRS to DAPNET portal

[Yogeswaran Umasankar]

Package: a2d
Version: 2.0.1-1
Severity: wishlist
Owner: Yogeswaran Umasankar 

I am packaging the new upstream version and uploading to 
https://mentors.debian.net 


* Package name     : a2d
   Version          : 2.0.1-1
   Upstream contact : Yogeswaran Umasankar 
 * URL              : https://github.com/NGC2023/a2d
 * License          : MIT, CC-BY-3.0
 * Vcs              : https://github.com/NGC2023/a2d
   Section          : hamradio
   Description: APRS to DAPNET portal

Changes between this version and the initial release submitted:
* New upstream version v2.0.1.
* Switched to poetry pyproject.toml from setup.py.

Regards,
--
  Yogeswaran Umasankar

Bug#1053973: a2d: New upstream version available v2.0.1 -- APRS to DAPNET portal.

[Yogeswaran Umasankar]

Package: a2d
Version: 2.0.1-1
Severity: wishlist
Owner: Yogeswaran Umasankar 

I am packaging the new upstream version and uploading to 
https://mentors.debian.net 


* Package name     : a2d
   Version          : 2.0.1-1
   Upstream contact : Yogeswaran Umasankar 
 * URL              : https://github.com/NGC2023/a2d
 * License          : MIT, CC-BY-3.0
 * Vcs              : https://github.com/NGC2023/a2d
   Section          : hamradio
   Description: APRS to DAPNET portal

Changes between this version and the initial release submitted:
* New upstream version v2.0.1.
* Switched to poetry pyproject.toml from setup.py.

Regards,
--
  Yogeswaran Umasankar

Bug#1053663: libraft2: Consider switching upstream to cowsql/raft

[Mathias Gibbens]

Hi Free and Laszlo,

On Sat, 2023-10-14 at 10:31 +0100, Free Ekanayaka wrote:
> As a consequence, I've renamed the libraft2 binary package to
> libraft0. Note that libraft0 already exists in bullseye, but there's
> nothing depending on it, so even in the weird case where somebody
> downloads libraft0 from sid and installs it in bullseye, nothing
> should break.

  Free, have you tested the upgrade path from a bullseye system with
libraft0 installed incrementally through to sid? Even though it's
probably a remote edge case, we should make sure the upgrade path works
smoothly. (Both with just libraft0 installed directly, as well as
indirectly by something like dqlite.)

  I've looked over the current packaging in salsa, and pushed a few
commits cleaning up the packaging a bit. I have two remaining comments:

  First, it looks like you've intending to introduce a libraft-tools
package, but it is currently empty -- do you mean to install something
for that binary package? Also, its short description is a copy of
libraft0's.

  Second, there's an existing patch in the packaging -- could that be
included in the upstream code so we can eliminate the Debian-specific
bit?

Mathias


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

Bug#1053972: Static network settings cause same IP to be assigned to all devices

[Christian Schneider]

Package: initramfs-tools
Version: 0.142

Dear Maintainers,

On a machine with multiple network interfaces (one internal and one 
external/USB), the following configuration brought up a static network 
configuration under Debian 11 (bullseye) and the machine could be 
connected to remotely via its primary (= internal) interface:

/etc/initramfs-tools/conf.d/ip:
IP="192.168.1.13::none"

After upgrading to Debian 12 (bookwork), the system could not be 
reached remotely anymore.  Apparently, the same IP and network 
configuration is now assigned to all interfaces.

Specifying a device in the configuration fixed the issue:

/etc/initramfs-tools/conf.d/ip:
IP="192.168.1.13:eno1:none"

It would be great to have the old behavior restored.

Thank you very much.

Best,
Christian

Bug#1053971: python-absl: please package v2.0 and add a d/watch file

[Alexandre Detiste]

Source: python-absl
Version: 0.15.0-2
Severity: normal
User: python3-...@packages.debian.org
Usertags: python3-six-removal

Dear Maintainer,

Please package latest version and remove python3-six
from the hardcoded dependencies.

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-1-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#1053970: python3-pylast: please upgrade to 5.2.0 and remove hardcoded python3-six dependency

[Alexandre Detiste]

Package: python3-pylast
Version: 4.1.0-2
Severity: normal
User: python3-...@packages.debian.org
Usertags: python3-six-removal

Dear Miantainer,

Please package latets version and remove python3-six
from the hardcoded dependencies.

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-1-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)

Versions of packages python3-pylast depends on:
ii  python33.11.4-5+b1
ii  python3-pkg-resources  68.1.2-2
ii  python3-six1.16.0-4

python3-pylast recommends no packages.

python3-pylast suggests no packages.

Bug#1053969: python-multipart: please package version 0.0.6

[Alexandre Detiste]

Source: python-multipart
Version: 0.0.5-3
Severity: normal
User: python3-...@packages.debian.org
Usertags: python3-six-removal

Hi,

Usage of python3-six was been removed before 0.0.6 was published:

https://github.com/andrew-d/python-multipart/pull/42

Please remove python3-six from the hardcoded build-dependencies.

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-1-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#1053968: python3-django-modeltranslation: please remove extraneous, obsolete, dependency on python3-six

[Alexandre Detiste]

Package: python3-django-modeltranslation
Version: 0.18.11-1
Severity: normal
User: python3-...@packages.debian.org
Usertags: python3-six-removal

Hi,

Usage of python3-six was been removed upstream for a while:

https://github.com/deschler/django-modeltranslation/pull/646/files


Please remove python3-six from the hardcoded dependencies.

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-1-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)

Versions of packages python3-django-modeltranslation depends on:
ii  python3 [python3-supported-min]  3.11.4-5+b1
ii  python3-django   3:3.2.21-1
ii  python3-importlib-metadata   4.12.0-1
ii  python3-six  1.16.0-4
ii  python3-typing-extensions4.7.1-2

python3-django-modeltranslation recommends no packages.

Versions of packages python3-django-modeltranslation suggests:
pn  python-django-modeltranslation-doc  

Bug#1053967: python3-traitsui: please remove extraneous, obsolete, dependency on python3-six

[Alexandre Detiste]

Package: python3-traitsui
Version: 7.2.1-2
Severity: normal
User: python3-...@packages.debian.org
Usertags: python3-six-removal

Hi,

Usage of python3-six was been dropped years ago:

https://github.com/enthought/traitsui/pull/767


Please remove python3-six from the hardcoded dependencies.

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-1-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)

Versions of packages python3-traitsui depends on:
ii  python3 3.11.4-5+b1
pn  python3-pyface  
ii  python3-six 1.16.0-4
pn  python3-traits  

python3-traitsui recommends no packages.

python3-traitsui suggests no packages.

Bug#1053966: python3-ironic-ui: please remove extraneous, obsolete, dependency on python3-six

[Alexandre Detiste]

Package: python3-ironic-ui
Version: 6.2.1-2
Severity: normal
User: python3-...@packages.debian.org
Usertags: python3-six-removal


Hi,

Usage of python3-six was been dropped years ago:
https://lists.openstack.org/pipermail/openstack-discuss/2019-October/010142.html

Please remove python3-six from the hardcoded dependencies.

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-1-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)

Versions of packages python3-ironic-ui depends on:
pn  openstack-dashboard 
ii  python3 3.11.4-5+b1
ii  python3-django  3:3.2.21-1
pn  python3-django-horizon  
pn  python3-ironicclient
ii  python3-pbr 5.11.1-3
ii  python3-six 1.16.0-4

python3-ironic-ui recommends no packages.

python3-ironic-ui suggests no packages.

Bug#1053965: libcairo2: Ugly Tahoma font rendering since version 1.17

[Zbynek Michl]

Package: libcairo2
Version: 1.16.0-7
Severity: normal
X-Debbugs-Cc: zbynek.mi...@gmail.com

Hello,

I have recently upgraded libcairo2 from 1.16.0 to 1.17.8 in my distro (Debian
Trixie). Since that rendering of Tahoma font in Xfce is broken.

Sample screenshots before and after the upgrade are attached.

I have found a similar issue reported here:
https://bugs.archlinux.org/task/64451

Thank you
Zbynek


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

Kernel: Linux 6.4.0-4-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=cs_CZ.UTF-8, LC_CTYPE=cs_CZ.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 libcairo2 depends on:
ii  libc6   2.37-7
ii  libfontconfig1  2.14.2-5
ii  libfreetype62.13.2+dfsg-1
ii  libpixman-1-0   0.42.2-1
ii  libpng16-16 1.6.40-1
ii  libx11-62:1.8.6-1
ii  libxcb-render0  1.15-1
ii  libxcb-shm0 1.15-1
ii  libxcb1 1.15-1
ii  libxext62:1.3.4-1+b1
ii  libxrender1 1:0.9.10-1.1
ii  zlib1g  1:1.2.13.dfsg-3

libcairo2 recommends no packages.

libcairo2 suggests no packages.

-- no debconf information

Bug#1053957: (no subject)

[William Desportes]

Control: reopen -1
Control: tags -1 + confirmed patch

Thank you for opening this bug.
Until now I was waiting on chromium but I have to realize my bug may be due to 
their stuff but I need to more on.
For now I managed right now to reproduce the bug on i386 using:

- docker run --rm --privileged multiarch/qemu-user-static --reset -p yes
- docker run -v $PWD:/app --workdir /app --rm i386/debian:bookworm /bin/bash

And installing all the tooling and stuff.

Then I get "selenium.common.exceptions.WebDriverException: Message: unknown error: 
session deleted because of page crash"

It seems like the crash goes away if I send the keys line by line and not all 
the text at once.
Maybe a memory issue of some type.

Works:
    for line in Simpsons.split('\n'):
    import_area.send_keys(line + "\n")

Crashes:
   import_area.send_keys(Simpsons)

To be continued :)

Bug#1053964: RFS: posixsignalmanager/0.3-4 -- posix signal handling for qt - headers

[Christoph Hueffelmann]

Package: sponsorship-requests
Severity: normal

Dear mentors,

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

 * Package name : posixsignalmanager
   Version  : 0.3-4
   Upstream contact : Martin Hostettler 
 * URL  : https://github.com/textshell/posixsignalmanager
 * License  : BSL-1.0
 * Vcs  : [fill in URL of packaging vcs]
   Section  : libs

The source builds the following binary packages:

  libposixsignalmanager0a - posix signal handling for qt - shared library
  libposixsignalmanager-dev - posix signal handling for qt - headers

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


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

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

  dget -x 
https://mentors.debian.net/debian/pool/main/p/posixsignalmanager/posixsignalmanager_0.3-4.dsc


Changes since the last upload:

 posixsignalmanager (0.3-4) unstable; urgency=medium
 .
   * Add support for catch2 version-3.x (#1053768)
   * Update patch to support riscv from upstream.

Regards,
--
  Christoph Hueffelmann

Bug#1053925: apt-listchanges: Data left after purge

[Jonathan Kamens]

Thanks, will be fixed in 4.3.

Bug#1053963: RFS: termpaint/0.3.0-3 [RC] -- low level terminal access - headers

[Christoph Hueffelmann]

Package: sponsorship-requests
Severity: important

Dear mentors,

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

 * Package name : termpaint
   Version  : 0.3.0-3
   Upstream contact : Martin Hostettler 
 * URL  : https://termpaint.namepad.de/
 * License  : bzip2-1.0.6, BSL-1.0 or Expat, BSL-1.0, 0BSD or 
BSL-1.0 or MIT-0, BSD-2-clause, BSD-3-clause

 * Vcs  : https://salsa.debian.org/debian/termpaint
   Section  : libs

The source builds the following binary packages:

  libtermpaint0a - low level terminal access - shared library
  libtermpaint-dev - low level terminal access - headers

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


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

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

  dget -x 
https://mentors.debian.net/debian/pool/main/t/termpaint/termpaint_0.3.0-3.dsc


Changes since the last upload:

 termpaint (0.3.0-3) unstable; urgency=medium
 .
   * Fix: Fails to build source after successful build (Closes: #1047032)
   * Upstream patch to fix catch2 version 3.x (Closes: #1053775)

Regards,
--
  Christoph Hueffelmann

Bug#1036167: breaks /usr/bin/flask; severity grave

[Lionel Élie Mamane]

severity 1036167 grave
thanks

This is worse than just a FTBFS; when the binary package is installed
(against versions of python3-flask-sqlalchemy now in stable, testing
or unstable), not only is flask-appbuilder completely non-functional
as far as I can determing, but even worse it breaks /usr/bin/flask
even when not using flask-appbuilder at all.

>From what I can observe, this is at least grave under:

  makes the package in question unusable or mostly so

Bug#1053962: uif: Cannot configure VLAN interfaces

[Mike Gabriel]

Package: src:uif
Version: 1.99.0-4.1
Severity: important
Tags: patch

The firewall script uif does not support VLAN interfaces as network  
interfaces.


The script bails out, because it does not like the "." in VLAN iface names.

Patch attached.


--

DAS-NETZWERKTEAM
c\o Technik- und Ökologiezentrum Eckernförde
Mike Gabriel, Marienthaler Str. 17, 24340 Eckernförde
mobile: +49 (1520) 1976 148
landline: +49 (4351) 850 8940

GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22  0782 9AF4 6B30 2577 1B31
mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de

>From d32bd9305be7217eadfffdb1c24c0f8dcdfa9e66 Mon Sep 17 00:00:00 2001
From: Mike Gabriel 
Date: Sat, 14 Oct 2023 23:54:28 +0200
Subject: [PATCH] uif.pl: Support VLAN interfaces, allow '.' in network
 interface names.

Signed-off-by: Mike Gabriel 
---
 uif.pl | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/uif.pl b/uif.pl
index 2cc72b2..d45c61e 100755
--- a/uif.pl
+++ b/uif.pl
@@ -530,7 +530,7 @@ sub validateData {
$$Interfaces{$key} = resolveHashentries($$Interfaces{$key}, 
$Interfaces);
}
foreach $key (keys (%$Interfaces)) {
-   if (!($$Interfaces{$key} =~ /^[a-zA-Z0-9+ ]+(:\d+)?$/)) {
+   if (!($$Interfaces{$key} =~ /^[\.a-zA-Z0-9+ ]+(:\d+)?$/)) {
die "invalid character in interface definition: 
$$Interfaces{$key}\n";
}
}
-- 
2.39.2



pgp3DfYWcPICu.pgp
Description: Digitale PGP-Signatur

Bug#1053961: O: ffuf -- Fast web fuzzer written in Go (program)

[Pedro Loami Barbosa dos Santos]

Package: wnpp
Severity: normal
X-Debbugs-Cc: f...@packages.debian.org, pe...@loami.eng.br
Control: affects -1 + src:ffuf

I am hereby orphaning ffuf. I'm no longer able to maintain this package. 
It's currently considerabliy outdated. I wish all the best to the next 
maintainer. 

The package description is:
 ffuf is a fest web fuzzer written in Go that allows typical directory
 discovery, virtual host discovery (without DNS records) and GET and POST
 parameter fuzzing.

Bug#1053960: texlive-fonts-extra: missing Breaks+Replaces: texlive-fonts-extra-links (<< 2023.20231007)

[Andreas Beckmann]

Package: texlive-fonts-extra
Version: 2023.20231007-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

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

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

  Preparing to unpack .../texlive-fonts-extra_2023.20231007-1_all.deb ...
  Unpacking texlive-fonts-extra (2023.20231007-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/texlive-fonts-extra_2023.20231007-1_all.deb (--unpack):
   trying to overwrite 
'/usr/share/texlive/texmf-dist/fonts/opentype/huerta/alegreya/AlegreyaSans-Black.otf',
 which is also in package texlive-fonts-extra-links 2023.20230613-2
  Errors were encountered while processing:
   /var/cache/apt/archives/texlive-fonts-extra_2023.20231007-1_all.deb


cheers,

Andreas


texlive-fonts-extra-links=2023.20230613-2_texlive-fonts-extra=2023.20231007-1.log.gz
Description: application/gzip

Bug#967266: Update to v1.1.0

[Bastian Germann]

I am going to upload baresip 1.1.0 built against gtk3 to experimental.

Bug#1053898: Hardening rsyslog.service breaks debian/tests/logcheck autopkgtest

[Richard Lewis]

On Fri, 13 Oct 2023 at 20:27, Michael Biebl  wrote:

> It turns out that `PrivateTmp=yes` breaks the logcheck autopkgtest.

i think the test tells rsyslog to write to /tmp and then calls
logcheck on the output outside the unit. But the PrivateTmp=true means
rsyslog is actually writing to [somewhere else] bind-mounted over
/tmp. It should be easy to fix by making the test use /var/log instead
of /tmp - will check and send a MR

Bug#1053959: grub-common: Upgrade from bookworm results in kernel packages configuration errors

[Алексей Шилин]

Package: grub-common
Version: 2.12~rc1-11

Hi,

Upgrading from bookworm to sid currently results in the following
message at the end:

   Errors were encountered while processing:
   linux-image-6.5.0-1-amd64
   linux-image-amd64
   
After looking through apt (term.log) and dpkg (dpkg.log) log files
(both are attached), it seems that it's caused by grub-common.

Here are the relevant parts from term.log:

   Preparing to unpack .../085-grub-common_2.12~rc1-11_amd64.deb ...
   Unpacking grub-common (2.12~rc1-11) over (2.06-13+deb12u1) ...
   
   [ skip ]
   
   Setting up linux-image-6.5.0-1-amd64 (6.5.3-1) ...
   I: /vmlinuz.old is now a symlink to boot/vmlinuz-6.1.0-13-amd64
   I: /initrd.img.old is now a symlink to boot/initrd.img-6.1.0-13-
   amd64
   I: /vmlinuz is now a symlink to boot/vmlinuz-6.5.0-1-amd64
   I: /initrd.img is now a symlink to boot/initrd.img-6.5.0-1-amd64
   /etc/kernel/postinst.d/initramfs-tools:
   update-initramfs: Generating /boot/initrd.img-6.5.0-1-amd64
   /etc/kernel/postinst.d/zz-update-grub:
   Generating grub configuration file ...
   /etc/grub.d/10_linux: 1: version_find_latest: not found
   run-parts: /etc/kernel/postinst.d/zz-update-grub exited with return
   code 127
   dpkg: error processing package linux-image-6.5.0-1-amd64 (--
   configure):
   installed linux-image-6.5.0-1-amd64 package post-installation script
   subprocess returned error exit status 1
   
   [ skip ]
   
   Setting up grub-common (2.12~rc1-11) ...
   Installing new version of config file /etc/grub.d/00_header ...
   Installing new version of config file /etc/grub.d/10_linux ...
   Installing new version of config file /etc/grub.d/20_linux_xen ...
   Installing new version of config file /etc/grub.d/30_os-prober ...
   Installing new version of config file /etc/grub.d/30_uefi-firmware
   ...
   
So here's what's happening:
 * /etc/grub.d/10_linux in bookworm is using `version_find_latest`
   shell function defined in /usr/share/grub/grub-mkconfig_lib.
 * That function no longer exists in grub-mkconfig_lib in sid.
 * /etc/grub.d/10_linux is marked as configuration file in the package
   while /usr/share/grub/grub-mkconfig_lib is not.
 * During the upgrade, the following sequence occurs:
  1. New grub-common is unpacked. As the result, /usr/share/grub/grub-
 mkconfig_lib is now the new version which doesn't have
 `version_find_latest` function defined, but /etc/grub.d/10_linux
 is still the old version since it's a configuration file.
  2. linux-image-6.5.0-1-amd64 is unpacked.
  3. linux-image-6.5.0-1-amd64 is configured. As the result, scripts
 under /etc/kernel/postinst.d are executed which in turn run
 `update-grub`.
  4. `update-grub` tries to run /etc/grub.d/10_linux (which is still
 the old version as grub-common is not configured yet), which
 fails due to being unable to find `version_find_latest` in new
 version of grub-mkconfig_lib. As the result, the kernel package
 enters half-configured state.
  5. grub-common is finally configured, and only then new versions of
 files under /etc/grub.d are installed.
 * As the result of the above, the upgrade ends with an error leaving
   kernel packages half-configured.

So the root issue is that grub-common files which depend on each other
are installed at different times which results in a window when running
`update-grub` will fail, and kernel packages happen to be extracted and
configured during that window.

The error vanishes after re-running the upgrade command which, given
that all grub-common files are now in place, finishes successfully,
hence the "normal" severity. Still a bug though.

-- 
Алексей Шилин 


dpkg.log.xz
Description: application/xz


term.log.xz
Description: application/xz

Bug#1053958: src:python-django-storages: fails to migrate to testing for too long: uploader built arch:all

[Paul Gevers]

Source: python-django-storages
Version: 1.13.2-1
Severity: serious
Control: close -1 1.14-1
Tags: sid trixie pending
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing 
and unstable for more than 30 days as having a Release Critical bug in 
testing [1]. Your package src:python-django-storages has been trying to 
migrate for 31 days [2]. Hence, I am filing this bug.


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


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


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


Your package is only blocked because the arch:all binary package(s) 
aren't built on a buildd. Unfortunately the Debian infrastructure 
doesn't allow arch:all packages to be properly binNMU'ed. Hence, I will 
shortly do a no-changes source-only upload to DELAYED/15, closing this 
bug. Please let me know if I should delay or cancel that upload.


Paul

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



OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1053957: src:phpldapadmin: fails to migrate to testing for too long: autopkgtest failure on armhf and i386

[Paul Gevers]

Source: phpldapadmin
Version: 1.2.6.3-0.3
Severity: serious
Control: close -1 1.2.6.6-1
Tags: sid trixie
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing 
and unstable for more than 30 days as having a Release Critical bug in 
testing [1]. Your package src:phpldapadmin has been trying to migrate 
for 31 days [2]. Hence, I am filing this bug. The version in unstable 
gained an autopkgtest (thanks for that) but it fails on armhf and on i386.


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


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


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


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


Paul

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



OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#967569: libcanberra: depends on deprecated GTK 2

[Bastian Germann]

Control: tags -1 patch

I have attached a patch to fix this.From 4d524a485be12f1fe4a6b7a4e612fd615c438b2e Mon Sep 17 00:00:00 2001
From: Bastian Germann 
Date: Sat, 14 Oct 2023 21:44:04 +0200
Subject: [PATCH] Drop gtk2 support (Closes: #967569)

---
 debian/control| 45 +--
 debian/control.in | 45 +--
 debian/libcanberra-gtk-dev.install|  2 --
 debian/libcanberra-gtk-module.install |  2 --
 debian/libcanberra-gtk-module.preinst | 15 -
 debian/libcanberra-gtk0.install   |  1 -
 debian/libcanberra-gtk0.symbols   |  9 --
 debian/rules  |  3 +-
 8 files changed, 3 insertions(+), 119 deletions(-)
 delete mode 100644 debian/libcanberra-gtk-dev.install
 delete mode 100644 debian/libcanberra-gtk-module.install
 delete mode 100644 debian/libcanberra-gtk-module.preinst
 delete mode 100644 debian/libcanberra-gtk0.install
 delete mode 100644 debian/libcanberra-gtk0.symbols

diff --git a/debian/control b/debian/control
index e37aab5..c4119ea 100644
--- a/debian/control
+++ b/debian/control
@@ -13,7 +13,6 @@ Build-Depends: debhelper-compat (= 13),
libasound2-dev [linux-any],
libvorbis-dev,
libgtk-3-dev (>= 3.0.0),
-   libgtk2.0-dev (>= 2.22),
libtdb-dev (>> 1.1) [!hurd-any],
gtk-doc-tools,
libpulse-dev (>= 0.9.11),
@@ -28,7 +27,7 @@ Package: libcanberra0
 Architecture: any
 Multi-Arch: same
 Depends: ${shlibs:Depends}, ${misc:Depends}, sound-theme-freedesktop
-Suggests: libcanberra-gtk0, libcanberra-pulse
+Suggests: libcanberra-pulse
 Description: simple abstract interface for playing event sounds
  libcanberra defines a simple abstract interface for playing event
  sounds.
@@ -77,19 +76,6 @@ Description: GStreamer backend for libcanberra
  .
  This package contains the GStreamer backend for libcanberra.
 
-Package: libcanberra-gtk0
-Architecture: any
-Multi-Arch: same
-Depends: ${shlibs:Depends}, ${misc:Depends}
-Recommends: libcanberra-gtk-module
-Description: GTK+ helper for playing widget event sounds with libcanberra
- libcanberra-gtk provides a few functions that simplify libcanberra
- usage from GTK+.
- .
- Contextual information is needed to play event sound. This library
- can help to compile directly event sounds property lists based on
- active GtkWidget objects or GdkEvent events.
-
 Package: libcanberra-gtk-common-dev
 Section: libdevel
 Architecture: all
@@ -108,35 +94,6 @@ Description: simple interface for playing event sounds (GTK+ shared development
  This package contains common headers for developing
  applications using libcanberra-gtk and libcanberra-gtk3
 
-Package: libcanberra-gtk-dev
-Section: libdevel
-Architecture: any
-Multi-Arch: same
-Depends: ${shlibs:Depends},
-   ${misc:Depends},
-   libcanberra-gtk0 (= ${binary:Version}),
-   libcanberra-dev (= ${binary:Version}),
-   libgtk2.0-dev (>= 2.20),
-   libcanberra-gtk-common-dev
-Description: simple interface for playing event sounds (GTK+ 2 development files)
- libcanberra-gtk provides a few functions that simplify
- libcanberra usage from GTK+.
- .
- Contextual information is needed to play event sound. This library
- can help to compile directly event sounds property lists based on
- active GtkWidget objects or GdkEvent events.
- .
- This package contains headers and libraries for developing
- applications that play event sounds with libcanberra-gtk.
-
-Package: libcanberra-gtk-module
-Architecture: any
-Multi-Arch: same
-Depends: ${shlibs:Depends}, ${misc:Depends}, libgtk2.0-0 (>= 2.24.5-4)
-Description: translates GTK+ widgets signals to event sounds
- A GtkModule which will automatically hook into all kinds of events
- inside a GTK+ program and generate sound events from them.
-
 Package: libcanberra-gtk3-0
 Architecture: any
 Multi-Arch: same
diff --git a/debian/control.in b/debian/control.in
index f14902c..c69ba60 100644
--- a/debian/control.in
+++ b/debian/control.in
@@ -9,7 +9,6 @@ Build-Depends: debhelper-compat (= 13),
libasound2-dev [linux-any],
libvorbis-dev,
libgtk-3-dev (>= 3.0.0),
-   libgtk2.0-dev (>= 2.22),
libtdb-dev (>> 1.1) [!hurd-any],
gtk-doc-tools,
libpulse-dev (>= 0.9.11),
@@ -24,7 +23,7 @@ Package: libcanberra0
 Architecture: any
 Multi-Arch: same
 Depends: ${shlibs:Depends}, ${misc:Depends}, sound-theme-freedesktop
-Suggests: libcanberra-gtk0, libcanberra-pulse
+Suggests: libcanberra-pulse
 Description: simple abstract interface for playing event sounds
  libcanberra defines a simple abstract interface for playing event
  sounds.
@@ -73,19 +72,6 @@ Description: GStreamer backend for libcanberra
  .
  This package contains the GStreamer backend for libcanberra.
 
-Package: libcanberra-gtk0
-Architecture: any
-Multi-Arch: same
-Depends: ${shlibs:Depends}, 

Bug#1053956: src:alsa-lib: fails to migrate to testing for too long: unresolved RC bugs

[Paul Gevers]

Source: alsa-lib
Version: 1.2.9-2
Severity: serious
Control: close -1 1.2.10-1
Tags: sid trixie
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 1052720
Control: block -1 by 1051901

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing 
and unstable for more than 30 days as having a Release Critical bug in 
testing [1]. Your package src:alsa-lib has been trying to migrate for 31 
days [2]. Hence, I am filing this bug. The version in unstable has 
unresolved RC bugs.


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


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


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


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


Paul

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



OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1033060: BTS #1036959 rasdaemon: invalid Maintainer field

[Taihsiang Ho (tai271828)]

Hi Russel, Mattia,

I think we can close this ticket if Russel is happy with his DDPO page
now. Mine looks good.

For the record:
The release team "fixed" the bug by using one name for field
Maintainer and the other name for Uploaders. See
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1036959 . Thank you
Russel, Mattia and Cyril for reporting/fixing the issue.

Kind regards,
Tai

Bug#967443: gnubg: depends on deprecated GTK 2

[Russ Allbery]

Bastian Germann  writes:

> I am uploading a NMU to DELAYED/10 in order to fix this.  The gtk3
> version uses a different OpenGL binding, so you might want to try to
> reenable it.

Upstream specifically says that the Gtk-3 support is buggy, does not work,
and should not be used.  How thoroughly did you test it?

-- 
Russ Allbery (r...@debian.org)  

Bug#1053955: rust-toml: please update to v0.7.8

[Jonas Smedegaard]

Source: rust-toml
Version: 0.7.6-1
Severity: normal
Tags: upstream

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Please update to (at least) newer upstream release v0.7.8.
-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmUq7pAACgkQLHwxRsGg
ASHnJA//cx9HiQ4IlI+FTTSwflG5yA+rME94OLZps1zrsep/s6VCZwlVB++jeYXv
QwmkLkO96aVG4OjT2EnGu4ecfpMygvQX1XGlIPxb0XahqfbihmHLHblEA0Mkzl/z
CtmknWGXzMUAP5DxcV2sP6vuEZZ3Dv6XmCd9lz5Ol4T+pmNvToxD1zLShckJIAxq
arN6drzGIzPeX0+4LPiKoWZSZKANAK5+hdjbNc9zvwn37d0BAux2Fur5jvMNrGYk
u1dGVcnyXndWz6NQp7Msvmgy8HiQp9TdXpu1UxN16wXGnVV2fKV/Lpw2FDtDjLPJ
z/dRCxk7TyDCexAPuWaxaXGE0Rlsu1bLzrmVKPo/v9bqoHpRkUQJjsgWwLawOwVO
D/OrJL3WrgLw5560IXVtWhvxE2iiAYs9v9q/5MqLnTsw4LG8mIJAJ1QiUb+l8p1e
xs+6CCVUS5YJ1dMBwUptpddQJHDMc3OBbpcLB0fp2hzUBCEnehGiXo0Rfw9ITa8+
9N40Lk7oXY0Xszt2B1Fer2+qYyaPqbnl50ItJq0FYZHcmWLvjEUUG0ZHBkKZRa43
0uABFMODPQ3Dduj7GJY6A5msd8mQ9N8EHSgugz8Y6cslRnaQ/t1jycmton3SoDJN
BIQe0jCPqo6iFb30DlHW3ETcLWJSJJkegfFPeY/9L8/daRHACeg=
=HRrJ
-END PGP SIGNATURE-

Bug#709275: [libmsv-java] Update to latest version

[Petter Reinholdtsen]

[Petter Reinholdtsen]
> I suspect a new enough maven version is available now.

I tried fetching the new version using uscan, and importing it using
gbp import-orig.  Two of the three patches did no longer apply, and the
last one needed to be unfuzzied.  Sadly the new version did not build,
and I am unable to figure out why.Happy
-- 
Happy hacking
Petter Reinholdtsen

Bug#1053953: rust-indexmap: please upgrade to v2

[Jonas Smedegaard]

Source: rust-indexmap
Version: 1.9.2-1
Severity: normal
Tags: upstream

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Please upgrade to (or seperately provide) newer upstream branch v2.
-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmUq7HwACgkQLHwxRsGg
ASEQ1Q//X+iHqlwtnxgfeja0ARd2dOwlX5PfYmTLlwsjqBmSYcEZXhwCvXyg6vbi
JzIwEly+FMC7LSfanqexB3fi9UdqYy+FBlI45IcsAk1hlDxdicTWVODZZhyLYX1m
lOOeUprTKyk9TfPRPvJBSBVue1LXkfP/Dh3WmKsiOxCIZ0nmVpEUGha/Tr2JYf7u
yhn2qtXRPcPZSupEgk/fkcfgtb1SqtuV6VHQ+mXAsBGF57Jl0VTbwjLAMSQAw24f
GRM1jKLfzKf4iE/QzJ5FtfhdIwbwBSEOliJw4jqMzbsRFgk1zo88ZDOYnRfbJ6KK
r5zk3cByiAq458R1G8ee9yI6TM9emfskH+Ut5shXoaqlYNvWT8iQxwMJm0+Zg5+C
eVO+ZRRrf280BHYEKI4dNnBgtFvnMz+8M/SHAel9ZIeseDD0vXZvlnrCKHOAO2Wh
f4Zkk6FobQcreMHiDxVCr+50c8utwTr8MNcuL+Q7DyOr4f4J5QXE8jIpwzuaN2pk
Fyqqy18cqiaMIFMdnC93SwYprImIG6cWTG/cKArx0TolXRV4S4A1G0TAvsadR5nu
oboSkTwBKGB6mhYgTrxAH335WfphdqKfstYE9r2Q/c/JKMM0HWAe8MnFzHf8uRTT
8VmhqJOQ6folQCKPvuir+ZmBuD6FOidhtcTDb5+z39dneD2o+yI=
=H1Zl
-END PGP SIGNATURE-

Bug#1053954: rust-anyhow: please update to v1.0.75

[Jonas Smedegaard]

Source: rust-anyhow
Version: 1.0.72-1
Severity: normal
Tags: upstream

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

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

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmUq7LsACgkQLHwxRsGg
ASFoHQ/9Fprf8Qe3uItqp2xyrG4UZ48NOVWL66q1nnKUd3jIF6/nLaiM3VDWxRIf
qAJYp/g7DXwgQSvjf7m0xdKT1DdFtYB+pg+23RqbRclWloqzC5obzkZ5WqI2njN3
3E6Poo0XQexOMJbiCRGk45DaJu8FwlBjogw0LKBiazKuY5a1xtjcuYJ5XbruQ+KE
QIOH8t9ufTebbgni34oHClvY0OMhJjWzyChlS9+9QZ5BShMpCqj6UeTH2lDesTqR
dvCrxkVaEHK8dwkqyxfNxvZ+wORa5ZUhL/qtc3ZwTr0xLJjx1/hteGbNw89bBY/i
SuZN7+iiLkWB7YhFplc2pUoocpYpVtZQfzcRCx8I9kyQzCdTt1X8FKvhsq1oMjQ/
t8FsNhS1RQ3gBL0cFs6xH6rdb7tBkzT3EJ+SFpYsptq4Lh0cm95ylX6KQsJgPSgw
4o5niRBSqikY0BrRi26PrlN4tQ14qbnam4TVaNfT0z+k8WEsDNXhzL9sVcfqChZy
bMUmndnwnt7MCtrzpLwKY6MmKkQQ0Qui5Nb190kJtFIilBwxt2DexXsAT3jIahuv
yBYpgvMsQR/bJ43IE5cK1oBdZmaNaWfso5aGSKg4sPxlpgoNmIsCu/t0j33tol2I
0WTGlioF/Go4ynolkPeG//8l9t0y+088KjrXz4mM27dONGLuZ+U=
=r7PR
-END PGP SIGNATURE-

Bug#1053952: rust-thiserror: please update to v1.0.48

[Jonas Smedegaard]

Source: rust-thiserror
Version: 1.0.38-1
Severity: normal
Tags: upstream

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

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

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmUq7DAACgkQLHwxRsGg
ASEdbg//T+OMM0ITM0dMACVgCH3uA49QhAAuUq2Aza9XJCogVdr3OXbKBVheNteY
Q36Gm1esdMju/qHkmkJo8LdN8zaK/O6+A9rgIb4d88VHeCUGd/hm9/FqiRwNqSYz
hrAob66TGS1exx+1A/dWfQCPJAl5XsfJN1yw679OIxA1BrRSIeld9Uw4LJE+TpP/
NoKJaIGG0jpwMt1ZtTS7/pWt2OAcWiCRTo5kEq3HPuyMAOgSDhZ6m08Za9iNfGpD
u4QQk2HN2AwZ6JK/KjZy6Olpq959akrdRK/H3dFiX8KoO4ra1KkKmpGxQbPhUR1W
KbPaabPZnBQ+OXd4pBQPwbnKvedYXoS4/G1XmgyOuQiDnRoVBr/bhOKh1QsH8pxQ
nRHBMHVaq1ByyS5zqW2UClKUprn38kicDA4y+H9n5U3ZRKFrMxdF6Xcl/cs3p47Y
iXquGd8Ya1rVTjbdvvBZ1NJhiJc41sdLvDOl1ta5UosCCF3bVq29sk2Uh4ssIveX
3V+KBNh5BFFw+/hS4gUadHBtQWiDx/qcGGOShdzsUfn+06C79z+VcGNv+0wPsIjg
rpapHBktL9x2oVHrZMTRyYqcPg84MPXR88Msv/ynkB05BxhwlG6uE5bsPC3RBzN1
Ol0W716WbUIOwqBcQmg1Ju0VkaBSvb/TTT3U9zSrZhmBXFzPnX0=
=/wZQ
-END PGP SIGNATURE-

Bug#1053951: rust-serde: please update to v1.0.188

[Jonas Smedegaard]

Source: rust-serde
Version: 1.0.171-1
Severity: normal
Tags: upstream

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Please up0date to (at least) newer upstream release v1.0.188.
-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmUq6+EACgkQLHwxRsGg
ASFiiBAAkdPIqhE9xN/ixynjD54VB5ZNyx1HQ79PZwxOsA9JeiTJ6TbJuiORqGTK
QoC2yq3IBvedmQjKWM9V1ioUfH4i4/6RGBV0INBvItkJf5WA0wlhB9PW4wBGSY07
E5t+5PtitD0Nh2ZqlzV4Qvy+V/kOgmD/0FRmFLF1xUQAkOfq7jmB6vbD0VKcAg2c
nx9uHjyH2DTyO6Qh+Wkw2MFfXk8DATYCSGn5tBA/9sGdthlafjWdFvp4FniqRDEs
3crnlWy6YqXL98BGMDFRUGTxkAm/mOKOlqSetGTHqZ6t3K55WJ+K0yGFFLzOiGF+
Fr8lIvepXOzwQyWBMXZpKVewN/sXY2uHW5AZP9eL6Eyx5oFq0P7fDdQmCwKcpd2b
prEoUzViRQuEwZQBeWV0jkdQP62iq1XMwftG9N0Z0alO5VEmBBLdGskCIS6/hAxS
5TfPIU4TePnPAE3w+8yB9MEKsIZ+94Iti/Qm2vkKD6Pz480tVlxEAb3T7h99io52
HhuKfg0uq2oYtL56OnLdVMzMcS57LRbH0oxOeKGsqyWJEjbPYrdqJ2tZyEIpljwo
LvBid5WsKKMWdfSH0k8XEpPHBaUsai/Z1pUxmyvyhXGJ1Su5RRk5PEyUbS0b2RBh
sCx0ZFsGM+80GyaVTqhaW15gT4YoZ3XUjsCuSMzgQKEyXgXiCWw=
=7sVe
-END PGP SIGNATURE-

Bug#967443: gnubg: depends on deprecated GTK 2

[Bastian Germann]

I am uploading a NMU to DELAYED/10 in order to fix this.
The gtk3 version uses a different OpenGL binding, so you might want to try to 
reenable it.diff -Nru gnubg-1.07.001/debian/changelog gnubg-1.07.001/debian/changelog
--- gnubg-1.07.001/debian/changelog 2023-08-05 18:38:39.0 +0200
+++ gnubg-1.07.001/debian/changelog 2023-10-14 18:37:33.0 +0200
@@ -1,3 +1,10 @@
+gnubg (1.07.001-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Build with GTK 3.  (Closes: #1036381, #967443)
+
+ -- Bastian Germann   Sat, 14 Oct 2023 18:37:33 +0200
+
 gnubg (1.07.001-2) unstable; urgency=medium
 
   [ Debian Janitor ]
diff -Nru gnubg-1.07.001/debian/control gnubg-1.07.001/debian/control
--- gnubg-1.07.001/debian/control   2023-08-05 18:38:39.0 +0200
+++ gnubg-1.07.001/debian/control   2023-10-14 18:35:17.0 +0200
@@ -9,13 +9,12 @@
  flex,
  graphicsmagick,
  libcairo2-dev,
- libcanberra-gtk-dev,
+ libcanberra-gtk3-dev,
  libcurl4-openssl-dev,
  libfreetype-dev,
  libglib2.0-dev,
  libgmp-dev,
- libgtk2.0-dev,
- libgtkglext1-dev,
+ libgtk-3-dev,
  libncurses-dev,
  libpng-dev,
  libreadline-dev,
diff -Nru gnubg-1.07.001/debian/rules gnubg-1.07.001/debian/rules
--- gnubg-1.07.001/debian/rules 2023-08-05 18:38:39.0 +0200
+++ gnubg-1.07.001/debian/rules 2023-10-14 18:34:38.0 +0200
@@ -44,7 +44,7 @@
 # Disable the 3D board for now, since it doesn't work with Mesa 21.x and
 # later.
 override_dh_auto_configure:
-   dh_auto_configure -- --with-gtk --without-board3d --with-sqlite \
+   dh_auto_configure -- --with-gtk3 --without-board3d --with-sqlite \
--with-python=/usr/bin/python3 --enable-threads $(SSE)
 
 # Disable building the rollout databases during an architecture-specific

Bug#1053950: openttd: Update to 13.4

[Jens Rex]

Package: openttd
Version: 13.0-2
Severity: wishlist

Dear Maintainer,

Debian packages are pretty far out of date at this point, with the 
latest version being 13.0 while 13.4 being available upstream.


Humbly requesting updated packages.

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

Kernel: Linux 6.5.0-1-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en

Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages openttd depends on:
ii  libc6   2.37-12
ii  libfluidsynth3  2.3.4-1
ii  libfontconfig1  2.14.2-6
ii  libfreetype62.13.2+dfsg-1
ii  libgcc-s1   13.2.0-4
ii  libicu7272.1-3
ii  liblzma55.4.4-0.1
ii  liblzo2-2   2.10-2
ii  libpng16-16 1.6.40-1
ii  libsdl2-2.0-0   2.28.4+dfsg-1
ii  libstdc++6  13.2.0-4
ii  openttd-data13.0-2
ii  zlib1g  1:1.2.13.dfsg-3

Versions of packages openttd recommends:
ii  openttd-opengfx  7.1-1
ii  openttd-openmsx  0.4.2-1
ii  openttd-opensfx  1.0.3-2

Versions of packages openttd suggests:
ii  timidity  2.14.0-8.1

-- no debconf information

Bug#1053949: transmission-gtk: printf() fmt string translation errors cause Transmission to crash

[pierre]

Package: transmission-gtk
Version: 3.00-2.1+deb12u1
Severity: important
Tags: upstream l10n
X-Debbugs-Cc: pierre_aussag...@yahoo.fr

Dear Maintainer,

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

   * What led up to the situation?

Launch transmission-gtk with locale set to  fr_FR.utf8

   * What was the outcome of this action?

start, then closes after a few seconds with message :

 *** invalid %N$ use detected ***
Abandon

   * What outcome did you expect instead?

Work as expected.

This is a bug for v3 that has been fixed in v4.
See : https://github.com/transmission/transmission/issues/1353

Would it be possible to fix it in Debian stable with some patch or by using v4
 ?


The workaround is to launch with :
LANG=C  transmission-gtk


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

Kernel: Linux 6.1.0-13-amd64 (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, 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 transmission-gtk depends on:
ii  libayatana-appindicator3-1  0.5.92-1
ii  libc6   2.36-9+deb12u3
ii  libcurl47.88.1-10+deb12u4
ii  libevent-2.1-7  2.1.12-stable-8
ii  libgdk-pixbuf-2.0-0 2.42.10+dfsg-1+b1
ii  libglib2.0-02.74.6-2
ii  libgtk-3-0  3.24.38-2~deb12u1
ii  libminiupnpc17  2.2.4-1+b1
ii  libnatpmp1  20150609-7.1+b2
ii  libpango-1.0-0  1.50.12+ds-1
ii  libssl3 3.0.11-1~deb12u1
ii  transmission-common 3.00-2.1+deb12u1
ii  zlib1g  1:1.2.13.dfsg-1

Versions of packages transmission-gtk recommends:
ii  xdg-utils  1.1.3-4.1

transmission-gtk suggests no packages.

-- no debconf information

Bug#1006292: bullseye-pu: package plasma-discover/5.20.5-3

[Patrick Franz]

Hi Adam,

On Sat, 14 Oct 2023 19:46:36 +0100 "Adam D. Barratt"  wrote:
[...]
> Thanks; please go ahead.

It's uploaded.


-- 
Med vänliga hälsningar

Patrick Franz

Bug#1053106: ACK

[Wouter Verhelst]

Yes please, would be great to make this happen.

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

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

Bug#1006292: bullseye-pu: package plasma-discover/5.20.5-3

[Adam D. Barratt]

On Tue, 2023-10-03 at 19:19 +0200, Patrick Franz wrote:
> Hej,
> 
> Am Montag, 2. Oktober 2023, 19:04:00 CEST schrieb Jonathan Wiltshire:
> [...]
> > Ping on this? It's urgent given the point release is planned for
> > the
> > coming weekend, and we're currently unsure if the related fix is
> > safe
> > to release without this one. If there's no answer we'll have to
> > play
> > safe and hold plasma-desktop back until the next cycle as well.
> 
> I've fixed it and it builds now. I'm attaching a debdiff to the
> version that was supposed to be uploaded.

Thanks; please go ahead.

Regards,

Adam

Bug#861781: update

[Thomas Lange]

I've removed the people not involed any more and the OVAL
organisation.

We may remove all organisations, because I'm not sure if
Debian is involved in any organisations any more.

-- 
 Thomas

Bug#1053747: [Debian-on-mobile-maintainers] Bug#1053747: Bug#1053747: Upload phosh to bookworm-backports ?

[Pirate Praveen]

On Sat, Oct 14 2023 at 18:26:58 +02:00:00, Guido Günther 
 wrote:

Hi,
On Fri, Oct 13, 2023 at 09:13:39PM +0530, Pirate Praveen via 
Debian-on-mobile-maintainers wrote:
 On Tue, 10 Oct 2023 23:56:54 +0200 Arnaud Ferraris 
mailto:aferra...@debian.org>>

 wrote:
 > Hi,
 >
 > Le 10/10/2023 à 11:03, Pirate Praveen via 
Debian-on-mobile-maintainers a

 > écrit :
 > > Package: phosh
 > > Version: 0.32.0-1
 > > Severity: wishlist
 > >
 > > I think it'd be a good idea to provide new versions of phosh 
(with phoc,
 > > wlroots, feedbackd) via bookworm-backports. I was earlier daily 
driving
 > > mobian trixie on my Librem 5 but since its automatic suspend 
broke I
 > > could not continue using it [1]. So I'm using mobian bookworm 
but I miss
 > > the newer phosh (especially easy access to suspend button, 
which I use

 > > often for power saving).
 >
 > As discussed in the Mobian issue you mention, the auto-suspend 
problem
 > you're experiencing is only happening with recent versions of 
phosh,
 > which basically reset the idle counter when a critical 
notification

 happens.
 >
 > Providing a backported version of phosh wouldn't help there, and 
the
 > solution should be provided by upstream gnome-settings-daemon[1]. 
In the
 > meantime, you can work around this issue by executing, for 
example:

 >
 >gsettings set sm.puri.phosh.notifications 
wakeup-screen-triggers '[]'


 Thanks this fixes the auto suspend, though one motivation for 
getting newer
 phosh was its suspend inhibition when wifi tethering is active, 
which is

 also disabled with this setting. But I can live with that until


Suspend when wifi hotspot is active is *not* related to any
wakup-screen-triggers. The phosh in stable/bookworm simply doesn't 
take

an inhibitor when the hotspot is active (this was added in 0.26.0).



I am using phosh 0.32 which I rebuilt on bookworm. So this added that 
feature but the other bug of never suspending made it unusable.

Cheers,
 -- Guido

 gnome-settings-daemon is fixed. This means I have to remember to 
toggle
 suspend when charging each time I turn on or off wifi tethering. I 
was using
 a script earlier to launch tethering and inhibit suspend earlier, I 
will go

 back to it until this gets fixed.






 > Cheers,
 > Arnaud
 >
 > [1]
 >
 
<>

 >
 > >
 > > I have built the debs already and started using it from 
yesterday. I
 > > have shared the debs in my personal repo [2]. I'd like to 
upload and
 > > help maintain it in bookworm-backports if you are okay with the 
idea of

 > > providing official backports.
 > >
 > > Since pureos crimson is not yet useable, I think this would be 
useful

 > > for many who want a newer base OS.
 > >
 > > [1]
 
<>

 > > [2] <>
 > >
 > > ___
 > > Debian-on-mobile-maintainers mailing list
 > > debian-on-mobile-maintain...@alioth-lists.debian.net 

 > > 
<>

 >
 >
 >






 ___
 Debian-on-mobile-maintainers mailing list
 debian-on-mobile-maintain...@alioth-lists.debian.net 

 

Bug#1053761: llvm-toolchain-16 16.0.6-15~deb11u2 flagged for acceptance

[Adam D Barratt]

package release.debian.org
tags 1053761 = bullseye pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian bullseye.

Thanks for your contribution!

Upload details
==

Package: llvm-toolchain-16
Version: 16.0.6-15~deb11u2

Explanation: build-dep on llvm-spirv instead of llvm-spirv-16

Bug#1019980: lintian: source-is-missing check for HTML is much too sensitive

[Bill Allombert]

On Sun, Sep 18, 2022 at 12:14:07AM +0100, Colin Watson wrote:
> Package: lintian
> Version: 2.115.3
> Severity: normal
> 
> Lintian issues these errors for putty 0.77-1:
> 
>   E: putty source: source-is-missing [doc/html/AppendixA.html]
>   E: putty source: source-is-missing [doc/html/AppendixB.html]
>   E: putty source: source-is-missing [doc/html/AppendixE.html]
>   E: putty source: source-is-missing [doc/html/Chapter10.html]
>   E: putty source: source-is-missing [doc/html/Chapter2.html]
>   E: putty source: source-is-missing [doc/html/Chapter3.html]
>   E: putty source: source-is-missing [doc/html/Chapter4.html]
>   E: putty source: source-is-missing [doc/html/Chapter5.html]
>   E: putty source: source-is-missing [doc/html/Chapter7.html]
>   E: putty source: source-is-missing [doc/html/Chapter8.html]
>   E: putty source: source-is-missing [doc/html/Chapter9.html]
>   E: putty source: source-is-missing [doc/html/IndexPage.html]
> 
> This is pretty oversensitive.  Firstly, it's HTML, which is still often
> enough written by hand anyway.  As it happens, these particular HTML
> files are generated from halibut input that's also provided in the
> source package, though I can't see how Lintian could possibly expect to
> know that.

Dear Lintian maintainers,

This test is causing hundreds of false positive and should be disabled as
soon as possible. This is a huge waste of time for everybody.

If you need help with that, please tell me, I have worked on lintian in the 
past.

Cheers,
-- 
Bill. 

Imagine a large red swirl here. 


signature.asc
Description: PGP signature

Bug#1043240: transition: pandas 1.5 -> 2.1

[Rebecca N. Palmer]

astropy isn't actually a regression (i.e. it's probably _a_ bug, but 
unrelated to pandas 2.x), and python-hypothesis appears to be fixed (by 
upstream, in 6.83.1).  I have filed individual bugs for the others.

Bug#1053106: please create a debian-za list for our Debian local user group in South Africa

[Stefano Rivera]

Hi Cord (2023.10.12_23:31:25_+0200)
> It would be also very much appreciated if several other people
> interested in the new list would send a mail to the bug, in order to
> record their interest. Til now there is none.

o/ I think this would be useful.

Stefano

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

Bug#1053941: python-geopandas: test failure with pandas 2.1

[Sebastiaan Couwenberg]

Control: tags -1 upstream
Control: forwarded -1 https://github.com/geopandas/geopandas/pull/2994

On Sat, 14 Oct 2023 18:00:53 +0100 "Rebecca N. Palmer" wrote:
python-geopandas fails its autopkgtest with pandas 2.1, currently in 
experimental.


Log:
https://ci.debian.net/data/autopkgtest/unstable/amd64/p/python-geopandas/38997837/log.gz

A common source of failures is new pandas FutureWarnings in tests that 
are set to fail on unexpected warnings.


The comment for the test in question suggests a known issues in pandas 
2.1.0:


 if not Version(pd.__version__) == Version("2.1.0"):
 # https://github.com/geopandas/geopandas/issues/2948 - bug in 
pandas 2.1.0


The workaround will need to be applied to 2.1.1 as well and likely all 
other 2.1.x releases.


I'll likely just add an xfail for this test if there is no upstream when 
pandas 2.1 moves to unstable.


Kind Regards,

Bas

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

Bug#1053948: patsy: FTBFS with pandas 2.1

[Rebecca N. Palmer]

Package: src:patsy
Version: 0.5.3-1
Control: block 1043240 by -1

patsy fails to build with pandas 2.1, currently in experimental.

Log:
https://launchpad.net/~rebecca-palmer/+archive/ubuntu/pandas2p1/+build/26770725/+files/buildlog_ubuntu-mantic-amd64.patsy_0.5.3-1_BUILDING.txt.gz

A common source of failures is new pandas FutureWarnings in tests that 
are set to fail on unexpected warnings.

Bug#1053852: btrfsd: Segfault in libgobject-2.0.so.0.7800.0[7fcec2dff000+34000]

[Matthias Klumpp]

Am Fr., 13. Okt. 2023 um 12:27 Uhr schrieb Vincent Blut
:
> [...]
> I built btrfsd with 59145f1 (utils: Don't free result twice when checking if 
> device is on
> battery) applied, that fixes the issue. Thanks!

Indeed, it was a really dumb oversight to free things manually that
automatic cleanup was already taking care of.
Sorry for that! There will be a new release today :-)

Cheers,
Matthias

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

Bug#1053946: tqdm: FTBFS with pandas 2.1

[Rebecca N. Palmer]

Package: src:tqdm
Version: 4.64.1-1
Control: block 1043240 by -1

tqdm fails to build with pandas 2.1, currently in experimental.

Log:
https://launchpad.net/~rebecca-palmer/+archive/ubuntu/pandas2p1/+build/26770822/+files/buildlog_ubuntu-mantic-amd64.tqdm_4.64.1-1_BUILDING.txt.gz

A common source of failures is new pandas FutureWarnings in tests that 
are set to fail on unexpected warnings.

Bug#1053947: dask: test failure with pandas 2.1

[Rebecca N. Palmer]

Package: src:dask
Version: 2023.8.0+dfsg-2
Control: block 1043240 by -1

dask fails its autopkgtest with pandas 2.1, currently in experimental.

Log:
https://ci.debian.net/data/autopkgtest/unstable/amd64/d/dask/38997774/log.gz

A common source of failures is new pandas FutureWarnings in tests that 
are set to fail on unexpected warnings.

Bug#1053945: seaborn: test failure with pandas 2.1

[Rebecca N. Palmer]

Package: src:seaborn
Version: 0.12.2-1
Control: block 1043240 by -1

seaborn fails its tests with pandas 2.1, currently in experimental.

Logs:
https://ci.debian.net/data/autopkgtest/unstable/amd64/s/seaborn/38997875/log.gz
https://launchpad.net/~rebecca-palmer/+archive/ubuntu/pandas2p1/+build/26770797/+files/buildlog_ubuntu-mantic-amd64.seaborn_0.12.2-1_BUILDING.txt.gz

A common source of failures is new pandas FutureWarnings in tests that 
are set to fail on unexpected warnings.

Bug#1053944: q2-types: test failure with pandas 2.1

[Rebecca N. Palmer]

Package: src:q2-types
Version: 2023.7.0-1
Control: block 1043240 by -1

q2-types fails its autopkgtest with pandas 2.1, currently in experimental.

Log:
https://ci.debian.net/data/autopkgtest/unstable/amd64/q/q2-types/38997869/log.gz

A common source of failures is new pandas FutureWarnings in tests that 
are set to fail on unexpected warnings.

Bug#1053943: q2-taxa: test failure with pandas 2.1

[Rebecca N. Palmer]

Package: src:q2-taxa
Version: 2023.7.0+dfsg-1
Control: block 1043240 by -1

q2-taxa fails its autopkgtest with pandas 2.1, currently in experimental.

Log:
https://ci.debian.net/data/autopkgtest/unstable/amd64/q/q2-taxa/38997868/log.gz

A common source of failures is new pandas FutureWarnings in tests that 
are set to fail on unexpected warnings.

Bug#1053942: q2-demux: test failure with pandas 2.1

[Rebecca N. Palmer]

Package: src:q2-demux
Version: 2023.7.0+dfsg-1
Control: block 1043240 by -1

q2-demux fails its autopkgtest with pandas 2.1, currently in experimental.

Log:
https://ci.debian.net/data/autopkgtest/unstable/amd64/q/q2-demux/38997862/log.gz

A common source of failures is new pandas FutureWarnings in tests that 
are set to fail on unexpected warnings.

Bug#1053941: python-geopandas: test failure with pandas 2.1

[Rebecca N. Palmer]

Package: src:python-geopandas
Version: 0.14.0-1
Control: block 1043240 by -1

python-geopandas fails its autopkgtest with pandas 2.1, currently in 
experimental.


Log:
https://ci.debian.net/data/autopkgtest/unstable/amd64/p/python-geopandas/38997837/log.gz

A common source of failures is new pandas FutureWarnings in tests that 
are set to fail on unexpected warnings.

Bug#1053940: python-cooler: test failure with pandas 2.1

[Rebecca N. Palmer]

Package: src:python-cooler
Version: 0.9.1-1
Control: block 1043240 by -1

python-cooler fails its autopkgtest with pandas 2.1, currently in 
experimental.


Log:
https://ci.debian.net/data/autopkgtest/unstable/amd64/p/python-cooler/38997833/log.gz

A common source of failures is new pandas FutureWarnings in tests that 
are set to fail on unexpected warnings.

Bug#1053939: pymatgen: test failure with pandas 2.1

[Rebecca N. Palmer]

Package: src:pymatgen
Version: 2023.06.23+dfsg1-2
Control: block 1043240 by -1

pymatgen fails its tests with pandas 2.1, currently in experimental.

Logs:
https://ci.debian.net/data/autopkgtest/unstable/amd64/p/pymatgen/38997822/log.gz

https://launchpad.net/~rebecca-palmer/+archive/ubuntu/pandas2p1/+build/26770738/+files/buildlog_ubuntu-mantic-amd64.pymatgen_2023.06.23+dfsg1-2_BUILDING.txt.gz

A common source of failures is new pandas FutureWarnings in tests that 
are set to fail on unexpected warnings.

Bug#1053938: python3-typeshed: please package a new snapshot

[Alexandre Detiste]

Package: python3-typeshed
Version: 0.0~git20221107.4f381af-1
Severity: normal

Hi,

I do understand that typing annotations are still a fast moving matter,
and users of typeshed should maybe rather install from pypi or git;
but still this one package is a huge conveniance to tip to.

Could you please update a new snapshot ?

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-1-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)

Versions of packages python3-typeshed depends on:
ii  python3  3.11.4-5+b1

python3-typeshed recommends no packages.

python3-typeshed suggests no packages.

-- no debconf information

Bug#1053747: [Debian-on-mobile-maintainers] Bug#1053747: Upload phosh to? bookworm-backports ?

[Guido Günther]

Hi,
On Fri, Oct 13, 2023 at 09:24:22PM +0530, Pirate Praveen wrote:
> On Wed, 11 Oct 2023 11:07:57 +0200 Guido =?iso-8859-1?Q?G=FCnther?=
>  wrote:
> > Hi Praveen,
> > I'm always in favour of providing newer phosh to users but see below for
> details:
> >
> > On Tue, Oct 10, 2023 at 02:33:52PM +0530, Pirate Praveen via
> Debian-on-mobile-maintainers wrote:
> > > Package: phosh
> > > Version: 0.32.0-1
> > > Severity: wishlist
> > >
> > > I think it'd be a good idea to provide new versions of phosh (with phoc,
> > > wlroots, feedbackd) via bookworm-backports. I was earlier daily driving
> > > mobian trixie on my Librem 5 but since its automatic suspend broke I
> could
> > > not continue using it [1]. So I'm using mobian bookworm but I miss the
> newer
> > > phosh (especially easy access to suspend button, which I use often for
> power
> > > saving).
> > >
> > > I have built the debs already and started using it from yesterday. I
> have
> > > shared the debs in my personal repo [2]. I'd like to upload and help
> > > maintain it in bookworm-backports if you are okay with the idea of
> providing
> > > official backports.
> >
> > I'm okay with the idea if you sign up to handle bug reports concerning
> > the backported versions. If that makes sense to you and Mobian has no
> > objections (as I think running it together with Mobian will be the main
> > use case for most people) we should maintain the backported branch in
> > the DebianOnMobile git too.
> >
> > Note that backporting phosh will imply backporting phoc at some point
> > and might also break phosh-mobile-settings at some point (and that
> > requires newer libadwaita already (which requires newer GTK). That
> > shouldn't' prevent us from backporting just now, just wanted to lay out
> > that it might get a bit more involved in the future.
> 
> I tried backporting phosh-mobile-settings now, as you mentioned it needs
> newer libadwaita, which in turn needs newer glib and gtk4. So I think gnome
> team won't like the official backports.

You can backport the *current* p-m-s version (see PureOS Crimson) without
newer libadwaita but that won't work forever.

Cheers,
 -- Guido

> 
> Arnaud,
> 
> Do you think it would be a good idea to have bookworm-backports suite in
> mobian repo and upload these there?
> 
> As for bugs, I think keeping up with new upstream versions would be a good
> strategy. If I go with byzantium experience, I'd think you will support
> newer versions on crimson, so having bookworm-backports should be easier to
> maintain.
> > Cheers and thanks for having a look at this,
> >  -- Guido
> >
> > >
> > > Since pureos crimson is not yet useable, I think this would be useful
> for
> > > many who want a newer base OS.
> > >
> > > [1]
> 
> > > [2] 
> > >
> > > ___
> > > Debian-on-mobile-maintainers mailing list
> > > debian-on-mobile-maintain...@alioth-lists.debian.net
> > > 
> > >
> >
> >
> 
> 
> 

Bug#1053747: [Debian-on-mobile-maintainers] Bug#1053747: Bug#1053747: Upload phosh to bookworm-backports ?

[Guido Günther]

Hi,
On Fri, Oct 13, 2023 at 09:13:39PM +0530, Pirate Praveen via 
Debian-on-mobile-maintainers wrote:
> On Tue, 10 Oct 2023 23:56:54 +0200 Arnaud Ferraris 
> wrote:
> > Hi,
> >
> > Le 10/10/2023 à 11:03, Pirate Praveen via Debian-on-mobile-maintainers a
> > écrit :
> > > Package: phosh
> > > Version: 0.32.0-1
> > > Severity: wishlist
> > >
> > > I think it'd be a good idea to provide new versions of phosh (with phoc,
> > > wlroots, feedbackd) via bookworm-backports. I was earlier daily driving
> > > mobian trixie on my Librem 5 but since its automatic suspend broke I
> > > could not continue using it [1]. So I'm using mobian bookworm but I miss
> > > the newer phosh (especially easy access to suspend button, which I use
> > > often for power saving).
> >
> > As discussed in the Mobian issue you mention, the auto-suspend problem
> > you're experiencing is only happening with recent versions of phosh,
> > which basically reset the idle counter when a critical notification
> happens.
> >
> > Providing a backported version of phosh wouldn't help there, and the
> > solution should be provided by upstream gnome-settings-daemon[1]. In the
> > meantime, you can work around this issue by executing, for example:
> >
> >gsettings set sm.puri.phosh.notifications wakeup-screen-triggers '[]'
> 
> Thanks this fixes the auto suspend, though one motivation for getting newer
> phosh was its suspend inhibition when wifi tethering is active, which is
> also disabled with this setting. But I can live with that until

Suspend when wifi hotspot is active is *not* related to any
wakup-screen-triggers. The phosh in stable/bookworm simply doesn't take
an inhibitor when the hotspot is active (this was added in 0.26.0).

Cheers,
 -- Guido

> gnome-settings-daemon is fixed. This means I have to remember to toggle
> suspend when charging each time I turn on or off wifi tethering. I was using
> a script earlier to launch tethering and inhibit suspend earlier, I will go
> back to it until this gets fixed.



> 
> > Cheers,
> > Arnaud
> >
> > [1]
> >
> 
> >
> > >
> > > I have built the debs already and started using it from yesterday. I
> > > have shared the debs in my personal repo [2]. I'd like to upload and
> > > help maintain it in bookworm-backports if you are okay with the idea of
> > > providing official backports.
> > >
> > > Since pureos crimson is not yet useable, I think this would be useful
> > > for many who want a newer base OS.
> > >
> > > [1]
> 
> > > [2] 
> > >
> > > ___
> > > Debian-on-mobile-maintainers mailing list
> > > debian-on-mobile-maintain...@alioth-lists.debian.net
> > > 
> >
> >
> >
> 
> 
> 

> ___
> Debian-on-mobile-maintainers mailing list
> debian-on-mobile-maintain...@alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-on-mobile-maintainers

Bug#1053761: bullseye-pu: package llvm-toolchain-16/16.0.6-15~deb11u1

[Andres Salomon]

On Sat, Oct 14 2023 at 12:01:05 PM +01:00:00, Adam D. Barratt 
 wrote:

On Sat, 2023-10-14 at 00:54 -0400, Andres Salomon wrote:

 I built deb11u2 with the following changes from 16.0.6-15. Chromium
 successfully builds against it. Let me know if you want me to file a
 separate release.d.o bug for it, or just upload it, or what.


[...]

 --- a/llvm-toolchain-16-16.0.6/debian/control   2023-09-10
 06:14:34.0 +
 +++ b/llvm-toolchain-16-16.0.6/debian/control   2023-10-13
 16:24:09.0 +
 @@ -23,7 +23,7 @@
  libctypes-ocaml-dev [amd64 arm64 armhf ppc64el riscv64 s390x],
  dh-exec, dh-ocaml [amd64 arm64 armhf ppc64el riscv64 s390x],
  libpfm4-dev [linux-any], python3-setuptools, libz3-dev,
 -llvm-spirv-16 [ amd64 arm64 armel armhf i386 mips64el ppc64el
 riscv64 s390x ]  | hello [!i386],
 +llvm-spirv [ amd64 arm64 armel armhf i386 mips64el ppc64el
 riscv64
 s390x ]  | hello [!i386],



Please go ahead (as a source-only upload).



Thanks, uploaded.


fwiw, for bookworm it looks like we'll need to use either 
llvm-spirv-14

or llvm-spirv-15.



I'll get started on the bookworm llvm stuff once chromium's 
uploaded/built for bullseye-security.


BTW, the bullseye llvm package went and reverted d/control when I 
rebuilt it, so I had to change d/control.in as well. The actual diff 
for what I uploaded:



diff -urN a/llvm-toolchain-16-16.0.6/debian/changelog 
b/llvm-toolchain-16-16.0.6/debian/changelog
--- a/llvm-toolchain-16-16.0.6/debian/changelog	2023-09-11 
13:40:42.0 +
+++ b/llvm-toolchain-16-16.0.6/debian/changelog	2023-10-13 
16:25:00.0 +

@@ -1,3 +1,16 @@
+llvm-toolchain-16 (1:16.0.6-15~deb11u2) bullseye; urgency=medium
+
+  * Build-dep on llvm-spirv instead of llvm-spirv-16 to make sbuild 
happy.

+
+ -- Andres Salomon   Fri, 13 Oct 2023 16:25:00 
+

+
+llvm-toolchain-16 (1:16.0.6-15~deb11u1) bullseye; urgency=medium
+
+  * Non-maintainer upload.
+  * Rebuild for bullseye.
+
+ -- Andres Salomon   Tue, 10 Oct 2023 05:55:47 
+

+
llvm-toolchain-16 (1:16.0.6-15) unstable; urgency=medium

  * Second attempt to refresh D158066.patch (Closes: #1049362)
diff -urN a/llvm-toolchain-16-16.0.6/debian/control 
b/llvm-toolchain-16-16.0.6/debian/control
--- a/llvm-toolchain-16-16.0.6/debian/control	2023-09-10 
06:14:34.0 +
+++ b/llvm-toolchain-16-16.0.6/debian/control	2023-10-13 
16:25:00.0 +

@@ -23,7 +23,7 @@
libctypes-ocaml-dev [amd64 arm64 armhf ppc64el riscv64 s390x],
dh-exec, dh-ocaml [amd64 arm64 armhf ppc64el riscv64 s390x],
libpfm4-dev [linux-any], python3-setuptools, libz3-dev,
-llvm-spirv-16 [ amd64 arm64 armel armhf i386 mips64el ppc64el 
riscv64 s390x ]  | hello [!i386],
+llvm-spirv [ amd64 arm64 armel armhf i386 mips64el ppc64el riscv64 
s390x ]  | hello [!i386],

spirv-tools [ linux-any ] | hello [ !i386],
wasi-libc | hello [ !any-i386],
libcurl4-openssl-dev | libcurl-dev,
diff -urN a/llvm-toolchain-16-16.0.6/debian/control.in 
b/llvm-toolchain-16-16.0.6/debian/control.in
--- a/llvm-toolchain-16-16.0.6/debian/control.in	2023-09-10 
06:14:36.0 +
+++ b/llvm-toolchain-16-16.0.6/debian/control.in	2023-10-13 
16:25:00.0 +

@@ -23,7 +23,7 @@
libctypes-ocaml-dev [amd64 arm64 armhf ppc64el riscv64 s390x],
dh-exec, dh-ocaml [amd64 arm64 armhf ppc64el riscv64 s390x],
libpfm4-dev [linux-any], python3-setuptools, libz3-dev,
-llvm-spirv-16 [ amd64 arm64 armel armhf i386 mips64el ppc64el 
riscv64 s390x ]  | hello [!i386],
+llvm-spirv [ amd64 arm64 armel armhf i386 mips64el ppc64el riscv64 
s390x ]  | hello [!i386],

spirv-tools [ linux-any ] | hello [ !i386],
wasi-libc | hello [ !any-i386],
libcurl4-openssl-dev | libcurl-dev,

Bug#967392: ghemical: depends on deprecated GTK 2

[Bastian Germann]

Please consider removing ghemical. It has quite a low popcon and is a blocker 
for removing both
libglade2 and gtkglext which should be removed with trixie even if we cannot 
remove GTK 2.

Bug#1053937: debian-installer: installer does not detect internal UFS-drive

[Patrick Rudin]

Package: debian-installer
Severity: important
Tags: d-i
X-Debbugs-Cc: taxi...@gmx.ch

I have a Microsoft Surface Go 4 Tablet, which has an internal 256 GB UFS-Drive.
Debian Live works fine, but its not possible to install Debian: When I get to
partitioning, the installer does not see the drive (the ubuntu installer does)
and only shows my installer-stick.

I guess the installer would need the ufshci-module to recognize the internal
UFS-Flash.

Tried with the stable-installer from Debian 12 and also with the daily build
from testing, no difference.





-- System Information:
Debian Release: 12.1
  APT prefers bookworm
  APT policy: (500, 'bookworm'), (500, 'stable')
Architecture: amd64 (x86_64)

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

Bug#931591: upgraded Handbrake crashes on encode with custom preset

[Harald Dunkel]

correction: the built-in presets are broken, too. It dies every
time. Error message:

[Sat Oct 14 17:58:17 2023] handbrake-gtk[52868]: segfault at 18 ip 
7f22a9c337eb sp 7f2229e5df40 error 4 in 
libavutil.so.58.2.100[7f22a9c17000+a8000] likely on CPU 4 (core 4, socket 0)
[Sat Oct 14 17:58:17 2023] Code: 02 00 e8 a8 39 fe ff e8 e3 3e fe ff 0f 1f 00 f3 0f 
1e fa 41 57 49 89 f7 41 56 49 89 fe 41 55 41 54 55 48 89 d5 53 48 83 ec 28 <48> 
8b 5f 18 48 89 54 24 08 64 48 8b 04 25 28 00 00 00 48 89 44 24

Regards
Harri

Bug#1053936: python3-distro-info: packaging lacks a py.typed flag file

[Alexandre Detiste]

Package: python3-distro-info
Version: 1.5
Severity: normal

Dear Maintainer,

While trying to validate game-data-packager's annotations, mypy complains:

$ mypy --strict tools/ppa.py'
tools/ppa.py:11: error: Skipping analyzing "distro_info": module is installed, 
but missing library stubs or py.typed marker  [import-untyped]
tools/ppa.py:11: note: See 
https://mypy.readthedocs.io/en/stable/running_mypy.html#missing-imports


After creating some py.typed - the locations _feels_ wrong,
but I don't know better - mypy will stop complaining:

~# mkdir /usr/lib/python3/dist-packages/distro_info
~# touch /usr/lib/python3/dist-packages/distro_info/py.typed

$ mypy --strict tools/ppa.py 
Success: no issues found in 1 source file


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-1-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)

Versions of packages python3-distro-info depends on:
ii  distro-info-data  0.58
ii  python3   3.11.4-5+b1

python3-distro-info recommends no packages.

python3-distro-info suggests no packages.

-- no debconf information

Bug#1053935: www.debian.org: outdated debian-cd, debian-archive, debian-ports mirror lists

[Jing Luo]

Package: www.debian.org
Severity: normal
X-Debbugs-Cc: mirr...@debian.org


The debian-cd [1][2], debian-archive [3], debian-ports [4] mirror lists are 
outdated. They do not reflect Mirrors.masterlist.in [5].
Related bug report: #1034832

Furthermore, the debian-cd mirroring instruction [6] says:

> You can register your mirror either by filling out _the mirror submission 
> form_ (note that the CDImage-* fields are the important ones), or by sending 
> an e-mail to debian...@lists.debian.org.

Now, the mirror submission form [7] does not allow submitting/updating 
debian-cd mirrors, and new debian-cd mirror submission sent to the debian-cd 
mailing lists have been ignored, all submission at least in the past 12 months 
have no reply.
Related bug report: #1053934

If the mirror lists are not automatically generated from Mirrors.masterlist.in, 
like /debian [8], maybe they really should be.

[1] https://www.debian.org/CD/http-ftp/
[2] https://www.debian.org/CD/mirroring/rsync-mirrors
[3] https://www.debian.org/distrib/archive
[4] https://www.ports.debian.org/mirrors
[5] 
https://salsa.debian.org/mirror-team/masterlist/-/blob/master/Mirrors.masterlist.in
[6] https://www.debian.org/CD/mirroring/
[7] https://www.debian.org/mirror/submit
[8] https://www.debian.org/mirror/list

Bug#1053934: www.debian.org: mirror submission form does not allow submitting or updating debian-cd mirrors

[Jing Luo]

Package: www.debian.org
Severity: important
X-Debbugs-Cc: debian...@lists.debian.org, mirr...@debian.org


The current debian-cd mirroring instruction page [1] says:

> You can register your mirror either by filling out _the mirror submission 
> form_ (note that the CDImage-* fields are the important ones), [...]

However, it looks like the submission form [2] has been updated recently, 
the HTTP path is "hard coded" to `/debian`. There is no `CDImage-*` fields
either. It is not possible to use this web form to submit/update a debian-cd 
mirror.

Either the instruction page needs to be updated with the latest procedure to 
submit a debian-cd mirror, or the form needs to be changed to allow 
debian-cd (or perhaps even debian-ports and debian-archive) mirror submission 
or update.

Bug#1052376: lxpanel: no longer obeys its geometry settings

[unknown]

Bug confirmed here on two laptops, exactly matching Francesco Poli's
description.

Grigor

Bug#1053933: ring: src:ring embeds md4c

[Tobias Frost]

Source: ring
Severity: important

Dear Maintainer,

ring embeds md4c. (3rdparty/md4c/)
This library is packaged in Debian as libmd4c, but the packaged version is not
used. This is a Policy violation (4.13).

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

Kernel: Linux 6.5.0-1-amd64 (SMP w/12 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
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

Bug#1052144: ghc: Needs to link against libatomic on at least m68k

[John Paul Adrian Glaubitz]

Hi!

On Sat, 2023-10-14 at 17:33 +0300, Ilias Tsitsimpis wrote:
> As a side note, I believe the attached patch is wrong, it changes the
> semantics of the functions. Notice that __sync_val_compare_and_swap()
> returns the initial value of the variable x, whereas
> __atomic_compare_exchange() returns true/false, depending on whether the
> operation succeeded. The correct patch is here [1].
> 
> Could this be the reason why your cross-compiler for m68k seg-faults?

Hmm, good point. I will verify that. Thanks for pointing this out!

Adrian

Bug#1052144: ghc: Needs to link against libatomic on at least m68k

[Ilias Tsitsimpis]

Hi Adrian,

On Sat, Oct 14, 2023 at 11:35AM, John Paul Adrian Glaubitz wrote:
> Attaching an updated version of the patch which applies against the 9.4.7-1
> version of the ghc package. Would be nice if it could be included for the
> next upload.

Thanks for the reminder, I will include this in the next upload.

As a side note, I believe the attached patch is wrong, it changes the
semantics of the functions. Notice that __sync_val_compare_and_swap()
returns the initial value of the variable x, whereas
__atomic_compare_exchange() returns true/false, depending on whether the
operation succeeded. The correct patch is here [1].

Could this be the reason why your cross-compiler for m68k seg-faults?

[1] 
https://gitlab.haskell.org/ghc/ghc/-/commit/f8fa1d08d7cbfef508bab355bda80f495e928f98

Best,

-- 
Ilias

Bug#1053932: mirrors: mirror submission for repo.jing.rocks/debian-archive

[Jing Luo]

Package: mirrors
Severity: wishlist
User: mirr...@packages.debian.org
Usertags: mirror-submission
X-Debbugs-Cc: szmun.l...@gmail.com


Submission-Type: new
Site: repo.jing.rocks
Old-http: /debian-archive/
Old-rsync: debian-archive/
Maintainer: Jing Luo 
Country: JP Japan
Location: Tokyo
Comment:

Trace Url: http://repo.jing.rocks/debian-archive/project/trace/
Trace Url: 
http://repo.jing.rocks/debian-archive/project/trace/klecker.debian.org
Trace Url: http://repo.jing.rocks/debian-archive/project/trace/repo.jing.rocks

Bug#1053931: restinio: [src:restinio] Uses embedded code copies

[Tobias Frost]

Source: restinio
Severity: important

Hi,

restino uses embedded code copies. This is against policy 4.13.

The directory dev/* contains for example
- catch2
- rapidjson
- nodejs/http_parser

There is also dev/restinio/third_party/zlib, which claims to be
  version 1.2.11, January 15th, 2017
This version might be suspectible to several security vulnerabilties.
I've not checked if it is used, though.

catch2 is declared as Build-Depends, but obviously not used:
When removing catch2, the package FTBFS.

Please use the packaged version whenever possible and to make sure
that they are used, remove the embedded code copies before building,
e.g in d/clean.

(Alternatively, repackaging the source package, would be possible,
as there is currently no upstream signature to verify)

Cheers,
tobi

Bug#1053930: mirrors: mirror submission for repo.jing.rocks/debian-ports

[Jing Luo]

Package: mirrors
Severity: wishlist
User: mirr...@packages.debian.org
Usertags: mirror-submission
X-Debbugs-Cc: szmun.l...@gmail.com


Submission-Type: new
Site: repo.jing.rocks
Ports-architecture: alpha hppa hurd-i386 ia64 kfreebsd-amd64 kfreebsd-i386 m68k 
powerpc ppc64 riscv64 sh4 sparc64 x32
Ports-http: /debian-ports/
Ports-rsync: debian-ports/
Maintainer: Jing Luo 
Country: JP Japan
Location: Tokyo
Comment: (please don't write this comment into Mirrors.masterlist.in) add 
/debian-ports/


Trace Url: http://repo.jing.rocks/debian-ports/project/trace/
Trace Url: http://repo.jing.rocks/debian-ports/project/trace/porta.debian.org
Trace Url: http://repo.jing.rocks/debian-ports/project/trace/repo.jing.rocks

Bug#1053929: linux-image-amd64: kernel fails to find all nvme SSDs

[Jeffrey Mark Siskind]

Package: linux-image-amd64
Version: 6.4.4-3~bpo12+1
Severity: important

Dear Maintainer,

   * What led up to the situation?

I purchased a new server: Supermicro AS-8125GS-TNHR. It has 17 NVME
drives installed:

1x Micron 7450
   12x Micron 9300
4x Micron 9400

Upon boot, /dev/nvme* only shows 10 drives: the Micron 7450, 8 of the
Micron 9300s, and 1 of the Micron 9400s. Before I plugged in the 12x
Micron 9300, /dev/nvme* only showed 2 drives: the Micron 7450 and 1 of
the Micron 9400s.

I run bookworm stable. Upon first install, it ran kernel
6.1.0-12. After an apt upgrade it ran 6.1.0-13. I also installed
6.4.0-0-deb12.2 from bookworm backports. All 3 exhibit the same
issue. the only difference is that under 6.1.0-13 the 10 drives that do
appear appear as /de/nvme{0,1,2,3,4,5,6,7,8,9} while under 6.4.0-0-deb12.2
the 10 drives that do appear appear as different numbers with some missing.

The 1x 7450 has 3 partitions: EFI, / formatted as btrfs, and swap.
The 12x 9300s are all formatted with 1 partition. There are 6 pairs of
2, Each pair has a btrfs raid1 file system. The 9400s are not yet formatted.

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

I tried 3 kernels: 6.1.0-12, 6.1.0-13, and 6.4.0-0-deb12.2.
I tried with and without the 12x 9300.
I enclose the output of ls /dev/nvme*, lspci -k, and hwinfo --disks below.

   * What was the outcome of this action?

All exhibit the same issue.

   * What outcome did you expect instead?

I had hoped that I would be able to access all 17 drives (and format
the 4x 9400s as a single btrfs raid1 filesystem).

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

Kernel: Linux 6.4.0-0.deb12.2-amd64 (SMP w/383 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
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 linux-image-amd64 depends on:
ii  linux-image-6.4.0-0.deb12.2-amd64  6.4.4-3~bpo12+1

linux-image-amd64 recommends no packages.

linux-image-amd64 suggests no packages.

-- no debconf information

Thanks,
Jeff (http: //engineering.purdue.edu/~qobi)

qobi@poto>ls /dev/nvme*
/dev/nvme1   /dev/nvme12n1/dev/nvme15n1/dev/nvme5n1
/dev/nvme10  /dev/nvme12n1p1  /dev/nvme15n1p1  /dev/nvme5n1p1
/dev/nvme10n1/dev/nvme14  /dev/nvme1n1 /dev/nvme6
/dev/nvme10n1p1  /dev/nvme14n1/dev/nvme1n1p1   /dev/nvme6n1
/dev/nvme11  /dev/nvme14n1p1  /dev/nvme3   /dev/nvme8
/dev/nvme11n1/dev/nvme14n1p2  /dev/nvme3n1 /dev/nvme8n1
/dev/nvme11n1p1  /dev/nvme14n1p3  /dev/nvme3n1p1   /dev/nvme8n1p1
/dev/nvme12  /dev/nvme15  /dev/nvme5
qobi@poto>
-
qobi@poto>lspci -k
00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 14a4 (rev 01)
   Subsystem: Super Micro Computer Inc Device 1d1c
00:00.2 IOMMU: Advanced Micro Devices, Inc. [AMD] Device 149e (rev 01)
   Subsystem: Advanced Micro Devices, Inc. [AMD] Device 149e
00:00.3 Generic system peripheral [0807]: Advanced Micro Devices, Inc. [AMD] 
Device 14a6
   Subsystem: Advanced Micro Devices, Inc. [AMD] Device 14a6
   Kernel driver in use: pcieport
00:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 149f (rev 01)
00:01.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 14ab (rev 01)
   Subsystem: Advanced Micro Devices, Inc. [AMD] Device 1234
   Kernel driver in use: pcieport
00:02.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 149f (rev 01)
00:03.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 149f (rev 01)
00:04.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 149f (rev 01)
00:05.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 149f (rev 01)
00:05.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 14aa (rev 01)
   Subsystem: Advanced Micro Devices, Inc. [AMD] Device 1234
   Kernel driver in use: pcieport
00:07.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 149f (rev 01)
00:07.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 14a7 (rev 01)
   Subsystem: Advanced Micro Devices, Inc. [AMD] Device 14a4
   Kernel driver in use: pcieport
00:07.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 14a7 (rev 01)
   Subsystem: Advanced Micro Devices, Inc. [AMD] Device 14a4
   Kernel driver in use: pcieport
00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller (rev 71)
   Subsystem: Super Micro Computer Inc FCH SMBus Controller
Kernel driver in use: piix4_smbus
   Kernel modules: i2c_piix4, sp5100_tco
00:14.3 ISA 

Bug#1053908: bookworm-pu: package calibre/6.13.0+repack-2+deb12u2

[yokota]

> It looks like you forgot the debdiff.

Oops, sorry. Here is debdeff.

--
YOKOTA Hiroshi


calibre_6.13.0+repack-2+deb12u2.debdiff
Description: Binary data

Bug#1053551: ftbfs on amd64 when building binary-arch

[Simon Richter]

Hi,

On 13.10.23 18:55, Simon Richter wrote:

There are a few dependency rules in the file that seem to do the same 
thing, but use the wrong target name, so they are ignored, and this 
doesn't seem to be a complete set anyway. I'm trying with the same 
addition of an order-only dependency that the gcc-13 commit does, if 
that fixes it, that should be good enough for now.


Okay, further debugging: The Modula2 tree uses $(generated_files) as a 
dependency to make sure the insn-*.h are generated before frontend files 
are built. This variable is set below the include directive in 
gcc/Makefile that pulls in the language fragments, so at the point where 
the rules are defined it is still empty, and since rule definitions 
evaluate the variables immediately, that is not revisited later, so all 
the Modula2 .o files are missing those dependencies.


I'm trying what happens if you set M2_OBJS = $(GM2_OBJS), so these .o 
files end up a) in normal dependency tracking, and b) to add the 
order-only dependency on $(generated_files) at the end of gcc/Makefiles 
to those objects as well.


The order-only dependency should be enough for the first build, and 
after that, normal dependency tracking takes over anyway, not that 
anyone cares.


Am I right in assuming that this is only a Debian problem because no one 
but us is gluing the M2 frontend onto gcc 12 anymore?


   Simon



OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1043240: transition: pandas 1.5 -> 2.1

[Rebecca N. Palmer]

Control: retitle -1 transition: pandas 1.5 -> 2.1

pandas 2.1 is now in experimental.  In addition to the above, it breaks 
these packages:
astropy dask patsy pymatgen python-cooler python-geopandas q2-demux 
q2-taxa q2-types seaborn tqdm

and maybe python-hypothesis.

(python-pauvre and sunpy are probably already fixed; drms and skyfield 
are probably unrelated to pandas.)


Build logs:
https://launchpad.net/~rebecca-palmer/+archive/ubuntu/pandas2p1/+builds?build_text=_state=failed

Autopkgtest logs:
https://qa.debian.org/excuses.php?experimental=1=pandas

Bug#1053926: mirrors: mirror submission for repo.jing.rocks/debian-cd

[Jing Luo]

Package: mirrors
Severity: wishlist
User: mirr...@packages.debian.org
Usertags: mirror-submission
X-Debbugs-Cc: szmun.l...@gmail.com


Submission-Type: new
Site: repo.jing.rocks
CDImage-http: /debian-cd/
CDImage-rsync: debian-cd/
Maintainer: Jing Luo 
Country: JP Japan
Location: Tokyo
Comment: (please don't write this comment into Mirrors.masterlist.in) add 
/debian-cd/, no architecture is excluded



Trace Url: http://repo.jing.rocks/debian-cd/project/trace/
Trace Url: http://repo.jing.rocks/debian-cd/project/trace/cdimage.debian.org
Trace Url: http://repo.jing.rocks/debian-cd/project/trace/repo.jing.rocks

Bug#1053925: apt-listchanges: Data left after purge

[Alexandre Detiste]

control: user cruft...@packages.debian.org
control: usertag -1 cruft

Hi, adding this to cruft list.

Thanks

Bug#1053663: libraft2: Consider switching upstream to cowsql/raft

[Free Ekanayaka]

Hi László,

László Böszörményi (GCS)  writes:

> Hi Free,
>
> On Sat, Oct 14, 2023 at 11:30 AM Free Ekanayaka  wrote:
>> Am I missing something? If there's consenus about this, I'd finalize the
>> changelog and start uploading raft-0.17.7-1.
>  Looks OK to me.

Thanks!

> Just a question if you tested building of raft with pbuilder.

I used cowbuilder, but yes.

> I've packaged your raft version 0.17.6 locally and it still hangs with
> the last output of 'PASS: test/unit/uv' when tried building with
> pbuilder.

The version that fixes it is 0.17.7, so yes, 0.17.6 should still fail.

Cheers,

Free

Bug#1053925: apt-listchanges: Data left after purge

[Andreas Metzler]

Package: apt-listchanges
Version: 4.2
Severity: normal


Hello,

root@argenau:~# dpkg --purge apt-listchanges
(Reading database ... 181039 files and directories currently installed.)
Removing apt-listchanges (4.2) ...
Purging configuration files for apt-listchanges (4.2) ...
Processing triggers for man-db (2.11.2-3) ...
root@argenau:~# ls /var/lib/apt/listchanges* -l
-rw-rw-r-- 1 root root 1639673 Oct 14 14:08 /var/lib/apt/listchanges
-rw-r--r-- 1 root root 1625708 Oct 14 14:03 /var/lib/apt/listchanges-old

/var/lib/apt/listchanges-snapshots:
total 1020
-rw-rw-r-- 1 root root 1039832 Oct 14 14:08 2023-10-14T14:06:17.tar.xz

cu Andreas

Bug#1053924: timew: autopkgtests fail with man-db 2.12.0

[Colin Watson]

Source: timew
Version: 1.5.0+ds.1-1
Severity: important
Tags: patch

In response to https://gitlab.com/man-db/man-db/-/issues/17, I changed
the mandb program in man-db 2.12.0 to issue a warning if it's run
without the -u/--user-db option but doesn't have the necessary
permissions to write to system databases.  This caused timew's
autopkgtests to fail due to the extra text on stderr.  The following
patch fixes it.

diff --git a/debian/tests/timewarrior b/debian/tests/timewarrior
index 53bea1c..dcd6021 100644
--- a/debian/tests/timewarrior
+++ b/debian/tests/timewarrior
@@ -11,7 +11,7 @@ mkdir src
 ln -s /usr/bin/timew src/timew
 
 # regen man DB, since the tests use it
-mandb
+mandb -u
 
 cd test
 # requires compilation

Thanks,

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

Bug#1053923: gnome-keyring: After upgrade to Bookworm gnome-keyring-daemon shuts down and does not restart correctly

[Nate Bargmann]

Package: gnome-keyring
Version: 42.1-1+b2
Severity: important

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Dear Maintainer,

About two months ago I upgraded this desktop from Bullseye to Bookworm.
With Bullseye, and Buster prior, gnome-keyring-daemon worked reliably
and without issue for automatically handling SSH keys and other
credentials.  After the upgrade it wasn't too long before I was puzzled
as to why I was being prompted for SSH key passwords.  A short
investigation revealed the daemon was not running.

I rebooted the system and the daemon was running and handling SSH key
passwords as I expected and I regarded the matter as an upgrade glitch
until some time later the prompts for SSH keys passwords returned.
Puzzled, I posted a message to the Debian User mailing list:

https://lists.debian.org/debian-user/2023/08/msg00406.html

Which did receive one followup.  Two weeks later I posted to the GNOME
Keyring discourse:

https://discourse.gnome.org/t/keyring-crashing-troubleshooting-help-please/16880

and was advised to open issues in the GNOME Keyring repository that I
have done:

https://gitlab.gnome.org/GNOME/gnome-keyring/-/issues/135
https://gitlab.gnome.org/GNOME/gnome-keyring/-/issues/136

Issue #135 has been updated with requested GDB output.

Since that time it doesn't matter if I logout/login or worm/cold restart
the system, gnome-keying-daemon will reliably shut down after about an
hour, restart but be useless having lost login credentials and then shut
down permanently until the next login event.

At one point I even moved the files under ~/.local/share/keyrings to a
temporary directory and let the daemon create new ones only for the
early shut downs to continue.  I also found that Chromium directly accesses
login.keyring under that directory so I restored the original to give
access to stored passwords under Chromium (as an aside, when the daemon
is not running and I start Chromium, I will get the GTK PIN Entry dialog
which opens the keyring for Chromium and it stays open until Chromium is
closed).

None of these actions have had any effect on keeping the daemon running.
Also, I have noticed no such issues on my laptop also running Debian 12
and the GNOME desktop.  One difference between the two systems is that I
have Chromium installed through Flatpack on the laptop rather than use
the provided Debian package (historical reasons).  On this desktop the
Debian Chromium package is installed.  Also, this desktop has snapd
installed to run the latest version of Hugo.  This was installed under
Bullseye with no apparent side effects.

Mostly I am recording this to provide information of the issues in
GNOME's Gitlab for the benefit of any future resolution.



- -- System Information:
Debian Release: 12.2
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 
'stable'), (100, 'bookworm-fasttrack')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.1.0-13-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE
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 gnome-keyring depends on:
ii  dbus-user-session [default-dbus-session-bus]  1.14.10-1~deb12u1
ii  dbus-x11 [dbus-session-bus]   1.14.10-1~deb12u1
ii  dconf-gsettings-backend [gsettings-backend]   0.40.0-4
ii  gcr   3.41.1-1+b1
ii  init-system-helpers   1.65.2
ii  libc6 2.36-9+deb12u3
ii  libgck-1-03.41.1-1+b1
ii  libgcr-base-3-1   3.41.1-1+b1
ii  libgcrypt20   1.10.1-3
ii  libglib2.0-0  2.74.6-2
ii  libsystemd0   252.17-1~deb12u1
ii  p11-kit   0.24.1-2
ii  pinentry-gnome3   1.2.1-1

Versions of packages gnome-keyring recommends:
ii  gnome-keyring-pkcs11  42.1-1+b2
ii  libpam-gnome-keyring  42.1-1+b2

gnome-keyring suggests no packages.

- -- debconf-show failed

-BEGIN PGP SIGNATURE-

iGsEARECACsWIQSC1k9rDmfNQfaJu6b7LFEw1VqIGQUCZSqDpg0cbjBuYkBuMG5i
LnVzAAoJEPssUTDVWogZ3HMAnj+rZguubzEymOl0Rzh8vWAUCZ2iAJ4iyU4fKTQp
nMDTtoAiXBI4SQLB/Q==
=5JZA
-END PGP SIGNATURE-

Bug#1053913: rsyslog: PrivateDevices=yes breaks forwarding messages to xconsole

[Sven Joachim]

On 2023-10-14 12:13 +0200, Michael Biebl wrote:

> Thanks for the bug report
>
> Am 14.10.23 um 10:15 schrieb Sven Joachim:
>> Package: rsyslog
>> Version: 8.2310.0-1
>> For many years I have been following the recipe for forwarding
>> messages
>> to xconsole, see "Logging to xconsole" section in README.Debian.
>> This stopped working after the upgrade to 8.2310.0-1, because with
>> PrivateDevices=yes rsyslogd gets its own /dev directory where there is
>> no /dev/xconsole.
>> Adding an override for this setting was not difficult, but the
>> necessity
>> to do that should be added to README.Debian.
>
>
> Could you try if adding
> ```
> BindPaths=-/dev/xconsole
> ```
> to the [Service] section in rsyslog.service fixes your issue?

Yes, that works :-) .  Thanks for the hint, I did not know about the
BindPaths= directive.

Cheers,
   Sven

Bug#1041692: python3-mesonpy: could the build be verbose by default

[stefanor]

Hi Simon (2023.10.14_10:54:21_+)
> > Another way to achieve this in packages like python-fabio and pyfai
> > would be to bypass pyproject and meson-python to run Meson directly,
> > either manually per-package via "export PYBUILD_SYSTEM=meson", or maybe
> > automatically in pybuild when build-backend = 'mesonpy' is found (but
> > perhaps that would be too much magic).
> 
> Also an option. Means duplicating less of debhelper in dh-python.
> 
> Yeah, having the pyproject backend do non-pyproject builds would be a
> bit unexpected, I agree. Not sure I'd want to go there.

Thinking about that more, does mesonpy ever do anything else beyond
building with meson?

Just scoring the meson pybuild backend above the pyproject backend
should be sufficient, then. That's how things stand right now.

Stefano

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

Bug#1053922: nextcloud-desktop: Two-factor authentication notifications unusable

[Krzysztof Lubański]

Package: nextcloud-desktop
Version: 3.7.3-1
Severity: important
Tags: upstream
X-Debbugs-Cc: bugs.debian@lubanski.waw.pl

Hi!

The current nextcloud-desktop package version in Debian bookworm/12.2
shows two-factor authentication notifications, but does not list them in
the main dialog window - so a user cannot approve or deny them.

This renders it unusable for two-factor authentication, requiring the
user to have a logged-in Nextcloud client on a different system to
approve their browser logins.

This has been fixed upstream in v3.8.0:

https://github.com/nextcloud/desktop/pull/5486/commits/ec7b5481d45f89bccbe2fc7cb8cd0548452c8729

Debian testing's previous nextcloud-desktop package version, 3.9.0-1,
had this working and was installable on bookworm without impacting
non-Nextcloud packages.

The current package version in testing, 3.10.0-1, however, depends on
versions of libstdc++6 and its dependency gcc-13-base from testing.

Cheers,
Luban


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

Kernel: Linux 6.1.0-13-amd64 (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_BAD_PAGE
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 nextcloud-desktop depends on:
ii  libc6  2.36-9+deb12u3
ii  libcloudproviders0 0.3.1-2
ii  libgcc-s1  12.2.0-14
ii  libglib2.0-0   2.74.6-2
ii  libkf5archive5 5.103.0-1
ii  libnextcloudsync0  3.7.3-1
ii  libqt5core5a   5.15.8+dfsg-11
ii  libqt5dbus55.15.8+dfsg-11
ii  libqt5gui5 5.15.8+dfsg-11
ii  libqt5keychain10.13.2-5
ii  libqt5network5 5.15.8+dfsg-11
ii  libqt5qml5 5.15.8+dfsg-3
ii  libqt5quick5   5.15.8+dfsg-3
ii  libqt5quickcontrols2-5 5.15.8+dfsg-2
ii  libqt5sql5-sqlite  5.15.8+dfsg-11
ii  libqt5svg5 5.15.8-3
ii  libqt5webenginecore5   5.15.13+dfsg-1~deb12u1
ii  libqt5webenginewidgets55.15.13+dfsg-1~deb12u1
ii  libqt5widgets5 5.15.8+dfsg-11
ii  libstdc++6 12.2.0-14
ii  nextcloud-desktop-common   3.7.3-1
ii  nextcloud-desktop-l10n 3.7.3-1
ii  qml-module-qt-labs-platform5.15.8+dfsg-2
ii  qml-module-qtgraphicaleffects  5.15.8-2
ii  qml-module-qtqml   5.15.8+dfsg-3
ii  qml-module-qtqml-models2   5.15.8+dfsg-3
ii  qml-module-qtquick-controls2   5.15.8+dfsg-2
ii  qml-module-qtquick-dialogs 5.15.8-2
ii  qml-module-qtquick-layouts 5.15.8+dfsg-3
ii  qml-module-qtquick-window2 5.15.8+dfsg-3
ii  qml-module-qtquick25.15.8+dfsg-3

Versions of packages nextcloud-desktop recommends:
ii  nextcloud-desktop-doc  3.7.3-1

nextcloud-desktop suggests no packages.

-- no debconf information

Bug#1053901: tech-ctte: Repeal merged-/usr file movement moratorium

[Stefano Rivera]

Hi Sean (2023.10.13_22:59:56_+0200)
> === BEGIN
> 
> OPTION A:
> 
> The Technical Committee formally repeals its moratorium recommending
> that maintainers of individual packages should not proactively move
> files from the root filesystem to corresponding locations under /usr in
> the data.tar.* of packages (see #1035831).
> 
> Under Constitution 6.1.5, the Technical Committee now recommends that
> maintainers consult with those driving the merged-/usr transition before
> moving files from the root filesystem to corresponding locations under
> /usr in the data.tar.* of packages.
> 
> The transition driver, which at the time of writing is Helmut Grohne, is
> using a phased approach, in which the moratorium is rolled back for only
> certain classes of packages, and changes, at a time.  In addition,
> restructuring uploads should be targeted at experimental, and left for
> three days.  This is in order that automated testing by dumat can occur.
> 
> We recommend following , as edited by
> the transition driver(s).  If there is any doubt as to whether a change
> you wish to make is appropriate, please seek explicit approval from the
> transition driver(s).
> 
> OPTION N:
> 
> None of the above.
> 
> === END

I vote A > N

Stefano

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


signature.asc
Description: PGP signature

Bug#1053663: libraft2: Consider switching upstream to cowsql/raft

[GCS]

Hi Free,

On Sat, Oct 14, 2023 at 11:30 AM Free Ekanayaka  wrote:
> Am I missing something? If there's consenus about this, I'd finalize the
> changelog and start uploading raft-0.17.7-1.
 Looks OK to me.
Just a question if you tested building of raft with pbuilder. I've
packaged your raft version 0.17.6 locally and it still hangs with the
last output of 'PASS: test/unit/uv' when tried building with pbuilder.

Cheers,
Laszlo/GCS

Bug#1053901: tech-ctte: Repeal merged-/usr file movement moratorium

[Helmut Grohne]

Hi,

On Fri, Oct 13, 2023 at 09:59:56PM +0100, Sean Whitton wrote:
> === BEGIN
> 
> OPTION A:
> 
> The Technical Committee formally repeals its moratorium recommending
> that maintainers of individual packages should not proactively move
> files from the root filesystem to corresponding locations under /usr in
> the data.tar.* of packages (see #1035831).
> 
> Under Constitution 6.1.5, the Technical Committee now recommends that
> maintainers consult with those driving the merged-/usr transition before
> moving files from the root filesystem to corresponding locations under
> /usr in the data.tar.* of packages.
> 
> The transition driver, which at the time of writing is Helmut Grohne, is
> using a phased approach, in which the moratorium is rolled back for only
> certain classes of packages, and changes, at a time.  In addition,
> restructuring uploads should be targeted at experimental, and left for
> three days.  This is in order that automated testing by dumat can occur.
> 
> We recommend following , as edited by
> the transition driver(s).  If there is any doubt as to whether a change
> you wish to make is appropriate, please seek explicit approval from the
> transition driver(s).
> 
> OPTION N:
> 
> None of the above.
> 
> === END

I explicitly abstain from voting.

Rationale: I am severely biased on this matter. When I started working
on /usr-merge, I indicated that I would abstain from related votes. This
is one of those votes. If I were instead voting A = N as a means of not
biasing the vote, I would lower the quorum by providing a vote and thus
increasing other voter's vote weights. Hence, I am not providing a vote
at all on this.

On a technical level, I support this matter of course and I even
encouraged developers to ignore the moratorium in specific cases already
as a means to gather more experience with doing so. For more background
information, refer to
https://lists.debian.org/debian-devel/2023/10/msg00028.html.

Helmut


signature.asc
Description: PGP signature

Bug#1053921: dnsmasq: missing Git tag upstream/2.90

[Gioele Barabucci]

Package: src:dnsmasq
Found: 2.90-1

Dear dnsmasq maintainer,

the tag upstream/2.90 is missing from the Git repo 
.


This breaks gbp-buildpackage and the Salsa-CI pipeline:

$ gbp buildpackage
gbp:error: upstream/2.90 is not a valid treeish

(From .)

Regards,

--
Gioele Barabucci

Bug#848578: [PATCH 1/2] ts: Enable perl locale input/output conversion (Closes: #848578)

[Nicolas Schier]

Enable perl locale support to ensure that I/O is treated with the
encoding indicated by the locale, be it UTF-8 or something else.

Link: https://perldoc.perl.org/perllocale#Unicode-and-UTF-8
Patch-by: Dr. Thomas Orgis 
Signed-off-by: Nicolas Schier 
---
 ts | 1 +
 1 file changed, 1 insertion(+)

diff --git a/ts b/ts
index af23cf7..71b0fbc 100755
--- a/ts
+++ b/ts
@@ -53,6 +53,7 @@ use warnings;
 use strict;
 use POSIX q{strftime};
 no warnings 'utf8';
+use open q{:locale};
 
 $|=1;
 
-- 
2.42.0

Bug#1041291: [PATCH 2/2] ts: Do not accept extra args and always read from stdin (Closes: #1041291)

[Nicolas Schier]

Stop accepting more args than the optional format string and explicitly
read only from stdin.

In the linked Debian bug report, a detailed description about irregular
behaviour of ts with special extra args is available.

Reported-by: Zefram 
Co-developed-by: Zefram 
Link: https://bugs.debian.org/1041291#5
Signed-off-by: Nicolas Schier 
---
 ts | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/ts b/ts
index 71b0fbc..982c164 100755
--- a/ts
+++ b/ts
@@ -67,7 +67,7 @@ GetOptions(
"i" => \$inc,
"s" => \$sincestart,
"m" => \$mono
-) || die "usage: ts [-r] [-i | -s] [-m] [format]\n";
+) && @ARGV <= 1 or die "usage: ts [-r] [-i | -s] [-m] [format]\n";
 
 if ($rel) {
eval q{
@@ -111,7 +111,7 @@ else {
 }
 
 
-while (<>) {
+while () {
if (! $rel) {
if ($hires) {
my $f=$format;
-- 
2.42.0

Bug#1053909: anbox: Failed to start as either binder or ashmem kernel drivers are not loaded

[Shengjing Zhu]

On Sat, Oct 14, 2023 at 12:21 PM Alex Relis  wrote:
> Further research also tells me that Anbox's development is inactive, so
> I might just give up on this. Just thought I'd let you know about the
> status of this package.

anbox is already removed from Debian 12 and later.
https://tracker.debian.org/pkg/anbox


--
Shengjing Zhu