On Thu, Nov 2, 2023 at 11:12 AM Arjen de Korte <suse+build@de-korte.org> wrote:
Citeren "Carlos E. R." <robin.listas@telefonica.net>:
On 2023-11-02 01:31, Simon Lees wrote:
On 11/2/23 09:19, Carlos E. R. wrote:
On 2023-11-01 17:14, Ben Greiner wrote:
Am 01.11.23 um 05:52 schrieb Roger Oberholtzer:
This repo seems to have gone away:
http://download.opensuse.org/repositories/devel:/languages:/python/15.5
Now there is one for 15.6 instead.
I'll guessing that this is a mistake?
Friendly reminder not to use devel:languages:python as repository. Ever.
From the project description:
Backporting of packages against older distribution releases should not be happening in this project, only build verification. If a package is needed on any of the older openSUSE products then maintenance update is to be created. Alternatively for SLE products submission by an interested party should be done by openSUSE:Backports project.
Where in YaST or zypper can we read those descriptions before we add a repo?
Tools to add repos, like the web search, or "opi", don't give any information. We users only have the name of the repos.
This info doesn't exist because none of these repositories are designed or intended to be used by general end users. They exist in general to be used by developers for development and testing purposes and shouldn't be considered something that is officially offered or supported by the openSUSE project. Although there are times where more experienced users do use some of these repo's at there own risk although this is certainly not something recommended by the project in general.
My point is, how are we to know?
The fact that openSUSE has extra repos is a selling point in the promotion materials. But we have no way to know which repos we can use and which we can't.
We just need some application that is not in the main repos, we use the facilities to find what repo has it, we add the repo, install the package, maybe the package wants some extra library, we search for it, we add that extra repo. No one tells us what repos are good to use and which are not. There is no repository description anywhere that we can read.
I beg to differ:
https://build.opensuse.org/project/show/devel:languages:python
Before adding a development project, it makes sense to at least check the project on OBS.
*Users* do not even know that OBS exists, what it is for or how to interpret information there. Users get redirected from software.opensuse.org (most common case) to 1-click install or sometimes just get a direct link to download.opensuse.org. Not much can be done about the latter, but the former boils down to the usual complaints about s.o.o being unsuitable as the end user-facing tool. Although even in the latter case zypper could support a mechanism to display a warning when adding a repository (as part of repository metadata) and such warnings could be generated automatically by OBS.
There is a communication problem here.
(I think I needed to add the python repo at some point on some computer because some other program, perhaps some update of SA, wanted it. I don't have access at the moment to that computer to check.)