openSUSE Build Service March 2013

buildservice@lists.opensuse.org

46 participants
43 discussions

[opensuse-buildservice] making SR review easier (was Re: [opensuse-packaging] Review policy)

by Adam Spiers

[setting Cc and Reply-To to the opensuse-buildservice list] Sascha Peilicke (speilicke(a)suse.com) wrote: > On 03/21/2013 09:50 AM, Togan Muftuoglu wrote: > > On 03/21/2013 09:10 AM, Sascha Peilicke wrote: > > > > The reason is I had a declination with a comment why I have not > > > > explained use of %ghost macro in a spec file, but a person who would > > > > have reviewed the rpm buildlogs for the package would realize the fact > > > > that rpmlint gives the following error. > > > > > > Who seriously looks at buildlogs when reviewing requests? > > > > I do and I would expect those who review requests do as well other wise > > why bother in the first place to generate a build log and rpmlint log. > > If the package doesnot build it is recommended to have a look at the > > build log. Well I would assume if it builds fine one still should look > > the logs and especially the rpmlint log > > Well, we review packages building for multiple architectures and a > plethora of distros. Of course I mostly care about openSUSE:Factory > (i586,x86_64) but still. And yes, I look at the rpmlint log for that > target too. And no, I don't look at any build-log. On a calm day, I > review ~50 packages 8-O Wow, I had no idea any one person did that much work! AFAICS, the rpmlint results are only available in two places: - the build log - the Rpmlint Results tab on each package's Overview page Right? And neither of these are formatted in a very nice way. > I simply don't have the time and it makes no > sense either. Packages that don't build are declined by > 'factory-auto' already, packages that build are good enough. I doubt > people would appreciate if we start commenting the fuzzy mess that > build-logs are ;-) Since I am not currently a regular reviewer, feel free to tell me if I'm talking rubbish, but it seems to me that there are some low-hanging fruit changes we could make here to make life much easier for reviewers, e.g.: - Change the Rpmlint Results tab to group warnings/errors by filter type, and just show the number of occurrences in each group. Then you can mouseover or click to see more details. - Add a way to view an rpmlint results summary via osc (is there an API call for this, or do you just have to grep the build log client-side?) - Automatically color the build log according to patterns. - Automatically split the build log into the different phases, e.g. - booting the VM - init_buildsystem etc. - %prep - %build - %install - /usr/lib/rpm/brp-* hooks - autoreqprov calculation - %clean - post-build checks (01-check-debuginfo ... 99-check-remove-rpms) - rpmlint - post-build tasks (e.g. "creating baselibs", "comparing built packages with former built") - VM power down and make each section expandable in the webUI with all sections starting collapsed and colour-coded red/green according to whether the section's contents matched any known failure patterns. (Actually I already have some code which might help implement this last idea.) Maybe an idea for the next hack week? If that makes sense to people then I can submit the idea as a proposal. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

8 years, 6 months

[opensuse-buildservice] Buildservice mirrors?

by Jim Henderson

I'm looking to mirror the Virtualbox_backports repository on the build service, but I seem to keep running into problems with connecting to rsync.opensuse.org (connection slots full or a few other odd issues). When I looked to see what mirrors there are of OBS, the list showed empty - do those repos not get mirrored anywhere? If they do, where can I find a list of them? Thanks, Jim -- Jim Henderson Please keep on-topic replies on the list so everyone benefits -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

8 years, 6 months

[opensuse-buildservice] project config preinstall i686 on x86_64

by Kanstantsin Shautsou

Hello, i have binary imported glibc packages for i686 and x86_64 (from fedora). I'm trying to Preinstall both arches, but it doesn't work. It also don't see Required: glibc(x86-32) or glibc.i686. Any ideas?-- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

8 years, 6 months

[opensuse-buildservice] Link, Aggregate and repositories... which to choose ??

by Gianluca

Dear All, I'm really confused about the documentation of Links, Aggregates and building against more repositories... and I don't know which one fit my situation. I have a project on which I'm building a package named "yarp". This package requires the library ACE and this library has been already packaged by the devel:libraries:ACE:major project. And I want to achieve a self-contained repository for my package yarp in order to just tell to the users to add my project repository without also the need to add the ACE repository. If I specify in my project repositories to use also ACE repository (<path project="devel:libraries:ACE:major" repository="openSUSE_12.3"/>) then the building of yarp package goes well, but the user has to add both ACE and my repository in order to statisfy all requirements and install ACE. I cannot find a way that implicity add also the ACE repository for the user, or that link in some ways the ACE package without wasting space. My first option was to use aggregate, but it is really discouraged its use because not only waste space but there is also a risk of incompatible breakages :-( But I'm not want to use link, because it rebuild the package ... and because I don't need to change anything to ACE, this option will be not only a waste of space but also a waste of building resources So... are there some other options ?? I wondering if there is a simple solution like a symbolic link toward the ACE package, in order to get all requires resolvable when the user add my repository. Is that possible ?? Thanks, Gianluca. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

8 years, 6 months

[opensuse-buildservice] Any docs for development about open build service

by Aaron Yung

Hi All I am curious about the OBS webui communication with the backend api, so I begin to study ROR for some days. Is there a easy way to understand the communication between OBS frontend webui and the backend api , just like some docs about activexml module or for developers? Thanks! ----- Go OBS -- View this message in context: http://opensuse.14.n6.nabble.com/Any-docs-for-development-about-open-build-… Sent from the opensuse-buildservice mailing list archive at Nabble.com. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

8 years, 6 months

[opensuse-buildservice] specfile with internally defined %macro that rep_server doesn't like

by Craig Gardner

