Oops, what happened here? Complete removal of mariadb-10.0 from unstable was of course not my intention. (And so far I cannot remember any of my (many many) RoQA RM requests causing such fallout.) Only some of the obsolete packages should go away, since automatic cruft removal sometimes has problems if both arch:all and arch:any packages are involved.
Hmm, my Subject translated into a valid dak command ... which was used instead of the one that I pasted from the cruft report. If I had used RM: mariadb-test [all] -- RoQA; obsolete arch:all package instead, nothing (unexpected) would have happened. (But I only realized right now that mariadb-test switched from all to any) > From an FTP team perspective that doesn't scale very well. And RMs are usually moreinfo-ed if they cause dependency problems. > Perhaps the best way is to have reportbug automatically CC the maintainer on an rm bug. Which sounds like a good idea. Sorry for the mess and extra work this causes. Andreas
