On Tue, 2020-06-16 at 08:32 +0300, Andrei Borzenkov wrote:
16.06.2020 03:58, Malcolm пишет:
My understanding is Package Hub is generally using the Leap packages so it won't provide much help in this case.
Hi Packages must exist in Factory/Tumbleweed to go back into Backports.
Sure version X.Y might exist in Leap, but Y.Z in Tumbleweed which is what would be subbed to this 'Community Backports' repository...
It really is just an aggregation of all those later version leaf packages that are present in Tumbleweed, but not Leap.
If package can be built in Leap environment, it would have been built in Leap repository in development project. The problem are packages that stopped building. No amount of reshuffling download location is going to replace someone actively maintaining new versions in old environment.
The problem is not "where to offer download", but usual "who is going to maintain them".
Sure, maintainance for older OS versions requires precious additional maintainer resources. We can't demand this from people who maintain openSUSE packages in their spare time. All I'm saying is that from a maintainer perspective, trying to fix the build for older distributions is not useless. It broadens the possible range of users for the package, and (at least for an old-fashioned person like me) it's a sign of code maturity if it doesn't just work in the latest environments. So this would also be a call to action for Leap users - rather than complaining that your desired package isn't available for Leap, branch the factory or devel repo package, fix it, and submit it back. One problem is IMHO that we constantly try to "modernize" spec files for Factory. More often than not, this means using rpmbuild features that are unavailable in older distributions. Thus, in a way, we create incompatibility ourselves, where it doesn't need to exist. Martin -- Dr. Martin Wilck <mwilck@suse.com>, Tel. +49 (0)911 74053 2107 SUSE Software Solutions Germany GmbH HRB 36809, AG Nürnberg GF: Felix Imendörffer