Hi fellow OBS experts, I have a problem with a specfile building in my own Build Service, version 2.3.8-ish. I suspect the same thing would happen with this specfile in OBS. Whenever I check in this specfile to my project, the rep_server gets very angry with me and gives me error messages. If fact, the src_server records the exact same messages. <cut> Odd number of elements in hash assignment at build/Build/Rpm.pm line 131, <SPEC> line 257. Use of uninitialized value in concatenation (.) or string at build/Build/Rpm.pm line 365, <SPEC> line 257. Odd number of elements in hash assignment at build/Build/Rpm.pm line 131, <SPEC> line 258. Use of uninitialized value in concatenation (.) or string at build/Build/Rpm.pm line 365, <SPEC> line 258. Odd number of elements in hash assignment at build/Build/Rpm.pm line 131, <SPEC> line 259. </cut> (There are actually more lines, but the text above is sufficient to show the error messages.) Looking at the specfile, the lines implicated took like this: <cut> %package_library cherrypy BSD %package_library django BSD %package_library iso8601 MIT </cut> The %package_library macro is defined as: <cut> %define package_library() \ %define library %1 \ %define license %2 \ %package lib-%{library} \ Summary: Foo Library: %{library} \ Group: Applications/System \ License: %{license} \ %description lib-%{library} \ Foo Shared Library: %{library} \ %files lib-%{library} \ %defattr(-,root,root) \ /%{_lib}/%{library} \ %{nil} </cut> This, of course, is a completely valid specfile when used with rpmbuild. It may not be written according to best practices, but it's entirely valid and very handy shorthand. It's just that the {src,rep}_server clearly don't like it. Is this something that should be filed as a bug in OBS? Any other suggestions on how to address this situation? -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

8 years, 6 months

[opensuse-buildservice] Add optional update for SLES to SUSE:SLE-11:SP2:Update

by Dirk Müller

Hi, could we please add http://download.novell.com/Download?buildid=IxkUO_gjJ4I~ as an additional package to SUSE:SLE-11:SP2:Update in OBS? I'm missing it in one of my projects. Thanks a lot in advance, Dirk -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

8 years, 6 months

[opensuse-buildservice] Replacement for my_work?

by Stephan Kulow

Hi, I have a script to query factory reminder mails and a lot of people seem to rely on them, but some update on build.opensuse.org broke it. Here is my code: my $ua = LWP::UserAgent->new; $ua->timeout(15); $ua->default_header("Accept" => "application/json"); my $mywork = $ua->get("https://build.opensuse.org/home/my_work?user=$user"); unless ($mywork->is_success) { die $mywork->status_line; } -> Here it always dies with a error 500 Please provide a replacement. Greetings, Stephan -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

8 years, 6 months

[opensuse-buildservice] texlive-2012.20120611-20120471.1.x86_64 for openSUSE 12.2 - mf.base missing

by Joerg Emmelmann

Hello! In above package I miss the following file: /var/lib/texmf/web2c/metafont/mf.base I have checked: # rpm -ql texlive-2012.20120611-20120471.1.x86_64 /usr/lib/tlpkg/TeXLive/TLConfig.pm /usr/lib/tlpkg/TeXLive/TLUtils.pm /usr/share/man/man8/public.8.gz /var/adm/update-scripts/texlive-2012.20120611-20120471.1-zypper # rpm -qf /var/lib/texmf/web2c/metafont texlive-filesystem-2012.61-30.1.noarch The package texlive-2011-13.5.1.noarch.rpm belonging to the updates of the openSUSE 12.2 distribution containes this file. Is there any OBS package where I can find this file? Hints: Due to a package dependency of texlive-achemso I cannot use texlive- 2011-13.5.1.noarch.rpm. My colleague which uses the texlive packages wants the font phvr7t and found this issue (see attachment). Thank you. Cheers Joerg -- ---------------------------------------------------------------- Jörg Emmelmann Max-Planck Institut für Intelligente Systeme (früher Max-Planck Institut für Metallforschung) Abt. Dietrich (IT-Gruppe) / Max Planck Institute for Intelligent Systems (formerly Max Planck Institute for Metals Research) Dept. Dietrich (IT-Group) Heisenbergstr. 3 70569 Stuttgart Tel. / phone: +49 711/689-1836 Fax. / fax: +49 711/689-1088 E-Mail / email: emmelmann(a)is.mpg.de ----------------------------------------------------------------

8 years, 6 months

[opensuse-buildservice] New project openSUSE:Current?

by Cristian Morales Vega

Sometimes you have appA in your repo building for both old and new openSUSE versions. appA depends on libA > X, but only the latest openSUSE version provides it. openSUSE <latest-1> came with libA <X-1>. The solution is to package libA > X for the old distributions and usually you do that linking to the devel project. I would like an openSUSE:Current project that would always contains the latest supported version of the packages. Right now the packages from openSUSE:12.1:Update, but once 12.2 is released it should be changed to openSUSE:12.2:Update. This way I could link to those packages instead of linking to the devel project. It would let me compile appA in old distros while giving to the users a libA package that is not soooooo unsupported (this would be officially unsupported anyway, but...). I would like this since it's a single place to change when a new openSUSE version is released (If needed I can do it). Looking at the openSUSE:12.1:Update project metadata I guess it would just need be something like <project name="openSUSE:Current"> <title>Current version of openSUSE</title> <description></description> <link project="openSUSE:12.1:Update"/> <debuginfo> <enable/> </debuginfo> </project> But I'm not sure since I never really saw a doc explaining the meaning of <link> in the *project metadata*, only in _link files. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

8 years, 6 months

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openSUSE Build Service March 2013