Bug#1065331: libhdf5-103-1t64: depends on libcurl4 instead of libcurl4t64

2024-03-18 Thread Vincent Lefevre
On 2024-03-18 20:58:02 +0100, Gilles Filippini wrote:
> Vincent Lefevre a écrit le 03/03/2024 à 01:08 :
> > Package: libhdf5-103-1t64
> > Version: 1.10.10+repack-3.1
> > Severity: serious
> > 
> > libhdf5-103-1t64 depends on libcurl4 instead of libcurl4t64.
> > This makes the upgrade of curl impossible.
> 
> How am I expected to solve this issue? As I understand it a binNMU should
> suffice. Am I right?

I think that the issue has now been fixed on the curl side:

https://salsa.debian.org/debian/curl/-/commit/40bdd3894230d325d382d59684c32d74202eee5c

-- 
Vincent Lefèvre  - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)



Bug#1066861: apt-get wants to remove packages instead of upgrading

2024-03-14 Thread Vincent Lefevre
Package: apt
Version: 2.7.13+b1
Severity: important

When I type "apt-get install libreoffice" to upgrade libreoffice,
apt-get wants to remove wine32:i386, while
"apt-get install libreoffice wine32:i386" shows that the upgrade
is actually possible without removing wine32:i386.

Debug information (attached) shows that in the former case:

Broken libgav1-1:i386 Depends on libabsl20220623:i386 < 20220623.1-3 @ii pmR > 
(>= 0~20220623.0-1)
  Considering libabsl20220623:i386 0 as a solution to libgav1-1:i386 2
  Added libabsl20220623:i386 to the remove list

while it could be upgraded to libabsl20220623t64:i386 instead.

I've attached the output of the following commands:

apt-get install -s -o Debug::pkgProblemResolver=true -o 
Debug::pkgDepCache::AutoInstall=true libreoffice >& out1

apt-get install -s -o Debug::pkgProblemResolver=true -o 
Debug::pkgDepCache::AutoInstall=true libreoffice wine32:i386 >& out2

-- Package-specific info:

-- apt-config dump --

APT "";
APT::Architecture "amd64";
APT::Build-Essential "";
APT::Build-Essential:: "build-essential";
APT::Install-Recommends "1";
APT::Install-Suggests "0";
APT::Key "";
APT::Key::Assert-Pubkey-Algo ">=rsa2048,ed25519,ed448";
APT::Sandbox "";
APT::Sandbox::User "_apt";
APT::Authentication "";
APT::Authentication::TrustCDROM "true";
APT::NeverAutoRemove "";
APT::NeverAutoRemove:: "^firmware-linux.*";
APT::NeverAutoRemove:: "^linux-firmware$";
APT::NeverAutoRemove:: "^linux-image-[a-z0-9]*$";
APT::NeverAutoRemove:: "^linux-image-[a-z0-9]*-[a-z0-9]*$";
APT::VersionedKernelPackages "";
APT::VersionedKernelPackages:: "linux-.*";
APT::VersionedKernelPackages:: "kfreebsd-.*";
APT::VersionedKernelPackages:: "gnumach-.*";
APT::VersionedKernelPackages:: ".*-modules";
APT::VersionedKernelPackages:: ".*-kernel";
APT::Never-MarkAuto-Sections "";
APT::Never-MarkAuto-Sections:: "metapackages";
APT::Never-MarkAuto-Sections:: "tasks";
APT::Move-Autobit-Sections "";
APT::Move-Autobit-Sections:: "oldlibs";
APT::AutoRemove "";
APT::AutoRemove::SuggestsImportant "false";
APT::Clean-Installed "false";
APT::Update "";
APT::Update::Post-Invoke-Success "";
APT::Update::Post-Invoke-Success:: "test -x /usr/bin/apt-show-versions || exit 
0 ; apt-show-versions -i";
APT::Architectures "";
APT::Architectures:: "amd64";
APT::Architectures:: "i386";
APT::Compressor "";
APT::Compressor::. "";
APT::Compressor::.::Name ".";
APT::Compressor::.::Extension "";
APT::Compressor::.::Binary "";
APT::Compressor::.::Cost "0";
APT::Compressor::zstd "";
APT::Compressor::zstd::Name "zstd";
APT::Compressor::zstd::Extension ".zst";
APT::Compressor::zstd::Binary "zstd";
APT::Compressor::zstd::Cost "60";
APT::Compressor::zstd::CompressArg "";
APT::Compressor::zstd::CompressArg:: "-19";
APT::Compressor::zstd::UncompressArg "";
APT::Compressor::zstd::UncompressArg:: "-d";
APT::Compressor::lz4 "";
APT::Compressor::lz4::Name "lz4";
APT::Compressor::lz4::Extension ".lz4";
APT::Compressor::lz4::Binary "false";
APT::Compressor::lz4::Cost "50";
APT::Compressor::gzip "";
APT::Compressor::gzip::Name "gzip";
APT::Compressor::gzip::Extension ".gz";
APT::Compressor::gzip::Binary "gzip";
APT::Compressor::gzip::Cost "100";
APT::Compressor::gzip::CompressArg "";
APT::Compressor::gzip::CompressArg:: "-6n";
APT::Compressor::gzip::UncompressArg "";
APT::Compressor::gzip::UncompressArg:: "-d";
APT::Compressor::xz "";
APT::Compressor::xz::Name "xz";
APT::Compressor::xz::Extension ".xz";
APT::Compressor::xz::Binary "xz";
APT::Compressor::xz::Cost "200";
APT::Compressor::xz::CompressArg "";
APT::Compressor::xz::CompressArg:: "-6";
APT::Compressor::xz::UncompressArg "";
APT::Compressor::xz::UncompressArg:: "-d";
APT::Compressor::bzip2 "";
APT::Compressor::bzip2::Name "bzip2";
APT::Compressor::bzip2::Extension ".bz2";
APT::Compressor::bzip2::Binary "bzip2";
APT::Compressor::bzip2::Cost "300";
APT::Compressor::bzip2::CompressArg "";
APT::Compressor::bzip2::CompressArg:: "-6";
APT::Compressor::bzip2::UncompressArg "";
APT::Compressor::bzip2::UncompressArg:: "-d";
APT::Compressor::lzma "";
APT::Compressor::lzma::Name "lzma";
APT::Compressor::lzma::Extension ".lzma";
APT::Compressor::lzma::Binary "xz";
APT::Compressor::lzma::Cost "400";
APT::Compressor::lzma::CompressArg "";
APT::Compressor::lzma::CompressArg:: "--format=lzma";
APT::Compressor::lzma::CompressArg:: "-6";
APT::Compressor::lzma::UncompressArg "";
APT::Compressor::lzma::UncompressArg:: "--format=lzma";
APT::Compressor::lzma::UncompressArg:: "-d";
Dir "/";
Dir::State "var/lib/apt";
Dir::State::lists "lists/";
Dir::State::cdroms "cdroms.list";
Dir::State::extended_states "extended_states";
Dir::State::status "/var/lib/dpkg/status";
Dir::Cache "var/cache/apt";
Dir::Cache::archives "archives/";
Dir::Cache::srcpkgcache "srcpkgcache.bin";
Dir::Cache::pkgcache "pkgcache.bin";
Dir::Etc "etc/apt";
Dir::Etc::sourcelist "sources.list";
Dir::Etc::sourceparts "sources.list.d";
Dir::Etc::main "apt.conf";
Dir::Etc::netrc "auth.conf";
Dir::Etc::netrcparts "auth.conf.d";
Dir::Etc::parts 

Bug#1066857: doc-debian: /usr/share/doc/debian/bug-reporting.txt should not be compressed

2024-03-14 Thread Vincent Lefevre
Package: doc-debian
Version: 11.3+nmu1
Severity: wishlist

The bug-reporting.txt file is rather small, thus it does not need to
be compressed. Having it compressed like currently breaks references,
such as in the apt-get(8) man page, which says

  APT bug page[1]. If you wish to report a bug in APT, please see
  /usr/share/doc/debian/bug-reporting.txt or the reportbug(1) command.

and in /usr/share/doc/debian/FAQ/support.en.html too, while only
/usr/share/doc/debian/bug-reporting.txt.gz exists.

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

doc-debian depends on no packages.

Versions of packages doc-debian recommends:
ii  debian-faq  11.1

Versions of packages doc-debian suggests:
ii  atril [postscript-viewer]   1.26.2-1.1+b1
ii  elinks [www-browser]0.16.1.1-4.1+b2
ii  firefox [www-browser]   123.0.1-1
hi  firefox-esr [www-browser]   92.0-local
ii  ghostscript [postscript-viewer] 10.02.1~dfsg-3+b1
ii  gv [postscript-viewer]  1:3.7.4-2+local1
ii  links [www-browser] 2.29-1+b3
ii  links2 [www-browser]2.29-1+b3
ii  lynx [www-browser]  2.9.0rel.0-2+b1
ii  qpdfview-ps-plugin [postscript-viewer]  0.5.0+ds-4
ii  w3m [www-browser]   0.5.3+git20230121-2+b3
ii  zathura-ps [postscript-viewer]  0.2.7-2+b2

-- no debconf information

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



Bug#1066856: apt: please update the URLs in the man pages

2024-03-14 Thread Vincent Lefevre
Package: apt
Version: 2.7.13+b1
Severity: minor

The URLs in the man pages should be updated. For instance, concerning
the b.d.o URLs in the various man pages, "http" should be changed to
"https".

In the apt-cache(8) man page:

http://www.research.att.com/sw/tools/graphviz/ gives a "Page Not Found"
error.

http://rw4.cs.uni-sb.de/users/sander/html/gsvcg1.html should be
changed to
https://www.rw.cdl.uni-saarland.de/people/sander/private/html/gsvcg1.html


-- Package-specific info:

-- (no /etc/apt/preferences present) --


-- (/etc/apt/preferences.d/no-adobe-flash-plugin present, but not submitted) --


-- (/etc/apt/preferences.d/no-pipewire present, but not submitted) --


-- (/etc/apt/sources.list present, but not submitted) --


-- (/etc/apt/sources.list.d/local-i386.list present, but not submitted) --


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

Versions of packages apt depends on:
ii  adduser 3.137
ii  base-passwd 3.6.3
ii  debian-archive-keyring  2023.4
ii  gpgv2.2.40-2
ii  libapt-pkg6.0t642.7.13+b1
ii  libc6   2.37-15.1
ii  libgcc-s1   14-20240303-1
ii  libgnutls30t64  3.8.3-1.1
ii  libseccomp2 2.5.5-1
ii  libstdc++6  14-20240303-1
ii  libsystemd0 255.4-1+b1

Versions of packages apt recommends:
ii  ca-certificates  20240203

Versions of packages apt suggests:
ii  apt-doc 2.7.13
ii  aptitude0.8.13-5+b2
ii  dpkg-dev1.22.6
ii  gnupg   2.2.40-2
ii  powermgmt-base  1.37

-- no debconf information

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



Bug#1066828: xz-utils: worse compression ratio should be announced in NEWS.Debian

2024-03-13 Thread Vincent Lefevre
Package: xz-utils
Version: 5.6.0-0.2
Severity: wishlist

After upgrading xz-utils from 5.4.5-0.3 to 5.6.0-0.2, the compression
ratio with "xz -9" has decreased. For instance, on 3 files:

Old   118822308   146463040   157197172
New   121120576   148930624   161255000

It took me some time to figure out. This is the reason:

/usr/share/doc/xz-utils/NEWS.gz

5.6.0 (2024-02-24)

[...]
* xz:

- Multithreaded mode is now the default. This improves
  compression speed and creates .xz files that can be
  decompressed in multithreaded mode. The downsides are
  increased memory usage and slightly worse compression ratio.
[...]

Using -T1 restores the old behavior.

Since this affects what the user gets and is some kind of regression,
this should be announced in NEWS.Debian, IMHO.

Note also that this change might affect diffs between .xz files (e.g.
after something is appended to the uncompressed file), though I have
not checked.

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

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

Versions of packages xz-utils depends on:
ii  libc6 2.37-15.1
ii  liblzma5  5.6.0-0.2

xz-utils recommends no packages.

xz-utils suggests no packages.

-- no debconf information

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



Bug#1065626: libgtk2.0-0t64 / libgtk2.0-bin dependency problem makes dpkg fail with attempt of removal of libgtk2.0-common

2024-03-12 Thread Vincent Lefevre
And on a 3rd machine, where I used

  aptitude --log-file=/tmp/aptitude.log --log-level=info


dpkg: dependency problems prevent removal of libb2-1:amd64:
 libqt6core6t64:amd64 depends on libb2-1 (>= 0.98.1).

dpkg: error processing package libb2-1:amd64 (--purge):
 dependency problems - not removing
(Reading database ... 795189 files and directories currently installed.)
Purging configuration files for libts0:amd64 (1.22-1+b1) ...
Errors were encountered while processing:
 libb2-1:amd64
E: Sub-process /usr/bin/dpkg returned an error code (1)


In the logs, this package libb2-1 appears only twice:

2024-03-13 01:33:14 [140549832112320] aptcache.cc:2323 INFO aptitude.apt.cache 
- aptitudeDepCache::sweep(): reinstating libb2-1:amd64

2024-03-13 01:34:48 [140549832112320] aptcache.cc:2323 INFO aptitude.apt.cache 
- aptitudeDepCache::sweep(): reinstating libb2-1:amd64

I've attached the compressed log file corresponding to this upgrade.

The packages that appear as REMOVE/INSTALL/UPGRADE in /var/log/aptitude:

[REMOVE, NOT USED] libatrildocument3:amd64 1.26.2-1
[REMOVE, NOT USED] libatrilview3:amd64 1.26.2-1
[REMOVE, NOT USED] libgxps2:amd64 0.3.2-3
[INSTALL, DEPENDENCIES] libatrildocument3t64:amd64 1.26.2-1.1+b1
[INSTALL, DEPENDENCIES] libatrilview3t64:amd64 1.26.2-1.1+b1
[INSTALL, DEPENDENCIES] libgxps2t64:amd64 0.3.2-4+b1
[INSTALL, DEPENDENCIES] libpoppler-cpp0t64:amd64 22.12.0-2.2
[INSTALL, DEPENDENCIES] libpoppler-glib8t64:amd64 22.12.0-2.2
[INSTALL, DEPENDENCIES] libpoppler-qt5-1t64:amd64 22.12.0-2.2
[INSTALL, DEPENDENCIES] libpoppler-qt6-3t64:amd64 22.12.0-2.2
[INSTALL, DEPENDENCIES] libpoppler126t64:amd64 22.12.0-2.2
[INSTALL, DEPENDENCIES] libqt6core6t64:amd64 6.4.2+dfsg-21.1+b1
[INSTALL, DEPENDENCIES] libqt6dbus6t64:amd64 6.4.2+dfsg-21.1+b1
[INSTALL, DEPENDENCIES] libqt6gui6t64:amd64 6.4.2+dfsg-21.1+b1
[INSTALL, DEPENDENCIES] libts0t64:amd64 1.22-1.1
[REMOVE, DEPENDENCIES] libpoppler-cpp0v5:amd64 22.12.0-2+b1
[REMOVE, DEPENDENCIES] libpoppler-glib8:amd64 22.12.0-2+b1
[REMOVE, DEPENDENCIES] libpoppler-glib8-dbgsym:amd64 22.12.0-2+b1
[REMOVE, DEPENDENCIES] libpoppler-qt5-1:amd64 22.12.0-2+b1
[REMOVE, DEPENDENCIES] libpoppler-qt6-3:amd64 22.12.0-2+b1
[REMOVE, DEPENDENCIES] libpoppler126:amd64 22.12.0-2+b1
[REMOVE, DEPENDENCIES] libpoppler126-dbgsym:amd64 22.12.0-2+b1
[REMOVE, DEPENDENCIES] libqt6core6:amd64 6.4.2+dfsg-21
[REMOVE, DEPENDENCIES] libqt6dbus6:amd64 6.4.2+dfsg-21
[REMOVE, DEPENDENCIES] libqt6gui6:amd64 6.4.2+dfsg-21
[REMOVE, DEPENDENCIES] libts0:amd64 1.22-1+b1
[UPGRADE] atril:amd64 1.26.2-1 -> 1.26.2-1.1+b1
[UPGRADE] atril-common:amd64 1.26.2-1 -> 1.26.2-1.1
[UPGRADE] libpoppler-dev:amd64 22.12.0-2+b1 -> 22.12.0-2.2
[UPGRADE] libpoppler-private-dev:amd64 22.12.0-2+b1 -> 22.12.0-2.2
[UPGRADE] poppler-utils:amd64 22.12.0-2+b1 -> 22.12.0-2.2

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


aptitude.log.xz
Description: Binary data


Bug#1065626: libgtk2.0-0t64 / libgtk2.0-bin dependency problem makes dpkg fail with attempt of removal of libgtk2.0-common

2024-03-12 Thread Vincent Lefevre
The same problem occurred on another machine, with other packages:

dpkg: dependency problems prevent removal of libjte2:amd64:
 libisofs6t64:amd64 depends on libjte2.

dpkg: error processing package libjte2:amd64 (--purge):
 dependency problems - not removing
(Reading database ... 708510 files and directories currently installed.)
Purging configuration files for libts0:amd64 (1.22-1+b1) ...
dpkg: dependency problems prevent removal of libid3tag0:amd64:
 libimlib2t64:amd64 depends on libid3tag0 (>= 0.15.1b).

dpkg: error processing package libid3tag0:amd64 (--purge):
 dependency problems - not removing
Errors were encountered while processing:
 libjte2:amd64
 libid3tag0:amd64

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



Bug#1065626: libgtk2.0-0t64 / libgtk2.0-bin dependency problem makes dpkg fail with attempt of removal of libgtk2.0-common

2024-03-07 Thread Vincent Lefevre
On 2024-03-07 17:15:05 +, Simon McVittie wrote:
> I can confirm that version 2.24.33-4 of libgtk2.0-common, libgtk2.0-0t64
> and libgtk2.0-bin are, in fact, installable (I have them installed
> right now). I can't see any dependency relationships between them that
> look suspicious.
> 
> If dpkg is removing libgtk2.0-common, then something must surely be
> asking dpkg to remove it?

But if it were aptitude, I would assume that it would have
a REMOVE line with this package in its logs.

> I notice that you have reported at least three bugs that are "the same
> shape" with three unrelated libraries, which suggests that this might
> be more of an aptitude problem than a GTK problem.

Some aptitude developer told me that installation issues were
in general due to declarations by packages.

> Other logs, in particular /var/log/apt/term.log, might provide more
> information about what actually happened.

I've attached the corresponding part of this file.
Note that libgtk2.0-common is mentioned only at the end
(what I had already given).

> Alternatively, if there is some heuristic about "try to keep packages
> from the same source at the same version" being applied, perhaps waiting
> for libgtk2.0-common_2.24.33-4 to become available from the
> Architecture: all buildd would help?

It was already available. And I installed it just after the error.
aptitude should obviously have proposed it for upgrade. I don't
know whether this is a bug in aptitude or something wrong in the
dependencies.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
Log started: 2024-03-07  16:01:43
(Reading database ...  (Reading database ... 5% (Reading database ... 10% 
(Reading database ... 15% (Reading database ... 20% (Reading database ... 25% 
(Reading database ... 30% (Reading database ... 35% (Reading database ... 40% 
(Reading database ... 45% (Reading database ... 50% (Reading database ... 55% 
(Reading database ... 60% (Reading database ... 65% (Reading database ... 70% 
(Reading database ... 75% (Reading database ... 80% (Reading database ... 85% 
(Reading database ... 90% (Reading database ... 95% (Reading database ... 100% 
(Reading database ... 655929 files and directories currently installed.)
Preparing to unpack .../libgtk2.0-bin_2.24.33-4_amd64.deb ...
Unpacking libgtk2.0-bin (2.24.33-4) over (2.24.33-3) ...
Preparing to unpack .../libgail-common_2.24.33-4_amd64.deb ...
Unpacking libgail-common:amd64 (2.24.33-4) over (2.24.33-3) ...
dpkg: libgail18:amd64: dependency problems, but removing anyway as you 
requested:
 libgnomecanvas2-0:amd64 depends on libgail18 (>= 1.18.0).

(Reading database ...  (Reading database ... 5% (Reading database ... 10% 
(Reading database ... 15% (Reading database ... 20% (Reading database ... 25% 
(Reading database ... 30% (Reading database ... 35% (Reading database ... 40% 
(Reading database ... 45% (Reading database ... 50% (Reading database ... 55% 
(Reading database ... 60% (Reading database ... 65% (Reading database ... 70% 
(Reading database ... 75% (Reading database ... 80% (Reading database ... 85% 
(Reading database ... 90% (Reading database ... 95% (Reading database ... 100% 
(Reading database ... 655928 files and directories currently installed.)
Removing libgail18:amd64 (2.24.33-3) ...
Selecting previously unselected package libgail18t64:amd64.
(Reading database ...  (Reading database ... 5% (Reading database ... 10% 
(Reading database ... 15% (Reading database ... 20% (Reading database ... 25% 
(Reading database ... 30% (Reading database ... 35% (Reading database ... 40% 
(Reading database ... 45% (Reading database ... 50% (Reading database ... 55% 
(Reading database ... 60% (Reading database ... 65% (Reading database ... 70% 
(Reading database ... 75% (Reading database ... 80% (Reading database ... 85% 
(Reading database ... 90% (Reading database ... 95% (Reading database ... 100% 
(Reading database ... 655923 files and directories currently installed.)
Preparing to unpack .../libgail18t64_2.24.33-4_amd64.deb ...
Unpacking libgail18t64:amd64 (2.24.33-4) ...
dpkg: libgtk2.0-0:amd64: dependency problems, but removing anyway as you 
requested:
 xournal depends on libgtk2.0-0 (>= 2.14.0).
 pinentry-gtk2 depends on libgtk2.0-0 (>= 2.18.0).
 pavumeter depends on libgtk2.0-0 (>= 2.8.0).
 libgtkmm-2.4-1v5:amd64 depends on libgtk2.0-0 (>= 2.24.0).
 libgnomecanvas2-0:amd64 depends on libgtk2.0-0 (>= 2.8.17).
 libgimp2.0:amd64 depends on libgtk2.0-0 (>= 2.24.10).
 ibus-gtk:amd64 depends on libgtk2.0-0 (>= 2.24.0).
 gromit depends on libgtk2.0-0 (>= 2.24.0).
 gkrellweather depends on libgtk2.0-0 (>= 2.8.0).
 gkrellm-volume depends on libgtk2.0-0 (>= 2.8.0).
 gkrellm depends on libgtk2.0-0 (>= 2.24.0).
 gimp depends on libgtk2.0-0 (>= 2.24.10).

(Reading database ...  (Reading database ... 5% (Reading database ... 10% 
(Reading database ... 15% 

Bug#1065625: libmtp9t64 / libmtp-runtime dependency problem makes dpkg fail with attempt of removal of libmtp-common

2024-03-07 Thread Vincent Lefevre
On 2024-03-07 16:00:35 +0100, Vincent Lefevre wrote:
> Will install 11 packages, and remove 3 packages.
> 8192 B of disk space will be used
> 
> [...]
> [HOLD, DEPENDENCIES] libmtp-common:amd64 1.1.21-3
> [...]
> [INSTALL, DEPENDENCIES] libgphoto2-6t64:amd64 2.5.31-2.1
> [INSTALL, DEPENDENCIES] libgphoto2-port12t64:amd64 2.5.31-2.1
> [INSTALL, DEPENDENCIES] libmtp9t64:amd64 1.1.21-3.1
> [REMOVE, DEPENDENCIES] libgphoto2-6:amd64 2.5.31-2
> [REMOVE, DEPENDENCIES] libgphoto2-port12:amd64 2.5.31-2
> [REMOVE, DEPENDENCIES] libmtp9:amd64 1.1.21-3
> [...]
> [UPGRADE] gvfs:amd64 1.53.90-2 -> 1.53.90-3
> [UPGRADE] gvfs-backends:amd64 1.53.90-2 -> 1.53.90-3
> [UPGRADE] gvfs-common:amd64 1.53.90-2 -> 1.53.90-3
> [UPGRADE] gvfs-daemons:amd64 1.53.90-2 -> 1.53.90-3
> [UPGRADE] gvfs-fuse:amd64 1.53.90-2 -> 1.53.90-3
> [UPGRADE] gvfs-libs:amd64 1.53.90-2 -> 1.53.90-3
> [UPGRADE] libgphoto2-l10n:amd64 2.5.31-2 -> 2.5.31-2.1
> [UPGRADE] libmtp-runtime:amd64 1.1.21-3 -> 1.1.21-3.1
> 

Note that libmtp-common:amd64 1.1.21-3.1 was available, but for
some unknown reason, aptitude did not propose its upgrade.

-- 
Vincent Lefèvre  - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)



Bug#1065626: libgtk2.0-0t64 / libgtk2.0-bin dependency problem makes dpkg fail with attempt of removal of libgtk2.0-common

2024-03-07 Thread Vincent Lefevre
Package: libgtk2.0-0t64
Version: 2.24.33-4
Severity: serious

During an upgrade with aptitude:

dpkg: dependency problems prevent removal of libgtk2.0-common:
 libgtk2.0-bin depends on libgtk2.0-common.
 libgtk2.0-0t64:amd64 depends on libgtk2.0-common.

dpkg: error processing package libgtk2.0-common (--purge):
 dependency problems - not removing
Errors were encountered while processing:
 libgtk2.0-common

Note that "apt install -f" has nothing to fix; this upgrade just
triggered a dpkg error (similar to bugs 1065603 and 1065625).

Moreover, like in these bugs, aptitude did not propose the removal
of libgtk2.0-common:

Aptitude 0.8.13: log report
Thu, Mar  7 2024 16:01:36 +0100

  IMPORTANT: this log only lists intended actions; actions which fail
  due to dpkg problems may not be completed.

Will install 5 packages, and remove 2 packages.
2048 B of disk space will be used

[...]
[HOLD, DEPENDENCIES] libgtk2.0-common:amd64 2.24.33-3
[...]
[INSTALL, DEPENDENCIES] libgail18t64:amd64 2.24.33-4
[INSTALL, DEPENDENCIES] libgtk2.0-0t64:amd64 2.24.33-4
[REMOVE, DEPENDENCIES] libgail18:amd64 2.24.33-3
[REMOVE, DEPENDENCIES] libgtk2.0-0:amd64 2.24.33-3
[...]
[UPGRADE] gtk2-engines-pixbuf:amd64 2.24.33-3 -> 2.24.33-4
[UPGRADE] libgail-common:amd64 2.24.33-3 -> 2.24.33-4
[UPGRADE] libgtk2.0-bin:amd64 2.24.33-3 -> 2.24.33-4


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

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

Versions of packages libgtk2.0-0t64 depends on:
ii  adwaita-icon-theme   46~rc-1
ii  gnome-icon-theme 3.12.0-5
ii  hicolor-icon-theme   0.17-2
ii  libatk1.0-0t64   2.51.90-2
ii  libc62.37-15.1
ii  libcairo21.18.0-1+b1
ii  libcups2t64  2.4.7-1.2+b1
ii  libfontconfig1   2.15.0-1
ii  libgdk-pixbuf-2.0-0  2.42.10+dfsg-3+b1
ii  libglib2.0-0t64  2.78.4-3
pn  libgtk2.0-common 
ii  libpango-1.0-0   1.51.0+ds-4
ii  libpangocairo-1.0-0  1.51.0+ds-4
ii  libpangoft2-1.0-01.51.0+ds-4
ii  libx11-6 2:1.8.7-1
ii  libxcomposite1   1:0.4.5-1
ii  libxcursor1  1:1.2.1-1
ii  libxdamage1  1:1.1.6-1
ii  libxext6 2:1.3.4-1+b1
ii  libxfixes3   1:6.0.0-2
ii  libxi6   2:1.8.1-1
ii  libxinerama1 2:1.1.4-3
ii  libxrandr2   2:1.5.2-2+b1
ii  libxrender1  1:0.9.10-1.1
ii  shared-mime-info 2.4-1

Versions of packages libgtk2.0-0t64 recommends:
ii  libgail-common   2.24.33-4
ii  libgtk2.0-bin2.24.33-4
ii  librsvg2-common  2.54.7+dfsg-2

Versions of packages libgtk2.0-0t64 suggests:
ii  gvfs  1.53.90-3

-- no debconf information

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



Bug#1065625: libmtp9t64 / libmtp-runtime dependency problem makes dpkg fail with attempt of removal of libmtp-common

2024-03-07 Thread Vincent Lefevre
Package: libmtp9t64
Version: 1.1.21-3.1
Severity: serious

During an upgrade with aptitude:

dpkg: dependency problems prevent removal of libmtp-common:
 libmtp9t64:amd64 depends on libmtp-common.
 libmtp-runtime depends on libmtp-common.

dpkg: error processing package libmtp-common (--purge):
 dependency problems - not removing
Errors were encountered while processing:
 libmtp-common

Note that "apt install -f" has nothing to fix; this upgrade just
triggered a dpkg error (similar to bug 1065603).

Moreover, like in bug 1065603, aptitude did not propose the removal
of libmtp-common:

Aptitude 0.8.13: log report
Thu, Mar  7 2024 15:49:03 +0100

  IMPORTANT: this log only lists intended actions; actions which fail
  due to dpkg problems may not be completed.

Will install 11 packages, and remove 3 packages.
8192 B of disk space will be used

[...]
[HOLD, DEPENDENCIES] libmtp-common:amd64 1.1.21-3
[...]
[INSTALL, DEPENDENCIES] libgphoto2-6t64:amd64 2.5.31-2.1
[INSTALL, DEPENDENCIES] libgphoto2-port12t64:amd64 2.5.31-2.1
[INSTALL, DEPENDENCIES] libmtp9t64:amd64 1.1.21-3.1
[REMOVE, DEPENDENCIES] libgphoto2-6:amd64 2.5.31-2
[REMOVE, DEPENDENCIES] libgphoto2-port12:amd64 2.5.31-2
[REMOVE, DEPENDENCIES] libmtp9:amd64 1.1.21-3
[...]
[UPGRADE] gvfs:amd64 1.53.90-2 -> 1.53.90-3
[UPGRADE] gvfs-backends:amd64 1.53.90-2 -> 1.53.90-3
[UPGRADE] gvfs-common:amd64 1.53.90-2 -> 1.53.90-3
[UPGRADE] gvfs-daemons:amd64 1.53.90-2 -> 1.53.90-3
[UPGRADE] gvfs-fuse:amd64 1.53.90-2 -> 1.53.90-3
[UPGRADE] gvfs-libs:amd64 1.53.90-2 -> 1.53.90-3
[UPGRADE] libgphoto2-l10n:amd64 2.5.31-2 -> 2.5.31-2.1
[UPGRADE] libmtp-runtime:amd64 1.1.21-3 -> 1.1.21-3.1


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

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

Versions of packages libmtp9t64 depends on:
ii  libc6  2.37-15.1
ii  libgcrypt201.10.3-2
pn  libmtp-common  
ii  libusb-1.0-0   2:1.0.27-1

Versions of packages libmtp9t64 recommends:
ii  libmtp-runtime  1.1.21-3.1
ii  udev255.3-2

libmtp9t64 suggests no packages.

-- no debconf information

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



Bug#731140: ghostscript: on PDF files with embedded fonts, ps2pdf changes the way fonts are rendered

2024-03-07 Thread Vincent Lefevre
On 2024-02-28 23:04:41 -0600, Steven Robbins wrote:
> On Mon, 2 Dec 2013 13:54:19 +0100 Vincent Lefevre  wrote:
> > font1.pdf is the original file (generated by pdflatex).
> > font2.pdf is the file obtained with "ps2pdf font1.pdf font2.pdf".
> > font.png shows the text of font1.pdf (left) and font2.pdf (right),
> > as obtained with xpdf.
> 
> I have repeated the test with ghostscript 10.02.1 and I cannot see any 
> difference (using xpdf, or using evince) between font1 and the output of 
> ps2pdf.

Well, with the font*.pdf files I had attached in my bug report, I can
no longer see any difference between font1.pdf and font2.pdf with xpdf
(or zathura). So I assume that this was actually a bug in xpdf (or
poppler), which did something wrong concerning font2.pdf.

I've also compared the rendering of these attached files on a Debian 11
machine with xpdf, and I cannot see any difference either.

So I suppose that this bug can be closed.

Regards,

-- 
Vincent Lefèvre  - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)



Bug#1065605: aptitude: useless backup of pkgstates

2024-03-07 Thread Vincent Lefevre
Package: aptitude
Version: 0.8.13-5+b2
Severity: minor

I ran aptitude to do an upgrade from the TUI (dpkg failed), then
quit just after it. This was before 11:28, since I reported this
failure at this time.

But /var/lib/aptitude contains

-rw-r--r-- 1 root root 10438852 2024-03-07 11:29:40 pkgstates
-rw-r--r-- 1 root root 10438852 2024-03-07 11:29:39 pkgstates.old

and these files have the same contents, which is useless.

I don't see what could have modified pkgstates... or perhaps from
the journalctl output:

Mar 07 11:22:25 qaa systemd[1]: Started packagekit.service - PackageKit Daemon.
[...]
Mar 07 11:30:11 qaa systemd[1]: packagekit.service: Deactivated successfully.

I could see nothing else.

-- Package-specific info:
Terminal: xterm-256color
$DISPLAY is set.
which aptitude: /bin/aptitude

aptitude version information:
aptitude 0.8.13
Compiler: g++ 13.2.0
Compiled against:
  apt version 6.0.0
  NCurses version 6.4
  libsigc++ version: 2.12.1
  Gtk+ support disabled.
  Qt support disabled.

Current library versions:
  NCurses version: ncurses 6.4.20240113
  cwidget version: 0.5.18
  Apt version: 6.0.0

aptitude linkage:
linux-vdso.so.1 (0x7fff813f9000)
libgtk3-nocsd.so.0 => /lib/x86_64-linux-gnu/libgtk3-nocsd.so.0 
(0x7f8fcf2bd000)
libapt-pkg.so.6.0 => /lib/x86_64-linux-gnu/libapt-pkg.so.6.0 
(0x7f8fcea0)
libncursesw.so.6 => /lib/x86_64-linux-gnu/libncursesw.so.6 
(0x7f8fcf283000)
libtinfo.so.6 => /lib/x86_64-linux-gnu/libtinfo.so.6 
(0x7f8fcf24e000)
libsigc-2.0.so.0 => /lib/x86_64-linux-gnu/libsigc-2.0.so.0 
(0x7f8fcf245000)
libcwidget.so.4 => /lib/x86_64-linux-gnu/libcwidget.so.4 
(0x7f8fcecfc000)
libsqlite3.so.0 => /lib/x86_64-linux-gnu/libsqlite3.so.0 
(0x7f8fce88a000)
libboost_iostreams.so.1.83.0 => 
/lib/x86_64-linux-gnu/libboost_iostreams.so.1.83.0 (0x7f8fcece2000)
libxapian.so.30 => /lib/x86_64-linux-gnu/libxapian.so.30 
(0x7f8fce60)
libstdc++.so.6 => /lib/x86_64-linux-gnu/libstdc++.so.6 
(0x7f8fce20)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7f8fce521000)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 
(0x7f8fcecb3000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f8fce01e000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7f8fcecae000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 
(0x7f8fceca9000)
libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x7f8fcec8a000)
libbz2.so.1.0 => /lib/x86_64-linux-gnu/libbz2.so.1.0 
(0x7f8fcec77000)
liblzma.so.5 => /lib/x86_64-linux-gnu/liblzma.so.5 (0x7f8fce4e4000)
liblz4.so.1 => /lib/x86_64-linux-gnu/liblz4.so.1 (0x7f8fcec4f000)
libzstd.so.1 => /lib/x86_64-linux-gnu/libzstd.so.1 (0x7f8fcdf5d000)
libudev.so.1 => /lib/x86_64-linux-gnu/libudev.so.1 (0x7f8fce857000)
libsystemd.so.0 => /lib/x86_64-linux-gnu/libsystemd.so.0 
(0x7f8fcde7b000)
libgcrypt.so.20 => /lib/x86_64-linux-gnu/libgcrypt.so.20 
(0x7f8fcdd33000)
libxxhash.so.0 => /lib/x86_64-linux-gnu/libxxhash.so.0 
(0x7f8fcec3a000)
/lib64/ld-linux-x86-64.so.2 (0x7f8fcf2e5000)
libuuid.so.1 => /lib/x86_64-linux-gnu/libuuid.so.1 (0x7f8fce4da000)
libcap.so.2 => /lib/x86_64-linux-gnu/libcap.so.2 (0x7f8fce4ce000)
libgpg-error.so.0 => /lib/x86_64-linux-gnu/libgpg-error.so.0 
(0x7f8fce4a5000)

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

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

Versions of packages aptitude depends on:
ii  aptitude-common   0.8.13-5
ii  libapt-pkg6.0t64  2.7.13+b1
ii  libboost-iostreams1.83.0  1.83.0-2.1
ii  libc6 2.37-15.1
ii  libcwidget4   0.5.18-6+b1
ii  libgcc-s1 14-20240303-1
ii  libncursesw6  6.4+20240113-1
ii  libsigc++-2.0-0v5 2.12.1-1
ii  libsqlite3-0  3.45.1-1
ii  libstdc++614-20240303-1
ii  libtinfo6 6.4+20240113-1
ii  libxapian30   1.4.22-1+b1

Versions of packages aptitude recommends:
ii  libdpkg-perl1.22.5
ii  sensible-utils  0.0.22

Versions of packages aptitude suggests:
ii  apt-xapian-index0.55
ii  aptitude-doc-en [aptitude-doc]  0.8.13-5
pn  debtags 
ii  tasksel 3.75

-- no debconf information

-- 
Vincent Lefèvre  - Web: 

Bug#1065603: libdebuginfod1t64 dependency problem breaks the upgrade

2024-03-07 Thread Vincent Lefevre
Control: retitle -1 libdebuginfod1t64 dependency problem makes dpkg fail with 
attempt of removal of libdebuginfod-common

On 2024-03-07 11:28:21 +0100, Vincent Lefevre wrote:
> When I wanted to upgrade, this ended up with
> 
> dpkg: dependency problems prevent removal of libdebuginfod-common:
>  libdebuginfod1t64:amd64 depends on libdebuginfod-common (>= 0.190-1.1).
> 
> dpkg: error processing package libdebuginfod-common (--purge):
>  dependency problems - not removing
> (Reading database ... 655945 files and directories currently installed.)
> Errors were encountered while processing:
>  libdebuginfod-common

Well, the issue just seems to be a dpkg failure. "apt install -f"
shows nothing to fix.

So I'm wondering why dpkg wanted to remove libdebuginfod-common.

FYI, I did the upgrade via aptitude, and this package wasn't proposed
for removal. In /var/log/aptitude, after discarding the HOLD lines
(which correspond to no changes for these packages):

Aptitude 0.8.13: log report
Thu, Mar  7 2024 11:24:24 +0100

  IMPORTANT: this log only lists intended actions; actions which fail
  due to dpkg problems may not be completed.

Will install 15 packages, and remove 6 packages.
5096 kB of disk space will be freed

[...]
[INSTALL, DEPENDENCIES] libasm1t64:amd64 0.190-1.1
[INSTALL, DEPENDENCIES] libdebuginfod1t64:amd64 0.190-1.1
[INSTALL, DEPENDENCIES] libdw1t64:amd64 0.190-1.1
[INSTALL, DEPENDENCIES] libelf1t64:amd64 0.190-1.1
[INSTALL, DEPENDENCIES] libglib2.0-0t64:amd64 2.78.4-3
[REMOVE, DEPENDENCIES] libasm1:amd64 0.190-1+b1
[REMOVE, DEPENDENCIES] libdebuginfod1:amd64 0.190-1+b1
[REMOVE, DEPENDENCIES] libdw1:amd64 0.190-1+b1
[REMOVE, DEPENDENCIES] libelf1:amd64 0.190-1+b1
[REMOVE, DEPENDENCIES] libglib2.0-0:amd64 2.78.4-1
[REMOVE, DEPENDENCIES] libglib2.0-0-dbgsym:amd64 2.78.4-1
[...]
[UPGRADE] elfutils:amd64 0.190-1+b1 -> 0.190-1.1
[UPGRADE] gir1.2-freedesktop:amd64 1.78.1-15 -> 1.78.1-16
[UPGRADE] gir1.2-freedesktop-dev:amd64 1.78.1-15 -> 1.78.1-16
[UPGRADE] gir1.2-girepository-2.0:amd64 1.78.1-15 -> 1.78.1-16
[UPGRADE] gir1.2-glib-2.0:amd64 1.78.1-15 -> 1.78.1-16
[UPGRADE] gir1.2-glib-2.0-dev:amd64 1.78.1-15 -> 1.78.1-16
[UPGRADE] libelf-dev:amd64 0.190-1+b1 -> 0.190-1.1
[UPGRADE] libglib2.0-bin:amd64 2.78.4-1 -> 2.78.4-3
[UPGRADE] libglib2.0-dev:amd64 2.78.4-1 -> 2.78.4-3
[UPGRADE] libglib2.0-dev-bin:amd64 2.78.4-1 -> 2.78.4-3


-- 
Vincent Lefèvre  - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)



Bug#1065603: libdebuginfod1t64 dependency problem breaks the upgrade

2024-03-07 Thread Vincent Lefevre
Package: libdebuginfod1t64
Version: 0.190-1.1
Severity: serious

When I wanted to upgrade, this ended up with

dpkg: dependency problems prevent removal of libdebuginfod-common:
 libdebuginfod1t64:amd64 depends on libdebuginfod-common (>= 0.190-1.1).

dpkg: error processing package libdebuginfod-common (--purge):
 dependency problems - not removing
(Reading database ... 655945 files and directories currently installed.)
Errors were encountered while processing:
 libdebuginfod-common

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

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

Versions of packages libdebuginfod1t64 depends on:
ii  libc6 2.37-15.1
ii  libcurl3t64-gnutls [libcurl3-gnutls]  8.6.0-3.2
pn  libdebuginfod-common  
ii  libdw1t64 0.190-1.1
ii  libelf1t640.190-1.1

libdebuginfod1t64 recommends no packages.

libdebuginfod1t64 suggests no packages.

-- no debconf information

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



Bug#1065429: dpkg -s: spurious error "dpkg-query: error: --status needs a valid package name"

2024-03-06 Thread Vincent Lefevre
On 2024-03-07 03:34:08 +0100, Guillem Jover wrote:
> > "apt-cache show libc6-dev" also lists this package.
> 
> apt behaves differently, this has been also a known discrepancy, but
> then they operate in general differently when it comes to their CLI
> arguments anyway.

The difference is bad for the user, making simple copy-paste
impossible, and usage more difficult: the user doesn't know
in advance whether the package name given by apt needs to be
completed for dpkg (systematically adding the main architecture
does not work for "Architecture: all" packages).

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



Bug#1065554: [Aptitude-devel] Bug#1065554: aptitude: the TUI silently breaks a "Recommends"

2024-03-06 Thread Vincent Lefevre
On 2024-03-06 21:36:09 +0100, Axel Beckert wrote:
> Hi Vincent,
> 
> Vincent Lefevre wrote:
> > Do you need the bundle?
> 
> Actually that would be interesting, as I have a vague idea how it
> might have been triggered and would like to experiment a bit if I can
> find a simpler reproducer.

[link sent in a private reply]

> BTW, do I remember right that you have APT::Install-Recommends set
> "false"?

AFAIK, perhaps except on a very old laptop (due to the lack of
disk space), I've always chosen to install recommends, which is
the default.

I usually have

  Aptitude::ProblemResolver::SolutionCost "safety, removals";

but this is not the case on this machine yet.

-- 
Vincent Lefèvre  - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)



Bug#1065554: [Aptitude-devel] Bug#1065554: aptitude: the TUI silently breaks a "Recommends"

2024-03-06 Thread Vincent Lefevre
On 2024-03-06 16:47:47 +0100, Axel Beckert wrote:
> Hi Vincent,
> 
> Vincent Lefevre wrote:
> > The aptitude TUI silently breaks a "Recommends":
> 
> I've seen also already seen this, but so far it always was for a
> reason here:
> 
> * On multiarch hosts, amd64 and i386 weren't in sync and there were
>   Breaks against any version not being the same version.

This is not a multiarch host yet.

> * An initial solution pulls in a package which Breaks the package in
>   question and that pulled in package later (manually or due to other
>   conflicts by manual changes) gets set to "keep uninstalled", but the
>   effect of its Breaks is not reverted.

I cannot see any Breaks of at-spi2-core.

Note that with the command line, I get

The following packages will be upgraded: 
  gtk-update-icon-cache libgtk-3-bin{b} libgtk-3-common 
The following packages are RECOMMENDED but will NOT be installed:
  libgtk-3-0t64 
3 packages upgraded, 0 newly installed, 0 to remove and 48 not upgraded.
Need to get 4763 kB of archives. After unpacking 3072 B will be used.
The following packages have unmet dependencies:
 libgtk-3-bin : Depends: libgtk-3-0t64 (>= 3.24.41-1.1) but it is not going to 
be installed
The following actions will resolve these dependencies:

 Keep the following packages at their current version:
1) libgtk-3-bin [3.24.41-1 (now, testing)]

Accept this solution? [Y/n/q/?] n
The following actions will resolve these dependencies:

 Remove the following packages: 
1) libatk-bridge2.0-0 [2.50.0-1+b1 (now, testing, unstable)]
2) libatk1.0-0 [2.50.0-1+b1 (now, testing, unstable)]   
3) libatspi2.0-0 [2.50.0-1+b1 (now, testing, unstable)] 
4) libgtk-3-0 [3.24.41-1 (now, testing, unstable)]  

 Install the following packages:
5) libatk-bridge2.0-0t64 [2.51.90-2 (unstable)] 
6) libatk1.0-0t64 [2.51.90-2 (unstable)]
7) libatspi2.0-0t64 [2.51.90-2 (unstable)]  
8) libgtk-3-0t64 [3.24.41-1.1 (unstable)]   

 Upgrade the following packages:
9) at-spi2-core [2.50.0-1+b1 (now, testing) -> 2.51.90-2 (unstable)]

Accept this solution? [Y/n/q/?] y
The following packages have unmet dependencies:
 libgtk-3-0t64 : Depends: libgtk-3-common (>= 3.24.41-1.1) but it is not going 
to be installed
The following actions will resolve these dependencies:

 Upgrade the following packages:
 
1) libgtk-3-common [3.24.41-1 (now, testing, unstable) -> 3.24.41-1.1 
(unstable)]

 Leave the following dependencies unresolved:   
 
2) libgtk-3-0t64 recommends libgtk-3-bin
 

Accept this solution? [Y/n/q/?] n
The following actions will resolve these dependencies:

 Keep the following packages at their current version:  
  
1) libgtk-3-0 [3.24.41-1 (now, testing, unstable)]  
  
2) libgtk-3-0t64 [Not Installed]
  

 Upgrade the following packages:
  
3) libgtk-3-common [3.24.41-1 (now, testing, unstable) -> 3.24.41-1.1~exp1 
(experimental)]

 Leave the following dependencies unresolved:   
  
4) libgtk-3-0 recommends libgtk-3-bin   
  
5) libgtk-3-0t64 recommends libgtk-3-bin
  

(Note: an upgrade to experimental is bad. BTW, no experimental
packages are currently installed.)

Accept this solution? [Y/n/q/?] n
The following actions will resolve these dependencies:

 Keep the following packages at their current version: 
1) libgtk-3-0 [3.24.41-1 (now, testing, unstable)] 
2) libgtk-3-0t64 [Not Installed]   
3) libgtk-3-common [3.24.41-1 (now, testing, unstable)]

 Leave the following dependencies unresolved:  
4) libgtk-3-0 recommends libgtk-3-bin  
5) libgtk-3-0t64 recommends libgtk-3-bin   

and then this is worse and worse. If I type 'y' for this solution,
I get:

The following NEW packages will be installed:
  libatk-bridge2.0-0t64{a} libatk1.0-0t64{a} libatspi2.0-0t64{a} 
The following packages will be REMOVED:
  at-spi2-core{u} libatk-bridge2.0-0{a} libatk1.0-0{a} libatspi2.0-0{a} 
libgtk-3-bin{u} 
The following packages will be upgraded:
  gtk-update-icon-cache 

Similarly, at-spi2-core gets removed without any warning on
the Recommends.

> But in your case neither of that se

Bug#1065546: d-i.debian.org: does not install "Recommends:" by default, at least uuid-runtime

2024-03-06 Thread Vincent Lefevre
I've eventuelly found

  https://www.debian.org/releases/stable/amd64/ch06s03.en.html#di-install-base

"For technical reasons packages installed during the installation of
the base system are installed without their “Recommends”. The rule
described above only takes effect after this point in the installation
process."

Then why are recommended packages not listed explicitly?

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



Bug#1065546: d-i.debian.org: does not install "Recommends:" by default, at least uuid-runtime

2024-03-06 Thread Vincent Lefevre
On 2024-03-06 13:53:48 +0100, Vincent Lefevre wrote:
> Note: I installed Debian with debian-12.1.0-amd64-netinst.iso.

Same issue on another machine where I installed Debian/testing using
debian-testing-amd64-netinst.iso on January 5.

-- 
Vincent Lefèvre  - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)



Bug#1065546: d-i.debian.org: does not install "Recommends:" by default, at least uuid-runtime

2024-03-06 Thread Vincent Lefevre
Package: d-i.debian.org
Severity: important

A few days ago, I noticed that the uuid-runtime package wasn't
installed, though libuuid1 was installed (when I installed Debian)
and had "Recommends: uuid-runtime".

FYI, uuid-runtime got pulled due to the rename of libuuid1 to
libuuid1t64.

Note: I installed Debian with debian-12.1.0-amd64-netinst.iso.

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



Bug#1065429: dpkg -s: spurious error "dpkg-query: error: --status needs a valid package name"

2024-03-04 Thread Vincent Lefevre
On 2024-03-04 13:47:00 +0100, Vincent Lefevre wrote:
> I get the following error:
> 
> cventin:~> dpkg -s libc6-dev
> dpkg-query: error: --status needs a valid package name but 'libc6-dev' is 
> not: ambiguous package name 'libc6-dev' with more than one installed instance

Wrong copy-paste (to match what is given below), but this is the
same error:

cventin:~> dpkg -s libnsl-dev
dpkg-query: error: --status needs a valid package name but 'libnsl-dev' is not: 
ambiguous package name 'libnsl-dev' with more than one installed instance

> while this is a valid package name: with an "apt" command, I get:
> 
> The following packages were automatically installed and are no longer 
> required:
>   libnsl-dev libnsl-dev:i386 libnsl2:i386 libtirpc-dev libtirpc-dev:i386
>   ^^
>   libtirpc3:i386
> [...]
> 
> The package name is listed above.

-- 
Vincent Lefèvre  - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)



Bug#1065429: dpkg -s: spurious error "dpkg-query: error: --status needs a valid package name"

2024-03-04 Thread Vincent Lefevre
Package: dpkg
Version: 1.22.5
Severity: important

I get the following error:

cventin:~> dpkg -s libc6-dev
dpkg-query: error: --status needs a valid package name but 'libc6-dev' is not: 
ambiguous package name 'libc6-dev' with more than one installed instance

while this is a valid package name: with an "apt" command, I get:

The following packages were automatically installed and are no longer required:
  libnsl-dev libnsl-dev:i386 libnsl2:i386 libtirpc-dev libtirpc-dev:i386
  ^^
  libtirpc3:i386
[...]

The package name is listed above.

"apt-cache show libc6-dev" also lists this package.

-- Package-specific info:

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

Versions of packages dpkg depends on:
ii  libbz2-1.0   1.0.8-5+b2
ii  libc62.37-15
ii  liblzma5 5.6.0-0.2
ii  libmd0   1.1.0-2
ii  libselinux1  3.5-2
ii  libzstd1 1.5.5+dfsg2-2
ii  tar  1.35+dfsg-3
ii  zlib1g   1:1.3.dfsg-3+b1

dpkg recommends no packages.

Versions of packages dpkg suggests:
ii  apt2.7.12
pn  debsig-verify  

-- no debconf information

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



Bug#1065331: libhdf5-103-1t64: depends on libcurl4 instead of libcurl4t64

2024-03-03 Thread Vincent Lefevre
On 2024-03-03 01:08:10 +0100, Vincent Lefevre wrote:
> Package: libhdf5-103-1t64
> Version: 1.10.10+repack-3.1
> Severity: serious
> 
> libhdf5-103-1t64 depends on libcurl4 instead of libcurl4t64.
> This makes the upgrade of curl impossible.

It seems that this was actually a bug in curl, where libcurl4t64
had an incorrect X-Time64-Compat and which has just been fixed in

https://salsa.debian.org/debian/curl/-/commit/40bdd3894230d325d382d59684c32d74202eee5c

-- 
Vincent Lefèvre  - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)



Bug#1065331: libhdf5-103-1t64: depends on libcurl4 instead of libcurl4t64

2024-03-02 Thread Vincent Lefevre
Package: libhdf5-103-1t64
Version: 1.10.10+repack-3.1
Severity: serious

libhdf5-103-1t64 depends on libcurl4 instead of libcurl4t64.
This makes the upgrade of curl impossible.

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

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

Versions of packages libhdf5-103-1t64 depends on:
ii  libc6   2.37-15.1
ii  libcurl48.6.0-3
ii  libssl3t64  3.1.5-1.1
ii  libsz2  1.1.2-1
ii  zlib1g  1:1.3.dfsg-3.1

libhdf5-103-1t64 recommends no packages.

libhdf5-103-1t64 suggests no packages.

-- no debconf information

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



Bug#1065310: deborphan should take "Provides:" into account

2024-03-02 Thread Vincent Lefevre
Package: deborphan
Version: 1.7.35
Severity: normal

qaa:~> deborphan
libgnutls-openssl27t64
libzvbi0t64

meaning that I could remove libgnutls-openssl27t64, but actually
this is not possible:

qaa:~> apt remove -s libgnutls-openssl27t64
[...]
The following packages will be REMOVED:
  gkrellm gkrellm-volume gkrellweather libgnutls-openssl27t64

Indeed, gkrellm depends on libgnutls-openssl27, which is provided
by libgnutls-openssl27t64:

Package: libgnutls-openssl27t64
[...]
Version: 3.8.3-1.1
Replaces: libgnutls-openssl27
Provides: libgnutls-openssl27 (= 3.8.3-1.1)
Depends: libgnutls30t64 (= 3.8.3-1.1), libc6 (>= 2.34)
Breaks: libgnutls-openssl27 (<< 3.8.3-1.1)
[...]

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

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

Versions of packages deborphan depends on:
ii  libc6  2.37-15.1

Versions of packages deborphan recommends:
ii  apt   2.7.13+b1
ii  gettext-base  0.21-14+b1

deborphan suggests no packages.

-- no debconf information

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



Bug#1064969: apt: can't upgrade with aptitude

2024-03-01 Thread Vincent Lefevre
And even in a simple case line cnee:

qaa:~> aptitude install -s cnee
The following packages will be REMOVED:  
  libxnee0{u} 
The following packages will be upgraded:
  cnee{b} 
1 packages upgraded, 0 newly installed, 1 to remove and 263 not upgraded.
Need to get 50.4 kB of archives. After unpacking 324 kB will be freed.
The following packages have unmet dependencies:
 cnee : Depends: libxnee0t64 but it is not going to be installed
The following actions will resolve these dependencies:

 Install the following packages:
1) libxnee0t64 [3.19-9.1 (unstable)]



Accept this solution? [Y/n/q/?] n
The following actions will resolve these dependencies:

 Keep the following packages at their current version:
1) cnee [3.19-9 (now, stable, testing)]   
2) libxnee0 [3.19-9 (now, stable, testing)]   



Accept this solution? [Y/n/q/?] n
The following actions will resolve these dependencies:

 Remove the following packages:
1) cnee [3.19-9 (now, stable, testing)]



Accept this solution? [Y/n/q/?] n

*** No more solutions available ***

No solutions are found, while with apt:

qaa:~> apt install -s cnee
[...]
The following additional packages will be installed:
  libxnee0t64
Suggested packages:
  xnee-doc
The following packages will be REMOVED:
  libxnee0
The following NEW packages will be installed:
  libxnee0t64
The following packages will be upgraded:
  cnee
1 upgraded, 1 newly installed, 1 to remove and 263 not upgraded.
Inst cnee [3.19-9] (3.19-9.1 Debian:unstable [amd64]) []
Remv libxnee0 [3.19-9] []
Inst libxnee0t64 (3.19-9.1 Debian:unstable [amd64])
Conf cnee (3.19-9.1 Debian:unstable [amd64])
Conf libxnee0t64 (3.19-9.1 Debian:unstable [amd64])

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



Bug#1064969: apt: can't upgrade with aptitude

2024-03-01 Thread Vincent Lefevre
On 2024-02-28 17:28:51 +0100, Sven Joachim wrote:
> No, in this case it is a problem with aptitude's resolver which
> manifests itself due to the following configuration setting:
> 
> > Aptitude::ProblemResolver::SolutionCost "safety, removals";
> 
> This does cause aptitude to hold apt back by default, rather than remove
> libapt-pkg6.0.  You can press 'n' at the prompt, the next solution
> aptitude then suggests is to upgrade apt.

Well, this is really stupid! aptitude sometimes wants to remove
lots of packages just to avoid the package renames, while apt
proposes a right solution (with some easy help)!

For instance, with apt:

cventin:~> apt install -s gir1.2-atk-1.0 libwine:i386
[...]
libwine:i386 is already the newest version (9.0~repack-4).
libwine:i386 set to manually installed.
The following additional packages will be installed:
  at-spi2-common at-spi2-core gir1.2-atspi-2.0 gir1.2-girepository-2.0-dev
  gobject-introspection gobject-introspection-bin libatk-adaptor
  libatk-bridge2.0-0t64 libatk-bridge2.0-dev libatk1.0-0t64 libatk1.0-dev
  libatspi2.0-0t64 libatspi2.0-dev libgirepository-1.0-dev
  libgirepository1.0-dev libglib2.0-0t64 libglib2.0-0t64:i386 libglib2.0-bin
  libglib2.0-data libglib2.0-dev libglib2.0-dev-bin python3-mako
  python3-markdown python3-markupsafe
Suggested packages:
  libgirepository1.0-doc low-memory-monitor low-memory-monitor:i386
  libglib2.0-doc python-mako-doc python3-beaker python-markdown-doc
The following packages will be REMOVED:
  libatk-bridge2.0-0 libatk1.0-0 libatspi2.0-0 libglib2.0-0 libglib2.0-0:i386
The following NEW packages will be installed:
  gir1.2-girepository-2.0-dev gobject-introspection gobject-introspection-bin
  libatk-bridge2.0-0t64 libatk1.0-0t64 libatspi2.0-0t64
  libgirepository-1.0-dev libgirepository1.0-dev libglib2.0-0t64
  libglib2.0-0t64:i386 python3-mako python3-markdown python3-markupsafe
The following packages will be upgraded:
  at-spi2-common at-spi2-core gir1.2-atk-1.0 gir1.2-atspi-2.0 libatk-adaptor
  libatk-bridge2.0-dev libatk1.0-dev libatspi2.0-dev libglib2.0-bin
  libglib2.0-data libglib2.0-dev libglib2.0-dev-bin
12 upgraded, 13 newly installed, 5 to remove and 263 not upgraded.
[...]

Note that all the removes correspond to package renames.

I had to provide libwine:i386, otherwise apt wanted to remove it.

With aptitude, I need to use 'n' 21 times until I reach the right
solution (with an unmet dependency after that, which can be resolved,
though).

cventin:~> aptitude install -s gir1.2-atk-1.0 libwine:i386
libwine:i386 is already installed at the requested version (9.0~repack-4)
libwine:i386 is already installed at the requested version (9.0~repack-4)
The following packages will be upgraded:
  at-spi2-common gir1.2-atk-1.0{b} 
2 packages upgraded, 0 newly installed, 0 to remove and 273 not upgraded.
Need to get 190 kB of archives. After unpacking 0 B will be used.
The following packages have unmet dependencies:
 libatk1.0-dev : Depends: gir1.2-atk-1.0 (= 2.50.0-1+b1) but 2.51.90-1 is to be 
installed
 gir1.2-atk-1.0 : Depends: libatk1.0-0t64 (>= 2.51.90) but it is not going to 
be installed
The following actions will resolve these dependencies:

 Keep the following packages at their current version:
1) gir1.2-atk-1.0 [2.50.0-1+b1 (now, testing)]



Accept this solution? [Y/n/q/?] n
The following actions will resolve these dependencies:

  Remove the following packages: 
1)  libatk-bridge2.0-dev [2.50.0-1+b1 (now, testing)]
2)  libatk1.0-0 [2.50.0-1+b1 (now, testing, unstable)]   
3)  libatk1.0-dev [2.50.0-1+b1 (now, testing)]   
4)  libglib2.0-0 [2.78.4-1 (now, testing, unstable)] 
5)  libglib2.0-0:i386 [2.78.4-1 (now, testing, unstable)]
6)  libgtk-3-dev [3.24.41-1 (now, testing)]  
7)  libgtk2.0-dev [2.24.33-3 (now, testing)] 

  Install the following packages:
8)  libatk1.0-0t64 [2.51.90-1 (unstable)]
9)  libglib2.0-0t64 [2.78.4-2.1 (unstable)]  
10) libglib2.0-0t64:i386 [2.78.4-2.1 (unstable)] 

  Upgrade the following packages:
11) libglib2.0-bin [2.78.4-1 (now, testing) -> 2.78.4-2.1 (unstable)]
12) libglib2.0-dev [2.78.4-1 (now, testing) -> 2.78.4-2.1 (unstable)]
13) libglib2.0-dev-bin [2.78.4-1 (now, testing) -> 2.78.4-2.1 (unstable)]



Accept this solution? [Y/n/q/?] n
The following actions will resolve these dependencies:

  Remove the following packages: 
1)  libatk-bridge2.0-dev [2.50.0-1+b1 (now, testing)]
2)  libatk1.0-0 [2.50.0-1+b1 (now, testing, unstable)]   
3)  libatk1.0-dev 

Bug#1064982: gnuplot-qt: gnuplot displays a window with nothing in it

2024-02-29 Thread Vincent Lefevre
Another thing: This problem actually appears even without FVWM's
ManualPlacement, i.e. if the window is displayed immediately. So
I suppose that it is likely to occur with other window managers.

A simple command to reproduce the issue:

  echo 'set terminal wxt; plot x' | gnuplot -persist

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



Bug#1064982: gnuplot-qt: gnuplot displays a window with nothing in it

2024-02-29 Thread Vincent Lefevre
On 2024-02-29 12:34:17 +0100, Vincent Lefevre wrote:
> Indeed, this was caused by the upgrade of the pango library. I've
> just posted on the upstream bug:
> 
> Actually, the problem also occurs with gnuplot 5. It has actually
> appeared with the 1.52 pango library: downgrading the pango packages
> to 1.51 makes the problem disappear, both with gnuplot 5 and 6. Now,
> I don't know whether this is a bug in pango or a bug in gnuplot that
> is triggered only with the new version of pango (for instance, it
> might be possible that pango 1.52 is faster than 1.51, making the
> problem appear, since it seems to be a race condition).

I've identified the "problematic" commit in Pango, and I would tend
to say that this is the reason:

https://gitlab.gnome.org/GNOME/pango/-/commit/89442dae443eba2aa0f0a526b4d6d39c0c9b13c6

According to the commit message, a new thread was created "for every
single fontconfig call". Now "a single fontconfig thread per fontmap"
is used. So I suppose that this makes Pango faster, triggering the
race condition in gnuplot.

I've updated the upstream gnuplot bug and opened a bug in Pango,
hoping confirmation:

https://gitlab.gnome.org/GNOME/pango/-/issues/784

-- 
Vincent Lefèvre  - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)



Bug#1064969: apt: can't upgrade with aptitude

2024-02-29 Thread Vincent Lefevre
On 2024-02-29 14:11:41 +0900, Simon Richter wrote:
> Hi,
> 
> On 2/28/24 23:49, Vincent Lefevre wrote:
> 
> > # aptitude install apt
> > The following packages will be upgraded:
> >apt{b} apt-doc
> > 2 packages upgraded, 0 newly installed, 0 to remove and 180 not upgraded.
> > Need to get 1622 kB of archives. After unpacking 0 B will be used.
> > The following packages have unmet dependencies:
> >   apt : Depends: libapt-pkg6.0t64 (>= 2.7.12+nmu1) but it is not going to 
> > be installed
> >   apt-utils : Depends: apt (= 2.7.12) but 2.7.12+nmu1 is to be installed
> > The following actions will resolve these dependencies:
> > 
> >   Keep the following packages at their current version:
> > 1) apt [2.7.12 (now, testing)]
> 
> That is a valid possible resolution. Presumably, if you reject this
> resolution, it will instead propose to upgrade apt-utils, install
> libapt-pkg6.0t64 and remove libapt-pkg6.0.
> 
> Since that is a larger change, the conservative proposal comes first.
> 
> apt-utils has a versioned dependency on apt, which means upgrading
> apt alone (which you requested)

No, this requests to upgrade *all* packages of the same source
(well, at least in the TUI, which I normally use, but there is
the same issue in the TUI).

> breaks another "unrelated" package. There has been some debate that
> resolvers should favour upgrading all binaries that are built from
> the same source together, but that has not been implemented yet, and
> it is unclear if that would have changed anything here.

See above, but in any case...

> > So, I suppose that this is also the case for aptitude: if aptitude
> > cannot upgrade just because of a rename, then this is a problem in
> > the involved packages.
> 
> Note that you haven't requested an "upgrade" (which would likely have
> worked, because it would have switched both apt and apt-utils to the new
> version, and the remaining involved packages were automatically installed as
> dependencies of the packages being upgraded).

This doesn't work with an upgrade either:

qaa:~> aptitude upgrade -s
Resolving dependencies...
The following NEW packages will be installed:
  libatrildocument3t64{a} libatrilview3t64{a} libboost-chrono1.83.0t64{a} 
  libcupsfilters1t64{a} libevdocument3-4t64{a} libevemu3t64{a} 
  libevview3-3t64{a} libfontembed1t64{a} libgxps2t64{a} 
  libtss2-mu-4.0.1-0t64{a} 
The following packages will be REMOVED:
  libatrildocument3{u} libatrilview3{u} libboost-chrono1.83.0{u} 
  libcupsfilters1{u} libevdocument3-4{u} libevemu3{u} libevview3-3{u} 
  libfontembed1{u} libgxps2{u} libtss2-mu0{u} 
The following packages will be upgraded:
  apt-doc at-spi2-common atril atril-common cups-browsed cups-filters 
  cups-filters-core-drivers evemu-tools evince evince-common 
  evolution-data-server-common gir1.2-pango-1.0 glib-networking 
  glib-networking-common glib-networking-services glibc-doc-reference 
  gnome-calendar gnome-remote-desktop gnome-settings-daemon 
  gnome-settings-daemon-common gnome-text-editor libboost-atomic1.83-dev 
  libboost-atomic1.83.0 libboost-chrono1.83-dev libboost-date-time1.83-dev 
  libboost-date-time1.83.0 libboost-filesystem1.83-dev 
  libboost-filesystem1.83.0 libboost-iostreams1.83.0 libboost-locale1.83.0 
  libboost-program-options1.83-dev libboost-program-options1.83.0 
  libboost-regex1.83-dev libboost-regex1.83.0 
  libboost-serialization1.83-dev libboost-serialization1.83.0 
  libboost-system1.83-dev libboost-system1.83.0 libboost-thread1.83-dev 
  libboost-thread1.83.0 libboost1.83-dev libglib2.0-data liblzma-dev 
  liblzma5 libnss-myhostname libnss-systemd libpam-runtime libpam-systemd 
  libpango-1.0-0 libpango1.0-dev libpangocairo-1.0-0 libpangoft2-1.0-0 
  libpangoxft-1.0-0 libsystemd-shared libsystemd0 libtss2-esys-3.0.2-0 
  libtss2-rc0 libtss2-sys1 libtss2-tcti-cmd0 libtss2-tcti-device0 
  libtss2-tcti-libtpms0 libtss2-tcti-mssim0 libtss2-tcti-spi-helper0 
  libtss2-tcti-swtpm0 libtss2-tctildr0 libudev1 pango1.0-tools sa-compile 
  spamassassin spamc spamd systemd systemd-dev systemd-sysv 
  systemd-timesyncd udev xz-utils 
The following packages are RECOMMENDED but will NOT be installed:
  evolution-data-server 
77 packages upgraded, 10 newly installed, 10 to remove and 22 not upgraded.
Need to get 37.2 MB/43.6 MB of archives. After unpacking 728 kB will be used.

apt-doc is proposed for upgrade, but not apt.

What's strange is that it appears to work for some packages, e.g.
libatrildocument3 replaced by libatrildocument3t64, but not for
other ones (e.g. libapt-pkg6.0 replaced by libapt-pkg6.0t64).

-- 
Vincent Lefèvre  - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)



Bug#1064982: gnuplot-qt: gnuplot displays a window with nothing in it

2024-02-29 Thread Vincent Lefevre
Control: found -1 5.4.4+dfsg1-2

On 2024-02-29 03:43:33 +0100, Vincent Lefevre wrote:
> Now, I can reproduce the bug on my other machine. I upgraded some
> packages, and I don't know whether this is related (only pango1.0
> packages seem related).

Indeed, this was caused by the upgrade of the pango library. I've
just posted on the upstream bug:

Actually, the problem also occurs with gnuplot 5. It has actually
appeared with the 1.52 pango library: downgrading the pango packages
to 1.51 makes the problem disappear, both with gnuplot 5 and 6. Now,
I don't know whether this is a bug in pango or a bug in gnuplot that
is triggered only with the new version of pango (for instance, it
might be possible that pango 1.52 is faster than 1.51, making the
problem appear, since it seems to be a race condition).

-- 
Vincent Lefèvre  - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)



Bug#1064982: gnuplot-qt: gnuplot displays a window with nothing in it

2024-02-28 Thread Vincent Lefevre
Control: forwarded -1 https://sourceforge.net/p/gnuplot/bugs/2693/

I've reported the bug upstream.

On 2024-02-29 04:07:17 +0100, Vincent Lefevre wrote:
> For instance, if I run
> 
>   { echo 'plot x' ; sleep 3 ; } | gnuplot -persist
> 
> there are no issues if I place the window before the 3 seconds,
> but the problem appears if I wait for more than 3 seconds.

But note that ssh and strace make the problem disappear
(even if I wait for more than 3 seconds).

-- 
Vincent Lefèvre  - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)



Bug#1064982: gnuplot-qt: gnuplot displays a window with nothing in it

2024-02-28 Thread Vincent Lefevre
Control: retitle -1 with GNUTERM=wxt, "gnuplot -persist" hangs if gnuplot 
cannot draw before stdin is closed, e.g. with FVWM's ManualPlacement

On 2024-02-29 03:47:41 +0100, Vincent Lefevre wrote:
> On 2024-02-29 03:43:33 +0100, Vincent Lefevre wrote:
> > This can be reproduced with the following script:
> > 
> > #!/bin/sh
> > 
> > gnuplot -persist < > plot '-' using 1:2 t '' with line
> > 0 0
> > 10 10
> > e
> > EOF
> > 
> > No issues with GNUTERM=qt, but with GNUTERM=wxt, it doesn't work.
> 
> Or just:
> 
> $ echo 'plot x' | gnuplot -persist

This may be related to my window manager FVWM (and its configuration),
where I choose the window position before it appears:

  ManualPlacement (aka active placement).  The user is required to
  place every new window manually.  The window  only  shows  as  a
  rubber  band  until a place is selected manually.  The window is
  placed when a mouse button or any key except Escape is  pressed.
  Escape  aborts  manual  placement which places the window in the
  top left corner of the screen.  If mouse  button  2  is  pressed
  during the initial placement of a window (respectively Shift and
  mouse  button  1 in case Mwm emulation has been enabled with the
  Emulate command), the user is asked to resize the window too.

For instance, if I run

  { echo 'plot x' ; sleep 3 ; } | gnuplot -persist

there are no issues if I place the window before the 3 seconds,
but the problem appears if I wait for more than 3 seconds.

The problem seems to be due to the fact that the standard input gets
closed before gnuplot can actually draw. Indeed,

  { echo 'plot x' ; exec >&- ; sleep 3 ; } | gnuplot -persist

triggers the problem even if I place the window before the 3 seconds.

-- 
Vincent Lefèvre  - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)



Bug#1064982: gnuplot-qt: gnuplot displays a window with nothing in it

2024-02-28 Thread Vincent Lefevre
On 2024-02-29 03:43:33 +0100, Vincent Lefevre wrote:
> This can be reproduced with the following script:
> 
> #!/bin/sh
> 
> gnuplot -persist < plot '-' using 1:2 t '' with line
> 0 0
> 10 10
> e
> EOF
> 
> No issues with GNUTERM=qt, but with GNUTERM=wxt, it doesn't work.

Or just:

$ echo 'plot x' | gnuplot -persist

> I suspect a race condition, as using strace makes the problem
> disappear. Using ssh (even "ssh localhost", then the test script)
> also makes the problem disappear.

Ditto with the above command.

-- 
Vincent Lefèvre  - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)



Bug#1064982: gnuplot-qt: gnuplot displays a window with nothing in it

2024-02-28 Thread Vincent Lefevre
On 2024-02-28 15:01:17 -0800, Dima Kogan wrote:
> Can you see if other wxt applications work on a system that's
> exhibiting this problem?

The issue seems specific to gnuplot under particular conditions.
See below.

Now, I can reproduce the bug on my other machine. I upgraded some
packages, and I don't know whether this is related (only pango1.0
packages seem related).

This can be reproduced with the following script:

#!/bin/sh

gnuplot -persist < - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)



Bug#1064982: gnuplot-qt: gnuplot displays a window with nothing in it

2024-02-28 Thread Vincent Lefevre
On 2024-02-28 10:39:49 -0800, Dima Kogan wrote:
> Hi. I'd like to get more clarity.
> 
> - You see the issue when you try to plot anything at all?
> 
> - You say "plot x" and you get a plot window, but it's all white, or
>   something?
> 
> - Only with the "qt" terminal?

It was the wxt terminal (which I normally use all the time).

I'll do more tests tomorrow since I can't reproduce the problem
remotely (or locally on a different machine).

I could also look at the strace and xtrace output.

When I got the problem, using FVWM's Delete command to remove
the window did not have any effect (so this is not just a
display issue, the process was frozen in some state); FVWM's
Destroy command worked. These commands are described as follows:

Delete
Sends a message to a window asking that it remove itself,
frequently causing the application to exit.

Destroy
Destroys an application window, which usually causes the
application to crash and burn.

The problem occurred first at 2024-02-28T19:12:24 CET.
At that time, journalctl shows:

Feb 28 19:12:24 cventin dbus-daemon[1489]: [session uid=1000 pid=1489] 
Activating via systemd: service name='org.freedesktop.portal.Desktop' 
unit='xdg-desktop-portal.service' requested by ':1.27' (uid=1000 pid=7164 
comm="/usr/bin/gnuplot -persist")
Feb 28 19:12:25 cventin systemd[1462]: Starting xdg-desktop-portal.service - 
Portal service...
Feb 28 19:12:25 cventin dbus-daemon[1489]: [session uid=1000 pid=1489] 
Activating via systemd: service name='org.freedesktop.portal.Documents' 
unit='xdg-document-portal.service' requested by ':1.28' (uid=1000 pid=7168 
comm="/usr/libexec/xdg-desktop-portal")
Feb 28 19:12:25 cventin systemd[1462]: Starting xdg-document-portal.service - 
flatpak document portal service...
Feb 28 19:12:25 cventin dbus-daemon[1489]: [session uid=1000 pid=1489] 
Activating via systemd: service 
name='org.freedesktop.impl.portal.PermissionStore' 
unit='xdg-permission-store.service' requested by ':1.29' (uid=1000 pid=7174 
comm="/usr/libexec/xdg-document-portal")
Feb 28 19:12:25 cventin systemd[1462]: Starting xdg-permission-store.service - 
sandboxed app permission store...
Feb 28 19:12:25 cventin dbus-daemon[1489]: [session uid=1000 pid=1489] 
Successfully activated service 'org.freedesktop.impl.portal.PermissionStore'
Feb 28 19:12:25 cventin systemd[1462]: Started xdg-permission-store.service - 
sandboxed app permission store.
Feb 28 19:12:25 cventin dbus-daemon[1489]: [session uid=1000 pid=1489] 
Successfully activated service 'org.freedesktop.portal.Documents'
Feb 28 19:12:25 cventin systemd[1462]: Started xdg-document-portal.service - 
flatpak document portal service.
Feb 28 19:12:25 cventin xdg-document-portal[7174]: Ignoring invalid max threads 
value 4294967295 > max (10).
Feb 28 19:12:25 cventin xdg-desktop-por[7168]: Choosing gtk.portal for 
org.freedesktop.impl.portal.Lockdown as a last-resort fallback
Feb 28 19:12:25 cventin xdg-desktop-por[7168]: The preferred method to match 
portal implementations to desktop environments is to use the portals.conf(5) 
configuration file
Feb 28 19:12:25 cventin dbus-daemon[1489]: [session uid=1000 pid=1489] 
Activating via systemd: service name='org.freedesktop.impl.portal.desktop.gtk' 
unit='xdg-desktop-portal-gtk.service' requested by ':1.28' (uid=1000 pid=7168 
comm="/usr/libexec/xdg-desktop-portal")
Feb 28 19:12:25 cventin systemd[1462]: Starting xdg-desktop-portal-gtk.service 
- Portal service (GTK/GNOME implementation)...
Feb 28 19:12:25 cventin dbus-daemon[1489]: [session uid=1000 pid=1489] 
Activating via systemd: service name='org.a11y.Bus' 
unit='at-spi-dbus-bus.service' requested by ':1.31' (uid=1000 pid=7189 
comm="/usr/libexec/xdg-desktop-portal-gtk")
Feb 28 19:12:25 cventin systemd[1462]: Starting at-spi-dbus-bus.service - 
Accessibility services bus...
Feb 28 19:12:25 cventin dbus-daemon[1489]: [session uid=1000 pid=1489] 
Successfully activated service 'org.a11y.Bus'
Feb 28 19:12:25 cventin systemd[1462]: Started at-spi-dbus-bus.service - 
Accessibility services bus.
Feb 28 19:12:25 cventin at-spi-bus-launcher[7197]: dbus-daemon[7197]: 
Activating service name='org.a11y.atspi.Registry' requested by ':1.0' (uid=1000 
pid=7189 comm="/usr/libexec/xdg-desktop-portal-gtk")
Feb 28 19:12:25 cventin at-spi-bus-launcher[7197]: dbus-daemon[7197]: 
Successfully activated service 'org.a11y.atspi.Registry'
Feb 28 19:12:25 cventin at-spi-bus-launcher[7203]: SpiRegistry daemon is 
running with well-known name - org.a11y.atspi.Registry
Feb 28 19:12:25 cventin dbus-daemon[1489]: [session uid=1000 pid=1489] 
Successfully activated service 'org.freedesktop.impl.portal.desktop.gtk'
Feb 28 19:12:25 cventin systemd[1462]: Started xdg-desktop-portal-gtk.service - 
Portal service (GTK/GNOME implementation).
Feb 28 19:12:25 cventin rtkit-daemon[811]: Supervising 3 threads of 1 processes 
of 1 users.
Feb 28 19:12:25 cventin rtkit-daemon[811]: Supervising 3 threads of 1 processes 
of 1 

Bug#1064982: gnuplot-qt: gnuplot displays a window with nothing in it

2024-02-28 Thread Vincent Lefevre
On 2024-02-28 19:20:58 +0100, Vincent Lefevre wrote:
> Before the upgrade to gnuplot 6, everything was fine. But after
> the upgrade, I get a window where nothing is drawn, i.e. I just
> get what's *behind* the window. That's always reproducible on
> this machine.
> 
> I've tried GNUTERM=wxt only. I'll do more tests tomorrow.

Interesting. This is not reproducible when the display is on
another machine (i.e. I connect via ssh). Perhaps an issue
related to the local X server?

-- 
Vincent Lefèvre  - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)



Bug#1064982: gnuplot-qt: gnuplot displays a window with nothing in it

2024-02-28 Thread Vincent Lefevre
Package: gnuplot-qt
Version: 6.0.0+dfsg1-1
Severity: grave
Justification: renders package unusable

Before the upgrade to gnuplot 6, everything was fine. But after
the upgrade, I get a window where nothing is drawn, i.e. I just
get what's *behind* the window. That's always reproducible on
this machine.

I've tried GNUTERM=wxt only. I'll do more tests tomorrow.

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

Versions of packages gnuplot-qt depends on:
ii  gnuplot-data 6.0.0+dfsg1-1
ii  libc62.37-15
ii  libcairo21.18.0-1+local1
ii  libedit2 3.1-20230828-1
ii  libgcc-s114-20240221-2.1
ii  libgd3   2.3.3-9+b1
ii  libglib2.0-0 2.78.4-1
ii  liblua5.4-0  5.4.6-3
ii  libpango-1.0-0   1.52.0+ds-1
ii  libpangocairo-1.0-0  1.52.0+ds-1
ii  libqt5core5a 5.15.10+dfsg-7
ii  libqt5gui5   5.15.10+dfsg-7
ii  libqt5network5   5.15.10+dfsg-7
ii  libqt5printsupport5  5.15.10+dfsg-7
ii  libqt5svg5   5.15.10-2+b1
ii  libqt5widgets5   5.15.10+dfsg-7
ii  libstdc++6   14-20240221-2.1
ii  libwebp7 1.3.2-0.4
ii  libwebpmux3  1.3.2-0.4
ii  libwxbase3.2-1   3.2.4+dfsg-3
ii  libwxgtk3.2-13.2.4+dfsg-3
ii  libx11-6 2:1.8.7-1

gnuplot-qt recommends no packages.

Versions of packages gnuplot-qt suggests:
ii  gnuplot-doc  6.0.0+dfsg1-1

-- no debconf information

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



Bug#1064969: apt: can't upgrade with aptitude

2024-02-28 Thread Vincent Lefevre
On 2024-02-28 18:32:20 +0100, Vincent Lefevre wrote:
> OK, but it appears that now, there are *many* other packages in
> a similar situation, and sometimes, aptitude wants to remove a
> potentially important package (see below). The resolution should
> be automatic in case of package rename.
> 
> # aptitude install libglib2.0-dev

I would add that in this apparently more complex case, apt
(e.g. "apt install libglib2.0-dev" or "apt dist-upgrade") is
far worse than aptitude as it wants to remove wine32:i386.

-- 
Vincent Lefèvre  - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)



Bug#1064969: apt: can't upgrade with aptitude

2024-02-28 Thread Vincent Lefevre
On 2024-02-28 17:28:51 +0100, Sven Joachim wrote:
> On 2024-02-28 15:49 +0100, Vincent Lefevre wrote:
> > So, I suppose that this is also the case for aptitude: if aptitude
> > cannot upgrade just because of a rename, then this is a problem in
> > the involved packages.
> 
> No, in this case it is a problem with aptitude's resolver which
> manifests itself due to the following configuration setting:
> 
> > Aptitude::ProblemResolver::SolutionCost "safety, removals";
> 
> This does cause aptitude to hold apt back by default, rather than
> remove libapt-pkg6.0.

The goal of this configuration setting (which was given in the
debian-user list in the past) was to prevent aptitude from removing
packages with no replacement (e.g. firefox, libreoffice, and so on).
Here, the libapt-pkg6.0 package has been renamed. I hope that you
can understand that this is a completely different situation.

> You can press 'n' at the prompt, the next solution aptitude then
> suggests is to upgrade apt.

OK, but it appears that now, there are *many* other packages in
a similar situation, and sometimes, aptitude wants to remove a
potentially important package (see below). The resolution should
be automatic in case of package rename.

# aptitude install libglib2.0-dev
The following packages will be REMOVED:
  libglib2.0-dev-bin{u}
The following packages will be upgraded:
  libglib2.0-data libglib2.0-dev{b}
2 packages upgraded, 0 newly installed, 1 to remove and 61 not upgraded.
Need to get 2865 kB of archives. After unpacking 716 kB will be freed.
The following packages have unmet dependencies:
 libglib2.0-dev : Depends: libglib2.0-0t64 (= 2.78.4-2) but it is not going to 
be installed
  Depends: libglib2.0-bin (= 2.78.4-2) but 2.78.4-1 is 
installed and it is kept back
  Depends: libglib2.0-dev-bin (= 2.78.4-2) but it is not going 
to be installed
The following actions will resolve these dependencies:

 Keep the following packages at their current version:
1) libglib2.0-dev [2.78.4-1 (now, testing)]
2) libglib2.0-dev-bin [2.78.4-1 (now, testing)]

Accept this solution? [Y/n/q/?] n
The following actions will resolve these dependencies:

 Remove the following packages:
1) libglib2.0-0 [2.78.4-1 (now, testing, unstable)]
2) libglib2.0-0:i386 [2.78.4-1 (now, testing, unstable)]
3) libglib2.0-bin [2.78.4-1 (now, testing)]

 Install the following packages:
4) libglib2.0-0t64 [2.78.4-2 (unstable)]
5) libglib2.0-0t64:i386 [2.78.4-2 (unstable)]
6) libglib2.0-bin:i386 [2.78.4-2 (unstable)]

 Upgrade the following packages:
7) libglib2.0-dev-bin [2.78.4-1 (now, testing) -> 2.78.4-2 (unstable)]

AFAIK, replacing libglib2.0-bin by libglib2.0-bin:i386 is not
equivalent.

With an explicit package list, aptitude immediately gives an
acceptable solution:

$ aptitude install -s libglib2.0-dev libglib2.0-bin libglib2.0-dev-bin 
libglib2.0-0t64 libglib2.0-0t64:i386
The following NEW packages will be installed:
  libglib2.0-0t64 libglib2.0-0t64:i386 
The following packages will be REMOVED:
  libglib2.0-0{a} libglib2.0-0:i386{a} 
The following packages will be upgraded:
  libglib2.0-bin libglib2.0-data libglib2.0-dev libglib2.0-dev-bin 

-- 
Vincent Lefèvre  - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)



Bug#1064969: apt: can't upgrade with aptitude

2024-02-28 Thread Vincent Lefevre
On 2024-02-28 15:56:56 +0100, Julian Andres Klode wrote:
> aptitude is not our chosen tool for distribution upgrades, as such
> failures there are not release critical for the packages. So while
> this is release critical for aptitude, it's a wishlist bug for apt
> that probably would end up being closed.
> 
> I do believe the correct syntax for aptitude would be to use
> 
> aptitude upgrade apt
> 
> though

