[opensuse] Are many 42.2 related (not 'official') repositories often out of sync with each other?
Hi All, I'm prepping a fallback Leap 42.2 system to substitute for my daily workhorse during it's 'vacation' in the shop for a warranty repair. I thought this process was going to be relatively straightforward, but I keep running into an astonishing number of inconsistencies like the examples excerpted below. (I have triple checked and both systems are definitely configured to use the same repositories): < abiword-3.0.1-1.14.x86_64 < abiword-docs-3.0.1-1.1.noarch ---
abiword-3.0.1-54.3.x86_64 abiword-docs-3.0.1-31.2.noarch
< dia-0.97.3-65.2.x86_64 < dia-lang-0.97.3-65.2.noarch ---
dia-0.97.3-3.35.x86_64 dia-lang-0.97.3-3.35.noarch
'zypper if epson-inkjet-printer-escpr' yields the following on one machine: Repository : @System Name : epson-inkjet-printer-escpr Version : 1.6.13-1lsb3.2 Arch : x86_64 Vendor : Seiko Epson Corporation ... and this on the other: Repository : @System Name : epson-inkjet-printer-escpr Version : 1.6.4-1lsb3.2 Arch : x86_64 Vendor : Seiko Epson Corporation ... Also, these inconsistencies aside (presuming this issue is going to be solved,) does anyone have a proven fast and reliable way to replicate an installed system on a parallel box without transplanting or imaging drives or attempting something like rsync? These systems are not much like each other from a hardware perspective, but I need the software that's installed on them to be the same. All constructive comments and ideas will be appreciated and are welcome! Thx! Carl -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Carl Hartung composed on 2017-06-27 23:09 (UTC-0400): .
I'm prepping a fallback Leap 42.2 system to substitute for my daily workhorse during it's 'vacation' in the shop for a warranty repair. . I thought this process was going to be relatively straightforward, but I keep running into an astonishing number of inconsistencies like the examples excerpted below. (I have triple checked and both systems are definitely configured to use the same repositories):
< abiword-3.0.1-1.14.x86_64 < abiword-docs-3.0.1-1.1.noarch ---
abiword-3.0.1-54.3.x86_64 abiword-docs-3.0.1-31.2.noarch
dia-0.97.3-3.35.x86_64 dia-lang-0.97.3-3.35.noarch ... 'zypper if epson-inkjet-printer-escpr' yields the following on one machine: ... Repository : @System . IIRC, the installed version not available from a currently enabled repo. . Name : epson-inkjet-printer-escpr Version : 1.6.13-1lsb3.2 ... Name : epson-inkjet-printer-escpr Version : 1.6.4-1lsb3.2 ... Also, these inconsistencies aside (presuming this issue is going to be solved,) does anyone have a proven fast and reliable way to replicate an installed system on a parallel box without transplanting or imaging drives or attempting something like rsync? These systems are not much
< dia-0.97.3-65.2.x86_64 < dia-lang-0.97.3-65.2.noarch --- like each other from a hardware perspective, but I need the software that's installed on them to be the same. . Yast2 sw_single [import|export] should make do what you want. Did you try? . All constructive comments and ideas will be appreciated and are welcome!
From host hpg33 here: # grep /etc/os-release PRETTY_NAME="openSUSE Leap 42.2" # zypper lr ... Alias | Name | Enabled | GPG Check | Refresh --------------+---------------+---------+-----------+-------- NonOSS | NonOSS | Yes | (r ) Yes | Yes OSS | OSS | Yes | (r ) Yes | Yes Packman | Packman | Yes | (r ) Yes | No Update | Update | Yes | (r ) Yes | Yes UpdateNonOSS | UpdateNonOSS | Yes | (r ) Yes | Yes # zypper se -s ~abiword | dia | epson-inkj abiword | package | 3.0.1-1.14 | x86_64 | OSS abiword-docs | package | 3.0.1-1.1 | noarch | OSS
Your currently installed packages do not all match what's currently available from your configured repos. Are either of these two installations updates from a previous release rather than originally 42.2 installs? If yes, installed packages could easily be higher version numbers even though older packages surviving the upgrade process. Using zypper in with --from &/or --oldpackage, or zypper dup, should be able to get one matched with the other, if repos truly match. libabiword-3_0 | package | 3.0.1-1.14 | x86_64 | OSS dia | package | 0.97.3-3.35 | x86_64 | OSS dia-lang | package | 0.97.3-3.35 | noarch | OSS epson-inkjet-printer-escpr | package | 1.4.0-4.4 | x86_64 | OSS -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Wed, 28 Jun 2017 00:20:47 -0400 Felix Miata wrote:
Carl Hartung composed on 2017-06-27 23:09 (UTC-0400): ...
'zypper if epson-inkjet-printer-escpr' yields the following on one machine: ... Repository : @System . IIRC, the installed version not available from a currently enabled repo. .
Thank you! :) ...
Yast2 sw_single [import|export] should make do what you want. Did you try? .
No, but I shall! Thank you very much, Felix! Carl -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2017-06-28 05:09, Carl Hartung wrote:
Hi All,
I'm prepping a fallback Leap 42.2 system to substitute for my daily workhorse during it's 'vacation' in the shop for a warranty repair.
I thought this process was going to be relatively straightforward, but I keep running into an astonishing number of inconsistencies like the examples excerpted below. (I have triple checked and both systems are definitely configured to use the same repositories):
< abiword-3.0.1-1.14.x86_64 < abiword-docs-3.0.1-1.1.noarch ---
abiword-3.0.1-54.3.x86_64 abiword-docs-3.0.1-31.2.noarch
You have not updated both machines the same day and hour. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
On Wed, 28 Jun 2017 11:25:00 +0200 Carlos E. R. wrote:
abiword-docs-3.0.1-31.2.noarch
You have not updated both machines the same day and hour.
Thank you, Carlos! In this case the systems are side-by-side. Carl -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2017-06-29 12:34, Carl Hartung wrote:
On Wed, 28 Jun 2017 11:25:00 +0200 Carlos E. R. wrote:
abiword-docs-3.0.1-31.2.noarch
You have not updated both machines the same day and hour.
Thank you, Carlos!
In this case the systems are side-by-side.
Even then, it does not prove that the updates were done at the same time nor that the repos are exactly the same. You could run "zypper lr --details" on both and post both results. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
On Thu, 29 Jun 2017 12:55:44 +0200 Carlos E. R. wrote:
On 2017-06-29 12:34, Carl Hartung wrote:
On Wed, 28 Jun 2017 11:25:00 +0200 Carlos E. R. wrote:
abiword-docs-3.0.1-31.2.noarch
You have not updated both machines the same day and hour.
Thank you, Carlos!
In this case the systems are side-by-side.
Even then, it does not prove that the updates were done at the same time nor that the repos are exactly the same.
You could run "zypper lr --details" on both and post both results.
Thank you, Carlos :) but that's way too much information to post to the list. There are 26 repos configured on each system and 'side by side' was meant in a literal sense. I confirmed and added them, as needed, to the second system while reading them off the main system -- so I know for a fact that the configured repositories are identical. What's happened in this case is the main system's software inventory has expanded 'organically' as I've used it. This included investigating alternative repositories and installing newer versions of software which are compatible with the main installation and adding and updating them individually. Now I'm finding it's quite a slog to retrace those steps on the second system, and this is why I've asked if there's an automated or semi-automated way of accomplishing this. I do appreciate your interest! :) Carl -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Op vrijdag 30 juni 2017 13:40:05 CEST schreef Carl Hartung:
On Thu, 29 Jun 2017 12:55:44 +0200
Carlos E. R. wrote:
On 2017-06-29 12:34, Carl Hartung wrote:
On Wed, 28 Jun 2017 11:25:00 +0200
Carlos E. R. wrote:
abiword-docs-3.0.1-31.2.noarch
You have not updated both machines the same day and hour.
Thank you, Carlos!
In this case the systems are side-by-side.
Even then, it does not prove that the updates were done at the same time nor that the repos are exactly the same.
You could run "zypper lr --details" on both and post both results.
Thank you, Carlos :) but that's way too much information to post to the list. There are 26 repos configured on each system and 'side by side' was meant in a literal sense. I confirmed and added them, as needed, to the second system while reading them off the main system -- so I know for a fact that the configured repositories are identical.
What's happened in this case is the main system's software inventory has expanded 'organically' as I've used it. This included investigating alternative repositories and installing newer versions of software which are compatible with the main installation and adding and updating them individually. Now I'm finding it's quite a slog to retrace those steps on the second system, and this is why I've asked if there's an automated or semi-automated way of accomplishing this.
I do appreciate your interest! :)
Carl 26 Repos? Why? This way your breaking everything that was tested thoroughly to give a stable experience. FWIW home: and devel: repos are meant to break stuff ( and fix it ), not for production use.
If you want the latest and greatest, Tumbleweed should be your choice. For managing mutliple machines, f.e. add a repo on all machines in one command, have a look at salt(stack). This one f.e. updates a Centos and 4 openSUSE (2 Leap, 2 TW ) machines in one go: salt '*' pkg.upgrade -- Gertjan Lettink, a.k.a. Knurpht openSUSE Board Member openSUSE Forums Team -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Fri, 30 Jun 2017 14:07:12 +0200 Knurpht - Gertjan Lettink wrote:
26 Repos? Why? This way your breaking everything that was tested thoroughly to give a stable experience. FWIW home: and devel: repos are meant to break stuff ( and fix it ), not for production use.
If you want the latest and greatest, Tumbleweed should be your choice.
For managing mutliple machines, f.e. add a repo on all machines in one command, have a look at salt(stack). This one f.e. updates a Centos and 4 openSUSE (2 Leap, 2 TW ) machines in one go: salt '*' pkg.upgrade
I had the same initial reaction once I'd finished enumerating them :) But, of course, that number includes an alternate (refresh only) and several added automatically but not enabled: 1 Node.js http://download.opensuse.org/repositories/devel:/languages:/nodejs/openSUSE_... 2 & 3 Packman (primary enabled, alternate 'refresh' only) http://ftp.gwdg.de/pub/linux/misc/packman/suse/openSUSE_Leap_42.2/ http://packman.inode.at/suse/openSUSE_Leap_42.2/ 4 Official MATE Desktop http://download.opensuse.org/repositories/X11:/MATE:/Current/openSUSE_Leap_4... 5 Visual Studio Code https://packages.microsoft.com/yumrepos/vscode 6 WINE http://download.opensuse.org/repositories/Emulators:/Wine/openSUSE_Leap_42.2... 7 X11:Cinnamon:Current http://download.opensuse.org/repositories/X11:/Cinnamon:/Current/openSUSE_Le... 8 Cinelerra https://cinelerra-cv.org/five/pkgs/leap/ 9 Leap 42.2 Non-OSS http://download.opensuse.org/distribution/leap/42.2/repo/non-oss/ 10 Leap 42.2 Non-OSS Updates http://download.opensuse.org/update/leap/42.2/non-oss/ 11 Leap 42.2 OSS http://download.opensuse.org/distribution/leap/42.2/repo/oss/ 12 Leap 42.2 OSS Updates http://download.opensuse.org/update/leap/42.2/oss 13 OBS GNOME Apps http://download.opensuse.org/repositories/GNOME:/Apps/openSUSE_Leap_42.2/ 14 OBS Mozilla http://download.opensuse.org/repositories/mozilla/openSUSE_Leap_42.2/ 15 openSUSE Education http://download.opensuse.org/repositories/Education/openSUSE_Leap_42.2/ 16 nVidia Graphics Drivers http://download.nvidia.com/opensuse/leap/42.2/ 17 Skype (needed for work) https://repo.skype.com/rpm/stable/ The remaining 9 are not enabled: - Installation source (USB stick) - Community Leap 42.2 A/V 'codecs' related (enabled when/if needed) - 2 x debug: OSS & Non-OSS - 2 x debug update: OSS & Non-OSS - 1 x OSS sources - 1 x Non-OSS sources To reiterate: I am not seeking help for a 'broken' system. I'm seeking a way to automate or semi-automate the synchronization of the two installed systems. Thanks for your interest & regards, Carl -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Carl Hartung composed on 2017-06-30 08:47 (UTC-0400):
I'm seeking a way to automate or semi-automate the synchronization of the two installed systems.
Repos are nothing more than the content of /etc/zypp/repos.d/*.repo. Tar that from one installation and extract it on the other, and the repository sets on the two installations will be identical. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Felix Miata wrote:
Carl Hartung composed on 2017-06-30 08:47 (UTC-0400):
I'm seeking a way to automate or semi-automate the synchronization of the two installed systems.
Repos are nothing more than the content of /etc/zypp/repos.d/*.repo. Tar that from one installation and extract it on the other, and the repository sets on the two installations will be identical.
Not completely. Yes, the repos will be identical. But which package (of an application available in several repos) is installed depends on when it was installed, and which of the repos had been active at that time. So even if you have identical repos one machine can have a different version installed than another. And 'zypper up' will never change that situation, as it won't change an application to another repo... A zypper dup on both/all machines (with identical repos) would sync them, but is probably not what you want. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2017-06-30 14:47, Carl Hartung wrote:
On Fri, 30 Jun 2017 14:07:12 +0200 Knurpht - Gertjan Lettink wrote:
26 Repos? Why? This way your breaking everything that was tested thoroughly to give a stable experience. FWIW home: and devel: repos are meant to break stuff ( and fix it ), not for production use.
If you want the latest and greatest, Tumbleweed should be your choice.
For managing mutliple machines, f.e. add a repo on all machines in one command, have a look at salt(stack). This one f.e. updates a Centos and 4 openSUSE (2 Leap, 2 TW ) machines in one go: salt '*' pkg.upgrade
I had the same initial reaction once I'd finished enumerating them :)
But, of course, that number includes an alternate (refresh only) and several added automatically but not enabled:
Seeing the list, it is not really excessive. You are using mostly specific repos for things that are only there: nvidia, cinelerra, packman... And some repos to keep some stuff more recent, like Wine. Some of the number are disabled, so they don't really count.
To reiterate: I am not seeking help for a 'broken' system. I'm seeking a way to automate or semi-automate the synchronization of the two installed systems.
There is no automated way. It would be the same set of tools as needed to replicate an installation on same or another machine. There are tools to save rpm package list and load it again (in YaST), but they do not consider where the rpms come from. It is what would be needed to reconstruct a machine in case of rebuild, too. And it is not easy to generate a list of repo/package list, because there is no way to query they rpm database and know from which repo a package comes. You need some code to relate vendor strings to repos instead.
Thanks for your interest & regards,
Welcome :-) -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
Op vrijdag 30 juni 2017 20:20:12 CEST schreef Carlos E. R.:
On 2017-06-30 14:47, Carl Hartung wrote:
On Fri, 30 Jun 2017 14:07:12 +0200
Knurpht - Gertjan Lettink wrote:
26 Repos? Why? This way your breaking everything that was tested thoroughly to give a stable experience. FWIW home: and devel: repos are meant to break stuff ( and fix it ), not for production use.
If you want the latest and greatest, Tumbleweed should be your choice.
For managing mutliple machines, f.e. add a repo on all machines in one command, have a look at salt(stack). This one f.e. updates a Centos and 4 openSUSE (2 Leap, 2 TW ) machines in one go: salt '*' pkg.upgrade
I had the same initial reaction once I'd finished enumerating them :)
But, of course, that number includes an alternate (refresh only) and
several added automatically but not enabled: Seeing the list, it is not really excessive. You are using mostly specific repos for things that are only there: nvidia, cinelerra, packman... And some repos to keep some stuff more recent, like Wine. Some of the number are disabled, so they don't really count.
To reiterate: I am not seeking help for a 'broken' system. I'm seeking a way to automate or semi-automate the synchronization of the two installed systems.
There is no automated way.
There is. Use Saltstack salt '*' cmd.run 'zypper ar WHATEVER' salt '*' cmd.run ''zypper in dog' does the job on both machines. openSUSE packages are available, setup is easy.
It would be the same set of tools as needed to replicate an installation on same or another machine. There are tools to save rpm package list and load it again (in YaST), but they do not consider where the rpms come from. It is what would be needed to reconstruct a machine in case of rebuild, too.
And it is not easy to generate a list of repo/package list, because there is no way to query they rpm database and know from which repo a package comes. You need some code to relate vendor strings to repos instead.
Thanks for your interest & regards,
Welcome :-)
-- Gertjan Lettink, a.k.a. Knurpht openSUSE Board Member openSUSE Forums Team -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2017-06-30 21:46, Knurpht - Gertjan Lettink wrote:
Op vrijdag 30 juni 2017 20:20:12 CEST schreef Carlos E. R.:
On 2017-06-30 14:47, Carl Hartung wrote:
On Fri, 30 Jun 2017 14:07:12 +0200
Knurpht - Gertjan Lettink wrote:
26 Repos? Why? This way your breaking everything that was tested thoroughly to give a stable experience. FWIW home: and devel: repos are meant to break stuff ( and fix it ), not for production use.
If you want the latest and greatest, Tumbleweed should be your choice.
For managing mutliple machines, f.e. add a repo on all machines in one command, have a look at salt(stack). This one f.e. updates a Centos and 4 openSUSE (2 Leap, 2 TW ) machines in one go: salt '*' pkg.upgrade
I had the same initial reaction once I'd finished enumerating them :)
But, of course, that number includes an alternate (refresh only) and
several added automatically but not enabled: Seeing the list, it is not really excessive. You are using mostly specific repos for things that are only there: nvidia, cinelerra, packman... And some repos to keep some stuff more recent, like Wine. Some of the number are disabled, so they don't really count.
To reiterate: I am not seeking help for a 'broken' system. I'm seeking a way to automate or semi-automate the synchronization of the two installed systems.
There is no automated way.
There is. Use Saltstack
salt '*' cmd.run 'zypper ar WHATEVER' salt '*' cmd.run ''zypper in dog' does the job on both machines. openSUSE packages are available, setup is easy.
https://software.opensuse.org/package/salt salt A parallel remote execution system Salt is a distributed remote execution system used to execute commands and query data. It was developed in order to bring the best solutions found in the world of remote execution together and make them better, faster and more malleable. Salt accomplishes this via its ability to handle larger loads of information, and not just dozens, but hundreds or even thousands of individual servers, handle them quickly and through a simple and manageable interface. Well, that helps if you do the operations on all the computers at the same time, but it does not help after the fact, say when a month later you want to have a second computer with the same list of packages from the same repos, and you do not have a list of the operations done on the first computer.
It would be the same set of tools as needed to replicate an installation on same or another machine. There are tools to save rpm package list and load it again (in YaST), but they do not consider where the rpms come from. It is what would be needed to reconstruct a machine in case of rebuild, too.
And it is not easy to generate a list of repo/package list, because there is no way to query they rpm database and know from which repo a package comes. You need some code to relate vendor strings to repos instead.
Thanks for your interest & regards,
Welcome :-)
-- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
On Fri, 30 Jun 2017 22:21:29 +0200 Carlos E. R. wrote:
https://software.opensuse.org/package/salt
salt A parallel remote execution system
Salt is a distributed remote execution system used to execute commands and query data. It was developed in order to bring the best solutions found in the world of remote execution together and make them better, faster and more malleable. Salt accomplishes this via its ability to handle larger loads of information, and not just dozens, but hundreds or even thousands of individual servers, handle them quickly and through a simple and manageable interface.
Well, that helps if you do the operations on all the computers at the same time, but it does not help after the fact, say when a month later you want to have a second computer with the same list of packages from the same repos, and you do not have a list of the operations done on the first computer.
This confirms my deductions, Carlos. Thanks for this! :) Carl -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Fri, 30 Jun 2017 21:46:30 +0200 Knurpht - Gertjan Lettink wrote:
There is. Use Saltstack
salt '*' cmd.run 'zypper ar WHATEVER' salt '*' cmd.run ''zypper in dog' does the job on both machines. openSUSE packages are available, setup is easy.
Thanks for the tip, Knurpht! Carl -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Tue, Jun 27, 2017 at 11:09 PM, Carl Hartung <opensuse@cehartung.com> wrote:
definitely configured to use the same repositories):
< abiword-3.0.1-1.14.x86_64 < abiword-docs-3.0.1-1.1.noarch ---
abiword-3.0.1-54.3.x86_64 abiword-docs-3.0.1-31.2.noarch
Are you running "zypper up" on the main machine? I use "zypper se -s abiword" to troubleshoot issues like this. I'm betting either those are being pulled from different repos or you aren't running "zypper up". If the repos are different, I don't know an automated way to sync them up. Greg -- Greg Freemyer Advances are made by answering questions. Discoveries are made by questioning answers. — Bernard Haisch -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Wed, 28 Jun 2017 06:57:30 -0400 Greg Freemyer wrote:
Are you running "zypper up" on the main machine?
On both systems, side by side.
I use "zypper se -s abiword" to troubleshoot issues like this. I'm betting either those are being pulled from different repos or you aren't running "zypper up".
You're spot on! As I suspected, some OBS repos I'd enabled in the past on the main system are involved. I haven't enabled 'allow vendor change' for obvious reasons. Resolving these is a bit of a slog, but I'm working my way through it. Thanks for the helpful feedback! Carl -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Wed, 28 Jun 2017 06:57:30 -0400 Greg Freemyer wrote:
Are you running "zypper up" on the main machine?
Always 'zypper refresh' then 'zypper update'
I use "zypper se -s abiword" to troubleshoot issues like this. I'm betting either those are being pulled from different repos or you aren't running "zypper up".
As I wrote earlier in the thread, the packages that are different being pulled from alternate repositories.
If the repos are different, I don't know an automated way to sync them up.
This is as I was beginning to suspect. I just need to block out some time to run YaST2's Software Management module side by side with the two machines. On the second system, those packages with newer versions available on the alternate repositories will, I believe, be highlighted in blue, so they're easy to spot. It's then just a matter of selecting them and choosing to install the alternate package. Not an automated solution, but not insurmountable either. Thank you very much for your feedback, Greg! :) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (6)
-
Carl Hartung -
Carlos E. R. -
Felix Miata -
Greg Freemyer -
Knurpht - Gertjan Lettink -
Peter Suetterlin