Re: Preparing for Git repository migration

Hello, Rutherther writes: > see > https://blog.codeberg.org/new-storage-limits-on-codeberg-what-you-need-to-know.html > for news on codeberg storage usage - 750 MB for git repos per user/org. I hadn’t realized this was also per-org. I filed a request for more storage, as the blog post suggests

Re: Preparing for Git repository migration

Hi all, see https://blog.codeberg.org/new-storage-limits-on-codeberg-what-you-need-to-know.html for news on codeberg storage usage - 750 MB for git repos per user/org. This is definitely going to affect guix organization, at least long term (should probably contact Codeberg regarding larger li

Re: Preparing for Git repository migration

Arun Isaac writes: >> I’m also happy to add your account to the “owners” team; let me know >> when you have one. > > I already have an account. Here it is: https://codeberg.org/arunisaac Added, thanks!

Re: Preparing for Git repository migration

Hi Ludo, > I’m also happy to add your account to the “owners” team; let me know > when you have one. I already have an account. Here it is: https://codeberg.org/arunisaac Thanks, Arun

Re: Preparing for Git repository migration

Ludovic Courtès writes: > Hello, > > Efraim Flashner writes: > >> Can we also ask the Savannah admins to change the cgit clone URIs for >> the repos that have been moved over? > > Is it feasible? I would think that Cgit has those hardcoded, no? Looking at cgitrc(5), I think it should be possib

Re: Preparing for Git repository migration

Hello, Arun Isaac writes: >> Looking at , there’s one >> repository I forgot to mention (shame on me): mumi. >> >> Arun, should I let you migrate it? Let me know what you prefer. > > Since you're already familiar with the process, it might be easier for

Re: Preparing for Git repository migration

Hello, Efraim Flashner writes: > Can we also ask the Savannah admins to change the cgit clone URIs for > the repos that have been moved over? Is it feasible? I would think that Cgit has those hardcoded, no? Ludo’.

Re: Preparing for Git repository migration

Hi Ludo, > Looking at , there’s one > repository I forgot to mention (shame on me): mumi. > > Arun, should I let you migrate it? Let me know what you prefer. Since you're already familiar with the process, it might be easier for you to migrate the mumi

Re: Preparing for Git repository migration

On Mon, May 12, 2025 at 03:23:50PM +0200, Ludovic Courtès wrote: > Hello, > > Ludovic Courtès writes: > > > Ludovic Courtès skribis: > > > >> For now, I’m happy to start migrating the dormant repositories > >> (bootstrappable, dhcp, gnunet, videos, emacs-guix). > > > > Done. > > > >> A few days

Re: Preparing for Git repository migration

Hi, "nomike (they/them)" writes: > On 09.05.25 10:34, Noé Lopez wrote: >> That would make a ton of dead links to cgit. How about writing on the >> savannah page and README that the repository is archived with the new >> url? > > If I have a clone of the guix and still have savannah as origin aft

Re: Preparing for Git repository migration

On 09.05.25 10:34, Noé Lopez wrote: That would make a ton of dead links to cgit. How about writing on the savannah page and README that the repository is archived with the new url? If I have a clone of the guix and still have savannah as origin after the migration, I won't immediately see any

Re: Preparing for Git repository migration

Hello, Ludovic Courtès writes: > Ludovic Courtès skribis: > >> For now, I’m happy to start migrating the dormant repositories >> (bootstrappable, dhcp, gnunet, videos, emacs-guix). > > Done. > >> A few days later I can move the rest (guix-artwork, guix-cuirass, >> maintenance, guix-consensus-do

Re: Preparing for Git repository migration

Ludovic Courtès skribis: > For now, I’m happy to start migrating the dormant repositories > (bootstrappable, dhcp, gnunet, videos, emacs-guix). Done. > A few days later I can move the rest (guix-artwork, guix-cuirass, > maintenance, guix-consensus-documents). > > Chris, can you migrate data-ser

Re: Preparing for Git repository migration

Noé Lopez writes: >> An open question is the strategy to adopt for migrated repositories >> (apart from guix.git); do we: >> >> 1. remove them entirely from Savannah? >> >> 2. “fork” them by adding a commit in their Savannah copy that removes >> all files and/or amends README to state th

Re: Preparing for Git repository migration

Hi, Christopher Baines writes: > Ludovic Courtès writes: > >> Chris, can you migrate data-service, build-coordinator, nar-herder, and >> qa-frontpage whenever is convenient for you? > > Yep, I just need access, I'm cbaines on Codeberg: > https://codeberg.org/cbaines I added you to the “Owners”

Re: Preparing for Git repository migration

Ludovic Courtès writes: > Hello Guix, > > Key dates defined in GCD 002 are: > > • By June 5th, all Git repos are migrated to Codeberg; > > • On a flag day between May 21st and June 5th, guix.git is migrated > (meaning that nobody pushes to Savannah after that date). > > How about Sunday M

Re: Preparing for Git repository migration

Ludovic Courtès writes: > Chris, can you migrate data-service, build-coordinator, nar-herder, and > qa-frontpage whenever is convenient for you? Yep, I just need access, I'm cbaines on Codeberg: https://codeberg.org/cbaines > An open question is the strategy to adopt for migrated repositories >