Can't apply all migrations when starting in docker about pypi-server

[ruohola]

There is a simple way to circumvent this problem. It's not a propre fix, but it makes this package usable: launch the program a first time, and let it crash. Afterwards, manually add an entry into the "migrations" table to prevent the faulty migration from being applied:

INSERT INTO migrations (id, name, ts) VALUES (8, 'packagefile_basename_unique.add_uniquie_basename_index', 'TIMESTAMP');

Replace TIMESTAMP with a valid timestamp (you can simply copy/paste one of the timestamps you get with the request SELECT ts from migrations)

You could just use CURRENT_TIMESTAMP when inserting.

[HarryMWinters]

Same. Bummer though. This would have fulfilled 120% of my use case.

[la-sanchez]

Same here.

[MoLt1eS]

Having the same issue

[jaredhanson11]

+1, I ran into the same issue. I switched to https://github.com/pypiserver/pypiserver. Doesn't have a nice gui and user nice management, but it does the job effectively enough.

[ruohola]

Still happening.

[vlastocom]

Just verified when researching #54 , this is still the case for the postgres configuration.

[ruohola]

Unfortunately this issue made the whole package unusable, so I just used https://github.com/pypiserver/pypiserver.

[fr-Pursuit]

There is a simple way to circumvent this problem. It's not a propre fix, but it makes this package usable: launch the program a first time, and let it crash. Afterwards, manually add an entry into the "migrations" table to prevent the faulty migration from being applied:

INSERT INTO migrations (id, name, ts) VALUES (8, 'packagefile_basename_unique.add_uniquie_basename_index', CURRENT_TIMESTAMP);

Edit: Thanks to @ruohola for his suggestion about the usage of CURRENT_TIMESTAMP !