> Your patch has a different context than the upstream commit, how did you create it? This makes it hard to check that the patch matches the upstream commit.
Do you have specifics in mind? I generated the patches using git format-patch from commits 29c5148598b5e48e505da3d620d9a30c49f1da0b and 302c111b99f19cee153cd68017629231eaa2371a. The only difference I see between these upstream commits and the ones in d/patches is that the CHANGLELOG section is not updated in the docs/index.rst file. I did not include it because the mentioned changes were under a "Version UNRELEASED (YYYY-MM-DD)" section that is not present in a released version. I also changed the "raw patches" from format-patch to add dep-3 headers instead of the "From 29c5148598b5e48e505da3d620d9a30c49f1da0b" that is generated by git format-patch. If formatting them with dep-3 headers was a mistake, then I can use the raw output of git format-patch instead. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2115654 Title: PyOtherSideQtRCImporter broken on Python3.12 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pyotherside/+bug/2115654/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
