Bug#1021857: llvm-14-dev: ClangConfig.cmake is still broken

[Pino Toscano]

Package: llvm-14-dev
Followup-For: Bug #1021857

Hi,

(sending properly again)

1:14.0.6-6 does some changes, however it does not fix all of it; this
is while trying to build qtcreator:

CMake Error at /usr/lib/llvm-14/lib/cmake/clang/ClangTargets.cmake:756 
(message):
  The imported target "diagtool" references the file

 "/usr/lib/llvm-14/bin/diagtool"

  but this file does not exist.  Possible reasons include:

  * The file was deleted, renamed, or moved to another location.

  * An install or uninstall procedure did not complete successfully.

  * The installation package was faulty and contained

 "/usr/lib/llvm-14/lib/cmake/clang/ClangTargets.cmake"

  but not all the files it references.

Call Stack (most recent call first):
  /usr/lib/cmake/clang-14/ClangConfig.cmake:19 (include)
  cmake/FindClang.cmake:1 (find_package)
  CMakeLists.txt:100 (find_package)

In practice, ClangTargets.cmake is still broken, as it tries to look for
tools.

I think that the "cmake-test" is incomplete, as it only tests the "LLVM"
cmake module and not the "Clang" one; adding a new check for
  find_package(Clang)
should help to make sure all the cmake bits are working as expected.

Thanks,
-- 
Pino

Bug#1021857: reopening 1021857

[Pino Toscano]

reopen 1021857 
thanks

1:14.0.6-6 does some changes, however it does not fix all of it; this
is while trying to build qtcreator:

CMake Error at /usr/lib/llvm-14/lib/cmake/clang/ClangTargets.cmake:756 
(message):
  The imported target "diagtool" references the file

 "/usr/lib/llvm-14/bin/diagtool"

  but this file does not exist.  Possible reasons include:

  * The file was deleted, renamed, or moved to another location.

  * An install or uninstall procedure did not complete successfully.

  * The installation package was faulty and contained

 "/usr/lib/llvm-14/lib/cmake/clang/ClangTargets.cmake"

  but not all the files it references.

Call Stack (most recent call first):
  /usr/lib/cmake/clang-14/ClangConfig.cmake:19 (include)
  cmake/FindClang.cmake:1 (find_package)
  CMakeLists.txt:100 (find_package)

Thanks,
-- 
Pino

Bug#1022567: xymon-client: ignore ramfs ro mounts

[Gürkan Myczko]

Package: xymon-client
Version: 4.3.30-1+b2
Severity: normal

Dear maintainer,

hostname:/etc/xymon/misc.d# cat mount-ro
#!/bin/sh

if egrep ' ro[, ]' /proc/mounts | egrep -v ' 
(iso9660|nfs4?|udf|cifs|smbfs|tmpfs|proc|sysfs|squashfs) ' ; then

exit 2
else
echo "No filesystems mounted read-only"
fi

Would it be possible to add ramfs to the list above to ignore reporting 
ramfs ro mounts?


Kind regards,

Bug#994151: yt-dlp: little script

[Andreas Tille]

Am Sun, Oct 23, 2022 at 10:57:29PM -0400 schrieb Andres Salomon:
> Thanks for the script! We still haven't seen a youtube-dl release and it's
> pretty clear the way that things are headed, so I've gone ahead and prepared
> the package for becoming replaced by yt-dlp:
> 
> https://salsa.debian.org/debian/youtube-dl/-/commits/master
> 
> Andreas & others, any thoughts/comments on this before I upload?

I'm perfectly fine whatever you educated people decide.  Just go
ahead.

Thanks a lot for caring for this
 
Andreas.

-- 
http://fam-tille.de

Bug#1022542: cruft: misc filter additions

[Alexandre Detiste]

Thank you very much.

Only commenting when there's something to comment,
the rest will be merged as-is.

Le dim. 23 oct. 2022 à 17:42, Christian Göttsche
 a écrit :
> II. appstream
>
> The shipped filter misses two entries:
>
> /var/cache/swcatalog
> /var/cache/swcatalog/cache

Ok I remember this one but did half the work:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009825

What about those ? Can I remove these ?
 /var/cache/app-info/gv
 /var/cache/app-info/gv/*.gvz
 /var/cache/app-info/xapian
 /var/cache/app-info/xapian/**

> III. fwupd
I wanted to give it a try anyway, thanks

> V. ingerman
I wrote a generic explain/ispell and removed the other languages.

> VII. llvm-15-runtime
>
> /var/lib/binfmts/llvm-15-runtime.binfmt

Packages with version in their name are a pain to follow...
this one would definitely benefit from providing it's own
definition in /usr/lib/cruft/filters-unex/

...but dh-cruft can't be used as-is for dynamic content,
but could be extended to replace the version number in it's output)

Greetings,

Bug#1019348: pidgin: after upgrading to libglib2.0-0, Pidgin crashes when I close a group chat

[Paul Wise]

Control: forwarded -1 https://issues.imfreedom.org/issue/PIDGIN-17702

On Sun, 2022-10-23 at 08:12 +0800, Paul Wise wrote:

> The person who made the patch will be filing an issue in the upstream
> Pidgin bug tracker and getting the patch included upstream.

The patch got sent to the Pidgin bug tracker linked above.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#1022566: fonts-mplus: upgrade of mplus leaves an old /usr/share/fonts/truetype/mplus behind

[Alexandre Detiste]

Package: fonts-mplus
Version: 063+git20221017+ds-1
Severity: normal

Hi,

After upgrade of mplus, I still have got old loose dir and cache file
from previous version:

/usr/share/fonts/truetype/mplus
/usr/share/fonts/truetype/mplus/.uuid

Please remove these files on upgrade.

This bug was found by the cruft-ng tool.

Thanks


-- System Information:
Debian Release: bookworm/sid
  APT prefers testing
  APT policy: (501, 'testing'), (450, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

-- no debconf information

Bug#1022291: hydrapaper: FTBFS: ModuleNotFoundError: No module named 'gi'

[Francisco M Neto]

Control:
reassign -1 blueprint-compiler
affects -1 + hydrapaper

--

Greetings,


looking into the build log, I find this:

> Traceback (most recent call last):
>   File "/usr/bin/blueprint-compiler", line 37, in 
> from blueprintcompiler import main
>   File "/usr/lib/python3/dist-packages/blueprintcompiler/main.py", 
line 25, in 

> from .lsp import LanguageServer
>   File "/usr/lib/python3/dist-packages/blueprintcompiler/lsp.py", 
line 24, in 

> from .completions import complete
>   File 
"/usr/lib/python3/dist-packages/blueprintcompiler/completions.py", line 
22, in 

> from . import gir, language
>   File "/usr/lib/python3/dist-packages/blueprintcompiler/gir.py", 
line 24, in 

> import gi # type: ignore
> ModuleNotFoundError: No module named 'gi'

Looks like blueprint-compiler tries to import gi but is unable to. 
hydrapaper Build-Depends on python3-gi (and blueprint-compiler for that 
matter). It seems that blueprint-compiler should depend on python3-gi to 
funcion properly since it imports it when it's called. It's a run 
dependency for blueprint-compiler, and not a build-dependency for 
hydrapaper.


I'm therefore reassigning to blueprint-compiler and tagging it as 
'affects'-ing hydrapaper.


Cheers,
Francisco

On 10/23/22 09:38, Lucas Nussbaum wrote:

Source: hydrapaper
Version: 3.3.1-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221023 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):

  debian/rules binary
dh binary --with python3
dh_update_autotools_config
dh_autoreconf
dh_auto_configure
cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 meson .. 
--wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc 
--localstatedir=/var --libdir=lib/x86_64-linux-gnu
The Meson build system
Version: 0.63.3
Source dir: /<>
Build dir: /<>/obj-x86_64-linux-gnu
Build type: native build
Project name: hydrapaper
Project version: 3.3.1
Host machine cpu family: x86_64
Host machine cpu: x86_64
Message: Looking for dependencies
Found pkg-config: /usr/bin/pkg-config (0.29.2)
Run-time dependency glib-2.0 found: YES 2.74.0
Run-time dependency gobject-introspection-1.0 found: YES 1.74.0
Run-time dependency gtk4 found: YES 4.8.1
Run-time dependency libadwaita-1 found: YES 1.2.0
Program python3 found: YES (/usr/bin/python3)
Run-time dependency dbus-1 found: YES 1.14.4
Message: Daemon Enabled: True
Configuring hydrapaperd using configuration
Configuring org.gabmus.hydrapaper.desktop.i18n.in using configuration
Program msgfmt found: YES (/usr/bin/msgfmt)
Configuring org.gabmus.hydrapaper.service using configuration
Configuring org.gabmus.hydrapaper.Daemon.service using configuration
Configuring org.gabmus.hydrapaperd.service using configuration
Configuring org.gabmus.hydrapaper.Daemon.desktop.i18n.in using configuration
Configuring org.gabmus.hydrapaper.gschema.xml using configuration
Program blueprint-compiler found: YES (/usr/bin/blueprint-compiler)
Configuring aboutdialog.ui using configuration
Found pkg-config: /usr/bin/pkg-config (0.29.2)
Program glib-compile-resources found: YES (/usr/bin/glib-compile-resources)
Program glib-compile-schemas found: YES (/usr/bin/glib-compile-schemas)
Program appstreamcli found: NO
Configuring hydrapaper using configuration
Message: Update translations
Program msginit found: YES (/usr/bin/msginit)
Program msgmerge found: YES (/usr/bin/msgmerge)
Program xgettext found: YES (/usr/bin/xgettext)
Program pandoc found: YES (/usr/bin/pandoc)
Message: Compiling man page from markdown to groff
WARNING: You should add the boolean check kwarg to the run_command call.
  It currently defaults to false,
  but it will default to true in future releases of meson.
  See also: https://github.com/mesonbuild/meson/issues/9300
Message: Man page compilation succeeded, installing
Build targets in project: 16

hydrapaper 3.3.1

   User defined options
 buildtype: plain
 libdir   : lib/x86_64-linux-gnu
 localstatedir: /var
 prefix   : /usr
 sysconfdir   : /etc
 wrap_mode: nodownload

Found ninja-1.11.1 at /usr/bin/ninja
dh_auto_build
cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 ninja -j8 -v
[1/12] /usr/bin/glib-compile-schemas --targetdir data ../data
No schema files found: doing nothing.
[2/12] /usr/bin/msgfmt ../po/es.po -o po/es/LC_MESSAGES/hydrapaper.mo
[3/12] /usr/bin/msgfmt ../po/de.po -o po/de/LC_MESSAGES/hydrapaper.mo
[4/12] /usr/bin/msgfmt ../po/it.po -o po/it/LC_MESSAGES/hydrapaper.mo
[5/12] /usr/bin/msgfmt ../po/pt_BR.po -o po/pt_BR/LC_MESSAGES/hydrapaper.mo
[6/12] /usr/bin/msgfmt ../po/sv.po -o po/sv/LC_MESSAGES/hydrapaper.mo
[7/12] /usr/bin/msgfmt ../po/ru.po -o po/ru/LC_MESSAGES/hydrapaper.mo
[8/12] /usr/bin/blueprin

Bug#994151: yt-dlp: little script

[Andres Salomon]

On Mon, 29 Aug 2022 19:09:45 -0400 (EDT) Unit 193  
wrote:
> On Mon, 01 Aug 2022 20:10:42 +0200 michel  
wrote:
> > I fleshed out the proposal a bit more. The simplest possibillity 
is to make symlinks, of both
> > the executable and module, to pretend they are youtube-dl and the 
module youyube_dl. This way,

> > also python programs that load the module could work.
> >
> > A little bit better is this little wraper. you link the exec and 
module to it.

> >
> > --
> > #!/usr/bin/python3
> >
> > import sys
> > from yt_dlp import *
> >
> > if __name__ == "__main__":
> >
> > args=sys.argv.copy()
> > args.pop(0)
> > args=['--compat-options','youtube-dl']+args
> >
> > main(args)
> > 
> >
> >

Thanks for the script! We still haven't seen a youtube-dl release and 
it's pretty clear the way that things are headed, so I've gone ahead 
and prepared the package for becoming replaced by yt-dlp:


https://salsa.debian.org/debian/youtube-dl/-/commits/master

Andreas & others, any thoughts/comments on this before I upload?

Thanks,
Andres

Bug#1022565: file: [regression] OpenPGP file MIME type reverted to application/octet-stream

[Paul Wise]

Package: file
Version: 1:5.41-4
Severity: important
Control: found -1 1:5.43-1

The detected MIME type of OpenPGP files is now application/octet-stream:

   $ file --mime-type /etc/apt/trusted.gpg.d/debian-archive-buster-stable.gpg
   /etc/apt/trusted.gpg.d/debian-archive-buster-stable.gpg: 
application/octet-stream

The detected MIME type of OpenPGP files in bullseye was application/pgp-keys:

   $ file --mime-type /etc/apt/trusted.gpg.d/debian-archive-buster-stable.gpg
   /etc/apt/trusted.gpg.d/debian-archive-buster-stable.gpg: application/pgp-keys

This is a regression in functionality that other packages rely on, e.g.
check-all-the-things passes application/pgp-keys files to hokey lint.

   $ file /etc/apt/trusted.gpg.d/debian-archive-buster-stable.gpg
   /etc/apt/trusted.gpg.d/debian-archive-buster-stable.gpg: OpenPGP Public Key 
Version 4, Created Tue Feb  5 20:38:40 2019, RSA (Encrypt or Sign, 4096 bits); 
User ID; Signature; OpenPGP Certificate

-- System Information:
Debian Release: bookworm/sid
  APT prefers testing-debug
  APT policy: (900, 'testing-debug'), (900, 'testing'), (800, 
'unstable-debug'), (800, 'unstable'), (790, 'buildd-unstable'), (700, 
'experimental-debug'), (700, 'experimental'), (690, 'buildd-experimental')
merged-usr: no
Architecture: amd64 (x86_64)

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

Versions of packages file depends on:
ii  libc6  2.35-3
ii  libmagic1  1:5.41-4

file recommends no packages.

file suggests no packages.

-- no debconf information

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#1022564: locale related segmentation fault

[Aleksi Suhonen]

Package: libc6
Version: 2.35-3
Severity: important

I ran into this issue while updating packages on a Debian/sid machine, 
and the install scripts for "ntpsec" and "tzdata" started failing with 
segfault. I couldn't find a way to reproduce it on that machine 
immediately. I started suspecting the machine might be failing.


But then I ran into the problem on another machine that runs "bird" 
routing daemon, as its control program "birdc" also started segfaulting, 
but started working if I set LC_ALL=C. Then I found I could also get the 
install scripts on the first machine to work with LC_ALL=C.


So, steps to reproduce:

root# apt-get install bird
root# LC_ALL=asdf birdc

I'm sure there's a way to reproduce it without installing new packages, 
but rather than trying to find one, I thought I'd report the problem as 
soon as possible, because it smells to me like there might be some 
overflow involved...


Best Regards,

--
Aleksi Suhonen

() ascii ribbon campaign
/\ support plain text e-mail

Bug#993755: libcrypt.so.1: cannot open shared object file when upgrading from Stretch to Sid

[Otto Kekäläinen]

There seems to be a lot of people hitting this:

* https://forums.debian.net/viewtopic.php?f=17=152419
* 
https://www.reddit.com/r/debian/comments/qcwpfr/sudo_is_completely_broken_after_i_accidentally/

Thus I am posting this to clarify things:

Release notes of Debian 11 (bullseye)
https://www.debian.org/releases/stable/amd64/release-notes/ch-upgrading.en.html#upgrade-to-debian-oldrelease

> 4.2.1. Upgrade to Debian 10 (buster)
> Direct upgrades from Debian releases older than 10 (buster) are not 
> supported. Display your Debian version with:
>   $ cat /etc/debian_version
> Please follow the instructions in the Release Notes for Debian 10 to upgrade 
> to Debian 10 first.

This means that people running Debian 9 (stretch) can't upgrade to
Debian 11 (bullseye). If they attempt to do so, they will run into
this libcrypt.1 issue.

Also people running Debian 10 (buster) can't upgrade to upcoming
Debian 12 (bookworm). . If they attempt to do so, they will also run
into this libcrypt.1 issue.


These are the steps I use in my CI scripts to automate upgrade from
Stretch to Sid or Buster to Sid:

.test-enable-sid-repos: 
  # Replace any old repos with just Sid
  - echo 'deb http://deb.debian.org/debian sid main' > /etc/apt/sources.list
  # Upgrade minimal stack first
  - apt-get update
  # Next step will fail on https://bugs.debian.org/993755
  #   /usr/bin/perl: error while loading shared libraries: libcrypt.so.1: cannot
  # open shared object file: No such file or directory
  #   dpkg: error processing package libc6:amd64 (--configure):
  - apt-get install -y apt || true
  # Apply workaround
  - cd $(mktemp -d)
  - apt -y download libcrypt1
  - dpkg-deb -x libcrypt1_*.deb .
  - cp -ra lib/* /lib/
  - find /lib/*/libcrypt.* -ls
  - apt -y --fix-broken install
  # Complete upgrade of minimal stack
  - apt-get install -y apt


Live example at
https://salsa.debian.org/mariadb-team/mariadb-server/-/merge_requests/22



