Fwd: Re: [opensuse] cloning 15.0 to 15.1
On 7/22/19 2:14 AM, jdd@dodin.org wrote:
Hello,
I know some recent discussion where held in this list (I presume) on similar subject, but don't remember a solution.
I have on a computer a working 15.0 install.
I just (yesterday) install 15.1 on an other partition.
is there a way to recover from the 15.0 a list of *main applications* (without libraries and dependencies) I could apply to the new 15.1?
could be like the manually selected apps on 15.0, for example
thanks jdd
This probably won't do, but fwiw . . . in Yast2 software management, you can create a text file from any package list that you create. (Right-click on the list, "Export this list ...") Any grouping that you can create - e.g., system, repository, group, pattern, status, search (including regular expressions and wild card), etc. Of course you would need a script to strip out the unwanted. --dg -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 22/07/2019 17.32, DennisG wrote:
On 7/22/19 2:14 AM, jdd@dodin.org wrote:
Hello,
I know some recent discussion where held in this list (I presume) on similar subject, but don't remember a solution.
I have on a computer a working 15.0 install.
I just (yesterday) install 15.1 on an other partition.
is there a way to recover from the 15.0 a list of *main applications* (without libraries and dependencies) I could apply to the new 15.1?
could be like the manually selected apps on 15.0, for example
This probably won't do, but fwiw . . . in Yast2 software management, you can create a text file from any package list that you create. (Right-click on the list, "Export this list ...") Any grouping that you can create - e.g., system, repository, group, pattern, status, search (including regular expressions and wild card), etc. Of course you would need a script to strip out the unwanted.
That's interesting, did not know that. The problem is that that file lacks repository info. Ie, this package was installed from this repo. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
On 7/22/19 1:13 PM, Carlos E. R. wrote:
On 22/07/2019 17.32, DennisG wrote:
On 7/22/19 2:14 AM, jdd@dodin.org wrote:
... This probably won't do, but fwiw . . . in Yast2 software management, you can create a text file from any package list that you create. (Right-click on the list, "Export this list ...") Any grouping that you can create - e.g., system, repository, group, pattern, status, search (including regular expressions and wild card), etc. Of course you would need a script to strip out the unwanted. That's interesting, did not know that.
The problem is that that file lacks repository info. Ie, this package was installed from this repo.
Right. I'm curious if there is a data store somewhere on the system where each package is associated with the providing repo; a program could correlate that with the list(s). Of course, if that there is such a store, it may just be easier to create the list(s) from there directly. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 22/07/2019 19.47, DennisG wrote:
On 7/22/19 1:13 PM, Carlos E. R. wrote:
On 22/07/2019 17.32, DennisG wrote:
On 7/22/19 2:14 AM, jdd@dodin.org wrote:
... This probably won't do, but fwiw . . . in Yast2 software management, you can create a text file from any package list that you create. (Right-click on the list, "Export this list ...") Any grouping that you can create - e.g., system, repository, group, pattern, status, search (including regular expressions and wild card), etc. Of course you would need a script to strip out the unwanted. That's interesting, did not know that.
The problem is that that file lacks repository info. Ie, this package was installed from this repo.
Right. I'm curious if there is a data store somewhere on the system where each package is associated with the providing repo; a program could correlate that with the list(s). Of course, if that there is such a store, it may just be easier to create the list(s) from there directly.
Yes, I have that in my notes. ------- zypper, list of packages installed from a repository cer@Telcontar:~> zypper --no-refresh se -s -i -r OBS_Emulators_Wine Loading repository data... Reading installed packages... S | Name | Type | Version | Arch | Repository ---+------------------+---------+---------------------+--------+--------------------- i | libFAudio0-32bit | package | 19.03-lp150.1.1 | x86_64 | OBS: Emulators: Wine i+ | wine | package | 4.9-lp150.1004.2 | x86_64 | OBS: Emulators: Wine i+ | wine-32bit | package | 4.9-lp150.1004.2 | x86_64 | OBS: Emulators: Wine i+ | wine-gecko | package | 2.47-lp150.55.1 | noarch | OBS: Emulators: Wine i+ | wine-mono | package | 4.7.1-lp150.1.1 | noarch | OBS: Emulators: Wine i+ | winetricks | package | 20190310-lp150.14.2 | x86_64 | OBS: Emulators: Wine cer@Telcontar:~> comma separated list cer@Telcontar:~> zypper --no-refresh se -s -i -r OBS_Emulators_Wine | sed 's/ *| */,/g' Loading repository data... Reading installed packages... S,Name,Type,Version,Arch,Repository ---+------------------+---------+---------------------+--------+--------------------- i,libFAudio0-32bit,package,19.03-lp150.1.1,x86_64,OBS: Emulators: Wine i+,wine,package,4.9-lp150.1004.2,x86_64,OBS: Emulators: Wine i+,wine-32bit,package,4.9-lp150.1004.2,x86_64,OBS: Emulators: Wine i+,wine-gecko,package,2.47-lp150.55.1,noarch,OBS: Emulators: Wine i+,wine-mono,package,4.7.1-lp150.1.1,noarch,OBS: Emulators: Wine i+,winetricks,package,20190310-lp150.14.2,x86_64,OBS: Emulators: Wine cer@Telcontar:~> ------------ You would have to repeat the query for each repository. Maybe another concoction would produce the full list, but I don't have that in my notes. This seems to work: zypper --no-refresh se -s -i Obtaining the list per repository would allow to concoct a complex zypper install list of packages from several repos. The list as produced above would not be it, has to be edited to include only names. zypper install -r "repository" long list of packages. I do not see how to include something like "list --from repo other_list --from another_repo" Might need --force. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
* Carlos E. R. <robin.listas@telefonica.net> [07-22-19 14:13]:
On 22/07/2019 19.47, DennisG wrote:
On 7/22/19 1:13 PM, Carlos E. R. wrote:
On 22/07/2019 17.32, DennisG wrote:
On 7/22/19 2:14 AM, jdd@dodin.org wrote:
... This probably won't do, but fwiw . . . in Yast2 software management, you can create a text file from any package list that you create. (Right-click on the list, "Export this list ...") Any grouping that you can create - e.g., system, repository, group, pattern, status, search (including regular expressions and wild card), etc. Of course you would need a script to strip out the unwanted. That's interesting, did not know that.
The problem is that that file lacks repository info. Ie, this package was installed from this repo.
Right. I'm curious if there is a data store somewhere on the system where each package is associated with the providing repo; a program could correlate that with the list(s). Of course, if that there is such a store, it may just be easier to create the list(s) from there directly.
Yes, I have that in my notes.
------- zypper, list of packages installed from a repository
cer@Telcontar:~> zypper --no-refresh se -s -i -r OBS_Emulators_Wine Loading repository data... Reading installed packages...
S | Name | Type | Version | Arch | Repository ---+------------------+---------+---------------------+--------+--------------------- i | libFAudio0-32bit | package | 19.03-lp150.1.1 | x86_64 | OBS: Emulators: Wine i+ | wine | package | 4.9-lp150.1004.2 | x86_64 | OBS: Emulators: Wine i+ | wine-32bit | package | 4.9-lp150.1004.2 | x86_64 | OBS: Emulators: Wine i+ | wine-gecko | package | 2.47-lp150.55.1 | noarch | OBS: Emulators: Wine i+ | wine-mono | package | 4.7.1-lp150.1.1 | noarch | OBS: Emulators: Wine i+ | winetricks | package | 20190310-lp150.14.2 | x86_64 | OBS: Emulators: Wine cer@Telcontar:~>
comma separated list
cer@Telcontar:~> zypper --no-refresh se -s -i -r OBS_Emulators_Wine | sed 's/ *| */,/g' Loading repository data... Reading installed packages...
S,Name,Type,Version,Arch,Repository ---+------------------+---------+---------------------+--------+--------------------- i,libFAudio0-32bit,package,19.03-lp150.1.1,x86_64,OBS: Emulators: Wine i+,wine,package,4.9-lp150.1004.2,x86_64,OBS: Emulators: Wine i+,wine-32bit,package,4.9-lp150.1004.2,x86_64,OBS: Emulators: Wine i+,wine-gecko,package,2.47-lp150.55.1,noarch,OBS: Emulators: Wine i+,wine-mono,package,4.7.1-lp150.1.1,noarch,OBS: Emulators: Wine i+,winetricks,package,20190310-lp150.14.2,x86_64,OBS: Emulators: Wine cer@Telcontar:~>
------------
You would have to repeat the query for each repository. Maybe another concoction would produce the full list, but I don't have that in my notes.
This seems to work:
zypper --no-refresh se -s -i
Obtaining the list per repository would allow to concoct a complex zypper install list of packages from several repos. The list as produced above would not be it, has to be edited to include only names.
zypper install -r "repository" long list of packages.
I do not see how to include something like "list --from repo other_list --from another_repo"
Might need --force.
zypper se -si -r 1 -r 2 -r 3 ... > list.txt -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 El 2019-07-22 a las 18:21 -0400, Patrick Shanahan escribió:
* Carlos E. R. <> [07-22-19 14:13]:
On 22/07/2019 19.47, DennisG wrote:
On 7/22/19 1:13 PM, Carlos E. R. wrote:
On 22/07/2019 17.32, DennisG wrote:
On 7/22/19 2:14 AM, jdd@dodin.org wrote:
...
...
You would have to repeat the query for each repository. Maybe another concoction would produce the full list, but I don't have that in my notes.
This seems to work:
zypper --no-refresh se -s -i
Obtaining the list per repository would allow to concoct a complex zypper install list of packages from several repos. The list as produced above would not be it, has to be edited to include only names.
zypper install -r "repository" long list of packages.
I do not see how to include something like "list --from repo other_list --from another_repo"
Might need --force.
zypper se -si -r 1 -r 2 -r 3 ... > list.txt
No, zypper install. Man does not say this is supported. - -- Cheers Carlos E. R. (from openSUSE 15.0 (Legolas)) -----BEGIN PGP SIGNATURE----- iHoEARECADoWIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCXTZZ/hwccm9iaW4ubGlz dGFzQHRlbGVmb25pY2EubmV0AAoJELUzGBxtjUfVS/8AnAtpfU3xpVCEMGIS7J6d G1gkYqk+AJ9OWVMYRjHN2zOP0GmNvBz3X6nMPg== =U1IW -----END PGP SIGNATURE-----
* Carlos E. R. <robin.listas@telefonica.net> [07-22-19 20:53]:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
El 2019-07-22 a las 18:21 -0400, Patrick Shanahan escribió:
* Carlos E. R. <> [07-22-19 14:13]:
On 22/07/2019 19.47, DennisG wrote:
On 7/22/19 1:13 PM, Carlos E. R. wrote:
On 22/07/2019 17.32, DennisG wrote:
On 7/22/19 2:14 AM, jdd@dodin.org wrote: > ...
...
You would have to repeat the query for each repository. Maybe another concoction would produce the full list, but I don't have that in my notes.
This seems to work:
zypper --no-refresh se -s -i
Obtaining the list per repository would allow to concoct a complex zypper install list of packages from several repos. The list as produced above would not be it, has to be edited to include only names.
zypper install -r "repository" long list of packages.
I do not see how to include something like "list --from repo other_list --from another_repo"
Might need --force.
zypper se -si -r 1 -r 2 -r 3 ... > list.txt
No, zypper install. Man does not say this is supported.
- -- Cheers Carlos E. R.
(from openSUSE 15.0 (Legolas))
-----BEGIN PGP SIGNATURE-----
iHoEARECADoWIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCXTZZ/hwccm9iaW4ubGlz dGFzQHRlbGVmb25pY2EubmV0AAoJELUzGBxtjUfVS/8AnAtpfU3xpVCEMGIS7J6d G1gkYqk+AJ9OWVMYRjHN2zOP0GmNvBz3X6nMPg== =U1IW -----END PGP SIGNATURE-----
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
no, it provides a list of what is installed and from what repo. you can then use the list to install from particular repos. much easier, alter/edit your 15.0 repos to point to 15.1 and "dup". -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
El 2019-07-22 a las 18:21 -0400, Patrick Shanahan escribió:
* Carlos E. R. <> [07-22-19 14:13]:
On 22/07/2019 19.47, DennisG wrote:
On 7/22/19 1:13 PM, Carlos E. R. wrote: > On 22/07/2019 17.32, DennisG wrote: >> On 7/22/19 2:14 AM, jdd@dodin.org wrote: >>> ...
...
You would have to repeat the query for each repository. Maybe another concoction would produce the full list, but I don't have that in my notes.
This seems to work:
zypper --no-refresh se -s -i
Obtaining the list per repository would allow to concoct a complex zypper install list of packages from several repos. The list as produced above would not be it, has to be edited to include only names.
zypper install -r "repository" long list of packages.
I do not see how to include something like "list --from repo other_list --from another_repo"
Might need --force.
zypper se -si -r 1 -r 2 -r 3 ... > list.txt
No, zypper install. Man does not say this is supported.
no, it provides a list of what is installed and from what repo.
you can then use the list to install from particular repos.
No, it doesn't. As I read the manual, if you give several repos to install from in the command line, it will do solving, not directly install from that one. zypper install --from repo1 pkg1 pkg2 pkg3 --from repo2 pkg4 pkg5 pkg6 This syntax doesn't do what it would seem. At least that is what I understand from the manual.
much easier, alter/edit your 15.0 repos to point to 15.1 and "dup".
That is not the intention. It may work, but it is not what we are trying to do. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
* Carlos E. R. <robin.listas@telefonica.net> [07-23-19 06:26]:
El 2019-07-22 a las 18:21 -0400, Patrick Shanahan escribió:
* Carlos E. R. <> [07-22-19 14:13]:
On 22/07/2019 19.47, DennisG wrote: > On 7/22/19 1:13 PM, Carlos E. R. wrote: >> On 22/07/2019 17.32, DennisG wrote: >>> On 7/22/19 2:14 AM, jdd@dodin.org wrote: >>>> ...
...
You would have to repeat the query for each repository. Maybe another concoction would produce the full list, but I don't have that in my notes.
This seems to work:
zypper --no-refresh se -s -i
Obtaining the list per repository would allow to concoct a complex zypper install list of packages from several repos. The list as produced above would not be it, has to be edited to include only names.
zypper install -r "repository" long list of packages.
I do not see how to include something like "list --from repo other_list --from another_repo"
Might need --force.
zypper se -si -r 1 -r 2 -r 3 ... > list.txt
No, zypper install. Man does not say this is supported.
no, it provides a list of what is installed and from what repo.
you can then use the list to install from particular repos.
No, it doesn't. As I read the manual, if you give several repos to install from in the command line, it will do solving, not directly install from that one.
zypper install --from repo1 pkg1 pkg2 pkg3 --from repo2 pkg4 pkg5 pkg6
This syntax doesn't do what it would seem. At least that is what I understand from the manual.
I don't know what you are twisting this into. break the generated list by repo, feed each repo separately to zypper, *not* as you described above. zypper in --from $repo < <repo.file.list>
much easier, alter/edit your 15.0 repos to point to 15.1 and "dup".
That is not the intention. It may work, but it is not what we are trying to do.
aiui, the intention was to duplicate a 15.0 system with 15.1 packages and that will do *exactly* that. forest != trees you are making it more difficult/complicated than it needs to be. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 23/07/2019 13.32, Patrick Shanahan wrote:
* Carlos E. R. <> [07-23-19 06:26]:
El 2019-07-22 a las 18:21 -0400, Patrick Shanahan escribió:
* Carlos E. R. <> [07-22-19 14:13]: > On 22/07/2019 19.47, DennisG wrote: >> On 7/22/19 1:13 PM, Carlos E. R. wrote: >>> On 22/07/2019 17.32, DennisG wrote: >>>> On 7/22/19 2:14 AM, jdd@dodin.org wrote: >>>>> ...
...
> You would have to repeat the query for each repository. Maybe another concoction would produce the full list, but I don't have that in my notes. > > This seems to work: > > zypper --no-refresh se -s -i > > > Obtaining the list per repository would allow to concoct a complex zypper install list of packages from several repos. The list as produced above would not be it, has to be edited to include only names. > > zypper install -r "repository" long list of packages. > > I do not see how to include something like "list --from repo other_list --from another_repo" > > > Might need --force. >
zypper se -si -r 1 -r 2 -r 3 ... > list.txt
No, zypper install. Man does not say this is supported.
no, it provides a list of what is installed and from what repo.
you can then use the list to install from particular repos.
No, it doesn't. As I read the manual, if you give several repos to install from in the command line, it will do solving, not directly install from that one.
zypper install --from repo1 pkg1 pkg2 pkg3 --from repo2 pkg4 pkg5 pkg6
This syntax doesn't do what it would seem. At least that is what I understand from the manual.
I don't know what you are twisting this into. break the generated list by repo, feed each repo separately to zypper, *not* as you described above. zypper in --from $repo < <repo.file.list>
That is exactly what I have been saying from the start.
much easier, alter/edit your 15.0 repos to point to 15.1 and "dup".
That is not the intention. It may work, but it is not what we are trying to do.
aiui, the intention was to duplicate a 15.0 system with 15.1 packages and that will do *exactly* that.
No. The OP said he wanted a new install to remove cruft and correct errors. He refused this method.
forest != trees you are making it more difficult/complicated than it needs to be.
-- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
I just think of a completely different way to get what I need. Several, in fact. It's matter of knowing what applications are installed, to compare them to a completely new/default install. But applications are: * installed in some places like /opt, /usr/share * have they main binary in *bin* folders so there are the lists we need. probably the *bin* is the best because all the other can be found by dependency check. then * use a script (find?) to list all the apps on the source computer > text file * do the same on the target computer > other text file diff the two text file to find new stuff, ask zypper to see which is in official repos, may be also ask obs to see what is there jdd -- http://dodin.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 07/22/2019 12:47 PM, DennisG wrote:
On 7/22/19 1:13 PM, Carlos E. R. wrote:
On 22/07/2019 17.32, DennisG wrote:
On 7/22/19 2:14 AM, jdd@dodin.org wrote:
... This probably won't do, but fwiw . . . in Yast2 software management, you can create a text file from any package list that you create. (Right-click on the list, "Export this list ...") Any grouping that you can create - e.g., system, repository, group, pattern, status, search (including regular expressions and wild card), etc. Of course you would need a script to strip out the unwanted. That's interesting, did not know that.
The problem is that that file lacks repository info. Ie, this package was installed from this repo.
Right. I'm curious if there is a data store somewhere on the system where each package is associated with the providing repo; a program could correlate that with the list(s). Of course, if that there is such a store, it may just be easier to create the list(s) from there directly.
I've never really seen this as a problem. Maybe I'm missing something like that you may have some package installed from /repositories/publishing instead of OSS and that is what you are trying to capture.... For me, I only have a dozen or less repos enabled, so it is trivial to just install a base system and rsync -a oldbox:/etc/zypp/repos.c newbox:/etc/zypp and then just take a saved package list created with: rpm -qa --queryformat "%{name}\n" | sort > list and then reinstall the whole list with: zypper in --no-recommends $(awk -vORS=" " '{print}' list) zypper may say has "package xyz doesn't exist" for the new release, then just delete that from the list and run it again. (note if your package list exceeds 2097152 chars, then pass the list through xargs -- doubtful you will) I'll try some of the other approaches that Patrick, dnh, etc.. have recommended, but I've not had a problem with this approach in many many moons. -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Hello, On Tue, 23 Jul 2019, David C. Rankin wrote:
rpm -qa --queryformat "%{name}\n" | sort > list
useless use of sort ;)
and then reinstall the whole list with:
zypper in --no-recommends $(awk -vORS=" " '{print}' list)
useless use of awk (that *I* say so ... *ugh* ;) zypper in --no-recommends $(< somefile ) or probably better: zypper in rpm libzypp zypper zypper in --no-recommends $(grep -v -e zypper -e libzypp -e rpm somefile)
zypper may say has "package xyz doesn't exist" for the new release, then just delete that from the list and run it again.
(note if your package list exceeds 2097152 chars,
Or rather: exceeds $(getconf ARG_MAX) chars ;)
then pass the list through xargs -- doubtful you will)
Probably not: rpm -qa --qf '%{name}\n' | wc 5679 5679 83254 But pruning libs from that list is probably a good idea, as you might end up with a lot of orphaned libs when a package once needed libfoo1 and now libfoo2 you'd end up with both instead of just libfoo2. So, starting from apps/binaries and omitting libs might be an idea. HTH, -dnh -- "Love is putting someone else's happiness before your own." -- unknown -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 23/07/2019 08.49, David Haller wrote:
But pruning libs from that list is probably a good idea, as you might end up with a lot of orphaned libs when a package once needed libfoo1 and now libfoo2 you'd end up with both instead of just libfoo2. So, starting from apps/binaries and omitting libs might be an idea.
Except that you are letting zypper choose the repo it gets the lib from, which may not be what you want. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
On 23/07/2019 07.23, David C. Rankin wrote:
On 07/22/2019 12:47 PM, DennisG wrote:
On 7/22/19 1:13 PM, Carlos E. R. wrote:
On 22/07/2019 17.32, DennisG wrote:
On 7/22/19 2:14 AM, jdd@dodin.org wrote:
... This probably won't do, but fwiw . . . in Yast2 software management, you can create a text file from any package list that you create. (Right-click on the list, "Export this list ...") Any grouping that you can create - e.g., system, repository, group, pattern, status, search (including regular expressions and wild card), etc. Of course you would need a script to strip out the unwanted. That's interesting, did not know that.
The problem is that that file lacks repository info. Ie, this package was installed from this repo.
Right. I'm curious if there is a data store somewhere on the system where each package is associated with the providing repo; a program could correlate that with the list(s). Of course, if that there is such a store, it may just be easier to create the list(s) from there directly.
I've never really seen this as a problem. Maybe I'm missing something like that you may have some package installed from /repositories/publishing instead of OSS and that is what you are trying to capture....
Certainly.
For me, I only have a dozen or less repos enabled, so it is trivial to just install a base system and rsync -a oldbox:/etc/zypp/repos.c newbox:/etc/zypp and then just take a saved package list created with:
rpm -qa --queryformat "%{name}\n" | sort > list
and then reinstall the whole list with:
zypper in --no-recommends $(awk -vORS=" " '{print}' list)
No. That will simply install a package that exists in two repos from the one with higher priority, not necessarily from the same repo it was on the original installation. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
participants (6)
-
Carlos E. R. -
David C. Rankin -
David Haller -
DennisG -
jdd＠dodin.org -
Patrick Shanahan