It looks like the --enable-doc waf configuration option was removed in the
commit "Add support for other asciidoc processors". Was there any discussion
about this change?
___
devel mailing list
devel@ntpsec.org
http://lists.ntpsec.org/mailman/listinfo/d
On Thu, Feb 14, 2019, at 12:56 PM, Eric S. Raymond via devel wrote:
> I've added a mandatory waf check for the libaes_siv library.
[snip]
> At some point it will probably be taken into OpenSSL and this separate
> dependency will go away.
Hmmm. I certainly understand why this is necessary to mov
On Sat, Feb 9, 2019, at 8:28 AM, Hal Murray via devel wrote:
> I thought we got farther than this last night.
>
> Does macos have OpenSSL? What version?
>
This (
https://stackoverflow.com/questions/43415106/openssl-conf-h-file-not-found-error-on-macos-sierra)
stackoverflow answer suggests it
Mostly for Ian, who was trying to recall where he left off with ntpsnmpd.
I had a working ntpsnmpd instance running on a workstation which has, sadly,
been consumed by entropy along with the rest of the assay I was using. However,
I do recall that I had a Cacti instance collecting data from ntps
On Fri, Oct 12, 2018, at 11:53 PM, Hal Murray via devel wrote:
> Context is de-bashing tests/option-tester.sh and tests/python3-tester.sh
Now that I got my home CI system up and running again, I see this fails for
Ubuntu 14, too.
[ubu14-test1] $ /bin/sh -xe /tmp/jenkins1012014110254104847.sh
+
On Mon, Nov 5, 2018, at 10:25 AM, James Browning via devel wrote:
> On Mon, Nov 5, 2018 at 7:03 AM Udo van den Heuvel via devel
> wrote:>>
>> When I googled PYTHONDARCHIR
Udo is pointing out that our PYTHONDARCHIR has its "D" in an odd place.
Looks like a typo.
___
On Fri, Aug 24, 2018, at 10:51 PM, 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.
>
I'm working, very very slowly, on setting up a CI runner o
On Mon, Aug 13, 2018, at 4:54 PM, Eric S. Raymond via devel wrote:
> That was my intent. I'll remove the comment and keep an ear out for any
> report
> of CentOS operation going sproing.
I updated #450 with a report of CentOS/RHEL behavior as I observed it this
morning.
___
On Tue, May 29, 2018, at 4:28 PM, Richard Laager via devel wrote:
> Choosing _which_ interfaces to listen() on at all is not userspace
> packet filtering.
This is my instinct as well. I suspect I don't understand what we're talking
about, so I am hesitant to comment.
Are you suggesting remov
I mentioned on the IRC channel that I was playing with a tool called Heaptrack,
which I read about on Hacker News, to search for why the memory footprint of
ntpd is (is it?) larger than we expect. I found a leak that ESR said looked
"pretty nasty." Because I have no idea what I'm doing with debu
On Wed, May 2, 2018, at 4:30 PM, Matthew Selsky via devel wrote:
> Maybe the docker images that clang-* and python-coverage are based on
I agree. It looks like the failing runs are all . . .
Using docker image
sha256:e7bdbd137f66d65e7cecae48f860acb0dbbfcfd3426d9282a16c3940f3fcf330 for
ruby:
On Sun, Mar 25, 2018 at 9:15 PM, Eric S. Raymond via devel wrote:
>
> A lot of typos got fixed when the GPSD repo moved off Savannah.
Did gpsd get moved off of Savannah? To where? I missed that.
___
devel mailing list
devel@ntpsec.org
http://lists.ntp
On Thu, Mar 15, 2018 at 7:09 PM, Sanjeev Gupta wrote:
> Jason, yes, that is the result of the bounty offer.
>
> I have not had a chance to play with it, but the offer included a
> requirement to upstream into cacti and provide a working example.
>
For reasons I can't explain yet, my Cacti server
On Fri, Mar 2, 2018 at 12:17 AM, Sanjeev Gupta wrote:
> Please see
>
> https://github.com/netniV/cacti-templates/tree/master/NTP
>
Sanjeev, was this template created in response to your bounty? I finally
worked through getting ntpsnmpd up and talking to AgentX on my test
machine, but all of my C
On Tue, Feb 27, 2018 at 3:46 PM, Hal Murray via devel wrote:
>
> What does "pages:deploy" do? On the diagram of all the steps, it's the lower
> of the pair on the right.
>
It looks like it is a CI job dedicated to:
python ./waf configure --enable-doc --prefix=/tmp/docbot-local
--htmldir=`pwd`/
On Mon, Feb 26, 2018 at 7:18 PM, Richard Laager via devel
wrote:
> On 02/26/2018 06:16 PM, Sanjeev Gupta wrote:
>> Richard, I am using cacti.
>
> That's what I was hoping to hear, since I also run Cacti. Are you
> willing to share your templates?
I'm also a Cacti user, though it has been years si
On Tue, Jan 9, 2018 at 10:26 AM, Ian Bruene via devel wrote:
>
> I have nearly finished filling out the MIB tree for SNMP. What gaps are left
> involve data I do not know how to get:
At the risk of sounding like a drop-out from a Scrum Master training
camp, could you explain briefly what the "sto
On Sun, Dec 24, 2017 at 3:02 PM, Fred Wright via devel wrote:
>
> The GPSD approach isn't necessarily ideal, but it's a lot less
> inconvenient than what ntpsec currently does.
Let's not copy exactly what gpsd does. I have bug #52661 "gpsd -V -
Different version strings generated between shallow
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 looks unexpected to me. There shouldn't be anything about 0.9.7
While freshening my NTPsec install to test the ntpq command history
bug, I accidentally ran ./waf install twice in a row because I thought
I had forgotten to run it at all. I thought I had forgotten because
ntpq -V still showed my old version 0.9.7+68.
On the second run, (which at the moment I tho
On Sat, Dec 23, 2017 at 3:24 PM, Eric S. Raymond via devel
wrote:
>
> This is highly annoying. We've done someting in our interpreter that busts
> that feature, but it is not obvious what. Perhaps the polyglot changes?
>
> I'll dig into this further when I get back from sword class
> --
>
I hap
On Wed, Dec 6, 2017 at 2:22 PM, Matthew Selsky via devel
wrote:
> We also don't have formal code reviews (before commit) since many devs push
> directly to "master". So we can't enforce any policies to code before they
> get committed to master.
>
> At some point, maybe soonish, can we stop pu
On Fri, Nov 24, 2017 at 2:51 AM, Hal Murray via devel wrote:
> Did this work before my change? Is somebody working on the gitlab stuff and
> my push just happened at the right time to uncover a bug?
I suspect this was a transient CI error or possibly related to work
Matt was doing at that time
Whoops. I failed to list reply.
On Mon, Nov 6, 2017 at 4:44 PM, Jason Azze wrote:
> On Sat, Nov 4, 2017 at 7:59 PM, Eric S. Raymond via devel
> wrote:
>> Here's my big question about the next year of development: should we
>> be moving the codebase out of C to Go?
>
> Would this be a direct tra
On Wed, Sep 27, 2017 at 4:19 PM, Eric S. Raymond via devel
wrote:
> Just to be sure, though, people with access to other platforms - like Red Hat
> and FreeBSD - should run these checks in Python
>
[x for x in sys.path if x.find('/usr/lib') != -1]
>
[x for x in sys.path if x.find('/usr/
On Wed, Sep 27, 2017 at 1:28 PM, Hal Murray via devel wrote:
> I'm getting duplicates of issue-closed messages from gitlab.
>
> Are you doing anything interesting? Is anybody else getting them?
I also got a duplicate on the ntpleapfetch closure message.
__
On Tue, Sep 26, 2017 at 5:35 AM, Eric S. Raymond via devel
wrote:
> Please, everybody get on the stick and test on every platform you can
> reach. We need to know that, *without* a PYTHONPATH set,
I tested CentOS 6.6. I used to have to export PYTHONPATH on this
platform. Now all tools in build/ma
27 matches
Mail list logo
