since about 2 weeks I get a dependency-problem when updating my tumbleweed installation:
**argon:~/bin #** zypper dup --no-allow-vendor-change
Warning: You are about to do a distribution upgrade with all enabled repositories. Make sure these repositories are compatible before you continue. See
'man zypper' for more information about this command.
Loading repository data...
Reading installed packages...
Computing distribution upgrade...
Problem: bundle-lang-kde-en-13.2-41.1.noarch obsoletes k3b-lang < 17.04.0 provided by k3b-lang-2.9.90+git20170220.0453-8.5.noarch
Solution 1: keep obsolete bundle-lang-kde-en-13.2-39.2.noarch
Solution 2: install bundle-lang-kde-en-13.2-41.1.noarch (with vendor change)
http://packman.links2linux.de --> openSUSE
**Choose from above solutions by number or cancel [1/2/c] (c): **
At first, I just choose to keep the obsolete package, thinking packman will catch up, thus resolving the issue. But now it looks like that’s not the right solution.
On the other hand, I read all times at this forum, to update without allowing a vendor-change.
So, can anyone advice how to loose this issue, and in the same time, still have a consistent package-set?
Oh, my repolist:
**argon:~/bin #** zypper lr
Repository priorities are without effect. All enabled repositories share the same priority.
# | Alias | Name | Enabled | GPG Check | Refresh
--+----------------------------------+----------------------------+---------+-----------+--------
1 | download.opensuse.org-non-oss | Main Repository (NON-OSS) | Yes | (r ) Yes | Yes
2 | download.opensuse.org-oss | Main Repository (OSS) | Yes | (r ) Yes | Yes
3 | download.opensuse.org-tumbleweed | Main Update Repository | Yes | (r ) Yes | Yes
4 | libdvdcss | libdvdcss | Yes | (r ) Yes | Yes
5 | openSUSE-20170322-0 | openSUSE-20170322-0 | No | ---- | ----
6 | packman | packman | Yes | (r ) Yes | Yes
7 | repo-debug | openSUSE-Tumbleweed-Debug | No | ---- | ----
8 | repo-source | openSUSE-Tumbleweed-Source | No | ---- | ----
If any more info is needed, please let me know.
Thanks,
rolf
While I can’t answer your question, I would like to point you to the fact that your repo list might be correct, but that can not be checked because the URLs of the repositories aren’t there. In theorie, you can give any names and/or aliases to your repos, but the address where all packages should come from is the deciding information
Well, Packman’s k3b package is outdated.
The current version is 17.04.1, and currently there’s 17.04.0 in the standard repos.
bundle-lang-kde includes the k3b translations for the standard package in Tumbleweed, that’s why bundle-lang-kde obsoletes k3b-lang < 17.04.0.
This means that bundle-lang-kde-xxx replaces k3b-lang < 17.04.0, and that would normally done automatically without asking. But in this case a manual intervention is required because the package is from a different vendor (openSUSE vs. Packman), and you specified the “–no-allow-vendor-change” option)
Previously there was no problem because Tumbleweed only contained k3b 2.0.3 (which was a lower version than the one in Packman).
You basically have these options:
remove the k3b-lang package (will be done automatically if you choose “Solution 2”)
uninstall bundle-lang-kde-xxx (and maybe install all relevant -lang packages)
wait until k3b has been updated on Packman
For explanation: xxx-lang packages contain translations for a certain package. But in Tumbleweed there are also bundle-lang packages that contain selected translations in a certain language.
I.e. a bundle-lang package contains translations of many packages for one particular language. On the other hand, a -lang package contains translations for one package in all (available) languages.
In the end it doesn’t matter much which set you choose to install.
Actually you don’t even have to install any translations at all (all applications would be in english-only then), but they are recommended so you’d either have to lock them or disable the installation of recommended packages.
thx.
Is there any way to tell how long it takes for Packman to update? Mostly, they are quite fast, AFAIK.
And, when I understand correctly:
the ‘bundle-lang-kde-en’ contains the english translations for all KDE-applications that without that bundle would be in english anyway?
For many packages they just link to openSUSE:Factory (i.e. Tumbleweed), so their packages are updated automatically.
But the KF5 based k3b has only been released last month, and in Factory/Tumbleweed since a few days. The Packman maintainer(s) are probably not even aware of this (yet).
I wrote an email to the Packman mailinglist two days ago, but so far there hasn’t been a reply.
And, when I understand correctly:
the ‘bundle-lang-kde-en’ contains the english translations for all KDE-applications that without that bundle would be in english anyway?
Not exactly.
The english translations are built into the applications anyway as you write.
bundle-lang-kde-en contains the british english translations (where available), and some english documentations/manuals.
In any case, neither bundle-lang-xxx-yyy nor -lang packages are critical, especially if you use english as system language anyway.
