Re: [oe] ANNOUNCEMENT: meta-python2 has been created
On Tue, Dec 03, 2019 at 12:26:44PM +0100, Martin Jansa wrote: > On Mon, Dec 02, 2019 at 08:10:17PM -0800, Tim Orling wrote: > > On Mon, Dec 2, 2019 at 8:07 AM Martin Jansa wrote: > > > > > Thanks > > > > > > It would be nice to delete all branches except master. Only master branch > > > makes sense now for meta-python2, right? > > > > > > " The stable branches were also kept, to make it easier to refer back to > > prior history > > and allow developers to use meta-python2 only in their workflow." > > > > I can see use cases where a developer may want to replace meta-python with > > meta-python2 and still be on a "stable" release. It also makes reviewing > > what existed in which release much easier with cgit or git log --oneline, > > which I do VERY frequently. If this is contentious then the OE-TSC will > > make the decision. > > But python2 is still in oe-core zeus and older so it should continue to > be maintained there, right? > > Why should people add meta-python2 to zeus (or older) builds? If there > are more security updates to python2 or any other recipes, then they > should still land in oe-core or meta-oe/meta-python as well and > maintaining the duplicates in meta-python2 seems unnecessary overhead. > > My understanding was that meta-python2 is just to help transition from > oe-core/master when the python2 is dropped there. I have to take this back (partially). There are some python2 recipes which were already removed from zeus, e.g. python-numpy: http://git.openembedded.org/openembedded-core/commit/?h=zeus&id=4e9659f24e2f699effadcbe378b6a746d77ccdbd python-nose: http://git.openembedded.org/openembedded-core/commit/?h=zeus&id=9f07b2836405d86e869780f8f1ae00843eadc409 I've noticed these 2, because they are used by catkin and rospy in meta-ros But I still don't feel well including this whole layer which duplicates many recipes from oe-core/zeus or meta-oe/zeus just for these 2 recipes (and making meta-python2 mandatory for every meta-ros/zeus user), so I'll probably just import them to meta-ros. Also neither of these is included in meta-python2, so it wouldn't help in my use-case and before understanding what the zeus branch is for I don't want to send patches to add them. Or can you please explain what's the advantage of using meta-python2/zeus? I mean including it in a build (not just for git log). On another topic, there is the compatibility issue caused by python/python2 being removed from HOSTTOOLS in: http://git.openembedded.org/openembedded-core/commit/?id=5f8f16b17f66966ae91aeabc23e97de5ecd17447 Is this something meta-python2 should help with the transition as well or should we leave that to distro maintainers? Khem already fixed few qt* recipes in meta-qt5 to use python3, but that's only in master branch and people who might want to use newer oe-core with older meta-qt5 (e.g. 5.12 LTS version) will need to work-around this as well. But I understand that changing HOSTTOOLS in meta-python2/conf/layer.conf is quite controversial as it has bigger side-effect than just making bunch of recipes available. Regards, signature.asc Description: PGP signature -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
Re: [oe] ANNOUNCEMENT: meta-python2 has been created
On Mon, Dec 02, 2019 at 08:10:17PM -0800, Tim Orling wrote: > On Mon, Dec 2, 2019 at 8:07 AM Martin Jansa wrote: > > > Thanks > > > > It would be nice to delete all branches except master. Only master branch > > makes sense now for meta-python2, right? > > > > " The stable branches were also kept, to make it easier to refer back to > prior history > and allow developers to use meta-python2 only in their workflow." > > I can see use cases where a developer may want to replace meta-python with > meta-python2 and still be on a "stable" release. It also makes reviewing > what existed in which release much easier with cgit or git log --oneline, > which I do VERY frequently. If this is contentious then the OE-TSC will > make the decision. But python2 is still in oe-core zeus and older so it should continue to be maintained there, right? Why should people add meta-python2 to zeus (or older) builds? If there are more security updates to python2 or any other recipes, then they should still land in oe-core or meta-oe/meta-python as well and maintaining the duplicates in meta-python2 seems unnecessary overhead. My understanding was that meta-python2 is just to help transition from oe-core/master when the python2 is dropped there. Regards, signature.asc Description: PGP signature -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
Re: [oe] ANNOUNCEMENT: meta-python2 has been created
On Mon, Dec 02, 2019 at 08:10:17PM -0800, Tim Orling wrote: > On Mon, Dec 2, 2019 at 8:07 AM Martin Jansa wrote: > > > Thanks > > > > It would be nice to delete all branches except master. Only master branch > > makes sense now for meta-python2, right? > > > > " The stable branches were also kept, to make it easier to refer back to > prior history > and allow developers to use meta-python2 only in their workflow." > > I can see use cases where a developer may want to replace meta-python with > meta-python2 and still be on a "stable" release. It also makes reviewing > what existed in which release much easier with cgit or git log --oneline, > which I do VERY frequently. If this is contentious then the OE-TSC will > make the decision. >... Martin beat me since I was about to make the same comment. Adding a layer with contents that in the best case duplicates what is already in another layer (and in the worst case is broken) only creates confusion. Replacing meta-python with meta-python2 sounds like a weird usecase, and LAYERDEPENDS from layers like meta-multimedia or meta-networking usually do not even make it an option to not include meta-python. In practice the most common case where meta-python2 would be included in a zeus or earlier distribution would be when someone includes both the meta-python and meta-python2 layers. cu Adrian -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
Re: [oe] ANNOUNCEMENT: meta-python2 has been created
On Mon, Dec 2, 2019 at 1:49 PM akuster808 wrote: > Tim, > > On 12/2/19 7:56 AM, Tim Orling wrote: > > Why? > > > > With the pending EOL (end-of-life) of Python 2 in a month [1], it is time > > to move python2 recipes to a new home. For that reason, meta-python2 [2] > > has been created as the home for legacy python2 recipes. > > Thanks for putting in the time to get this sorted out. > It was a slog, but it was worth it. You are welcome :) > > > How? > > > > It was a design goal to keep the original history of meta-python, but > only > > the python2 parts. In order to accomplish this git-filter-repo was used > > [3]. The exact steps used can be seen in a gist [4]. After that script > was > > run, manual merging of *.inc and *.bb files was performed to make recipe > > maintenance with AUH (auto upgrade helper) and devtool easier. Since this > > layer does not have to support two python versions, the reason for the > *.bb > > and *.inc split has been eliminated. Commits that upgraded recipes to > > python2-incompatible versions were reverted. Changes to make the recipes > > build and ptests be runnable were also made (to master branch). The > stable > > branches were also kept, to make it easier to refer back to prior history > > and allow developers to use meta-python2 only in their workflow. NOTE: > The > > stable branches may require work to make them usable, this was outside > the > > scope of the immediate effort. > > > Should we have a separate patch work for this layer? > > As I understand it, that requires a separate mailing list, which currently feels like undo overhead. But I would love a separate patchwork instance. If the normal Stable branch format is used for patches, it should be > easy to sort out so we can see how it goes and make adjustments as we go. > > The volume for stable meta-python patches tends to be low so I don't > mind sorting things out from master to zeus between the two branches. > > There are a few changes I would like to make to the zeus branch of meta-python2 (clean up of packagegroup-meta-python2 and such), but I agree that the amount of patches tends to be low and it is not that much of a burden. It certainly seems worth supporting zeus, as I had originally intended meta-python2 to exist before the zeus release. It is also worth considering warrior. Much further back than that I would want to hear from users that want to step up to help maintain the older stable releases. It is certainly doable to perform builds on gitlab-ci for as far back as 'kas' supports releases (which as I recall is krogoth and morty believe it or not). > > - armin > > > > What next? > > = > > Python2 recipes from meta-python will be dropped via patches sent to the > > mailing list. Python2 recipes from meta-oe and meta-networking, which > have > > already been added to meta-python2, will be dropped via patches to the > > mailing list. Other layers are welcome to do the same. > > > > Recipe upgrades to meta-python2 will also be coming, for instance Django > > 1.11.x LTS is the last version to support Python 2, but we are not at the > > latest release of that series. > > > > The original meta-python will become Python3-only and patches for python2 > > support will be nacked and redirected to meta-python2. > > > > python2 itself will likely be moved from oe-core into meta-python2 > > > > [1] https://www.python.org/doc/sunset-python-2/ > > [2] https://git.openembedded.org/meta-python2/ > > [3] https://github.com/newren/git-filter-repo > > [4] https://gist.github.com/moto-timo/ab70ab96ddbaf5fd1226bd21dbbfec9b > > > -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
Re: [oe] ANNOUNCEMENT: meta-python2 has been created
On Mon, Dec 2, 2019 at 8:07 AM Martin Jansa wrote: > Thanks > > It would be nice to delete all branches except master. Only master branch > makes sense now for meta-python2, right? > > " The stable branches were also kept, to make it easier to refer back to prior history and allow developers to use meta-python2 only in their workflow." I can see use cases where a developer may want to replace meta-python with meta-python2 and still be on a "stable" release. It also makes reviewing what existed in which release much easier with cgit or git log --oneline, which I do VERY frequently. If this is contentious then the OE-TSC will make the decision. > On Mon, Dec 2, 2019 at 4:57 PM Tim Orling wrote: > >> Why? >> >> With the pending EOL (end-of-life) of Python 2 in a month [1], it is time >> to move python2 recipes to a new home. For that reason, meta-python2 [2] >> has been created as the home for legacy python2 recipes. >> >> How? >> >> It was a design goal to keep the original history of meta-python, but only >> the python2 parts. In order to accomplish this git-filter-repo was used >> [3]. The exact steps used can be seen in a gist [4]. After that script was >> run, manual merging of *.inc and *.bb files was performed to make recipe >> maintenance with AUH (auto upgrade helper) and devtool easier. Since this >> layer does not have to support two python versions, the reason for the >> *.bb >> and *.inc split has been eliminated. Commits that upgraded recipes to >> python2-incompatible versions were reverted. Changes to make the recipes >> build and ptests be runnable were also made (to master branch). The stable >> branches were also kept, to make it easier to refer back to prior history >> and allow developers to use meta-python2 only in their workflow. NOTE: The >> stable branches may require work to make them usable, this was outside the >> scope of the immediate effort. >> >> What next? >> = >> Python2 recipes from meta-python will be dropped via patches sent to the >> mailing list. Python2 recipes from meta-oe and meta-networking, which have >> already been added to meta-python2, will be dropped via patches to the >> mailing list. Other layers are welcome to do the same. >> >> Recipe upgrades to meta-python2 will also be coming, for instance Django >> 1.11.x LTS is the last version to support Python 2, but we are not at the >> latest release of that series. >> >> The original meta-python will become Python3-only and patches for python2 >> support will be nacked and redirected to meta-python2. >> >> python2 itself will likely be moved from oe-core into meta-python2 >> >> [1] https://www.python.org/doc/sunset-python-2/ >> [2] https://git.openembedded.org/meta-python2/ >> [3] https://github.com/newren/git-filter-repo >> [4] https://gist.github.com/moto-timo/ab70ab96ddbaf5fd1226bd21dbbfec9b >> -- >> ___ >> Openembedded-devel mailing list >> Openembedded-devel@lists.openembedded.org >> http://lists.openembedded.org/mailman/listinfo/openembedded-devel >> > -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
Re: [oe] ANNOUNCEMENT: meta-python2 has been created
Tim, On 12/2/19 7:56 AM, Tim Orling wrote: > Why? > > With the pending EOL (end-of-life) of Python 2 in a month [1], it is time > to move python2 recipes to a new home. For that reason, meta-python2 [2] > has been created as the home for legacy python2 recipes. Thanks for putting in the time to get this sorted out. > > How? > > It was a design goal to keep the original history of meta-python, but only > the python2 parts. In order to accomplish this git-filter-repo was used > [3]. The exact steps used can be seen in a gist [4]. After that script was > run, manual merging of *.inc and *.bb files was performed to make recipe > maintenance with AUH (auto upgrade helper) and devtool easier. Since this > layer does not have to support two python versions, the reason for the *.bb > and *.inc split has been eliminated. Commits that upgraded recipes to > python2-incompatible versions were reverted. Changes to make the recipes > build and ptests be runnable were also made (to master branch). The stable > branches were also kept, to make it easier to refer back to prior history > and allow developers to use meta-python2 only in their workflow. NOTE: The > stable branches may require work to make them usable, this was outside the > scope of the immediate effort. Should we have a separate patch work for this layer? If the normal Stable branch format is used for patches, it should be easy to sort out so we can see how it goes and make adjustments as we go. The volume for stable meta-python patches tends to be low so I don't mind sorting things out from master to zeus between the two branches. - armin > > What next? > = > Python2 recipes from meta-python will be dropped via patches sent to the > mailing list. Python2 recipes from meta-oe and meta-networking, which have > already been added to meta-python2, will be dropped via patches to the > mailing list. Other layers are welcome to do the same. > > Recipe upgrades to meta-python2 will also be coming, for instance Django > 1.11.x LTS is the last version to support Python 2, but we are not at the > latest release of that series. > > The original meta-python will become Python3-only and patches for python2 > support will be nacked and redirected to meta-python2. > > python2 itself will likely be moved from oe-core into meta-python2 > > [1] https://www.python.org/doc/sunset-python-2/ > [2] https://git.openembedded.org/meta-python2/ > [3] https://github.com/newren/git-filter-repo > [4] https://gist.github.com/moto-timo/ab70ab96ddbaf5fd1226bd21dbbfec9b -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
Re: [oe] ANNOUNCEMENT: meta-python2 has been created
Thanks It would be nice to delete all branches except master. Only master branch makes sense now for meta-python2, right? On Mon, Dec 2, 2019 at 4:57 PM Tim Orling wrote: > Why? > > With the pending EOL (end-of-life) of Python 2 in a month [1], it is time > to move python2 recipes to a new home. For that reason, meta-python2 [2] > has been created as the home for legacy python2 recipes. > > How? > > It was a design goal to keep the original history of meta-python, but only > the python2 parts. In order to accomplish this git-filter-repo was used > [3]. The exact steps used can be seen in a gist [4]. After that script was > run, manual merging of *.inc and *.bb files was performed to make recipe > maintenance with AUH (auto upgrade helper) and devtool easier. Since this > layer does not have to support two python versions, the reason for the *.bb > and *.inc split has been eliminated. Commits that upgraded recipes to > python2-incompatible versions were reverted. Changes to make the recipes > build and ptests be runnable were also made (to master branch). The stable > branches were also kept, to make it easier to refer back to prior history > and allow developers to use meta-python2 only in their workflow. NOTE: The > stable branches may require work to make them usable, this was outside the > scope of the immediate effort. > > What next? > = > Python2 recipes from meta-python will be dropped via patches sent to the > mailing list. Python2 recipes from meta-oe and meta-networking, which have > already been added to meta-python2, will be dropped via patches to the > mailing list. Other layers are welcome to do the same. > > Recipe upgrades to meta-python2 will also be coming, for instance Django > 1.11.x LTS is the last version to support Python 2, but we are not at the > latest release of that series. > > The original meta-python will become Python3-only and patches for python2 > support will be nacked and redirected to meta-python2. > > python2 itself will likely be moved from oe-core into meta-python2 > > [1] https://www.python.org/doc/sunset-python-2/ > [2] https://git.openembedded.org/meta-python2/ > [3] https://github.com/newren/git-filter-repo > [4] https://gist.github.com/moto-timo/ab70ab96ddbaf5fd1226bd21dbbfec9b > -- > ___ > Openembedded-devel mailing list > Openembedded-devel@lists.openembedded.org > http://lists.openembedded.org/mailman/listinfo/openembedded-devel > -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
[oe] ANNOUNCEMENT: meta-python2 has been created
Why? With the pending EOL (end-of-life) of Python 2 in a month [1], it is time to move python2 recipes to a new home. For that reason, meta-python2 [2] has been created as the home for legacy python2 recipes. How? It was a design goal to keep the original history of meta-python, but only the python2 parts. In order to accomplish this git-filter-repo was used [3]. The exact steps used can be seen in a gist [4]. After that script was run, manual merging of *.inc and *.bb files was performed to make recipe maintenance with AUH (auto upgrade helper) and devtool easier. Since this layer does not have to support two python versions, the reason for the *.bb and *.inc split has been eliminated. Commits that upgraded recipes to python2-incompatible versions were reverted. Changes to make the recipes build and ptests be runnable were also made (to master branch). The stable branches were also kept, to make it easier to refer back to prior history and allow developers to use meta-python2 only in their workflow. NOTE: The stable branches may require work to make them usable, this was outside the scope of the immediate effort. What next? = Python2 recipes from meta-python will be dropped via patches sent to the mailing list. Python2 recipes from meta-oe and meta-networking, which have already been added to meta-python2, will be dropped via patches to the mailing list. Other layers are welcome to do the same. Recipe upgrades to meta-python2 will also be coming, for instance Django 1.11.x LTS is the last version to support Python 2, but we are not at the latest release of that series. The original meta-python will become Python3-only and patches for python2 support will be nacked and redirected to meta-python2. python2 itself will likely be moved from oe-core into meta-python2 [1] https://www.python.org/doc/sunset-python-2/ [2] https://git.openembedded.org/meta-python2/ [3] https://github.com/newren/git-filter-repo [4] https://gist.github.com/moto-timo/ab70ab96ddbaf5fd1226bd21dbbfec9b -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
