Re: Packaging InVesalius
Hi Andreas,
Now the rename is working. He is renaming the tarball to invesalius_3.0~b3.orig.tar.gz. To make it work I used uversionmangle instead of dversionmangle. The folder inside this tarball has the name "invesalius3-3.0-b3" instead of "invesalius_3.0~b3", is this a problem?
The Lintian returns two warnings:
W: invesalius: extra-license-file usr/share/doc/invesalius/LICENSE.txt.gz > It's because the package has two license files, one in English and other in Portuguese. The Portuguese version is because a license must be in Portuguese to be recognized by the Brazilian government.
W: invesalius: binary-without-manpage usr/bin/invesalius-3.0 > If you think it's necessary, I can create a manpage to InVesalius.
Best regards.
----- Mensagem original -----
De: "Thiago Franco Moraes" <tfmoraes@cti.gov.br>
Para: debian-med@lists.debian.org
Enviadas: Domingo, 20 de Janeiro de 2013 22:48:02
Assunto: Re: Packaging InVesalius
Hi Andreas,
On Mon, Jan 14, 2013 at 11:59 AM, Andreas Tille <andreas@an3as.eu> wrote:
> Hi Thiago,
>
> On Sun, Jan 13, 2013 at 05:39:11PM -0200, Thiago Franco Moraes wrote:
>> I updated the debian/watch to match the last invesalius release. I
>> have to use "opts=dversionmangle" to match the package version to git
>> tag. I wrote a get-orig-source too (well, actually, I copied the one
>> Andreas Tille wrote python-casmoothing :) ).
>
> Could you imagine how frequently I copy myself from other packages? :-)
:)
> I checked the build and it creates a package. Please note that the watch
> file does not work 100% - I needed to manually
>
> ln -s invesalius_3.0.0b3.orig.tar.gz invesalius_3.0~b3.orig.tar.gz
>
> Without testing I think an additional "filenamemangle" is your friend -
> please check the `man uscan?.
I got today (sunday) to try to resolve this, but I was not able to get
filenamemangle work. Maybe I need to try more.
>> Ah, I have to wrote a
>> patch to change the shebang from "#!/usr/local/bin/python" to
>> "#!/usr/bin/python".
>
> Yep - and there are some other lintian warnings - perhaps you simply use
> your upstream hat to fix some permissions. I'd also think that you
> could do the patch above upstream - I can not really imagine that there
> are production boxes where you find the Python interpreter in
> /usr/local these days (or use env).
Using the git tag invesalius-3.0.0b3 as base, I created a new branch
(beta3) and I resolved these problems with permissions and the
shebangs. Ah, I took the opportunity to backport some commits from
trunk into this branch (Thanks git for makes it easier :) ), some of
these commits fix bugs in InVesalius 3 beta 3. After the backport, I
created a new tag v3.0-b3.
> Kind regards
>
> Andreas.
>
> --
> http://fam-tille.de
Thanks again!
--
To UNSUBSCRIBE, email to debian-med-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: [🔎] CAMmoLX9RJ+u1gPr8ke4pT-gOqrPoW26ggtasRN2Nr00bKiRvpA@mail.gmail.com">http://lists.debian.org/[🔎] CAMmoLX9RJ+u1gPr8ke4pT-gOqrPoW26ggtasRN2Nr00bKiRvpA@mail.gmail.com
Reply to: