rjuju
commented
2 years ago @df7cb I'm wondering how to properly merge this. It's unlikely that we'll do a new debian 1.2.0-2 release, especially when the latest commits from last week could use a 1.2.1 version, so I don't know how to merge the suggested debian/changelog with a new one for a new release while keeping proper attribution for the changes in it?
Fix some issues reported by lintian
Set upstream metadata fields: Bug-Database, Bug-Submit, Repository, Repository-Browse. (upstream-metadata-file-is-missing, upstream-metadata-missing-bug-tracking, upstream-metadata-missing-repository)
Update standards version to 4.6.1, no changes needed. (out-of-date-standards-version)
This merge proposal was created automatically by the Janitor bot. For more information, including instructions on how to disable these merge proposals, see https://janitor.debian.net/lintian-fixes.
You can follow up to this merge proposal as you normally would.
The bot will automatically update the merge proposal to resolve merge conflicts or close the merge proposal when all changes are applied through other means (e.g. cherry-picks). Updates may take several hours to propagate.
Build and test logs for this branch can be found at https://janitor.debian.net/lintian-fixes/pkg/powa-collector/b1318bf7-6f0e-431f-9710-98756793be31.
These changes have no impact on the binary debdiff.
You can also view the diffoscope diff (unfiltered).