emacs-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[debbugs-tracker] bug#35539: closed (Add more release testing automation


From: GNU bug Tracking System
Subject: [debbugs-tracker] bug#35539: closed (Add more release testing automation for Guix releases)
Date: Sat, 18 May 2019 12:04:02 +0000

Your message dated Sat, 18 May 2019 14:03:02 +0200
with message-id <address@hidden>
and subject line Re: bug#35539: Add more release testing automation for Guix 
releases
has caused the debbugs.gnu.org bug report #35539,
regarding Add more release testing automation for Guix releases
to be marked as done.

(If you believe you have received this mail in error, please contact
address@hidden)


-- 
35539: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=35539
GNU Bug Tracking System
Contact address@hidden with problems
--- Begin Message --- Subject: Add more release testing automation for Guix releases Date: Fri, 3 May 2019 10:50:53 +0200 User-agent: NeoMutt/20180716
mate-applets failed to build multiple times in the Guix 1.0 ISO, so
MATE cannot be installed.  I guess I should have tested more before
release; not much can be done about it now (you may close this bug if
really not much can be done), however maybe a more thorough testing
checklist or automation may be helpful for future releases.



--- End Message ---
--- Begin Message --- Subject: Re: bug#35539: Add more release testing automation for Guix releases Date: Sat, 18 May 2019 14:03:02 +0200 User-agent: Gnus/5.13 (Gnus v5.13) Emacs/26.2 (gnu/linux)
Hello,

Ludovic Courtès <address@hidden> skribis:

> I agree we need more automation here.  One way to do this would be
> something like ‘make assert-binaries-available’, which checks for
> substitute availability (it could be a prerequisite of ‘make dist’),
> where we’d explicitly check for DEs on x86_64 and i686.

I did that in 762ba22efe01006d959503dc368ee54b16ccea31; 1.0.1 will
definitely have substitutes for MATE, GNOME, etc.

There’s surely still room for improvement in that area, but let’s open
more specific bugs as we see fit.

Thanks,
Ludo’.


--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]