Actions
Bug #12840
closedUpgrade of openvpn-client-export package after 2.6.0 upgrade failed
Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
OpenVPN
Target version:
-
Start date:
Due date:
% Done:
0%
Estimated time:
Plus Target Version:
Release Notes:
Default
Affected Version:
Affected Architecture:
Description
I just upgraded from pfsense 2.5.2 to 2.6.0. Several packages did not auto upgrade (I don't know if they should have). But upon upgrading my packages, they all seemed to go well until I went to upgrade `openvpn-client-export`. It failed with the below output:
>>> Upgrading pfSense-pkg-openvpn-client-export... Updating pfSense-core repository catalogue... pfSense-core repository is up to date. Updating pfSense repository catalogue... pfSense repository is up to date. All repositories are up to date. pkg-static: freeradius3 has a missing dependency: openldap-client pkg-static: nss_ldap has a missing dependency: openldap-client pkg-static: pfSense has a missing dependency: unbound112 Checking integrity... done (0 conflicting) The following 2 package(s) will be affected (of 0 checked): Installed packages to be UPGRADED: openvpn: 2.5.2_2 -> 2.5.4_1 [pfSense] pfSense-pkg-openvpn-client-export: 1.6_2 -> 1.6_4 [pfSense] Number of packages to be upgraded: 2 [1/2] Upgrading openvpn from 2.5.2_2 to 2.5.4_1... ===> Creating groups. Using existing group 'openvpn'. ===> Creating users Creating user 'openvpn' with uid '301'. pw: group `301' does not exist pkg-static: PRE-INSTALL script failed Failed
So it seems it's failing to upgrade openvpn. I already had an openvpn group, as it notes. Maybe it is not using the correct group id in that case in the upgrade?
Thanks!
Actions