Re: alien, xfree86, and other bugs
> And this is not only you who are used to doing this. In my opinion, this
> is WRONG. All bug fixes MUST also go to stable (and this is especailly
> true for frozen). What this means to me is that I have look through all
> those debian-installer messages and make a note what packages in unstable
> have to be used instead of "stable" counterparts. But this is not the
> worst thing. With "alien" which is actually in binary-all/ this is fine.
> But what can I do with packages which are already use libc6?
> I don't want to install libc6 because I want to have worry-free
> possibility to use commercial developmental suits like Motif and XRT PDS.
> (They use libc5 and I think won't have the upgrade for libc6 available for
> a long time, and if they will - it costs money!)
If only bug fixes could be allowed in, this would be a good idea.
Unfortunately, this isn't a practical possibility. Every time a new
package is uploaded to fix a bug, there is the possibility of introducing
new bugs either in the "patch" code, other code that got added for some
reason, or even in the packaging itself.
At some point, there just isn't time for the testing group to validate
new package before release. At least twice I've had to remove "simple
major bug fixes" because they were compiled against libc6 from hamm.
Brian
( bcwhite@verisim.com )
-------------------------------------------------------------------------------
The squeaky wheel doesn't always get the grease. Sometimes it gets replaced.
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
debian-user-request@lists.debian.org .
Trouble? e-mail to templin@bucknell.edu .
Reply to: