FS#38656 - [ruby-atk] Wrong package version?

Attached to Project: Community Packages
Opened by Methos (Methos) - Saturday, 25 January 2014, 10:36 GMT
Last edited by Alexander F. Rødseth (xyproto) - Tuesday, 28 January 2014, 14:30 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Alexander F. Rødseth (xyproto)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 2
Private No

Details

While trying to update I got the error that my locale ruby-atk (ruby-gdkpxbuf2, ruby-glb2,ruby-gtk2, ruby-pango also) is newer than that in the community repo.
I think that with the last update the version naming went wrong. I think it shouldn't be ruby-atk 2.0.0-3 but 2.0.3-1.
The questionable commit was https://projects.archlinux.org/svntogit/community.git/commit/trunk?h=packages/ruby-gtk2&id=8a550c2de5b36e2ea6acca5f49da95dfded7cb80
This task depends upon

Closed by  Alexander F. Rødseth (xyproto)
Tuesday, 28 January 2014, 14:30 GMT
Reason for closing:  Fixed
Comment by Gregory Gleason (gsgleason) - Saturday, 25 January 2014, 16:26 GMT
I also had this happen starting last night.

:: Starting full system upgrade...
warning: ruby-atk: local (2.0.2-1) is newer than community (2.0.0-3)
warning: ruby-gdkpixbuf2: local (2.0.2-1) is newer than community (2.0.0-3)
warning: ruby-glib2: local (2.0.2-1) is newer than community (2.0.0-3)
warning: ruby-gtk2: local (2.0.2-1) is newer than community (2.0.0-3)
warning: ruby-pango: local (2.0.2-1) is newer than community (2.0.0-3)

Comment by Nicolai Pudimat (InspectorMustache) - Sunday, 26 January 2014, 22:39 GMT
Same here.
Comment by Alexander F. Rødseth (xyproto) - Monday, 27 January 2014, 18:35 GMT
My bad.

There is a new version waiting in [community-testing]. Once it is moved (not by me), this problem is resolved.

In the mean time, I will consider looking into removing the warnings as well.
Comment by Thomas Dziedzic (tomd123) - Tuesday, 28 January 2014, 04:05 GMT
I moved the ruby rebuild to stable repos, this issue should be fixed.
I will let maintainer close this bug.
Comment by Alexander F. Rødseth (xyproto) - Tuesday, 28 January 2014, 14:30 GMT
Thanks for moving, Thomas Dziedzic.

Loading...