From: "Clément Lassieur" <clement@lassieur.org>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel@gnu.org
Subject: Re: packages which are broken after core-updates merge
Date: Tue, 04 Apr 2017 16:10:03 +0200 [thread overview]
Message-ID: <87pogs2ric.fsf@lassieur.org> (raw)
In-Reply-To: <87y3vg31s7.fsf@elephly.net>
Ricardo Wurmus <rekado@elephly.net> writes:
> Clément Lassieur <clement@lassieur.org> writes:
>
>>> Clément Lassieur transcribed 0.2K bytes:
>>>> > icecat is failing, with new profiles, with old profiles. This can be
>>>> > reproduced in a new profile by selecting 'Preferences > Applications'.
>>>> > It should immediately crash.
>>>>
>>>> It doesn't crash when "--with-system-icu" is removed.
>>>
>>> Can you send a patch for this?
>>
>> Sure, but I'm not sure it is the right solution. It would be preferable
>> to use system libraries when we can. What the other think?
>
> This usually indicates that upstream forked the library (or that the
> depend on this particular version of the API). I think it’s better to
> comment the configure flag with a FIXME and have a version of Icecat
> that is usable than a version of Icecat that immediately crashes when
> you start it.
>
> In any case I think it would be good to file a bug report upstream with
> information about the exact version of ICU that we’re building with.
See https://debbugs.gnu.org/cgi/bugreport.cgi?bug=26361.
next prev parent reply other threads:[~2017-04-04 14:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-03 16:40 packages which are broken after core-updates merge ng0
2017-04-03 23:10 ` Clément Lassieur
2017-04-04 8:30 ` ng0
2017-04-04 8:23 ` Clément Lassieur
2017-04-04 10:28 ` Ricardo Wurmus
2017-04-04 12:40 ` Clément Lassieur
2017-04-04 14:10 ` Clément Lassieur [this message]
2017-04-04 12:17 ` Ludovic Courtès
2017-04-04 12:39 ` Clément Lassieur
2017-04-04 14:12 ` Ricardo Wurmus
2017-04-04 14:56 ` ng0
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=87pogs2ric.fsf@lassieur.org \
--to=clement@lassieur.org \
--cc=guix-devel@gnu.org \
--cc=rekado@elephly.net \
/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.