[opensuse-buildservice] centos developer toolsets
hi all, is there any way how I can enable "Developer Toolsets" in centos/rhel projects in the OBS, please? For one of my packages I need gcc toolset >= 5.x, unfortunately these distros contain 4.x only. reference: https://www.softwarecollections.org/en/scls/rhscl/devtoolset-7/ or do I need to import all these packages into my OBS? http://mirror.centos.org/centos/7/sclo/x86_64/rh/devtoolset-7/ thanks, Petr -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On Dienstag, 8. Januar 2019, 09:36:41 CET Petr Vanek wrote:
hi all,
is there any way how I can enable "Developer Toolsets" in centos/rhel projects in the OBS, please?
For one of my packages I need gcc toolset >= 5.x, unfortunately these distros contain 4.x only.
reference:
https://www.softwarecollections.org/en/scls/rhscl/devtoolset-7/
or do I need to import all these packages into my OBS?
http://mirror.centos.org/centos/7/sclo/x86_64/rh/devtoolset-7/
seems so ... these are just single files without any repository data. Importing the src.rpm's seems to be the easiest -- Adrian Schroeter SUSE Linux Products GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany email: adrian@suse.de -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On Tuesday 2019-01-08 09:41, Adrian Schröter wrote:
On Dienstag, 8. Januar 2019, 09:36:41 CET Petr Vanek wrote:
hi all,
is there any way how I can enable "Developer Toolsets" in centos/rhel projects in the OBS, please?
For one of my packages I need gcc toolset >= 5.x, unfortunately these distros contain 4.x only.
reference:
https://www.softwarecollections.org/en/scls/rhscl/devtoolset-7/
or do I need to import all these packages into my OBS?
http://mirror.centos.org/centos/7/sclo/x86_64/rh/devtoolset-7/
seems so ... these are just single files without any repository data.
Importing the src.rpm's seems to be the easiest
Just import the binrpms (make empty project, copy into /srv/obs/build/.../:full/ and run bs_admin rescan-repository) -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On Dienstag, 8. Januar 2019, 10:48:51 CET Jan Engelhardt wrote:
On Tuesday 2019-01-08 09:41, Adrian Schröter wrote:
On Dienstag, 8. Januar 2019, 09:36:41 CET Petr Vanek wrote:
hi all,
is there any way how I can enable "Developer Toolsets" in centos/rhel projects in the OBS, please?
For one of my packages I need gcc toolset >= 5.x, unfortunately these distros contain 4.x only.
reference:
https://www.softwarecollections.org/en/scls/rhscl/devtoolset-7/
or do I need to import all these packages into my OBS?
http://mirror.centos.org/centos/7/sclo/x86_64/rh/devtoolset-7/
seems so ... these are just single files without any repository data.
Importing the src.rpm's seems to be the easiest
Just import the binrpms (make empty project, copy into /srv/obs/build/.../:full/ and run bs_admin rescan-repository)
no, sorry, I will not maintain, verify and update these manually. (your howto is btw quite risky, because any repository rebuild event will drop them ;) -- Adrian Schroeter SUSE Linux Products GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany email: adrian@suse.de -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On Tuesday 2019-01-08 11:04, Adrian Schröter wrote:
http://mirror.centos.org/centos/7/sclo/x86_64/rh/devtoolset-7/
Importing the src.rpm's seems to be the easiest
Just import the binrpms (make empty project, copy into /srv/obs/build/.../:full/ and run bs_admin rescan-repository)
no, sorry, I will not maintain, verify and update these manually.
Well, can DoD support rpmmd-less directories like zypper?
(your howto is btw quite risky, because any repository rebuild event will drop them ;)
Where is that rebuild event supposed to come from? Unless one maliciously adds a BSpkg (sosc ls pr:p), the project is empty, i.e. has no BSpkgs that could ever be built. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On Tue, 8 Jan 2019, Petr Vanek wrote:
hi all,
is there any way how I can enable "Developer Toolsets" in centos/rhel projects in the OBS, please?
For one of my packages I need gcc toolset >= 5.x, unfortunately these distros contain 4.x only.
reference:
https://www.softwarecollections.org/en/scls/rhscl/devtoolset-7/
or do I need to import all these packages into my OBS?
http://mirror.centos.org/centos/7/sclo/x86_64/rh/devtoolset-7/
I've backported GCC 4.8 for RHEL 5/6 using the SRPMs, which wasn't too painful - just lots of FileProvides and overrides in the project config, plus removing unnecessary features and dependencies from the RPM spec. Multilib (building 32-bit on 64-bit) was one of the major things to drop, as we don't need it and there didn't seem to be a good way of convincing OBS to install two architectures' worth of libc. You can see it in shells:fish:nightly:master:g++48 - might help get you started. All my specfile changes are marked with initials ([DAA]). David Adam zanchey@ucc.gu.uwa.edu.au -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On Tue, Jan 8, 2019 at 3:36 AM Petr Vanek <petr@yarpen.cz> wrote:
hi all,
is there any way how I can enable "Developer Toolsets" in centos/rhel projects in the OBS, please?
For one of my packages I need gcc toolset >= 5.x, unfortunately these distros contain 4.x only.
reference:
https://www.softwarecollections.org/en/scls/rhscl/devtoolset-7/
or do I need to import all these packages into my OBS?
http://mirror.centos.org/centos/7/sclo/x86_64/rh/devtoolset-7/
Yes, just enable the SCL repository in your project meta for CentOS 7. For example, this is what I have: <repository name="CentOS_7"> <path project="Fedora:EPEL:7" repository="standard"/> <path project="CentOS:CentOS-7" repository="scl-rhscl"/> <path project="CentOS:CentOS-7" repository="standard"/> <arch>x86_64</arch> </repository> That enables EPEL and the RHSCL repository for CentOS 7 on top of the regular base repo. -- 真実はいつも一つ！/ Always, there's only one truth! -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On 1/8/2019 12:03 PM, Neal Gompa wrote:
On Tue, Jan 8, 2019 at 3:36 AM Petr Vanek <petr@yarpen.cz> wrote:
hi all,
is there any way how I can enable "Developer Toolsets" in centos/rhel projects in the OBS, please?
For one of my packages I need gcc toolset >= 5.x, unfortunately these distros contain 4.x only.
reference:
https://www.softwarecollections.org/en/scls/rhscl/devtoolset-7/
or do I need to import all these packages into my OBS?
http://mirror.centos.org/centos/7/sclo/x86_64/rh/devtoolset-7/
Yes, just enable the SCL repository in your project meta for CentOS 7.
For example, this is what I have:
<repository name="CentOS_7"> <path project="Fedora:EPEL:7" repository="standard"/> <path project="CentOS:CentOS-7" repository="scl-rhscl"/> <path project="CentOS:CentOS-7" repository="standard"/> <arch>x86_64</arch> </repository>
That enables EPEL and the RHSCL repository for CentOS 7 on top of the regular base repo.
This is excellent! Thank you very much. The only issue is that the sync looks outdated. Because my build (osc build ...) wants to download older, already non-existing packages from http://ftp.halifax.rwth-aachen.de/centos/7/sclo/x86_64/rh actually requested: devtoolset-7-oprofile-1.2.0-1.el7.sc1.x86_64.rpm but provided: devtoolset-7-oprofile-1.2.0-2.el7.sc1.x86_64.rpm Is there some auto-update set? -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On Dienstag, 8. Januar 2019, 12:46:12 CET Petr Vanek wrote:
On 1/8/2019 12:03 PM, Neal Gompa wrote:
On Tue, Jan 8, 2019 at 3:36 AM Petr Vanek <petr@yarpen.cz> wrote:
hi all,
is there any way how I can enable "Developer Toolsets" in centos/rhel projects in the OBS, please?
For one of my packages I need gcc toolset >= 5.x, unfortunately these distros contain 4.x only.
reference:
https://www.softwarecollections.org/en/scls/rhscl/devtoolset-7/
or do I need to import all these packages into my OBS?
http://mirror.centos.org/centos/7/sclo/x86_64/rh/devtoolset-7/
Yes, just enable the SCL repository in your project meta for CentOS 7.
For example, this is what I have: <repository name="CentOS_7">
<path project="Fedora:EPEL:7" repository="standard"/> <path project="CentOS:CentOS-7" repository="scl-rhscl"/> <path project="CentOS:CentOS-7" repository="standard"/> <arch>x86_64</arch>
</repository>
That enables EPEL and the RHSCL repository for CentOS 7 on top of the regular base repo.
This is excellent! Thank you very much.
The only issue is that the sync looks outdated. Because my build (osc build ...) wants to download older, already non-existing packages from http://ftp.halifax.rwth-aachen.de/centos/7/sclo/x86_64/rh
actually requested: devtoolset-7-oprofile-1.2.0-1.el7.sc1.x86_64.rpm
but provided: devtoolset-7-oprofile-1.2.0-2.el7.sc1.x86_64.rpm
Is there some auto-update set?
nah, that repo gets currently refused, because the gpg for the signature is not matching anymore. However, I have atm no clue where I can find the official pubkeys from a proven source for them. They are not listed here at least: https://www.centos.org/keys/ Does ne1 has a clue? -- Adrian Schroeter SUSE Linux Products GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany email: adrian@suse.de -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On Tue, Jan 8, 2019 at 9:32 AM Adrian Schröter <adrian@suse.de> wrote:
On Dienstag, 8. Januar 2019, 12:46:12 CET Petr Vanek wrote:
On 1/8/2019 12:03 PM, Neal Gompa wrote:
On Tue, Jan 8, 2019 at 3:36 AM Petr Vanek <petr@yarpen.cz> wrote:
hi all,
is there any way how I can enable "Developer Toolsets" in centos/rhel projects in the OBS, please?
For one of my packages I need gcc toolset >= 5.x, unfortunately these distros contain 4.x only.
reference:
https://www.softwarecollections.org/en/scls/rhscl/devtoolset-7/
or do I need to import all these packages into my OBS?
http://mirror.centos.org/centos/7/sclo/x86_64/rh/devtoolset-7/
Yes, just enable the SCL repository in your project meta for CentOS 7.
For example, this is what I have: <repository name="CentOS_7">
<path project="Fedora:EPEL:7" repository="standard"/> <path project="CentOS:CentOS-7" repository="scl-rhscl"/> <path project="CentOS:CentOS-7" repository="standard"/> <arch>x86_64</arch>
</repository>
That enables EPEL and the RHSCL repository for CentOS 7 on top of the regular base repo.
This is excellent! Thank you very much.
The only issue is that the sync looks outdated. Because my build (osc build ...) wants to download older, already non-existing packages from http://ftp.halifax.rwth-aachen.de/centos/7/sclo/x86_64/rh
actually requested: devtoolset-7-oprofile-1.2.0-1.el7.sc1.x86_64.rpm
but provided: devtoolset-7-oprofile-1.2.0-2.el7.sc1.x86_64.rpm
Is there some auto-update set?
nah, that repo gets currently refused, because the gpg for the signature is not matching anymore.
However, I have atm no clue where I can find the official pubkeys from a proven source for them. They are not listed here at least:
Does ne1 has a clue?
The rhscl and sclo repos are done by the Software Collections SIG. So that GPG key should be valid for it. -- 真実はいつも一つ！/ Always, there's only one truth! -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On Dienstag, 8. Januar 2019, 15:36:13 CET Neal Gompa wrote:
On Tue, Jan 8, 2019 at 9:32 AM Adrian Schröter <adrian@suse.de> wrote:
On Dienstag, 8. Januar 2019, 12:46:12 CET Petr Vanek wrote:
On 1/8/2019 12:03 PM, Neal Gompa wrote:
On Tue, Jan 8, 2019 at 3:36 AM Petr Vanek <petr@yarpen.cz> wrote:
hi all,
is there any way how I can enable "Developer Toolsets" in centos/rhel projects in the OBS, please?
For one of my packages I need gcc toolset >= 5.x, unfortunately these distros contain 4.x only.
reference:
https://www.softwarecollections.org/en/scls/rhscl/devtoolset-7/
or do I need to import all these packages into my OBS?
http://mirror.centos.org/centos/7/sclo/x86_64/rh/devtoolset-7/
Yes, just enable the SCL repository in your project meta for CentOS 7.
For example, this is what I have: <repository name="CentOS_7">
<path project="Fedora:EPEL:7" repository="standard"/> <path project="CentOS:CentOS-7" repository="scl-rhscl"/> <path project="CentOS:CentOS-7" repository="standard"/> <arch>x86_64</arch>
</repository>
That enables EPEL and the RHSCL repository for CentOS 7 on top of the regular base repo.
This is excellent! Thank you very much.
The only issue is that the sync looks outdated. Because my build (osc build ...) wants to download older, already non-existing packages from http://ftp.halifax.rwth-aachen.de/centos/7/sclo/x86_64/rh
actually requested: devtoolset-7-oprofile-1.2.0-1.el7.sc1.x86_64.rpm
but provided: devtoolset-7-oprofile-1.2.0-2.el7.sc1.x86_64.rpm
Is there some auto-update set?
nah, that repo gets currently refused, because the gpg for the signature is not matching anymore.
However, I have atm no clue where I can find the official pubkeys from a
proven source for them. They are not listed here at least: https://www.centos.org/keys/
Does ne1 has a clue?
The rhscl and sclo repos are done by the Software Collections SIG. So that GPG key should be valid for it.
right, that is the one which is configured ... however, it seems the signature seems to be broken indeed atm: # gpg2 --verify repomd.asc repomd gpg: Signatur vom Sa 19 Mai 2018 02:44:12 CEST gpg: mittels RSA-Schlüssel 4EB84E71F2EE9D55 gpg: FALSCHE Signatur von "CentOS SoftwareCollections SIG (https:// wiki.centos.org/SpecialInterestGroup/SCLo) <security@centos.org>" [unbekannt] -- Adrian Schroeter SUSE Linux Products GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany email: adrian@suse.de -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On Tue, Jan 08, 2019 at 04:01:19PM +0100, Adrian Schröter wrote:
On Dienstag, 8. Januar 2019, 15:36:13 CET Neal Gompa wrote:
On Tue, Jan 8, 2019 at 9:32 AM Adrian Schröter <adrian@suse.de> wrote:
On Dienstag, 8. Januar 2019, 12:46:12 CET Petr Vanek wrote:
On 1/8/2019 12:03 PM, Neal Gompa wrote:
On Tue, Jan 8, 2019 at 3:36 AM Petr Vanek <petr@yarpen.cz> wrote:
hi all,
is there any way how I can enable "Developer Toolsets" in centos/rhel projects in the OBS, please?
For one of my packages I need gcc toolset >= 5.x, unfortunately these distros contain 4.x only.
reference:
https://www.softwarecollections.org/en/scls/rhscl/devtoolset-7/
or do I need to import all these packages into my OBS?
http://mirror.centos.org/centos/7/sclo/x86_64/rh/devtoolset-7/
Yes, just enable the SCL repository in your project meta for CentOS 7.
For example, this is what I have: <repository name="CentOS_7">
<path project="Fedora:EPEL:7" repository="standard"/> <path project="CentOS:CentOS-7" repository="scl-rhscl"/> <path project="CentOS:CentOS-7" repository="standard"/> <arch>x86_64</arch>
</repository>
That enables EPEL and the RHSCL repository for CentOS 7 on top of the regular base repo.
This is excellent! Thank you very much.
The only issue is that the sync looks outdated. Because my build (osc build ...) wants to download older, already non-existing packages from http://ftp.halifax.rwth-aachen.de/centos/7/sclo/x86_64/rh
actually requested: devtoolset-7-oprofile-1.2.0-1.el7.sc1.x86_64.rpm
but provided: devtoolset-7-oprofile-1.2.0-2.el7.sc1.x86_64.rpm
Is there some auto-update set?
nah, that repo gets currently refused, because the gpg for the signature is not matching anymore.
However, I have atm no clue where I can find the official pubkeys from a
proven source for them. They are not listed here at least: https://www.centos.org/keys/
Does ne1 has a clue?
The rhscl and sclo repos are done by the Software Collections SIG. So that GPG key should be valid for it.
right, that is the one which is configured ...
however, it seems the signature seems to be broken indeed atm:
Which doesn't surprise me, as the sig was made May 2018... So somebody on the centos side screwed up. (btw, why do we use http://ftp.halifax.rwth-aachen.de instead of http://mirror.centos.org for that repo? Not that it matters, the sig is also wrong on mirror.centos.org) Cheers, Michael. -- Michael Schroeder mls@suse.de SUSE LINUX GmbH, GF Jeff Hawn, HRB 16746 AG Nuernberg main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);} -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On 1/9/19 11:29 AM, Michael Schroeder wrote:
On Tue, Jan 08, 2019 at 04:01:19PM +0100, Adrian Schröter wrote:
On Dienstag, 8. Januar 2019, 15:36:13 CET Neal Gompa wrote:
On Dienstag, 8. Januar 2019, 12:46:12 CET Petr Vanek wrote:
On 1/8/2019 12:03 PM, Neal Gompa wrote:
On Tue, Jan 8, 2019 at 3:36 AM Petr Vanek <petr@yarpen.cz> wrote: > hi all, > > is there any way how I can enable "Developer Toolsets" in centos/rhel > projects in the OBS, please? > > For one of my packages I need gcc toolset >= 5.x, unfortunately these > distros contain 4.x only. > > reference: > > https://www.softwarecollections.org/en/scls/rhscl/devtoolset-7/ > > or do I need to import all these packages into my OBS? > > http://mirror.centos.org/centos/7/sclo/x86_64/rh/devtoolset-7/ Yes, just enable the SCL repository in your project meta for CentOS 7.
For example, this is what I have: <repository name="CentOS_7">
<path project="Fedora:EPEL:7" repository="standard"/> <path project="CentOS:CentOS-7" repository="scl-rhscl"/> <path project="CentOS:CentOS-7" repository="standard"/> <arch>x86_64</arch>
</repository>
That enables EPEL and the RHSCL repository for CentOS 7 on top of the regular base repo. This is excellent! Thank you very much.
The only issue is that the sync looks outdated. Because my build (osc build ...) wants to download older, already non-existing packages from http://ftp.halifax.rwth-aachen.de/centos/7/sclo/x86_64/rh
actually requested: devtoolset-7-oprofile-1.2.0-1.el7.sc1.x86_64.rpm
but provided: devtoolset-7-oprofile-1.2.0-2.el7.sc1.x86_64.rpm
Is there some auto-update set? nah, that repo gets currently refused, because the gpg for the signature is not matching anymore.
However, I have atm no clue where I can find the official pubkeys from a
proven source for them. They are not listed here at least: https://www.centos.org/keys/
Does ne1 has a clue? The rhscl and sclo repos are done by the Software Collections SIG. So
On Tue, Jan 8, 2019 at 9:32 AM Adrian Schröter <adrian@suse.de> wrote: that GPG key should be valid for it. right, that is the one which is configured ...
however, it seems the signature seems to be broken indeed atm: Which doesn't surprise me, as the sig was made May 2018... So somebody on the centos side screwed up.
(btw, why do we use http://ftp.halifax.rwth-aachen.de instead of http://mirror.centos.org for that repo? Not that it matters, the sig is also wrong on mirror.centos.org)
Is there any chance to get it resolved, please? Eg. to update OBS gpg keyring to accept this key? Or should I contact SCL guys somehow? Petr -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On Mon, Jan 21, 2019 at 9:00 AM Petr Vanek <petr@yarpen.cz> wrote:
On 1/9/19 11:29 AM, Michael Schroeder wrote:
On Tue, Jan 08, 2019 at 04:01:19PM +0100, Adrian Schröter wrote:
On Dienstag, 8. Januar 2019, 15:36:13 CET Neal Gompa wrote:
On Dienstag, 8. Januar 2019, 12:46:12 CET Petr Vanek wrote:
On 1/8/2019 12:03 PM, Neal Gompa wrote: > On Tue, Jan 8, 2019 at 3:36 AM Petr Vanek <petr@yarpen.cz> wrote: >> hi all, >> >> is there any way how I can enable "Developer Toolsets" in centos/rhel >> projects in the OBS, please? >> >> For one of my packages I need gcc toolset >= 5.x, unfortunately these >> distros contain 4.x only. >> >> reference: >> >> https://www.softwarecollections.org/en/scls/rhscl/devtoolset-7/ >> >> or do I need to import all these packages into my OBS? >> >> http://mirror.centos.org/centos/7/sclo/x86_64/rh/devtoolset-7/ > Yes, just enable the SCL repository in your project meta for CentOS 7. > > For example, this is what I have: > <repository name="CentOS_7"> > > <path project="Fedora:EPEL:7" repository="standard"/> > <path project="CentOS:CentOS-7" repository="scl-rhscl"/> > <path project="CentOS:CentOS-7" repository="standard"/> > <arch>x86_64</arch> > > </repository> > > That enables EPEL and the RHSCL repository for CentOS 7 on top of the > regular base repo. This is excellent! Thank you very much.
The only issue is that the sync looks outdated. Because my build (osc build ...) wants to download older, already non-existing packages from http://ftp.halifax.rwth-aachen.de/centos/7/sclo/x86_64/rh
actually requested: devtoolset-7-oprofile-1.2.0-1.el7.sc1.x86_64.rpm
but provided: devtoolset-7-oprofile-1.2.0-2.el7.sc1.x86_64.rpm
Is there some auto-update set? nah, that repo gets currently refused, because the gpg for the signature is not matching anymore.
However, I have atm no clue where I can find the official pubkeys from a
proven source for them. They are not listed here at least: https://www.centos.org/keys/
Does ne1 has a clue? The rhscl and sclo repos are done by the Software Collections SIG. So
On Tue, Jan 8, 2019 at 9:32 AM Adrian Schröter <adrian@suse.de> wrote: that GPG key should be valid for it. right, that is the one which is configured ...
however, it seems the signature seems to be broken indeed atm: Which doesn't surprise me, as the sig was made May 2018... So somebody on the centos side screwed up.
(btw, why do we use http://ftp.halifax.rwth-aachen.de instead of http://mirror.centos.org for that repo? Not that it matters, the sig is also wrong on mirror.centos.org)
Is there any chance to get it resolved, please? Eg. to update OBS gpg keyring to accept this key? Or should I contact SCL guys somehow?
I've filed a bug report with the CentOS project about it: https://bugs.centos.org/view.php?id=15732 In the future, when this is discovered, please file a bug report so that they know. -- 真実はいつも一つ！/ Always, there's only one truth! -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
participants (6)
-
Adrian Schröter -
David Adam -
Jan Engelhardt -
Michael Schroeder -
Neal Gompa -
Petr Vanek