Re: ITP strap-base - Some questions
Hi Andreas, Hi Charles,
You mean svn commit -m "some text" ? I completely forgot about
this. I had to explore svn since I have not worked with svn before. I
become more and more confident with the build system but I still encounter
some minor problems.
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.
---
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
---
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.
---
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 (-:.
---
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? ---
---
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.
Best regards
Christoph
Reply to: