Hi Sébastien, many thanks for you preparations.
On Fri, Nov 02, 2012 at 05:09:10PM -0400, Sébastien Boisvert wrote: > The Ray Debian package is now at > http://anonscm.debian.org/gitweb/?p=debian-med/ray.git;a=summary I cloned this and think the packaging is fine so far. However, I do not see any upstream and pristine-tar branch. Could you please post what a `git branch` at your site says? > I fixed everything that lintian reported except these: > > W: ray-extra: unusual-interpreter > ./usr/share/ray/scripts/plot-color-distributions.R #!/usr/bin/Rscript > W: ray-extra: unusual-interpreter > ./usr/share/ray/scripts/plot-coverage-distribution.R #!/usr/bin/Rscript > W: ray-extra: unusual-interpreter > ./usr/share/ray/scripts/plot-library-distribution.R #!/usr/bin/Rscript > > r-base-core installs /usr/bin/Rscript so it is legit. Yes. I would consider this a lintian bug. > Maybe /usr/bin/Rscript should be added in > > /usr/share/lintian/checks/scripts (package lintian) > > > Using /usr/bin/env Rscript also throws unusual-interpreter. I do not see any reason to try tricks to circumvent lintian problems. If I were you I would use `reportbug lintian` to report this problem. If you are bored by these lintian warnings you could meanwhile add the lines above in a file debian/ray.lintian-overrides and lintian will ignore the warnings. > >In the Debian Med team we are using the team mailing list as maintainer > >so everybody gets informed about uploads, bugs etc. It is easy to add > >other uploaders (people feeling responsible and adding code to the > >packaging). > > > > Done. Great. > >and install these using a file ray.manpages containing just this string > >(see dh_installman). A patch would be fine as well but editing a plain > >file is way more comfortable than handling a patch and it is easier to > >point upstream to a plain file when asking upstream to include this file. > > > > I added debian/Ray.1 that is simplier than a patch. Fine. > >Keep on your good work and feel free to keep on asking if something else > >might remain unclear > > > > My question: what's next ? I think the package deserves a watch file to enable uscan detecting new versions. Unfortunately it is not that obvious to me how to download a versioned source tarball - otherwise I would have just injected such a watch file. > I think debian/2.1.0-4 should do it, unless you have other suggestions, in > which case > I will gladly implement them. I just have one remark for the versioning: While it is a good idea to have differently versioned packages if there are changes it is kind of usual to uploading a *new* package starting with version 2.1.0-1. The rationale is that changes done before the first upload to the official Debian mirror are not really relevant. While this is rather some "usual" thing to do there is no real need I would like you to consider this. However, if there was some non-Debian upload (I have noticed that 2.1.0-2 was targeting at precise) you should definitely leave the versioning as it is now. What needs to be done before the upload is to file an so called ITP (=Intend To Package) bug using reportbug wnpp and following the menu. It makes sense to add a final remark that the package will be maintained in the Debian Med team and also give the Vcs-Git location. Kind regards and thanks for your work on this Andreas. -- http://fam-tille.de -- To UNSUBSCRIBE, email to debian-med-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20121103172609.ga18...@an3as.eu
