-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Downgread librealsense version from v2.47.0 to v2.45.0 #1925
Comments
Hi @ranjitkathiriya That is an unusual error. Typically, if the librealsense version has been upgraded without the RealSense ROS wrapper being rebuilt afterwards then I would expect the log to say "Built with 2.45.0, running with 2.47.0". If librealsense 2.47.0 was installed with Debian packages then you could initiate a purge to uninstall all librealsense related packages. |
I am installing it from this link https://github.com/IntelRealSense/librealsense/blob/master/doc/distribution_linux.md, how can I install the 2.45.0 version only. I tried installing from this link every time it is installing the new version. I also tried these steps for installing v2.45.0 If you were using the Debian packages then follow the installation guide to remove the current version, then re-install Librealsense SDK using an explicit version/build:
While installing the utils package I am getting this error
|
Assuming that you are starting at the beginning of the package installation instructions after having purged the previos packages: If you have registered the server key and added the server to the list of repositories, have you then installed the librealsense2-dkms package? |
Yes, I have followed the steps from the beginning.
Yes, I have installed it but It is taking the latest version 2.47.0.
|
As a new RealSense ROS wrapper version tends to be released quite soon after a new librealsense version, maybe you could wait for a wrapper that is compatible with 2.47.0 to be released by Doronhi the RealSense ROS wrapper developer and then build that wrapper on top of 2.47.0. |
Hi, I am not aware of any relevant API changes in the new librealsense2 2.47.0 version so rebuilding realsense2_camera after installing librealsense2 version 2.47.0 should work fine
) If you wish to revert back to librealsense2 v2.45.0, a solution to the issue you are having is manually installing the dependencies to the correct version. That is:
And maybe some more dependencies, if you more error message starting with |
I tried to revert back but I am getting these errors.
|
Replace 4552 with 4551. |
Same Error and 551 is for melodic afaik,
Anyways, I will wait for 1 week |
Thanks very much for the update @ranjitkathiriya - if you are going to wait for a week then I will keep this case open for a further time period. Good luck! |
@MartyG-RealSense thank you for your support. Have you considered a more permanent solution to this issue? This is a recurring problem when the versions change and these 1-week breaks are a drawback for system stability. We would like to avoid building from source since there is a deb package or having to create an apt caching server just to solve this so please consider it seriously. Can you time better the releases or you find a way to keep the previous versions? |
Hi @garcia-g A suitable solution for you may be to build using the ROS wrapper's Method 1 if possible, so that a matching librealsense and ROS wrapper version are installed from packages together at the same time instead of installing librealsense and the ROs wrapper separately. https://github.com/IntelRealSense/realsense-ros#method-1-the-ros-distribution Whilst using Method 1 means that you would likely not be installing the very latest librealsense version, it should ensure that your SDK and wrapper versions always have their ideal match. |
Hello @garcia-g, I am building for source because I am using a real sense-viewer to visualize depth and based on that I am implementing it to an algorithm. If you are not using real sense viewer as I do. Then I would suggest directly follow method one as suggested by @MartyG-RealSense. Advantages you will get if you are not building from the source. Ref: Link
|
Thank you @MartyG-RealSense and @ranjitkathiriya for your kind advice. I will try the ROS distribution (Method 1) but that doesn't solve my problem entirely. The issue remains as I will have no control on the updates since the ROS distribution also removes the packages once the latest version is released, which, if unlucky, will render my system unusable. Since we use docker and CI, we can survive but it's not the ideal situation. In docker, we use pinned versions of the packages for stability, so not having the previous versions will cause the CI to fail. I'm wondering if someone else uses docker with pinned versions and how they solve these issues 🤔 About building the code, @ranjitkathiriya you're right: it's too much waste for something that should be solved more easily. |
You are very welcome @garcia-g I can recall a past case in which someone needed control over when and how updates occurred. It was suggested that a custom fork of the official RealSense GitHub was created on the person's own GitHub account. |
Sorry to update that due to some delays and since librealsense2 v2.48.0 is expected very soon it is possible that the next realsense2_camera version will be delayed by a couple of days and maybe skip librealsense2 v2.47.0. |
Thanks very much @doronhi for the information about the release schedule. |
@MartyG-RealSense Thank you for the tip, I'll consider that option too. |
Hi @ranjitkathiriya Do you require further assistance with this case, please? Thanks! |
No! thanks. |
Thanks very much @ranjitkathiriya for the update! |
Actually, I thought to keep this case open, but now it's okay! |
Hello there,
My PC has auto-upgraded to v2.47.0 librealsense version and I am getting an error when I am executing realsense camera.
Error:
The text was updated successfully, but these errors were encountered: