2017-01-13 0:42 GMT+02:00 Andreas Beckmann :
> Looks good. Cloning/reassigning/retitling the bug accordingly, to keep
> an RC bug against mariadb-10.0 open.
Ok, so we need to have one RC against 10.0 open all the time to
prevent it from migrating from unstable to testing until it has been
cleaned
Processing control commands:
> clone -1 -2
Bug #850147 [src:mariadb-10.0] mariadb-10.0: stretch should be released with
mariadb-10.1 only
Bug 850147 cloned as bug 851208
> reassign -1 src:mysql-defaults 1.0.1
Bug #850147 [src:mariadb-10.0] mariadb-10.0: stretch should be released with
mariadb-10
Control: clone -1 -2
Control: reassign -1 src:mysql-defaults 1.0.1
Control: retitle -1 mysql-defaults: switch to mariadb-10.1
On 2017-01-12 23:31, Otto Kekäläinen wrote:
> Fix committed in
> https://anonscm.debian.org/cgit/pkg-mysql/mysql.git/commit/?id=9ead71eaee19f5c701f7e6c7a9919b2c7de6418b
Lo
Fix committed in
https://anonscm.debian.org/cgit/pkg-mysql/mysql.git/commit/?id=9ead71eaee19f5c701f7e6c7a9919b2c7de6418b
Source: mariadb-10.0
Version: 10.0.28-2
Severity: serious
Hi,
the remaining bits needed for the transition from mariadb-10.0 to
mariadb-10.1 are updates to the dependencies in mysql-defaults
(and this RC bug to get 10.0 removed at some point).
Andreas
5 matches
Mail list logo