[Bug 360550] Re: Broken dependency in build-essential for AMD64

2009-07-06 Thread Andy Riebs
As the original poster... My god, you guys have a phenomenal ability to discourage useful bug reports. Back when I reported the initial problem, I had been using nothing other than "apt-get update && apt-get upgrade". About 200 years later [note: intentional sarcasm; you may not understand it], you

[Bug 360550] Re: Broken dependency in build-essential for AMD64

2009-07-06 Thread Steve Langasek
Your aptitude output shows that you have versions of the g++, g++-4.3, and libstdc++6-4.3-dev packages installed on your system that did not come from Ubuntu 8.04, and the rest of the packages from the gcc source are not in your apt sources.list. So the only way apt can install build-essential on

[Bug 360550] Re: Broken dependency in build-essential for AMD64

2009-06-29 Thread Scott Ritchie
** Changed in: build-essential (Ubuntu) Status: New => Incomplete -- Broken dependency in build-essential for AMD64 https://bugs.launchpad.net/bugs/360550 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing lis

[Bug 360550] Re: Broken dependency in build-essential for AMD64

2009-06-29 Thread Scott Ritchie
what happens when you do apt-get -f install ? -- Broken dependency in build-essential for AMD64 https://bugs.launchpad.net/bugs/360550 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.

[Bug 360550] Re: Broken dependency in build-essential for AMD64

2009-06-23 Thread gareth
Thanks for the sensible comments Colin, Here is what I originally got when trying to install build-essential: -- sudo aptitude install build-essential Reading package lists... Done Building dependency tree Reading state information... Done Initializi

[Bug 360550] Re: Broken dependency in build-essential for AMD64

2009-06-23 Thread Andy Riebs
Sorry, I no longer have access to that system, and all my personal systems have been upgraded to Jaunty. -- Broken dependency in build-essential for AMD64 https://bugs.launchpad.net/bugs/360550 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubun

[Bug 360550] Re: Broken dependency in build-essential for AMD64

2009-06-23 Thread Colin Watson
Well, let's be a bit analytical about this rather than just repeating assertions at each other! Also, I don't know what "perhaps move to apt- get" means; the original reporter *was* using apt-get. The version of g++ stated in the dependency is definitely available in hardy: g++ | 4:4.2.3-1

[Bug 360550] Re: Broken dependency in build-essential for AMD64

2009-06-23 Thread gareth
perhaps move to apt-get? -- Broken dependency in build-essential for AMD64 https://bugs.launchpad.net/bugs/360550 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubu

[Bug 360550] Re: Broken dependency in build-essential for AMD64

2009-06-23 Thread gareth
Either there are broken dependencies or it is reporting broken dependencies when there aren't any. This is a bug. ** Changed in: build-essential (Ubuntu) Status: Invalid => New -- Broken dependency in build-essential for AMD64 https://bugs.launchpad.net/bugs/360550 You received this bug

[Bug 360550] Re: Broken dependency in build-essential for AMD64

2009-06-23 Thread Matthias Klose
there's nothing broken. all dependencies can be fulfilled. ** Changed in: build-essential (Ubuntu) Status: New => Invalid -- Broken dependency in build-essential for AMD64 https://bugs.launchpad.net/bugs/360550 You received this bug notification because you are a member of Ubuntu Bugs, wh

[Bug 360550] Re: Broken dependency in build-essential for AMD64

2009-06-15 Thread gareth
Thanks for the workaround. Also have this bug in i386 version. -- Broken dependency in build-essential for AMD64 https://bugs.launchpad.net/bugs/360550 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-b