-
Notifications
You must be signed in to change notification settings - Fork 235
Not sure this is supposed to be here #1535
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
Conversation
Reviewer's GuideThis PR removes the forced symlink of podman-remote to podman from the build_llama_and_whisper.sh script to prevent overwriting the host's podman binary. Flow diagram for podman symlink removal in build_llama_and_whisper.shflowchart TD
A[Start install_ramalama] --> B{Was podman symlink created?}
B -- Before PR --> C[ln -sf /usr/bin/podman-remote /usr/bin/podman]
C --> D[Continue install_ramalama]
B -- After PR --> D
D[Continue install_ramalama] --> E[Check /run/ramalama]
E --> F[Install ramalama if present]
E --> G[End if not present]
File-Level Changes
Tips and commandsInteracting with Sourcery
Customizing Your ExperienceAccess your dashboard to:
Getting Help
|
Think it's only meant for the: container-images/scripts/build-cli.sh version, it's breaking podman on my bootc system and replacing /usr/bin/podman with a broken /usr/bin/podman-remote symlink. Signed-off-by: Eric Curtin <[email protected]>
97ce34b
to
ce11e66
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Summary of Changes
Hello @ericcurtin, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!
This pull request aims to fix a specific issue encountered on bootc systems where a build script was incorrectly creating a symlink for the podman
command, leading to a broken setup. The change removes this problematic symlink creation from the script where it was deemed unnecessary.
Highlights
- Symlink Removal: Removed the explicit creation of a symlink from
/usr/bin/podman
to/usr/bin/podman-remote
within theinstall_ramalama
function in thebuild_llama_and_whisper.sh
script. - Fix for Bootc Systems: This change addresses an issue reported by the author where this symlink creation was causing the
podman
command to break on bootc systems by replacing the expected binary with a potentially non-functional symlink.
Using Gemini Code Assist
The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.
Invoking Gemini
You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command>
or @gemini-code-assist <command>
. Below is a summary of the supported commands.
Feature | Command | Description |
---|---|---|
Code Review | /gemini review |
Performs a code review for the current pull request in its current state. |
Pull Request Summary | /gemini summary |
Provides a summary of the current pull request in its current state. |
Comment | @gemini-code-assist | Responds in comments when explicitly tagged, both in issue comments and review comments. |
Help | /gemini help |
Displays a list of available commands. |
Customization
To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/
folder in the base of the repository. Detailed instructions can be found here.
Limitations & Feedback
Gemini Code Assist is currently in preview and may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments to provide feedback.
You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.
Footnotes
-
Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configureGemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hey @ericcurtin - I've reviewed your changes and they look great!
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code Review
This pull request correctly removes a symlink creation (ln -sf /usr/bin/podman-remote /usr/bin/podman
) from the build_llama_and_whisper.sh
script. This symlink was causing issues by breaking the host's podman executable when the script was run in certain environments. The removal addresses this bug, as the symlink is likely only intended for specific container images built by other scripts.
This is needed in the ramalama-cli install at least. |
@@ -278,8 +278,7 @@ clone_and_build_llama_cpp() { | |||
} | |||
|
|||
install_ramalama() { | |||
# link podman-remote to podman for use by RamaLama | |||
ln -sf /usr/bin/podman-remote /usr/bin/podman |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You could just move this below the if /run/ramalama line below, or we should move it to the containerfile that installs podman-remote.
Actually after further search this is correct. |
Think it's only meant for the:
container-images/scripts/build-cli.sh
version, it's breaking podman on my bootc system and replacing /usr/bin/podman with a broken /usr/bin/podman-remote symlink.
Summary by Sourcery
Bug Fixes: