From: "Ludovic Courtès" <ludo@gnu.org>
To: Sharlatan Hellseher <sharlatanus@gmail.com>
Cc: zimon.toutoune@gmail.com, guix-devel@gnu.org
Subject: Re: Automatically testing package updates
Date: Sun, 15 Dec 2024 00:51:44 +0100 [thread overview]
Message-ID: <87ldwhkelr.fsf@gnu.org> (raw)
In-Reply-To: <875xo0q319.fsf@gmail.com> (Sharlatan Hellseher's message of "Tue, 03 Dec 2024 14:01:06 +0000")
Hi,
Sharlatan Hellseher <sharlatanus@gmail.com> skribis:
> I try to keep cadence with update in astronomy module monthly and having
> ongoing refresh work for golang collection. Maybe we may have some API
> output on that type available at <https://packages.guix.gnu.org/>,
> showing the impact ration of the given package and the number of
> dependents as well?
I’m not sure what you mean here.
But what about having an astronomy update manifest?
[...]
> From other side but current implementation of pyproject-build-system or
> python-build-system and related importer/updater in most of the cases
> just breaks the package completely. It looks like the issue comes from
> the fact that Python in a massive migration to pyproject.toml (setup.py
> and setup.cfg are becoming deprecated) which specifies install, test and
> dev dependencies and during refresh it can't be parsed, so it would
> block automatic packge refresh.
Oh. So we should update the pypi importer/updater to parse that, right?
Ludo’.
next prev parent reply other threads:[~2024-12-14 23:52 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-03 14:01 Re: Automatically testing package updates Sharlatan Hellseher
2024-12-14 23:51 ` Ludovic Courtès [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-12-02 13:44 Ludovic Courtès
2024-12-02 14:50 ` Simon Tournier
2024-12-02 19:14 ` Simon Tournier
2024-12-02 19:16 ` Simon Tournier
2024-12-05 7:20 ` Efraim Flashner
2024-12-05 8:06 ` Hilton Chain
2024-12-05 9:23 ` Ricardo Wurmus
2024-12-05 13:29 ` Suhail Singh
2024-12-05 15:31 ` Ricardo Wurmus
2024-12-05 16:10 ` Suhail Singh
2024-12-05 19:07 ` Attila Lendvai
2024-12-05 19:55 ` Ricardo Wurmus
2024-12-06 5:09 ` Suhail Singh
2024-12-14 23:46 ` Ludovic Courtès
2024-12-06 4:53 ` Suhail Singh
2024-12-05 19:58 ` Ricardo Wurmus
2024-12-03 0:32 ` Vagrant Cascadian
2024-12-14 23:47 ` Ludovic Courtès
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=87ldwhkelr.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=sharlatanus@gmail.com \
--cc=zimon.toutoune@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).