Re: Jumping the queue: merge r-team before python-team?

Hi Ricardo, On Fri, Apr 11 2025, Ricardo Wurmus wrote: > There has now been a new R release while the branch has been waiting Upstream will always do as they please. To us, it's more important what's in Guix. Your branch should be merged now (and before you update R) after our new branch merge

Re: Jumping the queue: merge r-team before python-team?

Am Fri, Apr 11, 2025 at 06:35:35AM -0700 schrieb Felix Lechner: > Your branch should be merged now (and before you update R) after our new > branch merge coordinator, Andreas Enge, signs off. No, no, I have never signed on that role. In particular, I am here only to push my own branches. :) So fa

Re: Jumping the queue: merge r-team before python-team?

Ludovic Courtès writes: > Greg Hogan skribis: > >> I'd rather have some team make progress than no one, and the only way >> to dig ourselves out of this hole is to be more assertive as Ricardo >> has been here. Let everyone else follow his lead soon after. > > Yes. I think it’s good that qa.gui

Re: Jumping the queue: merge r-team before python-team?

Am Fri, Apr 11, 2025 at 04:55:27PM +0200 schrieb Ludovic Courtès: > But we also need more flexibility, in particular the ability to say > “this branch is ready so it should be merged now”. Well, there *is* flexibility. If the r-team branch is ready and built out on CI, say, you can merge it now (w

Re: [Shepherd] Default value for #:wait-for-termination?

Felix Lechner via "Development of GNU Guix and the GNU System distribution." skribis: > Should we change the default for the #:wait-for-termination? parameter > in the Shepherd's make-timer-constructor to #t? Yes, I think so. Just not in the stable 1.0.x series. Ludo’.

Re: Jumping the queue: merge r-team before python-team?

Christopher Baines skribis: >> But we also need more flexibility, in particular the ability to say >> “this branch is ready so it should be merged now”. Could we provide a >> way to change the order of branches shown by qa.guix.gnu.org? > > The current mechanism to do this is mentioned on [1], b

Re: Shepherd testimonial/questions

Hi Daniel, Daniel Littlewood skribis: > I recently started using the shepherd to automate services on my guix > system laptop. I wanted to send a message, mostly to express what a > pleasant experience it was! I wrote it up on my blog, with some > context.[1] Thanks for the kind words! :-) > 1

Re: Jumping the queue: merge r-team before python-team?

Am Fri, Apr 11, 2025 at 05:22:57PM +0200 schrieb Ludovic Courtès: > Oh, my bad; so each person/group responsible for a branch can right away > mark it as blocked by ‘r-team’ , and > then ‘r-team’ will be at the top of the list and QA will pick it up. > Did I get t

Re: Jumping the queue: merge r-team before python-team?

Ludovic Courtès writes: > Christopher Baines skribis: > >>> But we also need more flexibility, in particular the ability to say >>> “this branch is ready so it should be merged now”. Could we provide a >>> way to change the order of branches shown by qa.guix.gnu.org? >> >> The current mechanism

Re: Slow guix pull? (was Re: Please don't leave GNU)

45mg <45mg.wri...@gmail.com> skribis: > It's probably a bug with the caching; I pull from a local authenticated > fork, which can't be too common, so it makes sense that this hasn't been > caught before. I haven't had time to properly debug it yet (deleting the > cache does not help). I noticed s

Re: [fr] Moment de convivialité Guix@Paris en mars

salut Nicolas, On Thu, 10 Apr 2025 at 10:58, Nicolas Graves wrote: > Dans les prochaines semaines, je vais probablement essayer d'en faire un > article sur le blog Guix, et peut-être même finir par rédiger la doc > pour le manuel. En voilà une bonne idée! 😀 à tantôt, simon

Re: Emacs dependent package input question

Hi Ian, On Sat, 05 Apr 2025 at 09:38, Ian Eure wrote: > a) Leave it as is. Don’t love it, but if there’s concensus that > this is the right way, then okay. Somehow, the consensus has been to have “maximally” featured packages – roughly speaking – and use -minimal when not. For instance, Al

Re: Setting procedure properties for build-system builders

Hi Nicolas, CC: core-team On Mon, 17 Mar 2025 at 10:53, ngra...@gmx.com wrote: > I would like to make that metadata available at the build-system > level. This would require setting procedure properties on builder > functions, in every build-system, like so: > > (set-procedure-properties! > gnu

Re: Jumping the queue: merge r-team before python-team?

Hey, Greg Hogan skribis: > I'd rather have some team make progress than no one, and the only way > to dig ourselves out of this hole is to be more assertive as Ricardo > has been here. Let everyone else follow his lead soon after. Yes. I think it’s good that qa.guix.gnu.org and the correspondi

Re: Jumping the queue: merge r-team before python-team?

Hi Andreas, On Fri, Apr 11 2025, Andreas Enge wrote: > Well, why should r-team go before qt-team or tex-team? > (I have no particular opinion and am fine with any decision on that > matter, but one should search agreement by qt-team and tex-team Some "one" has to do it. Why not you? Kind regar