<html>
  <head>
    <meta content="text/html; charset=utf-8" http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix">On 05/04/16 14:48, Raju DV wrote:<br>
    </div>
    <blockquote cite="mid:5703C21D.6090104@openmailbox.org" type="cite">
      <meta content="text/html; charset=utf-8" http-equiv="Content-Type">
      <br>
      <br>
      <div class="moz-cite-prefix">On Tuesday 05 April 2016 06:07 PM,
        Vikas Tara wrote:<br>
      </div>
      <blockquote cite="mid:5703B184.3040209@hamaralinux.org"
        type="cite">
        <meta content="text/html; charset=utf-8"
          http-equiv="Content-Type">
        <div class="moz-cite-prefix">On 05/04/16 10:00, Raju D V wrote:<br>
        </div>
        <blockquote cite="mid:57037EC4.6040204@openmailbox.org"
          type="cite">
          <meta content="text/html; charset=utf-8"
            http-equiv="Content-Type">
          <br>
          <br>
          <div class="moz-cite-prefix">On Monday 04 April 2016 06:39 PM,
            Vikas Tara wrote:<br>
          </div>
          <blockquote cite="mid:57026778.2080307@hamaralinux.org"
            type="cite">
            <meta content="text/html; charset=utf-8"
              http-equiv="Content-Type">
            <div class="moz-cite-prefix">On 04/04/16 12:29, Raju D V
              wrote:<br>
            </div>
            <blockquote cite="mid:57025026.6060605@openmailbox.org"
              type="cite">
              <meta content="text/html; charset=utf-8"
                http-equiv="Content-Type">
              <Snipped><br>
              <br>
              We have resolved all dependencies of ubiquity.<br>
              But while building the package I am getting these errors.<br>
              <br>
              <a moz-do-not-send="true" id="pasteurl"
href="https://paste.hamaralinux.org/?8a06c8faf08e37ba#7qRiaD4KBs0y+TPNOQqE2hnacYNZ8DJPhbc18vEDA0k=">https://paste.hamaralinux.org/?8a06c8faf08e37ba#7qRiaD4KBs0y+TPNOQqE2hnacYNZ8DJPhbc18vEDA0k=</a><br>
              <br>
              These are being caused by the checks that pep8 package
              runs on the python files. <br>
              There is a long list of error codes being listed there. <br>
              <br>
              I have the description of the error codes listed here <a
                moz-do-not-send="true" class="moz-txt-link-freetext"
                href="http://pep8.readthedocs.org/en/latest/intro.html"><a class="moz-txt-link-freetext" href="http://pep8.readthedocs.org/en/latest/intro.html">http://pep8.readthedocs.org/en/latest/intro.html</a></a><br>
              <br>
              But I am not sure how to resolve them. <br>
              I tried manually editing the particular files, but that
              results in more error codes for the same line. <br>
              Has anyone faced this earlier?<br>
            </blockquote>
            <br>
            This could be to do with version of pep that is in use.<br>
            <br>
            Can you compare the version you are using with the one in
            the ubuntu version that your taking Ubiquity source from?<br>
            <br>
            It's likely that there is a different pep rules set and that
            is causing your issue.<br>
            <br>
          </blockquote>
          <br>
          <tt>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. </tt><tt><br>
          </tt><tt><br>
          </tt><tt>But now the state of errors with different versions
            of ubiquity in different Ubuntu releases are as follows. </tt><tt><br>
          </tt><tt><br>
          </tt><tt>with ubiquity-xenial </tt><tt><br>
          </tt><tt><br>
          </tt><tt>    <a moz-do-not-send="true"
              class="moz-txt-link-freetext"
href="https://paste.hamaralinux.org/?eac6a80e81788fd4#zDq5Qw/ZGoirbX4Ywxnix+XXxE13NfGLKJ9Cpe7zil8=">https://paste.hamaralinux.org/?eac6a80e81788fd4#zDq5Qw/ZGoirbX4Ywxnix+XXxE13NfGLKJ9Cpe7zil8=</a></tt><tt><br>
          </tt><tt><br>
          </tt><tt>with ubiquity-wily </tt><tt><br>
          </tt><tt><br>
          </tt><tt>    </tt><tt><a moz-do-not-send="true" id="pasteurl"
