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

Re: How can g++ (stable) be incompatible with a fresh stable install?

On Thu, Jan 8, 2015 at 11:30 AM, Sven Joachim <svenjoac@gmx.de> wrote:
> On 2015-01-08 15:14 +0100, Kynn Jones wrote:
>> 4. The key dependecy chain behind the error shown above goes like this:
>>
>>     g++ depends on
>>     g++-4.7 (>= 4.7.2-1~) depends on
>>     libstdc++6-4.7-dev (= 4.7.2-5) depends on
>>     libc6-dev (>= 2.13-5) depends on
>>     libc6 (= 2.13-38+deb7u4)
>
> That's the problem, apparently your mirror only has libc6-dev
> 2.13-38+deb7u4, but the current version in wheezy is 2.13-38+deb7u6.
> Since the installation CD already contains libc6 2.13-38+deb7u6 but not
> libc6-dev, there is a version skew.

Thanks!

> What does "apt-cache policy libc6 libc6-dev" print?

    libc6:
      Installed: 2.13-38+deb7u6
      Candidate: 2.13-38+deb7u6
      Version table:
         2.19-13 0
            750 http://debian.csail.mit.edu/debian/ testing/main amd64 Packages
            750 http://ftp.us.debian.org/debian/ testing/main amd64 Packages
             50 http://debian.csail.mit.edu/debian/ unstable/main amd64 Packages
             50 http://ftp.us.debian.org/debian/ unstable/main amd64 Packages
     *** 2.13-38+deb7u6 0
            995 http://debian.csail.mit.edu/debian/ stable/main amd64 Packages
            995 http://ftp.us.debian.org/debian/ stable/main amd64 Packages
            100 /var/lib/dpkg/status
         2.13-38+deb7u4 0
           1000 http://security.debian.org/ stable/updates/main amd64 Packages
    libc6-dev:
      Installed: (none)
      Candidate: 2.13-38+deb7u4
      Version table:
         2.19-13 0
            750 http://debian.csail.mit.edu/debian/ testing/main amd64 Packages
            750 http://ftp.us.debian.org/debian/ testing/main amd64 Packages
             50 http://debian.csail.mit.edu/debian/ unstable/main amd64 Packages
             50 http://ftp.us.debian.org/debian/ unstable/main amd64 Packages
         2.13-38+deb7u6 0
            995 http://debian.csail.mit.edu/debian/ stable/main amd64 Packages
            995 http://ftp.us.debian.org/debian/ stable/main amd64 Packages
         2.13-38+deb7u4 0
           1000 http://security.debian.org/ stable/updates/main amd64 Packages

Thanks for the `apt-cache policy` clue.

The version skew seems to be between the installation CD and
http://security.debian.org/stable.  (BTW, the skew does not apply to
the other packages in the dependency chain, AFAICT.  Details below.)

I can think of the following possible solutions:

  1. change the priorities so that stable trumps security;
  2. (somehow) force the installation of libc6-dev v. 2.13-38+deb7u6;
  3. (somehow) downgrade my libc6 to the version in
security.debian.org stable (2.13-38+deb7u4);

The last one seems the most prudent one, but I have no idea of how to
go about it, since practically everything depends on libc6...

The good news is that now the situation is far less bewildering (thank
you for that), and what remains is purely technical (even if I'm
clueless on how to go about it).





FWIW, here's the output of `apt-cache policy` for all the packages in
the dependency chain I posted originally.  As you can see,
security.debian.org comes into the picture only for libc6 and
libc6-dev.

libc6:
  Installed: 2.13-38+deb7u6
  Candidate: 2.13-38+deb7u6
  Version table:
     2.19-13 0
        750 http://debian.csail.mit.edu/debian/ testing/main amd64 Packages
        750 http://ftp.us.debian.org/debian/ testing/main amd64 Packages
         50 http://debian.csail.mit.edu/debian/ unstable/main amd64 Packages
         50 http://ftp.us.debian.org/debian/ unstable/main amd64 Packages
 *** 2.13-38+deb7u6 0
        995 http://debian.csail.mit.edu/debian/ stable/main amd64 Packages
        995 http://ftp.us.debian.org/debian/ stable/main amd64 Packages
        100 /var/lib/dpkg/status
     2.13-38+deb7u4 0
       1000 http://security.debian.org/ stable/updates/main amd64 Packages
libc6-dev:
  Installed: (none)
  Candidate: 2.13-38+deb7u4
  Version table:
     2.19-13 0
        750 http://debian.csail.mit.edu/debian/ testing/main amd64 Packages
        750 http://ftp.us.debian.org/debian/ testing/main amd64 Packages
         50 http://debian.csail.mit.edu/debian/ unstable/main amd64 Packages
         50 http://ftp.us.debian.org/debian/ unstable/main amd64 Packages
     2.13-38+deb7u6 0
        995 http://debian.csail.mit.edu/debian/ stable/main amd64 Packages
        995 http://ftp.us.debian.org/debian/ stable/main amd64 Packages
     2.13-38+deb7u4 0
       1000 http://security.debian.org/ stable/updates/main amd64 Packages
libstdc++6-4.7-dev:
  Installed: (none)
  Candidate: 4.7.2-5
  Version table:
     4.7.4-3 0
         50 http://debian.csail.mit.edu/debian/ unstable/main amd64 Packages
         50 http://ftp.us.debian.org/debian/ unstable/main amd64 Packages
     4.7.2-5 0
        995 http://debian.csail.mit.edu/debian/ stable/main amd64 Packages
        995 http://ftp.us.debian.org/debian/ stable/main amd64 Packages
g++-4.7:
  Installed: (none)
  Candidate: 4.7.2-5
  Version table:
     4.7.4-3 0
         50 http://debian.csail.mit.edu/debian/ unstable/main amd64 Packages
         50 http://ftp.us.debian.org/debian/ unstable/main amd64 Packages
     4.7.2-5 0
        995 http://debian.csail.mit.edu/debian/ stable/main amd64 Packages
        995 http://ftp.us.debian.org/debian/ stable/main amd64 Packages
g++:
  Installed: (none)
  Candidate: 4:4.7.2-1
  Version table:
     4:4.9.2-1 0
         50 http://debian.csail.mit.edu/debian/ unstable/main amd64 Packages
         50 http://ftp.us.debian.org/debian/ unstable/main amd64 Packages
     4:4.9.1-5 0
        750 http://debian.csail.mit.edu/debian/ testing/main amd64 Packages
        750 http://ftp.us.debian.org/debian/ testing/main amd64 Packages
     4:4.7.2-1 0
        995 http://debian.csail.mit.edu/debian/ stable/main amd64 Packages
        995 http://ftp.us.debian.org/debian/ stable/main amd64 Packages
Reply to: