toughts on migrating from tumbleweed to "official" 13.2

I noticed some unstablility in tumbleweed (even though not “HW” = drivers problem), but I’m havin problem with rails, DNS in chromium, from time to time with booting ( I’ve to recreate grub, mkinitrd) which I’ve not encountered on 13.2. And I want real stable development enviroment. So is it good tought to "migrate from tumbleweed to 13.2 or what are the recomeded steps - adding repos, zypper dup …?

I made the same step at the end of January. I did it via new installation of 13.2.
I have the separated /home directory so it was not problem.
I am satisfied so far.

IMO

  • Tumbleweed repos might be contributing to instability but maybe not on your system. From what you’ve posted nothing is possible but speculation. Still, TW is intended to be used by those who like living a bit more on the edge, not those seeking rock hard stability. If you’re building a Dev platform, I personally wouldn’t select TW, but you need to be more specific what your issues are or better at surrounding and identifying specific issues instead of describing issues in a very general sense.

  • You mentioned “rails.” If you are referring to Ruby on Rails, you might consider building your platform based on the Ruby repos instead of entirely on the OSS repos. Although I’ve mentioned building a ruby Dev environment on openSUSE in the past, I’m close to posting a new updated procedure which isn’t too different shortly. For now, you’ll find it in a deprecated section installing an old version of some software I describe
    https://en.opensuse.org/User:Tsu2/Kibana#Install_Overview_.28This_applies_only_to_kibana_2.x_and_earlier_for_archival_purposes.29

  • As for things like “DNS in Chromium” - well, AFAIK there’s really no such thing as that. DNS resolution is system functionality and not typically a Browser function although bad attempts at resolution can be stored in a browser cache. And, without some detail, I don’t think anyone can speculate on your booting issues which may or may not be due to using TW instead of the standard version of openSUSE.

TSU

this is my problem with chromium

dns_probe_finished_nxdomain

and it appears ~ 2times a day so it’s anoying, I need to

pkill -f chromium

and then it works, though I’ve no problem with DNS on the “system side” - zypper, gem install and also firefox they’re working just fine. And today mornin I noticed this problem also on 13.2 so it seems to be chromium problem

Whenever you describe a problem with an app like Chromium,

  • You need to describe where you installed the app from (likely the TW repos)
  • The version (one simple way to obtain the version for any app is by opening the Menu option Help > About…)
  • If the problem is reproducible, you should submit a bug to https://bugzilla.opensuse.org. Use the same login credentials you used for these Forums. Include your steps to re-produce and anything you might have tried to research or attempt to fix the problem.

TSU

FYI
I just announced a new Guide on my wiki for installing a Ruby Dev environment

https://forums.opensuse.org/showthread.php/507926-Installing-Ruby-on-openSUSE

You may still want to re-deploy as a normal 13.2 instead of TW, the general approach to a Dev platform is that you’ll be introducing so much uncertainty during your building, it’s practical and prudent to minimize potential issues by starting with as stable a platform as possible. So, unless TW is providing some real benefit, it’s not recommended.

But, if you want to live very much on the edge of instability there are poorer choices than TW.

Note that my Guide describes how to install the TW Ruby repo, and you can decide to install latest Ruby from the Ruby repos as well (AFAIK openSUSE only offers 2.1.5 as latest while 2.2.2 is available from the Ruby repos).

TSU

Actually even for a Dev machine having up to date software-stacks is quite desirable imo. You seem to develop using Ruby and I do not know how much hassle it is to be up to date with just the Ruby stack, but I feel that the same with C++ is quite a hassle. For me having the latest C++ standard features available really matters. The same goes for up to date Boost libs etc…

From this perspective I would rather argue in favor of using TW for development machines…