As per subject :
A pair of RB951 detect new version despite the same is listed above.
Same behavior checking/updating via script.
Any idea ?
New version available is ROS 7. To update to ROS 7 you need it manually dragging and dropping inside Winbox the NPK file downloaded previously for the architecture of your device.
Regards.
But it shouldn’t show that when using stable channel.
Only when first going through upgrade-channel. No ?
He is using stable channel. When I upgraded to ROS7 I’m also used 6.49.8 and the only “solution” is upgrading to ROS 7 because it’s logic. Actual ROS 7.10.2 is newer than 6.49.8, but you can’t upgrade by assistant because I think for kernel version changes and you need update manually. It’s the same when upgrade from Debian 11 to Debian 12, you need do it manually changing the repositories and then update.
Regards.
But do they pay you to write this bulls–t?
@OKNET
Actually exist two version of RouterOS 6.49.8, one 6.49.8 build 1689763242 and one 6.49.8 build 1684760871
If you have installed the build 1684760871 and you select long-term, the system offers to upgrade to 1689763242, but visually… change nothing… “version 6.49.8”.
If you have installed the build 1689763242 and you select stable, the system offers to downgrade to 1684760871, but visually… change nothing… “version 6.49.8”.
The last version is what is proposed if you select “long-term”.
The binary downloaded from MikroTik is the same (the last long-term build 1689763242). Is on the version check the error.
Why MikroTik do that?
Because the staff don’t work for me, otherwise I’d have them correct this terrible bulls–t, which does nothing but confuse users.
Info sources (lat checked on 2023-08-01 at 19:49 CEST):
https://upgrade.mikrotik.com/routeros/LATEST.6fix = 6.49.8 1689763242
https://upgrade.mikrotik.com/routeros/LATEST.6 = 6.49.8 1684760871
… Cry or laugh? Best laugh…
Thanks for the info rextended.
Not clear: stable and long-term download link point to the same file : https://download.mikrotik.com/routeros/6.49.8/routeros-mipsbe-6.49.8.npk !!
Why all my other 6.49.8 machines say “already up to date” ?
Do you mean my two RB saying “new version available” have long-term installed instead of stable (or vice-versa) ??
How is it possible , when all my actual 6.49.8 machines follow the same upgrade script ??
How eventually can I get 1689763242 rather than 1684760871 ?
From position 0x28:
AA-BD-B7-64 = 1689763242
Your link is the last 6.49.8 (long-term) build 1689763242
There isn't a question that hasn't already been answered in my previous post.
For install the last version, select long-term, not "stable"
Well, I actually select nothing, my script does :
/system package update
check-for-updates once
:if ( [get status] = “New version is available”) do={
install
}
If the “wrong” 6.49.8 is already installed (you said 1684760871 asks to upgrade) where can I get the other 6.49.8 if the one link points to is still the wrong one ?
Is impossible to select "nothing".
Or check for long-term, or check for stable, or check for the other options, basing as it is already set up.
This is the last time I'll answer you, I feel like you're kidding me.
Rex, sorry to intervene but your explanation is not clear.
It doesn’t make sense to me either.
Please be specific as to WHICH version he needs to use.
@holvoetn
Tell me what's not clear here:
That last sentence.
What does that mean ?
Is better with "?
Is on the “version check” the error.
Or this?
The error is in the internal process for verifying if the installed version is updated.
That last version is perfect.
Now I get what you mean.
We’re here not to kidding anyone, explaining something that is SO clear in explainer mind, is one of most difficult task when discussing online.
You said there are TWO version of 6.49.8 , so I understand two .npk files.
On mikrotik “software” V6 section there are two columns: long-term and stable for each architecture , anyway those two point to SAME ARCHIVE FILE :
https://download.mikrotik.com/routeros/6.49.8/routeros-mipsbe-6.49.8.npk (in my case of mipsbe)
Is this real long-term or stable ? You said long-term.
Ok I put it into RB files section and reboot trying to force a system update , nothing changes, probably because the same version is already installed, probably the same happens when installing via script.
How can I install that 6.49.8 that won’t tell me “new version is available” like in all other 6.49.8 routerboards I own ???
At this point , what am I not understanding ??
Speculating here …
Assuming Rex is correct about the error in the upgrade check process (quite likely, he’s usually right about these things 
), maybe you first need to DOWNgrade.
Then apply the latest version manually.
And then it should be the real latest version.
I’ll give it a try.
I’m asking why this behavior in two machine only, probably they have been updated lately when the long-term was left as the only package available.
Most likely explanation, I think.
BTW automatic upgrade is usually a bad idea.