"Marcelo E. Magallon" <[EMAIL PROTECTED]> writes: > Hi, > > On Mon, Jun 02, 2003 at 03:15:19PM -0400, Deedra Waters wrote: > > > I've been working on the package "kernel-patch-speakup" which has a > > source package called speakup-cvs and produces the binary called > > kernel-patch-speakup_20021221-1_all.deb, well, there is a stable > > version of speakup that I'd like to package and have it keep the > > kernel-patch-speakup name. This source package is called speakup, and > > produces a similar binary called "kernel-patch-speakup_1.5-1_all.deb" > > > The problem currently is that the new source package produces a > > binary package which already exists, and is generated by a different > > source package > > I am not sure I understand why that's a problem. The only thing you > have to take into account is adding an epoch to the new > kernel-patch-speakup,
Sure, the epoch is of course necessary. What I am wondering about is how katie will react if a source package is uploaded which produces a binary package which is already produced by another source package. I.e., is there any thing one would need to be careful about, or does this Just Work? -- CYa, Mario | Debian Developer <URL:http://debian.org/> | Get my public key via finger [EMAIL PROTECTED] | 1024D/7FC1A0854909BCCDBE6C102DDFFC022A6B113E44