Re: Enabling UMTS on Archos G9 in Plasma Active

[Maurice de la Ferte]

Jean Hi, 

On October 29, 2012 at 2:41 PM Jean Cayron  wrote:

> Maurice,
> 2012/10/26 Maurice de la Ferte 
>
> > Hi all,
> >
> > we added 3G/UMTS support to our latest Archos Gen9 Plasma Active devel and
> > testing images.
> > Great thanks to Ruediger Gad who did this work and also published accurate
> > dokumentation
> > about on
> > http://ruedigergad.com/2012/10/07/enabling-umts-on-archos-g9-in-plasma-active/#more-566
> >
> > Latest weekly Testing and Devel images should already contain all needed
> > parts to get the external
> > Archos 3G UMTS stick running out of the box:
> >
> You said in the past that testing image was not maintained, that one should
> test with devel image. Is it still the case?
 
No, we did some work on testing image definitions and project setup, by this
the testing project contains the release state plus few handpicked 
updates/fixes.
Also the testing project is building on top of the same frozen Mer version
we took for the release, so it is a qualified staging project for updates in
the field.

 
Sadly to project setup with Mer, Nemo and hardware adaptions is a bit
confusing. But the changes releated to Archos 3G UMTS support taking only
place inside the hardware adaption projects and are available for the
devel and testing images (also pvr is affected). The build and publishing
of Archos hardware adaption rpms for the release image is disabled at the
moment till we agree to ship it.
 
>
> And what about the hardware acceleration of Archos G9, as it improved? Is
> there someone working on it? In other words, does it worth to try the pvr
> image again?
 
At the moment no one is working on Archos G9 hardware adaption with pvr.
But I added the 3G support in the same way like for omapfb. The screensaver
and powerdevil support is still disabled by 
'plasma-mobile-config-archos-gen9-pvr'
package.
 
Cheers,
 
Maurice

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

Enabling UMTS on Archos G9 in Plasma Active

[Maurice de la Ferte]

Hi all,

we added 3G/UMTS support to our latest Archos Gen9 Plasma Active devel and 
testing images.
Great thanks to Ruediger Gad who did this work and also published accurate 
dokumentation
about on 
http://ruedigergad.com/2012/10/07/enabling-umts-on-archos-g9-in-plasma-active/#more-566

Latest weekly Testing and Devel images should already contain all needed parts 
to get the external
Archos 3G UMTS stick running out of the box:

http://share.basyskom.com/plasma-active/archos_gen9.html

Also If you like to try it out on a previous installed release image, just do 
following
steps in 'Konsole' application:

mer@device# su
root@device# zypper ar -f 
http://repo.pub.meego.com/Project:/KDE:/Mer_Extras:/Adaptation:/Archos-gen9/Project_KDE_Trunk_Testing_0.20120816.1_armv7l/
 Archos_gen9_testing
root@device# zypper refresh
root@device# zypper up

Please note, a kernel update to the flash is mandatory to get the 3G/UMTS 
support working.

Sadly for lack of this stick I'm not able to verify it on my own, but I cannot 
find any regressions
yet. Feedback would be very nice, so we can make this update available to 
release image repository.

Cheers,

Maurice

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

Continuous Integration Status on Mer PA Development Project

[Maurice de la Ferte]

Hi all,

here a short overview of our CI Status pointing to Mer PA Development Project.
Feedback about needed changes would be nice:

Status
-
Repository URL
Branch

CI disabled
bangarang-2.2+
https://git.gitorious.org/bangarang/bangarang.git
master

CI disabled
calligra-2.6~alpha0
git://anongit.kde.org/calligra
master

CI enabled
contour-0.1.3~
git://anongit.kde.org/contour
master

CI enabled
declarative-plasmoids-4.10~
git://anongit.kde.org/declarative-plasmoids
master

CI enabled
kde-runtime-4.9.0+
git://anongit.kde.org/kde-runtime
remotes/origin/KDE/4.9

CI enabled
kde-workspace-4.9.0+
git://anongit.kde.org/kde-workspace
remotes/origin/KDE/4.9

CI disabled
kdelibs-4.9.0+
git://anongit.kde.org/kdelibs
remotes/origin/KDE/4.9

CI disabled
kdepim-4.9.0+
git://anongit.kde.org/kdepim
master

CI disabled
kdepim-runtime-4.9.0+
git://anongit.kde.org/kdepim-runtime
master

CI disabled
kdepimlibs-4.9.0+
git://anongit.kde.org/kdepimlibs
master

CI enabled
libkactivities-6.3~
git://anongit.kde.org/kactivities
remotes/origin/KDE/4.9

CI enabled
maliit-active-0.1+
git://anongit.kde.org/plasma-active-maliit
master

