From: ng0 <ng0@we.make.ritual.n0.is>
To: Leo Famulari <leo@famulari.name>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: tor: Update to 0.2.8.7.
Date: Fri, 26 Aug 2016 10:58:47 +0000 [thread overview]
Message-ID: <87a8fzokyg.fsf@we.make.ritual.n0.is> (raw)
In-Reply-To: <87h9a7zu1n.fsf@we.make.ritual.n0.is>
ng0 <ng0@we.make.ritual.n0.is> writes:
> Leo Famulari <leo@famulari.name> writes:
>
>> [ Unknown signature status ]
>> On Wed, Aug 24, 2016 at 07:32:52PM +0000, ng0 wrote:
>>> Updates tor to 0.2.8.7, released.. today? yesterday? Well, recently.
>>
>> Thanks, pushed as ec9be00fc.
>>
>>> Question: why is perl not a native-input for tor? I see some
>>> version-update.pl complaining update it but not fatally failing.
>>
>> It looks like 'scripts/main/updateVersions.pl' is a tool used by the Tor
>> maintainers when preparing new releases of Tor. I'm not sure about the
>> other script in that directory, 'checkOptionDocs.pl'.
>>
>> Should we add Perl?
>
> maybe, I can't be certain until I've added and run it.
> https://gitweb.torproject.org/tor.git/tree/scripts/maint/checkOptionDocs.pl.in
>
> I will do so today.
I think this perl script is not even used in the standard check phase.
Maybe it is used in the full-check phase, which we might be able to add
once we have all the applications this phase requires (stem, and some
more) if we want/can run test-full.
--
ng0
For non-prism friendly talk find me on http://www.psyced.org
next prev parent reply other threads:[~2016-08-26 10:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-24 19:32 [PATCH] gnu: tor: Update to 0.2.8.7 ng0
2016-08-24 20:12 ` Leo Famulari
2016-08-26 10:47 ` ng0
2016-08-26 10:58 ` ng0 [this message]
2016-08-26 23:24 ` Leo Famulari
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=87a8fzokyg.fsf@we.make.ritual.n0.is \
--to=ng0@we.make.ritual.n0.is \
--cc=guix-devel@gnu.org \
--cc=leo@famulari.name \
/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).