-
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
Milestone
Comments
The essensence here is:
and:
This is suspected as only affect "Build on ..." 15.4 base OS installs. |
Noteworthy here is our existing explicit addition of the required path during/in our existing %build scriptlet: |
phillxnet
added a commit
to phillxnet/rockstor-core
that referenced
this issue
Jan 22, 2024
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.
phillxnet
added a commit
to phillxnet/rockstor-core
that referenced
this issue
Jan 22, 2024
…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.
phillxnet
added a commit
to phillxnet/rockstor-core
that referenced
this issue
Jan 22, 2024
…ockstor#2782 - Fix location of our temp legacy poetry path removal. - Add echo of PATH used by rest of build.sh.
phillxnet
added a commit
to phillxnet/rockstor-core
that referenced
this issue
Jan 23, 2024
…ockstor#2782 - remove not only substring instance of legacy Poetry path, but also our temp front-of-path entry.
phillxnet
added a commit
to phillxnet/rockstor-core
that referenced
this issue
Jan 23, 2024
…ockstor#2782 - remove deleted-in-%post RPM scriptlet .venv related path.
phillxnet
added a commit
to phillxnet/rockstor-core
that referenced
this issue
Jan 23, 2024
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. ## Includes: - 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. - Add echo of PATH used by remainder of build.sh. - Remove .venv related path from PATH as the entire directory is deleted in the %post RPM scriptlet. And build.sh (outside of development) is run after this: from %posttrans.
phillxnet
added a commit
that referenced
this issue
Jan 23, 2024
…-poetry-version-in-5.0.6-0-rpm Failure to remove legacy poetry version in 5.0.6-0 rpm #2782
Closing as: |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Thanks to @FroggyFlox for highlighting this issue. During rpm update, we execute our build.sh script from within rpmbuild's %posttrans scriptlet. As from rpm 5.0.6-0 the build.sh shell script also:
This new Poetry update mechanism was part of the following pull request:
Update Poetry build system & normalise on Python 3.11 #2703 #2754 #2693 by @phillxnet @FroggyFlox in #2755
However; during more recent update testing concerning our next Stable release (from our last), given we are now in Release Candidate phase in testin updates/branch, a 4.6.1-0 machine failed to update to a pre-release rpm version of 5.0.6-2781.
The
/var/log/zypp/history
rpm log had the following contents.Where-as post this Leap 15.4 reproducer system (
zypper dup
'ed from 15.3) we have the following contents:So we see the failure of the legacy Poerty to:
and we also have the newer version inappropriately co-resident, as per pipx's feedback within the above log excerpt, and from:
It is proposed that in this setting we have an insufficient path to identify the existence of the legacy Poetry version and thus skip entirely running its uninstaller.
The text was updated successfully, but these errors were encountered: