Building fixes/32 packages for Debian 10 or 11 fails to clone from GitHub about packaging HOT 5 CLOSED

Does this help when applying to fixes/32 ?
59f9ca0
See
#123

from packaging.

Yes, that fixes the problem - thank you very much for your help - You are a STAR!!!! :)

The "mythtv.make" that arrives in the "packaging.git" for fixes/32 still has the "git" rather than the "https" reference, so I had to make the changes myself before starting the build - Granted, this wasn't a difficult thing to do, once I knew the problem, but wouldn't it be easier (and far more friendly to potential Mythtv users) to make this change at the source, rather than having to go through the process of failure?

Thanks once again for your help - Very much appreciated. I've been a Mythtv user since about 2007 - not sure how I could now do without it LOL.

from packaging.

I cherry-picked it to fixes/32 (4a63b1f)

from packaging.

I just had the same problem on the fixes/31 branch (trying to build a new frontend to match an existing backend). Is it worth documenting the oldest release which is considered "supported" and checking this has been cherry picked into the relevant branches?

from packaging.