Re: Trying out Codeberg

Hi, On Thu, 13 Mar 2025 at 10:36, Adrien 'neox' Bourmault wrote: > the default CI recipes/code depends on > docker.io images Well, Cuirass (one CI tool used by the Guix project) is able to work with Forgejo. > nodeJS and npm. Also, the javascript

Re: Trying out Codeberg

Hello, Adrien 'neox' Bourmault writes: [...] > If I can help by sharing Libre en Communs' experience, I'll be very > happy to do so. I'll start here by explaining a bit what I have in > mind. > > Libre en Communs needed a forge software to be able to provide means > for people (both very techni

Re: Trying out Codeberg

Le vendredi 07 mars 2025 à 02:53 +0100, Denis 'GNUtoo' Carikli a écrit : > On Thu, 06 Mar 2025 10:10:03 +0900 > Maxim Cournoyer wrote: > > > > Is Docker the only current solution for runners in the CI? > This is my understanding from my discussion with neox. > > > > Having a less generic solutio

Re: Trying out Codeberg

On Thu, 06 Mar 2025 10:10:03 +0900 Maxim Cournoyer wrote: > > Is Docker the only current solution for runners in the CI? This is my understanding from my discussion with neox. > > Having a less generic solution might be better though, like using > > 'guix' or 'debootstrap' to build containers wi

Re: Trying out Codeberg

Maxim Cournoyer writes: Hi Denis, Denis 'GNUtoo' Carikli writes: On Sat, 22 Feb 2025 22:35:21 +0900 Maxim Cournoyer wrote: [0] https://forge.a-lec.org/ (self-hosted in France by a nonprofit! [1]) [1] https://www.a-lec.org/ Personally I have a private repository on forge.a-lec.org that

Re: Trying out Codeberg

Hi Denis, Denis 'GNUtoo' Carikli writes: > On Sat, 22 Feb 2025 22:35:21 +0900 > Maxim Cournoyer wrote: >> [0] https://forge.a-lec.org/ (self-hosted in France by a nonprofit! [1]) >> [1] https://www.a-lec.org/ > Personally I have a private repository on forge.a-lec.org that I use > for Q/A for

Re: Trying out Codeberg

On Sat, 22 Feb 2025 22:35:21 +0900 Maxim Cournoyer wrote: > [0] https://forge.a-lec.org/ (self-hosted in France by a nonprofit! [1]) > [1] https://www.a-lec.org/ Personally I have a private repository on forge.a-lec.org that I use for Q/A for a project I participate in, and so I push and pull re

Re: Trying out Codeberg

Greg Hogan writes: [...] > git push civodul HEAD:refs/for/master/$(git branch --show-current) \ > -o title="$(git log -1 --pretty=format:'%s')" \ > -o description="$(git log -1 --pretty=format:'%b' | awk 1 ORS='')" > > [0] https://codeberg.org/civodul/guix/pulls/12 > For Emacs users, maybe

Re: Trying out Codeberg

Am 27.02.25 um 15:49 schrieb Greg Hogan: git push civodul HEAD:refs/for/master/$(git branch --show-current) \ -o title="$(git log -1 --pretty=format:'%s')" \ -o description="$(git log -1 --pretty=format:'%b' | awk 1 ORS='')" Untested: The third code-snippet in

Re: Trying out Codeberg

On Fri, Feb 21, 2025 at 3:45 AM Alexis Simon wrote: > > Hello, > > For those interested I tried the AGit workflow [1] on guix-science and > it worked nicely to start a PR from the command line without forking > [2]. Not sure it was mentioned before. I ran the following for a single commit pull re

Re: Posting GCD #002? (was Re: Trying out Codeberg)

GCD 002 is officially submitted now! :-) https://issues.guix.gnu.org/76503 Ludo’.

Re: Posting GCD #002? (was Re: Trying out Codeberg)

Hi, Simon Tournier skribis: > On Sun, 16 Feb 2025 at 17:41, Ludovic Courtès wrote: > >> I’ll be formally posting GCD #002 soon (“Migrating repositories, issues, >> and patches to Codeberg”) > > As discussed elsewhere [1], we need a GCD process in order to amend > Accepted GCDs without running a

Posting GCD #002? (was Re: Trying out Codeberg)

Hi Ludo, On Sun, 16 Feb 2025 at 17:41, Ludovic Courtès wrote: > I’ll be formally posting GCD #002 soon (“Migrating repositories, issues, > and patches to Codeberg”) As discussed elsewhere [1], we need a GCD process in order to amend Accepted GCDs without running a complete dance. My question i

Re: Trying out Codeberg

Hi Simon, Simon Tournier writes: > Hi Efraim, > > On Fri, 21 Feb 2025 at 09:01, Efraim Flashner wrote: > >>What parts of codeberg do you find slow? Is it loading the >> website or navigating between different pages or a different workflow? > > Somehow loading the website and then n

Re: Trying out Codeberg

Hi Efraim, On Fri, 21 Feb 2025 at 09:01, Efraim Flashner wrote: >What parts of codeberg do you find slow? Is it loading the > website or navigating between different pages or a different workflow? Somehow loading the website and then navigate between different pages. But that’s not

Re: Trying out Codeberg

Hello, For those interested I tried the AGit workflow [1] on guix-science and it worked nicely to start a PR from the command line without forking [2]. Not sure it was mentioned before. Alexis [1] https://codeberg.org/forgejo/docs/src/branch/v7.0/docs/user/agit-support.md [2] https://codeb

Re: Trying out Codeberg

Hi, On Tue, 18 Feb 2025 at 13:39, Rostislav Svoboda wrote: > People, I find codeberg to be slow :-/ It’s “slow“ on my side too but not slower than gitlab.com or gitlab.inria.fr or etc. :-) My main annoyance isn’t “slow” but I cannot locally cache. It’s impracticable when you have a poor netw

Re: Trying out Codeberg

Hi Olivier, On Sun, 16 Feb 2025 at 13:51, Olivier Dion wrote: > I have not follow the entire thread about this migration. > > Will the mail-patch workflow still available? The mail-patch workflow is still available. It will be available until a GCD changing is accepted. And such GCD will expl

Re: Trying out Codeberg

Hi Ludo, On Sun, 16 Feb 2025 at 17:41, Ludovic Courtès wrote: >perhaps even before GCD #001 is committed > (not sure what’s going on here :-)) Probably because I’m lagging… Well, now it’s ready from my side. :-) Feel free to tweak, if it’s not clear enough. Cheer

Re: Trying out Codeberg

People, I find codeberg to be slow :-/ Cheers, Bost

Re: Trying out Codeberg

I have not follow the entire thread about this migration. Will the mail-patch workflow still available? On Sun, 16 Feb 2025, Ludovic Courtès wrote: > Hello Guix, > > I’ll be formally posting GCD #002 soon (“Migrating repositories, issues, > and patches to Codeberg”), perhaps even before GCD #0

Re: Trying out Codeberg

Hello Ludo' > 1. try and look at pull requests, but only for trivial packaging > changes (I will close pull requests that don’t fit the bill); Please pull this one: https://codeberg.org/civodul/guix/pulls/3 That's an ideal candidate. It's just a silly Emacs package that "displays a buffer