Hi,
how can I solve this problem?
**
Problema: nada fornece libcrypto.so.1.0.0(OPENSSL_1.0.0)(64bit) que é necessário a pclsync-3.1.1-2.x86_64
Solução 1: desinstalação de pclsync-3.1.1-2.x86_64
Solução 2: quebrar pclsync-3.1.1-2.x86_64 ao ignorar algumas das dependências**
I have installed some packages to try to solve it, but nothing work.
Many thanks
Now, I don’t speak any portugese, but if this
“desinstalação de pclsync-3.1.1-2.x86_64”
actually means, what I think it does (uninstall pclsync-3.1.1-2.x86_64), then that is the correct solution.
AK
The answer may not be totally clear cut.
What are you doing that asks for pclsync (A search of my systems says I don’t have that installed)?
If you’re installing an application that requires it, perhaps there is a more updated version.
TSU
Replace “updated” with “compatible” or “built for openSUSE and not some other OS”.
I translate
“nada fornece libcrypto.so.1.0.0(OPENSSL_1.0.0)(64bit)”
to “nothing provides” and so it is:
rpm -q --provides libopenssl1_0_0
libcrypto.so.1.0.0()(64bit)
Notice the difference?
Whatever this pclsync package is and wherever it came from, it certainly is not built for openSUSE, so the only clean solution is not to install or if already installed to uninstall it.
AK
“pclsync” is for pCloud Drive… so I don’t want to remove it
I have installed libopenssl1_0_0 and libopenssl-devel to try to solve, but didn’t
TSU
If you don’t want to have an inconsistent package database and want zypper/rpm to stop complaining, then you will have no other choice.
See above, there is no openSUSE package which will satisfy the requirement
libcrypto.so.1.0.0**(OPENSSL_1.0.0)**(64bit)
so rpm/zypper will keep on complaining and rightly so.
While it might be possible or even likely the program is working anyway (if not, you will get funny “symbol lookup error” messages), you will have to hack around the problem. Either way, the only solution to keep your package database sane is to remove that package.
After that you can try to hack around the problem, but first you will have to uninstall that package.
AK
No the OP wants to install pclsync but libcrypto is missing.
Here, under oS 13.2, libcrypto.so.1.0.0 can be found in package libopenssl1_0_0 (version 1.01k) from the update repo.
From openSUSE Software I see that LEAP 42.2 package is version 1.02j. If the installed .so library has a slightly different numbering, just make a simlink to in the same directory (as root, obviously) named libcrypto.so.1.0.0.
@vinicius
Se me permite a sugestão, ao postar essas mensagens tente traduzir para o Inglês, mesmo que não fique exatamente igual o pessoal daqui vai entender bem melhor, tem pouca gente que entende Português nesse forum.
Now, I don’t want to get rude, but have you actually read this thread before answering?
So the package is already installed, now isn’t it?
And about installing libopenssl_1_0_0
And by reading (my) other comments, you will find out why this problem will remain.
So again, the only way to keep the package data base of zypper/rpm consistent is to uninstall that incompatible RPM and try to hack around (unpacking the contents of the RPM and copy them manually and then hope for the best) and not to installl that package via rpm/zypper.
AK
Now, for people knowing how to build RPMs, here is a quick, hackish and butt-ugly but “clean” in the sense of “don’t f*ck up your rpm data base” solution.
pclsync.spec:
#
# spec file for package pclsync
#
### ugly hack (getting rid of requirement for libssl.so.1.0.0(OPENSSL_1.0.0) and the like)
%define _use_internal_dependency_generator 0
%define my_requires /tmp/my-requires
Name: pclsync
Version: 3.1.1
Release: 1000.1
License: SUSE-NonFree
Summary: Client for pCloud Drive
Url: http://pcloud.com
Group: Productivity/Networking/Other
Source0: pCloud_Linux_amd64_3.1.1.deb
Source1: pCloud_Linux_i386_3.1.1.deb
BuildRequires: dpkg
BuildRoot: %{_tmppath}/%{name}-%{version}-build
%description
pCloud Drive is a GUI, that allows you to open your pCloud account as a virtual file system.
pCloud is a cloud storage provider that combines usability with sophisticated technology to
give you the most convenient way to access all your files on the go. pCloud is supported on
six platforms: Linux, MacOS and Windows as pCloud Drive; Android and iOS as native mobile
applications; and through a web panel on my.pCloud.com. The platform capability includes
advanced sharing options, file versioning and preserving of deleted files, advanced streaming
options for audio and video files, as well as view options for the most commonly used file
formats. Some of the pCloud Drive specific features include virtual asynchronous file system
and a multi-folder synchronization tool.
%prep
## nothing to do
%build
## nothing to do
%install
pushd %{buildroot}
%ifarch x86_64
dpkg -X %{SOURCE0} .
rm -rf usr/lib usr/share/menu
gunzip -f -n usr/share/doc/pclsync/changelog.gz
mkdir -p usr/share/doc/packages/
mv usr/share/doc/pclsync usr/share/doc/packages/
sed -i 's|Icon=.*|Icon=pcloud-icon|g' usr/share/applications/pclsync.desktop
sed -i 's|Categories=.*|Categories=Network;FileTransfer;|g' usr/share/applications/pclsync.desktop
%else
dpkg -X %{SOURCE1} .
rm -rf usr/lib usr/share/menu
gunzip -f -n usr/share/doc/pclsync/changelog.gz
mkdir -p usr/share/doc/packages/
mv usr/share/doc/pclsync usr/share/doc/packages/
sed -i 's|Icon=.*|Icon=pcloud-icon|g' usr/share/applications/pclsync.desktop
sed -i 's|Categories=.*|Categories=Network;FileTransfer;|g' usr/share/applications/pclsync.desktop
%endif
#### ugly hack to get rid of unsatisfiable requirement for libssl.so.1.0.0(OPENSSL_1.0.0) and the like
#### as debian packages tend to do some stricter versioning of libs here which would also be detected
#### by /usr/lib/rpm/find-requires and result in an uninstallable package
%__cat << EOF > %{my_requires}
%{__find_requires} | grep -vE "OPENSSL_1\.0"
EOF
%__chmod 755 %{my_requires}
%define __find_requires %{my_requires}
%clean
%__rm -f %{my_requires}
%__rm -rf %{buildroot}
%files
%defattr(-,root,root)
%{_bindir}/psyncgui
%{_datadir}/applications/%{name}.desktop
%{_datadir}/pixmaps/pcloud-icon.*
%{_docdir}/%{name}
The two .deb files can be obtained from https://www.pcloud.com/download-free-online-cloud-file-storage.html under “Linux”.
But honestly, after reading through a whole load of “BS-Bingo” and nearly choking on the “unbreakable security” claim on the main page, I seriously don’t want to be involved any further in helping to distribute this type of crapware, so I’m out of here.
So if you don’t know what to do with the spec file above, don’t bother me, I just wrote and tested that this builds installable RPMs, I did not test if the application is actually running and working as expected, so use at your own risk, no matter if you use that spec to build a RPM or not.
AK
I read the first post:
Problema: nada fornece libcrypto.so.1.0.0(OPENSSL_1.0.0)(64bit) que é necessário a pclsync-3.1.1-2.x86_64
Solução 1: desinstalação de pclsync-3.1.1-2.x86_64
Solução 2: quebrar pclsync-3.1.1-2.x86_64 ao ignorar algumas das dependências
The first line translate as : nothing supply libcripto.so.1.0.0… necessary for pclsync.
I don’t want to disagree, but as far as I can read the message means that pclsync was not installed, since it can’t find the exact .so.x.x file and the OP paused installation to ask here. Of course, the OP could have forced install (Solution 2) so I suggested checking if the .so lib is correctly named or create a simlink in the lib folder, as IME this usually works when installing a package not using the same library base as your distro version.
Ok, thanks guys