pfSense

same system also had same issue for system-patches. Can't change title.
perhaps this is a general issue for more packages, but i didn't have any other installed on it.

Package System Patches does not exist in current pfSense version and it has been removed. @ 2016-04-12 23:54:38

I installed System Patches OK on a full install test system in a VM.
Then I tried to install it on a real Alix 32-bit that I have upgraded to 2.3-RELEASE. System Patches appears in the list of available packages. When I install it, I get:

Installing pfSense-pkg-System_Patches...

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.
The following 1 package(s) will be affected (of 0 checked):

New packages to be INSTALLED:
pfSense-pkg-System_Patches: 1.1.4_1 [pfSense]

The process will require 31 KiB more space.
8 KiB to be downloaded.
Fetching pfSense-pkg-System_Patches-1.1.4_1.txz: . done
Checking integrity... done (0 conflicting)
[1/1] Installing pfSense-pkg-System_Patches-1.1.4_1...
[1/1] Extracting pfSense-pkg-System_Patches-1.1.4_1:

and it stops at that point and the GUI displays:
pfSense-pkg-System_Patches installation failed!

I tried installing something else that should be harmless and easy - Notes - and got the same sort of stuff.
Is there a general problem installing packages on Alix nanoBSD?

Jim Pingle wrote:

On 2.2.x the Quagga package is "Quagga OSPF" and on 2.3 it's "Quagga_OSPF". So the package still exists, but the space was changed to an underscore in its name. Removing it and stating that the package doesn't exist may be technically true by an exact name match, but it's unexpected and potentially harmful.

The upgrade code could handle that situation better. It affects at least Quagga and System patches.

The code that checks for those packages uses tag <internal_name> to compare, and in this case it's Quagga_OSPF and System_Patches that should match

I setup a test with 2.2.6 with Quagga OSPF and System Patches installed, upgraded it to 2.3.0 via auto-update (thinking I would confirm the breakage), and it worked fine. Packages installed, worked post-upgrade without touching it.

Renato: was this something fixed server-side in the pkg repo? no commit on the ticket, and don't see anything in the change log for the main repo that's related, so not sure what changed.

Chris Buechler wrote:

I setup a test with 2.2.6 with Quagga OSPF and System Patches installed, upgraded it to 2.3.0 via auto-update (thinking I would confirm the breakage), and it worked fine. Packages installed, worked post-upgrade without touching it.

Renato: was this something fixed server-side in the pkg repo? no commit on the ticket, and don't see anything in the change log for the main repo that's related, so not sure what changed.

I couldn't reproduce it either, but changes done for #6137 should help cases like this one to don't happen anymore.

This is only an issue upgrading from 2.1.x (and likely earlier but haven't tried).

pushed config upgrade code to rename those packages in the config. It looks like OSPF and System Patches are the only two that were renamed, but if anyone knows of others, please let us know.

the config upgrade code worked, or would have if it were actually in the config at that point. The pre_upgrade_command uninstalls all packages, so that's gone at the point convert_config runs. Reverted that config upgrade code, testing alternate approach.

Package list now correct, the package reinstall was skipped until my last commit on #6137. This succeeded with that change made manually, leaving for confirmation again once that hits a snapshot.