From: Sharlatan Hellseher <sharlatanus@gmail.com>
To: zimon.toutoune@gmail.com
Cc: guix-devel@gnu.org
Subject: Re: Re: Automatically testing package updates
Date: Tue, 03 Dec 2024 14:01:06 +0000 [thread overview]
Message-ID: <875xo0q319.fsf@gmail.com> (raw)
In-Reply-To: 87a5ddoq2r.fsf@gmail.com
[-- Attachment #1: Type: text/plain, Size: 1075 bytes --]
Hi,
That option I've been dreaming about for a long time!
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?
Some quick script (WIP) to calculate that stats based on build system.
<https://debbugs.gnu.org/cgi/bugreport.cgi?bug=74268>
There is no much work after "guix refresh -u <go-package>" when I've
refreshed Golang packae.
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.
--
Oleg
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next reply other threads:[~2024-12-03 14:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-03 14:01 Sharlatan Hellseher [this message]
2024-12-14 23:51 ` Automatically testing package updates 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=875xo0q319.fsf@gmail.com \
--to=sharlatanus@gmail.com \
--cc=guix-devel@gnu.org \
--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).