Re: [Banshee-List] banshee+monoaddins+opensuse

[Nelson Marques <nmo marques gmail com>]

There's obviously a communication problem which I can't fix... so I
did as asked, placed the mono-addins on Banshee repo and 11.3 and 11.4
builds are now building against mono-addins 0.6.2 and completly
ignoring that all applications that are provided by openSUSE 11.4/11.3
have an explicit requires for mono(0.5.0.0) which might trigger fun
events with packagekit updating not to mention that some application
will be broken for sure.

Since I don't have a 11.4 system, I can't test them. For what I've
seen in Factory, upgrading from 0.6.1 (0.6.0.0) for 0.6.2 (0.6.0.0)
doesn't bring problems, but on 11.4 applications were built against
0.5.0.0 and have it on the requirements.

I do it like Pilatus, from here I wash my hands.

NM


2011/10/5 Stephen Shaw <sshaw decriptor com>:
> On Tue, Oct 4, 2011 at 09:46, Nelson Marques <nmo marques gmail com> wrote:
>> 2011/10/4 Andres G. Aragoneses <knocte gmail com>:
>>> On 10/04/2011 04:05 PM, Nelson Marques wrote:
>>>>
>>>> 2011/10/4 Andres G. Aragoneses<knocte gmail com>:
>>>>>
>>>>> Hey Nelson, you mind answering a couple of questions about this:
>>>>
>>>> Hey
>>>>
>>>>> On 10/04/2011 01:22 AM, Nelson Marques wrote:
>>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> Banshee 2.2.0 from the Banshee repository is build against the
>>>>>> dependencies provided by the base system (in your case openSUSE 11.4),
>>>>>> this means it was build against mono framework and mono-addins
>>>>>> provided by 11.4. Since 11.4 doesn't provide all the dependencies we
>>>>>> add the ones missing, a list can be found here[1].
>>>>>>
>>>>>> I did some changes[2] with the introduction of banshee 2.2.0, one of
>>>>>> them was to remove some packages from the mono framework (ex:
>>>>>> mono-core) and mono-addins because if people installed them it would
>>>>>> break other applications (F-Spot and GNOME Do are 2 known cases).
>>>>>
>>>>> Break applications in what way? You have logs or URLs of bugs about this?
>>>>
>>>> Applications stopped working, didn't even launched. This was reported
>>>> to me by a user in #opensuse-gnome, and F-Spot was one of the
>>>> identified applications that stopped working. A few days later I've
>>>> seen complaints ago GNOME Do as well.
>>>>
>>>> Also like two weeks ago, a user on this list also confirmed this
>>>> situation. I haven't opened a bug report because with the introduction
>>>> of Banshee 2.2.0 SLE and SLE11SP1 would not provide the dependencies
>>>> to build banshee 2.2.0 (ex: gstreamer), so I wiped those packages.
>>>>
>>>> If you need any kind of report or deeper look into this, I can
>>>> replicate that behavior and get a branch with banshee linking against
>>>> a different version of mono-addins and pull the logs from f-spot.
>>>
>>> Well, at least a stacktrace of the problem when launching the application
>>> under a terminal, would be the minimal thing to ask.
>>
>> I have created Banshee:Testing for this and configured two
>> repositories, one for 11.4 and another for Factory. This is plain
>> Banshee with mono-addins 0.6.2. I don't have a 11.4 install to test
>> this, but I'll see if I can grab someone to do this test and give the
>> output.
>>
>> I'll share some news about this soon. I've found problems myself
>> because I only 3 applications, banshee/totem, chrome and
>> gnome-terminal :)
>>
>> NM
>>
>>>
>>>
>>>>
>>>>>
>>>>>> I dont mind adding a build target to link against a more updated
>>>>>> version of mono if someone has usage for it, but be warned that if
>>>>>> people update other apps built against a different version might stop
>>>>>> working.
>>>>>
>>>>> I still don't know why you think you need to pull a newer mono for this
>>>>> mono-addins issue. MonoAddins is a package completely independent from
>>>>> Mono
>>>>> and you can pull a new version from it without tinkering with the rest of
>>>>> mono-related packages.
>>>>
>>>> OBS allows me to create a built target using any number of
>>>> repositories I want, since mono-addins is maintained on Mono:Factory,
>>>> linking against that repo would use the latest mono framework and
>>>> mono-addins.
>>>
>>> I see! Well, then in my opinion what should happen is that MonoAddins should
>>> be moved to Mono:Community repository, not to Mono:Factory.
>>
>> I don't understand much of the Mono layout on OBS, Stephen has helped
>> me when I needed, I did updated some packages and did some tinkering
>> for older systems (SLE11). It's probably something that the best way
>> would be to talk with the Mono maintainers. I know that Mono:Factory
>> is important because that's the development project for openSUSE
>> Factory, whatever goes to openSUSE is taken from Mono:Factory.
>>
>> I've submitted yesterday mono-addins 0.6.2, but that's my role there,
>> if I find something that can be updated, I'll submit the update, and I
>> submitted to Mono:Factory after asking Stephen what would be the
>> proper recipient.
>>
>> NM
>
> So, I'm not sure I'm follow this entirely, but what you might want to
> do is just link to the mono-addins package in the Mono:Factory
> project.  That way it will rebuild against whatever mono is currently
> available in that repository whether it be 11.4 or factory.
>
> Cheers,
> Stephen
>
> PS. If you do have to have a newer mono, you could build against the
> Mono:Factory repository (or which ever mono repo) and then require the
> user to add that mono repo.  A 1 click would make that more
> transparent.
> _______________________________________________
> banshee-list mailing list
> banshee-list gnome org
> http://mail.gnome.org/mailman/listinfo/banshee-list  (unsubscribe here)
>



-- 
Nelson Marques

/* http://www.marques.so
  nmo marques gmail com */