Packages installed from openSUSE:Factory repo

English Applications
1

Today I attempted to install alacritty and it failed with a resource not found error and I noticed the repo it was trying to hit was openSUSE:Factory rather than repo-oss.

I am not sure how openSUSE:Factory made it into the list of repos or if it should be there at all.
After a quick look I noticed there were a whole bunch of system packages installed from this repo so I ran zypper dup --from repo-oss --allow-vendor-change and this moved a whole bunch or packages back to repo-oss.
The openSUSE:Factory repo had the same priority as repo-oss, I have subsequently lowered the priority which allowed me to install alacritty.

Again, I have no idea how it got into this state or if it’s actually a problem. Could someone shed some light on what could be going on here, how I should handle it, and how I can clean up the packages left over?

For reference here is my current repo list.

#  | Alias                          | Name                          | Enabled | GPG Check | Refresh | Priority | URI---+--------------------------------+-------------------------------+---------+-----------+---------+----------+---------------------------------------------------------------------------------
 9 | repo-non-oss                   | openSUSE-Tumbleweed-Non-Oss   | Yes     | (r ) Yes  | No      |    1     | https://mirror.2degrees.nz/opensuse/tumbleweed/repo/non-oss/
10 | repo-oss                       | openSUSE-Tumbleweed-Oss       | Yes     | (r ) Yes  | No      |    1     | https://mirror.2degrees.nz/opensuse/tumbleweed/repo/oss/
 2 | download.nvidia.com-tumbleweed | nVidia Graphics Drivers       | Yes     | (r ) Yes  | No      |   90     | https://download.nvidia.com/opensuse/tumbleweed
 1 | brave-browser                  | brave-browser                 | Yes     | (r ) Yes  | No      |   99     | https://brave-browser-rpm-release.s3.brave.com/x86_64/
 3 | ftp.gwdg.de-Essentials         | Packman Essentials Repository | Yes     | (r ) Yes  | No      |   99     | http://ftp.gwdg.de/pub/linux/misc/packman/suse/openSUSE_Tumbleweed/Essentials
 5 | openSUSE-20220415-0            | openSUSE-20220415-0           | No      | ----      | ----    |   99     | hd:/?device=/dev/disk/by-id/usb-Verbatim_OTG_Tiny_070B5A591DFD0171-0:0-part2
 7 | packman                        | Packman                       | Yes     | (r ) Yes  | No      |   99     | https://ftp.gwdg.de/pub/linux/misc/packman/suse/openSUSE_Tumbleweed/
 8 | repo-debug                     | openSUSE-Tumbleweed-Debug     | No      | ----      | ----    |   99     | https://mirror.2degrees.nz/opensuse/debug/tumbleweed/repo/oss/
11 | repo-source                    | openSUSE-Tumbleweed-Source    | No      | ----      | ----    |   99     | https://mirror.2degrees.nz/opensuse/source/tumbleweed/repo/oss/
12 | repo-update                    | openSUSE-Tumbleweed-Update    | Yes     | (r ) Yes  | No      |   99     | http://download.opensuse.org/update/tumbleweed/
13 | server_database                | server:database               | Yes     | (r ) Yes  | Yes     |   99     | https://download.opensuse.org/repositories/server:/database/openSUSE_Tumbleweed/
14 | teamviewer                     | TeamViewer - x86_64           | Yes     | (r ) Yes  | No      |   99     | https://linux.teamviewer.com/yum/stable/main/binary-x86_64/
15 | vscode                         | Visual Studio Code            | Yes     | (r ) Yes  | No      |   99     | https://packages.microsoft.com/yumrepos/vscode
 4 | home_Dead_Mozay                | home:Dead_Mozay               | Yes     | (r ) Yes  | No      |  100     | https://download.opensuse.org/repositories/home:/Dead_Mozay/openSUSE_Tumbleweed/
 6 | openSUSE_Factory               | openSUSE:Factory              | Yes     | (r ) Yes  | No      |  200     | https://download.opensuse.org/repositories/openSUSE:/Factory/standard/
  • NB refresh is off as I handle this a different way
2 
 9 | repo-non-oss                   | openSUSE-Tumbleweed-Non-Oss   | Yes     | (r ) Yes  | No      |    1     | https://mirror.2degrees.nz/opensuse/tumbleweed/repo/non-oss/
10 | repo-oss                       | openSUSE-Tumbleweed-Oss       | Yes     | (r ) Yes  | No      |    1     | https://mirror.2degrees.nz/opensuse/tumbleweed/repo/oss/

Please switch the priority to 99 and switch refresh on at all Repos, you otherwise will run in trouble.

I would delete the factory Repo.

3

I have only changed the priorities after discovering this “issue” but, shouldn’t the priority be to install packages from these two repos? Could you please explain why they shouldn’t have a higher priority?

Also I don’t have auto refresh on as I have a cron job that does zypper ref and a “download only” dup every few hours.

4

Most people want install (not installed) packages from f. e. Packman not openSUSE.
So the Packman priority should be higher as openSUSE.

Same with packages from kf5 Repo or qt5 repo or or or.

So best practice is to let the priority of the OSS, non-OSS (SLE-Update, oss-Update, Backports-Update) on 99 and set the priority for other Repos.

5

Ok, that’s something to think about. However I’m not sure I would want to prioritise packman over the default repos … Rather, explicitly install packages from packman that I want from there; VLC for example. My understanding is that (unless I specify otherwise) the packages are “sticky” so a vendor swap wont happen regardless of priority. Is that incorrect? I guess I could achieve that by setting packman lower than the defaults.

I still don’t understand how/why I got so many packages from Factory. Nor if this is an actual problem position to be in? I’m kind of assuming that I don’t want this.

6

Thats why i wrote:

Most people want install (not installed) packages from f. e. Packman not openSUSE.

7

Nice list of repos. However you have no idea how it got into this state. My suggestion is using a configuration which works: https://forums.opensuse.org/entry.php/250-The-command-line-is-by-far-the-easiest-way-to-update-Tumbleweed

I use the above settings since May 2022 and perform daily upgrades for the single objective of proving their robustness. Even quarterly upgrades work well with the same settings