January 2020 - openSUSE Build Service - openSUSE Mailing Lists

[opensuse-buildservice] Centos build stuck with "downloading 6 dod packages"
by Johanna Amann 27 Mar '20

27 Mar '20

Hi, I am trying to build a package for CentOS that requires some packages from epel + the developer toolset to be built. I added the repositories in the project meta configuration - which looks like this: <repository name="CentOS_7"> <path project="security:zeek" repository="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> The spec file then require some packages from the repository, speficically: BuildRequires: epel-release kernel-devel cmake3 devtoolset-7 After trying this, the build has been blocked with the status “downloading 6 dod packages”. Could anyone point me to what I am doing wrong? Link to build: https://build.opensuse.org/package/show/home:0xxon:branches:security:zeek-c… Link to project meta: https://build.opensuse.org/projects/home:0xxon:branches:security:zeek-cento… Thanks a lot, Johanna -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

3 10

[opensuse-buildservice] how to restart obs services correctly?
by Stefan Seyfried 27 Feb '20

27 Feb '20

Hi all, last weeks my instance (2.10) had strange problems, often everything was slow / sluggish but the OBS server was more or less idle (I have thrown enough hardware at the problem I guess, 16GB of RAM and 10 VCPUs on a not totally up-to-date intel xeon x5670). Even the webfrontend was not responding and "osc st" for example took many minutes to eventually finish. Investigating, I found lots of "rpc timeout" messages in all services log files. Just restarting some of them (src server, scheduler) seemed to fix the issue often, but then it reappeard a day or a week later. Finally I just rebooted the whole server, now everything is fine again. I also enabled $logtimeout =1 in BSRPC.pm, even before rebooting. It looked like communication with bs_srcserver was the one that timed out, and from my hopeless tries in stracing the issue I'd guess some lock around the lastevents file was the problem. I think that this was caused by restarting services in the wrong order, which was finally "fixed" by rebooting the server. Is there a recommended way to restart all services without rebooting the server? Or is a reboot the simplest way to achieve that ;-) Thanks, seife -- Stefan Seyfried "For a successful technology, reality must take precedence over public relations, for nature cannot be fooled." -- Richard Feynman -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

5 7

[opensuse-buildservice] AlpineLinux and OBS
by David Sugar 21 Feb '20

21 Feb '20

This is just to raise the question to simply initiate a discussion, why not have AlpineLinux on OBS too? On the positive side, it should be relatively easy to adapt since it is really rather similar to Arch, which is already supported on OBS, but simpler. On the other hand, unlike Arch, it also has 6 month releases that are supported for 2 years. I do appreciate those would accumulate over time. It also has a lot more architectures supported. So I do appreciate that it could also become a maintenance time sink in OBS. Also, I have no sense of the real size of the AlpineLinux using community, and I suspect most use it from the docker and container perspective, which is a valid and potential community that could benefit from OBS. In my particular case, I do use Alpine very broadly, and specifically for headless arm/IoT devices.-- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

4 8

[opensuse-buildservice] OBS on Kubernetes
by Moritz Röhrich 03 Feb '20

03 Feb '20

Dear OBS Maintainers, I am running a deployment of OBS on a Kubernetes cluster. In particular, I am running a horizontal pod autoscaler, that creates more worker pods as-needed and removes them when they have been idle for long enough. This works reasonably well, but leaves a lot of 'dead' workers lingering in the build status page, since Kubernetes assigns new unique pod names every time a pod is created. Is there a way to configure OBS to assume a worker is not coming back if it has not been reachable some time? Best regards, Moritz -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 2

[opensuse-buildservice] osc use_keyring without windowmanager
by Joop Boonen 01 Feb '20

01 Feb '20

Dear all, I would like to use osc with use_keyring without a windowmanager i.e. on a server without X/wayland. Is this possible as according to the documentation [1]. use_keyring only supports (For KDE the KWallet is used, for GNOME it is Seahorse.). I've currently have a windowmanager installed on my server VM but I don't want this anymore as it makes the server slower, uses more resources and uses more power. Regards, Joop. [1] https://openbuildservice.org/help/manuals/obs-user-guide/cha.obs.osc.html -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

4 6

[opensuse-buildservice] OBS in cold start after regression
by Adrian Schröter 31 Jan '20

31 Jan '20

Hi, we had a serious regression in spec file parser of OBS since yesterday. We need therefore a cold start of the schedulers to get into guaranteed clean state again. sorry adrian -- Adrian Schroeter <adrian(a)suse.de> Build Infrastructure Project Manager SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany (HRB 247165, AG München), Geschäftsführer: Felix Imendörffer -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 2

[opensuse-buildservice] Re: [opensuse-factory] OBS in cold start after regression
by Adrian Schröter 31 Jan '20

31 Jan '20

On Freitag, 31. Januar 2020, 12:27:42 CET Aleksa Sarai wrote: > On 2020-01-31, Adrian Schröter <adrian(a)suse.de> wrote: > > we had a serious regression in spec file parser of OBS > > since yesterday. > > > > We need therefore a cold start of the schedulers to get into > > guaranteed clean state again. > > I hate to add more fuel to the fire -- but it looks like OBS is down > now? I get "Sorry, our script crashed." errors after a really long > timeout. The storage was not able to handle the load of all the scheduler cold starts... We do it incremental now. -- Adrian Schroeter <adrian(a)suse.de> Build Infrastructure Project Manager SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany (HRB 247165, AG München), Geschäftsführer: Felix Imendörffer -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

1 0

[opensuse-buildservice] Issues with python3-beautifulsoup4
by Hamish MB 31 Jan '20

31 Jan '20

Hi all, Apologies if this is the wrong place to send. I've been having an issue where packages built in OBS suddenly depend on python3dist(bs4) instead of python3-beautifulsoup4 or another package that exists, does anyone know why this might be? I assume it's something wrong in my spec file. This never used to happen though, and now it happens for both Fedora 30 and 31. Can anyone give me any advice? Thanks, Hamish McIntyre-Bhatty

3 2

[opensuse-buildservice] Centos8: nothing provides libperl
by Mathias Radtke 28 Jan '20

28 Jan '20

Hi did something change in the Centos8 Repositories used by the OBS? Just checked and almost every package complains about not providing libperl.so.5.26 and perl-Encode(x86-64). Howevery none of these packages has these dependencies. Regards Mathias -- Mathias Radtke Save the Date: opsi-Konferenz 2 Tage Workshops, Konferenz und Best Practice bei der opsiconf in Mainz am 2./3.März 2020 weitere Infos und Anmeldung unter opsiconf.org opsi - Open PC-Server-Integration das Open Source Client-Management-System von uib gmbh Birgit Hubal Vertrieb / Projektkoordination eMail: b.hubal(a)uib.de Tel. +49 6131 / 27561-18 Fax +49 6131 / 27561-22 uib gmbh Bonifaziusplatz 1B 55118 Mainz Internet: https://uib.de https://opsi.org Geschäftsführer: Dr. Detlef Oertel, Erol Ülükmen Handelsregister: Amtsgericht Mainz HRB 6942 -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 4

[opensuse-buildservice] Question about usage of 'osc build' and building dependent packages
by Michael Pujos 22 Jan '20

22 Jan '20

Hi, I am a bit new to osc and OBS and for now I'm just building RPMs locally for openSUSE TW using 'osc build' Under my home:<account> folder, I have 2 packages: libfoo and foo. I created a .spec for libfoo and have it built successfully with 'osc build'. Now I want to build foo and made a .spec for it. It depends on libfoo and the .spec references it but I can't understand how to have the RPMS generated for libfoo to be installed in the chroot for foo which are necessary for it to compile. I can manually install libfoo RPMs with 'osc shell' but they are removed when building foo (and --noinit does not help). My guess is that this approach is wrong. So what is the proper workflow to build dependent packages locally ? Eventually I plan to have it built by OBS but I would like to avoid it without having stuff working locally first (if possible)... -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 2

[opensuse-buildservice] Build issues with Ubuntu 17.04 and 17.10
by Dirk Stöcker 22 Jan '20

22 Jan '20

Hello, I have setup repositories for Ubuntu 17.04 and 17.10 like this: <repository name="Ubuntu_17.10"> <path project="Ubuntu:17.10" repository="universe"/> <arch>x86_64</arch> <arch>i586</arch> </repository> <repository name="Ubuntu_17.04"> <path project="Ubuntu:17.04" repository="universe"/> <arch>x86_64</arch> <arch>i586</arch> </repository> When I try to build against it locally I get errors like this: 17.04: Server returned an error: HTTP Error 404: remote error http //ftp.heanet.ie/mirrors/ubuntu/pool/main/f/fonts-freefont/fonts-freefont-ttf_20120503-6_all.deb remote error Not Found 17.10: Server returned an error: HTTP Error 404: remote error http //ftp.halifax.rwth-aachen.de/ubuntu/pool/universe/t/texlive-lang/texlive-lang-german_2017.20170818-1_all.deb remote error Not Found I also tried adding "update" or "standard" or only using "standard". The missing files change, but the result is the same. I can't build. I can build fine for all openSUSE as well as for Ubuntu 18.04 and 16.04. Is Ubuntu 17 somehow corrupted in OBS? There usually are files with another version available at the download places. The data to download and the version information in OBS don't seem to match. Ciao -- http://www.dstoecker.eu/ (PGP key available) -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

3 8

[opensuse-buildservice] OSB Debian InRelease signature
by Michael Ströder 21 Jan '20

21 Jan '20

HI! Thanks for also providing Debian support on OBS. I'm starting to use it and it builds my packages just fine. I'd also like to use download.opensuse.org directly as apt repo (Debian 10 aka buster). But when adding the repo to Debian with correct key "apt update" complains about missing signatore for InRelease (probably wants InRelease.gpg). The work-around is to add the repo with option [trusted=yes] but obviously this is not what anybody wants. Where should I file ticket for this? Ciao, Michael. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 2

[opensuse-buildservice] Missing 2.10.1 release in OBS:Server:2.10?
by Stefan Seyfried 16 Jan '20

16 Jan '20

Hi all, see $subject, should OBS:Server:2.10 get some updates from time to time? The 2.10.1 release is now 5 months old already ;-) Have fun, seife -- Stefan Seyfried "For a successful technology, reality must take precedence over public relations, for nature cannot be fooled." -- Richard Feynman -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

3 4

[opensuse-buildservice] %dist rpm macro for Fedora 31 resolves to .fc30
by Fritz Elfert 15 Jan '20

15 Jan '20

Subject says it all. Should resolve to .fc31 Cheers -Fritz -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

3 2

[opensuse-buildservice] Release trigger via token behaves differently than releasing via osc.
by Stefan Seyfried 14 Jan '20

14 Jan '20

Hi all, I'm running obs 2.10 in a private instance. I have a problem with releasing binaries via token. My setup is: Project Foo-Cloud:testing with a setup like <project name="Foo-Cloud:testing"> <title>Foo-Cloud testing</title> <description>All package updates get tested here before submitting tobasic prj</description> <person userid="seife" role="bugowner"/> <person userid="seife" role="maintainer"/> <debuginfo> <enable/> </debuginfo> <repository name="SLES15"> <releasetarget project="Foo-Cloud" repository="SLES15" trigger="manual"/> <path project="Foo-Cloud" repository="SLES15"/> <arch>x86_64</arch> </repository> <repository name="SLES12-SP1"> <path project="SLES12-SP1" repository="standard"/> <arch>x86_64</arch> </repository> <repository name="SLES12"> <releasetarget project="Foo-Cloud" repository="SLES12" trigger="manual"/> <path project="Foo-Cloud" repository="SLES12"/> <arch>x86_64</arch> </repository> <repository name="SLES11-SP4"> <releasetarget project="Foo-Cloud" repository="SLES11-SP4" trigger="manual"/> <path project="Foo-Cloud" repository="SLES11-SP4"/> <path project="devel_languages:go" repository="SLES11-SP3"/> <arch>x86_64</arch> </repository> <repository name="SLES11-SP3"> <releasetarget project="Foo-Cloud" repository="SLES11-SP3" trigger="manual"/> <path project="Foo-Cloud" repository="SLES11-SP3"/> <arch>x86_64</arch> </repository> <repository name="SLES11-SP2"> <releasetarget project="Foo-Cloud" repository="SLES11-SP2" trigger="manual"/> <path project="Foo-Cloud" repository="SLES11-SP2"/> <arch>x86_64</arch> </repository> <repository name="SLES11-SP1"> <releasetarget project="Foo-Cloud" repository="SLES11-SP1" trigger="manual"/> <path project="Foo-Cloud" repository="SLES11-SP1"/> <arch>x86_64</arch> </repository> </project> "Foo-Cloud" is similar. The package looks like: <package name="foo-api-reference-client" project="Foo-Cloud:testing"> <title>foo-api-reference-client</title> <description>Will be released via "osc release" to Foo-Cloud!</description> <person userid="service_trigger" role="maintainer"/> </package> The package in Foo-Cloud: <package name="foo-api-reference-client" project="Foo-Cloud"> <title>foo-api-reference-client</title> <description>Will be released via "osc release" to Foo-Cloud!</description> <person userid="service_trigger" role="maintainer"/> <build> <disable/> </build> </package> (I'm just transitioning from "build(testing)->submitrequrest->build" to "build and release via token") The tokens of user service_trigger look like: <directory count="2"> <entry id="94" string="FQ2dYeUS1VQSR7VQgnWE9iMa" kind="runservice" project="Foo-Cloud:testing" package="foo-api-reference-client"/> <entry id="95" string="oFzZnPriT4SKZiArh5vnaqpT" kind="release" project="Foo-Cloud:testing" package="foo-api-reference-client"/> </directory> Build is triggered via OBS_TOKEN_RUN=FQ2dYeUS1VQSR7VQgnWE9iMa curl -f -X POST -H "Content-Type: application/octet-stream" -H "Authorization: Token $OBS_TOKEN_RUN" https://obs/trigger/runservice This works well. Release is the same: OBS_TOKEN_REL=oFzZnPriT4SKZiArh5vnaqpT curl -f -X POST -H "Content-Type: application/octet-stream" -H "Authorization: Token $OBS_TOKEN_REL" https://obs/trigger/release However, this triggers only the release of one repository, SLES11-SP1, and then stops. If I run "osc release" as the service_trigger user, then it works fine and all repos are released. I'm lookint ath the "matched_repo?" function in src/api/app/controllers/trigger_controller.rb, wondering if it is doing everything correctly, but I don't grok enough ruby on rails to judge ;-) Any hints? Best regards, seife -- Stefan Seyfried "For a successful technology, reality must take precedence over public relations, for nature cannot be fooled." -- Richard Feynman -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 3

[opensuse-buildservice] Broken project "SUSE:SLE-12:SLE-Module-Web-Scripting" on build.opensuse.org prevents builds at our federated OBS instance for SLE_12?
by Lorenz Hüdepohl 13 Jan '20

13 Jan '20

Dear group, I noticed that we can no longer build packages in our own federated OBS instance for all SLE_12 repositories. I believe this seems ultimately to be related to an issue with the project "SUSE:SLE-12:SLE-Module-Web-Scripting" on build.opensuse.org, which has the status: "The repository setup is broken, build or publish not possible". Our local projects have an entry <repository name="SLE_12_SP4"> <path project="openSUSE.org:SUSE:SLE-12-SP4:GA" repository="standard"/> <arch>x86_64</arch> </repository> in their project meta ("openSUSE.org" is of course our configured interconnect to "https://api.opensuse.org/public"). The corresponding project meta for "SUSE:SLE-12-SP4:GA/standard" references repositories from "SUSE:SLE-12:SLE-Module-Web-Scripting", and in our scheduler_x86_64.log I find entries such as - software/System: openSUSE.org:SUSE:SLE-12:SLE-Module-Web-Scripting: \ 503 remote error: Service Unavailable Is there something we can do at our end to fix this or has this to be dealt with at build.opensuse.org? Feel free to ask for any further information necessary to help to resolve this! Kind regards and thank you for your time, Lorenz Hüdepohl -- Dr. Lorenz Hüdepohl Max Planck Computing and Data Facility -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 2

[opensuse-buildservice] Arch Linux support
by Adrian Schröter 10 Jan '20

10 Jan '20

Hi, OBS was not able to build for Arch Linux since december. That was caused by the new zstd based compression archives. We have added support for that now and the Arch jobs should continue soon. Please note that you need some more stuff for Arch local builds now. Take the not yet released packages for osc build libarchive bsdtar from OBS:Server:Unstable if you need Arch local builds right now. Have a nice weekend adrian -- Adrian Schroeter <adrian(a)suse.de> Build Infrastructure Project Manager SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany (HRB 247165, AG München), Geschäftsführer: Felix Imendörffer -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

1 0

[opensuse-buildservice] KDE: projects
by Mathias Homann 09 Jan '20

09 Jan '20

Hi, KDE:Qt5, KDE:Frameworks5 and KDE:Applications are still being built for Leap 15.0, but not yet for LEap 15.2 ... Cheers MH -- Mathias Homann Mathias.Homann@openSUSE:.org irc: [Lemmy] @ freenode, ircnet obs: lemmy04 keybase: https://keybase.io/lemmy gpg key fingerprint: 8029 2240 F4DD 7776 E7D2 C042 6B8E 029E 13F2 C102 -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 1

[opensuse-buildservice] Re: arm builds on local OBS
by Andreas Schwab 08 Jan '20

08 Jan '20

On Dez 06 2019, Srivats P wrote: > What is unclear to me at this point is qemu-linux-user is needed for which > distro/arch? Raspbian10/x86_64? I can't seem to find this on build.opensuse > .org You need to aggregate it from openSUSE:Factory/qemu:linux-user/standard/x86_64. Andreas. -- Andreas Schwab, SUSE Labs, schwab(a)suse.de GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7 "And now for something completely different." -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

3 19

[opensuse-buildservice] Unresolvable module packages in CentOS 8
by Ondrej Musil 08 Jan '20

08 Jan '20

I have some packages in a project which need packages from the CentOS 8 module streams, but these packages are unresolvable even though they are available in the CentOS 8 repos. I have found before that I need to use the "ExpandFlags: module-xxx" directive in the Project Configuration, and for example adding "ExpandFlags: module:python36-3.6" worked for packages requiring Python for me. But now I need JDK 1.8.0 for one package and even though I added "ExpandFlags: module:javapackages-runtime-201801", the package "javapackages-filesystem" is unresolvable. And in a package requiring either "mariadb-devel" or "mysql-devel", both of these are unresolvable, even after adding "ExpandFlags: module:mariadb-10.3" and "ExpandFlags: module:mysql-8.0". This is my C8 meta setup BTW: <repository name="CentOS_8"> <path project="openSUSE.org:CentOS:CentOS-8" repository="baseos"/> <path project="openSUSE.org:CentOS:CentOS-8" repository="appstream"/> <path project="openSUSE.org:CentOS:CentOS-8" repository="extras"/> <path project="openSUSE.org:CentOS:CentOS-8" repository="powertools"/> <path project="openSUSE.org:Fedora:EPEL:8" repository="CentOS"/> <arch>x86_64</arch> </repository> Is this a bug or do I need to set up something in project configuration? Best regards Ondrej M. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

1 0

[opensuse-buildservice] Cannot create new project in self-hosted OBS 2.11
by Ondrej Musil 08 Jan '20

08 Jan '20

