A cvs checkout of the latest 6.2 version incorrectly reports itself as being 6.15, which does not exist. If you use cvs deploy it reports the wrong version number and update status continually screams that the module is unsupported and must be updated.

I looked through the commits and found that the .info file got committed to the 6.1 branch instead of the 6.2 branch, which is probably the problem.

Comments

jvandervort’s picture

jvandervort commented

Give it another try when you get a chance.
Are you using the branch head or the latest released tag?
This cvs repo had troubles with release tags being added to the wrong branch,
but I thought it was all worked out.

karens’s picture

karens commented

OK, the 6.x-2.10 version is broken, the 6.x-2.x-dev version works fine, but I don't want the dev version and update status still reports that 6.x-2.10 is the recommended version. You might want to create an official release that can be checked out correctly.

jvandervort’s picture

jvandervort commented
Status: Active » Fixed

6.x-2.11 just released. Once packaging runs we should be good again.

redndahead’s picture

redndahead commented

Thanks Jon for keeping up with this.

karens’s picture

karens commented

Much better! Thanks for the quick response!

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.