Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fixed newer packages mistakenly considered as older #30

Merged
merged 2 commits into from
Jun 20, 2020
Merged

Fixed newer packages mistakenly considered as older #30

merged 2 commits into from
Jun 20, 2020

Conversation

Ballasi
Copy link
Contributor

@Ballasi Ballasi commented Jun 20, 2020

I had this prompt while using the program today.

image

After investigating the code, I realized that the number after the .r is being ignored.

With this exact setup (where oldVersion and newVersion are in the form of 456.r4x-1), the oldVer and newVer arrays becomes the same, and returns false.

I made a simple fix for now, but it probably needs a deeper look. I couldn't find any reliant package version conventions online, and I am not sure how the program should behave if the .rXX is being added or removed. For now, I just checked if it existed on both versions.

When a package had a pkgver containing `-rXX`, the number was ignored.
Therefore, the program can wrongly consider a newer package as older.
@ericm ericm merged commit eb8e4e8 into ericm:master Jun 20, 2020
@Ballasi Ballasi deleted the newer-fix branch June 20, 2020 22:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants