[workflow] Triaging issues (was Automatically close bug report when a patch is committed)

Hi Christopher, [note: I'm deleting the "In-Reply-To:" header and changing subject to try to start a new thread] Christopher Baines writes: > Giovanni Biscuolo writes: [...] >> 20 bugs with messages similar to this one: >> >> >> rofi-wayland was added in: >> >>

Re: Guix pull speed

Hi Josselin, On Thu, 7 Sept 2023 at 10:37, Josselin Poiret wrote: [...] Thanks for explaining. Cheers, simon

Re: [workflow] Automatically close bug report when a patch is committed

Hi Maxim and Ludovic, I'm including you, Ludovic, becaus in the past you requested a similar git hook installation for Guix and maybe you have more info Maxim Cournoyer writes: > Giovanni Biscuolo writes: [...] OK, I really found the wrong examples as Christopher pointed out, but my

Re: CI job for lisp-team branch

On Wed, Sep 06, 2023 at 03:47:01PM +0300, Efraim Flashner wrote: > On Mon, Sep 04, 2023 at 09:27:44AM +, Guillaume Le Vaillant wrote: > > Hi. > > I created a lisp-team branch to work one some updates for clisp and > > sbcl. Could someone with admin access to the CI things add a job for it? > >

Re: CI job for lisp-team branch

On Thu, Sep 07, 2023 at 12:31:39PM +, Guillaume Le Vaillant wrote: > Efraim Flashner skribis: > > > On Wed, Sep 06, 2023 at 03:47:01PM +0300, Efraim Flashner wrote: > >> > >> I commented on IRC but figured I should post to the mailing list. > >> > >> I tested sbcl@2.3.8 on riscv64-linux

Re: Guix pull speed

-- Simon Tournier writes: > Do it copy on the fly? I mean, is it first written somewhere then moved? It just copies the output of the building process, which shouldn't be too big. It's waiting for build output though, hence why it's taking so much time. >> It's building the same! Just

Re: CI job for lisp-team branch

Efraim Flashner skribis: > On Wed, Sep 06, 2023 at 03:47:01PM +0300, Efraim Flashner wrote: >> >> I commented on IRC but figured I should post to the mailing list. >> >> I tested sbcl@2.3.8 on riscv64-linux and the build failed in the contrib >> section. I see the patch was removed, presumably

Re: [workflow] Automatically close bug report when a patch is committed

Hi Simon, Simon Tournier writes: > On Wed, 06 Sep 2023 at 12:14, Maxim Cournoyer > wrote: > >>> Let's avoid manual gardening as much as possible! :-) >> >> I like the idea! > > I think that automatizing is not trivial. Sadly. If we "restrict" the automation to "close the bugs that are

Re: [workflow] Automatically close bug report when a patch is committed

Hi Gio', On Thu, Sep 7, 2023 at 4:08 AM Giovanni Biscuolo wrote: > > close the bugs that are listed in > the commit message Perhaps you'd like to see Debian's hook [1] for the Salsa web forge (which is controversially based on Gitlab). The regex does not work properly for more than two bugs,

Re: Guix related things in Germany at the end of October/start of November

On Tue, Sep 05, 2023 at 06:28:09PM +0100, Christopher Baines wrote: > Hey, > > PackagingCon [1] is happening in Berlin on the 26th to the 28th of > October, and the Reproducible Builds summit is happening in Hamburg on > the 31st of October to the 2nd of November. > > 1:

Re: [workflow] Automatically close bug report when a patch is committed

On 2023-09-07, Giovanni Biscuolo wrote: > Hi Maxim and Ludovic, > Maxim Cournoyer writes: >> Giovanni Biscuolo writes: .. >>> When I asket I though the best way would be to scan for a string like >>> "Close #" in the commit message (the committer should add >>> such a string) but probably this

Re: Process for reviewing patches as someone without commit access

On 2023-09-06, Maxim Cournoyer wrote: > Simon Tournier writes: >> On Wed, 06 Sep 2023 at 16:55, Christopher Baines wrote: >> >>> Once we know what tags to use, I can have the QA frontpage do something >>> similar to the "Mark as moreinfo" links, so it's easy to just click a >>> button then send

Re: [workflow] Automatically close bug report when a patch is committed

Hi, Felix Lechner writes: > Hi Gio', > > On Thu, Sep 7, 2023 at 4:08 AM Giovanni Biscuolo wrote: >> >> close the bugs that are listed in >> the commit message > > Perhaps you'd like to see Debian's hook [1] for the Salsa web forge > (which is controversially based on Gitlab). > > The regex

Re: [workflow] Automatically close bug report when a patch is committed

Hi, Giovanni Biscuolo writes: [...] >>> The first thing we need is a server side git post-receive hook on >>> Savannah, I've opened the sr#110928 support request: >>> https://savannah.nongnu.org/support/index.php?110928 >> >> It's something that the Savannah folks would need to maintain >>

Re: Pinned versions should be a requirement.

On 2023-09-07, Simon Tournier wrote: > Hi, > > On Mon, 04 Sep 2023 at 21:59, Distopico wrote: > >> In my experience using Guix and attempting to make contributions, I've >> noticed that the vast majority of times when a library breaks, it's >> because one of its dependencies changed version. >

Re: [workflow] Automatically close bug report when a patch is committed

Hi Maxim, Maxim Cournoyer writes: > Simon Tournier writes: [...] >> Maybe patchwork already running (I think) could help, trying to >> regularly rebase the branch dedicated to the submission on the top of >> master, then if all is fine, somehow the two heads from the master >> branch and the

Re: CI job for lisp-team branch

I reported the issue upstream at with your log file. Let's see what they say... signature.asc Description: PGP signature

Re: Building from git

Hi, On 2023-09-07 13:06, Simon Tournier wrote: > Hi, > > On Sat, 02 Sep 2023 at 11:03, Nicolas Débonnaire > wrote: > >> guix shell -D guix --pure >> ./bootstrap >> ./configure --localstatedir=/var --syscondir=/etc >> make > > [...] > >> Error: fontconfig:Didn't find expected font family.

Re: Process for reviewing patches as someone without commit access

Hi, On Wed, 06 Sep 2023 at 22:47, Maxim Cournoyer wrote: >> Well, using emacs-debbugs and then >> >> C-u M-x debbugs-gnu-usertags guix-patches RET >> >> the list of usertags is: >> >> guix-patches for-core-updates >> guix-patches reviewed-looks-good >> >> And if instead of

Re: Pinned versions should be a requirement.

Hi, On Mon, 04 Sep 2023 at 21:59, Distopico wrote: > In my experience using Guix and attempting to make contributions, I've > noticed that the vast majority of times when a library breaks, it's > because one of its dependencies changed version. That’s because contributor and/or reviewer are

Re: [workflow] Automatically close bug report when a patch is committed

Hi, On Wed, 06 Sep 2023 at 22:01, Maxim Cournoyer wrote: > We could use Gerrit's commit hook that adds a unique ID as a git > trailer. Then it should become possible to Do we still already have Gerrit running? Cheers, simon

Re: Building from git

Hi, On Sat, 02 Sep 2023 at 11:03, Nicolas Débonnaire wrote: > guix shell -D guix --pure > ./bootstrap > ./configure --localstatedir=/var --syscondir=/etc > make [...] > Error: fontconfig:Didn't find expected font family. Perhaps URW Type 1 > fonts need installing? Hum, weird. That’s because

Re: [workflow] Automatically close bug report when a patch is committed

Hi Felix, Felix Lechner writes: > Hi Gio', > > On Thu, Sep 7, 2023 at 4:08 AM Giovanni Biscuolo wrote: >> >> close the bugs that are listed in >> the commit message > > Perhaps you'd like to see Debian's hook [1] for the Salsa web forge > (which is controversially based on Gitlab). [...]

Re: [workflow] Automatically close bug report when a patch is committed

Hi Vagrant! On Thu, Sep 7, 2023 at 9:13 AM Vagrant Cascadian wrote: > > So... I maintain the guix package in Debian, and want to make sure > that whatever bug-closing indicator guix upstream uses, does not end up > triggering when I push new upstream versions to salsa.debian.org ... and >

Re: [workflow] Automatically close bug report when a patch is committed

On 2023-09-07, Maxim Cournoyer wrote: > Felix Lechner writes: >> On Thu, Sep 7, 2023 at 4:08 AM Giovanni Biscuolo wrote: >>> >>> close the bugs that are listed in >>> the commit message ... > Did you see my message about integrating a commit-hook similar to what > Gerrit uses? It produces

Re: How can we decrease the cognitive overhead for contributors?

Hi Katherine, Hi Liliana, On Thu, Sep 7, 2023 at 1:39 PM Katherine Cox-Buday wrote: > > Liliana, many of your responses in this thread are not OK. Thank you for your candor! I also sensed some negativity in that interaction. Both of you, please feel free to direct your comments to me—privately

Re: [workflow] Triaging issues (was Automatically close bug report when a patch is committed)

On 2023-09-07, Giovanni Biscuolo wrote: > Christopher Baines writes: > >> Giovanni Biscuolo writes: > > [...] > >>> 20 bugs with messages similar to this one: >>> >>> >>> rofi-wayland was added in: >>> >>> 04b5450ad852735dfa50961d3afc789b2e52b407 gnu: Add rofi-wayland. >>> >>> And updated to

Re: Branch (and team?) for mesa updates

On Sun, 2023-08-27 at 12:45 +0800, dan wrote: > Hi John, > > Aug 26, 2023 08:51:49 John Kehayias : > > > > > > Though at least (gnu packages gl) looks pretty > > reasonable to start for maybe a graphics team? Maybe with vulkan? > > > > I'm still not sure but I should probably propose something

Re: Next action, survey?

On 9/6/23 3:34 AM, Simon Tournier wrote: Well, from my point of view, the next steps are: + Propose a survey (questions), open a new thread (or a bug report) for iterating. I'll open a bug report and start logging notes/suggestions against it. In it, I'll include your points: +

Re: How can we decrease the cognitive overhead for contributors?

On 9/6/23 3:07 AM, Simon Tournier wrote: As you said, we are all different, thus it means that any collaboration cannot be full-frictionless. Because any social interaction implies norms and standards. Norms and standards are by their definition excluding. For example, we communicate in

Re: How can we decrease the cognitive overhead for contributors?

On 9/5/23 2:43 PM, Liliana Marie Prikler wrote: Am Dienstag, dem 05.09.2023 um 19:40 +0100 schrieb (: Liliana Marie Prikler writes: Uhm, we have snippets? Well, those are exclusive to Emacs :)  And without regard to /that/ issue, I do think that there's a problem if the commit format is so

Re: Building from git

On 2023-09-07 14:06:05 +0200, Simon Tournier wrote: > Hi, > > On Sat, 02 Sep 2023 at 11:03, Nicolas Débonnaire > wrote: > > > guix shell -D guix --pure > > ./bootstrap > > ./configure --localstatedir=/var --syscondir=/etc > > make > > [...] > > > Error: fontconfig:Didn't find expected font

Cadence For Merging python-team into master

Hi Lars, What is the cadence for merging the python-team branch into master? Should you do it, me, or someone else? best, jgart