CI disabled
nepomuk-core-4.9.0+
git://anongit.kde.org/nepomuk-core
master

CI enabled
okular-4.8.2+
git://anongit.kde.org/okular
remotes/origin/mart/okularActive

CI enabled
plasma-addons-4.9.0+
git://anongit.kde.org/kdeplasma-addons
master

CI enabled
plasma-mobile-0.4~
git://anongit.kde.org/plasma-mobile
master

CI enabled
plasma-mobile-config-archos-gen9-0.2.15+
git://anongit.kde.org/plasma-mobile-config
remotes/origin/archos-gen9

CI enabled
plasma-mobile-config-archos-gen9-pvr-0.2.15+
git://anongit.kde.org/plasma-mobile-config
remotes/origin/archos-gen9-pvr

CI enabled
plasma-mobile-config-default-0.2.15+
git://anongit.kde.org/plasma-mobile-config
master

CI enabled
plasma-mobile-config-vivaldi-0.2.15+
git://anongit.kde.org/plasma-mobile-config
remotes/origin/vivaldi

CI enabled
share-like-connect-0.3~
git://anongit.kde.org/share-like-connect
master

CI disabled
shared-desktop-ontologies-0.10.0+
git://oscaf.git.sourceforge.net/gitroot/oscaf/shared-desktop-ontologies
master

CI enabled
startactive-0.2+
git://anongit.kde.org/startactive
master

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

Re: Reopening development

[Maurice de la Ferte]

 

On October 16, 2012 at 12:39 PM Marco Martin  wrote:

> On Tuesday 16 October 2012, Maurice de la Ferte wrote:
> > Marco hi,
> > 
> > in my opinion we should clean up the changes files inside OBS
> > before. This means dropping all automatically CI entries till last
> > release. I would suggest a replacement by an qualified changelog
> > entry, but sadly have no time to do it on my own.
> > So far I know the osc commands like 'osc commit' get stuck
> > very often when the changes files are too big.
>
> do you mean clearing completely the changes generated bi CI? maybe can be done
> by a script?
 
Yes, just keeping the human entries like the example for plasma-mobile changes 
below:

* Wed Oct 10 2012 Maurice de la Ferté  - 
0.4~git20121010.114153
- Plasma Active Three release
- Add workaround to get buttons on e.g. archos gen9 on some panels resposive 
again
  https://bugs.kde.org/show_bug.cgi?id=304875
- Remove unneeded requires and specific spec files
- Repository URL: git://anongit.kde.org/plasma-mobile
- Branch:  master
- Commit ID: d9926d250ac1f141572d0e9f904380b575dd59bb

* Tue Dec 13 2011 Javier Llorente  - 0.3
- Repository URL: git://anongit.kde.org/plasma-mobile
- Branch:  master
- Commit ID: 4fab06881388c658553afad27ff61a784aacfcc1

* Fri Oct 07 2011 Javier Llorente  - 0.2
- Repository URL: git://anongit.kde.org/plasma-mobile
- Branch:  Active/1.0
- Commit ID: 81df1de08a08cfc9ae32d8916762a6fc255d1bb3

 
It should be possible by script, but I strongly recommend to do it by hand.
Also it is very interesting for me to increase the version number of CI 
autoversion
of e.g. plasma-mobile from 0.4~ to 0.4+. I would prefer to
have real 0.4 package in between but do not have the time to do it.
 
Cheers,
 
Maurice

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

Re: Reopening development

[Maurice de la Ferte]

Marco hi,
 
in my opinion we should clean up the changes files inside OBS
before. This means dropping all automatically CI entries till last
release. I would suggest a replacement by an qualified changelog
entry, but sadly have no time to do it on my own.
So far I know the osc commands like 'osc commit' get stuck
very often when the changes files are too big.
Please drop me a line when I should switch CI to other branches.
 
Cheers
 
Maurice 

On October 16, 2012 at 12:21 PM Marco Martin  wrote:

> Hi all,
> this week i want to reopen features development in master of plasma-mobile,
> contour, sharelikeconnect and whatnot.
>
> so this will mean merging some branches that are hanging around since some
> time that require master of kde-runtime and nepomuk-core
> (this also means continuous integration on the Devel project will go on
> master, could be put on 4.9 branches on the Testing project if really needed)
>
> so, any strong opinions on this?
>
> Cheers,
> Marco Martin
> ___
> Active mailing list
> Active@kde.org
> https://mail.kde.org/mailman/listinfo/active
>
--
Maurice S. de la Ferté

basysKom GmbH
Südwestpark 108 | 90449 Nürnberg | Germany
Tel: +49 911 689 367 - 0 | Fax: +49 911 689 367 - 299
maurice.fe...@basyskom.com  | www.basyskom.com

Handelsregister: Darmstadt HRB 9352 | Sitz: Darmstadt
Geschäftsführung: Dr.-Ing. Eva Brucherseifer, Heike Ziegler

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

Re: Upgrading from RC4 to Release 3

[Maurice de la Ferte]

David hi, 

On October 15, 2012 at 9:27 PM David Talmage  wrote:

> Just last night I installed Plasma Active 3 RC4 on my WeTab. This morning, you
> fine people made the official release!  To upgrade, must I use the USB stick
> again?  Is 'zypper refresh ; zypper update' sufficient? I did that this 
> morning
> and it upgraded only four packages: okular-active, okular-corelib, plasma-
> mobile-config-default, and plasma-mobile-config-default-blacklist.
 
Yes, by 'zypper refresh ; zypper update' you are on the same revisions as the 
official
PA3 release. The rc images and the final release are using the same rpm 
repositories.
 
Cheers,
 
Maurice

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

Re: Installation of PA3

[Maurice de la Ferte]

Thomas Hi, 

On October 15, 2012 at 8:34 PM Thomas Pfeiffer  wrote:

> > Following steps should work from Plasma Active live mode:
> >
> > su
> > export PATH=${PATH}:/sbin:/usr/sbin
> > installer-shell
>
> Oh, that would work? So we should put that on the installation Wiki page then,
> as having to attach a USB keyboard for installation may really be an obstacle
> for some people (for example those who use only a laptop and don't even own a
> USB keyboard anymore).
 

Yes, it works and I already added this to 
http://share.basyskom.com/plasma-active/wetab.html
 
Cheers,
 
Maurice

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

Re: Installation of PA3

[Maurice de la Ferte]

Wolfgang hi, 

On October 15, 2012 at 2:28 PM Wolfgang Romey  wrote:

> Hallo, I am a long time KDE-user on Debian Sid and have Plasma-Active on my
> weTab for some time, from wich I kicked the original OS. I have testet the
> meego and mer weekly builds from basykom and the latest iso from balsam.
 
First I like to point out, the MeeGo based image are outdated and not supported
anymore.
 
>
> Now I have installed PA3 and maybe it is interesting for you, when I give
> feedback. But first, I want to thank you all for the great work. I hope, there
> will be hardware soon.
>
> The first thing, I want to make a remark on, is the installer. Is there a way,
> to get PA3 installed, without a usb-keybord? I think, that is importeant for
> the normal user.
 
Following steps should work from Plasma Active live mode:
 
su
export PATH=${PATH}:/sbin:/usr/sbin
installer-shell
 
>
> By the way, what is the diffrence between the iso from 14.10.2012 and the
> iso.1 from 15.10.2012?
 
There was no difference and the already removed .1 files are
unneeded dublicated artifacts.
 
Great thanks for your feedback!
 
Cheers,
 
Maurice
 

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

Re: rc4

[Maurice de la Ferte]

On October 11, 2012 at 8:37 PM Yannick Kiekens  wrote:

> Is there an archos gen9 RC4 image?
 
 
sorry upload fail, but here it is:
http://share.basyskom.com/plasma-active/deployment/archos-gen9/tablet/mer/testing/
 
>
> Bug reports mention an RC3 image but i can't find it here:
> http://share.basyskom.com/plasma-active/deployment/archos-gen9/
> There's only the weekly images
>
> Yannick Kiekens
>
> On Thu, Oct 11, 2012 at 6:56 PM, Marco Martin  wrote:
>
> > http://share.basyskom.com/plasma-active/deployment/wetab-
> > exopc/tablet/mer/testing/
> >
> > reasons to delay further must be very, very valid :p
> >
> > --
> > Marco Martin
> > ___
> > Active mailing list
> > Active@kde.org
> > https://mail.kde.org/mailman/listinfo/active
> >
--
Maurice S. de la Ferté

basysKom GmbH
Südwestpark 108 | 90449 Nürnberg | Germany
Tel: +49 911 689 367 - 0 | Fax: +49 911 689 367 - 299
maurice.fe...@basyskom.com  | www.basyskom.com

Handelsregister: Darmstadt HRB 9352 | Sitz: Darmstadt
Geschäftsführung: Dr.-Ing. Eva Brucherseifer, Heike Ziegler

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

Re: wetab install

[Maurice de la Ferte]

Hi, 

On October 8, 2012 at 12:31 PM "Sebastian Kügler"  wrote:

> On Saturday, October 06, 2012 17:05:21 Nicola De Filippo wrote:
> > i suggest to add this line
> > "root@linux printf "\x9d\x2a\x44\x7b"|dd of=/dev/sdX bs=1 count=4 seek=440"
> > to  the instructions to  install mer image on wetab.
>
> For mere mortals, what does this do?
>
> (It's always a good idea to note that, since not everybody in a multi-
> disciplinary team has the same domain knowledge.)
 
this command modifies the ID inside the partition table.
This kind of hack is needed because a WeTab without patched
bios do only like to start from a internal recovery partition
after using the recovery grip. This hex number is the identifier
of the internal recovery partition and by this we are able to
install from a external flash drive.
 
Cheers,
 
Maurice

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

Re: wetab install

[Maurice de la Ferte]

Hi,
 
On October 6, 2012 at 5:05 PM Nicola De Filippo  
wrote:

> Hi,
> i suggest to add this line
> "root@linux printf "\x9d\x2a\x44\x7b"|dd of=/dev/sdX bs=1 count=4 seek=440" to
> the instructions to  install mer image on wetab.
  [http://dict.leo.org/ende?lp=ende&p=_xpAA&search=shouldn%27t&trestr=0x8040] 
shouldn't be necessary for basysKom Mer/MeeGo based Wetab/ExoPC images.
Those image are already affected by a
'printf "\x9d\x2a\x44\x7b" | dd of=${IMAGE} bs=1 count=4 seek=440 conv=notrunc'
 
But a useful hint for others.
 
Cheers
 
Maurice

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

Re: Release candidate image

[Maurice de la Ferte]

Hi all,
 
this Plasma Actice 3 Mer based release candidate image for WeTab / EXOPC is
pubished on following URL:
 
http://share.basyskom.com/plasma-active/deployment/wetab-exopc/tablet/mer/testing/

Thanks for testing,
 
Maurice
 
On October 4, 2012 at 4:43 PM Marco Martin  wrote:

> Hi all,
>
> here is an image for x86 from the "stable" repos, those we want to use for the
> release (ie, any zypper up shouldn't explode on your face :p)
>
> http://share.basyskom.com/plasma-active/deployment/wetab-
> exopc/tablet/mer/stable/
>
> (thanks Maurice for taking care of this ;)
> please give it a try to see if there is still something broken.
>
> I'm more looking for macro problems like crashes, powermanagement issues,
> stuff not starting, apps missing etc.
> code-wise there shouldn't be more updates if something very serious doesn't
> surface
>
> Cheers,
> Marco Martin
> ___
> Active mailing list
> Active@kde.org
> https://mail.kde.org/mailman/listinfo/active
>
--
Maurice S. de la Ferté

basysKom GmbH
Südwestpark 108 | 90449 Nürnberg | Germany
Tel: +49 911 689 367 - 0 | Fax: +49 911 689 367 - 299
maurice.fe...@basyskom.com  | www.basyskom.com

Handelsregister: Darmstadt HRB 9352 | Sitz: Darmstadt
Geschäftsführung: Dr.-Ing. Eva Brucherseifer, Heike Ziegler

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

Re: Plasma Active 3

[Maurice de la Ferte]

Hi, 

On September 9, 2012 at 7:37 PM Marco Martin  wrote:

> On Sunday 09 September 2012, Nicola De Filippo wrote:
> > Hi,
> >
> > > On Tuesday 04 September 2012, Marco Martin wrote:
> > > > On Thursday 30 August 2012, Marco Martin wrote:
> > > > > on more pr side, announcement material:
> > > > > * list of some features
> > > > > * announcement and dot articles
> > > > > * tons of screenshots
> > > > > * video (can give a try, but i don't have cameras that shoot decent
> > > > > high res video, so anybody with a decent camera is welcome to do so)
> > > >
> > > > this is a fisrst quick video:
> > > > http://www.youtube.com/watch?v=J0JJUTIEcAI
> > >
> > > with some touches based on comments:
> > > http://www.youtube.com/watch?v=_kopxlYA6Bk
> >
> > beatifull!! Where is the image? I want try on my wetab!
> >               Nicola
>
> you can try
> http://www.notmart.org/basyskom-plasma-active-devel-mer-usb-live-x86.usbimg
>
> (meh, i hope we can have weekly automatic images soon)
  ^
 
http://share.basyskom.com/plasma-active/wetab.html --> "Development Mer Image" 
does not work?
 
Cheers,

Maurice

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

Re: issues with latest mer release

[Maurice de la Ferte]

Hi all, 

On August 10, 2012 at 7:29 PM Marco Martin  wrote:

> Hi all,
> last tuesday there was a release of mer core, so, now obs build against it.
>
> unfortunately it seems to break the x86 generic adaption, live usb images
> won't boot correctly anymore, this is due to the merge of udev inside systemd
> (i think)
>
> this means the next auto generated plasma active devel images won't work
>
>
> the devices under /dev won't be created, so it's unable to mount the root
> filesystem and finish the boot.
>
> iirc there was some work on a fix at
> https://build.pub.meego.com/project/show?project=home%3Asage%3Amer%3Ax86-fix
>
> unfortunately doesn't seem to work, it still can't create the devices.
> during the image creation it was also still complaining of some not found
> exectuables, suck as insmod, modprobe etc.
> i fixed that in a branch there
> https://build.pub.meego.com/package/show?package=mkinitrd&project=home%3Amart%3Abranches%3Ahome%3Asage%3Amer%3Ax86-
> fix
>
> but the main problem still persists. does anybody have any idea about it?
> 
 
After comparing the package lists between last week and current images, I
found out package 'MAKEDEV' is missing on current PA Mer devel Image. So
it looks like a package group was changed or a dependency got lost.
 
Cheers,
 
Maurice

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

Re: Trouble with archos image

[Maurice de la Ferte]

Yannick Hi,
 

On August 8, 2012 at 8:16 PM Yannick Kiekens  wrote:

> >
> >
> > 1) Activity switcher does not work by strange side effects of pvr driver,
> > the activity switcher
> >    on omapfb image works fine.
> >
> > 2) Power-management was disabled on pvr image as work around to prevent
> > trouble after suspend.
> >    On omapfb image the power-management is working.
> >
> >
>
> I did test the omapfb image:
>
> 1) the activity switcher showed activities, but adding an activity or
> changing the settings of the existing activities locked up the activity
> edit screen
> 2) omapfb image got stuck in a loop: it said it wanted to lock the screen,
> but went to sleep state instead. No way to get out the cycle. Reinstalling
> the image and trying to locking/sleep these things in active settings
> didn't work.
>
> As I am trying to develop an active app, i prefer the pvr image, no power
> management is better than malfunctioning power management. But these issues
> should be discussed in a bugtracker.
>
> What I really want to say here is:
> bugs.kde.org is rather overwhelming for someone not involved. And I really
> want to get involved getting such issues revloved. I work with Qt on debian
> x86 at work. Some good documentation and/or guidance should get me going.
 
