Control: unmerge 842442 Control: block 648621 by 842442 Control: affects 842442 + src:libindicator src:libunique src:vino src:goocanvas src:libunique3 src:libgnomecanvas src:gnome-keyring src:cinnamon-session src:gtksourceview2 src:clutter-imcontext src:tumbler Control: tags 648621 + help
Hi Michel, On Wed, Mar 01, 2017 at 11:34:59PM +0100, Michael Biebl wrote: > Afaics, this is a duplicate of #648621, so merging accordingly. I saw that other bug when filing this one, but figured the other bug/patch was stuck, because it has a number of unaddressed concerns nobody is working on. Merging these bugs effectively says "do the whole thing or nothing happens". The reasons for keeping them separate are: * The major goal of 648621 is to make libglib2.0-dev Multi-Arch: same. * The only goal of 842442 is to make glib-genmarshal executable during cross builds. * 842442 covers a small subset of 648621. * None of the concerns mentioned for 648621 apply to 842442. * In the patch of 842442, I was very careful to only do "safe" things, i.e. move only things that are known to be architecture-independent. At a later time, we can try moving more of libglib2.0-dev to libglib2.0-dev-bin to make it Multi-Arch: same, but 842442 already makes some things (listed under affects) work. * Thus 842442 is applicable right now, while 648621 needs someone working out the remaining issues[1]. Adding the help tag. I thus ask you to keep these issues separate to make any kind of progress possible. 648621 simply is too big to move on. Once this bug is fixed, we will get a better understanding of the remaining issues (because the qa tooling will no longer be stuck at 842442) and the diff for 648621 will become thinner and thus easier to fix and review. I am sorry for not having made the relation between these bugs more clear in my original submission. The perfect is the enemy of the good. Helmut [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=648621#20 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=648621#38