November 2010 - openSUSE Build Service

[opensuse-buildservice] OBS build takes wrong if clause
by Volker Stoppe 08 Nov '10

08 Nov '10

Hallo list! I am new to the OpenSuSE Build Service and I was given the task, to extend a spec-file to build the zabbix-package also for CentOS. Therfor I built an if-query with ?centos_version, as described in http://de.opensuse.org/Build_Service/Pakete_f%C3%BCr_mehrere_Distributionen… The packaged for the default distribution builds well (sles) but the build for CentOS fails with the message: "nothing provides tcpd-devel, nothing provides apache2-devel, nothing provides iksemel-devel, nothing provides pkg-config, nothing provides httpd_devel" This is our own OBS but the administrator ensured that the system is able to build CentOS-packages. Below is an excerpt of my spec-file. Can someone explain me why the build of the centos-packages queries the dependencies from "if %suse_version"? ---- snip ---- # BuildRequires: libssh2-devel # BuildRequires: net-snmp-devel # BuildRequires: OpenIPMI-devel # BuildRequires: openldap2-devel # BuildRequires: postgresql-devel # BuildRequires: sqlite-devel # # %if 0%{?suse_version} < 1020 # BuildRequires: curl-devel mysql-devel tcpd-devel apache2-devel iksemel-devel pkg-config # %else # BuildRequires: fdupes libcurl-devel libmysqlclient-devel apache2-devel iksemel-devel pkg-config # %endif # # %if 0%{?centos_version} >= 501 # BuildRequires: httpd_devel iksemel-devel # %endif ---- snap ---- The CentOS-repo is added for my zabbix project: ----- snip ----- CentOS_CentOS-5 (i586, x86_64) openSUSE.org:CentOS:CentOS-5/standard ----- snap ----- This version of our OBS is: Repository: SLE-11-SDK-SP1 Name: obs-server Version: 1.7.2-0.2.32 Architektur: x86_64 If someone could give me a hint to the problem I would be very thankful! Greetings vst -- 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] The disconnect
by Robert Schweikert 08 Nov '10

08 Nov '10

Hi, Something has been troubling me for a while and I was a bit confused about things. But now, I can finally put my finger on where from my perspective things break down. This might turn out to be a bit of a lengthy message; thus, please bear with me. I followed a relatively recent and very lengthy discussion thread that started out on a specific topic and eventually hit on the build service, philosophical discussions about other distributions and our lack of packages in contrib etc. (the thread was not on an openSUSE list :( ). At some point, the discussion also hit the height of the entry barrier for contributions. While in general I have to agree, the barrier for openSUSE package contribution is pretty low, it just dawned on me today where things are amiss, at least from my perspective. Let me try and use an example to illustrate the problem I think exists. A while back I packaged perl-critic and it's dependencies, starting out in my home project to make sure all is well and then I submitted everything to devel:languages:perl. From there I figured the packages would eventually find their way into the distribution automagically, or at the vary least into contrib. Well, that didn't happen. Based on a mail on the packaging list I guess what I need to do to get things into the distribution is to have another sr for the packages to the openSUSE:Factory project. But, that I cannot do as I am not a maintainer of devel:languages:perl. Now, I'd have to get added as a maintainer in that project and then do an sr for perl-critic and dependencies. Then rinse and repeat for any packages I might submit to other top level projects. Generally this is not really that bad, but it involves extra steps that are not necessarily obvious, and IMHO there is a disconnect. In my mind, when I submitted the packages to devel:languages:perl I was done. done meaning, I made a contribution to openSUSE, and the packages will be available to users that just configure "standard" repositories. What was left to do was to check back every few month and see if the packages needed a version bump. There was no indication that I needed to take a second, third, and forth step to make the packages available outside the devel project. This might be evident (or buried) in some wiki page, but I do not recall reading it, and looking for this type of info recently yielded nothing. Therefore, I claim that if it happened to me it will happen to other people. The possible result being that they might walk away and be lost as contributors. While I can understand that we might not want to pull everything that lurks in a devel project into the "standard" distribution I think we should strongly consider putting all those packages automagically into contrib. Here is how I think this might work. When a release is being created, first beta time frame I'd say, scan all the packages that are in devel projects or other projects that are not home: and check if the package builds for the targeted distribution (openSUSE 11.3 or Factory etc.). If the build succeeds and the package is not part of the "standard" distribution, then put the package into contrib automatically. The advantage of this is that a contributor that stops at step 2, i.e. gets the packages out of his/her home project and into a higher level project such as devel:languages:XXX or virtualization will be able to see/use the packages as part of the extended distribution (base repo + contrb). In addition, users can access the packages without having to add moving targets, i.e. devel projects, as update repositories to their systems. Last but not least this automatic collection will bolster the number of packages available through "standard" repositories and thus will bolster openSUSE. Also something the marketing team will be able to exploit ;) . Contributors that want packages in the "base" repo will still need to take the extra steps. A bit easier to find or more obvious documentation might be helpful there. The short summary/request is: Collect all packages that successfully built for a given distribution that reside in projects outside of home: and stick them into contrib: One of the gory details would be to skip packages in projects like "bleeding-edge" during the automatic collection. But I beleive there is already a flag for things like that already, if I recall a discussion on this list correctly. Robert -- Robert Schweikert MAY THE SOURCE BE WITH YOU Software Engineer Consultant LINUX rschweikert(a)novell.com 781-464-8147 Novell Making IT Work As One -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

12 28

[opensuse-buildservice] openSUSE Build Service 2.1 Release
by Andreas Jaeger 08 Nov '10

08 Nov '10

The openSUSE Build Service - OBS - is now officially at release 2.1. We're delighted with the improvements in this release, including an enhanced web interface, integration with online code management systems and better access controls. OBS 2.1 Introduces New Features =========================== Enhanced web user interface This iteration has enhanced the web user interface of openSUSE Build Service with features that were previously only in the osc command line client. It now allows submitting of packages to other projects, showing a history of changes and who did them, with associated comments. This means that the full work flow needed to build packages, contribute them to projects and collaborate on them is available from the web interface. Integration with online source code management tools Users of the Build Service may now access a new concept called 'source services'. Source services allow, for example, the automatic checkout of source code for a package from a remote server via Git or Subversion, building a tar ball from these checked out sources, and using them for building a package. It also enables direct download of tar balls from remote sites. This allows packagers to work with external sources without downloading them to their own workstations, and makes it easy to rebuild packages after upstream changes with a single click. Better access controls The access controls have been enhanced so that read/write access to a project can be granted on an individual basis. This allows for tighter control of work flows where needed. You can for example ensure people don't have access to security updates while they are being tested. Using OBS ========= To use the Open Source Build Service, you can access the public instance on build.opensuse.org or install it on your own hardware to have a private Build Service. For local installations you can install from source, or use the ready-to-run appliance image, either directly or in a virtual machine. You can also obtain an installation image to install an openSUSE 11.3 system with the Build Service pre-installed. For details check http://en.opensuse.org/openSUSE:Build_Service_installations For more information about the Build Service, check http://en.opensuse.org/Portal:Build_Service. Thanks ====== This release of the OBS has received many contributions from other companies, community members and foundations, making this release a truly collaborative product. We would like to thank everyone who helped make the openSUSE Build Service 2.1 possible! Special thanks go to Martin Mohring and the OBS team at The Linux Foundation, who contributed the extended access handling. About the Build Service ================== The Build Service is an open package and distribution development platform providing a transparent infrastructure for developers to build packages for a variety of Linux distributions and hardware architectures. build.opensuse.org is a freely available service and can build packages for the most popular distributions besides openSUSE including SUSE Linux Enterprise, Debian, Fedora, Mandriva, Red Hat Enterprise Linux and Ubuntu. The Build Service aims to significantly reduce the costs and risks related to the distribution of applications, from building, providing and maintaining them. It does so by providing a convenient web and command-line interface, which developers can use to upload their code and build instructions. The Build Service will then create a clean, virtualized operating system, install any required build dependencies and create the package. This process will be repeated for each supported operating system. Once the build is finished, all packages will be made available in a set of repositories for easy distribution. The Build Service at build.opensuse.org currently builds about 100,000 packages from 25,000 users working on 15,000 different projects. Communities and companies using their own Build Service installation include the MeeGo Project, VLC team, Dell, Cray and many others. For more information about the Build Service, check http://en.opensuse.org/Portal:Build_Service. -- Andreas Jaeger, Program Manager openSUSE, aj(a){novell.com,opensuse.org} Twitter: jaegerandi | Identica: jaegerandi SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126 -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

7 10

[opensuse-buildservice] Help there's a problem with https://build.opensuse.org/package/show? action menu.
by Dave Plater 08 Nov '10

08 Nov '10

I am getting very frustrated with the build service : I can work around checkin to newly relinked packages that wants to mangle my spec file and delete the contents of local copies but now I'm pulling my hair out. I cannot access the "Alter Package Information" item in the "Actions" menu link in the overview page, "only report bug", in packages where I'm maintainer but not a project maintainer. I can alter the information via "osc meta pkg graphics openCOLLADA -e" and it appears after about 15 min to 1 hour but I cant do anything in the web ui except report a bug to myself. I tried a message to the build service list. This morning (UTC +2) I tried the #opensuse-buildservice irc and I got this : <davepl> Hi, can somebody help with a bug in the webui part of the build service. I can only access report bug on the action menu, when logged in via https://build.opensuse.org/ and https://build.opensuse.org/stage/. This happens in all packages where I'm package maintainer but not a project maintainer. ie. The Action menu link on the overview page in "multimedia:libs jack" gives me : report bug, delete package, edit package [11:12] <davepl> information, submit package, branch package and a second report bug at the bottom.The Action menu link on the overview page in "graphics blender" gives me : report bug only. I'm a project maintainer in multimedia:libs but only a package maintainer of graphics blender. I can use the command line osc meta pkg graphics openCOLLADA -e (the package I actually want to change) and the change goes through and further command line [11:12] <davepl> osc meta pkg shows the change but I can't see it in the web ui (yet). If I try "osc meta pkg graphics dcraw -e" I get "no permission to change package" which is expected. So we aren't back to normal. [11:12] [404] davepl #opensuse-buildservice Cannot send to channel [11:12] [404] davepl #opensuse-buildservice Cannot send to channel [11:12] [404] davepl #opensuse-buildservice Cannot send to channel [11:14] <-> nickserv> help register [11:14] [Notice] -NickServ- ***** NickServ Help ***** [11:14] [Notice] -NickServ- Help for REGISTER: [11:14] [Notice] -NickServ- [11:14] [Notice] -NickServ- This will register your current nickname with NickServ. [11:14] [Notice] -NickServ- This will allow you to assert some form of identity on [11:14] [Notice] -NickServ- the network and to be added to access lists. Furthermore, [11:14] [Notice] -NickServ- NickServ will warn users using your nick without [11:14] [Notice] -NickServ- identifying and allow you to kill ghosts. [11:14] [Notice] -NickServ- The password is a case-sensitive password that you make [11:14] [Notice] -NickServ- up. Please write down or memorize your password! You [11:14] [Notice] -NickServ- will need it later to change settings. [11:14] [Notice] -NickServ- [11:14] [Notice] -NickServ- You have to confirm the email address. To do this, [11:14] [Notice] -NickServ- follow the instructions in the message sent to the email [11:14] [Notice] -NickServ- address. [11:14] [Notice] -NickServ- [11:14] [Notice] -NickServ- Syntax: REGISTER <password> <email-address> [11:14] [Notice] -NickServ- [11:14] [Notice] -NickServ- Examples: [11:14] [Notice] -NickServ- /msg NickServ REGISTER bar foo(a)bar.com [11:14] [Notice] -NickServ- ***** End of Help ***** [11:16] <davepl> /msg NickServ REGISTER davepl1954 davejplater(a)gmail.com [11:16] [404] davepl #opensuse-buildservice Cannot send to channel My nick is davepl and has been for a long time. This is taking up my precious time. Please help, a bug report about build service takes a life time. I think it was just last weekend I couldn't log in for a day until it was fixed which put me back with packages I was working on. Dave P user plater -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

3 4

[opensuse-buildservice] How can I add two reposities in config.kiwi
by caoshouying 08 Nov '10

08 Nov '10

Hi, all I want build a kiwi image with OBS, I edited the file config.kiwi and added reposities. It failed when I used two reposities. I combined two reposities , and it work right. But I want to know how to add two reposities. Thanks! kevin -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

2 1

Re: [opensuse-buildservice] Help there's a problem with https://build.opensuse.org/package/show? action menu.
by Sascha Peilicke 08 Nov '10

08 Nov '10

Hi Dave, > The last bug I made for build service was ignored, I will search for it > when I have time, I think it's still open but fixed a long time ago. In general, we don't ignore bugs. It may take some time to fix them though. Can you post the bugno. of the one you think is fixed already? > The > build service irc used to be a place to get help but now it's a closed > shop that I can't get into. As said, IMO this relates to recent auth changes on FreeNode. Try registering with SASL instead of NickServ. > What product do I submit a bug against? Ok I've found Build Service > under openSUSE.org. That's perfectly fine, but please don't file multiple bugs for the same issue. This only takes time for us to triage and mark as duplicates. Hey, we're an opensource project, so patience is key sometimes :-) BTW. I'm already looking into your issue. -- Mit freundlichen Grüßen, Sascha Peilicke http://saschpe.wordpress.com

2 1

[opensuse-buildservice] Ubuntu 10.10 Repository on build.opensuse.org
by Fritz Elfert 08 Nov '10

08 Nov '10

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, Just a shot question: Are there any plans to add Ubuntu 10.10 to the list of available repositories? Thanks in advance -Fritz -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iD8DBQFMuQ83boM4mAMyprARAu2fAJ9/bfyJ237nm5kkcvokxwvEmNvpXwCeOYGl 6GTQd2EOxM5QTfx+P821JfM= =jHOs -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

5 8

[opensuse-buildservice] eta to Fedora:14?
by Robert Xu 08 Nov '10

08 Nov '10

Hi all, I know it's hard work to do, but when will the Fedora:14 build target become available? -- later, Robert Xu -- 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] Licensing - CC BY-NC-SA
by Nelson Marques 07 Nov '10

07 Nov '10

Dear people, I'm asking this because one of my favorite metathemes for GNOME is CC-BY-NC-SA. What concerns me is the 'NC' which I'm not sure if because of it I can distribute it through OBS as a package. Though this is a personal reason, I usually push some packages to Contrib or other projects, since it's stuff I keep updated for myself. Anyone could clear out this licensing issue around CC BY-NC-SA. Thanks in advance, Nelson -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

1 1

[opensuse-buildservice] I'm unable to access anything but report a bug in the Action menu in web ui in packages that I maintain but am not a project maintainer.
by Dave Plater 07 Nov '10

07 Nov '10

Hi, I wanted to beautify the graphics openCOLLADA description in the web ui and when clicking the Actions menu all I get is "report bug" as if I'm not logged in. I checked multimedia:apps where I'm a project maintainer and I get a full menu as with my home project but KDE:Extra kid3, graphics blender and openCOLLADA and openSUSE:Factory:Contrib bacula where I'm only the package maintainer - nothing but report bug :-( Thanks in advance for fixing it. Dave P -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

1 2