On 2016-06-23 01:04 -0400, Eric S. Raymond wrote:
> Eric S. Raymond :
> > ./waf configure --enable-debug-gdb fails. gdb complains of not being
> > able to see dany debugging symbols.
>
> Never mind, second try worked. Maybe I fat-fingered someting.
Strange, any ideas as to the conditions you we
On 2016-06-26 23:49 -0700, Hal Murray wrote:
> $ ./waf --list
> --- building host ---
> The cache directory is empty: reconfigure the project
That looks like a regression I will look at it this morning, strange.
Amar.
___
devel mailing list
devel@ntps
On 2016-08-03 13:35 -0700, Gary E. Miller wrote:
> Yo All!
>
> I just tried to compile ntpsec on a new gentoo install. It failed.
There is a ticket for this I will try to get my patch in soon.
Amar.
___
devel mailing list
devel@ntpsec.org
http://list
On 2016-08-09 15:58 +, Mark Atwood wrote:
> This looks great, Christian.
>
> Is there anything we need to do to have our buildbot system test it?
I will take a look at this later on and let you know.
Amar.
___
devel mailing list
devel@ntpsec.org
h
On 2016-08-11 08:11 -0400, Eric S. Raymond wrote:
> This is a heads-up to Amar.
>
> As part of the effort to rewrite ntpq in Python, I have renamed the old
> pylib/ directory to wafhelpers/ and created a new pylib/ that contains
> an installable Python module. (The rename is to maintain paralleli
On 2016-08-11 09:04 -0400, Eric S. Raymond wrote:
> How is it the entire build? There are lots of wscript files not in there...
That's the source designation files, all the logic is in the former 'pylib' dir.
> 'wafbuild' was in fact my first choice. Can't use it; there's a collision
> with
>
On 2016-08-11 21:28 +, Mark Atwood wrote:
> It is time for another point release.
>
> I've received enough private communications from people who are successfuilly
> running lab machines on tip, and people who are successfully running lab
> machines on the previous point release, and that my w
On 2016-08-19 10:41 -0400, Eric S. Raymond wrote:
> This is heads-up to Amar.
>
> I need the waf recipe modified so that the contents of pylib is
> installed as a Python module named 'ntp'.
>
> (Right now this is for the packet module. I intend to move
> the ntpstats.py used by ntpviz there as w
On 2016-01-24 19:40 +0800, Sanjeev Gupta wrote:
> Hi,
>
> Looking at: https://buildbot.ntpsec.org/#/builders , I see no slaves with
> gcc5.
>
> Amar, I can set some up, if it would help.?? debian/testing or
> ubuntu/16/04-dev
I can set that up thanks for the suggestion I've added it to the lis
On 2016-01-24 09:38 -0600, Daniel Poirot wrote:
> Do we have a Linux host with external access yet?
>
> The Coverity Scan service is down right now.
I can work on that I have added it to the list I will let you know after I
finish migrating Buildbot.
Amar.
I've added a release mode to the build. The instructions are in the commit
message. This lowers the barrier for entry for using NTPSec and ensures our
tested versions work the same for the public.
I'll be enabling snapshots using BuildBot and uploading them to ftp.ntpsec.org
for users that wa
Sorry for the late response tried to organise a little and procmail threw this
into the wrong folder.
I'm currently working on and will still be working on:
* Expanding workers under Buildbot
- The old operating systems are back up just need to be enabled. I'm
waiting for this unti
In 7d8b2d1 utmpx.h was always assumed to be available. This is not true as
OpenBSD does not have utmpx support.
There is no point in hoping for utmpx support in OpenBSD either I won't repeat
the discussions here but there are plenty on the OpenBSD lists.
Can someone look at this please and bri
On 2016-02-05 21:30 -0800, Hal Murray wrote:
>
> I took a quick look. It won't be hard to put that stuff back, but it's
> typical of the sort of code that Eric ripped out for good reasons.
If we had known OpenBSD was going to be tossed out with it we would have kept
it
-- you're right it was
On 2016-02-06 10:11 -0800, Hal Murray wrote:
>
> Does buildbot have an OpenBSD machine?
Yes, I will hook it up to BuildBot as soon as this problem is fixed.
> Do we have a way to test on RTEMS?
Working on this not sure what the ETA is.
Amar.
___
de
On 2016-02-06 14:34 -0500, Eric S. Raymond wrote:
>
> OK. With that context, I think this stopped being a real issue a long time
> ago.
> Nobody bills by login time these days because pay-for-play timesharing is
> as dead as disco. It stopped making sense when personal worstations connected
> by
Nevermind Hal already removed it.
Amar.
___
devel mailing list
devel@ntpsec.org
http://lists.ntpsec.org/mailman/listinfo/devel
On 2016-02-10 11:32 -0800, Hal Murray wrote:
>
> >From a NetBSD box:
> Checking for header sys/timex.h: not found
> Compilation check failed but include exists sys/timex.h
> Checking for header sys/audio.h: not found
>
>
> On NetBSD and FreeBSD 9, sys/timex.
Cross compiling works. Usage is really simple:
waf configure --cross-compiler=/path/to/cross/cc
Use --cross-cflags and --cross-ldflags as necessary.
I'll be hooking up an ARM cross build to buildbot that will download and run on
one of the RPI2s I have here to ensure the cross compiling actu
On 2016-02-11 21:25 -0600, Joel Sherrill wrote:
>
> How does it derive the name of the cross compiler? There is nothing there
> about
> the target.
That is something that is needed for auto* to work correctly. Right now we
don't make any platform-based assumptions that I know of.
Amar.
On 2016-02-12 03:12 -0800, Hal Murray wrote:
> > Cross compiling works. Usage is really simple:
>
> Great/congrats.
Thanks!
> I think it would be great if you wrote up a HOWTO type document, including
> the setup stuff and the required (if any) cflags and ldflags. I think any
> combination
On 2016-02-12 11:02 -0800, Hal Murray wrote:
> I think there are two things I'm looking for. One is the concepts. The
> other is the details. Text that I can cut/paste cover the details. It
> probably takes a sentence or two to explain the concept.
>
> It can be as simple as "Install the co
On 2016-02-21 21:53 +, Mark Atwood wrote:
> Hi!
>
> Unless there is reason not to, I will tag and release version 0.9.3 on
> Tuesday.
Wednesday would be better just to give an extra day of leeway. I will aim for
Tuesday (2016-02-23).
> Amar: are you confident in the cross compile work?
On 2016-02-21 15:39 -0800, Hal Murray wrote:
>
> As far as I can find, perl is only used by a couple of utilities that are not
> part of the build process.
>
> Is it even worth checking for it at all?
When I first started the build I wanted to make sure we compiled NTP classic
1:1. It's a sof
On 2016-02-21 18:53 -0800, Hal Murray wrote:
>
> v...@darkbeer.org said:
> > When I first started the build I wanted to make sure we compiled NTP classic
> > 1:1. It's a soft dependency now you can add mandatory=False to the check.
>
> What do we gain by leaving it in at all?
Eventually I wan
On 2016-02-29 19:23 +, Mark Atwood wrote:
> - what is the status of the buildbot farm?:
> ?? - what new targets have been added?
> ?? - are we still all green for release?
> - what is the status of the start of the waf-replay branch?
> - what other things have you been working on this week?
So
On 2016-03-08 20:50 +0800, Sanjeev Gupta wrote:
> At www.ntpsec.org , could there be a link to the tarballs??? Or is this
> something to be done at 1.0 ?
We don't currently have tarballs however I did add support for a release mode
which will let us have real tarballs with pre-generated manpages
On 2016-03-13 22:51 -0700, Hal Murray wrote:
> The first is bleeding edge. Developers can grab the latest from git. In
> this context, testers count as developers even if they don't write any code.
> Support consists of going forward. Old releases are never fixed. They are
> supported onl
On 2016-03-15 01:46 -0700, Hal Murray wrote:
> I'm not sure what you have in mind for "test results". How is a non-wizard
> going to be able to evaluate anything other than a yes/no, and we will
> already have filtered out the no-s.
That is all they need to know really. The purpose of the test
On 2016-03-18 15:25 -0700, Hal Murray wrote:
> I think I have figured out part of the disconnect on some of the recent
> discussion.
>
> There are two types of releases. I'll call them "big" and "little". Does
> anybody have suggestions for better terms?
>
> A little release is no big deal.
On 2016-03-22 17:49 -0700, Hal Murray wrote:
> Has anybody seen this? Or hints on how to debug it?
>
> --- installing host ---
> Waf: Entering directory `/home/murray/ntpsec/play/ted3/host'
> Waf: Leaving directory `/home/murray/ntpsec/play/ted3/host'
> --- installing main ---
> Waf: Entering d
I have added snaphots to Buildbot.
When all of our primary builders pass it will generate a snapshot. This
snapshot is built in release-mode so Bison or asciidoc aren't needed.
Snapshots will appear here:
https://ftp.ntpsec.org/pub/snapshots/
Amar.
_
There is now a builder for ARM64 cross compiling:
https://buildbot.ntpsec.org/#/builders/40
I will be setting up MIPS as well.
Eventually the binaries will be archived and shipped to real ARM and MIPS
devices to run the testsuite and make sure the binaries work.
Amar.
__
On 2016-03-23 14:02 -0700, Hal Murray wrote:
>
> Nice. Thanks.
>
> v...@darkbeer.org said:
> > Snapshots will appear here:
> > https://ftp.ntpsec.org/pub/snapshots/
>
> How long will they stay around?
I will write a crontab to keep the last 50 or so files then move the rest to
archive/snap
On 2016-03-23 15:25 -0700, Hal Murray wrote:
> > I will be setting up MIPS as well.
>
> Do you have any wrong-endian systems in your collection? That would be high
> on my list.
Got some examples? I'll see what I can do. I really want to keep all of this
low-heat and low-power I may be able
On 2016-03-23 16:32 -0700, Hal Murray wrote:
>
> v...@darkbeer.org said:
> >> Do you have any wrong-endian systems in your collection?
> >> That would be high on my list.
>
> > Got some examples? I'll see what I can do. I really want to keep all of
> > this low-heat and low-power I may be able
>From my commit message:
Bump version to 0.9.3.
devel shouldn't be at 0.9.2 still as it has already been released. This will
make the snapshots easier to understand as users are always testing the next
release not the current.
Amar.
___
devel mai
I've created milestones on the ticket tracker and placed all the previous
tickets to each miletone with each respective version.
If we close any tickets that are open now please set the milestone to 0.9.3.
Amar.
___
devel mailing list
devel@ntpsec.org
On 2016-03-24 21:47 -0700, Hal Murray wrote:
>
> v...@darkbeer.org said:
> > devel shouldn't be at 0.9.2 still as it has already been released. This
> > will make the snapshots easier to understand as users are always testing the
> > next release not the current.
>
> 0.9.3 isn't right either.
On 2016-03-24 23:18 -0700, Hal Murray wrote:
>
> I don't see how the next version is any better than the previous one. It may
> seem that way to you, but it will be just as logical to somebody else who
> gets started the other way.
Because what is in master right now *is* 0.9.3. It's very com
On 2016-03-25 09:47 -0400, Eric S. Raymond wrote:
> Amar Takhar :
> > Advancing the version stops that confusion.
>
> Another praxtice often used is to append "+" to the version after a release.
Oh? I've never heard of that interesting. I will throw that in it can
On 2016-03-25 13:51 -0700, Hal Murray wrote:
> > So, ntpd 0.9.2-afceec0+
>
> I'd put the + right after the 2:
> ntpd 0.9.2+afceec0 or ntpd 0.9.2+ if you build without git.
>
> My normal mode of operation is to have a master copy on one system, rsync to
> other systems dropping the .git directo
On 2016-03-28 15:23 +, Mark Atwood wrote:
> Good morning, everybody.
>
> I am on my way to the Linux Foundation Collaboration Summit, where I will be,
> among other things, representing NTPsec.
Sounds great! Please keep us posted! :)
> Tomorrow morning will be another metronomic 0.9.* vers
On 2016-03-29 12:25 -0700, Hal Murray wrote:
>
> It would be nice if waf was smart enough to recompile version at all the
> right times. It might miss some case. I mostly use a script that rm-s the
> build directory so I haven't had problems.
Can you elaborate on this please? Are you talking
Does anyone have any suggestions for commits that should have regression tests?
Typically we'd do this off of a bug report so what I will do is open a ticket
first then write a test for it.
Not all suggestions will be suitable I want to have these as examples for
anyone
wanting to write a re
Does anyone here have any reference clocks they're not using? I'm looking for
different clocks to test as many of the refclock drivers as possible.
I have some RF shielded boxes here and GPS signal generators so I can build my
own GPS signals then test for reception on the other side. I do ske
On 2016-04-08 12:34 -0700, Hal Murray wrote:
>
> v...@darkbeer.org said:
> > My initial tests will be via PPS signals wired to the GPIO pins on RPIs.
> > This will only let me test one type of refclock driver. I should be able
> > to find something to test audio, too.
>
> Actually, that lets
On 2016-04-08 13:20 -0700, Hal Murray wrote:
>
> v...@darkbeer.org said:
> > OK that's good news at least. I haven't looked into many of the refclock
> > drivers. Thanks for the info.
>
> Keep in mind that many of the drivers have sub-drivers or modes.
Right, I will use code coverage to ensur
On 2016-04-08 13:49 -0700, Hal Murray wrote:
> Why do you think it will be more reliable? It's the same idea. Changing a
> signal on a pin generates an interrupt which wanders through a few layers of
> bit testing and dispatching and eventually gets to the PPS code that grabs
> the time.
Beca
On 2016-04-08 20:44 -0700, Hal Murray wrote:
> I haven't had any troubles with serial ports. (other than not finding them
> on modern systems)
Individually they're fine. Once you start scaling and doing testing they can
be
pretty frail. I spent a lot of time fighting bad serial ports, driver
On 2016-04-15 17:57 +, Mark Atwood wrote:
> Hi!
>
> I have just ordered a batch of the Navisys GR-701-W USB connected GPS
> receivers.?? They are probably at least 5 weeks from delivery to my
> hackerspace. When they arrive, I will ship some to some NTPsec people, and
> then put the rest u
I'm confused at the first commit for the replay branch. I was expecting it to
be after the first conversion of the repository.
Is there a reason that 69ddfd9 was used?
Amar.
___
devel mailing list
devel@ntpsec.org
http://lists.ntpsec.org/mailman/list
On 2016-05-03 02:43 -0700, Hal Murray wrote:
> > Does anyone here have any reference clocks they're not using? I'm looking
> > for different clocks to test as many of the refclock drivers as possible.
>
> What's your current collection?
I don't have any right now other than the various GPS chip
Before I start pushing some of the major changes to make the 'replay' branch
happen I need a few questions answered:
- Is it easier to edit the source for renamed defines to match current or
should I add compat shims.
- Will the source layout change almost immediately to match current or sh
On 2016-05-05 14:59 -0700, Gary E. Miller wrote:
> Yo All!
>
> Found a bug in NTPsec git head.
Whoa, thanks. Can you open a ticket for this please?
I will take care of it tonight or first thing in the morning.
Amar.
___
devel mailing list
devel@ntps
On 2016-05-05 17:24 -0700, Gary E. Miller wrote:
>
> Gotta link to your bug tracker?
Sorry, I should have provided that:
https://gitlab.com/groups/NTPsec/issues
Amar.
___
devel mailing list
devel@ntpsec.org
http://lists.ntpsec.org/mailman/listinfo/
This is fixed sorry for the delay I forgot to push!
Amar.
___
devel mailing list
devel@ntpsec.org
http://lists.ntpsec.org/mailman/listinfo/devel
On 2016-05-12 11:57 -0400, Eric S. Raymond wrote:
> Push-to-update of eweb pages has stopped working.
>
> Amar, would you please fix this?
Really? Strange, looking at it now.
Amar.
___
devel mailing list
devel@ntpsec.org
http://lists.ntpsec.org/mailm
On 2016-05-12 11:57 -0400, Eric S. Raymond wrote:
> Push-to-update of eweb pages has stopped working.
It appears to have worked fine:
https://buildbot.ntpsec.org/#/builders/13/builds/45
The changes are there, too:
https://www.ntpsec.org/getting-involved.html
I think maybe your browser cach
On 2016-05-14 18:42 +, Mark Atwood wrote:
> Hi!
>
> It is looking like its time for the next release.?? Baring a stop, I will tag
> it
> 0.9.3 and release on Tuesday, 2016-05-17, during OSCON.
>
> Please avoid checking in any major changes until after then.
>
> Hal, Daniel, Eric, Amar, plea
On 2016-05-27 19:30 +, Mark Atwood wrote:
> Hello Amar,
>
> Is there a ntpsec.org SMTP server? ?? ??Google and O365 are starting to clamp
> down harder on sending emails with From addresses other than theirs.
No there isn't but there can be if it is needed using SSL + password auth you
want
On 2016-05-30 01:36 +, Mark Atwood wrote:
> I would like to be able to send email from mark.atw...@ntpsec.com??from my
> usual
> email clients.?? Google used to let one prove that you owned an address, and
> then add it to the set from From addresses one could send from.?? Some time
> ago,
>
On 2016-05-31 17:03 -0700, Gary E. Miller wrote:
> Yo All!
>
> I just installed Gentoo stable on a Pi3 and pullef ntpsec git head.
>
> No joy. This is with Python 3.4. Ideas anyone?
Not designed to work with Python 3.4. I will try to fix this tomorrow. Can
you
open a ticket for this, please
Just noticed you opened a ticket I'll figure it out thanks!
Amar.
___
devel mailing list
devel@ntpsec.org
http://lists.ntpsec.org/mailman/listinfo/devel
On 2016-06-10 18:16 -0700, Gary E. Miller wrote:
> Yo Webmaster!
>
> Soemthing marginal about the ntpsec.org SSL cert, as seen by Wheezy:
I have no idea what's going on. Our certificate is signed by GlobalSign. I
checked from multiple hosts it works fine.
Amar.
__
On 2016-06-10 19:12 -0700, Gary E. Miller wrote:
> Yo Amar!
>
> "One of the root or intermediate certificates has expired (115 days ago)"
I see what's going on, I will fix this tomorrow, it the cert in Apache.
Thanks for pointing it out, this would not have been fixed going with a
different reg
I went ahead and fixed this for www.ntpsec.org I will fix it for all other
services tomorrow. A certificate got left in the chain I was using I have
removed it.
Amar.
___
devel mailing list
devel@ntpsec.org
http://lists.ntpsec.org/mailman/listinfo/de
On 2016-06-10 19:30 -0700, Gary E. Miller wrote:
>
> Qualys still gives it an F.
>
> https://www.ssllabs.com/ssltest/analyze.html?d=ntpsec.org&latest
For a seperate issue. The one you reported has been fixed.
I'll take care of this tomorrow.
Amar.
On 2016-06-17 09:35 -0400, Eric S. Raymond wrote:
> I created a testfarm/index.txt master, but pushing it doesn't publish
> a testfarm/index.html page.
It wasn't setup to install files in subdirectories I have fixed this.
Amar.
___
devel mailing list
d
69 matches
Mail list logo
