Re: Connecting those interested in getting GT.M into the Debian repositories
On Sun, Sep 05, 2010 at 03:35:27PM -0400, Alan O'Neill wrote:
> The package I'm ready to submit installs the 32-bit version of GT.M
> 5.4.000A. Additionally, I'll be able to build a package for the 64-bit
Are there different source tarballs for 32 and 64 bit? I'm just asking
because usually in Debian we try to build the binary packages for
different architectures (i386, amd64 and others) from *one* single
source package. The build provess might differ in some options but
usually there is one source package.
> I could also build packages for earlier versions, if desired,
I don't think we should spend to much time in the past. I guess we will
have enough work to do with present and future releases.
> and as new versions come out, I could put those together as well. I've
> walked a bit of the directory structure under
> http://svn.debian.org/viewsvn/debian-med/trunk/packages/, and it appears
> that the next level is a package name followed immediately by "trunk"
> and the "debian" directory (e.g.,
> .../trunk/packages/fastdnaml/trunk/debian). So should I store things at
> or is it preferable to store it something like
> or perhaps something else?
I would go with .../trunk/packages/fis-gtm in any case. The version
number will be available in the debian/changelog file and does not
belong to the directory structure. If you answer my question above in a
way that (at least for the moment) there is no chance to build from one
single source binaries for different architectures, we could perhaps
try something like
(but not 32 and 64, because there are other architectures in Debian
which are 32 or 64 and which you probably do not have in mind). My
recommendation would be to try a source layout which fits building of
> My second question is about how to issue the actual commands to submit
> the package. For the purpose of this e-mail, I'll guess that I'll be
> storing things under .../trunk/packages/fis-gtm/54000a/32/trunk. On my
> local server, I issued the following command to create a test area.
> svnadmin create /home/alan/debian-med
You do not need svnadmin. This is for the administration on the svn
*server*. (BTW, if you are more comfortable with Git, you could also
use Git - if not for a beginner SVN might be a bit more comfortable -
the Git experts might like to correct me ...)
> Then I issued this next command to import my files
> svn import <location on my server of files to import>
It seems that your SVN book makes things more complex than needed.
The Debian Med policy document has some simple commands listed at
So a simple:
svn co svn+ssh://firstname.lastname@example.org/svn/debian-med/trunk/packages
should have provided you with all the stuff you need. If you are
scared by the lot of stuff which might simply steal your bandwidth
I just created a directroy fis-gtm which provides a fresh workspace
for your purpose without checking out everything:
svn co svn+ssh://email@example.com/svn/debian-med/trunk/packages/fis-gtm
> At this point it seems that svn knows about my files. And I can even
> checkout the files with
> svn checkout
> But all this stuff seems to work because the files are already on my
> server. Of course, my goal is to put the files onto the server where
> the actual debian-med lives. So I seem to be approaching things from
> the wrong end. Can you give me a hint as to how the svn command(s)
> should be structured to copy the files from my server to debian-med?
Forget the book (not honestly - but to get start working quickly), put
your files in the fis-gtm directory you got above and then do
svn add <yourfiles>
> Thanks again!
Hope this helps - if not do not hesitate to keep on asking.