OK, though this is much slower. But still, apt is not upgraded
with this solution (and there is no way to choose another action
manually):

# aptitude upgrade apt
Resolving dependencies...
The following packages have been kept back:
  apt
No packages will be installed, upgraded, or removed.
0 packages upgraded, 0 newly installed, 0 to remove and 182 not upgraded.
Need to get 0 B of archives. After unpacking 0 B will be used.

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



Bug#1064969: apt: can't upgrade with aptitude

2024-02-28 Thread Vincent Lefevre
Source: apt
Version: 2.7.12+nmu1
Severity: serious

While there are no upgrade issues with apt itself (according
to "apt install -s apt"), aptitude does not want to upgrade
apt automatically, while this just appears to be a package
rename:

# aptitude install apt
The following packages will be upgraded: 
  apt{b} apt-doc 
2 packages upgraded, 0 newly installed, 0 to remove and 180 not upgraded.
Need to get 1622 kB of archives. After unpacking 0 B will be used.
The following packages have unmet dependencies:
 apt : Depends: libapt-pkg6.0t64 (>= 2.7.12+nmu1) but it is not going to be 
installed
 apt-utils : Depends: apt (= 2.7.12) but 2.7.12+nmu1 is to be installed
The following actions will resolve these dependencies:

 Keep the following packages at their current version:
1) apt [2.7.12 (now, testing)]

I don't know whether this is actually an issue with aptitude, but at

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1059068#15

David Kalnischkies says:
| You should really know this by now as that isn't your first report, but
| okay: Upgrade problems are NEVER a problem to be solved in apt,
| they are ALWAYS a problem in the involved packages. NO EXCEPTIONS.

So, I suppose that this is also the case for aptitude: if aptitude
cannot upgrade just because of a rename, then this is a problem in
the involved packages.

-- Package-specific info:

-- apt-config dump --

APT "";
APT::Architecture "amd64";
APT::Build-Essential "";
APT::Build-Essential:: "build-essential";
APT::Install-Recommends "1";
APT::Install-Suggests "0";
APT::Sandbox "";
APT::Sandbox::User "_apt";
APT::Authentication "";
APT::Authentication::TrustCDROM "true";
APT::NeverAutoRemove "";
APT::NeverAutoRemove:: "^firmware-linux.*";
APT::NeverAutoRemove:: "^linux-firmware$";
APT::NeverAutoRemove:: "^linux-image-[a-z0-9]*$";
APT::NeverAutoRemove:: "^linux-image-[a-z0-9]*-[a-z0-9]*$";
APT::VersionedKernelPackages "";
APT::VersionedKernelPackages:: "linux-.*";
APT::VersionedKernelPackages:: "kfreebsd-.*";
APT::VersionedKernelPackages:: "gnumach-.*";
APT::VersionedKernelPackages:: ".*-modules";
APT::VersionedKernelPackages:: ".*-kernel";
APT::Never-MarkAuto-Sections "";
APT::Never-MarkAuto-Sections:: "metapackages";
APT::Never-MarkAuto-Sections:: "tasks";
APT::Move-Autobit-Sections "";
APT::Move-Autobit-Sections:: "oldlibs";
APT::AutoRemove "";
APT::AutoRemove::SuggestsImportant "false";
APT::Clean-Installed "false";
APT::Update "";
APT::Update::Post-Invoke-Success "";
APT::Update::Post-Invoke-Success:: "test -x /usr/bin/apt-show-versions || exit 
0 ; apt-show-versions -i";
APT::Architectures "";
APT::Architectures:: "amd64";
APT::Architectures:: "i386";
APT::Compressor "";
APT::Compressor::. "";
APT::Compressor::.::Name ".";
APT::Compressor::.::Extension "";
APT::Compressor::.::Binary "";
APT::Compressor::.::Cost "0";
APT::Compressor::zstd "";
APT::Compressor::zstd::Name "zstd";
APT::Compressor::zstd::Extension ".zst";
APT::Compressor::zstd::Binary "zstd";
APT::Compressor::zstd::Cost "60";
APT::Compressor::zstd::CompressArg "";
APT::Compressor::zstd::CompressArg:: "-19";
APT::Compressor::zstd::UncompressArg "";
APT::Compressor::zstd::UncompressArg:: "-d";
APT::Compressor::lz4 "";
APT::Compressor::lz4::Name "lz4";
APT::Compressor::lz4::Extension ".lz4";
APT::Compressor::lz4::Binary "false";
APT::Compressor::lz4::Cost "50";
APT::Compressor::gzip "";
APT::Compressor::gzip::Name "gzip";
APT::Compressor::gzip::Extension ".gz";
APT::Compressor::gzip::Binary "gzip";
APT::Compressor::gzip::Cost "100";
APT::Compressor::gzip::CompressArg "";
APT::Compressor::gzip::CompressArg:: "-6n";
APT::Compressor::gzip::UncompressArg "";
APT::Compressor::gzip::UncompressArg:: "-d";
APT::Compressor::xz "";
APT::Compressor::xz::Name "xz";
APT::Compressor::xz::Extension ".xz";
APT::Compressor::xz::Binary "xz";
APT::Compressor::xz::Cost "200";
APT::Compressor::xz::CompressArg "";
APT::Compressor::xz::CompressArg:: "-6";
APT::Compressor::xz::UncompressArg "";
APT::Compressor::xz::UncompressArg:: "-d";
APT::Compressor::bzip2 "";
APT::Compressor::bzip2::Name "bzip2";
APT::Compressor::bzip2::Extension ".bz2";
APT::Compressor::bzip2::Binary "bzip2";
APT::Compressor::bzip2::Cost "300";
APT::Compressor::bzip2::CompressArg "";
APT::Compressor::bzip2::CompressArg:: "-6";
APT::Compressor::bzip2::UncompressArg "";
APT::Compressor::bzip2::UncompressArg:: "-d";
APT::Compressor::lzma "";
APT::Compressor::lzma::Name "lzma";
APT::Compressor::lzma::Extension ".lzma";
APT::Compressor::lzma::Binary "xz";
APT::Compressor::lzma::Cost "400";
APT::Compressor::lzma::CompressArg "";
APT::Compressor::lzma::CompressArg:: "--format=lzma";
APT::Compressor::lzma::CompressArg:: "-6";
APT::Compressor::lzma::UncompressArg "";
APT::Compressor::lzma::UncompressArg:: "--format=lzma";
APT::Compressor::lzma::UncompressArg:: "-d";
Dir "/";
Dir::State "var/lib/apt";
Dir::State::lists "lists/";
Dir::State::cdroms "cdroms.list";
Dir::State::extended_states "extended_states";
Dir::State::status 

Bug#1055067: isc-dhcp-client: network-manager 1.44.2-3 changed path to nm-dhcp-helper, apparmor need update

2024-02-25 Thread Vincent Lefevre
On 2024-02-26 00:22:01 +0100, Sven-Haegar Koch wrote:
> While installing your test package I lost wifi connection, but I think 
> that was not from your package but from updating network-manager from 
> unstable at the same time (did dist-upgrade), which always breaks my 
> network.

