[sugar] Joyride is open for development!
Hi, I noticed an IRC conversation this morning asking whether Joyride is open for 9.1 development -- after checking with Scott and Michael, the answer is that it absolutely is. Please don't push broken code, though, since we'd like Joyride to remain usable for everyone. The current plan is to wait until F10 is released (end of November) before rebasing Joyride onto it. Thanks, - Chris. -- Chris Ball [EMAIL PROTECTED] ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] Joyride is open for development!
On Fri, Oct 17, 2008 at 9:14 PM, Chris Ball [EMAIL PROTECTED] wrote: The current plan is to wait until F10 is released (end of November) before rebasing Joyride onto it. But the decision to rebase has been made? Thanks, Marco ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] Joyride is open for development!
2008/10/17 Marco Pesenti Gritti [EMAIL PROTECTED]: On Fri, Oct 17, 2008 at 9:14 PM, Chris Ball [EMAIL PROTECTED] wrote: The current plan is to wait until F10 is released (end of November) before rebasing Joyride onto it. But the decision to rebase has been made? Well, I believe Michael, Chris and I are in favor of it, and I haven't heard any strong arguments against doing so. (Then again, I'm not particularly looking forward to the work!) The real question is whether we're going to settle with F10, or try to follow Rawhide or even to wait for F11. My strong opinion is that 9.1 should be based on F10, and I don't yet have a strong opinion on what 9.2 should follow. I think dgilmore has argued that we should be trying to stay absolutely current with Fedora, so that we have a chance to make changes before Fedora stabilizes, and so that every Fedora release has the absolute latest Sugar. (I think we've got enough problems fixing our own bugs, and I don't want to be making changes and trying to stabilize at the same time Fedora is making changes to try to do so.) Anyway, that argument is still open. And if anyone would like to make the strong argument that we should *not* rebase on F10, they should do so before F10 is released and we start trying to move joyride to it. But unless anyone objects the plan is to move to F10 ASAP so we're not trying to shake all the bugs out of the rebase the month before we're scheduled to release. --scott -- ( http://cscott.net/ ) ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] joyride-weekly: joyride-2230
On 31.07.2008, at 02:41, Michael Stone wrote: Dear world, This week's 'please test this joyride' is joyride-2230. Test group release notes, care of Charlie, are available at http://wiki.laptop.org/go/ Test_Group_Release_Notes#Build_Joyride_2230 olpc-update thinks that build does not exist. - Bert - ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] joyride-weekly: joyride-2230
On 31 Jul 2008, at 14:44, Bert Freudenberg wrote: On 31.07.2008, at 15:14, Bert Freudenberg wrote: On 31.07.2008, at 02:41, Michael Stone wrote: Dear world, This week's 'please test this joyride' is joyride-2230. Test group release notes, care of Charlie, are available at http://wiki.laptop.org/go/ Test_Group_Release_Notes#Build_Joyride_2230 olpc-update thinks that build does not exist. The error actually is unexpected server greeting: fakeroot Glad it's not just me then. I thought I had some random intermittent network issue (for the last week or two) so had given up with olpc- updates rsync attempts to the server. I defaulted back to manually downloading the .toc and .usb files from the web server, sticking them on a USB stick and using olpc-update --usb. --Gary ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] joyride-weekly: joyride-2230
On 31.07.2008, at 17:59, Gary C Martin wrote: On 31 Jul 2008, at 14:44, Bert Freudenberg wrote: On 31.07.2008, at 15:14, Bert Freudenberg wrote: On 31.07.2008, at 02:41, Michael Stone wrote: Dear world, This week's 'please test this joyride' is joyride-2230. Test group release notes, care of Charlie, are available at http://wiki.laptop.org/go/ Test_Group_Release_Notes#Build_Joyride_2230 olpc-update thinks that build does not exist. The error actually is unexpected server greeting: fakeroot Glad it's not just me then. I thought I had some random intermittent network issue (for the last week or two) so had given up with olpc- updates rsync attempts to the server. I defaulted back to manually downloading the .toc and .usb files from the web server, sticking them on a USB stick and using olpc-update --usb. SOmeone fixed it. I updated to 2233 just fine. - Bert - ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
[sugar] joyride-weekly: joyride-2230
Dear world, This week's 'please test this joyride' is joyride-2230. Test group release notes, care of Charlie, are available at http://wiki.laptop.org/go/Test_Group_Release_Notes#Build_Joyride_2230 I'll push this announcement out further as discussed in last night's email as soon as I'm able. Michael ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
[sugar] joyride-weekly builds for testing.
As part of our gradual stabilization program, each week, we're going to nominate the newest non-disqualified Tinderbox-approved joyride build available as of 9:00 AM EDT on Wednesday as the joyride-weekly test candidate for people who are unable to contribute test results against joyride-latest. Please do everything in your power to ensure that builds at risk of being nominated are worthy of these testers' consideration. Or else. :) Finally, this week's joyride-weekly build is joyride-2200. Michael ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
[sugar] Joyride 2201 blocker
I do most of my work with CLI from the Terminal. On my XO with Joyride 2201 there is no bash history accessible in Terminal -- hitting up-arrow at the prompt does NOT call up what had been previously entered at the prompt. [bash history is accessible from the text console (alt-ctl-F1).] mikus ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] Joyride 2201 blocker
On Wed, 2008-07-23 at 19:20 -0400, Mikus Grinbergs wrote: I do most of my work with CLI from the Terminal. On my XO with Joyride 2201 there is no bash history accessible in Terminal -- hitting up-arrow at the prompt does NOT call up what had been previously entered at the prompt. [bash history is accessible from the text console (alt-ctl-F1).] Please file a ticket, and also let us know which joyride version this did work with (if known). Thanks, Daniel ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] Joyride 2201 blocker
Am 23.07.2008 um 20:28 schrieb Daniel Drake: On Wed, 2008-07-23 at 19:20 -0400, Mikus Grinbergs wrote: I do most of my work with CLI from the Terminal. On my XO with Joyride 2201 there is no bash history accessible in Terminal -- hitting up-arrow at the prompt does NOT call up what had been previously entered at the prompt. [bash history is accessible from the text console (alt-ctl-F1).] Please file a ticket, and also let us know which joyride version this did work with (if known). I filed http://dev.laptop.org/ticket/7613 earlier today before I noticed that many other short cuts are broken, too - frame key, journal key, or the cursor keys as you found. - Bert - ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] Joyride 2201 blocker
Just added a ticket for this myself: http://dev.laptop.org/ticket/7617 Seems to affect quite a number of keys – at least on my XO B4 with Spanish overlay (worked fine in 2174). I'd previously added ticket (Journal search and frame key have no effect): http://dev.laptop.org/ticket/7616 But am now assuming some keyboard mapping has gone wonky in the latest Joyrides (it's been about a week since Joyride was available to the non-hardcore dev so 2174 was last I could install). --Gary On 24 Jul 2008, at 01:28, Daniel Drake wrote: On Wed, 2008-07-23 at 19:20 -0400, Mikus Grinbergs wrote: I do most of my work with CLI from the Terminal. On my XO with Joyride 2201 there is no bash history accessible in Terminal -- hitting up-arrow at the prompt does NOT call up what had been previously entered at the prompt. [bash history is accessible from the text console (alt-ctl-F1).] Please file a ticket, and also let us know which joyride version this did work with (if known). Thanks, Daniel ___ Devel mailing list [EMAIL PROTECTED] http://lists.laptop.org/listinfo/devel ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] Joyride 2201 blocker
I get the same result on Joyride 2202 (manually upgraded to 2203). What is happening is that in Terminal on my XO certain keypresses (e.g., up-arrow, right-arrow, end) are not being recognized. mikus ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] Joyride shutdown flaky
On Sun, Jul 13, 2008 at 10:03 PM, Mikus Grinbergs [EMAIL PROTECTED] wrote: Running recent Joyride on my G1G1. When I request a shutdown, it sometimes proceeds hands off. But sometimes, after the Sugar shell has closed - nothing further seems to happen. On those occasions, sometimes the ending-picture (with the don't do this icons) is presented if I press alt-ctl-F2 (the Sugar shell was on alt-ctl-F3). If I can get to the ending picture, the shutdown completes by itself after what seems like a LONG time. But if I don't get to the ending picture, I'm left to complete the shutdown process by holding down the power button for more than four seconds. Hi, this is http://dev.laptop.org/ticket/7350 , AFAICS. Regards, Tomeu ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] Joyride shutdown flaky
Running recent Joyride on my G1G1. When I request a shutdown, it sometimes proceeds hands off. But sometimes, after the Sugar shell has closed - nothing further seems to happen. On those occasions, sometimes the ending-picture (with the don't do this icons) is presented if I press alt-ctl-F2 (the Sugar shell was on alt-ctl-F3). If I can get to the ending picture, the shutdown completes by itself after what seems like a LONG time. But if I don't get to the ending picture, I'm left to complete the shutdown process by holding down the power button for more than four seconds. Hi, this is http://dev.laptop.org/ticket/7350 , AFAICS. I believe I've seen this problem while PolicyKit-0.8-2.fc9.i386 was installed on my system. I'm o.k. if #7350 fixes this problem. But the initial #7350 description talks about can't shutdown .. if multiple sessions. I normally don't use the text console, and I clicked on 'Shutdown' in the Home view -- so I think I've had this problem even when I did not have multiple sessions. [Also, the initial #7350 description does not talk about seeing the ending picture on ctl-alt-F2 instead of on ctl-alt-F3.] mikus ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] Joyride shutdown flaky
On Mon, 2008-07-14 at 11:27 +0200, Tomeu Vizoso wrote: On Sun, Jul 13, 2008 at 10:03 PM, Mikus Grinbergs [EMAIL PROTECTED] wrote: Running recent Joyride on my G1G1. When I request a shutdown, it sometimes proceeds hands off. But sometimes, after the Sugar shell has closed - nothing further seems to happen. On those occasions, sometimes the ending-picture (with the don't do this icons) is presented if I press alt-ctl-F2 (the Sugar shell was on alt-ctl-F3). If I can get to the ending picture, the shutdown completes by itself after what seems like a LONG time. But if I don't get to the ending picture, I'm left to complete the shutdown process by holding down the power button for more than four seconds. Hi, this is http://dev.laptop.org/ticket/7350 , AFAICS. I disagree. #7350 just makes the shutdown menu item appear to do nothing. In this case the shutdown process is clearly started. I think I have seen the issue too. Mikus, can you please file a trac ticket? Thanks, Daniel ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
[sugar] Joyride is reopened for development.
Hi, We announced the Joyride builds as having been frozen for new features several months ago, as we solidified the Update.1 build. Now that it's doing fine in its own stream, we're reopening the Joyride process for new development. So, consider Joyride to be gradually unfreezing. Please announce large changes before pushing them, and push via the Joyride ~/public_rpms process or the Koji dist-olpc2 branch. We'd like to invite a discussion about process changes to ensure that our Joyride builds continue to be stable and usable. Ideas welcome! And finally, this doesn't mean that Update.1 is finished -- it's still very important that we keep on top of the remaining testing and bugs in that stream. Thanks! - Chris. -- Chris Ball [EMAIL PROTECTED] ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] Joyride is reopened for development.
Chris wrote * Continue to have (all) activities present in Joyride builds. I don't know how many others are like me, but for me this creates awkwardness (I dual-boot my G1G1 between a public will see this build (e.g., Update.1) and a development build (e.g., Joyride). My problem is that I customize the builds I use -- that takes time. So it is not practical for me to install *every* Joyride build that comes along. But Activities in /usr/share/activities seem to take precedence over same-name Activities in /home/olpc/Activities. Suppose a new Joyride supplies an Activity in /usr/share/activities that supersedes the one I have. At the moment I don't have a procedure whereby I myself can replace just that one Activity there (if I don't want to install that whole new Joyride). [I *have* worked out how to replace individual Activities in /home/olpc/Activities.] Would (as root) just unzipping a copy of the new .xo file into /usr/share/activities work for me ? [I believe the XO keeps a registry of Activities -- would that need updating also ?] Thanks in advance for assistance, mikus ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] Joyride is reopened for development.
Hi Mikus, But Activities in /usr/share/activities seem to take precedence over same-name Activities in /home/olpc/Activities. My understanding is that exactly the opposite is true, but I might be wrong -- /home/olpc/Activities should be taking precedence. Thanks, - Chris. -- Chris Ball [EMAIL PROTECTED] ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] joyride smoke test results?
--- Erik Blankinship wrote: Is there a wiki page where release notes / smoke test notes on joyride are posted? There used to be such a page before JoyRiding. Also, it looks like the automated release notes have stopped again. --- end of quote --- Smoke Test notes and/or any other notes from testing (usually bugs that make a build a waste of time to try out) should be posted here: http://wiki.laptop.org/go/Test_Group_Release_Notes - AlexL ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] joyride smoke test results?
On 10 Dec 2007 14:48:05 -0500, Alexander M. Latham [EMAIL PROTECTED] wrote: --- Erik Blankinship wrote: Is there a wiki page where release notes / smoke test notes on joyride are posted? There used to be such a page before JoyRiding. Also, it looks like the automated release notes have stopped again. --- end of quote --- Smoke Test notes and/or any other notes from testing (usually bugs that make a build a waste of time to try out) should be posted here: http://wiki.laptop.org/go/Test_Group_Release_Notes Great -- I've updated the page. http://wiki.laptop.org/go/Test_Group_Release_Notes#Joyride_Builds ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] joyride smoke test results?
A related question not yet answered on that wiki page: What is the last known joyride that, for the most part, worked? ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] joyride smoke test results?
--- [EMAIL PROTECTED] wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Erik Blankinship wrote: A related question not yet answered on that wiki page: What is the last known joyride that, for the most part, worked? Wiki notes notwithstanding, 1395 is working for me. Note that I did a clean install (square-key with usb autoreinstallation). - --Ben -BEGIN PGP SIGNATURE- --- end of quote --- There are some sugar rpms that are missing, which have caused a lot of activities to fail to launch, mostly becuase of Attribute errors. I believe our new build manager is aware of this, and is working on getting those rpms back into joyride. Were you able to get browse or record to load? Those are two which won't load for me on 1394, which should be the same as 1395 based on the changelogs (http://dev.laptop.org/~bert/joyride-pkgs.html), but that's not for certain. - AlexL ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] joyride smoke test results?
Wiki notes notwithstanding, 1395 is working for me. Note that I did a clean install (square-key with usb autoreinstallation). Just tried that on a b3 and same problem -- activities don't launch (other than Journal). ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] joyride smoke test results?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Erik Blankinship wrote: Wiki notes notwithstanding, 1395 is working for me. Note that I did a clean install (square-key with usb autoreinstallation). Just tried that on a b3 and same problem -- activities don't launch (other than Journal). It looks like some things work and some don't. I tried Chat, Connect, Calculator, Clock, and Distance, all of which launched fine. Record doesn't launch, and neither does Browse. - --Ben -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHXapSUJT6e6HFtqQRAp2bAJsGnz3HN00leXdEdqBPK9NXPTIQNgCgoXi9 KnO7Y0zSvrbyUETaRsMYTW0= =MgCG -END PGP SIGNATURE- ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] joyride smoke test results?
--- Erik Blankinship wrote: A related question not yet answered on that wiki page: What is the last known joyride that, for the most part, worked? --- end of quote --- It looks like the last joyride test that went through the 1 hour smoke test was Joyride 1372. Unfortunately, joyride builds come out faster than they can be tested. Pretty soon we hope to have the results of tinderbox determine whether we post a joyride build or not. One of the things tinderbox does is try to load each activity. This will catch these big regressions very quickly. cscott is also working on making some headless tests that will be run on builds in order to find major bugs right off the bat. Also, mstone is working on Buildbot to do additional testing. If you have access to the teamwiki, the minutes from the testing meeting we had about this are here: http://wiki.laptop.org/go/TestMtg%2C_2007-12-02 - AlexL ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] Joyride build errors
On Nov 12, 2007, at 13:25 , Ed Stoner wrote: At http://xs-dev.laptop.org/~cscott/olpc/streams/joyride/build258/ devel_jffs2/build.log I see: No activity matches FlipSticks No activity matches CartoonBuilder I am the developer of both of these activities and believe I've done everything I am supposed to to get them included. I'm obviously missing something though. Can anyone explain what these errors mean and what I should be doing to resolve them? flipsticks-1.xo != FlipSticks-1.xo cartoon-builder-1.xo != CartoonBuilder-1.xo - Bert - ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] Joyride build errors
Are you saying I need to change the filenames? I named the xo packages based on how the repositories were setup. Does the build system look at the activity.info and check that they are the same? -Ed Bert Freudenberg wrote: On Nov 12, 2007, at 13:25 , Ed Stoner wrote: At http://xs-dev.laptop.org/~cscott/olpc/streams/joyride/build258/devel_jffs2/build.log I see: No activity matches FlipSticks No activity matches CartoonBuilder I am the developer of both of these activities and believe I've done everything I am supposed to to get them included. I'm obviously missing something though. Can anyone explain what these errors mean and what I should be doing to resolve them? flipsticks-1.xo != FlipSticks-1.xo cartoon-builder-1.xo != CartoonBuilder-1.xo - Bert - ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] Joyride build errors
On Nov 12, 2007, at 16:22 , Ed Stoner wrote: Are you saying I need to change the filenames? Yes. You should switch to bundlebuilder anyway, bundle-signing will require this soonish. This will also ensure a correctly-named .xo file. - Bert - I named the xo packages based on how the repositories were setup. Does the build system look at the activity.info and check that they are the same? -Ed Bert Freudenberg wrote: On Nov 12, 2007, at 13:25 , Ed Stoner wrote: At http://xs-dev.laptop.org/~cscott/olpc/streams/joyride/build258/ devel_jffs2/build.log I see: No activity matches FlipSticks No activity matches CartoonBuilder I am the developer of both of these activities and believe I've done everything I am supposed to to get them included. I'm obviously missing something though. Can anyone explain what these errors mean and what I should be doing to resolve them? flipsticks-1.xo != FlipSticks-1.xo cartoon-builder-1.xo != CartoonBuilder-1.xo - Bert - ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
[sugar] joyride logs
What is the secret to turning on reliable logs in Joyride? ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] Joyride
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Fri, 26 Oct 2007 at 10:03:55 -0400, Michael Stone wrote: 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. It seems to work for me, but just for clarification: I understand that if a Fedora contributor builds an RPM in Koji for the OLPC-2 branch, that will land in the next Joyride build too. Is this correct? Does this apply to all packages with an OLPC-2 branch, or just the ones explicitly listed in pilgrim? Is there a Trac component against which we can file bugs of the form please apply attached patch to pilgrim, or do we just use distro? Who should we assign those bugs to? Simon -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: OpenPGP key: http://www.pseudorandom.co.uk/2003/contact/ or pgp.net iD8DBQFHIfmOWSc8zVUw7HYRAj4FAKCaflvioIvJnMBkZVJB3iZ8OlsexgCdHWvW BqilM2FOKhn6H23/SKeWJoQ= =fBGH -END PGP SIGNATURE- ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] Joyride
On Fri, Oct 26, 2007 at 03:28:31PM +0100, Simon McVittie wrote: It seems to work for me, but just for clarification: I understand that if a Fedora contributor builds an RPM in Koji for the OLPC-2 branch, that will land in the next Joyride build too. Is this correct? Packages listed in pilgrim will also be pulled from the OLPC-2 branch in Fedora's Koji. Is there a Trac component against which we can file bugs of the form please apply attached patch to pilgrim, or do we just use distro? Who should we assign those bugs to? Assign the bugs to me until further notice. (mstone) There should be a build-system component in Trac. If there's not, one will appear shortly. Michael ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] Joyride
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:
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 -
___
Sugar mailing list
Sugar@lists.laptop.org
http://lists.laptop.org/listinfo/sugar
[sugar] 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 - ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] Joyride
On 10/25/07, Bert Freudenberg [EMAIL PROTECTED] wrote: Could someone *please* explain and document the current process of getting RPMs and XO bundles into the build? I don't have answers, but I do have clues. https://dev.laptop.org/ticket/4441 links to https://dev.laptop.org/ticket/4251 ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] Joyride
On Oct 25, 2007, at 10:32 , Erik Blankinship wrote: On 10/25/07, Bert Freudenberg [EMAIL PROTECTED] wrote: Could someone *please* explain and document the current process of getting RPMs and XO bundles into the build? I don't have answers, but I do have clues. https://dev.laptop.org/ticket/4441 links to https://dev.laptop.org/ticket/4251 Thanks Eric - I've been gathering clues too and I think I actually have an understanding, but still, some official policy is necessary. Also I'm tired of explaining the state of affairs to other developers who do not follow the lists and bug trackers and IRC discussions as closely - I just want a page I can point them to. - Bert - ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] Joyride package log
On 10/19/07, Bert Freudenberg [EMAIL PROTECTED] wrote: This now shows the latest changelog entry for rpms in the joyride repo, too: http://dev.laptop.org/~bert/joyride-pkgs Unfortunately, sugar rpms do not have sensible change log entries. Enjoy anyway. I can fix the scripts to put NEWS in the rpm changelog but afaik the plan is to have a separate changelog inside public_rpms. Marco ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] Joyride package log
This now shows the latest changelog entry for rpms in the joyride repo, too: http://dev.laptop.org/~bert/joyride-pkgs Unfortunately, sugar rpms do not have sensible change log entries. Enjoy anyway. - Bert - On Oct 17, 2007, at 2:31 , Bert Freudenberg wrote: It's right there: http://dev.laptop.org/~bert/joyride-diffpkgs.sh Though it is not perfect - doesn't deal with failed builds too well. - Bert - On Oct 17, 2007, at 2:21 , Michael Stone wrote: Go Bert! Can you please publish this script so we can see if we can include it directly in the build process? Thanks, Michael On Wed, Oct 17, 2007 at 02:01:23AM +0200, Bert Freudenberg wrote: I made a little script to list package changes between joyride builds: http://dev.laptop.org/~bert/joyride-pkgs Enjoy! - Bert - ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
[sugar] Joyride package log
I made a little script to list package changes between joyride builds: http://dev.laptop.org/~bert/joyride-pkgs Enjoy! - Bert - ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] Joyride package log
Go Bert! Can you please publish this script so we can see if we can include it directly in the build process? Thanks, Michael On Wed, Oct 17, 2007 at 02:01:23AM +0200, Bert Freudenberg wrote: I made a little script to list package changes between joyride builds: http://dev.laptop.org/~bert/joyride-pkgs Enjoy! - Bert - ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] Joyride package log
It's right there: http://dev.laptop.org/~bert/joyride-diffpkgs.sh Though it is not perfect - doesn't deal with failed builds too well. - Bert - On Oct 17, 2007, at 2:21 , Michael Stone wrote: Go Bert! Can you please publish this script so we can see if we can include it directly in the build process? Thanks, Michael On Wed, Oct 17, 2007 at 02:01:23AM +0200, Bert Freudenberg wrote: I made a little script to list package changes between joyride builds: http://dev.laptop.org/~bert/joyride-pkgs Enjoy! - Bert - ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
