http://forums.gentoo.org/viewtopic.php?p=7505130#7505130 and IRC channel (freenode) isn't available - therefore this report
An overview of the repoman output is available at: http://packages.gentooexperimental.org/repoman-current-issues.txt
Sorry a lot. Was an accident due me running the wrong script (the one for committing) instead of the one only running "repoman full" to prepare the Gnome 3.10 stabilization list with all the dependencies. I am reverting it just now after discussion in #gentoo-infra (thanks a lot to all the people that helped me) Sorry again :(
*** Bug 502170 has been marked as a duplicate of this bug. ***
Using the following bit of code: directory=~/.maildir/.INBOX.Mailing\ Lists.Commits/ for f in $(grep -rl '^[ ]*arch stable, bug 888' $directory) ; do grep Subject ${f} | sed 's/.*commit in //' | sed 's/ ChangeLog//' done | sort | uniq > ~/GNOME.fixed We can get a list of packages and ebuilds that were affected: http://dev.gentoo.org/~tomwij/files/tmp/GNOME.affected If we replace the commit message by the one that fixes it: Fix wrong commit, bug 502160 We can also generate a list of those that are fixed: http://dev.gentoo.org/~tomwij/files/tmp/GNOME.fixed In the end, when we're done; we can verify our work this way: http://dev.gentoo.org/~tomwij/files/tmp/GNOME.diff I'll run this every once in a while; if you want me to run it, let me know. I expect to run this when the revert is done so we can at least verify on the ChangeLog level that everything is addressed; if someone is interested, we can later try to verify this on a diff based level.
I think all is ok now
For me, glibmm is still trying to upgrade to 2.38.1 from 2.36.2 and that is trying to pull in the unstable glib. I am assuming it is just a question of waiting for the changes to propagate to the rest of the mirrors.
(In reply to Jack from comment #6) > For me, glibmm is still trying to upgrade to 2.38.1 from 2.36.2 and that is > trying to pull in the unstable glib. I am assuming it is just a question of > waiting for the changes to propagate to the rest of the mirrors. Indeed, that package is still affected: http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/dev-cpp/glibmm/ A quick look at the updated diff reveals that these are still affected: app-editors/latexila: latexila-2.10.1.ebuild dev-cpp/glibmm: glibmm-2.38.1.ebuild Looking at the other one mentioned, it indeed is still affected: http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/app-editors/latexila/
What's with the packages that are in the "fixed" list but not in the "affected" list?
(In reply to Ari Entlich from comment #8) > What's with the packages that are in the "fixed" list but not in the > "affected" list? Some are just split up versions of the "affected" list; there also appear to be a few false positives where no actual change has been made to the file, I hope.
*** Bug 502188 has been marked as a duplicate of this bug. ***
+ 23 Feb 2014; Pacho Ramos <pacho@gentoo.org> glibmm-2.38.1.ebuild: + Revert wrong commit Pacho has requested me to do the other commit: + 23 Feb 2014; Tom Wijsman <TomWij@gentoo.org> latexila-2.10.1.ebuild: + Fix wrong commit, bug 502160 Done.
