Re: emacs-guix (upstream) needs more love: a survey of repositories, homepage and issues

2022-06-03 Thread Théo Maxime Tyburn
Hi all, > Would you be willing to coordinate work on Emacs-Guix for some time? > If so, I’m in favor of granting you commit access so you can first push > these four commits, and eventually apply patches that are submitted or > fix bugs here and there. > > If Giovanni or Théo wants to do that, tha

Re: Move switch-symlinks to (guix build utils)

2022-06-03 Thread bokr
Hi, I am not expert on kernel link internals, but if you need/prefer atomic change to a specific link, does my log [1] below suggest a way? On +2022-06-03 21:30:39 +0200, Ludovic Courtès wrote: > Hi, > > Maxime Devos skribis: > > >, Maybe replace > > > >(symlink target pivot) > > > > by (s

Re: The Little Guixer

2022-06-03 Thread Yasuaki Kudo
Let's do this together, all of us, and publish in complete Free Software format compiled by Guix 😄😄 > On Jun 4, 2022, at 01:41, Ludovic Courtès wrote: > > Sounds like a great idea; feel inclined to do so? :-) > > Ludo’.

Feed on specific topic (public-inbox?)

2022-06-03 Thread zimoun
Hi, On Thu, 02 Jun 2022 at 21:35, Luis Felipe wrote: > As for reviewing patches or just taking a look at reported issues > against parts of Guix one is interested, it would be easier if there > were some kind of subscription system. Say, I'd like to subscribe to > issues on Python packages, Span

Re: Feed on specific topic (public-inbox?)

2022-06-03 Thread zimoun
On Fri, 03 Jun 2022 at 10:22, zimoun wrote: > Note that recent ’public-inbox’ comes from with the tool ’lei’. This > tool ’lei’ allows to query a public-inbox server and then fetch some > filtered messages to use it locally. Currently, the Guix package is at > 1.6 and it requires an update at 1.

Re: proposal: guix-ment...@gnu.org list/alias

2022-06-03 Thread jbranso
June 2, 2022 4:00 AM, "Ricardo Wurmus" wrote: > zimoun writes: > >> Ah sorry, I overcomplicate the discussion. :-) > > Hah, no worries! It’s worth discussing this before we implement a > workflow that ends up being *more* confusing than the status quo. > >> To me, it could be nice to have a t

Re: proposal: guix-ment...@gnu.org list/alias

2022-06-03 Thread Liliana Marie Prikler
Am Mittwoch, dem 01.06.2022 um 22:17 +0200 schrieb Ricardo Wurmus: > Hi, > > to help new contributors get their first contribution into Guix I > think it would be good to do this: > > 1. create a new private mailing list or mailing alias > guix-ment...@gnu.org > > 2. ask for experienced Guix con

Re: proposal: guix-ment...@gnu.org list/alias

2022-06-03 Thread Ricardo Wurmus
Liliana Marie Prikler writes: > As a specific measure against potential abuse as well as a way of > helping out newcomers, what if instead of making new contributors CC > guix-mentors, we made it so that forwarding to guix-mentors is handled > by the spam filter? That is once it's established

Re: proposal: guix-ment...@gnu.org list/alias

2022-06-03 Thread Tobias Geerinckx-Rice
Hi Lily, Liliana Marie Prikler 写道: That is once it's established that a new contribution is actually a contribution, the patch is forwarded separately to guix-mentors (along with reply-to: for the original bug etc. set up in a way that's useful to mentors), claiming takes place, and so on.

Re: proposal: guix-ment...@gnu.org list/alias

2022-06-03 Thread Liliana Marie Prikler
Hi Tobias, Am Freitag, dem 03.06.2022 um 13:21 +0200 schrieb Tobias Geerinckx- Rice: > Hi Lily, > > Liliana Marie Prikler 写道: > > That is once it's established that a new > > contribution is actually a contribution, the patch is forwarded > > separately to guix-mentors (along with reply-to: for t

Re: proposal: guix-ment...@gnu.org list/alias

2022-06-03 Thread Tobias Geerinckx-Rice
Liliana Marie Prikler 写道: So first things first, this would only apply to guix-patches (I believe), since that is where "contributions" as in "patches that need review" are sent to. My proposal is roughly as follows: 1. When a new contributor sends a mail to guix-patches, the mail gets added

Re: proposal: guix-ment...@gnu.org list/alias

2022-06-03 Thread zimoun
Hi, On Fri, 03 Jun 2022 at 13:48, Liliana Marie Prikler wrote: > 1. When a new contributor sends a mail to guix-patches, the mail gets > added to a manual approval queue. (This currently happens) > 2. A human operator manually approves of the patch as in flags it as > "Not spam" (This currently

Re: Move switch-symlinks to (guix build utils)

2022-06-03 Thread Ludovic Courtès
Hi, Maxime Devos skribis: > Arun Isaac schreef op do 02-06-2022 om 20:36 [+0530]: >> Hi Maxime, >> >> > To avoid a world-rebuild, you could for now make a module (guix build >> > symlinks) or such?  An alternative is (gnu build activation), but then >> > some (guix ...) modules would depend on

Re: Release v1.4?

2022-06-03 Thread Ludovic Courtès
Hello! zimoun skribis: > Schedule a release is the occasion to tackle some not-so-fun tasks as > merging the ’staging’ branch [1], many upgrades as Haskell [2] or Julia, > etc. Thanks for the heads-up! I think merging ‘staging’ should be top-priority. People are welcome to upgrade/reconfigure

Re: The Little Guixer

2022-06-03 Thread Ludovic Courtès
Sounds like a great idea; feel inclined to do so? :-) Ludo’.

Re: Move switch-symlinks to (guix build utils)

2022-06-03 Thread Maxime Devos
Ludovic Courtès schreef op vr 03-06-2022 om 18:38 [+0200]: > That’s EACCES? It's EEXIST. > > If we move it to (guix build utils), I'd prefer the bug to be addressed > > first. > > Yes, better be cautious before “setting it in stone”.  Do you have a fix > in mind? Maybe replace (symlink tar

Re: Move switch-symlinks to (guix build utils)

2022-06-03 Thread Ludovic Courtès
Hi, Maxime Devos skribis: > Maybe replace > >(symlink target pivot) > > by (symlink/remove-old target pivot) > > where > > (define (symlink/remove-old target link) > "Make a symbolic link named LINK pointing to TARGET. > If LINK already exists, it will be removed first. > This is not an at

Re: Move switch-symlinks to (guix build utils)

2022-06-03 Thread Ludovic Courtès
Hi, Maxime Devos skribis: > Maybe replace > >(symlink target pivot) > > by (symlink/remove-old target pivot) > > where > > (define (symlink/remove-old target link) > "Make a symbolic link named LINK pointing to TARGET. > If LINK already exists, it will be removed first. > This is not an at

Re: On commit access, patch review, and remaining healthy

2022-06-03 Thread Ludovic Courtès
Hi, Brian Cully skribis: > Ludovic Courtès writes: > >> If you are using Emacs, does debbugs.el have >> shortcomings that make it a problem to review patches? To be clear, the question was directed primarily at current committers. > 1) It’d be nice if ‘M-x debbug-guix’ existed. I (bri

Re: On commit access, patch review, and remaining healthy

2022-06-03 Thread Ludovic Courtès
Hi, Pier-Hugues Pellerin skribis: > As a new-new Guix user, I did find the review process or the time it > takes really long. > Maybe I've tackle too complex updates[0], I don't know but I don't > have a clear path how to push it. Yeah. :-/ The long delays are mostly due to the lack of review

Re: proposal: guix-ment...@gnu.org list/alias

2022-06-03 Thread Ludovic Courtès
Hey! Ricardo Wurmus skribis: > I’d still want to have the patches hit guix-patches and the changes made > by a mentor detailed there. guix-mentors is meant primarily as a > coordination space for mentors — it’s how new contributors get a > personal mentor for the journey from raw contribution t

Re: proposal: guix-ment...@gnu.org list/alias

2022-06-03 Thread Ricardo Wurmus
Ludovic Courtès writes: > Hey! > > Ricardo Wurmus skribis: > >> I’d still want to have the patches hit guix-patches and the changes made >> by a mentor detailed there. guix-mentors is meant primarily as a >> coordination space for mentors — it’s how new contributors get a >> personal mentor f

Re: On commit access, patch review, and remaining healthy

2022-06-03 Thread Ricardo Wurmus
Hi Ludo, > Interesting. Since I already used Gnus before, I didn’t have much to > learn when I started using debbugs.el. > > I know some people here use debbugs.el with other email clients like > mu4e, so perhaps they can comment? We could add guidance in the > manual. Since some time mu4e us