December 2008 - openSUSE Build Service

[opensuse-buildservice] sles-release package for SLE_10
by Kevin James 09 Dec '08

09 Dec '08

Hi, Is there a reason why the package sles-release isn't included in the SLE_10 repository? I'm compiling a third party package and the setup checks for /etc/SuSE-release to do some work. for openSuSE_11.0 the openSuSE-release package is available for the BuildRequires: in the spec file, but for SLE_10 the sles-release package (that's installed on a SLES 10 VM I checked) that's in the BuildRequires: gives the following error: buildinfo is broken... it says: expansion error: nothing provides sles-release Cheers, KEv. -- Kevin James Applied Technology Senior Strategist Novell Global Enablement ------------------------ Novell, Inc. http://www.novell.com -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

1 0

Re: [opensuse-buildservice] New repositories excluded
by Kevin James 08 Dec '08

08 Dec '08

project home:rincewind23, package all except perl-XML-XPath (which is aggregated from elsewhere). Cheers, KEv. On Mon, 2008-12-08 at 13:53 -0300, Cristian Rodríguez wrote: > Kevin James escribió: > > > > > I haven't excluded anything, and I can't see anything in any of my spec > > files that would limit build to SuSE only. Anyone tell me what I'm doing > > wrong? > > Please tell us exact package name and project. > > -- Kevin James Applied Technology Senior Strategist Novell Global Enablement ------------------------ Novell, Inc. http://www.novell.com -- 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] New repositories excluded
by Kevin James 08 Dec '08

08 Dec '08

Hi all, One of the packages I'm trying to build with the build service for openSuSE 11.0 isn't compiling properly. The author of the package, on his mailing lists, says that the project compiles fine on his Ubuntu system, so I tried to add the Ubuntu 8.04 repository to my home project to see if I can figure out the difference. I did this, but it now says that all of my packages are excluded on this repository (except one, which is aggregated from another project). I haven't excluded anything, and I can't see anything in any of my spec files that would limit build to SuSE only. Anyone tell me what I'm doing wrong? Cheers, Kev. -- Kevin James Applied Technology Senior Strategist Novell Global Enablement ------------------------ Novell, Inc. http://www.novell.com -- 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] Czech Packagers Team - Virtual Packages
by Stanislav Brabec 08 Dec '08

08 Dec '08

Here is my proposal for a new Build Service feature that may prevent linking packages or projects just for rebuild with a new version. Virtual packages and virtual joint projects =========================================== Virtual packages and virtual joint project would be a special type of projects, that are part of a standard binary repository, but they have no source present in the project. It may have several typical use cases: Virtual dependency packages --------------------------- When a project intents to update a library to a newer version, virtual dependency packages and projects may determine packages that will have broken/changed dependencies after installing of a new library. How it should look. Either package or a project should have a new attribute: "Rebuild parent project packages" Possible values: "ignore": Rebuild only packages in this project and nothing else (just the current behavior) "rebuild broken": Rebuild parent project packages, that cannot be used with newer version any more (it typically happens for package, that require exact version it is built against, or packages that don't follow shared library packaging conventions) "smart rebuild": Rebuild packages that require package or symbol that are no more part of the output of the new package. "all dependencies": Behave just like a single repository and rebuild everything which uses the new in the build. Examples of use for particular values: "rebuild broken": Building some modules require the same version of the base package it was build with. When trying to update base package in a project, it will rebuild all such modules. "smart rebuild": Testing package poppler update: New poppler has a new soname and it requires to rebuild all packages that are linked with poppler. However it is possible to install these packages (and use shared library from the parent project), testing of the new library requires to rebuild these package with the new library). "all dependencies": Testing new core package (bison, gcc). All packages, that have this package in BuildRequires on build system will be rebuilt. Virtual package may become non-virtual. If you need to patch one of the packages to be able to rebuild it in the new repository, you have to link it physically to the joint repository. In this moment, package becomes equal to the normal link package, disabled by default. Virtual/non-virtual joint project --------------------------------- Just now, one can include two different projects, that have a disjunctive packages. Virtual joint project would determine packages that will build differently (or break) in one or another parent repository and rebuild them as a separate repository. Virtual joint project could be a separate project that contains rebuilds of packages in the intersection of both project. Virtual joint project may become non-virtual. If you need to patch one of the packages to be able to rebuild it with both projects included, you have to add it physically to the joint repository. In this moment, the joint project feature would be equal to the normal repository with "Rebuild parent project packages" set. Example: Suppose you have a testing repository of new poppler (different soname) and a multimedia:photo with a new version of GIMP (requires poppler). You can easily include both multimedia:photo and poppler test repositories, but you cannot test new gimp with a new poppler. Creating of virtual joint project will automatically detect these packages and rebuild them. There could be again the tag "Rebuild parent projects packages" with the same values as above. Benefits: Virtual packages: Now they are often substituted by links. Several years later, nobody knows, why such link was created and the link may rot there forever. Virtual joint project: It will allow to test result of a dangerous package check-in without actually doing it. -- Best Regards / S pozdravem, Stanislav Brabec software developer --------------------------------------------------------------------- SUSE LINUX, s. r. o. e-mail: sbrabec(a)suse.cz Lihovarská 1060/12 tel: +420 284 028 966, +49 911 740538747 190 00 Praha 9 fax: +420 284 028 951 Czech Republic http://www.suse.cz/ -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

1 0

Re: [opensuse-buildservice] openSUSE:Factory & 11.1 repos - meta data primary.xml
by Adrian Schröter 08 Dec '08

08 Dec '08

On Montag 08 Dezember 2008 12:37:29 Martin Mohring wrote: > Michael Schroeder wrote: > > On Mon, Dec 08, 2008 at 11:17:30AM +0100, Martin Mohring wrote: > >> We use primary.xml for Download on Demand. Do we sit on a dead horse? > >> What else could we use instead for getting the meta data? > > > > You should also support the susetags format, it's pretty easy to parse. > > Which files in a SUSE repo file hierachy must we parse *instead* of > rpmmd primary.xml? It is suse/setup/descr/packages.gz . However, this format might get superceeded by an extended rpm-md with next release (or not, the plan exists for a longer time already, but it did not happen so far) ... -- Adrian Schroeter SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) email: adrian(a)suse.de -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

4 4

Re: [opensuse-buildservice] Using another home: project as repository
by Kevin James 08 Dec '08

08 Dec '08

Thanks, Joop I had tried that initially, but I was getting 400 errors from the server. I just tried it again and it worked ok. Just need to fix my spec file now ;) Cheers, KEv. On Mon, 2008-12-08 at 15:03 +0100, Joop Boonen wrote: > Hello Kevin, > > This might be helpful for you: > http://lists.opensuse.org/opensuse-buildservice/2008-11/msg00039.html > > Regards, > > Joop. > > > Hi all, > > > > If another user's home:xxx project has packages that are in my build (or > > install) requirements, can I add their project as a repository for my > > home: project? The reason I ask is that I just tried it, and I'm getting > > 400 errors when osc tries to write the project data back to the server. > > > > I would have used aggregate but all the documentation says this is a bad > > style. > > > > Cheers, > > KEv. > > > > > > -- > > Kevin James > > Applied Technology Senior Strategist > > Novell Global Enablement > > ------------------------ > > Novell, Inc. > > http://www.novell.com > > > > -- > > To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org > > For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org > > > > > > -- Kevin James Applied Technology Senior Strategist Novell Global Enablement ------------------------ Novell, Inc. http://www.novell.com -- 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] Using another home: project as repository
by Kevin James 08 Dec '08

08 Dec '08

Hi all, If another user's home:xxx project has packages that are in my build (or install) requirements, can I add their project as a repository for my home: project? The reason I ask is that I just tried it, and I'm getting 400 errors when osc tries to write the project data back to the server. I would have used aggregate but all the documentation says this is a bad style. Cheers, KEv. -- Kevin James Applied Technology Senior Strategist Novell Global Enablement ------------------------ Novell, Inc. http://www.novell.com -- 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] Coverity support?
by Lars Marowsky-Bree 08 Dec '08

08 Dec '08

Hi, at around LinuxTag there was some talk to include Coverity support into the build service, so that build packages could be scrutinized by a static source code analyzer. Has this gone anywhere, or is there any way to help it along? This would be really quite useful. Regards, Lars -- Teamlead Kernel, SuSE Labs, Research and Development SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) "Experience is the name everyone gives to their mistakes." -- Oscar Wilde -- 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] Unresolved OBS 1.0 dependencies for SLE10
by Carsten Hoeger 08 Dec '08

08 Dec '08

Hi, refering to http://lists.opensuse.org/opensuse-buildservice/2008-07/msg00064.html there are still unsatisfied deps, e.g. yum-metadata-parser is still missing. -- With best regards, Carsten Hoeger

2 6

[opensuse-buildservice] RPATH
by Matwey V. Kornilov 05 Dec '08

05 Dec '08

Hi, /usr/lib/rpm/brp-rpath says: ERROR: RPATH "/usr/src/packages/BUILD/... on ... is not allowed I think I understand why: just because the binary was linked with -rpath RPMBUILDDIR/... What is the correct solution of the problem? Should I patch the Makefile? Is there way to change rpath in the linked binary? -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

5 5