upgrade through setup.py doesn't overwrite existing bzrlib
Bug #102751 reported by
Martin Pool
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Bazaar |
Confirmed
|
Medium
|
Unassigned | ||
Bug Description
I had bzr 0.15rc3 installed in my home directory, and just tried 'python setup.py install --home ~' from bzr.dev to upgrade it. This installed the new bzr script, but didn't upgrade the library; therefore warnings about them being out of sync and no new features.
Maybe this is something to do with the egg-info files that setup.py now seems to install?
I think if the version number is the same, it will install the upgrades, but if the version number is different (even if it's higher), it won't overwrite the old files.
Revision history for this message
| Alexander Belchenko (bialix) wrote | #1 |
| Changed in bzr: | |
| importance: | Undecided → Medium |
| status: | Unconfirmed → Confirmed |
| tags: | added: setup.py |
| tags: | added: check-for-breezy |
| tags: | removed: check-for-breezy |
To post a comment you must log in.
I'm think we also can write support for 'uninstall' target of setup.py.