Bug#993071: kmail: symbol lookup error: /lib/x86_64-linux-gnu/libKF5Libkleo.so.5: undefined symbol: _ZN5GpgME6UserID9SignatureltERKS1_

[Norbert Preining]

On Sat, 28 Aug 2021, Johannes Rohr wrote:
> >> libgpgmepp.so.6 => /usr/local/lib/libgpgmepp.so.6 (0x7efde318f000)
> > That is a version you compiled yourself, and you cannot expect that this
> > is supported.
> 
> Yikes. Must have done that ages ago and forgotten about it.

Does it now work?

Best

Norbert

--
PREINING Norbert  https://www.preining.info
Fujitsu Research  +  IFMGA Guide  +  TU Wien  +  TeX Live  + Debian Dev
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Bug#992277: protontricks: With any command, fails with "KeyError: 'LibraryFolders'"

[Stephan Lachnit]

Hi,


thanks for reporting. I can confirm this. I will fix it with the version 
1.6.0, which has been released 3 weeks ago.


Since I don't have much time right now, it will probably stay in this 
state for the next couple of weeks (sorry).



Regards

Stephan


On Mon, 16 Aug 2021 09:48:41 -0700 Brian Vaughan  
wrote:


> Package: protontricks
> Version: 1.5.0-1
> Severity: grave
> Justification: renders package unusable
> X-Debbugs-Cc: bgvaug...@gmail.com
>
> Dear Maintainer,
>
> Simply executing 'protontricks' shows the usage instructions. 
Executing it with

> commands results in a Python error message.
>
> $ protontricks -s "No Man's Sky"
> Traceback (most recent call last):
> File "/usr/bin/protontricks", line 33, in 
> sys.exit(load_entry_point('protontricks==1.5.0', 'console_scripts',
> 'protontricks')())
> File "/usr/lib/python3/dist-packages/protontricks/cli.py", line 167, 
in main

> steam_lib_paths = get_steam_lib_paths(steam_path)
> File "/usr/lib/python3/dist-packages/protontricks/steam.py", line 613, in
> get_steam_lib_paths
> library_folders = parse_library_folders(folders_vdf_path.read_text())
> File "/usr/lib/python3/dist-packages/protontricks/steam.py", line 597, in
> parse_library_folders
> Path(value) for key, value in vdf_data["LibraryFolders"].items()
> KeyError: 'LibraryFolders'
>
> $ protontricks --gui
> Traceback (most recent call last):
> File "/usr/bin/protontricks", line 33, in 
> sys.exit(load_entry_point('protontricks==1.5.0', 'console_scripts',
> 'protontricks')())
> File "/usr/lib/python3/dist-packages/protontricks/cli.py", line 167, 
in main

> steam_lib_paths = get_steam_lib_paths(steam_path)
> File "/usr/lib/python3/dist-packages/protontricks/steam.py", line 613, in
> get_steam_lib_paths
> library_folders = parse_library_folders(folders_vdf_path.read_text())
> File "/usr/lib/python3/dist-packages/protontricks/steam.py", line 597, in
> parse_library_folders
> Path(value) for key, value in vdf_data["LibraryFolders"].items()
> KeyError: 'LibraryFolders'
>
> I had previously installed protontricks as a normal user, using pipx, 
following

> the instructions at https://github.com/Matoking/protontricks and used it
> successfully. I uninstalled it, using pipx, prior to installing the 
Debian

> package.
>
>
> -- System Information:
> Debian Release: 11.0
> APT prefers unstable
> APT policy: (500, 'unstable'), (1, 'experimental')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
>
> Kernel: Linux 5.10.0-8-amd64 (SMP w/12 CPU threads)
> Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
> TAINT_UNSIGNED_MODULE
> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE not

> set
> Shell: /bin/sh linked to /usr/bin/dash

Bug#978842: marked as done (jellyfish1: ftbfs with autoconf 2.70)

[Debian Bug Tracking System]

Your message dated Sat, 28 Aug 2021 22:18:23 +
with message-id 
and subject line Bug#978842: fixed in jellyfish1 1.1.11-6
has caused the Debian Bug report #978842,
regarding jellyfish1: ftbfs with autoconf 2.70
to be marked as done.

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

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


-- 
978842: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978842
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:jellyfish1
Version: 1.1.11-4
Severity: normal
Tags: sid bookworm
User: d...@debian.org
Usertags: ftbfs-ac270

[This bug report is not targeted to the upcoming bullseye release]

The package fails to build in a test rebuild on at least amd64 with
autoconf 2.70, but succeeds to build with autoconf 2.69. The
severity of this report will be raised before the bookworm release,
so nothing has to be done for the bullseye release.

The full build log can be found at:
http://qa-logs.debian.net/2020/09/26.ac270/jellyfish1_1.1.11-4_unstable_ac270.log
The last lines of the build log are at the end of this report.

To build with autoconf 2.70, please install the autoconf package from
experimental:  apt-get -t=experimental install autoconf 

[...]
dpkg-source: info: unpacking jellyfish1_1.1.11-4.debian.tar.xz
dpkg-source: info: using patch list from debian/patches/series
dpkg-source: info: applying man
dpkg-source: info: applying arm64.patch
dpkg-source: info: applying mips.patch

Check disk space


Sufficient free space for build

User Environment


APT_CONFIG=/var/lib/sbuild/apt.conf
HOME=/sbuild-nonexistent
LANG=C.UTF-8
LC_ALL=C.UTF-8
LOGNAME=user42
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
SCHROOT_ALIAS_NAME=unstable
SCHROOT_CHROOT_NAME=sid-amd64-sbuild
SCHROOT_COMMAND=env
SCHROOT_GID=1001
SCHROOT_GROUP=user42
SCHROOT_SESSION_ID=sid-amd64-sbuild-ab27b603-bfd9-4e72-811c-d2ab857b3693
SCHROOT_UID=1001
SCHROOT_USER=user42
SHELL=/bin/sh
USER=user42

dpkg-buildpackage
-

Command: dpkg-buildpackage -us -uc -sa -rfakeroot
dpkg-buildpackage: info: source package jellyfish1
dpkg-buildpackage: info: source version 1.1.11-4
dpkg-buildpackage: info: source distribution unstable
dpkg-buildpackage: info: source changed by Andreas Tille 
 dpkg-source --before-build .
dpkg-buildpackage: info: host architecture amd64
 fakeroot debian/rules clean
dh clean
   debian/rules override_dh_clean
make[1]: Entering directory '/<>'
dh_clean
if [ -d debian/tmp_save_tests ] ; then \
mv debian/tmp_save_tests/* tests ; \
rmdir debian/tmp_save_tests ; \
fi
make[1]: Leaving directory '/<>'
 dpkg-source -b .
dpkg-source: info: using source format '3.0 (quilt)'
dpkg-source: info: building jellyfish1 using existing 
./jellyfish1_1.1.11.orig.tar.gz
dpkg-source: info: using patch list from debian/patches/series
dpkg-source: info: building jellyfish1 in jellyfish1_1.1.11-4.debian.tar.xz
dpkg-source: info: building jellyfish1 in jellyfish1_1.1.11-4.dsc
 debian/rules build
dh build
   dh_update_autotools_config
   dh_autoreconf
configure.ac:8: error: AC_CONFIG_MACRO_DIR can only be used once
./lib/autoconf/general.m4:1849: AC_CONFIG_MACRO_DIR is expanded from...
configure.ac:8: the top level
autom4te: error: /usr/bin/m4 failed with exit status: 1
aclocal: error: echo failed with exit status: 1
autoreconf: error: aclocal failed with exit status: 1
dh_autoreconf: error: autoreconf -f -i returned exit code 1
make: *** [debian/rules:10: build] Error 25
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2
--- End Message ---
--- Begin Message ---
Source: jellyfish1
Source-Version: 1.1.11-6
Done: Nilesh Patra 

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

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

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

Debian distribution maintenance software
pp.
Nilesh Patra  (supplier of updated jellyfish1 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 29 Aug 2021 03:40:58 +0530
Source: jellyfish1
Architecture: source
Version: 1.1.11-6
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Bug#981823: librust-alacritty-terminal-dev is not installable

[James McCoy]

On Sat, Aug 28, 2021, 15:39 Steve Langasek 
wrote:

> Note that although rust-alacritty-terminal may no longer need
> rust-terminfo,
> if it still depends on rust-vte, then the package is still not buildable
> because the only version of rust-vte in the archive is 0.3 and
> rust-alacritty-terminal requires 0.8.
>

Yeah, I'm working my way through the dependency stack.  Rust-vte and
rust-alacritty-terminal are going to be updated.

>

Bug#992917: grok: FTBFS due to RPC removal from glibc

[Stig Sandbeck Mathisen]

On Wed, Aug 25, 2021 at 12:46:40AM +0200, Aurelien Jarno wrote:
> Source: grok
> Version: 1.20110708.1-4.5
> Severity: serious
> Tags: patch ftbfs
> Justification: fails to build from source (but built successfully in the past)
> 
> 
> The glibc SunRPC implementation has been marked obsolete for some time.
> It has been removed upstream from glibc 2.32, and it got disabled in the
> recent glibc uploads. The TI RPC implementation should be used instead,
> which also brings new features (IPv6, Kerberos support, ...).
> 
> For this reason grok now fails to build from source. You will find
> attached a patch to switch to the TI RPC implementation, fixing the
> FTBFS.
> 
> Regards,
> Aurelien

Hello,

Thank you for the bug report and patch.  I did a slight adjustment, adding the
parameters in debian/rules, and targeting the "gnu" libc, see
https://salsa.debian.org/debian/grok/-/commit/fe4c4b549ae2595007271df7502feb54115f4dda

-- 
Stig Sandbeck Mathisen

Bug#978843: marked as done (jellyfish: ftbfs with autoconf 2.70)

[Debian Bug Tracking System]

Your message dated Sat, 28 Aug 2021 19:49:41 +
with message-id 
and subject line Bug#978843: fixed in jellyfish 2.3.0-11
has caused the Debian Bug report #978843,
regarding jellyfish: ftbfs with autoconf 2.70
to be marked as done.

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

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


-- 
978843: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978843
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:jellyfish
Version: 2.3.0-6
Severity: normal
Tags: sid bookworm
User: d...@debian.org
Usertags: ftbfs-ac270

[This bug report is not targeted to the upcoming bullseye release]

The package fails to build in a test rebuild on at least amd64 with
autoconf 2.70, but succeeds to build with autoconf 2.69. The
severity of this report will be raised before the bookworm release,
so nothing has to be done for the bullseye release.

The full build log can be found at:
http://qa-logs.debian.net/2020/09/26.ac270/jellyfish_2.3.0-6_unstable_ac270.log
The last lines of the build log are at the end of this report.

To build with autoconf 2.70, please install the autoconf package from
experimental:  apt-get -t=experimental install autoconf 

[...]
am__untar='$${TAR-tar} xf -'
bindir='${exec_prefix}/bin'
build='x86_64-pc-linux-gnu'
build_alias='x86_64-linux-gnu'
build_cpu='x86_64'
build_os='linux-gnu'
build_vendor='pc'
datadir='${datarootdir}'
datarootdir='${prefix}/share'
docdir='${datarootdir}/doc/${PACKAGE_TARNAME}'
dvidir='${docdir}'
exec_prefix='NONE'
host='x86_64-pc-linux-gnu'
host_alias=''
host_cpu='x86_64'
host_os='linux-gnu'
host_vendor='pc'
htmldir='${docdir}'
includedir='${prefix}/include'
infodir='${prefix}/share/info'
install_sh='${SHELL} /<>/install-sh'
libdir='${prefix}/lib/x86_64-linux-gnu'
libexecdir='${exec_prefix}/libexec'
localedir='${datarootdir}/locale'
localstatedir='/var'
mandir='${prefix}/share/man'
mkdir_p='$(MKDIR_P)'
oldincludedir='/usr/include'
pdfdir='${docdir}'
prefix='/usr'
program_transform_name='s,x,x,'
psdir='${docdir}'
runstatedir='/run'
sbindir='${exec_prefix}/sbin'
sharedstatedir='${prefix}/com'
sysconfdir='/etc'
target_alias=''

## --- ##
## confdefs.h. ##
## --- ##

/* confdefs.h */
#define PACKAGE_NAME "jellyfish"
#define PACKAGE_TARNAME "jellyfish"
#define PACKAGE_VERSION "2.3.0"
#define PACKAGE_STRING "jellyfish 2.3.0"
#define PACKAGE_BUGREPORT "gmarc...@umd.edu"
#define PACKAGE_URL ""
#define PACKAGE "jellyfish"
#define VERSION "2.3.0"
#define HAVE_SYS_TYPES_H 1
#define HAVE_SYS_STAT_H 1
#define HAVE_STRINGS_H 1
#define HAVE_INTTYPES_H 1
#define HAVE_STDINT_H 1
#define HAVE_UNISTD_H 1
#define HAVE_STDLIB_H 1
#define HAVE_STRING_H 1
#define STDC_HEADERS 1
#define HAVE_DLFCN_H 1
#define LT_OBJDIR ".libs/"
#define HAVE_HTSLIB 1

configure: exit 2
dh_auto_configure: error: ./configure --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 --enable-swig 
--enable-perl-binding --enable-htslib --enable-python-binding 
PYTHON=/usr/bin/python3 returned exit code 2
make[1]: *** [debian/rules:50: override_dh_auto_configure] Error 25
make[1]: Leaving directory '/<>'
make: *** [debian/rules:21: binary] Error 2
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2
--- End Message ---
--- Begin Message ---
Source: jellyfish
Source-Version: 2.3.0-11
Done: Étienne Mollier 

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

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

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

Debian distribution maintenance software
pp.
Étienne Mollier  (supplier of updated jellyfish package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 28 Aug 2021 21:01:20 +0200
Source: jellyfish
Architecture: source
Version: 2.3.0-11
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Étienne Mollier 
Closes: 978843 983273
Changes:
 

Processed: tagging 992917

[Debian Bug Tracking System]

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

> tags 992917 + confirmed pending
Bug #992917 [src:grok] grok: FTBFS due to RPC removal from glibc
Added tag(s) confirmed and pending.
> thanks
Stopping processing here.

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

Bug#981823: librust-alacritty-terminal-dev is not installable

[Steve Langasek]

Note that although rust-alacritty-terminal may no longer need rust-terminfo,
if it still depends on rust-vte, then the package is still not buildable
because the only version of rust-vte in the archive is 0.3 and
rust-alacritty-terminal requires 0.8.


-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org


signature.asc
Description: PGP signature

Processed: Bug#978843 marked as pending in jellyfish

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #978843 [src:jellyfish] jellyfish: ftbfs with autoconf 2.70
Added tag(s) pending.

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

Bug#978843: marked as pending in jellyfish

[Étienne Mollier]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/med-team/jellyfish/-/commit/02ca089066f65cb5252bc29ce98e06a1ee721766


add fix-autoreconf.patch; address ftbfs

This patch provides protection to a couple of macros in configure.ac
to avoid breakage of the script configure which is produced by the
autoconf 2.70.

Closes: #978843


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/978843

Bug#993106: marked as done (lcalc FTBFS: Makefile.am:9: error: 'pkgconfig_DATA' is used but 'pkgconfigdir' is undefined)

[Debian Bug Tracking System]

Your message dated Sat, 28 Aug 2021 17:33:36 +
with message-id 
and subject line Bug#993106: fixed in lcalc 2.0.3-2
has caused the Debian Bug report #993106,
regarding lcalc FTBFS: Makefile.am:9: error: 'pkgconfig_DATA' is used but 
'pkgconfigdir' is undefined
to be marked as done.

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

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


-- 
993106: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993106
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: lcalc
Version: 2.0.3-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/package.php?p=lcalc=sid

...
   dh_autoreconf -a
libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, 'build-aux'.
libtoolize: copying file 'build-aux/ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'm4'.
libtoolize: copying file 'm4/libtool.m4'
libtoolize: copying file 'm4/ltoptions.m4'
libtoolize: copying file 'm4/ltsugar.m4'
libtoolize: copying file 'm4/ltversion.m4'
libtoolize: copying file 'm4/lt~obsolete.m4'
configure.ac:34: installing 'build-aux/ar-lib'
configure.ac:34: installing 'build-aux/compile'
configure.ac:191: installing 'build-aux/config.guess'
configure.ac:191: installing 'build-aux/config.sub'
configure.ac:19: installing 'build-aux/install-sh'
configure.ac:19: installing 'build-aux/missing'
Makefile.am:9: error: 'pkgconfig_DATA' is used but 'pkgconfigdir' is undefined
src/lcalc/Makefile.am: installing 'build-aux/depcomp'
parallel-tests: installing 'build-aux/test-driver'
autoreconf: error: automake failed with exit status: 1
dh_autoreconf: error: autoreconf -f -i returned exit code 1
make: *** [debian/rules:8: binary-arch] Error 25


This is likely related to autoconf 2.71.
--- End Message ---
--- Begin Message ---
Source: lcalc
Source-Version: 2.0.3-2
Done: Julien Puydt 

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

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

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

Debian distribution maintenance software
pp.
Julien Puydt  (supplier of updated lcalc package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 28 Aug 2021 19:16:30 +0200
Source: lcalc
Architecture: source
Version: 2.0.3-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Team 

Changed-By: Julien Puydt 
Closes: 993106
Changes:
 lcalc (2.0.3-2) unstable; urgency=medium
 .
   * Add b-dep on pkg-config (Closes: #993106).
Checksums-Sha1:
 734ec1eebd90443ebfa6e526aa00ac83e2141326 2145 lcalc_2.0.3-2.dsc
 148a5f80b0df731df50544cb5d8230ba2df17103 4652 lcalc_2.0.3-2.debian.tar.xz
 90f067787d6c8d9050e66645b6ec3871a7e82974 5795 lcalc_2.0.3-2_source.buildinfo
Checksums-Sha256:
 04294644fa45a14a869acf1a055ca7b845647b3e125d0797864de0e7d2612af9 2145 
lcalc_2.0.3-2.dsc
 1eae4fcebf525d2376eda0a3951fe5aa74064c8b881eb1cb961c1c2d5eeb4dd7 4652 
lcalc_2.0.3-2.debian.tar.xz
 1696d3f7f959e2a34dc4f4a77a842c6bf672a6eea5253ced55438e90c8502e17 5795 
lcalc_2.0.3-2_source.buildinfo
Files:
 cd4a84c8086b1867d4f8a0307f397db8 2145 math optional lcalc_2.0.3-2.dsc
 e8b9b22c71dba903c39a22ad9362093c 4652 math optional lcalc_2.0.3-2.debian.tar.xz
 d4c662efdf45e1390eba35db9b7fc9be 5795 math optional 
lcalc_2.0.3-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJGBAEBCgAwFiEEgS7v2KP7pKzk3xFLBMU71/4DBVEFAmEqb50SHGpwdXlkdEBk
ZWJpYW4ub3JnAAoJEATFO9f+AwVRaIsP/Ag5JpPTDddWhZfKpigoBm6cbPN+UVDF
GE+IqWnb057B/6i36JxI90Hkt4K/fH6t/xwAZfoLig/BeZTJ6hR63qUUxFmIF5w8
nZrRoUojfVw1v8/zrQXFSnVIdZ93V7rL5ROm6HQqZsGKX+knSuq/jpDbFYz5KNYM
AgEi4g855HOfBwIrFom1f49F03rdkTivFGXQfTGhY+zAxX85tsza+SpIJd1Ut5Lq
i4cvER/TUGQXV97ytAyrG+5WZXfSCvzUyyoZIESQsCRjRIXEgq159QfxqVsGmbsA
hf25o5FOL/FVNmQX/QkvnqUti2wKjgp3u5oXd7E+alRWdG8IMjugAXmcwFZZUE+N
0qbRMIEdgw/tTbqZdddIZ/NZfD0VOMU3a0iax2EzSfj8Q4Wfy1v/fZG2JNZaRmC1
RHbpvcplAhqg2vL5O2xtVi6E3bDI5B0807CW3zmvY7g7w46xkpfh18s25nydMF1U
Qyawwmd6suToH4BTUOgoMz5gqsK99LHvDoQtpp8bCozxXj3AslZYgrIb4EwlvMtt
ijIBIZsl53wzGmQAytG5aSHQHhLb5ecoCf9y/6R1uBgCU3/DKsd8tgc9KMbmF1Dt
rKe51PMVpP3bULPBspD/hJsnIJVNkxtEvg4JJVLRNTHCJeZKcTHt+0iyJy6U0UMp
w9ZIJ84MLUb5
=9g6Z
-END PGP SIGNATURE End Message ---

Bug#992927: mutt: Mutt 2.1.2 is available, fixing a potential data-loss IMAP bug

[Antonio Radici]

On Wed, Aug 25, 2021 at 10:20:17AM +0200, Vincent Lefevre wrote:
> Package: mutt
> Version: 2.0.5-4.1
> Severity: grave
> Justification: causes non-serious data loss
> 
> Mutt 2.1.2 is available. From the announce: "This is an important
> bug-fix release, fixing a potential data-loss IMAP bug. IMAP users
> are strongly advised to upgrade."
> 
> For stable and oldstable: "Packagers, please consider backporting
> commit 647efbd1 if at all possible."
> 
> See
> http://lists.mutt.org/pipermail/mutt-announce/Week-of-Mon-20210823/40.html
> for additional information.
> 
> Note also that there is a minor "mutt -v" output issue with the
> current Mutt and, in particular, GNU Autoconf 2.71, which is now
> in unstable. I fixed this issue in Mutt's repository yesterday
> and I'm going to report a second bug for that.

I'm going to have this fixed in the next few days (by Sep 1st)

Bug#992087: libfonts-java: contains a file with a non-free "disparaging to Sun" license

[tony mancill]

On Sat, Aug 28, 2021 at 02:21:02PM +0200, Pierre Gruet wrote:
> Control: tags -1 pending
> 
> Hello,
> 
> After a deeper examination, I see the file with the non-free contents is
> useless anyway, none of the files it attempts to patch exists. I think this
> file got lost here as it obviously comes from itext, not libfonts.
> 
> I offer to team-upload the package soon.

Hi Pierre,

Thank you for helping us clean up some of the cruft that has
accumulated in these packages.

Cheers,
tony

Bug#993214: mpi4py: autopkgtest regression around 2021-08-25

[Graham Inggs]

Source: mpi4py
Version: 3.0.3-8
Severity: serious
User: debian...@lists.debian.org
Usertags: regression
X-Debbugs-CC: debian...@lists.debian.org

Hi Maintainer

Some time around 2021-08-25, mpi4py's autopkgtests regressed in testing [1].
This seems to coincide with the migration of pmix/4.1.0-3 to testing,
but may be unrelated.

Regards
Graham


[1] https://ci.debian.net/packages/m/mpi4py/testing/amd64/

Bug#993166: marked as done (rust-crossbeam-deque_0.7.4-1_mips64el-buildd.changes REJECTED)

[Debian Bug Tracking System]

Your message dated Sat, 28 Aug 2021 16:19:47 +
with message-id 
and subject line Bug#993166: fixed in rust-crossbeam-deque 0.7.4-2
has caused the Debian Bug report #993166,
regarding rust-crossbeam-deque_0.7.4-1_mips64el-buildd.changes REJECTED
to be marked as done.

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

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


-- 
993166: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993166
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rust-crossbeam-deque
Version: 0.7.4-1
Severity: serious

On 2021-08-28 09:03, Debian FTP Masters wrote:
> librust-crossbeam-deque-dev_0.7.4-1_mips64el.deb: has 1 file(s) with a 
> timestamp too far in the past:
>   usr/share/doc/librust-crossbeam-deque-dev/changelog.gz (Thu Nov 29 21:33:09 
> 1973)
> 
> 
> 
> ===
> 
> Please feel free to respond to this email if you don't understand why
> your files were rejected, or if you upload new files which address our
> concerns.
> 
> 
> 
--- End Message ---
--- Begin Message ---
Source: rust-crossbeam-deque
Source-Version: 0.7.4-2
Done: Peter Michael Green 

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

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

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

Debian distribution maintenance software
pp.
Peter Michael Green  (supplier of updated 
rust-crossbeam-deque package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 28 Aug 2021 16:06:15 +
Source: rust-crossbeam-deque
Architecture: source
Version: 0.7.4-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Rust Maintainers 

Changed-By: Peter Michael Green 
Closes: 993166
Changes:
 rust-crossbeam-deque (0.7.4-2) unstable; urgency=medium
 .
   * Team upload.
   * Package crossbeam-deque 0.7.4 from crates.io using debcargo 2.4.4
   * Workaround timestamp issue on changelog in /usr/share/doc (Closes: 993166)
Checksums-Sha1:
 cf60e0ee130887c0114f80506230a4a575622c35 2512 rust-crossbeam-deque_0.7.4-2.dsc
 3f7c72a75220218984afd775a61adce0509fa1bb 3116 
rust-crossbeam-deque_0.7.4-2.debian.tar.xz
 93685ee32346f62fb046e19d78bb9eab9148b276 7609 
rust-crossbeam-deque_0.7.4-2_source.buildinfo
Checksums-Sha256:
 54472bd3d5951f16a3864d1f292d8bc6a0d386e9557a089ff72afdc8346aab81 2512 
rust-crossbeam-deque_0.7.4-2.dsc
 d786bcbf3b05a595a5567a6b55b457f283095d2bc6701a96e043e491162e21af 3116 
rust-crossbeam-deque_0.7.4-2.debian.tar.xz
 70634514fbaa0f8e0da76cf7be4155470348af782dee340f252c7d3b028d12e0 7609 
rust-crossbeam-deque_0.7.4-2_source.buildinfo
Files:
 b8a32cccda701958f5bc957db222c653 2512 rust optional 
rust-crossbeam-deque_0.7.4-2.dsc
 40cb15fd9d7908d0587faff764f9541c 3116 rust optional 
rust-crossbeam-deque_0.7.4-2.debian.tar.xz
 fb0a5453f306f9b7fa5e45d101e3425c 7609 rust optional 
rust-crossbeam-deque_0.7.4-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJIBAEBCAAyFiEEU0DQATYMplbjSX63DEjqKnqP/XsFAmEqX2cUHHBsdWd3YXNo
QGRlYmlhbi5vcmcACgkQDEjqKnqP/XsqGQ//VpVRcmXIpFFPXaQJIfrrCKNRwuoa
3QD2NhayYjxx6UF55krTqCmDG0lpFhxtosCFi9fk9LawoyWpgUD9y8Ap9f9q5icW
h8cS0fuWCZJPgfpYvmr6C3yRJPZkX93krIbkNA4PcTJo7VzRQjz2AHYTRxwpy5xt
+Jve/0rPRa1tlAw6ALxkrUwwBdyQj3qcvYaufdvb5MwTK5aj9tHYlGOsB6jgth/I
fo2SwHum64ucrD0u3sFuaNYcRAQ5bf4GlBf9cVN4lWufVlBpNzMXg5CWUESUAJ+P
E0NUwmuO22oxpBOwhfLTC2uHzK4gNEAPpDsfDmbUOi8KOeLSEH0W5RfipaDITVl9
2OMGn3umRR0NzTx1ic0k+czn+G92DSTDb9dHA4LP/C/F2HKvNgE7jZWziMpET40+
Idql0PIU3Cld+fJtA7viFUjx7HRTYvppJ6Hdj2EIXwdcJ1qtjMzUQk2IriwUF3sF
Y5uI18sMJfcKFMyT0//w1H7+XVhHXm04bqkdK2rJCek82tswpc4kwZfv7CsB2OrJ
LPBAypcQelZ0EQ2cc+Ji6ZurT2GiVv0G4STylOTSQrdr2AewNilhMTi97B7pnldY
g2FBXWZ9F40I66OgJd3nNysed7sMDCzVHI4/Eos3ZaGPf6xrpo9SSDaM862+XCnb
9nKTOYwZPeLLxdw=
=l7sn
-END PGP SIGNATURE End Message ---

Processed: Re: Bug#993204: gnome-shell-timer: does not declare compatibility with GNOME Shell 40

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #993204 [gnome-shell-timer] gnome-shell-timer: does not declare 
compatibility with GNOME Shell 40
Severity set to 'serious' from 'important'

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

Bug#993209: mat2: autopkgtests fail with libimage-exiftool-perl >= 12.23

[gregor herrmann]

Package: mat2
Version: 0.12.1-3
Severity: serious
Tags: upstream sid bookworm fixed-upstream patch

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

mat2's autopkgtests fail with newer libimage-exiftool-perl:

https://ci.debian.net/data/autopkgtest/testing/amd64/m/mat2/14885837/log.gz

>   self.assertEqual(v, case['expected_meta'][k])
E   AssertionError: 'MP4 Base Media v1 [IS0 14496-12:2003]' != 'MP4 
 Base Media v1 [IS0 14496-12:2003]'
E   - MP4 Base Media v1 [IS0 14496-12:2003]
E   + MP4  Base Media v1 [IS0 14496-12:2003]
E   ?+


This is caused by a typo fix in lib/Image/ExifTool/QuickTime.pm in
12.23:

- -'isom' => 'MP4  Base Media v1 [IS0 14496-12:2003]', # video/mp4
+'isom' => 'MP4 Base Media v1 [IS0 14496-12:2003]', # video/mp4 (or audio)


In mat2 there's this test for the "old" version of the string:

% grep -ri "mp4  base media"   
tests/test_libmat2.py:'MajorBrand': 'MP4  Base Media v1 [IS0 
14496-12:2003]',


Apparently this is already fixed in upstream git:
https://0xacab.org/jvoisin/mat2/-/commit/6df615281b2a649b85ff7670f6d87d3beed0b977


I'm attaching a slightly rebased quilt patch based on this commit.

(After this we still see a test failure during build and in
autopkgtests, but this is #992912 / 
https://0xacab.org/jvoisin/mat2/-/commit/c9be50f968212b01f8d8ad85e59e19c3e67d8578
)


Cheers,
gregor

-BEGIN PGP SIGNATURE-

iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAmEqWXJfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx
RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ
qgZ8Zg//VTv9wNcLrnV+vHZ0jVYaOVHZpJZzhc4XZbJKJxC5U6kWDZp4drTMR+tf
PXWYUlR4X+eklzQs5n+kZQiFNqZ+A6mgWzjCc6p7wkpfQcnZgjrGNFHLdWlZ++pg
hobTKm2rSXoo1zf3AlJpf2i8/6hWouDGSiLtR4se3YHDtH2HfVzhvGwOR/Z1JuCD
OG1Zxq/1j8CHEHX0Az/rL3hGUfWKo0G6P4y2yqlH7UeL0gfE+EDhCUGLkYjeFYqq
WasWosXTm5xO3vqNsf/8l1bpIbk7bUXsoBHO5FMs27vDBQ2VokYkPVLabLnXT+wY
2LcQkVjsAEZN9PkOfGpeNLQ1JiKHWlbwFqZ/VHoT+n1377DZj+Gcs3FzghwN9Hqd
vaQ5EXj9c3R7wCqGN+Ct92hKbdPTnsqX1UmM/FbkfOcMW5Xy9itTzZYMYnYsOeJv
iU5EyHrJNODcSzolPeJnn3fr3X69k1zD9Tf55oAVofP5xXAqPNU0RCN0B7gKK6nI
KDACC1I75noGvpFmoEkZAc3TxlZJyMTzMKoyDeXNWQjIt2gNwIUFaGz7xYIJyGp1
GNxHkPL98fiiTo3Y5nITEraekD4Gj3B8BFUelhdmssCVl2GO23KR5Bmq3fd6CtrS
hZdE4rz+dnBG3BWoMyao2lWZJ3yY/dU0+jI8CUc/R6zKJF70XMk=
=ROMt
-END PGP SIGNATURE-
>From 6df615281b2a649b85ff7670f6d87d3beed0b977 Mon Sep 17 00:00:00 2001
From: jvoisin 
Date: Sun, 6 Jun 2021 16:25:59 +0200
Subject: [PATCH] Fix the CI for recent exiftool versions

Always a joy to deal with withespaces
---
 tests/test_libmat2.py | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

--- a/tests/test_libmat2.py
+++ b/tests/test_libmat2.py
@@ -448,7 +448,7 @@
 'HandlerDescription': 'SoundHandler',
 'HandlerType': 'Metadata',
 'HandlerVendorID': 'Apple',
-'MajorBrand': 'MP4  Base Media v1 [IS0 14496-12:2003]',
+'MajorBrand': 'Base Media v1 [IS0 14496-12:2003]',
 'MediaDataOffset': 48,
 'MediaDataSize': 379872,
 'MediaHeaderVersion': 0,
@@ -502,7 +502,7 @@
 p2 = case['parser'](p1.output_filename)
 for k, v in p2.get_meta().items():
 self.assertIn(k, case['expected_meta'])
-self.assertEqual(v, case['expected_meta'][k])
+self.assertIn(str(case['expected_meta'][k]), str(v))
 self.assertTrue(p2.remove_all())
 
 os.remove(target)

Bug#993208: js8call: TX broken

[Levente Kovacs]

Package: js8call
Version: 2.2.0+ds-2
Severity: critical
Justification: breaks the whole system
X-Debbugs-Cc: leventel...@gmail.com

Dear Maintainer,


   * What led up to the situation?
I isnstalled js8call, and tried to transmit.
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
I pressed the tune button.
   * What was the outcome of this action?
The waterfall was freezing, showing only one line of information. The
TX wasn't happening. Some application, including firefox wasn't able to play
videos. Can't exit JS8CALL. The GUI disappears, but the process remains there.
   * What outcome did you expect instead?
Stable transmit of audio signals, no other app to break.


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

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

Versions of packages js8call depends on:
ii  libc6  2.31-13
ii  libfftw3-single3   3.3.8-2
ii  libgcc-s1  10.2.1-6
ii  libgfortran5   10.2.1-6
ii  libgomp1   10.2.1-6
ii  libhamlib-utils4.0-7
ii  libhamlib4 4.0-7
ii  libqcustomplot2.0  2.0.1+dfsg1-4
ii  libqt5core5a   5.15.2+dfsg-9
ii  libqt5gui5 5.15.2+dfsg-9
ii  libqt5multimedia5  5.15.2-3
ii  libqt5network5 5.15.2+dfsg-9
ii  libqt5serialport5  5.15.2-2
ii  libqt5widgets5 5.15.2+dfsg-9
ii  libsqlite3-0   3.34.1-3
ii  libstdc++6 10.2.1-6
ii  wsjtx-data 2.3.0+repack-2

js8call recommends no packages.

js8call suggests no packages.

Bug#993167: marked as done (dont_be_a_module.patch is too dirty)

[Debian Bug Tracking System]

Your message dated Sat, 28 Aug 2021 15:33:29 +
with message-id 
and subject line Bug#993167: fixed in node-strip-json-comments 4.0.0-2
has caused the Debian Bug report #993167,
regarding dont_be_a_module.patch is too dirty
to be marked as done.

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

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


-- 
993167: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993167
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: node-strip-json-comments
Version: 4.0.0-1
Severity: serious

I have to drop dont_be_a_module.patch ; it's too dirty. I'll do it
later today, but still want to prevent any migration to testing.

J.Puydt
--- End Message ---
--- Begin Message ---
Source: node-strip-json-comments
Source-Version: 4.0.0-2
Done: Julien Puydt 

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

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

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

Debian distribution maintenance software
pp.
Julien Puydt  (supplier of updated node-strip-json-comments 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 28 Aug 2021 17:06:44 +0200
Source: node-strip-json-comments
Architecture: source
Version: 4.0.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Julien Puydt 
Closes: 993167
Changes:
 node-strip-json-comments (4.0.0-2) unstable; urgency=medium
 .
   * Drop the patch to stay require-able (Closes: #993167).
Checksums-Sha1:
 86bec744274c00f90ad2eeb74eb99f4c4e82 2219 
node-strip-json-comments_4.0.0-2.dsc
 4b6f033bf19efc8f8f5073645fc499b51ea0e247 3872 
node-strip-json-comments_4.0.0-2.debian.tar.xz
 cb3116d244b6d4af3cfa5243c462a0ae6371c8bb 8080 
node-strip-json-comments_4.0.0-2_source.buildinfo
Checksums-Sha256:
 326e40553a08eec25daeb85013b3a6f774f31f22d0e9c447506e219dc473d0e9 2219 
node-strip-json-comments_4.0.0-2.dsc
 f32bde19cf67adc684beae139665a1d8b8d172ebbc4eaa273088e16fdd4d7059 3872 
node-strip-json-comments_4.0.0-2.debian.tar.xz
 e3d304e154a96c9277056d1ebe6df2b595d0c61e2ee3995ec97bdec9adffc0c9 8080 
node-strip-json-comments_4.0.0-2_source.buildinfo
Files:
 37bc37b7ff277bf9c2cd2c4a74e5cb5c 2219 javascript optional 
node-strip-json-comments_4.0.0-2.dsc
 421fc3264081537da0f0b590d3ec38e1 3872 javascript optional 
node-strip-json-comments_4.0.0-2.debian.tar.xz
 3a9f5bb073617e632eb4b2a30ee28f06 8080 javascript optional 
node-strip-json-comments_4.0.0-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJGBAEBCgAwFiEEgS7v2KP7pKzk3xFLBMU71/4DBVEFAmEqUUESHGpwdXlkdEBk
ZWJpYW4ub3JnAAoJEATFO9f+AwVRx1kP+wf/bQ4qxPgRdqakXhXsDub82XEOIXhU
znOhRbzzwNpCJP2xibdpEX2F/zofefHLFC8qxi5Kh2dgBNC6hGmKyvKfaQFwyItN
UVAceYaO7Ksg1HhlhpZfzmKSZ2DFxzBCOPjlARbZvMwvDWBWJwOI9PF/IEludrVB
uvo6rE7Mymuay5PjTEEi0UR+nZtQkSgFN4kMqagLi43GubOCfPcJzCzKL5GVHMgX
MZckdwypyZlilMHI9PJkpbFnbj7UvuOVDbzCvDYETcGxPKiVnLHLHnYUnzU3V02y
to2puw7gwKKAaodYtHPW1+KJYUVkTLXyaNWC7SHNST8lICivEYWSYEvKmc/N1AAp
wSxu+05X1mqk2hRKJ+W+m3AMVzoHwo4uGITctnKVVrFO0RFqcCfS+zEspW7lW896
leXF8wpCnVFpXi6HBfM3HR2oVTMpEDBkShX+tigtmOlQCBifoXdLE51tfK72pxnc
UMiCLelKQP6zwZDckyDjYlO4r4OkUbGFbXU7TYQWMNNw8IINGXBTOCYWnaDRnTWo
wgD7K5jMPNV4k9Bo9SZXJXSqzzoQdMAkicbekkHF815gmGSaPpDGl2sFLlluKxHf
MpyWTFCNf62e86o+nFYNOHrvC6b231ISMDLXfXwe4yWNOtsVOFbttvKedRIwMLjJ
bHI8Qx7bSUrn
=it6y
-END PGP SIGNATURE End Message ---

Bug#993167: marked as pending in node-strip-json-comments

[Julien Puydt]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/js-team/node-strip-json-comments/-/commit/4b54da3ae6c2a1dc83a362ab0726d6f4ed0a08a5


Drop the patch to stay require-able (Closes: #993167)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/993167

Processed: Bug#993167 marked as pending in node-strip-json-comments

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #993167 [node-strip-json-comments] dont_be_a_module.patch is too dirty
Added tag(s) pending.

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

Bug#993164: proftpd-core: When upgrading from Buster to Bullseyes, the installation of ProFTPd fails

[Hilmar Preuße]

Am 28.08.2021 um 16:46 teilte Andreas Günther mit:

Hi,

please keep the bug in Cc.


here I have the output from systemctl status proftpd.service:
proftpd.service - ProFTPD FTP Server
  Loaded: loaded (/lib/systemd/system/proftpd.service; enabled; 
vendor preset: enabled)
  Active: failed (Result: exit-code) since Sat 2021-08-28 10:16:33 
CEST; 6h ago
     Process: 37982 ExecStartPre=/usr/sbin/proftpd --configtest -c 
$CONFIG_FILE (code=exited, status=1/FAILURE)

     CPU: 6ms

Aug 28 10:16:33 web systemd[1]: Starting ProFTPD FTP Server...
Aug 28 10:16:33 web proftpd[37982]: Checking syntax of configuration file
Aug 28 10:16:33 web proftpd[37982]: 2021-08-28 10:16:33,852 web 
proftpd[37982]: mod_dso/0.5: unable to load 'mod_tls.c'; check to see if 
'/usr/lib/proftpd/mod_tls.la' exists
Aug 28 10:16:33 web proftpd[37982]: 2021-08-28 10:16:33,852 web 
proftpd[37982]: fatal: LoadModule: error loading module 'mod_tls.c': 
Datei oder Verzeichnis nicht gefunden on line 16 o>
Aug 28 10:16:33 web proftpd[37982]: 2021-08-28 10:16:33,852 web 
proftpd[37982]: warning: unable to include '/etc/proftpd/modules.conf': 
Die Operation ist nicht erlaubt
Aug 28 10:16:33 web proftpd[37982]: 2021-08-28 10:16:33,853 web 
proftpd[37982]: mod_dso/0.5: unable to load 'mod_wrap.c'; check to see 
if '/usr/lib/proftpd/mod_wrap.la' exists
Aug 28 10:16:33 web proftpd[37982]: 2021-08-28 10:16:33,853 web 
proftpd[37982]: fatal: LoadModule: error loading module 'mod_wrap.c': 
Datei oder Verzeichnis nicht gefunden on line 8 o>
Aug 28 10:16:33 web systemd[1]: proftpd.service: Control process exited, 
code=exited, status=1/FAILURE
Aug 28 10:16:33 web systemd[1]: proftpd.service: Failed with result 
'exit-code'.

Aug 28 10:16:33 web systemd[1]: Failed to start ProFTPD FTP Server.



Hmm, weird: the modules in question should be provided by 
proftpd-mod-wrap & proftpd-mod-crypto, should should have installed. 
Could you check if the files /usr/lib/proftpd/mod_tls.so & 
/usr/lib/proftpd/mod_wrap.so do exist?


Hilmar
--
sigfault




OpenPGP_signature
Description: OpenPGP digital signature

Bug#993207: regression: constant ~20% CPU usage + crackling sound since 15.0+dfsg1-2

[Christoph Anton Mitterer]

Source: pulseaudio
Version: 15.0+dfsg1-2
Severity: grave
Justification: renders package unusable



Hi

Since upgrading to 15.0+dfsg1-2, the pulseaudio daemon runs constantly at 
around ~20% CPU
on my system (even when no sound is played).

If sound is played it's constantly crackling.

Downgrading to the previous 14.2-2 from testing (and restarting the daemon) 
fixes the issue.

Any ideas?

Thanks,
Chris.


-- Package-specific info:
File '/etc/default/pulseaudio' does not exist


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

Kernel: Linux 5.10.0-8-amd64 (SMP w/4 CPU threads)
Locale: LANG=en_DE.UTF-8, LC_CTYPE=en_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

-- no debconf information
# This file is part of PulseAudio.
#
# PulseAudio is free software; you can redistribute it and/or modify
# it under the terms of the GNU Lesser General Public License as published by
# the Free Software Foundation; either version 2 of the License, or
# (at your option) any later version.
#
# PulseAudio is distributed in the hope that it will be useful, but
# WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
# General Public License for more details.
#
# You should have received a copy of the GNU Lesser General Public License
# along with PulseAudio; if not, see .

## Configuration file for PulseAudio clients. See pulse-client.conf(5) for
## more information. Default values are commented out.  Use either ; or # for
## commenting.

; default-sink =
; default-source =
; default-server =
; default-dbus-server =

; autospawn = yes
; daemon-binary = /usr/bin/pulseaudio
; extra-arguments = --log-target=syslog

; cookie-file =

; enable-shm = yes
; shm-size-bytes = 0 # setting this 0 will use the system-default, usually 64 
MiB

; auto-connect-localhost = no
; auto-connect-display = no
# This file is part of PulseAudio.
#
# PulseAudio is free software; you can redistribute it and/or modify
# it under the terms of the GNU Lesser General Public License as published by
# the Free Software Foundation; either version 2 of the License, or
# (at your option) any later version.
#
# PulseAudio is distributed in the hope that it will be useful, but
# WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
# General Public License for more details.
#
# You should have received a copy of the GNU Lesser General Public License
# along with PulseAudio; if not, see .

## Configuration file for the PulseAudio daemon. See pulse-daemon.conf(5) for
## more information. Default values are commented out.  Use either ; or # for
## commenting.

; daemonize = no
; fail = yes
; allow-module-loading = yes
; allow-exit = yes
; use-pid-file = yes
; system-instance = no
; local-server-type = user
; enable-shm = yes
; enable-memfd = yes
; shm-size-bytes = 0 # setting this 0 will use the system-default, usually 64 
MiB
; lock-memory = no
; cpu-limit = no

; high-priority = yes
; nice-level = -11

; realtime-scheduling = yes
; realtime-priority = 5

; exit-idle-time = 20
; scache-idle-time = 20

; dl-search-path = (depends on architecture)

; load-default-script-file = yes
; default-script-file = /etc/pulse/default.pa

; log-target = auto
; log-level = notice
; log-meta = no
; log-time = no
; log-backtrace = 0

; resample-method = speex-float-1
; avoid-resampling = false
; enable-remixing = yes
; remixing-use-all-sink-channels = yes
; remixing-produce-lfe = no
; remixing-consume-lfe = no
; lfe-crossover-freq = 0

; flat-volumes = no

; rescue-streams = yes

; rlimit-fsize = -1
; rlimit-data = -1
; rlimit-stack = -1
; rlimit-core = -1
; rlimit-as = -1
; rlimit-rss = -1
; rlimit-nproc = -1
; rlimit-nofile = 256
; rlimit-memlock = -1
; rlimit-locks = -1
; rlimit-sigpending = -1
; rlimit-msgqueue = -1
; rlimit-nice = 31
; rlimit-rtprio = 9
; rlimit-rttime = 20

; default-sample-format = s16le
; default-sample-rate = 44100
; alternate-sample-rate = 48000
; default-sample-channels = 2
; default-channel-map = front-left,front-right

; default-fragments = 4
; default-fragment-size-msec = 25

; enable-deferred-volume = yes
; deferred-volume-safety-margin-usec = 8000
; deferred-volume-extra-delay-usec = 0
#!/usr/bin/pulseaudio -nF
#
# This file is part of PulseAudio.
#
# PulseAudio is free software; you can redistribute it and/or modify it
# under the terms of the GNU Lesser General Public License as published by
# the Free Software Foundation; either version 2 of the License, or
# (at your option) any later version.
#
# PulseAudio is distributed in the hope that it will be useful, but
# WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR 

Bug#993071: kmail: symbol lookup error: /lib/x86_64-linux-gnu/libKF5Libkleo.so.5: undefined symbol: _ZN5GpgME6UserID9SignatureltERKS1_

[Norbert Preining]

> libgpgmepp.so.6 => /usr/local/lib/libgpgmepp.so.6 (0x7efde318f000)

That is a version you compiled yourself, and you cannot expect that this
is supported.

Please remove local version and retest.

Best

Norbert

--
PREINING Norbert  https://www.preining.info
Fujitsu Research  +  IFMGA Guide  +  TU Wien  +  TeX Live  + Debian Dev
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Bug#993071: kmail: symbol lookup error: /lib/x86_64-linux-gnu/libKF5Libkleo.so.5: undefined symbol: _ZN5GpgME6UserID9SignatureltERKS1_

[Johannes Rohr]

Am 28.08.21 um 16:50 schrieb Norbert Preining:
>> libgpgmepp.so.6 => /usr/local/lib/libgpgmepp.so.6 (0x7efde318f000)
> That is a version you compiled yourself, and you cannot expect that this
> is supported.

Yikes. Must have done that ages ago and forgotten about it.

Sorry,

Johannes



>
> Please remove local version and retest.
>
> Best
>
> Norbert
>
> --
> PREINING Norbert  https://www.preining.info
> Fujitsu Research  +  IFMGA Guide  +  TU Wien  +  TeX Live  + Debian Dev
> GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Bug#993071: marked as done (kmail: symbol lookup error: /lib/x86_64-linux-gnu/libKF5Libkleo.so.5: undefined symbol: _ZN5GpgME6UserID9SignatureltERKS1_)

[Debian Bug Tracking System]

Your message dated Sat, 28 Aug 2021 16:12:25 +0200
with message-id 
and subject line Re: Bug#993071: kmail: symbol lookup error: 
/lib/x86_64-linux-gnu/libKF5Libkleo.so.5: undefined symbol: 
_ZN5GpgME6UserID9SignatureltERKS1_
has caused the Debian Bug report #993071,
regarding kmail: symbol lookup error: /lib/x86_64-linux-gnu/libKF5Libkleo.so.5: 
undefined symbol: _ZN5GpgME6UserID9SignatureltERKS1_
to be marked as done.

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

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


-- 
993071: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993071
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: kmail
Version: 4:21.08.0-1
Severity: grave
Justification: renders package unusable

As of today's upgrades, kmail fails to start:

kmail: symbol lookup error: /lib/x86_64-linux-gnu/libKF5Libkleo.so.5:
undefined symbol: _ZN5GpgME6UserID9SignatureltERKS1_



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

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

Versions of packages kmail depends on:
ii  akonadi-server   4:21.08.0-1
ii  kdepim-runtime   4:21.08.0-1
ii  kio  5.83.0-2
ii  libc6    2.31-17
ii  libgcc-s1    11.2.0-3
ii  libgpgmepp6  1.16.0-1
ii  libkf5akonadiagentbase5 [libkf5akonadiagentbase5-21.08]  4:21.08.0-1
ii  libkf5akonadicontact5 [libkf5akonadicontact5-21.08]  4:21.08.0-1
ii  libkf5akonadicore5abi2 [libkf5akonadicore5-21.08]    4:21.08.0-1
ii  libkf5akonadimime5 [libkf5akonadimime5-21.08]    4:21.08.0-1
ii  libkf5akonadisearch-bin  4:21.08.0-1
ii  libkf5akonadisearch-plugins  4:21.08.0-1
ii  libkf5akonadisearchdebug5 [libkf5akonadisearchdebug5-21.08]  4:21.08.0-1
ii  libkf5akonadisearchpim5 [libkf5akonadisearchpim5-21.08]  4:21.08.0-1
ii  libkf5akonadiwidgets5abi1 [libkf5akonadiwidgets5-21.08]  4:21.08.0-1
ii  libkf5bookmarks5 5.83.0-2
ii  libkf5calendarcore5abi2  5:5.83.0-2
ii  libkf5calendarutils5 [libkf5calendarutils5-21.08]    4:21.08.0-1
ii  libkf5codecs5    5.83.0-2
ii  libkf5completion5    5.83.0-2
ii  libkf5configcore5    5.83.0-2
ii  libkf5configgui5 5.83.0-2
ii  libkf5configwidgets5 5.83.0-3
ii  libkf5contacts5  5:5.83.0-2
ii  libkf5coreaddons5    5.83.0-2
ii  libkf5crash5 5.83.0-2
ii  libkf5dbusaddons5    5.83.0-2
ii  libkf5grantleetheme-plugins  21.08.0-1
ii  libkf5gravatar5abi2 [libkf5gravatar5-21.08]  4:21.08.0-1
ii  libkf5guiaddons5 5.83.0-2
ii  libkf5i18n5  5.83.0-3
ii  libkf5iconthemes5    5.83.0-2
ii  libkf5identitymanagement5 [libkf5identitymanagement5-21.08]  21.08.0-1
ii  libkf5itemmodels5    5.83.0-2
ii  libkf5itemviews5 5.83.0-2
ii  libkf5jobwidgets5    5.83.0-2
ii  libkf5kcmutils5  5.83.0-2
ii  libkf5kiocore5   5.83.0-2
ii  libkf5kiofilewidgets5    5.83.0-2
ii  libkf5kiogui5    5.83.0-2
ii  libkf5kiowidgets5    5.83.0-2
ii  libkf5kontactinterface5 [libkf5kontactinterface5-21.08]  21.08.0-1
ii  libkf5ksieveui5 [libkf5ksieveui5-21.08]  4:21.08.0-1
ii  libkf5ldap5abi1 

Processed: bug 985840 is forwarded to https://gitlab.com/gitlab-org/gitlab-shell/-/issues/197

[Debian Bug Tracking System]

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

> forwarded 985840 https://gitlab.com/gitlab-org/gitlab-shell/-/issues/197
Bug #985840 [gitlab-shell] gitlab-shell: should not ship /usr/bin/check
Set Bug forwarded-to-address to 
'https://gitlab.com/gitlab-org/gitlab-shell/-/issues/197'.
> thanks
Stopping processing here.

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

Bug#993071: kmail: symbol lookup error: /lib/x86_64-linux-gnu/libKF5Libkleo.so.5: undefined symbol: _ZN5GpgME6UserID9SignatureltERKS1_

[Norbert Preining]

Hi Daniel, hi all

> kmail: symbol lookup error: /lib/x86_64-linux-gnu/libKF5Libkleo.so.5:
> undefined symbol: _ZN5GpgME6UserID9SignatureltERKS1_

Sending this through c++filt we see
GpgME::UserID::Signature::operator<(GpgME::UserID::Signature const&)

That looks like an API breakage in libgpgme to me. Dropping symbols and
not changing soname etc.

GPGME maintainers, do you have any comments or explanations?

Thanks

Norbert

--
PREINING Norbert  https://www.preining.info
Fujitsu Research  +  IFMGA Guide  +  TU Wien  +  TeX Live  + Debian Dev
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Bug#959452: marked as done (array-info: Build-Depends on obsolete package linux-kernel-headers)

[Debian Bug Tracking System]

Your message dated Sat, 28 Aug 2021 12:49:05 +
with message-id 
and subject line Bug#959452: fixed in array-info 0.16-6
has caused the Debian Bug report #959452,
regarding array-info: Build-Depends on obsolete package linux-kernel-headers
to be marked as done.

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

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


-- 
959452: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959452
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:array-info
Version: 0.16-4
Severity: serious

linux-kernel-headers was removed from unstable in 2007 (I think).  It
is now effectively a virtual package provided by linux-libc-dev, but
it's not a documented virtual package name and I would like to stop
providing it.  Please change the dependency to linux-libc-dev.

Ben.

-- 
Ben Hutchings
The first rule of tautology club is the first rule of tautology club.



signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---
Source: array-info
Source-Version: 0.16-6
Done: Petter Reinholdtsen 

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

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

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

Debian distribution maintenance software
pp.
Petter Reinholdtsen  (supplier of updated array-info package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 28 Aug 2021 14:29:17 +0200
Source: array-info
Architecture: source
Version: 0.16-6
Distribution: unstable
Urgency: medium
Maintainer: Petter Reinholdtsen 
Changed-By: Petter Reinholdtsen 
Closes: 959452
Changes:
 array-info (0.16-6) unstable; urgency=medium
 .
   * Include fix from 0.16-4.1 by Sudip Mukherjee to remove dependency
 on linux-kernel-headers (Closes: #959452).
Checksums-Sha1:
 4473095b06f27ce4ed710db6b8e5fa9d72c163aa 1851 array-info_0.16-6.dsc
 ef614a1ac52db7e81e8fefb0b586bb84a2834f06 3372 array-info_0.16-6.debian.tar.xz
 8935e395d87ee66c14a9d756e8c138a228541514 7909 
array-info_0.16-6_source.buildinfo
Checksums-Sha256:
 3b01086f09e7514306090325cfc126678d814a4670f96c652d809079abc5ff76 1851 
array-info_0.16-6.dsc
 d7ebb0ac5f3ec7367369027cd57feeb89b7dafbecf5e25e1f5893c23f2e6b4bf 3372 
array-info_0.16-6.debian.tar.xz
 3f75c82ed9cd86d0b9b180f18299a4d403951340f4af34e0d815db4c72d6d195 7909 
array-info_0.16-6_source.buildinfo
Files:
 b7156be5a5e10e4b9ec1ca5eb77f0714 1851 admin optional array-info_0.16-6.dsc
 6f0743413610edcab5f3e6f775ae3a81 3372 admin optional 
array-info_0.16-6.debian.tar.xz
 2200c2ff506d54525ab953893e7a3129 7909 admin optional 
array-info_0.16-6_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEERqLf4owIeylOb9kkgSgKoIe6+w4FAmEqLFQACgkQgSgKoIe6
+w4uDg//c/Gygebo+7DXxHDsOD9+2VW+xnYR3TtrqLAKKxPR3K9WK/PonPLx1K8Y
HOxrWd8iE76OEAXCmo8OU9Zs639pVWBxevxFaOHVdSfgoqk/lkmB0xksz9YnAWPk
OkO3ZRJEs0Qb8+7hTN7zgfUdGF2krtNWKHL6cMmD1JjanaykZi1NH+sHedkNhZBA
s364UkCFKuUXIKF7MerLbe3PqN/PNI//id+JDII89p5fs8T7ox2jcXq1tYyBlErk
ysEr9E7d7gRVmZ3A1822fY6QAUPnbnDc6/VKFQSDRShHBMAha40YvXU6jbOeW52Z
9/z136k4vhBPeU7E2rwkpNXh0fhVRdFC0ELIHRuC1DOxqK/F54Wf6p4gPQ+N/Nql
GBWMWnUzhKlbE8bFc6O6m/bEvl1nNgHOVkiYKe7wGb5703kTjHmKCWdqBbnojqFP
cb6GB+lp6ApSy1m5FCLCaVs/dbGCrpOpLr3tspwj7QLdL5qGRP6oSCVCfq/9Q2NA
6jg09Zh0Pr/z2ejHWgCRG0nNXrjIRqgvxhzBNbDrTl/N/EvCT7jV31bG77Pab19S
cijE7B30sYWMYiydey0gFtXwVBZpFVggXoCKMZ0JTucuaTkSwMX6OsH3RW5dZjNC
RkBBDZN6kF/MLRLGDpyRGLdYNKWwtxMFZQ+E8JVr+OWeTZmv7W8=
=/x16
-END PGP SIGNATURE End Message ---

Processed: Re: Bug#992087: libfonts-java: contains a file with a non-free "disparaging to Sun" license

[Debian Bug Tracking System]

Processing control commands:

> tags -1 pending
Bug #992087 [src:libfonts-java] libfonts-java: contains a file with a non-free 
"disparaging to Sun" license
Added tag(s) pending.

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

Bug#992087: libfonts-java: contains a file with a non-free "disparaging to Sun" license

[Pierre Gruet]

Control: tags -1 pending

Hello,

After a deeper examination, I see the file with the non-free contents is 
useless anyway, none of the files it attempts to patch exists. I think 
this file got lost here as it obviously comes from itext, not libfonts.


I offer to team-upload the package soon.

Best,

--
Pierre

Bug#993176: libssh2 FTBFS: configure.ac:130: error: m4_undefine: undefined macro: backend

[Helmut Grohne]

Source: libssh2
Version: 1.9.0-3
Severity: serious
Tags: ftbfs

libssh2 fails to build from source. A build ends as follows:

|dh_autoreconf
| configure.ac:130: error: m4_undefine: undefined macro: backend
| configure.ac:130: the top level
| autom4te: error: /usr/bin/m4 failed with exit status: 1
| aclocal: error: /usr/bin/autom4te failed with exit status: 1
| autoreconf: error: aclocal failed with exit status: 1
| dh_autoreconf: error: autoreconf -f -i returned exit code 1
| make: *** [debian/rules:13: binary] Error 25
| dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 
2

Helmut

Processed: tagging 959452

[Debian Bug Tracking System]

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

> tags 959452 + ftbfs
Bug #959452 {Done: Sudip Mukherjee } 
[src:array-info] array-info: Build-Depends on obsolete package 
linux-kernel-headers
Added tag(s) ftbfs.
> thanks
Stopping processing here.

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

Bug#993172: gcc-11-base: i386 (Geode LX): latest testing migration produces sig ILL (due to #993162 ?)

[Francesco Poli (wintermute)]

Package: gcc-11-base
Version: 11.2.0-3
Severity: grave
Justification: renders package unusable

Hello!

During today's upgrade, apt-listbugs[^NOTE] warned me that upgrading
libc6 (2.31-13 -> 2.31-17) would produce sig ILL on Geode LX i386 CPUs.
See bug [#993162].

Since I have a Geode LX based box (a Soekris net5501), I decided to
pin libc6 to version 2.31-13, in order to avoid issues, while waiting
for a fixed version of libc6 to migrate to Debian testing (bookworm).

Despite this, I began to see sig ILL (for instance, the smartd daemon
could not be restarted), after the upgrade.

Some tests revealed that these issues were caused by the upgrades
of libstdc++6, libgcc-s1, and libgomp1 (10.2.1-6->11.2.0-3),
allowed by the new installation of gcc-11-base.
Downgrading those three packages and removing gcc-11-base seems to
avoid the sig ILL issues.

I am therefore filing this bug report against gcc-11-base, as a
courtesy to other apt-listbugs users (who will thus be warned
about the need to avoid installing gcc-11-base on Geode LX systems).

Please do not close, reassign, or downgrade the severity of this bug
report, until a proper fix is in place in libc6 and its effects have
propagated to binary packages generated from gcc-11.

Feel free to block this bug report by 993162, if appropriate.

Thanks for your understanding and patience!


[^NOTE]: for the record, I am the current maintainer of apt-listbugs
 and, yes, that package is useful to me as well (of course!)

[#993162]: 


-- System Information:
Debian Release: bookworm/sid
  APT prefers testing
  APT policy: (800, 'testing'), (500, 'unstable')
Architecture: i386 (i586)

Kernel: Linux 5.10.0-8-686 (SMP w/1 CPU thread)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
LSM: AppArmor: enabled

Bug#993162: libc6: i386 (Geode LX): latest push to Bookwork produces multiple sig ILL

[Martin-Éric Racine]

la 28. elok. 2021 klo 13.43 Martin-Éric Racine
(martin-eric.rac...@iki.fi) kirjoitti:
>
> la 28. elok. 2021 klo 13.40 Aurelien Jarno (aurel...@aurel32.net) kirjoitti:
> >
> > On 2021-08-28 13:36, Martin-Éric Racine wrote:
> > > la 28. elok. 2021 klo 12.58 Aurelien Jarno (aurel...@aurel32.net) 
> > > kirjoitti:
> > > > > $ sudo coredumpctl debug 1011
> > > > >PID: 1011 (apt-get)
> > > > >UID: 0 (root)
> > > > >GID: 0 (root)
> > > > > Signal: 4 (ILL)
> > > > >  Timestamp: Sat 2021-08-28 11:00:34 EEST (3min 22s ago)
> > > > >   Command Line: apt-get --quiet --quiet update
> > > > > Executable: /usr/bin/apt-get
> > > > >  Control Group: /user.slice/user-1000.slice/session-4.scope
> > > > >   Unit: session-4.scope
> > > > >  Slice: user-1000.slice
> > > > >Session: 4
> > > > >  Owner UID: 1000 (perkelix)
> > > > >Boot ID: 77dfa6eb16584c02b84de4e2b8feb781
> > > > > Machine ID: 1063a9d1fb9df6e371ea9f94491345ed
> > > > >   Hostname: geode
> > > > >Storage: 
> > > > > /var/lib/systemd/coredump/core.apt-get.0.77dfa6eb16584c02b84de4e2b8feb781.1011.163013763400.zst
> > > > >Message: Process 1011 (apt-get) of user 0 dumped core.
> > > > >
> > > > > Stack trace of thread 1011:
> > > > > #0  0xb7ad2ed0 __cpu_indicator_init 
> > > > > (libgcc_s.so.1 + 0x2ed0)
> > > > > #1  0xb7faf02c call_init (ld-linux.so.2 + 
> > > > > 0x1102c)
> > > > > #2  0xb7faf132 call_init (ld-linux.so.2 + 
> > > > > 0x11132)
> > > > > #3  0xb7f9f0fa _dl_start_user (ld-linux.so.2 
> > > > > + 0x10fa)
> > > >
> > > > The SIGILL happens in __cpu_indicator_init which is provided by
> > > > libgcc-s1. Bookworm got a new upstream version of this package compared
> > > > to bullseye, so if you also upgraded it, it's more likely to be the
> > > > issue. In that case, have you tried to downgrade it?
> > >
> > > Just did. Here's the result:
> > >
> > > $ sudo coredumpctl debug 2083
> > >PID: 2083 (apt-get)
> > >UID: 0 (root)
> > >GID: 0 (root)
> > > Signal: 4 (ILL)
> > >  Timestamp: Sat 2021-08-28 13:33:05 EEST (1min 36s ago)
> > >   Command Line: apt-get update
> > > Executable: /usr/bin/apt-get
> > >  Control Group: /user.slice/user-1000.slice/session-2.scope
> > >   Unit: session-2.scope
> > >  Slice: user-1000.slice
> > >Session: 2
> > >  Owner UID: 1000 (perkelix)
> > >Boot ID: a200afe0e5134b8a812b05c898c8b859
> > > Machine ID: 1063a9d1fb9df6e371ea9f94491345ed
> > >   Hostname: geode
> > >Storage:
> > > /var/lib/systemd/coredump/core.apt-get.0.a200afe0e5134b8a812b05c898c8b859.2083.163014678500.zst
> > >Message: Process 2083 (apt-get) of user 0 dumped core.
> > >
> > > Stack trace of thread 2083:
> > > #0  0xb7ae9170 frame_dummy (libstdc++.so.6 + 
> > > 0x87170)
> >
> > It seems that all libraries from gcc-11 are now compiled with Intel CET
> > enabled, following an upstream commit [1]. I guess you will also have to
> > downgrade libstdc++6.
> >
> > [1] 
> > https://gcc.gnu.org/git/?p=gcc.git;a=commit;h=8d286dd118a5bd16f7ae0fb9dfcdcfd020bea803
>
> Sure enough, downgrading libstdc++6 too fixed it.

Preventing other binaries from crashing with sig ILL required
downgrading libgomp1 and other packages build from GCC11 as well.

Martin-Éric

Bug#993162: libc6: i386 (Geode LX): latest push to Bookwork produces multiple sig ILL

[Martin-Éric Racine]

la 28. elok. 2021 klo 13.40 Aurelien Jarno (aurel...@aurel32.net) kirjoitti:
>
> On 2021-08-28 13:36, Martin-Éric Racine wrote:
> > la 28. elok. 2021 klo 12.58 Aurelien Jarno (aurel...@aurel32.net) kirjoitti:
> > > > $ sudo coredumpctl debug 1011
> > > >PID: 1011 (apt-get)
> > > >UID: 0 (root)
> > > >GID: 0 (root)
> > > > Signal: 4 (ILL)
> > > >  Timestamp: Sat 2021-08-28 11:00:34 EEST (3min 22s ago)
> > > >   Command Line: apt-get --quiet --quiet update
> > > > Executable: /usr/bin/apt-get
> > > >  Control Group: /user.slice/user-1000.slice/session-4.scope
> > > >   Unit: session-4.scope
> > > >  Slice: user-1000.slice
> > > >Session: 4
> > > >  Owner UID: 1000 (perkelix)
> > > >Boot ID: 77dfa6eb16584c02b84de4e2b8feb781
> > > > Machine ID: 1063a9d1fb9df6e371ea9f94491345ed
> > > >   Hostname: geode
> > > >Storage: 
> > > > /var/lib/systemd/coredump/core.apt-get.0.77dfa6eb16584c02b84de4e2b8feb781.1011.163013763400.zst
> > > >Message: Process 1011 (apt-get) of user 0 dumped core.
> > > >
> > > > Stack trace of thread 1011:
> > > > #0  0xb7ad2ed0 __cpu_indicator_init 
> > > > (libgcc_s.so.1 + 0x2ed0)
> > > > #1  0xb7faf02c call_init (ld-linux.so.2 + 
> > > > 0x1102c)
> > > > #2  0xb7faf132 call_init (ld-linux.so.2 + 
> > > > 0x11132)
> > > > #3  0xb7f9f0fa _dl_start_user (ld-linux.so.2 + 
> > > > 0x10fa)
> > >
> > > The SIGILL happens in __cpu_indicator_init which is provided by
> > > libgcc-s1. Bookworm got a new upstream version of this package compared
> > > to bullseye, so if you also upgraded it, it's more likely to be the
> > > issue. In that case, have you tried to downgrade it?
> >
> > Just did. Here's the result:
> >
> > $ sudo coredumpctl debug 2083
> >PID: 2083 (apt-get)
> >UID: 0 (root)
> >GID: 0 (root)
> > Signal: 4 (ILL)
> >  Timestamp: Sat 2021-08-28 13:33:05 EEST (1min 36s ago)
> >   Command Line: apt-get update
> > Executable: /usr/bin/apt-get
> >  Control Group: /user.slice/user-1000.slice/session-2.scope
> >   Unit: session-2.scope
> >  Slice: user-1000.slice
> >Session: 2
> >  Owner UID: 1000 (perkelix)
> >Boot ID: a200afe0e5134b8a812b05c898c8b859
> > Machine ID: 1063a9d1fb9df6e371ea9f94491345ed
> >   Hostname: geode
> >Storage:
> > /var/lib/systemd/coredump/core.apt-get.0.a200afe0e5134b8a812b05c898c8b859.2083.163014678500.zst
> >Message: Process 2083 (apt-get) of user 0 dumped core.
> >
> > Stack trace of thread 2083:
> > #0  0xb7ae9170 frame_dummy (libstdc++.so.6 + 
> > 0x87170)
>
> It seems that all libraries from gcc-11 are now compiled with Intel CET
> enabled, following an upstream commit [1]. I guess you will also have to
> downgrade libstdc++6.
>
> [1] 
> https://gcc.gnu.org/git/?p=gcc.git;a=commit;h=8d286dd118a5bd16f7ae0fb9dfcdcfd020bea803

Sure enough, downgrading libstdc++6 too fixed it.

Martin-Éric

Bug#993162: libc6: i386 (Geode LX): latest push to Bookwork produces multiple sig ILL

[Aurelien Jarno]

On 2021-08-28 13:36, Martin-Éric Racine wrote:
> la 28. elok. 2021 klo 12.58 Aurelien Jarno (aurel...@aurel32.net) kirjoitti:
> > > $ sudo coredumpctl debug 1011
> > >PID: 1011 (apt-get)
> > >UID: 0 (root)
> > >GID: 0 (root)
> > > Signal: 4 (ILL)
> > >  Timestamp: Sat 2021-08-28 11:00:34 EEST (3min 22s ago)
> > >   Command Line: apt-get --quiet --quiet update
> > > Executable: /usr/bin/apt-get
> > >  Control Group: /user.slice/user-1000.slice/session-4.scope
> > >   Unit: session-4.scope
> > >  Slice: user-1000.slice
> > >Session: 4
> > >  Owner UID: 1000 (perkelix)
> > >Boot ID: 77dfa6eb16584c02b84de4e2b8feb781
> > > Machine ID: 1063a9d1fb9df6e371ea9f94491345ed
> > >   Hostname: geode
> > >Storage: 
> > > /var/lib/systemd/coredump/core.apt-get.0.77dfa6eb16584c02b84de4e2b8feb781.1011.163013763400.zst
> > >Message: Process 1011 (apt-get) of user 0 dumped core.
> > >
> > > Stack trace of thread 1011:
> > > #0  0xb7ad2ed0 __cpu_indicator_init 
> > > (libgcc_s.so.1 + 0x2ed0)
> > > #1  0xb7faf02c call_init (ld-linux.so.2 + 0x1102c)
> > > #2  0xb7faf132 call_init (ld-linux.so.2 + 0x11132)
> > > #3  0xb7f9f0fa _dl_start_user (ld-linux.so.2 + 
> > > 0x10fa)
> >
> > The SIGILL happens in __cpu_indicator_init which is provided by
> > libgcc-s1. Bookworm got a new upstream version of this package compared
> > to bullseye, so if you also upgraded it, it's more likely to be the
> > issue. In that case, have you tried to downgrade it?
> 
> Just did. Here's the result:
> 
> $ sudo coredumpctl debug 2083
>PID: 2083 (apt-get)
>UID: 0 (root)
>GID: 0 (root)
> Signal: 4 (ILL)
>  Timestamp: Sat 2021-08-28 13:33:05 EEST (1min 36s ago)
>   Command Line: apt-get update
> Executable: /usr/bin/apt-get
>  Control Group: /user.slice/user-1000.slice/session-2.scope
>   Unit: session-2.scope
>  Slice: user-1000.slice
>Session: 2
>  Owner UID: 1000 (perkelix)
>Boot ID: a200afe0e5134b8a812b05c898c8b859
> Machine ID: 1063a9d1fb9df6e371ea9f94491345ed
>   Hostname: geode
>Storage:
> /var/lib/systemd/coredump/core.apt-get.0.a200afe0e5134b8a812b05c898c8b859.2083.163014678500.zst
>Message: Process 2083 (apt-get) of user 0 dumped core.
> 
> Stack trace of thread 2083:
> #0  0xb7ae9170 frame_dummy (libstdc++.so.6 + 0x87170)

It seems that all libraries from gcc-11 are now compiled with Intel CET
enabled, following an upstream commit [1]. I guess you will also have to
downgrade libstdc++6.

[1] 
https://gcc.gnu.org/git/?p=gcc.git;a=commit;h=8d286dd118a5bd16f7ae0fb9dfcdcfd020bea803

-- 
Aurelien Jarno  GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://www.aurel32.net

Processed: unarchiving 959452

[Debian Bug Tracking System]

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

> unarchive 959452
Bug #959452 {Done: Sudip Mukherjee } 
[src:array-info] array-info: Build-Depends on obsolete package 
linux-kernel-headers
Unarchived Bug 959452
> thanks
Stopping processing here.

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

Processed: found 993162 in gcc-11/11.2.0-3

[Debian Bug Tracking System]

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

> found 993162 gcc-11/11.2.0-3
Bug #993162 [libgcc-s1] libgcc-s1: i386 (Geode LX): latest push to Bookwork 
produces multiple sig ILL
Marked as found in versions gcc-11/11.2.0-3.
> thanks
Stopping processing here.

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

Bug#993162: libc6: i386 (Geode LX): latest push to Bookwork produces multiple sig ILL

[Martin-Éric Racine]

la 28. elok. 2021 klo 12.58 Aurelien Jarno (aurel...@aurel32.net) kirjoitti:
> > $ sudo coredumpctl debug 1011
> >PID: 1011 (apt-get)
> >UID: 0 (root)
> >GID: 0 (root)
> > Signal: 4 (ILL)
> >  Timestamp: Sat 2021-08-28 11:00:34 EEST (3min 22s ago)
> >   Command Line: apt-get --quiet --quiet update
> > Executable: /usr/bin/apt-get
> >  Control Group: /user.slice/user-1000.slice/session-4.scope
> >   Unit: session-4.scope
> >  Slice: user-1000.slice
> >Session: 4
> >  Owner UID: 1000 (perkelix)
> >Boot ID: 77dfa6eb16584c02b84de4e2b8feb781
> > Machine ID: 1063a9d1fb9df6e371ea9f94491345ed
> >   Hostname: geode
> >Storage: 
> > /var/lib/systemd/coredump/core.apt-get.0.77dfa6eb16584c02b84de4e2b8feb781.1011.163013763400.zst
> >Message: Process 1011 (apt-get) of user 0 dumped core.
> >
> > Stack trace of thread 1011:
> > #0  0xb7ad2ed0 __cpu_indicator_init (libgcc_s.so.1 
> > + 0x2ed0)
> > #1  0xb7faf02c call_init (ld-linux.so.2 + 0x1102c)
> > #2  0xb7faf132 call_init (ld-linux.so.2 + 0x11132)
> > #3  0xb7f9f0fa _dl_start_user (ld-linux.so.2 + 
> > 0x10fa)
>
> The SIGILL happens in __cpu_indicator_init which is provided by
> libgcc-s1. Bookworm got a new upstream version of this package compared
> to bullseye, so if you also upgraded it, it's more likely to be the
> issue. In that case, have you tried to downgrade it?

