April 2011 - openSUSE Build Service - openSUSE Mailing Lists

[opensuse-buildservice] Re: [PATCH] [api] update_workerstatus runs for all users
by Sascha Peilicke 05 Apr '11

05 Apr '11

Ich war durch Zufall auch grad an diesem Code, wie kann den ein Cache-Lookup einen Zlib::GzipFile::Error werfen? > - begin > - data = Rails.cache.read(key) > - rescue Zlib::GzipFile::Error > - data = nil > - end > - unless data > - data = update_workerstatus_cache > + begin > + data = Rails.cache.read('workerstatus') > + rescue Zlib::GzipFile::Error > + data = nil > + end -- Mit freundlichen Grüßen, Sascha Peilicke SUSE Linux Products GmbH

1 0

[opensuse-buildservice] 504 Gateway Time-Out on https://build.opensuse.org/
by doiggl＠velocitynet.com.au 05 Apr '11

05 Apr '11

Hello, Anyone else getting the error [1] when connecting to https://build.opensuse.org/ Glenn [1] 504 Gateway Time-Out Unable to connect to origin web server. The web site you are attempting to access is currently unreachable. This may be due to a network outage, or the web site might be experiencing technical difficulties. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

4 3

[opensuse-buildservice] Local OBS: bad config SUSE:SLE-10:SP4:SDK
by Marcel Ritter 05 Apr '11

05 Apr '11

Hi, we're running a local instance of the opensuse build service (2.1.6) and we're trying to build kernel modules against the SLES 10 SP4 repo(s) "SUSE:SLE-10:SP4"/"SUSE:SLE-10:SP4:SDK" However the scheduler keeps complaining about "bad config (openSUSE.org:SUSE:SLE-10:SP4)" and refuses to build any packages. Same setup works fine for SLES 10 SP3. Any ideas? Bye, Marcel -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

3 3

Re: [opensuse-buildservice] Signing key for packages from OBS
by Peter Albrecht 04 Apr '11

04 Apr '11

Sorry, should have gone here as well. ---------- Weitergeleitete Nachricht ---------- Betreff: Re: [opensuse-buildservice] Signing key for packages from OBS Datum: Montag, 4. April 2011 Von: Peter Albrecht <albrecht(a)opensourceservices.de> An: Michael Schroeder <mls(a)suse.de> Hi Michael, > > I am looking for the gpg key which has been used to sign a package > > from OBS. Any idea where the keys are located? > > The public key should be stored in the repository. Thanks, that's what I was looking for. > > I am specifically looking for the key for the proftpd package for SLE > > 11 SP1. rpm --checksig returns "MISSING KEYS: GPG#807cc84a". Any help > > is appreciated. > > I don't think SLE11SP1 contains a proftpd package. What build service > project are you talking about? Correct, SLE 11 does not contain proftpd. I use this package for training purposes. When I talk about software installation using rpm, I use this package for several reasons (showing scripts included in a package, checking the signature, etc). The project is this: https://build.opensuse.org/project/show?project=server%3Aftp Thanks again, Peter -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

2 1

[opensuse-buildservice] Signing key for packages from OBS
by Peter Albrecht 04 Apr '11

04 Apr '11

Hi, I am looking for the gpg key which has been used to sign a package from OBS. Any idea where the keys are located? I am specifically looking for the key for the proftpd package for SLE 11 SP1. rpm --checksig returns "MISSING KEYS: GPG#807cc84a". Any help is appreciated. Thank you, Peter -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

2 1

[opensuse-buildservice] <link project> and submitrequests
by Wolfgang Rosenauer 04 Apr '11

04 Apr '11

Hi, I just learned in another thread that for linked packages the release numbering doesn't work as expected. Now I have the issue that I need to have that numbering reliable what means that I cannot do submitrequests into that target project as it creates those links automatically. That is likely caused by the prj config: <link project="xyz"> I need to use in that project to have the correct chain for branching non-existing packages out of that project. Is there a solution for that situation? I used to do copypacs but that only works when the package is added the first time. Thanks, Wolfgang -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

1 0

[opensuse-buildservice] automatic release numbering
by Wolfgang Rosenauer 04 Apr '11

04 Apr '11

Hi, I know this is frequently asked and I pretty much understand how it works but I currently see one issue: The example is the avahi package in project openSUSE:Evergreen:11.1 All spec files in the package have Release: 9.<RELEASE12> But the build logs show: I have the following modifications for avahi.spec: 36c36 < Release: 9.<RELEASE12> --- > Release: 9.6.1 Could somebody please explain or rather tell me how to fix it? The other following issue has been an issue for a long time but I'm not sure I reported it in detail yet. I regularly notice that in devel:tools:scm/mercurial: It gets patch level updates pretty often and currently has (according to the specfile) Version: 1.8.1 Release: 1 as it was updated a few days ago with the new 1.8.1 version. Still OBS internally always increases the "source change" count: I have the following modifications for mercurial.spec: 32c32 < Release: 1 --- > Release: 42.1 It _seems_ to me that it's happening only for branched/linked packages against openSUSE:Factory (or probably any other link target) but still it looks wrong to me. Wolfgang -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

3 3

[opensuse-buildservice] Fedora 14 and KDE version
by Gerd Fleischer 04 Apr '11

04 Apr '11

Hi, I build a kde-dependent package for fedora 14. The obs is using kde 4.5.2, the original version for Fedora 14. If you install everything from the update repository you end up with kde 4.6.1 currently. AFAIK they are not always binary compatible? However, I think the different versions are causing problems. Gerd -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

2 1

[opensuse-buildservice] Release from prjconf does not override Release from rpm spec
by Olaf Hering 03 Apr '11

03 Apr '11

If the prjconf contains 'Release: <CI_CNT>.<B_CNT>.foo' and a specfile contains 'Release: <CI_CNT>.<B_CNT>.bar' the resulting package will not get 'foo' in its rpm release number. Shouldnt the global Release: override anything that happens to be in the Release line in the specfiles? I consider the current behaviour a bug, as seen in 'home:olh > hello_world'. Olaf -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

1 0

[opensuse-buildservice] nothing provides licenses?
by Gerd Fleischer 02 Apr '11

02 Apr '11

Hi, I have a package that does not build for factory, error message is "nothing provides liceses", how to add them? Thanks, Gerd -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

3 2