Updating tumbleweed comes up with the following problem:
Problem: problem with installed package libraw19-0.19.5-2.3.x86_64
Solution 1: install libraw19-0.19.5-142.21.x86_64 (with vendor change)
openSUSE --> obs://build.opensuse.org/graphics
Solution 2: keep obsolete libraw19-0.19.5-2.3.x86_64
Since I don’t use the repo “obs://build.opensuse.org/graphics” I think there must be another option?
Hi
You have the ‘graphics’ repository active (obs is the builder)… use 2 if not wanting to switch (since they are the same versions, just build number is different 142.21 vs 2.3).
You won’t find the problem with only that informmation…
You apparently have an application installed (likely some kind of graphics application) that requires the file.
If you don’t want to investigate further and track down which app requires this file, you can probably trust that location. In general, Developers who use OBS are typically trustworthy, it’s comparable to installing a package from a private repo from https://software.opensuse.org/search.
At least everything in OBS is public and open to scrutiny.
Otherwise you can ask yourself what graphics apps you have on your system, if any of them are unusual in some way.
Maybe even inspect your zypper update history to see what immediately preceded or followed this special file.
Of course, if you have some kind of unusual security issue to deal with, you might want to weigh the risk of special packages on your system.
TSU
Thank you, malcolmlewis and tsu2. I investigated further:
linux-4skc:~ # zypper rm libraw19
Reading installed packages...
Resolving package dependencies...
The following 14 packages are going to be REMOVED:
gegl-0_4 gegl-0_4-lang gimp gimp-lang gimp-plugin-aa gimp-plugins-python gwenview5 gwenview5-lang kdegraphics-thumbnailers libKF5KDcraw5 libgegl-0_4-0 libgimp-2_0-0 libgimpui-2_0-0 libraw19
14 packages to remove.
After the operation, 130.4 MiB will be freed.
Continue? [y/n/v/...? shows all options] (y): n
linux-4skc:~ #
As you can see this package is used e.g. in gimp. I would have thought that other people have the same problem. I used malcolmlewis’ suggestion but suspect this problem will come again.
Hi
So, where did gimp come from, I suspect the graphics repository, again it’s likely active in your repository output?
zypper lr -E
All it’s looking to do is a vendor change, I suspect your output from the following command will show the vendors as the graphics repository;
zypper if gimp | grep Vendor
I use my own local build for claws mail, I see;
zypper if claws-mail | grep Vendor
Vendor : obs://build.opensuse.org/server:mail
Again, even switching won’t be an issue since they are the same release, the major.minor build count just makes it want to update to that one…
Thanks malcolmlewis for the vendor of gimp it just says openSUSE
linux-4skc:~ # zypper lr -E
Repository priorities in effect: (See 'zypper lr -P' for details)
80 (raised priority) : 1 repository
90 (raised priority) : 3 repositories
99 (default priority) : 3 repositories
# | Alias | Name | Enabled | GPG Check | Refresh
---+--------------------------------------+-----------------------------+---------+-----------+--------
1 | http-download.opensuse.org-02d60008 | openSUSE:Factory | Yes | (r ) Yes | Yes
2 | https-download.opensuse.org-4d2b8b7e | home:ecsos | Yes | (r ) Yes | Yes
6 | packman | packman | Yes | (r ) Yes | Yes
8 | repo-non-oss | openSUSE-Tumbleweed-Non-Oss | Yes | (r ) Yes | Yes
9 | repo-oss | openSUSE-Tumbleweed-Oss | Yes | (r ) Yes | Yes
11 | repo-update | openSUSE-Tumbleweed-Update | Yes | (r ) Yes | Yes
12 | skype-stable | skype (stable) | Yes | (r ) Yes | Yes
linux-4skc:~ # zypper if gimp | grep Vendor
Vendor : openSUSE
linux-4skc:~
Hi
So what is that Factory one?
zypper lr -d -E
linux-4skc:~ # zypper lr -d -E
# | Alias | Name | Enabled | GPG Check | Refresh | Priority | Type | URI | Service
---+--------------------------------------+-----------------------------+---------+-----------+---------+----------+--------+--------------------------------------------------------------------------+--------
1 | http-download.opensuse.org-02d60008 | openSUSE:Factory | Yes | (r ) Yes | Yes | 99 | rpm-md | http://download.opensuse.org/repositories/openSUSE:/Factory/snapshot/ |
2 | https-download.opensuse.org-4d2b8b7e | home:ecsos | Yes | (r ) Yes | Yes | 99 | rpm-md | https://download.opensuse.org/repositories/home:/ecsos/openSUSE_Factory/ |
6 | packman | packman | Yes | (r ) Yes | Yes | 80 | rpm-md | http://packman.inode.at/suse/openSUSE_Tumbleweed/ |
8 | repo-non-oss | openSUSE-Tumbleweed-Non-Oss | Yes | (r ) Yes | Yes | 90 | rpm-md | http://download.opensuse.org/tumbleweed/repo/non-oss/ |
9 | repo-oss | openSUSE-Tumbleweed-Oss | Yes | (r ) Yes | Yes | 90 | rpm-md | http://download.opensuse.org/tumbleweed/repo/oss/ |
11 | repo-update | openSUSE-Tumbleweed-Update | Yes | (r ) Yes | Yes | 90 | rpm-md | http://download.opensuse.org/update/tumbleweed/ |
12 | skype-stable | skype (stable) | Yes | (r ) Yes | Yes | 99 | rpm-md | https://repo.skype.com/rpm/stable/ |
linux-4skc:~ #
It seems the Factory URL http://download.opensuse.org/repositories/openSUSE:/Factory/snapshot/ in the browser always changes to http://download.opensuse.org/tumbleweed/repo/oss/
Hi
So it’s coming from the ecos repository https://download.opensuse.org/repositories/home:/ecsos/openSUSE_Factory/x86_64/libraw19-0.19.5-142.21.x86_64.rpm.mirrorlist I suspect with the amount of linked packages that user has it’s a stale binary. This happens if a package is deleted and the binaries are not wiped, the joys of using non standard repos.
Unless the user deletes you will be stuck with the issue, considering Tumbleweed has moved to libraw20, I suggest you peruse Show home:ecsos - openSUSE Build Service and look at most of those packages (372) are just links to development projects that are pushing the packages to Tumbleweed anyway…
I suspect that your gimp version is linked to libraw19 instead of the Tumbleweed version that uses libraw20…
I just recently switched from Herbster0815 to ecsos (at the most 3 weeks ago) because the programme MediathekView from Herbster0815 did not run any more. I removed this programme and the repo and installed it again from the other repo (ecsos). So what would be the best way to approach this? disable this repo and try to move the packages to tumbleweed? How would you do this?
Hi
I would disable the repository and dup again to see if the packages switch to the Tumbleweed repository. Not sure why you have the snapshot one either (or are you using tumbleweed-cli?).
Add verbosity as well;
zypper -vvv dup
You do realize the MediathekView in ecsos is (again) just a link to the Herbster0815 one (which the user fixed a few days ago)?
Look at top right Links to home:Herbster0815 / MediathekView so your move was short lived…?? What you should do is ask the user Herbster0815 to submit to the likes of Multimedia:Apps and submit to Factory (or Packman).
Thanks malcolmlewis, I removed ecsos repos and another zypper dup removed libraw19 and installed a few other packages. I checked before and libraw20 was already installed. The tumbleweed repo came when I installed it and that was several years ago so I presume that were the standard tumbleweed packages. I had the odd questions here but apart from that the tumbleweed OS works very well without major problems and with good advice from the people here. I presume the snapshot repo (with the name Factory) can be removed since it is only the normal tumbleweed repo. I cannot remember where this cam from probably from a “1 click install”.
Hi
Yes, I would remove it 
Now, go ask the MediathekView packager to push it to a development repository Check the changelog for the email address…