[cl-debian] New packages: ironclad, tbnl, url-rewrite
Hello, I've packaged three CL libraries I'm currently playing with: cl-ironclad Cryptography package for ANSI Common Lisp cl-tbnl A toolkit for building dynamic websites with Common Lisp cl-url-rewrite Common Lisp package for rewriting URLs in (X)HTML documents The darcs repositories are available here: http://debian.muvara.org/darcs/ If you decide to include them in Debian, I should be able to provide patches and keep them updated. Regards, alceste, who hopes to have followed the right procedure :-) -- Alceste Scalas <alceste@muvara.org>
Ola, Let me first thank you for packaging these libraries. The packaging itself it pretty good, impressively so for a non-DD :-). In general: maybe you could use dh_lisp, it actually is pretty easy to use and 'just works'. Also: E: url-rewrite source: package-uses-debhelper-but-lacks-build-depends N: N: If a package uses debhelper, it must declare a Build-Depends on N: debhelper. N: W: url-rewrite source: build-depends-without-arch-dep N: N: The control file specifies source relations for architecture-dependent N: packages, but no architecture-dependent packages are built. There are N: some exceptions, e.g. build dependencies that have to be satisfied N: while calling the "clean" target of debian/rules, the most common case N: of which is a Build-Depends: debhelper if you use dh_clean in the N: "clean" target. In other cases, you most likely need to change N: Build-Depends to Build-Depends-Indep. N: N: Refer to Policy Manual, section 7.6 for details. On Sunday 16 October 2005 15:34, Alceste Scalas wrote:
cl-ironclad Cryptography package for ANSI Common Lisp
When I downloaded upstream I got version 0.9.1. Also:: there was no UPSTREAM_ironclad_0.9 tag in the darcs archive. darcs-buildpackage and my darcs-build.sh script expect this.
cl-tbnl A toolkit for building dynamic websites with Common Lisp
Great! I was thinking of taking a look at it only yesterday. The replacement of the jpg (good find!) should be noted in a debian/README file (which is then also installed of course) W: cl-tbnl: non-standard-dir-perm usr/share/common-lisp/source/tbnl/contrib/ 0655 != 0755
cl-url-rewrite Common Lisp package for rewriting URLs in (X)HTML documents
E: cl-url-rewrite: changelog-file-not-compressed CHANGELOG
If you decide to include them in Debian, I should be able to provide patches and keep them updated.
Great! If you fix these small problems (or tell me to fix them and then resync from my darcs repositories) I'll be more then happy to upload them. Groetjes, Peter -- signature -at- pvaneynd.mailworks.org http://www.livejournal.com/users/pvaneynd/ "God, root, what is difference?" Pitr | "God is more forgiving." Dave Aronson|
Il giorno lun, 17/10/2005 alle 09.01 +0200, Peter Van Eynde ha scritto:
In general: maybe you could use dh_lisp, it actually is pretty easy to use and 'just works'.
Uh, I believed I was still using it... Is there any of its feature that I didn't use (and maybe reinvent)?
When I downloaded [ironclad] upstream I got version 0.9.1.
Oops! Sorry, I forgot to say that I'm experiencing some compilation errors with ironclad-0.9.1 + cmucl. I'd suggest to keep the 0.9 version until I'll sort them out and/or ask the upstream author. I should work on it very soon. Other than this, I've fixed everything you pointed out. I've also switched to darcs-buildpackage, with new repositories built from scratch and managed the Right Way(TM) (well, hopefully :-) The repositories are here: http://debian.muvara.org/darcs/debs http://debian.muvara.org/darcs/upstream The upstream/ directory contains the upstream repos used by darcs-buildpackage. I've applied some patches in there, too, to avoid non-free content appear in .orig.tar.gz when packages are built. More in detail: tbnl: replaced non-free Frank Zappa photo ironclad: removed some non-free patented algorithms The upstream version numbers have been slightly altered to reflect the changes. All the remaining debian-specific patches (e.g. adding debian/ directory) are applied in the debs/ repositories. Oh, I didn't run dbp-markdeb yet. Is all this stuff ok? Feel free to apply all the fixes you need and/or ask me to do so, whatever is faster :-) Regards, alceste -- Alceste Scalas <alceste@muvara.org>
On Wednesday 19 October 2005 14:18, Alceste Scalas wrote:
Uh, I believed I was still using it... Is there any of its feature that I didn't use (and maybe reinvent)?
Sorry I was not awake then it seems. I thought I saw postinst files etc.
Other than this, I've fixed everything you pointed out. I've also switched to darcs-buildpackage, with new repositories built from scratch and managed the Right Way(TM) (well, hopefully :-)
Well, actually I use a script instead of the actual buildpackage program, but I do use the general idea and other scripts. I had a problem with the program recreating .orig.tar.gz files, which never works.
The upstream/ directory contains the upstream repos used by darcs-buildpackage. I've applied some patches in there, too, to avoid non-free content appear in .orig.tar.gz when packages are built. More in detail:
That is ok, but should only be noted in the README.Debian file, no alteration of upstream version numbers is needed.
Oh, I didn't run dbp-markdeb yet.
Hmm. I only run it after I get the confirmation that it got uploaded. I think that in this way you mark the actual tree that got uploaded. If so I think I should mark my branch of you tree and you should import it again. Boh.
Feel free to apply all the fixes you need and/or ask me to do so, whatever is faster :-)
Ok. I will download the new archives and see. Groetjes, Peter -- signature -at- pvaneynd.mailworks.org http://www.livejournal.com/users/pvaneynd/ "God, root, what is difference?" Pitr | "God is more forgiving." Dave Aronson|
Il giorno mer, 19/10/2005 alle 20.06 +0200, Peter Van Eynde ha scritto:
On Wednesday 19 October 2005 14:18, Alceste Scalas wrote:
The upstream/ directory contains the upstream repos used by darcs-buildpackage. I've applied some patches in there, too, to avoid non-free content appear in .orig.tar.gz when packages are built. More in detail:
That is ok, but should only be noted in the README.Debian file, no alteration of upstream version numbers is needed.
Ok, next releases will keep the upstream version numbers. Regards, alceste -- Alceste Scalas <alceste@muvara.org>
participants (2)
-
Alceste Scalas -
Peter Van Eynde