[Bug 238679] New: yast2-bootloader is needed by yast2-installation in installed system
https://bugzilla.novell.com/show_bug.cgi?id=238679 Summary: yast2-bootloader is needed by yast2-installation in installed system Product: openSUSE 10.3 Version: unspecified Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: yast2-maintainers@suse.de ReportedBy: aj@novell.com QAContact: jsrain@novell.com OtherBugsDependingO 238668 nThis: I do not think that the yast2-bootloader module is essential in a minimal system. But it cannot get removed since yast2-installation needs it. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=238679 ------- Comment #1 from sh@novell.com 2007-01-25 07:52 MST ------- It might be helpful to split up yast2-installation into yast2-installation-stage1 and yast2-installation-stage2. -stage1 definitely needs yast2-bootloader, grub and lilo, but -stage2 probably does not. Maybe (don't know for sure) this would even get dependencies to yast2-storage and dependent packages (evms, lvm) out of yast2-installation-stage2. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=238679 ------- Comment #2 from aj@novell.com 2007-01-26 00:41 MST ------- Yes, that split sounds like a good idea. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=238679 ------- Comment #3 from jsrain@novell.com 2007-01-26 01:00 MST ------- Whato do we gain if we split it? We can simply remove the dependency on yast2-bootloader and have the yast2-bootloader in the list of modules which need to be present for 1st stage. The question is how to deal with the limal-bootloader and perl-Bootloader stuff. It obviously needs to be installed in order to finish 1st stage of the installation properly. It should be enforced during installation, but after installation it should be possible to remove it. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=238679 sh@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |snwint@novell.com ------- Comment #4 from sh@novell.com 2007-02-07 06:43 MST ------- Well, splitting up yast2-installation would fix just this problem. We could make yast2-installation-stage1 require limal-bootloader and perl-bootloader. Maybe we could limit this to dependencies of the inst-sys: inst-sys requires limal-bootloader and perl-bootloader. This might also be sufficient. Steffen? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=238679 snwint@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|snwint@novell.com | ------- Comment #5 from snwint@novell.com 2007-02-07 07:06 MST ------- Fine with me, just let me know when you do it. Or adjust BuildRequires of installation-images yourself. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=238679 jdsn@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|yast2-maintainers@suse.de |locilka@novell.com Status|ASSIGNED |NEW -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=238679 locilka@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |aj@novell.com ------- Comment #6 from locilka@novell.com 2007-02-12 05:50 MST ------- Splitting installation is indeed good idea, nowadays there are a lot of dependencies that should be solved another way that RPM:requires. For instance, Installation doesn't need yast2-users and yast2-registration, these steps are only mentioned in the control file but I can imagine system with one user (root) and without registration. We need to solve these dependencies for the control-file itself. Andreas, what do you think of that? Why don't we install the control-file package which would require or recommend these packages? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=238679 locilka@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |visnov@novell.com, mvidner@novell.com, | |snwint@novell.com, jsrain@novell.com ------- Comment #7 from locilka@novell.com 2007-02-12 06:09 MST ------- Proposal is to leave yast2-installation package and create another yast2-first-stage-installation or yast2-installation-initial and move some YCP clients and modules to that new package (with their dependencies). Inst-sys would contain: * yast2-installation-initial (probing agents, bootloader, storage deps.) * yast2-installation (Add-Ons, Workflow logic) Installed system (second stage) would contain: * yast2-installation (optionally yast2-installation-initial, of course) Anyway, I see a big problem when inst-sys practically ignores the dependencies and we have to define what is needed manually. Is there any possibility for automation? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=238679 aj@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|aj@novell.com | ------- Comment #8 from aj@novell.com 2007-02-12 06:26 MST ------- I have no good idea - perhaps you like to discuss this on the yast mailing lists. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=238679 ------- Comment #9 from locilka@novell.com 2007-02-12 09:44 MST ------- OK, problem solved. For the first implementation, yast2-installation will: * require only packages that are really needed for the second stage * recommend packages that are defined by the workflow * ignore required packages for the first stage (fulfilled by inst-sys) This will solve the problem with dependencies, problem with too many YCP scripts installed in the system can be ignored, 256 kB is nothing. There is no need to split yast2-installation (thx Jsrain) to more packages, the only quite-needed splitting would be Add-Ons. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=238679 locilka@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FIXED ------- Comment #10 from locilka@novell.com 2007-02-15 09:18 MST ------- Implemented in yast2-installation-2.15.9 Splitting Add-Ons to a separate YaST module might be possible in some next step. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=238679 aj@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |stefan.fent@novell.com Status|RESOLVED |REOPENED Resolution|FIXED | ------- Comment #11 from aj@novell.com 2007-02-28 02:35 MST ------- We now have Bug 249679: The first stage really needs yast2-bootloader - in the chroot environment :-(. So, what shall we do? Should we revert this? Or do you have some good ideas? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=238679 locilka@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |NEEDINFO Info Provider| |snwint@novell.com ------- Comment #12 from locilka@novell.com 2007-02-28 02:54 MST ------- First stage? that's OK, First stage is covered by the inst-sys, isn't it? snwint: is yast2-bootloader in inst-sys? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=238679 aj@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |REOPENED Info Provider|snwint@novell.com | ------- Comment #13 from aj@novell.com 2007-02-28 03:00 MST ------- That's the trap we all fail in. yast2-bootloader is used in first stage but run from the chroot :-(. Perhaps we might not need everything from the package - but we need it... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=238679 locilka@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |ASSIGNED ------- Comment #14 from locilka@novell.com 2007-02-28 03:01 MST ------- Ah, Stano told me that the problem might be because we: - Switch to the installed system (chroot) - Write bootloader settings in chroot Maybe we just need some library, binary, whatever... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=238679 locilka@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FIXED ------- Comment #15 from locilka@novell.com 2007-02-28 03:03 MST ------- Let's close this bug as fixed. Because many other changes than only "yast2-bootloader" were made. And let's solve this issue in bug 249679 instead. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
participants (1)
-
bugzilla_noreply＠novell.com