Bug#1053729: RFP: SAIL image decoding library

[Andrius Merkys]

Hi Dmitry,

On 2023-10-17 16:25, Dmitry Baryshev wrote:

 > Does it produce desired Debian packages?

I've just pushed a couple of fixes to the Debian rules. I'm able to 
build packages on LUbuntu 23.04. Maybe a couple of small fixes are still 
needed to build packages on Debian. So the recommended git sha to use is 
4705cb4cf96. It's a release candidate and ready to use in client 
applications.


In Debian the common practice is to separate the upstream repository 
(i.e., the package source) from packaging repository (i.e., where Debian 
packaging instructions are being developed). Common practice is to host 
the latter on salsa.debian.org, usually together with the package 
source. Thus I would suggest following this approach. I have put a short 
guide about how to do that [1].



 > Are these packages lintian-clean?

The only error Lintian showed is "unknown distribution", but this is 
because I run it on Ubunutu.


Right.

 > Do you know any software already in Debian which would benefit from 
having SAIL in Debian?


It's a library and I guess end users will benefit from it.


OK, makes sense.

Since this is an image decoding library, my personal opinion is that it 
would better fit the scope of Debian Multimedia Team instead of Debian 
Science Team.


[1] https://wiki.debian.org/AndriusMerkys/PackagingInSeconds

Best wishes,
Andrius

Bug#1054074: update

[Jens Rapp]

Now, two days after, touchpad works normal again. Why? Don't know which
is worse than if it still wouldn't work.

what happened?

seems there is another bug: when I happen to plug the usb-c charger
while in standby, system crashes after wakeup. After rebooting,
everything was fine with the touchpad. Maybe just a coincidence?

dmesg shows this now:

$ sudo dmesg | grep -i mouse
[    1.886340] mousedev: PS/2 mouse device common for all mice
[    2.689681] psmouse serio1: elantech: assuming hardware version 4
(with firmware version 0x5f3001)
[    2.704141] psmouse serio1: elantech: Synaptics capabilities query
result 0x90, 0x18, 0x10.
[    2.719334] psmouse serio1: elantech: Elan sample query result 00, 1b, 97
[    2.734455] psmouse serio1: elantech: Elan ic body: 0x14, current fw
version: 0x2
[    2.764542] psmouse serio1: elantech: Trying to set up SMBus access

Bug#1053912: transition: alglib

[Anton Gladky]

Hi Sebastian,

uploaded, thanks!

Anton


Am Di., 17. Okt. 2023 um 17:37 Uhr schrieb Sebastian Ramacher <
sramac...@debian.org>:

> Control: tags -1 confirmed
> Control: forwarded -1
> https://release.debian.org/transitions/html/auto-alglib.html
>
> Hi Anton
>
> On 2023-10-14 09:59:15 +0200, Anton Gladky wrote:
> > Please schedule the transition of alglib. All reverse dependencies are
> built and fine.
>
> Please go ahead.
>
> Cheers
> --
> Sebastian Ramacher
>

Bug#1054147: libgraphics-magick-perl: Cannot find fonts after gsfonts transition

[phil]

Package: libgraphics-magick-perl
Version: 1.4+really1.3.40-4
Severity: normal

Dear Maintainer,

With the transition from gsfonts -> fonts-urw-base35, fonts have moved and 
libgraphics-magick-perl (or maybe underlying libimage-magick? I can't tell), 
can't find fonts. When you generate images with text you get:

```
Exception 405: Unable to read font (/usr/share/fonts/type1/gsfonts/n022004l.pfb)
```

The directory `/usr/share/fonts/type1/gsfonts` no longer belongs to any 
package, though it existed and was almost-empty (except for a `.uuid` file) on 
my machine due to the transition.


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

Kernel: Linux 6.2.9-x86_64-linode160 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages libgraphics-magick-perl depends on:
ii  libc6   2.36-9+deb12u3
ii  libgraphicsmagick-q16-3 1.4+really1.3.40-4
ii  perl5.36.0-7
ii  perl-base [perlapi-5.36.0]  5.36.0-7

libgraphics-magick-perl recommends no packages.

Versions of packages libgraphics-magick-perl suggests:
pn  graphicsmagick-dbg  

-- no debconf information

Bug#1054101: webkit2gtk: No provider of eglCreateImage found. Requires one of: EGL 15, yelp can't start

[肖盛文]

在 2023/10/18 06:48, Alberto Garcia 写道:

On Tue, Oct 17, 2023 at 10:39:45AM +0800, xiao sheng wen wrote:

No provider of eglCreateImage found.  Requires one of:
 EGL 15
Aborted

Do you have the egl library installed?

Yes.

There are following egl packages already installed in my OS:

dpkg -l|grep egl
ii  libegl-mesa0:amd64 20.3.5-1 amd64    
free implementation of the EGL API -- Mesa vendor library
ii  libegl1:amd64 1.3.2-1  amd64    
Vendor neutral GL dispatch library -- EGL support
ii  libegl1-mesa:amd64 20.3.5-1 amd64    
transitional dummy package
ii  libgegl-0.4-0:amd64 1:0.4.26-2   
amd64    Generic Graphics Library
ii  libgegl-common 1:0.4.26-2   all  
Generic Graphics Library - common files
ii  libwayland-egl++0:amd64 0.2.8-1  
amd64    wayland compositor infrastructure - EGL library C++ bindings
ii  libwayland-egl1:amd64 1.18.0-2~exp1.1  
amd64    wayland compositor infrastructure - EGL library
ii  libwayland-egl1-mesa:amd64 20.3.5-1 
amd64    transitional dummy package





Berto

Thanks!

--
肖盛文 xiao sheng wen
https://www.atzlinux.com 《铜豌豆 Linux》基于 Debian 的 Linux 中文 桌面 操作系统
Debian QA page: https://qa.debian.org/developer.php?login=atzlinux%40sina.com
Debian salsa: https://salsa.debian.org/atzlinux-guest
GnuPG Public Key: 0x00186602339240CB



OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1054043: texlive: Texlive updates are too large

[Stefan Monnier]

>>  Stefan "dreaming of Debian updates as efficient as
>>  `git fetch` :-)"
> You are not the first one, who complains and (probably) not the last
> one.  Due to the limited man power in the team, we simply copy the
> packaging scheme given by TeX Live upstream and this is what you
> see here.

Indeed, I think the "fix" should probably be in the generic Debian
infrastructure rather than in any specific (set of) packages.

At most, the package maintainers might need to activate a special flag
telling that delta-encoding this package should be done by default.

> I'm aware of an idea called debdelta[1], maybe it is helpful for you.

Oh, that's indeed very interesting.  I hadn't heard of it yet.
It's very close to what I was thinking Debian should do.
And now I wonder why this is not better integrated into Debian so it's
used by default for packages like `texlive-fonts-extra`.
It could reduce the bandwidth load on Debian servers and even
potentially reduce the disk space used as well (if some .deb are deleted
in favor of deltas).


Stefan

Bug#1054146: nmu: libalien-wxwidgets-perl_0.69+dfsg-6+b2

[Scott Talbert]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu
X-Debbugs-Cc: libalien-wxwidgets-p...@packages.debian.org
Control: affects -1 + src:libalien-wxwidgets-perl

nmu libalien-wxwidgets-perl_0.69+dfsg-6+b2 . ANY . unstable . -m "Rebuild 
against libwxgtk3.2-dev 3.2.3+dfsg-1"

Bug#1052510: Ping: Bug#1052510: abook: double free detected in tcache 2

[Alejandro Colomar]

Ping

On Sat, Sep 23, 2023 at 04:53:18PM +0200, Alejandro Colomar wrote:
> Package: abook
> Version: 0.6.1-3
> Severity: normal
> Tags: upstream
> X-Debbugs-Cc: a...@kernel.org
> 
> Dear Maintainer,
> 
> abook(1) is freeing twice.  I can reproduce it with the following
> address book and command.
> 
> $ cat ./ab
> # abook addressbook file
> 
> [format]
> program=abook
> version=0.6.1
> 
> 
> [0]
> name=John Smith
> email=j...@example.com
> mobile=123123123
> nick=j
> groups=friends
> 
> 
> $ abook --convert --outformat mutt --infile ./ab
> alias -group \��L�friends j John Smith 
> free(): double free detected in tcache 2
> Aborted
> 
> 
> Thanks,
> Alex
> 
> 
> -- System Information:
> Debian Release: trixie/sid
>   APT prefers testing
>   APT policy: (500, 'testing'), (1, 'experimental')
> Architecture: amd64 (x86_64)
> 
> Kernel: Linux 6.4.0-4-amd64 (SMP w/24 CPU threads; PREEMPT)
> Locale: LANG=C.utf8, LC_CTYPE=C.utf8 (charmap=UTF-8), LANGUAGE not set
> Shell: /bin/sh linked to /usr/bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled
> 
> Versions of packages abook depends on:
> ii  debconf [debconf-2.0]  1.5.82
> ii  libc6  2.37-8
> ii  libncursesw6   6.4+20230625-2
> ii  libreadline8   8.2-1.3
> ii  libtinfo6  6.4+20230625-2
> 
> abook recommends no packages.
> 
> abook suggests no packages.
> 
> -- debconf information excluded

-- 



signature.asc
Description: PGP signature

Bug#1054145: libtk-img: undefined symbol: jpeg_std_huff_table

[ofv]

Package: libtk-img
Version: 1:1.4.15+dfsg-2
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: o...@wanadoo.es

Dear Maintainer,

$ wish
% package require img::jpeg
couldn't load file 
"/usr/lib/tcltk/x86_64-linux-gnu/Img1.4.15/libjpegtcl9.5.0.so": 
/usr/lib/tcltk/x86_64-linux-gnu/Img1.4.15/libjpegtcl9.5.0.so: undefined symbol: 
jpeg_std_huff_table
% 

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

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

Versions of packages libtk-img depends on:
ii  libc6 2.37-12
ii  libjpeg62-turbo   1:2.1.5-2
ii  libpng16-16   1.6.40-2
ii  libtiff6  4.5.1+git230720-1
ii  libtk8.6 [libtk]  8.6.13-2
ii  libx11-6  2:1.8.7-1
ii  zlib1g1:1.2.13.dfsg-3

libtk-img recommends no packages.

Versions of packages libtk-img suggests:
pn  libtk-img-doc  

-- no debconf information

Bug#851042: molds: FTBFS: liblapacke.so: undefined reference to `sgemqr_'

[Santiago Vila]

Hello.

I have successful build logs for "molds" in bullseye,
bookworm, and trixie.

I don't quite understand how a bug may be both
"ftbfs" and "wontfix". In my opinion, the bug
reported by Lucas Nussbaum is fixed and may be
closed.

OTOH, if this bug is being kept open to track something
different (what Graham Inggs called "a recurring problem"
in a previous message), maybe it would make sense to
retitle at least.

Thanks.

Bug#1054101: webkit2gtk: No provider of eglCreateImage found. Requires one of: EGL 15, yelp can't start

[Alberto Garcia]

On Tue, Oct 17, 2023 at 10:39:45AM +0800, xiao sheng wen wrote:
> No provider of eglCreateImage found.  Requires one of:
> EGL 15
> Aborted

Do you have the egl library installed?

Berto

Bug#1040057: python3.11: segmentation fault triggered by slixmpp unittest suite

[Martin]

Control: clone -1 -2
Control: reassign -1 src:python3.11
Control: retitle -2 slixmpp: meaningless autopkg tests
Control: reassign -2 src:slixmpp

Yes, the autopkg tests need rework for sure. Thanks for pointing out its
deficiencies! But that's a different bug, therefore I cloned it.

The (assumed) bug in Python 3.11 can be triggered without the slixmpp
Debian package and without any autopkg tests on amd64:

$ wget https://codeberg.org/poezio/slixmpp/archive/slix-1.8.4.tar.gz
$ tar xzf slix-1.8.4.tar.gz
$ cd slixmpp/
$ python3.11 -m pdb ./run_tests.py tests/test_stanza_error.py
...
(Pdb) r
...
(Pdb) quit
Segmentation fault

With python3.12, the segfault is gone.

Bug#831233: libmongodb-perl: build hangs with sbuild and libeatmydata

[Santiago Vila]

Version: 2.2.2-1

Hello. I can build libmongodb-perl using eatmydata at
least since bullseye. Closing with bullseye version.

Thanks.

Bug#917656: libnet-server-mail-perl: FTBFS (failing tests)

[Santiago Vila]

Hello.

According to my build logs, libnet-server-mail-perl (the
affected package against which I initially reported this)
seems to be buildable without errors (not even random) at least since buster.

In normal circumstances I would just go ahead and close the
bug, but due to the multiple reassigns I'm not confident enough,
so I leave it to you.

Thanks.

Bug#787462: libfile-sync-perl: FTBFS with perl 5.22

[Santiago Vila]

El 5/6/15 a las 0:22, Dominic Hargreaves escribió:

Retitling/downgrading accordingly. I guess it's worth keeping open
if only so that it doesn't confuse anyone else, even if it's not
really a bug in the package.


Hello. According to my build logs, this package builds ok with
eatmydata at least since bullseye, so I'd suggest to close the bug.

Thanks.

Bug#1054143: davical: Commiting a recuring event with start date before 1/1/1900 end up in a HTTP error 500

[Benedikt Spranger]

Package: davical
Version: 1.1.12-2
Severity: important
Tags: upstream

Dear Maintainer,

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

   * What led up to the situation?
 Try to update an event with a starting date before 1/1/1900

   * What exactly did you do (or not do) that was effective (or
 ineffective)?
 Create a recuring event in a calendar software with starting date
 09/19/1897

   * What was the outcome of this action?
 davical: BUG: :DAViCal Fatal Error: [42804] SQLSTATE[42804]:
 Datatype mismatch: 7 ERROR:  column "dtstart_orig" is of type
 timestamp with time zone but expression is of type integer

   * What outcome did you expect instead?
 davical add/update the event in the user calendar

*** End of the template - remove these template lines ***

I send a merge request with a fix to the upstream project:
https://gitlab.com/davical-project/davical/-/merge_requests/116

Regards
Benedikt Spranger

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

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

Versions of packages davical depends on:
ii  libawl-php0.64-1
ii  libdbd-pg-perl3.17.0-1
ii  libyaml-perl  1.30-2
ii  perl  5.36.0-9
ii  php   2:8.2+93
ii  php-pgsql 2:8.2+93
ii  php-xml   2:8.2+93
ii  php8.2 [php]  8.2.10-2
ii  php8.2-cli [php-cli]  8.2.10-2
ii  php8.2-pgsql [php-pgsql]  8.2.10-2
ii  php8.2-xml [php-xml]  8.2.10-2
ii  postgresql-client 16+255
ii  postgresql-client-11 [postgresql-client]  11.7-0+deb10u1
ii  postgresql-client-12 [postgresql-client]  12.4-3
ii  postgresql-client-13 [postgresql-client]  13.4-3
ii  postgresql-client-14 [postgresql-client]  14.5-3
ii  postgresql-client-15 [postgresql-client]  15.4-3
ii  postgresql-client-16 [postgresql-client]  16.0-2

Versions of packages davical recommends:
ii  php-curl2:8.2+93
ii  php8.2-curl [php-curl]  8.2.10-2
ii  postgresql  16+255

Versions of packages davical suggests:
pn  php-ldap | php5-ldap  

-- Configuration Files:
/etc/davical/config.php changed [not included]

-- no debconf information

Bug#847096: elfutils: Does not build when using eatmydata

[Santiago Vila]

Version: 0.183-1

Hello. According to my build logs, this is fixed at least in bullseye,
so I'm closing with this message.

Thanks.

Bug#1054043: texlive: Texlive updates are too large

[Preuße]

On 16.10.2023 17:28, Stefan Monnier wrote:

Hi Stefan,


 Stefan "dreaming of Debian updates as efficient as
 `git fetch` :-)"



You are not the first one, who complains and (probably) not the last 
one. Due to the limited man power in the team, we simply copy the 
packaging scheme given by TeX Live upstream and this is what you see 
here. So unfortunately there is nothing, which will be done from our 
side. I try to have as less as uploads as possible, which do not bring 
in new upstream features or bug fixes.


I'm aware of an idea called debdelta[1], maybe it is helpful for you.

H.

[1] http://debdelta.debian.net/
--
sigfault



OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1054142: cron-daemon-common: Cron now depends on systemd.

[Jerry Kaisler]

Package: cron-daemon-common
Severity: important
X-Debbugs-Cc: bugrep...@ntlhelp.net

Dear Maintainer,

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

   * What led up to the situation? cron should NOT depend on systemd.
   * What exactly did you do (or not do) that was effective (or
 ineffective)? tried to install a base system without systemd.
   * What was the outcome of this action? It failed because systemd was not
installed.
   * What outcome did you expect instead? the ability to install cron after
stripping out the hot steaming pile that is systemd.

*** End of the template - remove these template lines ***


-- System Information:
Debian Release: bookworm/sid
  APT prefers jammy-updates
  APT policy: (500, 'jammy-updates'), (500, 'jammy-security'), (500, 'jammy'), 
