From: Marius Bakke <mbakke@fastmail.com>
To: Pierre Neidhardt <mail@ambrevar.xyz>, 39318-done@debbugs.gnu.org
Subject: bug#39318: [core-updates] 'make-desktop-entry-file' is not exported
Date: Thu, 30 Jan 2020 22:35:11 +0100 [thread overview]
Message-ID: <877e18ocfk.fsf@devup.no> (raw)
In-Reply-To: <8736bwrd60.fsf@ambrevar.xyz>
[-- Attachment #1: Type: text/plain, Size: 1230 bytes --]
Pierre Neidhardt <mail@ambrevar.xyz> writes:
> Marius Bakke <mbakke@fastmail.com> writes:
>
>> Obviously the CI system can not offer substitutes in advance for a
>> world-rebuilding change! :-)
>>
>> I feel slightly offended by being asked to try your untested patch. Are
>> you under the impression that I _don't_ have to rebuild the world?
>
> Duh, my bad, sorry I was probably too distracted with other things at
> Guix Days, I completely missed that the world obviously had to be rebuilt.
> I guess I'm not used to dealing with core-updates :p
>
> Actually, this brings up a genuine question: how do you test core-updates
> for these type of changes? Do we really have a rebuild the whole thing on
> every iteration?
Changing (guix build utils) is an extreme case, but pretty much. I keep
a TODO list of things I want to do on that branch, and once it gets big
enough, I try to implement all at once before starting the Big Rebuild.
Then go do something else until a node in the graph fails to build.
Berlin typically has substitutes all the way up to 'guix', so it's "not
that bad" unless you are changing the really low layers.
> Cheers, and sorry for the mishaps!
No worries, and sorry for the angry comment. :-)
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
prev parent reply other threads:[~2020-01-30 21:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-27 23:40 bug#39318: [core-updates] 'make-desktop-entry-file' is not exported Marius Bakke
2020-01-28 7:47 ` Pierre Neidhardt
2020-01-29 10:34 ` Marius Bakke
2020-01-29 11:12 ` Pierre Neidhardt
2020-01-30 15:49 ` Pierre Neidhardt
2020-01-30 16:12 ` Marius Bakke
2020-01-30 18:51 ` Pierre Neidhardt
2020-01-30 21:35 ` Marius Bakke [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=877e18ocfk.fsf@devup.no \
--to=mbakke@fastmail.com \
--cc=39318-done@debbugs.gnu.org \
--cc=mail@ambrevar.xyz \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.