Bug#379374: Spe packaging status
Stefano Canepa wrote: > Emilio Pozuelo Monfort wrote: >> [ CCing debian-python and ITA 379374 ] > >> Hello Stefano > >> I've updated spe's packaging files in the PAPT repository a bit, and was >> wondering what's the status of your ITA bug. If you don't plan to own the >> package in Debian, we could maintain it in the team, although if you want to >> maintain it yourself (with or without the team's help) that's alright too. >> Let >> me know what do you think and I'll act accordingly. > > How can I download your modifications? They are in the repository. You can do svn co svn://svn.debian.org/svn/python-apps/packages/spe/ to get it, and 'svn up' to update when there are new revisions. > I don't want to own the package > spe is just a product I use, the team can own the package. That's nice. I've updated the Maintainer so it's the Python Applications Packaging Team. It was Debian QA before, since the package was orphaned. > I started the > NM process and just want to understand how to do packages to help > debian. I just need one more package as I'm on hold in the process. There is some good documentation out there, such as the new maintainer's guide, the debian policy or the developers reference. I suggest you to take a look at them if you haven't already done it. http://www.us.debian.org/doc/ Take care, Emilio > Bye > sc > signature.asc Description: OpenPGP digital signature
Bug#379374: Spe packaging status
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Emilio Pozuelo Monfort wrote: > [ CCing debian-python and ITA 379374 ] > > Hello Stefano > > I've updated spe's packaging files in the PAPT repository a bit, and was > wondering what's the status of your ITA bug. If you don't plan to own the > package in Debian, we could maintain it in the team, although if you want to > maintain it yourself (with or without the team's help) that's alright too. Let > me know what do you think and I'll act accordingly. > > Also, I've seen there are new releases in your svn repository, but I couldn't > find any tarball for them. Is there any reason for this? If not, would you > mind > releasing a tarball whenever you make a release? > > Cheers, > Emilio > I'm working from spe SVN. The package I did was wrong. The correct release is number is 0.8.4b. There is no tarbar and I did some errors that messed up team SVN. I need the help of the team. bye sc - -- Stefano Canepa aka sc: [EMAIL PROTECTED] - http://www.stefanocanepa.it Three great virtues of a programmer: laziness, impatience and hubris. Le tre grandi virtù di un programmatore: pigrizia, impazienza e arroganza. (Larry Wall) -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHR1W+l8XQY46MbvERAgIrAKCGIjb2tXubCnLIEiqMePpbIXbdnwCfaRko 7IkOllTchMj3q9R3h57F3fQ= =gDyl -END PGP SIGNATURE- begin:vcard fn:Stefano Canepa n:Canepa;Stefano email;internet:[EMAIL PROTECTED] x-mozilla-html:FALSE version:2.1 end:vcard
Bug#379374: Spe packaging status
[ CCing debian-python and ITA 379374 ] Hello Stefano I've updated spe's packaging files in the PAPT repository a bit, and was wondering what's the status of your ITA bug. If you don't plan to own the package in Debian, we could maintain it in the team, although if you want to maintain it yourself (with or without the team's help) that's alright too. Let me know what do you think and I'll act accordingly. Also, I've seen there are new releases in your svn repository, but I couldn't find any tarball for them. Is there any reason for this? If not, would you mind releasing a tarball whenever you make a release? Cheers, Emilio signature.asc Description: OpenPGP digital signature
