Hello all, I have just now rebased gnome-team, just so that we keep up to date with master (three merge conflicts related to rust!).
But this does not solve the fundamental problem - I am convinced there is a problematic commit hidden somewhere inside the branch. The only way of debugging this is by "git bisect" - then pushing the checked out "middle" commit and letting data.qa try to evaluate the branch. For 200 commits, this should take 7 trials. Is some committer from the Gnome team interested in giving it a try? Or do you spot suspicious commits? I am a bit wary about the package moves to gnome-circle with the left-behind public alias, although it should be safe with "(@". Andreas
