openSUSE Build Service November 2013

buildservice@lists.opensuse.org

50 participants
55 discussions

Re: [opensuse-buildservice] Stalled submit requests

by Matwey V. Kornilov

Hm... You have inspired me to try this on the coming weekend. :) With obs rest/xml api, I need a tiny python script to manage all the things out. It is easy, you're right. 2012/10/18 Jos Poortvliet <jos(a)opensuse.org>: > On Sunday, October 07, 2012 12:09:43 Matwey V. Kornilov wrote: > >> Hi, > >> > >> Is there a page to see full list of submit requests, ordered by date? This > >> statistics is of quite interest. > >> > >> For instance, there is no reaction for two month: (It is not ok for devel: > >> project, I think) > >> > >> >> https://build.opensuse.org/project/requests?project=network%3Amessaging%3Aam > >> qp > >> > >> I think, having such a page, such statistics, one would be able to > >> redistribute his power. > > > > Not a bad idea at all - it'd nice to show which projects need some help, > which are doing very well etcetera. Maybe a top-ten of fastest SR/MR > solvers, too ;-) > > > > Crazy idea: Adrian responded to you that it is possible to request this info > from the API. If you got the skillzz to do that, it'd be nice to publish > those statistics somewhere - and that part I could help with. Something like > a weekly overview of the health of the OBS projects and stuff like that. > > > > Up for it? > > > > /Jos -- With best regards, Matwey V. Kornilov http://0x2207.blogspot.com xmpp:0x2207@jabber.ru -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

5 years, 9 months

Open Build Service(OBS) 2.3.4 released

by Adrian Schröter

Open Build Service(OBS) 2.3.4 just got released =============================================== This is a bugfix release in first place. But also the distribuition default target list has been updated. This release is most important for cross build support. Building against openSUSE 12.2 and Factory for ARM architecture works now out-of-the-box. OBS 2.3.4 is published in "openSUSE:Tools" project: http://download.opensuse.org/repositories/openSUSE:Tools/ Appliances can be used as usual: http://en.opensuse.org/openSUSE:Build_Service_Appliance Release Notes: ============== Feature backports: ================== * Added "Hostarch" in _buildinfo for osc local builds of cross builds Changes: ======== * package meta creation of package copy command is not copying relationships and devel definitions anymore. * Added openSUSE 12.2 to default target list * Removed openSUSE 11.4 from default target list (EOL soon) * Fedora 15 is EOL, removed from default list Bugfixes: ========= * backend: allow access to access protected project repositories when users are in both projects. * backend: increase vrev on package source copy * webui: fixed underscores in code listings * webui: Do not expose user email address in anonymous mode * obsworker: do not fail when no /etc/sysconfig/proxy exists * build: fixed cross architecture initilisation for chroot builds -- Adrian Schroeter SUSE Linux Products GmbH email: adrian(a)suse.de -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

5 years, 9 months

OBS and package version number

by Henri Gomez

Hi to all, I'm new to OBS and started to use it to package some stuff from my GitHub repo : https://github.com/hgomez/devops-incubator For one package, mynexus (https://build.opensuse.org/package/show/home:henri_gomez:devops-incubator/m…), I created this _service : <services> <service name="tar_scm"> <param name="scm">git</param> <param name="url">https://github.com/hgomez/devops-incubator.git</ param> <param name="versionformat">2.6.3</param> </service> <service name="recompress"> <param name="compression">gz</param> <param name="file">*.tar</param> </service> <service name="extract_file"> <param name="archive">*devops-incubator*.tar.gz</param> <param name="files">devops-incubator*/rpm-packaging/mynexus/SOURCES/*</param> <param name="files">devops-incubator*/rpm-packaging/mynexus/SPECS/*.spec</param> </service> <service name="download_url"> <param name="host">download.sonatype.com</param> <param name="protocol">http</param> <param name="path">/nexus/oss/nexus-2.6.3-01.war</param> <param name="filename">nexus-2.6.3.war</param> </service> <service name="download_url"> <param name="host">archive.apache.org</param> <param name="protocol">http</param> <param name="path">/dist/tomcat/tomcat-7/v7.0.47/bin/extras/catalina-jmx-remote.jar</param> <param name="filename">catalina-jmx-remote-7.0.47.jar</param> </service> <service name="download_url"> <param name="host">archive.apache.org</param> <param name="protocol">http</param> <param name="path">/dist/tomcat/tomcat-7/v7.0.47/bin/apache-tomcat-7.0.47.tar.gz</param> </service> <service name="set_version"> </service> </services> But I'm wondering with version produced is not 2.6.3 but 2.6.32.6.3-13.1 ie : https://build.opensuse.org/package/live_build_log/home:henri_gomez:devops-i… Advices very welcomed Thanks -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

