[SOLVED] ChangeLog.text is not updated on the https link on slackware.com

marav · 07-01-2021, 11:37 AM

Quote:

Originally Posted by chrisretusn

Solved? At this moment in time, no. 2021-07-01 22:26 PST (Philippine Standard Time)

http://www.slackware.com/changelog/c...php?cpu=x86_64 still shows:

Code:

Thu Jun 24 22:01:01 UTC 2021
kde/kmymoney-5.1.2-x86_64-1.txz: Upgraded.
n/gnupg2-2.2.28-x86_64-1.txz: Upgraded.
       Probably best to revert to this version for now.
x/xf86-input-libinput-1.1.0-x86_64-1.txz: Upgraded.
+--------------------------+
Wed Jun 23 20:40:52 UTC 2021
a/dialog-1.3_20210621-x86_64-1.txz: Upgraded.

Did I miss the solution?

The changelog is good
http://ftp.slackware.com/pub/slackwa.../ChangeLog.txt

I think this is just the script that generates the php page for x86_64 who probably has an issue

jkh2cpu · 07-01-2021, 11:44 AM

I'm the OP, and I just marked the post as unsolved. Yesterday I marked it solved when people were getting the message, but I see that I'm not making myself entirely clear.

Go to Slackware.com and click on ChangeLogs. Click the http link to slackware64-current, and you will find that the ChangeLog.txt is still dated 6/24. The ftp site for slackware64-current is up-to-date.

A noob is not going to figure this out. (I'm not asking for a discussion on whether or not noobs should be in the swift waters without hope or a clue.)

John.

jkh2cpu · 07-01-2021, 01:07 PM

I'm the OP. Now it is fixed!

John.

Wrong again, John. Yeah, it's different, but now it's the slackware64 ChangeLog.txt rather than the slackware64-current ChangeLog.txt. The former has always been up-to-date. I'm guessing that the next try will hit the mark.

John.

blancamolinos · 07-01-2021, 01:29 PM

For this link in Slackware site the last entry is for

Mon Jun 7 18:53:49 UTC 2021

http://www.slackware.com/changelog/c...php?cpu=x86_64

sombragris · 07-01-2021, 02:05 PM

I suggest to unmark the isue since it is not solved yet. Right now -current x86_64 gives me some June 7 changes as the latest updates. And I don't think this even belongs to current. This is yet to be fixed.

garpu · 07-01-2021, 03:43 PM

Heh, had a double-take that the patches only showed June 7 and were showing incorrect version numbers.

Didier Spaier · 07-01-2021, 04:07 PM

Move on, folks. Depending on the mirror to which the algorithm links (which can vary upon at least your IP) you can get or not an up to date information, as this mirror can have been synced or not since the last update, there's not much that can be done about that, unless there be a check in this algorithm to compare the file with the one on the primary mirror. And this check would be costly, even more so if done for all files to be downloaded some of which can be real huge.

Bottom line: find a mirror that is reasonably up to date, close to you and fast in the mirror list, and use that one.

sombragris · 07-01-2021, 04:39 PM

Quote:

Originally Posted by Didier Spaier

Move on, folks. Depending on the mirror to which the algorithm links (which can vary upon at least your IP) you can get or not an up to date information, as this mirror can have been synced or not since the last update, there's not much that can be done about that, unless there be a check in this algorithm to compare the file with the one on the primary mirror. And this check would be costly, even more so if done for all files to be downloaded some of which can be real huge.

Bottom line: find a mirror that is reasonably up to date, close to you and fast in the mirror list, and use that one.

I don't think the mirror has anything to do with this. Both the default and selected mirror were up to date but still the webpage showed outdated or incorrect content.

Now it appears to be fixed.

bassmadrigal · 07-01-2021, 09:05 PM

Quote:

Originally Posted by Didier Spaier

Move on, folks. Depending on the mirror to which the algorithm links (which can vary upon at least your IP) you can get or not an up to date information, as this mirror can have been synced or not since the last update, there's not much that can be done about that, unless there be a check in this algorithm to compare the file with the one on the primary mirror. And this check would be costly, even more so if done for all files to be downloaded some of which can be real huge.

Bottom line: find a mirror that is reasonably up to date, close to you and fast in the mirror list, and use that one.

Do you really think the website has the logic to pick the mirror closest to the person when updating the ChangeLog page?

We're talking about the http://www.slackware.com/changelog/current.php?cpu=x86_64 page, not https://mirrors.slackware.com/slackware/slackware64-current/ChangeLog.txt

I doubt that page uses the mirrorbrain service like mirrors.slackware.com. It's probably set to check a specific server no matter who accesses the webpage. It is likely that the script used was broken or the mirror used by the script was out-of-date.

Either way, it's fixed now.

chrisretusn · 07-01-2021, 10:03 PM

Quote:

Originally Posted by marav

The changelog is good
http://ftp.slackware.com/pub/slackwa.../ChangeLog.txt

I think this is just the script that generates the php page for x86_64 who probably has an issue

I just checked it and now http://www.slackware.com/changelog/c...php?cpu=x86_64 is good.

chrisretusn · 07-01-2021, 10:10 PM

The site is good now. Like @bassmadrigal said, I doubt the site (http://www.slackware.com/changelog/c...php?cpu=x86_64) is use the "mirrors" to get the changelog.

I don't use it for mirroring my local copy at any rate. I use it to check the log everyday. It's a pinned tab (so is stable) in my browser so they load when I start my browser so I can see what's been updated. The mirror I use has been on target.