[opensuse-factory] RC1 -> RC2 failed because of systemd
All, Before we go Gold, can the zypper dup process be updated to warn users of the possibility of needing to add init=/sbin/sysvinit to menu.lst before allowing them to proceed? I'm just talking about a simple test message that pops up somehow. I know the zypper package itself is not the way to do this because users will still be running zypper from 11.4 most likely. Is their a text file, or license file trick we could play to force a warning to the user? If not, is there a way to rush out a 11.4 update to zypper that would have it check the update repo and if its 12.1, give a warning? == my story I have a desktop machine that I upgraded a week or two ago from Tumbleweed to RC1. That went reasonably smooth. I "think" I was running systemd after that upgrade. I did NOT have a init= statement in /boot/grub/menu.lst, and I think the RC1 default was systemd. I just upgraded to RC2 via zypper up. (Note the repo was already set and I had already re-enabled a number of devel repos, so I didn't feel the need to use zypper dup.) Anyway, after the upgrade I rebooted immediately and ended up in Emergency Mode. Fortunately I knew to add init=/sbin/sysvinit. I know that will be in the release notes, but that just doesn't seem like enough of a safeguard. I don't think many of the "zypper dup" upgraders will read the release notes. Greg -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 11/04/2011 06:10 PM, Greg Freemyer wrote:
All,
Before we go Gold, can the zypper dup process be updated to warn users of the possibility of needing to add init=/sbin/sysvinit to menu.lst before allowing them to proceed?
I'm just talking about a simple test message that pops up somehow.
I know the zypper package itself is not the way to do this because users will still be running zypper from 11.4 most likely.
Is their a text file, or license file trick we could play to force a warning to the user?
If not, is there a way to rush out a 11.4 update to zypper that would have it check the update repo and if its 12.1, give a warning?
== my story
I have a desktop machine that I upgraded a week or two ago from Tumbleweed to RC1. That went reasonably smooth.
I "think" I was running systemd after that upgrade. I did NOT have a init= statement in /boot/grub/menu.lst, and I think the RC1 default was systemd.
I just upgraded to RC2 via zypper up. (Note the repo was already set and I had already re-enabled a number of devel repos, so I didn't feel the need to use zypper dup.)
Anyway, after the upgrade I rebooted immediately and ended up in Emergency Mode. Fortunately I knew to add init=/sbin/sysvinit.
I know that will be in the release notes, but that just doesn't seem like enough of a safeguard. I don't think many of the "zypper dup" upgraders will read the release notes.
When you did a "zypper up", you took away tha ability for zypper to downgrade packages and to change vendors. In my "zypper dup" upgrade from RC1 to RC2, a number of each occurred. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Fri, Nov 4, 2011 at 8:19 PM, Larry Finger <Larry.Finger@lwfinger.net> wrote:
On 11/04/2011 06:10 PM, Greg Freemyer wrote:
All,
Before we go Gold, can the zypper dup process be updated to warn users of the possibility of needing to add init=/sbin/sysvinit to menu.lst before allowing them to proceed?
I'm just talking about a simple test message that pops up somehow.
I know the zypper package itself is not the way to do this because users will still be running zypper from 11.4 most likely.
Is their a text file, or license file trick we could play to force a warning to the user?
If not, is there a way to rush out a 11.4 update to zypper that would have it check the update repo and if its 12.1, give a warning?
== my story
I have a desktop machine that I upgraded a week or two ago from Tumbleweed to RC1. That went reasonably smooth.
I "think" I was running systemd after that upgrade. I did NOT have a init= statement in /boot/grub/menu.lst, and I think the RC1 default was systemd.
I just upgraded to RC2 via zypper up. (Note the repo was already set and I had already re-enabled a number of devel repos, so I didn't feel the need to use zypper dup.)
Anyway, after the upgrade I rebooted immediately and ended up in Emergency Mode. Fortunately I knew to add init=/sbin/sysvinit.
I know that will be in the release notes, but that just doesn't seem like enough of a safeguard. I don't think many of the "zypper dup" upgraders will read the release notes.
When you did a "zypper up", you took away tha ability for zypper to downgrade packages and to change vendors. In my "zypper dup" upgrade from RC1 to RC2, a number of each occurred.
I'm, away from the computer until Monday. I'll try to - disable everything but the 12.1 OSS - remove the init= statement from menu.lst - zypper dup - reboot I don't have your confidence. Since I had recently upgraded to -RC1, almost all of my packages were already the same repo as -RC2. In fact about 2400 packages were upgraded by zypper up. Greg -- Greg Freemyer Head of EDD Tape Extraction and Processing team Litigation Triage Solutions Specialist http://www.linkedin.com/in/gregfreemyer CNN/TruTV Aired Forensic Imaging Demo - http://insession.blogs.cnn.com/2010/03/23/how-computer-evidence-gets-retriev... The Norcross Group The Intersection of Evidence & Technology http://www.norcrossgroup.com -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 11/05/2011 06:38 PM, Greg Freemyer wrote:
I'm, away from the computer until Monday. I'll try to
- disable everything but the 12.1 OSS - remove the init= statement from menu.lst - zypper dup - reboot
I don't have your confidence. Since I had recently upgraded to -RC1, almost all of my packages were already the same repo as -RC2. In fact about 2400 packages were upgraded by zypper up.
I did a 'zypper up' first and got ~2700 packages. When I repeated 'zypper up', I got a list of packages that would not be upgraded. With 'zypper dup', I got another ~80 packages, that were mostly downgrades and vendor changes. After that competed, 'zypper up' was clean. Larry -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Sat, Nov 5, 2011 at 9:58 PM, Larry Finger <Larry.Finger@lwfinger.net> wrote:
On 11/05/2011 06:38 PM, Greg Freemyer wrote:
I'm, away from the computer until Monday. I'll try to
- disable everything but the 12.1 OSS - remove the init= statement from menu.lst - zypper dup - reboot
I don't have your confidence. Since I had recently upgraded to -RC1, almost all of my packages were already the same repo as -RC2. In fact about 2400 packages were upgraded by zypper up.
I did a 'zypper up' first and got ~2700 packages. When I repeated 'zypper up', I got a list of packages that would not be upgraded. With 'zypper dup', I got another ~80 packages, that were mostly downgrades and vendor changes. After that competed, 'zypper up' was clean.
Larry
Larry, You may have been right, or it may have been a repo transition issue. Anyway, systemd now seems to be working on my machine. == details When I did the zypper dup, I had about 100 packages removed which really surprised me. Other than that the biggest thing is I got a new kernel. I don't if a kernel issue may have caused my earlier issues or not. Greg -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (2)
-
Greg Freemyer -
Larry Finger