That is a very good catch.
I did gtk-sharp3-2.99.3-11.el7 because in dist-git, the last build was gtk-sharp3-2.99.3-10.el7.
I don't know how elsupergomez got gtk-sharp3-2.99.3-16.el7 built without it being in dist-git.
I'll get it fixed so we are not going backwards in release.
This update has been submitted for testing by tdawson.
This update has been pushed to testing.
epel7 already has gtk-sharp-2.99.3-16.el7 - why going backwards in release won't work.
Bodhi is disabling automatic push to stable due to negative karma. The maintainer may push manually if they determine that the issue is not severe.
I ment to say - going backwards in release won't work.
That is a very good catch. I did gtk-sharp3-2.99.3-11.el7 because in dist-git, the last build was gtk-sharp3-2.99.3-10.el7. I don't know how elsupergomez got gtk-sharp3-2.99.3-16.el7 built without it being in dist-git. I'll get it fixed so we are not going backwards in release.
This update has been obsoleted by gtk-sharp3-2.99.3-17.el7.