Re: [HEADS UP] wxPython 4.2.0 in Rawhide
On Tue, 16 Aug 2022, Steven A. Falco wrote: On 8/16/22 09:29 AM, Steven A. Falco wrote: On 8/15/22 08:38 PM, Scott Talbert wrote: On Sat, 13 Aug 2022, Steven A. Falco wrote: On 8/12/22 11:35 AM, Steven A. Falco wrote: On 8/12/22 11:00 AM, Scott Talbert wrote: On Fri, 12 Aug 2022, Steven A. Falco wrote: It turns out that there is a bug in wxPython whereby it installs an error handler that should not be installed by a library [1]. KiCad can work around that by adding a compile flag to disable its own error handler [2]. Credit to Ian for identifying the problem and the work-around. I've started a new KiCad build [3] in the side-tag. [1] https://github.com/wxWidgets/wxWidgets/issues/22717 [2] https://gitlab.com/kicad/code/kicad/-/issues/12217 [3] https://koji.fedoraproject.org/koji/taskinfo?taskID=90710152 The KiCad build in the side-tag completed, and I've tested it on x86_64 and aarch64. It all looks good, so I am fine with merging the side-tag. Scott - What will be the process for getting this into F37? I'm curious as to the timeline so I can handle the changes there. OK, I went ahead and submitted the bodhi request to merge the side-tag. On F37, do you have any strong feelings about whether this should or should not go in F37? If yes, we should probably do a similar side-tag build. Thanks for allowing us to have input on that, Scott. I posted a message to the KiCad developers to get their comments, since I would need their support to fix any bugs that might come up. I'll forward their preferences as soon as I hear from them. The KiCad developers are in favor of updating to wxPython 4.2.0 in Fedora 37. Scott - if you agree, please set up a side-tag when convenient. I'll then make the necessary KiCad changes and run a build in the side-tag. Done, created side tag f37-build-side-56650 and built wxPython there. Thanks - I've started a KiCad build [1]. It should be ready later today. [1] https://koji.fedoraproject.org/koji/taskinfo?taskID=90874286 The KiCad build for F37 is complete in f37-build-side-56650. Scott - please merge the tag when convenient. Thanks. Done - thanks! Let me know if you run into any issues. I'll cherry-pick the fix for that issue with GLib logging as soon as upstream fixes it, and you can remove the workaround in kicad. Scott___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: [HEADS UP] wxPython 4.2.0 in Rawhide
On 8/16/22 09:29 AM, Steven A. Falco wrote: On 8/15/22 08:38 PM, Scott Talbert wrote: On Sat, 13 Aug 2022, Steven A. Falco wrote: On 8/12/22 11:35 AM, Steven A. Falco wrote: On 8/12/22 11:00 AM, Scott Talbert wrote: On Fri, 12 Aug 2022, Steven A. Falco wrote: It turns out that there is a bug in wxPython whereby it installs an error handler that should not be installed by a library [1]. KiCad can work around that by adding a compile flag to disable its own error handler [2]. Credit to Ian for identifying the problem and the work-around. I've started a new KiCad build [3] in the side-tag. [1] https://github.com/wxWidgets/wxWidgets/issues/22717 [2] https://gitlab.com/kicad/code/kicad/-/issues/12217 [3] https://koji.fedoraproject.org/koji/taskinfo?taskID=90710152 The KiCad build in the side-tag completed, and I've tested it on x86_64 and aarch64. It all looks good, so I am fine with merging the side-tag. Scott - What will be the process for getting this into F37? I'm curious as to the timeline so I can handle the changes there. OK, I went ahead and submitted the bodhi request to merge the side-tag. On F37, do you have any strong feelings about whether this should or should not go in F37? If yes, we should probably do a similar side-tag build. Thanks for allowing us to have input on that, Scott. I posted a message to the KiCad developers to get their comments, since I would need their support to fix any bugs that might come up. I'll forward their preferences as soon as I hear from them. The KiCad developers are in favor of updating to wxPython 4.2.0 in Fedora 37. Scott - if you agree, please set up a side-tag when convenient. I'll then make the necessary KiCad changes and run a build in the side-tag. Done, created side tag f37-build-side-56650 and built wxPython there. Thanks - I've started a KiCad build [1]. It should be ready later today. [1] https://koji.fedoraproject.org/koji/taskinfo?taskID=90874286 The KiCad build for F37 is complete in f37-build-side-56650. Scott - please merge the tag when convenient. Thanks. Steve ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: [HEADS UP] wxPython 4.2.0 in Rawhide
On 8/15/22 08:38 PM, Scott Talbert wrote: On Sat, 13 Aug 2022, Steven A. Falco wrote: On 8/12/22 11:35 AM, Steven A. Falco wrote: On 8/12/22 11:00 AM, Scott Talbert wrote: On Fri, 12 Aug 2022, Steven A. Falco wrote: It turns out that there is a bug in wxPython whereby it installs an error handler that should not be installed by a library [1]. KiCad can work around that by adding a compile flag to disable its own error handler [2]. Credit to Ian for identifying the problem and the work-around. I've started a new KiCad build [3] in the side-tag. [1] https://github.com/wxWidgets/wxWidgets/issues/22717 [2] https://gitlab.com/kicad/code/kicad/-/issues/12217 [3] https://koji.fedoraproject.org/koji/taskinfo?taskID=90710152 The KiCad build in the side-tag completed, and I've tested it on x86_64 and aarch64. It all looks good, so I am fine with merging the side-tag. Scott - What will be the process for getting this into F37? I'm curious as to the timeline so I can handle the changes there. OK, I went ahead and submitted the bodhi request to merge the side-tag. On F37, do you have any strong feelings about whether this should or should not go in F37? If yes, we should probably do a similar side-tag build. Thanks for allowing us to have input on that, Scott. I posted a message to the KiCad developers to get their comments, since I would need their support to fix any bugs that might come up. I'll forward their preferences as soon as I hear from them. The KiCad developers are in favor of updating to wxPython 4.2.0 in Fedora 37. Scott - if you agree, please set up a side-tag when convenient. I'll then make the necessary KiCad changes and run a build in the side-tag. Done, created side tag f37-build-side-56650 and built wxPython there. Thanks - I've started a KiCad build [1]. It should be ready later today. Steve [1] https://koji.fedoraproject.org/koji/taskinfo?taskID=90874286 ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: [HEADS UP] wxPython 4.2.0 in Rawhide
On Sat, 13 Aug 2022, Steven A. Falco wrote: On 8/12/22 11:35 AM, Steven A. Falco wrote: On 8/12/22 11:00 AM, Scott Talbert wrote: On Fri, 12 Aug 2022, Steven A. Falco wrote: It turns out that there is a bug in wxPython whereby it installs an error handler that should not be installed by a library [1]. KiCad can work around that by adding a compile flag to disable its own error handler [2]. Credit to Ian for identifying the problem and the work-around. I've started a new KiCad build [3] in the side-tag. [1] https://github.com/wxWidgets/wxWidgets/issues/22717 [2] https://gitlab.com/kicad/code/kicad/-/issues/12217 [3] https://koji.fedoraproject.org/koji/taskinfo?taskID=90710152 The KiCad build in the side-tag completed, and I've tested it on x86_64 and aarch64. It all looks good, so I am fine with merging the side-tag. Scott - What will be the process for getting this into F37? I'm curious as to the timeline so I can handle the changes there. OK, I went ahead and submitted the bodhi request to merge the side-tag. On F37, do you have any strong feelings about whether this should or should not go in F37? If yes, we should probably do a similar side-tag build. Thanks for allowing us to have input on that, Scott. I posted a message to the KiCad developers to get their comments, since I would need their support to fix any bugs that might come up. I'll forward their preferences as soon as I hear from them. The KiCad developers are in favor of updating to wxPython 4.2.0 in Fedora 37. Scott - if you agree, please set up a side-tag when convenient. I'll then make the necessary KiCad changes and run a build in the side-tag. Done, created side tag f37-build-side-56650 and built wxPython there. Scott___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: [HEADS UP] wxPython 4.2.0 in Rawhide
On 8/12/22 11:35 AM, Steven A. Falco wrote: On 8/12/22 11:00 AM, Scott Talbert wrote: On Fri, 12 Aug 2022, Steven A. Falco wrote: It turns out that there is a bug in wxPython whereby it installs an error handler that should not be installed by a library [1]. KiCad can work around that by adding a compile flag to disable its own error handler [2]. Credit to Ian for identifying the problem and the work-around. I've started a new KiCad build [3] in the side-tag. [1] https://github.com/wxWidgets/wxWidgets/issues/22717 [2] https://gitlab.com/kicad/code/kicad/-/issues/12217 [3] https://koji.fedoraproject.org/koji/taskinfo?taskID=90710152 The KiCad build in the side-tag completed, and I've tested it on x86_64 and aarch64. It all looks good, so I am fine with merging the side-tag. Scott - What will be the process for getting this into F37? I'm curious as to the timeline so I can handle the changes there. OK, I went ahead and submitted the bodhi request to merge the side-tag. On F37, do you have any strong feelings about whether this should or should not go in F37? If yes, we should probably do a similar side-tag build. Thanks for allowing us to have input on that, Scott. I posted a message to the KiCad developers to get their comments, since I would need their support to fix any bugs that might come up. I'll forward their preferences as soon as I hear from them. The KiCad developers are in favor of updating to wxPython 4.2.0 in Fedora 37. Scott - if you agree, please set up a side-tag when convenient. I'll then make the necessary KiCad changes and run a build in the side-tag. Steve ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: [HEADS UP] wxPython 4.2.0 in Rawhide
On 8/12/22 11:00 AM, Scott Talbert wrote: On Fri, 12 Aug 2022, Steven A. Falco wrote: It turns out that there is a bug in wxPython whereby it installs an error handler that should not be installed by a library [1]. KiCad can work around that by adding a compile flag to disable its own error handler [2]. Credit to Ian for identifying the problem and the work-around. I've started a new KiCad build [3] in the side-tag. [1] https://github.com/wxWidgets/wxWidgets/issues/22717 [2] https://gitlab.com/kicad/code/kicad/-/issues/12217 [3] https://koji.fedoraproject.org/koji/taskinfo?taskID=90710152 The KiCad build in the side-tag completed, and I've tested it on x86_64 and aarch64. It all looks good, so I am fine with merging the side-tag. Scott - What will be the process for getting this into F37? I'm curious as to the timeline so I can handle the changes there. OK, I went ahead and submitted the bodhi request to merge the side-tag. On F37, do you have any strong feelings about whether this should or should not go in F37? If yes, we should probably do a similar side-tag build. Thanks for allowing us to have input on that, Scott. I posted a message to the KiCad developers to get their comments, since I would need their support to fix any bugs that might come up. I'll forward their preferences as soon as I hear from them. Steve ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: [HEADS UP] wxPython 4.2.0 in Rawhide
On Fri, 12 Aug 2022, Steven A. Falco wrote: It turns out that there is a bug in wxPython whereby it installs an error handler that should not be installed by a library [1]. KiCad can work around that by adding a compile flag to disable its own error handler [2]. Credit to Ian for identifying the problem and the work-around. I've started a new KiCad build [3] in the side-tag. [1] https://github.com/wxWidgets/wxWidgets/issues/22717 [2] https://gitlab.com/kicad/code/kicad/-/issues/12217 [3] https://koji.fedoraproject.org/koji/taskinfo?taskID=90710152 The KiCad build in the side-tag completed, and I've tested it on x86_64 and aarch64. It all looks good, so I am fine with merging the side-tag. Scott - What will be the process for getting this into F37? I'm curious as to the timeline so I can handle the changes there. OK, I went ahead and submitted the bodhi request to merge the side-tag. On F37, do you have any strong feelings about whether this should or should not go in F37? If yes, we should probably do a similar side-tag build. Scott___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: [HEADS UP] wxPython 4.2.0 in Rawhide
On 8/11/22 03:43 PM, Steven A. Falco wrote: It turns out that there is a bug in wxPython whereby it installs an error handler that should not be installed by a library [1]. KiCad can work around that by adding a compile flag to disable its own error handler [2]. Credit to Ian for identifying the problem and the work-around. I've started a new KiCad build [3] in the side-tag. [1] https://github.com/wxWidgets/wxWidgets/issues/22717 [2] https://gitlab.com/kicad/code/kicad/-/issues/12217 [3] https://koji.fedoraproject.org/koji/taskinfo?taskID=90710152 The KiCad build in the side-tag completed, and I've tested it on x86_64 and aarch64. It all looks good, so I am fine with merging the side-tag. Scott - What will be the process for getting this into F37? I'm curious as to the timeline so I can handle the changes there. Steve ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: [HEADS UP] wxPython 4.2.0 in Rawhide
On 8/11/22 12:26 PM, Steven A. Falco wrote: On 8/11/22 09:56 AM, Steven A. Falco wrote: On 8/10/22 07:41 PM, Scott Talbert wrote: On Tue, 9 Aug 2022, Steven A. Falco wrote: On 8/9/22 06:00 PM, Scott Talbert wrote: On Tue, 9 Aug 2022, Steven A. Falco wrote: On 8/9/22 05:06 PM, Scott Talbert wrote: On Tue, 9 Aug 2022, Steven A. Falco wrote: On 8/9/22 02:25 PM, Steven A. Falco wrote: On 8/9/22 01:09 PM, Scott Talbert wrote: Hi, Upstream wxPython has finally made a new release and this involves migrating to wxWidgets 3.2.0 at the same time. I'm planning to build the new wxPython in Rawhide after F37 branch (although could put it in F37 later). For those packages that use both wxPython and wxWidgets (I *think* this is just kicad?), do you want me to do this in a side-tag so we can switch the packages at the same time? Or just build in rawhide and let you fix things up? That is very good news, Scott. The upstream KiCad devs are working on 3.2.0 right now, as part of their efforts to support the new M1 Apple machines. If KiCad is the only customer, I'd say there is no need to do a side-tag, unless that is easier for you. I'm fine either way. I should add that I would like to see this in F37 at some point, because that will help with retiring the old wxWidgets code from KiCad sooner. Yeah, we can get the changes into F37. So KiCad isn't quite ready to move yet? I can hold off until you're ready. I've spoken with the upstream KiCad developers, and based on that conversation I think you should go ahead and put the new wxWidgets / wxPython into Rawhide when it is convenient for you, without waiting for KiCad. There is a KiCad Copr [1], where we make nightly pre-release builds of what will become the KiCad 7.x series, with 7.0.0 probably releasing towards the end of the year. The KiCad 7 series is where the upstream devs prefer to integrate with the new wxWidgets / wxPython both because of the risk of new bugs and also so they don't have to backport fixes to the older KiCad 6.x series. So, once you have the new wxWidgets / wxPython in Rawhide, I'll try it out locally and in our Copr. Based on how that goes, we can consider switching over the downstream Rawhide builds. But based on the way the timing has worked out, and because we don't want to do a major version upgrade of KiCad in a stable Fedora release, we may not be able to switch KiCad to the new wxWidgets / wxPython in F37. The problem though, is that while wxWidgets versions are parallel installable, wxPython versions are not. So, once I update to wxPython 4.2.0 (which links with wxWidgets 3.2.0), wxPython 4.0.7 will be gone. I'm presuming that's going to break KiCad? It is a bit awkward to be mediating between the Fedora devel list and the KiCad one, but I think we are nearly there. According to one of the KiCad leads: "The Flatpak has been running the wx 3.1 branch since v6 was released, and so far there have been no issues. We already have Windows and macOS running the 3.1 versions, so I don't see why we need to hold the Linux builds back." So, I think we are good to go forward and retire wxPython 4.0.7 at your convenience. If it is not too much trouble to use a side-tag, I'll make the KiCad build there and it can all go in together. My schedule is quite open, so I shouldn't hold you up. Please let me know whenever you are ready. No rush. And thanks for your patience. :-) OK, I pushed wxPython 4.2.0 to Rawhide (now F38) and am building in side tag f38-build-side-56468. It's still building at the moment. Also, I sent you a pull request to rebuild kicad with wxWidgets 3.2.0 and wxPython 4.2.0. I was able to rebuild it in a copr successfully with these changes. I merged your pull request. For some reason the merge button on the pull request page threw an error, so I added your fork as a remote, and merged it that way. It is building now [1] and will probably take 4 hours or so. Thanks for the patch! Steve [1] https://koji.fedoraproject.org/koji/taskinfo?taskID=90701098 I've cancelled that build. I tried running the x86_64 version in a VM and it crashes at various points. I'll have to investigate further. It turns out that there is a bug in wxPython whereby it installs an error handler that should not be installed by a library [1]. KiCad can work around that by adding a compile flag to disable its own error handler [2]. Credit to Ian for identifying the problem and the work-around. I've started a new KiCad build [3] in the side-tag. Steve [1] https://github.com/wxWidgets/wxWidgets/issues/22717 [2] https://gitlab.com/kicad/code/kicad/-/issues/12217 [3] https://koji.fedoraproject.org/koji/taskinfo?taskID=90710152 ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/proj
Re: [HEADS UP] wxPython 4.2.0 in Rawhide
On 8/11/22 09:56 AM, Steven A. Falco wrote: On 8/10/22 07:41 PM, Scott Talbert wrote: On Tue, 9 Aug 2022, Steven A. Falco wrote: On 8/9/22 06:00 PM, Scott Talbert wrote: On Tue, 9 Aug 2022, Steven A. Falco wrote: On 8/9/22 05:06 PM, Scott Talbert wrote: On Tue, 9 Aug 2022, Steven A. Falco wrote: On 8/9/22 02:25 PM, Steven A. Falco wrote: On 8/9/22 01:09 PM, Scott Talbert wrote: Hi, Upstream wxPython has finally made a new release and this involves migrating to wxWidgets 3.2.0 at the same time. I'm planning to build the new wxPython in Rawhide after F37 branch (although could put it in F37 later). For those packages that use both wxPython and wxWidgets (I *think* this is just kicad?), do you want me to do this in a side-tag so we can switch the packages at the same time? Or just build in rawhide and let you fix things up? That is very good news, Scott. The upstream KiCad devs are working on 3.2.0 right now, as part of their efforts to support the new M1 Apple machines. If KiCad is the only customer, I'd say there is no need to do a side-tag, unless that is easier for you. I'm fine either way. I should add that I would like to see this in F37 at some point, because that will help with retiring the old wxWidgets code from KiCad sooner. Yeah, we can get the changes into F37. So KiCad isn't quite ready to move yet? I can hold off until you're ready. I've spoken with the upstream KiCad developers, and based on that conversation I think you should go ahead and put the new wxWidgets / wxPython into Rawhide when it is convenient for you, without waiting for KiCad. There is a KiCad Copr [1], where we make nightly pre-release builds of what will become the KiCad 7.x series, with 7.0.0 probably releasing towards the end of the year. The KiCad 7 series is where the upstream devs prefer to integrate with the new wxWidgets / wxPython both because of the risk of new bugs and also so they don't have to backport fixes to the older KiCad 6.x series. So, once you have the new wxWidgets / wxPython in Rawhide, I'll try it out locally and in our Copr. Based on how that goes, we can consider switching over the downstream Rawhide builds. But based on the way the timing has worked out, and because we don't want to do a major version upgrade of KiCad in a stable Fedora release, we may not be able to switch KiCad to the new wxWidgets / wxPython in F37. The problem though, is that while wxWidgets versions are parallel installable, wxPython versions are not. So, once I update to wxPython 4.2.0 (which links with wxWidgets 3.2.0), wxPython 4.0.7 will be gone. I'm presuming that's going to break KiCad? It is a bit awkward to be mediating between the Fedora devel list and the KiCad one, but I think we are nearly there. According to one of the KiCad leads: "The Flatpak has been running the wx 3.1 branch since v6 was released, and so far there have been no issues. We already have Windows and macOS running the 3.1 versions, so I don't see why we need to hold the Linux builds back." So, I think we are good to go forward and retire wxPython 4.0.7 at your convenience. If it is not too much trouble to use a side-tag, I'll make the KiCad build there and it can all go in together. My schedule is quite open, so I shouldn't hold you up. Please let me know whenever you are ready. No rush. And thanks for your patience. :-) OK, I pushed wxPython 4.2.0 to Rawhide (now F38) and am building in side tag f38-build-side-56468. It's still building at the moment. Also, I sent you a pull request to rebuild kicad with wxWidgets 3.2.0 and wxPython 4.2.0. I was able to rebuild it in a copr successfully with these changes. I merged your pull request. For some reason the merge button on the pull request page threw an error, so I added your fork as a remote, and merged it that way. It is building now [1] and will probably take 4 hours or so. Thanks for the patch! Steve [1] https://koji.fedoraproject.org/koji/taskinfo?taskID=90701098 I've cancelled that build. I tried running the x86_64 version in a VM and it crashes at various points. I'll have to investigate further. Steve ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: [HEADS UP] wxPython 4.2.0 in Rawhide
On 8/10/22 07:41 PM, Scott Talbert wrote: On Tue, 9 Aug 2022, Steven A. Falco wrote: On 8/9/22 06:00 PM, Scott Talbert wrote: On Tue, 9 Aug 2022, Steven A. Falco wrote: On 8/9/22 05:06 PM, Scott Talbert wrote: On Tue, 9 Aug 2022, Steven A. Falco wrote: On 8/9/22 02:25 PM, Steven A. Falco wrote: On 8/9/22 01:09 PM, Scott Talbert wrote: Hi, Upstream wxPython has finally made a new release and this involves migrating to wxWidgets 3.2.0 at the same time. I'm planning to build the new wxPython in Rawhide after F37 branch (although could put it in F37 later). For those packages that use both wxPython and wxWidgets (I *think* this is just kicad?), do you want me to do this in a side-tag so we can switch the packages at the same time? Or just build in rawhide and let you fix things up? That is very good news, Scott. The upstream KiCad devs are working on 3.2.0 right now, as part of their efforts to support the new M1 Apple machines. If KiCad is the only customer, I'd say there is no need to do a side-tag, unless that is easier for you. I'm fine either way. I should add that I would like to see this in F37 at some point, because that will help with retiring the old wxWidgets code from KiCad sooner. Yeah, we can get the changes into F37. So KiCad isn't quite ready to move yet? I can hold off until you're ready. I've spoken with the upstream KiCad developers, and based on that conversation I think you should go ahead and put the new wxWidgets / wxPython into Rawhide when it is convenient for you, without waiting for KiCad. There is a KiCad Copr [1], where we make nightly pre-release builds of what will become the KiCad 7.x series, with 7.0.0 probably releasing towards the end of the year. The KiCad 7 series is where the upstream devs prefer to integrate with the new wxWidgets / wxPython both because of the risk of new bugs and also so they don't have to backport fixes to the older KiCad 6.x series. So, once you have the new wxWidgets / wxPython in Rawhide, I'll try it out locally and in our Copr. Based on how that goes, we can consider switching over the downstream Rawhide builds. But based on the way the timing has worked out, and because we don't want to do a major version upgrade of KiCad in a stable Fedora release, we may not be able to switch KiCad to the new wxWidgets / wxPython in F37. The problem though, is that while wxWidgets versions are parallel installable, wxPython versions are not. So, once I update to wxPython 4.2.0 (which links with wxWidgets 3.2.0), wxPython 4.0.7 will be gone. I'm presuming that's going to break KiCad? It is a bit awkward to be mediating between the Fedora devel list and the KiCad one, but I think we are nearly there. According to one of the KiCad leads: "The Flatpak has been running the wx 3.1 branch since v6 was released, and so far there have been no issues. We already have Windows and macOS running the 3.1 versions, so I don't see why we need to hold the Linux builds back." So, I think we are good to go forward and retire wxPython 4.0.7 at your convenience. If it is not too much trouble to use a side-tag, I'll make the KiCad build there and it can all go in together. My schedule is quite open, so I shouldn't hold you up. Please let me know whenever you are ready. No rush. And thanks for your patience. :-) OK, I pushed wxPython 4.2.0 to Rawhide (now F38) and am building in side tag f38-build-side-56468. It's still building at the moment. Also, I sent you a pull request to rebuild kicad with wxWidgets 3.2.0 and wxPython 4.2.0. I was able to rebuild it in a copr successfully with these changes. I merged your pull request. For some reason the merge button on the pull request page threw an error, so I added your fork as a remote, and merged it that way. It is building now [1] and will probably take 4 hours or so. Thanks for the patch! Steve [1] https://koji.fedoraproject.org/koji/taskinfo?taskID=90701098 ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: [HEADS UP] wxPython 4.2.0 in Rawhide
On Tue, 9 Aug 2022, Steven A. Falco wrote: On 8/9/22 06:00 PM, Scott Talbert wrote: On Tue, 9 Aug 2022, Steven A. Falco wrote: On 8/9/22 05:06 PM, Scott Talbert wrote: On Tue, 9 Aug 2022, Steven A. Falco wrote: On 8/9/22 02:25 PM, Steven A. Falco wrote: On 8/9/22 01:09 PM, Scott Talbert wrote: Hi, Upstream wxPython has finally made a new release and this involves migrating to wxWidgets 3.2.0 at the same time. I'm planning to build the new wxPython in Rawhide after F37 branch (although could put it in F37 later). For those packages that use both wxPython and wxWidgets (I *think* this is just kicad?), do you want me to do this in a side-tag so we can switch the packages at the same time? Or just build in rawhide and let you fix things up? That is very good news, Scott. The upstream KiCad devs are working on 3.2.0 right now, as part of their efforts to support the new M1 Apple machines. If KiCad is the only customer, I'd say there is no need to do a side-tag, unless that is easier for you. I'm fine either way. I should add that I would like to see this in F37 at some point, because that will help with retiring the old wxWidgets code from KiCad sooner. Yeah, we can get the changes into F37. So KiCad isn't quite ready to move yet? I can hold off until you're ready. I've spoken with the upstream KiCad developers, and based on that conversation I think you should go ahead and put the new wxWidgets / wxPython into Rawhide when it is convenient for you, without waiting for KiCad. There is a KiCad Copr [1], where we make nightly pre-release builds of what will become the KiCad 7.x series, with 7.0.0 probably releasing towards the end of the year. The KiCad 7 series is where the upstream devs prefer to integrate with the new wxWidgets / wxPython both because of the risk of new bugs and also so they don't have to backport fixes to the older KiCad 6.x series. So, once you have the new wxWidgets / wxPython in Rawhide, I'll try it out locally and in our Copr. Based on how that goes, we can consider switching over the downstream Rawhide builds. But based on the way the timing has worked out, and because we don't want to do a major version upgrade of KiCad in a stable Fedora release, we may not be able to switch KiCad to the new wxWidgets / wxPython in F37. The problem though, is that while wxWidgets versions are parallel installable, wxPython versions are not. So, once I update to wxPython 4.2.0 (which links with wxWidgets 3.2.0), wxPython 4.0.7 will be gone. I'm presuming that's going to break KiCad? It is a bit awkward to be mediating between the Fedora devel list and the KiCad one, but I think we are nearly there. According to one of the KiCad leads: "The Flatpak has been running the wx 3.1 branch since v6 was released, and so far there have been no issues. We already have Windows and macOS running the 3.1 versions, so I don't see why we need to hold the Linux builds back." So, I think we are good to go forward and retire wxPython 4.0.7 at your convenience. If it is not too much trouble to use a side-tag, I'll make the KiCad build there and it can all go in together. My schedule is quite open, so I shouldn't hold you up. Please let me know whenever you are ready. No rush. And thanks for your patience. :-) OK, I pushed wxPython 4.2.0 to Rawhide (now F38) and am building in side tag f38-build-side-56468. It's still building at the moment. Also, I sent you a pull request to rebuild kicad with wxWidgets 3.2.0 and wxPython 4.2.0. I was able to rebuild it in a copr successfully with these changes. Thanks, Scott___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: [HEADS UP] wxPython 4.2.0 in Rawhide
On 8/9/22 06:00 PM, Scott Talbert wrote: On Tue, 9 Aug 2022, Steven A. Falco wrote: On 8/9/22 05:06 PM, Scott Talbert wrote: On Tue, 9 Aug 2022, Steven A. Falco wrote: On 8/9/22 02:25 PM, Steven A. Falco wrote: On 8/9/22 01:09 PM, Scott Talbert wrote: Hi, Upstream wxPython has finally made a new release and this involves migrating to wxWidgets 3.2.0 at the same time. I'm planning to build the new wxPython in Rawhide after F37 branch (although could put it in F37 later). For those packages that use both wxPython and wxWidgets (I *think* this is just kicad?), do you want me to do this in a side-tag so we can switch the packages at the same time? Or just build in rawhide and let you fix things up? That is very good news, Scott. The upstream KiCad devs are working on 3.2.0 right now, as part of their efforts to support the new M1 Apple machines. If KiCad is the only customer, I'd say there is no need to do a side-tag, unless that is easier for you. I'm fine either way. I should add that I would like to see this in F37 at some point, because that will help with retiring the old wxWidgets code from KiCad sooner. Yeah, we can get the changes into F37. So KiCad isn't quite ready to move yet? I can hold off until you're ready. I've spoken with the upstream KiCad developers, and based on that conversation I think you should go ahead and put the new wxWidgets / wxPython into Rawhide when it is convenient for you, without waiting for KiCad. There is a KiCad Copr [1], where we make nightly pre-release builds of what will become the KiCad 7.x series, with 7.0.0 probably releasing towards the end of the year. The KiCad 7 series is where the upstream devs prefer to integrate with the new wxWidgets / wxPython both because of the risk of new bugs and also so they don't have to backport fixes to the older KiCad 6.x series. So, once you have the new wxWidgets / wxPython in Rawhide, I'll try it out locally and in our Copr. Based on how that goes, we can consider switching over the downstream Rawhide builds. But based on the way the timing has worked out, and because we don't want to do a major version upgrade of KiCad in a stable Fedora release, we may not be able to switch KiCad to the new wxWidgets / wxPython in F37. The problem though, is that while wxWidgets versions are parallel installable, wxPython versions are not. So, once I update to wxPython 4.2.0 (which links with wxWidgets 3.2.0), wxPython 4.0.7 will be gone. I'm presuming that's going to break KiCad? It is a bit awkward to be mediating between the Fedora devel list and the KiCad one, but I think we are nearly there. According to one of the KiCad leads: "The Flatpak has been running the wx 3.1 branch since v6 was released, and so far there have been no issues. We already have Windows and macOS running the 3.1 versions, so I don't see why we need to hold the Linux builds back." So, I think we are good to go forward and retire wxPython 4.0.7 at your convenience. If it is not too much trouble to use a side-tag, I'll make the KiCad build there and it can all go in together. My schedule is quite open, so I shouldn't hold you up. Please let me know whenever you are ready. No rush. And thanks for your patience. :-) Steve ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: [HEADS UP] wxPython 4.2.0 in Rawhide
On Tue, 9 Aug 2022, Steven A. Falco wrote: On 8/9/22 05:06 PM, Scott Talbert wrote: On Tue, 9 Aug 2022, Steven A. Falco wrote: On 8/9/22 02:25 PM, Steven A. Falco wrote: On 8/9/22 01:09 PM, Scott Talbert wrote: Hi, Upstream wxPython has finally made a new release and this involves migrating to wxWidgets 3.2.0 at the same time. I'm planning to build the new wxPython in Rawhide after F37 branch (although could put it in F37 later). For those packages that use both wxPython and wxWidgets (I *think* this is just kicad?), do you want me to do this in a side-tag so we can switch the packages at the same time? Or just build in rawhide and let you fix things up? That is very good news, Scott. The upstream KiCad devs are working on 3.2.0 right now, as part of their efforts to support the new M1 Apple machines. If KiCad is the only customer, I'd say there is no need to do a side-tag, unless that is easier for you. I'm fine either way. I should add that I would like to see this in F37 at some point, because that will help with retiring the old wxWidgets code from KiCad sooner. Yeah, we can get the changes into F37. So KiCad isn't quite ready to move yet? I can hold off until you're ready. I've spoken with the upstream KiCad developers, and based on that conversation I think you should go ahead and put the new wxWidgets / wxPython into Rawhide when it is convenient for you, without waiting for KiCad. There is a KiCad Copr [1], where we make nightly pre-release builds of what will become the KiCad 7.x series, with 7.0.0 probably releasing towards the end of the year. The KiCad 7 series is where the upstream devs prefer to integrate with the new wxWidgets / wxPython both because of the risk of new bugs and also so they don't have to backport fixes to the older KiCad 6.x series. So, once you have the new wxWidgets / wxPython in Rawhide, I'll try it out locally and in our Copr. Based on how that goes, we can consider switching over the downstream Rawhide builds. But based on the way the timing has worked out, and because we don't want to do a major version upgrade of KiCad in a stable Fedora release, we may not be able to switch KiCad to the new wxWidgets / wxPython in F37. The problem though, is that while wxWidgets versions are parallel installable, wxPython versions are not. So, once I update to wxPython 4.2.0 (which links with wxWidgets 3.2.0), wxPython 4.0.7 will be gone. I'm presuming that's going to break KiCad? Scott___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: [HEADS UP] wxPython 4.2.0 in Rawhide
On 8/9/22 05:06 PM, Scott Talbert wrote: On Tue, 9 Aug 2022, Steven A. Falco wrote: On 8/9/22 02:25 PM, Steven A. Falco wrote: On 8/9/22 01:09 PM, Scott Talbert wrote: Hi, Upstream wxPython has finally made a new release and this involves migrating to wxWidgets 3.2.0 at the same time. I'm planning to build the new wxPython in Rawhide after F37 branch (although could put it in F37 later). For those packages that use both wxPython and wxWidgets (I *think* this is just kicad?), do you want me to do this in a side-tag so we can switch the packages at the same time? Or just build in rawhide and let you fix things up? That is very good news, Scott. The upstream KiCad devs are working on 3.2.0 right now, as part of their efforts to support the new M1 Apple machines. If KiCad is the only customer, I'd say there is no need to do a side-tag, unless that is easier for you. I'm fine either way. I should add that I would like to see this in F37 at some point, because that will help with retiring the old wxWidgets code from KiCad sooner. Yeah, we can get the changes into F37. So KiCad isn't quite ready to move yet? I can hold off until you're ready. I've spoken with the upstream KiCad developers, and based on that conversation I think you should go ahead and put the new wxWidgets / wxPython into Rawhide when it is convenient for you, without waiting for KiCad. There is a KiCad Copr [1], where we make nightly pre-release builds of what will become the KiCad 7.x series, with 7.0.0 probably releasing towards the end of the year. The KiCad 7 series is where the upstream devs prefer to integrate with the new wxWidgets / wxPython both because of the risk of new bugs and also so they don't have to backport fixes to the older KiCad 6.x series. So, once you have the new wxWidgets / wxPython in Rawhide, I'll try it out locally and in our Copr. Based on how that goes, we can consider switching over the downstream Rawhide builds. But based on the way the timing has worked out, and because we don't want to do a major version upgrade of KiCad in a stable Fedora release, we may not be able to switch KiCad to the new wxWidgets / wxPython in F37. Steve [1] https://copr.fedorainfracloud.org/coprs/g/kicad/kicad/ ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: [HEADS UP] wxPython 4.2.0 in Rawhide
On Tue, 9 Aug 2022, Steven A. Falco wrote: On 8/9/22 02:25 PM, Steven A. Falco wrote: On 8/9/22 01:09 PM, Scott Talbert wrote: Hi, Upstream wxPython has finally made a new release and this involves migrating to wxWidgets 3.2.0 at the same time. I'm planning to build the new wxPython in Rawhide after F37 branch (although could put it in F37 later). For those packages that use both wxPython and wxWidgets (I *think* this is just kicad?), do you want me to do this in a side-tag so we can switch the packages at the same time? Or just build in rawhide and let you fix things up? That is very good news, Scott. The upstream KiCad devs are working on 3.2.0 right now, as part of their efforts to support the new M1 Apple machines. If KiCad is the only customer, I'd say there is no need to do a side-tag, unless that is easier for you. I'm fine either way. I should add that I would like to see this in F37 at some point, because that will help with retiring the old wxWidgets code from KiCad sooner. Yeah, we can get the changes into F37. So KiCad isn't quite ready to move yet? I can hold off until you're ready. Scott___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: [HEADS UP] wxPython 4.2.0 in Rawhide
On 8/9/22 02:25 PM, Steven A. Falco wrote: On 8/9/22 01:09 PM, Scott Talbert wrote: Hi, Upstream wxPython has finally made a new release and this involves migrating to wxWidgets 3.2.0 at the same time. I'm planning to build the new wxPython in Rawhide after F37 branch (although could put it in F37 later). For those packages that use both wxPython and wxWidgets (I *think* this is just kicad?), do you want me to do this in a side-tag so we can switch the packages at the same time? Or just build in rawhide and let you fix things up? That is very good news, Scott. The upstream KiCad devs are working on 3.2.0 right now, as part of their efforts to support the new M1 Apple machines. If KiCad is the only customer, I'd say there is no need to do a side-tag, unless that is easier for you. I'm fine either way. I should add that I would like to see this in F37 at some point, because that will help with retiring the old wxWidgets code from KiCad sooner. Steve ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: [HEADS UP] wxPython 4.2.0 in Rawhide
On 8/9/22 01:09 PM, Scott Talbert wrote: Hi, Upstream wxPython has finally made a new release and this involves migrating to wxWidgets 3.2.0 at the same time. I'm planning to build the new wxPython in Rawhide after F37 branch (although could put it in F37 later). For those packages that use both wxPython and wxWidgets (I *think* this is just kicad?), do you want me to do this in a side-tag so we can switch the packages at the same time? Or just build in rawhide and let you fix things up? That is very good news, Scott. The upstream KiCad devs are working on 3.2.0 right now, as part of their efforts to support the new M1 Apple machines. If KiCad is the only customer, I'd say there is no need to do a side-tag, unless that is easier for you. I'm fine either way. Thanks, Steve ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
