Hello everyone,
We are ready to start a closed beta for tag2upload.
For the first stage, these are the kind of participants we want:
- Individual maintainer or small team, where everyone is on board.
DDs and DMs are equally welcome.
- (At least some of) the packages are uploaded relatively often.
- Happy to perform an occasional upload that only touches d/changelog,
for testing.
- Happy to risk breakage or lossage, including possible broken uploads.
We don't expect broken uploads, but one point of the beta is to
discover any problems of that kind.
- You already use dgit to upload.
This is not because using tag2upload requires using dgit.
There are two reasons for this limitation at this stage:
There are some complications that will be avoided in git trees that
are already known to work fine with dgit.
On a social/pedagogical level, users of dgit will already be familiar
with some of our terminology etc.
- Happy to tolerate the history of your package on dgit-repos diverging
a bit from what's on salsa.
(Interleaving dgit pushes and tag2upload will add some merges.)
- Willing to tolerate rough edges!
Just to note, we will not ask you to use tag2upload for every upload of
the packages for which it is enabled. Uploads done in the usual way can freely be done too.
If you'd like to sign up, write to us at <dgit-owner@debian.org>,
specifying a list of your packages for which we should enable tag2upload processing, and confirming you have your co-maintainers agreement.
Or just reply to dgit-owner@ or on debian-devel if you have some
questions first.
For more information, see <https://wiki.debian.org/tag2upload>.
For the tag2upload Delegates,
- (At least some of) the packages are uploaded relatively often.
- You already use dgit to upload.
If you'd like to sign up, write to us at <dgit-owner@debian.org>, specifying a list of your packages for which we should enable tag2upload processing, and confirming you have your co-maintainers agreement.
Hi Sean,
Quoting Sean Whitton (2025-03-15 02:49:58)
- (At least some of) the packages are uploaded relatively often.
with the upcoming freeze, I do not expect too many uploads to be necessary (but
can be done if needed). But is that a problem?
- You already use dgit to upload.
The wiki page says to use git-debpush from src:dgit. Which version of git-debpush is new enough? Does the version from Bookworm work?
If you'd like to sign up, write to us at <dgit-owner@debian.org>, specifying >> a list of your packages for which we should enable tag2upload processing, and
confirming you have your co-maintainers agreement.
No co-maintainers and happy to try out tag2upload for: box64, ldraw-parts-free,
pico-sdk, picotool, vcmi, img2pdf, plakativ
Co-maintainer (Jochen) agrees: sbuild
Yay!
I'm happy to beta-test this. Exactly what features are required from
dgit to be able to use tag2upload? Maybe I can offer myself to vet the process as a package maintainer that only minimally uses dgit, assuming
that I can manage to install and get dgit to work on my machine. A
simple 'dpkg -i' of 12.9 worked now, and I was able to run 'dgit build'
in my existing libntlm git clone. I haven't been using dgit before
this, but maybe this is sufficient to count me as a dgit user.
Packages (for example): libntlm, cppi, git2cl, guile-fibers
Sean Whitton <spwhitton@spwhitton.name> writes:
That should be enough! If you were able to do at least one upload using
'dgit push-source' for each package to confirm everything is okay, that
would be great.
I'll try. I got a SSH push warning on first use -- how would I verify
this host SSH key? What's the risk uploaders getting MITM'ed here?
The authenticity of host 'push.dgit.debian.org (2001:41b8:202:deb::311:78)' can't be established.
ED25519 key fingerprint is SHA256:O4i2PPFELuj49wYZSwLt+a2r356sB19KMCFhrUKkYiM.
This key is not known by any other names.
Are you sure you want to continue connecting (yes/no/[fingerprint])?
That should be enough! If you were able to do at least one upload using 'dgit push-source' for each package to confirm everything is okay, that
would be great.
Sean Whitton <spwhitton@spwhitton.name> writes:
Packages (for example): libntlm, cppi, git2cl, guile-fibers
That should be enough! If you were able to do at least one upload using
'dgit push-source' for each package to confirm everything is okay, that
would be great.
Should be done for libntlm, git2cl and guile-fibers now. Dgit didn't
like cppi, doesn't it handle bare-debian/-style packaging? See: https://salsa.debian.org/debian/cppi
I used this command:
dgit --gbp push-source --deliberately-not-fast-forward
Based on my understanding of:
https://manpages.debian.org/testing/dgit/dgit-maint-gbp.7.en.html#UPLOADING
I'm doing this on a laptop running Trisquel aramo (Ubuntu 22.04 clone)
with plenty of packages installed from Guix, including GnuPG, git and
even dpkg. I was positively surprised dgit didn't blow up, good job!
Should be done for libntlm, git2cl and guile-fibers now. Dgit didn't
like cppi, doesn't it handle bare-debian/-style packaging? See:
https://salsa.debian.org/debian/cppi
It has --quilt=baredebian+git and --quilt=baredebian+tarball for this
-- please give one of those a try.
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 546 |
| Nodes: | 16 (2 / 14) |
| Uptime: | 154:55:40 |
| Calls: | 10,383 |
| Files: | 14,054 |
| Messages: | 6,417,848 |