|
Bugzilla – Full Text Bug Listing |
| Summary: | splitting of cryptsetup-mkinitrd broke booting systems that reside on an encrypted lvm | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE Tumbleweed | Reporter: | Christoph Obexer <cobexer> |
| Component: | Security | Assignee: | Ludwig Nussel <lnussel> |
| Status: | RESOLVED FIXED | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Critical | ||
| Priority: | P5 - None | CC: | aschnell, ismail, lnussel, mls |
| Version: | 13.1 Milestone 1 | ||
| Target Milestone: | --- | ||
| Hardware: | x86-64 | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: | Solver testcase | ||
|
Description
Christoph Obexer
2012-12-29 22:55:05 UTC
assigning to idonmez since he committed cryptsetup-mkinitrd to Factory Ludwig? Hmm. I've added a packageand(mkinitrd:cryptsetup) to the package to have it auto installed if both mkinitrd and cryptsetup are installed. To make really sure yast could probably also add it as requirement when installing with root on crypted lvm. Would that be possible? This is an autogenerated message for OBS integration: This bug (796167) was mentioned in https://build.opensuse.org/request/show/147355 Factory / cryptsetup-mkinitrd The package dependencies have to work reliable for 'zypper up' anyway so I don't see the need to add special handling in YaST. the "zypper dup" case is handled by the split-provides, I'm referring to the initial installation here. Created attachment 519267 [details] Solver testcase (In reply to comment #6) > the "zypper dup" case is handled by the split-provides, I'm referring to the > initial installation here. No, it is not. Yesterday, I spend some time with Dirk to debug why this is the case. Here's the result of "zypper -v dup --debug-solver" from the old set of packages (before the split). Ok, so either we need to split the bug into separate ones now or take one step at a time. From my PoV the packaging side is implemented correctly by the split-provides and the new packageand I added yesterday. If zypp doesn't evaluate those tags properly it's a zypp or solver bug so we have to reassign. But first I'd like to have Arvin make yast explicitly require cryptsetup-mkinitrd during initial installation if root is on crypted lvm. Just to make sure it's installed as the package tags are only weak deps. Apparently I misunderstood "to make really sure yast could probably ..." as being something nice to have. The problem with adding cryptsetup-mkinitrd during installation only if the volume group is using an encrypted physical volume is that the package will be missing if later on an encrypted physical volume is added to a volume group so far not including encrypted physical volumes. So I will simply add cryptsetup-mkinitrd where so far cryptsetup is installed. After all I don't see the reason for a package-split with only a few files - and no reason is provided in the changelog. I recommend to make a separate bug for the zypp problem. This is an autogenerated message for OBS integration: This bug (796167) was mentioned in https://build.opensuse.org/request/show/148446 Factory / yast2-storage |