Hello everyone, I cannot create a new project in our OBS instance via the web UI. When I try it, it just shows a page with 500: Internal Server Error after sending the request. This used to work just fine before. The only mention about it in the logs I could found is this in /srv/obs/log/src_server.log: 2020-01-08 06:58:52: [2461] GET (192.168.20.190) /source/abcde/_project/_history?deleted=1 And then in the /srv/www/obs/api/log/apache_access.log: 192.168.214.3 - - [08/Jan/2020:06:58:44 +0000] "GET /project/new HTTP/1.1" 200 2877 192.168.214.3 - - [08/Jan/2020:06:58:52 +0000] "POST /project/create HTTP/1.1" 500 4322 And some error in /srv/www/obs/api/log/production.log: https://gist.github.com/omusil24/aafe398bde1acd4bc4c20333d2dd7dd1 The system is a VM made using the OBS 2.10 Appliance iso, running OpenSuse 15.1. I updated the whole system just yesterday, so OBS version is 2.11~alpha.20200106T110100.2104ff17ec-lp151.9451.1. But it didn't work even before the update, when there was version 2.11~alpha.20191204T172817.a980c45881-lp151.9306.2. Also, I noticed some errors about SSL certs in apache_error.log, that might be related to this: [Wed Jan 08 06:47:58.856442 2020] [ssl:warn] [pid 1773] AH01909: api:443:0 server certificate does NOT include an ID which matches the server name I believe I set up the correct address everywhere in config though. Am I supposed to run some special rake task or something like that? I tried running the following, but I don't know if that did anything useful: RAILS_ENV="production" rake writeconfiguration And I also restarted the VM several times after changing the config files. Can anyone help me with this? Thank you, and best regards. Ondrej M. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 3

[opensuse-buildservice] NVidia repository signature failure
by Todd Rme 07 Jan '20

07 Jan '20

I am getting the following issue with the NVidia repository with YaST2: An error occurred during repository initialization. [NVidia|https://download.nvidia.com/opensuse/tumbleweed] Valid metadata not found at specified URL History: - Signature verification failed for repomd.xml - Can't provide /repodata/repomd.xml Has the signature changed or is there another issue? -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

1 0

[opensuse-buildservice] Arch:Community builds stuck in downloading dod packages
by Dmitry Ivanov 07 Jan '20

07 Jan '20

Hello, I noticed that some days ago Arch:Community builds for my project suddenly got stuck in "blocked" state with tool tip in web interface saying "downloading 21 dod packages". It's been like that for several days already and it doesn't seem like it's making any progress. Here's my project: https://build.opensuse.org/project/show/home:d1vanov:quentier-development. Here's the Arch part from my meta: <repository name="Arch"> <path project="Arch:Community" repository="standard"/> <arch>x86_64</arch> </repository> I noticed the problem some days ago, before that it used to work fine. Could you please advise if I can do anything on my side to resolve it? Thanks, Dmitry. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 1

[opensuse-buildservice] about prjconf
by Christian 07 Jan '20

07 Jan '20

Hi, am trying to do this in my prjconf (home:computersalat:lap) %if 0%{?is_opensuse} && 0%{?sle_version} >= 150000 %if 0%{?is_opensuse} && 0%{?sle_version} == 150100 Release: lp151.<CI_CNT>.<B_CNT>.CS %endif %if 0%{?is_opensuse} && 0%{?sle_version} == 150200 Release: lp152.<CI_CNT>.<B_CNT>.CS %endif %endif but it is not working ... hence I tried a local build with a modified spec %install echo 0%{?sle_version} and builds for Leap-15.0 will show echo 0150000 and builds for Leap-15.1 will also show echo 0150100 I did as shown in: https://en.opensuse.org/openSUSE:Build_Service_cross_distribution_howto built packages look like: heimdall-1.4.2-lp150.1.4.x86_64.rpm but should look like: heimdall-1.4.2-lp150.1.4.CS.x86_64.rpm Can someone please explain me what I am doing wrong ? Thank you -- Christian ------------------------------------------------------------ https://join.worldcommunitygrid.org?recruiterId=177038 ------------------------------------------------------------ http://www.sc24.de - Sportbekleidung ------------------------------------------------------------

1 0

[opensuse-buildservice] bouncing messages when sent from unknown[2620:113:80c0:8::18]
by Christian 06 Jan '20

06 Jan '20

Hi, can you please fix DNS: 2020-01-02T00:00:10.190836+00:00 vssys002 postfix/smtpd[23654]: warning: hostname static.opensuse.org does not resolve to address 2620:113:80c0:8::18 2020-01-02T00:00:10.191211+00:00 vssys002 postfix/smtpd[23654]: connect from unknown[2620:113:80c0:8::18] 2020-01-02T00:00:10.226956+00:00 vssys002 postfix/smtpd[23654]: NOQUEUE: reject: RCPT from unknown[2620:113:80c0:8::18]: 550 5.7.25 Client host rejected: cannot find your hostname, [2620:113:80c0:8::18]; from=< opensuse-security-announce+bounces-probe-chris=computersalat.de(a)opensuse.org> to=<chris(a)computersalat.de> proto=ESMTP helo=<hydra.opensuse.org> Thank you -- Christian ------------------------------------------------------------ https://join.worldcommunitygrid.org?recruiterId=177038 ------------------------------------------------------------ http://www.sc24.de - Sportbekleidung ------------------------------------------------------------

1 0

[opensuse-buildservice] Debian Testing builds fail
by Rosanne DiMesio 05 Jan '20

05 Jan '20

https://build.opensuse.org/project/show/Emulators:Wine:Debian Worked fine yesterday, today everything fails with: [ 30s] [ 3.430388] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00007f00 [ 30s] [ 3.430388] [ 30s] [ 3.431423] CPU: 4 PID: 1 Comm: build Not tainted 4.12.14-lp151.28.36-default #1 openSUSE Leap 15.1 [ 30s] [ 3.432413] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.12.0-0-ga698c89-rebuilt.opensuse.org 04/01/2014 [ 30s] [ 3.433627] Call Trace: [ 30s] [ 3.433707] dump_stack+0x5c/0x86 [ 30s] [ 3.433707] panic+0xd5/0x233 [ 30s] [ 3.433707] ? perf_event_exit_task+0xc9/0x360 [ 30s] [ 3.433707] do_exit+0xb8a/0xb90 [ 30s] [ 3.433707] ? __do_page_fault+0x256/0x4c0 [ 30s] [ 3.433707] do_group_exit+0x3a/0xb0 [ 30s] [ 3.433707] SyS_exit_group+0x10/0x20 [ 30s] [ 3.433707] do_fast_syscall_32+0xba/0x230 [ 30s] [ 3.433707] entry_SYSCALL_compat_after_hwframe+0x52/0x5a [ 30s] [ 3.433707] Kernel Offset: disabled [ 30s] [ 3.433707] Rebooting in 1 seconds.. [ 31s] ### VM INTERACTION END ### [ 31s] No buildstatus set, either the base system is broken (kernel/initrd/udev/glibc/bash/perl) [ 31s] or the build host has a kernel or hardware problem... -- Rosanne DiMesio <dimesio(a)gmail.com> -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 4

[opensuse-buildservice] i586 FAudio packages for Debian & Ubuntu shown as excluded
by Rosanne DiMesio 04 Jan '20

04 Jan '20

So, overnight my previous problem with i586 Wine packages for Debian, Ubuntu and Fedora being stuck in disabled seems to have been solved. But now there is another problem: my i586 FAudio packages in the same projects show as "excluded" and the previously-built packages are gone from the repository. As a result, the i586 wine-devel and wine-staging packages for Debian 10, Ubuntu 18.04, and Ubuntu 19.04 are unresolvable because nothing provides libfaudio-dev. I did not "exclude" the FAudio packages; can someone please unexclude them? I also just checked the wine-stable packages in my Fedora and Debian Wine projects, and the i586 packages are stuck in disabled just like the wine-devel and wine-staging were previously. I don't need to build a new version of wine-stable at the moment, but will soon when Wine 5.0 is released, so that needs to be fixed, too. This problem came on suddenly; it seems as if someone changed a setting somewhere. Please change it back. Everything in Emulators:Wine:Fedora and Emulators:Wine:Debian is either a Wine package or a package needed for Wine, and all are needed in both i586 and x86_64. -- Rosanne DiMesio <dimesio(a)gmail.com> -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

1 0

[opensuse-buildservice] i586 Fedora, Ubuntu, and Debian repositories are stuck in disabled
by Rosanne DiMesio 04 Jan '20

04 Jan '20

All my i586 repositories in https://build.opensuse.org/package/show/Emulators:Wine:Debian/wine-devel and https://build.opensuse.org/package/show/Emulators:Wine:Fedora/wine-devel are stuck in disabled, even though they are enabled for those packages. I tried adding BuildFlags: onlybuild:wine-devel to the project config, and it didn't help. -- Rosanne DiMesio <dimesio(a)gmail.com> -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

1 0