[gentoo-openstack] devstack on gentoo

[gentoo-openstack] devstack on gentoo

[Iván Chavero]

Hello,

I'm adding gentoo as a supported distro in stack.sh and i have a 
question. what's the proper way of handling conflicts like this one??

[blocks B      ] <sys-apps/pciutils-3.1.9-r2 
("<sys-apps/pciutils-3.1.9-r2" is blocking sys-apps/hwids-20130329)
[blocks B      ] sys-apps/module-init-tools 
("sys-apps/module-init-tools" is blocking sys-apps/kmod-12-r1)
[blocks B      ] sys-apps/module-init-tools ("virtual/modutils" is 
blocking sys-apps/module-init-tools-3.5)

let the user deal with it or make stack.sh solve this...

personally i would like to let the user solve this conflicts manually. 
but i could be wrong

here's the githup repo in case you want to check it out

https://github.com/imcsk8/devstack

thanks!

-- 
Iván Chavero
Hacker

Re: [gentoo-openstack] devstack on gentoo

[Matthew Thode]

[-- Attachment #1: Type: text/plain, Size: 1217 bytes --]

On 05/10/13 13:21, Iván Chavero wrote:
> 
> Hello,
> 
> I'm adding gentoo as a supported distro in stack.sh and i have a
> question. what's the proper way of handling conflicts like this one??
> 
> [blocks B      ] <sys-apps/pciutils-3.1.9-r2
> ("<sys-apps/pciutils-3.1.9-r2" is blocking sys-apps/hwids-20130329)
> [blocks B      ] sys-apps/module-init-tools
> ("sys-apps/module-init-tools" is blocking sys-apps/kmod-12-r1)
> [blocks B      ] sys-apps/module-init-tools ("virtual/modutils" is
> blocking sys-apps/module-init-tools-3.5)
> 
> let the user deal with it or make stack.sh solve this...
> 
> personally i would like to let the user solve this conflicts manually.
> but i could be wrong
> 
> here's the githup repo in case you want to check it out
> 
> https://github.com/imcsk8/devstack
> 
> thanks!
> 
This is a blocking loop that doesn't have to do with openstack (it's a
general upgrade issue) :P

but in this case you should unmerge module-init-tools (kmod replaces it).

I haven't had the opportunity to test devstack work, but I'd be
interested in hearing your progress as we probably want to do this on
Gentoo as well.


-- 
-- Matthew Thode (prometheanfire)


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

Re: [gentoo-openstack] devstack on gentoo

[Iván Chavero]

El 10/05/13 13:22, Matthew Thode escribió:
> On 05/10/13 13:21, Iván Chavero wrote:
>> Hello,
>>
>> I'm adding gentoo as a supported distro in stack.sh and i have a
>> question. what's the proper way of handling conflicts like this one??
>>
>> [blocks B      ] <sys-apps/pciutils-3.1.9-r2
>> ("<sys-apps/pciutils-3.1.9-r2" is blocking sys-apps/hwids-20130329)
>> [blocks B      ] sys-apps/module-init-tools
>> ("sys-apps/module-init-tools" is blocking sys-apps/kmod-12-r1)
>> [blocks B      ] sys-apps/module-init-tools ("virtual/modutils" is
>> blocking sys-apps/module-init-tools-3.5)
>>
>> let the user deal with it or make stack.sh solve this...
>>
>> personally i would like to let the user solve this conflicts manually.
>> but i could be wrong
>>
>> here's the githup repo in case you want to check it out
>>
>> https://github.com/imcsk8/devstack
>>
>> thanks!
>>
> This is a blocking loop that doesn't have to do with openstack (it's a
> general upgrade issue) :P
>
> but in this case you should unmerge module-init-tools (kmod replaces it).
>
> I haven't had the opportunity to test devstack work, but I'd be
> interested in hearing your progress as we probably want to do this on
> Gentoo as well.
>
>

oh yeah i just put those lines as an example of the problems that we 
face while running stack.sh on gentoo.
my question was about what stack.sh should do: let the user solve the 
conflict or modify it so it solves this type of problems. but i guess 
that it should be the user the one that solves the conflicts

thanks

-- 
Iván Chavero
Hacker

Re: [gentoo-openstack] devstack on gentoo

[Matthew Thode]

[-- Attachment #1: Type: text/plain, Size: 1779 bytes --]

On 05/10/13 15:11, Iván Chavero wrote:
> El 10/05/13 13:22, Matthew Thode escribió:
>> On 05/10/13 13:21, Iván Chavero wrote:
>>> Hello,
>>>
>>> I'm adding gentoo as a supported distro in stack.sh and i have a
>>> question. what's the proper way of handling conflicts like this one??
>>>
>>> [blocks B      ] <sys-apps/pciutils-3.1.9-r2
>>> ("<sys-apps/pciutils-3.1.9-r2" is blocking sys-apps/hwids-20130329)
>>> [blocks B      ] sys-apps/module-init-tools
>>> ("sys-apps/module-init-tools" is blocking sys-apps/kmod-12-r1)
>>> [blocks B      ] sys-apps/module-init-tools ("virtual/modutils" is
>>> blocking sys-apps/module-init-tools-3.5)
>>>
>>> let the user deal with it or make stack.sh solve this...
>>>
>>> personally i would like to let the user solve this conflicts manually.
>>> but i could be wrong
>>>
>>> here's the githup repo in case you want to check it out
>>>
>>> https://github.com/imcsk8/devstack
>>>
>>> thanks!
>>>
>> This is a blocking loop that doesn't have to do with openstack (it's a
>> general upgrade issue) :P
>>
>> but in this case you should unmerge module-init-tools (kmod replaces it).
>>
>> I haven't had the opportunity to test devstack work, but I'd be
>> interested in hearing your progress as we probably want to do this on
>> Gentoo as well.
>>
>>
> 
> oh yeah i just put those lines as an example of the problems that we
> face while running stack.sh on gentoo.
> my question was about what stack.sh should do: let the user solve the
> conflict or modify it so it solves this type of problems. but i guess
> that it should be the user the one that solves the conflicts
> 
> thanks
> 
Ya, it should be either upstream(packager) or the end user :D

-- 
-- Matthew Thode (prometheanfire)


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

Re: [gentoo-openstack] devstack on gentoo

[Iván Chavero]

i also took out kernel stuff like KVM modules since gentoo users usualy 
compile their own kernels.
the script is working pretty well so far. the working version is on 
github (https://github.com/imcsk8/devstack)



El 10/05/13 15:07, Matthew Thode escribió:
> On 05/10/13 15:11, Iván Chavero wrote:
>> El 10/05/13 13:22, Matthew Thode escribió:
>>> On 05/10/13 13:21, Iván Chavero wrote:
>>>> Hello,
>>>>
>>>> I'm adding gentoo as a supported distro in stack.sh and i have a
>>>> question. what's the proper way of handling conflicts like this one??
>>>>
>>>> [blocks B      ] <sys-apps/pciutils-3.1.9-r2
>>>> ("<sys-apps/pciutils-3.1.9-r2" is blocking sys-apps/hwids-20130329)
>>>> [blocks B      ] sys-apps/module-init-tools
>>>> ("sys-apps/module-init-tools" is blocking sys-apps/kmod-12-r1)
>>>> [blocks B      ] sys-apps/module-init-tools ("virtual/modutils" is
>>>> blocking sys-apps/module-init-tools-3.5)
>>>>
>>>> let the user deal with it or make stack.sh solve this...
>>>>
>>>> personally i would like to let the user solve this conflicts manually.
>>>> but i could be wrong
>>>>
>>>> here's the githup repo in case you want to check it out
>>>>
>>>> https://github.com/imcsk8/devstack
>>>>
>>>> thanks!
>>>>
>>> This is a blocking loop that doesn't have to do with openstack (it's a
>>> general upgrade issue) :P
>>>
>>> but in this case you should unmerge module-init-tools (kmod replaces it).
>>>
>>> I haven't had the opportunity to test devstack work, but I'd be
>>> interested in hearing your progress as we probably want to do this on
>>> Gentoo as well.
>>>
>>>
>> oh yeah i just put those lines as an example of the problems that we
>> face while running stack.sh on gentoo.
>> my question was about what stack.sh should do: let the user solve the
>> conflict or modify it so it solves this type of problems. but i guess
>> that it should be the user the one that solves the conflicts
>>
>> thanks
>>
> Ya, it should be either upstream(packager) or the end user :D
>


-- 
Iván Chavero
Hacker

Re: [gentoo-openstack] devstack on gentoo

[Matthew Thode]

[-- Attachment #1: Type: text/plain, Size: 2257 bytes --]

On 05/10/13 16:34, Iván Chavero wrote:
> 
> i also took out kernel stuff like KVM modules since gentoo users usualy
> compile their own kernels.
> the script is working pretty well so far. the working version is on
> github (https://github.com/imcsk8/devstack)
> 
> 
> 
> El 10/05/13 15:07, Matthew Thode escribió:
>> On 05/10/13 15:11, Iván Chavero wrote:
>>> El 10/05/13 13:22, Matthew Thode escribió:
>>>> On 05/10/13 13:21, Iván Chavero wrote:
>>>>> Hello,
>>>>>
>>>>> I'm adding gentoo as a supported distro in stack.sh and i have a
>>>>> question. what's the proper way of handling conflicts like this one??
>>>>>
>>>>> [blocks B      ] <sys-apps/pciutils-3.1.9-r2
>>>>> ("<sys-apps/pciutils-3.1.9-r2" is blocking sys-apps/hwids-20130329)
>>>>> [blocks B      ] sys-apps/module-init-tools
>>>>> ("sys-apps/module-init-tools" is blocking sys-apps/kmod-12-r1)
>>>>> [blocks B      ] sys-apps/module-init-tools ("virtual/modutils" is
>>>>> blocking sys-apps/module-init-tools-3.5)
>>>>>
>>>>> let the user deal with it or make stack.sh solve this...
>>>>>
>>>>> personally i would like to let the user solve this conflicts manually.
>>>>> but i could be wrong
>>>>>
>>>>> here's the githup repo in case you want to check it out
>>>>>
>>>>> https://github.com/imcsk8/devstack
>>>>>
>>>>> thanks!
>>>>>
>>>> This is a blocking loop that doesn't have to do with openstack (it's a
>>>> general upgrade issue) :P
>>>>
>>>> but in this case you should unmerge module-init-tools (kmod replaces
>>>> it).
>>>>
>>>> I haven't had the opportunity to test devstack work, but I'd be
>>>> interested in hearing your progress as we probably want to do this on
>>>> Gentoo as well.
>>>>
>>>>
>>> oh yeah i just put those lines as an example of the problems that we
>>> face while running stack.sh on gentoo.
>>> my question was about what stack.sh should do: let the user solve the
>>> conflict or modify it so it solves this type of problems. but i guess
>>> that it should be the user the one that solves the conflicts
>>>
>>> thanks
>>>
>> Ya, it should be either upstream(packager) or the end user :D
>>
> 
> 
Ya, better to rely on kernel config checking.

-- 
-- Matthew Thode (prometheanfire)


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]