On Thu, 27 Jan 2022 17:54:32 +0100, Marcus Meissner wrote:
or "here's a changelog that shows what has changed and when" - while that's included in the polkit.changes output, it's not in the RPM itself, so users who want to make sure something is patched don't really have an obvious place to look to see if a security issue has been fixed.
the changes file is in the RPM though:
rpm -q --changelog polkit
I never knew that command existed. Thank you for that (I'm used to looking for a changelog file in the docs directory).
The usage of SLE packages is a good thing and does make sense, but it seems there are some things that are less than ideal with this arrangement. Not being able to easily find the code for packages like this (I would never have thought to look under SUSE:SLE-15:Update even though I know SLE packages are used) is one such issue.
see andreas followup email.
Not being able to to search software.opensuse.org for packages for 15.3 is another (several people have reported issues with this - for example, searching for krita was one that someone had suggested), there is no package listed for 15.3. There's one for Tumbleweed and one for 15.2, but not for 15.3, and even for SLE-15-SP1, it's either 'experimental' or 'community'.
software.o.o might need some love, yes.
Thanks for confirming that. I've had a couple of folks in the openSUSE Facebook group complain about this, and I've suggested that they open bugzilla tickets so they can interact directly with whomever would be working to resolve it, but I don't know if they did (I hadn't run into the package issue myself, since I tend to have everything installed that I need at this point anyways), but we have had a couple of very vocal folks actively telling new users to stay away from 15.3 because of this issue. Jim -- Jim Henderson Please keep on-topic replies on the list so everyone benefits