Probably because he offers security related packages there. Should he have named it “Unsecure” or “JustUseIt”? What is in a name?
Official is only OSS and non_OSS and their related Update, Debug and Source repos of an openSUSE version.
@rokejulianlockhart It’s an openSUSE Build Service Development project, staging prior to going into the distribution, that package is not one of them and just lives there from a maintenance perspective.
There are many repos like that where packages send and stage for going into a distribution. Or someone agrees to maintain and push to Factory, which gets a legal once over etc.
Ask any of the maintainers and they will say only use for testing…
1 Like
@hcvv, I thought all non-official repositories started with Home: to differentiate them from official ones.
Ah, @malcolmlewis, so it is an official repository, it just includes potentially untested packages? Does that mean that eventually it should be included in the official OSS repository? I’m using it now and it’s great.
@rokejulianlockhart No, which is part of the issue and a recent discussion on the Factory ML, along with the likes of opi.
If it’s in the ‘Distribution’ tree it’s official and supported, been through Legal checks and in most cases openQA. Development is for staging (and yes in some cases untested), then there are also ISV ones for Organizations using the openSUSE Build Service. Then home ones for whatever…
1 Like
Thanks for that. Seems unnecessarily convoluted having them all on the same level of hierarchy as Home: - you’d think at the top would be Official: and Home:, and then the former would contain the official repositories, simply named. But I’m no infrastructure engineer.
@malcolmlewis, can you point me to that?
I’ve installed veracrypt on TW from the security repository, haven’t had any issues with that. 1.26.7 is the version I have installed. That said, what @malcolmlewis said about that repo is correct - so it would be a ‘use at your own risk’.
1 Like
@rokejulianlockhart It’s that same python thread…
1 Like