[Touch-packages] [Bug 1943818] Re: mesa built with -O3 on ppc64el has broken EGL

[Matthias Klose]

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

[Matthias Klose]

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

[Matthias Klose]

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

[Matthias Klose]

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

[Matthias Klose]

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

[Matthias Klose]

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

[Matthias Klose]

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

[Matthias Klose]

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

[Matthias Klose]

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

[Matthias Klose]

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

[Matthias Klose]

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

[Matthias Klose]

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

[Matthias Klose]

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

[Matthias Klose]

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

[Matthias Klose]

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

[Matthias Klose]

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

[Matthias Klose]

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

[Matthias Klose]

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

[Matthias Klose]

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

[Matthias Klose]

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

[Matthias Klose]

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

[Matthias Klose]

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

[Matthias Klose]

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): 

[Touch-packages] [Bug 1971474] [NEW] SRU: Update gdb to the final 12.1 release in 22.04 LTS

[Matthias Klose]

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?

[Matthias Klose]

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

[Matthias Klose]

** 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()

[Matthias Klose]

$ 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()

[Matthias Klose]

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

[Matthias Klose]

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

[Matthias Klose]

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

[Matthias Klose]

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

[Matthias Klose]

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

[Matthias Klose]

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

[Touch-packages] [Bug 1946965] Re: python3-defaults: py3versions -i does not list python3.10 when it is installed

[Matthias Klose]

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 

[Touch-packages] [Bug 1943818] Re: mesa built with -O3 on ppc64el has broken EGL

[Matthias Klose]

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

[Matthias Klose]

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

[Matthias Klose]

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

[Matthias Klose]

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

[Matthias Klose]

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

[Touch-packages] [Bug 1939973] [NEW] make 4.3-4.1 triggers build failures

[Matthias Klose]

Public bug reported:

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.

** Affects: make-dfsg (Ubuntu)
 Importance: High
 Status: Confirmed


** Tags: block-proposed rls-ii-incoming

** Changed in: make-dfsg (Ubuntu)
   Status: New => Confirmed

** Changed in: make-dfsg (Ubuntu)
   Importance: Undecided => High

** Tags added: block-proposed rls-ii-incoming

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

[Touch-packages] [Bug 1939413] Re: /usr/lib/aarch64-linux-gnu/libprotobuf.a’ generated with LTO version 9.2 instead of the expected 11.0

[Matthias Klose]

** Changed in: protobuf (Ubuntu)
   Status: Fix Committed => New

** Changed in: protobuf (Ubuntu)
 Assignee: Gunnar Hjalmarsson (gunnarhj) => Matthias Klose (doko)

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

[Matthias Klose]

rebuilding just hides the issue. need to find out why the lto sections
are in the archive.

-- 
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:
  Fix Committed

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 1934505]

[Matthias Klose]

looking at a 20210706 build, the fix seems to work.  Unsure what I did
wrong yesterday.  So the fix would be needed on the trunk and the
branch.

-- 
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/1934505

Title:
  gdb 11 doesn't work on impish/s390x: internal-error:
  displaced_step_prepare_status linux_displaced_step_prepare(gdbarch*,
  thread_info*, CORE_ADDR&): Assertion
  `gdbarch_data->num_disp_step_buffers > 0' failed.

Status in gdb:
  Confirmed
Status in gdb package in Ubuntu:
  Fix Released

Bug description:
  gdb doesn't work on impish/s390x at the minute. Even if you say 'no'
  to both questions you still can't debug:

  ubuntu@laney-bos01-s390x-2:~/glib-networking-2.66.0/build$ gdb ls
  GNU gdb (Ubuntu 11.0.50.20210630-0ubuntu1) 11.0.50.20210630-git
  Copyright (C) 2021 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.
  Type "show copying" and "show warranty" for details.
  This GDB was configured as "s390x-linux-gnu".
  Type "show configuration" for configuration details.
  For bug reporting instructions, please see:
  .
  Find the GDB manual and other documentation resources online at:
  .

  For help, type "help".
  Type "apropos word" to search for commands related to "word"...
  Reading symbols from ls...
  (No debugging symbols found in ls)
  (gdb) run
  Starting program: /usr/bin/ls
  /build/gdb-Ti35un/gdb-11.0.50.20210630/gdb/linux-tdep.c:2550: internal-error: 
displaced_step_prepare_status linux_displaced_step_prepare(gdbarch*, 
thread_info*, CORE_ADDR&): Assertion `gdbarch_data->num_disp_step_buffers > 0' 
failed.
  A problem internal to GDB has been detected,
  further debugging may prove unreliable.
  Quit this debugging session? (y or n) n

  This is a bug, please report it.  For instructions, see:
  .

  /build/gdb-Ti35un/gdb-11.0.50.20210630/gdb/linux-tdep.c:2550: internal-error: 
displaced_step_prepare_status linux_displaced_step_prepare(gdbarch*, 
thread_info*, CORE_ADDR&): Assertion `gdbarch_data->num_disp_step_buffers > 0' 
failed.
  A problem internal to GDB has been detected,
  further debugging may prove unreliable.
  Create a core file of GDB? (y or n) n
  Command aborted.
  (gdb)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gdb/+bug/1934505/+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 1934505]

[Matthias Klose]

yes, double checked,
https://launchpad.net/ubuntu/+source/gdb/11.0.90.20210705-0ubuntu2/+build/21752179

Ubuntu's compiler enables a few hardening flags by default,
-D_FORTIFY_SOURCE=2 -fstack-protector-strong -Wformat -Werror=format-security
but that's unchanged from the gdb 10.2 build.

-- 
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/1934505

Title:
  gdb 11 doesn't work on impish/s390x: internal-error:
  displaced_step_prepare_status linux_displaced_step_prepare(gdbarch*,
  thread_info*, CORE_ADDR&): Assertion
  `gdbarch_data->num_disp_step_buffers > 0' failed.

Status in gdb:
  Confirmed
Status in gdb package in Ubuntu:
  Fix Released

Bug description:
  gdb doesn't work on impish/s390x at the minute. Even if you say 'no'
  to both questions you still can't debug:

  ubuntu@laney-bos01-s390x-2:~/glib-networking-2.66.0/build$ gdb ls
  GNU gdb (Ubuntu 11.0.50.20210630-0ubuntu1) 11.0.50.20210630-git
  Copyright (C) 2021 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.
  Type "show copying" and "show warranty" for details.
  This GDB was configured as "s390x-linux-gnu".
  Type "show configuration" for configuration details.
  For bug reporting instructions, please see:
  .
  Find the GDB manual and other documentation resources online at:
  .

  For help, type "help".
  Type "apropos word" to search for commands related to "word"...
  Reading symbols from ls...
  (No debugging symbols found in ls)
  (gdb) run
  Starting program: /usr/bin/ls
  /build/gdb-Ti35un/gdb-11.0.50.20210630/gdb/linux-tdep.c:2550: internal-error: 
displaced_step_prepare_status linux_displaced_step_prepare(gdbarch*, 
thread_info*, CORE_ADDR&): Assertion `gdbarch_data->num_disp_step_buffers > 0' 
failed.
  A problem internal to GDB has been detected,
  further debugging may prove unreliable.
  Quit this debugging session? (y or n) n

  This is a bug, please report it.  For instructions, see:
  .

  /build/gdb-Ti35un/gdb-11.0.50.20210630/gdb/linux-tdep.c:2550: internal-error: 
displaced_step_prepare_status linux_displaced_step_prepare(gdbarch*, 
thread_info*, CORE_ADDR&): Assertion `gdbarch_data->num_disp_step_buffers > 0' 
failed.
  A problem internal to GDB has been detected,
  further debugging may prove unreliable.
  Create a core file of GDB? (y or n) n
  Command aborted.
  (gdb)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gdb/+bug/1934505/+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 1934505] Re: gdb 11 doesn't work on impish/s390x: internal-error: displaced_step_prepare_status linux_displaced_step_prepare(gdbarch*, thread_info*, CORE_ADDR&): Assertion `gdbar

[Matthias Klose]

fixed in 11.0.90.20210705-0ubuntu2

** Changed in: gdb (Ubuntu)
   Status: Confirmed => Fix Released

-- 
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/1934505

Title:
  gdb 11 doesn't work on impish/s390x: internal-error:
  displaced_step_prepare_status linux_displaced_step_prepare(gdbarch*,
  thread_info*, CORE_ADDR&): Assertion
  `gdbarch_data->num_disp_step_buffers > 0' failed.

Status in gdb:
  Confirmed
Status in gdb package in Ubuntu:
  Fix Released

Bug description:
  gdb doesn't work on impish/s390x at the minute. Even if you say 'no'
  to both questions you still can't debug:

  ubuntu@laney-bos01-s390x-2:~/glib-networking-2.66.0/build$ gdb ls
  GNU gdb (Ubuntu 11.0.50.20210630-0ubuntu1) 11.0.50.20210630-git
  Copyright (C) 2021 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.
  Type "show copying" and "show warranty" for details.
  This GDB was configured as "s390x-linux-gnu".
  Type "show configuration" for configuration details.
  For bug reporting instructions, please see:
  .
  Find the GDB manual and other documentation resources online at:
  .

  For help, type "help".
  Type "apropos word" to search for commands related to "word"...
  Reading symbols from ls...
  (No debugging symbols found in ls)
  (gdb) run
  Starting program: /usr/bin/ls
  /build/gdb-Ti35un/gdb-11.0.50.20210630/gdb/linux-tdep.c:2550: internal-error: 
displaced_step_prepare_status linux_displaced_step_prepare(gdbarch*, 
thread_info*, CORE_ADDR&): Assertion `gdbarch_data->num_disp_step_buffers > 0' 
failed.
  A problem internal to GDB has been detected,
  further debugging may prove unreliable.
  Quit this debugging session? (y or n) n

  This is a bug, please report it.  For instructions, see:
  .

  /build/gdb-Ti35un/gdb-11.0.50.20210630/gdb/linux-tdep.c:2550: internal-error: 
displaced_step_prepare_status linux_displaced_step_prepare(gdbarch*, 
thread_info*, CORE_ADDR&): Assertion `gdbarch_data->num_disp_step_buffers > 0' 
failed.
  A problem internal to GDB has been detected,
  further debugging may prove unreliable.
  Create a core file of GDB? (y or n) n
  Command aborted.
  (gdb)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gdb/+bug/1934505/+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 1934505]

[Matthias Klose]

no, that patch doesn't help.  the gdb 10.2 build was fine, working
correctly.

gdb: configured with: --build=s390x-linux-gnu
 --host=s390x-linux-gnu
 --prefix=/usr
 --libexecdir=${prefix}/lib/gdb
 --disable-werror
 --disable-maintainer-mode
 --disable-dependency-tracking
 --disable-silent-rules
 --disable-gdbtk
 --disable-shared
 --with-system-readline
 --with-pkgversion='Ubuntu 11.0.90.20210705-0ubuntu2'
 --srcdir=/<>
 --with-expat
 --with-system-zlib
 --without-guile
 --without-babeltrace
 --with-debuginfod
 --with-babeltrace
 --with-system-gdbinit=/etc/gdb/gdbinit
 --with-system-gdbinit-dir=/etc/gdb/gdbinit.d
 --enable-tui
 --with-lzma
 --with-python=python3
 --with-xxhash
 --with-mpfr

-- 
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/1934505

Title:
  gdb 11 doesn't work on impish/s390x: internal-error:
  displaced_step_prepare_status linux_displaced_step_prepare(gdbarch*,
  thread_info*, CORE_ADDR&): Assertion
  `gdbarch_data->num_disp_step_buffers > 0' failed.

Status in gdb:
  Confirmed
Status in gdb package in Ubuntu:
  Confirmed

Bug description:
  gdb doesn't work on impish/s390x at the minute. Even if you say 'no'
  to both questions you still can't debug:

  ubuntu@laney-bos01-s390x-2:~/glib-networking-2.66.0/build$ gdb ls
  GNU gdb (Ubuntu 11.0.50.20210630-0ubuntu1) 11.0.50.20210630-git
  Copyright (C) 2021 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.
  Type "show copying" and "show warranty" for details.
  This GDB was configured as "s390x-linux-gnu".
  Type "show configuration" for configuration details.
  For bug reporting instructions, please see:
  .
  Find the GDB manual and other documentation resources online at:
  .

  For help, type "help".
  Type "apropos word" to search for commands related to "word"...
  Reading symbols from ls...
  (No debugging symbols found in ls)
  (gdb) run
  Starting program: /usr/bin/ls
  /build/gdb-Ti35un/gdb-11.0.50.20210630/gdb/linux-tdep.c:2550: internal-error: 
displaced_step_prepare_status linux_displaced_step_prepare(gdbarch*, 
thread_info*, CORE_ADDR&): Assertion `gdbarch_data->num_disp_step_buffers > 0' 
failed.
  A problem internal to GDB has been detected,
  further debugging may prove unreliable.
  Quit this debugging session? (y or n) n

  This is a bug, please report it.  For instructions, see:
  .

  /build/gdb-Ti35un/gdb-11.0.50.20210630/gdb/linux-tdep.c:2550: internal-error: 
displaced_step_prepare_status linux_displaced_step_prepare(gdbarch*, 
thread_info*, CORE_ADDR&): Assertion `gdbarch_data->num_disp_step_buffers > 0' 
failed.
  A problem internal to GDB has been detected,
  further debugging may prove unreliable.
  Create a core file of GDB? (y or n) n
  Command aborted.
  (gdb)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gdb/+bug/1934505/+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 1934505]

[Matthias Klose]

for a s390x setup, maybe see
https://developer.ibm.com/components/ibm-linuxone/gettingstarted/

-- 
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/1934505

