From: Michael Zucchi <notzed@gmail.com>
To: "Julien Lepiller" <julien@lepiller.eu>,
"Björn Höfling" <bjoern.hoefling@bjoernhoefling.de>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: icu4j, antlr4, source archives without a root path
Date: Mon, 6 Jul 2020 11:13:21 +0930 [thread overview]
Message-ID: <ca1d4ba8-03ee-79ce-b45f-304e45e1b1ff@gmail.com> (raw)
In-Reply-To: <20200705142005.1bc30e5d@tachikoma.lepiller.eu>
Hi there,
Sorry. I've lost completely any interest in guix (and all else
computer/software related) so do with it and any other patches I sent
what you will.
Regards,
Michael
On 5/7/20 9:50 pm, Julien Lepiller wrote:
> Le Sun, 28 Jun 2020 22:41:35 +0200,
> Julien Lepiller <julien@lepiller.eu> a écrit :
>> Hi,
>>
>> I took your patch and changed it a bit to enable tests. They require
>> JUnitParams, which we don't have, as well as some work to actually be
>> able to run the tests without having the package try to download
>> anything.
>>
>> Attached are two patches, that add java-junitparams and that update
>> icu4j with the proper sources.
>>
>> I also tried to use the git repository, but that failed because three
>> data archive files come from git-lfs and are not fetched by git-fetch,
>> so I kept using the release tarball instead. I've rebuilt the few
>> packages listed by guix refresh successfully.
>>
>> WDYT?
> Since there was no answer to this, I pushed the patches as
> 52a23d8e4872f5cb313d4456fc3e4c56280a2918 and
> ee1dc9b3d19364e17b15a158194cddfff91778c8.
>
prev parent reply other threads:[~2020-07-06 1:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-11 0:29 icu4j, antlr4, source archives without a root path Michael Zucchi
2020-05-12 21:57 ` Björn Höfling
2020-06-28 20:41 ` Julien Lepiller
2020-07-05 12:20 ` Julien Lepiller
2020-07-06 1:43 ` Michael Zucchi [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=ca1d4ba8-03ee-79ce-b45f-304e45e1b1ff@gmail.com \
--to=notzed@gmail.com \
--cc=bjoern.hoefling@bjoernhoefling.de \
--cc=guix-devel@gnu.org \
--cc=julien@lepiller.eu \
/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).