-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi there,
I feel this question must be fairly simple, but I couldn't find the answer anywhere I looked. I have a package in NEW (lorene, to be precise). It's an entirely new package. Since it is in the queue, I have been able to improve it. The improvements add evenmore binary packages to this source package, so the new version would need to go through NEW again in any case. What would be the workflow to push this new version? 1- simply compile and upload normally 2- same as above, but using the -v option of dpkg-genchanges to include the full changelog in the changes file 3- request the current package to be rejected, then reupload with the same version number 4- any other? Kind regards, Thibaut. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJX4Sp4AAoJEJOUU0jg3ChAoOkQALmtenvCtErbAD519DgeuQz0 c4XUbFdYxwSZw4EBXMzbAhdG8KmPbpLT3mrnu9xLRF4PGur+odOII5X+tB+FfEsB ATVIgHRqGt6EBEaU78c9Flam+jH3MYNfo9pk6lzqM/xJMhk5WK7AkVoVULh02z9u G5ZDUySPfdAcHgi4BiRqual2ucKq9w9XNWr7CuGz8gyRQ4qB1hqMwYqTRPbzLQ3a Sd40QdmxE1pA6Q6NsKw6eD9D7WEySHGigAFVY7LviE2yJOMTBosMEb4Xp0nrRIqi D5WO474Jmm2Zju9c/EfldDrjtXYWlQHLS8OmxB5/tNoPWpv3pAokgl6fEjkr2io0 KU8s8U5tctlSqpX+WccfCHqn+MfX9cmow89IiiYr1LAMgn103esorJ8xLNq3AtyX POiLKFPjCCIoRupjA1Cx5xz62S+wOc9jPDtya7CoNAzkCSwzuYOtlNCtDJG7Rhpt yW7zTGfDZjX3yTKw1wdk/Q/T09qePSunMI5dOMwWDADIQjfI/fMFOXb4KsB6V82+ AXS89pwdcemXa5c7E8zcYSQ0KgoKfgzlC/ui5GbnVpWm2j0xC3UJj13zIoZ0l5jq dZuJqG4Z2gw76QSQkxJ8pHeCDjvhBBDJU0+JJcIfRC2dBQqCtrgPeU/UQ7pIl7IH xjArJeh328ZtU9sYDWSg =2pAT -----END PGP SIGNATURE-----
