-
Notifications
You must be signed in to change notification settings - Fork 138
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Failure to remove legacy poetry version in 5.0.6-0 rpm #2782 #2783
Failure to remove legacy poetry version in 5.0.6-0 rpm #2782 #2783
Conversation
Add legacy poetry install path to avoid failing its uninstall. Without this additional path, when build.sh is run from within RPM's constrained %posttrans scriptlet, we fail to find and uninstall our prior 1.1.15 poetry version. This leads to having both poetry 1.1.15 (via upstream installer) and our new pipx installed poetry 1.7.1.
TestingUsing an rpm build for 15.4 with the proposed patch included, we now have a successful legacy poetry identification and removal on a system with only the legacy Poetry installed.
And a subsequent which confirms this:
But we still have a dangling reference, as if we call on the poetry binary:
We see a reference to the following now dead link:
It would seem the legacy upstream install/uninstall script has not completely removed what it had previously installed. We also have not affected the issue detailed failed venv creation. However if we re-run build.sh all is then well:
with a successfully established (from build.sh) password-store config also (pre initrock):
|
When removing the legacy installer 'dead link' via:
we still experience:
However if we reset path to it's exact same value at the time:
this 'artifact'/ghost/in-memory cached binary reference or what-ever goes away.
|
…ckstor#2782 - Remove dangling legacy poetry symlink - apparently neglected by legacy poetry installer/uninstaller. - After the above there is an in-memory 'poetry' resolution to `/root/.local/bin/poetry' until path is reset. So use reset as opportunity to remove legacy path.
…ockstor#2782 - Fix location of our temp legacy poetry path removal. - Add echo of PATH used by rest of build.sh.
Retest of branch to-date:
Our path modification looks to be malfunctioning when our to-be-removed path is at the front !!
But when it leads, as in our current case:
Substring fails us. So we also need the following to remove our just-added (front of path) temp legacy poetry path:
[EDIT] Looks like I missed the miss-match here: will re-visit and test:
|
…ockstor#2782 - remove not only substring instance of legacy Poetry path, but also our temp front-of-path entry.
Legacy path removed:
So our last stable to pending testing RC2 has successful legacy poetry removal now, but we have an unchanged outcome re new Poetry establishing our .venv:
and
|
…ockstor#2782 - remove deleted-in-%post RPM scriptlet .venv related path.
Final state pre-squash and re-presenting this draft PR. We now have a successful legacy poetry removal:
But have yet to establish why our new .venv is not successfully recreated from within RPM's invocation of build.sh:
However a re-run from the shell of build.sh:
Note that when run under a regular root shell we have the following PATH report:
Path env comparisons:
|
Add legacy poetry install path to avoid failing its uninstall. Without this additional path, when build.sh is run from within RPM's constrained %posttrans scriptlet, we fail to find and uninstall our prior 1.1.15 poetry version. This leads to having both poetry 1.1.15 (via upstream installer) and our new pipx installed poetry 1.7.1. After having checked-for/uninstalled this legacy version we then need to remove the associated legacy path.
Fixes #2782