From: Ken Brown <kbrown@cornell.edu>
To: cygwin-apps@cygwin.com
Subject: Re: [ITA] perl-Error, perl-Locale-gettext, perl-Win32-GUI, perl-libwin32
Date: Fri, 13 Mar 2015 10:55:00 -0000 [thread overview]
Message-ID: <5502C226.2060003@cornell.edu> (raw)
In-Reply-To: <871tktrfbq.fsf@Rainer.invalid>
On 3/12/2015 7:00 PM, Achim Gratz wrote:
> Achim Gratz writes:
>> Ken, would you still know if the Log-Log4Perl and Text-BibTeX tests were
>> clean previously? I'm getting what looks like an encoding problem from
>> Text-BibTeX and an offset in some file sizes(?) for Log-Log4Perl.
No, sorry. I don't even know for sure if I ran the tests.
> The "offset" seems to be a file mode check that doesn't work due to me
> being an administrator. Text-BibTeX tests clean in the stage2 build, so
> there's either a dependency cycle or missing dependency somewhere. In
> any case, it looks good to me now.
>
> Lastly, could you please check if Biber really needs the obsolete
> File-Slurp-Unicode or couldn't just depend on File-Slurp instead?
The current upstream Biber depends on File-Slurp. But it also requires
Perl 5.16 or later, so I won't be able to rebuild it and get rid of the
dependency on File-Slurp-Unicode until you update Perl in May.
Ken
next prev parent reply other threads:[~2015-03-13 10:55 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-12 11:31 Achim Gratz
2015-03-12 13:03 ` Eric Blake
2015-03-12 13:11 ` Ken Brown
2015-03-12 16:28 ` Yaakov Selkowitz
2015-03-12 18:44 ` Achim Gratz
2015-03-12 22:44 ` Achim Gratz
2015-03-12 23:01 ` Achim Gratz
2015-03-13 10:55 ` Ken Brown [this message]
2015-03-13 21:50 ` Achim Gratz
2015-03-12 23:56 ` Jon TURNEY
2015-03-13 6:13 ` Achim Gratz
2015-03-13 14:34 ` Jon TURNEY
2015-03-13 9:36 ` Corinna Vinschen
2015-03-13 19:21 ` Yaakov Selkowitz
2015-03-13 19:40 ` Achim Gratz
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=5502C226.2060003@cornell.edu \
--to=kbrown@cornell.edu \
--cc=cygwin-apps@cygwin.com \
/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.
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).