Bug#1082656: screen: New upstream version 5.0.0 available

2024-09-24 Thread Axel Beckert
Control: tag -1 + confirmed

Hi Mika,

Michael Prokop wrote:
> GNU Screen v.5.0.0 was released on 2024-08-29:
> 
>   https://lists.gnu.org/archive/html/screen-users/2024-08/msg0.html
> 
> Would be nice to have it available in Debian/trixie. :)

Ack. I though wonder if should be packaged separately.

Despite it is not mentioned in the release notes, AFAIK the capability
to be used as serial terminal has been removed as well and for many
this is a deal breaker.

I also already received requests to patch Screen 5.0.0 to include the
nethack feature again...

So I currently see this possibilities:

1. Ignore these feature removals, move forward and package Screen
   5.0.0 as "screen".

2. Rename "screen" to "screen4" and package Screen 5.0.0 as "screen".

3. Package Screen 5.0.0 as "screen5".

(2. and 3. are nevertheless only feasible in the long run if upstream
at least continues to provide security features for their screen-v4
branch for a while.)

Will check if serial support really has been removed—as I would have
expected it to be included in the release notes. If it's still
there, chances are very high that I'll go with option #1.

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE



Bug#1079577: supysonic: crashes if media file path contains non-ASCII characters

2024-08-24 Thread Axel
Package: supysonic
Version: 0.7.2+ds-2
Severity: important
X-Debbugs-Cc: a...@users.sourceforge.net

Dear Maintainer,

the app (e.g. Tempo) shows all files but Supysonic crashes if the file to play 
or
transcode contains a Unicode character like “Ö“ in its path or file name. As a
consequence, such files cannot be played in the app, while files whose paths 
and names
only contain ASCII characters, are easily played.


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

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

Versions of packages supysonic depends on:
ii  fonts-glyphicons-halflings  1.009~3.4.1+dfsg-3
ii  libjs-bootstrap 3.4.1+dfsg-3
ii  libjs-jquery3.6.1+dfsg+~3.5.14-1
ii  libjs-sphinxdoc 5.3.0-4
ii  python3 3.11.2-1+b1
ii  python3-click   8.1.3-2
ii  python3-flask   2.2.2-3
ii  python3-lxml4.9.2-1+b1
ii  python3-mediafile   0.11.0-1
ii  python3-pil 9.4.0-1.1+deb12u1
ii  python3-pony0.7.16+ds-3
ii  python3-requests2.28.1+dfsg-1
ii  python3-watchdog2.2.1-1
ii  python3-zipstream-ng1.4.0-1

Versions of packages supysonic recommends:
ii  flac 1.4.2+ds-2
ii  lame 3.100-6
ii  libapache2-mod-wsgi-py3  4.9.4-1+b2

Versions of packages supysonic suggests:
ii  python3-psycopg2  2.9.5-1+b1

-- debconf-show failed


Bug#1077869: [Pkg-zsh-devel] Bug#1077869: zsh: please use secure URLs in debian/upstream/metadata

2024-08-05 Thread Axel Beckert
Control: tag -1 + confirmed

Hi Simon,

Simon McVittie wrote:
> While looking for upstream fixes for zsh compatibility with gcc 14,
> I noticed that the source package uses git:// and http:// URLs in
> debian/upstream/metadata, which do not authenticate the identity of the
> remote server and so are vulnerable to man-in-the-middle attacks. Please
> replace them with their equivalent https:// URLs, for example by applying
> the attached patch.

Thanks. The last time I looked, IIRC neither HTTPS *.sourceforge.io
not git over HTTPS did work. But that was probably already more than a
year ago.

> -Changelog: http://zsh.sourceforge.net/releases.html
> +Changelog: https://zsh.sourceforge.io/releases.html

Works.

> -FAQ: http://zsh.sourceforge.net/FAQ/
> +FAQ: https://zsh.sourceforge.io/FAQ/

Works.

> -Homepage: http://zsh.sourceforge.net/
> +Homepage: https://zsh.sourceforge.io/

Works.

> -Repository: git://git.code.sf.net/p/zsh/code
> +Repository: https://git.code.sf.net/p/zsh/code

Odd. Works with "git clone", but not in a browser. Oh well.

> -Documentation: http://zsh.sourceforge.net/Doc/
> +Documentation: https://zsh.sourceforge.io/Doc/

Works.

So yes, we should apply this.

P.S.: Thanks also for the gcc-14 patch!

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE



Bug#1077557: Most changelog items missing in 2.117.1 changelog entry (Re: lintian_2.117.1_source.changes ACCEPTED into unstable)

2024-07-30 Thread Axel Beckert
Hi Bastien,

Bastien Roucariès wrote:
> > Thanks a lot for stepping in and daring to do a Lintian release!
> > 
> > Unfortunately a few things went rather bad and I wanted to fix
> > this up quickly:
> > 
> > * No tag change summary (private/generate-tag-summary not run)
> > 
> > * Most changelog entries and closed bug numbers missing. (gbp dch not
> >   run or went weirdly bad?) IMHO this makes this version of Lintian
> >   unfit for release, hence the RC severity. Also to avoid that this
> >   version to migrates to testing.

> > * Wrong version number. There are quite some new tags in this release,
> >   hence a feature additions, which requires the minor version to be
> >   bumped (i.e. to 2.118.0) according to Semantic Versioning (which
> >   Lintian tries to follow for a while now): https://semver.org/
> > 
> > * The last git commits included in the upload are not pushed to the
> >   git repository on Salsa.
> 
> Will fix and add a checklist to CONTRIBUTING.md

Merci beaucoup!

Actually some parts are already in there indirectly via the pointer to
doc/release.md:

$ private/generate-tag-summary --in-place

But the "gbp dch" seems indeed missing (I also see no script calling
that) except for a hint with "e.g. via `dch -r`", despite the switch
to it happened in early 2019.

Instead there's a lot of outdated stuff about no more existing
lintian.debian.org in there.

I'll try to cross-check what else is no more up-to-date in these two
files as soon as I find time to work on Lintian again. (Hopefully
rather soon.)

What also should go into that checklist is running the

  private/post-release-version-bump

script after the upload. It creates that "WIP (generated at release
time: please do not add entries below.)" line and updates the version
number in debian/changelog.

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE



Bug#1077557: Most changelog items missing in 2.117.1 changelog entry (Re: lintian_2.117.1_source.changes ACCEPTED into unstable)

2024-07-29 Thread Axel Beckert
Package: lintian
Version: 2.117.1
Severity: serious

Hi Bastien,

Debian FTP Masters wrote:
> Date: Sat, 27 Jul 2024 21:39:04 +
> Source: lintian
> Architecture: source
> Version: 2.117.1
> Distribution: unstable
> Urgency: medium
> Maintainer: Debian Lintian Maintainers 
> Changed-By: Bastien Roucariès 
> Closes: 1077112
> Changes:
>  lintian (2.117.1) unstable; urgency=medium
>  .
>[ Axel Beckert ]
>* Retroactively mention #1033894 in previous changelog entry.
>  .
>[ Otto Kekäläinen ]
>* Declare compliance with Debian Policy 4.7.0
>* Salsa-CI: Run both current and new Lintian to
>  ensure full compatibility
>  .
>[ Bastien Roucariès ]
>* Avoid an error with recent dpkg tools
>* Workarround failure with recent gcc
>* invalid-versioned-provides could not be anymore tested
>  due to dpkg-dev change
>* rebuild against dh-elpa >=2.1.5 (Closes: #1077112)
> Checksums-Sha1: […]

Thanks a lot for stepping in and daring to do a Lintian release!

Unfortunately a few things went rather bad and I wanted to fix
this up quickly:

* No tag change summary (private/generate-tag-summary not run)

* Most changelog entries and closed bug numbers missing. (gbp dch not
  run or went weirdly bad?) IMHO this makes this version of Lintian
  unfit for release, hence the RC severity. Also to avoid that this
  version to migrates to testing.
  
* Wrong version number. There are quite some new tags in this release,
  hence a feature additions, which requires the minor version to be
  bumped (i.e. to 2.118.0) according to Semantic Versioning (which
  Lintian tries to follow for a while now): https://semver.org/

* The last git commits included in the upload are not pushed to the
  git repository on Salsa.

Especially because of the last issue, currently nobody can continue
working on Lintian and fix the other things mentioned. So please push
your work as soon as possible, so that we can fix the remaining issues
with the 2.117.1.

This is what I would retroactively add to the 2.117.1 changelog entry
(based on current git with the current changelog entries from the
upload manually fiddled in) and then just tagging an 2.118.0 release
to get things back on track:

+  * Summary of tag changes:
++ Added:
+  - gir-package-name-does-not-match
+  - package-installs-deprecated-python2-path
+  - systemd-alternatives
+  - systemd-diversion
+  - uses-deprecated-python-stdlib
++ Removed:
+  - uses-python-distutils

   [ Axel Beckert ]
   * Retroactively mention #1033894 in previous changelog entry.
+  * data/changes-file/known-dists: Add trixie and forky
+  * Refresh data (fonts and debhelper add-ons and commands)
+  * Refresh data (add-ons, commands, fonts)

   [ Bastien Roucariès ]
+  * Avoid an error with recent dpkg tools
+  * Workarround failure with recent gcc
+  * invalid-versioned-provides could not be anymore tested due to
+dpkg-dev change
   * rebuild against dh-elpa >=2.1.5 (Closes: #1077112)

+  [ Simon McVittie ]
+  * gobject-introspection | dh-sequence-gir implements dh --with=gir
+(Closes: #964290, #1063709)
+  * gir: Also look for GIR XML in /usr/lib/${DEB_HOST_MULTIARCH}/gir-1.0
+  * t/recipes/checks/desktop/gnome/gir: Install multiarch files correctly
+  * t: Assert that desktop/gnome/gir checks are done on multiarch locations
+  * t: Exercise the good (no warnings) case for multiarch desktop/gnome/gir
+  * tags: Describe preferred Provides for typelib-package-name-does-not-match
+  * tags: Mention the multiarch directory for public GIR XML
+  * tags: Say how to add Depends/Provides for gir-missing-typelib-dependency
+  * t: Catch up with best practices for GIR XML packaging
+  * desktop/gnome/gir: Check for GIR XML canonical naming
+  * data: Add nogir as a known build-profile
+
+  [ Louis-Philippe Véronneau ]
+  * missing-prerequisite-for-pyproject-backend: add support for whey
+  * Modify checks for the python3-pdm-pep517 -> python3-pdm-backend rename.
+  * New tag: uses-deprecated-python-stdlib
+  * New tag: package-installs-deprecated-python2-path (Closes: #1033294)
+  * Refactor 'python-module-in-wrong-location' check
+
+  [ Nilesh Patra ]
+  * Obsolete package python3-pdm-pep517 replaced by python3-pdm-backend
+  * Remove strict check for comma in "Origin" field in DEP3 header
+  * [ci skip] Revert "Remove strict check for comma in "Origin" field in
+DEP3 header"
+
+  [ James McCoy ]
+  * t: Fix compilation failures with dpkg 1.22.6 (Closes: #1066261)
+
+  [ Colin Watson ]
+  * Add alioth-lists.debian.net to team maintenance check
+
+  [ Simon Quigley ]
+  * Add "oracular" as a known Ubuntu distribution.
+
+  [ Bo YU ]
+  * Update debian-policy for 4.7.0
+
+  [ Kentaro Hayashi ]
+  * ci: check longer timeout for autopkgtest
+
+  [ Luca Boccassi ]
+  * Upgrade the severity of missing-sy

Bug#1076556: opensc: egk-tool shows no data

2024-07-18 Thread Axel Stammler
Package: opensc
Version: 0.23.0-0.3+deb12u1
Severity: normal
X-Debbugs-Cc: a...@users.sourceforge.net

Dear Maintainer,

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

The output never shows any data even though the card is valid and functional:

$ egk-tool -v
Using reader with a card: Lenovo Lenovo USB Smartcard Keyboard [Lenovo Keyboard 
Smartcard Reader] (0911040045) 00 00
Connecting to card in reader Lenovo Lenovo USB Smartcard Keyboard [Lenovo 
Keyboard Smartcard Reader] (0911040045) 00 00...
Using card driver STARCOS.
$ egk-tool --pd
Using reader with a card: Lenovo Lenovo USB Smartcard Keyboard [Lenovo Keyboard 
Smartcard Reader] (0911040045) 00 00
$ egk-tool --vd
Using reader with a card: Lenovo Lenovo USB Smartcard Keyboard [Lenovo Keyboard 
Smartcard Reader] (0911040045) 00 00
$ egk-tool -v --vd
Using reader with a card: Lenovo Lenovo USB Smartcard Keyboard [Lenovo Keyboard 
Smartcard Reader] (0911040045) 00 00
Connecting to card in reader Lenovo Lenovo USB Smartcard Keyboard [Lenovo 
Keyboard Smartcard Reader] (0911040045) 00 00...
Using card driver STARCOS.
$ egk-tool --gvd
Using reader with a card: Lenovo Lenovo USB Smartcard Keyboard [Lenovo Keyboard 
Smartcard Reader] (0911040045) 00 00
$

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

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

Versions of packages opensc depends on:
ii  libc6  2.36-9+deb12u7
ii  libreadline8   8.2-1.3
ii  libssl33.0.13-1~deb12u1
ii  opensc-pkcs11  0.23.0-0.3+deb12u1
ii  zlib1g 1:1.2.13.dfsg-1

Versions of packages opensc recommends:
ii  pcscd  1.9.9-2

opensc suggests no packages.

-- debconf-show failed



Bug#1076456: iptables-netflow-dkms: No more builds on Debian 11 Bullseye since kernel linux-image-5.10.0-31-amd64 (5.10.221-1) due to "unexport find_module" kernel backport from 5.12

2024-07-16 Thread Axel Beckert
Package: iptables-netflow-dkms
Version: 2.5.1-2
Severity: grave
Tags: patch bullseye

Since linux-image-5.10.0-31-amd64/5.10.221-1, ipt_NETFLOW.ko no more
builds on Debian 11 Bullseye:

Citing from /var/lib/dkms/ipt-netflow/2.5.1/build/make.log:

DKMS make.log for ipt-netflow-2.5.1 for kernel 5.10.0-31-amd64 (x86_64)
Tue Jul 16 16:17:06 UTC 2024
./gen_compat_def > compat_def.h
Test symbol xt_family linux/netfilter_ipv4/ip_tables.h
Test struct timeval linux/ktime.h
Test struct proc_ops linux/proc_fs.h
Test symbol synchronize_sched linux/rcupdate.h
Compiling for kernel 5.10.221
make -C /lib/modules/5.10.0-31-amd64/build 
M=/var/lib/dkms/ipt-netflow/2.5.1/build modules CONFIG_DEBUG_INFO
make[1]: warning: jobserver unavailable: using -j1.  Add '+' to parent make 
rule.
make[1]: Entering directory '/usr/src/linux-headers-5.10.0-31-amd64'
  CC [M]  /var/lib/dkms/ipt-netflow/2.5.1/build/ipt_NETFLOW.o
/var/lib/dkms/ipt-netflow/2.5.1/build/ipt_NETFLOW.c: In function 'nf_seq_show':
/var/lib/dkms/ipt-netflow/2.5.1/build/ipt_NETFLOW.c:755:39: warning: format 
'%lu' expects argument of type ' 3 has type 's64' {aka 'long long int'} 
[-Wformat=]
  755 |seq_printf(seq, " Flows selected %lu, discarded %lu.",
  | ~~^
  |   |
  |   long unsigned int
  | %llu
/var/lib/dkms/ipt-netflow/2.5.1/build/ipt_NETFLOW.c:755:54: warning: format 
'%lu' expects argument of type ' 4 has type 's64' {aka 'long long int'} 
[-Wformat=]
  755 |seq_printf(seq, " Flows selected %lu, discarded %lu.",
  |~~^
  |  |
  |  long unsigned int
  |%llu
/var/lib/dkms/ipt-netflow/2.5.1/build/ipt_NETFLOW.c:759:39: warning: format 
'%lu' expects argument of type ' 3 has type 's64' {aka 'long long int'} 
[-Wformat=]
  759 |seq_printf(seq, " Flows selected %lu.", 
atomic64_read(&flows_selected));
  | ~~^
  |   |
  |   long unsigned int
  | %llu
  MODPOST /var/lib/dkms/ipt-netflow/2.5.1/build/Module.symvers
ERROR: modpost: "find_module" 
[/var/lib/dkms/ipt-netflow/2.5.1/build/ipt_NETFLOW.ko] undefined!
make[3]: *** 
[/usr/src/linux-headers-5.10.0-31-common/scripts/Makefile.modpost:123: 
/var/lib/dkms/ipt-netfloror 1
make[3]: *** Deleting file 
'/var/lib/dkms/ipt-netflow/2.5.1/build/Module.symvers'
make[2]: *** [/usr/src/linux-headers-5.10.0-31-common/Makefile:1783: modules] 
Error 2
make[1]: *** [/usr/src/linux-headers-5.10.0-31-common/Makefile:192: __sub-make] 
Error 2
make[1]: Leaving directory '/usr/src/linux-headers-5.10.0-31-amd64'
make: *** [Makefile:25: ipt_NETFLOW.ko] Error 2

This happens, because upstream kernel 5.10.220 backported this change
from kernel 5.12:

- module: unexport find_module and module_mutex

Backporting upstream commit
https://github.com/aabc/ipt-netflow/commit/5aae3791922bd3df878605b15e83ea48a4bd096c
with updated version constraint fixes the issue:

Index: iptables-netflow-2.5.1/compat.h
===
--- iptables-netflow-2.5.1.orig/compat.h
+++ iptables-netflow-2.5.1/compat.h
@@ -749,4 +749,29 @@ unsigned long long strtoul(const char *c
return result;
 }
 
+#if LINUX_VERSION_CODE >= KERNEL_VERSION(5,12,0) || LINUX_VERSION_CODE >= 
KERNEL_VERSION(5,10,220)
+/*
+ * find_module() is unexported in v5.12:
+ *   089049f6c9956 ("module: unexport find_module and module_mutex")
+ * and module_mutex is replaced with RCU in
+ *   a006050575745 ("module: use RCU to synchronize find_module")
+ */
+#include 
+struct module *find_module(const char *name)
+{
+   struct module *mod;
+
+   rcu_read_lock_sched();
+   /* Yes this is crazy, but should work. */
+   list_for_each_entry_rcu(mod, &THIS_MODULE->list, list) {
+   if (!strcmp(mod->name, name)) {
+   rcu_read_unlock_sched();
+   return mod;
+   }
+   }
+   rcu_read_unlock_sched();
+   return NULL;
+}
+#endif
+
 #endif /* COMPAT_NETFLOW_H */

I intend to do a bullseye-proposed-stable upload for that.



Bug#1074494: Bug#1071199: O: wicd -- wired and wireless network manager written in Python

2024-06-30 Thread Axel Beckert
Hi Jeremy,

Jeremy Bícha wrote:
> Package: ftp.debian.org
> User: ftp.debian@packages.debian.org
> Usertags: remove
> X-Debbugs-Cc: w...@packages.debian.org
> Control: affects -1 src:wicd
> 
> Please remove wicd from Debian experimental. It was removed from
> unstable years ago and is not present in stable or oldstable. It has
> not been updated in experimental since its removal from unstable.

Jeremy Bícha wrote:
> Oh, I was not expecting a recent bug like this to exist. I only
> noticed it after I requested (and got) removal of wicd from
> experimental earlier today.

*sigh*

> I guess this counts as the "month or two" you suggested.

Yes. it does and the removal is fine. I though would have expected
that you at least have a short look at
https://tracker.debian.org/pkg/wicd before requesting remove as it
clearly listed #1071199 under "action needed" (and currently still
does, but I will close it with this mail).

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE



Bug#1073239: bb: either no sound frozen text output while using pulseaudio as default on more recent debian

2024-06-15 Thread Axel Beckert
Control: severity -1 important
Control: forcemerge 123150 -1

Hi,

t...@treaki.tk wrote:
> Severity: grave
> Justification: renders package unusable

No, it doesn't. See
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=123150#189 for an
easy workaround. Hence severity important is more fitting—the same
severity as #123150 has, btw.

> debian 11 and i have seen this bug since debian 7 or so,

Yes, that's https://bugs.debian.org/123150

> please look into it finally.

Please note that we already looked into it, it's non-trivial, there
are known workarounds and we've asked for _help_ on this—not for
bashing. Please read https://bugs.debian.org/123150

    Regards, Axel
-- 
 ,''`.  |  Axel Beckert , https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE



Bug#1073114: unburden-home-dir: stop build-depending on pcre3

2024-06-14 Thread Axel Beckert
Control: tag -1 + patch pending

Hi again

Axel Beckert wrote:
> The sole reason I use it over grep is that it supports multiline
> matches. It though seems that grep might be able to do that — albeit
> non-obviously — via "grep -Pzov", too.

Nope, even much simpler cases fail to remove just a substring from a
single line:

~ → printf 'foo\ngnarz\nbar\n' | fgrep -voz nar
~ → printf 'foo\ngnarz\nbar\n' | fgrep -ov nar

etc.

> Otherwise, I'll probably just use the original with "perl -E". It's
> just the build system trying to remove any unwanted crap (multiline
>  tags including their contents) from the generated HTML
> documentation.

The following change works and produces byte for byte the identical
result as "pcregrep -Mv", it's just a bit longer:

-   pcregrep -Mv 
'<script[^>]*>[^<]*|<(form|input).*?>|' | \
+   perl -E 'local $$/; my $$input=<>; $$input =~ 
s:]*>[^<]*\n*|<(form|input).*?>|\n*::gsm; print 
$$input;' | \

("$$" instead of "$" is needed even inside single quotes as this is
inside a Makefile where $ is a special character already.)

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE



Bug#1073114: unburden-home-dir: stop build-depending on pcre3

2024-06-14 Thread Axel Beckert
Control: tag -1  + confirmed

Hi Chris,

Chris Hofstaedtler wrote:
> we want to get rid of pcre3 in trixie. As such unburden-home-dir's
> Build-Depends on pcregrep dependency will become unsatisfiable.

Thanks for the bug report! So pcregrep hasn't been ported (by
PCRE upstream) to libpcre2 either? *sigh*

The sole reason I use it over grep is that it supports multiline
matches. It though seems that grep might be able to do that — albeit
non-obviously — via "grep -Pzov", too.

Otherwise, I'll probably just use the original with "perl -E". It's
just the build system trying to remove any unwanted crap (multiline

Bug#1072922: nullmailer: "sendmail -bs" crashes: "traps: nullmailer-smtp[15059] general protection fault ip:7f0368d73dd9 sp:7fff5e3d7088 error:0 in libc.so.6[7f0368c41000+157000]"

2024-06-10 Thread Axel Beckert
Hi David,

David Bremner wrote:
> swaks -t brem...@debian.org --pipe 'gdb -batch -ex run -ex bt --args 
> /usr/lib/sendmail -bs'
> 
> This actually runs without segfaulting, which made me think it might be
> a memory error.

There's one memory fix commit upstream in the master branch:
https://github.com/bruceg/nullmailer/commit/834e2eb6b7eac2648fc371c432a46e98d5966bb4

Could it be this one? At least "fdbuf.c" sounds as if it might be
involved in file descriptor thingies.

> Attempt #3
> 
> swaks -t brem...@debian.org --pipe 'valgrind /usr/lib/sendmail -bs'
> 
> This also runs without errors,

Clearly a Heisenbug. ;-)

> so I'm out of ideas for the moment.

Maybe upstream has an idea if it's not that already made commit?

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE



Bug#1072232: screen: use wtmpdb to write wtmp entries

2024-06-10 Thread Axel Beckert
Control: block -1 by 1072237

Hi Chris,

Chris Hofstaedtler wrote:
> Per the discussion on debian-devel, Debian will switch to wtmpdb for
> Y2038-safe wtmp recording. If your package writes wtmp entries,
> please switch to libwtmpdb.

Well, screen in Debian does not write them directly but via the
utempter helper utility from the libutempter0 package to avoid
setgid-/setuid-related security issues.

So I assume this bug report is depending on the fix of
https://bugs.debian.org/1072237

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE



Bug#1072922: nullmailer: "sendmail -bs" crashes: "traps: nullmailer-smtp[15059] general protection fault ip:7f0368d73dd9 sp:7fff5e3d7088 error:0 in libc.so.6[7f0368c41000+157000]"

2024-06-10 Thread Axel Beckert
Package: nullmailer
Version: 1:2.2+10~g7ed88a0-5
Severity: important
Control: found -1 1:2.2-3

Dear David,

I managed to reproducibly crash nullmailer-smtpd with a "general
protection fault" by calling the following command:

  swaks -t a...@debian.org --pipe 'sendmail -bs'

This call produces the following output first:

  === Trying pipe to sendmail -bs...
  === Connected to sendmail -bs.
  <-  220 nullmailer-smtpd ready
   -> EHLO kote1.lugs.ch
  <-  250 2.3.0 OK
   -> MAIL FROM:
  <-  250 2.1.0 Sender accepted
   -> RCPT TO:
  <-  250 2.1.5 Recipient accepted
   -> DATA
  <-  354 End your message with a period on a line by itself
   -> Date: Mon, 10 Jun 2024 13:21:49 +0200
   -> To: a...@debian.org
   -> From: r...@kote1.lugs.ch
   -> Subject: test Mon, 10 Jun 2024 13:21:49 +0200
   -> Message-Id: <20240610132149.015...@kote1.lugs.ch>
   -> X-Mailer: swaks v20240103.0 jetmore.org/john/code/swaks/
   ->
   -> This is a test mailing
   ->
   ->
   -> .
  *** Child process closed connection unexpectedly.

In /var/log/syslog I then find these log entries:

  2024-06-10T13:21:49.468475+02:00 kote1 nullmailer: Trigger pulled.
  2024-06-10T13:21:49.468687+02:00 kote1 nullmailer: Rescanning queue.
  2024-06-10T13:21:49.468781+02:00 kote1 nullmailer: Starting delivery, 1 
message(s) in queue.
  2024-06-10T13:21:49.468793+02:00 kote1 nullmailer: Starting delivery: host: … 
protocol: smtp file: 1718018509.15060
  2024-06-10T13:21:49.468802+02:00 kote1 nullmailer: From:  
to: 
  2024-06-10T13:21:49.468808+02:00 kote1 nullmailer: Message-Id: 
<20240610132149.015...@kote1.lugs.ch>
  2024-06-10T13:21:49.471688+02:00 kote1 kernel: traps: nullmailer-smtp[15059] 
general protection fault ip:7f0368d73dd9 sp:7fff5e3d7088 error:0 in 
libc.so.6[7f0368c41000+157000]
  2024-06-10T13:21:49.600127+02:00 kote1 nullmailer: smtp: Succeeded: 250 2.6.0 
<20240610132149.015...@kote1.lugs.ch> [InternalId=172490181574991, Hostname=…] 
1171 bytes in 0.106, 10.754 KB/sec Queued mail for delivery
  2024-06-10T13:21:49.601067+02:00 kote1 nullmailer: Sent file.
  2024-06-10T13:21:49.601118+02:00 kote1 nullmailer: Delivery complete, 0 
message(s) remain.

The mail though seemed to end up in the queue. But since swaks exits
with non-zero due to "sendmail -bs" exits with non-zero, our Ansible
playbook fails, too.

I initially ran into this on a production host running Debian 11
Bullseye with different settings (hence marking as found in the version
in Bullseye), but I can still reproduce it on a test VM with Debian
Unstable where I installed nullmailer temporarily as well. (Bug report
resembles state on the latter.)

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

Kernel: Linux 6.8.12-amd64 (SMP w/4 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: sysvinit (via /sbin/init)
LSM: AppArmor: enabled

Versions of packages nullmailer depends on:
ii  debconf [debconf-2.0]  1.5.86
ii  libc6  2.38-12.1
ii  libgnutls30t64 3.8.5-4
ii  libstdc++6 14.1.0-1

nullmailer recommends no packages.

nullmailer suggests no packages.

-- debconf information:
* shared/mailname: kote1.lugs.ch
* nullmailer/relayhost:
* nullmailer/adminaddr: a...@deuxchevaux.org
  nullmailer/defaultdomain: lugs.ch



Bug#1072522: cozy: File conflict with blackbox-terminal/0.14.0-3: /usr/share/icons/hicolor/scalable/actions/settings-symbolic.svg

2024-06-03 Thread Axel Beckert
Package: cozy
Severity: serious
Version: 1.3.0-2
Control: affects -1 blackbox-terminal

Hi Manuel,

installing cozy fails if blackbox-terminal (at least at version
0.14.0-3) is also installed due to a file conflict at
/usr/share/icons/hicolor/scalable/actions/settings-symbolic.svg (and
potentially further files as dpkg always only reports the first
occurrence):

Preparing to unpack .../11-cozy_1.3.0-2_all.deb ...
Unpacking cozy (1.3.0-2) ...
dpkg: error processing archive 
/tmp/apt-dpkg-install-RrJabH/11-cozy_1.3.0-2_all.deb (--unpack):
 trying to overwrite 
'/usr/share/icons/hicolor/scalable/actions/settings-symbolic.svg', which is 
also in package blackbox-terminal 0.14.0-3

The probably easiest and cleanest way to fix this is to rename the
file. Best way would be if neither package would use such a generic file
name. (X-Debbugs-Cc'ed the blackbox-terminal maintainers.)

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

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



Bug#1071414: mediathekview: make radio programmes available, too

2024-05-18 Thread Axel
Package: mediathekview
Version: 13.2.1+ds-1
Severity: wishlist
X-Debbugs-Cc: a...@users.sourceforge.net

Dear Maintainer,

It would be great if radio programmes could be included, e.g. radio theatre from
Deutschlandfunk and science from BR24.

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

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

Versions of packages mediathekview depends on:
ii  default-jre [java9-runtime] 2:1.17-74
ii  java-wrappers   0.4
ii  libcommons-compress-java1.22-1
ii  libcommons-configuration2-java  2.8.0-2
ii  libcommons-dbcp2-java   2.9.0-1
ii  libcommons-lang3-java   3.12.0-2
ii  libcommons-pool2-java   2.11.1-1
ii  libcontrolsfx-java  11.0.0-1
ii  libguava-java   31.1-1
ii  libjackson2-core-java   2.14.1-1
ii  libjchart2d-java3.2.2+dfsg2-3
ii  libjiconfont-font-awesome-java  4.7.0.1-1
ii  libjiconfont-java   1.0.0-2
ii  libjiconfont-swing-java 1.0.1-2
ii  libjide-oss-java3.7.6+dfsg-2
ii  liblog4j2-java  2.19.0-2
ii  libmbassador-java   1.3.1-2
ii  libmiglayout-java   5.1-3
ii  libokhttp-java  3.13.1-3
ii  libopenjfx-java 11.0.11+1-3
ii  libslf4j-java   1.7.32-1
ii  libswingx-java  1:1.6.2-4
ii  libxz-java  1.9-1
ii  openjdk-17-jre [java9-runtime]  17.0.11+9-1~deb12u1

Versions of packages mediathekview recommends:
ii  flvstreamer  2.1c1-1.1
ii  mplayer  2:1.5+svn38408-1
ii  mpv  0.35.1-4

Versions of packages mediathekview suggests:
ii  ffmpeg  7:5.1.4-0+deb12u1

-- no debconf information



Bug#1067025: dokuwiki: Please package the new upstream version 2024-02-06a "Kaos"

2024-05-15 Thread Axel Beckert
Hi Daniel,

Daniel Baumann wrote one month ago:
> any news or ETA on this?

No. I can work on this earliest after the next Lintian release. (Which
I hope to get done during Pentecoste.)

> do you need help?

I fear so. Actually I've taken over Debian's dokuwiki after I NMUed it
because it was horribly out of date and had open RC bugs.

But I currently can't invest as much time in Debian as I probably
should and there are more pressing issues like a new Lintian release
and some RC bugs in other packages of mine.

Not sure about Anton. Haven't heard from him in a while with regards
to DokuWiki, but he seems generally active in Debian.

So if you want to join Debians DokuWiki team as another uploader, feel
free to add yourself and work on the package.

    Regards, Axel
-- 
 ,''`.  |  Axel Beckert , https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE


signature.asc
Description: PGP signature


Bug#1071199: O: wicd -- wired and wireless network manager written in Python

2024-05-15 Thread Axel Beckert
Package: wnpp
Severity: normal
X-Debbugs-Cc: w...@packages.debian.org, txg...@gmail.com, z...@fsfe.org, 
a...@bastelmap.de, b...@debian.org
Control: affects -1 + src:wicd

Let's face it, neither me nor Giap Tran haven't done anything on wicd
since 2019 — beside moving it from unstable to experimental due to the
rather incomplete upstream state of the Python 3 port. I even forgot
to push a commit for years. (I just pushed things now and merged
Bastian's changes from Salsa. → https://salsa.debian.org/debian/wicd)

Looking at https://git.launchpad.net/wicd/log/ it seems that since
then yet another dev (Andreas Messer) tried himself on wicd upstream
and stopped again. (The last dev I had contact with was Guido Serra.)

(I've X-Debbugs-Cc'ed all mentioned persons.)

I actually haven't looked yet if the code as of October 2022 (just
documentation changes afterwards) actually works as the last device
where I used wicd on for wifi connections (an Asus EeePC 900) got very
unreliable due to fan failure. And I haven't fixed that yet.

The package is currently only available in Debian Experimental (see
https://tracker.debian.org/pkg/wicd) and its description is:

 Wicd is a general-purpose network configuration server which aims
 to provide a simple but flexible interface for connecting to networks.

 Its features include:

  * wide variety of settings;
  * ability to connect to (and maintain profiles for) both wired and
wireless networks;
  * support for many encryption schemes, including WEP, WPA, WPA2 and
custom schemes;
  * wireless-tools compatibility;
  * tray icon showing network activity and signal strength;
  * lack of GNOME dependencies (although it does require GTK+), making it
easy to use in Xfce, Fluxbox, Openbox, Enlightenment, etc.

In case there's nobody stepping up for adoption within a month or two
or so, I'll probably request removal from Debian. It's in bad shape
for long enough and I have enough other packages which need my time.


Bug#1071007: sherlock has an undeclared file conflict on /usr/lib/python3/dist-packages/__init__.py

2024-05-13 Thread Axel Beckert
Control: affects -1 - pycrc
Control: clone -1 -2 -3
Control: reassign -2 pycrc 0.10.0-2
Control: retitle -1 sherlock: Must not ship 
/usr/lib/python3/dist-packages/__init__.py
Control: retitle -2 pycrc: Must not ship 
/usr/lib/python3/dist-packages/__init__.py
Control: reassign -3 lintian 2.117.0
Control: severity -3 wishlist
Control: retitle -3 lintian: Should warn if a package ships 
/usr/lib/python*/dist-packages/__init__.py

Hi Helmut,

Helmut Grohne wrote:
> This bug report has been automatically filed with no human intervention.
> The source code is available at https://salsa.debian.org/helmutg/dumat.

Ok, this explains why you didn't notice that this is actually a
separate bug in each of these packages. :-)

> sherlock has an undeclared file conflict. This may result in an unpack
> error from dpkg.
> 
> The file /usr/lib/python3/dist-packages/__init__.py is contained in the
> packages
>  * pycrc/0.10.0-2 as present in trixie|unstable
>  * sherlock/0.14.3+git20240511.b83f5be-1 as present in unstable

My Python foo isn't that well versed, but as far as I understand
actually no package must ship an __init__.py file at (more or less)
root level (i.e. directly in /usr/lib/python*/dist-packages/ or — since
usrmerge also — /lib/python*/dist-packages/).

Accordingly cloning the bug report for pycrc as it must not ship that
file either.

And cloning it a second time as wishlist bug report against Lintian so
that these cases get caught much earlier. Might be implemented as
extension of python-module-has-overly-generic-name (as the module name
seems the empty string in that case ;-) which so far already catches
cases like e.g. /usr/lib/python3/dist-packages/doc/__init__.py.

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE


signature.asc
Description: PGP signature


Bug#1070295: cgroupfs-mount: Fails to upgrade or remove if elogind is running: "umount: /sys/fs/cgroup/elogind: target is busy."

2024-05-03 Thread Axel Beckert
Package: cgroupfs-mount
Severity: serious
Version: 1.4+nmu1

Hi,

cgroupfs-mount fails to upgrade from 1.4 to 1.4+nmu1 for me (elogind +
sysvinit) as follows:

Setting up cgroupfs-mount (1.4+nmu1) ...
Unmounting cgroupfs hierarchyumount: /sys/fs/cgroup/elogind: target is busy.
invoke-rc.d: initscript cgroupfs-mount, action "restart" failed.
dpkg: error processing package cgroupfs-mount (--configure):
 installed cgroupfs-mount package post-installation script subprocess returned 
error exit status 1

Trying to remove the package fails in the same way:

Removing cgroupfs-mount (1.4+nmu1) ...
Unmounting cgroupfs hierarchyumount: /sys/fs/cgroup/elogind: target is busy.
invoke-rc.d: initscript cgroupfs-mount, action "stop" failed.
dpkg: error processing package cgroupfs-mount (--remove):
 installed cgroupfs-mount package pre-removal script subprocess returned error 
exit status 1

Stopping elogind before trying to unmount /sys/fs/cgroup/elogind solves
the issue.

P.S.: Given that Christian's NMU doesn't even touch the maintainer
scripts, I suspect that this issue is also present in version 1.4. I
though didn't notice it before then, so it might be related to recent
elogind changes, hence Cc'ing the Debian Init System Diversity Team,
too.

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

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



Bug#1066438: backuppc-rsync: FTBFS: lib/compat.c:154:16: error: too few arguments to function ‘gettimeofday’

2024-04-18 Thread Axel Beckert
Control: tag -1 + patch

Hi Andreas,

Andreas Hasenack wrote:
> This fixes the build:
> 
> --- a/configure.ac
> +++ b/configure.ac
> @@ -852,6 +852,7 @@ fi
> 
>  AC_CACHE_CHECK([if gettimeofday takes tz
> argument],rsync_cv_HAVE_GETTIMEOFDAY_TZ,[
>  AC_COMPILE_IFELSE([AC_LANG_PROGRAM([[#include 
> +#include 
>  #include ]], [[struct timeval tv; exit(gettimeofday(&tv,
> NULL));]])],[rsync_cv_HAVE_GETTIMEOFDAY_TZ=yes],[rsync_cv_HAVE_GETTIMEOFDAY_TZ=no])])
>  if test x"$rsync_cv_HAVE_GETTIMEOFDAY_TZ" != x"no"; then
>  AC_DEFINE(HAVE_GETTIMEOFDAY_TZ, 1, [Define to 1 if gettimeofday()
> takes a time-zone arg])

Thanks a lot! I was always trying to add that include line into actual
C files. It didn't occur to me that I need to add it to configure.

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE



Bug#1068183: php-horde: Cannot use administrative functions

2024-04-01 Thread Axel
Package: php-horde
Version: 5.2.23+debian0-6
Severity: important
X-Debbugs-Cc: a...@users.sourceforge.net

Dear Maintainer,

the menu entries "Administratin → Users" and "Update all configurations" lead 
to HTTP
error 500; user.log contains the line

PHP ERROR: Trying to access array offset on value of type null [pid 802365 on 
line 146 of "/usr/share/php/Horde/Themes/Element.php"]


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

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

Versions of packages php-horde depends on:
ii  dpkg   1.21.22
ii  php2:8.2+93
ii  php-cli2:8.2+93
ii  php-common 2:93
ii  php-horde-alarm2.2.10-10
ii  php-horde-argv 2.1.0-9
ii  php-horde-auth 2.2.2-10
ii  php-horde-autoloader   2.1.2-11
ii  php-horde-browser  2.0.16-5
ii  php-horde-core 2.31.18+debian0-2
ii  php-horde-date 2.4.1-9
ii  php-horde-exception2.0.8-10
ii  php-horde-form 2.0.20-2
ii  php-horde-group2.1.1-12
ii  php-horde-http 2.1.7-11
ii  php-horde-image2.6.1-2
ii  php-horde-logintasks   2.0.8-1
ii  php-horde-mail 2.6.6-5
ii  php-horde-mime 2.11.2-2
ii  php-horde-nls  2.2.1-6
ii  php-horde-perms2.1.8-5
ii  php-horde-prefs2.9.0-9
ii  php-horde-role 1.0.1-17
ii  php-horde-rpc  2.1.9-2
ii  php-horde-serialize2.0.5-10
ii  php-horde-support  2.2.2-2
ii  php-horde-text-diff2.2.1-3
ii  php-horde-text-filter  2.3.7-1
ii  php-horde-token2.0.9-9
ii  php-horde-tree 2.0.5-6
ii  php-horde-url  2.2.6-9
ii  php-horde-util 2.5.12-2
ii  php-horde-vfs  2.4.2-1
ii  php-horde-view 2.0.6-10
ii  php8.2 [php]   8.2.7-1~deb12u1
ii  php8.2-cli [php-cli]   8.2.7-1~deb12u1

Versions of packages php-horde recommends:
ii  apache2 [httpd]2.4.57-2
ii  php-console-table  1.3.1-1
pn  php-file-find  
pn  php-file-fstab 
ii  php-horde-activesync   2.41.9-1
ii  php-horde-db   2.4.1-8
ii  php-horde-feed 2.0.4-9
ii  php-horde-oauth2.0.4-6
ii  php-horde-openxchange  1.0.1-6
ii  php-horde-service-facebook 2.0.10-6
ii  php-horde-service-twitter  2.1.6-6
ii  php-horde-service-weather  2.5.6-1
ii  php-horde-syncml   2.0.7-7
ii  php-net-dns2   1.5.0-1
ii  php-pear [php-console-getopt]  1:1.10.13+submodules+notgz+2022032202-2
pn  php-services-weather   

php-horde suggests no packages.

-- no debconf information


Bug#1068043: BinNMU 1.11-1+b1 depends on both, libmspack0 and libmspack0t64, and is hence uninstallable (at least on armhf)

2024-03-29 Thread Axel Beckert
Package: cabextract
Version: 1.11-1
Severity: serious
X-Debbugs-Cc: a...@debian.org

>From aptitude's dependency view on armhf:

iFA (pin --\ cabextract   0   72.7 kB  1.11-1  1.11-1+b1
  --\ Depends (3)
--- libc6 (>= 2.34)
--- libmspack0 (>= 0.9.1-1)
--- libmspack0t64 (>= 0.4) (UNSATISFIED)

As libmspack0t64 breaks libmspack0 they can't be installed together.

This is likely caused by hardcoding a dependency on libmspack0 in
debian/control:

https://sources.debian.org/src/cabextract/1.11-1/debian/control/#L10

-- System Information:
Debian Release: trixie/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (500, 'unstable-debug'), (500, 
'buildd-unstable'), (500, 'testing'), (110, 'experimental'), (1, 
'experimental-debug'), (1, 'buildd-experimental')
Architecture: armhf (armv7l)

Kernel: Linux 6.6.15-armmp-lpae (SMP w/4 CPU threads)
Kernel taint flags: TAINT_CRAP
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: sysvinit (via /sbin/init)
LSM: AppArmor: enabled

Versions of packages cabextract depends on:
ii  libc6   2.37-15.1
ii  libmspack0  0.11-1

cabextract recommends no packages.

cabextract suggests no packages.

-- no debconf information



Bug#1067534: Manual deps on lib* need updating for the time64 transition

2024-03-25 Thread Axel Beckert
Control: tag -1 + pending

Hi Andrey,

thanks for bringing this up.

Andrey Rakhmatullin wrote:
> All subpackages have manually specified deps like libqt5core5a, all of them
> need updating to lib*t64 ones.

I though disagree with the phrase "all subpackages". As far as I can
see there are solely two dependencies of only one binary package
(namely qutebrowser) affected: libqt5core5a and libqt5dbus5.

I neither see a package called libqt5webkit5t64 nor a package called.
libqt5webenginecore5t64.

    Regards, Axel
-- 
 ,''`.  |  Axel Beckert , https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE



Bug#1067600: unhtml: Seems not to use UTF-8

2024-03-24 Thread Axel Stammler
Package: unhtml
Version: 2.3.9-5
Severity: wishlist
X-Debbugs-Cc: a...@users.sourceforge.net

Dear Maintainer,

UTF-8 characters show up as '' instead of '°'. Maybe there could be an 
option to set
locale or character set.


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

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

Versions of packages unhtml depends on:
ii  libc6  2.36-9+deb12u4

unhtml recommends no packages.

unhtml suggests no packages.

-- debconf-show failed


Bug#1067110: xymon: Upgrade process hangs with zombie in postinst

2024-03-18 Thread Axel Beckert
Package: xymon
Severity: serious
Version: 4.3.30-2
Tags: pending

Due to a superfluous leftover debconf initialisation in xymon.postinst
not being removed with the cleaning up of old transition code, upgrading
xymon (but not xymon-client) resulted in a hanging upgrade process as
well as in a xymon.postinst zombie process.

A fix is committed locally and I'll upload soon, but it still needs some
more testing how to handle further, but more harmless leftovers from
that incomplete code removal.

Filing this bug mostly due to several transitions (well, mostly t64
transitions) being listed on https://tracker.debian.org/pkg/xymon to
make clear why an upload is currently necessary.

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

Kernel: Linux 6.6.13-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN
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: sysvinit (via /sbin/init)
LSM: AppArmor: enabled



Bug#1065435: [Aptitude-devel] Bug#1065435: aptitude: FTBFS on armhf and armel (probably -Werror=implicit-function-declaration related)

2024-03-16 Thread Axel Beckert
Hi Steinar and Christoph,

Steinar H. Gunderson wrote:
> struct timeval
> {
> #ifdef __USE_TIME_BITS64
>   __time64_t tv_sec;/* Seconds.  */
>   __suseconds64_t tv_usec;  /* Microseconds.  */
> #else 
>   __time_t tv_sec;  /* Seconds.  */
>   __suseconds_t tv_usec;/* Microseconds.  */
> #endif
> };
> #endif
> 
> But the fix is straightforward, no? Just change the offending test to 
> something like
> 
>   CPPUNIT_ASSERT_EQUAL(static_cast(99), c.tv_usec);
> 
> and it should work no matter what type c.tv_usec is. Or, if you prefer
> brace-initialization (which would prevent you from ever writing in a too-big
> value, like 999 or something):
> 
>   CPPUNIT_ASSERT_EQUAL(decltype(c.tv_usec){99}, c.tv_usec);
> 
> /* Steinar */

Thanks for the patch!

Christoph Biedl wrote:
> Therefore, any progress on this?

Not before the patch (hints) from Steinar. (Although there's also a
recent merge request mentioning some FTBFS fix, but it's unclear if
this issue is meant or something else. Will have to look into it,
too.)

> Do you need help?

I'm happy about any help with aptitude as we currently don't really
have any active upstream developer. C++ is not something that I'm
particularly good at.

> I didn't get very far at a first glance, aptitude's build
> dependencies are currently uninstallable, at least in arm{el,hf}.

I got my sid armhf Raspi fixed today (it stopped booting a while ago,
seemed to have been a usrmerge related issue), so I can now test
patches locally on armhf again.

Will try to get an upload done based on Steinar's patch instructions
soon-ish. But I first need to get the Raspi uptodate with the current
state of Sid.

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE



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

2024-03-06 Thread Axel Beckert
Hi Vincent,

Vincent Lefevre wrote:
> > 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.

That was already mentioned in the original bug report's footer, yes.
Otherwise I would have asked. :-)

> > * 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.

Yes, I've checked that, too.

That's also why I mentioned them: These cases don't apply and hence
it's NOT one of the two common cases, where it's more obvious (albeit
not necessarily good) that this happens.

[I removed the additional details, but they might come in handy later,
so thanks!]

> > But in your case neither of that seems to be case. So it indeed might
> > be a bug in this case.
> 
> 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.

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

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE



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

2024-03-06 Thread Axel Beckert
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.

* 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.

But in your case neither of that seems to be case. So it indeed might
be a bug in this case.

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE



Bug#1065435: aptitude: FTBFS on armhf and armel (probably -Werror=implicit-function-declaration related)

2024-03-04 Thread Axel Beckert
Source: aptitude
Version: 0.8.13-5
Severity: serious
Tags: ftbfs
X-Debbugs-Cc: a...@debian.org, z...@debian.org

Citing from https://buildd.debian.org/status/package.php?p=aptitude:

BinNMU changelog for aptitude on amd64, arm64, armel, armhf, i386, mips64el, 
ppc64el, riscv64, s390x, alpha, hppa, hurd-i386, ia64, loong64, m68k, powerpc, 
ppc64, sh4, sparc64 and x32:

Rebuild for time_t

Tail of log for aptitude on armel:

/usr/include/cppunit/TestAssert.h:161:6: note: candidate: ‘template 
void CppUnit::assertEquals(const T&, const T&, SourceLine, const std::string&)’
  161 | void assertEquals( const T& expected,
  |  ^~~~
/usr/include/cppunit/TestAssert.h:161:6: note:   template argument 
deduction/substitution failed:
../../tests/test_misc.cc:187:5: note:   deduced conflicting types for parameter 
‘const T’ (‘long int’ and ‘__suseconds64_t’ {aka ‘long long int’})
  187 | CPPUNIT_ASSERT_EQUAL(static_cast(99), c.tv_usec);
  | ^
make[3]: *** [Makefile:869: test_misc.o] Error 1
make[3]: Leaving directory '/<>/build/tests'
make[2]: *** [Makefile:1169: check-am] Error 2
make[2]: Leaving directory '/<>/build/tests'
/bin/sh: 1: ./cppunit_test: not found
make[1]: *** [debian/rules:39: override_dh_auto_test-arch] Error 127
make[1]: Leaving directory '/<>'
make: *** [debian/rules:22: binary-arch] Error 2

Tail of log for aptitude on armhf:

/usr/include/cppunit/TestAssert.h:161:6: note: candidate: ‘template 
void CppUnit::assertEquals(const T&, const T&, SourceLine, const std::string&)’
  161 | void assertEquals( const T& expected,
  |  ^~~~
/usr/include/cppunit/TestAssert.h:161:6: note:   template argument 
deduction/substitution failed:
../../tests/test_misc.cc:187:5: note:   deduced conflicting types for parameter 
‘const T’ (‘long int’ and ‘__suseconds64_t’ {aka ‘long long int’})
  187 | CPPUNIT_ASSERT_EQUAL(static_cast(99), c.tv_usec);
  | ^
make[3]: *** [Makefile:869: test_misc.o] Error 1
make[3]: Leaving directory '/<>/build/tests'
make[2]: *** [Makefile:1169: check-am] Error 2
make[2]: Leaving directory '/<>/build/tests'
/bin/sh: 1: ./cppunit_test: not found
make[1]: *** [debian/rules:39: override_dh_auto_test-arch] Error 127
make[1]: Leaving directory '/<>'
make: *** [debian/rules:22: binary-arch] Error 2

Given the time and the architectures failing, this is probably related
to dpkg switching on -Werror=implicit-function-declaration on these
architectures (see https://bugs.debian.org/1065371 and a good summary
of a similar case in https://bugs.debian.org/1065431 against lintian).

-- Package-specific info:
Terminal: xterm-256color
$DISPLAY is set.
which aptitude: /usr/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 (0x7ffc0a3eb000)
libgtk3-nocsd.so.0 => /lib/x86_64-linux-gnu/libgtk3-nocsd.so.0 
(0x7f8fca645000)
libapt-pkg.so.6.0 => /lib/x86_64-linux-gnu/libapt-pkg.so.6.0 
(0x7f8fc9e0)
libncursesw.so.6 => /lib/x86_64-linux-gnu/libncursesw.so.6 
(0x7f8fca1c6000)
libtinfo.so.6 => /lib/x86_64-linux-gnu/libtinfo.so.6 
(0x7f8fca191000)
libsigc-2.0.so.0 => /lib/x86_64-linux-gnu/libsigc-2.0.so.0 
(0x7f8fca188000)
libcwidget.so.4 => /lib/x86_64-linux-gnu/libcwidget.so.4 
(0x7f8fca084000)
libsqlite3.so.0 => /lib/x86_64-linux-gnu/libsqlite3.so.0 
(0x7f8fc9c8a000)
libboost_iostreams.so.1.83.0 => 
/lib/x86_64-linux-gnu/libboost_iostreams.so.1.83.0 (0x7f8fca06a000)
libxapian.so.30 => /lib/x86_64-linux-gnu/libxapian.so.30 
(0x7f8fc9a0)
libstdc++.so.6 => /lib/x86_64-linux-gnu/libstdc++.so.6 
(0x7f8fc960)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7f8fc9921000)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 
(0x7f8fca03b000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f8fc941e000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7f8fc9c85000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 
(0x7f8fc9c8)
libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x7f8fc9c61000)
libbz2.so.1.0 => /lib/x86_64-linux-gnu/libbz2.so.1.0 
(0x7f8fc990e000)
liblzma.so.5 => /lib/x86_64-linux-gnu/liblzma.so.5 (0x7f8fc98d1000)
liblz4.so.1 => /lib/x86_64-linux-gnu/liblz4.so.1 (0x7f8fc98ab000)
libzstd.so.1 => /lib/x86_64-linux-gnu/libzstd.so.1 (0x7f8fc935d000)
libudev.so.1 => /lib/x86_64-linux-gnu/libudev.so.1 (0x7f8fc9878000)
libsystemd.so.0 => /lib/x86_64-linux-gnu/libsystemd.so.0 
(0x7f8fc927b000)
libgcrypt.so.20 => /lib/x86_64-linux-gnu/libgcrypt.so.2

Bug#1063721: spip: has stopped working, complains about PHP version being ‘too recent’

2024-02-11 Thread Axel
Package: spip
Version: 4.1.9+dfsg-1+deb12u4
Severity: important
X-Debbugs-Cc: a...@users.sourceforge.net

Dear Maintainer,

after the upgrade, I could not log in to my site anymore. After making a backup 
of my
files, I first tried reinstalling, then purging + installing. a2ensite and 
spip_add_site
do not complain but …/ecrire shows:

“This installation will probably fail, or damage your site. PHP version 8.2.7 
too recent (maximum = 8.1.99)”

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

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

Versions of packages spip depends on:
ii  fonts-dustin20030517-14
ii  libjs-jquery3.6.1+dfsg+~3.5.14-1
ii  libjs-jquery-form   12-4
ii  libjs-jquery-jstree 3.3.12+dfsg1-2
ii  libjs-mediaelement  2.15.1+dfsg-3
ii  libjs-prefix-free   1.0.10+repack-5
ii  libjs-twitter-bootstrap-datepicker  1.3.1+dfsg1-4.1
ii  node-js-cookie  3.0.1+~3.0.0-3
ii  php-common  2:93
ii  php-getid3  1.9.22+dfsg-1
ii  php-mysql   2:8.2+93
ii  php-pgsql   2:8.2+93
ii  php-sqlite3 2:8.2+93
ii  php-xml 2:8.2+93
ii  php8.2-pgsql [php-pgsql]8.2.7-1~deb12u1
ii  php8.2-sqlite3 [php-sqlite3]8.2.7-1~deb12u1
ii  php8.2-xml [php-xml]8.2.7-1~deb12u1

Versions of packages spip recommends:
ii  apache2 [httpd]2.4.57-2
ii  default-mysql-server   1.1.0
ii  imagemagick8:6.9.11.60+dfsg-1.6
ii  imagemagick-6.q16 [imagemagick]8:6.9.11.60+dfsg-1.6
ii  mariadb-server [virtual-mysql-server]  1:10.11.6-0+deb12u1
ii  netpbm 2:11.01.00-2
ii  php-sqlite32:8.2+93
ii  php8.2-sqlite3 [php-sqlite3]   8.2.7-1~deb12u1
ii  postgresql 15+248

spip suggests no packages.

-- debconf information:
  spip/webserver: apache2


Bug#1012289: RFH: lintian -- Debian package checker

2024-02-05 Thread Axel Beckert
Hi Bill,

Bill Allombert wrote:
> By the way, what happened to lintian.debian.org ?

Seems as if someone (not me, just noticed it today when
"private/refresh-data" failed…) pulled the plug on at least the DNS
name. Probably because it hasn't been updated since Felix' try to
rewrite it, which AFAIK was never finished, but the old thing also no
more worked. (There's probably a lot of legacy code in
"lib/Lintian/Output" related to one of these two website generations,
maybe even both.)

IMHO it's generally a good thing, except that it would have been
better to redirect it to the according UDD pages instead.

    Regards, Axel
-- 
 ,''`.  |  Axel Beckert , https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE



Bug#1012289: RFH: lintian -- Debian package checker

2024-02-04 Thread Axel Beckert
Hi,

Bastien Roucariès wrote:
> Le dimanche 4 février 2024, 14:02:58 UTC Bill Allombert a écrit :
> > Areyou still available as lintian maintainer ? It sure would need an upload.
> I can
> 
> I am doing some pull request update

By coincidence I started to work on Lintian today (well, actually
yesterday) again, too, but saw these two mails only afterwards. Mostly
fixed the systemd/udev/usrmerge related test suite failures as well as
merged some of the open merge requests.

Let's try together to get a release done soon.

    Regards, Axel
-- 
 ,''`.  |  Axel Beckert , https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE



Bug#1062776: mpv: Please include option to exit with non-zero code on eof on streams

2024-02-03 Thread Axel Stammler
Package: mpv
Version: 0.35.1-4
Severity: wishlist
X-Debbugs-Cc: a...@users.sourceforge.net

Dear Maintainer,

on radio streams or other streams that have no proper end-of-file, MPV 
sometimes reports
end-of-file and closes down on errors. I would like to distinguish these 
instances from
user-requested terminations (done by pressing ‘q’, for instance) using an 
option to make MPV
exit with a non-zero return code on end-of-file.


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

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

Versions of packages mpv depends on:
ii  libarchive13  3.6.2-1
ii  libasound21.2.8-1+b1
ii  libass9   1:0.17.1-1
ii  libavcodec59  7:5.1.4-0+deb12u1
ii  libavdevice59 7:5.1.4-0+deb12u1
ii  libavfilter8  7:5.1.4-0+deb12u1
ii  libavformat59 7:5.1.4-0+deb12u1
ii  libavutil57   7:5.1.4-0+deb12u1
ii  libbluray21:1.3.4-1
ii  libc6 2.36-9+deb12u4
ii  libcaca0  0.99.beta20-3
ii  libcdio-cdda2 10.2+2.0.1-1
ii  libcdio-paranoia2 10.2+2.0.1-1
ii  libcdio19 2.1.0-4
ii  libdrm2   2.4.114-1+b1
ii  libdvdnav46.1.1-1
ii  libegl1   1.6.0-1
ii  libgbm1   22.3.6-1+deb12u1
ii  libjack-jackd2-0 [libjack-0.125]  1.9.21~dfsg-3
ii  libjpeg62-turbo   1:2.1.5-2
ii  liblcms2-22.14-2
ii  liblua5.2-0   5.2.4-3
ii  libmujs2  1.3.2-1
ii  libpipewire-0.3-0 0.3.65-3
ii  libplacebo208 4.208.0-3
ii  libpulse0 16.1+dfsg1-2+b1
ii  librubberband23.1.2+dfsg0-1
ii  libsdl2-2.0-0 2.26.5+dfsg-1
ii  libsixel1 1.10.3-3
ii  libswresample47:5.1.4-0+deb12u1
ii  libswscale6   7:5.1.4-0+deb12u1
ii  libuchardet0  0.0.7-1
ii  libva-drm22.17.0-1
ii  libva-wayland22.17.0-1
ii  libva-x11-2   2.17.0-1
ii  libva22.17.0-1
ii  libvdpau1 1.5-2
ii  libvulkan11.3.239.0-1
ii  libwayland-client01.21.0-1
ii  libwayland-cursor01.21.0-1
ii  libwayland-egl1   1.21.0-1
ii  libx11-6  2:1.8.4-2+deb12u2
ii  libxext6  2:1.3.4-1+b1
ii  libxinerama1  2:1.1.4-3
ii  libxkbcommon0 1.5.0-1
ii  libxpresent1  1.0.0-2+b10
ii  libxrandr22:1.5.2-2+b1
ii  libxss1   1:1.2.3-1
ii  libxv12:1.0.11-1.1
ii  libzimg2  3.0.4+ds1-1
ii  zlib1g1:1.2.13.dfsg-1

Versions of packages mpv recommends:
ii  xdg-utils  1.1.3-4.1
ii  yt-dlp 2023.03.04-1

Versions of packages mpv suggests:
pn  libcuda1  

-- debconf-show failed


Bug#743650: looks like a terminal config problem to me

2024-01-29 Thread Axel Scheepers
Hi,

On Tue, 22 Nov 2016 10:50:23 +0100 Adam Borowski  wrote:
> It's not a text program's duty to choose the exact shades, it's the terminal
> that's supposed to provide something readable.  And for the 16 basic colors,
> all of them are supposed to be readable against the default background.
...
> If you want them to be readable against white, you need to adjust them -- or
> preferably, have the terminal provide reasonable defaults if you choose a
> reversed color scheme.

I think the proper way to have 16 color support is to use the
'background' colors for output but in bold, so the darker version. On
terminals with a black background there should be a setting to have
these bold colors shown as the bright variants. This way the color is
supported on both backgrounds and one can still use a back and
foreground combination from the darker and brighter colors for e.g.
status bars etc.

Kind regards,
Axel



Bug#1010806: apt: Avoid color output on monochrome terminals

2024-01-29 Thread Axel Scheepers
Using 'ncolors' for both function and variable isn't really nice but
as is the function will exit when you use it with an unknown terminal
which might not be ok. Maybe using the following would be better;

#include 
#include 

int
ncolors(void)
{
int err, n = -1;

if (setupterm(NULL, 1, &err) == OK) {
n = tigetnum("colors");
del_curterm(cur_term);
}

return n;
}

You should also link ncurses (which brings in a bit of cruft).
Kind regards,
Axel

On Mon, Jan 29, 2024 at 1:53 PM Axel Scheepers
 wrote:
>
> 1010...@bugs.debian.org
>
> On Thu, 26 May 2022 11:03:25 +0200 Axel Scheepers
>  wrote:
> > Or the other way around as I proposed. The entire problem of knowing what
> > and how to use color goes away when curses is used. Would you accept a
> > patch for using that instead?
>
> I've forgot about this but how about the following?
>
> #include 
> #include 
>
> int
> ncolors(void)
> {
> int ncolors = -1;
>
> if (setupterm(NULL, 1, NULL) == OK) {
> ncolors = tigetnum("colors");
> del_curterm(cur_term);
> }
>
> return ncolors;
> }
>
> This doesn't initialise the terminal so you can still do the
> progressbar without clearing the screen and/or use hardcoded ansi
> codes for colors if you want. It returns the number of colors for the
> used terminal or -1 if color is not supported. Maybe the progressbar
> should be optional in that case too. I think it would be a nice
> addition and one doesn't have to use apt-get  and/or apt-cache
> instead.
> Also, maybe using italics, bold and reverse video instead of colors
> can be considered? They usually do the right thing with either
> background. Anyway, I hope you can implement the above function to
> make at least monochrome and/or dumb terminals behave.
>
> Kind regards,
> Axel



Bug#1010806: apt: Avoid color output on monochrome terminals

2024-01-29 Thread Axel Scheepers
1010...@bugs.debian.org

On Thu, 26 May 2022 11:03:25 +0200 Axel Scheepers
 wrote:
> Or the other way around as I proposed. The entire problem of knowing what
> and how to use color goes away when curses is used. Would you accept a
> patch for using that instead?

I've forgot about this but how about the following?

#include 
#include 

int
ncolors(void)
{
int ncolors = -1;

if (setupterm(NULL, 1, NULL) == OK) {
ncolors = tigetnum("colors");
del_curterm(cur_term);
}

return ncolors;
}

This doesn't initialise the terminal so you can still do the
progressbar without clearing the screen and/or use hardcoded ansi
codes for colors if you want. It returns the number of colors for the
used terminal or -1 if color is not supported. Maybe the progressbar
should be optional in that case too. I think it would be a nice
addition and one doesn't have to use apt-get  and/or apt-cache
instead.
Also, maybe using italics, bold and reverse video instead of colors
can be considered? They usually do the right thing with either
background. Anyway, I hope you can implement the above function to
make at least monochrome and/or dumb terminals behave.

Kind regards,
Axel



Bug#1059807: supysonic: crashes trying to access files whose path contains UTF-8 characters

2024-01-16 Thread Axel
Package: supysonic
Version: 0.7.2+ds-2
Followup-For: Bug #1059807
X-Debbugs-Cc: a...@users.sourceforge.net

Dear Maintainer,

some files stream, others do not. In some cases,  contains:

uncaught Mutagen exception in loadfile: 'ascii' codec can't encode character 
'\\u2014' in position 108: ordinal not in range(128)


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

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

Versions of packages supysonic depends on:
ii  fonts-glyphicons-halflings  1.009~3.4.1+dfsg-3
ii  libjs-bootstrap 3.4.1+dfsg-3
ii  libjs-jquery3.6.1+dfsg+~3.5.14-1
ii  libjs-sphinxdoc 5.3.0-4
ii  python3 3.11.2-1+b1
ii  python3-click   8.1.3-2
ii  python3-flask   2.2.2-3
ii  python3-lxml4.9.2-1+b1
ii  python3-mediafile   0.11.0-1
ii  python3-pil 9.4.0-1.1+b1
ii  python3-pony0.7.16+ds-3
ii  python3-requests2.28.1+dfsg-1
ii  python3-watchdog2.2.1-1
ii  python3-zipstream-ng1.4.0-1

Versions of packages supysonic recommends:
ii  flac 1.4.2+ds-2
ii  lame 3.100-6
ii  libapache2-mod-wsgi-py3  4.9.4-1+b2

Versions of packages supysonic suggests:
ii  python3-psycopg2  2.9.5-1+b1

-- no debconf information



Bug#1060831: steam: unmet dependencies: libgl1-mesa-dri:i386 : Depends: libllvm17:i386

2024-01-15 Thread Axel Dürrbaum

Package: steam
Version: 1:1.0.0.78
Severity: normal

Dear Maintainer,

upgrade of Debian today led to the deinstallation of steam due to a missing
depency

libgl1-mesa-dri:i386 : Depends: libllvm17:i386

Thanks,
Axel


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

Kernel: Linux 6.6.9-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_US.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 steam depends on:
ii  steam-launcher  1:1.0.0.78

steam recommends no packages.

steam suggests no packages.

-- debconf information:
* steam/question: I AGREE
  steam/purge:
* steam/need-nvidia-i386:
* steam/license:BEGIN:VCARD
FN:Axel Dürrbaum
N:Dürrbaum;Axel;;;
ORG:Universität Kassel;FB 15 Maschinenbau / FG Mess- und Regelungstechnik
ADR;TYPE=work:;;Raum 1713,Mönchebergstrasse 7;Kassel;Hessen;34125;Deutschl
 and
EMAIL;TYPE=work;PREF=1:axel.duerrb...@mrt.uni-kassel.de
TITLE:Dipl-Ing.
TEL;TYPE=work:++49 561 804 3261
TEL;TYPE=fax:++49 561 804 2847
NOTE:PGP KeyID: 0x694BFDA0\n	PGP Fingerprint: 902B 49AA 4BEF 5DBB 0120 DC37
  3A99 6EBD 694B FDA0\n	
X-MOZILLA-HTML:FALSE
URL:http://www.uni-kassel.de/fb15/mrt/
ROLE:Labor-Ingenieur
TZ;VALUE=TEXT:Europe/Berlin
END:VCARD


Bug#1060288: locales: Please allow selection of C.UTF-8 when (re)configuring locales

2024-01-09 Thread Axel Scheepers
Hi,

On Tue, Jan 9, 2024 at 11:54 PM Aurelien Jarno  wrote:
> The problem is that you end-up with two C.UTF-8 locales on the system.
> The one generated and the one provided by libc6. Normally that should
> work fine, but there is no 100% guarantee that the C.UTF-8 working is
> working fine during a major upgrade, between the time libc6 and locales
> are unpacked.

Ah ok I understand, thanks for explaining.

> I have just implemented that in git, the current behaviour is a
> left-over from before the time C.UTF-8 existed.

Thanks!

Kind regards,
Axel Scheepers



Bug#1060288: locales: Please allow selection of C.UTF-8 when (re)configuring locales

2024-01-09 Thread Axel Scheepers
Hello,

On Tue, Jan 9, 2024 at 7:18 AM Aurelien Jarno  wrote:
> C.UTF-8 is not shown on purpose, because it doesn't need to be
> generated, it is always available on the system. What you want is
> probably to be able to select it as a default locale.

Ah yes indeed. I was confused because it's an entry in /etc/locale.gen
and uncommenting it and running dpkg-reconfigure locales showed it was
generating it. This is the first time I had to use C.UTF-8. Can you
elaborate on why it would be problematic to include it in the list?

> A better workaround is probably to select a random locale to be
> generated, then you should be able to select the C.UTF-8 locale as
> default.

Thanks, yes indeed that's better.
Kind regards,
Axel Scheepers



Bug#1060288: locales: Please allow selection of C.UTF-8 when (re)configuring locales

2024-01-08 Thread Axel Scheepers
Package: locales
Version: 2.36-9+deb12u3
Severity: wishlist
Tags: d-i l10n

Dear Maintainer,

It would be nice to have C.UTF-8 in the list which dpkg-reconfigure locales
shows; When installing a desktop I usually select the C locale since the
others don't really apply and I'm unable to use a different locale setting
for date and lang. This however breaks gnome since it requires a utf-8
locale and I'm unable to select C.UTF-8 at installation.
A workaround is to uncomment the C.UTF-8 locale in /etc/locale.gen
and run dpkg-reconfigure locales after installation.

Kind regards,
Axel Scheepers

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

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

Versions of packages locales depends on:
ii  debconf [debconf-2.0]  1.5.82
ii  libc-bin   2.36-9+deb12u3
ii  libc-l10n  2.36-9+deb12u3

locales recommends no packages.

locales suggests no packages.

-- debconf information:
* locales/locales_to_be_generated: C.UTF-8 UTF-8
* locales/default_environment_locale: C.UTF-8



Bug#1059807: supysonic: does not write log file

2024-01-01 Thread Axel
Package: supysonic
Version: 0.7.2+ds-2
Severity: normal
X-Debbugs-Cc: a...@users.sourceforge.net

Dear Maintainer,

some audio files cause the script to die prematurely, probably while attempting 
to
transcode the audio. Unfortunately no log entries are created whatsoever. If 
the log file
cannot be created, an error message is produced, but even the debug setting 
does not
result in any entries.

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

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

Versions of packages supysonic depends on:
ii  fonts-glyphicons-halflings  1.009~3.4.1+dfsg-3
ii  libjs-bootstrap 3.4.1+dfsg-3
ii  libjs-jquery3.6.1+dfsg+~3.5.14-1
ii  libjs-sphinxdoc 5.3.0-4
ii  python3 3.11.2-1+b1
ii  python3-click   8.1.3-2
ii  python3-flask   2.2.2-3
ii  python3-lxml4.9.2-1+b1
ii  python3-mediafile   0.11.0-1
ii  python3-pil 9.4.0-1.1+b1
ii  python3-pony0.7.16+ds-3
ii  python3-requests2.28.1+dfsg-1
ii  python3-watchdog2.2.1-1
ii  python3-zipstream-ng1.4.0-1

Versions of packages supysonic recommends:
ii  flac 1.4.2+ds-2
ii  lame 3.100-6
ii  libapache2-mod-wsgi-py3  4.9.4-1+b2

Versions of packages supysonic suggests:
ii  python3-psycopg2  2.9.5-1+b1

-- no debconf information



Bug#1000044: ccze: depends on obsolete pcre3 library

2023-12-24 Thread Axel Beckert
Control: tag -1 + pending

Hi Yavor,

sorry for the late reply, but I only managed to continue on this now
as I'm on holidays now.

Yavor Doganov wrote:
> Here it is -- no memory leaks and I could not obtain crash or abort
> with the logs I've tested.  Note that while my original patch
> introduced some leaks, it also fixes some in the original code.

Thanks again for these patches! They indeed work much better than
before this set of patches. I though got another crash on this line:

Dec 24 06:43:16 c6 kernel: net_ratelimit: 1 callbacks suppressed

I think I managed to fix it and will also upload, but I'd be happy for
a short review of yours:

Backtrace is as follows:

Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by `ccze -A'.
Program terminated with signal SIGABRT, Aborted.
#0  __pthread_kill_implementation (threadid=, 
signo=signo@entry=6, no_tid=no_tid@entry=0) at ./nptl/pthread_kill.c:44
44  ./nptl/pthread_kill.c: No such file or directory.
(gdb) bt
#0  __pthread_kill_implementation (threadid=, 
signo=signo@entry=6, no_tid=no_tid@entry=0) at ./nptl/pthread_kill.c:44
#1  0x7fe6a065715f in __pthread_kill_internal (signo=6, threadid=) at ./nptl/pthread_kill.c:78
#2  0x7fe6a0609472 in __GI_raise (sig=sig@entry=6) at 
../sysdeps/posix/raise.c:26
#3  0x7fe6a05f34b2 in __GI_abort () at ./stdlib/abort.c:79
#4  0x7fe6a05f41ed in __libc_message (fmt=fmt@entry=0x7fe6a076678c "%s\n") 
at ../sysdeps/posix/libc_fatal.c:150
#5  0x7fe6a0660a75 in malloc_printerr (str=str@entry=0x7fe6a076422c 
"free(): invalid pointer") at ./malloc/malloc.c:5658
#6  0x7fe6a06627f4 in _int_free (av=, p=, 
have_lock=have_lock@entry=0) at ./malloc/malloc.c:4432
#7  0x7fe6a066516f in __GI___libc_free (mem=) at 
./malloc/malloc.c:3367
#8  0x7fe6a05b6467 in ccze_syslog_process (offsets=0x558834ff3170) at 
./src/mod_syslog.c:97
#9  ccze_syslog_handle (str=, length=, 
rest=0x7fffc99b28c8) at ./src/mod_syslog.c:134
#10 0x558833642a2f in ccze_plugin_run 
(pluginset=pluginset@entry=0x558834fefd30, 
subject=subject@entry=0x558834fe59c0 "Dec 24 06:43:16 c6 kernel: 
net_ratelimit: 1 callbacks suppressed", subjlen=64, 
rest=rest@entry=0x7fffc99b28c8, 
type=type@entry=CCZE_PLUGIN_TYPE_FULL, 
handled=handled@entry=0x7fffc99b28a4, status=0x7fffc99b28a8) at 
./src/ccze-plugin.c:327
#11 0x558833640616 in ccze_main () at ./src/ccze.c:706
#12 main (argc=, argv=) at ./src/ccze.c:756

Commenting out the "free (process);" in line 97 of src/mod_syslog.c
via the pcre2.patch seems to have fixed that:
https://salsa.debian.org/debian/ccze/-/commit/11b90155a6559e2121836483c2acacf35d8fca3b

Do you think that change would have any other impact? At least no more
crashes, so I'll upload anyway. But if you find some drawbacks, please
tell me.

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE



Bug#999921: xymon: depends on obsolete pcre3 library

2023-12-21 Thread Axel Beckert
Hi Yavor,

Yavor Doganov wrote:
> Please find a patch which I've been testing for a while with no ill
> effects AFAICT.  However, I'm not familiar at all with this package so
> it's possible that I've missed something.  I also couldn't test all
> available functionality.

Thanks a lot also for that patch! I have enough servers and clients
around to test the patch. (And thanks in general that you seemingly
crawl through all these annoying PCRE3→2 bugs and provide patches.
Much appreciated!)

Upstream said, they're having it on their roadmap, too, but I haven't
seen anything in that direction yet in the upstream SVN repo. (And I'm
tracking trunk.)

So I'll also forward the patch there, maybe first notify them, then
test it and then forward it.

> Unfortunately the patch does not apply cleanly to the latest upstream
> release (4.4-alpha) but I am ready and willing to rebase it, whenever
> you decide to package it.  Just let me know.

Also on my todo list, but that's first planned for experimental, not
yet unstable.

So I wouldn't say no to a rebased patch set for 4.4alpha as that's
where upstream is currently working on.

Will likely work on these (and ccze) over the holidays.

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE



Bug#1058942: gawk: Inconsistent parsing of "\|\|" and "||" (two pipes) in -F option

2023-12-18 Thread Axel Beckert
Package: gawk
Version: 1:5.2.1-2 1:5.1.0-1

Hi,

I initially ran into this issue on Debian 11 Bullseye, but I can also
reproduce it in Debian Unstable as of now:

We do have logs which separate fields with "||", i.e. two pipe
characters. (Yeah, likely not ideal, but that's given. :-)

With mawk I can parse them easily:

  $ echo 'a||b' | mawk -F'\|\|' '{print $1"X"$2}'
  aXb

(backslashes because multicharacter $FS is considered to be a regular
expression and hence the special character pipe needs to be
escaped. mawk also argues otherwise — IMHO correctly.)

gawk though behaves strange and especially inconsistently:

  $ echo 'a||b' | gawk -F'\|\|' '{print $1"X"$2}'
  gawk: warning: escape sequence `\|' treated as plain `|'
  a||bX

Ok, so '\|' should be written as just '|'? Unexpected, but ok. Let's do
that:

  $ echo 'a||b' | gawk -F'||' '{print $1"X"$2}'
  a||bX

No more argues, but the output is as wrong as before. It's also not that
it treated the pipe as regular expression (in which case it would
probably match any empty string twice and should probably output
something like "a|").

I though would have kinda expected that "||" is considered to be a
regular expression and hence would require the backslash.

Using e.g.

  $ echo 'a||b' | gawk 'FS="\|\|" {print $1"X"$2}'
  gawk: cmd. line:1: warning: escape sequence `\|' treated as plain `|'
  a||bX

seems to make no difference.

What does work as expected with gawk (and mawk) is though this:

  $ echo 'a||b' | gawk -F'[|][|]' '{print $1"X"$2}'
  aXb

Interestingly, if only a single pipe character is used as delimited it
works as expected again:

  $ echo 'a|b' | gawk -F'\|' '{print $1"X"$2}'
  gawk: warning: escape sequence `\|' treated as plain `|'
  aXb
  $ echo 'a|b' | gawk -F'|' '{print $1"X"$2}'
  aXb

So the bug seems to only appear if at least two pipes are used as
delimiter. (It behaves the same way with three pipes as with two pipes.)

Part of the bug or a separate bug might be that it argues even in the
two character version (hence expected to be a regexp) about "\|" being
interpreted as plain "|" which from my point of view is only correct in
the one-letter (plus espaping) variant '\|', but not for '\|\|'.

Counter examples:

  $ echo 'afbgc' | awk -F 'f|g' '{print $1, $2, $3}'
  a b c
  $ echo 'afbgc' | awk -F 'f\|g' '{print $1, $2, $3}'
  awk: warning: escape sequence `\|' treated as plain `|'
  a b c
  $ echo 'af|gc' | awk -F 'f\|g' '{print $1, $2}'
  awk: warning: escape sequence `\|' treated as plain `|'
  a |

In the last example it IMHO should not have replaced the "\|" with just
a "|" which is also not "plain" but a special character which was meant
to be escaped. The wanted output was "a c".

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

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

Versions of packages gawk depends on:
ii  libc6 2.37-13
ii  libgmp10  2:6.3.0+dfsg-2
ii  libmpfr6  4.2.1-1
ii  libreadline8  8.2-3
ii  libsigsegv2   2.14-1

gawk recommends no packages.

Versions of packages gawk suggests:
pn  gawk-doc  

-- no debconf information



Bug#1057688: [Aptitude-devel] Bug#1057688: aptitude: Stray input on window click when running under tmux

2023-12-07 Thread Axel Beckert
Hi Sven,

Sven Joachim via Aptitude-devel wrote:
> Debian ncurses maintainer here, bringing the ncurses upstream developer
> into the loop.

Thanks for that!

> In addition to aptitude, mouse support is also broken in dialog(1) under
> tmux.
>
> > Maybe this bug should instead be assigned to ncurses?
> 
> Probably should be reassigned to ncurses-base, but let's first see what
> Thomas has to say about it.

JFTR: If it turns out as a bug which indeed needs not (only) to be
fixed in ncurses, it's likely not in aptitude but in libcwidget4. (The
separation stems from times where aptitude still also had a GUI
frontend.)

P.S.: Thanks to Thomas for fixing the recent ncurses issues (htop,
etc.) so quickly at upstream!

    Regards, Axel
-- 
 ,''`.  |  Axel Beckert , https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE



Bug#1057417: systemd tmpfiles seems to delete lost+found again

2023-12-05 Thread Axel Scheepers
Yes you are right, I overlooked the existing exception, it is indeed
probably the setup which causes it. I had rebooted the box previously and
tested only the clearing service.

Kind regards,
Axel

Op di 5 dec. 2023 00:38 schreef Michael Biebl :

> Am 04.12.23 um 23:09 schrieb Michael Biebl:
> > The code to exclude lost+found appears to be still there:
> >
> https://github.com/systemd/systemd/blob/main/src/tmpfiles/tmpfiles.c#L720
> >
> > Can you create a lost+found directory and then run
> > SYSTEMD_LOG_LEVEL=debug systemd-tmpfiles --prefix /tmp
> >
> > ?
>
> I haven't really debugged this fully, but from a cursory glance it
> appears that systemd-tmpfiles-setup.service is responsible for nuking
> /tmp/lost+found
>
> systemd-tmpfiles --create --remove --boot --exclude-prefix=/dev
> doesn't preserve /tmp/lost+found which looks like a regression.
>


Bug#1057417: systemd tmpfiles seems to delete lost+found again

2023-12-04 Thread Axel Scheepers
On Mon, Dec 4, 2023 at 8:27 PM Luca Boccassi  wrote:
> But the main point is, it's fine if you do a custom local setup with
> the appropriate local configuration, but then you also need to add the
> appropriate config for tmpfiles.d. You can either mask or replace
> tmp.conf, simply add your own file as /etc/tmpfiles.d/tmp.conf and it
> will have priority, and do what you need for your custom local setup.

Oh, ok. I admit I have a traditional unix background where it's common
practice to have these a separate real partitions instead. I'll just keep
the exception I already made then. I have some users on the system
which sometimes store larger things in there.

Thanks,
Kind regards,

Axel



Bug#1057417: systemd tmpfiles seems to delete lost+found again

2023-12-04 Thread Axel Scheepers
On Mon, Dec 4, 2023 at 6:58 PM Luca Boccassi  wrote:
> You have a separate, non-tmpfs filesystem on /tmp? How did you end up
> with such a setup?

Hi Luca,

I always configure separate /var, /tmp and /home filesystems. In this case
the system is also low on ram so tmpfs is not really an option (I think?).
Is using tmpfs the preferred way to handle this on debian? Or maybe ext4
as a filesystem is not preferred in this case?

Kind regards,
Axel



Bug#1057417: systemd tmpfiles seems to delete lost+found again

2023-12-04 Thread Axel Scheepers
Package: systemd
Version: 252.17-1~deb12u1
Severity: normal
Tags: patch

Dear Maintainer,

   * What led up to the situation?

(previous bug at #788193).

Automatic run of e2scrub reported:

So sorry, the automatic e2scrub of /tmp on mahogany.vultrusercontent.com failed.

A log of what happened follows:
× e2scrub@-tmp.service - Online ext4 Metadata Check for /tmp
 Loaded: loaded (/lib/systemd/system/e2scrub@.service; static)
 Active: failed (Result: exit-code) since Sun 2023-12-03 03:11:03
CET; 137ms ago
   Docs: man:e2scrub(8)
Process: 25375 ExecStart=/sbin/e2scrub -t /tmp (code=exited,
status=1/FAILURE)
   Main PID: 25375 (code=exited, status=1/FAILURE)
CPU: 227ms

Dec 03 03:11:00 mahogany systemd[1]: Starting e2scrub@-tmp.service -
Online ext4 Metadata Check for /tmp...
Dec 03 03:11:01 mahogany e2scrub@-tmp[25387]:   Logical volume
"tmp.e2scrub" created.
Dec 03 03:11:01 mahogany e2scrub@-tmp[25415]: e2fsck 1.47.0 (5-Feb-2023)
Dec 03 03:11:01 mahogany e2scrub@-tmp[25415]: Pass 1: Checking inodes,
blocks, and sizes
Dec 03 03:11:01 mahogany e2scrub@-tmp[25415]: Pass 2: Checking
directory structure
Dec 03 03:11:01 mahogany e2scrub@-tmp[25415]: Pass 3: Checking
directory connectivity
Dec 03 03:11:01 mahogany e2scrub@-tmp[25415]: /lost+found not found.
Create? yes
Dec 03 03:11:01 mahogany e2scrub@-tmp[25415]: Pass 4: Checking reference counts
Dec 03 03:11:01 mahogany e2scrub@-tmp[25415]: Pass 5: Checking group
summary information
Dec 03 03:11:01 mahogany e2scrub@-tmp[25415]: /dev/system/tmp.e2scrub:
* FILE SYSTEM WAS MODIFIED *
Dec 03 03:11:01 mahogany e2scrub@-tmp[25415]: /dev/system/tmp.e2scrub:
21/124928 files (0.0% non-contiguous), 17515/499712 blocks
Dec 03 03:11:01 mahogany e2scrub@-tmp[25375]: /tmp: Scrub FAILED due
to corruption!  Unmount and run e2fsck -y.
Dec 03 03:11:01 mahogany e2scrub@-tmp[25420]: tune2fs 1.47.0 (5-Feb-2023)
Dec 03 03:11:01 mahogany e2scrub@-tmp[25420]: Setting filesystem error
flag to force fsck.
Dec 03 03:11:01 mahogany e2scrub@-tmp[25422]:   Logical volume
"tmp.e2scrub" successfully removed.
Dec 03 03:11:03 mahogany systemd[1]: e2scrub@-tmp.service: Main
process exited, code=exited, status=1/FAILURE
Dec 03 03:11:03 mahogany systemd[1]: e2scrub@-tmp.service: Failed with
result 'exit-code'.
Dec 03 03:11:03 mahogany systemd[1]: Failed to start
e2scrub@-tmp.service - Online ext4 Metadata Check for /tmp.
Dec 03 03:11:03 mahogany systemd[1]: e2scrub@-tmp.service: Triggering
OnFailure= dependencies.


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

Ineffective: put /tmp on a separate filesystem, effective; add lost+found
to /usr/lib/tmpfiles.d;

 cat /usr/lib/tmpfiles.d/tmp-lost-and-found.conf 
x   /tmp/lost+found


I can't find an exeption in the source nor in /usr/lib/tmpfiles.d/*
root@mahogany:/tmp/src/systemd-252.17/src/tmpfiles# ed tmpfiles.c 
158825
/.journal
   ".journal",
-3,+3n
764 S_ISREG(sx.stx_mode) &&
765 sx.stx_uid == 0 &&
766 STR_IN_SET(de->d_name,
767".journal",
768"aquota.user",
769"aquota.group")) {
770 log_debug("Skipping \"%s\".", sub_path);

Maybe I'm missing something but if not can it be added to either
/usr/lib/tmpfiles.d or as a patch to tmpfiles.c?
I can confirm adding it to tmpfiles.d solves the problem for me.

Happy holidays, kind regards,

Axel

-- Package-specific info:

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

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

Versions of packages systemd depends on:
ii  libacl12.3.1-3
ii  libaudit1  1:3.0.9-1
ii  libblkid1  2.38.1-5+b1
ii  libc6  2.36-9+deb12u3
ii  libcap21:2.66-4
ii  libcryptsetup122:2.6.1-4~deb12u1
ii  libfdisk1  2.38.1-5+b1
ii  libgcrypt201.10.1-3
ii  libkmod2   30+20221128-1
ii  liblz4-1   1.9.4-1
ii  liblzma5   5.4.1-0.2
ii  libmount1  2.38.1-5+b1
ii  libp11-kit00.24.1-2
ii  libseccomp22.5.4-1+b3
ii  libselinux13.4-1+b6
ii  libssl33.0.11-1~deb12u2
ii  libsystemd-shared  252.17-1~deb12u1
ii  libsystemd0252.17-1~deb12u1
ii  libzstd1   1.5.4+dfsg2-5
ii  mount  2.38.1-5+b1

Versions of p

Bug#1000044: ccze: depends on obsolete pcre3 library

2023-12-03 Thread Axel Beckert
Control: tag -1 - pending

Hi Yavor,

Yavor Doganov wrote:
> Please find a patch attached (I was not able to test all plugins).

Thanks again for that huge patch. I've pushed it and several other
changes to Salsa.

A local test on my /var/log/syslog immediately ran into a segfault,
though, so I guess, that's one of the plugins you couldn't test.

Culprit is this line, actually the first line in my current /var/log/syslog:

  Dec  3 06:38:28 c6 syslog-ng[26651]: Configuration reload request received, 
reloading configuration;

Example for a minimal reproducer:

  $ echo 'Dec  3 06:38:28 c6 syslog-ng[26651]: Configuration reload request 
received, reloading configuration;' | ccze -A
  free(): invalid pointer
  [1]17679 done   echo  |
 17680 IOT instruction (core dumped)  ccze -A

A backtrace of the core dump gave the following output:

  #0  __pthread_kill_implementation (threadid=, 
signo=signo@entry=6, no_tid=no_tid@entry=0) at ./nptl/pthread_kill.c:44
  #1  0x77d1c15f in __pthread_kill_internal (signo=6, 
threadid=) at ./nptl/pthread_kill.c:78
  #2  0x77cce472 in __GI_raise (sig=sig@entry=6) at 
../sysdeps/posix/raise.c:26
  #3  0x77cb84b2 in __GI_abort () at ./stdlib/abort.c:79
  #4  0x77cb91ed in __libc_message (fmt=fmt@entry=0x77e2b78c 
"%s\n") at ../sysdeps/posix/libc_fatal.c:150
  #5  0x77d25a75 in malloc_printerr (str=str@entry=0x77e2922c 
"free(): invalid pointer") at ./malloc/malloc.c:5658
  #6  0x77d277f4 in _int_free (av=, p=, 
have_lock=have_lock@entry=0) at ./malloc/malloc.c:4432
  #7  0x77d2a16f in __GI___libc_free (mem=mem@entry=0x55566c08) at 
./malloc/malloc.c:3367
  #8  0x77c7b393 in ccze_syslog_process (offsets=0x5556e170) at 
./src/mod_syslog.c:63
  #9  ccze_syslog_handle (str=, length=, 
rest=0x7fffd9a8) at ./src/mod_syslog.c:126
  #10 0xaa1f in ccze_plugin_run 
(pluginset=pluginset@entry=0x5556ad30, subject=subject@entry=0x555609c0 
"Dec  3 06:38:28 c6 syslog-ng[26651]: Configuration reload request received, 
reloading configuration;", subjlen=100, rest=rest@entry=0x7fffd9a8, 
type=type@entry=CCZE_PLUGIN_TYPE_FULL, 
  handled=handled@entry=0x7fffd984, status=0x7fffd988) at 
./src/ccze-plugin.c:327
  #11 0x8696 in ccze_main () at ./src/ccze.c:706
  #12 main (argc=, argv=) at ./src/ccze.c:753

Seems to be the "free(process)" in line 63 of src/mod_syslog.c. But
neither commenting it out (which might have caused a memory leak) nor
replacing it with "pcre2_substring_free(process)" (as present
elsewhere shortly afterwards is this file) did fix the segfault. It
just started to look different, so the latter might be part of the
fix, but in that case it's is not the complete fix .

I currently assume that any line starting with a date and then a
process name with process id in brackets will trigger this as it's the
parsing of the process id inside the brackets where the crash happens.

So in case you have an idea how to fix this, I'd be happy.

(As mentioned elsewhere already, this migration is a huge PCRE
upstream mess and I'm glad about any help as this is not my only
package affected.)

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE



Bug#1034398: ccze: Project homepage on github no longer exists / abandoned upstream?

2023-12-03 Thread Axel Beckert
Control: tag -1 + pending

Hi Nika,

Michael Prokop wrote:
> https://github.com/madhouse/ccze throws a 404,

Yeah, I know. I think this was a reaction on Microsoft buying Github.

> maybe https://git.madhouse-project.org/archive/ccze
> is the proper place to refer to nowadays,

Thanks for that link! I knew it was on
https://git.madhouse-project.org/algernon/ccze before and then
suddenly vanished there, too, which was very weird …

> but it looks like the project was abandoned / is unmaintained from
> upstream?

… because when I took over the package from Gergely (upstream and
previous package maintainer), he promised me to still fix severe
issues like security issues. Completely removing the source code repo
did not fit into that statement. So it's just another case showing
that changing URLs for repos is a really bad idea. But I guess Forgejo
doesn't have a repo flag "archived" so Gergely helped himself that
way.

Wanted to contact him for the PCRE2 migration (and my motivation on
this was rather low as that whole PCRE2 "migration" was a real mess at
PCRE upstream), but Yavor was quicker with sending in a patch.

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE



Bug#1000044: ccze: depends on obsolete pcre3 library

2023-12-03 Thread Axel Beckert
Hi Yavor,

Yavor Doganov wrote:
> Please find a patch attached

Thanks a lot!

> (I was not able to test all plugins).

Better than nothing.

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE



Bug#1057044: xymon: ntpdate no longer supports the -p option

2023-11-28 Thread Axel Beckert
Hi Carsten,

Carsten Leonhardt wrote:
> ntpdate emits a warning when called with the -p option. I've attached a
> patch to drop that option from xymonserver.cfg.

Thanks. Sounds kinda familiar.

> If you prefer, I can also commit directly to salsa.

Fine for me, thanks!

> Subject: [PATCH] xymon: update xymonserver.cfg: ntpdate no longer
>  supports the "-p" option (cf. #926877).

Oh, #926877 was my bug report. Maybe that's why it sounds familiar.
%-)

    Regards, Axel
-- 
 ,''`.  |  Axel Beckert , https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE



Bug#1042845: libembperl-perl: FTBFS with Perl 5.38: test failures

2023-11-26 Thread Axel Beckert
Hi,

gregor herrmann wrote:
> On Tue, 01 Aug 2023 22:41:12 +0200, Axel Beckert wrote:
> > > I assume the diagnostics have changed again and it's just the tests that
> > > need adjusting, but I haven't checked properly.
> > Will look into it, but may take a while.
> 
> Now would be a good time :)

Yep. Got mail about the auto removal a week ago or so. (I'm subscribed
via rss2email to my Debian Maintainer Dashboard.)

> As the perl 5.38 transition is immanent, the bug's severity has been
> raised to serious; and bot dam and me failed to understand the test
> system so I guess this is now your turn :)

Upstream might have been faster this time than I am these days: 3.0.0
is out: https://metacpan.org/dist/Embperl

http://matrix.cpantesters.org/?dist=Embperl+3.0.0 doesn't look too
well for 5.38, though. I will see.

Most if not all our changes seem to have been merged according to the
changelog.

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE



Bug#1055463: sysvinit-core: Please entirely remove SysVinit

2023-11-06 Thread Axel Beckert
Hi,

Patrik Schindler wrote:
> After I've upgraded my server to Bookworm today, I'll now do a rollback from
> backup because of numerous issues with many services not coming up
> anymore.

Works fine for me, especially in Bookworm. Running servers as well as
workstations with it.

> For this reason, I propose to remove SysVinit completely from the next Debian
> release,

You are trolling us, right? The opposite is the proper implication
from what you've described.

Debian is about choice, not about spoon-feeding users and leaving them
without choice in many places like at least one well-known Debian
derivative does.

    Regards, Axel
-- 
 ,''`.  |  Axel Beckert , https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE



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

2023-10-16 Thread Axel Beckert
Package: apt-listchanges
Version: 4.2
Severity: normal

Hi Jonathan,

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

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

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

--- News for falkon ---

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

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

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

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

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

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

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

--- News for libdrm2 ---

libdrm (2.3.0-4) experimental; urgency=low

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

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

-- Package-specific info:
==> /etc/apt/listchanges.conf <==
[apt]
frontend=pager
email_address=root
confirm=0
save_seen=/var/lib/apt/listchanges
which=news
email_format=text
headers=true
reverse=false
capture_snapshots=auto
snapshot_dir=/var/lib/apt/listchanges-snapshots


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

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

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

apt-listchanges recommends no packages.

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

Bug#1035477: installation-reports: grub or kernel of D-I image hangs on Thinkpad X13s after "EFI stub: Exiting boot services..."

2023-10-11 Thread Axel Beckert
Hi Emanuele,

Emanuele Rocca wrote:
> On 2023-10-10 01:45, Axel Beckert wrote:
> > I tried that, installer ran through fine, grub boots from disk after
> > installation, kernel loads initramfs and then falls into the initramfs
> > prompt and fractions of a second later (sometimes even beforehand) the
> > whole screen goes black and then nothing helps then pressing the power
> > button for about 10 seconds.
> 
> This sounds like you might have missed the wiki step "Add qnoc-sc8280xp
> module to initramfs":
> https://wiki.debian.org/InstallingDebianOn/Thinkpad/X13s

I indeed missed that first, but fixed it via rescue mode of the
d-i image.

> OK then once you chroot into the installed system you should be able to
> check if qnoc-sc8280xp is in /etc/initramfs-tools/modules. If not,
> 
>  echo qnoc-sc8280xp >> /etc/initramfs-tools/modules

Was already in there.

> To triple-check that the needed module is in there:
> 
>  zstdcat /initrd.img | cpio -itv | grep qnoc-sc8280xp.ko

Was also already in there.

Additionally there are quite some messages about things being pending
due to waiting for something else from that kernel module seconds
before the screen blanks. Can send pictures I made of it, in case they
could be helpful.

And since you've mentioned /initrd.img instead of /boot/initrd.img (as
I have a single filesystem installation for now), I also added a
symlink at /initrd.img pointing to /boot/initrd.img. But it didn't
change anything either. (I later noticed that this likely was
unnecessary as GRUB also looks for kernel and initrd.img under /boot
and for a versioned file anyways.)

> In any case, the daily netinst image should now work!

Indeed. Had to use that to check the above today as the mini.iso no
more works due to the updated kernel in sid.

> There's no need to manually copy any firmware and similar
> shenanigans.

Well, still quite some shenanigans left for now.

> If you have the time, please follow the
> InstallingDebianOn/Thinkpad/X13s page again from the begingging to
> the end (quite a few things have changed) and let me know if that
> works for you.

Haven't done a reinstallation for now. (And I'm actually not that keen
on it currently, but I will have to do it at some point, because I
forgot to enable disk encryption. But I'd first like to understand
what's wrong as I seem to have followed all steps.)

Via d-i's rescue mode I have also updated the kernel to 6.5.0-2, but
the symptoms stay: Lots of "pending/waiting for" message by
qnoc-sc8280xp and then a dark, blank screen and nothing happens
anymore.

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE



Bug#1035477: installation-reports: grub or kernel of D-I image hangs on Thinkpad X13s after "EFI stub: Exiting boot services..."

2023-10-09 Thread Axel Beckert
Hi Emanuele,

Axel Beckert wrote:
> Emanuele Rocca wrote:
> > On 2023-05-04 11:53, Axel Beckert wrote:
> > > Sure. I intend to run Debian Unstable on it anyway
> > 
> > Now you can. :-)
> 
> Hmmm, I tried a few days ago (October 1st) with the image from
> https://cdimage.debian.org/cdimage/daily-builds/sid_d-i/current/arm64/iso-cd/
> and it hang with a message saying something about "generating empty
> device tree" or so.

And that image didn't contain the dtb files to copy while the mini.iso
from d-i.d.o did.

> > https://wiki.debian.org/InstallingDebianOn/Thinkpad/X13s
> 
> Ah, I see, there's much more than just the installer image needed.

I tried that, installer ran through fine, grub boots from disk after
installation, kernel loads initramfs and then falls into the initramfs
prompt and fractions of a second later (sometimes even beforehand) the
whole screen goes black and then nothing helps then pressing the power
button for about 10 seconds.

The same happens if I start the recovery mode from the grub menu when
booting from the disk.

arm64.nopauth is in there.

And I can easily install tons of packages when I boot from the
installer USB stick into the rescue mode and chroot into the
installation on disk.

Even installing the recommended packages did not change anything with
regards to the screen going black about 12 seconds after booting.

I also tried to disable any console font changes via

  dpkg-reconfigure -plow console-setup console-setup-linux

but to no avail.

Any ideas what could have gone wrong or how I can fix this? I feel I'm
_s_ close. :-)

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE



Bug#1053725: apt-listchanges: Shows NEWS for package tor from 2008

2023-10-09 Thread Axel Beckert
Hi Jonathan,

Jonathan Kamens wrote:
> OK, this will be fixed in 4.1.

Yay, thanks!

> Description of the bug and fix, copied from the commit message:
> 
> Bug:
> * Main package a has both changelog and NEWS.
> * Subpackage a-sub has identical changelog but no NEWS.
> * Both a and a-sub version 1 are installed but not in database.
> * apt goes to upgrade a and a-sub to version 2.
> * apt-listchanges parses a-sub first, records installed entries under
>   package a instead of a-sub, since we were using the package name in
>   the changelog entry to determine where in the seen DB to record
>   entries.

Ouch, that seemed rather non-trivial to figure out and reproduce.

> I added a unit test for this case which now passes, and all other unit tests
> continue to pass with the change described above.

Perfect!

> Note that the database is entirely replaced when upgraded from pre-4.0 to
> 4.x because its format and what we're storing in it are completely
> different.

Ok, wasn't sure how relevant its content is. Just tried to help. :-)

> ># EASY-INSTALL-ENTRY-SCRIPT: 
> > 'apt-listchanges==3.27','console_scripts','apt-listchanges'
> 
> Thanks, fixed this as well.

Great!

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE



Bug#1053725: apt-listchanges: Shows NEWS for package tor from 2008

2023-10-09 Thread Axel Beckert
Hi Jonathan.

Jonathan Kamens wrote:
> Not the same bug. #1053696 only applies to changelog entries, not NEWS
> entries, since the latter can't be downloaded via apt.

Good point. I'm glad that I filed my bug report despite Russ' bug report.

> I am thus far unable to reproduce this. Still investigating.

Anything I can help? This is a Sid installation running more or less
permanently (besides reboots :-) since May 2016. So the
apt-listchanges database might have seen a few packages. Then again,
it seems rather short for > 14'000 installed packages.

I've attached my /var/lib/apt/listchanges file. (State after having
shown that NEWS entry from 2008, though.)

BTW, while trying to figure out where that db could be I noticed that
despite 4.0 is installed according to "dpkg -l apt-listchanges", the
tool itself contains a different version number:

  ~ → head -2 /usr/bin/apt-listchanges
  #!/usr/bin/python3
  # EASY-INSTALL-ENTRY-SCRIPT: 
'apt-listchanges==3.27','console_scripts','apt-listchanges'

HTH!

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE


listchanges
Description: application/data


Bug#1053725: apt-listchanges: Shows NEWS for package tor from 2008

2023-10-09 Thread Axel Beckert
Package: apt-listchanges
Version: 4.0
Severity: normal

Hi,

after the upgrade to 4.0, apt-listchanges showed me this ancient NEWS
when upgrading tor from 0.4.8.6-1 to 0.4.8.7-1.

Reading changelogs... Done
apt-listchanges: News
-

--- News for tor ---

tor (0.2.0.26-rc-1) experimental; urgency=critical

  * weak cryptographic keys

It has been discovered that the random number generator in Debian's
openssl package is predictable.  This is caused by an incorrect
Debian-specific change to the openssl package (CVE-2008-0166).  As a
result, cryptographic key material may be guessable.

See Debian Security Advisory number 1571 (DSA-1571) for more information:
http://lists.debian.org/debian-security-announce/2008/msg00152.html

If you run a Tor server using this package please see
/var/lib/tor/keys/moved-away-by-tor-package/README.REALLY

 -- Peter Palfrader   Tue, 13 May 2008 12:49:05 +0200

(press q to quit)

(In this case it even was an especially embarassing topic for Debian...)

Might be related or the same as #1053696 by Russ (X-Debbugs-Cc'ed).


-- Package-specific info:
==> /etc/apt/listchanges.conf <==
[apt]
frontend=pager
email_address=root
confirm=0
save_seen=/var/lib/apt/listchanges
which=news
email_format=text
headers=true
reverse=false



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

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

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

apt-listchanges recommends no packages.

Versions of packages apt-listchanges suggests:
ii  alacritty [x-terminal-emulator]0.12.2-2+b1
ii  chromium [www-browser] 117.0.5938.149-1
ii  cool-retro-term [x-terminal-emulator]  1.2.0+ds2-1+b1
ii  dillo [www-browser]3.0.5-7+b1
ii  edbrowse [www-browser] 3.7.7-5
ii  elinks [www-browser]   0.16.1.1-4
ii  eterm [x-terminal-emulator]0.9.6-7.1
ii  falkon [www-browser]   23.08.1-1
ii  firefox [www-browser]  118.0-1+b1
ii  firefox-esr [www-browser]  115.3.0esr-1+b1
ii  gnome-console [x-terminal-emulator]45.0-1
ii  gnome-terminal [x-terminal-emulator]   3.50.0-1
ii  hv3 [www-browser]  3.0~fossil20110109-8
ii  kitty [x-terminal-emulator]0.26.5-5
ii  konqueror [www-browser]4:22.12.3-2
ii  konsole [x-terminal-emulator]  4:23.08.1-1
ii  lilyterm [x-terminal-emulator] 0.9.9.4+git20150208.f600c0-5+b1
ii  links [www-browser]2.29-1+b1
ii  links2 [www-browser]   2.29-1+b1
ii  luakit [www-browser]   1:2.3.3-1
ii  lxterminal [x-terminal-emulator]   0.4.0-2
ii  lynx [www-browser] 2.9.0dev.12-1
ii  midori [www-browser]   7.0-2.1+b1
ii  netrik [www-browser]   1.16.1-4
ii  netsurf [www-browser]  3.6-3.2
ii  netsurf-gtk [www-browser]  3.10-3.1
ii  postfix [mail-transport-agent] 3.8.2-1
ii  pterm [x-terminal-emulator]0.79-1
ii  python3-gi 3.46.0-1
ii  qterminal [x-terminal-emulator]1.3.0-1
ii  qutebrowser [www-browser]  2.5.4-1
ii  rxvt-unicode [x-terminal-emulator] 9.31-1
ii  sakura [x-terminal-emulator]   3.8.7-1
ii  stterm [x-terminal-emulator]   0.9-1
ii  surf [www-browser] 2.1+git20221016-5
ii  terminator [x-terminal-emulator]   2.1.3-1
ii  terminology [x-terminal-emulator]  1.13.0-2
ii  termit [x-terminal-emulator]   3.1-3
ii  tilix [x-terminal-emulator]1.9.5-2
ii  w3m [www-browser]  0.5.3+git20230121-2
ii  xfce4-terminal [x-terminal-emulator]   1.1.0-2
ii  xterm [x-terminal-emulator]385-1
ii  yakuake [x-terminal-emulator]  23.08.1-1
ii  zutty [x-terminal-emulator]0.14.6.20230701+dfsg1-2

-- debconf information:
* apt-listchanges/confirm: false
  apt-listchanges/no-network: false
* apt-listchanges/email-format: text
* apt-listchanges/email-address: root
* apt-listchanges/headers: true
* apt-listchanges/save-seen: true
* apt-listchanges/which: news
* apt-listchanges/reverse: false
* apt-listchanges/fronte

Bug#1035477: installation-reports: grub or kernel of D-I image hangs on Thinkpad X13s after "EFI stub: Exiting boot services..."

2023-10-06 Thread Axel Beckert
Hi Emanuele,

Emanuele Rocca wrote:
> On 2023-05-04 11:53, Axel Beckert wrote:
> > Sure. I intend to run Debian Unstable on it anyway
> 
> Now you can. :-)

Hmmm, I tried a few days ago (October 1st) with the image from
https://cdimage.debian.org/cdimage/daily-builds/sid_d-i/current/arm64/iso-cd/
and it hang with a message saying something about "generating empty
device tree" or so.

> https://wiki.debian.org/InstallingDebianOn/Thinkpad/X13s

Ah, I see, there's much more than just the installer image needed.
Thanks for that hint!

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE



Bug#1051673: deal.ii: uploader email address maybe invalid (Matthias Maier)

2023-09-11 Thread Axel Beckert
Hi Ansgar,

Ansgar wrote:
> On Mon, 2023-09-11 at 10:32 +0200, Ben Tris wrote:
> > The email address for uploader Matthias Maier is now
> >  this is not found in qa.
> 
> I don't understand what the problem here should be? The mail address
> should be valid.

I suspect an issue with https://qa.debian.org/developer.php having an
issue with e-mail addresses with capital letters and Ben
misinterpreting that as an issue with the package despite the issue is
somewhere else. All bugs he filed were about e-mail addresses with
capital letters.

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE



Bug#1051328: grub-common: wrong-path-for-interpreter /usr/bin/sh != /bin/sh [etc/grub.d/25_bli]

2023-09-06 Thread Axel Beckert
Hi Julian,

Julian Andres Klode wrote:
> > For some reason, possibly usrmerge-triggered, since 2.12~rc1-7
> > /etc/grub.d/25_bli sports the following non-standard shebang line:
> > 
> >   #!/usr/bin/sh
> > 
> > as lintian also reports:
> > 
> >   → lintian grub-common_2.12\~rc1-9_amd64.deb
> >   E: grub-common: wrong-path-for-interpreter /usr/bin/sh != /bin/sh 
> > [etc/grub.d/25_bli]
>
> Merged-usr has been mandatory since bookworm

Nevertheless the Debian Policy nowhere mentions /usr/bin/sh but only
/bin/sh.

> it has been addressed in the upstream git branch and will be fixed
> in the final 2.12 release.

Ok, that's good to hear.

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE



Bug#1050393: Unneeded dependency on "dconf-gsettings-backend | gsettings-backend"?

2023-09-06 Thread Axel Beckert
Control: severity -1 important

Hi,

John Zaitseff wrote:
> The latest (Sid) version of emacs-common now depends on
> "dconf-gsettings-backend | gsettings-backend", which in turn
> eventually installs dbus-daemon -- which is problematic in a Debian
> build chroot environment.  Can that dependency be downgraded to
> Recommends or Suggests?

Or put the dependency back into those packages which actually require
dbus. Because the current dependency setup causes dbus and other
completely unnecessary desktop stuff to be pulled in on servers and
VMs where just emacs-nox is installed despite emacs-nox is meant for
non desktop systems. (And please remember that the "d" in "dbus"
stands for "desktop".)

John Zaitseff wrote:
> After a bit of digging around through the package source code, this
> is as a result of using the binaries from the "pgtk" build of Emacs
> for common binaries -- since "other builds' emacsclients cannot
> connect to pgtk under Wayland".

*sigh*

> Given that that is a good reason, IMHO, for using the binaries in
> that way, feel free to close this bug report.

No, this is a rather severe degradation of emacs-nox's usability and
needs to be fixed, either by splitting off these components into a new
package emacs-common-pgtk or simlar if Wayland causes such problems
for other variants or by solving it in another way which causes less
issues for the other variants, too —- like e.g. putting these
dependencies in other packages with emacs-common just sporting them in
Recommends or Suggests.

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE



Bug#1051328: grub-common: wrong-path-for-interpreter /usr/bin/sh != /bin/sh [etc/grub.d/25_bli]

2023-09-06 Thread Axel Beckert
Package: grub-common
File: /etc/grub.d/25_bli
Version: 2.12~rc1-7
Version: 2.12~rc1-9
Severity: serious

For some reason, possibly usrmerge-triggered, since 2.12~rc1-7
/etc/grub.d/25_bli sports the following non-standard shebang line:

  #!/usr/bin/sh

as lintian also reports:

  → lintian grub-common_2.12\~rc1-9_amd64.deb
  E: grub-common: wrong-path-for-interpreter /usr/bin/sh != /bin/sh 
[etc/grub.d/25_bli]

Interestingly only this single file seems to be affected.

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

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

Versions of packages grub-common depends on:
ii  gettext-base0.21-13
ii  libc6   2.37-7
ii  libdevmapper1.02.1  2:1.02.185-2
ii  libefiboot1 37-6
ii  libefivar1  37-6
ii  libfreetype62.13.2+dfsg-1
ii  libfuse3-3  3.14.0-4
ii  liblzma55.4.4-0.1

Versions of packages grub-common recommends:
pn  os-prober  

Versions of packages grub-common suggests:
ii  console-setup  1.222
ii  desktop-base   12.0.6+nmu1
pn  grub-emu   
ii  mtools 4.0.43-1
pn  multiboot-doc  
ii  xorriso1.5.4-4

-- no debconf information



Bug#1051192: solid-auth, liblog-any-perl: solid-auth became uninstallable after liblog-any-perl dropped liblog-any-adapter-perl Provides

2023-09-04 Thread Axel Beckert
Hi gregor,

gregor herrmann wrote:
> > > I noticed that liblog-any-adapter-perl was removed in 2015, and, more
> > > importantly, I checked with `apt-cache rdepends
> > > liblog-any-adapter-perl' which, unless I was blind, didn't show
> > > anything.
> > I can confirm that — looks like a bug around virtual packages:
> 
> Thanks for double-checking!

You're welcome.

> > → grep-aptavail -FDepends -P liblog-any-adapter-perl | fgrep 
> > liblog-any-adapter-perl
> 
> Nice, I always forget the syntax.

Didn't get it right on the first try, either. :-)

> With different output:
> 
> % grep-aptavail -FDepends -P liblog-any-adapter-perl -s Source,Package,Depends

I had -S in my mind, but that's the opposite of -P and hence got weird
results. :-)

> > Should we do this in solid-auth, too, or just use solely
> > liblog-any-perl?
> 
> I'd go for only liblog-any-perl everywhere as is gone …

The longer I think about the more I tend towards that direction, too.

gregor herrmann wrote:
> These 4 are fixed in git to only use liblog-any-perl (but not
> uploaded as there is no practical problem).
[…]
> Done for src:libweb-solid-auth-perl, and uploaded.

Perfect. Thanks a lot!

> Hm, and I found more in git:
> 
> % grep liblog-any-adapter-perl */debian/control
> liblog-any-adapter-screen-perl/debian/control: liblog-any-perl | 
> liblog-any-adapter-perl ,
> liblog-any-adapter-screen-perl/debian/control: liblog-any-perl | 
> liblog-any-adapter-perl,
> librdf-linkeddata-perl/debian/control: liblog-any-adapter-perl,
> librdf-linkeddata-perl/debian/control: liblog-any-adapter-perl,
> 
> Not found by grep-aptavail? Next weirdness …

I think I managed to solve that mystery:

> Oh, look, the latter has fresh autopkgtest failures on ci.d.n.

O.o

I think something went wrong here as the commit message doesn't fit at
all with the changes:
https://salsa.debian.org/perl-team/modules/packages/librdf-linkeddata-perl/-/commit/6955989b1474f72cb75c33aa3f0cde418c82ff68

Then again, that was 6 years ago.

Ah, that were solely build-dependencies, not run-time dependencies. At
least that mystery is solved. :-)

Anyway, thanks for your efforts and sorry that I currently can't help
that much with the actual work. (Lagging behind with fixing RC bugs in
my non-team packages, too…)

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE



Bug#1051209: dpkg-dev: dpkg-source --commit should use configured default editor instead of forcing nano

2023-09-04 Thread Axel Kittenberger
Package: dpkg-dev
Version: 1.22.0
Severity: normal

Dear Maintainer,

   * What led up to the situation?

 using: dpkg-source --commit

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

 I used `update-alternatives --config editor` because I want to edit with 
vim.
 (actually it became the default editor already by manually install 
vim-gtk3)

   * What was the outcome of this action?

dpkg-source uses nano

   * What outcome did you expect instead?

dpkg-source using vim (or just call `editor`)

-- Package-specific info:
This system uses merged-usr-via-aliased-dirs, going behind dpkg's
back, breaking its core assumptions. This can cause silent file
overwrites and disappearances, and its general tools misbehavior.
See .

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

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

Versions of packages dpkg-dev depends on:
ii  binutils  2.41-4
ii  bzip2 1.0.8-5+b1
ii  libdpkg-perl  1.22.0
ii  make  4.3-4.1
ii  patch 2.7.6-7
ii  perl  5.36.0-7
ii  tar   1.34+dfsg-1.2
ii  xz-utils  5.4.4-0.1

Versions of packages dpkg-dev recommends:
ii  build-essential  12.10
ii  clang-14 [c-compiler]1:14.0.6-13
ii  fakeroot 1.32.1-1
ii  gcc [c-compiler] 4:13.2.0-1
ii  gcc-13 [c-compiler]  13.2.0-2
ii  gnupg2.2.40-1.1
ii  gpgv 2.2.40-1.1
ii  libalgorithm-merge-perl  0.08-5

Versions of packages dpkg-dev suggests:
ii  debian-keyring  2023.05.26

-- no debconf information



Bug#1051192: solid-auth,liblog-any-perl: solid-auth became uninstallable after liblog-any-perl dropped liblog-any-adapter-perl Provides

2023-09-04 Thread Axel Beckert
Hi gregor,

gregor herrmann wrote:
> > after the upload of liblog-any-perl/1.717-1, solid-auth/0.91-1 became
> > uninstallable as it depends on liblog-any-adapter-perl which is no more
> > provided by liblog-any-perl since 1.717-1.
> 
> Oops, sorry for that.

Well, aptitude automatically suggested to hold back liblog-any-perl. :-)

> I noticed that liblog-any-adapter-perl was removed in 2015, and, more
> importantly, I checked with `apt-cache rdepends
> liblog-any-adapter-perl' which, unless I was blind, didn't show
> anything.

I can confirm that — looks like a bug around virtual packages:

→ apt-rdepends liblog-any-adapter-perl
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
liblog-any-adapter-perl
→ apt-cache rdepends liblog-any-adapter-perl

→

Weird. 

> > I'm not sure, but I assume, this is best fixed in
> > src:libweb-solid-auth-perl. An according revert in liblog-any-perl would
> > fix the issue as well, though.
> 
> A fix in libweb-solid-auth-perl seems more appropriate to me; unless
> we have more hidden dependencies …

As far as I can see, solid-auth should be the last one. All others
already have it as last part of a list of alternative dependencies, so
no issue:

→ grep-aptavail -FDepends -P liblog-any-adapter-perl | fgrep 
liblog-any-adapter-perl
Depends: perl:any, libboolean-perl, libclone-perl, libdata-visitor-perl, 
libfailures-perl, libhttp-message-perl, libjson-perl, liblog-any-perl | 
liblog-any-adapter-perl, libmime-types-perl, libmoo-perl, libsafe-isa-perl, 
libstrictures-perl, libtype-tiny-perl, liburi-namespacemap-perl, liburi-perl, 
liburi-template-perl, libxml-regexp-perl
Depends: perl:any, liblog-any-perl | liblog-any-adapter-perl
Depends: perl:any, liblog-any-perl | liblog-any-adapter-perl, 
liblog-dispatch-perl
Depends: perl:any, liblog-any-perl | liblog-any-adapter-perl
Depends: libfile-libmagic-perl, libjson-perl, liblog-any-adapter-log4perl-perl, 
liblog-any-adapter-perl, liblog-log4perl-perl, libpath-tiny-perl, 
libstring-escape-perl, libweb-solid-auth-perl, perl:any
→ 

Should we do this in solid-auth, too, or just use solely
liblog-any-perl?

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE



Bug#1051192: solid-auth,liblog-any-perl: solid-auth became uninstallable after liblog-any-perl dropped liblog-any-adapter-perl Provides

2023-09-04 Thread Axel Beckert
Package: solid-auth,liblog-any-perl
Severity: serious
Control: found -1 liblog-any-perl/1.717-1
Control: found -1 solid-auth/0.91-1

Hi,

after the upload of liblog-any-perl/1.717-1, solid-auth/0.91-1 became
uninstallable as it depends on liblog-any-adapter-perl which is no more
provided by liblog-any-perl since 1.717-1.

I'm not sure, but I assume, this is best fixed in
src:libweb-solid-auth-perl. An according revert in liblog-any-perl would
fix the issue as well, though.

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

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



Bug#1042463: lintian does not accept overrides in the syntax used on ftp-master

2023-09-01 Thread Axel Beckert
Control: tag -1 + moreinfo

Hi Julian,

Julian Andres Klode wrote:
> lintian in the archive needs to restore support for the old override
> format, or ftpmaster needs to be updated to the new lintian.

We had a lengthy discussion about the override format changes made by
Felix (see https://bugs.debian.org/1007002) and there's no way back
(including "backwards compatibility") unless someone volunteers to
implement a fix for this. (I won't do that as mentioned in this
thread. See also below for some reasoning.)

> Normal source-only uploads do not trigger the issue usually, but
> there surely have been people adopting their overrides to the new
> format who now get stuck (like me) at binary-NEW with a reject when
> having to do a binary upload.

Please give an explicit example. I'm not sure if you and me think of
the same "new" and "old" format. → Tagged as "moreinfo".

As mentioned in #1007002 there's a script in the migrate-overrides
branch of https://salsa.debian.org/lintian/lintian/ which can
automatically migrate tags in override files.

But so far it only knows a few of the very annoying tags — which is also
the reason it's not in the package yet.

But I'm willing to extend that script and maybe even implement a mode
for ftp-masters if I get an example of a file which needs to be
migrated (including file name and maybe default path).

But for that I need old real-life examples. (Maybe ftp-masters can
give me the file/list Julian mentioned or tell me where to find it?)

> For an orderly transition, lintian needs to […]

Please tell this the previous lintian lead developer who decided and
implemented this inmidst of tons of other invasive changes (like
rewriting Lintian's internal module structure) without doing a release
for months or doing a release after one of these invasive changes.

It's anything but a simple "git revert" to get the old format back.
And a compatibility mode would require implementing the old override
format in the new framework from scratch.

Short said: IMHO we should do a forward escape instead of trying to
implement a very work-intensive backwards compatibility. For which we
don't seem to have the resources anyway unless someone volunteers.

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE



Bug#1050522: wdm: FTBFS: fatal error: pango/pango.h: No such file or directory

2023-08-25 Thread Axel Beckert
Control: tag -1 + confirmed pending

Hi Aurelien,

Aurelien Jarno wrote:
> wdm fails to build from source. From my build log on amd64:

Thanks for the bug report!

> | /usr/include/WINGs/WINGsP.h:8:10: fatal error: pango/pango.h: No such file 
> or directory
> | 8 | #include 

I can reproduce in a clean chroot. But it does not happen when
building in my Sid workstation. So it looks like a missing
respectively now separate build dependency.

Just tested: Adding a build-dependency on libpango1.0-dev suffices to
get it building in a clean chroot again.

    Regards, Axel
-- 
 ,''`.  |  Axel Beckert , https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE



Bug#1050116: openuniverse: Please do not refer to unavailable packages in descriptions

2023-08-19 Thread Axel Stammler
Package: openuniverse
Severity: minor
X-Debbugs-Cc: a...@users.sourceforge.net

Dear Maintainer,

the description available through

apt show openuniverse

ends by saying: “users are recommended to use Celestia instead”

but there is no Debian package of that or a similar name.

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

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

Versions of packages openuniverse depends on:
ii  libc6   2.36-9+deb12u1
ii  libgcc-s1   12.2.0-14
ii  libgl1  1.6.0-1
ii  libglu1-mesa [libglu1]  9.0.2-1.1
ii  libglut3.12 3.4.0-1
ii  libjpeg62-turbo 1:2.1.5-2
pn  libplib1
ii  libstdc++6  12.2.0-14
pn  openuniverse-common 

openuniverse recommends no packages.

openuniverse suggests no packages.


Bug#1043447: grub-efi-amd64: Should provide grub-efi

2023-08-11 Thread Axel Stammler
Package: grub-efi-amd64
Version: 2.06-13
Severity: wishlist
X-Debbugs-Cc: a...@users.sourceforge.net

Dear Maintainer,

I have created a small package for myself that changes the Grub boot menu to 
contain the
hostname (so that booting from removable media is made abundantly clear). So 
far I have
made this package dependent on grub-pc or grub-efi, so this would help avoid 
listing all
architectures in the dependencies.

In the configuration files below, ‘Gabriel’ is used as hostname.


-- Package-specific info:

*** BEGIN /proc/mounts
/dev/sda2 / ext4 rw,relatime,errors=remount-ro 0 0
/dev/sda5 /usr ext4 rw,relatime 0 0
/dev/sda4 /tmp ext4 rw,relatime 0 0
/dev/sda3 /boot ext4 rw,relatime 0 0
/dev/sda6 /var ext4 rw,relatime 0 0
/dev/sda1 /boot/efi vfat 
rw,relatime,fmask=0077,dmask=0077,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro
 0 0
/dev/mapper/sda8_crypt /home ext4 rw,relatime 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="0"
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_gpt
insmod ext2
set root='hd0,gpt5'
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt5 
--hint-efi=hd0,gpt5 --hint-baremetal=ahci0,gpt5  
77212bdf-01ef-446c-8bbe-d9e97e0ceb5d
else
  search --no-floppy --fs-uuid --set=root 77212bdf-01ef-446c-8bbe-d9e97e0ceb5d
fi
font="/share/grub/unicode.pf2"
fi

if loadfont $font ; then
  set gfxmode=auto
  load_video
  insmod gfxterm
  set locale_dir=$prefix/locale
  set lang=en_IE
  insmod gettext
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_gpt
insmod ext2
set root='hd0,gpt5'
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt5 
--hint-efi=hd0,gpt5 --hint-baremetal=ahci0,gpt5  
77212bdf-01ef-446c-8bbe-d9e97e0ceb5d
else
  search --no-floppy --fs-uuid --set=root 77212bdf-01ef-446c-8bbe-d9e97e0ceb5d
fi
insmod png
if background_image /share/desktop-base/emerald-theme/grub/grub-16x9.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=
export linux_gfx_mode
menuentry 'Gabriel: Debian GNU/Linux' --class gabriel_ --class gnu-linux 
--class gnu --class os $menuentry_id_option 
'gnulinux-simple-2458cb7b-31b4-45e5-bdb4-aee6d3430c35' {
load_video
insmod gzio
if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
insmod part_gpt
insmod ext2
set root='hd0,gpt3'
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt3 
--hint-efi=hd0,gpt3 --hint-baremetal=ahci0,gpt3  
977f3a57-d0fc-48d2-838d-aec444865121
else
  search --no-floppy --fs-uuid --set=root 
977f3a57-d0fc-48d2-838d-aec444865121
fi
echo'Loading Linux 6.1.0-11-amd64 ...'
linux   /vmlinuz-6.1.0-11-amd64 
root=UUID=2458cb7b-31b4-45e5-bdb4-aee6d3430c35 ro  quiet
echo'Loading initial ramdisk ...'
initrd  /initrd.img-6.1.0-11-amd64
}
submenu 'Advanced options for Gabriel: Debian GNU/Linux' $menuentry_id_option 
'gnulinux-advanced-2458cb7b-31b4-45e5-bdb4-aee6d3430c35' {
menuentry 'Gabriel: Debian GNU/Linux, with Linux 6.1.0-11-amd64' 
--class gabriel_ --class gnu-linux --class gnu --clas

Bug#1043338: gnome: Third-level keyboard characters are mostly very strange and wrong

2023-08-09 Thread Axel Stammler
Package: gnome
Version: 1:43+1
Severity: important
X-Debbugs-Cc: a...@users.sourceforge.net

Dear Maintainer,

Here are some mistaken third-level ( or ) settings and their 
expected
values as shown on my German keyboard and as they correctly appear on the 
console:

regular Shift   Alt-Gr  expectedconsole
ß   ?   —   backslash   \
+   *   ]   tilde   ~
8   (   ∞   open square bracket [


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

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

Versions of packages gnome depends on:
ii  avahi-daemon 0.8-10
ii  cheese   43.0-1
ii  cups-pk-helper   0.2.6-1+b1
ii  desktop-base 12.0.6+nmu1~deb12u1
ii  evolution3.46.4-2
ii  evolution-plugins3.46.4-2
ii  file-roller  43.0-1
ii  gnome-calendar   43.1-2
ii  gnome-clocks 43.0-1
ii  gnome-color-manager  3.36.0-1+b1
ii  gnome-core   1:43+1
ii  gnome-maps   43.5-2~deb12u1
ii  gnome-music  42.1-1
ii  gnome-sound-recorder 43~beta-1
ii  gnome-tweaks 42~beta-4
ii  gnome-weather43.0-1
ii  gstreamer1.0-libav   1.22.0-2
ii  gstreamer1.0-plugins-ugly1.22.0-2
ii  libgsf-bin   1.14.50-1
ii  libproxy1-plugin-networkmanager  0.4.18-1.2
ii  libreoffice-calc 4:7.4.7-1
ii  libreoffice-gnome4:7.4.7-1
ii  libreoffice-impress  4:7.4.7-1
ii  libreoffice-writer   4:7.4.7-1
ii  network-manager-gnome1.30.0-2
ii  orca 43.1-1
ii  rhythmbox3.4.6-2+b1
ii  rhythmbox-plugin-cdrecorder  3.4.6-2+b1
ii  rhythmbox-plugins3.4.6-2+b1
ii  rygel-playbin0.42.1-1
ii  rygel-tracker0.42.1-1
ii  seahorse 43.0-1
ii  shotwell 0.30.17-1+b1
ii  simple-scan  42.5-2
ii  totem-plugins43.0-2
ii  xdg-user-dirs-gtk0.11-1

Versions of packages gnome recommends:
ii  gnome-games   1:43+1
ii  gnome-initial-setup   43.2-6
ii  gnome-remote-desktop  43.3-1
ii  transmission-gtk  3.00-2.1+b1

Versions of packages gnome suggests:
pn  alacarte  
pn  empathy   
pn  firefox-esr-l10n-all | firefox-l10n-all   
pn  goobox | sound-juicer 
pn  polari
pn  vinagre   
pn  webext-ublock-origin-firefox | webext-ublock-origin-chromium  

Versions of packages gnome-core depends on:
ii  adwaita-icon-theme43-1
ii  at-spi2-core  2.46.0-5
ii  baobab43.0-1
ii  dconf-cli 0.40.0-4
ii  dconf-gsettings-backend   0.40.0-4
ii  eog   43.2-1
ii  evince43.1-2+b1
ii  evolution-data-server 3.46.4-2
ii  fonts-cantarell   0.303.1-1
ii  gdm3  43.0-3
ii  gkbd-capplet  3.28.1-1
ii  glib-networking   2.74.0-4
ii  gnome-backgrounds 43.1-1
ii  gnome-bluetooth-sendto42.5-3
ii  gnome-calculator  1:43.0.1-2
ii  gnome-characters  43.1-1
ii  gnome-contacts43.1-1
ii  gnome-control-center  1:43.6-2~deb12u1
ii  gnome-disk-utility43.0-1
ii  gnome-font-viewer 43.0-1
ii  gnome-keyring 42.1-1+b2
ii  gnome-logs43.0-1
ii  gnome-menus   3.36.0-1.1
ii  gnome-online-accounts 3.46.0-1
ii  gnome-session 43.0-1
ii  gnome-settings-daemon 43.0-4
ii  gnome-shell   43.6-1~deb12u1
ii  gnome-shell-extensions43.1-1
ii  gnome-software43.5-1~deb12u1
ii  gnome-sushi   43.0-2
ii  gnome-system-monitor  42.0-2
ii  gnome-terminal3.46.8-1
ii  gnome-text-editor 43.2-1
ii  gnome-themes-extra3.28-2
ii  gnome-user-docs   43.0-2
ii  gnome-user-share  43.0-1
ii  gsettings-desktop-schemas 43.0-1
ii  gstreamer1.0-packagekit   1.2.6-5
ii  gstreamer1.0-plugins-base 1.22.0-3+

Bug#1042911: Breaks Emacs 29.1 upgrade: muse-split.el:41:2: Error: Cannot open load file: No such file or directory, assoc

2023-08-02 Thread Axel Beckert
Package: elpa-muse
Version: 3.20+dfsg-7
Severity: serious
X-Debbugs-Cc: a...@debian.org
Control: affects -1 emacs emacs-gtk emacs-lucid emacs-nox emacs-pgtk

Since upgrading to Emacs 29.1, byte-(re-)compilation fails as follows:

[…]
Install elpa-muse for emacs
install/muse-3.20: Handling install of emacsen flavor emacs
install/muse-3.20: byte-compiling for emacs

In toplevel form:
cgi.el:71:2: Warning: Package cl is deprecated
cgi.el:87:13: Warning: Unknown defun property ‘character’

In cgi-decode-string:
cgi.el:94:4: Warning: ‘do’ is an obsolete alias (as of 27.1); use ‘cl-do’ 
instead.
cgi.el:101:15: Warning: ‘incf’ is an obsolete alias (as of 27.1); use ‘cl-incf’ 
instead.
cgi.el:108:17: Warning: ‘incf’ is an obsolete alias (as of 27.1); use ‘cl-incf’ 
instead.

In cgi-decode:
cgi.el:124:6: Warning: ‘flet’ is an obsolete macro (as of 24.3); use either 
‘cl-flet’ or ‘cl-letf’.

In cgi-arguments:
cgi.el:161:13: Warning: ‘loop’ is an obsolete alias (as of 27.1); use ‘cl-loop’ 
instead.

In end of data:
cgi.el:197:16: Warning: the function ‘calendar-current-date’ might not be 
defined at runtime.

In toplevel form:
htmlize-hack.el:12:13: Warning: ‘loop’ is an obsolete alias (as of 27.1); use 
‘cl-loop’ instead.
htmlize-hack.el:17:8: Warning: ‘reduce’ is an obsolete function (as of 27.1); 
use ‘cl-reduce’ instead.

In muse-backlink-insert-hook-func:
muse-backlink.el:264:12: Warning: ‘font-lock-fontify-buffer’ is for interactive 
use only; use ‘font-lock-ensure’ or ‘font-lock-flush’ instead.

In end of data:
muse-backlink.el:313:33: Warning: the function ‘muse-make-link’ might not be 
defined at runtime.

In toplevel form:
muse-colors.el:60:2: Warning: custom-declare-variable 
`muse-colors-autogen-headings' docstring has wrong usage of unescaped single 
quotes (use \= or different
 quoting)
muse-colors.el:94:2: Warning: custom-declare-variable 
`muse-colors-inline-image-method' docstring has wrong usage of unescaped single 
quotes (use \= or differ
ent quoting)

In muse-colors-region:
muse-colors.el:577:10: Warning: ‘inhibit-point-motion-hooks’ is an obsolete 
variable (as of 25.1); use ‘cursor-intangible-mode’ or ‘cursor-sensor-mode’ 
instea
d

In muse-unhighlight-region:
muse-colors.el:732:10: Warning: ‘inhibit-point-motion-hooks’ is an obsolete 
variable (as of 25.1); use ‘cursor-intangible-mode’ or ‘cursor-sensor-mode’ 
instea
d

In muse-colors-lisp-tag:
muse-colors.el:775:30: Warning: ‘muse-looking-back’ called with 1 argument, but 
requires 2 or 3

In muse-docbook-markup-paragraph:
muse-docbook.el:233:41: Warning: ‘muse-looking-back’ called with 1 argument, 
but requires 2 or 3

In toplevel form:
muse-html.el:67:2: Warning: custom-declare-variable `muse-html-style-sheet' 
docstring wider than 80 characters
muse-html.el:96:2: Warning: custom-declare-variable `muse-xhtml-style-sheet' 
docstring wider than 80 characters
muse-html.el:399:2: Warning: custom-declare-variable 
`muse-html-meta-content-encoding' docstring has wrong usage of unescaped single 
quotes (use \= or differe
nt quoting)
muse-html.el:421:2: Warning: custom-declare-variable 
`muse-html-src-allowed-modes' docstring has wrong usage of unescaped single 
quotes (use \= or different q
uoting)

In muse-html-markup-paragraph:
muse-html.el:490:6: Warning: ‘muse-looking-back’ called with 1 argument, but 
requires 2 or 3

In muse-html-src-tag:
muse-html.el:670:16: Warning: ‘font-lock-fontify-buffer’ is for interactive use 
only; use ‘font-lock-ensure’ or ‘font-lock-flush’ instead.
../../elpa-src/muse-3.20/cgi.el: Warning: Unknown defun property ‘character’
../../elpa-src/muse-3.20/cgi.el: Warning: ‘do’ is an obsolete alias (as of 
27.1); use ‘cl-do’ instead.
../../elpa-src/muse-3.20/cgi.el: Warning: ‘incf’ is an obsolete alias (as of 
27.1); use ‘cl-incf’ instead.
../../elpa-src/muse-3.20/cgi.el: Warning: ‘incf’ is an obsolete alias (as of 
27.1); use ‘cl-incf’ instead.
../../elpa-src/muse-3.20/cgi.el: Warning: ‘incf’ is an obsolete alias (as of 
27.1); use ‘cl-incf’ instead.
../../elpa-src/muse-3.20/cgi.el: Warning: ‘flet’ is an obsolete macro (as of 
24.3); use either ‘cl-flet’ or ‘cl-letf’.
../../elpa-src/muse-3.20/cgi.el: Warning: ‘loop’ is an obsolete alias (as of 
27.1); use ‘cl-loop’ instead.
../../elpa-src/muse-3.20/muse-ipc.el: Warning: ‘return-from’ is an obsolete 
alias (as of 27.1); use ‘cl-return-from’ instead.
../../elpa-src/muse-3.20/muse-ipc.el: Warning: ‘return-from’ is an obsolete 
alias (as of 27.1); use ‘cl-return-from’ instead.

In toplevel form:
muse-ipc.el:50:2: Warning: custom-declare-variable `muse-ipc-ignore-done' 
docstring has wrong usage of unescaped single quotes (use \= or different 
quoting)
muse-ipc.el:80:2: Warning: ‘defun*’ is an obsolete alias (as of 27.1); use 
‘cl-defun’ instead.

In muse-ipc-server-filter:
muse-ipc.el:93:6: Warning: ‘return-from’ is an obsolete alias (as of 27.1); use 
‘cl-return-from’ instead.

In muse-journal-generate-pages:
muse-journal.el:186:24: Warning: value returned from (match-strin

Bug#1042907: Breaks Emacs 29.1 upgrade: haskell.el:30:2: Error: Eager macro-expansion failure: (error "Misplaced t or ‘otherwise’ clause")

2023-08-02 Thread Axel Beckert
Package: elpa-haskell-mode
Version: 17.2-5
Severity: serious
X-Debbugs-Cc: a...@debian.org
Control: affects -1 emacs emacs-gtk emacs-lucid emacs-nox emacs-pgtk

After upgrading Emacs to 29.1, byte-(re-)compiling fails as follows:

[…]
Install elpa-haskell-mode for emacs
install/haskell-mode-17.2snapshot: Handling install of emacsen flavor emacs
install/haskell-mode-17.2snapshot: byte-compiling for emacs
../../elpa-src/haskell-mode-17.2snapshot/haskell-cabal.el: Warning: Case 
'before will match ‘quote’.  If that’s intended, write (before quote) instead.  
Otherwise, don’t quote ‘before’.
../../elpa-src/haskell-mode-17.2snapshot/haskell-cabal.el: Warning: Case 'after 
will match ‘quote’.  If that’s intended, write (after quote) instead.  
Otherwise, don’t quote ‘after’.
../../elpa-src/haskell-mode-17.2snapshot/haskell-cabal.el: Warning: Case 
'single will match ‘quote’.  If that’s intended, write (single quote) instead.  
Otherwise, don’t quote ‘single’.
../../elpa-src/haskell-mode-17.2snapshot/haskell-process.el: Warning: Case 
'ghci will match ‘quote’.  If that’s intended, write (ghci quote) instead.  
Otherwise, don’t quote ‘ghci’.
../../elpa-src/haskell-mode-17.2snapshot/haskell-process.el: Warning: Case 
'cabal-repl will match ‘quote’.  If that’s intended, write (cabal-repl quote) 
instead.  Otherwise, don’t quote ‘cabal-repl’.
../../elpa-src/haskell-mode-17.2snapshot/haskell-process.el: Warning: Case 
'stack-ghci will match ‘quote’.  If that’s intended, write (stack-ghci quote) 
instead.  Otherwise, don’t quote ‘stack-ghci’.
../../elpa-src/haskell-mode-17.2snapshot/haskell-commands.el: Warning: Case 
'unknown-command will match ‘quote’.  If that’s intended, write 
(unknown-command quote) instead.  Otherwise, don’t quote ‘unknown-command’.
../../elpa-src/haskell-mode-17.2snapshot/haskell-commands.el: Warning: Case 
'option-missing will match ‘quote’.  If that’s intended, write (option-missing 
quote) instead.  Otherwise, don’t quote ‘option-missing’.
../../elpa-src/haskell-mode-17.2snapshot/haskell-commands.el: Warning: Case 
'interactive-error will match ‘quote’.  If that’s intended, write 
(interactive-error quote) instead.  Otherwise, don’t quote ‘interactive-error’.

In toplevel form:
ghci-script-mode.el:20:2: Error: Eager macro-expansion failure: (error 
"Misplaced t or ‘otherwise’ clause")

In haskell-cabal-classify-line:
haskell-cabal.el:363:2: Warning: docstring wider than 80 characters
haskell-cabal.el:363:2: Warning: docstring has wrong usage of unescaped single 
quotes (use \= or different quoting)

In haskell-cabal-enum-targets:
haskell-cabal.el:496:2: Warning: docstring wider than 80 characters

In haskell-cabal-listify:
haskell-cabal.el:701:12: Warning: Case 'before will match ‘quote’.  If that’s 
intended, write (before quote) instead.  Otherwise, don’t quote ‘before’.
haskell-cabal.el:701:12: Warning: Case 'after will match ‘quote’.  If that’s 
intended, write (after quote) instead.  Otherwise, don’t quote ‘after’.
haskell-cabal.el:701:12: Warning: Case 'single will match ‘quote’.  If that’s 
intended, write (single quote) instead.  Otherwise, don’t quote ‘single’.

In haskell-cabal-line-filename:
haskell-cabal.el:926:2: Warning: docstring wider than 80 characters

In haskell-blank-line-p:
haskell-collapse.el:46:9: Warning: ‘point-at-eol’ is an obsolete function (as 
of 29.1); use ‘line-end-position’ or ‘pos-eol’ instead.

In haskell-hide-toggle-all:
haskell-collapse.el:95:19: Warning: ‘point-at-bol’ is an obsolete function (as 
of 29.1); use ‘line-beginning-position’ or ‘pos-bol’ instead.

In toplevel form:
haskell-commands.el:652:12: Error: Misplaced t or ‘otherwise’ clause

In toplevel form:
haskell-compile.el:42:2: Warning: custom-declare-variable 
`haskell-compile-cabal-build-command' docstring wider than 80 characters
haskell-compile.el:49:2: Warning: custom-declare-variable 
`haskell-compile-cabal-build-alt-command' docstring wider than 80 characters
haskell-compile.el:56:2: Warning: custom-declare-variable 
`haskell-compile-stack-build-command' docstring wider than 80 characters
haskell-compile.el:63:2: Warning: custom-declare-variable 
`haskell-compile-stack-build-alt-command' docstring wider than 80 characters
haskell-compile.el:70:2: Warning: custom-declare-variable 
`haskell-compile-command' docstring wider than 80 characters
haskell-compile.el:83:2: Warning: custom-declare-variable 
`haskell-compiler-type' docstring wider than 80 characters

In haskell-completions-grab-pragma-prefix:
haskell-completions.el:146:2: Warning: docstring has wrong usage of unescaped 
single quotes (use \= or different quoting)

In haskell-completions-grab-identifier-prefix:
haskell-completions.el:216:2: Warning: docstring has wrong usage of unescaped 
single quotes (use \= or different quoting)

In haskell-completions-grab-prefix:
haskell-completions.el:267:2: Warning: docstring has wrong usage of unescaped 
single quotes (use \= or different quoting)

In haskell-completions--simple-completions:

Bug#1042900: Breaks Emacs 29.1 upgrade: pointback.el:34:2: Error: Cannot open load file: No such file or directory, assoc

2023-08-02 Thread Axel Beckert
Package: elpa-pointback
Version: 0.2-4
Severity: serious
X-Debbugs-Cc: a...@debian.org
Control: affects -1 emacs emacs-gtk emacs-lucid emacs-nox emacs-pgtk

Since the upgrade to Emacs 29.1-1, byte (re-)compilation fails as
follows:

[…]
Install elpa-pointback for emacs
install/pointback-0.2: Handling install of emacsen flavor emacs
install/pointback-0.2: byte-compiling for emacs

In toplevel form:
pointback.el:34:2: Error: Cannot open load file: No such file or directory, 
assoc
ERROR: install script from elpa-pointback package failed
dpkg: error processing package emacs-gtk (--configure):
 installed emacs-gtk package post-installation script subprocess returned error 
exit status 1
dpkg: dependency problems prevent configuration of emacs:
[…]

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

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

Versions of packages elpa-pointback depends on:
ii  dh-elpa-helper  2.0.17
ii  emacsen-common  3.0.5

Versions of packages elpa-pointback recommends:
iu  emacs  1:29.1+1-2
ih  emacs-gtk [emacs]  1:29.1+1-2

elpa-pointback suggests no packages.

-- no debconf information


Bug#1042845: libembperl-perl: FTBFS with Perl 5.38: test failures

2023-08-01 Thread Axel Beckert
Hi Niko,

Niko Tyni wrote:
> This package fails to build from source with Perl 5.38 (currently in
> experimental.)

Thanks for the bug report.

> I assume the diagnostics have changed again and it's just the tests that
> need adjusting, but I haven't checked properly.

Will look into it, but may take a while.

>cat: test/tmp/httpd.pid: No such file or directory

That one looks familiar, but IIRC was a red herring.

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE



Bug#1042563: installation-reports: installation OK, screen remains blank during boot and GDM Greeter

2023-08-01 Thread Dr. Axel Stammler

Hi, Steve and Len,

Thank you for pointing this out.

On Mon 2023-07-31 09.22.35, Lennart Sorensen wrote:

On Sun, Jul 30, 2023 at 01:08:13PM +0100, Steve McIntyre wrote:



I'm a little confused here...

You say the machine is a Thinkpad X230, but the attached cpuinfo says
you have an Atom CPU and the DMI data says it's an ASUSTeK Eee
PC. What hardware are we actually looking at here please?


It also says 4.15 kernel which is clearly not bookworm.  I think the
installation log was accidentally from a much earlier install on a
different machine.


The installation report must indeed be ancient, from an installation on an Eee 
‘netbook’ some years ago, possibly Stretch or an even older release.

My bug report relates to the situation after an upgrade from Bullseye on the 
Thinkpad X230:

$ lscpu
Architecture:x86_64
CPU op-mode(s):  32-bit, 64-bit
Address sizes:   36 bits physical, 48 bits virtual
Byte Order:  Little Endian
CPU(s):  4
On-line CPU(s) list: 0-3
Vendor ID:   GenuineIntel
Model name:  Intel(R) Core(TM) i5-3320M CPU @ 2.60GHz
CPU family:  6
Model:   58
Thread(s) per core:  2
Core(s) per socket:  2
Socket(s):   1
Stepping:9
CPU(s) scaling MHz:  55%
CPU max MHz: 3300.
CPU min MHz: 1200.
BogoMIPS:5188.29
Flags:   fpu vme de pse tsc msr pae mce cx8 apic sep 
mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe 
syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology 
nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est 
tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer 
aes xsave avx f16c rdrand lahf_lm cpuid_fault epb pti ssbd ibrs ibpb stibp 
tpr_shadow vnmi flexpriority ept vpid fsgsbase smep erms xsaveopt dtherm ida 
arat pln pts md_clear flush_l1d
Virtualization:  VT-x
L1d cache:   64 KiB (2 instances)
L1i cache:   64 KiB (2 instances)
L2 cache:512 KiB (2 instances)
L3 cache:3 MiB (1 instance)
NUMA node(s):1
NUMA node0 CPU(s):   0-3
Vulnerability Itlb multihit: KVM: Mitigation: VMX disabled
Vulnerability L1tf:  Mitigation; PTE Inversion; VMX conditional 
cache flushes, SMT vulnerable
Vulnerability Mds:   Mitigation; Clear CPU buffers; SMT vulnerable
Vulnerability Meltdown:  Mitigation; PTI
Vulnerability Mmio stale data:   Unknown: No mitigations
Vulnerability Retbleed:  Not affected
Vulnerability Spec store bypass: Mitigation; Speculative Store Bypass disabled 
via prctl
Vulnerability Spectre v1:Mitigation; usercopy/swapgs barriers and 
__user pointer sanitization
Vulnerability Spectre v2:Mitigation; Retpolines, IBPB conditional, 
IBRS_FW, STIBP conditional, RSB filling, PBRSB-eIBRS Not affected
Vulnerability Srbds: Vulnerable: No microcode
Vulnerability Tsx async abort:   Not affected

$ uname -a
Linux bamboo 6.1.0-10-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.38-2 (2023-07-27) 
x86_64 GNU/Linux

$ sudo lshw
bamboo
description: Notebook
product: 23331U1 (LENOVO_MT_2333)
vendor: LENOVO
version: ThinkPad X230
serial: PK056K9
width: 64 bits
capabilities: smbios-2.7 dmi-2.7 smp vsyscall32
configuration: administrator_password=disabled chassis=notebook 
family=ThinkPad X230 power-on_password=disabled sku=LENOVO_MT_2333 
uuid=470dc001-5217-11cb-9533-a6ac2582edd3
  *-core
   description: Motherboard
   product: 23331U1
   vendor: LENOVO
   physical id: 0
   version: Not Defined
   serial: 1ZSSK37N2VP
   slot: Not Available
 *-cpu
  description: CPU
  product: Intel(R) Core(TM) i5-3320M CPU @ 2.60GHz
  vendor: Intel Corp.
  physical id: 1
  bus info: cpu@0
  version: 6.58.9
  serial: None
  slot: CPU Socket - U3E1
  size: 2019MHz
  capacity: 3300MHz
  width: 64 bits
  clock: 100MHz
  capabilities: lm fpu fpu_exception wp vme de pse tsc msr pae mce cx8 
apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht 
tm pbe syscall nx rdtscp x86-64 constant_tsc arch_perfmon pebs bts rep_good 
nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl 
vmx smx est tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic popcnt 
tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm cpuid_fault epb pti ssbd 
ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid fsgsbase smep erms 
xsaveopt dtherm ida arat pln pts md_clear flush_l1d cpufreq
  

Bug#1042563: installation-reports: installation OK, screen remains blank during boot and GDM Greeter

2023-07-30 Thread Axel Stammler
Package: installation-reports
Severity: important
X-Debbugs-Cc: a...@users.sourceforge.net

(Please provide enough information to help the Debian
maintainers evaluate the report efficiently - e.g., by filling
in the sections below.)

Everything work well _after_ I remove the computer from the docking station and 
put it
back.

- boots into visible Grub menu (including background picture)
- Grub works well
- kernel starts without any output (except that the screen is first grey = 
lit-up and
  turns totally dark a few seconds later)
- password prompt for encrypted disk (if used) is not visible but password can 
be entered
  blindly; password prompt and all other output becomes visible when computer 
is briefly
  removed from docking station
- GDM is started, Greeter screen remains invisible if computer has not been 
removed from
  station, becomes visible then
- Greeter screen is visible after logging out

Boot method: network
Image version: 
https://www.debian.org/releases/bookworm/amd64/ch05s01.en.html#boot-initrd
Date: 

Machine: Think Pad X 230 with docking station
Partitions: 


Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [O]
Detect network card:[O]
Configure network:  [O]
Detect media:   [O]
Load installer modules: [O]
Clock/timezone setup:   [O]
User/password setup:[O]
Detect hard drives: [O]
Partition hard drives:  [O]
Install base system:[O]
Install tasks:  [O]
Install boot loader:[O]
Overall install:[O]

Comments/Problems:

see above

Please make sure that any installation logs that you think would
be useful are attached to this report. (You can find them in the
installer system in /var/log/ and later on the installed system
under /var/log/installer.) Please compress large files using gzip.


-- Package-specific info:

==
Installer lsb-release:
==
DISTRIB_ID=Debian
DISTRIB_DESCRIPTION="Debian GNU/Linux installer"
DISTRIB_RELEASE="10 (buster) - installer build 20180430-00:04"
X_INSTALLATION_MEDIUM=cdrom

==
Installer hardware-summary:
==
uname -a: Linux bamboo-w 4.15.0-3-amd64 #1 SMP Debian 4.15.17-1 (2018-04-19) 
x86_64 GNU/Linux
lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation Atom Processor 
D4xx/D5xx/N4xx/N5xx DMI Bridge [8086:a010] (rev 02)
lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:83ac]
lspci -knn: 00:02.0 VGA compatible controller [0300]: Intel Corporation Atom 
Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics Controller [8086:a011] (rev 
02)
lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:83ac]
lspci -knn: 00:02.1 Display controller [0380]: Intel Corporation Atom Processor 
D4xx/D5xx/N4xx/N5xx Integrated Graphics Controller [8086:a012] (rev 02)
lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:83ac]
lspci -knn: 00:1b.0 Audio device [0403]: Intel Corporation NM10/ICH7 Family 
High Definition Audio Controller [8086:27d8] (rev 02)
lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:84d3]
lspci -knn: Kernel driver in use: snd_hda_intel
lspci -knn: Kernel modules: snd_hda_intel
lspci -knn: 00:1c.0 PCI bridge [0604]: Intel Corporation NM10/ICH7 Family PCI 
Express Port 1 [8086:27d0] (rev 02)
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:1c.1 PCI bridge [0604]: Intel Corporation NM10/ICH7 Family PCI 
Express Port 2 [8086:27d2] (rev 02)
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:1c.3 PCI bridge [0604]: Intel Corporation NM10/ICH7 Family PCI 
Express Port 4 [8086:27d6] (rev 02)
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:1d.0 USB controller [0c03]: Intel Corporation NM10/ICH7 Family 
USB UHCI Controller #1 [8086:27c8] (rev 02)
lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:83ad]
lspci -knn: Kernel driver in use: uhci_hcd
lspci -knn: Kernel modules: uhci_hcd
lspci -knn: 00:1d.1 USB controller [0c03]: Intel Corporation NM10/ICH7 Family 
USB UHCI Controller #2 [8086:27c9] (rev 02)
lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:83ad]
lspci -knn: Kernel driver in use: uhci_hcd
lspci -knn: Kernel modules: uhci_hcd
lspci -knn: 00:1d.2 USB controller [0c03]: Intel Corporation NM10/ICH7 Family 
USB UHCI Controller #3 [8086:27ca] (rev 02)
lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:83ad]
lspci -knn: Kernel driver in use: uhci_hcd
lspci -knn: Kernel modules: uhci_hcd
lspci -knn: 00:1d.3 USB controller [0c03]: Intel Corporation NM10/ICH7 Family 
USB UHCI Controller #4 [8086:27cb] (rev 02)
lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:83ad]
lspci -knn: Kernel driver in use: uhci_hcd
lspci -knn: Kernel modules: uhci_hcd
lspci -knn: 00:1d.7 USB controller [0c03]: Intel Corporation NM10/ICH7 F

Bug#1042503: linux-image-6.4.0-1-amd64: grafic performance regression with kernel 6.4

2023-07-29 Thread axel
Package: src:linux
Version: 6.4.4-1
Severity: important
X-Debbugs-Cc: at...@t-online.de

Dear Maintainer,
today kernel 6.4.4 entered testing and with this kernel the performance in
games for me is extremely low. I tested supraland, witcher 3 and d2r and get
less than 20 fps in all three games with my AMD RX 6600. If I boot kernel 6.3.7
everything is fine again and I get 60+ fps in those games.

Regards
Axel


-- Package-specific info:
** Version:
Linux version 6.4.0-1-amd64 (debian-ker...@lists.debian.org) (gcc-13 (Debian 
13.1.0-9) 13.1.0, GNU ld (GNU Binutils for Debian) 2.40.90.20230720) #1 SMP 
PREEMPT_DYNAMIC Debian 6.4.4-1 (2023-07-23)

** Command line:
BOOT_IMAGE=/vmlinuz-6.4.0-1-amd64 
root=UUID=c57fdd64-b119-4474-9f1c-39e9811d75bf ro quiet splash

** Not tainted

** Kernel log:
[   19.235329] systemd-journald[656]: 
/var/log/journal/7663e6adcfa04ffba5821731707b6777/user-1001.journal: Monotonic 
clock jumped backwards relative to last journal entry, rotating.
[   19.413455] NET: Registered PF_QIPCRTR protocol family
[   19.593424] r8169 :05:00.0: firmware: direct-loading firmware 
rtl_nic/rtl8125b-2.fw
[   19.624196] RTL8226B_RTL8221B 2.5Gbps PHY r8169-0-500:00: attached PHY 
driver (mii_bus:phy_addr=r8169-0-500:00, irq=MAC)
[   19.833023] r8169 :05:00.0 enp5s0: Link is Down
[   19.896786] bridge: filtering via arp/ip/ip6tables is no longer available by 
default. Update your scripts to load br_netfilter if you need this.
[   20.456190] r8169 :05:00.0: invalid VPD tag 0x00 (size 0) at offset 0; 
assume missing optional EEPROM
[   20.646975] memfd_create() without MFD_EXEC nor MFD_NOEXEC_SEAL, pid=1477 
'kvm'
[   23.800214] r8169 :05:00.0 enp5s0: Link is Up - 1Gbps/Full - flow 
control off
[   23.800226] IPv6: ADDRCONF(NETDEV_CHANGE): enp5s0: link becomes ready
[   83.732268] sr 9:0:0:0: [sr0] tag#17 FAILED Result: hostbyte=DID_OK 
driverbyte=DRIVER_OK cmd_age=0s
[   83.732273] sr 9:0:0:0: [sr0] tag#17 Sense Key : Not Ready [deferred] 
[   83.732275] sr 9:0:0:0: [sr0] tag#17 Add. Sense: Medium not present - tray 
closed
[   83.732276] sr 9:0:0:0: [sr0] tag#17 CDB: Read(10) 28 00 00 00 00 00 00 00 
08 00
[   83.732277] I/O error, dev sr0, sector 0 op 0x0:(READ) flags 0x80700 
phys_seg 3 prio class 2
[   83.732296] sr 9:0:0:0: [sr0] tag#18 unaligned transfer
[   83.732298] I/O error, dev sr0, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 
prio class 2
[   83.732301] Buffer I/O error on dev sr0, logical block 0, async page read
[   83.732309] sr 9:0:0:0: [sr0] tag#19 unaligned transfer
[   83.732310] I/O error, dev sr0, sector 1 op 0x0:(READ) flags 0x0 phys_seg 1 
prio class 2
[   83.732311] Buffer I/O error on dev sr0, logical block 1, async page read
[   83.732316] sr 9:0:0:0: [sr0] tag#20 unaligned transfer
[   83.732317] I/O error, dev sr0, sector 2 op 0x0:(READ) flags 0x0 phys_seg 1 
prio class 2
[   83.732318] Buffer I/O error on dev sr0, logical block 2, async page read
[   83.732321] sr 9:0:0:0: [sr0] tag#21 unaligned transfer
[   83.732322] I/O error, dev sr0, sector 3 op 0x0:(READ) flags 0x0 phys_seg 1 
prio class 2
[   83.732323] Buffer I/O error on dev sr0, logical block 3, async page read
[   83.732327] sr 9:0:0:0: [sr0] tag#22 unaligned transfer
[   83.732327] I/O error, dev sr0, sector 4 op 0x0:(READ) flags 0x0 phys_seg 1 
prio class 2
[   83.732328] Buffer I/O error on dev sr0, logical block 4, async page read
[   83.732332] sr 9:0:0:0: [sr0] tag#23 unaligned transfer
[   83.732332] I/O error, dev sr0, sector 5 op 0x0:(READ) flags 0x0 phys_seg 1 
prio class 2
[   83.732333] Buffer I/O error on dev sr0, logical block 5, async page read
[   83.732337] sr 9:0:0:0: [sr0] tag#24 unaligned transfer
[   83.732338] I/O error, dev sr0, sector 6 op 0x0:(READ) flags 0x0 phys_seg 1 
prio class 2
[   83.732339] Buffer I/O error on dev sr0, logical block 6, async page read
[   83.732343] sr 9:0:0:0: [sr0] tag#25 unaligned transfer
[   83.732343] I/O error, dev sr0, sector 7 op 0x0:(READ) flags 0x0 phys_seg 1 
prio class 2
[   83.732344] Buffer I/O error on dev sr0, logical block 7, async page read
[   87.373494] sr 9:0:0:0: [sr0] tag#29 FAILED Result: hostbyte=DID_OK 
driverbyte=DRIVER_OK cmd_age=0s
[   87.373499] sr 9:0:0:0: [sr0] tag#29 Sense Key : Not Ready [deferred] 
[   87.373501] sr 9:0:0:0: [sr0] tag#29 Add. Sense: Medium not present - tray 
closed
[   87.373502] sr 9:0:0:0: [sr0] tag#29 CDB: Read(10) 28 00 00 00 00 00 00 00 
08 00
[   87.373503] I/O error, dev sr0, sector 0 op 0x0:(READ) flags 0x80700 
phys_seg 3 prio class 2
[   87.373522] sr 9:0:0:0: [sr0] tag#30 unaligned transfer
[   87.373525] Buffer I/O error on dev sr0, logical block 0, async page read
[   87.373533] sr 9:0:0:0: [sr0] tag#0 unaligned transfer
[   87.373534] Buffer I/O error on dev sr0, logical block 1, async page read
[   87.373539] sr 9:0:0:0: [sr0] tag#1 unaligned transfer
[   87.373542] sr 9:0:0:0: [sr0] tag#2 unaligned transfer
[   87.373546] sr 9:0:0:0: [sr0] tag#3 unaligned transfer
[  

Bug#1042059: installation-reports: success

2023-07-25 Thread Axel Stammler
Package: installation-reports
Severity: normal
X-Debbugs-Cc: a...@users.sourceforge.net

(Please provide enough information to help the Debian
maintainers evaluate the report efficiently - e.g., by filling
in the sections below.)

Boot method: network
Image version: 
https://www.debian.org/releases/bookworm/amd64/ch05s01.en.html#boot-initrd
Date: 

Machine: Lenovo Think Pad X 230
Partitions: 
Filesystem Type 1K-blocks  Used Available Use% Mounted on
udev   devtmpfs   3878408 0   3878408   0% /dev
tmpfs  tmpfs   782380  1644780736   1% /run
/dev/sdd1  ext4   2808488127452   2518220   5% /
/dev/sdd6  ext4  19047080   4867716  13186496  27% /usr
tmpfs  tmpfs  3911880 0   3911880   0% /dev/shm
tmpfs  tmpfs 5120 8  5112   1% /run/lock
/dev/sdd5  ext4   1307744   228   1222832   1% /tmp
/dev/sdd9  ext4978972141860770040  16% /home
/dev/sdd7  ext4   4720160762808   3696900  18% /var
tmpfs  tmpfs   782376   148782228   1% /run/user/1001

Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [O]
Detect network card:[O]
Configure network:  [O]
Detect media:   [O]
Load installer modules: [O]
Clock/timezone setup:   [O]
User/password setup:[O]
Detect hard drives: [O]
Partition hard drives:  [O] SD card
Install base system:[O]
Install tasks:  [O]
Install boot loader:[O]
Overall install:[O]

Comments/Problems: boots & works correctly & very fast (on different machines, 
too), probably due to better firmware




Please make sure that any installation logs that you think would
be useful are attached to this report. (You can find them in the
installer system in /var/log/ and later on the installed system
under /var/log/installer.) Please compress large files using gzip.


-- Package-specific info:

==
Installer lsb-release:
==
DISTRIB_ID=Debian
DISTRIB_DESCRIPTION="Debian GNU/Linux installer"
DISTRIB_RELEASE="12 (bookworm) - installer build 20230607"
X_INSTALLATION_MEDIUM=netboot

==
Installer hardware-summary:
==
uname -a: Linux bookworm-sd 6.1.0-9-amd64 #1 SMP PREEMPT_DYNAMIC Debian 
6.1.27-1 (2023-05-08) x86_64 GNU/Linux
lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation 3rd Gen Core 
processor DRAM Controller [8086:0154] (rev 09)
lspci -knn: Subsystem: Lenovo Device [17aa:21fa]
lspci -knn: 00:02.0 VGA compatible controller [0300]: Intel Corporation 3rd Gen 
Core processor Graphics Controller [8086:0166] (rev 09)
lspci -knn: Subsystem: Lenovo Device [17aa:21fa]
lspci -knn: 00:14.0 USB controller [0c03]: Intel Corporation 7 Series/C210 
Series Chipset Family USB xHCI Host Controller [8086:1e31] (rev 04)
lspci -knn: Subsystem: Lenovo Device [17aa:21fa]
lspci -knn: Kernel driver in use: xhci_hcd
lspci -knn: Kernel modules: xhci_pci
lspci -knn: 00:16.0 Communication controller [0780]: Intel Corporation 7 
Series/C216 Chipset Family MEI Controller #1 [8086:1e3a] (rev 04)
lspci -knn: Subsystem: Lenovo Device [17aa:21fa]
lspci -knn: 00:16.3 Serial controller [0700]: Intel Corporation 7 Series/C210 
Series Chipset Family KT Controller [8086:1e3d] (rev 04)
lspci -knn: Subsystem: Lenovo Device [17aa:21fa]
lspci -knn: Kernel driver in use: serial
lspci -knn: 00:19.0 Ethernet controller [0200]: Intel Corporation 82579LM 
Gigabit Network Connection (Lewisville) [8086:1502] (rev 04)
lspci -knn: Subsystem: Lenovo Device [17aa:21f3]
lspci -knn: Kernel driver in use: e1000e
lspci -knn: Kernel modules: e1000e
lspci -knn: 00:1a.0 USB controller [0c03]: Intel Corporation 7 Series/C216 
Chipset Family USB Enhanced Host Controller #2 [8086:1e2d] (rev 04)
lspci -knn: Subsystem: Lenovo Device [17aa:21fa]
lspci -knn: Kernel driver in use: ehci-pci
lspci -knn: Kernel modules: ehci_pci
lspci -knn: 00:1b.0 Audio device [0403]: Intel Corporation 7 Series/C216 
Chipset Family High Definition Audio Controller [8086:1e20] (rev 04)
lspci -knn: Subsystem: Lenovo Device [17aa:21fa]
lspci -knn: 00:1c.0 PCI bridge [0604]: Intel Corporation 7 Series/C216 Chipset 
Family PCI Express Root Port 1 [8086:1e10] (rev c4)
lspci -knn: Subsystem: Lenovo Device [17aa:21fa]
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:1c.1 PCI bridge [0604]: Intel Corporation 7 Series/C210 Series 
Chipset Family PCI Express Root Port 2 [8086:1e12] (rev c4)
lspci -knn: Subsystem: Lenovo Device [17aa:21fa]
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:1c.2 PCI bridge [0604]: Intel Corporation 7 Series/C210 Series 
Chipset Family PCI Express Root Port 3 [8086:1e14] (rev c4)
lspci -knn: Subsystem: Lenovo Devic

Bug#1040841: texstudio: enable terminal build option

2023-07-17 Thread Axel Kittenberger
Hello Tom,
I'm very sorry, I overlooked that on this machine "which texstudio"
resulted in "/usr/local/bin/texstudio".
Some self compiled version at some point due to testing something back
then, which took preference. I removed that, started the
correct distribution one, and yes the terminal is there as designed.
Thank you very much, you can close this as taken care of with full
satisfaction.
- Axel

On Fri, Jul 14, 2023 at 9:11 PM Tom Jampen  wrote:

> tags 1040841 + unreproducible
> thanks
>
> Hi Axel
>
> I remember your email and I've found it in my archive, it's from Oct
> 2021. I checked my git commits and found that I've activated the
> terminal with the upload of version 3.0.4+ds-2 in Oct 2021[1]. The
> internal terminal is still working for me with the current version in
> Bookworm (4.3.1+ds-2).
>
> I see the additional "Terminal" tab next to "Message", "Log", "Preview"
> and "Search Results" (as it is shown in your github pull request). When
> I start TeXstudio with a clean config, the Terminal tab is there as
> well. Sorry, I can't reproduce this.
>
> You say the tab is not visible when you start TeXstudio? And you don't
> see the config options if you enable advanced options?
>
> Kind regards
> Tom
>
> [1]:
>
> https://tracker.debian.org/news/1267252/accepted-texstudio-304ds-2-source-into-unstable/
>


Bug#1041299: rawloader: multiple undeclared file conflicts

2023-07-17 Thread Axel Beckert
Hi!

Helmut Grohne wrote:
> rawloader contains multiple undeclared file conflicts
> 
> usr/bin/identify is contained in graphicsmagick-imagemagick-compat.

Please note that /usr/bin/identify is also included in
imagemagick-6.q16 and imagemagick-6.q16hdri and is handled by
update-alternatives by these two packages:

imagemagick-6.q16: /usr/bin/identify-im6.q16
imagemagick-6.q16hdri: /usr/bin/identify-im6.q16hdri

lrwxrwxrwx 1 root root 26 May  5  2017 /usr/bin/identify -> 
/etc/alternatives/identify*

So even though these do not directly ship this binary, a conflict
would be needed there, too, unless it is renamed.

    Regards, Axel
-- 
 ,''`.  |  Axel Beckert , https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE



Bug#1040841: texstudio: enable terminal build option

2023-07-11 Thread Axel Kittenberger
Package: texstudio
Version: 4.3.1+ds-2
Severity: wishlist

Dear Maintainer,

3 Years ago I wrote an integrated terminal for TeXStudio, (
https://github.com/texstudio-org/texstudio/pull/993 ), since then it has been
integreated into upstream, but please you need to enable it in build
configuration (its optional, as it is an Linux only thing).

OPTION_TERMINAL=yes build option.

I was already once disappointed not seeing been enable in bullseye, but was
promised it will be in bookworm (I don't find the communication anymore tough,
I believe it was personal email). However now upgraded to bookworm, I have to
find it again to not have been enabled.

Please, please, please enable it in debian build of the package, so after a few
more years I may finally get it into the default package.


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

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

Versions of packages texstudio depends on:
ii  libc62.36-9
ii  libgcc-s112.2.0-14
ii  libhunspell-1.7-01.7.1-1
ii  libphonon4qt5-4  4:4.11.1-4
ii  libpoppler-qt5-1 22.12.0-2+b1
ii  libqt5concurrent55.15.8+dfsg-11
ii  libqt5core5a 5.15.8+dfsg-11
ii  libqt5gui5   5.15.8+dfsg-11
ii  libqt5network5   5.15.8+dfsg-11
ii  libqt5printsupport5  5.15.8+dfsg-11
ii  libqt5qml5   5.15.8+dfsg-3
ii  libqt5svg5   5.15.8-3
ii  libqt5widgets5   5.15.8+dfsg-11
ii  libqt5xml5   5.15.8+dfsg-11
ii  libqtermwidget5-11.2.0-2
ii  libquazip5-1 0.9.1-3
ii  libstdc++6   12.2.0-14
ii  libx11-6 2:1.8.4-2+deb12u1
ii  phonon4qt5   4:4.11.1-4
ii  zlib1g   1:1.2.13.dfsg-1

Versions of packages texstudio recommends:
ii  adwaita-qt 1.4.2-3
ii  texlive-base   2022.20230122-3
ii  texlive-latex-base 2022.20230122-3
ii  texlive-latex-recommended  2022.20230122-3
ii  texstudio-doc  4.3.1+ds-2
ii  texstudio-l10n 4.3.1+ds-2

Versions of packages texstudio suggests:
ii  hunspell-de-at [hunspell-dictionary]  20161207-11
ii  hunspell-de-de [hunspell-dictionary]  20161207-11
ii  hunspell-en-us [hunspell-dictionary]  1:2020.12.07-2
ii  mythes-en-us [mythes-thesaurus]   1:7.5.0-1
ii  texlive-fonts-recommended 2022.20230122-3
ii  texlive-latex-extra   2022.20230122-4

-- no debconf information



Bug#1038203: iptables-netflow-dkms: module fails to build for Linux 6.4: error: implicit declaration of function 'register_sysctl_paths'

2023-07-05 Thread Axel Beckert
Control: forwarded -1 https://github.com/aabc/ipt-netflow/issues/220

Hi Andreas,

Andreas Beckmann wrote:
> /var/lib/dkms/ipt-netflow/2.6/build/ipt_NETFLOW.c: In function 
> 'ipt_netflow_init':
> /var/lib/dkms/ipt-netflow/2.6/build/ipt_NETFLOW.c:5688:33: error: implicit 
> declaration of function 'register_sysctl_paths'; did you mean 
> 'register_sysctl_table'? [-Werror=implicit-function-declaration]
>  5688 | netflow_sysctl_header = 
> register_sysctl_paths(netflow_sysctl_path, netflow_sysctl_table);

register_sysctl_paths has been removed from the kernel:
https://github.com/torvalds/linux/commit/0199849acd07d07e2a8e42757653ca8b14a122f5

Based on
https://github.com/kalamlacki/ipt-netflow/commit/2a1d250a701405b81fdf3548b4b9c12bf266a306
and
https://github.com/kalamlacki/ipt-netflow/commit/373b58781a0fc99fcb354ea3b5e4f3a006a71ab6
I've created a patch which does not hardcode the new variant but which
is backwards compatible. Will push and upload soon.

Thanks for the bug report.

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE



Bug#1033222: libgl1-mesa-dri: Segmentation fault with nouveau_dri.so

2023-07-03 Thread Axel Beckert
Hi Christophe,

Christophe Lohr wrote:
>   Xorg is carshing with a segfault:
> 
> (EE) Backtrace:
> (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x139) [0x55c365ce4cf9]
> (EE) 1: /lib/x86_64-linux-gnu/libc.so.6 (__sigaction+0x40) [0x7f00ef25af90]
> (EE) 2: /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so 
> (nouveau_drm_screen_create+0x4406c) [0x7f00ed75999c]
> (EE) 3: /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so 
> (nouveau_drm_screen_create+0x1e4c9) [0x7f00ed733df9]
> (EE) 4: /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so 
> (nouveau_drm_screen_create+0x266) [0x7f00ed715b96]
> (EE) unw_get_proc_name failed: no unwind info found [-10]
> ../..
> Fatal server error:
> (EE) Caught signal 11 (Segmentation fault). Server aborting
> 
> any workaround meantime? ;-)

I think I've run into the same or at least a very similar issue (see
https://bugs.debian.org/1040254, reported against
xserver-xorg-video-nouveau) and my fix was (unfortunately) to switch
from xserver-xorg-video-nouveau to the non-free binary-only driver
xserver-xorg-video-nvidia with nvidia-kernel-dkms.

(Using nvidia-open-kernel-dkms instead of nvidia-kernel-dkms did not
suffice for me as it had other issues, it made X show up on only one
screen and without any xrandr or nvidia-settings capabilities.)

HTH

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE



Bug#1025419: libunwind 1.6.2-2 upgrade makes xorg crash on startup

2023-07-03 Thread Axel Beckert
Hi,

Thomas Glanzmann wrote:
> the issue is already fixed upstream in libunwind.

And that fix seems to have been backported in 1.6.2-3 (now in stable,
testing and unstable), see https://bugs.debian.org/1026217

So this bug report likely can be closed as fixed in libunwind/1.6.2-3
or (force-) merged with #1026217. (But I'd like to have a second pair
of eyes agreeing that these two issues are indeed the same before
merging or closing.)

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE



Bug#1040254: xserver-xorg-video-nouveau: Regression: Crashes with "(EE) Caught signal 11 (Segmentation fault). Server aborting" upon start after dist-upgrade from Bullseye to Bookworm

2023-07-03 Thread Axel Beckert
Package: xserver-xorg-video-nouveau
Severity: grave
Version: 1:1.0.17-2

Dear Maintainer,

> What led up to the situation?

I've dist-upgraded a 7 years old HP workstation with an "NVIDIA
Corporation GM206 [GeForce GTX 960] (rev a1)" graphics card from Debian
11 to 12. It was previously working fine with the nouveau driver and
three screens attached.

After the dist-upgrade, X crashes immediately and reproducibly with
segfault upon start. Tried IIRC two times with wdm and once with
startx. The following log is from the last try with wdm _before_ using a
different driver:

X.Org X Server 1.21.1.7
X Protocol Version 11, Revision 0
Current Operating System: Linux emehari 6.1.0-9-amd64 #1 SMP PREEMPT_DYNAMIC 
Debian 6.1.27-1 (2023-05-08) x86_64
Kernel command line: BOOT_IMAGE=/boot/vmlinuz-6.1.0-9-amd64 
root=/dev/mapper/vgssd-root ro kaslr pti=on slab_nomerge page_poison=1 
slub_debug=FPZ
xorg-server 2:21.1.7-3 (https://www.debian.org/support)
Current version of pixman: 0.42.2
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Tue Jun 27 23:06:34 2023
(==) Using config directory: "/etc/X11/xorg.conf.d"
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
nvc0_screen_create:1072 - Base screen init failed: -19
(EE)
(EE) Backtrace:
(EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x139) [0x55dc10b2ad29]
(EE) 1: /lib/x86_64-linux-gnu/libc.so.6 (__sigaction+0x40) [0x7f895105af90]
(EE) 2: /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so 
(nouveau_drm_screen_create+0x4406c) [0x7f894f36c2fc]
(EE) 3: /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so 
(nouveau_drm_screen_create+0x1e4c9) [0x7f894f346759]
(EE) 4: /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so 
(nouveau_drm_screen_create+0x266) [0x7f894f3284f6]
(EE) unw_get_proc_name failed: no unwind info found [-10]
(EE) 5: /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so (?+0x0) [0x7f894eaaaf76]
(EE) 6: /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so 
(__driDriverGetExtensions_d3d12+0x61dab4) [0x7f894f0c8ff4]
(EE) 7: /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so 
(__driDriverGetExtensions_d3d12+0x1a93) [0x7f894eaacfd3]
(EE) 8: /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so 
(__driDriverGetExtensions_d3d12+0xa1a5) [0x7f894eab56e5]
(EE) 9: /usr/lib/x86_64-linux-gnu/libgbm.so.1 (gbm_format_get_name+0xf2e) 
[0x7f895079beae]
(EE) 10: /usr/lib/x86_64-linux-gnu/libgbm.so.1 (gbm_format_get_name+0x16f8) 
[0x7f895079c678]
(EE) unw_get_proc_name failed: no unwind info found [-10]
(EE) 11: /usr/lib/x86_64-linux-gnu/libgbm.so.1 (?+0x0) [0x7f895079a74c]
(EE) 12: /usr/lib/x86_64-linux-gnu/libgbm.so.1 (gbm_create_device+0x44) 
[0x7f895079a884]
(EE) 13: /usr/lib/xorg/modules/libglamoregl.so (glamor_egl_init+0x61) 
[0x7f89507d43c1]
(EE) unw_get_proc_name failed: no unwind info found [-10]
(EE) 14: /usr/lib/xorg/modules/drivers/modesetting_drv.so (?+0x0) 
[0x7f8951949733]
(EE) 15: /usr/lib/xorg/Xorg (InitOutput+0x952) [0x55dc109fa4c2]
(EE) 16: /usr/lib/xorg/Xorg (InitFonts+0x1ce) [0x55dc109bb4de]
(EE) 17: /lib/x86_64-linux-gnu/libc.so.6 (__libc_init_first+0x8a) 
[0x7f895104618a]
(EE) 18: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0x85) 
[0x7f8951046245]
(EE) 19: /usr/lib/xorg/Xorg (_start+0x21) [0x55dc109a4b71]
(EE)
(EE) Segmentation fault at address 0x20
(EE)
Fatal server error:
(EE) Caught signal 11 (Segmentation fault). Server aborting

Switching to xserver-xorg-video-nvidia with nvidia-kernel-dkms (but not
nvidia-open-kernel-source — which made X show up on only one screen
without any xrandr or nvidia-settings capabilities) fixed the
issue. Hence reporting this against the nouveau driver as replacing it
fixed the issue.

(Feel free to reassign this bug to e.g. xserver-xorg-core/2:21.1.7-3 or
libgl1-mesa-dri/22.3.6-1+deb12u1 or similar if you think the bug is
nevertheless rather in there.)

There was no xorg.conf besides the system-provided /etc/xorg.conf.d/*
files present. Now there is one needed due to the three-headed monkey,
eh three-headed screen setup.

So basically nouveau with that graphics card (and maybe my screen setup
which includes two rotated screens, see below) is impossible due to a
severe regression in (likely) the noveau driver.

I would have expected that I could just use the much preferred free
nouveau driver as with Bullseye.

Hardware is an "HP EliteDesk 800 G2 TWR" with an "NVIDIA Corporation
GM206 [GeForce GTX 960] (rev a1)" graphics card:

# lspci | fgrep VGA
01:00.0 VGA compatible controller: NVIDIA Corporation GM206 [GeForce GTX 960] 
(rev a1)

I can also reinstall xserver-xorg-video-nouveau if wanted to
e.g. provide an additional backtrace with gdb or strace the execution in
case that would offer more insight than the backtrace from Xorg.0.log
respectively syslog

Bug#1040197: elpa-ghub: Fails to upgrade from 3.5.6-1 to 3.6.0-2 due to dropped but still required dependency on elpa-treepy

2023-07-03 Thread Axel Beckert
Package: elpa-ghub
Version: 3.6.0-2
Severity: serious

Hi,

somewhere between elpa-ghub 3.5.6-1 and 3.6.0-2, it dropped the
dependency on elpa-treepy despite it still seems necessary.

It might be that this was some automatic thing as this change was not
mentioned in debian/changelog.

Here's a summary of the upgrade failure:

~ # egrep 'treepy|ghub' /var/log/apt/term.log
Preparing to unpack .../elpa-ghub_3.6.0-2_all.deb ...
Remove elpa-ghub for emacs
remove/ghub-0: Handling removal of emacsen flavor emacs
Unpacking elpa-ghub (3.6.0-2) over (3.5.6-1) ...
Removing elpa-treepy (0.1.2-2) ...
Remove elpa-treepy for emacs
remove/treepy-0.1.1: Handling removal of emacsen flavor emacs
Setting up elpa-ghub (3.6.0-2) ...
Install elpa-ghub for emacs
install/ghub-3.6.0: Handling install of emacsen flavor emacs
install/ghub-3.6.0: byte-compiling for emacs
buck.el:37:1: Error: Cannot open load file: No such file or directory, treepy
ghub-graphql.el:26:1: Error: Cannot open load file: No such file or directory, 
treepy
ghub.el:1012:1: Error: Cannot open load file: No such file or directory, treepy
glab.el:37:1: Error: Cannot open load file: No such file or directory, treepy
gogs.el:37:1: Error: Cannot open load file: No such file or directory, treepy
gtea.el:37:1: Error: Cannot open load file: No such file or directory, treepy
ERROR: install script from elpa-ghub package failed
dpkg: error processing package elpa-ghub (--configure):
 installed elpa-ghub package post-installation script subprocess returned error 
exit status 1
 elpa-ghub

-- System Information:
Debian Release: trixie/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (980, 'unstable-debug'), (600, 'testing'), 
(111, 'buildd-unstable'), (111, 'buildd-experimental'), (110, 'experimental'), 
(105, 'experimental-debug')
merged-usr: no
Architecture: amd64 (x86_64)

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

Versions of packages elpa-ghub depends on:
ii  dh-elpa-helper  2.0.16
ii  emacsen-common  3.0.5

Versions of packages elpa-ghub recommends:
ii  emacs  1:28.2+1-15
ii  emacs-gtk [emacs]  1:28.2+1-15

elpa-ghub suggests no packages.

-- no debconf information



Bug#999918: [Pkg-zsh-devel] Bug#999918: Bug#999918: Bug#999918: zsh: depends on obsolete pcre3 library

2023-07-01 Thread Axel Beckert
Hi Bastian,

Bastian Germann wrote:
> zsh builds without libpcre3-dev installed.

Yeah, I know. Did that before.

> Please consider dropping the dependency until the next version is
> released.

Nope. That's only my last resort.

    Regards, Axel
-- 
 ,''`.  |  Axel Beckert , https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE



Bug#1036933: screen-udeb: Should screen really be installed setgid utmp?

2023-06-26 Thread Axel Beckert
Hi,

Sven Joachim wrote:
> Recently I noticed that the screen program in the screen-udeb
> package is installed setgid utmp, and I wonder if this actually
> makes any sense.

I suspect that setgid utmp indeed is not needed the installer context
from a general viewpoint, but screen is rather picky about its
permissions, especially setgid and setuid. (See below.) So our
decision back then was based on the following:

Screen has two supported ways to edit /var/log/wtmp:

A) via setgid utmp
B) via libutempter

Because we didn't want to pull in another library (libutempter) into
the installer when we created screen-udeb (and hence adding the need
to provide a libutempter udeb as well as libutempter freezes before
installer releases, etc.), we decided continue to use (A) for the
screen-udeb while the remainder of the screen package switched from
(A) to (B).

> While I do not have much experience with the installer, I would expect
> it to run all programs as root anyway, so there should be no need for
> setgid there.

Good point. Then again, it shouldn't do any harm for the very same
reason, right?

Screen is particular picky about its and /run/screen's permissions and
it might refuse to work if they're not set to one of the supported
permission combinations. See /usr/share/doc/screen/README.Debian.gz

So changing them definitely needs some additional tests. In general,
I'd prefer to avoid that, especially in the udeb where it does no
harm.

> Having screen installed setgid sets up a secure execution environment
> that precludes the use of certain environment variables, see the
> "Secure-execution mode" section in ld.so(8).  Recently ncurses has also
> started to restrict such programs, see #1034372.

Thanks for that pointer, wasn't aware of that kind of feature. But I
fail to see how
https://invisible-island.net/ncurses/NEWS.html#index-t20230408 is
related.

https://invisible-island.net/ncurses/NEWS.html#index-t20230418 and
https://invisible-island.net/ncurses/NEWS.html#index-t20230423 look
more related, though. Maybe a typo in #1034372, 08 vs 18?

Anyway, IMHO ncurses should not care about setuid/setgid when already
called under root. It makes sense under any other user, though.

> Hopefully none of this matters much.  I have CC'ed debian-boot, as the
> people working on the installer will be much more qualified to give
> advice than I am.

Cyril Brulebois wrote:
> Given the first sentence of this last paragraph, it looks like we're not
> considering doing anything for Bookworm at this time

That's also the reason why I didn't reply back in May: We were way to
deep into the Bookworm freeze to do anything on that front IMHO. And
the installer just worked fine with regards to its screen usage.

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE



Bug#1005512: irqtop: Errors in man pages

2023-06-14 Thread Axel Beckert
Hi Helge,

thanks for the bug report!

Helge Kreutzmann wrote:
> Finally the issues I'm reporting have accumulated over time and are
> not always discovered by me, so sometimes my description of the
> problem my be a bit limited - do not hesitate to ask so we can clarify
> them.

Yeah, I think that's the place where things went a bit wrong.

> Man page: irqtop.1
> Issue:ethtool → B(8)

I'm sorry, but this is a groff-written man page, but your suggested
change seems POD syntax.

> "show extra eth stats (from ethtool)"

That line now renders in man like this:

"show extra eth stats (from B(8))"

I don't think that's wanted.

Besides we render htop(1) and friends under "SEE ALSO" also without
any special formatting.

So I'll make it simply "ethtool(8)".
  
> Man page: irqtop.1
> Issue:enouth → enough

"enouth" neither is nor ever was in this Debian package.

> "Show per-cpu statistics by specified mode. Available modes are: B, "
> "B, B. The default option B detects the width of "
> "window, then shows the per-cpu statistics if the width of window is large "
> "enouth to show a full line of statistics."

Neither is this text.

A quick search on codesearch.debian.net reveals that this is part of
the man page from the _other_ tool named irqtop, the one from
util-linux:
https://sources.debian.org/src/util-linux/2.38.1-5/sys-utils/irqtop.1.adoc/?hl=29#L29

Which is not yet shipped in a binary package in Debian as I didn't
manage to start the migration between the two irqtops timely before
the Bookworm freeze.

Please report that error against src:util-linux.

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE



Bug#1037264: bug#64058: [PATCH] wc: Fix crashes due to incomplete AVX2 enumeration

2023-06-14 Thread Axel Beckert
Control: tag 1037264 + patch

Hi Pádraig,

On Wed, Jun 14, 2023 at 11:46:58AM +0100, Pádraig Brady wrote:
> On 14/06/2023 05:14, Paul Eggert wrote:
> > Thanks for the bug report. I installed the attached patch into coreutils
> > on Savannah. It builds on your idea with several other changes:
> > 
> > * There's a similar issue with cksum.c and pclmul.
> > 
> > * configure.ac can be simplified, since it seems there's no point
> > compiling these instructions if __builtin_cpu_supports doesn't work.
> > 
> > * This lets us simplify the source code a bit more.
> > 
> > Please let me know if the attached patch works for you.
> 
> __builtin_cpu_supports() looks to have sufficient support in
> Arch + compiler versions for our needs, so that's good.
> 
> Paul you removed the "avx" check from cksum.c. Was that intended?
> 
> > PS. Does the attached cksum.c / pclmul change fix any user-visible
> > misbehavior? If so, what should we put into the NEWS file?
> 
> We have an illegal instruction issue with cksum under Xen DomU
> which may be related, as discussed at: https://bugs.debian.org/1037264
> 
> Axel does the attached patch change anything for you?

Yes! This patch helps! Thanks a lot! :-)

Cc'ing the Debian bug report again (and doing a nearly fullquote for
that) and tagging Debian's bug report as containing a patch. (Given
it's high bug report number it should do any harm in GNU's BTS even if
it uses the same control syntax…)

> diff --git a/src/cksum.c b/src/cksum.c
> index 85afab0ac..881d90413 100644
> --- a/src/cksum.c
> +++ b/src/cksum.c
> @@ -160,29 +160,16 @@ static bool
>  pclmul_supported (void)
>  {
>  # if USE_PCLMUL_CRC32
> -  unsigned int eax = 0;
> -  unsigned int ebx = 0;
> -  unsigned int ecx = 0;
> -  unsigned int edx = 0;
> -
> -  if (! __get_cpuid (1, &eax, &ebx, &ecx, &edx))
> -{
> -  if (cksum_debug)
> -error (0, 0, "%s", _("failed to get cpuid"));
> -  return false;
> -}
> -
> -  if (! (ecx & bit_PCLMUL) || ! (ecx & bit_AVX))
> -{
> -  if (cksum_debug)
> -error (0, 0, "%s", _("pclmul support not detected"));
> -  return false;
> -}
> +  bool pclmul_enabled = 0 < __builtin_cpu_supports ("pclmul")
> +&& 0 < __builtin_cpu_supports ("avx");
>  
>if (cksum_debug)
> -error (0, 0, "%s", _("using pclmul hardware support"));
> +error (0, 0, "%s",
> +   (pclmul_enabled
> +? _("using pclmul hardware support")
> +: _("pclmul support not detected")));
>  
> -  return true;
> +  return pclmul_enabled;
>  # else
>if (cksum_debug)
>  error (0, 0, "%s", _("using generic hardware support"));

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE



Bug#1037264: cksum crashes intermittently with "Illegal instruction" on some Xen DomU

2023-06-13 Thread Axel Beckert
Hi,

Pádraig Brady wrote:
> At this stage it would be good to get the output from `cpuid -1`

Ok, I've attached the output of "cpuid -1" from both affected DomUs
(the outputs slightly differ) as well as of the unaffected hosting
server (same CPU) for comparison.

cpuid-domu1.txt and cpuid-domu2.txt is the output on the two affected
DomUs (VMs) and cpuid-dom0.txt is the output on the (Debian 11) Xen
hosting server.

One more note: The Xen version running on the hosting server is
4.14.5+94-ge49571868d-1 (the one from Debian 11), in case that's of
interest.

HTH!

    Regards, Axel
-- 
 ,''`.  |  Axel Beckert , https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE


cpuid-domu1.txt.gz
Description: application/gzip


cpuid-domu2.txt.gz
Description: application/gzip


cpuid-dom0.txt.gz
Description: application/gzip


signature.asc
Description: PGP signature


Bug#1037264: cksum crashes intermittently with "Illegal instruction" on some Xen DomU

2023-06-13 Thread Axel Beckert
n
Illegal instruction
Illegal instruction
Illegal instruction
Illegal instruction
Illegal instruction
Illegal instruction
Illegal instruction
Illegal instruction
Illegal instruction
Illegal instruction
Illegal instruction
Illegal instruction
Illegal instruction
Illegal instruction
Illegal instruction
Illegal instruction
Illegal instruction
Illegal instruction
Illegal instruction
Illegal instruction
Illegal instruction
Illegal instruction
Illegal instruction
Illegal instruction
Illegal instruction
Illegal instruction
Illegal instruction
Illegal instruction
Illegal instruction
Illegal instruction
Illegal instruction
Illegal instruction
[…]

This intensity happens on that DomU with both, with and without the
patch and it doesn't seem to make a difference if e.g. debug symbols
are installed or not.

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE


signature.asc
Description: PGP signature


Bug#1037264: cksum crashes intermittently with "Illegal instruction" on some Xen DomU

2023-06-12 Thread Axel Beckert
Hi Kristoffer,

Kristoffer Brånemyr wrote:
> But I think it's a bit suspicious that it only crashes sometimes.If
> there was some instruction which causes this, should it not happen
> everytime?

Good point.

> Can you reproduce the problem running cksum in gdb?

Yes:

# dd if=/dev/urandom count=1 2> /dev/null | gdb -ex run -ex bt -batch cksum
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".

Program received signal SIGILL, Illegal instruction.
0x5556ccf5 in cksum_pclmul (fp=0x77faca80 <_IO_2_1_stdin_>, 
crc_out=0x7fffe8d0, length_out=0x7fffe8c8) at src/cksum_pclmul.c:59
59  src/cksum_pclmul.c: No such file or directory.
#0  0x5556ccf5 in cksum_pclmul (fp=0x77faca80 <_IO_2_1_stdin_>, 
crc_out=0x7fffe8d0, length_out=0x7fffe8c8) at src/cksum_pclmul.c:59
#1  0xabb0 in crc_sum_stream (stream=0x77faca80 
<_IO_2_1_stdin_>, resstream=0x7fffe9f0, length=0x7fffe9e8) at 
src/cksum.c:269
#2  0x7eaa in digest_file (filename=filename@entry=0x5556d14f 
"-", bin_result=bin_result@entry=0x7fffe9f0 '/' , "\377", 
missing=missing@entry=0x7fffe9e0, length=length@entry=0x7fffe9e8, 
binary=) at src/digest.c:945
#3  0x71c7 in main (argc=1, argv=) at 
src/digest.c:1504

Does this help?

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE



  1   2   3   4   5   6   7   8   9   10   >