can't update features in buckminster [message #554497] |
Mon, 23 August 2010 12:01 |
Vlad Dumitrescu Messages: 431 Registered: July 2009 Location: Gothenburg |
Senior Member |
|
|
Hi,
I have a working Buckminster installation that I use with Hudson. All nice and dandy. Alongside the normal Bucky features I need to install my own headless plugin, to do some custom build steps.
The problem is that now when I need to update my feature, I get an error:
Cannot complete the install because of a conflicting dependency.
[0]Software being installed: Erlide core (headless) 0.8.6.201008231151 (org.erlide.headless.feature.group 0.8.6.201008231151)
[0]Software currently installed: Erlide core (headless) 0.8.6.201007231400 (org.erlide.headless.feature.group 0.8.6.201007231400)
[0]Only one of the following can be installed at once:
[0.2]Erlang Interface 0.8.2.201008170742 (org.erlide.jinterface 0.8.2.201008170742)
[0.2]Erlang Interface 0.8.2.201007231400 (org.erlide.jinterface 0.8.2.201007231400)
[0.2]Erlang Interface 0.8.2.201008231151 (org.erlide.jinterface 0.8.2.201008231151)
[0.2]org.erlide.jinterface 0.8.1.201005250801
[0]Cannot satisfy dependency:
[0.2]From: Erlide core (headless) 0.8.6.201007231400 (org.erlide.headless.feature.group 0.8.6.201007231400)
[0.2]To: org.erlide.jinterface [0.8.2.201007231400]
[0]Cannot satisfy dependency:
[0.2]From: Erlide core (headless) 0.8.6.201008231151 (org.erlide.headless.feature.group 0.8.6.201008231151)
[0.2]To: org.erlide.jinterface [0.8.2.201008231151]
I tried to uninstall the old version, doesn't work either (albeit silently).
What is the problem? (Can it be related to the fact that the update site where I installed from doesn't have that version available?)
What can I do to be able to update?
best regards,
Vlad
[Updated on: Mon, 23 August 2010 12:02] Report message to a moderator
|
|
|
|
|
|
|
|
|
|
Re: can't update features in buckminster [message #554537 is a reply to message #554520] |
Mon, 23 August 2010 13:51 |
|
Hi Vlad and Johannes,
On 08/23/2010 03:23 PM, Johannes Utzig wrote:
> Am 23.08.2010 15:19, schrieb Vlad Dumitrescu:
>> With 'buckminster install' and 'buckminster uninstall'. They should call
>> the director under the hood, don't they?
>>
Yes, they do. But there is one difference. With the director, you can provide a whole slew of things to be installed in
one single command and they can be installed from several repositories. p2 will do one single plan and then install all
of it. With Buckminster install, the whole installation process is repeated for each thing that is installed so it's
generally much slower and sometimes less reliable. The end result should be the same but there are corner cases where p2
will make different decisions depending on how much it has access to.
>
> The buckminster install and uninstall is originally based on the old
> update manager and I don't think that it has the same functionality as
> the p2 director.
>
>>> The director should be the safer bet in any case...
Absolutely. The motivation for Buckminster install was to provide a smooth migration path when moving from the old
update manager to p2. It's still there because we don't want to break peoples builds but today it's just a very thin
layer on top of the director.
I definitely agree with Johannes. Use the director instead.
- thomas
|
|
|
|
Powered by
FUDForum. Page generated in 0.02506 seconds