Just did. Here's the result:

$ sudo coredumpctl debug 2083
   PID: 2083 (apt-get)
   UID: 0 (root)
   GID: 0 (root)
Signal: 4 (ILL)
 Timestamp: Sat 2021-08-28 13:33:05 EEST (1min 36s ago)
  Command Line: apt-get update
Executable: /usr/bin/apt-get
 Control Group: /user.slice/user-1000.slice/session-2.scope
  Unit: session-2.scope
 Slice: user-1000.slice
   Session: 2
 Owner UID: 1000 (perkelix)
   Boot ID: a200afe0e5134b8a812b05c898c8b859
Machine ID: 1063a9d1fb9df6e371ea9f94491345ed
  Hostname: geode
   Storage:
/var/lib/systemd/coredump/core.apt-get.0.a200afe0e5134b8a812b05c898c8b859.2083.163014678500.zst
   Message: Process 2083 (apt-get) of user 0 dumped core.

Stack trace of thread 2083:
#0  0xb7ae9170 frame_dummy (libstdc++.so.6 + 0x87170)

gdb terminated by signal ILL.

Martin-Éric

Processed: retitle 993162 to libgcc-s1: i386 (Geode LX): latest push to Bookwork produces multiple sig ILL

[Debian Bug Tracking System]

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

> retitle 993162 libgcc-s1: i386 (Geode LX): latest push to Bookwork produces 
> multiple sig ILL
Bug #993162 [libgcc-s1] libc6: i386 (Geode LX): latest push to Bookwork 
produces multiple sig ILL
Changed Bug title to 'libgcc-s1: i386 (Geode LX): latest push to Bookwork 
produces multiple sig ILL' from 'libc6: i386 (Geode LX): latest push to 
Bookwork produces multiple sig ILL'.
> thanks
Stopping processing here.

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

Processed (with 1 error): Re: Bug#993162: libc6: i386 (Geode LX): latest push to Bookwork produces multiple sig ILL

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 libgcc-s1
Bug #993162 [libc6] libc6: i386 (Geode LX): latest push to Bookwork produces 
multiple sig ILL
Bug reassigned from package 'libc6' to 'libgcc-s1'.
No longer marked as found in versions glibc/2.31-17.
Ignoring request to alter fixed versions of bug #993162 to the same values 
previously set
> found -1 libgcc-s1/11.2.0-3
Bug #993162 [libgcc-s1] libc6: i386 (Geode LX): latest push to Bookwork 
produces multiple sig ILL
The source libgcc-s1 and version 11.2.0-3 do not appear to match any binary 
packages
Marked as found in versions libgcc-s1/11.2.0-3.
> retitle -1: libgcc-s1: i386 (Geode LX): latest push to Bookwork produces 
> multiple sig ILL
Unknown command or malformed arguments to command.


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

Bug#993162: libc6: i386 (Geode LX): latest push to Bookwork produces multiple sig ILL

[Aurelien Jarno]

control: reassign -1 libgcc-s1
control: found -1 libgcc-s1/11.2.0-3
control: retitle -1: libgcc-s1: i386 (Geode LX): latest push to Bookwork 
produces multiple sig ILL

On 2021-08-28 11:58, Aurelien Jarno wrote:
> Hi,
> 
> On 2021-08-28 11:17, Martin-Éric Racine wrote:
> > Package: libc6
> > Version: 2.31-17
> > Severity: grave
> > Justification: renders package unusable
> > 
> > Since 2.31-17 trickled into Bookworm, a number of executables (including 
> > APT and GDB) die with sig ILL. An example:
> 
> Have you upgraded other packages at the same time? At a first glance it
> doesn't seem related to libc6.
> 
> > $ sudo coredumpctl debug 1011
> >PID: 1011 (apt-get)
> >UID: 0 (root)
> >GID: 0 (root)
> > Signal: 4 (ILL)
> >  Timestamp: Sat 2021-08-28 11:00:34 EEST (3min 22s ago)
> >   Command Line: apt-get --quiet --quiet update
> > Executable: /usr/bin/apt-get
> >  Control Group: /user.slice/user-1000.slice/session-4.scope
> >   Unit: session-4.scope
> >  Slice: user-1000.slice
> >Session: 4
> >  Owner UID: 1000 (perkelix)
> >Boot ID: 77dfa6eb16584c02b84de4e2b8feb781
> > Machine ID: 1063a9d1fb9df6e371ea9f94491345ed
> >   Hostname: geode
> >Storage: 
> > /var/lib/systemd/coredump/core.apt-get.0.77dfa6eb16584c02b84de4e2b8feb781.1011.163013763400.zst
> >Message: Process 1011 (apt-get) of user 0 dumped core.
> > 
> > Stack trace of thread 1011:
> > #0  0xb7ad2ed0 __cpu_indicator_init (libgcc_s.so.1 
> > + 0x2ed0)

