The /usr/bin/pulp-migrate command uses #!/usr/bin/python to find the scripting environment. This is bad for running Pulp in environments other than the system installed Python (such as virtualenv, or if the user wants to run in a different version of Python.) It should use env instead, which will find which Python interpreter to use by inspecting the environment.
I completed the work on this ticket in this commit: https://github.com/pulp/pulp/commit/421a95ca2efb57be1d63593f668933055296abaf jdob reviewed this work as part of my story about migrations, which is why I am skipping this ticket status ahead to MODIFIED.
build: 0.334
verified [root@pulp-master ~]# rpm -q pulp-rpm-server pulp-rpm-server-0.0.335-1.fc17.noarch [ [root@pulp-master ~]# [root@pulp-master ~]# pulp-manage-db Beginning database migrations. Migration package pulp.server.db.migrations.platform is up to date at version 0 Database migrations complete. Loading content types. Content types loaded. [root@pulp-master ~]#
Pulp v2.0 released