Package for libquoin-clojure
debian at babilen5.org
Tue May 21 14:47:43 UTC 2013
On Sat, May 18, 2013 at 07:42 +0200, Eugenio Cano-Manuel Mendoza wrote:
First and foremost: You don't have to CC me as I am subscribed to this list. I
am currently getting your mails twice.
> Before I push libscout-clojure again I want to make a few questions:
Please name the source-package (and hence the git repository) "scout" as that
name has not yet been taken in Debian and it is the name of the upstream
project. The *binary* package should, naturally, be libscout-clojure.
> Do we have to add a debian/VERSION tag? I see it in robert-hooke but not in
The debian/VERSION tag references the commit that has been uploaded, I
typically tag that *after* I uploaded a package (or after it has been
uploaded) and sign the tag. You can easily push the tag later with "git push
> Regarding the branches, I currently have master, upstream, and
> pristine-tar. According to http://wiki.debian.org/Java/JavaGit this is enough
> but I see that slingshot and robert-hooke has them as remote branches. What am
> I missing?
You have to push those branches explicitly. A "git push --all" or "git push
--tags" would probably get them too, but you can also push them explicitly.
> debian/control source should be "scout", package name "libscout-clojure" git
> repository name "scout-clojure". Am I correct?
Not quite .. I'd like it if the git repository has the same name as the source
package. You would therefore have scout for repo and source package +
libscout-clojure for the binary.
I think we should only suffix the source-package name with -clojure if the
original name has already been taken in Debian (which is the case for
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 836 bytes
Desc: Digital signature
More information about the Pkg-clojure-maintainers