i have a folder with an old plone version 2.5 and i would restore it on mac os mavericks or ubuntu 12.04. I know, that this really old plone version need python 2.4. I get it form python.org for mac os x but i don't found anything for ubuntu 12.04. I tried to restore this dump but it's not easy without a good documentation for version 2.5.
How can i restore this dump?
Start with an installer from https://launchpad.net/plone/2.5/2.5.5 . That will take care of not only Python, but also handle other binary components.
Install Plone on the target server, then transfer any custom add-on Plone products from the source server. Test it.
When that's running, copy the Data.fs file from the source to overwrite the Data.fs on the target.
Related
I have a new Macbook Pro (M1) and I need to install multiple versions of dotnet core - my large solution has a mixture of versions, to busy to address that issue right now.
But how to I handle this situation ? (note I have a symlink for the X64 version of dotnet)
I'm not sure if it will work for your specific case, but if you're okay with x64 architecture for all .NET versions, it should work.
Delete usr/local/share/dotnet if you have one.
Download installers with x64 architecture for all .NET versions you need;
You need to figure out which of them will be placed in 64 folder. !! Install them first !! After this inside usr/local/share/dotnet you will have only 64 folder.
Copy all files from usr/local/share/dotnet/64 to usr/local/share/dotnet
Delete usr/local/share/dotnet/64 folder
Install the rest of versions via installer and be sure that thay will be placed in usr/local/share/dotnet NOT in usr/local/share/dotnet/64
I work on a centOS 6.6 distro and would like to use Rstudio. I would like to use an up to date version say v>0.99 but from the download page I can see that Rstudio desktop requires RHEL7.
Looking for older versions of rstudio desktop I see that RHEL6 can only get v<=0.981103, though Rstudio server seems fine, and I am OK if many can use a server version.
rpm is a no go for me so is there a way to get the sources for the server version like they provide for the desktop version ? I can't find it anywhere but it appears it is possible: see this post.
Of course if there is a trick to build Rstudio desktop on centOS 6.6 I am a buyer...
You won't be able to build RStudio Desktop for RHEL6 because of a glibc requirement induced by Qt 5.4. This is not easily evaded so if you have a platform requirement for RHEL6 you'll want to stick with the server version.
The desktop and server versions of RStudio are actually built from the same source code. You can get the source for any RStudio release here:
https://github.com/rstudio/rstudio/releases
The make-package Server RPM command in rstudio/package/linux will start the build once you've got all the dependencies installed. See here for details (or INSTALL): https://github.com/rstudio/rstudio/wiki/Installing-RStudio-Dependencies
This is my first attempt at making a Qt Application work on different systems.
I have opted for static linking method.I have already compiled the sources of Qt 5.5 and compiled my application with the static Qt. The executable is working fine on my computer.
My operating system is Ubuntu 15.04. But when I tried to run the same executable on Ubuntu 14.04 then I ran into trouble. The key details of the error message are given below.
libstdc++.so.6 cxxabi_1.3.8 not found
I did a standard Google search and realised it was because I had a newer version of it on my machine, the machine where I had created the executable. There were so many different approaches to handle this problem. One of the solutions I saw involved shipping your own copy of libstdc++.so with the executable. But when I tried to copy the .so file to a pen drive, there was a warning saying that the file system does not support such files.
My question is , what am I doing wrong ? Also if I wanted to make the executable target Ubuntu 10.04, what would be the correct procedure handling the backward compatibility issues. I know that one method would be to install the same OS on my machine and then create the executable , is there any other way?
libstd++ is backward compatible but not forward compatible, which means you can run a program with a newer version of libstdc++ than the one you compiled it with but not vice-versa. This is what you experienced.
One way to deal with this issue is using older OS versions as the build machine. When you for example use Ubuntu 14.04 LTS, you'll get this list of compatible target systems.
The build system you're using will probably limit available compilers. On Ubuntu 14.04 you get GCC 4.8, which is good for most C++11 and packages for clang 3.6 are available, which will give you full C++14 support.
Targeting Ubuntu 10.04 will be challenging if you do not want to use a stone age compiler.
The idea of shipping libstdc++ will not help you much because you'll run into the same problem with libc.
I have searched all day in order to use Qt 5.4 or Qt 5.5.
I have two machines, one running Ubuntu 15 and the other Ubuntu 14, but got the same results.
I have installed the program through the download-online package, and now I have beautiful /opt/Qt/5.4/ and /opt/Qt/5.5 folders.
That's all. I am stuck in here. If I run qmake -version, the reply is:
Using Qt version 5.2.1 in /usr/lib/x86_64-linux-gnu
Also, if I run qtchooser -list-versions, I get:
4
5
default
qt4-x86_64 linux-gnu
qt4
qt5-x86_64 linux-gnu
qt5
I have to use SuperCollider 3.7 for an important project, and I need Q t5.4 or higher. Is there anybody who can tell me what to do after installing the package to make programs see Qt 5.4 or higher?
I even tried to build from the source code, but in that case init-repository doesn't work.
Luca
I have had the same problem different times, therefore my late answer.
You should create the file /etc/xdg/qtchooser/default.conf, and put the path to the bin and lib directory, for example:
/opt/Qt/5.5/gcc_64/bin
/opt/Qt/5.5/gcc_64/lib
Now this is the default configuration, and it is shown with qtchooser -l as such.
See man qtchooser:
/etc/xdg/qtchooser/*.conf
System-wide configuration files. Each has two lines, the first is the path to the binaries and the second is the path to the
Qt libraries. If a default.conf is provided, the settings from it will be automatically used in case nothing else is selected.
Launch any version of Qt Creator. It can be either the old one from previous install or the newer one.
Go to Projects/Manager Kits and add kits in which you are interested (Qt 5.4, 5.5 or the one which is install by default)
Open any project, code and build with any of the specified kits.
As I was digging in the right way to change the default choice for qt session in my old ubuntu 14.04 LTS, I did find this old topic as best match for my own question.
So here my answer for any 14.04 living in 2019 : the default package qmake point on qtchooser, which looks for its conf in /usr/lib/x86_64-linux-gnu/qt* directories
The default conf is in /usr/lib/x86_64-linux-gnu/qt-default/ .
If you haven't this, look at your "qtchooser -print-env" result to see what's your own path. I think that a good practice to set this as system default should be to create a link from the xdg default to your ubuntu standard default (as it works for me) :
sudo mkdir -p /etc/xdg/qtchooser/
cd /etc/xdg/qtchooser/
ln -s /usr/lib/x86_64-linux-gnu/qt-default/qtchooser/default.conf default.conf
As far I can see, there's no more things as "Managers Kits" in qtcreator
I'm having some difficulty upgrading my Plone install to 4.2.5.
The old Plone/zope install was running on Ubuntu 8.04. I upgraded the OS to 12.04, and reinstalled plone and zope.
I followed the instructions at: http://plone.org/documentation/manual/upgrade-guide/minor-version-upgrades for the upgrade.
The 12.04 install was successful, the trouble comes when I copy my old configs, and data over into the new install.
When I run bin/buildout after copying over, I get the message:
Error: Buildout now includes 'buildout-versions' (and part of the older 'buildout.dumppickedversions').
Remove the extension from your configuration and look at the 'show-picked-versions' option in buildout's documentation.
I tried removing the extensions, which allows bin/buildout to finish without error, however when I start zope, I get the following error:
File "/home/plone/Plone/buildout-cache/eggs/ZODB3-3.10.5-py2.7-linux-x86_64.egg/persistent/init.py", line 19, in
from cPersistence import Persistent, GHOST, UPTODATE, CHANGED, STICKY
ImportError: /home/plone/Plone/buildout-cache/eggs/ZODB3-3.10.5-py2.7-linux-x86_64.egg/persistent/cPersistence.so: undefined symbol: PyUnicodeUCS2_AsEncodedString
Python comes in two Unicode flavours; narrow and wide, or UCS2 and UCS4, with wide builds allowing for more Unicode character support. Your compiled C extension is compiled with a wide Python but you are now using a narrow Python.
Your best bet is to remove the ZODB3 egg and have buildout recreate it. Delete the /home/plone/Plone/buildout-cache/eggs/ZODB3-3.10.5-py2.7-linux-x86_64.egg directory altogether.
You probably have to do this for more eggs that have extensions.