Bug#51816: marked as done (conflicting packages)
Debian Bug Tracking System
with message-id <2000022400...@cibalia.gkvk.hr>
and subject line This can't be fixed, sorry.
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Darren Benham
(administrator, Debian Bugs database)
--------------------------------------
Received: (at submit) by bugs.debian.org; 2 Dec 1999 21:07:09 +0000
Received: (qmail 26320 invoked from network); 2 Dec 1999 21:07:07 -0000
Received: from maestro.hl.lu.se (kl...@194.47.62.5)
by master.debian.org with SMTP; 2 Dec 1999 21:07:07 -0000
Received: from localhost (klasa@localhost)
by maestro.hl.lu.se (8.9.3/8.9.3) with ESMTP id WAA18092
for <sub...@bugs.debian.org>; Thu, 2 Dec 1999 22:04:51 +0100
Date: Thu, 2 Dec 1999 22:04:51 +0100 (CET)
From: Klas Lindberg <kl...@maestro.hl.lu.se>
To: sub...@bugs.debian.org
Subject: conflicting packages
Message-ID: <Pine.LNX.4.10.991202...@maestro.hl.lu.se>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Package: libstc++2.9-dev
Version: 2.91.60-5
Tjo!
libstdc++2.9-dev_2.91.60-5 depends on libc6-dev
libstdc++2.9_2.91.60-5 depends on libc6
Accordning to www.debian.org/Packages/stable/... neither specify any
must-have version number for libc6[-dev]
libc6-dev_2.1.2-10 is installed
libc6_2.1.2-10 is installed
libstdc++2.9-dev_2.91.60-5 conflicts with libc6-dev_2.1.2-10
libstdc++2.9_2.91.60-5 does NOT conflict with libc6_2.1.2-10
Thus, I can install libstdc++2.9. In turn, I can run binaries compiled
against libstdc++2.9, but I cannot compile the sources myself... This
sucks.
Ofcourse, I can always upgrade g++ and libraries to unstable versions and
think nothing more of it. The practical problem for me is that I have
C++ sources which won't compile against the unstable version of libstdc++.
Please fix the dependencies or tell me something to do that solves the
problem and won't give me a broken system. I won't resort to dpkg
--force-depends for this kind of thing.
harebra / klasa
---------------------------------------
Received: (at 51816-close) by bugs.debian.org; 23 Feb 2000 23:41:34 +0000
Received: (qmail 14888 invoked from network); 23 Feb 2000 23:41:32 -0000
Received: from cibalia.gkvk.hr (ma...@161.53.211.3)
by master.debian.org with SMTP; 23 Feb 2000 23:41:32 -0000
Received: from joy by cibalia.gkvk.hr with local (Exim 2.05 #1 (Debian))
id 12NlX2-0002ZM-00; Thu, 24 Feb 2000 00:49:24 +0100
Date: Thu, 24 Feb 2000 00:49:24 +0100
From: Josip Rodin <j...@cibalia.gkvk.hr>
To: 51816...@bugs.debian.org
Subject: This can't be fixed, sorry.
Message-ID: <2000022400...@cibalia.gkvk.hr>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
User-Agent: Mutt/1.0pre2i
Hi,
Klas Lindberg <kl...@maestro.hl.lu.se> wrote:
> Thus, I can install libstdc++2.9. In turn, I can run binaries compiled
> against libstdc++2.9, but I cannot compile the sources myself... This
> sucks.
> Ofcourse, I can always upgrade g++ and libraries to unstable versions and
> think nothing more of it. The practical problem for me is that I have
> C++ sources which won't compile against the unstable version of libstdc++.
>
> Please fix the dependencies or tell me something to do that solves the
> problem and won't give me a broken system. I won't resort to dpkg
> --force-depends for this kind of thing.
There is no way to get libstdc++2.9-dev in Debian again, the conflicts are
there for a purpose. You should adjust your old sources to compile with the
latest g++/libstdc++2.10 (the -fpermissive option for g++ could be useful).
I'm closing this bug now, since no one else bothered to do it before.
--
enJoy -*/\*- don't even try to pronounce my first name
--
To UNSUBSCRIBE, email to debian-bugs-c...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org