<html theme="default-light"><head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head><body text="#000000">Peter,<span></span><br>
<blockquote type="cite"
cite="mid:CALeDE9No=Vg==q=o90zy6jdVK6qxEhWLjQsMuOsGbdWNH3+ZCQ@mail.gmail.com"
style="border: 0px none ! important;">
<div xmlns="http://www.w3.org/1999/xhtml" class="__pbConvHr"
style="margin:30px 25px 10px 25px;"><div
style="width:100%;border-top:2px solid
rgba(146,154,163,0.7);padding-top:10px;"> <div
style="display:inline-block;white-space:nowrap;vertical-align:middle;width:49%;">
<a style="color:#485664
!important;padding-right:6px;font-weight:500;text-decoration:none
!important;" href="mailto:pbrobinson@gmail.com" moz-do-not-send="true">Peter
Robinson</a></div> <div
style="display:inline-block;white-space:nowrap;vertical-align:middle;width:48%;text-align:
right;"> <font color="#909AA4"><span style="padding-left:6px">May
1, 2020 at 3:42 AM</span></font></div> </div></div>
<div xmlns="http://www.w3.org/1999/xhtml" class="__pbConvBody"
__pbrmquotes="true"
style="color:#909AA4;margin-left:24px;margin-right:24px;"><pre wrap="">Alex,
</pre><blockquote type="cite"><pre wrap="">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:
</pre></blockquote><pre wrap="">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.</pre></div>
</blockquote>
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.<br>
<blockquote type="cite"
cite="mid:CALeDE9No=Vg==q=o90zy6jdVK6qxEhWLjQsMuOsGbdWNH3+ZCQ@mail.gmail.com"
style="border: 0px none ! important;">
<div xmlns="http://www.w3.org/1999/xhtml" class="__pbConvBody"
__pbrmquotes="true"
style="color:#909AA4;margin-left:24px;margin-right:24px;">
<pre wrap="">
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. </pre>
</div>
</blockquote>
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.<br>
<blockquote type="cite"
cite="mid:CALeDE9No=Vg==q=o90zy6jdVK6qxEhWLjQsMuOsGbdWNH3+ZCQ@mail.gmail.com"
style="border: 0px none ! important;">
<div xmlns="http://www.w3.org/1999/xhtml" class="__pbConvBody"
__pbrmquotes="true"
style="color:#909AA4;margin-left:24px;margin-right:24px;">
<pre wrap="">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.</pre>
</div>
</blockquote>
<blockquote type="cite"
cite="mid:CALeDE9No=Vg==q=o90zy6jdVK6qxEhWLjQsMuOsGbdWNH3+ZCQ@mail.gmail.com"
style="border: 0px none ! important;">
<div xmlns="http://www.w3.org/1999/xhtml" class="__pbConvBody"
__pbrmquotes="true"
style="color:#909AA4;margin-left:24px;margin-right:24px;">
<pre wrap="">
An update will fix it for those running on installed systems just fine.
</pre>
<blockquote type="cite"><pre wrap=""><a class="moz-txt-link-freetext" href="https://github.com/sugarlabs/sugar-toolkit-gtk3/commit/2018c930adae85c18b1c51b5f80836fcad6c392c.patch">https://github.com/sugarlabs/sugar-toolkit-gtk3/commit/2018c930adae85c18b1c51b5f80836fcad6c392c.patch</a>
This commit can be viewed at
<a class="moz-txt-link-freetext" href="https://github.com/sugarlabs/sugar-toolkit-gtk3/commit/2018c930adae85c18b1c51b5f80836fcad6c392c">https://github.com/sugarlabs/sugar-toolkit-gtk3/commit/2018c930adae85c18b1c51b5f80836fcad6c392c</a>
</pre></blockquote><pre wrap="">Please create a pull request against the package or coordinate with
Ibiam to get a PR done.</pre></div>
</blockquote>
Will do.
<blockquote type="cite"
cite="mid:CALeDE9No=Vg==q=o90zy6jdVK6qxEhWLjQsMuOsGbdWNH3+ZCQ@mail.gmail.com"
style="border: 0px none ! important;">
<div xmlns="http://www.w3.org/1999/xhtml" class="__pbConvBody"
__pbrmquotes="true"
style="color:#909AA4;margin-left:24px;margin-right:24px;"><blockquote
type="cite"><pre wrap="">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.
</pre></blockquote><pre wrap="">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.</pre></div>
</blockquote>
literally just add 'patch' as one of the packages installed (in F33)<br>
<blockquote type="cite"
cite="mid:CALeDE9No=Vg==q=o90zy6jdVK6qxEhWLjQsMuOsGbdWNH3+ZCQ@mail.gmail.com"
style="border: 0px none ! important;">
<div xmlns="http://www.w3.org/1999/xhtml" class="__pbConvBody"
__pbrmquotes="true"
style="color:#909AA4;margin-left:24px;margin-right:24px;">
<pre wrap="">
Peter
</pre>
</div>
<div xmlns="http://www.w3.org/1999/xhtml" class="__pbConvHr"
style="margin:30px 25px 10px 25px;"><div
style="width:100%;border-top:2px solid
rgba(146,154,163,0.7);padding-top:10px;"> <div
style="display:inline-block;white-space:nowrap;vertical-align:middle;width:49%;">
<a style="color:#485664
!important;padding-right:6px;font-weight:500;text-decoration:none
!important;" href="mailto:aperez@alexperez.com" moz-do-not-send="true">Alex
Perez</a></div> <div
style="display:inline-block;white-space:nowrap;vertical-align:middle;width:48%;text-align:
right;"> <font color="#909AA4"><span style="padding-left:6px">April
30, 2020 at 4:32 PM</span></font></div> </div></div>
<div xmlns="http://www.w3.org/1999/xhtml" class="__pbConvBody"
__pbrmquotes="true"
style="color:#909AA4;margin-left:24px;margin-right:24px;">Peter,
<br>
<br>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:
<br>
<br><a class="moz-txt-link-freetext" href="https://github.com/sugarlabs/sugar-toolkit-gtk3/commit/2018c930adae85c18b1c51b5f80836fcad6c392c.patch">https://github.com/sugarlabs/sugar-toolkit-gtk3/commit/2018c930adae85c18b1c51b5f80836fcad6c392c.patch</a>
<br>
<br>This commit can be viewed at
<a class="moz-txt-link-freetext" href="https://github.com/sugarlabs/sugar-toolkit-gtk3/commit/2018c930adae85c18b1c51b5f80836fcad6c392c">https://github.com/sugarlabs/sugar-toolkit-gtk3/commit/2018c930adae85c18b1c51b5f80836fcad6c392c</a>
<br>
<br>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.
<br>
<br>I'd also like to request that we add the 'patch' package to the
default
list of installed packages, in the respin.
<br>_______________________________________________
<br>SoaS mailing list
<br><a class="moz-txt-link-abbreviated" href="mailto:SoaS@lists.sugarlabs.org">SoaS@lists.sugarlabs.org</a>
<br><a class="moz-txt-link-freetext" href="http://lists.sugarlabs.org/listinfo/soas">http://lists.sugarlabs.org/listinfo/soas</a>
<br>
</div>
</blockquote>
<br>
</body></html>