Home | Docs | Forums | Lists | Bugs | Planet | Store | GMN | Get Gentoo!

Full Text Bug Listing

The emerge dies.

  Someone seems to have copied the EVMS 1.2.x ebuild and renamed it (not a big
deal), then not tested it (bad)!  There are big changes, the install is no
exception.  I will attach an ebuild I mostly made while privately messing-
around with the unstable tree.  It doesn't work perfect (I was having trouble
getting the optional use flags to work, so commented that out), but it gets
closer than a copied ebuild!

-- Daniel Mannarino

Reproducible: Always
Steps to Reproduce:

1. Emerge evms
2.
3. Profit!  Oops, not on Slashdot...

Actual Results:  
Erm, nothing!

Expected Results:  
Anything!
Well, installed for starters :;)

 Someone seems to have copied the EVMS 1.2.x ebuild and renamed it (not a big
deal), then not tested it (bad)!  There are big changes, the install is no
exception.  I will attach an ebuild I mostly made while privately messing-
around with the 1.9xs.  It doesn't work perfect (I was having trouble
getting the optional use flags to work, so commented that out), but it gets
closer than a copied ebuild!  Also, someone who uses it should seriously
scrutinize the init script.  I haven't taken a real stab at using this stuff
yet, so I haven't.  However I think the ebuild should be fixed/masked ASAP.

I'm still working on it though, and may have a real one later tonight.

-- Daniel Mannarino

Created an attachment (id=10250) [details]
evms-2.0.0.ebuild (Updated ebuild)

   Here it is.	Like I said, it's not perfect, though it should compile
and not trash your system.  :;)

   BTW, I am sorry:  I seem to have double-posted the bug.

-- Daniel Mannarino

Created an attachment (id=10252) [details]
evms-2.0.0.ebuild (Fixed ebuild, Mark II)

   Try this one instead, it fixes the use flags.

-- Daniel Mannarino

evms-2 requires a different kernel patch too, I believe

Thanks for the ebuild, it compiled and installed fine (I am going to change
from LVM 
to EVMS and have yet to actually test the new EVMS). 

Here a comment: I think the ebuild should also install the files INSTALL, 
INSTALL.initrd, and INSTALL.HA into /usr/share/doc/evms-2.0.0/ because they 
contain valuable information (for example how to setup kernel and EVMS when
your 
rootfs is on a EVMS volume, which is what I need). 

Two more observations: 
 
The ebuild still installs the /etc/init.d/evms script from 
EVMS 1 which does not work with EVMS 2. 
The tarball has a sample initrc script in the doc dir. With 
EVMS 2 it's enough to just call evms_activate or 
evms_deactivate. But because EVMS 2 has no longer 
kernel-based discovery and discovery is now done in 
user space, I think it would be good to have EVMS 
support in /etc/init.d/checkfs (i.e. an evms_activate call), 
just like it is already done for LVM and RAID. 
 
In my tests evms_activate segfaults during execution 
inside the initrd environment when used with 
linux-2.5.66-mm3 (I applied the 2.5.66 patches from the 
EVMS 2 tarball). And because my rootfs is on LVM, I 
can't boot. Thus I fear I can't investigate this any further. 
There were no helpful error messages. Maybe I look 
again into this when I have more time. 
 
Good luck. 

Please ignore my comment about evms_activate segfaulting. 
I had very stupid bug in my initrd. 

Ok, as I broke it i'm now going to repair it...
Here's what I did so far:
- Checked in the updated ebuild as -r1 and removed -r0.
- Added a new init-script as evms2-init (-r1 uses this one)
- Added INSTALL, INSTALL.initrd, and INSTALL.HA to DODOC.

I think all that has to be done from this point on is:
- EVMS support in /etc/init.d/checkfs (i.e. an evms_activate call)


So far so good...

Shouldn't EVMS-2 be masked until there are kernels with EVMS-2 support in the 
Portage tree, i.e. which have the respective patches applied? 
 
EVMS-2.0.0 supports kernels 2.5.66 and 2.4.20. But so far none of those kernels 
works out of the box with EVMS-2, all need special patches which can be found in 
the EVMS tarball. And as far as I see none of the kernels currently in Portage has 
these patches applied. All EVMS enabled kernels in the Portage tree still need the 
EVMS-1.2 tools and libraries. 
 

As I can see the 2.0.0-r1 has ~ in it and is masked in that way.
I think the kernel ebuilds should ensure to pick the right version by adding/editing DEPEND and RDEPEND to <evms-2.0.0 .

Thank you  ::)

please try it in combination with gentoo-sources-2.4.20-r3 which has evms 2.0
support in it 
by using USE="evms2". You might want to use aavm (USE="aavm") when running with
evms 
2.0 - also remember to read the evms2 doc in the gentoo-sources documentation
or in the 
evms 2.0 build. This stuff is pretty new and will b0rk lvm2 - *user beware*.
I'd recommend 
staying with 1.2.1 until this is more tested. You'll also need an initrd if
you're going to have 
your root partition is using evms. But, anyone who wants to test this out on a
development 
box - it is there. 

If using evms 2.0 ruins your system - don't say I didn't warn you or recommend
that you do 
plenty of research first. 

Regards, 

Jay 

seems the ebuild is fixed and there is support in @ least one kernel. 
 
closing. 
 
Jay