I confirm this upload fixed it. Thanks!
Change:
+gcc-10 (10-20200416-0ubuntu1) focal; urgency=medium
+
+ * GCC snapshot, taken from the trunk (20200416, 44b326839d8).
+ * libgcc-sN: Don't add the libgcc-N-dev breaks for backports.
+
+ -- Matthias Klose Thu, 16 Apr 2020 17:36:04 +0200
New
now fixed
** Changed in: gcc-10 (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1872854
Title:
GCC-10 library conflict on s390x
To manage notifications
Yes, it is a pain sometimes to track down those apt errors since apt
does not automatically resolve those dependency chains and clearly print
out which breaks/replace/provides/depends it chokes on.
However there is a testcase Dockerfile and the same file run on amd64
does not yield the issue.
> I see what's going wrong. preparing an update for the PPA
Ok, good!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1872854
Title:
GCC-10 library conflict on s390x
To manage notifications about
I see what's going wrong. preparing an update for the PPA
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1872854
Title:
GCC-10 library conflict on s390x
To manage notifications about this bug go
I can't see yet, why this is only seen on s390x. the libgcc1 built from gcc-10
depends on
Depends: gcc-10-base (= 10-20200405-0ubuntu1~18.04), libgcc-s1 (>=
10-20200405-0ubuntu1~18.04), libc6
(>= 2.14)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Seems this libcc1-0 binary package was built from the gcc-9 source
package and it worked fine. With the introduction of gcc-10 into the PPA
there was a new provider for this binary package and thus it stopped
working.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Switching to the PPA ppa:ubuntu-toolchain-r/ppa fixes this for Bionic,
since there is no gcc-10 there and this issue does not occur. That repo
does however not contain GCC-9 for Xenial, and most of Travis-CI jobs
still run on Xenial (their default distro at the moment), so
recommending everybody
Sorry for sloppy bug report. Here are exact steps to reproduce on a
Ubuntu 18.04 host (arch amd64) running s390x in a Docker container. The
bug is not repeatable on amd64 since the s390x packages available on
Bionic is slightly different.
# Install s390x emulators
sudo apt install
Not enabled by default, but whitelisted https://github.com/travis-ci
/apt-source-safelist/blob/master/ubuntu.json#L557 and one of the easiest
ways to run CI on multiple gcc compiler versions, and architectures
since fairly recently (https://docs.travis-ci.com/user/multi-cpu-
architectures/).
--
What do you mean, "one of the default ones on Travis-CI"? Travis-CI
should not be enabling ANY ppas by default as part of an Ubuntu base.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1872854
Title:
11 matches
Mail list logo
