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