July 2008 - openSUSE Build Service - openSUSE Mailing Lists

[opensuse-buildservice] Aggregating from non-standard repository name
by Archie Cobbs 08 Jul '08

08 Jul '08

If you look at the status of the voiceglue package in the network:telephony project on openSUSE_Factory, you will see the build failed because "missing repositories: devel:languages:perl/openSUSE_Factory": https://build.opensuse.org/package/show?package=voiceglue&project=network%3… Here's why.... This RPM needs perl-ExtUtils-CBuilder to build, which is provided by project devel:languages:perl. So it contains an _aggregate: <aggregatelist> <aggregate project="devel:languages:perl"> <package>perl-ExtUtils-CBuilder</package> </aggregate> ... </aggregatelist> But for some reason the "devel:languages:perl" names their factory repository "SUSE_Linux_Factory" instead of "openSUSE_Factory". My questions are: (a) How do I tell the OBS to look in "openSUSE_Factory" instead of "SUSE_Linux_Factory"? (b) Why in the world is that project using a non-standard name? Thanks, -Archie -- Archie L. Cobbs --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

2 2

[opensuse-buildservice] Aggregating from non-standard repository name
by Archie Cobbs 08 Jul '08

08 Jul '08

Marcus wrote: > Btw: why don't you directly build against this repository? This would avoid > package duplicates on the mirrors. Because I was told to... see below. Clearly there is some confusion or disagreement on whether it is better to add a repository to your project or aggregate in order to make BuildRequires RPMs available. Maybe the collective wisdom of this list can come up with a definitive "best practice" here? Thanks, -Archie ---------- Forwarded message ---------- From: Peter Nixon <listuser(a)peternixon.net> Date: Fri, May 23, 2008 at 11:43 AM Subject: Re: Meta-data change for network:telephony To: Archie Cobbs <archie(a)dellroad.org> Cc: max(a)novell.com, mrueckert(a)novell.com, hvogel(a)novell.com, richard.bos(a)xs4all.nl, lurch(a)gmx.li, opensuse.org(a)jerris.com, pvanveen84(a)hotmail.com Archie You are not irritating.. I asked all these questions and more to Darix (mrueckert) and he patiently answered them :-) When you put another project as a dependency of your project in the metadata it will allow your packages to build, but then when someone tries to use your repo to install your package those dependencies will not be supplied if they are needed as "Requires" forcing the user to go off in search of those dependencies too. When you "link" a particular package into your project it is rebuilt which takes up resources on the Build Service but is usefull if you want one of IT'S dependencies to be supplied by a package in your project without touching its spec, or if you want to build for a target which is not enable in it's home project. Once built the package is uploaded to the mirrors which also takes up mirror resources, and it also will have a different build version number which means that you may (or may not) randomly upgrade existing packages of the same name on your users system.. When you "aggregate" a particular package into your project it is not rebuilt, but rather copied directly from its home project. It keeps the same version number, so when it is uploaded to mirrors it does take up resources on them but it will not replace the same package if already installed on a users system (from the parent project). This is the preferred and cleanest way of sucking in a few extra dependencies to your project. I hope that makes things clearer. Regards Peter On Fri 23 May 2008, Archie Cobbs wrote: > On Fri, May 23, 2008 at 2:17 AM, Peter Nixon <listuser(a)peternixon.net> wrote: > > > > It would be much better if you simply aggregated the packages you > > > > require rather than linking in extra entire projects. Look at > > > > the "freeradius-client" package for an example. > > Got it, looks easy. > > What follows is a separate question, feel free to ignore if I'm > starting to get irritating... > > The goal here is simply to have certain RPMs that exist in other > projects (but not in standard SuSE) available as Build-Requires. > > As I understand it, aggregating is akin to copying in a package from > another project into your project. When you aggregate another package > X from project A into project B, then when you search for "X" on > software.opensuse.org, you get a match for "project A package X" and > also "project B package X", and OBS is building package X twice, once > in each project, producing two separate downloadable RPMs. > > On the other hand, I thought that adding another project to your > project (via "osc meta -a PRJ") simply made the RPMs in that other > project available to your project (e.g. for Build-Requires, etc). > I.e., it did the equivalent of "zypper addrepo otherproject" to your > project. The result is that there is no redundant building of any RPM > twice, in contrast to linking/aggregating. > > It to me seems like (since I don't need to modify these RPMs) that the > second option is more sensible than the first. > > Obviously, there is some other cost to the second option that I'm > unaware of. Can you explain what it is? > > Thanks, > -Archie > > -- > Archie L. Cobbs -- Peter Nixon http://peternixon.net/ -- Archie L. Cobbs --------------------------------------------------------------------- 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] eclipse-bs status report, week 27
by Michal Marek 08 Jul '08

08 Jul '08

(sorry for the late report, it's my fault, not long's) [GREEN] - connection wizard to select api server and set user:pass, reads and writes this info from/to .oscrc - dialog to set some more .oscrc options [OUTLOOK] - start writing code for browsing projects / packages --------------------------------------------------------------------- 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] fedora-release in default installs
by Chris Frey 07 Jul '08

07 Jul '08

Hi, Would it be possible to include the fedora-release package in the Fedora repos by default? This would include the /etc/rpm/macros.dist file, which includes the macros %fedora and %fc9 and %fc8. This package is usually installed automatically when installing Fedora through the usual process. It would make it possible to write spec files that build on multiple distros, both inside and outside the Opensuse Build Service. The %fedora_version macro available on OBS is not available on a regular Fedora9 install. Thanks, - Chris --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

3 2

[opensuse-buildservice] obs-api-0.9.99-3.1.noarch.rpm missing files /srv/www/docs !!!
by Christian 07 Jul '08

07 Jul '08

Hi, there are missing files inside "obs-api-0.9.99-3.1.noarch.rpm". complete dir "/srv/www/docs" is missing. Kind regards Chris --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

3 5

[opensuse-buildservice] Expansion error
by Ladislav Michnovič 07 Jul '08

07 Jul '08

Hello. I see in my home project home:lmich expansion error for dist 10.2: expansion error nothing provides xorg-x11-libxcb-devel needed by xosd-devel I have already added substitution in my prjconf: osc meta prjconf home:lmich %if 0%{?suse_version} < 1030 Substitute: xorg-x11-libxcb-devel xorg-x11-devel Substitute: plib-devel plib ... Is it a bug in BS or I'm missing something? Thanks for your hints. Regards Ladislav. --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

2 2

[opensuse-buildservice] config file cleanup
by Susanne Oberhauser 07 Jul '08

07 Jul '08

