From: Vagrant Cascadian <vagrant@debian.org>
To: guix-devel@gnu.org
Cc: Sharlatan Hellseher <sharlatanus@gmail.com>
Subject: python-dbus-python changes triggered many rebuilds
Date: Fri, 01 Nov 2024 17:20:51 -0700 [thread overview]
Message-ID: <874j4q7afw.fsf@wireframe> (raw)
[-- Attachment #1: Type: text/plain, Size: 1332 bytes --]
A large rebuild was triggered by:
commit a9abf9a7b30f6801e122cae759df87b44c458773
Author: Sharlatan Hellseher <sharlatanus@gmail.com>
Date: Fri Nov 1 21:10:04 2024 +0000
gnu: python-dbus-python: Fix indentation.
* gnu/packages/python-xyz.scm (python-dbus-python): Fix indentation,
adjust order of fields, sort inputs alphabetically.
Change-Id: I895518f041bd2cfc9c2f94774a9d1db47b26ffc3
Guix refresh claims this would trigger 3987 builds on x86_64-linux, and
ci is cranking away at over 13000 builds across several architectures:
https://ci.guix.gnu.org/eval/1772855
Anyone able to cancel that evaluation?
I pushed a commit reverting the ordering changes, which I think appears
to not trigger the rebuild:
commit ea11d3608566174c4bae70faa4f9d0c67748d2db
Author: Vagrant Cascadian <vagrant@debian.org>
Date: Fri Nov 1 16:55:02 2024 -0700
gnu: python-dbus-python: Revert ordering change on native-inputs.
A large number of rebuilds (3987 according to guix refresh) was triggered by:
a9abf9a7b30f6801e122cae759df87b44c458773 gnu: python-dbus-python: Fix
indentation.
Reverting the ordering changes does not trigger any rebuilds.
* gnu/packages/python-xyz.scm (python-dbus-python): Unsort native-inputs.
Hopefully that was the right thing to do!
live well,
vagrant
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
next reply other threads:[~2024-11-02 0:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-02 0:20 Vagrant Cascadian [this message]
2024-11-02 2:13 ` python-dbus-python changes triggered many rebuilds Ian Eure
2024-11-02 9:15 ` Ricardo Wurmus
2024-11-02 8:16 ` Sharlatan Hellseher
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=874j4q7afw.fsf@wireframe \
--to=vagrant@debian.org \
--cc=guix-devel@gnu.org \
--cc=sharlatanus@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).