best repos for building IVI-1.2 image?

[Alison Chaiken]

I've tried using mic2 to build IVI images for Atom using both
repo.meego.com/MeeGo/builds/1.2.80/latest and
repo.meego.com/MeeGo/builds/trunk/latest. Despite rumors that the
broken festival-voice dependency is fixed
(https://bugs.meego.com/show_bug.cgi?id=22515), I still hit that
error:

festival-1.96-10.1.i586 requires festival-voice

I also get

Error: failed to create image : Failed to build transaction :
meego-ux-panels-0.3.12.1-1.21.i586 requires meego-ux-daemon >= 0.2.27
meego-app-im-0.2.7-1.25.i586 requires libmeegotouchcore.so.0
meego-app-im-0.2.7-1.25.i586 requires meego-handset-sound-theme

with both repos. Should I be using a different source for packages
to build an image with @IVI and @IVI Applications package groups?
Thanks.

[Clark, Joel]

On Wednesday, August 24, 2011 4:11 PM Alison Chaiken
I've tried using mic2 to build IVI images for Atom using both
repo.meego.com/MeeGo/builds/1.2.80/latest and
repo.meego.com/MeeGo/builds/trunk/latest. Despite rumors that the
broken festival-voice dependency is fixed
(https://bugs.meego.com/show_bug.cgi?id=22515), I still hit that
festival-1.96-10.1.i586 requires festival-voice

I have not checked the status of this issue, but generally "Fixed" means the developer has submitted the fix, "Released" means the Release engineering team has accepted the fix and it should show up in the repos at the next weekly build.

I also get
meego-ux-panels-0.3.12.1-1.21.i586 requires meego-ux-daemon >= 0.2.27
meego-app-im-0.2.7-1.25.i586 requires libmeegotouchcore.so.0
meego-app-im-0.2.7-1.25.i586 requires meego-handset-sound-theme
with both repos. Should I be using a different source for packages
Thanks.
Alison Chaiken

We are in the process of removing the dependencies on all "meego-ux" and "meego-app" modules.
We don't see them moving forward to MeeGo IVI 1.3 release. That's why all the dependencies are broken. I suggest removing the patterns that pull any meego-ux or meego-app modules from your kickstart file at least until we get this working in the default build.

regards
Joel

[T***@public.gmane.org]

Hi,

From: Alison Chaiken
I've tried using mic2 to build IVI images for Atom using both
repo.meego.com/MeeGo/builds/1.2.80/latest and
repo.meego.com/MeeGo/builds/trunk/latest. Despite rumors that the
broken festival-voice dependency is fixed

*snip*

Umm, your subject line says you want to build an 1.2 image? Or are you really after a 1.3 image, because that's the story the repos tell.

Just checking

Thomas

[Alison Chaiken]

Post by T***@public.gmane.org
Umm, your subject line says you want to build an 1.2 image?

Actually I want to build "latest stable" for a demo and can't figure
out which repo to pull from, which is why the subject line is "best
repos for building IVI-1.2 image?".

Post by T***@public.gmane.org
Or are you really after a 1.3 image, because that's the story the repos tell.

That's what I kind of figured. What repos do you then suggest for
1.2 latest-stable? I have a feeling the answer is, "The May 1.2.0
release" but hope to be told otherwise!

[T***@public.gmane.org]

Hi,

Post by Alison Chaiken

Post by T***@public.gmane.org
Umm, your subject line says you want to build an 1.2 image?

Actually I want to build "latest stable" for a demo and can't figure
out which repo to pull from, which is why the subject line is "best
repos for building IVI-1.2 image?".

Stable sounds like 1.2, someone correct me if I'm wrong.
(I'm not that familiar with IVI, that's more my general view)

Post by Alison Chaiken

Post by T***@public.gmane.org
Or are you really after a 1.3 image, because that's the story the

repos tell.
That's what I kind of figured. What repos do you then suggest for
1.2 latest-stable? I have a feeling the answer is, "The May 1.2.0
release" but hope to be told otherwise!

There is this 1.2.0.x series which is, according to general
meego roadmap, being released soon as 1.2.1.

1.3 seems to be a 'bit of a mess' at the moment still. But signs are
that it actually might start stabilizing. First ARM images have
been sighted, IA32 hopefully soon too.

Just my 0,02€

Thomas

PS: See also Joel's email, he's more specific about IVI while I'm more general.

[Clark, Joel]

Post by Alison Chaiken
What repos do you then suggest for
1.2 latest-stable? I have a feeling the answer is, "The May 1.2.0
release" but hope to be told otherwise!
Alison Chaiken

I suggest building against:
http://repo.meego.com/MeeGo/releases/1.2.0/repos/
and then doing a runtime update to get the stuff in
http://repo.meego.com/MeeGo/updates/1.2.0/repos/

What are you looking for in later repos?

The MeeGo IVI project team is not working aligning with any of the 1.2.0.90 or later 1.2 branches, Those branches are using the 1.2.0 core to build some segment specific additional UX features. (i.e. more tablet specific development etc.).

We've also noticed that stuff in the 1.2.0 branch after July 6 such as:
http://repo.meego.com/MeeGo/builds/1.2.0/1.2.0.1.2.20110809.1/repos/
have been breaking IVI

1.2.80 and 1.2.90 branches are the precursor to 1.3. There are substantial changes there which the MeeGo IVI project team is still working on resolving in order to get our first pre-release 1.3 IVI builds working.


regards
Joel

[Alison Chaiken]

Post by Clark, Joel
http://repo.meego.com/MeeGo/releases/1.2.0/repos/
and then doing a runtime update to get the stuff in
http://repo.meego.com/MeeGo/updates/1.2.0/repos/
What are you looking for in later repos?

If I'm installing some random user program like Thunderbird or
Rhythmbox or Totem, I'll grab a tarball from the project in question's
trunk/stable/latest branch and configure-make-make_install it, which
nearly always works. Calling a branch "stable" if it's not
tremendously stable is a bit confusing, although it's not IVI's fault
if the Core team is doing so.

Proceeding with 1.2.0 repos, thanks again.

[Clark, Joel]

Post by Alison Chaiken

Post by Clark, Joel
http://repo.meego.com/MeeGo/releases/1.2.0/repos/
and then doing a runtime update to get the stuff in
http://repo.meego.com/MeeGo/updates/1.2.0/repos/
What are you looking for in later repos?

If I'm installing some random user program like Thunderbird or
Rhythmbox or Totem, I'll grab a tarball from the project in question's
trunk/stable/latest branch and configure-make-make_install it, which
nearly always works. Calling a branch "stable" if it's not
tremendously stable is a bit confusing, although it's not IVI's fault
if the Core team is doing so.
Proceeding with 1.2.0 repos, thanks again.
Alison Chaiken

Recent testing leads me to change my recommendation. Instead of building a new image I suggest using the image already built in the releases/1.2.0/images directory and then do the updates as needed.

I believe the images we released in http://repo.meego.com/MeeGo/releases/1.2.0/repos/ are stable and we did quite a bit of testing updating that image with the "updates" in
http://repo.meego.com/MeeGo/updates/1.2.0/repos/

What appears to be badly broken right now is building new images even from the same repos used to build the released images. I've seen several different folks reporting various symptoms that all seem to be related to changes in the MIC image tool since May 19. The break appears to have happened around July 26.

regards
Joel

[Alison Chaiken]

I find that installing the 1.2.0 release and then zypping up from

download.meego.com/live/Trunk/standard/

on pinetrail leads to installation of the 3.0.0 kernel-adaptation-pc,
which is cool, except that the kernel comes with no new /lib/modules,
which turns out to be a directory that I'd come to cherish. No big
worries as I can revert to the earlier kernel-adaptation-pinetrail and
its non-empty /lib/modules.