On Thu, Mar 22, 2001 at 10:44:17AM -0600, Manoj Srivastava wrote: > >> There is not technical reason > >> for not building uploads to stable unstable twice in buildd either. > > Marcus> I think this is not true. What is meant by this? It means > Marcus> building the same package twice, with the same version > Marcus> number, but the source (debian/changelog) modified to read > Marcus> "stable" and "unstable" each once. > > Umm. No. If I have two buildd's, one for unstable, and one for > stable. When a package comes in for unstable, it goes to the unstable > buildd, and vice versa. When a package comes in for both, it is sent > to both buildd's, and the packlage built by the unstable buildd goes > into incoming normally, and the other one is hand installed by an > admin into proposed updates or something.
Proposed updates. So. That's a factor I did not include in my calculation. (In Germany one would say "you catched me on the cold foot" ;) > Marcus> Having two different packages with the same version number is > Marcus> evil, too. The package pool won't be able to cope for good > Marcus> reasons. > > The stable package need not go into the package pool. Am I > mistaken in assuming that proposed updates packages are not in the > package pool? If I am mistaken, please scratch this part of my > message. I don't know. If it is, then you can scratch my messages instead. Thanks, Marcus -- `Rhubarb is no Egyptian god.' Debian http://www.debian.org [EMAIL PROTECTED] Marcus Brinkmann GNU http://www.gnu.org [EMAIL PROTECTED] [EMAIL PROTECTED] http://www.marcus-brinkmann.de
