+++ mateusz.ka...@gmail.com [2014-10-27 10:30 +0100]: > Package: g++-4.9-arm-linux-gnueabihf > Severity: grave > Justification: renders package unusable > > Dear Maintainer, > > I cannot install gnueabihf for armhf toolchain on amd64 platform. > > g++-4.9-arm-linux-gnueabihf : Depends: gcc-4.9-base (= 4.9.1-18) but > 4.9.1-19 is to be installed > Depends: cpp-4.9-arm-linux-gnueabihf (>= > 4.9.1-18) but it is not going to be installed > Depends: gcc-4.9-arm-linux-gnueabihf (= > 4.9.1-18) but it is not going to be installed > Depends: libstdc++-4.9-dev:armhf (= > 4.9.1-18) but it is not going to be installed > E: Unable to correct problems, you have held broken packages. > > I believe this is because current gcc-4.9-base in Debian is 4.9.1-19 which > is in conflict with 4.9.1-18, and there is no existing package of > gcc-4.9-base-4.9.1-18 for amd64 architecture in any repository. Solution > would probably to update packages.
Yes, these packages need to be rebuilt against gcc 4.9.1-19. However the gcc maintainer has disabled the behaviour that lets this package build in -19. See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766924 That can be patched around for now, but last night there was also a new glibc building. Both have to be in sync on an arch before a rebuild can occur. That should be in a better state by now, so I hope to upload new toolchains today. The close assocation with gcc means that (lib) dependencies have to be exact version matches. Actually the gcc-4.9-base dependency (just copyright/docs) version requirements could be relaxed, but as the others stuff (built from the same version) have to be in sync anyway this makes no practical difference. Wookey -- Principal hats: Linaro, Emdebian, Wookware, Balloonboard, ARM http://wookware.org/ -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
