I know I can install this with the traditional rpm command, and I know it will work, but I always get some nasty comments about doing so. YAST doesn't seem to see it. PLEASE don't tell me that Libre Office is just as good; it's not. --doug
Douglas McGarrett <dmcgarrett@optonline.net> writes:
I know I can install this with the traditional rpm command, and I know it will work, but I always get some nasty comments about doing so. YAST doesn't seem to see it. PLEASE don't tell me that Libre Office is just as good; it's not. --doug
zyyper can install rpm files too: zypper in <your_rpm_file> Charles
On Tue, Oct 19, 2021 at 1:27 AM Douglas McGarrett <dmcgarrett@optonline.net> wrote:
I know I can install this with the traditional rpm command, and I know it will work, but I always get some nasty comments about doing so. YAST doesn't seem to see it. PLEASE don't tell me that Libre Office is just as good; it's not. --doug
The advantage with YaST/zypper for something like this (installing a known package) is that they will pull in any additional RPMs that are needed. The rpm command does not do that. It will just complain and leave you to finding the missing bits. If there are no mnissing bits, there is no difference. I use all three programs, depending on what I'm up to. In the end, they are maintaining the same database that describes what is installed. -- Roger Oberholtzer
On 10/19/21 2:33 AM, Roger Oberholtzer wrote:
I know I can install this with the traditional rpm command, and I know it will work, but I always get some nasty comments about doing so. YAST doesn't seem to see it. PLEASE don't tell me that Libre Office is just as good; it's not. --doug The advantage with YaST/zypper for something like this (installing a known package) is that they will pull in any additional RPMs that are needed. The rpm command does not do that. It will just complain and leave you to finding the missing bits. If there are no mnissing bits,
On Tue, Oct 19, 2021 at 1:27 AM Douglas McGarrett <dmcgarrett@optonline.net> wrote: there is no difference. I use all three programs, depending on what I'm up to. In the end, they are maintaining the same database that describes what is installed.
Doug, the other replies to your request were not probably aware of the many repeated very difficult problems you have had using rpm and zypper, and hence the frequent advice on this list that you use YaST for managing software and repositories. This softmaker rpm package is a corner case that represents a very teeny fraction of the software you install. You should still use YaST whenever possible. For this app however, you will need to use zypper. Please do not use rpm. I suggest you run as root: zypper -in -D <filename> which will do a "dry-run" installation first to inform you of any dependency problems, etc. Once in the clear, you can run: zypper -in <filename> to do the actual install. If the dry-run produces errors, copy those to a post back here before proceeding with the actual install. --dg 15.2 & 15.3/KDE
DennisG <dwgallien@gmail.com> writes:
This softmaker rpm package is a corner case that represents a very teeny fraction of the software you install. You should still use YaST whenever possible. For this app however, you will need to use zypper. Please do not use rpm.
This is definitely a corner case. Out of curiosity, I downloaded the rpm, copy the payload to a temp dir to take a look at it. It is terribly packaged for a rpm that is meant for multiple distros. The software is installed into the /usr hierarchy and relies on system libraries. I run ldd against the binaries on my Tumbleweed system and everything was OK. However, it might not work with Leap that have older libraries. They should have included everything and install into the /opt hierarchy. Charles
On 10/20/21 04:22, Charles Philip Chan wrote:
DennisG <dwgallien@gmail.com> writes:
This softmaker rpm package is a corner case that represents a very teeny fraction of the software you install. You should still use YaST whenever possible. For this app however, you will need to use zypper. Please do not use rpm.
This is definitely a corner case. Out of curiosity, I downloaded the rpm, copy the payload to a temp dir to take a look at it. It is terribly packaged for a rpm that is meant for multiple distros. The software is installed into the /usr hierarchy and relies on system libraries. I run ldd against the binaries on my Tumbleweed system and everything was OK. However, it might not work with Leap that have older libraries. They should have included everything and install into the /opt hierarchy.
I'll disagree 100% here, what this package does is exactly what i'd expect an rpm to do, the whole point of using an rpm is to make the most of system libraries and the fact they get security updates. If you want everything bundled use a flatpak. This approach generally works ok because libraries with the same .so name and version should be backwards compatible so if you presume that Centos is the oldest thing worth supporting you build for that and then Leap, Fedora and Tumbleweed will be fine until they no longer ship a .so with that version number and then you get a clear error when launching the app. Sure using obs and building specific rpm's for each version is probably slightly better, but many companies have done what softmaker is doing for many years and its a far better approach then bundling libaries like openssl and not necessarily providing timely security updates. -- Simon Lees (Simotek) http://simotek.net Emergency Update Team keybase.io/simotek SUSE Linux Adelaide Australia, UTC+10:30 GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B
On 19/10/2021 18.31, DennisG wrote:
On 10/19/21 2:33 AM, Roger Oberholtzer wrote:
I know I can install this with the traditional rpm command, and I know it will work, but I always get some nasty comments about doing so. YAST doesn't seem to see it. PLEASE don't tell me that Libre Office is just as good; it's not. --doug The advantage with YaST/zypper for something like this (installing a known package) is that they will pull in any additional RPMs that are needed. The rpm command does not do that. It will just complain and leave you to finding the missing bits. If there are no mnissing bits,
On Tue, Oct 19, 2021 at 1:27 AM Douglas McGarrett <> wrote: there is no difference. I use all three programs, depending on what I'm up to. In the end, they are maintaining the same database that describes what is installed.
Doug, the other replies to your request were not probably aware of the many repeated very difficult problems you have had using rpm and zypper, and hence the frequent advice on this list that you use YaST for managing software and repositories.
This softmaker rpm package is a corner case that represents a very teeny fraction of the software you install. You should still use YaST whenever possible. For this app however, you will need to use zypper. Please do not use rpm.
I suggest you run as root: zypper -in -D <filename> which will do a "dry-run" installation first to inform you of any dependency problems, etc. Once in the clear, you can run: zypper -in <filename> to do the actual install. If the dry-run produces errors, copy those to a post back here before proceeding with the actual install.
Note: you have to specify the path to filename, even if the rpm resides in the current directory. If not, zypper will try to find it in the configured repositories and fail. It can also be done with YaST, using the method described by Peter, and which I also described long ago to Doug. -- Cheers / Saludos, Carlos E. R. (from 15.2 x86_64 at Telcontar)
Am 19.10.21 um 01:26 schrieb Douglas McGarrett:
I know I can install this with the traditional rpm command, and I know it will work, but I always get some nasty comments about doing so. YAST doesn't seem to see it. PLEASE don't tell me that Libre Office is just as good; it's not. --doug
What I would do (in my German Yast, roughly translated) Add a directory for all rpm packages to a convenient location, put the rpm package there. Go to Yast - configure Software Repositories Go to - add repository Point Yast to that directory, mark it in Yast as rpm directory. Do a refresh of all directories in Yast Then in Yast go to - install software In my Yast "show repositories" is set You should see in that rpm repository the rpm package (if you did refresh the repositories!) Use Yast to install it. Should work. Peter
On 20/10/2021 11.45, Peter McD wrote:
Am 19.10.21 um 01:26 schrieb Douglas McGarrett:
I know I can install this with the traditional rpm command, and I know it will work, but I always get some nasty comments about doing so. YAST doesn't seem to see it. PLEASE don't tell me that Libre Office is just as good; it's not.
What I would do (in my German Yast, roughly translated)
I would do the same.
Add a directory for all rpm packages to a convenient location, put the rpm package there.
Go to Yast - configure Software Repositories Go to - add repository Point Yast to that directory, mark it in Yast as rpm directory. Do a refresh of all directories in Yast Then in Yast go to - install software
In my Yast "show repositories" is set
You should see in that rpm repository the rpm package (if you did refresh the repositories!)
Use Yast to install it.
Should work.
Peter
-- Cheers / Saludos, Carlos E. R. (from 15.2 x86_64 at Telcontar)
On Wed, Oct 20, 2021 at 12:32 PM Peter McD <peter.posts@gmx.net> wrote:
What I would do (in my German Yast, roughly translated)
Add a directory for all rpm packages to a convenient location, put the rpm package there.
Go to Yast - configure Software Repositories Go to - add repository Point Yast to that directory, mark it in Yast as rpm directory. Do a refresh of all directories in Yast Then in Yast go to - install software
Am I missing something? You can tell zypper it install rpms. If something additional is needed, it will check the defined repos and offer to install them as well. Exactly as YaST does. What additional thing is YaST doing? In both cases you have downloaded some rpms to your system. In both cases any ones you have missed that can be found are also installed. Since you have downloaded the rpms, I suspect that both yast and zypper will caution you that the rpm signatures cannot be verified. In both cases, you can choose to ignore this and continue. -- Roger Oberholtzer
On 20/10/2021 19.51, Roger Oberholtzer wrote:
On Wed, Oct 20, 2021 at 12:32 PM Peter McD <peter.posts@gmx.net> wrote:
What I would do (in my German Yast, roughly translated)
Add a directory for all rpm packages to a convenient location, put the rpm package there.
Go to Yast - configure Software Repositories Go to - add repository Point Yast to that directory, mark it in Yast as rpm directory. Do a refresh of all directories in Yast Then in Yast go to - install software
Am I missing something? You can tell zypper it install rpms. If something additional is needed, it will check the defined repos and offer to install them as well. Exactly as YaST does. What additional thing is YaST doing? In both cases you have downloaded some rpms to your system. In both cases any ones you have missed that can be found are also installed.
Yes, you are missing something :-) Suppose you download something.rpm, which copies to /home/roger/Downloads. You then do: $ cd /home/roger/Downloads/ $ sudo zypper install something.rpm refreshing repos... ... something.rpm not found $ (from memory) See what happens? zypper looks inside the repos and ignores the current directory. the trick is to give the path: $ cd /home/roger/Downloads/ $ sudo zypper install /home/roger/Downloads/something.rpm Problem: package will be orphaned. The method that Peter proposes is better and is the one I use: Download the rpms to /home/roger/Downloads/MyRepo/ # cd /home/roger/Downloads/MyRepo zypper addrepo --check --refresh \ /home/roger/Downloads/MyRepo MyRepo Then you only have to use: zypper install something to install it, or the equivalent in YaST. Also, when you download a new version, updates will work. -- Cheers / Saludos, Carlos E. R. (from 15.2 x86_64 at Telcontar)
On 10/20/21 2:50 PM, Carlos E. R. wrote:
On 20/10/2021 19.51, Roger Oberholtzer wrote:
On Wed, Oct 20, 2021 at 12:32 PM Peter McD <peter.posts@gmx.net> wrote:
What I would do (in my German Yast, roughly translated)
Add a directory for all rpm packages to a convenient location, put the rpm package there.
Go to Yast - configure Software Repositories Go to - add repository Point Yast to that directory, mark it in Yast as rpm directory. Do a refresh of all directories in Yast Then in Yast go to - install software
Am I missing something? You can tell zypper it install rpms. If something additional is needed, it will check the defined repos and offer to install them as well. Exactly as YaST does. What additional thing is YaST doing? In both cases you have downloaded some rpms to your system. In both cases any ones you have missed that can be found are also installed.
Yes, you are missing something :-)
Suppose you download something.rpm, which copies to /home/roger/Downloads.
You then do:
$ cd /home/roger/Downloads/ $ sudo zypper install something.rpm refreshing repos... ... something.rpm not found $
(from memory)
See what happens? zypper looks inside the repos and ignores the current directory.
the trick is to give the path:
$ cd /home/roger/Downloads/ $ sudo zypper install /home/roger/Downloads/something.rpm
Problem: package will be orphaned.
The method that Peter proposes is better and is the one I use:
Download the rpms to /home/roger/Downloads/MyRepo/
# cd /home/roger/Downloads/MyRepo zypper addrepo --check --refresh \ /home/roger/Downloads/MyRepo MyRepo
Then you only have to use:
zypper install something
to install it, or the equivalent in YaST. Also, when you download a new version, updates will work.
I am sincere when I say that this is all wonderful stuff from you guys. Just note however that it seems to go astray from the reason why I gave Doug the YaST advice in the first place: He has had a world of problems for /three years/ using the command line for software or attempting anything even remotely sophisticated, which has consumed - literally - many hours of time and effort by folks here trying to unwind what he did and continues to repeat doing. Speaking only for myself, I've hit my limit doing this (with this OP). For those more generous and patient than I, my hat is off to you and feel free to continue. 😁 --dg 15.2 & 15.3/KDE
On 20/10/2021 22.01, DennisG wrote:
On 10/20/21 2:50 PM, Carlos E. R. wrote:
On 20/10/2021 19.51, Roger Oberholtzer wrote:
On Wed, Oct 20, 2021 at 12:32 PM Peter McD <> wrote:
I am sincere when I say that this is all wonderful stuff from you guys. Just note however that it seems to go astray from the reason why I gave Doug the YaST advice in the first place: He has had a world of problems for /three years/ using the command line for software or attempting anything even remotely sophisticated, which has consumed - literally - many hours of time and effort by folks here trying to unwind what he did and continues to repeat doing.
You are right. - He doesn't know/understand how repositories work. How to add a repository, how to search for a repository, how to reject incorrect repositories. o I do not know where to find correct and simple documentation on this. We all know the above things, but can we explain them, with photos? - He still doesn't know how to search for a package with YaST and install it. - He doesn't understand how to use the openSUSE search tools to find a package, then add that correct repository, and then download and install the correct package using YaST or zypper. Proof of that: The other day we found that he had active in his system the repo: "http://packman.inode.at/suse/openSUSE_12.2/". He doesn't understand that repo can destroy his system, and how it came to be there. My guess: via one click install, by clicking at the wrong place. He should now be removing that repo (adding the right one), searching for anything installed from it, and remove those found packages.
Speaking only for myself, I've hit my limit doing this (with this OP). For those more generous and patient than I, my hat is off to you and feel free to continue. 😁
You are absolutely right. I try to help; I have explained all those things to him in the past even with photos, writing a post that takes *hours* to complete. He still makes the same question months later! It is very discouraging and puts me in a terrible mood I hate. And I have seen him rush ahead with procedures found on Internet without waiting for feedback from us, further worsening the problem. -- Cheers / Saludos, Carlos E. R. (from 15.2 x86_64 at Telcontar)
On Wed, Oct 20, 2021 at 8:50 PM Carlos E. R. <robin.listas@telefonica.net> wrote:
On 20/10/2021 19.51, Roger Oberholtzer wrote:
On Wed, Oct 20, 2021 at 12:32 PM Peter McD <peter.posts@gmx.net> wrote:
What I would do (in my German Yast, roughly translated)
Add a directory for all rpm packages to a convenient location, put the rpm package there.
Go to Yast - configure Software Repositories Go to - add repository Point Yast to that directory, mark it in Yast as rpm directory. Do a refresh of all directories in Yast Then in Yast go to - install software
Am I missing something? You can tell zypper it install rpms. If something additional is needed, it will check the defined repos and offer to install them as well. Exactly as YaST does. What additional thing is YaST doing? In both cases you have downloaded some rpms to your system. In both cases any ones you have missed that can be found are also installed.
Yes, you are missing something :-)
Suppose you download something.rpm, which copies to /home/roger/Downloads.
You then do:
$ cd /home/roger/Downloads/ $ sudo zypper install something.rpm refreshing repos... ... something.rpm not found $
(from memory)
You should give as a parameter to zypper the name of the rpm files you have downloaded and want to install. Just like you do with the rpm command. It will then install them and and additional bits found to be needed. You do not need to give the full path to the rpm. Just use a name that exists. In the current directory is ok. Or wherever you told it the file was by the name you gave. Maybe this is an undocumented way to use zypper. But I have been doing so for years.
See what happens? zypper looks inside the repos and ignores the current directory.
the trick is to give the path:
$ cd /home/roger/Downloads/ $ sudo zypper install /home/roger/Downloads/something.rpm
Problem: package will be orphaned.
Orphaned? If a package is installed, it is not orphaned. Isn't an orphaned package one that was installed to satisfy some requirement, and the requirement goes away. Then that package is no longer needed. I personally doubt that yast does anything different in this respect compared to zypper. Doesn't yast use zypper to do the heavy lifting?
to install it, or the equivalent in YaST. Also, when you download a new version, updates will work.
This I can agree about. If you place an update here then it will get updated when you do an update. This is the only benefit I see of this. None of the other arguments are, from my experience, correct. -- Roger Oberholtzer
On Thu, Oct 21, 2021 at 9:53 AM Roger Oberholtzer <roger.oberholtzer@gmail.com> wrote:
$ cd /home/roger/Downloads/ $ sudo zypper install /home/roger/Downloads/something.rpm
Problem: package will be orphaned.
Orphaned? If a package is installed, it is not orphaned.
In case of zyper orphaned package is a package that does not come from any repository. More precisely, no repository provides this package.
Isn't an orphaned package one that was installed to satisfy some requirement, and the requirement goes away.
No.
Then that package is no longer needed.
This is an "unneeded" package.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thursday, 2021-10-21 at 08:50 +0200, Roger Oberholtzer wrote:
On Wed, Oct 20, 2021 at 8:50 PM Carlos E. R. <...> wrote:
On 20/10/2021 19.51, Roger Oberholtzer wrote:
On Wed, Oct 20, 2021 at 12:32 PM Peter McD <...> wrote:
...
Yes, you are missing something :-)
Suppose you download something.rpm, which copies to /home/roger/Downloads.
You then do:
$ cd /home/roger/Downloads/ $ sudo zypper install something.rpm refreshing repos... ... something.rpm not found $
(from memory)
You should give as a parameter to zypper the name of the rpm files you have downloaded and want to install. Just like you do with the rpm command. It will then install them and and additional bits found to be needed. You do not need to give the full path to the rpm. Just use a name that exists. In the current directory is ok. Or wherever you told it the file was by the name you gave.
Maybe this is an undocumented way to use zypper. But I have been doing so for years.
Telcontar:/home/cer/Downloads/Firefox_downloads # ls -l imap-2007e_suse-16.1.2.x86_64.rpm - -rw-r--r-- 1 cer users 617229 Jun 20 2014 imap-2007e_suse-16.1.2.x86_64.rpm Telcontar:/home/cer/Downloads/Firefox_downloads # zypper info imap-2007e_suse-16.1.2.x86_64.rpm Loading repository data... Reading installed packages... package 'imap-2007e_suse-16.1.2.x86_64.rpm' not found. Telcontar:/home/cer/Downloads/Firefox_downloads # zypper info ./imap-2007e_suse-16.1.2.x86_64.rpm Loading repository data... Reading installed packages... package './imap-2007e_suse-16.1.2.x86_64.rpm' not found. Telcontar:/home/cer/Downloads/Firefox_downloads # zypper info /home/cer/Downloads/Firefox_downloads/imap-2007e_suse-16.1.2.x86_64.rpm Loading repository data... Reading installed packages... package '/home/cer/Downloads/Firefox_downloads/imap-2007e_suse-16.1.2.x86_64.rpm' not found. Telcontar:/home/cer/Downloads/Firefox_downloads # Yet: Telcontar:/home/cer/Downloads/Firefox_downloads # zypper install imap-2007e_suse-16.1.2.x86_64.rpm Loading repository data... Reading installed packages... Resolving package dependencies... The following NEW package is going to be installed: imap 1 new package to install. Overall download size: 602.8 KiB. Already cached: 0 B. After the operation, additional 4.2 MiB will be used. Continue? [y/n/v/...? shows all options] (y): y Retrieving package imap-2007e_suse-16.1.2.x86_64 (1/1), 602.8 KiB ( 4.2 MiB unpacked) Checking for file conflicts: .........................................................................................................................................................................[done] (1/1) Installing: imap-2007e_suse-16.1.2.x86_64 ......................................................................................................................................................[done] Telcontar:/home/cer/Downloads/Firefox_downloads # Telcontar:/home/cer/Downloads/Firefox_downloads # zypper info imap Loading repository data... Reading installed packages... Information for package imap: - ----------------------------- Repository : @System Name : imap Version : 2007e_suse-16.1.2 Arch : x86_64 Vendor : openSUSE Installed Size : 4.2 MiB Installed : Yes Status : up-to-date Source package : imap-2007e_suse-16.1.2.src Summary : IMAP4, POP2, and POP3 Mail Server Description : This package contains IMAP4, POP2, and POP3 mail servers. After installation, activate the servers in the file /etc/inetd.conf. Telcontar:/home/cer/Downloads/Firefox_downloads # And the package is indeed orphaned: YaST displays it in red.
Problem: package will be orphaned.
Orphaned? If a package is installed, it is not orphaned. Isn't an orphaned package one that was installed to satisfy some requirement, and the requirement goes away. Then that package is no longer needed.
Orphaned means it does't come from any repository. YaST (nor zypper) knows where it came from, can't update it automatically.
I personally doubt that yast does anything different in this respect compared to zypper. Doesn't yast use zypper to do the heavy lifting?
Nope. It calls the same libraries as zypper does, but never zypper itself.
to install it, or the equivalent in YaST. Also, when you download a new version, updates will work.
This I can agree about. If you place an update here then it will get updated when you do an update. This is the only benefit I see of this. None of the other arguments are, from my experience, correct.
Well, see above :-) - -- Cheers, Carlos E. R. (from openSUSE 15.2 x86_64 at Telcontar) -----BEGIN PGP SIGNATURE----- iHoEARECADoWIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCYXEiHhwccm9iaW4ubGlz dGFzQHRlbGVmb25pY2EubmV0AAoJELUzGBxtjUfV37gAoIa6hFPuf7rpkCSDnK8E zxs4TjWsAJ0Ydy4cCgoBWx87YHNmkn3qNMtd2w== =gYWG -----END PGP SIGNATURE-----
participants (8)
-
Andrei Borzenkov -
Carlos E. R. -
Charles Philip Chan -
DennisG -
Douglas McGarrett -
Peter McD -
Roger Oberholtzer -
Simon Lees