[opensuse] Repository changes when upgrade to Leap
I have recently upgraded to Leap. The previous bug that I filed was resolved by one of the download packages I assume. Anyway, it worked:-) Now I am curious what to do with all of the 13.2 repositories that existed before the upgrade. The upgrade appeared to make no attempt to change these to Leap 42.1 equivalents. Is there a recommended procedure for this? Don -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Thu, 4 Feb 2016 17:47:22 -0700 don fisher <hdf3@comcast.net> wrote:
I have recently upgraded to Leap. The previous bug that I filed was resolved by one of the download packages I assume. Anyway, it worked:-) Now I am curious what to do with all of the 13.2 repositories that existed before the upgrade. The upgrade appeared to make no attempt to change these to Leap 42.1 equivalents. Is there a recommended procedure for this?
That doesn't sound right. I upgraded (downgraded?) a 13.2 system to Leap last weekend and I think I remember being asked whether or not to keep the 13.2 repositories. In fact, I think I was able to choose to enable, disable, or remove each individual repository by a toggle...? note: I used the iso/dvd download and the full gui install. Your experience could vary if you used cli zypper. Ralph -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 02/04/2016 06:31 PM, listreader wrote:
On Thu, 4 Feb 2016 17:47:22 -0700 don fisher <hdf3@comcast.net> wrote:
I have recently upgraded to Leap. The previous bug that I filed was resolved by one of the download packages I assume. Anyway, it worked:-) Now I am curious what to do with all of the 13.2 repositories that existed before the upgrade. The upgrade appeared to make no attempt to change these to Leap 42.1 equivalents. Is there a recommended procedure for this?
That doesn't sound right. I upgraded (downgraded?) a 13.2 system to Leap last weekend and I think I remember being asked whether or not to keep the 13.2 repositories. In fact, I think I was able to choose to enable, disable, or remove each individual repository by a toggle...?
note: I used the iso/dvd download and the full gui install. Your experience could vary if you used cli zypper.
Ralph
My problem is that when the system got to the last step, it claimed that it did not recognize my disk and quit. So when I came back, no that the fixes are in place, all the references to 13.2 repos are gone. I still have a 13.2 system running, so have all of the data. I just do not know how to get it to 42.1. I assume that I can add the new repos, but do not know how to associate the installed packages with the new repos. Does this happen with the zypper ref and zypper dup commands already suggested? Don -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Thu, 4 Feb 2016 18:42:24 -0700 don fisher <hdf3@comcast.net> wrote:
My problem is that when the system got to the last step, it claimed that it did not recognize my disk and quit. So when I came back, no that the fixes are in place, all the references to 13.2 repos are gone. I still have a 13.2 system running, so have all of the data. I just do not know how to get it to 42.1. I assume that I can add the new repos, but do not know how to associate the installed packages with the new repos. Does this happen with the zypper ref and zypper dup commands already suggested?
I missed your earlier thread of messages so I don't know your situation and certainly don't want to make it any worse... Was your first attempt at upgrading to Leap, the one that failed, using the iso/dvd gui or was it using cli zypper? And then you tried to repair it through cli zypper? But your system is still now identifying as 13.2? And you have neither 13.2 nor Leap repositories defined? Assuming you were first using iso/dvd, and assuming your data is safely secured / backed up, and assuming you now have available whatever "fix" you say you now have in place - a lot of assumptions there! - why did you not just try the iso/dvd gui upgrade path all over again from the beginning? Ralph -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2016-02-05 04:28, listreader wrote:
On Thu, 4 Feb 2016 18:42:24 -0700 don fisher <> wrote:
I missed your earlier thread of messages so I don't know your situation and certainly don't want to make it any worse...
Yes, some clarification is needed.
Was your first attempt at upgrading to Leap, the one that failed, using the iso/dvd gui or was it using cli zypper? And then you tried to repair it through cli zypper? But your system is still now identifying as 13.2?
And where? Because if it is at boot, it is has no signification. That particular string is not updated. Instead, we have to look at "/etc/os-release".
And you have neither 13.2 nor Leap repositories defined?
Assuming you were first using iso/dvd, and assuming your data is safely secured / backed up, and assuming you now have available whatever "fix" you say you now have in place - a lot of assumptions there! - why did you not just try the iso/dvd gui upgrade path all over again from the beginning?
-- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
On 02/04/2016 08:28 PM, listreader wrote:
On Thu, 4 Feb 2016 18:42:24 -0700 don fisher <hdf3@comcast.net> wrote:
My problem is that when the system got to the last step, it claimed that it did not recognize my disk and quit. So when I came back, no that the fixes are in place, all the references to 13.2 repos are gone. I still have a 13.2 system running, so have all of the data. I just do not know how to get it to 42.1. I assume that I can add the new repos, but do not know how to associate the installed packages with the new repos. Does this happen with the zypper ref and zypper dup commands already suggested?
I missed your earlier thread of messages so I don't know your situation and certainly don't want to make it any worse...
Was your first attempt at upgrading to Leap, the one that failed, using the iso/dvd gui or was it using cli zypper? And then you tried to repair it through cli zypper? But your system is still now identifying as 13.2? And you have neither 13.2 nor Leap repositories defined?
Assuming you were first using iso/dvd, and assuming your data is safely secured / backed up, and assuming you now have available whatever "fix" you say you now have in place - a lot of assumptions there! - why did you not just try the iso/dvd gui upgrade path all over again from the beginning?
Ralph
My first attempt was using the DVD, and it failed on the last step. Following message was displayed: Internal error: Please report a bug report with logs Detail unknown udev device /dev/disk/by-id/wwnQx5002538844584d30-part2 Call: /usr/share/YaST2/lib/bootloader/udev_mapping.rb:42in to kernel device I filed a bug report 949796 and the situation has been resolved buy the openSuse team. But the first attempt removed the 13.2 system, so when I ran it again there was no reference to the 13.2 repos. How do you generate a "safely secured / backed up"? I do have one because I make a mirror image on a bootable USB drive. Is there another way? Don -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2016-02-05 18:34, don fisher wrote:
On 02/04/2016 08:28 PM, listreader wrote:
My first attempt was using the DVD, and it failed on the last step. Following message was displayed:
Internal error: Please report a bug report with logs Detail unknown udev device /dev/disk/by-id/wwnQx5002538844584d30-part2 Call: /usr/share/YaST2/lib/bootloader/udev_mapping.rb:42in to kernel device
I filed a bug report 949796 and the situation has been resolved buy the openSuse team. But the first attempt removed the 13.2 system, so when I ran it again there was no reference to the 13.2 repos.
But that bugzilla (which was made last October) is about tumbleweed. I see no mention on it that you were attempting to upgrade a 13.2 system using the DVD. What you report there is "Trying to modify the bootloader setup, YaST2-Bootloader complains", and later I see mentions to «routine "zypper dup"». What is described in the bugzilla doesn't match what you say here. You say here:
But the first attempt removed the 13.2 system, so when I ran it again there was no reference to the 13.2 repos.
If 13.2 was removed on the first attempt, what you have to try is a clean install. Of course there can't be any reference to 13.2 repos. All was destroyed, you say. I'm now very confused about what you are doing and what is your real problem.
How do you generate a "safely secured / backed up"? I do have one because I make a mirror image on a bootable USB drive. Is there another way?
A mirror image is probably the best type of backup. So, you can restore the complete original system and try again the upgrade. Or install fresh, new, and restore only the data you want to restore. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
On 02/05/2016 01:14 PM, Carlos E. R. wrote:
On 2016-02-05 18:34, don fisher wrote:
On 02/04/2016 08:28 PM, listreader wrote:
My first attempt was using the DVD, and it failed on the last step. Following message was displayed:
Internal error: Please report a bug report with logs Detail unknown udev device /dev/disk/by-id/wwnQx5002538844584d30-part2 Call: /usr/share/YaST2/lib/bootloader/udev_mapping.rb:42in to kernel device
I filed a bug report 949796 and the situation has been resolved buy the openSuse team. But the first attempt removed the 13.2 system, so when I ran it again there was no reference to the 13.2 repos.
But that bugzilla (which was made last October) is about tumbleweed. I see no mention on it that you were attempting to upgrade a 13.2 system using the DVD. What you report there is "Trying to modify the bootloader setup, YaST2-Bootloader complains", and later I see mentions to «routine "zypper dup"». What is described in the bugzilla doesn't match what you say here.
You say here:
But the first attempt removed the 13.2 system, so when I ran it again there was no reference to the 13.2 repos.
If 13.2 was removed on the first attempt, what you have to try is a clean install. Of course there can't be any reference to 13.2 repos. All was destroyed, you say.
I'm now very confused about what you are doing and what is your real problem.
How do you generate a "safely secured / backed up"? I do have one because I make a mirror image on a bootable USB drive. Is there another way?
A mirror image is probably the best type of backup. So, you can restore the complete original system and try again the upgrade. Or install fresh, new, and restore only the data you want to restore.
I made an error. My bug was 963247, which the "team?" decided was a duplicate of 949796. I do not understand the wwn mapping, so cannot dispute the claim. I just thought that the install should not fail, and wanted to report it. I am trying to run Leap 42.1 on a Samsung SSD. I have been running 13.2 from that drive for about a year. My graphics card is not well supported by the kernels in the 13.2 chain, so I really wanted to upgrade. My problem is that I cannot get Leap to run from the SSD, which is really fast:-) Since 13.2 ran without incident, I was surprised that booting was broken by Leap. The status of the wwn mapping problem reported by bugzilla 949796 is still "in progress", which I assume means not resolved. So a repeat of what I have done will probably not yield different results, unless you have any suggestions. The return email I received from Josef Reidinger suggested that I change the default mount to UUID. But he did not respond when I asked how one accomplishes this. I am currently building a leap 42.1 on a magnetic disk. I will see how that proceeds. Don -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
The return email I received from Josef Reidinger suggested that I change the default mount to UUID. But he did not respond when I asked how one accomplishes this. The easiest way is by yast2 partitioner, which you can use under "expert
On 05/02/2016 23:30, don fisher wrote: partioner" (not quite sure of the wording) during the early Leap:42.1 install stage. Right click to edit the partition and under "fstab options" you'll see the five mount options : "Device name", "Device ID", "Volume label", "Device Path" and "UUID" Not sure how changing your 13.2 partitions to UUID will affect your system, I jumped to Leap from 12.1 so maybe you should use 13.2 yast to set all your partitions to UUID before attempting the Leap install. UUID makes fstab very difficult to read. "Device name" aka /dev/sdxx can confuse the installation system when there are other linux systems on the same computer as it isn't unique. Regards Dave P -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2016-02-05 22:30, don fisher wrote:
On 02/05/2016 01:14 PM, Carlos E. R. wrote:
I made an error. My bug was 963247, which the "team?" decided was a duplicate of 949796.
Yes, I noticed that hours later.
I do not understand the wwn mapping, so cannot dispute the claim. I just thought that the install should not fail, and wanted to report it.
"wwn" is just one type of "by-id" mapping. Others are ata, scsi, and some other.
The status of the wwn mapping problem reported by bugzilla 949796 is still "in progress", which I assume means not resolved. So a repeat of what I have done will probably not yield different results, unless you have any suggestions. The return email I received from Josef Reidinger suggested that I change the default mount to UUID. But he did not respond when I asked how one accomplishes this.
On the installer, expert partitioner section, look at the left panel. At the bottom there is an entry labelled "settings". Click there. Change the "mount by" settings. This applies to new partitions. Then go to the "hard disk" section. Click on the disk. Edit all the existing partitions. Click on the "fstab options" button, and make sure the correct "mount by" is active, if not change it. One by one. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
On 02/06/2016 06:25 AM, Carlos E. R. wrote:
On 2016-02-05 22:30, don fisher wrote:
On 02/05/2016 01:14 PM, Carlos E. R. wrote:
I made an error. My bug was 963247, which the "team?" decided was a duplicate of 949796.
Yes, I noticed that hours later.
I do not understand the wwn mapping, so cannot dispute the claim. I just thought that the install should not fail, and wanted to report it.
"wwn" is just one type of "by-id" mapping. Others are ata, scsi, and some other.
The status of the wwn mapping problem reported by bugzilla 949796 is still "in progress", which I assume means not resolved. So a repeat of what I have done will probably not yield different results, unless you have any suggestions. The return email I received from Josef Reidinger suggested that I change the default mount to UUID. But he did not respond when I asked how one accomplishes this.
On the installer, expert partitioner section, look at the left panel. At the bottom there is an entry labelled "settings". Click there. Change the "mount by" settings. This applies to new partitions.
Then go to the "hard disk" section. Click on the disk. Edit all the existing partitions. Click on the "fstab options" button, and make sure the correct "mount by" is active, if not change it. One by one.
Thanks. I did the left panel settings options you suggested. I did not change the individual fstab option. I was surprised that it worked for swap and home and not root. Lots of lessons to learn. Where do the mount by options appear, except in fstab and grub? If I want to change my swap and back to UUID, is it as simple as editing the fstab file? Don -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
don fisher composed on 2016-02-06 11:43 (UTC-0700):
If I want to change my swap and back to UUID, is it as simple as editing the fstab file?
It can be. FWIW, this is the / entry in fstab from this 42.1 installation, as created by YaST at installation (minus superfluous space characters): LABEL=1md12root4 / ext4 noatime,acl 1 1 -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2016-02-06 19:43, don fisher wrote:
On 02/06/2016 06:25 AM, Carlos E. R. wrote:
Thanks. I did the left panel settings options you suggested. I did not change the individual fstab option.
You should.
I was surprised that it worked for swap and home and not root.
That's why I told you to review the individual entries. I noticed that Leap partitioner doesn't seem to respect fully the global setting.
Lots of lessons to learn. Where do the mount by options appear, except in fstab and grub?
Only there.
If I want to change my swap and back to UUID, is it as simple as editing the fstab file?
Yes. And grub. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
On 2016-02-05 01:47, don fisher wrote:
I have recently upgraded to Leap. The previous bug that I filed was resolved by one of the download packages I assume. Anyway, it worked:-) Now I am curious what to do with all of the 13.2 repositories that existed before the upgrade. The upgrade appeared to make no attempt to change these to Leap 42.1 equivalents. Is there a recommended procedure for this?
There is no automatic procedure. You have to decide yourself, as the administrator, what to do with each one. One by one :-) Really, the decision is your own. For myself, I reactivate packman (just edit the path, the version), and then those for packages that are not available in oss. First I search to find out which repos have it before deciding to use the same repo or another. Those repositories that are used to get more recent versions of packages, I evaluate and decide case by case whether to update them or not. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
participants (5)
-
Carlos E. R. -
Dave Plater -
don fisher -
Felix Miata -
listreader