Hi Yaroslav, > well, technically speaking there is no strict requirement to host packaging > repository on git.debian.org but it is indeed strongly encouraged! I have refreshed my keys on alioth and set up the new git remote for cnrun.
> Somewhat > stronger advisory (almost requirement) is to point to the repository which has > a branch with debian/ packaging in its default HEAD -- that seems to be the > case (although once again it is outdated so do not know if building package > out > of its fresh git clone would work just fine with dpkg-buildpackage ;-) ) > My concern is already existing proliferation of different git > repositories especially that the one pointed by Vcs-git field is already > outdated I believe (carries 0.11 packaging): I was waiting for any last-minute amendments you might want me to do before last 'release' commit :} > Vcs-Git: git://github.com/hmmr/cnrun.git > Vcs-Browser: http://cnrun.git.sourceforge.net/git/gitweb-index.cgi Updated my repositories at git.debian.org and edited debian/control accordingly and pushed. > 2. > there is no need to upload to experimental since this is a NEW pkg -- > target unstable Ok. > 3. > "building on original work by Thomas Nowotny <[email protected]>" > so I guess worth adjusting debian/copyright? ;-) Fixed in debian/copyright. Thank you both for bringing this up: I have now made a more thorough effort at it. I also fixed vcs fields in debian/control and set things up on alioth.debian.org for aghermann, too. So, please refetch the dsc from the same location: http://johnhommer.com/academic/code/cnrun/source/deb/cnrun_1.1.12-1.dsc Cheers, Andrei -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/CADRQDB2SjUuftRv1=yone5w3bhp8xzfq3ntoyddz6fr_7q3...@mail.gmail.com
