-----BEGIN PGP SIGNED MESSAGE-----
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"
I would like to continue packaging the speakup-cvs as well though, because
there is a great deal of time between speakup releases, anda lot of blind
people like to use the speakup cvs.
Basically my plan was to have the stable version of speakup use the
kernel-patch-speakup package name and move the speakup-cvs source into
kernel-patch-speakup-cvs, or something to that effect.
The problem currently is that the new source package produces a binary
package which already exists, and is generated by a different source
Would anyone be able to give me ideas on how to resolve this?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)
Comment: Made with pgp4pine 1.76
-----END PGP SIGNATURE-----