From: ludo@gnu.org (Ludovic Courtès)
To: 宋文武 <iyzsong@member.fsf.org>
Cc: guix-devel@gnu.org
Subject: Re: Gnome-updates
Date: Wed, 27 Apr 2016 16:58:47 +0200 [thread overview]
Message-ID: <87d1pb14k8.fsf@gnu.org> (raw)
In-Reply-To: <87r3dr3yyc.fsf@member.fsf.org> ("宋文武"'s message of "Wed, 27 Apr 2016 22:31:39 +0800")
iyzsong@member.fsf.org (宋文武) skribis:
> ludo@gnu.org (Ludovic Courtès) writes:
>
>> Andreas Enge <andreas@enge.fr> skribis:
>>
>>> the gnome-updates branch has built on x86, and compared to master, there are
>>> not that many regressions:
>>> http://hydra.gnu.org/eval/108921?compare=master#tabs-now-fail
>>
>> In fact this slightly overestimates the failures compared to master; in
>> particular, all the Octave/Fltk-related failures are already in master.
>>
>>> I saw a few that seem to be related to fonts and freetype, but I am not
>>> a specialist. Do you think we could nevertheless merge back to master?
>>> In any case, it would be nice if people who are competent in these matters
>>> could have a look at the few remaining build failures.
>>
>> Since ‘make assert-binaries-available’ passed, I went ahead and merge
>> the branch.
> Oh, luckily the merge doesn't have effect.
>>
>> If anything goes wrong, please let us know!
> Sorry, this is still not ready yet!
Indeed! I screwed things up in two ways: I didn’t revert the reverts,
meaning the merge had not effect, and because of this, I failed to
realize that things that were broken before were still broken. My bad!
Specifically, Mark told me that at least these important packages fail
to build: evolution-data-server, gedit, gnome-control-center,
gnome-session, gtkmm, totem, mupdf.
> I have skip a gjs test temporary, and disable the spell plugin of
> gedit. I'd continue to work on the gnome-updates branch, and will
> reply to this thread when it's ok.
OK!
Thanks, and sorry all for the mess!
Ludo’.
next prev parent reply other threads:[~2016-04-27 14:58 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-26 17:37 Gnome-updates Andreas Enge
2016-04-27 13:11 ` Gnome-updates Ludovic Courtès
2016-04-27 14:31 ` Gnome-updates 宋文武
2016-04-27 14:58 ` Ludovic Courtès [this message]
2016-04-27 19:33 ` Gnome-updates Ludovic Courtès
2016-04-30 8:33 ` Gnome-updates 宋文武
2016-05-02 8:17 ` Gnome-updates Ludovic Courtès
2016-05-02 14:47 ` Gnome-updates 宋文武
2016-05-02 18:35 ` Gnome-updates Leo Famulari
2016-05-03 0:38 ` Gnome-updates 宋文武
2016-05-03 17:32 ` Gnome-updates Efraim Flashner
2016-05-03 21:07 ` Gnome-updates Leo Famulari
2016-05-03 11:35 ` Gnome-updates Ludovic Courtès
2016-05-11 8:08 ` Gnome-updates Andreas Enge
[not found] <20170513232810.28268.54349@vcs0.savannah.gnu.org>
2017-05-14 12:45 ` gnome-updates Ludovic Courtès
2017-05-14 15:35 ` gnome-updates Marius Bakke
2017-05-14 17:04 ` gnome-updates Leo Famulari
2017-05-24 20:17 ` gnome-updates Marius Bakke
2017-05-24 21:07 ` gnome-updates Leo Famulari
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=87d1pb14k8.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=iyzsong@member.fsf.org \
/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).