Hey Bill,

The only time I've seen this is when switching from (for example) tip of the 'dev' brach of Galaxy over to 16.01, 15.10, or some other stable release.

Basically, sqlalchemy_migrate sees the 0130_change_pref_datatype.pyc (or some other one) and thinks a version should exist.

The easiest fix for this is something like: `find . -name "*.pyc" -delete`, executed from your galaxy root directory.

-Dannon

On Thu, Feb 25, 2016 at 3:50 PM, William Ge <wge@centrilliontech.com> wrote:

Hi, all,

I am new to Galaxy. The following error was encountered when I tried to run Galaxy after getting PostgreSQL up:

File "/home/galaxy/galaxy/eggs/sqlalchemy_migrate-0.9.6-py2.6.egg/migrate/versioning/version.py", line 204, in script

"There is no script for %d version" % self.version

AssertionError: There is no script for 130 version

I searched the lists and forums, but have not found any message. Anyone can give some hits?

I’m running this on CentOS 6.7, virtual environment, python2.6, PostgresQL 8.4.20.

Thanks in advance!

Bill

___________________________________________________________
Please keep all replies on the list by using "reply all"
in your mail client. To manage your subscriptions to this
and other Galaxy lists, please use the interface at:
https://lists.galaxyproject.org/

To search Galaxy mailing lists use the unified search at:
http://galaxyproject.org/search/mailinglists/