[opensuse] help with zypper
I wanted to build a openSuse 13.2 system on an AMD rather than my current Intel platform. I was planning on installing 13.2 from the installation disk, then adding the packages required to mirror my current system. I have studied a lot of the zypper manpage, bloody 1953 lines long! I found a file /var/log/zypp/history that appears to contain all of the updates to my system. The manpage suggests "see the shell command". But the manpage also says "shell support is not complete so expect bugs there". The history file appears to have installation date and time, a command, package name, version, architecture, followed by what appears to be maybe some path to the RPM? Is this what the shell is expecting, and will it read these lines and update my other machine? Or is this the wrong approach all together? The manpage states that if I had set the keeppackages property, all of the RPMs would be saved in /var/cache/zypp/packages and I could use zypper to install them directly from there. But I did not know about that property until recently. Comments, suggestions? Thanks Don -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2015-04-07 22:39, don fisher wrote:
I wanted to build a openSuse 13.2 system on an AMD rather than my current Intel platform. I was planning on installing 13.2 from the installation disk, then adding the packages required to mirror my current system.
I have studied a lot of the zypper manpage, bloody 1953 lines long! I found a file /var/log/zypp/history that appears to contain all of the updates to my system. The manpage suggests "see the shell command". But the manpage also says "shell support is not complete so expect bugs there".
The history file appears to have installation date and time, a command, package name, version, architecture, followed by what appears to be maybe some path to the RPM?
Is this what the shell is expecting, and will it read these lines and update my other machine? Or is this the wrong approach all together? The manpage states that if I had set the keeppackages property, all of the RPMs would be saved in /var/cache/zypp/packages and I could use zypper to install them directly from there. But I did not know about that property until recently.
Comments, suggestions?
Thanks Don
Hi Don, You can query the rpm db. This will get you a list of package names: rpm -qa --qf "%{NAME} ">installed_rpms Then you could put this on your new system and run something like: zypper in $(cat installed_rpms) -Michael -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2015-04-08 05:25, Michael J Dur wrote:
On 2015-04-07 22:39, don fisher wrote:
This will get you a list of package names: rpm -qa --qf "%{NAME} ">installed_rpms
Then you could put this on your new system and run something like: zypper in $(cat installed_rpms)
True. But the list doesn't contain data as to what repo to obtain each package from, and that is a problem when we use alternate repos for the same packages. YaST package manager can export/import a list of installed packages. But it also does not consider repos. - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlUlUDwACgkQja8UbcUWM1wOvwD+JGQKwKaZlm3g5+xpIyAtqEcA WECJC4qykULj08PqokQA/jdOJCzbHIKz1W1wdBX1ziPO8T50ISVyp6LlmbFqoBVI =xjQ4 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Le 08/04/2015 17:58, Carlos E. R. a écrit :
True. But the list doesn't contain data as to what repo to obtain each package from, and that is a problem when we use alternate repos for the same packages.
zypper lr should give a list that ca, be used to include them, isn't it? jdd -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2015-04-08 18:06, jdd wrote:
Le 08/04/2015 17:58, Carlos E. R. a écrit :
True. But the list doesn't contain data as to what repo to obtain each package from, and that is a problem when we use alternate repos for the same packages.
zypper lr should give a list that ca, be used to include them, isn't it?
No. That produces a list of repos. We need a list of packages installed from each repo, separate. Suppose, for instance, that you have libxine2-codecs and xine-ui installed. The second package can be obtained from several places: * xine-ui: Video player with plugins - 0.99.7.36.2 [multimedia:xine] - 0.99.7.8.1.3 [suse-oss] - 0.99.7.42.10 [packman] Now, "zypper in xine-ui" will install... from where? You do want to make sure it comes from packman. So you need a paired list of packages, and the exact repo each came from. - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlUlVugACgkQja8UbcUWM1y/dAEAjh9yop6ebbSzqkS3qN0TXlLt GYBKi8nN6S3QnUrznasA/3tOxfkBWGt5JNITZJ4SayxUDfV3NL0lZd6jmI4yg2/E =dN5V -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Le 08/04/2015 18:27, Carlos E. R. a écrit :
No. That produces a list of repos.
like the one zypper knows of in the running distro We need a list of packages
installed from each repo, separate.
how do zypper know that from the beginning? is it not in the rpm database? if not where? jdd -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Wed, 8 Apr 2015 18:34, jdd wrote:
Le 08/04/2015 18:27, Carlos E. R. a écrit :
No. That produces a list of repos.
like the one zypper knows of in the running distro
We need a list of packages
installed from each repo, separate.
how do zypper know that from the beginning? is it not in the rpm database? if not where?
That is stored in the "Vendor" field in the rpm, and thus rpm database. "rpm -qi <package>" shows it. And for a list of installed packages and from which repo, zypper aso has the answer (well, maybe not in the wanted format, but that's what sed is for): "zypper search --installed-only --details --sort-by-repo" split that by reponame, and be aware that some packages give back "(System Packages)" as reponame (LANG=C), mostly foreign packages (without the needed info in the "Vendor" field), or packages that are not found in any of the "active" repos. - Yamaban.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2015-04-08 18:54, Yamaban wrote:
On Wed, 8 Apr 2015 18:34, jdd wrote:
how do zypper know that from the beginning? is it not in the rpm database? if not where?
That is stored in the "Vendor" field in the rpm, and thus rpm database. "rpm -qi <package>" shows it.
Not quite. The "Vendor" is not the same string as the repo name. IIRC, different repos can have the same vendor string. - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF0EAREIAAYFAlUlYYQACgkQja8UbcUWM1zpNAD4ofY/zqxLPyNfZ9JRBg3qST6C diZjiYShjO8UvXomhAD+JwiwAKb2wGoGiSMXuqG2eFzc1FD1fw2X+WmICL1cT4g= =maTT -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 04/08/2015 12:27 PM, Carlos E. R. wrote:
On 2015-04-08 18:06, jdd wrote:
Le 08/04/2015 17:58, Carlos E. R. a écrit :
True. But the list doesn't contain data as to what repo to obtain each package from, and that is a problem when we use alternate repos for the same packages.
zypper lr should give a list that ca, be used to include them, isn't it? No. That produces a list of repos. We need a list of packages installed from each repo, separate.
I don't see that as a problem. Go back to the
This will get you a list of package names: rpm -qa --qf "%{NAME}">installed_rpms
Now use that file with a foreach script that runs zypper info on each one. That will tell you repository it came from. Run that output though SED to extract the relevant info and you have the package + repository -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2015-04-08 18:48, Anton Aylward wrote:
On 04/08/2015 12:27 PM, Carlos E. R. wrote:
...
Now use that file with a foreach script that runs
zypper info
on each one. That will tell you repository it came from.
Run that output though SED to extract the relevant info and you have the package + repository
That can take hours to run, provided I could code it. - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlUlYq8ACgkQja8UbcUWM1wnZwEAgMX2WP/uvN55GdpbTUP2W7Gx L1zonjWxqFaA549Cma4A/A8Gc4bXl+tOj2C6u3to/IFcFWpxAjlTXMoyMghXzgeH =0hK8 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Hello, On Wed, 08 Apr 2015, Carlos E. R. wrote:
On 2015-04-08 18:48, Anton Aylward wrote:
On 04/08/2015 12:27 PM, Carlos E. R. wrote: [..] Now use that file with a foreach script that runs
zypper info
on each one. That will tell you repository it came from.
Run that output though SED to extract the relevant info and you have the package + repository
That can take hours to run, provided I could code it.
Try zypper pa -iN | tr -d '|' | \ awk -F' ' '$1 == "i" {printf("%s\t%s\t%s\n", $3, $2, $5); }' (or start with a file for each repo, e.g. 'zypper pa -i -r Packman |...') Or rather: let zypper write a file first and then work on that or those. HTH, -dnh -- If only I'd spent some of that effort on chasing girls. But then, it's much easier to understand a polysubstitution cypher than a female. -- Robert Uhl -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2015-04-09 09:32, David Haller wrote:
Hello,
On Wed, 08 Apr 2015, Carlos E. R. wrote:
That can take hours to run, provided I could code it.
Try
zypper pa -iN | tr -d '|' | \ awk -F' ' '$1 == "i" {printf("%s\t%s\t%s\n", $3, $2, $5); }'
(or start with a file for each repo, e.g. 'zypper pa -i -r Packman |...')
Or rather: let zypper write a file first and then work on that or those.
Interesting... I tried: cer@minas-tirith:~> zypper pa -iN -r Ext_Packman Repository 'Packman Repository' is out-of-date. You can run 'zypper refresh' as root to update it. Loading repository data... Reading installed packages... S | Repository | Name | Version | Arch - --+--------------------+--------------------------------------------+--------------------------------------+------- i | @System | AdobeICCProfiles | 2.0-150.1.6 | noarch i | @System | ConsoleKit | 0.4.5-19.2.1 | x86_64 i | @System | ConsoleKit-32bit | 0.4.5-19.2.1 | x86_64 i | @System | ConsoleKit-x11 | 0.4.5-19.2.1 | x86_64 i | @System | DirectFB | 1.6.3-4.1.3 | x86_64 i | @System | DirectFB-Mesa | 1.6.3-4.1.3 | x86_64 i | @System | GeoIP | 1.5.1-2.1.2 | x86_64 ... i | @System | attr | 2.4.47-2.1.2 | x86_64 i | Packman Repository | audacious | 3.6-3.1 | x86_64 v | Packman Repository | audacious | 3.6-3.1 | i586 i | Packman Repository | audacious-lang | 3.6-3.1 | noarch i | Packman Repository | audacious-plugins | 3.6-2.2 | x86_64 v | Packman Repository | audacious-plugins | 3.6-2.2 | i586 i | Packman Repository | audacious-plugins-extra | 3.6-2.2 | x86_64 v | Packman Repository | audacious-plugins-extra | 3.6-2.2 | i586 i | Packman Repository | audacious-plugins-lang | 3.6-2.2 | noarch i | @System | audiofile | 0.3.6-2.1.2 | x86_64 i | @System | audiofile-devel | 0.3.6-2.1.2 | x86_64 or: cer@minas-tirith:~> zypper pa -iN "Packman Repository" | less Repository 'Packman Repository' is out-of-date. You can run 'zypper refresh' as root to update it. Loading repository data... Reading installed packages... S | Repository | Name | Version | Arch - --+--------------------+--------------------------------------------+--------------------------------------+------- i | @System | AdobeICCProfiles | 2.0-150.1.6 | noarch i | @System | ConsoleKit | 0.4.5-19.2.1 | x86_64 i | @System | ConsoleKit-32bit | 0.4.5-19.2.1 | x86_64 ... i | @System | atk-devel | 2.10.0-1.1 | x86_64 i | @System | attr | 2.4.47-2.1.2 | x86_64 i | Packman Repository | audacious | 3.6-3.1 | x86_64 v | Packman Repository | audacious | 3.6-3.1 | i586 i | Packman Repository | audacious-lang | 3.6-3.1 | noarch It is ignoring the repository in the command line, it lists everything. Well, not everything: whatever it considers "@System", then Packman. Your line with awk produces interesting output: AdobeICCProfiles openSUSE-13.1-Non-Oss noarch ConsoleKit openSUSE-13.1-1.10 x86_64 ConsoleKit openSUSE-13.1-Oss x86_64 ConsoleKit-32bit openSUSE-13.1-1.10 x86_64 ConsoleKit-32bit openSUSE-13.1-Oss x86_64 ConsoleKit-x11 openSUSE-13.1-1.10 x86_64 ConsoleKit-x11 openSUSE-13.1-Oss x86_64 DirectFB openSUSE-13.1-1.10 x86_64 DirectFB openSUSE-13.1-Oss x86_64 DirectFB-Mesa openSUSE-13.1-1.10 x86_64 DirectFB-Mesa openSUSE-13.1-Oss x86_64 ... Repository Packman 2.0.8-4.2 LibreOffice OBS: fh2epub LibreOffice OBS: fh2odg ... devel:languages:pascal OBS 2.6.4-1.1 devel:languages:pascal OBS 2.6.4-1.1 devel:languages:pascal OBS 2.6.4-1.1 It appears to be having problems with repository names with spaces: cer@minas-tirith:~> zypper lr # | Alias | Name | Enabled | Refresh - ---+----------------------------+------------------------------------+---------+-------- 1 | Ext_Packman | Packman Repository | Yes | Yes 2 | Local_RPMs | Local RPMs | Yes | Yes 3 | Local_RPMs_13.1 | Local RPMs 13.1 | Yes | Yes 4 | OBSH_Akoellh | OBSH: Akoellh (blueman) | Yes | Yes 5 | OBSH_Akoellh_update | OBSH: Akoellh updates | Yes | Yes 6 | OBS_KDE_KDE3 | OBS KDE:DE3 | Yes | Yes 7 | OBS_Kernel_vanilla | OBS: Kernel:vanilla | Yes | Yes 8 | OBS_LO_43 | OBS: LibreOffice 4.3 | Yes | Yes 9 | OBS_devel_languages_pascal | OBS devel:languages:pascal | Yes | Yes 10 | OBS_server_mail | OBS: server: mail | Yes | Yes 11 | google-chrome | google-chrome | Yes | Yes 12 | openSUSE-13.1-1.10 | openSUSE-13.1-1.10 | Yes | Yes 13 | opensuse-guide.org-repo | libdvdcss repository | Yes | Yes 14 | repo-debug | openSUSE-13.1-Debug | No | Yes 15 | repo-debug-update | openSUSE-13.1-Update-Debug | No | Yes 16 | repo-debug-update-non-oss | openSUSE-13.1-Update-Debug-Non-Oss | No | Yes 17 | repo-non-oss | openSUSE-13.1-Non-Oss | Yes | Yes 18 | repo-oss | openSUSE-13.1-Oss | Yes | Yes 19 | repo-source | openSUSE-13.1-Source | No | Yes 20 | repo-update | openSUSE-13.1-Update | Yes | Yes 21 | repo-update-non-oss | openSUSE-13.1-Update-Non-Oss | Yes | Yes cer@minas-tirith:~> The command is quite interesting, it can be refined to produce a list of packages related to repos. Maybe for reinstall, or backup/restore, the best thing would be a file per repo, and a line per package. Then another concoction could be fed from that with zypper install to install the correct things from the right places, yes. - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlUmwi4ACgkQja8UbcUWM1zM3wD/VdU7NL0G7Zcy6Ji9+0p3GrCP YdORIEnUU0E3JV4tC3cA/ifQImPn0ORV5AC7tprvqCWZIkyeY4moD4SVvpjlgeLw =sNDU -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Hello, On Thu, 09 Apr 2015, Carlos E. R. wrote:
On 2015-04-09 09:32, David Haller wrote:
zypper pa -iN | tr -d '|' | \ awk -F' ' '$1 == "i" {printf("%s\t%s\t%s\n", $3, $2, $5); }'
(or start with a file for each repo, e.g. 'zypper pa -i -r Packman |...')
Or rather: let zypper write a file first and then work on that or those.
Interesting...
I tried:
cer@minas-tirith:~> zypper pa -iN -r Ext_Packman Repository 'Packman Repository' is out-of-date. You can run 'zypper refresh' as root to update it. Loading repository data... Reading installed packages... S | Repository | Name | Version | Arch - --+--------------------+--------------------------------------------+--------------------------------------+------- i | @System | AdobeICCProfiles | 2.0-150.1.6 | noarch [..] i | Packman Repository | audacious | 3.6-3.1 | x86_64
I suspect that the packages listed under @system are "orphaned" ... Have a look at e.g. what versions of AdobeICCProfiles you have available in your repos (e.g. in Yast in the version tab). At least, here, it works, with 'zypper pa -iN -r packman' I do not get any @system packages, just "packman' ones. How about checking about orphaned and if not, open a bug ...
Your line with awk produces interesting output:
AdobeICCProfiles openSUSE-13.1-Non-Oss noarch ConsoleKit openSUSE-13.1-1.10 x86_64 [...] Repository Packman 2.0.8-4.2 LibreOffice OBS: fh2epub LibreOffice OBS: fh2odg [..] It appears to be having problems with repository names with spaces:
Yeah, I chose spaces as field seperator, as using '|' gave those wide spacefilled fields. Just as a "stop-gap" measure, needing some "space-pruning" later, just use "|" as seperator. This looks good: head -20 /tmp/dh/zypper-pa.txt | \ awk -F'|' ' $1 ~ /^i/ { gsub(" ", "", $0); printf("%s\t%s\t%s\n", $3, $2, $5); }' (That'll waste your inner spaces in repos though, using head -20 /tmp/dh/zypper-pa.txt | \ awk -F'|' ' $1 ~ /^i/ { gsub(" ", "", $3); gsub("^ *", "", $2); gsub(" *$", "", $2); gsub(" ", "", $5); printf("%s\t%s\t%s\n", $3, $2, $5); }' should work though.
cer@minas-tirith:~> zypper lr # | Alias | Name | Enabled | Refresh - ---+----------------------------+------------------------------------+---------+-------- 1 | Ext_Packman | Packman Repository | Yes | Yes
I generally edit my /etc/zypp/repos.d/*.repo files to get sane repo names ;) Some (home) repos have _reeaaaaallly_ long "names" ... e.g. name=Printing System Development Project (openSUSE_12.1) The "actual" name (also in the OBS-URL is simply "Printing"), and I usually use just that repo-name part from the URL, possibly exchanging ':' with '_' or not ;)
The command is quite interesting, it can be refined to produce a list of packages related to repos.
Jep. Some tweaks might be required (and I'm not sure if the ARCH is even relevant).
Maybe for reinstall, or backup/restore, the best thing would be a file per repo, and a line per package. Then another concoction could be fed from that with zypper install to install the correct things from the right places, yes.
Yeah, command-line length might be a problem though, but installing "by repo" won't work anyway, I'd guess, so 'in --force' might be needed anyway, so you could do that for the repos and than do a complete 'zypper dup' to clean up or so ;) Or you could just sort and diff those 'zypper pa' files and do it manually :) HTH, -dnh -- BOFH excuse #438: sticky bit has come loose -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2015-04-09 22:24, David Haller wrote:
On Thu, 09 Apr 2015, Carlos E. R. wrote:
I suspect that the packages listed under @system are "orphaned" ...
No, there are 4972 such packages, including yast components. They are not orphaned.
Have a look at e.g. what versions of AdobeICCProfiles you have available in your repos (e.g. in Yast in the version tab). At least, here, it works, with 'zypper pa -iN -r packman' I do not get any @system packages, just "packman' ones. How about checking about orphaned and if not, open a bug ...
Maybe because "packman" doesn't have a space in the name. In my setup it does: cer@minas-tirith:~> zypper lr # | Alias | Name | Enabled | Refresh - ---+----------------------------+------------------------------------+---------+-------- 1 | Ext_Packman | Packman Repository | Yes | Yes - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlUnAPgACgkQja8UbcUWM1yR1AD/d79lpp4nh6CV8Z4PnVP6RBq6 grrh1JUII4wVgYOvwHsA/AhNfsHqbguaHpwb6UAXS1DE0HnymkCuh6zzHJtgjX7n =w/mH -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Hello, On Fri, 10 Apr 2015, Carlos E. R. wrote:
On 2015-04-09 22:24, David Haller wrote:
On Thu, 09 Apr 2015, Carlos E. R. wrote: [..] I suspect that the packages listed under @system are "orphaned" ...
No, there are 4972 such packages, including yast components. They are not orphaned.
Ok.
Have a look at e.g. what versions of AdobeICCProfiles you have available in your repos (e.g. in Yast in the version tab). At least, here, it works, with 'zypper pa -iN -r packman' I do not get any @system packages, just "packman' ones. How about checking about orphaned and if not, open a bug ...
Maybe because "packman" doesn't have a space in the name. In my setup it does:
cer@minas-tirith:~> zypper lr # | Alias | Name | Enabled | Refresh - ---+----------------------------+------------------------------------+---------+-------- 1 | Ext_Packman | Packman Repository | Yes | Yes
But you called 'zypper pa -r Packman_Ext' (didn't you, so no spaces)... And anyway, I think it's a bug in either case. In the meantime, a 'grep -v @system' is not that hard as a workaround, eh? :) -dnh -- The chat program is in public domain. This is not the GNU public license. If it breaks then you get to keep both pieces. (Copyright notice for the chat program) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2015-04-10 01:37, David Haller wrote:
Hello,
On Fri, 10 Apr 2015, Carlos E. R. wrote:
Maybe because "packman" doesn't have a space in the name. In my setup it does:
cer@minas-tirith:~> zypper lr # | Alias | Name | Enabled | Refresh - ---+----------------------------+------------------------------------+---------+--------
1 | Ext_Packman | Packman Repository | Yes | Yes
But you called 'zypper pa -r Packman_Ext' (didn't you, so no spaces)...
True, but that's the alias, not the name.
And anyway, I think it's a bug in either case.
Seems so.
In the meantime, a 'grep -v @system' is not that hard as a workaround, eh? :)
I'll probably, time allowing, write something to convert the full output to a comma separated list, which can be imported to a calc sheet and studied. Or further filtered to produce useful output for reinstallation, dunno. The output is peculiar, anyway. - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlUpqBsACgkQja8UbcUWM1zBzAD/Yn7N2tpg2oXHGkMiY4m6en8t Kt1KwuSDnuzFXKqQgEsA/38D40Ui1UwsBruSDCAZ5NmCSo9l6P8QCzvKydum95rB =fLtK -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 04/07/2015 08:25 PM, Michael J Dur wrote:
Hi Don, You can query the rpm db.
This will get you a list of package names: rpm -qa --qf "%{NAME} ">installed_rpms
Then you could put this on your new system and run something like: zypper in $(cat installed_rpms)
-Michael
I have looked at the zypper manpage and cannot fine a unique definition for zypper in. There appears to be 'info' and 'install', both starting with in. I thought ar was used to add repositories. Please clarify before I make a mess of things. Sorry, Don -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Wed, 8 Apr 2015 19:10, don fisher wrote:
On 04/07/2015 08:25 PM, Michael J Dur wrote:
Hi Don, You can query the rpm db.
This will get you a list of package names: rpm -qa --qf "%{NAME} ">installed_rpms
Then you could put this on your new system and run something like: zypper in $(cat installed_rpms)
-Michael
I have looked at the zypper manpage and cannot fine a unique definition for zypper in. There appears to be 'info' and 'install', both starting with in. I thought ar was used to add repositories. Please clarify before I make a mess of things.
"zypper help" gives you a short overview of the commands, just a snippet here: Software Management: install, in Install packages. ... Querying: search, se Search for packages matching a pattern. info, if Show full information for specified packages. install == in info == if - Yamaban -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 04/08/2015 10:10 AM, don fisher wrote:
I have looked at the zypper manpage and cannot fine a unique definition for zypper in. There appears to be 'info' and 'install', both starting with in. I thought ar was used to add repositories. Please clarify before I make a mess of things.
Sorry, Don
Thanks, "in" not clear from the manpage. I did not bother to look at help when the manpage was before me. I was following the update repos thread as well as the install the rpms thread. I still cannot find a reference to zypper ca being used to install the repos listed in the output of zypper lr. Sorry for becoming crossed. Don -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2015-04-08 19:37, don fisher wrote:
I still cannot find a reference to zypper ca being used to install the repos listed in the output of zypper lr. Sorry for becoming crossed.
You can restore the repo list by restoring the directory "/etc/zypp/repos.d/". - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlUluhwACgkQja8UbcUWM1ynNQD+P4O7dMhs/ZxQ/AHZSm65sI4V RS8PCpN1gk+5NGMpGacA/AnOhbTk0IdVYUxHJKzpc80ZGzkhmPkA3ssOSm/Twxcr =7sSd -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (7)
-
Anton Aylward -
Carlos E. R. -
David Haller -
don fisher -
jdd -
Michael J Dur -
Yamaban