yes, please submit.

Anas

On 16 May 2011, at 04:17, Dong, Junfeng wrote:

> Hi Anas,
> I see you have accepted the request of libtool in Trunk:Testing, while not 
> submitted the change to apr, gysper, pacrunner, which I pushed in devel:next.
> Do I need to resubmit them to Trunk:Testing?
> 
> Junfeng
> 
> -----Original Message-----
> From: Anas Nashif [mailto:[email protected]] 
> Sent: Tuesday, May 10, 2011 5:29 PM
> To: Dong, Junfeng
> Cc: Carsten Munk; [email protected]
> Subject: Re: [meego-packaging] [Headsup] libtool is going to update to 2.4 in 
> Meego 1.3
> 
> i will put it in devel:next and see what happens. Please stay tuned.
> 
> Anas
> 
> On 10 May 2011, at 07:33, Dong, Junfeng wrote:
> 
>> I have tested the change in devel:base, and fixed all the regression exposed 
>> in devel:base. But it is still likely some packages which uncovered by 
>> devel:base are affected by it. That is why I submit the heads up.
>> 
>> Junfeng
>> 
>> -----Original Message-----
>> From: [email protected] [mailto:[email protected]] On Behalf Of 
>> Carsten Munk
>> Sent: Tuesday, May 10, 2011 2:24 PM
>> To: Dong, Junfeng
>> Cc: Arjan van de Ven; [email protected]
>> Subject: Re: [meego-packaging] [Headsup] libtool is going to update to 2.4 
>> in Meego 1.3
>> 
>> 011/5/10 Dong, Junfeng <[email protected]>:
>>> If the new libtool doesn't enter Trunk:Testing, how do we catch which 
>>> package will be affected by it?
>>> 
>>> And a typo error in my former email, you should add "autoreconf --force 
>>> --install".
>>> Junfeng
>> 
>> If I was you, I would first enter it into devel:base to test
>> regresssions, or, alternatively set up a "linked project" of
>> Trunk:Testing temporarily, inserting the libtool change, seeing the
>> effect on the builds and being ready to send patches.
>> 
>> /Carsten
>> 
>>> 
>>> -----Original Message-----
>>> From: Arjan van de Ven [mailto:[email protected]]
>>> Sent: Monday, May 09, 2011 10:14 PM
>>> To: Dong, Junfeng
>>> Cc: [email protected]
>>> Subject: Re: [meego-packaging] [Headsup] libtool is going to update to 2.4 
>>> in Meego 1.3
>>> 
>>> On 5/9/2011 6:17 AM, Dong, Junfeng wrote:
>>>> Hi maintainers,
>>>> I am going to update libtool to the latest version 2.4. If your
>>>> package depends on an old version libtool (see the file of ltmain.sh),
>>>> it may run into compiler time error. You need add "autoconf -force
>>>> -install" in your spec file before running "configure".
>>>> I have fixed some packages in devel:base project, for example
>>>> "pixman", "geoclue" and "ofono". If your packages still can't work by
>>>> this way, feel free to contact me. I am glad to help you investigate
>>>> the problem.
>>>> 
>>> 
>>> and obviously we'll not go to this new libtool until all packages are
>>> fixed....
>>> 
>>> _______________________________________________
>>> MeeGo-packaging mailing list
>>> [email protected]
>>> http://lists.meego.com/listinfo/meego-packaging
>>> 
>> _______________________________________________
>> MeeGo-packaging mailing list
>> [email protected]
>> http://lists.meego.com/listinfo/meego-packaging
> 

_______________________________________________
MeeGo-packaging mailing list
[email protected]
http://lists.meego.com/listinfo/meego-packaging

Reply via email to