Re: guile-gnutls copy at codeberg
Simon Josefsson <[email protected]> Fri, 11 Jul 2025 23:25:23 +0200
| Newsgroups | gmane.network.gnutls.general |
|---|---|
| Message-ID | <[email protected]> |
--===============8892627140024934637== Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature" --=-=-= Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Ludovic Court=C3=A8s <[email protected]> writes: >> https://codeberg.org/guile-gnutls/guile-gnutls > > I would support such a move. ... > IMO you have all the authority to do it! Thank you! > I would suggest migrating the project (including issues and PRs): it=E2= =80=99s > a super easy and mostly lossless process with Codeberg. I think you=E2= =80=99ll > first need to delete this repo and then click on =E2=80=9C+=E2=80=9D in t= he blue banner > at the top and then =E2=80=9CNew migration=E2=80=9D. Done! Now https://gitlab.com/gnutls/guile is a read-only archived project. I'll try to push out a new release to put a flag down that guile-gnutls is now on codeberg and that we are open for business there. >> - GitLab Pipelines - this is a very important QA tool and I wouldn't >> want to release anything without having all those tests. So whatever >> we do, the GitLab CI/CD will be important for some time still. I >> don't speak Forgejo CI/CD but will try to learn, but it appears far >> behind GitLab CI/CD feature-wise. I don't see any problem having a >> GitLab read-only mirror project for CI/CD purposes, I do that for some >> other projects without GitLab presence. > > Yeah, that I don=E2=80=99t know. There=E2=80=99s the integrated Woodpeck= er CI but I=E2=80=99ve > never used it. I've setup a read-only GitLab CI/CD project: https://gitlab.com/gsasl/guile-gnutls/-/pipelines For as long as we have the .gitlab-ci.yml file in the guile-gnutls project, people can push the codenerh repository to their personal gitlab space and CI/CD will just work there. I wonder if codeberg merge requests can be thought to point or use GitLab CI/CD status, but I don't think this is important. >> - GitLab release pages - I've been using this feature as a learning >> excercise, but I'm not sure how important it is. I guess codeberg has >> something similar. I find these pages rather ugly, and prefer old >> school HTTPS/FTP publication with stable URLs and a mirror network. >> Savannah and ftp.gnu.org provides this, and we can continue use that >> (or not). > > I would just use Git tags these days, but then that rules out > complicated pre-processing =C3=A0 la Gnulib. The migration migrated the release page too. But I'm not sure there is any value in these? We still push tarballs to ftp.gnu.org. We put a copy of relevant gnulib files in guile-gnutls's git, so no gnulib is necessary. But adding autoconf+automake as a build dependency for everyone may not be nice (is guile-gnutls part of the guix bootstrap? is it before autoconf/automake?), so maybe there is some utility in publishing curated tarballs for some time still. >> Btw, I pushed a copy of GitLab 'master' branch to a 'main' branch on >> Codeberg since it seemed like a nice time to change branch name too. > > Agreed. The migration re-created the master branch, but I pushed it as main now. I'm not sure we should remove the master branch? We can just stop push to it. /Simon --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQNoBAEWCgMQFiEEo8ychwudMQq61M8vUXIrCP5HRaIFAmhxgUMUHHNpbW9uQGpv c2Vmc3Nvbi5vcmfCHCYAmDMEXJLOtBYJKwYBBAHaRw8BAQdACIcrZIvhrxDBkK9f V+QlTmXxo2naObDuGtw58YaxlOu0JVNpbW9uIEpvc2Vmc3NvbiA8c2ltb25Aam9z ZWZzc29uLm9yZz6IlgQTFggAPgIbAwULCQgHAgYVCAkKCwIEFgIDAQIeAQIXgBYh BLHSvRN1vst4TPT4xNc89jjFPAa+BQJn0XQkBQkNZGbwAAoJENc89jjFPAa+BtIA /iR73CfBurG9y8pASh3cbGOMHpDZfMAtosu6jbpO69GHAP4p7l57d+iVty2VQMsx +3TCSAvZkpr4P/FuTzZ8JZe8BrgzBFySz4EWCSsGAQQB2kcPAQEHQOxTCIOaeXAx I2hIX4HK9bQTpNVei708oNr1Klm8qCGKiPUEGBYIACYCGwIWIQSx0r0Tdb7LeEz0 +MTXPPY4xTwGvgUCZ9F0SgUJDWRmSQCBdiAEGRYIAB0WIQSjzJyHC50xCrrUzy9R cisI/kdFogUCXJLPgQAKCRBRcisI/kdFoqdMAQCgH45aseZgIrwKOvUOA9QfsmeE 8GZHYNuFHmM9FEQS6AD6A4x5aYvoY6lo98pgtw2HPDhmcCXFItjXCrV4A0GmJA4J ENc89jjFPAa+wUUBAO64fbZek6FPlRK0DrlWsrjCXuLi6PUxyzCAY6lG2nhUAQC6 qobB9mkZlZ0qihy1x4JRtflqFcqqT9n7iUZkCDIiDbg4BFySz2oSCisGAQQBl1UB BQEBB0AxlRumDW6nZY7A+VCfek9VpEx6PJmdJyYPt3lNHMd6HAMBCAeIfgQYFggA JgIbDBYhBLHSvRN1vst4TPT4xNc89jjFPAa+BQJn0XTSBQkNZGboAAoJENc89jjF PAa+0M0BAPPRq73kLnHYNDMniVBOzUdi2XeF32idjEWWfjvyIJUOAP4wZ+ALxIeh is3Uw2BzGZE6ttXQ2Q+DeCJO3TPpIqaXDAAKCRBRcisI/kdFojGsAQCZOhvYTs0/ gf+WTNmU++Jdh+TtBaxWEnbL8xhTfgI0TQD/c/0+91kn4pZVlUtwad29JWsPxkZZ 4/zd2H6fx0A/hgc= =9wIU -----END PGP SIGNATURE----- --=-=-=-- --===============8892627140024934637== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Gnutls-help mailing list [email protected] http://lists.gnupg.org/mailman/listinfo/gnutls-help --===============8892627140024934637==--