Hello Thomas, > There are autopkgtest for most of the reverese depends of jsonschemat. Feel > free to NMU it to experimental, so we can use the pseudo-excuse patch to see > if the transition goes well...
Awesome, I started working on a "new" release (upstream made 3 more releases in the meanwhile) and I'm pushing my work to my fork on salsa: https://salsa.debian.org/samueloph/python-jsonschema/-/tree/debian/samueloph/new-release In case anyone looks at it, beware that the branch might be in an ugly state (test commits and stuff) as I'm using that as a backup for my work while I change between laptop and desktop. Also if anyone gets ahead of me, feel free to use what I did and upload it first. The package is building fine, but I still need to write proper commit messages and patch descriptions (besides checking if I broke any doc with the sphinx changes). Thomas, when I'm ready to upload to experimental, how should I proceed with merging the changes? I can always keep them in my fork for you to pick and push, if that's easier. I say this because publishing an MR against debian/yoga doesn't seem like it's enough as the upstream releases are kept in the repo by their tags (not branches). Or maybe you want to keep this outside of the git repo until it reaches experimental? Either way is fine for me. Thank you! -- Samuel Henrique <samueloph>
