Skip to content
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

Fedora/Linux installer deleting all symlinks while package update #14086

Closed
53c70r opened this issue Sep 3, 2020 · 8 comments
Closed

Fedora/Linux installer deleting all symlinks while package update #14086

53c70r opened this issue Sep 3, 2020 · 8 comments
Labels
bug Stale Marks an issue as stale, to be closed if no action is taken

Comments

@53c70r
Copy link

53c70r commented Sep 3, 2020

Using the Linux installer from https://docs.rapid7.com/metasploit/installing-the-metasploit-framework/ i noticed after updating the package all symlinks are gone leaving all binaries in place without any references to the environment.
Symlinks are placed correctly only after installation.

Fedora 32

@53c70r 53c70r added the bug label Sep 3, 2020
@VainlyStrain
Copy link

+1
had this for quite some time now (since first installation on Fedora 29). I solved it by uninstalling, then installing again (NOT reinstall):

msfvpdate.sh

sudo dnf remove metasploit-framework
sudo dnf install metasploit-framework

@53c70r
Copy link
Author

53c70r commented Sep 3, 2020

This should be fixed within the .spec file while rpm building.

@53c70r
Copy link
Author

53c70r commented Sep 10, 2020

Setting reference to
rapid7/metasploit-omnibus#133

@github-actions
Copy link

Hi!

This issue has been left open with no activity for a while now.

We get a lot of issues, so we currently close issues after 60 days of inactivity. It’s been at least 30 days since the last update here.
If we missed this issue or if you want to keep it open, please reply here. You can also add the label "not stale" to keep this issue open!

As a friendly reminder: the best way to see this issue, or any other, fixed is to open a Pull Request.

@github-actions github-actions bot added the Stale Marks an issue as stale, to be closed if no action is taken label Oct 10, 2020
@53c70r
Copy link
Author

53c70r commented Oct 14, 2020

Bump.

@github-actions github-actions bot removed the Stale Marks an issue as stale, to be closed if no action is taken label Oct 14, 2020
@VainlyStrain
Copy link

I have looked into it. There is a script here (responsible for the shortcuts) that is executed correctly every time the package is freshly installed. However, it is not triggered when there is a package update.

In the Fedora documentation, it says that the scriplets are called with a different argument when upgrading than when installing. Maybe this is the issue here? As I am unfamiliar with packaging, I can't fix the issue myself and submit a pull request, sorry :/

But hopefully this reply was able to help a person able to fix it.

@github-actions
Copy link

Hi!

This issue has been left open with no activity for a while now.

We get a lot of issues, so we currently close issues after 60 days of inactivity. It’s been at least 30 days since the last update here.
If we missed this issue or if you want to keep it open, please reply here. You can also add the label "not stale" to keep this issue open!

As a friendly reminder: the best way to see this issue, or any other, fixed is to open a Pull Request.

@github-actions github-actions bot added the Stale Marks an issue as stale, to be closed if no action is taken label Nov 30, 2020
@dwelch-r7
Copy link
Contributor

We're going to just keep track of this issue in the omnibus repo here: rapid7/metasploit-omnibus#133

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Stale Marks an issue as stale, to be closed if no action is taken
Projects
None yet
Development

No branches or pull requests

3 participants