From: zimoun <zimon.toutoune@gmail.com>
To: Kyle Meyer <kyle@kyleam.com>,
Thiago Jung Bauermann <bauermann@kolabnow.com>
Cc: Arun Isaac <arunisaac@systemreboot.net>,
Maxim Cournoyer <maxim.cournoyer@gmail.com>,
guix-devel@gnu.org
Subject: Re: Updating mumi on berlin
Date: Thu, 05 May 2022 10:37:51 +0200 [thread overview]
Message-ID: <86sfpo5q8w.fsf@gmail.com> (raw)
In-Reply-To: <87o80cvjdl.fsf@kyleam.com>
Hi Kyle and Thiago,
Reading your both answers…
On Wed, 04 May 2022 at 21:49, Kyle Meyer <kyle@kyleam.com> wrote:
> I've tried sit down and update Guix's public-inbox definition a few
> times, but there are various test failures that I didn't figure out how
> to handle in the time I had. (IIRC, I think they're related to the lei
> tests expecting to be able to kill the lei-daemon process, which isn't
> the case in Guix's build environment.)
On Thu, 05 May 2022 at 00:13, Thiago Jung Bauermann <bauermann@kolabnow.com> wrote:
> Yes, that's what I'm seeing as well. The lei-daemon process is actually
> killed, but because of bug 30948 it is left in a zombie state and so the
> testsuite thinks that it didn't go away.
>
> The testsuite checks whether lei-daemon is gone by doing a
> “kill(<lei-daemon pid>, 0)”, which unfortunately succeeds for zombie processes.
>
> I've been meaning to add child reaping to the Guix builder process, but
> I'm moving very slowly due to time constraints and my unfamiliarity with
> that part of Guix...
…why not just disable the specific test or if not possible, turn off the
test suite ’#:tests? #f’. Whereas it is not the best, it would allow to
have ’lei’ while waiting the fix at the Guix build environment level.
WDYT?
> $ guix shell -p path/to/profile -- lei up --all
How do you query all new ones for a specific list?
Thiago, do you use ’piem’ [1]?
Kyle, the function ’piem-inject-thread-into-maildir’ [2] is really
handy. But I would like this signature instead:
--8<---------------cut here---------------start------------->8---
(defun piem-inject-thread-into-maildir (mid &optional inbox message-only)
--8<---------------cut here---------------end--------------->8---
i.e., passing an ’inbox’ argument and this argument would be also passed
to ’piem-inbox-maildir-directory’ and ’piem-mid-url’,
--8<---------------cut here---------------start------------->8---
(let ((maildir-directory (piem-inbox-maildir-directory inbox)))
[...]
(let ((url (concat (piem-mid-url mid inbox)
--8<---------------cut here---------------end--------------->8---
Then using ’piem-inboxes’ accordingly, I have,
--8<---------------cut here---------------start------------->8---
(defun my/public-inbox-insert (number)
(interactive "nBug number: ")
(let* ((meta (car (debbugs-get-status number)))
(inbox (car (debbugs-get-attribute meta 'package))) ;Probably inaccurate for the general case
(raw (debbugs-get-attribute meta 'msgid))
(msgid (replace-regexp-in-string "<\\|>" "" raw)))
(message "Message-ID: %s from %s." msgid inbox)
(my/piem-inject-thread-into-maildir msgid inbox))))
--8<---------------cut here---------------end--------------->8---
For sure, it could be improved but it fits my needs.
When I do old bug squashing, I use ’M-x debbugs-gnu’ and pick some.
Sometimes, when the thread is long and complex [3], I just drop it
because it requires from me more work to deal with just the reading;
other said, I inject the thread to my local inbox which allows me to
read it offline, but more importantly, read it (or navigate) with my
favorite tool not the Gnus-like interface.
1: <https://git.kyleam.com/piem/about/>
2: <https://git.kyleam.com/piem/tree/piem.el#n759>
3: <https://yhetil.org/guix-bugs/87wpg7ffbm.fsf@gnu.org/#r>
Cheers,
simon
next prev parent reply other threads:[~2022-05-05 9:49 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-22 5:38 Updating mumi on berlin Arun Isaac
2022-04-27 6:27 ` zimoun
2022-04-27 11:14 ` Arun Isaac
2022-05-02 10:33 ` zimoun
2022-05-03 17:33 ` Arun Isaac
2022-05-03 20:42 ` Thiago Jung Bauermann
2022-05-04 8:00 ` zimoun
2022-05-05 1:49 ` Kyle Meyer
2022-05-05 3:13 ` Thiago Jung Bauermann
2022-05-05 14:45 ` Maxim Cournoyer
2022-05-06 3:16 ` Thiago Jung Bauermann
2022-05-07 22:20 ` Ludovic Courtès
2022-05-08 1:00 ` Thiago Jung Bauermann
2022-05-15 20:59 ` Ludovic Courtès
2022-05-16 8:27 ` Maxime Devos
2022-06-04 22:36 ` Thiago Jung Bauermann
2022-05-05 8:37 ` zimoun [this message]
2022-05-06 2:24 ` public-inbox v1.7 update (was: Updating mumi on berlin) Kyle Meyer
2022-05-06 7:37 ` zimoun
2022-05-08 4:41 ` Kyle Meyer
2022-05-09 13:58 ` zimoun
2022-05-06 3:22 ` Updating mumi on berlin Thiago Jung Bauermann
2022-05-06 7:48 ` zimoun
2022-05-15 22:05 ` Thiago Jung Bauermann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86sfpo5q8w.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=arunisaac@systemreboot.net \
--cc=bauermann@kolabnow.com \
--cc=guix-devel@gnu.org \
--cc=kyle@kyleam.com \
--cc=maxim.cournoyer@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).