fix: xrpld symlink renamed incorrectly#6012
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## develop #6012 +/- ##
=======================================
Coverage 78.3% 78.3%
=======================================
Files 816 816
Lines 68887 68887
Branches 8304 8303 -1
=======================================
+ Hits 53943 53945 +2
+ Misses 14944 14942 -2 🚀 New features to boost your workflow:
|
|
Thanks - I'll push a commit to the renaming script as well soon. |
|
I updated the Note that after running We will rip off the bandaid soon, see #5983 (which still needs more work), but I do not plan to merge that until after 3.0.0 to avoid us having to update the deployment scripts in a rush. |
|
@legleux I also looked at the statement you said had no effect, even though on my machine it was complaining. I tried again and now it's compiling fine, so I also removed it from the script. |
High Level Overview of Change
#5975 Changed the target of the
xrpldsymlink toxrpldand now points to itself.We renamed the
rippledtarget toxrpldbut set the output binary to still berippledso this symlink should not have been updated.To be clear, this PR recreates the previous configuration:
bin ├── rippled └── xrpld -> rippledor we can just rip the band-aid off now and have
rippledbe a symlink toxrpld.Type of Change