https://bugs.kde.org/show_bug.cgi?id=348128

--- Comment #8 from mat...@dnet.it ---
Hi Jack,

I dont know if the guys will be able to backport the fix, and how long it is
going to take.
However, you can build a custom version for yourself very easily in the
meantime.

Here some instructions on how to go about it (run these in the terminal):
#make a temporary directory
mkdir /tmp/cantor
cd /tmp/cantor

#download the source of your currently installed cantor package
sudo apt-get install debian-keyring
sudo apt-get source cantor

#the above will create a subdirectory called "cantor-version-number-something"
#in there you will find the directory "src" (i cant test right now, so you
might have to look for it)
#find and edit the file "src/backends/sage/sagesession.cpp" according to the
submitted patch
#which you can find here:
https://quickgit.kde.org/?p=cantor.git&a=commitdiff&h=5d185d21431a989055ab4a1501584dbb3ea17842&hp=ad75e06d3b4317ab45e1b84419b9abb8e33ad6fa
#this patch is very simple: you only have to ad "+(|Math)" right after "Sage"
on the right line
#the "right line" is 194 for the latest cantor, but it might be some lines up
or down in your version

#now rebuild the package
sudo apt-get install dpkg-dev
sudo apt-get install build-dep cantor
cd "cantor-version-something"
dpkg-buildpackage -b -us -uc
cd ..

#you should now have some debian packages 
#install the sage backend with
sudo dpkg -i cantor-backend-sage*.deb

Once again, this is just the temporary workaround that I used until the change
will show up in the official Ubuntu repositories.

Good luck!
Matteo

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to