I have been looking at the corresponding instruction, this is:

2ed0 <__cpu_indicator_init@GCC_4.8.0>:
2ed0:   f3 0f 1e fb endbr32

This is an Intel CET instruction, and it seems your CPU doesn't support
executing it. Anyway this shows that the problem is in libgcc-s1, I am
therefore reassigning the bug.

Regards,
Aurelien

-- 
Aurelien Jarno  GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://www.aurel32.net


signature.asc
Description: PGP signature

Bug#993169: eckit FTBFS on 32bit: error: narrowing conversion of ‘20210616123456’ from ‘long long int’ to ‘long int’

[Adrian Bunk]

Source: eckit
Version: 1.17.1-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/logs.php?pkg=eckit=1.17.1-1

...
/<>/tests/sql/test_simple_functions.cc:587:27: error: narrowing 
conversion of ‘20210616123456’ from ‘long long int’ to ‘long int’ [-Wnarrowing]
...

Processed: 981662 severity

[Debian Bug Tracking System]

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

> severity 981662 important
Bug #981662 {Done: Bastian Germann } [src:xfsprogs] 
xfsprogs-udeb depends on libinih1, not libinih1-udeb
Severity set to 'important' from 'serious'
>
End of message, stopping processing here.

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

Processed: tagging 993157

