Beta test of new NUT UPS package
-
It's been tracked down to a specific problem with a branch of the repo. I'm sure it will be fixed soon.
Thank you for your patience.
-
It's been tracked down to a specific problem with a branch of the repo. I'm sure it will be fixed soon.
Thank you for your patience.
Awesome, thank you! :)
-th3r3isnospoon
-
On Community Edition here also seeing the XML error message.
The process will require 17 MiB more space.
1 MiB to be downloaded.
Fetching nut-2.7.4.txz: …....... done
Fetching neon-0.30.1.txz: .......... done
Checking integrity... done (0 conflicting)
[1/4] Installing neon-0.30.1…
[1/4] Extracting neon-0.30.1: …....... done
[2/4] Installing net-snmp-5.7.3_11…
[2/4] Extracting net-snmp-5.7.3_11: …....... done
[3/4] Installing nut-2.7.4…
[3/4] Extracting nut-2.7.4: …....... done
[4/4] Installing pfSense-pkg-nut-2.7.4_1…
[4/4] Extracting pfSense-pkg-nut-2.7.4_1: …....... done
XML error: PKGINFOLINK at line 8 cannot occur more than once
Message from net-snmp-5.7.3_11:And uninstall show following:-
Removing pfSense-pkg-nut…
Checking integrity... done (0 conflicting)
Deinstallation has been requested for the following 1 packages (of 0 packages in the universe):Installed packages to be REMOVED:
pfSense-pkg-nut-2.7.4_1Number of packages to be removed: 1
[1/1] Deinstalling pfSense-pkg-nut-2.7.4_1…
The nut package is not installed.Deletion aborted.[1/1] Deleting files for pfSense-pkg-nut-2.7.4_1: …....... done
The nut package is not installed.Deletion aborted.>>> Removing stale packages... done.
Success -
You can fix it right now by installing beta 6 back manually or change your firmware branch to development, re-install package (you can do it from GUI, even if package itself is broken) and then change branch to stable.
Or just wait for a fix in repo. -
@w0w:
You can fix it right now by installing beta 6 back manually or change your firmware branch to development, re-install package (you can do it from GUI, even if package itself is broken) and then change branch to stable.
Or just wait for a fix in repo.Thank you for the reply and I will wait for fix in repo.
-
Still waiting for NUT to be installed and usable.
-
The one package I decide to install on a Sunday… :-\
-
@w0w:
You can fix it right now by installing beta 6 back manually or change your firmware branch to development, re-install package (you can do it from GUI, even if package itself is broken) and then change branch to stable.
Or just wait for a fix in repo.I tried this today. I switched to the development branch in Updates, reinstalled the NUT package. Although the installation completed successfully, NUT would not start and there was no GUI menu for NUT either.
Configured my system back to stable branch, reinstalled NUT with the error and left it like that until a fix arrives. -
-
Hi Denny,
Just want to say thank you for the great work, I'm still on beta 3, it was working fine and I wanted to wait until the release had had feedback.
My set up here has had a power cut and everything worked perfectly both with the master and all of the slaves. Huge weight off my mind and key component in me being able to recommend pfsense to people.
Anything to bear in mind now upgrading from b3 to the latest version?
Thanks again.
John
-
John,
Should be no problem moving from beta 3 to the release version.
Denny
-
I had no issues on my site uninstalling the latest beta and installing the prod version.
Thanks for the opportunity to help beta test this package.
-
S stephenw10 referenced this topic on
