Re: Bug#34672: Installing xlib6g removed xlib6.
I hereby request adjudication of this dispute. Santiago refuses to
acknowledge my perfectly valid way of handling a package reorganization...a
change that was made 2 years ago.
Santiago, send me no further mail on this issue. It is in the technical
committee's hands now.
As proof of the falsity of his assertions, I exhibit the following:
ii xlib6 3.3.6-14 shared libraries required by libc5 X clients
ii xlib6-altdev 3.3.6-14 include files and libraries for libc5 X client development
ii xlib6g 4.0.1-5 pseudopackage providing X libraries
ii xlib6g-dev 4.0.1-5 pseudopackage providing X library development files
ii xlibs 4.0.1-5 X Window System client libraries
ii xlibs-dev 4.0.1-5 X Window System client library development files
Alternatively, you can form the simultaneous installation status of xlib6
and xlib6g on any potato machine, since further reorganization in the wake
of XFree86 4.0 has taken place.
On Thu, Nov 16, 2000 at 11:31:16AM +0100, Santiago Vila wrote:
> reopen 34672
> On Tue, 14 Nov 2000, Debian Bug Tracking System wrote:
> > Upgrades from hamm or earlier to potato are not supported by the project.
> I have never read anything like that in policy.
It doesn't have to be in policy.
> > In any case, the point is moot because one can install the a more recent
> > xlib6 package in conjuction with xlib6g/xlibs and not have any problems.
> If you say that then it seems that you didn't understand this bug after all.
> This bug is about upgrades, not about installing a new system.
You are so dense it makes me gasp for breath.
There is nothing in policy that says I cannot have a package declare a
versioned Replaces and versioned Conflicts against the same package, and
that is in fact what I did, and appropriately so because of reorganization
of the package contents. Without the Conflict, people could be left
without some important files altogether.
YOU are the one who exhibits no understanding.
IF YOU UPGRADE TO CONTEMPORANEOUS VERSIONS OF XLIB6 AND XLIB6G AT THE SAME
TIME, THERE IS NO PROBLEM AND XLIB6 IS NOT REMOVED.
There is absolutely nothing in any policy anywhere that says that running
dpkg -i one-debian-package.deb
is not allowed to cause another to be removed. If there were, we wouldn't
have a "Conflict" package relationship.
> > If you reopen this bug I will appeal to the technical committee. Go away.
> Please, do it (or better, fix the bug).
What needs to be fixed is your broken brain.
> We have always supported upgrades from any previous release.
If you insist on sticking with an obsolete, conflicted-with version of a
package despite the availability of a working upgrade path, that is wholly
your problem. Not mine, and not Debian's.
G. Branden Robinson | Psychology is really biology.
Debian GNU/Linux | Biology is really chemistry.
firstname.lastname@example.org | Chemistry is really physics.
http://deadbeast.net/~branden/ | Physics is really math.