January 2020 - openSUSE Build Service - openSUSE Mailing Lists

[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