Tumbleweed-cli has no effect

English Applications
1

I’m not sure since when, but I realised that tumbleweed-cli is not changing the repositories anymore. These are my repositories right now:

# zypper repos -u
Repository priorities are without effect. All enabled repositories share the same priority.

# | Alias                             | Name                             | Enabled | GPG Check | Refresh | URI
--+-----------------------------------+----------------------------------+---------+-----------+---------+-----------------------------------------------------------------------------------
1 | download.nvidia.com-tumbleweed    | nVidia Graphics Drivers          | Yes     | (r ) Yes  | Yes     | https://download.nvidia.com/opensuse/tumbleweed
2 | ftp.gwdg.de-openSUSE_Tumbleweed_1 | Packman Repository               | Yes     | (r ) Yes  | Yes     | http://ftp.gwdg.de/pub/linux/misc/packman/suse/openSUSE_Tumbleweed/
3 | libnvidia-container               | libnvidia-container              | Yes     | (r ) Yes  | No      | https://nvidia.github.io/libnvidia-container/stable/opensuse-leap15.1/x86_64
4 | libnvidia-container-experimental  | libnvidia-container-experimental | Yes     | (r ) Yes  | No      | https://nvidia.github.io/libnvidia-container/experimental/opensuse-leap15.1/x86_64
5 | openSUSE:repo-non-oss             | repo-non-oss                     | Yes     | (r ) Yes  | Yes     | http://cdn.opensuse.org/tumbleweed/repo/non-oss
6 | openSUSE:repo-openh264            | repo-openh264                    | Yes     | (r ) Yes  | Yes     | http://codecs.opensuse.org/openh264/openSUSE_Tumbleweed
7 | openSUSE:repo-oss                 | repo-oss                         | Yes     | (r ) Yes  | Yes     | http://cdn.opensuse.org/tumbleweed/repo/oss
8 | openSUSE:repo-oss-source          | repo-oss-source                  | No      | ----      | ----    | http://cdn.opensuse.org/source/tumbleweed/repo/oss
9 | openSUSE:update-tumbleweed        | update-tumbleweed                | Yes     | (r ) Yes  | Yes     | http://cdn.opensuse.org/update/tumbleweed

according to tumbleweed-cli I’m on:

# tumbleweed status
latest   : 20240430
target   : 20240427
installed: 20240427

So I should be on 20240427, but as you can see there’s no mention of that in my repositories. I tried to remove the disabled repositories, such as:

# zypper removerepo 8
Removing repository 'repo-oss-debug' ..............................................................................................[done]
Removing repository 'repo-oss-debug' ..............................................................................................[done]
Repository 'repo-oss-debug' has been removed. [volatile]
Warning: Repo 'openSUSE:repo-oss-debug' is managed by service 'openSUSE'. Volatile changes are reset by the next service refresh!

So it seems that the “openSUSE” service keeps an eye on repositories, and probably prevents tumbleweed-cli from doing its job.

What am I doing wrong? Is tumbleweed-cli dead?

Thanks!

2

This command is useless as it misses the important information: the URL
Show

zypper lr -d
3

I realised that and corrected my post probably two seconds before yours. Is it useful now? :slight_smile:

4

The cdn.repos are inserted by an rpm:
show:
zypper se -si repos

5 
# zypper se -si repos
Loading repository data...
Reading installed packages...

S  | Name                             | Type    | Version              | Arch   | Repository
---+----------------------------------+---------+----------------------+--------+------------------
i  | girepository-1_0                 | package | 1.80.1-2.1           | x86_64 | (System Packages)
i  | libgirepository-1_0-1            | package | 1.80.1-2.1           | x86_64 | (System Packages)
i  | libgirepository-2_0-0            | package | 2.80.0-2.1           | x86_64 | repo-oss
i  | libpcreposix0                    | package | 8.45-3.1             | x86_64 | repo-oss
i  | librepository                    | package | 1.1.6-2.2            | noarch | repo-oss
i+ | openSUSE-repos-Tumbleweed        | package | 20240412.89bd714-3.1 | x86_64 | repo-oss
i+ | openSUSE-repos-Tumbleweed-NVIDIA | package | 20240412.89bd714-2.1 | x86_64 | (System Packages)
i  | typelib-1_0-GIRepository-3_0     | package | 2.80.0-2.1           | x86_64 | repo-oss
6

You need to remove and taboo openSUSE-repos-Tumbleweed and openSUSE-repos-Tumbleweed-NVIDIA.

Then you need to repeat tumbleweed init again, to ad the snapshot repos.

If you need the Nvidia repo, you need to add it again via the standard way…

7

ok thanks! That somehow also removed the main repos, but I added them back from Yast and tumbleweed-cli seems to be doing its job again.

8

Aaargh. One should not use tumbleweed-cli anymore. It can and will lead to serious breakage, often pretty much beyond repair.

9

wait, what, why?

10

Because things change quickly in TW, and going back to previous TW snapshot will not undo the changes already made. It does not work like f.e. a btrfs snapshot.

11

Who said anything about “going back”? I use Tumbleweed snapshots simply because it allows me to install additional packages without risking to potentially pull dozens and hundreds of updated dependencies. This is test system where I often install and remove something and I want stable environment which I update when I see appropriate.

12

I experimented with “tumbleweed-cli” and decided against using it. But it is still occasionally useful to access the history repos to revert to an earlier version of a package.

13

ok, I thought there was something new I was missing. Obviously it’s not a way to revert an update.

I use it with snapper. If an update makes my system unusable, I do a snapper rollback. This will also teleport me back to a previous TW snapshot, and I can sit on it until a future snapshot solves the problem. If I need to install anything from that snapshot while I wait I can, which I couldn’t do just by rolling back.

The only issue I have is when something has made a change in my home directory before I rollback, because the home is not rolled back. For instance, if I open a new version of thunderbird and then rollback, the old thunderbird complains.

I must say that I haven’t needed it in a while. It saved my back side several times in the past though (I have been rolling this installation for 6 years!), when TW was a lot less stable. Also when the nvidia repository was not aligned with the TW kernel it was a real mess.

14

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.