From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp10.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms8.migadu.com with LMTPS id QPq0EOMPcmTUdgEAkFu2QA (envelope-from ) for ; Sat, 27 May 2023 16:12:51 +0200 Received: from aspmx1.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp10.migadu.com with LMTPS id 2HTaD+MPcmQ1WgEAG6o9tA (envelope-from ) for ; Sat, 27 May 2023 16:12:51 +0200 Received: from mail1.fsfe.org (mail1.fsfe.org [217.69.89.151]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by aspmx1.migadu.com (Postfix) with ESMTPS id 71F423E2EC for ; Sat, 27 May 2023 16:12:47 +0200 (CEST) From: Jelle Licht DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fsfe.org; s=2021100501; t=1685196765; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type; bh=SEh9i3s7un15KH4seMyy9kkIIP1Exd950lUAqHmJ3Ak=; b=YgE3Mds6Je8ofcI+EzriYZNdKXBm3YCDPM1pitY5viV2aCROo70BmsQBvSGz1P3rLjiJwO XZMckGaqTwRGQ6YJZL9vzwCe0ZXKmi2cv566ln90ROnXfSkm0wdYX4SJlw2a5SE9gyyhFL L1EbRfE+zi0aaXJFK3a2ZMM5qZEPxQ8= To: piem@inbox.kyleam.com Subject: On the road to (GNU) debbugs support, some blockers Date: Sat, 27 May 2023 16:12:43 +0200 Message-ID: <87y1l9ualg.fsf@fsfe.org> MIME-Version: 1.0 Content-Type: text/plain X-Migadu-Flow: FLOW_IN X-Migadu-Country: DE ARC-Seal: i=1; s=key1; d=kyleam.com; t=1685196771; a=rsa-sha256; cv=none; b=HSF+pU20rXqPwaKkOnnsIqCzJHjBWE/eNMmWcoaHW1s9+HmOjJo6A4dhVSwrbG1LKUICxs c/kgPeYSqEScTosSXKT7zG3FEx2F+1U6YAJJhpEK/7O2e5Gsd2XtZRVuEWoDI37t2hNMYP 3IVfzuR2Z5mq+ADwQEgHi7ymFUHPJTxcQy4hKksQFpbfTRU22gmals7uOPa/k6mvaUmsn5 xyxJT1+R6NCvCUydTM8n73WF+fAD8vPBkZtp5jzbB6NmdngkldHXIXt5M9uiBwhXjJMJlX 1lDC6dn/Y82cj0FmDMTDVwvp9tSXTmpcS9mun04+tVZto1haNXt5L4ywlI3bBw== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=pass header.d=fsfe.org header.s=2021100501 header.b=YgE3Mds6; dmarc=pass (policy=none) header.from=fsfe.org; spf=pass (aspmx1.migadu.com: domain of jlicht@fsfe.org designates 217.69.89.151 as permitted sender) smtp.mailfrom=jlicht@fsfe.org ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=kyleam.com; s=key1; t=1685196771; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: dkim-signature; bh=SEh9i3s7un15KH4seMyy9kkIIP1Exd950lUAqHmJ3Ak=; b=sDQPdbjEko1fy8qlp/rSOV1MYMA6lokx5n701qjGzDe9DidHNgWjhQsqbHzOzBDoZ4BUF1 hbnzMEnX2JQP5tP1W4SHLGjGnyIKsq6H/yn1wZ/a7x5xeyD7EbAyk/6kijc0WPYOXUda7d CwXdRUY1qC3Sfudkws6qnwDKRbJU1cY6mr32CANWTYYAsuauip1ifyxcGop1K3Pg0phWPl hO94cOQWI25BZ4qkLB1O8yt5G7p5ntlb48aESPohpDG01nkmwxLLLY1Uh5n4trxTrdyKmk 5IXWm4+OQTB7H5zFnyOT/ZFy6/yrhy4rflpao59QnlCv4YROs0tMKtayVuL5lA== X-Migadu-Scanner: scn1.migadu.com Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=fsfe.org header.s=2021100501 header.b=YgE3Mds6; dmarc=pass (policy=none) header.from=fsfe.org; spf=pass (aspmx1.migadu.com: domain of jlicht@fsfe.org designates 217.69.89.151 as permitted sender) smtp.mailfrom=jlicht@fsfe.org X-Migadu-Spam-Score: -7.69 X-Spam-Score: -7.69 X-Migadu-Queue-Id: 71F423E2EC X-TUID: KuWmtYmb4wRJ Thanks for working on piem, and sharing it under a free license! In getting some local hacks set up, I ran into some inconsistencies and issues, which may very well be misunderstandings on my part. The first one: the public-inbox-config man page (`man 5 public-inbox-config') demonstrates a url without trailing '/'. Piem's documentation uses an url with trailing '/'. It seems `piem-b4--get-am-files' assumes this url always has a trailing '/', which makes it not work for the examples used in the public-inbox-config manpage (and in particular, my pre-existing configuration). I'm not unsure if public inbox supports the trailing '/', but I see no reason to assume it would not. The second issue; in order to map (GNU) debbugs data to inbox configurations, the current best way I've worked out is to use the X-GNU-PR-Package header. Concretely, I've had to adjust `piem-gnus-get-inbox' to also take this particular mail header into account when trying to find matching configured inboxes. I am not aware of a way for debbugs users to be able to use this, without messing with non-debbugs users of gnus. Advice appreciated. NB, I also added the `:gnu-pr-package' to my configured piem inboxes so the matching could take place in the first place, of course, but this is already possible with via {setq,Customize system,$HOME.public-inbox/config}. Third issue: The `piem-gnus-mid-to-thread' seems to prepend a line like: "From mboxrd@z Thu Jan 1 00:00:00 1970" to entries. The issue comes up when we already have a line that starts with "From " at the top, which after running the `replace-regexp-in-string' boils down to something like in my generated m-piem file: --8<---------------cut here---------------start------------->8--- >From mboxrd@z Thu Jan 1 00:00:00 1970 >>From unknown Sat May 27 07:31:53 2023 [rest of file] --8<---------------cut here---------------end--------------->8--- AFAIK, b4 am can't deal with this, as the "From " line needs to be the first line, and any later lines need to be parsed as email header (which ">From ..." is not). Any solutions appreciated, that (again) don't impact non-debbugs users of gnus. My local current hack changed the format string "From mboxrd@z Thu Jan 1 00:00:00 1970\n%s\n" by "%s\n", and the regex from "^>*From " into "^>+From", but this will of course break if any of the mails I'm working with contains a line starting with "From ". Thanks for any help, and please let me know if you'd be interested patches for a (clean) integration with (GNU) debbugs. Kind regards, Jelle Licht