[cl-debian] ironclad, tbnl, url-rewrite: updates and questions
Hello, a few updates on the three packages I'm providing (sorry for the late, due to a *very* annoying hard disk crash). Ironclad: * accepted in main; * got the first bug: #335868. Yayyyy! * fixed the bug; * updated the package to the latest upstream release. TBNL: * rejected by ftp-master, due to debian/copyright issues; * fixed the bug; * updated the package to the latest upstream release. URL-REWRITE: * rejected by ftp-master, due to debian/copyright issues; * fixed the bug. My darcs repositories (managed with darcs-buildpackage) are available at the usual location: http://debian.muvara.org/darcs/debs (.deb sources) http://debian.muvara.org/darcs/upstream/ (upstream repos) And now, a few questions... 1. I've noticed that bug reports and ftp-master responses for other cl-debian packages are being sent to this mailing list, too. Is there a way to automate the process for my packages? 2. How should I notify when my repositories have got interesting updates? Is email pestering (like this one) ok? 3. Have you got a procedure for signing the patches being recorded on darcs? (I've used one for Mercurial[1], that *should* be adaptable to darcs); 4. Should a copy of my repositories go under http://cl-debian.alioth.debian.org/ ? If yes, is there anything I should do? Of course, you can point me to any fine manual that I should have read before asking :-) Regards, aleste - - - - References: [1] Mercurial distributed SCM: http://selenic.com/mercurial/ -- Alceste Scalas <alceste@muvara.org>
Hello! On Sat 29 Oct 2005 18:02 +0200, Alceste Scalas wrote:
My darcs repositories (managed with darcs-buildpackage) are available at the usual location:
http://debian.muvara.org/darcs/debs (.deb sources) http://debian.muvara.org/darcs/upstream/ (upstream repos)
And now, a few questions...
1. I've noticed that bug reports and ftp-master responses for other cl-debian packages are being sent to this mailing list, too. Is there a way to automate the process for my packages?
IIRC you should subscribe the CL-Debian mailing-list to source-package@packages.qa.debian.org, but I never tried. Go to http://packages.qa.debian.org/source-package for more info.
2. How should I notify when my repositories have got interesting updates? Is email pestering (like this one) ok?
Sure!
3. Have you got a procedure for signing the patches being recorded on darcs? (I've used one for Mercurial[1], that *should* be adaptable to darcs);
Well, if you use `darcs send`, there's a --sign option (`darcs send --help` or the manual at [1]). AFAIK there's no way to sign with `darcs record` and anyway even when a signed patch is integrated, there's no record of the PGP key in package/_darcs/patches/patch.gz :-(
4. Should a copy of my repositories go under http://cl-debian.alioth.debian.org/ ? If yes, is there anything I should do?
IMHO yes, for sure. Get an account on http://alioth.debian.org and then Peter should add you to the group. Thx, bye, Gismo / Luca [1] file:///usr/share/doc/darcs/manual/index.html#x1-440003.5.5
Il giorno sab, 29/10/2005 alle 18.02 +0200, Alceste Scalas ha scritto:
Ironclad: * accepted in main; * got the first bug: #335868. Yayyyy! * fixed the bug; * updated the package to the latest upstream release.
FYI: I've just updated the ironclad repositories to the new upstream release (0.10). Usual links: http://debian.muvara.org/darcs/debs (.deb sources) http://debian.muvara.org/darcs/upstream/ (upstream repos) Regards, alceste -- Alceste Scalas <alceste@muvara.org>
participants (2)
-
Alceste Scalas -
Luca Capello