Re: [SoaS] Fix Startup issue with F35 SOAS

[Chihurumnaya Ibiam]

I'm still trying to figure out how that happened and I'll try taking a look
when I can.

-- 

Ibiam Chihurumnaya
ibiamchihurumn...@gmail.com




On Sat, Feb 12, 2022 at 9:00 AM Peter Robinson  wrote:

> On Sat, Feb 12, 2022 at 1:40 AM Alex Perez  wrote:
> >
> > There's a fixed Fedora 35 SoaS ISO at
> http://download.sugarlabs.org/soas/Fedora-SoaS-Live-x86_64-F35-20220211.iso
> which I have confirmed is working as expected.
> >
> > The above ISO is 1.2 gigabytes in size.
>
> Great, do we know why/how this slipped through the gaps? For those
> that aren't aware the Fedora schedule for F-36 is at the following
> link. The main date to note is the final freeze on 5th April.
>
> https://fedorapeople.org/groups/schedule/f-36/f-36-key-tasks.html
>
> > Chihurumnaya Ibiam wrote on 2/9/2022 12:37 PM:
> >
> > Hi Everyone,
> >
> > A fix for the fail to start issue on F35 SOAS has been fixed and
> deployed to F35, so an update on an F35 would get the fix, you can view the
> current stable versions for sugar-toolkit-gtk3.
> >
> > --
> >
> > Ibiam Chihurumnaya
> > ibiamchihurumn...@gmail.com
> >
> >
> > ___
> > SoaS mailing list
> > SoaS@lists.sugarlabs.org
> > http://lists.sugarlabs.org/listinfo/soas
>
___
SoaS mailing list
SoaS@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/soas

[SoaS] Fix Startup issue with F35 SOAS

[Chihurumnaya Ibiam]

Hi Everyone,

A fix for the fail to start issue on F35 SOAS has been fixed and deployed
to F35, so an update on an F35 would get the fix, you can view the current
stable versions for sugar-toolkit-gtk3
.

-- 

Ibiam Chihurumnaya
ibiamchihurumn...@gmail.com
___
SoaS mailing list
SoaS@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/soas

Re: [SoaS] Location of Turtle Blocks snapshots within directory structure?

[Chihurumnaya Ibiam]

Good day,

I'm guessing you're trying to save the python code of your current program,
you can save it from
the turtle art activity and it'll be saved in your journal, which you can
open with Pippy activity and copy
the code, save to a file in the terminal and share that file to a host via
any means of your choosing.

Since it's a liveuser each session is lost and you can't use a flash drive,
although that depends on your
VM so you can also easily copy the file.

One reason why it's difficult to save some files outside Sugar is that the
files in Sugar are meant to be run
in Sugar and Sugar creates journal objects and these objects are mostly
linked to tmp files which can be deleted
after they're used.

Hope this helps.

-- 

Ibiam Chihurumnaya
ib...@sugarlabs.org



On Mon, May 24, 2021 at 3:55 AM  wrote:

