On Wed, 11 Sep 2024, Hal Murray via devel wrote:
I'm trying to cleanup the tangle in ntp_control.c that generates warnings.
They may be actual bugs. The problem is that the man page says long while
the actual size may be 32 or 64 on 32 bit Linux systems.
If I knew the size, the fix would be
On Sat, 7 Sep 2024, Hal Murray via devel wrote:
Does #ifdef work on functions? I thought not, but the old code looks like
its doing that.
It only works when the apparent functions are macros. The preprocessor
knows nothing about functions.
On Sat, 7 Sep 2024, Hal Murray via devel wrote:
On Tue, 25 Jun 2024, Hal Murray via devel wrote:
$ grep rtems wscript */wscript wafhelpers/*
wscript:if ctx.options.enable_rtems_trace:
wscript:ctx.find_program("rtems-tld", var="BIN_RTEMS_TLD",
wscript: path_list=[ctx.options.rtems_trace_path,
wscript:# Bor
On Fri, 21 Jun 2024, Hal Murray via devel wrote:
Does anybody other than me run/test on NetBSD?
Ocasionally. I have a NetBSD 6.1.5 VM.
The test-all part of option-tester gets the following error.
Why only in option-tester?
ntp_stdlib includes signal.h
Do we have to do some magic to ma
On Thu, 2 May 2024, Hal Murray via devel wrote:
Note that for AT&T, the normal case of an NTP client goes through NAT so
NTP isn't using port 123 and doesn't get blocked.
Many, if not most, NAT implementations avoid remapping "privileged" client
ports, on the theory that specific port numbe
On Wed, 3 Jan 2024, Matthew Selsky wrote:
On Tue, Jan 02, 2024 at 08:52:53PM -0800, Fred Wright via devel wrote:
It should, though if the timestamps get updated in the process it would
trade bad name ordering for bad timestamp ordering. The ideal thing would
be to fix the names but keep the
On Tue, 2 Jan 2024, Hal Murray via devel wrote:
Fred Wright said:
[context is my reply to the released message.]
For some reason the antecedent to this message wasn't sent to the list,
though I'd noticed the release by checking the repo.
My copy was sent to:
Subject: NTPsec 1.2.3 released
On Wed, 3 Jan 2024, Matthew Selsky wrote:
On Tue, Jan 02, 2024 at 07:21:39PM -0800, Fred Wright via devel wrote:
There are a couple of minor issues that I should have noticed in the RC but
didn't:
1) The 1.2.2a entry is missing from NEWS. This is presumably because of the
way the
On Sat, 30 Dec 2023, Hal Murray via devel wrote:
Thanks.
and thanks to all who contributed and tested.
For some reason the antecedent to this message wasn't sent to the list,
though I'd noticed the release by checking the repo.
There are a couple of minor issues that I should have notic
On Mon, 25 Dec 2023, Fred Wright via devel wrote:
Commit 07231d10e2 to add cipher-find also added exp-timing.c to the build
list but didn't actually add a source for it. Thus the attic build fails.
It probably makes sense to fix this before the release since it's a
regressio
Commit 07231d10e2 to add cipher-find also added exp-timing.c to the build
list but didn't actually add a source for it. Thus the attic build fails.
It probably makes sense to fix this before the release since it's a
regression and also doesn't affect any normally installed components, and
On Thu, 21 Dec 2023, Hal Murray wrote:
Let's put that stuff on the back burner until the release is out.
Agreed for OpenBSD per se, though it might be worth trying to determine
whether the apparent fencepost error with OPENSSL_VERSION_NUMBER is really
OpenBSD-specific, or a more general pr
On Thu, 21 Dec 2023, Fred Wright via devel wrote:
I found one build error that's a regression - in OpenBSD 5.6. It's
"'CMAC_CTX' undeclared" in authreadkeys.c, which is due to the new
conditional around the inclusion of . Some other sources
include this unc
I found one build error that's a regression - in OpenBSD 5.6. It's
"'CMAC_CTX' undeclared" in authreadkeys.c, which is due to the new
conditional around the inclusion of . Some other sources
include this unconditionally, and macencrypt.c has it in an if/else
construct. The else case there
On Mon, 18 Dec 2023, Hal Murray via devel wrote:
James said:
It sounds like a race condition in our wscript files or waf. How willing are
you to sink time into this, I think it's a losing proposition.
I've got a --jobs=1 in my script. That was added to make sure the printout
was easy to rea
On Mon, 18 Dec 2023, Fred Wright wrote:
On Mon, 18 Dec 2023, Matthew Selsky wrote:
On Sun, Dec 17, 2023 at 08:17:23PM -0800, Fred Wright via devel wrote:
There are also a bunch of warnings with some compilers, which might be
worth
looking at. They're often fairly easy to fix, and some
it would be heavy-handed
for the normal build procedure. Or even having CI tests both ways might
be useful, to distiguish between errors and warnings. Though if CI tests
had the ability to report error versus warning results, that would be
unnecessary.
On Mon, 18 Dec 2023, Matthew Selsky w
On Wed, 6 Dec 2023, Matthew Selsky via devel wrote:
Sounds good. I'll aim to release ~15-Dec-2023.
Fortunately this hasn't happened yet. :-)
The main issue I've found is that the "struct var" in ntp_control.c, is
relying on anonymous unions, which are a relatively new language feature.
Th
On Sat, 18 Nov 2023, Fred Wright via devel wrote:
[...]
With or without this problem, it's a bad idea to combine multiple
unrelated changes into a single MR anyway. It's best to stick to one
topic per branch, both locally and in any MRs derived from such
branches.
I neglected t
In general, it's a good idea to read an actual book on git, rather than
trying to understand it purely through manpages. The one I used (almost a
decade ago) is this one:
https://www.amazon.com/gp/product/1449316387/
It doesn't tell you everything you might want to know, but it cov
On Fri, 4 Aug 2023, James Browning via devel wrote:
On 08/04/2023 6:35 PM PDT Fred Wright via devel wrote:
:::snip:::
I notice that the two commits for that don't seem to be in any branch.
Having commits only "owned" by a tag and not a branch seems fragile.
I do
On Fri, 4 Aug 2023, Fred Wright via devel wrote:
On Fri, 4 Aug 2023, Matthew Selsky wrote:
On Fri, Aug 04, 2023 at 01:47:29PM -0700, Fred Wright via devel wrote:
And for that matter, what exactly is 1.2.2a, given that there's no git tag
for that version?
1.2.2a is 1.2.2 + the 2 line
On Fri, 4 Aug 2023, Matthew Selsky wrote:
On Fri, Aug 04, 2023 at 01:47:29PM -0700, Fred Wright via devel wrote:
And for that matter, what exactly is 1.2.2a, given that there's no git tag
for that version?
1.2.2a is 1.2.2 + the 2 line patch to avoid the crash. We'll releas
On Thu, 3 Aug 2023, Hal Murray via devel wrote:
Should that also go to users@ and devel@?
What fraction of people on users or devel are also on announce?
And for that matter, what exactly is 1.2.2a, given that there's no git tag
for that version?
Fred Wright
_
On Sun, 23 Jul 2023, Hal Murray via devel wrote:
git log on a fresh clone shows things like this:
Author: Hal Murray
Date: Tue Jul 4 15:16:47 2023 -0700
Squash warnings about not handled enumeration
I haven't used that email in ages. My profile has been updated. Mail from
gitlab goe
On Mon, 2 Jan 2023, folkert via devel wrote:
[...]
It makes it include the delay in the json output.
Note that the delay is not the full story in the time uncertainty. A
long-standing ntpdig bug is that it fails to include the dispersion. The
delay gives the uncertainty in the server->cl
On Tue, 3 Jan 2023, folkert wrote:
Lost me. What about sntp do you want to put on gitlab?
Oh, reading these in reverse order. I think you are offering to
add this as a Merge Request on GitLab? Yes, that would be good.
Can I please send the patch via e-mail? I've been struggeling with
gi
On Tue, 3 Jan 2023, folkert via devel wrote:
Lost me. What about sntp do you want to put on gitlab?
Oh, reading these in reverse order. I think you are offering to
add this as a Merge Request on GitLab? Yes, that would be good.
Can I please send the patch via e-mail? I've been struggeli
On Wed, 21 Dec 2022, Hal Murray via devel wrote:
Google says:
https://developers.google.com/time/smear
We encourage anyone smearing leap seconds to use a 24-hour linear smear from
noon to noon UTC.
There were earlier versions which did sine rather than linear.
Hmm. I don't recall any non
On Wed, 21 Dec 2022, Fred Wright via devel wrote:
On Wed, 21 Dec 2022, Hal Murray wrote:
I guess if you don't see the issue I'll have to look more closely; I
thought
you might "just know" the problem.
Does git head work on 3.0?
Yes. I think it gets confused when
On Wed, 21 Dec 2022, Hal Murray wrote:
f...@fwright.net said:
It's 1.1.1s, which is the latest 1.1. I don'think there's anything
nonstandard besides using versioned install locations so that multiple
versions can be installed side-by-side.
I poked around some more. I have it building and r
On Wed, 21 Dec 2022, Hal Murray wrote:
but if breaking OpenSSL 1.1 was unintentional, then it needs to be fixed
I'm not aware of any intententional breakage. I'm pretty sure we would have
done it at configure time.
I don't think *unintentional* breakage would be done at configure time.
On Wed, 21 Dec 2022, Hal Murray via devel wrote:
Does anybody use it?
Do any distros build with it enabled?
Should we add an "#warn untested" to the code?
If some systems need leap-smeared time to get around bugs in their code,
they should be free to implement an *internal* leap-smeared tim
The build currently fails when building againts OpenSSL 1.1. MacPorts is
currently building it that way since the last release failed to build
against OpenSSL 3 (due to the attic problem), though it should be able to
move to OpenSSL 3 on the next release. So it's not actually an issue for
On Wed, 21 Dec 2022, Matt Selsky via devel wrote:
This is only a 2 minute delay, if I converted all timestamps to UTC correctly.
My last post was delayed 11 minutes, which is longer than it should be,
but not awful.
I did find that a spammer was abusing our Mailman instance's web
interfa
On Mon, 19 Dec 2022, James Browning via devel wrote:
On 12/18/2022 6:02 PM PST Hal Murray via devel wrote:
The commit message for that is lacking the blank line after the summary
line. This means that some git tools treat the entire commit message as the
summary, creating obnoxiously long li
On Sat, 17 Dec 2022, Hal Murray via devel wrote:
I just pushed code to save 10 NTS keys used to make cookies.
The commit message for that is lacking the blank line after the summary
line. This means that some git tools treat the entire commit message as
the summary, creating obnoxiously l
On Thu, 15 Dec 2022, Matthew Selsky via devel wrote:
On Wed, Dec 14, 2022 at 03:39:29PM -0800, James Browning via devel wrote:
'Do not apply transform to symbolic link targets' [1] Which I
got from googling 'gnu tar transform' IIRC. It is also a
gnuism, but I do not see a portable transform t
On Thu, 8 Dec 2022, James Browning via devel wrote:
Selsky broke the build[1] back in May 2020 when switching the
python_scripts variable in /wscript to a set when Python 2.6
does not support sets. Given the lack of complaints, I suspect
no one uses 2.6 anymore, which can be dropped.
Python
On Tue, 15 Feb 2022, Hal Murray via devel wrote:
matthew.sel...@twosigma.com said:
Are we worried about the speed of the build, lack of build support on
particular platforms, or something else?
I'm not particularly concerned about the speed of a build. As far as I know,
nobody has complain
On Fri, 27 Aug 2021, MLewis via devel wrote:
"
A new set of patches submitted to the Linux kernel mailing list summarises
the progress of the project to enable Rust to be used alongside C for
implementing the Linux kernel.
[...]
"
There's a YouTube video of a talk on this subject. It's
On Sun, 14 Mar 2021, Hal Murray via devel wrote:
[Context is cleaning up ntp_control]
This will probably be simple after somebody gives me a good example and/or
explains things to me.
I want to put a (pointer to a) function in a field of a struct.
The type of that function includes a pointer
On Thu, 17 Dec 2020, Eric S. Raymond wrote:
James Browning via devel :
The ntpsec forks belonging to rlaager, selsky, and ianbreune are still
detached. A quick check shows that there are no forks. The page I looked at
claimed that such detached repositories cannot be reattached. TLDR there is
On Sat, 12 Dec 2020, James Browning via devel wrote:
On Sat, Dec 12, 2020, at 6:41 PM Gary E. Miller via devel
wrote:
Yo James!
On Sat, 12 Dec 2020 18:35:13 -0800
James Browning via devel wrote:
The following patch clears it up on the machine I bisected on.
No, that uses the installed
On Wed, 14 Oct 2020, Hal Murray via devel wrote:
I'm setting up a new Debian system. I'm far from a Debian wizard, but I'm not
a total newbie either.
I have a ntp.pth setup, so ntpq finds the python libraries.
[...]
File "/usr/local/lib/python3/dist-packages/ntp/ntpc.py", line 49, in _dlo
On Wed, 2 Sep 2020, Hal Murray via devel wrote:
As of 1.1.9, NTPsec doesn't build "normally" on Debian 7...
Debian 7 is pretty old. Support ended May 2018
Do we want to support versions of distros that the vendor doesn't support any
more? My vote would be no.
There are sometimes signifi
On Thu, 3 Sep 2020, Hal Murray wrote:
I don't see how to use your master/entry macros to solve my problem.
I didn't mean for those to be usable as is, but just as an illustration of
the concept. YMMV.
The current code has only one table but it needs a symbol for the offset of
each slot
On Sun, 30 Aug 2020, Hal Murray via devel wrote:
Is there any way to do something like
#define FOO $FOO+1
I want to keep track of the number of times a macro has been called. That
seems like something that would happen often enough that there would be a
standard recipe but I haven't seen it.
On Tue, 16 Jun 2020, Mike Simpson via devel wrote:
There is libressl from the OpenBSD team
https://www.libressl.org/
It was forked from openssl in 2014
The last time I tried it, libaes_siv wouldn't build with LibreSSL, so that
would need to be fixed. Unless LibreSSL provides an adequate A
On Thu, 16 Apr 2020, Hal Murray via devel wrote:
Because RS232 signaling is negative logic.
That's what I used to think, but somebody corrected me many years ago.
The data is upside down but the control signals are not.
From https://en.wikipedia.org/wiki/RS-232
under Voltage levels
For d
On Sat, 31 Aug 2019, Matthew Selsky wrote:
On Fri, Aug 30, 2019 at 08:01:59PM -0700, Fred Wright via devel wrote:
On Thu, 29 Aug 2019, Gary E. Miller via devel wrote:
Warnings on OSX:
[ 73/131] Compiling libntp/ntp_calendar.c
../../ntpd/ntp_control.c:2612:27: warning: format specifies
On Fri, 30 Aug 2019, Fred Wright via devel wrote:
On Thu, 29 Aug 2019, Gary E. Miller via devel wrote:
Warnings on OSX:
[ 73/131] Compiling libntp/ntp_calendar.c
../../ntpd/ntp_control.c:2612:27: warning: format specifies type 'unsigned
short' but the argument has type &#x
On Thu, 29 Aug 2019, Gary E. Miller via devel wrote:
Warnings on OSX:
[ 73/131] Compiling libntp/ntp_calendar.c
../../ntpd/ntp_control.c:2612:27: warning: format specifies type 'unsigned
short' but the argument has type 'unsigned int' [-Wformat]
socktoa(rmt_addr),
On Wed, 21 Aug 2019, Hal Murray via devel wrote:
ntpd/refclock_gpsd.c has:
#define _XOPEN_SOURCE 600
I see the following warning:
NetBSD:
../../ntpd/refclock_gpsd.c:2118:6: warning: implicit declaration of function
'strlcpy' [-Wimplicit-function-declaration]
FreeBSD:
../../ntpd/refclock_gps
On Fri, 16 Aug 2019, Eric S. Raymond via devel wrote:
Sanjeev Gupta :
sizeof(double) seems to be 8 bytes. The 8192 * No of Secs per week
overflows this.
Huh. If "long double" isn't 16 bytes, we're foing to have a problem.
There's no guarantee that long double differs from double. Anythi
On Mon, 22 Jul 2019, Gary E. Miller via devel wrote:
No one has a solid answer to the NTS ALPN issue?
"at some time the NTPSEC server would return "\x07ntske/1" instead of
just "ntske/1"."
Doesn't ring any BELs for me. :-)
All kidding aside, it's probably not a coincidence that \x07 is the
On Sun, 30 Jun 2019, Mark Atwood wrote:
The NTPsec Project is pleased to announce the tagging of version 1.1.5
I guess "tagging" is a good description given that the tarball doesn't
seem to have been published. :-)
Fred Wright
___
devel mailing
On Sun, 7 Apr 2019, Hal Murray wrote:
Does a simple void cast work? E.g.:
(void) strerror_r(...)
I haven't found the magic using that approach.
../../ntpd/nts.c:214:16: warning: ignoring return value of ???strerror_r???,
declared with attribute warn_unused_result [-Wunused-result]
On Sun, 7 Apr 2019, Eric S. Raymond via devel wrote:
Hal Murray via devel :
../../ntpd/nts.c:213:9: warning: ignoring return value of ???strerror_r???,
declared with attribute warn_unused_result [-Wunused-result]
I'm only getting this on Ubuntu, so a secondary question is why isn't that
check
On Wed, 20 Mar 2019, James Browning via devel wrote:
On Wed, Mar 20, 2019 at 6:30 PM Gary E. Miller via devel
wrote:
Yo All!
Something recently broke in NTPsec when using Python 3.6:
?
I thought I got that bug with?a4453ee5a4 "Fix polyglot library for Python3 on
NetBSD".
Wher
On Mon, 11 Mar 2019, Eric S. Raymond via devel wrote:
GPSes will roll over to their third era on April 6th.
Those of us with constellations of test GPSes will need to take time
to audit how much of our kit has gone toes-up. Maybe none of it
immedately, as manufacturers tend to pivod on their
On Sun, 10 Feb 2019, Hal Murray wrote:
What's involved in getting developer access to the Mac world?
It depends on what you mean by that. There are both free and paid
developer accounts. The free version gives you access to most of the
developer downloads. That's all I've ever used. I t
On Sat, 9 Feb 2019, Hal Murray via devel wrote:
I thought we got farther than this last night.
Does macos have OpenSSL? What version?
Stage: build
Name: macos-basic
Trace: ../../include/nts.h:7:10: fatal error: 'openssl/ssl.h' file not found
#include
^~~
1 error generat
On Tue, 29 Jan 2019, Gary E. Miller via devel wrote:
On Tue, 29 Jan 2019 19:01:40 -0800 (PST)
Fred Wright via devel wrote:
Well, the way we use sys.stdout is warned about in the Python doc.
That is enough for me to want it aligned with the python doc.
The real question is why the build
On Tue, 29 Jan 2019, Gary E. Miller via devel wrote:
On Tue, 29 Jan 2019 17:11:15 -0800
Hal Murray via devel wrote:
Gary said:
Update:
Works: 2.7, 3.7
Fails: 3.5, 3.6
It was working a week or two ago.
Yup.
Did we change anything? (I don't think so.)
Agreed, not in that area. I hav
On Sat, 25 Aug 2018, Hal Murray wrote:
Thanks.
https://gitlab.com/NTPsec/ntpsec/merge_requests/776
I approved the merge request, but I don't get anything new with git pull or a
fresh clone.
That just flags it as "approved", but doesn't actually merge it.
Is the "Merge" button active for
On Fri, 24 Aug 2018, Hal Murray via devel wrote:
On a PowerPC:
TEST(numtoa, RefidStr)../../tests/libntp/numtoa.c:19::FAIL: Expected
'68.51.34.17' Was '17.34.51.68'
It's probably a bug in the test code.
Yes, it is. The argument to refid_str() is expected to be in network byte
order, but t
On Sat, 23 Dec 2017, Hal Murray via devel wrote:
> Should it be included in a tarball?
> How about wafhelpers/.autorevision-cache?
>
> Should it be moved to $build/main/ntpd/, similar to the way that derived
> python files were moved to $build/main/pylib/?
I think it should, and I made a brief a
On Sat, 23 Dec 2017, Hal Murray wrote:
> > but isn't when compiled extensions like 'ntpc' are involved. Extensions
> > almost never work with a different Python that the one they were compiled
> > and linked for, with a variety of possible failure modes.
>
> Should ntpc.so get installed in the A
On Sat, 23 Dec 2017, Jason Azze via devel wrote:
> On Sat, Dec 23, 2017 at 5:47 PM, Hal Murray wrote:
> >
> >> I ran a ./waf distclean before my configure, build, install steps. I will
> >> try from a fresh clone.
> >
> >> Before I open a GitLab issue, is this unexpected behavior?
> >
> > It sure
On Wed, 20 Dec 2017, Richard Laager via devel wrote:
> Rather than debate hypotheticals further, I have submitted a merge
> request to implement the "option H" idea being discussed:
> https://gitlab.com/NTPsec/ntpsec/merge_requests/615
>
> I'm looking for feedback on that particular merge request
(from a different thread)
On Fri, 8 Dec 2017, Richard Laager via devel wrote:
> I agree that your system does not have /usr/local in its sys.path by
> default.
[...]
> 1) Ignore prefix and install to /usr. This is Fred Wright's solution and
> is what is seemingly the point of fix_python_config.p
On Sun, 10 Dec 2017, Eric S. Raymond via devel wrote:
> Ian Bruene via devel :
> > After reading over the discussion regarding the recent /issues/, I have come
> > to a side: Revert Fred's fix and throughly document the import breakage.
>
> Ugly, but simple. I'd like to hear counterargument from
On Wed, 6 Dec 2017, Ian Bruene via devel wrote:
> For installs the only remaining problem is that for unknown reasons it
> sometimes doesn't follow the PREFIX when installing the python libs.
There's nothing "unknown" about it. This has been discussed at length on
this ML, as well as being expl
On Wed, 29 Nov 2017, Eric S. Raymond wrote:
> Fred Wright via devel :
> >
> > On Sat, 25 Nov 2017, Hal Murray via devel wrote:
> >
> > > It seems like a good idea for somebody to actually test our code on a
> > > big-endian system.
> >
> > I&#x
On Sat, 25 Nov 2017, Eric S. Raymond via devel wrote:
> Hal Murray :
> > devel@ntpsec.org said:
> > > waf doesn't know that config.h exists; this is its way to pass
> > > configuration
> > > switches. The fact that we generate a config.h is really legacy behavior
> > > from autoconf and could b
On Sat, 25 Nov 2017, Hal Murray via devel wrote:
> It seems like a good idea for somebody to actually test our code on a
> big-endian system.
I've run it on my PowerBook (OSX 10.5), though I didn't attempt any
detailed analysis of the behavior. The clock offset had more wander than
I'd like, bu
On Wed, 29 Nov 2017, Ian Bruene via devel wrote:
>
> On 11/29/2017 04:17 PM, Hal Murray via devel wrote:
> > That link lets you test python code using the new libraries.
> >
> > In a previous version of that code, the link was in ntpclients and you could
> > run things by cd-ing there. Now the li
On Sat, 4 Nov 2017, Eric S. Raymond via devel wrote:
> * Fred and Gary need to have, and resolve, their argument about what to
> do to the build recipe around Python library installation. For
> concreteness, this should probably start with a proposed patch from
> Fred.
My existing patch h
On Mon, 30 Oct 2017, Hal Murray via devel wrote:
> fallenpega...@gmail.com said:
> > I suggest running it with gpsd for a while instead of NTPsec, and see if
> > gpsd's logging identifies the issue.
>
> > Or if the ntpd log contains the NMEA strings, it may be possible to
> > reconstruct a gpsd pl
On Thu, 19 Oct 2017, Eric S. Raymond via devel wrote:
> Fred, can we get an updaterd MR and rationale for your library-path
> fix proposal?
OK, here goes:
First of all, here's the case table for the "usability check" again:
Exists? In sys.path?Usable?
---
On Thu, 19 Oct 2017, Eric S. Raymond via devel wrote:
> Fred, can we get an updaterd MR and rationale for your library-path
> fix proposal?
Yes, but I'm about to go away for the weekend. I'll do that next week.
BTW, I do have an outstanding MR (561) for a minor doc fix that should be
non-contr
On Sat, 7 Oct 2017, Hal Murray wrote:
> > No, if "storing" includes the code that may clean up old library installs.
>
> Ahh... Thanks. That brings up a question I've been wondering about for ages.
>
> What sort of cleanup does waf install do? Is that documented anyplace?
I don't think instal
On Sat, 7 Oct 2017, Hal Murray wrote:
> >>> Should it also printout where it will install the python libraries?
> >> Good idea. I'd take that patch.
>
> > It's already there. Look at PYTHONDIR towards the end.
>
> Thanks.
>
> Is that used for anything other that storing python libraries?
No, i
On Sat, 7 Oct 2017, Gary E. Miller via devel wrote:
> On Sat, 7 Oct 2017 12:15:27 -0700 (PDT)
> Fred Wright via devel wrote:
>
>
> > Makes sense. Fedora is one of the systems where Python doesn't
> > include a "local" directory in the sys.path set
On Sat, 7 Oct 2017, Eric S. Raymond via devel wrote:
> Hal Murray via devel :
> > waf configure prints out:
> > PREFIX: /usr/local
> >
> > Should it also printout where it will install the python libraries?
>
> Good idea. I'd take that patch.
It's already there. Look
On Sat, 7 Oct 2017, Hal Murray via devel wrote:
> If I have PYTHONPATH defined as /usr/local/lib/python2.7/site-packages
> Then the python libs get installed in /usr/local/lib/...
> If I unset PYTHONPATH, they get installed to /usr/lib/...
Doh! (on Eric's behalf) That would be an unfortunate pr
On Thu, 5 Oct 2017, Hal Murray wrote:
> >> Warnings are easily lost in the noise. So either create the
> >> directory or treat it as an error and bail.
>
> > There are two issues with just "creating the directory":
> > 1) There's no guarantee that Python will actually use it.
> > 2) Creating the
On Fri, 6 Oct 2017, Eric S. Raymond via devel wrote:
> Fred Wright writes:
> >Sorry for the lateness, but I realized that the current code still has a
> >bug (as well as a couple of deficiencies of a more-or-less cosmetic
> >nature). It's currently checking sys.path in the *running* Python, but i
On Sun, 1 Oct 2017, Eric S. Raymond wrote:
> Fred Wright via devel :
> > On Sun, 1 Oct 2017, Eric S. Raymond via devel wrote:
> > > Gary E. Miller via devel :
> > > > How do you plan that a local NTPsec install from source does not
> > > > ove
On Sun, 1 Oct 2017, Eric S. Raymond via devel wrote:
> Gary E. Miller via devel :
> > How do you plan that a local NTPsec install from source does not
> > overwite an NTPsec install from the native OS repositories?
>
> That now will never happen if the /usr/local/lb/python-X.Y directory exists;
>
will require much more than just
> changes to get_python_lib().
Agreed.
On Thu, 28 Sep 2017, Gary E. Miller via devel wrote:
> On Wed, 27 Sep 2017 19:02:23 -0700 (PDT)
> Fred Wright via devel wrote:
>
> > One of the ways to do #1 is to use the path returned by
> > get_pyth
On Wed, 27 Sep 2017, Eric S. Raymond via devel wrote:
> Gary E. Miller via devel :
> > What we see that pip does, is edit the sys.path to include the
> > location an egg is installed. That looks to me like a method
> > to go forward with.
>
> It looks to me like a fscking disaster, introducing ye
On Wed, 27 Sep 2017, Gary E. Miller via devel wrote:
> Fred Wright via devel wrote:
> It only matters
> > for Linux, since get_python_lib() returns FHS-compliant results on
> > *BSD, and on OSX the paths are so completely different that FHS
> > doesn't apply.
&g
On Wed, 27 Sep 2017, Gary E. Miller via devel wrote:
>
> What we see that pip does, is edit the sys.path to include the
> location an egg is installed. That looks to me like a method
> to go forward with.
That sounds plausible, but we need to figure out how it does that. It's
not just about "ed
On Wed, 27 Sep 2017, Eric S. Raymond wrote:
> Fred Wright via devel :
> > FYI, I just took a look at sys.path on the three Linuces I have here
> > (Ubuntu, CentOS, and Fedora), and none of them has a single entry with
> > "local" as part of the path.
>
> I se
On Wed, 27 Sep 2017, Eric S. Raymond wrote:
> Fred Wright via devel :
> >
> > On Wed, 27 Sep 2017, Eric S. Raymond via devel wrote:
> >
> > > I've pushed a fix for Fred Wright's FixConfig class that seems to
> > > solve the problem of incorrect
On Wed, 27 Sep 2017, Fred Wright wrote:
> On Wed, 27 Sep 2017, Eric S. Raymond via devel wrote:
>
> > I've pushed a fix for Fred Wright's FixConfig class that seems to
> > solve the problem of incorrect Python library locations.
> >
> > I tested it with no --prefix option and with --prefix=/usr,
>
On Wed, 27 Sep 2017, Eric S. Raymond via devel wrote:
> I've pushed a fix for Fred Wright's FixConfig class that seems to
> solve the problem of incorrect Python library locations.
>
> I tested it with no --prefix option and with --prefix=/usr,
> using install --destdir=/tmp/ntp.
>
> Gary, please
On Tue, 26 Sep 2017, Eric S. Raymond wrote:
> Fred Wright via devel :
>
> > BTW, I have a tool that lists a few things including the library paths for
> > every version of Python it can find on the system. I can submit it to
> > devel/ if you like.
>
> Please d
1 - 100 of 127 matches
Mail list logo
