Task:Maemo OBS - Revision history

imported_>woody14619: /* Weekly meetings */

2012-06-04T22:12:13Z

Weekly meetings

← Older revision		Revision as of 22:12, 4 June 2012
Line 9:		Line 9:

	We are currently having weekly meetings on Mondays, 15:00 UTC. We will be using the maemo-developers mailing list for communications.		We are currently having weekly meetings on Mondays, 15:00 UTC. We will be using the maemo-developers mailing list for communications.

			Meeting minutes can be found [[Task:Maemo_OBS:Meeting_Minutes\|here]].

	== Issues ==		== Issues ==

imported_>xfade: May 29 updates

2012-05-29T15:58:12Z

May 29 updates

← Older revision		Revision as of 15:58, 29 May 2012
Line 62:		Line 62:

	javispedro will be playing with this.		javispedro will be playing with this.

			=== May 29 2012 ===

			xfade:
			I've imported qt4-dev with armel binaries into the PR1.3 repo. This fixed building Qt apps for Fremantle

			Currently trying to build qemu dynamically linked for PR1.3, starting out with the qemu-kvm version that was uploaded to extras-devel. This failed building a few times on OBS because the vm ran out of memory. Trying again :)

imported_>javispedro at 16:39, 22 May 2012

2012-05-22T16:39:05Z

← Older revision		Revision as of 16:39, 22 May 2012
Line 45:		Line 45:

	Additionally, we agreed that we should look for more information on the use of Scratchbox2 on OBS.		Additionally, we agreed that we should look for more information on the use of Scratchbox2 on OBS.

			=== May 22 2012 ===

			[http://mg.pov.lt/maemo-meeting-irclog/latest.log.html#t2012-05-22T17:59:44]

			The imported Fremantle 1.3 SDK packages are not yet built. Some issues have already been found (such as [https://bugs.maemo.org/show_bug.cgi?id=11445 the presence of x86 binaries in some official SDK armel packages]). Even with all qt-based packages failing because of the previous issue, the number of failing packages did not grow to unmanageable proportions.


			Additionally, we have extra documentation regarding the use of SB2: [http://wiki.merproject.org/wiki/Platform_SDK_and_SB2].

			The idea of the build process using SB2 is 1) the builder creates a new virtual machine, 2) installs the base Fremantle X86 packages to it, 3) installs Scratchbox2 and the arm crosscompiler, 4) boots the VM, 5) installs some more packages, 6) configures the SB2 target and installs base packages to it, 6 ) enters SB2 and starts building.

			Therefore, the first detected requirement is that we need to provide the following Fremantle X86 debian packages:
			# Scratchbox2
			# CodeSourcery 2009q3

			javispedro will be playing with this.

imported_>jeremiah: /* Goals */

2012-05-14T21:08:52Z

Goals

← Older revision		Revision as of 21:08, 14 May 2012
Line 3:		Line 3:
	This project enables the following:		This project enables the following:

	*~~To provide e~~ a single community OBS that includes Harmattan, Fremantle and Diablo as targets to faciliate the development of applications that work on all platforms.		*Provide a single, community OBS that includes Harmattan, Fremantle and Diablo as targets to faciliate the development of applications that work on all platforms.
	*To collaborate with Mer/Nemo to share the costs of maintaining and operating community OBS.		*To collaborate with Mer/Nemo to share the costs of maintaining and operating the community OBS.

	== Weekly meetings ==		== Weekly meetings ==

imported_>javispedro: Undoing some mess up

2012-04-24T10:54:56Z

Undoing some mess up

@@ Line 5: / Line 5: @@
 *To provide e a single community OBS that includes Harmattan, Fremantle and Diablo as targets to faciliate the development of applications that work on all platforms.
 *To collaborate with Mer/Nemo to share the costs of maintaining and operating community OBS.
 == Issues ==
@@ Line 12: / Line 16: @@
 Maemo SDK ships what is called a rootstrap with many packages preinstalled. Developers usually do not explicitly mention those packages in their build dependencies because they're already preinstalled.
 OBS doesn't accept rootstraps. Each builder process starts with an empty virtual machine, and from there a fixed set of packages is installed onto it.
 === Scratchboxisms ===
@@ Line 20: / Line 32: @@
 Many packages have scratchboxisms. The exact number is yet to be determined. Hopefully, not large.
-SB2 might help here.
+==== Solutions to consider ====

imported_>javispedro: I like SD69's wording better!

2012-04-24T10:54:15Z

I like SD69's wording better!

@@ Line 1: / Line 1: @@
 == Goals ==
 This project enables the following:
-To provide e a single community OBS that includes Harmattan, Fremantle and Diablo as targets to faciliate the development of applications that work on all platforms.
+*To provide e a single community OBS that includes Harmattan, Fremantle and Diablo as targets to faciliate the development of applications that work on all platforms.
+*To collaborate with Mer/Nemo to share the costs of maintaining and operating community OBS.
 == Issues ==
@@ Line 20: / Line 12: @@
 Maemo SDK ships what is called a rootstrap with many packages preinstalled. Developers usually do not explicitly mention those packages in their build dependencies because they're already preinstalled.
 OBS doesn't accept rootstraps. Each builder process starts with an empty virtual machine, and from there a fixed set of packages is installed onto it.
 === Scratchboxisms ===
@@ Line 36: / Line 20: @@
 Many packages have scratchboxisms. The exact number is yet to be determined. Hopefully, not large.
-==== Solutions to consider ====
+SB2 might help here.

imported_>javispedro at 10:53, 24 April 2012

2012-04-24T10:53:41Z

@@ Line 9: / Line 9: @@
 To collaborate with Mer/Nemo to share the costs of maintaining and operating community OBS.
 == Issues ==
@@ Line 37: / Line 41: @@
 # Manually fix the packages. The hard way. Most build problems are trivial, but even then this might require quite some time.
 # ... Emulate those Scratchboxisms in some other way?

imported_>javispedro at 10:48, 24 April 2012

2012-04-24T10:48:32Z

← Older revision		Revision as of 10:48, 24 April 2012
Line 16:		Line 16:
	Maemo SDK ships what is called a rootstrap with many packages preinstalled. Developers usually do not explicitly mention those packages in their build dependencies because they're already preinstalled.		Maemo SDK ships what is called a rootstrap with many packages preinstalled. Developers usually do not explicitly mention those packages in their build dependencies because they're already preinstalled.

	OBS doesn't accept rootstraps. Each builder process starts with an empty virtual machine, and from there a fixed set of packages is installed onto it.		OBS doesn't accept rootstraps. Each builder process starts with an empty virtual machine, and from there a fixed set of packages is installed onto it.

			Therefore, the packages that do not explicitly list the in-rootstrap packages in their build-dependencies fail to build.

			==== Solutions to consider ====

			# Manually go through all build failures and add the missing build-dependencies to the packages. Hard to contact all the package maintainers.
			# Manually go through all build failures and add the missing build-dependencies to the fixed list of packages that are preinstalled when the VM starts. Each package on this list adds to the build time of all packages...
			# Investigate the use of an actual rootstrap (maybe with SB2 it is possible?)

	=== Scratchboxisms ===		=== Scratchboxisms ===
Line 24:		Line 32:
	Many packages have scratchboxisms. The exact number is yet to be determined. Hopefully, not large.		Many packages have scratchboxisms. The exact number is yet to be determined. Hopefully, not large.

	SB2 might help here.		==== Solutions to consider ====

			# SB2 might help here.
			# Manually fix the packages. The hard way. Most build problems are trivial, but even then this might require quite some time.
			# ... Emulate those Scratchboxisms in some other way?

imported_>sd69: /* Goal */

2012-04-23T17:30:44Z

Goal

← Older revision		Revision as of 17:30, 23 April 2012
Line 1:		Line 1:
	== ~~Goal~~ ==		== Goals ==

	To move the current Fremantle autobuilder to maemo.org OBS . Probably Diablo and Chinook as secondary goals.		To move the current Fremantle autobuilder to maemo.org OBS. Probably Diablo and Chinook as secondary goals.


			This project enables the following:

			To provide e a single community OBS that includes Harmattan, Fremantle and Diablo as targets to faciliate the development of applications that work on all platforms.

			To collaborate with Mer/Nemo to share the costs of maintaining and operating community OBS.

	== Issues ==		== Issues ==

imported_>javispedro: New page: == Goal == To move the current Fremantle autobuilder to maemo.org OBS . Probably Diablo and Chinook as secondary goals. == Issues == === Build dependencies === Maemo SDK ships what is ...

2012-04-23T16:19:01Z

New page: == Goal == To move the current Fremantle autobuilder to maemo.org OBS . Probably Diablo and Chinook as secondary goals. == Issues == === Build dependencies === Maemo SDK ships what is ...

New page

== Goal ==

To move the current Fremantle autobuilder to maemo.org OBS . Probably Diablo and Chinook as secondary goals.

== Issues ==

=== Build dependencies ===

Maemo SDK ships what is called a rootstrap with many packages preinstalled. Developers usually do not explicitly mention those packages in their build dependencies because they're already preinstalled.

OBS doesn't accept rootstraps. Each builder process starts with an empty virtual machine, and from there a fixed set of packages is installed onto it.

=== Scratchboxisms ===

A scratchboxism happens when a developer assumes something that is only true when running under Scratchbox(1). It might be a special environment variable, special directory, the behavior of certain commands, the fact that is actually x86, or the use of a custom Scratchbox devkit.

Many packages have scratchboxisms. The exact number is yet to be determined. Hopefully, not large.

SB2 might help here.