Re: ITP strap-base - Some questions
Hi Christoph,
On Thu, May 31, 2012 at 11:27:44AM +0200, Dr. med. Christoph Gille wrote:
> Hi Andreas, Hi Charles,
>
> You mean svn commit -m "some text" ?
Yes. Alternatively if you simply call
svn commit
your $EDITOR pops up and asks you for a comment (at least this should be
the default configuration). Please give some piece of information (one
liner is in most cases enough) that describes your change / motivation
of the change to keep other team members informed. I did several times
asked for comments on development list of the team[1] and putted you in
CC and because I did not got any answer I assumed you might have a quite
strict SPAM filter. It would be nice if you could give some summary
about the issues I mentioned[1] or at least some sign that you received
the messages.
> I completely forgot about
> this. I had to explore svn since I have not worked with svn before.
If you might prefer Git this is also established in the team. Otherwise
it should not be that hard to teach you the very few secrets which are
relevant here. :-)
> I
> become more and more confident with the build system but I still encounter
> some minor problems.
May be it makes sense to consider MoM[2]?
> Do I need svn commit each time I try package building via
> svn-buildpackage -rfakeroot -uc -us ? Or can I use option
> --svn-ignore? Is it using the local files or the files on the svn server.
As I said in one of my other mails I'm personally not using
svn-buildpackage but rather plain debuild / pdebuild. Perhaps some
user of svn-buildpackage could answer this question. In any case I
have the strong impression that you are commiting to frequently and
to many intermediate (testing) steps.
> I have successfully resolved some svn conflicts, but currently I am
> stuck. I would like to create a directory
> packages/strap/trunk/debian/bin/ but svn does not let me do this.
>
> $ svn mkdir debian/bin
> $ svn commit -m "try mkdir debian/bin"
> Adding trunk/debian/bin
> svn: Commit failed (details follow):
> svn: File already exists: filesystem '/svn/debian-med/db', transaction
> '11117-1', path '/trunk/packages/strap/trunk/debian/bin'
>
> I also did
> $ svn resolved debian/bin
> and
> $ svn update
> without success
>
> What do you suggest? As a work around I have a directory debian/bin2
May be you forgot to `svn up` before starting to work? I remember
that I created to simplify your packaging. I did now moved everything
from debian/bin2 to debian/bin - just `svn up`.
> reportbugs could not connect to the bug database even though I have
> direct internet connection without http proxy.
> Then reportbugs suddenly terminated and all my edits were lost.
Ahh, that's sad. reportbug needs a configured SMTP server because it
sends an e-mail. In principle your mail should not be lost but rather
sit somewhere in /tmp. You could have sended the content of this
file to control@bugs.debian.org.
> The packages strap and strap-base are almost finished. I changed
> strap such that it works for now with the software already
> packaged for Debian. Therefore I can finish my other debian packages
> later. I am pleased, that there are already that many alignment
> tools available (-:.
As far as I loked into the file
compilationDependencies.jar
it contains even more yet packaged java classes. For this purpose I
also uploaded neobio to NEW yesterday and hope it will arrive soon.
> Strap needs two small files from texlive-latex-extra. The large
> package texlive-latex-extra is 500MB in size. Therefore I decided not to
> add texlive-latex-extra to the "Depends:" because I do not want
> to waste that much disk space just for two small
> files (texshade.sty and vmargin.sty). Instead Strap checks whether
> texlive-latex-extra is installed and if not it loads the two files
> on demand from the Strap server. Is this OK? ---
In principle it is no problem to depend from texlive-latex-extra.
Please remind that at package build time you can not relay on any
internet connection because the package should build on an offline
computer.
> The automatically generated strap-base/trunk/debian/postrm lacks the
> line #!/bin/sh. Is this a bug in dh_installmenu? Removing of
> strap-base dpkg -r strap-base fails because
> /var/lib/dpkg/info/strap-base.postrm does not start with #!/bin/sh.
> After fixing /var/lib/dpkg/info/strap-base.postrm with a text editor,
> dpkg -r strap-base works.
Please read my comments about your postrm file in my mails below.
Please drop it - or explain why at all you added it. It is not clear at
all to me.
Hope this helps and in any case thanks for your work on strap packaging
Andreas.
[1] Links to my mails asking for clarification on debian-med-packaging list
http://lists.alioth.debian.org/pipermail/debian-med-packaging/2012-May/015718.html
http://lists.alioth.debian.org/pipermail/debian-med-packaging/2012-May/015719.html
http://lists.alioth.debian.org/pipermail/debian-med-packaging/2012-May/015737.html
http://lists.alioth.debian.org/pipermail/debian-med-packaging/2012-May/015738.html
[2] https://wiki.debian.org/DebianMed/MoM
--
http://fam-tille.de
Reply to: