On the project's site, rambox.pro, the link to download the Rambox for Linux DEB, i.e [https://getrambox.herokuapp.com/download/linux_64?filetype=deb], leads instead to downloading a tar.gz file that most Ubuntu users would not know what to do with.
The browser prompts the user to save a .deb file
The browser prompts the user to save a .tar.gz file
The project's website.
Duplicate of #1164 #1148 #1096 #169 #1304 #1456 #1538
But this is the best issue report from all of them.
Found the same issue, deb link resolves to tar.gz
It's been two months since the issue was reported.
Since the homepage is what users usually visit when they want to try a (new) software and since this should be as easy as fixing a typo in a link, that fact kind of gives the impression that the project has been abandoned or at least is in no healthy state developer-activity-wise.
@DaDummy Maybe it needs more manpower
Same for version 0.5.17 now
Why does nobody fix this?
Because it's code is hosted somewhere else then this repo, so it could be fixed only by @saenzramiro and its priority is pretty low.
One way to get around this issue is to go directly to https://github.com/saenzramiro/rambox/releases/latest and download the latest deb from here.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Website has changed and links to deb packages have been removed. This is one way to resolve the issue. On the front page, Linux users can now download appimage (60 MiB) or snap (110 MiB) packages but the deb package (40 MiB) is still on the GitHub page.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
This issue has been automatically closed since there has not been any recent activity. Please open a new issue for related bugs.
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.