MuPDf cannot be updated from 1.17.0-rc1 to 1.17.0.

[NamelessUzer]

MuPDf cannot be updated from 1.17.0-rc1 to 1.17.0. I believe the reason is they have the same extract dir mupdf-1.17.0-windows.

[mark05e]

i think you should uninstall / install in this scenario

[NamelessUzer]

i think you should uninstall / install in this scenario

This of course can solve the problem. But is it OK to let users follow your method every time when they encounter the same situations?

[mark05e]

Sure - Though I say this from personal experience.

[mark05e]

Just went through the script again and observed that $matchHead variable was used when extracting the directory.

I have proposed a change to use the $version variable. Difference between the two variables:

• $version: 3.7.1
• $matchHead: Returns first two or three digits seperated by a dot (e.g. 3.7.1-rc.1 = 3.7.1 , 3.7.1.2-rc.1 = 3.7.1 or 3.7-rc.1 = 3.7)

[mark05e]

@ssfjhh - looks like the first proposed solution is the way to go.

Updates to release candidates are not desired

ref

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[NamelessUzer]

The problem reappeared again. Should we reopen this issue? mupdf has updated to 1.20.0 . https://github.com/ScoopInstaller/Extras/blob/22820921192115c8f58863d60fb203805af7cc9f/bucket/mupdf.json#L2 But scoop treated 1.20.0-rc2 as the latest version. `> scoop update mupdf

mupdf: 1.20.0-rc2 (latest version) Latest versions for all apps are installed! For more information try 'scoop status'`

[rashil2000]

Actually, it shouldn't consider rcX versions, because they're release candidates. The checkver needs to be modified.

[niheaven]

Set force_update to true will force scoop update to bucket version and may temporally fix the issue

scoop config force_update true