I learned today that Guix will chug happily along applying a transform to a
nonexistent package.
For example, I can run:
guix environment --with-latest=not-exist --ad-hoc which
This shows no warning or errors. I think it would be beneficial to show an
error & bail if the target of a
br...@waegenei.re writes:
> Today I pushed 2 commits¹ related to the package to master, mainly to
> update it to 2.33.0. But since then https://data.guix.gnu.org/ went
> offline and Cuirass' evaluation #4930² has 556 failed build. Newly
> failed builds have unhelpful logs, ending with "cannot
Hello,
br...@waegenei.re writes:
> Hello Guix,
>
> Today I pushed 2 commits¹ related to the package to master, mainly to update
> it to 2.33.0. But since then https://data.guix.gnu.org/ went offline and
> Cuirass' evaluation #4930² has 556 failed build. Newly failed builds have
> unhelpful
Hello Guix,
Today I pushed 2 commits¹ related to the package to master, mainly to update it
to 2.33.0. But since then https://data.guix.gnu.org/ went offline and Cuirass'
evaluation #4930² has 556 failed build. Newly failed builds have unhelpful
logs, ending with "cannot build missing
Hi,
On Wed, 28 Jul 2021 at 13:50, Mathieu Othacehe wrote:
> A new core-updates-frozen branch is available here:
> https://git.savannah.gnu.org/cgit/guix.git/log/?h=core-updates-frozen.
Cool!
> Your help is welcome :).
What is the schedule for the merge?
(I am back from holidays. :-))
[-bug, +devel]
Mario, Guix,
On 2021-08-17 11:13, Mario Domenech Goulart wrote:
(I tried to post this comment via the form in
http://issues.guix.gnu.org/22366 , but apparently that hasn't worked --
trying e-mail now)
Thank you for mentioning this, or I would have assumed it had been fixed
by
Hi Tobias,
On Tue, 29 Jun 2021 at 16:40, Tobias Geerinckx-Rice wrote:
> Question: I think committers should be trusted with discretion in
> how they prefer to manage their keys, but how about briefly
> documenting a suggested sane key-management strategy to new
> committers, like we already