Title:
  gdb 11 doesn't work on impish/s390x: internal-error:
  displaced_step_prepare_status linux_displaced_step_prepare(gdbarch*,
  thread_info*, CORE_ADDR&): Assertion
  `gdbarch_data->num_disp_step_buffers > 0' failed.

Status in gdb:
  Confirmed
Status in gdb package in Ubuntu:
  Confirmed

Bug description:
  gdb doesn't work on impish/s390x at the minute. Even if you say 'no'
  to both questions you still can't debug:

  ubuntu@laney-bos01-s390x-2:~/glib-networking-2.66.0/build$ gdb ls
  GNU gdb (Ubuntu 11.0.50.20210630-0ubuntu1) 11.0.50.20210630-git
  Copyright (C) 2021 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.
  Type "show copying" and "show warranty" for details.
  This GDB was configured as "s390x-linux-gnu".
  Type "show configuration" for configuration details.
  For bug reporting instructions, please see:
  .
  Find the GDB manual and other documentation resources online at:
  .

  For help, type "help".
  Type "apropos word" to search for commands related to "word"...
  Reading symbols from ls...
  (No debugging symbols found in ls)
  (gdb) run
  Starting program: /usr/bin/ls
  /build/gdb-Ti35un/gdb-11.0.50.20210630/gdb/linux-tdep.c:2550: internal-error: 
displaced_step_prepare_status linux_displaced_step_prepare(gdbarch*, 
thread_info*, CORE_ADDR&): Assertion `gdbarch_data->num_disp_step_buffers > 0' 
failed.
  A problem internal to GDB has been detected,
  further debugging may prove unreliable.
  Quit this debugging session? (y or n) n

  This is a bug, please report it.  For instructions, see:
  .

  /build/gdb-Ti35un/gdb-11.0.50.20210630/gdb/linux-tdep.c:2550: internal-error: 
displaced_step_prepare_status linux_displaced_step_prepare(gdbarch*, 
thread_info*, CORE_ADDR&): Assertion `gdbarch_data->num_disp_step_buffers > 0' 
failed.
  A problem internal to GDB has been detected,
  further debugging may prove unreliable.
  Create a core file of GDB? (y or n) n
  Command aborted.
  (gdb)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gdb/+bug/1934505/+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 1934505] Re: gdb 11 doesn't work on impish: internal-error: displaced_step_prepare_status linux_displaced_step_prepare(gdbarch*, thread_info*, CORE_ADDR&): Assertion `gdbarch_dat

[Matthias Klose]

** Bug watch added: Sourceware.org Bugzilla #28056
   https://sourceware.org/bugzilla/show_bug.cgi?id=28056

** Also affects: gdb via
   https://sourceware.org/bugzilla/show_bug.cgi?id=28056
   Importance: Unknown
   Status: Unknown

** Changed in: gdb (Ubuntu)
   Status: New => Confirmed

** Changed in: gdb (Ubuntu)
   Importance: Undecided => High

-- 
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/1934505

Title:
  gdb 11 doesn't work on impish: internal-error:
  displaced_step_prepare_status linux_displaced_step_prepare(gdbarch*,
  thread_info*, CORE_ADDR&): Assertion
  `gdbarch_data->num_disp_step_buffers > 0' failed.

Status in gdb:
  Unknown
Status in gdb package in Ubuntu:
  Confirmed

Bug description:
  gdb doesn't work on impish/s390x at the minute. Even if you say 'no'
  to both questions you still can't debug:

  ubuntu@laney-bos01-s390x-2:~/glib-networking-2.66.0/build$ gdb ls
  GNU gdb (Ubuntu 11.0.50.20210630-0ubuntu1) 11.0.50.20210630-git
  Copyright (C) 2021 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.
  Type "show copying" and "show warranty" for details.
  This GDB was configured as "s390x-linux-gnu".
  Type "show configuration" for configuration details.
  For bug reporting instructions, please see:
  .
  Find the GDB manual and other documentation resources online at:
  .

  For help, type "help".
  Type "apropos word" to search for commands related to "word"...
  Reading symbols from ls...
  (No debugging symbols found in ls)
  (gdb) run
  Starting program: /usr/bin/ls
  /build/gdb-Ti35un/gdb-11.0.50.20210630/gdb/linux-tdep.c:2550: internal-error: 
displaced_step_prepare_status linux_displaced_step_prepare(gdbarch*, 
thread_info*, CORE_ADDR&): Assertion `gdbarch_data->num_disp_step_buffers > 0' 
failed.
  A problem internal to GDB has been detected,
  further debugging may prove unreliable.
  Quit this debugging session? (y or n) n

  This is a bug, please report it.  For instructions, see:
  .

  /build/gdb-Ti35un/gdb-11.0.50.20210630/gdb/linux-tdep.c:2550: internal-error: 
