Todo #14795
closed
Transition to nut-devel
0%
Description
The current NUT package is based upon the 2.8.0 distribution of NUT. Unfortunately, since its release in April of 2022, 2.8.0 has proved to be a very problematic release with numerous defects. Most especially, defects in NUT's USB library result in signal 10/11 crashes on FreeBSD, and there are also issues with SNMP drivers as well. This has affected a lot of pfSense users.
While these and other serious issues have been addressed in NUT mainline, there has been no new release of NUT, and as of this point it appears that a release is no closer than it was a year ago. There is officially no timeline, and the recommendation from the project is to simply build from git. Most distributions have heeded this advice, abandoned 2.8.0, and moved to mainline git.
I have been distributing unofficial builds of various NUT components for more than 6 months, all the while hoping and waiting for a 2.8.1 to address the issues. I'm ready to throw in the towel. FreeBSD has a package, nut-devel, that tracks NUT mainline git and is up to date. I believe that it is time to give up on nut-2.8.0, and make the switch to nut-devel. I will submit a PR shortly.
Related issues
Updated by Jim Pingle 8 months ago
- Tracker changed from Bug to Todo
- Status changed from New to Pull Request Review
- Affected Architecture deleted (
All)
Updated by Marcos M 7 months ago
- Related to Bug #13997: NUT Package and 23.01 added
Updated by Kris Phillips 7 months ago
Plus should be updated with this as well. It is still on 2.8.0.
Updated by Denny Page 7 months ago
The pfSense-pkg-nut build appears to be failing due to an issue upstream in the FreeBSD nut-devel package. I have filed a bug report upstream to address the issue.
Updated by Marcos M 6 months ago
- File nut-devel-2023.10.07_1.pkg added
- Status changed from Resolved to Feedback
- Install
nutfrom the package manager GUI - Upload the attached file to the firewall
- Remove the old dependency:
pkg remove -fy nut - Install the new dependency:
pkg install -fy /tmp/nut-devel-2023.10.07_1.pkg
Updated by Denny Page 6 months ago
Thank you Marcos. Can you also post the ARM version please?
Updated by Denny Page 6 months ago
Hey all, I've got a good dozen testers that have reported successful results with 2.8.1. Reported tests include local USB, SNMP, and remote NUT. I am sure that there are others who are not bothering to report their successful use, but there have been no complaints of failure. I believe we are completely ready to publish the package.
There is one outstanding PR, https://github.com/pfsense/FreeBSD-ports/pull/1316, that is a very minor tweak to the format of notification messages. I would like to include the PR unless it will delay publishing.
Thanks
Updated by Denny Page 6 months ago
Guys, the version number for the released package is wrong. It's not in my original PR, but when the notification tweak to nut_email.php was merged, the version number in the Makefile was changed from 2.8.1 to 2.8.2. This should have been left at 2.8.1 or at most 2.8.1_1.
Updated by Marcos M 6 months ago
- Status changed from Feedback to Resolved
The minor version bump is correct; the version needed to be bumped for the notification tweak to be picked up. There's no real consistency on how PORTREVISION is used and sometimes that does get bumped instead (which is what controls the version number after _). See https://docs.freebsd.org/en/books/porters-handbook/makefiles/index.html#makefile-portrevision
Updated by Denny Page 6 months ago
I'm sorry, but the minor version bump was not correct. The pfSense package numbering is intended to align with the NUT release number. See discussion in the original PR.
I cannot speak to PORTREVISION in the general FreeBSD case, but I can speak to it in the pfSense NUT Package case. PORTREVISION has been carefully maintained in the 5+ years I have maintained this package.
Updated by Marcos M 6 months ago
I missed that since the dependency tracking version is by git commits (which don't necessarily align with the release version); currently that is 9b9d5099c which is some commits behind the 2.8.1 release. Ultimately it doesn't really affect anything so whatever you prefer to use there is fine. A new commit would be needed that sets PORTVERSION and PORTEPOCH accordingly.
Updated by Denny Page 6 months ago
Are you saying that if we republish the package as 2.8.1_2 it would work, even though a 2.8.2 has been previously published?
Updated by Denny Page 6 months ago
If it will work, I have a PR prepared: https://github.com/pfsense/FreeBSD-ports/pull/1329. Thanks.