Hi,
I’m considering whether to update from Leap 42.2 to Tumbleweed or to Leap 42.3 (and then soon to 15.0). I tend to use several packages from unofficial repositories.
Never having used a rolling release distro, I’m worried that it could be more prone to dependency conflicts than Leap when using additional repos. After all, additional repos are provided separately for each (supported) Leap version for a reason: e.g. a program compiled against 42.2 may not work on 42.3 and vice versa. Similarly, I’d guess that when libraries in the Tumbleweed base system are updated, a package in an unofficial repo that depends on an older version of a library may not work until the maintainer of the repo recompiles it against the newer version. Packages in different additional repos might even depend on different library versions, depending on when they were compiled.
Is this a significant issue in practice? Or are build service repos perhaps automatically recompiled when Tumbleweed changes?
Thanks for clarification.
Depends on the repos in question and what the maintainer is doing to
maintain them.
Since anyone can create a repo using the build service, you’re talking
literally about thousands of potential repositories maintained by
individuals who may or may not be continuing to keep things up to date.
If you stick with packman and the standard repos, you generally should be
find regardless of whether you use Leap or Tumbleweed. If you start
adding in other repos, you need to look specifically at how the repo
owners are managing their repo. For example, I wouldn’t advise using the
repos in my personal home project on the build service, because I
maintain the content there only when it suits me.
Jim
Jim Henderson
openSUSE Forums Administrator
Forum Use Terms & Conditions at http://tinyurl.com/openSUSE-T-C
Thx! Well, I don’t tend to use repos under download.opensuse.org/repositories/home: .In addition to packman, I use a few repos under KDE:, Publishing, a few repos under devel: , etc. These are maintained by various openSUSE teams, not random people, and are well-maintained, aren’t they?
(Also, I sometimes use them to get newer versions of software, which is unnecessary with Tumbleweed, I guess. But I think sometimes they contain packages that are not in the official repos.)
How I did when I install TW: like you, I have some software that is a “must have” for me. I search in openSUSE software these packages. I was lucky, TW had all that I need.
BTW, try TW for few days. After that there will be no way back.
Now I have only TW repos.
I am running into conflicts during updates. These conflicting libs are dependencies for Fotoxx: https://software.opensuse.org/package/fotoxx
I am install now (from multimedia: photo). No conflicts at all. Tw with KDE here.
PS. I suppose that you install TW, zypper dup, after that you try to install fotoxx.
On Tue, 27 Mar 2018 08:16:01 +0000, groszdani wrote:
> Thx! Well, I don’t tend to use repos under
> download.opensuse.org/repositories/home: .In addition to packman, I use
> a few repos under KDE:, Publishing, a few repos under devel: , etc.
> These are maintained by various openSUSE teams, not random people, and
> are well-maintained, aren’t they?
> (Also, I sometimes use them to get newer versions of software, which is
> unnecessary with Tumbleweed, I guess. But I think sometimes they contain
> packages that are not in the official repos.)
They should be, yes.
But if you do run into trouble, feel free to ask here or ping the
maintainer through OBS.
Jim
–
Jim Henderson
openSUSE Forums Administrator
Forum Use Terms & Conditions at http://tinyurl.com/openSUSE-T-C
Best practice for Tumbleweed if you find it’s lacking a/some package(s): ask the maintainer to add it to Tw. That way you can be sure it’s built against the stock libs etc. and definitely will not have any dependency conflicts. In fact you move that problem to the maintainer.
Another solution is to start your own repo ( Yes, we can ), branch the original package and test it. That would at least avoid a conflict with packages in the originating repo.
Thx, trying Tumbleweed then.