"Dr. Burkard Lutz" <b.l...@online.de> writes:
> The actual version ("0.34") is the first which contains all desired
> functions, and after extensive testing I hope that there are only
> minor bugs left.
Thanks for explaining.
> Therfore I decided to make an attempt for publishing it on debian.
> Should I rename it to "0.10"?
No. 0.34 is fine. I just wanted to understand the state of things
> Now you can see the project under the following address:
> https://gitlab.com/b.lutz1/galvani I changed the group name to
> "galvani" but the path to the project remained the same.
OK. Excellent. A distro-agnostic location to host the upstream version
control is desirable. You do your development there, and when you're
ready to release, you should make a tag. Currently there aren't any:
https://gitlab.com/b.lutz1/galvani/-/tags
To indicate which commit, exactly is being released, you should make a
tag called 'v0.34' or '0.34' or something like that.
Once you make a tab, gitlab will create a tarball with your sources at
that tag. This is your "release tarball".
The debianization repo should live on salsa. Generally you have 3
branches:
- "pristine-tar" contains the release tarballs
- "upstream" contains the unpacked upstream sources. Each upstream
release is one commit
- "master" branches off "upstream"; contains the debianization
This isn't the "best" way to do it, but it's how most packages are set
up. Look around on salsa; you'll see this layout everywhere. The "gbp"
tool is useful to manipulate the debianized repo. In particularly, you
can import new release tarballs with
gbp import-orig --pristine-tar whatever.tar.gz
The upstream release tarball location is encoded in the debian/watch
file. The "uscan" tool is used to interpret this file, and to see if new
release tarballs are available, and to download them. In order for this
to work, debian/watch has to be written properly. This is described here:
https://wiki.debian.org/debian/watch
It looks like gitlab keeps changing their file layout, so you'll need to
play with it until
uscan --verbose --report-status
sees your tarball.
> I saw that you are a member of debian-science-team. Did you have some
> time so far to have a look at my project? Do you think debian-science-
> team could be interested in that project?
Yes. Joining a team is what you usually want. It doesn't mean that
somebody else will fix all your problems (you're still the primary
maintainer), but it's a signal that if a team member wants to fix stuff
while you're not available, you're ok with that.
debian-science is a fine place for this. Follow the policy:
https://science-team.pages.debian.net/policy/
Mostly it means that you put your debianization into their subdirectory
on salsa:
https://salsa.debian.org/science-team/
And that you set the team to be the Maintainer and yourself as the
Uploader. Read the policy.
> I'm looking for a sponsor to publish the project on debian. Can you
> perhaps help me in that issue?
Sure. Try to make a debianized repository as I described above, and let
me know when you're done. Or if you need help.
