<div dir="ltr"><div class="gmail_default" style="font-family:verdana,sans-serif;font-size:large">Python packages: <a href="https://github.com/sukhdeepg/sugar-toolkit-gtk3-python-packages" style="font-family:Arial,Helvetica,sans-serif;font-size:small">https://github.com/sukhdeepg/sugar-toolkit-gtk3-python-packages</a>. This is the first step with respect to an earlier reply from James Cameron. I've understood the depth of the issue from <a href="http://lists.sugarlabs.org/archive/sugar-devel/2019-July/057058.html">this result</a> after the Debian bug 931666 search. If this isn't the right way, please let me know. </div></div> <div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Jul 22, 2019 at 9:30 PM <<a href="mailto:sugar-devel-request@lists.sugarlabs.org">sugar-devel-request@lists.sugarlabs.org</a>> wrote: </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Send Sugar-devel mailing list submissions to <a href="mailto:sugar-devel@lists.sugarlabs.org" target="_blank">sugar-devel@lists.sugarlabs.org</a> To subscribe or unsubscribe via the World Wide Web, visit <a href="http://lists.sugarlabs.org/listinfo/sugar-devel" rel="noreferrer" target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a> or, via email, send a message with subject or body 'help' to <a href="mailto:sugar-devel-request@lists.sugarlabs.org" target="_blank">sugar-devel-request@lists.sugarlabs.org</a> You can reach the person managing the list at <a href="mailto:sugar-devel-owner@lists.sugarlabs.org" target="_blank">sugar-devel-owner@lists.sugarlabs.org</a> When replying, please edit your Subject line so it is more specific than "Re: Contents of Sugar-devel digest..." Today's Topics: 1. Re: [FEATURE] Separate python version packages for sugar-toolkit-gtk3 (James Cameron) 2. Releasing activities on ASLO (Swarup N) ---------------------------------------------------------------------- Message: 1 Date: Mon, 22 Jul 2019 16:05:25 +1000 From: James Cameron <<a href="mailto:quozl@laptop.org" target="_blank">quozl@laptop.org</a>> To: <a href="mailto:sugar-devel@lists.sugarlabs.org" target="_blank">sugar-devel@lists.sugarlabs.org</a> Subject: Re: [Sugar-devel] [FEATURE] Separate python version packages for sugar-toolkit-gtk3 Message-ID: <<a href="mailto:20190722060525.GA2624@laptop.org" target="_blank">20190722060525.GA2624@laptop.org</a>> Content-Type: text/plain; charset=iso-8859-1 G'day Sukhdeep, I don't know what your approach was, sorry. What is needed now is a python3-sugar3 deb package, containing the HEAD of _master_ branch, built for python3, alongside a python-sugar3 deb package, built for python2. Both would be installed at once. Also, the python-sugar3 package shouldn't contain /usr/bin/sugar-activity3 as that file is for python3, and therefore should be in the python3-sugar3 package. Also, it should be documented so that anyone else to reproduce the packaging. Debian bug 931666 is related. Mailing list automatically adds [Sugar-devel] subject tag, if it is not already present. You don't need to add it, but it is harmless if you do. Hope that helps! On Sun, Jul 21, 2019 at 12:12:34PM +0530, sukhdeep gill wrote: > Hello! > > I've created deb packages for sugar-toolkit-gtk3 using this [1]source. With and > without --with-python3 option. E.g. output looks like this: > python-sugar3_0.114~sukhdeep.0-1_all.deb. > Is this is a correct approach to take for creating the package? > > P.S. [Sugar-devel] subject tag was used in most of the email archives I > checked. Please let me know if I should use that going further. > > Thanks, > Sukhdeep Gill > > References: > > [1] <a href="https://github.com/sugarlabs/sugar/blob/master/docs/debian-packaging-example.md" rel="noreferrer" target="_blank">https://github.com/sugarlabs/sugar/blob/master/docs/debian-packaging-example.md</a> > _______________________________________________ > Sugar-devel mailing list > <a href="mailto:Sugar-devel@lists.sugarlabs.org" target="_blank">Sugar-devel@lists.sugarlabs.org</a> > <a href="http://lists.sugarlabs.org/listinfo/sugar-devel" rel="noreferrer" target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a> -- James Cameron <a href="http://quozl.netrek.org/" rel="noreferrer" target="_blank">http://quozl.netrek.org/</a> ------------------------------ Message: 2 Date: Mon, 22 Jul 2019 19:59:02 +0530 From: Swarup N <<a href="mailto:nswarup14@gmail.com" target="_blank">nswarup14@gmail.com</a>> To: James Cameron <<a href="mailto:quozl@laptop.org" target="_blank">quozl@laptop.org</a>>, Sugar-dev Devel <<a href="mailto:sugar-devel@lists.sugarlabs.org" target="_blank">sugar-devel@lists.sugarlabs.org</a>> Subject: [Sugar-devel] Releasing activities on ASLO Message-ID: <CAFaDYNs6m-QUxaoJE6cUshjdYKHdfewGrJH=2O=<a href="mailto:m-FgkMpYNiw@mail.gmail.com" target="_blank">m-FgkMpYNiw@mail.gmail.com</a>> Content-Type: text/plain; charset="utf-8" Hello, I wish to release activities on ASLO. This is in part of work for GSoC 2019. I have been testing activities on Fedora 18, Ubuntu 18.04, and Ubuntu 16.04 (not yet, but I plan to start). Are there any other platforms I need to test on? Are there any release notes I need to include? Is there a format I need to follow? What is procedure to bundle activities in .xo format? Thanks. -------------- next part -------------- An HTML attachment was scrubbed... URL: <<a href="http://lists.sugarlabs.org/archive/sugar-devel/attachments/20190722/2ffb3755/attachment-0001.html" rel="noreferrer" target="_blank">http://lists.sugarlabs.org/archive/sugar-devel/attachments/20190722/2ffb3755/attachment-0001.html</a>> ------------------------------ Subject: Digest Footer _______________________________________________ Sugar-devel mailing list <a href="mailto:Sugar-devel@lists.sugarlabs.org" target="_blank">Sugar-devel@lists.sugarlabs.org</a> <a href="http://lists.sugarlabs.org/listinfo/sugar-devel" rel="noreferrer" target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a> ------------------------------ End of Sugar-devel Digest, Vol 129, Issue 27 ******************************************** </blockquote></div>