the kde lockscreen issue you are describing sounds exactly like the reason
why we disabled the Power-management for pvr. Please make sure you are using
the image related 'zImage-for-omapfb-rootfs-on-' kernel deployed it into
'zImage' renamed by the Archos SDE. Sorry if the howto point not out that you
cannot mix pvr/omapfb kernel and root filesystem, but with the right zImage
it should work.

I can confirm the that the 'Edit Activity' or 'Add Resources' will get stuck on
basyskom-plasma-active-archos-gen9-omapfb-tablet-mer-devel-120805-1800.tar.bz2
image. It would be very nice if you could file a bug about to:

Bug Tracker URL: https://bugs.kde.org/
Product: Active
Component: General
Hardware Platform: MeeGo/Harmattan
Operating System: Linux

Also please add the image name which you are using to the Details section.

Please note, the Plasma Active Mer images are build from parts which are
maintained by three different communities (Plasma Active, Neno and Mer).
Sometimes it is a bit hard to address a bug to the right place, so its
always a good idea to get in contact with the active people on #active
channel before filing.

Great thanks for your feedback and help to get Plasma Active stabilized.
Your help is very welcome!

Cheers,

Maurice


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

Re: Proposal: Plasma Active Three end of August

[Maurice de la Ferte]

Yannick Hi,

> My archos G9 is currently running the pvr image from last sunday 12/08
> I'd love to help test if there is some sort of testplan, otherwise i could
> need some help writing better bug-reports besides:
>
> 1) Activity switcher doesn't work &
> 2) power-management doesn't work
 
 
1) Activity switcher does not work by strange side effects of pvr driver, the 
activity switcher
   on omapfb image works fine.
 
2) Power-management was disabled on pvr image as work around to prevent trouble 
after suspend.
   On omapfb image the power-management is working.
 
 
Cheers,
 
Maurice 
 
--
Maurice S. de la Ferté

basysKom GmbH
Südwestpark 108 | 90449 Nürnberg | Germany
Tel: +49 911 689 367 - 0 | Fax: +49 911 689 367 - 299
maurice.fe...@basyskom.com  | www.basyskom.com

Handelsregister: Darmstadt HRB 9352 | Sitz: Darmstadt
Geschäftsführung: Dr.-Ing. Eva Brucherseifer, Heike Ziegler

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

Weekly Plasma Active images

[Maurice de la Ferte]

Hi all,

we at basysKom setup weekly image builds for following image types:

KDE Plasma Active Mer based testing USB/DVD/CD live x86 live and install image
KDE Plasma Active Mer based development USB/DVD/CD live x86 live and install 
image
KDE Plasma Active next Mer preview development USB/DVD/CD live x86 live and 
install image
KDE Plasma Active MeeGo based testing USB/DVD/CD live x86 live and install image
KDE Plasma Active MeeGo based development USB/DVD/CD live x86 live and install 
image
KDE Plasma Active Mer based Archos gen9 development root filesystem tarball 
(without hardware acceleration)
KDE Plasma Active Mer based Archos gen9 testing root filesystem tarball 
(without hardware acceleration)
KDE Plasma Active Mer based Archos gen9 development root filesystem tarball 
(with hardware acceleration, but less stable)
KDE Plasma Active Mer based Archos gen9 testing root filesystem tarball (with 
hardware acceleration, but less stable)

Those images will be build weekly at Friday and Sunday evening automatically 
and can be customized
by the related kickstart files stored inside 'legacy-kickstarts' directory of 
following repository:

URL: git://anongit.kde.org/plasma-active-kickstart
Branch: master

Please note, all images are available at our new download area on:

http://share.basyskom.com/plasma-active/

The Plasma Active Installation Wiki was already updated. Please do not wonder, 
the old
download area 'http://share.basyskom.com/contour/Deployment/' will be removed 
soon.

Cheers and have fun,

Maurice

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

Re: INFO: New x86 Mer Plasma Active "Devel" Live Image is Available

[Maurice de la Ferte]

Sascha Hi,
 
this repository contain the image build descriptions for Plasma Active Mer
images.

Cheers

Maurice 

On July 23, 2012 at 6:37 PM Sascha Manns  wrote:

> Hello Maurice, hello List,
>
> Hudson Daemon wrote at Montag, 23. Juli 2012, 17:59:58:
> > Repo URL:  git://anongit.kde.org/plasma-active-kickstart
> Just a question. What exactly is plasma-active-kickstart?
> --
> Sincerly yours
> Sascha Manns
> Community & Support Agent /
> Balsam Plasma Active Developer open-slx GmbH
> Web (business): http://www.open-slx.com
> Web (private): http://saigkill.homelinux.net
> ___
> Active mailing list
> Active@kde.org
> https://mail.kde.org/mailman/listinfo/active
>

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

Weekly Mer based x86 Plasma Active Images

[Maurice de la Ferte]

Hi all,

by now we are building and publishing x86 Mer images on every friday evening.
If you like to modify the image layout or package setup, you can easly do it
by changing the related kickstart file in following repository:

Repo URL:  git://anongit.kde.org/plasma-active-kickstart
Branch: master
File: legacy-kickstarts/basyskom-plasma-active-devel-mer-usb-live-x86.ks (devel 
image)
File: legacy-kickstarts/basyskom-plasma-active-testing-mer-usb-live-x86.ks 
(testing image)

In case of an broken image build you will also get informed on this list with 
containing
build log. Sadly the testing image build is broken by missing dependencies. So 
far I see
NetworkManager-kde on Project:KDE:Trunk:Testing needs to be updated from 
Project:KDE:Devel.

Sadly my time for Plasma Active is very restricted, so if you like to take over 
some
responsibilities for system integration and packaging, please do not hesitate 
to contact
me.

Cheers

Maurice

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

Status of Continous Integration on build.pub.meego.com

[Maurice de la Ferte]

Hi all,

here a shot overview of current continous integration of Project:KDE:Devel
on build.pub.meego.com.

Enabled Continous Integration
-
declarative-plasmoids: Branch master
kde-runtime: Branch master
kde-workspace: Branch Active/2.1
okular: mart/okularActive
libkactivities: Branch master
contour: Branch master
plasma-addons: Branch master
plasma-mobile-config-default: Repo plasma-mobile-config, Branch master
plasma-mobile-config-meego: Repo plasma-mobile-config, Branch meego
plasma-mobile-config-vivaldi: Repo plasma-mobile-config, Branch vivaldi
plasma-mobile: Branch Active/2.1
share-like-connect: Branch master
startactive: Branch master

Disabled Continous Integration
--
bangarang: repo https://git.gitorious.org/bangarang/bangarang.git, Branch master
calligra: Branch master
kdelibs: Branch KDE/4.8 (with huge patch created between KDE/4.8 and 
ivan/plasma-active-patches branch)
kdepim: Branch master
kdepim-runtime: Branch master
kdepimlibs: Branch master
nepomuk-core: Branch master
shared-desktop-ontologies: Branch master


Cheers

Maurice

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

Re: Maliit, Plasma Active and Mer

[Maurice de la Ferte]

Thomas Hi,
 
could you try to remove /home/mer/.kde and a reboot afterwards?
 
Cheers
 
Maurice 

On May 23, 2012 at 8:48 PM Thomas Pfeiffer  wrote:

