Faulty dependencies.

Bug #621694 reported by Erik Johansson-Evegård
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
gcc-4.1 (Ubuntu)
Fix Released
Medium
Unassigned
Maverick
Fix Released
Medium
Unassigned
icu (Ubuntu)
Invalid
Undecided
Unassigned
Maverick
Invalid
Undecided
Unassigned
libgenome (Ubuntu)
Fix Released
Undecided
Unassigned
Maverick
Fix Released
Undecided
Unassigned
torch3 (Debian)
Fix Released
Unknown
torch3 (Ubuntu)
Fix Released
Undecided
Unassigned
Maverick
Fix Released
Undecided
Unassigned
wine1.0 (Ubuntu)
Fix Released
Undecided
Unassigned
Maverick
Fix Released
Undecided
Unassigned

Bug Description

Binary package hint: gcc-4.1

g++-4.1 package is an old version and depends on older version than what is installed in system.

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: g++-4.1 4.1.2-27ubuntu1
ProcVersionSignature: Ubuntu 2.6.35-15.21-generic 2.6.35.1
Uname: Linux 2.6.35-15-generic x86_64
NonfreeKernelModules: wl nvidia
Architecture: amd64
Date: Sat Aug 21 12:27:37 2010
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.utf8
 SHELL=/bin/bash
SourcePackage: gcc-4.1

Revision history for this message
Erik Johansson-Evegård (erik-johansson-evegard) wrote :
Revision history for this message
Erik Johansson-Evegård (erik-johansson-evegard) wrote :

Sure wish someone could fix this soon. Should not take more than some minutes.

Revision history for this message
Matthias Klose (doko) wrote :

> Sure wish someone could fix this soon. Should not take more than some minutes.

yes, setting to invalid. gcc-4.1 is not part of 10.10. please remove the package.

Changed in gcc-4.1 (Ubuntu):
status: New → Invalid
Revision history for this message
Colin Watson (cjwatson) wrote : Re: [Bug 621694] Re: Faulty dependencies.

On Mon, Sep 06, 2010 at 08:05:31PM -0000, Matthias Klose wrote:
> yes, setting to invalid. gcc-4.1 is not part of 10.10. please remove the
> package.

If you want it removed from the archive, reopen this bug and subscribe
ubuntu-archive. However, there are still some dependencies on the C++
portions (though I know those are no longer built):

-- maverick/main build deps on g++-4.1:
icu
-- maverick/universe amd64 deps on libstdc++6-4.1-dev:
libgenome-1.3-0-dev
libtorch3-dev
-- maverick/universe i386 deps on libstdc++6-4.1-dev:
libgenome-1.3-0-dev
libtorch3-dev
-- maverick/universe armel deps on libstdc++6-4.1-dev:
libgenome-1.3-0-dev
libtorch3-dev
-- maverick/universe powerpc deps on libstdc++6-4.1-dev:
libgenome-1.3-0-dev
libtorch3-dev
-- maverick/multiverse build deps on libstdc++6-4.1-dev:
wine1.0

Revision history for this message
Matthias Klose (doko) wrote :

the wine1.0 build-deps
  libstdc++6-4.2-dev | libstdc++6-4.1-dev | libstdc++-dev
should just be dropped. g++ is included in build-essential

Changed in wine1.0 (Ubuntu):
status: New → Triaged
milestone: none → ubuntu-10.10
Revision history for this message
Matthias Klose (doko) wrote :

libtorch3-dev depends on:

Depends: libtorch3c2 (= 3.1-2), c++abi2-dev | libstdc++6-4.1-dev

again, which is bogus. should be dropped.

Revision history for this message
Matthias Klose (doko) wrote :

libgenome needs a rebuild to drop the dependency

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package libgenome - 1.3.1-3build1

---------------
libgenome (1.3.1-3build1) maverick; urgency=low

  * Rebuild to drop dependency on libstdc++6-4.1-dev. LP: #621694.
 -- Matthias Klose <email address hidden> Tue, 07 Sep 2010 12:38:55 +0200

Changed in libgenome (Ubuntu):
status: New → Fix Released
Matthias Klose (doko)
Changed in torch3 (Ubuntu):
milestone: none → ubuntu-10.10
status: New → Triaged
Changed in libgenome (Ubuntu):
milestone: none → ubuntu-10.10
Changed in gcc-4.1 (Ubuntu):
milestone: none → ubuntu-10.10
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package wine1.0 - 1.0.1-0ubuntu14

---------------
wine1.0 (1.0.1-0ubuntu14) maverick; urgency=low

  * Build with newer libstdc++6 (LP: #621694)
    - use lib32stdc++6 on amd64
 -- Scott Ritchie <email address hidden> Tue, 07 Sep 2010 18:07:30 -0700

Changed in wine1.0 (Ubuntu Maverick):
status: Triaged → Fix Released
Revision history for this message
Matthias Klose (doko) wrote :

torch3 3.1-2.1 now in maverick

Changed in torch3 (Ubuntu Maverick):
status: Triaged → Fix Released
Revision history for this message
Matthias Klose (doko) wrote :

now gcc-4.1 binaries can be removed

Changed in gcc-4.1 (Ubuntu Maverick):
importance: Undecided → Medium
status: Invalid → Triaged
Revision history for this message
Colin Watson (cjwatson) wrote :

icu still build-depends on g++-4.1. Opening a new task for that.

Revision history for this message
Colin Watson (cjwatson) wrote :

Oh, sorry, false positive. The build-dependencies read:

Build-Depends: cdbs, debhelper (>= 5), quilt, doxygen, gcc-multilib [amd64 kfreebsd-amd64 ppc64] | gcc-4.1 (<< 4.1.2) [amd64 kfreebsd-amd64 ppc64], g++-multilib [amd64 kfreebsd-amd64 ppc64] | g++-4.1 (<< 4.1.2) [amd64 kfreebsd-amd64 ppc64], libc6-dev-i386 [amd64], libc0.1-dev-i386 [kfreebsd-amd64], libc6-dev-powerpc [ppc64]

... which is kind of weird, but is satisfiable without g++-4.1.

Changed in icu (Ubuntu Maverick):
status: New → Invalid
Revision history for this message
Colin Watson (cjwatson) wrote :

I've removed the g++-4.1 and libstdc++6-4.1-dev binary packages, which were the ones originally reported as broken here.

Matthias: The gcc-4.1 source package as a whole can only be removed if I also remove gpc-4.1. Unfortunately, the default gpc package still depends on gpc-4.1. Nobody is depending or build-depending on gpc, but all the same this seems like a risky removal. Perhaps you could file a separate bug for this and subscribe ubuntu-archive if you want to pursue this?

Changed in gcc-4.1 (Ubuntu Maverick):
status: Triaged → Fix Released
Changed in torch3 (Debian):
status: Unknown → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.