Public bug reported:
seen in trantor 1.5.12+ds-1ubuntu3:
Build-Depends: cmake, debhelper-compat (=13), dh-cmake, dh-cmake-compat
(=1)
replacing (=1) with (= 1) lets the parsing succeed.
$ sudo apt build-dep .
Note, using directory '.' to get the build dependencies
Reading package lists... Done
that doesn't show up in component-mismatches yet. something in main
still depending on it
** Changed in: isc-dhcp (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
same test failures with pygobject 3.48.1-1
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pygobject in Ubuntu.
https://bugs.launchpad.net/bugs/2057836
Title:
gst-python1.0 fails to build: test failures
Status in
Debian added a b-d on pygobject >= 3.48.1, which we don't have
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pygobject in Ubuntu.
https://bugs.launchpad.net/bugs/2057836
Title:
gst-python1.0 fails to build: test failures
** Changed in: gdb (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gdb in Ubuntu.
https://bugs.launchpad.net/bugs/1982336
Title:
[24.04 FEAT] GDB: Support for new IBM Z
Public bug reported:
[--] 8 tests from TestScrollView
[ RUN ] TestScrollView.TestQueueDrawScrollDownNoScrollbars
[ OK ] TestScrollView.TestQueueDrawScrollDownNoScrollbars (434 ms)
[ RUN ] TestScrollView.TestQueueDrawScrollUpNoScrollbars
[ OK ]
** Changed in: nux (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to nux in Ubuntu.
https://bugs.launchpad.net/bugs/2054350
Title:
nux ftbfs from source, failing test
Status in nux
Public bug reported:
seen in noble, all architectures:
[--] 1 test from TestLoggingWriter
[ RUN ] TestLoggingWriter.TestWriteMessage
gtest-nuxcore-logger.cpp:171: Failure
Value of: result
Expected: is equal to 0x5d40f0 pointing to "ERROR 2010-09-10 06:34:45
test.module
disco is EOL
** Changed in: nux (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to nux in Ubuntu.
https://bugs.launchpad.net/bugs/1815094
Title:
[FTBFS] cast between incompatible
builds
** Changed in: nux (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to nux in Ubuntu.
https://bugs.launchpad.net/bugs/1570894
Title:
s390x build failure
Status in nux
** Changed in: python3-defaults (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python3-defaults in
Ubuntu.
https://bugs.launchpad.net/bugs/2051997
Title:
bdebstrap fails to build
** Changed in: python3-defaults (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python3-defaults in
Ubuntu.
https://bugs.launchpad.net/bugs/2051990
Title:
python3-defaults 3.12 causes
better, but still not complete:
1186s autopkgtest [04:54:38]: test root-unittest: [---
1186s Interpreter: python3
1186s
1186s rm -rf ./build
1186s rm -rf ./staging
1186s rm -rf ./tests/testarea ./tests/unit/tmp
1186s rm -rf ./tmp
1186s rm -rf ./snap-build
1186s rm -rf ./parts
NMUed
** Changed in: bdebstrap (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python3-defaults in
Ubuntu.
https://bugs.launchpad.net/bugs/2051997
Title:
bdebstrap fails to build
NMUed in Debian
** Changed in: aubio (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python3-defaults in
Ubuntu.
https://bugs.launchpad.net/bugs/2051990
Title:
python3-defaults
** Bug watch added: Debian Bug tracker #1061735
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061735
** Also affects: bdebstrap (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061735
Importance: Unknown
Status: Unknown
--
You received this bug notification
** Changed in: ufw (Ubuntu)
Status: In Progress => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ufw in Ubuntu.
https://bugs.launchpad.net/bugs/2051540
Title:
ufw ftbfs with Python 3.12 as default
Public bug reported:
[...]
Running ./test_pep484.py with python3
s
--
Ran 0 tests in 0.000s
NO TESTS RAN (skipped=1)
make[2]: *** [Makefile:9: check] Error 5
make[2]: Leaving directory '/<>/test'
make[1]: *** [debian/rules:16:
Public bug reported:
==
ERROR: test_ufwcommand_parse
(tests.unit.test_parser.ParserTestCase.test_ufwcommand_parse)
Test UFWCommand.parse()
--
Traceback (most
Public bug reported:
debian/rules override_dh_auto_test
make[1]: Entering directory '/<>'
tests/run-linters --errors-only
Skipping mypy tests, mypy is not installed
Running pylint...
* Module apport-retrace
bin/apport-retrace:577:44: E0601: Using variable 'crashid' before
The python3 symlink is not meant to be handled by alternatives.
** Changed in: python3-defaults (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python3-defaults in
Ubuntu.
Public bug reported:
autopkg tests ignored for migration of python3-defaults adding 3.12:
These are the autopkg tests for packages, which we'll ignore for the
initial migration of python3-defaults adding 3.12.
** Affects: python3-defaults (Ubuntu)
Importance: Undecided
Status: New
not a binutils issue, please reinstall, as the error message says
** Changed in: binutils (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to binutils in Ubuntu.
this is not a binutils issue, please reinstall as the error message
suggests
** Changed in: binutils (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to binutils in Ubuntu.
closing as won't fix for 20.04 LTS
** Changed in: binutils (Ubuntu)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to binutils in Ubuntu.
https://bugs.launchpad.net/bugs/1977958
Title:
please remove the package, and re-install it
** Changed in: binutils (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to binutils in Ubuntu.
https://bugs.launchpad.net/bugs/1824249
Title:
this is not a binutils issue. try to re-donwload your updates
** Changed in: binutils (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to binutils in Ubuntu.
we currently don't build cross compilers on riscv64, because it slows
down the toolchain updates. That might change, if we have native
hardware for our buildds.
** Changed in: binutils (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of
please provide a test case
** Changed in: binutils (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to binutils in Ubuntu.
https://bugs.launchpad.net/bugs/2039149
Title:
readelf riscv
Public bug reported:
TBD
** Affects: gnutls28 (Ubuntu)
Importance: Undecided
Status: New
** Affects: libarchive (Ubuntu)
Importance: Undecided
Status: New
** Affects: libselinux (Ubuntu)
Importance: Undecided
Status: New
** Affects: libxml2 (Ubuntu)
** Changed in: setuptools (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dh-python in Ubuntu.
https://bugs.launchpad.net/bugs/2037205
Title:
setuptools: FTBFS in mantic
Status
is that still the case with recent compiler versions?
** Changed in: gcc-11 (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1943818
after retries, all the autopkg tests pass, binutils test results don't
show regressions.
** Tags removed: verification-needed verification-needed-jammy
** Tags added: verification-done verification-done-jammy
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
the package successfully built. All the autopkg tests from the previous
comment have been retried and succeeded.
** Tags removed: verification-needed verification-needed-jammy
** Tags added: verification-done verification-done-jammy
--
You received this bug notification because you are a
** No longer affects: libunwind (Ubuntu Lunar)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libunwind in Ubuntu.
https://bugs.launchpad.net/bugs/2025458
Title:
SRU: rebuild libunwind with GCC 11.4
Status in libunwind
** Bug watch added: Debian Bug tracker #1039962
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039962
** Also affects: libunwind (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039962
Importance: Unknown
Status: Unknown
--
You received this bug notification
Public bug reported:
Reported in LP: #1997161
after updating GCC 11 in 22.04 LTS to 11.3, and now to 11.4, linking
with the static libraries provided by libunwind-dev fails with:
lto1: fatal error: bytecode stream in file '/usr/lib/gcc/x86_64-linux-
The real issue is, that the .a files in the libunwind-dev package are
not stripped, and therefore the LTO information is kept in these files.
This is done by intent in the packaging. Trying to figure why ...
In the meantime the least invasive thing to do is to just rebuild with
GCC 11.4.
** Also
Public bug reported:
The tests sometimes fail with spurious lto-wrapper warnings and let the
build fail. Ignore these warnings, they don't matter for the test
outcome.
Also apply four fixes from the binutils 2.38 branch:
* SRU: LP: #1982105. Update from the binutils 2.38 branch:
- Fix PR
** Changed in: binutils (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to binutils in Ubuntu.
https://bugs.launchpad.net/bugs/1982105
Title:
update binutils to the 2.38 branch in 22.04
** Summary changed:
- update binutils to the 2.38 branch in 20.04 LTS
+ update binutils to the 2.38 branch in 22.04 LTS
** Description changed:
- SRU: update binutils to the 2.38 branch in 20.04 LTS.
+ SRU: update binutils to the 2.38 branch in 22.04 LTS.
The new build will be validated by
tested together with the binutils and GCC SRUs. No regressions.
** Tags removed: verification-needed verification-needed-jammy
** Tags added: verification-done verification-done-jammy
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
all autopkg tests passed now
** Tags removed: verification-needed verification-needed-jammy
** Tags added: verification-done verification-needed-done
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to binutils in Ubuntu.
bash upstream encodes the patchlevel into the version number, while
patches and security fixes in Ubuntu are applied on top of the upstream
version. That's expected behavior.
** Changed in: bash (Ubuntu)
Status: New => Won't Fix
--
You received this bug notification because you are a
** Description changed:
Update gdb to the final 12.1 release in 22.04 LTS. jammy ships with the
gdb 12.1 release candidate, taken from the gdb-12 branch. Changes up to
the final release are:
- - updated gnulib library
- - Fix for PR mi/29002 (Windows only)
- - gdb: fix 'remote show
** Also affects: python3-defaults (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python3-defaults in
Ubuntu.
https://bugs.launchpad.net/bugs/1982108
Title:
SRU: update
** Description changed:
SRU: update binutils to the 2.38 branch in 20.04 LTS.
The new build will be validated by the main component on all
architectures.
+
+ test rebuilds at
+
https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20220728-jammy-jammy.html
+
** Also affects: binutils (Ubuntu Jammy)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to binutils in Ubuntu.
https://bugs.launchpad.net/bugs/1982105
Title:
update binutils to the
** Changed in: binutils (Ubuntu Kinetic)
Status: New => Fix Released
** Changed in: binutils (Ubuntu Jammy)
Status: New => In Progress
** Changed in: binutils (Ubuntu Jammy)
Assignee: Canonical Foundations Team (canonical-foundations) => Matthias
Klose (doko)
Public bug reported:
SRU: update binutils to the 2.38 branch in 20.04 LTS.
The new build will be validated by the main component on all
architectures.
** Affects: binutils (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member
** Changed in: binutils (Ubuntu Kinetic)
Status: New => Fix Released
** Changed in: binutils (Ubuntu Jammy)
Status: New => In Progress
** Changed in: binutils (Ubuntu Jammy)
Assignee: Canonical Foundations Team (canonical-foundations) => Matthias
Klose (doko)
Public bug reported:
as seen in a test rebuild, this package fails to build in the jammy
release pocket (note the log behind the link might go away):
https://launchpadlibrarian.net/604216394/buildlog_ubuntu-jammy-
amd64.icu_70.1-2_BUILDING.txt.gz
[...]
make[4]: Leaving directory
Public bug reported:
as seen in a test rebuild, this package fails to build in the jammy
release pocket (note the log behind the link might go away):
https://launchpadlibrarian.net/604216345/buildlog_ubuntu-
jammy-i386.librsvg_2.52.5+dfsg-3_BUILDING.txt.gz
test
Public bug reported:
as seen in a test rebuild, this package fails to build in the jammy
release pocket (note the log behind the link might go away):
https://launchpadlibrarian.net/604216054/buildlog_ubuntu-jammy-
amd64.accountsservice_22.07.5-2ubuntu1_BUILDING.txt.gz
Ok: 2
Public bug reported:
Update gdb to the final 12.1 release in 22.04 LTS. jammy ships with the
gdb 12.1 release candidate, taken from the gdb-12 branch. Changes up to
the final release are:
- updated gnulib library
- Fix for PR mi/29002 (Windows only)
- gdb: fix 'remote show FOO-packet' aliases
mir builds with the recent gcc-11 in jammy, closing
** Changed in: mir (Ubuntu)
Status: New => Invalid
** Changed in: gcc-11 (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir
** Changed in: python3.10 (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python2.7 in Ubuntu.
https://bugs.launchpad.net/bugs/1452115
Title:
Python interpreter binary is not
$ cupsctl
_debug_logging=1
_remote_admin=0
_remote_any=0
_share_printers=0
_user_cancel_any=0
BrowseLocalProtocols=dnssd
DefaultAuthType=Basic
ErrorPolicy=retry-job
IdleExitTimeout=60
JobPrivateAccess=default
JobPrivateValues=default
MaxLogSize=0
PageLogFormat=
SubscriptionPrivateAccess=default
doko@xe1:~$ driverless
ipp://HP%20LaserJet%20500%20colorMFP%20M570dw%20(6C84AD)._ipp._tcp.local/
doko@xe1:~$ driverless --std-ipp-uris
ipp://NPI6C84AD.local:631/ipp/printer
doko@xe1:~$ lpstat -v
lpstat: No destinations added.
$ ps aux | grep cups-browsed
root 94786 0.0 0.0 172744 11908 ?
python3.10 now in -proposed
** Changed in: python3.10 (Ubuntu)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dh-python in Ubuntu.
https://bugs.launchpad.net/bugs/1960608
Title:
there is no python-is-python2 in jammy anymore
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to six in Ubuntu.
https://bugs.launchpad.net/bugs/1958720
Title:
python3-yaml and python3-six are not co-installable with
we will not change the ISA for the upcoming 22.04 LTS release, but do
the change not before the GCC 12 defaults change planned for 22.10.
** Changed in: binutils (Ubuntu Jammy)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
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,
** 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
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
** 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
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’
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 beca
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:
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.
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
** 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 subs
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:
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.
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
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
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
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
** 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
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.
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:
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
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
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
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.
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,
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
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
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.
** 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
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
--
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
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
** 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
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
*** 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
*** 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
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.
** 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
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.
1 - 100 of 1233 matches
Mail list logo