href="https://paste.hamaralinux.org/?a8e52deb317d44e0#I3qDiSsBkAxjUiwj61SfU7wN3csosfono07pFmeJ+kU=">https://paste.hamaralinux.org/?a8e52deb317d44e0#I3qDiSsBkAxjUiwj61SfU7wN3csosfono07pFmeJ+kU=</a></tt><tt><br>
          </tt><tt><br>
          </tt><tt>with ubiquity-vivid</tt><tt><br>
          </tt><tt><br>
          </tt><tt>    <a moz-do-not-send="true"
              class="moz-txt-link-freetext"
href="https://paste.hamaralinux.org/?1fa2820e8f4fafcf#yb8YF7M9sJ81DNiwBCMnEEgVdpYd+fLxX46a+Yaoruo=">https://paste.hamaralinux.org/?1fa2820e8f4fafcf#yb8YF7M9sJ81DNiwBCMnEEgVdpYd+fLxX46a+Yaoruo=</a></tt><tt><br>
          </tt><tt><br>
          </tt><tt>with ubiquity-trusty</tt><tt><br>
          </tt><tt><br>
          </tt><tt>    <a moz-do-not-send="true"
              class="moz-txt-link-freetext"
href="https://paste.hamaralinux.org/?c666daa6d77e8323#yQoh5I6TeBy5vqzqC9kfGShQHH8LvtQWgm6Y+f6X4gM=">https://paste.hamaralinux.org/?c666daa6d77e8323#yQoh5I6TeBy5vqzqC9kfGShQHH8LvtQWgm6Y+f6X4gM=</a></tt><tt><br>
          </tt><tt><br>
          </tt><tt><br>
          </tt><tt><br>
          </tt><tt>Out of all these builds, the problems with xenial,
            wily & vivid have this similar block of errors</tt><br>
          <br>
---------------------------------------------------------------------------<br>
          <pre><code>checking <span class="keyword">for</span> PANEL... no
configure: <span class="keyword">error</span>: Package requirements (glib-<span class="number">2.0</span>
                          gtk+-<span class="number">3.0</span> >= <span class="number">3.1</span><span class="number">.4</span>
                          indicator3-<span class="number">0.4</span> >= <span class="number">12.10</span><span class="number">.2</span>
                          libido3-<span class="number">0.1</span> >= <span class="number">13.10</span><span class="number">.1</span>
                          x11) were <span class="keyword">not</span> met:

Requested 'indicator3-<span class="number">0.4</span> >= <span class="number">12.10</span><span class="number">.2</span>' <span class="keyword">but</span> <span class="property">version</span> <span class="keyword">of</span> libindicator3 <span class="keyword">is</span> <span class="number">0.5</span><span class="number">.0</span>
Requested 'libido3-<span class="number">0.1</span> >= <span class="number">13.10</span><span class="number">.1</span>' <span class="keyword">but</span> <span class="property">version</span> <span class="keyword">of</span> libido <span class="keyword">is</span> <span class="number">0.3</span><span class="number">.4</span>


-------------------------------------------------------------------------

while with Trusty a lot of errors are just because of pep8 tests. 

</code>
</pre>
          <tt> Now I am trying to build the ubuntu specific versions of
            indicator and libido. </tt></blockquote>
        This is great work Raju - well done :)<br>
        <br>
        Personally though - I would work with the trusty packages and
        solve the pep errors. You have successfully done that on other
        ubuntu versions already.<br>
        <br>
        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!<br>
      </blockquote>
      I moved on from trusty  to vivid after seeing these bug reports<br>
      <br>
      <a moz-do-not-send="true" class="moz-txt-link-freetext"
        href="https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=797398">https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=797398</a><br>
      <br>
      <a moz-do-not-send="true" class="moz-txt-link-freetext"
        href="https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1492261">https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1492261</a><br>
      <br>
      They state that they have been resolved in the next releases. <br>
      <br>
      But all the next releases prior to ubuntu are complaining for
      libido and libindicator errors. <br>
      <br>
      I am trying to get libido built. It has a dependency which
      requires specifically gcc-4.7 and g++-4.7<br>
      while these packages are no more in debian. debian has 4.8 and 5</blockquote>
    Try moving back to trusty and working on the pep errors - that
    should get us further<br>
    <br>
  </body>
</html>