[Touch-packages] [Bug 1959325] Re: New binutils causes build failures for many RISC-V packages

2022-01-28 Thread 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

2022-01-27 Thread 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

2021-11-05 Thread 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

2021-09-16 Thread 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

2021-08-26 Thread 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

2021-08-26 Thread 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

2021-08-26 Thread 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

2021-08-15 Thread 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

2021-08-15 Thread 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

2021-08-13 Thread 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

2021-08-12 Thread 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]

2021-07-07 Thread 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]

2021-07-07 Thread 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

2021-07-07 Thread 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]

2021-07-06 Thread 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]

2021-07-06 Thread 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

2021-07-05 Thread 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]

2021-06-30 Thread 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

2021-06-28 Thread 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

2021-06-28 Thread 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

2021-06-01 Thread 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

2021-05-25 Thread 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

2021-05-20 Thread 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]

2021-05-08 Thread 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

2021-05-08 Thread 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

2021-05-07 Thread 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]

2021-05-07 Thread 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

2021-05-05 Thread 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

2021-05-05 Thread 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

2021-05-04 Thread 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

2021-05-04 Thread 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

2021-05-03 Thread 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

2021-05-03 Thread 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

2021-04-22 Thread 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

2021-04-22 Thread 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

2021-04-22 Thread 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

2021-03-29 Thread 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

2021-03-09 Thread 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

2021-03-09 Thread 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

2021-03-09 Thread 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

2021-02-18 Thread 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

2021-02-16 Thread 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

2021-02-10 Thread 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

2021-02-10 Thread 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

2021-02-10 Thread 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

2021-02-10 Thread 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

2021-02-10 Thread 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)

2021-02-08 Thread 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

2021-02-06 Thread 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)

2021-01-07 Thread 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

2020-12-17 Thread 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

2020-12-14 Thread 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

2020-12-14 Thread 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

2020-12-11 Thread 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

2020-11-26 Thread 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

2020-11-11 Thread 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

2020-11-09 Thread 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

2020-11-04 Thread 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

2020-10-30 Thread 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

2020-10-30 Thread 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

2020-10-29 Thread 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

2020-10-09 Thread 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

2020-09-25 Thread 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

2020-09-22 Thread 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

2020-09-17 Thread 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

2020-09-17 Thread 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

2020-09-04 Thread 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

2020-08-13 Thread 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

2020-08-13 Thread 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


[Touch-packages] [Bug 1891486] [NEW] vim ftbfs in focal (armhf, ppc64el)

2020-08-13 Thread Matthias Klose
Public bug reported:

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

---
Executed:  2257 Tests
 Skipped:31 Tests
  FAILED: 1 Tests


Failures: 
From test_debugger.vim:
Found errors in Test_Debugger():
function 
RunTheTest[40]..Test_Debugger[157]..RunDbgCmd[8]..WaitForAssert[2]..6_WaitForCommon[11]..59
 line 1: Expected 'No breakpoints defined' but got 'cmd: echo Foo()'
function 
RunTheTest[40]..Test_Debugger[185]..RunDbgCmd[8]..WaitForAssert[2]..6_WaitForCommon[11]..71
 line 1: Expected '19' but got '~\[  occurs 74 times]'
function 
RunTheTest[40]..Test_Debugger[188]..RunDbgCmd[8]..WaitForAssert[2]..6_WaitForCommon[11]..72
 line 1: Expected 'E161: Breakpoint not found: 2' but got '~\[  occurs 74 
times]'
function 
RunTheTest[40]..Test_Debugger[192]..RunDbgCmd[8]..WaitForAssert[2]..6_WaitForCommon[11]..73
 line 1: Expected 'Entering Debug mode.  Type "cont" to continue.' but got '~\[ 
 occurs 74 times]'
function 
RunTheTest[40]..Test_Debugger[192]..RunDbgCmd[8]..WaitForAssert[2]..6_WaitForCommon[11]..74
 line 1: Expected 'function Bazz' but got '~\[  occurs 74 times]'
function 
RunTheTest[40]..Test_Debugger[192]..RunDbgCmd[8]..WaitForAssert[2]..6_WaitForCommon[11]..75
 line 1: Expected 'line 2: let var1 = 3 + a:var' but got '~\[  occurs 74 times]'
function 
RunTheTest[40]..Test_Debugger[199]..RunDbgCmd[8]..WaitForAssert[2]..6_WaitForCommon[11]..76
 line 1: Expected '  3  func Bazz  line 2' but got '~\[  occurs 74 times]'
function 
RunTheTest[40]..Test_Debugger[199]..RunDbgCmd[8]..WaitForAssert[2]..6_WaitForCommon[11]..77
 line 1: Expected '  4  expr var3' but got '~\[  occurs 74 times]'
function 
RunTheTest[40]..Test_Debugger[201]..RunDbgCmd[8]..WaitForAssert[2]..6_WaitForCommon[11]..78
 line 1: Expected 'Breakpoint in "Bazz" line 5' but got '~\[  occurs 74 times]'
function 
RunTheTest[40]..Test_Debugger[201]..RunDbgCmd[8]..WaitForAssert[2]..6_WaitForCommon[11]..79
 line 1: Expected 'Oldval = "''another var''"' but got '~\[  occurs 74 times]'
function 
RunTheTest[40]..Test_Debugger[201]..RunDbgCmd[8]..WaitForAssert[2]..6_WaitForCommon[11]..80
 line 1: Expected 'Newval = "''value2''"' but got '~\[  occurs 74 times]'
function 
RunTheTest[40]..Test_Debugger[201]..RunDbgCmd[8]..WaitForAssert[2]..6_WaitForCommon[11]..81
 line 1: Expected 'function Bazz' but got '~\[  occurs 74 times]'
function 
RunTheTest[40]..Test_Debugger[201]..RunDbgCmd[8]..WaitForAssert[2]..6_WaitForCommon[11]..82
 line 1: Expected 'line 5: catch' but got '~\[  occurs 74 times]'
function 
RunTheTest[40]..Test_Debugger[208]..RunDbgCmd[8]..WaitForAssert[2]..6_WaitForCommon[11]..83
 line 1: Expected 'No breakpoints defined' but got '~\[  occurs 74 times]'
function 
RunTheTest[40]..Test_Debugger[211]..RunDbgCmd[8]..WaitForAssert[2]..6_WaitForCommon[11]..84
 line 1: Expected 'Error detected while processing function Bazz:' but got '~\[ 
 occurs 74 times]'
function 
RunTheTest[40]..Test_Debugger[211]..RunDbgCmd[8]..WaitForAssert[2]..6_WaitForCommon[11]..85
 line 1: Expected 'line5:' but got '~\[  occurs 74 times]'
function 
RunTheTest[40]..Test_Debugger[211]..RunDbgCmd[8]..WaitForAssert[2]..6_WaitForCommon[11]..86
 line 1: Expected 'E475: Invalid argument: abcd' but got '~\[  occurs 74 times]'
function 
RunTheTest[40]..Test_Debugger[215]..RunDbgCmd[8]..WaitForAssert[2]..6_WaitForCommon[11]..87
 line 1: Expected 'E475: Invalid argument: func' but got '~\[  occurs 74 times]'
function 
RunTheTest[40]..Test_Debugger[216]..RunDbgCmd[8]..WaitForAssert[2]..6_WaitForCommon[11]..88
 line 1: Expected 'E475: Invalid argument: func 2' but got '~\[  occurs 74 
times]'
function 
RunTheTest[40]..Test_Debugger[217]..RunDbgCmd[8]..WaitForAssert[2]..6_WaitForCommon[11]..89
 line 1: Expected 'E475: Invalid argument: func a()' but got '~\[  occurs 74 
times]'
function 
RunTheTest[40]..Test_Debugger[218]..RunDbgCmd[8]..WaitForAssert[2]..6_WaitForCommon[11]..90
 line 1: Expected 'E475: Invalid argument: abcd' but got '~\[  occurs 74 times]'
function 
RunTheTest[40]..Test_Debugger[219]..RunDbgCmd[8]..WaitForAssert[2]..6_WaitForCommon[11]..91
 line 1: Expected 'E475: Invalid argument: func' but got '~\[  occurs 74 times]'
function 
RunTheTest[40]..Test_Debugger[220]..RunDbgCmd[8]..WaitForAssert[2]..6_WaitForCommon[11]..92
 line 1: Expected 'E475: Invalid argument: func a()' but got '~\[  occurs 74 
times]'
function 
RunTheTest[40]..Test_Debugger[221]..RunDbgCmd[8]..WaitForAssert[2]..6_WaitForCommon[11]..93
 line 1: Expected 'E161: Breakpoint not found: func a' but got '~\[  occurs 74 
times]'
function 

[Touch-packages] [Bug 1891479] [NEW] pycurl ftbfs in focal (wait-deps)

2020-08-13 Thread Matthias Klose
Public bug reported:

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

Missing build dependencies: python-sphinx

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


** Tags: ftbfs rls-ff-incoming

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

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

** Tags added: ftbfs rls-ff-incoming

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

Title:
  pycurl ftbfs in focal (wait-deps)

Status in pycurl package in Ubuntu:
  Confirmed

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

  Missing build dependencies: python-sphinx

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

2020-08-13 Thread Matthias Klose
Public bug reported:

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

** Affects: gdk-pixbuf (Ubuntu)
 Importance: High
 Status: Confirmed


** Tags: ftbfs rls-ff-incoming

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

** Changed in: gdk-pixbuf (Ubuntu)
   Importance: Undecided => High

** Tags added: ftbfs rls-ff-incoming

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

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 1890272] [NEW] SRU: Update to the final python 2.7.18 release

2020-08-04 Thread Matthias Klose
Public bug reported:

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.

** Affects: python2.7 (Ubuntu)
 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/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.

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] [NEW] SRU: update gdb 9.2 for 20.04 LTS

2020-08-04 Thread Matthias Klose
Public bug reported:

SRU: update gdb 9.2 for 20.04 LTS

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

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 1883880] Re: fix non-8-bit x86 displacements breaking AVX512 builds on Bionic

2020-07-14 Thread Matthias Klose
yes, this looks sensible as a SRU

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

Title:
  fix non-8-bit x86 displacements breaking AVX512 builds on Bionic

Status in binutils package in Ubuntu:
  Fix Released
Status in binutils source package in Bionic:
  In Progress

Bug description:
  [Impact]

   * the assembler scales non 8 bit cases which was identified
 to break e.g. some AVX512 code. It is nasty as it isn't a compile/link/ 
 time error. Instead the instructions might silently be corrupted until 
 running. Things might even work on some but fail on other systems if 
 e.g. the AVX code paths only run on newer chips.

* The fix is upstream for a while and not re-changed again. Furthermore 
  it is in several Ubuntu releases without bugs due to that, which should 
  make the backport rather safe.

  [Test Case]

   * Simple example to trigger the bug:

  echo "vmovaps 0x40(,%rax,1),%zmm0" | as --64 -o avx.o && objdump -d
  avx.o | grep vmovaps

  The expected output is that the objdump output matches the vmovaps
  instruction input. When using binutils with the bug, the initial 0x40
  will be incorrect.

  Working:
  $ echo "vmovaps 0x40(,%rax,1),%zmm0" | as --64 -o avx.o && objdump -d avx.o | 
grep vmovaps
 0: 62 f1 7c 48 28 04 05 vmovaps 0x40(,%rax,1),%zmm0
  Failing:
  $ echo "vmovaps 0x40(,%rax,1),%zmm0" | as --64 -o avx.o && objdump -d avx.o | 
grep vmovaps
 0: 62 f1 7c 48 28 04 05 vmovaps 0x1(,%rax,1),%zmm0

  [Regression Potential]

   * Well, this is a double edged sword. On one hand this is fortunately a 
 small change and only affects something formerly clearly broken. So it 
 should be good and only change cases formerly being bad.
 But OTOH binutils areused in so many cases that I feel unable to say
 "nothing will happen". The change goes to the gnu assembler, so that is 
 the place to look out for regressions.

  [Other Info]
   
   * needs a sponsor experienced with binutils to check potential pitfalls


  
  ---

  
  Hi,
  DPDK has run into some issues in the past
   https://bugs.dpdk.org/show_bug.cgi?id=97
   https://bugs.dpdk.org/show_bug.cgi?id=249

  Eventually the issues got resolved in binutils via
   https://sourceware.org/bugzilla/show_bug.cgi?id=23465

  After binutils is fixed people rebuilding DPDK themselve can use
   http://patches.dpdk.org/patch/71679/
  to gain more performance while on Bionics bintuils level.

  Note: Bionic is on DPDK 17.11.x which will not get further stable release 
afaik. But quite often people build their own DPDK. In fact this came up as a 
request from Openvswitch upstream/Intel to allow such builds on Bionic.
  I'd ping those people about the bug and ask them to participate in the 
verification if this becomes an SRU.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1883880/+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 1882089] Re: RM: ubuntu-app-launch obsolete, unused, ftbfs

2020-06-04 Thread Matthias Klose
Removing packages from groovy:
url-dispatcher 0.1+17.04.20170328-0ubuntu6 in groovy
liburl-dispatcher1 0.1+17.04.20170328-0ubuntu6 in groovy amd64
liburl-dispatcher1 0.1+17.04.20170328-0ubuntu6 in groovy arm64
liburl-dispatcher1 0.1+17.04.20170328-0ubuntu6 in groovy armhf
liburl-dispatcher1 0.1+17.04.20170328-0ubuntu6 in groovy ppc64el
liburl-dispatcher1 0.1+17.04.20170328-0ubuntu6 in groovy s390x
liburl-dispatcher1-dev 0.1+17.04.20170328-0ubuntu6 in groovy 
amd64
liburl-dispatcher1-dev 0.1+17.04.20170328-0ubuntu6 in groovy 
arm64
liburl-dispatcher1-dev 0.1+17.04.20170328-0ubuntu6 in groovy 
armhf
liburl-dispatcher1-dev 0.1+17.04.20170328-0ubuntu6 in groovy 
ppc64el
liburl-dispatcher1-dev 0.1+17.04.20170328-0ubuntu6 in groovy 
s390x
url-dispatcher 0.1+17.04.20170328-0ubuntu6 in groovy amd64
url-dispatcher 0.1+17.04.20170328-0ubuntu6 in groovy arm64
url-dispatcher 0.1+17.04.20170328-0ubuntu6 in groovy armhf
url-dispatcher 0.1+17.04.20170328-0ubuntu6 in groovy ppc64el
url-dispatcher 0.1+17.04.20170328-0ubuntu6 in groovy s390x
url-dispatcher-testability 0.1+17.04.20170328-0ubuntu6 in 
groovy amd64
url-dispatcher-testability 0.1+17.04.20170328-0ubuntu6 in 
groovy arm64
url-dispatcher-testability 0.1+17.04.20170328-0ubuntu6 in 
groovy armhf
url-dispatcher-testability 0.1+17.04.20170328-0ubuntu6 in 
groovy i386
url-dispatcher-testability 0.1+17.04.20170328-0ubuntu6 in 
groovy ppc64el
url-dispatcher-testability 0.1+17.04.20170328-0ubuntu6 in 
groovy riscv64
url-dispatcher-testability 0.1+17.04.20170328-0ubuntu6 in 
groovy s390x
url-dispatcher-tools 0.1+17.04.20170328-0ubuntu6 in groovy amd64
url-dispatcher-tools 0.1+17.04.20170328-0ubuntu6 in groovy arm64
url-dispatcher-tools 0.1+17.04.20170328-0ubuntu6 in groovy armhf
url-dispatcher-tools 0.1+17.04.20170328-0ubuntu6 in groovy 
ppc64el
url-dispatcher-tools 0.1+17.04.20170328-0ubuntu6 in groovy s390x
url-dispatcher-tools-gui 0.1+17.04.20170328-0ubuntu6 in groovy 
amd64
url-dispatcher-tools-gui 0.1+17.04.20170328-0ubuntu6 in groovy 
arm64
url-dispatcher-tools-gui 0.1+17.04.20170328-0ubuntu6 in groovy 
armhf
url-dispatcher-tools-gui 0.1+17.04.20170328-0ubuntu6 in groovy 
ppc64el
url-dispatcher-tools-gui 0.1+17.04.20170328-0ubuntu6 in groovy 
s390x
Comment: LP: #1882089, remove
1 package successfully removed.


** Changed in: url-dispatcher (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  RM: ubuntu-app-launch obsolete, unused, ftbfs

Status in ubuntu-app-launch package in Ubuntu:
  Fix Released
Status in url-dispatcher package in Ubuntu:
  Fix Released

Bug description:
  RM: ubuntu-app-launch obsolete, unused, ftbfs

  ubuntu-app-launch is obsolete, unused by any Desktop Environment in
  the Archive.

  It also ftbfs with new glib / unity bindings.

  There are four packages in the archive that still link/depend/use
  ubuntu-app-launch, and all of them are now fixed in groovy-proposed,
  and should migrate soon.

  url-dispatcher is also obsolete and should be simply removed together
  with ubuntu-app-launch.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-app-launch/+bug/1882089/+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 1882089] Re: RM: ubuntu-app-launch obsolete, unused, ftbfs

2020-06-04 Thread Matthias Klose
Removing packages from groovy:
ubuntu-app-launch 0.12+17.04.20170404.2-0ubuntu6 in groovy
gir1.2-ubuntu-app-launch-3 0.12+17.04.20170404.2-0ubuntu6 in 
groovy amd64
gir1.2-ubuntu-app-launch-3 0.12+17.04.20170404.2-0ubuntu6 in 
groovy arm64
gir1.2-ubuntu-app-launch-3 0.12+17.04.20170404.2-0ubuntu6 in 
groovy armhf
gir1.2-ubuntu-app-launch-3 0.12+17.04.20170404.2-0ubuntu6 in 
groovy ppc64el
gir1.2-ubuntu-app-launch-3 0.12+17.04.20170404.2-0ubuntu6 in 
groovy s390x
libubuntu-app-launch3-dev 0.12+17.04.20170404.2-0ubuntu6 in 
groovy amd64
libubuntu-app-launch3-dev 0.12+17.04.20170404.2-0ubuntu6 in 
groovy arm64
libubuntu-app-launch3-dev 0.12+17.04.20170404.2-0ubuntu6 in 
groovy armhf
libubuntu-app-launch3-dev 0.12+17.04.20170404.2-0ubuntu6 in 
groovy ppc64el
libubuntu-app-launch3-dev 0.12+17.04.20170404.2-0ubuntu6 in 
groovy s390x
libubuntu-app-launch4 0.12+17.04.20170404.2-0ubuntu6 in groovy 
amd64
libubuntu-app-launch4 0.12+17.04.20170404.2-0ubuntu6 in groovy 
arm64
libubuntu-app-launch4 0.12+17.04.20170404.2-0ubuntu6 in groovy 
armhf
libubuntu-app-launch4 0.12+17.04.20170404.2-0ubuntu6 in groovy 
ppc64el
libubuntu-app-launch4 0.12+17.04.20170404.2-0ubuntu6 in groovy 
s390x
ubuntu-app-launch 0.12+17.04.20170404.2-0ubuntu6 in groovy amd64
ubuntu-app-launch 0.12+17.04.20170404.2-0ubuntu6 in groovy arm64
ubuntu-app-launch 0.12+17.04.20170404.2-0ubuntu6 in groovy armhf
ubuntu-app-launch 0.12+17.04.20170404.2-0ubuntu6 in groovy 
ppc64el
ubuntu-app-launch 0.12+17.04.20170404.2-0ubuntu6 in groovy s390x
ubuntu-app-launch-tools 0.12+17.04.20170404.2-0ubuntu6 in 
groovy amd64
ubuntu-app-launch-tools 0.12+17.04.20170404.2-0ubuntu6 in 
groovy arm64
ubuntu-app-launch-tools 0.12+17.04.20170404.2-0ubuntu6 in 
groovy armhf
ubuntu-app-launch-tools 0.12+17.04.20170404.2-0ubuntu6 in 
groovy ppc64el
ubuntu-app-launch-tools 0.12+17.04.20170404.2-0ubuntu6 in 
groovy s390x
ubuntu-app-test 0.12+17.04.20170404.2-0ubuntu6 in groovy amd64
ubuntu-app-test 0.12+17.04.20170404.2-0ubuntu6 in groovy arm64
ubuntu-app-test 0.12+17.04.20170404.2-0ubuntu6 in groovy armhf
ubuntu-app-test 0.12+17.04.20170404.2-0ubuntu6 in groovy ppc64el
ubuntu-app-test 0.12+17.04.20170404.2-0ubuntu6 in groovy s390x
Comment: LP: #1882089, remove
1 package successfully removed.


