Project

General

Profile

Actions
Copy link

Bug #9177

closed

FRR 0.2_4 installation broken with pfSense 2.4.4_1

Added by Chris Bennetts almost 7 years ago. Updated almost 7 years ago.

Status:
Not a Bug
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
12/06/2018
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Affected Version:
2.4.4_1
Affected Plus Version:
Affected Architecture:

Description

The package doesn't like 2.4.4+

>>> Installing pfSense-pkg-frr... 
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.
Checking integrity... done (0 conflicting)
The following 9 package(s) will be affected (of 0 checked):

Installed packages to be REMOVED:
    pfSense-2.4.4_1
    bind-tools-9.12.2P2

New packages to be INSTALLED:
    pfSense-pkg-frr: 0.2_4 [pfSense]
    frr5: 5.0.1 [pfSense]
    libssh: 0.7.6 [pfSense]
    rtrlib: 0.5.0 [pfSense]

Installed packages to be DOWNGRADED:
    ndpi: 2.4.d20180830_1,1 -> 2.4.d20180830,1 [pfSense]
    json-c: 0.13.1 -> 0.13 [pfSense]

Installed packages to be REINSTALLED:
    ntopng-3.6.d201800910,1 [pfSense] (needed shared library changed)

Number of packages to be removed: 2
Number of packages to be installed: 4
Number of packages to be reinstalled: 1
Number of packages to be downgraded: 2

The operation will free 29 MiB.
pkg-static: Cannot delete vital package: pfSense!
pkg-static: If you are sure you want to remove pfSense, 
pkg-static: unset the 'vital' flag with: pkg set -v 0 pfSense
Failed
Actions
Copy link
 #1

Updated by Jim Pingle almost 7 years ago

  • Status changed from New to Not a Bug

I can't replicate this on 2.4.4-p1.

Looks like you messed up the package repositories on that box somehow, like maybe you upgraded to 2.4.4-p1 and then pointed the package repo at snapshots/2.4.5 and did something and then maybe switched back.

Start a thread on the forum to discuss the problem and figure out how it happened first. Then if it's determined there is a bug somewhere, a more accurate issue can be created.

Actions
Copy link
 #2

Updated by Chris Bennetts almost 7 years ago

Jim's reasoning turned out correct. A reinstall of 2.4.4, upgrade to p1 and package installation worked 100%.
This should be closed.

Actions
Copy link

Also available in: Atom PDF