Heads up, Mark! Need a policy check from you wearing your
external-relations hat.
In response to GitLab issue $471: Default to python3...
https://gitlab.com/NTPsec/ntpsec/issues/471
...I just added the following to our advice for packegers.
.
Yo Eric!
On Tue, 20 Mar 2018 11:30:33 -0400 (EDT)
"Eric S. Raymond via devel" wrote:
> The shebang lines in our Python scripts point to "python". Part of
> our standard tests check that you can change that to "python3" without
> breaking anything.
Uh, no, you break Gentoo. gentoo allows a use
Gary E. Miller via devel :
> On Tue, 20 Mar 2018 11:30:33 -0400 (EDT)
> "Eric S. Raymond via devel" wrote:
>
> > The shebang lines in our Python scripts point to "python". Part of
> > our standard tests check that you can change that to "python3" without
> > breaking anything.
>
> Uh, no, you b
Yo Eric!
On Tue, 20 Mar 2018 12:58:28 -0400
"Eric S. Raymond" wrote:
> Gary E. Miller via devel :
> > On Tue, 20 Mar 2018 11:30:33 -0400 (EDT)
> > "Eric S. Raymond via devel" wrote:
> >
> > > The shebang lines in our Python scripts point to "python". Part
> > > of our standard tests check t
Yo All!
The email below is from the time-nuts mailing list, forwarded to there
from Dr. Levine. I think he works for NIST, or similar.
The discussion is about an NTP server set to UT1, not UTC. So now
we have UTC, UT1, and several varieties of leap smear being served over
NTP.
Currently I am p
Gary said:
> Currently I am playing with a Javad GPS that lets you set your PPS to GPS,
> SBAS, GLONASS, GALILEO, BeiDou, QZSS, IRNSS, UTC(USNO), UTC(SU), UTC(SBAS),
> UTC(GALILEO), UTC(BeiDou), UTC(QZZSS) or UTC(IRNSS)
What is the theoretical spread on all those different flavors of time? How
I would prefer to see a ./waf configure option (with the default being
some sort of autodetection). That is, I want to be able to do something
like this:
./waf configure --with-python=/usr/bin/python3
Given that this option has been rejected, I think what you have is
reasonable.
--
Richard
On Tue, Mar 20, 2018 at 01:55:20PM -0500, Richard Laager via devel wrote:
> I would prefer to see a ./waf configure option (with the default being
> some sort of autodetection). That is, I want to be able to do something
> like this:
>
> ./waf configure --with-python=/usr/bin/python3
>
> Given th
Yo Richard!
On Tue, 20 Mar 2018 13:55:20 -0500
Richard Laager via devel wrote:
> I would prefer to see a ./waf configure option (with the default being
> some sort of autodetection). That is, I want to be able to do
> something like this:
>
> ./waf configure --with-python=/usr/bin/python3
It a
On 03/20/2018 01:59 PM, Matthew Selsky wrote:
> Sorry, I'm confused. Why has this option been rejected?
Eric S. Raymond just wrote, "I think your objection to having waf futz
with them is sound."
> Also, Richard, as you speaking as a distro packager, or as an individual?
In this case, both. It
On 03/20/2018 02:02 PM, Gary E. Miller via devel wrote:
>> I would prefer to see a ./waf configure option (with the default being
>> some sort of autodetection). That is, I want to be able to do
>> something like this:
>>
>> ./waf configure --with-python=/usr/bin/python3
> It already does that.
It
On 03/20/2018 02:58 PM, Gary E. Miller via devel wrote:
> How does it handle multiple Pythons at the same time?
Python is a specific example of the generalized problem of wanting two
different versions of the same software installed at the same time. That
generalized problem is solved by versionin
Yo Richard!
On Tue, 20 Mar 2018 15:48:37 -0500
Richard Laager via devel wrote:
> On 03/20/2018 02:58 PM, Gary E. Miller via devel wrote:
> > How does it handle multiple Pythons at the same time?
>
> Python is a specific example of the generalized problem of wanting two
> different versions of
Yo Eric!
On Tue, 20 Mar 2018 17:19:38 -0400
"Eric S. Raymond via devel" wrote:
> Richard Laager via devel :
> > On 03/20/2018 01:59 PM, Matthew Selsky wrote:
> > > Sorry, I'm confused. Why has this option been rejected?
> >
> > Eric S. Raymond just wrote, "I think your objection to having
I've read the thread.
We will not do shebang munging for Python versioning.
This is something for the distro packagers to do. I understand that it
makes some work for Debian (and thank you for doing that!), but I like the
Debian patch that does it: it's big, bright, clear and obvious what it's
>
> About time the NTP told the user what time is being served?
>
Yes.
It should got into an extension block.
Two, one for time base, one for PPS source. What is the natural length of
an extension block? My preference is a US-ASCII string or a UTF8 string,
instead of a binary enum. "UTC", "U
>> About time the NTP told the user what time is being served?
>Yes.
> It should got into an extension block.
It seems like a wild goose chase to me. We should focus on distributing UTC.
> It should got into an extension block.
> Two, one for time base, one for PPS source. ...
The PPS idea is
>From packaging/packaging.txt
> The shebang lines in our Python scripts point to
> "python". Part of our standard tests check that
> you can change that to "python3" without breaking
> anything.
What sort of testing is that? How do I run it on my setup?
--
These are my opinions. I hate spam
Yo Hal!
On Tue, 20 Mar 2018 21:03:45 -0700
Hal Murray via devel wrote:
> From packaging/packaging.txt
>
> > The shebang lines in our Python scripts point to
> > "python". Part of our standard tests check that
> > you can change that to "python3" without breaking
> > anything.
>
> What sort
Yo Hal!
On Tue, 20 Mar 2018 16:57:58 -0700
Hal Murray via devel wrote:
> >> About time the NTP told the user what time is being served?
>
> >Yes.
> > It should got into an extension block.
>
> It seems like a wild goose chase to me. We should focus on
> distributing UTC.
I'm fine with th
20 matches
Mail list logo
