public inbox for gentoo-openstack@lists.gentoo.org
 help / color / mirror / Atom feed
From: Matthew Thode <prometheanfire@gentoo.org>
To: gentoo-openstack@lists.gentoo.org
Subject: Re: [gentoo-openstack] devstack on gentoo
Date: Fri, 10 May 2013 16:07:46 -0500	[thread overview]
Message-ID: <518D61A2.3080002@gentoo.org> (raw)
In-Reply-To: <518D5477.2000604@chavero.com.mx>

[-- 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 --]

  reply	other threads:[~2013-05-10 21:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1368158407-14739-mlmmj-2748880e@lists.gentoo.org>
2013-05-10 18:21 ` [gentoo-openstack] devstack on gentoo Iván Chavero
2013-05-10 19:22   ` Matthew Thode
2013-05-10 20:11     ` Iván Chavero
2013-05-10 21:07       ` Matthew Thode [this message]
2013-05-10 21:34         ` Iván Chavero
2013-05-11  4:03           ` Matthew Thode

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=518D61A2.3080002@gentoo.org \
    --to=prometheanfire@gentoo.org \
    --cc=gentoo-openstack@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox