On Wed, Oct 21, 2015 at 3:42 PM, Carlos E. R. <robin.listas@telefonica.net> wrote:

On 2015-10-21 15:38, Roger Oberholtzer wrote:

...

I see that there are repos for Leap/42.1-Beta1 as well as Leap/42.1-RC1 and Leap/42.1-Current. I installed Leap/42.1-Beta1. If I want to track the state of Leap without doing a re-install, would it make sense to change my repos to Leap/42.1-RC1? And then Leap/42.1-RC2 when it is available, and so on? How are others doing this?

I have this:

Eleanor-421:~ # zypper lr --details # | Alias | Name | Enabled | GPG Check | Refresh | Priority | Type | URI | Service --+-----------------+-----------------------+---------+-----------+---------+----------+--------+----------------------------------------------------------------------------------------+-------- 1 | openSUSE-42.1-0 | openSUSE-42.1-0 | No | ---- | No | 99 | yast2 | cd:///?devices=/dev/disk/by-id/ata-VMware_Virtual_IDE_CDROM_Drive_10000000000000000001 | 2 | repo-debug | openSUSE-Leap-Debug | No | ---- | Yes | 99 | NONE | http://download.opensuse.org/debug/distribution/leap/42.1/repo/oss/ | 3 | repo-non-oss | openSUSE-Leap-Non-Oss | Yes | (r ) Yes | Yes | 99 | yast2 | http://download.opensuse.org/distribution/leap/42.1/repo/non-oss/ | 4 | repo-oss | openSUSE-Leap-Oss | Yes | (r ) Yes | Yes | 99 | yast2 | http://download.opensuse.org/distribution/leap/42.1-Current/repo/oss/ | 5 | repo-source | openSUSE-Leap-Source | No | ---- | Yes | 99 | NONE | http://download.opensuse.org/source/distribution/leap/42.1/repo/oss/ | 6 | repo-update | openSUSE-Leap-Update | Yes | (r ) Yes | Yes | 99 | rpm-md | http://download.opensuse.org/update/42.1/ | Eleanor-421:~ # cat /etc/os-release NAME="openSUSE Leap" VERSION="42.1" VERSION_ID="42.1" PRETTY_NAME="openSUSE Leap 42.1 (x86_64)" ID=opensuse ANSI_COLOR="0;32" CPE_NAME="cpe:/o:opensuse:opensuse:42.1" BUG_REPORT_URL="https://bugs.opensuse.org" HOME_URL="https://opensuse.org/" ID_LIKE="suse" Eleanor-421:~ #

I think I have RC1.

I installed Beta1. My repos are listed the same as yours. But there is not really a leap/42.1 directory. So it must be looking at one of the three that really exist: http://download.opensuse.org/distribution/leap/42.1-Beta1/ http://download.opensuse.org/distribution/leap/42.1-RC1/ http://download.opensuse.org/distribution/leap/42.1-Current/ If I want to add a package, and it exists in leap/42.1-RC1 but not leap/42.1-Beta1, it is not seen. I do not want to just add RC1 packages. Unless I move my system to RC1. But as the repos do not actually list RC1 (as you demonstrated), I am uncertain how to proceed without really destroying my system. I see that you do have on repo set to leap/42.1-Current, but no others. You like to live dangerously! -- Roger Oberholtzer -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On Wed, Oct 21, 2015 at 4:44 PM, Carlos E. R. <robin.listas@telefonica.net> wrote:

I have just zypper duped all the way here.

I tried a dup of the Beta1 install, leaving the repos as the Beta1 install defined them. It did pull in many updates. But is also borked my system. The update failed at some point, and I had no choice but to force a reboot. Never a good thing. I had to reinstall the Beta. I am trying to decide if I want to do that again... -- Roger Oberholtzer -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On Wed, Oct 21, 2015 at 5:41 PM, Carlos E. R. <robin.listas@telefonica.net> wrote:

Be sure to stop apparmor before running an update, it can crash the kernel, in the middle of the updates. It happened to me with quite horrible results, but I was able to reconstruct it.

I read that after my first attempt. I usually do not install/run apparmor. But it may have snuck in on my first Leap install. I have just updated the system and am just going to reboot to see what happens. But at least the update completed this time. -- Roger Oberholtzer -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org