Re: Updating mumi on berlin

[Thiago Jung Bauermann]

Hello Ludo,

Ludovic Courtès  writes:

> Thiago Jung Bauermann  skribis:
>
>> I tried the latter a couple of weeks ago and it didn't work either,
>> though it's highly likely that I did something wrong in my Scheme code.
>> I also didn't use the 1-second timer hack so perhaps that was it.
>>
>> I just tested this (adapted from the mutter package) and it worked:
>>
>> @@ -4137,6 +4142,26 @@ (define-public public-inbox
>>   ;; the builder.
>>   (substitute* "t/httpd-unix.t"
>> (("^SKIP: \\{") "SKIP: { skip('Guix');"
>> + (replace 'check
>> +   (lambda* (#:key target
>> + (tests? (not target)) (test-flags '())
>> + #:allow-other-keys)
>> + (if tests?
>> + (match (primitive-fork)
>> +   (0 ;child process
>> +(set-child-subreaper!)
>> +;; Use tini so that signals are properly handled and
>> +;; doubly-forked processes get reaped; otherwise,
>> +;; lei-daemon is kept as a zombie and the testsuite
>> +;; fails thinking that it didn't quit as it should.
>> +(apply execlp "tini" "--"
>> +   "make" "check" test-flags))
>
> How does a basic SIGCHLD handler fare?
>
>   (sigaction SIGCHLD
> (lambda _ (false-if-exception (waitpid WAIT_ANY WNOHANG

I finally had a chance to try this, but it didn't work. I didn't try the
changes suggested by Maxime though.

Here's the full ‘check’ phase I tried:

--8<---cut here---start->8---
(replace 'check
  (lambda* (#:key target
(tests? (not target)) (test-flags '())
#:allow-other-keys)
(if tests?
(match (primitive-fork)
  (0 ;child process
(set-child-subreaper!)

;; lei tests build UNIX domain sockets in the temporary
;; directory, but the path of those sockets can be at most
;; 108 chars and Guix' default value for the variables
;; below already use 47 chars. Use the shortest temporary
;; path possible to avoid hitting the limit.
(setenv "TEMP" "/tmp")
(setenv "TEMPDIR" "/tmp")
(setenv "TMP" "/tmp")
(setenv "TMPDIR" "/tmp")

(sigaction SIGCHLD
  (lambda _ (false-if-exception (waitpid WAIT_ANY WNOHANG
(exit (status:exit-val
(apply system* "make" "check" test-flags
  (pid
(match (waitpid pid)
  ((_ . status)
(unless (zero? status)
  (error "`make check' exited with status" status))
(format #t "test suite not run~%"
--8<---cut here---end--->8---

-- 
Thanks
Thiago

Re: Mummi wishlist: API using Message-ID

[Ricardo Wurmus]

Ricardo Wurmus  writes:

> zimoun  writes:
>
>> For example .  The number #16 is
>> really difficult to guess. :-)
>>
>> Instead, it is easy to get the Message-ID.  (Using emacs-notmuch, only
>> hit the key ’ci’) Therefore, it could be nice to be able to provide
>> e.g., the URL:
>>
>> 
>>
>> redirecting to .  And maybe the
>> current webpage could provide the Message-ID, easy to copy and then
>> paste in my email reader.
>
> This is now implemented in mumi.
>
> Once delpoyed to issues.guix.gnu.org you can visit
>
> https://issues.guix.gnu.org/msgid/HAv_FWZRa_dCADY6U07oX-E2vTrtcxk8ltkpfvTpYCsIh4O5PuItHGIh6w-g5GGmoqVEfkjDUOplpUErdGEPAiFYdrjjDhwd9RJ4OyjjGgY=@hector.link
>
> and it would redirect to https://issues.guix.gnu.org/33899.  It doesn’t
> yet jump to the correct message number, but that’s easy to implement.
> (I only had time for one little hack.)

Mumi commit 9b28ec7d152623692877bcb767e5c654e59e57ed adds an anchor for
the message id and redirects /msgid URLs to issue URL + message id
fragment.

-- 
Ricardo

Re: Teams

[david larsson]

On 4 June 2022 12:07:15 UTC, Ricardo Wurmus  wrote:

* Rust team

[...]

Tobias Geerinckx-Rice


OK what the hell.



Would you wanna create and be the Bash team person as well? :)

Best regards,
David

Re: Teams

[Maxime Devos]

Tobias Geerinckx-Rice schreef op za 04-06-2022 om 14:50 [+]:
> I think we should also have (natural) language 'teams' who can be pinged 
> when, e.g., a news item lands, through a single guix-translators@ meta-alias, 
> and who can co-ordinate before releases.
> 
> I'll take -nl.  Maxime?

Ok sure.


signature.asc
Description: This is a digitally signed message part

Re: Teams

[Tobias Geerinckx-Rice]

On 4 June 2022 12:07:15 UTC, Ricardo Wurmus  wrote:
>* Rust team
[...]
>Tobias Geerinckx-Rice

OK what the hell.

I'll also join Leo on a kernel/module/initrd team if they're interested.

I think we should also have (natural) language 'teams' who can be pinged when, 
e.g., a news item lands, through a single guix-translators@ meta-alias, and who 
can co-ordinate before releases.

I'll take -nl.  Maxime?

Ricardo,

Kind regards,

T G-R

Sent on the go.  Excuse or enjoy my brevity.

Re: Teams

[Ekaitz Zarraga]

> Hi Guix,
>
> this is not a new idea[1]: let’s add a page to the website that lists teams
> and a mail alias for each of the teams.
>
> For example, the “R team” consists of people familiar with how R
> packaging works in Guix, e.g. Simon and myself. There would be an alias
> “guix-tea...@gnu.org”. People with questions about R in Guix could
> write an email to that alias.
>
> Mumi could also send email to guix-tea...@gnu.org to remind them about
> patches relating to R / Bioconductor / CRAN, etc.
>
> Maintainers could write to these teams before releases to ask if there
> are any obstacles to a release.
>
> As a first step I’d suggest collecting teams, setting up the email
> aliases, and updating the website to show the existing teams. Here’s
> a draft of three teams:
>
> * R team
> Simon Tournier
> Ricardo Wurmus
>
> * Java team
> Julien Lepiller
>
> * Rust team
> Efraim Flashner
> Aleksandr Vityazev
> Arun Isaac
> John Soo
> Maxim Cournoyer
> Nicolas Goaziou
> Tobias Geerinckx-Rice
>
> What do you think?
>
>
> --
> Ricardo
>
> [1]: https://lists.gnu.org/archive/html/guix-devel/2021-12/msg00224.html


If you want to add a Bootstrapping team, feel free to add me there.

Thanks for this effort. It's really interesting.

Cheers,
Ekaitz

Re: Teams

[Maxime Devos]

Ricardo Wurmus schreef op za 04-06-2022 om 14:07 [+0200]:
> As a first step I’d suggest collecting teams, setting up the email
> aliases, and updating the website to show the existing teams.  Here’s
> a draft of three teams:
> 
> [...]

You can add me to the Rust team and to a new Minetest team.
Maybe Vivien Kraus would be interested in joining the Minetest team.

Greetings,
Maxime.


signature.asc
Description: This is a digitally signed message part

Teams

[Ricardo Wurmus]

Hi Guix,

this is not a new idea[1]: let’s add a page to the website that lists teams
and a mail alias for each of the teams.

For example, the “R team” consists of people familiar with how R
packaging works in Guix, e.g. Simon and myself.  There would be an alias
“guix-tea...@gnu.org”.  People with questions about R in Guix could
write an email to that alias.

Mumi could also send email to guix-tea...@gnu.org to remind them about
patches relating to R / Bioconductor / CRAN, etc.

Maintainers could write to these teams before releases to ask if there
are any obstacles to a release.

As a first step I’d suggest collecting teams, setting up the email
aliases, and updating the website to show the existing teams.  Here’s
a draft of three teams:

* R team
Simon Tournier
Ricardo Wurmus

* Java team
Julien Lepiller

* Rust team
Efraim Flashner
Aleksandr Vityazev
Arun Isaac
John Soo
Maxim Cournoyer
Nicolas Goaziou
Tobias Geerinckx-Rice

What do you think?


-- 
Ricardo

[1]: https://lists.gnu.org/archive/html/guix-devel/2021-12/msg00224.html

Re: Mummi wishlist: API using Message-ID

[Ricardo Wurmus]

zimoun  writes:

> For example .  The number #16 is
> really difficult to guess. :-)
>
> Instead, it is easy to get the Message-ID.  (Using emacs-notmuch, only
> hit the key ’ci’) Therefore, it could be nice to be able to provide
> e.g., the URL:
>
> 
>
> redirecting to .  And maybe the
> current webpage could provide the Message-ID, easy to copy and then
> paste in my email reader.

This is now implemented in mumi.

Once delpoyed to issues.guix.gnu.org you can visit

https://issues.guix.gnu.org/msgid/HAv_FWZRa_dCADY6U07oX-E2vTrtcxk8ltkpfvTpYCsIh4O5PuItHGIh6w-g5GGmoqVEfkjDUOplpUErdGEPAiFYdrjjDhwd9RJ4OyjjGgY=@hector.link

and it would redirect to https://issues.guix.gnu.org/33899.  It doesn’t
yet jump to the correct message number, but that’s easy to implement.
(I only had time for one little hack.)

-- 
Ricardo

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

[Maxime Devos]

b...@bokr.com schreef op za 04-06-2022 om 01:55 [+0200]:
> 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?
> [...]

Only the replacing of an old by a new symlink needs to be atomic, and
this is already the case.  The only non-atomicity is that if
interrupted, an extra symlink [...].new can be created, but except for
tidyness this is not really a problem AFAICT.

Speaking of atomicity, I wonder if 'fsync'ing the symlink or the
directory is required?  E.g., is it possible after a power interruption
for the contents (= target) of the new symlink to be truncated without
doing a 'fsync' before the rename?

Greetings,
Maxime.


signature.asc
Description: This is a digitally signed message part

Re: The Little Guixer

[vidak]

On 2022-06-04 09:09, Yasuaki Kudo wrote:
> 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’.

we could do a small wiki?

i'm down to help.

~vidak

Re: wishlist: “repack” generations history of profile

[Giovanni Biscuolo]

Hi Simon,

I know you know very well all I'm saying here, I'm just commenting for
casual readers of this thread

zimoun  writes:

[...]

> The generation #1 can be lost.  For sure it depends on the cluster
> policy but, as a sysadmin, I do not tell all the users that a GC will be
> run – and even if I am doing, I am sure that some user will miss to save
> the channels.scm and manifest.scm for each generation.

I don't know how easy or not is the implementation of this feature and
for sure it would be a plus, but IMHO all users must understand that for
their projects (profiles) to be reproducible and versioned the /only/
way is to keep channels.scm and manifests.scm in a VCS (i.e. git)

> That’s why, something like “repack” is missing.  As a user, I should be
> able to do
>
> guix package --switch-generation=1
>
> whatever the sysadmin collects about the old generations and whatever I
> saved using some external tools.

...except you wish to reproduce the project on another machine, or
/gnu/store is lost or corrupted for some reason

Also consider that sometimes pepole in teams choose to work on the same
project in different (not shared) profiles (i.e. for reproducibility
testing), this way generation history is not the same and the only way
to "sync" would be to exchange channels.scm and manifest.scm

Also, from a collaborative workflow point of view, keeping the two
"reproduce me" files (channels and manifest) is more efficient since
people can describe what (and why) they chenged things between "saved"
project generations; not committed channels.scm and manifests.scm should
be considered "local testing"

IMVHO there is no easy workaround to keeping channels.scm and
manifests.scm in a VCS, better sooner than later users should do it

[...]

Happy hacking! Gio'

-- 
Giovanni Biscuolo

Xelera IT Infrastructures


signature.asc
Description: PGP signature