Fwd: [opensuse-factory] Instructions for Tumbleweed & Factory Users*All should read*

English Install/Boot/Login
1

You should all read this (4 “Forwarded Messages”)

Further comments and questions, on the factory mail list, as the decisions are made and commented there. Here they just percolate.

I’m just acting as percolator :wink:

Saludos,

carlos.e.r arroba opensuse.org

-------- Forwarded Message --------
Subject: [opensuse-factory] Instructions for Tumbleweed & Factory Users All should read
Date: Tue, 04 Nov 2014 10:45:19 +0100
From: Richard Brown <...@suse.de>
To: opensuse-factory@opensuse.org

Hi All,

It’s openSUSE 13.2 release day, apologies for posting this a little
later than intended, but here are the instructions for Tumblweed and
Factory users to move to the ‘new’ merged Tumbleweed

Tumbleweed users must follow these instructions as soon as possible to
continue to get rolling updates.

Factory users need to do this within the next 6 months, by which time
the old Factory repositories will be removed. We will be sending out
reminders as that deadline approaches, but you can do it now.

Remove your existing system repositories

mkdir /etc/zypp/repos.d/old

mv /etc/zypp/repos.d/*.repo /etc/zypp/repos.d/old

Then add the new repositories for Tumbleweed

zypper ar -f -c http://download.opensuse.org/tumbleweed/repo/oss repo-oss

zypper ar -f -c http://download.opensuse.org/tumbleweed/repo/non-oss repo-non-oss

zypper ar -f -c http://download.opensuse.org/tumbleweed/repo/debug repo-debug

Then zypper dup to new Tumbleweed

zypper dup

REGARDING ADDITIONAL REPOSITORIES:
The above instructions will remove ALL additional repositories you have
configured.
You will need to re-add those you need but please consider the below.

Users who are using additional ‘openSUSE_Tumbleweed’ repositories from
OBS are recommended to either stop using those repositories or wait a
few days to ensure the build service has had time sync up and has the
packages built for ‘new’ Tumbleweed. We’ll be posting updates here once
we have them.

Users who are using additional ‘openSUSE_Factory’ repositories should be
fine, besides the obvious ‘name mismatch’ which is obviously cosmetic,
but will get your packages on your machine while we get OBS to reflect
the merger.

–

Richard Brown
QA Engineer
openSUSE Chairman

Phone +4991174053-361
SUSE LINUX GmbH, Maxfeldstr. 5, D-90409 Nuernberg
GF: Jeff Hawn, Jennifer Guild, Felix Imendoerffer, HRB 21284 (AG Nuernberg)

–
To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org
To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

-------- Forwarded Message --------
Subject: Re: [opensuse-factory] Instructions for Tumbleweed & Factory Users All should read
Date: Tue, 4 Nov 2014 12:19:53 +0100
From: Richard Brown <...@opensuse.org>
To: Todd Rme <...@gmail.com>
CC: opensuse-factory <opensuse-factory@opensuse.org>

On 4 November 2014 11:05, Todd Rme <> wrote:
>
> Great!
>
> A few questions:
>
> What is the story with the Tumbleweed “updates” repo that was
> discussed in the earlier thread? Is that not going to happen at all,
> or is it happening later, or has a decision not been made? I am not
> even sure what would go in there if Tumbleweed is a rolling release.

I think it will happen, but it is not happening as part of this merger.
It will be for updates for specific things, to address urgent security
issues (eg. Shellshock), where we need to get updates out to users of
Tumbleweed faster than the Factory development process would otherwise
allow.

> I am still unclear about OBS project configuration. In the OBS “Add
> Repositories to __” page, it lists “openSUSE Factory” and “openSUSE
> Tumbleweed”. Are these the same, or does “openSUSE Factory” pointing
> to the “testing” project that should only be used by devel projects?

I understand the confusion, I think it’s best if I explain a bit of
background subtlety that might not be obvious to many.

OBS has support for different ‘repositories’ attached to a Project.

openSUSE:Factory has several, 2 of which are relevant to this
discussion, standard and snapshot

<repository name=“openSUSE_Factory”>
<path project=“openSUSE:Factory” repository=“standard”/>
<arch>i586</arch>
<arch>x86_64</arch>
</repository>

<repository name=“openSUSE_Factory”>
<path project=“openSUSE:Factory” repository=“snapshot”/>
<arch>i586</arch>
<arch>x86_64</arch>
</repository>

‘standard’ is the repository which is used by openQA for testing, so
it’s effectively ‘the version of factory currently being tested by
openQA’.

‘snapshot’ is the repository which contains the latest, passed,
released snapshot from Factory. This is what we now call Tumbleweed

By the end of today (I’m working on it right now), openSUSE_Tumbleweed
in OBS will match openSUSE:Factory snapshot - they’ll be the same
thing, identical in every way besides the name

> If they are the same, what target should devel projects use to build
> against the “testing” version of Factory, and what should it be
> called? If devel projects does not already have this target, should
> it be added? Should publishing of this repository be enabled or
> disabled?

My advice would be the following:

Devel Project Maintainers should build against openSUSE Factory
standard or openSUSE Factory snapshot depending on how they want to
work.
Some projects might prefer building against standard, build against
‘what is coming’ in Factory, but that potentially can make it harder
to test manually. Other projects might prefer building against
snapshot, ‘what is released’ in Factory snapshot/Tumbleweed, which
makes it easier for them to test, but potentially can cause issues if
Factory has something on the way that interacts with their packages.
It’s really down to the Devel Project maintainer, and that difference
between standard and snapshot isn’t new and today’s changes don’t
change anything in that regard (ie. if you’re a Devel Project
maintainer and this hasn’t bothered you before, it shouldn’t bother
you today)

However, Devel Projects are easy - they exist in order to funnel
packages to Factory, they’re meant to be used by
developers/contributors… people who won’t mind having repositories
named ‘Factory’ on their Tumbleweed installation - ie. ‘not users’

However, if you’re a maintainer of an OBS Project that targets users,
I’d recommend the following

ONCE I post here announcing the openSUSE Tumbleweed Project in OBS is
ready, then build your project against openSUSE_Tumbleweed and not
openSUSE Factory standard or snapshot

That way, your OBS Project will be clearly obvious that it’s intended
for the users of the Tumbleweed rolling release, and the repository
URL will have ‘Tumbleweed’ in the name, not Factory.

>
> And when you say “devel project”, is this any project that has
> packages that are marked as devel packages for Factory?

I mean a Devel Project, a project that exists to funnel packages into
Factory, as described on our wiki:
https://en.opensuse.org/openSUSE:Factory_development_model

To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org
To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

-------- Forwarded Message --------
Subject: Re: [opensuse-factory] Instructions for Tumbleweed & Factory Users All should read
Date: Tue, 04 Nov 2014 13:42:21 +0100
From: Stephan Kulow <...@suse.de>
To: opensuse-factory@opensuse.org

On 04.11.2014 12:19, Richard Brown wrote:
> On 4 November 2014 11:05, Todd Rme <> wrote:
>
> ‘standard’ is the repository which is used by openQA for testing, so
> it’s effectively ‘the version of factory currently being tested by
> openQA’.
>
> ‘snapshot’ is the repository which contains the latest, passed,
> released snapshot from Factory. This is what we now call Tumbleweed
>
No, ‘snapshot’ is just a random snapshot of standard. It has nothing to
do with the published repo.

Greetings, Stephan

–
To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org
To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

-------- Forwarded Message --------
Subject: Re: [opensuse-factory] Instructions for Tumbleweed & Factory Users All should read
Date: Tue, 04 Nov 2014 13:50:25 +0100
From: Stephan Kulow <...@suse.de>
To: İsmail Dönmez <...@suse.de>
CC: opensuse-factory@opensuse.org

On 04.11.2014 13:44, İsmail Dönmez wrote:
> On 04 Nov 13:42, Stephan Kulow wrote:
>> On 04.11.2014 12:19, Richard Brown wrote:
>>> On 4 November 2014 11:05, Todd Rme <> wrote:
>>>
>>> ‘standard’ is the repository which is used by openQA for
>>> testing, so it’s effectively ‘the version of factory currently
>>> being tested by openQA’.
>>>
>>> ‘snapshot’ is the repository which contains the latest, passed,
>>> released snapshot from Factory. This is what we now call
>>> Tumbleweed
>>>
>> No, ‘snapshot’ is just a random snapshot of standard. It has
>> nothing to do with the published repo.
>
> What repo should we use to build against the rolling release then?
>
The release coming from Factory called Tumbleweed? How about
openSUSE_Factory_Releases_Tumbleweed?

Greetings, Stephan

–
To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org
To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

2

Thank You Carlos!

As I have been updating Factory for a very long time, I think I will do a clean install using:

http://download.opensuse.org/tumbleweed/iso/

and sym link to my 13.2 /home --and then use the urls from the guide Later, I will do the same with Factory.

That will give me three 13.2 /roots on my new SDD and /home on my 10K-rpm Barracuda HDD – nice!

That is unless you Pro’s give me some reason not to.

3

On 2014-11-04 14:56, snakedriver wrote:

>and sym link to my 13.2 /home
…
> That will give me three 13.2 /roots on my new SDD and /home on my
> 10K-rpm Barracuda HDD – nice!

I don’t think you should share the same home folders across several
releases. The most recent one could do changes that are not understood
by the older one.

–
Cheers / Saludos,

Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)

4

You need separate homes if you share between versions. What I do is install the newest in its own root partition and NOT mount home. Once I have tested and satisfied I rename the home that was created in root partition and mount my real home. For the most part the problem is Desktop settings But other apps may have problems with configs accross version. In general more so when going back since a new version m,ay introduce new config options that the older version does not understand

Never saw the point in using multiply versions of the same OS unless you need to test accross multiple versions for deportment of apps. But In that case VM’s seem to be a better way.

5

When I put a different release/version on the same computer, I mount my home partition as “/xhome”. Then I add symlinks to it from my home directory. My home directory, for the alternate version, is part of the root file system.

That allows me to have separate configurations for the different versions, but keep other user data in common.

6

Many Thanks all; knew I should ask before I messed up! Appreciate the various solutions.

Questions for nrickert:

  1. I see you used “symlinks” (plural). so, are you symlinking individual folders (like mail) within /xhome to say individual folders within /tweedhome; or. is that a single symlink /xhome ln /tweedhome.

  2. “symlinks to it from my home directory” so. that would be from /tweedhome back to /xhome? Does it make a difference?

please list a few examples of what works for you.

Thanks

7

I do something similar to the following. Note that I am in my home directory when I do this. I normally use “csh” as shell, but I’ll use bash syntax below since most folk use that. The "% " is my shell prompt.


% rmdir bin   ## because the install creates an empty bin directory.
% for i in bin lib .profile .bashrc .ssh .gnupg Mail PRIVATE
    do
         ln -s ../../xhome/$USER/$i .
    done

Here “PRIVATE” is just a directory that I use a lot (has latex documents). I don’t link “.mozilla” because the two versions might have different firefox versions. And I don’t link “.kde4”.

That gives me my standard shell scripts, mail, ssh settings, gpg settings. I have other directories that I don’t use as much, so I haven’t bothered with those. My multimedia stuff, such as music, is on a completely different partition which I mount in all versions and also share with Windows via samba.

8

Neat! Thanks for the lessons everyone!