[debian-mysql] Bug#886756: Bug#886756: Regression: Specified key was too long; max key length is 767 bytes

Robie Basak robie.basak at ubuntu.com
Tue Aug 7 20:37:37 BST 2018

On Tue, Aug 07, 2018 at 10:02:14PM +0300, Otto Kekäläinen wrote:
> Right now I don't have a good workfow on how to mark certain bugs as
> qualified for stable release update. There is a risk I forget about
> this after it is fixed in sid. Suggestions on workflow tips welcome
> from fellow Debian maintainers.

I'm not sure how to use Debian BTS for this type of thing.

You could use git-notes to flag particular commits for cherry-pick, or
maintain a scratch (not QA'd) branch just with cherry-picks that you can
throw away when you're ready to do a proper branch for stretch.

Or if you're planning to also cherry-pick for Ubuntu stable releases,
you can use Launchpad, link the Debian bug, and use Ubuntu stable bug
tasks for the tracking. This won't track when you have landed something
into stretch though.


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/pkg-mysql-maint/attachments/20180807/82e66194/attachment.sig>

More information about the pkg-mysql-maint mailing list