[Debian Bug Tracking System]

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

> tags 993157 + bookworm sid
Bug #993157 [src:libsdl2-mixer] libsdl2-mixer FTBFS: Error in tempfile() using 
template $srcdir/build-scripts/XX: Parent directory 
($srcdir/build-scripts/) does not exist at /usr/bin/autoreconf line 403.
Added tag(s) bookworm and sid.
> thanks
Stopping processing here.

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

Bug#993162: libc6: i386 (Geode LX): latest push to Bookwork produces multiple sig ILL

[Aurelien Jarno]

Hi,

On 2021-08-28 11:17, Martin-Éric Racine wrote:
> Package: libc6
> Version: 2.31-17
> Severity: grave
> Justification: renders package unusable
> 
> Since 2.31-17 trickled into Bookworm, a number of executables (including APT 
> and GDB) die with sig ILL. An example:

Have you upgraded other packages at the same time? At a first glance it
doesn't seem related to libc6.

> $ sudo coredumpctl debug 1011
>PID: 1011 (apt-get)
>UID: 0 (root)
>GID: 0 (root)
> Signal: 4 (ILL)
>  Timestamp: Sat 2021-08-28 11:00:34 EEST (3min 22s ago)
>   Command Line: apt-get --quiet --quiet update
> Executable: /usr/bin/apt-get
>  Control Group: /user.slice/user-1000.slice/session-4.scope
>   Unit: session-4.scope
>  Slice: user-1000.slice
>Session: 4
>  Owner UID: 1000 (perkelix)
>Boot ID: 77dfa6eb16584c02b84de4e2b8feb781
> Machine ID: 1063a9d1fb9df6e371ea9f94491345ed
>   Hostname: geode
>Storage: 
> /var/lib/systemd/coredump/core.apt-get.0.77dfa6eb16584c02b84de4e2b8feb781.1011.163013763400.zst
>Message: Process 1011 (apt-get) of user 0 dumped core.
> 
> Stack trace of thread 1011:
> #0  0xb7ad2ed0 __cpu_indicator_init (libgcc_s.so.1 + 
> 0x2ed0)
> #1  0xb7faf02c call_init (ld-linux.so.2 + 0x1102c)
> #2  0xb7faf132 call_init (ld-linux.so.2 + 0x11132)
> #3  0xb7f9f0fa _dl_start_user (ld-linux.so.2 + 0x10fa)

The SIGILL happens in __cpu_indicator_init which is provided by
libgcc-s1. Bookworm got a new upstream version of this package compared
to bullseye, so if you also upgraded it, it's more likely to be the
issue. In that case, have you tried to downgrade it?

Regards,
Aurelien

-- 
Aurelien Jarno  GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://www.aurel32.net


signature.asc
Description: PGP signature

Processed: tagging 993147

[Debian Bug Tracking System]

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

> tags 993147 + bookworm sid
Bug #993147 [src:libstatgrab] libstatgrab FTBFS: ./configure: line 7892: syntax 
error near unexpected token `ac_fn_check_decl'
Added tag(s) sid and bookworm.
> thanks
Stopping processing here.

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

Bug#993167: dont_be_a_module.patch is too dirty

[Julien Puydt]

Package: node-strip-json-comments
Version: 4.0.0-1
Severity: serious

I have to drop dont_be_a_module.patch ; it's too dirty. I'll do it
later today, but still want to prevent any migration to testing.

J.Puydt

Bug#992798: your mail

[Michael Prokop]

Hi Samuel,

* Samuel Henrique [Fri Aug 27, 2021 at 07:10:14PM +0100]:
> Thanks for providing the MR, Michael,

> There's just one thing missing so the MR can close this bugreport; it
> needs to drop the shellcheck autopkgtest.

> Would you like to amend this change to your MR?

Ah, I misunderstood the request regarding autopkgtest.
Thanks for letting me know! I just updated the MR accordingly.

regards
-mika-


signature.asc
Description: Digital signature

Bug#993166: rust-crossbeam-deque_0.7.4-1_mips64el-buildd.changes REJECTED

[Aurelien Jarno]

Source: rust-crossbeam-deque
Version: 0.7.4-1
Severity: serious

On 2021-08-28 09:03, Debian FTP Masters wrote:
> librust-crossbeam-deque-dev_0.7.4-1_mips64el.deb: has 1 file(s) with a 
> timestamp too far in the past:
>   usr/share/doc/librust-crossbeam-deque-dev/changelog.gz (Thu Nov 29 21:33:09 
> 1973)
> 
> 
> 
> ===
> 
> Please feel free to respond to this email if you don't understand why
> your files were rejected, or if you upload new files which address our
> concerns.
> 
> 
> 

Processed: tagging 993143

[Debian Bug Tracking System]

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

> tags 993143 + bookworm sid
Bug #993143 [src:kconfig-frontends] kconfig-frontends FTBFS: autoreconf: error: 
cannot create scripts/.autostuff/scripts: No such file or directory
Added tag(s) sid and bookworm.
> thanks
Stopping processing here.

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

Processed: tagging 993094

[Debian Bug Tracking System]

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

> tags 993094 + bookworm sid
Bug #993094 [src:sdl-mixer1.2] sdl-mixer1.2 FTBFS: autoreconf failure
Added tag(s) bookworm and sid.
> thanks
Stopping processing here.

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

Processed: tagging 993099

[Debian Bug Tracking System]

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

> tags 993099 + bookworm sid
Bug #993099 [src:libprelude] libprelude arch-only FTBFS: Can't exec 
"gtkdocize": No such file or directory at 
/usr/share/autoconf/Autom4te/FileUtils.pm line 293.
Added tag(s) sid and bookworm.
> thanks
Stopping processing here.

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

Processed: tagging 993084

[Debian Bug Tracking System]

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

> tags 993084 + bookworm sid
Bug #993084 [src:libopenobex] libopenobex FTBFS: build failure
Added tag(s) bookworm and sid.
> thanks
Stopping processing here.

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

Bug#993164: proftpd-core: When upgrading from Buster to Bullseyes, the installation of ProFTPd fails

[Hilmar Preuße]

Am 28.08.2021 um 10:20 teilte Andreas Guenther mit:

Hi,

Although I do speak German I prefer English error messages. ;-)

Could you provide the output of "systemctl status proftpd.service" and 
"journalctl -xe" and the /var/log/proftpd/proftpd.log?


Thanks!


This error occurred for the first time when upgrading the system from 
Buster to Bullseye:
dpkg: Fehler beim Bearbeiten des Paketes proftpd-mod-crypto (--configure):
Abhängigkeitsprobleme - verbleibt unkonfiguriert
dpkg: Abhängigkeitsprobleme verhindern Konfiguration von proftpd-mod-wrap:
proftpd-mod-wrap hängt ab von proftpd-core (= 1.3.7a+dfsg-12); aber:
Paket proftpd-core ist noch nicht konfiguriert.
.
.
Fehler traten auf beim Bearbeiten von:
 proftpd-core
 proftpd-mod-crypto
 proftpd-mod-wrap
 proftpd-basic

Then I deleted all the packages involved and tried to reinstall them with 
the same result:
 dpkg --remove proftpd-basic proftpd-core proftpd-mod-crypto 
proftpd-mod-wrap
 apt install proftpd-core proftpd-basic proftpd-mod-crypto proftpd-mod-wrap

After deleting all packages again, I only installed proftpd-core:

 apt install proftpd-core

See "systemctl status proftpd.service" and "journalctl -xe" for details.
dpkg: Fehler beim Bearbeiten des Paketes proftpd-core (--configure):
  »installiertes proftpd-core-Skript des Paketes 
post-installation«-Unterprozess gab den Fehlerwert 1 zurück
Fehler traten auf beim Bearbeiten von:
proftpd-core

The package obviously cannot be installed due to the proftpd-core script.

My expectation of you would be to make ProFTPd installable.





--
sigfault




OpenPGP_signature
Description: OpenPGP digital signature

Bug#993164: proftpd-core: When upgrading from Buster to Bullseyes, the installation of ProFTPd fails

[Andreas Guenther]

Package: proftpd-core
Version: 1.3.7a+dfsg-12
Severity: serious
Justification: 1

Dear Maintainer,

   This error occurred for the first time when upgrading the system from Buster 
to Bullseye:
   dpkg: Fehler beim Bearbeiten des Paketes proftpd-mod-crypto (--configure):
   Abhängigkeitsprobleme - verbleibt unkonfiguriert
   dpkg: Abhängigkeitsprobleme verhindern Konfiguration von proftpd-mod-wrap:
   proftpd-mod-wrap hängt ab von proftpd-core (= 1.3.7a+dfsg-12); aber:
   Paket proftpd-core ist noch nicht konfiguriert.
   .
   .
   Fehler traten auf beim Bearbeiten von:
proftpd-core
proftpd-mod-crypto
proftpd-mod-wrap
proftpd-basic

   Then I deleted all the packages involved and tried to reinstall them with 
the same result:
dpkg --remove proftpd-basic proftpd-core proftpd-mod-crypto proftpd-mod-wrap
apt install proftpd-core proftpd-basic proftpd-mod-crypto proftpd-mod-wrap
   
   After deleting all packages again, I only installed proftpd-core:
apt install proftpd-core

   See "systemctl status proftpd.service" and "journalctl -xe" for details.
   dpkg: Fehler beim Bearbeiten des Paketes proftpd-core (--configure):
 »installiertes proftpd-core-Skript des Paketes 
post-installation«-Unterprozess gab den Fehlerwert 1 zurück
   Fehler traten auf beim Bearbeiten von:
   proftpd-core
   
   The package obviously cannot be installed due to the proftpd-core script.
   
   My expectation of you would be to make ProFTPd installable.

   Best regards
   Andreas Günther


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

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

Versions of packages proftpd-core depends on:
ii  adduser  3.118
ii  debianutils  4.11.2
ii  init-system-helpers  1.60
ii  libacl1  2.2.53-10
ii  libc62.31-13
ii  libcap2  1:2.44-1
ii  libcrypt11:4.4.18-4
ii  libhiredis0.14   0.14.1-1
ii  libmemcached11   1.0.18-4.2
ii  libmemcachedutil21.0.18-4.2
ii  libncursesw6 6.2+20201114-2
ii  libpam-runtime   1.4.0-9
ii  libpam0g 1.4.0-9
ii  libpcre3 2:8.39-13
ii  libssl1.11.1.1k-1
ii  libtinfo66.2+20201114-2
ii  lsb-base 11.1.0
ii  netbase  6.3
ii  sed  4.7-1
ii  ucf  3.0043
ii  zlib1g   1:1.2.11.dfsg-2

Versions of packages proftpd-core recommends:
ii  proftpd-doc  1.3.7a+dfsg-12

Versions of packages proftpd-core suggests:
pn  openbsd-inetd | inet-superserver  
ii  openssl   1.1.1k-1
pn  proftpd-mod-crypto
pn  proftpd-mod-geoip 
pn  proftpd-mod-ldap  
pn  proftpd-mod-mysql 
pn  proftpd-mod-odbc  
pn  proftpd-mod-pgsql 
pn  proftpd-mod-snmp  
pn  proftpd-mod-sqlite
pn  proftpd-mod-wrap  

-- Configuration Files:
/etc/logrotate.d/proftpd-core changed:
/var/log/proftpd/proftpd.log 
/var/log/proftpd/controls.log 
/var/log/proftpd/tls.log
/var/log/proftpd/sftp.log
{
weekly
missingok
rotate 7
compress
delaycompress
notifempty
create 640 root adm
sharedscripts
postrotate
# reload could be not sufficient for all logs, a restart is 
safer
invoke-rc.d proftpd restart 2>/dev/null >/dev/null || true
endscript
}
/var/log/proftpd/xferlog
/var/log/proftpd/xferreport
{
monthly
missingok
rotate 7
compress
delaycompress
notifempty
create 640 root adm
sharedscripts
prerotate
endscript
postrotate
# reload could be not sufficient for all logs, a restart is 
safer
invoke-rc.d proftpd restart 2>/dev/null >/dev/null || true
# run ftpstats on past transfer log
ftpstats -a -r -l 2 -d -h -f /var/log/proftpd/xferlog.0 
2>/dev/null >/var/log/proftpd/xferreport || true
endscript
}


-- no debconf information

Bug#993162: libc6: i386 (Geode LX): latest push to Bookwork produces multiple sig ILL

[Martin-Éric Racine]

Package: libc6
Version: 2.31-17
Severity: grave
Justification: renders package unusable

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Since 2.31-17 trickled into Bookworm, a number of executables (including APT 
and GDB) die with sig ILL. An example:

$ sudo coredumpctl debug 1011
   PID: 1011 (apt-get)
   UID: 0 (root)
   GID: 0 (root)
Signal: 4 (ILL)
 Timestamp: Sat 2021-08-28 11:00:34 EEST (3min 22s ago)
  Command Line: apt-get --quiet --quiet update
Executable: /usr/bin/apt-get
 Control Group: /user.slice/user-1000.slice/session-4.scope
  Unit: session-4.scope
 Slice: user-1000.slice
   Session: 4
 Owner UID: 1000 (perkelix)
   Boot ID: 77dfa6eb16584c02b84de4e2b8feb781
Machine ID: 1063a9d1fb9df6e371ea9f94491345ed
  Hostname: geode
   Storage: 
/var/lib/systemd/coredump/core.apt-get.0.77dfa6eb16584c02b84de4e2b8feb781.1011.163013763400.zst
   Message: Process 1011 (apt-get) of user 0 dumped core.

Stack trace of thread 1011:
#0  0xb7ad2ed0 __cpu_indicator_init (libgcc_s.so.1 + 
0x2ed0)
#1  0xb7faf02c call_init (ld-linux.so.2 + 0x1102c)
#2  0xb7faf132 call_init (ld-linux.so.2 + 0x11132)
#3  0xb7f9f0fa _dl_start_user (ld-linux.so.2 + 0x10fa)

Stack trace for other executables show the same cause as above.

$ cat /proc/cpuinfo 
processor   : 0
vendor_id   : AuthenticAMD
cpu family  : 5
model   : 10
model name  : Geode(TM) Integrated Processor by AMD PCS
stepping: 2
cpu MHz : 497.996
cache size  : 128 KB
physical id : 0
siblings: 1
core id : 0
cpu cores   : 1
apicid  : 0
initial apicid  : 0
fdiv_bug: no
f00f_bug: no
coma_bug: no
fpu : yes
fpu_exception   : yes
cpuid level : 1
wp  : yes
flags   : fpu de pse tsc msr cx8 sep pge cmov clflush mmx mmxext 
3dnowext 3dnow cpuid 3dnowprefetch vmmcall
bugs: sysret_ss_attrs spectre_v1 spectre_v2 spec_store_bypass
bogomips: 995.99
clflush size: 32
cache_alignment : 32
address sizes   : 32 bits physical, 32 bits virtual
power management:

Feel free to reassign as appropriate.

Cheers!
Martin-Éric

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEyJACx3qL7GpObXOQrh+Cd8S017YFAmEp8TIACgkQrh+Cd8S0
17YLcQ/9GU6jypIgCKXTN48qzbAbDZYiGnKmsRJ7vXmmKZOLH75SWsmT++NJi+lf
SPe0JCKRhBuRVBx+0kIRZ89KaTn/L4fWXMb1UF9wLQQEkvQfj0Vbnwi5lgQuLTTw
x99Zouh9s9OtRQ+SZhQnuTts2SeiYLN9xkmCVPlK4LUSYuNfXJ60dOmmCXvgzpoQ
7BAZ43XciA5jU2+SmK506oFCVjNQWstgncRKMVj2++apdXiSZXZ1cP2RLfIpurLU
OH6Ke3iifeOgcNuhPbLfva5rrdwFIEo0mEKzNzgpzIsOzBjow2EAmLehr24iAcoy
BkxGuTdGeUtF/rOQFEwhtPi2BwAqrgqSe0BFvy8D4rfY2wM0fprAV6/1xtMRAGCX
HBo+VQPbBjcfW91sKXIBMAolJcirV1HoiKGZCjjQpPzZUSe7oTnFmVFvsSiCkfAb
gNL4MTKnN6s5F4rGDmOcIxQ2B5h/AK/au8yB6gjPpyDWjQJ3812PpHlOoFUjrQzu
Mhdr+er8oWZc8Thq9IN+tv76CeV9FLWPwNs8Fs5yVi11Tj5SCJJrNEe3IqnUBKj6
ioxg3WLAY3V+dYrFCTycZuaE+3wO9uNDmJZWFOOKeBptgiMqxgGOuoDO/IFSBLst
kslWCmTguCn7EoHFGEK4Tlv8cSNZbZaIcsdDWNNgibFPqG12I8I=
=uPzL
-END PGP SIGNATURE-

Bug#987008: Grub fails to find LVM volume after previous LV rename

[Rogier]

Additional information for the benefit of anybody who uses LVM and 
grub, and is unsure if or when this problem will affect them:

Besides the system being rendered unbootable, another symptom of this 
problem being acute is that, at that time, update-grub will most 
probably(*) print messages of the following kind, one for each LVM 
filesystem affected:

grub-probe: error: disk `lvmid/**------
**/**------**' not found.

The immediate workaround, if this problem occurs, would be to make 
another modification to the LVM configuration. Then run update-grub 
again. For verification, the following command can also be used:

grub-probe -d /dev/mapper/ -t 
fs

If the problem is acute, the error message should be printed, if it is 
not acute, then there should be no error message (no warranties :-).

Kind regards,

Rogier.


(*) but not if os-prober is disabled for update-grub.

Bug#993157: libsdl2-mixer FTBFS: Error in tempfile() using template $srcdir/build-scripts/XXXXXXXXXX: Parent directory ($srcdir/build-scripts/) does not exist at /usr/bin/autoreconf line 403.

[Helmut Grohne]

Source: libsdl2-mixer
Version: 2.0.4+dfsg1-3
Severity: serious
Tags: ftbfs

libsdl2-mixer fails to build from source in unstable. A build ends as
follows:

|debian/rules override_dh_autoreconf
| make[1]: Entering directory '/<>'
| aclocal --force --install -I /usr/share/aclocal/ -I acinclude
| aclocal: warning: autoconf input should be named 'configure.ac', not 
'configure.in'
| dh_autoreconf
| autoreconf: warning: autoconf input should be named 'configure.ac', not 
'configure.in'
| aclocal: warning: autoconf input should be named 'configure.ac', not 
'configure.in'
| autoreconf: error: cannot create $srcdir/build-scripts: No such file or 
directory
| libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, 'build-scripts'.
| libtoolize: copying file 'build-scripts/ltmain.sh'
| libtoolize: Consider adding 'AC_CONFIG_MACRO_DIRS([m4])' to configure.in,
| libtoolize: and rerunning libtoolize and aclocal.
| libtoolize: Consider adding '-I m4' to ACLOCAL_AMFLAGS in Makefile.am.
| aclocal: warning: autoconf input should be named 'configure.ac', not 
'configure.in'
| configure.in:48: warning: The macro `AC_PROG_LIBTOOL' is obsolete.
| configure.in:48: You should run autoupdate.
| aclocal.m4:113: AC_PROG_LIBTOOL is expanded from...
| configure.in:48: the top level
| configure.in:93: warning: The macro `AC_HELP_STRING' is obsolete.
| configure.in:93: You should run autoupdate.
| ./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
| configure.in:93: the top level
| configure.in:99: warning: The macro `AC_TRY_COMPILE' is obsolete.
| configure.in:99: You should run autoupdate.
| ./lib/autoconf/general.m4:2847: AC_TRY_COMPILE is expanded from...
| configure.in:99: the top level
| configure.in:153: warning: The macro `AC_TRY_COMPILE' is obsolete.
| configure.in:153: You should run autoupdate.
| ./lib/autoconf/general.m4:2847: AC_TRY_COMPILE is expanded from...
| configure.in:153: the top level
| configure.in:192: warning: The macro `AC_TRY_RUN' is obsolete.
| configure.in:192: You should run autoupdate.
| ./lib/autoconf/general.m4:2997: AC_TRY_RUN is expanded from...
| aclocal.m4:9360: AM_PATH_SDL2 is expanded from...
| configure.in:192: the top level
| configure.in:192: warning: The macro `AC_TRY_LINK' is obsolete.
| configure.in:192: You should run autoupdate.
| ./lib/autoconf/general.m4:2920: AC_TRY_LINK is expanded from...
| aclocal.m4:9360: AM_PATH_SDL2 is expanded from...
| configure.in:192: the top level
| configure.in:210: warning: The macro `AC_HELP_STRING' is obsolete.
| configure.in:210: You should run autoupdate.
| ./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
| configure.in:210: the top level
| configure.in:229: warning: The macro `AC_HELP_STRING' is obsolete.
| configure.in:229: You should run autoupdate.
| ./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
| configure.in:229: the top level
| configure.in:236: warning: The macro `AC_HELP_STRING' is obsolete.
| configure.in:236: You should run autoupdate.
| ./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
| configure.in:236: the top level
| configure.in:240: warning: The macro `AC_HELP_STRING' is obsolete.
| configure.in:240: You should run autoupdate.
| ./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
| configure.in:240: the top level
| configure.in:243: warning: The macro `AC_HELP_STRING' is obsolete.
| configure.in:243: You should run autoupdate.
| ./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
| configure.in:243: the top level
| configure.in:283: warning: The macro `AC_HELP_STRING' is obsolete.
| configure.in:283: You should run autoupdate.
| ./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
| configure.in:283: the top level
| configure.in:286: warning: The macro `AC_HELP_STRING' is obsolete.
| configure.in:286: You should run autoupdate.
| ./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
| configure.in:286: the top level
| configure.in:302: warning: The macro `AC_TRY_RUN' is obsolete.
| configure.in:302: You should run autoupdate.
| ./lib/autoconf/general.m4:2997: AC_TRY_RUN is expanded from...
| configure.in:302: the top level
| configure.in:354: warning: The macro `AC_HELP_STRING' is obsolete.
| configure.in:354: You should run autoupdate.
| ./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
| configure.in:354: the top level
| configure.in:359: warning: The macro `AC_HELP_STRING' is obsolete.
| configure.in:359: You should run autoupdate.
| ./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
| configure.in:359: the top level
| configure.in:366: warning: The macro `AC_HELP_STRING' is obsolete.
| configure.in:366: You should run autoupdate.
| ./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
| configure.in:366: the top level
| configure.in:397: warning: The macro `AC_HELP_STRING' is obsolete.
| configure.in:397: You should run autoupdate.
|