Bug 126976 – lvm2-2.01.14 stabilization bug

• Status: RESOLVED WONTFIX
• Product: Gentoo Linux

[Description Eric Edgar (RETIRED) 2006-03-20 09:08:50 UTC]

looking to stabilize on this version of lvm2

[Comment 1 Torsten Veller (RETIRED) 2006-03-20 09:23:28 UTC]

This is lvm2-2.01.14-r1?

Please verify the dependency on device-mapper! This is the only ebuild with "=sys-fs/device-mapper-1.01*"
device-mapper-1.01* is not the latest stable on most arches. Downgrade upgrade cycle.

[Comment 2 Aron Griffis (RETIRED) 2006-03-24 11:43:32 UTC]

(In reply to comment #1)
> This is lvm2-2.01.14-r1?
> 
> Please verify the dependency on device-mapper! This is the only ebuild with
> "=sys-fs/device-mapper-1.01*"
> device-mapper-1.01* is not the latest stable on most arches. Downgrade upgrade
> cycle.

Possibly unavoidable.  Later versions of device-mapper require later versions of lvm2 due to API changes, for example see bug 126484

[Comment 3 Torsten Veller (RETIRED) 2006-03-26 04:09:09 UTC]

I think we should try our best to avoid a possible cycle.

Keywords for sys-fs/lvm2:
           | a a a h i m m p p p s s s x 
           | l m r p a 6 i p p p 3 h p 8 
           | p d m p 6 8 p c c c 9   a 6 
           | h 6   a 4 k s   6 - 0   r   
           | a 4             4 m     c   
           |                   a         
           |                   c         
           |                   o         
           |                   s         
-----------+----------------------------
2.01.09    | + +   + +     + +       + +  DEPEND=">=sys-fs/device-mapper-1.01"
2.01.09-r1 | ~ ~   ~       ~ ~       ~ ~  DEPEND=">=sys-fs/device-mapper-1.01"
2.01.13    | ~ ~   ~     ~ ~ ~       ~ ~  DEPEND=">=sys-fs/device-mapper-1.01"
2.01.14-r1 | ~ ~   ~     ~ ~ ~       ~ ~  DEPEND="=sys-fs/device-mapper-1.01*"
2.02.01    |   ~           ~           ~  DEPEND=">=sys-fs/device-mapper-1.02
2.02.02    |   ~     ~     ~           ~  DEPEND=">=sys-fs/device-mapper-1.02.03


Keywords for sys-fs/device-mapper:
        | a a a h i m m p p p s s s x 
        | l m r p a 6 i p p p 3 h p 8 
        | p d m p 6 8 p c c c 9   a 6 
        | h 6   a 4 k s   6 - 0   r   
        | a 4             4 m     c   
        |                   a         
        |                   c         
        |                   o         
        |                   s         
--------+----------------------------
1.01.03 | + + + + + + + + +   + + + + 
1.01.04 | ~ ~ ~ ~ ~ ~ ~ ~ ~   ~ ~ ~ ~ 
1.01.05 | ~ ~ ~ ~ ~ ~ ~ ~ ~   ~ ~ ~ ~ 
1.02.02 | ~ + + + + + ~ + +   + + + + 
1.02.03 | ~ ~ ~ ~ ~ ~ ~ ~ ~   ~ ~ ~ ~ 

I see the following options:
- remove stable mark from sys-fs/device-mapper-1.02.02
- we wait for some 2.02.* version
what else?
Or am i wrong here?

[Comment 4 Mark Loeser (RETIRED) 2006-04-19 12:45:11 UTC]

rocket said we could go with lvm2-2.02.01, which means a few other things need to go stable as well.

cluster: are >=sys-cluster/cman-1.01.00', '>=sys-cluster/dlm-1.01.00  these ready to go stable?

[Comment 5 Gustavo Zacarias (RETIRED) 2006-04-19 12:52:04 UTC]

Why don't we use proper USE flags for cman so if some arch can't test it can be masked in the mean time? Negation USE flags such as "nocman" are really bad and horrible.
And honestly here, which arch team is REALLY testing the functionality of this stuff as in a real clustered LVM2 solution?

[Comment 6 Eric Edgar (RETIRED) 2006-04-19 15:03:34 UTC]

Closing this bug as we have device-mapper issues that require us to stabilize on a higher version.  Opening a new lvm2-2.02.03 stabilization bug.