Thank you for the test and report!
Regarding the changes, I hoped the NEWS and UPGRADING files detail them
extensively enough :)
Protocol-wise, there were some aliases added, and one notable change was
addition of TRACKING for queries and replies to not mix up, more so with
massive setups of
Thanks for the update.
I'm currently away from a PC so can't dig into libusb nuances. Cursorily I
remember discussions that FreeBSD at least had a different implementation
or build of libusb, in particular for error handling (-1 or more nuanced
IIRC). Not sure which side NetBSD picked.
As for
Hi,
I built successfully package with 2.8.0-rc1 for VMware ESXi (6.7 and 7.0
tested). Now, this package provides only the client part of NUT (upsc and
upsmon) and I think that this part of code has few evolutions since 2.7.4
Client has to be able to communicate with NUT servers running older
I am taking the tarball I built from rc1 and using it as if released in
pkgsrc. The great news is that it only took me about 15 minutes to
update the package.
I am getting one error:
=> Checking for non-existent script interpreters in ups-nut-2.7.4.1
ERROR: [check-interpreter.mk] The
On Mar 31, 2022, at 9:18 AM, Greg Troxel wrote:
>
> I see your point about distcheck. I tend to build tarballs from source
> to then use in pkgsrc (not that I publish those tarballs and packages),
> to be able to debug the combination of upstream and pkgsrc to be ready
> for a release. I can
> Are there any known backward incompatible changes?
e.g. conf file settings or commands that won't work anymore?
None that I am aware of. There are a few new config keywords (and aliases
to older concepts), so programs from the older NUT packages would probably
safely refuse to start while
> They were survived by the next name in line, NUT v2.8.0(-rc1). Le NUT est
> mort, long live the NUT!
Thank you to everyone who made this happen!
Are there any known backward incompatible changes?
e.g. conf file settings or commands that won't work anymore?
Thank you,
David Zomaya
Eaton
