Bug 10028 - Initscripts update want to empty /etc/crypttab !!
Summary: Initscripts update want to empty /etc/crypttab !!
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: release_blocker critical
Target Milestone: ---
Assignee: Olivier Blin
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-05-08 22:46 CEST by Morgan Leijström
Modified: 2013-05-09 09:18 CEST (History)
2 users (show)

See Also:
Source RPM: Initscripts-9.41-14.mga3
CVE:
Status comment:


Attachments
Screenshot (62.28 KB, image/png)
2013-05-08 23:22 CEST, Morgan Leijström
Details

Description Morgan Leijström 2013-05-08 22:46:40 CEST
Description of problem:
Initscripts update want to empty /etc/crypttab and i guess that would render system unbootable, or cause further problem (have not tested.)

* To be sure not to ship a wrecking system i post this ASAP and set it release blocker, be free to change if that is wrong. *

Version-Release number of selected component (if applicable): 9.41-14.mga3


How reproducible:
Sorry have no time to test right now.


Steps to Reproduce:
1. Installed 3RC (last update this morning)
  One disk containing ext4 /boot, rest of partitions in a encrypted LVM
  crypttab conbtain the UUID of sda5
2. Ran update now
3. It asks as attached image the.rpmnew is empty.  (see attached screen shot)
  (I selected do nothing.)


Reproducible: 

Steps to Reproduce:
Morgan Leijström 2013-05-08 22:46:58 CEST

Priority: Normal => release_blocker

Comment 1 David Walser 2013-05-08 23:17:46 CEST
People had the same issue with the setup package and /etc/{g,}shadow, but of course you shouldn't overwrite any of those files with the .rpmnew files.  They put an exception in mgaapplet so it wouldn't even ask you for those files, so I suppose /etc/crypttab could be added to that list.  It'd be nice if there was a better solution where you could give %config(noreplace) another option where it wouldn't create an .rpmnew at all.

CC: (none) => thierry.vignaud, tmb

Comment 2 Morgan Leijström 2013-05-08 23:22:44 CEST
Created attachment 3903 [details]
Screenshot
Comment 3 Thomas Backlund 2013-05-08 23:38:39 CEST
Fixed in rpmdrake 5.49

Status: NEW => RESOLVED
Resolution: (none) => FIXED

Comment 4 Morgan Leijström 2013-05-09 09:18:25 CEST
That was quick! Thanks :)

Note You need to log in before you can comment on or make changes to this bug.