Bug#407417: Confusing versioning of libstdc++6[-...]
severity 407417 minor
thanks
Ludovic Brenta writes:
severity 407417 serious
justification: file clashes without Conflicts between packages
thanks
Matthias Klose writes:
Ludovic Brenta writes:
Proposed solution 3:
1) Do not build libstdc++6-{dbg,dev,pic} from gcc-3.4 anymore.
why?
Because we do not build libstdc++6 from gcc-3.4 anymore.
that's not a reason.
2) In gcc-defaults, build libstdc++6-{dbg,dev,pic} that, in etch,
depend on libstdc++6-4.1-{dbg,dev,pic}.
maybe, but not anymore for etch. For a cosmetic change it's not worth
touching three source packages.
Actually, just two (gcc-3.4 and gcc-defaults), but I'm nit-picking.
More importantly, I disagree that it is a cosmetic change:
- the libstdc++6-{dbg,dev,pic} packages in the archive are unusable
because there is no matching libstdc++6; normally this would qualify
as a grave functionality bug.
no, that's plain wrong. It's the nature of an ABI compatible library
that newer versions match earlier versions.
- the libstdc++6-{dbg,dev,pic} contain files clashing with
libstdc++6-4.1-{dbg,dev,pic} but do not Conflict with them; see [1].
I believe that that alone qualifies as a serious policy violation
bug.
wrong again. -dev and -pic packages don't conflict and can be
installed together. libstdc++6-4.1-dbg conflicts with the other -dbg
packages, which is sufficient.
- The same file clashes apply to libstdc++5-3.3-{dbg,dev,pic}, too.
and libstdc++6-4.1-dbg conflicts with libstdc++5-dbg as well. nothing
wrong.
You may argue that the separated debug symbols make only sense in
libstdc++6-4.1-dbg, but again, that's not the only purpose of the -dbg
packages; these provide the library built with--enable-libstdcxx-debug
as well.
g++-3.4 will go away in lenny. I don't see the need to introduce
defaults packages in gcc-defaults.
OK, that's an option too; I suggest we just drop
libstdc++6-{dbg,dev,pic} from gcc-3.4, and modify gcc-4.1 so that its
packages Conflict with the ones from gcc-3.3. I'm willing to do that
myself, in the etch branch.
I object to this change; the only thing you might consider is to
remove the separated debug symbols from libstdc++6-dbg.
Matthias
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#407417: Confusing versioning of libstdc++6[-...]
Actually, the only package that has file conflicts is libstdc++6-dbg; it conflicts with both libstdc++5-3.3-dbg and libstdc++6-4.1-dbg; in addition it will conflict in the future with libstdc++6-4.2-dbg. -- Ludovic Brenta. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#407417: Confusing versioning of libstdc++6[-...]
severity 407417 serious
justification: file clashes without Conflicts between packages
thanks
Matthias Klose writes:
Ludovic Brenta writes:
Proposed solution 3:
1) Do not build libstdc++6-{dbg,dev,pic} from gcc-3.4 anymore.
why?
Because we do not build libstdc++6 from gcc-3.4 anymore.
2) In gcc-defaults, build libstdc++6-{dbg,dev,pic} that, in etch,
depend on libstdc++6-4.1-{dbg,dev,pic}.
maybe, but not anymore for etch. For a cosmetic change it's not worth
touching three source packages.
Actually, just two (gcc-3.4 and gcc-defaults), but I'm nit-picking.
More importantly, I disagree that it is a cosmetic change:
- the libstdc++6-{dbg,dev,pic} packages in the archive are unusable
because there is no matching libstdc++6; normally this would qualify
as a grave functionality bug.
- the libstdc++6-{dbg,dev,pic} contain files clashing with
libstdc++6-4.1-{dbg,dev,pic} but do not Conflict with them; see [1].
I believe that that alone qualifies as a serious policy violation
bug.
- The same file clashes apply to libstdc++5-3.3-{dbg,dev,pic}, too.
[1]
http://packages.debian.org/cgi-bin/search_contents.pl?version=testingarch=amd64case=insensitiveword=libstdc%2B%2B6-dbgsearchmode=filelist
I personally vote against solution 2, since we don't build g++-3.4
anymore and so the libstdc++6-{dbg,dev,pic} from gcc-3.4 are useless
anyway.
huh, we don't build g++-3.4 anymore? thats news.
Sorry, that was a thinko; I meant libstdc++6.
g++-3.4 will go away in lenny. I don't see the need to introduce
defaults packages in gcc-defaults.
OK, that's an option too; I suggest we just drop
libstdc++6-{dbg,dev,pic} from gcc-3.4, and modify gcc-4.1 so that its
packages Conflict with the ones from gcc-3.3. I'm willing to do that
myself, in the etch branch.
--
Ludovic Brenta.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#407417: Confusing versioning of libstdc++6[-...]
Package: gcc-3.4
Version: 3.4.6-5
Severity: important
Stephan Krempel writes:
Dear Debian GCC Maintainers,
first I want to wish you a happy new year and thank you for your work.
This time I am a bit confused about some of the package names and
versions.
libstdc++6 is from source gcc-4.1, but libstdc++6-dbg, -dev, -doc,
-pic are still from gcc-3.4. As a simple user I would expect that
installing libstdc++6[-...] give me everything in matching versions.
Is there any reason why libstdc++6[-...] are not only dependency
packages depending on the respective package with the default
compiler ABI, at the moment libstdc++6-4.1[-...]?
As long as we are in unstable this wouldn't be of high interest, but
in the upcomming stable release some users could become very
confused.
I hope this is not an already discussed issue, couldn't find an old
thread about it.
Indeed, this is confusing.
The gcc-3.4 source package builds libstdc++6-{dbg,dev,pic} which
depend on libstdc++6 (= 3.4.6-5).
The gcc-4.1 source package builds libstdc++6-4.1-{dbg,dev,pic} which
depend on libstdc++6 (= 4.1.1-19).
The current version of libstdc++6 satisfies both dependencies, and
this is proably wrong.
Stephan, the workaround for now is to install
libstdc++6-4.1-{dbg,dev,pic}, and remove libstdc++6-{dbg,dev,pic}.
Proposed solution 1:
1) Do not build libstdc++6-{dbg,dev,pic} from gcc-3.4 anymore.
2) In gcc-4.1, change libstdc++6-4.1-{dbg,dev,pic} to
libstdc++6-{dbg,dev,pic}, with Conflicts and Replaces.
Proposed solution 2:
1) In gcc-4.1, change libstdc++6-4.1-{dbg,dev,pic} to Conflict with
and Replace libstdc++6-{dbg,dev,pic}.
Proposed solution 3:
1) Do not build libstdc++6-{dbg,dev,pic} from gcc-3.4 anymore.
2) In gcc-defaults, build libstdc++6-{dbg,dev,pic} that, in etch,
depend on libstdc++6-4.1-{dbg,dev,pic}.
I personally vote against solution 2, since we don't build g++-3.4
anymore and so the libstdc++6-{dbg,dev,pic} from gcc-3.4 are useless
anyway. I think solution 3 is the best if we want to support multiple
versions of g++.
--
Ludovic Brenta.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#407417: Confusing versioning of libstdc++6[-...]
tags 407417 + wontfix
severity 407417 minor
thanks
Ludovic Brenta writes:
Package: gcc-3.4
Version: 3.4.6-5
Severity: important
Stephan Krempel writes:
Dear Debian GCC Maintainers,
first I want to wish you a happy new year and thank you for your work.
This time I am a bit confused about some of the package names and
versions.
libstdc++6 is from source gcc-4.1, but libstdc++6-dbg, -dev, -doc,
-pic are still from gcc-3.4. As a simple user I would expect that
installing libstdc++6[-...] give me everything in matching versions.
Is there any reason why libstdc++6[-...] are not only dependency
packages depending on the respective package with the default
compiler ABI, at the moment libstdc++6-4.1[-...]?
As long as we are in unstable this wouldn't be of high interest, but
in the upcomming stable release some users could become very
confused.
I hope this is not an already discussed issue, couldn't find an old
thread about it.
Indeed, this is confusing.
The gcc-3.4 source package builds libstdc++6-{dbg,dev,pic} which
depend on libstdc++6 (= 3.4.6-5).
The gcc-4.1 source package builds libstdc++6-4.1-{dbg,dev,pic} which
depend on libstdc++6 (= 4.1.1-19).
The current version of libstdc++6 satisfies both dependencies, and
this is proably wrong.
Stephan, the workaround for now is to install
libstdc++6-4.1-{dbg,dev,pic}, and remove libstdc++6-{dbg,dev,pic}.
note that you always get the correct -dev package installed.
Proposed solution 1:
1) Do not build libstdc++6-{dbg,dev,pic} from gcc-3.4 anymore.
2) In gcc-4.1, change libstdc++6-4.1-{dbg,dev,pic} to
libstdc++6-{dbg,dev,pic}, with Conflicts and Replaces.
Proposed solution 2:
1) In gcc-4.1, change libstdc++6-4.1-{dbg,dev,pic} to Conflict with
and Replace libstdc++6-{dbg,dev,pic}.
no, we do want installations of different g++ versions in parallel.
Proposed solution 3:
1) Do not build libstdc++6-{dbg,dev,pic} from gcc-3.4 anymore.
why?
2) In gcc-defaults, build libstdc++6-{dbg,dev,pic} that, in etch,
depend on libstdc++6-4.1-{dbg,dev,pic}.
maybe, but not anymore for etch. For a cosmetic change it's not worth
touching three source packages.
I personally vote against solution 2, since we don't build g++-3.4
anymore and so the libstdc++6-{dbg,dev,pic} from gcc-3.4 are useless
anyway.
huh, we don't build g++-3.4 anymore? thats news.
g++-3.4 will go away in lenny. I don't see the need to introduce
defaults packages in gcc-defaults.
Matthias
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
