Hi Yaroslav, Sorry for taking a week to respond. There was not a single day last week I could have a contiguous space of one hour to address the issues.
> there is 1 more crucial step: projects which are not Debian specific > should not be packaged in "native debian" format, i.e. when you > have only .orig.tar.gz + .dsc -- they should have .diff.gz or > .debian.tar.gz ( source format quilt 3.0, which I would recommend to use > as well) , and their version must include debian revision... I set up quilt, but there is no .diff.gz as there is no patches, for the simple reason that the communication between maintainer (me) and the upstream (me again) never leaves localhost. The newly created debian/source/format now contains "3.0 (quilt)". I also set up pbuilder, and with little effort, it successfully builds aghermann from upstream tarball (after renaming aghermann-0.4.3.3.tar.bz2 to aghermann_0.4.3.3.orig.tar.bz2). And, no warnings from lintian. > so if 0.4.3.2 is the "upstream" release number, debian release should be > 0.4.3.2-1 and version in debian/changelog should be adjusted > accordingly. My changelog now has all entries as you suggest. Also, "unstable" is replaced with "UNRELEASED" throughout. > 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)? On this point, I'd like to clarify that I would rather do Debian releases from upstream tarballs (i.e., as produced by "make dist-bzip2" and not directly from Git). As matters stand, git snapshots can be buggy, or not in a buildable state at all. Put differently, the workflow goes like this: (1) make dist-bzip2 when it's ready and upload to the URL mentioned in debian/watch; (2) fetch it, rename replacing '-' with '_' and inserting '.orig'; (3) untar, cd and debuild. > having vcs- fields (useful for debcheckout) would be + as well I did add vcs entries, but as I said above, I don't propose to build from git, so perhaps vcs- fields are not applicable? > I bet you lack build-depends My debian/control file contiained: "Build-Depends: debhelper (>= 7)". As g++ >= 4.6.2 is required, I changed this record accordingly. > 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/ Done. > Do you have GPG key btw? doesn't have to be signed by a DD (yet) but it > would be great to identify at least that we are talking to the same > person ;-) so, just sign you source package (debsign) and either upload > to mentors.debian.org (preferrable) or make it available anywhere else > -- I could then grab it from there, do review, build, upload (if > everything is ok of cause) Now I have a PGP key associated with this email address (public part is available here: http://johnhommer.com/academic/pgpkey, and also uploaded to subkeys.pgp.net). > 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) . Oh, I was probably missing something dead obvious here... Alioth being suspiciously similar to berlios.de (where I tried to host my git tree before giving up in favour of github.com), I suspect I might/should be able to eventually do git push to. After poking around a second time, I did git init and git clone in my ~ at aghermann.alioth.debian.org, and then it was the Aha moment.. :} Now, the corresponding record in .git/config is: [remote "origin-da"] url = ssh://[email protected]/home/users/hmmr-guest/public.git/aghermann fetch = +refs/heads/*:refs/remotes/origin-da/* So this should be it. Again, sorry for confusion. Finally, I have uploaded all the files produced by debuild to johnhommer.com/academic/code/aghermann/source, and pushed the last changes to github.com/hmmr/aghermann, much hopeful this time I will pass :} Cheers -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/CADRQDB0Jg9TJ+92kcxWxeso=s+ejrtsebdqgg9s3ozgdhv0...@mail.gmail.com
