package naming
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 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 package Would anyone be able to give me ideas on how to resolve this? Thanks Deedra -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQE+26JTU5AGPOTGNc8RAh9ZAJ9kAcJug4mKKlcWdUWujuzeEtqOQQCgvKuZ +72u7yelYACIjCgcPGISoGE= =DrQ1 -END PGP SIGNATURE-
key signing
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I'm in the process of applying to become a debian developer, and am having a great deal of trouble getting my gpg key signed. I've checked the keysigning coordination page, registered my request for keysigning, and finally sent mail to [EMAIL PROTECTED] to try and find a debian developer that is close enough to me to try and get my gpg key signed. I'm almost totally blind, and unable to drive which makes things more dificult, because I can't drive to where any developers are to get the key signed that way. I'm wondering if any of you would be coming through florida any time soon, mainly St. Petersburg, Tampa, or Clearwater who would be willing to sign my gpg key. Sense I can't drive, I'm more or less limited to those cities. Thanks, Deedra -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQE+w9OGU5AGPOTGNc8RAr9oAKCX+03Zm7fJ6A++tKClqO+1KL9UwACeNKjd wBbrEHjA/HHhfl86xpxGXP4= =RcSK -END PGP SIGNATURE-
