unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: "Clément Lassieur" <clement@lassieur.org>
To: ng0 <contact.ng0@cryptolab.net>
Cc: 26462@debbugs.gnu.org
Subject: bug#26462: Fix crashes in programs using system ICU
Date: Fri, 14 Apr 2017 01:01:08 +0200	[thread overview]
Message-ID: <87d1cf6hfv.fsf@lassieur.org> (raw)
In-Reply-To: <20170412114756.wsr2bqlkq2herafh@abyayala>

ng0 <contact.ng0@cryptolab.net> writes:
> Clément Lassieur transcribed 0.8K bytes:
>> ng0 <contact.ng0@cryptolab.net> writes:
>> 
>> > Clément Lassieur transcribed 0.1K bytes:
>> >> The first patch fixes system ICU.  This allows Icecat to use system ICU
>> >
>> > Cool :)
>> >
>> >> without crashing, and it also fixes crashes in 0ad, which I'm working
>> >> on.
>> >> 
>> >> 
>> >> 
>> > Woooo. You picked up my 0ad work (or started from scratch)? I was stuck on mozjs38 for an eternity
>> > and gave up.
>> > Do you need further help or something? I unpublished the repo this was
>> > in, so the last progress isn't public.
>> 
>> :-) I picked up your work, of course.  The mozjs issue is fixed (a patch
>> that was applied to the bundled mozjs had to be applied to the system
>> mozjs we use), and with this ICU patch, I can play!  I just played for
>> 5min without a problem.  I just need to cleanup things, to package NVTT
>> (did you do it?), and then I can send the patch.
>
> Wow :) That is so exciting... really. And you only get to add the
> package on top of every package list "0" and "a" once :D

Cool! ;)

> I don't want to sound pushy or anything, I don't even know how much I
> messed up or not, but it would be cool to mention me as co-authored
> depending on the code :)
> If you don't do it, it's fine aswell because I'm so happy you picked it up!

Of course I'll do it!  You did most of the work :)

> No, I left NVTT as "to do". But when I had an github account, I made
> Nvidia publish a new release for NVTT. So it's just a matter of
> packaging the NVTT dependencies. This should not block the 0ad package
> commit in my opinion. As no release happened for a long time - until I requested them to
> do so - every project which makes use of NVTT just bundled a working state of NVTT.

Ok, so I'll let it as is if you think it's fine.

      reply	other threads:[~2017-04-13 23:02 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-12 10:48 bug#26462: Fix crashes in programs using system ICU Clément Lassieur
2017-04-12 10:53 ` bug#26462: [PATCH 1/2] gnu: icu4c: " Clément Lassieur
2017-04-12 10:53   ` bug#26462: [PATCH 2/2] gnu: icecat: Use " Clément Lassieur
2017-04-12 11:51   ` bug#26462: [PATCH 1/2] gnu: icu4c: Fix crashes in programs using " Ludovic Courtès
2017-04-14 14:51     ` bug#26462: [PATCH] " Clément Lassieur
2017-04-16  9:54       ` Ludovic Courtès
2017-04-17 18:45         ` Clément Lassieur
2017-04-14 14:55     ` bug#26462: [PATCH 1/2] " Clément Lassieur
2017-04-14 14:59       ` Clément Lassieur
2017-04-14 15:18         ` Ludovic Courtès
2017-04-12 10:55 ` bug#26462: " Clément Lassieur
2017-04-12 11:22 ` ng0
2017-04-12 11:31   ` Clément Lassieur
2017-04-12 11:42     ` Clément Lassieur
2017-04-12 11:53       ` ng0
2017-04-13 22:53         ` Clément Lassieur
2017-04-12 11:47     ` ng0
2017-04-13 23:01       ` Clément Lassieur [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

  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=87d1cf6hfv.fsf@lassieur.org \
    --to=clement@lassieur.org \
    --cc=26462@debbugs.gnu.org \
    --cc=contact.ng0@cryptolab.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 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).