Re: [Sugar-devel] [SoaS] Help soas is not building in fedora30 rawhide

[James Cameron]

On Fri, Nov 16, 2018 at 05:23:44PM -0500, Frederick Grose wrote:
> On Thu, Nov 15, 2018 at 5:03 PM Thomas Gilliard  wrote:
> >
> > Helpsoas is not building in fedora30 rawhide
> 
> The livemedia.log shows this error report:

Thanks for finding that, I had no idea where it would be.

> ...
> 2018-11-16 17:02:07,578 INFO pylorax: Non interactive installation failed:
> 2018-11-16 17:02:07,579 INFO pylorax: Problem: conflicting requests
> 2018-11-16 17:02:07,579 INFO pylorax: - nothing provides
> ld-linux-armhf.so.3 needed by sugar-pippy-72-1.fc30.x86_64
> 2018-11-16 17:02:07,579 INFO pylorax: - nothing provides
> ld-linux-armhf.so.3(GLIBC_2.4) needed by sugar-pippy-72-1.fc30.x86_64
> 2018-11-16 17:02:07,579 INFO pylorax: - nothing provides
> libgcc_s.so.1(GCC_3.5) needed by sugar-pippy-72-1.fc30.x86_64
> 2018-11-16 17:02:07,579 INFO pylorax: - nothing provides
> libstdc++.so.6(CXXABI_ARM_1.3.3) needed by
> sugar-pippy-72-1.fc30.x86_64.

An architecture mixup.

Cause is the Fedora package for x86_64 contains ARM architecture files
in library/box2d_arm/, which in turn are in the tar.gz, also in the
.xo file, and also in git.

Fixes might be one of;

1.  adjust the package to remove the binaries, and add box2d
dependencies, or;

2.  maintain a fork of the sources without dependencies embedded, as
we've done for the Physics activity (see the dfsg branch there).

> 2018-11-16 17:02:07,579 INFO pylorax:
> 2018-11-16 17:02:07,579 INFO pylorax: The installer will now terminate.
> ...

-- 
James Cameron
http://quozl.netrek.org/
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Help soas is not building in fedora30 rawhide

[Frederick Grose]

On Thu, Nov 15, 2018 at 5:03 PM Thomas Gilliard  wrote:
>
> Helpsoas is not building in fedora30 rawhide

The livemedia.log shows this error report:
...
2018-11-16 17:02:07,578 INFO pylorax: Non interactive installation failed:
2018-11-16 17:02:07,579 INFO pylorax: Problem: conflicting requests
2018-11-16 17:02:07,579 INFO pylorax: - nothing provides
ld-linux-armhf.so.3 needed by sugar-pippy-72-1.fc30.x86_64
2018-11-16 17:02:07,579 INFO pylorax: - nothing provides
ld-linux-armhf.so.3(GLIBC_2.4) needed by sugar-pippy-72-1.fc30.x86_64
2018-11-16 17:02:07,579 INFO pylorax: - nothing provides
libgcc_s.so.1(GCC_3.5) needed by sugar-pippy-72-1.fc30.x86_64
2018-11-16 17:02:07,579 INFO pylorax: - nothing provides
libstdc++.so.6(CXXABI_ARM_1.3.3) needed by
sugar-pippy-72-1.fc30.x86_64.
2018-11-16 17:02:07,579 INFO pylorax:
2018-11-16 17:02:07,579 INFO pylorax: The installer will now terminate.
...
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Switching sugarlabs.org to Backdrop CMS

[James Cameron]

Thanks, good question.

In the past year, the changes made to the web site via GitHub have
almost entirely been for style or appearance.

Changes to content have been very rare.

People who we all should expect to provide content, such as Thomas, the
new marketing team, yourself, and the oversight board, have not
provided content.

The Airspace Jekyll theme we use has diverged from the original theme
design, rather than using a cascade, and rather than taking any issues
upstream.

A content management system would help to stop this waste of effort on
style or appearance tweaks.

Backdrop is just one of many.  There are others.

On Fri, Nov 16, 2018 at 11:29:42AM -0500, Walter Bender wrote:
> Could you (or someone) please articulate why you think this will reduce the
> maintenance burden? (I ask with complete ignorance about Backdrop.)
> 
> regards.
> 
> -walter
> 
> On Fri, Nov 16, 2018 at 4:01 AM James Cameron <[1]qu...@laptop.org> wrote:
> 
> Backdrop CMS is a lightweight content management system for
> non-profits.
> 
> Backdrop CMS joined the Software Freedom Conservancy recently, and
> Sugar Labs is also part of SFC.
> 
> Have we any volunteers interested in converting the web site and
> content to Backdrop?  It seems to have all the features needed, and
> may help to release our volunteers to work on more important things,
> such as Music Blocks, Turtle Blocks, Sugarizer, Sugar, or activities.
> 
> Steps;
> 
> * [ ] establish a list of volunteers,
> 
> * [ ] build a list of requirements and acceptance criteria,
> 
> * [ ] check for alternate CMS implementations,
> 
> * [ ] verify we have consensus to proceed,
> 
> * [ ] verify oversight board is in favour,
> 
> * [ ] instantiate the CMS,
> 
> * [ ] copy content from old site,
> 
> * [ ] maintain content.
> 
> --
> James Cameron
> [2]http://quozl.netrek.org/
> ___
> Sugar-devel mailing list
> [3]Sugar-devel@lists.sugarlabs.org
> [4]http://lists.sugarlabs.org/listinfo/sugar-devel
> 
> --
> Walter Bender
> Sugar Labs
> [5]http://www.sugarlabs.org
> [6]
> 
> References:
> 
> [1] mailto:qu...@laptop.org
> [2] http://quozl.netrek.org/
> [3] mailto:Sugar-devel@lists.sugarlabs.org
> [4] http://lists.sugarlabs.org/listinfo/sugar-devel
> [5] http://www.sugarlabs.org/
> [6] http://www.sugarlabs.org/

-- 
James Cameron
http://quozl.netrek.org/
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Switching sugarlabs.org to Backdrop CMS

[Walter Bender]

Could you (or someone) please articulate why you think this will reduce the
maintenance burden? (I ask with complete ignorance about Backdrop.)

regards.

-walter

On Fri, Nov 16, 2018 at 4:01 AM James Cameron  wrote:

> Backdrop CMS is a lightweight content management system for
> non-profits.
>
> Backdrop CMS joined the Software Freedom Conservancy recently, and
> Sugar Labs is also part of SFC.
>
> Have we any volunteers interested in converting the web site and
> content to Backdrop?  It seems to have all the features needed, and
> may help to release our volunteers to work on more important things,
> such as Music Blocks, Turtle Blocks, Sugarizer, Sugar, or activities.
>
> Steps;
>
> * [ ] establish a list of volunteers,
>
> * [ ] build a list of requirements and acceptance criteria,
>
> * [ ] check for alternate CMS implementations,
>
> * [ ] verify we have consensus to proceed,
>
> * [ ] verify oversight board is in favour,
>
> * [ ] instantiate the CMS,
>
> * [ ] copy content from old site,
>
> * [ ] maintain content.
>
> --
> James Cameron
> http://quozl.netrek.org/
> ___
> Sugar-devel mailing list
> Sugar-devel@lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/sugar-devel
>


-- 
Walter Bender
Sugar Labs
http://www.sugarlabs.org

___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

[Sugar-devel] Switching sugarlabs.org to Backdrop CMS

[James Cameron]

Backdrop CMS is a lightweight content management system for
non-profits.

Backdrop CMS joined the Software Freedom Conservancy recently, and
Sugar Labs is also part of SFC.

Have we any volunteers interested in converting the web site and
content to Backdrop?  It seems to have all the features needed, and
may help to release our volunteers to work on more important things,
such as Music Blocks, Turtle Blocks, Sugarizer, Sugar, or activities.

Steps;

* [ ] establish a list of volunteers,

* [ ] build a list of requirements and acceptance criteria,

* [ ] check for alternate CMS implementations,

* [ ] verify we have consensus to proceed,

* [ ] verify oversight board is in favour,

* [ ] instantiate the CMS,

* [ ] copy content from old site,

* [ ] maintain content.

-- 
James Cameron
http://quozl.netrek.org/
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel