Re: HTCondor Uploads
Hi Tim,
On 2024-05-24 17:10:49, Tim Theisen wrote:
Now that I have it, what is the procedure for getting HTCondor uploaded
into Debian?
once the package is ready for upload, I usually perform the following steps:
1. Prepare the debian/changelog file for upload
If you use git-buildpackage, the command
gbp dch --release --commit
might be helpful to get a good starting point. Depending on your taste,
you might want to polish the entry generated by "gbp dch". If you don't
use git-buildpackage, it might be worth checking the functionality of
"dch" (see dch(1)).
Make sure you target the right distribution. "Normal" package updates
are usually uploaded to "unstable" (see [0] for details). The upload
urgency is usually "medium" (see [1]).
Also check whether the upload closes open bugs. If it does, the archive
maintenance software can close them automatically for you by adding
"closes" statements in the changelog (see [2] for the precise syntax).
This way the bug tracker also automatically learns about the package
version fixing the bug.
2. Push changes to salsa:
git push origin : --follow-tags
3. Wait for potential issues spotted by the salsa CI. If there are
issues which slipped through your local checks, address them.
4. Otherwise build the source package.
5. Add the required signatures:
debsign condor_<version>_source.changes
6. Upload the package (I use dput-ng for this):
dput condor_<version>_source.changes
7. Tag the Debian release. Again git-buildpackage might be helpful:
gbp tag --sign-tags
8. Push Debian release tag to salsa:
git push origin : --follow-tags
I hope this helps.
Best regards,
Peter
[0]
https://www.debian.org/doc/manuals/developers-reference/resources.en.html#distributions
[1]
https://www.debian.org/doc/manuals/developers-reference/best-pkging-practices.en.html#selecting-the-upload-urgency
[2]
https://www.debian.org/doc/manuals/developers-reference/pkgs.en.html#when-bugs-are-closed-by-new-uploads
Reply to: