Package: golang-github-golang-jwt-jwt Severity: wishlist Hi. For your information, I have uploaded golang-github-golang-jwt-jwt-v5 since v5 is required by (at least) ssh3 that I'm packaging. I'm opening this bug to discuss:
1) Can you confirm that golang-github-golang-jwt-jwt cannot be upgraded past v4 due to the dependencies stuck on v4 API? Or is there a way? I see that you uploaded v5.0.0 and then had to revert back to 4.5.0 earlier. This assumption is behind the upload of v5. 2) How about shipping the 'jwt' binary from the v5 source package? I'm not entirely sure how to go about that -- maybe you drop the binary package and upload to experimental, and I'll add the binary package in the v5 package and upload to experimental, and we can test upgrade cycles, and then synchronize a time to upload both into unstable? Other ideas how to do the migration are appreciated, I'm not sure there are good documentation on this. The ftp-master were quite quick to approve the v5 package (6 hours!), I had intended to reach out to you before it ended up in the archive -- sorry about that. Btw, feel free to help maintain the v5 package and add yourself as Uploaders too. /Simon
signature.asc
Description: PGP signature
