Bug#1055922: rmatrix: ABI change in Matrix 1.6-2

[Andreas Tille]

Hi Graham,

Am Sun, Nov 19, 2023 at 01:55:04PM -0100 schrieb Graham Inggs:
> On Sat, 18 Nov 2023 at 19:18, Andreas Tille  wrote:
> > We need some means to follow ABI changes.  In Debian we could use
> > something like r-matrix-abi-VERSION.
> 
> Indeed, this is one solution.  As you saw in [1], upstream now provide
> an ABI version and a way to extract it:
> > Matrix will commence ABI versioning in 1.6-2.  The ABI version will be 
> > available
> > in R as Matrix.Version()[["abi"]] and in C as R_MATRIX_ABI_VERSION (from 
> > header
> > Matrix/Matrix.h).  It is numeric_version("1") in Matrix 1.6-2 and 
> > _implicitly_
> > numeric_version("0") in Matrix < 1.6-2.

I'd personally would prefer, if we would implement this ABI versioning
in our packaging in the long term.
 
> However, since rmatrix has over 100 reverse-dependencies, and only a
> very small number of these are broken by the ABI change, we feel this
> may be overkill, but wouldn't dissuade anyone from proposing patches
> to implement this.

This somehow reminds me to bug #1040038 where r-graphics-engine was
implemented in r-base.  I'm willing to help with the implementation of
R_MATRIX_ABI_VERSION but my motivation would be increased if the
authorship of the patches would be mentioned at least in d/changelog
(which was not the case for r-graphics-engine).
 
> Another option is simply to add a versioned dependency on
> r-cran-matrix to the affected packages, e.g.:
> Depends: r-cran-matrix (>= 1.6-2-1)
> ...but this requires a source change and an upload, is error-prone,
> and a binNMU would not be sufficient.
> 
> We liked the change you made to r-cran-tmb [2], as this allows the
> affected packages to be binNMU'd and gain a versioned dependency on
> r-cran-matrix.  Would you please apply this to the other affected
> packages (only r-cran-irlba and r-cran-openmx, if I understand
> correctly)?

Done.
 
> Unfortunately, it seems the two-sided dependency introduced
> subsequently [3], which produces:
> r-cran-matrix (>= 1.6-2-1), r-cran-matrix (<= 1.6-2-199)
> ...is too strict, and r-cran-tmb already needs another rebuild due to
> the upload of rmatrix 1.6-3-1.  Would you please revert that change
> and upload?

I've reverted this but in previous discussion[4] with Paul we agreed
upon the strict version dependency.  I think this is only necessary for
r-cran-tmb (where upstream is enforcing this with a test I'm hesitating
to patch out).  But maybe upstream can work with the freshly implemented
R_MATRIX_ABI_VERSION and thus we can come back to upstream if the
autopkgtest will fire next time (which will happen now after the next
r-cran-matrix update).

Kind regards
   Andreas.
 
> [1] https://stat.ethz.ch/pipermail/r-sig-mac/2023-October/014890.html
> [2] 
> https://salsa.debian.org/r-pkg-team/r-cran-tmb/-/commit/92579f72c2db4d51a45cf317f580d790da158f4f
> [3] 
> https://salsa.debian.org/r-pkg-team/r-cran-tmb/-/commit/0a4d35d10f9c875863fa0238287cee8ab25aecdd

[4] https://lists.debian.org/debian-r/2023/11/msg7.html 

-- 
http://fam-tille.de

Bug#1054372: python3-django-macaddress: incompatible with python3-django in bookworm

[s3v]

Dear Maintainer,

After enabling tests during build (minimal settings.py is needed) and applying 
upstream commit [1][2],
I was able to build your package in a sid chroot environment and all test pass 
as well.

Kind Regards

[1] 
https://github.com/django-macaddress/django-macaddress/pull/41/commits/a722016312a97
[2] https://github.com/django-macaddress/django-macaddress/pull/44diff -Nru --exclude changelog django-macaddress-1.5.0/debian/control django-macaddress-1.5.0/debian/control
--- django-macaddress-1.5.0/debian/control  2022-04-25 01:57:12.0 +
+++ django-macaddress-1.5.0/debian/control  2023-11-20 08:16:34.0 +
@@ -7,6 +7,10 @@
  debhelper-compat (= 12),
  dh-python,
  python3-all,
+ python3-django,
+ python3-netaddr,
+ python3-pytest,
+ python3-pytest-django,
  python3-setuptools,
 Standards-Version: 4.5.0
 Vcs-Git: https://salsa.debian.org/python-team/packages/django-macaddress.git
diff -Nru --exclude changelog django-macaddress-1.5.0/debian/patches/newdjango.patch django-macaddress-1.5.0/debian/patches/newdjango.patch
--- django-macaddress-1.5.0/debian/patches/newdjango.patch  1970-01-01 00:00:00.0 +
+++ django-macaddress-1.5.0/debian/patches/newdjango.patch  2023-11-20 08:16:20.0 +
@@ -0,0 +1,24 @@
+--- /dev/null
 b/macaddress/tests/settings.py
+@@ -0,0 +1,10 @@
++INSTALLED_APPS = [
++'macaddress',
++]
++
++DATABASES = {
++'default': {
++'ENGINE': 'django.db.backends.sqlite3',
++'NAME': 'mydatabase',
++}
++}
+--- a/macaddress/formfields.py
 b/macaddress/formfields.py
+@@ -1,6 +1,6 @@
++from django.core.validators import EMPTY_VALUES
+ from django.forms import Field
+-from django.forms.fields import EMPTY_VALUES
+-from django.utils.translation import ugettext_lazy as _
++from django.utils.translation import gettext_lazy as _
+ #"From Django 1.8: The django.forms.util module has been renamed. Use django.forms.utils instead."
+ try:
+ from django.forms.utils import ValidationError
diff -Nru --exclude changelog django-macaddress-1.5.0/debian/patches/series django-macaddress-1.5.0/debian/patches/series
--- django-macaddress-1.5.0/debian/patches/series   1970-01-01 00:00:00.0 +
+++ django-macaddress-1.5.0/debian/patches/series   2023-11-20 08:14:54.0 +
@@ -0,0 +1 @@
+newdjango.patch
diff -Nru --exclude changelog django-macaddress-1.5.0/debian/rules django-macaddress-1.5.0/debian/rules
--- django-macaddress-1.5.0/debian/rules2022-04-25 01:57:12.0 +
+++ django-macaddress-1.5.0/debian/rules2023-11-20 08:13:26.0 +
@@ -5,8 +5,7 @@
 #export DH_VERBOSE=1
 
 export PYBUILD_NAME=django-macaddress
-
-override_dh_auto_test:
+export DJANGO_SETTINGS_MODULE=macaddress.tests.settings
 
 %:
dh $@  --with python3 --buildsystem=pybuild

Bug#1042676: marked as done (python-public: FTBFS with Sphinx 7.1, docutils 0.20: error: invalid command 'build_sphinx')

[Debian Bug Tracking System]

Your message dated Mon, 20 Nov 2023 09:47:46 +0100
with message-id 
and subject line Re: python-public: FTBFS with Sphinx 7.1, docutils 0.20: 
error: invalid command 'build_sphinx'
has caused the Debian Bug report #1042676,
regarding python-public: FTBFS with Sphinx 7.1, docutils 0.20: error: invalid 
command 'build_sphinx'
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1042676: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042676
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-public
Version: 2.3-4
Severity: important
Tags: ftbfs
User: python-modules-t...@lists.alioth.debian.org
Usertags: sphinx7.1

Hi,

python-public fails to build with Sphinx 7.1 and docutils 0.20, both of which
are currently available in experimental.

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> python3 setup.py build_sphinx
> usage: setup.py [global_opts] cmd1 [cmd1_opts] [cmd2 [cmd2_opts] ...]
>or: setup.py --help [cmd1 cmd2 ...]
>or: setup.py --help-commands
>or: setup.py cmd --help
> 
> error: invalid command 'build_sphinx'
> make[1]: *** [debian/rules:14: override_dh_installdocs] Error 1


The full build log is available from:
http://qa-logs.debian.net/2023/07/30/exp/python-public_2.3-4_unstable_sphinx-exp.log

Please see [1] for Sphinx changelog and [2] for Docutils changelog.

Also see [3] for the list of deprecated/removed APIs in Sphinx and possible
alternatives to them.

Some notable changes in Sphinx 6 and Sphinx 7:

- Sphinx no longer includes jquery.js and underscore.js by default.
  Please use python3-sphinxcontrib.jquery package if you are using a custom
  template and it still needs jquery.

- The setup.py build_sphinx command was removed. Please instead call
  sphinx-build or "python3 -m sphinx" directly.

- For packages using the extlinks extension, the caption should contain
  exactly one "%s" placeholder (if caption is not None).

In case you have questions, please Cc sph...@packages.debian.org on reply.

[1]: https://www.sphinx-doc.org/en/master/changes.html
[2]: 
https://repo.or.cz/docutils.git/blob/refs/tags/docutils-0.20.1:/RELEASE-NOTES.txt
[3]: 
https://www.sphinx-doc.org/en/master/extdev/deprecated.html#dev-deprecated-apis

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=sphinx7.1;users=python-modules-t...@lists.alioth.debian.org
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=sphinx7.1&fusertaguser=python-modules-t...@lists.alioth.debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results

If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
--- End Message ---
--- Begin Message ---
Hi,

this problem is solved since Josenilson has uploaded version 4.0
of the package thus closing the bug.

Kind regards
Andreas.

PS: Josenilson, I've pushed pristine-tar information to the packaging Git.

-- 
http://fam-tille.de--- End Message ---

Processed: Bug#1050451 marked as pending in libperl-languageserver-perl

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1050451 [src:libperl-languageserver-perl] libperl-languageserver-perl: 
autopkgtest failure with Perl 5.38: given is deprecated
Added tag(s) pending.

-- 
1050451: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050451
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1050451: marked as pending in libperl-languageserver-perl

[Damyan Ivanov]

Control: tag -1 pending

Hello,

Bug #1050451 in libperl-languageserver-perl reported by you has been fixed in 
the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/perl-team/modules/packages/libperl-languageserver-perl/-/commit/3c59be99c41e4f397602bdd6ebfce81eb13666c7


patch away given/when/smartmatch usage; deprecated in perl 5.38

Closes: #1050451


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1050451

Bug#1056303: pg_createcluster destroys data directory under certain conditions

[Max Kellermann]

Package: postgresql-common
Version: 248
Severity: critical

When I tried to use "pg_createcluster" to configure my pre-existing
PostgreSQL data directory with a new Debian install, it deleted the
whole cluster with all databases instead.  (This serious data loss
justifies "severity critical" according to
https://www.debian.org/Bugs/Developer#severities)

Steps to reproduce:

 pg_createcluster 15 test
 cp /etc/postgresql/15/test/postgresql.conf /var/lib/postgresql/15/test/
 rm -r /etc/postgresql/15/test
 pg_createcluster 15 test

This creates a new cluster just for the demo, then deletes the
configuration directory, after copying the postgresql.conf to the data
directory.

I expect the second "pg_createcluster" call to find the existing data
directory and configure it; and it tries to do so indeed:

 Configuring already existing cluster (configuration: /etc/postgresql/15/test, 
data: /var/lib/postgresql/15/test, owner: 103:111)

After it finds and moves a "postgresql.conf", it however fails to find
"pg_hba.conf"

 Error: move_conffile: required configuration file 
/var/lib/postgresql/15/test/pg_hba.conf does not exist

This fails the whole operation, and apparently, "pg_createcluster"
tries to roll back by invoking "pg_dropcluster 15 test 2>/dev/null",
destroying all pre-existing data.

If "postgresql.conf" does not exist (or is empty), "pg_dropcluster" is
not invoked.

Bug#1050451: marked as done (libperl-languageserver-perl: autopkgtest failure with Perl 5.38: given is deprecated)

[Debian Bug Tracking System]

Your message dated Mon, 20 Nov 2023 09:04:44 +
with message-id 
and subject line Bug#1050451: fixed in libperl-languageserver-perl 2.6.1-2
has caused the Debian Bug report #1050451,
regarding libperl-languageserver-perl: autopkgtest failure with Perl 5.38: 
given is deprecated
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1050451: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050451
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libperl-languageserver-perl
Version: 2.5.0-1
Severity: important
Tags: trixie sid upstream
User: debian-p...@lists.debian.org
Usertags: perl-5.38-transition autopkgtest
Forwarded: https://github.com/richterger/Perl-LanguageServer/issues/190

This package fails its autopkgtest checks with Perl 5.38 (currently
in experimental.)

  
https://ci.debian.net/data/autopkgtest/unstable/amd64/libp/libperl-languageserver-perl/37098313/log.gz

 61s #   Failed test ' /usr/bin/perl -w -M"Perl::LanguageServer" -e 1 2>&1 
produced no (non-whitelisted) output'
 61s #   at /usr/share/pkg-perl-autopkgtest/runtime-deps.d/use.t line 110.
 61s # Structures begin differing at:
 61s #  $got->[0] = 'given is deprecated at 
/usr/share/perl5/Perl/LanguageServer/Parser.pm line 136.
 61s # '
 61s # $expected->[0] = Does not exist
 61s 
 61s #   Failed test 'env PERL_DL_NONLAZY=1  /usr/bin/perl -w 
-M"Perl::LanguageServer" -e 1 2>&1 produced no (non-whitelisted) output'
 61s #   at /usr/share/pkg-perl-autopkgtest/runtime-deps.d/use.t line 110.
 61s # Structures begin differing at:
 61s #  $got->[0] = 'given is deprecated at 
/usr/share/perl5/Perl/LanguageServer/Parser.pm line 136.
 61s # '
 61s # $expected->[0] = Does not exist
 61s # Looks like you failed 2 tests of 4.

-- 
Niko Tyni   nt...@debian.org
--- End Message ---
--- Begin Message ---
Source: libperl-languageserver-perl
Source-Version: 2.6.1-2
Done: Damyan Ivanov 

We believe that the bug you reported is fixed in the latest version of
libperl-languageserver-perl, which is due to be installed in the Debian FTP 
archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1050...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Damyan Ivanov  (supplier of updated 
libperl-languageserver-perl package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 20 Nov 2023 08:49:46 +
Source: libperl-languageserver-perl
Architecture: source
Version: 2.6.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Perl Group 
Changed-By: Damyan Ivanov 
Closes: 1050451
Changes:
 libperl-languageserver-perl (2.6.1-2) unstable; urgency=medium
 .
   * Team upload
 .
   * patch away given/when/smartmatch usage; deprecated in perl 5.38
 (Closes: #1050451)
Checksums-Sha1: 
 d2f8e78ddc9f9da3f4956d0c1846de58e8e42c7f 2645 
libperl-languageserver-perl_2.6.1-2.dsc
 85178f8d8273acdd2e3f3eb5100ce4e8cd19 6696 
libperl-languageserver-perl_2.6.1-2.debian.tar.xz
Checksums-Sha256: 
 9c5cd8d51942e4ee853ca2d2b281189e4103060fdf3b14c7d7ea9455b1ae7cc8 2645 
libperl-languageserver-perl_2.6.1-2.dsc
 09ba886656921237c901a1454840c7613cb6ea4f39b4fba98d5af4b9dd70b4a3 6696 
libperl-languageserver-perl_2.6.1-2.debian.tar.xz
Files: 
 788104a6c373fe00cc54a79778063d35 2645 perl optional 
libperl-languageserver-perl_2.6.1-2.dsc
 e9b8d5e1350eafa1cfc1805dc913085c 6696 perl optional 
libperl-languageserver-perl_2.6.1-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEErqDETssFbpNjDZ0z276dTZnSoAQFAmVbHd4ACgkQ276dTZnS
oAS5TxAAhkcr2dVyRrswogkKn1dX8KDzl+Sr7SCjlP73Qrv1IXi15cb82y5hCGDt
jqwg3fKH9YiHYgJI33tiNWGoOwvlvZr160oYCaAMEFU/DHG2LgxJNR2JcJh4f7dQ
F/nYY5Ce6TuI83v9oAon18pbZeOqi1DRDN5/pvcgSugMD5i4fiLKxjU3590Knw4a
8HcOnf4bF6P+x/LW2T324/ArIVIX1Qb6HNV5TCwF/y4phDiMLIOTt2hTg13QEvI3
Af+wGmhEHwqA2Y8cYlKubnmZd5RQnGmodsee+QIx8rBZfOcwbMPs2ZvKnqXAeVUa
aeg2iCNvEldqbo7IF9y5WUgw4Rh5grWE8tGlwFuVC/46B9A86PLYmGP+xdA77fa7
osWa+tBKvcHPTIAWILkktdujeXMP7iPxdk+3arYiIyb/c/YXEVK1dY9VKIBEN7it
+WVAleOygJtv/zO+JgCJq99EQHM7FOs4hMic4ZfvevxJEuRd0OO9nECPvoqDW4An
FERg/K8X+3ODwwOY/K+UDSdTcMyZnZKdciBEx6zlYt1o4uXb/9heKD0vNmeG/Hku
axcsJFipnZ0nsgNgnws8mNL40p+zl

Bug#1056186: marked as done (texlive-binaries: zlib library mismatch)

[Debian Bug Tracking System]

Your message dated Mon, 20 Nov 2023 09:06:37 +
with message-id 
and subject line Bug#1056183: fixed in texlive-bin 2023.20230311.66589-8
has caused the Debian Bug report #1056183,
regarding texlive-binaries: zlib library mismatch
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1056183: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056183
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: texlive-binaries
Version: 2023.20230311.66589-7
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: calcu...@rezozer.net

Hi, the issue appeared to me within a Sid schroot environment 
at postinstallation time of tex-common.
I traced it back to texlive-binaries by looking the logfile at
the fmutils stage. The issue seems to originate from the recent migration
from zlib 1.2.13 to zlib 1.3. For short, the following command-line

  $ luatex -ini -jobname=luatex -progname=luatex luatex.ini

gives

  PANIC: unprotected error in call to Lua API (zlib library version does not 
match - header: 1.2.13, library: 1.3)
  aborted

Best wishes,
Jerome


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

Kernel: Linux 6.1.0-0.deb11.6-amd64 (SMP w/12 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: unable to detect

Versions of packages texlive-binaries depends on:
ii  libc6   2.37-12
ii  libcairo2   1.18.0-1
ii  libfontconfig1  2.14.2-6
ii  libfreetype62.13.2+dfsg-1
ii  libgcc-s1   13.2.0-6
ii  libgraphite2-3  1.3.14-1
ii  libharfbuzz0b   8.0.1-1
ii  libicu7272.1-4
ii  libkpathsea62023.20230311.66589-7
ii  libmpfr64.2.1-1
ii  libpaper1   1.1.29
ii  libpixman-1-0   0.42.2-1
ii  libpng16-16 1.6.40-2
ii  libpotrace0 1.16-2
ii  libptexenc1 2023.20230311.66589-7
ii  libstdc++6  13.2.0-6
ii  libsynctex2 2023.20230311.66589-7
ii  libteckit0  2.5.11+ds1-1+b1
ii  libtexlua53-5   2023.20230311.66589-7
ii  libx11-62:1.8.7-1
ii  libxaw7 2:1.0.14-1
ii  libxi6  2:1.8-1+b1
ii  libxmu6 2:1.1.3-3
ii  libxpm4 1:3.5.17-1
ii  libxt6  1:1.2.1-1.1
ii  libzzip-0-130.13.72+dfsg.1-1.1
ii  perl5.36.0-9
ii  t1utils 1.41-4
ih  tex-common  6.18
ii  zlib1g  1:1.3.dfsg-2

Versions of packages texlive-binaries recommends:
pn  dvisvgm   
ii  texlive-base  2023.20231007-1

Versions of packages texlive-binaries suggests:
pn  hintview   
pn  texlive-binaries-sse2  

Versions of packages tex-common depends on:
ii  ucf  3.0043+nmu1

Versions of packages tex-common suggests:
ii  debhelper  13.11.8

Versions of packages texlive-binaries is related to:
ih  tex-common6.18
ii  texlive-base  2023.20231007-1

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: texlive-bin
Source-Version: 2023.20230311.66589-8
Done: Hilmar Preusse 

We believe that the bug you reported is fixed in the latest version of
texlive-bin, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1056...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Hilmar Preusse  (supplier of updated texlive-bin package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 20 Nov 2023 08:45:38 +
Source: texlive-bin
Architecture: source
Version: 2023.20230311.66589-8
Distribution: unstable
Urgency: high
Maintainer: Debian TeX Task Force 
Changed-By: Hilmar Preusse 
Closes: 1056183
Changes:
 texlive-bin (2023.20230311.66589-8) unstable; urgency=high
 .
   * Untighten version check of zlib in texk/web2c/luatexdir/luazlib/lzlib.c
 again to make binaries linked with 1.2.x runnable with 1.3.x
 (Closes: #1056183).
Checksums-Sha1:
 3b4c80709c1c62d4b7e1c2c4481203fa654854b5 3493 
texlive-bin_2023.20230311.66589-8.dsc
 8f76ee3ed5abe543ad13dec86a6426efb2993e63 151592 
texlive-bin_2023.20230311.66589-8.debian.tar.xz
 daa68e9d8f35fefc3a3195cf51532b88108b9149 6024 
texlive-bin_2023.20230311.66589-8_source.b

Bug#1056183: marked as done (texlive-luatex: lualatex exits immediately due to new zlib)

[Debian Bug Tracking System]

Your message dated Mon, 20 Nov 2023 09:06:37 +
with message-id 
and subject line Bug#1056183: fixed in texlive-bin 2023.20230311.66589-8
has caused the Debian Bug report #1056183,
regarding texlive-luatex: lualatex exits immediately due to new zlib
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1056183: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056183
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: texlive-luatex
Version: 2023.20231007-1
Severity: important
X-Debbugs-Cc: dankamong...@gmail.com

Dear Maintainer,

I recently updated zlib1g:amd64 (1:1.2.13.dfsg-3, 1:1.3.dfsg-2) in unstable.

lualatex immediately stopped working, with the error:

[schwarzgerat](0) $ lualatex
PANIC: unprotected error in call to Lua API (zlib library version does not
match - header: 1.2.13, library: 1.3)
Aborted (core dumped)
[schwarzgerat](134) $

Should just need a rebuild, but perhaps this (unnecessary?) check ought be
removed? Isn't this what SOVERSIONs are for?


-- Package-specific info:
IMPORTANT INFORMATION: We will only consider bug reports concerning
the packaging of TeX Live as relevant. If you have problems with
combination of packages in a LaTeX document, please consult your
local TeX User Group, the comp.text.tex user group, the author of
the original .sty file, or any other help resource. 

In particular, bugs that are related to up-upstream, i.e., neither
Debian nor TeX Live (upstream), but the original package authors,
will be closed immediately.

   *** The Debian TeX Team is *not* a LaTeX Help Desk ***

If you report an error when running one of the TeX-related binaries 
(latex, pdftex, metafont,...), or if the bug is related to bad or wrong
output, please include a MINIMAL example input file that produces the
error in your report.

Please run your example with
(pdf)latex -recorder ...
(or any other program that supports -recorder) and send us the generated
file with the extension .fls, it lists all the files loaded during
the run and can easily explain problems induced by outdated files in
your home directory.

Don't forget to also include minimal examples of other files that are 
needed, e.g. bibtex databases. Often it also helps
to include the logfile. Please, never send included pictures!

If your example file isn't short or produces more than one page of
output (except when multiple pages are needed to show the problem),
you can probably minimize it further. Instructions on how to do that
can be found at

http://www.minimalbeispiel.de/mini-en.html (english)

or 

http://www.minimalbeispiel.de/mini.html (german)

##
minimal input file


##
other files

##
 List of ls-R files

-rw-r--r-- 1 root root 2496 2023-11-10 04:56 /var/lib/texmf/ls-R
lrwxrwxrwx 1 root root 29 2022-10-12 17:25 /usr/share/texmf/ls-R -> 
/var/lib/texmf/ls-R-TEXMFMAIN
lrwxrwxrwx 1 root root 31 2023-10-08 16:00 /usr/share/texlive/texmf-dist/ls-R 
-> /var/lib/texmf/ls-R-TEXLIVEDIST
lrwxrwxrwx 1 root root 31 2023-10-08 16:00 /usr/share/texlive/texmf-dist/ls-R 
-> /var/lib/texmf/ls-R-TEXLIVEDIST
##
 Config files
-rw-r--r-- 1 root root 475 2023-08-28 14:30 /etc/texmf/web2c/texmf.cnf
lrwxrwxrwx 1 root root 33 2023-10-08 16:00 /usr/share/texmf/web2c/fmtutil.cnf 
-> /var/lib/texmf/fmtutil.cnf-DEBIAN
lrwxrwxrwx 1 root root 32 2023-10-08 16:00 /usr/share/texmf/web2c/updmap.cfg -> 
/var/lib/texmf/updmap.cfg-DEBIAN
-rw-r--r-- 1 root root 5289 2023-11-10 04:54 
/var/lib/texmf/tex/generic/config/language.dat
##
 Files in /etc/texmf/web2c/
total 8
-rw-r--r-- 1 root root 283 2016-02-22 09:54 mktex.cnf
-rw-r--r-- 1 root root 475 2023-08-28 14:30 texmf.cnf
##
 md5sums of texmf.d
ca40c66f144b4bafc3e59a2dd32ecb9c  /etc/texmf/texmf.d/00debian.cnf

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

Kernel: Linux 6.5.9nlb2 (SMP w/64 CPU threads)
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)

Versions of packages texlive-luatex depends on:
ii  libjs-jquery  3.6.1+dfsg+~3.5.14-1
ii  lmodern   2.005-1
ii  tex-common6.18
ii  texlive-base  2023.20231007-1

Bug#1056189: marked as done (luahbtex: PANIC: unprotected error in call to Lua API (zlib library version does not match - header: 1.2.13, library: 1.3))

[Debian Bug Tracking System]

Your message dated Mon, 20 Nov 2023 09:06:37 +
with message-id 
and subject line Bug#1056183: fixed in texlive-bin 2023.20230311.66589-8
has caused the Debian Bug report #1056183,
regarding luahbtex: PANIC: unprotected error in call to Lua API (zlib library 
version does not match - header: 1.2.13, library: 1.3)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1056183: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056183
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: texlive-binaries
Version: 2023.20230311.66589-7
Severity: important
Affects: tex-common

Hello,

trying to install texlive-latex-base+texlive-plain-generic to fullfill a
build dependency resulted in:
8X--
Setting up tex-common (6.18) ...
Running mktexlsr. This may take some time... done.
Running updmap-sys. This may take some time... done.
Running mktexlsr /var/lib/texmf ... done.
Building format(s) --all.
This may take some time...
fmtutil failed. Output has been stored in
/tmp/fmtutil.VGYt4Mud
Please include this file if you report a bug.

dpkg: error processing package tex-common (--configure):
 installed tex-common package post-installation script subprocess returned 
error exit status 1
[...]
Errors were encountered while processing:
 tex-common
E: Sub-process /usr/bin/dpkg returned an error code (1)
8X--

/tmp/fmtutil.VGYt4Mud (attached) shows:
...
fmtutil [INFO]: --- remaking luahbtex with luahbtex
fmtutil: running `luahbtex -ini   -jobname=luahbtex -progname=luahbtex 
luatex.ini' ...
PANIC: unprotected error in call to Lua API (zlib library version does not 
match - header: 1.2.13, library: 1.3)
Aborted
...

I am submitting against texlive-binaries since it contains the failing
binary.

cu Andreas

##
minimal input file


##
other files

##
 List of ls-R files

lrwxrwxrwx 1 root root 31 Oct  8 20:00 /usr/share/texlive/texmf-dist/ls-R -> 
/var/lib/texmf/ls-R-TEXLIVEDIST
##
 Config files
-rw-r--r-- 1 root root 475 Nov 18 15:02 /etc/texmf/web2c/texmf.cnf
lrwxrwxrwx 1 root root 33 Oct  8 20:00 /usr/share/texmf/web2c/fmtutil.cnf -> 
/var/lib/texmf/fmtutil.cnf-DEBIAN
lrwxrwxrwx 1 root root 32 Oct  8 20:00 /usr/share/texmf/web2c/updmap.cfg -> 
/var/lib/texmf/updmap.cfg-DEBIAN
-rw-r--r-- 1 root root 2942 Nov 18 15:02 
/var/lib/texmf/tex/generic/config/language.dat
##
 Files in /etc/texmf/web2c/
total 8
-rw-r--r-- 1 root root 283 Apr  1  2019 mktex.cnf
-rw-r--r-- 1 root root 475 Nov 18 15:02 texmf.cnf
##
 md5sums of texmf.d
ca40c66f144b4bafc3e59a2dd32ecb9c  /etc/texmf/texmf.d/00debian.cnf

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

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

Versions of packages texlive-binaries depends on:
ii  libc6   2.37-12
ii  libcairo2   1.18.0-1
ii  libfontconfig1  2.14.2-6
ii  libfreetype62.13.2+dfsg-1
ii  libgcc-s1   13.2.0-6
ii  libgraphite2-3  1.3.14-1
ii  libharfbuzz0b   8.0.1-1
ii  libicu7272.1-4
ii  libkpathsea62023.20230311.66589-7
ii  libmpfr64.2.1-1
ii  libpaper1   1.1.29
ii  libpixman-1-0   0.42.2-1
ii  libpng16-16 1.6.40-2
ii  libpotrace0 1.16-2
ii  libptexenc1 2023.20230311.66589-7
ii  libstdc++6  13.2.0-6
ii  libsynctex2 2023.20230311.66589-7
ii  libteckit0  2.5.11+ds1-1+b1
ii  libtexlua53-5   2023.20230311.66589-7
ii  libx11-62:1.8.7-1
ii  libxaw7 2:1.0.14-1
ii  libxi6  2:1.8-1+b1
ii  libxmu6 2:1.1.3-3
ii  libxpm4 1:3.5.17-1
ii  libxt6  1:1.2.1-1.1
ii  libzzip-0-130.13.72+dfsg.1-1.1
ii  perl5.36.0-9
ii  t1utils 1.41-4
ih  tex-common  6.18
ii  zlib1g  1:1.3.dfsg-2

Versions of packages texlive-binaries recommends:
pn  dvisvgm   
ii  texlive-base  2023.20231007-1

Versions of packages texlive-binaries suggests:
pn  hintview   
pn  texlive-binaries-sse2  

Versions of packages tex-common depends on:
ii  ucf  3.0043+nmu1

Versions of packages tex-common suggests:
ii  debhelper  13.11.8

Versions of packages texlive-binaries is related to:
ih  tex-common6.18
ii  texlive-base  2023.20231007-1

-- no d

Bug#1056210: marked as done (luatex panics with zlib 1.3)

[Debian Bug Tracking System]

Your message dated Mon, 20 Nov 2023 09:06:37 +
with message-id 
and subject line Bug#1056183: fixed in texlive-bin 2023.20230311.66589-8
has caused the Debian Bug report #1056183,
regarding luatex panics with zlib 1.3
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1056183: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056183
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: texlive-binaries
Version: 2023.20230311.66589-7

The luatex binary shipped with texlive is not compatible with zlib 1.3 
(zlib1g 1:1.3.dfsg-2 on Debian Sid).


$ luatex
PANIC: unprotected error in call to Lua API (zlib library version does 
not match - header: 1.2.13, library: 1.3)

Aborted
$

This bug has also been reported on the Arch Linux forum:

https://bugs.archlinux.org/task/79470

I am using Debian GNU/Linux trixie/sid (up to date) with the Linux 
6.5.0-4-amd64 kernel.


Regards,
François Rozet.
--- End Message ---
--- Begin Message ---
Source: texlive-bin
Source-Version: 2023.20230311.66589-8
Done: Hilmar Preusse 

We believe that the bug you reported is fixed in the latest version of
texlive-bin, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1056...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Hilmar Preusse  (supplier of updated texlive-bin package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 20 Nov 2023 08:45:38 +
Source: texlive-bin
Architecture: source
Version: 2023.20230311.66589-8
Distribution: unstable
Urgency: high
Maintainer: Debian TeX Task Force 
Changed-By: Hilmar Preusse 
Closes: 1056183
Changes:
 texlive-bin (2023.20230311.66589-8) unstable; urgency=high
 .
   * Untighten version check of zlib in texk/web2c/luatexdir/luazlib/lzlib.c
 again to make binaries linked with 1.2.x runnable with 1.3.x
 (Closes: #1056183).
Checksums-Sha1:
 3b4c80709c1c62d4b7e1c2c4481203fa654854b5 3493 
texlive-bin_2023.20230311.66589-8.dsc
 8f76ee3ed5abe543ad13dec86a6426efb2993e63 151592 
texlive-bin_2023.20230311.66589-8.debian.tar.xz
 daa68e9d8f35fefc3a3195cf51532b88108b9149 6024 
texlive-bin_2023.20230311.66589-8_source.buildinfo
Checksums-Sha256:
 23fa93bd8f2611d622ec80bb7f7a6df7d6e7797b05aa1b492b0caeee5c4a33e0 3493 
texlive-bin_2023.20230311.66589-8.dsc
 f188e66c81f9abcefd67fe4f72c1c39253ddf5180c522aa9de0848676dfca58b 151592 
texlive-bin_2023.20230311.66589-8.debian.tar.xz
 61b7e63177931d80e092575005f447b5f466b37fee3e6c8848a59b2c42d9 6024 
texlive-bin_2023.20230311.66589-8_source.buildinfo
Files:
 d922a083b805fe6277586d8ccd4e571f 3493 tex optional 
texlive-bin_2023.20230311.66589-8.dsc
 cee11863954d28e2925b6dabd9076005 151592 tex optional 
texlive-bin_2023.20230311.66589-8.debian.tar.xz
 9b5e19187e00d140e9b30f65d7876633 6024 tex optional 
texlive-bin_2023.20230311.66589-8_source.buildinfo

-BEGIN PGP SIGNATURE-

iQKTBAEBCgB9FiEEaXGmC/nkbIhxf16kxiZYRqvgLIsFAmVbHUJfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDY5
NzFBNjBCRjlFNDZDODg3MTdGNUVBNEM2MjY1ODQ2QUJFMDJDOEIACgkQxiZYRqvg
LIufrRAAtIa8Mc0Gm6iSPqH45tY9If6s89YDqk8gi88V8xcc5mS9maX1pOEX2ZRC
qYv3dR+Dk8woVxbAE6a/UVu/5ktp/TX3lWwSWaPUS/NenyGnf4MG9RXufTDE4+Pr
UHb/bD3M4tMTq1f4CrmGQmy5aQEmlHuj7V6/jJAbPskx0/PFb2TQgJwIw0Benyqe
IRNL5QwvqykJLUTBv3pgE66UnyU5Vja/pVIJ2ZSndC9N4FHqHNkhA7uDTmdOY34s
gm2OUQc7Kl5uzcNKfmYR+RZ9ysuJdaqOF8nl0uAVSnxPu0b0acddyC2yic4CP6MQ
/Eq9uD5YW2qAZUnuZPDVRGP5riIz87AX6G9df+l9IcN386nY+j9/1DE1zVTJ7cKD
kAnNeN7fqMxM040VaETf1jFQDnPnE17TAnt+gGvBFFBxZrzL+eUeO+R/Lc+Da5vP
IGwRB1+5EeuUojwIJhKfDWW42yEMyS7tjgsegnf0UcE7RtbiJchowYbZtYc4CrGG
hbCBrX4Lhyvf7kF7nR+zrhZXUXlE1eoGLdU105ASF46x3i5KkkJAkmbdyNUdcW1F
34nhVsicnG//ehQzrrVCR6ynSbjhVBPsd9POaAO1Bl6G2hhQqTYxnmyvGUwH00CZ
5XS52S2NgsWNZi2OzMNbWsVMtYX4S16UmEdXVdQf2U49rx/H6Jg=
=seLE
-END PGP SIGNATURE End Message ---

Bug#1013285: marked as done (needrestart: Failed to check for processor microcode upgrades.)

[Debian Bug Tracking System]

Your message dated Mon, 20 Nov 2023 09:19:05 +
with message-id 
and subject line Bug#1013285: fixed in needrestart 3.6-6
has caused the Debian Bug report #1013285,
regarding needrestart: Failed to check for processor microcode upgrades.
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1013285: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013285
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: needrestart
Version: 3.6-1
Severity: normal

`sudo needrestart -w` always prints "Failed to check for processor
microcode upgrades." on my AMD Ryzen 9 3900X 12-Core Processor.

I also don't have 'cpuid' in /dev/cpu/##/, but fixing that doesn't help.

  $ ls -l /dev/cpu/0/
  total 0
  crw---. 1 root root 202, 0 Jun 20 02:29 msr
  $ lsmod | grep -i cpuid
  $ sudo modprobe cpuid
  [sudo] password for nicholas:
  $ lsmod | grep -i cpuid
  cpuid  16384  0
  $ ls -l /dev/cpu/0/
  total 0
  crw---. 1 root root 203, 0 Jun 20 13:48 cpuid
  crw---. 1 root root 202, 0 Jun 20 02:29 msr
  $ sudo /usr/sbin/needrestart -w
  Scanning processor microcode...

  Failed to check for processor microcode upgrades.

The first core's worth of cpuinfo looks like this:

  processor   : 0
  vendor_id   : AuthenticAMD
  cpu family  : 23
  model   : 113
  model name  : AMD Ryzen 9 3900X 12-Core Processor
  stepping: 0
  microcode   : 0x8701021
  cpu MHz : 2200.000
  cache size  : 512 KB
  physical id : 0
  siblings: 24
  core id : 0
  cpu cores   : 12
  apicid  : 0
  initial apicid  : 0
  fpu : yes
  fpu_exception   : yes
  cpuid level : 16
  wp  : yes
  flags   : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr
pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext
fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_good nopl nonstop_tsc
cpuid extd_apicid aperfmperf rapl pni pclmulqdq monitor ssse3 fma cx16
sse4_1 sse4_2 x2apic movbe popcnt aes xsave avx f16c rdrand lahf_lm
cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch
osvw ibs skinit wdt tce topoext perfctr_core perfctr_nb bpext
perfctr_llc mwaitx cpb cat_l3 cdp_l3 hw_pstate ssbd mba ibpb stibp
vmmcall fsgsbase bmi1 avx2 smep bmi2 cqm rdt_a rdseed adx smap
clflushopt clwb sha_ni xsaveopt xsavec xgetbv1 xsaves cqm_llc
cqm_occup_llc cqm_mbm_total cqm_mbm_local clzero irperf xsaveerptr
rdpru wbnoinvd arat npt lbrv svm_lock nrip_save tsc_scale vmcb_clean
flushbyasid decodeassists pausefilter pfthreshold avic v_vmsave_vmload
vgif v_spec_ctrl umip rdpid overflow_recov succor smca sev sev_es
  bugs: sysret_ss_attrs spectre_v1 spectre_v2 spec_store_bypass
  bogomips: 7586.41
  TLB size: 3072 4K pages
  clflush size: 64
  cache_alignment : 64
  address sizes   : 43 bits physical, 48 bits virtual
  power management: ts ttp tm hwpstate cpb eff_freq_ro [13] [14]

The log from needrestart -w -v shows a failure "Use of uninitialized
value $processor in concatenation (.) or string at
/usr/share/perl5/NeedRestart/uCode.pm line 61.", but I think that's
only an error in a logging statement after it's already failed:

  $ sudo /usr/sbin/needrestart -w -v
  [main] eval /etc/needrestart/needrestart.conf
  [main] needrestart v3.6
  [main] running in root mode
  [Core] Using UI 'NeedRestart::UI::stdio'...
  [main] systemd detected
  [ucode] using NeedRestart::uCode::AMD
  [ucode] using NeedRestart::uCode::Intel
  [uCode/AMD] #0 Failed to open /dev/cpu/0/cpuid (Missed `modprobe
cpuid`?): No such file or directory
  [uCode/AMD] #0 cpuid 0x00870f10  (/proc/cpuinfo)
  [uCode/AMD] #0 running ucode 0x08701021
  [uCode/AMD] cpuid 0x00100f80: found processor id 0x1080
  [uCode/AMD] cpuid 0x00100f81: found processor id 0x1081
  [uCode/AMD] cpuid 0x00100f62: found processor id 0x1062
  [uCode/AMD] cpuid 0x00100f23: found processor id 0x1022
  [uCode/AMD] cpuid 0x00100f43: found processor id 0x1043
  [uCode/AMD] cpuid 0x00100f91: found processor id 0x1081
  [uCode/AMD] cpuid 0x00100f2a: found processor id 0x1020
  [uCode/AMD] cpuid 0x00100f63: found processor id 0x1043
  [uCode/AMD] cpuid 0x00100f42: found processor id 0x1041
  [uCode/AMD] cpuid 0x00300f10: found processor id 0x3010
  [uCode/AMD] cpuid 0x00200f31: found processor id 0x2031
  [uCode/AMD] cpuid 0x00100f52: found processor id 0x1041
  [uCode/AMD] cpuid 0x00100fa0: found processor id 0x10a0
  [uCode/AMD] cpuid 0x00100f53: found processor id 0x1043
  [uCode/AMD] cpuid 0x

Bug#1051243: This affects the build of the pspp package

[Friedrich Beckmann]

Hi all,

i noticed a failure in our CI pipeline for pspp probably due to this bug. The 
problem occurs when I try to install "apt install texlive-plain-generic“. The 
install fails with


….
Processing triggers for tex-common (6.18) …
locale: Cannot set LC_CTYPE to default locale: No such file or directory
locale: Cannot set LC_MESSAGES to default locale: No such file or directory
locale: Cannot set LC_ALL to default locale: No such file or directory
Running updmap-sys. This may take some time... done.
Running mktexlsr /var/lib/texmf ... done.
Building format(s) --all.
This may take some time... 
fmtutil failed. Output has been stored in
/tmp/fmtutil.S3jngCrK
Please include this file if you report a bug.

dpkg: error processing package tex-common (--configure):
 installed tex-common package post-installation script subprocess returned 
error exit status 1
Errors were encountered while processing:
 tex-common
E: Sub-process /usr/bin/dpkg returned an error code (1)
….


In /tmp/fmtutil.S3jngCrk the following error messages are shown:


 /tmp/fmtutil.S3jngCrk 
...
No pages of output.
Transcript written on latex.log.
fmtutil [INFO]: log file copied to: /var/lib/texmf/web2c/pdftex/latex.log
fmtutil [INFO]: /var/lib/texmf/web2c/pdftex/latex.fmt installed.
fmtutil [ERROR]: running `luatex -ini   -jobname=luatex -progname=luatex 
luatex.ini 

Processed: Re: Bug#1056304: lualatex needs to be rebuilt against zlib 1.3

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 texlive-binaries
Bug #1056304 [texlive-latex-base] lualatex needs to be rebuilt against zlib 1.3
Bug reassigned from package 'texlive-latex-base' to 'texlive-binaries'.
No longer marked as found in versions texlive-base/2023.20231007-1.
Ignoring request to alter fixed versions of bug #1056304 to the same values 
previously set
> block -1 by 1056204
Bug #1056304 [texlive-binaries] lualatex needs to be rebuilt against zlib 1.3
1056304 was not blocked by any bugs.
1056304 was not blocking any bugs.
Added blocking bug(s) of 1056304: 1056204
> severity -1 grave
Bug #1056304 [texlive-binaries] lualatex needs to be rebuilt against zlib 1.3
Severity set to 'grave' from 'important'
> forcemerge -1 1056183
Bug #1056304 [texlive-binaries] lualatex needs to be rebuilt against zlib 1.3
Bug #1056304 [texlive-binaries] lualatex needs to be rebuilt against zlib 1.3
Marked as fixed in versions texlive-bin/2023.20230311.66589-8.
Marked as found in versions texlive-bin/2023.20230311.66589-7.
Bug #1056183 {Done: Hilmar Preusse } [texlive-binaries] 
texlive-luatex: lualatex exits immediately due to new zlib
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions texlive-bin/2023.20230311.66589-8.
No longer marked as fixed in versions texlive-bin/2023.20230311.66589-8.
No longer marked as fixed in versions texlive-bin/2023.20230311.66589-8.
No longer marked as fixed in versions texlive-bin/2023.20230311.66589-8.
Removed indication that 1056183 affects tex-common
Removed indication that 1056186 affects tex-common
Removed indication that 1056189 affects tex-common
Removed indication that 1056210 affects tex-common
Bug #1056210 [texlive-binaries] luatex panics with zlib 1.3
Marked as fixed in versions texlive-bin/2023.20230311.66589-8.
Marked as fixed in versions texlive-bin/2023.20230311.66589-8.
Marked as fixed in versions texlive-bin/2023.20230311.66589-8.
Marked as fixed in versions texlive-bin/2023.20230311.66589-8.
Bug #1056186 [texlive-binaries] texlive-binaries: zlib library mismatch
Bug #1056189 [texlive-binaries] luahbtex: PANIC: unprotected error in call to 
Lua API (zlib library version does not match - header: 1.2.13, library: 1.3)
Merged 1056183 1056186 1056189 1056210 1056304

-- 
1056183: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056183
1056186: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056186
1056189: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056189
1056210: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056210
1056304: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056304
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1056298: riseup-vpn dns configuration don't work with systemd-resolved

[Nilesh Patra]

Control: severity -1 normal
Control: tags -1 moreinfo

On Mon, 20 Nov 2023 12:36:51 +0530 Pirate Praveen  wrote:
> It misses a dependency on openvpn-systemd-resolved and on boomworm it 
> was working after installing it.

I do not have this installed however riseup-vpn works for me without any
issues. Others who have tested this package on bookworm in the past also
did not have any such issues.

I tried with systemd-resolved installed without openvpn-systemd-resolved
install - no problems observed.

> But on mobian trixie, which has 
> systemd-resolved installed by default (through mobian-base), dns 
> resolution fails when riseup vpn is connected.

I do not have a device to try out mobian. I tried it on debian
trixie/testing with openvpn-system-resolved and I do not see any such
issue.

> ;; communications error to 127.0.0.53#53: timed out
> ;; communications error to 127.0.0.53#53: timed out
> ;; no servers could be reached

OTOH, this log has very superficial info and is not helpful into
debugging if there's even anything wrong with riseup-vpn.

This maybe a setup/configuration issue for your system. I did find a
similar issue on the systemd repository itself[1] and the fix was to add
in a "DNS=" entry in resolved.conf. Can you try this and report back?

Could you also check this on a different network connection?

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

Best,
Nilesh


signature.asc
Description: PGP signature

Processed: Re: riseup-vpn dns configuration don't work with systemd-resolved

[Debian Bug Tracking System]

Processing control commands:

> severity -1 normal
Bug #1056298 [riseup-vpn] riseup-vpn dns configuration don't work with 
systemd-resolved
Severity set to 'normal' from 'grave'
> tags -1 moreinfo
Bug #1056298 [riseup-vpn] riseup-vpn dns configuration don't work with 
systemd-resolved
Added tag(s) moreinfo.

-- 
1056298: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056298
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1051243: PANIC: unprotected error in call to Lua API (zlib library version does not match - header: 1.2.13, library: 1.3)

[Friedrich Beckmann]

The previous error messages showed that the locale was not configured. I 
configured the locale
but the problem persists but now with an additional PANIC:

 /tmp/fmtutil.kYG8CZ8c

No pages of output.
Transcript written on pdfetex.log.
fmtutil [INFO]: log file copied to: /var/lib/texmf/web2c/pdftex/pdfetex.log
fmtutil [INFO]: /var/lib/texmf/web2c/pdftex/pdfetex.fmt installed.
fmtutil [INFO]: --- remaking dvilualatex with luatex
fmtutil: running `luatex -ini   -jobname=dvilualatex -progname=dvilualatex 
dvilualatex.ini' ...
PANIC: unprotected error in call to Lua API (zlib library version does not 
match - header: 1.2.13, library: 1.3)
Aborted
fmtutil [ERROR]: running `luatex -ini   -jobname=luatex -progname=luatex 
luatex.ini 

Bug#1042593: marked as done (flufl.lock: FTBFS with Sphinx 7.1, docutils 0.20: error: invalid command 'build_sphinx')

[Debian Bug Tracking System]

Your message dated Mon, 20 Nov 2023 10:34:04 +
with message-id 
and subject line Bug#1042593: fixed in flufl.lock 5.0.1-5
has caused the Debian Bug report #1042593,
regarding flufl.lock: FTBFS with Sphinx 7.1, docutils 0.20: error: invalid 
command 'build_sphinx'
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1042593: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042593
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: flufl.lock
Version: 5.0.1-4
Severity: important
Tags: ftbfs
User: python-modules-t...@lists.alioth.debian.org
Usertags: sphinx7.1

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_build
> I: pybuild base:240: /usr/bin/python3 setup.py build 
> /usr/lib/python3/dist-packages/setuptools/dist.py:945: 
> SetuptoolsDeprecationWarning: The namespace_packages parameter is deprecated.
> !!
> 
> 
> 
> Please replace its usage with implicit namespaces (PEP 420).
> 
> See 
> https://setuptools.pypa.io/en/latest/references/keywords.html#keyword-namespace-packages
>  for details.
> 
> 
> 
> !!
>   ep.load()(self, ep.name, value)
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.11_flufl.lock/build/tests
> copying tests/__init__.py -> 
> /<>/.pybuild/cpython3_3.11_flufl.lock/build/tests
> copying tests/test_api.py -> 
> /<>/.pybuild/cpython3_3.11_flufl.lock/build/tests
> copying tests/test_lock.py -> 
> /<>/.pybuild/cpython3_3.11_flufl.lock/build/tests
> creating /<>/.pybuild/cpython3_3.11_flufl.lock/build/docs
> copying docs/conf.py -> 
> /<>/.pybuild/cpython3_3.11_flufl.lock/build/docs
> copying docs/__init__.py -> 
> /<>/.pybuild/cpython3_3.11_flufl.lock/build/docs
> creating /<>/.pybuild/cpython3_3.11_flufl.lock/build/flufl
> creating /<>/.pybuild/cpython3_3.11_flufl.lock/build/flufl/lock
> copying flufl/lock/__init__.py -> 
> /<>/.pybuild/cpython3_3.11_flufl.lock/build/flufl/lock
> copying flufl/lock/_lockfile.py -> 
> /<>/.pybuild/cpython3_3.11_flufl.lock/build/flufl/lock
> running egg_info
> writing flufl.lock.egg-info/PKG-INFO
> writing dependency_links to flufl.lock.egg-info/dependency_links.txt
> writing namespace_packages to flufl.lock.egg-info/namespace_packages.txt
> writing requirements to flufl.lock.egg-info/requires.txt
> writing top-level names to flufl.lock.egg-info/top_level.txt
> reading manifest file 'flufl.lock.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> warning: no files found matching '*.po' anywhere in distribution
> warning: no files found matching '*.mo' anywhere in distribution
> warning: no previously-included files found matching '.gitignore'
> no previously-included directories found matching 'build'
> no previously-included directories found matching '.tox'
> no previously-included directories found matching 'dist'
> adding license file 'LICENSE'
> writing manifest file 'flufl.lock.egg-info/SOURCES.txt'
> copying docs/NEWS.rst -> 
> /<>/.pybuild/cpython3_3.11_flufl.lock/build/docs
> copying docs/apiref.rst -> 
> /<>/.pybuild/cpython3_3.11_flufl.lock/build/docs
> copying docs/index.rst -> 
> /<>/.pybuild/cpython3_3.11_flufl.lock/build/docs
> copying docs/theory.rst -> 
> /<>/.pybuild/cpython3_3.11_flufl.lock/build/docs
> copying docs/using.rst -> 
> /<>/.pybuild/cpython3_3.11_flufl.lock/build/docs
> python3 setup.py build_sphinx
> /usr/lib/python3/dist-packages/setuptools/dist.py:945: 
> SetuptoolsDeprecationWarning: The namespace_packages parameter is deprecated.
> !!
> 
> 
> 
> Please replace its usage with implicit namespaces (PEP 420).
> 
> See 
> https://setuptools.pypa.io/en/latest/references/keywords.html#keyword-namespace-packages
>  for details.
> 
> 
> 
> !!
>   ep.load()(self, ep.name, value)
> usage: setup.py [global_opts] cmd1 [cmd1_opts] [cmd2 [cmd2_opts] ...]
>or: setup.py --help [cmd1 cmd2 ...]
>or: setup.py --help-commands
>or: setup.py cmd --help
> 
> error: invalid command 'build_sphinx'
> make[1]: *** [debian/rules:15: override_dh_auto_build] Error 1


The full build log is available from:
http://qa-logs.debian.net/2023/07/30/exp/flufl.lock_5.0.1

Bug#1055142: marked as done (nvidia-graphics-drivers-tesla-470: CVE-2023-31022)

[Debian Bug Tracking System]

Your message dated Mon, 20 Nov 2023 11:20:17 +
with message-id 
and subject line Bug#1055142: fixed in nvidia-graphics-drivers-tesla-470 
470.223.02-1
has caused the Debian Bug report #1055142,
regarding nvidia-graphics-drivers-tesla-470: CVE-2023-31022
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1055142: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055142
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nvidia-graphics-drivers
Severity: normal
Tags: security
X-Debbugs-Cc: Debian Security Team 
Control: clone -1 -2 -3 -4 -5 -6 -7 -8 -9
Control: reassign -2 src:nvidia-graphics-drivers-legacy-340xx 340.76-6
Control: retitle -2 nvidia-graphics-drivers-legacy-340xx: CVE-2023-31022
Control: tag -2 + wontfix
Control: reassign -3 src:nvidia-graphics-drivers-legacy-390xx 390.48-4
Control: retitle -3 nvidia-graphics-drivers-legacy-390xx: CVE-2023-31022
Control: tag -3 + wontfix
Control: reassign -4 src:nvidia-graphics-drivers-tesla-418 418.87.01-1
Control: retitle -4 nvidia-graphics-drivers-tesla-418: CVE-2023-31022
Control: tag -4 + wontfix
Control: reassign -5 src:nvidia-graphics-drivers-tesla-450 450.51.05-1
Control: retitle -5 nvidia-graphics-drivers-tesla-450: CVE-2023-31022
Control: tag -5 + wontfix
Control: reassign -6 src:nvidia-graphics-drivers-tesla-460 460.32.03-1
Control: retitle -6 nvidia-graphics-drivers-tesla-460: CVE-2023-31022
Control: tag -6 + wontfix
Control: close -6 460.106.00-3
Control: reassign -7 src:nvidia-graphics-drivers-tesla-470 470.57.02-1
Control: retitle -7 nvidia-graphics-drivers-tesla-470: CVE-2023-31022
Control: reassign -8 src:nvidia-graphics-drivers-tesla 510.85.02-1
Control: retitle -8 nvidia-graphics-drivers-tesla: CVE-2023-31022
Control: found -8 515.48.07-1
Control: found -8 525.60.13-1
Control: found -8 535.54.03-1
Control: reassign -9 src:nvidia-open-gpu-kernel-modules 515.43.04-1
Control: retitle -9 nvidia-open-gpu-kernel-modules: CVE-2023-31022
Control: found -9 520.56.06-1
Control: found -9 525.85.12-1
Control: found -9 530.30.02-1
Control: found -9 535.43.02-1
Control: found -9 545.23.06-1
Control: found -1 340.24-1
Control: found -1 343.22-1
Control: found -1 396.18-1
Control: found -1 430.14-1
Control: found -1 455.23.04-1
Control: found -1 465.24.02-1
Control: found -1 495.44-1
Control: found -1 515.48.07-1
Control: found -1 520.56.06-1
Control: found -1 525.53-1
Control: found -1 530.30.02-1
Control: found -1 535.43.02-1
Control: found -1 545.23.06-1

https://nvidia.custhelp.com/app/answers/detail/a_id/5491

CVE-2023-31022  NVIDIA GPU Display Driver for Windows and Linux contains
a vulnerability in the kernel mode layer, where a NULL-pointer
dereference may lead to denial of service.

Linux Driver Branch CVE IDs Addressed
R545, R535, R525, R470  CVE-2023-31022

Driver Branch   Affected Driver VersionsUpdated Driver 
Version
R545All driver versions prior to 545.29.02  545.29.02
R535All driver versions prior to 535.129.03 535.129.03
R525All driver versions prior to 525.147.05 525.147.05
R470All driver versions prior to 470.223.02 470.223.02


Andreas
--- End Message ---
--- Begin Message ---
Source: nvidia-graphics-drivers-tesla-470
Source-Version: 470.223.02-1
Done: Andreas Beckmann 

We believe that the bug you reported is fixed in the latest version of
nvidia-graphics-drivers-tesla-470, which is due to be installed in the Debian 
FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1055...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Andreas Beckmann  (supplier of updated 
nvidia-graphics-drivers-tesla-470 package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 20 Nov 2023 11:43:36 +0100
Source: nvidia-graphics-drivers-tesla-470
Architecture: source
Version: 470.223.02-1
Distribution: unstable
Urgency: medium
Maintainer: Debian NVIDIA Maintainers 
Changed-By: Andreas Beckmann 
Closes: 1055142
Changes:
 nvidia-graphics-drivers-tesla-470 (470.223.02-1) unstable; urgency=medium
 .
   * New upstream long term support branch release 470.223.02 (2023-10-31).
 * Fixed CVE-2

Bug#1056287: marked as done (adios2: binary-all FTBFS)

[Debian Bug Tracking System]

Your message dated Mon, 20 Nov 2023 11:19:18 +
with message-id 
and subject line Bug#1056287: fixed in adios2 2.8.2+dfsg1-3
has caused the Debian Bug report #1056287,
regarding adios2: binary-all FTBFS
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1056287: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056287
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: adios2
Version: 2.8.2+dfsg1-2
Severity: serious
Tags: ftbfs
X-Debbugs-Cc: Drew Parsons 

https://buildd.debian.org/status/fetch.php?pkg=adios2&arch=all&ver=2.8.2%2Bdfsg1-2&stamp=1700402832&raw=0

...
   debian/rules override_dh_missing
make[1]: Entering directory '/<>'
dh_missing --sourcedir=install-serial
dh_missing: warning: usr/bin/adios2-config.serial exists in install-serial but 
is not installed to anywhere 
dh_missing: error: missing files, aborting
The following debhelper tools have reported what they installed (with 
files per package)
 * dh_cmake_install: adios2-data (13), adios2-mpi-bin (7), 
adios2-scripts (14), adios2-serial-bin (4), libadios2-mpi-c++11-2 (4), 
libadios2-mpi-c++11-dev (16), libadios2-mpi-c-2 (4), libadios2-mpi-c-dev (12), 
libadios2-mpi-core-2 (5), libadios2-mpi-core-dev (184), libadios2-mpi-fortran-2 
(4), libadios2-mpi-fortran-dev (33), libadios2-serial-c++11-2 (2), 
libadios2-serial-c++11-dev (15), libadios2-serial-c-2 (2), 
libadios2-serial-c-dev (11), libadios2-serial-core-2 (3), 
libadios2-serial-core-dev (183), libadios2-serial-fortran-2 (2), 
libadios2-serial-fortran-dev (30), python3-adios2-mpi (1), 
python3-adios2-serial (1)
 * dh_install: adios2-data (0), adios2-mpi-bin (0), adios2-scripts (0), 
adios2-serial-bin (0), libadios2-common-c++11-dev (0), libadios2-common-c-dev 
(0), libadios2-common-core-dev (0), libadios2-mpi-auxiliary-2 (10), 
libadios2-mpi-auxiliary-dev (6), libadios2-mpi-c++11-2 (0), 
libadios2-mpi-c++11-dev (0), libadios2-mpi-c-2 (0), libadios2-mpi-c-dev (0), 
libadios2-mpi-core-2 (0), libadios2-mpi-core-dev (0), libadios2-mpi-fortran-2 
(0), libadios2-mpi-fortran-dev (0), libadios2-serial-auxiliary-2 (10), 
libadios2-serial-auxiliary-dev (6), libadios2-serial-c++11-2 (0), 
libadios2-serial-c++11-dev (0), libadios2-serial-c-2 (0), 
libadios2-serial-c-dev (0), libadios2-serial-core-2 (0), 
libadios2-serial-core-dev (0), libadios2-serial-fortran-2 (0), 
libadios2-serial-fortran-dev (0), python3-adios2 (1), python3-adios2-mpi (0), 
python3-adios2-serial (0)
 * dh_installdocs: adios2-data (0), adios2-mpi-bin (0), adios2-scripts 
(0), adios2-serial-bin (0), libadios2-common-c++11-dev (0), 
libadios2-common-c-dev (0), libadios2-common-core-dev (0), 
libadios2-mpi-auxiliary-2 (0), libadios2-mpi-auxiliary-dev (0), 
libadios2-mpi-c++11-2 (0), libadios2-mpi-c++11-dev (0), libadios2-mpi-c-2 (0), 
libadios2-mpi-c-dev (0), libadios2-mpi-core-2 (0), libadios2-mpi-core-dev (0), 
libadios2-mpi-fortran-2 (0), libadios2-mpi-fortran-dev (0), 
libadios2-serial-auxiliary-2 (0), libadios2-serial-auxiliary-dev (0), 
libadios2-serial-c++11-2 (0), libadios2-serial-c++11-dev (0), 
libadios2-serial-c-2 (0), libadios2-serial-c-dev (0), libadios2-serial-core-2 
(0), libadios2-serial-core-dev (0), libadios2-serial-fortran-2 (0), 
libadios2-serial-fortran-dev (0), python3-adios2 (1), python3-adios2-mpi (0), 
python3-adios2-serial (0)
If the missing files are installed by another tool, please file a bug 
against it.
When filing the report, if the tool is not part of debhelper itself, 
please reference the
"Logging helpers and dh_missing" section from the "PROGRAMMING" guide 
for debhelper (10.6.3+).
  (in the debhelper package: /usr/share/doc/debhelper/PROGRAMMING.md.gz)
Be sure to test with dpkg-buildpackage -A/-B as the results may vary 
when only a subset is built
If the omission is intentional or no other helper can take care of this 
consider adding the
paths to debian/not-installed.
make[1]: *** [debian/rules:172: override_dh_missing] Error 25
--- End Message ---
--- Begin Message ---
Source: adios2
Source-Version: 2.8.2+dfsg1-3
Done: Drew Parsons 

We believe that the bug you reported is fixed in the latest version of
adios2, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1056...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software

Bug#1056312: zlib1g makes tex-common fail to install due to fmtutil failing

[Johannes Schauer Marin Rodrigues]

Package: zlib1g
Version: 1:1.3.dfsg-2
Severity: serious

Hi,

I didn't investigate this further yet but filing this as RC as it is easy to
reproduce and it's easy to find out that only zlib1g changed using debbisect.
Downgrading to zlib1g 1:1.2.13.dfsg-3 makes the problem go away. Steps to
reproduce:

$ mmdebstrap --include=tex-common,texlive-base unstable /dev/null
Processing triggers for tex-common (6.18) ...
Running updmap-sys. This may take some time... done.
Running mktexlsr /var/lib/texmf ... done.
Building format(s) --all.
This may take some time... 
fmtutil failed. Output has been stored in
/tmp/fmtutil.tcAsaQVq
Please include this file if you report a bug.

dpkg: error processing package tex-common (--configure):
 installed tex-common package post-installation script subprocess returned 
error exit status 1
Errors were encountered while processing:
 tex-common
E: Sub-process env returned an error code (1)

Bug#1056313: network-manager: breaks networking

[Vincent Lefevre]

Package: network-manager
Version: 1.44.2-4
Severity: grave
Justification: renders package unusable

Just after the upgrade of network-manager from 1.44.2-1 to 1.44.2-4,
my network is down.

In the journalctl logs, I can see

[...]
Nov 20 12:08:58 cventin NetworkManager[286424]:   [1700478538.0092] 
policy: auto-activating connection 'Wired connection 1' 
(c89d3bc3-8d9e-44f8-ac86-7e6884d08219)
Nov 20 12:08:58 cventin NetworkManager[286424]:   [1700478538.0098] 
device (enp0s25): Activation: starting connection 'Wired connection 1' 
(c89d3bc3-8d9e-44f8-ac86-7e6884d08219)
Nov 20 12:08:58 cventin NetworkManager[286424]:   [1700478538.0099] 
device (enp0s25): state change: disconnected -> prepare (reason 'none', 
sys-iface-state: 'managed')
Nov 20 12:08:58 cventin NetworkManager[286424]:   [1700478538.0103] 
manager: NetworkManager state is now CONNECTING
Nov 20 12:08:58 cventin NetworkManager[286424]:   [1700478538.0106] 
device (enp0s25): state change: prepare -> config (reason 'none', 
sys-iface-state: 'managed')
Nov 20 12:08:58 cventin NetworkManager[286424]:   [1700478538.0116] 
device (enp0s25): state change: config -> ip-config (reason 'none', 
sys-iface-state: 'managed')
Nov 20 12:08:58 cventin NetworkManager[286424]:   [1700478538.0122] dhcp4 
(enp0s25): activation: beginning transaction (timeout in 45 seconds)
Nov 20 12:08:58 cventin NetworkManager[286424]:   [1700478538.0158] dhcp4 
(enp0s25): dhclient started with pid 294230
Nov 20 12:08:58 cventin avahi-daemon[758]: Joining mDNS multicast group on 
interface enp0s25.IPv6 with address fe80::9a90:96ff:febd:7ff7.
Nov 20 12:08:58 cventin avahi-daemon[758]: New relevant interface enp0s25.IPv6 
for mDNS.
Nov 20 12:08:58 cventin avahi-daemon[758]: Registering new address record for 
fe80::9a90:96ff:febd:7ff7 on enp0s25.*.
Nov 20 12:08:58 cventin dhclient[294231]: execve (/usr/libexec/nm-dhcp-helper, 
...): Permission denied
Nov 20 12:08:58 cventin kernel: audit: type=1400 audit(1700478538.018:40): 
apparmor="DENIED" operation="exec" class="file" profile="/{,usr/}sbin/dhclient" 
name="/usr/libexec/nm-dhcp-helper" pid=294231 comm="dhclient" 
requested_mask="x" denied_mask="x" fsuid=0 ouid=0
Nov 20 12:08:58 cventin dhclient[294230]: DHCPREQUEST for 140.77.13.17 on 
enp0s25 to 255.255.255.255 port 67
Nov 20 12:08:58 cventin dhclient[294230]: DHCPACK of 140.77.13.17 from 
140.77.1.11
Nov 20 12:08:58 cventin dhclient[294233]: execve (/usr/libexec/nm-dhcp-helper, 
...): Permission denied
Nov 20 12:08:58 cventin kernel: audit: type=1400 audit(1700478538.042:41): 
apparmor="DENIED" operation="exec" class="file" profile="/{,usr/}sbin/dhclient" 
name="/usr/libexec/nm-dhcp-helper" pid=294233 comm="dhclient" 
requested_mask="x" denied_mask="x" fsuid=0 ouid=0
Nov 20 12:08:58 cventin dhclient[294230]: bound to 140.77.13.17 -- renewal in 
36738 seconds.
[...]

The issue disappeared after downgrading back to 1.44.2-1.

Note: the errors about /usr/libexec/nm-dhcp-helper changed to

Nov 20 12:17:42 cventin dhclient[295468]: execve (/usr/libexec/nm-dhcp-helper, 
...): No such file or directory

but the network is working. I don't whether this is related, though.

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

Kernel: Linux 6.5.0-4-amd64 (SMP w/12 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=POSIX, 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 network-manager depends on:
ii  adduser 3.137
ii  dbus [default-dbus-system-bus]  1.14.10-3
ii  libaudit1   1:3.1.1-1
ii  libbluetooth3   5.70-1
ii  libc6   2.37-12
ii  libcurl3-gnutls 8.4.0-2
ii  libglib2.0-02.78.1-4
ii  libgnutls30 3.8.1-4+b1
ii  libjansson4 2.14-2
ii  libmm-glib0 1.22.0-1
ii  libndp0 1.8-1
ii  libnewt0.52 0.52.24-1
ii  libnm0  1.44.2-4
ii  libpsl5 0.21.2-1+b1
ii  libreadline88.2-1.3
ii  libselinux1 3.5-1
ii  libsystemd0 254.5-1
ii  libteamdctl01.31-1
ii  libudev1254.5-1
ii  polkitd 123-3
ii  udev254.5-1

Versions of packages network-manager recommends:
ii  dnsmasq-base [dnsmasq-base]  2.89-1
ii  libpam-systemd   254.5-1
ii  modemmanager 1.22.0-1
pn  ppp 

Processed: Re: network-manager: breaks networking

[Debian Bug Tracking System]

Processing control commands:

> found -1 1.44.2-3
Bug #1056313 [network-manager] network-manager: breaks networking
Marked as found in versions network-manager/1.44.2-3.
> retitle -1 network-manager: breaks networking (Permission denied for the new 
> /usr/libexec/nm-dhcp-helper)
Bug #1056313 [network-manager] network-manager: breaks networking
Changed Bug title to 'network-manager: breaks networking (Permission denied for 
the new /usr/libexec/nm-dhcp-helper)' from 'network-manager: breaks networking'.

-- 
1056313: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056313
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1056313: network-manager: breaks networking

[Vincent Lefevre]

Control: found -1 1.44.2-3
Control: retitle -1 network-manager: breaks networking (Permission denied for 
the new /usr/libexec/nm-dhcp-helper)

On 2023-11-20 12:24:36 +0100, Vincent Lefevre wrote:
> Package: network-manager
> Version: 1.44.2-4
> Severity: grave
> Justification: renders package unusable
> 
> Just after the upgrade of network-manager from 1.44.2-1 to 1.44.2-4,
> my network is down.

The testing version 1.44.2-3 is broken too.

> The issue disappeared after downgrading back to 1.44.2-1.
> 
> Note: the errors about /usr/libexec/nm-dhcp-helper changed to
> 
> Nov 20 12:17:42 cventin dhclient[295468]: execve 
> (/usr/libexec/nm-dhcp-helper, ...): No such file or directory
> 
> but the network is working. I don't whether this is related, though.

This is because /usr/libexec/nm-dhcp-helper exists in
1.44.2-3 and 1.44.2-4, but not in 1.44.2-1.

I suspect that nm-dhcp-helper has been added because it is now needed.
But it doesn't work due to the "Permission denied".

I've attached more journalctl output, in case it is needed.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
Nov 20 12:26:43 cventin systemd[1]: Starting NetworkManager.service - Network 
Manager...
Nov 20 12:26:43 cventin dbus-daemon[761]: [system] Successfully activated 
service 'org.freedesktop.nm_dispatcher'
Nov 20 12:26:43 cventin systemd[1]: Started NetworkManager-dispatcher.service - 
Network Manager Script Dispatcher Service.
Nov 20 12:26:43 cventin NetworkManager[296512]:   [1700479603.2215] 
NetworkManager (version 1.44.2) is starting... (after a restart, 
boot:69bc9a99-ac9d-4eb8-9de9-9471a74d32b3)
Nov 20 12:26:43 cventin NetworkManager[296512]:   [1700479603.2216] Read 
config: /etc/NetworkManager/NetworkManager.conf (lib: no-mac-addr-change.conf) 
(etc: dhcp.conf, logging.conf)
Nov 20 12:26:43 cventin NetworkManager[296512]:   [1700479603.2284] 
manager[0x564430a339a0]: monitoring kernel firmware directory '/lib/firmware'.
Nov 20 12:26:43 cventin NetworkManager[296512]:   [1700479603.2285] 
monitoring ifupdown state file '/run/network/ifstate'.
Nov 20 12:26:43 cventin dbus-daemon[761]: [system] Activating via systemd: 
service name='org.freedesktop.hostname1' 
unit='dbus-org.freedesktop.hostname1.service' requested by ':1.269' (uid=0 
pid=296512 comm="/usr/sbin/NetworkManager --no-daemon")
Nov 20 12:26:43 cventin systemd[1]: Starting systemd-hostnamed.service - 
Hostname Service...
Nov 20 12:26:43 cventin dbus-daemon[761]: [system] Successfully activated 
service 'org.freedesktop.hostname1'
Nov 20 12:26:43 cventin systemd[1]: Started systemd-hostnamed.service - 
Hostname Service.
Nov 20 12:26:43 cventin NetworkManager[296512]:   [1700479603.3134] 
hostname: hostname: using hostnamed
Nov 20 12:26:43 cventin NetworkManager[296512]:   [1700479603.3134] 
hostname: static hostname changed from (none) to "cventin"
Nov 20 12:26:43 cventin NetworkManager[296512]:   [1700479603.3140] 
dns-mgr: init: dns=default,systemd-resolved rc-manager=symlink (auto)
Nov 20 12:26:43 cventin NetworkManager[296512]:   [1700479603.3144] 
manager[0x564430a339a0]: rfkill: Wi-Fi hardware radio set enabled
Nov 20 12:26:43 cventin NetworkManager[296512]:   [1700479603.3145] 
manager[0x564430a339a0]: rfkill: WWAN hardware radio set enabled
Nov 20 12:26:43 cventin NetworkManager[296512]:   [1700479603.3171] 
Loaded device plugin: NMWifiFactory 
(/usr/lib/x86_64-linux-gnu/NetworkManager/1.44.2/libnm-device-plugin-wifi.so)
Nov 20 12:26:43 cventin NetworkManager[296512]:   [1700479603.3205] 
Loaded device plugin: NMBluezManager 
(/usr/lib/x86_64-linux-gnu/NetworkManager/1.44.2/libnm-device-plugin-bluetooth.so)
Nov 20 12:26:43 cventin NetworkManager[296512]:   [1700479603.3208] 
Loaded device plugin: NMWwanFactory 
(/usr/lib/x86_64-linux-gnu/NetworkManager/1.44.2/libnm-device-plugin-wwan.so)
Nov 20 12:26:43 cventin NetworkManager[296512]:   [1700479603.3224] 
Loaded device plugin: NMTeamFactory 
(/usr/lib/x86_64-linux-gnu/NetworkManager/1.44.2/libnm-device-plugin-team.so)
Nov 20 12:26:43 cventin NetworkManager[296512]:   [1700479603.3228] 
Loaded device plugin: NMAtmManager 
(/usr/lib/x86_64-linux-gnu/NetworkManager/1.44.2/libnm-device-plugin-adsl.so)
Nov 20 12:26:43 cventin NetworkManager[296512]:   [1700479603.3231] 
manager: rfkill: Wi-Fi enabled by radio killswitch; enabled by state file
Nov 20 12:26:43 cventin NetworkManager[296512]:   [1700479603.3232] 
manager: rfkill: WWAN enabled by radio killswitch; enabled by state file
Nov 20 12:26:43 cventin NetworkManager[296512]:   [1700479603.3233] 
manager: Networking is enabled by state file
Nov 20 12:26:43 cventin NetworkManager[296512]:   [1700479603.3238] 
settings: Loaded settings plugin: ifupdown 
("/usr/lib/x86_64-linux-gnu/NetworkManager/1.44.2/libnm-settings-plugin-ifupdown.so")
Nov 20 12:26:43 cventin NetworkManager[296512]:   [1700479603.3239] 
settings: 

Bug#1051243: texlive-binaries needs rebuild due to update of zlib to 1.3

[Friedrich Beckmann]

I did a rebuild of texlive-binaries from source. Then I installed the created 
packages. The build environment contains zlib1g-dev 1.3-dfsg2.

Then "apt install texlive-plain-generic“ will work.

So texlive needs a rebuild due to the zlib version update as texlive seems to 
remember which version of zlib was used during build.

Bug#1051243: This affects the build of the pspp package

[Preuße]

On 20.11.2023 10:43, Friedrich Beckmann wrote:

Hi,


i noticed a failure in our CI pipeline for pspp probably due to this bug. The 
problem occurs when I try to install "apt install texlive-plain-generic“. The 
install fails with



A new package is on the way. Another adaption to zlib is needed, I'll 
trigger that later on.


H.
--
sigfault



OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1056312: zlib1g makes tex-common fail to install due to fmtutil failing

[Luca Boccassi]

Control: found -1 1:1.3.dfsg-1

On Mon, 20 Nov 2023 12:20:55 +0100 Johannes Schauer Marin Rodrigues
 wrote:
> Package: zlib1g
> Version: 1:1.3.dfsg-2
> Severity: serious
> 
> Hi,
> 
> I didn't investigate this further yet but filing this as RC as it is
easy to
> reproduce and it's easy to find out that only zlib1g changed using
debbisect.
> Downgrading to zlib1g 1:1.2.13.dfsg-3 makes the problem go away.
Steps to
> reproduce:
> 
> $ mmdebstrap --include=tex-common,texlive-base unstable /dev/null
> Processing triggers for tex-common (6.18) ...
> Running updmap-sys. This may take some time... done.
> Running mktexlsr /var/lib/texmf ... done.
> Building format(s) --all.
>   This may take some time... 
> fmtutil failed. Output has been stored in
> /tmp/fmtutil.tcAsaQVq
> Please include this file if you report a bug.
> 
> dpkg: error processing package tex-common (--configure):
>  installed tex-common package post-installation script subprocess
returned error exit status 1
> Errors were encountered while processing:
>  tex-common
> E: Sub-process env returned an error code (1)

Looks like this was introduced by 1:1.3.dfsg-1, as it can be reproduced
in a minimal sid chroot by installing it from
https://snapshot.debian.org/archive/debian/20231118T151103Z/pool/main/z/zlib/zlib1g_1.3.dfsg-1_amd64.deb
and then installing texlive-base:

<...>
Processing triggers for tex-common (6.18) ...
Running updmap-sys. This may take some time... done.
Running mktexlsr /var/lib/texmf ... done.
Building format(s) --all.
This may take some time... 
fmtutil failed. Output has been stored in
/tmp/fmtutil.ohLhbhu3
Please include this file if you report a bug.

dpkg: error processing package tex-common (--configure):
 installed tex-common package post-installation script subprocess returned 
error exit status 1
Errors were encountered while processing:
 tex-common
E: Sub-process /usr/bin/dpkg returned an error code (1)
# dpkg -l | grep zlib
ii  zlib1g:amd64 1:1.3.dfsg-1   amd64   
 compression library - runtime
ii  zlib1g-dev:amd64 1:1.3.dfsg-1   amd64   
 compression library - development

-- 
Kind regards,
Luca Boccassi


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

Processed: Re: zlib1g makes tex-common fail to install due to fmtutil failing

[Debian Bug Tracking System]

Processing control commands:

> found -1 1:1.3.dfsg-1
Bug #1056312 [zlib1g] zlib1g makes tex-common fail to install due to fmtutil 
failing
Marked as found in versions zlib/1:1.3.dfsg-1.

-- 
1056312: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056312
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1056312: zlib1g makes tex-common fail to install due to fmtutil failing

[Luca Boccassi]

On Mon, 20 Nov 2023 11:57:20 + Luca Boccassi 
wrote:
> Control: found -1 1:1.3.dfsg-1
> 
> On Mon, 20 Nov 2023 12:20:55 +0100 Johannes Schauer Marin Rodrigues
>  wrote:
> > Package: zlib1g
> > Version: 1:1.3.dfsg-2
> > Severity: serious
> > 
> > Hi,
> > 
> > I didn't investigate this further yet but filing this as RC as it
is
> easy to
> > reproduce and it's easy to find out that only zlib1g changed using
> debbisect.
> > Downgrading to zlib1g 1:1.2.13.dfsg-3 makes the problem go away.
> Steps to
> > reproduce:
> > 
> > $ mmdebstrap --include=tex-common,texlive-base unstable /dev/null
> > Processing triggers for tex-common (6.18) ...
> > Running updmap-sys. This may take some time... done.
> > Running mktexlsr /var/lib/texmf ... done.
> > Building format(s) --all.
> >   This may take some time... 
> > fmtutil failed. Output has been stored in
> > /tmp/fmtutil.tcAsaQVq
> > Please include this file if you report a bug.
> > 
> > dpkg: error processing package tex-common (--configure):
> >  installed tex-common package post-installation script subprocess
> returned error exit status 1
> > Errors were encountered while processing:
> >  tex-common
> > E: Sub-process env returned an error code (1)
> 
> Looks like this was introduced by 1:1.3.dfsg-1, as it can be
reproduced
> in a minimal sid chroot by installing it from
>
https://snapshot.debian.org/archive/debian/20231118T151103Z/pool/main/z/zlib/zlib1g_1.3.dfsg-1_amd64.deb
> and then installing texlive-base:
> 
> <...>
> Processing triggers for tex-common (6.18) ...
> Running updmap-sys. This may take some time... done.
> Running mktexlsr /var/lib/texmf ... done.
> Building format(s) --all.
>   This may take some time... 
> fmtutil failed. Output has been stored in
> /tmp/fmtutil.ohLhbhu3
> Please include this file if you report a bug.
> 
> dpkg: error processing package tex-common (--configure):
>  installed tex-common package post-installation script subprocess
returned error exit status 1
> Errors were encountered while processing:
>  tex-common
> E: Sub-process /usr/bin/dpkg returned an error code (1)
> # dpkg -l | grep zlib
> ii  zlib1g:amd64 1:1.3.dfsg-1  
amd64    compression library - runtime
> ii  zlib1g-dev:amd64 1:1.3.dfsg-1  
amd64    compression library - development
> 
> -- 

Looks like a problem in texlive itself, so this can probably be
moved/merged:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051243#48

-- 
Kind regards,
Luca Boccassi


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

Bug#1051243: This affects the build of the pspp package

[Luca Boccassi]

On Mon, 20 Nov 2023 12:50:24 +0100 =?UTF-8?B?UHJldcOfZSwgSGlsbWFy?=
 wrote:
> On 20.11.2023 10:43, Friedrich Beckmann wrote:
> 
> Hi,
> 
> > i noticed a failure in our CI pipeline for pspp probably due to
this bug. The problem occurs when I try to install "apt install
texlive-plain-generic“. The install fails with
> > 
> 
> A new package is on the way. Another adaption to zlib is needed, I'll
> trigger that later on.

PANIC: unprotected error in call to Lua API (zlib library version does
not match - header: 1.2.13, library: 1.3)

This looks like an undeclared versioning dependency issue. If there are
such constraints, please consider declaring them appropriately in the
package control file by defining a dependency on the exact upstream
version of zlib (e.g.: >= 1.3~ and << 1.3.1 or something like that).
Then every new upstream revision of zlib need to be handled as a sort-
of soname transition for tex-common.

-- 
Kind regards,
Luca Boccassi


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

Bug#1056313: network-manager: breaks networking

[Vincent Lefevre]

On 2023-11-20 12:42:14 +0100, Vincent Lefevre wrote:
> I suspect that nm-dhcp-helper has been added because it is now needed.
> But it doesn't work due to the "Permission denied".

If I understand correctly, /usr/lib/NetworkManager/nm-dhcp-helper moved
to /usr/libexec/nm-dhcp-helper, but /etc/apparmor.d/sbin.dhclient from
isc-dhcp-client was not updated.

/etc/apparmor.d/sbin.dhclient still contains the old paths.

Shouldn't there be a "Breaks:" on isc-dhcp-client (<< 4.4.3-P1-4) in
order to ensure that the user also upgrades isc-dhcp-client or block
the upgrade until isc-dhcp-clients gets modified?

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

Processed: severity of 1050300 is grave

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 1050300 grave
Bug #1050300 [mkbootimg] mkbootimg package missing gki module
Severity set to 'grave' from 'normal'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1050300: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050300
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: found 1050300 in 33.0.3-2~bpo12+1

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> found 1050300 33.0.3-2~bpo12+1
Bug #1050300 [mkbootimg] mkbootimg package missing gki module
There is no source info for the package 'mkbootimg' at version 
'33.0.3-2~bpo12+1' with architecture ''
Unable to make a source version for version '33.0.3-2~bpo12+1'
Marked as found in versions 33.0.3-2~bpo12+1.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1050300: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050300
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1056313: network-manager: breaks networking

[Vincent Lefevre]

On 2023-11-20 12:24:36 +0100, Vincent Lefevre wrote:
> Note: the errors about /usr/libexec/nm-dhcp-helper changed to
> 
> Nov 20 12:17:42 cventin dhclient[295468]: execve 
> (/usr/libexec/nm-dhcp-helper, ...): No such file or directory
> 
> but the network is working. I don't whether this is related, though.

Forget about the "No such file or directory" error. This was the
first time I got it, and I suspect that it is due to the downgrade of
network-manager (something normally not supported), e.g. the running
dhclient was still expecting the new paths, which disappeared with
the downgrade.

So, the only issue seems the "Permission denied" with the new
network-manager versions due to the change of the paths done for

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

   * Install helper binaries into /usr/libexec (Closes: #1026388)

and the fact that /etc/apparmor.d/sbin.dhclient from
isc-dhcp-client 4.4.3-P1-4 still has the old paths.

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

Bug#1051243: This affects the build of the pspp package

[Preuße]

On 20.11.2023 13:11, Luca Boccassi wrote:

Hi,


This looks like an undeclared versioning dependency issue. If there are
such constraints, please consider declaring them appropriately in the
package control file by defining a dependency on the exact upstream
version of zlib (e.g.: >= 1.3~ and << 1.3.1 or something like that).
Then every new upstream revision of zlib need to be handled as a sort-
of soname transition for tex-common.



Currently it is rather an overdone version check in the source code. In 
rev -8 we have untighten that check. Further a simple rebuild would have 
solved the issue too.


H.
--
sigfault



OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1055922: rmatrix: ABI change in Matrix 1.6-2

[Graham Inggs]

Hi Dirk

On Sun, 19 Nov 2023 at 14:59, Dirk Eddelbuettel  wrote:
> So it contains a patch by Mikael which had been applied _permitting Matrix
> 1.6-2_ to get to CRAN. So for this particular pair it was the other way 
> around.

Great, thanks for clearing that up.

> So I leave this in your hands. If you think that after all this needs a
> transtion, I may shrug but will of course help.

Well, we are doing a transition (for some value of), just not a
"rebuild everything" transition like we must do for C libraries, but a
"rebuild only affected things" like we do for Python and other
interpreted languages.

On Sun, 19 Nov 2023 at 17:28, Dirk Eddelbuettel  wrote:
> Done in lme4 1.1-35.1-3.

Thanks.  I see now r-cran-lme4 now has a:
Depends: r-cran-matrix (>= 1.6-2)
...however this is not correct, because dpkg considers r-cran-matrix
1.6-1.1-1 in testing to meet that requirement, and the tests still
fail with that version.

$ dpkg --compare-versions 1.6-1.1-1 ge 1.6-2 && echo True
True

Please change that to:
Depends: r-cran-matrix (>= 1.6-2-1)
... and re-upload, because dpkg considers 1.6-2 to be upstream version
1.6 and Debian revision 2, whereas we need upstream version 1.6-2 and
Debian revision 1.

$ dpkg --compare-versions 1.6-1.1-1 ge 1.6-2-1 && echo True


Regards
Graham

Bug#1055922: rmatrix: ABI change in Matrix 1.6-2

[Graham Inggs]

Hi Andreas

On Mon, 20 Nov 2023 at 06:59, Andreas Tille  wrote:
> > We liked the change you made to r-cran-tmb [2], as this allows the
> > affected packages to be binNMU'd and gain a versioned dependency on
> > r-cran-matrix.  Would you please apply this to the other affected
> > packages (only r-cran-irlba and r-cran-openmx, if I understand
> > correctly)?
>
> Done.

Thanks!

For the r-cran-tmb upload, I now see only autopkgtest regressions [1] for:
r-cran-insight/0.19.6+dfsg-1
r-cran-parameters/0.21.2-1
I have not investigated, but these seem to be passing in unstable, so
can be hinted if needed.

For the r-cran-irlba upload, there's only one autopkgtest regression [2] for:
r-cran-seurat/4.4.0-1
This autopkgtest currently fails in unstable as well, would you please
investigate?
It seems your r-cran-seuratobject 5.0.0-1 upload is blocked by this
same regression for 19 days [3] and r-cran-seurat has not yet been
updated to the new upstream version 5.0.1.  Does something prevent you
from updating?

For the r-cran-openmx upload, there are no autopkgtest regressions [4]
\o/

> I've reverted this but in previous discussion[4] with Paul we agreed
> upon the strict version dependency.  I think this is only necessary for
> r-cran-tmb (where upstream is enforcing this with a test I'm hesitating
> to patch out).  But maybe upstream can work with the freshly implemented
> R_MATRIX_ABI_VERSION and thus we can come back to upstream if the
> autopkgtest will fire next time (which will happen now after the next
> r-cran-matrix update).

Thanks again.  Yes, let's wait to see how TMB upstream deals with this.

Regards
Graham


[1] https://qa.debian.org/excuses.php?package=r-cran-tmb
[2] https://qa.debian.org/excuses.php?package=r-cran-irlba
[3] https://qa.debian.org/excuses.php?package=r-cran-seuratobject
[4] https://qa.debian.org/excuses.php?package=r-cran-openmx

Bug#1055922: rmatrix: ABI change in Matrix 1.6-2

[Dirk Eddelbuettel]

Hi Graham,

On 20 November 2023 at 12:13, Graham Inggs wrote:
| On Sun, 19 Nov 2023 at 14:59, Dirk Eddelbuettel  wrote:
| > So it contains a patch by Mikael which had been applied _permitting Matrix
| > 1.6-2_ to get to CRAN. So for this particular pair it was the other way 
around.
| 
| Great, thanks for clearing that up.
| 
| > So I leave this in your hands. If you think that after all this needs a
| > transtion, I may shrug but will of course help.
| 
| Well, we are doing a transition (for some value of), just not a
| "rebuild everything" transition like we must do for C libraries, but a
| "rebuild only affected things" like we do for Python and other
| interpreted languages.
| 
| On Sun, 19 Nov 2023 at 17:28, Dirk Eddelbuettel  wrote:
| > Done in lme4 1.1-35.1-3.
| 
| Thanks.  I see now r-cran-lme4 now has a:
| Depends: r-cran-matrix (>= 1.6-2)
| ...however this is not correct, because dpkg considers r-cran-matrix
| 1.6-1.1-1 in testing to meet that requirement, and the tests still
| fail with that version.
| 
| $ dpkg --compare-versions 1.6-1.1-1 ge 1.6-2 && echo True
| True
| 
| Please change that to:
| Depends: r-cran-matrix (>= 1.6-2-1)
| ... and re-upload, because dpkg considers 1.6-2 to be upstream version
| 1.6 and Debian revision 2, whereas we need upstream version 1.6-2 and
| Debian revision 1.
| 
| $ dpkg --compare-versions 1.6-1.1-1 ge 1.6-2-1 && echo True
| 

Dang. Fell into a well-known hole there.  Will fix ASAP. Had in the back of
my mind some notion of 'cannot express Debian build number' but that is
clearly wrong.

Dirk

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

Processed: tagging 1051243

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 1051243 + ftbfs
Bug #1051243 [tex-common] tex-common: fmtutil failed on tex-common upgrade
Added tag(s) ftbfs.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1051243: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051243
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1055922: rmatrix: ABI change in Matrix 1.6-2

[Andreas Tille]

Hi Graham,

Am Mon, Nov 20, 2023 at 12:21:39PM -0100 schrieb Graham Inggs:
> For the r-cran-tmb upload, I now see only autopkgtest regressions [1] for:
> r-cran-insight/0.19.6+dfsg-1
> r-cran-parameters/0.21.2-1
> I have not investigated, but these seem to be passing in unstable, so
> can be hinted if needed.

OK, let me know if I should do something.
 
> For the r-cran-irlba upload, there's only one autopkgtest regression [2] for:
> r-cran-seurat/4.4.0-1
> This autopkgtest currently fails in unstable as well, would you please
> investigate?

By chance I tried to upgrade r-cran-seurat a couple of hours ago since
there is a new upstream version (which follows r-cran-seuratobject
version bump).  Unfortunately it needs a new dependency which I pushed
to new[5].  Since I have no idea what the failures in r-cran-seurat test
log[6] mean I would prefer to wait until we can upload the latest
version.

> It seems your r-cran-seuratobject 5.0.0-1 upload is blocked by this
> same regression for 19 days [3] and r-cran-seurat has not yet been
> updated to the new upstream version 5.0.1.  Does something prevent you
> from updating?

See above.
 
> For the r-cran-openmx upload, there are no autopkgtest regressions [4]
> \o/

Nice.
 
> > I've reverted this but in previous discussion[4] with Paul we agreed
> > upon the strict version dependency.  I think this is only necessary for
> > r-cran-tmb (where upstream is enforcing this with a test I'm hesitating
> > to patch out).  But maybe upstream can work with the freshly implemented
> > R_MATRIX_ABI_VERSION and thus we can come back to upstream if the
> > autopkgtest will fire next time (which will happen now after the next
> > r-cran-matrix update).
> 
> Thanks again.  Yes, let's wait to see how TMB upstream deals with this.

Kind regards and thank you for your work in release team
   Andreas.
 
> [1] https://qa.debian.org/excuses.php?package=r-cran-tmb
> [2] https://qa.debian.org/excuses.php?package=r-cran-irlba
> [3] https://qa.debian.org/excuses.php?package=r-cran-seuratobject
> [4] https://qa.debian.org/excuses.php?package=r-cran-openmx


[5] https://ftp-master.debian.org/new/r-cran-fastdummies_1.7.3-1.html
[6] https://ci.debian.net/packages/r/r-cran-seurat/unstable/amd64/40043272/

-- 
http://fam-tille.de

Bug#1051243: tex-common: fmtutil failed on tex-common upgrade

[Gunnar Hjalmarsson]

X-Debbugs-Cc: debian-input-met...@lists.debian.org

On 2023-11-18 21:20, Gunnar Hjalmarsson wrote:
This problem prevents the ibus-table package, where tex-common is 
indirectly in Build-Depends, from building in unstable.


https://buildd.debian.org/status/logs.php?pkg=ibus-table&ver=1.17.4-2&arch=all


FTR I can confirm that the latest version of texlive-bin fixed that 
problem, and ibus-table has been successfully built now.


--
Gunnar

Bug#1050854: xarray test failure on amd64

[Andreas Tille]

Hi Rebecca,

Am Sun, Nov 19, 2023 at 09:58:26PM + schrieb Rebecca N. Palmer:
> This bug is now a crash (not the original error message):
> https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-xarray/39962554/log.gz
> I don't know whether the same patch still works.
> 
> The Salsa repository now appears to be up to date.

I've pushed a candidate for the next upstream version.
 
> You probably also want to include the fixes for the other two RC bugs (see
> there).

I guess you might specifically think of bug #1053700 where you provided
the idea for a patch.  I would be extremely grateful if you could commit
your patch right to the Git repository.  You obviously inspected the
code while I never ever touched xarray code before.  I simply stumbled
upon it due to a testing removal warning and I'm pretty loaded with
other stuff.

Thanks a lot
Andreas. 

-- 
http://fam-tille.de

Bug#1056312: zlib1g makes tex-common fail to install due to fmtutil failing

[Hilmar Preusse]

Package: zlib1g
Version: 1:1.3.dfsg-2
Followup-For: Bug #1056312
X-Debbugs-Cc: debian-tex-ma...@lists.debian.org

Hello Mark,

In 1:1.2.6.dfsg-2 an "Breaks: ... texlive-binaries (<< 2009-12)" statement
was introduced to make sure the broken tl-bin packages are phased out.
We now need the same again: 2023.20230311.66589-7 is the last broken version;
2023.20230311.66589-8 contains the fix and has been uploaded this morning.

Please bump the version in that breaks statement!

Many thanks!

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

Kernel: Linux 6.1.21-v8+ (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_CRAP
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)

Versions of packages zlib1g depends on:
ii  libc6  2.36-9+rpt2+deb12u3

zlib1g recommends no packages.

zlib1g suggests no packages.

-- no debconf information

-- 
sigmentation fault


signature.asc
Description: PGP signature

Bug#1056279: Looks like the systemctl links are gone but not the pm-utils ones

[Helmut Grohne]

Hi,

I've spend the better part of today on this thanks to Freexian.

On Mon, Nov 20, 2023 at 12:35:58AM +0100, Helmut Grohne wrote:
> Different reproducer:
> 
> mmdebstrap trixie /dev/null http://deb.debian.org/debian 
> --include=systemd-sysv,molly-guard --customize-hook='sed -i -e s/trixie/sid/ 
> $1/etc/apt/sources.list' --chrooted-customize-hook='apt-get update' 
> --customize-hook='test -e $1/lib/molly-guard/reboot' 
> --chrooted-customize-hook='apt-get -y install systemd-sysv' 
> --customize-hook='ls -l $1/lib/molly-guard/'

> I've dug into dpkg and usually when it moves a file from / to /usr,
> it'll first unpack the new file (unknowingly replacing the existing old
> one) and then removes the old one (via pkg_remove_old_files). During
> that removal, it has a check to see whether the file to be removed
> happens to match one of the files it just installed and skips the
> removal in that case. For some reason, this safety check does not work
> when the file is diverted.

I retried this a few times and still think it is correct. As a
consequence, the original approach of duplicating diversions cannot work
at all. As soon as we have two diversions whose targets equal up to
aliasing, we run into this problem and to make matters worse, we are
loosing a file that we just unpacked. We have no way of keeping (and
later restoring) it via any kind of maintainer scripts. Therefore we
really cannot do the duplicate diversion approach. It was a nice idea,
but doesn't work. Back to the drawing board.

We still must have two diversions to as unpacking either of the
locations from another package would clobber the location we want
diverted. What changes is that the diversion targets must differ in more
than aliasing.

I think an example would help. Say we divert /sbin/halt. We must divert
both /sbin/halt and /usr/sbin/halt or we risk clobbering our copy. If we
divert the latter to /usr/lib/molly-guard/halt, we must not divert the
former to /lib/molly-guard/halt or the file will be lost in unpack. So
the later might become /lib/molly-guard/halt.usr-is-merged or something.

This is fairly inconvenient as molly-guard doesn't know about
halt.usr-is-merged. I think there is three possible ways to deal with
this:
 a) molly-guard tries both locations.
 b) We add a dpkg-trigger on /sbin/halt such that when
/usr/lib/molly-guard/halt is missing but
/lib/molly-guard/halt.usr-is-merged is not, we can add a symlink.
 c) We give up on supporting /sbin/halt (as opposed to /usr/sbin/halt)
and simply declare Breaks against any provider of /sbin/halt.

I argue that we should be selecting that last option, because /sbin/halt
is something that we want to go away entirely. When we release trixie,
we want all of them moved to /usr/sbin/halt. So we'd have versioned
Breaks for systemd-sysv, sysvinit-core, runit-init and finit-sysv. Note
that since Breaks does not prevent concurrent unpack, we must still
install the extra diversion. Note that since the other package must
declare Conflicts with molly-guard, molly-guard cannot use Conflicts
without impacting upgrades. The mutual conflict would require apt to
temporarily remove molly-guard (or /sbin/init!) and that is known to
impact upgrades.  Also note that since sysvinit-core and others have not
yet moved, molly-guard must now declare unversioned Breaks for all of
them for as long as they have not moved and once they moved, it can add
a version to the Breaks.

So I went ahead an implemented this. Since I didn't want to fall into my
trap of too little testing again, I wrote some test cases (attached) and
to my surprise found another problem!

/sbin/halt actually is a symbolic link to /bin/systemctl. In 255,
/usr/sbin/halt becomes a symlink to ../bin/systemctl. Observe how we
turned an absolute symlink into a relative once since we no longer
cross a toplevel directory in line with policy. As we move this relative
symlink to /usr/lib/molly-guard, it becomes a broken symbolic link. So
if you now install molly-guard and systemd-sysv in unstable, these links
are gone. You may then reinstall systemd-sysv and see them reinstated.
And now they're broken.

There is no easy way to fix this beyond moving these programs to a
different name in the same directory. I suggest
/usr/sbin/halt.no-molly-guard. Appending a suffix is what most
diversions do and this avoids breaking symlinks.

I've attached the prospective change to this mail. It passes piuparts
and it passes my own test cases. I definitely think it should be
reviewed before uploaded. One thing I already see for possible
improvement is that since we declare Breaks against all providers of
/sbin/halt, this diversion does not actually have to persist beyond
postinst. Once molly-guard is configured, we know that any broken
package is no longer installed nor unpacked. A molly-guard.postinst
could remove the diversion of /sbin/halt to
/sbin/halt.no-molly-guard.usr-is-merged. Then we are only left with one
diversion per command which also 

Processed: No longer affects ibus-table

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> affects 1051243 - ibus-table
Bug #1051243 [tex-common] tex-common: fmtutil failed on tex-common upgrade
Removed indication that 1051243 affects ibus-table
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
1051243: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051243
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: tagging 1055874, reassign 1056072 to wnpp, tagging 1056272, tagging 1051243, tagging 1056184 ...

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 1055874 + pending
Bug #1055874 {Done: Santiago Vila } 
[src:intel-graphics-compiler] intel-graphics-compiler: FTBFS in bookworm with 
intel-vc-intrinsics-dev 0.11
Added tag(s) pending.
> reassign 1056072 wnpp
Bug #1056072 [eww] RFP: eww A widget system written in Rust
Warning: Unknown package 'eww'
Bug reassigned from package 'eww' to 'wnpp'.
Ignoring request to alter found versions of bug #1056072 to the same values 
previously set
Ignoring request to alter fixed versions of bug #1056072 to the same values 
previously set
> tags 1056272 + sid trixie
Bug #1056272 [src:g3dviewer] RM: g3dviewer -- ROM; abandoned upstream; depends 
on gtk2
Added tag(s) sid and trixie.
> tags 1051243 + sid trixie
Bug #1051243 [tex-common] tex-common: fmtutil failed on tex-common upgrade
Added tag(s) trixie and sid.
> tags 1056184 + sid trixie
Bug #1056184 [src:python-ase] python-ase: FTBFS: ERROR: Broken link: 
:git:`COPYING`: Non-existing path: ../COPYING
Added tag(s) trixie and sid.
> tags 1054477 + sid trixie
Bug #1054477 {Done: Don Armstrong } [src:autorandr] autorandr: 
install autorandr.service twice once dh_installsystemd installs to /usr
Added tag(s) trixie and sid.
> found 1056014 3.1.2+dfsg-4
Bug #1056014 [src:cryptojs] cryptojs: Library no more maintained, please keep 
out of next Debian stable
Marked as found in versions cryptojs/3.1.2+dfsg-4.
> tags 1055980 + sid trixie
Bug #1055980 [src:pandoc-sidenote] pandoc-sidenote needs a source upload for 
ghc 9.4
Added tag(s) sid and trixie.
> tags 1054489 + sid trixie
Bug #1054489 [src:tarantool] tarantool: installs a systemd unit twice when 
dh_systemd_enable installs to /usr
Added tag(s) sid and trixie.
> tags 1054484 + sid trixie
Bug #1054484 [varnish] varnish: installs varnish.service twice once 
dh_installsystemd installs to /usr
Added tag(s) sid and trixie.
> tags 1054193 + sid trixie
Bug #1054193 [src:arpwatch] arpwatch: installs arpwatch@.service twice once 
dh_installsystemd installs to /usr
Added tag(s) sid and trixie.
> tags 1054190 + sid trixie
Bug #1054190 [src:arpon] arpon: installs arpon@.service twice once 
dh_installsystemd installs to /usr
Added tag(s) trixie and sid.
> tags 1055916 + sid trixie
Bug #1055916 [gedit] uninstallable in unstable
Added tag(s) sid and trixie.
> tags 1055877 - bookworm
Bug #1055877 [src:ndcube] ndcube: FTBFS in bookworm: leap-second file is expired
Removed tag(s) bookworm.
> notfound 1056292 255-rc2-1
Bug #1056292 [systemd-sysv] duplicated diversions are still broken by moved 
files
There is no source info for the package 'systemd-sysv' at version '255-rc2-1' 
with architecture ''
Unable to make a source version for version '255-rc2-1'
No longer marked as found in versions 255-rc2-1.
> found 1056292 255~rc2-1
Bug #1056292 [systemd-sysv] duplicated diversions are still broken by moved 
files
Marked as found in versions systemd/255~rc2-1.
> reassign 1038296 src:yubikey-manager 4.0.9-1
Bug #1038296 {Done: Dr. Tobias Quathamer } 
[python3-yubikey-manager] please drop transitional package 
python3-yubikey-manager from src:yubikey-manager
Bug reassigned from package 'python3-yubikey-manager' to 'src:yubikey-manager'.
No longer marked as found in versions yubikey-manager/4.0.9-1.
No longer marked as fixed in versions yubikey-manager/4.0.9-2.
Bug #1038296 {Done: Dr. Tobias Quathamer } 
[src:yubikey-manager] please drop transitional package python3-yubikey-manager 
from src:yubikey-manager
Marked as found in versions yubikey-manager/4.0.9-1.
> fixed 1038296 4.0.9-2
Bug #1038296 {Done: Dr. Tobias Quathamer } 
[src:yubikey-manager] please drop transitional package python3-yubikey-manager 
from src:yubikey-manager
Marked as fixed in versions yubikey-manager/4.0.9-2.
> reassign 1032643 src:cmigemo 1:1.2+gh0.20150404-8
Bug #1032643 {Done: Youhei SASAKI } [migemo-el] please 
drop transitional package migemo-el from src:cmigemo
Bug reassigned from package 'migemo-el' to 'src:cmigemo'.
No longer marked as found in versions cmigemo/1:1.2+gh0.20150404-8.
No longer marked as fixed in versions cmigemo/1:1.2+gh0.20220623-1.
Bug #1032643 {Done: Youhei SASAKI } [src:cmigemo] 
please drop transitional package migemo-el from src:cmigemo
Marked as found in versions cmigemo/1:1.2+gh0.20150404-8.
> fixed 1032643 1:1.2+gh0.20220623-1
Bug #1032643 {Done: Youhei SASAKI } [src:cmigemo] 
please drop transitional package migemo-el from src:cmigemo
Marked as fixed in versions cmigemo/1:1.2+gh0.20220623-1.
> tags 988090 - bookworm + experimental
Bug #988090 {Done: Jonathan Kamens } [src:apt-listchanges] 
planned removal of db5.3 will break python's dbm.ndbm and therefore 
apt-listchanges
Removed tag(s) bookworm.
Bug #988090 {Done: Jonathan Kamens } [src:apt-listchanges] 
planned removal of db5.3 will break python's dbm.ndbm and therefore 
apt-listchanges
Added tag(s) experimental.
> notfixed 874301 2.38.0-4.1
Bug #874301 {Done: Adrian Bunk } [src:libgtop2] libgtop2: 
FTBFS on kFreeBSD: strlcpy undefined
No l

Processed: severity of 1056283 is grave, found 1056283 in 15.4-3

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> # make it RC as it was fixed in DSA but no further updates will happen in 
> unstable
> severity 1056283 grave
Bug #1056283 [src:postgresql-15] postgresql-15: CVE-2023-5868 CVE-2023-5869 
CVE-2023-5870
Severity set to 'grave' from 'important'
> found 1056283 15.4-3
Bug #1056283 [src:postgresql-15] postgresql-15: CVE-2023-5868 CVE-2023-5869 
CVE-2023-5870
Marked as found in versions postgresql-15/15.4-3.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1056283: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056283
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Re: Bug#1056315: texlive-latex-base: lualatex - zlib library version does not match

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 texlive-binaries
Bug #1056315 [texlive-latex-base] texlive-latex-base: lualatex - zlib library 
version does not match
Bug reassigned from package 'texlive-latex-base' to 'texlive-binaries'.
No longer marked as found in versions texlive-base/2023.20231007-1.
Ignoring request to alter fixed versions of bug #1056315 to the same values 
previously set
> block -1 by 1056204
Bug #1056315 [texlive-binaries] texlive-latex-base: lualatex - zlib library 
version does not match
1056315 was not blocked by any bugs.
1056315 was not blocking any bugs.
Added blocking bug(s) of 1056315: 1056204
> severity -1 grave
Bug #1056315 [texlive-binaries] texlive-latex-base: lualatex - zlib library 
version does not match
Severity set to 'grave' from 'normal'
> forcemerge -1 1056183
Bug #1056315 [texlive-binaries] texlive-latex-base: lualatex - zlib library 
version does not match
Bug #1056315 [texlive-binaries] texlive-latex-base: lualatex - zlib library 
version does not match
Marked as fixed in versions texlive-bin/2023.20230311.66589-8.
Marked as found in versions texlive-bin/2023.20230311.66589-7.
Bug #1056183 [texlive-binaries] texlive-luatex: lualatex exits immediately due 
to new zlib
Bug #1056186 [texlive-binaries] texlive-binaries: zlib library mismatch
Bug #1056189 [texlive-binaries] luahbtex: PANIC: unprotected error in call to 
Lua API (zlib library version does not match - header: 1.2.13, library: 1.3)
Bug #1056210 [texlive-binaries] luatex panics with zlib 1.3
Bug #1056304 [texlive-binaries] lualatex needs to be rebuilt against zlib 1.3
Merged 1056183 1056186 1056189 1056210 1056304 1056315

-- 
1056183: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056183
1056186: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056186
1056189: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056189
1056210: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056210
1056304: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056304
1056315: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056315
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1054187: marked as done (dico: installs systemd units twice once dh_installsystemd installs to /usr)

[Debian Bug Tracking System]

Your message dated Mon, 20 Nov 2023 16:49:07 +
with message-id 
and subject line Bug#1054187: fixed in dico 2.11-4
has caused the Debian Bug report #1054187,
regarding dico: installs systemd units twice once dh_installsystemd installs to 
/usr
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1054187: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054187
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: dicod
Version: 2.11-3
Tags: patch
User: helm...@debian.org
Usertags: dep17m2

We want to change dh_installsystemd to install units to /usr to finalize
the /usr-merge transition via DEP17. When doing so, the dicod will
install some of its units twice. They'll be present in
/usr/lib/systemd/system (via dh_installsystemd) and in
/lib/systemd/system (via dh_install). Doing so is a policy violation.
I'm attaching a patch for your convenience. Once I upload debhelper,
this bug will become release-critical.

Helmut
diff -Nru dico-2.11/debian/changelog dico-2.11/debian/changelog
--- dico-2.11/debian/changelog  2023-06-30 05:52:24.0 +0200
+++ dico-2.11/debian/changelog  2023-10-18 15:00:02.0 +0200
@@ -1,3 +1,10 @@
+dico (2.11-3.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Install systemd units only once. (Closes: #-1)
+
+ -- Helmut Grohne   Wed, 18 Oct 2023 15:00:02 +0200
+
 dico (2.11-3) unstable; urgency=medium
 
   [ Debian Janitor ]
diff -Nru dico-2.11/debian/dicod.install dico-2.11/debian/dicod.install
--- dico-2.11/debian/dicod.install  2023-06-30 05:52:24.0 +0200
+++ dico-2.11/debian/dicod.install  2023-10-18 14:59:43.0 +0200
@@ -16,6 +16,4 @@
 usr/lib/*/dico/pcre.so
 usr/lib/*/dico/pam.so
 usr/lib/*/dico/metaphone2.so
-debian/dicod@.service lib/systemd/system/
-debian/dicod.socket lib/systemd/system/
 debian/xinetd/dicod etc/xinetd.d/
diff -Nru dico-2.11/debian/dicod.links dico-2.11/debian/dicod.links
--- dico-2.11/debian/dicod.links2023-06-30 05:52:24.0 +0200
+++ dico-2.11/debian/dicod.links2023-10-18 15:00:02.0 +0200
@@ -1,4 +1,3 @@
 usr/bin/dicodconfig usr/sbin/dictdconfig
 usr/share/man/man8/dicodconfig.8.gz usr/share/man/man8/dictdconfig.8.gz
 etc/init.d/dicod etc/init.d/dictd
-lib/systemd/system/dicod.service lib/systemd/system/dictd.service
diff -Nru dico-2.11/debian/rules dico-2.11/debian/rules
--- dico-2.11/debian/rules  2023-06-30 05:52:24.0 +0200
+++ dico-2.11/debian/rules  2023-10-18 15:00:02.0 +0200
@@ -47,3 +47,6 @@
 override_dh_auto_test:
mkdir -p $(TEST_HOME)
HOME=$(TEST_HOME) dh_auto_test || cat dicod/tests/testsuite.log
+
+execute_after_dh_installsystemd:
+   ln -s dicod.service debian/dicod/`test -e 
debian/dicod/lib/systemd/system/dicod.service || echo 
usr/`lib/systemd/system/dictd.service
--- End Message ---
--- Begin Message ---
Source: dico
Source-Version: 2.11-4
Done: Marc Dequènes (Duck) 

We believe that the bug you reported is fixed in the latest version of
dico, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1054...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Marc Dequènes (Duck)  (supplier of updated dico package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 21 Nov 2023 01:26:32 +0900
Source: dico
Architecture: source
Version: 2.11-4
Distribution: unstable
Urgency: medium
Maintainer: Ritesh Raj Sarraf 
Changed-By: Marc Dequènes (Duck) 
Closes: 1054187
Changes:
 dico (2.11-4) unstable; urgency=medium
 .
   * Install systemd units only once. (thanks Helmut Grohne)
 (Closes: #1054187)
Checksums-Sha1:
 4c9cf55cbe579967bfdda2487db106b5450aeb91 2901 dico_2.11-4.dsc
 99afc0eb2e890d5ec79bdce2cc79069d06edc23d 26952 dico_2.11-4.debian.tar.xz
 7a9e053a647b6c0d570abc786b9b4e54323cd918 12941 dico_2.11-4_amd64.buildinfo
Checksums-Sha256:
 3a4dc56d93bd7631fc2e68f3b3d53669cd11580de73c1583b884a9bf6052cebf 2901 
dico_2.11-4.dsc
 69b9a0425eef0972289f3b5ac852abdf76a7d265a076eb9fa4c5aa0219b10102 26952 
dico_2.11-4.debian.tar.xz
 025aa02442c87a80e770c647b8ec3569ca018e4a34bf1a8fc4dd800cacf7f68d 12941 
dico_2.11-4_amd64.buildinfo
File

Bug#1056313: [Pkg-utopia-maintainers] Bug#1056313: network-manager: breaks networking

[Michael Biebl]

Control: severity -1 normal
Control: block -1 1055067


Am 20.11.23 um 13:25 schrieb Vincent Lefevre:

On 2023-11-20 12:42:14 +0100, Vincent Lefevre wrote:

I suspect that nm-dhcp-helper has been added because it is now needed.
But it doesn't work due to the "Permission denied".


If I understand correctly, /usr/lib/NetworkManager/nm-dhcp-helper moved
to /usr/libexec/nm-dhcp-helper, but /etc/apparmor.d/sbin.dhclient from
isc-dhcp-client was not updated.

/etc/apparmor.d/sbin.dhclient still contains the old paths.


Please work together with the isc-dhcp-client maintainers to get this 
AppArmor config updated.

There is nothing that can be done in the network-manager package about this.



Shouldn't there be a "Breaks:" on isc-dhcp-client (<< 4.4.3-P1-4) in
order to ensure that the user also upgrades isc-dhcp-client or block
the upgrade until isc-dhcp-clients gets modified?


We could consider adding such a versioned Breaks, once a fixed version 
of isc-dhcp-client exists.


Given that network-manager by default no longer uses dhclient, and 
unversioned Breaks is not warranted.





OpenPGP_signature.asc
Description: OpenPGP digital signature

Processed (with 1 error): Re: [Pkg-utopia-maintainers] Bug#1056313: network-manager: breaks networking

[Debian Bug Tracking System]

Processing control commands:

> severity -1 normal
Bug #1056313 [network-manager] network-manager: breaks networking (Permission 
denied for the new /usr/libexec/nm-dhcp-helper)
Severity set to 'normal' from 'grave'
> block -1 1055067
Unknown command or malformed arguments to command.


-- 
1056313: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056313
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: limit source to awffull, tagging 1000027

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> limit source awffull
Limiting to bugs with field 'source' containing at least one of 'awffull'
Limit currently set to 'source':'awffull'

> tags 127 + pending
Bug #127 [src:awffull] awffull: depends on obsolete pcre3 library
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
127: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=127
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1052803: marked as done (golang-github-gosexy-gettext: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 8 github.com/gosexy/gettext returned exit code 1)

[Debian Bug Tracking System]

Your message dated Mon, 20 Nov 2023 20:34:00 +
with message-id 
and subject line Bug#1052803: fixed in golang-github-gosexy-gettext 
0~git20130221-2.2
has caused the Debian Bug report #1052803,
regarding golang-github-gosexy-gettext: FTBFS: dh_auto_test: error: cd 
obj-x86_64-linux-gnu && go test -vet=off -v -p 8 github.com/gosexy/gettext 
returned exit code 1
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1052803: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052803
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: golang-github-gosexy-gettext
Version: 0~git20130221-2.1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230925 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> LC_ALL=C.UTF-8 dh_auto_test
>   cd obj-x86_64-linux-gnu && go test -vet=off -v -p 8 
> github.com/gosexy/gettext
> === RUN   TestSpanishMexico
> Hello, world!
> gettext_test.go:45: Failed translation.
> An apple
> gettext_test.go:53: Failed translation.
> 3 apples
> gettext_test.go:61: Failed translation.
> Good morning
> gettext_test.go:69: Failed translation.
> Good bye!
> gettext_test.go:77: Failed translation.
> --- FAIL: TestSpanishMexico (0.00s)
> === RUN   TestGermanDeutschland
> Hello, world!
> gettext_test.go:95: Failed translation.
> An apple
> gettext_test.go:103: Failed translation.
> 3 apples
> gettext_test.go:111: Failed translation.
> Good morning
> gettext_test.go:119: Failed translation.
> Good bye!
> gettext_test.go:127: Failed translation.
> --- FAIL: TestGermanDeutschland (0.00s)
> FAIL
> FAIL  github.com/gosexy/gettext   0.005s
> FAIL
> dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 8 
> github.com/gosexy/gettext returned exit code 1


The full build log is available from:
http://qa-logs.debian.net/2023/09/25/golang-github-gosexy-gettext_0~git20130221-2.1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230925;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20230925&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: golang-github-gosexy-gettext
Source-Version: 0~git20130221-2.2
Done: Mathias Gibbens 

We believe that the bug you reported is fixed in the latest version of
golang-github-gosexy-gettext, which is due to be installed in the Debian FTP 
archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1052...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Mathias Gibbens  (supplier of updated 
golang-github-gosexy-gettext package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 10 Nov 2023 19:12:55 +
Source: golang-github-gosexy-gettext
Architecture: source
Version: 0~git20130221-2.2
Distribution: unstable
Urgency: medium
Maintainer: Steve Langasek 
Changed-By: Mathias Gibbens 
Closes: 1052803
Changes:
 golang-github-gosexy-gettext (0~git20130221-2.2) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Run tests with LC_ALL=en_US.utf8 (Closes: #1052803)
Checksums-Sha1:
 c57ea9ea7c2aea4e351e3fa8d5200f4405a9397b 2058 
golang-github-gosexy-gettext_0~git20130221-2.2.dsc
 20f0b527baa86ec18a17311690915d41c96169f5 4304 
golang-github-gosexy-gettext_0~git20130221.orig.tar.xz
 ad5233fc8cc8f3418b2593c296b6002967e17859 2824 
golang-github-gosexy-gettext_0~git20130221-2.2.debian.tar.xz
 b9ed3485e1d891e597787c2926d9cfa73b

Bug#1056189: marked as done (luahbtex: PANIC: unprotected error in call to Lua API (zlib library version does not match - header: 1.2.13, library: 1.3))

[Debian Bug Tracking System]

Your message dated Mon, 20 Nov 2023 22:22:59 +0100
with message-id 
and subject line Re: Bug#1056183: texlive-luatex: lualatex exits immediately 
due to new zlib
has caused the Debian Bug report #1056183,
regarding luahbtex: PANIC: unprotected error in call to Lua API (zlib library 
version does not match - header: 1.2.13, library: 1.3)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1056183: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056183
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: texlive-binaries
Version: 2023.20230311.66589-7
Severity: important
Affects: tex-common

Hello,

trying to install texlive-latex-base+texlive-plain-generic to fullfill a
build dependency resulted in:
8X--
Setting up tex-common (6.18) ...
Running mktexlsr. This may take some time... done.
Running updmap-sys. This may take some time... done.
Running mktexlsr /var/lib/texmf ... done.
Building format(s) --all.
This may take some time...
fmtutil failed. Output has been stored in
/tmp/fmtutil.VGYt4Mud
Please include this file if you report a bug.

dpkg: error processing package tex-common (--configure):
 installed tex-common package post-installation script subprocess returned 
error exit status 1
[...]
Errors were encountered while processing:
 tex-common
E: Sub-process /usr/bin/dpkg returned an error code (1)
8X--

/tmp/fmtutil.VGYt4Mud (attached) shows:
...
fmtutil [INFO]: --- remaking luahbtex with luahbtex
fmtutil: running `luahbtex -ini   -jobname=luahbtex -progname=luahbtex 
luatex.ini' ...
PANIC: unprotected error in call to Lua API (zlib library version does not 
match - header: 1.2.13, library: 1.3)
Aborted
...

I am submitting against texlive-binaries since it contains the failing
binary.

cu Andreas

##
minimal input file


##
other files

##
 List of ls-R files

lrwxrwxrwx 1 root root 31 Oct  8 20:00 /usr/share/texlive/texmf-dist/ls-R -> 
/var/lib/texmf/ls-R-TEXLIVEDIST
##
 Config files
-rw-r--r-- 1 root root 475 Nov 18 15:02 /etc/texmf/web2c/texmf.cnf
lrwxrwxrwx 1 root root 33 Oct  8 20:00 /usr/share/texmf/web2c/fmtutil.cnf -> 
/var/lib/texmf/fmtutil.cnf-DEBIAN
lrwxrwxrwx 1 root root 32 Oct  8 20:00 /usr/share/texmf/web2c/updmap.cfg -> 
/var/lib/texmf/updmap.cfg-DEBIAN
-rw-r--r-- 1 root root 2942 Nov 18 15:02 
/var/lib/texmf/tex/generic/config/language.dat
##
 Files in /etc/texmf/web2c/
total 8
-rw-r--r-- 1 root root 283 Apr  1  2019 mktex.cnf
-rw-r--r-- 1 root root 475 Nov 18 15:02 texmf.cnf
##
 md5sums of texmf.d
ca40c66f144b4bafc3e59a2dd32ecb9c  /etc/texmf/texmf.d/00debian.cnf

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

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

Versions of packages texlive-binaries depends on:
ii  libc6   2.37-12
ii  libcairo2   1.18.0-1
ii  libfontconfig1  2.14.2-6
ii  libfreetype62.13.2+dfsg-1
ii  libgcc-s1   13.2.0-6
ii  libgraphite2-3  1.3.14-1
ii  libharfbuzz0b   8.0.1-1
ii  libicu7272.1-4
ii  libkpathsea62023.20230311.66589-7
ii  libmpfr64.2.1-1
ii  libpaper1   1.1.29
ii  libpixman-1-0   0.42.2-1
ii  libpng16-16 1.6.40-2
ii  libpotrace0 1.16-2
ii  libptexenc1 2023.20230311.66589-7
ii  libstdc++6  13.2.0-6
ii  libsynctex2 2023.20230311.66589-7
ii  libteckit0  2.5.11+ds1-1+b1
ii  libtexlua53-5   2023.20230311.66589-7
ii  libx11-62:1.8.7-1
ii  libxaw7 2:1.0.14-1
ii  libxi6  2:1.8-1+b1
ii  libxmu6 2:1.1.3-3
ii  libxpm4 1:3.5.17-1
ii  libxt6  1:1.2.1-1.1
ii  libzzip-0-130.13.72+dfsg.1-1.1
ii  perl5.36.0-9
ii  t1utils 1.41-4
ih  tex-common  6.18
ii  zlib1g  1:1.3.dfsg-2

Versions of packages texlive-binaries recommends:
pn  dvisvgm   
ii  texlive-base  2023.20231007-1

Versions of packages texlive-binaries suggests:
pn  hintview   
pn  texlive-binaries-sse2  

Versions of packages tex-common depends on:
ii  ucf  3.0043+nmu1

Versions of packages tex-common suggests:
ii  debhelper  13.11.8

Versions of packages texlive-binaries is related to:
ih  tex-common6.18
ii  texlive-base  202

Bug#1056210: marked as done (luatex panics with zlib 1.3)

[Debian Bug Tracking System]

Your message dated Mon, 20 Nov 2023 22:22:59 +0100
with message-id 
and subject line Re: Bug#1056183: texlive-luatex: lualatex exits immediately 
due to new zlib
has caused the Debian Bug report #1056183,
regarding luatex panics with zlib 1.3
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1056183: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056183
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: texlive-binaries
Version: 2023.20230311.66589-7

The luatex binary shipped with texlive is not compatible with zlib 1.3 
(zlib1g 1:1.3.dfsg-2 on Debian Sid).


$ luatex
PANIC: unprotected error in call to Lua API (zlib library version does 
not match - header: 1.2.13, library: 1.3)

Aborted
$

This bug has also been reported on the Arch Linux forum:

https://bugs.archlinux.org/task/79470

I am using Debian GNU/Linux trixie/sid (up to date) with the Linux 
6.5.0-4-amd64 kernel.


Regards,
François Rozet.
--- End Message ---
--- Begin Message ---

On 18.11.2023 11:48, Nick Black (Public gmail account) wrote:

Package: texlive-luatex
Version: 2023.20231007-1
Severity: important
X-Debbugs-Cc: dankamong...@gmail.com

Dear Maintainer,

Forcemerge did not work as expected. Instead of closing one bug, 5 were 
re-opened. Re-close.


H.
--
sigfault



OpenPGP_signature.asc
Description: OpenPGP digital signature
--- End Message ---

Bug#1056186: marked as done (texlive-binaries: zlib library mismatch)

[Debian Bug Tracking System]

Your message dated Mon, 20 Nov 2023 22:22:59 +0100
with message-id 
and subject line Re: Bug#1056183: texlive-luatex: lualatex exits immediately 
due to new zlib
has caused the Debian Bug report #1056183,
regarding texlive-binaries: zlib library mismatch
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1056183: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056183
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: texlive-binaries
Version: 2023.20230311.66589-7
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: calcu...@rezozer.net

Hi, the issue appeared to me within a Sid schroot environment 
at postinstallation time of tex-common.
I traced it back to texlive-binaries by looking the logfile at
the fmutils stage. The issue seems to originate from the recent migration
from zlib 1.2.13 to zlib 1.3. For short, the following command-line

  $ luatex -ini -jobname=luatex -progname=luatex luatex.ini

gives

  PANIC: unprotected error in call to Lua API (zlib library version does not 
match - header: 1.2.13, library: 1.3)
  aborted

Best wishes,
Jerome


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

Kernel: Linux 6.1.0-0.deb11.6-amd64 (SMP w/12 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: unable to detect

Versions of packages texlive-binaries depends on:
ii  libc6   2.37-12
ii  libcairo2   1.18.0-1
ii  libfontconfig1  2.14.2-6
ii  libfreetype62.13.2+dfsg-1
ii  libgcc-s1   13.2.0-6
ii  libgraphite2-3  1.3.14-1
ii  libharfbuzz0b   8.0.1-1
ii  libicu7272.1-4
ii  libkpathsea62023.20230311.66589-7
ii  libmpfr64.2.1-1
ii  libpaper1   1.1.29
ii  libpixman-1-0   0.42.2-1
ii  libpng16-16 1.6.40-2
ii  libpotrace0 1.16-2
ii  libptexenc1 2023.20230311.66589-7
ii  libstdc++6  13.2.0-6
ii  libsynctex2 2023.20230311.66589-7
ii  libteckit0  2.5.11+ds1-1+b1
ii  libtexlua53-5   2023.20230311.66589-7
ii  libx11-62:1.8.7-1
ii  libxaw7 2:1.0.14-1
ii  libxi6  2:1.8-1+b1
ii  libxmu6 2:1.1.3-3
ii  libxpm4 1:3.5.17-1
ii  libxt6  1:1.2.1-1.1
ii  libzzip-0-130.13.72+dfsg.1-1.1
ii  perl5.36.0-9
ii  t1utils 1.41-4
ih  tex-common  6.18
ii  zlib1g  1:1.3.dfsg-2

Versions of packages texlive-binaries recommends:
pn  dvisvgm   
ii  texlive-base  2023.20231007-1

Versions of packages texlive-binaries suggests:
pn  hintview   
pn  texlive-binaries-sse2  

Versions of packages tex-common depends on:
ii  ucf  3.0043+nmu1

Versions of packages tex-common suggests:
ii  debhelper  13.11.8

Versions of packages texlive-binaries is related to:
ih  tex-common6.18
ii  texlive-base  2023.20231007-1

-- no debconf information
--- End Message ---
--- Begin Message ---

On 18.11.2023 11:48, Nick Black (Public gmail account) wrote:

Package: texlive-luatex
Version: 2023.20231007-1
Severity: important
X-Debbugs-Cc: dankamong...@gmail.com

Dear Maintainer,

Forcemerge did not work as expected. Instead of closing one bug, 5 were 
re-opened. Re-close.


H.
--
sigfault



OpenPGP_signature.asc
Description: OpenPGP digital signature
--- End Message ---

Bug#1056183: marked as done (texlive-luatex: lualatex exits immediately due to new zlib)

[Debian Bug Tracking System]

Your message dated Mon, 20 Nov 2023 22:22:59 +0100
with message-id 
and subject line Re: Bug#1056183: texlive-luatex: lualatex exits immediately 
due to new zlib
has caused the Debian Bug report #1056183,
regarding texlive-luatex: lualatex exits immediately due to new zlib
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1056183: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056183
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: texlive-luatex
Version: 2023.20231007-1
Severity: important
X-Debbugs-Cc: dankamong...@gmail.com

Dear Maintainer,

I recently updated zlib1g:amd64 (1:1.2.13.dfsg-3, 1:1.3.dfsg-2) in unstable.

lualatex immediately stopped working, with the error:

[schwarzgerat](0) $ lualatex
PANIC: unprotected error in call to Lua API (zlib library version does not
match - header: 1.2.13, library: 1.3)
Aborted (core dumped)
[schwarzgerat](134) $

Should just need a rebuild, but perhaps this (unnecessary?) check ought be
removed? Isn't this what SOVERSIONs are for?


-- Package-specific info:
IMPORTANT INFORMATION: We will only consider bug reports concerning
the packaging of TeX Live as relevant. If you have problems with
combination of packages in a LaTeX document, please consult your
local TeX User Group, the comp.text.tex user group, the author of
the original .sty file, or any other help resource. 

In particular, bugs that are related to up-upstream, i.e., neither
Debian nor TeX Live (upstream), but the original package authors,
will be closed immediately.

   *** The Debian TeX Team is *not* a LaTeX Help Desk ***

If you report an error when running one of the TeX-related binaries 
(latex, pdftex, metafont,...), or if the bug is related to bad or wrong
output, please include a MINIMAL example input file that produces the
error in your report.

Please run your example with
(pdf)latex -recorder ...
(or any other program that supports -recorder) and send us the generated
file with the extension .fls, it lists all the files loaded during
the run and can easily explain problems induced by outdated files in
your home directory.

Don't forget to also include minimal examples of other files that are 
needed, e.g. bibtex databases. Often it also helps
to include the logfile. Please, never send included pictures!

If your example file isn't short or produces more than one page of
output (except when multiple pages are needed to show the problem),
you can probably minimize it further. Instructions on how to do that
can be found at

http://www.minimalbeispiel.de/mini-en.html (english)

or 

http://www.minimalbeispiel.de/mini.html (german)

##
minimal input file


##
other files

##
 List of ls-R files

-rw-r--r-- 1 root root 2496 2023-11-10 04:56 /var/lib/texmf/ls-R
lrwxrwxrwx 1 root root 29 2022-10-12 17:25 /usr/share/texmf/ls-R -> 
/var/lib/texmf/ls-R-TEXMFMAIN
lrwxrwxrwx 1 root root 31 2023-10-08 16:00 /usr/share/texlive/texmf-dist/ls-R 
-> /var/lib/texmf/ls-R-TEXLIVEDIST
lrwxrwxrwx 1 root root 31 2023-10-08 16:00 /usr/share/texlive/texmf-dist/ls-R 
-> /var/lib/texmf/ls-R-TEXLIVEDIST
##
 Config files
-rw-r--r-- 1 root root 475 2023-08-28 14:30 /etc/texmf/web2c/texmf.cnf
lrwxrwxrwx 1 root root 33 2023-10-08 16:00 /usr/share/texmf/web2c/fmtutil.cnf 
-> /var/lib/texmf/fmtutil.cnf-DEBIAN
lrwxrwxrwx 1 root root 32 2023-10-08 16:00 /usr/share/texmf/web2c/updmap.cfg -> 
/var/lib/texmf/updmap.cfg-DEBIAN
-rw-r--r-- 1 root root 5289 2023-11-10 04:54 
/var/lib/texmf/tex/generic/config/language.dat
##
 Files in /etc/texmf/web2c/
total 8
-rw-r--r-- 1 root root 283 2016-02-22 09:54 mktex.cnf
-rw-r--r-- 1 root root 475 2023-08-28 14:30 texmf.cnf
##
 md5sums of texmf.d
ca40c66f144b4bafc3e59a2dd32ecb9c  /etc/texmf/texmf.d/00debian.cnf

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

Kernel: Linux 6.5.9nlb2 (SMP w/64 CPU threads)
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)

Versions of packages texlive-luatex depends on:
ii  libjs-jquery  3.6.1+dfsg+~3.5.14-1
ii  lmodern   2.005-1
ii  tex-common6.18
ii  texlive-base 

Bug#1056304: marked as done (lualatex needs to be rebuilt against zlib 1.3)

[Debian Bug Tracking System]

Your message dated Mon, 20 Nov 2023 22:22:59 +0100
with message-id 
and subject line Re: Bug#1056183: texlive-luatex: lualatex exits immediately 
due to new zlib
has caused the Debian Bug report #1056183,
regarding lualatex needs to be rebuilt against zlib 1.3
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1056183: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056183
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: texlive-latex-base
Version: 2023.20231007-1
Severity: important

% lualatex
PANIC: unprotected error in call to Lua API (zlib library version does not 
match - header: 1.2.13, library: 1.3)
zsh: IOT instruction  lualatex
% lualatex --credits
This is LuaHBTeX, Version 1.17.0 (TeX Live 2023/Debian)

The LuaTeX team is Hans Hagen, Hartmut Henkel, Taco Hoekwater, Luigi Scarso.

LuaHBTeX merges and builds upon (parts of) the code from these projects:

tex   : Donald Knuth
etex  : Peter Breitenlohner, Phil Taylor and friends
omega : John Plaice and Yannis Haralambous
aleph : Giuseppe Bilotta
pdftex: Han The Thanh and friends
kpathsea  : Karl Berry, Olaf Weber and others
lua   : Roberto Ierusalimschy, Waldemar Celes and Luiz Henrique de 
Figueiredo
metapost  : John Hobby, Taco Hoekwater, Luigi Scarso, Hans Hagen and friends
pplib : Paweł Jackowski
fontforge : George Williams (partial)
luajit: Mike Pall (used in LuajitTeX)

Compiled with libharfbuzz 8.0.1; using 8.0.1
Compiled with libpng 1.6.40; using 1.6.40
Compiled with lua version 5.3.6
Compiled with mplib version 2.02
Compiled with zlib 1.2.13; using 1.3

Development id: 7581



Packages zlib1g and zlib1g-dev are at version 1.3.dfsg-2 (from unstable).
--- End Message ---
--- Begin Message ---

On 18.11.2023 11:48, Nick Black (Public gmail account) wrote:

Package: texlive-luatex
Version: 2023.20231007-1
Severity: important
X-Debbugs-Cc: dankamong...@gmail.com

Dear Maintainer,

Forcemerge did not work as expected. Instead of closing one bug, 5 were 
re-opened. Re-close.


H.
--
sigfault



OpenPGP_signature.asc
Description: OpenPGP digital signature
--- End Message ---

Bug#1056315: marked as done (texlive-latex-base: lualatex - zlib library version does not match)

[Debian Bug Tracking System]

Your message dated Mon, 20 Nov 2023 22:22:59 +0100
with message-id 
and subject line Re: Bug#1056183: texlive-luatex: lualatex exits immediately 
due to new zlib
has caused the Debian Bug report #1056183,
regarding texlive-latex-base: lualatex - zlib library version does not match
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1056183: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056183
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: texlive-latex-base
Version: 2023.20231007-1
Severity: normal

Dear Maintainer,

When trying to compile a Latex file with lualatex, lualatex fails immediately
with the following messages:

"""
> lualatex toto.tex
PANIC: unprotected error in call to Lua API (zlib library version does not
match - header: 1.2.13, library: 1.3)
zsh: IOT instruction (core dumped)  lualatex toto.tex
"""

zlib1g is indeed at the version 1.3 in sid.
(zlib1g is at 1.2.13 in testing/stable)



-- Package-specific info:
IMPORTANT INFORMATION: We will only consider bug reports concerning
the packaging of TeX Live as relevant. If you have problems with
combination of packages in a LaTeX document, please consult your
local TeX User Group, the comp.text.tex user group, the author of
the original .sty file, or any other help resource. 

In particular, bugs that are related to up-upstream, i.e., neither
Debian nor TeX Live (upstream), but the original package authors,
will be closed immediately.

   *** The Debian TeX Team is *not* a LaTeX Help Desk ***

If you report an error when running one of the TeX-related binaries 
(latex, pdftex, metafont,...), or if the bug is related to bad or wrong
output, please include a MINIMAL example input file that produces the
error in your report.

Please run your example with
(pdf)latex -recorder ...
(or any other program that supports -recorder) and send us the generated
file with the extension .fls, it lists all the files loaded during
the run and can easily explain problems induced by outdated files in
your home directory.

Don't forget to also include minimal examples of other files that are 
needed, e.g. bibtex databases. Often it also helps
to include the logfile. Please, never send included pictures!

If your example file isn't short or produces more than one page of
output (except when multiple pages are needed to show the problem),
you can probably minimize it further. Instructions on how to do that
can be found at

http://www.minimalbeispiel.de/mini-en.html (english)

or 

http://www.minimalbeispiel.de/mini.html (german)

##
minimal input file


##
other files

##
 List of ls-R files

-rw-rw-r-- 1 root staff 80 Apr  8  2020 /usr/local/share/texmf/ls-R
-rw-r--r-- 1 root root 3471 Nov 20 10:35 /var/lib/texmf/ls-R
lrwxrwxrwx 1 root root 29 Oct 12  2022 /usr/share/texmf/ls-R -> 
/var/lib/texmf/ls-R-TEXMFMAIN
lrwxrwxrwx 1 root root 31 Oct  8 22:00 /usr/share/texlive/texmf-dist/ls-R -> 
/var/lib/texmf/ls-R-TEXLIVEDIST
lrwxrwxrwx 1 root root 31 Oct  8 22:00 /usr/share/texlive/texmf-dist/ls-R -> 
/var/lib/texmf/ls-R-TEXLIVEDIST
##
 Config files
-rw-r--r-- 1 root root 475 Oct 13  2022 /etc/texmf/web2c/texmf.cnf
lrwxrwxrwx 1 root root 33 Oct  8 22:00 /usr/share/texmf/web2c/fmtutil.cnf -> 
/var/lib/texmf/fmtutil.cnf-DEBIAN
lrwxrwxrwx 1 root root 32 Oct  8 22:00 /usr/share/texmf/web2c/updmap.cfg -> 
/var/lib/texmf/updmap.cfg-DEBIAN
-rw-r--r-- 1 root root 3430 Nov 10 10:00 
/var/lib/texmf/tex/generic/config/language.dat
##
 Files in /etc/texmf/web2c/
total 8
-rw-r--r-- 1 root root 283 Sep  4  2021 mktex.cnf
-rw-r--r-- 1 root root 475 Oct 13  2022 texmf.cnf
##
 md5sums of texmf.d
ca40c66f144b4bafc3e59a2dd32ecb9c  /etc/texmf/texmf.d/00debian.cnf

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

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

Versions of packages texlive-latex-base depends on:
ii  fonts-lmodern 2.005-1
ii  tex-common6.18
ii  texlive-base  2023.20231007-1
ii  texlive-binaries  2023.20230311.66589-7

texlive-latex-base recommends no package

Bug#1056292: marked as pending in systemd

[Luca Boccassi]

Control: tag -1 pending

Hello,

Bug #1056292 in systemd reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/systemd-team/systemd/-/commit/0dc66cb2c6c2837460518fc7f89968ba2de10f9f


Bump conflict with molly-guard to 0.8.2

The previous workarounds are not enough, so a new upload will be
needed.

Closes: #1056292


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1056292

Processed: Bug#1056292 marked as pending in systemd

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1056292 [systemd-sysv] duplicated diversions are still broken by moved 
files
Added tag(s) pending.

-- 
1056292: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056292
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1051243: texlive-binaries -8 version fixed the problem

[Friedrich Beckmann]

The problem is gone with the -8 release of texlive-binaries.

Thanks!!!

Bug#1056292: marked as done (duplicated diversions are still broken by moved files)

[Debian Bug Tracking System]

Your message dated Mon, 20 Nov 2023 23:05:23 +
with message-id 
and subject line Bug#1056292: fixed in systemd 255~rc2-3
has caused the Debian Bug report #1056292,
regarding duplicated diversions are still broken by moved files
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1056292: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056292
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: molly-guard
Version: 0.8.1
Severity: grave
X-Debbugs-Cc: debian.a...@manchmal.in-ulm.de

Greetings,

after upgrading from 0.7.2 to 0.8.1, the symlinks in /usr/lib/molly-guard/
are gone. As this happened on a second machine today, I reckon it's not
a coincidence.


Current state:

# ls -l /usr/lib/molly-guard/
total 8
-rwxr-xr-x 1 root root   99  5. Okt 00:17 coldreboot
-rwxr-xr-x 1 root root 3365 11. Nov 23:02 molly-guard


Old state:

# ls -l /usr/lib/molly-guard/
total 7
-rwxr-xr-x 1 root root   99  5. Okt 00:17 coldreboot
lrwxrwxrwx 1 root root   14 30. Sep 12:34 halt -> /bin/systemctl
-rwxr-xr-x 1 root root 2847  9. Jul 2019  molly-guard
lrwxrwxrwx 1 root root   14 30. Sep 12:34 poweroff -> /bin/systemctl
lrwxrwxrwx 1 root root   14 30. Sep 12:34 reboot -> /bin/systemctl
lrwxrwxrwx 1 root root   14 30. Sep 12:34 shutdown -> /bin/systemctl


This is the upgrade log:

Preparing to unpack .../molly-guard_0.8.1_all.deb ...
No diversion 'diversion of /sbin/pm-hibernate by molly-guard', none removed.
No diversion 'diversion of /sbin/pm-suspend by molly-guard', none removed.
No diversion 'diversion of /sbin/pm-suspend-hybrid by molly-guard', none 
removed.
Adding 'diversion of /usr/sbin/halt to /usr/lib/molly-guard/halt by molly-guard'
Leaving 'diversion of /sbin/halt to /lib/molly-guard/halt by molly-guard'
Adding 'diversion of /usr/sbin/poweroff to /usr/lib/molly-guard/poweroff by 
molly-guard'
Leaving 'diversion of /sbin/poweroff to /lib/molly-guard/poweroff by 
molly-guard'
Adding 'diversion of /usr/sbin/reboot to /usr/lib/molly-guard/reboot by 
molly-guard'
Leaving 'diversion of /sbin/reboot to /lib/molly-guard/reboot by molly-guard'
Adding 'diversion of /usr/sbin/shutdown to /usr/lib/molly-guard/shutdown by 
molly-guard'
Leaving 'diversion of /sbin/shutdown to /lib/molly-guard/shutdown by 
molly-guard'
Adding 'diversion of /usr/sbin/coldreboot to /usr/lib/molly-guard/coldreboot by 
molly-guard'
Leaving 'diversion of /sbin/coldreboot to /lib/molly-guard/coldreboot by 
molly-guard'
Removing 'diversion of /usr/sbin/pm-hibernate to /lib/molly-guard/pm-hibernate 
by molly-guard'
Adding 'diversion of /usr/sbin/pm-hibernate to 
/usr/lib/molly-guard/pm-hibernate by molly-guard'
Removing 'diversion of /usr/sbin/pm-suspend to /lib/molly-guard/pm-suspend by 
molly-guard'
Adding 'diversion of /usr/sbin/pm-suspend to /usr/lib/molly-guard/pm-suspend by 
molly-guard'
Removing 'diversion of /usr/sbin/pm-suspend-hybrid to 
/lib/molly-guard/pm-suspend-hybrid by molly-guard'
Adding 'diversion of /usr/sbin/pm-suspend-hybrid to 
/usr/lib/molly-guard/pm-suspend-hybrid by molly-guard'
Unpacking molly-guard (0.8.1) over (0.7.2) ...
dpkg: warning: unable to delete old directory '/lib/molly-guard': Directory not 
empty
Setting up molly-guard (0.8.1) ...


The resultat is a major problem, hence the severity: Trying to shut down
or reboot just triggers an error:

# shutdown -P
E: not a regular file: /usr/lib/molly-guard/shutdown

(Workaround: Manually restore the links.)

Looking into the maintainer scripts, I see some changes were done. Can
you please re-check they to the right thing?

Regards,

Chri- "diversions are a nightmare" stoph


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: systemd
Source-Version: 255~rc2-3
Done: Luca Boccassi 

We believe that the bug you reported is fixed in the latest version of
systemd, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1056...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Luca Boccassi  (supplier of updated systemd package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 20 Nov 2023 20:58:27 +
Source: systemd
Architecture: so

Bug#1043419: raising missing trigger interest to serious

[Lorenzo]

Hi Helmut,

On Sat, 18 Nov 2023 17:40:23 +0100 Helmut Grohne 
wrote:

First the actionable part:

> Is there actually any issue with promoting the change from
> experimental to unstable?
Yes: the version in experimental is definitely RC buggy, for reasons
unrelated to usrmerge

> If you lack a sponsor, I am willing to help
> out once to get this fixed.
Thanks, really appreciated:
I prepared a runit_2.1.2-54+usrmerge runit upload targeted at unstable
with two commits backported, you can find it on mentors

https://mentors.debian.net/package/runit/
dget -x
https://mentors.debian.net/debian/pool/main/r/runit/runit_2.1.2-54+usrmerge.dsc

and on salsa (usrmerge branch)
https://salsa.debian.org/debian/runit/-/tree/usrmerge?ref_type=heads

let me know if something else is needed for this upload.

Now the annoying part:

> it still affects
> trixie and sid, so by raising it to serious, we get rid of the bug in
> trixie before too long (either via upload or autoremove).

> [...] However, runit's triggers do
> not work anymore. That's a serious bug and we're tracking it like
> that.

I disagree about the severity (it should be assessed by looking at
the broken feature that is provided by the trigger) and especially I
disagree that the malfunction of this specific feature should cause the
removal of runit from testing (and the same goes for any other
alternative init system).
I'm stopping here as I think you don't want to spend further time on
this bug since it can be fixed with an upload, but I can elaborate if
you want me to.

Best Regards,
Lorenzo

> 
> Helmut
> 
> 
> 

Bug#1055136: marked as done (nvidia-graphics-drivers: CVE-2023-31022)

[Debian Bug Tracking System]

Your message dated Tue, 21 Nov 2023 02:34:44 +
with message-id 
and subject line Bug#1055136: fixed in nvidia-graphics-drivers 525.147.05-1
has caused the Debian Bug report #1055136,
regarding nvidia-graphics-drivers: CVE-2023-31022
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1055136: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055136
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nvidia-graphics-drivers
Severity: normal
Tags: security
X-Debbugs-Cc: Debian Security Team 
Control: clone -1 -2 -3 -4 -5 -6 -7 -8 -9
Control: reassign -2 src:nvidia-graphics-drivers-legacy-340xx 340.76-6
Control: retitle -2 nvidia-graphics-drivers-legacy-340xx: CVE-2023-31022
Control: tag -2 + wontfix
Control: reassign -3 src:nvidia-graphics-drivers-legacy-390xx 390.48-4
Control: retitle -3 nvidia-graphics-drivers-legacy-390xx: CVE-2023-31022
Control: tag -3 + wontfix
Control: reassign -4 src:nvidia-graphics-drivers-tesla-418 418.87.01-1
Control: retitle -4 nvidia-graphics-drivers-tesla-418: CVE-2023-31022
Control: tag -4 + wontfix
Control: reassign -5 src:nvidia-graphics-drivers-tesla-450 450.51.05-1
Control: retitle -5 nvidia-graphics-drivers-tesla-450: CVE-2023-31022
Control: tag -5 + wontfix
Control: reassign -6 src:nvidia-graphics-drivers-tesla-460 460.32.03-1
Control: retitle -6 nvidia-graphics-drivers-tesla-460: CVE-2023-31022
Control: tag -6 + wontfix
Control: close -6 460.106.00-3
Control: reassign -7 src:nvidia-graphics-drivers-tesla-470 470.57.02-1
Control: retitle -7 nvidia-graphics-drivers-tesla-470: CVE-2023-31022
Control: reassign -8 src:nvidia-graphics-drivers-tesla 510.85.02-1
Control: retitle -8 nvidia-graphics-drivers-tesla: CVE-2023-31022
Control: found -8 515.48.07-1
Control: found -8 525.60.13-1
Control: found -8 535.54.03-1
Control: reassign -9 src:nvidia-open-gpu-kernel-modules 515.43.04-1
Control: retitle -9 nvidia-open-gpu-kernel-modules: CVE-2023-31022
Control: found -9 520.56.06-1
Control: found -9 525.85.12-1
Control: found -9 530.30.02-1
Control: found -9 535.43.02-1
Control: found -9 545.23.06-1
Control: found -1 340.24-1
Control: found -1 343.22-1
Control: found -1 396.18-1
Control: found -1 430.14-1
Control: found -1 455.23.04-1
Control: found -1 465.24.02-1
Control: found -1 495.44-1
Control: found -1 515.48.07-1
Control: found -1 520.56.06-1
Control: found -1 525.53-1
Control: found -1 530.30.02-1
Control: found -1 535.43.02-1
Control: found -1 545.23.06-1

https://nvidia.custhelp.com/app/answers/detail/a_id/5491

CVE-2023-31022  NVIDIA GPU Display Driver for Windows and Linux contains
a vulnerability in the kernel mode layer, where a NULL-pointer
dereference may lead to denial of service.

Linux Driver Branch CVE IDs Addressed
R545, R535, R525, R470  CVE-2023-31022

Driver Branch   Affected Driver VersionsUpdated Driver 
Version
R545All driver versions prior to 545.29.02  545.29.02
R535All driver versions prior to 535.129.03 535.129.03
R525All driver versions prior to 525.147.05 525.147.05
R470All driver versions prior to 470.223.02 470.223.02


Andreas
--- End Message ---
--- Begin Message ---
Source: nvidia-graphics-drivers
Source-Version: 525.147.05-1
Done: Andreas Beckmann 

We believe that the bug you reported is fixed in the latest version of
nvidia-graphics-drivers, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1055...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Andreas Beckmann  (supplier of updated nvidia-graphics-drivers 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 21 Nov 2023 02:33:52 +0100
Source: nvidia-graphics-drivers
Architecture: source
Version: 525.147.05-1
Distribution: unstable
Urgency: medium
Maintainer: Debian NVIDIA Maintainers 
Changed-By: Andreas Beckmann 
Closes: 1055136
Changes:
 nvidia-graphics-drivers (525.147.05-1) unstable; urgency=medium
 .
   * New upstream production branch release 525.147.05 (2023-10-31).
 * Fixed CVE-2023-31022.  (Closes: #1055136)
   https://nvidia.custhelp.com/app/answers/d

Bug#1056286: marked as pending in node-get-stream

[Yadd]

Control: tag -1 pending

Hello,

Bug #1056286 in node-get-stream reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/js-team/node-get-stream/-/commit/13e93e0f85787ef76a4f89c0bc802fb896b86945


Drop Internet test

Closes: #1056286


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1056286

Processed: Bug#1056286 marked as pending in node-get-stream

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1056286 [node-get-stream] node-get-stream: FTBFS in sid with internet 
access disabled
Added tag(s) pending.

-- 
1056286: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056286
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1056286: marked as done (node-get-stream: FTBFS in sid with internet access disabled)

[Debian Bug Tracking System]

Your message dated Tue, 21 Nov 2023 04:50:05 +
with message-id 
and subject line Bug#1056286: fixed in node-get-stream 8.0.1-9
has caused the Debian Bug report #1056286,
regarding node-get-stream: FTBFS in sid with internet access disabled
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1056286: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056286
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: node-get-stream
Version: 8.0.1-8
Severity: serious
Tags: patch

Hello,

looks like the package is using internet during tests, and so FTBFS without 
internet access.

The log is:

  ✔ string › handles truncated UTF-8 sequences over maxBuffer
  ✔ string › get stream with invalid UTF-8 sequences
  ─

  integration › works with fetch()

  Rejected promise returned by test. Reason:

  TypeError {
cause: Error {
  code: 'ENOTFOUND',
  errno: -3008,
  hostname: 'nodejs.org',
  syscall: 'getaddrinfo',
  message: 'getaddrinfo ENOTFOUND nodejs.org',
},
message: 'fetch failed',
  }

  › async file://test/integration.js:66:18

  ─

  1 test failed
dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1


Can you please have a look?

thanks

G.
--- End Message ---
--- Begin Message ---
Source: node-get-stream
Source-Version: 8.0.1-9
Done: Yadd 

We believe that the bug you reported is fixed in the latest version of
node-get-stream, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1056...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Yadd  (supplier of updated node-get-stream package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 21 Nov 2023 07:13:06 +0400
Source: node-get-stream
Architecture: source
Version: 8.0.1-9
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Yadd 
Closes: 1056286
Changes:
 node-get-stream (8.0.1-9) unstable; urgency=medium
 .
   * Team upload
   * Drop Internet test (Closes: #1056286)
Checksums-Sha1: 
 c861f8d1ee2c909e2b6f938aa97e75a8ee84d4e7 2140 node-get-stream_8.0.1-9.dsc
 f858394b57b349b3242e337c49a38e2b66331e38 5996 
node-get-stream_8.0.1-9.debian.tar.xz
Checksums-Sha256: 
 00894d39eed05a308b73e88aa9866c1b8d68a7488f8b3fd9db4fc26a94b114dc 2140 
node-get-stream_8.0.1-9.dsc
 f29c3db2e6bdbe668b86fe18a307292292713499781c2740cc70325410117727 5996 
node-get-stream_8.0.1-9.debian.tar.xz
Files: 
 f54f4b31bf2cfbd11a3eb11819bc8f42 2140 javascript optional 
node-get-stream_8.0.1-9.dsc
 a10aff2ef7b8296d971c62f6aea3b5a6 5996 javascript optional 
node-get-stream_8.0.1-9.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAmVcMhEACgkQ9tdMp8mZ
7unSzw//Q9+gASczo9WrVCCHHap8qTJWPryE4Ds3mtjPvNpdn7pjplZnJMwhajBx
57/FhugtEVY5I/chohhfWHchaWzhOCDws+Fa1bDUXAXji6QkD136fa5OCY3EkEfl
Z2Djow9NwyBDRo92QYdGTZ4nKndUNIbgLOZJ9B2iTInGdA62XZa0esJP/dhZXiuI
PKmisMGMw8c4FCH8ZOvCAK5y2BQkJLrKJqh2rJq+SmeGrhGBNR+P4IUgyRDrH2m5
SQO6SvuWdTlXQzV2ngv6d3GmsM6BGXlBB3cRON3hbnrFTi/sZ6IsSb8tuWBvKAJw
CkyoXdMkUFsaPhYr9ht/pJInvUOu4o5HMSzere4uhtP0GM6Suqdxzq1Kmqro3Ei2
AW3GIQcHqTX+7cEqUnCjtH+Jm8h79e/RYvgsFCE4WhPkWXBxQgNIItiVYIxCHb/K
pKEKKjX1a8SzxCscH60AkR4bcN0JWfvIGXICiJWrrgxvJendTAIWGv9x5apGPEGQ
NGwjj1uCDTLMufvvoDn2wZQC2HJcS9qWpgEuQRhVCZkM1f6LNCxowyeC3vdjtAXb
+AUewFTPltqzyYC28BtsVEsTpVgyrugOf9KwXaxJoKADfjzEMx8iwB1id5s1C0FM
c6EZNZFUJmhMLDfAGs6mwwFMnC7bwLFajgAb4B+Wg4d/Q2/5UdE=
=M40q
-END PGP SIGNATURE End Message ---

Processed: reassign bugs to the package that closed them

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> #britney gets confused when a bug is closed by a package other than the 
> package it is filed aginst.
> reassign 1053840 blockdiag
Bug #1053840 {Done: Sergio de Almeida Cipriano Junior } 
[src:python-ws4py] src:python-ws4py: unsatisfied build dependency in testing: 
python3-sphinxcontrib.seqdiag
Bug reassigned from package 'src:python-ws4py' to 'blockdiag'.
No longer marked as found in versions python-ws4py/0.5.1+dfsg1-2.
No longer marked as fixed in versions blockdiag/2.0.1+dfsg-2.
> close 1053840 2.0.1+dfsg-2
Bug #1053840 {Done: Sergio de Almeida Cipriano Junior } 
[blockdiag] src:python-ws4py: unsatisfied build dependency in testing: 
python3-sphinxcontrib.seqdiag
There is no source info for the package 'blockdiag' at version '2.0.1+dfsg-2' 
with architecture ''
Unable to make a source version for version '2.0.1+dfsg-2'
Marked as fixed in versions 2.0.1+dfsg-2.
Bug #1053840 {Done: Sergio de Almeida Cipriano Junior } 
[blockdiag] src:python-ws4py: unsatisfied build dependency in testing: 
python3-sphinxcontrib.seqdiag
Bug 1053840 is already marked as done; not doing anything.
> reassign 1042120 blockdiag
Bug #1042120 {Done: Sergio de Almeida Cipriano Junior } 
[src:seqdiag] seqdiag: FTBFS: AttributeError: 'DiagramMetrics' object has no 
attribute 'textbox'
Bug reassigned from package 'src:seqdiag' to 'blockdiag'.
No longer marked as found in versions seqdiag/2.0.0+dfsg-1.
No longer marked as fixed in versions blockdiag/2.0.1+dfsg-2.
> close 1042120 2.0.1+dfsg-2
Bug #1042120 {Done: Sergio de Almeida Cipriano Junior } 
[blockdiag] seqdiag: FTBFS: AttributeError: 'DiagramMetrics' object has no 
attribute 'textbox'
There is no source info for the package 'blockdiag' at version '2.0.1+dfsg-2' 
with architecture ''
Unable to make a source version for version '2.0.1+dfsg-2'
Marked as fixed in versions 2.0.1+dfsg-2.
Bug #1042120 {Done: Sergio de Almeida Cipriano Junior } 
[blockdiag] seqdiag: FTBFS: AttributeError: 'DiagramMetrics' object has no 
attribute 'textbox'
Bug 1042120 is already marked as done; not doing anything.
> reassign 1049330 blockdiag
Bug #1049330 {Done: Sergio de Almeida Cipriano Junior } 
[python3-seqdiag] python3-seqdiag: fails with Pil 10
Bug reassigned from package 'python3-seqdiag' to 'blockdiag'.
No longer marked as found in versions seqdiag/2.0.0+dfsg-1.
No longer marked as fixed in versions blockdiag/2.0.1+dfsg-2.
> close 1049330 2.0.1+dfsg-2
Bug #1049330 {Done: Sergio de Almeida Cipriano Junior } 
[blockdiag] python3-seqdiag: fails with Pil 10
There is no source info for the package 'blockdiag' at version '2.0.1+dfsg-2' 
with architecture ''
Unable to make a source version for version '2.0.1+dfsg-2'
Marked as fixed in versions 2.0.1+dfsg-2.
Bug #1049330 {Done: Sergio de Almeida Cipriano Junior } 
[blockdiag] python3-seqdiag: fails with Pil 10
Bug 1049330 is already marked as done; not doing anything.
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
1042120: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042120
1049330: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1049330
1053840: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053840
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems