Greetings Mattia and thank you for your reply, >control: reassign -1 sponsorship-requests
>> Package: tldp >> Severity: normal >> >> Greetings Mentors and other Debian folk, >> >> I am looking for a sponsor for my package "python3-tldp": > >emh, I'm pretty sure is very very hard to find sponsorship filing a >bug against a non-existing package ;) Yes, sorry. My first attempt was rejected for not matching package 'sponsorship-requests' so I figured that I had to use the package name. I guess I'm still understanding how to interact smoothly with the Debian system. >you're lucky that somebody reads bugs filed against unknown >packages :) Yes, and your reply has been very helpful. >> * Package name : tldp >> Version : 0.7.8 >> Upstream Author : Martin A. Brown >> * URL : https://github.com/tLDP/python-tldp.git >> * License : MIT >> Section : python >> >> It builds these binary packages: >> >> python3-tldp - automatic publishing tool for DocBook, Linuxdoc and >> Asciidoc >> >> To access further information about this package, please visit the >> following URL: >> >> https://github.com/tLDP/python-tldp >> >> Also available, here: >> >> dget -x http://linux-ip.net/debian.ITP-822181/tldp_0.7.8.dsc > >[ to be clear about the following: I'm not going to sponsor this >package; NEW (as in ITPs) from totally new people are outside my >policy, sorry ] Understood. >being also a guy that cyclically processes RFSes, let me ask you: >why not using mentors.d.n? Well, I'm on the 'debian-ment...@lists.debian.org' mailing list. Is that what you mean by mentors.d.n? >Furthermor, the signature on that file is made with a 1024 bit DSA >key, something that I don't really consider secure, and that we >removed from our keyrings. Do you mind creating a new one, at >least 4096 bit RSA? Sure. It could stand updating. I can certainly do that. >> Changes since the last upload: >> >> tldp (0.7.8) unstable; urgency=low >> >> * creating a manpage to satisfy Lintian, bumping version >> * renamed source package to 'tldp' >> * Initial release (Closes: #822181) >> >> -- Martin A. Brown <mar...@linux-ip.net> Tue, 19 Apr 2016 15:40:13 -0400 > >umh. If this is the first version of the package, the changelog >should contain only the "initial release" line. Also, the version >is totally off, please read the in the debian policy the chapter >dealing with the version and native/non-native stuff. I have read the entire Policy Manual, the Debian Developer's Manual, the Debian New Maintainers' Guide and the Guide for Debian Maintainers, but I still do not understand the native vs. quilt distinction. I asked on debian-ment...@lists.debian.org, but have not gotten an answer or a pointer. I am happy to make changes to my package to try to make it conform. In order to do so, I simply need more guidance. For me, it would help to see an example of a package that provides a debian/ packaging directory, but is not hosted on alioth. >> This is the first upload and/or request for sponsorship of >> python3-tldp. >> >> The package builds (successfully) using 'gpb buildpackage' straight >> from a cloned checkout (on master at HEAD). > >I'm going to assume you used either sbuild or pbuilder with gbp, as >packages are supposed to build in a clean *sid* chroot. Well, I was able to build the package (straight from checkout) using 'debuild', 'debuild-pbuilder' and 'gbp buildpackage'. Also, I did not know about the clean 'sid' chroot, despite having plowed through the mountain of documentation. Thank you. >> The lintian warnings I >> see are: >> >> W: tldp source: newer-standards-version 3.9.8 (current is 3.9.6) > >update lintian, this has been fixed yesterday. OK. Probably if I use a 'sid' instance, that will work. >Well, if it says the current is 3.9.6 you are using an actually too old >lintian to be really effective; please always use the version you can >find in unstable or jessie-backports. > >> W: tldp source: debian-watch-file-in-native-package > >well, yes, i said above why. > >I have a feeling you are not running lintian with pedatinc enable, >please run lintian with more verbosity level. (note that i didn't >even downloaded the package, this is just a sensation). $ lintian --pedantic ../tldp_0.7.8.dsc W: tldp source: newer-standards-version 3.9.8 (current is 3.9.6) W: tldp source: debian-watch-file-in-native-package P: tldp source: debian-watch-may-check-gpg-signature (I have not running lintian myself, rather I'm letting it get called by the build scripts.) >PS: your email is full of trailing whitespaces on basically every >line, I wonder what MUA you are using (my guess is alpine?) and how >you manage to do so (manually hit the space bar then return? :o). Yes, alpine. Possibly the alpine editor? I note your observation. Again, thank you for all of the feedback! It has been instructive and helpful! -Martin -- Martin A. Brown http://linux-ip.net/
