Hi David,
On Fri, Jun 21, 2013 at 03:28:45PM +0200, David Parsons wrote:
> Hi again,
>
> I've just commited the changes, pdebuild looks OK, although it does
> complain about some hooks not being found.
I'm not sure what hooks you might mean - my pbuilder run was perfectly
fine. I fixed a lintian error (you should not Build-Depends on
Build-Essential packages (libc6-dev) by just removing libc6-dev and some
minor spelling, formatting things mentioned by lintian.
> I'll be away for two weeks so don't take it personally if I don't
> answer ;-)
If it's vacation just enjoy it. We need to wait with the upload until
the source of the pdf documentation is provided. I also would be happy
if we could sort out the issue that the internal utilities end up in
/usr/bin instead of /usr/lib/kissplice - what do you think about my
suggestion?
If anybody else might be interested in this package as well - you've got
two weeks to provide a patch. ;-)
Kind regards
Andreas.
> Le 21/06/2013 11:41, Andreas Tille a écrit :
> >Hi David,
> >
> >On Fri, Jun 21, 2013 at 10:37:50AM +0200, David Parsons wrote:
> >>I didn't write manpages for the other executables because they
> >>shouldn't be called directly from the user. The main executable is
> >>actually a python script that calls all the other executables in an
> >>integrated pipeline (with some executions being done in parallel) .
> >>I personally don't like the multi-binary arch very much but I won't
> >>be able to modify this right now. I'll talk about that with the
> >>upstream team.
> >The best way to fix this would be to move the binaries in question
> >to /usr/lib/kissplice and adapt the PATH inside the main program.
> >Given the fact that it is somehow about esthetics I would not call
> >this a stumbling stone for a first upload, but it would be nice to
> >have a better design.
> >
> >>>Finally the source would be considered as "non-free" because the source
> >>>for doc/user_guide.pdf is missing. The best way to fix this is to ask
> >>>upstream for the LaTeX source of this documentation. If they do not
> >>>want to distribute this source we need to remove the doc from the source
> >>>tarball (which would be suboptimal, thought). Given that upstream is
> >>>cooperative the doc should also be installed into the binary package -
> >>>just mention it in debian/docs.
> >>I'll add the .tex and add it to the binary package
> >It only needs to be inside the *source* package. It is sufficient to
> >ship (even the prebuilded) PDF inside the binary, but the source simply
> >needs to exist.
> >
> >>Thanks a lot !
> >You are welcome
> >
> > Andreas.
> >
>
>
> --
> 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/51c4550d.2010...@inria.fr
>
>
--
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/20130624072318.gc14...@an3as.eu
