On Thu, Jul 2, 2015 at 11:31 AM, ellanios82 wrote:

How to Save the output of rpm -qa : as a Text-file ??

rpm -qa > Text-file -- 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-07-02 10:31, ellanios82 wrote:

Hello List ,

Can one Save the output of|rpm -qa|of the present running system as the input for|zypper

Yes, sure.

- then , in the event of a system crash , needing a complete re-install :

what please is the Syntax for instruction to Zypper to install the saved reserve output of rpm -qa

I haven't tried, but I don't think the syntax is the same. You could feed zypper a single line with package names, whereas rpm prints a line at a time. But you could generate that with a simple script. By the way, YaST does have this functionality. You can export the list of packages to a file, and later import it. Directly. The real problem is different: you need a list of rpms separated by exact repository, in order to tell zypper what exact repo to use for reinstalling each package. YaST also fails in this respect: the exported list misses all repository info. - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF0EAREIAAYFAlWVCdkACgkQja8UbcUWM1zoJwD4gi3Fx4kkhHT+G8bq4c3rcmFT lhqRBiV+ZTDiFwuIPgD8Dje9zn9OpcUmof9KoPCoQiy+RMxWUAh96UCaP8owOss= =nepV -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 07/02/2015 11:42 AM, Andrei Borzenkov wrote:

On Thu, Jul 2, 2015 at 11:31 AM, ellanios82 wrote:

...

...

How to Save the output of rpm -qa : as a Text-file ??

rpm -qa > Text-file .

................ and , how please Andrei , can i feed that Text file into Zypper , to achieve re-install? thanks regards -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 07/02/2015 12:38 PM, Anton Aylward wrote:

On 07/02/2015 04:31 AM, ellanios82 wrote:

...

Hello List ,

Can one Save the output of rpm -qa of the present running system as the input for zypper

............

- then , in the event of a system crash , needing a complete re-install :

what please is the Syntax for instruction to Zypper to install the saved reserve output of rpm -qa You mean something like the procedure described in this article

http://www.cyberciti.biz/tips/linux-get-list-installed-software-reinstallati... ...............

- thanks , Anton - is it so that the recipe for re-install is ?? : zypper install `cat /backup/installed-software.log | tr "\n" " "` ................... thanks regards -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 07/02/2015 01:38 PM, Carlos E. R. wrote:

The link posted tells a trick to remove versions strings from the output:

rpm -qa --qf "%{NAME}\n" | sort > /backup/installed-software.log

(you should learn about pipes and redirection: it is a fundamental feature of the command line. Generating a text file the way shown above is not a feature of "rpm", but of Linux. Any CLI Linux program can do that.) ...............

many thanks , Carlos - what please is the correct Incantation to instruct Zypper to re-install ?? : - something like ??: zypper install `cat zypper install `cat /backup/installed-software.log` .......... regards -- 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-07-02 12:48, ellanios82 wrote:

On 07/02/2015 01:38 PM, Carlos E. R. wrote:

- what please is the correct Incantation to instruct Zypper to re-install ?? :

I don't know, I would have to try. Perhaps xargs -a rpmlistfile zypper install You will probably have to add -n. See the man page. However, why not use YaST? It has this functionality built in. - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlWVHSYACgkQja8UbcUWM1x22QD6A6P5xo7FIVlhOG8p9TZ79+hg HAN23j7BVdv4f8dIzxYA/jfIU1BWKqEUtjIHwlupLG/7HXmF986oXYQuFnX8YtgQ =3WV/ -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 07/02/2015 02:14 PM, Carlos E. R. wrote:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256

On 2015-07-02 12:48, ellanios82 wrote:

...

On 07/02/2015 01:38 PM, Carlos E. R. wrote:

...

- what please is the correct Incantation to instruct Zypper to re-install ?? : I don't know, I would have to try.

Perhaps

xargs -a rpmlistfile zypper install

You will probably have to add -n. See the man page.

However, why not use YaST? It has this functionality built in.

................ - thanks : where inside Yast should i look to find this function ? regards -- 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-07-02 13:22, ellanios82 wrote:

- this must be basic housekeeping knowledge

Nope. I have never seen a plain and good and tested procedure. There is autoyast, though. There is (was?) yast bacup/restore, which uses autoyast somewhat. But I repeat and insist: it does not take into account repositories. - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlWVJBcACgkQja8UbcUWM1zB/QD/d6TG3ZdyjXNCP9xJ284k6+0c cXcoMw9xTc4rUNlT0L4A/iTNzvZ//bOzrNUO3uh5UiKobYviGvKX2ZtB1BwDPH7K =wQEQ -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

* Carlos E. R. [07-02-15 07:42]:

On 2015-07-02 13:25, ellanios82 wrote:

...

- thanks : where inside Yast should i look to find this function ?

Somewhere in package management, export package list.

But I repeat: neither method caters for repositories.

But it would be a simple matter to add a file in addition to the package list containing: /etc/zypp/locks and /etc/zypp/repos.d/* And you have all needed to recreate a system. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 07/02/2015 07:22 AM, ellanios82 wrote:

Because recovery from a system crash is such a hard experience ,

When I've had a catastrophic crash, that is a completely unrecoverable disk fatality, I use it s an excuse to install a completely new system, an upgrade. Apart from a backup of /home and /srv, my key backup is all the config in /etc. There are very few programs outside the regular set I use and those are well noted. Backing up the RPM database and the thread we've been feeding you, which I think has been adequate for those of us who have responded, but we can't tell your level of technical expertise in these matters, is not an approach I would bother with. I can see it, yes; I can see the point of it yes; but Its not a path I'd follow because my set of "other" programs is dictated more by the extra repositories I have. Backing up the list of repositories is simpler. We've been assuming, probably based on your previous posts, that you have a basic technical knowledge. That last post of min with the rpm command that produced both name and url can be used in a simple shell script that read the two elements on each line and uses them as parameters to zypper. This is shell programming 101. ============================= Now let me go into "Consulting mode" and rather than answer the question as you asked it, try to solve the problem you have that so far you haven't actually described, only hinted at. You talk of a "system crash" without saying what has actually happened. Of you have certain classes of "crash" then its to late to extract anything from the ROM database unless you happen to have a full backup of same and another system on which to restore/extract it. So why don't you describe to us in as much detail as you can what happened, what the 'system crash' amounts to. Perhaps there is some other avenue you can pursue that we might think of. =========================== I must say that backing up the RPM database and the matching URLs as per my last message is a novel idea. I might just do that :-) -- 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

On 07/02/2015 07:51 AM, ellanios82 wrote:

On 07/02/2015 02:44 PM, Carlos E. R. wrote:

...

On 2015-07-02 13:22, ellanios82 wrote:

...

...

- this must be basic housekeeping knowledge Nope. I have never seen a plain and good and tested procedure.

---

- seems to me , that it will be Valuable asset for some knowledgeable expert to craft a script , for Zypper to Restore the stored output from

rpm -qa > text-file

{ zypper knows its enabled repositories }

Is that because you backed up the list of repositories (presumably along with the rest of /etc and all the other configuration items?) No, really. Given the data file, this is shell programming 101. I wouldn't even bother with a script, I do it as a single line of shell. And others have covered that earlier in this thread so I don't know why you are belabouring the point. -- 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-07-02 13:45, Anton Aylward wrote:

On 07/02/2015 07:41 AM, Carlos E. R. wrote:

...

But I repeat: neither method caters for repositories.

which gets back to my version of the 'rpm -qa' that includes the URL.

?? Let me see. cer@minas-tirith:~> rpm -qa --qf "%{NAME}\t%{DISTURL}\n" libdrm_nouveau2 obs://build.opensuse.org/openSUSE:13.1/standard/6e54f61ac4b419fd5831dd2e921b58a2-libdrm libgcrypt11-32bit obs://build.opensuse.org/openSUSE:Maintenance:2961/openSUSE_13.1_Update/ea4836cd9a2de039535ba5953f4c6c6e-libgcrypt.openSUSE_13.1_Update texlive-concrete obs://build.opensuse.org/openSUSE:13.1/standard/397f03548a1a456670144b62d4f3a860-texlive-specs-c geoclue2 obs://build.opensuse.org/openSUSE:13.1/standard/55d6a9b4d9b23fff26cba462d60a60ae-geoclue2 insserv-compat obs://build.opensuse.org/openSUSE:13.1/standard/aa3b56cb41311f3ba5d5a17b1cda2e68-insserv-compat texlive-present obs://build.opensuse.org/openSUSE:13.1/standard/136172f0ea6b3aeab091105d2d7420de-texlive-specs-p libzvbi0 obs://build.opensuse.org/openSUSE:13.1/standard/cd43bd20adb415691841f5e64ab7b7b2-zvbi libmysqlcppconn6 obs://build.opensuse.org/LibreOffice:4.3/openSUSE_13.1/09ac97b520741f43c52499496cca81cb-mysql-connector-cpp texlive-latexpand obs://build.opensuse.org/openSUSE:Maintenance:2684/openSUSE_13.1_Update/b025d425835eed128df649cd9099d982-texlive-specs-l.openSUSE_13.1_Update libva-x11-1 obs://build.opensuse.org/openSUSE:13.1/standard/09ba04452bea1f3dc5fe864a42e25b45-libva It is not an http URL. I don't know where those hashes come from. If the package version changes an iota, the URL maybe is not valid. I don't see how to feed that to zypper... We need a method that lists packages from each repository. I have been told of a method: zypper se -si --sort-by-repo ... S | Name | Type | Version | Arch | Repository - --+--------------------------------------------+---------+--------------------------------------+--------+----------------------------- i | handbrake-cli | package | 0.10.1-2.13 | x86_64 | (System Packages) i | libxmmsclient6 | package | 0.8-2.123 | x86_64 | (System Packages) i | libxmmsclient-glib1 | package | 0.8-2.123 | x86_64 | (System Packages) i | libbellesip0 | package | 1.4.0-11.9 | x86_64 | (System Packages) i | xmms2-plugin-base | package | 0.8-2.123 | x86_64 | (System Packages) i | handbrake-gtk | package | 0.10.1-2.13 | x86_64 | (System Packages) i | xmms2 | package | 0.8-2.123 | x86_64 | (System Packages) i | ffmpeg2theora | package | 0.29-2.100 | x86_64 | (System Packages) i | xine-ui | package | 0.99.9-50.16 | x86_64 | (System Packages) i | webpin | package | 1.2.4-2.1 | noarch | (System Packages) i | wifi-radar | package | 2.0.s08-2.1 | noarch | (System Packages) i | wtf | package | 20071004-2.1 | noarch | Local RPMs i | cgrep | package | 8.15-2.1 | x86_64 | Local RPMs 13.1 i | pstotext | package | 1.9-1.1 | x86_64 | Local RPMs 13.1 i | trickle | package | 1.07-9.1 | x86_64 | Local RPMs 13.1 i | xpdf | package | 3.03-6.1 | x86_64 | Local RPMs 13.1 i | fpc-doc | package | 2.6.4-1.1 | x86_64 | OBS devel:languages:pascal i | fpc | package | 2.6.4-1.1 | x86_64 | OBS devel:languages:pascal i | libQt4Pas5 | package | 2.5-1.1 | x86_64 | OBS devel:languages:pascal i | fpc-src | package | 2.6.4-1.1 | x86_64 | OBS devel:languages:pascal i | lazarus | package | 1.4.0-1.1 | x86_64 | OBS devel:languages:pascal i | ktranslator | package | 0.4-83.16 | x86_64 | OBS KDE:DE3 i | rekall | package | 2.4.6-118.17 | x86_64 | OBS KDE:DE3 i | rekall-examples | package | 2.4.6-118.17 | x86_64 | OBS KDE:DE3 i | rekall-mysql | package | 2.4.6-118.17 | x86_64 | OBS KDE:DE3 i | rekall-sqlite | package | 2.4.6-118.17 | x86_64 | OBS KDE:DE3 i | rekall-xbase | package | 2.4.6-118.17 | x86_64 | OBS KDE:DE3 i | libvisual-32bit | package | 0.4.0-393.1 | x86_64 | OBS KDE:DE3 i | cdr2epub | package | 0.9.2-2.1 | x86_64 | OBS: LibreOffice 4.3 i | cdr2odg | package | 0.9.2-2.1 | x86_64 | OBS: LibreOffice 4.3 i | cmx2epub | package | 0.9.2-2.1 | x86_64 | OBS: LibreOffice 4.3 i | cmx2odg | package | 0.9.2-2.1 | x86_64 | OBS: LibreOffice 4.3 i i | openSUSE-2015-446 | patch | 1 | noarch | openSUSE-13.1-Update i | openSUSE-2015-443 | patch | 1 | noarch | openSUSE-13.1-Update i | openSUSE-2015-447 | patch | 1 | noarch | openSUSE-13.1-Update i | openSUSE-2015-451 | patch | 1 | noarch | openSUSE-13.1-Update i | flash-player | package | 11.2.202.468-123.1 | x86_64 | openSUSE-13.1-Update-Non-Oss i | flash-player-gnome | package | 11.2.202.468-123.1 | x86_64 | openSUSE-13.1-Update-Non-Oss i | openSUSE-2013-624 | patch | 1 | noarch | openSUSE-13.1-Update-Non-Oss i | openSUSE-2013-689 | patch | 1 | noarch | openSUSE-13.1-Update-Non-Oss i | openSUSE-2013-879 | patch | 1 | noarch | openSUSE-13.1-Update-Non-Oss This is not usable right away: it lists patches, many packages appear listed as from (System Packages), whatever that is. We could filter on type packages (-t). But even then... you have to script it a lot. There is no rpm command that lists all the rpms and the repository they came from, because the rpm command doesn't know anything about repositories. That's is zypper/yast/apper labor. And zypper does not produce a list in an usable manner; not that I know. - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlWVKC8ACgkQja8UbcUWM1xz7AD/acJjyoCPyU5js3zieGwWNIGz FAngg8Tl/2ER1AAjbuEBAJAs6mSCddhOEX2jx9qOKQT1jjVQWoeqRrVPesfFq2MV =EQyW -----END PGP SIGNATURE----- -- 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-07-02 13:58, ellanios82 wrote:

zypper knows its enabled repositories

So? You get it to print the list, then tell me how to do it ;-) - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlWVKbcACgkQja8UbcUWM1zoEwD/d8Rl0wGzcQinia1Fv7L/QhpB 3WJpV8prsyY5HrW+5boBAIMGXlQ9YNPzz4TQyGKdUIJ/f4CntAK+B4c+TYrp1GHl =FXHj -----END PGP SIGNATURE----- -- 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-07-02 13:56, ellanios82 wrote:

Particularly for Recovery from system crash :

That's what yast backup/restore attempted. - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlWVKw4ACgkQja8UbcUWM1yfeAD9Ef4pWRe263NFznwzoz7jzP6O /Vu+N7kZISeTEOSb2wgA/384WBeSKRSFr9Qr+KEbGFNXN6oaT+TRPl29nIc1dbdr =UwC9 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 07/02/2015 03:12 PM, Carlos E. R. wrote:

What we need is a method to reinstall the same list of packages, and each from the same repository it was installed previously. ...................

just for simplicity : if one runs openSuSE Tumbleweed , then there are only THREE repositories ................... regards -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 07/02/2015 03:27 PM, Carlos E. R. wrote:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256

On 2015-07-02 14:17, ellanios82 wrote:

...

just for simplicity :

if one runs openSuSE Tumbleweed , then there are only THREE repositories In that case, just use yast. It will work.

I'm assuming you mean OSS, NON-OSS, and updates.

If one of the repos is packman or any other thing, it will not work. .................

- yes yes : just those 3 repos : thus , if some expert like Anton could provide a single line of Shell to strip stuff out of 'rpm-qa > text,file' leaving a long list of package-names only separated by a Space , then : with just 3 repos , "zypper install text.file" should work like a charm? ................... regards -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 07/02/2015 08:01 AM, Carlos E. R. wrote:

I don't see how to feed that to zypper...

RTFM man zyyper says <quote> install (in) [options] ... ..... -r, --repo Work only with the repository specified by the alias, name, number or URI. This option can be used multiple times. </quote> and <quote> Zypper also accepts special URIs identifying openSUSE Build Service (OBS) repositories in the addrepo command. These URIs have the form of obs://<project>/[platform], where project is the name of the OBS project and platform is the target platform (OS) for which the repository is in </quote> -- 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

* Carlos E. R. [07-02-15 08:04]: [...]

This is not usable right away: it lists patches, many packages appear listed as from (System Packages), whatever that is. We could filter on type packages (-t). But even then... you have to script it a lot.

"System Packages" would be those packages or pckage versions that do not currently exist in your enabled repos, ie: zypper search does not find a repo containing "package". -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 07/02/2015 08:27 AM, Carlos E. R. wrote:

On 2015-07-02 14:17, ellanios82 wrote:

...

just for simplicity :

...

if one runs openSuSE Tumbleweed , then there are only THREE repositories

In that case, just use yast. It will work.

I'm assuming you mean OSS, NON-OSS, and updates.

If one of the repos is packman or any other thing, it will not work.

Or if you have a special interests such as mine in photography and add repos for items that aren't in the main ones or want "bleeding edge' updates, then no, its not just those three. YMMV. Mine does. -- 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-07-02 15:25, Patrick Shanahan wrote:

* Carlos E. R. [07-02-15 08:04]: [...]

...

This is not usable right away: it lists patches, many packages appear listed as from (System Packages), whatever that is. We could filter on type packages (-t). But even then... you have to script it a lot.

"System Packages" would be those packages or pckage versions that do not currently exist in your enabled repos, ie: zypper search does not find a repo containing "package".

But it is not true. I verified. The list contains hundreds of packages as "system" which are in fact available on some of the configured repo. It may be, though, that the installed version has disappeared from the repos, which now have a somewhat more recent version. I have not verified this, it just occurred to me. - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlWVTP8ACgkQja8UbcUWM1yU0gD+O0H4yEbsVXdkKR5Ids17kHTG CXTMYEr+5V2ba5OrA2oA/it0igFsZERrv6KkAGMoQqXD7Od+D05+orfb8gZzdhAe =mXYk -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On Thu, Jul 2, 2015 at 8:45 AM, Carlos E. R. wrote:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256

On 2015-07-02 15:54, Anton Aylward wrote:

...

On 07/02/2015 08:15 AM, Carlos E. R. wrote:

...

On 2015-07-02 13:57, Anton Aylward wrote:

...

No, really. Given the data file, this is shell programming 101. I wouldn't even bother with a script, I do it as a single line of shell. And others have covered that earlier in this thread so I don't know why you are belabouring the point.

No, I do not know how to do it properly. I have been trying to figure it out for some years.

Don't be silly, Carlos, you've already answered that with xargs.

You miss one very important detail: repos.

I'll explain it with an example.

Suppose I installed "xine".

Suppose I run the sequence to reinstall all. So I tell zypper to install "xine". Zypper will chose, on its own, whether to install from oss or packman, based on some criteria of its own (probably the priority).

However, this will not do! I absolutely want xine to be installed from the same repo as it was installed previously!

Now you tell me how to produce an exact list of all the packages installed from, say, packman. Or rather, to produce several lists, one per repo, of all packages. Or some variant of the above.

I hate how packaging injects its deficiencies into users' lives like this, it's a real hamper on productivity. Even OS X and Windows have packages, different kinds of packaging systems (3rd party stuff for example) but none of it slaps the user in the face and demands the kind of attention and knowledge required like is necessary on Linux. It really drives me crazy. It's totally workable with default repos but as soon as I start adding 3rd party repos, it rapidly turns into a mess. Stateless systems is what we need. Android has it. Windows 8 has it. iOS has it. It's just somehow the old sclerotic types who insist on Linux on the desktop being encumbered with ancient ideas that are now really inconvenient for those who just want a free/libre OS that just works, because we have work to do, rather than learning esoteric nonsense about how computers work. -- Chris Murphy -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 07/02/2015 07:51 PM, Carlos E. R. wrote:

to the issue the OP posed. ..........................

- In the matter of Simplicity , perhaps , having just 3 basic Repos , it is a Plus-Point for Tumbleweed ................ regards -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On Thu, Jul 2, 2015 at 10:51 AM, Carlos E. R. wrote:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256

On 2015-07-02 18:12, Chris Murphy wrote:

...

On Thu, Jul 2, 2015 at 8:45 AM, Carlos E. R. <> wrote:

...

...

Now you tell me how to produce an exact list of all the packages installed from, say, packman. Or rather, to produce several lists, one per repo, of all packages. Or some variant of the above.

I hate how packaging injects its deficiencies into users' lives like this, it's a real hamper on productivity. Even OS X and Windows have packages, different kinds of packaging systems (3rd party stuff for example) but none of it slaps the user in the face and demands the kind of attention and knowledge required like is necessary on Linux. It really drives me crazy. It's totally workable with default repos but as soon as I start adding 3rd party repos, it rapidly turns into a mess.

No, I can not agree.

If one has to install or reinstall Windows, from scratch, not from an OEM recovery partition, one has to first install Windows, then start chasing on different web sites for the drivers for different pieces of hardware in the board or attached externally to it (say, video, sound, printer, etc), then start chasing other web sites to download the software you need (say java, flash, acrobat, vlc, firefox, moby, libreoffice). Some of the "packages" will need one to validate existing licenses or buy and pay new ones. Say, for instance, the antivirus.

It can take days!

This can still be ugly in certain cases, but it's immensely better with Windows 8.1 than previously. The recovery partition reset is not to be casually discarded, nor the refresh feature of Windows 8.1 which returns the system to a near factory state while keeping user data and settings intact. That alone is vastly better than anything we currently have with any Linux desktop distro. The functional equivalent of reset is the same as on Android and iOS. If you have a branded system (Dell, HP, ASUS), it's a matter of plugging in a service tag into their web site, and you get all the recommended drivers for that system to download. Why would you ever need this? If you want an unbranded Windows installation, which is now possible: http://windows.microsoft.com/en-us/windows-8/create-reset-refresh-media I've done this and the whole thing takes maybe an hour or two. Not days. Macs have clean installs totally idiot proof. But there is no statelessness, no reset or refresh like Windows. Nor a reset like iOS.

In Linux, and specifically with openSUSE, you can download everything using a single program (say zypper, or yast, or apper), and from a single site; even when choosing external sites, the downloads and installations are handled by that single program.

In Windows, to keep it updated, one has to again chase different sites, download and install, separately. With some applications, those applications check for updates the instant they run, and apply them, but not always in a fully automatic manner.

No single application for updating it all.

That's true. GNOME Software has made this a lot easier as a user facing way of doing it.

But anyway, this has no relation at all to the issue the OP posed.

Ok well it sounded like there was a complaint about how to determine the current and previous state of a system so it can be replicated/restored on that system or some other system. -- Chris Murphy -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On Thu, Jul 2, 2015 at 3:26 PM, Carlos E. R. wrote:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256

On 2015-07-02 20:18, Chris Murphy wrote:

...

On Thu, Jul 2, 2015 at 10:51 AM, Carlos E. R. <> wrote:

...

...

It can take days!

This can still be ugly in certain cases, but it's immensely better with Windows 8.1 than previously. The recovery partition reset is not to be casually discarded,

Having a recovery partition (which is an old trick) is cheating.

Why? It's how Windows has been installed itself for years now. Even if you aren't using the OEM utility, and use Microsoft's installer on today's UEFI computers, you get a recovery partition. It's not cheating, it's how the OS works by default.

You can not compare installing Linux to installing Windows if one of them is installed from scratch and the other from an image.

I can compare them. One is closer to a stateless system, the other isn't. It's a completely fair comparison when discussion how OS's should be installed, and reset.

And I have heard of recovery partitions in machines sold with SLED, from HP I believe.

All users should have this option, not just people buying HP computers.

...

nor the refresh feature of Windows 8.1 which returns the system to a near factory state while keeping user data and settings intact. That alone is vastly better than anything we currently have with any Linux desktop distro.

You have something similar, even more powerful, with btrfs snapshots.

It is certainly going in the right direction. It's not as simple as just having two options: full reset (obliterate everything except the OS), vs system refresh (clean up temporary files and most user and system settings, keep user data). But Windows NTFS has had shadow copy snapshots for quite a while also, so they've been doing system update rollbacks for a long time now.

...

The functional equivalent of reset is the same as on Android and iOS.

But you need a third party app, like AppMgr III, to then recover all your previously installed apps, which is what the OP wants.

It is a matter of granularity that needs improvement. At least on my Cyanogenmod phone, apps I've installed are separate from the OS, so I can to major OS upgrades and rollbacks by changing that OS image, without having to reinstall apps or user data. But there isn't sufficient granularity between non-OS apps I've downloaded and my data.

...

If you have a branded system (Dell, HP, ASUS), it's a matter of plugging in a service tag into their web site, and you get all the recommended drivers for that system to download.

You do not need that in Linux, as all the drivers are distributed in the kernel. But if you did, why don't those brands do the same with Linux?

I don't understand the question.

...

I've done this and the whole thing takes maybe an hour or two. Not days.

And will it install for you the video driver, the printer driver, nero, the TomTom drive, java, flash, firefox, thunderbird, libreoffice, etc? Sure? With a single reboot?

Windows, no that's probably 8 reboots. OS X yes, and if its in the app store then you also get all of those things updated automatically. Again, GNOME Software makes this quite a bit better. The one thing I don't like are offline updates, where by it reboots to do the update and then reboots again after the update. Even Windows and OS X on OS updates close out the current user session, perform the update, then reboot once. So this could be better right now. Going forward: Btrfs snapshots + containers to get an atomic "offline" update with a user defined reboot when it's convenient for them. This would look like: 1. Create container 2. Launch updates daemon 3. Updater snapshots the file system and downloads updates. 4. Applies updates to the snapshot and cleans up. 5. User is notified there are system updates and to reboot when convenient to take advantage. 6. On reboot, the subvolumes containing the updated system is booted. So this way the software update is completely atomic rather than updating a live in-use system and libraries. So in use things are just yanked out from under running programs. The update can completely implode spectacularly badly and yet, the current system is totally unaffected, it could even crash the container and things would be OK. To clean up, simply automatically delete the bad snapshots. And very nicely one reboot only. And at the users discretion. We're not too far from this. -- Chris Murphy -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On Thu, Jul 2, 2015 at 7:50 PM, Carlos E. R. wrote:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256

On 2015-07-03 01:59, Chris Murphy wrote:

...

On Thu, Jul 2, 2015 at 3:26 PM, Carlos E. R. <> wrote:

...

...

Having a recovery partition (which is an old trick) is cheating.

Why? It's how Windows has been installed itself for years now.

No. That's mot installing Windows, that's restoring a backup image, made by the people that made the computer. You have no say in what to install, you have to accept the choices made by somebody else.

Well this is just a b.s. argument over what constitutes "installing Windows". Using your logic, numerous Linux distro live CD weren't really installing Linux either because they were using dd to copy an ext4 image to the drive, and then resizing the file system after copying, and finally fixing up some configuration files. This still used the distros installer app, as when packages are installed to a new file system. I don't buy the distinction between them at all. They're both installations of an OS. And I already pointed out that Microsoft provides a generic Windows installer. You give Microsoft the OEM software key and Microsoft will provide a download for their decrapified Windows installer. So you get exclusively Microsoft's choice in software, rather than the OEM. It's hardly any different than, again, the bundled apps that a live Linux distro chooses for you. In either case you can choose to uninstall them after installation.

And anyway, talking about Windows "advantages" is not interesting to the OP or this list.

It isn't a Windows advantages commentary. It's the advantage of stateless systems, with Windows as one of the examples that you just happen to be fussing over more than the others. -- Chris Murphy -- 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-07-03 12:56, Florian Gleixner wrote:

Easiest way is to create a autoyast profile from your running system. Install autoyast2 and then run

yast2 clone_system

Does it generate info to know to install different packages from different repositories? Because the YaST feature that exports/imports the package list does not.

Another handy tool is yast2 support. Install yast2-support and navigate to "support" in yast2. then create a support-tarball. This contains many information you may want to review if your system has been reinstalled.

Intriguing. I have to try this. Thanks for the idea. - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlWWbSAACgkQja8UbcUWM1yBfgEAk4qZ40SmLxgCd9k5Ibz0aa6B /AOsQqxCezXXIG5psLkA/izgGAHDrtz7iyrC4XcBUSuxg0O0KMSemHKkNO4R0oyo =/5Ne -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 07/03/2015 01:56 PM, Florian Gleixner wrote:

On 07/02/2015 10:31 AM, ellanios82 wrote:

...

Hello List ,

Can one Save the output of|rpm -qa|of the present running system as the input for|zypper

............

- then , in the event of a system crash , needing a complete re-install :

what please is the Syntax for instruction to Zypper to install the saved reserve output of rpm -qa

&

How to Save the output of rpm -qa : as a Text-file ??

thanks

regards ellan

|

Easiest way is to create a autoyast profile from your running system. Install autoyast2 and then run

yast2 clone_system

It takes some time and then you have a xml: /root/autoinst.xml which contains not only rpm packages but also partition/filesystem layout, system settings, network settings and much more.

Documentation is here:

https://www.suse.com/documentation/sles11/singlehtml/book_autoyast/book_auto...

If you reinstall the system, you have to feed the installer with the autoyast xml file.

Another handy tool is yast2 support. Install yast2-support and navigate to "support" in yast2. then create a support-tarball. This contains many information you may want to review if your system has been reinstalled. ...............

- this is most Valuable : thank you so much regards ellan -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

ellanios82 wrote:

On 07/03/2015 01:56 PM, Florian Gleixner wrote:

...

If you reinstall the system, you have to feed the installer with the autoyast xml file.

...................

the Installer ..................

- is this the Distribution ISO Installer ?? - what page of ISO installer screen contains autoyast.xml input field ??

One place is the command line (kernel arguments, linuxrc arguments): autoyast=tftp://hostname/ay/mirage-autoinst.xml I'm sure the usual schemes work, e.g. ftp://, http://, file:/// -- Per Jessen, Zürich (32.9°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

ellanios82 wrote:

On 07/03/2015 04:47 PM, Per Jessen wrote:

...

ellanios82 wrote:

...

On 07/03/2015 01:56 PM, Florian Gleixner wrote:

...

If you reinstall the system, you have to feed the installer with the autoyast xml file. ...................

the Installer ..................

- is this the Distribution ISO Installer ?? - what page of ISO installer screen contains autoyast.xml input field ?? One place is the command line (kernel arguments, linuxrc arguments):

autoyast=tftp://hostname/ay/mirage-autoinst.xml

I'm sure the usual schemes work, e.g. ftp://, http://, file:///

...........

Thanks Per [ i am afraid my knowledge is too 'Junior' to understand :( ]

. . . am i to flame-up my LIVE usb stick opensuse . . . then open Konsole , mount my other usb stick containing autoinst.xml

and ,

, at the CLI write :

autoyast=/mnt/sdd1[my-usb-stick]/autoinst.xml

Hi Ellan I am not sure this will work with a LIVE stick or CD. With a normal installer CD/stick, right at the beginning when you boot the installer and you have the menu options "Harddisk, Install, Rescue etcetera", you can add options. Same place where you would add "init S" or "install=http:// or "nomodeset" and all of those. /Per -- Per Jessen, Zürich (34.0°C) http://www.dns24.ch/ - free dynamic DNS, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Thank you very much Florian : terrific : "Easiest way is to create a autoyast profile from your running system. Install autoyast2 and then run yast2 clone_system It takes some time and then you have a xml: /root/autoinst.xml which contains not only rpm packages but also partition/filesystem layout, system settings, network settings and much more." Documentation : https://www.suse.com/documentation/sles11/singlehtml/book_autoyast/book_auto... ................ regards -- 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-07-02 20:01, Anton Aylward wrote:

On 07/02/2015 10:45 AM, Carlos E. R. wrote:

...

Now you tell me how to produce an exact list of all the packages installed from, say, packman. Or rather, to produce several lists, one per repo, of all packages. Or some variant of the above.

I've already given the code for producing a two-column listing, the name of the package and the URL it came from.

It's an URL to obs:, not the repository name nor alias. From the sample I posted previously:

cer@minas-tirith:~> rpm -qa --qf "%{NAME}\t%{DISTURL}\n" libdrm_nouveau2 obs://build.opensuse.org/openSUSE:13.1/standard/6e54f61ac4b419fd5831dd2e921b58a2-libdrm

libgcrypt11-32bit obs://build.opensuse.org/openSUSE:Maintenance:2961/openSUSE_13.1_Update/ea4836cd9a2de039535ba5953f4c6c6e-libgcrypt.openSUSE_13.1_Update

texlive-concrete obs://build.opensuse.org/openSUSE:13.1/standard/397f03548a1a456670144b62d4f3a860-texlive-specs-c

geoclue2 obs://build.opensuse.org/openSUSE:13.1/standard/55d6a9b4d9b23fff26cba462d60a60ae-geoclue2

insserv-compat obs://build.opensuse.org/openSUSE:13.1/standard/aa3b56cb41311f3ba5d5a17b1cda2e68-insserv-compat

texlive-present obs://build.opensuse.org/openSUSE:13.1/standard/136172f0ea6b3aeab091105d2d7420de-texlive-specs-p

libzvbi0 obs://build.opensuse.org/openSUSE:13.1/standard/cd43bd20adb415691841f5e64ab7b7b2-zvbi

libmysqlcppconn6 obs://build.opensuse.org/LibreOffice:4.3/openSUSE_13.1/09ac97b520741f43c52499496cca81cb-mysql-connector-cpp

texlive-latexpand obs://build.opensuse.org/openSUSE:Maintenance:2684/openSUSE_13.1_Update/b025d425835eed128df649cd9099d982-texlive-specs-l.openSUSE_13.1_Update

libva-x11-1 obs://build.opensuse.org/openSUSE:13.1/standard/09ba04452bea1f3dc5fe864a42e25b45-libva

Its a trivial latter to sort on the second filed.

No, it is not. I would have to extract the repository name from those randomly ugly looking urls.

You then have a number of ways you can get the result you ask for. One is to split the file manually according to the grouping of that second field.

yeah, trivial:

texlive-latexpand obs://build.opensuse.org/openSUSE:Maintenance:2684/openSUSE_13.1_Update/b025d425835eed128df649cd9099d982-texlive-specs-l.openSUSE_13.1_Update

openSUSE_13.1_Update

libmysqlcppconn6 obs://build.opensuse.org/LibreOffice:4.3/openSUSE_13.1/09ac97b520741f43c52499496cca81cb-mysql-connector-cpp LibreOffice:4.3 sigh...

Another is to use a small awk script to do the grouping.

I know not awk. :-} And... the repo name here, its "OBS: LibreOffice 4.3", and the alias is "OBS_LO_43", not "LibreOffice:4.3", so I would have to do translations in order to issue the proper "zypper install from list" command.

Mapping back from the URI that the RPM database knows about to the takes a but of thought.

All that is a concoction that is forced because neither zypper nor rpm are capable of directly printing the repository name, and we have to work around creating our own complex code to do it. ...

It may even be that, on mature systems that have had many updates to the same packages over time there are different "Maintenance" references. That is certainly the case on my system, where I have been running 'zypper up' every week since 13.1 was installed, a couple of months after its release.

For practical purposes, updates and oss are the same repo. Or the same "vendor", rather. In fact, what I would do if I were to work on this, is an rpm query, relating vendors to repositories. - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlWXDpgACgkQja8UbcUWM1wB4wD9HrNzUYbbK2SYNz0CmXZgvJTA TezFxrtSnoZVCKb60FwA/RAL9f0huF5aJd7eNASJgaLYpryhDxP+U2JVSqX/7qMx =n5z3 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 07/03/2015 06:37 PM, Carlos E. R. wrote:

All that is a concoction that is forced because neither zypper nor rpm are capable of directly printing the repository name, and we have to work around creating our own complex code to do it.

In absolute terms you statement is true. In practical terms it is irrelevant. The issue isn't the name of the repository, its about being able to reinstall a crashed system. As I pointed out, zypper deals with a URI and the OBS" based results is a perfectly valid URI as far as zypper is concerned. The RPM database does not, should not and I hope never will contain the repository information in the way you are asking for a simple reason. The values in /etc/zypp/respos.d can be changed, hand edited even (BTDT), and the RPM database has no way of knowing about them. Think about the implications of that. -- 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

i think that Florian has provided the most helpful : "Easiest way is to create a autoyast profile from your running system. Install autoyast2 and then run yast2 clone_system It takes some time and then you have a xml: /root/autoinst.xml which contains not only rpm packages but also partition/filesystem layout, system settings, network settings and much more. Documentation is here: https://www.suse.com/documentation/sles11/singlehtml/book_autoyast/book_auto... If you reinstall the system, you have to feed the installer with the autoyast xml file. Another handy tool is yast2 support. Install yast2-support and navigate to "support" in yast2. then create a support-tarball. This contains many information you may want to review if your system has been reinstalled. " ................. { as this is SLE stuff . . . it is surely polished } ............... regards -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 07/05/2015 08:32 AM, Carlos E. R. wrote:

On 2015-07-05 13:57, Anton Aylward wrote:

...

On 07/03/2015 06:37 PM, Carlos E. R. wrote:

...

In fact, what I would do if I were to work on this, is an rpm query, relating vendors to repositories.

...

You would have to do that outside of the RPM database.

Vendor string is stored in the database. You are right, the repository name can't, it changes, but there must be a way to calculate it: zypper does, somehow.

Think of a 'relational database'. One table being in the RPM database, one table being somewhere in /etc/zypp/repos.d/ The 'join' that zypper makes is based on the content. I'm not sure how, not sure of the specifics, but I'm sure that someone with enough knowledge of C or C+ could "use the Source, Luke", and tell us. Knowing the what I'm sure it cold be reconstructed in Perl, Python or Ruby. Shell might be a bit of a stretch. -- 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-07-05 15:11, Anton Aylward wrote:

On 07/05/2015 08:32 AM, Carlos E. R. wrote:

...

Vendor string is stored in the database. You are right, the repository name can't, it changes, but there must be a way to calculate it: zypper does, somehow.

Think of a 'relational database'. One table being in the RPM database, one table being somewhere in /etc/zypp/repos.d/

Yep. Thus I need to find out where the "vendor" string out of a repository can be obtained. I can see it in "/var/cache/zypp/raw/repo-oss/content": VENDOR openSUSE But other repos don't have that file. I can, probably, obtain it by hand guessing. - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlWZY+oACgkQja8UbcUWM1za8wD9FLsLBZVnB+MFafw1lX7I20TG +hzrfQUoLyVysZ5AsWwBAIkn8JgLQrbmnfg0HRUyThXCr1T10pCskWe4msSB/qH+ =XyRS -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

ellanios82 wrote:

On 07/03/2015 05:46 PM, Per Jessen wrote:

what page of ISO installer screen contains autoyast.xml input field ??

There is only one input field, it's just a line of text. Here you can add kernel arguments and linuxrc arguments, such as these: nomodeset install=http://...... debug=1 init [S123] usessh=1 autoyast=<file> And many many more. All on one line, space-separated. -- Per Jessen, Zürich (23.3°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org