Joyride

Could someone *please* explain and document the current process of  
getting RPMs and XO bundles into the build?

Etoys has been broken for weeks now unless I installed the latest  
bundle manually, just because the XO bundle was not pulled into the  
build. We're at bundle version Etoys-63 now, the build is still at  
Etoys-60.

A search for "joyride" comes up virtually empty:

        http://wiki.laptop.org/go/Special:Search?search=joyride

And once the joyride build process is explained, could you outline  
your intents to killing joy, too?

- Bert -

I'm sorry, this went to the wrong dev-* list. Please ignore :-)

- Bert -

On Oct 25, 2007, at 10:25 , Bert Freudenberg wrote:

You might have better luck asking on devel. I'm not sure if Scott and
Michael read the sugar list.

Marco

On 10/25/07, Bert Freudenberg <[hidden email]> wrote:

Marco, Bert,

I do read the sugar list, I saw Bert's email, and I am definitely guilty
of not having offered a timely reply to your questions. My apologies.

> On 10/25/07, Bert Freudenberg <[hidden email]> wrote:
> > Could someone *please* explain and document the current process of
> > getting RPMs and XO bundles into the build?

The list of packages that pilgrim knows to install is at

  http://dev.laptop.org/git?p=users/cscott/pilgrim;a=blob;f=streams.d/olpc-development.stream;h=5e607540940e24bc97ffbf4d14429893324d5646;hb=autobuild#l50

The current process for RPMS already listed at that location is to
upload an RPM with a higher version number to ~/public_rpms/<build> on
dev.laptop.org.

Please, please, please also include the SRPM in that directory alongside
the RPM. We aren't using it yet, but we will be very shortly.

------

The process for new .xos is to have one of m_stone, c_scott, cjb, or
marcopg apply a patch to

  http://dev.laptop.org/git?p=users/cscott/pilgrim;a=blob;f=streams.d/olpc-development.stream;h=5e607540940e24bc97ffbf4d14429893324d5646;hb=autobuild#l178

that lists the activity name and to upload the .xo file to

  http://olpc.download.redhat.com/activities/<build>

I believe Marco knows how to do this.

We are half-way through the change to our build-tools that is required
to read .xo bundles from ~/public_rpms/<build. I fully expect this
change to land by early next week; it has not yet because the person who
has to integrate it has simply had higher priority bugs (namely, getting
first-boot activation to a deployable state).

------

Again, sorry for the delay.  More details about current speculations for
killing joy will follow this afternoon.

Michael


 

Marco pointed out that my previous email was not clear enough about the
process for including .xo bundles (#4251). The update on that bug is as
follows:

  Please follow Bert's example by putting your .xo bundles in
  ${HOME}/public_rpms/<build>/

Now, concerning #4253:

  ChangeLogs, in the format

  """
  <pkg-lines>      (containing ".xo", ".rpm")
  <detail-lines>   (not containing the string ".xo", ".rpm", "--")
  -- <signature>   (-- is the line marker)

  <pkg>
  <pkg>.rpm
  <detail>
  -- <signature>
  """

  as exemplified in

    /home/mstone/public_rpms/rainbow/ChangeLog

  will be _required_ to drive package inclusion in the builds.

Let me repeat that.

Your packages and activity bundles WILL NOT BE INCLUDED unless you
supply change-entries, in the format above, for the exact version of
the package or activity bundle you are trying to put into a build.
(This is because we *must* get accurate, comprehensive, human-readable
ChangeLogs and the most direct method of accomplishing that is to
require you to write them as a prerequisite of package inclusion.)

If you don't like the format, please contribute a patch to

  git://dev.laptop.org/users/mstone/buildtools

specifically to the file 'collect_rpms.py' and to the 'changelogs'
package contained therein that adds support for your preferred format.

We are very happy to support other ChangeLog formats and collection
methods but are currently unable to support them on our own.

Finally, intentions for killing joy will be outlined in a separate email
as soon as they are finalized (hopefully tonight).

Questions?

Michael

P.S. - If you have them, please include your source rpms alongside the
binary ones.

Also, I've stubbed out a page at

  http://wiki.laptop.org/go/Joyride

to accumulate content from this thread. Please help fill it in.

On Thu, Oct 25, 2007 at 10:25:04AM -0400, Bert Freudenberg wrote: