gcc-12_12.1.0-1_source.changes ACCEPTED into unstable

2022-05-08 Thread Debian FTP Masters
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 08 May 2022 15:44:36 +0200 Source: gcc-12 Architecture: source Version: 12.1.0-1 Distribution: unstable Urgency: medium Maintainer: Debian GCC Maintainers Changed-By: Matthias Klose Changes: gcc-12 (12.1.0-1)

Bug#1010728: Please provide libatomic-dev package with unversioned libatomic.so

2022-05-08 Thread Dmitry Shachnev
Package: libatomic1 Version: 12-20220428-1 Severity: wishlist Dear Maintainer, Currently we have libatomic.so.1 but no unversioned libatomic.so. The next version of Qt (6.3.1) will have this CMake code to find atomic library when there std::atomic does not work out of the box:

Processing of gcc-12_12.1.0-1_source.changes

2022-05-08 Thread Debian FTP Masters
gcc-12_12.1.0-1_source.changes uploaded successfully to localhost along with the files: gcc-12_12.1.0-1.dsc gcc-12_12.1.0.orig.tar.gz gcc-12_12.1.0-1.debian.tar.xz gcc-12_12.1.0-1_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)

Bug#968670: dwz: Fails with "Unknown DWARF DW_OP_1" (more info needed)

2022-05-08 Thread Michael Tokarev
It is the same on arm64 too, eg: https://buildd.debian.org/status/package.php?p=qemu=bullseye-backports /mjt

Bug#968670: dwz: Fails with "Unknown DWARF DW_OP_1" (more info needed)

2022-05-08 Thread Michael Tokarev
On Sat, 6 Feb 2021 08:54:57 +0100 Dennis Filder wrote: Control: tag -1 - patch + moreinfo After looking into this some more, I don't think this is necessarily a bug in dwz, but it could also be either someone using rogue DW_OP_* definitions with values 0x00 and 0x01 or a buggy