Re: [IAEP] [Sugar-devel] Sugar Trisquel image Ready for testing.

On 23/11/2020, James Cameron wrote: > Or the adding the pulseaudio package is not the right way to convince > GStreamer to work with ALSA. > [...] if you can find out how TOAST did this, it could then be done in > Sugar Live Build. OK, I'll have a look at that. Always happy to get rid of

Re: [IAEP] [Sugar-devel] Sugar Trisquel image Ready for testing.

On Mon, Nov 23, 2020 at 05:15:35AM +0100, Martin Guy wrote: > Thanks. I'm flattered that my previous email became the release > announcement! > > On 23/11/2020, James Cameron wrote: > > On Sun, Nov 22, 2020 at 08:03:02AM +0100, Martin Guy wrote: > >> - The alsa "Headphone" control is muted, so

Re: [IAEP] [Sugar-devel] Sugar Trisquel image Ready for testing.

Thanks. I'm flattered that my previous email became the release announcement! On 23/11/2020, James Cameron wrote: > On Sun, Nov 22, 2020 at 08:03:02AM +0100, Martin Guy wrote: >> - The alsa "Headphone" control is muted, so no sound comes out of >> external speakers. "alsactl init" fixes this

Re: [IAEP] [Sugar-devel] Sugar Trisquel image Ready for testing.

On Sun, Nov 22, 2020 at 08:03:02AM +0100, Martin Guy wrote: > First, thanks to all who have made Trisquel On A Stick TOAST a reality > (as well as being the first little-endian recursive acronym I've seen) > > It achieves almost all of the goals I had for "Sugar Live Everything": > - It works on

Re: [IAEP] [Sugar-devel] Sugar Trisquel image Ready for testing.

Updated link: https://wiki.sugarlabs.org/go/Trisquel_On_A_Sugar_Toast On Sun, Nov 22, 2020 at 11:01 AM Frederick Grose wrote: > Thank you Martin for seeing this through to a solution! > > Would you consider simplifying and updating the Trisquel on a Sugar Toast > page on the Sugar Labs wiki? >

Re: [IAEP] [Sugar-devel] Sugar Trisquel image Ready for testing.

Thank you Martin for seeing this through to a solution! Would you consider simplifying and updating the Trisquel on a Sugar Toast page on the Sugar Labs wiki? https://wiki.sugarlabs.org/go/Trisquel_On_A_Sugar_Toast Your efforts will reward many. On

Re: [IAEP] [Sugar-devel] Sugar Trisquel image Ready for testing.

> First, thanks to all who have made Trisquel On A Stick TOAST a reality Trisquel on a Sugar TOAST. Gnash! ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep

Re: [IAEP] [Sugar-devel] Sugar Trisquel image Ready for testing.

First, thanks to all who have made Trisquel On A Stick TOAST a reality (as well as being the first little-endian recursive acronym I've seen) It achieves almost all of the goals I had for "Sugar Live Everything": - It works on 32-bit machines - It has lots of Activities - It autostarts if you

Re: [IAEP] [Sugar-devel] Sugar Trisquel image Ready for testing.

Present at http://us.archive.trisquel.info/iso/trisquel-sugar_9.0_i686.iso ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep

Re: [IAEP] [Sugar-devel] Sugar Trisquel image Ready for testing.

On 19/11/2020, Ruben wrote: > The i386 image was produced at the same time as the amd64 one, and is > available at > https://cdimage.trisquel.info/trisquel-images/trisquel-sugar_9.0_i386.iso 404 Not Found and the 64-bit image has also disappeared. M

Re: [IAEP] [Sugar-devel] Sugar Trisquel image Ready for testing.

On 20/11/2020, Martin Guy wrote: > On 19/11/2020, Ruben wrote: >> On 11/4/20 4:34 PM, Martin Guy wrote: >>> I have managed to get all the Activities in Etiona installed. >> Could you describe your overall build goal? > > I am hoping that the Trisquel 386 image achieves this goal and look >

Re: [IAEP] [Sugar-devel] Sugar Trisquel image Ready for testing.

On 19/11/2020, Ruben wrote: > On 11/4/20 4:34 PM, Martin Guy wrote: >> I have managed to get all the Activities in Etiona installed. > Could you describe your overall build goal? My goal was a Sugar live system with lots of activities that works on 32-bit hardware, which is the cheapest for poor

Re: [IAEP] [Sugar-devel] Sugar Trisquel image Ready for testing.

On Wed, Nov 04, 2020 at 04:34:23PM +0100, Martin Guy wrote: > The awkward ones were Music Keyboard in Python3, which needs the > python ctcsound module, that is only available for Python2 in > Debian, but it is Python version agnostic so I fish it out and copy > it into /usr/lib/python3.7, Yes,

Re: [IAEP] [Sugar-devel] Sugar Trisquel image Ready for testing.

On Tue, 3 Nov 2020 at 23:01, James Cameron wrote: > On Tue, Nov 03, 2020 at 02:16:27PM +0100, Martin Guy wrote: > > I notice that Music Blocks isn't in the Trisquel Etiona set > Music Blocks doesn't run as a Sugar activity yet. OK, thanks. > > Of the other activities, I couldn't make Develop do

Re: [IAEP] [Sugar-devel] Sugar Trisquel image Ready for testing.

On Tue, Nov 03, 2020 at 02:16:27PM +0100, Martin Guy wrote: > I notice that Music Blocks isn't in the Trisquel Etiona set, and it > seems a prime candidate for inclusion. Music Blocks doesn't run as a Sugar activity yet. Walter would be best person to ask about that. > Of the other activities,

Re: [IAEP] [Sugar-devel] Sugar Trisquel image Ready for testing.

Music Blocks was made to run from a browser and it currently fails to start in sugar, there's an open issue for it https://github.com/sugarlabs/musicblocks/issues/2579. When you say "Couldn't make Develop do anything useful" I'm guessing you mean you couldn't use the activity, the activity helps

Re: [IAEP] [Sugar-devel] Sugar Trisquel image Ready for testing.

On 03/11/2020, Chihurumnaya Ibiam wrote: > On Sat, Oct 31, 2020 at 11:20 AM Martin Guy wrote: >> > the included activities are: >> > >> > abacus >> > analyzejournal >> > browse >> > calculate >> > ... >> >> I've been looking at what activities to include in a Sugar Live >> Everything i386

Re: [IAEP] [Sugar-devel] Sugar Trisquel image Ready for testing.

On Sat, Oct 31, 2020 at 11:20 AM Martin Guy wrote: > > the included activities are: > > > > abacus > > analyzejournal > > browse > > calculate > > ... > > I've been looking at what activities to include in a Sugar Live > Everything i386 release, but it looks like you've made my task easier. >

Re: [IAEP] [Sugar-devel] Sugar Trisquel image Ready for testing.

Yes the metadistro still provides i386. -- Ibiam Chihurumnaya ibiamchihurumn...@gmail.com On Sat, Oct 31, 2020 at 9:06 AM Martin Guy wrote: > Does the metadistro it's based on still provide i386? > If so, making a 32-bit image should be a doddle. If not... > >M >

Re: [IAEP] [Sugar-devel] Sugar Trisquel image Ready for testing.

It might be a worthwhile exercise to come up with a consistent naming convention :P On Sat, Oct 31, 2020 at 6:20 AM Martin Guy wrote: > > > the included activities are: > > > > abacus > > analyzejournal > > browse > > calculate > > ... > > I've been looking at what activities to include in a

Re: [IAEP] [Sugar-devel] Sugar Trisquel image Ready for testing.

> the included activities are: > > abacus > analyzejournal > browse > calculate > ... I've been looking at what activities to include in a Sugar Live Everything i386 release, but it looks like you've made my task easier. Shall I call it Sugar Live Trisqel in honour of the Activity selection or do

Re: [IAEP] [Sugar-devel] Sugar Trisquel image Ready for testing.

Does the metadistro it's based on still provide i386? If so, making a 32-bit image should be a doddle. If not... M ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep

Re: [IAEP] [Sugar-devel] Sugar Trisquel image Ready for testing.

The 64bit seems to be just amd64. -- Ibiam Chihurumnaya ibiamchihurumn...@gmail.com On Thu, Oct 29, 2020 at 8:38 PM Martin Guy wrote: > Excellent! Only amd64? :) > >M > > On 29/10/2020, Chihurumnaya Ibiam wrote: > > Hi Everyone, > > > > The sugar trisquel image has been released > > <

Re: [IAEP] [Sugar-devel] Sugar Trisquel image Ready for testing.

Excellent! Only amd64? :) M On 29/10/2020, Chihurumnaya Ibiam wrote: > Hi Everyone, > > The sugar trisquel image has been released > > by Ruben and it needs to be tested. > > He'd said this earlier; > > It took