2.7.0 release has broken package management for 2.6.0 ?
-
Hi All,
I'm running multiple PFSense systems on 2.6.0 CE and I noticed 2.7.0 CE was released a couple of days ago.
At the same time all my 2.6.0 systems started reporting package updates are available for numerous packages, including:
arpwatch, avahi, cron, iperf, nmap, Notes, openvpn-client-export, pfBlockerNG-devel, RRD_Summary, snort, squid, and squidGuard to name a few.
I tried updating them on one system which is a testbed but it cannot update any of them with the following error:
WARNING: Current pkg repository has a new PHP major version. pfSense should be upgraded before installing any new package.So it seems that 2.6.0 is pointing to the 2.7.0 package repository, and trying to update incompatible packages ?
It's not just package updates that are not working however, much more seriously it's now seemingly impossible to install a new package on a 2.6.0 system at all.
For example if I try to install the avahi package on a 2.6.0 system which currently does not have it installed it also fails with:
WARNING: Current pkg repository has a new PHP major version. pfSense should be upgraded before installing any new package.Can someone from netgate please comment on whether this is just a bug/mistake or whether package updating/installing for 2.6.0 is now officially no longer possible ?
While I fully intend to update to 2.7.0 over time (after plenty of testing) I cannot at the moment, and if I cannot reinstall a package, I can't do disaster recovery from a backup as the system would not be able to reinstall packages during the restore. (Nor can I install any new features I don't currently already have installed)
Anyone else seeing this issue ?
-
D DBMandrake referenced this topic on
-
@DBMandrake said in 2.7.0 release has broken package management for 2.6.0 ?:
Anyone else seeing this issue ?
Yes, I'm seeing the same thing on a PC Engines APU2 running 2.6.0.
-
@Misterb Found the issue.
Due to the changes pushed to the repositories as part of the 2.7.0 release, 2.7.0 is now listed as "Current", so the Update settings are automatically trying to access 2.7.0 repositories even though the system is still running 2.6.0... seems a bit daft to me...
Go to System->Update->Update Settings, manually change the Branch to 2.6.0 then save settings. I have just done this to all my systems.
If you go to another page then come back it should now say "Previous Stable version (2.6.0 DEPRECATED)" and you should find there are no longer any invalid package updates waiting to install.
I was also able to successfully install a package that wasn't previously installed then uninstall it again.
Hope this helps.
-
@DBMandrake said in 2.7.0 release has broken package management for 2.6.0 ?:
Due to the changes pushed to the repositories as part of the 2.7.0 release, 2.7.0 is now listed as "Current", so the Update settings are automatically trying to access 2.7.0 repositories even though the system is still running 2.6.0... seems a bit daft to me...
In my eyes it's not daft, it's broken.
Go to System->Update->Update Settings, manually change the Branch to 2.6.0 then save settings. I have just done this to all my systems.
If you go to another page then come back it should now say "Previous Stable version (2.6.0 DEPRECATED)" and you should find there are no longer any invalid package updates waiting to install.
Almost. With my installation I'm still seeing an update to pfBlockerNG-devel available but all the other packages I have installed are showing up-to-date.
-
@Misterb said in 2.7.0 release has broken package management for 2.6.0 ?:
Go to System->Update->Update Settings, manually change the Branch to 2.6.0 then save settings. I have just done this to all my systems. If you go to another page then come back it should now say "Previous Stable version (2.6.0 DEPRECATED)" and you should find there are no longer any invalid package updates waiting to install.Almost. With my installation I'm still seeing an update to pfBlockerNG-devel available but all the other packages I have installed are showing up-to-date.
Ah wait, it's possible that there was already an update for pfBlockerNG-devel waiting to be installed which I had not bothered with in 2.6.0.
-
@Misterb I think there was a PFBlockerNG-Devel update for 2.6.0 a few weeks ago. Pretty sure I remember installing one.
-
@DBMandrake
https://redmine.pfsense.org/issues/10464
It's a long standing issue.Don't install packages for the wrong version. (yes I know that isn't what was intended) In the past it would try, and do things like upgrade PHP, breaking the old version.
Change System/Update/Settings to Previous Stable branch to be on 2.6, then install/update packages.
Edit: sorry didn't get down to @DBMandrake's later post saying this. I try to flag it everywhere I see it posted.
-
@SteveITS said in 2.7.0 release has broken package management for 2.6.0 ?:
@DBMandrake
https://redmine.pfsense.org/issues/10464
It's a long standing issue.Don't install packages for the wrong version. (yes I know that isn't what was intended) In the past it would try, and do things like upgrade PHP, breaking the old version.
The problem is, whether I tried to manually install a package via the GUI or not, some background process had already attempted to update some system packages (not those listed in the GUI) and in the process broken the pkg command itself. (although I notice the GUI uses pkg-static)
See my other thread.
This happened on four different systems, three of which I didn't even log into until I was aware of the issues on the first system, so definitely something that happened automatically as a result of the package repositories being updated on the servers.
I had to manually fix the pkg command on all four systems and they still complain about the fact that the FreeBSD package library is now using a newer database version than it should be.
This really shouldn't be happening without user interaction.
I haven't experienced these problems before because this is the first time that "Current" has changed versions in the repositories since I've been using PFSense. (Since I started with 2.6.0 which has been out for 1 1/2 years now)
Change System/Update/Settings to Previous Stable branch to be on 2.6, then install/update packages.
That doesn't fix the pkg command at the command line though, I had to fix that manually.