Dear All,
long time was OK with Tumbleweed.
now, trying to install i.e. wine, rstudio i get issue with the repo below:
https://download.opensuse.org/repositories/openSUSE:/Tumbleweed:/OldKey/standard/ (openSUSE:Tumbleweed:OldKey)
do you know how to fix the issue?
This is an invalid repository. Only you know why and how you added it. Show the full output of
zypper lr -d
Hello hui,
thank you for your answer.
i did not add this repo.
when installing a wine i get such window:
your command gives:
| Alias | Name | Enabled | GPG Check | Refresh | Priority | Type | URI | Service
—±-------------------------------------±---------------------------------------±--------±----------±--------±---------±-------±------------------------------------------------------------------------------±-------
1 | download.opensuse.org-non-oss | Main Repository (NON-OSS) | Yes | (r ) Yes | Yes | 99 | rpm-md | http://download.opensuse.org/tumbleweed/repo/non-oss/ |
2 | download.opensuse.org-oss | Main Repository (OSS) | Yes | (r ) Yes | Yes | 99 | rpm-md | http://download.opensuse.org/tumbleweed/repo/oss/ |
3 | download.opensuse.org-tumbleweed | Main Update Repository | Yes | (r ) Yes | Yes | 99 | rpm-md | http://download.opensuse.org/update/tumbleweed/ |
4 | https-download.opensuse.org-1e4f4c1e | openSUSE:Tumbleweed | Yes | (r ) Yes | Yes | 99 | rpm-md | https://download.opensuse.org/repositories/openSUSE:/Tumbleweed/standard/ |
5 | https-download.opensuse.org-ccd190f3 | Emulators | Yes | (r ) Yes | Yes | 99 | rpm-md | https://download.opensuse.org/repositories/Emulators/openSUSE_Tumbleweed/ |
6 | openSUSE-20230209-0 | openSUSE-20230209-0 | No | ---- | ---- | 99 | rpm-md | hd:/?device=/dev/disk/by-id/usb-Wilk_GOODRAM_8GB_070147A3C1B25A49-0:0-part2 |
7 | repo-debug | openSUSE-Tumbleweed-Debug | No | ---- | ---- | 99 | NONE | http://download.opensuse.org/debug/tumbleweed/repo/oss/ |
8 | repo-openh264 | Open H.264 Codec (openSUSE Tumbleweed) | Yes | (r ) Yes | Yes | 99 | rpm-md | Index of /openh264/openSUSE_Tumbleweed |
9 | repo-source | openSUSE-Tumbleweed-Source | No | ---- | ---- | 99 | NONE | http://download.opensuse.org/source/tumbleweed/repo/oss/ |
10 | snappy | snappy | Yes | (r ) Yes | Yes | 99 | rpm-md | https://download.opensuse.org/repositories/system:/snappy/openSUSE_Tumbleweed |
You don’t need an additional repo to install wine, as it is contained in the OSS repo. Simply use “zypper in wine” or the GUI way via yast2-software.
You did the big mistake to use one-click install. This leads to broken repos. Never use one-click installs (search forum if you need more information.).
Remove repo 4 and 5 as they are from one-click installs.
Remove repo 6 as it is your initial installation media.
If you want to add packages from additional repos, always use the expert way to add the repo. This will prevent you from adding broken one-click install repos.
hej hui
thanks for your comments. just wanted to get the version 8 of wine, thats why i tried one click.
to be fair, nobody warned me to not use the one click install…
i have removed the 4-6 repos now.
i need to work Rstudio, but the repo is broken (same issues as above) and not available on the Discover.
do you know where to fine the package if you are so handy with Suse?
i am still learning and after 1,5y i am a newbie 
Sorry, but what you describe is strange. Why do you try to use additional repos? Did you ever use the search function in the graphical yast2-software? Please don’t use Discover! Use the openSUSE yast2-software! Or didn’t you just simply try to install the packages via commandline
zypper in wine
zypper in rstudio
wine-8.0 is in the standard Tumbleweed OSS repo
rstudio-2022.02.2 is in the standard Tumbleweed OSS repo
rstudio from above installation way does not work. i had to break some dependencies…
i use some flatpaks, one snap and rest installed from Discover…
i know that i should not use Discover and keep only Yast Software.
so far everything worked more than well.
last week i had to change the m2 drive and reinstall system.
and some issues has started… you get lazy without problems but not running RStudio is a key problem for me.
rstudio is broken far beyond recognition and doesn’t build anymore as dependencies are unfulfilled…even home repositories are affected.
I wasn’t able to find a repo with a properly built rstudio. This looks like an upstream problem if i read some of the comments…
this is what i read as well.
anyway, thanks for your help and time.
i start to consider running ubuntu in KVM with Rstudio 
have a good remaining Sunday.
again, sorry for posting after myself.
i have managed to install the R Studio and it works.
i used the daily builds, it reports there is missing signature but press ignore and it installs:
sudo zypper install ./rstudio-2023.03.0-382-x86_64.rpm
Loading repository data...
Reading installed packages...
Resolving package dependencies...
The following 2 NEW packages are going to be installed:
libpq5 rstudio
2 new packages to install.
Overall download size: 132.3 MiB. Already cached: 0 B. After the operation,
additional 576.6 MiB will be used.
Continue? [y/n/v/...? shows all options] (y): y
Retrieving: libpq5-15.2-1.1.x86_64 (Main Repository (OSS)) (1/2), 217.0 KiB
Retrieving: libpq5-15.2-1.1.x86_64.rpm .......................[done (3.0 KiB/s)]
Retrieving: rstudio-2023.03.0+382-1.x86_64 (Plain RPM files cache)
(2/2), 132.1 MiB
rstudio-2023.03.0-382-x86_64.rpm:
Header V4 RSA/SHA256 Signature, key ID 3f32ee77e331692f: NOKEY
V4 RSA/SHA256 Signature, key ID 3f32ee77e331692f: NOKEY
warning: /var/tmp/zypp.fC5e7G/zypper/_tmpRPMcache_/%CLI%/rstudio-2023.03.0-382-x86_64.rpm: Header V4 RSA/SHA256 Signature, key ID e331692f: NOKEY
Looking for gpg key ID E331692F in cache /var/cache/zypp/pubkeys.
Repository Plain RPM files cache does not define additional 'gpgkey=' URLs.
rstudio-2023.03.0+382-1.x86_64 (Plain RPM files cache): Signature verification failed [4-Signatures public key is not available]
Abort, retry, ignore? [a/r/i] (a): i
Checking for file conflicts: ....................................................................................................[done]
(1/2) Installing: libpq5-15.2-1.1.x86_64 ........................................................................................[done]
warning: /var/cache/zypper/RPMS/rstudio-2023.03.0-382-x86_64.rpm: Header V4 RSA/SHA256 Signature, key ID e331692f: NOKEY
(2/2) Installing: rstudio-2023.03.0+382-1.x86_64 ................................................................................[done]
Executing %posttrans scripts ....................................................................................................[done]
You download the rpm, where should zypper see for the key, that is in the Repo of rstudio (if it exists)?
So only way is to ignore or add the Repo or download and add the key by hand…
Going to bump this topic because it’s relevant: Every “1 Click Install” for https://software.opensuse.org/package/ is trying to add nonexistent repo https://download.opensuse.org/repositories/openSUSE:/Tumbleweed:/OldKey/standard/ (openSUSE:Tumbleweed:OldKey) for me.
I can no longer use “1 Click Install” from software.opensuse.org because of this and must manually add repos (if necessary) and use the terminal.
No amount of "me too"s on this forum is going to fix it. Someone needs to create a patch and convince developers that this patch is correct and needs to be applied. “Bumping” it won’t auto-magically do it.
I’m… sorry? But not really sorry. Am I to understand the repos added when using the yast “1 Click Install” is the cause of this issue, or is that repo somehow added to every OBS build? I would not mind assisting in tackling my issue myself, but if you would be so kind as to “point” me into the right direction of where the problem is, I can take action from there, building my own packages and installing them locally if I have to.
EDIT: It looks like this OBS entry explains a lot:Show openSUSE:Tumbleweed:OldKey - openSUSE Build Service
Tumbleweed Old Key
This is a temporary project to provide the former openSUSE Factory key
until factory got a full rebuild.otherwise local build package validation is complaining when used in unsecure build
environments like chroot.
And " empty-fake-package" was last changed about 2 months ago, which is about the time I believe I started experiencing this issue.
OBS was not designed as a platform to publish packages. OBS was designed as a platform to build packages. So, from the OBS point of view it is perfectly legal to have project that is not published but used when building packages in other projects.
Because packages built in one project may depend on packages from other projects, 1 Click Install tries to add all repositories which may be necessary (technically - all repositories listed in project definition). Unfortunately, when generating repositories list 1 Click Install does not distinguish between “build only” repositories and “published” repositories.
From the point of view of OBS developers there is no bug - it works as designed. To fix it one needs to either find out how to filter out repositories when generating 1 Click Install metadata using existing information or extend OBS to somehow mark such repositories. Which is why I said: “create patch and convince developers it really has to be applied”. Both may not be quite easy.
