* the hardy patch uses 'dpatch' as the patch system, but your debdiff patches inline
* the distribution name is set to 'stable' for all debdiffs. This should be '<ubuntu release>-security' for each debdiff. Eg, for hardy, use 'hardy-security'
* the version is incorrect for each debdiff. Please see https://wiki.ubuntu.com/SecurityTeam/UpdatePreparation#Packaging for details
* you used the Debian packager's name in the changelog. You should use your own since Matthijs Kooijman did not prepare these debdiffs, you did
As per https://wiki.ubuntu.com/SecurityTeam/SponsorsQueue I am unsubscribing ubuntu-security-sponsors, marking the bug Incomplete and assigning to you. Please resubscribe ubuntu-security-sponsors and set the status to 'NEW' when the changes are complete, and detail the testing performed.
Remko, thank you for your patches for openttd. Unfortunately I cannot process them because they do not follow the procedures detailed in https:/ /wiki.ubuntu. com/SecurityTea m/UpdatePrepara tion#Packaging. Specifically:
* the hardy patch uses 'dpatch' as the patch system, but your debdiff patches inline /wiki.ubuntu. com/SecurityTea m/UpdatePrepara tion#Packaging for details
* the distribution name is set to 'stable' for all debdiffs. This should be '<ubuntu release>-security' for each debdiff. Eg, for hardy, use 'hardy-security'
* the version is incorrect for each debdiff. Please see https:/
* you used the Debian packager's name in the changelog. You should use your own since Matthijs Kooijman did not prepare these debdiffs, you did
As per https:/ /wiki.ubuntu. com/SecurityTea m/SponsorsQueue I am unsubscribing ubuntu- security- sponsors, marking the bug Incomplete and assigning to you. Please resubscribe ubuntu- security- sponsors and set the status to 'NEW' when the changes are complete, and detail the testing performed.
Thanks again for your work on this!