displaced_step_prepare_status linux_displaced_step_prepare(gdbarch*, 
thread_info*, CORE_ADDR&): Assertion `gdbarch_data->num_disp_step_buffers > 0' 
failed.
  A problem internal to GDB has been detected,
  further debugging may prove unreliable.
  Create a core file of GDB? (y or n) n
  Command aborted.
  (gdb)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gdb/+bug/1934505/+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 1933775]

[Matthias Klose]

No, the gcc packages don't depend on any tbb package.  Probably tbb
needs an update to a new upstream version in the distro.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tbb in Ubuntu.
https://bugs.launchpad.net/bugs/1933775

Title:
  libgcc-s1 and libstdc++6 depend on broken libtbb2 package

Status in gcc:
  In Progress
Status in tbb package in Ubuntu:
  New

Bug description:
  The gcc-11 source package produces libgcc-s1 and (I think?)
  libstdc++6. Both of these binary packages on Hirsute depend on libtbb2
  version 2020.3-1. The latter contains deprecated APIs that create
  #pragma generated warnings whenever  is included.

  See upstream for discussion:

  https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101228

To manage notifications about this bug go to:
https://bugs.launchpad.net/gcc/+bug/1933775/+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 1933775] Re: libgcc-s1 and libstdc++6 depend on broken libtbb2 package

[Matthias Klose]

No gcc package depends on libtbb2

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tbb in Ubuntu.
https://bugs.launchpad.net/bugs/1933775

Title:
  libgcc-s1 and libstdc++6 depend on broken libtbb2 package

Status in gcc:
  Confirmed
Status in tbb package in Ubuntu:
  New

Bug description:
  The gcc-11 source package produces libgcc-s1 and (I think?)
  libstdc++6. Both of these binary packages on Hirsute depend on libtbb2
  version 2020.3-1. The latter contains deprecated APIs that create
  #pragma generated warnings whenever  is included.

  See upstream for discussion:

  https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101228

To manage notifications about this bug go to:
https://bugs.launchpad.net/gcc/+bug/1933775/+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 1933775] Re: libgcc-s1 and libstdc++6 depend on broken libtbb2 package

[Matthias Klose]

No, see the upstream issue. A new tbb upstream version is needed.


** Package changed: gcc-11 (Ubuntu) => tbb (Ubuntu)

** Tags removed: deprecated execution gcc intel libstdc++ pragma tbb warning
** Tags added: rls-ii-incoming

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tbb in Ubuntu.
https://bugs.launchpad.net/bugs/1933775

Title:
  libgcc-s1 and libstdc++6 depend on broken libtbb2 package

Status in gcc:
  Confirmed
Status in tbb package in Ubuntu:
  New

Bug description:
  The gcc-11 source package produces libgcc-s1 and (I think?)
  libstdc++6. Both of these binary packages on Hirsute depend on libtbb2
  version 2020.3-1. The latter contains deprecated APIs that create
  #pragma generated warnings whenever  is included.

  See upstream for discussion:

  https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101228

To manage notifications about this bug go to:
https://bugs.launchpad.net/gcc/+bug/1933775/+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

Re: [Touch-packages] [Bug 1927192] Re: gdb ftbfs on armhf, testsuite timeouts

[Matthias Klose]

On 5/31/21 8:03 PM, Balint Reczey wrote:
> @doko would it be enough keep ld-* unstripped on armhf and armel only?

sure, that would fix the immediate issue. but is there a reason why you don't
want to have this across all architectures, or is this meant just for the 
backports?

-- 
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/1927192

Title:
  gdb ftbfs on armhf, testsuite timeouts

Status in gdb:
  Incomplete
Status in gdb package in Ubuntu:
  Fix Released
Status in glibc package in Ubuntu:
  Fix Committed
Status in gdb source package in Focal:
  New
Status in glibc source package in Focal:
  New
Status in gdb source package in Groovy:
  New
Status in glibc source package in Groovy:
  New
Status in gdb source package in Hirsute:
  New
Status in glibc source package in Hirsute:
  New
Status in gdb source package in Impish:
  Fix Released
Status in glibc source package in Impish:
  Fix Committed

Bug description:
  see https://launchpad.net/ubuntu/+source/gdb/10.2-0ubuntu3

  $ zcat buildlog_ubuntu-impish-armhf.gdb_10.2-0ubuntu3_BUILDING.txt.gz | fgrep 
'(timeout)'|wc -l
  10451

To manage notifications about this bug go to:
https://bugs.launchpad.net/gdb/+bug/1927192/+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 1152187] Re: [MIR] systemd

[Matthias Klose]

we usually don't require MIRs for new binary packages.  Please just make
sure that the security team knows about the added binary in bionic, and
then we can promote it.

** Changed in: systemd (Ubuntu Bionic)
   Status: New => Incomplete

-- 
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/1152187

Title:
  [MIR] systemd

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Bionic:
  Incomplete

Bug description:
  * The package is in universe and built on all archs:
  https://launchpad.net/ubuntu/+source/systemd/44-10ubuntu1

  * Rationale:

  - in a first step we want systemd-services promoted to replace ubuntu-
  system-services

  -  We will also want to move from consolekit to logind soon
  (https://blueprints.launchpad.net/ubuntu/+spec/foundations-1303
  -consolekit-logind-migration)

  - udev has been merged in the systemd source upstream so we will want
  to build it from there at some point as well

  we don't plan to use the systemd init system at this point

  * Security:

  there has been some security issues in the past
  http://secunia.com/advisories/search/?search=systemd
  http://secunia.com/advisories/48220/
  http://secunia.com/advisories/48208/
  http://secunia.com/advisories/48331/

  Those are mostly logind issue and have been fixed upstream.

  Our current package is outdated but we do plan to update it before
  starting using logind. There should be no issue with the services

  * Quality:
  - there is no RC bug in debian: 
http://bugs.debian.org/cgi-bin/pkgreport.cgi?repeatmerged=no=systemd
  - there is no bug open in launchpad: 
https://launchpad.net/ubuntu/+source/systemd/+bugs
  - upstream is active and responsive to issues

  The desktop bugs team is subscribed to the package in launchpad,
  foundations/desktop will maintain the package and look to the bug
  reports regularly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1152187/+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 1927192] Re: gdb ftbfs on armhf, testsuite timeouts

[Matthias Klose]

No, you would need to provide symlinks for all variants, for the real
file and all the symlinks.

The unstripped ld.so is 220k, the stripped one 192k. So these 28k look
pretty marginal to add, and I wouldn't see this a regression in size.

Attaching the diff that already is in the glibc in impish.  I don't see
regression potential with this patch.


** Patch added: "ld.diff"
   
https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1927192/+attachment/5498947/+files/ld.diff

-- 
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/1927192

Title:
  gdb ftbfs on armhf, testsuite timeouts

Status in gdb:
  Incomplete
Status in gdb package in Ubuntu:
  Fix Released
Status in glibc package in Ubuntu:
  Fix Committed
Status in gdb source package in Focal:
  New
Status in glibc source package in Focal:
  New
Status in gdb source package in Groovy:
  New
Status in glibc source package in Groovy:
  New
Status in gdb source package in Hirsute:
  New
Status in glibc source package in Hirsute:
  New
Status in gdb source package in Impish:
  Fix Released
Status in glibc source package in Impish:
  Fix Committed

Bug description:
  see https://launchpad.net/ubuntu/+source/gdb/10.2-0ubuntu3

  $ zcat buildlog_ubuntu-impish-armhf.gdb_10.2-0ubuntu3_BUILDING.txt.gz | fgrep 
'(timeout)'|wc -l
  10451

To manage notifications about this bug go to:
https://bugs.launchpad.net/gdb/+bug/1927192/+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 1927192]

[Matthias Klose]

or 3) make sure that the detached debug information for ld.so is
available and can be found.

-- 
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/1927192

Title:
  gdb ftbfs on armhf, testsuite timeouts

Status in gdb:
  Incomplete
Status in gdb package in Ubuntu:
  Fix Released
Status in glibc package in Ubuntu:
  Fix Committed
Status in gdb source package in Focal:
  New
Status in glibc source package in Focal:
  New
Status in gdb source package in Groovy:
  New
Status in glibc source package in Groovy:
  New
Status in gdb source package in Hirsute:
  New
Status in glibc source package in Hirsute:
  New
Status in gdb source package in Impish:
  Fix Released
Status in glibc source package in Impish:
  Fix Committed

Bug description:
  see https://launchpad.net/ubuntu/+source/gdb/10.2-0ubuntu3

  $ zcat buildlog_ubuntu-impish-armhf.gdb_10.2-0ubuntu3_BUILDING.txt.gz | fgrep 
'(timeout)'|wc -l
  10451

To manage notifications about this bug go to:
https://bugs.launchpad.net/gdb/+bug/1927192/+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 1927192] Re: gdb ftbfs on armhf, testsuite timeouts

[Matthias Klose]

see also
https://sourceware.org/pipermail/libc-alpha/2021-May/126011.html

so not stripping ld.so

-- 
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/1927192

Title:
  gdb ftbfs on armhf, testsuite timeouts

Status in gdb:
  Incomplete
Status in gdb package in Ubuntu:
  Fix Released
Status in glibc package in Ubuntu:
  Fix Committed
Status in gdb source package in Focal:
  New
Status in glibc source package in Focal:
  New
Status in gdb source package in Groovy:
  New
Status in glibc source package in Groovy:
  New
Status in gdb source package in Hirsute:
  New
Status in glibc source package in Hirsute:
  New
Status in gdb source package in Impish:
  Fix Released
Status in glibc source package in Impish:
  Fix Committed

Bug description:
  see https://launchpad.net/ubuntu/+source/gdb/10.2-0ubuntu3

  $ zcat buildlog_ubuntu-impish-armhf.gdb_10.2-0ubuntu3_BUILDING.txt.gz | fgrep 
'(timeout)'|wc -l
  10451

To manage notifications about this bug go to:
https://bugs.launchpad.net/gdb/+bug/1927192/+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 1927192] Re: gdb ftbfs on armhf, testsuite timeouts

[Matthias Klose]

It's ok to strip glibc/ld.so on armhf, but then gdb needs to be able to
find the debug symbols.

For impish,

 - call dh_strip in glibc with current debhelper, not compat 8,
   so that the build-id's are resolved by build file system
   layout, not the original file names. That's already done in
   glibc 2.33-0ubuntu6

 - let the gdb build depend on libc6-dbg on armhf, also let
   gdb depend on libc6-dbg on armhf, instead of recommending
   it.

The alternative is not to strip glibc's ld.so on armhf, as Luis
suggested.


** Also affects: gdb (Ubuntu Hirsute)
   Importance: Undecided
   Status: New

** Also affects: gdb (Ubuntu Groovy)
   Importance: Undecided
   Status: New

** Also affects: gdb (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Also affects: glibc (Ubuntu)
   Importance: Undecided
   Status: New

** Tags added: rls-ff-incoming rls-gg-incoming rls-hh-incoming

** Changed in: glibc (Ubuntu Impish)
   Status: New => Fix Committed

** Changed in: gdb (Ubuntu Impish)
   Status: Confirmed => 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/1927192

Title:
  gdb ftbfs on armhf, testsuite timeouts

Status in gdb:
  Incomplete
Status in gdb package in Ubuntu:
  Fix Committed
Status in glibc package in Ubuntu:
  Fix Committed
Status in gdb source package in Focal:
  New
Status in glibc source package in Focal:
  New
Status in gdb source package in Groovy:
  New
Status in glibc source package in Groovy:
  New
Status in gdb source package in Hirsute:
  New
Status in glibc source package in Hirsute:
  New
Status in gdb source package in Impish:
  Fix Committed
Status in glibc source package in Impish:
  Fix Committed

Bug description:
  see https://launchpad.net/ubuntu/+source/gdb/10.2-0ubuntu3

  $ zcat buildlog_ubuntu-impish-armhf.gdb_10.2-0ubuntu3_BUILDING.txt.gz | fgrep 
'(timeout)'|wc -l
  10451

To manage notifications about this bug go to:
https://bugs.launchpad.net/gdb/+bug/1927192/+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 1926934]

[Matthias Klose]

this is "fixed" in the glibc 2.33 branch, if I understand the glibc
maintainers correctly, they consider this as a workaround (see PR27744).

-- 
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/1926934

Title:
  gdb batch calls time out on armhf

Status in gdb:
  Confirmed
Status in gdb package in Ubuntu:
  New

Bug description:
  seen when trying to build the gcc-10, or gcc-snapshot packages.  A lot
  of tests in the guality test suite time out after 300 seconds (the
  default dejagnu timeout). These tests, like pr36728-1.c run ok on
  other architectures (and fail), but timeout on armhf.

  Seen in impish with gcc-10 and gcc-snapshot.

  Trying to run the gdb 10.2 tests on both hirsute and impish, I see a
  lot of timeouts as well.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gdb/+bug/1926934/+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 1927192] Re: gdb ftbfs on armhf, testsuite timeouts

[Matthias Klose]

** Bug watch added: Sourceware.org Bugzilla #27826
   https://sourceware.org/bugzilla/show_bug.cgi?id=27826

** Also affects: gdb via
   https://sourceware.org/bugzilla/show_bug.cgi?id=27826
   Importance: Unknown
   Status: Unknown

-- 
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/1927192

Title:
  gdb ftbfs on armhf, testsuite timeouts

Status in gdb:
  Unknown
Status in gdb package in Ubuntu:
  Confirmed

Bug description:
  see https://launchpad.net/ubuntu/+source/gdb/10.2-0ubuntu3

  $ zcat buildlog_ubuntu-impish-armhf.gdb_10.2-0ubuntu3_BUILDING.txt.gz | fgrep 
'(timeout)'|wc -l
  10451

To manage notifications about this bug go to:
https://bugs.launchpad.net/gdb/+bug/1927192/+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 1927192] [NEW] gdb ftbfs on armhf, testsuite timeouts

[Matthias Klose]

Public bug reported:

see https://launchpad.net/ubuntu/+source/gdb/10.2-0ubuntu3

$ zcat buildlog_ubuntu-impish-armhf.gdb_10.2-0ubuntu3_BUILDING.txt.gz | fgrep 
'(timeout)'|wc -l
10451

** Affects: gdb (Ubuntu)
 Importance: High
 Status: Confirmed


** Tags: ftbfs rls-ii-incoming

** Tags added: ftbfs

** Changed in: gdb (Ubuntu)
   Status: New => Confirmed

** Changed in: gdb (Ubuntu)
   Importance: Undecided => High

** Tags added: rls-ii-incoming

** Summary changed:

- gdb ftbfs on armha, tessuite timeouts
+ gdb ftbfs on armhf, testsuite timeouts

-- 
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/1927192

Title:
  gdb ftbfs on armhf, testsuite timeouts

Status in gdb package in Ubuntu:
  Confirmed

Bug description:
  see https://launchpad.net/ubuntu/+source/gdb/10.2-0ubuntu3

  $ zcat buildlog_ubuntu-impish-armhf.gdb_10.2-0ubuntu3_BUILDING.txt.gz | fgrep 
'(timeout)'|wc -l
  10451

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1927192/+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 1926934] Re: gdb batch calls time out on armhf

[Matthias Klose]

** Tags added: ftbfs

-- 
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/1926934

Title:
  gdb batch calls time out on armhf

Status in gdb:
  Confirmed
Status in gdb package in Ubuntu:
  New

Bug description:
  seen when trying to build the gcc-10, or gcc-snapshot packages.  A lot
  of tests in the guality test suite time out after 300 seconds (the
  default dejagnu timeout). These tests, like pr36728-1.c run ok on
  other architectures (and fail), but timeout on armhf.

  Seen in impish with gcc-10 and gcc-snapshot.

  Trying to run the gdb 10.2 tests on both hirsute and impish, I see a
  lot of timeouts as well.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gdb/+bug/1926934/+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 1927070] Re: stack-overflow on GNU libiberty/rust-demangle.c:1024 demangle_type

[Matthias Klose]

what value do these bug reports have?  did you file these upstream? it's
also not clear which version you are testing

** 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/1927070

Title:
  stack-overflow on GNU libiberty/rust-demangle.c:1024 demangle_type

Status in binutils package in Ubuntu:
  Incomplete

Bug description:
  stack-overflowon GNU libiberty/rust-demangle.c:84 peek when we run 
  cat /crashes/poc | ./cxxfilt
  /crashes/poc:
  
F}��.]]��_RYFB1_��z^A^R]M�^?N�^K^]�J^@^@^@^@^@^@^@^@�^A^@��]^yCo#Mo?NCgyCo7MoPggCo~NMG^P#��=^F~@c�Cqot�_ZooSk;^]���]^yCo7Mo?NCgyCo7MoPggCo~NMG^P#^R�7Cg^V^A_���^?^@^A�_ZooSoBbg6^@g^_�@gg��g!T^[

  asan output:
  root@f960c0e3747a:cat /crashes/poc | ./cxxfilt 
  ASAN:SIGSEGV
  =
  ==35495==ERROR: AddressSanitizer: stack-overflow on address 0x7ffcda322ff8 
(pc 0x006a0e3f bp 0x7ffcda323000 sp 0x7ffcda322ff0 T0)
  #0 0x6a0e3e in peek rust-demangle.c:84
  #1 0x6a0f96 in next rust-demangle.c:105
  #2 0x6a478f in demangle_type rust-demangle.c:864
  #3 0x6a5110 in demangle_type rust-demangle.c:1024
  #4 0x6a5110 in demangle_type rust-demangle.c:1024
  #5 0x6a5110 in demangle_type rust-demangle.c:1024
  #6 0x6a5110 in demangle_type rust-demangle.c:1024
  #7 0x6a5110 in demangle_type rust-demangle.c:1024
  #8 0x6a5110 in demangle_type rust-demangle.c:1024
  #9 0x6a5110 in demangle_type rust-demangle.c:1024
  #10 0x6a5110 in demangle_type rust-demangle.c:1024
  #11 0x6a5110 in demangle_type rust-demangle.c:1024
  #12 0x6a5110 in demangle_type rust-demangle.c:1024
  #13 0x6a5110 in demangle_type rust-demangle.c:1024
  #14 0x6a5110 in demangle_type rust-demangle.c:1024
  #15 0x6a5110 in demangle_type rust-demangle.c:1024
  #16 0x6a5110 in demangle_type rust-demangle.c:1024
  #17 0x6a5110 in demangle_type rust-demangle.c:1024
  #18 0x6a5110 in demangle_type rust-demangle.c:1024
  #19 0x6a5110 in demangle_type rust-demangle.c:1024
  #20 0x6a5110 in demangle_type rust-demangle.c:1024
  #21 0x6a5110 in demangle_type rust-demangle.c:1024
  #22 0x6a5110 in demangle_type rust-demangle.c:1024
  #23 0x6a5110 in demangle_type rust-demangle.c:1024
  #24 0x6a5110 in demangle_type rust-demangle.c:1024
  #25 0x6a5110 in demangle_type rust-demangle.c:1024
  #26 0x6a5110 in demangle_type rust-demangle.c:1024
  #27 0x6a5110 in demangle_type rust-demangle.c:1024
  #28 0x6a5110 in demangle_type rust-demangle.c:1024
  #29 0x6a5110 in demangle_type rust-demangle.c:1024
  #30 0x6a5110 in demangle_type rust-demangle.c:1024
  #31 0x6a5110 in demangle_type rust-demangle.c:1024
  #32 0x6a5110 in demangle_type rust-demangle.c:1024
  #33 0x6a5110 in demangle_type rust-demangle.c:1024
  #34 0x6a5110 in demangle_type rust-demangle.c:1024
  #35 0x6a5110 in demangle_type rust-demangle.c:1024
  #36 0x6a5110 in demangle_type rust-demangle.c:1024
  #37 0x6a5110 in demangle_type rust-demangle.c:1024
  #38 0x6a5110 in demangle_type rust-demangle.c:1024
  #39 0x6a5110 in demangle_type rust-demangle.c:1024
  #40 0x6a5110 in demangle_type rust-demangle.c:1024
  #41 0x6a5110 in demangle_type rust-demangle.c:1024
  #42 0x6a5110 in demangle_type rust-demangle.c:1024
  #43 0x6a5110 in demangle_type rust-demangle.c:1024
  #44 0x6a5110 in demangle_type rust-demangle.c:1024
  #45 0x6a5110 in demangle_type rust-demangle.c:1024
  #46 0x6a5110 in demangle_type rust-demangle.c:1024
  #47 0x6a5110 in demangle_type rust-demangle.c:1024
  #48 0x6a5110 in demangle_type rust-demangle.c:1024
  #49 0x6a5110 in demangle_type rust-demangle.c:1024
  #50 0x6a5110 in demangle_type rust-demangle.c:1024
  #51 0x6a5110 in demangle_type rust-demangle.c:1024
  #52 0x6a5110 in demangle_type rust-demangle.c:1024
  #53 0x6a5110 in demangle_type rust-demangle.c:1024
  #54 0x6a5110 in demangle_type rust-demangle.c:1024
  #55 0x6a5110 in demangle_type rust-demangle.c:1024
  #56 0x6a5110 in demangle_type rust-demangle.c:1024
  #57 0x6a5110 in demangle_type rust-demangle.c:1024
  #58 0x6a5110 in demangle_type rust-demangle.c:1024
  #59 0x6a5110 in demangle_type rust-demangle.c:1024
  #60 0x6a5110 in demangle_type rust-demangle.c:1024
  #61 0x6a5110 in demangle_type rust-demangle.c:1024
  #62 0x6a5110 in demangle_type rust-demangle.c:1024
  #63 0x6a5110 in demangle_type rust-demangle.c:1024
  #64 0x6a5110 in demangle_type rust-demangle.c:1024
  #65 0x6a5110 in demangle_type rust-demangle.c:1024
  #66 0x6a5110 in demangle_type rust-demangle.c:1024
  #67 0x6a5110 in demangle_type rust-demangle.c:1024
   

[Touch-packages] [Bug 1926934] Re: gdb batch calls time out on armhf

[Matthias Klose]

** Bug watch added: Sourceware.org Bugzilla #27810
   https://sourceware.org/bugzilla/show_bug.cgi?id=27810

** Also affects: gdb via
   https://sourceware.org/bugzilla/show_bug.cgi?id=27810
   Importance: Unknown
   Status: Unknown

-- 
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/1926934

Title:
  gdb batch calls time out on armhf

Status in gdb:
  Unknown
Status in gdb package in Ubuntu:
  New

Bug description:
  seen when trying to build the gcc-10, or gcc-snapshot packages.  A lot
  of tests in the guality test suite time out after 300 seconds (the
  default dejagnu timeout). These tests, like pr36728-1.c run ok on
  other architectures (and fail), but timeout on armhf.

  Seen in impish with gcc-10 and gcc-snapshot.

  Trying to run the gdb 10.2 tests on both hirsute and impish, I see a
  lot of timeouts as well.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gdb/+bug/1926934/+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 1926934] [NEW] gdb batch calls time out on armhf

[Matthias Klose]

Public bug reported:

seen when trying to build the gcc-10, or gcc-snapshot packages.  A lot
of tests in the guality test suite time out after 300 seconds (the
default dejagnu timeout). These tests, like pr36728-1.c run ok on other
architectures (and fail), but timeout on armhf.

Seen in impish with gcc-10 and gcc-snapshot.

Trying to run the gdb 10.2 tests on both hirsute and impish, I see a lot
of timeouts as well.

** 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/1926934

Title:
  gdb batch calls time out on armhf

Status in gdb package in Ubuntu:
  New

Bug description:
  seen when trying to build the gcc-10, or gcc-snapshot packages.  A lot
  of tests in the guality test suite time out after 300 seconds (the
  default dejagnu timeout). These tests, like pr36728-1.c run ok on
  other architectures (and fail), but timeout on armhf.

  Seen in impish with gcc-10 and gcc-snapshot.

  Trying to run the gdb 10.2 tests on both hirsute and impish, I see a
  lot of timeouts as well.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1926934/+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 1925401] Re: stack-overflow on binutils/__interceptor_strlen

[Matthias Klose]

*** This bug is a duplicate of bug 1925348 ***
https://bugs.launchpad.net/bugs/1925348

** This bug has been marked a duplicate of bug 1925348
   stack-overflow on GNU libiberty/rust-demangle.c:664 demangle_path

-- 
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/1925401

Title:
  stack-overflow on binutils/__interceptor_strlen

Status in binutils package in Ubuntu:
  New

Bug description:
  ==36966==ERROR: AddressSanitizer: stack-overflow on address 0x7ffc5b883fe8 
(pc 0x7f07be5f21a4 bp 0x7ffc5b884860 sp 0x7ffc5b883ff0 T0)
  #0 0x7f07be5f21a3 in __interceptor_strlen 
(/usr/lib/x86_64-linux-gnu/libasan.so.2+0x701a3)
  #1 0x6a3f4a in demangle_type rust-demangle.c:869
  #2 0x6a40d5 in demangle_type rust-demangle.c:903
  #3 0x6a44d7 in demangle_type rust-demangle.c:972
  #4 0x6a399d in demangle_path rust-demangle.c:747
  #5 0x6a4929 in demangle_type rust-demangle.c:1031
  #6 0x6a4897 in demangle_type rust-demangle.c:1024
  #7 0x6a44d7 in demangle_type rust-demangle.c:972
  #8 0x6a399d in demangle_path rust-demangle.c:747
  #9 0x6a4929 in demangle_type rust-demangle.c:1031
  #10 0x6a4897 in demangle_type rust-demangle.c:1024
  #11 0x6a44d7 in demangle_type rust-demangle.c:972
  #12 0x6a399d in demangle_path rust-demangle.c:747
  #13 0x6a4929 in demangle_type rust-demangle.c:1031
  #14 0x6a4897 in demangle_type rust-demangle.c:1024
  #15 0x6a44d7 in demangle_type rust-demangle.c:972
  #16 0x6a399d in demangle_path rust-demangle.c:747
  #17 0x6a4929 in demangle_type rust-demangle.c:1031
  #18 0x6a4897 in demangle_type rust-demangle.c:1024
  #19 0x6a44d7 in demangle_type rust-demangle.c:972
  #20 0x6a399d in demangle_path rust-demangle.c:747
  #21 0x6a4929 in demangle_type rust-demangle.c:1031
  #22 0x6a4897 in demangle_type rust-demangle.c:1024
  #23 0x6a44d7 in demangle_type rust-demangle.c:972
  #24 0x6a399d in demangle_path rust-demangle.c:747
  #25 0x6a4929 in demangle_type rust-demangle.c:1031
  #26 0x6a4897 in demangle_type rust-demangle.c:1024
  #27 0x6a44d7 in demangle_type rust-demangle.c:972
  #28 0x6a399d in demangle_path rust-demangle.c:747
  #29 0x6a4929 in demangle_type rust-demangle.c:1031
  #30 0x6a4897 in demangle_type rust-demangle.c:1024
  #31 0x6a44d7 in demangle_type rust-demangle.c:972
  #32 0x6a399d in demangle_path rust-demangle.c:747
  #33 0x6a4929 in demangle_type rust-demangle.c:1031
  #34 0x6a4897 in demangle_type rust-demangle.c:1024
  #35 0x6a44d7 in demangle_type rust-demangle.c:972
  #36 0x6a399d in demangle_path rust-demangle.c:747
  #37 0x6a4929 in demangle_type rust-demangle.c:1031
  #38 0x6a4897 in demangle_type rust-demangle.c:1024
  #39 0x6a44d7 in demangle_type rust-demangle.c:972
  #40 0x6a399d in demangle_path rust-demangle.c:747
  #41 0x6a4929 in demangle_type rust-demangle.c:1031
  #42 0x6a4897 in demangle_type rust-demangle.c:1024
  #43 0x6a44d7 in demangle_type rust-demangle.c:972
  #44 0x6a399d in demangle_path rust-demangle.c:747
  #45 0x6a4929 in demangle_type rust-demangle.c:1031
  #46 0x6a4897 in demangle_type rust-demangle.c:1024
  #47 0x6a44d7 in demangle_type rust-demangle.c:972
  #48 0x6a399d in demangle_path rust-demangle.c:747
  #49 0x6a4929 in demangle_type rust-demangle.c:1031
  #50 0x6a4897 in demangle_type rust-demangle.c:1024
  #51 0x6a44d7 in demangle_type rust-demangle.c:972
  #52 0x6a399d in demangle_path rust-demangle.c:747
  #53 0x6a4929 in demangle_type rust-demangle.c:1031
  #54 0x6a4897 in demangle_type rust-demangle.c:1024
  #55 0x6a44d7 in demangle_type rust-demangle.c:972
  #56 0x6a399d in demangle_path rust-demangle.c:747
  #57 0x6a4929 in demangle_type rust-demangle.c:1031
  #58 0x6a4897 in demangle_type rust-demangle.c:1024
  #59 0x6a44d7 in demangle_type rust-demangle.c:972
  #60 0x6a399d in demangle_path rust-demangle.c:747
  #61 0x6a4929 in demangle_type rust-demangle.c:1031
  #62 0x6a4897 in demangle_type rust-demangle.c:1024
  #63 0x6a44d7 in demangle_type rust-demangle.c:972
  #64 0x6a399d in demangle_path rust-demangle.c:747
  #65 0x6a4929 in demangle_type rust-demangle.c:1031
  #66 0x6a4897 in demangle_type rust-demangle.c:1024
  #67 0x6a44d7 in demangle_type rust-demangle.c:972
  #68 0x6a399d in demangle_path rust-demangle.c:747
  #69 0x6a4929 in demangle_type rust-demangle.c:1031
  #70 0x6a4897 in demangle_type rust-demangle.c:1024
  #71 0x6a44d7 in demangle_type rust-demangle.c:972
  #72 0x6a399d in demangle_path rust-demangle.c:747
  #73 0x6a4929 in demangle_type rust-demangle.c:1031
  #74 0x6a4897 in demangle_type rust-demangle.c:1024
  #75 0x6a44d7 in demangle_type rust-demangle.c:972
  #76 0x6a399d 

[Touch-packages] [Bug 1925400] Re: stack-overflow on binutils/in __asan_memcpy

[Matthias Klose]

*** This bug is a duplicate of bug 1925348 ***
https://bugs.launchpad.net/bugs/1925348

** This bug has been marked a duplicate of bug 1925348
   stack-overflow on GNU libiberty/rust-demangle.c:664 demangle_path

-- 
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/1925400

Title:
  stack-overflow on binutils/in __asan_memcpy

Status in binutils package in Ubuntu:
  New

Bug description:
  ==32900==ERROR: AddressSanitizer: stack-overflow on address 0x7ffe20ebff88 
(pc 0x7faa529f75cf bp 0x7ffe20ec0800 sp 0x7ffe20ebff90 T0)
  #0 0x7faa529f75ce in __asan_memcpy 
(/usr/lib/x86_64-linux-gnu/libasan.so.2+0x8c5ce)
  #1 0x6a660a in str_buf_append rust-demangle.c:1490
  #2 0x6a6651 in str_buf_demangle_callback rust-demangle.c:1497
  #3 0x6a131f in print_str rust-demangle.c:273
  #4 0x6a398e in demangle_path rust-demangle.c:746
  #5 0x6a4929 in demangle_type rust-demangle.c:1031
  #6 0x6a4897 in demangle_type rust-demangle.c:1024
  #7 0x6a399d in demangle_path rust-demangle.c:747
  #8 0x6a4929 in demangle_type rust-demangle.c:1031
  #9 0x6a4897 in demangle_type rust-demangle.c:1024
  #10 0x6a399d in demangle_path rust-demangle.c:747
  #11 0x6a4929 in demangle_type rust-demangle.c:1031
  #12 0x6a4897 in demangle_type rust-demangle.c:1024
  #13 0x6a399d in demangle_path rust-demangle.c:747
  #14 0x6a4929 in demangle_type rust-demangle.c:1031
  #15 0x6a4897 in demangle_type rust-demangle.c:1024
  #16 0x6a399d in demangle_path rust-demangle.c:747
  #17 0x6a4929 in demangle_type rust-demangle.c:1031
  #18 0x6a4897 in demangle_type rust-demangle.c:1024
  #19 0x6a399d in demangle_path rust-demangle.c:747
  #20 0x6a4929 in demangle_type rust-demangle.c:1031
  #21 0x6a4897 in demangle_type rust-demangle.c:1024
  #22 0x6a399d in demangle_path rust-demangle.c:747
  #23 0x6a4929 in demangle_type rust-demangle.c:1031
  #24 0x6a4897 in demangle_type rust-demangle.c:1024
  #25 0x6a399d in demangle_path rust-demangle.c:747
  #26 0x6a4929 in demangle_type rust-demangle.c:1031
  #27 0x6a4897 in demangle_type rust-demangle.c:1024
  #28 0x6a399d in demangle_path rust-demangle.c:747
  #29 0x6a4929 in demangle_type rust-demangle.c:1031
  #30 0x6a4897 in demangle_type rust-demangle.c:1024
  #31 0x6a399d in demangle_path rust-demangle.c:747
  #32 0x6a4929 in demangle_type rust-demangle.c:1031
  #33 0x6a4897 in demangle_type rust-demangle.c:1024
  #34 0x6a399d in demangle_path rust-demangle.c:747
  #35 0x6a4929 in demangle_type rust-demangle.c:1031
  #36 0x6a4897 in demangle_type rust-demangle.c:1024
  #37 0x6a399d in demangle_path rust-demangle.c:747
  #38 0x6a4929 in demangle_type rust-demangle.c:1031
  #39 0x6a4897 in demangle_type rust-demangle.c:1024
  #40 0x6a399d in demangle_path rust-demangle.c:747
  #41 0x6a4929 in demangle_type rust-demangle.c:1031
  #42 0x6a4897 in demangle_type rust-demangle.c:1024
  #43 0x6a399d in demangle_path rust-demangle.c:747
  #44 0x6a4929 in demangle_type rust-demangle.c:1031
  #45 0x6a4897 in demangle_type rust-demangle.c:1024
  #46 0x6a399d in demangle_path rust-demangle.c:747
  #47 0x6a4929 in demangle_type rust-demangle.c:1031
  #48 0x6a4897 in demangle_type rust-demangle.c:1024
  #49 0x6a399d in demangle_path rust-demangle.c:747
  #50 0x6a4929 in demangle_type rust-demangle.c:1031
  #51 0x6a4897 in demangle_type rust-demangle.c:1024
  #52 0x6a399d in demangle_path rust-demangle.c:747
  #53 0x6a4929 in demangle_type rust-demangle.c:1031
  #54 0x6a4897 in demangle_type rust-demangle.c:1024
  #55 0x6a399d in demangle_path rust-demangle.c:747
  #56 0x6a4929 in demangle_type rust-demangle.c:1031
  #57 0x6a4897 in demangle_type rust-demangle.c:1024
  #58 0x6a399d in demangle_path rust-demangle.c:747
  #59 0x6a4929 in demangle_type rust-demangle.c:1031
  #60 0x6a4897 in demangle_type rust-demangle.c:1024
  #61 0x6a399d in demangle_path rust-demangle.c:747
  #62 0x6a4929 in demangle_type rust-demangle.c:1031
  #63 0x6a4897 in demangle_type rust-demangle.c:1024
  #64 0x6a399d in demangle_path rust-demangle.c:747
  #65 0x6a4929 in demangle_type rust-demangle.c:1031
  #66 0x6a4897 in demangle_type rust-demangle.c:1024
  #67 0x6a399d in demangle_path rust-demangle.c:747
  #68 0x6a4929 in demangle_type rust-demangle.c:1031
  #69 0x6a4897 in demangle_type rust-demangle.c:1024
  #70 0x6a399d in demangle_path rust-demangle.c:747
  #71 0x6a4929 in demangle_type rust-demangle.c:1031
  #72 0x6a4897 in demangle_type rust-demangle.c:1024
  #73 0x6a399d in demangle_path rust-demangle.c:747
  #74 0x6a4929 in demangle_type rust-demangle.c:1031
  #75 0x6a4897 in demangle_type rust-demangle.c:1024
  

[Touch-packages] [Bug 1925348] Re: stack-overflow on GNU libiberty/rust-demangle.c:664 demangle_path

[Matthias Klose]

please don't submit issues like this without a reproducer.


** 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/1925348

Title:
  stack-overflow on GNU libiberty/rust-demangle.c:664 demangle_path

Status in binutils package in Ubuntu:
  Incomplete

Bug description:
  ==34504==ERROR: AddressSanitizer: stack-overflow on address 0x7ffee6038f48 
(pc 0x006a3331 bp 0x7ffee6039060 sp 0x7ffee6038f20 T0)
  #0 0x6a3330 in demangle_path rust-demangle.c:664
  #1 0x6a3bd1 in demangle_path rust-demangle.c:774
  #2 0x6a3bd1 in demangle_path rust-demangle.c:774
  #3 0x6a3bd1 in demangle_path rust-demangle.c:774
  #4 0x6a3bd1 in demangle_path rust-demangle.c:774
  #5 0x6a3bd1 in demangle_path rust-demangle.c:774
  #6 0x6a3bd1 in demangle_path rust-demangle.c:774
  #7 0x6a3bd1 in demangle_path rust-demangle.c:774
  #8 0x6a3bd1 in demangle_path rust-demangle.c:774
  #9 0x6a3bd1 in demangle_path rust-demangle.c:774
  #10 0x6a3bd1 in demangle_path rust-demangle.c:774
  #11 0x6a3bd1 in demangle_path rust-demangle.c:774
  #12 0x6a3bd1 in demangle_path rust-demangle.c:774
  #13 0x6a3bd1 in demangle_path rust-demangle.c:774
  #14 0x6a3bd1 in demangle_path rust-demangle.c:774
  #15 0x6a3bd1 in demangle_path rust-demangle.c:774
  #16 0x6a3bd1 in demangle_path rust-demangle.c:774
  #17 0x6a3bd1 in demangle_path rust-demangle.c:774
  #18 0x6a3bd1 in demangle_path rust-demangle.c:774
  #19 0x6a3bd1 in demangle_path rust-demangle.c:774
  #20 0x6a3bd1 in demangle_path rust-demangle.c:774
  #21 0x6a3bd1 in demangle_path rust-demangle.c:774
  #22 0x6a3bd1 in demangle_path rust-demangle.c:774
  #23 0x6a3bd1 in demangle_path rust-demangle.c:774
  #24 0x6a3bd1 in demangle_path rust-demangle.c:774
  #25 0x6a3bd1 in demangle_path rust-demangle.c:774
  #26 0x6a3bd1 in demangle_path rust-demangle.c:774
  #27 0x6a3bd1 in demangle_path rust-demangle.c:774
  #28 0x6a3bd1 in demangle_path rust-demangle.c:774
  #29 0x6a3bd1 in demangle_path rust-demangle.c:774
  #30 0x6a3bd1 in demangle_path rust-demangle.c:774
  #31 0x6a3bd1 in demangle_path rust-demangle.c:774
  #32 0x6a3bd1 in demangle_path rust-demangle.c:774
  #33 0x6a3bd1 in demangle_path rust-demangle.c:774
  #34 0x6a3bd1 in demangle_path rust-demangle.c:774
  #35 0x6a3bd1 in demangle_path rust-demangle.c:774
  #36 0x6a3bd1 in demangle_path rust-demangle.c:774
  #37 0x6a3bd1 in demangle_path rust-demangle.c:774
  #38 0x6a3bd1 in demangle_path rust-demangle.c:774
  #39 0x6a3bd1 in demangle_path rust-demangle.c:774
  #40 0x6a3bd1 in demangle_path rust-demangle.c:774
  #41 0x6a3bd1 in demangle_path rust-demangle.c:774
  #42 0x6a3bd1 in demangle_path rust-demangle.c:774
  #43 0x6a3bd1 in demangle_path rust-demangle.c:774
  #44 0x6a3bd1 in demangle_path rust-demangle.c:774
  #45 0x6a3bd1 in demangle_path rust-demangle.c:774
  #46 0x6a3bd1 in demangle_path rust-demangle.c:774
  #47 0x6a3bd1 in demangle_path rust-demangle.c:774
  #48 0x6a3bd1 in demangle_path rust-demangle.c:774
  #49 0x6a3bd1 in demangle_path rust-demangle.c:774
  #50 0x6a3bd1 in demangle_path rust-demangle.c:774
  #51 0x6a3bd1 in demangle_path rust-demangle.c:774
  #52 0x6a3bd1 in demangle_path rust-demangle.c:774
  #53 0x6a3bd1 in demangle_path rust-demangle.c:774
  #54 0x6a3bd1 in demangle_path rust-demangle.c:774
  #55 0x6a3bd1 in demangle_path rust-demangle.c:774
  #56 0x6a3bd1 in demangle_path rust-demangle.c:774
  #57 0x6a3bd1 in demangle_path rust-demangle.c:774
  #58 0x6a3bd1 in demangle_path rust-demangle.c:774
  #59 0x6a3bd1 in demangle_path rust-demangle.c:774
  #60 0x6a3bd1 in demangle_path rust-demangle.c:774
  #61 0x6a3bd1 in demangle_path rust-demangle.c:774
  #62 0x6a3bd1 in demangle_path rust-demangle.c:774
  #63 0x6a3bd1 in demangle_path rust-demangle.c:774
  #64 0x6a3bd1 in demangle_path rust-demangle.c:774
  #65 0x6a3bd1 in demangle_path rust-demangle.c:774
  #66 0x6a3bd1 in demangle_path rust-demangle.c:774
  #67 0x6a3bd1 in demangle_path rust-demangle.c:774
  #68 0x6a3bd1 in demangle_path rust-demangle.c:774
  #69 0x6a3bd1 in demangle_path rust-demangle.c:774
  #70 0x6a3bd1 in demangle_path rust-demangle.c:774
  #71 0x6a3bd1 in demangle_path rust-demangle.c:774
  #72 0x6a3bd1 in demangle_path rust-demangle.c:774
  #73 0x6a3bd1 in demangle_path rust-demangle.c:774
  #74 0x6a3bd1 in demangle_path rust-demangle.c:774
  #75 0x6a3bd1 in demangle_path rust-demangle.c:774
  #76 0x6a3bd1 in demangle_path rust-demangle.c:774
  #77 0x6a3bd1 in demangle_path rust-demangle.c:774
  #78 0x6a3bd1 in demangle_path 

[Touch-packages] [Bug 1864062] Re: autopkgtest regressions with gmp 6.2.0

[Matthias Klose]

** Changed in: gmp (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gmp in Ubuntu.
https://bugs.launchpad.net/bugs/1864062

Title:
  autopkgtest regressions with gmp 6.2.0

Status in gmp package in Ubuntu:
  Invalid
Status in libmath-gmp-perl package in Ubuntu:
  Fix Released
Status in libmath-prime-util-gmp-perl package in Ubuntu:
  Fix Released
Status in postgresql-pgmp package in Ubuntu:
  Fix Released
Status in gmp package in Debian:
  Fix Released

Bug description:
  Change in behaviour in GMP makes adjustments needed in reverse
  dependencies:

  postgresql-pgmp needs merging 1.0.4-1 from Debian unstable.
  Perl tests need to be fixed, see the linked Debian bug report.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gmp/+bug/1864062/+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 1318635] Re: qtbase failed to build on arm64 on utopic

[Matthias Klose]

utopic is EOL, closing the issue

** Changed in: gcc-defaults (Ubuntu)
   Status: Confirmed => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/1318635

Title:
  qtbase failed to build on arm64 on utopic

Status in gcc-defaults package in Ubuntu:
  Invalid
Status in qtbase-opensource-src package in Ubuntu:
  Fix Released

Bug description:
  The latest qtbase upload:
  
https://launchpad.net/ubuntu/utopic/+source/qtbase-opensource-src/5.2.1+dfsg-1ubuntu16

  failed to build on arm64:
  ---
  gcc -c -include .pch/Qt5Core -g -O2 -fstack-protector 
--param=ssp-buffer-size=4 -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 
-O2 -fvisibility=hidden -Wall -W -D_REENTRANT -fPIC -DQT_NO_MTDEV 
-DQT_NO_USING_NAMESPACE -DQT_BUILD_CORE_LIB -DQT_BUILDING_QT 
-DQT_NO_CAST_TO_ASCII -DQT_ASCII_CAST_WARNINGS -DQT_MOC_COMPAT 
-DQT_USE_QSTRINGBUILDER -DQT_DEPRECATED_WARNINGS 
-DQT_DISABLE_DEPRECATED_BEFORE=0x05 
-DELF_INTERPRETER=\"/lib/ld-linux-aarch64.so.1\" -DQT_USE_ICU 
-DPCRE_HAVE_CONFIG_H -DQT_CORE_LIB -D_LARGEFILE64_SOURCE -D_LARGEFILE_SOURCE 
-DQT_NO_DEBUG -I../../mkspecs/linux-g++ -I. -I../../include 
-I../../include/QtCore -I../../include/QtCore/5.2.1 
-I../../include/QtCore/5.2.1/QtCore -Iglobal -I../3rdparty/pcre 
-I../3rdparty/harfbuzz/src -I../3rdparty/md5 -I../3rdparty/md4 
-I../3rdparty/sha3 -I.moc -o .obj/pcre16_jit_compile.o 
../3rdparty/pcre/pcre16_jit_compile.c
  gcc: internal compiler error: Segmentation fault (program cc1)
  Please submit a full bug report,
  with preprocessed source if appropriate.
  See  for instructions.
  Makefile:19974: recipe for target '.obj/pcre16_fullinfo.o' failed
  ---

  The previous build on utopic was fine, and a trusty build with the
  same patch as ubuntu16 built ok.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gcc-defaults/+bug/1318635/+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 1403758] Re: Unity8 shows black screen with Qt 5.4.0

[Matthias Klose]

the binutils issues is fixed upstream. closing the binutils task.

** Changed in: binutils (Ubuntu)
   Status: Incomplete => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/1403758

Title:
  Unity8 shows black screen with Qt 5.4.0

Status in binutils:
  Unknown
Status in binutils package in Ubuntu:
  Fix Released
Status in gcc-defaults package in Ubuntu:
  Incomplete
Status in qtbase-opensource-src package in Ubuntu:
  Fix Released
Status in ubuntu-ui-toolkit package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  Fix Released

Bug description:
  With bug #1403511 taken care of in Qt, apps do not anymore crash with
  Qt 5.4 and device does not anymore go into reboot loop. However,
  nothing is visible on the screen.

  It seems unity8, unity8-dash etc are all running. unity8.log attached

  Relevant upstream links referring GCC5 as the reason to require -fPIC:
  
http://code.qt.io/cgit/qt/qtbase.git/commit/?id=36d6eb721e7d5997ade75e289d4088dc48678d0d
  
http://code.qt.io/cgit/qt/qtbase.git/commit/?id=3eca75de67b3fd2c890715b30c7899cebc096fe9

To manage notifications about this bug go to:
https://bugs.launchpad.net/binutils/+bug/1403758/+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 1899088] Re: Python.h library referencing problem

[Matthias Klose]

this is correct behavior. The headers are searched in
/usr/include/python3.8


** Package changed: gcc-defaults (Ubuntu) => python3-defaults (Ubuntu)

** 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/1899088

Title:
  Python.h library referencing problem

Status in python3-defaults package in Ubuntu:
  Invalid

Bug description:
  In the file /usrinclude/python3.8/cpython/pystate.h, on line 9, it is
  trying to reference the initconfig file but is using the path
  "cpython/initconfig" even though initconfig is in the same directory
  as pystate.h and gcc thinks that it means another directory called
  cpython inside the cpython directory. Please change pystate.h so that
  it references the correct path, modified it on my machine:

  previous: #include "cpython/initconfig.h"
  new: #include /*cpython/*/"initconfig.h"

  please change from previous to new

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gcc 4:7.4.0-1ubuntu2.3
  ProcVersionSignature: Ubuntu 5.4.0-48.52~18.04.1-generic 5.4.60
  Uname: Linux 5.4.0-48-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.17
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct  8 17:50:12 2020
  InstallationDate: Installed on 2020-03-31 (191 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  SourcePackage: gcc-defaults
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1899088/+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 1915250] Re: buildd file owner/group for shared libraries

[Matthias Klose]

** Changed in: debhelper (Ubuntu)
   Status: Confirmed => Fix Committed

** Changed in: fakeroot (Ubuntu)
   Status: Confirmed => Fix Committed

** Changed in: binutils (Ubuntu)
   Status: Confirmed => 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/1915250

Title:
  buildd file owner/group for shared libraries

Status in binutils package in Ubuntu:
  Invalid
Status in debhelper package in Ubuntu:
  Fix Committed
Status in fakeroot package in Ubuntu:
  Fix Committed
Status in glibc package in Ubuntu:
  Invalid
Status in debhelper package in Debian:
  Unknown

Bug description:
  fakeroot with glibc broke dpkg-deb for packages that do not use
  "Rules-Requires-Root: no" was broken.

  binutils stopped preserving permissions from objcopy & strip, leading
  to incorrect permissions of files after stripping.

  fakeroot is now patched with better glibc 2.33 support. TODO upstream
  changes.

  binutils is not fixed, as upstream changes are still being discussed.
  Instead we have worked around objcopy/strip in debhelper to call those
  tools from dh_strip in a safe manner.

  We also rebuilt binutils against glibc 2.32, to avoid this new
  behaviour. However, we need to resolve bintuils in a better way, one
  way or another.

  
  --

  the current state of -proposed creates deb packages with buildd file
  owner/group for shared libraries.

  reported at least for kwayland-integration.

  $ dpkg -c kwayland-integration_5.20.90-0ubuntu1_amd64.deb|grep \.so
  -rw-r--r-- doko/doko 18984 2021-01-21 23:44 
./usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kguiaddons/kmodifierkey/kmodifierkey_wayland.so
  -rw-r--r-- doko/doko 85392 2021-01-21 23:44 
./usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kwindowsystem/KF5WindowSystemKWaylandPlugin.so
  -rw-r--r-- doko/doko 35536 2021-01-21 23:44 
./usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/org.kde.kidletime.platforms/KF5IdleTimeKWaylandPlugin.so

   - in a release pocket, rebuild binutils from proposed. correctly
     restores the file ownership

   - in a release pocket, update glibc from proposed. then rebuild
     binutils from proposed. shows the wrong ownership

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1915250/+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 1915250] Re: buildd file owner/group for shared libraries

[Matthias Klose]

that's the proposed patch to dh_strip to keep permissions and owners
independent of strip/objcopy keeping these.

** Patch added: "dh_strip.diff"
   
https://bugs.launchpad.net/ubuntu/+source/fakeroot/+bug/1915250/+attachment/5464124/+files/dh_strip.diff

-- 
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/1915250

Title:
  buildd file owner/group for shared libraries

Status in binutils package in Ubuntu:
  Confirmed
Status in debhelper package in Ubuntu:
  Confirmed
Status in fakeroot package in Ubuntu:
  Confirmed
Status in glibc package in Ubuntu:
  Confirmed
Status in debhelper package in Debian:
  Unknown

Bug description:
  the current state of -proposed creates deb packages with buildd file
  owner/group for shared libraries.

  reported at least for kwayland-integration.

  $ dpkg -c kwayland-integration_5.20.90-0ubuntu1_amd64.deb|grep \.so
  -rw-r--r-- doko/doko 18984 2021-01-21 23:44 
./usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kguiaddons/kmodifierkey/kmodifierkey_wayland.so
  -rw-r--r-- doko/doko 85392 2021-01-21 23:44 
./usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kwindowsystem/KF5WindowSystemKWaylandPlugin.so
  -rw-r--r-- doko/doko 35536 2021-01-21 23:44 
./usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/org.kde.kidletime.platforms/KF5IdleTimeKWaylandPlugin.so

   - in a release pocket, rebuild binutils from proposed. correctly
 restores the file ownership

   - in a release pocket, update glibc from proposed. then rebuild
 binutils from proposed. shows the wrong ownership

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1915250/+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 1915250] Re: buildd file owner/group for shared libraries

[Matthias Klose]

** Changed in: binutils (Ubuntu)
   Importance: Undecided => High

** Bug watch added: Debian Bug tracker #982457
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982457

** Also affects: debhelper (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982457
   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/1915250

Title:
  buildd file owner/group for shared libraries

Status in binutils package in Ubuntu:
  Confirmed
Status in debhelper package in Ubuntu:
  Confirmed
Status in fakeroot package in Ubuntu:
  Confirmed
Status in glibc package in Ubuntu:
  Confirmed
Status in debhelper package in Debian:
  Unknown

Bug description:
  the current state of -proposed creates deb packages with buildd file
  owner/group for shared libraries.

  reported at least for kwayland-integration.

  $ dpkg -c kwayland-integration_5.20.90-0ubuntu1_amd64.deb|grep \.so
  -rw-r--r-- doko/doko 18984 2021-01-21 23:44 
./usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kguiaddons/kmodifierkey/kmodifierkey_wayland.so
  -rw-r--r-- doko/doko 85392 2021-01-21 23:44 
./usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kwindowsystem/KF5WindowSystemKWaylandPlugin.so
  -rw-r--r-- doko/doko 35536 2021-01-21 23:44 
./usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/org.kde.kidletime.platforms/KF5IdleTimeKWaylandPlugin.so

   - in a release pocket, rebuild binutils from proposed. correctly
 restores the file ownership

   - in a release pocket, update glibc from proposed. then rebuild
 binutils from proposed. shows the wrong ownership

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1915250/+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 1915250] Re: buildd file owner/group for shared libraries

[Matthias Klose]

currently building binutils against the release pocket to mitigate the
immediate issue

-- 
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/1915250

Title:
  buildd file owner/group for shared libraries

Status in binutils package in Ubuntu:
  New
Status in debhelper package in Ubuntu:
  New
Status in fakeroot package in Ubuntu:
  Confirmed
Status in glibc package in Ubuntu:
  New

Bug description:
  the current state of -proposed creates deb packages with buildd file
  owner/group for shared libraries.

  reported at least for kwayland-integration.

  $ dpkg -c kwayland-integration_5.20.90-0ubuntu1_amd64.deb|grep \.so
  -rw-r--r-- doko/doko 18984 2021-01-21 23:44 
./usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kguiaddons/kmodifierkey/kmodifierkey_wayland.so
  -rw-r--r-- doko/doko 85392 2021-01-21 23:44 
./usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kwindowsystem/KF5WindowSystemKWaylandPlugin.so
  -rw-r--r-- doko/doko 35536 2021-01-21 23:44 
./usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/org.kde.kidletime.platforms/KF5IdleTimeKWaylandPlugin.so

   - in a release pocket, rebuild binutils from proposed. correctly
 restores the file ownership

   - in a release pocket, update glibc from proposed. then rebuild
 binutils from proposed. shows the wrong ownership

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1915250/+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 1915250] Re: buildd file owner/group for shared libraries

[Matthias Klose]

also why is the dh sequencer calling dh_fixperms before doing
modifications on files (e.g. dh_strip)?

-- 
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/1915250

Title:
  buildd file owner/group for shared libraries

Status in binutils package in Ubuntu:
  New
Status in debhelper package in Ubuntu:
  New
Status in fakeroot package in Ubuntu:
  Confirmed
Status in glibc package in Ubuntu:
  New

Bug description:
  the current state of -proposed creates deb packages with buildd file
  owner/group for shared libraries.

  reported at least for kwayland-integration.

  $ dpkg -c kwayland-integration_5.20.90-0ubuntu1_amd64.deb|grep \.so
  -rw-r--r-- doko/doko 18984 2021-01-21 23:44 
./usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kguiaddons/kmodifierkey/kmodifierkey_wayland.so
  -rw-r--r-- doko/doko 85392 2021-01-21 23:44 
./usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kwindowsystem/KF5WindowSystemKWaylandPlugin.so
  -rw-r--r-- doko/doko 35536 2021-01-21 23:44 
./usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/org.kde.kidletime.platforms/KF5IdleTimeKWaylandPlugin.so

   - in a release pocket, rebuild binutils from proposed. correctly
 restores the file ownership

   - in a release pocket, update glibc from proposed. then rebuild
 binutils from proposed. shows the wrong ownership

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1915250/+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 1915250] Re: buildd file owner/group for shared libraries

[Matthias Klose]

fakeroot needs an update for glibc-2.33, see
https://bugzilla.redhat.com/show_bug.cgi?id=1889862

not just the build fix from
https://lists.fedoraproject.org/archives/list/de...@lists.fedoraproject.org/message/SMQ3RYXEYTVZH6PLQMKNB3NM4XLPMNZO/

discussions of tools not preserving file ownership/permissions:
https://groups.google.com/g/linux.gentoo.dev/c/WG-OLQe3yng/m/ZlqM-QC6BQAJ

binutils discussion:
https://sourceware.org/pipermail/binutils/2021-February/115241.html

make the packaging helper more robust:
https://git.archlinux.org/pacman.git/commit/?id=88d054093c1c99a697d95b26bd9aad5bc4d8e170


** Bug watch added: Red Hat Bugzilla #1889862
   https://bugzilla.redhat.com/show_bug.cgi?id=1889862

-- 
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/1915250

Title:
  buildd file owner/group for shared libraries

Status in binutils package in Ubuntu:
  New
Status in debhelper package in Ubuntu:
  New
Status in fakeroot package in Ubuntu:
  Confirmed
Status in glibc package in Ubuntu:
  New

Bug description:
  the current state of -proposed creates deb packages with buildd file
  owner/group for shared libraries.

  reported at least for kwayland-integration.

  $ dpkg -c kwayland-integration_5.20.90-0ubuntu1_amd64.deb|grep \.so
  -rw-r--r-- doko/doko 18984 2021-01-21 23:44 
./usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kguiaddons/kmodifierkey/kmodifierkey_wayland.so
  -rw-r--r-- doko/doko 85392 2021-01-21 23:44 
./usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kwindowsystem/KF5WindowSystemKWaylandPlugin.so
  -rw-r--r-- doko/doko 35536 2021-01-21 23:44 
./usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/org.kde.kidletime.platforms/KF5IdleTimeKWaylandPlugin.so

   - in a release pocket, rebuild binutils from proposed. correctly
 restores the file ownership

   - in a release pocket, update glibc from proposed. then rebuild
 binutils from proposed. shows the wrong ownership

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1915250/+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 1915250] Re: buildd file owner/group for shared libraries

[Matthias Klose]

** Package changed: glibc (Ubuntu) => fakeroot (Ubuntu)

** Also affects: glibc (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: binutils (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: debhelper (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/1915250

Title:
  buildd file owner/group for shared libraries

Status in binutils package in Ubuntu:
  New
Status in debhelper package in Ubuntu:
  New
Status in fakeroot package in Ubuntu:
  Confirmed
Status in glibc package in Ubuntu:
  New

Bug description:
  the current state of -proposed creates deb packages with buildd file
  owner/group for shared libraries.

  reported at least for kwayland-integration.

  $ dpkg -c kwayland-integration_5.20.90-0ubuntu1_amd64.deb|grep \.so
  -rw-r--r-- doko/doko 18984 2021-01-21 23:44 
./usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kguiaddons/kmodifierkey/kmodifierkey_wayland.so
  -rw-r--r-- doko/doko 85392 2021-01-21 23:44 
./usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kwindowsystem/KF5WindowSystemKWaylandPlugin.so
  -rw-r--r-- doko/doko 35536 2021-01-21 23:44 
./usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/org.kde.kidletime.platforms/KF5IdleTimeKWaylandPlugin.so

   - in a release pocket, rebuild binutils from proposed. correctly
 restores the file ownership

   - in a release pocket, update glibc from proposed. then rebuild
 binutils from proposed. shows the wrong ownership

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1915250/+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 1915009] [NEW] [MIR] libmd (dependency of libbsd)

[Matthias Klose]

Public bug reported:

[MIR] libmd (dependency of libbsd)

** Affects: libbsd (Ubuntu)
 Importance: High
 Status: New

** Affects: libmd (Ubuntu)
 Importance: High
 Status: Incomplete


** Tags: hirsute rls-hh-incoming

** Changed in: libmd (Ubuntu)
   Importance: Undecided => High

** Also affects: libbsd (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: libbsd (Ubuntu)
   Importance: Undecided => High

** Tags added: rls-hh-incoming

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libbsd in Ubuntu.
https://bugs.launchpad.net/bugs/1915009

Title:
  [MIR] libmd (dependency of libbsd)

Status in libbsd package in Ubuntu:
  New
Status in libmd package in Ubuntu:
  Incomplete

Bug description:
  [MIR] libmd (dependency of libbsd)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libbsd/+bug/1915009/+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 1907472] Re: glibc x32 autopkgtest fails in hirsute with binutils and audit in -proposed

[Matthias Klose]

removed the update-excuse tag. that's unrelated to the current 2.33
migration.

** Tags removed: update-excuse

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to audit in Ubuntu.
https://bugs.launchpad.net/bugs/1907472

Title:
  glibc x32 autopkgtest fails in hirsute with binutils and audit in
  -proposed

Status in audit package in Ubuntu:
  New
Status in binutils package in Ubuntu:
  New
Status in glibc package in Ubuntu:
  New

Bug description:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-
  hirsute/hirsute/amd64/g/glibc/20201208_160143_17354@/log.gz

  --
  FAIL: math/test-double-libmvec-sincos
  original exit status 1
  Didn't expect signal from child: got `Illegal instruction'
  --
  --
  FAIL: math/test-double-vlen2-sincos
  original exit status 132
  --
  --
  FAIL: math/test-float-libmvec-sincosf
  original exit status 1
  Didn't expect signal from child: got `Illegal instruction'
  --
  --
  FAIL: math/test-float-vlen4-sincos
  original exit status 132
  --

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/audit/+bug/1907472/+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 1910576] [NEW] [MIR] libbpf (dependency of iproute2)

