Re: Bug#2655: ld.so includes header file, clashes with old libc
Let's try this again with the correct email address.
> Could you use Replaces, please, not Conflicts ? Using Conflicts will
> force people to remove their existing libc before upgrading ld.so,
> which I think is not what you intend ...
> ...
> > > Even if it should then it should use `Replaces: libc' to ensure that
> > > the old libc's files are overwritten properly.
> >
> > Replaces isn't applicable here.
>
> I think it is. If you want to discuss it further please mail me
> privately and we can sort it out.
Perhaps you should redescribe exactly what Replaces does. I thought
it was only to be used when one package totally takes the place of
another. What else is it for? Turning on --force-overwrite for
selected packages?
> > Ian, in the future, please ask on debian-devel if you
> > aren't sure about something before filing a misdirected bug report.
>
> Surely I should just do as anyone else, and if the thing is definitely
> a bug (which I was convinced it was) file the report against whatever
> package seems most likely to me ?
I prefer to ask for clarification first whenever I'm not sure about
something rather than burdening someone else with straightening out
the bug list.
> After all, the package
> maintainer(s) in question can always reassign the bug to another
> package if they wish.
Yes, but you are much more familiar than me with how the bug system
works. I always have go digging through old, saved email to remember
how to do anything more than close a bug. Are there any plans to make
the WWW interface more useful? It sure would be handy if bugs could
be closed, reassigned, replied to, etc. from it.
David
--
David Engel Optical Data Systems, Inc.
david@ods.com 1101 E. Arapaho Road
(214) 234-6400 Richardson, TX 75081
Reply to: