On 09/06/2019 01.40, David C. Rankin wrote:

On 06/08/2019 05:48 PM, Patrick Shanahan wrote:

...

I am considering wiping my main system drive and reinstalling Tw clean but would like to have the same packages on the new system. I will backup home and replace the new home contents with the backedup data.

is this feasible?

how to save the currently installed pkgs for reinstall?

and yes, btrfs for entire system.

thoughts?

tks,

Save the list of current packages installed, e.g. open an xterm and:

$ rpm -qa --queryformat "%{name}\n" | sort > installed_pkgs.txt

You now have all the package names saved in installed_pkgs.txt. Then when you load your new system, after your base install is done, you can simply open a terminal and (optionally delete the cruft from installed_pkgs.txt), then

# zypper in --no-recommends $(awk -vORS=" " '{print}' installed_pkgs.txt)

As long as you only use the default repositories. Any extra, and the result is unpredictable. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)

On 09/06/2019 10.43, Per Jessen wrote:

Patrick Shanahan wrote:

...

I am considering wiping my main system drive and reinstalling Tw clean but would like to have the same packages on the new system. I will backup home and replace the new home contents with the backedup data.

is this feasible?

how to save the currently installed pkgs for reinstall?

You can save a list - YaST->Software Managment->Extras->Export package list. (I presume there is a zypper incantation too). It can be imported during installation. Unfortunately the list does not include banned packages which make it slightly less useful, but ignoring that, it's very useful.

This will generate a list of installed packages from a particular 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:~> Same with 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:~> From this we could separate the package list using "cut -d"," -f2", and then repeat for each repository we have defined: for REPOS in repo1 repo2 repo3 do zypper --no-refresh se -s -i -r $REPOS > $REPOS.raw.packagelist cat $REPOS.raw.packagelist | sed 's/ *| */,/g' | cut -d"," -f2 > $REPOS.packagelist done Another zypper command could install that list (modifying the one from David): zypper in $(awk -vORS=" " '{print}' installed_pkgs.txt) --repo OBS_Emulators_Wine or another "for" to repeat for each repo. There is a doubt about whether the command line buffer will take the entire package list, I think there is a limit (64K?). Can a zypper take input from a file directly? All that untested. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sunday, 2019-06-09 at 11:47 +0200, Per Jessen wrote:

Carlos E. R. wrote:

...

There is a doubt about whether the command line buffer will take the entire package list, I think there is a limit (64K?). Can a zypper take input from a file directly?

if not, xargs will help you issue multiple zypper in, at optimal length.

No, that has a problem: not having the entire list of packages may break the solver case. It will not consider everything in order to solve dependencies, and may want to bring other different packages to solve the needs. - -- Cheers, Carlos E. R. (from openSUSE 15.0 x86_64 at Telcontar) El 2019-06-09 a las 11:47 +0200, Per Jessen escribió: -----BEGIN PGP SIGNATURE----- iHoEARECADoWIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCXPzZwBwccm9iaW4ubGlz dGFzQHRlbGVmb25pY2EubmV0AAoJELUzGBxtjUfVCuMAn0OTGkHqPu21qdBoA9h8 4Sd1w6uWAJ96VlR02XFPjSgSOsOOwW5+hfkQWw== =FROS -----END PGP SIGNATURE-----

On 09/06/2019 12.56, Per Jessen wrote:

Carlos E. R. wrote:

...

On Sunday, 2019-06-09 at 11:47 +0200, Per Jessen wrote:

...

Carlos E. R. wrote:

...

There is a doubt about whether the command line buffer will take the entire package list, I think there is a limit (64K?). Can a zypper take input from a file directly?

if not, xargs will help you issue multiple zypper in, at optimal length.

No, that has a problem: not having the entire list of packages may break the solver case. It will not consider everything in order to solve dependencies, and may want to bring other different packages to solve the needs.

I'm not sure that is a real issue. You would face the same problem doing it manually. Nothing much there can be done if your package list exceeds 2Mb - still, even at 40 chars per package, that's 50000+ packages :-)

Yeah, I thought the limit was still 64KB. I need double than that. But at 2MB limit, no problem. The theoretical issue was that the missing dependency could be solved by packages that go in the next split command line. By feeding the complete command line there should not be dependencies issues, if the release is the same. On upgrades there could be problems. I mean, the goal is to have the same list of packages, to solve the dependencies with the same solution as the original installation did. A clone as far as possible. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sunday, 2019-06-09 at 05:10 -0500, David C. Rankin wrote:

On 06/09/2019 04:47 AM, Per Jessen wrote:

...

Carlos E. R. wrote:

...

There is a doubt about whether the command line buffer will take the entire package list, I think there is a limit (64K?). Can a zypper take input from a file directly?

if not, xargs will help you issue multiple zypper in, at optimal length.

Good catch and call from both Carlos and Per:

The limitation is an OS provided limitation on the character limit for the command line. You can check with:

$ getconf ARG_MAX 2097152

Ah. Didn't know that. At sometime in the past it was 64KB.

So there is a 2 Megabyte limit to your command line on 42.3. If you exceed that than pass the list through xargs which will break up the command line into subsets that do not exceed ARG_MAX.

Which may result in dependency hell. A switch to not verify dependencies would be needed, plus another run to solve pending dependencies later.

Given my install has a huge number of development libraries, matching -devel, -debug and 32-bit packages installed and I only have 78K for all chars in all package names, it would be hard to see how somebody could have 26X times more packages installed than I do -- but who know??

The point is you should always check, e.g.

-rw-r--r-- 1 david david 78467 Jun 8 18:31 423install-name.txt

rpm -qa --queryformat "%{name}\n" | sort > installed_pkgs.txt cer@Telcontar:~> l installed_pkgs.txt - -rw-r--r-- 1 cer users 136554 Jun 9 12:17 installed_pkgs.txt cer@Telcontar:~> Way more than you, but still under the limit. Wait, we need to count the spaces. Ah, no, because new lines are removed. - -- Cheers, Carlos E. R. (from openSUSE 15.0 x86_64 at Telcontar) -----BEGIN PGP SIGNATURE----- iHoEARECADoWIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCXPzeNBwccm9iaW4ubGlz dGFzQHRlbGVmb25pY2EubmV0AAoJELUzGBxtjUfVaiAAoJgut9Yyuee6fgvkkUfw KrEY6o6sAJwJ78BMaRZRAz0TgnNsN5o8We0iGQ== =nb/k -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 09/06/2019 15.06, David C. Rankin wrote:

On 06/09/2019 05:23 AM, Carlos E. R. wrote:

...

cer@Telcontar:~> l installed_pkgs.txt -rw-r--r-- 1 cer users 136554 Jun 9 12:17 installed_pkgs.txt cer@Telcontar:~>

Way more than you, but still under the limit. Wait, we need to count the spaces. Ah, no, because new lines are removed.

Right, and remember right now I have my installed shoehorned into a VM (except that 423 is on a 500M SSD). It would be interesting to know who has the largest package name install (talk about an rpm hog!) and then see if it comes close to the character limit.

I remember someone that clicked on "install all" (yast1?) and then asked on the list because things did not work :-D -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)

Le 09/06/2019 à 15:06, David C. Rankin a écrit :

On 06/09/2019 05:23 AM, Carlos E. R. wrote:

...

cer@Telcontar:~> l installed_pkgs.txt -rw-r--r-- 1 cer users 136554 Jun 9 12:17 installed_pkgs.txt cer@Telcontar:~>

Way more than you, but still under the limit. Wait, we need to count the spaces. Ah, no, because new lines are removed.

best should be to know the list of *main* packages (excluding all dependencies), minus default packages always installed, just to complete the install but anyway this shouldn't cope with manual installs like brother drivers and so on. jdd -- http://dodin.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 09/06/2019 11.57, Dave Howorth wrote:

On Sun, 09 Jun 2019 10:43:43 +0200 Per Jessen <> wrote:

...

Patrick Shanahan wrote:

...

I am considering wiping my main system drive and reinstalling Tw clean but would like to have the same packages on the new system. I will backup home and replace the new home contents with the backedup data.

is this feasible?

how to save the currently installed pkgs for reinstall?

You can save a list - YaST->Software Managment->Extras->Export package list.

There's no such menu entry under YaST->Software Managment->Extras on my system? Leap 15.0

I see it under "File". -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)

On 09/06/2019 13.36, Dave Howorth wrote:

On Sun, 9 Jun 2019 12:52:27 +0200 "Carlos E. R." <> wrote:

...

...

...

You can save a list - YaST->Software Managment->Extras->Export package list.

There's no such menu entry under YaST->Software Managment->Extras on my system? Leap 15.0

I see it under "File".

I do see YaST->Software Managment->File->Export yes, thanks. That saves the list as XML, which doesn't seem so helpful for the OP's purpose. The XML file is apparently intended for use with AutoYaST.

Yes, it is intended for autoyast. When I tried it years ago, it did not save repository information, thus not useful for most cases. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)

On 6/9/19 2:36 PM, Dave Howorth wrote:

YaST->Software Managment->File->Export

 my TW :  don't have : YaST->Software Managment->File->Export  - just YaST->Software Managment , but without ->File->Export ..... thanks YaST->Software Managment->File->Export -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

ellanios82 wrote:

On 6/9/19 11:43 AM, Per Jessen wrote:

...

You can save a list - YaST->Software Managment->Extras->Export package list

- on my TW , Yast does not have Extras [ under Software Management ] - any ideas 'what extra' Yast package needs to be installed?

That's weird - see attached. -- Per Jessen, Zürich (16.6°C) http://www.cloudsuisse.com/ - your owncloud, hosted in Switzerland.