[Matthias Klose]

Public bug reported:

[MIR] libbpf (dependency of iproute2)

** Affects: iproute2 (Ubuntu)
 Importance: High
 Assignee: Kernel Packages (kernel-packages)
 Status: New

** Affects: libbpf (Ubuntu)
 Importance: High
 Assignee: Kernel Packages (kernel-packages)
 Status: Incomplete


** Tags: hirsute rls-hh-incoming

** Also affects: iproute2 (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: iproute2 (Ubuntu)
   Importance: Undecided => High

** Changed in: libbpf (Ubuntu)
   Importance: Undecided => High

** Tags added: rls-hh-incoming

** Changed in: iproute2 (Ubuntu)
 Assignee: (unassigned) => Kernel Packages (kernel-packages)

** Changed in: libbpf (Ubuntu)
 Assignee: (unassigned) => Kernel Packages (kernel-packages)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iproute2 in Ubuntu.
https://bugs.launchpad.net/bugs/1910576

Title:
  [MIR] libbpf (dependency of iproute2)

Status in iproute2 package in Ubuntu:
  New
Status in libbpf package in Ubuntu:
  Incomplete

Bug description:
  [MIR] libbpf (dependency of iproute2)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1910576/+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 1908502] [NEW] [MIR] libtiff5 dependency on libdeflate0

