migration files not installed
Bug #1394722 reported by
Robert Kukura
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Group Based Policy |
Invalid
|
Critical
|
Robert Kukura | ||
Bug Description
When "python setup.py install" is run, files needed to run gbp-db-manage don't get installed. These include at least alembic.ini and the python modules in the versions directory.
| Changed in group-based-policy: | |
| assignee: | nobody → Robert Kukura (rkukura) |
| Changed in group-based-policy: | |
| importance: | Undecided → Critical |
| status: | New → Confirmed |
| milestone: | none → juno-gbp-3 |
Revision history for this message
| Robert Kukura (rkukura) wrote | #1 |
| Changed in group-based-policy: | |
| status: | Confirmed → Invalid |
Revision history for this message
| Robert Kukura (rkukura) wrote | #2 |
To post a comment you must log in.
The correct files do get installed and added to the egg-info/SOURCE.txt file when "python setup.py install" or "python setup.py sdist" is run inside a get repo. I've changed the Fedora packaging to use tarballs generated from a git repo, similar to the way official release tarballs are created, which will be used when available.