On 1/10/22 19:19, Matěj Cepl wrote:
Dne 10. 01. 22 v 8:37 Simon Lees napsal(a):
Something along the lines of users kept adding d:l:p to there Leap setups which would then cause unintended consequences as extra packages would be swapped and many things would break. d:l:p then disabled publishing for Leap to prevent this but some people inside SUSE needed this and some people in the community weren't that happy, so backports was created to 1. as Matej said meet the need of the people inside SUSE and 2. to make it less likely that users who installed this repo would completely break there systems.
Let me suggest this two-fold solution:
- We will stop publishing packages from Leap/SLE repositories of d:l:p.
If you want to pull from d:l:p:* you have d:l:p:backports for it.
- If there is any consensus, what should be added to project
configuration of d:l:p:backports, I will gladly add it, just with the caveats mentioned before (absolutely not maintenance aside from running backports_repo.py from time to time, so that the packages there are just a mirror of packages in Factory).
Sounds reasonable to me, from memory this resembles the setup we had when backports was first created.