[Matthias Klose]

Public bug reported:

tiff 4.1.0+git201212-1 enabled deflate support, adding libdeflate0 as a
dependency to libtiff5, making the package uninstallable.

Therefor I uploaded 4.1.0+git201212-1ubuntu1 disabling the deflate
support to make libtiff5 installable again.

Either this package stays this way, or it needs a MIR for libdeflate.

** Affects: libdeflate (Ubuntu)
 Importance: Undecided
 Status: Incomplete

** Affects: tiff (Ubuntu)
 Importance: Undecided
 Status: Confirmed


** Tags: rls-hh-incoming

** Also affects: libdeflate (Ubuntu)
   Importance: Undecided
   Status: New

** Tags added: rls-hh-incoming

** Changed in: libdeflate (Ubuntu)
   Status: New => Incomplete

** Changed in: tiff (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tiff in Ubuntu.
https://bugs.launchpad.net/bugs/1908502

Title:
  [MIR] libtiff5 dependency on libdeflate0

Status in libdeflate package in Ubuntu:
  Incomplete
Status in tiff package in Ubuntu:
  Confirmed

Bug description:
  tiff 4.1.0+git201212-1 enabled deflate support, adding libdeflate0 as
  a dependency to libtiff5, making the package uninstallable.

  Therefor I uploaded 4.1.0+git201212-1ubuntu1 disabling the deflate
  support to make libtiff5 installable again.

  Either this package stays this way, or it needs a MIR for libdeflate.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libdeflate/+bug/1908502/+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 1907789] Re: 2.35.50 breaks ld -no-pie

