[OLPC_Boston] OLPC_Boston Digest, Vol 16, Issue 3

[MIKE H.]

hi everyone

i'm sorry to be asking here but, i was wondering if anyone knew what to do
when your developers key won't install. I typed in su to get root and then
copied and pasted the wget link to download the file. It doesn't download
though, and instead the screen goes directly to saying that the download is
finished. I tried to download a new copy from my XO, but i was simply given
a link to my old activation key. I was wondering if maybe the link is bad?

I am asking this question here because I would like to try out F11 on my
XO-1

any help/suggestion would be greatly appreciated

-mike


On Wed, Aug 12, 2009 at 12:00 PM, <olpc_boston-request at lists.laptop.org>wrote:

> Send OLPC_Boston mailing list submissions to
>        olpc_boston at lists.laptop.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
>        http://lists.laptop.org/listinfo/olpc_boston
> or, via email, send a message with subject or body 'help' to
>        olpc_boston-request at lists.laptop.org
>
> You can reach the person managing the list at
>        olpc_boston-owner at lists.laptop.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of OLPC_Boston digest..."
>
>
> Today's Topics:
>
>   1. Re: Gathering Sugar feedback [Was: Re: Another F11        build for
>      the XO-1 has been released] (Caroline Meeks)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Tue, 11 Aug 2009 22:52:48 -0400
> From: Caroline Meeks <caroline at solutiongrove.com>
> Subject: Re: [OLPC_Boston] Gathering Sugar feedback [Was: Re: Another
>        F11     build for the XO-1 has been released]
> To: Mel Chua <mel at melchua.com>
> Cc: olpc_boston at lists.laptop.org, Gary C Martin
>        <gary at garycmartin.com>, smparrish at gmail.com
> Message-ID:
>        <b74fba2b0908111952r53ce425avac2caa9956cb3e66 at mail.gmail.com>
> Content-Type: text/plain; charset="iso-8859-1"
>
> Yes, I'm very interested in how to better track issues that involve changes
> at the Fedora level.
> Not totally following whats going on below. Any advice/todos come out of
> it?
>
> Thanks,
> Caroline
>
> On Fri, Aug 7, 2009 at 2:06 AM, Mel Chua <mel at melchua.com> wrote:
>
> > If it's a bug in the Sugar code, it should absolutely go into the Sugar
> > trac (dev.sugarlabs.org) - I believe the case Gary was mentioning was a
> > bug in Fedora discovered while using Sugar (running on top of Fedora).
> >
> > In any case, it sounds like the three of us aren't in much of a position
> > to tackle this problem, but a deployment hacker working with students
> > during the school year may be. Copying the Boston list, since there are
> > several groups working or planning to work with schools directly who
> > might have someone interested in taking on the specific problem of a
> > bugtracking workflow/interface for the coming semester.
> >
> > --Mel
> >
> > On 08/06/2009 06:02 AM, Steven M. Parrish wrote:
> > >>> How would you like to receive (potential) bug feedback, via Fedora
> > >>> tickets, or just via the mail list? Initial report chit chat usually
> > >>> starts out as an email or two, but if via trac, do you have a
> 'parent'
> > >>> tracker ticket I should reference so all tickets end up linked to one
> > >>> tracker ticket you can see/reference?
> > >>>
> > >>> I'm just cc:ing Mel (Hi Mel), on this as tackling Fedora
> > >>> feedback/tickets is a fairly incessant, buzz/hum in a room fairly
> empty
> > >>> of elegant solutions, so far.
> > >> Yep. Gary and I have been talking
> > >> (
> >
> http://blog.melchua.com/2009/08/06/downstream-sugar-labs-reporting-fedora-
> > >> tickets/) about it in the context of working on a downstream project
> > (Sugar
> > >> Labs) that finds Fedora bugs occasionally but isn't sure how to report
> > them
> > >> up, and the Websites list has also recently had a 'ticket workflow is
> > >> confusing' conversation too
> > >> (
> >
> https://www.redhat.com/archives/fedora-websites-list/2009-August/msg00004.
> > >> html)
> > >>
> > >> --Mel
> > >
> > > The two of you bring up some very valid issues on bug reporting for
> Sugar
> > and
> > > Fedora.  To me this seems like something that needs to be addressed as
> > our
> > > target audience (children) will be very confused.  Off the top of my
> head
> > this
> > > is a quick idea.
> > >
> > > We need a simple bug reporting tool to live either at laptop.org or
> > > sugarlabs.org.  Normally in FedoraLand bugs reported against a Sugar
> > component
> > > would be referred to the upstream devs anyway.   Until this can be
> > realized
> > > maybe we should just use the trak instance at laptop.org.
> > >
> > > This needs alot more thought.
> > >
> > > Steven
> > >
> > >
> > > =====================================================
> > > Steven M. Parrish
> > >
> >
> -------------------------------------------------------------------------------------------------
> > > gpg fingerprint: 4B6C 8357 059E B7ED 8095 0FD6 1F4B EDA0 A9A6 13C0
> > > http://tuxbrewr.fedorapeople.org/
> > > irc.freenode.net: SMParrish @ #fedora-kde, #fedora-devel,
> #fedora-olpc,
> > #sugar
> > _______________________________________________
> > OLPC_Boston mailing list
> > OLPC_Boston at lists.laptop.org
> > http://lists.laptop.org/listinfo/olpc_boston
> >
>
>
>
> --
> Caroline Meeks
> Solution Grove
> Caroline at SolutionGrove.com
>
> 617-500-3488 - Office
> 505-213-3268 - Fax
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL:
> http://lists.laptop.org/pipermail/olpc_boston/attachments/20090811/69a8eaf8/attachment-0001.htm
>
> ------------------------------
>
> _______________________________________________
> OLPC_Boston mailing list
> OLPC_Boston at lists.laptop.org
> http://lists.laptop.org/listinfo/olpc_boston
>
>
> End of OLPC_Boston Digest, Vol 16, Issue 3
> ******************************************
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.laptop.org/pipermail/olpc_boston/attachments/20090817/cf23ddfb/attachment.htm