Aghermann packaging (Was: your mail)
Hi,
On Tue, Dec 20, 2011 at 07:07:16PM -0500, Yaroslav Halchenko wrote:
>
> also I myself do that and recommend others -- I leave changelog entries
> with UNRELEASED (or neurodebian ;-) ) instead of unstable unless it
> actually got into unstable. That helps later on to see which versions
> made into Debian just by looking at the changelog
Yes! Please regard
http://debian-med.alioth.debian.org/docs/policy.html#debian-changelog
> 2.
> looking at
> https://github.com/hmmr/aghermann/blob/master/debian/control
> it looks incomplete -- have you tried to build the package in a clean
> environment (e.g. using pbuilder, or git-pbuilder if you use
> git-buildpackage, or cowbuilder)? I bet you lack build-depends
>
> having vcs- fields (useful for debcheckout) would be + as well
See item 8. in
http://debian-med.alioth.debian.org/docs/policy.html#debian-control
> 3.
> https://github.com/hmmr/aghermann/blob/master/debian/copyright
> I would strongly recommend to convert it to use DEP-5:
> http://dep.debian.net/deps/dep5/
See
http://debian-med.alioth.debian.org/docs/policy.html#debian-copyright
> 4. alioth project -- probably others could comment on that ... but we
> don't need to wait -- for me to do final review and sponsor its upload
> to Debian I would just need source package (.orig.tar.gz + .dsc +
> .debian.tar.gz or .diff.gz) .
Lacking the original question I can not properly comment on this. If
the question was whether you should upload before commiting the code to
Alioth I'd say it is no precondition but definitely helps. If you want
to set Vcs fields properly and valid (see question 2.) it should be
quite logical that you should commit to Alioth first and finally it is
not that much of work.
Kind regards
Andreas.
--
http://fam-tille.de
Reply to: