Bug 217740 - Stabilize sys-fs/device-mapper-1.02.24-r1
Bug#: 217740 Product:  Gentoo Linux Version: unspecified Platform: All
OS/Version: Linux Status: RESOLVED Severity: enhancement Priority: P3
Resolution: FIXED Assigned To: base-system@gentoo.org Reported By: vapier@gentoo.org
Component: Ebuilds
URL: 
Summary: Stabilize sys-fs/device-mapper-1.02.24-r1
Keywords:  STABLEREQ
Status Whiteboard: 
Opened: 2008-04-14 22:47 0000
Description:   Opened: 2008-04-14 22:47 0000 
doit

------- Comment #1 From Markus Rothe 2008-04-15 05:43:02 0000 ------- 
ppc64 stable

------- Comment #2 From Tobias Klausmann 2008-04-16 19:26:19 0000 ------- 
Stable on alpha.

------- Comment #3 From nixnut 2008-04-17 18:11:40 0000 ------- 
ppc stable

------- Comment #4 From Markus Meier 2008-04-20 16:14:22 0000 ------- 
amd64/x86 stable

------- Comment #5 From Raúl Porcel 2008-04-21 17:58:39 0000 ------- 
ia64/sparc stable

------- Comment #6 From Jeroen Roovers 2008-04-21 18:22:16 0000 ------- 
Stable for HPPA.

------- Comment #7 From Calum Selkirk 2008-04-22 13:16:45 0000 ------- 
nixnut: this is stable on ppc!? .. no it isn't. After an 'emerge world &&
etc-update' (which pulled in this device-mapper update) my encrypted /home and
swap are no-longer mounted on boot (no prompt for passphrase, nada). Having
lost, irrecoverably, my encypted /home on the last cryptsetup/device-mapper
update I'm about ready to give  up expecting any kind of 'stable' on Gentoo.

------- Comment #8 From SpanKY 2008-04-22 19:06:50 0000 ------- 
if you have a problem with a package, open a new bug report

------- Comment #9 From solar 2008-06-18 01:28:35 0000 ------- 
Stable?

sys-fs/device-mapper-1.02.24-r1 (/etc/init.d/device-mapper)

 * The device-mapper init script is written for baselayout-2
 * Please do not use it with baselayout-1

baselayout-2 is not in stable and thus we can't do an etc-update.

------- Comment #10 From Robin Johnson 2008-06-18 02:22:01 0000 ------- 
solar: Barking up the wrong tree.
/etc/init.d/device-mapper is ONLY to set up entries from /etc/dmtab on
baselayout2 (via dm-start.sh). Baselayout1 calls dm-start.sh automatically
anyway.

If your /etc/dmtab is empty, there is no point in using
/etc/init.d/device-mapper.