[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#870258: marked as done (GCC 7 related library transitions)

Your message dated Wed, 10 Oct 2018 21:15:07 +0200
with message-id <371570c0-67e9-dfb6-c247-5e2cc891647e@debian.org>
and subject line Re: Bug#870258: GCC 7 related library transitions
has caused the Debian Bug report #870258,
regarding GCC 7 related library transitions
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
870258: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=870258
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: release.debian.org
Severity: normal
User: release.debian.org@packages.debian.org
Usertags: transition

Bumping the GCC default to GCC 7 triggers some GCC library transitions.

 - libgfortran3 -> libgfortran4
 - libgphobos68 -> libgphobos71
 - libgo7 -> libgo9
 - libasan3 -> libasan4

Afaics only the first mentioned library has reverse dependencies in the archive,
the other ones don't have any.

I'm planning to bump the GCC default next week if possible, together with the
GCC 7.2 release candidate.

--- End Message ---
--- Begin Message --- 
On 03/03/2018 10:59, Emilio Pozuelo Monfort wrote:
> On 31/07/17 13:42, Matthias Klose wrote:
>> Package: release.debian.org
>> Severity: normal
>> User: release.debian.org@packages.debian.org
>> Usertags: transition
>>
>> Bumping the GCC default to GCC 7 triggers some GCC library transitions.
>>
>>  - libgfortran3 -> libgfortran4
>>  - libgphobos68 -> libgphobos71
>>  - libgo7 -> libgo9
>>  - libasan3 -> libasan4
>>
>> Afaics only the first mentioned library has reverse dependencies in the archive,
>> the other ones don't have any.
> 
> Turns out libgo had several rdeps, just not on amd64. I scheduled several
> binNMUs for those, and things are looking better. This is the current situation:
> 
> $ dak rm -Rn -s testing gcc-6 gcc-6-cross gcc-6-cross-ports
> 
> | Checking reverse dependencies...
> | # Broken Depends:
> | acmetool: acmetool [mips mips64el mipsel s390x]
> | gcc-defaults: gcj-aarch64-linux-gnu [amd64 i386]
> |               gcj-arm-linux-gnueabi [amd64 arm64 i386]
> |               gcj-arm-linux-gnueabihf [amd64 arm64 i386]
> |               gcj-jdk
> |               gcj-jre
> |               gcj-jre-headless
> |               gcj-mips-linux-gnu [amd64 i386]
> |               gcj-mips64el-linux-gnuabi64 [amd64 i386]
> |               gcj-mipsel-linux-gnu [amd64 i386]
> |               gcj-powerpc64le-linux-gnu [amd64 i386]
> |               gcj-s390x-linux-gnu [amd64 i386]
> |               libgcj-bc
> | gcc-defaults-ports: gcj-alpha-linux-gnu [amd64 i386]
> |                     gcj-hppa-linux-gnu [amd64 i386]
> |                     gcj-m68k-linux-gnu [amd64 i386]
> |                     gcj-mips64-linux-gnuabi64 [amd64 i386]
> |                     gcj-powerpc-linux-gnu [amd64 i386 ppc64el]
> |                     gcj-powerpc-linux-gnuspe [amd64 i386]
> |                     gcj-powerpc64-linux-gnu [amd64 i386]
> |                     gcj-sh4-linux-gnu [amd64 i386]
> |                     gcj-sparc64-linux-gnu [amd64 i386]
> | golang-github-xordataexchange-crypt: golang-github-xordataexchange-crypt [mips mips64el mipsel s390x]
> | kamailio: kamailio-java-modules
> | pdftk: pdftk
> | starpu-contrib/contrib: starpu-contrib-examples [amd64]
> 
> Of the rdeps, kamailio and pdftk (and gcc-defaults* obviously) are due to GCJ.
> acmetool and golang-github-xordataexchange-crypt are due to libgo* but are fixed
> in sid, but are having some trouble migrating to testing, but nothing too important.
> starpu-contrib builds with GCC 6 and ends up depending on libgfortran3. It needs to
> be updated to GCC 7.
> 
> So the most important thing here is GCJ. Is it gone for good? If so we need to file
> bugs for the rdeps so they move to openjdk or default-jdk or whatever.
> 
> As for the build-deps:
> 
> | 
> | # Broken Build-Depends:
> | aqemu: g++-6
> |        gcc-6
> | blackbox: g++-6
> |           gcc-6
> | boost1.62: g++-6
> | boost1.63: g++-6
> | caffe-contrib/contrib: g++-6
> |                        gcc-6
> | dewalls: libstdc++-6-dev
> | ecj: gcj-6-jdk
> | eztrace-contrib/contrib: g++-6
> |                          gcc-6
> | firefox-esr: g++-6
> |              gcc-6
> | gmp-ecm: gcc-6
> | grub2: gcc-6
> |        gcc-6-multilib
> | kodi: g++-6
> |       gcc-6
> | libpam-script: libgfortran3
> | shiboken: g++-6
> | squid3: g++-6
> |         gcc-6
> | starpu-contrib/contrib: g++-6
> |                         gcc-6
> |                         gcc-6-plugin-dev
> |                         gfortran-6
> | thunderbird: g++-6
> |              gcc-6
> 
> As you can see it's a bunch of packages building with gcc-6 & g++-6. They probably
> need new upstream versions that support GCC 7. The only exception is libpam-script
> build-depending on libgfortran3 for no apparent good reason. I filed #889876 for that.
> 
> As for the GCJ removal, I crafted this list of binary packages. This is running
> for sid, so it catches more stuff.
> 
> $ dak rm -Rn -b gcj-jdk gcj-jre gcj-jre-headless libgcj17 libgcj-bc
> 
> | Will remove the following packages from unstable:
> | 
> |    gcj-jdk | 4:6.4.0-3d1 | amd64, arm64, armel, armhf, hurd-i386, i386, kfreebsd-amd64, kfreebsd-i386, mips, mips64el, mipsel, powerpc, ppc64el, s390x
> |    gcj-jre | 4:6.4.0-3d1 | amd64, arm64, armel, armhf, hurd-i386, i386, kfreebsd-amd64, kfreebsd-i386, mips, mips64el, mipsel, powerpc, ppc64el, s390x
> | gcj-jre-headless | 4:6.4.0-3d1 | amd64, arm64, armel, armhf, hurd-i386, i386, kfreebsd-amd64, kfreebsd-i386, mips, mips64el, mipsel, powerpc, ppc64el, s390x
> |  libgcj-bc |  6.4.0-3d1 | amd64, arm64, armel, armhf, hurd-i386, i386, kfreebsd-amd64, kfreebsd-i386, mips, mips64el, mipsel, powerpc, ppc64el, s390x
> |   libgcj17 |    6.4.0-7 | kfreebsd-amd64
> |   libgcj17 |   6.4.0-11 | hurd-i386, kfreebsd-i386
> |   libgcj17 |   6.4.0-12 | amd64, arm64, armel, armhf, i386, mips, mips64el, mipsel, powerpc, ppc64el, s390x
> | 
> | Maintainer: Debian GCC Maintainers <debian-gcc@lists.debian.org>
> | 
> | ------------------- Reason -------------------
> | 
> | ----------------------------------------------
> | 
> | Checking reverse dependencies...
> | # Broken Depends:
> | ant: ant-gcj
> |      ant-optional-gcj
> | ecj: ecj-gcj
> |      ecj1
> |      libecj-java-gcj
> | gcc-5: gcj-5-jdk
> |        libgcj16-dev
> | gcc-6: gcj-6-jdk
> |        gcj-6-jre-headless
> |        gcj-6-jre-lib
> |        libgcj17-awt
> |        libgcj17-dbg
> |        libgcj17-dev
> | java-common: default-jdk [hurd-i386]
> |              default-jdk-headless [hurd-i386]
> |              default-jre [hurd-i386]
> |              default-jre-headless [hurd-i386]
> |              gcj-native-helper
> | javatools: java-propose-classpath
> | kamailio: kamailio-java-modules [amd64 arm64 armel armhf i386 kfreebsd-amd64 kfreebsd-i386 mips mips64el mipsel powerpc ppc64el s390x]
> | libxerces2-java: libxerces2-java-gcj
> | pdftk: pdftk
> | 
> | # Broken Build-Depends:
> | automake-1.15: gcj-jdk
> | ecj: libgcj-bc
> | gcc-defaults: gcj-jdk
> | gcc-doc-defaults/contrib: gcj-jdk
> | jaminid: gcj-jdk
> | kamailio: gcj-jdk
> | libidn: gcj-jdk
> | pdftk: gcj-jdk
> | 
> | Dependency problem found.
> 
> Some things here need to be updated to use openjdk or default-jdk, e.g. kamailio, pdftk, libidn...
> Other things likely need to be removed since GCJ is no more, e.g. ant-gcj, ecj-gcj...

All the library transitions are done. As for build-rdeps, there's just chromium
remaining in testing (plus firefox-esr, which is fixed in sid and pending
testing migration). I'll keep an eye on chromium and remove gcc-6 if it gets
fixed. So let's close this.

Cheers,
Emilio

--- End Message ---
Reply to: