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 original timestamps. Three of the four
On Tue, Jan 02, 2024 at 08:55:38PM -0800, Fred Wright via devel wrote:
> That explains it. I don't subscribe to the announce list, based on the
> expectation that announcements would be cross-posted here. Cross-posting
> only needs to be done by the sender, while cross-subscribing would need to
On Tue, Jan 02, 2024 at 07:21:39PM -0800, Fred Wright via devel wrote:
Hi Fred,
> 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 patch release was forked off of the
On Wed, Dec 06, 2023 at 01:56:51AM +, Matthew Selsky via devel wrote:
> Sounds good. I'll aim to release ~15-Dec-2023.
Hi all,
Sorry for the delays. I have a release candidate tarball available:
https://ftp.ntpsec.org/pub/releases/ntpsec-1.2.3rc1.tar.gz
https://ftp.ntpsec.org/pub/relea
On Sun, Dec 17, 2023 at 08:17:23PM -0800, Fred Wright via devel wrote:
Hi Fred,
> 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.
> They were originally a GNU extension, eventually becoming
On Sat, Dec 02, 2023 at 08:09:00PM -0800, Hal Murray wrote:
>
> I think you should release what we have as soon as it is convenient.
>
> There are many more things I would like to include but we aren't making much
> progress so it's time to do it.
Hi Hal,
Sounds good. I'll aim to release
On Sun, Nov 26, 2023 at 11:43:14PM +, Hal Murray (--- via vc wrote:
> Hal Murray pushed to branch master at [1]NTPsec / ntpsec
>
> Commits:
>
> • [2]d98ce8d7
>by Hal Murray at 2023-11-26T15:42:51-08:00
>
> Fix mode 6 client to round up to 4 bytes (was 8)
>
> 1
On Sun, Oct 29, 2023 at 10:50:56PM -0700, Hal Murray via devel wrote:
>
> The last time this was suggested, I encouraged waiting until we fixed mssntp.
> Well, I think we have it fixed but we haven't found anybody to test it.
Sounds good. Can you please update NEWS.adoc with mssntp and other
On Thu, Oct 19, 2023 at 02:27:56PM -0700, Hal Murray via devel wrote:
> It works fine from my test program. What's different about ntpd?
Hi Hal,
Are you running ntpd with --jaildir (or -i) or some chroot-like functionality?
Cheers,
-Matt
___
devel
On Wed, Oct 18, 2023 at 09:37:06PM -0700, Hal Murray via devel wrote:
> I put the samba socket in /tmp/
> ntpd couldn't see it. My test programs work fine.
>
> 18 Oct 20:52:00 ntpd[5671]: SIGND: can not connect socket
> '/tmp/fake-samba-socket/socket': No such file or directory
>
> What's
On Mon, Sep 25, 2023 at 04:29:37PM -0700, Hal Murray via devel wrote:
> I have a slight preference for double, but it doesn't really matter.
>
> I've seen some example with double on the left bar and single on the
> top/bottom.
> That was probably the web version.
Hi Hal,
Do you have an
On Mon, Sep 04, 2023 at 02:25:46PM -0700, Gary E. Miller via devel wrote:
> From RHEL:
>
> "The RHEL 8 AppStream Lifecycle Page puts the end date of RHEL 8's
> Python 2.7 package at June 2024."
>
> https://access.redhat.com/solutions/4455511
Hi Gary,
Is the implication that we can safely drop
On Mon, Aug 07, 2023 at 02:14:40PM -0500, Richard Laager via devel wrote:
> That said, I did advocate for merging it back in to master (as a no-op). But
> I don't feel particularly strongly about that.
The code fix itself is already in master. I'll merge the 1.2.2a NEWS into
master later this
The NTPsec Project is pleased to announce the tagging of version 1.2.2a
* Fix a crash in ntpd if NTS is disabled and an NTS-enabled client request
(mode 3) is received. (CVE-2023-4012) #794
For other changes since the previous release, please consult the project
NEWS.adoc file at
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?
Hi Fred,
1.2.2a is 1.2.2 + the 2 line patch to avoid the crash. We'll release 1.2.3 in
late August with all of the changes in
On Thu, Aug 03, 2023 at 11:38:25PM -0700, Hal Murray wrote:
> Should that also go to users@ and devel@?
I'll do this shortly.
Thanks,
-Matt
___
devel mailing list
devel@ntpsec.org
https://lists.ntpsec.org/mailman/listinfo/devel
Hi Hal,
>• [10]libntp/pymodule-mac.c
>
>══
>
> ... ... @@ -143,6 +143,10 @@ void do_mac(char *name,
> 143 143 *maclen = 0;
> 144 144 return;
> 145 145 }
>
Hi Hal,
I do not use it. My servers are all configured directly in ntp.conf
Thanks,
-Matt
___
devel mailing list
devel@ntpsec.org
https://lists.ntpsec.org/mailman/listinfo/devel
On Wed, Feb 08, 2023 at 11:16:53AM -0800, Gary E. Miller via devel wrote:
> The coverity scans are not part of the GitLab CI. They run off the
> GitHub mirror.
The GitLab CI triggers the scan. See
https://gitlab.com/NTPsec/ntpsec/-/pipeline_schedules
Coverity then points at GitHub for some
On Mon, Feb 06, 2023 at 10:51:02PM -0800, Hal Murray via devel wrote:
>
> > Do you have a coverity account?
> > https://scan.coverity.com
> > Then go to "My Dashboard" and "Add project".
>
> Should we document that? Where?
The account creation seems self-explanatory. Or did you want to
Hi all,
I plan to cut a release on Thu 12/22/2022. I'm sorry about the delays in
getting this release out the door.
If there's anything that absolutely must be in this release and can't wait
until the next release, please let me know. Otherwise, I plan to tidy up the
NEWS file as needed and
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 type option as
> tar on macOS uses -s and some BSDs
On Fri, Apr 22, 2022 at 12:13:25AM -0700, Hal Murray via devel wrote:
> nts nowildcards at the top level to set the default
> nowildcards at the server level
> wildcardsOK at the server level to override the default
Hi Hal,
Sorry, I'm not following what you mean here. Do you have a patch or
On Fri, Feb 25, 2022 at 12:02:34PM -0800, Gary E. Miller via devel wrote:
> Yo Hal!
>
> On Tue, 22 Feb 2022 14:39:21 -0800
> Hal Murray via devel wrote:
>
> > They don't work. See https://gitlab.com/NTPsec/ntpsec/-/issues/729
> >
> > There is a single line of code that disables them.
> >
> >
On Tue, Feb 15, 2022 at 01:16:26PM -0800, Hal Murray via devel wrote:
>
> I have a simple patch that will turn off building things in attic/
>
> Should we make off be the default and change that to --enable-attic?
Hi Hal,
Are we worried about the speed of the build, lack of build support on
On Tue, Jun 29, 2021 at 04:41:30PM -0400, Eric S. Raymond via devel wrote:
> Well, first, the historical target for accuracy of WAN time service is
> more than an order of magnitude higher than 1ms. The worst-case jitter
> that could add would be barely above the measurement-noise floor at
On Mon, Jun 14, 2021 at 11:27:06PM -0700, Hal Murray via devel wrote:
>
> I think I've updated the mailing lists, but hmur...@ntpsec.org forwards to my
> old email and I can't figure out how to change that.
>
> My notes include:
> https://devel.ntpsec.org/settings/panel/email/
> but that host
On Mon, Jan 25, 2021 at 03:21:10PM -0800, James Browning via devel wrote:
>Someone twisted a knob somewhere
A new client for Coverity was released and it's more picky than the old client
apparently.
See https://scan.coverity.com/ "Coverity Upgrade to 2020.09"
Thanks,
-Matt
On Mon, Dec 21, 2020 at 06:48:39PM +, Matthew Selsky via devel wrote:
> www.ntpsec.org was moved back to GitLab pages and it should be working now.
> docs.ntpsec.org is still pending some work by GitLab support.
GL support fixed docs.ntpsec.org per
https://gitlab.com/gitlab-com/gl
Hi James,
>We currently do not have builders for the tags freebsd-11, freebsd-12, and
>ubuntu-1604-lts. It would appear that in the late unpleasantness that the
>builders detached. This should be fixable by having the
>builders admin(s) reattach them in the settings. It should be
On Sun, Sep 06, 2020 at 06:18:40PM -0500, Richard Laager via devel wrote:
> On 9/6/20 5:43 PM, Hal Murray via devel wrote:
> > Anybody using the modem driver?
>
> I tested in November, for fun, not any practical reason. NIST's service
> is still up. The USNO service was dead. I emailed them and
I also previously setup Codacy in order to see what other SAST systems could
do. See https://app.codacy.com/gl/NTPsec/ntpsec/dashboard
Let me know what you think. If either are useful, I'll integrate them more
tightly in our workflows.
Thanks,
-Matt
On Wed, Sep 02, 2020 at 08:53:41AM -0400, Eric S. Raymond via devel wrote:
> Sanjeev Gupta :
> > They support *any* git repository.
>
> Huh. Their docs are out of date, then.
I tried adding our GitLab repo today and I get an error message that new GitLab
repos have been disabled by the site
On Thu, Apr 30, 2020 at 08:03:26PM +0800, Sanjeev Gupta wrote:
>Hal,
>I have sent in a MR,
>https://gitlab.com/NTPsec/ntpsec/-/merge_requests/1121
>for your review.
Hi Sanjeev!
I submitted https://gitlab.com/NTPsec/ntpsec/-/merge_requests/1122 before I saw
this.
My MR also
Hi Hal and team,
Much our of NTS code uses BSD-4-Clause-UC instead of BSD-2-Clause (our
preferred license for new code).
What this license selection intentional?
Is BSD-4-Clause-UC intended for code owned by the University of California, or
does it make sense for others to use this license as
On Tue, Apr 21, 2020 at 04:57:04PM +, Robin H. Johnson via devel wrote:
> Can you please log the IP of the host you used that did not have the
> file?
>
> distfiles.gentoo.org is a bouncer with many mirrors
Hi Robin,
We call "emerge-webrsync" in our CI. Are you asking us to log the output
On Thu, Mar 26, 2020 at 12:57:33PM -0700, Hal Murray via devel wrote:
> I just pushed the change.
Can we bring back support of older OpenSSL releases for builds that don't need
NTS support?
OpenSSL 1.0.2 is supported via paid extended support per
On Tue, Mar 24, 2020 at 12:40:42PM -0700, Hal Murray via devel wrote:
> I'd like to check the OpenSSL version number and give a sensible error
> message
> rather than some mumbo jumble from the compiler.
I would model the check that we removed in
On Mon, Jan 20, 2020 at 11:53:44AM -0800, Hal Murray via devel wrote:
> If so, can somebody send me an example script.
See https://gitlab.com/NTPsec/ntpsec/blob/master/.gitlab-ci.yml#L450 and
https://gitlab.com/NTPsec/ntpsec/blob/master/INSTALL.adoc#user-content-cross-compiling
Cheers,
-Matt
On Mon, Jan 13, 2020 at 05:06:01PM -0800, Hal Murray via devel wrote:
> A year or 2 ago, I put together a script to test as many build time options
> as
> I thought reasonable. It's in ./tests/option-tester.sh
>
> Does anybody other than me use it?
>
> It's a bit of a CPU hog -- too much to
On Mon, Jan 13, 2020 at 05:06:01PM -0800, Hal Murray via devel wrote:
> How does waf tell the c compiler which Python.h to use?
> My system has:
> /usr/include/python2.7/Python.h
> /usr/include/python3.7m/Python.h
./waf --python=/path/to/python
OR
/path/to/python waf
> What can we do
On Mon, Dec 09, 2019 at 11:35:05AM -0800, Hal Murray via devel wrote:
>
> I haven't seen that mail recently.
Authors are emailed for failed pipelines See
https://docs.gitlab.com/ee/ci/pipelines.html
We also email specific users for failed pipelines. See
On Sun, Dec 01, 2019 at 10:45:28AM +0100, Udo van den Heuvel via devel wrote:
> On 01-12-2019 10:14, Udo van den Heuvel via devel wrote:
> > The macro _wrong_version_format_terminate_build can be used to work
> > around this issue:
>
> Perhaps also in this way:
>
> rpmbuild -bb --define
On Sat, Sep 21, 2019 at 01:09:30PM -0700, Paul Theodoropoulos via devel wrote:
>On 9/21/2019 13:00 PM, James Browning wrote:
>
> On Sat, Sep 21, 2019, 12:55 PM Paul Theodoropoulos via devel
> <[1]devel@ntpsec.org> wrote:
>
>Just a quick note, as I'm vetting all my
On Tue, Sep 17, 2019 at 09:39:15PM -0700, Hal Murray wrote:
> > Only thing left to revert is missing guards near "switch (rl_what) {"
> > near line 3630 in ntpd/ntp_config.h
>
> The whole point of this change was to get rid of ifdefs that weren't needed
> because the symbols they were checking
On Tue, Sep 17, 2019 at 08:42:18PM -0700, Hal Murray wrote:
> > Can you partially revert ...
>
> I thought I had fixed it. Have you done a recent pull? Is the current code
> still broken?
Only thing left to revert is missing guards near "switch (rl_what) {" near line
3630 in
On Sun, Sep 15, 2019 at 06:18:47PM -0700, Hal Murray via devel wrote:
>
> There are various #ifdefs testing RLIMIT_MEMLOCK and friends
>
> The Linux man page for setrlimit says:
>getrlimit(), setrlimit(): POSIX.1-2001, POSIX.1-2008, SVr4, 4.3BSD.
> So I think we can assume it exists and
On Mon, Sep 09, 2019 at 08:46:26AM -0700, James Browning via devel wrote:
>While working on a script, I stumbled across this issue. the cmd.Cmd
>class does not call its precmd function from its onecmd function in
>either Python 2.7 or 3.6. I see several possible paths forward.
>
>
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 type 'unsigned
> > short' but
On Mon, Aug 26, 2019 at 10:51:58PM -0700, Hal Murray via devel wrote:
> > A relatively quick search suggests mandatory=True as an argument.
>
> That makes waf fail if the code chunk doesn't work.
You want "mandatory=False" since this is a probe, not a requirement.
And you want to pass "-Werror"
On Mon, Aug 26, 2019 at 04:55:48PM -0700, Gary E. Miller via devel wrote:
> _GNU_SOURCE should not always be defined, but it does need to be defined
> in certain cases. For example, on glibc < 2.10, you need to define
> it to get strnlen() and struct ifreq.
>
> From glibc 2.10, you instead need
On Sat, Aug 24, 2019 at 02:42:08AM -0700, Hal Murray via devel wrote:
> Stage: build
> Name: fedora-rawhide-refclocks-gpsd
> Trace: GPG Keys are configured as:
> file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-
> 31-x86_64
> Public key for glibc-common-2.30.9000-1.fc32.x86_64.rpm is not installed.
>
On Fri, Aug 23, 2019 at 02:12:21PM -0400, Eric S. Raymond via devel wrote:
> Sanjeev Gupta :
> > We need a point release. Significant things that have happened recently:
> >
> >
> >- The g and G suffixes
> >- Removal of neoclock4x
> >- Some doc changes
> >- The ALPN change
> >
>
On Mon, Aug 19, 2019 at 06:33:52PM -0700, Gary E. Miller via devel wrote:
> For some reason GitLab has not allowed me to merge from their web pages
> for a few weeks. I have to merge manually...
Hi Gary,
Sounds like you ran into https://gitlab.com/gitlab-org/gitlab-ee/issues/12686
I'm not
On Fri, Aug 02, 2019 at 06:31:34AM +0200, Udo van den Heuvel wrote:
> Builds successfully after adapting the directories in the %files section.
Excellent!
> URL: http://www.ntpsec.org
> Requires(post): systemd-units
> Requires(preun): systemd-units
> Requires(postun): systemd-units
>
On Thu, Aug 01, 2019 at 07:19:02PM +0200, Udo van den Heuvel wrote:
> On 01-08-19 19:00, Matthew Selsky wrote:
> > You may need to specifically use %{__python3} when you call "waf" in the 2
> > places in the %build section.
>
> So maybe not use --python=%{__python3} for waf?
"--python" should
On Thu, Aug 01, 2019 at 05:02:58PM +0200, Udo van den Heuvel wrote:
> On 01-08-19 16:39, Udo van den Heuvel via devel wrote:
> > The 1.1.6 code does not.
>
> The workaround now works when I use the pathfix.py line with this
> addition: %{buildroot}%{_sbindir}/*
>
> The whole SPEC then looks like
On Thu, Aug 01, 2019 at 04:31:52PM +0200, Udo van den Heuvel wrote:
> On 01-08-19 16:27, Matthew Selsky wrote:
> > On Thu, Aug 01, 2019 at 04:18:30PM +0200, Udo van den Heuvel wrote:
> >
> > See
> > https://gitlab.com/NTPsec/ntpsec/commit/3ee8e4c3c3cf4b2d6f010874e7f447a23a1710cf
> > for the
On Thu, Aug 01, 2019 at 04:18:30PM +0200, Udo van den Heuvel wrote:
> The build shows otherwise, else there would not be an error.
> Or did I miss a step in the build process?
See
https://gitlab.com/NTPsec/ntpsec/commit/3ee8e4c3c3cf4b2d6f010874e7f447a23a1710cf
for the change that we made to
On Thu, Aug 01, 2019 at 03:32:40PM +0200, Udo van den Heuvel via devel wrote:
> On 01-08-19 15:24, Udo van den Heuvel via devel wrote:
> > The script will exit with nonzero exit code, rendering the build failed.
>
> When trying to work around this in my spec file, I use:
> pathfix.py -pni
On Thu, Mar 28, 2019 at 04:38:44PM -0700, Gary E. Miller via devel wrote:
> Potential extra security is just an added feature that you get for free
> once you add certificate pinning to handle the ostfalia case.
>
> Check the pin, but do not check the chain:
>
> server ostfalie.de noval pin
On Thu, Mar 28, 2019 at 04:06:05PM -0700, Gary E. Miller via devel wrote:
> > I think public key (as opposed to certificate) pinning is the common
> > approach these days. The application simply requires that one of the
> > public keys in the chain match the pinned public key. The user can
> >
On Mon, Mar 25, 2019 at 04:00:23AM -0700, Hal Murray via devel wrote:
>
> I thought it had been removed.
[...]
> Stage: build
> Name: debian-oldoldstable-basic
> Trace: Err http://deb.debian.org oldoldstable-updates/main amd64 Packages
> 404 Not Found [IP: 151.101.248.204 80]
> W: Failed to
On Fri, Mar 22, 2019 at 06:32:10PM -0700, Gary E. Miller via devel wrote:
> I think this is what you want:
Perfect.
> I tried to modify the wscript to do that, but failed...
In ntpd/wscript, try replacing this:
use="libntpd_obj ntp M parse RT CAP SECCOMP PTHREAD NTPD "
On Fri, Mar 22, 2019 at 04:52:33PM -0700, Gary E. Miller via devel wrote:
> Yo Hal!
>
> New issue. I have a really old server that has been running NTPsec
> git head until recently. Now it fails, the openssl is too old.
>
> # openssl version
> OpenSSL 1.0.2o 27 Mar 2018
>
> I know I can
On Tue, Mar 19, 2019 at 06:42:48PM -0400, Eric S. Raymond wrote:
> I'm confused. That YAML isn't Docker description? What interprets it?
No, it's not Docker description. See https://docs.gitlab.com/ee/ci/yaml/ for
the documentation.
Thanks,
-Matt
On Tue, Mar 19, 2019 at 03:08:48PM -0400, Eric S. Raymond wrote:
> Matthew Selsky :
> > On Mon, Mar 18, 2019 at 08:13:27PM -0400, Eric S. Raymond via devel wrote:
> > > Coverity scan builds are busted for me. Log enclosed. Are the ones
> > > triggered by the CI system working?
> >
> > Yes, the
On Mon, Mar 18, 2019 at 08:13:27PM -0400, Eric S. Raymond via devel wrote:
> Coverity scan builds are busted for me. Log enclosed. Are the ones
> triggered by the CI system working?
Yes, the CI triggered coverity builds are working. See
https://gitlab.com/NTPsec/ntpsec/pipelines/52498442
On Tue, Mar 05, 2019 at 12:46:29PM -0600, Richard Laager via devel wrote:
> On 3/5/19 12:45 PM, Gary E. Miller via devel wrote:
> > Yo Eric!
> >
> > On Tue, 5 Mar 2019 02:11:52 -0500
> > "Eric S. Raymond via devel" wrote:
> >
> >>> That would leave the configure option. I've never used it.
>
On Mon, Mar 04, 2019 at 12:11:07PM -0800, Gary E. Miller via devel wrote:
> Given the Comodo mess of last week I expect a lot more people will want to
> do pinning next month.
Do you have a reference for this mess?
Thanks,
-Matt
___
devel mailing
On Fri, Feb 22, 2019 at 01:51:28AM -0800, Hal Murray via devel wrote:
>
> My bad - warnings, not errors.
>
> It works. (on 32 bit systems)
I've filed https://gitlab.com/NTPsec/ntpsec/issues/561 to track this.
Thanks,
-Matt
___
devel mailing list
On Sat, Feb 09, 2019 at 05:28:16AM -0800, 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
>
On Sun, Feb 10, 2019 at 05:30:36PM -0800, Hal Murray wrote:
>
> If it's easy for waf, it would be nice to document the version of OpenSSL we
> are using to build.
The version that we built against, or the version that we're currently
dynamically linked with? Eg, we might build with 1.0.2n,
On Sun, Feb 10, 2019 at 05:02:48PM -0800, Fred Wright via devel wrote:
>
> 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:
On Sat, Feb 09, 2019 at 02:19:50PM -0800, Hal Murray via devel wrote:
>
> e...@thyrsus.com said:
> >> Are we ever going to want to use anything older than TLS1.2? Spec says
> >> no,
> >> but it might be interesting for testing.
> > I'm not interested in complicating our lives with a surfeit of
On Thu, Feb 07, 2019 at 05:28:33AM -0800, Hal Murray via devel wrote:
>
> I pushed the start of NTS-KE-client code, partly in order to find things like
> this.
>
>
> Job #157857979 (
>
On Mon, Feb 04, 2019 at 05:34:56PM -0800, Hal Murray wrote:
> > Now, if it doesn't meet our accuracy thresholds, that's another story.
>
> Do we have any accuracy standards?
See https://www.ntpsec.org/drivers.html
INACCURATE
Remove GPS drivers and time radios for which the hardware offers no
On Mon, Feb 04, 2019 at 01:39:48PM -0500, Eric S. Raymond via devel wrote:
> I found a documentation error.
>
> The page for the modem driver says:
>
> This driver requires a 9600 bps modem with a Hayes-compatible command
> set and control over the modem data terminal ready (DTR) control
On Tue, Jan 29, 2019 at 07:18:20PM -0800, Gary E. Miller via devel wrote:
> Yo Fred!
>
> 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
On Sun, Jan 27, 2019 at 06:44:59AM -0500, Eric S. Raymond via devel wrote:
> Hal Murray via devel :
> > It's up to version 2.0.14, Dev 2018, about a year since the version we are
> > using.
We're using a version from 6 months ago
(https://gitlab.com/ita1024/waf-old/commits/waf-1.9)
> At some
On Wed, Jan 23, 2019 at 01:36:33AM -0800, Hal Murray wrote:
>
> e...@thyrsus.com said:
> > In particular, some of our targets (some BSDs, I don't remember which) have
> > only microsecond, not nanosecond resolution in the clock-adjustment calls.
>
> NetBSD and FreeBSD have NANO.
>
> Matthew
On Wed, Jan 23, 2019 at 12:43:53AM -0500, Eric S. Raymond wrote:
> That's because our actual support target is this:
>
> This software should build on any operating system conformant to
> POSIX.1-2001 and ISO/IEC 9899:1999 (C99). In addition, the operating
> system must have an
On Wed, Jan 23, 2019 at 12:23:26PM -0800, James Browning via devel wrote:
>I think I remember seeing that. IIRC I was piping something somewhere.
>That was back before pylib/poly.py though.
Per https://docs.python.org/2/library/io.html#io.TextIOBase:
buffer
The underlying binary buffer
On Tue, Jan 22, 2019 at 07:37:18PM -0800, Hal Murray via devel wrote:
>
> We have various cruft associated with threads. Can we add POSIX threads to
> our list of requirements? Or is it already included in POSIX.1-2001 and
> ISO/IEC 9899:1999 (C99)?
POSIX threads are optional for
Is it possible to make lockclock a run-time-only option, instead of a
compile-time + runtime otion?
If remains a compile-time option, then we'll need to add CI targets for it so
that we're always testing that it compiles cleanly.
Thanks,
-Matt
___
On Mon, Dec 24, 2018 at 11:14:47AM -0800, Hal Murray wrote:
>
> > That still makes this table a maintainence headache. Can we instead say
> > that
> > we built on modern/supported-by-upstream releases of popular operating
> > systems and distributions. And we build test on the platforms
On Mon, Dec 24, 2018 at 09:48:53AM -0500, Eric S. Raymond via devel wrote:
> Hal Murray via devel :
> >
> > We need a mechanism to review/update things occasionally and a list of
> > things
> > that need occasional review.
> >
> > Here is a starter:
> >
On Mon, Dec 24, 2018 at 03:50:33PM +0100, Achim Gratz via devel wrote:
> Am 24.12.2018 um 11:32 schrieb Hal Murray via devel:
> > You can see POSIX.1-2001, SUSv3, online for free here:
> > http://www.unix.org/version3/
>
> I prefer the online version from the Open Group:
>
>
On Tue, Dec 11, 2018 at 03:01:06PM -0800, Gary E. Miller via devel wrote:
>
> I am unaware of any other Python libraries not in the base Python that
> NTPsec uses. For some reason *BSD don't like curses.
>
> You know any other used Python packages not in the base Python?
What about the "gps"
On Mon, Dec 17, 2018 at 01:55:16PM -0800, Hal Murray via devel wrote:
>
> James Browning said:
> > IIRC OpenSUSE does the same thing. I don't recall seeing a streak of red
> > build fail indicators though. Possibly because I seem to remember adding it
> > to the CI file.
Is there any value in my adding a waf check for the "gps" python module and
skipping the checking/installation of ntpclients/ntploggps.py if it's not
found, similar to what I did for the "curses" python module and ntpmon?
It would take only a few minutes.
Thanks,
-Matt
> We can add it to the output of "./waf help" if that makes it easier to
> discover.
https://gitlab.com/NTPsec/ntpsec/merge_requests/854
Thanks,
-Matt
___
devel mailing list
devel@ntpsec.org
http://lists.ntpsec.org/mailman/listinfo/devel
On Fri, Dec 07, 2018 at 01:37:44PM -0600, Richard Laager via devel wrote:
> Traditionally, there has often been a "make uninstall" target that
> removes everything that "make install" installs. Does NTPsec have a
> ./waf uninstall?
Yes. Waf provides it as a built-in.
$ ./waf uninstall
---
On Thu, Dec 06, 2018 at 11:48:37AM -0800, Hal Murray via devel wrote:
> I think we should remove ntpleapfetch from the main package and tarball -
> probably move it off to a separate package.
Classic includes a perl version of the script (as /usr/bin/update-leap) in
their packaging. So we
Hi,
Let me clear up two things:
- The project doesn't build docs by default
(https://gitlab.com/NTPsec/ntpsec/blob/master/wafhelpers/options.py#L90). You
must specify "--enable-doc" to "waf configure".
- Our CI doesn't attempt to build documentation for all targets in an effort to
make sure
On Sun, Nov 04, 2018 at 09:47:14PM -0800, Hal Murray via devel wrote:
> [Was: Subject: Re: ntpleapfetch broken on FreeBSD 11.2 or NetBSD 8.0]
>
> > I was working on that a little try checking out merge request !831
>
> How do I do that?
>
> That should be simple, but it's not in my working set.
On Fri, Oct 19, 2018 at 03:24:13PM +0200, Udo van den Heuvel via devel wrote:
> When building ntpsec on fedora 29 I see things like:
>
> [ 29/167] Compiling docs/driver_oncore.txt
> /usr/bin/asciidoc:471: DeprecationWarning: Flags not at the start of the
> expression '^(?u)[^\\W\\d][-\\w]*$'
>
On Tue, Aug 28, 2018 at 11:54:42AM -0700, Hal Murray via devel wrote:
> It makes us look sloppy. We worked hard to get (almost) no warnings. We
> should maintain that reputation.
>
> Also, we should document the new warnings the linker gives about tempnam from
> the python library.
Python
On Mon, Aug 27, 2018 at 05:20:45PM -0700, Hal Murray via devel wrote:
>
> What's the story?
>
> I'm catching up after being off line for several weeks. I updated a NetBSD
> box to 8.0 and now it produces lots and lots of warnings that I expect would
> get fixed before a release.
I brought up
Ian,
Is there a way to have Unity spit out information on test coverage percentage?
If so, tell me how and I'll take a look at wiring it into our gitlab CI.
Thanks,
-Matt
___
devel mailing list
devel@ntpsec.org
1 - 100 of 153 matches
Mail list logo
