Closed zoomequipd closed 3 years ago
ya i see many people getting this problem with jemalloc, the easier is just add options to apt to overwrite the file and forget, i will add that to both scripts today or tomorrow, thanks
ok pushed, i have added this to both scripts
#!/bin/bash
if [ $(dpkg -l "jemalloc*" | grep -q "ii jemalloc") ]; then
aptitude install -f checkinstall curl build-essential jq autoconf libjemalloc-dev -y
else
echo "installed"
fi
./test.sh
installed
i have removed else condition in script
ok that isn't perfect hm
ok this oen works better
#!/bin/bash
if ! $(dpkg -l "libjemalloc*" | grep -q "ii libjemalloc"); then
aptitude install -f checkinstall curl build-essential jq autoconf libjemalloc-dev -y
else
echo "installed"
fi
If you want to maintain the separation of kvm-qeum.sh from cape2.sh you might consider installing aptitude in cape2.sh or use apt-get install
(which seems to be the current state of things in cape2.sh)
ah true, the aptitude was introduced by one user, as it solves better dependencies, but we don't need that in cape2.sh, it was just bad c&p, thanks for catch that, pushing fix
just tested it from a snapshot taken just after running kvm-qemu - looks good to me!
Thanks a bunch for all the work you put into this -it has saved me so much time!
Thank you for testing, glat is was useful, let me know if you see any other bug
El dom., 7 mar. 2021 0:09, zoomequipd notifications@github.com escribió:
just tested it from a snapshot taken just after running kvm-qemu - looks good to me!
Thanks a bunch for all the work you put into this -it has saved me so much time!
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/doomedraven/Tools/issues/82#issuecomment-792107785, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAOFH3ZQYDD2TPFP5UWTWPLTCKYZZANCNFSM4YW7KFVA .
Prerequisites
Please answer the following questions for yourself before submitting an issue.
Expected Behavior
jemalloc should install cleanly without any errors
Current Behavior
the execution of cape2.sh ends with an error regarding jemolloc
ln: failed to create symbolic link '/usr/lib/x86_64-linux-gnu/libjemalloc.so': File exists
Failure Information (for bugs)
Steps to Reproduce
Please provide detailed steps for reproducing the issue.
sudo ./kvm-qemu.sh all <username> | tee kvm-qemu.log
sudo ./cape2.sh base cape | tee cape.log
Context
I believe this is a result of running kvm-qemu.sh which installs jemalloc in a different manner, thus resulting in a conflict.
https://github.com/doomedraven/Tools/blob/41bdab856c6bb9e5a559d77606aea8101a5a94f0/Virtualization/kvm-qemu.sh#L774-L778
I suspect reusing the logic from
kvm-qemu.sh
is a solution, though I'm not confident if that's the best solution. I am happy to submit a PR with some direction.As a sidenote, though I don't think it matter here, I also observed that the file installed via the package in
kvm-qemu.sh
is different than the one attempted to be symlink'ed incape2.sh
Failure Logs