[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-active
Subject:    Re: When will PA Devel repos upgrade to 4.11?
From:       Jan Grulich <jgrulich () redhat ! com>
Date:       2013-07-11 18:50:53
Message-ID: 51DEFE8D.6030005 () redhat ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


Dne 11.7.2013 20:33, Hillel Lubman napsal(a):
> Did anyone manage to run devel PA on Nexus 7 recently? Making current 
> upgrades (using devel repos) always ends up in unusable system for me 
> (PA comes up, but UI is completely frozen and there are segfaults 
> before it loads).
> 
> Regards,
> 
> Hillel.
> 
I have PA on my Nexus 7 (using [1] tarball) and I updated yesterday from 
devel repositories and everything seems to be okay. But I'm always 
scared (I don't know whether it will work after restart or not) when 
doing updates. Do you use MultiBoot or you have only PA on your Nexus 7? 
Because I would like to figure out how to install the latest tarball as 
a second system to my Nexus 7. It worked with some old image but I'm not 
able to make it work with [1] for example.

[1] 
http://files.kde.org/plasma/active/3.0/images/nexus7/plasma-active-armv7hl-google-nexus7-devel-2013-07-06.tar.gz


Jan


> 
> On Thu, Jul 11, 2013 at 2:29 PM, Thomas Pfeiffer 
> <colomar@autistici.org <mailto:colomar@autistici.org>> wrote:
> 
> Hi everyone (and especially Marco),
> are there already plans for when to switch the PA Devel repos to
> Plasma
> Workspaces 4.11? Any rough estimations for when this might happen?
> 
> Background:
> The KMail Active GSoC project currently faces a problem: Our
> prototype needs
> some improvements in the Plasma Components that are not yet
> available in the
> 4.10 version. Therefore Mike has created some patched 4.10
> packages in order
> to make it work on the PA Devel images. However, there seem to be some
> incompatibilities which render the prototype (along with most of
> PA) pretty
> much useless (I get the error "This object could not be created
> for the
> following reason: Could not create a declarativeappletscript
> ScriptEngine for
> the Active Mail Prototype Widget" and the same for other Plasmoids
> as well).
> 
> With 4.11, we wouldn't face that problem. Now the question is
> whether it's
> worth the effort for Mike to fix his patched packages or whether
> we should just
> wait for 4.11 to hit the Devel repos.
> 
> Thanks,
> Thomas
> _______________________________________________
> Active mailing list
> Active@kde.org <mailto:Active@kde.org>
> https://mail.kde.org/mailman/listinfo/active
> 
> 
> 
> 
> _______________________________________________
> Active mailing list
> Active@kde.org
> https://mail.kde.org/mailman/listinfo/active


-- 
Jan Grulich
Red Hat Czech, s.r.o
jgrulich@redhat.com


[Attachment #5 (text/html)]

<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix">Dne 11.7.2013 20:33, Hillel Lubman
      napsal(a):<br>
    </div>
    <blockquote
cite="mid:CAPh=7Pqi0412Yi5z8GdZBnHY03UUgsdh5grywJST+-g65p0u_g@mail.gmail.com"
      type="cite">
      <div dir="ltr">Did anyone manage to run devel PA on Nexus 7
        recently? Making current upgrades (using devel repos) always
        ends up in unusable system for me (PA comes up, but UI is
        completely frozen and there are segfaults before it loads).<br>
        <br>
        Regards,<br>
        <br>
        Hillel.<br>
      </div>
      <div class="gmail_extra"><br>
      </div>
    </blockquote>
    I have PA on my Nexus 7 (using [1] tarball) and I updated yesterday
    from devel repositories and everything seems to be okay. But I'm
    always scared (I don't know whether it will work after restart or
    not) when doing updates. Do you use MultiBoot or you have only PA on
    your Nexus 7? Because I would like to figure out how to install the
    latest tarball as a second system to my Nexus 7. It worked with some
    old image but I'm not able to make it work with [1] for example.<br>
    <br>
    [1]
<a class="moz-txt-link-freetext" \
href="http://files.kde.org/plasma/active/3.0/images/nexus7/plasma-active-armv7hl-googl \
e-nexus7-devel-2013-07-06.tar.gz">http://files.kde.org/plasma/active/3.0/images/nexus7/plasma-active-armv7hl-google-nexus7-devel-2013-07-06.tar.gz</a><br>
  <br>
    Jan<br>
    <br>
    <br>
    <blockquote
cite="mid:CAPh=7Pqi0412Yi5z8GdZBnHY03UUgsdh5grywJST+-g65p0u_g@mail.gmail.com"
      type="cite">
      <div class="gmail_extra"><br>
        <div class="gmail_quote">On Thu, Jul 11, 2013 at 2:29 PM, Thomas
          Pfeiffer <span dir="ltr">&lt;<a moz-do-not-send="true"
              href="mailto:colomar@autistici.org" \
target="_blank">colomar@autistici.org</a>&gt;</span>  wrote:<br>
          <blockquote class="gmail_quote" style="margin:0 0 0
            .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi
            everyone (and especially Marco),<br>
            are there already plans for when to switch the PA Devel
            repos to Plasma<br>
            Workspaces 4.11? Any rough estimations for when this might
            happen?<br>
            <br>
            Background:<br>
            The KMail Active GSoC project currently faces a problem: Our
            prototype needs<br>
            some improvements in the Plasma Components that are not yet
            available in the<br>
            4.10 version. Therefore Mike has created some patched 4.10
            packages in order<br>
            to make it work on the PA Devel images. However, there seem
            to be some<br>
            incompatibilities which render the prototype (along with
            most of PA) pretty<br>
            much useless (I get the error "This object could not be
            created for the<br>
            following reason: Could not create a declarativeappletscript
            ScriptEngine for<br>
            the Active Mail Prototype Widget" and the same for other
            Plasmoids as well).<br>
            <br>
            With 4.11, we wouldn't face that problem. Now the question
            is whether it's<br>
            worth the effort for Mike to fix his patched packages or
            whether we should just<br>
            wait for 4.11 to hit the Devel repos.<br>
            <br>
            Thanks,<br>
            Thomas<br>
            _______________________________________________<br>
            Active mailing list<br>
            <a moz-do-not-send="true" \
href="mailto:Active@kde.org">Active@kde.org</a><br>  <a moz-do-not-send="true"
              href="https://mail.kde.org/mailman/listinfo/active"
              target="_blank">https://mail.kde.org/mailman/listinfo/active</a><br>
          </blockquote>
        </div>
        <br>
      </div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
Active mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Active@kde.org">Active@kde.org</a>
<a class="moz-txt-link-freetext" \
href="https://mail.kde.org/mailman/listinfo/active">https://mail.kde.org/mailman/listinfo/active</a>
 </pre>
    </blockquote>
    <br>
    <br>
    <pre class="moz-signature" cols="72">-- 
Jan Grulich 
Red Hat Czech, s.r.o
<a class="moz-txt-link-abbreviated" \
href="mailto:jgrulich@redhat.com">jgrulich@redhat.com</a></pre>  </body>
</html>



_______________________________________________
Active mailing list
Active@kde.org
https://mail.kde.org/mailman/listinfo/active


[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic