[Touch-packages] [Bug 2085147] Re: Wrong timezone detection (always UTC)
fixed in 2024b-1ubuntu2
** Changed in: tzdata (Ubuntu)
Status: New => Fix Committed
** Tags removed: block-proposed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tzdata in Ubuntu.
https://bugs.launchpad.net/bugs/2085147
Title:
Wrong timezone detection (always UTC)
Status in tzdata package in Ubuntu:
Fix Committed
Bug description:
With tzdata 2024b-1ubuntu1 (plucky-proposed), the timezone is wrongly
detected to be UTC, no matter what I do.
This is working fine with 2024a-4ubuntu1, which is what was released
in Oracular.
Simple reproducer:
```cpp
#include
#include
int main() {
const std::chrono::zoned_time cur_time{ std::chrono::current_zone(),
std::chrono::system_clock::now()
};
std::cout << cur_time << '\n';
}
```
Compiled with `g++ -std=c++20 main.cpp`
```
$ ./a.out
2024-10-21 16:14:17.489489001 UTC
$ dpkg-query -W tzdata
tzdata2024b-1ubuntu1
$ sudo apt install tzdata/oracular
[...]
$ dpkg-query -W tzdata
tzdata2024a-4ubuntu1
$ ./a.out
2024-10-21 18:16:25.554620585 CEST
```
ProblemType: Bug
DistroRelease: Ubuntu 25.04
Package: tzdata 2024b-1ubuntu1
ProcVersionSignature: Ubuntu 6.8.0-45.45-generic 6.8.12
Uname: Linux 6.8.0-45-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.30.0-0ubuntu4
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: sway
Date: Mon Oct 21 14:11:36 2024
InstallationDate: Installed on 2023-08-02 (446 days ago)
InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
PackageArchitecture: all
ProcEnviron:
LANG=fr_FR.UTF-8
PATH=(custom, no user)
SHELL=/bin/zsh
TERM=alacritty
XDG_RUNTIME_DIR=
SourcePackage: tzdata
UpgradeStatus: Upgraded to plucky on 2024-06-12 (131 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2085147/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2032532] Re: cron autopkgtest failure on armhf
apparently fixed for 25.04 ** Changed in: exim4 (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cron in Ubuntu. https://bugs.launchpad.net/bugs/2032532 Title: cron autopkgtest failure on armhf Status in cron package in Ubuntu: Fix Released Status in exim4 package in Ubuntu: Fix Released Bug description: The cron autopkgtests fail on armhf when run with exim4, blocking the latest exim4 merge's migration: https://code.launchpad.net/~bryce/ubuntu/+source/exim4/+git/exim4/+merge/448540 https://autopkgtest.ubuntu.com/packages/c/cron/mantic/armhf https://autopkgtest.ubuntu.com/results/autopkgtest-mantic/mantic/armhf/c/cron/20230821_121833_8b636@/log.gz 1824s autopkgtest [07:59:06]: test check-listings-protection: [--- 1826s +-+ 1826s | Here we are testing the patch | 1826s | features/protect-list.patch| 1826s +-+ 1826s = adding user 'dummy' = 1826s info: Adding user `dummy' ... 1826s logger: send message failed: Invalid argument 1826s info: Selecting UID/GID from range 1000 to 5 ... 1826s logger: send message failed: Invalid argument 1826s info: Adding new group `dummy' (1001) ... 1826s logger: send message failed: Invalid argument 1826s info: Adding new user `dummy' (1001) with group `dummy (1001)' ... 1826s logger: send message failed: Invalid argument 1826s info: Creating home directory `/home/dummy' ... 1826s logger: send message failed: Invalid argument 1826s info: Copying files from `/etc/skel' ... 1826s logger: send message failed: Invalid argument 1826s info: Adding new user `dummy' to supplemental / extra groups `users' ... 1826s logger: send message failed: Invalid argument 1826s info: Adding user `dummy' to group `users' ... 1826s logger: send message failed: Invalid argument 1826s = Inject an obfuscated line into dummy's crontab == 1827s == testing the crontab of user 'dummy' = 1827s = here is a hexa dump of $(crontab -u dummy -l) 1827s 2a 20 2a 20 2a 20 2a 20 2a 20 3e 2f 74 6d 70 2f |* * * * * >/tmp/| 1827s 0010 78 3b 0d 6e 6f 20 63 72 6f 6e 74 61 62 20 66 6f |x;.no crontab fo| 1827s 0020 72 20 64 75 6d 6d 79 08 08 62 6f 0a |r dummy..bo.| 1827s 002c 1827s +-+ 1827s | Good! characters and were protected | 1827s +-+ 1827s autopkgtest [07:59:09]: test check-listings-protection: ---] 1831s check-listings-protection FAIL stderr: logger: send message failed: Invalid argument 1831s autopkgtest [07:59:13]: test check-listings-protection: - - - - - - - - - - stderr - - - - - - - - - - 1831s logger: send message failed: Invalid argument 1831s logger: send message failed: Invalid argument 1831s logger: send message failed: Invalid argument 1831s logger: send message failed: Invalid argument 1831s logger: send message failed: Invalid argument 1831s logger: send message failed: Invalid argument 1831s logger: send message failed: Invalid argument To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cron/+bug/2032532/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2032532] Re: cron autopkgtest failure on armhf
apparently fixed for 25.04 ** Changed in: cron (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cron in Ubuntu. https://bugs.launchpad.net/bugs/2032532 Title: cron autopkgtest failure on armhf Status in cron package in Ubuntu: Fix Released Status in exim4 package in Ubuntu: Fix Released Bug description: The cron autopkgtests fail on armhf when run with exim4, blocking the latest exim4 merge's migration: https://code.launchpad.net/~bryce/ubuntu/+source/exim4/+git/exim4/+merge/448540 https://autopkgtest.ubuntu.com/packages/c/cron/mantic/armhf https://autopkgtest.ubuntu.com/results/autopkgtest-mantic/mantic/armhf/c/cron/20230821_121833_8b636@/log.gz 1824s autopkgtest [07:59:06]: test check-listings-protection: [--- 1826s +-+ 1826s | Here we are testing the patch | 1826s | features/protect-list.patch| 1826s +-+ 1826s = adding user 'dummy' = 1826s info: Adding user `dummy' ... 1826s logger: send message failed: Invalid argument 1826s info: Selecting UID/GID from range 1000 to 5 ... 1826s logger: send message failed: Invalid argument 1826s info: Adding new group `dummy' (1001) ... 1826s logger: send message failed: Invalid argument 1826s info: Adding new user `dummy' (1001) with group `dummy (1001)' ... 1826s logger: send message failed: Invalid argument 1826s info: Creating home directory `/home/dummy' ... 1826s logger: send message failed: Invalid argument 1826s info: Copying files from `/etc/skel' ... 1826s logger: send message failed: Invalid argument 1826s info: Adding new user `dummy' to supplemental / extra groups `users' ... 1826s logger: send message failed: Invalid argument 1826s info: Adding user `dummy' to group `users' ... 1826s logger: send message failed: Invalid argument 1826s = Inject an obfuscated line into dummy's crontab == 1827s == testing the crontab of user 'dummy' = 1827s = here is a hexa dump of $(crontab -u dummy -l) 1827s 2a 20 2a 20 2a 20 2a 20 2a 20 3e 2f 74 6d 70 2f |* * * * * >/tmp/| 1827s 0010 78 3b 0d 6e 6f 20 63 72 6f 6e 74 61 62 20 66 6f |x;.no crontab fo| 1827s 0020 72 20 64 75 6d 6d 79 08 08 62 6f 0a |r dummy..bo.| 1827s 002c 1827s +-+ 1827s | Good! characters and were protected | 1827s +-+ 1827s autopkgtest [07:59:09]: test check-listings-protection: ---] 1831s check-listings-protection FAIL stderr: logger: send message failed: Invalid argument 1831s autopkgtest [07:59:13]: test check-listings-protection: - - - - - - - - - - stderr - - - - - - - - - - 1831s logger: send message failed: Invalid argument 1831s logger: send message failed: Invalid argument 1831s logger: send message failed: Invalid argument 1831s logger: send message failed: Invalid argument 1831s logger: send message failed: Invalid argument 1831s logger: send message failed: Invalid argument 1831s logger: send message failed: Invalid argument To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cron/+bug/2032532/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2084923] Re: Upload for Plucky has wrong strings
** Tags removed: block-proposed ** Changed in: base-files (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/2084923 Title: Upload for Plucky has wrong strings Status in base-files package in Ubuntu: Fix Committed Bug description: Just blocking the migration: https://launchpad.net/ubuntu/+source/base-files/13.5ubuntu1 os-release, issue, etc should say something like "Ubuntu Plucky Puffin (development branch)", not directly the version number. Looking at the diff for the Oracular release gives a hint: http://launchpadlibrarian.net/753020717/base-files_13.3ubuntu5_13.3ubuntu6.diff.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/2084923/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2083480] Re: SRU: no-change rebuild to pick up changed build flags on ppc64el and s390x
bind9 uploaded 2024-10-04 ** Changed in: bind9 (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to krb5 in Ubuntu. https://bugs.launchpad.net/bugs/2083480 Title: SRU: no-change rebuild to pick up changed build flags on ppc64el and s390x Status in acl package in Ubuntu: New Status in apache2 package in Ubuntu: New Status in attr package in Ubuntu: New Status in audit package in Ubuntu: New Status in bind9 package in Ubuntu: Invalid Status in boost1.83 package in Ubuntu: New Status in ceph package in Ubuntu: Invalid Status in chrony package in Ubuntu: New Status in e2fsprogs package in Ubuntu: Invalid Status in eigen3 package in Ubuntu: New Status in elfutils package in Ubuntu: New Status in expat package in Ubuntu: Invalid Status in gmp package in Ubuntu: New Status in haproxy package in Ubuntu: New Status in isc-kea package in Ubuntu: New Status in isl package in Ubuntu: New Status in kmod package in Ubuntu: New Status in krb5 package in Ubuntu: New Status in libaio package in Ubuntu: New Status in libbsd package in Ubuntu: New Status in libcap2 package in Ubuntu: New Status in libgpg-error package in Ubuntu: New Status in libidn2 package in Ubuntu: New Status in libmd package in Ubuntu: New Status in libnl3 package in Ubuntu: New Status in libselinux package in Ubuntu: New Status in libunistring package in Ubuntu: New Status in libunwind package in Ubuntu: New Status in libvirt package in Ubuntu: Invalid Status in libzpc package in Ubuntu: New Status in mpclib3 package in Ubuntu: New Status in mpfr4 package in Ubuntu: New Status in nfs-utils package in Ubuntu: New Status in nghttp2 package in Ubuntu: New Status in openjdk-21 package in Ubuntu: Invalid Status in openldap package in Ubuntu: New Status in openvswitch package in Ubuntu: New Status in pcre2 package in Ubuntu: New Status in perl package in Ubuntu: New Status in php8.3 package in Ubuntu: Invalid Status in rabbitmq-server package in Ubuntu: Invalid Status in ruby3.2 package in Ubuntu: New Status in sqlite3 package in Ubuntu: New Status in vsftpd package in Ubuntu: New Bug description: SRU: no-change rebuild to pick up changed build flags on ppc64el and s390x This is batch of packages that we want to rebuild to pick up the changed build flags on ppc64el (LP: #2064539) and s390x (LP: #2064538). Impact: These are no change uploads on architectures other than ppc64el and s390x. All of those packages already built successful in oracular with the changed build flags. We will validate picking up the changed build flags by inspecting the log files on ppc64el and s390x. The packages are now all built, and passing autopkg tests (the failing software-properties test is unrelated). Packages already rebuilt in noble-updates: e2fsprogs expat libvirt php8.3 rabbitmq-server Packages, that are not yet ready: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/acl/+bug/2083480/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2083480] Re: SRU: no-change rebuild to pick up changed build flags on ppc64el and s390x
ceph already uploaded. we need the boost1.83 rebuild to promote the one boost binary package ** Changed in: ceph (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to krb5 in Ubuntu. https://bugs.launchpad.net/bugs/2083480 Title: SRU: no-change rebuild to pick up changed build flags on ppc64el and s390x Status in acl package in Ubuntu: New Status in apache2 package in Ubuntu: New Status in attr package in Ubuntu: New Status in audit package in Ubuntu: New Status in bind9 package in Ubuntu: Invalid Status in boost1.83 package in Ubuntu: New Status in ceph package in Ubuntu: Invalid Status in chrony package in Ubuntu: New Status in e2fsprogs package in Ubuntu: Invalid Status in eigen3 package in Ubuntu: New Status in elfutils package in Ubuntu: New Status in expat package in Ubuntu: Invalid Status in gmp package in Ubuntu: New Status in haproxy package in Ubuntu: New Status in isc-kea package in Ubuntu: New Status in isl package in Ubuntu: New Status in kmod package in Ubuntu: New Status in krb5 package in Ubuntu: New Status in libaio package in Ubuntu: New Status in libbsd package in Ubuntu: New Status in libcap2 package in Ubuntu: New Status in libgpg-error package in Ubuntu: New Status in libidn2 package in Ubuntu: New Status in libmd package in Ubuntu: New Status in libnl3 package in Ubuntu: New Status in libselinux package in Ubuntu: New Status in libunistring package in Ubuntu: New Status in libunwind package in Ubuntu: New Status in libvirt package in Ubuntu: Invalid Status in libzpc package in Ubuntu: New Status in mpclib3 package in Ubuntu: New Status in mpfr4 package in Ubuntu: New Status in nfs-utils package in Ubuntu: New Status in nghttp2 package in Ubuntu: New Status in openjdk-21 package in Ubuntu: Invalid Status in openldap package in Ubuntu: New Status in openvswitch package in Ubuntu: New Status in pcre2 package in Ubuntu: New Status in perl package in Ubuntu: New Status in php8.3 package in Ubuntu: Invalid Status in rabbitmq-server package in Ubuntu: Invalid Status in ruby3.2 package in Ubuntu: New Status in sqlite3 package in Ubuntu: New Status in vsftpd package in Ubuntu: New Bug description: SRU: no-change rebuild to pick up changed build flags on ppc64el and s390x This is batch of packages that we want to rebuild to pick up the changed build flags on ppc64el (LP: #2064539) and s390x (LP: #2064538). Impact: These are no change uploads on architectures other than ppc64el and s390x. All of those packages already built successful in oracular with the changed build flags. We will validate picking up the changed build flags by inspecting the log files on ppc64el and s390x. The packages are now all built, and passing autopkg tests (the failing software-properties test is unrelated). Packages already rebuilt in noble-updates: e2fsprogs expat libvirt php8.3 rabbitmq-server Packages, that are not yet ready: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/acl/+bug/2083480/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2076024] Re: SRU: build with -fno-omit-frame-pointer
the autopkg test regression is not caused by binutils, but by the newer gcc 13.3.0 version. This is reported in LP: #2081797, and needs an adjustment in the kernel packages. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/2076024 Title: SRU: build with -fno-omit-frame-pointer Status in binutils package in Ubuntu: New Status in binutils source package in Noble: Fix Committed Bug description: SRU: * SRU: LP: #2076024: Build with -fno-omit-frame-pointer. * Build loong64 packages on arm64 and ppc64el. * ld.bfd, ld.gold: When no package-metadata option is given, fall-back to the envvar ELF_PACKAGE_METADATA. The first one enables the -fno-omit-frame-pointer flag on the architectures where it is the default. The second one just builds packages which are already built on other architectures on two more architectues. The third patch is a no-op, because ELF_PACKAGE_DATA is not set by default anywhere in noble. It gets used by the cross compiler packages to set the correct package name. Without it, cross compiler packages would look like being built from the gcc-N packages, not the gcc-N-cross packages. These changes were part of a test rebuild of the main component on all architectures, with results at https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20240912-noble-tc-noble.html https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20240912-noble-noble.html The first one is built with all proposed changes to the binutils, GCC, LLVM and Python packages, the second one is a reference test rebuild with unmodified release and updates pockets. Comparing these, we find one progression, and some regressions. - urwid, progression. builds with the updated packages, fails in the noble archive. Not further investigated. - linux-* (11 packages). This is LP: #2081797, a configuration issue based on a GCC version. The fixed compiler already is in the noble release, but still identifies as 13.2.0. The kernel team is aware of that, and makes the fix of the next upload. A test build with the fix worked fine, and survived a reboot on an amd64 laptop. - gcc-14 fails in the archive, but is part of the planned updates. This is caused by some gnat 64bit time_t fixes. - bpftrace is a build failure seen with the LLVM 18.1.8 update, however caused by some underlinking in bpftrace. The proposed fix should be SRU'd together with the LLVM update. - There are some Python related failures, which still need to be investigated. These have to be addressed before the Python SRUs (doing that later than the binutils, GCC and LLVM updates). These are heat, pydantic, python-oslo-config, python-xmlschema and walinuxagent The packages proposed as SRUs don't show regressions in their testsuites which are run during the builds. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/2076024/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2076024] Re: SRU: build with -fno-omit-frame-pointer
checked the build logs that the flags are passed ** Tags removed: verification-needed verification-needed-noble ** Tags added: verification-done verification-done-noble -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/2076024 Title: SRU: build with -fno-omit-frame-pointer Status in binutils package in Ubuntu: New Status in binutils source package in Noble: Fix Committed Bug description: SRU: * SRU: LP: #2076024: Build with -fno-omit-frame-pointer. * Build loong64 packages on arm64 and ppc64el. * ld.bfd, ld.gold: When no package-metadata option is given, fall-back to the envvar ELF_PACKAGE_METADATA. The first one enables the -fno-omit-frame-pointer flag on the architectures where it is the default. The second one just builds packages which are already built on other architectures on two more architectues. The third patch is a no-op, because ELF_PACKAGE_DATA is not set by default anywhere in noble. It gets used by the cross compiler packages to set the correct package name. Without it, cross compiler packages would look like being built from the gcc-N packages, not the gcc-N-cross packages. These changes were part of a test rebuild of the main component on all architectures, with results at https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20240912-noble-tc-noble.html https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20240912-noble-noble.html The first one is built with all proposed changes to the binutils, GCC, LLVM and Python packages, the second one is a reference test rebuild with unmodified release and updates pockets. Comparing these, we find one progression, and some regressions. - urwid, progression. builds with the updated packages, fails in the noble archive. Not further investigated. - linux-* (11 packages). This is LP: #2081797, a configuration issue based on a GCC version. The fixed compiler already is in the noble release, but still identifies as 13.2.0. The kernel team is aware of that, and makes the fix of the next upload. A test build with the fix worked fine, and survived a reboot on an amd64 laptop. - gcc-14 fails in the archive, but is part of the planned updates. This is caused by some gnat 64bit time_t fixes. - bpftrace is a build failure seen with the LLVM 18.1.8 update, however caused by some underlinking in bpftrace. The proposed fix should be SRU'd together with the LLVM update. - There are some Python related failures, which still need to be investigated. These have to be addressed before the Python SRUs (doing that later than the binutils, GCC and LLVM updates). These are heat, pydantic, python-oslo-config, python-xmlschema and walinuxagent The packages proposed as SRUs don't show regressions in their testsuites which are run during the builds. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/2076024/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2083480] Re: SRU: no-change rebuild to pick up changed build flags on ppc64el and s390x
openjdk-21 will be addressed with the 2024.10 security updates ** Description changed: SRU: no-change rebuild to pick up changed build flags on ppc64el and s390x This is batch of packages that we want to rebuild to pick up the changed build flags on ppc64el (LP: #2064539) and s390x (LP: #2064538). Impact: These are no change uploads on architectures other than ppc64el and s390x. All of those packages already built successful in oracular with the changed build flags. We will validate picking up the changed build flags by inspecting the log files on ppc64el and s390x. The packages are now all built, and passing autopkg tests (the failing software-properties test is unrelated). + Packages already rebuilt in noble-updates: + e2fsprogs expat libvirt php8.3 rabbitmq-server + Packages, that are not yet ready: ** Changed in: e2fsprogs (Ubuntu) Status: New => Invalid ** Changed in: expat (Ubuntu) Status: New => Invalid ** Changed in: libvirt (Ubuntu) Status: New => Invalid ** Changed in: php8.3 (Ubuntu) Status: New => Invalid ** Changed in: rabbitmq-server (Ubuntu) Status: New => Invalid ** Changed in: openjdk-21 (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to krb5 in Ubuntu. https://bugs.launchpad.net/bugs/2083480 Title: SRU: no-change rebuild to pick up changed build flags on ppc64el and s390x Status in acl package in Ubuntu: New Status in apache2 package in Ubuntu: New Status in attr package in Ubuntu: New Status in audit package in Ubuntu: New Status in bind9 package in Ubuntu: New Status in boost1.83 package in Ubuntu: New Status in ceph package in Ubuntu: New Status in chrony package in Ubuntu: New Status in e2fsprogs package in Ubuntu: Invalid Status in eigen3 package in Ubuntu: New Status in elfutils package in Ubuntu: New Status in expat package in Ubuntu: Invalid Status in gmp package in Ubuntu: New Status in haproxy package in Ubuntu: New Status in isc-kea package in Ubuntu: New Status in isl package in Ubuntu: New Status in kmod package in Ubuntu: New Status in krb5 package in Ubuntu: New Status in libaio package in Ubuntu: New Status in libbsd package in Ubuntu: New Status in libcap2 package in Ubuntu: New Status in libgpg-error package in Ubuntu: New Status in libidn2 package in Ubuntu: New Status in libmd package in Ubuntu: New Status in libnl3 package in Ubuntu: New Status in libselinux package in Ubuntu: New Status in libunistring package in Ubuntu: New Status in libunwind package in Ubuntu: New Status in libvirt package in Ubuntu: Invalid Status in libzpc package in Ubuntu: New Status in mpclib3 package in Ubuntu: New Status in mpfr4 package in Ubuntu: New Status in nfs-utils package in Ubuntu: New Status in nghttp2 package in Ubuntu: New Status in openjdk-21 package in Ubuntu: Invalid Status in openldap package in Ubuntu: New Status in openvswitch package in Ubuntu: New Status in pcre2 package in Ubuntu: New Status in perl package in Ubuntu: New Status in php8.3 package in Ubuntu: Invalid Status in rabbitmq-server package in Ubuntu: Invalid Status in ruby3.2 package in Ubuntu: New Status in sqlite3 package in Ubuntu: New Status in vsftpd package in Ubuntu: New Bug description: SRU: no-change rebuild to pick up changed build flags on ppc64el and s390x This is batch of packages that we want to rebuild to pick up the changed build flags on ppc64el (LP: #2064539) and s390x (LP: #2064538). Impact: These are no change uploads on architectures other than ppc64el and s390x. All of those packages already built successful in oracular with the changed build flags. We will validate picking up the changed build flags by inspecting the log files on ppc64el and s390x. The packages are now all built, and passing autopkg tests (the failing software-properties test is unrelated). Packages already rebuilt in noble-updates: e2fsprogs expat libvirt php8.3 rabbitmq-server Packages, that are not yet ready: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/acl/+bug/2083480/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2083480] [NEW] SRU: no-change rebuild to pick up changed build flags on ppc64el and s390x
Public bug reported: SRU: no-change rebuild to pick up changed build flags on ppc64el and s390x This is batch of packages that we want to rebuild to pick up the changed build flags on ppc64el (LP: #2064539) and s390x (LP: #2064538). Impact: These are no change uploads on architectures other than ppc64el and s390x. All of those packages already built successful in oracular with the changed build flags. We will validate picking up the changed build flags by inspecting the log files on ppc64el and s390x. The packages are now all built, and passing autopkg tests (the failing software-properties test is unrelated). Packages, that are not yet ready: ** Affects: acl (Ubuntu) Importance: Undecided Status: New ** Affects: apache2 (Ubuntu) Importance: Undecided Status: New ** Affects: attr (Ubuntu) Importance: Undecided Status: New ** Affects: audit (Ubuntu) Importance: Undecided Status: New ** Affects: bind9 (Ubuntu) Importance: Undecided Status: New ** Affects: boost1.83 (Ubuntu) Importance: Undecided Status: New ** Affects: ceph (Ubuntu) Importance: Undecided Status: New ** Affects: chrony (Ubuntu) Importance: Undecided Status: New ** Affects: e2fsprogs (Ubuntu) Importance: Undecided Status: New ** Affects: eigen3 (Ubuntu) Importance: Undecided Status: New ** Affects: elfutils (Ubuntu) Importance: Undecided Status: New ** Affects: expat (Ubuntu) Importance: Undecided Status: New ** Affects: gmp (Ubuntu) Importance: Undecided Status: New ** Affects: haproxy (Ubuntu) Importance: Undecided Status: New ** Affects: isc-kea (Ubuntu) Importance: Undecided Status: New ** Affects: isl (Ubuntu) Importance: Undecided Status: New ** Affects: kmod (Ubuntu) Importance: Undecided Status: New ** Affects: krb5 (Ubuntu) Importance: Undecided Status: New ** Affects: libaio (Ubuntu) Importance: Undecided Status: New ** Affects: libbsd (Ubuntu) Importance: Undecided Status: New ** Affects: libcap2 (Ubuntu) Importance: Undecided Status: New ** Affects: libgpg-error (Ubuntu) Importance: Undecided Status: New ** Affects: libidn2 (Ubuntu) Importance: Undecided Status: New ** Affects: libmd (Ubuntu) Importance: Undecided Status: New ** Affects: libnl3 (Ubuntu) Importance: Undecided Status: New ** Affects: libselinux (Ubuntu) Importance: Undecided Status: New ** Affects: libunistring (Ubuntu) Importance: Undecided Status: New ** Affects: libunwind (Ubuntu) Importance: Undecided Status: New ** Affects: libvirt (Ubuntu) Importance: Undecided Status: New ** Affects: libzpc (Ubuntu) Importance: Undecided Status: New ** Affects: mpclib3 (Ubuntu) Importance: Undecided Status: New ** Affects: mpfr4 (Ubuntu) Importance: Undecided Status: New ** Affects: nfs-utils (Ubuntu) Importance: Undecided Status: New ** Affects: nghttp2 (Ubuntu) Importance: Undecided Status: New ** Affects: openjdk-21 (Ubuntu) Importance: Undecided Status: New ** Affects: openldap (Ubuntu) Importance: Undecided Status: New ** Affects: openvswitch (Ubuntu) Importance: Undecided Status: New ** Affects: pcre2 (Ubuntu) Importance: Undecided Status: New ** Affects: perl (Ubuntu) Importance: Undecided Status: New ** Affects: php8.3 (Ubuntu) Importance: Undecided Status: New ** Affects: rabbitmq-server (Ubuntu) Importance: Undecided Status: New ** Affects: ruby3.2 (Ubuntu) Importance: Undecided Status: New ** Affects: sqlite3 (Ubuntu) Importance: Undecided Status: New ** Affects: vsftpd (Ubuntu) Importance: Undecided Status: New ** Also affects: acl (Ubuntu) Importance: Undecided Status: New ** Also affects: apache2 (Ubuntu) Importance: Undecided Status: New ** Also affects: audit (Ubuntu) Importance: Undecided Status: New ** Also affects: bind9 (Ubuntu) Importance: Undecided Status: New ** Also affects: boost1.83 (Ubuntu) Importance: Undecided Status: New ** Also affects: ceph (Ubuntu) Importance: Undecided Status: New ** Also affects: chrony (Ubuntu) Importance: Undecided Status: New ** Also affects: e2fsprogs (Ubuntu) Importance: Undecided Status: New ** Also affects: eigen3 (Ubuntu) Importance: Undecided Status: New ** Also affects: elfutils (Ubuntu) Importance: Undecided Status: New ** Also affects: expat (Ubuntu) Importance: Undecided Status: New ** Also affects: gmp (Ubuntu) Importance: Undecided
[Touch-packages] [Bug 2073363] Re: SRU: backport the final gdb 15.1 release to 24.04 LTS
** Description changed: SRU: backport the final gdb 15.1 release to 24.04 LTS, including the changes from 20240403 up to the release 20240707. - The updated gdb will be part of a test rebuild of 24.04 LTS main on all - architectures. + A test rebuild using these packages was done as described in LP: + #2076024. + + The gdb testsuite run during the build doesn't show regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdb in Ubuntu. https://bugs.launchpad.net/bugs/2073363 Title: SRU: backport the final gdb 15.1 release to 24.04 LTS Status in gdb package in Ubuntu: New Bug description: SRU: backport the final gdb 15.1 release to 24.04 LTS, including the changes from 20240403 up to the release 20240707. A test rebuild using these packages was done as described in LP: #2076024. The gdb testsuite run during the build doesn't show regressions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/2073363/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2076024] Re: SRU: build with -fno-omit-frame-pointer
** Description changed: - SRU: build with -fno-omit-frame-pointer, if it's enabled in dpkg- - buildflags. + SRU: + + * SRU: LP: #2076024: Build with -fno-omit-frame-pointer. + * Build loong64 packages on arm64 and ppc64el. + * ld.bfd, ld.gold: When no package-metadata option is given, fall-back + to the envvar ELF_PACKAGE_METADATA. + + The first one enables the -fno-omit-frame-pointer flag on the + architectures where it is the default. + + The second one just builds packages which are already built on other + architectures on two more architectues. + + The third patch is a no-op, because ELF_PACKAGE_DATA is not set by + default anywhere in noble. It gets used by the cross compiler packages + to set the correct package name. Without it, cross compiler packages + would look like being built from the gcc-N packages, not the gcc-N-cross + packages. + + These changes were part of a test rebuild of the main component on all architectures, with results at + https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20240912-noble-tc-noble.html + https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20240912-noble-noble.html + + The first one is built with all proposed changes to the binutils, GCC, + LLVM and Python packages, the second one is a reference test rebuild + with unmodified release and updates pockets. + + Comparing these, we find one progression, and some regressions. + + - urwid, progression. builds with the updated packages, fails in the noble + archive. Not further investigated. + + - linux-* (11 packages). This is LP: #2081797, a configuration issue based + on a GCC version. The fixed compiler already is in the noble release, but + still identifies as 13.2.0. The kernel team is aware of that, and makes + the fix of the next upload. + A test build with the fix worked fine, and survived a reboot on an amd64 + laptop. + + - gcc-14 fails in the archive, but is part of the planned updates. This is + caused by some gnat 64bit time_t fixes. + + - bpftrace is a build failure seen with the LLVM 18.1.8 update, however caused + by some underlinking in bpftrace. The proposed fix should be SRU'd together + with the LLVM update. + + - There are some Python related failures, which still need to be investigated. + These have to be addressed before the Python SRUs (doing that later than + the binutils, GCC and LLVM updates). These are heat, pydantic, + python-oslo-config, python-xmlschema and walinuxagent + + The packages proposed as SRUs don't show regressions in their testsuites + which are run during the builds. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/2076024 Title: SRU: build with -fno-omit-frame-pointer Status in binutils package in Ubuntu: New Bug description: SRU: * SRU: LP: #2076024: Build with -fno-omit-frame-pointer. * Build loong64 packages on arm64 and ppc64el. * ld.bfd, ld.gold: When no package-metadata option is given, fall-back to the envvar ELF_PACKAGE_METADATA. The first one enables the -fno-omit-frame-pointer flag on the architectures where it is the default. The second one just builds packages which are already built on other architectures on two more architectues. The third patch is a no-op, because ELF_PACKAGE_DATA is not set by default anywhere in noble. It gets used by the cross compiler packages to set the correct package name. Without it, cross compiler packages would look like being built from the gcc-N packages, not the gcc-N-cross packages. These changes were part of a test rebuild of the main component on all architectures, with results at https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20240912-noble-tc-noble.html https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20240912-noble-noble.html The first one is built with all proposed changes to the binutils, GCC, LLVM and Python packages, the second one is a reference test rebuild with unmodified release and updates pockets. Comparing these, we find one progression, and some regressions. - urwid, progression. builds with the updated packages, fails in the noble archive. Not further investigated. - linux-* (11 packages). This is LP: #2081797, a configuration issue based on a GCC version. The fixed compiler already is in the noble release, but still identifies as 13.2.0. The kernel team is aware of that, and makes the fix of the next upload. A test build with the fix worked fine, and survived a reboot on an amd64 laptop. - gcc-14 fails in the archive, but is part of the planned updates. This is caused by some gnat 64bit time_t fixes. - bpftrace is a build failure seen with the LLVM 18.1.8 update, however caused by some underlinking in bpftrace. The proposed fix should be SRU'd together with the LLVM
[Touch-packages] [Bug 2077940] [NEW] setuptools v72 removed the test command
Public bug reported: the autopkg tests fail with setuptools v72: v72.0.0 === Deprecations and Removals - - The test command has been removed. Users relying on 'setup.py test' will need to migrate to another test runner or pin setuptools before this version. (#931) [...] 121s autopkgtest [16:15:43]: test run-tests: [--- 121s MESA: error: ZINK: vkCreateInstance failed (VK_ERROR_INCOMPATIBLE_DRIVER) 121s glx: failed to create drisw screen 121s 121s (setup.py:4590): dbind-WARNING **: 16:15:43.530: AT-SPI: Error retrieving accessibility bus address: org.freedesktop.DBus.Error.ServiceUnknown: The name org.a11y.Bus was not provided by any .service files 121s ERROR: Python module Queue not found 121s ERROR: Python module urllib2 not found 122s ERROR: Python module Queue not found 122s ERROR: Python module ConfigParser not found 122s /usr/lib/python3/dist-packages/setuptools/_distutils/dist.py:268: UserWarning: Unknown distribution option: 'test_suite' 122s warnings.warn(msg) 122s usage: setup.py [global_opts] cmd1 [cmd1_opts] [cmd2 [cmd2_opts] ...] 122sor: setup.py --help [cmd1 cmd2 ...] 122sor: setup.py --help-commands 122sor: setup.py cmd --help 122s 122s error: invalid command 'test' ** Affects: software-properties (Ubuntu) Importance: High Status: Confirmed ** Tags: rls-oo-incoming ** Changed in: software-properties (Ubuntu) Status: New => Confirmed ** Changed in: software-properties (Ubuntu) Importance: Undecided => High ** Tags added: rls-oo-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/2077940 Title: setuptools v72 removed the test command Status in software-properties package in Ubuntu: Confirmed Bug description: the autopkg tests fail with setuptools v72: v72.0.0 === Deprecations and Removals - - The test command has been removed. Users relying on 'setup.py test' will need to migrate to another test runner or pin setuptools before this version. (#931) [...] 121s autopkgtest [16:15:43]: test run-tests: [--- 121s MESA: error: ZINK: vkCreateInstance failed (VK_ERROR_INCOMPATIBLE_DRIVER) 121s glx: failed to create drisw screen 121s 121s (setup.py:4590): dbind-WARNING **: 16:15:43.530: AT-SPI: Error retrieving accessibility bus address: org.freedesktop.DBus.Error.ServiceUnknown: The name org.a11y.Bus was not provided by any .service files 121s ERROR: Python module Queue not found 121s ERROR: Python module urllib2 not found 122s ERROR: Python module Queue not found 122s ERROR: Python module ConfigParser not found 122s /usr/lib/python3/dist-packages/setuptools/_distutils/dist.py:268: UserWarning: Unknown distribution option: 'test_suite' 122s warnings.warn(msg) 122s usage: setup.py [global_opts] cmd1 [cmd1_opts] [cmd2 [cmd2_opts] ...] 122sor: setup.py --help [cmd1 cmd2 ...] 122sor: setup.py --help-commands 122sor: setup.py cmd --help 122s 122s error: invalid command 'test' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2077940/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2076340] Re: SRU: no-change rebuild to pick up changed build flags on ppc64el and s390x
The packages are now all built, and passing autopkg tests (the failing software-properties test is unrelated). Packages, that are not yet ready: - atlas (ftbfs) - s390-tools, s390-tools-signed (not yet uploaded) - postgresql-16 (superseded by security upload, new upload in the unapproved queue) ** Description changed: SRU: no-change rebuild to pick up changed build flags on ppc64el and s390x This is batch of packages that we want to rebuild to pick up the changed build flags on ppc64el (LP: #2064539) and s390x (LP: #2064538). Impact: These are no change uploads on architectures other than ppc64el and s390x. All of those packages already built successful in oracular with the changed build flags. We will validate picking up the changed build flags by inspecting the log files on ppc64el and s390x. - Packages with all passing autopkg tests: - lapack golang-1.22 dotnet8 docker.io-app cyrus-sasl2 containerd-app rustc runc-app python-greenlet powerpc-utils p11-kit libzdnn libdeflate + The packages are now all built, and passing autopkg tests (the failing + software-properties test is unrelated). + + Packages, that are not yet ready: + + - atlas (ftbfs) + - s390-tools, s390-tools-signed (not yet uploaded) + - postgresql-16 (superseded by security upload, new upload in the unapproved queue) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bzip2 in Ubuntu. https://bugs.launchpad.net/bugs/2076340 Title: SRU: no-change rebuild to pick up changed build flags on ppc64el and s390x Status in atlas package in Ubuntu: New Status in bzip2 package in Ubuntu: Fix Released Status in containerd-app package in Ubuntu: New Status in curl package in Ubuntu: New Status in cyrus-sasl2 package in Ubuntu: New Status in dbus package in Ubuntu: Fix Released Status in docker.io-app package in Ubuntu: New Status in dotnet8 package in Ubuntu: New Status in gnutls28 package in Ubuntu: New Status in golang-1.22 package in Ubuntu: New Status in icu package in Ubuntu: Fix Released Status in lapack package in Ubuntu: Fix Released Status in libdeflate package in Ubuntu: New Status in libseccomp package in Ubuntu: Fix Released Status in libzdnn package in Ubuntu: Fix Released Status in libzstd package in Ubuntu: New Status in lz4 package in Ubuntu: New Status in mysql-8.0 package in Ubuntu: New Status in nettle package in Ubuntu: New Status in openssh package in Ubuntu: New Status in openssl package in Ubuntu: New Status in p11-kit package in Ubuntu: New Status in postgresql-16 package in Ubuntu: New Status in postgresql-common package in Ubuntu: New Status in powerpc-utils package in Ubuntu: Fix Released Status in python-greenlet package in Ubuntu: Fix Released Status in qemu package in Ubuntu: New Status in runc-app package in Ubuntu: Fix Released Status in rustc package in Ubuntu: New Status in s390-tools package in Ubuntu: New Status in s390-tools-signed package in Ubuntu: New Status in systemd package in Ubuntu: New Status in util-linux package in Ubuntu: New Status in xz-utils package in Ubuntu: New Status in zlib package in Ubuntu: New Status in atlas source package in Noble: Fix Committed Status in bzip2 source package in Noble: Fix Committed Status in containerd-app source package in Noble: Fix Committed Status in curl source package in Noble: Fix Committed Status in cyrus-sasl2 source package in Noble: Fix Committed Status in dbus source package in Noble: Fix Committed Status in docker.io-app source package in Noble: Fix Committed Status in dotnet8 source package in Noble: Fix Committed Status in gnutls28 source package in Noble: Fix Committed Status in golang-1.22 source package in Noble: Fix Committed Status in icu source package in Noble: Fix Committed Status in lapack source package in Noble: Fix Committed Status in libdeflate source package in Noble: Fix Committed Status in libseccomp source package in Noble: Fix Committed Status in libzdnn source package in Noble: Fix Committed Status in libzstd source package in Noble: Fix Committed Status in lz4 source package in Noble: Fix Committed Status in mysql-8.0 source package in Noble: Fix Committed Status in nettle source package in Noble: Fix Committed Status in openssh source package in Noble: Fix Committed Status in openssl source package in Noble: Fix Committed Status in p11-kit source package in Noble: Fix Committed Status in postgresql-16 source package in Noble: Fix Committed Status in postgresql-common source package in Noble: Fix Committed Status in powerpc-utils source package in Noble: Fix Committed Status in python-greenlet source package in Noble: Fix Committed Status in qemu source package in Noble: Fix Committed Status in runc-app source package in Noble: Fix Committed Status in rustc source package in Noble: Fix Committed S
[Touch-packages] [Bug 2075567] Re: zlib fails to build on s390x on oracular with gcc 14
fixed in gcc-14 14.2.0-3ubuntu1
** Changed in: gcc-14 (Ubuntu)
Status: New => Fix Released
** Changed in: gcc-14 (Ubuntu)
Assignee: (unassigned) => Matthias Klose (doko)
** Changed in: zlib (Ubuntu)
Status: Triaged => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to zlib in Ubuntu.
https://bugs.launchpad.net/bugs/2075567
Title:
zlib fails to build on s390x on oracular with gcc 14
Status in Ubuntu on IBM z Systems:
Triaged
Status in gcc-14 package in Ubuntu:
Fix Released
Status in zlib package in Ubuntu:
Invalid
Bug description:
Rebuilding zlib for s390x on oracular fails to build, probably due to
gcc 14 usage (since it became more strict).
Full build log can be found here:
https://launchpadlibrarian.net/741961061/buildlog_ubuntu-oracular-s390x.zlib_1%3A1.3.dfsg-3.1ubuntu4_BUILDING.txt.gz
erroneous lines are:
D_LARGEFILE64_SOURCE=1 -DHAVE_HIDDEN -DHAVE_IFUNC -DHAVE_S390X_VX -march=z13
-mzarch -c -o crc32-vx.o contrib/s390/crc32-vx.c
contrib/s390/crc32-vx.c: In function ‘crc32_le_vgfm_16’:
contrib/s390/crc32-vx.c:91:52: error: incompatible type for argument 3 of
‘__builtin_s390_vgfmag’
91 | v1 = (uv2di)vec_gfmsum_accum_128(r2r1, v1, part1);
|^
||
|uv16qi {aka
__vector(16) unsigned char}
contrib/s390/crc32-vx.c:91:52: note: expected ‘__int128 unsigned’ but
argument is of type ‘uv16qi’ {aka ‘__vector(16) unsigned char’}
contrib/s390/crc32-vx.c:92:52: error: incompatible type for argument 3 of
‘__builtin_s390_vgfmag’
92 | v2 = (uv2di)vec_gfmsum_accum_128(r2r1, v2, part2);
|^
||
|uv16qi {aka
__vector(16) unsigned char}
contrib/s390/crc32-vx.c:92:52: note: expected ‘__int128 unsigned’ but
argument is of type ‘uv16qi’ {aka ‘__vector(16) unsigned char’}
contrib/s390/crc32-vx.c:93:52: error: incompatible type for argument 3 of
‘__builtin_s390_vgfmag’
93 | v3 = (uv2di)vec_gfmsum_accum_128(r2r1, v3, part3);
|^
||
|uv16qi {aka
__vector(16) unsigned char}
contrib/s390/crc32-vx.c:93:52: note: expected ‘__int128 unsigned’ but
argument is of type ‘uv16qi’ {aka ‘__vector(16) unsigned char’}
contrib/s390/crc32-vx.c:94:52: error: incompatible type for argument 3 of
‘__builtin_s390_vgfmag’
94 | v4 = (uv2di)vec_gfmsum_accum_128(r2r1, v4, part4);
|^
||
|uv16qi {aka
__vector(16) unsigned char}
contrib/s390/crc32-vx.c:94:52: note: expected ‘__int128 unsigned’ but
argument is of type ‘uv16qi’ {aka ‘__vector(16) unsigned char’}
contrib/s390/crc32-vx.c:105:48: error: incompatible type for argument 3 of
‘__builtin_s390_vgfmag’
105 | v1 = (uv2di)vec_gfmsum_accum_128(r4r3, v1, (uv16qi)v2);
|^~
||
|__vector(16) unsigned
char
contrib/s390/crc32-vx.c:105:48: note: expected ‘__int128 unsigned’ but
argument is of type ‘__vector(16) unsigned char’
contrib/s390/crc32-vx.c:106:48: error: incompatible type for argument 3 of
‘__builtin_s390_vgfmag’
106 | v1 = (uv2di)vec_gfmsum_accum_128(r4r3, v1, (uv16qi)v3);
|^~
||
|__vector(16) unsigned
char
contrib/s390/crc32-vx.c:106:48: note: expected ‘__int128 unsigned’ but
argument is of type ‘__vector(16) unsigned char’
contrib/s390/crc32-vx.c:107:48: error: incompatible type for argument 3 of
‘__builtin_s390_vgfmag’
107 | v1 = (uv2di)vec_gfmsum_accum_128(r4r3, v1, (uv16qi)v4);
|^~
||
|__vector(16) unsigned
char
contrib/s390/crc32-vx.c:107:48: note: expected ‘__int128 unsigned’ but
argument is of type ‘__vector(16) unsigned char’
contrib/s390/crc32-vx.c:114:52: error: incompatible type for argument 3 of
‘__builtin_s390_vgfmag’
114 | v1 = (uv2di)vec_gfmsum_accum_128(r4r3, v1, (
[Touch-packages] [Bug 2076340] Re: SRU: no-change rebuild to pick up changed build flags on ppc64el and s390x
** Description changed: SRU: no-change rebuild to pick up changed build flags on ppc64el and s390x This is batch of packages that we want to rebuild to pick up the changed build flags on ppc64el (LP: #2064539) and s390x (LP: #2064538). Impact: These are no change uploads on architectures other than ppc64el and s390x. All of those packages already built successful in oracular with the changed build flags. We will validate picking up the changed build flags by inspecting the log files on ppc64el and s390x. + + Packages with all passing autopkg tests: + lapack golang-1.22 dotnet8 docker.io-app cyrus-sasl2 containerd-app rustc runc-app python-greenlet powerpc-utils p11-kit libzdnn libdeflate -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bzip2 in Ubuntu. https://bugs.launchpad.net/bugs/2076340 Title: SRU: no-change rebuild to pick up changed build flags on ppc64el and s390x Status in atlas package in Ubuntu: New Status in bzip2 package in Ubuntu: New Status in containerd-app package in Ubuntu: New Status in curl package in Ubuntu: New Status in cyrus-sasl2 package in Ubuntu: New Status in dbus package in Ubuntu: New Status in docker.io-app package in Ubuntu: New Status in dotnet8 package in Ubuntu: New Status in gnutls28 package in Ubuntu: New Status in golang-1.22 package in Ubuntu: New Status in icu package in Ubuntu: New Status in lapack package in Ubuntu: New Status in libdeflate package in Ubuntu: New Status in libseccomp package in Ubuntu: New Status in libzdnn package in Ubuntu: Fix Released Status in libzstd package in Ubuntu: New Status in lz4 package in Ubuntu: New Status in mysql-8.0 package in Ubuntu: New Status in nettle package in Ubuntu: New Status in openssh package in Ubuntu: New Status in openssl package in Ubuntu: New Status in p11-kit package in Ubuntu: New Status in postgresql-16 package in Ubuntu: New Status in postgresql-common package in Ubuntu: New Status in powerpc-utils package in Ubuntu: Fix Released Status in python-greenlet package in Ubuntu: Fix Released Status in qemu package in Ubuntu: New Status in runc-app package in Ubuntu: Fix Released Status in rustc package in Ubuntu: New Status in s390-tools package in Ubuntu: New Status in systemd package in Ubuntu: New Status in util-linux package in Ubuntu: New Status in xz-utils package in Ubuntu: New Status in zlib package in Ubuntu: New Status in atlas source package in Noble: Fix Committed Status in bzip2 source package in Noble: Fix Committed Status in containerd-app source package in Noble: Fix Committed Status in curl source package in Noble: Fix Committed Status in cyrus-sasl2 source package in Noble: Fix Committed Status in dbus source package in Noble: Fix Committed Status in docker.io-app source package in Noble: Fix Committed Status in dotnet8 source package in Noble: Fix Committed Status in gnutls28 source package in Noble: Fix Committed Status in golang-1.22 source package in Noble: Fix Committed Status in icu source package in Noble: Fix Committed Status in lapack source package in Noble: Fix Committed Status in libdeflate source package in Noble: Fix Committed Status in libseccomp source package in Noble: Fix Committed Status in libzdnn source package in Noble: Fix Committed Status in libzstd source package in Noble: Fix Committed Status in lz4 source package in Noble: Fix Committed Status in mysql-8.0 source package in Noble: Fix Committed Status in nettle source package in Noble: Fix Committed Status in openssh source package in Noble: Fix Committed Status in openssl source package in Noble: Fix Committed Status in p11-kit source package in Noble: Fix Committed Status in postgresql-16 source package in Noble: Fix Committed Status in postgresql-common source package in Noble: Fix Committed Status in powerpc-utils source package in Noble: Fix Committed Status in python-greenlet source package in Noble: Fix Committed Status in qemu source package in Noble: Fix Committed Status in runc-app source package in Noble: Fix Committed Status in rustc source package in Noble: Fix Committed Status in s390-tools source package in Noble: Fix Committed Status in systemd source package in Noble: Fix Committed Status in util-linux source package in Noble: Fix Committed Status in xz-utils source package in Noble: Fix Committed Status in zlib source package in Noble: Fix Committed Bug description: SRU: no-change rebuild to pick up changed build flags on ppc64el and s390x This is batch of packages that we want to rebuild to pick up the changed build flags on ppc64el (LP: #2064539) and s390x (LP: #2064538). Impact: These are no change uploads on architectures other than ppc64el and s390x. All of those packages already built successful in oracular with the changed build flags.
[Touch-packages] [Bug 2076340] Re: SRU: no-change rebuild to pick up changed build flags on ppc64el and s390x
** Description changed: SRU: no-change rebuild to pick up changed build flags on ppc64el and s390x + + This is batch of packages that we want to rebuild to pick up the changed + build flags on ppc64el (LP: #2064539) and s390x (LP: #2064538). + + Impact: These are no change uploads on architectures other than ppc64el + and s390x. All of those packages already built successful in oracular + with the changed build flags. + + We will validate picking up the changed build flags by inspecting the + log files on ppc64el and s390x. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bzip2 in Ubuntu. https://bugs.launchpad.net/bugs/2076340 Title: SRU: no-change rebuild to pick up changed build flags on ppc64el and s390x Status in atlas package in Ubuntu: New Status in bzip2 package in Ubuntu: New Status in containerd-app package in Ubuntu: New Status in curl package in Ubuntu: New Status in cyrus-sasl2 package in Ubuntu: New Status in dbus package in Ubuntu: New Status in docker.io-app package in Ubuntu: New Status in dotnet8 package in Ubuntu: New Status in gnutls28 package in Ubuntu: New Status in golang-1.22 package in Ubuntu: New Status in icu package in Ubuntu: New Status in lapack package in Ubuntu: New Status in libdeflate package in Ubuntu: New Status in libseccomp package in Ubuntu: New Status in libzdnn package in Ubuntu: Fix Released Status in libzstd package in Ubuntu: New Status in lz4 package in Ubuntu: New Status in mysql-8.0 package in Ubuntu: New Status in nettle package in Ubuntu: New Status in openssh package in Ubuntu: New Status in openssl package in Ubuntu: New Status in p11-kit package in Ubuntu: New Status in postgresql-common package in Ubuntu: New Status in powerpc-utils package in Ubuntu: Fix Released Status in python-greenlet package in Ubuntu: New Status in qemu package in Ubuntu: New Status in runc-app package in Ubuntu: New Status in rustc package in Ubuntu: New Status in s390-tools package in Ubuntu: New Status in systemd package in Ubuntu: New Status in util-linux package in Ubuntu: New Status in xz-utils package in Ubuntu: New Status in zlib package in Ubuntu: New Status in atlas source package in Noble: New Status in bzip2 source package in Noble: New Status in containerd-app source package in Noble: New Status in curl source package in Noble: New Status in cyrus-sasl2 source package in Noble: New Status in dbus source package in Noble: New Status in docker.io-app source package in Noble: New Status in dotnet8 source package in Noble: New Status in gnutls28 source package in Noble: New Status in golang-1.22 source package in Noble: New Status in icu source package in Noble: New Status in lapack source package in Noble: New Status in libdeflate source package in Noble: New Status in libseccomp source package in Noble: New Status in libzdnn source package in Noble: New Status in libzstd source package in Noble: New Status in lz4 source package in Noble: New Status in mysql-8.0 source package in Noble: New Status in nettle source package in Noble: New Status in openssh source package in Noble: New Status in openssl source package in Noble: New Status in p11-kit source package in Noble: New Status in postgresql-common source package in Noble: New Status in powerpc-utils source package in Noble: New Status in python-greenlet source package in Noble: New Status in qemu source package in Noble: New Status in runc-app source package in Noble: New Status in rustc source package in Noble: New Status in s390-tools source package in Noble: New Status in systemd source package in Noble: New Status in util-linux source package in Noble: New Status in xz-utils source package in Noble: New Status in zlib source package in Noble: New Bug description: SRU: no-change rebuild to pick up changed build flags on ppc64el and s390x This is batch of packages that we want to rebuild to pick up the changed build flags on ppc64el (LP: #2064539) and s390x (LP: #2064538). Impact: These are no change uploads on architectures other than ppc64el and s390x. All of those packages already built successful in oracular with the changed build flags. We will validate picking up the changed build flags by inspecting the log files on ppc64el and s390x. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/atlas/+bug/2076340/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2076340] Re: SRU: no-change rebuild to pick up changed build flags on ppc64el and s390x
** Also affects: util-linux (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: bzip2 (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: curl (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: dbus (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: nettle (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: cyrus-sasl2 (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: openssl (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: openssh (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: zlib (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: atlas (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: icu (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: lapack (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: qemu (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: s390-tools (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: powerpc-utils (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: postgresql-common (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: xz-utils (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: python-greenlet (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: p11-kit (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: gnutls28 (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: libseccomp (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: lz4 (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: rustc (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: libzstd (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: mysql-8.0 (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: libdeflate (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: libzdnn (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: dotnet8 (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: docker.io-app (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: containerd-app (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: runc-app (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: golang-1.22 (Ubuntu Noble) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bzip2 in Ubuntu. https://bugs.launchpad.net/bugs/2076340 Title: SRU: no-change rebuild to pick up changed build flags on ppc64el and s390x Status in atlas package in Ubuntu: New Status in bzip2 package in Ubuntu: New Status in containerd-app package in Ubuntu: New Status in curl package in Ubuntu: New Status in cyrus-sasl2 package in Ubuntu: New Status in dbus package in Ubuntu: New Status in docker.io-app package in Ubuntu: New Status in dotnet8 package in Ubuntu: New Status in gnutls28 package in Ubuntu: New Status in golang-1.22 package in Ubuntu: New Status in icu package in Ubuntu: New Status in lapack package in Ubuntu: New Status in libdeflate package in Ubuntu: New Status in libseccomp package in Ubuntu: New Status in libzdnn package in Ubuntu: Fix Released Status in libzstd package in Ubuntu: New Status in lz4 package in Ubuntu: New Status in mysql-8.0 package in Ubuntu: New Status in nettle package in Ubuntu: New Status in openssh package in Ubuntu: New Status in openssl package in Ubuntu: New Status in p11-kit package in Ubuntu: New Status in postgresql-common package in Ubuntu: New Status in powerpc-utils package in Ubuntu: Fix Released Status in python-greenlet package in Ubuntu: New Status in qemu package in Ubuntu: New Status in runc-app package in Ubuntu: New Status in rustc package in Ubuntu: New Status in s390-tools package in Ubuntu: New Status in systemd package in Ubuntu: New Status in util-linux package in Ubuntu: New Status in xz-utils package in Ubuntu: New Status in zlib package in Ubuntu: New Status in atlas source package in Noble: New Status in bzip2 source package in Noble: New Status in containerd-app source package in Noble: New Status in curl source package in Noble: New Status in cyrus-sasl2 source package in Noble: New Status in dbus source package in Noble: New Status in docker.io-app source package in Noble: New Status in dotnet8 source package in Noble: New Status in gnutls28 source
[Touch-packages] [Bug 2076340] Re: SRU: no-change rebuild to pick up changed build flags on ppc64el and s390x
** Also affects: postgresql-common (Ubuntu) Importance: Undecided Status: New ** Also affects: p11-kit (Ubuntu) Importance: Undecided Status: New ** Also affects: openssl (Ubuntu) Importance: Undecided Status: New ** Also affects: openssh (Ubuntu) Importance: Undecided Status: New ** Also affects: nettle (Ubuntu) Importance: Undecided Status: New ** Also affects: mysql-8.0 (Ubuntu) Importance: Undecided Status: New ** Also affects: lz4 (Ubuntu) Importance: Undecided Status: New ** Also affects: libzstd (Ubuntu) Importance: Undecided Status: New ** Also affects: libzdnn (Ubuntu) Importance: Undecided Status: New ** Also affects: libseccomp (Ubuntu) Importance: Undecided Status: New ** Also affects: libdeflate (Ubuntu) Importance: Undecided Status: New ** Also affects: lapack (Ubuntu) Importance: Undecided Status: New ** Also affects: icu (Ubuntu) Importance: Undecided Status: New ** Also affects: golang-1.22 (Ubuntu) Importance: Undecided Status: New ** Also affects: gnutls28 (Ubuntu) Importance: Undecided Status: New ** Also affects: dotnet8 (Ubuntu) Importance: Undecided Status: New ** Also affects: docker.io-app (Ubuntu) Importance: Undecided Status: New ** Also affects: dbus (Ubuntu) Importance: Undecided Status: New ** Also affects: cyrus-sasl2 (Ubuntu) Importance: Undecided Status: New ** Also affects: curl (Ubuntu) Importance: Undecided Status: New ** Also affects: containerd-app (Ubuntu) Importance: Undecided Status: New ** Also affects: bzip2 (Ubuntu) Importance: Undecided Status: New ** Also affects: atlas (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bzip2 in Ubuntu. https://bugs.launchpad.net/bugs/2076340 Title: SRU: no-change rebuild to pick up changed build flags on ppc64el and s390x Status in atlas package in Ubuntu: New Status in bzip2 package in Ubuntu: New Status in containerd-app package in Ubuntu: New Status in curl package in Ubuntu: New Status in cyrus-sasl2 package in Ubuntu: New Status in dbus package in Ubuntu: New Status in docker.io-app package in Ubuntu: New Status in dotnet8 package in Ubuntu: New Status in gnutls28 package in Ubuntu: New Status in golang-1.22 package in Ubuntu: New Status in icu package in Ubuntu: New Status in lapack package in Ubuntu: New Status in libdeflate package in Ubuntu: New Status in libseccomp package in Ubuntu: New Status in libzdnn package in Ubuntu: New Status in libzstd package in Ubuntu: New Status in lz4 package in Ubuntu: New Status in mysql-8.0 package in Ubuntu: New Status in nettle package in Ubuntu: New Status in openssh package in Ubuntu: New Status in openssl package in Ubuntu: New Status in p11-kit package in Ubuntu: New Status in postgresql-common package in Ubuntu: New Status in powerpc-utils package in Ubuntu: New Status in python-greenlet package in Ubuntu: New Status in qemu package in Ubuntu: New Status in runc-app package in Ubuntu: New Status in rustc package in Ubuntu: New Status in s390-tools package in Ubuntu: New Status in systemd package in Ubuntu: New Status in util-linux package in Ubuntu: New Status in xz-utils package in Ubuntu: New Status in zlib package in Ubuntu: New Bug description: SRU: no-change rebuild to pick up changed build flags on ppc64el and s390x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/atlas/+bug/2076340/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2076340] Re: SRU: no-change rebuild to pick up changed build flags on ppc64el and s390x
** Also affects: s390-tools (Ubuntu) Importance: Undecided Status: New ** Also affects: rustc (Ubuntu) Importance: Undecided Status: New ** Also affects: runc-app (Ubuntu) Importance: Undecided Status: New ** Also affects: qemu (Ubuntu) Importance: Undecided Status: New ** Also affects: python-greenlet (Ubuntu) Importance: Undecided Status: New ** Also affects: powerpc-utils (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2076340 Title: SRU: no-change rebuild to pick up changed build flags on ppc64el and s390x Status in mysql-8.0 package in Ubuntu: New Status in nettle package in Ubuntu: New Status in openssh package in Ubuntu: New Status in openssl package in Ubuntu: New Status in p11-kit package in Ubuntu: New Status in postgresql-common package in Ubuntu: New Status in powerpc-utils package in Ubuntu: New Status in python-greenlet package in Ubuntu: New Status in qemu package in Ubuntu: New Status in runc-app package in Ubuntu: New Status in rustc package in Ubuntu: New Status in s390-tools package in Ubuntu: New Status in systemd package in Ubuntu: New Status in util-linux package in Ubuntu: New Status in xz-utils package in Ubuntu: New Status in zlib package in Ubuntu: New Bug description: SRU: no-change rebuild to pick up changed build flags on ppc64el and s390x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/2076340/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2076340] Re: SRU: no-change rebuild to pick up changed build flags on ppc64el and s390x
** Also affects: xz-utils (Ubuntu) Importance: Undecided Status: New ** Also affects: util-linux (Ubuntu) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xz-utils in Ubuntu. https://bugs.launchpad.net/bugs/2076340 Title: SRU: no-change rebuild to pick up changed build flags on ppc64el and s390x Status in runc-app package in Ubuntu: New Status in rustc package in Ubuntu: New Status in s390-tools package in Ubuntu: New Status in systemd package in Ubuntu: New Status in util-linux package in Ubuntu: New Status in xz-utils package in Ubuntu: New Status in zlib package in Ubuntu: New Bug description: SRU: no-change rebuild to pick up changed build flags on ppc64el and s390x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/runc-app/+bug/2076340/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2076340] [NEW] SRU: no-change rebuild to pick up changed build flags on ppc64el and s390x
Public bug reported: SRU: no-change rebuild to pick up changed build flags on ppc64el and s390x ** Affects: zlib (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to zlib in Ubuntu. https://bugs.launchpad.net/bugs/2076340 Title: SRU: no-change rebuild to pick up changed build flags on ppc64el and s390x Status in zlib package in Ubuntu: New Bug description: SRU: no-change rebuild to pick up changed build flags on ppc64el and s390x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zlib/+bug/2076340/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2074113] Re: pymdown-extensions: FTBFS: AssertionError: False is not true
** Changed in: python3-defaults (Ubuntu) Status: New => Invalid ** Changed in: pymdown-extensions (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/2074113 Title: pymdown-extensions: FTBFS: AssertionError: False is not true Status in pymdown-extensions package in Ubuntu: Fix Released Status in python3-defaults package in Ubuntu: Invalid Status in pymdown-extensions package in Debian: Fix Released Bug description: Imported from Debian bug http://bugs.debian.org/1076907: Package: src:pymdown-extensions Version: 10.8.1-1 Severity: serious Tags: ftbfs Dear maintainer: During a rebuild of all packages in unstable, your package failed to build: [...] debian/rules binary dh binary --buildsystem=pybuild dh_update_autotools_config -O--buildsystem=pybuild dh_autoreconf -O--buildsystem=pybuild dh_auto_configure -O--buildsystem=pybuild dh_auto_build -O--buildsystem=pybuild I: pybuild plugin_pyproject:129: Building wheel for python3.12 with "build" module I: pybuild base:311: python3.12 -m build --skip-dependency-check --no-isolation --wheel --outdir /<>/.pybuild/cpython3_3.12_pymdownx * Building wheel... Successfully built pymdown_extensions-10.8.1-py3-none-any.whl I: pybuild plugin_pyproject:144: Unpacking wheel built for python3.12 with "installer" module dh_auto_test -O--buildsystem=pybuild I: pybuild base:311: cd /<>/.pybuild/cpython3_3.12_pymdownx/build; python3.12 -m pytest tests = test session starts == platform linux -- Python 3.12.4, pytest-8.2.2, pluggy-1.5.0 rootdir: /<>/.pybuild/cpython3_3.12_pymdownx/build configfile: pyproject.toml collected 532 items tests/test_extensions/test_arithmatex.py .. [ 1%] tests/test_extensions/test_b64.py . [ 2%] tests/test_extensions/test_betterem.py ..[ 3%] tests/test_extensions/test_blocks/test_admonitions.py [ 6%] tests/test_extensions/test_blocks/test_definition.py . [ 7%] tests/test_extensions/test_blocks/test_details.py ...[ 9%] tests/test_extensions/test_blocks/test_general_blocks.py ... [ 12%] .[ 15%] tests/test_extensions/test_blocks/test_html.py [ 18%] tests/test_extensions/test_blocks/test_legacy_tab.py [ 20%] tests/test_extensions/test_blocks/test_tab.py ...[ 22%] tests/test_extensions/test_details.py ...[ 25%] tests/test_extensions/test_emoji.py .. [ 25%] tests/test_extensions/test_escapeall.py [ 26%] tests/test_extensions/test_highlight.py FF [ 32%] tests/test_extensions/test_inlinehilite.py ...FF [ 36%] tests/test_extensions/test_keys.py . [ 36%] tests/test_extensions/test_legacy_slugs.py ..[ 37%] tests/test_extensions/test_magiclink.py [ 42%] tests/test_extensions/test_pathconverter.py [ 47%] .[ 51%] tests/test_extensions/test_saneheaders.py .. [ 53%] tests/test_extensions/test_slugs.py [ 54%] tests/test_extensions/test_smartsymbols.py ... [ 56%] tests/test_extensions/test_snippets.py . [ 62%] .[ 65%] tests/test_extensions/test_striphmtl.py .[ 66%] tests/test_extensions/test_superfences.py .. [ 71%] [ 77%] tests/test_extensions/test_tabbed.py . [ 81%] tests/test_extensions/test_tabbed_alternate.py . [ 84%] tests/test_syntax.py ... [ 94%] [ 96%] tests/test_targeted.py . [ 99%] tests/test_versions.py [100%] === FAILURES === __
[Touch-packages] [Bug 2071468] Re: ELF package metadata failure: environment variable ‘DEB_HOST_ARCH’ not defined
dpkg 1.22.11ubuntu1 stops passing the --specs option. It will be
replaced by
- dpkg-buildpackage setting ELF_PACKAGE_METADATA in the environment,
which gets picked up GCC and clang, and added as a linker option.
- the linkers ld.bfd, gold, mold and lld picking up ELF_PACKAGE_METADATA
if they don't see a package-metadata option.
This is committed, and will be uploaded later.
- dpkg-buildflags passing an option --encoded-package-metadata, which
can be safely passed.
This option has to go upstream first into the linkers, so that we
don't have API incompatible linker versions in the archive.
If the fix for the other packages in this report is the only ubuntu delta,
it can be safely dropped.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to graphite2 in Ubuntu.
https://bugs.launchpad.net/bugs/2071468
Title:
ELF package metadata failure: environment variable ‘DEB_HOST_ARCH’ not
defined
Status in asymptote package in Ubuntu:
Fix Released
Status in curl package in Ubuntu:
Fix Released
Status in deal.ii package in Ubuntu:
New
Status in doxygen package in Ubuntu:
Fix Released
Status in dpkg package in Ubuntu:
Triaged
Status in gcl27 package in Ubuntu:
New
Status in graphite2 package in Ubuntu:
Fix Released
Status in gsequencer package in Ubuntu:
Fix Released
Status in gsl package in Ubuntu:
New
Status in haskell-devscripts package in Ubuntu:
Fix Released
Status in jose package in Ubuntu:
New
Status in ksmtuned package in Ubuntu:
Fix Released
Status in libreoffice package in Ubuntu:
Fix Released
Status in libtpms package in Ubuntu:
New
Status in mosh package in Ubuntu:
Fix Released
Status in mpich package in Ubuntu:
New
Status in mwrap package in Ubuntu:
Fix Released
Status in proftpd package in Ubuntu:
New
Status in proftpd-dfsg package in Ubuntu:
Fix Released
Status in quantlib package in Ubuntu:
Fix Released
Status in serf package in Ubuntu:
Fix Released
Status in setserial package in Ubuntu:
Fix Released
Status in speech-dispatcher package in Ubuntu:
New
Status in squid package in Ubuntu:
Fix Released
Status in swtpm package in Ubuntu:
Fix Released
Status in texinfo package in Ubuntu:
Triaged
Status in tix package in Ubuntu:
Fix Released
Bug description:
The ELF package note metadata introduced in dpkg 1.22.6ubuntu11
(refined in 1.22.6ubuntu14) can cause this failure:
```
gcc fatal error: environment variable ‘DEB_HOST_ARCH’ not defined
```
This happens when the `-specs=/usr/share/dpkg/elf-package-
metadata.specs` parameter is set but the needed environment variables
are not set. Cases:
1. Only the LDFLAGS is queried from dpkg-buildflags. Affected source
packages builds: python3.12, openjdk-21, cdbs (causing dvbstreamer and
rp-pppoe fail to build)
2. autopkgtests
3. debugging a crash of an application build with the -spec parameter
4. People like to iteratively continue building the software in the
build dir while hacking on the package and then have no environment
variable set.
This approach is too fragile. An alternative approach would be to specify the
`--package-metadata` linker flag directly. The problem with that approach is
that the curly brackets and quotation marks need to be escaped. Example
failure: Building dpkg would add this parameter to the LDFLAGS:
```
-Wl,--package-metadata,{"type":"deb","os":"ubuntu","name":"dpkg","version":"1.22.6ubuntu15","architecture":"amd64"}
```
The following configure script call (non-relevant parameters deleted):
```
$ gcc
-Wl,--package-metadata,{type:deb,os:ubuntu,name:dpkg,version:1.22.6ubuntu15,architecture:amd64}
/usr/bin/ld: cannot find {type:deb: No such file or directory
/usr/bin/ld: cannot find os:ubuntu: No such file or directory
/usr/bin/ld: cannot find name:dpkg: No such file or directory
/usr/bin/ld: cannot find version:1.22.6ubuntu15: No such file or directory
/usr/bin/ld: cannot find architecture:amd64}: No such file or directory
```
Proposed solution: Add support for an `--escaped-package-metadata` parameter
to the linkers that takes an URL encoded (RFC 3986) parameter. Example:
```
-Wl,--encoded-package-metadata,%7B%22type%22:%22deb%22%2C%22os%22:%22ubuntu%22%2C%22name%22:%22dpkg%22%2C%22version%22:%221.22.6ubuntu15%22%2C%22architecture%22:%22amd64%22%7D
```
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/asymptote/+bug/2071468/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2074191] Re: Binary RM of 32-bit binaries on s390x
** Changed in: zlib (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to zlib in Ubuntu. https://bugs.launchpad.net/bugs/2074191 Title: Binary RM of 32-bit binaries on s390x Status in glibc package in Ubuntu: Incomplete Status in zlib package in Ubuntu: In Progress Bug description: Hi, Could you please do a binary removal of the following binary packages in the oracular release pocket? lib32z1 lib32z1-dev libc6-s390 libc6-dev-s390 oaklisp We have removed the support for 32-bit binaries on s390x (see bug 2067350), and these leftovers are preventing glibc from migrating. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/2074191/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2075337] Re: py3clean fails when using alternate character set
the fallback dpkg -L call in dh-python's autoscripts/prerm-py3clean should also set the env var. ** Also affects: dh-python (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dh-python in Ubuntu. https://bugs.launchpad.net/bugs/2075337 Title: py3clean fails when using alternate character set Status in dh-python package in Ubuntu: New Status in python3-defaults package in Ubuntu: New Bug description: We noticed this in bug 2060769 but think it is a separate issue. dh_python3 is putting a py3clean invocation into package prerm maintainer scripts. When that runs, it explodes if the system character set is for example ISO-8859-1. This appears to affect every package for which dh_python3 has inserted a call to py3clean into the package prerm. python3-minimal 3.12.3-0ubuntu1 In this reproducer, cloud-init is at 24.1.3-0ubuntu3.3. Steps to reproduce: $ lxc launch ubuntu:noble rbasak-pro-l8n $ lxc shell rbasak-pro-l8n # locale-gen fr_FR Generating locales (this might take a while)... fr_FR.ISO-8859-1... done Generation complete. # update-locale LANG=fr_FR # exit # adjust terminal to ISO-8859-1 $ lxc shell rbasak-pro-l8n # apt update && apt install --reinstall cloud-init Expected results: success Actual results: Lecture des listes de paquets... Fait Construction de l'arbre des dépendances... Fait Lecture des informations d'état... Fait 0 mis à jour, 0 nouvellement installés, 1 réinstallés, 0 à enlever et 5 non mis à jour. Il est nécessaire de prendre 598 ko dans les archives. Après cette opération, 0 o d'espace disque supplémentaires seront utilisés. Réception de :1 http://archive.ubuntu.com/ubuntu noble-updates/main amd64 cloud-init all 24.1.3-0ubuntu3.3 [598 kB] 598 ko réceptionnés en 1s (926 ko/s) Préconfiguration des paquets... (Lecture de la base de données... 34406 fichiers et répertoires déjà installés.) Préparation du dépaquetage de .../cloud-init_24.1.3-0ubuntu3.3_all.deb ... Traceback (most recent call last): File "/usr/bin/py3clean", line 210, in main() File "/usr/bin/py3clean", line 196, in main pfiles = set(dpf.from_package(options.package)) ^^ File "/usr/share/python3/debpython/files.py", line 54, in from_package stdout = str(stdout, 'utf-8') UnicodeDecodeError: 'utf-8' codec can't decode byte 0xe9 in position 2417: invalid continuation byte dpkg: avertissement: le sous-processus ancien paquet cloud-init script pre-removal a renvoyé un état de sortie d'erreur 1 dpkg: tentative d'exécution du script du nouveau paquet à la place... Traceback (most recent call last): File "/usr/bin/py3clean", line 210, in main() File "/usr/bin/py3clean", line 196, in main pfiles = set(dpf.from_package(options.package)) ^^ File "/usr/share/python3/debpython/files.py", line 54, in from_package stdout = str(stdout, 'utf-8') UnicodeDecodeError: 'utf-8' codec can't decode byte 0xe9 in position 2417: invalid continuation byte dpkg: erreur de traitement de l'archive /var/cache/apt/archives/cloud-init_24.1.3-0ubuntu3.3_all.deb (--unpack) : le sous-processus nouveau cloud-init paquet pre-removal script a renvoyé un état de sortie d'erreur 1 dmesg: read kernel buffer failed: Operation not permitted Traceback (most recent call last): File "/usr/bin/py3compile", line 323, in main() File "/usr/bin/py3compile", line 302, in main compile(files, versions, File "/usr/bin/py3compile", line 185, in compile for fn, versions_to_compile in filter_files(files, e_patterns, versions): File "/usr/bin/py3compile", line 128, in filter_files for fpath in files: File "/usr/share/python3/debpython/files.py", line 71, in filter_public for fn in files: File "/usr/share/python3/debpython/files.py", line 54, in from_package stdout = str(stdout, 'utf-8') UnicodeDecodeError: 'utf-8' codec can't decode byte 0xe9 in position 2417: invalid continuation byte dpkg: erreur lors du nettoyage: le sous-processus paquet cloud-init script post-installation installé a renvoyé un état de sortie d'erreur 1 Des erreurs ont été rencontrées pendant l'exécution : /var/cache/apt/archives/cloud-init_24.1.3-0ubuntu3.3_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dh-python/+bug/2075337/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://lau
[Touch-packages] [Bug 2074191] Re: Binary RM of 32-bit binaries on s390x
updated zlib not to build the 32bit binaries, but it currently ftbfs the gcc packages should be all done now, not building the s390x multilibs anymore. ** Also affects: zlib (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to zlib in Ubuntu. https://bugs.launchpad.net/bugs/2074191 Title: Binary RM of 32-bit binaries on s390x Status in glibc package in Ubuntu: Incomplete Status in zlib package in Ubuntu: New Bug description: Hi, Could you please do a binary removal of the following binary packages in the oracular release pocket? lib32z1 lib32z1-dev libc6-s390 libc6-dev-s390 oaklisp We have removed the support for 32-bit binaries on s390x (see bug 2067350), and these leftovers are preventing glibc from migrating. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/2074191/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2076024] [NEW] SRU: build with -fno-omit-frame-pointer
Public bug reported: SRU: build with -fno-omit-frame-pointer, if it's enabled in dpkg- buildflags. ** Affects: binutils (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/2076024 Title: SRU: build with -fno-omit-frame-pointer Status in binutils package in Ubuntu: New Bug description: SRU: build with -fno-omit-frame-pointer, if it's enabled in dpkg- buildflags. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/2076024/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2075337] Re: py3clean fails when using alternate character set
ta, I'll merge that for oracular together with the python 3.12.5 updates -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dh-python in Ubuntu. https://bugs.launchpad.net/bugs/2075337 Title: py3clean fails when using alternate character set Status in dh-python package in Ubuntu: New Status in python3-defaults package in Ubuntu: New Bug description: We noticed this in bug 2060769 but think it is a separate issue. dh_python3 is putting a py3clean invocation into package prerm maintainer scripts. When that runs, it explodes if the system character set is for example ISO-8859-1. This appears to affect every package for which dh_python3 has inserted a call to py3clean into the package prerm. python3-minimal 3.12.3-0ubuntu1 In this reproducer, cloud-init is at 24.1.3-0ubuntu3.3. Steps to reproduce: $ lxc launch ubuntu:noble rbasak-pro-l8n $ lxc shell rbasak-pro-l8n # locale-gen fr_FR Generating locales (this might take a while)... fr_FR.ISO-8859-1... done Generation complete. # update-locale LANG=fr_FR # exit # adjust terminal to ISO-8859-1 $ lxc shell rbasak-pro-l8n # apt update && apt install --reinstall cloud-init Expected results: success Actual results: Lecture des listes de paquets... Fait Construction de l'arbre des dépendances... Fait Lecture des informations d'état... Fait 0 mis à jour, 0 nouvellement installés, 1 réinstallés, 0 à enlever et 5 non mis à jour. Il est nécessaire de prendre 598 ko dans les archives. Après cette opération, 0 o d'espace disque supplémentaires seront utilisés. Réception de :1 http://archive.ubuntu.com/ubuntu noble-updates/main amd64 cloud-init all 24.1.3-0ubuntu3.3 [598 kB] 598 ko réceptionnés en 1s (926 ko/s) Préconfiguration des paquets... (Lecture de la base de données... 34406 fichiers et répertoires déjà installés.) Préparation du dépaquetage de .../cloud-init_24.1.3-0ubuntu3.3_all.deb ... Traceback (most recent call last): File "/usr/bin/py3clean", line 210, in main() File "/usr/bin/py3clean", line 196, in main pfiles = set(dpf.from_package(options.package)) ^^ File "/usr/share/python3/debpython/files.py", line 54, in from_package stdout = str(stdout, 'utf-8') UnicodeDecodeError: 'utf-8' codec can't decode byte 0xe9 in position 2417: invalid continuation byte dpkg: avertissement: le sous-processus ancien paquet cloud-init script pre-removal a renvoyé un état de sortie d'erreur 1 dpkg: tentative d'exécution du script du nouveau paquet à la place... Traceback (most recent call last): File "/usr/bin/py3clean", line 210, in main() File "/usr/bin/py3clean", line 196, in main pfiles = set(dpf.from_package(options.package)) ^^ File "/usr/share/python3/debpython/files.py", line 54, in from_package stdout = str(stdout, 'utf-8') UnicodeDecodeError: 'utf-8' codec can't decode byte 0xe9 in position 2417: invalid continuation byte dpkg: erreur de traitement de l'archive /var/cache/apt/archives/cloud-init_24.1.3-0ubuntu3.3_all.deb (--unpack) : le sous-processus nouveau cloud-init paquet pre-removal script a renvoyé un état de sortie d'erreur 1 dmesg: read kernel buffer failed: Operation not permitted Traceback (most recent call last): File "/usr/bin/py3compile", line 323, in main() File "/usr/bin/py3compile", line 302, in main compile(files, versions, File "/usr/bin/py3compile", line 185, in compile for fn, versions_to_compile in filter_files(files, e_patterns, versions): File "/usr/bin/py3compile", line 128, in filter_files for fpath in files: File "/usr/share/python3/debpython/files.py", line 71, in filter_public for fn in files: File "/usr/share/python3/debpython/files.py", line 54, in from_package stdout = str(stdout, 'utf-8') UnicodeDecodeError: 'utf-8' codec can't decode byte 0xe9 in position 2417: invalid continuation byte dpkg: erreur lors du nettoyage: le sous-processus paquet cloud-init script post-installation installé a renvoyé un état de sortie d'erreur 1 Des erreurs ont été rencontrées pendant l'exécution : /var/cache/apt/archives/cloud-init_24.1.3-0ubuntu3.3_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dh-python/+bug/2075337/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2075337] Re: py3clean fails when using alternate character set
** Also affects: python3-defaults (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: dh-python (Ubuntu Noble) Importance: Undecided Status: New ** Changed in: python3-defaults (Ubuntu) Assignee: (unassigned) => Matthias Klose (doko) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/2075337 Title: py3clean fails when using alternate character set Status in dh-python package in Ubuntu: New Status in python3-defaults package in Ubuntu: New Status in dh-python source package in Noble: New Status in python3-defaults source package in Noble: New Bug description: We noticed this in bug 2060769 but think it is a separate issue. dh_python3 is putting a py3clean invocation into package prerm maintainer scripts. When that runs, it explodes if the system character set is for example ISO-8859-1. This appears to affect every package for which dh_python3 has inserted a call to py3clean into the package prerm. python3-minimal 3.12.3-0ubuntu1 In this reproducer, cloud-init is at 24.1.3-0ubuntu3.3. Steps to reproduce: $ lxc launch ubuntu:noble rbasak-pro-l8n $ lxc shell rbasak-pro-l8n # locale-gen fr_FR Generating locales (this might take a while)... fr_FR.ISO-8859-1... done Generation complete. # update-locale LANG=fr_FR # exit # adjust terminal to ISO-8859-1 $ lxc shell rbasak-pro-l8n # apt update && apt install --reinstall cloud-init Expected results: success Actual results: Lecture des listes de paquets... Fait Construction de l'arbre des dépendances... Fait Lecture des informations d'état... Fait 0 mis à jour, 0 nouvellement installés, 1 réinstallés, 0 à enlever et 5 non mis à jour. Il est nécessaire de prendre 598 ko dans les archives. Après cette opération, 0 o d'espace disque supplémentaires seront utilisés. Réception de :1 http://archive.ubuntu.com/ubuntu noble-updates/main amd64 cloud-init all 24.1.3-0ubuntu3.3 [598 kB] 598 ko réceptionnés en 1s (926 ko/s) Préconfiguration des paquets... (Lecture de la base de données... 34406 fichiers et répertoires déjà installés.) Préparation du dépaquetage de .../cloud-init_24.1.3-0ubuntu3.3_all.deb ... Traceback (most recent call last): File "/usr/bin/py3clean", line 210, in main() File "/usr/bin/py3clean", line 196, in main pfiles = set(dpf.from_package(options.package)) ^^ File "/usr/share/python3/debpython/files.py", line 54, in from_package stdout = str(stdout, 'utf-8') UnicodeDecodeError: 'utf-8' codec can't decode byte 0xe9 in position 2417: invalid continuation byte dpkg: avertissement: le sous-processus ancien paquet cloud-init script pre-removal a renvoyé un état de sortie d'erreur 1 dpkg: tentative d'exécution du script du nouveau paquet à la place... Traceback (most recent call last): File "/usr/bin/py3clean", line 210, in main() File "/usr/bin/py3clean", line 196, in main pfiles = set(dpf.from_package(options.package)) ^^ File "/usr/share/python3/debpython/files.py", line 54, in from_package stdout = str(stdout, 'utf-8') UnicodeDecodeError: 'utf-8' codec can't decode byte 0xe9 in position 2417: invalid continuation byte dpkg: erreur de traitement de l'archive /var/cache/apt/archives/cloud-init_24.1.3-0ubuntu3.3_all.deb (--unpack) : le sous-processus nouveau cloud-init paquet pre-removal script a renvoyé un état de sortie d'erreur 1 dmesg: read kernel buffer failed: Operation not permitted Traceback (most recent call last): File "/usr/bin/py3compile", line 323, in main() File "/usr/bin/py3compile", line 302, in main compile(files, versions, File "/usr/bin/py3compile", line 185, in compile for fn, versions_to_compile in filter_files(files, e_patterns, versions): File "/usr/bin/py3compile", line 128, in filter_files for fpath in files: File "/usr/share/python3/debpython/files.py", line 71, in filter_public for fn in files: File "/usr/share/python3/debpython/files.py", line 54, in from_package stdout = str(stdout, 'utf-8') UnicodeDecodeError: 'utf-8' codec can't decode byte 0xe9 in position 2417: invalid continuation byte dpkg: erreur lors du nettoyage: le sous-processus paquet cloud-init script post-installation installé a renvoyé un état de
[Touch-packages] [Bug 2061834] [NEW] apt build-dep . fails to parse build dependencies
Public bug reported: seen in trantor 1.5.12+ds-1ubuntu3: Build-Depends: cmake, debhelper-compat (=13), dh-cmake, dh-cmake-compat (=1) replacing (=1) with (= 1) lets the parsing succeed. $ sudo apt build-dep . Note, using directory '.' to get the build dependencies Reading package lists... Done E: Problem parsing dependency: Build-Depends E: Unable to get build-dependency information for . ** Affects: apt (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/2061834 Title: apt build-dep . fails to parse build dependencies Status in apt package in Ubuntu: New Bug description: seen in trantor 1.5.12+ds-1ubuntu3: Build-Depends: cmake, debhelper-compat (=13), dh-cmake, dh-cmake- compat (=1) replacing (=1) with (= 1) lets the parsing succeed. $ sudo apt build-dep . Note, using directory '.' to get the build dependencies Reading package lists... Done E: Problem parsing dependency: Build-Depends E: Unable to get build-dependency information for . To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2061834/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2058242] Re: Demote isc-dhcp to universe
that doesn't show up in component-mismatches yet. something in main still depending on it ** Changed in: isc-dhcp (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/2058242 Title: Demote isc-dhcp to universe Status in isc-dhcp package in Ubuntu: Incomplete Bug description: Following the replacement of dhclient by dhcpcd as new DHCP client tool, it is now time to demote isc-dhcp-client. After demoting isc- dhcp-server (bug # 2045577) the complete isc-dhcp can be demoted. ``` $ reverse-depends -c main,restricted isc-dhcp-client $ reverse-depends -c main,restricted -b isc-dhcp-client ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/2058242/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2057836] Re: gst-python1.0 fails to build: test failures
same test failures with pygobject 3.48.1-1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pygobject in Ubuntu. https://bugs.launchpad.net/bugs/2057836 Title: gst-python1.0 fails to build: test failures Status in pygobject: New Status in gst-python1.0 package in Ubuntu: Triaged Status in pygobject package in Ubuntu: Triaged Status in gst-python1.0 package in Debian: Confirmed Bug description: gst-python1.0 fails to build because of test failures. https://launchpad.net/ubuntu/+source/gst-python1.0/1.22.10-1build1 https://launchpad.net/ubuntu/+source/gst-python1.0/1.24.0-1 I have reported the issue to the upstream developers https://gitlab.freedesktop.org/gstreamer/gstreamer/-/issues/3353 To manage notifications about this bug go to: https://bugs.launchpad.net/pygobject/+bug/2057836/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2057836] Re: gst-python1.0 fails to build: test failures
Debian added a b-d on pygobject >= 3.48.1, which we don't have -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pygobject in Ubuntu. https://bugs.launchpad.net/bugs/2057836 Title: gst-python1.0 fails to build: test failures Status in pygobject: New Status in gst-python1.0 package in Ubuntu: Triaged Status in pygobject package in Ubuntu: Triaged Status in gst-python1.0 package in Debian: Confirmed Bug description: gst-python1.0 fails to build because of test failures. https://launchpad.net/ubuntu/+source/gst-python1.0/1.22.10-1build1 https://launchpad.net/ubuntu/+source/gst-python1.0/1.24.0-1 I have reported the issue to the upstream developers https://gitlab.freedesktop.org/gstreamer/gstreamer/-/issues/3353 To manage notifications about this bug go to: https://bugs.launchpad.net/pygobject/+bug/2057836/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1982336] Re: [24.04 FEAT] GDB: Support for new IBM Z Hardware (IBM z16)
** Changed in: gdb (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdb in Ubuntu. https://bugs.launchpad.net/bugs/1982336 Title: [24.04 FEAT] GDB: Support for new IBM Z Hardware (IBM z16) Status in Ubuntu on IBM z Systems: In Progress Status in gdb package in Ubuntu: Fix Committed Bug description: GDB Support for new IBM Z Hardware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1982336/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2054351] [NEW] nux ftbfs on armhf (tests segfaulting)
Public bug reported: [--] 8 tests from TestScrollView [ RUN ] TestScrollView.TestQueueDrawScrollDownNoScrollbars [ OK ] TestScrollView.TestQueueDrawScrollDownNoScrollbars (434 ms) [ RUN ] TestScrollView.TestQueueDrawScrollUpNoScrollbars [ OK ] TestScrollView.TestQueueDrawScrollUpNoScrollbars (496 ms) [ RUN ] TestScrollView.TestQueueDrawScrollDown [ OK ] TestScrollView.TestQueueDrawScrollDown (446 ms) [ RUN ] TestScrollView.TestQueueDrawScrollUp Segmentation fault (core dumped) make[3]: *** [Makefile:2670: check-headless] Error 139 make[3]: Leaving directory '/<>/tests' make[2]: *** [Makefile:1061: check-headless] Error 2 ** Affects: nux (Ubuntu) Importance: Undecided Status: New ** Tags: ftbfs rls-nn-incoming ** Tags added: ftbfs rls-nn-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to nux in Ubuntu. https://bugs.launchpad.net/bugs/2054351 Title: nux ftbfs on armhf (tests segfaulting) Status in nux package in Ubuntu: New Bug description: [--] 8 tests from TestScrollView [ RUN ] TestScrollView.TestQueueDrawScrollDownNoScrollbars [ OK ] TestScrollView.TestQueueDrawScrollDownNoScrollbars (434 ms) [ RUN ] TestScrollView.TestQueueDrawScrollUpNoScrollbars [ OK ] TestScrollView.TestQueueDrawScrollUpNoScrollbars (496 ms) [ RUN ] TestScrollView.TestQueueDrawScrollDown [ OK ] TestScrollView.TestQueueDrawScrollDown (446 ms) [ RUN ] TestScrollView.TestQueueDrawScrollUp Segmentation fault (core dumped) make[3]: *** [Makefile:2670: check-headless] Error 139 make[3]: Leaving directory '/<>/tests' make[2]: *** [Makefile:1061: check-headless] Error 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nux/+bug/2054351/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2054350] Re: nux ftbfs from source, failing test
** Changed in: nux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to nux in Ubuntu. https://bugs.launchpad.net/bugs/2054350 Title: nux ftbfs from source, failing test Status in nux package in Ubuntu: Confirmed Bug description: seen in noble, all architectures: [--] 1 test from TestLoggingWriter [ RUN ] TestLoggingWriter.TestWriteMessage gtest-nuxcore-logger.cpp:171: Failure Value of: result Expected: is equal to 0x5d40f0 pointing to "ERROR 2010-09-10 06:34:45 test.module testfile.cpp:1234 my message\n" Actual: "ERROR 2010-09-10 07:34:45 test.module testfile.cpp:1234 my message\n" [ FAILED ] TestLoggingWriter.TestWriteMessage (0 ms) [--] 1 test from TestLoggingWriter (0 ms total) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nux/+bug/2054350/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2054350] [NEW] nux ftbfs from source, failing test
Public bug reported: seen in noble, all architectures: [--] 1 test from TestLoggingWriter [ RUN ] TestLoggingWriter.TestWriteMessage gtest-nuxcore-logger.cpp:171: Failure Value of: result Expected: is equal to 0x5d40f0 pointing to "ERROR 2010-09-10 06:34:45 test.module testfile.cpp:1234 my message\n" Actual: "ERROR 2010-09-10 07:34:45 test.module testfile.cpp:1234 my message\n" [ FAILED ] TestLoggingWriter.TestWriteMessage (0 ms) [--] 1 test from TestLoggingWriter (0 ms total) ** Affects: nux (Ubuntu) Importance: Undecided Status: New ** Tags: ftbfs rls-nn-incoming ** Tags added: ftbfs rls-nn-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to nux in Ubuntu. https://bugs.launchpad.net/bugs/2054350 Title: nux ftbfs from source, failing test Status in nux package in Ubuntu: New Bug description: seen in noble, all architectures: [--] 1 test from TestLoggingWriter [ RUN ] TestLoggingWriter.TestWriteMessage gtest-nuxcore-logger.cpp:171: Failure Value of: result Expected: is equal to 0x5d40f0 pointing to "ERROR 2010-09-10 06:34:45 test.module testfile.cpp:1234 my message\n" Actual: "ERROR 2010-09-10 07:34:45 test.module testfile.cpp:1234 my message\n" [ FAILED ] TestLoggingWriter.TestWriteMessage (0 ms) [--] 1 test from TestLoggingWriter (0 ms total) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nux/+bug/2054350/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1815094] Re: [FTBFS] cast between incompatible function types from ‘bool (*)(nux::TextEntry*)’ to ‘GSourceFunc’ gcc >= 8.1 (Disco)
disco is EOL ** Changed in: nux (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to nux in Ubuntu. https://bugs.launchpad.net/bugs/1815094 Title: [FTBFS] cast between incompatible function types from ‘bool (*)(nux::TextEntry*)’ to ‘GSourceFunc’ gcc >= 8.1 (Disco) Status in nux package in Ubuntu: Invalid Bug description: In disco it doesn't compile. I get cast between incompatible function types from ‘bool (*)(nux::TextEntry*)’ to ‘GSourceFunc’ Either we should build it with -Wextra -Wno-cast-function-type in configure.ac or fix pointer to function for g++ > 8.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nux/+bug/1815094/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1570894] Re: s390x build failure
builds
** Changed in: nux (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to nux in Ubuntu.
https://bugs.launchpad.net/bugs/1570894
Title:
s390x build failure
Status in nux package in Ubuntu:
Fix Released
Bug description:
poking s390x build failure:
Executing gtest-nuxgraphics under dummy xserver results in illigel
instructions:
# .libs/gtest-nuxgraphics
[==] Running 9 tests from 2 test cases.
[--] Global test environment set-up.
[--] 8 tests from TestTextures
[ RUN ] TestTextures.TestTextureSizes
Illegal instruction (core dumped)
Program received signal SIGILL, Illegal instruction.
0x03fffdf2e53a in nux::NThreadSafeCounter::Increment (this=0x3fffdf53f2e
) at ThreadGNU.cpp:31
31return __sync_add_and_fetch (&m_Counter, 1);
(gdb) backtrace full
#0 0x03fffdf2e53a in nux::NThreadSafeCounter::Increment
(this=0x3fffdf53f2e ) at ThreadGNU.cpp:31
No locals.
But there is nothing special in ThreadGNU.cpp:31 it simply does:
int NThreadSafeCounter::Increment()
{
return __sync_add_and_fetch (&m_Counter, 1);
}
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nux/+bug/1570894/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2051997] Re: bdebstrap fails to build with python3-defaults 3.12
** Changed in: python3-defaults (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python3-defaults in
Ubuntu.
https://bugs.launchpad.net/bugs/2051997
Title:
bdebstrap fails to build with python3-defaults 3.12
Status in bdebstrap package in Ubuntu:
Fix Released
Status in python3-defaults package in Ubuntu:
Invalid
Status in bdebstrap package in Debian:
New
Bug description:
When building bdebstrap with python3-default 3.12 the following error occurs
--
usr/bin/python3.12 -m pylint --rcfile=/<>/tests/pylint.conf --
/<>/bdebstrap tests /<>/setup.py
FAIL
test_flake8 (tests.test_shellcheck.ShellcheckTestCase.test_flake8)
Test: Run shellcheck on Shell source code. ... Running following command:
shellcheck /<>/hooks/disable-units
/<>/hooks/enable-units
ok
==
FAIL: test_pylint (tests.test_pylint.PylintTestCase.test_pylint)
Test: Run pylint on Python source code.
--
Traceback (most recent call last):
File "/<>/tests/test_pylint.py", line 74, in test_pylint
self.fail("\n".join(msgs))
AssertionError: pylint found issues:
* Module setup
/<>/setup.py:26:0: E0401: Unable to import 'distutils.log'
(import-error)
/<>/setup.py:27:0: E0401: Unable to import
'distutils.command.build' (import-error)
/<>/setup.py:28:0: E0401: Unable to import
'distutils.command.clean' (import-error)
/<>/setup.py:57:4: C0116: Missing function or method docstring
(missing-function-docstring)
/<>/setup.py:54:0: R0903: Too few public methods (1/2)
(too-few-public-methods)
/<>/setup.py:65:4: C0116: Missing function or method docstring
(missing-function-docstring)
/<>/setup.py:62:0: R0903: Too few public methods (1/2)
(too-few-public-methods)
--
due to removal of distutils in python 3.12
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bdebstrap/+bug/2051997/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2051990] Re: python3-defaults 3.12 causes aubio to fail to build from source
** Changed in: python3-defaults (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python3-defaults in
Ubuntu.
https://bugs.launchpad.net/bugs/2051990
Title:
python3-defaults 3.12 causes aubio to fail to build from source
Status in aubio package in Ubuntu:
Fix Released
Status in python3-defaults package in Ubuntu:
Invalid
Status in aubio package in Debian:
New
Bug description:
python3 ./waf configure --verbose --destdir=debian/tmp --prefix=/usr
--enable-fftw3f --libdir=/usr/lib/x86_64-linux-gnu
/<>/waflib/Utils.py:443: SyntaxWarning: invalid escape sequence
'\d'
return re.split('\d+$',s)[0]
/<>/waflib/ConfigSet.py:7: SyntaxWarning: invalid escape
sequence '\ '
re_imp=re.compile('^(#)*?([^#=]*?)\ =\ (.*?)$',re.M)
/<>/waflib/ansiterm.py:178: SyntaxWarning: invalid escape
sequence '\['
ansi_tokens=re.compile('(?:\x1b\[([0-9?;]*)([a-zA-Z])|([^\x1b]+))')
Traceback (most recent call last):
File "/<>/./waf", line 164, in
from waflib import Scripting
File "/<>/waflib/Scripting.py", line 7, in
from waflib import
Utils,Configure,Logs,Options,ConfigSet,Context,Errors,Build,Node
File "/<>/waflib/Configure.py", line 6, in
from waflib import ConfigSet,Utils,Options,Logs,Context,Build,Errors
File "/<>/waflib/Options.py", line 6, in
from waflib import Logs,Utils,Context,Errors
File "/<>/waflib/Context.py", line 5, in
import os,re,imp,sys
ModuleNotFoundError: No module named 'imp'
make[1]: *** [debian/rules:45: override_dh_auto_configure] Error 1
make[1]: Leaving directory '/<>'
make: *** [debian/rules:22: binary] Error 2
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status
2
Build finished at 2024-02-01T21:23:22Z
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/aubio/+bug/2051990/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2051540] Re: ufw ftbfs with Python 3.12 as default
better, but still not complete:
1186s autopkgtest [04:54:38]: test root-unittest: [---
1186s Interpreter: python3
1186s
1186s rm -rf ./build
1186s rm -rf ./staging
1186s rm -rf ./tests/testarea ./tests/unit/tmp
1186s rm -rf ./tmp
1186s rm -rf ./snap-build
1186s rm -rf ./parts ./stage ./prime
1186s rm -f ./locales/mo/*.mo
1186s rm -f ./tests/unit/*.pyc ./tests/*.pyc ./src/*.pyc
1186s rm -rf ./tests/unit/__pycache__ ./tests/__pycache__ ./src/__pycache__
1186s rm -rf ./.coverage
1186s rm -f ./ufw # unittest symlink
1186s = Functional Tests =
1186s net.ipv4.ip_forward = 0
1186s net.ipv6.conf.default.forwarding = 0
1186s net.ipv6.conf.all.forwarding = 0
1186s
1186s Performing tests 'root/bugs'
1186s - installing
1187s Traceback (most recent call last):
1187s File "/tmp/autopkgtest.qdhyuB/build.T34/src/./setup.py", line 28, in
1187s from distutils.command.install import install as _install
1187s ModuleNotFoundError: No module named 'distutils'
** Changed in: ufw (Ubuntu)
Status: Fix Released => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ufw in Ubuntu.
https://bugs.launchpad.net/bugs/2051540
Title:
ufw ftbfs with Python 3.12 as default
Status in ufw:
Fix Committed
Status in ufw package in Ubuntu:
Confirmed
Status in ufw package in Debian:
Fix Released
Bug description:
==
ERROR: test_ufwcommand_parse
(tests.unit.test_parser.ParserTestCase.test_ufwcommand_parse)
Test UFWCommand.parse()
--
Traceback (most recent call last):
File "/<>/tests/unit/test_parser.py", line 88, in
test_ufwcommand_parse
self.assertEquals('status', pr.action, "%s != 'status'" % (pr.action))
^
AttributeError: 'ParserTestCase' object has no attribute 'assertEquals'. Did
you mean: 'assertEqual'?
==
ERROR: test_ufwcommand_rule_get_command
(tests.unit.test_parser.ParserTestCase.test_ufwcommand_rule_get_command)
Test UFWCommand(Route)Rule.get_command()
--
Traceback (most recent call last):
File "/<>/tests/unit/test_parser.py", line 375, in
test_ufwcommand_rule_get_command
self.assertEquals(len(errors), 0,
^
AttributeError: 'ParserTestCase' object has no attribute 'assertEquals'. Did
you mean: 'assertEqual'?
--
Ran 24 tests in 7.584s
FAILED (errors=9)
test_skeleton
test_example (tests.unit.test_skeleton.SkeletonTestCase.test_example)
Test example dummy test ... ok
--
Ran 1 test in 0.000s
OK
To manage notifications about this bug go to:
https://bugs.launchpad.net/ufw/+bug/2051540/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2051997] Re: bdebstrap fails to build with python3-defaults 3.12
NMUed
** Changed in: bdebstrap (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python3-defaults in
Ubuntu.
https://bugs.launchpad.net/bugs/2051997
Title:
bdebstrap fails to build with python3-defaults 3.12
Status in bdebstrap package in Ubuntu:
In Progress
Status in python3-defaults package in Ubuntu:
New
Status in bdebstrap package in Debian:
Unknown
Bug description:
When building bdebstrap with python3-default 3.12 the following error occurs
--
usr/bin/python3.12 -m pylint --rcfile=/<>/tests/pylint.conf --
/<>/bdebstrap tests /<>/setup.py
FAIL
test_flake8 (tests.test_shellcheck.ShellcheckTestCase.test_flake8)
Test: Run shellcheck on Shell source code. ... Running following command:
shellcheck /<>/hooks/disable-units
/<>/hooks/enable-units
ok
==
FAIL: test_pylint (tests.test_pylint.PylintTestCase.test_pylint)
Test: Run pylint on Python source code.
--
Traceback (most recent call last):
File "/<>/tests/test_pylint.py", line 74, in test_pylint
self.fail("\n".join(msgs))
AssertionError: pylint found issues:
* Module setup
/<>/setup.py:26:0: E0401: Unable to import 'distutils.log'
(import-error)
/<>/setup.py:27:0: E0401: Unable to import
'distutils.command.build' (import-error)
/<>/setup.py:28:0: E0401: Unable to import
'distutils.command.clean' (import-error)
/<>/setup.py:57:4: C0116: Missing function or method docstring
(missing-function-docstring)
/<>/setup.py:54:0: R0903: Too few public methods (1/2)
(too-few-public-methods)
/<>/setup.py:65:4: C0116: Missing function or method docstring
(missing-function-docstring)
/<>/setup.py:62:0: R0903: Too few public methods (1/2)
(too-few-public-methods)
--
due to removal of distutils in python 3.12
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bdebstrap/+bug/2051997/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2051990] Re: python3-defaults 3.12 causes aubio to fail to build from source
NMUed in Debian
** Changed in: aubio (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python3-defaults in
Ubuntu.
https://bugs.launchpad.net/bugs/2051990
Title:
python3-defaults 3.12 causes aubio to fail to build from source
Status in aubio package in Ubuntu:
In Progress
Status in python3-defaults package in Ubuntu:
New
Status in aubio package in Debian:
New
Bug description:
python3 ./waf configure --verbose --destdir=debian/tmp --prefix=/usr
--enable-fftw3f --libdir=/usr/lib/x86_64-linux-gnu
/<>/waflib/Utils.py:443: SyntaxWarning: invalid escape sequence
'\d'
return re.split('\d+$',s)[0]
/<>/waflib/ConfigSet.py:7: SyntaxWarning: invalid escape
sequence '\ '
re_imp=re.compile('^(#)*?([^#=]*?)\ =\ (.*?)$',re.M)
/<>/waflib/ansiterm.py:178: SyntaxWarning: invalid escape
sequence '\['
ansi_tokens=re.compile('(?:\x1b\[([0-9?;]*)([a-zA-Z])|([^\x1b]+))')
Traceback (most recent call last):
File "/<>/./waf", line 164, in
from waflib import Scripting
File "/<>/waflib/Scripting.py", line 7, in
from waflib import
Utils,Configure,Logs,Options,ConfigSet,Context,Errors,Build,Node
File "/<>/waflib/Configure.py", line 6, in
from waflib import ConfigSet,Utils,Options,Logs,Context,Build,Errors
File "/<>/waflib/Options.py", line 6, in
from waflib import Logs,Utils,Context,Errors
File "/<>/waflib/Context.py", line 5, in
import os,re,imp,sys
ModuleNotFoundError: No module named 'imp'
make[1]: *** [debian/rules:45: override_dh_auto_configure] Error 1
make[1]: Leaving directory '/<>'
make: *** [debian/rules:22: binary] Error 2
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status
2
Build finished at 2024-02-01T21:23:22Z
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/aubio/+bug/2051990/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2051997] Re: bdebstrap fails to build with python3-defaults 3.12
** Bug watch added: Debian Bug tracker #1061735
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061735
** Also affects: bdebstrap (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061735
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python3-defaults in
Ubuntu.
https://bugs.launchpad.net/bugs/2051997
Title:
bdebstrap fails to build with python3-defaults 3.12
Status in bdebstrap package in Ubuntu:
New
Status in python3-defaults package in Ubuntu:
New
Status in bdebstrap package in Debian:
Unknown
Bug description:
When building bdebstrap with python3-default 3.12 the following error occurs
--
usr/bin/python3.12 -m pylint --rcfile=/<>/tests/pylint.conf --
/<>/bdebstrap tests /<>/setup.py
FAIL
test_flake8 (tests.test_shellcheck.ShellcheckTestCase.test_flake8)
Test: Run shellcheck on Shell source code. ... Running following command:
shellcheck /<>/hooks/disable-units
/<>/hooks/enable-units
ok
==
FAIL: test_pylint (tests.test_pylint.PylintTestCase.test_pylint)
Test: Run pylint on Python source code.
--
Traceback (most recent call last):
File "/<>/tests/test_pylint.py", line 74, in test_pylint
self.fail("\n".join(msgs))
AssertionError: pylint found issues:
* Module setup
/<>/setup.py:26:0: E0401: Unable to import 'distutils.log'
(import-error)
/<>/setup.py:27:0: E0401: Unable to import
'distutils.command.build' (import-error)
/<>/setup.py:28:0: E0401: Unable to import
'distutils.command.clean' (import-error)
/<>/setup.py:57:4: C0116: Missing function or method docstring
(missing-function-docstring)
/<>/setup.py:54:0: R0903: Too few public methods (1/2)
(too-few-public-methods)
/<>/setup.py:65:4: C0116: Missing function or method docstring
(missing-function-docstring)
/<>/setup.py:62:0: R0903: Too few public methods (1/2)
(too-few-public-methods)
--
due to removal of distutils in python 3.12
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bdebstrap/+bug/2051997/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2051540] Re: ufw ftbfs with Python 3.12 as default
** Changed in: ufw (Ubuntu)
Status: In Progress => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ufw in Ubuntu.
https://bugs.launchpad.net/bugs/2051540
Title:
ufw ftbfs with Python 3.12 as default
Status in ufw:
Fix Committed
Status in ufw package in Ubuntu:
Confirmed
Status in ufw package in Debian:
Fix Released
Bug description:
==
ERROR: test_ufwcommand_parse
(tests.unit.test_parser.ParserTestCase.test_ufwcommand_parse)
Test UFWCommand.parse()
--
Traceback (most recent call last):
File "/<>/tests/unit/test_parser.py", line 88, in
test_ufwcommand_parse
self.assertEquals('status', pr.action, "%s != 'status'" % (pr.action))
^
AttributeError: 'ParserTestCase' object has no attribute 'assertEquals'. Did
you mean: 'assertEqual'?
==
ERROR: test_ufwcommand_rule_get_command
(tests.unit.test_parser.ParserTestCase.test_ufwcommand_rule_get_command)
Test UFWCommand(Route)Rule.get_command()
--
Traceback (most recent call last):
File "/<>/tests/unit/test_parser.py", line 375, in
test_ufwcommand_rule_get_command
self.assertEquals(len(errors), 0,
^
AttributeError: 'ParserTestCase' object has no attribute 'assertEquals'. Did
you mean: 'assertEqual'?
--
Ran 24 tests in 7.584s
FAILED (errors=9)
test_skeleton
test_example (tests.unit.test_skeleton.SkeletonTestCase.test_example)
Test example dummy test ... ok
--
Ran 1 test in 0.000s
OK
To manage notifications about this bug go to:
https://bugs.launchpad.net/ufw/+bug/2051540/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2051541] [NEW] unattended-upgrades ftbfs with Python 3.12 as default
Public bug reported: [...] Running ./test_pep484.py with python3 s -- Ran 0 tests in 0.000s NO TESTS RAN (skipped=1) make[2]: *** [Makefile:9: check] Error 5 make[2]: Leaving directory '/<>/test' make[1]: *** [debian/rules:16: override_dh_auto_test] Error 2 5 is a new exit value when all tests are skipped. ** Affects: unattended-upgrades (Ubuntu) Importance: High Status: Confirmed ** Tags: ftbfs rls-nn-incoming ** Changed in: unattended-upgrades (Ubuntu) Status: New => Confirmed ** Changed in: unattended-upgrades (Ubuntu) Importance: Undecided => High ** Tags added: ftbfs rls-nn-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/2051541 Title: unattended-upgrades ftbfs with Python 3.12 as default Status in unattended-upgrades package in Ubuntu: Confirmed Bug description: [...] Running ./test_pep484.py with python3 s -- Ran 0 tests in 0.000s NO TESTS RAN (skipped=1) make[2]: *** [Makefile:9: check] Error 5 make[2]: Leaving directory '/<>/test' make[1]: *** [debian/rules:16: override_dh_auto_test] Error 2 5 is a new exit value when all tests are skipped. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/2051541/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2051540] [NEW] ufw ftbfs with Python 3.12 as default
Public bug reported:
==
ERROR: test_ufwcommand_parse
(tests.unit.test_parser.ParserTestCase.test_ufwcommand_parse)
Test UFWCommand.parse()
--
Traceback (most recent call last):
File "/<>/tests/unit/test_parser.py", line 88, in
test_ufwcommand_parse
self.assertEquals('status', pr.action, "%s != 'status'" % (pr.action))
^
AttributeError: 'ParserTestCase' object has no attribute 'assertEquals'. Did
you mean: 'assertEqual'?
==
ERROR: test_ufwcommand_rule_get_command
(tests.unit.test_parser.ParserTestCase.test_ufwcommand_rule_get_command)
Test UFWCommand(Route)Rule.get_command()
--
Traceback (most recent call last):
File "/<>/tests/unit/test_parser.py", line 375, in
test_ufwcommand_rule_get_command
self.assertEquals(len(errors), 0,
^
AttributeError: 'ParserTestCase' object has no attribute 'assertEquals'. Did
you mean: 'assertEqual'?
--
Ran 24 tests in 7.584s
FAILED (errors=9)
test_skeleton
test_example (tests.unit.test_skeleton.SkeletonTestCase.test_example)
Test example dummy test ... ok
--
Ran 1 test in 0.000s
OK
** Affects: ufw (Ubuntu)
Importance: High
Status: Confirmed
** Tags: ftbfs rls-nn-incoming
** Changed in: ufw (Ubuntu)
Status: New => Confirmed
** Changed in: ufw (Ubuntu)
Importance: Undecided => High
** Tags added: ftbfs rls-nn-incoming
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ufw in Ubuntu.
https://bugs.launchpad.net/bugs/2051540
Title:
ufw ftbfs with Python 3.12 as default
Status in ufw package in Ubuntu:
Confirmed
Bug description:
==
ERROR: test_ufwcommand_parse
(tests.unit.test_parser.ParserTestCase.test_ufwcommand_parse)
Test UFWCommand.parse()
--
Traceback (most recent call last):
File "/<>/tests/unit/test_parser.py", line 88, in
test_ufwcommand_parse
self.assertEquals('status', pr.action, "%s != 'status'" % (pr.action))
^
AttributeError: 'ParserTestCase' object has no attribute 'assertEquals'. Did
you mean: 'assertEqual'?
==
ERROR: test_ufwcommand_rule_get_command
(tests.unit.test_parser.ParserTestCase.test_ufwcommand_rule_get_command)
Test UFWCommand(Route)Rule.get_command()
--
Traceback (most recent call last):
File "/<>/tests/unit/test_parser.py", line 375, in
test_ufwcommand_rule_get_command
self.assertEquals(len(errors), 0,
^
AttributeError: 'ParserTestCase' object has no attribute 'assertEquals'. Did
you mean: 'assertEqual'?
--
Ran 24 tests in 7.584s
FAILED (errors=9)
test_skeleton
test_example (tests.unit.test_skeleton.SkeletonTestCase.test_example)
Test example dummy test ... ok
--
Ran 1 test in 0.000s
OK
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ufw/+bug/2051540/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2051512] [NEW] apport ftbfs with Python 3.12 as the default
Public bug reported: debian/rules override_dh_auto_test make[1]: Entering directory '/<>' tests/run-linters --errors-only Skipping mypy tests, mypy is not installed Running pylint... * Module apport-retrace bin/apport-retrace:577:44: E0601: Using variable 'crashid' before assignment (used-before-assignment) make[1]: *** [debian/rules:23: override_dh_auto_test] Error 2 make[1]: Leaving directory '/<>' make: *** [debian/rules:4: binary] Error 2 ** Affects: apport (Ubuntu) Importance: High Status: Confirmed ** Tags: ftbfs rls-nn-incoming ** Changed in: apport (Ubuntu) Status: New => Confirmed ** Changed in: apport (Ubuntu) Importance: Undecided => High ** Tags added: ftbfs rls-nn-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/2051512 Title: apport ftbfs with Python 3.12 as the default Status in apport package in Ubuntu: Confirmed Bug description: debian/rules override_dh_auto_test make[1]: Entering directory '/<>' tests/run-linters --errors-only Skipping mypy tests, mypy is not installed Running pylint... * Module apport-retrace bin/apport-retrace:577:44: E0601: Using variable 'crashid' before assignment (used-before-assignment) make[1]: *** [debian/rules:23: override_dh_auto_test] Error 2 make[1]: Leaving directory '/<>' make: *** [debian/rules:4: binary] Error 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2051512/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2015243] Re: py3versions doesn't follow symlinks (like realpath)
The python3 symlink is not meant to be handled by alternatives. ** Changed in: python3-defaults (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/2015243 Title: py3versions doesn't follow symlinks (like realpath) Status in python3-defaults package in Ubuntu: Invalid Bug description: In case if we have more than one python version and manage them by update-alternatives, the path to the python binary looks like: root@devvm-14-143:~# ls -la /usr/bin/python3 lrwxrwxrwx 1 root root 25 Apr 4 08:11 /usr/bin/python3 -> /etc/alternatives/python3 root@devvm-14-143:~# ls -la /etc/alternatives/python3 lrwxrwxrwx 1 root root 18 Apr 4 08:11 /etc/alternatives/python3 -> /usr/bin/python3.8 So even we use the correct default version of python3 (like in Focal it is python3.8) py3version will fail root@devvm-14-143:~# py3versions -d py3versions: the symlink /usr/bin/python3 does not point to the python3 default version. It must be reset to point to python3.8 This caused due to os.readlink doesn't follow multiply symlinks, so I suggest to use Path from pathlib. I have attached patch with suggested changes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/2015243/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2049369] [NEW] autopkg tests ignored for migration of python3-defaults adding 3.12
Public bug reported: autopkg tests ignored for migration of python3-defaults adding 3.12: These are the autopkg tests for packages, which we'll ignore for the initial migration of python3-defaults adding 3.12. ** Affects: python3-defaults (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/2049369 Title: autopkg tests ignored for migration of python3-defaults adding 3.12 Status in python3-defaults package in Ubuntu: New Bug description: autopkg tests ignored for migration of python3-defaults adding 3.12: These are the autopkg tests for packages, which we'll ignore for the initial migration of python3-defaults adding 3.12. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/2049369/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1775994] Re: package libbinutils:amd64 2.30-20ubuntu2~18.04 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting con
not a binutils issue, please reinstall, as the error message says ** Changed in: binutils (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1775994 Title: package libbinutils:amd64 2.30-20ubuntu2~18.04 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in binutils package in Ubuntu: Invalid Bug description: as I opened the laptop, I got this bug error ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libbinutils:amd64 2.30-20ubuntu2~18.04 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 AptOrdering: binutils:amd64: Install binutils-common:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Sat Jun 9 02:55:07 2018 Dependencies: binutils-common 2.30-20ubuntu2~18.04 gcc-8-base 8-20180414-1ubuntu2 libc6 2.27-3ubuntu1 libgcc1 1:8-20180414-1ubuntu2 zlib1g 1:1.2.11.dfsg-0ubuntu2 DuplicateSignature: package:libbinutils:amd64:2.30-20ubuntu2~18.04 Processing triggers for man-db (2.8.3-2) ... dpkg: error processing package libbinutils:amd64 (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2018-05-31 (9 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: binutils Title: package libbinutils:amd64 2.30-20ubuntu2~18.04 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1775994/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1918462] Re: package libbinutils:amd64 2.34-6ubuntu1.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configur
this is not a binutils issue, please reinstall as the error message suggests ** Changed in: binutils (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1918462 Title: package libbinutils:amd64 2.34-6ubuntu1.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in binutils package in Ubuntu: Invalid Bug description: It gives error since 2 weeks in every turning on of computer ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libbinutils:amd64 2.34-6ubuntu1.1 ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 AptOrdering: linux-libc-dev:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Mar 10 08:19:53 2021 DuplicateSignature: package:libbinutils:amd64:2.34-6ubuntu1.1 Setting up linux-libc-dev:amd64 (5.4.0-66.74) ... dpkg: error processing package libbinutils:amd64 (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2020-09-28 (162 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.4 SourcePackage: binutils Title: package libbinutils:amd64 2.34-6ubuntu1.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1918462/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1977958] Re: binutils: addr2line: getting error "DWARF error: section .debug_str is larger than its filesize" when building Android 8.1 on Ubuntu 20.04
closing as won't fix for 20.04 LTS ** Changed in: binutils (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1977958 Title: binutils: addr2line: getting error "DWARF error: section .debug_str is larger than its filesize" when building Android 8.1 on Ubuntu 20.04 Status in binutils package in Ubuntu: Won't Fix Bug description: Getting the error "DWARF error: section .debug_str is larger than its filesize" when building an Android app. This is traced back to a security fix introduced in version 2.34-6ubuntu1.3 of binutils. Reverting to 2.34-6ubuntu1 resolves the issue temporarily, but the fix is to allow for .debug_str sizes up to 10x larger than the file size (because of compression). It looks like this fix was made already for Ubuntu 22.04 (binutils 2.38), but has not been backported to 20.04. More detail on the issue and fix is available here: https://sourceware.org/bugzilla/show_bug.cgi?id=28834 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1977958/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1824249] Re: package binutils-multiarch (not installed) [modified: usr/bin/x86_64-linux-gnu-addr2line usr/bin/x86_64-linux-gnu-ar usr/bin/x86_64-linux-gnu-gprof usr/bin/x86_64-li
please remove the package, and re-install it ** Changed in: binutils (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1824249 Title: package binutils-multiarch (not installed) [modified: usr/bin/x86_64-linux-gnu-addr2line usr/bin/x86_64-linux-gnu-ar usr/bin/x86_64-linux-gnu-gprof usr/bin/x86_64-linux-gnu-nm usr/bin/x86_64-linux-gnu-objcopy usr/bin/x86_64-linux-gnu-objdump usr/bin/x86_64-linux-gnu-ranlib usr/bin/x86_64-linux-gnu-readelf usr/bin/x86_64-linux-gnu-size usr/bin/x86_64-linux-gnu-strings usr/bin/x86_64-linux-gnu-strip] failed to install/upgrade: new binutils-multiarch package pre-installation script subprocess returned error exit status 2 Status in binutils package in Ubuntu: Invalid Bug description: non si riesce ad installare multiarch e binutils ProblemType: Package DistroRelease: Ubuntu 18.10 Package: binutils-multiarch (not installed) [modified: usr/bin/x86_64-linux-gnu-addr2line usr/bin/x86_64-linux-gnu-ar usr/bin/x86_64-linux-gnu-gprof usr/bin/x86_64-linux-gnu-nm usr/bin/x86_64-linux-gnu-objcopy usr/bin/x86_64-linux-gnu-objdump usr/bin/x86_64-linux-gnu-ranlib usr/bin/x86_64-linux-gnu-readelf usr/bin/x86_64-linux-gnu-size usr/bin/x86_64-linux-gnu-strings usr/bin/x86_64-linux-gnu-strip] ProcVersionSignature: Ubuntu 4.18.0-18.19-generic 4.18.20 Uname: Linux 4.18.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu13.3 Architecture: amd64 Date: Wed Apr 10 20:39:45 2019 ErrorMessage: new binutils-multiarch package pre-installation script subprocess returned error exit status 2 InstallationDate: Installed on 2019-04-09 (1 days ago) InstallationMedia: Lubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.10 PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15-3 RelatedPackageVersions: dpkg 1.19.0.5ubuntu5 apt 1.7.4 SourcePackage: binutils Title: package binutils-multiarch (not installed) [modified: usr/bin/x86_64-linux-gnu-addr2line usr/bin/x86_64-linux-gnu-ar usr/bin/x86_64-linux-gnu-gprof usr/bin/x86_64-linux-gnu-nm usr/bin/x86_64-linux-gnu-objcopy usr/bin/x86_64-linux-gnu-objdump usr/bin/x86_64-linux-gnu-ranlib usr/bin/x86_64-linux-gnu-readelf usr/bin/x86_64-linux-gnu-size usr/bin/x86_64-linux-gnu-strings usr/bin/x86_64-linux-gnu-strip] failed to install/upgrade: new binutils-multiarch package pre-installation script subprocess returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1824249/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2025564] Re: package binutils-common 2.40-2ubuntu4.1 failed to install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error exit status 2
this is not a binutils issue. try to re-donwload your updates ** Changed in: binutils (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/2025564 Title: package binutils-common 2.40-2ubuntu4.1 failed to install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error exit status 2 Status in binutils package in Ubuntu: Invalid Bug description: Appeared on apt update. ProblemType: Package DistroRelease: Ubuntu 23.04 Package: binutils-common 2.40-2ubuntu4.1 ProcVersionSignature: Ubuntu 6.2.0-24.24-generic 6.2.12 Uname: Linux 6.2.0-24-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass Date: Sun Jul 2 12:15:47 2023 Dependencies: DpkgHistoryLog: Start-Date: 2023-07-02 12:15:46 Commandline: /usr/bin/unattended-upgrade Upgrade: libctf-nobfd0:amd64 (2.40-2ubuntu4, 2.40-2ubuntu4.1), libbinutils:amd64 (2.40-2ubuntu4, 2.40-2ubuntu4.1), binutils-x86-64-linux-gnu:amd64 (2.40-2ubuntu4, 2.40-2ubuntu4.1), libctf0:amd64 (2.40-2ubuntu4, 2.40-2ubuntu4.1), binutils-common:amd64 (2.40-2ubuntu4, 2.40-2ubuntu4.1), libgprofng0:amd64 (2.40-2ubuntu4, 2.40-2ubuntu4.1), binutils:amd64 (2.40-2ubuntu4, 2.40-2ubuntu4.1) DuplicateSignature: package:binutils-common:2.40-2ubuntu4.1 Unpacking binutils (2.40-2ubuntu4.1) over (2.40-2ubuntu4) ... dpkg-deb: error: failed to read archive '/tmp/apt-dpkg-install-sp1YtE/5-binutils_2.40-2ubuntu4.1_amd64.deb': No such file or directory dpkg: error processing archive /tmp/apt-dpkg-install-sp1YtE/5-binutils_2.40-2ubuntu4.1_amd64.deb (--unpack): dpkg-deb --fsys-tarfile subprocess returned error exit status 2 ErrorMessage: dpkg-deb --fsys-tarfile subprocess returned error exit status 2 InstallationDate: Installed on 2021-12-21 (557 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211220) Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.21ubuntu1 apt 2.6.0 SourcePackage: binutils Title: package binutils-common 2.40-2ubuntu4.1 failed to install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error exit status 2 UpgradeStatus: Upgraded to lunar on 2023-04-20 (72 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/2025564/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2029525] Re: binutils-i686-linux-gnu not provided for riscv64
we currently don't build cross compilers on riscv64, because it slows down the toolchain updates. That might change, if we have native hardware for our buildds. ** Changed in: binutils (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/2029525 Title: binutils-i686-linux-gnu not provided for riscv64 Status in binutils package in Ubuntu: Confirmed Bug description: Currently i686 binutils package is provided for the following arches: amd64 arm64 i386 ppc64el It is required for cross-compilation, but it is currently not provided for riscv64, so on that platform I can't cross-compile. Please consider providing binutils-i686-linux-gnu for riscv64. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/2029525/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2039149] Re: readelf riscv unknown
please provide a test case ** Changed in: binutils (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/2039149 Title: readelf riscv unknown Status in binutils package in Ubuntu: Incomplete Bug description: 1) Description: Ubuntu 22.04.3 LTS Release: 22.04 2) binutils: Installed: 2.38-4ubuntu2.3 Candidate: 2.38-4ubuntu2.3 Version table: *** 2.38-4ubuntu2.3 500 500 http://be.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages 100 /var/lib/dpkg/status 2.38-3ubuntu1 500 500 http://be.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 3) I'm hand assembling an ELF file and the readelf utility in the binutils package doesn't recognize riscv which is the e_machine 243. LoongArch or 258 and x86 or 3 are recognized, for example. But not riscv. 4) Readelf states that 243 is an unknown e_machine. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: binutils 2.38-4ubuntu2.3 ProcVersionSignature: Ubuntu 6.2.0-34.34~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-34-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Thu Oct 12 10:14:30 2023 InstallationDate: Installed on 2023-07-12 (91 days ago) InstallationMedia: Xubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) SourcePackage: binutils UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/2039149/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2044506] [NEW] issues on armhf with -fstack-clash-protection
Public bug reported: TBD ** Affects: gnutls28 (Ubuntu) Importance: Undecided Status: New ** Affects: libarchive (Ubuntu) Importance: Undecided Status: New ** Affects: libselinux (Ubuntu) Importance: Undecided Status: New ** Affects: libxml2 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libselinux in Ubuntu. https://bugs.launchpad.net/bugs/2044506 Title: issues on armhf with -fstack-clash-protection Status in gnutls28 package in Ubuntu: New Status in libarchive package in Ubuntu: New Status in libselinux package in Ubuntu: New Status in libxml2 package in Ubuntu: New Bug description: TBD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnutls28/+bug/2044506/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2037205] Re: setuptools: FTBFS in mantic
** Changed in: setuptools (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dh-python in Ubuntu. https://bugs.launchpad.net/bugs/2037205 Title: setuptools: FTBFS in mantic Status in dh-python package in Ubuntu: New Status in setuptools package in Ubuntu: Fix Committed Status in dh-python package in Debian: New Status in setuptools package in Debian: New Bug description: As seen in the mantic test rebuild [1], setuptools 68.1.2-1 currently FTBFS: Traceback (most recent call last): File "/<>/setuptools/config/setupcfg.py", line 284, in __setitem__ current_value = getattr(target_obj, option_name) AttributeError: 'MinimalDistribution' object has no attribute 'entry_points' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/<>/setup.py", line 92, in dist = setuptools.setup(**setup_params) File "/<>/setuptools/__init__.py", line 106, in setup _install_setup_requires(attrs) File "/<>/setuptools/__init__.py", line 77, in _install_setup_requires dist.parse_config_files(ignore_option_errors=True) File "/<>/setuptools/dist.py", line 895, in parse_config_files setupcfg.parse_configuration( File "/<>/setuptools/config/setupcfg.py", line 177, in parse_configuration options.parse() File "/<>/setuptools/config/setupcfg.py", line 500, in parse section_parser_method(section_options) File "/<>/setuptools/config/setupcfg.py", line 727, in parse_section_entry_points self['entry_points'] = parsed File "/<>/setuptools/config/setupcfg.py", line 286, in __setitem__ raise KeyError(option_name) KeyError: 'entry_points' E: pybuild pybuild:395: clean: plugin distutils failed with: exit code=1: python3.11 setup.py clean [1] https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20230830-mantic-mantic.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dh-python/+bug/2037205/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1943818] Re: mesa built with -O3 on ppc64el has broken EGL
is that still the case with recent compiler versions? ** Changed in: gcc-11 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1943818 Title: mesa built with -O3 on ppc64el has broken EGL Status in Mesa: New Status in The Ubuntu-power-systems project: New Status in gcc-11 package in Ubuntu: Incomplete Status in mesa package in Ubuntu: Confirmed Bug description: If mesa is built with -O3 then EGL will fail with: libEGL warning: DRI2: failed to create any config this can be easily reproduced by building libepoxy which then runs a series of tests. The same is fine on amd64, and also ppc64el is fine with gcc-10 and -O3. To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1943818/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2022845] Re: SRU: update binutils to the 2.38 branch and ignore lto-wrapper warnings
after retries, all the autopkg tests pass, binutils test results don't show regressions. ** Tags removed: verification-needed verification-needed-jammy ** Tags added: verification-done verification-done-jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/2022845 Title: SRU: update binutils to the 2.38 branch and ignore lto-wrapper warnings Status in binutils package in Ubuntu: New Status in binutils source package in Jammy: Fix Committed Bug description: The tests sometimes fail with spurious lto-wrapper warnings and let the build fail. Ignore these warnings, they don't matter for the test outcome. Also apply four fixes from the binutils 2.38 branch: * SRU: LP: #1982105. Update from the binutils 2.38 branch: - Fix PR ld/29435: elf: Reset alignment for each PT_LOAD segment. - PowerPC64 pcrel got relocs against local symbols. - Fix PR ld/27998: i386: Don't allow GOTOFF relocation against IFUNC symbol for PIC. - Fix PR ld/29377: x86: Properly check invalid relocation against protected symbol. * Ignore lto-wrapper warnings when running the testsuite. https://sourceware.org/bugzilla/show_bug.cgi?id=29435 https://sourceware.org/bugzilla/show_bug.cgi?id=27998 https://sourceware.org/bugzilla/show_bug.cgi?id=29377 All changes are already in 2.39 in kinetic, and 2.40 in lunar. The changes come with test cases, and pass when running the testsuite. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/2022845/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2025458] Re: SRU: rebuild libunwind with GCC 11.4
the package successfully built. All the autopkg tests from the previous comment have been retried and succeeded. ** Tags removed: verification-needed verification-needed-jammy ** Tags added: verification-done verification-done-jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libunwind in Ubuntu. https://bugs.launchpad.net/bugs/2025458 Title: SRU: rebuild libunwind with GCC 11.4 Status in libunwind package in Ubuntu: New Status in libunwind source package in Jammy: Fix Committed Bug description: Reported in LP: #1997161 after updating GCC 11 in 22.04 LTS to 11.3, and now to 11.4, linking with the static libraries provided by libunwind-dev fails with: lto1: fatal error: bytecode stream in file '/usr/lib/gcc/x86_64-linux- gnu/11/../../../x86_64-linux-gnu/libunwind-x86_64.a' generated with LTO version 11.2 instead of the expected 11.3 This happens, because gcc-11 bumped the LTO version in 11.3 (11.3.0-1ubuntu1~22.04), plus the static libraries are not stripped in the packaging. Fixes could be to change the packaging, disable the LTO build for the package, or just rebuild with the new compiler. For 22.04 LTS, the least invasive action seems to be the no-change rebuild. To verify the packages: check that the package builds with the correct compiler version, and that the tests succeed during the build. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libunwind/+bug/2025458/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2025458] Re: SRU: rebuild libunwind with GCC 11.4
** No longer affects: libunwind (Ubuntu Lunar) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libunwind in Ubuntu. https://bugs.launchpad.net/bugs/2025458 Title: SRU: rebuild libunwind with GCC 11.4 Status in libunwind package in Ubuntu: New Status in libunwind source package in Jammy: Fix Committed Bug description: Reported in LP: #1997161 after updating GCC 11 in 22.04 LTS to 11.3, and now to 11.4, linking with the static libraries provided by libunwind-dev fails with: lto1: fatal error: bytecode stream in file '/usr/lib/gcc/x86_64-linux- gnu/11/../../../x86_64-linux-gnu/libunwind-x86_64.a' generated with LTO version 11.2 instead of the expected 11.3 This happens, because gcc-11 bumped the LTO version in 11.3 (11.3.0-1ubuntu1~22.04), plus the static libraries are not stripped in the packaging. Fixes could be to change the packaging, disable the LTO build for the package, or just rebuild with the new compiler. For 22.04 LTS, the least invasive action seems to be the no-change rebuild. To verify the packages: check that the package builds with the correct compiler version, and that the tests succeed during the build. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libunwind/+bug/2025458/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1997161] Re: libunwind-dev has wrong LTO data
** Bug watch added: Debian Bug tracker #1039962 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039962 ** Also affects: libunwind (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039962 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libunwind in Ubuntu. https://bugs.launchpad.net/bugs/1997161 Title: libunwind-dev has wrong LTO data Status in libunwind package in Ubuntu: Confirmed Status in llvm-toolchain-14 package in Ubuntu: Invalid Status in libunwind source package in Jammy: New Status in libunwind package in Debian: Unknown Bug description: When linking libunwind into my program I get the following message: lto1: fatal error: bytecode stream in file '/usr/lib/gcc/x86_64-linux- gnu/11/../../../x86_64-linux-gnu/libunwind-x86_64.a' generated with LTO version 11.2 instead of the expected 11.3 LTO stands for link time optimization. My guess is that libunwind-x86_64.a in Ubuntu repositories was compiled with earlier gcc 11.2, but the gcc version on this new installation of 22.04 is 11.3. I am not certain whether the right fix is to recompile with newer compiler version, or to make the library without turning on link time optimization options. libunwind is used for debugging, so there is no obvious benefit in enabling link time optimization for this library. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libunwind/+bug/1997161/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2025458] [NEW] SRU: rebuild libunwind with GCC 11.4
Public bug reported: Reported in LP: #1997161 after updating GCC 11 in 22.04 LTS to 11.3, and now to 11.4, linking with the static libraries provided by libunwind-dev fails with: lto1: fatal error: bytecode stream in file '/usr/lib/gcc/x86_64-linux- gnu/11/../../../x86_64-linux-gnu/libunwind-x86_64.a' generated with LTO version 11.2 instead of the expected 11.3 This happens, because gcc-11 bumped the LTO version in 11.3 (11.3.0-1ubuntu1~22.04), plus the static libraries are not stripped in the packaging. Fixes could be to change the packaging, disable the LTO build for the package, or just rebuild with the new compiler. For 22.04 LTS, the least invasive action seems to be the no-change rebuild. To verify the packages: check that the package builds with the correct compiler version, and that the tests succeed during the build. ** Affects: libunwind (Ubuntu) Importance: Undecided Status: New ** Affects: libunwind (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: libunwind (Ubuntu Lunar) Importance: Undecided Status: New ** Description changed: + Reported in LP: #1997161 + after updating GCC 11 in 22.04 LTS to 11.3, and now to 11.4, linking with the static libraries provided by libunwind-dev fails with: lto1: fatal error: bytecode stream in file '/usr/lib/gcc/x86_64-linux- gnu/11/../../../x86_64-linux-gnu/libunwind-x86_64.a' generated with LTO version 11.2 instead of the expected 11.3 This happens, because gcc-11 bumped the LTO version in 11.3 (11.3.0-1ubuntu1~22.04), plus the static libraries are not stripped in the packaging. Fixes could be to change the packaging, disable the LTO build for the package, or just rebuild with the new compiler. For 22.04 LTS, the least invasive action seems to be the no-change rebuild. To verify the packages: check that the package builds with the correct compiler version, and that the tests succeed during the build. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libunwind in Ubuntu. https://bugs.launchpad.net/bugs/2025458 Title: SRU: rebuild libunwind with GCC 11.4 Status in libunwind package in Ubuntu: New Status in libunwind source package in Lunar: New Bug description: Reported in LP: #1997161 after updating GCC 11 in 22.04 LTS to 11.3, and now to 11.4, linking with the static libraries provided by libunwind-dev fails with: lto1: fatal error: bytecode stream in file '/usr/lib/gcc/x86_64-linux- gnu/11/../../../x86_64-linux-gnu/libunwind-x86_64.a' generated with LTO version 11.2 instead of the expected 11.3 This happens, because gcc-11 bumped the LTO version in 11.3 (11.3.0-1ubuntu1~22.04), plus the static libraries are not stripped in the packaging. Fixes could be to change the packaging, disable the LTO build for the package, or just rebuild with the new compiler. For 22.04 LTS, the least invasive action seems to be the no-change rebuild. To verify the packages: check that the package builds with the correct compiler version, and that the tests succeed during the build. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libunwind/+bug/2025458/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1997161] Re: libunwind-dev has wrong LTO data
The real issue is, that the .a files in the libunwind-dev package are not stripped, and therefore the LTO information is kept in these files. This is done by intent in the packaging. Trying to figure why ... In the meantime the least invasive thing to do is to just rebuild with GCC 11.4. ** Also affects: libunwind (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: llvm-toolchain-14 (Ubuntu Jammy) Importance: Undecided Status: New ** No longer affects: llvm-toolchain-14 (Ubuntu Jammy) ** Changed in: llvm-toolchain-14 (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libunwind in Ubuntu. https://bugs.launchpad.net/bugs/1997161 Title: libunwind-dev has wrong LTO data Status in libunwind package in Ubuntu: Confirmed Status in llvm-toolchain-14 package in Ubuntu: Invalid Status in libunwind source package in Jammy: New Bug description: When linking libunwind into my program I get the following message: lto1: fatal error: bytecode stream in file '/usr/lib/gcc/x86_64-linux- gnu/11/../../../x86_64-linux-gnu/libunwind-x86_64.a' generated with LTO version 11.2 instead of the expected 11.3 LTO stands for link time optimization. My guess is that libunwind-x86_64.a in Ubuntu repositories was compiled with earlier gcc 11.2, but the gcc version on this new installation of 22.04 is 11.3. I am not certain whether the right fix is to recompile with newer compiler version, or to make the library without turning on link time optimization options. libunwind is used for debugging, so there is no obvious benefit in enabling link time optimization for this library. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libunwind/+bug/1997161/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2022845] [NEW] SRU: update binutils to the 2.38 branch and ignore lto-wrapper warnings
Public bug reported: The tests sometimes fail with spurious lto-wrapper warnings and let the build fail. Ignore these warnings, they don't matter for the test outcome. Also apply four fixes from the binutils 2.38 branch: * SRU: LP: #1982105. Update from the binutils 2.38 branch: - Fix PR ld/29435: elf: Reset alignment for each PT_LOAD segment. - PowerPC64 pcrel got relocs against local symbols. - Fix PR ld/27998: i386: Don't allow GOTOFF relocation against IFUNC symbol for PIC. - Fix PR ld/29377: x86: Properly check invalid relocation against protected symbol. * Ignore lto-wrapper warnings when running the testsuite. https://sourceware.org/bugzilla/show_bug.cgi?id=29435 https://sourceware.org/bugzilla/show_bug.cgi?id=27998 https://sourceware.org/bugzilla/show_bug.cgi?id=29377 All changes are already in 2.39 in kinetic, and 2.40 in lunar. The changes come with test cases, and pass when running the testsuite. ** Affects: binutils (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/2022845 Title: SRU: update binutils to the 2.38 branch and ignore lto-wrapper warnings Status in binutils package in Ubuntu: New Bug description: The tests sometimes fail with spurious lto-wrapper warnings and let the build fail. Ignore these warnings, they don't matter for the test outcome. Also apply four fixes from the binutils 2.38 branch: * SRU: LP: #1982105. Update from the binutils 2.38 branch: - Fix PR ld/29435: elf: Reset alignment for each PT_LOAD segment. - PowerPC64 pcrel got relocs against local symbols. - Fix PR ld/27998: i386: Don't allow GOTOFF relocation against IFUNC symbol for PIC. - Fix PR ld/29377: x86: Properly check invalid relocation against protected symbol. * Ignore lto-wrapper warnings when running the testsuite. https://sourceware.org/bugzilla/show_bug.cgi?id=29435 https://sourceware.org/bugzilla/show_bug.cgi?id=27998 https://sourceware.org/bugzilla/show_bug.cgi?id=29377 All changes are already in 2.39 in kinetic, and 2.40 in lunar. The changes come with test cases, and pass when running the testsuite. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/2022845/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1982105] Re: update binutils to the 2.38 branch in 22.04 LTS
** Changed in: binutils (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1982105 Title: update binutils to the 2.38 branch in 22.04 LTS Status in binutils package in Ubuntu: Invalid Status in binutils source package in Jammy: Fix Released Bug description: SRU: update binutils to the 2.38 branch in 22.04 LTS. The new build will be validated by the main component on all architectures. test rebuilds at https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20220728-jammy-jammy.html https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20220728-jammy-gcc-jammy.html the first one is the reference test rebuild, the second one the rebuild using updated binutils, GCC and python packages. Analysis: regressions on riscv64 (caused by enabling the tests) are: abseil adsys colord dovecot glib-networking glibc gnome-bluetooth3 gnome-control-center google-perftools json-glib libfprint libgdata memcached mir openvswitch ovn pmdk power-profiles-daemon strace swtpm vim devscripts is not a regression, introduced by a custom dpkg- buildpackage wrapper. binutils and python3-stdlib-extensions are superseded which are part of the planned updates. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1982105/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1982105] Re: update binutils to the 2.38 branch in 22.04 LTS
** Summary changed: - update binutils to the 2.38 branch in 20.04 LTS + update binutils to the 2.38 branch in 22.04 LTS ** Description changed: - SRU: update binutils to the 2.38 branch in 20.04 LTS. + SRU: update binutils to the 2.38 branch in 22.04 LTS. The new build will be validated by the main component on all architectures. test rebuilds at https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20220728-jammy-jammy.html https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20220728-jammy-gcc-jammy.html the first one is the reference test rebuild, the second one the rebuild using updated binutils, GCC and python packages. Analysis: regressions on riscv64 (caused by enabling the tests) are: abseil adsys colord dovecot glib-networking glibc gnome-bluetooth3 gnome-control-center google-perftools json-glib libfprint libgdata memcached mir openvswitch ovn pmdk power-profiles-daemon strace swtpm vim devscripts is not a regression, introduced by a custom dpkg-buildpackage wrapper. binutils and python3-stdlib-extensions are superseded which are part of the planned updates. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1982105 Title: update binutils to the 2.38 branch in 22.04 LTS Status in binutils package in Ubuntu: New Status in binutils source package in Jammy: Fix Committed Bug description: SRU: update binutils to the 2.38 branch in 22.04 LTS. The new build will be validated by the main component on all architectures. test rebuilds at https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20220728-jammy-jammy.html https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20220728-jammy-gcc-jammy.html the first one is the reference test rebuild, the second one the rebuild using updated binutils, GCC and python packages. Analysis: regressions on riscv64 (caused by enabling the tests) are: abseil adsys colord dovecot glib-networking glibc gnome-bluetooth3 gnome-control-center google-perftools json-glib libfprint libgdata memcached mir openvswitch ovn pmdk power-profiles-daemon strace swtpm vim devscripts is not a regression, introduced by a custom dpkg- buildpackage wrapper. binutils and python3-stdlib-extensions are superseded which are part of the planned updates. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1982105/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1971474] Re: SRU: Update gdb to the final 12.1 release in 22.04 LTS
tested together with the binutils and GCC SRUs. No regressions. ** Tags removed: verification-needed verification-needed-jammy ** Tags added: verification-done verification-done-jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdb in Ubuntu. https://bugs.launchpad.net/bugs/1971474 Title: SRU: Update gdb to the final 12.1 release in 22.04 LTS Status in gdb package in Ubuntu: Invalid Status in gdb source package in Jammy: Fix Committed Bug description: Update gdb to the final 12.1 release in 22.04 LTS. jammy ships with the gdb 12.1 release candidate, taken from the gdb-12 branch. Changes up to the final release are: - updated gnulib library - Fix for PR mi/29002 (Windows only) - gdb: fix 'remote show FOO-packet' aliases - various testsuite fixes - fixing compiler warnings - Fix bug in Ada number lexing - Remove "Ada Settings" node from the manual - Handle TLS variable lookups when using separate debug files. - PR 28980: gdb: don't copy entirely optimized out values in value_copy - gdb/mi: fix use after free of frame_info causing spurious notifications Comparing the test results between the two builds doesn't show any regression on any architecture. Also tested with a test rebuild of main, see LP: #1970233. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1971474/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1982105] Re: update binutils to the 2.38 branch in 20.04 LTS
all autopkg tests passed now ** Tags removed: verification-needed verification-needed-jammy ** Tags added: verification-done verification-needed-done -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1982105 Title: update binutils to the 2.38 branch in 20.04 LTS Status in binutils package in Ubuntu: New Status in binutils source package in Jammy: Fix Committed Bug description: SRU: update binutils to the 2.38 branch in 20.04 LTS. The new build will be validated by the main component on all architectures. test rebuilds at https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20220728-jammy-jammy.html https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20220728-jammy-gcc-jammy.html the first one is the reference test rebuild, the second one the rebuild using updated binutils, GCC and python packages. Analysis: regressions on riscv64 (caused by enabling the tests) are: abseil adsys colord dovecot glib-networking glibc gnome-bluetooth3 gnome-control-center google-perftools json-glib libfprint libgdata memcached mir openvswitch ovn pmdk power-profiles-daemon strace swtpm vim devscripts is not a regression, introduced by a custom dpkg- buildpackage wrapper. binutils and python3-stdlib-extensions are superseded which are part of the planned updates. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1982105/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1969856] Re: bash --version does not correspond to package name
bash upstream encodes the patchlevel into the version number, while patches and security fixes in Ubuntu are applied on top of the upstream version. That's expected behavior. ** Changed in: bash (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/1969856 Title: bash --version does not correspond to package name Status in bash package in Ubuntu: Won't Fix Bug description: While investigating a potentially compromised system, I ran `bash --version` and got the following: `GNU bash, version 4.4.20(1)-release (x86_64-pc-linux-gnu)` Disquieting, given that I had just installed a package named `bash_4.4.18-2ubuntu1.3_amd64.deb`. I downloaded the `.deb` archive and, upon extracting it, checked its hash (SHA256) against the instance on my path. They were the same (`15d4469eb3da716fefcc0c395a5b1d1657ad0555ec3ae623e727bb0dfcee19cf`)--indicating, presumably, that I was running whatever version was in the `.deb` I'd just downloaded. Why is the version reported by the binary different from the version used to denote the package? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1969856/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1971474] Re: SRU: Update gdb to the final 12.1 release in 22.04 LTS
** Description changed: Update gdb to the final 12.1 release in 22.04 LTS. jammy ships with the gdb 12.1 release candidate, taken from the gdb-12 branch. Changes up to the final release are: - - updated gnulib library - - Fix for PR mi/29002 (Windows only) - - gdb: fix 'remote show FOO-packet' aliases - - various testsuite fixes - - fixing compiler warnings - - Fix bug in Ada number lexing - - Remove "Ada Settings" node from the manual - - Handle TLS variable lookups when using separate debug files. - - PR 28980: gdb: don't copy entirely optimized out values in value_copy - - gdb/mi: fix use after free of frame_info causing spurious notifications + - updated gnulib library + - Fix for PR mi/29002 (Windows only) + - gdb: fix 'remote show FOO-packet' aliases + - various testsuite fixes + - fixing compiler warnings + - Fix bug in Ada number lexing + - Remove "Ada Settings" node from the manual + - Handle TLS variable lookups when using separate debug files. + - PR 28980: gdb: don't copy entirely optimized out values in value_copy + - gdb/mi: fix use after free of frame_info causing spurious notifications Comparing the test results between the two builds doesn't show any regression on any architecture. + + Also tested with a test rebuild of main, see LP: #1970233. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdb in Ubuntu. https://bugs.launchpad.net/bugs/1971474 Title: SRU: Update gdb to the final 12.1 release in 22.04 LTS Status in gdb package in Ubuntu: Confirmed Status in gdb source package in Jammy: Confirmed Bug description: Update gdb to the final 12.1 release in 22.04 LTS. jammy ships with the gdb 12.1 release candidate, taken from the gdb-12 branch. Changes up to the final release are: - updated gnulib library - Fix for PR mi/29002 (Windows only) - gdb: fix 'remote show FOO-packet' aliases - various testsuite fixes - fixing compiler warnings - Fix bug in Ada number lexing - Remove "Ada Settings" node from the manual - Handle TLS variable lookups when using separate debug files. - PR 28980: gdb: don't copy entirely optimized out values in value_copy - gdb/mi: fix use after free of frame_info causing spurious notifications Comparing the test results between the two builds doesn't show any regression on any architecture. Also tested with a test rebuild of main, see LP: #1970233. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1971474/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1982108] Re: SRU: update python3.10 to the 3.10.5 release in 22.04 LTS
** Also affects: python3-defaults (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1982108 Title: SRU: update python3.10 to the 3.10.5 release in 22.04 LTS Status in python3-defaults package in Ubuntu: New Status in python3-stdlib-extensions package in Ubuntu: Confirmed Status in python3.10 package in Ubuntu: Confirmed Status in python3-defaults source package in Jammy: New Status in python3-stdlib-extensions source package in Jammy: Confirmed Status in python3.10 source package in Jammy: Confirmed Bug description: SRU: update python3.10 to the 3.10.5 release in 22.04 LTS we are doing a test rebuild of 22.04 main to check for regressions. test rebuilds at https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20220728-jammy-jammy.html https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20220728-jammy-gcc-jammy.html the first one is the reference test rebuild, the second one the rebuild using updated binutils, GCC and python packages. Analysis: regressions on riscv64 (caused by enabling the tests) are: abseil adsys colord dovecot glib-networking glibc gnome-bluetooth3 gnome-control-center google-perftools json-glib libfprint libgdata memcached mir openvswitch ovn pmdk power-profiles-daemon strace swtpm vim devscripts is not a regression, introduced by a custom dpkg- buildpackage wrapper. binutils and python3-stdlib-extensions are superseded which are part of the planned updates. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1982108/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1982105] Re: update binutils to the 2.38 branch in 20.04 LTS
** Description changed: SRU: update binutils to the 2.38 branch in 20.04 LTS. The new build will be validated by the main component on all architectures. + + test rebuilds at + https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20220728-jammy-jammy.html + https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20220728-jammy-gcc-jammy.html + + the first one is the reference test rebuild, the second one the rebuild + using updated binutils, GCC and python packages. + + Analysis: + + regressions on riscv64 (caused by enabling the tests) are: + + abseil + adsys + colord + dovecot + glib-networking + glibc + gnome-bluetooth3 + gnome-control-center + google-perftools + json-glib + libfprint + libgdata + memcached + mir + openvswitch + ovn + pmdk + power-profiles-daemon + strace + swtpm + vim + + devscripts is not a regression, introduced by a custom dpkg-buildpackage + wrapper. + + binutils and python3-stdlib-extensions are superseded which are part of + the planned updates. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1982105 Title: update binutils to the 2.38 branch in 20.04 LTS Status in binutils package in Ubuntu: New Status in binutils source package in Jammy: New Bug description: SRU: update binutils to the 2.38 branch in 20.04 LTS. The new build will be validated by the main component on all architectures. test rebuilds at https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20220728-jammy-jammy.html https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20220728-jammy-gcc-jammy.html the first one is the reference test rebuild, the second one the rebuild using updated binutils, GCC and python packages. Analysis: regressions on riscv64 (caused by enabling the tests) are: abseil adsys colord dovecot glib-networking glibc gnome-bluetooth3 gnome-control-center google-perftools json-glib libfprint libgdata memcached mir openvswitch ovn pmdk power-profiles-daemon strace swtpm vim devscripts is not a regression, introduced by a custom dpkg- buildpackage wrapper. binutils and python3-stdlib-extensions are superseded which are part of the planned updates. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1982105/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1982105] Re: update binutils to the 2.38 branch in 20.04 LTS
** Also affects: binutils (Ubuntu Jammy) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1982105 Title: update binutils to the 2.38 branch in 20.04 LTS Status in binutils package in Ubuntu: New Status in binutils source package in Jammy: New Bug description: SRU: update binutils to the 2.38 branch in 20.04 LTS. The new build will be validated by the main component on all architectures. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1982105/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1974115] Re: [UBUNTU 22.04] BINUTILS: Adding new platform name IBM z16
** Changed in: binutils (Ubuntu Kinetic) Status: New => Fix Released ** Changed in: binutils (Ubuntu Jammy) Status: New => In Progress ** Changed in: binutils (Ubuntu Jammy) Assignee: Canonical Foundations Team (canonical-foundations) => Matthias Klose (doko) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1974115 Title: [UBUNTU 22.04] BINUTILS: Adding new platform name IBM z16 Status in Ubuntu on IBM z Systems: New Status in binutils package in Ubuntu: Fix Released Status in binutils source package in Jammy: In Progress Status in binutils source package in Kinetic: Fix Released Bug description: SRU Justification: == [Impact] * As of today the architectural (level) name 'arch14' is used as CPU name for the new IBM z16 system. * The real name 'z16' couldn't be used until officially announced. * That happened meanwhile, hence we can now add and use the real name. [Test Plan] * Check if the same (proper) opcodes are detected on an IBM z16 system with and without the patch. Since only the identification and name of a z16 system was modified. * Or the simplest test is probably to check (after having 'binutils' installed on an Ubuntu 22.04 s390x system) if not only: 'as -m64 -march=arch14 --target-help' but also: 'as -m64 -march=z16 --target-help' succeeds and leads to the same output. (As it does for '-march=arch13' and '-march=arch15'.) [Where problems could occur] * Issues could happen if the conditional statement that look for architectural / CPU name are paired wrongly, since: * 'z16' belongs to 'arch14', 'z15' to 'arch13', etc. * If these pairs are not handled correctly, or the identification is erroneous a wrong system might be identified and wrong instructions used etc. [Other] * This is a hardware enablement SRU to enhance the IBM z16 support. __ After the announcement support for the official machine name z16 has been added to binutils. Please consider picking up the following patch from 2.37 branch: commit e24d2a2d11008aa363366c1087219f3e3405782a (origin/binutils-2_37-branch, 2.37) IBM zSystems: Add support for z16 as CPU name. So far z16 was identified as arch14. After the machine has been announced we can now add the real name. (cherry picked from commit 69341966def7f6551bc4452684136831d6a6941c) (cherry picked from commit fb4d148004f28494e9fb5d2400a13308d07a7988) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1974115/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1982105] [NEW] update binutils to the 2.38 branch in 20.04 LTS
Public bug reported: SRU: update binutils to the 2.38 branch in 20.04 LTS. The new build will be validated by the main component on all architectures. ** Affects: binutils (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1982105 Title: update binutils to the 2.38 branch in 20.04 LTS Status in binutils package in Ubuntu: New Bug description: SRU: update binutils to the 2.38 branch in 20.04 LTS. The new build will be validated by the main component on all architectures. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1982105/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1978129] Re: Incomplete support for DT_RELR relocations on Ubuntu 22.04
** Changed in: binutils (Ubuntu Kinetic) Status: New => Fix Released ** Changed in: binutils (Ubuntu Jammy) Status: New => In Progress ** Changed in: binutils (Ubuntu Jammy) Assignee: Canonical Foundations Team (canonical-foundations) => Matthias Klose (doko) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1978129 Title: Incomplete support for DT_RELR relocations on Ubuntu 22.04 Status in The Ubuntu-power-systems project: New Status in binutils package in Ubuntu: Fix Released Status in binutils source package in Jammy: In Progress Status in binutils source package in Kinetic: Fix Released Bug description: SRU Justification: == [Impact] * The latest glibc uses DT_RELR relocations, but it turned out that the linker support is still incomplete, as of binutils-2.38-3ubuntu1 on Ubuntu 22.04. * It lacks the fix/commit 'PowerPC64 DT_RELR relative reloc addresses'. * As discussed at the binutils mailing list: https://sourceware.org/pipermail/binutils/2022-March/119921.html this fixes several (glibc) regressions (from 574 to 17). * Instead of stashing r_offset final address calculations in ppc64_elf_size_stubs for use by ppc64_elf_build_stubs, section/offset pairs need to be kept. [Test Plan] * Build and run the official (make) check: git clone git://sourceware.org/git/glibc.git mkdir build && cd build ../glibc/configure --prefix=/usr && make -j8 && make check [Where problems could occur] * In case relr_addr is not replaced everywhere it's deletion in elf64-ppc.c can cause problems, which will mainly occur at build time. * The relr section/offset array may lead to problems if the array is not properly handled or used. * The rewrite of append_relr_off may cause issues due to wrong allocs erroneous pointer arithmetic or array handling. * The entirely new sort_relr function may introduce new code issues or performance issues. * The adjustments of ppc64_elf_size_stubs and ppc64_elf_build_stubs to the new relr code could be done wrong in which case the linker support is still not working. * But the patch was discussed at the upstream mailing list: https://sourceware.org/pipermail/binutils/2022-March/thread.html#119921 * and is limited to ppc, and even to file 'elf64-ppc.c'. __ == Comment: #0 - Matheus Salgueiro Castanho - 2022-06-09 09:32:29 == ---Problem Description--- Latest glibc uses DT_RELR relocations, but linker support is incomplete as of binutils-2.38-3ubuntu1 on Ubuntu 22.04. It lacks the following fix integrated into the upstream 2.38 branch: PowerPC64 DT_RELR relative reloc addresses https://sourceware.org/git/?p=binutils-gdb.git;a=commit;h=e4a35c7319628045302d4c597cb27f1b0a08c858 As mentioned in the binutils mailing list when this patch was discussed, this fixes several glibc regressions: https://sourceware.org/pipermail/binutils/2022-March/119921.html Contact Information = Matheus Castanho/mscasta...@ibm.com ---uname output--- N/A Machine Type = N/A ---Debugger--- A debugger is not configured ---Steps to Reproduce--- git clone git://sourceware.org/git/glibc.git mkdir build && cd build ../glibc/configure --prefix=/usr && make -j8 && make check Userspace tool common name: binutils The userspace tool has the following bit modes: 64-bit Userspace rpm: binutils Userspace tool obtained from project website: na *Additional Instructions for Matheus Castanho/mscasta...@ibm.com: -Attach ltrace and strace of userspace application. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1978129/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1976258] [NEW] icu ftbfs in the jammy release pocket
Public bug reported: as seen in a test rebuild, this package fails to build in the jammy release pocket (note the log behind the link might go away): https://launchpadlibrarian.net/604216394/buildlog_ubuntu-jammy- amd64.icu_70.1-2_BUILDING.txt.gz [...] make[4]: Leaving directory '/<>/source/test/cintltst' - | *** FAILING TEST SUMMARY FOR: intltest TestCanonicalID TimeZoneTest format | *** END FAILING TEST SUMMARY FOR: intltest --- ALL TESTS SUMMARY: ok: testdata iotest cintltst = ERRS: intltest make[3]: *** [Makefile:91: check-recursive] Error 1 ** Affects: icu (Ubuntu) Importance: Undecided Status: New ** Tags: ftbfs rls-jj-incoming ** Tags added: ftbfs rls-jj-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to icu in Ubuntu. https://bugs.launchpad.net/bugs/1976258 Title: icu ftbfs in the jammy release pocket Status in icu package in Ubuntu: New Bug description: as seen in a test rebuild, this package fails to build in the jammy release pocket (note the log behind the link might go away): https://launchpadlibrarian.net/604216394/buildlog_ubuntu-jammy- amd64.icu_70.1-2_BUILDING.txt.gz [...] make[4]: Leaving directory '/<>/source/test/cintltst' - | *** FAILING TEST SUMMARY FOR: intltest TestCanonicalID TimeZoneTest format | *** END FAILING TEST SUMMARY FOR: intltest --- ALL TESTS SUMMARY: ok: testdata iotest cintltst = ERRS: intltest make[3]: *** [Makefile:91: check-recursive] Error 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/icu/+bug/1976258/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1976259] [NEW] librsvg ftbfs in the jammy release pocket
Public bug reported: as seen in a test rebuild, this package fails to build in the jammy release pocket (note the log behind the link might go away): https://launchpadlibrarian.net/604216345/buildlog_ubuntu- jammy-i386.librsvg_2.52.5+dfsg-3_BUILDING.txt.gz test url_resolver::tests::allows_relative ... ok failures: transform::tests::parses_transform_list stdout thread 'transform::tests::parses_transform_list' panicked at 'assertion failed: t1.y0.approx_eq(t2.y0, (epsilon, 1))', src/transform.rs:716:9 transform::tests::parses_valid_transform stdout thread 'transform::tests::parses_valid_transform' panicked at 'assertion failed: t1.y0.approx_eq(t2.y0, (epsilon, 1))', src/transform.rs:716:9 failures: transform::tests::parses_transform_list transform::tests::parses_valid_transform test result: FAILED. 254 passed; 2 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.02s error: test failed, to rerun pass '--lib' make[5]: *** [Makefile:1537: check-local] Error 101 ** Affects: librsvg (Ubuntu) Importance: Undecided Status: New ** Tags: ftbfs rls-jj-incoming ** Tags added: ftbfs rls-jj-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to librsvg in Ubuntu. https://bugs.launchpad.net/bugs/1976259 Title: librsvg ftbfs in the jammy release pocket Status in librsvg package in Ubuntu: New Bug description: as seen in a test rebuild, this package fails to build in the jammy release pocket (note the log behind the link might go away): https://launchpadlibrarian.net/604216345/buildlog_ubuntu- jammy-i386.librsvg_2.52.5+dfsg-3_BUILDING.txt.gz test url_resolver::tests::allows_relative ... ok failures: transform::tests::parses_transform_list stdout thread 'transform::tests::parses_transform_list' panicked at 'assertion failed: t1.y0.approx_eq(t2.y0, (epsilon, 1))', src/transform.rs:716:9 transform::tests::parses_valid_transform stdout thread 'transform::tests::parses_valid_transform' panicked at 'assertion failed: t1.y0.approx_eq(t2.y0, (epsilon, 1))', src/transform.rs:716:9 failures: transform::tests::parses_transform_list transform::tests::parses_valid_transform test result: FAILED. 254 passed; 2 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.02s error: test failed, to rerun pass '--lib' make[5]: *** [Makefile:1537: check-local] Error 101 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/librsvg/+bug/1976259/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1976255] [NEW] accountsservice ftbfs in the jammy release pocket
Public bug reported: as seen in a test rebuild, this package fails to build in the jammy release pocket (note the log behind the link might go away): https://launchpadlibrarian.net/604216054/buildlog_ubuntu-jammy- amd64.accountsservice_22.07.5-2ubuntu1_BUILDING.txt.gz Ok: 2 Expected Fail: 0 Fail: 10 Unexpected Pass:0 Skipped:0 Timeout:0 Full log written to /<>/obj-x86_64-linux-gnu/meson-logs/testlog.txt cd obj-x86_64-linux-gnu && tail -v -n \+0 meson-logs/testlog.txt ==> meson-logs/testlog.txt <== Log of Meson test suite run on 2022-05-30T08:33:42.861398 Inherited environment: SCHROOT_GID=2501 DEB_HOST_MULTIARCH=x86_64-linux- gnu LC_ALL=C.UTF-8 DEB_HOST_GNU_SYSTEM=linux-gnu DEB_BUILD_GNU_TYPE=x86_64-linux-gnu DEB_LDFLAGS_MAINT_APPEND=-Wl,--as- needed DEB_TARGET_ARCH_LIBC=gnu DEB_BUILD_ARCH_ENDIAN=little DEB_BUILD_GNU_SYSTEM=linux-gnu DEB_BUILD_ARCH_BITS=64 DEB_BUILD_OPTIONS=parallel=4 DEB_HOST_ARCH=amd64 DEB_TARGET_ARCH_ENDIAN=little DEB_BUILD_PROFILES=noudeb SOURCE_DATE_EPOCH=1645543676 V=1 DEB_HOST_ARCH_BITS=64 LANG=C.UTF-8 MAKEFLAGS='' SCHROOT_GROUP=buildd DEB_TARGET_ARCH=amd64 DEB_HOST_GNU_CPU=x86_64 DEB_BUILD_ARCH_LIBC=gnu MFLAGS='' DEB_TARGET_ARCH_BITS=64 DEB_BUILD_ARCH_CPU=amd64 SCHROOT_ALIAS_NAME=build-PACKAGEBUILD-23614463 DEB_HOST_ARCH_OS=linux SHELL=/bin/sh DEB_HOST_ARCH_CPU=amd64 SCHROOT_USER=buildd PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games DEB_BUILD_ARCH_ABI=base DEB_BUILD_ARCH=amd64 DEB_HOST_ARCH_LIBC=gnu SCHROOT_SESSION_ID=build-PACKAGEBUILD-23614463 DEB_TARGET_ARCH_CPU=amd64 DEB_HOST_GNU_TYPE=x86_64-linux-gnu DEB_BUILD_ARCH_OS=linux LOGNAME=buildd DEB_TARGET_MULTIARCH=x86_64-linux-gnu DEB_BUILD_GNU_CPU=x86_64 DEB_TARGET_ARCH_OS=linux USER=buildd DEB_HOST_ARCH_ABI=base DEB_BUILD_MULTIARCH=x86_64-linux-gnu DEB_TARGET_GNU_TYPE=x86_64-linux-gnu DEB_TARGET_ARCH_ABI=base SCHROOT_UID=2001 SCHROOT_COMMAND='dpkg-buildpackage -us -uc -mLaunchpad Build Daemon -b -rfakeroot' DEB_TARGET_GNU_CPU=x86_64 APT_CONFIG=/var/lib/sbuild/apt.conf HOME=/<>/debian/.debhelper/generated/_source/home DEB_RULES_REQUIRES_ROOT=binary-targets DEB_TARGET_GNU_SYSTEM=linux-gnu DEB_HOST_ARCH_ENDIAN=little TERM=unknown SCHROOT_CHROOT_NAME=build- PACKAGEBUILD-23614463 MAKELEVEL=1 DH_INTERNAL_BUILDFLAGS=1 ASFLAGS='' CFLAGS='-g -O2 -ffile-prefix-map=/<>=. -flto=auto -ffat- lto-objects -flto=auto -ffat-lto-objects -fstack-protector-strong -Wformat -Werror=format-security' CPPFLAGS='-Wdate-time -D_FORTIFY_SOURCE=2' CXXFLAGS='-g -O2 -ffile-prefix- map=/<>=. -flto=auto -ffat-lto-objects -flto=auto -ffat- lto-objects -fstack-protector-strong -Wformat -Werror=format-security' DFLAGS=-frelease FCFLAGS='-g -O2 -ffile-prefix-map=/<>=. -flto=auto -ffat-lto-objects -flto=auto -ffat-lto-objects -fstack- protector-strong' FFLAGS='-g -O2 -ffile-prefix-map=/<>=. -flto=auto -ffat-lto-objects -flto=auto -ffat-lto-objects -fstack- protector-strong' GCJFLAGS='-g -O2 -ffile-prefix-map=/<>=. -flto=auto -ffat-lto-objects -fstack-protector-strong' LDFLAGS='-Wl,-Bsymbolic-functions -flto=auto -ffat-lto-objects -flto=auto -Wl,-z,relro -Wl,--as-needed' OBJCFLAGS='-g -O2 -ffile- prefix-map=/<>=. -flto=auto -ffat-lto-objects -flto=auto -ffat-lto-objects -fstack-protector-strong -Wformat -Werror=format- security' OBJCXXFLAGS='-g -O2 -ffile-prefix-map=/<>=. -flto=auto -ffat-lto-objects -flto=auto -ffat-lto-objects -fstack- protector-strong -Wformat -Werror=format-security' XDG_RUNTIME_DIR=/tmp/dh-xdg-rundir-JPi9I5rR MESON_TESTTHREADS=4 1/12 accountsservice:accounts-service+libaccountsservice+TestAccountsService / TestAccountsService.test_cache_user FAIL0.33s exit status 1 08:33:42 LD_LIBRARY_PATH=/<>/obj-x86_64-linux-gnu/src/libaccountsservice GI_TYPELIB_PATH=/<>/obj-x86_64-linux-gnu/src/libaccountsservice G_DEBUG=fatal-criticals G_MESSAGES_DEBUG=all MALLOC_PERTURB_=58 /usr/bin/python3 /<>/obj-x86_64-linux-gnu/../tests/test-libaccountsservice.py TestAccountsService.test_cache_user --- output --- test_cache_user (__main__.TestAccountsService) ... (process:11790): accountsservice-DEBUG: 08:33:43.062: Finding a graphical session for user 2001 (process:11790): accountsservice-DEBUG: 08:33:43.062: Failed to identify the current session (process:11790): accountsservice-DEBUG: 08:33:43.062: ActUserManager: seat unloaded, so trying to set loaded property (process:11790): accountsservice-DEBUG: 08:33:43.062: ActUserManager: Seat wouldn't load, so giving up on it and setting loaded property (process:11790): accountsservice-DEBUG: 08:33:43.062: ActUserManager: already loaded, so not setting loaded property (process:11790): accountsservice-DEBUG: 08:33:43.063: ActUserManager: Creating user 'user', 'I am User', 1 (process:11790): accountsservice-DEBUG: 08:33:43.063: ActUserManager: calling 'ListCachedUsers' (process:11790): accountsservic
[Touch-packages] [Bug 1971474] [NEW] SRU: Update gdb to the final 12.1 release in 22.04 LTS
Public bug reported: Update gdb to the final 12.1 release in 22.04 LTS. jammy ships with the gdb 12.1 release candidate, taken from the gdb-12 branch. Changes up to the final release are: - updated gnulib library - Fix for PR mi/29002 (Windows only) - gdb: fix 'remote show FOO-packet' aliases - various testsuite fixes - fixing compiler warnings - Fix bug in Ada number lexing - Remove "Ada Settings" node from the manual - Handle TLS variable lookups when using separate debug files. - PR 28980: gdb: don't copy entirely optimized out values in value_copy - gdb/mi: fix use after free of frame_info causing spurious notifications Comparing the test results between the two builds doesn't show any regression on any architecture. ** Affects: gdb (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdb in Ubuntu. https://bugs.launchpad.net/bugs/1971474 Title: SRU: Update gdb to the final 12.1 release in 22.04 LTS Status in gdb package in Ubuntu: New Bug description: Update gdb to the final 12.1 release in 22.04 LTS. jammy ships with the gdb 12.1 release candidate, taken from the gdb-12 branch. Changes up to the final release are: - updated gnulib library - Fix for PR mi/29002 (Windows only) - gdb: fix 'remote show FOO-packet' aliases - various testsuite fixes - fixing compiler warnings - Fix bug in Ada number lexing - Remove "Ada Settings" node from the manual - Handle TLS variable lookups when using separate debug files. - PR 28980: gdb: don't copy entirely optimized out values in value_copy - gdb/mi: fix use after free of frame_info causing spurious notifications Comparing the test results between the two builds doesn't show any regression on any architecture. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1971474/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1953200] Re: [jammy] FTBFS, gcc ICE?
mir builds with the recent gcc-11 in jammy, closing ** Changed in: mir (Ubuntu) Status: New => Invalid ** Changed in: gcc-11 (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1953200 Title: [jammy] FTBFS, gcc ICE? Status in gcc-11 package in Ubuntu: Invalid Status in mir package in Ubuntu: Invalid Bug description: https://launchpad.net/ubuntu/+source/mir/2.4.1-0ubuntu3 [ 38%] Building CXX object src/client/CMakeFiles/mirclientobjects.dir/event_printer.cpp.o cd /<>/build-amd64/src/client && /usr/bin/c++ -DCLIENT_PLATFORM_VERSION=\"MIR_CLIENT_PLATFORM_5\" -DEGL_NO_X11 -DLOG_NDEBUG=1 -DLTTNG_UST_HAVE_SDT_INTEGRATION -DMESA_EGL_NO_X11_HEADERS -DMIR_CLIENT_PLATFORM_PATH=\"/usr/lib/x86_64-linux-gnu/mir/client-platform/\" -DMIR_DRMMODEADDFB_HAS_CONST_SIGNATURE -DMIR_LOG_COMPONENT_FALLBACK=\"mirclient\" -DMIR_VERSION_MAJOR=2 -DMIR_VERSION_MICRO=1 -DMIR_VERSION_MINOR=4 -D_FILE_OFFSET_BITS=64 -D_GNU_SOURCE -I/<>/include/core -I/<>/include/common -I/<>/include/cookie -I/<>/src/include/common -I/<>/build-amd64/src/capnproto -I/<>/build-amd64/src/protobuf -I/<>/build-amd64/src/client -I/<>/include/platform -I/<>/include/client -I/<>/src/include/client -I/<>/src/include/cookie -I/usr/include/libdrm -g -O2 -ffile-prefix-map=/<>=. -flto=auto -ffat-lto-objects -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -pthread -g -std=c++17 -Wall -fno-strict-aliasing -pedantic -Wnon-virtual-dtor -Wextra -fPIC -Werror -Wno-mismatched-tags -Wno-psabi -flto -ffat-lto-objects -std=c++17 -MD -MT src/client/CMakeFiles/mirclientobjects.dir/event_printer.cpp.o -MF CMakeFiles/mirclientobjects.dir/event_printer.cpp.o.d -o CMakeFiles/mirclientobjects.dir/event_printer.cpp.o -c /<>/src/client/event_printer.cpp In file included from /usr/include/boost/bind.hpp:30, from /<>/src/client/rpc/mir_protobuf_rpc_channel.cpp:44: /usr/include/boost/bind.hpp:36:1: note: ‘#pragma message: The practice of declaring the Bind placeholders (_1, _2, ...) in the global namespace is deprecated. Please use + using namespace boost::placeholders, or define BOOST_BIND_GLOBAL_PLACEHOLDERS to retain the current behavior.’ 36 | BOOST_PRAGMA_MESSAGE( | ^~~~ The bug is not reproducible, so it is likely a hardware or OS problem. make[3]: *** [src/client/lttng/CMakeFiles/mirclientlttng-static.dir/build.make:107: src/client/lttng/CMakeFiles/mirclientlttng-static.dir/input_receiver_report.cpp.o] Error 1 make[3]: Leaving directory '/<>/build-amd64' make[2]: *** [CMakeFiles/Makefile2:4657: src/client/lttng/CMakeFiles/mirclientlttng-static.dir/all] Error 2 make[2]: *** Waiting for unfinished jobs Possibly relevant, this seems to be using boost 1.74.0-13ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-11/+bug/1953200/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1452115] Re: Python interpreter binary is not compiled as PIE
** Changed in: python3.10 (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python2.7 in Ubuntu. https://bugs.launchpad.net/bugs/1452115 Title: Python interpreter binary is not compiled as PIE Status in Python: New Status in python2.7 package in Ubuntu: Fix Released Status in python3.10 package in Ubuntu: Fix Committed Status in python3.4 package in Ubuntu: Fix Released Status in python3.6 package in Ubuntu: Confirmed Status in python3.7 package in Ubuntu: Confirmed Status in python3.8 package in Ubuntu: Confirmed Status in python3.9 package in Ubuntu: New Status in python3.7 package in Debian: New Status in python3.8 package in Debian: New Bug description: The python2.7 binary (installed at /usr/bin/python2.7; package version 2.7.6-8) is not compiled as a position independent executable (PIE). It appears that the python compilation process is somewhat arcane and the hardening wrapper probably doesn't do the trick for it. This is incredibly dangerous as it means that any vulnerability within a native module (e.g. ctypes-based), or within python itself will expose an incredibly large amount of known memory contents at known addresses (including a large number of dangerous instruction groupings). This enables ROP-based (https://en.wikipedia.org/wiki/Return-oriented_programming) to abuse the interpreter itself to bypass non-executable page protections. I have put together an example vulnerable C shared object (with a buffer overflow) accessed via python through the ctypes interface as an example. This uses a single ROP "gadget" on top of using the known PLT location for system(3) (https://en.wikipedia.org/wiki/Return-to-libc_attack) to call "id". The example code is accessible at: - https://gist.github.com/ChaosData/ae6076cb1c3cc7b0a367 I'm not exactly familiar enough with the python build process to say where exactly an -fPIE needs to be injected into a script/makefile, but I feel that given the perceived general preference for ctypes- based modules over python written ones, as the native code implementations tend to be more performant, this feels like a large security hole within the system. Given the nature of this "issue," I'm not 100% sure of where it is best reported, but from what I can tell, this conflicts with the Ubuntu hardening features and is definitely exploitable should a native module contain a sufficiently exploitable vulnerability that allows for control of the instruction register. To manage notifications about this bug go to: https://bugs.launchpad.net/python/+bug/1452115/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1965112] Re: cupsd crashed with SIGSEGV in __strcmp_evex()
$ cupsctl
_debug_logging=1
_remote_admin=0
_remote_any=0
_share_printers=0
_user_cancel_any=0
BrowseLocalProtocols=dnssd
DefaultAuthType=Basic
ErrorPolicy=retry-job
IdleExitTimeout=60
JobPrivateAccess=default
JobPrivateValues=default
MaxLogSize=0
PageLogFormat=
SubscriptionPrivateAccess=default
SubscriptionPrivateValues=default
WebInterface=Yes
** Attachment added: "cupsd.conf"
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1965112/+attachment/5569712/+files/cupsd.conf
** Changed in: cups (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1965112
Title:
cupsd crashed with SIGSEGV in __strcmp_evex()
Status in cups package in Ubuntu:
New
Bug description:
trying to print with jammy 20220316, to a network printer
ProblemType: Crash
DistroRelease: Ubuntu 22.04
Package: cups-daemon 2.4.1op1-1ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19
Uname: Linux 5.15.0-22-generic x86_64
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: pass
Date: Wed Mar 16 11:00:00 2022
ExecutablePath: /usr/sbin/cupsd
InstallationDate: Installed on 2022-02-28 (15 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220226)
Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No
destinations added.
MachineType: LENOVO 20Y5CTO1WW
Papersize: a4
ProcAttrCurrent: /usr/sbin/cupsd (enforce)
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.15.0-22-generic
root=UUID=229d75cc-2aa3-4f8f-b5bd-d310f6218a3f ro quiet splash vt.handoff=7
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-22-generic
root=UUID=229d75cc-2aa3-4f8f-b5bd-d310f6218a3f ro quiet splash vt.handoff=7
RebootRequiredPkgs: Error: path contained symlinks.
SegvAnalysis:
Segfault happened at: 0x7fdde6d9698c <__strcmp_evex+44>: vpcmpeqb
(%rsi),%ymm17,%k1{%k2}
PC (0x7fdde6d9698c) ok
source "(%rsi)" (0x) not located in a known VMA region (needed
readable region)!
destination "%ymm17" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: cups
StacktraceTop:
__strcmp_evex () at ../sysdeps/x86_64/multiarch/strcmp-evex.S:139
?? ()
?? ()
?? ()
__libc_start_call_main (main=main@entry=0x55ea813993a0, argc=argc@entry=2,
argv=argv@entry=0x7fffb71a6eb8) at ../sysdeps/nptl/libc_start_call_main.h:58
Title: cupsd crashed with SIGSEGV in __strcmp_evex()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
dmi.bios.date: 10/14/2021
dmi.bios.release: 1.11
dmi.bios.vendor: LENOVO
dmi.bios.version: N40ET29W (1.11 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20Y5CTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0T08861 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.11
dmi.modalias:
dmi:bvnLENOVO:bvrN40ET29W(1.11):bd10/14/2021:br1.11:efr1.11:svnLENOVO:pn20Y5CTO1WW:pvrThinkPadX1ExtremeGen4i:rvnLENOVO:rn20Y5CTO1WW:rvrSDK0T08861WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20Y5_BU_Think_FM_ThinkPadX1ExtremeGen4i:
dmi.product.family: ThinkPad X1 Extreme Gen 4i
dmi.product.name: 20Y5CTO1WW
dmi.product.sku: LENOVO_MT_20Y5_BU_Think_FM_ThinkPad X1 Extreme Gen 4i
dmi.product.version: ThinkPad X1 Extreme Gen 4i
dmi.sys.vendor: LENOVO
separator:
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1965112/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1965112] Re: cupsd crashed with SIGSEGV in __strcmp_evex()
doko@xe1:~$ driverless
ipp://HP%20LaserJet%20500%20colorMFP%20M570dw%20(6C84AD)._ipp._tcp.local/
doko@xe1:~$ driverless --std-ipp-uris
ipp://NPI6C84AD.local:631/ipp/printer
doko@xe1:~$ lpstat -v
lpstat: No destinations added.
$ ps aux | grep cups-browsed
root 94786 0.0 0.0 172744 11908 ?Ssl 11:00 0:00
/usr/sbin/cups-browsed
doko 110175 0.0 0.0 9560 2428 pts/4S+ 17:21 0:00 grep
--color=auto cups-browsed
Trying to print a png image with eog
** Attachment added: "error_log"
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1965112/+attachment/5569701/+files/error_log
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1965112
Title:
cupsd crashed with SIGSEGV in __strcmp_evex()
Status in cups package in Ubuntu:
New
Bug description:
trying to print with jammy 20220316, to a network printer
ProblemType: Crash
DistroRelease: Ubuntu 22.04
Package: cups-daemon 2.4.1op1-1ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19
Uname: Linux 5.15.0-22-generic x86_64
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: pass
Date: Wed Mar 16 11:00:00 2022
ExecutablePath: /usr/sbin/cupsd
InstallationDate: Installed on 2022-02-28 (15 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220226)
Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No
destinations added.
MachineType: LENOVO 20Y5CTO1WW
Papersize: a4
ProcAttrCurrent: /usr/sbin/cupsd (enforce)
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.15.0-22-generic
root=UUID=229d75cc-2aa3-4f8f-b5bd-d310f6218a3f ro quiet splash vt.handoff=7
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-22-generic
root=UUID=229d75cc-2aa3-4f8f-b5bd-d310f6218a3f ro quiet splash vt.handoff=7
RebootRequiredPkgs: Error: path contained symlinks.
SegvAnalysis:
Segfault happened at: 0x7fdde6d9698c <__strcmp_evex+44>: vpcmpeqb
(%rsi),%ymm17,%k1{%k2}
PC (0x7fdde6d9698c) ok
source "(%rsi)" (0x) not located in a known VMA region (needed
readable region)!
destination "%ymm17" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: cups
StacktraceTop:
__strcmp_evex () at ../sysdeps/x86_64/multiarch/strcmp-evex.S:139
?? ()
?? ()
?? ()
__libc_start_call_main (main=main@entry=0x55ea813993a0, argc=argc@entry=2,
argv=argv@entry=0x7fffb71a6eb8) at ../sysdeps/nptl/libc_start_call_main.h:58
Title: cupsd crashed with SIGSEGV in __strcmp_evex()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
dmi.bios.date: 10/14/2021
dmi.bios.release: 1.11
dmi.bios.vendor: LENOVO
dmi.bios.version: N40ET29W (1.11 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20Y5CTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0T08861 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.11
dmi.modalias:
dmi:bvnLENOVO:bvrN40ET29W(1.11):bd10/14/2021:br1.11:efr1.11:svnLENOVO:pn20Y5CTO1WW:pvrThinkPadX1ExtremeGen4i:rvnLENOVO:rn20Y5CTO1WW:rvrSDK0T08861WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20Y5_BU_Think_FM_ThinkPadX1ExtremeGen4i:
dmi.product.family: ThinkPad X1 Extreme Gen 4i
dmi.product.name: 20Y5CTO1WW
dmi.product.sku: LENOVO_MT_20Y5_BU_Think_FM_ThinkPad X1 Extreme Gen 4i
dmi.product.version: ThinkPad X1 Extreme Gen 4i
dmi.sys.vendor: LENOVO
separator:
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1965112/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1960608] Re: python-pip >= 21.3.1+dfsg-3 fails pip3-root.sh autopkgtest with python3.10
python3.10 now in -proposed ** Changed in: python3.10 (Ubuntu) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dh-python in Ubuntu. https://bugs.launchpad.net/bugs/1960608 Title: python-pip >= 21.3.1+dfsg-3 fails pip3-root.sh autopkgtest with python3.10 Status in dh-python package in Ubuntu: Fix Released Status in python-pip package in Ubuntu: New Status in python3.10 package in Ubuntu: Fix Committed Bug description: pip3-root.sh expects world package to be installed in /usr/local/lib/python3.*/dist-packages whereas it is actually installed into /usr/lib/python3.10/site-packages/. It even fails to uninstall the package right after installing it: ubuntu@autopkgtest:~$ sudo python3 -m pip install world Collecting world Using cached world-4.1.1-py3-none-any.whl Collecting atpublic Using cached atpublic-3.0.1-py3-none-any.whl (4.8 kB) Installing collected packages: atpublic, world Successfully installed atpublic-3.0.1 world-4.1.1 WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv ubuntu@autopkgtest:~$ sudo python3 -m pip uninstall world WARNING: Skipping world as it is not installed. WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dh-python/+bug/1960608/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1958720] Re: python3-yaml and python3-six are not co-installable with python-is-python2 in jammy
there is no python-is-python2 in jammy anymore -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to six in Ubuntu. https://bugs.launchpad.net/bugs/1958720 Title: python3-yaml and python3-six are not co-installable with python-is- python2 in jammy Status in pyyaml package in Ubuntu: Confirmed Status in six package in Ubuntu: Invalid Bug description: The packages python3-yaml and python-is-python2 are not co-installable in jammy and I believe they should be. This currently prevents me from upgrading one of my machines from focal to jammy. Further analysis with the help of Stefano Rivera revealed that what- is-python no longer produces a python-is-python2 package and the changelog hints at that being intentional. Jammy still has a python2 package, though. python3-yaml in jammy breaks on python (<2.7.18). The python-is- python2 package in focal is version 2.7.17-4 and in impish it is 2.7.18-9 and thus will be forcefully removed when going to jammy. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pyyaml/+bug/1958720/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1959325] Re: New binutils causes build failures for many RISC-V packages
we will not change the ISA for the upcoming 22.04 LTS release, but do the change not before the GCC 12 defaults change planned for 22.10. ** Changed in: binutils (Ubuntu Jammy) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1959325 Title: New binutils causes build failures for many RISC-V packages Status in binutils package in Ubuntu: In Progress Status in binutils source package in Jammy: In Progress Bug description: binutils 2.37.90.20220126-0ubuntu1 changes the -march flags. We see a lot of packages not building in proposed anymore: OpenSBI, ktexteditor, ... Best regards Heinrich To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1959325/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1959325] Re: New binutils causes build failures for many RISC-V packages
adding exact references from IRC logs ... please provide these in the first place. https://launchpadlibrarian.net/582482377/buildlog_ubuntu-jammy- riscv64.ktexteditor_5.90.0-0ubuntu2_BUILDING.txt.gz" -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1959325 Title: New binutils causes build failures for many RISC-V packages Status in binutils package in Ubuntu: Confirmed Status in binutils source package in Jammy: Confirmed Bug description: binutils 2.37.90.20220126-0ubuntu1 changes the -march flags. We see a lot of packages not building in proposed anymore: OpenSBI, ktexteditor, ... Best regards Heinrich To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1959325/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1958389] Re: Jammy builds of xen segfault, but only on launchpad x86 builders
** Bug watch added: Sourceware.org Bugzilla #28826 https://sourceware.org/bugzilla/show_bug.cgi?id=28826 ** Also affects: binutils via https://sourceware.org/bugzilla/show_bug.cgi?id=28826 Importance: Unknown Status: Unknown ** Bug watch added: Debian Bug tracker #1004269 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004269 ** Also affects: binutils (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004269 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1958389 Title: Jammy builds of xen segfault, but only on launchpad x86 builders Status in binutils: Unknown Status in launchpad-buildd: New Status in binutils package in Ubuntu: New Status in xen package in Ubuntu: Invalid Status in binutils package in Debian: Unknown Bug description: FTBFS in Jammy on LP infra: https://launchpadlibrarian.net/580924961/buildlog_ubuntu-jammy-amd64.xen_4.16.0-1~ubuntu1~jammyppa4_BUILDING.txt.gz https://launchpadlibrarian.net/581060687/buildlog_ubuntu-jammy-amd64.xen_4.16.0-1~ubuntu1~jammyppa6_BUILDING.txt.gz Related PPA: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4760/+packages Summary: - Build reliably fails on LP - Build in local sbuild works reliably on my Laptop - Build in local VM (sizing like LP builders) works (other crashes but works) - Build on AMD server (chip more similar to LP) works reliably Failing step: On Launchpad build infrastructure it breaks on ld: $ x86_64-linux-gnu-ld -mi386pep --subsystem=10 --image-base=0x82d04000 --stack=0,0 --heap=0,0 --section-alignment=0x20 --file-alignment=0x20 --major-image-version=4 --minor-image-version=16 --major-os-version=2 --minor-os-version=0 --major-subsystem-version=2 --minor-subsystem-version=0 --no-insert-timestamp --build-id=sha1 -T efi.lds -N prelink.o /<>/xen/common/symbols-dummy.o -b pe-x86-64 efi/buildid.o -o /<>/xen/.xen.efi.0x82d04000.0 && : Segmentation fault (core dumped --- Steps to recreate (result depends on platform) # you can grab the package from https://launchpad.net/~ci-train-ppa- service/+archive/ubuntu/4760/+packages sudo vim /etc/apt/sources.list sudo apt update sudo apt dist-upgrade -y sudo apt build-dep xen sudo apt install flex bison python3-dev libpython3-dev dpkg-dev devscripts apport-retrace sudo mkdir /mnt/build sudo chmod go+w /mnt/build cd /mnt/build # copy in things from host scp xen_4.16.0-1~ubuntu1~jammyppa6.dsc xen_4.16.0-1~ubuntu1~jammyppa6.debian.tar.xz xen_4.16.0.orig.tar.bz2 ubuntu@:/mnt/build dpkg-source -x xen_4.16.0-1~ubuntu1~jammyppa6.dsc xen_4.16.0 cd xen_4.16.0 dpkg-buildpackage -i -us -uc -b --- In a jammy VM 4cpu/8G I get some avx2 crashes but the build works: Jan 19 07:41:27 j kernel: x86_64-linux-gn[130016]: segfault at 0 ip 7f189432ef3d sp 7ffc8e2361d8 error 4 in libc.so.6[7f18941bb000+194000] Jan 19 07:41:27 j kernel: Code: f8 77 c3 66 2e 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 89 f8 48 89 fa c5 f9 ef c0 25 ff 0f 00 00 3d e0 0f 00 00 0f 87 33 01 00 00 fd 74 0f c5 fd d7 c1 85 c0 74 57 f3 0f bc c0 c5 f8 77 c3 66 66 #0 __strlen_avx2 () at ../sysdeps/x86_64/multiarch/strlen-avx2.S:74 74../sysdeps/x86_64/multiarch/strlen-avx2.S: No such file or directory. (gdb) bt #0 __strlen_avx2 () at ../sysdeps/x86_64/multiarch/strlen-avx2.S:74 #1 0x7fa98d63c2d0 in ?? () from /lib/x86_64-linux-gnu/libbfd-2.37.50-system.20220106.so #2 0x7fa98d6021e8 in ?? () from /lib/x86_64-linux-gnu/libbfd-2.37.50-system.20220106.so #3 0x7fa98d602509 in coff_write_alien_symbol () from /lib/x86_64-linux-gnu/libbfd-2.37.50-system.20220106.so #4 0x7fa98d6033bd in _bfd_coff_final_link () from /lib/x86_64-linux-gnu/libbfd-2.37.50-system.20220106.so #5 0x562bdaaae3bf in ?? () #6 0x7fa98d2e8fd0 in __libc_start_call_main (main=main@entry=0x562bdaaad5e0, argc=argc@entry=8, argv=argv@entry=0x7ffc797f2968) at ../sysdeps/nptl/libc_start_call_main.h:58 #7 0x7fa98d2e907d in __libc_start_main_impl (main=0x562bdaaad5e0, argc=8, argv=0x7ffc797f2968, init=, fini=, rtld_fini=, stack_end=0x7ffc797f2958) at ../csu/libc-start.c:409 #8 0x562bdaaad515 in ?? () ^^ that is a different crash than on th LP builders ! And despite those crashes the build does appear to work oO?! The same crashes I see on my local sbuild runs, the full set of one build is Jan 19 07:39:02 Keschdeichel kernel: x86_64-linux-gn[4131180]: segfault at 0 ip 7f566e8b3f3d sp 7ffde04b75a8 error 4 in libc.so.6[7f566e74+194000] Jan 19 07:39:03 Keschdeichel kernel: x86_64-linux-gn[4131332]: segfault at 0 ip 7fbba26e4f3d sp 7fffab8a5b68 error 4 in libc.so.6[7fbba2571000+194000] Jan 19 07:39:03 Keschdeichel kernel: x86_64-linux-gn[413
[Touch-packages] [Bug 1946965] Re: python3-defaults: py3versions -i does not list python3.10 when it is installed
Removing packages from impish-proposed: python3-defaults 3.9.4-1ubuntu1 in impish 2to3 3.9.4-1ubuntu1 in impish amd64 2to3 3.9.4-1ubuntu1 in impish arm64 2to3 3.9.4-1ubuntu1 in impish armhf 2to3 3.9.4-1ubuntu1 in impish i386 2to3 3.9.4-1ubuntu1 in impish ppc64el 2to3 3.9.4-1ubuntu1 in impish riscv64 2to3 3.9.4-1ubuntu1 in impish s390x idle 3.9.4-1ubuntu1 in impish amd64 idle 3.9.4-1ubuntu1 in impish arm64 idle 3.9.4-1ubuntu1 in impish armhf idle 3.9.4-1ubuntu1 in impish i386 idle 3.9.4-1ubuntu1 in impish ppc64el idle 3.9.4-1ubuntu1 in impish riscv64 idle 3.9.4-1ubuntu1 in impish s390x idle3 3.9.4-1ubuntu1 in impish amd64 idle3 3.9.4-1ubuntu1 in impish arm64 idle3 3.9.4-1ubuntu1 in impish armhf idle3 3.9.4-1ubuntu1 in impish i386 idle3 3.9.4-1ubuntu1 in impish ppc64el idle3 3.9.4-1ubuntu1 in impish riscv64 idle3 3.9.4-1ubuntu1 in impish s390x libpython3-all-dbg 3.9.4-1ubuntu1 in impish amd64 libpython3-all-dbg 3.9.4-1ubuntu1 in impish arm64 libpython3-all-dbg 3.9.4-1ubuntu1 in impish armhf libpython3-all-dbg 3.9.4-1ubuntu1 in impish i386 libpython3-all-dbg 3.9.4-1ubuntu1 in impish ppc64el libpython3-all-dbg 3.9.4-1ubuntu1 in impish riscv64 libpython3-all-dbg 3.9.4-1ubuntu1 in impish s390x libpython3-all-dev 3.9.4-1ubuntu1 in impish amd64 libpython3-all-dev 3.9.4-1ubuntu1 in impish arm64 libpython3-all-dev 3.9.4-1ubuntu1 in impish armhf libpython3-all-dev 3.9.4-1ubuntu1 in impish i386 libpython3-all-dev 3.9.4-1ubuntu1 in impish ppc64el libpython3-all-dev 3.9.4-1ubuntu1 in impish riscv64 libpython3-all-dev 3.9.4-1ubuntu1 in impish s390x libpython3-dbg 3.9.4-1ubuntu1 in impish amd64 libpython3-dbg 3.9.4-1ubuntu1 in impish arm64 libpython3-dbg 3.9.4-1ubuntu1 in impish armhf libpython3-dbg 3.9.4-1ubuntu1 in impish i386 libpython3-dbg 3.9.4-1ubuntu1 in impish ppc64el libpython3-dbg 3.9.4-1ubuntu1 in impish riscv64 libpython3-dbg 3.9.4-1ubuntu1 in impish s390x libpython3-dev 3.9.4-1ubuntu1 in impish amd64 libpython3-dev 3.9.4-1ubuntu1 in impish arm64 libpython3-dev 3.9.4-1ubuntu1 in impish armhf libpython3-dev 3.9.4-1ubuntu1 in impish i386 libpython3-dev 3.9.4-1ubuntu1 in impish ppc64el libpython3-dev 3.9.4-1ubuntu1 in impish riscv64 libpython3-dev 3.9.4-1ubuntu1 in impish s390x libpython3-stdlib 3.9.4-1ubuntu1 in impish amd64 libpython3-stdlib 3.9.4-1ubuntu1 in impish arm64 libpython3-stdlib 3.9.4-1ubuntu1 in impish armhf libpython3-stdlib 3.9.4-1ubuntu1 in impish i386 libpython3-stdlib 3.9.4-1ubuntu1 in impish ppc64el libpython3-stdlib 3.9.4-1ubuntu1 in impish riscv64 libpython3-stdlib 3.9.4-1ubuntu1 in impish s390x python3 3.9.4-1ubuntu1 in impish amd64 python3 3.9.4-1ubuntu1 in impish arm64 python3 3.9.4-1ubuntu1 in impish armhf python3 3.9.4-1ubuntu1 in impish i386 python3 3.9.4-1ubuntu1 in impish ppc64el python3 3.9.4-1ubuntu1 in impish riscv64 python3 3.9.4-1ubuntu1 in impish s390x python3-all 3.9.4-1ubuntu1 in impish amd64 python3-all 3.9.4-1ubuntu1 in impish arm64 python3-all 3.9.4-1ubuntu1 in impish armhf python3-all 3.9.4-1ubuntu1 in impish i386 python3-all 3.9.4-1ubuntu1 in impish ppc64el python3-all 3.9.4-1ubuntu1 in impish riscv64 python3-all 3.9.4-1ubuntu1 in impish s390x python3-all-dbg 3.9.4-1ubuntu1 in impish amd64 python3-all-dbg 3.9.4-1ubuntu1 in impish arm64 python3-all-dbg 3.9.4-1ubuntu1 in impish armhf python3-all-dbg 3.9.4-1ubuntu1 in impish i386 python3-all-dbg 3.9.4-1ubuntu1 in impish ppc64el python3-all-dbg 3.9.4-1ubuntu1 in impish riscv64 python3-all-dbg 3.9.4-1ubuntu1 in impish s390x python3-all-dev 3.9.4-1ubuntu1 in impish amd64 python3-all-dev 3.9.4-1ubuntu1 in impish arm64 python3-all-dev 3.9.4-1ubuntu1 in impish armhf python3-all-dev 3.9.4-1ubuntu1 in impish i386 python3-all-dev 3.9.4-1u
[Touch-packages] [Bug 1943818] Re: mesa built with -O3 on ppc64el has broken EGL
** Tags added: ppc64el -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1943818 Title: mesa built with -O3 on ppc64el has broken EGL Status in Mesa: Unknown Status in gcc-11 package in Ubuntu: New Status in mesa package in Ubuntu: New Bug description: If mesa is built with -O3 then EGL will fail with: libEGL warning: DRI2: failed to create any config this can be easily reproduced by building libepoxy which then runs a series of tests. The same is fine on amd64, and also ppc64el is fine with gcc-10 and -O3. To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1943818/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1939413] Re: /usr/lib/aarch64-linux-gnu/libprotobuf.a’ generated with LTO version 9.2 instead of the expected 11.0
3.12.4-1ubuntu1 using binutils 2.36 OK 3.12.4-1ubuntu2 BAD -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to protobuf in Ubuntu. https://bugs.launchpad.net/bugs/1939413 Title: /usr/lib/aarch64-linux-gnu/libprotobuf.a’ generated with LTO version 9.2 instead of the expected 11.0 Status in mozc package in Ubuntu: Invalid Status in protobuf package in Ubuntu: New Bug description: When trying to build package mozc for arm64 the following error popped up: lto1: fatal error: bytecode stream in file ‘/usr/lib/aarch64-linux- gnu/libprotobuf.a’ generated with LTO version 9.2 instead of the expected 11.0 Why does the library contain LTO information at all? Best regards Heinrich To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mozc/+bug/1939413/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1939413] Re: /usr/lib/aarch64-linux-gnu/libprotobuf.a’ generated with LTO version 9.2 instead of the expected 11.0
correctly stripped on other architectures, also not stripped in hirsute, so not a regression in impish. ** Tags removed: ftbfs ** Tags added: rls-ii-incoming ** Changed in: protobuf (Ubuntu) Assignee: Matthias Klose (doko) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to protobuf in Ubuntu. https://bugs.launchpad.net/bugs/1939413 Title: /usr/lib/aarch64-linux-gnu/libprotobuf.a’ generated with LTO version 9.2 instead of the expected 11.0 Status in mozc package in Ubuntu: Invalid Status in protobuf package in Ubuntu: New Bug description: When trying to build package mozc for arm64 the following error popped up: lto1: fatal error: bytecode stream in file ‘/usr/lib/aarch64-linux- gnu/libprotobuf.a’ generated with LTO version 9.2 instead of the expected 11.0 Why does the library contain LTO information at all? Best regards Heinrich To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mozc/+bug/1939413/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1939413] Re: /usr/lib/aarch64-linux-gnu/libprotobuf.a’ generated with LTO version 9.2 instead of the expected 11.0
the real problem here is that the package is not stripped at all on arm64. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to protobuf in Ubuntu. https://bugs.launchpad.net/bugs/1939413 Title: /usr/lib/aarch64-linux-gnu/libprotobuf.a’ generated with LTO version 9.2 instead of the expected 11.0 Status in mozc package in Ubuntu: Invalid Status in protobuf package in Ubuntu: New Bug description: When trying to build package mozc for arm64 the following error popped up: lto1: fatal error: bytecode stream in file ‘/usr/lib/aarch64-linux- gnu/libprotobuf.a’ generated with LTO version 9.2 instead of the expected 11.0 Why does the library contain LTO information at all? Best regards Heinrich To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mozc/+bug/1939413/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1939973] Re: make 4.3-4.1 triggers build failures
copied the binary packages to https://launchpad.net/~doko/+archive/ubuntu/toolchain and removed them from impish-proposed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to make-dfsg in Ubuntu. https://bugs.launchpad.net/bugs/1939973 Title: make 4.3-4.1 triggers build failures Status in make-dfsg package in Ubuntu: Confirmed Bug description: trying to rebuild cross-toolchain-base from https://launchpad.net/~ubuntu-toolchain-r/+archive/ubuntu/volatile/+packages triggers a build failure: [...] START stamp-dir/init-binutils tar -x -f /usr/src/binutils/binutils-2.37.tar.xz set -e; cd binutils-2.37 ; cp -a /usr/src/binutils/debian/ . ; if [ -n "$(grep -v '^\#' /<>/debian/patches/binutils/series)" ]; then QUILT_PATCHES=/<>/debian/patches/binutils quilt --quiltrc /dev/null push -a; fi; rm -rf .pc cd binutils-2.37 ; env -i CROSS_ARCHS="amd64 i386 s390x ppc64el arm64 armhf armel powerpc" debian/rules stamps/control make: dpkg-architecture: No such file or directory make: lsb_release: No such file or directory make: lsb_release: No such file or directory make: pwd: No such file or directory make: dpkg-parsechangelog: No such file or directory make: dpkg-parsechangelog: No such file or directory make: dpkg-parsechangelog: No such file or directory make: dpkg-parsechangelog: No such file or directory debian/rules:163: *** unexpected source package name: . Stop. make: *** [debian/rules:215: stamp-dir/init-binutils] Error 2 dpkg-buildpackage.pl: error: debian/rules build subprocess returned exit status 2 working around by omitting the -i option to env, or by setting PATH explicitly. Reverting to the version in the release pocket lets the c-t-b- build succeed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/make-dfsg/+bug/1939973/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