** Changed in: ubuntu-app-launch (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  RM: ubuntu-app-launch obsolete, unused, ftbfs

Status in ubuntu-app-launch package in Ubuntu:
  Fix Released
Status in url-dispatcher package in Ubuntu:
  Fix Released

Bug description:
  RM: ubuntu-app-launch obsolete, unused, ftbfs

  ubuntu-app-launch is obsolete, unused by any Desktop Environment in
  the Archive.

  It also ftbfs with new glib / unity bindings.

  There are four packages in the archive that still link/depend/use
  ubuntu-app-launch, and all of them are now fixed in groovy-proposed,
  and should migrate soon.

  url-dispatcher is also obsolete and should be simply removed together
  with ubuntu-app-launch.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-app-launch/+bug/1882089/+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 1879721] Re: zmqpp: ftbfs in groovy, no rdeps, remove the package

2020-05-20 Thread Matthias Klose
Removing packages from groovy:
zmqpp 4.1.2-0ubuntu2 in groovy
libzmqpp-dev 4.1.2-0ubuntu2 in groovy amd64
libzmqpp-dev 4.1.2-0ubuntu2 in groovy arm64
libzmqpp-dev 4.1.2-0ubuntu2 in groovy armhf
libzmqpp-dev 4.1.2-0ubuntu2 in groovy ppc64el
libzmqpp-dev 4.1.2-0ubuntu2 in groovy s390x
libzmqpp4 4.1.2-0ubuntu2 in groovy amd64
libzmqpp4 4.1.2-0ubuntu2 in groovy arm64
libzmqpp4 4.1.2-0ubuntu2 in groovy armhf
libzmqpp4 4.1.2-0ubuntu2 in groovy ppc64el
libzmqpp4 4.1.2-0ubuntu2 in groovy s390x
Comment: LP: #1879721, remove zmqpp, no rdeps
1 package successfully removed.


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

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

Title:
  zmqpp: ftbfs in groovy, no rdeps, remove the package

Status in zmqpp package in Ubuntu:
  Fix Released

Bug description:
  zmqpp: ftbfs in groovy, no rdeps, remove the package

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zmqpp/+bug/1879721/+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 1879721] [NEW] zmqpp: ftbfs in groovy, no rdeps, remove the package

2020-05-20 Thread Matthias Klose
Public bug reported:

zmqpp: ftbfs in groovy, no rdeps, remove the package

** Affects: zmqpp (Ubuntu)
 Importance: Undecided
 Status: Fix Released

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

Title:
  zmqpp: ftbfs in groovy, no rdeps, remove the package

Status in zmqpp package in Ubuntu:
  Fix Released

Bug description:
  zmqpp: ftbfs in groovy, no rdeps, remove the package

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zmqpp/+bug/1879721/+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 1878517] Re: please apply bash 5.0 patch 17

2020-05-14 Thread Matthias Klose
** Tags added: rls-ff-incoming

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

Title:
  please apply bash 5.0 patch 17

Status in bash package in Ubuntu:
  New

