Hi Andreas, Some quick answers (without looking at detail):
On Fri, Jul 17, 2015 at 01:10:35PM +0200, Andreas Beckmann wrote: > I pushed another one to deregister the my.cnf.fallback alternative on > removal, otherwise purge gets noisy about the dangling link. Having looked at your previous patches I feel that you have a better grasp on this fix than I do and agree with the principle of your proposed fix, so I'm happy to take your direction on this - both on the patches and on coordination with mariadb. Please feel free to upload from VCS as needed to fix this issue. > In my tests with piuparts the upgrade paths now looks fine. Only people > that track sid and use mariadb, i.e. that had upgraded to mysql-common > 5.6.25-2, may end up with an unneccessary my.cnf.migrated (could be the > pristine my.cnf from before the switch). It would be quite easy to > detect this as well, we would just need a (list of) md5sums of the old > pristine my.cnf to compare against. We can do this later too, right? > Will we have to adjust the versioning of the Breaks/Depends somehow to > also cover Ubuntu properly? mariadb in Ubuntu has never created the symlink. As it had the mysql-common update-alternatives symlink code first, it didn't need it. It was my error in understanding that this was blocking Otto in Debian since mysql-common wasn't updated in Debian (jessie was in freeze at the time we did it, and I neglected it after jessie was released). I'll take a look before I update Ubuntu. I might just need to make sure that the symlink is never deleted, or verify that the code won't ever do that. > And now we are moving slightly offtopic in this bug: I'll take this off the bug and reply on the list. Robie
signature.asc
Description: Digital signature