update and package install in 2.8.0-DEVELOPMENT (amd64) no longer possible....

peters77

Hi,

I was on the 2.7.0.-dev branch and all was well. I recently got an update to 2.7.0. and that worked.
Now the dashboard shows I'm on 2.8.0-DEVELOPMENT (amd64) and an update is offered:

Version 2.8.0.a.20230728.0600 is available.
Version information updated at Sun Jul 30 10:40:59 CEST 2023

My system:

PC Engines APU2
BIOS 	Vendor: coreboot
Version: 4.0.7
Release Date: Tue Feb 28 2017
Version 	2.8.0-DEVELOPMENT (amd64)
built on Mon Jul 03 06:04:41 UTC 2023
FreeBSD 14.0-CURRENT

Version 2.8.0.a.20230728.0600 is available.
Version information updated at Sun Jul 30 10:40:59 CEST 2023  
CPU Type 	AMD GX-412TC SOC
4 CPUs: 1 package(s) x 4 core(s)
AES-NI CPU Crypto: Yes (active)
QAT Crypto: No

If I go to updates it shows I#m still on the 2.7.0. dev branch?
Bildschirmfoto 2023-07-30 um 10.48.45.png
If I hit confirm it stalls with:

Another instance of pfSense-upgrade is running.  Try again later

Same if I try to update packages or try to install new packages!

Any idea howto fix that?

Regards,

Christian

peters77

If I did an pkg-static update -f

I get:

Updating pfSense-core repository catalogue...
Fetching meta.conf: 100%    163 B   0.2kB/s    00:01    
Fetching packagesite.pkg: 100%    2 KiB   1.8kB/s    00:01    
Processing entries: 100%
pfSense-core repository update completed. 7 packages processed.
Updating pfSense repository catalogue...
Fetching meta.conf: 100%    163 B   0.2kB/s    00:01    
Fetching packagesite.pkg: 100%  154 KiB 157.5kB/s    00:01    
Processing entries:   0%
Newer FreeBSD version for package zstd:
To ignore this error set IGNORE_OSVERSION=yes
- package: 1400093
- running kernel: 1400090
Ignore the mismatch and continue? [y/N]: 
pkg-static: repository pfSense contains packages for wrong OS version: FreeBSD:14:amd64
Processing entries: 100%
Unable to update repository pfSense
Error updating repositories!

...?

peters77

pfSense-upgrade -d -c

shows:

pfSense-repoc-static: invalid signature
failed to read the repo data.
failed to update the repository settings!!!
failed to update the repository settings!!!

peters77

pkg-static upgrade -f

on the cmd line did the update to the latest version which is reflected in the gui now.
But I'm still unable to install any more package. :-(
Try to install wireguard but got:

Another instance of pfSense-upgrade is running.  Try again later

jimp

We aren't publishing 2.8.0 repo information to the public at the moment because we just did a large upstream merge and we need to test things internally before unleashing it for wider testing. For example, the builds now have OpenSSL 3.0 so we need to assess the impact of that.

$ openssl version
OpenSSL 3.0.9 30 May 2023 (Library: OpenSSL 3.0.9 30 May 2023)

mrmanuel

Is this still the case, more than a year later?

stephenw10

Is what still the case? You shouldn't be seeing 2.8-dev available. That was a glitch in the update repos that was fixed long ago.

Patch

@jimp said in update and package install in 2.8.0-DEVELOPMENT (amd64) no longer possible....:

We aren't publishing 2.8.0 repo information to the public at the moment because we just did a large upstream merge and we need to test things internally before unleashing it for wider testing. For example, the builds now have OpenSSL 3.0 so we need to assess the impact of that.

@mrmanuel said in update and package install in 2.8.0-DEVELOPMENT (amd64) no longer possible....:

Is this still the case, more than a year later?

A very reasonable question imo.
A year is a long time to assess the impact of OpenSSL 3.0 of any of the other immediate effects of an upstream merge.

Which places some doubt on if that was ever really the reason.

@Patch said in Is CE really slower with (security) updates compared to plus ?:

In contrast Netgate now just develop the propriety (Plus) version. Then when they feel like it they later release / back port the features they want to release to the CE version. This approach removes all benefit of the CE version to Negate, leaving it only as competition and a burden to support. It's only value to Netgate I can see is it lets them claim pfsense is open source and limits concentrated user backlash. Time will see how long it lasts.

History so far
CE v2.7.0 and plus v23.05 & v23.05.1 were released in Jun 2023 with 103 + 14 common redmine issues. 13 v2.7.0 added plus in v23.09

CE v2.7.1 and plus v23.09 was released in Nov 2023 with 132 common redmine issues. 5 v2.7.1 added to plus in v23.09.1

CE v2.7.2 and Plus and v23.09.1 were released in Dec 2023 with 19 common redmine issues.

Plus v24.03 was released in Apr 2024 with 108 redmine issues in common with unavailable CE v2.8 and 2 issues possibly in later CE version CE-Next

Plus v24.08 has 94 redmine issues in common with unavailable CE v2.8 and 27 issues possibly in later CE version CE-Next

Which implies significant risk in any user assuming the updates to the open source version will be available going forwards. Which maybe confirmed by

@stephenw10 said in update and package install in 2.8.0-DEVELOPMENT (amd64) no longer possible....:

You shouldn't be seeing 2.8-dev available. That was a glitch in the update repos that was fixed long ago.

mrmanuel

Thanks for all replies. Every day I'm experiencing more and more regressions in pfSense, so I was hoping to test at least the beta. Is there no possibility to do so?

stephenw10

Not currently. In CE at least.