> When I made the debug log changes you asked for last night, I was
> thinking the same thine. A lot of duplication.
> After release we should rip and shred that.
Sounds good to me.
--
These are my opinions. I hate spam.
___
devel mailing lis
Yo Hal!
On Sat, 05 Apr 2025 15:13:53 -0700
Hal Murray via devel wrote:
> Is there any reason to have a DPRINT next to a msyslog that prints
> the same stuff?
>
> DPRINT is only useful if you are running with -n and msyslog stuff
> goes to the console too in that case. Right?
When I made the d
Is there any reason to have a DPRINT next to a msyslog that prints the
same stuff?
DPRINT is only useful if you are running with -n and msyslog stuff goes to
the console too in that case. Right?
--
These are my opinions. I hate spam.
___
deve
> Change pushed.
Thanks.
+Alternatively you can create a link your python3 called python. Assuming
Looks like a "to" got lost.
create a link your
create a link to your
> > > Should we fix waf install to do the magic for SELinux?
...
> Gentoo, Ubuntu, and others, do SELinux. BUt not by def
>> On FreeBSD, ./buildprep -n says:
>> pkg install bison python3
>> ln -s /usr/local/bin/python3 /usr/local/bin/python
>> pkg install ca_root_nss
>> I think the ln step is bogus. So I'll remove it.
> What makes you think it's bogus? Aside from whether it's best to point
> to 'python3' or t
On Wednesday, March 26, 2025 11:09:51 AM Pacific Daylight Time Hal Murray
wrote:
> If somebody is still using Python 2, do they have to manually fix the link
> from waf to point to the old waf? Or is there some magic that takes care
> of that?
THERE IS NO MAGIC HERE, nor any fancy Python tricks.
On Sun, 30 Mar 2025, Fred Wright wrote:
On Sun, 30 Mar 2025, James Browning via devel wrote:
On Sunday, March 30, 2025 4:44:51 PM Pacific Daylight Time Fred Wright via
devel wrote:
I'm not sure what you mean by "my patches", given that I've never
submitted any for this issue, though I'd sugge
What's the story on new waf install directories vs old waf directories?
Do we need to change the code and/or fix the documentation?
Is there anything else we need to sort out before a release?
--
These are my opinions. I hate spam.
___
devel mai
> A lot of changes in the last few days.
Nothing has changed in the core ntpd code in a long time.
Many of the recent changes have been in documentation.
I've improved buildprep. It's still pretty crappy but nobody was
somplaining.
> Some I am not happy about.
Anything specific?
> I sug
Yo Hal!
On Wed, 02 Apr 2025 23:05:55 -0700
Hal Murray wrote:
> > Best to educate the user to debug his own Python issues.
>
> Have you looked at README-PYTHON?
Nope. Non standard file name. Why would anyone look there?
Actually, who ever reads any of the doc??
> I thought it was pretty g
Yo Hal!
On Thu, 03 Apr 2025 21:41:02 -0700
Hal Murray wrote:
> >> Have you looked at README-PYTHON?
> > See attached.
>
> Looks good. Thanks.
I'll have more Friday. Mostly references.
RGDS
GARY
---
Gary E. Miller Re
On Monday, March 17, 2025 4:52:25 PM Pacific Daylight Time Hal Murray via devel
wrote:
> Back in 2018, I did some work on getting ntpd to start as ntp:ntp
> There was a way on Linux to set some capabilities on a file.
>
> Somebody talked me/us out of this. I don't remember why.
>
> I've poked a
On Monday, March 24, 2025 3:12:44 PM Pacific Daylight Time Hal Murray via devel
wrote:
> What's the story on new waf install directories vs old waf directories?
The pylib/wscript has been changed so that the egg-info, and all .py files in
pylib are installed in PYTHONDIR (see MR 1450)
TLDR PYTH
If somebody is still using Python 2, do they have to manually fix the link
from waf to point to the old waf? Or is there some magic that takes care
of that?
--
These are my opinions. I hate spam.
___
devel mailing list
devel@ntpsec.org
https://l
14 matches
Mail list logo