>
> Hello, I'm using live image Fedora-SoaS-Live-x86_64-32-1.6.iso, which boots 
> into Sugar v0.116. My only motivation for now is to use the Turtle Blocks 
> activity. Turtle Blocks (on a virtualized x86-64 guest on VirtualBox!) runs, 
> as per a thoroughly unscientific benchmark, at least 30x faster than the 
> no-install JavaScript version on a nonvirtualized web browser. Hence this 
> choice of software stack.
>
>
> The problem: I can program, run, debug without a problem; but I can't save my 
> work on any storage outside the Sugar virtual machine. I've installed the 
> Terminal activity, ftp and sftp clients, etc... so it's just a matter of 
> knowing which file I have to squirrel away (or bring back if I'm trying to 
> resume work on
>
> Which files should I be exfiltrating in order to snapshot the current
> state of Turtle
> Blocks? How do I cause those files to be created using the Sugar/Turtle 
> Blocks user interface?
>
> Thanks very much for any information,
> --Ken Irusta
>
> ___
> SoaS mailing list
> SoaS@lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/soas
>
___
SoaS mailing list
SoaS@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/soas

[SoaS] Package Rename of sugar-dimensions Complete

[Chihurumnaya Ibiam]

Hi Everyone,

sugar-visualmatch 
has now been renamed to sugar-dimensions
 and I'll be orphaning
the sugar-visualmatch package ASAP.

-- 

Ibiam Chihurumnaya
ib...@sugarlabs.org
___
SoaS mailing list
SoaS@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/soas

[SoaS] F34 Beta Test

[Chihurumnaya Ibiam]

Hi Everyone,

I recently tested the F34 Beta with the Beta working as expected and all
activities starting and working as expected but two, Typing Turtle and
Memorize.

Typing Turtle starts and the `start lesson` button does nothing and this
error is shown in the logs;

Traceback (most recent call last):
  File "/usr/share/sugar/activities/TypingTurtle.activity/mainscreen.py",
line 262, in lesson_clicked_cb

self.activity.push_screen(lessonscreen.LessonScreen(self.visible_lesson,
self.keyboard_images, self.activity))
  File "/usr/share/sugar/activities/TypingTurtle.activity/lessonscreen.py",
line 141, in __init__
self.keyboard.set_layout(keyboard.get_layout())
  File "/usr/share/sugar/activities/TypingTurtle.activity/keyboard.py",
line 119, in get_layout
if _is_olpcm_model():
  File "/usr/share/sugar/activities/TypingTurtle.activity/keyboard.py",
line 110, in _is_olpcm_model
p = subprocess.Popen(["setxkbmap", "-query"], stdout=subprocess.PIPE)
  File "/usr/lib64/python3.9/subprocess.py", line 951, in __init__
self._execute_child(args, executable, preexec_fn, close_fds,
  File "/usr/lib64/python3.9/subprocess.py", line 1823, in _execute_child
raise child_exception_type(errno_num, err_msg, err_filename)
FileNotFoundError: [Errno 2] No such file or directory: 'setxkbmap'

Fixed in #3
.

Memorize started but couldn't load any games with error;

1617191045.608474 ERROR root: Read: Error parsing file
'xml.etree.ElementTree.Element' object has no attribute 'getchildren'
1617191045.608657 ERROR root:  Reading setup file
/usr/share/sugar/activities/Memorize.activity/demos/addition.zip

(sugar-activity3:3000): Gtk-WARNING **: 12:44:25.198: Drawing a gadget with
negative dimensions. Did you forget to allocate a size? (node menuitem
owner SugarPaletteHeader)
Traceback (most recent call last):
  File "/usr/share/sugar/activities/Memorize.activity/activity.py", line
465, in change_game
self.game.change_game(widget, game_name, size, mode, title, color)
  File "/usr/share/sugar/activities/Memorize.activity/game.py", line 330,
in change_game
size = int(self.model.data['size'])
KeyError: 'size'

Fixed in #31 .

Please test if you can.

-- 

Ibiam Chihurumnaya
ib...@sugarlabs.org
___
SoaS mailing list
SoaS@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/soas

[SoaS] Opened issue to unretire sugar-flipsticks

[Chihurumnaya Ibiam]

Good day,

I've just opened an issue  to unretire
sugar-flipsticks, it should've been updated a while ago but it wasn't and I
just updated it.

-- 

Ibiam Chihurumnaya
ibiamchihurumn...@gmail.com
___
SoaS mailing list
SoaS@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/soas

Re: [SoaS] New 0.118 RPMs for rawhide/F34 are working

[Chihurumnaya Ibiam]

Thanks for testing.

-- 

Ibiam Chihurumnaya
ibiamchihurumn...@gmail.com



On Mon, Jan 25, 2021 at 12:29 AM Alex Perez  wrote:

> Ibiam,
>
> I've downloaded the built RPMs from Fedora Koji at
> https://koji.fedoraproject.org/koji/taskinfo?taskID=60326176 and have
> manually installed them with rpm on my rawhide laptop and can confirm it
> works just fine.
>
> Thanks for making this happen!
>
> Alex
> ___
> SoaS mailing list
> SoaS@lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/soas
>
___
SoaS mailing list
SoaS@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/soas

Re: [SoaS] Remove from distro list please

[Chihurumnaya Ibiam]

Hi Adam,

You can go to http://lists.sugarlabs.org/listinfo/soas and use the
unsubscribe option to unsubscribe.
Regards.

-- 

Ibiam Chihurumnaya
ibiamchihurumn...@gmail.com



On Sat, Jan 23, 2021 at 5:49 PM Adam Payton 
wrote:

> Hi,
>
> Please remove me from distro list now, I no longer need to be on.
>
> Thanks,
> Adam
> ___
> SoaS mailing list
> SoaS@lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/soas
>
___
SoaS mailing list
SoaS@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/soas

Re: [SoaS] Collaboration failure with Fedora rawhide & Sugar 0.116

[Chihurumnaya Ibiam]

I've added patches for both commits
 and will remove
the patches when the package
is updated to 0.118.

-- 

Ibiam Chihurumnaya
ibiamchihurumn...@gmail.com



On Sun, Jan 17, 2021 at 10:09 PM Alex Perez  wrote:

> Ibiam,
>
> When you set the collaboration server to jabber.sugarlabs.org in the
> Network Control Panel within Sugar, it fails to connect to the server,
> with a Python error of "TypeError: Object of type DBusException is not
> JSON serializable"
>
> Full sugar log output at https://termbin.com/z6g0
>
>
___
SoaS mailing list
SoaS@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/soas

Re: [SoaS] Sugar-starchart, flipsticks, labyrinth in Fedora Rawhide fails to install due to no python3 activity port

[Chihurumnaya Ibiam]

I thought I'd already updated sugar-flipsticks as there'd been a new
release for the latest
version which has been ported to Python 3 but it seems I thought wrong,
I'll have fixed it
right now but I can't upload anything to sunjammer as my password has
expired and needs to be reset.

I'd told Peter to retire sugar-labyrinth as there's not been anything done
on it and I don't see that happening
anytime soon, sugar-starchart has an open PR but that's on hold, we can
retire the package and claim it again
if need be.

I agree with retiring sugar-distance and sugar-fototoon.

-- 

Ibiam Chihurumnaya
ibiamchihurumn...@gmail.com



On Sun, Jan 17, 2021 at 9:51 PM Alex Perez  wrote:

> Ibiam,
>
> As of tonight's latest nightly build, sugar-starchart will not install,
> due to the missing python2 toolkit dependency. Are you planning on
> fixing this prior to the release of Fedora 34, which would need to be in
> the next week or two?
>
>
> All of the above activities fail to install for the same reason: the
> missing python2 sugar toolkit dependency:
>
> * sugar-flipsticks
> * sugar-labyrinth
> * sugar-starchart
>
> DNF fails with:
>
>   Problem: conflicting requests
>- nothing provides sugar-toolkit needed by
> sugar-starchart-16-12.fc31.noarch
> (try to add '--skip-broken' to skip uninstallable packages)
>
> Additionally, sugar-distance and sugar-fototoon will install, but does
> not execute properly. Given that sugar-distance doesn't actually work
> properly with non-XO laptpos, I strongly recommend we retire the
> package, and remove it entirely from Rawhide, so it will be properly
> gone in F34. The same goes for the other activities above, if we don't
> expect to fix them in the next week or two.
>
> Regards,
> Alex Perez
>
___
SoaS mailing list
SoaS@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/soas

Re: [SoaS] Collaboration failure with Fedora rawhide & Sugar 0.116

[Chihurumnaya Ibiam]

As James stated, the issue has been fixed in 0.118 and I'll get to updating
our downstream soon.

-- 

Ibiam Chihurumnaya
ibiamchihurumn...@gmail.com



On Sun, Jan 17, 2021 at 10:09 PM Alex Perez  wrote:

> Ibiam,
>
> When you set the collaboration server to jabber.sugarlabs.org in the
> Network Control Panel within Sugar, it fails to connect to the server,
> with a Python error of "TypeError: Object of type DBusException is not
> JSON serializable"
>
> Full sugar log output at https://termbin.com/z6g0
>
>
___
SoaS mailing list
SoaS@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/soas

Re: [SoaS] SOAS 33/34 Changes.

[Chihurumnaya Ibiam]

Thanks for testing, can you share a log of the activity after it fails to
start?

-- 

Ibiam Chihurumnaya
ibiamchihurumn...@gmail.com



On Thu, Jan 14, 2021 at 3:17 AM Alex Perez  wrote:

> I tested today's nightly rawhide of SoaS, and can confirm it behaves as
> expected/desired, with session auto-login. All activities start _except_
> FotoToon.
>
> Downloaded from
> https://kojipkgs.fedoraproject.org/compose/rawhide/Fedora-Rawhide-20210113.n.0/compose/Spins/x86_64/iso/Fedora-SoaS-Live-x86_64-Rawhide-20210113.n.0.iso
>
> SoaS raw-xz for armhfp (Raspberry Pi, etc) image at
> https://kojipkgs.fedoraproject.org/compose/rawhide/Fedora-Rawhide-20210113.n.0/compose/Spins/armhfp/images/Fedora-SoaS-armhfp-Rawhide-20210113.n.0-sda.raw.xz
>
> On 1/13/2021 2:39:25 AM, Chihurumnaya Ibiam 
> wrote:
> Edit made, changes can be viewed in the SoaS download page
> <https://wiki.sugarlabs.org/go/Sugar_on_a_Stick/Downloads>.
>
> --
>
> Ibiam Chihurumnaya
> ibiamchihurumn...@gmail.com
>
>
>
> On Mon, Jan 11, 2021 at 7:07 PM Peter Robinson 
> wrote:
>
>> On Mon, Jan 11, 2021 at 4:56 PM Chihurumnaya Ibiam
>>  wrote:
>> >
>> > Hi Everyone,
>> >
>> > SOAS was failing to build in F34 due to telepathy-salut being
>> deprecated and needed as a dependency in sugar, F33 beta had an issue where
>> startup goes straight to login.
>> >
>> > Both have been fixed after today's compose was released and can be
>> tested.
>> > Download here.
>> >
>> > I don't think it's wise to change the download link in our wiki to
>> reflect this - uploaded to sunjammer of course - as it's a compose image
>> but Peter can tell if it's wise to.
>>
>> The link is for rawhide which is the nightly development snapshots, it
>> might be worthwhile putting a link for those interested in testing
>> that to know the state of SoAS for the next release and be able to
>> test issues with it and provide fixes, there's also an arm  nightly
>> image too.
>>
> ___ SoaS mailing list
> SoaS@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/soas
>
> ___
> SoaS mailing list
> SoaS@lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/soas
>
___
SoaS mailing list
SoaS@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/soas

Re: [SoaS] SOAS 33/34 Changes.

[Chihurumnaya Ibiam]

Edit made, changes can be viewed in the SoaS download page
<https://wiki.sugarlabs.org/go/Sugar_on_a_Stick/Downloads>.

-- 

Ibiam Chihurumnaya
ibiamchihurumn...@gmail.com



On Mon, Jan 11, 2021 at 7:07 PM Peter Robinson  wrote:

> On Mon, Jan 11, 2021 at 4:56 PM Chihurumnaya Ibiam
>  wrote:
> >
> > Hi Everyone,
> >
> > SOAS was failing to build in F34 due to telepathy-salut being deprecated
> and needed as a dependency in sugar, F33 beta had an issue where startup
> goes straight to login.
> >
> > Both have been fixed after today's compose was released and can be
> tested.
> > Download here.
> >
> > I don't think it's wise to change the download link in our wiki to
> reflect this - uploaded to sunjammer of course - as it's a compose image
> but Peter can tell if it's wise to.
>
> The link is for rawhide which is the nightly development snapshots, it
> might be worthwhile putting a link for those interested in testing
> that to know the state of SoAS for the next release and be able to
> test issues with it and provide fixes, there's also an arm  nightly
> image too.
>
___
SoaS mailing list
SoaS@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/soas

[SoaS] SOAS 33/34 Changes.

[Chihurumnaya Ibiam]

Hi Everyone,

SOAS was failing to build in F34 due to telepathy-salut being deprecated
and needed as a dependency in sugar, F33 beta had an issue where startup
goes straight to login.

Both have been fixed after today's compose was released and can be tested.
Download here

.

I don't think it's wise to change the download link in our wiki to reflect
this - uploaded to sunjammer of course - as it's a compose image but Peter
can tell if it's wise to.

-- 

Ibiam Chihurumnaya
ibiamchihurumn...@gmail.com
___
SoaS mailing list
SoaS@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/soas

Re: [SoaS] Issue with telepathy-salut

[Chihurumnaya Ibiam]

On Tue, Dec 22, 2020 at 8:53 PM James Cameron  wrote:

> Summary: you are conflating git patches with diff patches.
>

Agreed, makes sense now.


> On Tue, Dec 22, 2020 at 12:55:49PM +0100, Chihurumnaya Ibiam wrote:
> > telepathy-salut-0.8.1.tar.gz does contain lib/ext/wocky as a
> > directory with files in it and it has the github repo as it's
> > upstream and that doesn't contain lib/ext /wocky as a directory but
> > as a wocky submodule. I don't see a reason why the git submodule is
> > affecting it at the moment
>
> It has affected it because of how you prepared the patch using git
> instead of using diff.
>

Yeah I normally prepare such patches with git as most of the time the
upstream on github is still active.
Now I know different.


> > Yeah I haven't created an PRs as I'm trying to get it to build
> > locally first, you can find the patch here.
>
> The patch is in error because;
>
> (a) it is generated using git(1), and contains no content except
> submodule hashes, yet you are asking to apply using patch(1),
>
> (b) unlike patch0, it does not have complete file paths.
>
> You should generate the patch again, using diff -ru, between two
> clones that have been prepared to the corresponding states.
>

Yeah I will.

>
> > The commit upstream shows that there was a change but the change was
> > to a submodule, the source files from telepathyfreedesktop.org
> > contains lib/ext/wocky but the source on github doesn't and that
> > explains the error from build.log
>
> You should not use the tar.gz from github, because it
>
> (a) does not equal the distributed software; therefore unsupported,
>
> (b) does not contain autoconf prepared source; therefore broken, and
>
> (c) does not have submodules expanded; therefore incomplete.
>
> > I used rpmbuild to build just the %prep section and ls shows there
> > files in lib /ext/wocky but still throws same error when applying
> > the patch and I don't get why right now but I think it's because the
> > patch is pointing to a submodule commit.
>
> No, it is because the patch is not intended for processing by
> patch(1).
>

Yeah, makes sense now.


> The patch(1) command has no clue (or glue) for handling git patches in
> that way.
>

I understand now.


> Hope that helps!
>

Yeah, thanks a lot.

>
> --
> James Cameron
> https://quozl.linux.org.au/



-- 

Ibiam Chihurumnaya
ibiamchihurumn...@gmail.com
___
SoaS mailing list
SoaS@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/soas

Re: [SoaS] Issue with telepathy-salut

[Chihurumnaya Ibiam]

On Mon, Dec 21, 2020 at 9:04 PM James Cameron  wrote:

> I don't believe it, because telepathy-salut-0.8.1.tar.gz does contain
> lib/ext/wocky, and it is a directory which contains files.  There's no
> reason why a git submodule should affect the tar.gz in that way.
>

telepathy-salut-0.8.1.tar.gz does contain lib/ext/wocky as a directory with
files in it
and it has the github repo <https://github.com/TelepathyIM/telepathy-salut>
as it's upstream and that doesn't contain lib/ext/wocky as a directory but
as
a wocky submodule. I don't see a reason why the git submodule is affecting
it at the moment


>
> It seems more likely the patch is in error.  How can I see the patch?
> https://src.fedoraproject.org/ didn't seem to have it.
>

Yeah I haven't created an PRs as I'm trying to get it to build locally
first, you can find the patch here <https://paste.centos.org/view/191e4487>
.

The commit upstream shows that there was a change but the change was to a
submodule,
the source files from telepathyfreedesktop.org contains lib/ext/wocky but
the source on github doesn't and
that explains the error from build.log


> You may place temporary shell commands for diagnosis in the %prep
> section before the %patch1.  Such as ls(1) or file(1).  This will give
> you output in the build log that you can use to diagnose further.
>

I used rpmbuild to build just the %prep section and ls shows there files in
lib/ext/wocky
but still throws same error when applying the patch and I don't get why
right now but I think it's because
the patch is pointing to a submodule commit.


> You should also consider building by hand using rpmbuild, as that will
> speed up your iterations for solving the problem.  Once you have it
> solved, go back to using the Fedora infrastructure to build.
>
> On Mon, Dec 21, 2020 at 04:50:39PM +0100, Chihurumnaya Ibiam wrote:
> > This isn't a problem on my path as I'm not trying to build
> telepathy-salut from
> > the source code so I didn't clone telepathy-salut,
> > building telepathy-salut locally and on koji doesn't work because of
> what I
> > stated above, I should've included the error
> > I got from the build log earlier;
> >
> > Patch #1 (update-wocky-to-fix-openssl1.1-build-issue.patch):
> > + echo 'Patch #1 (update-wocky-to-fix-openssl1.1-build-issue.patch):'
> > + /usr/bin/patch --no-backup-if-mismatch -p1 --fuzz=0
> > File lib/ext/wocky is not a regular file -- refusing to patch
> >
> > You can find the full build log [1]here.
> >
> > The error seems to happen because in the source code, [2]lib/ext/wocky
> is pointing to a particular commit in the wocky submodule,
> >
> > hence the patch failing as that's not a regular file.
> >
> > --
> >
> > Ibiam Chihurumnaya
> > [3]ibiamchihurumn...@gmail.com
> >
> > On Sat, Dec 19, 2020 at 12:43 AM James Cameron <[4]qu...@laptop.org>
> wrote:
> >
> > On Thu, Dec 17, 2020 at 12:52:11PM +0100, Chihurumnaya Ibiam wrote:
> > > Hi Everyone,
> > >
> > > I'm currently working on fixing telepathy-salut to use openssl 1.0
> > > which has been fixed upstream in this [1]commit but the problem is,
> > > lib/ext/wocky points to a particular commit in the wocky submodule
> > > of TelepathyIM hence the patch fails as it isn't a regular file,
> > > it's supposed to be a directory but in this case it's empty as it's
> > > pointing to a particular commit.
> >
> > When the wocky directory is empty, that suggests the submodule has
> not
> > been checked out.
> >
> > > What are the possible ways to fix this?
> >
> > When cloning, use --recurse-submodules.  Or, use `git submodule
> update
> > --init --recursive` after cloning.
> >
> > Should you be preparing a patch for packaging, you can also work
> > around such git problems by using a recursive diff between two clones
> > of wocky.  You may need to tweak the diffs with sed.
> >
> > --
> > James Cameron
> > [5]http://quozl.netrek.org/
> >
> > References:
> >
> > [1]
> https://kojipkgs.fedoraproject.org//work/tasks/1714/57311714/build.log
> > [2]
> https://github.com/TelepathyIM/wocky/tree/64062d2f0119b89d15e7bb0e0f6fa54ec23ff7f8
> > [3] mailto:ibiamchihurumn...@gmail.com
> > [4] mailto:qu...@laptop.org
> > [5] http://quozl.netrek.org/
>
> --
> James Cameron
> https://quozl.linux.org.au/




-- 

Ibiam Chihurumnaya
ibiamchihurumn...@gmail.com
___
SoaS mailing list
SoaS@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/soas

Re: [SoaS] Issue with telepathy-salut

[Chihurumnaya Ibiam]

This isn't a problem on my path as I'm not trying to build telepathy-salut
from the source code so I didn't clone telepathy-salut,
building telepathy-salut locally and on koji doesn't work because of what I
stated above, I should've included the error
I got from the build log earlier;

Patch #1 (update-wocky-to-fix-openssl1.1-build-issue.patch):
+ echo 'Patch #1 (update-wocky-to-fix-openssl1.1-build-issue.patch):'
+ /usr/bin/patch --no-backup-if-mismatch -p1 --fuzz=0
File lib/ext/wocky is not a regular file -- refusing to patch


You can find the full build log here
<https://kojipkgs.fedoraproject.org//work/tasks/1714/57311714/build.log>.

The error seems to happen because in the source code, lib/ext/wocky
<https://github.com/TelepathyIM/wocky/tree/64062d2f0119b89d15e7bb0e0f6fa54ec23ff7f8>
is pointing to a particular commit in the wocky submodule,

hence the patch failing as that's not a regular file.


-- 

Ibiam Chihurumnaya
ibiamchihurumn...@gmail.com



On Sat, Dec 19, 2020 at 12:43 AM James Cameron  wrote:

> On Thu, Dec 17, 2020 at 12:52:11PM +0100, Chihurumnaya Ibiam wrote:
> > Hi Everyone,
> >
> > I'm currently working on fixing telepathy-salut to use openssl 1.0
> > which has been fixed upstream in this [1]commit but the problem is,
> > lib/ext/wocky points to a particular commit in the wocky submodule
> > of TelepathyIM hence the patch fails as it isn't a regular file,
> > it's supposed to be a directory but in this case it's empty as it's
> > pointing to a particular commit.
>
> When the wocky directory is empty, that suggests the submodule has not
> been checked out.
>
> > What are the possible ways to fix this?
>
> When cloning, use --recurse-submodules.  Or, use `git submodule update
> --init --recursive` after cloning.
>
> Should you be preparing a patch for packaging, you can also work
> around such git problems by using a recursive diff between two clones
> of wocky.  You may need to tweak the diffs with sed.
>
> --
> James Cameron
> http://quozl.netrek.org/
>
___
SoaS mailing list
SoaS@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/soas

[SoaS] Issue with telepathy-salut

[Chihurumnaya Ibiam]

Hi Everyone,

I'm currently working on fixing telepathy-salut to use openssl 1.0 which
has been fixed upstream in this commit

but the problem is, lib/ext/wocky points to a particular commit in the
wocky submodule of TelepathyIM hence the patch fails as it isn't a regular
file, it's supposed to be a directory but in this case it's empty as it's
pointing to a particular commit.

What are the possible ways to fix this?

-- 

Ibiam Chihurumnaya
ibiamchihurumn...@gmail.com
___
SoaS mailing list
SoaS@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/soas

Re: [SoaS] Fwd: Retired Fedora packages with maintainers

[Chihurumnaya Ibiam]

Yes it was removed as one of the defaults as it hasn't been ported to
python3 yet,
once it's ported I'll update it and you should get it in the next upgrade.

On Tue, May 12, 2020 at 6:27 PM Thomas Gilliard 
wrote:

> Note that irc works in Soas but is not installed.
> Dnf install in sugar terminal works, then call it in terminal.
>
> On May 12, 2020, at 10:14 AM, Alex Perez  wrote:
>
> 
>
> FYI. See below e-mail. There may be others in the list that I'm unaware of. 
> Ibiam, we should probably get you set up as a maintainer
> for the sugar packages listed below:
>
> Here's a curated list of packages that are/may be relevant to us/SoaS:
>
> rpms/sugar-analyze is retired but does not list 'orphan' in its users
> rpms/sugar-analyze is retired and has the following: 'maintainers': 
> pbrobinson, tuxbrewr, callkalpa
> rpms/sugar-help is retired but does not list 'orphan' in its users
> rpms/sugar-help is retired and has the following: 'maintainers': pbrobinson, 
> callkalpa
> rpms/sugar-presence-service is retired and has the following: 'maintainers': 
> pbrobinson, tomeu
>
> rpms/webkitgtk is retired but does not list 'orphan' in its users
> rpms/webkitgtk is retired and has the following: 'maintainers': pwalter, 
> kevin, tpopela, huzaifas, mso
> rpms/webkitgtk3 is retired but does not list 'orphan' in its users
> rpms/webkitgtk3 is retired and has the following: 'maintainers': phatina, 
> mclasen, pwalter, tpopela 'groups': @gnome-sig
> rpms/webkitgtk4 is retired but does not list 'orphan' in its users
> rpms/webkitgtk4 is retired and has the following: 'maintainers': tpopela, 
> kalev, catanzaro 'groups': @gnome-sig
>
>
>
>
> *From:* Pierre-Yves Chibon  
> *Date:* May 11, 2020 at 11:49 PM
> *To:* devel-annou...@lists.fedoraproject.org
> *Subject:* Retired packages with maintainers
>
> Good Morning Everyone,
>
> A little while ago we have received the request on the infra issue tracker to
> remove all maintainers of retired packages [1].
>
> So today I decided to look at what this would look like and wrote a script 
> that
> queries PDC for the list of all branches on all projects [2], gather from it a
> list of all the packages that are retired on all their branches (so all 
> branches
> are ``active=false``).
> For each of these retired project, it queries dist-git to find out if they 
> still
> have maintainers in addition to the ``orphan`` user.
>
> The outcome of this script can be found there:
>
>   https://pingou.fedorapeople.org/retired_packages_with_maintainers.log
>
>
> Some stats about this:
> - 881 RPM packages are retired and still have maintainers (out of 4322 retired
>   RPMs).
> - 662 of them are not orphaned
> - 42 modules are retired and still have maintainers (out of 42 retired 
> modules).
> - all of them are not orphaned
> - 2 containers are retired and still have maintainers (out of 3 retired
>   containers).
> - all of them are not orphaned
>
> Which brings a couple of questions:
> - Do we have a documented way to mark modules as orphaned or retired?
> - Should we orphan all the RPM packages that are retired but not orphaned?
>
>
> Finally, does everyone agree about the original request: "remove all 
> maintainers
> of retired packages"? Or should we bring this to FESCo?
>
>
> Thanks for your inputs,
>
> Pierre
>
>
> [1] https://pagure.io/fedora-infrastructure/issue/8600
> [2] https://pdc.fedoraproject.org/extras/active_branches.json (8+Mb file)
> ___
> devel-announce mailing list -- devel-annou...@lists.fedoraproject.org
> To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org
> Fedora Code of Conduct: 
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/devel-annou...@lists.fedoraproject.org
>
>
> ___
> SoaS mailing list
> SoaS@lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/soas
>
> ___
> SoaS mailing list
> SoaS@lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/soas
>
___
SoaS mailing list
SoaS@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/soas

Re: [SoaS] Fwd: Retired Fedora packages with maintainers

[Chihurumnaya Ibiam]

I've asked Peter to add me as a maintainer to some of the packages listed
above.

sugar-presence-service was only used by etoys-sugar package which has now
been retired.
webkitgtk4 is now webkit2gtk3 and is still being maintained.

On Tue, May 12, 2020 at 6:14 PM Alex Perez  wrote:

> FYI. See below e-mail. There may be others in the list that I'm unaware of. 
> Ibiam, we should probably get you set up as a maintainer
> for the sugar packages listed below:
>
> Here's a curated list of packages that are/may be relevant to us/SoaS:
>
> rpms/sugar-analyze is retired but does not list 'orphan' in its users
> rpms/sugar-analyze is retired and has the following: 'maintainers': 
> pbrobinson, tuxbrewr, callkalpa
> rpms/sugar-help is retired but does not list 'orphan' in its users
> rpms/sugar-help is retired and has the following: 'maintainers': pbrobinson, 
> callkalpa
> rpms/sugar-presence-service is retired and has the following: 'maintainers': 
> pbrobinson, tomeu
>
> rpms/webkitgtk is retired but does not list 'orphan' in its users
> rpms/webkitgtk is retired and has the following: 'maintainers': pwalter, 
> kevin, tpopela, huzaifas, mso
> rpms/webkitgtk3 is retired but does not list 'orphan' in its users
> rpms/webkitgtk3 is retired and has the following: 'maintainers': phatina, 
> mclasen, pwalter, tpopela 'groups': @gnome-sig
> rpms/webkitgtk4 is retired but does not list 'orphan' in its users
> rpms/webkitgtk4 is retired and has the following: 'maintainers': tpopela, 
> kalev, catanzaro 'groups': @gnome-sig
>
>
>
>
> *From:* Pierre-Yves Chibon  
> *Date:* May 11, 2020 at 11:49 PM
> *To:* devel-annou...@lists.fedoraproject.org
> *Subject:* Retired packages with maintainers
>
> Good Morning Everyone,
>
> A little while ago we have received the request on the infra issue tracker to
> remove all maintainers of retired packages [1].
>
> So today I decided to look at what this would look like and wrote a script 
> that
> queries PDC for the list of all branches on all projects [2], gather from it a
> list of all the packages that are retired on all their branches (so all 
> branches
> are ``active=false``).
> For each of these retired project, it queries dist-git to find out if they 
> still
> have maintainers in addition to the ``orphan`` user.
>
> The outcome of this script can be found there:
>
>   https://pingou.fedorapeople.org/retired_packages_with_maintainers.log
>
>
> Some stats about this:
> - 881 RPM packages are retired and still have maintainers (out of 4322 retired
>   RPMs).
> - 662 of them are not orphaned
> - 42 modules are retired and still have maintainers (out of 42 retired 
> modules).
> - all of them are not orphaned
> - 2 containers are retired and still have maintainers (out of 3 retired
>   containers).
> - all of them are not orphaned
>
> Which brings a couple of questions:
> - Do we have a documented way to mark modules as orphaned or retired?
> - Should we orphan all the RPM packages that are retired but not orphaned?
>
>
> Finally, does everyone agree about the original request: "remove all 
> maintainers
> of retired packages"? Or should we bring this to FESCo?
>
>
> Thanks for your inputs,
>
> Pierre
>
>
> [1] https://pagure.io/fedora-infrastructure/issue/8600
> [2] https://pdc.fedoraproject.org/extras/active_branches.json (8+Mb file)
> ___
> devel-announce mailing list -- devel-annou...@lists.fedoraproject.org
> To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org
> Fedora Code of Conduct: 
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/devel-annou...@lists.fedoraproject.org
>
>
> ___
> SoaS mailing list
> SoaS@lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/soas
>
___
SoaS mailing list
SoaS@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/soas

Re: [SoaS] Urgent need to incorporate patch into sugar-toolkit-gtk3 for F32 SoaS, then request re-spin

[Chihurumnaya Ibiam]

I just opened a PR
 for
the patch.

On Fri, May 1, 2020 at 4:19 PM Alex Perez  wrote:

> Peter,
>
> Peter Robinson 
> May 1, 2020 at 3:42 AM
>
> Alex,
>
>
> What is the process for requesting a re-spin of F32 SoaS? I've
> discovered an unfortunate bug in the release F32 SoaS
> sugar-toolkit-gtk3, and the necessary patch is here:
>
> The process is one of two methods 1) get in a time machine and go back
> to a time prior to release 2) we fix it for Fedora 33.
>
> That's fine, we will definitely want to get it this patch pulled in for
> F33/rawhide, and then in to F32 stable as an update. What I'm really after
> is how _we_ (Sugar Labs) can re-build our own spin, which incorporates this
> fix.
>
> This is why we have a beta release and nightly builds and release
> candidates on the way to GA, to test and get the bugs like this. We
> can push the fix as an update for those that install SoaS but we don't
> have the resources to completely respin the live images just because
> you decided to only test things post release.
>
> Totally understandable, however your tone isn't particularly constructive
> here. Just the facts, please. I'm not asking you to do this work, just
> provide guidance, so _we_ can do this independently.
>
> I'm sorry, but we don't
> have the resource for that, and it's been that way and communicated as
> such since the original SoaS release.
>
> An update will fix it for those running on installed systems just fine.
>
>
> https://github.com/sugarlabs/sugar-toolkit-gtk3/commit/2018c930adae85c18b1c51b5f80836fcad6c392c.patch
>
> This commit can be viewed 
> athttps://github.com/sugarlabs/sugar-toolkit-gtk3/commit/2018c930adae85c18b1c51b5f80836fcad6c392c
>
> Please create a pull request against the package or coordinate with
> Ibiam to get a PR done.
>
> Will do.
>
> I've verified it fixes the problem of not being able to start
> external/downloaded activities, by manually applying it from a running
> LiveCD/ISO environment with patch, then killing jarabe.
>
> I'd also like to request that we add the 'patch' package to the default
> list of installed packages, in the respin.
>
> I don't know what you mean by "default list of installed packages". We
> won't be re-spinning, the F-32 ship has sailed.
>
> literally just add 'patch' as one of the packages installed (in F33)
>
> Peter
>
>
> Alex Perez 
> April 30, 2020 at 4:32 PM
> Peter,
>
> What is the process for requesting a re-spin of F32 SoaS? I've discovered
> an unfortunate bug in the release F32 SoaS sugar-toolkit-gtk3, and the
> necessary patch is here:
>
>
> https://github.com/sugarlabs/sugar-toolkit-gtk3/commit/2018c930adae85c18b1c51b5f80836fcad6c392c.patch
>
> This commit can be viewed at
> https://github.com/sugarlabs/sugar-toolkit-gtk3/commit/2018c930adae85c18b1c51b5f80836fcad6c392c
>
> I've verified it fixes the problem of not being able to start
> external/downloaded activities, by manually applying it from a running
> LiveCD/ISO environment with patch, then killing jarabe.
>
> I'd also like to request that we add the 'patch' package to the default
> list of installed packages, in the respin.
> ___
> SoaS mailing list
> SoaS@lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/soas
>
>
> ___
> SoaS mailing list
> SoaS@lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/soas
>
___
SoaS mailing list
SoaS@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/soas

Re: [SoaS] Fedora 32 Sugar on a Stick (0.116) status/testing

[Chihurumnaya Ibiam]

On Mon, Feb 24, 2020 at 1:35 AM James Cameron  wrote:

> On Mon, Feb 24, 2020 at 12:57:56AM +0100, Chihurumnaya Ibiam wrote:
> > On Sun, Feb 23, 2020 at 9:34 PM James Cameron wrote:
> > > On Sun, Feb 23, 2020 at 11:40:04AM -0800, Alex Perez wrote:
> > > > Testing with the following nightly SoaS Live ISO,
> > > > Fedora-SoaS-Live-x86_64-32-20200222.n.0.iso, the following
> > > > results were observed:
> > >
> > > Thanks for testing.
> > >
> > > > Words (23) - Incompatible with Sugar 0.116, needs to be ported
> > > > to Python 3. I propose removal of the package
> > >
> > > Is ported already.  Use v24.
> >
> > There's an open PR but it failed to build in koji, fixing that.
>
> Interesting.
>
> https://src.fedoraproject.org/rpms/sugar-words/pull-request/1
>
> Yes, I see.  I suggest testing those spec file lines before commit.
> It is wasteful of time and resources to rely on koji to do your tests.
> I recommend testing with rpmbuild.
>

Yeah I do test locally, can't remember the conditions why the PR was opened.


> In particular,
>
> * po/cpp.po was removed,
>
> * rm could use -f to quietly fail if the file is already gone,
>
> > [...]
> > > > Clock (22) - Not sure which version is compatible with 0.116, if
> > > > any.
> > >
> > > Known problem fixed but not yet released.  Use v22 with 0fdfc22
> > > ("Fix fail to start, ModuleNotFoundError, ProgressToolButton")
> >
> > An update was made over 2 weeks ago, it should work fine. Can you
> > provide logs if otherwise.
>
> It's a pretty fundamental mistake by me in v22, so I can't see how it
> would work.  The needed commit is not in rpms/sugar-clock yet.
>

> I forked for OLPC OS.  I've pushed my local branch r22.1 which has a
> tag v22.1 which has the commit.
>
> https://download.sugarlabs.org/sources/honey/Clock/Clock-22.1.tar.bz2
>
>
Thanks.

> [...]
> > > > Will not install, broken dependencies:
> > > > Physics (34) - has py2 dependencies that need to be changed/fixed
> > >
> > > v34 is Python 2.  Use v35 instead.
> > >
> > > For my work using Ubuntu 20.04 the Box2D project had to be
> > > packaged for Python 3.
> >
> > There's an open PR for an update.
>
> Where?  I've looked upstream and in Fedora sources, can't see one.
>

I'd meant Pippy activity
<https://src.fedoraproject.org/rpms/sugar-pippy/pull-request/2#>.

>
> --
> James Cameron
> http://quozl.netrek.org/
>
___
SoaS mailing list
SoaS@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/soas

Re: [SoaS] Fedora 32 Sugar on a Stick (0.116) status/testing

[Chihurumnaya Ibiam]

On Sun, Feb 23, 2020 at 9:34 PM James Cameron  wrote:

> On Sun, Feb 23, 2020 at 11:40:04AM -0800, Alex Perez wrote:
> > Testing with the following nightly SoaS Live ISO,
> > Fedora-SoaS-Live-x86_64-32-20200222.n.0.iso, the following results
> > were observed:
>
> Thanks for testing.
>
> My answers below are on the assumption that Python 2 is not being
> provided by Fedora, despite Red Hat continuing to support it on their
> other products.  Anyone planning to deploy Sugar in a school would add
> Python 2 with Sugar Toolkit and immediately gain access to more
> activities.
>
> > Default-installed activities which fail to start:
> > Visual Match (49) - no longer maintained, now called Dimensions. I
> > propose immediate removal of package.
>
> VisualMatch was renamed to Dimensions.  It is not yet ported.  A
> pull-request is being worked;
>
> https://github.com/sugarlabs/dimensions/pull/16
>
> Fedora could either track the renaming, or use the new source.
>
>
I'd planned on changing the name after the port to python3 is completed and
activity is released.

> Paint (69) - upon start, says it needs to be ported to Python 3,
> > then bails.  Should work?
>
> No, v69 is Python 2 only.  Use v70.
>

Yet to update that.


> > Words (23) - Incompatible with Sugar 0.116, needs to be ported to
> > Python 3. I propose removal of the package
>
> Is ported already.  Use v24.
>

There's an open PR but it failed to build in koji, fixing that.


> > IRC (12) - Incompatible with Sugar 0.116 - Package should be
> > removed, no port to Py3 available
>
> Yes, v12 is Python 2 only.
>

I don't think the package should be removed provided there's an update
upstream.


> > InfoSlicer (version 25) - Incompatible with Sugar 0.116 - Package
> > should be removed, no port to Py3 available
>
> Yes, v25 is Python 2 only.
>
> > Get Books (18.2) - Py3 version is 19, needs to be upgraded in
> > package if we want to keep it
>
> No, v19 is Python 2 only.  It is not yet ported.  A pull-request is
> being worked;
>
> https://github.com/sugarlabs/get-books-activity/pull/31
>
> > FotoToon (23.1) - This version should work, but doesn't seem
> > to. Requires investigation or removal
>
> No, v23.1 is Python 2 only.  Use v25.
>

Added to TODO list.


> > Finance (14), needs to be upgraded to 15 for Sugar 0.116+
>
> Yes, v14 is Python 2 only.  Use v15.
>
> > Clock (22) - Not sure which version is compatible with 0.116, if
> > any.
>
> Known problem fixed but not yet released.  Use v22 with 0fdfc22 ("Fix
> fail to start, ModuleNotFoundError, ProgressToolButton")
>

An update was made over 2 weeks ago, it should work fine. Can you provide
logs if otherwise.

>
> > Distance (version 36),  Should work, doesn't seem to start. Requires
> > investigation.
>
> No, shouldn't work, as v36 is Python 2 only.  It is one of the very
> difficult activities to port, since it requires two laptops.  It can't
> be done with virtual machines.
>
> > Log (41) - Fails on start-up with AttributeError, ideally should be
> > ported to python 3.
>
> No, v41 is Python 3 already, and should work.  Does work on Ubuntu
> 20.04 beta.  Sounds like you have a Fedora specific error to diagnose.
>

I agree with James.

>
> The dependencies are unusual for this activity; check you have covered
> them properly.  On Ubuntu 20.04 the dependencies include;
>
> python3, python3-sugar3, python3-gi, python3-urllib3,
> gir1.2-glib-2.0, gir1.2-gtk-3.0, gir1.2-pango-1.0,
> net-tools, procps
>

Thanks, I'll update the dependency list.


> > Activities which start and work:
> > Abacus (61), Browse (204), Terminal (47), Typing Turtle (32), Chat
> > (86), Maze (29), Moon (19), Memorize, Record (201), Read (123),
> > Image Viewer (65), Jukebox (36), Memorize (57), Portfolio (52), Read
> > (123), Speak (58), StopWatch, Story (20), TurtleBlocks (220), Typing
> > Turtle (32) Write (101), Calculate (46), Jukebox (36), Measure (103)
> >
> > Not installed by default, does not start once installed:
> > Hello World (version 6)
>
> v7 is Python 2.  Port was done.  Next version should be Python 3.
>
> > FractionBounce (version 25, needs to be updated to 28)
>
> Yes.
>
> > ColorDeducto (7) - incompatible with Sugar 0.112+, must be removed
>
> Or use the next version.  v7 is Python 2.  Port was done.  Next version
> should be Python 3.
>
> > Nutrition (py2 only)
>
> v15 is Python 2.  Port was done.  Next version should be Python 3.
>
> > Pukklanapac (py2 only)
>
> v13 is Python 2.  It is not yet ported.  A pull-request is
> being worked;
>
> https://github.com/sugarlabs/pukllanapac/pull/10
>
> > Ruler 33 (py2 only)
>
> v33 is Python 2.  It is not yet ported.
>
> > LocoSugar (v11, py2 only)
>
> v11 is Python 2.  It is not yet ported.
>
> > Recall (py2 only, telepathy issue)
>
> v6 is Python 2.  It is not yet ported.


Added activities to  todo list, I'd missed some of them.

>
> > Will not install, broken dependencies:
> > Physics (34) - has py2 dependencies that need to be changed/fixed
>
> v34 is Python 2.  

Re: [SoaS] Sugar on Fedora 31

[Chihurumnaya Ibiam]

I looked at the sugar repo in the fedora sources repository and noticed
that the sugar version is still v0.114,
I'm not good with packaging but I can help apply patches up to the latest
version - v0.116 -, I'd like to know
how applying patches works. Thanks.

--

Ibiam Chihurumnaya
ibiamchihurumn...@sugarlabs.org 



On Fri, Oct 18, 2019 at 9:10 AM Peter Robinson  wrote:

> Hi All,
>
> Just a reminder we're in final freeze for Fedora 31, I'm assuming
> people are testing it.
>
> Just a reminder you can get the latest nightly composes here:
>
> https://kojipkgs.fedoraproject.org/compose/branched/latest-Fedora-31/compose/Spins/x86_64/iso/
>
> https://kojipkgs.fedoraproject.org/compose/branched/latest-Fedora-31/compose/Spins/armhfp/images/
>
> We have slipped a week so if there's fixes needed we basically need
> them by Monday.
>
> Peter
> ___
> SoaS mailing list
> SoaS@lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/soas
>
___
SoaS mailing list
SoaS@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/soas