From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp1 ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms11 with LMTPS id xrcJJOA/UWANTQAA0tVLHw (envelope-from ) for ; Tue, 16 Mar 2021 23:31:44 +0000 Received: from aspmx1.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp1 with LMTPS id ODhDH+A/UWDUKAAAbx9fmQ (envelope-from ) for ; Tue, 16 Mar 2021 23:31:44 +0000 Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by aspmx1.migadu.com (Postfix) with ESMTPS id 3D57424690 for ; Wed, 17 Mar 2021 00:31:44 +0100 (CET) Received: from localhost ([::1]:48620 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1lMJA6-0002iF-Nv for larch@yhetil.org; Tue, 16 Mar 2021 19:31:42 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]:59066) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1lMJ7Q-000098-Tm for guix-devel@gnu.org; Tue, 16 Mar 2021 19:28:56 -0400 Received: from mira.cbaines.net ([212.71.252.8]:51702) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1lMJ7M-00069C-KZ for guix-devel@gnu.org; Tue, 16 Mar 2021 19:28:56 -0400 Received: from localhost (unknown [IPv6:2a02:8010:68c1:0:8ac0:b4c7:f5c8:7caa]) by mira.cbaines.net (Postfix) with ESMTPSA id F182927BC54; Tue, 16 Mar 2021 23:28:50 +0000 (GMT) Received: from capella (localhost [127.0.0.1]) by localhost (OpenSMTPD) with ESMTP id 9fe1b33c; Tue, 16 Mar 2021 23:28:50 +0000 (UTC) References: User-agent: mu4e 1.4.15; emacs 27.1 From: Christopher Baines To: =?utf-8?Q?L=C3=A9o?= Le Bouter Subject: Re: Fedora/Debian release monitoring inspiration for Guix Data Service In-reply-to: Date: Tue, 16 Mar 2021 23:28:46 +0000 Message-ID: <87blbiel01.fsf@cbaines.net> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature" Received-SPF: pass client-ip=212.71.252.8; envelope-from=mail@cbaines.net; helo=mira.cbaines.net X-Spam_score_int: -18 X-Spam_score: -1.9 X-Spam_bar: - X-Spam_report: (-1.9 / 5.0 requ) BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: guix-devel@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: guix-devel@gnu.org Errors-To: guix-devel-bounces+larch=yhetil.org@gnu.org Sender: "Guix-devel" X-Migadu-Flow: FLOW_IN ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1615937504; h=from:from:sender:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type:in-reply-to:in-reply-to: references:references:list-id:list-help:list-unsubscribe: list-subscribe:list-post; bh=vZdNEMO3zYhkJaFQmwcvxu21SZsKO+7v9Kotx8XRHS4=; b=LIa198YT5dtao54n0BuCiHnF5EhNOtR5GY88tSVJwfL50V6+VmgOxIMBoNlOb8Wq7mwHNC mR3Rinq4q4KtnX2AzDvLaWoNY03fqK2iAfLaWOOtwXXAYcGyNDYAxYY8TbRSmoqG5cKts0 fT398IPuPi3rnO0X0jNkXxCCbhzNJ2CEp6K0OdOGDH0l6+DqBik8ykqZRf93mTc0UO8v2y yajQhB+1sYH3lcXAHWIAOyBUzluNVQ62Q0MQ+Em1N6OClQVwnaCmGuGTgHQgrKTRkxgKMW g5qXIVXUen37xYLi3nooEX03PdRktiymopvIGg+rxSCHFZx/S06pWYalW1F2rA== ARC-Seal: i=1; s=key1; d=yhetil.org; t=1615937504; a=rsa-sha256; cv=none; b=dJUF3Pyf7+aQMoArV4VlOJil8MZXZIfqNicHirthxzL/ydgEePPqxrMgxmpuJbRRPu2sZA 0d5/QY4lnXsWdDnCXIk5q0TMbzxTGEsJzCcvqL5wZzzFouuAPFu6vcnGrKa+XCCLgRhEIX 1BSjcNKsAhcg7ziz1Kt4Dgft6oFQxfDXeAblwk/gRC7W5UAvrU6Az3AG7hN8lYiYmAy7dc v8fXp4HbAdtEFzgrsugCmWWjpoPaAQYH4Wagpee4Yw/2UgTzbNxdGGdtaWX1Fsn1KBjg/Z P3Z8ifQaqDLew9JK48h7w+VvY/uqHMC6R89H/iKfFc4q6ALfLOhm7usH4Imstg== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=none; dmarc=none; spf=pass (aspmx1.migadu.com: domain of guix-devel-bounces@gnu.org designates 209.51.188.17 as permitted sender) smtp.mailfrom=guix-devel-bounces@gnu.org X-Migadu-Spam-Score: -4.50 Authentication-Results: aspmx1.migadu.com; dkim=none; dmarc=none; spf=pass (aspmx1.migadu.com: domain of guix-devel-bounces@gnu.org designates 209.51.188.17 as permitted sender) smtp.mailfrom=guix-devel-bounces@gnu.org X-Migadu-Queue-Id: 3D57424690 X-Spam-Score: -4.50 X-Migadu-Scanner: scn0.migadu.com X-TUID: CfV5h8XGHWKe --=-=-= Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable L=C3=A9o Le Bouter writes: > It seems Fedora has automated infrastructure and feeds to monitor new > upstream releases so that maintainers can get notifications on them. > > https://release-monitoring.org/ > > Functional feed: > https://apps.fedoraproject.org/datagrepper/raw?rows_per_page=3D1&delta=3D= 127800&category=3Dhotness > > I could not find the actual data it is based on for release monitoring > (like Debian watch files). I think it might be in the service itself. > I could not find a similar feed for Debian's watch/uscan but it would > be nice if they provided some sort of RSS feed (global or scoped to > packages or sets of packages). > > I am thinking we should really get something like this with the Guix > Data Service, start including something similar to Debian uscan/watch > rules in every package so we can get reliable (in majority of cases) > update notifications. I did spot these patches https://patches.guix-patches.cbaines.net/project/guix-patches/list/?series= =3D7298 I think the Guix Data Service could run the "refresh" code from Guix and store relevant data, although I'm also thinking along the lines of trying to generate patches, like you go on to below... > We could also have some feature that gives you a feed for a manifest or > operating-system definition so that people can prioritize work on what > they care about easily. > > I would really love to have some RSS feed for new upstream releases > from Guix Data Service based on my operating-system definition I would > upload there. So, one thing I'm hoping to start work on in the coming weeks/months is the long awaited service for providing subscriptions/notifications for the Guix Data Service (+ other services). My current plan is to use a WebSub like pattern, but this could easily be adapted to RSS/email/... > We could even go as far as preparing a patch (similar to guix refresh > -u && etc/committer.scm) and trying to build it and all it's > dependents and if it doesnt cause any new failures we could send an > automated patch contribution on guix-patches directly and tag it with > "ci-update-ok" or something so a maintainer just has to double-check > quickly and push (very efficient workflow). Yeah, one problem with the current automated patch review stuff I've got going at the moment is that there's no feedback when the Guix Data Service finds out that things do/don't build. However, as I also set out above, there's been a plan and design for making that possible for years, it just needs implementing. One thing I'm hoping to do once it's possible to subscribe to Guix Data Service data is make the checks in Patchwork actually reflective of results (like 4 packages broken by these changes), rather than just providing links, and someone having to figure out what information is hidden within. Those same subscriptions could be used to prompt people to look at patches for package updates that don't introduce breakages (following what you set out above). The pieces are slowly coming together for this, at least with the way I would approach it. For example, it's possible to get commits in to data.guix-patches.cbaines.net now by just pushing to the Git repository, so to set out something similar to what you describe above: - Some service watches for new releases (through the guix refresh code), and then makes commits, and pushes them to a Git repo - There's a Guix Data Service reading from that Git repository, it starts processing the changes - Something (probably the "service" above") subscribes to find out when relevant information is available (like build successes/failures) - Builds happen via the Guix Build Coordinator, which feeds information back to the Guix Data Service - That "service" gets the notifications that the commits are good, and prompts someone to review them I hope some of that makes sense, Chris --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQKlBAEBCgCPFiEEPonu50WOcg2XVOCyXiijOwuE9XcFAmBRPy9fFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDNF ODlFRUU3NDU4RTcyMEQ5NzU0RTBCMjVFMjhBMzNCMEI4NEY1NzcRHG1haWxAY2Jh aW5lcy5uZXQACgkQXiijOwuE9Xf9Jw//QPcyUDaFeRv1MYaC1LQ8GjMlA/ymqc7H CLj6DJ5xpJYUt3h9XTyMRuLX+qeYjTYwWOtjX5KeFIxml9GFToe+jWLHiQB+1b8w Enb12pKlB2lyHKnZeyo+68jQyXvu/+q8/gXtU+QIYjCBlTIlULP0Qj2emX+rqYm7 oXizmSmdUoOXOwbq9oapxiLu1qcCc1O1ZZgiG4VK6L8ZnzLjBdbOZfiUHBFPIIxt hKD3t9RMom391LMPWvMy2XG8o6DORCm0SajzIb0liTe1MnetVGLPqvXwxyGxa5EG ATl/JBN+wHMZ8FR88696pLBGpC1WDuGBtOHy5mlCMF+IpW9iMVnGktEYtlGtw2Mi NLM+Wk3zTQDfrW31vwbJRTvKCoKKix4z1h8htva7Mrp/pPxuFwfD4P1ka+iQ5x0K 9UhBxSA7i7XcCMeenI6M3ZkVqoNZnAvGoeaPABzVVB8KQK7WA6+aWTfy9+3CX8zQ Q33TJG6j9YtMcgTsRQar3+CE9m8guS8+W/Gi3VuQ5woVa5dohNyAJTzbflI7DLl7 qUYlsFYHi1kuhVyP2FF0Q9lVsrkzCyY3mMVys0hY02jHlQKCaUiYozjEFIxkC+7c YrvPKHwzhkhthTUdkCmOUdCufVMPmlgzLVcWzdNSECiO8l1rpueduF0d6qv4zflX rkXSerrg8fg= =uhWd -----END PGP SIGNATURE----- --=-=-=--