[Hamara-devel] Fwd: Re: Ubiquity Packaging work

[Raju DV]

On Tuesday 05 April 2016 06:07 PM, Vikas Tara wrote:
> On 05/04/16 10:00, Raju D V wrote:
>>
>>
>> On Monday 04 April 2016 06:39 PM, Vikas Tara wrote:
>>> On 04/04/16 12:29, Raju D V wrote:
>>>> <Snipped>
>>>>
>>>> We have resolved all dependencies of ubiquity.
>>>> But while building the package I am getting these errors.
>>>>
>>>> https://paste.hamaralinux.org/?8a06c8faf08e37ba#7qRiaD4KBs0y+TPNOQqE2hnacYNZ8DJPhbc18vEDA0k=
>>>>
>>>> These are being caused by the checks that pep8 package runs on the 
>>>> python files.
>>>> There is a long list of error codes being listed there.
>>>>
>>>> I have the description of the error codes listed here 
>>>> http://pep8.readthedocs.org/en/latest/intro.html
>>>>
>>>> But I am not sure how to resolve them.
>>>> I tried manually editing the particular files, but that results in 
>>>> more error codes for the same line.
>>>> Has anyone faced this earlier?
>>>
>>> This could be to do with version of pep that is in use.
>>>
>>> Can you compare the version you are using with the one in the ubuntu 
>>> version that your taking Ubiquity source from?
>>>
>>> It's likely that there is a different pep rules set and that is 
>>> causing your issue.
>>>
>>
>> The pep8 issue has been resolved. It was complaining about some 
>> particular files. In its configuration we have configured it to skip 
>> the checks for those files.
>>
>> But now the state of errors with different versions of ubiquity in 
>> different Ubuntu releases are as follows.
>>
>> with ubiquity-xenial
>>
>> https://paste.hamaralinux.org/?eac6a80e81788fd4#zDq5Qw/ZGoirbX4Ywxnix+XXxE13NfGLKJ9Cpe7zil8=
>>
>> with ubiquity-wily
>>
>> https://paste.hamaralinux.org/?a8e52deb317d44e0#I3qDiSsBkAxjUiwj61SfU7wN3csosfono07pFmeJ+kU=
>>
>> with ubiquity-vivid
>>
>> https://paste.hamaralinux.org/?1fa2820e8f4fafcf#yb8YF7M9sJ81DNiwBCMnEEgVdpYd+fLxX46a+Yaoruo=
>>
>> with ubiquity-trusty
>>
>> https://paste.hamaralinux.org/?c666daa6d77e8323#yQoh5I6TeBy5vqzqC9kfGShQHH8LvtQWgm6Y+f6X4gM=
>>
>>
>>
>> Out of all these builds, the problems with xenial, wily & vivid have 
>> this similar block of errors
>>
>> ---------------------------------------------------------------------------
>> |checking for PANEL... no configure: error: Package requirements 
>> (glib-2.0 gtk+-3.0 >= 3.1.4 indicator3-0.4 >= 12.10.2 libido3-0.1 >= 
>> 13.10.1 x11) were not met: Requested 'indicator3-0.4 >= 12.10.2' but 
>> version of libindicator3 is 0.5.0 Requested 'libido3-0.1 >= 13.10.1' 
>> but version of libido is 0.3.4 
>> ------------------------------------------------------------------------- 
>> while with Trusty a lot of errors are just because of pep8 tests. |
>>  Now I am trying to build the ubuntu specific versions of indicator 
>> and libido. 
> This is great work Raju - well done :)
>
> Personally though - I would work with the trusty packages and solve 
> the pep errors. You have successfully done that on other ubuntu 
> versions already.
>
> I think solving the indicator and libido3-0.1 errors are a much bigger 
> can of worms that you probably don't want right now!
I moved on from trusty  to vivid after seeing these bug reports

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=797398

https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1492261

They state that they have been resolved in the next releases.

But all the next releases prior to ubuntu are complaining for libido and 
libindicator errors.

I am trying to get libido built. It has a dependency which requires 
specifically gcc-4.7 and g++-4.7
while these packages are no more in debian. debian has 4.8 and 5


>
>
> _______________________________________________
> Hamara-devel mailing list
> Hamara-devel at lists.hamaralinux.org
> http://lists.hamaralinux.org/listinfo/hamara-devel

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.hamaralinux.org/pipermail/hamara-devel/attachments/20160405/0c25c58c/attachment-0001.html>