On Mon, 22 Aug 2022 12:19:08 +0200, Simon Lees wrote:
On 8/22/22 18:39, Ben Greiner wrote:
Am 22.08.22 um 08:59 schrieb Simon Lees:
On 8/22/22 15:05, Takashi Iwai wrote:
On Sun, 21 Aug 2022 15:39:21 +0200, Eric Schirra wrote:
Sorry Takashi,
I don't think that's right. Because a few weeks ago I asked for exactly the same reason how the repos should be called, because you can't find a description/guideline anywhere. I was told: openSUSE_Leap_15.3 15.4 One long and one short. Well. That's how they want it.
I myself don't mind either way, honestly speaking.
If there is neither proper guide line nor official recommendation, I don't mind even to keep them as is, and proactively ignore any complaints about the resource usage.
In reality we have a pretty big mix everywhere with 15.3 some repo's changed others didn't this was pretty much at maintainers discretion while as a community we decided on this list that we should use 15.4 rather then openSUSE_
Whoever told him "how they want it" for 'openSUSE_Leap_15.3', was either wrong or speaking for their own special repo. It went the exact other direction in devel:languages:python, where his request to change it back caused everything to break down.
https://lists.opensuse.org/archives/list/packaging@lists.opensuse.org/thread...
I can't find the vote discussion on the mailing list archives anymore but I am pretty sure that it was before the 15.4 times. The change was from openSUSE_Leap_15.3 to 15.3
The decision was made for 15.4 before it was released (So that 15.4 was consistent when repos were created), some maintainers also chose to retrospectively do the change for 15.3
OK, after all, the below sounds like the likely-safe action: - openSUSE_Leap_15.4 is an incorrect repo setup, and should be dropped; either immediately or after some grace period. - openSUSE_Leap_15.3 seems already having some hanging users, and the coexistence with 15.3 seems more or less admitted. We may leave this for now until EOL of Leap 15.3. thanks, Takashi