On Wed, Apr 20, 2016 at 10:12:45PM +0200, Tobias Frost wrote: > (If you go for experimental, please reopen the RM bug for the binaries > in sid once it enters the archives)
In the case this goes to experimental the right kind of thing to do is
to completely remove it from unstable (sources included). This might
seems harsh, but it's really not :)
But I'm not sure what would be the problem of having it on experimental:
if the only problem this thing has is that it misrenders images on some
cards, then I'd say to upload this version to unstable, and block it
there with another RC bug on it, and treat it as a separate bug. I know
voluntarily introducing a bug is bad, but I'd weight it against *this*
bug, and keeping in mind we're talking about debian *unstable*.
Maintainers, what do you think?
Can you prepare an upload, maybe based on Gianfranco's work? Or either
say that what he did is "Great And Blessed" and confirm that you're cool
with us uploading it? :)
And tell us what you prefers between uploading the new in experimental
and removing the current one from unstable or uploading this directly to
unstable.
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`.
more about me: https://mapreri.org : :' :
Launchpad user: https://launchpad.net/~mapreri `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia `-
signature.asc
Description: PGP signature
