Bug#1055044: RM: sugar-artwork/0.120-1

[Jonas Smedegaard]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: rm
X-Debbugs-Cc: sugar-artw...@packages.debian.org
Control: affects -1 + src:sugar-artwork

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

(explain the reason for the removal here)

The binary package gtk2-engines-sugar is obsolete, and seems to need
manual removal from testing for newer releases to migrate.

Kind regards,

 - Jonas
-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmU/QSoACgkQLHwxRsGg
ASFNvw/9HSlA4lJHHlAmU5RA3GalGUrva9zOV6IYimWxw67FUaM03JNdc8uk79+W
KR0qVha2/oFzUMWCLlQeZrNB9tOIQfkobSGbMzERWmnYVEU9Z+zJypHrlwWcieVr
k13hX5/9hqmOJsfEH8Mo7suau05T9SVT2MxapK+v13bjvdFPp+Jwj0L04uOhOJVk
HiQ3yvN2EvNgpm+ofbxdTKvsrJl4VnrdL/ZfO34CvYv4ZQQ+BfEj6Zp4bdooI5Qq
9xTI47Iu70aLJ2/MncxrvD8kKO1c/ELhESQeHCDCMJyjL3jHKJxbuSbzTAAr4eMr
bgt1Jb3Em0TyH7uzc3kmgb9/bkADaAEYaaxH5v9YodtF5sQPxu6AurmJqYNkKSf6
qUt9Tyt8WCz7bpIUl5gUftLGWf3bFSm00kWtF3k68aF0MvH6N++CwCzTNiANQyen
UA7DB7VosSh15GB6acH7AgSAa1OWou37OgOpQHkVBBVtoZtlI9QcfP6R1+eMAmZC
OgzjgjvHQG+sv5yAHzGw84c5oDpmZntPttHoSlQQlq+8i4C/EsUD2rXXOsDYkz11
YKzyJS4V9UWTmahpZmSTrc5XrTrtuAQAX57ydKItuCZ76UkqxDGiPp0bFIs6nMp2
zTPyu1upM8OTjwV8DF+BLzfjbUhOmt8Ki8Sb7781p3G0V/yE/qY=
=O0Q3
-END PGP SIGNATURE-

Bug#1055043: Debian carnivore: port from Python 2 to 3

[Paul Wise]

Package: qa.debian.org
Severity: serious
User: qa.debian@packages.debian.org
Usertags: carnivore
X-Debbugs-CC: m...@qa.debian.org, debian-pyt...@lists.debian.org

The carnivore system which tracks the activity of Debian members is
written in Python 2, which has been removed from Debian, so carnivore
needs porting to Python 3 and volunteers are needed to work on that.

https://salsa.debian.org/qa/qa/-/tree/master/carnivore/
https://salsa.debian.org/qa/qa/-/blob/master/data/cronjobs/carnivore
https://salsa.debian.org/qa/qa/-/blob/data/cronjobs/ddpo.carnivore
https://salsa.debian.org/qa/qa/-/blob/data/ddpo/extract_carnivore.pl

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#1053885: manpages generation for many commands is flawed

[Osamu Aoki]

control: reassign -1 src:golang-github-spf13-cobra
thanks

Hi,

On Mon, 2023-10-30 at 03:12 +, Mathias Gibbens wrote:
> Hi Osamu,
> 
>   Thanks for noticing and reporting this. I've looked into it a bit,
> and I think it would be appropriate to report this to the spf13/cobra
> project[0]. From my reading of the LXD/Incus use of the library, I
> don't think they're doing anything "special" that would affect the
> behavior generating the manpages. If you do report it there, we can re-
> assign this bug to src:golang-github-spf13-cobra.
> 
> Mathias
> 
> [0] -- https://github.com/spf13/cobra

Thanks for your assessment.  I had the same feeling but wasn't sure on build
process.  Let's reassign this.

Bug#1052597: RFS: libkysdk-base/2.2.0.1-1 -- common files for kylin sdk base library

[xibowen]

Hi. thanks for reply.

>
> I'm curious if libkysdk-base-common is really needed? This will also
> require a NEW processing btw.
>

I have removed the libkysdk-base-common and uploaded to mentors.

Lastest upload: https://mentors.debian.net/package/libkysdk-base/

 libkysdk-base (2.2.0.1-1) unstable; urgency=medium
 .
   * Update libs soname version.
   * Fix compile error on armhf and ppc64el.
   * d/control:
 - Add Multi-Arch.

Regards,
xibowen

Bug#1051979: Do not suggest APT::Default-Release setting

[Osamu Aoki]

control: tags -1 pending
thanks

Hi,

On Thu, 2023-09-21 at 21:56 +0700, Max Nikulin wrote:
> 
> On 18/09/2023 20:12, Osamu Aoki wrote:
> > 
> > Since　Bug#1041708 was mentioned, I CC it.
> 
> It is marked as "done", so perhaps you need to reopen it if you expect
> some actions.
> 
> > I propose to replace this line with
> > 
> >     APT::Default-Release "testing";
> > 
> > I think this don't drive people to set this to "stable" as much.
> 
>  From my point of view it is a bit better, but hardly noticeable. And it
> is still misleading for Debian users since testing has security updates
> as well, thus not so trivial regexp is preferred. apt.conf(5) has more
> examples, but neither of them is close to what might be used in real life:

Although, repository for testing security updates exists, it is hardly used in
practice. 

> > Default-Release
> > 
> > Default release to install packages from if more than one version is
> > available. Contains release name, codename or release version. Examples:
> > 'stable', 'testing', 'unstable', 'bookworm', 'trixie', '4.0', '5.0*'.
> > See also apt_preferences(5).
> 
> I believe that explicit warnings against usage of APT::Default-Release
> will be helpful for users.
> 
> I have not noticed issues with regexp and "apt-get source" or synaptic
> in bookworm. Either they exist or not, mention of regexp as an option is
> valuable from my point of view (with or without a warning concerning
> lack of support in some tool). It will affect decision of those who are
> aware of regexp from the bullseye release notes.
> 

I don't want to spend too much on past release related bugs (including
documentation).  DR is an entry document so it shouldn't clutter.  I decided to
change DR as follows by drop mentioning "APT::Default-Release "stable":

Current text:
   The target release archive can be set by several methods.
   * "/etc/apt/apt.conf" configuration file with "APT::Default-Release 
"stable";"
   line
   * command line option, e.g., "apt-get install -t testing some-package"
   
Updated text:

   The target release archive can be set by the command line option, e.g., 
"apt-get
   install -t testing some-package"
   
For APT bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041708
this is outside of my control and it has been closed by the maintainer.  So I
didn't CC this reply.

Regards,

Osamu

Bug#1053885: manpages generation for many commands is flawed

[Mathias Gibbens]

Hi Osamu,

  Thanks for noticing and reporting this. I've looked into it a bit,
and I think it would be appropriate to report this to the spf13/cobra
project[0]. From my reading of the LXD/Incus use of the library, I
don't think they're doing anything "special" that would affect the
behavior generating the manpages. If you do report it there, we can re-
assign this bug to src:golang-github-spf13-cobra.

Mathias

[0] -- https://github.com/spf13/cobra


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

Bug#1031978: debian-reference-fr: wrong position for tables in french PDF version

[Osamu Aoki]

Control: severity -1 wishlist
Control: tags -1 wontfix
thanks

There is no simple way to change table placement in PDF for debian-reference
(DR).  I think the mentioned table is in the correct position in HTML.  Latex
tool chain relocate it to appropriate position considering the PDF is page
based.

I understand this may be uncomfortable for you but this is mostly preference
issue.  So this is wishlist bug.  Also this happens outside of my control, I
mark this as wontfix.

Best regards,

Osamu

Bug#1055041: RFS: a2d/2.0.3-1 -- APRS to DAPNET portal

[Yogeswaran Umasankar]

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

Dear mentors,

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

 * Package name : a2d
   Version  : 2.0.3-1
   Upstream contact : Yogeswaran Umasankar 
 * URL  : https://github.com/NGC2023/a2d
 * License  : MIT, CC-BY-3.0
 * Vcs  : https://salsa.debian.org/yogu/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/

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

  dget -x https://mentors.debian.net/debian/pool/main/a/a2d/a2d_2.0.3-1.dsc

Changes since the last upload:

 a2d (2.0.3-1) unstable; urgency=medium
 .
   * New upstream version.
   * Fixed failed VCS repository. (Closes: #1055040)

Regards,
-- 
  Yogeswaran Umasankar

Bug#1055040: a2d: Failed to analyze the VCS repository, and new upstream available

[Yogeswaran Umasankar]

Package: a2d
Version: 2.0.0-1
Severity: normal
X-Debbugs-Cc: kd8...@gmail.com

Hi,
In tracker debian, vcswatch reports that there is an error with this package's 
VCS.

I am uploading the updated package with new upstream, and fixed VCS repository 
in the Debian/control.

New upstream version: 2.0.3

Regards,
 Yogeswaran.

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

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

Versions of packages a2d depends on:
ii  certbot   2.1.0-4
ii  init-system-helpers   1.65.2
ii  nginx 1.24.0-2
ii  python3   3.11.2-1+b1
ii  python3-crontab   3.0.0-1
ii  python3-cryptography  38.0.4-3
ii  python3-flask 2.2.5-1
ii  python3-gunicorn  20.1.0-6
ii  python3-psutil5.9.5-1
ii  python3-requests  2.28.1+dfsg-1

a2d recommends no packages.

a2d suggests no packages.

-- no debconf information

Bug#686481: debian-reference instructs users on how to install non-free software

[Osamu Aoki]

Control: tags -1 - moreinfo
Control: tags -1 + wontfix
thanks

This is about https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=686481

I have made major update of debian-reference (DR) in 2012 and 2022 to address
this bug report concerns and non-free-firmware. I realized this old bug is still
around for my package.  Let me reassess this bug.

The title of this bug by "SirGrant" is misleading at least for the current DR. 
DR doesn't instruct *instruct* user to install non-free software.  DR only
provides  information on how to install non-free software.

Moreover, current DR explicitly mention in "2.1.6. Debian is 100% free software"
https://www.debian.org/doc/manuals/debian-reference/ch02.en.html#_debian_is_100_free_software
as:

   Users should be aware of the risks of using packages in the non-free, 
non-free-
   firmware and contrib areas:
   
   * lack of freedom for such software packages
   * lack of support from Debian on such software packages (Debian can't 
 support software properly without having access to its source code.)
   * contamination of your 100% free Debian system

So I think I am respectful for people not wishing to get close to non-free.

My message was a bit ambiguous in
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=686481#20 .

What I meant was I am happy to accept practical path for technical measures on
DR (not Debian Policy) which enable to keep quiet on even mentioning non-free in
DR as an optional build feature for particular distribution.  After 10+ years,
no productive proposal nor discussion has happened on this direction.

Also, in light of Debian CD including non-free-firmware these days, I think that
the level of *mention* in DR is appropriate.  So I can close this bug but for
avoiding future repeat of this discussion, I decided to keep this bug but with
changing this bug tag from moreinfo to wontfix.

Regards,

Osamu

PS: I am CCing people who participated on this bug.  I intentinally excluded
list address.

Bug#1055039: redis-server: Crash every two hours (oom), seemingly due to systemd's ProcSubset=pid

[Arnaud Rebillout]

Package: redis-server
Version: 5:7.0.11-1
Severity: important
User: de...@kali.org
Usertags: origin-kali

Dear Maintainer,

After migrating an instance from bullseye to bookworm, redis started to
crash every 2 hours. I tracked it to a change in the system unit file,
the value ProcSubset=pid is what causes the issue.

Long story below.

Part of the Kali Linux infrastructure, we have a host that runs
mirrorbits, a geo redirector. Mirrorbits stores its data in a redis
database.

Some quick numbers:

```
# free -h
 total  used  free  shared  buff/cache  available
Mem:  61Gi  24Gi  13Gi   612Ki22Gi   37Gi
Swap:   0B0B0B

# redis-cli info | grep -E '(used_memory_(peak_)?human)'
used_memory_human:22.94G
used_memory_peak_human:23.24G
```

This instance is managed with Ansible. Not in producion yet.

It was running fine with Debian bullseye, then we re-deployed it on a
bookworm VM. On this new host, Redis crashes every two hours roughly:

```
# journalctl | grep redis | grep code=killed | tail
Oct 28 14:58:30 host systemd[1]: redis.service: Main process exited, 
code=killed, status=11/SEGV
Oct 28 16:44:24 host systemd[1]: redis.service: Main process exited, 
code=killed, status=11/SEGV
Oct 28 18:49:49 host systemd[1]: redis.service: Main process exited, 
code=killed, status=11/SEGV
Oct 28 21:07:28 host systemd[1]: redis.service: Main process exited, 
code=killed, status=11/SEGV
Oct 28 22:54:32 host systemd[1]: redis.service: Main process exited, 
code=killed, status=11/SEGV
Oct 29 00:39:06 host systemd[1]: redis.service: Main process exited, 
code=killed, status=11/SEGV
Oct 29 02:43:30 host systemd[1]: redis.service: Main process exited, 
code=killed, status=11/SEGV
```

Looking at the Redis log files, we see this kind of line, repeated
hundreds of times within a few seconds, before Redis finally crashes:

```
8:M 15 Oct 2023 01:55:55.811 # Out Of Memory allocating 24576 bytes!
```

First thing I did was to disable the RDB snapshot (set every hours in
our config), just to make sure it was not related. It was not, Redis
kept crashing.

Redis RAM usage is rather constant for us (from 22G to 24G), and on this
machine there's only mirrorbits+redis running. There's plenty of RAM
available, I monitored the RAM during a crash, and `free` reports around
37G of RAM available. So I don't think we're running out of RAM.

I checked what changed in the Redis package, between bullseye and
bookworm, and this commit stands out:

d/redis-server.service: harden systemd service file
https://salsa.debian.org/lamby/pkg-redis/-/commit/8fec88c1

I tried to revert the systemd unit file to the bullseye version, and
Redis worked again, no more crash. From there I re-enabled the changes
one by one, until I found the setting that causes the crash:

ProcSubset=pid

I'm not really knowledgeable regarding systemd hardening, but after
reading the doc, it seems pretty clear that this setting is
questionable, and probably shouldn't be enabled.

Quoting systemd.exec(5)`:

If "pid", all files and directories not directly associated with process
management and introspection are made invisible in the /proc/ file
system configured for the unit's processes. [...] Note that Linux
exposes various kernel APIs via /proc/, which are made unavailable with
this setting. Since these APIs are used frequently this option is useful
only in a few, specific cases, and is not suitable for most non-trivial
programs.

At this point I think there's enough information to support disabling
ProcSubset=pid. Please tell me if you need more information, since the
issue is reproducible, it's easy for me to provide more logs.

Thanks in advance!

Arnaud

Bug#1050769: dh-cargo: should provide a build() method

[duck]

Quack,

Sorry for the lag, I really lacked time and energy recently but I'll try 
to upload a fix soon.


On 2023-10-07 04:09, Jeremy Bícha wrote:

No, greetd needs to build itself correctly regardless of whether there
are helper functions available.


You're right and I did not realize nocheck would be used for real in 
this package. I never saw this as a perfect solution but until debcargo 
implements what's needed that seemed fine.



https://salsa.debian.org/debian/greetd/-/merge_requests/4


It looks fine but that's precisely what I wanted to avoid: I do not want 
to maintain the build steps and have to update the calls and flags when 
cargo or any other piece of tooling changes.
Maybe that won't change often but that's still silly to implement that 
in each and every leaf package and as a consequence there's no unified 
policy.

Unfortunately I do not have the bandwidth to propose debcargo changes.

So I guess I'll apply the patch you kindly provided but I'm thinking 
about handing over the maintainership of wlgreet and greetd to people 
who really have time to do it properly, or… maybe comaint.


Anyway, thanks for the report and patch everyone.
\_o<

--
Marc Dequènes

Bug#1054644: xfsprogs-udeb: causes D-I to fail, reporting errors about missing partition devices

[Anthony Iliopoulos]

On Sun, Oct 29, 2023 at 09:02:01PM +0100, Philip Hands wrote:
> Philip Hands  writes:
> 
> > Anthony Iliopoulos  writes:
> > ...
> >> Yeap it is due to nrext64, I've submitted a patch to grub (should have
> >> cc'ed linux-xfs..)
> >>
> >> https://lore.kernel.org/grub-devel/20231026095339.31802-1-ail...@suse.com/
> >
> > That certainly seems to fix this bug.
> 
> ... but sadly that may not be the end of the story.
> 
> I've persuaded D-I to use the patched grub version, and when testing it,
> it now gets past the previous failure to complete the install, but then
> fails to boot after the first reboot, as seen here:
> 
>   https://openqa.debian.net/tests/200160#step/_console_wait_login/7
> 
> where it drops to the 'grub rescue>' prompt, complaining that:
> 
>   error: file `/boot/grub/i386-pc/normal.mod' not found.
> 
> if one types `ls (hd0,msdos1)/boot/grub/i386-pc` at that rescue prompt,
> it lists the files up to msdospart.mod and then says:
> 
>   error: invalid XFS directory entry.
> 
> (BTW the directory seemed fine before the reboot, because I listed it)

This issue exists independently of the large extent counter, and it is
related to grub commit ef7850c75 ("fs/xfs: Fix issues found while
fuzzing the XFS filesystem"). That's actually the issue described in
#1051543.

There's a proposed fix at [1], and it works as expected with that patch
applied.

Regards,
Anthony

[1] https://lore.kernel.org/grub-devel/20231018030347.36174-1-n...@vault24.org/

Bug#1055038: libreoffice-dictionaries: Please enable Esperanto hunspell dict, hyphenation and thesaurus packages.

[Agustin Martin]

Source: libreoffice-dictionaries
Version: 1:7.5.0-1
Severity: wishlist

Hi, Rene and Mattia

Please enable Esperanto stuff from libreoffice dictionaries. This
stuff was added in 2021

https://gerrit.libreoffice.org/c/dictionaries/+/110415

In particular, hunspell dict is an hunspell dict using real hunspell
capabilities. It should work far better that previous myspell-eo,
derived from ispell Esperanto dictionary and limited to pure myspell
capabilities. There were no previous packages for hyphenation patterns
and thesaurus but while we are at this, ...

I am attaching a diff with what seems to me the required changes for
Esperanto stuff to be enabled.

Current myspell-eo conflicts with hunspell-eo, so only required
coordination is to upload a new eo-spell package with myspell-eo made
a transitional package once lo-dicts provide this eo stuff.

Regards,

-- 
Agustin
From 7e1947c35d94594221e62d0cda65e367a4d287ee Mon Sep 17 00:00:00 2001
From: Agustin Martin Domingo 
Date: Sun, 29 Oct 2023 23:51:02 +0100
Subject: [PATCH] Enable esperanto hunspell dict, hyphenation and thesaurus
 packages.

---
 debian/control   | 42 ++
 debian/copyright |  4 
 debian/helper.py |  1 +
 debian/list.json | 15 +++
 debian/rules.install |  4 
 5 files changed, 66 insertions(+)

diff --git a/debian/control b/debian/control
index 9b6f375..193dcb8 100644
--- a/debian/control
+++ b/debian/control
@@ -486,6 +486,48 @@ Description: English (GB) dictionary for hunspell
  terminal interface using Curses library, an Ispell pipe interface and a
  LibreOffice UNO module.
 
+Package: hyphen-eo
+Architecture: all
+Multi-Arch: foreign
+Depends: dictionaries-common, ${misc:Depends}
+Suggests: libreoffice-writer
+Provides: hyphen-hyphenation-patterns, hyphen-hyphenation-patterns-eo
+Description: Esperanto hyphenation patterns
+ This package contains the Esperanto hyphenation patterns.
+ .
+ You can use these patterns with programs which take advantage of libhyphen,
+ like LibreOffice.
+
+Package: hunspell-eo
+Architecture: all
+Multi-Arch: foreign
+Depends: dictionaries-common, ${misc:Depends}, ${hunspell:Depends}
+Suggests: hunspell, libreoffice-writer
+Provides: hunspell-dictionary, hunspell-dictionary-eo
+Breaks: myspell-eo (<< 2.1.2000.02.25-62)
+Replaces: myspell-eo (<< 2.1.2000.02.25-62)
+Description: Esperanto dictionary for hunspell
+ This is the Esperanto dictionary for use with the hunspell
+ spellchecker.
+ .
+ Hunspell is a spell checker and morphological analyzer library and program
+ designed for languages with rich morphology and complex word compounding or
+ character encoding. It is based on MySpell and features an Ispell-like
+ terminal interface using Curses library, an Ispell pipe interface and a
+ LibreOffice UNO module.
+
+Package: mythes-eo
+Architecture: all
+Multi-Arch: foreign
+Depends: dictionaries-common, ${misc:Depends}
+Suggests: libreoffice-writer
+Provides: mythes-thesaurus, mythes-thesaurus-eo
+Description: Esperanto Thesaurus for LibreOffice
+ Libreoffice is a full-featured office productivity suite that provides a
+ near drop-in replacement for Microsoft(R) Office.
+ .
+ This package contains the Esperanto thesaurus for LibreOffice.
+
 Package: hyphen-es
 Architecture: all
 Multi-Arch: foreign
diff --git a/debian/copyright b/debian/copyright
index 82fcc87..1fc4c84 100644
--- a/debian/copyright
+++ b/debian/copyright
@@ -187,6 +187,10 @@ License: custom1
  % Please contact the TUGboat editorial staff 
  % for corrections and omissions.
 
+Files: dictionaries/eo/*
+Copyright: Artur Trzewik 
+License: GPL-2+
+
 Files: dictionaries/es/*
 Copyright: Santiago Bosio 
 License: GPL-3+ or LGPL-3+ or MPL-1.1+
diff --git a/debian/helper.py b/debian/helper.py
index 9436a1e..7f3c471 100755
--- a/debian/helper.py
+++ b/debian/helper.py
@@ -68,6 +68,7 @@ breaks_replaces = {
  "hunspell-bg": ("myspell-bg", '<<', '4.1-5'),
  "hunspell-en-gb": ("myspell-en-gb", '<<', "1:5.0.1+dfsg-1"),
  "hunspell-en-za": ("myspell-en-za", '<<', "1:5.0.1+dfsg-1"),
+ "hunspell-eo": ("myspell-eo", '<<', "2.1.2000.02.25-62"),
  "hunspell-hr": ('myspell-hr', '<<', '1:6.0.3-2'),
  "hunspell-it": ("myspell-it", '<<', "1:5.0.1+dfsg-1"),
  "hunspell-kmr": ('myspell-ku', '<<', '1:5.1.3-2'),
diff --git a/debian/list.json b/debian/list.json
index 859366e..7b325f2 100644
--- a/debian/list.json
+++ b/debian/list.json
@@ -232,6 +232,21 @@
 ],
 "name": "English (GB)"
 },
+{
+"639-1": "eo",
+"code": "eo",
+"hunspell": [
+"eo.aff",
+"eo.dic"
+],
+"hyphen": [
+"hyph_eo.dic"
+],
+"mythes": [
+"th_eo.dat"
+],
+"name": "Esperanto"
+},
 {
 "639-1": "es",
 "code": "es",
diff --git a/debian/rules.install b/debian/rules.install
index 2233111..d08a234 100644
--- a/debian/rules.install
+++ b/debian/rules.install
@@ -50,6 +50,10 @@ 

Bug#1055037: debbugsconfig fails due to missing /usr/share/doc/debbugs/examples/text

[Ian Kelling]

Package: debbugs
Version: 2.6.0

Steps to reproduce:

# debbugsconfig 
cp: cannot stat '/usr/share/doc/debbugs/examples/text': No such file or 
directory
No such file or directory at /usr/sbin/debbugsconfig line 82.


Workaround:

gunzip /usr/share/doc/debbugs/examples/text.gz

Bug#1033548: 02:00 timers dont run in DST transition night

[Michael Biebl]

Control: forwarded -1 https://github.com/systemd/systemd/issues/5595

I think the above upstream issue pretty much describes what you are 
seeing, so marking as forwarded accordingly.


Michael


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1042029: graph-tool: FTBFS: collect2: fatal error: ld terminated with signal 9 [Killed]

[Jerome BENOIT]

Hi all,
I downgraded the severity to normal as this issue is before all
a resource issue. I have no problem to build it on a 24 CPUs amd64 box
with 64 GB of RAM (and with ~ 4/3 of 64 GB of SWAP).
Please keep in mind that graph-tool is scientific tool for big-data,
so the choice of the optimization option is relevant.
Best wishes, Jerome
--
Jerome BENOIT | calculus+at-rezozer^dot*net
https://qa.debian.org/developer.php?login=calcu...@rezozer.net
AE28 AE15 710D FF1D 87E5  A762 3F92 19A6 7F36 C68B


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1055010: golang-github-nats-io-nkeys: CVE-2023-46129

[Mathias Gibbens]

Control: block 1055011 by 1055010

  I've pushed the packaging updates for the latest release to salsa,
but the fix introduces a regression in golang-github-nats-io-jwt, which
I have reported upstream at https://github.com/nats-io/jwt/issues/211.

Mathias


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

Bug#717778: checkinstall: mkdir -p fails (fstrans broken again?)

[Stephen Gelman]

 Sorry for the delay, I uploaded checkinstall 1.6.2+git20170426.d24a630-4
which has this fix.

Stephen

On Oct 23, 2023 at 9:58:53 AM, Stephen Gelman  wrote:

> It’s maintained, however the upstream no longer exists so I need to vet
> any patches myself. I will take a look at the provided patch and get it
> uploaded!
>
> Stephen
>
> On Oct 20, 2023 at 8:56:31 AM, Siddh Raman Pant  wrote:
>
>> Is the package no longer maintained? If it is, it should be removed from
>> the repo.
>>
>> It is 2023, and checkinstall is still broken.
>>
>> Thanks,
>> Siddh
>>
>> On Sat, 02 Jul 2022 02:18:35 + Geoffrey Hausheer <
>> debianbug...@pblue.org> wrote:
>>
>> Package: checkinstall
>>
>> Version: 1.6.2+git20170426.d24a630-2
>>
>> Followup-For: Bug #717778
>>
>> X-Debbugs-Cc: debianbug...@pblue.org
>>
>>
>> It appears that the root of this issue may be in instw_setpathrel
>>
>> Specifically, the 'stat' command that is used to get the length of a
>> symlink should
>>
>> be 'lstat' instead.
>>
>>
>> Here is a 1 line-patch that addressed the issue for me:
>>
>>
>> --- a/installwatch/installwatch.c
>>
>> +++ b/installwatch/installwatch.c
>>
>> @@ -1691,7 +1691,7 @@
>>
>>   if ( dirfd == AT_FDCWD ) return instw_setpath(instw, relpath);
>>
>>
>>
>>   snprintf(proc_path, PROC_PATH_LEN, "/proc/self/fd/%d", dirfd);
>>
>> - if(true_stat(proc_path, ) == -1)
>>
>> + if(true_lstat(proc_path, ) == -1)
>>
>>   goto out;
>>
>>   if(!(newpath = malloc(s.st_size+strlen(relpath)+2)))
>>
>>   goto out;
>>
>>
>>
>>
>> -- System Information:
>>
>> Debian Release: 11.3
>>
>>   APT prefers stable-updates
>>
>>   APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500,
>> 'stable')
>>
>> Architecture: amd64 (x86_64)
>>
>>
>> Kernel: Linux 5.10.67-zfs (SMP w/4 CPU threads)
>>
>> Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
>> TAINT_UNSIGNED_MODULE
>>
>> Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
>>
>> Shell: /bin/sh linked to /bin/dash
>>
>> Init: unable to detect
>>
>>
>> Versions of packages checkinstall depends on:
>>
>> ii  dpkg-dev1.20.10
>>
>> ii  file1:5.39-3
>>
>> ii  libc6   2.31-13+deb11u3
>>
>> ii  sensible-utils  0.0.14
>>
>>
>> Versions of packages checkinstall recommends:
>>
>> ii  make  4.3-4.1
>>
>>
>> Versions of packages checkinstall suggests:
>>
>> ii  gettext  0.21-4
>>
>>
>> -- Configuration Files:
>>
>> /etc/checkinstallrc changed [not included]
>>
>>
>> -- no debconf information
>>
>>
>>
>>

Bug#1055036: bookworm-pu: package crmsh/4.4.1-1+deb12u1

[Valentin Vidic]

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

[ Reason ]
As reported in #1042448, crmsh has a regression in the bookworm
release if the command is run by a non-root user.

[ Impact ]
Running the command as non-root user results in a permission error
while in Debian 11 this worked correctly:
PermissionError: [Errno 1] Operation not permitted: '/var/log/crmsh/crmsh.log'

[ Tests ]
Updated package was tested with autopkgtest and manually to check if the
permissions error is handled correctly by the command.

[ Risks ]
The change is simple and applied in the upstream and unstable
package for a while now.

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

[ Changes ]
Log file is now created by the postinst with the correct permissions
and the code is updated to not fail if the owner of the log file
cannot be updated (as in the case of non-root user).


diff -Nru crmsh-4.4.1/debian/changelog crmsh-4.4.1/debian/changelog
--- crmsh-4.4.1/debian/changelog2023-03-03 22:48:41.0 +0100
+++ crmsh-4.4.1/debian/changelog2023-10-29 20:46:13.0 +0100
@@ -1,3 +1,10 @@
+crmsh (4.4.1-1+deb12u1) bookworm; urgency=medium
+
+  * d/postinst: create a logging directory (Closes: #1042448)
+  * d/patches: add patch for log file error
+
+ -- Valentin Vidic   Sun, 29 Oct 2023 20:46:13 +0100
+
 crmsh (4.4.1-1) unstable; urgency=medium
 
   [ Bas Couwenberg ]
diff -Nru crmsh-4.4.1/debian/control crmsh-4.4.1/debian/control
--- crmsh-4.4.1/debian/control  2023-03-03 22:46:48.0 +0100
+++ crmsh-4.4.1/debian/control  2023-10-29 20:46:13.0 +0100
@@ -43,6 +43,7 @@
 Breaks: pacemaker (<< 1.1.12)
 Suggests:
  bash-completion,
+ cluster-glue,
  csync2,
  dmidecode,
  fdisk | util-linux (<< 2.29.2-3~),
diff -Nru crmsh-4.4.1/debian/crmsh.postinst crmsh-4.4.1/debian/crmsh.postinst
--- crmsh-4.4.1/debian/crmsh.postinst   1970-01-01 01:00:00.0 +0100
+++ crmsh-4.4.1/debian/crmsh.postinst   2023-10-29 20:46:13.0 +0100
@@ -0,0 +1,46 @@
+#!/bin/sh
+# postinst script for crmsh
+#
+# see: dh_installdeb(1)
+
+set -e
+
+# summary of how this script can be called:
+#*  `configure' 
+#*  `abort-upgrade' 
+#*  `abort-remove' `in-favour' 
+#  
+#*  `abort-deconfigure' `in-favour'
+#`removing'
+#   
+# for details, see http://www.debian.org/doc/debian-policy/ or
+# the debian-policy package
+#
+
+case "$1" in
+configure)
+mkdir -p /var/log/crmsh
+chown hacluster:haclient /var/log/crmsh
+chmod 0775 /var/log/crmsh
+
+touch /var/log/crmsh/crmsh.log
+chown hacluster:haclient /var/log/crmsh/crmsh.log
+chmod 0664 /var/log/crmsh/crmsh.log
+;;
+
+abort-upgrade|abort-remove|abort-deconfigure)
+
+;;
+
+*)
+echo "postinst called with unknown argument \`$1'" >&2
+exit 1
+;;
+esac
+
+# dh_installdeb will replace this with shell code automatically
+# generated by other debhelper scripts.
+
+#DEBHELPER#
+
+exit 0
diff -Nru crmsh-4.4.1/debian/crmsh.postrm crmsh-4.4.1/debian/crmsh.postrm
--- crmsh-4.4.1/debian/crmsh.postrm 1970-01-01 01:00:00.0 +0100
+++ crmsh-4.4.1/debian/crmsh.postrm 2023-10-29 20:46:13.0 +0100
@@ -0,0 +1,41 @@
+#!/bin/sh
+# postrm script for crmsh
+#
+# see: dh_installdeb(1)
+
+set -e
+
+# summary of how this script can be called:
+#*  `remove'
+#*  `purge'
+#*  `upgrade' 
+#*  `failed-upgrade' 
+#*  `abort-install'
+#*  `abort-install' 
+#*  `abort-upgrade' 
+#*  `disappear' 
+#  
+# for details, see https://www.debian.org/doc/debian-policy/ or
+# the debian-policy package
+
+
+case "$1" in
+purge)
+rm -rf /var/log/crmsh
+;;
+
+remove|upgrade|failed-upgrade|abort-install|abort-upgrade|disappear)
+;;
+
+*)
+echo "postrm called with unknown argument \`$1'" >&2
+exit 1
+;;
+esac
+
+# dh_installdeb will replace this with shell code automatically
+# generated by other debhelper scripts.
+
+#DEBHELPER#
+
+exit 0
diff -Nru crmsh-4.4.1/debian/patches/0019-Fix-log-file-error.patch 
crmsh-4.4.1/debian/patches/0019-Fix-log-file-error.patch
--- crmsh-4.4.1/debian/patches/0019-Fix-log-file-error.patch1970-01-01 
01:00:00.0 +0100
+++ crmsh-4.4.1/debian/patches/0019-Fix-log-file-error.patch2023-10-29 
20:46:13.0 +0100
@@ -0,0 +1,52 @@
+From b4abe21d2fd55ced0f56baff5c4892a4826aa0f7 Mon Sep 17 00:00:00 2001
+From: nicholasyang 
+Date: Tue, 25 Oct 2022 13:28:40 +0800
+Subject: [PATCH] fix: log: fail to open log file even if user is in haclient
+ group (bsc#1204670)
+
+The file had been created 

Bug#1054286: bookworm-pu: package python-cogent/2023.2.12a1+dfsg-2+deb12u1

[Santiago Vila]

El 29/10/23 a las 20:11, Adam D. Barratt escribió:

Flagged for rejection.


Thank you!


Continuing to use this bug is fine, but please send an updated debdiff
to it matching what you upload.


Ok, I'm attaching the updated debdiff here.

Everything is explained in the changelog.

Thanks.diff -Nru python-cogent-2023.2.12a1+dfsg/debian/changelog 
python-cogent-2023.2.12a1+dfsg/debian/changelog
--- python-cogent-2023.2.12a1+dfsg/debian/changelog 2023-02-24 
14:18:01.0 +0100
+++ python-cogent-2023.2.12a1+dfsg/debian/changelog 2023-10-29 
21:45:00.0 +0100
@@ -1,3 +1,14 @@
+python-cogent (2023.2.12a1+dfsg-2+deb12u1) bookworm; urgency=medium
+
+  * Team upload.
+  * Drop old patch fix-build-on-single-cpu-systems.patch, as it was
+disabling the affected tests for everybody.
+  * Add new patch skip-parallel-tests-on-single-cpu-systems.patch,
+where the tests are only skipped when the system has a single CPU.
+Closes: #1030885.
+
+ -- Santiago Vila   Sun, 29 Oct 2023 21:45:00 +0100
+
 python-cogent (2023.2.12a1+dfsg-2) unstable; urgency=medium
 
   * Restrict to 64 bit architectures
diff -Nru 
python-cogent-2023.2.12a1+dfsg/debian/patches/fix-build-on-single-cpu-systems.patch
 
python-cogent-2023.2.12a1+dfsg/debian/patches/fix-build-on-single-cpu-systems.patch
--- 
python-cogent-2023.2.12a1+dfsg/debian/patches/fix-build-on-single-cpu-systems.patch
 2023-02-24 14:18:01.0 +0100
+++ 
python-cogent-2023.2.12a1+dfsg/debian/patches/fix-build-on-single-cpu-systems.patch
 1970-01-01 01:00:00.0 +0100
@@ -1,59 +0,0 @@
-Author:: Santiago Vila 
-Last-Upate: Wed, 8 Feb 2023 19:40:13 +0100
-Bug-Debian: https://bugs.debian.org/1030885
-Description: Skip tests that are failing on single-cpu systems
-
 a/tests/test_app/test_evo.py
-+++ b/tests/test_app/test_evo.py
-@@ -2,7 +2,7 @@ import pathlib
- 
- from os.path import dirname, join
- from tempfile import TemporaryDirectory
--from unittest import TestCase, main
-+from unittest import TestCase, main, skip
- from unittest.mock import MagicMock
- 
- from numpy.testing import assert_allclose, assert_raises
-@@ -854,6 +854,7 @@ class TestBootstrap(TestCase):
- # correct message being relayed
- self.assertTrue("ValueError: '-' at" in result.message)
- 
-+@skip("Does not work on single-cpu systems")
- def test_bstrap_parallel(self):
- """exercising bootstrap with parallel"""
- aln = load_aligned_seqs(join(data_dir, "brca1.fasta"), moltype="dna")
 a/tests/test_util/test_parallel.py
-+++ b/tests/test_util/test_parallel.py
-@@ -2,7 +2,7 @@ import multiprocessing
- import sys
- import time
- 
--from unittest import TestCase, main, skipIf
-+from unittest import TestCase, main, skipIf, skip
- 
- import numpy
- 
-@@ -35,6 +35,7 @@ def check_is_master_process(n):
- 
- 
- class ParallelTests(TestCase):
-+@skip("Does not work on single-cpu systems")
- def test_create_processes(self):
- """Procressor pool should create multiple distingue processes"""
- max_worker_count = multiprocessing.cpu_count() - 1
-@@ -45,6 +46,7 @@ class ParallelTests(TestCase):
- self.assertEqual(sorted(list(result_values)), index)
- self.assertEqual(len(set(result_processes)), max_worker_count)
- 
-+@skip("Does not work on single-cpu systems")
- def test_random_seeding(self):
- """Random seed should be set every function call"""
- # On Windows process ids are not guaranteed to be 
sequential(1,2,3,4...)
-@@ -56,6 +58,7 @@ class ParallelTests(TestCase):
- self.assertEqual(result1[0], result2[0])
- self.assertNotEqual(result1, result2)
- 
-+@skip("Does not work on single-cpu systems")
- @skipIf(sys.version_info[1] < 7, "method exclusive to Python 3.7 and 
above")
- def test_is_master_process(self):
- """
diff -Nru python-cogent-2023.2.12a1+dfsg/debian/patches/series 
python-cogent-2023.2.12a1+dfsg/debian/patches/series
--- python-cogent-2023.2.12a1+dfsg/debian/patches/series2023-02-24 
14:18:01.0 +0100
+++ python-cogent-2023.2.12a1+dfsg/debian/patches/series2023-10-29 
21:45:00.0 +0100
@@ -2,4 +2,4 @@
 fix_interpreter.patch
 remove-jupyter-sphinx.patch
 ignore_tests_accessing_network.patch
-fix-build-on-single-cpu-systems.patch
+skip-parallel-tests-on-single-cpu-systems.patch
diff -Nru 
python-cogent-2023.2.12a1+dfsg/debian/patches/skip-parallel-tests-on-single-cpu-systems.patch
 
python-cogent-2023.2.12a1+dfsg/debian/patches/skip-parallel-tests-on-single-cpu-systems.patch
--- 
python-cogent-2023.2.12a1+dfsg/debian/patches/skip-parallel-tests-on-single-cpu-systems.patch
   1970-01-01 01:00:00.0 +0100
+++ 
python-cogent-2023.2.12a1+dfsg/debian/patches/skip-parallel-tests-on-single-cpu-systems.patch
   2023-10-29 21:45:00.0 +0100
@@ -0,0 +1,73 @@
+Author: Santiago Vila 
+Last-Update: 2023-10-28
+Bug-Debian: https://bugs.debian.org/1030885
+Description: Skip parallel tests 

Bug#1053301: udev.postinst removes valid /etc/rc*.d/ symlinks

[Matthias Geiger]

On Thu, 05 Oct 2023 16:31:00 +0100 Luca Boccassi  wrote:
> Control: severity -1 minor
>
> On Wed, 4 Oct 2023 22:00:06 +0100 Mark Hindley 
> wrote:
> > Control: tags -1 patch
> > Control: affects -1 initscripts
> > Control: severity -1 serious
> > Justification: Breaks unrelated packages, breaks non-systemd boot
> >
> > Michael,
> >
> > Please find a patch below that addresses this issue in my test setup.
> I can
> > offer to NMU if you would like?
> >
> > I have provided an easy means to reproduce the bug and a clear
> justfication for
> > why I think this is an RC bug. If you disagree, please explain why,
> rather than
> > just changing the severity. Thanks.
>
> If you want to see your changes merged, I would recommend to stop
> playing games with severity and send a MR on Salsa instead. It will be
> quicker, easier and much more effective.
>
> --
> Kind regards,

> Luca Boccassi

Created https://salsa.debian.org/systemd-team/systemd/-/merge_requests/219 .

I hope this gets resolved soon so my openRC system gets unbroken.

best,

--
Matthias Geiger 
Debian Maintainer
"Freiheit ist immer Freiheit des anders Denkenden" -- Rosa Luxemburg



OpenPGP_0x18BD106B3B6C5475.asc
Description: OpenPGP public key


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#958682: node-jsonld: Remove dependency to node-request

[Jonas Smedegaard]

Quoting Praveen Arimbrathodiyil (2023-10-29 18:10:08)
> On Fri, 31 Dec 2021 13:17:07 +0100 Yadd  wrote:
> > updating node-jsonld is enough to fix this issue:
> 
> Hi Jonas,
> 
> Are you planning to update node-jsonld?
> 
> > Else we can simply remove this package from Debian since it seems 
> > useless (no reverse dependencies).
> 
> This is blocking removal of deprecated node-request.

Yes, I still want to work on node-jsonld - I will make time to look at
this soon...

 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/
 * Sponsorship: https://ko-fi.com/drjones

 [x] quote me freely  [ ] ask before reusing  [ ] keep private

signature.asc
Description: signature

Bug#958692: node-matrix-js-sdk: Remove dependency to node-request

[Jonas Smedegaard]

Quoting Praveen Arimbrathodiyil (2023-10-29 18:13:55)
> On Fri, 24 Apr 2020 13:52:39 +0200 y...@debian.org wrote:
> > Upstream has deprecated node-request:
> > https://github.com/request/request/issues/3142
> > 
> > It can be replaced by node-got 
> > 
> > 
> 
> Hi Jonas, Hubert,
> 
> Are you planning to update matrix-js-sdk? We'd like to remove deprecated 
> node-request from the archive and this package is a blocker.

I have no interest in matrix-js-sdk.

 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/
 * Sponsorship: https://ko-fi.com/drjones

 [x] quote me freely  [ ] ask before reusing  [ ] keep private

signature.asc
Description: signature

Bug#1054914: orthanc-dicomweb: An unknown command in CMakeLists.txt encountered while attempting to build the orthanc-dicomweb_1.15 package.

[Andreas Tille]

Hi Israel,

Am Sat, Oct 28, 2023 at 03:01:58PM + schrieb Komolehin Israel Timilehin:
> 
> During the build process, I encountered the following error:
> 
> CMake Error at CMakeLists.txt:208 (DefineSourceBasenameForTarget):
>   Unknown CMake command "DefineSourceBasenameForTarget".
> This error seems to be related to an unknown CMake command used in the 
> CMakeLists.txt file.

I confirm I can reproduce the same error with latest upstream
version[1].  I really hope Sebastian can clarify this.

Kind regards
Andreas.


[1] https://salsa.debian.org/med-team/orthanc-dicomweb/-/jobs/4867398#L2591 

-- 
http://fam-tille.de

Bug#1055035: ftp.debian.org: missing links on mirrors for contrib and non-free-firmware

[Lucas Nussbaum]

Package: ftp.debian.org
Severity: important

Hi,

On 2023-10-17, slurm-wlm-contrib was uploaded to bookworm-security.
Apparently it was the first ever security upload to contrib, and I
noticed there's a missing link in /pool from contrib to updates/contrib
(there are such links for main and non-free). The same issue is also
present for non-free-firmware.

See https://deb.debian.org/debian-security/pool/ or
http://security.debian.org/debian-security/pool/

The UDD patches importer chokes on this, that's how I noticed.

Best,

Lucas

Bug#1055022: bullseye-pu: package distro-info-data/0.51+deb11u5, distro-info/1.0+deb11u1

[stefanor]

Hi Adam (2023.10.29_19:17:58_+)
> It looks like you uploaded a binary-only build of distro-info-data,
> rather than including a source build:

Indeed, oops. Kill that, I'll do a source-only upload.

Stefano

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

Bug#1052863: krb5: FTBFS: dh_auto_test: error: cd build && make -j1 check "TESTSUITEFLAGS=-j1 --verbose" VERBOSE=1 returned exit code 2

[Lucas Nussbaum]

Hi,

I changed my setup slightly to use a hostname that resolves, and can
confirm this does not fail anymore.

I'll let you decide whether you want to keep this bug open (with a lower
severity) or not. I'm fine with either.

Lucas

Bug#1052748: mpi4py fails test_dynproc.TestDPM.testJoin: socket.gaierror: [Errno -2] Name or service not known

[Lucas Nussbaum]

Hi Drew,

On 28/09/23 at 13:31 +0200, Drew Parsons wrote:
> Source: mpi4py
> Followup-For: Bug #1052748
> Control: severity 1052748 important
> Control: tags 1052748 moreinfo 
> 
> I can't reproduce this error, and debci tests at
> https://ci.debian.net/packages/m/mpi4py/ continue to pass
> So I'm downgrading severity.
> 
> I figure there are two possibilities
> - it was a transitory error related to some other library transition
> - or it's triggered by the network configuration on your test system.
> 
> For instance, https://github.com/mpi4py/mpi4py/issues/240 was
> triggered by a network configured with IPV6 only. But that issue
> should be resolved already in mpi4py 3.1.4
> 
> Your test log shows your network accesses http://127.0.0.1:12990
> so it is using IPv4.
> 
> Can you reproduce the testJoin error?

This was apparently caused by the build system using a hostname that
cannot be resolved. I fixed that, and mpi4py now builds fine. I'll let
you decide whether you want to keep this bug open or not.

Lucas

Bug#1055034: mysql-8.0: CVE-2023-22032 CVE-2023-22059 CVE-2023-22064 CVE-2023-22066 CVE-2023-22068 CVE-2023-22070 CVE-2023-22078 CVE-2023-22079 CVE-2023-22084 CVE-2023-22092 CVE-2023-22097 CVE-2023-22

[Salvatore Bonaccorso]

Source: mysql-8.0
Version: 8.0.34-1
Severity: grave
Tags: security upstream
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerabilities were published for mysql-8.0.

CVE-2023-22032[0]:
| Vulnerability in the MySQL Server product of Oracle MySQL
| (component: Server: Optimizer).  Supported versions that are
| affected are 8.0.34 and prior and  8.1.0. Easily exploitable
| vulnerability allows high privileged attacker with network access
| via multiple protocols to compromise MySQL Server.  Successful
| attacks of this vulnerability can result in unauthorized ability to
| cause a hang or frequently repeatable crash (complete DOS) of MySQL
| Server. CVSS 3.1 Base Score 4.9 (Availability impacts).  CVSS
| Vector: (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H).


CVE-2023-22059[1]:
| Vulnerability in the MySQL Server product of Oracle MySQL
| (component: Server: Optimizer).  Supported versions that are
| affected are 8.0.34 and prior and  8.1.0. Easily exploitable
| vulnerability allows low privileged attacker with network access via
| multiple protocols to compromise MySQL Server.  Successful attacks
| of this vulnerability can result in unauthorized ability to cause a
| hang or frequently repeatable crash (complete DOS) of MySQL Server.
| CVSS 3.1 Base Score 6.5 (Availability impacts).  CVSS Vector:
| (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H).


CVE-2023-22064[2]:
| Vulnerability in the MySQL Server product of Oracle MySQL
| (component: Server: Optimizer).  Supported versions that are
| affected are 8.0.34 and prior. Easily exploitable vulnerability
| allows high privileged attacker with network access via multiple
| protocols to compromise MySQL Server.  Successful attacks of this
| vulnerability can result in unauthorized ability to cause a hang or
| frequently repeatable crash (complete DOS) of MySQL Server. CVSS 3.1
| Base Score 4.9 (Availability impacts).  CVSS Vector:
| (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H).


CVE-2023-22066[3]:
| Vulnerability in the MySQL Server product of Oracle MySQL
| (component: InnoDB).  Supported versions that are affected are
| 8.0.34 and prior and  8.1.0. Easily exploitable vulnerability allows
| high privileged attacker with network access via multiple protocols
| to compromise MySQL Server.  Successful attacks of this
| vulnerability can result in unauthorized ability to cause a hang or
| frequently repeatable crash (complete DOS) of MySQL Server. CVSS 3.1
| Base Score 4.9 (Availability impacts).  CVSS Vector:
| (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H).


CVE-2023-22068[4]:
| Vulnerability in the MySQL Server product of Oracle MySQL
| (component: InnoDB).  Supported versions that are affected are
| 8.0.34 and prior and  8.1.0. Easily exploitable vulnerability allows
| high privileged attacker with network access via multiple protocols
| to compromise MySQL Server.  Successful attacks of this
| vulnerability can result in unauthorized ability to cause a hang or
| frequently repeatable crash (complete DOS) of MySQL Server. CVSS 3.1
| Base Score 4.9 (Availability impacts).  CVSS Vector:
| (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H).


CVE-2023-22070[5]:
| Vulnerability in the MySQL Server product of Oracle MySQL
| (component: Server: Optimizer).  Supported versions that are
| affected are 8.0.34 and prior and  8.1.0. Easily exploitable
| vulnerability allows high privileged attacker with network access
| via multiple protocols to compromise MySQL Server.  Successful
| attacks of this vulnerability can result in unauthorized ability to
| cause a hang or frequently repeatable crash (complete DOS) of MySQL
| Server. CVSS 3.1 Base Score 4.9 (Availability impacts).  CVSS
| Vector: (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H).


CVE-2023-22078[6]:
| Vulnerability in the MySQL Server product of Oracle MySQL
| (component: Server: Optimizer).  Supported versions that are
| affected are 8.0.34 and prior and  8.1.0. Easily exploitable
| vulnerability allows high privileged attacker with network access
| via multiple protocols to compromise MySQL Server.  Successful
| attacks of this vulnerability can result in unauthorized ability to
| cause a hang or frequently repeatable crash (complete DOS) of MySQL
| Server. CVSS 3.1 Base Score 4.9 (Availability impacts).  CVSS
| Vector: (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H).


CVE-2023-22079[7]:
| Vulnerability in the MySQL Server product of Oracle MySQL
| (component: Server: Optimizer).  Supported versions that are
| affected are 8.0.34 and prior. Easily exploitable vulnerability
| allows low privileged attacker with network access via multiple
| protocols to compromise MySQL Server.  Successful attacks of this
| vulnerability can result in unauthorized ability to cause a hang or
| frequently repeatable crash (complete DOS) of MySQL Server. CVSS 3.1
| Base Score 6.5 (Availability impacts).  CVSS Vector:
| (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H).


CVE-2023-22084[8]:
| 

Bug#1054904: Missing user data

[Chris Carr]

Hi,

After an eight year gap I'm afraid save files were not compatible anyway,
but please could you expand on what you mean by character history? Which
files are missing? Most personal stuff should be in ~/.angband/Angband,
which is not cleansed. I didn't have anything in /var/games/angband when I
tested the package, so curious to know what you lost.

Thanks

Chris

Bug#1054644: xfsprogs-udeb: causes D-I to fail, reporting errors about missing partition devices

[Philip Hands]

Philip Hands  writes:

> Anthony Iliopoulos  writes:
> ...
>> Yeap it is due to nrext64, I've submitted a patch to grub (should have
>> cc'ed linux-xfs..)
>>
>> https://lore.kernel.org/grub-devel/20231026095339.31802-1-ail...@suse.com/
>
> That certainly seems to fix this bug.

... but sadly that may not be the end of the story.

I've persuaded D-I to use the patched grub version, and when testing it,
it now gets past the previous failure to complete the install, but then
fails to boot after the first reboot, as seen here:

  https://openqa.debian.net/tests/200160#step/_console_wait_login/7

where it drops to the 'grub rescue>' prompt, complaining that:

  error: file `/boot/grub/i386-pc/normal.mod' not found.

if one types `ls (hd0,msdos1)/boot/grub/i386-pc` at that rescue prompt,
it lists the files up to msdospart.mod and then says:

  error: invalid XFS directory entry.

(BTW the directory seemed fine before the reboot, because I listed it)

This makes me wonder: Could it be that the code within the grub
components that get installed onto the disk also needs to be patched to
understand the newer directory structure, and without that it is unable
to read the whole directory, and thus fails to boot it?

Cheers, Phil.

P.S. If you want to try this for yourself, the test image used (that pulls in
the patched grub) is to be found here:

https://salsa.debian.org/philh/grub2/-/jobs/4865564/artifacts/file/debian/output/debian-202306XX+ABI~6.5.0~3+salsaci+20231029+21-amd64-gtkmini.iso

and adding `partman/default_filesystem=xfs` on the kernel command line
before booting into D-I will get it to default to using XFS.
-- 
Philip Hands -- https://hands.com/~phil


signature.asc
Description: PGP signature

Bug#1055033: evince: [Printing] Please add printing in a booklet

[Nicolas Patrois]

Package: evince
Version: 45.0-1
Severity: wishlist
Tags: upstream

Dear Maintainer,

I can print a document in a booklet with a well-known proprietary pdf reader, I
can also rearrange pages in a pdf in order to print it in a booklet (as booklet
imposer does) but I can’t tell evince to print directly a document in a
booklet.
Maybe it’s a GTK window dedicated to printing that should be enhanced, not
evince.

Yours,
Nicolas Patrois


-- System Information:
Debian Release: trixie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 5.16.0-6-686-pae (SMP w/3 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=fr_FR:fr:en_GB:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages evince depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.40.0-4
ii  evince-common45.0-1
ii  gconf-gsettings-backend [gsettings-backend]  3.2.6-8
ii  gsettings-desktop-schemas45.0-1
ii  libatk1.0-0  2.50.0-1
ii  libc62.37-12
ii  libcairo-gobject21.18.0-1
ii  libcairo21.18.0-1
ii  libevdocument3-4 45.0-1
ii  libevview3-3 45.0-1
ii  libgdk-pixbuf-2.0-0  2.42.10+dfsg-1+b1
ii  libglib2.0-0 2.78.1-1
ii  libgnome-desktop-3-2044.0-2
ii  libgtk-3-0   3.24.38-5
ii  libhandy-1-0 1.8.2-3
ii  libpango-1.0-0   1.51.0+ds-2
ii  libpangocairo-1.0-0  1.51.0+ds-2
ii  libsecret-1-00.21.1-1
ii  shared-mime-info 2.2-1

Versions of packages evince recommends:
ii  dbus-user-session [default-dbus-session-bus]  1.14.10-2
ii  dbus-x11 [dbus-session-bus]   1.14.10-2

Versions of packages evince suggests:
ii  gvfs   1.52.1-1
ii  nautilus-sendto3.8.6-4
ii  poppler-data   0.4.12-1
ii  unrar-nonfree [unrar]  3.3.6-2

-- debconf-show failed

Bug#1055027: Document workaround for potentially unusable pipewire-jack

[Paul Gevers]

Hi

On 29-10-2023 19:14, Nicholas D Steeves wrote:

When I switched to Pipewire for bookworm I learned that pipewire-jack
wasn't yet ready for general use due to broken sample rate
pass-through, as well as frequent Ardour hangs.  Thus I filed a bug
(#1054019), tested the proposed workaround, and Dylan Aïssi gave me
the ACK to document it.


If it's broken, instead of recommending bookworm-backports, can't we fix 
it in a point release?


Paul


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1055032: Please update to latest upstream version

[Jonathan Carter]

Package: python3-textual
Severity: normal
X-Debbugs-Cc: 

Dear maintainer,

The current version of python3-textual in Debian is quite out of date, and it's 
not possible to run newer textual apps with it anymore., Please upgrade to the 
latest upstream version (currenly (0.40.0) so that this package can be useful 
again.

thanks

-Jonathan



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

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

Bug#1055022: bullseye-pu: package distro-info-data/0.51+deb11u5, distro-info/1.0+deb11u1

[Adam D. Barratt]

On Sun, 2023-10-29 at 15:53 +0200, Stefano Rivera wrote:
> Bullseye version of #1055009.
> 
> [ Reason ]
> This is a regular distro-info-data update, adding Ubuntu 24.04 LTS.
> It includes some corrections to historical data, one of which affects
> the distro-info test-suite.
> 
> So, included is a coupled update of distro-info to expect the new
> values in its test-suite.

It looks like you uploaded a binary-only build of distro-info-data,
rather than including a source build:

distro-info-data_0.51+deb11u5_all.deb: trying to install to oldstable-new, but 
could not find source (distro-info-data 0.51+deb11u5)

and on the queued side:

Oct 29 10:47:55 processing /distro-info-data_0.58+deb12u1_source.changes
Oct 29 10:47:55 distro-info-data_0.58+deb12u1_source.changes processed 
successfully (uploader bdr...@debian.org)
Oct 29 10:47:56 processing /distro-info_1.5+deb12u1_source.changes
Oct 29 10:47:56 distro-info_1.5+deb12u1_source.changes processed successfully 
(uploader bdr...@debian.org)
Oct 29 14:04:43 processing /distro-info_1.0+deb11u1_source.changes
Oct 29 14:04:43 distro-info_1.0+deb11u1_source.changes processed successfully 
(uploader bdr...@debian.org)
Oct 29 14:04:44 processing /distro-info-data_0.51+deb11u5_amd64.changes
Oct 29 14:04:44 distro-info-data_0.51+deb11u5_amd64.changes processed 
successfully (uploader bdr...@debian.org)

Regards,

Adam

Bug#1054286: bookworm-pu: package python-cogent/2023.2.12a1+dfsg-2+deb12u1

[Adam D. Barratt]

On Sun, 2023-10-29 at 13:44 +0100, Santiago Vila wrote:
> Dear Release Managers:
> 
> Please reject the upload I made for bookworm.
> 
> Following the suggestion from Holger, I've fixed this issue
> in the optimal way in unstable:
> 
> https://tracker.debian.org/news/1474401/accepted-python-cogent-2023212a1dfsg-4-source-into-unstable/
> 
> and now I'd like to upload the same fix for bookworm
> using the "+deb12u1" version string.

Flagged for rejection.

> (Not sure if this release.debian.org bug should then be closed so
> that
> I submit it again, or it's better that we keep it open for the
> new upload, please do what is more convenient for you).
> 

Continuing to use this bug is fine, but please send an updated debdiff
to it matching what you upload.

Regards,

Adam

Bug#1041248: keepassxc: new upstream version

[Matthias Geiger]

I updated keepassxc to 2.7.6 and created the respective MRs 11,12 and 13 
at https://salsa.debian.org/debian/keepassxc.


The package builds and runs fine for me. I fixed a lot of minor stuff.

best,

werdahias

Bug#1055031: bookworm-pu: package mda-lv2/1.2.10-1+deb12u1

[Sebastian Ramacher]

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

[ Reason ]
LV2 plugins are supposed to be installed in /usr/lib/lv2 as these
plugins are also consumed by third-party software. mda-lv2 installed the
plugins in a multi-arch location and were unable to be found.

[ Impact ]
LV2 plugins provided by mda-lv2 is not found by some LV2 consuming
software packages.

[ Risks ]
The change is trivial.

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

[ Changes ]
With the updated version, lv2dir is set during the build to the correct
location. The same fix has been uploaded to unstable.

Cheers
-- 
Sebastian Ramacher
diff --git a/debian/changelog b/debian/changelog
index 7df9ad7..b02aed1 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+mda-lv2 (1.2.10-1+deb12u1) bookworm; urgency=medium
+
+  * debian/gbp.conf: Work in bookworm branch
+  * debian/rules: Fix LV2 plugin installation location (Closes: #1055029)
+
+ -- Sebastian Ramacher   Sun, 29 Oct 2023 19:49:22 +0100
+
 mda-lv2 (1.2.10-1) unstable; urgency=medium
 
   * New upstream version 1.2.10
diff --git a/debian/gbp.conf b/debian/gbp.conf
index 0a3b09a..b5f4317 100644
--- a/debian/gbp.conf
+++ b/debian/gbp.conf
@@ -1,3 +1,4 @@
 [DEFAULT]
 sign-tags = True
 pristine-tar = True
+debian-branch = bookworm
diff --git a/debian/rules b/debian/rules
index 87ee2a8..4744f87 100755
--- a/debian/rules
+++ b/debian/rules
@@ -9,5 +9,8 @@ CONFIG += strict
 %:
dh $@ --buildsystem=meson
 
+override_dh_auto_configure:
+   dh_auto_configure -- -Dlv2dir=/usr/lib/lv2
+
 # No tests available
 override_dh_auto_test:

Bug#1054919: kaccounts-providers: google authentication hang after username entry

[Alexis Murzeau]

Hi,

Thanks for your reply!

On 29/10/2023 18:30, Nicholas D Steeves wrote:

The webpage issue is maybe caused by the use of Qt webkit, using an older
UserAgent probably causes Google to offer an older login page that works with
Qt webkit.


That sounds plausible to me.  If that's the case then it seems like it
may be better to patch Qt webkit.  I wonder if this is a case where
whatever UserAgent Qt webkit validated is the one the package declares
(where it shouldn't be overridden for the general case), or if everybody
involved just forgot to update it?


As the UserAgent is required to make the login work, can it be added to the
package ?


Agreed, either Qt webkit should be fixed, or else kaccount-providers
should begin overriding UserAgent.  It's nice to see a Google issue that
we can fix on our side!

Best,
Nicholas



I'm not sure how Qt webkit works, but I guess it behaves like a old
chrome browser. I don't know if it uses a different user agent, but
maybe Google doesn't recognize that it doesn't support newer web stuff.

Qt 6 doesn't seem to have Qt webkit anymore, but QtWebEngine instead.
I guess signon-ui should move to QtWebEngine instead but sadly upstream
seems rather dead :(, the previous signon-ui release was more than 5
years ago.

That's in fact why I've opened a report on this package, it seemed to be
the more feasible and realistic solution.
It is a chance that google signon can still work :)

--
Alexis Murzeau
PGP: B7E6 0EBB 9293 7B06 BDBC  2787 E7BD 1904 F480 937F |

Bug#1055026: do not create web statistic for all language combinations

[Thomas Lange]

There's also the problem, that a lot of files are outdated.

After I removed some files for german manually I now see this:

https://www.debian.org/devel/website/stats/de.en.html
Last Modified: Sun, Oct 29 15:26:29 UTC 2023   Last Built: Sun, Oct 29 15:29:11 
UTC 2023

This was recreated today, but

https://www.debian.org/devel/website/stats/de.de.html
Zuletzt geändert: Dienstag den 13. Jun 2023 um 19:26:34 Uhr UTC   Zuletzt 
gebaut: Dienstag den 13. Jun 2023 um 22:59:06 Uhr UTC 

Similar for nl.nl.html and nl.de.html.


-- 
 Thomas

Bug#1054233: liblilv-0-0: Package does not follow FHS, it adds /usr/lib/$(DEB_HOST_MULTIARCH) to the --default-lv2-path waf configure option, see rules file, line 21.

[Sebastian Ramacher]

On 2023-10-29 17:45:56 +0100, Sebastian Ramacher wrote:
> On 2023-10-29 07:01:07 -0700, Erich Eickmeyer wrote:
> > Sebastian,
> > 
> > I'm fairly certian Robin Gareus made it quite clear what Jeremy was saying
> > in his reply:
> > 
> > >The LV2 FHS that Jeremy mention can be found at
> > >https://lv2plug.in/pages/filesystem-hierarchy-standard.html
> > >
> > >Now you may not like, or disagree with the official standard, but breaking
> > it is not acceptable. This affects various >3rd party software, notably
> > Reaper, Harrison Mixbus, Ardour and other non-free DAWs that expect LV2
> > plugins in >/usr/lib/lv2/
> 
> 
> 
> > >
> > >LV2s are to be installed $PREFIX/lib/lv2 (unrelated to $LIBDIR).
> > >Most LV2 plugin build systems use LV2DIR = $PREFIX/lib/lv2 for this.
> > 
> > This does divert from the standard location in which shared libraries are
> > expected to be located, but LV2 plugins, as you are aware, are not normal
> > shared libraries. If they cannot be found in /usr/lib/lv2, then it literally
> > breaks the functionality of several DAWs out there, including Ardour (which
> > we ship). Sure, users can always manually add the search path of
> > /usr/lib/$(DEB_HOST_MULTIARCH)/lv2 to the software, but that's an
> > unnecessary inconvenience.
> 
> lilv does not install LV2 plugins. If other packages abuse lilv's libdir
> as base to determine LV2DIR, those packages are buggy. As you explain
> above, it's not $libdir/lv2 but $prefix/lib/lv2 that's to be used.

FWIW, the only packages in Debian installing LV2 plugins in multi-arch
locations are mda-lv2 and naspro-bridges. Fixes for both have been
uploaded to unstable.

Cheers
-- 
Sebastian Ramacher

Bug#1055028: do not create po statistic for all language combinations

[Thomas Lange]

Package: www.debian.org

Currently we generate several hundereds of files in international/l10n/po/
A lot of them are around 2.2M big.

We have an overall of 8700 files in this directory.
Do we really need statistic like these? For e.g.
/international/l10n/po/de@hebrew
/international/l10n/po/sa.de.html

We should review if we really need all these files in there.

The directory currently needs 2.2 GB disk space.
-- 
regards Thomas

Bug#1055027: Document workaround for potentially unusable pipewire-jack

[Nicholas D Steeves]

Package: release-notes
Severity: normal
X-Debbugs-Cc: Utopia Maintenance Team 

Control: block 1054019 by -1

Hello,

When I switched to Pipewire for bookworm I learned that pipewire-jack
wasn't yet ready for general use due to broken sample rate
pass-through, as well as frequent Ardour hangs.  Thus I filed a bug
(#1054019), tested the proposed workaround, and Dylan Aïssi gave me
the ACK to document it.

After all, it's nice when release notes answer "Is $new_technology
ready to switch to, are there caveats, or do I need to wait for the
next Debian stable release" :)

I've prepared a draft in the following merge request, and I suspect it
needs edits before it's ready to merge:

  https://salsa.debian.org/ddp-team/release-notes/-/merge_requests/201

Thank you,
Nicholas

Bug#1053994: (no subject)

[Николай]

I sent a request to the linux kernel bugzilla.


https://bugzilla.kernel.org/show_bug.cgi?id=218085

Bug#1007559: [Pkg-clamav-devel] Bug#1007559: clamsmtp: please consider upgrading to 3.0 source format

[Sebastian Andrzej Siewior]

On October 28, 2023 1:05:06 PM GMT+02:00, Bastian Germann  
wrote:
>I am uploading a NMU to DELAYED/10 in order to fix this.
>Please find the debdiff attached.
Hi,

I am team clamav but I don't feel responsible for clamsmtp. The last upload was 
a NMU. That said, I don't mind if you reschudule it to 0-day.

-- 
Sebastian

Bug#1054919: kaccounts-providers: google authentication hang after username entry

[Nicholas D Steeves]

Version: 4:22.12.3-1
Control: tag -1 upstream confirmed

Hi,

Thank you for reporting this bug.

Alexis Murzeau  writes:

> To fix this, I've put this line in /etc/signon-ui/webkit-
> options.d/accounts.google.com.conf:
> UserAgent = Mozilla/5.0 (X11; Linux x86_64; rv:57.0) Gecko/20100101
> Firefox/77.0

I've tested this proposal, and it fixes Google signon for me.  This will
transitively fix things like kio-gdrive that are broken in bookworm; For
users of Google things, Bookworm's KDE is a poor user experience, or
"bad story", compared to GNOME.

> The webpage issue is maybe caused by the use of Qt webkit, using an older
> UserAgent probably causes Google to offer an older login page that works with
> Qt webkit.

That sounds plausible to me.  If that's the case then it seems like it
may be better to patch Qt webkit.  I wonder if this is a case where
whatever UserAgent Qt webkit validated is the one the package declares
(where it shouldn't be overridden for the general case), or if everybody
involved just forgot to update it?

> As the UserAgent is required to make the login work, can it be added to the
> package ?

Agreed, either Qt webkit should be fixed, or else kaccount-providers
should begin overriding UserAgent.  It's nice to see a Google issue that
we can fix on our side!

Best,
Nicholas


signature.asc
Description: PGP signature

Bug#1055026: do not create web statistic for all language combinations

[Thomas Lange]

Package: www.debian.org


Currently we generate nearly 700 html files in /devel/website/stats
most of them not needed and each around 2.5M big so we have 1.6GB data
there.

The web logs show that only the file in the native language and the
engish version is accessed. There are also no link to the other translations.

For example combinations like de.fr.html, fr.de.html are not needed.
I wonder why these are generated and I guess we could save a lot of
building time in 4webwml.

-- 
regards Thomas

Bug#958682: node-jsonld: Remove dependency to node-request

[Praveen Arimbrathodiyil]

On Fri, 31 Dec 2021 13:17:07 +0100 Yadd  wrote:

Hi,

updating node-jsonld is enough to fix this issue:


Hi Jonas,

Are you planning to update node-jsonld?

Else we can simply remove this package from Debian since it seems 
useless (no reverse dependencies).


This is blocking removal of deprecated node-request.


OpenPGP_0x8F53E0193B294B75.asc
Description: OpenPGP public key


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1055025: manpages-zh: environ(5) versus environ(7)

[Patrice Duroux]

Package: manpages-zh
Version: 1.6.4.0-1
Severity: minor

Dear Maintainer,

I discovered this section inconsistency about the 'environ' man page while
using https://manpages.debian.org/ that prioritizes environ(5) and so provides
the content with very few languages (all zh relatives). Forcing environ(7)
gives the result for some other languages then.

Regards,
Patrice


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

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

Bug#958692: node-matrix-js-sdk: Remove dependency to node-request

[Praveen Arimbrathodiyil]

On Fri, 24 Apr 2020 13:52:39 +0200 y...@debian.org wrote:

Upstream has deprecated node-request:
https://github.com/request/request/issues/3142

It can be replaced by node-got 





Hi Jonas, Hubert,

Are you planning to update matrix-js-sdk? We'd like to remove deprecated 
node-request from the archive and this package is a blocker.


thanks
Praveen


OpenPGP_0x8F53E0193B294B75.asc
Description: OpenPGP public key


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1054218: texlive-latex-base: pdflatex failures on big-endian architectures (s390x)

[Hilmar Preuße]

On 10/19/23 14:20, Stuart Prescott wrote:

Hi Stuart,


The unittests of the 'plastex' package run pdflatex to generate some
figures, and then extract the text from the figures to verify that
various implementation details of the package are working. These tests
pass on all release architectures except s390x. They also fail on ppc64.
The common feature of the failures is that the architecture is
big-endian.



I've got a patch from upstream, which /seems/ to solve the issue. 
Packages for PPC64 are here [1]. If you need packages for s390x, the 
debian.tar.xz and the dsc file are there too. Please be so kind to test 
on s390 too. Please be aware that simply copying the pdftex binary out 
of the package is not sufficient, the format file needs to re-generated 
too, better install the packages.


Hilmar

[1] https://www.beckmann.pro/~hille42/debian_1054218/
--
Testmail



OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1054657: transition: r-bioc-biocgenerics

[Andreas Tille]

Hi Graham,

Am Sun, Oct 29, 2023 at 02:57:01PM -0100 schrieb Graham Inggs:
> Hi Andreas
> 
> On Sun, 29 Oct 2023 at 04:33, Andreas Tille  wrote:
> > Can you confirm that packages uploaded to experimental can be moved in
> > one rush from experimental to unstable without extra uploads?
> 
> I don't think this has ever been possible.  The packages would need to
> be uploaded again to unstable, presumably at the appropriate
> dependency level in the transition.

Sorry, my question was probably confusing.  I was not talking about the
new packages.  I was talking about the 170 r-bioc-* packages.  If I
upload these to experimental, will it be necessary to upload these to
unstable again or can these be moved to unstable in one rush.  Also
interesting in this connection:  Will the tracker display the levels
of packages uploaded to experimental?
 
> Seeing these packages would be NEW, even if they were initially
> uploaded directly to unstable, they would likely still require
> source-only uploads for migration anyway.

I'm comfortable with doing source-only uploads of packages that have
passed NEW.  I'm not comfortable with uploading 170 packages twice -
once to experimmental and once again to unstable.  Given that all
this work has mainly ended up on my shoulders I would prefer to
upload directly to unstable and simply bear with the waiting time
in NEW.

> > Do you
> > have this process in mind after the moreinfo tag is removed?
> 
> No, after the NEW packages have cleared NEW and the moreinfo tag is
> removed, we'll consider a slot for the transition. 

But you just mentioned the tracker in your previous mail[1].

> We would like to
> avoid stalling the transition with multiple packages going through
> NEW, and putting pressure on FTP Masters by telling them a package is
> needed for a transition is not nice either.

I admit I personally see the bigger drawback on spending my time twice
on 170 packages than waiting for new packages.  Please explain (again)
the real drawback of a transition that was delayed due to waiting for
new packages in total by estimated (not verified) by about two weeks.

Kind regards
   Andreas.

[1] https://release.debian.org/transitions/html/r-api-bioc-3.18.html

-- 
http://fam-tille.de

Bug#1002901: node-request-capture-har is a wrapper around deprecated node-request

[Praveen Arimbrathodiyil]

On Fri, 31 Dec 2021 13:02:44 +0100 Yadd  wrote:

Package: node-request-capture-har
Version: 1.2.2-2
Severity: serious
Tags: upstream security
Justification: security
X-Debbugs-Cc: Debian Security Team 

node-request-capture-har is usable only as a wrapper around deprecated
node-request. Then it should be removed from Debian bookstorm.




yarnpkg 4.x in experimental no longer depends on this package. So once 
we reupload that to unstable, we can file rm request for this package.


We are pretty close to the unstable reupload 
https://lists.debian.org/debian-js/2023/10/msg00080.html


OpenPGP_0x8F53E0193B294B75.asc
Description: OpenPGP public key


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1054233: liblilv-0-0: Package does not follow FHS, it adds /usr/lib/$(DEB_HOST_MULTIARCH) to the --default-lv2-path waf configure option, see rules file, line 21.

[Sebastian Ramacher]

On 2023-10-29 07:01:07 -0700, Erich Eickmeyer wrote:
> Sebastian,
> 
> I'm fairly certian Robin Gareus made it quite clear what Jeremy was saying
> in his reply:
> 
> >The LV2 FHS that Jeremy mention can be found at
> >https://lv2plug.in/pages/filesystem-hierarchy-standard.html
> >
> >Now you may not like, or disagree with the official standard, but breaking
> it is not acceptable. This affects various >3rd party software, notably
> Reaper, Harrison Mixbus, Ardour and other non-free DAWs that expect LV2
> plugins in >/usr/lib/lv2/



> >
> >LV2s are to be installed $PREFIX/lib/lv2 (unrelated to $LIBDIR).
> >Most LV2 plugin build systems use LV2DIR = $PREFIX/lib/lv2 for this.
> 
> This does divert from the standard location in which shared libraries are
> expected to be located, but LV2 plugins, as you are aware, are not normal
> shared libraries. If they cannot be found in /usr/lib/lv2, then it literally
> breaks the functionality of several DAWs out there, including Ardour (which
> we ship). Sure, users can always manually add the search path of
> /usr/lib/$(DEB_HOST_MULTIARCH)/lv2 to the software, but that's an
> unnecessary inconvenience.

lilv does not install LV2 plugins. If other packages abuse lilv's libdir
as base to determine LV2DIR, those packages are buggy. As you explain
above, it's not $libdir/lv2 but $prefix/lib/lv2 that's to be used.

> I checked the salsa repo for liblilv (and another) and it seems as though
> /usr/lib/$(DEB_HOST_MULTIARCH)/lv2 is being intentionally set as the install
> location here, so this simply needs to be reverted. I can even set-up the
> pull request.

Please point me to the place where this is set as install location.

Cheers
-- 
Sebastian Ramacher

Bug#1054630: dgit - cant import llvm-toolchain-15.

[Ian Jackson]

Ian Jackson writes ("Re: Bug#1054630: dgit - cant import llvm-toolchain-15."):
> I'll work on some kind of fix.

I have a fix.  There's some minor reorganisation of the dsc import
code, to make my fix apply to whatever is wrong with the historical
info in the package changelog.  So I won't be backporting this right
away as a stable release update.  I will consider doing that after
it's been in testing for a while.

You should find that you can install the 11.4 .deb, which I intend
to upload later today, directly on whatever system you are using.
Or, build your own from the source; again, after I've uploaded.

Anyway, thanks for the report.

Regards,
Ian.

-- 
Ian JacksonThese opinions are my own.  

Pronouns: they/he.  If I emailed you from @fyvzl.net or @evade.org.uk,
that is a private address which bypasses my fierce spamfilter.

Bug#1052915: libdnf: FTBFS: dh_install: error: missing files, aborting

[Luca Boccassi]

Control: tags -1 pending

On Tue, 26 Sep 2023 15:28:47 +0200 Lucas Nussbaum 
wrote:
> Source: libdnf
> Version: 0.69.0-2
> Severity: serious
> Justification: FTBFS
> Tags: trixie sid ftbfs
> User: lu...@debian.org
> Usertags: ftbfs-20230925 ftbfs-trixie
> 
> Hi,
> 
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
> 
> 
> Relevant part (hopefully):
> > make[3]: Entering directory '/<>/build'
> > make[3]: Nothing to be done for 'preinstall'.
> > make[3]: Leaving directory '/<>/build'
> > Install the project...
> > /usr/bin/cmake -P cmake_install.cmake
> > -- Install configuration: "None"
> > -- Installing: /<>/debian/tmp/usr/lib/x86_64-linux-
gnu/pkgconfig/libdnf.pc
> > -- Installing:
/<>/debian/tmp/usr/include/libdnf/config.h
> > -- Installing:
/<>/debian/tmp/usr/include/libdnf/log.hpp
> > -- Installing:
/<>/debian/tmp/usr/include/libdnf/nevra.hpp
> > -- Installing:
/<>/debian/tmp/usr/include/libdnf/nsvcap.hpp
> > -- Installing: /<>/debian/tmp/usr/include/libdnf/dnf-
advisory.h
> > -- Installing: /<>/debian/tmp/usr/include/libdnf/dnf-
advisorypkg.h
> > -- Installing: /<>/debian/tmp/usr/include/libdnf/dnf-
advisoryref.h
> > -- Installing: /<>/debian/tmp/usr/include/libdnf/dnf-
db.h
> > -- Installing: /<>/debian/tmp/usr/include/libdnf/dnf-
conf.h
> > -- Installing: /<>/debian/tmp/usr/include/libdnf/dnf-
context.h
> > -- Installing: /<>/debian/tmp/usr/include/libdnf/dnf-
enums.h
> > -- Installing: /<>/debian/tmp/usr/include/libdnf/dnf-
goal.h
> > -- Installing: /<>/debian/tmp/usr/include/libdnf/dnf-
keyring.h
> > -- Installing: /<>/debian/tmp/usr/include/libdnf/dnf-
lock.h
> > -- Installing: /<>/debian/tmp/usr/include/libdnf/dnf-
package.h
> > -- Installing: /<>/debian/tmp/usr/include/libdnf/dnf-
packagedelta.h
> > -- Installing: /<>/debian/tmp/usr/include/libdnf/dnf-
repo-loader.h
> > -- Installing: /<>/debian/tmp/usr/include/libdnf/dnf-
rpmts.h
> > -- Installing: /<>/debian/tmp/usr/include/libdnf/dnf-
sack.h
> > -- Installing: /<>/debian/tmp/usr/include/libdnf/dnf-
reldep.h
> > -- Installing: /<>/debian/tmp/usr/include/libdnf/dnf-
reldep-list.h
> > -- Installing: /<>/debian/tmp/usr/include/libdnf/dnf-
repo.h
> > -- Installing: /<>/debian/tmp/usr/include/libdnf/dnf-
state.h
> > -- Installing: /<>/debian/tmp/usr/include/libdnf/dnf-
transaction.h
> > -- Installing: /<>/debian/tmp/usr/include/libdnf/dnf-
types.h
> > -- Installing: /<>/debian/tmp/usr/include/libdnf/dnf-
utils.h
> > -- Installing: /<>/debian/tmp/usr/include/libdnf/dnf-
version.h
> > -- Installing:
/<>/debian/tmp/usr/include/libdnf/libdnf.h
> > -- Installing: /<>/debian/tmp/usr/include/libdnf/hy-
goal.h
> > -- Installing: /<>/debian/tmp/usr/include/libdnf/hy-
nevra.h
> > -- Installing: /<>/debian/tmp/usr/include/libdnf/hy-
package.h
> > -- Installing: /<>/debian/tmp/usr/include/libdnf/hy-
packageset.h
> > -- Installing: /<>/debian/tmp/usr/include/libdnf/hy-
query.h
> > -- Installing: /<>/debian/tmp/usr/include/libdnf/hy-
repo.h
> > -- Installing: /<>/debian/tmp/usr/include/libdnf/hy-
selector.h
> > -- Installing: /<>/debian/tmp/usr/include/libdnf/hy-
subject.h
> > -- Installing: /<>/debian/tmp/usr/include/libdnf/hy-
types.h
> > -- Installing: /<>/debian/tmp/usr/include/libdnf/hy-
util.h

Uploaded NMU to DELAYED/5 fixing this issue with the attached debdiff.

-- 
Kind regards,
Luca Boccassi
diff -Nru libdnf-0.69.0/debian/changelog libdnf-0.69.0/debian/changelog
--- libdnf-0.69.0/debian/changelog	2023-01-08 09:08:51.0 +
+++ libdnf-0.69.0/debian/changelog	2023-10-29 15:57:28.0 +
@@ -1,3 +1,10 @@
+libdnf (0.69.0-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Move python3 modules from /usr/lib/local/ (Closes: #1052915)
+
+ -- Luca Boccassi   Sun, 29 Oct 2023 15:57:28 +
+
 libdnf (0.69.0-2) unstable; urgency=medium
 
   * Set myself to maintainer
diff -Nru libdnf-0.69.0/debian/python3-hawkey.install libdnf-0.69.0/debian/python3-hawkey.install
--- libdnf-0.69.0/debian/python3-hawkey.install	2022-11-12 22:06:07.0 +
+++ libdnf-0.69.0/debian/python3-hawkey.install	2023-10-29 15:53:24.0 +
@@ -1 +1 @@
-usr/local/lib/python3.*/dist-packages/hawkey
+usr/lib/python3/dist-packages/hawkey
diff -Nru libdnf-0.69.0/debian/python3-libdnf.install libdnf-0.69.0/debian/python3-libdnf.install
--- libdnf-0.69.0/debian/python3-libdnf.install	2022-11-12 22:06:07.0 +
+++ libdnf-0.69.0/debian/python3-libdnf.install	2023-10-29 15:53:37.0 +
@@ -1 +1 @@
-usr/local/lib/python3.*/dist-packages/libdnf
+usr/lib/python3/dist-packages/libdnf


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

Bug#1054657: transition: r-bioc-biocgenerics

[Graham Inggs]

Hi Andreas

On Sun, 29 Oct 2023 at 04:33, Andreas Tille  wrote:
> Can you confirm that packages uploaded to experimental can be moved in
> one rush from experimental to unstable without extra uploads?

I don't think this has ever been possible.  The packages would need to
be uploaded again to unstable, presumably at the appropriate
dependency level in the transition.

Seeing these packages would be NEW, even if they were initially
uploaded directly to unstable, they would likely still require
source-only uploads for migration anyway.

> Do you
> have this process in mind after the moreinfo tag is removed?

No, after the NEW packages have cleared NEW and the moreinfo tag is
removed, we'll consider a slot for the transition.  We would like to
avoid stalling the transition with multiple packages going through
NEW, and putting pressure on FTP Masters by telling them a package is
needed for a transition is not nice either.

Regards
Graham

Bug#1052911: librepo: FTBFS: dh_install: error: missing files, aborting

[Luca Boccassi]

Control: tags -1 pending

On Tue, 26 Sep 2023 15:28:51 +0200 Lucas Nussbaum 
wrote:
> Source: librepo
> Version: 1.14.5-3
> Severity: serious
> Justification: FTBFS
> Tags: trixie sid ftbfs
> User: lu...@debian.org
> Usertags: ftbfs-20230925 ftbfs-trixie
> 
> Hi,
> 
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
> 
> 
> Relevant part (hopefully):
> > make[3]: Entering directory '/<>/build'
> > make[3]: Nothing to be done for 'preinstall'.
> > make[3]: Leaving directory '/<>/build'
> > Install the project...
> > /usr/bin/cmake -P cmake_install.cmake
> > -- Install configuration: "None"
> > -- Installing:
/<>/debian/tmp/usr/include/librepo/checksum.h
> > -- Installing:
/<>/debian/tmp/usr/include/librepo/fastestmirror.h
> > -- Installing:
/<>/debian/tmp/usr/include/librepo/gpg.h
> > -- Installing:
/<>/debian/tmp/usr/include/librepo/handle.h
> > -- Installing:
/<>/debian/tmp/usr/include/librepo/librepo.h
> > -- Installing:
/<>/debian/tmp/usr/include/librepo/metadata_downloader.h
> > -- Installing:
/<>/debian/tmp/usr/include/librepo/metalink.h
> > -- Installing:
/<>/debian/tmp/usr/include/librepo/mirrorlist.h
> > -- Installing:
/<>/debian/tmp/usr/include/librepo/package_downloader.h
> > -- Installing:
/<>/debian/tmp/usr/include/librepo/rcodes.h
> > -- Installing:
/<>/debian/tmp/usr/include/librepo/repoconf.h
> > -- Installing:
/<>/debian/tmp/usr/include/librepo/repomd.h
> > -- Installing:
/<>/debian/tmp/usr/include/librepo/repoutil_yum.h
> > -- Installing:
/<>/debian/tmp/usr/include/librepo/result.h
> > -- Installing:
/<>/debian/tmp/usr/include/librepo/types.h
> > -- Installing:
/<>/debian/tmp/usr/include/librepo/url_substitution.h
> > -- Installing:
/<>/debian/tmp/usr/include/librepo/util.h
> > -- Installing:
/<>/debian/tmp/usr/include/librepo/version.h
> > -- Installing:
/<>/debian/tmp/usr/include/librepo/xmlparser.h
> > -- Installing:
/<>/debian/tmp/usr/include/librepo/yum.h
> > -- Installing:
/<>/debian/tmp/usr/include/librepo/downloader.h
> > -- Installing:
/<>/debian/tmp/usr/include/librepo/downloader_internal.h
> > -- Installing:
/<>/debian/tmp/usr/include/librepo/downloadtarget.h
> > -- Installing: /<>/debian/tmp/usr/lib/x86_64-linux-
gnu/librepo.so.0
> > -- Installing: /<>/debian/tmp/usr/lib/x86_64-linux-
gnu/librepo.so
> > -- Installing: /<>/debian/tmp/usr/lib/x86_64-linux-
gnu/pkgconfig/librepo.pc
> > -- Installing: /<>/debian/tmp/usr/lib/python3/dist-
packages/librepo/__init__.py
> > -- Installing: /<>/debian/tmp/usr/lib/python3/dist-
packages/librepo/_librepo.so
> > make[2]: Leaving directory '/<>/build'
> > # Use system-provides files.
> > rm -fv 'build/doc/python/_static/jquery.js' \
> >    'build/doc/python/_static/underscore.js' \
> >    'build/doc/c/html/jquery.js' \
> >    'build/doc/python/_static/doctools.js' \
> >    'build/doc/python/_static/language_data.js' \
> >    'build/doc/python/_static/searchtools.js'
> > removed 'build/doc/python/_static/jquery.js'
> > removed 'build/doc/python/_static/underscore.js'
> > removed 'build/doc/c/html/jquery.js'

Uploaded NMU to DELAYED/5 fixing this issue with the attached debdiff.

-- 
Kind regards,
Luca Boccassi
diff -Nru librepo-1.14.5/debian/changelog librepo-1.14.5/debian/changelog
--- librepo-1.14.5/debian/changelog	2023-01-10 08:23:24.0 +
+++ librepo-1.14.5/debian/changelog	2023-10-29 15:42:43.0 +
@@ -1,3 +1,10 @@
+librepo (1.14.5-3.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Move python3 modules from /usr/lib/local/ (Closes: #1052911)
+
+ -- Luca Boccassi   Sun, 29 Oct 2023 15:42:43 +
+
 librepo (1.14.5-3) unstable; urgency=medium
 
   * Update patch for test_yum_package_downloading.py thanks to
diff -Nru librepo-1.14.5/debian/python3-librepo.install librepo-1.14.5/debian/python3-librepo.install
--- librepo-1.14.5/debian/python3-librepo.install	2022-11-13 08:26:30.0 +
+++ librepo-1.14.5/debian/python3-librepo.install	2023-10-29 15:42:22.0 +
@@ -1 +1 @@
-usr/local/lib/python3.*
+usr/lib/python3


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

Bug#1052913: libcomps: FTBFS: dh_install: error: missing files, aborting

[Luca Boccassi]

Control: tags -1 pending

On Tue, 26 Sep 2023 15:28:41 +0200 Lucas Nussbaum 
wrote:
> Source: libcomps
> Version: 0.1.19-2
> Severity: serious
> Justification: FTBFS
> Tags: trixie sid ftbfs
> User: lu...@debian.org
> Usertags: ftbfs-20230925 ftbfs-trixie
> 
> Hi,
> 
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
> 
> 
> Relevant part (hopefully):
> > make[3]: Entering directory '/<>/build'
> > make[3]: Nothing to be done for 'preinstall'.
> > make[3]: Leaving directory '/<>/build'
> > Install the project...
> > /usr/bin/cmake -P cmake_install.cmake
> > -- Install configuration: "None"
> > -- Installing: /<>/debian/tmp/usr/lib/x86_64-linux-
gnu/libcomps.so.0
> > -- Installing: /<>/debian/tmp/usr/lib/x86_64-linux-
gnu/libcomps.so
> > -- Installing:
/<>/debian/tmp/usr/include/libcomps/comps_doc.h
> > -- Installing:
/<>/debian/tmp/usr/include/libcomps/comps_docgroup.h
> > -- Installing:
/<>/debian/tmp/usr/include/libcomps/comps_doccategory.h
> > -- Installing:
/<>/debian/tmp/usr/include/libcomps/comps_docenv.h
> > -- Installing:
/<>/debian/tmp/usr/include/libcomps/comps_docpackage.h
> > -- Installing:
/<>/debian/tmp/usr/include/libcomps/comps_docgroupid.h
> > -- Installing:
/<>/debian/tmp/usr/include/libcomps/comps_obj.h
> > -- Installing:
/<>/debian/tmp/usr/include/libcomps/comps_mm.h
> > -- Installing:
/<>/debian/tmp/usr/include/libcomps/comps_hslist.h
> > -- Installing:
/<>/debian/tmp/usr/include/libcomps/comps_dict.h
> > -- Installing:
/<>/debian/tmp/usr/include/libcomps/comps_objradix.h
> > -- Installing:
/<>/debian/tmp/usr/include/libcomps/comps_objmradix.h
> > -- Installing:
/<>/debian/tmp/usr/include/libcomps/comps_objdict.h
> > -- Installing:
/<>/debian/tmp/usr/include/libcomps/comps_objlist.h
> > -- Installing:
/<>/debian/tmp/usr/include/libcomps/comps_elem.h
> > -- Installing:
/<>/debian/tmp/usr/include/libcomps/comps_radix.h
> > -- Installing:
/<>/debian/tmp/usr/include/libcomps/comps_mradix.h
> > -- Installing:
/<>/debian/tmp/usr/include/libcomps/comps_bradix.h
> > -- Installing:
/<>/debian/tmp/usr/include/libcomps/comps_set.h
> > -- Installing:
/<>/debian/tmp/usr/include/libcomps/comps_parse.h
> > -- Installing:
/<>/debian/tmp/usr/include/libcomps/comps_log.h
> > -- Installing:
/<>/debian/tmp/usr/include/libcomps/comps_default.h
> > -- Installing:
/<>/debian/tmp/usr/include/libcomps/comps_utils.h
> > -- Installing:
/<>/debian/tmp/usr/include/libcomps/comps_validate.h
> > -- Installing:
/<>/debian/tmp/usr/include/libcomps/comps_log_codes.h
> > -- Up-to-date: /<>/debian/tmp/usr/lib/x86_64-linux-
gnu/libcomps.so.0
> > -- Up-to-date: /<>/debian/tmp/usr/lib/x86_64-linux-
gnu/libcomps.so
> > -- Installing: /<>/debian/tmp/usr/lib/x86_64-linux-
gnu/pkgconfig/libcomps.pc
> > -- Up-to-date: /<>/debian/tmp/usr/lib/x86_64-linux-
gnu/pkgconfig/libcomps.pc
> > -- Installing: /<>/debian/tmp/usr/lib/python3/dist-
packages/libcomps/__init__.py
> > -- Installing: /<>/debian/tmp/usr/lib/python3/dist-
packages/libcomps/_libpycomps.so
> > running install_egg_info
> > /usr/lib/python3/dist-packages/setuptools/_distutils/cmd.py:66:
SetuptoolsDeprecationWarning: setup.py install is deprecated.
> > !!

Uploaded NMU to DELAYED/5 fixing this issue with the attached debdiff.

-- 
Kind regards,
Luca Boccassi
diff -Nru libcomps-0.1.19/debian/changelog libcomps-0.1.19/debian/changelog
--- libcomps-0.1.19/debian/changelog	2023-01-07 19:04:37.0 +
+++ libcomps-0.1.19/debian/changelog	2023-10-29 15:32:45.0 +
@@ -1,3 +1,10 @@
+libcomps (0.1.19-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Move python3 modules from /usr/lib/local/ (Closes: #1052913)
+
+ -- Luca Boccassi   Sun, 29 Oct 2023 15:32:45 +
+
 libcomps (0.1.19-2) unstable; urgency=medium
 
   * Set myself to maintainer.
diff -Nru libcomps-0.1.19/debian/python3-libcomps.install libcomps-0.1.19/debian/python3-libcomps.install
--- libcomps-0.1.19/debian/python3-libcomps.install	2022-11-13 08:29:48.0 +
+++ libcomps-0.1.19/debian/python3-libcomps.install	2023-10-29 15:31:40.0 +
@@ -1 +1 @@
-usr/local/lib/python3.*
+usr/lib/python3*


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

Bug#1051323: libseccomp: Please add support for loongarch64

[Felix Geyer]

Control: tags -1 - patch

Hi,

On 06.09.23 10:27, zhangdandan wrote:

Would it be possible to include the support for LoongArch in the next upload?
Your opinions are welcome.
If you have any questions, you can contact me at any time.

[1]:https://github.com/seccomp/libseccomp
[2]:https://github.com/seccomp/libseccomp/pull/356
[3]:https://packages.debian.org/source/sid/libseccomp


That's quite a large set of changes and they don't apply cleanly against
v2.5.4.
Therefore I'd prefer to wait until upstream has released v2.6.0 with
LoongArch support.

Best regards,
Felix

Bug#969177: debmake: cannot create deb for nodejs modeule

[Osamu Aoki]

Hi,

On Sun, 2023-10-29 at 23:52 +0900, Osamu Aoki wrote:
> Hi,
> 
> On Sun, 2023-10-29 at 15:11 +0530, Pirate Praveen wrote:
> ...
> > As you noted in subsequent comment, we can skip package.yaml. Build depends
> > can be dh-sequence-nodejs instead of pkg-js-tools (npm2deb did that switch).
> 
> Both in bookworm and sid, dh-sequence-nodejs is a virtual package offered by
> dh-
> nodejs.  The binary package dh-nodejs is based on source package pkg-js-tools
> which seems to have gone through package split.
> 
> Although I just updated package, it may be good idea to change this to dh-
> nodejs
> now.
> 
> > If dh-sequence-nodejs is in Build Deps then we don't need to add --with
> > nodejs
> > to dh as well.
> 
> This seems to be redundant but I think no harm and good practice to be
> explicit
> to be future proof.  This comes from python experience.  I may be wrong.
> 
> Osamu
> > 

dh-nodejs is Depends on pkg-js-tools
pkg-js-tools is not Depends (only Suggests) for dh-nodejs
For packaging we only need dh-nodejs

So requiring pkg-js-tools is not enough... needs to be fixed.

Bug#969177: debmake: cannot create deb for nodejs modeule

[Osamu Aoki]

Hi,

On Sun, 2023-10-29 at 15:11 +0530, Pirate Praveen wrote:
...
> As you noted in subsequent comment, we can skip package.yaml. Build depends
> can be dh-sequence-nodejs instead of pkg-js-tools (npm2deb did that switch).

Both in bookworm and sid, dh-sequence-nodejs is a virtual package offered by dh-
nodejs.  The binary package dh-nodejs is based on source package pkg-js-tools
which seems to have gone through package split.

Although I just updated package, it may be good idea to change this to dh-nodejs
now.

> If dh-sequence-nodejs is in Build Deps then we don't need to add --with nodejs
> to dh as well.

This seems to be redundant but I think no harm and good practice to be explicit
to be future proof.  This comes from python experience.  I may be wrong.

Osamu
> 

Bug#888670: gnome-system-tools: has been unmaintained upstream for a long time

[Bastian Germann]

Nothing has changed in the new upstream project since it was created.
Not even the existing Debian patches were imported.
So the original assumptions still hold for the fork.

Bug#1054777: Fwd: Bug#1054777: libfiu: FTBFS: dh_auto_test: error: make -j8 test V=1 LC_ALL=C returned exit code 2

[Alberto Bertogli]

On Sun, Oct 29, 2023 at 02:00:32PM +, Chris Lamb wrote:

Dear Alberto,


I think this is likely a problem I already fixed back in February in
commit 5dcc6d4.


Ah, cherry-picking that commit fixed it for me. I've gone ahead and
uploaded that to Debian in order to close this RC bug, but please do
feel free to also release a libfiu v1.2 as well.

That would have the added advantage of "clearing out" the other patch
we had to apply re. Link-Time Optimisation.


Great!

I've just released libfiu 1.2 then :)

Just in case, one of the possibly-impacting patches is updating to 
setuptools, that may need some adjustments in the build-depends:


https://blitiri.com.ar/git/r/libfiu/c/88b961aad6b1fcbc0e1decbf34a0bc9510600988/

Hopefully with that you can clear the other patch!

Thank you!
Alberto

Bug#1054981: libtk-objeditor-perl: FTBFS: dh_auto_test: error: make -j8 test TEST_VERBOSE=1 returned exit code 2

[Dominique Dumont]

On Sunday, 29 October 2023 01:09:21 CET you wrote:
> This seems to be broken by libtk-objscanner-perl 2.018-1 (building in
> a testing chroot with 2.017-2 still works).
> 
> Dominique, I think that's a case for you :)

ack. I'll handle it upstream. No need to open a bug there.

All the best

Bug#1055024: cryptsetup-initramfs changes crypttab entries order when generating initramfs

[Nicolas Melot]

Package: cryptsetup-initramfs
Version: 2:2.4.3-1ubuntu1.1
Severity: important
Tags: upstream d-i
X-Debbugs-Cc: ny...@doramail.com

Dear Maintainer,

This is a repost of the same bug report I submitted to Ubuntu maintainers on
https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/2031499 and that
seems to have been left as is. I am now hitting the same issue on Debian
Bookworm.

update-initramfs does not generate entries of initrd's /cryptroot/crypttab in
the same order as system's /etc/crypttab, when entries tagged as "initramfs"
are placed before entries that are not, or that are detected as necessary to
unlock the root partition. This is a problem if partitions automatically
detected as needed depends on a partition that is not detected as necessary;
even if it actually is. For examples, see system's /etc/crypttab below:

#
keyring UUID=abcdefg none luks,initramfs
swap /dev/xps-nicmel/swap legacy luks,keyscript=/etc/luks-key.sh

Turns to initrd's /cryptroot/crypttab:

swap /dev/mapper/xps--nicmel-swap legacy luks,keyscript=/etc/luks-key.sh
keyring UUID=abcdefg none luks,initramfs

The swap partition gets its key from the script luks-key.sh, which itself reads
it from keyring. update-initramfs cannot detect this dependency and places swap
as to be decrypted first. Decryption will fail at boot because it won't find
the necessary key.

I could work around the problem by modifying /usr/share/initramfs-
tools/hooks/cryptroot from

177 generate_initrd_crypttab() {
178 local devnos usage IFS="$(printf '\t\n ')"
179 mkdir -- "$DESTDIR/cryptroot"
180 true >"$DESTDIR/cryptroot/targets"
181
182 {
183 if devnos="$(get_mnt_devno /)"; then
184 if [ -n "$devnos" ]; then
185 usage=rootfs foreach_cryptdev crypttab_find_and_print_entry $devnos
186 fi
187 else
188 cryptsetup_message "WARNING: Couldn't determine root device"
189 fi
190
191 if devnos="$(get_resume_devno)" && [ -n "$devnos" ]; then
192 usage=resume foreach_cryptdev crypttab_find_and_print_entry $devnos
193 fi
194
195 if devnos="$(get_mnt_devno /usr)" && [ -n "$devnos" ]; then
196 usage="" foreach_cryptdev crypttab_find_and_print_entry $devnos
197 fi
198
199 # add crypttab entries with the 'initramfs' option set
200 crypttab_foreach_entry crypttab_print_initramfs_entry
201 } 3>"$DESTDIR/cryptroot/crypttab"
202 rm -f "$DESTDIR/cryptroot/targets"
203 }

to

generate_initrd_crypttab() {
178 local devnos usage IFS="$(printf '\t\n ')"
179 mkdir -- "$DESTDIR/cryptroot"
180 true >"$DESTDIR/cryptroot/targets"
181
182 {
183 # add crypttab entries with the 'initramfs' option set
184 crypttab_foreach_entry crypttab_print_initramfs_entry
185
186 if devnos="$(get_mnt_devno /)"; then
187 if [ -n "$devnos" ]; then
188 usage=rootfs foreach_cryptdev crypttab_find_and_print_entry $devnos
189 fi
190 else
191 cryptsetup_message "WARNING: Couldn't determine root device"
192 fi
193
194 if devnos="$(get_resume_devno)" && [ -n "$devnos" ]; then
195 usage=resume foreach_cryptdev crypttab_find_and_print_entry $devnos
196 fi
197
198 if devnos="$(get_mnt_devno /usr)" && [ -n "$devnos" ]; then
199 usage="" foreach_cryptdev crypttab_find_and_print_entry $devnos
200 fi
201 } 3>"$DESTDIR/cryptroot/crypttab"
202 rm -f "$DESTDIR/cryptroot/targets"
203 }

i.e. moving line 200 to line 183, so that "initramfs"-tagged entries are
generated before other entries. Of course this is a quick and dirty fix and
won't stand many other scenarios.

A possible quick fix includes an order field in options section of
/etc/crypttab, or preserving entries order of system's crypttab. A better one
would be a dependency option, e.g. depends=keyring in the example above:

keyring UUID=abcdefg none luks,initramfs
swap /dev/xps-nicmel/swap legacy luks,keyscript=/etc/luks-
key.sh,depends=keyring


-- Package-specific info:
-- /proc/cmdline
BOOT_IMAGE=/vmlinuz-6.2.0-35-generic root=ZFS=xps-nicmel/ubuntu-22.04 ro quiet 
splash resume=UUID=dd6ea7ab-5651-4d11-ae2c-b02869051ea3 vt.handoff=1

-- /etc/crypttab
# 

keyring UUID=ab96a60d-94e8-40cf-b6e8-e29d30a5b5ec   none
luks,initramfs
#ubuntu-22.04   /dev/xps-nicmel/ubuntu-22.04none
luks
nvme0n1p10  /dev/nvme0n1p10 xps-nicmel  
luks,initramfs,keyscript=/etc/luks-key.sh
nvme0n1p11  /dev/nvme0n1p11 xps-nicmel  
luks,initramfs,keyscript=/etc/luks-key.sh
nvme0n1p12  /dev/nvme0n1p12 xps-nicmel  
luks,initramfs,keyscript=/etc/luks-key.sh
nvme0n1p13  /dev/nvme0n1p13 xps-nicmel  
luks,initramfs,keyscript=/etc/luks-key.sh
nvme0n1p16  /dev/nvme0n1p16 xps-nicmel  
luks,initramfs,keyscript=/etc/luks-key.sh
nvme0n1p17  /dev/nvme0n1p17 xps-nicmel  
luks,initramfs,keyscript=/etc/luks-key.sh
nvme0n1p18  /dev/nvme0n1p18

Bug#1054777: Fwd: Bug#1054777: libfiu: FTBFS: dh_auto_test: error: make -j8 test V=1 LC_ALL=C returned exit code 2

[Chris Lamb]

Dear Alberto,

> I think this is likely a problem I already fixed back in February in 
> commit 5dcc6d4.

Ah, cherry-picking that commit fixed it for me. I've gone ahead and
uploaded that to Debian in order to close this RC bug, but please do
feel free to also release a libfiu v1.2 as well.

That would have the added advantage of "clearing out" the other patch
we had to apply re. Link-Time Optimisation.


Best wishes,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org  chris-lamb.co.uk
   `-

Bug#1054233: liblilv-0-0: Package does not follow FHS, it adds /usr/lib/$(DEB_HOST_MULTIARCH) to the --default-lv2-path waf configure option, see rules file, line 21.

[Erich Eickmeyer]

Sebastian,

I'm fairly certian Robin Gareus made it quite clear what Jeremy was 
saying in his reply:


>The LV2 FHS that Jeremy mention can be found at
>https://lv2plug.in/pages/filesystem-hierarchy-standard.html
>
>Now you may not like, or disagree with the official standard, but 
breaking it is not acceptable. This affects various >3rd party software, 
notably Reaper, Harrison Mixbus, Ardour and other non-free DAWs that 
expect LV2 plugins in >/usr/lib/lv2/

>
>LV2s are to be installed $PREFIX/lib/lv2 (unrelated to $LIBDIR).
>Most LV2 plugin build systems use LV2DIR = $PREFIX/lib/lv2 for this.

This does divert from the standard location in which shared libraries 
are expected to be located, but LV2 plugins, as you are aware, are not 
normal shared libraries. If they cannot be found in /usr/lib/lv2, then 
it literally breaks the functionality of several DAWs out there, 
including Ardour (which we ship). Sure, users can always manually add 
the search path of /usr/lib/$(DEB_HOST_MULTIARCH)/lv2 to the software, 
but that's an unnecessary inconvenience.


I checked the salsa repo for liblilv (and another) and it seems as 
though /usr/lib/$(DEB_HOST_MULTIARCH)/lv2 is being intentionally set as 
the install location here, so this simply needs to be reverted. I can 
even set-up the pull request.


Beyond that, I will be fairly unhappy if I have to downstream patch this.

Cheers,
Erich

--
Erich Eickmeyer
Project Leader - Ubuntu Studio
Technical Lead - Edubuntu

On 10/29/23 05:10, Sebastian Ramacher wrote:

Control: tags -1 moreinfo

On 2023-10-19 17:51:33 +0200, Jeremy Jongepier wrote:

Package: liblilv-0-0
Version: 0.24.14-1
Severity: important

Package does not follow FHS, it adds /usr/lib/$(DEB_HOST_MULTIARCH) to the 
--default-lv2-path waf configure option, see rules file, line 21. The addition 
of this line indicates that something fundamental has changed, namely the 
default path where Debian installs its LV2 plugins. These go into 
/usr/lib/$(DEB_HOST_MULTIARCH) too now which breaks setups running software 
that uses the FHS as a starting point for LV2 plugin discovery. The LV2 plugin 
packages that Debian now installs are now not discovered anymore.

I think you are mistaken. It you compare the the default path in
meson.build and the one specified in debian/rules, it extends the
default path with /usr/lib/$(DEB_HOST_MULTIARCH)/lv2 (note the lv2).

Please describe the actual problem that you are seeing.

Cheers


--
Project Leader - Ubuntu Studio
Technical Lead - Edubuntu

Bug#1055023: FTBFS: libpoe-component-client-dns-perl requires DNS during tests.

[Sven Mueller]

Package: libpoe-component-client-dns-perl
Severity: serious
Version: 1:1.054-3

While rebuilding debian trixie in a network-restricted environment, we
ran into this build error (using sbuild):

Can't call method "rdstring" on an undefined value at t/06_hosts.t line 143.
# Looks like your test exited with 22 just after 1.

The problem is likely that DNS does work to some degree (it can
resolve some hosts, I'm not sure what the exact response is on other
hosts).

The test at 
https://sources.debian.org/src/libpoe-component-client-dns-perl/1%3A1.054-3/t/06_hosts.t/#L14
isn't a sufficient precaution to work around the Debian Policy
*requirement* that required build targets *must* *not* *use* network
resources that weren't created by the build processes themselves. The
test itself is already using network resources it hasn't created
itself.

Please disable this test or ensure that it's not using external resolvers.

Kind regards,
Sven

Bug#1055022: bullseye-pu: package distro-info-data/0.51+deb11u5, distro-info/1.0+deb11u1

[Stefano Rivera]

Package: release.debian.org
Severity: normal
Tags: bullseye
User: release.debian@packages.debian.org
Usertags: pu
X-Debbugs-Cc: distro-info-d...@packages.debian.org
Control: affects -1 + src:distro-info-data

Bullseye version of #1055009.

[ Reason ]
This is a regular distro-info-data update, adding Ubuntu 24.04 LTS.
It includes some corrections to historical data, one of which affects
the distro-info test-suite.

So, included is a coupled update of distro-info to expect the new values
in its test-suite. In unstable, I updated Build-Depends and Depends on
distro-info-data to help autopkgtests. For stable I just updated the
Build-Depends.

In addition to the changes backported in bullseye is a set of patches to
ensure distro-info's Python packaging metadata version PEP-440
compliant.

[ Impact ]
Stable systems would be unaware of the new Ubuntu LTS.

[ Tests ]
distro-info-data is just CSV data, with some automated tests to verify
the structure and sanity-check the values.

distro-info has a more complex test suite that covers real-world tests
with old stable releases. This needed to be updated for the data
changes.

Build tests and autopkgtests pass in both packages.

Manually verified that the Python package has valid PEP-440 metadata.

[ Risks ]
Trivial, low risk.

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

[ Changes ]

 distro-info-data (0.51+deb11u5) bullseye; urgency=medium
   * Update data to 0.59:
 - Add Ubuntu 24.04 LTS Noble Numbat (LP: #2041662).
 - Correct Ubuntu 6.10 EOL date to 2008-04-25
 - Correct Ubuntu 16.04 ESM begin to 2021-04-30
 - Move Ubuntu 12.04 ESM end date back to Friday, 2019-04-26
 - Correct Debian 3.1 EOL date to 2008-03-31
 - Correct Debian 7 EOL date to 2016-04-25
 - Move Debian 9 EOL to the 9.13 release date 2020-07-18
 - Move Debian 10 EOL to the 10.13 release date 2022-09-10

 distro-info (1.0+deb11u1) bullseye; urgency=medium
   * python:
 - Assert that Python version is PEP440 compliant
 - Handle more Debian versions correctly in make_pep440_compliant
   * Update tests for distro-info-data 0.51+deb11u5, which adjusted Debian 7's
 EoL (Closes: #1054946)

diff --git a/debian.csv b/debian.csv
index 8272895..2646246 100644
--- a/debian.csv
+++ b/debian.csv
@@ -6,14 +6,14 @@ version,codename,series,created,release,eol,eol-lts,eol-elts
 2.1,Slink,slink,1998-07-24,1999-03-09,2000-10-30
 2.2,Potato,potato,1999-03-09,2000-08-15,2003-07-30
 3.0,Woody,woody,2000-08-15,2002-07-19,2006-06-30
-3.1,Sarge,sarge,2002-07-19,2005-06-06,2008-03-30
+3.1,Sarge,sarge,2002-07-19,2005-06-06,2008-03-31
 4.0,Etch,etch,2005-06-06,2007-04-08,2010-02-15
 5.0,Lenny,lenny,2007-04-08,2009-02-14,2012-02-06
 6.0,Squeeze,squeeze,2009-02-14,2011-02-06,2014-05-31,2016-02-29
-7,Wheezy,wheezy,2011-02-06,2013-05-04,2016-04-26,2018-05-31,2020-06-30
+7,Wheezy,wheezy,2011-02-06,2013-05-04,2016-04-25,2018-05-31,2020-06-30
 8,Jessie,jessie,2013-05-04,2015-04-26,2018-06-17,2020-06-30,2025-06-30
-9,Stretch,stretch,2015-04-26,2017-06-17,2020-07-06,2022-06-30,2027-06-30
-10,Buster,buster,2017-06-17,2019-07-06,2022-08-14,2024-06-30,2029-06-30
+9,Stretch,stretch,2015-04-26,2017-06-17,2020-07-18,2022-06-30,2027-06-30
+10,Buster,buster,2017-06-17,2019-07-06,2022-09-10,2024-06-30,2029-06-30
 11,Bullseye,bullseye,2019-07-06,2021-08-14,2024-08-14
 12,Bookworm,bookworm,2021-08-14,2023-06-10,2026-06-10
 13,Trixie,trixie,2023-06-10
diff --git a/debian/changelog b/debian/changelog
index ea4f4da..aee8df2 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,17 @@
+distro-info-data (0.51+deb11u5) bullseye; urgency=medium
+
+  * Update data to 0.59:
+- Add Ubuntu 24.04 LTS Noble Numbat (LP: #2041662).
+- Correct Ubuntu 6.10 EOL date to 2008-04-25
+- Correct Ubuntu 16.04 ESM begin to 2021-04-30
+- Move Ubuntu 12.04 ESM end date back to Friday, 2019-04-26
+- Correct Debian 3.1 EOL date to 2008-03-31
+- Correct Debian 7 EOL date to 2016-04-25
+- Move Debian 9 EOL to the 9.13 release date 2020-07-18
+- Move Debian 10 EOL to the 10.13 release date 2022-09-10
+
+ -- Stefano Rivera   Sun, 29 Oct 2023 14:57:15 +0200
+
 distro-info-data (0.51+deb11u4) bullseye; urgency=medium
 
   * Update data to 0.58:
diff --git a/ubuntu.csv b/ubuntu.csv
index 14ef832..3667f04 100644
--- a/ubuntu.csv
+++ b/ubuntu.csv
@@ -3,7 +3,7 @@ version,codename,series,created,release,eol,eol-server,eol-esm
 5.04,Hoary Hedgehog,hoary,2004-10-20,2005-04-08,2006-10-31
 5.10,Breezy Badger,breezy,2005-04-08,2005-10-12,2007-04-13
 6.06 LTS,Dapper Drake,dapper,2005-10-12,2006-06-01,2009-07-14,2011-06-01
-6.10,Edgy Eft,edgy,2006-06-01,2006-10-26,2008-04-26
+6.10,Edgy Eft,edgy,2006-06-01,2006-10-26,2008-04-25
 7.04,Feisty Fawn,feisty,2006-10-26,2007-04-19,2008-10-19
 7.10,Gutsy 

Bug#1054337: lv2 version in debian is outdated

[niels nowatzki]

Hi,

assuming your workload to be quite high, maybe it helps to file a patch.

This should suffice to incorporate the newer releases. Apparently i
can't test this properly. 

diff --git a/debian/watch b/debian/watch
index db1b900..6f49a6f 100644
--- a/debian/watch
+++ b/debian/watch
@@ -1,3 +1,3 @@
 version=4
 opts=pgpmode=auto \
- https://lv2plug.in/spec/lv2-([\d.]*)\.tar\.bz2
+ https://lv2plug.in/spec/lv2-([\d.]*)\.(?:tar\.(?:bz2|xz))
-- 

Bug#1052942: insserv: FTBFS: insserv: Could not read script nolsbheader: No such file or directory

[Santiago Vila]

El 29/10/23 a las 14:20, Mark Hindley escribió:

Lucas,

I am afraid I still cannot reproduce this.

I attach my successful .buildinfo. What are the differences to yours?


Hello. The problem is that failed builds do not produce .buildinfo files,
so we can't compare buildinfo files in this case.

However, I can create a machine for you to reproduce the problem.

Please contact me privately for details.

Thanks.

Bug#1054921: Build error for quantlib-swig on mips64el

[Dirk Eddelbuettel]

The Debian package fails to build now on mipsel, a log is at [1]. The gist
seems to be a relocation error:

   g++ -shared -Wl,-O1 -Wl,-Bsymbolic-functions -O0 -g0 -mxgot --param 
ggc-min-expand=20 -DBOOST_NO_AUTO_PTR 
build/temp.linux-mips64-cpython-311/QuantLib/quantlib_wrap.o 
-L/usr/lib/mips64el-linux-gnuabi64 -L/usr/lib -lQuantLib -o 
build/lib.linux-mips64-cpython-311/QuantLib/_QuantLib.cpython-311-mips64el-linux-gnuabi64.so
 -fopenmp
   build/temp.linux-mips64-cpython-311/QuantLib/quantlib_wrap.o: in function 
`virtual thunk to QuantLib::HimalayaOption::arguments::~arguments()':
   
quantlib_wrap.cpp:(.text._ZN8QuantLib14HimalayaOption9argumentsD1Ev[_ZN8QuantLib14HimalayaOption9argumentsD1Ev]+0x104):
 relocation truncated to fit: R_MIPS_GOT_PAGE against 
`.text._ZN8QuantLib14HimalayaOption9argumentsD1Ev'

Luigi, and idea if that is a known swig-on-mips64el issue and if we can
addres it with particular flag? As the Debian bug report at [2] states, "this
used to work" and I didn't change anything for the 1.32 pair of quantlib and
quantlib-swig.

For quantlib-swig, and for a few years now, I set some exotic compiler flags:

   ifneq "$(findstring $(cpu), mipsel mips mips64el)" ""
   compilerflags   = -O0 -g0 -mxgot --param ggc-min-expand=20 
-DBOOST_NO_AUTO_PTR
   endif

but that mostly came from trying to keep the build with time or ram limits.

Any hints would be most welcome.

Cheers, Dirk

[1] 
https://buildd.debian.org/status/fetch.php?pkg=quantlib-swig=mips64el=1.32-1=1698321785=0
[2] https://bugs.debian.org/1054921, also in CC for this email

-- 
dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org

Bug#1052942: insserv: FTBFS: insserv: Could not read script nolsbheader: No such file or directory

[Mark Hindley]

Lucas,

I am afraid I still cannot reproduce this.

I attach my successful .buildinfo. What are the differences to yours?

Thanks

Mark
Format: 1.0
Source: insserv
Binary: insserv insserv-dbgsym
Architecture: amd64
Version: 1.24.0-1
Checksums-Md5:
 3c928ff0990c2942950fa368b3978086 79480 insserv-dbgsym_1.24.0-1_amd64.deb
 9bffd1e3395d57a5979030bc472dc80c 50572 insserv_1.24.0-1_amd64.deb
Checksums-Sha1:
 aa26018adc027c1af58704991d3339c1a43dccf2 79480 
insserv-dbgsym_1.24.0-1_amd64.deb
 1d1a7b8f6e5b5ea864a7661f34e767b9a93e4b77 50572 insserv_1.24.0-1_amd64.deb
Checksums-Sha256:
 39912ad2e18538a91ae397467a6cd96519dd948fee2ed90b39c40b4477352bc1 79480 
insserv-dbgsym_1.24.0-1_amd64.deb
 e4e58a1a6a3cb6a68e205341606b1702ef10dd5bd6d43af03e123b536b4cc8f8 50572 
insserv_1.24.0-1_amd64.deb
Build-Origin: Debian
Build-Architecture: amd64
Build-Date: Sun, 29 Oct 2023 13:16:40 +
Build-Path: /build/insserv-1.24.0
Build-Tainted-By:
 merged-usr-via-aliased-dirs
Installed-Build-Depends:
 autoconf (= 2.71-3),
 automake (= 1:1.16.5-1.3),
 autopoint (= 0.21-12),
 autotools-dev (= 20220109.1),
 base-files (= 13),
 base-passwd (= 3.6.1),
 bash (= 5.2.15-2+b2),
 bash-completion (= 1:2.11-8),
 binutils (= 2.40.50.20230625-1),
 binutils-common (= 2.40.50.20230625-1),
 binutils-x86-64-linux-gnu (= 2.40.50.20230625-1),
 bsdextrautils (= 2.38.1-5+b1),
 bsdutils (= 1:2.38.1-5+b1),
 build-essential (= 12.10),
 bzip2 (= 1.0.8-5+b1),
 coreutils (= 9.1-1),
 cpp (= 4:12.3.0-1),
 cpp-10 (= 10.4.0-9),
 cpp-11 (= 11.4.0-1),
 cpp-12 (= 12.3.0-5),
 cpp-6 (= 6.5.0-2),
 cpp-8 (= 8.4.0-4),
 cpp-9 (= 9.5.0-3),
 dash (= 0.5.12-6),
 debconf (= 1.5.82),
 debhelper (= 13.11.4),
 debianutils (= 5.7-0.4),
 dh-autoreconf (= 20),
 dh-strip-nondeterminism (= 1.13.1-1),
 diffutils (= 1:3.8-4),
 dpkg (= 1.21.22),
 dpkg-dev (= 1.21.22),
 dwz (= 0.15-1),
 file (= 1:5.44-3),
 findutils (= 4.9.0-4),
 g++ (= 4:12.3.0-1),
 g++-12 (= 12.3.0-5),
 gcc (= 4:12.3.0-1),
 gcc-10 (= 10.4.0-9),
 gcc-10-base (= 10.4.0-9),
 gcc-11 (= 11.4.0-1),
 gcc-11-base (= 11.4.0-1),
 gcc-12 (= 12.3.0-5),
 gcc-12-base (= 12.3.0-5),
 gcc-13-base (= 13.1.0-7),
 gcc-6 (= 6.5.0-2),
 gcc-6-base (= 6.5.0-2),
 gcc-7-base (= 7.4.0-14),
 gcc-8 (= 8.4.0-4),
 gcc-8-base (= 8.4.0-4),
 gcc-9 (= 9.5.0-3),
 gcc-9-base (= 9.5.0-3),
 gettext (= 0.21-12),
 gettext-base (= 0.21-12),
 grep (= 3.8-5),
 groff-base (= 1.22.4-10),
 gzip (= 1.12-1),
 hostname (= 3.23+nmu1),
 init-system-helpers (= 1.65.2),
 intltool-debian (= 0.35.0+20060710.6),
 libacl1 (= 2.3.1-3),
 libarchive-zip-perl (= 1.68-1),
 libasan3 (= 6.5.0-2),
 libasan5 (= 9.5.0-3),
 libasan6 (= 11.4.0-1),
 libasan8 (= 13.1.0-7),
 libatomic1 (= 13.1.0-7),
 libattr1 (= 1:2.5.1-4),
 libaudit-common (= 1:3.0.9-1),
 libaudit1 (= 1:3.0.9-1),
 libbinutils (= 2.40.50.20230625-1),
 libblkid1 (= 2.38.1-5+b1),
 libbz2-1.0 (= 1.0.8-5+b1),
 libc-bin (= 2.36-9),
 libc-dev-bin (= 2.36-9),
 libc6 (= 2.36-9),
 libc6-dev (= 2.36-9),
 libcap-ng0 (= 0.8.3-1+b3),
 libcap2 (= 1:2.66-4),
 libcc1-0 (= 13.1.0-7),
 libcilkrts5 (= 7.4.0-14),
 libcom-err2 (= 1.47.0-2),
 libcrypt-dev (= 1:4.4.35-1),
 libcrypt1 (= 1:4.4.35-1),
 libctf-nobfd0 (= 2.40.50.20230625-1),
 libctf0 (= 2.40.50.20230625-1),
 libdb5.3 (= 5.3.28+dfsg2-1),
 libdebconfclient0 (= 0.270),
 libdebhelper-perl (= 13.11.4),
 libdpkg-perl (= 1.21.22),
 libelf1 (= 0.188-2.1),
 libfile-find-rule-perl (= 0.34-3),
 libfile-stripnondeterminism-perl (= 1.13.1-1),
 libgcc-10-dev (= 10.4.0-9),
 libgcc-11-dev (= 11.4.0-1),
 libgcc-12-dev (= 12.3.0-5),
 libgcc-6-dev (= 6.5.0-2),
 libgcc-8-dev (= 8.4.0-4),
 libgcc-9-dev (= 9.5.0-3),
 libgcc-s1 (= 13.1.0-7),
 libgcrypt20 (= 1.10.2-2),
 libgdbm-compat4 (= 1.23-3),
 libgdbm6 (= 1.23-3),
 libgmp10 (= 2:6.2.1+dfsg1-1.1),
 libgomp1 (= 13.1.0-7),
 libgpg-error0 (= 1.46-1),
 libgprofng0 (= 2.40.50.20230625-1),
 libgssapi-krb5-2 (= 1.20.1-2),
 libicu72 (= 72.1-3),
 libisl19 (= 0.20-2),
 libisl22 (= 0.22.1-1),
 libisl23 (= 0.26-3),
 libitm1 (= 13.1.0-7),
 libjansson4 (= 2.14-2),
 libk5crypto3 (= 1.20.1-2),
 libkeyutils1 (= 1.6.3-2),
 libkrb5-3 (= 1.20.1-2),
 libkrb5support0 (= 1.20.1-2),
 liblsan0 (= 13.1.0-7),
 liblz4-1 (= 1.9.4-1),
 liblzma5 (= 5.4.1-0.2),
 libmagic-mgc (= 1:5.44-3),
 libmagic1 (= 1:5.44-3),
 libmd0 (= 1.1.0-1),
 libmount1 (= 2.38.1-5+b1),
 libmpc3 (= 1.3.1-1),
 libmpfr6 (= 4.2.0-1),
 libmpx2 (= 8.4.0-4),
 libnsl-dev (= 1.3.0-2),
 libnsl2 (= 1.3.0-2),
 libnumber-compare-perl (= 0.03-3),
 libpam-modules (= 1.5.2-6),
 libpam-modules-bin (= 1.5.2-6),
 libpam-runtime (= 1.5.2-6),
 libpam0g (= 1.5.2-6),
 libpcre2-8-0 (= 10.42-1),
 libperl5.36 (= 5.36.0-7),
 libpipeline1 (= 1.5.7-1),
 libquadmath0 (= 13.1.0-7),
 libseccomp2 (= 2.5.4-1+b3),
 libselinux1 (= 3.4-1+b6),
 libsmartcols1 (= 2.38.1-5+b1),
 libssl3 (= 3.0.9-1),
 libstdc++-12-dev (= 12.3.0-5),
 libstdc++6 (= 13.1.0-7),
 libsub-override-perl (= 0.09-4),
 libsystemd0 (= 253-4),
 libtext-glob-perl (= 0.11-3),
 libtinfo6 (= 6.4-4),
 libtirpc-common (= 1.3.3+ds-1),
 libtirpc-dev (= 1.3.3+ds-1),
 libtirpc3 (= 1.3.3+ds-1),
 

Bug#1055021: linux: mips64el loongson3 kernel crashes when running cmake

[Aurelien Jarno]

Source: linux
Version: 5.10.197-1
Severity: grave
Tags: upstream patch
X-Debbugs-Cc: d...@debian.org, debian-m...@lists.debian.org

The loongson3 flavour of the mips64el kernel crash when running cmake:

| [ 4390.501529] do_cpu invoked from kernel context![#1]:
| [ 4390.506483] CPU: 3 PID: 24061 Comm: iou-sqp-22284 Not tainted 
5.10.0-26-loongson-3 #1 Debian 5.10.197-1
| [ 4390.515820] Hardware name: Loongson 
Lemote-3A4000-7A-1w-V1.00-A1901/Lemote-3A4000-7A-1w-V1.00-A1901, BIOS 
Loongson-PMON-V3.3-20201222 12/22/2020
| [ 4390.528699] $ 0 :  80bf9030 0001 
98020f844000
| [ 4390.536669] $ 4 : 9801017bb2c0 80dbc0b8 0008 
02008200
| [ 4390.544634] $ 8 : 0001 0001  
02e27c19
| [ 4390.552600] $12 : 5400cce0 80199c00 01ea 
01ea
| [ 4390.560565] $16 : 980100253700 80ecc740  
9800023cb8c0
| [ 4390.568530] $20 : 80ecdce0 9801017bb2c0 9801017bb8e0 

| [ 4390.576495] $24 : 0028 98020f847e58
| [ 4390.584461] $28 : 98020f844000 98020f847d40 9800023cb8c0 
80bf925c
| [ 4390.592426] Hi : 00de
| [ 4390.595974] Lo : d70a40ec
| [ 4390.599532] epc : 802177c0 _save_fp+0x10/0xa0
| [ 4390.604727] ra : 80bf925c __schedule+0x804/0xe08
| [ 4390.610263] Status: 5400cce2 KX SX UX KERNEL EXL
| [ 4390.614949] Cause : 102c (ExcCode 0b)
| [ 4390.618930] PrId : 0014c004 (ICT Loongson-3)
| [ 4390.623257] Modules linked in: asix usbnet mii sg ip6t_REJECT 
nf_reject_ipv6 ip6table_filter ip6_tables nfnetlink_log nfnetlink xt_hashlimit 
ipt_REJECT nf_reject_ipv4 xt_NFLOG xt_multiport xt_tcpudp xt_state xt_conntrack 
nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c iptable_filter sch_fq 
tcp_bbr fuse drm drm_panel_orientation_quirks configfs ip_tables x_tables 
autofs4 ext4 crc16 mbcache jbd2 crc32c_generic ohci_pci dm_mod r8169 realtek 
mdio_devres ohci_hcd ehci_pci of_mdio xhci_pci xhci_hcd ehci_hcd fixed_phy 
libphy usbcore usb_common
| [ 4390.671116] Process iou-sqp-22284 (pid: 24061, 
threadinfo=743a6e5b, task=63cca72a, tls=00fff0de98e0)
| [ 4390.681930] Stack : 80ed  80ed 
98020f6e8c40
| [ 4390.689897] 98020004 d37c8307c148dccb 9801017bb2c0 

| [ 4390.697863]  0001 90
| [ 4390.721759] 980104957480 98020f6e8c00  
80ed
| [ 4390.729724] 98020f6e8c40 98020f6e8c08  

| [ 4390.737689]  9801017bb2c0 802c61f8 
98020f6e8c48
| [ 4390.745655] 98020f6e8c48 2d7071732d756f69 003438323232 
d37c8307c148dccb
| [ 4390.753621] 807106e0 98020f6e8c00 9801097e90c8 
7400cce0
| [ 4390.761588] ...
| [ 4390.764017] Call Trace:
| [ 4390.766453] [] _save_fp+0x10/0xa0
| [ 4390.771306] [] __schedule+0x804/0xe08
| [ 4390.776497] [] schedule+0x58/0x150
| [ 4390.781432] [] io_sq_thread+0x550/0x578
| [ 4390.786798] [] ret_from_kernel_thread+0x14/0x1c
| [ 4390.792856]
| [ 4390.794330] Code: 000c6940 05a10011   f4830b10 f4850b30 
f4870b50 f4890b70 f48b0b90
| [ 4390.804038]
| [ 4411.502993] rcu: INFO: rcu_preempt self-detected stall on CPU
| [ 4411.508728] rcu: 1-...!: (5250 ticks this GP) 
idle=2c6/1/0x4002 softirq=1149627/1149627 fqs=4
| [ 4411.518413] (t=5254 jiffies g=735145 q=4914963)
| [ 4411.522999] rcu: rcu_preempt kthread starved for 5248 jiffies! g735145 
f0x2 RCU_GP_WAIT_FQS(5) ->state=0x200 ->cpu=2
| [ 4411.533458] rcu: Unless rcu_preempt kthread gets sufficient CPU time, OOM 
is now expected behavior.
| [ 4411.542535] rcu: RCU grace-period kthread stack dump:
| [ 4411.547552] task:rcu_preempt state:R stack: 0 pid: 13 ppid: 2 
flags:0x0010
| [ 4411.555860] Stack : 80ed 80bff978 80ed 
8031bbd4
| [ 4411.563826] 0004 d37c8307c148dccb 98010025 
00208040
| [ 4411.571791] 80ed 9801002c7c98 80ed 
80f62ce0
| [ 4411.579756]  0006 0001 
80bf98b8
| [ 4411.587721]  0001000f9aa0  
80bfdb98
| [ 4411.595686] 8030bbc8 5400cce1 80ed 

| [ 4411.603651] 98000236cc78 0001000f9aa0 80319968 
0842
| [ 4411.611617] 98010025 d37c8307c148dccb 80f62a80 

| [ 4411.619582] 80ed 80ed 80ecdce0 
8030b40c
| [ 4411.627548] 80ef11f0 80ed 811f 
80f6
| [ 4411.635515] ...
| [ 4411.637947] Call Trace:
| [ 4411.640384] [] __schedule+0x50c/0xe08
| [ 4411.645586] [] schedule+0x58/0x150
| [ 4411.650527] [] schedule_timeout+0x98/0x1e8
| [ 4411.656156] 

Bug#1055020: further informations

[cage]

Hi!

Maybe this reports could be useful someway:

https://savannah.gnu.org/bugs/?64748

Hope this helps!

Bye!
C.

Bug#1055020: gettext-el: Fails to visit PO files

[cage]

Package: gettext-el
Version: 0.21-13
Severity: important

Dear Maintainer,

visiting a PO files fails to  activate po-mode; no buffer is shown and
an error is printed instead on the minibuffer:

"po-find-file-coding-system-guts: Symbol's function definition is void: 
po-with-temp-buffer"

Thanks in advance!
C.


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

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

Versions of packages gettext-el depends on:
ii  dh-elpa-helper  2.0.17
ii  emacsen-common  3.0.5
ii  gettext 0.21-13+b1

gettext-el recommends no packages.

gettext-el suggests no packages.

-- no debconf information

Bug#1052859: geonames: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && make -j8 test ARGS\+=--verbose ARGS\+=-j8 VERBOSE=1 returned exit code 2

[Mike Gabriel]

Hi,

On  So 29 Okt 2023 11:17:21 CET, Mike Gabriel wrote:


Investigating deeper...


underlying cause that introduced this FTBFS in geonames is this patch  
[1] in glibc (added with glibc 2.37-8):


[1]  
https://salsa.debian.org/glibc-team/glibc/-/blob/sid/debian/patches/any/git-c-utf-8-language.diff


I just rebuilt 2.37-12 (glibc version currently in unstable) with that  
patch disabled in d/p/series and geonames builds fine again.


Cc:ing Aurelien Jarno who  cherry-picked that patch from upstream into  
the glibc Debian package.


@Aurelien: Any idea, what my cause the observed FTBFS in geonames (#1052859).

Mike
--

mike gabriel aka sunweaver (Debian Developer)
mobile: +49 (1520) 1976 148
landline: +49 (4351) 486 14 27

GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22  0782 9AF4 6B30 2577 1B31
mail: sunwea...@debian.org, http://sunweavers.net



pgplzv4YjSFbO.pgp
Description: Digitale PGP-Signatur

Bug#1054286: bookworm-pu: package python-cogent/2023.2.12a1+dfsg-2+deb12u1

[Santiago Vila]

Dear Release Managers:

Please reject the upload I made for bookworm.

Following the suggestion from Holger, I've fixed this issue
in the optimal way in unstable:

https://tracker.debian.org/news/1474401/accepted-python-cogent-2023212a1dfsg-4-source-into-unstable/

and now I'd like to upload the same fix for bookworm
using the "+deb12u1" version string.

(Not sure if this release.debian.org bug should then be closed so that
I submit it again, or it's better that we keep it open for the
new upload, please do what is more convenient for you).

Thanks.

Bug#1042572: claws-mail: can't update claws-mail to v4.1.1 from bullseye-backports

[Andreas Rönnquist]

I have now uploaded updated backported packages to mentors, that need
sponsoring to get into Debian (I am currently without a gpg-key, so I
need sponsoring to upload packages).

I have uploaded both an updated bullseye (11) version and a new
backport for Debian 12, to provide an upgrade path.

(I have pushed the branches to the salsa, and will tag the releases
when they enter Debian).

best
-- Andreas Rönnquist
gus...@debian.org

Bug#1053657: dhcpcd-base has ineffective Replaces due to /usr-merge and looses files in upgrade

[Martin-Éric Racine]

On Mon, Oct 9, 2023 at 10:00 AM Emilio Pozuelo Monfort  wrote:
>
> On 08/10/2023 08:15, Helmut Grohne wrote:
> > I'm sorry for not having spotted this before the point release and will
> > now monitor stable p-u suites for similar problems to raise this
> > earlier.
>
> Great, thanks.

I highly doubt that this was intoduced by the point release.

> > Can I assume that a package sits in p-u for at least three days
> > before migrating to a stable release?
>
> Yes, p-u is frozen about 5 or 6 days before the release. Exceptions can 
> happen,
> but excluding those you can assume that.

debdiff attached via previous message. If this looks good, I'll upload
and file the unblock request.

Martin-Éric

Bug#1054233: liblilv-0-0: Package does not follow FHS, it adds /usr/lib/$(DEB_HOST_MULTIARCH) to the --default-lv2-path waf configure option, see rules file, line 21.

[Sebastian Ramacher]

Control: tags -1 moreinfo

On 2023-10-19 17:51:33 +0200, Jeremy Jongepier wrote:
> Package: liblilv-0-0
> Version: 0.24.14-1
> Severity: important
> 
> Package does not follow FHS, it adds /usr/lib/$(DEB_HOST_MULTIARCH) to the 
> --default-lv2-path waf configure option, see rules file, line 21. The 
> addition of this line indicates that something fundamental has changed, 
> namely the default path where Debian installs its LV2 plugins. These go into 
> /usr/lib/$(DEB_HOST_MULTIARCH) too now which breaks setups running software 
> that uses the FHS as a starting point for LV2 plugin discovery. The LV2 
> plugin packages that Debian now installs are now not discovered anymore.

I think you are mistaken. It you compare the the default path in
meson.build and the one specified in debian/rules, it extends the
default path with /usr/lib/$(DEB_HOST_MULTIARCH)/lv2 (note the lv2).

Please describe the actual problem that you are seeing.

Cheers
-- 
Sebastian Ramacher

Bug#1055016: override: tasksel-data:admin/optional

[Cyril Brulebois]

Daniel Lewart  (2023-10-29):
> Package: ftp.debian.org
> Severity: normal
> User: ftp.debian@packages.debian.org
> Usertags: override
> X-Debbugs-Cc: task...@packages.debian.org, debian-b...@lists.debian.org, 
> 855...@bugs.debian.org, 954...@bugs.debian.org
> Control: affects -1 + src:tasksel
> 
> FTP Team,
> 
> #855151 - tasksel: should not be Priority: important
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=855151
> 
> #954090 - override: tasksel:admin/optional
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954090
> 
> However, tasksel is still installed by default because of the following:
> $ apt-cache show tasksel-data | grep -E '^(Package|Depends|Priority)'
> Package: tasksel-data
> Depends: tasksel (= 3.73)
> Priority: important
> 
> Please change tasksel-data from:
> admin/important
> to:
> admin/optional

It's probably safe since pkgsel's postinst features:

if db_get pkgsel/run_tasksel && [ "$RET" = true ]; then
log "starting tasksel"
db_progress INFO pkgsel/progress/tasksel
apt-install tasksel  # ensure tasksel is installed


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature

Bug#1055019: RM: ffmpeg2theora -- RoQA; dead upstream, missed bookworm, RC buggy

[Sebastian Ramacher]

Package: ftp.debian.org
Severity: normal
User: ftp.debian@packages.debian.org
Usertags: remove
X-Debbugs-Cc: ffmpeg2the...@packages.debian.org, sramac...@debian.org
Control: affects -1 + src:ffmpeg2theora

ffmpeg2theora is RC buggy (see #1013423) and thus missed the bookworm
release. As it's also dead upstream (homepage is 404), please remove it
from unstable.

Cheers
-- 
Sebastian Ramacher

Bug#1055007: additional information

[Denis Prost]

Sorry I posted the previous message from a wrong email address.

On Sun, 29 Oct 2023 11:40:58 +0100 
=?UTF-8?Q?Gall=C3=A9co_Pays_de_Redon?=  wrote:


> the report says that /etc/NetworkManager/NetworkManager.conf changed,
> but I reset it to an empty file as it is when network-manager is
> installed and the nmcli commands results was the same.
>
>
>

Bug#1055018: RFS: claws-mail/4.1.1-4~bpo12+1 -- Fast, lightweight and user-friendly GTK based email client

[Andreas Rönnquist]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "claws-mail":
(Please also see my upload to mentors of claws-mail to 
bullseye-backports-sloppy).

 * Package name : claws-mail
   Version  : 4.1.1-4~bpo12+1
   Upstream contact : https://www.claws-mail.org
 * URL  : https://www.claws-mail.org
 * License  : GPL-2+, BSD-3-clause-EP, GPL-3+, Apache
 * Vcs  : https://salsa.debian.org/claws-mail-team/claws-mail
   Section  : mail

The source builds the following binary packages:

  claws-mail - Fast, lightweight and user-friendly GTK based email client
  libclaws-mail-dev - Development files for Claws Mail plugins
  claws-mail-plugins - Installs plugins for the Claws Mail mailer
  claws-mail-spamassassin - SpamAssassin plugin for Claws Mail
  claws-mail-pgpmime - PGP/MIME plugin for Claws Mail
  claws-mail-pgpinline - PGP/inline plugin for Claws Mail
  claws-mail-smime-plugin - S/MIME signature/encryption handling for Claws Mail
  claws-mail-bogofilter - Bogofilter plugin for Claws Mail
  claws-mail-i18n - Locale data for Claws Mail (i18n support)
  claws-mail-doc - User documentation for Claws Mail mailer
  claws-mail-tools - Helper and utility scripts for Claws Mail mailer
  claws-mail-extra-plugins - Extra plugins collection for Claws Mail
  claws-mail-acpi-notifier - Laptop's Mail LED control for Claws Mail
  claws-mail-address-keeper - Address keeper plugin for Claws Mail
  claws-mail-archiver-plugin - Archiver plugin for Claws Mail
  claws-mail-attach-remover - Mail attachment remover for Claws Mail
  claws-mail-attach-warner - Missing attachment warnings for Claws Mail
  claws-mail-bsfilter-plugin - Spam filtering using bsfilter for Claws Mail
  claws-mail-clamd-plugin - ClamAV socket-based plugin for Claws Mail
  claws-mail-dillo-viewer - HTML viewer plugin for Claws Mail using Dillo
  claws-mail-fancy-plugin - HTML mail viewer using GTK WebKit
  claws-mail-feeds-reader - Feeds (RSS/Atom/RDF) reader plugin for Claws Mail
  claws-mail-fetchinfo-plugin - Add X-FETCH headers plugin for Claws Mail
  claws-mail-gdata-plugin - Access to GData (Google services) for Claws Mail
  claws-mail-keyword-warner - Warning on message keywords for Claws Mail
  claws-mail-libravatar - Display sender avatar from a libravatar server
  claws-mail-litehtml-viewer - HTML viewer plugin using litehtml library
  claws-mail-newmail-plugin - New mail logger plugin for Claws Mail
  claws-mail-mailmbox-plugin - mbox format mailboxes handler for Claws Mail
  claws-mail-managesieve - manage Sieve filters with Claws Mail
  claws-mail-multi-notifier - Various new mail notifiers for Claws Mail
  claws-mail-tnef-parser - TNEF attachment handler for Claws Mail
  claws-mail-perl-filter - Message filtering plugin using perl for Claws Mail
  claws-mail-pdf-viewer - PDF and PostScript attachment viewer for Claws Mail
  claws-mail-python-plugin - Python plugin and console for Claws Mail
  claws-mail-spam-report - Spam reporting plugin for Claws Mail
  claws-mail-vcalendar-plugin - vCalendar message handling plugin for Claws Mail

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

  https://mentors.debian.net/package/claws-mail/

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

  dget -x 
https://mentors.debian.net/debian/pool/main/c/claws-mail/claws-mail_4.1.1-4~bpo12+1.dsc

Changes since the last upload:

 claws-mail (4.1.1-4~bpo12+1) bookworm-backports; urgency=medium
 .
   * Rebuild for bookworm-backports.
 .
 claws-mail (4.1.1-4) unstable; urgency=medium
 .
   * Fix typo in changelog (thanks lintian!)
   * Remove obsolete news file
   * Set Standards-Version to 4.6.2 with no other changes
   * Update copyright year ranges
 .
 claws-mail (4.1.1-3) unstable; urgency=high
 .
   [ David (Plasma) Paul ]
   * Move documentation Build-Depends to Build-Depends-Indep (Closes: #1036898)
 .
   [ Ricardo Mones ]
   * Revert "Remove bsfilter plugin for testing migration"
   * Add upstream patch to fix build with gcc 13 (Closes: #1037605)
   * Raised urgency because of RC bug

Regards,
-- 
  Andreas Rönnquist

Bug#1054567: ocserv: Compilation error on the LoongArch architecture

[wuruilong]

在 2023/10/26 下午2:47, Aron Xu 写道:

Hi,


On Oct 26, 2023, at 10:54, wuruilong  wrote:

Source: ocserv
Version: 1.2.1-1
Severity: normal
X-Debbugs-Cc: wuruil...@loongson.cn

Dear Maintainer,

  There is a compilation error for ocserv on the loongarch machine.
Tested the patch attached to the email on the LoongArch machine and it resolved 
the issue.


I see the patch is quite straightforward, would you mind submit it to upstream, 
too?

Cheers,
Aron


Hi,

I encountered an issue with duplicate email registration on the upstream 
GitLab, and it will take three days to resolve.
After addressing this problem, I will proceed to submit the code to the 
upstream.

wuruilong

Bug#1055017: node-html-webpack-plugin_5.5.3+~cs14.4.8-1_all-buildd.changes REJECTED

[Aurelien Jarno]

Source: node-html-webpack-plugin
Version: 5.5.3+~cs14.4.8-1
Severity: serious

On 2023-10-29 04:49, Debian FTP Masters wrote:
> 
> 
> Version check failed:
> Your upload included the binary package node-html-minifier-terser, version 
> 5.5.3+~cs14.4.8-1, for all,
> however unstable already has version 7.2.0~5.5.3+~cs14.4.7-2.
> Uploads to unstable must have a higher version than present in unstable.
> 
> Mapping sid to unstable.
> 
> ===
> 
> Please feel free to respond to this email if you don't understand why
> your files were rejected, or if you upload new files which address our
> concerns.
> 
> 
> 

Bug#1055016: override: tasksel-data:admin/optional

[Daniel Lewart]

Package: ftp.debian.org
Severity: normal
User: ftp.debian@packages.debian.org
Usertags: override
X-Debbugs-Cc: task...@packages.debian.org, debian-b...@lists.debian.org, 
855...@bugs.debian.org, 954...@bugs.debian.org
Control: affects -1 + src:tasksel

FTP Team,

#855151 - tasksel: should not be Priority: important
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=855151

#954090 - override: tasksel:admin/optional
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954090

However, tasksel is still installed by default because of the following:
$ apt-cache show tasksel-data | grep -E '^(Package|Depends|Priority)'
Package: tasksel-data
Depends: tasksel (= 3.73)
Priority: important

Please change tasksel-data from:
admin/important
to:
admin/optional

Thank you!
Daniel Lewart
Urbana, Illinois

Bug#1055015: zotero.desktop entry is not showing in the app launcher

[Emin Inan]

Package: libglib2.0-0
Version: 2.74.6-2

Zotero app does not show up in the App Launcher. I confirm zotero.desktop 
exists in /usr/share/applications/ after the install. My workaround is to 
rename the zotero.desktop file to zotero_2.desktop. Same file contents. 
However, when the file name is something other than zotero.desktop, the Zotero 
app properly show up in the app launcher.

Please refer to the following Github issue for background:

https://github.com/retorquere/zotero-deb/issues/92

I am using Debian 12, kernel 6.3, and GNOME 43.

Bug#1055014: RFS: streamlink/6.3.1-1 -- CLI for extracting video streams from various websites to a video player

[Alexis Murzeau]

Package: sponsorship-requests
Severity: normal


Dear mentors,

I am looking for a sponsor for my package "streamlink" for a new
upstream version 6.3.1.

  * Package name: streamlink
Version : 6.3.1-1
Upstream Author : Streamlink Team
  * URL : https://streamlink.github.io/
  * License : BSD-2-clause, Apache-2.0, MIT/Expat, SIL-OFL-1.1
  * Vcs : https://salsa.debian.org/amurzeau/streamlink/
Section : python

It builds those binary packages:
  python3-streamlink - Python module for extracting video streams from
various websites
  python3-streamlink-doc - CLI for extracting video streams from
various websites (documentation)
  streamlink - CLI for extracting video streams from various websites
to a video player


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

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

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

  dget -x 
https://mentors.debian.net/debian/pool/main/s/streamlink/streamlink_6.3.1-1.dsc


Changes since the last upload to unstable:
streamlink (6.3.1-1) unstable; urgency=medium

  * New upstream version 6.3.1

 -- Alexis Murzeau   Sun, 29 Oct 2023 10:28:08 +0100

Regards,

--
Alexis Murzeau
PGP: B7E6 0EBB 9293 7B06 BDBC  2787 E7BD 1904 F480 937F |

Bug#1055013: RFS: claws-mail/4.1.1-4~bpo11+1 -- Fast, lightweight and user-friendly GTK based email client

[Andreas Rönnquist]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "claws-mail":
(Please also see my mentors upload for bookworm-backports of the same package).

 * Package name : claws-mail
   Version  : 4.1.1-4~bpo11+1
   Upstream contact : https://www.claws-mail.org
 * URL  : https://www.claws-mail.org
 * License  : GPL-2+, BSD-3-clause-EP, GPL-3+, Apache
 * Vcs  : https://salsa.debian.org/claws-mail-team/claws-mail
   Section  : mail

The source builds the following binary packages:

  claws-mail - Fast, lightweight and user-friendly GTK based email client
  libclaws-mail-dev - Development files for Claws Mail plugins
  claws-mail-plugins - Installs plugins for the Claws Mail mailer
  claws-mail-spamassassin - SpamAssassin plugin for Claws Mail
  claws-mail-pgpmime - PGP/MIME plugin for Claws Mail
  claws-mail-pgpinline - PGP/inline plugin for Claws Mail
  claws-mail-smime-plugin - S/MIME signature/encryption handling for Claws Mail
  claws-mail-bogofilter - Bogofilter plugin for Claws Mail
  claws-mail-i18n - Locale data for Claws Mail (i18n support)
  claws-mail-doc - User documentation for Claws Mail mailer
  claws-mail-tools - Helper and utility scripts for Claws Mail mailer
  claws-mail-extra-plugins - Extra plugins collection for Claws Mail
  claws-mail-acpi-notifier - Laptop's Mail LED control for Claws Mail
  claws-mail-address-keeper - Address keeper plugin for Claws Mail
  claws-mail-archiver-plugin - Archiver plugin for Claws Mail
  claws-mail-attach-remover - Mail attachment remover for Claws Mail
  claws-mail-attach-warner - Missing attachment warnings for Claws Mail
  claws-mail-bsfilter-plugin - Spam filtering using bsfilter for Claws Mail
  claws-mail-clamd-plugin - ClamAV socket-based plugin for Claws Mail
  claws-mail-dillo-viewer - HTML viewer plugin for Claws Mail using Dillo
  claws-mail-fancy-plugin - HTML mail viewer using GTK WebKit
  claws-mail-feeds-reader - Feeds (RSS/Atom/RDF) reader plugin for Claws Mail
  claws-mail-fetchinfo-plugin - Add X-FETCH headers plugin for Claws Mail
  claws-mail-gdata-plugin - Access to GData (Google services) for Claws Mail
  claws-mail-keyword-warner - Warning on message keywords for Claws Mail
  claws-mail-libravatar - Display sender avatar from a libravatar server
  claws-mail-litehtml-viewer - HTML viewer plugin using litehtml library
  claws-mail-newmail-plugin - New mail logger plugin for Claws Mail
  claws-mail-mailmbox-plugin - mbox format mailboxes handler for Claws Mail
  claws-mail-managesieve - manage Sieve filters with Claws Mail
  claws-mail-multi-notifier - Various new mail notifiers for Claws Mail
  claws-mail-tnef-parser - TNEF attachment handler for Claws Mail
  claws-mail-perl-filter - Message filtering plugin using perl for Claws Mail
  claws-mail-pdf-viewer - PDF and PostScript attachment viewer for Claws Mail
  claws-mail-python-plugin - Python plugin and console for Claws Mail
  claws-mail-spam-report - Spam reporting plugin for Claws Mail
  claws-mail-vcalendar-plugin - vCalendar message handling plugin for Claws Mail

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

  https://mentors.debian.net/package/claws-mail/

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

  dget -x 
https://mentors.debian.net/debian/pool/main/c/claws-mail/claws-mail_4.1.1-4~bpo11+1.dsc

Changes since the last upload:

 claws-mail (4.1.1-4~bpo11+1) bullseye-backports-sloppy; urgency=medium
 .
   * Rebuild for bullseye-backports-sloppy.
 .
 claws-mail (4.1.1-4) unstable; urgency=medium
 .
   * Fix typo in changelog (thanks lintian!)
   * Remove obsolete news file
   * Set Standards-Version to 4.6.2 with no other changes
   * Update copyright year ranges
 .
 claws-mail (4.1.1-3) unstable; urgency=high
 .
   [ David (Plasma) Paul ]
   * Move documentation Build-Depends to Build-Depends-Indep (Closes: #1036898)
 .
   [ Ricardo Mones ]
   * Revert "Remove bsfilter plugin for testing migration"
   * Add upstream patch to fix build with gcc 13 (Closes: #1037605)
   * Raised urgency because of RC bug
 .
 claws-mail (4.1.1-2~bpo11+1) bullseye-backports; urgency=medium
 .
   * Rebuild for bullseye-backports.
 .
 claws-mail (4.1.1-2) unstable; urgency=medium
 .
   [ Vagrant Cascadian ]
   * debian/rules: Use UTC for manpage date.
 .
   [ Ricardo Mones ]
   * Remove bsfilter plugin for testing migration
 .
 claws-mail (4.1.1-1) unstable; urgency=medium
 .
   [ Andreas Rönnquist ]
   * Fix typo in manpage for keyword-warner
 .
   [ Ricardo Mones ]
   * New upstream version 4.1.1
   * Remove patches already in this upstream release
   * Install new fancywebextension into fancy plugin
   * Use same version for all manpages
   * Use a fixed date for all manpages
   * Set Stantards-Version to 4.6.1, no other changes
   * Remove obsolete pattern from copyright
   * Adjust lintian override
   * Remove lintian 

Bug#1054323: r-cran-tmb: autopkgtest needs update for new version of rmatrix: Package version inconsistency detected

[Graham Inggs]

Control: found -1 1.9.6-2

> still depends on:
> r-cran-matrix (>= 1.6-1.1)
>
> So the version is still not correct.

Note that this is Depends, not Build-Depends.

I found that in debian/control, r-cran-tmb has Depends:
r-cran-matrix (>= 1.5-3-1~), but this is somehow replaced in the
binary package, presumably by dh-r?

Andreas, would it be possible for dh-r to always replace the version
in r-cran-tmb's Depends with r-cran-matrix (>= [the version of
r-cran-matrix it was built with]) ?

Then you can avoid modifying Build-Depends and upstream's DESCRIPTION,
and will allow r-cran-tmb to be binNMU'd when needed.  It should also
allow for easier backporting.

Regards
Graham

Bug#1054777: Fwd: Bug#1054777: libfiu: FTBFS: dh_auto_test: error: make -j8 test V=1 LC_ALL=C returned exit code 2

[Alberto Bertogli]

On Sat, Oct 28, 2023 at 09:58:14AM +0100, Chris Lamb wrote:

Hey Alberto,

Hope all is well with you. Just wondering if you received the below
re. a recently-filed bug report against libfiu. I can reproduce it
locally if that helps.


I got it, but I appreciate you forwarding it explicitly anyway just in 
case, and the confirmation of a reproduction!




./wrap-python 3 ./test-basic.py
Can't find python3 bindings, run make python3
make[3]: *** [Makefile:96: py-run-test-basic] Error 1


Looking at this, I don find any issues with the Makefile dependency 
chain itself.


I think this is likely a problem I already fixed back in February in 
commit 5dcc6d4.


https://blitiri.com.ar/git/r/libfiu/c/5dcc6d449dc86d4ba9abc99ac52fd5798e573738/

There have been a few commits since v1.1, I think a v1.2 is probably 
overdue at this point in any case.


Chris, do you want to confirm that patch fixes the issue in the Debian 
build environment? And if so I can just make a 1.2 including it. Do you 
think that would be the most practical course of action here?


Thank you!
Alberto

Bug#1055007: additional information

[Galléco Pays de Redon]

the report says that /etc/NetworkManager/NetworkManager.conf changed, 
but I reset it to an empty file as it is when network-manager is 
installed and the nmcli commands results was the same.

Bug#940511: [Pkg-javascript-devel] Bug#940511: Our mutual interest in /usr/bin/yarn

[Pirate Praveen]

On Mon, 21 Nov 2022 09:39:31 +0100 "Yadd"  wrote:

I don't think that "Provides: yarn" is a good thing here since "/usr/bin/yarn" isn't 
provided by yarnpkg. "Provides: node-yarn" seems enough here and without any consequences.


As a compromise, can we have a debconf prompt to notify users about this 
conflict and to run


sudo ln -s /usr/bin/yarnpkg /usr/bin/yarn

if they want to use yarn command.

Automating this via a postinst may be a good idea too, but not sure if 
that is allowed by policy. May be we can ask for an exception since this 
is a special case. This way people who want to use yarn command has a 
way to do it easily.


Prompting users is a bad idea in general if we can have good defaults, 
but we don't have much options left here.


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1054642: Failing ARP relay from external -> Linux bridge -> veth port --> NS veth port

[Daniel Gröber]

Hi Peter,

On Fri, Oct 27, 2023 at 09:29:25AM +, peter.gasparo...@orange.com wrote:
> No attempt at all? Then it's against your own rules I've read before
> submitting this.

I think Luca was a bit harsh here, I'd be happy to help debug this. From a
first look it seems unlikely this is related to iproute2, smells more like
a kernel issue to me, but either way we need a reproducer.

So first step to move this forward is to put together a self contained set
of instructions to reproduce the problem. Your original report is a bit
sparse on context and details.

If you don't feel up to compiling the reproducer script yourself you could
start by showing us your system state using

$ ip -d addr show   # on the host and inside the NS if you could
$ bridge -d link; bridge fdb

snippets from /etc/network/interfaces or similar relevant config would help
too.

--Daniel


signature.asc
Description: PGP signature

Bug#1055012: ITP: libnginx-mod-vts -- Nginx virtual host traffic status module

[Gregor Jasny]

Package: wnpp
Severity: wishlist
Owner: Gregor Jasny 
X-Debbugs-Cc: debian-de...@lists.debian.org, 
pkg-nginx-maintain...@alioth-lists.debian.net

* Package name: libnginx-mod-vts
  Version : 0.2.2
  Upstream Contact: YoungJoo.Kim (김영주) 
* URL : https://github.com/vozlt/nginx-module-vts
* License : BSD-2-Clause
  Programming Lang: C
  Description : Nginx virtual host traffic status module

This package enables easy monitoring of nginx instances with
telegraf [1]. We use it in production since a very long time
and would like to switch from a locally built package to one
maintained by the distribution.

Maintaining this package seems to be low-effort. I could
maintain it on my own or join forces with the Debian
nginx maintainers.

Thanks,
Gregor

[1] 
https://github.com/influxdata/telegraf/blob/master/plugins/inputs/nginx_vts/README.md

Bug#1053347: newer 6.5 kernels still don't work on Dell T140

[Ivan Sergio Borgonovo]

Hi,

problem still persist with linux-image-6.5.0-3-amd64

BTW I don't know if since the package changed name it is still the right 
place to report any update.


thanks

--
Ivan Sergio Borgonovo
https://www.webthatworks.it https://www.borgonovo.net