6 years, 12 months

Fedora19 libjpeg hassles

by Fritz Elfert

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi guys, As you might know, Fedora replaced libjpeg by libjpeg-turbo some releases ago. Until up to F18, they kept the package-names however. Now, with F19, they renamed the *package* libjpeg to libjpeg-turbo. This package still provides /usr/lib{64}/libjpeg.so.62 et. al. This appears to confuse OBS quite a bit: Just an example my EHS package. It BuildRequires doxygen and graphviz which triggers all the following For 32bit: nothing provides libjpeg.so.62 needed by graphviz, nothing provides libjpeg.so.62 needed by gdk-pixbuf2, nothing provides libjpeg.so.62(LIBJPEG_6.2) needed by gdk-pixbuf2, nothing provides libjpeg.so.62 needed by gd, nothing provides libjpeg.so.62(LIBJPEG_6.2) needed by gd, nothing provides libjpeg.so.62 needed by ghostscript, nothing provides libjpeg.so.62(LIBJPEG_6.2) needed by ghostscript, nothing provides libjpeg.so.62 needed by libtiff, nothing provides libjpeg.so.62(LIBJPEG_6.2) needed by libtiff, nothing provides libjpeg.so.62 needed by jasper-libs, nothing provides libjpeg.so.62(LIBJPEG_6.2) needed by jasper-libs For 64bit: nothing provides libjpeg.so.62()(64bit) needed by graphviz, nothing provides libjpeg.so.62()(64bit) needed by gdk-pixbuf2, nothing provides libjpeg.so.62(LIBJPEG_6.2)(64bit) needed by gdk-pixbuf2, nothing provides libjpeg.so.62()(64bit) needed by gd, nothing provides libjpeg.so.62(LIBJPEG_6.2)(64bit) needed by gd, nothing provides libjpeg.so.62()(64bit) needed by ghostscript, nothing provides libjpeg.so.62(LIBJPEG_6.2)(64bit) needed by ghostscript, nothing provides libjpeg.so.62()(64bit) needed by libtiff, nothing provides libjpeg.so.62(LIBJPEG_6.2)(64bit) needed by libtiff, nothing provides libjpeg.so.62()(64bit) needed by jasper-libs, nothing provides libjpeg.so.62(LIBJPEG_6.2)(64bit) needed by jasper-libs I tried to work around that, using a custom buildconfig, however then I also have some packages which actually need libjpeg. E.g: There is my OpenNX package which BuildRequires: wxGTK-devel which in turn requires libjpeg. It fails during linkage (despite using my custom projconf below): ... [ 295s] CXXLD opennx [ 297s] /bin/ld: warning: libjpeg.so.62, needed by /usr/lib/gcc/i686-redhat-linux/4.8.1/../../../libwx_gtk2u_xrc-2.8.so, not found (try using -rpath or -rpath-link) [ 297s] /usr/lib/gcc/i686-redhat-linux/4.8.1/../../../libwx_gtk2u_core-2.8.so: undefined reference to `jpeg_finish_decompress(a)LIBJPEG_6.2' ... even though I can see in the build log that libjpeg-turbo-devel gets installed before the build starts. The package builds fine on a local F19 machine. This is the custom prjconf which I tried to use. %if "%_repository" == "Fedora_19" Required: libjpeg-turbo Keep: libjpeg-turbo Substitute: libjpeg libjpeg-turbo Substitute: libjpeg-devel libjpeg-turbo-devel Ignore: libjpeg.so.62 Ignore: libjpeg.so.62(LIBJPEG_6.2) Ignore: libjpeg.so.62()(64bit) Ignore: libjpeg.so.62(LIBJPEG_6.2)(64bit) Ignore: libjpeg = 6b:java-1.7.0-openjdk %endif Can any admin perhaps tweak the global config for Fedora19 in a way that OBS "knows" about which package provides libjpeg.so.62 ? Thanks -Fritz -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.15 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlKSnqkACgkQboM4mAMyprC7BACgitidEgJBtJes+nQyFnLqNlUR wNcAniWgqOgo3fbpHxmaWgP9FDWEWFke =ZAc7 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

6 years, 12 months

Problem with SLE targets only (error: Installed (but unpackaged) file(s) found)

by Guillaume Gardet

Hi, I need PHP 5.4 for SLE 11 SP2, so I am trying to build it. It builds fine for openSUSE but fails for SLE 11 with "error: Installed (but unpackaged) file(s) found:". %files sections are defined and it works for openSUSE targets. Do I miss something? If you want to have a look at the spec file, it is here: https://build.opensuse.org/package/show/home:Guillaume_G:branches:Applicati… Guillaume -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

6 years, 12 months

OBS and maintenance workflow?

by Guillaume Gardet

Hi, I need to submit an update for openSUSE 13.1. If I try to submit it to openSUSE:13.1:Update, I get the following error: ******************************************************************************** Unable to submit: The target project openSUSE:13.1:Update is a maintenance release project, a submit self is not possible, please use the maintenance workflow instead. ******************************************************************************** How should I proceed? Guillaume -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

6 years, 12 months

Failed to remove target repository

by Malcolm

Hi In my project; https://build.opensuse.org/project/repositories/home:malcolmlewis:SLE_11_SP… I'm try to remove the SLE 11 SP2 repository via the web UI, I however get the error "Failed to remove target 'SLE_11_SP2' Unable to delete repository; following repositories depend on this project: home:tom_enos/SLE_11_SP2" This repository/project doesn't seem to exist anymore? https://build.opensuse.org/project/repositories/home:tom_enos/SLE_11_SP2 Can someone remove, or is it possible to force via osc locally? -- Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890) SLED 11 SP3 (x86_64) GNOME 2.28.0 Kernel 3.0.101-0.8-default up 3 days 20:29, 2 users, load average: 0.23, 0.42, 0.56 CPU Intel® B840(a)1.9GHz | GPU Intel® Sandybridge Mobile -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

6 years, 12 months

not all binaries being published

by Darin Perusich

Hello All, The i586 and x86_64 binary packages for the check_mk package in server:monitoring are not being published but all the noarch packages are, and this is only in the openSUSE 13.1 repository. I triggered a rebuild yesterday which completed successfully but nothing was published. The build and publish flags for the repo and package are enabled for 13.1 so I have not idea what would cause this. Can someone from the build service team take a look at this or tell me what, if anything, I can do as a maintainer to fix this? -- Later, Darin -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

6 years, 12 months

autoreconf missing in build

by Hans-Peter Jansen

Hi, while at it, I find it a little surprising (again), that a package like python3 cannot be built in a new project due to a missing autoconf package. https://build.opensuse.org/project/monitor/home:frispete:python3 https://build.opensuse.org/package/live_build_log/home:frispete:python3/pyt… Is that to be expected? IOW, do I really need to adjust projects with something like Preinstall: autoconf in prjconf? Cheers, Pete -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

6 years, 12 months

Small webui gitch in repository operations

by Hans-Peter Jansen

Hi, now, that adding a new (openSUSE) repo results in adding them for all possible archs, which I find - ähem - surprising, there's a small webui glitch in correcting that for more than one arch: Say you add 2 repos, now you want to edit both to remove the arm targets: click on the first edit repo link and remove the unwanted archs, click on the second edit repo link and remove the unwanted archs as well. The Update button keeps disabled: you need to reload the page between each repo edit. Cheers, Pete -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

6 years, 12 months

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openSUSE Build Service November 2013