(100, 'jammy-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Bug#1054141: fd - incompatible with clap 4.4.6

[Peter Green]

Package: rust-fd-find
Version: 8.7.0-3
Severity: serious

This bug affects both 8.7.0-3 in testing and 8.7.0-4 in unstable.

I recently uploaded clap 4.4.6, since this was not a semver bump I was not
expecting any breakage. Unfortunately it turns out it broke fd.

There are (at least) two issues, the first is that the "unstable-grouped"
feature was removed in clap 4.2.0 by the commit
https://github.com/clap-rs/clap/commit/d5089b267235db72a6ea146ac4f1cb7f79a170a6
"fix!: Remove stablized unstable-grouped feature". By removing the reference to
the "unstable-grouped" feature I was able to successfully build fd and run it's
tests against clap versions 4.2.0 through 4.2.4.

The second issue arises starting with clap version 4.2.5, a bunch of tests fail
with errors like.

 test_custom_ignore_files stdout 
thread 'test_custom_ignore_files' panicked at '`fd --ignore-file custom.ignore 
foo` did not exit successfully.
stdout:
---
---
stderr:
---
thread 'main' panicked at 'Command fd: Argument group 'execs' conflicts with 
non-existent 'has_results' id', 
/root/.cargo/registry/src/github.com-1ecc6299db9ec823/clap_builder-4.2.5/src/builder/debug_asserts.rs:317:13
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
---', tests/testenv/mod.rs:238:13

I'm not sure what should be done about this second issue. I've filed a bug 
upstream
at https://github.com/sharkdp/fd/issues/1397

Bug#1054115: [pkg-apparmor] Bug#1054123: apparmor breaks nfs root

[Christian Boltz]

Hello,

(cross-posting to the referenced bug so that the information appears in 
both bugs)

Am Dienstag, 17. Oktober 2023, 14:18:43 CEST schrieb Anton Ivanov:
> The default profile denies network functionality and it breaks
> man and other software which has an apparmor profile. They stop
> working on NFS.
>
> For an example see Debian bug 1054115
>
> While it is possible to solve it on a case by case basis, the
> right bugfix is to check if root and/or /usr are on NFS and
> load an extra profile to allow network access.
>
> Alternatively, the kernel should stop treating network filesystem
> access as network access for apparmor purposes. That, however,
> is likely to a be a bit difficult.
[...]
> Kernel: Linux 5.10.0-22-amd64 (SMP w/12 CPU threads)

This issue was fixed in kernel 6.0 [1] - which means your 5.10.0 kernel 
is too old and doesn't contain the fix yet.

Unfortunately I don't know the exact commit, or how hard it would be to 
backport the fix to an older kernel. (If you are interested in 
backporting, I'd recommend to ask John Johansen for details.)

If upgrading to a newer kernel is not an option, a possible workaround 
is to add
network inet stream,
network inet6 stream,
to the affected profile or an abstraction - or to abstractions/base if you 
really want it in all profiles.

Note: These two rules allow _all_ TCP/IP network access, not only NFS.

Also note that abstractions/nameservice already contains these two rules 
(for DNS resolution etc.), so this workaround is already accidentally in 
place in some profiles ;-)


Regards,

Christian Boltz

[1] see https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1784499
comment 13
-- 
Having presentation after lunch break when sun is shinning really sucks.
[Josef Reidinger in yast-devel]


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

Bug#1051983: RFS: golang-github-katalix-go-l2tp

[Nilesh Patra]

On Tue, Oct 17, 2023 at 09:27:38PM +0100, Tom Parkin wrote:
> On  Wed, Oct 18, 2023 at 01:38:58 +0530, Nilesh Patra wrote:
> > I've uploaded your package to NEW. However, please look at my commits.
> 
> Thank you very much :-)
> 
> I've just had a look at your changes on the debian/0.1.6-1 tag.  Thank
> you for catching the copyright for l2tp.h!
> 
> Should I merge these changes on debian/sid?

I think they are already in the same branch, no?


https://salsa.debian.org/go-team/packages/golang-github-katalix-go-l2tp/-/commits/debian/sid

We tag debian releases with debian/ tag for easy tracking. LMK if I
misunderstood something.

> > I also have a quick question -- is the interface of the library somehow
> > architecture dependent? if so the "M-A: foreign" field should be
> > dropped.
> 
> No, it shouldn't be.

Cool, thanks for the prompt reply!

Best,
Nilesh


signature.asc
Description: PGP signature

Bug#1052019: RFS: golang-github-gookit-color/1.5.4-1

[Nilesh Patra]

On Wed, Oct 04, 2023 at 02:20:38PM +0530, Afeedh Shaji wrote:
> I am looking for a sponsor for the package "golang-github-gookit-color".
> This package is a prerequisite for upcoming package "lazygit" (#908894).
> 
> I pushed to our team's Salsa:
> 
>   https://salsa.debian.org/go-team/packages/golang-github-gookit-color
> 
> Could you please reviewing/sponsoring this?
> Any kind of reviews and suggestions are appreciated.

Uploaded. However please look at my commits.

Thanks for your contribution!

Best,
Nilesh


signature.asc
Description: PGP signature

Bug#1054140: python-refurb: FTBFS with mypy 1.6.0

[Michael R. Crusoe]

Source: python-refurb
Version: 1.21.0-1
Severity: normal
Tags: patch ftbfs upstream

Dear Maintainer,

Mypy 1.6.0-1 is in unstable, an unfortunately it causes a build-type 
test for python-refurb to fail[0]. I reported this upstream[1] and they 
maintainer provided a fix[2]. Would you please apply this as a patch to 
unblock the migration of mypy 1.6.0-1 to testing. Or, if you wish, I can 
do a team-upload of python-refurb for you.


Thanks,

[0] 
https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-refurb/39057922/log.gz


[1] https://github.com/dosisod/refurb/issues/295

[2] https://github.com/dosisod/refurb/pull/296

--
Michael R. Crusoe



OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1051983: RFS: golang-github-katalix-go-l2tp

[Tom Parkin]

Hi Nilesh,

On  Wed, Oct 18, 2023 at 01:38:58 +0530, Nilesh Patra wrote:
> I've uploaded your package to NEW. However, please look at my commits.

Thank you very much :-)

I've just had a look at your changes on the debian/0.1.6-1 tag.  Thank
you for catching the copyright for l2tp.h!

Should I merge these changes on debian/sid?

> I also have a quick question -- is the interface of the library somehow
> architecture dependent? if so the "M-A: foreign" field should be
> dropped.

No, it shouldn't be.

> Thanks for your contribution!

Thanks again for your help in getting it uploaded.

Tom


signature.asc
Description: PGP signature

Bug#1053520: RFS: golang-github-ozeidan-fuzzy-patricia/3.0.0-1

[Nilesh Patra]

On Sun, Oct 08, 2023 at 11:31:14AM +0530, Ananthu C V wrote:
> I am looking for a sponsor for the package 
> "golang-github-ozeidan-fuzzy-patricia".
> This package is a prerequisite for upcoming package "lazygit" (#908894).
> 
> I pushed to our team's Salsa:
> 
>   
> https://salsa.debian.org/go-team/packages/golang-github-ozeidan-fuzzy-patricia
> 
> Could you please review/sponsor this?
> Any kind of reviews and suggestions are appreciated

Please fix the description in d/control. Also IMHO the copyright holder
should be as per what's mentioned in the license and authors file, not
as per repository owner -- update that too.

Best,
Nilesh


signature.asc
Description: PGP signature

Bug#1052470: [Pkg-javascript-devel] Bug#1052470: nodejs: Please fix testsuite for openssl-3.1

[Jérémy Lal]

Le mar. 17 oct. 2023 à 21:37, Sebastian Andrzej Siewior <
sebast...@breakpoint.cc> a écrit :

> On 2023-09-22 22:52:48 [+0200], Jérémy Lal wrote:
> > Thanks, will include it soon.
>
> Thanks. Any update on this?
> I added two patches. The first one is a cherry-pick from upstream, the
> second has been forwarded upstream via
> https://github.com/nodejs/node/pull/49885
>
> but upstream has no interest in applying it. So you could apply it and
> drop it after new openssl migrated to testing. Another option would be
> to binNMU later on, don't want to cause too much trouble here ;)


I did not forget about this. Really sorry for the delay.
Currently I'd be more willing to help someone maintain nodejs than doing it
myself.
However, I'll probably deal with the next 18.x update very soon, including
your patch.

Jérémy

Bug#1051983: RFS: golang-github-katalix-go-l2tp

[Nilesh Patra]

I've uploaded your package to NEW. However, please look at my commits.

I also have a quick question -- is the interface of the library somehow
architecture dependent? if so the "M-A: foreign" field should be
dropped.

Thanks for your contribution!

Best,
Nilesh


signature.asc
Description: PGP signature

Bug#1054139: file conflict between python3-ledger-dbgsym and ledger-dbgsym

[Marcin Owsiany]

Package: python3-ledger-dbgsym
Version: 3.3.0-3
Severity: normal

I got the following error when trying to install ledger-dbgsym while
python3-ledger-dbgsym is already installed:

Przygotowywanie do rozpakowania pakietu .../ledger-dbgsym_3.3.0-3_amd64.deb ...
Rozpakowywanie pakietu ledger-dbgsym (3.3.0-3) ...
dpkg: błąd przetwarzania archiwum 
/var/cache/apt/archives/ledger-dbgsym_3.3.0-3_amd64.deb (--unpack):
 próba nadpisania 
"/usr/lib/debug/.build-id/bb/b9da531167728c34db6adc7a5ace6f0d21a6d2.debug", 
który istnieje także w pakiecie python3-ledger-dbgsym 3.3.0-3
Wystąpiły błędy podczas przetwarzania:
 /var/cache/apt/archives/ledger-dbgsym_3.3.0-3_amd64.deb

I guess the packages should conflict with each other?

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

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

Versions of packages python3-ledger-dbgsym depends on:
ii  python3-ledger  3.3.0-3

python3-ledger-dbgsym recommends no packages.

python3-ledger-dbgsym suggests no packages.

-- no debconf information

Bug#1051075: babeltrace2: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file

[Michael Jeanson]

On 2023-09-02 06:53, zhangdandan wrote:

Source: babeltrace2
Version: 2.0.5-1
Severity: wishlist
Tags: sid ftbfs
User: debian-de...@lists.debian.org
Usertags: loongarch64

    Dear maintainers,

When compiling the package babeltrace2 for loong64 in the Debian Package 
Auto-Building environment [1], The error message is as follows.
dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols 
file: see diff output below
dpkg-gensymbols: warning: debian/libbabeltrace2-0/DEBIAN/symbols doesn't match 
completely debian/libbabeltrace2-0.symbols

--- debian/libbabeltrace2-0.symbols (libbabeltrace2-0_2.0.5-1_loong64)
+++ dpkg-gensymbolsee2M2Y    2023-09-01 15:10:42.916098851 +
@@ -193,14 +193,14 @@
   __bt_get_end_section_component_class_descriptors@Base 2.0.0
   __bt_get_end_section_plugin_descriptor_attributes@Base 2.0.0
   __bt_get_end_section_plugin_descriptors@Base 2.0.0
- __start___bt_plugin_component_class_descriptor_attributes@Base 2.0.0
- __start___bt_plugin_component_class_descriptors@Base 2.0.0
- __start___bt_plugin_descriptor_attributes@Base 2.0.0
- __start___bt_plugin_descriptors@Base 2.0.0
- __stop___bt_plugin_component_class_descriptor_attributes@Base 2.0.0
- __stop___bt_plugin_component_class_descriptors@Base 2.0.0
- __stop___bt_plugin_descriptor_attributes@Base 2.0.0
- __stop___bt_plugin_descriptors@Base 2.0.0
+#MISSING: 2.0.5-1# 
__start___bt_plugin_component_class_descriptor_attributes@Base 2.0.0

+#MISSING: 2.0.5-1# __start___bt_plugin_component_class_descriptors@Base 2.0.0
+#MISSING: 2.0.5-1# __start___bt_plugin_descriptor_attributes@Base 2.0.0
+#MISSING: 2.0.5-1# __start___bt_plugin_descriptors@Base 2.0.0
+#MISSING: 2.0.5-1# 
__stop___bt_plugin_component_class_descriptor_attributes@Base 2.0.0

+#MISSING: 2.0.5-1# __stop___bt_plugin_component_class_descriptors@Base 2.0.0
+#MISSING: 2.0.5-1# __stop___bt_plugin_descriptor_attributes@Base 2.0.0
+#MISSING: 2.0.5-1# __stop___bt_plugin_descriptors@Base 2.0.0
   bt_clock_class_borrow_user_attributes@Base 2.0.0
   bt_clock_class_borrow_user_attributes_const@Base 2.0.0
   bt_clock_class_create@Base 2.0.0
dh_makeshlibs: error: failing due to earlier errors


The full build log is available from the link [2].
Please consider updating the symbols file.
If you have any questions, you can contact me at any time.

[1]:https://buildd.debian.org/status/package.php?p=babeltrace2=sid
[2]:https://buildd.debian.org/status/fetch.php?pkg=babeltrace2=loong64=2.0.5-1=1693581057=0

thanks,
Dandan Zhang


Hi,

I'd like to understand first why those symbols are not present when building 
on loongarch, do you have an idea?


Thanks,

Michael

Bug#1054097: ITP: libparse-man-perl -- Perl library for parsing nroff-formatted manpages

[Ole Peder Brandtzæg]

On Tue, Oct 17, 2023 at 09:25:50AM +0300, Andrius Merkys wrote:
> I have just uploaded libparse-man-perl. You may find its packaging
> repository on salsa:
> 
> https://salsa.debian.org/perl-team/modules/packages/libparse-man-perl
> 
> Feel free to add yourself to the list of its uploaders.

Many thanks! My request for a Salsa account was just approved, so will
familiarise myeslf with the machinery now. =)

Best,
Ole

-- 
Ole Peder Brandtzæg | En KLST/ITK-hybrid
We drive, we sleep, we drive some more.

Bug#1052470: [Pkg-javascript-devel] Bug#1052470: nodejs: Please fix testsuite for openssl-3.1

[Sebastian Andrzej Siewior]

On 2023-09-22 22:52:48 [+0200], Jérémy Lal wrote:
> Thanks, will include it soon.

Thanks. Any update on this?
I added two patches. The first one is a cherry-pick from upstream, the
second has been forwarded upstream via
https://github.com/nodejs/node/pull/49885

but upstream has no interest in applying it. So you could apply it and
drop it after new openssl migrated to testing. Another option would be
to binNMU later on, don't want to cause too much trouble here ;)

Sebastian

Bug#962064: "--extra-repository-key" option also not recognizing relative paths

[Carlos Henrique Lima Melara]

Hi there, sbuild developers.

Today I was building some packages and I needed a custom archive to be
added to sbuild. The repo was added but for some reason I kept seeing:

gpg: can't open '../file.asc': No such file or directory

It took a while, a bunch of name changes checking out the BTS to realize
relative paths were the issue.

Long story short, passing the absolute path worked. But usually people
(at least myself) expect relative paths to work, so if you don't plan to
implement this functionality soon(ish), could you consider adding this
caveat to the manpage?

Cheers,
Charles


signature.asc
Description: PGP signature

Bug#1054138: RFP: prometheus-ganeti-exporter -- Export Ganeti Statistics to Prometheus

[Antoine Beaupre]

Package: wnpp
Severity: wishlist
X-Debbugs-Cc: gan...@packages.debian.org

* Package name: prometheus-ganeti-exporter
  Version : No release published
  Upstream Contact: https://github.com/ganeti/
* URL : https://github.com/ganeti/prometheus-ganeti-exporter
* License : BSD-2-Clause
  Programming Lang: Python
  Description : Export Ganeti Statistics to Prometheus

No real long description upstream.

Bug#1054137: apt: let dh_installsystemd choose the location of units

[Helmut Grohne]

Source: apt
Version: 2.7.6
Tags: patch
User: helm...@debian.org
Usertags: dep17m2

We want to move aliased files from / to /usr to finalize the /usr-merge
transition via DEP17. apt is involved, because it install systemd units.
It currently hard codes their location to /lib/systemd/system. Rather
than moving them to /usr directly, I recommend using dh_installsystemd,
because backports will automatically revert back to the previous
location honouring the file move moratorium in bookworm. I'm attaching a
patch for your convenience. Once dh_installsystemd is updated and apt
binNMUed, it will have no files left in aliased locations.

Helmut
diff -Nru apt-2.7.6/debian/apt-daily-upgrade.service 
apt-2.7.6+nmu1/debian/apt-daily-upgrade.service
--- apt-2.7.6/debian/apt-daily-upgrade.service  2023-09-20 10:25:26.0 
+0200
+++ apt-2.7.6+nmu1/debian/apt-daily-upgrade.service 1970-01-01 
01:00:00.0 +0100
@@ -1,12 +0,0 @@
-[Unit]
-Description=Daily apt upgrade and clean activities
-Documentation=man:apt(8)
-ConditionACPower=true
-After=apt-daily.service network.target network-online.target 
systemd-networkd.service NetworkManager.service connman.service
-
-[Service]
-Type=oneshot
-ExecStartPre=-/usr/lib/apt/apt-helper wait-online
-ExecStart=/usr/lib/apt/apt.systemd.daily install
-KillMode=process
-TimeoutStopSec=900
diff -Nru apt-2.7.6/debian/apt-daily-upgrade.timer 
apt-2.7.6+nmu1/debian/apt-daily-upgrade.timer
--- apt-2.7.6/debian/apt-daily-upgrade.timer2023-09-20 10:25:26.0 
+0200
+++ apt-2.7.6+nmu1/debian/apt-daily-upgrade.timer   1970-01-01 
01:00:00.0 +0100
@@ -1,11 +0,0 @@
-[Unit]
-Description=Daily apt upgrade and clean activities
-After=apt-daily.timer
-
-[Timer]
-OnCalendar=*-*-* 6:00
-RandomizedDelaySec=60m
-Persistent=true
-
-[Install]
-WantedBy=timers.target
diff -Nru apt-2.7.6/debian/apt-daily.service 
apt-2.7.6+nmu1/debian/apt-daily.service
--- apt-2.7.6/debian/apt-daily.service  2023-09-20 10:25:26.0 +0200
+++ apt-2.7.6+nmu1/debian/apt-daily.service 1970-01-01 01:00:00.0 
+0100
@@ -1,11 +0,0 @@
-[Unit]
-Description=Daily apt download activities
-Documentation=man:apt(8)
-ConditionACPower=true
-After=network.target network-online.target systemd-networkd.service 
NetworkManager.service connman.service
-
-[Service]
-Type=oneshot
-ExecStartPre=-/usr/lib/apt/apt-helper wait-online
-ExecStart=/usr/lib/apt/apt.systemd.daily update
-
diff -Nru apt-2.7.6/debian/apt-daily.timer apt-2.7.6+nmu1/debian/apt-daily.timer
--- apt-2.7.6/debian/apt-daily.timer2023-09-20 10:25:26.0 +0200
+++ apt-2.7.6+nmu1/debian/apt-daily.timer   1970-01-01 01:00:00.0 
+0100
@@ -1,10 +0,0 @@
-[Unit]
-Description=Daily apt download activities
-
-[Timer]
-OnCalendar=*-*-* 6,18:00
-RandomizedDelaySec=12h
-Persistent=true
-
-[Install]
-WantedBy=timers.target
diff -Nru apt-2.7.6/debian/apt.apt-daily-upgrade.service 
apt-2.7.6+nmu1/debian/apt.apt-daily-upgrade.service
--- apt-2.7.6/debian/apt.apt-daily-upgrade.service  1970-01-01 
01:00:00.0 +0100
+++ apt-2.7.6+nmu1/debian/apt.apt-daily-upgrade.service 2023-09-20 
10:25:26.0 +0200
@@ -0,0 +1,12 @@
+[Unit]
+Description=Daily apt upgrade and clean activities
+Documentation=man:apt(8)
+ConditionACPower=true
+After=apt-daily.service network.target network-online.target 
systemd-networkd.service NetworkManager.service connman.service
+
+[Service]
+Type=oneshot
+ExecStartPre=-/usr/lib/apt/apt-helper wait-online
+ExecStart=/usr/lib/apt/apt.systemd.daily install
+KillMode=process
+TimeoutStopSec=900
diff -Nru apt-2.7.6/debian/apt.apt-daily-upgrade.timer 
apt-2.7.6+nmu1/debian/apt.apt-daily-upgrade.timer
--- apt-2.7.6/debian/apt.apt-daily-upgrade.timer1970-01-01 
01:00:00.0 +0100
+++ apt-2.7.6+nmu1/debian/apt.apt-daily-upgrade.timer   2023-09-20 
10:25:26.0 +0200
@@ -0,0 +1,11 @@
+[Unit]
+Description=Daily apt upgrade and clean activities
+After=apt-daily.timer
+
+[Timer]
+OnCalendar=*-*-* 6:00
+RandomizedDelaySec=60m
+Persistent=true
+
+[Install]
+WantedBy=timers.target
diff -Nru apt-2.7.6/debian/apt.apt-daily.service 
apt-2.7.6+nmu1/debian/apt.apt-daily.service
--- apt-2.7.6/debian/apt.apt-daily.service  1970-01-01 01:00:00.0 
+0100
+++ apt-2.7.6+nmu1/debian/apt.apt-daily.service 2023-09-20 10:25:26.0 
+0200
@@ -0,0 +1,11 @@
+[Unit]
+Description=Daily apt download activities
+Documentation=man:apt(8)
+ConditionACPower=true
+After=network.target network-online.target systemd-networkd.service 
NetworkManager.service connman.service
+
+[Service]
+Type=oneshot
+ExecStartPre=-/usr/lib/apt/apt-helper wait-online
+ExecStart=/usr/lib/apt/apt.systemd.daily update
+
diff -Nru apt-2.7.6/debian/apt.apt-daily.timer 
apt-2.7.6+nmu1/debian/apt.apt-daily.timer
--- apt-2.7.6/debian/apt.apt-daily.timer1970-01-01 01:00:00.0 
+0100
+++ apt-2.7.6+nmu1/debian/apt.apt-daily.timer   2023-09-20 10:25:26.0 
+0200
@@ -0,0 +1,10 @@
+[Unit]

Bug#1054096: bookworm-pu: package llvm-toolchain-16/16.0.6-15~deb12u1

[Adam D. Barratt]

Control: tags -1 confirmed

On Mon, 2023-10-16 at 17:36 -0400, Andres Salomon wrote:
> Here's the update to stable for clang-16, like we recently did for 
> oldstable.
> 
> [ Reason ]
> 
> Chromium 118 wouldn't build on clang-13, so we added clang-16 to 
> oldstable (#1053761). In order to be consistent across distributions 
> (and also allowing us to drop a bunch of clang-14 & clang-15
> workaround 
> patches from chromium), we should add clang-16 to stable as well.
> 

+  * Rebuild for bullseye.

*cough* :-)

With the above fixed, please go ahead.

Regards,

Adam

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

[Martin Hostettler]

On Sun, Oct 15, 2023 at 06:51:51AM -0400, Thomas Dickey wrote:
> 
> Likewise, it uses xterm's documentation (and source code) extensively
> (such as in termquery.cpp) without mentioning the source of the information.

Yes, termquery.cpp is a testing helper shipped in the source that has the
need to name modes.

I mean where else would one get names for those than the only contemporary
documentation of those things. Which is the xterm documentation.

Yes, i should not have assumed that it's totally obvious to anyone in the
space that those things are either from some floating around DEC manuals or
from ctlseqs.

I'm happy to fix that with a link back to your site, as it really is one of
the best sources.

But that files is not even linked into the library so it's a bit of a
tanget wrt termpaint itself.

For the rest, i don't think there is a lot that is similar to xterm except
as technically needed (e.g. the details of the 256 color color map)

But in the end this whole project is based on careful study¹ (and
redocumentation) of a lot of terminal implementations including xterm,
so some things might have stuck in my mind. I'm happy to look into any
other places where you feel that attribution is missing.

But this is all quite of topic here, so let's take that to private mail or
to the upstream issue tracker.

Regards, 
 - Martin


¹ which even lead me to report some improvments to xterm some years ago.

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

[Martin Hostettler]

On Sun, Oct 15, 2023 at 04:51:47AM -0400, Thomas Dickey wrote:
> On Sun, Oct 15, 2023 at 02:23:28AM +0200, Salvo Tomaselli wrote:
> > Could you improve the description?
> > 
> > What does this do?
> > 
> > For me low level access is ioctl, write or similar…
> 
> no - in this case "low level" is a synonym for "hard-coded"
> 
> It's just another of the programs written with the assumption that the
> terminal is xterm (or one of its imitators).

Well the long description clearly states that it only focuses on
"terminals in the tradition of VT1xx (like xterm, etc)".

It does make vastly different choices in terminal support than termcap and
ncurses. That allows is to have a more direct mapping of the terminal
functions but of course, it does not support nearly the breadth of
terminals that ncurses can support.

But i think that is ok, as many users nowadays use terminals in the
supported set.

Another choice where it differs is the it is build with the reality in mind
that $TERM is much more likely to be blatently wrong that than it having to
work with a terminal that is not "xterm like". Thus is uses terminal
response fingerprinting and terminal self identification to decide what
terminal implementation it is likely talking to and then uses its internal
(hard coded) terminal information to select features and workarounds.

Yes. That is throwing the towel on expecting properly administrated
systems, but a varity of factors ends making properly administrated
systems to be on the decline.

> 
> Unlike the last one on this topic, it uses the terminology of ncurses
> without using the word "ncurses".

I'm not sure what you mean with the terminology of ncurses, mostly because
ncurses certainly defined a lot of the terminology of the field and thus
it's hard to say where something is ncurses (or curses) specific or just
the broader terminology with terminals.

And i think the debian package is not really the place for a detailed
discussion of the tradeoffs between say ncurses and termpaint. Or termpaint
and s-lang or ... They would need a lot of nouance, and i'm pretty sure i
would get it wrong. So i think it is better to be silent on that than to
offer something incomplete.

As you pointed out, it is not even a alternative to ncurses, because it has
a vastly smaller set of supported terminals.

 - Martin

Bug#1054136: ITP: node-prosemirror-tables -- enhances table support

[Ananthu C V]

Package: wnpp
Severity: wishlist
Owner: Ananthu C V 
X-Debbugs-Cc: debian-de...@lists.debian.org

* Package name: node-prosemirror-tables
  Version : 1.3.4
  Upstream Author : ProseMirror
* URL : https://github.com/prosemirror/prosemirror-tables
* License : Expat
  Programming Lang: JavaScript
  Description : enhances table support

 This module defines a schema extension to support tables with rowspan/colspan 
support,
 a custom selection class for cell selections in such a table, a plugin to 
manage such
 selections and enforce invariants on such tables, and a number of commands to 
work with
 tables.

This package is a dependency required to package tiptap (#963902), a dependency 
used by
gitlab.

I intend to package this myself and maintain it as part of the javascript team. 
But as I
hold no uploading rights, I will be needing a sponsor.

Bug#1054019: broken sample rate passthrough

[Nicholas D Steeves]

Hi Dylan,

Oops!  Yes, thank you, I forgot to test a newer pipewire after tiring
and running out of time during the initial investigation.

0.3.82-1~bpo12+1 solves the bug :)

Rather than close this bug as fixed right away, do you think it would be
worthwhile to keep it open and/or add something to the bookworm release
notes?  I could write a few words if you'd prefer.  There are always
questions of "can I switch to $new_technology without regressions", and
I think this would help answer them.

It's also the case that pipewire-jack makes taking one's first steps in
Linux music production much easier, but sample rate mismatches are RC
for this use case...so at a minimum release notes should be provided.

What you do you think?
Regards,
Nicholas


signature.asc
Description: PGP signature

Bug#1054135: ruby-jsonb-accessor Adds typed jsonb backed fields to your ActiveRecord models.

[Ravi Dwivedi]

package: wnpp
Severity: wishlist
Owner: 'Ravi Dwivedi' 

*Package Name : ruby-jsonb-accessor
 Version :  1.3.10
 Upstream Author : Michael Crismali
*URL :  https://github.com/devmynd/jsonb_accessor
*License : Expat
*Description : Adds typed jsonb backed fields to your ActiveRecord models.

I am packaging ruby-jsonb-accessor as it is required for gitlab.

--
Ravi Dwivedi

Bug#986333: debian-security-support: Match ecosystems with limited support

[Holger Levsen]

On Tue, Oct 17, 2023 at 02:11:24PM -0300, Santiago Ruano Rincón wrote:
> > because the bug is closed in unstable. if it's still fixed in older suite,
> > we (in Debian, in general) don't keep the bugs open.
> s/still/still to be/?

sorry, I ment 'unfixed', not 'fixed'.
 
> > else you would need to re-open all other bugs too, which are not fixed in 
> > older suites.
> OK. My intention is/was to re-open bugs that I needed to fix. Along with
> #986333, I need to close #986581 in bullseye and buster too (*). For
> this update, may I stick with the unarchiving & reopening procedure, to
> keep it consistent?
> 
> Or do you still want me to open a new bug for it?

I'd prefer neither. Just add Closes: #123456 in changelog and the BTS will
correctly mark it fixed in that version as well. Maybe you need to manually
unarchive the bug for this, but there's no need to reopen. 
 
> Indeed, brain fail typo! 

happens to the best! :)
 
> I correct:
> "As discussed in #debian-lts, unarchiving & reopening since this bug is
> present in bullseye and buster"

that makes sense. :)


-- 
cheers,
Holger

 ⢀⣴⠾⠻⢶⣦⠀
 ⣾⠁⢠⠒⠀⣿⡁  holger@(debian|reproducible-builds|layer-acht).org
 ⢿⡄⠘⠷⠚⠋⠀  OpenPGP: B8BF54137B09D35CF026FE9D 091AB856069AAA1C
 ⠈⠳⣄

Where will you go when you become a climate refugee?


signature.asc
Description: PGP signature

Bug#1054134: yoshimi: suggest replacing homepage in d/control

[Patrice Duroux]

Package: yoshimi
Version: 2.3.1-1
Severity: wishlist

Dear Maintainer,

I suggest replacing:
https://yoshimi.sourceforge.io
by:
https://yoshimi.github.io/

A nicer and better place to get more information
from my PoV.

Many thanks,
Patrice

ps: a patch attached in case


-- 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-2-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

Versions of packages yoshimi depends on:
ii  libasound21.2.10-1
ii  libc6 2.37-12
ii  libcairo2 1.18.0-1
ii  libfftw3-single3  3.3.10-1
ii  libfltk-images1.3 1.3.8-5
ii  libfltk1.31.3.8-5
ii  libgcc-s1 13.2.0-5
ii  libjack-jackd2-0 [libjack-0.125]  1.9.21~dfsg-3
ii  libmxml1  3.3.1-1
ii  libreadline8  8.2-1.3
ii  libstdc++613.2.0-5
ii  libtinfo6 6.4+20231007-1
ii  yoshimi-data  2.3.1-1
ii  zlib1g1:1.2.13.dfsg-3

Versions of packages yoshimi recommends:
pn  jackd
ii  yoshimi-doc  2.3.1-1

yoshimi suggests no packages.

-- no debconf information
diff --git a/debian/control b/debian/control
index a327c31..b8e6b9d 100644
--- a/debian/control
+++ b/debian/control
@@ -32,7 +32,7 @@ Standards-Version: 4.6.2
 Rules-Requires-Root: no
 Vcs-Git: https://salsa.debian.org/multimedia-team/yoshimi.git
 Vcs-Browser: https://salsa.debian.org/multimedia-team/yoshimi
-Homepage: https://yoshimi.sourceforge.io
+Homepage: https://yoshimi.github.io
 
 Package: yoshimi
 Architecture: any

Bug#986333: debian-security-support: Match ecosystems with limited support

[Santiago Ruano Rincón]

El 17/10/23 a las 16:49, Holger Levsen escribió:
> On Tue, Oct 17, 2023 at 09:28:04AM -0300, Santiago Ruano Rincón wrote:
> > El 17/10/23 a las 09:18, Holger Levsen escribió:
> > > On Mon, Oct 16, 2023 at 11:49:27PM -0300, Santiago Ruano Rincón wrote:
> > > > As discussed in #debian-lts, unarchiving & reopening since this bug is
> > > > present in bullseye and bookworm: "golang*" installed packages are not
> > > > reported.
> > > I really would have prefered a new bug, instead of unarchiving this one.
> > Why? It is the same bug. (Real question, I am happy to improve my
> > workflows)
> 
> because the bug is closed in unstable. if it's still fixed in older suite,
> we (in Debian, in general) don't keep the bugs open.

s/still/still to be/?

> 
> else you would need to re-open all other bugs too, which are not fixed in 
> older suites.

OK. My intention is/was to re-open bugs that I needed to fix. Along with
#986333, I need to close #986581 in bullseye and buster too (*). For
this update, may I stick with the unarchiving & reopening procedure, to
keep it consistent?

Or do you still want me to open a new bug for it?

> > > And pretty please, please fix this in bookworm first, and get it accepted 
> > > by
> > > SRMs, before pushing this into bullseye.
> > As discussed on #debian-lts, this is already fixed in bookworm.
> 
> I was merely refering to what you wrote above: "As discussed in #debian-lts,
> unarchiving & reopening since this bug is present in bullseye and bookworm" 
> :-D

Indeed, brain fail typo! 

I correct:
"As discussed in #debian-lts, unarchiving & reopening since this bug is
present in bullseye and buster"

Cheers!

 -- Santiago

* as documented in the #986333-related git commit
(bf9dc3b6b76f6aa5bee6591a20428744a214cb69). Thanks Sylvain for properly
documenting this!



signature.asc
Description: PGP signature

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

[Rusan Ioan]

Same issue also all my systems (with various displays...and also on 
remote display)


--
Cu stima,
Ioan Rusan

Bug#986333: debian-security-support: Match ecosystems with limited support

[Holger Levsen]

On Tue, Oct 17, 2023 at 09:28:04AM -0300, Santiago Ruano Rincón wrote:
> El 17/10/23 a las 09:18, Holger Levsen escribió:
> > On Mon, Oct 16, 2023 at 11:49:27PM -0300, Santiago Ruano Rincón wrote:
> > > As discussed in #debian-lts, unarchiving & reopening since this bug is
> > > present in bullseye and bookworm: "golang*" installed packages are not
> > > reported.
> > I really would have prefered a new bug, instead of unarchiving this one.
> Why? It is the same bug. (Real question, I am happy to improve my
> workflows)

because the bug is closed in unstable. if it's still fixed in older suite,
we (in Debian, in general) don't keep the bugs open.

else you would need to re-open all other bugs too, which are not fixed in 
older suites.

> > And pretty please, please fix this in bookworm first, and get it accepted by
> > SRMs, before pushing this into bullseye.
> As discussed on #debian-lts, this is already fixed in bookworm.

I was merely refering to what you wrote above: "As discussed in #debian-lts,
unarchiving & reopening since this bug is present in bullseye and bookworm" :-D

(see above)
 
> Thanks!

thank you too!


-- 
cheers,
Holger

 ⢀⣴⠾⠻⢶⣦⠀
 ⣾⠁⢠⠒⠀⣿⡁  holger@(debian|reproducible-builds|layer-acht).org
 ⢿⡄⠘⠷⠚⠋⠀  OpenPGP: B8BF54137B09D35CF026FE9D 091AB856069AAA1C
 ⠈⠳⣄

The road to fascism is lined with people telling you to stop overreacting.


signature.asc
Description: PGP signature

Bug#1053122: Fwd: Re: Bug#1053122: linux-image-6.5.0-1-amd64: using smp_processor_id() in preemptible

[Ben Hutchings]

Control: tag -1 - moreinfo

 Forwarded Message 
From: Gabriel Francisco 
To: Ben Hutchings 
Subject: Re: Bug#1053122: linux-image-6.5.0-1-amd64: using
smp_processor_id() in preemptible
Date: 12/10/23 20:23:30
Message-Id:


Hi,

> The CPU registers contain several addresses starting 89, except for
> rbx which starts 99 (and is the faulting address).  That looks like
> a single bit got flipped.

Thanks for the explanation! (now I know how to detect bit flips) :D

> The first BUG message should be more meaningful that what comes after.
> This shows the kernel tried to access non-existent memory.

Yes, I should have reported the first one indeed, I thought too much and
ended reporting the second one. Sorry about that.

> This could be due to a kernel bug, but is more likely a hardware
> problem.  Please test the RAM with memtest86+.  Also if you've enabled
> any overclocking options, turn those off.

Even with XMP(3000@1.35v) enabled (F4-3000C16-16GISB), memtest86+ ran for 3
hours and printed PASS in the screen.
I removed the XMP profile from my memories and ordered new rams to check if
my current ones are faulty (or not).

The message in dmesg was only one occasion. (but I reported it anyways)

The hang does still happens with/without XMP when running 6.5.x kernel
series. It happens when maximizing a video (or time-to-time when my cursor
enters the video area) when using kernel 6.5.x. It does not happen with
kernel 6.1.x series.

I'm using amgpu module.

Greetings,

*Gabriel Francisco*
Linux User #507840
email: frc.gabriel[at]gmail.com 


On Thu, Oct 5, 2023 at 1:15 AM Ben Hutchings  wrote:

> Control: retitle -1 linux-image-6.5.0-1-amd64: Kernel page fault in
> process exit due to bit flip
> Control: tag -1 moreinfo
> 
> On Wed, 2023-09-27 at 20:45 +0200, Gabriel Francisco wrote:
> > Package: src:linux
> > Version: 6.5.3-1
> > Severity: important
> > Tags: upstream
> > X-Debbugs-Cc: frc.gabr...@gmail.com
> > 
> > Dear Maintainer,
> > 
> > First of all thanks for your hard work!
> > 
> > I noticed my computer started freezing for few seconds when
> entering/exiting
> > full screen videos in youtube using firefox and while trying to check if
> the
> > issue also afected chromium I saw the following message in dmesg:
> > 
> > [12569.564300] BUG: unable to handle page fault for address:
> 991989e936b8
> > [12569.564304] #PF: supervisor write access in kernel mode
> > [12569.564306] #PF: error_code(0x0002) - not-present page
> 
> The first BUG message should be more meaningful that what comes after.
> This shows the kernel tried to access non-existent memory.
> 
> > [12569.564308] PGD 0 P4D 0
> > [12569.564311] Oops: 0002 [#1] PREEMPT SMP NOPTI
> > [12569.564314] CPU: 10 PID: 328649 Comm: Chroot Helper Not tainted
> 6.5.0-1-amd64 #1  Debian 6.5.3-1
> > [12569.564317] Hardware name: ASUS System Product Name/ROG STRIX B550-F
> GAMING WIFI II, BIOS 3205 08/14/2023
> > [12569.564318] RIP: 0010:down_write+0x23/0x70
> > [12569.564324] Code: 90 90 90 90 90 90 90 f3 0f 1e fa 0f 1f 44 00 00 53
> 48 89 fb e8 2e bc ff ff bf 01 00 00 00 e8 74 3a 53 ff 31 c0 ba 01 00 00 00
>  48 0f b1 13 75 33 65 48 8b 04 25 80 29 03 00 48 89 43 08 bf 01
> > [12569.564326] RSP: 0018:a189d736fc70 EFLAGS: 00010246
> > [12569.564328] RAX:  RBX: 991989e936b8 RCX:
> 891797aaef00
> > [12569.564330] RDX: 0001 RSI: 891989e645c0 RDI:
> 8e7c95dc
> > [12569.564331] RBP:  R08: 0060 R09:
> 80400014
> > [12569.564333] R10: 8918cbfeb7f8 R11: 0006 R12:
> 7f7e5fd0
> > [12569.564334] R13: 0001 R14: 891989e645c0 R15:
> 891989e64958
> 
> The CPU registers contain several addresses starting 89, except for
> rbx which starts 99 (and is the faulting address).  That looks like
> a single bit got flipped.
> 
> This could be due to a kernel bug, but is more likely a hardware
> problem.  Please test the RAM with memtest86+.  Also if you've enabled
> any overclocking options, turn those off.
> 
> [...]
> > After that the computer can't shutdown and systemd keeps waiting on
> process PID 328649 (Chroot Helper).
> 
> This (and the other BUG messages) are because that process crashed in
> kernel mode and couldn't properly exit.
> 
> Ben.
> 
> --
> Ben Hutchings
> Beware of bugs in the above code;
> I have only proved it correct, not tried it. - Donald Knuth
> 
> 

Hi,> The CPU registers contain several addresses starting 89, except for
> rbx which starts 99 (and is the faulting address).  That looks like> a single bit got flipped.Thanks for the explanation! (now I know how to detect bit flips) :D> The first BUG message should be more meaningful that what comes after.> This shows the kernel tried to access non-existent memory.Yes, I should have reported the first one indeed, I thought too much and ended reporting the second one. Sorry about that.> This could be due to a kernel bug, but is more 

Bug#1036277: Fix keama FTBFS on s390x patch

[Athos Ribeiro]

As proposed in my latest comment:
https://salsa.debian.org/debian/isc-dhcp/-/merge_requests/15

--
Athos Ribeiro

Bug#1053774: spdlog: need new upstream release 1.12 for catch2 v3

[Andreas Tille]

Hi Michael,

I tried the update but there are build time test failures[1].
Could you have a look?

Kind regards
   Andreas.


[1] https://salsa.debian.org/med-team/spdlog/-/jobs/4795796

Am Tue, Oct 10, 2023 at 08:11:13PM +0200 schrieb Drew Parsons:
> Source: spdlog
> Version: 1:1.10.0+ds-1
> Severity: serious
> Justification: debci
> 
> catch2 v3 was recently uploaded, but breaks spdlog's tests.
> 
> spdlog upstream has released v1.12.0 which uses catch2 v3.
> 
> ___
> Debian-med-packaging mailing list
> debian-med-packag...@alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-med-packaging
> 

-- 
http://fam-tille.de

Bug#1054133: ITP: bidscoin -- a toolkit to convert raw neuroimaging data according to the BIDS standard

[Zwiers, M.P. (Marcel)]

Package: ITP
Severity: wishlist

* Package name: bidscoin
  Version : 4.2.0
  Upstream Author : Marcel Zwiers
* URL : https://github.com/Donders-Institute/bidscoin
* License : GPL-v3+
  Copyright   : Marcel Zwiers
  Programming Lang: Python
  Description : A GUI toolkit to convert raw neuroimaging data according to 
the BIDS standard

BIDScoin is a new and user-friendly Python application suite that converts 
(“coins”) source-level (raw) neuroimaging data sets to standardized data sets 
that are organized according to the Brain Imaging Data Structure (BIDS) 
specification. The BIDScoin 4.2.0 package is intended to be included in 
NeuroDebian, to support researchers building reproducible analyses pipelines 
and data sharing workflows. BIDScoin is an actively maintained package that 
comes with a GUI and various command line tools and utilities. Please note the 
following packaging guidelines:

  *   Manpages are automatically build for every cli
  *   Continuous integration is implemented using pytests running as GitHub 
Actions
  *   All source code can be pip installed or is already packaged with 
NeuroDebian (dcm2niix)
  *   The main branch is dependent on PyQt6
  *   Every (PyQt6) BIDScoin release on pypi is backported to PyQt5 as a 
protected GitHub branch. This branch can be pip installed on distributions that 
do not natively support Qt6

For more information see:
https://bidscoin.readthedocs.io/en/latest/index.html

Bug#1054119: data loss patch for qpdf targeted at stable (11.3.0)

[Adam D. Barratt]

# bcc control@bugs.d.o
user release.debian@packages.debian.org
usertags 1054119 pu
tags 1054119 bookworm moreinfo
retitle 1054119 bookworm-pu: package qpdf/11.3.0-1
thanks

On Tue, 2023-10-17 at 07:32 -0400, Jay Berkenbilt wrote:
> The attached patch to qpdf 11.3.0 fixes a bug that could potentially
> result in loss of data. I'd like permission from the release team to
> upload this to stable. I've been a debian developer since 2005, but
> it's been years since I've last prepared a release to the stable
> distribution. As far as I can tell, the current procedure is to
> upload with the target distribution as "stable" and upload to ftp-
> master. This will direct the package the proposed-updates queue. Is
> this correct?
> 

Close, but a few rough edges. :-)

In relation to your query above, suite codenames - i.e. "bookworm" in
this case - are preferred over designations such as "stable", as
they're more self-documenting over time. Technically, such uploads
enter the "stable-new" queue, from where we can accept them (or not)
into p-u, but that's an implementation detail.

In terms of the patch, the diff we would need for review is a source
debdiff of an appropriately-versioned package that you've built and
tested against stable, not just the patch to the source code. I'd
suggest reviewing 
https://www.debian.org/doc/manuals/developers-reference/pkgs.en.html#special-case-uploads-to-the-stable-and-oldstable-distributions
as a more general primer on the process.

As noted in the dev-ref section, please use "reportbug
release.debian.org" for p-u requests, or set equivalent metadata. That
helps ensure that the request ends up in the correct section of our BTS
web view, where uncategorised bugs may get overlooked for some time.
I've fixed up the relevant bits for this request (see the start of my
reply).

Regards,

Adam

Bug#1054132: podget: line 2532: ITEM_TITLE: unbound variable

[ael]

Package: podget
Version: 0.9.1-1
Severity: normal

I haven't had time to see whether this is something trivial, but just to
report that the new podget is giving:

/usr/bin/podget: line 2532: ITEM_TITLE: unbound variable

In context:
Downloading feed index from 
http://www.thenakedscientists.com/naked_scientists_podcast.xml
2023-10-17 16:59:51 
URL:https://www.thenakedscientists.com/naked_scientists_podcast.xml 
[2448064/2448064] -> "-" [1]
/usr/bin/podget: line 2532: ITEM_TITLE: unbound variable

serverlist entry is
http://www.thenakedscientists.com/naked_scientists_podcast.xml sci n_sci



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

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

Versions of packages podget depends on:
ii  gawk  1:5.2.1-2
ii  mawk  1.3.4.20230808-1
ii  wget  1.21.4-1+b1

podget recommends no packages.

podget suggests no packages.

-- no debconf information

Bug#1054131: podget: line 2532: ITEM_TITLE: unbound variable

[ael]

Package: podget
Version: 0.9.1-1
Severity: normal

I haven't had time to see whether this is omething trivial, but just to
report that the new podget is giving:

/usr/bin/podget: line 2532: ITEM_TITLE: unbound variable

In context:
Downloading feed index from 
http://www.thenakedscientists.com/naked_scientists_podcast.xml
2023-10-17 16:59:51 
URL:https://www.thenakedscientists.com/naked_scientists_podcast.xml 
[2448064/2448064] -> "-" [1]
/usr/bin/podget: line 2532: ITEM_TITLE: unbound variable

serverlist entry is
http://www.thenakedscientists.com/naked_scientists_podcast.xml sci n_sci



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

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

Versions of packages podget depends on:
ii  gawk  1:5.2.1-2
ii  mawk  1.3.4.20230808-1
ii  wget  1.21.4-1+b1

podget recommends no packages.

podget suggests no packages.

-- no debconf information

Bug#1053911: I close this bug report

[Georges Khaznadar]

Hello,

X-Cron-Env headers can be useful, don't they?

It those headers are annoying you, please consider using procmail. 
I suppose that something like the following, in procmail's rc file,
sould do the job accordingly to your taste:

 part of the file .procmailrc -
:0:
*^From: Cron Daemon.*
| sed 's/X-Cron-Env.*//'
---

You can also tune your e-mail client to hide "X-Cron-Env" headers by
default. For example I'm using mutt, which does not show those headers by
default. Indeed, mutt provides a keyboard shortcut to toggle all headers'
visibility, so I can look at those headers at will.

I close this bug report now, please free to reopen it if you consider
writing the documentation for cron manual's page, to explain cron's
new feature to everybody.

Best regards,   Georges.

-- 
Georges KHAZNADAR et Jocelyne FOURNIER
22 rue des mouettes, 59240 Dunkerque France.
Téléphone +33 (0)3 28 29 17 70



signature.asc
Description: PGP signature

Bug#1054130: podget: line 2532: ITEM_TITLE: unbound variable

[ael]

Package: podget
Version: 0.9.1-1
Severity: normal

I haven't had time to see whether this is omething trivial, but just to
report that the new podget is giving:

/usr/bin/podget: line 2532: ITEM_TITLE: unbound variable

In context:
Downloading feed index from 
http://www.thenakedscientists.com/naked_scientists_podcast.xml
2023-10-17 16:59:51 
URL:https://www.thenakedscientists.com/naked_scientists_podcast.xml 
[2448064/2448064] -> "-" [1]
/usr/bin/podget: line 2532: ITEM_TITLE: unbound variable

serverlist entry is
http://www.thenakedscientists.com/naked_scientists_podcast.xml sci n_sci



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

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

Versions of packages podget depends on:
ii  gawk  1:5.2.1-2
ii  mawk  1.3.4.20230808-1
ii  wget  1.21.4-1+b1

podget recommends no packages.

podget suggests no packages.

-- no debconf information

Bug#1053866: transition: jpeg-xl

[Sebastian Ramacher]

Hi Mathieu

On 2023-10-13 16:42:34 +0200, Mathieu Malaterre wrote:
> On Fri, Oct 13, 2023 at 11:57 AM Sebastian Ramacher
>  wrote:
> >
> > Control: tags -1 moreinfo
> > Control: forwarded -1 
> > https://release.debian.org/transitions/html/auto-jpeg-xl.html
> >
> > On 2023-10-13 10:44:31 +0200, Mathieu Malaterre wrote:
> > > Package: release.debian.org
> > > Severity: normal
> > > User: release.debian@packages.debian.org
> > > Usertags: transition
> > >
> > > This is a minor SONAME transiton. Two (unused anywhere) symbols were
> > > removed.
> >
> > Are the reverse dependencies known to build with the new version?
> 
> Nope. I've requested an account on debomatic-amd64 to run the following:
> 
> % cat jxl.commands
> rebuild ffmpeg_7:6.0-7 unstable experimental
> rebuild geeqie_1:2.1-1 unstable experimental
> rebuild gimp_2.10.34-1 unstable experimental
> rebuild graphicsmagick_1.4+really1.3.42-1 unstable experimental
> rebuild imlib2_1.12.1-1 unstable experimental
> rebuild kimageformats_5.107.0-3 unstable experimental
> rebuild krita_1:5.2.0+dfsg-1 unstable experimental
> rebuild swayimg_1.12-1 unstable experimental
> rebuild vips_8.14.5-1 unstable experimental
> rebuild webkit2gtk_2.42.1-2 unstable experimental
> rebuild wpewebkit_2.42.1-1 unstable experimental
> 
> 
> will post back when I get access.

Alright, thanks. Please let us know as soon as you have the results.

Cheers
-- 
Sebastian Ramacher

Bug#968683: wireguard-tools: missing dependency in wireguard-tools resolvconf - wg-quick up

[Daniel Gröber]

Hi Mathias,

On Mon, Oct 16, 2023 at 09:33:14AM +0200, Mathias Behrle wrote:
> > What is your exact use-case? I assume it's for a desktop VPN, in which case
> > adding systemd-resolved support to wg-quick might be less
> > problematic.
> 
> Yes, indeed my use case is a desktop VPN. 
> 
> FWIW both resolvconf and systemd-resolved broke immediately my DNS, while
> openresolv worked.

Right, so there's the real root-cause. I think we should take the time to
debug and fix your systemd-resolved problem instead of bypassing it.

In case you're not aware systemd-resolved has a resolvconf compatibility
interface[1] now, so this will actually fix your wg-quick problem too. We
should likely do a push to get all openresolv|resolvconf dependencies
updated to add systemd-resolvd across Debian.

[1]: https://github.com/systemd/systemd/issues/7202

Unlike openresolv/resolvconf systemd-resolved actually has a data/config
model that has the potential to work for all use-cases I'm aware of without
hacks, so as much as I lament relying on yet another thing from under the
systemd umbrella it's the only reasonably modern solution capable of being
the default I'm aware of.

> I don't know for which reasons Recommends for the resolve tools were
> dropped to Suggests.

Unit 193, any explaination?

commit 324d375b79fab138f0c83af022bbe9e795d5e696
Author: Unit 193 
Date:   Fri May 15 18:32:09 2020 -0400

d/control: Lower 'openresolv | resolvconf' to suggests.

diff --git a/debian/control b/debian/control
index 09513a2..9093d4b 100644
--- a/debian/control
+++ b/debian/control
@@ -40,8 +40,8 @@ Depends:
  ${shlibs:Depends},
 Recommends:
  nftables | iptables,
- openresolv | resolvconf,
  wireguard-modules (>= 0.0.20171001) | wireguard-dkms (>= 0.0.20191219),
+Suggests: openresolv | resolvconf,
 Description: fast, modern, secure kernel VPN tunnel (userland utilities)
  WireGuard is a novel VPN that runs inside the Linux Kernel and uses
  state-of-the-art cryptography (the "Noise" protocol). It aims to be

> The issue for me is that
>
> 1) First the description in control
> 
>  This package contains command-line tools to interact with the
>  WireGuard kernel module.  Currently, it provides only a single tool:
>  .
>  wg: set and retrieve configuration of WireGuard interfaces
> 
> is no more appropriate. It ships now wg-quick, too.

That's unrelated open a seperate bug for that please.

> 2) The decision to downgrade resolve tools to Suggests may perhaps date back 
> to
> a time where wg was indeed the only binary shipped in the package?

I doubt it wg-quick has existed for a good long while. My guess is the
recommends was demoted because of DNS problems with openresolv/resolvconf ;)

> Now wg-quick failed from the beginning which is a major annoyance and a
> really bad user experience. 

Right, but you have to admit that by using a commandline tool you're
already well into poweruser territory so IMO you (or anyone doing that) is
expected to be able to debug this.

See I would expect most desktop users to deploy their wg VPN tunnels using
NetworkManager integration or some such. If DNS is broken in that case I'd
consider that a big problem as, say, my mum can't be expected to debug
this, haha.

> I think it could be a very common use case to use wireguard
> configurations with DNS entries. Thus the package should work
> out-of-the-box in a default Debian installation.

It's just not that clear-cut due to the brokenness of the
openresolv/resolvconf approach. I would agree if there were no known
downsides to installing them but alas..

> As a thought: if it makes substantial problems to install by default a resolv
> conf tool on servers would it perhaps improve things a little bit, if wg-quick
> would be phased out into a separate package?

Unfortunately the firewall functionality of wg-quick is still important on
servers. There just aren't any easy solutions here. To move things forward
we have to do the (hard) work of debugging why systemd-resolvd is broken in
your case and fixing it. I'm happy to help with that tho.

> Finally, if that all is yet not applicable for you then please document the
> current situation in README.Debian where my next source of information for the
> package is when I run into problems. It would have helped me lot ;)

Was there not a reasonable error message pointing at the missing
resolvconf? If so I think we may want to patch wg-quick to make the problem
a bit more verbose.

--Daniel


signature.asc
Description: PGP signature

Bug#1053912: transition: alglib

[Sebastian Ramacher]

Control: tags -1 confirmed
Control: forwarded -1 
https://release.debian.org/transitions/html/auto-alglib.html

Hi Anton

On 2023-10-14 09:59:15 +0200, Anton Gladky wrote:
> Please schedule the transition of alglib. All reverse dependencies are built 
> and fine.

Please go ahead.

Cheers
-- 
Sebastian Ramacher

Bug#1054129: Hugin fails to pass error messages from enblend to user

[Michael Deegan]

Package: hugin
Version: 2023.0~beta1+dfsg-1
Severity: normal

Hello, like in #799730, I encountered a case where stitching would abort,
and the user would be left wondering why, with no useful hints in the log
(example attached).

I strongly suggest ensuring that both stdout and stderr from enblend are
sent to the log/console. And yeah, reporting the commandline(s) invoked
would also save a bit of time when debugging (I ran ps repeatedly until
enblend showed up), as in my case it would have been immediately apparent
that enblend was complaining about too much overlap between images:

michael@joyola:/mnt/photos/2023/20231007$ /usr/bin/enblend 
-f4108x9286+77+1545 --compression=LZW -o pa073123-pa073129-Panini\ General.tif 
-- pa073123-pa073129-Panini\ General000*tif 2>stderr
michael@joyola:/mnt/photos/2023/20231007$ echo $?
1
michael@joyola:/mnt/photos/2023/20231007$ cat stderr
enblend: info: loading next image: pa073123-pa073129-Panini General.tif 
1/1
enblend: info: loading next image: pa073123-pa073129-Panini General0001.tif 
1/1

enblend: excessive image overlap detected; too high risk of defective seam 
line
enblend: note: remove at least one of the images
enblend: info: remove invalid output image "pa073123-pa073129-Panini 
General.tif"

Okay, so I just need to remove one or more images (like I had already
intended to but had forgotten to. :P)

Note that enblend sends nothing to stdout and all messages to stderr.

Thanks,

-- System Information:
Debian Release: 12.2
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 
'oldstable-updates'), (500, 'oldstable-security'), (500, 'stable'), (500, 
'oldstable'), (490, 'testing'), (400, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages hugin depends on:
ii  enblend 4.2-10+b1
ii  enfuse  4.2-10+b1
ii  hugin-tools 2023.0~beta1+dfsg-1
ii  libc6   2.36-9+deb12u3
ii  libepoxy0   1.5.10-1
ii  libexiv2-27 0.27.6-1
ii  libfftw3-double33.3.10-1
ii  libgcc-s1   12.2.0-14
ii  libglu1-mesa [libglu1]  9.0.2-1.1
ii  libglx0 1.6.0-1
ii  libgomp112.2.0-14
ii  libimage-exiftool-perl  12.57+dfsg-1
ii  liblcms2-2  2.14-2
ii  libopengl0  1.6.0-1
ii  libpano13-3 2.9.21+dfsg-3
ii  libsqlite3-03.40.1-2
ii  libstdc++6  13.2.0-4
ii  libtiff64.5.0-6
ii  libvigraimpex11 1.11.1+dfsg-11
ii  libwxbase3.2-1  3.2.2+dfsg-2
ii  libwxgtk-gl3.2-13.2.2+dfsg-2
ii  libwxgtk3.2-1   3.2.2+dfsg-2
ii  make4.3-4.1

hugin recommends no packages.

Versions of packages hugin suggests:
ii  darktable4.2.1-4
ii  dcraw9.28-3+b1
ii  rawtherapee  5.9-1+b1

-- no debconf information

-MD

-- 
-
Michael Deegan   Hugaholic  https://www.deegan.id.au/
  Jung, zr jbeel?  --

Stitching panorama...


Platform: Linux 6.1.0-12-amd64 x86_64
Version: 2023.0.0.de090f232982
Working directory: /mnt/photos/2023/20231007
Output prefix: pa073123-pa073129-Panini General

Blender: enblend 4.2
ExifTool version: 12.57

Number of active images: 7
Output exposure value: 8.3
Canvas size: 4270x10836
ROI: (77, 1545) - (4185, 10831) 
FOV: 70x116
Projection: Panini General(19)
Using GPU for remapping: true

Panorama Outputs:
* Exposure corrected, low dynamic range

Remapped Images:
* Exposure corrected, low dynamic range

First input image
Number: 0
Filename: /mnt/photos/2023/20231007/pa073123.jpg
Size: 4608x3456
Projection: Normal (rectilinear)
Response type: custom (EMoR)
HFOV: 68
Exposure value: 8.3


Remapping LDR images...
Blending images...

Process took 1: 8 min

Bug#910728: [Pkg-utopia-maintainers] Bug#910728: network-manager-openvpn-gnome: TLS authentication does not get saved

[Michael Biebl]

Am 17.10.23 um 17:14 schrieb Michael Biebl:
Then report this upstream at 
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues



Or better directly at
https://gitlab.gnome.org/GNOME/NetworkManager-openvpn



OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1054128: coreutils: cp -p --parent not working

[Pádraig Brady]

On 17/10/2023 15:54, Georg Borgström wrote:

Package: coreutils
Version: 9.1-1
Severity: normal

Dear Maintainer,

This doesn't work in bookworm but works in bullseye:

$ mkdir /tmp/newdir
$ cp -p --parent /etc/passwd /tmp/newdir
cp: ‘etc’: No such file or directory

/tmp/newdir/etc gets created but with wrong permission and also the error 
message above.

$ ls -ald /tmp/newdir/etc
drwx-- 2 gb gb 60 Oct 17 14:54 /tmp/newdir/etc

Should be:
drwxr-xr-x 2 gb gb 60 Oct 17 11:09 /tmp/newdir/etc

Could be the same as:
https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/2017414


I think the upstream fix (released in coreutils 9.4) is:
https://github.com/coreutils/coreutils/commit/c6b1fe434

Pádraig

Bug#1052502: ibus crashed and refuses to restart

[Gunnar Hjalmarsson]

Control: tags -1 + moreinfo

Hi Nicolas,

Since you are on LXDE it's not clear to me why you use IBus at all. You 
don't need IBus to use dead keys and a compose key.


If you run

im-config -n none

and reboot, you will enter a session without ibus-daemon running and 
without environment variables telling your apps to use IBus.


Can you please try that and let us know if you are able to make sense of 
your keyboard that way.


--
Rgds,
Gunnar Hjalmarsson

Bug#910728: [Pkg-utopia-maintainers] Bug#910728: network-manager-openvpn-gnome: TLS authentication does not get saved

[Michael Biebl]

Am 16.10.23 um 08:48 schrieb neonknight:

Package: network-manager-openvpn-gnome
Version: 1.10.2-2
Followup-For: Bug #910728
X-Debbugs-Cc: debian-b...@neonknight.ch

what relevant information are the developers missing to be able to fix this
issue?


Thanks for your offer to help.

Since you are able to reproduce the issue, please run a git bisect to 
find the first faulty commit.
Then report this upstream at 
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues

and report back with the issue number.

Regards,
Michael


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1054088: sanoid: let dh_installsystemd choose the location of units

[Michael Jeanson]

On 2023-10-16 15:38, Helmut Grohne wrote:

Source: sanoid
Version: 2.2.0-1
Tags: patch
User: helm...@debian.org
Usertags: dep17m2

We want to move all aliased files from / to /usr to finalize the
/usr-merge transition via DEP17. sanoid is affected, because it installs
two systemd units. One of its units is installed via dh_installsystemd
and will move to /usr when the placement in dh_installsystemd changes.
The other unit is hard coded to /lib/systemd/system via
debian/sanoid.install. Rather than moving it to /usr, I recommend
installing it using dh_installsystemd as well, because it'll revert back
to the old location when uploading to bookworm-backports, which will
comply with the file move moratorium that still is in effect for
bookworm. I'm attaching a patch for your convenience.

Helmut


Thanks for the patch, it will be included in the next upload.

Bug#1054128: coreutils: cp -p --parent not working

[Georg Borgström]

Package: coreutils
Version: 9.1-1
Severity: normal

Dear Maintainer,

This doesn't work in bookworm but works in bullseye:

$ mkdir /tmp/newdir
$ cp -p --parent /etc/passwd /tmp/newdir
cp: ‘etc’: No such file or directory

/tmp/newdir/etc gets created but with wrong permission and also the error 
message above.

$ ls -ald /tmp/newdir/etc
drwx-- 2 gb gb 60 Oct 17 14:54 /tmp/newdir/etc

Should be:
drwxr-xr-x 2 gb gb 60 Oct 17 11:09 /tmp/newdir/etc

Could be the same as:
https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/2017414

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

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

Versions of packages coreutils depends on:
ii  libacl1  2.3.1-3
ii  libattr1 1:2.5.1-4
ii  libc62.36-9+deb12u3
ii  libgmp10 2:6.2.1+dfsg1-1.1
ii  libselinux1  3.4-1+b6

coreutils recommends no packages.

coreutils suggests no packages.

-- no debconf information

Bug#1054019: broken sample rate passthrough

[Dylan Aïssi]

Hi Nicholas,

Le dim. 15 oct. 2023 à 23:27, Nicholas D Steeves  a écrit :
>
> So yeah, it looks like Pipewire's default sample rate is always
> applied when using pipewire or JACK sinks, despite
> "default.clock.allowed-rates" being set, except with using pulseaudio.
> I'm not sure why this is the case, but it seems wrong that everything
> is buggy except Pipewire and Pulseaudio...and that's why I'm reporting
> this bug against pipewire.  Please feel free to reassign if this is a
> naive assessment.
>
> I hope this is enough to identify which package[s] is[are] affected as
> well as to forward the bug upstream.  Please let me know if any more
> info is required.

pipewire 0.3.65 is quite old now. May I ask you to test with pipewire
in bookworm-backports (i.e. 0.3.82-1~bpo12+1)? To check if this bug
is already fixed in the latest version.

Best regards,
Dylan

Bug#1036277: Ship keama - The KEA Migration Assistant

[Athos Ribeiro]

On Mon, Oct 16, 2023 at 06:26:50PM -0300, Santiago Ruano Rincón wrote:


Oi Athos,


Hey Santiago!


isc-dhcp is FTBFS on s390x, and I think it is keama-related.


It is, I am sorry for not spotting this earlier.



The relevant part of a (giveback) build log:

   [snip]
   cat /tmp/keama-test-errors
   configdata4.in4 doesn't provide expected output
   test -f /tmp/keama-test-errors
   test ! -s /tmp/keama-test-errors
   make[1]: *** [debian/rules:83: override_dh_auto_test] Error 1
   make[1]: Leaving directory '/<>'
   make: *** [debian/rules:42: build-arch] Error 2
   dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit 
status 2
   [snip]

Full log:
https://buildd.debian.org/status/fetch.php?pkg=isc-dhcp=s390x=4.4.3-P1-3=1694824585=0

Do you have any idea why?


Yes. After some debugging, I realized that the upstream tests assume
that the tests will run in a little-endian machine.

keama/tests/configdata4.in4 has
  min-secs 20;
and
keama/tests/configdata4.out has
//{
//  "name": "min-secs",
//  "code": 14,
//  "value": 5120
//},

It uses libc's ntohs function to convert that value from network byte
order to the host's byte order.

In little endian machines, it will convert 20 into 5120. However, if we
are in big endian manchines (e.g., s390x), it will convert 20 into 20
(noop).

Here is a small reproducer:

  #include 
  #include 

  void main() {
uint8_t a = 1;
printf("%d\n", ntohs(a));
  }

This should print 20 in x86_64 and print 1 in s390x.

While this could drive additional discutions [1] such as whether a
configuration file used in one architecture should only be converted in
a computer using the same architecture and should be intended to be used
in the same architecture, this specific configuration directive
(min-secs) is not yet supported by kea (note that the converted
configuration snippet is commented out, and if you check
keama/tests/configdata4.out, there are additional comments pointing the
lack of support out and a link to an upstream bug).

Therefore, I am inclined to patch the test suite so that the min-secs
value in that test (and in the test expectation) is set to 0 (zero),
which would cover both little and big endian systems, but will no longer
test the conversion. Then, I will also file an upstream bug to discuss
[1] and check whether the tests should support s390x systems.

Thoughts?

--
Athos Ribeiro

Bug#1015915: fixed in pipewire 0.3.81-1

[Dylan Aïssi]

Hi Vuk,

Le mar. 17 oct. 2023 à 16:15, Vuk Mirovic  a écrit :
>
> Can we get malloc_trim fix backported to stable?
> It can be applied to 0.3.65 easily and shouldn't mess anything.

Sure, but since it's not a security fix, we will have to follow the
"proposed-updates" mechanism [1]. That means it will land in
the debian archive with the next point release. We can anyway
already prepare the package, thus I just created a new branch
"debian/bookworm-updates" on salsa [2]. I don't have much time
this week, so feel free to propose a MR, or I will prepare when
time permits.

Best regards,
Dylan

[1] https://www.debian.org/releases/proposed-updates
[2] 
https://salsa.debian.org/utopia-team/pipewire/-/commits/debian/bookworm-updates

Bug#1054127: scummvm: Please consider enabling support for grim:monkey4

[Antoine Le Gonidec]

Package: scummvm
Version: 2.7.0+dfsg-1
Severity: wishlist

Upstream build rules do not include the grim:monkey4 engine in the
generated binary.

Please consider tweaking debian/rules to enable it in the Debian build
of ScummVM, so it could be used as an alternative to WINE when someone
wants to play Monkey Island 4.

While this engine is still in an unfinished state, an explicit warning
is shown when trying to use it. So even if support for it is included,
users are warned that they should not get their expectations too high.

In addition it might provide us with more bug reports using this engine,
leading to more help in getting it to a more complete state.

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

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

Versions of packages scummvm depends on:
ii  liba52-0.7.4   0.7.4-20
ii  libasound2 1.2.9-2 # Not upgraded to 1.2.10-1 because of bug 
#1051901
ii  libc6  2.37-12
ii  libcurl3-gnutls8.4.0-2
ii  libfaad2   2.10.1-1
ii  libflac12  1.4.3+ds-2
ii  libfluidsynth3 2.3.4-1
ii  libfreetype6   2.13.2+dfsg-1
ii  libfribidi01.0.13-3
ii  libgif75.2.1-2.5
ii  libglib2.0-0   2.78.0-2
ii  libgtk-3-0 3.24.38-5
ii  libieee1284-3  0.2.11-14
ii  libjpeg62-turbo1:2.1.5-2
ii  libmad00.15.1b-10.1+b1
ii  libmpeg2-4 0.5.1-9
ii  libogg01.3.5-3
ii  libpng16-161.6.40-2
ii  libsdl2-2.0-0  2.28.4+dfsg-1
ii  libsdl2-net-2.0-0  2.2.0+dfsg-2
ii  libsndio7.01.9.0-0.3+b2
ii  libspeechd20.11.5-2
ii  libstdc++6 13.2.0-5
ii  libtheora0 1.1.1+dfsg.1-16.1+b1
ii  libvorbis0a1.3.7-1
ii  libvorbisfile3 1.3.7-1
ii  scummvm-data   2.7.0+dfsg-1
ii  zlib1g 1:1.2.13.dfsg-3

scummvm recommends no packages.

Versions of packages scummvm suggests:
pn  beneath-a-steel-sky 
pn  drascula
pn  flight-of-the-amazon-queen  
ii  fluidsynth  2.3.4-1
pn  lure-of-the-temptress   

-- no debconf information

Bug#1003868: Debian 11

[Alberto Gonzalez Iniesta]

tags 1003868 + pending
thanks

Hi, the configure option will be added in the next upload.
Sorry Albert, old releases aren't built with it.

Regards,

Alberto


On Fri, Sep 29, 2023 at 03:34:55PM +0200, Albert van der Veen wrote:
> In response to the bug report that covers 2.9.3-1+deb10u1: Is
> 2.9.3-3+deb11u1 built with the option --enable-collection-global-lock?
> 
> Best,
> Albert van der Veen

-- 
Alberto Gonzalez Iniesta| Formación, consultoría y soporte técnico
mailto/sip: a...@inittab.org | en GNU/Linux y software libre
Encrypted mail preferred| http://inittab.com

Key fingerprint = 5347 CBD8 3E30 A9EB 4D7D  4BF2 009B 3375 6B9A AA55

Bug#1053826: gcc-12: internal compiler error with template specialization on floating point non-type-param in C++20 mode

[Matthias Klose]

This is fixed in GCC 13, available in testing and unstable.  Doesn't look like a 
regression, so it's unlikely to be backported.


On 12.10.23 09:20, Andre Naujoks wrote:

Package: gcc-12
Version: 12.3.0-10
Severity: normal
X-Debbugs-Cc: andre.nauj...@keysight.com

Hello.

The following piece of code generates a compiler error with gcc-12 in C++20
mode:

template 
struct F {
 static double foo() { return D; }
};

template 
struct F {
 static double foo() { return 1.0; }
};

int main()
{
 return F::foo();
}

gcc-13 in sid does compile this correctly. on godbolt only gcc-trunk, not
gcc-13, compiles this, so from my point of view, it may be a Debian patch in
gcc-13 in sid, which fixes this.

The error (on gcc-12 from sid) is this:

$ g++-12 -std=c++20 -o test test.cpp
test.cpp: In function ‘int main()’:
test.cpp:13:29: internal compiler error: in unify, at cp/pt.cc:24903
13 | return F::foo();
   | ^~
0x7f41729256c9 __libc_start_call_main
 ../sysdeps/nptl/libc_start_call_main.h:58
0x7f4172925784 __libc_start_main_impl
 ../csu/libc-start.c:360
Please submit a full bug report, with preprocessed source (by using -freport-
bug).
Please include the complete backtrace with any bug report.
See  for instructions.



gcc in bookworm looks a little different but should be the same bug:

$ g++ -std=c++20 -o test test.cpp
test.cpp: In function 'int main()':
test.cpp:13:29: internal compiler error: in unify, at cp/pt.cc:24832
13 | return F::foo();
   | ^~
0x1afaeb6 internal_error(char const*, ...)
 ???:0
0x69ec5a fancy_abort(char const*, int, char const*)
 ???:0
0x813491 most_specialized_partial_spec(tree_node*, int)
 ???:0
0x830231 instantiate_class_template(tree_node*)
 ???:0
0x86621b complete_type(tree_node*)
 ???:0
0x7f5c79 c_parse_file()
 ???:0
0x8e019d c_common_parse_file()
 ???:0
Please submit a full bug report, with preprocessed source (by using -freport-
bug).
Please include the complete backtrace with any bug report.
See  for instructions.

Thanks in advance!

Andre



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

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

Versions of packages gcc-12 depends on:
ii  binutils   2.41-6
ii  cpp-12 12.3.0-10
ii  gcc-12-base12.3.0-10
ii  libc6  2.37-12
ii  libcc1-0   13.2.0-5
ii  libgcc-12-dev  12.3.0-10
ii  libgcc-s1  13.2.0-5
ii  libgmp10   2:6.3.0+dfsg-2
ii  libisl23   0.26-3
ii  libmpc31.3.1-1
ii  libmpfr6   4.2.1-1
ii  libstdc++6 13.2.0-5
ii  libzstd1   1.5.5+dfsg2-2
ii  zlib1g 1:1.2.13.dfsg-3

Versions of packages gcc-12 recommends:
ii  libc6-dev  2.37-12

Versions of packages gcc-12 suggests:
ii  gcc-12-doc   12.2.0-1
pn  gcc-12-locales   
pn  gcc-12-multilib  

-- no debconf information

Bug#1052015: RFS: blktrace/1.3.0-1 -- utilities for block layer IO tracing

[Daichi Fukui]

Hi Bas, Dmitry,

It's been a while since the last contact.
I would appreciate it if you could take some time to review this draft
and sponsor it.

Best,
Fukui

On Sat, 23 Sept 2023 at 16:06, Daichi Fukui
 wrote:
>
> Hi,
> (CC: Bas, Dmitry)
>
> It's been a week since I filed this bug report.
> I would appreciate it if you could take time to review this draft and
> sponsor it.
>
> Best,
> Fukui
>
> On Sat, 16 Sep 2023 14:21:01 +0900 Daichi Fukui
>  wrote:
> > Package: sponsorship-requests
> > Severity: normal
> >
> > Dear mentors,
> > (CC: Bas, Dmitry)
> >
> > I am looking for a sponsor for the new version 1.3.0-1 of the package
> > "blktrace" as shown below.
> > If you think this is satisfactory and helpful, I would like you to
> > upload that draft to the archive.
> >
> > FYI, I forked the blktrace repository in salsa and added my changes as
> > well as pristine-tar and upstream branches for 1.3.0.
> > Hopefully it is helpful for you to update the repository in salsa.
> >
> >  * Package name : blktrace
> >Version  : 1.3.0-1
> >Upstream contact : [fill in name and email of upstream]
> >  * URL  :
> > https://git.kernel.org/pub/scm/linux/kernel/git/axboe/blktrace.git/about/
> >  * License  : GPL, GPL-2+, public-domain, GPL-2
> >  * Vcs  : https://salsa.debian.org/debian/blktrace
> >Section  : utils
> >
> > The source builds the following binary packages:
> >
> >   blktrace - utilities for block layer IO tracing
> >
> > To access further information about this package, please visit the
> > following URL:
> >
> >   https://mentors.debian.net/package/blktrace/
> >
> > Alternatively, you can download the package with 'dget' using this command:
> >
> >   dget -x 
> > https://mentors.debian.net/debian/pool/main/b/blktrace/blktrace_1.3.0-1.dsc
> >
> > Changes since the last upload:
> >
> >  blktrace (1.3.0-1) unstable; urgency=medium
> >  .
> >[ Debian Janitor ]
> >* Trim trailing whitespace.
> >* Remove 1 obsolete maintscript entry.
> >* Bump debhelper from old 11 to 13.
> >* Set debhelper-compat version in Build-Depends.
> >* Fix day-of-week for changelog entry 0~git-20061221162513-1.
> >* Update standards version to 4.6.0, no changes needed.
> >* Avoid explicitly specifying -Wl,--as-needed linker flag.
> >[ Fukui Daichi ]
> >* New upstream version 1.3.0
> >* Remove and fix patches to catch up with 1.3.0
> >* Update d/copyright
> >
> > Regards,
> > Fukui
> >
> >

Bug#916475: [Pkg-electronics-devel] Bug#916475: ghdl: various suggestions to simplify the packaging

[Daniel Gröber]

Hi Nicolas,

On Wed, Oct 11, 2023 at 10:58:22PM +0200, Nicolas Boulenguez wrote:
> > honestly the whole link script looks like a hack to me, I prefer the
> > way it was before.
> 
> I agree that an executable debian/libghdl-dev.links is a last resort,
> but a reader discovering the package does not need to [...].

Well at least the new version has more docs and works, I'll take it. Let's
see if Andreas just reverts it or not ;)

More comments inline below.

> Subject: [PATCH 07/14] Delegate computation of Built-Using to dh-builtusing

This breaks the build for me since I build the source package on bookworm
(via gbp). I might hold off on this one until dh-builtusing is backported.

> From caf2fa626289a1850da5d0c46431b009f30c793c Mon Sep 17 00:00:00 2001
> From: Nicolas Boulenguez 
> Date: Thu, 5 Oct 2023 14:39:35 +0200
> Subject: [PATCH 12/14] Various minor improvements in the test driver
> 
> Enable more alerts by the shell.
> 
> Check the argument count.
> 
> Replace test cascades with 'case' constructs.
> 
> There is no need to create RUNDIR because the script is called after a
> 'make install'.
> 
> There is no need to check that the RUNDIR variable is not empty, it is
> set in all branches of the previous construct.
> ---
>  debian/tests/ghdl-tests | 34 +++---
>  1 file changed, 15 insertions(+), 19 deletions(-)
> 
> diff --git a/debian/tests/ghdl-tests b/debian/tests/ghdl-tests
> index 5868e16c..871d594b 100755
> --- a/debian/tests/ghdl-tests
> +++ b/debian/tests/ghdl-tests
> @@ -1,39 +1,35 @@
>  #!/bin/sh
>  
> -set -e
> +set -C -e -f -u
>  
>  # The pyunit tests are not run here. These parts are not activated in
>  # Debian yet.
>  TESTS="sanity gna vests synth vpi vhpi"
>  
> +test $# = 2

This is kind of obscure, think of the (lack of an) error message. If we
skip this we'll get an "undefined $2" error due to set -u, which I find is
more helpful than a quiet exit rv>0.

> -if [ "$2" = mcode ]; then
> - BACKEND=mcode
> -elif [ "$2" = llvm ]; then
> - BACKEND=llvm
> -elif [ "$2" = gcc ]; then
> - BACKEND=gcc
> -else
> +case "$2" in
> +gcc|llvm|mcode)
> + BACKEND=$2
> + ;;
> +*)
>   echo >&2 "Invalid backend specification"
>   exit 1
> -fi
> +esac
>  
> -if [ "$1" = buildtest ]; then
> +case "$1" in
> +buildtest)
>   RUNDIR=testrundir/$BACKEND
> - mkdir -p "$RUNDIR"
>   GHDL="$PWD/$RUNDIR/usr/bin/ghdl-$BACKEND"
> -elif [ "$1" = autopkgtest ]; then
> + ;;
> +autopkgtest)
>   RUNDIR="$AUTOPKGTEST_TMP"
>   GHDL=/usr/bin/ghdl-$BACKEND
> -else
> + ;;
> +*)
>   echo >&2 "Invalid test environment specification"
>   exit 1
> -fi
> -
> -if [ -z "$RUNDIR" ]; then
> - echo >&2 "RUNDIR is empty string"
> - exit 1
> -fi
> +esac
>  
>  # Copy testsuite into $RUNDIR to execute there, so that no cleanup is 
> necessary
>  # (entire $RUNDIR will be deleted later). Also copy src/grt as at least one 
> test
> -- 
> 2.39.2

--Daniel


signature.asc
Description: PGP signature

Bug#1053729: RFP: SAIL image decoding library

[Dmitry Baryshev]

Hi!

> Does it produce desired Debian packages?

I've just pushed a couple of fixes to the Debian rules. I'm able to build
packages on LUbuntu 23.04. Maybe a couple of small fixes are still needed
to build packages on Debian. So the recommended git sha to use is
4705cb4cf96. It's a release candidate and ready to use in client
applications.

> Are these packages lintian-clean?

The only error Lintian showed is "unknown distribution", but this is
because I run it on Ubunutu.

> Do you know any software already in Debian which would benefit from
having SAIL in Debian?

It's a library and I guess end users will benefit from it.

-- Dmitry


вт, 17 окт. 2023 г. в 14:43, Andrius Merkys :

> Hi Dmitry,
>
> On 2023-10-17 13:29, Dmitry Baryshev wrote:
> > It would be great to have SAIL in Debian, at least in experimental. It's
> > a C/C++ image decoding library similar to FreeImage. It's already
> > available in Conan and VCPKG with thousands of installations.
> >
> > Website: https://sail.software/ 
> > GitHub:https://github.com/HappySeaFox/sail
> > 
> > RFP request: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053729
> > 
> > Build system: CMake
> > Debian rules: Yes, but need revisiting
> >
> > Please pardon me if I'm writing to a wrong mailing list. Please CC any
> > comments as I'm not in the list.
>
> I saw the GitHub repository already has debian/ directory, this is a
> good start. Does it produce desired Debian packages? Are these packages
> lintian-clean? Do you know any software already in Debian which would
> benefit from having SAIL in Debian?
>
> Best wishes,
> Andrius
>

Bug#1054125: dh-builtusing: Please backport dh-builtusing to bookworm

[Daniel Gröber]

Source: dh-builtusing
Version: 0.0.5
Severity: wishlist
X-Debbugs-Cc: d...@darkboxed.org

Hi Nicolas,

would it be possible to get dh-builtusing backported for bookworm? We
want to use dh-builtusing in ghdl (as you know ;), but I run my
package builds on bookworm, inside an sbuild chroot, but gbp breaks
when building the source package it's going to hand to the chroot.

```
dh /usr/share/ada/packaging.mk
dh: error: unable to load addon builtusing: Can't locate 
Debian/Debhelper/Sequence/builtusing.pm in @INC (you may need to install the 
Debian::Debhelper::Sequence::builtusing module) (@INC contains: /etc/perl 
/usr/local/lib/x86_64-linux-gnu/perl/5.36.0 /usr/local/share/perl/5.36.0 
/usr/lib/x86_64-linux-gnu/perl5/5.36 /usr/share/perl5 
/usr/lib/x86_64-linux-gnu/perl-base /usr/lib/x86_64-linux-gnu/perl/5.36 
/usr/share/perl/5.36 /usr/local/lib/site_perl) at (eval 15) line 1.
BEGIN failed--compilation aborted at (eval 15) line 1.

debian/rules:10: /usr/share/ada/packaging.mk: No such file or directory
make: *** [debian/rules:65: /usr/share/ada/packaging.mk] Error 255
E: Failed to clean source directory /home/dxld/share/dev/deb/pkg/ghdl 
(/home/dxld/share/dev/deb/pkg/ghdl_3.0.0+dfsg2-1.dsc)
gbp:error: 'sbuild -d unstable --anything-failed-commands %SBUILD_SHELL' 
failed: it exited with 1
```

I've reported the dh-ada-library error seperately, I think either of
those problems would break the srcpkg build.

Thanks,
--Daniel

Bug#1054124: dh-ada-library: dh_ada_library output causes /usr/share/ada/packaging.mk:81: *** missing separator error

[Daniel Gröber]

Package: dh-ada-library
Version: 8.6
Severity: normal
X-Debbugs-Cc: d...@darkboxed.org

Hi Nicolas,

on my bookworm system importing dh-ada-library's packaging.mk is
causing a make error. AFAICT due to `dh_ada_library --export-versions`
including some copyright output in DEB_GNAT_VERSION:

```
$ dh_ada_library --export-versions
DEB_ADA_SOURCE_DIR:=usr/share/ada/adainclude
DEB_LIB_DIR:=usr/lib/x86_64-linux-gnu
DEB_ADA_LIB_INFO_DIR:=usr/lib/x86_64-linux-gnu/ada/adalib
DEB_GNAT_PROJECT_DIR:=usr/share/gpr
DEB_GNAT_VERSION:=GNATMAKE 10.2.1 20210110
Copyright (C) 1995-2020, Free Software Foundation, Inc.
This is free software; see the source for copying conditions.
There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR 
PURPOSE.
```

I'm not sure what changed to break this, ghdl has been using
dh-ada-library for a while now and this wasn't a problem before.

Thanks,
--Daniel

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

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

Versions of packages dh-ada-library depends on:
ii  debhelper  13.11.4
ii  gnat-1010.2.1-6
ii  perl   5.36.0-7

dh-ada-library recommends no packages.

Versions of packages dh-ada-library suggests:
pn  gprbuild  

-- no debconf information

Bug#1052159: Patch available

[Daniel Teichmann]

Hey,

The underlaying problem was that at $config->ldap->re were 
LDAP\ResultEntry objects stored. They can't be serialized anymore (since 
PHP8.1).
And since $ldap->re is inside of $config object, it will be written to 
$_SESSION too. This fails silently (except if you call 
session_write_close() somewhere).


This patch should clean up the remaining results.

--- a/html/main.php

+++ b/html/main.php
@@ -524,6 +524,9 @@
 /* Show page... */
 echo $display;

+/* Avoid serializing results. */
+$config->ldap->clearResult();
+
 /* Save plist and config */
 session::global_set('plist',$plist);
 session::global_set('config',$config);
--- a/include/class_ldap.inc
+++ b/include/class_ldap.inc
@@ -475,6 +475,10 @@
 if (!is_null(self::$sr[$srp]) && !is_bool(self::$sr[$srp])) {
 @ldap_free_result(self::$sr[$srp]);
 }
+
+    if (isset($this->re) && in_array($srp, $this->re) && 
isset($this->re[$srp])) {

+    unset($this->re[$srp]);
+    }
 }
 }

--- a/html/index.php
+++ b/html/index.php
@@ -380,7 +380,8 @@

 stats::log('global', 'global', array(), $action = 'login', 
$amount = 1, 0);


-    unset($config->ldap->re); // Avoid serializing results.
+    // Avoid serializing results.
+    $config->ldap->clearResult();
 session_write_close();

 if (isset($plug) && isset($plist->dirlist[$plug])) {

Bug#1054108: apt-listchanges: Shows ancient NEWS for falkon and src:libdrm packages

[Jonathan Kamens]

Is it possible for you to find the file in 
/var/lib/apt/listchanges-snapshots corresponding to the time of the apt 
run when this issue occurred and either email it to me separately (don't 
append to the ticket) if it's small enough or if it's not then upload it 
somewhere and share the link with me? That will greatly help me to 
troubleshoot this.


Thanks,

jik

On 10/17/23 02:36, Axel Beckert wrote:

Package: apt-listchanges
Version: 4.2
Severity: normal

Hi Jonathan,

two other cases of ancient NEWS items being show, this time with
apt-listchanges 4.2 and when upgrading falkon from 23.08.1-1 to
23.08.2-1 and multiple src:libdrm packages from 2.4.115-1 to 2.4.116-1:

$ dpkg -l 'libdrm*'
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Tr
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name  Version  Architecture Description
+++-=---===
ii  libdrm-amdgpu1:amd64  2.4.115-1amd64Userspace interface
ii  libdrm-amdgpu1:i386   2.4.115-1i386 Userspace interface
ii  libdrm-common 2.4.115-1all  Userspace interface
ii  libdrm-dev:amd64  2.4.115-1amd64Userspace interface
ii  libdrm-intel1:amd64   2.4.115-1amd64Userspace interface
ii  libdrm-intel1:i3862.4.115-1i386 Userspace interface
ii  libdrm-nouveau2:amd64 2.4.115-1amd64Userspace interface
ii  libdrm-nouveau2:i386  2.4.115-1i386 Userspace interface
ii  libdrm-radeon1:amd64  2.4.115-1amd64Userspace interface
ii  libdrm-radeon1:i386   2.4.115-1i386 Userspace interface
ii  libdrm2:amd64 2.4.115-1amd64Userspace interface
ii  libdrm2:i386  2.4.115-1i386 Userspace interface
ii  libdrm2-dbgsym:amd64  2.4.115-1amd64debug symbols for l

I got shown three NEWS entries, one from a few days ago (correct), one
from 2018 (falkon) and one from 2007, seemingly for libdrm2, but I
suspect that at least the multiarch setup (libdrm2:amd64 vs
libdrm2:i386, see above) might have played a role:

--- News for falkon ---

falkon (3.0.0-3) unstable; urgency=medium
   ===

   Falkon is a replacement for the former package Qupzilla. If you, or some
   other user of this computer were using Qupzilla formerly, it is possible
   to restore bookmarks which were gathered with Qupzilla, so they become
   available for Falkon users.

   Here is a method for user John Doe, in shell language:

   # USER_HOME=/home/johnDoe;
   # cp ${USER_HOME}/.config/qupzilla/profiles/default/bookmarks.json \
   ${USER_HOME}/.config/falkon/profiles/defaults/

   Please notice that doing so will erase any previous file
   ${USER_HOME}/.config/falkon/profiles/defaults/bookmarks.json

  -- Georges Khaznadar   Tue, 03 Apr 2018 18:26:55 +0200

[Inbetween was NEWS for xca 2.5.0-1 which was current as I upgraded from
2.4.0-2+b1]

--- News for libdrm2 ---

libdrm (2.3.0-4) experimental; urgency=low

   * We are now shipping libdrm with the default permissions set to 666,
 rather than the upstream default of 660. If you have untrusted users,
 you should configure the X server to explicitly use a mode of 660 in
 the xorg.conf.

  -- David Nusinow   Wed, 18 Apr 2007 22:44:21 -0400

-- Package-specific info:

-- System Information:
Debian Release: trixie/sid
   APT prefers unstable
   APT policy: (990, 'unstable'), (600, 'testing'), (500, 'unstable-debug'), 
(500, 'buildd-unstable'), (110, 'experimental'), (1, 'experimental-debug'), (1, 
'buildd-experimental')
merged-usr: no
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.5.0-1-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
LSM: AppArmor: enabled

Versions of packages apt-listchanges depends on:
ii  apt 2.7.6
ii  cdebconf [debconf-2.0]  0.271
ii  debconf [debconf-2.0]   1.5.82
ii  python3 3.11.4-5+b1
ii  python3-apt 2.6.0
ii  python3-debconf 1.5.82
ii  sensible-utils  0.0.20
ii  ucf 3.0043+nmu1

apt-listchanges recommends no packages.

Versions of packages apt-listchanges suggests:
ii  alacritty [x-terminal-emulator]0.12.2-2+b1
ii  chromium [www-browser] 118.0.5993.70-1
ii  cool-retro-term [x-terminal-emulator]  1.2.0+ds2-1+b1
ii  dillo [www-browser]3.0.5-7+b1
ii  edbrowse [www-browser] 3.7.7-5
ii  elinks [www-browser]   0.16.1.1-4
ii  eterm [x-terminal-emulator]0.9.6-7.1
ii  falkon [www-browser]   23.08.1-1
ii  firefox [www-browser]  118.0.2-1
ii  firefox-esr [www-browser]  115.3.0esr-1+b1
ii  gnome-console 

Bug#1054115: closed by Colin Watson (Re: Bug#1054115: broken on NFS)

[Anton Ivanov]

On 17/10/2023 13:00, Debian Bug Tracking System wrote:

This is an automatic notification regarding your Bug report
which was filed against the man-db package:

#1054115: broken on NFS

It has been closed by Colin Watson .

Their explanation is attached below along with your original report.
If this explanation is unsatisfactory and you have not received a
better one in a separate message then please contact Colin Watson 
 by
replying to this email.



Apologies for reopening, you can close it again after that.

Actually, to be fair this is not just usr.bin.man.

As apparmor creep across more and more things it needs to become aware 
of network filesystems.


What Debian as a whole needs is an extra profile to load

network inet

network inet6

as defaults ONLY if /usr and/or root is on a network filesystem. That is 
an apparmor bug, not man bug.


Further to this. For documentation purposes: network inet and inet6 
needs to added both to the man and groff profiles.


Fixing man results in a similar failure invoking groff. It starts 
working only after both have been fixed.


--
Anton R. Ivanov
Cambridgegreys Limited. Registered in England. Company Number 10273661
https://www.cambridgegreys.com/

Bug#1054123: apparmor breaks nfs root

[Anton Ivanov]

Package: apparmor
Version: 3.0.8-3
Severity: important

Dear Maintainer,

The default profile denies network functionality and it breaks
man and other software which has an apparmor profile. They stop
working on NFS.

For an example see Debian bug 1054115

While it is possible to solve it on a case by case basis, the
right bugfix is to check if root and/or /usr are on NFS and
load an extra profile to allow network access.

Alternatively, the kernel should stop treating network filesystem
access as network access for apparmor purposes. That, however,
is likely to a be a bit difficult.

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

Kernel: Linux 5.10.0-22-amd64 (SMP w/12 CPU threads)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages apparmor depends on:
ii  debconf [debconf-2.0]  1.5.82
ii  libc6  2.36-9+deb12u2

apparmor recommends no packages.

Versions of packages apparmor suggests:
pn  apparmor-profiles-extra  
pn  apparmor-utils   

-- debconf information excluded

Bug#1054122: bookworm-pu: package axis/1.4-28

[Markus Koschany]

Package: release.debian.org
Severity: normal
Tags: bookworm
User: release.debian@packages.debian.org
Usertags: pu
X-Debbugs-Cc: a...@debian.org

[ Reason ]

Fixing CVE-2023-40743: Axis allows potentially dangerous lookup
mechanisms which may lead to DoS, SSRF or even RCE.

[ Tests ]

The fix is trivial. If the name of the JNDI service contains a certain
string then do nothing. That filters out unsupported protocols
effectively.

[ Risks ]

Axis in Debian is mainly used to build other software packages and
serves no other purpose. It is very unlikely that it is used in third
party applications outside of Debian but better safe than sorry.

[ 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

Regards,

Markus
diff -Nru axis-1.4/debian/changelog axis-1.4/debian/changelog
--- axis-1.4/debian/changelog   2018-12-03 08:25:51.0 +0100
+++ axis-1.4/debian/changelog   2023-10-17 14:05:20.0 +0200
@@ -1,3 +1,15 @@
+axis (1.4-28+deb12u1) bookworm; urgency=medium
+
+  * Team upload.
+  * Fix CVE-2023-40743:
+When integrating Apache Axis 1.x in an application, it may not have been
+obvious that looking up a service through "ServiceFactory.getService"
+allows potentially dangerous lookup mechanisms such as LDAP. When passing
+untrusted input to this API method, this could expose the application to
+DoS, SSRF and even attacks leading to RCE. (Closes: #1051288)
+
+ -- Markus Koschany   Tue, 17 Oct 2023 14:05:20 +0200
+
 axis (1.4-28) unstable; urgency=medium
 
   * Fixed the build failure with Java 11 (Closes: #911187)
diff -Nru axis-1.4/debian/patches/CVE-2023-40743.patch 
axis-1.4/debian/patches/CVE-2023-40743.patch
--- axis-1.4/debian/patches/CVE-2023-40743.patch1970-01-01 
01:00:00.0 +0100
+++ axis-1.4/debian/patches/CVE-2023-40743.patch2023-10-17 
14:05:20.0 +0200
@@ -0,0 +1,32 @@
+From: Markus Koschany 
+Date: Tue, 17 Oct 2023 00:46:49 +0200
+Subject: CVE-2023-40743
+
+Origin: 
https://github.com/apache/axis-axis1-java/commit/7e66753427466590d6def0125e448d2791723210
+---
+ src/org/apache/axis/client/ServiceFactory.java | 5 +
+ 1 file changed, 5 insertions(+)
+
+diff --git a/src/org/apache/axis/client/ServiceFactory.java 
b/src/org/apache/axis/client/ServiceFactory.java
+index 33054a5..73e89ee 100644
+--- a/src/org/apache/axis/client/ServiceFactory.java
 b/src/org/apache/axis/client/ServiceFactory.java
+@@ -106,6 +106,10 @@ public class ServiceFactory extends 
javax.xml.rpc.ServiceFactory
+ 
+ if (context != null) {
+ String name = (String)environment.get("jndiName");
++
++  if(name!=null && (name.toUpperCase().indexOf("LDAP")!=-1 || 
name.toUpperCase().indexOf("RMI")!=-1 || name.toUpperCase().indexOf("JMS")!=-1 
|| name.toUpperCase().indexOf("JMX")!=-1) || 
name.toUpperCase().indexOf("JRMP")!=-1 || 
name.toUpperCase().indexOf("JAVA")!=-1 || 
name.toUpperCase().indexOf("DNS")!=-1)  {
++  return null;
++}
+ if (name == null) {
+ name = "axisServiceName";
+ }
+@@ -120,6 +124,7 @@ public class ServiceFactory extends 
javax.xml.rpc.ServiceFactory
+ context.bind(name, service);
+ } catch (NamingException e1) {
+ // !!! Couldn't do it, what should we do here?
++  return null;
+ }
+ }
+ } else {
diff -Nru axis-1.4/debian/patches/series axis-1.4/debian/patches/series
--- axis-1.4/debian/patches/series  2018-12-03 00:33:50.0 +0100
+++ axis-1.4/debian/patches/series  2023-10-17 14:05:20.0 +0200
@@ -8,3 +8,4 @@
 java9-compatibility.patch
 java11-compatibility.patch
 CVE-2018-8032.patch
+CVE-2023-40743.patch

Bug#1040057: meaningless autopkg tests

[Matthias Klose]

Control: reassign -1 src:slixmpp

while looking at this, I think the autopkg test is just meaningless:

 - it installs the *build deps* of the source package
 - it then runs the tests without building the package
 - it does *not* install any of the built packages.
 - are the segfaults triggered by testing an unbuilt package?

that's not something an autopkg test should do. You are supposed to install the 
built packages, and test these packages.


You should run the the tests twice, one time with python3-slixmpp installed, and 
then with python3-slixmpp and python3-slixmpp-lib installed to test the package 
with the installed optimizations.


Please make sure that you test the installed packages, not the files from the 
source package.

Bug#1054121: bullseye-pu: package axis/1.4-28

[Markus Koschany]

Package: release.debian.org
Severity: normal
Tags: bullseye
User: release.debian@packages.debian.org
Usertags: pu
X-Debbugs-Cc: a...@debian.org

[ Reason ]

Fixing CVE-2023-40743: Axis allows potentially dangerous lookup
mechanisms which may lead to DoS, SSRF or even RCE.

[ Tests ]

The fix is trivial. If the name of the JNDI service contains a certain
string then do nothing. That filters out unsupported protocols
effectively.

[ Risks ]

Axis in Debian is mainly used to build other software packages and
serves no other purpose. It is very unlikely that it is used in third
party applications outside of Debian but better safe than sorry.

[ 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

Regards,

Markus
diff -Nru axis-1.4/debian/changelog axis-1.4/debian/changelog
--- axis-1.4/debian/changelog   2018-12-03 08:25:51.0 +0100
+++ axis-1.4/debian/changelog   2023-10-17 14:05:20.0 +0200
@@ -1,3 +1,15 @@
+axis (1.4-28+deb11u1) bullseye; urgency=medium
+
+  * Team upload.
+  * Fix CVE-2023-40743:
+When integrating Apache Axis 1.x in an application, it may not have been
+obvious that looking up a service through "ServiceFactory.getService"
+allows potentially dangerous lookup mechanisms such as LDAP. When passing
+untrusted input to this API method, this could expose the application to
+DoS, SSRF and even attacks leading to RCE. (Closes: #1051288)
+
+ -- Markus Koschany   Tue, 17 Oct 2023 14:05:20 +0200
+
 axis (1.4-28) unstable; urgency=medium
 
   * Fixed the build failure with Java 11 (Closes: #911187)
diff -Nru axis-1.4/debian/patches/CVE-2023-40743.patch 
axis-1.4/debian/patches/CVE-2023-40743.patch
--- axis-1.4/debian/patches/CVE-2023-40743.patch1970-01-01 
01:00:00.0 +0100
+++ axis-1.4/debian/patches/CVE-2023-40743.patch2023-10-17 
14:05:20.0 +0200
@@ -0,0 +1,32 @@
+From: Markus Koschany 
+Date: Tue, 17 Oct 2023 00:46:49 +0200
+Subject: CVE-2023-40743
+
+Origin: 
https://github.com/apache/axis-axis1-java/commit/7e66753427466590d6def0125e448d2791723210
+---
+ src/org/apache/axis/client/ServiceFactory.java | 5 +
+ 1 file changed, 5 insertions(+)
+
+diff --git a/src/org/apache/axis/client/ServiceFactory.java 
b/src/org/apache/axis/client/ServiceFactory.java
+index 33054a5..73e89ee 100644
+--- a/src/org/apache/axis/client/ServiceFactory.java
 b/src/org/apache/axis/client/ServiceFactory.java
+@@ -106,6 +106,10 @@ public class ServiceFactory extends 
javax.xml.rpc.ServiceFactory
+ 
+ if (context != null) {
+ String name = (String)environment.get("jndiName");
++
++  if(name!=null && (name.toUpperCase().indexOf("LDAP")!=-1 || 
name.toUpperCase().indexOf("RMI")!=-1 || name.toUpperCase().indexOf("JMS")!=-1 
|| name.toUpperCase().indexOf("JMX")!=-1) || 
name.toUpperCase().indexOf("JRMP")!=-1 || 
name.toUpperCase().indexOf("JAVA")!=-1 || 
name.toUpperCase().indexOf("DNS")!=-1)  {
++  return null;
++}
+ if (name == null) {
+ name = "axisServiceName";
+ }
+@@ -120,6 +124,7 @@ public class ServiceFactory extends 
javax.xml.rpc.ServiceFactory
+ context.bind(name, service);
+ } catch (NamingException e1) {
+ // !!! Couldn't do it, what should we do here?
++  return null;
+ }
+ }
+ } else {
diff -Nru axis-1.4/debian/patches/series axis-1.4/debian/patches/series
--- axis-1.4/debian/patches/series  2018-12-03 00:33:50.0 +0100
+++ axis-1.4/debian/patches/series  2023-10-17 14:05:20.0 +0200
@@ -8,3 +8,4 @@
 java9-compatibility.patch
 java11-compatibility.patch
 CVE-2018-8032.patch
+CVE-2023-40743.patch

Bug#986333: debian-security-support: Match ecosystems with limited support

[Santiago Ruano Rincón]

El 17/10/23 a las 09:18, Holger Levsen escribió:
> On Mon, Oct 16, 2023 at 11:49:27PM -0300, Santiago Ruano Rincón wrote:
> > As discussed in #debian-lts, unarchiving & reopening since this bug is
> > present in bullseye and bookworm: "golang*" installed packages are not
> > reported.
> 
> I really would have prefered a new bug, instead of unarchiving this one.

Why? It is the same bug. (Real question, I am happy to improve my
workflows)

> (Also because retitling it now, to make it clear that this bug is now about
> bookworm and bullseye, obfuscates the original issue of the bug.)
> 

I would expect that information be visible in the bug tracker without
retitling.

> And pretty please, please fix this in bookworm first, and get it accepted by
> SRMs, before pushing this into bullseye.

As discussed on #debian-lts, this is already fixed in bookworm.

Thanks!

 -- S


signature.asc
Description: PGP signature

Bug#1054098: base-passwd: Fix non-linux build

[Colin Watson]

On Tue, Oct 17, 2023 at 01:12:46AM +0200, Samuel Thibault wrote:
> I tried to build base-passwd on hurd-amd64, but this change
> 
>   Make it possible to configure whether to use SELinux or not.
> 
> broke the non-Linux builds. Here is a patch to fix this.

I used my preferred spelling of the variable name, but otherwise
applied.  Thanks!

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

Bug#1020303: Ping

[Alberto Gonzalez Iniesta]

On Sun, Oct 08, 2023 at 12:59:21PM +0100, Jonathan Wiltshire wrote:
> Hi,
> 
> On Mon, Jun 26, 2023 at 06:42:18PM +0100, Jonathan Wiltshire wrote:
> > On Tue, Mar 21, 2023 at 12:58:31PM +0100, Alberto Gonzalez Iniesta wrote:
> > > Hi, all. We're looking forward to uploading the latest CRS package to
> > > bullseye-backports, but this will require this pending update to
> > > bullseye. Any news on this front?
> > 
> > Please go ahead.
> 
> This request was approved but not uploaded in time for the previous point
> release (11.8). Should it be included in 11.9, or should this request be
> abandoned and closed?
> 

Hi, Jonathan.

Sorry I missed the previous point release. I thought, from Tobias last
mail, that he would do the upload. I just made it.

Regards,

Alberto

-- 
Alberto Gonzalez Iniesta| Formación, consultoría y soporte técnico
mailto/sip: a...@inittab.org | en GNU/Linux y software libre
Encrypted mail preferred| http://inittab.com

Key fingerprint = 5347 CBD8 3E30 A9EB 4D7D  4BF2 009B 3375 6B9A AA55

Bug#1054120: perl: open EMFILE failure misreported

[Eric Wong]

Package: perl
Version: 5.36.0-9
Severity: normal
Tags: upstream

The `open' perlop fails to report EMFILE (Too many open files)
when it fails due to having too many open files.

strace confirms the underlying open(2) syscall does fail with
EMFILE, but Perl misreports `$!' as EINVAL (Invalid argument).

A quick repro to open a lot of temporary files is below

perl -e '@x = map {open my $x, ">", undef or die "open: $!"; $x } (0..0xf)'

This also affects Perl 5.32.1 (in Debian bullseye).

I suspect this is because Perl is calling free(3) (or similar)
to release allocations upon open(2) failure and failed to
preserve the value of `errno' prior to calling free(3).

So something like this save_errno use ought to fix it:

int save_errno = errno;
free(allocated);
errno = save_errno;

Thanks in advance for forwarding this to upstream since I don't
agree with the Terms of Service or the JavaScript requirement
of upstream's bug tracker.

Bug#1052683: ITP: railway -- GUI application for searching train journeys

[Arnaud Ferraris]

Hi,

Le 26/09/2023 à 18:24, Blair Noctis a écrit :

On Tue, 26 Sep 2023 09:11:01 +0200 Arnaud Ferraris  wrote:

Package: wnpp
Severity: wishlist
Owner: Arnaud Ferraris 
X-Debbugs-Cc: debian-de...@lists.debian.org, aferra...@debian.org

* Package name: railway
   Version : 2.0.0
   Upstream Contact: Julian Schmidhuber 
* URL : https://gitlab.com/schmiddi-on-mobile/railway
* License : GPL
   Programming Lang: Rust
   Description : GUI application for searching train journeys

Railway is a graphical application allowing one to look up travel information
for many different railways, all without needing to navigate through different
websites.

It lets the user search for journeys, view their details (timetable, price,
delays, plaftorm if available) and bookmark them. This application also has an
adaptive user interface for use on mobile devices.


Please consider renaming it to something like gnome-railway (since it's a GNOME
application) or diebahn (its old name). "Railway" is too broad for an
application that almost exclusively serves the Europe.


Sure, I can go for "railway-gtk" as other similarly broadly named apps 
("gnome-railway" would be confusing in a different way, as it's not an 
official GNOME app). I'd rather not go for "diebahn" though, as it could 
be misleading users into thinking it's a Germany-only app.


Cheers,
Arnaud



OpenPGP_0xD3EBB5966BB99196.asc
Description: OpenPGP public key


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1053729: RFP: SAIL image decoding library

[Andrius Merkys]

Hi Dmitry,

On 2023-10-17 13:29, Dmitry Baryshev wrote:
It would be great to have SAIL in Debian, at least in experimental. It's 
a C/C++ image decoding library similar to FreeImage. It's already 
available in Conan and VCPKG with thousands of installations.


Website: https://sail.software/ 
GitHub:https://github.com/HappySeaFox/sail 

RFP request: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053729 


Build system: CMake
Debian rules: Yes, but need revisiting

Please pardon me if I'm writing to a wrong mailing list. Please CC any 
comments as I'm not in the list.


I saw the GitHub repository already has debian/ directory, this is a 
good start. Does it produce desired Debian packages? Are these packages 
lintian-clean? Do you know any software already in Debian which would 
benefit from having SAIL in Debian?


Best wishes,
Andrius

Bug#1054119: data loss patch for qpdf targeted at stable (11.3.0)

[Jay Berkenbilt]

Package: release.debian.org
X-Debbugs-CC: q...@debian.org

The attached patch to qpdf 11.3.0 fixes a bug that could potentially
result in loss of data. I'd like permission from the release team to
upload this to stable. I've been a debian developer since 2005, but
it's been years since I've last prepared a release to the stable
distribution. As far as I can tell, the current procedure is to upload
with the target distribution as "stable" and upload to ftp-master.
This will direct the package the proposed-updates queue. Is this
correct?

The nature of the bug is that, if a quoted octal character with one or
two digits instead of three digits appears in the file, the following
character will be dropped from the string. This bug snuck in in a pull
request I accepted that performed significant performance optimization
on the tokenizer. Because it only affects strings in metadata when
qpdf is used in its default configuration, and because such quoted
characters of this type don't appear very often, it's somewhat of a
corner case, but I think the bug is critical to fix because there is a
chance that it could silently damage files in ways that would be hard
to detect.

Please let me know if I should proceed with an update to stable.

--Jay Berkenbilt (a.k.a. q...@debian.org)--- libqpdf/QPDFTokenizer.cc.orig	2023-10-17 07:19:31.829119946 -0400
+++ libqpdf/QPDFTokenizer.cc	2023-10-17 07:20:55.689510562 -0400
@@ -739,17 +739,22 @@
 void
 QPDFTokenizer::inCharCode(char ch)
 {
+bool handled = false;
 if (('0' <= ch) && (ch <= '7')) {
 this->char_code = 8 * this->char_code + (int(ch) - int('0'));
 if (++(this->digit_count) < 3) {
 return;
 }
-// We've accumulated \ddd.  PDF Spec says to ignore
-// high-order overflow.
+handled = true;
 }
+// We've accumulated \ddd or we have \d or \dd followed by other
+// than an octal digit. The PDF Spec says to ignore high-order
+// overflow.
 this->val += char(this->char_code % 256);
 this->state = st_in_string;
-return;
+if (!handled) {
+inString(ch);
+}
 }
 
 void

Bug#1039380: sphinxsearch.service

[Luca Boccassi]

On Tue, 4 Jul 2023 12:55:05 +0200 Roland Rosenfeld 
wrote:
> tags 1039380 + patch
> thanks
> 
> In addition to the missing sphinxsearch.service unit, I noted another
> problem with /etc/init.d/sphinxsearch: stopping (or restarting) the
> service always takes 30 seconds on my system, which is quite annoying
> if you want to quickly restart the service or reboot the server and
> you have always to ways until the 30 seconds timeout occurs.
> 
> So I decided to create a little sphinxsearch.service, which does the
> job for my needs.  In contrast to /etc/init.d/sphinxsearch it does
not
> check for /etc/default/sphinxsearch (START=yes), but I think that
>  systemctl enable|disable sphinxsearch
> is a better solution for this.
> 
> It also does not check whether /etc/sphinxsearch/sphinx.conf exists,
> but I'm not sure where this is needed for.
> 
> Maybe this could be helpful for someone else.

Instead of those ExecStartPre=, you can simply use
RuntimeDirectoryPreserve=yes and RuntimeDirectory=sphinxsearch

-- 
Kind regards,
Luca Boccassi


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

Bug#1053668: diffoscope: Consider using `file -i` as fallback for unknown file output

[Chris Lamb]

Version: 251

FC Stegerman wrote:

> I would argue that this is a bug in file(1) as Magdir/communications
> uses a "string" test, which is for binary files.  If this is a text
> file, not a binary format, it should be forcing a text file test by
> using "string/t" instead.
>
> That said, this is likely not the only such bug (I already encountered
> one before [1]), so the suggestion below makes sense to me.

Yes to both things. This was actually implemented and fixed last week,
although I didn't encode the entry in debian/changelog correctly so
this bug wasn't closed… so closing it now in BCC. :)

Thanks to you both.


Best wishes,

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

Bug#1052854: python-vulndb: FTBFS: FileNotFoundError: [Errno 2] No such file or directory: '/<>/.pybuild/cpython3_3.11/build/vulndb/db'

[Gianfranco Costamagna]

Hello,


I haven't seen that many of these. A few, yes, maybe 3?


3 under my personal ddpo, e.g. borgbackup this one and some others.
In any case, I agree with your proposal, borgbackup is already "fixed" in some 
way, and I plan to workaround
vulndb too.

G.



On balance, it still seems like the right change to have made.
There is the risk of silent breakage from missing files, but I haven't
heard of any of those, yet.

I'm coming around to making cleaning .egg-info configurable.
Right now you have to skip pybuild cleaning entirely, which is not
complex. But it's more than the one line instruction to skip egg-info
cleaning. I think configuration makes sense.

Stefano

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


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1054117: python3-pymemcache: Cannot import module. Missing files.

[Patrick Mau]

Package: python3-pymemcache
Version: 4.0.0-3
Severity: important
X-Debbugs-Cc: p...@me.com

Dear Maintainer,

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

   * What led up to the situation?

   Installing the latest version in Debian unstable/sid

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

   A simple import will show the issue. See below.

   * What was the outcome of this action?

$ python3
Python 3.11.6 (main, Oct  8 2023, 05:06:43) [GCC 13.2.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import pymemcache
Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python3/dist-packages/pymemcache/__init__.py", line 3, in 

from pymemcache.client.base import Client  # noqa
^
ModuleNotFoundError: No module named 'pymemcache.client'

   * What outcome did you expect instead?

   I expected the import to succeed, but the "client" module is missing
   from the package. See here:

   https://github.com/pinterest/pymemcache/tree/master/pymemcache

*** End of the template - remove these template lines ***


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

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

Versions of packages python3-pymemcache depends on:
ii  python3  3.11.4-5+b1
ii  python3-six  1.16.0-4

python3-pymemcache recommends no packages.

python3-pymemcache suggests no packages.

Bug#1054116: ITP: puppet-module-puppet -- Puppet module for Puppet itself (client and server)

[Thomas Goirand]

Package: wnpp
Severity: wishlist
Owner: Thomas Goirand 
X-Debbugs-Cc: debian-de...@lists.debian.org

* Package name: puppet-module-puppet
  Version : 18.0.0
  Upstream Contact: Theforeman
* URL : https://github.com/theforeman/puppet-puppet
* License : Apache-2.0
  Programming Lang: Puppet, Ruby
  Description : Puppet module for Puppet itself (client and server)

 Puppet lets you centrally manage every important aspect of your system using a
 cross-platform specification language that manages all the separate elements
 normally aggregated in different files, like users, cron jobs, and hosts,
 along with obviously discrete elements like packages, services, and files.
 .
 This module contains a puppet to setup, configure and maintain puppet itself,
 client and server.

Bug#1051983: RFS: golang-github-katalix-go-l2tp

[Tom Parkin]

Hi pkg-go,

I am seeking a sponsor for the package
golang-github-katalix-go-l2tp[1], which contains tools that are
used by default by the NetworkManager-l2tp[2] plugin.  Currently
nm-l2tp users have to build/install the go-l2tp programs themselves if
they wish to make use of them.

The package has already been through one round of review[3] (many
thanks to everyone who contributed).  As a result since I first posted
the package, I have:

 * Trimmed the description to focus on the specifics of the package(s)
   from an end-user perspective,

 * Added a library package in addition to the program package.  The
   repo name uses the library package naming convention as upstream
   is intended to be primarily used as a library,

 * Relocated the programs from usr/bin to usr/sbin as they require
   root permissions,

 * Reworked the manpages for the programs to live in section 8 of the
   manual (reflecting the program relocation to usr/sbin), and fixed
   up roff formatting issues reported by lintian on sid.

The package builds using gbp-buildpackage on bookworm, and is lintian
clean on bookworm and sid, modulo some complaints about hardening
which I understand are going to be resolved on the tooling side[4].

Further review comments welcome and thank you for your help to date.

Best regards,
Tom

[1]. https://salsa.debian.org/go-team/packages/golang-github-katalix-go-l2tp
[2]. https://github.com/nm-l2tp/NetworkManager-l2tp
[3]. https://lists.debian.org/debian-go/2023/09/msg00022.html
[4]. https://lists.debian.org/debian-go/2023/09/msg00029.html
-- 
Tom Parkin
Katalix Systems Ltd
https://katalix.com
Catalysts for your Embedded Linux software development


signature.asc
Description: PGP signature

Bug#1054081: ITP: librewolf -- community-maintained, privacy and security-focused browser based on firefox

[Kilian Romberg]

Hi Mathias,

On Tue, Oct 17, 2023 at 09:21:04AM +0200, Mathias Behrle wrote:
> While I would like to very much to have Librewolf as a native Debian package
> available, are you aware that Debian isn't running OBS as build service?

Yes I am, please excuse my poor explanation. Have a look at the script
at 
https://codeberg.org/librewolf/debian-obs/src/branch/b118.0.2/scripts/prep-librewolf-dpkg.sh.
This serves as a builder for the relevant files to upload and pass to
dpkg-buildpackage to build (based on the Firefox packaging). Only difference is 
that the LibreWolf team sends these to OBS for building the source binary.

I have tested this script for the latest Firefox version (and they have
too, recently), and it seems to work! This will enable immediate
packaging for each Firefox version uploaded to the Debian repos.

> The most logical for me would be to enlarge "Maintainers of Mozilla-related
> packages ".

Thanks for suggesting that, sounds good!

Cheers,
Kilian


signature.asc
Description: PGP signature

Bug#1054115: broken on NFS

[Anton Ivanov]

Package: man-db
Version: 2.11.2-2
Severity: important

Can the genius who denied man internet access please
come forward and explain how it will now work on NFS-root
systems

[   79.257369] audit: type=1400 audit(1697531933.690:139): apparmor="DENIED" 
operation="sendmsg" profile="/usr/bin/man" pid=3921 comm="man" 
laddr=192.168.3.98 lport=676 faddr=192.168.3.3 fport=2049 family="inet" 
sock_type="stream" protocol=6 requested_mask="send" denied_mask="send"

Genius. Sheer, unadulterated, crystallized and purified.


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

Kernel: Linux 5.10.0-22-amd64 (SMP w/12 CPU threads)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages man-db depends on:
ii  bsdextrautils  2.38.1-5+b1
ii  bsdmainutils   12.1.8
ii  debconf [debconf-2.0]  1.5.82
ii  groff-base 1.22.4-10
ii  libc6  2.36-9+deb12u2
ii  libgdbm6   1.23-3
ii  libpipeline1   1.5.7-1
ii  libseccomp22.5.4-1+b3
ii  zlib1g 1:1.2.13.dfsg-1

man-db recommends no packages.

Versions of packages man-db suggests:
ii  apparmor   3.0.8-3
ii  chromium [www-browser] 116.0.5845.180-1~deb12u1
ii  firefox-esr [www-browser]  102.15.1esr-1~deb12u1
pn  groff  
ii  less   590-2
ii  lynx [www-browser] 2.9.0dev.12-1
ii  w3m [www-browser]  0.5.3+git20230121-2

-- debconf information excluded

Bug#1054114: snac2: The Apache configuration is incorrect

[Richard Levitte]

Package: snac2
Version: 2.41-1
Severity: normal
X-Debbugs-Cc: rich...@levitte.org

Dear Maintainer,

When installing snac2 (apt install snac2), I got the following messages:

apache2_invoke: Enable configuration snac2
apache2_reload: Your configuration is broken. Not reloading Apache 2
apache2_reload: AH00526: Syntax error on line 2 of 
/etc/apache2/conf-enabled/snac2.conf:
apache2_reload: Invalid command 'ProxyPass', perhaps misspelled or defined 
by a module not included in the server configuration

The problem was easily fixed with 'a2enmod proxy', but wouldn't it make
sense if the package did this on its own?

Cheers,
Richard

-- 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.0.0-6-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=sv_SE.utf8, LC_CTYPE=sv_SE.utf8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages snac2 depends on:
ii  adduser   3.137
ii  libc6 2.37-12
ii  libcurl4  8.4.0-2
ii  libssl3   3.0.11-1

Versions of packages snac2 recommends:
ii  apache2 [httpd]  2.4.57-3
ii  ssl-cert 1.1.2

snac2 suggests no packages.

-- 
Richard Levitte rich...@levitte.org
http://richard.levitte.org/

"Life is a tremendous celebration - and I'm invited!"
-- from a friend's blog, translated from Swedish

Bug#1054113: ITP: puppet-module-extlib -- Puppet module for Extlib

[Thomas Goirand]

Package: wnpp
Severity: wishlist
Owner: Thomas Goirand 
X-Debbugs-Cc: debian-de...@lists.debian.org

* Package name: puppet-module-extlib
  Version : 7.0.0
  Upstream Contact: Vox Pupuli
* URL : https://github.com/voxpupuli/puppet-extlib
* License : Apache-2.0
  Programming Lang: Puppet, Ruby
  Description : Puppet module for Extlib

 Puppet lets you centrally manage every important aspect of your system using a
 cross-platform specification language that manages all the separate elements
 normally aggregated in different files, like users, cron jobs, and hosts,
 along with obviously discrete elements like packages, services, and files.
 .
 This module contains extlib: functions and facts that are out of scope for
 stdlib. Some of them are even intrinsically tied to stdlib..

This is a dependency to package puppet-module-puppet (ie: a puppet module
to setup and configure the puppet agent & server).