> On Monday 21 May 2012 19:26:08 Marco Martin wrote:
>
> I updated my Meego Devel image today, it installed Maliit & Co but the
> keyboard does not show up. Do I need to change a config file or do something
> else for it to work?
> ___
> Active mailing list
> Active@kde.org
> https://mail.kde.org/mailman/listinfo/active
>
--
Maurice S. de la Ferté

basysKom GmbH
Südwestpark 108 | 90449 Nürnberg | Germany
Tel: +49 911 689 367 - 0 | Fax: +49 911 689 367 - 299
maurice.fe...@basyskom.com  | www.basyskom.com

Handelsregister: Darmstadt HRB 9352 | Sitz: Darmstadt
Geschäftsführung: Dr.-Ing. Eva Brucherseifer

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

Re: GCC versions

[Maurice de la Ferte]

Hi, 

On May 4, 2012 at 10:38 AM Ivan Cukic  wrote:

> Hi all,
>
> Can you please specify here which compiler versions are used in our various
> images - balsam, mer...
 
mer --> gcc-4.6.3
meego --> gcc-4.5.1
 
>
> As far as I have seen, the meego image is 4.5.something.
>
> I'm asking because for after 4.9, I'm planning to require more modern
> compilers (4.6 like Qt5 will require, or unlikely even 4.7) for stuff like
> kamd, contourd etc.
 
Latest Mer-Next release already contain some qt5 (alfa) packages:
 
http://releases.merproject.org/releases/0.20120517.0.0.1/builds/i586/packages/i586/
 
Or see https://build.pub.meego.com/project/packages?project=Mer%3AQt5%3ADevel
 
cheers
 
Maurice

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

Re: Questions about building plasma active

[Maurice de la Ferte]

Jonathan Hi,
 
first I like to point out that the our basyskom tegra2 images are part
of a early hardware evaluation for Plasma Active development purpose.
Those images are outdated and unsupported.
 
On April 28, 2012 at 5:01 AM Jonathan Schultz  wrote:

> Hello folks,
>
> I've just discovered this project so please bear with me if I ask
> questions to which the answers are already out there.
>
> I've just been trying to install KDE Active on a Motorola Xoom, which is
> a Tegra 2 device. The basyskom install scripts don't seem to work, but I
> was able to flash the boot image and install the filesystem on an SD
> card as per the directions. When I booted nothing happened. :(
> Literally, no messages, nothing.
>
> But I have been able to install Debian and KDE/netbook using this
> information: http://forum.xda-developers.com/showthread.php?t=1192639
>
> So my questions are:
>
> 1. Can anyone suggest how to figure out what's going wrong with
> basyskom's images?
 
The images and helper script are working on a Point of View tablet
(TAB-TEG-10-1-4GB-3G) with pre installed Android 2.3. In case they
fail, the reason could be a different partition layout on "Motorola Xoom"
(you should get a hint on std error output by usind the helper scripts),
a invalid Android boot image (in case of pre installed Android > 2.3).
Also please keep in mind the published image (2011-12-09) needs a kernel
with enabled swap support, you will find it inside following rpm (you have
to unpack the rpm by hand to get the new boot image):
 
http://repo.pub.meego.com//Project:/KDE:/Mer_Extras:/Adaptation:/Tegra2/Mer_Extras_armv7hl/armv7hl/boot-image-tegra-0.1-3.5.Project.KDE.Mer_Extras.Adaptation.Tegra2.armv7hl.rpm
 
In case you like to adapt the kernel for your own needs,
the following url could be a good starting point:
 
https://build.pub.meego.com/package/files?package=kernel-adaptation-tegra&project=Project%3AKDE%3AMer_Extras%3AAdaptation%3ATegra2
 
Thats all we have.
 
Cheers
 
Maurice
 
 
 

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

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

[Maurice de la Ferte]

 
> Definitely. And for that, we need a process for testing the upgrade process
> _before_ end-users can gain access to the updated packages.
> Would installing the the last stable image, switching to the Testing 
> repository
> and then updating be the correct way?
 
This seems to be a good work-flow to test the update process.

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

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

[Maurice de la Ferte]

Hi, 

On April 17, 2012 at 1:02 AM "Lamarque V. Souza" 
 wrote:

> Em Monday 16 April 2012, Thomas Pfeiffer escreveu:
> > On Tuesday 03 April 2012 18:22:00 Maurice de la Ferte wrote:
> > > Hi all,
> > >
> > > at the moment we have a well tested and improved state of Plasma Active 2
> > > in our 'Project:KDE:Trunk:Testing' project. We like to ship this state
> > > into the 'Project:KDE:Trunk project' asap which is the package feed of
> > > our MeeGo/Mer end-user like images. This state is represented by several
> > > 'testing' marked images with '2012-03-27' timestamp prefix.
> >
> > Today, I put myself in an end-user position again:
> > I installed the plasma active two stable meego image
> > (basyskom-plasma-active- two-meego-usb-live.iso) and - without changing
> > anything beforehand - ran zypper ref and zypper up (maybe that's not what
> > an end-user is supposed to do, but it's possible and does not come with a
> > warning, and I don't know of a safer way to update).
> > This left my system in a pretty buggy state: The task switcher does not
> > display thumbnails (i.e. it does not work), the top bar is black with a
> > grey border and I could not add Berlin_Routes.pdf to an activity. This is
> > not what I call "well tested and improved".
 
Great thanks for testing this scenario and congratulations to find this update
issue. It would be very nice if you could also file a bug for this.
 
 
>
>         The problem with task switcher happens probably because the
> ~/.kde/share/config/kwinrc is configured with a different tabbox layout. The
> one we use now is:
>
> [TabBox]
> LayoutName=window_strip
>
>         PA2 uses "LayoutName=thumbnails" in ~/kde/share/config/kwinrc, we need
> to edit that file to fix this problem. I will see if we can use kconf_update
> for that.
>
>         The other problem is still an open issue:
> https://bugs.kde.org/show_bug.cgi?id=292820 . Today I've added a patch to
> kdelibs that seems to workaround the problem (needs more testing).
>
> > Maybe the code works if compiled as a testing image, but that's not the
> > realistic use-case. What has to actually work is that an end-user who
> > installed the latest stable image available (which currently is PA 2) can
> > update her system in order to receive bug fixes.
> > Maybe we can't get that in PA2 anymore, but this should definitely be our
> > aim for PA3: If a user updates her "stable" system from the "stable"
> > repositories, it has to have fewer bugs afterwards, not more.
> > Sorry for the rant. I don't have a problem with a buggy system personally,
> > but once we have actual end-users using and updating their devices and
> > they get what I got today, they ain't gonna be happy.
>
>         We need more people testing the upgrade process and reporting bugs.
 
I'm not happy about this situation too and this might be just the peak of an 
iceberg,
but this is the why we need people testing different kind of scenarios. I would
really like to see a kind of public test checklist and more people who get 
involved
into testing. Thanks for your feedback!
 
Cheers
 
Maurice
 
>
> --
> Lamarque V. Souza
> http://www.basyskom.com/

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

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

[Maurice de la Ferte]

Hi all,

at the moment we have a well tested and improved state of Plasma Active 2
in our 'Project:KDE:Trunk:Testing' project. We like to ship this state into
the 'Project:KDE:Trunk project' asap which is the package feed of our
MeeGo/Mer end-user like images. This state is represented by several 'testing'
marked images with '2012-03-27' timestamp prefix.

Cheers
Maurice

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

Re: About Plasma Active

[Maurice de la Ferte]

Dean Hi,
 
I'm doing much of the Plasma Active Integration on MeeGo/Mer,
also I'm involved in some x86/arm hardware adaptions and building
device images. You can count me in.
 
Cheers
 
Maurice
 

On March 27, 2012 at 5:06 PM Dean Howell  wrote:

> Plasma Active Team,
>
> We at The Powerbase  are probably the most
> excited blog on the Internet when it comes to Vivaldi, Plasma-Active and
> everything related to it.  We want to bring some attention to the core team
> and thought it would be fun to interview you guys *like a team*.
>
> We would like to send you some of our questions and *hopefully,* more than
> one of you will be able to answer.  It would be great for our readers to
> get the perspective of some of the other developers.  Would you guys be
> interested in doing that?
>
> In addition to that, we are opening up guest blogs on The Powerbase, 'ala
> what OMG Ubuntu does for the Ubuntu developer community.  We have a strong
> KDE readership and it would be a great place for you guys to share
> development updates.
>
> Best Regards,
>
> --
> Dean Howell,
> Editor-in-chief
> The Powerbase 

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

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

[Maurice de la Ferte]

 
On March 9, 2012 at 3:45 PM "Lamarque V. Souza" 
 wrote:

> Em Friday 09 March 2012, Maurice de la Ferte escreveu:
> > On March 9, 2012 at 1:43 PM "Lamarque V. Souza"
>  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@device# echo "modprobe fuse" >> /etc/rc.local
 
This makes sure needed kernel modules get loaded at boot-up.

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

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

[Maurice de la Ferte]

On March 9, 2012 at 1:43 PM "Lamarque V. Souza" 
 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-stable.html)
zypper is pointing to the Project:KDE:Trunk OBS project and will get those 
updates
by just "zypper up" in a few hours.
 
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.
 
Cheers
Maurice

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

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

[Maurice de la Ferte]

Hi all,

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.

Cheers
Maurice

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