With the future stable upgrade, it would be very bad to lose the
network connection (not just wifi is concerned) during the upgrade.
I suppose that once the new isc-dhcp-client package is available,
network-manager should break the old versions (something like that...
I don't know whether this is sufficient).

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



Bug#1064500: avahi-autoipd: should stop recommending isc-dhcp-client

2024-02-23 Thread Vincent Lefevre
Package: avahi-autoipd
Version: 0.8-13+b1
Severity: wishlist

ISC no longer maintains the client part of isc-dhcp.
Moreover, isc-dhcp-client no longer works with NetworkManager.
avahi-autoipd should use an alternative DHCP client.

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

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

Versions of packages avahi-autoipd depends on:
ii  adduser 3.137
ii  libc6   2.37-15
ii  libdaemon0  0.14-7.1

Versions of packages avahi-autoipd recommends:
ii  iproute2 6.7.0-2
ii  isc-dhcp-client  4.4.3-P1-5

avahi-autoipd suggests no packages.

-- no debconf information

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



Bug#1064469: debgpt: does not handle errors

2024-02-22 Thread Vincent Lefevre
Package: debgpt
Version: 0.4.94
Severity: minor

debgpt does not handle errors:

qaa:~> debgpt -Q -A "who are you?"
[19:06:24] OpenAIFrontend> Starting conversation  frontend.py:66
[...]
LLM[2]> Traceback (most recent call last):
  File "/bin/debgpt", line 8, in 
sys.exit(main())
 ^^
  File "/usr/lib/python3/dist-packages/debgpt/cli.py", line 455, in main
frontend.query_once(f, msg)
  File "/usr/lib/python3/dist-packages/debgpt/frontend.py", line 218, in 
query_once
reply = f(text)
^^^
  File "/usr/lib/python3/dist-packages/debgpt/frontend.py", line 96, in __call__
return self.query(*args, **kwargs)
   ^^^
  File "/usr/lib/python3/dist-packages/debgpt/frontend.py", line 131, in query
completion = self.client.chat.completions.create(
 
  File "/usr/lib/python3/dist-packages/openai/_utils/_utils.py", line 275, in 
wrapper
return func(*args, **kwargs)
   ^
  File "/usr/lib/python3/dist-packages/openai/resources/chat/completions.py", 
line 663, in create
return self._post(
   ^^^
  File "/usr/lib/python3/dist-packages/openai/_base_client.py", line 1200, in 
post
return cast(ResponseT, self.request(cast_to, opts, stream=stream, 
stream_cls=stream_cls))
   
^
  File "/usr/lib/python3/dist-packages/openai/_base_client.py", line 889, in 
request
return self._request(
   ^^
  File "/usr/lib/python3/dist-packages/openai/_base_client.py", line 980, in 
_request
raise self._make_status_error_from_response(err.response) from None
openai.AuthenticationError: Error code: 401 - {'error': {'message': 'Incorrect 
API key provided: empty. You can find your API key at 
https://platform.openai.com/account/api-keys.', 'type': 
'invalid_request_error', 'param': None, 'code': 'invalid_api_key'}}

I would expect just a clear error message.

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

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

Versions of packages debgpt depends on:
ii  python3 3.11.6-1
ii  python3-bs4 4.12.3-1
ii  python3-openai  1.12.0-1
ii  python3-prompt-toolkit  3.0.43-1
ii  python3-requests2.31.0+dfsg-1
ii  python3-rich13.3.1-2
ii  python3-tomli   2.0.1-2

Versions of packages debgpt recommends:
ii  git  1:2.43.0-1
ii  man-db   2.12.0-3
ii  python3-zmq  24.0.1-5+b1
ii  tldr 0.9.2-5

Versions of packages debgpt suggests:
pn  python3-torch | python3-torch-cuda | python3-torch-rocm  
pn  python3-transformers 

-- no debconf information

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



Bug#1064402: luametatex: "mtxrun --generate": lua error : startup file: /bin/mtxrun.lua:2438: attempt to assign to const variable 'i'

2024-02-21 Thread Vincent Lefevre
Control: retitle -1 luametatex: "mtxrun --generate": lua error : startup file: 
/bin/mtxrun.lua:2438: attempt to assign to const variable 'i'

More accurate title, as described below.

On 2024-02-21 16:15:31 +0100, Vincent Lefevre wrote:
> Indeed, I can reproduce the problem on another machine, only with
> luametatex 2.11.01+ds-2:
> 
> qaa:~> mtxrun --generate
> lua error : startup file: /bin/mtxrun.lua:2438: attempt to assign to const 
> variable 'i'
> 
> You'll see the failure in an upgrade if you upgrade luametatex at the
> same time as the TeX Live packages (at least, *not after* TeX Live).

-- 
Vincent Lefèvre  - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)



Bug#1064402: texlive-binaries: tex-common configure: lua error : startup file: /bin/mtxrun.lua:2438: attempt to assign to const variable 'i'

2024-02-21 Thread Vincent Lefevre
Control: reassign -1 luametatex 2.11.01+ds-2
Control: severity -1 grave
Control: affects -1 texlive-binaries

On 2024-02-21 15:46:04 +0100, Vincent Lefevre wrote:
> On 2024-02-21 15:28:17 +0100, Vincent Lefevre wrote:
> > /tmp/mtxrun.gd7J0NKo just contains:
> > 
> > lua error : startup file: /bin/mtxrun.lua:2438: attempt to assign to const 
> > variable 'i'
> > 
> > Note: the tex-common and context (from which /bin/mtxrun.lua comes
> > from) are still old packages, and there were no issues with them
> > in the past. So I assume that the bug has been introduced in
> > /usr/bin/texlua (/bin/mtxrun.lua is a texlua script), which is
> > provided by texlive-binaries.
> 
> Or it could be due to luametatex, which appears in /bin/mtxrun.lua
> and has been upgraded:
> 
> 2024-02-21 14:47:52 upgrade luametatex:amd64 2.10.08+ds-1+b1 2.11.01+ds-2

Indeed, I can reproduce the problem on another machine, only with
luametatex 2.11.01+ds-2:

qaa:~> mtxrun --generate
lua error : startup file: /bin/mtxrun.lua:2438: attempt to assign to const 
variable 'i'

You'll see the failure in an upgrade if you upgrade luametatex at the
same time as the TeX Live packages (at least, *not after* TeX Live).

-- 
Vincent Lefèvre  - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)



Bug#1064402: texlive-binaries: tex-common configure: lua error : startup file: /bin/mtxrun.lua:2438: attempt to assign to const variable 'i'

2024-02-21 Thread Vincent Lefevre
On 2024-02-21 15:28:17 +0100, Vincent Lefevre wrote:
> /tmp/mtxrun.gd7J0NKo just contains:
> 
> lua error : startup file: /bin/mtxrun.lua:2438: attempt to assign to const 
> variable 'i'
> 
> Note: the tex-common and context (from which /bin/mtxrun.lua comes
> from) are still old packages, and there were no issues with them
> in the past. So I assume that the bug has been introduced in
> /usr/bin/texlua (/bin/mtxrun.lua is a texlua script), which is
> provided by texlive-binaries.

Or it could be due to luametatex, which appears in /bin/mtxrun.lua
and has been upgraded:

2024-02-21 14:47:52 upgrade luametatex:amd64 2.10.08+ds-1+b1 2.11.01+ds-2

-- 
Vincent Lefèvre  - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)



Bug#1064402: texlive-binaries: tex-common configure: lua error : startup file: /bin/mtxrun.lua:2438: attempt to assign to const variable 'i'

2024-02-21 Thread Vincent Lefevre
Package: texlive-binaries
Version: 2023.20230311.66589-8+b1
Severity: serious

When upgrading TeX Live:

[...]
Processing triggers for tex-common (6.18) ...
Running mktexlsr. This may take some time... done.
Running mtxrun --generate. This may take some time... 
mtxrun --generate failed. Output has been stored in
/tmp/mtxrun.gd7J0NKo
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

/tmp/mtxrun.gd7J0NKo just contains:

lua error : startup file: /bin/mtxrun.lua:2438: attempt to assign to const 
variable 'i'

Note: the tex-common and context (from which /bin/mtxrun.lua comes
from) are still old packages, and there were no issues with them
in the past. So I assume that the bug has been introduced in
/usr/bin/texlua (/bin/mtxrun.lua is a texlua script), which is
provided by texlive-binaries.

-- 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 4243 2024-02-21 14:57:26 /var/lib/texmf/ls-R
lrwxrwxrwx 1 root root 29 2022-10-12 23:25:33 /usr/share/texmf/ls-R -> 
/var/lib/texmf/ls-R-TEXMFMAIN
lrwxrwxrwx 1 root root 31 2024-02-14 15:08:19 
/usr/share/texlive/texmf-dist/ls-R -> /var/lib/texmf/ls-R-TEXLIVEDIST
lrwxrwxrwx 1 root root 31 2024-02-14 15:08:19 
/usr/share/texlive/texmf-dist/ls-R -> /var/lib/texmf/ls-R-TEXLIVEDIST
##
 Config files
-rw-r--r-- 1 root root 475 2024-02-21 14:57:26 /etc/texmf/web2c/texmf.cnf
lrwxrwxrwx 1 root root 33 2024-02-14 15:08:19 
/usr/share/texmf/web2c/fmtutil.cnf -> /var/lib/texmf/fmtutil.cnf-DEBIAN
lrwxrwxrwx 1 root root 32 2024-02-14 15:08:19 /usr/share/texmf/web2c/updmap.cfg 
-> /var/lib/texmf/updmap.cfg-DEBIAN
-rw-r--r-- 1 root root 5334 2024-02-21 14:57:26 
/var/lib/texmf/tex/generic/config/language.dat
##
 Files in /etc/texmf/web2c/
total 8
-rw-r--r-- 1 root root 283 2014-10-21 02:46:09 mktex.cnf
-rw-r--r-- 1 root root 475 2024-02-21 14:57:26 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'), (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)

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

Versions of packages texlive-binaries depends on:
ii  libc6   2.37-15
ii  libcairo2   1.18.0-1+b1
ii  libfontconfig1  2.15.0-1
ii  libfreetype62.13.2+dfsg-1+b1
ii  libgcc-s1   14-20240201-3
ii  libgraphite2-3  1.3.14-2
ii  libharfbuzz0b   8.3.0-2
ii  libicu7272.1-4+b1
ii  libkpathsea62023.20230311.66589-8+b1
ii  libmpfr64.2.1-1
ii  libpaper1 

Bug#854149: affected fonts

2024-02-18 Thread Vincent Lefevre
On 2018-03-16 21:40:56 +0100, Horst Schirmeier wrote:
> My test case: echo -e 'a\u0308a'
> 
> Correct rendering: äa
> (That's what I see with: Courier, Cousine, DejaVu Sans Mono, FreeMono)
> 
> Incorrect rendering: aä
> (That's what I see with: Andale Mono, Bitstream Vera Sans Mono, Courier
> 10 Pitch, Courier New, Hack Mono, Liberation Mono, Mitra Mono, Nimbus
> Mono L, Noto Mono, Oxygen Mono, Tlwg Mono, Tlwg Typo, Ubuntu Mono)

With libvte-2.91-0 0.75.91-2, I get äa as expected with DejaVu Sans Mono
and Liberation Mono.

But

echo -e '1\u03362'

is incorrect with both, though the result is different:
with DejaVu Sans Mono, I get a strikethrough 2, but with
Liberation Mono, the strikethrough is between 1 and 2.
And for

echo -e '...c\u20dd...'

the circle is after the c is both cases.

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



Bug#1063905: mksh: /usr/bin/mksh and /usr/bin/mksh-static are no longer in /etc/shells

2024-02-14 Thread Vincent Lefevre
Control: reopen 1063905

On 2024-02-14 15:22:43 +, Thorsten Glaser wrote:
> Vincent Lefevre dixit:
> 
> >/usr/bin/mksh and /usr/bin/mksh-static are no longer in /etc/shells:
> 
> That’s correct. Their presence was a bug caused by add-shells
> misbehaviour which I have worked around in maintainer scripts.
> They should never have been in there.

This is not a bug in add-shell, but done on purpose as the presence
of the real path in /etc/shells is *needed* by some programs. See

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

-- 
Vincent Lefèvre  - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)



Bug#1063905: mksh: /usr/bin/mksh and /usr/bin/mksh-static are no longer in /etc/shells

2024-02-14 Thread Vincent Lefevre
Package: mksh
Version: 59c-34
Severity: normal

/usr/bin/mksh and /usr/bin/mksh-static are no longer in /etc/shells:

This is an automated report from zira.
Recent changes to /etc/shells:

4 -rw-r--r-- 1 root root 325 Feb  7 11:07 /etc/shells

diff  -Ndu  /var/cache/diffmon/old_file_dir/zira:!etc!shells.gz /etc/shells
--- /tmp/diffmon60322024-02-08 07:37:34.427704557 +0100
+++ /etc/shells 2024-02-07 11:07:49.984040544 +0100
@@ -15,8 +15,6 @@
 /usr/bin/rbash
 /usr/bin/dash
 /usr/bin/zsh-static
-/usr/bin/mksh
-/usr/bin/mksh-static
 /usr/bin/yash
 /usr/bin/fish
 /bin/ksh93

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

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

Versions of packages mksh depends on:
ii  libc6  2.37-15

Versions of packages mksh recommends:
ii  ed  1.20-1

mksh suggests no packages.

-- no debconf information

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



Bug#1063529: wdiff: broken when the input contains a null character

2024-02-09 Thread Vincent Lefevre
Package: wdiff
Version: 1.2.2-6
Severity: normal

wdiff is broken when the input contains a null character.
For instance, create 2 files a and b with

  printf "a\n2\n3\n4\n5\n6\n7\n8\n" > a
  printf "b\n2\n3\n4\n5\n6\n7\n8\n\000\n" > b

$ wdiff a b
b
2
3
4
5
6
7
8

instead of something like

[-a-]{+b+}
2
3
4
5
6
7
8
{+^@+}

Similarly, the following is incorrect:

$ diff -au a b | wdiff -d
++ b2024-02-09 14:11:23.981863795 +0100
@@ -1,4 +1,4 @@
b
2
3
4
@@ -6,3 +6,4 @@
6
7
8

There is no such issue if I replace \000 by \001.
So this is specific to the null character.

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

Versions of packages wdiff depends on:
ii  libc6  2.37-15
ii  libtinfo6  6.4+20240113-1

wdiff recommends no packages.

Versions of packages wdiff suggests:
ii  wdiff-doc  1.2.2-6

-- no debconf information

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



Bug#1063522: file: does not recognize unified diff file with binary data

2024-02-09 Thread Vincent Lefevre
Control: tags -1 upstream fixed-upstream

On 2024-02-09 13:51:20 +0100, Vincent Lefevre wrote:
> Debian's file utility does not recognize unified diff file with
> binary data. To reproduce, create 2 files a and b with
> 
>   { seq 1 9 && printf "\001"; } > a
>   { seq 2 9 && printf "\002"; } > b
> 
> Then
> 
> $ diff -u a b | /usr/bin/file -
> /dev/stdin: data
> 
> There is no such issue with "file" from https://github.com/file/file
> for which I get
> 
> $ diff -u a b | file -
> /dev/stdin: unified diff output text
> 
> as expected.

After testing, I could see that this is the following upstream commit

  https://github.com/file/file/commit/ed96f0ee95090c799b9215cc81f1a6095d81e5c8

that fixes the issue.

-- 
Vincent Lefèvre  - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)



Bug#1063522: file: does not recognize unified diff file with binary data

2024-02-09 Thread Vincent Lefevre
Package: file
Version: 1:5.45-2+b1
Severity: normal

Debian's file utility does not recognize unified diff file with
binary data. To reproduce, create 2 files a and b with

  { seq 1 9 && printf "\001"; } > a
  { seq 2 9 && printf "\002"; } > b

Then

$ diff -u a b | /usr/bin/file -
/dev/stdin: data

There is no such issue with "file" from https://github.com/file/file
for which I get

$ diff -u a b | file -
/dev/stdin: unified diff output text

as expected.

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

Versions of packages file depends on:
ii  libc6  2.37-15
ii  libmagic1  1:5.45-2+b1

file recommends no packages.

file suggests no packages.

-- no debconf information

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



Bug#1063405: sensible-utils: error "realpath: '': No such file or directory" / possible recursive loop

2024-02-07 Thread Vincent Lefevre
Package: sensible-utils
Version: 0.0.22
Severity: normal

After the upgrade to 0.0.22, I'm getting the following error with
sensible-pager:

realpath: '': No such file or directory

(the other sensible-* utilities are likely to have the same issue
since the related code is very similar).

This is due to

# Prevent recursive loops, where environment variables are set to this 
script
[ x$(realpath "$(command -v "$candidate" || true)" || true) = x"$program" ] 
&& return

where $candidate is a command with arguments. For instance,
I have PAGER="less -Lis". Hence the issue.

The full string for "command -v" is expected to be the executable name
(without arguments). So the executable is not found, and "command -v"
fails without any output, so that realpath outputs an error to stderr
for this reason.

There is the same issue when the command doesn't exist:

cventin:~> PAGER=foo sensible-pager
realpath: '': No such file or directory
PAGER: 1: foo: not found
Missing filename ("less --help" for help)

In any case, the "realpath: '': No such file or directory" just
concerns internals and should be hidden from the user.

The problem is actually worse than the error message as there can
be a loop:

cventin:~> PAGER="sensible-pager " sensible-pager
realpath: '': No such file or directory
realpath: '': No such file or directory
realpath: '': No such file or directory
realpath: '': No such file or directory
realpath: '': No such file or directory
realpath: '': No such file or directory
realpath: '': No such file or directory
realpath: '': No such file or directory
realpath: '': No such file or directory
realpath: '': No such file or directory
[...]

So I suggest 2 fixes:

1. In the candidate, take only everything until the first space,
   i.e. use "${candidate%% *}" instead of "$candidate".

2. Redirect the realpath standard error to /dev/null in order to
   avoid the error message when the executable is not found.

This gives:

# Prevent recursive loops, where environment variables are set to this 
script
[ x$(realpath "$(command -v "${candidate%% *}" || true)" 2> /dev/null || 
true) = x"$program" ] && return

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

-- no debconf information

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



Bug#953998: closing 953998

2024-01-29 Thread Vincent Lefevre
On 2024-01-29 19:52:33 +0100, Laurent Bigonville wrote:
> I see that the patch has been merged upstream.
> 
> I guess that this bug can be closed?

However, the Debian package has not been updated yet.

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



Bug#718446: tracker-extract possibly prevents shutdown to complete

2024-01-29 Thread Vincent Lefevre
On 2024-01-29 15:03:44 +, Simon McVittie wrote:
> On Mon, 29 Jan 2024 at 15:22:31 +0100, Vincent Lefevre wrote:
> > However, in my case,
> > tracker-extract (gst-plugin-scan) was yielding a crash in nouveau
> > 
> > 2023-12-19T03:10:02.176832+01:00 qaa tracker-extract-3[1967]: 
> > nvc0_screen_create:1077 - Error allocating PGRAPH context for M2MF: -16
> > 2023-12-19T03:10:02.177550+01:00 qaa kernel: [ cut here 
> > ]
> > 2023-12-19T03:10:02.177568+01:00 qaa kernel: nouveau :01:00.0: timeout
> > [...]
> > 2023-12-19T03:10:02.177710+01:00 qaa kernel: CPU: 3 PID: 1967 Comm: 
> > gst-plugin-scan Tainted: GW  6.5.0-5-amd64 #1  Debian 
> > 6.5.13-1
> 
> That's certainly a kernel/driver bug. In principle it should not be
> possible for Tracker to cause a crash in kernel code (was this an OOPS
> or a BUG message or what?), even if it wanted to do this intentionally.

No OOPS / BUG messages, just "nouveau :01:00.0: timeout". Xorg
also triggered this error. This was due to missing symbolic links
in the firmware-misc-nonfree package:

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

-- 
Vincent Lefèvre  - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)



Bug#718446: tracker-extract possibly prevents shutdown to complete

2024-01-29 Thread Vincent Lefevre
On 2013-07-31 23:41:49 +0200, Sebastian Niehaus wrote:
> Am 31.07.2013 23:15, schrieb Michael Biebl:
> 
> >> I suppose the other processes regarding NFS are okay to be running after 
> >> /etc/init.d/sendsigs but tracker-extract should have been finished. 
> > 
> > Are you using NFS for your $HOME directory?
> 
> No, $HOME is on the maschine's local disk.
> 
> The NFS file system however is mounted into one user's home like
> 
> /home/user1/nfs

IMHO, the process should stop immediately at shutdown and not try
to finish its task first.

When I upgraded a machine from stable to testing in December 2023,
tracker-extract was also preventing the shutdown (always, AFAIK),
and I had no NFS, just the local disk. However, in my case,
tracker-extract (gst-plugin-scan) was yielding a crash in nouveau

2023-12-19T03:10:02.176832+01:00 qaa tracker-extract-3[1967]: 
nvc0_screen_create:1077 - Error allocating PGRAPH context for M2MF: -16
2023-12-19T03:10:02.177550+01:00 qaa kernel: [ cut here 
]
2023-12-19T03:10:02.177568+01:00 qaa kernel: nouveau :01:00.0: timeout
[...]
2023-12-19T03:10:02.177710+01:00 qaa kernel: CPU: 3 PID: 1967 Comm: 
gst-plugin-scan Tainted: GW  6.5.0-5-amd64 #1  Debian 6.5.13-1

and gst-plugin-scan even survived SIGKILL:

[...]
2023-12-19T03:13:06.240298+01:00 qaa systemd[2079]: tracker-extract-3.service: 
State 'final-sigterm' timed out. Killing.
2023-12-19T03:13:06.240435+01:00 qaa systemd[2079]: tracker-extract-3.service: 
Killing process 2150 (gst-plugin-scan) with signal SIGKILL.
2023-12-19T03:13:40.973708+01:00 qaa kernel: INFO: task gst-plugin-scan:2150 
blocked for more than 120 seconds.
2023-12-19T03:13:40.973803+01:00 qaa kernel:   Tainted: GW  
6.5.0-5-amd64 #1 Debian 6.5.13-1
2023-12-19T03:13:40.973810+01:00 qaa kernel: "echo 0 > 
/proc/sys/kernel/hung_task_timeout_secs" disables this message.
2023-12-19T03:13:40.973816+01:00 qaa kernel: task:gst-plugin-scan state:D 
stack:0 pid:2150  ppid:2079   flags:0x0006
[...]
2023-12-19T03:14:36.240345+01:00 qaa systemd[2079]: tracker-extract-3.service: 
Processes still around after final SIGKILL. Entering failed mode.
[...]

So perhaps in this particular case, there was nothing that could
be done on the tracker-extract side, but I'm wondering.

Since then, the nouveau issue has been fixed, but I had removed
tracker-extract earlier, and I didn't try again to see whether
the problem was solved about it.

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



Bug#1061734: aptitude: in TUI, incorrect "will be automatically removed because of dependency errors" message

2024-01-29 Thread Vincent Lefevre
Note that there was a similar bug in the past (2005, fixed in 2016):

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

with title:

  aptitude: "X will be automatically removed because of dependency errors:"
  then no errors shown

On 2024-01-29 11:20:45 +0100, Vincent Lefevre wrote:
> When I choose to upgrade swig from the TUI, I get the incorrect message
> 
> 
> swig4.0 (remove, 4.1.0-0.3) will be automatically removed because of
> dependency errors:
> 
> 
> with nothing else.

I cannot reproduce this issue on another machine, which doesn't have
a foreign architecture. I get just after 'g' and putting the cursor
over the swig4.0 line:


swig4.0 (remove, 4.1.0-0.3) will be automatically removed because of dependency
errors:

  * swig (upgrade, 4.1.0-0.3 -> 4.2.0-1) conflicts with swig4.0


However, AFAIK, it will be automatically removed not because of the
conflict, but because the new swig package no longer depends on it
(on both machines, swig4.0 is marked as automatically installed).

This is a different message from

> Then, when I type ':' over the swig4.0 line, this message changes to:
> 
> 
> swig4.0 (remove, 4.1.0-0.3) was installed automatically; it is being removed
> because all of the packages which depend upon it are being removed:
> 
>   * swig (upgrade, 4.1.0-0.3 -> 4.2.0-1) depends on swig4.0 (>= 4.1.0-0.3)
> (provided by swig4.0:i386 4.1.0-0.3)
> 

-- 
Vincent Lefèvre  - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)



Bug#1061734: aptitude: in TUI, incorrect "will be automatically removed because of dependency errors" message

2024-01-29 Thread Vincent Lefevre
Package: aptitude
Version: 0.8.13-5+b1
Severity: normal

When I choose to upgrade swig from the TUI, I get the incorrect message


swig4.0 (remove, 4.1.0-0.3) will be automatically removed because of dependency
errors:


with nothing else.

With more details:

I currently have

i   swig   4.1.0-0.34.2.0-1

Over this line, I type '+', so that I get:

aptitude 0.8.13 @ cventinDisk: -184 kB   DL: 1429 kB
[...]
iu  swig +5509 kB  4.1.0-0.34.2.0-1

Now, I type 'g', and I get:

--\ Packages to be upgraded (1) 
iu  swig +5509 kB  4.1.0-0.34.2.0-1 
--\ Packages being deleted due to unsatisfied dependencies (1)
idA swig4.0  -5693 kB  4.1.0-0.34.1.0-0.3   
--\ Packages being held back (15)
[...]

Over the swig line, I get:


swig (upgrade, 4.1.0-0.3 -> 4.2.0-1) will be upgraded from version 4.1.0-0.3 to
version 4.2.0-1.


Over the swig4.0 line, I get:


swig4.0 (remove, 4.1.0-0.3) will be automatically removed because of dependency
errors:


with nothing else. Without any error message, this doesn't make sense.

Then, when I type ':' over the swig4.0 line, this message changes to:


swig4.0 (remove, 4.1.0-0.3) was installed automatically; it is being removed
because all of the packages which depend upon it are being removed:

  * swig (upgrade, 4.1.0-0.3 -> 4.2.0-1) depends on swig4.0 (>= 4.1.0-0.3)
(provided by swig4.0:i386 4.1.0-0.3)


Now this is almost correct. I don't understand the ":i386". This is
a configured foreign architecture on this machine, but this package
is not installed:

cventin:~> dpkg -l | grep swig
ii  swig   4.1.0-0.3
all  Generate scripting interfaces to C/C++ code
ii  swig4.04.1.0-0.3
amd64Generate scripting interfaces to C/C++ code

Note that with the currently installed swig package:

Package: swig
Version: 4.1.0-0.3
[...]
Architecture: all
Replaces: swig2.0
Depends: swig4.0 (>= 4.1.0-0.3)
Suggests: swig-doc, swig-examples
Conflicts: swig2.0

and with the new version:

Package: swig
Version: 4.2.0-1
[...]
Architecture: amd64
Replaces: swig4.0
Depends: libc6 (>= 2.34), libgcc-s1 (>= 3.0), libpcre2-8-0 (>= 10.22), 
libstdc++6 (>= 13.1)
Suggests: swig-doc, swig-examples
Conflicts: swig4.0

-- Package-specific info:
Terminal: xterm-256color
$DISPLAY is set.
which aptitude: /bin/aptitude

aptitude version information:
aptitude 0.8.13
Compiler: g++ 13.2.0
Compiled against:
  apt version 6.0.0
  NCurses version 6.4
  libsigc++ version: 2.12.1
  Gtk+ support disabled.
  Qt support disabled.

Current library versions:
  NCurses version: ncurses 6.4.20240113
  cwidget version: 0.5.18
  Apt version: 6.0.0

aptitude linkage:
linux-vdso.so.1 (0x7ffeeaddb000)
libgtk3-nocsd.so.0 => /lib/x86_64-linux-gnu/libgtk3-nocsd.so.0 
(0x7fa687a8f000)
libapt-pkg.so.6.0 => /lib/x86_64-linux-gnu/libapt-pkg.so.6.0 
(0x7fa68720)
libncursesw.so.6 => /lib/x86_64-linux-gnu/libncursesw.so.6 
(0x7fa687a55000)
libtinfo.so.6 => /lib/x86_64-linux-gnu/libtinfo.so.6 
(0x7fa6875cb000)
libsigc-2.0.so.0 => /lib/x86_64-linux-gnu/libsigc-2.0.so.0 
(0x7fa687a4c000)
libcwidget.so.4 => /lib/x86_64-linux-gnu/libcwidget.so.4 
(0x7fa6874c9000)
libsqlite3.so.0 => /lib/x86_64-linux-gnu/libsqlite3.so.0 
(0x7fa68708a000)
libboost_iostreams.so.1.83.0 => 
/lib/x86_64-linux-gnu/libboost_iostreams.so.1.83.0 (0x7fa6874af000)
libxapian.so.30 => /lib/x86_64-linux-gnu/libxapian.so.30 
(0x7fa686e0)
libstdc++.so.6 => /lib/x86_64-linux-gnu/libstdc++.so.6 
(0x7fa686a0)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7fa686d21000)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 
(0x7fa687482000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7fa68681e000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7fa687a43000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 
(0x7fa68747d000)
libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x7fa68745e000)
libbz2.so.1.0 => /lib/x86_64-linux-gnu/libbz2.so.1.0 
(0x7fa68744b000)
liblzma.so.5 => /lib/x86_64-linux-gnu/liblzma.so.5 

Bug#1061148: apt: option -a has several meanings and is unusable

2024-01-26 Thread Vincent Lefevre
On 2024-01-19 18:38:06 +0100, David Kalnischkies wrote:
> On Fri, Jan 19, 2024 at 05:10:40PM +0100, Vincent Lefevre wrote:
> > The -a=... version is not documented in the manual, only -a alone,
> 
> Compare -t, which also doesn't say -t=foo. Probably mostly due to -t foo
> working as well or just because the manpages like their inconsistencies
> and would deserve some love, but who has the time to not just complain
> but also actually write all of it…

This is not the same thing. The -t option is listed only with an
argument, while there is a -a option *without* an argument:

  apt-get [-asqdyfmubV] ... [-a=architecture] ...
^ here

Perhaps this is a mistake...

> (reordered for posterity)
> 
> >-a, --host-architecture
> >This option controls the architecture packages are built for by
> >apt-get source --compile and how cross-builddependencies are
> >satisfied.
> > 
> > There are 2 verbs "controls" and "are built". And I don't see how
> > to parse "for by".
> 
> A package is "built for" the given (with -a) host architecture by
> "apt-get source --compile" – aka its instructed to cross-compile
> a package for the given host architecture instead of doing a "normal"
> compile where host and build architecture are the same.

OK, it took me some time to find how this sentence should be parsed.
In particular, I thought that this description was for the -a version
without an argument (see above), and the sentence couldn't have any
sense as a consequence.

BTW, in the option listing, whether an option takes an argument is
generally indicated. For instance, in the cp man page:

   -S, --suffix=SUFFIX
  override the usual backup suffix

And simpler sentences would be easier to understand, with the context
given first. For instance, something like

  With "apt-get source --compile", packages are built for the
  given architecture instead of [...]

Or more explicitly:

-a, --host-architecture=ARCH
  With "apt-get source --compile", packages are built for
  architecture ARCH instead of [...]

> So, "apt-get source -b -a armhf foo" will (simplified) build a
> "foo_armhf.deb" on your (likely amd64) machine to be used on another
> (probably less powerful) armhf machine. Similar for build-dep, just
> that this won't build anything but interprets certain dependencies
> differently.

If build-dep is also concerned by this option, this should be said.

> >By default is it not set which means that the host
> >architecture is the same as the build architecture (which is
> >defined by APT::Architecture). Configuration Item:
> >APT::Get::Host-Architecture.
> 
> > In the next sentence: "is it". Should this be
> > "it is"? The comma is missing before "which".
> 
> Perhaps it should, "is it not" has the hint of a question. In German
> I would write such a sentence without a comma as the added phrase isn't
> [that] optional, but not sure if a German – or English – teacher would
> actually agree on me claiming "definition phrase", which are not
> separated by commas in both languages. Could easily be done without
> a which if we were really trying.

Here, "which means..." relates to an entire statement ("it is not set"),
so that a comma is needed. See

  https://guinlist.wordpress.com/tag/clause-referring-which/

"2. Relating to an Entire Statement
[...]
(c) Octavian defeated his enemies in battle, which enabled him to
become Roman Emperor.

/Which/ here refers to what /Octavian/ did, not the /battle/.

In this usage, /which/ is always needed instead of /who/ or /that/, it
always follows a comma, and it has a singular verb after it. [...]"
^^

Or this (in French):

  
https://www.anglaisfacile.com/exercices/exercice-anglais-2/exercice-anglais-26463.php

(this is the case where "which" is translated in French by "ce que"
or "ce qui", instead of just "que" or "qui" when "which" relates to
a noun).

-- 
Vincent Lefèvre  - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)



Bug#1061423: xpdf: performance of a second text search should be improved

2024-01-25 Thread Vincent Lefevre
Hi Adam,

On 2024-01-24 18:08:25 +, Adam Sampson wrote:
> On Wed, Jan 24, 2024 at 11:30:01AM +0100, Vincent Lefevre wrote:
> > With zathura, the first search needs the same time as xpdf, but a
> > second search is much faster (almost immediate). xpdf text search
> > should be improved to be as fast as zathura.
> 
> Looking at the code, Zathura uses poppler-glib, which implements search
> in the same way as xpopple -- it renders each page to a TextPage object
> and searches the text strings in that. However, poppler-glib caches the
> TextPages once they've been rendered, whereas xpopple renders them again
> for each new search.
> 
> I've just pushed a commit to xpopple git to add a similar cache, which
> seems to have the desired effect. It'll use a bit more memory this way
> but I don't expect it'll be a concern relative to the size of the rest
> of the PDF data...

Thanks. On PDF files with many pages (e.g., large books), it can
actually take much more memory, but I think that this is beneficial
in general. On such files, this is where a text search would take
time without the cache.

For instance, for the POSIX spec (3952 pages), which is quite an
extreme case, the RSS memory increases from 55 MB to 3.4 GB after a
search across the full document. For the Debian handbook (498 pages),
which is a rather large book, the RSS memory increases from 37 MB to
430 MB (which is less than what Firefox takes on my machine).

I think that if memory is an issue for some users, the cache could be
made optional. Or perhaps poppler-glib could be improved to provide
a cache just for text (for the POSIX spec, the full text itself just
takes about 10 MB).

-- 
Vincent Lefèvre  - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)



Bug#1032428: firefox: Menu handling with the mouse is broken

2024-01-24 Thread Vincent Lefevre
On 2023-05-05 17:37:02 +0200, Vincent Lefevre wrote:
> Actually not completely fixed. I can still see issues with
> the menu bar.

The menus with firefox 122.0-1 and FVWM seem to work fine, which
is not the case with the previous firefox version 121.0.1-1.

Perhaps this bug can be closed as fixed in 122.0-1, or we can wait
for confirmation by upstream (I've posted this information in the
upstream bug).

-- 
Vincent Lefèvre  - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)



Bug#1061438: tpm2-tss: can't upgrade the tpm2-tss packages to 4.0.1-6; missing Conflicts?

2024-01-24 Thread Vincent Lefevre
Source: tpm2-tss
Version: 4.0.1-6
Severity: serious

It is not possible to upgrade the tpm2-tss packages to 4.0.1-6 with
"apt upgrade" or with aptitude (command line or its TUI, without a
*manual* dependency resolution):

root@disset:~# apt upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
The following packages have been kept back:
  libtss2-esys-3.0.2-0 libtss2-sys1 libtss2-tcti-cmd0 libtss2-tcti-device0
  libtss2-tcti-mssim0 libtss2-tcti-swtpm0
[...]

This is apparently due to the rename of libtss2-mu0 to
libtss2-mu-4.0.1-0. This latter package has a Breaks+Replaces,
but is that sufficient? i.e. isn't Conflicts needed?

https://wiki.debian.org/RenamingPackages says "Conflicts should only
be used if two packages can never be unpacked at the same time",
which is the case for libtss2-mu0 and libtss2-mu-4.0.1-0.

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

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

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



Bug#1061433: grub-common: duplicate "single" in /etc/grub.d/10_linux

2024-01-24 Thread Vincent Lefevre
Package: grub-common
Version: 2.12-1
Severity: minor

In the generated /boot/grub/grub.cfg file:

  linux   /boot/vmlinuz-6.6.11-amd64 root=... ro single single dis_ucode_ldr 

There is a duplicate "single".

/etc/grub.d/10_linux has

: ${GRUB_CMDLINE_LINUX_RECOVERY:=single}
[...]
if [ -x /lib/recovery-mode/recovery-menu ]; then
GRUB_CMDLINE_LINUX_RECOVERY="${GRUB_CMDLINE_LINUX_RECOVERY} recovery"
else
GRUB_CMDLINE_LINUX_RECOVERY="${GRUB_CMDLINE_LINUX_RECOVERY} single"
fi

So one may get "single" twice.

-- Package-specific info:

*** BEGIN /proc/mounts
/dev/sda5 / ext4 rw,relatime,errors=remount-ro 0 0
*** END /proc/mounts

*** BEGIN /boot/grub/grub.cfg
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#

### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
  set have_grubenv=true
  load_env
fi
if [ "${next_entry}" ] ; then
   set default="${next_entry}"
   set next_entry=
   save_env next_entry
   set boot_once=true
else
   set default="${saved_entry}"
fi

if [ x"${feature_menuentry_id}" = xy ]; then
  menuentry_id_option="--id"
else
  menuentry_id_option=""
fi

export menuentry_id_option

if [ "${prev_saved_entry}" ]; then
  set saved_entry="${prev_saved_entry}"
  save_env saved_entry
  set prev_saved_entry=
  save_env prev_saved_entry
  set boot_once=true
fi

function savedefault {
  if [ -z "${boot_once}" ]; then
saved_entry="${chosen}"
save_env saved_entry
  fi
}
function load_video {
  if [ x$feature_all_video_module = xy ]; then
insmod all_video
  else
insmod efi_gop
insmod efi_uga
insmod ieee1275_fb
insmod vbe
insmod vga
insmod video_bochs
insmod video_cirrus
  fi
}

if [ x$feature_default_font_path = xy ] ; then
   font=unicode
else
insmod part_msdos
insmod ext2
set root='hd0,msdos5'
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos5 
--hint-efi=hd0,msdos5 --hint-baremetal=ahci0,msdos5  
4bcb3bbd-f516-4ddf-be96-6fa3a8cdc8a0
else
  search --no-floppy --fs-uuid --set=root 4bcb3bbd-f516-4ddf-be96-6fa3a8cdc8a0
fi
font="/usr/share/grub/unicode.pf2"
fi

if loadfont $font ; then
  set gfxmode=1024x768 640x480
  load_video
  insmod gfxterm
fi
terminal_output gfxterm
if [ "${recordfail}" = 1 ] ; then
  set timeout=30
else
  if [ x$feature_timeout_style = xy ] ; then
set timeout_style=menu
set timeout=5
  # Fallback normal timeout code in case the timeout_style feature is
  # unavailable.
  else
set timeout=5
  fi
fi
### END /etc/grub.d/00_header ###

### BEGIN /etc/grub.d/05_debian_theme ###
insmod part_msdos
insmod ext2
set root='hd0,msdos5'
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos5 
--hint-efi=hd0,msdos5 --hint-baremetal=ahci0,msdos5  
4bcb3bbd-f516-4ddf-be96-6fa3a8cdc8a0
else
  search --no-floppy --fs-uuid --set=root 4bcb3bbd-f516-4ddf-be96-6fa3a8cdc8a0
fi
insmod png
if background_image /usr/share/desktop-base/emerald-theme/grub/grub-4x3.png; 
then
  set color_normal=white/black
  set color_highlight=black/white
else
  set menu_color_normal=cyan/blue
  set menu_color_highlight=white/blue
fi
### END /etc/grub.d/05_debian_theme ###

### BEGIN /etc/grub.d/10_linux ###
function gfxmode {
set gfxpayload="${1}"
}
set linux_gfx_mode=keep
export linux_gfx_mode
menuentry 'Debian GNU/Linux, with Linux 6.6.11-amd64' --class debian --class 
gnu-linux --class gnu --class os $menuentry_id_option 
'gnulinux-6.6.11-amd64-advanced-4bcb3bbd-f516-4ddf-be96-6fa3a8cdc8a0' {
savedefault
load_video
gfxmode $linux_gfx_mode
insmod gzio
if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
insmod part_msdos
insmod ext2
set root='hd0,msdos5'
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos5 
--hint-efi=hd0,msdos5 --hint-baremetal=ahci0,msdos5  
4bcb3bbd-f516-4ddf-be96-6fa3a8cdc8a0
else
  search --no-floppy --fs-uuid --set=root 
4bcb3bbd-f516-4ddf-be96-6fa3a8cdc8a0
fi
echo'Loading Linux 6.6.11-amd64 ...'
linux   /boot/vmlinuz-6.6.11-amd64 
root=UUID=4bcb3bbd-f516-4ddf-be96-6fa3a8cdc8a0 ro  quiet
echo'Loading initial ramdisk ...'
initrd  /boot/initrd.img-6.6.11-amd64
}
menuentry 'Debian GNU/Linux, with Linux 6.6.11-amd64 (recovery mode)' --class 
debian --class gnu-linux --class gnu --class os $menuentry_id_option 
'gnulinux-6.6.11-amd64-recovery-4bcb3bbd-f516-4ddf-be96-6fa3a8cdc8a0' {
load_video
gfxmode $linux_gfx_mode
insmod gzio
if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
insmod part_msdos
insmod ext2
set root='hd0,msdos5'
if [ 

Bug#1061423: xpdf: performance of a second text search should be improved

2024-01-24 Thread Vincent Lefevre
Package: xpdf
Version: 3.04+git20240118-1
Severity: wishlist

With xpdf, a second search (with Ctrl-F), on a different word, takes
about the same time as the first search.

With zathura, the first search needs the same time as xpdf, but a
second search is much faster (almost immediate). xpdf text search
should be improved to be as fast as zathura.

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

Versions of packages xpdf depends on:
ii  libc6  2.37-14
ii  libgcc-s1  13.2.0-10
ii  libpaper1  1.1.29
ii  libpoppler126  22.12.0-2+local1
ii  libstdc++6 13.2.0-10
ii  libx11-6   2:1.8.7-1
ii  libxm4 2.3.8-3
ii  libxt6 1:1.2.1-1.1

Versions of packages xpdf recommends:
ii  cups-bsd  2.4.7-1+b1
ii  fonts-urw-base35  20200910-7
ii  poppler-data  0.4.12-1
ii  poppler-utils 22.12.0-2+local1
ii  sensible-utils0.0.20

xpdf suggests no packages.

-- no debconf information

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



Bug#852025: xdg-utils: chromium should not be automatically set as XDG default-web-browser default-web-browser

2024-01-22 Thread Vincent Lefevre
On 2019-11-26 11:19:38 +1300, martin f krafft wrote:
> xdg-utils on Debian really ought to default to x-www-browser.

This would be better than an arbitrary default (which I cannot
change). Or sensible-browser (provided by sensible-utils) when
available; it has the advantage to dynamically be configurable
by the end user (who can use 2 different browsers in 2 different
contexts at the same time).

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



Bug#1061294: sensible-utils: sensible-browser(1) man page has incorrect title SENSIBLE-EDITOR(1)

2024-01-22 Thread Vincent Lefevre
Package: sensible-utils
Version: 0.0.20
Severity: minor

When I type "man sensible-browser", I get:

SENSIBLE-EDITOR(1)  General Commands Manual SENSIBLE-EDITOR(1)

[...]

Debian12 Jan 2020   SENSIBLE-EDITOR(1)

However, the other contents are correct. The man page title
should have been "SENSIBLE-BROWSER(1)".

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

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

-- no debconf information

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



Bug#1061292: xdg-utils: cannot set default-web-browser: $BROWSER is set and can't be changed with xdg-settings

2024-01-22 Thread Vincent Lefevre
Package: xdg-utils
Version: 1.1.3-4.1
Severity: important

I would like xdg-open to use sensible-browser instead of the default
firefox-esr.desktop. But I get the following error:

qaa:~> xdg-settings set default-web-browser sensible-browser.desktop
xdg-settings: $BROWSER is set and can't be changed with xdg-settings

$BROWSER is the configuration for sensible-browser, so I don't
understand why I get that.

Hmm... the xdg-settings seems to use $BROWSER internally. I don't know
the intent. In any case, $BROWSER is not honored by xdg-open (which
uses firefox-esr.desktop instead of $BROWSER).

-- Package-specific info:
Desktop environment: XDG_CURRENT_DESKTOP=

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

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

xdg-utils depends on no packages.

Versions of packages xdg-utils recommends:
ii  libfile-mimeinfo-perl  0.34-1
ii  libnet-dbus-perl   1.2.0-2+b1
ii  libx11-protocol-perl   0.56-9
ii  x11-utils  7.7+6
ii  x11-xserver-utils  7.7+10

xdg-utils suggests no packages.

-- no debconf information

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



Bug#1061164: cron: with a black background, /etc/supercat/spcrc-crontab makes default text invisible

2024-01-19 Thread Vincent Lefevre
Package: cron
Version: 3.0pl1-183
Severity: normal

Using spc with the provided /etc/supercat/spcrc-crontab config file
makes default text invisible with a black background.

Example:

  echo '6 5 * * * foo > /dev/null' | spc -t crontab

gives "6 5 * * * foo". The remaining is invisible. Note that using the
-r spc option (to reverse black and white) doesn't change anything.

I suppose that this is due to

Blackblk   (.*)

IMHO, the color of the default text shouldn't be changed (changing it
seems rather unusual).

-- Package-specific info:
--- EDITOR:
not set

--- /usr/bin/editor:
/usr/bin/nano

--- /usr/bin/crontab:
-rwxr-sr-x 1 root crontab 47840 2024-01-18 09:51:30 /usr/bin/crontab

--- /var/spool/cron:
drwxr-xr-x 5 root root 4096 2023-12-25 03:13:01 /var/spool/cron

--- /var/spool/cron/crontabs:
drwx-wx--T 2 root crontab 4096 2024-01-15 15:44:54 /var/spool/cron/crontabs

--- /etc/cron.d:
drwxr-xr-x 2 root root 4096 2024-01-20 00:09:14 /etc/cron.d

--- /etc/cron.daily:
drwxr-xr-x 2 root root 4096 2024-01-20 00:09:14 /etc/cron.daily

--- /etc/cron.hourly:
drwxr-xr-x 2 root root 4096 2024-01-20 00:09:15 /etc/cron.hourly

--- /etc/cron.monthly:
drwxr-xr-x 2 root root 4096 2024-01-20 00:09:15 /etc/cron.monthly

--- /etc/cron.weekly:
drwxr-xr-x 2 root root 4096 2024-01-20 00:09:15 /etc/cron.weekly


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

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

Versions of packages cron depends on:
ii  cron-daemon-common   3.0pl1-183
ii  init-system-helpers  1.66
ii  libc62.37-13
ii  libpam-runtime   1.5.2-9.1
ii  libpam0g 1.5.2-9.1+b1
ii  libselinux1  3.5-1+b2
ii  sensible-utils   0.0.20

Versions of packages cron recommends:
ii  postfix [mail-transport-agent]  3.8.4-1
ii  supercat0.5.7-1

Versions of packages cron suggests:
ii  anacron2.3-39+b1
pn  checksecurity  
ii  logrotate  3.21.0-2

Versions of packages cron is related to:
pn  libnss-ldap   
pn  libnss-ldapd  
pn  libpam-ldap   
pn  libpam-mount  
pn  nis   
pn  nscd  

-- no debconf information

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



Bug#1061148: apt: option -a has several meanings and is unusable

2024-01-19 Thread Vincent Lefevre
On 2024-01-19 16:43:24 +0100, Julian Andres Klode wrote:
> On Fri, Jan 19, 2024 at 03:43:25PM +0100, Vincent Lefevre wrote:
> > Package: apt
> > Version: 2.7.9
> > Severity: normal
> > 
> > In the apt-get(8) man page:
> > 
> >apt-get [-asqdyfmubV] [-o=config_string] [-c=config_file]
> >[-t=target_release] [-a=architecture] {update | upgrade |
> >dselect-upgrade | dist-upgrade |
> >install pkg [{=pkg_version_number | /target_release}]...  |
> >remove pkg...  | purge pkg...  |
> >source pkg [{=pkg_version_number | /target_release}]...  |
> >build-dep pkg [{=pkg_version_number | /target_release}]...  |
> >download pkg [{=pkg_version_number | /target_release}]...  |
> >check | clean | autoclean | autoremove | {-v | --version} |
> >{-h | --help}}
> > 
> > So option -a appears both as a single option -a and as -a=architecture.
> > 
> > In the apt(8) man page, only the second form is listed, but for both
> > commands, it is unusable:
> > 
> > # apt-get -a=i386 install libfontconfig-dev
> > E: Command line option 'a' [from -a=i386] is not understood in combination 
> > with the other options.
> > 
> > # apt -a=i386 install libfontconfig-dev
> > E: Command line option 'a' [from -a=i386] is not understood in combination 
> > with the other options.
> 
> -a in that sense is an argument to build-dep and family (source --build,
> satisfy). It is short for host-architecture, and makes no sense in any
> other command.

Perhaps this should be explicitly documented. And the error message
should be clarified (note: "install" is a command, not an option).

> You seem to be trying to install libfontconfig-dev:i386

OK, but I was looking at an option to install several packages
(package list to be copy-pasted) for a foreign architecture
without much typing.

> We haven't explained that it works outside of source --compile and
> build-dep (i.e. in satisfy) but I fail to see how you get to try
> to pass this to install after reading the manual page.

The -a=... version is not documented in the manual, only -a alone,
but even for that, I don't understand the manual; the grammar seems
incorrect:

   -a, --host-architecture
   This option controls the architecture packages are built for by
   apt-get source --compile and how cross-builddependencies are
   satisfied. By default is it not set which means that the host
   architecture is the same as the build architecture (which is
   defined by APT::Architecture). Configuration Item:
   APT::Get::Host-Architecture.

There are 2 verbs "controls" and "are built". And I don't see how
to parse "for by". In the next sentence: "is it". Should this be
"it is"? The comma is missing before "which". Still, I don't see
what this option does.

-- 
Vincent Lefèvre  - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)



