I've changed the metadata to reflect your last update. However, would it be possible to give an explicit rationale for the Won't Fix in Kinetic? I'm guessing it's due to Kinetic being almost EOL combined with the server-centric nature of the package ?
Also, I'm a bit confused by the debian/changelog part of the debdiff, as it removes Jammy-related entries to add a Focal one. Would it be possible to generate one for each targetted release against the relevant versions currently in the archive to clarify things?
In addition, it's usually required to explicitly mark out all the fixed bugs in the changelog entry via a LP: #XXXXXXX stanza so that their status can be automatically updated as the package goes through the motions.
Hi,
I've changed the metadata to reflect your last update. However, would it be possible to give an explicit rationale for the Won't Fix in Kinetic? I'm guessing it's due to Kinetic being almost EOL combined with the server-centric nature of the package ?
Also, I'm a bit confused by the debian/changelog part of the debdiff, as it removes Jammy-related entries to add a Focal one. Would it be possible to generate one for each targetted release against the relevant versions currently in the archive to clarify things?
In addition, it's usually required to explicitly mark out all the fixed bugs in the changelog entry via a LP: #XXXXXXX stanza so that their status can be automatically updated as the package goes through the motions.