Updating Project:KDE:Trunk project on build.pub.meego.com

Maurice de la Ferte Maurice.Ferte at basyskom.com
Fri Mar 9 15:03:45 UTC 2012


 
On March 9, 2012 at 3:45 PM "Lamarque V. Souza" <Lamarque.Souza.ext at basyskom.com> wrote:

> Em Friday 09 March 2012, Maurice de la Ferte escreveu:
> > On March 9, 2012 at 1:43 PM "Lamarque V. Souza"
> <Lamarque.Souza.ext at basyskom.com> wrote:
> > > Em Friday 09 March 2012, Maurice de la Ferte escreveu:
> > > > Hi all,
> > >
> > >         Hi,
> > >
> > >
> > > > at the moment we have a well tested and improved state of Plasma Active
> > > > 2 in our testing project. We like to ship this state into the
> > > > Project:KDE:Trunk project this afternoon which is the package feed of
> > > > our MeeGo/Mer end-user images. We still have some small bugs but users
> > > > in the field will benefit from this update and Mer based images are
> > > > getting possible.
> > >
> > >         Does that also mean users who want to update their PA2
> > >installations can
> > >
> > > point zypper to Project:KDE:Trunk repo and trigger the update?
> >
>> > This depends on the installation image, in case a "demo" or "stable release
> > image" was taken (e.g.
> > http://share.basyskom.com/contour/Deployment/latest-meego-plasma-active-st
> > able.html) zypper is pointing to the Project:KDE:Trunk OBS project and will
> > get those updates by just "zypper up" in a few hours.
>
>         Good that is what I wanted to know.
>   
> > In case you have a "Testing" image installation zypper is pointing to
> > Project:KDE:Trunk:Testing OBS project, which is the gate for updates on
> > "Project:KDE:Trunk". This means it does not make sense to add the
> > 'Project:KDE:Trunk' repo because the updates are allready available.
> > For some more background about the purpose of different images please see:
> > http://mail.kde.org/pipermail/active/2011-October/001440.html
>> > I hope this will clearify it a bit.
>
>         Yes, it does. The name "Trunk" in Project:KDE:Trunk is misleading
> though. In subversion jargon trunk is the development branch but by the e-mail
> above Project:KDE:Trunk is the stable version, Project:KDE:Devel is the
> development version (this one makes sense) and Project:KDE:Trunk:Testing is
> the intermediate version (the yet to be Project:KDE:Trunk).
>
> --
 
Yes this name is misleading but this a adaption of a common MeeGo project setup.
Please note, to get the new security features running there is a additional command
after updating needed:

    root at device# echo "modprobe fuse" >> /etc/rc.local
 
This makes sure needed kernel modules get loaded at boot-up.



More information about the Active mailing list