<div dir="ltr">Yes, Agreed. It would not be good if we configure the toolkit for only one version of Python.<div>May we change our <a href="http://configure.ac">configure.ac</a> as gyoto and dbus-python and then try?</div><div> </div><div>Thanks!</div></div> <div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Jul 9, 2019 at 12:18 PM ANIKET MATHUR <<a href="mailto:amathur@ec.iitr.ac.in">amathur@ec.iitr.ac.in</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"><div dir="ltr">Thanks for reminding.<div> </div><div>That's what I have got to track progress</div><div><a href="https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931666" target="_blank">https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931666</a> </div></div> <div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Jul 9, 2019 at 12:15 PM James Cameron <<a href="mailto:quozl@laptop.org" target="_blank">quozl@laptop.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">Debian's bug tracking system should send you a bug number by e-mail. Without that number, few others will be able to see progress or outcome. On Tue, Jul 09, 2019 at 08:40:17AM +0530, ANIKET MATHUR wrote: > Reported the problem as a bug to Debian using the reportbug program. > > Thanks! > > On Fri, Jul 5, 2019 at 8:22 PM ANIKET MATHUR <[1]<a href="mailto:amathur@ec.iitr.ac.in" target="_blank">amathur@ec.iitr.ac.in</a>> wrote: > > Sent the email to [2]<a href="mailto:debian-devel@lists.debian.org" target="_blank">debian-devel@lists.debian.org</a> as well. > > On Fri, Jul 5, 2019 at 4:13 PM ANIKET MATHUR <[3]<a href="mailto:amathur@ec.iitr.ac.in" target="_blank">amathur@ec.iitr.ac.in</a>> > wrote: > > Sent an email to the Debian user mailing list [4] > <a href="mailto:debian-user@lists.debian.org" target="_blank">debian-user@lists.debian.org</a> requesting for packaging v0.114. > > Packaging of Sugar-toolkit-gtk3 (sugar3) v0.114. > > [profile_ma] > ANIKET MATHUR <[5] 4:10 PM (2 minutes > <a href="mailto:amathur@ec.iitr.ac.in" target="_blank">amathur@ec.iitr.ac.in</a>> ago) [cleardot] > [cleardot] > to debian-user > [cleardot] > G'day, > Aniket Mathur this side, an active contributor of Sugarlabs as well as > a GSoC 19 participant. This mail is a small query regarding the > packaging of "sugar3" module. > > We currently have v0.112 packaged. In the latest version (0.114) > Sugarlabs have made the toolkit compatible with both Python and Python > 3. But we don't have Debian multi-version packages for the latest > version. This prevents us to scale our testing as well as limits the > number of testers. > > We don't know how to make multi-version local packages, that we can > distribute for testing. > > It would be good if we have Debian packages for v 0.114. > > Need Help. > Regards. > > On Tue, Jul 2, 2019 at 12:02 PM ANIKET MATHUR <[6]<a href="mailto:amathur@ec.iitr.ac.in" target="_blank">amathur@ec.iitr.ac.in</a> > > wrote: > > Yes, I was asking about Debian packages. Sorry for incomplete > information. > > I read sources of some Debian packages:- > ~ They do use six for keeping multi-version compatibility. > ~ Instead of a [7]<a href="http://configure.ac" rel="noreferrer" target="_blank">configure.ac</a>, they use setup.py. > ~ In setup.py, they define entry-points as per the commands from > the command line specifying python-foo or python3-foo. > > I also did a github search for 'python [8]<a href="http://configure.ac" rel="noreferrer" target="_blank">configure.ac</a>' , looked > into a considerable amount of commits of different users and > organizations with the motive of "why don't we ask for help from > those who seems to be successful in doing it". > > From my research, I found out that the guys at "balabit" seems to > be able to do it. > I opened an [9]issue asking for help and clearance. > > The next step is to contact the Debian developers. > > Thanks! > > On Mon, Jul 1, 2019 at 5:21 AM James Cameron <[10]<a href="mailto:quozl@laptop.org" target="_blank">quozl@laptop.org</a>> > wrote: > > You neglected to mention that you are asking about Debian and > Ubuntu > binary packages. Ubuntu packages come from Debian unchanged, > so your > question can be reduced to Debian packaging. > > We're the wrong people to ask. It's not a skill any of us at > Sugar > Labs have, otherwise we would have done it by now. > > The people who know how to do this are Debian and Ubuntu > package > developers. > > I've tried asking one of the Debian developers but they were > too busy > to give private assistance. Private assistance does not scale, > so the > return on investment is meagre. > > I suggest you try these things; > > 1. write a throw-away script to download all Debian packages > that > depend on Python 2 or Python 3, intersect a union of source > packages > that support both versions, and then list those packages that > contain > [11]<a href="http://configure.ac" rel="noreferrer" target="_blank">configure.ac</a> in the source package, > > 2. review those Debian and Ubuntu source packages that are > used to > generate binary packages for both Python 2 and Python 3, and > list the > package design patterns that you observe, > > 3. contact the Debian developers using their mailing lists, or > other > methods, > > 4. engage in the Debian project by reporting a bug that asks > for > packaging of a new version of the toolkit; currently 0.112 is > packaged. > > On Sat, Jun 29, 2019 at 02:32:33PM +0530, ANIKET MATHUR wrote: > > Hello everyone, > > > > I have been working on developing multi-version packages for > toolkit which can > > build for both Python and Python 3. I successfully build > packages for python, > > but not able to yet built one's having multi-version support. > I have been > > working on this for some time in the last two weeks, trying > to get something > > from the source code of existing tools that have these > packages, like 'pip' and > > a lot more. > > > > I need help and suggestions in this work. :-) > > > > Thanks! > > > _______________________________________________ > > Sugar-devel mailing list > > [12]<a href="mailto:Sugar-devel@lists.sugarlabs.org" target="_blank">Sugar-devel@lists.sugarlabs.org</a> > > [13]<a href="http://lists.sugarlabs.org/listinfo/sugar-devel" rel="noreferrer" target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a> > > -- > James Cameron > [14]<a href="http://quozl.netrek.org/" rel="noreferrer" target="_blank">http://quozl.netrek.org/</a> > _______________________________________________ > Sugar-devel mailing list > [15]<a href="mailto:Sugar-devel@lists.sugarlabs.org" target="_blank">Sugar-devel@lists.sugarlabs.org</a> > [16]<a href="http://lists.sugarlabs.org/listinfo/sugar-devel" rel="noreferrer" target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a> > > References: > > [1] mailto:<a href="mailto:amathur@ec.iitr.ac.in" target="_blank">amathur@ec.iitr.ac.in</a> > [2] mailto:<a href="mailto:debian-devel@lists.debian.org" target="_blank">debian-devel@lists.debian.org</a> > [3] mailto:<a href="mailto:amathur@ec.iitr.ac.in" target="_blank">amathur@ec.iitr.ac.in</a> > [4] mailto:<a href="mailto:debian-user@lists.debian.org" target="_blank">debian-user@lists.debian.org</a> > [5] mailto:<a href="mailto:amathur@ec.iitr.ac.in" target="_blank">amathur@ec.iitr.ac.in</a> > [6] mailto:<a href="mailto:amathur@ec.iitr.ac.in" target="_blank">amathur@ec.iitr.ac.in</a> > [7] <a href="http://configure.ac/" rel="noreferrer" target="_blank">http://configure.ac/</a> > [8] <a href="http://configure.ac/" rel="noreferrer" target="_blank">http://configure.ac/</a> > [9] <a href="https://github.com/balabit/syslog-ng/issues/2814" rel="noreferrer" target="_blank">https://github.com/balabit/syslog-ng/issues/2814</a> > [10] mailto:<a href="mailto:quozl@laptop.org" target="_blank">quozl@laptop.org</a> > [11] <a href="http://configure.ac/" rel="noreferrer" target="_blank">http://configure.ac/</a> > [12] mailto:<a href="mailto:Sugar-devel@lists.sugarlabs.org" target="_blank">Sugar-devel@lists.sugarlabs.org</a> > [13] <a href="http://lists.sugarlabs.org/listinfo/sugar-devel" rel="noreferrer" target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a> > [14] <a href="http://quozl.netrek.org/" rel="noreferrer" target="_blank">http://quozl.netrek.org/</a> > [15] mailto:<a href="mailto:Sugar-devel@lists.sugarlabs.org" target="_blank">Sugar-devel@lists.sugarlabs.org</a> > [16] <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> _______________________________________________ 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> </blockquote></div> </blockquote></div>