Bug#937302: playonlinux: Python2 removal in sid/bullseye
On Mon, 11 May 2020, Markus Koschany wrote: Anyway, I pushed a change to allow resizing that window so that should at least help. Thank you very much! That solved the problem. I have just uploaded playonlinux with your patch to unstable. Great! Feel free to ping me if any bugs related to the port come up. Happy to help. Scott
Bug#937302: playonlinux: Python2 removal in sid/bullseye
Am 10.05.20 um 18:30 schrieb Scott Talbert: [...] >> Okay. I think the problem is that the UI layout is somewhat >> statically defined and it does not leave enough room for the German(?) >> translations. Let me see if I can figure out how to make that better. >> >> I did figure out how to make that window resizable though so that >> should help. > > Yes. It must have something to do with your theme. Even if I change my > language to German, both buttons are completely visible. What theme do > you use? > > Anyway, I pushed a change to allow resizing that window so that should > at least help. > > Scott > Thank you very much! That solved the problem. I have just uploaded playonlinux with your patch to unstable. Regards, Markus signature.asc Description: OpenPGP digital signature
Bug#937302: playonlinux: Python2 removal in sid/bullseye
On Sun, 10 May 2020, Scott Talbert wrote: I'm attaching a screenshot. I thought it would be related to the Python 3 port but maybe it's just a playonlinux or wxpython bug with certain Gnome themes? The two buttons "Abbrechen" (Cancel) and "Anwenden" (Apply) should be either in the center or correctly align to the right side of the window. But the "Anwenden"-Button is cut in half and it is impossible to resize it. It is still possible to click on every button, so it shouldn't be too much of problem though. Okay. I think the problem is that the UI layout is somewhat statically defined and it does not leave enough room for the German(?) translations. Let me see if I can figure out how to make that better. I did figure out how to make that window resizable though so that should help. Yes. It must have something to do with your theme. Even if I change my language to German, both buttons are completely visible. What theme do you use? Anyway, I pushed a change to allow resizing that window so that should at least help. Scott
Bug#937302: playonlinux: Python2 removal in sid/bullseye
On Sun, 10 May 2020, Markus Koschany wrote: I'm attaching a screenshot. I thought it would be related to the Python 3 port but maybe it's just a playonlinux or wxpython bug with certain Gnome themes? The two buttons "Abbrechen" (Cancel) and "Anwenden" (Apply) should be either in the center or correctly align to the right side of the window. But the "Anwenden"-Button is cut in half and it is impossible to resize it. It is still possible to click on every button, so it shouldn't be too much of problem though. Okay. I think the problem is that the UI layout is somewhat statically defined and it does not leave enough room for the German(?) translations. Let me see if I can figure out how to make that better. I did figure out how to make that window resizable though so that should help. Scott
Bug#937302: playonlinux: Python2 removal in sid/bullseye
I'm attaching a screenshot. I thought it would be related to the Python 3 port but maybe it's just a playonlinux or wxpython bug with certain Gnome themes? The two buttons "Abbrechen" (Cancel) and "Anwenden" (Apply) should be either in the center or correctly align to the right side of the window. But the "Anwenden"-Button is cut in half and it is impossible to resize it. It is still possible to click on every button, so it shouldn't be too much of problem though. Markus signature.asc Description: OpenPGP digital signature
Bug#937302: playonlinux: Python2 removal in sid/bullseye
On Sun, 10 May 2020, Markus Koschany wrote: Thanks for all your work on porting playonlinux to Python 3. I have tested the port for a while now. Compiling works as expected. After installing the i386 Wine version I could install Internet Explorer 7 and MTPaint. The only glitches I found are in the settings menu. I can't resize the windows and the buttons are only partially visible. Apart from that it looks like the basic features are working. If we can find a solution for the settings menu, I can upload playonlinux to unstable. Thanks for your testing and feedback. Can you be a little more specific about the issues with the settings menu? When I access the settings windows, all of the buttons seem to be visible for me. I do see the fact that the window is not resizable, but I also see that behavior with the Python 2 version, so that does not seem to be something introduced by the Python 3 port. Perhaps you can show a screenshot for the buttons being partially visible? Thanks, Scott
Bug#937302: playonlinux: Python2 removal in sid/bullseye
Hi Scott, Am 07.05.20 um 17:19 schrieb Scott Talbert: [...] >> I haven't had the time to really review and test your patch but I will >> do so eventually. > > Thanks. Let me know if you would like me to just NMU it as well. Thanks for all your work on porting playonlinux to Python 3. I have tested the port for a while now. Compiling works as expected. After installing the i386 Wine version I could install Internet Explorer 7 and MTPaint. The only glitches I found are in the settings menu. I can't resize the windows and the buttons are only partially visible. Apart from that it looks like the basic features are working. If we can find a solution for the settings menu, I can upload playonlinux to unstable. Regards, Markus signature.asc Description: OpenPGP digital signature
Bug#937302: playonlinux: Python2 removal in sid/bullseye
On Thu, 23 Apr 2020, Markus Koschany wrote: OK, so it turns out the port to Python 3 was a bit harder than expected, but I think I've got something ready for further review / testing. I have done some initial testing, but I'm not that familiar with playonlinux so I would appreciate some additional testing. I submitted my patch as a merge request here: https://salsa.debian.org/games-team/playonlinux/-/merge_requests/1 Please do let me know if you encounter any bugs. I will fix them. Hello Markus and Bertrand, Did you have any chance to review my patch or test it yet? Thanks, Scott I haven't had the time to really review and test your patch but I will do so eventually. Thanks. Let me know if you would like me to just NMU it as well. Regards, Scott
Bug#937302: playonlinux: Python2 removal in sid/bullseye
Hi Scott, Am 23.04.20 um 17:21 schrieb Scott Talbert: > On Wed, 15 Apr 2020, Scott Talbert wrote: > >> OK, so it turns out the port to Python 3 was a bit harder than >> expected, but I think I've got something ready for further review / >> testing. I have done some initial testing, but I'm not that familiar >> with playonlinux so I would appreciate some additional testing. I >> submitted my patch as a merge request here: >> >> https://salsa.debian.org/games-team/playonlinux/-/merge_requests/1 >> >> Please do let me know if you encounter any bugs. I will fix them. > > Hello Markus and Bertrand, > > Did you have any chance to review my patch or test it yet? > > Thanks, > Scott I haven't had the time to really review and test your patch but I will do so eventually. Regards, Markus signature.asc Description: OpenPGP digital signature
Bug#937302: playonlinux: Python2 removal in sid/bullseye
On Wed, 15 Apr 2020, Scott Talbert wrote: OK, so it turns out the port to Python 3 was a bit harder than expected, but I think I've got something ready for further review / testing. I have done some initial testing, but I'm not that familiar with playonlinux so I would appreciate some additional testing. I submitted my patch as a merge request here: https://salsa.debian.org/games-team/playonlinux/-/merge_requests/1 Please do let me know if you encounter any bugs. I will fix them. Hello Markus and Bertrand, Did you have any chance to review my patch or test it yet? Thanks, Scott
Bug#937302: playonlinux: Python2 removal in sid/bullseye
On Wed, 8 Apr 2020, Markus Koschany wrote: So, I took an initial look at trying to package Phoenicis, but it looks like a rather large task (ie, lots of missing dependencies). On the other hand, I looked at the Python code, and at first glance, it doesn't look like it would be *that* difficult to port to Python 3. Would you be amenable to me developing a patch to port to Python 3, at least as an interim solution? sure feel free to work on a patch to fix #937302, no need to ask for my approval. OK, so it turns out the port to Python 3 was a bit harder than expected, but I think I've got something ready for further review / testing. I have done some initial testing, but I'm not that familiar with playonlinux so I would appreciate some additional testing. I submitted my patch as a merge request here: https://salsa.debian.org/games-team/playonlinux/-/merge_requests/1 Please do let me know if you encounter any bugs. I will fix them. Scott
Bug#937302: playonlinux: Python2 removal in sid/bullseye
Am 08.04.20 um 16:20 schrieb Scott Talbert: [...] > So, I took an initial look at trying to package Phoenicis, but it looks > like a rather large task (ie, lots of missing dependencies). > > On the other hand, I looked at the Python code, and at first glance, it > doesn't look like it would be *that* difficult to port to Python 3. > Would you be amenable to me developing a patch to port to Python 3, at > least as an interim solution? > > Thanks, > Scott Hello Scott, sure feel free to work on a patch to fix #937302, no need to ask for my approval. Cheers, Markus signature.asc Description: OpenPGP digital signature
Bug#937302: playonlinux: Python2 removal in sid/bullseye
On Tue, 3 Mar 2020, Scott Talbert wrote: Sorry, I do not mean any disrespect. What can I do to help? I believe the best thing to do would be to package the new Java version. https://github.com/PhoenicisOrg/phoenicis This requires some knowledge of Java and how Java applications are packaged for Debian. I have created https://wiki.debian.org/Java/Packaging https://wiki.debian.org/Java/Packaging/Maven which should give you some hints. If packaging the new version is out of scope for you, you could try to find out which build-dependencies have been already packaged and what we need to do in order to get phoenicis into Debian. There is a tool called mh_make that helps to create a preliminary debian directory. http://collab.debian.net/portal/planet-debian/markus-koschany-pdfsam-how-to-upgrade-a-maven-application-for-debian It is by far not perfect but it might help you to complete this task. Okay, I will take a stab at it. I'm mostly a Python packager but it will be interesting to try some Java. So, I took an initial look at trying to package Phoenicis, but it looks like a rather large task (ie, lots of missing dependencies). On the other hand, I looked at the Python code, and at first glance, it doesn't look like it would be *that* difficult to port to Python 3. Would you be amenable to me developing a patch to port to Python 3, at least as an interim solution? Thanks, Scott
Bug#937302: playonlinux: Python2 removal in sid/bullseye
On Tue, 3 Mar 2020, Markus Koschany wrote: Sorry, I do not mean any disrespect. What can I do to help? I believe the best thing to do would be to package the new Java version. https://github.com/PhoenicisOrg/phoenicis This requires some knowledge of Java and how Java applications are packaged for Debian. I have created https://wiki.debian.org/Java/Packaging https://wiki.debian.org/Java/Packaging/Maven which should give you some hints. If packaging the new version is out of scope for you, you could try to find out which build-dependencies have been already packaged and what we need to do in order to get phoenicis into Debian. There is a tool called mh_make that helps to create a preliminary debian directory. http://collab.debian.net/portal/planet-debian/markus-koschany-pdfsam-how-to-upgrade-a-maven-application-for-debian It is by far not perfect but it might help you to complete this task. Okay, I will take a stab at it. I'm mostly a Python packager but it will be interesting to try some Java. Scott
Bug#937302: playonlinux: Python2 removal in sid/bullseye
Am 03.03.20 um 01:54 schrieb Scott Talbert: [...] > Sorry, I do not mean any disrespect. What can I do to help? I believe the best thing to do would be to package the new Java version. https://github.com/PhoenicisOrg/phoenicis This requires some knowledge of Java and how Java applications are packaged for Debian. I have created https://wiki.debian.org/Java/Packaging https://wiki.debian.org/Java/Packaging/Maven which should give you some hints. If packaging the new version is out of scope for you, you could try to find out which build-dependencies have been already packaged and what we need to do in order to get phoenicis into Debian. There is a tool called mh_make that helps to create a preliminary debian directory. http://collab.debian.net/portal/planet-debian/markus-koschany-pdfsam-how-to-upgrade-a-maven-application-for-debian It is by far not perfect but it might help you to complete this task. signature.asc Description: OpenPGP digital signature
Bug#937302: playonlinux: Python2 removal in sid/bullseye
On Tue, 3 Mar 2020, Markus Koschany wrote: Because it is preventing Python 2 removal work. Python 2 removal is a long process, involving nearly 3500 packages [1]. It is not happening in one instant, but gradually over time. At the moment, playonlinux is a leaf package from a Python 2 perspective and is thus blocking its Python 2 rdeps from being removed. Scott [1] http://sandrotosi.me/debian/py2removal/index.html Right, and that's the completely wrong approach. You can't just remove important packages because of your goal. You have to actively help people who have contributed to Debian for several years now. Just asking them to remove their packages is disrespectful and a poor way to contribute to Debian. Sorry, I do not mean any disrespect. What can I do to help? Scott
Bug#937302: playonlinux: Python2 removal in sid/bullseye
Am 02.03.20 um 23:46 schrieb Scott Talbert: [...] > Because it is preventing Python 2 removal work. Python 2 removal is a > long process, involving nearly 3500 packages [1]. It is not happening > in one instant, but gradually over time. At the moment, playonlinux is > a leaf package from a Python 2 perspective and is thus blocking its > Python 2 rdeps from being removed. > > Scott > > [1] http://sandrotosi.me/debian/py2removal/index.html Right, and that's the completely wrong approach. You can't just remove important packages because of your goal. You have to actively help people who have contributed to Debian for several years now. Just asking them to remove their packages is disrespectful and a poor way to contribute to Debian. signature.asc Description: OpenPGP digital signature
Bug#937302: playonlinux: Python2 removal in sid/bullseye
On Mon, 2 Mar 2020, Markus Koschany wrote: What is the games team plan for Python 3 support in playonlinux? Do you plan to port it to Python 3? Or remove? I don't plan to port playonlinux to Python 3. However, a new version of playonlinux is currently developped under Java [1]. There is no release date for now, but I will package it when a stable version is available. Best, Bertrand [1] https://github.com/PhoenicisOrg/phoenicis Should we then RM playonlinux from Debian? Scott Why should we remove playonlinux from Debian? There is a Java port that just needs to be packaged. Python 2 has not been removed from Debian yet. All that is needed is someone who works on it. It is completely reasonable to have a package in unstable and not in testing for a while, especially when it has a popcon inst value of more than 4700. Because it is preventing Python 2 removal work. Python 2 removal is a long process, involving nearly 3500 packages [1]. It is not happening in one instant, but gradually over time. At the moment, playonlinux is a leaf package from a Python 2 perspective and is thus blocking its Python 2 rdeps from being removed. Scott [1] http://sandrotosi.me/debian/py2removal/index.html
Bug#937302: playonlinux: Python2 removal in sid/bullseye
Am 02.03.20 um 03:03 schrieb Scott Talbert: > On Sat, 29 Feb 2020, Bertrand Marc wrote: > >>> On Thu, 30 Jan 2020, Scott Talbert wrote: What is the games team plan for Python 3 support in playonlinux? Do you plan to port it to Python 3? Or remove? >> >> I don't plan to port playonlinux to Python 3. However, a new version >> of playonlinux is currently developped under Java [1]. There is no >> release date for now, but I will >> package it when a stable version is available. >> >> Best, >> Bertrand >> >> [1] https://github.com/PhoenicisOrg/phoenicis > > Should we then RM playonlinux from Debian? > > Scott Why should we remove playonlinux from Debian? There is a Java port that just needs to be packaged. Python 2 has not been removed from Debian yet. All that is needed is someone who works on it. It is completely reasonable to have a package in unstable and not in testing for a while, especially when it has a popcon inst value of more than 4700. signature.asc Description: OpenPGP digital signature
Bug#937302: playonlinux: Python2 removal in sid/bullseye
On Sat, 29 Feb 2020, Bertrand Marc wrote: On Thu, 30 Jan 2020, Scott Talbert wrote: What is the games team plan for Python 3 support in playonlinux? Do you plan to port it to Python 3? Or remove? I don't plan to port playonlinux to Python 3. However, a new version of playonlinux is currently developped under Java [1]. There is no release date for now, but I will package it when a stable version is available. Best, Bertrand [1] https://github.com/PhoenicisOrg/phoenicis Should we then RM playonlinux from Debian? Scott
Bug#937302: playonlinux: Python2 removal in sid/bullseye
Hi Scott, > On Thu, 30 Jan 2020, Scott Talbert wrote: >> >> What is the games team plan for Python 3 support in playonlinux? Do you >> plan to port it to Python 3? Or remove? I don't plan to port playonlinux to Python 3. However, a new version of playonlinux is currently developped under Java [1]. There is no release date for now, but I will package it when a stable version is available. Best, Bertrand [1] https://github.com/PhoenicisOrg/phoenicis
Bug#937302: playonlinux: Python2 removal in sid/bullseye
On Thu, 30 Jan 2020, Scott Talbert wrote: Package: src:playonlinux Version: 4.3.4-1 Severity: normal Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2removal Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html Your package either build-depends, depends on Python2, or uses Python2 in the autopkg tests. Please stop using Python2, and fix this issue by one of the following actions. Hello, What is the games team plan for Python 3 support in playonlinux? Do you plan to port it to Python 3? Or remove? Ping?
Bug#937302: playonlinux: Python2 removal in sid/bullseye
On Fri, 30 Aug 2019, Matthias Klose wrote: Package: src:playonlinux Version: 4.3.4-1 Severity: normal Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2removal Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html Your package either build-depends, depends on Python2, or uses Python2 in the autopkg tests. Please stop using Python2, and fix this issue by one of the following actions. Hello, What is the games team plan for Python 3 support in playonlinux? Do you plan to port it to Python 3? Or remove? Thanks, Scott