Hi folks, after some discussions and thinking I propose to clean up the obs config setup as described below. The configs are a little messy, each service doing his own stuff in his own way (just like logging and monitoring, but that's another story). Now here's the challenge I have: The config is central to each service, if I mess it up, it doesn't work any more, and it's easy to mess it up because there is tiny bits of background knowledge you need to have about e.g. rails, and how things are related. So I'm somewhat reluctant to start patching things and messing around with them. I'd like to propose a new scheme anyhow and get hints from you how to migrate there. Proposal: Each service has two or more small config files below /etc/obs, a '.public' one, an optional '.private' one, and if needed additional '.whatsoever' ones. /etc/obs/$SERVICE.{public,private,...} where $SERVICE is one of api webclient scheduler srcserver reposerver worker sign dispatcher publisher hermes The '.public' files are simply copied to all machines that need to know about this specific service. for example the api talks to a local database which belongs just to this api server, so this is configured in /etc/obs/api.private. However the api hostname is needed by several services, so that's in /etc/obs/api.public. Another example are the workers. They need to register with dispatchers and need to talk to srcservers and reposervers, so they read the /etc/obs/{dispatcher,srcserver,reposerver}.public and find all they need in there. I'm unbiassed wether to use yaml or ini style config files, lightweight and full parsers for each exist in all scripting languages, The one thing I know for sure though is that I hardly can clean up the phletora of hard coded URLs and addresses all over the place without breaking everything :( S. =================================================================== I did a little search on candidates that need to use the config. I've looked for the usual suspects as host names, plus for static IPv4 addresses and manually cleaned up the list a bit: cd /space/SVN/opensuse-forge/trunk/buildservice/src svngrep -nE "HOST|(opensuse|suse|novell)\.(de|com|org)|[0-9]\.[0-9]{1,3}\.[0-9]{1,3}\.[0-9]{1,3}" . ./sign/signd:27:my $signhost = '127.0.0.1'; ./sign/signd:212:die("will not proxy to myself\n") if $signhost eq '1270.0.1' && $port eq $proxyport && !$phrases; ./sign/signd:338: die("unknown key: $user\n") if $signhost eq '127.0.01' && $port eq $proxyport; ./sign/sign.conf:2:user: build(a)suse.de ./sign/sign.c:2104: host = strdup("127.0.0.1"); ./clientlib/perl/lib/OpenSUSE/BuildServiceAPI.pm:17:use constant APIHOST => 'api.opensuse.org'; ./clientlib/perl/lib/OpenSUSE/BuildServiceAPI.pm:37: $self->apihost( $param{apihost} || APIHOST ); ./clientlib/python/osc/osc_expand_link.pl:86:$cfg->{apiurl} ||= 'https://api.opensuse.org'; ./clientlib/python/osc/osc/core.py:2993: result.append('http://download.opensuse.org/repositories/%s/' % project.replace(':', ':/')) ./clientlib/python/osc/osc/conf.py:20:{'apisrv': 'https://api.opensuse.org/', ./clientlib/python/osc/osc/conf.py:22: 'auth_dict': {'api.opensuse.org': {'user': 'poeml', 'pass': 'secret'}, ./clientlib/python/osc/osc/conf.py:23: 'apitest.opensuse.org': {'user': 'poeml', 'pass': 'secret'}, ./clientlib/python/osc/osc/conf.py:24: 'foo.opensuse.org': {'user': 'foo', 'pass': 'foo'}}, ./clientlib/python/osc/osc/conf.py:29: 'urllist': ['http://download.opensuse.org/repositories/%(project)s/%(repository)s/%(arch…', ./clientlib/python/osc/osc/conf.py:30: 'http://api.opensuseorg/rpm/%(project)s/%(repository)s/_repository/%(buildar…'], ./clientlib/python/osc/osc/conf.py:42:DEFAULTS = { 'apisrv': 'https://api.opensuse.org/', ./clientlib/python/osc/osc/conf.py:54: 'http://download.opensuse.org/repositories/%(project)s/%(repository)s/%(arch…', ./clientlib/python/osc/osc/commandline.py:903: metadata) on download.opensuse.org. ./clientlib/python/osc/osc/commandline.py:914: url_tmpl = 'http://download.opensuse.org/repositories/%s/%s/%s.repo' ./clientlib/python/osc/osc/commandline.py:1742: sys.stderr.write('See http://download.opensuse.org/repositories/openSUSE:/Tools/\n') ./tools/upstream/import.rb:30:puts ">> Logging into https://api.opensuse.org" ./tools/upstream/oscupstream.rb:15:$api_url="https://api.opensuse.org/" ./tools/upstream/oscupstream.rb:62: # activeServer holds value of "apisrv" or default "api.opensuse.org" ./tools/upstream/config.rb:4: 'host' => 'http://127.0.01:3001' ./tools/eclipse-plugin/org.opensuse.bs.newWizard/src/org/opensuse/bs/newWizard/core/NewWizard.java:154: buf.add("# URL to access API server, e.g. https://api.opensuse.org/"); ./tools/eclipse-plugin/org.opensuse.bs.newWizard/src/org/opensuse/bs/newWizard/core/NewWizard.java:155: buf.add("# you also need a section [https://api.opensuse.org/] with the credentials"); ./tools/eclipse-plugin/org.opensuse.bs.newWizard/src/org/opensuse/bs/newWizard/core/NewWizard.java:156: buf.add("#apisrv = https://api.opensuse.org/"); buf.add(""); ./tools/eclipse-plugin/org.opensuse.bs.newWizard/src/org/opensuse/bs/newWizard/core/BSPage.java:62: "\"api.opensuse.org\". " + ./tools/eclipse-plugin/org.opensuse.bs.ui/src/org/opensuse/bs/wizards/ConnectionWizard.java:133: buf.add("# URL to access API server, e.g. https://api.opensuse.org/"); ./tools/eclipse-plugin/org.opensuse.bs.ui/src/org/opensuse/bs/wizards/ConnectionWizard.java:134: buf.add("# you also need a section [https://api.opensuse.org/] with the credentials"); ./tools/eclipse-plugin/org.opensuse.bs.ui/src/org/opensuse/bs/wizards/ConnectionWizard.java:135: buf.add("#apisrv = https://api.opensuse.org/"); buf.add(""); ./tools/eclipse-plugin/org.opensuse.bs.ui/src/org/opensuse/bs/wizards/BSPage.java:62: "\"api.opensuse.org\". " + ./template-system/apbd.gemspec:19:#spec.hompage = 'http://en.opensuseorg/Abstract_Package_Build_Description' ./obsc/setup.py:27: url='https://forgesvn1.novell.com/svn/opensuse/trunk/buildservice/src/obsc/', ./README.devel:66: server: buildservice.suse.de ./README.devel:72: server: buildservice.suse.de (internal), api.opensuse.org (external) ./README.devel:78: server: buildservice.suse.de (internal), build.opensuse.org (external) ./frontend/vendor/plugins/exception_notification/lib/exception_notifiable.rb:36: addresses = [IPAddr.new("127.0.0.1")] ./frontend/vendor/plugins/exception_notification/README:47: consider_local "64.72.18.143", "14.17.21.25" ./frontend/vendor/plugins/exception_notification/README:52: consider_local "64.72.18.143/24" ./frontend/vendor/plugins/exception_notification/README:54:The address "127.0.0.1" is always considered local. If you want to completely ./frontend/vendor/plugins/exception_notification/README:55:reset the list of all addresses (for instance, if you wanted "127.0.0.1" to ./frontend/config/environments/production_slave.rb:23:# ICHAIN_HOST = "212.12.12.12" ./frontend/config/environments/production_slave.rb:25:SOURCE_HOST = "localhost" ./frontend/config/environments/development.L12.rb:18:SOURCE_HOST = "buildservice.suse.de" ./frontend/config/environments/development.L12.rb:19:#SOURCE_HOST = "localhost" ./frontend/config/environments/production.rb:23:ICHAIN_HOST = "212.1212.12" ./frontend/config/environments/production.rb:25:SOURCE_HOST = "storage" ./frontend/config/environments/stage.rb:22:ICHAIN_HOST = "212.12.12.12" ./frontend/config/environments/stage.rb:25:SOURCE_HOST = "storage" ./frontend/config/environments/development_base.rb:18:SOURCE_HOST = "buildservice.suse.de" ./frontend/config/environments/development_base.rb:19:#SOURCE_HOST = "localhost" ./frontend/config/environments/development_base.rb:26:# If ICHAIN_HOST is set to "simulate", iChain is simulated in the ./frontend/config/environments/development_base.rb:31:# This will replace the old constant ICHAIN_HOST. ./frontend/config/environments/test.rb:22:SOURCE_HOST = "localhost" ./frontend/config/lighttpd.conf:4:server.bind = "0.0.0.0" ./frontend/config/database.yml:21: host: 127.0.0.1 ./frontend/config/database.yml:34: host: 127.0.0.1 ./frontend/README:52:should be on and ".cgi" should respond. All requests from 127.0.0.1 go ./frontend/README:62:on requests from 127.0.0.1. ./frontend/app/controllers/public_controller.rb:111: response = Net::HTTP.start(SOURCE_HOST,SOURCE_PORT) do |http| ./frontend/app/views/ichain_notifier/approval.rhtml:6:http://build.opensuse.org/project/show?project=home%3A<%= @user.login %> ./frontend/app/views/ichain_notifier/approval.rhtml:13: - Ask on the mailinglist (opensuse-buildservice(a)opensuse.org) if you want to ./frontend/app/views/layouts/rbac.rhtml:24: <a href="http://build.opensuse.org">Build Service Web Client</a> | ./frontend/app/views/layouts/rbac.rhtml:27: <a href="http://www.opensuse.org">openSUSE Home</a> ./frontend/app/models/ichain_notifier.rb:6: from 'admin(a)opensuse.org' ./frontend/app/models/ichain_notifier.rb:15: from 'admin(a)opensuse.org' ./webclient/config/environments/production_slave.rb:23:FRONTEND_HOST = "127.0.42.2" ./webclient/config/environments/production_slave.rb:27:BUGZILLA_HOST = "http://my.bugzilla/" ./webclient/config/environments/production_slave.rb:28:DOWNLOAD_URL = "http://127.0.42.3/" ./webclient/config/environments/production.rb:23:FRONTEND_HOST = "api-internal.opensuse.org" ./webclient/config/environments/production.rb:27:BUGZILLA_HOST = "https://bugzilla.novell.com" ./webclient/config/environments/production.rb:28:DOWNLOAD_URL = "http://download.opensuse.org/repositories" ./webclient/config/environments/production.rb:36:### ICHAIN_HOST = "212.12.12.12" ./webclient/config/environments/stage.rb:18:#config.action_controller.asset_host = "https://build.opensuse.org/stage" ./webclient/config/environments/stage.rb:23:FRONTEND_HOST = "api-internal.opensuse.org" ./webclient/config/environments/stage.rb:27:BUGZILLA_HOST = "http://bugzilla.novell.com" ./webclient/config/environments/stage.rb:34:### ICHAIN_HOST = "212.1212.12" ./webclient/config/environments/development_base.rb:20:FRONTEND_HOST = "api.opensuse.org" ./webclient/config/environments/development_base.rb:25:BUGZILLA_HOST = nil ./webclient/config/environments/development_base.rb:32:# If ICHAIN_HOST is set to "simulate", iChain is simulated in the ./webclient/config/environments/development_base.rb:46:### ICHAIN_HOST = "212.12.12.12" ./webclient/config/environments/test.rb:21:FRONTEND_HOST = "localhost" ./webclient/README:52:should be on and ".cgi" should respond. All requests from 127.0.0.1 go ./webclient/README:62:on requests from 127.0.0.1. ./webclient/public/javascripts/prototype.js:1:/* Prototype JavaScript framework, version 1.6.0.1 ./webclient/public/javascripts/prototype.js:10: Version: '1.6.0.1', ./webclient/public/css/local/contentadd_style.css:21: list-style-image:url(http://static.opensuse.org/c/css/common/images/liDot_d…; ./webclient/public/css/local/contentadd_style.css:30: background: #fff url(http://static.opensuse.org/hosts/build.o.o/css/images/darkgrey_searchbo… top left no-repeat; ./webclient/public/css/local/contentadd_style.css:33: background: url(http://static.opensuse.org/hosts/build.o.o/css/images/darkgrey_searchbo… top right no-repeat; ./webclient/public/css/local/contentadd_style.css:36: background: url(http://static.opensuse.org/hosts/build.o.o/css/images/darkgrey_searchbo… bottom left no-repeat; ./webclient/public/css/local/contentadd_style.css:39: background: url(http://static.opensuse.org/hosts/build.o.o/css/images/darkgrey_searchbo… bottom right no-repeat; ./webclient/public/css/local/style.css:10:@import url(http://static.opensuse.org/c/css/yaml/core/base.css); ./webclient/public/css/local/style.css:11:@import url(http://static.opensuse.org/c/css/common/basemod_opensuse.css); ./webclient/public/css/local/style.css:12:@import url(http://static.opensuse.org/c/css/yaml/screen/content_default.css); ./webclient/public/css/local/style.css:13:@import url(http://static.opensuse.org/c/css/common/contentmod_opensuse.css); ./webclient/public/css/local/style.css:14:@import url(http://static.opensuse.org/hosts/build.o.o/css/contentadd_style.css); ./webclient/public/css/local/style.css:15:@import url(http://static.opensuse.org/c/css/common/opensuse_boxes.css); ./webclient/public/css/local/style.css:16:@import url(http://static.opensuse.org/c/css/common/print/print_003.css); ./webclient/public/css/local/style.css:17:@import url(http://static.opensuse.org/hosts/build.o.o/css/patch.css); /* overrides old styles */ ./webclient/public/css/local/style.css:18:@import url(http://static.opensuse.org/hosts/build.o.o/css/dialog.css); /* style for dialog boxes */ ./webclient/app/helpers/application_helper.rb:77: "#{BUGZILLA_HOST}/enter_bug.cgi?classification=7340&product=openSUSE.org&component=3rd%20party%20software&assigned_to=#{email}&short_desc=#{desc}" ./webclient/app/views/main/index.rhtml:14:<%= link_to 'openSUSE Build Service', 'http://en.opensuse.org/Build_Service', ./webclient/app/views/main/index.rhtml:16:It can build packages for <a href="http://en.opensuse.org/Build_Service/cross_distribution_package_how_to">various Linux distributions.</a><br/> ./webclient/app/views/main/index.rhtml:19:<p class="description">Everyone can download the resulting software packages via the <a href="http://software.opensuse.org/search">software search and browsing interface</a>.</p> ./webclient/app/views/main/index.rhtml:67:<a href="mailto:opensuse-buildservice+subscribe@opensuse.org"> ./webclient/app/views/main/index.rhtml:68:opensuse-buildservice@opensuse.org</a> mailing list.<br/> ./webclient/app/views/main/index.rhtml:69:We have also an active IRC channel <a href="irc://irc.opensuse.org/opensuse-buildservice">#opensuse-buildservice</a> running on Freenode.<br/> ./webclient/app/views/main/about.rhtml:6:<p>Check the openSUSE <a href="http://en.opensuse.org/Build_Service"> ./webclient/app/views/main/accountinfo.rhtml:9:to <a href="mailto:admin@opensuse.org">the OpenSUSE Admin</a>. ./webclient/app/views/main/accountinfo.rhtml:14: <a href="http://www.opensuse.org">www.opensuse.org</a> (e.g. for Bugzilla), please ./webclient/app/views/project/new.rhtml:19:Please request a new project via <a href="https://bugzilla.novell.com/enter_bug.cgi?classification=7340&product=openS…">bugzilla</a>. ./webclient/app/views/project/new.rhtml:20:You can also discuss the requested project setup on <a href="mailto:opensuse-buildservice@opensuse.org">opensuse-buildservice(a)opensuse.org</a> ./webclient/app/views/user/edit.rhtml:33: <%= hidden_field_tag( "source_host", "buildservice.suse.de" ) %> ./webclient/app/views/user/edit.rhtml:35: <%= hidden_field_tag( "rpm_host", "buildservice.suse.de" ) %> ./webclient/app/views/user/edit.rhtml:42: <%= hidden_field_tag( "source_host", "buildservice.suse.de" ) %> ./webclient/app/views/user/edit.rhtml:44: <%= hidden_field_tag( "rpm_host", "buildservice.suse.de" ) %> ./webclient/app/views/user/request_ichain.rhtml:13: <a href="mailto:opensuse-buildservice+subscribe@opensuse.org">subscribe</a> to the ./webclient/app/views/user/request_ichain.rhtml:14: <a href="http://lists.opensuse.org/opensuse-buildservice/">buildservice mailing list</a>.</p> ./webclient/app/views/user/request_ichain.rhtml:18: <a href="http://en.opensuse.org/Application_Black_List">http://en.opensuse.org/Application_Black_List</a> ./webclient/app/views/user/request_ichain.rhtml:23: <a href="http://software.opensuse.org/search/">http://software.opensuse.org/search/</a> ./webclient/app/views/layouts/application.rhtml:23: <form id="loginfrm" action="https://build.opensuse.org/ICSLogin/auth-up" method="post" enctype="application/x-www-form-urlencoded"> ./webclient/app/views/layouts/application.rhtml:24: <input type="hidden" name="url" value="http://build.opensuse.org/privacy/ichain_login" /> ./webclient/app/views/layouts/application.rhtml:38: <td><a href="https://secure-www.novell.com/selfreg/jsp/forgotPassword.jsp" onclick="forgotPassword();return false;">forgot password?</a></td> ./webclient/app/views/layouts/application.rhtml:70: { 'The Build Service' => 'http://en.opensuse.org/Build_Service' }, ./webclient/app/views/layouts/application.rhtml:71: { 'Building Packages' => 'http://en.opensuse.org/SUSE_Build_Tutorial' }, ./webclient/app/views/layouts/application.rhtml:72: { 'Writing spec Files' => 'http://forgeftp.novell.com//library/SUSE%20Package%20Conventions/spc.html' }, ./webclient/app/views/layouts/application.rhtml:73: { 'Reporting a Bug' => 'http://en.opensuse.org/Submit_a_Bug' } ./webclient/app/views/layouts/application.rhtml:115: <a href="http://en.opensuse.org/Legal">Legal Information</a> | ./webclient/app/views/layouts/application.rhtml:116: <a href="mailto:webmaster@opensuse.org">Feedback</a> ./webclient/app/views/layouts/application2.rhtml:11: <link href="http://static.opensuse.org/hosts/build.o.o/css/style.css" rel="stylesheet" type="text/css"/> ./webclient/app/views/layouts/application2.rhtml:12: <link href="http://static.opensuse.org/hosts/build.o.o/images/favicon.ico" rel="shortcut icon" /> ./webclient/app/views/layouts/application2.rhtml:14: <link href="http://static.opensuse.org/c/css/common/iehacks_opensuse.css" rel="stylesheet" type="text/css"/> ./webclient/app/views/layouts/application2.rhtml:15: <link href="http://static.opensuse.org/hosts/build.o.o/css/iehacks.css" rel="stylesheet" type="text/css"/> ./webclient/app/views/layouts/application2.rhtml:33: <a href="http://build.opensuse.org"><img src="http://static.opensuse.org/c/images/common/geeko.jpg" alt="openSUSE" /></a> ./webclient/app/views/layouts/application2.rhtml:55: <li style="list-style-image: url(http://static.opensuse.org/c/css/common/images/liDot_download.png)"><a href="http://software.opensuse.org/">Get Software</a></li> ./webclient/app/views/layouts/application2.rhtml:56: <li style="list-style-image: url(http://static.opensuse.org/c/css/common/images/liDot_wiki.png)"><a href="http://en.opensuse.org/">Wiki</a></li> ./webclient/app/views/layouts/application2.rhtml:57: <li style="list-style-image: url(http://static.opensuse.org/c/css/common/images/liDot_build.png)"><a href="http://build.opensuse.org/">Build Software</a></li> ./webclient/app/views/layouts/application2.rhtml:58: <li style="list-style-image: url(http://static.opensuse.org/c/css/common/images/liDot_community.png)"><a href="http://users.opensuse.org/">User Directory</a></li> ./webclient/app/views/layouts/application2.rhtml:59: <li style="list-style-image: url(http://static.opensuse.org/c/css/common/images/liDot_wiki.png)"><a href="http://news.opensuse.org/">News</a></li> ./webclient/app/views/layouts/application2.rhtml:60: <li style="list-style-image: url(http://static.opensuse.org/c/css/common/images/liDot_wiki.png)"><a href="http://forums.opensuse.org">Forums</a></li> ./webclient/app/views/layouts/application2.rhtml:61: <li style="list-style-image: url(http://static.opensuse.org/c/css/common/images/liDot_wiki.png)"><a href="http://shop.opensuse.org/">Shop</a></li> ./webclient/app/views/layouts/application2.rhtml:146: { 'The Build Service' => 'http://en.opensuse.org/Build_Service' }, ./webclient/app/views/layouts/application2.rhtml:147: { 'Building Packages' => 'http://en.opensuse.org/SUSE_Build_Tutorial' }, ./webclient/app/views/layouts/application2.rhtml:148: { 'Writing spec Files' => 'http://en.opensuse.org/SUSE_Build_Tutorial#Specfiles' }, ./webclient/app/views/layouts/application2.rhtml:149: { 'Reporting a Bug' => 'http://en.opensuse.org/Submit_a_Bug' } ./webclient/app/views/layouts/application2.rhtml:256: <option value="http://de.test.opensuse.org/Main_Page">Deutsch</option> ./webclient/app/views/layouts/application2.rhtml:257: <option value="http://fr.test.opensuse.org/Main_Page">FranÃ§ais</option> ./webclient/app/views/layouts/application2.rhtml:296: <a href="http://en.opensuse.org/openSUSE:About">About openSUSE</a> | <a href="http://en.opensuse.org/Legal">Legal information</a> | <a href="mailto:webmaster@opensuse.org">Feedback</a> ./webclient/app/views/layouts/application2.rhtml:299: <a href="http://www.novell.com/linux/"><img src="http://static.opensuse.org/c/images/common/founded_novell.gif" alt="Founded by Novell" /></a> ./webclient/app/views/layouts/application2.rhtml:326: <a href="http://en.opensuse.org/Sponsors"><img src="http://files.opensuse.org/opensuse/en/5/54/Amd.png" title="Sponsored by AMD" alt="Sponsored by AMD"/></a> ./webclient/app/views/layouts/application2.rhtml:327: <a href="http://en.opensuse.org/Sponsors"><img title="Sponsored by: IP Exchange" alt="Sponsored by: IP Exchange" src="http://files.opensuse.org/opensuse/en/b/b6/Ip-exchange.gif"/></a> ./tester/tests/svn_helper:4:svn_remote = "https://forgesvn1.novell.com/svn/opensuse/trunk/buildservice/" ./tester/tests/101.test:9:curl build.opensuse.org >/dev/null ./tester/tests/100.test:9:curl api.opensuse.org ./common/lib/switchtower/configuration.rb:10:set :repository, proc {"--username #{svnuser} https://forgesvn1.novell.com/svn/opensuse/trunk/buildservice/src/#{applicat…"} ./common/lib/switchtower/configuration.rb:15:set :cl_mail_from, "Automated Deploy Message <abauer(a)suse.com>" ./common/lib/switchtower/configuration.rb:18:#set :cl_mail_to, ["abauer(a)suse.de", "cschum(a)suse.de", "freitag(a)suse.de", "cwh(a)suse.de"] ./common/lib/switchtower/configuration.rb:19:set :cl_mail_to, "opensuse-svn(a)forge.novell.com" ./common/lib/switchtower/configuration.rb:22:set :cl_branch_url, proc {"https://forgesvn1.novell.com/svn/opensuse/branches/deploy/#{application}/#{… release_path}"} ./common/lib/switchtower/configuration.rb:26:role :web, "buildserviceapi.suse.de" ./common/lib/switchtower/configuration.rb:27:role :app, "buildserviceapi.suse.de" ./common/lib/switchtower/configuration.rb:28:role :db, "buildserviceapi.suse.de" ./common/lib/switchtower/opensuse.rb:52: Net::SMTP.start('relay.suse.de', 25) do |smtp| ./software/config/environments/development.rb:23:API_HOST = "gacht.suse.de:3001" ./software/config/environments/production.rb:20:API_HOST = "api-internal.opensuse.org" ./software/config/boot.rb:25: # Asking for 1.1.6 will give you 1.16.5206, if available -- makes it easier to use beta gems ./software/config/environment.rb:60: map.default_server :rest, API_HOST ./software/README:69:info will also be shown in the browser on requests from 127.0.0.1. ./software/public/help_media_102.html:56: The <b>Mini CD</b> conatins a bootable system that allows an installation from a network installation repository. This installation method is only recommended for experienced users. More information is available at <a href="http://en.opensuse.org/INSTALL_Internet">Installing openSUSE 10.2 from the Internet</a>. ./software/public/expert.html:17: <a href="http://en.opensuse.org/Mirrors_Released_Version">http://en.opensuse.org/Mirrors_Released_Version</a>. ./backend/License:10: Adrian Schroeter <adrian(a)suse.de> ./backend/bs_repserver:391: # $status->{'uri'} = 'http://192.168.1.102:4711'; ./backend/bs_repserver:1476: $ymp->{'xmlns:os'} = 'http://opensuse.org/Standards/One_Click_Install'; ./backend/bs_repserver:1477: $ymp->{'xmlns'} = 'http://opensuse.org/Standards/One_Click_Install'; ./backend/bs_publish:253: print FILE "gpgkey=http://download.opensuse.org/openSUSE-Build-Service.asc\n"; ./backend/bs_publish:411: $ymp->{'xmlns:os'} = 'http://opensuse.org/Standards/One_Click_Install'; ./backend/bs_publish:412: $ymp->{'xmlns'} = 'http://opensuse.org/Standards/One_Click_Install'; ./backend/XML/Structured.pm:526:Copyright 2006 Michael Schroeder E<lt>mls(a)suse.deE<gt> ./backend/BSConfig.pm:48:#our $stageserver = 'rsync://127.0.0.1/put-repos-main'; ./backend/BSConfig.pm:49:#our $stageserver_sync = 'rsync://127.0.0.1/trigger-repos-sync'; ./backend/BSConfig.pm:52:#our $repodownload = 'http://software.opensuse.org/download/repositories'; ./backend/bs_srcserver:1104: open(F, '-|', $BSConfig::sign, '-P', "$srcrep/:upload/signkey.$$", '-g', @keyargs , "$projid OBS Project", "$projid\(a)build.opensuse.org") || die("$BSConfig::sign: $!\n"); ./backend/README:8: https://forgesvn1.novell.com/svn/opensuse/trunk/buildservice/src/build ./backend_dummy/config/database.yml:13: host: 127.0.0.1 ./backend_dummy/config/database.yml:28: host: 127.0.0.1 ./backend_dummy/config/database.yml:35: host: 127.0.0.1 ./backend_dummy/config/deploy.rb:12:set :repository, "--username #{svnuser} https://svn.suse.de/svn/opensuse/trunk/buildservice/src/#{application}" ./backend_dummy/config/deploy.rb:25:role :web, "buildserviceapi.suse.de" ./backend_dummy/config/deploy.rb:26:role :app, "buildserviceapi.suse.de" ./backend_dummy/config/deploy.rb:27:role :db, "buildserviceapi.suse.de" ./backend_dummy/README:52:should be on and ".cgi" should respond. All requests from 127.0.0.1 go ./backend_dummy/README:62:on requests from 127.0.0.1. -- Susanne Oberhauser +49-911-74053-574 SUSE -- a Novell Business OPS Engineering Maxfeldstraße 5 Processes and Infrastructure Nürnberg SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) --------------------------------------------------------------------- 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] Identify the repository a package comes from
by Nikolay Derkach 07 Jul '08

07 Jul '08

Hi, Is there any way to identify the repository a package bellongs to? The input data is a package with 'openSUSE Build Service' vendor tag in the header. The only way which comes to my mind is to check the GPG key the package is signed with (since it's unique for a repo) and afterwards map that key to a repository. But is there any 'map' actually available? And another question, is it possible to get a package bugowner by any means except parsing the output of 'osc meta'? Maybe any API call? -- Regards, Nikolay Derkach --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

3 2

[opensuse-buildservice] Missing configurations files for fedora repos
by Anas Nashif 06 Jul '08

06 Jul '08

Hi, I am installing a local instance of OBS and while following the instructions to do that I noticed that in /usr/lib/obs/server/build/configs/ there exist many config files for opensuse and other distros but not fedora. Are config files for fedora available somewhere else or is there some other reason why they are missing? Thanks, Anas --------------------------------------------------------------------- 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] Fedora package selection
by Chris Frey 05 Jul '08

05 Jul '08

Hi, This is a question from a Build Service newbie... I'm hoping to use the Build Service to compile multi-platform binaries of the Barry project (http://sf.net/projects/barry) as I'm the upstream developer. There are 3 parts to Barry, one of which is a GUI that depends on packages such as libglademm24-devel to build. These packages are usually available by default, via yum, in Fedora 8, but they don't appear to be available in the Fedora:8 repository in the Build Service. I'm sure I'm just looking in the wrong place. Any pointers would be greatly appreciated. Thanks, - Chris --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

2 4