[Matthias Klose]

** Bug watch added: Sourceware.org Bugzilla #27050
   https://sourceware.org/bugzilla/show_bug.cgi?id=27050

** Also affects: binutils via
   https://sourceware.org/bugzilla/show_bug.cgi?id=27050
   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/1907789

Title:
  2.35.50 breaks ld -no-pie

Status in binutils:
  Unknown
Status in binutils package in Ubuntu:
  Fix Committed

Bug description:
  The qemu build reaches (and always did) a step where it tries to link some
  img files. That is done via the command:
$ ld -m elf_i386 -T /<>/pc-bios/optionrom//flat.lds -no-pie -s 
-o multiboot.img multiboot.o

  Recently that still works in Debian [1] but no more in Ubuntu [2].

  I think that the new binutils broke me.
  In hirsute proposed those are at 2.35.50.20201210-0ubuntu1

  The issue is easily isolated, and by copying the two files around I
  found the following:

  Hirsute: 2.35.50.20201210-0ubuntu1 - bad
  Hirsute: 2.35.50.20201207-0ubuntu1 - bad
  Sid: 2.35.1-4  - good
  Groovy:  2.35.1-1ubuntu1   - good
  Focal:   2.34-6ubuntu1 - good

  I'll attach these two files to the bug, just thro them into a directory and
  run the command:
   $ ld -m elf_i386 -T ./flat.lds -no-pie -s -o linuxboot.img linuxboot.o

  If that is an intentional change please guide how this is now supposed
  to work.

  [1]: 
https://buildd.debian.org/status/fetch.php?pkg=qemu=amd64=1%3A5.2%2Bdfsg-2=1607598738=1
  [2]: 
https://launchpadlibrarian.net/510801929/buildlog_ubuntu-hirsute-amd64.qemu_1%3A5.2+dfsg-2ubuntu1~ppa2_BUILD

To manage notifications about this bug go to:
https://bugs.launchpad.net/binutils/+bug/1907789/+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 1908063] Re: gdb-multiarch 8.1.1-0ubuntu1 regression: assertion failure or internal error when connecting to QEMU aarch64 gdbstub

[Matthias Klose]

** Also affects: gdb (Ubuntu Bionic)
   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/1908063

Title:
  gdb-multiarch 8.1.1-0ubuntu1 regression: assertion failure or internal
  error when connecting to QEMU aarch64 gdbstub

Status in gdb package in Ubuntu:
  New
Status in gdb source package in Bionic:
  New

Bug description:
  This bug is a regression introduced in 8.1.1-0ubuntu1 for Bionic --
  the previous 8.1-0ubuntu3.2 gdb works fine with QEMU's gdbstub.

  Reproduce:
  Get the sources for QEMU 5.2.0, and build the aarch64-linux-user target. (It 
looks like Bionic's QEMU is old enough that it doesn't provoke this gdb error.)

  Run
   qemu-aarch64 -g 1234 path/to/some/aarch64/binary

  In another terminal, start gdb-multiarch. At the (gdb) prompt, type
  "target remote :1234". GDB will dump core:

  (gdb) target remote :1234
  Remote debugging using :1234
  Recursive internal problem.
  Aborted (core dumped)

  You can see a variant of this also in the QEMU test suite with "make
  -C your-qemu-build-dir check-tcg", where the error message includes an
  assertion failure:

  [...]

  timeout 60  
/home/petmay01/linaro/qemu-from-laptop/qemu/tests/guest-debug/run-test.py --gdb 
/usr/bin/gdb-multiarch --qemu 
/home/petmay01/linaro/qemu-from-laptop/qemu/build/aarch64-linux/qemu-aarch64 
--qargs "" --bin sha1 --test 
/home/petmay01/linaro/qemu-from-laptop/qemu/tests/tcg/multiarch/gdbstub/sha1.py 
>  run-gdbstub-sha1.out
  /build/gdb-veKdC1/gdb-8.1.1/gdb/regcache.c:122: internal-error: void* 
init_regcache_descr(gdbarch*): Assertion `MAX_REGISTER_SIZE >= 
descr->sizeof_register[i]' failed.
  A problem internal to GDB has been detected,
  further debugging may prove unreliable.

  This is a bug, please report it.  For instructions, see:
  .

  Aborted (core dumped)
  
/home/petmay01/linaro/qemu-from-laptop/qemu/tests/tcg/multiarch/Makefile.target:51:
 recipe for target 'run-gdbstub-sha1' failed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1908063/+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 1907789] Re: 2.35.50 breaks ld -no-pie

[Matthias Klose]

** Changed in: binutils (Ubuntu)
   Status: New => Fix Committed

-- 
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/1907789

Title:
  2.35.50 breaks ld -no-pie

Status in binutils package in Ubuntu:
  Fix Committed

Bug description:
  The qemu build reaches (and always did) a step where it tries to link some
  img files. That is done via the command:
$ ld -m elf_i386 -T /<>/pc-bios/optionrom//flat.lds -no-pie -s 
-o multiboot.img multiboot.o

  Recently that still works in Debian [1] but no more in Ubuntu [2].

  I think that the new binutils broke me.
  In hirsute proposed those are at 2.35.50.20201210-0ubuntu1

  The issue is easily isolated, and by copying the two files around I
  found the following:

  Hirsute: 2.35.50.20201210-0ubuntu1 - bad
  Hirsute: 2.35.50.20201207-0ubuntu1 - bad
  Sid: 2.35.1-4  - good
  Groovy:  2.35.1-1ubuntu1   - good
  Focal:   2.34-6ubuntu1 - good

  I'll attach these two files to the bug, just thro them into a directory and
  run the command:
   $ ld -m elf_i386 -T ./flat.lds -no-pie -s -o linuxboot.img linuxboot.o

  If that is an intentional change please guide how this is now supposed
  to work.

  [1]: 
https://buildd.debian.org/status/fetch.php?pkg=qemu=amd64=1%3A5.2%2Bdfsg-2=1607598738=1
  [2]: 
https://launchpadlibrarian.net/510801929/buildlog_ubuntu-hirsute-amd64.qemu_1%3A5.2+dfsg-2ubuntu1~ppa2_BUILD

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1907789/+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 1905768] Re: ld: DWARF error: could not find variable specification at offset

[Matthias Klose]

fixed in hirsute

** Changed in: binutils (Ubuntu)
   Status: New => Fix Released

-- 
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/1905768

Title:
  ld: DWARF error: could not find variable specification at offset

Status in binutils package in Ubuntu:
  Fix Released
Status in binutils package in Debian:
  Unknown

Bug description:
  Fixed upstream. Please update (I still get the error in
  2.35.1-1ubuntu1 on groovy).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1905768/+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 1903849] [NEW] vim ftbfs

[Matthias Klose]

Public bug reported:

see
https://launchpad.net/ubuntu/+source/vim/2:8.2.1913-1ubuntu1

blocking the perl transition

** Affects: vim (Ubuntu)
 Importance: High
 Status: Confirmed


** Tags: ftbfs rls-hh-incoming

** Changed in: vim (Ubuntu)
   Status: New => Confirmed

** Changed in: vim (Ubuntu)
   Importance: Undecided => High

** Tags added: ftbfs rls-hh-incoming

** Description changed:

  see
  https://launchpad.net/ubuntu/+source/vim/2:8.2.1913-1ubuntu1
+ 
+ blocking the perl transition

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to vim in Ubuntu.
https://bugs.launchpad.net/bugs/1903849

Title:
  vim ftbfs

Status in vim package in Ubuntu:
  Confirmed

Bug description:
  see
  https://launchpad.net/ubuntu/+source/vim/2:8.2.1913-1ubuntu1

  blocking the perl transition

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1903849/+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 1902225] Re: SRU: update gdb 8.1.1 for 18.04 LTS

[Matthias Klose]

all packages built, gdb test suite looks ok.
LP: #1901026 was tested separately.

The BOT only reports bogus, so ignore it.



** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done verification-done-bionic

-- 
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/1902225

Title:
  SRU: update gdb 8.1.1 for 18.04 LTS

Status in gdb package in Ubuntu:
  New
Status in gdb source package in Bionic:
  Fix Committed

Bug description:
  gdb 8.1.1 is a minor bug fix release for 8.1. Some of the issues fixed
  in 8.1.1 are already fixed in the branch update in 8.1-0ubuntu3:

   * gdb 8.1.1 release.
  This is a minor corrective release over GDB 8.1, fixing following issues:
  - PR gdb/23028 (inconsistent disassemble of vcvtpd2dq)
  - PR gdb/23053 (Fix -D_GLIBCXX_DEBUG gdb-add-index regression)
  - PR gdb/23127 ([AArch64] GDB cannot be used for debugging software that
uses high Virtual Addresses)
  - PR server/23158 (gdbserver no longer functional on Windows)
  - PR breakpoints/23210 ([8.1/8.2 Regression] Bogus Breakpoint address
adjusted from 0xf7fe7dd3 to 0xf7fe7dd3)
  Already fixed in 8.1-0ubuntu3:
  - PR gdb/22824 (misleading description of new rbreak Python function in
GDB 8.1 NEWS file)
  - PR gdb/22849 (ctrl-c doesn't work in extended-remote)
  - PR gdb/22907 ([Regression] gdbserver doesn't work with filename-only
binaries).
* Allow remote debugging over a Unix local domain socket. LP: #1901026.

  This minor version update fixes four upstream issues (not counting the
  Windows specific issue), plus allows remote debugging over a Unix
  local domain socket., a patch taken from the 8.2 development.

  Validation: The tests run during build time are passing, and the
  remote debugging is checked to be working (no automated test case).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1902225/+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 1901026] Re: [GDB] No socket file connection support

[Matthias Klose]

from what I see, all these are unrelated to the bug fix, but problems
with the test infrastructure.

** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done verification-done-bionic

-- 
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/1901026

Title:
  [GDB] No socket file connection support

Status in gdb package in Ubuntu:
  New
Status in gdb source package in Bionic:
  Fix Committed

Bug description:
  GDB on Ubuntu 18.04 (GNU gdb (Ubuntu 8.1-0ubuntu3.2)
  8.1.0.20180409-git) does not support connecting to a remote target via
  a socket file.

  This is the error we get:

  (gdb) target remote /run/user/1000/at-spi2-QTZBS0/socket
  /run/user/1000/at-spi2-QTZBS0/socket: No such device or address.

  Commit c1168a2f66553cd4730931cf59e3be8378a1a03f enables this in GDB.
  It would be nice to have it backported.

  Here's the commit link: https://sourceware.org/git/?p=binutils-
  gdb.git;a=commit;h=c1168a2f66553cd4730931cf59e3be8378a1a03f

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1901026/+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 1901026] Re: [GDB] No socket file connection support

[Matthias Klose]

** Also affects: gdb (Ubuntu Bionic)
   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/1901026

Title:
  [GDB] No socket file connection support

Status in gdb package in Ubuntu:
  New
Status in gdb source package in Bionic:
  New

Bug description:
  GDB on Ubuntu 18.04 (GNU gdb (Ubuntu 8.1-0ubuntu3.2)
  8.1.0.20180409-git) does not support connecting to a remote target via
  a socket file.

  This is the error we get:

  (gdb) target remote /run/user/1000/at-spi2-QTZBS0/socket
  /run/user/1000/at-spi2-QTZBS0/socket: No such device or address.

  Commit c1168a2f66553cd4730931cf59e3be8378a1a03f enables this in GDB.
  It would be nice to have it backported.

  Here's the commit link: https://sourceware.org/git/?p=binutils-
  gdb.git;a=commit;h=c1168a2f66553cd4730931cf59e3be8378a1a03f

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1901026/+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 1902225] [NEW] SRU: update gdb 8.1.1 for 18.04 LTS

[Matthias Klose]

Public bug reported:

gdb 8.1.1 is a minor bug fix release for 8.1. Some of the issues fixed
in 8.1.1 are already fixed in the branch update in 8.1-0ubuntu3:

 * gdb 8.1.1 release.
This is a minor corrective release over GDB 8.1, fixing following issues:
- PR gdb/23028 (inconsistent disassemble of vcvtpd2dq)
- PR gdb/23053 (Fix -D_GLIBCXX_DEBUG gdb-add-index regression)
- PR gdb/23127 ([AArch64] GDB cannot be used for debugging software that
  uses high Virtual Addresses)
- PR server/23158 (gdbserver no longer functional on Windows)
- PR breakpoints/23210 ([8.1/8.2 Regression] Bogus Breakpoint address
  adjusted from 0xf7fe7dd3 to 0xf7fe7dd3)
Already fixed in 8.1-0ubuntu3:
- PR gdb/22824 (misleading description of new rbreak Python function in
  GDB 8.1 NEWS file)
- PR gdb/22849 (ctrl-c doesn't work in extended-remote)
- PR gdb/22907 ([Regression] gdbserver doesn't work with filename-only
  binaries).
  * Allow remote debugging over a Unix local domain socket. LP: #1901026.

This minor version update fixes four upstream issues (not counting the
Windows specific issue), plus allows remote debugging over a Unix local
domain socket., a patch taken from the 8.2 development.

Validation: The tests run during build time are passing, and the remote
debugging is checked to be working (no automated test case).

** 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/1902225

Title:
  SRU: update gdb 8.1.1 for 18.04 LTS

Status in gdb package in Ubuntu:
  New

Bug description:
  gdb 8.1.1 is a minor bug fix release for 8.1. Some of the issues fixed
  in 8.1.1 are already fixed in the branch update in 8.1-0ubuntu3:

   * gdb 8.1.1 release.
  This is a minor corrective release over GDB 8.1, fixing following issues:
  - PR gdb/23028 (inconsistent disassemble of vcvtpd2dq)
  - PR gdb/23053 (Fix -D_GLIBCXX_DEBUG gdb-add-index regression)
  - PR gdb/23127 ([AArch64] GDB cannot be used for debugging software that
uses high Virtual Addresses)
  - PR server/23158 (gdbserver no longer functional on Windows)
  - PR breakpoints/23210 ([8.1/8.2 Regression] Bogus Breakpoint address
adjusted from 0xf7fe7dd3 to 0xf7fe7dd3)
  Already fixed in 8.1-0ubuntu3:
  - PR gdb/22824 (misleading description of new rbreak Python function in
GDB 8.1 NEWS file)
  - PR gdb/22849 (ctrl-c doesn't work in extended-remote)
  - PR gdb/22907 ([Regression] gdbserver doesn't work with filename-only
binaries).
* Allow remote debugging over a Unix local domain socket. LP: #1901026.

  This minor version update fixes four upstream issues (not counting the
  Windows specific issue), plus allows remote debugging over a Unix
  local domain socket., a patch taken from the 8.2 development.

  Validation: The tests run during build time are passing, and the
  remote debugging is checked to be working (no automated test case).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1902225/+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 1890270] Re: SRU: update gdb 9.2 for 20.04 LTS

[Matthias Klose]

** Changed in: gdb (Ubuntu)
   Status: New => Fix Released

-- 
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/1890270

Title:
  SRU: update gdb 9.2 for 20.04 LTS

Status in gdb package in Ubuntu:
  Fix Released
Status in gdb source package in Focal:
  Fix Released

Bug description:
  SRU: update gdb 9.2 for 20.04 LTS

  according to https://sourceware.org/gdb/ this is a bug fix release:

  """
  This is a minor corrective release over GDB 9.1, fixing the following issues:

  PR tui/25586 (Resizing the source/disassembly or command window produces 
corrupted display)
  PR gdb/25650 (GDB can't 'printf' a convenience variable holding an inferior 
address)
  PR build/25981 (Use of short i386 register names breaks compilation on recent 
Solaris 11.4)
  PR symtab/26003 (infinite loop loading symbols from separate debug objfile)
  PR build/26029 (GDB build failure on SPARC)
  """

  Regression potential: minimal, package also not used by normal users,
  but for development.

  Acceptence criteria:  Package builds, no regressions in the testsuite.

  The package also was part of a focal test rebuild, see LP: #1879481.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1890270/+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 1899168] [NEW] SRU: update python2.7 to the 2.7.18 release

[Matthias Klose]

Public bug reported:

This is a proposal to backport the Python 2.7.18 release to bionic, like
it was done for 2.7.17 in LP: #1855133.

** Affects: python-stdlib-extensions (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: python2.7 (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: python-stdlib-extensions (Ubuntu Bionic)
 Importance: Undecided
 Status: New

** Affects: python2.7 (Ubuntu Bionic)
 Importance: Undecided
 Status: New

** Also affects: python2.7 (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: python-stdlib-extensions (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: python2.7 (Ubuntu Bionic)
   Importance: Undecided
   Status: New

-- 
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/1899168

Title:
  SRU: update python2.7 to the 2.7.18 release

Status in python-stdlib-extensions package in Ubuntu:
  New
Status in python2.7 package in Ubuntu:
  New
Status in python-stdlib-extensions source package in Bionic:
  New
Status in python2.7 source package in Bionic:
  New

Bug description:
  This is a proposal to backport the Python 2.7.18 release to bionic,
  like it was done for 2.7.17 in LP: #1855133.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-stdlib-extensions/+bug/1899168/+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 1890272] Re: SRU: Update to the final python 2.7.18 release

[Matthias Klose]

builds ok, test results look ok.


** Tags removed: verification-needed verification-needed-focal
** Tags added: verification-done verification-done-focal

-- 
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/1890272

Title:
  SRU: Update to the final python 2.7.18 release

Status in python2.7 package in Ubuntu:
  New
Status in python2.7 source package in Focal:
  Fix Committed

Bug description:
  Ubuntu 20.04 LTS shipped with the python 2.7.18 release candidate.
  Please let's update to the final release.

  Upstream changes are:

  - Documentation changes

  - Identify as 2.7.18 instead of 2.7.18rc1

  Acceptance criteria: The package builds, and the testsuite doesn't
  show regressions.

  The package was also part of an archive test rebuild (main), and
  didn't show any regressions.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1890272/+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 1890270] Re: SRU: update gdb 9.2 for 20.04 LTS

[Matthias Klose]

package works as expected. test suite check done with the binary upload.

** Tags removed: verification-needed verification-needed-focal
** Tags added: verification-done verification-done-focal

-- 
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/1890270

Title:
  SRU: update gdb 9.2 for 20.04 LTS

Status in gdb package in Ubuntu:
  New
Status in gdb source package in Focal:
  Fix Committed

Bug description:
  SRU: update gdb 9.2 for 20.04 LTS

  according to https://sourceware.org/gdb/ this is a bug fix release:

  """
  This is a minor corrective release over GDB 9.1, fixing the following issues:

  PR tui/25586 (Resizing the source/disassembly or command window produces 
corrupted display)
  PR gdb/25650 (GDB can't 'printf' a convenience variable holding an inferior 
address)
  PR build/25981 (Use of short i386 register names breaks compilation on recent 
Solaris 11.4)
  PR symtab/26003 (infinite loop loading symbols from separate debug objfile)
  PR build/26029 (GDB build failure on SPARC)
  """

  Regression potential: minimal, package also not used by normal users,
  but for development.

  Acceptence criteria:  Package builds, no regressions in the testsuite.

  The package also was part of a focal test rebuild, see LP: #1879481.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1890270/+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 1890272] Re: SRU: Update to the final python 2.7.18 release

[Matthias Klose]

** Description changed:

  Ubuntu 20.04 LTS shipped with the python 2.7.18 release candidate.
  Please let's update to the final release.
  
  Upstream changes are:
  
  - Documentation changes
  
  - Identify as 2.7.18 instead of 2.7.18rc1
  
  Acceptance criteria: The package builds, and the testsuite doesn't show
  regressions.
+ 
+ The package was also part of an archive test rebuild (main), and didn't
+ show any regressions.

-- 
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/1890272

Title:
  SRU: Update to the final python 2.7.18 release

Status in python2.7 package in Ubuntu:
  New

Bug description:
  Ubuntu 20.04 LTS shipped with the python 2.7.18 release candidate.
  Please let's update to the final release.

  Upstream changes are:

  - Documentation changes

  - Identify as 2.7.18 instead of 2.7.18rc1

  Acceptance criteria: The package builds, and the testsuite doesn't
  show regressions.

  The package was also part of an archive test rebuild (main), and
  didn't show any regressions.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1890272/+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 1890270] Re: SRU: update gdb 9.2 for 20.04 LTS

[Matthias Klose]

** Description changed:

  SRU: update gdb 9.2 for 20.04 LTS
  
  according to https://sourceware.org/gdb/ this is a bug fix release:
  
  """
  This is a minor corrective release over GDB 9.1, fixing the following issues:
  
  PR tui/25586 (Resizing the source/disassembly or command window produces 
corrupted display)
  PR gdb/25650 (GDB can't 'printf' a convenience variable holding an inferior 
address)
  PR build/25981 (Use of short i386 register names breaks compilation on recent 
Solaris 11.4)
  PR symtab/26003 (infinite loop loading symbols from separate debug objfile)
  PR build/26029 (GDB build failure on SPARC)
  """
  
  Regression potential: minimal, package also not used by normal users,
  but for development.
  
  Acceptence criteria:  Package builds, no regressions in the testsuite.
+ 
+ The package also was part of a focal test rebuild, see LP: #1879481.

-- 
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/1890270

Title:
  SRU: update gdb 9.2 for 20.04 LTS

Status in gdb package in Ubuntu:
  New

Bug description:
  SRU: update gdb 9.2 for 20.04 LTS

  according to https://sourceware.org/gdb/ this is a bug fix release:

  """
  This is a minor corrective release over GDB 9.1, fixing the following issues:

  PR tui/25586 (Resizing the source/disassembly or command window produces 
corrupted display)
  PR gdb/25650 (GDB can't 'printf' a convenience variable holding an inferior 
address)
  PR build/25981 (Use of short i386 register names breaks compilation on recent 
Solaris 11.4)
  PR symtab/26003 (infinite loop loading symbols from separate debug objfile)
  PR build/26029 (GDB build failure on SPARC)
  """

  Regression potential: minimal, package also not used by normal users,
  but for development.

  Acceptence criteria:  Package builds, no regressions in the testsuite.

  The package also was part of a focal test rebuild, see LP: #1879481.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1890270/+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 1890270] Re: SRU: update gdb 9.2 for 20.04 LTS

[Matthias Klose]

** Description changed:

  SRU: update gdb 9.2 for 20.04 LTS
+ 
+ according to https://sourceware.org/gdb/ this is a bug fix release:
+ 
+ """
+ This is a minor corrective release over GDB 9.1, fixing the following issues:
+ 
+ PR tui/25586 (Resizing the source/disassembly or command window produces 
corrupted display)
+ PR gdb/25650 (GDB can't 'printf' a convenience variable holding an inferior 
address)
+ PR build/25981 (Use of short i386 register names breaks compilation on recent 
Solaris 11.4)
+ PR symtab/26003 (infinite loop loading symbols from separate debug objfile)
+ PR build/26029 (GDB build failure on SPARC)
+ """
+ 
+ Regression potential: minimal, package also not used by normal users,
+ but for development.
+ 
+ Acceptence criteria:  Package builds, no regressions in the testsuite.

-- 
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/1890270

Title:
  SRU: update gdb 9.2 for 20.04 LTS

Status in gdb package in Ubuntu:
  New

Bug description:
  SRU: update gdb 9.2 for 20.04 LTS

  according to https://sourceware.org/gdb/ this is a bug fix release:

  """
  This is a minor corrective release over GDB 9.1, fixing the following issues:

  PR tui/25586 (Resizing the source/disassembly or command window produces 
corrupted display)
  PR gdb/25650 (GDB can't 'printf' a convenience variable holding an inferior 
address)
  PR build/25981 (Use of short i386 register names breaks compilation on recent 
Solaris 11.4)
  PR symtab/26003 (infinite loop loading symbols from separate debug objfile)
  PR build/26029 (GDB build failure on SPARC)
  """

  Regression potential: minimal, package also not used by normal users,
  but for development.

  Acceptence criteria:  Package builds, no regressions in the testsuite.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1890270/+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 1891474] Re: gdk-pixbuf ftbfs in focal/s390x

[Matthias Klose]

that worked on the second retry

** Changed in: gdk-pixbuf (Ubuntu)
   Status: Confirmed => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gdk-pixbuf in Ubuntu.
https://bugs.launchpad.net/bugs/1891474

Title:
  gdk-pixbuf ftbfs in focal/s390x

Status in gdk-pixbuf package in Ubuntu:
  Invalid

Bug description:
  seen in a focal test rebuild:
  
https://launchpad.net/ubuntu/+archive/test-rebuild-20200810-focal/+build/19794513

  
  Ok:   22
  Expected Fail: 0
  Fail:  1
  Unexpected Pass:   0
  Skipped:   0
  Timeout:   0

  
  The output from the failed tests:

   6/23 gdk-pixbuf:slow / pixbuf-randomly-modified  FAIL 0.52 s
  (killed by signal 5 SIGTRAP)

  --- command ---
  16:22:55 
GDK_PIXBUF_MODULE_FILE='/<>/gdk-pixbuf-2.40.0+dfsg/obj-s390x-linux-gnu/gdk-pixbuf/loaders.cache'
 G_TEST_SRCDIR='/<>/gdk-pixbuf-2.40.0+dfsg/tests' 
G_TEST_BUILDDIR='/<>/gdk-pixbuf-2.40.0+dfsg/obj-s390x-linux-gnu/tests'
 
/<>/gdk-pixbuf-2.40.0+dfsg/obj-s390x-linux-gnu/tests/pixbuf-randomly-modified
 -k --tap
  --- stdout ---
  # random seed: R02S818441d868b74ad43d50db5aedeb15ea
  # GLib-GIO-DEBUG: _g_io_module_get_default: Found default implementation 
local (GLocalVfs) for ?gio-vfs?
  # Modified image is written to pixbuf-randomly-modified-image
  1..65
  # Start of pixbuf tests
  # Start of randomly-modified tests
  ok 1 /pixbuf/randomly-modified/bad-header.ico
  ok 2 /pixbuf/randomly-modified/bmp-line-overflow.bmp
  ok 3 /pixbuf/randomly-modified/bug775232.pnm
  ok 4 /pixbuf/randomly-modified/bug775242.bmp
  ok 5 /pixbuf/randomly-modified/bug775648.qtif
  ok 6 /pixbuf/randomly-modified/bug775697.jpg
  ok 7 /pixbuf/randomly-modified/bug776040.ico
  ok 8 /pixbuf/randomly-modified/crash.ico
  ok 9 /pixbuf/randomly-modified/decodecolormap.bmp
  ok 10 /pixbuf/randomly-modified/invalid.1.xpm
  ok 11 /pixbuf/randomly-modified/invalid.2.ico
  ok 12 /pixbuf/randomly-modified/invalid.4.ppm
  ok 13 /pixbuf/randomly-modified/valid.1.bmp
  ok 14 /pixbuf/randomly-modified/valid.1.gif
  Bail out! GLib-FATAL-ERROR: ../../../glib/gmem.c:173: failed to allocate 
131072 bytes
  --- stderr ---

  
(/<>/gdk-pixbuf-2.40.0+dfsg/obj-s390x-linux-gnu/tests/pixbuf-randomly-modified:10136):
 GLib-ERROR **: 16:22:56.100: ../../../glib/gmem.c:173: failed to allocate 
131072 bytes
  ---

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1891474/+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 1870088] Re: xz-utils ftbfs in focal

[Matthias Klose]

seen in a focal test rebuild:
https://launchpad.net/ubuntu/+archive/test-rebuild-20200810-focal/+build/19801445


** Changed in: xz-utils (Ubuntu Focal)
   Status: Fix Committed => Confirmed

** Tags added: rls-ff-incoming

-- 
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/1870088

Title:
  xz-utils ftbfs in focal

Status in xz-utils package in Ubuntu:
  Fix Released
Status in xz-utils source package in Focal:
  Confirmed
Status in xz-utils package in Debian:
  New

Bug description:
  seen in the second focal test rebuild
  
https://launchpad.net/ubuntu/+archive/test-rebuild-20200327-focal/+build/18988321/+files/buildlog_ubuntu-focal-amd64.xz-utils_5.2.4-1_BUILDING.txt.gz

  dh build --parallel 
  make[2]: Leaving directory '/<>'
 dh_testroot -O--parallel
 dh_prep -O--parallel
 debian/rules override_dh_auto_install
  make[2]: Entering directory '/<>'
  dh_auto_install --builddirectory debian/xzdec-build
  dh_auto_install --builddirectory debian/normal-build
  dh_auto_install --builddirectory debian/static-build
  set -e; arch=$(dpkg-architecture -qDEB_HOST_MULTIARCH); \
  install -d debian/tmp/lib/$arch; \
  mv debian/tmp/usr/lib/$arch/liblzma.so.* debian/tmp/lib/$arch/; \
  dso=$(basename $(readlink debian/tmp/usr/lib/$arch/liblzma.so)); \
  ln -s -f /lib/$arch/$dso debian/tmp/usr/lib/$arch/liblzma.so
  mv: cannot stat 'debian/tmp/usr/lib/x86_64-linux-gnu/liblzma.so.*': No such 
file or directory
  make[2]: *** [debian/rules:34: override_dh_auto_install] Error 1
  make[2]: Leaving directory '/<>'
  make[1]: *** [debian/rules:4: install] 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/xz-utils/+bug/1870088/+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