From: Antonio Terceiro <firstname.lastname@example.org>
To: Eric Wong <email@example.com>
Cc: Hleb Valoshka <firstname.lastname@example.org>, email@example.com
Subject: Re: [PATCH] test/test_linux.rb: use plain ASCII in tempfile name
Date: Tue, 23 Feb 2016 08:00:09 -0300 [thread overview]
Message-ID: <20160223110009.GB31015@softwarelivre.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1385 bytes --]
On Tue, Feb 23, 2016 at 01:51:38AM +0000, Eric Wong wrote:
> Hleb Valoshka <firstname.lastname@example.org> wrote:
> Hleb: please reply-to-all, we don't require subscription
> since moving off librelist. This also prevents the list server
> being a single-point-of-failure(-or-censorship).
> > On 2/22/16, Antonio Terceiro <email@example.com> wrote:
> > > On Debian, this fixes the build against ruby2.3, which otherwise fails
> > > with errors like:
> > >
> > > RegexpError: /.../n has a non escaped non ASCII character in non ASCII-8BIT
> > > script
> > > - tmp = Tempfile.new("\xde\xad\xbe\xef") # valid path, really :)
> > > + tmp = Tempfile.new('raindrops')
> > I suspect that such names were created intentionally, so your patch
> > may not be correct.
> Right; raindrops should work with any paths the FS may throw at it.
I did realize it was on purpose, but didn't have the time to dig it the
root cause and wen't with the easiest fix I could find.
> I posted an alternate RFC patch for this problem a few weeks ago:
> I'm tempted to apply the above as Ruby might continue with existing
> Antonio: thoughts?
Works for me as well.
Antonio Terceiro <firstname.lastname@example.org>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 820 bytes --]
next prev parent reply other threads:[~2016-02-23 11:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-22 17:49 [PATCH] test/test_linux.rb: use plain ASCII in tempfile name Antonio Terceiro
2016-02-22 18:28 ` Hleb Valoshka
2016-02-23 1:51 ` Eric Wong
2016-02-23 11:00 ` Antonio Terceiro [this message]
2016-02-29 12:47 ` Eric Wong
2016-03-01 12:01 ` Antonio Terceiro
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:
List information: https://yhbt.net/raindrops/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).