-
Notifications
You must be signed in to change notification settings - Fork 17
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
Missing refresh of list of updatable packages, when switching testing repo off or on #103
Comments
Cannot reproduce it right now, will have to wait for package updates. In general, it should refresh all the packages on switching from regular to testing (or testing to regular), so it is a bug in implementation. Hopefully, can test it soon. |
I wish I could have been using the issue templates: I forgot to mention the version of the SailfishOS:Chum GUI application with which I observed this. Nevertheless, this bug is present in all versions up to (and including) v0.5.5, I tested it every now and then, mostly involuntarily.
Maybe it does that, but just does not refresh things at the GUI. OTOH, I can switch between pages and the stale package list remains, only closing and re-opening the SailfishOS:Chum GUI app does. Also note that I have never tried to install one of the packages from the SailfishOS:Chum:Testing repo after I switched back to the SailfishOS:Chum repo. |
I cannot reproduce it still. Every time I switch between testing and regular repository, I get the data updated. To check, select some package that you want to track. Let's say "Advanced Camera". Go to that package in regular repository and note version-release under "Available version". That may depend on SFOS version that you use. For me now, Advanced Camera displays as available version: 0.9.8-1.4.1.jolla . Without closing Chum GUI, if I switch to testing repo in GUI settings and go back to Advanced Camera, I will get 0.9.8-1.9.1.jolla. So, package versioning is updated as expected. As for not updated lists in "Updates", cannot see it either. Would have to try to catch a time when the list is different in regular and testing repo. |
That was not the original point rsp. not the test case: It only happened with a package, which was freshly updated locally (i.e., the update was installed). Side note: Sorry, my description was not really concise after the initial message here; I think it is unambiguous in the first message.
Patchmanager currently is updated in the testing, but not yet in the regular repo. Note that the "additional observation" also requires to have updatable packages in the regular repo and having installed one of these updates from the regular repo, before you switch to the testing repo, which also must offer updateable packages. |
I have tested with patch manager and cannot reproduce original issue:
I wonder if something is off in your repo configs. Check whether |
No, just the two OBS repos for Chum and Storeman. I will retest sometime the upcoming days or weekend, maybe on another device. |
yes, that looks absolutely fine. |
I cannot reproduce this either, now. Maybe I did something differently, maybe something is different, or I just had a knot in my brain. Sorry for the seemingly unnecessary fuzz. |
Observation
Additional observation
These (already updated) packages are displayed with "Installed version X.Y.Z" and "Available version X.Y.Z" (with identical version X.Y.Z).
Thus there seems to be something fundamentally wrong with the refreshing logic for the updates page.
Potential resolution
Do automatically and fully refresh the updates page after switching on or off the testing repository in the settings.
The text was updated successfully, but these errors were encountered: