I wanted to update my ipfire from core 180 to 184, but pakfire only gives me the option for core update 183. I have refreshed pakfire several times over the last few days, unfortunately without success. Isn’t it possible to update directly from 180 to 181, 182 and 183? Or maybe I missed some update notice?
How can I get to 184 without reinstalling? Not that I necessarily want the new “design”, but otherwise one or two changes in 184 are interesting to me.
Oh, I checked the logs for pakfire, there is no error message of any kind, the refresh ends with HTTP 200 - OK, then “…finished”
Thanks for your help
I have no idea why you are having that problem. There was another forum user who was having the same problem yesterday or the day before.
I have updated three vm systems and one physical system and all went to 184 with no problems.
I have just checked a few of the mirrors and they had the 184 files available.
Even if some other mirrors are not synced the fact that some have the 184 files means that the update should be able to go ahead.
I am afraid I have no idea what might be causing the problem.
CU184 is already showing as being used by 13% of users with an enabled fireinfo profile.
Maybe someone else has some thoughts on what could be causing the problem.
Thanks for your quick reply, I appreciate it
I only see 183 stable as well,
Are you able to post your System log -Pakfire log ?
Today’s pakfire log:
Uhrzeit Abschnitt
15:17:37 pakfire: PAKFIRE INFO: Pakfire has finished. Closing.
15:17:37 pakfire: DOWNLOAD FINISHED: ipfire/pakfire2/2.27-x86_64/lists/core-list.db
15:17:37 pakfire: DOWNLOAD INFO: Signature of core-list.db is fine.
15:17:37 pakfire: DOWNLOAD INFO: File received. Start checking signature...
15:17:37 pakfire: DOWNLOAD INFO: HTTP-Status-Code: 200 - 200 OK
15:17:36 pakfire: DOWNLOAD INFO: ipfire/pakfire2/2.27-x86_64/lists/core-list.db has size of 903 b ytes
15:17:36 pakfire: DOWNLOAD INFO: Host: ftp.fau.de (HTTPS) - File: ipfire/pakfire2/2.27-x86_64/lis ts/core-list.db
15:17:36 pakfire: MIRROR INFO: 21 servers found in list
15:17:36 pakfire: DOWNLOAD STARTED: lists/core-list.db
15:17:36 pakfire: CORE INFO: core-list.db is 38027 seconds old. - DEBUG: force
15:17:36 pakfire: DOWNLOAD FINISHED: ipfire/pakfire2/2.27-x86_64/lists/packages_list.db
15:17:36 pakfire: DOWNLOAD INFO: Signature of packages_list.db is fine.
15:17:36 pakfire: DOWNLOAD INFO: File received. Start checking signature...
15:17:36 pakfire: DOWNLOAD INFO: HTTP-Status-Code: 200 - 200 OK
15:17:35 pakfire: DOWNLOAD INFO: ipfire/pakfire2/2.27-x86_64/lists/packages_list.db has size of 5 313 bytes
15:17:33 pakfire: DOWNLOAD INFO: Host: mirrors.ocf.berkeley.edu (HTTPS) - File: ipfire/pakfire2/2 .27-x86_64/lists/packages_list.db
15:17:33 pakfire: MIRROR INFO: 21 servers found in list
15:17:33 pakfire: DOWNLOAD STARTED: lists/packages_list.db
15:17:33 pakfire: DB INFO: packages_list.db is 38025 seconds old. - DEBUG: force
15:17:33 pakfire: DOWNLOAD FINISHED: 2.27-x86_64/lists/server-list.db
15:17:33 pakfire: DOWNLOAD INFO: Signature of server-list.db is fine.
15:17:33 pakfire: DOWNLOAD INFO: File received. Start checking signature...
15:17:33 pakfire: DOWNLOAD INFO: HTTP-Status-Code: 200 - 200 OK
15:17:33 pakfire: DOWNLOAD INFO: 2.27-x86_64/lists/server-list.db has size of 2068 bytes
15:17:32 pakfire: DOWNLOAD INFO: Host: pakfire.ipfire.org (HTTPS) - File: 2.27-x86_64/lists/serve r-list.db
15:17:32 pakfire: DOWNLOAD STARTED: 2.27-x86_64/lists/server-list.db
15:17:32 pakfire: MIRROR INFO: server-list.db is 38026 seconds old. - DEBUG: force
15:17:32 pakfire: PAKFIRE INFO: IPFire Pakfire 2.27-x86_64 started!
05:01:56 pakfire: PAKFIRE INFO: Pakfire has finished. Closing.
05:01:56 pakfire: CORE INFO: core-list.db is 1087 seconds old. - DEBUG: noforce
05:01:55 pakfire: DB INFO: packages_list.db is 1087 seconds old. - DEBUG: noforce
05:01:55 pakfire: MIRROR INFO: server-list.db is 1089 seconds old. - DEBUG: noforce
05:01:55 pakfire: PAKFIRE INFO: IPFire Pakfire 2.27-x86_64 started!
04:43:49 pakfire: PAKFIRE INFO: Pakfire has finished. Closing.
04:43:49 pakfire: DOWNLOAD FINISHED: pakfire2/2.27-x86_64/lists/core-list.db
04:43:49 pakfire: DOWNLOAD INFO: Signature of core-list.db is fine.
04:43:49 pakfire: DOWNLOAD INFO: File received. Start checking signature...
04:43:49 pakfire: DOWNLOAD INFO: HTTP-Status-Code: 200 - 200 OK
04:43:49 pakfire: DOWNLOAD INFO: pakfire2/2.27-x86_64/lists/core-list.db has size of 903 bytes
04:43:48 pakfire: DOWNLOAD INFO: Host: mirror1.ipfire.org (HTTPS) - File: pakfire2/2.27-x86_64/li sts/core-list.db
04:43:48 pakfire: MIRROR INFO: 21 servers found in list
04:43:48 pakfire: DOWNLOAD STARTED: lists/core-list.db
04:43:48 pakfire: CORE INFO: core-list.db is 85309 seconds old. - DEBUG: force
04:43:48 pakfire: DOWNLOAD FINISHED: ipfire/pakfire2/2.27-x86_64/lists/packages_list.db
04:43:48 pakfire: DOWNLOAD INFO: Signature of packages_list.db is fine.
04:43:48 pakfire: DOWNLOAD INFO: File received. Start checking signature...
04:43:48 pakfire: DOWNLOAD INFO: HTTP-Status-Code: 200 - 200 OK
04:43:47 pakfire: DOWNLOAD INFO: ipfire/pakfire2/2.27-x86_64/lists/packages_list.db has size of 5 313 bytes
04:43:46 pakfire: DOWNLOAD INFO: Host: mirrors.ocf.berkeley.edu (HTTPS) - File: ipfire/pakfire2/2 .27-x86_64/lists/packages_list.db
04:43:46 pakfire: MIRROR INFO: 21 servers found in list
04:43:46 pakfire: DOWNLOAD STARTED: lists/packages_list.db
04:43:46 pakfire: DB INFO: packages_list.db is 85308 seconds old. - DEBUG: force
04:43:46 pakfire: DOWNLOAD FINISHED: 2.27-x86_64/lists/server-list.db
04:43:46 pakfire: DOWNLOAD INFO: Signature of server-list.db is fine.
04:43:46 pakfire: DOWNLOAD INFO: File received. Start checking signature...
04:43:46 pakfire: DOWNLOAD INFO: HTTP-Status-Code: 200 - 200 OK
04:43:46 pakfire: DOWNLOAD INFO: 2.27-x86_64/lists/server-list.db has size of 2066 bytes
04:43:45 pakfire: DOWNLOAD INFO: Host: pakfire.ipfire.org (HTTPS) - File: 2.27-x86_64/lists/serve r-list.db
04:43:45 pakfire: DOWNLOAD STARTED: 2.27-x86_64/lists/server-list.db
04:43:45 pakfire: MIRROR INFO: server-list.db is 85308 seconds old. - DEBUG: force
04:43:45 pakfire: PAKFIRE INFO: IPFire Pakfire 2.27-x86_64 started!
1 Like
Okay, I think I understand what is happening.
My update was from 183 to 184.
You are going from 180 to 184.
However the major version changed in CU183 from 2.27 to 2.29
So pakfire is looking in the 2.27 version directories which will update to 183 because 182 will be 2.27-core182 and that mirror directory will update from 2.27-core182 to 2.29-core183.
Then a pakfire refresh will now refresh from the major version 2.29 directries which will then go from 2.29-core183 to 2.29-core184.
I believe that Pakfire does updates within one major version at a time so because your start and end numbers for the core updsates go across a major version pakfire will do it in two goes.
If you do an update at each Core Update release you will never experience this. If you leave several Core Updates to be done and they cross across a major version number change then the update will have to be done in two parts.
2 Likes
Basically, the proper way is to update first to 2.27 -core183
and then 2.29-core184 will become available ?
I believe so but i haven’t gone through the pakfire code to check it and don’t have the time currently to do that.
It is the fact that the mirrors have different directories for the 2.27 and 2.29 versions that makes me believe all CU versions within 2.27 will be first updated and then itcan get a new refresh from the 2.29 directories.
2 Likes
I noticed someone already updated IPFire on AWS, the last version was 182 and now it is 184, just an observation
Thank you for your efforts! Your explanation makes sense, I will give it a try over the weekend.
Will keep you informed
Your guess was absolutely correct, I updated directly to core 183 and in a second, separate step to 184.
thanks again for your support!
2 Likes