-
-
Notifications
You must be signed in to change notification settings - Fork 129
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
Flag lib32 out of date when non lib32 marked out of date #230
base: master
Are you sure you want to change the base?
Conversation
Signed-off-by: Lars Rustand <[email protected]>
Thanks for the PR, just started testing, the second message after entering an out of date text only lists the original flagged out of date package. while two packages where flagged out of date. It would be nice to also list that This message is what I am talking about.
I'm also wondering if this case is always valid hmm since lib32-foo can be updated before foo, so maybe it should try and compare the pkgver. Already found such a case here:
|
Oops, didn't actually test more than the first step. I will see what I can
do about it.
|
Signed-off-by: Lars Rustand <[email protected]>
This should take care of the issues you mentioned. |
Signed-off-by: Lars Rustand <[email protected]>
Found one issue when flagging lib32-libssh2 out of date while libssh2 was already flagged:
Since libssh is in [testing] and [core] in my test setup. |
I'm sorry it has taken so long for me to respond to this. Currently I don't have the time to look at this for a while, but feel free to finish the work on this if you want. |
Took a stab at trying to fix issue #110, marking lib32 package as out of date when non lib32 package is flagged. I also added the reverse case, when a lib32 package is flagged the non lib32 package (and others based on the same pkgbase) also get flagged. Hope I got everything right as this is my first time working with django.