| 1 |
On 05/10/13 16:34, Iván Chavero wrote: |
| 2 |
> |
| 3 |
> i also took out kernel stuff like KVM modules since gentoo users usualy |
| 4 |
> compile their own kernels. |
| 5 |
> the script is working pretty well so far. the working version is on |
| 6 |
> github (https://github.com/imcsk8/devstack) |
| 7 |
> |
| 8 |
> |
| 9 |
> |
| 10 |
> El 10/05/13 15:07, Matthew Thode escribió: |
| 11 |
>> On 05/10/13 15:11, Iván Chavero wrote: |
| 12 |
>>> El 10/05/13 13:22, Matthew Thode escribió: |
| 13 |
>>>> On 05/10/13 13:21, Iván Chavero wrote: |
| 14 |
>>>>> Hello, |
| 15 |
>>>>> |
| 16 |
>>>>> I'm adding gentoo as a supported distro in stack.sh and i have a |
| 17 |
>>>>> question. what's the proper way of handling conflicts like this one?? |
| 18 |
>>>>> |
| 19 |
>>>>> [blocks B ] <sys-apps/pciutils-3.1.9-r2 |
| 20 |
>>>>> ("<sys-apps/pciutils-3.1.9-r2" is blocking sys-apps/hwids-20130329) |
| 21 |
>>>>> [blocks B ] sys-apps/module-init-tools |
| 22 |
>>>>> ("sys-apps/module-init-tools" is blocking sys-apps/kmod-12-r1) |
| 23 |
>>>>> [blocks B ] sys-apps/module-init-tools ("virtual/modutils" is |
| 24 |
>>>>> blocking sys-apps/module-init-tools-3.5) |
| 25 |
>>>>> |
| 26 |
>>>>> let the user deal with it or make stack.sh solve this... |
| 27 |
>>>>> |
| 28 |
>>>>> personally i would like to let the user solve this conflicts manually. |
| 29 |
>>>>> but i could be wrong |
| 30 |
>>>>> |
| 31 |
>>>>> here's the githup repo in case you want to check it out |
| 32 |
>>>>> |
| 33 |
>>>>> https://github.com/imcsk8/devstack |
| 34 |
>>>>> |
| 35 |
>>>>> thanks! |
| 36 |
>>>>> |
| 37 |
>>>> This is a blocking loop that doesn't have to do with openstack (it's a |
| 38 |
>>>> general upgrade issue) :P |
| 39 |
>>>> |
| 40 |
>>>> but in this case you should unmerge module-init-tools (kmod replaces |
| 41 |
>>>> it). |
| 42 |
>>>> |
| 43 |
>>>> I haven't had the opportunity to test devstack work, but I'd be |
| 44 |
>>>> interested in hearing your progress as we probably want to do this on |
| 45 |
>>>> Gentoo as well. |
| 46 |
>>>> |
| 47 |
>>>> |
| 48 |
>>> oh yeah i just put those lines as an example of the problems that we |
| 49 |
>>> face while running stack.sh on gentoo. |
| 50 |
>>> my question was about what stack.sh should do: let the user solve the |
| 51 |
>>> conflict or modify it so it solves this type of problems. but i guess |
| 52 |
>>> that it should be the user the one that solves the conflicts |
| 53 |
>>> |
| 54 |
>>> thanks |
| 55 |
>>> |
| 56 |
>> Ya, it should be either upstream(packager) or the end user :D |
| 57 |
>> |
| 58 |
> |
| 59 |
> |
| 60 |
Ya, better to rely on kernel config checking. |
| 61 |
|
| 62 |
-- |
| 63 |
-- Matthew Thode (prometheanfire) |
Archives