Bug#1061148: apt: option -a has several meanings and is unusable

2024-01-19 Thread Vincent Lefevre
Package: apt
Version: 2.7.9
Severity: normal

In the apt-get(8) man page:

   apt-get [-asqdyfmubV] [-o=config_string] [-c=config_file]
   [-t=target_release] [-a=architecture] {update | upgrade |
   dselect-upgrade | dist-upgrade |
   install pkg [{=pkg_version_number | /target_release}]...  |
   remove pkg...  | purge pkg...  |
   source pkg [{=pkg_version_number | /target_release}]...  |
   build-dep pkg [{=pkg_version_number | /target_release}]...  |
   download pkg [{=pkg_version_number | /target_release}]...  |
   check | clean | autoclean | autoremove | {-v | --version} |
   {-h | --help}}

So option -a appears both as a single option -a and as -a=architecture.

In the apt(8) man page, only the second form is listed, but for both
commands, it is unusable:

# apt-get -a=i386 install libfontconfig-dev
E: Command line option 'a' [from -a=i386] is not understood in combination with 
the other options.

# apt -a=i386 install libfontconfig-dev
E: Command line option 'a' [from -a=i386] is not understood in combination with 
the other options.

-- Package-specific info:

-- (no /etc/apt/preferences present) --


-- (/etc/apt/preferences.d/no-adobe-flash-plugin present, but not submitted) --


-- (/etc/apt/preferences.d/no-pipewire present, but not submitted) --


-- (/etc/apt/sources.list present, but not submitted) --


-- (/etc/apt/sources.list.d/local-i386.list present, but not submitted) --


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

Versions of packages apt depends on:
ii  adduser 3.137
ii  base-passwd 3.6.3
ii  debian-archive-keyring  2023.4
ii  gpgv2.2.40-1.1+b1
ii  libapt-pkg6.0   2.7.9
ii  libc6   2.37-13
ii  libgcc-s1   13.2.0-9
ii  libgnutls30 3.8.3-1
ii  libseccomp2 2.5.5-1
ii  libstdc++6  13.2.0-9
ii  libsystemd0 255.2-4

Versions of packages apt recommends:
ii  ca-certificates  20230311

Versions of packages apt suggests:
ii  apt-doc 2.7.9
ii  aptitude0.8.13-5+b1
ii  dpkg-dev1.22.2
ii  gnupg   2.2.40-1.1
ii  powermgmt-base  1.37

-- no debconf information

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



Bug#1059936: Tracked down `behavior of -n is non-portable`

2024-01-15 Thread Vincent Lefevre
Control: reassign -1 klibc-utils
Control: forcemerge 1055694 -1

Note: Bug 1055694 was initially described as a different bug, but
it was retitled on January 9 (to match the change in coreutils),
so that it became the same bug as 1059936. Hence the merge.

On 2024-01-15 05:09:10 +, Alexander Huynh wrote:
> I believe the offending line is in the `klibc` package, after some tracing: 
> https://salsa.debian.org/kernel-team/klibc/-/blob/2078f63fe594652d42e19060b05aa03966fbd8a5/debian/initramfs-tools/hooks/klibc-utils#L31

Yes, this is mentioned in the merge request at

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055694#43

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



Bug#1060673: nvidia-persistenced: Flushing system-wide workqueues will be prohibited in near future

2024-01-12 Thread Vincent Lefevre
Package: nvidia-persistenced
Version: 525.85.05-1+b1
Severity: important

With the 6.6.9-amd64 kernel (not before), I get:

Jan 12 15:25:54 cventin kernel: WARNING: Flushing system-wide workqueues will 
be prohibited in near future.
Jan 12 15:25:54 cventin kernel: CPU: 8 PID: 794 Comm: nvidia-persiste Tainted: 
P   OE  6.6.9-amd64 #1  Debian 6.6.9-1
Jan 12 15:25:54 cventin kernel: Hardware name: Dell Inc. Precision Tower 
7810/0GWHMW, BIOS A07 04/14/2015
Jan 12 15:25:54 cventin kernel: Call Trace:
Jan 12 15:25:54 cventin kernel:  
Jan 12 15:25:54 cventin kernel:  dump_stack_lvl+0x47/0x60
Jan 12 15:25:54 cventin kernel:  os_flush_work_queue+0x55/0x70 [nvidia]
Jan 12 15:25:54 cventin kernel:  rm_disable_adapter+0x52/0xd0 [nvidia]
Jan 12 15:25:54 cventin kernel:  ? down_trylock+0x11/0x40
Jan 12 15:25:54 cventin kernel:  nv_shutdown_adapter+0x17/0xa0 [nvidia]
Jan 12 15:25:54 cventin kernel:  nv_close_device+0xea/0x170 [nvidia]
Jan 12 15:25:54 cventin kernel:  nvidia_close+0xcf/0x3a0 [nvidia]
Jan 12 15:25:54 cventin kernel:  nvidia_frontend_close+0x2e/0x50 [nvidia]
Jan 12 15:25:54 cventin kernel:  __fput+0xf5/0x290
Jan 12 15:25:54 cventin kernel:  __x64_sys_close+0x3d/0x80
Jan 12 15:25:54 cventin kernel:  do_syscall_64+0x60/0xc0
Jan 12 15:25:54 cventin kernel:  ? syscall_exit_to_user_mode+0x2b/0x40
Jan 12 15:25:54 cventin kernel:  ? do_syscall_64+0x6c/0xc0
Jan 12 15:25:54 cventin kernel:  ? exit_to_user_mode_prepare+0x40/0x1e0
Jan 12 15:25:54 cventin kernel:  ? syscall_exit_to_user_mode+0x2b/0x40
Jan 12 15:25:54 cventin kernel:  ? do_syscall_64+0x6c/0xc0
Jan 12 15:25:54 cventin kernel:  ? syscall_exit_to_user_mode+0x2b/0x40
Jan 12 15:25:54 cventin kernel:  ? do_syscall_64+0x6c/0xc0
Jan 12 15:25:54 cventin kernel:  ? exit_to_user_mode_prepare+0x40/0x1e0
Jan 12 15:25:54 cventin kernel:  entry_SYSCALL_64_after_hwframe+0x6e/0xd8
Jan 12 15:25:54 cventin kernel: RIP: 0033:0x7f631be6f1a0
Jan 12 15:25:54 cventin kernel: Code: 0d 00 00 00 eb b2 e8 5f 01 02 00 66 2e 0f 
1f 84 00 00 00 00 00 0f 1f 44 00 00 80 3d 41 34 0e 00 00 74 17 b8 03 00 00 00 
0f 05 <48> 3d 00 f0 ff ff 77 48 c3 0f 1f 80 00 00 00 00 48 83 ec 18 89 7c
Jan 12 15:25:54 cventin kernel: RSP: 002b:7ffe78073cf8 EFLAGS: 0202 
ORIG_RAX: 0003
Jan 12 15:25:54 cventin kernel: RAX: ffda RBX:  
RCX: 7f631be6f1a0
Jan 12 15:25:54 cventin kernel: RDX:  RSI: 0003 
RDI: 0003
Jan 12 15:25:54 cventin kernel: RBP: 0003 R08: 7ffe78073e90 
R09: 7ffe78073eac
Jan 12 15:25:54 cventin kernel: R10: 8aa9e9ddd50363d7 R11: 0202 
R12: 
Jan 12 15:25:54 cventin kernel: R13: 7f631ba2ef80 R14: 7f631ba2ef60 
R15: c1d00011
Jan 12 15:25:54 cventin kernel:  

https://lore.kernel.org/lkml/42f1067f-3232-0a64-4c19-6165dabf4...@i-love.sakura.ne.jp/T/
(where this warning has been introduced) says "Therefore, start
emitting runtime message so that all out-of-tree users will
understand that they need to update their code."

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

Versions of packages nvidia-persistenced depends on:
ii  adduser   3.137
ii  init-system-helpers   1.66
ii  libc6 2.37-13
ii  libnvidia-legacy-390xx-cfg1 [libnvidia-cfg1-any]  390.157-6
ii  libtirpc3 1.3.4+ds-1

nvidia-persistenced recommends no packages.

nvidia-persistenced suggests no packages.

-- no debconf information

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



Bug#1060664: gpg: Option --keyserver-options=auto-key-retrieve does not work

2024-01-12 Thread Vincent Lefevre
Control: retitle -1 gpg auto-key-retrieve does not work

I've tried --auto-key-retrieve on a different machine, and this
doesn't have any effect either:

cventin:~> gpg --verbose --keyserver pgpkeys.eu --auto-key-retrieve --verify 
/home/vlefevre/.cpan/sources/authors/id/C/CA/CAVAC/CHECKSUMS
gpg: armor header: Hash: SHA1
gpg: armor header: Version: GnuPG v2.0.14 (GNU/Linux)
gpg: original file name=''
gpg: Signature made 2023-12-17T16:29:09 CET
gpg:using RSA key 77576125A905F1BA
gpg: Can't check signature: No public key

Putting the option in .gnupg/gpg.conf doesn't have any effect either.

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



Bug#1060664: gpg: Option --keyserver-options=auto-key-retrieve does not work

2024-01-12 Thread Vincent Lefevre
Package: gpg
Version: 2.2.40-1.1+b1
Severity: normal
Affects: libmodule-signature-perl

The --keyserver-options=auto-key-retrieve option does not work. It is
described as an obsolete alias for the option auto-key-retrieve, but
it is still documented, so that it is still expected to be supported.
Note that it is still used by libmodule-signature-perl.

The test I did:

zira:~> MODULE_SIGNATURE_VERBOSE=1 MODULE_SIGNATURE_KEYSERVER=pgpkeys.eu cpan 
-i XML::RPC
Reading '/home/vinc17/.cpan/Metadata'
  Database was generated on Thu, 11 Jan 2024 22:41:02 GMT
Running install for module 'XML::RPC'
CPAN: Digest::SHA loaded ok (v6.04)
CPAN: Module::Signature loaded ok (v0.88)
Executing 
gpg/--verify/--batch/--no-tty/--keyserver=hkp://pgpkeys.eu:11371/--keyserver-options=auto-key-retrieve//tmp/E4jnBjTWP8
gpg: Signature made 2023-12-17T16:29:09 CET
gpg:using RSA key 77576125A905F1BA
gpg: Can't check signature: No public key

Signature invalid for file 
/home/vinc17/.cpan/sources/authors/id/C/CA/CAVAC/CHECKSUMS. Please investigate.
[...]

zira:~[2]> gpg --keyserver pgpkeys.eu --recv-keys 77576125A905F1BA
gpg: key 328DA867450F89EC: 13 duplicate signatures removed
gpg: key 328DA867450F89EC: "PAUSE Batch Signing Key 2024 
" 1 new user ID
gpg: key 328DA867450F89EC: "PAUSE Batch Signing Key 2024 
" 14 new signatures
gpg: key 328DA867450F89EC: "PAUSE Batch Signing Key 2024 
" 2 new subkeys
gpg: Total number processed: 1
gpg:   new user IDs: 1
gpg:new subkeys: 2
gpg: new signatures: 14

zira:~> MODULE_SIGNATURE_VERBOSE=1 MODULE_SIGNATURE_KEYSERVER=pgpkeys.eu cpan 
-i XML::RPC
Reading '/home/vinc17/.cpan/Metadata'
  Database was generated on Thu, 11 Jan 2024 22:41:02 GMT
Running install for module 'XML::RPC'
CPAN: Digest::SHA loaded ok (v6.04)
CPAN: Module::Signature loaded ok (v0.88)
Executing 
gpg/--verify/--batch/--no-tty/--keyserver=hkp://pgpkeys.eu:11371/--keyserver-options=auto-key-retrieve//tmp/TMJRFmY_zR
gpg: Signature made 2023-12-17T16:29:09 CET
gpg:using RSA key 77576125A905F1BA
gpg: Good signature from "PAUSE Batch Signing Key 2024 " 
[unknown]
[...]

In summary, the public key was missing and wasn't retrieved
automatically, even though --keyserver-options=auto-key-retrieve was
used. Then I retrieved the key explicitly with --recv-keys and using
the same keyserver, which succeeded, and the signature could be
verified.

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

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

Versions of packages gpg depends on:
ii  gpgconf2.2.40-1.1+b1
ii  libassuan0 2.5.6-1
ii  libbz2-1.0 1.0.8-5+b2
ii  libc6  2.37-13
ii  libgcrypt201.10.3-2
ii  libgpg-error0  1.47-3
ii  libreadline8   8.2-3
ii  libsqlite3-0   3.44.2-1
ii  zlib1g 1:1.3.dfsg-3

Versions of packages gpg recommends:
ii  gnupg  2.2.40-1.1

gpg suggests no packages.

-- no debconf information

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



Bug#1060648: libmodule-signature-perl: obsolete pool.sks-keyservers.net yields a 20-second timeout in DNS resolution and a possible failure

2024-01-11 Thread Vincent Lefevre
Package: libmodule-signature-perl
Version: 0.88-2
Severity: normal
Tags: upstream
Forwarded: https://rt.cpan.org/Public/Bug/Display.html?id=151098

When I used "cpan -i ...", I could see several timeouts in the
strace output:

725098 00:37:58.837653 connect(3, {sa_family=AF_INET, sin_port=htons(53), 
sin_addr=inet_addr("192.168.1.1")}, 16) = 0
725098 00:37:58.837679 poll([{fd=3, events=POLLOUT}], 1, 0) = 1 ([{fd=3, 
revents=POLLOUT}])
725098 00:37:58.837692 sendto(3, 
"\30\330\1\0\0\1\0\0\0\0\0\0\4pool\16sks-keyservers\3net\0\0\1\0\1", 41, 
MSG_NOSIGNAL, NULL, 0) = 41
725098 00:37:58.837733 poll([{fd=3, events=POLLIN}], 1, 5000) = 0 (Timeout)
725098 00:38:03.843214 socket(AF_INET6, SOCK_DGRAM|SOCK_CLOEXEC|SOCK_NONBLOCK, 
IPPROTO_IP) = 4
725098 00:38:03.843459 setsockopt(4, SOL_IPV6, IPV6_RECVERR, [1], 4) = 0
725098 00:38:03.843704 connect(4, {sa_family=AF_INET6, sin6_port=htons(53), 
sin6_flowinfo=htonl(0), inet_pton(AF_INET6, "2a02:8428:1b1d:4d01::1", 
_addr), sin6_scope_id=0}, 28) = 0
725098 00:38:03.843826 poll([{fd=4, events=POLLOUT}], 1, 0) = 1 ([{fd=4, 
revents=POLLOUT}])
725098 00:38:03.843846 sendto(4, 
"\30\330\1\0\0\1\0\0\0\0\0\0\4pool\16sks-keyservers\3net\0\0\1\0\1", 41, 
MSG_NOSIGNAL, NULL, 0) = 41
725098 00:38:03.844005 poll([{fd=4, events=POLLIN}], 1, 5000) = 0 (Timeout)
725098 00:38:08.849500 poll([{fd=3, events=POLLOUT}], 1, 0) = 1 ([{fd=3, 
revents=POLLOUT}])
725098 00:38:08.849728 sendto(3, 
"\30\330\1\0\0\1\0\0\0\0\0\0\4pool\16sks-keyservers\3net\0\0\1\0\1", 41, 
MSG_NOSIGNAL, NULL, 0) = 41
725098 00:38:08.849986 poll([{fd=3, events=POLLIN}], 1, 5000) = 0 (Timeout)
725098 00:38:13.855521 poll([{fd=4, events=POLLOUT}], 1, 0) = 1 ([{fd=4, 
revents=POLLOUT}])
725098 00:38:13.855577 sendto(4, 
"\30\330\1\0\0\1\0\0\0\0\0\0\4pool\16sks-keyservers\3net\0\0\1\0\1", 41, 
MSG_NOSIGNAL, NULL, 0) = 41
725098 00:38:13.855728 poll([{fd=4, events=POLLIN}], 1, 5000) = 0 (Timeout)
725098 00:38:18.861210 close(3) = 0
725098 00:38:18.861470 close(4) = 0

i.e. 20 seconds in total.

This is due to the DNS resolution of pool.sks-keyservers.net, which
no longer exists:

  
https://unix.stackexchange.com/questions/656205/sks-keyservers-gone-what-to-use-instead

The DNS records have no longer been provided since 2021-06-21!

On one of my machines, the installation with "cpan -i" even fails
because subkeys are missing (I don't know why there is a difference
between machines, but perhaps a correct keyserver selected by this
module would solve the issue).

I've just reported the upstream bug.

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

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

Versions of packages libmodule-signature-perl depends on:
ii  perl  5.38.2-2

Versions of packages libmodule-signature-perl recommends:
ii  gnupg  2.2.40-1.1

libmodule-signature-perl suggests no packages.

-- no debconf information

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



Bug#1060314: zathura: selecting multiple lines of text increases the window width when the mouse button is released

2024-01-09 Thread Vincent Lefevre
On 2024-01-09 15:39:20 +0100, Sebastian Ramacher wrote:
> Control: tags -1 fixed-upstream
> 
> On 2024-01-09 14:13:20 +0100, Vincent Lefevre wrote:
> > Package: zathura
> > Version: 0.5.4-1
> > Severity: important
> > 
> > When I select multiple lines of text, the window width is sometimes
> > increased just after the mouse button is released. It seems that the
> > total width of the text (as if it were on a single line) determines
> > how much the window width will be at least.
> 
> Already fixed upstream: 
> https://git.pwmt.org/pwmt/girara/-/commit/87775a28e3a4195b19f0976b2c2d38b96c4b7fa0

OK. I didn't find it because it is in the girara project instead of
zathura. I was a bit confused.

So this would mean that the bug is actually in libgirara-gtk3-3?

-- 
Vincent Lefèvre  - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)



Bug#1060314: zathura: selecting multiple lines of text increases the window width when the mouse button is released

2024-01-09 Thread Vincent Lefevre
Control: forwarded -1 https://git.pwmt.org/pwmt/zathura/-/issues/396

I've just reported the bug upstream.

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



Bug#1060314: zathura: selecting multiple lines of text increases the window width when the mouse button is released

2024-01-09 Thread Vincent Lefevre
Control: retitle -1 zathura: selecting text displays the selected text in the 
status bar, which can insanely increase the window width
Control: tags -1 security

Better description. The issue is due to the fact that the selected
text is displayed in the status bar, and the window width is increased
to make this text completely visible in the status bar.

I suppose that PDF files could be designed to produce a denial of
service when text is selected, e.g. with tiny invisible text (the
font size in the PDF document does not matter since the characters
in the status bar have a fixed width).

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



Bug#1060314: zathura: selecting multiple lines of text increases the window width when the mouse button is released

2024-01-09 Thread Vincent Lefevre
Package: zathura
Version: 0.5.4-1
Severity: important

When I select multiple lines of text, the window width is sometimes
increased just after the mouse button is released. It seems that the
total width of the text (as if it were on a single line) determines
how much the window width will be at least.

To reproduce:

1. Open a PDF file with "zathura some_file.pdf".

2. Select multiple lines of text.

For instance, I got a window increased to a width of 30521 pixels,
which is much larger than the screen width (2560). This makes the
X server quite unresponsive.

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

Versions of packages zathura depends on:
ii  libc62.37-13
ii  libcairo21.18.0-1+b1
ii  libgirara-gtk3-3 0.4.1-1
ii  libglib2.0-0 2.78.3-1
ii  libgtk-3-0   3.24.39-1
ii  libjson-glib-1.0-0   1.8.0-2
ii  libmagic11:5.45-2+b1
ii  libpango-1.0-0   1.51.0+ds-3
ii  libseccomp2  2.5.5-1
ii  libsqlite3-0 3.44.2-1
ii  libsynctex2  2023.20230311.66589-8
ii  zathura-pdf-poppler  0.3.2-1

zathura recommends no packages.

Versions of packages zathura suggests:
ii  elinks [www-browser]   0.16.1.1-4.1
ii  firefox [www-browser]  121.0-2
hi  firefox-esr [www-browser]  92.0-local
ii  links [www-browser]2.29-1+b1
ii  links2 [www-browser]   2.29-1+b1
ii  lynx [www-browser] 2.9.0dev.12-1
ii  w3m [www-browser]  0.5.3+git20230121-2+b2
pn  zathura-cb 
pn  zathura-djvu   
ii  zathura-ps 0.2.7-2+b2

-- no debconf information

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



Bug#731164: ghostscript: ps2pdf makes highlighted/annotated text unreadable by poppler-based PDF viewers

2024-01-06 Thread Vincent Lefevre
On 2024-01-06 18:17:20 +0100, Vincent Lefevre wrote:
> I confirm. However, Firefox 121 (from the Debian package) still
> has the same issue with "out.pdf". That said, if I try again
> "ps2pdf temp.pdf out.pdf" with ghostscript 10.02.1~dfsg-1 (on
> my Debian/unstable machine), Firefox displays the new out.pdf
> document just like the poppler-based PDF viewers, with readable
> text (and with no warnings). So, if there was a bug in ghostscript,
> it is now "fixed".

I may have done something wrong in my tests, because actually,
only xpdf is now fine with the old out.pdf file. But all xpdf,
zathura and atril have no issues with the file generated by the
current ps2pdf. This confirms a good change in ghostscript.

However, the new ps2pdf triggers a bug / unimplemented feature
in atril (but this isn't a bug in ghostscript).

-- 
Vincent Lefèvre  - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)



Bug#731164: ghostscript: ps2pdf makes highlighted/annotated text unreadable by poppler-based PDF viewers

2024-01-06 Thread Vincent Lefevre
On 2024-01-05 22:58:58 -0600, Steven Robbins wrote:
> On Mon, 2 Dec 2013 17:15:19 +0100 Vincent Lefevre  wrote:
> > Package: ghostscript
> > Version: 9.05~dfsg-8
> > Severity: important
> > 
> > When I use ps2pdf on a file with highlighted/annotated text (as
> > produced by Apple's Preview on Mac OS X 10.6.8), this text is
> > displayed below the background with poppler-based PDF viewers
> > (xpdf, evince, okular).
> > 
> > I've attached the original file temp.pdf (no problems with it),
> > the out.pdf file produced by "ps2pdf temp.pdf out.pdf", which
> > cannot be read correctly by poppler-based PDF viewers, and the
> > out.png file, which is a screenshot of "xpdf out.pdf" (so that
> > you can see the problem).
> 
> I don't know where the problem lay, but just tested now with xpdf 
> 3.04+git20231213-1.  Both temp.pdf and out.pdf displayed identically.

I confirm. However, Firefox 121 (from the Debian package) still
has the same issue with "out.pdf". That said, if I try again
"ps2pdf temp.pdf out.pdf" with ghostscript 10.02.1~dfsg-1 (on
my Debian/unstable machine), Firefox displays the new out.pdf
document just like the poppler-based PDF viewers, with readable
text (and with no warnings). So, if there was a bug in ghostscript,
it is now "fixed".

FYI, "qpdf --check temp.pdf" signals an error in the PDF file:

WARNING: temp.pdf (object 11 0): object has offset 0

and "ps2pdf temp.pdf out.pdf" now fixes it silently.

-- 
Vincent Lefèvre  - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)



Bug#1060108: xbase-clients: should not depend (not even recommend) xinit

