Andreas,
Here is the second attempt. :-)
New Git Repository
----------------------------
After reading more carefully the instructions in:
https://honk.sigxcpu.org/piki/development/debian_packages_in_git/
https://wiki.debian.org/PackagingWithGit
I have restructured the Git repository from scratch.
It is now at:
git+ssh://git.debian.org/git/debian-med/vista-foia.git
Browse Link:
http://anonscm.debian.org/gitweb/?p=debian-med/vista-foia.git
Build Process
---------------------
The following commands, work for me to replicate the build in a fresh
directory:
git clone git://git.debian.org/git/debian-med/vista-foia.git
cd vista-foia
git archive --format tar.gz
--output=../vista-foia_0.20130405-1.debian.tar.gz master debian
git archive --format tar.gz
--output=../vista-foia_0.20130405.orig.tar.gz upstream
git-buildpackage
It's main dependency is the fis-gtm package.
The cloned Git repository takes 3.3 Gb in disk.
Once the build concludes, I can do:
cd ..
ls
and get to see the following files:
vista-foia-0.20130405_0.20130405-1_amd64.deb
vista-foia_0.20130405-1_all.deb
vista-foia_0.20130405-1_amd64.build
vista-foia_0.20130405-1_amd64.changes
vista-foia_0.20130405-1.debian.tar.gz
vista-foia_0.20130405-1.dsc
vista-foia_0.20130405.orig.tar.gz
and at that level, I can install the package with:
sudo dpkg -i vista-foia-0.20130405_0.20130405-1_amd64.deb
and the meta-package with:
sudo dpkg -i vista-foia_0.20130405-1_all.deb
This installs vista-foia in the directory
/usr/share/vista-foia/V-0.20130405/
The bulk of the package is in the "r" routines directory:
/usr/share/vista-foia/V-0.20130405/r
that contains 27543 MUMPS files
and the "globals" directory, that host the basic database:
/usr/share/vista-foia/V-0.20130405/g
with files
1.2G database.dat
1.5K database.gld
Pristine Tar:
-----------------
When building the repository, I first attempted to import the source
tarball with the --pristine-tar option, as recommended here:
https://wiki.debian.org/PackagingWithGit#pristine-tar
but got the following error message:
gbp:info: No git repository found, creating one.
gbp:info: Tag upstream/0.20130405 not found, importing Upstream tarball
xdelta: warning: no matches found in from file, patch will apply without it
error: excessively large binary delta for
/tmp/pristine-tar.ETnVfcsL8q/origtarball
(Please consider filing a bug report.)
pristine-tar: failed to generate delta
gbp:error: Couldn't commit to 'pristine-tar' with upstream 'upstream':
/usr/bin/pristine-tar returned 1
The VistA-M tarball is 407Mb. This is probably the reason.
So, fell back to importing with the simpler command:
gbp import-dsc vista-foia_0.20130405-1.dsc
This was done, starting from a pre-built package,
as recommended here:
https://wiki.debian.org/PackagingWithGit#Getting_started
So, the repository currently doesn't have a "pristine-tar" branch.
The upstream sources are in the "upstream" branch,
and it is the composition of the source tree from the
VistA repository:
https://github.com/OSEHRA/VistA
that contains CMake + Python insfrastructure,
and the Vista-M repository:
https://github.com/OSEHRA/VistA-M
that contains the actual MUMPS source routines and globals
of VistA proper.
Version Number
-----------------------
Following your comments, I simplified the version number to just use
vista-foia 0.20130405
As you pointed out, the VistA-M source tree is much bigger than the
CMake+Python infrastructure in the VistA source tree. So using the
version number of the biggest tree, makes sense.
I'll be very curious to hear if the build of this restructured tree can
be replicated.
Tagging
------------
I'm now looking into tagging the upstream branch, which seems to be
needed for git-buildpackage to work out of the box, without requiring
that we manually create the tar.gz source files from the upstream branch.
(... advice will be welcome here....).
Follow Up Question
----------------------------
Should I delete at some point the "vista" Git repository in Alioth ?
Now that this is in the "vista-foia" git repository that actually
matches the package name.
I have not come across a process for removing Git repositories
from Alioth. ( I would suspect that there is a web page that I should
read before attempting such thing). Any guidance on what to do
about it will be greatly appreciated.
Best Regards,
Luis