$ cp -av lib/x86_64-linux-gnu/* /lib/x86_64-linux-gnu/
$ apt -y --fix-broken install

Bug#1022364: qutebrowser: FTBFS: dh_usrlocal: error: debian/qutebrowser/usr/local/bin/qutebrowser is not a directory

[Axel Beckert]

Control: tag -1 + pending

Hi again,

Axel Beckert wrote:
> > >dh_usrlocal -O--buildsystem=pybuild -O--link-doc=qutebrowser
> > > dh_usrlocal: error: debian/qutebrowser/usr/local/bin/qutebrowser is not a 
> > > directory
> 
> This is clearly the one which makes the build stop at the end.
> 
> Looks like something suddenly installs the qutebrowser binary _also_
> into /usr/local/bin/. I so far just have no idea yet what or why.
> 
> Actually the following override in debian/rules would fix it and the
> resulting .deb has no debdiff to 2.5.2-1 as in unstable/testing, but
> I'd first like to understand what actually goes wrong instead of
> fixing symptoms:
> 
>   override_dh_usrlocal:
>   rm -rvf debian/qutebrowser/usr/local/

I'm quite sure the culprit lies hidden somewhere in an
python3-setuptools upstream release between probably 65.3.0 (seems to
have worked for the past 5 weeks unless Lucas' rebuilds happen more
seldom, in which case 59.6.0 would be the last known working version)
and 65.5.0 (clearly broken, installs qutebrowser and only that file
into /usr/bin/ _and_ /usr/local/bin/).

Since the upstream changelog is rather terse about potential huge
changes like e.g. …

* #3576: Updated version of ``validate_pyproject``.
* #3617: Merge with pypa/distutils@6852b20 including fix for
  pypa/distutils#181.

… I have no idea which of the changes actually could have triggered
this issue.

So I'm going with the above mentioned hardball fix.

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#1022540: build-essential: please add riscv64 support

[Paul Wise]

Control: tags -1 - ftbfs

On Sun, 2022-10-23 at 22:48 +0800, Bo YU wrote:

> Subject: Bug#1022540: build-essential: please add riscv64 support
> Tags: ftbfs, patch

Since this is not a build failure, the ftbfs tag should not be added.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#1022175: tup: FTBFS on riscv64

[Paul Wise]

On Fri, 2022-10-21 at 12:46 +, JunYuan Tan wrote:

> There is a merged upstream patch [1] that fixes this issue for riscv64.

I think this is the wrong approach, since it means that every new arch
that comes along needs to add a string for itself and the list of
strings grows longer and longer even though tup doesn't actually do
anything differently on arches except x86_64, other than pass along the
architecture string to the Tupfiles it runs.

If there is a standard define for the current architecture string
defined by GCC/clang, then the code should use that, so that the right
architecture string will be present by default on all distros.

If there is not, then debian/rules should pass $(DEB_HOST_GNU_TYPE) to
the CONFIG_TUP_ARCH field in the tup.config file in dh_auto_configure.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#1019624: UPSONIC IRT-3K 2U broken by length checking in blazer_usb/nutdrv_qx

[Trent W. Buck]

On Fri 21 Oct 2022 21:35:18 +0200, Laurent Bigonville wrote:
> On Tue, 13 Sep 2022 10:19:24 +1000 "Trent W. Buck" 
> wrote:
> Hello,
> >
> > Short version:
> >
> > 1. UPSONIC IRT-3K 2U speaks a variant of Q1 which omits final \r.
> > 2. nut 2.4 doesn't check for final \r, so it Just Works.
> > 3. nut 2.7 checks for final \r, cannot talk to my UPS.
> > 4. I fixed #3 but it's not very good.
> 
> Do you think you could check whether nut 2.8.0 (currently in unstable) works
> with your UPS?

That UPS is currently in production, so I can't easily mess with it.
I also do not have a spare.

However, I did find this which looks like the same bug:

https://github.com/networkupstools/nut/issues/441
https://github.com/zykh/nut/commit/1595a06501daa93e06035a861e3db7ccab2871dd

I don't know how I missed this earlier.

> Otherwise if the bug is still happening, could you please open a bug
> upstream if it's not already done?

I'm happy enough to mark this as done in sid.
When Debian 12 ships, if I run into this again, I'll reopen it.

I added a comment upstream:

https://github.com/networkupstools/nut/issues/441#issuecomment-1288238345

Bug#1022343: [Pkg-pascal-devel] Bug#1022343: view3dscene: FTBFS: view3dscene.lpr(63, 17) Fatal: Can't find unit CastleCubeMaps used by view3dscene

[Michalis Kamburelis]

The new CGE (Castle Game Engine) indeed broke compatibility in this
regard: the unit has been renamed
CastleCubeMaps->CastleInternalCubeMaps . There are likely other small
incompatibilities -- view3dscene in general "exercises" a lot of
obscure CGE API (where we don't care much about backward compat,
because we predict almost nobody except view3dscene is using
something), and upgrading view3dscene and CGE usually have to be done
together.

In this case, view3dscene 4.2.0, which was released along with CGE,
contains a fixed (and generally better) view3dscene version. See

- 
https://castle-engine.io/wp/2022/09/12/castle-game-engine-7-0-alpha-2-release-many-new-components-lights-primitives-fonts-sound-new-cameras-terrains-sprite-sheet-editor-delphi/
,
- https://github.com/castle-engine/castle-engine/releases/tag/v7.0-alpha.2 ,
- https://github.com/castle-engine/view3dscene/releases/tag/v4.2.0 .

So my preferred way to solve this would be to just have view3dscene
4.2.0 in Debian.

Regards,
Michalis

niedz., 23 paź 2022 o 15:15 Lucas Nussbaum  napisał(a):
>
> Source: view3dscene
> Version: 4.0.0-3
> Severity: serious
> Justification: FTBFS
> Tags: bookworm sid ftbfs
> User: lu...@debian.org
> Usertags: ftbfs-20221023 ftbfs-bookworm
>
> Hi,
>
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
>
>
> Relevant part (hopefully):
> > make[3]: Entering directory '/<>/embedded_data/screen_effects'
> > file_to_pascal_string flashlight.glsl screen_effects_flashlight.glsl.inc
> > file_to_pascal_string edge_detect.glsl screen_effects_edge_detect.glsl.inc
> > make[3]: Leaving directory '/<>/embedded_data/screen_effects'
> > make[2]: Leaving directory '/<>'
> > fpc -k"-z relro -z now" -dRELEASE -Mobjfpc -Sh -Ci -Sm -Sc -Sg -Si -O2 -Xs 
> > -Fu/usr/lib/x86_64-linux-gnu/fpc/3.2.2/units/castle-game-engine  
> > code/view3dscene.lpr
> > Compiling Release Version
> > Free Pascal Compiler version 3.2.2+dfsg-15 [2022/08/20] for x86_64
> > Copyright (c) 1993-2021 by Florian Klaempfl and others
> > Target OS: Linux for x86-64
> > Compiling code/view3dscene.lpr
> > view3dscene.lpr(60,21) Warning: Unit "CastleProgress" is deprecated: "use 
> > TUIState and WaitForRenderAndCall to display progress of loading operations"
> > view3dscene.lpr(63,17) Fatal: Can't find unit CastleCubeMaps used by 
> > view3dscene
> > Fatal: Compilation aborted
> > Error: /usr/bin/ppcx64 returned an error exitcode
> > make[1]: *** [debian/rules:53: override_dh_auto_build-arch] Error 1
>
>
> The full build log is available from:
> http://qa-logs.debian.net/2022/10/23/view3dscene_4.0.0-3_unstable.log
>
> All bugs filed during this archive rebuild are listed at:
> https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20221023;users=lu...@debian.org
> or:
> https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20221023=lu...@debian.org=1=1=1=1#results
>
> A list of current common problems and possible solutions is available at
> http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
>
> If you reassign this bug to another package, please marking it as 
> 'affects'-ing
> this package. See https://www.debian.org/Bugs/server-control#affects
>
> If you fail to reproduce this, please provide a build log and diff it with 
> mine
> so that we can identify if something relevant changed in the meantime.
>
> ___
> Pkg-pascal-devel mailing list
> pkg-pascal-de...@alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-pascal-devel

Bug#1022563: perl: FTBFS on hurd-i386: op/stat.t fails

[Samuel Thibault]

Package: perl
Version: 5.36.0-4
Severity: normal

Hello,

On hurd-i386, op/stat.t fails like this:

not ok 36 - ls and -b agreeing on /dev (0 310)
# Failed test 36 - ls and -b agreeing on /dev (0 310) at op/stat.t line 323
#  got "0"
# expected "310"
# = before
# total 68340
# lrwxr-xr-x 1 root root   13 Oct 23 17:56 MAKEDEV -> /sbin/MAKEDEV
# -rw-r- 1 root root0 Nov 24  2019 cd0
# -rw-r- 1 root root0 Nov 24  2019 cd1
# -rw--- 1 root root0 Nov 24  2019 com0
# -rw--- 1 root root0 Nov 24  2019 com1
# -rw--- 1 root root0 Nov 24  2019 com2
# -rw--- 1 root root0 Nov 24  2019 com3
etc.

The issue is that nowadays ls doesn't manage to see that entries are
block or character devices any more. This is because it now passes
AT_NO_AUTOMOUNT to its statx call, thus preventing from actually asking
translators whether they are character or block devices (O_NOTRANS, see
glibc's 13710e7e6af6c8965cc9a63a0660cb4ce1966557).

We have the same kind of issue with e.g.

stat /dev/null

because the stat tool also passes AT_NO_AUTOMOUNT nowadays.

I'm really not sure what to do about this, since there is technically
no difference between the null translator sitting on /dev/null and
a translator configured on /net/foobar. At best we could have an
xattr that we could set on /dev/ entries, to distinguish between
AT_NO_AUTOMOUNT and O_NOTRANS.

Samuel

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

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

Versions of packages perl depends on:
ii  dpkg   1.21.9+b1
ii  libperl5.345.34.0-5
ii  perl-base  5.34.0-5
ii  perl-modules-5.34  5.34.0-5

Versions of packages perl recommends:
ii  netbase  6.4

Versions of packages perl suggests:
pn  libtap-harness-archive-perl  
ii  libterm-readline-gnu-perl1.43-1
ii  make 4.3-4.1
ii  perl-doc 5.34.0-5

-- no debconf information

-- 
Samuel
---
Pour une évaluation indépendante, transparente et rigoureuse !
Je soutiens la Commission d'Évaluation de l'Inria.

Bug#1021925: prometheus-openstack-exporter: diff for NMU version 0.1.4-2.2

[Raúl Benencia]

Control: tags 1021925 + patch
Control: tags 1021925 + pending


Dear maintainer,

I've prepared an NMU for prometheus-openstack-exporter (versioned as 
0.1.4-2.2). The diff
is attached to this message.

I require a sponsor to have it uploaded.

Best wishes,
-- 
Raúl Benencia
diff -Nru prometheus-openstack-exporter-0.1.4/debian/changelog prometheus-openstack-exporter-0.1.4/debian/changelog
--- prometheus-openstack-exporter-0.1.4/debian/changelog	2022-10-15 03:39:55.0 -0700
+++ prometheus-openstack-exporter-0.1.4/debian/changelog	2022-10-23 15:30:50.0 -0700
@@ -1,3 +1,10 @@
+prometheus-openstack-exporter (0.1.4-2.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Disable setuptools package automatic discovery (Closes: #1021925)
+
+ -- Raúl Benencia   Sun, 23 Oct 2022 15:30:50 -0700
+
 prometheus-openstack-exporter (0.1.4-2.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru prometheus-openstack-exporter-0.1.4/debian/patches/disable-package-autodiscovery.patch prometheus-openstack-exporter-0.1.4/debian/patches/disable-package-autodiscovery.patch
--- prometheus-openstack-exporter-0.1.4/debian/patches/disable-package-autodiscovery.patch	1969-12-31 16:00:00.0 -0800
+++ prometheus-openstack-exporter-0.1.4/debian/patches/disable-package-autodiscovery.patch	2022-10-23 15:30:50.0 -0700
@@ -0,0 +1,32 @@
+From: Raúl Benencia 
+Date: Sat, 22 Oct 2022 11:17:24 -0700
+X-Dgit-Generated: 0.1.4-2.1 d12f61eaa20032eb3b7aa86269b355eebd10f6c4
+Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021925
+Forwarded: https://github.com/canonical/prometheus-openstack-exporter/pull/122
+Subject: Disable package autodiscovery
+
+Due to a change in setuptools>v61, package autodiscovery causes Debian
+builds to fail with:
+
+  error: Multiple top-level packages discovered in a flat-layout: ['snap', 'debian'].
+
+This can be fixed by disabling package autodiscovery. More information
+in:
+
+- https://setuptools.pypa.io/en/latest/history.html#v61-0-0
+- https://github.com/pypa/setuptools/issues/3227
+
+---
+
+diff --git a/setup.py b/setup.py
+index 3f42480..0b14083 100644
+--- a/setup.py
 b/setup.py
+@@ -15,6 +15,7 @@ setup(
+ keywords=["prometheus", "openstack", "exporter"],
+ url="https://github.com/CanonicalLtd/prometheus-openstack-exporter;,
+ scripts=["prometheus-openstack-exporter"],
++packages=[],
+ install_requires=[
+ "prometheus_client",
+ "python-keystoneclient<=3.10.0",
diff -Nru prometheus-openstack-exporter-0.1.4/debian/patches/series prometheus-openstack-exporter-0.1.4/debian/patches/series
--- prometheus-openstack-exporter-0.1.4/debian/patches/series	2022-10-15 03:39:55.0 -0700
+++ prometheus-openstack-exporter-0.1.4/debian/patches/series	2022-10-23 15:30:50.0 -0700
@@ -1 +1,2 @@
 python3-shebang.patch
+disable-package-autodiscovery.patch


signature.asc
Description: PGP signature

Bug#1022562: ftp.debian.org: lintian autorejects: add duplicate-contact

[Paul Wise]

Package: ftp.debian.org
Severity: wishlist
User: ftp.debian@packages.debian.org
Usertags: lintian

The packages emitting the lintian tag duplicate-contact results in the
Debian QA services maintainers getting cron mails (for eg see #1022259).

In order to avoid the cron spam and the need to file a bug and have a
new upload in order to stop the cron spam, it would be nice if the
lintian tag duplicate-contact could be added to the autoreject list.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#1022561: ftp.debian.org: lintian autorejects: add no-phrase

[Paul Wise]

Package: ftp.debian.org
Severity: wishlist
User: ftp.debian@packages.debian.org
Usertags: lintian

The packages emitting the lintian tag no-phrase results in the Debian
QA services maintainers getting cron mails (for eg see #1022102).

In order to avoid the cron spam and the need to file a bug and have a
new upload in order to stop the cron spam, it would be nice if the
lintian tag no-phrase could be added to the autoreject list.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#1022533: foot: pending patches

[Andrea Pappacoda]

Hi Birger, I've submitted the aforementioned patch to Salsa, together 
with a bigger one that enables profile-guided optimizations and makes 
foot provide x-terminal-emulator. It'd be great if you could review, 
and possibly accept them :)


You can find the two merge requests here:
https://salsa.debian.org/birger/foot/-/merge_requests/3
https://salsa.debian.org/birger/foot/-/merge_requests/4

Thanks for you work on the foot package!

--
OpenPGP key: 66DE F152 8299 0C21 99EF  A801 A8A1 28A8 AB1C EE49

Bug#1022352: lua-mode: FTBFS: tests failed

[Hilko Bengen]

FTBFS confirmed with elpa-buttercup/1.26-{1,2,3}, tests work just fine
using elpa-buttercup/1.24-1.

Bug#1022544: linux-image-6.0.0-2-amd64: No more sound after upgrade to 6.0.0-2

[Daniel Serpell]

Hi Again.

This is in kernel bugzilla now:
   https://bugzilla.kernel.org/show_bug.cgi?id=216613

Regards,
Daniel.

Bug#1022544: linux-image-6.0.0-2-amd64: No more sound after upgrade to 6.0.0-2

[Daniel Serpell]

Hi!

On Sun, 23 Oct 2022 23:24:46 +0200 Diederik de Haas
 wrote:
>
> On Sunday, 23 October 2022 19:01:52 CEST pdorm...@free.fr wrote:
> > After upgrade from 6.0.0-1 to 6.0.0-2, I don't have sound anymore.
> > I believe that the relevant dmesg message is this one, as it is not printed
> > with the 6.0.0-1 version:
> >
> > snd_hda_codec_hdmi ehdaudio0D2: failed to create hda codec -12
> > snd_hda_codec_hdmi ehdaudio0D2: ASoC: error at snd_soc_component_probe on
> > ehdaudio0D2: -12 skl_hda_dsp_generic skl_hda_dsp_generic: ASoC: failed to
> > instantiate card -12 skl_hda_dsp_generic: probe of skl_hda_dsp_generic
> > failed with error -12
> >
> > git bisect indicates that the bad commit is:
> > [7494e2e6c55ed192f2b91c821fd6832744ba8741] ALSA: hda: Fix page fault in
> > snd_hda_codec_shutdown()
>
> Thanks for that wonderful analyses!
>
> Both you and Lisandro had "sof-audio-pci-intel-tgl" in dmesg, but I don't.
> Lisandro also has the firmware-intel-sound package installed (but not you).
> Sound on my system works with 6.0.0-2, so the 'intel' part looks relevant.
>

I have the same bug. In the meantime, I can get sound by disabling SOF, adding
"snd-intel-dspcfg.dsp_driver=1" to the kernel command line, but with no mic
support.

My audio device is Intel tigerlake:
$ lspci | grep audio
00:1f.3 Multimedia audio controller: Intel Corporation Tiger Lake-LP
Smart Sound Technology Audio Controller (rev 20)

And I also have the firmware installed:
$ dpkg -l | grep 'firmware-intel-sound\|linux-image-6'
ii  firmware-intel-sound
20210818-1 all  Binary firmware
for Intel sound DSPs
ii  linux-image-6.0.0-2-amd64
6.0.3-1amd64Linux 6.0 for
64-bit PCs (signed)

Regards,
Daniel.

Bug#1016814: libqt5gui5:amd64: Conditional jump or move depends on uninitialised value(s)

[Dmitry Shachnev]

Hi Thorsten!

On Sun, Aug 07, 2022 at 10:37:45PM +0200, Thorsten Glaser wrote:
> Package: libqt5gui5
> Version: 5.15.2+dfsg-9
> Severity: normal
> X-Debbugs-Cc: t...@mirbsd.de
> 
> Running a Qt application (musescore3) against Valgrind shows:
> 
> ==27770== Conditional jump or move depends on uninitialised value(s)
> ==27770==at 0x7470A2E: __vfprintf_internal (vfprintf-internal.c:1687)
> ==27770==by 0x74839C5: __vsnprintf_internal (vsnprintf.c:114)
> ==27770==by 0x7511D30: __snprintf_chk (snprintf_chk.c:38)
> ==27770==by 0xB50DA79: ??? (in 
> /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5.15.2)
> ==27770==by 0xB50F232: ??? (in 
> /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5.15.2)
> ==27770==by 0xB50FC92: ??? (in 
> /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5.15.2)
> ==27770==by 0xB50A403: 
> QXcbConnection::QXcbConnection(QXcbNativeInterface*, bool, unsigned int, char 
> const*) (in /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5.15.2)
> ==27770==by 0xB50D112: QXcbIntegration::QXcbIntegration(QStringList 
> const&, int&, char**) (in /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5.15.2)
> ==27770==by 0x485346E: ??? (in 
> /usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqxcb.so)
> ==27770==by 0x67438FB: 
> QGuiApplicationPrivate::createPlatformIntegration() (in 
> /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5.15.2)
> ==27770==by 0x6744D4F: QGuiApplicationPrivate::createEventDispatcher() 
> (in /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5.15.2)
> ==27770==by 0x6F86A55: QCoreApplicationPrivate::init() (in 
> /usr/lib/x86_64-linux-gnu/libQt5Core.so.5.15.2)
> ==27770==  Uninitialised value was created by a stack allocation
> ==27770==at 0xB50E7A0: ??? (in 
> /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5.15.2)
> 
> I don’t always see this. In this example, $DISPLAY points to Xtightvnc
> from tightvncserver (= 1:1.3.10-3).

Does it still happen with the latest version of Qt (5.15.6)?

If yes, can you please install libqt5gui5-dbgsym and generate a new
stacktrace?

--
Dmitry Shachnev


signature.asc
Description: PGP signature

Bug#1022544: linux-image-6.0.0-2-amd64: No more sound after upgrade to 6.0.0-2

[Diederik de Haas]

Control: tag -1 upstream

On Sunday, 23 October 2022 19:01:52 CEST pdorm...@free.fr wrote:
> After upgrade from 6.0.0-1 to 6.0.0-2, I don't have sound anymore.
> I believe that the relevant dmesg message is this one, as it is not printed
> with the 6.0.0-1 version:
> 
> snd_hda_codec_hdmi ehdaudio0D2: failed to create hda codec -12
> snd_hda_codec_hdmi ehdaudio0D2: ASoC: error at snd_soc_component_probe on
> ehdaudio0D2: -12 skl_hda_dsp_generic skl_hda_dsp_generic: ASoC: failed to
> instantiate card -12 skl_hda_dsp_generic: probe of skl_hda_dsp_generic
> failed with error -12
> 
> git bisect indicates that the bad commit is:
> [7494e2e6c55ed192f2b91c821fd6832744ba8741] ALSA: hda: Fix page fault in
> snd_hda_codec_shutdown()

Thanks for that wonderful analyses!

Both you and Lisandro had "sof-audio-pci-intel-tgl" in dmesg, but I don't.
Lisandro also has the firmware-intel-sound package installed (but not you).
Sound on my system works with 6.0.0-2, so the 'intel' part looks relevant.

Could you report it upstream by replying to the thread linked in that commit:
https://lore.kernel.org/all/20220816111727.3218543-7-cezary.rojew...@intel.com/

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

Bug#1022560: libx11: CVE-2022-3554

[Moritz Mühlenhoff]

Source: libx11
X-Debbugs-CC: t...@security.debian.org
Severity: important
Tags: security

Hi,

The following vulnerability was published for libx11.

CVE-2022-3554[0]:
| A vulnerability has been found in X.org libX11 and classified as
| problematic. This vulnerability affects the function
| _XimRegisterIMInstantiateCallback of the file
| modules/im/ximcp/imsClbk.c. The manipulation leads to memory leak. It
| is recommended to apply a patch to fix this issue. VDB-211054 is the
| identifier assigned to this vulnerability.

https://gitlab.freedesktop.org/xorg/lib/libx11/commit/1d11822601fd24a396b354fa616b04ed3df8b4ef

If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2022-3554
https://www.cve.org/CVERecord?id=CVE-2022-3554

Please adjust the affected versions in the BTS as needed.

Bug#1022559: Acknowledgement (firmware-misc-nonfree: With firmware-misc-nonfree instaled, system crashes (complete freeze/lockup) every few minutes)

[Rui Dinis]

Hi.

 

Here is some aditional information.

 

I have a Nvidia Zotac 1080TI mini. With firmware-misc-nonfree installed,
system crashes (complete freeze/lockup, no errors on screen) every few
minutes/hours, and the only solution is a reset. Without
firmware-misc-nonfree, never crashes.

 

The package version of firmware-misc-nonfree is 20210818-1

 

I'm using 4 screens connected to my Nvidia Graphic Card, and I'm with KDE
Plasma.

 

Without the package firmware-misc-nonfree installed, the systems throws this
errors, but it never crashes:

# journalctl -b | grep firmware

Oct 23 20:08:23 Blackbeard kernel: nouveau :01:00.0: firmware: failed to
load nvidia/gp102/nvdec/scrubber.bin (-2)

Oct 23 20:08:23 Blackbeard kernel: nouveau :01:00.0: firmware: failed to
load nvidia/gp102/acr/bl.bin (-2)

Oct 23 20:08:23 Blackbeard kernel: nouveau :01:00.0: firmware: failed to
load nvidia/gp102/acr/bl.bin (-2)

Oct 23 20:08:23 Blackbeard kernel: nouveau :01:00.0: acr: firmware
unavailable

Oct 23 20:08:23 Blackbeard kernel: nouveau :01:00.0: pmu: firmware
unavailable

Oct 23 20:08:23 Blackbeard kernel: nouveau :01:00.0: gr: firmware
unavailable

Oct 23 20:08:23 Blackbeard kernel: nouveau :01:00.0: sec2: firmware
unavailable

 

# inxi -G

Graphics:

  Device-1: NVIDIA GP102 [GeForce GTX 1080 Ti] driver: nouveau v: kernel

  Device-2: Microdia Camera type: USB driver: snd-usb-audio,uvcvideo

  Display: x11 server: X.Org v: 1.21.1.4 driver: X: loaded: modesetting

unloaded: fbdev,vesa dri: swrast gpu: nouveau resolution: 1:
1920x1080~60Hz

2: 1920x1080~60Hz 3: 1920x1080~60Hz 4: 1920x1080~60Hz

 OpenGL: renderer: llvmpipe (LLVM 14.0.6 256 bits) v: 4.5 Mesa 22.2.0

 

$ glxinfo|egrep "OpenGL vendor|OpenGL renderer"

OpenGL vendor string: Mesa/X.org

OpenGL renderer string: llvmpipe (LLVM 14.0.6, 256 bits)

 

$ lspci | grep -i "nvidia"

01:00.0 VGA compatible controller: NVIDIA Corporation GP102 [GeForce GTX
1080 Ti] (rev a1)

01:00.1 Audio device: NVIDIA Corporation GP102 HDMI Audio Controller (rev
a1)

 

Thanks.

 

Regards

 

 

 

 

Thank you for filing a new Bug report with Debian.

 

You can follow progress on this Bug here: 1022559:

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

 

This is an automatically generated reply to let you know your message has
been received.

 

Your message is being forwarded to the package maintainers and other
interested parties for their attention; they will reply in due course.

 

Your message has been sent to the package maintainer(s):

Debian Kernel Team < 
debian-ker...@lists.debian.org>

 

If you wish to submit further information on this problem, please send it to
 1022...@bugs.debian.org.

 

Please do not send mail to  
ow...@bugs.debian.org unless you wish to report a problem with the
Bug-tracking system.

 

--

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

Debian Bug Tracking System

Contact   ow...@bugs.debian.org with problems

 

Bug#1022199: apt: certificate verification fails after adding custom root certificates through ca-certificates

[Julian Andres Klode]

Control: reassign -1 gnutls
Control: affects -1 apt

apt just calls gnutls_certificate_set_x509_system_trust() and
gnutls_set_default_priority() so this should not be our issue.

On Fri, Oct 21, 2022 at 10:05:45PM +0200, Marc Riudalbas Clemente wrote:
> Package: apt
> Version: 2.5.3+b1
> Severity: important
> X-Debbugs-Cc: marc.riudalbas.cleme...@aiticon.com
> 
> Dear Maintainer,
> 
> *** What led up to the situation?
> 
> We need to install CA certificates to our servers so we can access to
> services which are running with certificates singed by our CA. If we
> dont, we can not use them. Example:
> 
> $ docker login dockerregistry.aiticon.net
> Username: ait-docker
> Password:
> Error response from daemon: Get "https://dockerregistry.aiticon.net/v2/":
> x509: certificate signed by unknown authority
> 
> After installing custom root certificates through ca-certificates, apt
> complains about other certificates (when pulling packages through https
> sources.lists):
> 
> This is what we have done so far:
> 
> * We installed our CA and its intermediate in a fresh Vanilla-Bullseye
> this way:
> 
> * Create our own directory to store CA and intermediate:
> $ sudo mkdir -p /usr/share/ca-certificates/aiticon.net
> 
> * saved the certificates files under the created folder:
> $ cat <<_EOF_ |sudo tee 
> /usr/share/ca-certificates/aiticon.net/Aiticon_Trust_PKI_intermediate_east.crt
> -BEGIN CERTIFICATE-
> X
> -END CERTIFICATE-
> 
> * Did the same for the following files
> /usr/share/ca-certificates/aiticon.net/Aiticon_Trust_PKI_root.crt
> /usr/share/ca-certificates/aiticon.net/Aiticon_Trust_PKI_intermediate_west.crt
> /usr/share/ca-certificates/aiticon.net/Aiticon_Trust_PKI_intermediate_east.crt
> 
> * The certificates are there:
> $ ls -lh
> total 12K
> -rw-r--r-- 1 root root 2,1K 18. Okt 13:46
> Aiticon_Trust_PKI_intermediate_east.crt
> -rw-r--r-- 1 root root 2,1K 18. Okt 13:45
> Aiticon_Trust_PKI_intermediate_west.crt
> -rw-r--r-- 1 root root 2,1K 18. Okt 13:45 Aiticon_Trust_PKI_root.crt
> 
> * Added the following lines in /etc/ca-certificates.conf
> $ cat <<_EOF_ |sudo tee --append /etc/ca-certificates.conf
> aiticon.net/Aiticon_Trust_PKI_root.crt
> aiticon.net/Aiticon_Trust_PKI_intermediate_west.crt
> aiticon.net/Aiticon_Trust_PKI_intermediate_east.crt
> _EOF_
> 
> * Updated the CA Certificates:
> $ sudo update-ca-certificates
> Updating certificates in /etc/ssl/certs...
> 3 added, 0 removed; done.
> Running hooks in /etc/ca-certificates/update.d...
> done.
> 
> * After doing this, we can successfully use our services with the
> installed signed certificates:
> 
> * Restart the docker service so it notices the are new CAs in the system
> $ sudo systemctl restart docker
> 
> * Try docker login again
> $ docker login dockerregistry.aiticon.net
> Username: ait-docker
> Password:
> WARNING! Your password will be stored unencrypted in
> /home/aiticon/.docker/config.json.
> Configure a credential helper to remove this warning. See
> https://docs.docker.com/engine/reference/commandline/login/#credentials-store
> 
> Login Succeeded
> 
> * And now, when executing a simple apt-get update, the certificate
> verification for other https lists fail. THIS HAPPENS WITH ALL sources.list,
> not only with docker (this is only an example):
> $ sudo apt update
> Err:3 https://download.docker.com/linux/debian bullseye InRelease
>   Certificate verification failed: The certificate is NOT trusted. The
> certificate issuer is unknown.  Could not handshake: Error in the
> certificate verification. [IP: 13.225.78.127 443]
> 
> 
> *** What exactly did you do (or not do) that was effective (or
> innefective)?
> 
> * Deleting again the CAs from /etc/ca-certificates.conf and running
> update-ca-certificates again leads to the situation from the
> beggining:
> 
> - apt works propperly, even with https source lists
> - we cant use our services, because the CA is not known in the system
> 
> *** What outcome did you expect instead?
> 
> * We expected to be able to use all our services running with our CA,
> because we installed the CA in our system.
> * We expected that the command apt update updates the package lists
> correctly.
> 
> -- Package-specific info:
> 
> -- apt-config dump --
> 
> APT "";
> APT::Architecture "amd64";
> APT::Build-Essential "";
> APT::Build-Essential:: "build-essential";
> APT::Install-Recommends "1";
> APT::Install-Suggests "0";
> APT::Sandbox "";
> APT::Sandbox::User "_apt";
> APT::Authentication "";
> APT::Authentication::TrustCDROM "true";
> APT::NeverAutoRemove "";
> APT::NeverAutoRemove:: "^firmware-linux.*";
> APT::NeverAutoRemove:: "^linux-firmware$";
> APT::NeverAutoRemove:: "^linux-image-[a-z0-9]*$";
> APT::NeverAutoRemove:: "^linux-image-[a-z0-9]*-[a-z0-9]*$";
> APT::VersionedKernelPackages "";
> APT::VersionedKernelPackages:: "linux-.*";
> APT::VersionedKernelPackages:: "kfreebsd-.*";
> APT::VersionedKernelPackages:: "gnumach-.*";
> APT::VersionedKernelPackages:: ".*-modules";
> 

Bug#991767: samba: Attempt to change password over IPv6 using kpasswd fails on AD DC server

[Andrew Bartlett]

Given that Debian 11 Bullseye has 4.13.13 now I think this can be
closed as fixed.

Bug#1022559: firmware-misc-nonfree: With firmware-misc-nonfree instaled, system crashes (complete freeze/lockup) every few minutes

[the.wingmanx]

Package: firmware-misc-nonfree
Version: 20210818-1
Severity: important

Dear Maintainer,

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

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

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


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

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

Bug#1022558: linux-image-6.0.0-2-amd64: Audio fails to start, but works with 5.19

[Lisandro Damián Nicanor Pérez Meyer]

Package: src:linux
Version: 6.0.3-1
Severity: important
X-Debbugs-Cc: lisan...@debian.org

>From dmesg (see below) audio stack fails to be initialized. If I boot
with 5.19 everything works as expected.

[   36.646398] sof-audio-pci-intel-tgl :00:1f.3: DSP detected with PCI 
class/subclass/prog-if info 0x040100
[   36.647271] sof-audio-pci-intel-tgl :00:1f.3: Digital mics found on 
Skylake+ platform, using SOF driver
[   36.648298] sof-audio-pci-intel-tgl :00:1f.3: DSP detected with PCI 
class/subclass/prog-if 0x040100
[   36.649675] sof-audio-pci-intel-tgl :00:1f.3: bound :00:02.0 (ops 
i915_audio_component_bind_ops [i915])
[   36.657376] sof-audio-pci-intel-tgl :00:1f.3: use msi interrupt mode
[   36.748803] sof-audio-pci-intel-tgl :00:1f.3: hda codecs found, mask 5
[   36.749759] sof-audio-pci-intel-tgl :00:1f.3: using HDA machine driver 
skl_hda_dsp_generic now
[   36.750527] sof-audio-pci-intel-tgl :00:1f.3: DMICs detected in NHLT 
tables: 2
[   36.766188] sof-audio-pci-intel-tgl :00:1f.3: firmware: direct-loading 
firmware intel/sof/sof-tgl.ri
[   36.766847] sof-audio-pci-intel-tgl :00:1f.3: Firmware info: version 
2:2:0-57864
[   36.767532] sof-audio-pci-intel-tgl :00:1f.3: Firmware: ABI 3:22:1 
Kernel ABI 3:23:0
[   36.768229] sof-audio-pci-intel-tgl :00:1f.3: unknown sof_ext_man header 
type 3 size 0x30
[   36.862793] sof-audio-pci-intel-tgl :00:1f.3: Firmware info: version 
2:2:0-57864
[   36.863749] sof-audio-pci-intel-tgl :00:1f.3: Firmware: ABI 3:22:1 
Kernel ABI 3:23:0
[   36.872189] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[   36.873133] Bluetooth: BNEP filters: protocol multicast
[   36.874082] Bluetooth: BNEP socket layer initialized
[   36.884360] sof-audio-pci-intel-tgl :00:1f.3: firmware: direct-loading 
firmware intel/sof-tplg/sof-hda-generic-2ch.tplg
[   36.885264] sof-audio-pci-intel-tgl :00:1f.3: Topology: ABI 3:22:1 
Kernel ABI 3:23:0
[   36.886343] skl_hda_dsp_generic skl_hda_dsp_generic: ASoC: Parent card not 
yet available, widget card binding deferred
[   36.891799] snd_hda_codec_hdmi ehdaudio0D2: failed to create hda codec -12
[   36.891867] snd_hda_codec_hdmi ehdaudio0D2: ASoC: error at 
snd_soc_component_probe on ehdaudio0D2: -12
[   36.891891] skl_hda_dsp_generic skl_hda_dsp_generic: ASoC: failed to 
instantiate card -12
[   36.895650] skl_hda_dsp_generic: probe of skl_hda_dsp_generic failed with 
error -12




-- Package-specific info:
** Version:
Linux version 6.0.0-2-amd64 (debian-ker...@lists.debian.org) (gcc-12 (Debian 
12.2.0-7) 12.2.0, GNU ld (GNU Binutils for Debian) 2.39) #1 SMP PREEMPT_DYNAMIC 
Debian 6.0.3-1 (2022-10-21)

** Command line:
BOOT_IMAGE=/vmlinuz-6.0.0-2-amd64 root=/dev/mapper/minerva--vg-root ro

** Not tainted

** Kernel log:
[   26.051482] Bluetooth: hci0: Boot Address: 0x24800
[   26.052488] Bluetooth: hci0: Firmware Version: 191-21.21
[   26.068068] r8169 :04:00.0: firmware: failed to load 
rtl_nic/rtl8168h-2.fw (-2)
[   26.068075] r8169 :04:00.0: firmware: failed to load 
rtl_nic/rtl8168h-2.fw (-2)
[   26.068076] r8169 :04:00.0: Direct firmware load for 
rtl_nic/rtl8168h-2.fw failed with error -2
[   26.068077] r8169 :04:00.0: Unable to load firmware 
rtl_nic/rtl8168h-2.fw (-2)
[   26.099450] Generic FE-GE Realtek PHY r8169-0-400:00: attached PHY driver 
(mii_bus:phy_addr=r8169-0-400:00, irq=MAC)
[   26.128618] iwlwifi :00:14.3: Detected Intel(R) Wi-Fi 6 AX201 160MHz, 
REV=0x351
[   26.129680] thermal thermal_zone6: failed to read out thermal zone (-61)
[   26.137587] NET: Registered PF_QIPCRTR protocol family
[   26.198974] Lockdown: Xorg: raw io port access is restricted; see man 
kernel_lockdown.7
[   26.206278] intel_rapl_msr: PL4 support detected.
[   26.206388] intel_rapl_common: Found RAPL domain package
[   26.206392] intel_rapl_common: Found RAPL domain core
[   26.206393] intel_rapl_common: Found RAPL domain uncore
[   26.231534] r8169 :04:00.0 enp4s0: Link is Down
[   26.276143] mei_hdcp :00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: 
bound :00:02.0 (ops i915_hdcp_component_ops [i915])
[   26.343929] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[   26.343935] Bluetooth: BNEP filters: protocol multicast
[   26.343939] Bluetooth: BNEP socket layer initialized
[   26.346280] sof-audio-pci-intel-tgl :00:1f.3: DSP detected with PCI 
class/subclass/prog-if info 0x040100
[   26.346356] sof-audio-pci-intel-tgl :00:1f.3: Digital mics found on 
Skylake+ platform, using SOF driver
[   26.346539] sof-audio-pci-intel-tgl :00:1f.3: DSP detected with PCI 
class/subclass/prog-if 0x040100
[   26.346601] sof-audio-pci-intel-tgl :00:1f.3: bound :00:02.0 (ops 
i915_audio_component_bind_ops [i915])
[   26.353468] sof-audio-pci-intel-tgl :00:1f.3: use msi interrupt mode
[   26.354006] iwlwifi :00:14.3: Detected RF HR B5, rfid=0x10a100
[   26.419178] iwlwifi :00:14.3: base HW address: 54:14:f3:d2:89:fd
[   26.425788] 

Bug#1022253: swi-prolog breaks logol autopkgtest on s390x

[olivier sallou]

Le dim. 23 oct. 2022, 19:21, Lev Lamberov  a écrit :

> Hi Paul,
>
> Вс 23 окт 2022 @ 10:10 Paul Gevers :
>
> > Hi Lev,
> >
> > On 23-10-2022 09:40, Lev Lamberov wrote:
> >> I'm not sure it is the solution, it needs testing. The change in
> >> swi-prolog concerns pre-compiled prolog source code, when there is no
> >> pre-complied prolog code rebuilt is not needed. SWI-Prolog supports
> >> three different kinds of pre-compilation, at least one of them was
> >> affected and another was not. The mentioned endiannes bug can be found
> >> in BTS, #1006818 [bts].
> >
> > I just ran the autopkgtest with a rebuild logol on s390x, see below.
> > Does that help?
> >
> > @logol maintainers, those ERRORs look scary if the test passes with it.
> > Is that just noise, or are real problems ignored?
>

Errors are "permission denied" related.

Default package config expects to write in different dirs (temp and results
dir), owned by root. If logol is to be executed as non root, a different
config file should be used, specifying user writable directories.




> Given the answer from Étienne looks like it *is* the solution. Thanks
> for your work on it!
>
> Cheers!
> Lev
>
>

Bug#1021884: libical3 bug was responsible

[ael]

Sorry, I should have closed this bug.

The problem was caused by a regression in libical3:
see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021698

Mind you, korganizer should not have dumped core...

ael

Bug#833287: A proper fix for Samba plugins linking against other libraries is upstream

[Andrew Bartlett]

https://bugzilla.samba.org/show_bug.cgi?id=14780 has the correct fix
for this, and this change landed in Samba 4.16.

This is a much harder bug to solve properly than it looks, but once
solved properly we should have proper static plugins that won't fail
during upgrades as they will be self-contained.

Andrew,
-- 
Andrew Bartlett (he/him)https://samba.org/~abartlet/
Samba Team Member (since 2001)  https://samba.org
Samba Developer, Catalyst IThttps://catalyst.net.nz/services/samba

Bug#1022557: shapelib: CVE-2022-0699

[Moritz Mühlenhoff]

Source: shapelib
X-Debbugs-CC: t...@security.debian.org
Severity: important
Tags: security

Hi,

The following vulnerability was published for shapelib.

CVE-2022-0699[0]:
| A double-free condition exists in contrib/shpsort.c of shapelib 1.5.0
| and older releases. This issue may allow an attacker to cause a denial
| of service or have other unspecified impact via control over malloc.

https://github.com/OSGeo/shapelib/issues/39
https://github.com/OSGeo/shapelib/commit/c75b9281a5b9452d92e1682bdfe6019a13ed819f

If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2022-0699
https://www.cve.org/CVERecord?id=CVE-2022-0699

Please adjust the affected versions in the BTS as needed.

Bug#1022556: exim4: CVE-2022-3620

[Moritz Mühlenhoff]

Source: exim4
X-Debbugs-CC: t...@security.debian.org
Severity: important
Tags: security

Hi,

The following vulnerability was published for exim4.

CVE-2022-3620[0]:
| A vulnerability was found in Exim and classified as problematic. This
| issue affects the function dmarc_dns_lookup of the file dmarc.c of the
| component DMARC Handler. The manipulation leads to use after free. The
| attack may be initiated remotely. The name of the patch is
| 12fb3842f81bcbd4a4519d5728f2d7e0e3ca1445. It is recommended to apply a
| patch to fix this issue. The associated identifier of this
| vulnerability is VDB-211919.

Introduced by: 
https://git.exim.org/exim.git/commit/92583637b25b6bde926f9ca6be7b085e5ac8b1e6 
(exim-4.95-RC0)
(as such Bullseye/Buster are not affected)

Fixed by: 
https://git.exim.org/exim.git/commit/12fb3842f81bcbd4a4519d5728f2d7e0e3ca1445

If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2022-3620
https://www.cve.org/CVERecord?id=CVE-2022-3620

Please adjust the affected versions in the BTS as needed.

Bug#1022555: tiff: CVE-2022-3627 CVE-2022-3626 CVE-2022-3599 CVE-2022-3598 CVE-2022-3597 CVE-2022-3570

[Moritz Mühlenhoff]

Source: tiff
X-Debbugs-CC: t...@security.debian.org
Severity: grave
Tags: security

Hi,

The following vulnerabilities were published for tiff.

CVE-2022-3627[0]:
| LibTIFF 4.4.0 has an out-of-bounds write in _TIFFmemcpy in
| libtiff/tif_unix.c:346 when called from extractImageSection,
| tools/tiffcrop.c:6860, allowing attackers to cause a denial-of-service
| via a crafted tiff file. For users that compile libtiff from sources,
| the fix is available with commit 236b7191.

https://gitlab.com/libtiff/libtiff/-/commit/236b7191f04c60d09ee836ae13b50f812c841047
https://gitlab.com/libtiff/libtiff/-/issues/411

CVE-2022-3626[1]:
| LibTIFF 4.4.0 has an out-of-bounds write in _TIFFmemset in
| libtiff/tif_unix.c:340 when called from processCropSelections,
| tools/tiffcrop.c:7619, allowing attackers to cause a denial-of-service
| via a crafted tiff file. For users that compile libtiff from sources,
| the fix is available with commit 236b7191.

https://gitlab.com/libtiff/libtiff/-/commit/236b7191f04c60d09ee836ae13b50f812c841047
https://gitlab.com/libtiff/libtiff/-/issues/426

CVE-2022-3599[2]:
| LibTIFF 4.4.0 has an out-of-bounds read in writeSingleSection in
| tools/tiffcrop.c:7345, allowing attackers to cause a denial-of-service
| via a crafted tiff file. For users that compile libtiff from sources,
| the fix is available with commit e8131125.

https://gitlab.com/libtiff/libtiff/-/commit/e813112545942107551433d61afd16ac094ff246
https://gitlab.com/libtiff/libtiff/-/issues/398

CVE-2022-3598[3]:
| LibTIFF 4.4.0 has an out-of-bounds write in
| extractContigSamplesShifted24bits in tools/tiffcrop.c:3604, allowing
| attackers to cause a denial-of-service via a crafted tiff file. For
| users that compile libtiff from sources, the fix is available with
| commit cfbb883b.

https://gitlab.com/libtiff/libtiff/-/commit/cfbb883bf6ea7bedcb04177cc4e52d304522fdff
https://gitlab.com/libtiff/libtiff/-/issues/435

CVE-2022-3597[4]:
| LibTIFF 4.4.0 has an out-of-bounds write in _TIFFmemcpy in
| libtiff/tif_unix.c:346 when called from extractImageSection,
| tools/tiffcrop.c:6826, allowing attackers to cause a denial-of-service
| via a crafted tiff file. For users that compile libtiff from sources,
| the fix is available with commit 236b7191.

https://gitlab.com/libtiff/libtiff/-/commit/236b7191f04c60d09ee836ae13b50f812c841047
https://gitlab.com/libtiff/libtiff/-/issues/413

CVE-2022-3570[5]:
| Multiple heap buffer overflows in tiffcrop.c utility in libtiff
| library Version 4.4.0 allows attacker to trigger unsafe or out of
| bounds memory access via crafted TIFF image file which could result
| into application crash, potential information disclosure or any other
| context-dependent impact

https://gitlab.com/libtiff/libtiff/-/commit/bd94a9b383d8755a27b5a1bc27660b8ad10b094c
https://gitlab.com/libtiff/libtiff/-/issues/381
https://gitlab.com/libtiff/libtiff/-/issues/386

If you fix the vulnerabilities please also make sure to include the
CVE (Common Vulnerabilities & Exposures) ids in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2022-3627
https://www.cve.org/CVERecord?id=CVE-2022-3627
[1] https://security-tracker.debian.org/tracker/CVE-2022-3626
https://www.cve.org/CVERecord?id=CVE-2022-3626
[2] https://security-tracker.debian.org/tracker/CVE-2022-3599
https://www.cve.org/CVERecord?id=CVE-2022-3599
[3] https://security-tracker.debian.org/tracker/CVE-2022-3598
https://www.cve.org/CVERecord?id=CVE-2022-3598
[4] https://security-tracker.debian.org/tracker/CVE-2022-3597
https://www.cve.org/CVERecord?id=CVE-2022-3597
[5] https://security-tracker.debian.org/tracker/CVE-2022-3570
https://www.cve.org/CVERecord?id=CVE-2022-3570

Please adjust the affected versions in the BTS as needed.

Bug#1022551: llvm-15's cmake now requires clang-tools-15, clang-tidy-15, clangd-15, even if unused

[Sylvestre Ledru]

Le 23/10/2022 à 20:39, Matthias Klose a écrit :

Package: src:llvm-toolchain-15
Version: 15.0.3-1
Severity: important
Tags: sid bookworm

llvm-15's cmake support now requires clang-tools-15, clang-tidy-15, 
clangd-15, even if unused. These checks should be optional.


seen when building cvise-2.6.0-1 with LLVM 15


it is fixed in experimental

Cheers

S

Bug#1021884: korganizer segfaults when adding new event

[Patrick Franz]

Hi,

does this happen for all types of calendars or only specific ones ?


-- 
Med vänliga hälsningar

Patrick Franz

Bug#1022173: Update (tested on bullseye, Libreoffice 1:7.0.4-4+deb11u4)

[Robin]

Hi Rene,

On Sun, 23 Oct 2022 09:25:26 +0200, Rene Engelhard wrote:
> Nope. Don't use nvidia is the solution here, as simple as  that. "Augen 
> auf beim Hardwarekauf" is a idiom here in Germany, rougly translated 
> "Open your eyes when buying hardware"

Exactly this „Augen auf beim Hardwarekauf” was what I did when I once bought 
this expensive hires and large screen durable, long-living notebook. It was 
delivered even with a preinstalled Linux on it instead of windows, and if you 
look back nvidia was recommended for linux, exactly because of other 
manufacturers didn't care much for linux drivers in those days. So there's no 
point in saying "Augen auf". Nowadays I couldn't effort to buy an equivalent 
replacement, so also there is no point in saying “dump it, while it's still 
working absolutely fine and fast and does it's job on everyday usage”, as you 
did before.

On Sun, 23 Oct 2022 09:25:26 +0200, Rene Engelhard wrote:
>For exactly the reasons you reiterate below people should not use or buy 
>nvidia stuff.

You could be sure, the way they have treated me by trying to brick this 
perfectly working notebook I will never ever again buy nvidia, and wouldn't 
ever recommend it to other people.

On Sun, 23 Oct 2022 09:25:26 +0200, Rene Engelhard wrote:
> use nouveau. Or use nouveau from the start.
You should read more carefully, please. I had clearly stated:
> [...] proprietary nvidia driver. With the latter all GUI
> menus open immediately, without any delay, while with 
> nouveau driver you'll have to wait sometimes more than 
> 8 seconds for a response after click.

Let me know if you have an idea how to use this obviously broken nouveau driver 
for everyday work. The noveau driver is what actually makes this notebook slow 
and nonfunctional. I really would like to follow your advice to get rid of the 
nvidia proprietary stuff. Btw, there is no point in saying “use it from the 
start”, since there simply was no nouveau driver.

On Sun, 23 Oct 2022 09:25:26 +0200, Rene Engelhard wrote:
> For the record: This is not bullseye. It is bullseye without updates 
> (and especially security updates)  (bullseye contains deb11u3, security 
> deb11u4)

Again, you should read way more carefully, really. I had clearly stated:

> This was a test using the preinstalled version as present
> in the Live USB device. I'll apply an apt-upgrade to this
> USB stick tomorrow and recheck. The installation-candidate
> for Libreoffice is:  1:7.0.4-4+deb11u4, which will be the
> next one I'm going to check out.
[...]
> Will check back with additional results once updated both
> the system and Libreoffice as said above.

So, as promised, I'm back with a report from completely recent apt-upgraded 
bullseye system (still without any backports).

Sadly, same issue with Libreoffice as described originally is present.

Technical data:

Libreoffice Version as reported by GUI:
Version: 7.0.4.2
Build ID: 00(Build:2)
CPU threads: 1; OS: Linux 4.9; UI render: default; VCL: gtk3
Locale: de-DE (de_DE.UTF-8); UI: de-DE
Debian package version: 1:7.0.4-4+deb11u4
Calc: threaded

$ apt-cache policy libreoffice* | grep -v '(keine)' | grep -B1 Installiert
libreoffice-calc:
  Installiert:   1:7.0.4-4+deb11u4
libreoffice-base-core:
  Installiert:   1:7.0.4-4+deb11u4
libreoffice-core:
  Installiert:   1:7.0.4-4+deb11u4
libreoffice-common:
  Installiert:   1:7.0.4-4+deb11u4
libreoffice-draw:
  Installiert:   1:7.0.4-4+deb11u4
libreoffice-impress:
  Installiert:   1:7.0.4-4+deb11u4
libreoffice-l10n-de:
  Installiert:   1:7.0.4-4+deb11u4
libreoffice-style-colibre:
  Installiert:   1:7.0.4-4+deb11u4
libreoffice-writer:
  Installiert:   1:7.0.4-4+deb11u4
libreoffice-help-de:
  Installiert:   1:7.0.4-4+deb11u4
libreoffice-help-common:
  Installiert:   1:7.0.4-4+deb11u4
libreoffice-math:
  Installiert:   1:7.0.4-4+deb11u4
libreoffice-gtk3:
  Installiert:   1:7.0.4-4+deb11u4

ucf:
  Installiert:   3.0043
libabw-0.1-1:
  Installiert:   0.1.3-1
libc6:
  Installiert:   2.31-13+deb11u5
libe-book-0.1-1:
  Installiert:   0.1.3-2
libepubgen-0.1-1:
  Installiert:   0.1.1-1
libetonyek-0.1-1:
  Installiert:   0.1.9-4
libgcc-s1:
  Installiert:   10.2.1-6
libicu67:
  Installiert:   67.1-7
libmwaw-0.3-3:
  Installiert:   0.3.17-1
libodfgen-0.1-1:
  Installiert:   0.1.8-2
librevenge-0.0-0:
  Installiert:   0.0.4-6+b1
libstaroffice-0.0-0:
  Installiert:   0.0.7-1
libstdc++6:
  Installiert:   10.2.1-6
libuno-cppu3:
  Installiert:   1:7.0.4-4+deb11u4
libuno-cppuhelpergcc3-3:
  Installiert:   1:7.0.4-4+deb11u4
libuno-sal3:
  Installiert:   1:7.0.4-4+deb11u4
libuno-salhelpergcc3-3:
  Installiert:   1:7.0.4-4+deb11u4
libwpd-0.10-10:
  Installiert:   0.10.3-1
libwpg-0.3-3:
  Installiert:   0.3.3-1
libwps-0.4-4:
  

Bug#1022554: libjettison-java: CVE-2022-40149

[Salvatore Bonaccorso]

Source: libjettison-java
Version: 1.4.1-1
Severity: important
Tags: security upstream
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerability was published for libjettison-java. It is
fixed upstream in 1.5.1.

CVE-2022-40149[0]:
| Those using Jettison to parse untrusted XML or JSON data may be
| vulnerable to Denial of Service attacks (DOS). If the parser is
| running on user supplied input, an attacker may supply content that
| causes the parser to crash by stackoverflow. This effect may support a
| denial of service attack.


If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2022-40149
https://www.cve.org/CVERecord?id=CVE-2022-40149
[1] https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=46538
[2] https://github.com/jettison-json/jettison/issues/45
[3] 
https://github.com/jettison-json/jettison/commit/395f8625bcf688743872c8e7f59360d372e77811

Regards,
Salvatore

Bug#1022553: libjettison-java: CVE-2022-40150

[Salvatore Bonaccorso]

Source: libjettison-java
Version: 1.4.1-1
Severity: important
Tags: security upstream
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerability was published for libjettison-java.

CVE-2022-40150[0]:
| Those using Jettison to parse untrusted XML or JSON data may be
| vulnerable to Denial of Service attacks (DOS). If the parser is
| running on user supplied input, an attacker may supply content that
| causes the parser to crash by Out of memory. This effect may support a
| denial of service attack.

This issue has not yet been fixed upstream at time of writing this
report.


If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2022-40150
https://www.cve.org/CVERecord?id=CVE-2022-40150
[1] https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=46549
[2] https://github.com/jettison-json/jettison/issues/45

Regards,
Salvatore

Bug#1014017: soundmodem: Fails to build with HID support

[Daniele Forsi]

Hello Alan,

I committed your patch to configure.ac in a branch and I think that we
should merge it to master:
https://salsa.debian.org/debian-hamradio-team/soundmodem/-/tree/hidraw

I didn't commit your patch to ptt.c yet.
What happens if we drop the check for hiddevinfo.product for C-Media entirely?

You changed the test to work with your hardware, which is fine, but it
seems that there are many more CM108s out there (I have one with ID
0d8c:013c).
I'm copying the list from https://usb-ids.gowdy.us/read/UD/0d8c so it
is archived with this bug report.

Id Name
0001 Audio Device
0002 Composite Device
0003 Sound Device
0004 CM6631A Audio Processor
0005 Blue Snowball
0006 Storm HP-USB500 5.1 Headset
000c Audio Adapter
000d Composite Device
000e Audio Adapter (Planet UP-100, Genius G-Talk)
0012
0014 Audio Adapter (Unitek Y-247A)
001f CM108 Audio Controller
0029
0102 CM106 Like Sound Device
0103 CM102-A+/102S+ Audio Controller
0104 CM103+ Audio Controller
0105 CM108 Audio Controller
0107 CM108 Audio Controller
010f CM108 Audio Controller
0115 CM108 Audio Controller
0134
0139 Multimedia Headset [Gigaware by Ignition L.P.]
013c CM108 Audio Controller
0201 CM6501
5000 Mass Storage Controller
5200 Mass Storage Controller(0D8C,5200)
b213 USB Phone CM109 (aka CT2000,VPT1000)

--
73 de IU5HKX Daniele

Bug#988288: /usr/bin/pimdataexporter: I can't import file zip configuration

[Patrick Franz]

Hi Davide,

I cannot reproduce this issue with the current version of KDE PIM 22.08.
I exported some KDE PIM data and when trying to import that data, the 
tool showed me exactly those configs I had exported.

Do you still experience the same even with KDE PIM 22.08 ?


-- 
Med vänliga hälsningar

Patrick Franz

Bug#1022552: RFS: cglm/0.8.6-1 -- Optimized OpenGL Mathematics library for C

[Leon Marz]

Package: sponsorship-requests
Severity: normal

Dear mentors,

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

* Package name : cglm
Version : 0.8.6-1
Upstream contact : Recep Aslantas 
* URL : https://github.com/recp/cglm
* License : Expat
* Vcs : https://salsa.debian.org/debian/cglm
Section : libs

The source builds the following binary packages:

libcglm-doc - Documentation for the cglm library
libcglm-dev - Development files for the cglm library
libcglm0 - Optimized OpenGL Mathematics library for C

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


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

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

dget -x https://mentors.debian.net/debian/pool/main/c/cglm/cglm_0.8.6-1.dsc

Changes since the last upload:

cglm (0.8.6-1) unstable; urgency=medium
.
   * New upstream release
   * Bump Standards-Version to 4.6.1
 - no changes needed

- Leon


OpenPGP_signature
Description: OpenPGP digital signature

Bug#862262: libkf5gapicalendar5: Google calendar changes not synced from Google.

[Patrick Franz]

Hi Andy,

sorry for the rather late reply, but do you still encounter this issue 
even with the current version of KDE PIM in unstable/testing ?


-- 
Med vänliga hälsningar

Patrick Franz

Bug#1014966: onionshare: CVE-2021-41867 CVE-2021-41868 CVE-2022-21688 CVE-2022-21689 CVE-2022-21690 CVE-2022-21691 CVE-2022-21692 CVE-2022-21693 CVE-2022-21694 CVE-2022-21695 CVE-2022-21696

[Salvatore Bonaccorso]

Hi Clément,

On Sun, Oct 23, 2022 at 06:27:08PM +0200, Clément Hermann wrote:
> Hi,
> 
> Le 22/10/2022 à 15:01, Salvatore Bonaccorso a écrit :
> 
> > Thanks for the quick reply! (much appreciated). I think it would be
> > good to get a confirmation from upstream and if possible to have
> > those advisories updates. E.g.
> > https://github.com/onionshare/onionshare/security/advisories/GHSA-x7wr-283h-5h2v
> > while mentioning "affected versions < 2.4" the patched version remains
> > "none". this might be that the < 2.4 just reflects the point in time
> > when the advisory was filled. OTOH you have arguments with the v2.5
> > release information that they might all be fixed.
> > 
> > To be on safe side, explicitly confirming by upstream would be great.
> 
> Agreed. And asked upstream:
> https://github.com/onionshare/onionshare/issues/1633.

Thank you!

Regards,
Salvatore

Bug#1022551: llvm-15's cmake now requires clang-tools-15, clang-tidy-15, clangd-15, even if unused

[Matthias Klose]

Package: src:llvm-toolchain-15
Version: 15.0.3-1
Severity: important
Tags: sid bookworm

llvm-15's cmake support now requires clang-tools-15, clang-tidy-15, clangd-15, 
even if unused. These checks should be optional.


seen when building cvise-2.6.0-1 with LLVM 15

Bug#1022550: gnote nocheck FTBFS: update-desktop-database not found

[Helmut Grohne]

Source: gnote
Version: 43.0-1
Severity: important
Justification: will be rc in trixie
Tags: ftbfs

gnote fails to build from source when enabling the nocheck build
profile. A build ends as follows:

| ../meson.build:63:6: ERROR: Program 'update-desktop-database' not found or 
not executable
| dh_auto_configure: error: cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 meson .. 
--wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc 
--localstatedir=/var --libdir=lib/x86_64-linux-gnu returned exit code 1
| make: *** [debian/rules:7: binary] Error 25
| dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 
2

I suppose that dropping the  annotation from
desktop-file-utils fixes this issue.

Helmut

Bug#1022549: RFP: python-hatch-nodejs-version -- Hatch plugin for versioning from a package.json file

[Julien Puydt]

Package: wnpp
Severity: wishlist
X-Debbugs-Cc: jpu...@debian.org, debian-pyt...@lists.debian.org

* Package name: python-hatch-nodejs-version
  Version : 0.3.0
  Upstream Author : Angus Hollands
* URL : https://github.com/agoose77/hatch-nodejs-version
* License : Expat
  Programming Lang: Python
  Description : Hatch plugin for versioning from a package.json file
This package provides two Hatch plugins:
- version source plugin that reads/writes the package version from the version
field of the Node.js package.json file.
- metadata hook plugin that reads PEP 621 metadata from the Node.js
package.json file.

It's a new dependency of nbformat, and I lack the time to package it myself
before some time... I'll turn it into an ITP if nobody shoots first.

Cheers,

J.Puydt

Bug#1022548: lokalize: text window does not repaint

[Luc Castermans]

Package: lokalize
Version: 4:22.08.2-1~np1
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: l...@castermans.org

Dear Maintainer,

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

lokalize open correctly, the window with translation memory shows correctly as 
well. Each file to translate opens correctly as well in a seperate window.
However the text in that window is NOT SHOWN at all. With this the application 
is not usable.


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


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

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

Versions of packages lokalize depends on:
ii  kio5.98.0-1
ii  libc6  2.36-1
ii  libhunspell-1.7-0  1.7.1-1
ii  libkf5completion5  5.98.0-1
ii  libkf5configcore5  5.98.0-1
ii  libkf5configgui5   5.98.0-1
ii  libkf5configwidgets5   5.98.0-1
ii  libkf5coreaddons5  5.98.0-1
ii  libkf5crash5   5.98.0-1
ii  libkf5dbusaddons5  5.98.0-1
ii  libkf5i18n55.98.0-1+b1
ii  libkf5itemviews5   5.98.0-1
ii  libkf5kiocore5 5.98.0-1
ii  libkf5kiofilewidgets5  5.98.0-1
ii  libkf5kiowidgets5  5.98.0-1
ii  libkf5notifications5   5.98.0-1
ii  libkf5sonnetcore5  5.98.0-1
ii  libkf5sonnetui55.98.0-1
ii  libkf5textwidgets5 5.98.0-1
ii  libkf5widgetsaddons5   5.98.0-1
ii  libkf5xmlgui5  5.98.0-1+b1
ii  libqt5core5a   5.15.6+dfsg-2
ii  libqt5dbus55.15.6+dfsg-2
ii  libqt5gui5 5.15.6+dfsg-2
ii  libqt5network5 5.15.6+dfsg-2
ii  libqt5sql5 5.15.6+dfsg-2
ii  libqt5sql5-sqlite  5.15.6+dfsg-2
ii  libqt5widgets5 5.15.6+dfsg-2
ii  libqt5xml5 5.15.6+dfsg-2
ii  libstdc++6 12.2.0-7

Versions of packages lokalize recommends:
ii  gettext0.21-9
ii  sonnet-plugins 5.98.0-1
ii  translate-toolkit  3.7.3-2

Versions of packages lokalize suggests:
ii  khelpcenter  4:22.08.2-1~np1
ii  poxml4:22.08.2-1~np1

-- no debconf information

Bug#1022547: rust-string-cache-codegen: please update to v0.5.2

[Jonas Smedegaard]

Source: rust-string-cache-codegen
Version: 0.5.1-2
Severity: normal
Tags: upstream

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Please update to newer minor upstream release v0.5.2, needed by projects
I am preparing for Debian.

 - Jonas

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmNVeTUACgkQLHwxRsGg
ASH84Q//T45fZBI70EStqxudUg0RsuqkksqtMmTI6woPbuS6GDER6Ny2fok0KNyz
ZPDK2bIsrcUkmsC0AHMHmR8aIFVsSxW0KPUDj4Vn3vOCjgQe6zHOQwWYjlDXUYTg
8BsU+6zNbo4VjaxmWbglQEAoZ3aPDaqqDOCBfZ03RMXyRGtgmaryn0fZtBlHu+o2
3vyzZ+ZuJ0sXsU1DPoQJKijQo66t9kLq1VsCtyaew4fpNEpsa3XGcF26kuJJMv48
WEBfK7uIw4bQ5HdoTUJUdQsQhVbz6nPsetOVXzG+INyhbbU/Vwc7A2kHXm0O6emw
rgXUdDuSOZmmnrFeASix2MMVXQ+TEjSVUuTUdG1w9zW69egA4bQyFn2dYp4u97Ap
UeiILzu0NooMcvu1KG/GgF2gYgyVJWEGsp9uXEN/Pm0w1ph8RU+4pXRjH4+RmwKN
+3DItKH0+lpFGejpYYaNtSVSf0kqMU5SXyTVI8jEdE8YAkS5jxJhbpVvry1b1Y2M
rBTE7qW0/b+SM3bNBMaN1j8O/GRd725plzalvc3ONqLj5JcoHyM5YAyJNhBgG0ZA
NM9I38HbJyXI8m9vuviN8MIs3TGLx2WVUnbSbb2KxFwTMRV9gNi7YBAu395zZvLG
yEGN016kbEej1k3aVSRWyz0IpX2/+n1Ozu4aP/4GNYQBkYEMW3A=
=A7oh
-END PGP SIGNATURE-

Bug#1022365: confirmed

[dann frazier]

Weird, tests pass for me locally. Will look into it.

Bug#1022364: qutebrowser: FTBFS: dh_usrlocal: error: debian/qutebrowser/usr/local/bin/qutebrowser is not a directory

[Axel Beckert]

Control: tag -1 + confirmed

Hi Lucas,

Lucas Nussbaum wrote:
> During a rebuild of all packages in sid, your package failed to build
> on amd64.

Thanks for the bug report. Can reproduce it here.

> Relevant part (hopefully):
[…]
> > I: dh_python3 pydist:302: Cannot find package that provides dataclasses. 
> > Please add package that provides it to Build-Depends or add "dataclasses 
> > python3-dataclasses" line to debian/py3dist-overrides or add proper 
> > dependency to Depends by hand and ignore this info.
> > I: dh_python3 pydist:302: Cannot find package that provides dataclasses. 
> > Please add package that provides it to Build-Depends or add "dataclasses 
> > python3-dataclasses" line to debian/py3dist-overrides or add proper 
> > dependency to Depends by hand and ignore this info.

I first thought that this is the relevant hint. But it also showed up
in previous successful builds, e.g. 2.5.2-1, so it was a red herring:
https://buildd.debian.org/status/fetch.php?pkg=qutebrowser=all=2.5.2-1=1655941699=0

> >dh_usrlocal -O--buildsystem=pybuild -O--link-doc=qutebrowser
> > dh_usrlocal: error: debian/qutebrowser/usr/local/bin/qutebrowser is not a 
> > directory

This is clearly the one which makes the build stop at the end.

Looks like something suddenly installs the qutebrowser binary _also_
into /usr/local/bin/. I so far just have no idea yet what or why.

Actually the following override in debian/rules would fix it and the
resulting .deb has no debdiff to 2.5.2-1 as in unstable/testing, but
I'd first like to understand what actually goes wrong instead of
fixing symptoms:

  override_dh_usrlocal:
rm -rvf debian/qutebrowser/usr/local/

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#1022042: kernel 5.10.149-2 does not help

[Diederik de Haas]

On zondag 23 oktober 2022 19:01:06 CEST Andreas Wirooks wrote:
> Am 23.10.22 um 14:27 schrieb Diederik de Haas:
> > On zondag 23 oktober 2022 14:10:11 CEST Andreas Wirooks wrote:
> >>> You both have kernel parameters like these. Can you explain why?
> >>> I have an AMD GPU on a machine and I have never set parameters like
> >>> these.
> >> 
> >> These are parameters for Southern Islands (si) and Sea Islands (cik) AMD
> >> GPUs:
> > I see you're already 'in'
> > https://gitlab.freedesktop.org/drm/amd/-/issues/2216 and that seems like
> > an important distinction to mention (to me).
> > All the other cases for where this issue was fixed, seem to have (much)
> > newer generation of GPUs.
> 
> I will write an update in the drm issue too.
> 
> I tested the old radeon driver by removing all si/cki options with
> kernel 5.10.149-2 and it boots ok and uses drm 2 instead drm 3.

Excellent. I saw you already added that info to the upstream bug :-)

> The debian 11/bullseye backport kernel 5.19.11-1~bpo11+1 boots ok with
> the amdgpu driver too using drm 3.

Alex Deucher (@agd5f) indicated the problem was caused by an incorrect 
backport to 5.10 and maybe the 2 identified ones aren't the only ones.

On zondag 23 oktober 2022 17:44:17 CEST inasprec...@disroot.org wrote:
> I tried booting 5.10.0-19 with an empty command line string and it
> worked
> 
> I don’t know if this an entirely separate issue, however.  I can
> file a separate bug if you think it is appropriate.

Given that switching to the radeon driver fixed the issue for you both, then I 
guess it's the same issue. So let's keep it to this bug, at least for now.

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

Bug#1022253: swi-prolog breaks logol autopkgtest on s390x

[Lev Lamberov]

Hi Paul,

Вс 23 окт 2022 @ 10:10 Paul Gevers :

> Hi Lev,
>
> On 23-10-2022 09:40, Lev Lamberov wrote:
>> I'm not sure it is the solution, it needs testing. The change in
>> swi-prolog concerns pre-compiled prolog source code, when there is no
>> pre-complied prolog code rebuilt is not needed. SWI-Prolog supports
>> three different kinds of pre-compilation, at least one of them was
>> affected and another was not. The mentioned endiannes bug can be found
>> in BTS, #1006818 [bts].
>
> I just ran the autopkgtest with a rebuild logol on s390x, see below. 
> Does that help?
>
> @logol maintainers, those ERRORs look scary if the test passes with it. 
> Is that just noise, or are real problems ignored?

Given the answer from Étienne looks like it *is* the solution. Thanks
for your work on it!

Cheers!
Lev

Bug#1022546: rust-siphasher: please update to v0.3.9

[Jonas Smedegaard]

Source: rust-siphasher
Version: 0.3.1-1
Severity: normal
Tags: upstream

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Please update to newer upstream release v0.3.9, needed by projects I am
preparing for Debian.

  - Jonas

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmNVd8gACgkQLHwxRsGg
ASEHFw/9GSsaSwWLViAUadyHSmc1uxWd/fRTPl978atVXdEm369+9ymVC1K3cDMJ
ImjeUDdR1+kmnvS8s+BvReEzIH/CEYXCGuLnMua6mI69WNYoJ/XRZ6WQgWBVbLpn
IkYtdQVf7Gq5HfP7MPN6WIwvZNXvxKbaZeeNc69wQ3Z0HTnW21TLqsht0l8HO03m
DNhRNl+wnFt1DZNhjOeCjLjT15BI3ImHlwt3hq5f7X6tpYhjR+b4M6RufjT7dMcY
y1Vz9wm60lTc2Ov1a0oyrGVNbQSXRx6hGibhVRdvLuFYzsky9BhDxhjvdkw5uRVG
XR6bkOLZk7xPlqkJETRcfkjS13sbSuRM2MUiSWMbJYTCF4m+xUTSsyzEd2dCEnv+
HnPcCSDJEtUHO9LUqC7Y6YeZ1GQ/77pcLC1tC7MD3nclOrqa80O1vUaY7M3bA8vV
uVU68bMiWbdVRsaUi0JyY+SRxSBvXpgWljRkcThZfMB0FR5RSaEzL350w/gKgVQl
B0jWSj7KipQADL0WAkbm+o+BNIWCVBJrdvypkc4TvRxuFkeIgIeDTl29OQtt05mq
Zn+wc5HUEWczoZo6e5y/WdqzIN2AvvznXQTyKqPTf8vCZUHhWFSbhO0OKJMq5ioz
UMca/ctQNh5A4CsIVrB3YdS5JW3CHi3FkaW1eHd9DkKNTbWbna4=
=JKB1
-END PGP SIGNATURE-

Bug#1022545: wishlist: please enable CONFIG_LEDS_USER

[Daniele Forsi]

Source: linux
Version: 5.10.140-1
Severity: wishlist
X-Debbugs-Cc: dfo...@gmail.com

Dear maintainers,

please considser building the uleds module (CONFIG_LEDS_USER=m).

The kernel documentation says:
> The uleds driver supports userspace LEDs. This can be useful for testing
> triggers and can also be used to implement virtual LEDs.

My use case is a PC with two on-board ethernet ports and only one activity LED 
on its front panel.

thanks,
Daniele

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

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

Bug#1022286: gnome-shell-extension-manager: FTBFS: ModuleNotFoundError: No module named 'gi'

[Simon McVittie]

Control: reassign -1 blueprint-compiler 0.4.0-3
Control: affects -1 + src:gnome-shell-extension-manager

On Sun, 23 Oct 2022 at 14:38:05 +0200, Lucas Nussbaum wrote:
> > Program blueprint-compiler found: YES (/usr/bin/blueprint-compiler)
...
> > Traceback (most recent call last):
> >   File "/usr/bin/blueprint-compiler", line 37, in 
> > from blueprintcompiler import main
...
> >   File "/usr/lib/python3/dist-packages/blueprintcompiler/gir.py", line 24, 
> > in 
> > import gi # type: ignore
> > ModuleNotFoundError: No module named 'gi'

This looks like a missing dependency in blueprint-compiler.

>From a brief look at the package, it seems like python3-gi might have been
added to debian/control, instead of adding it to debian/control.in and
then regenerating debian/control with `make -f debian/rules clean`. This
effectively results in the change being reverted whenever the package
is rebuilt.

smcv

Bug#1022544: linux-image-6.0.0-2-amd64: No more sound after upgrade to 6.0.0-2

[pdormeau]

Package: src:linux
Version: 6.0.3-1
Severity: normal

Dear Maintainer,

After upgrade from 6.0.0-1 to 6.0.0-2, I don't have sound anymore.
I believe that the relevant dmesg message is this one, as it is not printed 
with the 6.0.0-1 version:

snd_hda_codec_hdmi ehdaudio0D2: failed to create hda codec -12
snd_hda_codec_hdmi ehdaudio0D2: ASoC: error at snd_soc_component_probe on 
ehdaudio0D2: -12
skl_hda_dsp_generic skl_hda_dsp_generic: ASoC: failed to instantiate card -12
skl_hda_dsp_generic: probe of skl_hda_dsp_generic failed with error -12

git bisect indicates that the bad commit is:
[7494e2e6c55ed192f2b91c821fd6832744ba8741] ALSA: hda: Fix page fault in 
snd_hda_codec_shutdown()

Ask me if you need further information.

Best regards

Pascal D

-- Package-specific info:
** Version:
Linux version 6.0.0-2-amd64 (debian-ker...@lists.debian.org) (gcc-12 (Debian 
12.2.0-7) 12.2.0, GNU ld (GNU Binutils for Debian) 2.39) #1 SMP PREEMPT_DYNAMIC 
Debian 6.0.3-1 (2022-10-21)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-6.0.0-2-amd64 
root=UUID=6dc0e7ec-e588-4c76-8c94-0ad097ce4975 ro acpi_backlight=video 
systemd.show-status=true systemd.restore_state=0 quiet

** Not tainted

** Kernel log:
[5.540610] sof-audio-pci-intel-tgl :00:1f.3: use msi interrupt mode
[5.570644] typec port0: bound usb1-port5 (ops connector_ops [usbcore])
[5.570664] typec port0: bound usb4-port1 (ops connector_ops [usbcore])
[5.609292] sof-audio-pci-intel-tgl :00:1f.3: hda codecs found, mask 5
[5.609296] sof-audio-pci-intel-tgl :00:1f.3: using HDA machine driver 
skl_hda_dsp_generic now
[5.609299] sof-audio-pci-intel-tgl :00:1f.3: DMICs detected in NHLT 
tables: 2
[5.610210] sof-audio-pci-intel-tgl :00:1f.3: firmware: direct-loading 
firmware intel/sof/sof-adl.ri
[5.610215] sof-audio-pci-intel-tgl :00:1f.3: Firmware info: version 
2:2:0-57864
[5.610216] sof-audio-pci-intel-tgl :00:1f.3: Firmware: ABI 3:22:1 
Kernel ABI 3:23:0
[5.610219] sof-audio-pci-intel-tgl :00:1f.3: unknown sof_ext_man header 
type 3 size 0x30
[5.622328] usb 1-10: new full-speed USB device number 3 using xhci_hcd
[5.633629] iwlwifi :00:14.3: firmware: direct-loading firmware 
iwlwifi-so-a0-gf-a0.pnvm
[5.633648] iwlwifi :00:14.3: loaded PNVM version a982b33e
[5.649224] iwlwifi :00:14.3: Detected RF GF, rfid=0x2010d000
[5.708919] sof-audio-pci-intel-tgl :00:1f.3: Firmware info: version 
2:2:0-57864
[5.708931] sof-audio-pci-intel-tgl :00:1f.3: Firmware: ABI 3:22:1 
Kernel ABI 3:23:0
[5.718238] iwlwifi :00:14.3: base HW address: 84:7b:57:57:88:e3
[5.737125] e1000e :00:1f.6 eth0: (PCI Express:2.5GT/s:Width x1) 
6c:24:08:b8:af:ec
[5.737131] e1000e :00:1f.6 eth0: Intel(R) PRO/1000 Network Connection
[5.737438] e1000e :00:1f.6 eth0: MAC: 15, PHY: 12, PBA No: FF-0FF
[5.774725] usb 1-10: New USB device found, idVendor=8087, idProduct=0033, 
bcdDevice= 0.00
[5.774739] usb 1-10: New USB device strings: Mfr=0, Product=0, 
SerialNumber=0
[6.526324] typec port1: bound usb1-port6 (ops connector_ops [usbcore])
[6.526358] typec port1: bound usb4-port3 (ops connector_ops [usbcore])
[8.263588] pstore: Using crash dump compression: deflate
[8.331887] pstore: Registered efi as persistent store backend
[8.413634] input: PC Speaker as /devices/platform/pcspkr/input/input9
[8.431300] RAPL PMU: API unit is 2^-32 Joules, 4 fixed counters, 655360 ms 
ovfl timer
[8.431302] RAPL PMU: hw unit of domain pp0-core 2^-14 Joules
[8.431303] RAPL PMU: hw unit of domain package 2^-14 Joules
[8.431303] RAPL PMU: hw unit of domain pp1-gpu 2^-14 Joules
[8.431304] RAPL PMU: hw unit of domain psys 2^-14 Joules
[8.432285] cryptd: max_cpu_qlen set to 1000
[8.436833] AVX2 version of gcm_enc/dec engaged.
[8.436868] AES CTR mode by8 optimization enabled
[9.577729] usb 1-10: USB disconnect, device number 3
[9.669273] intel_rapl_msr: PL4 support detected.
[9.669309] intel_rapl_common: Found RAPL domain package
[9.669313] intel_rapl_common: Found RAPL domain core
[9.669314] intel_rapl_common: Found RAPL domain uncore
[9.669316] intel_rapl_common: Found RAPL domain psys
[9.732174] mei_hdcp :00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: 
bound :00:02.0 (ops i915_hdcp_component_ops [i915])
[9.738623] input: SYNA801A:00 06CB:CEC6 Mouse as 
/devices/pci:00/:00:15.0/i2c_designware.0/i2c-14/i2c-SYNA801A:00/0018:06CB:CEC6.0001/input/input10
[9.738703] input: SYNA801A:00 06CB:CEC6 Touchpad as 
/devices/pci:00/:00:15.0/i2c_designware.0/i2c-14/i2c-SYNA801A:00/0018:06CB:CEC6.0001/input/input11
[9.738765] hid-generic 0018:06CB:CEC6.0001: input,hidraw0: I2C HID v1.00 
Mouse [SYNA801A:00 06CB:CEC6] on i2c-SYNA801A:00
[9.739190] iTCO_vendor_support: vendor-support=0
[9.741148] iTCO_wdt iTCO_wdt: Found a Intel PCH TCO device (Version=6, 
TCOBASE=0x0400)
[

Bug#1022042: kernel 5.10.149-2 does not help

[Andreas Wirooks]

Am 23.10.22 um 14:27 schrieb Diederik de Haas:

On zondag 23 oktober 2022 14:10:11 CEST Andreas Wirooks wrote:

You both have kernel parameters like these. Can you explain why?
I have an AMD GPU on a machine and I have never set parameters like these.

These are parameters for Southern Islands (si) and Sea Islands (cik) AMD
GPUs:

I see you're already 'in' https://gitlab.freedesktop.org/drm/amd/-/issues/2216
and that seems like an important distinction to mention (to me).
All the other cases for where this issue was fixed, seem to have (much) newer
generation of GPUs.


I will write an update in the drm issue too.

I tested the old radeon driver by removing all si/cki options with
kernel 5.10.149-2 and it boots ok and uses drm 2 instead drm 3.

But of course i added these options again and rebooted with 5.10.140-1
because of Vulkan support in the amdgpu driver using drm 3.

The debian 11/bullseye backport kernel 5.19.11-1~bpo11+1 boots ok with
the amdgpu driver too using drm 3.

Bug#1022289: libassuan: FTBFS: configure: error: libgpg-error was not found

[Andreas Metzler]

On 2022-10-23 Lucas Nussbaum  wrote:
> Source: libassuan
> Version: 2.5.5-4
> Severity: serious
> Justification: FTBFS
> Tags: bookworm sid ftbfs
> User: lu...@debian.org
> Usertags: ftbfs-20221023 ftbfs-bookworm

> Hi,

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


> Relevant part (hopefully):
> > ../configure: line 15745: /usr/i686-w64-mingw32/bin/gpg-error-config: No 
> > such file or directory
[...]


Hello,

Caused by new gpg-error dropping gpg-error-config, this works for me:

--- libassuan-2.5.5/debian/rules2022-04-30 17:47:12.0 +0200
+++ patched/libassuan-2.5.5.patched/debian/rules2022-10-23 
18:23:40.505849321 +0200
@@ -27,7 +27,6 @@
for cpu in i686 x86_64; do \
 mkdir -p build-$$cpu-w64-mingw32 && \
 cd build-$$cpu-w64-mingw32 && $(WIN_FLAGS) ../configure \
-   --with-libgpg-error-prefix=/usr/$$cpu-w64-mingw32 \
--prefix=/usr/$$cpu-w64-mingw32 \
--enable-static \
--host $$cpu-w64-mingw32 && \

and a successful build with gpg-error 1.46 and a patched build with 1.47 look
almost identical except for configure messages changing:
-checking for gpg-error-config... /usr/x86_64-w64-mingw32/bin/gpg-error-config
+checking for gpg-error-config... no
 checking for gpgrt-config... /usr/bin/gpgrt-config
 configure: Use gpgrt-config with /usr/x86_64-w64-mingw32/lib as 
gpg-error-config
-checking for GPG Error - version >= 1.17... yes (1.45)
+checking for GPG Error - version >= 1.17... yes (1.46)

cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'

Bug#1009031: possible workaround for libgit-raw-perl FTBFS with libgit2 1.3.0

[gregor herrmann]

Control: tag -1 + fixed-upstream

On Sun, 23 Oct 2022 17:17:22 +0200, gregor herrmann wrote:

> On Sat, 22 Oct 2022 18:48:31 +0200, Étienne Mollier wrote:
> 
> > Taking the approach of refreshing the test suite to match the
> > output produced by the new libgit2 seems to do the job to
> > address the test suite failure.  I also checked this has no
> > adverse effects on reverse dependencies.  Variations between the
> > reference and the new update are also minimal and seem to make
> > sense.
> 
> Interesting finding!
> The last time I looked I had the impression that this needs more
> changes / changes in the actual code but obviously I was wrong.

And now this is apparently fixed upstream in the 0.89 release:

https://github.com/jacquesg/p5-Git-Raw/issues/222#issuecomment-1288150066


Cheers,
gregor

-- 
 .''`.  https://info.comodo.priv.at -- Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
   `-   


signature.asc
Description: Digital Signature

Bug#1014966: onionshare: CVE-2021-41867 CVE-2021-41868 CVE-2022-21688 CVE-2022-21689 CVE-2022-21690 CVE-2022-21691 CVE-2022-21692 CVE-2022-21693 CVE-2022-21694 CVE-2022-21695 CVE-2022-21696

[Clément Hermann]

Hi,

Le 22/10/2022 à 15:01, Salvatore Bonaccorso a écrit :


Thanks for the quick reply! (much appreciated). I think it would be
good to get a confirmation from upstream and if possible to have
those advisories updates. E.g.
https://github.com/onionshare/onionshare/security/advisories/GHSA-x7wr-283h-5h2v
while mentioning "affected versions < 2.4" the patched version remains
"none". this might be that the < 2.4 just reflects the point in time
when the advisory was filled. OTOH you have arguments with the v2.5
release information that they might all be fixed.

To be on safe side, explicitly confirming by upstream would be great.


Agreed. And asked upstream: 
https://github.com/onionshare/onionshare/issues/1633.


Cheers,

--
nodens

Bug#1022543: Lower intel-rapl-mmio power limit on ThinkPad T490 since 5.18.0-3-amd64

[Hannes von Haugwitz]

Package: src:linux
Version: 6.0.3-1
Severity: important

Hello,

starting with 5.18.0-3-amd64 I experience significant performance loss
(clock speed slows down to 400 MHz) on higher CPU usage.

After checking for differences I figured out that the long-term intel rapl mmio
power limit now defaults to 5W (AC mode) / 10W (battery mode) compared
to 25W with 5.18.0-2-amd64:

AC mode:
$ uname -a
Linux sulfur 6.0.0-2-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.0.3-1 
(2022-10-21) x86_64 GNU/Linux
$ cat /sys/class/power_supply/AC/online
1
$ cat 
/sys/class/powercap/intel-rapl-mmio/intel-rapl-mmio\:0/constraint_0_power_limit_uw
500

Battery mode:
$ uname -a
Linux sulfur 6.0.0-2-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.0.3-1 
(2022-10-21) x86_64 GNU/Linux
$ cat /sys/class/power_supply/AC/online
0
$ cat 
/sys/class/powercap/intel-rapl-mmio/intel-rapl-mmio\:0/constraint_0_power_limit_uw
1000

Note that the limit in battery mode is actually higher than in AC mode.

Booting into 5.18.0-2-amd64 the default power limit is 25W:

AC mode:
$ uname -a
Linux sulfur 5.18.0-2-amd64 #1 SMP PREEMPT_DYNAMIC Debian 5.18.5-1 
(2022-06-16) x86_64 GNU/Linux
$ cat /sys/class/power_supply/AC/online
1
$ cat 
/sys/class/powercap/intel-rapl-mmio/intel-rapl-mmio\:0/constraint_0_power_limit_uw
2500

Battery mode:
$ uname -a
Linux sulfur 5.18.0-2-amd64 #1 SMP PREEMPT_DYNAMIC Debian 5.18.5-1 
(2022-06-16) x86_64 GNU/Linux
$ cat /sys/class/power_supply/AC/online
0
$ cat 
/sys/class/powercap/intel-rapl-mmio/intel-rapl-mmio\:0/constraint_0_power_limit_uw
2500

I can manually set the power limit to 2500 (fixing the performance
issues), but the embedded controller changes it back to 500 after
some time.

Please let me know if I can provide any further information.

Best regards

Hannes

-- Package-specific info:
** Version:
Linux version 6.0.0-2-amd64 (debian-ker...@lists.debian.org) (gcc-12 (Debian 
12.2.0-7) 12.2.0, GNU ld (GNU Binutils for Debian) 2.39) #1 SMP PREEMPT_DYNAMIC 
Debian 6.0.3-1 (2022-10-21)

** Command line:
BOOT_IMAGE=/vmlinuz-6.0.0-2-amd64 root=/dev/mapper/sulfur--vg-root ro 
apparmor=0 quiet

** Not tainted

** Kernel log:
Unable to read kernel log; any relevant messages should be attached

** Model information
sys_vendor: LENOVO
product_name: 20N2CTO1WW
product_version: ThinkPad T490
chassis_vendor: LENOVO
chassis_version: None
bios_vendor: LENOVO
bios_version: N2IET99W (1.77 )
board_vendor: LENOVO
board_name: 20N2CTO1WW
board_version: SDK0R32862 WIN

** Loaded modules:
snd_seq_dummy
snd_hrtimer
snd_seq
snd_seq_device
ctr
ccm
xt_CHECKSUM
nft_chain_nat
xt_MASQUERADE
nf_nat
nf_conntrack
nf_defrag_ipv6
nf_defrag_ipv4
xt_tcpudp
nft_compat
bridge
stp
llc
nf_tables
libcrc32c
rfcomm
cmac
algif_hash
algif_skcipher
af_alg
bnep
nfnetlink
nls_ascii
nls_cp437
vfat
fat
btusb
btrtl
btbcm
btintel
btmtk
bluetooth
uvcvideo
videobuf2_vmalloc
jitterentropy_rng
videobuf2_memops
videobuf2_v4l2
videobuf2_common
sha512_ssse3
sha512_generic
videodev
drbg
ansi_cprng
mc
ecdh_generic
ecc
intel_pmc_core_pltdrv
intel_pmc_core
snd_sof_pci_intel_cnl
snd_sof_intel_hda_common
soundwire_intel
soundwire_generic_allocation
soundwire_cadence
snd_sof_intel_hda
snd_sof_pci
snd_sof_xtensa_dsp
snd_sof
snd_sof_utils
soundwire_bus
snd_soc_skl
x86_pkg_temp_thermal
snd_soc_hdac_hda
intel_powerclamp
coretemp
snd_hda_ext_core
snd_soc_sst_ipc
snd_hda_codec_hdmi
snd_soc_sst_dsp
iTCO_wdt
kvm_intel
snd_soc_acpi_intel_match
rtsx_pci_sdmmc
intel_pmc_bxt
iTCO_vendor_support
snd_soc_acpi
iwlmvm
ee1004
watchdog
mei_hdcp
mmc_core
snd_ctl_led
intel_rapl_msr
snd_soc_core
wmi_bmof
snd_hda_codec_realtek
intel_wmi_thunderbolt
kvm
snd_compress
mac80211
snd_hda_codec_generic
irqbypass
snd_hda_intel
crc32_pclmul
libarc4
snd_intel_dspcfg
snd_intel_sdw_acpi
ghash_clmulni_intel
snd_hda_codec
iwlwifi
rapl
e1000e
snd_hda_core
intel_cstate
snd_hwdep
xhci_pci
snd_pcm
intel_uncore
xhci_hcd
pcspkr
joydev
ptp
i2c_i801
thinkpad_acpi
efi_pstore
pps_core
snd_timer
i2c_smbus
cfg80211
thunderbolt
mei_me
processor_thermal_device_pci_legacy
usbcore
nvram
processor_thermal_device
rtsx_pci
platform_profile
mei
processor_thermal_rfim
ucsi_acpi
ledtrig_audio
processor_thermal_mbox
typec_ucsi
intel_lpss_pci
processor_thermal_rapl
intel_lpss
snd
idma64
intel_rapl_common
usb_common
roles
intel_pch_thermal
soundcore
intel_soc_dts_iosf
typec
wmi
rfkill
battery
int3403_thermal
int340x_thermal_zone
ac
int3400_thermal
button
acpi_thermal_rel
acpi_pad
msr
parport_pc
ppdev
lp
parport
fuse
configfs
efivarfs
ip_tables
x_tables
autofs4
ext4
crc16
mbcache
jbd2
crc32c_generic
dm_crypt
dm_mod
i915
i2c_algo_bit
drm_buddy
drm_display_helper
drm_kms_helper
cec
rc_core
crc32c_intel
ttm
nvme
nvme_core
drm
aesni_intel
t10_pi
psmouse
crypto_simd
cryptd
crc64_rocksoft
evdev
crc64
crc_t10dif
serio_raw
crct10dif_generic
crct10dif_pclmul
crct10dif_common
video

-- System Information:
Debian Release: bookworm/sid
  APT prefers 

Bug#1022042: linux-image-amd64: linux-image-5.10.0-19-amd64 fails to boot on machines with AMD integrated graphics

[inasprecali]

Diederik de Haas  writes:
> Then I'm inclined to think this *is* a separate issue, which is
> due to the upgrade to -19, but that you happen to have an AMD
> GPU is 'not' relevant.
>
> I realize it's not what you want, but may result in an useful
> extra data point if you (for this test) switch those parameters
> to enable radeon support and disable amdgpu support. Can you try
> that?
>
> If that test does not make a difference, then I'm quite sure
> it's a separate issue and it would be best to open a new bug
> report for that.

I tried booting 5.10.0-19 with an empty command line string and it
worked, although it’s now using the "radeon" gpu driver while I’d
like to use the "amdgpu" driver instead, mainly for better Vulkan
support.

Booting with command line options to disable "radeon" and enable
"amdgpu" works for 5.10.0-18 and earlier.

I don’t know if this an entirely separate issue, however.  I can
file a separate bug if you think it is appropriate.

Best regards.

--
inasprecali

Bug#1022042: linux-image-amd64: linux-image-5.10.0-19-amd64 fails to boot on machines with AMD integrated graphics

[inasprecali]

Diederik de Haas  writes:
> Then I'm inclined to think this *is* a separate issue, which is
> due to the upgrade to -19, but that you happen to have an AMD
> GPU is 'not' relevant.

> I realize it's not what you want, but may result in an useful
> extra data point if you (for this test) switch those parameters
> to enable radeon support and disable amdgpu support. Can you try
> that?
>
> If that test does not make a difference, then I'm quite sure
> it's a separate issue and it would be best to open a new bug
> report for that.

Bug#1022542: cruft: misc filter additions

[Christian Göttsche]

Package: cruft-ng
Version: 0.9.46

Hi,

thanks for maintaining and improving cruft(-ng).

Several miscellaneous false positives I encountered:

I. ccache
ccache stores a cache of symlinks to supported compilers at
/usr/lib/ccache/, updated via a dpkg trigger.
One could reimplement update-ccache-symlinks(8), but a much simpler
script works also:

/etc/cruft/explain/ccache:

#!/bin/sh

set -eu

find /usr/lib/ccache/ -maxdepth 1 -type l ! -empty

II. appstream

The shipped filter misses two entries:

/var/cache/swcatalog
/var/cache/swcatalog/cache

III. fwupd

/var/cache/fwupd
/var/cache/fwupd/devices.json
/var/cache/fwupd/metadata.xmlb
/var/cache/fwupd/metainfo.xmlb
/var/cache/fwupd/quirks.xmlb
/var/cache/fwupdmgr
/var/lib/fwupd
/var/lib/fwupd/gnupg
/var/lib/fwupd/gnupg/private-keys-v1.d
/var/lib/fwupd/gnupg/pubring.kbx
/var/lib/fwupd/gnupg/pubring.kbx~
/var/lib/fwupd/gnupg/trustdb.gpg
/var/lib/fwupd/metadata
/var/lib/fwupd/metadata/lvfs
/var/lib/fwupd/metadata/lvfs/metadata.xml.gz
/var/lib/fwupd/metadata/lvfs/metadata.xml.gz.jcat
/var/lib/fwupd/pending.db
/var/lib/fwupd/pki
/var/lib/fwupd/pki/client.pem
/var/lib/fwupd/pki/secret.key
/var/lib/fwupd/quirks.d
/var/lib/fwupd/remotes.d

IV. grub-efi-amd64(-bin)

For EFI files of grub2 I use a mixture of filters and exclude:

/etc/cruft/explain/grub-efi-amd64-bin:
#!/bin/sh

set -e

dpkg-query -L grub-efi-amd64-bin | grep ^/usr/lib/grub/x86_64-efi
| grep -e '\.mod$' -e '\.lst$' | sed 's#usr/lib#boot#'


/etc/cruft/filters/grub-efi-amd64:

/boot/efi
/boot/efi/EFI
/boot/efi/EFI/debian
/boot/efi/EFI/debian/BOOTX64.CSV
/boot/efi/EFI/debian/fbx64.efi
/boot/efi/EFI/debian/grub.cfg
/boot/efi/EFI/debian/grubx64.efi
/boot/efi/EFI/debian/mmx64.efi
/boot/efi/EFI/debian/shimx64.efi
/boot/grub/.background_cache.png
/boot/grub/x86_64-efi
/boot/grub/x86_64-efi/core.efi
/boot/grub/x86_64-efi/grub.efi
/boot/grub/x86_64-efi/load.cfg
/boot/grub/x86_64-efi/modinfo.sh

V. ingerman

/usr/lib/ispell/ngerman.hash
/var/lib/ispell/ngerman.compat
/var/lib/ispell/ngerman.hash
/var/lib/ispell/ngerman.remove

VI. kde-config-sddm

/etc/sddm.conf.d
/etc/sddm.conf.d/kde_settings.conf

VII. llvm-15-runtime

/var/lib/binfmts/llvm-15-runtime.binfmt

VIII. pbuilder

pbuilder is missing two entries:

/var/cache/pbuilder/base.tgz
/var/cache/pbuilder/ccache/**

IX. policycoreutils-dev

/var/lib/sepolgen/interface_info

X. rkhunter

/var/lib/rkhunter/db/rkhunter.dat
/var/lib/rkhunter/db/rkhunter.dat.old
/var/lib/rkhunter/db/rkhunter_prop_list.dat

XI. tlp

/var/lib/tlp/rfkill_saved

XII. usbguard

/etc/usbguard/rules.conf

XIII. vnstat

/var/lib/vnstat/vnstat.db

Bug#1022244: displaycal: int() base must be >= 2 and <= 36, or 0

[Christian Marillat]

On 22 oct. 2022 18:51, Michael Below  wrote:

> Package: displaycal
> Version: 3.9.8-1
> Severity: important
> X-Debbugs-Cc: be...@judiz.de
>
> Dear Maintainer,

Hi,

> today I reinstalled displaycal after some months (last measured profile
> is about one year old), for the first time with python 3. On startup, I
> get the above error message. The main menu shows up, but when I choose
> any of the main functions (Calibration etc), the message shows again and
> none of the functions work.
>
> The error message can't be copy/pasted, but I will send a screen cap
> with another message.

Nothing is displayed in a terminal when displaycal is launched from a
terminal ?

To not display german words :

LANG=C displaycal

Christian

Bug#1009031: possible workaround for libgit-raw-perl FTBFS with libgit2 1.3.0

[gregor herrmann]

On Sat, 22 Oct 2022 18:48:31 +0200, Étienne Mollier wrote:

> Taking the approach of refreshing the test suite to match the
> output produced by the new libgit2 seems to do the job to
> address the test suite failure.  I also checked this has no
> adverse effects on reverse dependencies.  Variations between the
> reference and the new update are also minimal and seem to make
> sense.

Interesting finding!
The last time I looked I had the impression that this needs more
changes / changes in the actual code but obviously I was wrong.

The only additional remark I have is:

-   libgit2-dev (>= 1.1.0),
+   libgit2-dev (>= 1.5.0),

as with your patch the tests fail in stable/bullseye.
 

Cheers,
gregor

-- 
 .''`.  https://info.comodo.priv.at -- Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
   `-   


signature.asc
Description: Digital Signature

Bug#1022541: biometric-auth: postrm scripts in source contains output from DebHelper result

[Alexandre Detiste]

Package: biometric-auth
Version: 0.9.71-1
Severity: normal

Hi,

The "dh_systemd_enable/11.2.1ubuntu1" line here is a red flag.

https://github.com/ukui/biometric-authentication/blob/Debian/debian/biometric-auth.postrm

"#DEBHELPER#" is already on line 3,
the existing script should be truncated from line 43.

Greetings,

Alexandre Detiste


-- System Information:
Debian Release: bookworm/sid
  APT prefers testing
  APT policy: (501, 'testing'), (450, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Bug#927950: O: mini-httpd -- Small HTTP server

[Bastian Germann]

Control: retitle -1 O: mini-httpd -- Small HTTP server
Control: noowner -1

Hi Khoa,

Your RFS was not refreshed after the bullseye freeze.
If you want the adoption to happen for bookworm you should take action soon.

Thanks,
Bastian

Bug#1022540: build-essential: please add riscv64 support

[Bo YU]

Source: build-essential
Version: 12.9
Severity: wishlist
Tags: ftbfs, patch
User: debian-ri...@lists.debian.org
Usertags: riscv64
X-Debbugs-Cc: debian-ri...@lists.debian.org

Dear Maintainer,

I have checked the build-essential source packages that has contained 
essential-packages-list-riscv64 file. I am not sure this is enough 
to build build-essential riscv64 package.

The patch that support riscv64 I have tested it on my real riscv64
board. If there is more work to do please let me know, 

thanks.

-- 
Regards,
--
  Bo YU

diff -Nru build-essential-12.9/debian/control 
build-essential-12.9/debian/control
--- build-essential-12.9/debian/control 2021-01-03 10:23:06.0 +
+++ build-essential-12.9/debian/control 2021-01-03 10:23:06.0 +
@@ -164,6 +164,25 @@
  to build-depend on, you can always leave out the packages this
  package depends on.
 
+Package: crossbuild-essential-riscv64
+Architecture: all
+Depends: ${cross-essential}, ${misc:Depends}
+Description: Informational list of cross-build-essential packages
+ If you do not plan to cross build Debian packages, you don't need
+ this package.  Starting with sbuild (>= 0.63.0) this package is
+ required for cross building Debian packages in a chroot.
+ .
+ This package contains an informational list of packages which are
+ considered essential for cross building Debian packages.  This
+ package also depends on the packages on that list, to make it easy to
+ have the cross-build-essential packages installed.
+ .
+ If you have this package installed, you only need to install whatever
+ a package specifies as its build-time dependencies to cross build the
+ package.  Conversely, if you are determining what your package needs
+ to build-depend on, you can always leave out the packages this
+ package depends on.
+
 Package: crossbuild-essential-s390x
 Architecture: all
 Depends: ${cross-essential}, ${misc:Depends}


signature.asc
Description: PGP signature

Bug#1022539: librust-enumset-dev: impossible to install

[Jonas Smedegaard]

Package: librust-enumset-dev
Version: 1.0.11-1
Severity: grave
Justification: renders package unusable

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Package is impossible to install: Depends on missing package
librust-enumset-derive-0.6+default-dev (and more).

(I notice that rust-enumset-derive is currently pending in NEW queue,
which I guess will solve this).

 - Jonas

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmNVU5YACgkQLHwxRsGg
ASEDrg//c4ZbBpKDzswEz606GeK+vayIq+HiZyIlfOLwb4cUtTY/NwaRjL5H/D8i
BR0zeLge4H6p9FNZ+qa8fzEEzzynGoqhzBWaed1Eu0OiIy0bwWbDXntXZjUuvj1f
qXeRoIen4dYqQ/0mQhdjEfRZwrQM8Gt+dQuw7LHPdFY17knDH8pJiQkjmlQgheWg
VTh12xUymLJ6lV8gKjFBjhAC6myqihkTfCW1wW5GvilHYgknYcEBzyhRT4QvP4EA
A6W2b+S4xsnvydfm5zQNL0B4UToiMeI1p/OYdRFbGkHIJ6YiX8Tflh1Q3rq8Uz9r
98OW5VqD6iNtFk33pz56wndITwuFPMSgHI4Zs918f1Iy/mfqO5KuYYMbZakECNvP
UX2hY1mbd59U3o+vU4k1mzXqOJVxfV+xTRWs3icviODtW9NUnlf76tUoMCxzH+U+
7sbSOM9Rn+P8GhAK7jrwzbgUybGlFFJ2tI7+8jcgvaK2z+k+ceOiq2KXLt3QQtGH
StBK5OMvg8aelcwj65PfG7hiq/MnuExylH4K+u4+4zPTYdTt/N5i1uGxXdNejWH5
1P56Y6dfItbFSB3dC3ggIuuVLvZ0EhUavO4r54mjqRW8dCD2MekVFaV+2pqHY1Vq
EXXfcu/QMHSbdu8fGRT1W5fMeZd3yZLcuhQt/cv8ndTxXHbfz8A=
=ecoj
-END PGP SIGNATURE-

Bug#1020414: neomutt 20220429+dfsg1-3 is compiled without sasl support

[Marc Kleine-Budde]

Hello,

I just updated to 20220429+dfsg1-3 which should add/switch on gsasl
support to neomutt, but it seems it isn't:

regards,
Marc

| ➜ apt-cache policy neomutt
| neomutt:
|   Installed: 20220429+dfsg1-3
|   Candidate: 20220429+dfsg1-3
|   Version table:
|  *** 20220429+dfsg1-3 500
| 500 https://ftp.debian.org/debian sid/main amd64 Packages
| 100 /var/lib/dpkg/status
|  20220429+dfsg1-2 700
| 700 https://ftp.debian.org/debian bookworm/main amd64 Packages
|  20201127+dfsg.1-1.2 500
| 500 https://ftp.debian.org/debian bullseye/main amd64 Packages
|  20180716+dfsg.1-1+deb10u2 500
| 500 https://ftp.debian.org/debian buster/main amd64 Packages

| ➜ neomutt -v  
| NeoMutt 20220429
| Copyright (C) 1996-2022 Michael R. Elkins and others.
| NeoMutt comes with ABSOLUTELY NO WARRANTY; for details type 'neomutt -vv'.
| NeoMutt is free software, and you are welcome to redistribute it
| under certain conditions; type 'neomutt -vv' for details.
| 
| System: Linux 6.0.0-2-amd64 (x86_64)
| ncurses: ncurses 6.3.20220423 (compiled with 6.3.20220423)
| libidn: 1.41 (compiled with 1.41)
| GPGME: 1.18.0
| GnuTLS: 3.7.8
| libnotmuch: 5.6.0
| storage: tokyocabinet
| 
| Configure options: --build=x86_64-linux-gnu --prefix=/usr
| {--includedir=${prefix}/include} {--mandir=${prefix}/share/man}
| {--infodir=${prefix}/share/info} --sysconfdir=/etc
| --localstatedir=/var --disable-option-checking --disable-silent-rules
| {--libdir=${prefix}/lib/x86_64-linux-gnu} --runstatedir=/run
| --disable-maintainer-mode --disable-dependency-tracking
| --mandir=/usr/share/man --libexecdir=/usr/libexec
| --with-mailpath=/var/mail --gpgme --lua --notmuch --with-ui --gnutls
| --gss --idn --mixmaster --tokyocabinet --sqlite --autocrypt --pkgconf
| 
| Compilation CFLAGS: -g -O2
| -ffile-prefix-map=/build/neomutt-Zycsz5/neomutt-20220429+dfsg1=.
| -fstack-protector-strong -Wformat -Werror=format-security -std=c99
| -D_ALL_SOURCE=1 -D_GNU_SOURCE=1 -D__EXTENSIONS__ -I/usr/include/lua5.4
| -I/usr/include -DNCURSES_WIDECHAR -I/usr/include/p11-kit-1 -isystem
| /usr/include/mit-krb5
| 
| Default options:
|   +attach_headers_color +compose_to_sender +compress +cond_date +debug 
|   +encrypt_to_self +forgotten_attachments +forwref +ifdef +imap +index_color 
|   +initials +limit_current_thread +multiple_fcc +nested_if +new_mail +nntp 
+pop 
|   +progress +quasi_delete +regcomp +reply_with_xorig +sensible_browser 
+sidebar 
|   +skip_quoted +smtp +status_color +timeout +tls_sni +trash 
| 
| Compile options:
|   +autocrypt +fcntl -flock -fmemopen +futimens +getaddrinfo +gnutls +gpgme 
|   -gsasl +gss +hcache -homespool +idn +inotify -locales_hack +lua +mixmaster 
^^
|   +nls +notmuch -openssl +pgp +regex -sasl +smime +sqlite +sun_attachment 
   ^
| 
| MAILPATH="/var/mail"
| MIXMASTER="mixmaster"
| PKGDATADIR="/usr/share/neomutt"
| SENDMAIL="/usr/sbin/sendmail"
| SYSCONFDIR="/etc"
| 
| To learn more about NeoMutt, visit: https://neomutt.org
| If you find a bug in NeoMutt, please raise an issue at:
| https://github.com/neomutt/neomutt/issues
| or send an email to: 


signature.asc
Description: PGP signature

Bug#1022538: python-mbed-ls: FTBFS: TypeError: dist must be a Distribution instance

[Lucas Nussbaum]

Source: python-mbed-ls
Version: 1.6.2+dfsg-7
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221023 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_clean
>   install -d 
> /<>/python-mbed-ls-1.6.2\+dfsg/debian/.debhelper/generated/_source/home
>   pybuild --clean -i python{version} -p 3.10
> D: pybuild pybuild:587: version: 5.20221008
> D: pybuild pybuild:588: ['/usr/bin/pybuild', '--clean', '-i', 
> 'python{version}', '-p', '3.10']
> D: pybuild pybuild:38: cfg: Namespace(verbose=True, quiet=False, 
> really_quiet=False, detect_only=False, clean_only=True, configure_only=False, 
> build_only=False, install_only=False, test_only=False, list_systems=False, 
> print_args=None, before_clean=None, clean_args=None, after_clean=None, 
> before_configure=None, configure_args=None, after_configure=None, 
> before_build=None, build_args=None, after_build=None, before_install=None, 
> install_args=None, after_install=None, before_test=None, test_args=None, 
> after_test=None, test_nose=False, test_nose2=False, test_pytest=False, 
> test_tox=False, test_custom=False, dir='/<>', 
> destdir='debian/tmp', ext_destdir=None, ext_pattern='\\.so(\\.[^/]*)?$', 
> ext_sub_pattern=None, ext_sub_repl=None, install_dir=None, name='mbed_ls', 
> system=None, versions=['3.10'], interpreter=['python{version}'], 
> disable=None, custom_tests=False)
> D: pybuild __init__:37: cannot initialize 'cmake' plugin: Missing command 
> 'cmake'
> D: pybuild tools:232: invoking: /usr/bin/dpkg-architecture
> D: pybuild debhelper:141: skipping package: python-mbed-ls-doc
> D: pybuild debhelper:172: source=python-mbed-ls, binary 
> packages=['python3-mbed-ls']
> D: pybuild pybuild:122: Plugin custom: certainty 0
> D: pybuild pybuild:122: Plugin distutils: certainty 50
> D: pybuild pybuild:122: Plugin flit: certainty 0
> D: pybuild pybuild:122: Plugin pyproject: certainty 0
> D: pybuild pybuild:148: detected build system: distutils (certainty: 50%)
> D: pybuild plugin_distutils:54: pydistutils config file:
> [clean]
> all=1
> [build]
> build_lib=/<>/.pybuild/cpython3_3.10_mbed_ls/build
> [install]
> force=1
> install_layout=deb
> install_scripts=$base/bin
> install_lib=/usr/lib/python3.10/dist-packages
> prefix=/usr
> 
> I: pybuild base:240: python3.10 setup.py clean 
> D: pybuild tools:232: invoking: python3.10 setup.py clean 
> /<>/setup.py:23: DeprecationWarning: The distutils package is 
> deprecated and slated for removal in Python 3.12. Use setuptools or check PEP 
> 632 for potential alternatives
>   from distutils.core import setup
> /usr/lib/python3/dist-packages/_distutils_hack/__init__.py:18: UserWarning: 
> Distutils was imported before Setuptools, but importing Setuptools also 
> replaces the `distutils` module in `sys.modules`. This may lead to 
> undesirable behaviors or errors. To avoid these issues, avoid using distutils 
> directly, ensure that setuptools is installed in the traditional way (e.g. 
> not an editable install), and/or make sure that setuptools is always imported 
> before distutils.
>   warnings.warn(
> /usr/lib/python3/dist-packages/_distutils_hack/__init__.py:33: UserWarning: 
> Setuptools is replacing distutils.
>   warnings.warn("Setuptools is replacing distutils.")
> /usr/lib/python3.10/distutils/dist.py:274: UserWarning: Unknown distribution 
> option: 'test_suite'
>   warnings.warn(msg)
> /usr/lib/python3.10/distutils/dist.py:274: UserWarning: Unknown distribution 
> option: 'entry_points'
>   warnings.warn(msg)
> /usr/lib/python3.10/distutils/dist.py:274: UserWarning: Unknown distribution 
> option: 'install_requires'
>   warnings.warn(msg)
> /usr/lib/python3.10/distutils/dist.py:274: UserWarning: Unknown distribution 
> option: 'tests_require'
>   warnings.warn(msg)
> /usr/lib/python3.10/distutils/dist.py:274: UserWarning: Unknown distribution 
> option: 'extras_require'
>   warnings.warn(msg)
> running clean
> Traceback (most recent call last):
>   File "/<>/setup.py", line 36, in 
> setup(name='mbed-ls',
>   File "/usr/lib/python3.10/distutils/core.py", line 148, in setup
> dist.run_commands()
>   File "/usr/lib/python3.10/distutils/dist.py", line 966, in run_commands
> self.run_command(cmd)
>   File "/usr/lib/python3.10/distutils/dist.py", line 983, in run_command
> cmd_obj = self.get_command_obj(command)
>   File "/usr/lib/python3.10/distutils/dist.py", line 858, in get_command_obj
> cmd_obj = self.command_obj[command] = klass(self)
>   

Bug#1022508: [Debian-med-packaging] Bug#1022508: ariba: FTBFS: failed tests

[Étienne Mollier]

Control: retitle -1 ariba: ftbfs with samtools 1.16
Control: tags -1 patch

Hi,

This bug is the ftbfs counterpart of #1021675, which is about
ariba test failure following htslib upgrade.  There is a
workaround available, but it is unclear yet whether the change
in results are a problem from a usability point of view, or just
cosmetic.  Pending advice upstream.

Have a nice day,  :)
-- 
Étienne Mollier 
Fingerprint:  8f91 b227 c7d6 f2b1 948c  8236 793c f67e 8f0d 11da
Sent from /dev/pts/2, please excuse my verbosity.
On air: Sandstone (IE) - Silhouettes Drown


signature.asc
Description: PGP signature

Bug#1022537: python-grpc-tools: FTBFS: error: each element of 'ext_modules' option must be an Extension instance or 2-tuple

[Lucas Nussbaum]

Source: python-grpc-tools
Version: 1.14.1-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221023 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
>  debian/rules binary
> dh binary  --with python3 --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:240: python3.10 setup.py config 
> /<>/setup.py:15: DeprecationWarning: The distutils package is 
> deprecated and slated for removal in Python 3.12. Use setuptools or check PEP 
> 632 for potential alternatives
>   from distutils import cygwinccompiler
> /usr/lib/python3/dist-packages/_distutils_hack/__init__.py:18: UserWarning: 
> Distutils was imported before Setuptools, but importing Setuptools also 
> replaces the `distutils` module in `sys.modules`. This may lead to 
> undesirable behaviors or errors. To avoid these issues, avoid using distutils 
> directly, ensure that setuptools is installed in the traditional way (e.g. 
> not an editable install), and/or make sure that setuptools is always imported 
> before distutils.
>   warnings.warn(
> /usr/lib/python3/dist-packages/_distutils_hack/__init__.py:33: UserWarning: 
> Setuptools is replacing distutils.
>   warnings.warn("Setuptools is replacing distutils.")
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:240: /usr/bin/python3 setup.py build 
> /<>/setup.py:15: DeprecationWarning: The distutils package is 
> deprecated and slated for removal in Python 3.12. Use setuptools or check PEP 
> 632 for potential alternatives
>   from distutils import cygwinccompiler
> /usr/lib/python3/dist-packages/_distutils_hack/__init__.py:18: UserWarning: 
> Distutils was imported before Setuptools, but importing Setuptools also 
> replaces the `distutils` module in `sys.modules`. This may lead to 
> undesirable behaviors or errors. To avoid these issues, avoid using distutils 
> directly, ensure that setuptools is installed in the traditional way (e.g. 
> not an editable install), and/or make sure that setuptools is always imported 
> before distutils.
>   warnings.warn(
> /usr/lib/python3/dist-packages/_distutils_hack/__init__.py:33: UserWarning: 
> Setuptools is replacing distutils.
>   warnings.warn("Setuptools is replacing distutils.")
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.10_grpcio-tools/build/grpc_tools
> copying grpc_tools/__init__.py -> 
> /<>/.pybuild/cpython3_3.10_grpcio-tools/build/grpc_tools
> copying grpc_tools/protoc.py -> 
> /<>/.pybuild/cpython3_3.10_grpcio-tools/build/grpc_tools
> copying grpc_tools/command.py -> 
> /<>/.pybuild/cpython3_3.10_grpcio-tools/build/grpc_tools
> creating 
> /<>/.pybuild/cpython3_3.10_grpcio-tools/build/grpc_tools/_proto
> creating 
> /<>/.pybuild/cpython3_3.10_grpcio-tools/build/grpc_tools/_proto/google
> creating 
> /<>/.pybuild/cpython3_3.10_grpcio-tools/build/grpc_tools/_proto/google/protobuf
> copying grpc_tools/_proto/google/protobuf/wrappers.proto -> 
> /<>/.pybuild/cpython3_3.10_grpcio-tools/build/grpc_tools/_proto/google/protobuf
> copying grpc_tools/_proto/google/protobuf/type.proto -> 
> /<>/.pybuild/cpython3_3.10_grpcio-tools/build/grpc_tools/_proto/google/protobuf
> copying grpc_tools/_proto/google/protobuf/timestamp.proto -> 
> /<>/.pybuild/cpython3_3.10_grpcio-tools/build/grpc_tools/_proto/google/protobuf
> copying grpc_tools/_proto/google/protobuf/struct.proto -> 
> /<>/.pybuild/cpython3_3.10_grpcio-tools/build/grpc_tools/_proto/google/protobuf
> copying grpc_tools/_proto/google/protobuf/source_context.proto -> 
> /<>/.pybuild/cpython3_3.10_grpcio-tools/build/grpc_tools/_proto/google/protobuf
> copying grpc_tools/_proto/google/protobuf/field_mask.proto -> 
> /<>/.pybuild/cpython3_3.10_grpcio-tools/build/grpc_tools/_proto/google/protobuf
> copying grpc_tools/_proto/google/protobuf/empty.proto -> 
> /<>/.pybuild/cpython3_3.10_grpcio-tools/build/grpc_tools/_proto/google/protobuf
> copying grpc_tools/_proto/google/protobuf/duration.proto -> 
> /<>/.pybuild/cpython3_3.10_grpcio-tools/build/grpc_tools/_proto/google/protobuf
> copying grpc_tools/_proto/google/protobuf/descriptor.proto -> 
> /<>/.pybuild/cpython3_3.10_grpcio-tools/build/grpc_tools/_proto/google/protobuf
> creating 
> /<>/.pybuild/cpython3_3.10_grpcio-tools/build/grpc_tools/_proto/google/protobuf/compiler
> copying grpc_tools/_proto/google/protobuf/compiler/plugin.proto -> 
> /

Bug#1022536: postgresql-rum: FTBFS: Error: debian/control needs updating from debian/control.in. Run 'pg_buildext updatecontrol'.

[Lucas Nussbaum]

Source: postgresql-rum
Version: 1.3.11-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221023 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> rm -f rum.so   librum.a  librum.pc
> rm -f src/rumsort.o src/rum_ts_utils.o src/rumtsquery.o src/rumbtree.o 
> src/rumbulk.o src/rumdatapage.o src/rumentrypage.o src/rumget.o 
> src/ruminsert.o src/rumscan.o src/rumutil.o src/rumvacuum.o src/rumvalidate.o 
> src/btree_rum.o src/rum_arr_utils.o  src/rumsort.bc src/rum_ts_utils.bc 
> src/rumtsquery.bc src/rumbtree.bc src/rumbulk.bc src/rumdatapage.bc 
> src/rumentrypage.bc src/rumget.bc src/ruminsert.bc src/rumscan.bc 
> src/rumutil.bc src/rumvacuum.bc src/rumvalidate.bc src/btree_rum.bc 
> src/rum_arr_utils.bc
> rm -rf results/ regression.diffs regression.out tmp_check/ tmp_check_iso/ 
> log/ output_iso/
> make[1]: Leaving directory '/<>'
>dh_clean
>pg_buildext checkcontrol
> --- debian/control2021-10-26 12:06:36.0 +
> +++ debian/control.vOrOQk 2022-10-23 07:36:01.483367125 +
> @@ -13,9 +13,9 @@
>  Vcs-Browser: https://salsa.debian.org/postgresql/postgresql-rum
>  Vcs-Git: https://salsa.debian.org/postgresql/postgresql-rum.git
>  
> -Package: postgresql-14-rum
> +Package: postgresql-15-rum
>  Architecture: any
> -Depends: postgresql-14, ${misc:Depends}, ${shlibs:Depends}
> +Depends: postgresql-15, ${misc:Depends}, ${shlibs:Depends}
>  Description: PostgreSQL RUM access method
>   This PostgreSQL extension provides the RUM access method, an inverted index
>   with additional information in posting lists.
> Error: debian/control needs updating from debian/control.in. Run 'pg_buildext 
> updatecontrol'.
> If you are seeing this message in a buildd log, a sourceful upload is 
> required.
> make: *** [debian/rules:7: clean] Error 1


The full build log is available from:
http://qa-logs.debian.net/2022/10/23/postgresql-rum_1.3.11-1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20221023;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20221023=lu...@debian.org=1=1=1=1#results

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

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

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.

Bug#1022535: pg-repack: FTBFS: Error: debian/control needs updating from debian/control.in. Run 'pg_buildext updatecontrol'.

[Lucas Nussbaum]

Source: pg-repack
Version: 1.4.7-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221023 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[2]: Entering directory '/<>/regress'
> rm -rf results/ regression.diffs regression.out tmp_check/ tmp_check_iso/ 
> log/ output_iso/
> make[2]: Leaving directory '/<>/regress'
> make[1]: Leaving directory '/<>'
>dh_clean
>pg_buildext checkcontrol
> --- debian/control2021-10-15 13:17:07.0 +
> +++ debian/control.uNZ0nv 2022-10-23 07:35:13.668024234 +
> @@ -11,9 +11,9 @@
>  Vcs-Browser: https://salsa.debian.org/postgresql/pg-repack
>  Vcs-Git: https://salsa.debian.org/postgresql/pg-repack.git
>  
> -Package: postgresql-14-repack
> +Package: postgresql-15-repack
>  Architecture: any
> -Depends: postgresql-14, ${shlibs:Depends}, ${misc:Depends}
> +Depends: postgresql-15, ${shlibs:Depends}, ${misc:Depends}
>  Description: reorganize tables in PostgreSQL databases with minimal locks
>   pg_repack is a PostgreSQL extension which lets you remove bloat from tables
>   and indexes, and optionally restore the physical order of clustered indexes.
> @@ -22,4 +22,4 @@
>   boot, with performance comparable to using CLUSTER directly.
>   .
>   This package contains the pg_repack program and the server extension for
> - PostgreSQL 14.
> + PostgreSQL 15.
> Error: debian/control needs updating from debian/control.in. Run 'pg_buildext 
> updatecontrol'.
> If you are seeing this message in a buildd log, a sourceful upload is 
> required.
> make: *** [debian/rules:24: clean] Error 1


The full build log is available from:
http://qa-logs.debian.net/2022/10/23/pg-repack_1.4.7-2_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20221023;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20221023=lu...@debian.org=1=1=1=1#results

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

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

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.

Bug#1022534: yaramod: FTBFS: distutils.errors.DistutilsClassError: command class must subclass Command

[Lucas Nussbaum]

Source: yaramod
Version: 3.6.0-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221023 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[4]: Entering directory '/<>/obj-x86_64-linux-gnu'
> [ 76%] Building CXX object 
> src/python/CMakeFiles/yaramod-python.dir/py_visitor.cpp.o
> [ 79%] Building CXX object 
> src/python/CMakeFiles/yaramod-python.dir/yaramod_python.cpp.o
> cd /<>/obj-x86_64-linux-gnu/src/python && /usr/bin/c++ 
> -DFMT_SHARED -Dyaramod_python_EXPORTS -isystem /usr/include/python3.10 
> -isystem /<>/include -isystem 
> /<>/obj-x86_64-linux-gnu/src -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wall -pedantic -Wdate-time -D_FORTIFY_SOURCE=2 -Wall 
> -Wextra -fPIC -fvisibility=hidden -Wall -Wextra -Wno-empty-body -pthread 
> -std=gnu++17 -MD -MT 
> src/python/CMakeFiles/yaramod-python.dir/py_visitor.cpp.o -MF 
> CMakeFiles/yaramod-python.dir/py_visitor.cpp.o.d -o 
> CMakeFiles/yaramod-python.dir/py_visitor.cpp.o -c 
> /<>/src/python/py_visitor.cpp
> cd /<>/obj-x86_64-linux-gnu/src/python && /usr/bin/c++ 
> -DFMT_SHARED -Dyaramod_python_EXPORTS -isystem /usr/include/python3.10 
> -isystem /<>/include -isystem 
> /<>/obj-x86_64-linux-gnu/src -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wall -pedantic -Wdate-time -D_FORTIFY_SOURCE=2 -Wall 
> -Wextra -fPIC -fvisibility=hidden -Wall -Wextra -Wno-empty-body -pthread 
> -std=gnu++17 -MD -MT 
> src/python/CMakeFiles/yaramod-python.dir/yaramod_python.cpp.o -MF 
> CMakeFiles/yaramod-python.dir/yaramod_python.cpp.o.d -o 
> CMakeFiles/yaramod-python.dir/yaramod_python.cpp.o -c 
> /<>/src/python/yaramod_python.cpp
> [ 83%] Building CXX object 
> tests/cpp/CMakeFiles/yaramod_tests.dir/representation_tests.cpp.o
> [ 83%] Building CXX object 
> tests/cpp/CMakeFiles/yaramod_tests.dir/builder_tests.cpp.o
> cd /<>/obj-x86_64-linux-gnu/tests/cpp && /usr/bin/c++ 
> -DFMT_SHARED -I/<>/tests/cpp -isystem /<>/include 
> -isystem /<>/obj-x86_64-linux-gnu/src -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wall -pedantic -Wdate-time -D_FORTIFY_SOURCE=2 -Wall 
> -Wextra -fPIE -Wall -Wextra -Wno-empty-body -pthread -DGTEST_HAS_PTHREAD=1 
> -std=gnu++17 -MD -MT 
> tests/cpp/CMakeFiles/yaramod_tests.dir/builder_tests.cpp.o -MF 
> CMakeFiles/yaramod_tests.dir/builder_tests.cpp.o.d -o 
> CMakeFiles/yaramod_tests.dir/builder_tests.cpp.o -c 
> /<>/tests/cpp/builder_tests.cpp
> [ 86%] Building CXX object 
> tests/cpp/CMakeFiles/yaramod_tests.dir/trie_tests.cpp.o
> cd /<>/obj-x86_64-linux-gnu/tests/cpp && /usr/bin/c++ 
> -DFMT_SHARED -I/<>/tests/cpp -isystem /<>/include 
> -isystem /<>/obj-x86_64-linux-gnu/src -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wall -pedantic -Wdate-time -D_FORTIFY_SOURCE=2 -Wall 
> -Wextra -fPIE -Wall -Wextra -Wno-empty-body -pthread -DGTEST_HAS_PTHREAD=1 
> -std=gnu++17 -MD -MT 
> tests/cpp/CMakeFiles/yaramod_tests.dir/representation_tests.cpp.o -MF 
> CMakeFiles/yaramod_tests.dir/representation_tests.cpp.o.d -o 
> CMakeFiles/yaramod_tests.dir/representation_tests.cpp.o -c 
> /<>/tests/cpp/representation_tests.cpp
> cd /<>/obj-x86_64-linux-gnu/tests/cpp && /usr/bin/c++ 
> -DFMT_SHARED -I/<>/tests/cpp -isystem /<>/include 
> -isystem /<>/obj-x86_64-linux-gnu/src -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wall -pedantic -Wdate-time -D_FORTIFY_SOURCE=2 -Wall 
> -Wextra -fPIE -Wall -Wextra -Wno-empty-body -pthread -DGTEST_HAS_PTHREAD=1 
> -std=gnu++17 -MD -MT tests/cpp/CMakeFiles/yaramod_tests.dir/trie_tests.cpp.o 
> -MF CMakeFiles/yaramod_tests.dir/trie_tests.cpp.o.d -o 
> CMakeFiles/yaramod_tests.dir/trie_tests.cpp.o -c 
> /<>/tests/cpp/trie_tests.cpp
> [ 90%] Building CXX object 
> tests/cpp/CMakeFiles/yaramod_tests.dir/tokenstream_tests.cpp.o
> [ 90%] Building CXX object 
> tests/cpp/CMakeFiles/yaramod_tests.dir/parser_tests.cpp.o
> cd /<>/obj-x86_64-linux-gnu/tests/cpp && /usr/bin/c++ 
> -DFMT_SHARED -I/<>/tests/cpp -isystem /<>/include 
> -isystem /<>/obj-x86_64-linux-gnu/src -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wall -pedantic -Wdate-time -D_FORTIFY_SOURCE=2 -Wall 
> -Wextra -fPIE -Wall -Wextra -Wno-empty-body -pthread -DGTEST_H

Bug#1022533: foot: missing dependency on libutf8proc

[Andrea Pappacoda]

Package: foot
Version: 1.13.1-1
Severity: normal
Tags: patch

Hi, foot is currently compiled without grapheme clustering, as its
debian/control file doesn't specify libutf8proc-dev in its Build-Depe
ndencies. You can check this by running:

$ foot --version
foot version: 1.13.1 -pgo +ime -graphemes -assertions

It'd be also great if you'd consider building with PGO (Profile-Guided
Optimizations), as upstream recommends doing so to optimize foot'
s latency; a set of scripts is provided to make use of PGO relatively easy. But
that's another issue :)

For more information about foot and it's build process, see upstream's
INSTALL.md file: 

I've included a patch fixing this issue; I've also added systemd to the list of
Build-Dependencies, as upstream's build process only installs systemd unit
files if systemd's pkg-config file is installed on the build machine.


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

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

Versions of packages foot depends on:
ii  foot-terminfo   1.13.1-1
ii  libc6   2.35-3
ii  libfcft43.1.5-1
ii  libfontconfig1  2.13.1-4.5
ii  libpixman-1-0   0.40.0-1
ii  libwayland-client0  1.21.0-1
ii  libwayland-cursor0  1.21.0-1
ii  libxkbcommon0   1.4.1-1

foot recommends no packages.

Versions of packages foot suggests:
ii  foot-themes  1.13.1-1

-- no debconf information
>From 992785e5cc35385688dd9239d9d9a4dcaa9078e3 Mon Sep 17 00:00:00 2001
From: Andrea Pappacoda 
Date: Sun, 23 Oct 2022 16:20:52 +0200
Subject: [PATCH] d/control: enable grapheme clustering

---
 debian/control | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/debian/control b/debian/control
index 4ee1c340..80c29701 100644
--- a/debian/control
+++ b/debian/control
@@ -16,6 +16,8 @@ Build-Depends: debhelper-compat (= 13),
libfcft-dev (>= 3.0.0),
libffi-dev,
libharfbuzz-dev,
+   libutf8proc-dev,
+   systemd [linux-any],
scdoc
 Standards-Version: 4.6.1.0
 Homepage: https://codeberg.org/dnkl/foot
-- 
2.35.1

Bug#1022532: wal2json: FTBFS: Error: debian/control needs updating from debian/control.in. Run 'pg_buildext updatecontrol'.

[Lucas Nussbaum]

Source: wal2json
Version: 2.4-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221023 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> rm -f wal2json.so wal2json.o  \
> wal2json.bc
> rm -rf results/ regression.diffs regression.out tmp_check/ tmp_check_iso/ 
> log/ output_iso/
> make[1]: Leaving directory '/<>'
>dh_clean
>pg_buildext checkcontrol
> --- debian/control2021-10-21 10:17:45.0 +
> +++ debian/control.Auey67 2022-10-23 07:37:13.244976439 +
> @@ -14,10 +14,10 @@
>  Vcs-Git: https://salsa.debian.org/postgresql/wal2json.git
>  Vcs-Browser: https://salsa.debian.org/postgresql/wal2json
>  
> -Package: postgresql-14-wal2json
> +Package: postgresql-15-wal2json
>  Architecture: any
>  Depends:
> - postgresql-14,
> + postgresql-15,
>   ${misc:Depends},
>   ${shlibs:Depends},
>  Description: PostgreSQL logical decoding JSON output plugin
> Error: debian/control needs updating from debian/control.in. Run 'pg_buildext 
> updatecontrol'.
> If you are seeing this message in a buildd log, a sourceful upload is 
> required.
> make: *** [debian/rules:12: clean] Error 1


The full build log is available from:
http://qa-logs.debian.net/2022/10/23/wal2json_2.4-2_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20221023;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20221023=lu...@debian.org=1=1=1=1#results

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

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

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.

Bug#1022531: soundgrain: FTBFS: error: Multiple top-level packages discovered in a flat-layout: ['debian', 'Resources'].

[Lucas Nussbaum]

Source: soundgrain
Version: 6.0.1-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221023 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
>  debian/rules build
> dh build --with python3 --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:240: python3.10 setup.py config 
> error: Multiple top-level packages discovered in a flat-layout: ['debian', 
> 'Resources'].
> 
> To avoid accidental inclusion of unwanted files or directories,
> setuptools will not proceed with this build.
> 
> If you are trying to create a single distribution with multiple packages
> on purpose, you should not rely on automatic discovery.
> Instead, consider the following options:
> 
> 1. set up custom discovery (`find` directive with `include` or `exclude`)
> 2. use a `src-layout`
> 3. explicitly set `py_modules` or `packages` with a list of names
> 
> To find more information, look for "package discovery" on setuptools docs.
> E: pybuild pybuild:379: configure: plugin distutils failed with: exit code=1: 
> python3.10 setup.py config 
> dh_auto_configure: error: pybuild --configure -i python{version} -p 3.10 
> returned exit code 13
> make: *** [debian/rules:4: build] Error 25


The full build log is available from:
http://qa-logs.debian.net/2022/10/23/soundgrain_6.0.1-2_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20221023;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20221023=lu...@debian.org=1=1=1=1#results

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

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

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.

Bug#1022530: src:salt: autopkgtest timeouts

[Paul Gevers]

Source: salt
Version: 3004.1+dfsg-2
Severity: serious
User: debian...@lists.debian.org
Usertags: timeout

Dear maintainer(s),

Your package has an autopkgtest, great. However, it fails. What's worse, 
it fails because it seems to hang and eventually times out due to 
autopkgtest. This happens since the beginning of October 2022. Can you 
please investigate the situation and fix it? I copied some of the output 
at the bottom of this report.


The release team has announced [1] that failing autopkgtest on amd64 and 
arm64 are considered RC in testing. Also tests that time out (while 
normally running in much less time) are bad for our infrastructure. I 
have added your package to our reject_list and will remove it once this 
bug is closed.


More information about this bug and the reason for filing it can be 
found on 
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation


Paul

[1] https://lists.debian.org/debian-devel-announce/2019/07/msg2.html

https://ci.debian.net/packages/s/salt/unstable/amd64/

https://ci.debian.net/data/autopkgtest/unstable/amd64/s/salt/27450067/log.gz

= test session starts 
==

platform linux -- Python 3.10.7, pytest-7.1.2, pluggy-1.0.0+repack
tempdir: /tmp/stsuite
max open files; soft: 3072; hard: 1048576
rootdir: /tmp/autopkgtest-lxc.bmdfc2kz/downtmp/autopkgtest_tmp
plugins: salt-factories-0.907.0, subtests-0.8.0, 
helpers-namespace-2021.4.29, skip-markers-1.3.0, tempdir-2019.10.12

collected 3896 items / 4 skipped

tests/pytests/functional/test_loader.py ss 
[  0%]
tests/pytests/functional/test_payload.py  
[  0%]
tests/pytests/functional/test_version.py ss 
[  0%]
tests/pytests/functional/cli/test_api.py s 
[  0%]
tests/pytests/functional/cli/test_batch.py . 
[  0%]
tests/pytests/functional/cli/test_salt_cloud.py . 
[  0%]
tests/pytests/functional/cli/test_salt_master.py ss 
[  0%]
tests/pytests/functional/fileserver/test_roots.py . 
[  0%]
tests/pytests/functional/logging/handlers/test_logstash_mod.py sF 
[  0%]
tests/pytests/functional/modules/test_aliases.py  
[  0%]
tests/pytests/functional/modules/test_ansiblegate.py ss 
[  0%]
tests/pytests/functional/modules/test_aptpkg.py autopkgtest [10:22:36]: 
ERROR: timed out on command "su -s /bin/bash debci -c set -e; export 
USER=`id -nu`; . /etc/profile >/dev/null 2>&1 || true;  . ~/.profile 
>/dev/null 2>&1 || true; 
buildtree="/tmp/autopkgtest-lxc.bmdfc2kz/downtmp/build.aQS/src"; mkdir 
-p -m 1777 -- 
"/tmp/autopkgtest-lxc.bmdfc2kz/downtmp/unittest-artifacts"; export 
AUTOPKGTEST_ARTIFACTS="/tmp/autopkgtest-lxc.bmdfc2kz/downtmp/unittest-artifacts"; 
export ADT_ARTIFACTS="$AUTOPKGTEST_ARTIFACTS"; mkdir -p -m 755 
"/tmp/autopkgtest-lxc.bmdfc2kz/downtmp/autopkgtest_tmp"; export 
AUTOPKGTEST_TMP="/tmp/autopkgtest-lxc.bmdfc2kz/downtmp/autopkgtest_tmp"; 
export ADTTMP="$AUTOPKGTEST_TMP"; export DEBIAN_FRONTEND=noninteractive; 
export LANG=C.UTF-8; export DEB_BUILD_OPTIONS=parallel=64; unset 
LANGUAGE LC_CTYPE LC_NUMERIC LC_TIME LC_COLLATE   LC_MONETARY 
LC_MESSAGES LC_PAPER LC_NAME LC_ADDRESS   LC_TELEPHONE LC_MEASUREMENT 
LC_IDENTIFICATION LC_ALL;cd "$buildtree"; exec 
/tmp/autopkgtest-lxc.bmdfc2kz/downtmp/wrapper.sh 
--script-pid-file=/tmp/autopkgtest_script_pid 
--stderr=/tmp/autopkgtest-lxc.bmdfc2kz/downtmp/unittest-stderr 
--stdout=/tmp/autopkgtest-lxc.bmdfc2kz/downtmp/unittest-stdout -- bash 
-ec 'cp -r conf scripts tests "$AUTOPKGTEST_TMP"; cd "$AUTOPKGTEST_TMP"; 
LC_ALL=C.UTF-8 NO_INTERNET=1 python3 -m pytest -ra 
tests/pytests/functional tests/pytests/integration tests/pytests/unit' 
;" (kind: test)

autopkgtest [10:22:36]: test unittest: ---]


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1022529: ITP: golang-github-ionos-cloud-sdk-go -- Go API client for IONOS Cloud

[Daniel Swarbrick]

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

* Package name: golang-github-ionos-cloud-sdk-go
  Version : 6.1.3-1
  Upstream Author : IONOS Cloud
* URL : https://github.com/ionos-cloud/sdk-go
* License : Apache-2.0
  Programming Lang: Go
  Description : Go API client for IONOS Cloud

IONOS enterprise-grade Infrastructure as a Service (IaaS) solutions can
be managed through the Cloud API, in addition to or as an alternative to
the "Data Center Designer" (DCD) browser-based tool.
.
The IONOS Cloud SDK for Go provides programmatic access to the IONOS
Cloud API.

This package is required to support IONOS Cloud service discovery in
Prometheus. I will co-maintain this package as part of the Debian Go
Packaging Team.

Bug#1022061: debian-kernel-handbook: improve kernel build steps for newbies

[Diederik de Haas]

Hi Dan!

Thanks so much for your description, it already gives me some ideas how to 
improve things wrt the documentation :-)

On Wednesday, 19 October 2022 23:56:23 CEST Dan Coleman wrote:
> use test-patches in debian/bin/test-patches.

>From bug 1022025:

On Thursday, 20 October 2022 21:48:20 CEST Diederik de Haas wrote:
> On Thursday, 20 October 2022 19:53:22 CEST Dan Coleman wrote:
> > > Apparently "test-patches" does not build a 'headers-common' package and
> > > therefor installing the headers failed which in turn made DKMS fail.
> > 
> > That seems like less-than-ideal behavior for test-patches.
> > Is that a bug that would benefit from being reported?

I (now) do think it is useful to file a (wishlist) bug against src:linux in 
which you request improvements to the 'test-patches' script:
1) also creates a headers-common package.

> When I finally managed to get the test kernel compiled, I couldn't install
> it, either via apt or dpkg. I was told that apt would take care of removing
> the dependencies causing the conflict, but it didn't. DKMS wasn't
> triggered, it was a mess.

2) make it easy/easier to install the resulting kernel deb, which does not 
involve removing an existing kernel (meta) package.

By setting the 'abiname' 'property' you can achieve that, but I don't know if 
that idea has been evaluated before and discarded.
But the kernel maintainers should be able to answer that.

Cheers,
  Diederik

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

Bug#1022528: postgresql-plproxy: FTBFS: Error: debian/control needs updating from debian/control.in. Run 'pg_buildext updatecontrol'.

[Lucas Nussbaum]

Source: postgresql-plproxy
Version: 2.10.0-7
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221023 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> rm -f plproxy.so   libplproxy.a  libplproxy.pc
> rm -f sql/plproxy--2.10.0.sql sql/plproxy--2.3.0--2.10.0.sql 
> sql/plproxy--2.4.0--2.10.0.sql sql/plproxy--2.5.0--2.10.0.sql 
> sql/plproxy--2.6.0--2.10.0.sql sql/plproxy--2.7.0--2.10.0.sql 
> sql/plproxy--2.8.0--2.10.0.sql sql/plproxy--2.9.0--2.10.0.sql
> rm -f src/scanner.o src/parser.tab.o src/cluster.o src/execute.o 
> src/function.o src/main.o src/query.o src/result.o src/type.o src/aatree.o 
> src/scanner.bc src/parser.tab.bc src/cluster.bc src/execute.bc 
> src/function.bc src/main.bc src/query.bc src/result.bc src/type.bc 
> src/aatree.bc
> rm -rf src/scanner.[ch] src/parser.tab.[ch] libplproxy.* plproxy.so
> rm -rf results/ regression.diffs regression.out tmp_check/ tmp_check_iso/ 
> log/ output_iso/
> make[1]: Leaving directory '/<>'
>dh_clean
>pg_buildext checkcontrol
> --- debian/control2021-09-30 19:20:40.0 +
> +++ debian/control.w50745 2022-10-23 07:28:48.959081164 +
> @@ -13,10 +13,10 @@
>  Vcs-Git: https://salsa.debian.org/postgresql/postgresql-plproxy.git
>  Vcs-Browser: https://salsa.debian.org/postgresql/postgresql-plproxy
>  
> -Package: postgresql-14-plproxy
> +Package: postgresql-15-plproxy
>  Architecture: any
> -Depends: postgresql-14, ${misc:Depends}, ${shlibs:Depends}
> -Description: database partitioning system for PostgreSQL 14
> +Depends: postgresql-15, ${misc:Depends}, ${shlibs:Depends}
> +Description: database partitioning system for PostgreSQL 15
>   PL/Proxy is a database partitioning system implemented as a PL language. 
> Main
>   idea is that proxy functions are created with same signature as the remote
>   functions to be called, so only destination info needs to be specified 
> inside
> Error: debian/control needs updating from debian/control.in. Run 'pg_buildext 
> updatecontrol'.
> If you are seeing this message in a buildd log, a sourceful upload is 
> required.
> make: *** [debian/rules:18: clean] Error 1


The full build log is available from:
http://qa-logs.debian.net/2022/10/23/postgresql-plproxy_2.10.0-7_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20221023;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20221023=lu...@debian.org=1=1=1=1#results

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

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

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.

Bug#1022527: ddupdate: FTBFS: distutils.errors.DistutilsClassError: command class must subclass Command

[Lucas Nussbaum]

Source: ddupdate
Version: 0.6.6-1.1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221023 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
>  debian/rules clean
> dh clean  --with python3 --buildsystem=pybuild
>dh_auto_clean -O--buildsystem=pybuild
> I: pybuild base:240: python3.10 setup.py clean 
> /<>/setup.py:7: DeprecationWarning: The distutils package is 
> deprecated and slated for removal in Python 3.12. Use setuptools or check PEP 
> 632 for potential alternatives
>   from distutils.command.clean import clean
> /usr/lib/python3/dist-packages/_distutils_hack/__init__.py:18: UserWarning: 
> Distutils was imported before Setuptools, but importing Setuptools also 
> replaces the `distutils` module in `sys.modules`. This may lead to 
> undesirable behaviors or errors. To avoid these issues, avoid using distutils 
> directly, ensure that setuptools is installed in the traditional way (e.g. 
> not an editable install), and/or make sure that setuptools is always imported 
> before distutils.
>   warnings.warn(
> /usr/lib/python3/dist-packages/_distutils_hack/__init__.py:33: UserWarning: 
> Setuptools is replacing distutils.
>   warnings.warn("Setuptools is replacing distutils.")
> Traceback (most recent call last):
>   File "/<>/setup.py", line 77, in 
> setup(
>   File "/usr/lib/python3/dist-packages/setuptools/__init__.py", line 87, in 
> setup
> return distutils.core.setup(**attrs)
>   File "/usr/lib/python3/dist-packages/setuptools/_distutils/core.py", line 
> 172, in setup
> ok = dist.parse_command_line()
>   File "/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py", line 
> 474, in parse_command_line
> args = self._parse_command_opts(parser, args)
>   File "/usr/lib/python3/dist-packages/setuptools/dist.py", line 1107, in 
> _parse_command_opts
> nargs = _Distribution._parse_command_opts(self, parser, args)
>   File "/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py", line 
> 540, in _parse_command_opts
> raise DistutilsClassError(
> distutils.errors.DistutilsClassError: command class  '__main__._ProjectClean'> must subclass Command
> E: pybuild pybuild:379: clean: plugin distutils failed with: exit code=1: 
> python3.10 setup.py clean 
> dh_auto_clean: error: pybuild --clean -i python{version} -p 3.10 returned 
> exit code 13
> make: *** [debian/rules:11: clean] Error 25


The full build log is available from:
http://qa-logs.debian.net/2022/10/23/ddupdate_0.6.6-1.1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20221023;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20221023=lu...@debian.org=1=1=1=1#results

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

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

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.

Bug#1022526: python-ssdeep: FTBFS: distutils.errors.DistutilsClassError: command class must subclass Command

[Lucas Nussbaum]

Source: python-ssdeep
Version: 3.1+dfsg-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221023 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
>  debian/rules binary
> dh binary --with python3 --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:240: python3.10 setup.py config 
> /<>/setup.py:7: DeprecationWarning: The distutils package is 
> deprecated and slated for removal in Python 3.12. Use setuptools or check PEP 
> 632 for potential alternatives
>   from distutils.command.build import build
> /usr/lib/python3/dist-packages/_distutils_hack/__init__.py:18: UserWarning: 
> Distutils was imported before Setuptools, but importing Setuptools also 
> replaces the `distutils` module in `sys.modules`. This may lead to 
> undesirable behaviors or errors. To avoid these issues, avoid using distutils 
> directly, ensure that setuptools is installed in the traditional way (e.g. 
> not an editable install), and/or make sure that setuptools is always imported 
> before distutils.
>   warnings.warn(
> /usr/lib/python3/dist-packages/_distutils_hack/__init__.py:33: UserWarning: 
> Setuptools is replacing distutils.
>   warnings.warn("Setuptools is replacing distutils.")
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:240: /usr/bin/python3 setup.py build 
> /<>/setup.py:7: DeprecationWarning: The distutils package is 
> deprecated and slated for removal in Python 3.12. Use setuptools or check PEP 
> 632 for potential alternatives
>   from distutils.command.build import build
> /usr/lib/python3/dist-packages/_distutils_hack/__init__.py:18: UserWarning: 
> Distutils was imported before Setuptools, but importing Setuptools also 
> replaces the `distutils` module in `sys.modules`. This may lead to 
> undesirable behaviors or errors. To avoid these issues, avoid using distutils 
> directly, ensure that setuptools is installed in the traditional way (e.g. 
> not an editable install), and/or make sure that setuptools is always imported 
> before distutils.
>   warnings.warn(
> /usr/lib/python3/dist-packages/_distutils_hack/__init__.py:33: UserWarning: 
> Setuptools is replacing distutils.
>   warnings.warn("Setuptools is replacing distutils.")
> Traceback (most recent call last):
>   File "/<>/setup.py", line 87, in 
> setup(
>   File "/usr/lib/python3/dist-packages/setuptools/__init__.py", line 87, in 
> setup
> return distutils.core.setup(**attrs)
>   File "/usr/lib/python3/dist-packages/setuptools/_distutils/core.py", line 
> 172, in setup
> ok = dist.parse_command_line()
>   File "/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py", line 
> 474, in parse_command_line
> args = self._parse_command_opts(parser, args)
>   File "/usr/lib/python3/dist-packages/setuptools/dist.py", line 1107, in 
> _parse_command_opts
> nargs = _Distribution._parse_command_opts(self, parser, args)
>   File "/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py", line 
> 540, in _parse_command_opts
> raise DistutilsClassError(
> distutils.errors.DistutilsClassError: command class  '__main__.CFFIBuild'> must subclass Command
> E: pybuild pybuild:379: build: plugin distutils failed with: exit code=1: 
> /usr/bin/python3 setup.py build 
> dh_auto_build: error: pybuild --build -i python{version} -p 3.10 returned 
> exit code 13
> make: *** [debian/rules:5: binary] Error 25


The full build log is available from:
http://qa-logs.debian.net/2022/10/23/python-ssdeep_3.1+dfsg-3_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20221023;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20221023=lu...@debian.org=1=1=1=1#results

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

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

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.

Bug#1022525: python-cbor: FTBFS: distutils.errors.DistutilsSetupError: each element of 'ext_modules' option must be an Extension instance or 2-tuple

[Lucas Nussbaum]

Source: python-cbor
Version: 1.0.0-1.1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221023 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
>  debian/rules build
> dh build --with python3 --buildsystem=pybuild
> dh: warning: Compatibility levels before 10 are deprecated (level 9 in use)
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> dh_auto_configure: warning: Compatibility levels before 10 are deprecated 
> (level 9 in use)
> I: pybuild base:240: python3.10 setup.py config 
> /<>/setup.py:19: DeprecationWarning: The distutils package is 
> deprecated and slated for removal in Python 3.12. Use setuptools or check PEP 
> 632 for potential alternatives
>   from distutils.command.build_ext import build_ext
> /usr/lib/python3/dist-packages/_distutils_hack/__init__.py:18: UserWarning: 
> Distutils was imported before Setuptools, but importing Setuptools also 
> replaces the `distutils` module in `sys.modules`. This may lead to 
> undesirable behaviors or errors. To avoid these issues, avoid using distutils 
> directly, ensure that setuptools is installed in the traditional way (e.g. 
> not an editable install), and/or make sure that setuptools is always imported 
> before distutils.
>   warnings.warn(
> /usr/lib/python3/dist-packages/_distutils_hack/__init__.py:33: UserWarning: 
> Setuptools is replacing distutils.
>   warnings.warn("Setuptools is replacing distutils.")
> /usr/lib/python3/dist-packages/setuptools/_distutils/extension.py:134: 
> UserWarning: Unknown Extension options: 'headers'
>   warnings.warn(msg)
> running config
>dh_auto_build -O--buildsystem=pybuild
> dh_auto_build: warning: Compatibility levels before 10 are deprecated (level 
> 9 in use)
> I: pybuild base:240: /usr/bin/python3 setup.py build 
> /<>/setup.py:19: DeprecationWarning: The distutils package is 
> deprecated and slated for removal in Python 3.12. Use setuptools or check PEP 
> 632 for potential alternatives
>   from distutils.command.build_ext import build_ext
> /usr/lib/python3/dist-packages/_distutils_hack/__init__.py:18: UserWarning: 
> Distutils was imported before Setuptools, but importing Setuptools also 
> replaces the `distutils` module in `sys.modules`. This may lead to 
> undesirable behaviors or errors. To avoid these issues, avoid using distutils 
> directly, ensure that setuptools is installed in the traditional way (e.g. 
> not an editable install), and/or make sure that setuptools is always imported 
> before distutils.
>   warnings.warn(
> /usr/lib/python3/dist-packages/_distutils_hack/__init__.py:33: UserWarning: 
> Setuptools is replacing distutils.
>   warnings.warn("Setuptools is replacing distutils.")
> /usr/lib/python3/dist-packages/setuptools/_distutils/extension.py:134: 
> UserWarning: Unknown Extension options: 'headers'
>   warnings.warn(msg)
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.10_cbor/build/cbor
> copying cbor/__init__.py -> 
> /<>/.pybuild/cpython3_3.10_cbor/build/cbor
> copying cbor/tagmap.py -> 
> /<>/.pybuild/cpython3_3.10_cbor/build/cbor
> copying cbor/VERSION.py -> 
> /<>/.pybuild/cpython3_3.10_cbor/build/cbor
> copying cbor/cbor.py -> 
> /<>/.pybuild/cpython3_3.10_cbor/build/cbor
> copying cbor/cbor_rpc_client.py -> 
> /<>/.pybuild/cpython3_3.10_cbor/build/cbor
> running build_ext
> Traceback (most recent call last):
>   File "/<>/setup.py", line 129, in 
> main()
>   File "/<>/setup.py", line 117, in main
> setup(**setup_options)
>   File "/usr/lib/python3/dist-packages/setuptools/__init__.py", line 87, in 
> setup
> return distutils.core.setup(**attrs)
>   File "/usr/lib/python3/dist-packages/setuptools/_distutils/core.py", line 
> 185, in setup
> return run_commands(dist)
>   File "/usr/lib/python3/dist-packages/setuptools/_distutils/core.py", line 
> 201, in run_commands
> dist.run_commands()
>   File "/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py", line 
> 968, in run_commands
> self.run_command(cmd)
>   File "/usr/lib/python3/dist-packages/setuptools/dist.py", line 1217, in 
> run_command
> super().run_command(command)
>   File "/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py", line 
> 987, in run_command
> cmd_obj.run()
>   File 
> "/usr/lib/python3/dist-packages/setuptools/_distutils/command/build.py", line 
> 132, in run
> self

Bug#1022523: lttnganalyses: FTBFS: AssertionError: "Error: Cannot open trace: 'utf-8' codec [53 chars]byte" != 'Timerange: [1970-01-01 00:00:01.00000000[1221 chars]3%\n'

[Lucas Nussbaum]

Source: lttnganalyses
Version: 0.6.1-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221023 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
>  debian/rules binary
> dh binary --with python3 --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:240: python3.10 setup.py config 
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:240: /usr/bin/python3 setup.py build 
> running build
> running build_py
> creating 
> /<>/.pybuild/cpython3_3.10_lttnganalyses/build/lttnganalyses
> copying lttnganalyses/__init__.py -> 
> /<>/.pybuild/cpython3_3.10_lttnganalyses/build/lttnganalyses
> copying lttnganalyses/_version.py -> 
> /<>/.pybuild/cpython3_3.10_lttnganalyses/build/lttnganalyses
> creating 
> /<>/.pybuild/cpython3_3.10_lttnganalyses/build/lttnganalyses/common
> copying lttnganalyses/common/__init__.py -> 
> /<>/.pybuild/cpython3_3.10_lttnganalyses/build/lttnganalyses/common
> copying lttnganalyses/common/parse_utils.py -> 
> /<>/.pybuild/cpython3_3.10_lttnganalyses/build/lttnganalyses/common
> copying lttnganalyses/common/format_utils.py -> 
> /<>/.pybuild/cpython3_3.10_lttnganalyses/build/lttnganalyses/common
> copying lttnganalyses/common/trace_utils.py -> 
> /<>/.pybuild/cpython3_3.10_lttnganalyses/build/lttnganalyses/common
> copying lttnganalyses/common/version_utils.py -> 
> /<>/.pybuild/cpython3_3.10_lttnganalyses/build/lttnganalyses/common
> copying lttnganalyses/common/time_utils.py -> 
> /<>/.pybuild/cpython3_3.10_lttnganalyses/build/lttnganalyses/common
> creating 
> /<>/.pybuild/cpython3_3.10_lttnganalyses/build/lttnganalyses/core
> copying lttnganalyses/core/__init__.py -> 
> /<>/.pybuild/cpython3_3.10_lttnganalyses/build/lttnganalyses/core
> copying lttnganalyses/core/period.py -> 
> /<>/.pybuild/cpython3_3.10_lttnganalyses/build/lttnganalyses/core
> copying lttnganalyses/core/cputop.py -> 
> /<>/.pybuild/cpython3_3.10_lttnganalyses/build/lttnganalyses/core
> copying lttnganalyses/core/memtop.py -> 
> /<>/.pybuild/cpython3_3.10_lttnganalyses/build/lttnganalyses/core
> copying lttnganalyses/core/irq.py -> 
> /<>/.pybuild/cpython3_3.10_lttnganalyses/build/lttnganalyses/core
> copying lttnganalyses/core/sched.py -> 
> /<>/.pybuild/cpython3_3.10_lttnganalyses/build/lttnganalyses/core
> copying lttnganalyses/core/periods.py -> 
> /<>/.pybuild/cpython3_3.10_lttnganalyses/build/lttnganalyses/core
> copying lttnganalyses/core/io.py -> 
> /<>/.pybuild/cpython3_3.10_lttnganalyses/build/lttnganalyses/core
> copying lttnganalyses/core/event.py -> 
> /<>/.pybuild/cpython3_3.10_lttnganalyses/build/lttnganalyses/core
> copying lttnganalyses/core/stats.py -> 
> /<>/.pybuild/cpython3_3.10_lttnganalyses/build/lttnganalyses/core
> copying lttnganalyses/core/syscalls.py -> 
> /<>/.pybuild/cpython3_3.10_lttnganalyses/build/lttnganalyses/core
> copying lttnganalyses/core/analysis.py -> 
> /<>/.pybuild/cpython3_3.10_lttnganalyses/build/lttnganalyses/core
> creating 
> /<>/.pybuild/cpython3_3.10_lttnganalyses/build/lttnganalyses/cli
> copying lttnganalyses/cli/__init__.py -> 
> /<>/.pybuild/cpython3_3.10_lttnganalyses/build/lttnganalyses/cli
> copying lttnganalyses/cli/cputop.py -> 
> /<>/.pybuild/cpython3_3.10_lttnganalyses/build/lttnganalyses/cli
> copying lttnganalyses/cli/syscallstats.py -> 
> /<>/.pybuild/cpython3_3.10_lttnganalyses/build/lttnganalyses/cli
> copying lttnganalyses/cli/memtop.py -> 
> /<>/.pybuild/cpython3_3.10_lttnganalyses/build/lttnganalyses/cli
> copying lttnganalyses/cli/progressbar.py -> 
> /<>/.pybuild/cpython3_3.10_lttnganalyses/build/lttnganalyses/cli
> copying lttnganalyses/cli/irq.py -> 
> /<>/.pybuild/cpython3_3.10_lttnganalyses/build/lttnganalyses/cli
> copying lttnganalyses/cli/period_parsing.py -> 
> /<>/.pybuild/cpython3_3.10_lttnganalyses/build/lttnganalyses/cli
> copying lttnganalyses/cli/sched.py -> 
> /<>/.pybuild/cpython3_3.10_lttnganalyses/build/lttnganalyses/cli
> copying lttnganalyses/cli/termgraph.py -> 
> /<>/.pybuild/cpython3_3.10_lttnganalyses/build/lttnganalyses/cli
> copying lttnganalyses/cli/periods.py -> 
> /<>/.pybuild/cpython3_3.10_lttnganalyses/build/lttnganalyses/cli
> copying lttnganalyses/cli/io.py -> 
> /<>/.pybuild/cpython3_3

Bug#1022524: postgresql-numeral: FTBFS: Error: debian/control needs updating from debian/control.in. Run 'pg_buildext updatecontrol'.

[Lucas Nussbaum]

Source: postgresql-numeral
Version: 1.3-4
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221023 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> rm -f numeral.so   libnumeral.a  libnumeral.pc
> rm -f numeral--1.sql
> rm -f numeral.o numeralfuncs.o numerallexer.yy.o numeralparser.tab.o 
> zahlfuncs.o zahllexer.yy.o zahlparser.tab.o romanfuncs.o romanlexer.yy.o 
> romanparser.tab.o numeral.bc numeralfuncs.bc numerallexer.yy.bc 
> numeralparser.tab.bc zahlfuncs.bc zahllexer.yy.bc zahlparser.tab.bc 
> romanfuncs.bc romanlexer.yy.bc romanparser.tab.bc
> rm -rf *.yy.* *.tab.*
> rm -rf results/ regression.diffs regression.out tmp_check/ tmp_check_iso/ 
> log/ output_iso/
> make[1]: Leaving directory '/<>'
>dh_clean
>pg_buildext checkcontrol
> --- debian/control2021-10-21 07:55:16.0 +
> +++ debian/control.G6MM9F 2022-10-23 07:35:09.819506919 +
> @@ -13,9 +13,9 @@
>  Vcs-Browser: https://github.com/df7cb/postgresql-numeral
>  Homepage: https://github.com/df7cb/postgresql-numeral
>  
> -Package: postgresql-14-numeral
> +Package: postgresql-15-numeral
>  Architecture: any
> -Depends: ${misc:Depends}, ${shlibs:Depends}, postgresql-14
> +Depends: ${misc:Depends}, ${shlibs:Depends}, postgresql-15
>  Description: numeral datatypes for PostgreSQL
>   This module provides numeric data types for PostgreSQL that use
>   numerals (words instead of digits) for input and output.
> Error: debian/control needs updating from debian/control.in. Run 'pg_buildext 
> updatecontrol'.
> If you are seeing this message in a buildd log, a sourceful upload is 
> required.
> make: *** [debian/rules:7: clean] Error 1


The full build log is available from:
http://qa-logs.debian.net/2022/10/23/postgresql-numeral_1.3-4_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20221023;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20221023=lu...@debian.org=1=1=1=1#results

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

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

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.

Bug#1022522: postgresql-pllua: FTBFS: Error: debian/control needs updating from debian/control.in. Run 'pg_buildext updatecontrol'.

[Lucas Nussbaum]

Source: postgresql-pllua
Version: 1:2.0.10-4
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221023 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[2]: Entering directory '/<>/hstore'
> rm -f hstore_pllua.so   libhstore_pllua.a  libhstore_pllua.pc
> rm -f hstore_pllua.o hstore_pllua.bc
> rm -rf results/ regression.diffs regression.out tmp_check/ tmp_check_iso/ 
> log/ output_iso/
> make[2]: Leaving directory '/<>/hstore'
> make[1]: Leaving directory '/<>'
>dh_clean
>pg_buildext checkcontrol
> --- debian/control2022-01-26 13:03:58.0 +
> +++ debian/control.2aKnSs 2022-10-23 07:35:54.028167597 +
> @@ -15,14 +15,14 @@
>  Vcs-Git: https://salsa.debian.org/postgresql/postgresql-pllua.git
>  Vcs-Browser: https://salsa.debian.org/postgresql/postgresql-pllua
>  
> -Package: postgresql-14-pllua
> +Package: postgresql-15-pllua
>  Architecture: any
>  Depends:
> - postgresql-contrib-14,
> + postgresql-contrib-15,
>   ${misc:Depends},
>   ${postgresql:Depends},
>   ${shlibs:Depends},
> -Description: Lua procedural language for PostgreSQL 14
> +Description: Lua procedural language for PostgreSQL 15
>   PL/Lua is an implementation of Lua as a loadable procedural language for
>   PostgreSQL: with PL/Lua you can use PostgreSQL functions and triggers
>   written in the Lua programming language.
> Error: debian/control needs updating from debian/control.in. Run 'pg_buildext 
> updatecontrol'.
> If you are seeing this message in a buildd log, a sourceful upload is 
> required.
> make: *** [debian/rules:31: clean] Error 1


The full build log is available from:
http://qa-logs.debian.net/2022/10/23/postgresql-pllua_2.0.10-4_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20221023;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20221023=lu...@debian.org=1=1=1=1#results

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

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

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.

Bug#1022521: powa-archivist: FTBFS: Error: debian/control needs updating from debian/control.in. Run 'pg_buildext updatecontrol'.

[Lucas Nussbaum]

Source: powa-archivist
Version: 4.1.4-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221023 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> rm -f powa.so powa.o  \
> powa.bc
> rm -rf results/ regression.diffs regression.out tmp_check/ tmp_check_iso/ 
> log/ output_iso/
> make[1]: Leaving directory '/<>'
>dh_clean
>pg_buildext checkcontrol
> --- debian/control2022-05-16 06:29:51.0 +
> +++ debian/control.WOM2ZY 2022-10-23 07:37:53.130315089 +
> @@ -13,12 +13,12 @@
>  Vcs-Browser: https://github.com/powa-team/powa-archivist
>  Vcs-Git: https://github.com/powa-team/powa-archivist.git
>  
> -Package: postgresql-14-powa
> +Package: postgresql-15-powa
>  Architecture: any
> -Depends: ${misc:Depends}, ${shlibs:Depends}, postgresql-14, 
> postgresql-contrib-14
> +Depends: ${misc:Depends}, ${shlibs:Depends}, postgresql-15, 
> postgresql-contrib-15
>  Provides: postgresql-powa
>  Suggests: powa-web, powa-collector
> -Description: PostgreSQL Workload Analyzer -- PostgreSQL 14 extension
> +Description: PostgreSQL Workload Analyzer -- PostgreSQL 15 extension
>   PoWA is a PostgreSQL Workload Analyzer that gathers performance stats and
>   provides real-time charts and graphs to help monitor and tune your 
> PostgreSQL
>   servers. This package contains the core extension of the PoWA project, the
> Error: debian/control needs updating from debian/control.in. Run 'pg_buildext 
> updatecontrol'.
> If you are seeing this message in a buildd log, a sourceful upload is 
> required.
> make: *** [debian/rules:11: clean] Error 1


The full build log is available from:
http://qa-logs.debian.net/2022/10/23/powa-archivist_4.1.4-1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20221023;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20221023=lu...@debian.org=1=1=1=1#results

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

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

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.

Bug#1022520: repmgr: FTBFS: Error: debian/control needs updating from debian/control.in. Run 'pg_buildext updatecontrol'.

[Lucas Nussbaum]

Source: repmgr
Version: 5.3.2-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221023 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
>  debian/rules clean
> pg_buildext checkcontrol
> --- debian/control2022-08-16 12:04:54.0 +
> +++ debian/control.sRXE11 2022-10-23 07:29:50.998361711 +
> @@ -48,14 +48,14 @@
>   .
>   This is a metapackage that depends on the version specific packages.
>  
> -Package: postgresql-14-repmgr
> +Package: postgresql-15-repmgr
>  Architecture: any
> -Depends: postgresql-14, repmgr-common (>= ${source:Version}), 
> ${misc:Depends}, ${shlibs:Depends}
> +Depends: postgresql-15, repmgr-common (>= ${source:Version}), 
> ${misc:Depends}, ${shlibs:Depends}
>  Suggests: rsync
> -Description: replication manager for PostgreSQL 14
> +Description: replication manager for PostgreSQL 15
>   repmgr is an open-source tool suite for managing replication and failover 
> in a
>   cluster of PostgreSQL servers. It enhances PostgreSQL's built-in hot-standby
>   capabilities with tools to set up standby servers, monitor replication, and
>   perform administrative tasks such as failover or manual switchover 
> operations.
>   .
> - This package contains repmgr for PostgreSQL 14.
> + This package contains repmgr for PostgreSQL 15.
> Error: debian/control needs updating from debian/control.in. Run 'pg_buildext 
> updatecontrol'.
> If you are seeing this message in a buildd log, a sourceful upload is 
> required.
> make: *** [/usr/share/postgresql-common/pgxs_debian_control.mk:9: 
> debian/control] Error 1


The full build log is available from:
http://qa-logs.debian.net/2022/10/23/repmgr_5.3.2-1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20221023;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20221023=lu...@debian.org=1=1=1=1#results

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

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

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.

Bug#1022519: readucks: FTBFS: distutils.errors.DistutilsClassError: command class must subclass Command

[Lucas Nussbaum]

Source: readucks
Version: 0.0.3-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221023 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
>  debian/rules clean
> dh clean --with python3 --buildsystem=pybuild
>dh_auto_clean -O--buildsystem=pybuild
> I: pybuild base:240: python3.10 setup.py clean 
> /<>/setup.py:14: DeprecationWarning: The distutils package is 
> deprecated and slated for removal in Python 3.12. Use setuptools or check PEP 
> 632 for potential alternatives
>   from distutils.command.build import build
> /usr/lib/python3/dist-packages/_distutils_hack/__init__.py:18: UserWarning: 
> Distutils was imported before Setuptools, but importing Setuptools also 
> replaces the `distutils` module in `sys.modules`. This may lead to 
> undesirable behaviors or errors. To avoid these issues, avoid using distutils 
> directly, ensure that setuptools is installed in the traditional way (e.g. 
> not an editable install), and/or make sure that setuptools is always imported 
> before distutils.
>   warnings.warn(
> /usr/lib/python3/dist-packages/_distutils_hack/__init__.py:33: UserWarning: 
> Setuptools is replacing distutils.
>   warnings.warn("Setuptools is replacing distutils.")
> Traceback (most recent call last):
>   File "/<>/setup.py", line 97, in 
> setup(name='readucks',
>   File "/usr/lib/python3/dist-packages/setuptools/__init__.py", line 87, in 
> setup
> return distutils.core.setup(**attrs)
>   File "/usr/lib/python3/dist-packages/setuptools/_distutils/core.py", line 
> 172, in setup
> ok = dist.parse_command_line()
>   File "/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py", line 
> 474, in parse_command_line
> args = self._parse_command_opts(parser, args)
>   File "/usr/lib/python3/dist-packages/setuptools/dist.py", line 1107, in 
> _parse_command_opts
> nargs = _Distribution._parse_command_opts(self, parser, args)
>   File "/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py", line 
> 540, in _parse_command_opts
> raise DistutilsClassError(
> distutils.errors.DistutilsClassError: command class  
> must subclass Command
> E: pybuild pybuild:379: clean: plugin distutils failed with: exit code=1: 
> python3.10 setup.py clean 
> dh_auto_clean: error: pybuild --clean -i python{version} -p 3.10 returned 
> exit code 13
> make: *** [debian/rules:6: clean] Error 25


The full build log is available from:
http://qa-logs.debian.net/2022/10/23/readucks_0.0.3-3_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20221023;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20221023=lu...@debian.org=1=1=1=1#results

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

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

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.

Bug#1022518: pg-fact-loader: FTBFS: Error: debian/control needs updating from debian/control.in. Run 'pg_buildext updatecontrol'.

[Lucas Nussbaum]

Source: pg-fact-loader
Version: 1.7.0-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221023 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
>  fakeroot debian/rules clean
> pg_buildext checkcontrol
> --- debian/control2022-08-23 20:21:07.0 +
> +++ debian/control.rr0bsP 2022-10-23 07:36:28.794770299 +
> @@ -7,8 +7,8 @@
>  Homepage: https://github.com/enova/pg_fact_loader
>  Vcs-Git: https://github.com/enova/pg_fact_loader.git
>  
> -Package: postgresql-14-pg-fact-loader
> +Package: postgresql-15-pg-fact-loader
>  Architecture: any
> -Depends: postgresql-14, ${shlibs:Depends}, ${misc:Depends}
> +Depends: postgresql-15, ${shlibs:Depends}, ${misc:Depends}
>  Description: Build fact tables asynchronously with Postgres
> - Use queue tables to build fact tables asynchronously for PostgreSQL 14.
> + Use queue tables to build fact tables asynchronously for PostgreSQL 15.
> Error: debian/control needs updating from debian/control.in. Run 'pg_buildext 
> updatecontrol'.
> If you are seeing this message in a buildd log, a sourceful upload is 
> required.
> make: *** [/usr/share/postgresql-common/pgxs_debian_control.mk:9: 
> debian/control] Error 1


The full build log is available from:
http://qa-logs.debian.net/2022/10/23/pg-fact-loader_1.7.0-1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20221023;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20221023=lu...@debian.org=1=1=1=1#results

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

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

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.