Bug description:
  I am using Ubuntu 20.04 for development and has hit a bug in bash 5.0
  patch 16.

  I can't reproduce it in pure bash, but with bats from
  https://github.com/bats-core/bats-core/ it is very easy to repro:

  ```
  # cat << EOF > ya.bats
  check() {
echo "check $@"
ls -l /proc/self/fd
  }

  @test "here file" {
check -p <(echo "hey")
false
  }
  EOF

  $ bats ya.bats
  ```

  Normally the output should contain the line

 lr-x-- 1 kir kir 64 May 14 02:01 63 -> pipe:[4616918]

  which is a result of a "here file" created by bash via <(echo "hey").

  In my testing, about 50% of runs don't have /dev/fd/63 listed.

  I found out this is a manifest of a bug introduced in bash 5.0 patch
  16 (see http://ftp.gnu.org/gnu/bash/bash-5.0-patches/bash50-016)

  The bug is fixed in 5.0 patch 17 (see
  http://ftp.gnu.org/gnu/bash/bash-5.0-patches/bash50-017).

  Please update bash to patchlevel 17.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1878517/+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 1873989] Re: Please remove wallpaper from Ubuntu

2020-04-22 Thread Matthias Klose
Removing packages from focal:
wallpaper 0.1-1ubuntu1 in focal
wallpaper 0.1-1ubuntu1 in focal amd64
wallpaper 0.1-1ubuntu1 in focal arm64
wallpaper 0.1-1ubuntu1 in focal armhf
wallpaper 0.1-1ubuntu1 in focal i386
wallpaper 0.1-1ubuntu1 in focal ppc64el
wallpaper 0.1-1ubuntu1 in focal riscv64
wallpaper 0.1-1ubuntu1 in focal s390x
Comment: LP: #1873989; remove, no rdeps
1 package successfully removed.


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

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

Title:
  Please remove wallpaper from Ubuntu

Status in ubuntu-meta package in Ubuntu:
  New
Status in wallpaper package in Ubuntu:
  Fix Released

Bug description:
  Ancient Ubuntu-only package with no rdeps that FTBFS on rebuild. No
  new upstream release since 2002 (https://www.cgarbs.de/stuff.en.html).
  Appears to just check if a given image(s) can be used as wallpaper -
  doesn't seem to merit inclusion as a package to me (the Bash script is
  available on the developer's site if people want it).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1873989/+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 1872502] Re: There is no installable python package on Focal

2020-04-14 Thread Matthias Klose
we have removed any reference to the python package in the archive.
Packages have to explicitly depend on python2 or python3.

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

Title:
  There is no installable python package on Focal

Status in python-defaults package in Ubuntu:
  New

Bug description:
  There is no installable "python" package on Focal. An attempt to
  install it produces the following error:

  $ sudo apt install python
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Package python is not available, but is referred to by another package.
  This may mean that the package is missing, has been obsoleted, or
  is only available from another source
  However the following packages replace it:
python2-minimal:i386 python2:i386 python2-minimal python2 python-is-python2 
2to3 python-is-python3

  E: Package 'python' has no installation candidate

  This breaks the installation of many other software packages which
  have the "python" package as a dependency.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-defaults/+bug/1872502/+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 1869814] Re: ubuntu-docs build failure - possible solution

2020-04-11 Thread Matthias Klose
** Changed in: libxml2 (Ubuntu)
   Status: In Progress => Fix Committed

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

Title:
  ubuntu-docs build failure - possible solution

Status in libxml2:
  New
Status in libxml2 package in Ubuntu:
  Fix Committed
Status in ubuntu-docs package in Ubuntu:
  Fix Released

Bug description:
  ubuntu-docs failed to build during the second Focal Fossa test
  rebuild:

  https://launchpad.net/ubuntu/+archive/test-
  rebuild-20200327-focal/+build/18982738

  It was itstool which failed to generate the localized zh_CN pages. If
  dropping zh_CN from ubuntu-help/Makefile.am, ubuntu-docs builds. But
  excluding the Chinese pages is apparently not an acceptable solution.

  The itstool package in focal {build-,}depends on python3. I built
  itstool in a PPA with python2 instead, and in that PPA ubuntu-docs
  built fine without modifications:

  https://launchpad.net/~gunnarhj/+archive/ubuntu/ubuntu-docs/+packages

  So the root cause seems to lie neither in ubuntu-docs nor itstool. I
  would suspect that python3-libxml2 is buggy, but since itstool was
  built against python2 in eoan, it's hard to tell if it's a regression.

  Would building itstool against python2 be an acceptable workaround in
  focal?

To manage notifications about this bug go to:
https://bugs.launchpad.net/libxml2/+bug/1869814/+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 1871111] Re: libaccounts-glib ftbfs in focal (test failure)

2020-04-07 Thread Matthias Klose
** Changed in: libaccounts-glib (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  libaccounts-glib ftbfs in focal (test failure)

Status in libaccounts-glib package in Ubuntu:
  Fix Released

Bug description:
  libaccounts-glib ftbfs in focal (test failure). the version in
  -proposed is needed to migrate for the python removal.

  https://launchpad.net/ubuntu/+source/libaccounts-
  glib/1.23+17.04.20161104-0ubuntu2

  FAIL: accounts-glib-test.sh
  ===

  Using dbus-test-runner
  (dbus-test-runner:8227): GLib-DEBUG: 15:12:24.315: posix_spawn avoided 
(workdir specified) (fd close requested) (child_setup specified) 
  (dbus-test-runner:8227): GLib-DEBUG: 15:12:24.316: posix_spawn avoided 
(automatic reaping requested) (fd close requested) 
  DBus daemon: 
unix:abstract=/tmp/dbus-xkXL1ezQug,guid=2934344a2dcc5fe1e7fb5b285e7e17d8
  (dbus-test-runner:8227): GLib-DEBUG: 15:12:24.318: setenv()/putenv() are not 
thread-safe and should not be used after threads are created
  (dbus-test-runner:8227): GLib-DEBUG: 15:12:24.318: setenv()/putenv() are not 
thread-safe and should not be used after threads are created
  (dbus-test-runner:8227): GLib-DEBUG: 15:12:24.318: setenv()/putenv() are not 
thread-safe and should not be used after threads are created
  (dbus-test-runner:8227): GLib-DEBUG: 15:12:24.318: posix_spawn avoided 
(workdir specified) (fd close requested) 
  task-0: Started with PID: 8233
  task-0: Running suite(s): accounts-glib
  task-0: ** (process:8262): DEBUG: 15:12:24.409: Error message: 
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name 
com.google.code.AccountsSSO.Accounts.Manager was not provided by any .service 
files
  task-0: ** (process:8262): DEBUG: 15:12:24.410: Ending read-only test
  task-0: (process:8271): GLib-DEBUG: 15:12:24.434: setenv()/putenv() are not 
thread-safe and should not be used after threads are created
  task-0: (process:8271): GLib-DEBUG: 15:12:24.436: unsetenv() is not 
thread-safe and should not be used after threads are created
  task-0: (process:8271): GLib-DEBUG: 15:12:24.436: setenv()/putenv() are not 
thread-safe and should not be used after threads are created
  task-0: (process:8271): GLib-DEBUG: 15:12:24.436: setenv()/putenv() are not 
thread-safe and should not be used after threads are created
  task-0: ** (process:8274): DEBUG: 15:12:24.443: Running loop
  task-0: ** (process:8278): DEBUG: 15:12:24.447: Running loop
  task-0: ** (process:8278): DEBUG: 15:12:24.547: releasing lock
  task-0: ** (process:8278): DEBUG: 15:12:24.549: account_store_locked_cb called
  task-0: ** (process:8282): DEBUG: 15:12:24.554: Running loop

  (process:8282): GLib-GIO-CRITICAL **: 15:12:24.654: g_task_return_boolean: 
assertion '!task->ever_returned' failed
  task-0: ** (process:8282): DEBUG: 15:12:24.654: Cancelling 0x56117363d660
  task-0: ** (process:8286): DEBUG: 15:12:24.820: 
test_store_read_only_handle_store_cb called
  task-0: ** (process:8286): DEBUG: 15:12:24.821: test_store_read_only_store_cb 
called
  task-0: ** (process:8289): DEBUG: 15:12:24.840:  Service tag: messaging
  task-0: ** (process:8289): DEBUG: 15:12:24.840:  Service tag: e-mail
  task-0: ** (process:8289): DEBUG: 15:12:24.841:  Service tag: sharing
  task-0: ** (process:8289): DEBUG: 15:12:24.842:  Service tag: video
  task-0: ** (process:8289): DEBUG: 15:12:25.407: Service id: 1
  task-0: ** (process:8289): DEBUG: 15:12:25.407: Service2 id: 2
  task-0: ** (process:8289): DEBUG: 15:12:25.407: Account id: 1

  (process:8289): accounts-glib-WARNING **: 15:12:25.408: Unable to load 
account 3
  task-0: ** (process:8296): DEBUG: 15:12:25.423: Got key parameters/server of 
type gchararray
  task-0: ** (process:8296): DEBUG: 15:12:25.423: Got key parameters/old-ssl of 
type gboolean
  task-0: ** (process:8296): DEBUG: 15:12:25.423: Got key 
parameters/fallback-conference-server of type gchararray
  task-0: ** (process:8296): DEBUG: 15:12:25.423: Got key parameters/port of 
type gint
  task-0: ** (process:8296): DEBUG: 15:12:25.425: Got key port of type gint
  task-0: ** (process:8296): DEBUG: 15:12:25.425: Got key message of type 
gchararray
  task-0: ** (process:8296): DEBUG: 15:12:25.425: Got key server of type 
gchararray
  task-0: ** (process:8296): DEBUG: 15:12:25.425: Got key old-ssl of type 
gboolean
  task-0: ** (process:8296): DEBUG: 15:12:25.425: Got key 
fallback-conference-server of type gchararray
  task-0: ** (process:8300): DEBUG: 15:12:25.430: Got key parameters/server of 
type s
  task-0: ** (process:8300): DEBUG: 15:12:25.430: Got key parameters/old-ssl of 
type b
  task-0: ** (process:8300): DEBUG: 15:12:25.430: Got key 
parameters/fallback-conference-server of type s
  task-0: ** (process:8300): DEBUG: 15:12:25.431: Got key parameters/port of 
type i
  

[Touch-packages] [Bug 1863532] Re: Invoking "python" brings inappropriate response from command-not-found when python3 installed

2020-04-07 Thread Matthias Klose
the current aligned output is more readable. So either leave it this
way, or keep it aligned while removing the space within the quotes.

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

Title:
  Invoking "python" brings inappropriate response from command-not-found
  when python3 installed

Status in command-not-found package in Ubuntu:
  Triaged
Status in python3-defaults package in Ubuntu:
  Triaged
Status in command-not-found source package in Focal:
  Triaged
Status in python3-defaults source package in Focal:
  Triaged

Bug description:
  Ubuntu Mate 20.04 development release, upgraded from 19.10. I don't
  have python 2.7 installed, but have python 3 installed as per default.

  Please see ascii-cast at
  https://asciinema.org/a/SZR20NHz2FN6N6O1hj2Mqmnv8 .

  Running `python` brings up text from command-not-found which suggests
  installing `python3` as a solution to the missing command. `python3`
  is already installed, is a later version than the one indicated by
  command-not-found and does not supply a binary or symlink named
  `python`.

  $ apt policy python
  python:
Installed: (none)
Candidate: (none)
Version table:
   2.7.17-1 -1
  100 /var/lib/dpkg/status
  $ apt policy python3
  python3:
Installed: 3.8.0-3
Candidate: 3.8.0-3
Version table:
   *** 3.8.0-3 500
  500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status
  $ apt policy command-not-found
  command-not-found:
Installed: 19.10.0
Candidate: 19.10.0
Version table:
   *** 19.10.0 500
  500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  500 http://gb.archive.ubuntu.com/ubuntu focal/main i386 Packages
  100 /var/lib/dpkg/status

  I don't know whether this is a bug in python3 or command-not-found
  (the latter of which doesn't seem to have been updated for 20.04 yet).
  i don't know if it is intentional that `python3` will not provide a
  binary or symlink named `python`. if that is the case, the output of
  `command-not-found` should be updated to reflect that.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: python3 3.8.0-3
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Mon Feb 17 01:35:16 2020
  InstallationDate: Installed on 2019-10-11 (128 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20190926.2)
  SourcePackage: python3-defaults
  UpgradeStatus: Upgraded to focal on 2020-02-07 (10 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/command-not-found/+bug/1863532/+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 1871111] Re: libaccounts-glib ftbfs in focal (test failure)

2020-04-07 Thread Matthias Klose
fixed in 1.23+17.04.20161104-0ubuntu3


** Changed in: libaccounts-glib (Ubuntu)
   Status: Confirmed => Fix Committed

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

Title:
  libaccounts-glib ftbfs in focal (test failure)

Status in libaccounts-glib package in Ubuntu:
  Fix Committed

Bug description:
  libaccounts-glib ftbfs in focal (test failure). the version in
  -proposed is needed to migrate for the python removal.

  https://launchpad.net/ubuntu/+source/libaccounts-
  glib/1.23+17.04.20161104-0ubuntu2

  FAIL: accounts-glib-test.sh
  ===

  Using dbus-test-runner
  (dbus-test-runner:8227): GLib-DEBUG: 15:12:24.315: posix_spawn avoided 
(workdir specified) (fd close requested) (child_setup specified) 
  (dbus-test-runner:8227): GLib-DEBUG: 15:12:24.316: posix_spawn avoided 
(automatic reaping requested) (fd close requested) 
  DBus daemon: 
unix:abstract=/tmp/dbus-xkXL1ezQug,guid=2934344a2dcc5fe1e7fb5b285e7e17d8
  (dbus-test-runner:8227): GLib-DEBUG: 15:12:24.318: setenv()/putenv() are not 
thread-safe and should not be used after threads are created
  (dbus-test-runner:8227): GLib-DEBUG: 15:12:24.318: setenv()/putenv() are not 
thread-safe and should not be used after threads are created
  (dbus-test-runner:8227): GLib-DEBUG: 15:12:24.318: setenv()/putenv() are not 
thread-safe and should not be used after threads are created
  (dbus-test-runner:8227): GLib-DEBUG: 15:12:24.318: posix_spawn avoided 
(workdir specified) (fd close requested) 
  task-0: Started with PID: 8233
  task-0: Running suite(s): accounts-glib
  task-0: ** (process:8262): DEBUG: 15:12:24.409: Error message: 
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name 
com.google.code.AccountsSSO.Accounts.Manager was not provided by any .service 
files
  task-0: ** (process:8262): DEBUG: 15:12:24.410: Ending read-only test
  task-0: (process:8271): GLib-DEBUG: 15:12:24.434: setenv()/putenv() are not 
thread-safe and should not be used after threads are created
  task-0: (process:8271): GLib-DEBUG: 15:12:24.436: unsetenv() is not 
thread-safe and should not be used after threads are created
  task-0: (process:8271): GLib-DEBUG: 15:12:24.436: setenv()/putenv() are not 
thread-safe and should not be used after threads are created
  task-0: (process:8271): GLib-DEBUG: 15:12:24.436: setenv()/putenv() are not 
thread-safe and should not be used after threads are created
  task-0: ** (process:8274): DEBUG: 15:12:24.443: Running loop
  task-0: ** (process:8278): DEBUG: 15:12:24.447: Running loop
  task-0: ** (process:8278): DEBUG: 15:12:24.547: releasing lock
  task-0: ** (process:8278): DEBUG: 15:12:24.549: account_store_locked_cb called
  task-0: ** (process:8282): DEBUG: 15:12:24.554: Running loop

  (process:8282): GLib-GIO-CRITICAL **: 15:12:24.654: g_task_return_boolean: 
assertion '!task->ever_returned' failed
  task-0: ** (process:8282): DEBUG: 15:12:24.654: Cancelling 0x56117363d660
  task-0: ** (process:8286): DEBUG: 15:12:24.820: 
test_store_read_only_handle_store_cb called
  task-0: ** (process:8286): DEBUG: 15:12:24.821: test_store_read_only_store_cb 
called
  task-0: ** (process:8289): DEBUG: 15:12:24.840:  Service tag: messaging
  task-0: ** (process:8289): DEBUG: 15:12:24.840:  Service tag: e-mail
  task-0: ** (process:8289): DEBUG: 15:12:24.841:  Service tag: sharing
  task-0: ** (process:8289): DEBUG: 15:12:24.842:  Service tag: video
  task-0: ** (process:8289): DEBUG: 15:12:25.407: Service id: 1
  task-0: ** (process:8289): DEBUG: 15:12:25.407: Service2 id: 2
  task-0: ** (process:8289): DEBUG: 15:12:25.407: Account id: 1

  (process:8289): accounts-glib-WARNING **: 15:12:25.408: Unable to load 
account 3
  task-0: ** (process:8296): DEBUG: 15:12:25.423: Got key parameters/server of 
type gchararray
  task-0: ** (process:8296): DEBUG: 15:12:25.423: Got key parameters/old-ssl of 
type gboolean
  task-0: ** (process:8296): DEBUG: 15:12:25.423: Got key 
parameters/fallback-conference-server of type gchararray
  task-0: ** (process:8296): DEBUG: 15:12:25.423: Got key parameters/port of 
type gint
  task-0: ** (process:8296): DEBUG: 15:12:25.425: Got key port of type gint
  task-0: ** (process:8296): DEBUG: 15:12:25.425: Got key message of type 
gchararray
  task-0: ** (process:8296): DEBUG: 15:12:25.425: Got key server of type 
gchararray
  task-0: ** (process:8296): DEBUG: 15:12:25.425: Got key old-ssl of type 
gboolean
  task-0: ** (process:8296): DEBUG: 15:12:25.425: Got key 
fallback-conference-server of type gchararray
  task-0: ** (process:8300): DEBUG: 15:12:25.430: Got key parameters/server of 
type s
  task-0: ** (process:8300): DEBUG: 15:12:25.430: Got key parameters/old-ssl of 
type b
  task-0: ** (process:8300): DEBUG: 15:12:25.430: Got key 
parameters/fallback-conference-server of type s
  task-0: ** (process:8300): DEBUG: 15:12:25.431: 

[Touch-packages] [Bug 1871111] [NEW] libaccounts-glib ftbfs in focal (test failure)

2020-04-06 Thread Matthias Klose
Public bug reported:

libaccounts-glib ftbfs in focal (test failure). the version in -proposed
is needed to migrate for the python removal.

https://launchpad.net/ubuntu/+source/libaccounts-
glib/1.23+17.04.20161104-0ubuntu2

FAIL: accounts-glib-test.sh
===

Using dbus-test-runner
(dbus-test-runner:8227): GLib-DEBUG: 15:12:24.315: posix_spawn avoided (workdir 
specified) (fd close requested) (child_setup specified) 
(dbus-test-runner:8227): GLib-DEBUG: 15:12:24.316: posix_spawn avoided 
(automatic reaping requested) (fd close requested) 
DBus daemon: 
unix:abstract=/tmp/dbus-xkXL1ezQug,guid=2934344a2dcc5fe1e7fb5b285e7e17d8
(dbus-test-runner:8227): GLib-DEBUG: 15:12:24.318: setenv()/putenv() are not 
thread-safe and should not be used after threads are created
(dbus-test-runner:8227): GLib-DEBUG: 15:12:24.318: setenv()/putenv() are not 
thread-safe and should not be used after threads are created
(dbus-test-runner:8227): GLib-DEBUG: 15:12:24.318: setenv()/putenv() are not 
thread-safe and should not be used after threads are created
(dbus-test-runner:8227): GLib-DEBUG: 15:12:24.318: posix_spawn avoided (workdir 
specified) (fd close requested) 
task-0: Started with PID: 8233
task-0: Running suite(s): accounts-glib
task-0: ** (process:8262): DEBUG: 15:12:24.409: Error message: 
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name 
com.google.code.AccountsSSO.Accounts.Manager was not provided by any .service 
files
task-0: ** (process:8262): DEBUG: 15:12:24.410: Ending read-only test
task-0: (process:8271): GLib-DEBUG: 15:12:24.434: setenv()/putenv() are not 
thread-safe and should not be used after threads are created
task-0: (process:8271): GLib-DEBUG: 15:12:24.436: unsetenv() is not thread-safe 
and should not be used after threads are created
task-0: (process:8271): GLib-DEBUG: 15:12:24.436: setenv()/putenv() are not 
thread-safe and should not be used after threads are created
task-0: (process:8271): GLib-DEBUG: 15:12:24.436: setenv()/putenv() are not 
thread-safe and should not be used after threads are created
task-0: ** (process:8274): DEBUG: 15:12:24.443: Running loop
task-0: ** (process:8278): DEBUG: 15:12:24.447: Running loop
task-0: ** (process:8278): DEBUG: 15:12:24.547: releasing lock
task-0: ** (process:8278): DEBUG: 15:12:24.549: account_store_locked_cb called
task-0: ** (process:8282): DEBUG: 15:12:24.554: Running loop

(process:8282): GLib-GIO-CRITICAL **: 15:12:24.654: g_task_return_boolean: 
assertion '!task->ever_returned' failed
task-0: ** (process:8282): DEBUG: 15:12:24.654: Cancelling 0x56117363d660
task-0: ** (process:8286): DEBUG: 15:12:24.820: 
test_store_read_only_handle_store_cb called
task-0: ** (process:8286): DEBUG: 15:12:24.821: test_store_read_only_store_cb 
called
task-0: ** (process:8289): DEBUG: 15:12:24.840:  Service tag: messaging
task-0: ** (process:8289): DEBUG: 15:12:24.840:  Service tag: e-mail
task-0: ** (process:8289): DEBUG: 15:12:24.841:  Service tag: sharing
task-0: ** (process:8289): DEBUG: 15:12:24.842:  Service tag: video
task-0: ** (process:8289): DEBUG: 15:12:25.407: Service id: 1
task-0: ** (process:8289): DEBUG: 15:12:25.407: Service2 id: 2
task-0: ** (process:8289): DEBUG: 15:12:25.407: Account id: 1

(process:8289): accounts-glib-WARNING **: 15:12:25.408: Unable to load account 3
task-0: ** (process:8296): DEBUG: 15:12:25.423: Got key parameters/server of 
type gchararray
task-0: ** (process:8296): DEBUG: 15:12:25.423: Got key parameters/old-ssl of 
type gboolean
task-0: ** (process:8296): DEBUG: 15:12:25.423: Got key 
parameters/fallback-conference-server of type gchararray
task-0: ** (process:8296): DEBUG: 15:12:25.423: Got key parameters/port of type 
gint
task-0: ** (process:8296): DEBUG: 15:12:25.425: Got key port of type gint
task-0: ** (process:8296): DEBUG: 15:12:25.425: Got key message of type 
gchararray
task-0: ** (process:8296): DEBUG: 15:12:25.425: Got key server of type 
gchararray
task-0: ** (process:8296): DEBUG: 15:12:25.425: Got key old-ssl of type gboolean
task-0: ** (process:8296): DEBUG: 15:12:25.425: Got key 
fallback-conference-server of type gchararray
task-0: ** (process:8300): DEBUG: 15:12:25.430: Got key parameters/server of 
type s
task-0: ** (process:8300): DEBUG: 15:12:25.430: Got key parameters/old-ssl of 
type b
task-0: ** (process:8300): DEBUG: 15:12:25.430: Got key 
parameters/fallback-conference-server of type s
task-0: ** (process:8300): DEBUG: 15:12:25.431: Got key parameters/port of type 
i
task-0: ** (process:8300): DEBUG: 15:12:25.432: Got key port of type n
task-0: ** (process:8300): DEBUG: 15:12:25.432: Got key message of type s
task-0: ** (process:8300): DEBUG: 15:12:25.432: Got key server of type s
task-0: ** (process:8300): DEBUG: 15:12:25.432: Got key old-ssl of type b
task-0: ** (process:8300): DEBUG: 15:12:25.432: Got key 
fallback-conference-server of type s
task-0: ** (process:8347): DEBUG: 15:12:25.550: Service name: OtherService
task-0: ** (process:8347): DEBUG: 

[Touch-packages] [Bug 1869117] Re: python-pip install fails in Ubuntu 20.04 unmet dependencies (Focal)

2020-04-01 Thread Matthias Klose
yes, please use python3-pip


** Changed in: python-pip (Ubuntu)
   Status: Confirmed => Won't Fix

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

Title:
  python-pip install fails in Ubuntu 20.04 unmet dependencies (Focal)

Status in python-pip package in Ubuntu:
  Won't Fix
Status in python2.7 package in Ubuntu:
  Invalid

Bug description:
  apt-get install python-pip fails in Ubuntu 20.04:

  The following packages have unmet dependencies:
   python-pip : Depends: python-pip-whl (= 18.1-5ubuntu1) but 20.0.2-2 is to be 
installed
Recommends: python-all-dev (>= 2.6) but it is not going to be 
installed
Recommends: python-wheel but it is not going to be installed
  E: Unable to correct problems, you have held broken packages.

  The python-pip package needs to be updated to accept newer versions of
  python-pip-whl.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-pip/+bug/1869117/+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] [NEW] xz-utils ftbfs in focal

2020-04-01 Thread Matthias Klose
Public bug reported:

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

** Affects: xz-utils (Ubuntu)
 Importance: High
 Status: Confirmed

** Affects: xz-utils (Debian)
 Importance: Unknown
 Status: Unknown


** Tags: ftbfs rls-ff-incoming

** Changed in: xz-utils (Ubuntu)
   Status: New => Confirmed

** Changed in: xz-utils (Ubuntu)
   Importance: Undecided => High

** Tags added: ftbfs rls-ff-incoming

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

** Also affects: xz-utils (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945961
   Importance: Unknown
   Status: Unknown

-- 
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:
  Confirmed
Status in xz-utils package in Debian:
  Unknown

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


[Touch-packages] [Bug 1869814] Re: ubuntu-docs build failure - possible solution

2020-04-01 Thread Matthias Klose
** Tags added: ftbfs

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

Title:
  ubuntu-docs build failure - possible solution

Status in itstool package in Ubuntu:
  Invalid
Status in libxml2 package in Ubuntu:
  In Progress
Status in ubuntu-docs package in Ubuntu:
  Fix Committed

Bug description:
  ubuntu-docs failed to build during the second Focal Fossa test
  rebuild:

  https://launchpad.net/ubuntu/+archive/test-
  rebuild-20200327-focal/+build/18982738

  It was itstool which failed to generate the localized zh_CN pages. If
  dropping zh_CN from ubuntu-help/Makefile.am, ubuntu-docs builds. But
  excluding the Chinese pages is apparently not an acceptable solution.

  The itstool package in focal {build-,}depends on python3. I built
  itstool in a PPA with python2 instead, and in that PPA ubuntu-docs
  built fine without modifications:

  https://launchpad.net/~gunnarhj/+archive/ubuntu/ubuntu-docs/+packages

  So the root cause seems to lie neither in ubuntu-docs nor itstool. I
  would suspect that python3-libxml2 is buggy, but since itstool was
  built against python2 in eoan, it's hard to tell if it's a regression.

  Would building itstool against python2 be an acceptable workaround in
  focal?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/itstool/+bug/1869814/+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 1870081] [NEW] session-migration ftbfs in focal

2020-04-01 Thread Matthias Klose
Public bug reported:

seen in the second focal test rebuild
https://launchpad.net/ubuntu/+archive/test-rebuild-20200327-focal/+build/18976653/+files/buildlog_ubuntu-focal-amd64.session-migration_0.3.4_BUILDING.txt.gz

nosetests3
.F...
==
FAIL: ensure assert when there is a typo in the script path or doesn't exist
--
Traceback (most recent call last):
  File "/<>/obj-x86_64-linux-gnu/tests/debhelper_tests.py", line 
89, in test_build_with_missing_script
self.assertTrue("dh_migrations: install -p -m755 script1.sh 
debian/vanilla/usr/share/session-migration/scripts returned exit code 1" in 
stdout)
AssertionError: False is not true

--
Ran 9 tests in 9.399s

FAILED (failures=1)
make[5]: *** [CMakeFiles/check.dir

** Affects: session-migration (Ubuntu)
 Importance: High
 Status: Confirmed


** Tags: ftbfs rls-ff-incoming

** Changed in: session-migration (Ubuntu)
   Status: New => Confirmed

** Changed in: session-migration (Ubuntu)
   Importance: Undecided => High

** Tags added: ftbfs rls-ff-incoming

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

Title:
  session-migration ftbfs in focal

Status in session-migration package in Ubuntu:
  Confirmed

Bug description:
  seen in the second focal test rebuild
  
https://launchpad.net/ubuntu/+archive/test-rebuild-20200327-focal/+build/18976653/+files/buildlog_ubuntu-focal-amd64.session-migration_0.3.4_BUILDING.txt.gz

  nosetests3
  .F...
  ==
  FAIL: ensure assert when there is a typo in the script path or doesn't exist
  --
  Traceback (most recent call last):
File "/<>/obj-x86_64-linux-gnu/tests/debhelper_tests.py", line 
89, in test_build_with_missing_script
  self.assertTrue("dh_migrations: install -p -m755 script1.sh 
debian/vanilla/usr/share/session-migration/scripts returned exit code 1" in 
stdout)
  AssertionError: False is not true

  --
  Ran 9 tests in 9.399s

  FAILED (failures=1)
  make[5]: *** [CMakeFiles/check.dir

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/session-migration/+bug/1870081/+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 1870073] [NEW] python-debian ftbfs in focal

2020-04-01 Thread Matthias Klose
Public bug reported:

seen in the second focal test rebuild
https://launchpad.net/ubuntu/+archive/test-rebuild-20200327-focal/+build/18963677/+files/buildlog_ubuntu-focal-amd64.python-glanceclient_1%3A2.17.0-0ubuntu2_BUILDING.txt.gz

During handling of the above exception, another exception occurred:


Traceback (most recent call last):

  File "/usr/lib/python3/dist-packages/requests/adapters.py", line 439, in 
send
resp = conn.urlopen(

  File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line 
719, in urlopen
retries = retries.increment(

  File "/usr/lib/python3/dist-packages/urllib3/util/retry.py", line 436, in 
increment
raise MaxRetryError(_pool, url, error or ResponseError(cause))

urllib3.exceptions.MaxRetryError:
HTTPSConnectionPool(host='0.0.0.0', port=45175): Max retries exceeded
with url: /v2/images/image123 (Caused by SSLError(SSLError("bad
handshake: SysCallError(-1, 'Unexpected EOF')")))


During handling of the above exception, another exception occurred:


Traceback (most recent call last):

  File "/<>/glanceclient/common/http.py", line 269, in _request
resp = self.session.request(method,

  File "/usr/lib/python3/dist-packages/requests/sessions.py", line 533, in 
request
resp = self.send(prep, **send_kwargs)

  File "/usr/lib/python3/dist-packages/requests/sessions.py", line 646, in 
send
r = adapter.send(request, **kwargs)

  File "/usr/lib/python3/dist-packages/requests/adapters.py", line 514, in 
send
raise SSLError(e, request=request)

requests.exceptions.SSLError: HTTPSConnectionPool(host='0.0.0.0',
port=45175): Max retries exceeded with url: /v2/images/image123 (Caused
by SSLError(SSLError("bad handshake: SysCallError(-1, 'Unexpected
EOF')")))


During handling of the above exception, another exception occurred:


Traceback (most recent call last):

  File "/<>/glanceclient/tests/unit/test_ssl.py", line 124, in 
test_v2_requests_cert_verification
gc.images.get('image123')

  File "/<>/glanceclient/v2/images.py", line 198, in get
return self._get(image_id)

  File "/<>/glanceclient/common/utils.py", line 598, in inner
return RequestIdProxy(wrapped(*args, **kwargs))

  File "/<>/glanceclient/v2/images.py", line 191, in _get
resp, body = self.http_client.get(url, headers=header)

  File "/<>/glanceclient/common/http.py", line 315, in get
return self._request('GET', url, **kwargs)

  File "/<>/glanceclient/common/http.py", line 282, in _request
raise exc.CommunicationError(message=message)

glanceclient.exc.CommunicationError: Error finding address for
https://0.0.0.0:45175/v2/images/image123:
HTTPSConnectionPool(host='0.0.0.0', port=45175): Max retries exceeded
with url: /v2/images/image123 (Caused by SSLError(SSLError("bad
handshake: SysCallError(-1, 'Unexpected EOF')")))


During handling of the above exception, another exception occurred:


Traceback (most recent call last):

  File "/usr/lib/python3/dist-packages/mock/mock.py", line 1330, in patched
return func(*args, **keywargs)

  File "/<>/glanceclient/tests/unit/test_ssl.py", line 128, in 
test_v2_requests_cert_verification
self.fail('No certificate failure message is received')

  File "/usr/lib/python3/dist-packages/unittest2/case.py", line 690, in fail
raise self.failureException(msg)

AssertionError: No certificate failure message is received


==
Totals
==
Ran: 635 tests in 1.7474 sec.
 - Passed: 623
 - Skipped: 7
 - Expected Fail: 0
 - Unexpected Success: 0
 - Failed: 5
Sum of execute time for each test: 5.8393 sec.

==
Worker Balance
==
 - Worker 0 (159 tests) => 0:00:01.182108
 - Worker 1 (159 tests) => 0:00:01.607279
 - Worker 2 (159 tests) => 0:00:01.570729
 - Worker 3 (158 tests) => 0:00:01.650056
make[1]: *** [debian/rules:24: override_dh_auto_test] Error 1
make[1]: Leaving directory '/<>'

** Affects: python-debian (Ubuntu)
 Importance: High
 Status: Confirmed


** Tags: ftbfs rls-ff-incoming

** Changed in: python-debian (Ubuntu)
   Status: New => Confirmed

** Changed in: python-debian (Ubuntu)
   Importance: Undecided => High

** Tags added: ftbfs rls-ff-incoming

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

Title:
  python-debian ftbfs in focal

Status in python-debian package in Ubuntu:
  Confirmed

Bug description:
  seen in the second focal test rebuild
  
https://launchpad.net/ubuntu/+archive/test-rebuild-20200327-focal/+build/18963677/+files/buildlog_ubuntu-focal-amd64.python-glanceclient_1%3A2.17.0-0ubuntu2_BUILDING.txt.gz

  During handling of the above exception, another exception occurred:

  
  Traceback (most recent call last):

File "/usr/lib/python3/dist-packages/requests/adapters.py", line 439, 
in send
  resp 

[Touch-packages] [Bug 1870055] [NEW] capnproto ftbfs in focal on s390x

2020-04-01 Thread Matthias Klose
Public bug reported:

second focal test rebuild
https://launchpadlibrarian.net/471777379/buildlog_ubuntu-focal-s390x.capnproto_0.7.0-5build1_BUILDING.txt.gz

make  check-TESTS
make[4]: Entering directory '/<>'
make[5]: Entering directory '/<>'
FAIL: src/capnp/compiler/capnp-test.sh
PASS: capnp-evolution-test
PASS: capnp-test

   Capn Proto 0.7.0: ./test-suite.log


# TOTAL: 3
# PASS:  2
# SKIP:  0
# XFAIL: 0
# FAIL:  1
# XPASS: 0
# ERROR: 0

.. contents:: :depth: 2

FAIL: src/capnp/compiler/capnp-test.sh
==

/<>/.libs/capnp convert: The input is not in "json" format. It 
looks like it is in "json" format. Try that instead.
Try '/<>/.libs/capnp convert --help' for more information.
cmp: EOF on - which is empty
FAILED: annotated json to binary
FAIL src/capnp/compiler/capnp-test.sh (exit status: 1)


Testsuite summary for Capn Proto 0.7.0

# TOTAL: 3
# PASS:  2
# SKIP:  0
# XFAIL: 0
# FAIL:  1
# XPASS: 0
# ERROR: 0

See ./test-suite.log
Please report to capnpr...@googlegroups.com


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


** Tags: ftbfs rls-ff-incoming

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

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

** Tags added: ftbfs rls-ff-incoming

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

Title:
  capnproto ftbfs in focal on s390x

Status in capnproto package in Ubuntu:
  Confirmed

Bug description:
  second focal test rebuild
  
https://launchpadlibrarian.net/471777379/buildlog_ubuntu-focal-s390x.capnproto_0.7.0-5build1_BUILDING.txt.gz

  make  check-TESTS
  make[4]: Entering directory '/<>'
  make[5]: Entering directory '/<>'
  FAIL: src/capnp/compiler/capnp-test.sh
  PASS: capnp-evolution-test
  PASS: capnp-test
  
 Capn Proto 0.7.0: ./test-suite.log
  

  # TOTAL: 3
  # PASS:  2
  # SKIP:  0
  # XFAIL: 0
  # FAIL:  1
  # XPASS: 0
  # ERROR: 0

  .. contents:: :depth: 2

  FAIL: src/capnp/compiler/capnp-test.sh
  ==

  /<>/.libs/capnp convert: The input is not in "json" format. It 
looks like it is in "json" format. Try that instead.
  Try '/<>/.libs/capnp convert --help' for more information.
  cmp: EOF on - which is empty
  FAILED: annotated json to binary
  FAIL src/capnp/compiler/capnp-test.sh (exit status: 1)

  
  Testsuite summary for Capn Proto 0.7.0
  
  # TOTAL: 3
  # PASS:  2
  # SKIP:  0
  # XFAIL: 0
  # FAIL:  1
  # XPASS: 0
  # ERROR: 0
  
  See ./test-suite.log
  Please report to capnpr...@googlegroups.com
  

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/capnproto/+bug/1870055/+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 1870059] [NEW] gtk+3.0 ftbfs in focal (all archs)

2020-04-01 Thread Matthias Klose
Public bug reported:

https://launchpadlibrarian.net/47194/buildlog_ubuntu-focal-
amd64.gtk+3.0_3.24.14-1ubuntu1_BUILDING.txt.gz

seen in the second focal test rebuild

make[2]: *** [Makefile:749: check-recursive] Error 1
make[2]: Target 'check' not remade because of errors.
make[2]: Leaving directory 
'/build/gtk+3.0-ucFLVC/gtk+3.0-3.24.14/debian/build/deb'
dh_auto_test: error: cd debian/build/deb && make -j4 check VERBOSE=1 -k check 
-j1 returned exit code 2
make[1]: *** [debian/rules:205: override_dh_auto_test] Error 25
make[1]: Leaving directory '/build/gtk+3.0-ucFLVC/gtk+3.0-3.24.14'
make: *** [debian/rules:135: binary] Error 2
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2

** Affects: gtk+3.0 (Ubuntu)
 Importance: High
 Status: Confirmed


** Tags: ftbfs rls-ff-incoming

** Changed in: gtk+3.0 (Ubuntu)
   Status: New => Confirmed

** Changed in: gtk+3.0 (Ubuntu)
   Importance: Undecided => High

** Tags added: ftbfs rls-ff-incoming

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

Title:
  gtk+3.0 ftbfs in focal (all archs)

Status in gtk+3.0 package in Ubuntu:
  Confirmed

Bug description:
  https://launchpadlibrarian.net/47194/buildlog_ubuntu-focal-
  amd64.gtk+3.0_3.24.14-1ubuntu1_BUILDING.txt.gz

  seen in the second focal test rebuild

  make[2]: *** [Makefile:749: check-recursive] Error 1
  make[2]: Target 'check' not remade because of errors.
  make[2]: Leaving directory 
'/build/gtk+3.0-ucFLVC/gtk+3.0-3.24.14/debian/build/deb'
  dh_auto_test: error: cd debian/build/deb && make -j4 check VERBOSE=1 -k check 
-j1 returned exit code 2
  make[1]: *** [debian/rules:205: override_dh_auto_test] Error 25
  make[1]: Leaving directory '/build/gtk+3.0-ucFLVC/gtk+3.0-3.24.14'
  make: *** [debian/rules:135: binary] Error 2
  dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 
2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1870059/+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 1870050] [NEW] busybox ftbfs in focal

2020-04-01 Thread Matthias Klose
Public bug reported:

https://launchpadlibrarian.net/471776317/buildlog_ubuntu-focal-
amd64.busybox_1%3A1.30.1-4ubuntu5_BUILDING.txt.gz

busybox ftbfs in focal

==
/usr/bin/ld: coreutils/lib.a(mktemp.o): in function `mktemp_main':
./debian/build/deb/coreutils/mktemp.c:102: warning: the use of `mktemp' is 
dangerous, better use `mkstemp' or `mkdtemp'
/usr/bin/ld: util-linux/lib.a(rdate.o): in function `rdate_main':
./debian/build/deb/util-linux/rdate.c:99: undefined reference to `stime'
/usr/bin/ld: coreutils/lib.a(date.o): in function `date_main':
./debian/build/deb/coreutils/date.c:306: undefined reference to `stime'
collect2: error: ld returned 1 exit status
Note: if build needs additional libraries, put them in CONFIG_EXTRA_LDLIBS.

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


** Tags: ftbfs rls-ff-incoming

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

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

** Tags added: ftbfs rls-ff-incoming

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

Title:
  busybox ftbfs in focal

Status in busybox package in Ubuntu:
  Confirmed

Bug description:
  https://launchpadlibrarian.net/471776317/buildlog_ubuntu-focal-
  amd64.busybox_1%3A1.30.1-4ubuntu5_BUILDING.txt.gz

  busybox ftbfs in focal

  ==
  /usr/bin/ld: coreutils/lib.a(mktemp.o): in function `mktemp_main':
  ./debian/build/deb/coreutils/mktemp.c:102: warning: the use of `mktemp' is 
dangerous, better use `mkstemp' or `mkdtemp'
  /usr/bin/ld: util-linux/lib.a(rdate.o): in function `rdate_main':
  ./debian/build/deb/util-linux/rdate.c:99: undefined reference to `stime'
  /usr/bin/ld: coreutils/lib.a(date.o): in function `date_main':
  ./debian/build/deb/coreutils/date.c:306: undefined reference to `stime'
  collect2: error: ld returned 1 exit status
  Note: if build needs additional libraries, put them in CONFIG_EXTRA_LDLIBS.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/1870050/+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 1869447] Re: python-is-python3 & python-is-python2 do not Provides: python

2020-03-28 Thread Matthias Klose
third party packages should *not* depend on python, but directly on
python2 (deprecated) or python3 (preferred)


** Changed in: python-defaults (Ubuntu)
   Status: New => Invalid

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

Title:
  python-is-python3 & python-is-python2 do not Provides: python

Status in python-defaults package in Ubuntu:
  Invalid
Status in python3-defaults package in Ubuntu:
  Invalid
Status in what-is-python package in Ubuntu:
  New

Bug description:
  This is a bug in Focal prerelease.

  Third-party packages like Steam currently appear to Depend: upon
  python, but nothing Provides: python, only Conflicts: python.

  I believe that python-is-... should Provide: python so that packages
  that expect to use /usr/bin/python aren't surprised.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-defaults/+bug/1869447/+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 1869117] Re: python-pip install fails in Ubuntu 20.04 unmet dependencies (Focal)

2020-03-26 Thread Matthias Klose
the python2.7 has nothing to do with python-pip

** Changed in: python2.7 (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  python-pip install fails in Ubuntu 20.04 unmet dependencies (Focal)

Status in python2.7 package in Ubuntu:
  Invalid

Bug description:
  apt-get install python-pip fails in Ubuntu 20.04:

  The following packages have unmet dependencies:
   python-pip : Depends: python-pip-whl (= 18.1-5ubuntu1) but 20.0.2-2 is to be 
installed
Recommends: python-all-dev (>= 2.6) but it is not going to be 
installed
Recommends: python-wheel but it is not going to be installed
  E: Unable to correct problems, you have held broken packages.

  The python-pip package needs to be updated to accept newer versions of
  python-pip-whl.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1869117/+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 1864992] Re: depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/lib/modules/5.4.0-14-generic/modules.builtin.bin'

2020-03-24 Thread Matthias Klose
reopening for focal. still seen in almost every autopkg test
(2020-03-24)

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

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

Title:
  depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could
  not open builtin file
  '/lib/modules/5.4.0-14-generic/modules.builtin.bin'

Status in kmod package in Ubuntu:
  New
Status in kmod source package in Bionic:
  Fix Committed
Status in kmod source package in Disco:
  Won't Fix
Status in kmod source package in Eoan:
  Fix Committed
Status in kmod source package in Focal:
  New

Bug description:
  [Impact]

  * There is no impact to the end user but spurious error messages (tons
  of them) causing the perception that something really bad happened:

  Example of one of those tons of messages:

  depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could
  not open builtin file
  '/lib/modules/5.4.0-14-generic/modules.builtin.bin'

  [Test Case]

  * sudo rm /lib/modules/$(uname -r)/modules.builtin.bin

  * sudo depmod -a -F /boot/System.map-$(uname -r)

  This will cause the spurious error messages because depmod -a -F won't
  have the "modules.builtin.bin" file created. This is a simulation of
  what the linux-modules postinst package does and an example of why the
  messages happen.

  [Regression Potential]

  * We are reverting a debian patch so we will be closer to upstream
  code base.

  * the change is about 2 different priority changes on verbosity, so
  biggest problem would be extra (or fewer) stdout/stderr messages (for
  scripts relying on them, for example).

  * I have tested with kernels 4.15, 5.0 and 5.3 and all of them seemed
  to work fine.

  [Other Info]

  * Original Description:

  During a Focal install from the ISO image several errors like:

  depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could
  not open builtin file
  '/lib/modules/5.4.0-14-generic/modules.builtin.bin'

  are logged in curtin's install logs. The installed system boots and
  works fine, but the error is clearly something we want to get rid of.

  At first glance this seems related to:

  https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1863261

  but the version of initramfs-tools in both the installer and installed
  system (checked with `chroot /target dpkg -l initramfs-tools` during
  the installation) is 0.136ubuntu1, which should contain Rafael's fix
  for that bug. I wonder if the update-initramfs diversion has a role
  here.

  I verified this happens at least on amd64 and arm64. I'm attaching the full 
install logs for a amd64 installation.
  ---
  ProblemType: Bug
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.4.0-14-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
  CasperVersion: 1.439
  DistroRelease: Ubuntu 20.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  LiveMediaBuild: Ubuntu-Server 20.04 LTS "Focal Fossa" - Alpha amd64 (20200225)
  Lsusb:
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Lsusb-t:
   /:  Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   /:  Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 
480M
  MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
  ProcFB: 0 qxldrmfb
  ProcKernelCmdLine: initrd=/casper/initrd quiet  --- maybe-ubiquity
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-14-generic N/A
   linux-backports-modules-5.4.0-14-generic  N/A
   linux-firmware1.186
  RfKill: Error: [Errno 2] No such file or directory: 

[Touch-packages] [Bug 1863414] Re: Have many "/usr/lib/python3.8/subprocess.py:838: RuntimeWarning: line buffering (buffering=1) isn't supported in binary mode, the default buffer size will be used" o

2020-03-23 Thread Matthias Klose
stuck in -proposed

** Changed in: python3.8 (Ubuntu Focal)
   Status: Won't Fix => In Progress

** Changed in: python3-defaults (Ubuntu Focal)
   Status: Confirmed => In Progress

** Changed in: python3.8 (Ubuntu Focal)
   Status: In Progress => 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/1863414

Title:
  Have many "/usr/lib/python3.8/subprocess.py:838: RuntimeWarning: line
  buffering (buffering=1) isn't supported in binary mode, the default
  buffer size will be used" on simple APT usage

Status in python3-defaults package in Ubuntu:
  In Progress
Status in python3.8 package in Ubuntu:
  Invalid
Status in python3-defaults source package in Focal:
  In Progress
Status in python3.8 source package in Focal:
  Invalid
Status in python3-defaults package in Debian:
  Unknown

Bug description:
  Steps to reproduce:
  1. Have Ubuntu 20.04 LTS installed
  2. Run regular APT task such as `sudo apt dist-upgrade`
  3. Wait it to finish

  Expected results:
  * APT runs without any warnings and/or errors

  Actual results:
  * APT runs with many python-related warnings like

  >```
  >/usr/lib/python3.8/subprocess.py:838: RuntimeWarning: line buffering 
(buffering=1) isn't supported >in binary mode, the default buffer size will be 
used
  >  self.stdin = io.open(p2cwrite, 'wb', bufsize)
  >
  >```

  Full output below:

  ```
  $ sudo apt dist-upgrade 
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Calculating upgrade... Done
  The following packages were automatically installed and are no longer 
required:
ruby-json ruby-pg ruby-sequel ruby-sequel-pg
  Use 'sudo apt autoremove' to remove them.
  The following NEW packages will be installed:
kdevelop55-libs libxentoolcore1 ubuntu-mate-wallpapers-focal
  The following packages will be upgraded:
atril atril-common debootstrap dmeventd dmsetup dnsmasq-base engrampa 
engrampa-common fwupd fwupd-signed gir1.2-atrildocument-1.5.0
gir1.2-atrilview-1.5.0 gir1.2-freedesktop gir1.2-glib-2.0 gir1.2-pluma-1.0 
initramfs-tools initramfs-tools-bin initramfs-tools-core
iproute2 isc-dhcp-client isc-dhcp-common jekyll k3b k3b-data k3b-i18n 
kdevelop kdevelop-data libatrildocument-dev libatrildocument3
libatrilview-dev libatrilview3 libdevmapper-event1.02.1 libdevmapper1.02.1 
libdistro-info-perl libfwupd2 libfwupdplugin1
libgirepository-1.0-1 libk3b7 libk3b7-extracodecs liblvm2cmd2.03 
libmate-sensors-applet-plugin-dev libmate-sensors-applet-plugin0
libmate-slab0 libmate-window-settings-dev libmate-window-settings1 
libmatedict-dev libmatedict6 libmysqlclient21 libmysqlclient21:i386
libvirt-clients libvirt-daemon libvirt-daemon-driver-qemu 
libvirt-daemon-driver-storage-rbd libvirt-daemon-system
libvirt-daemon-system-systemd libvirt0 libxenstore3.0 
libxmlgraphics-commons-java lvm2 mate-applets mate-applets-common mate-common
mate-control-center mate-control-center-common mate-core 
mate-desktop-environment mate-desktop-environment-core
mate-desktop-environment-extra mate-desktop-environment-extras 
mate-dock-applet mate-media mate-media-common mate-netbook
mate-netbook-common mate-notification-daemon 
mate-notification-daemon-common mate-power-manager mate-power-manager-common
mate-screensaver mate-screensaver-common mate-sensors-applet 
mate-sensors-applet-common mate-sensors-applet-nvidia mate-system-monitor
mate-system-monitor-common mate-terminal mate-terminal-common 
mate-user-share mate-user-share-common mate-utils mate-utils-common maxima
maxima-doc maxima-share mozo nano pluma pluma-common pluma-dev pluma-doc 
plymouth-theme-ubuntu-mate-logo plymouth-theme-ubuntu-mate-text
python-caja-common python3-caja python3-distro-info python3-macaroonbakery 
qemu-block-extra qemu-kvm qemu-system-common qemu-system-data
qemu-system-gui qemu-system-x86 qemu-utils ubuntu-mate-artwork 
ubuntu-mate-default-settings ubuntu-mate-icon-themes
ubuntu-mate-lightdm-theme ubuntu-mate-live-settings ubuntu-mate-themes 
ubuntu-mate-wallpapers ubuntu-mate-wallpapers-artful
ubuntu-mate-wallpapers-bionic ubuntu-mate-wallpapers-common 
ubuntu-mate-wallpapers-complete ubuntu-mate-wallpapers-cosmic
ubuntu-mate-wallpapers-disco ubuntu-mate-wallpapers-eoan 
ubuntu-mate-wallpapers-legacy ubuntu-mate-wallpapers-photos
ubuntu-mate-wallpapers-utopic ubuntu-mate-wallpapers-vivid 
ubuntu-mate-wallpapers-wily ubuntu-mate-wallpapers-xenial
ubuntu-mate-wallpapers-yakkety ubuntu-mate-wallpapers-zesty umbrello
  136 upgraded, 3 newly installed, 0 to remove and 0 not upgraded.
  Need to get 215 MB of archives.
  After this operation, 12,8 MB of additional disk space will be used.
  Do you want to continue? [Y/n] 
  Get:1 http://archive.ubuntu.com/ubuntu focal/universe amd64 mate-common all 
1.24.0-1ubuntu1 [17,0 kB]
  

[Touch-packages] [Bug 1742941] Re: zlib: improve crc32 performance on P8

2020-02-25 Thread Matthias Klose
** Changed in: zlib (Ubuntu)
   Status: Triaged => In Progress

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

Title:
  zlib: improve  crc32 performance on P8

Status in The Ubuntu-power-systems project:
  Triaged
Status in zlib package in Ubuntu:
  In Progress

Bug description:
  Calculate the checksum of data that is 16 byte aligned and a multiple
  of  16 bytes.

  The first step is to reduce it to 1024 bits. We do this in 8 parallel
   chunks in order to mask the latency of the vpmsum instructions. If we
   have more than 32 kB of data to checksum we repeat this step multiple
   times, passing in the previous 1024 bits.

   The next step is to reduce the 1024 bits to 64 bits. This step adds
   32 bits of 0s to the end - this matches what a CRC does. We just
   calculate constants that land the data in this 32 bits.

   We then use fixed point Barrett reduction to compute a mod n over GF(2)
   for n = CRC using POWER8 instructions. We use x = 32.

   http://en.wikipedia.org/wiki/Barrett_reduction

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


  1   2   3   4   5   6   7   8   9   10   >