2024-01-05 Thread Vincent Lefevre
Package: xbase-clients
Version: 1:7.7+23
Severity: normal

The xbase-clients package is there to provide only X clients, not
an X server.

This package currently depends on xinit, which has the effect to
install an X server. The goal of xinit is to start an X server;
this utility is not an X client. So xbase-clients should not depend
(not even recommend) xinit.

Note: a typical use of X clients without a local X server is via ssh.

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

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

Versions of packages xbase-clients depends on:
ii  x11-apps   7.7+11
ii  x11-session-utils  7.7+6
ii  x11-utils  7.7+6
ii  x11-xkb-utils  7.7+8
ii  x11-xserver-utils  7.7+10
ii  xauth  1:1.1.2-1
ii  xinit  1.4.2-1

xbase-clients recommends no packages.

Versions of packages xbase-clients suggests:
pn  x11-xfs-utils  

-- no debconf information

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



Bug#470501: ghostscript bug

2024-01-05 Thread Vincent Lefevre
On 2024-01-04 22:14:55 -0600, Steven Robbins wrote:
> Supplied file renders fine using ghostscript 10.02.1.

I confirm, even on Debian 11 (oldstable).

As said, it could have been

  https://bugs.ghostscript.com/show_bug.cgi?id=689340

(fixed in April 2011).

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



Bug#910274: ghostscript: ps2pdf removes links from PDF files

2024-01-05 Thread Vincent Lefevre
Control: tags -1 wontfix

(see below)

On 2024-01-04 20:42:57 -0600, Steven Robbins wrote:
> On Fri, 5 Oct 2018 13:58:44 +0200 Vincent Lefevre  wrote:
> 
> > Upstream has closed my bug report as a duplicate of bug 699830 again.
> > However, there has been another bug report from another user (who
> > also uses Ghostscript for its compress feature):
> > 
> >   https://bugs.ghostscript.com/show_bug.cgi?id=699896
> > 
> > also closed as a duplicate, 
> 
> Both upstream bugs are closed, so I'm closing this Debian bug as well.

A summary of the above upstream bug: depending on the provided options,
ps2pdf (ps2pdfwr) will preserve either the PDF links or the annotations.
It will no longer preserve both (so ps2pdfwr may lose information,
contrary to the previous versions).

Concerning the \usepackage[pdfa]{hyperref} I had suggested, this is
eventually a bad workaround as the boxes around the links will be
printed, making the printed document less readable.

-- 
Vincent Lefèvre  - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)



Bug#430922: gs-common: ps2pdf does not copy metadata from input PDF

2024-01-05 Thread Vincent Lefevre
On 2024-01-05 00:21:01 -0600, Steven Robbins wrote:
> Tested with ghostscript 10.02.1 and found the metadata was preserved:
[...]

Indeed, and FYI, I could check that this was also the case
in Debian 11 (oldstable).

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



Bug#1059954: apt: "apt changelog" may fail because it tries to fetch an old version

2024-01-03 Thread Vincent Lefevre
Package: apt
Version: 2.7.7
Severity: normal

I get the following error (after "apt update"):

cventin:~> apt changelog dkms
Err:1 https://metadata.ftp-master.debian.org dkms 3.0.12-3 Changelog
  Changelog unavailable for dkms=3.0.12-3 (404  Not Found [IP: 146.75.118.132 
443])
E: Failed to fetch 
https://metadata.ftp-master.debian.org/changelogs/main/d/dkms/dkms_3.0.12-3_changelog
  Changelog unavailable for dkms=3.0.12-3 (404  Not Found [IP: 146.75.118.132 
443])

"apt changelog" should take the latest version to avoid a failure,
e.g.

https://metadata.ftp-master.debian.org/changelogs/main/d/dkms/dkms_3.0.12-4_changelog

I already got such an error for another package 2 days ago
(bug 1059822), so this seems to be rather common.

-- Package-specific info:

-- (no /etc/apt/preferences present) --


-- (/etc/apt/preferences.d/no-adobe-flash-plugin present, but not submitted) --


-- (/etc/apt/preferences.d/no-pipewire present, but not submitted) --


-- (/etc/apt/sources.list present, but not submitted) --


-- (/etc/apt/sources.list.d/local-i386.list present, but not submitted) --


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

Versions of packages apt depends on:
ii  adduser 3.137
ii  base-passwd 3.6.3
ii  debian-archive-keyring  2023.4
ii  gpgv2.2.40-1.1
ii  libapt-pkg6.0   2.7.7
ii  libc6   2.37-13
ii  libgcc-s1   13.2.0-9
ii  libgnutls30 3.8.2-1
ii  libseccomp2 2.5.4-2+b1
ii  libstdc++6  13.2.0-9
ii  libsystemd0 254.5-1

Versions of packages apt recommends:
ii  ca-certificates  20230311

Versions of packages apt suggests:
ii  apt-doc 2.7.7
ii  aptitude0.8.13-5+b1
ii  dpkg-dev1.22.2
ii  gnupg   2.2.40-1.1
ii  powermgmt-base  1.37

-- no debconf information

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



Bug#1059936: initramfs-tools: update-initramfs yields "cp: warning: behavior of -n is non-portable and may change in future"

2024-01-03 Thread Vincent Lefevre
Package: initramfs-tools
Version: 0.142
Severity: normal

I get the following warnings with coreutils 9.4-3:

Processing triggers for initramfs-tools (0.142) ...
update-initramfs: Generating /boot/initrd.img-6.5.0-5-amd64
[...]
cp: warning: behavior of -n is non-portable and may change in future; use 
--update=none instead
cp: warning: behavior of -n is non-portable and may change in future; use 
--update=none instead
cp: warning: behavior of -n is non-portable and may change in future; use 
--update=none instead
[...]

-- Package-specific info:
-- initramfs sizes
-rw-r--r-- 1 root root 62M 2023-12-19 03:08:02 /boot/initrd.img-6.1.0-16-amd64
-rw-r--r-- 1 root root 66M 2024-01-03 22:25:04 /boot/initrd.img-6.5.0-5-amd64
-- /proc/cmdline
BOOT_IMAGE=/vmlinuz-6.5.0-5-amd64 root=/dev/mapper/qaa--vg-root ro quiet

-- resume
RESUME=/dev/mapper/qaa--vg-swap_1
-- /proc/filesystems
ext3
ext2
ext4
fuseblk
vfat

-- lsmod
Module  Size  Used by
tls   151552  0
nfnetlink  20480  1
rfcomm102400  4
ctr12288  1
ccm20480  3
snd_seq_dummy  12288  0
snd_hrtimer12288  1
snd_seq   114688  7 snd_seq_dummy
snd_seq_device 16384  1 snd_seq
cmac   12288  3
algif_hash 12288  1
algif_skcipher 12288  1
af_alg 36864  6 algif_hash,algif_skcipher
snd_hda_codec_hdmi 90112  1
qrtr   57344  4
bnep   36864  2
binfmt_misc28672  1
dell_rbtn  20480  0
snd_sof_pci_intel_tgl12288  0
snd_sof_intel_hda_common   204800  1 snd_sof_pci_intel_tgl
soundwire_intel61440  1 snd_sof_intel_hda_common
soundwire_generic_allocation12288  1 soundwire_intel
snd_sof_intel_hda_mlink40960  2 soundwire_intel,snd_sof_intel_hda_common
soundwire_cadence  45056  1 soundwire_intel
snd_sof_intel_hda  24576  1 snd_sof_intel_hda_common
intel_uncore_frequency12288  0
snd_sof_pci24576  2 snd_sof_intel_hda_common,snd_sof_pci_intel_tgl
intel_uncore_frequency_common16384  1 intel_uncore_frequency
snd_sof_xtensa_dsp 16384  1 snd_sof_intel_hda_common
x86_pkg_temp_thermal16384  0
btusb  81920  0
snd_sof   356352  3 
snd_sof_pci,snd_sof_intel_hda_common,snd_sof_intel_hda
intel_powerclamp   16384  0
btrtl  28672  1 btusb
snd_sof_utils  16384  1 snd_sof
coretemp   16384  0
snd_soc_hdac_hda   24576  1 snd_sof_intel_hda_common
btbcm  24576  1 btusb
snd_hda_ext_core   36864  4 
snd_sof_intel_hda_common,snd_soc_hdac_hda,snd_sof_intel_hda_mlink,snd_sof_intel_hda
iwlmvm589824  0
snd_ctl_led24576  0
btintel57344  1 btusb
snd_soc_acpi_intel_match90112  2 
snd_sof_intel_hda_common,snd_sof_pci_intel_tgl
btmtk  12288  1 btusb
kvm_intel 413696  0
snd_hda_codec_realtek   192512  1
snd_soc_acpi   12288  2 
snd_soc_acpi_intel_match,snd_sof_intel_hda_common
snd_hda_codec_generic   114688  1 snd_hda_codec_realtek
bluetooth1134592  34 btrtl,btmtk,btintel,btbcm,bnep,btusb,rfcomm
snd_soc_core  421888  4 
soundwire_intel,snd_sof,snd_sof_intel_hda_common,snd_soc_hdac_hda
mac80211 1392640  1 iwlmvm
snd_compress   28672  1 snd_soc_core
kvm  1359872  1 kvm_intel
soundwire_bus 114688  3 
soundwire_intel,soundwire_generic_allocation,soundwire_cadence
libarc412288  1 mac80211
snd_hda_intel  61440  1
snd_intel_dspcfg   32768  3 snd_hda_intel,snd_sof,snd_sof_intel_hda_common
snd_intel_sdw_acpi 16384  2 snd_sof_intel_hda_common,snd_intel_dspcfg
sha3_generic   16384  1
dell_laptop32768  0
snd_hda_codec 225280  6 
snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec_realtek,snd_soc_hdac_hda,snd_sof_intel_hda
jitterentropy_rng  20480  1
uvcvideo  147456  0
irqbypass  12288  1 kvm
ledtrig_audio  12288  3 snd_ctl_led,snd_hda_codec_generic,dell_laptop
iwlwifi   544768  1 iwlmvm
joydev 24576  0
hid_sensor_als 16384  1
videobuf2_vmalloc  20480  1 uvcvideo
rapl   20480  0
snd_hda_core  147456  9 
snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_ext_core,snd_hda_codec,snd_hda_codec_realtek,snd_sof_intel_hda_common,snd_soc_hdac_hda,snd_sof_intel_hda
uvc12288  1 uvcvideo
drbg   49152  1
dell_wmi   16384  0
hid_sensor_trigger 20480  2 hid_sensor_als
mei_hdcp   28672  0
mei_wdt12288  0
mei_pxp16384  0
nls_ascii  12288  1
intel_cstate   20480  0
snd_hwdep  20480  1 snd_hda_codec
videobuf2_memops   16384  1 videobuf2_vmalloc
intel_rapl_msr   

Bug#1059822: ftp.debian.org: Changelog unavailable for linux=6.6.8-1

2024-01-01 Thread Vincent Lefevre
Package: ftp.debian.org
Severity: normal

Changelog for linux=6.6.8-1 is unavailable. After an "apt update":

qaa:~> apt changelog linux-libc-dev
Err:1 https://metadata.ftp-master.debian.org linux 6.6.8-1 Changelog
  Changelog unavailable for linux=6.6.8-1 (404  Not Found [IP: 
2a04:4e42:6a::644 443])
E: Failed to fetch 
https://metadata.ftp-master.debian.org/changelogs/main/l/linux/linux_6.6.8-1_changelog
  Changelog unavailable for linux=6.6.8-1 (404  Not Found [IP: 
2a04:4e42:6a::644 443])

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



Bug#1059771: gpg: --batch has no effect

2023-12-31 Thread Vincent Lefevre
On 2023-12-31 18:55:10 +0100, Vincent Lefevre wrote:
> When I run "gpg --batch -d file.gpg < /dev/null", I'm still asked
> for a passphrase, while the gpg(1) man page says for this option:
> 
>   Use batch mode. Never ask, do not allow interactive commands.

I've eventually found that "--pinentry-mode error" (or
"--pinentry-mode cancel") allows me to avoid this issue.

I suppose that --batch should set the pinentry mode to "error"
so that it behaves as documented.

-- 
Vincent Lefèvre  - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)



Bug#1059771: gpg: --batch has no effect

2023-12-31 Thread Vincent Lefevre
Package: gpg
Version: 2.2.40-1.1
Severity: normal

When I run "gpg --batch -d file.gpg < /dev/null", I'm still asked
for a passphrase, while the gpg(1) man page says for this option:

  Use batch mode. Never ask, do not allow interactive commands.

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

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

Versions of packages gpg depends on:
ii  gpgconf2.2.40-1.1
ii  libassuan0 2.5.6-1
ii  libbz2-1.0 1.0.8-5+b1
ii  libc6  2.37-13
ii  libgcrypt201.10.3-2
ii  libgpg-error0  1.47-3
ii  libreadline8   8.2-3
ii  libsqlite3-0   3.44.2-1
ii  zlib1g 1:1.3.dfsg-3

Versions of packages gpg recommends:
ii  gnupg  2.2.40-1.1

gpg suggests no packages.

-- no debconf information

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



Bug#1059324: subversion: "svn revert -R" signals reverted files with no changes

2023-12-23 Thread Vincent Lefevre
Control: retitle -1 subversion: "svn revert -R" signals reverted files with no 
changes if seen as read-only, e.g. caused by a different owner

Let's have a bug title with more details...

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



Bug#1059324: subversion: "svn revert -R" signals reverted files with no changes

2023-12-23 Thread Vincent Lefevre
Control: tags -1 upstream
Control: forwarded -1 https://issues.apache.org/jira/browse/SVN-4622
Control: severity -1 normal

But see also the following thread I've started:
  https://lists.apache.org/thread/p1ky889bxwy8okqly7h1lgckxfpldnxs

There are actually 2 related issues:

1. "svn revert" wants to set the write permission (even if there
   are no changes), and if the file was regarded as read-only, a
   confusing "Reverted" message is output.

2. The consequence of 1 is possibly repeated "Reverted" messages
   if the file belongs to a different user.

In my case, the cause was that the concerned files were belonging to
root (this was a mistake). So this was issue 2 (and partially 1).

The upstream bug currently corresponds to issue 2 only.

But I think that issue 1 should also be regarded as a bug, unless
there is a good reason for "svn revert" to set the write permission
(to be discussed upstream). In case the behavior will not change,
the output message would need a clarification.

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



Bug#1059324: subversion: "svn revert -R" signals reverted files with no changes

2023-12-22 Thread Vincent Lefevre
Package: subversion
Version: 1.14.2-5+b1
Severity: important

I get the following:

qaa% svn st
M   config.dat
M   dpkg-l
M   grub.cfg
M   mutt-v
M   postconf
M   selections
M   version.out
qaa% svn pl -v etc/apache2/mods-available/dnssd.conf
Properties on 'etc/apache2/mods-available/dnssd.conf':
  source
qaa:/etc/apache2/mods-available/dnssd.conf
  svn:mime-type
text/plain
qaa% svn diff etc/apache2/mods-available/dnssd.conf
qaa% svn revert -R .
Reverted 'selections'
Reverted 'version.out'
Reverted 'postconf'
Reverted 'etc/apache2/conf-available/javascript-common.conf'
Reverted 'etc/apache2/mods-available/dnssd.load'
Reverted 'etc/apache2/mods-available/dnssd.conf'
Reverted 'mutt-v'
Reverted 'config.dat'
Reverted 'grub.cfg'
Reverted 'dpkg-l'
qaa% svn pl -v etc/apache2/mods-available/dnssd.conf
Properties on 'etc/apache2/mods-available/dnssd.conf':
  source
qaa:/etc/apache2/mods-available/dnssd.conf
  svn:mime-type
text/plain
qaa% 

I don't see why etc/apache2/mods-available/dnssd.conf is signaled
as reverted. Is there some data corruption somewhere?

This seems reproducible.

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

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

Versions of packages subversion depends on:
ii  libapr1  1.7.2-3
ii  libaprutil1  1.6.3-1
ii  libc62.37-13
ii  libsvn1  1.14.2-5+b1

subversion recommends no packages.

Versions of packages subversion suggests:
pn  db5.3-util  
pn  libapache2-mod-svn  
ii  patch   2.7.6-7
ii  subversion-tools1.14.2-5+b1

-- no debconf information

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



Bug#1059314: imagemagick-6.q16: please update "Suggests: imagemagick-doc" to imagemagick-6-doc

2023-12-22 Thread Vincent Lefevre
Package: imagemagick-6.q16
Version: 8:6.9.12.98+dfsg1-4
Severity: serious

The imagemagick-doc package is not longer built and has been replaced
by imagemagick-6-doc. So the "Suggests" should be updated.

Note that the current Suggests can prevent installations/upgrades if
suggested packages are installed by default, e.g. with --install-suggests
or APT::Install-Suggests set to true.

-- Package-specific info:
ImageMagick program version
---
animate:  ImageMagick 6.9.12-98 Q16 x86_64 18038 https://legacy.imagemagick.org
compare:  ImageMagick 6.9.12-98 Q16 x86_64 18038 https://legacy.imagemagick.org
convert:  ImageMagick 6.9.12-98 Q16 x86_64 18038 https://legacy.imagemagick.org
composite:  ImageMagick 6.9.12-98 Q16 x86_64 18038 
https://legacy.imagemagick.org
conjure:  ImageMagick 6.9.12-98 Q16 x86_64 18038 https://legacy.imagemagick.org
display:  ImageMagick 6.9.12-98 Q16 x86_64 18038 https://legacy.imagemagick.org
identify:  ImageMagick 6.9.12-98 Q16 x86_64 18038 https://legacy.imagemagick.org
import:  ImageMagick 6.9.12-98 Q16 x86_64 18038 https://legacy.imagemagick.org
mogrify:  ImageMagick 6.9.12-98 Q16 x86_64 18038 https://legacy.imagemagick.org
montage:  ImageMagick 6.9.12-98 Q16 x86_64 18038 https://legacy.imagemagick.org
stream:  ImageMagick 6.9.12-98 Q16 x86_64 18038 https://legacy.imagemagick.org

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

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

Versions of packages imagemagick-6.q16 depends on:
ii  hicolor-icon-theme 0.17-2
ii  libc6  2.37-13
ii  libmagickcore-6.q16-7  8:6.9.12.98+dfsg1-4
ii  libmagickwand-6.q16-7  8:6.9.12.98+dfsg1-4

Versions of packages imagemagick-6.q16 recommends:
ii  ghostscript  10.02.1~dfsg-1
ii  libmagickcore-6.q16-7-extra  8:6.9.12.98+dfsg1-4
ii  netpbm   2:11.04.05-2

Versions of packages imagemagick-6.q16 suggests:
pn  autotrace
ii  cups-bsd [lpr]   2.4.7-1
ii  curl 8.5.0-1
pn  enscript 
pn  ffmpeg   
ii  fig2dev [transfig]   1:3.2.9-3
ii  gimp 2.10.36-2
ii  gnuplot-qt [gnuplot] 5.4.4+dfsg1-2+b2
pn  grads
ii  graphviz 2.42.2-7+b3
ii  groff-base   1.23.0-3
pn  hp2xx
pn  html2ps  
pn  imagemagick-doc  
pn  libraw-bin   
ii  libwmf-bin   0.2.13-1.1
pn  mplayer  
pn  povray   
pn  radiance 
ii  sane-utils   1.2.1-7
ii  texlive-binaries [texlive-base-bin]  2023.20230311.66589-8
ii  xdg-utils1.1.3-4.1

-- no debconf information

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



Bug#1059197: light-locker: disconnects the bluetooth devices when locking

2023-12-20 Thread Vincent Lefevre
Package: light-locker
Version: 1.8.0-3
Severity: important

light-locker disconnects the bluetooth devices when locking.

This is just a screen locker. Locking should not affect bluetooth.

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

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

Versions of packages light-locker depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.40.0-4
ii  libc62.37-13
ii  libcairo21.18.0-1
ii  libdbus-1-3  1.14.10-3
ii  libdbus-glib-1-2 0.112-3
ii  libglib2.0-0 2.78.3-1
ii  libgtk-3-0   3.24.38-6
ii  libpango-1.0-0   1.51.0+ds-3
ii  libpangocairo-1.0-0  1.51.0+ds-3
ii  libsystemd0  254.5-1
ii  libx11-6 2:1.8.7-1
ii  libxext6 2:1.3.4-1+b1
ii  libxss1  1:1.2.3-1
ii  lightdm  1.32.0-4+b1

light-locker recommends no packages.

light-locker suggests no packages.

-- no debconf information

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



Bug#1059193: imagemagick-6-doc: missing Breaks+Replaces against the dropped imagemagick-doc package, in order to force its removal

2023-12-20 Thread Vincent Lefevre
Package: imagemagick-6-doc
Version: 8:6.9.12.98+dfsg1-4
Severity: serious
Justification: Policy 7.6.2

On my new laptop, I can't upgrade the imagemagick packages
automatically from 8:6.9.11.60+dfsg-1.6 to 8:6.9.12.98+dfsg1-4
with aptitude (I need to enter the dependency resolution so
that imagemagick-doc, which is no longer built, gets removed).

The 8:6.9.12.98+dfsg1-1 changelog says:

  * Drop package imagemagick-doc and imagemagick-common

and the imagemagick-doc currently installed (from bookworm) is
just a dummy package, so that there is no reason to keep it. If
I understand correctly, imagemagick-6-doc intends to replace it,
so I'm reporting the bug against imagemagick-6-doc.

So this is the case "7.6.2. Replacing whole packages, forcing their
removal" of the Debian policy, and also

  https://wiki.debian.org/RenamingPackages

which says to use "Breaks:" + "Replaces:".

-- Package-specific info:
ImageMagick program version
---
animate:  ImageMagick 6.9.12-98 Q16 x86_64 18038 https://legacy.imagemagick.org
compare:  ImageMagick 6.9.12-98 Q16 x86_64 18038 https://legacy.imagemagick.org
convert:  ImageMagick 6.9.12-98 Q16 x86_64 18038 https://legacy.imagemagick.org
composite:  ImageMagick 6.9.12-98 Q16 x86_64 18038 
https://legacy.imagemagick.org
conjure:  ImageMagick 6.9.12-98 Q16 x86_64 18038 https://legacy.imagemagick.org
display:  ImageMagick 6.9.12-98 Q16 x86_64 18038 https://legacy.imagemagick.org
identify:  ImageMagick 6.9.12-98 Q16 x86_64 18038 https://legacy.imagemagick.org
import:  ImageMagick 6.9.12-98 Q16 x86_64 18038 https://legacy.imagemagick.org
mogrify:  ImageMagick 6.9.12-98 Q16 x86_64 18038 https://legacy.imagemagick.org
montage:  ImageMagick 6.9.12-98 Q16 x86_64 18038 https://legacy.imagemagick.org
stream:  ImageMagick 6.9.12-98 Q16 x86_64 18038 https://legacy.imagemagick.org

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

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

Versions of packages imagemagick-6-doc depends on:
ii  dpkg  1.22.2
ii  imagemagick-6-common  8:6.9.11.60+dfsg-1.6

Versions of packages imagemagick-6-doc recommends:
ii  elinks [www-browser]   0.16.1.1-4.1
ii  firefox [www-browser]  121.0-1
ii  firefox-esr [www-browser]  115.6.0esr-1
ii  libjs-bootstrap3.4.1+dfsg-3
ii  libjs-jquery   3.6.1+dfsg+~3.5.14-1
ii  libjs-jquery-fancybox  12-4
ii  libjs-jquery-mousewheel1:3.1.13-5
ii  links [www-browser]2.28-1+b2
ii  links2 [www-browser]   2.28-1+b2
ii  lynx [www-browser] 2.9.0dev.12-1
ii  w3m [www-browser]  0.5.3+git20230121-2

Versions of packages imagemagick-6-doc suggests:
ii  imagemagick  8:6.9.12.98+dfsg1-4
ii  imagemagick-6.q16 [imagemagick]  8:6.9.12.98+dfsg1-4

-- no debconf information

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



  1   2   3   4   5   6   7   8   9   10   >