August 2009 - openSUSE Build Service - openSUSE Mailing Lists

[opensuse-buildservice] Pruning builds to conserve build power?
by Lars Marowsky-Bree 20 Aug '09

20 Aug '09

Hi, I'm not sure whether this has been given some thought yet. But it seems that there's an awful lot of build power "wasted" to rebuild packages that don't have users (anymore), or a lot of _links around which are no longer used etc. Is there possibly some way to prune them from blocking the rebuild power of the system? Low-key solution: require that each "build & publish" bit is refreshed manually every N weeks? Regards, Lars -- Architect Storage/HA, OPS Engineering, Novell, Inc. 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

4 5

[opensuse-buildservice] Packagers Section in Weekly News
by Sascha 'saigkill' Manns 20 Aug '09

20 Aug '09

Hello Mates, today i got an interesting Idea in our Weekly News Survey. An User asks for an own Packaging Section. He mean that that is an place for Packagers to announce fixed Packages (with an Bugzilla Reference). So the Weekly News Format is maybe: * Bugzilla-Number and Summary * Package and Version * Date and Packager * Free Text: What is changed. (Short Issue). Exists interesting about that Idea? Would Packager like to announce through the Weekly News? -- Sincerely yours Sascha Manns openSUSE Ambassador openSUSE Marketing Team openSUSE Build Service Web: http://saschamanns.gulli.to Project-Blog: http://lizards.opensuse.org/author/saigkill Private-Blog: http://saschasbacktrace.blogspot.com -- 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] server:php repository warning
by Cristian Rodríguez 20 Aug '09

20 Aug '09

Hi: Recently we have switched server:php repositories to PHP 5.3.x , there are a number of issues that you should be aware in case you are using them - In some builds, mysql extensions are broken, this has been fixed in the meanwhile. - Initial testing results are far from promising... if you find any problem please fill a bug report at bugzilla.novell.com - There is an inconsistency between server:php and server:php:extensions so packages may get uninstalled, or broken on upgrade, this is temporary. Thanks for flying with openSUSE ;-) . -- 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] How to change my email address?
by Paul Elliott 19 Aug '09

19 Aug '09

Home of pelliott11 https://build.opensuse.org/home shows my name and email address. My email address has changed. How do I change it? "Edit User Data" and "Edit Tag Data" show no applicable fields. Than You. -- Paul Elliott 1(512)837-1096 pelliott(a)BlackPatchPanel.com PMB 181, 11900 Metric Blvd Suite J http://www.free.blackpatchpanel.com/pme/ Austin TX 78758-3117

2 5

RE: [opensuse-buildservice] -fPIC failing on RHEL5/CentOS5 builds?
by Scott Cantor 19 Aug '09

19 Aug '09

Scott Cantor wrote on 2009-08-18: > So, ummm, that ain't from me. I did try passing the mcpu option in a simple > command manually when I scanned my working config.log, but I didn't get that > deprecation warning at the time, so I'm looking into it, but seems to me > this is a problem. (For anybody else's benefit...) I found the docs on controlling the build and from what I can tell the osc source code and my local copy of the settings includes OptFlags that match the right compiler settings but the default values used by the build service in the VMs are out of date. I'm attempting to override them with the new defaults and expect that will fix it. I guess I'd ask that whoever maintains the remote builds update those defaults if possible. Non-relocatable code causes problems with SELinux among other things. -- Scott -- 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] -fPIC failing on RHEL5/CentOS5 builds?
by Scott Cantor 19 Aug '09

19 Aug '09

I've just started attempting to use the build service for my project and got a report that one of the binaries contained a bunch of text relocations, indicating -fPIC wasn't used during the build. After some cross checking, I found that the usual checks in configure were being done, but that on two of the build platforms (RH5/CentOS5), the gcc/g++ checks were failing and it was omitting the flag. Both architectures were affected. I tested locally with CentOS 5 and confirmed that I get different (correct) results from my rpmbuild. I know there's no direct access to config.log, so it's a bit difficult to determine why this might be, but wondered if anybody had a clue or has seen this behavior in their projects? For reference the checks I'm referring to are: checking for gcc option to produce PIC... -fPIC checking if gcc PIC flag -fPIC works... no checking for g++ option to produce PIC... -fPIC checking if g++ PIC flag -fPIC works... no I saw nothing unexpected in my local config.log where the check passes, it's a typical gcc/g++ command. -- Scott -- 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] Re: [Mono-list] MonoOSC Help wanted :-)
by Petit Eric 18 Aug '09

18 Aug '09

2009/8/18 Oisín Grehan <oising(a)gmail.com>: > Is that OSC as in Open Sound Control? sorry, i don't understand your question, you mean : MonoOSC is Open source ? > > On Tue, Aug 18, 2009 at 6:47 AM, Petit Eric <surfzoid(a)gmail.com> wrote: >> >> Hi >> An user ask to an "quickstart guide", is there an MonoOSC user who >> want to write it ? >> >> https://sourceforge.net/tracker/index.php?func=detail&aid=2839338&group_id=… >> >> Unlucky, i really haven't got time and don't practice doc. >> >> -- >> Cordially. >> >> Small Eric Quotations of the days: >> >> --------------------------------------------------------------------------- >> I have no special talents. I am only passionately curious >> _______________________________________________ >> Mono-list maillist - Mono-list(a)lists.ximian.com >> http://lists.ximian.com/mailman/listinfo/mono-list > > > > -- > > --- > 404 signature missing > -- Cordially. Small Eric Quotations of the days: --------------------------------------------------------------------------- I have no special talents. I am only passionately curious -- 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] package publishing issues
by Cristian Rodríguez 18 Aug '09

18 Aug '09

Hi: The server:php and server:php:extensions repositories are taking a significant amount of time that varies between 3 days to weeks to get already built packages published to the download server, I was wondering how exactly the obs chooses what to publish and when, and if that is configurable .. let's say: I have target A in server:php and target B in server:php:extensions, B uses A for build and hence depends on it, If A rebuilds I want to have A and B published at the same time to avoid inconsistencies, is that possible ? -- 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] MonoOSC Help wanted :-)
by Petit Eric 18 Aug '09

18 Aug '09

Hi An user ask to an "quickstart guide", is there an MonoOSC user who want to write it ? https://sourceforge.net/tracker/index.php?func=detail&aid=2839338&group_id=… Unlucky, i really haven't got time and don't practice doc. -- Cordially. Small Eric Quotations of the days: --------------------------------------------------------------------------- I have no special talents. I am only passionately curious -- 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] Unowned directories question
by doiggl＠velocitynet.com.au 18 Aug '09

18 Aug '09

Hello To get past this Warning message I have gotten a workaround for it. (see workaround below) Warning message: bugzilla-3.4.1-14.1.noarch.rpm: directories not owned by a package: - /etc/httpd - /etc/httpd/conf.d - /usr/share/bugzilla/extensions - /usr/share/bugzilla/lib bugzilla-doc-3.4.1-14.1.noarch.rpm: directories not owned by a package: - /usr/share/bugzilla/docs bugzilla-doc-build-3.4.1-14.1.noarch.rpm: directories not owned by a package: - /usr/share/bugzilla/docs System halted. #WORKAROUND #---------- %if 0%{?suse_version} # With unowned dirs /etc/httpd/, the build will fail so own them ourselves %dir %{_sysconfdir}/etc/httpd %dir %{_sysconfdir}/etc/httpd/conf.d %dir %{_sysconfdir}/etc/httpd/conf.d/bugzilla.conf %endif Questions: Does the workaround look ok ?, and at what line should I place the code in the .specfile ? Specfile -> https://build.opensuse.org/package/view_file?file=bugzilla.spec&package=Bug… Thanks for the advice Glenn -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

4 4

[opensuse-buildservice] Is this a bug in osc?
by Dave Plater 17 Aug '09

17 Aug '09

I removed a package from my build service project and home directory ( a .desktop file) and then found that it was necessary so I put it back in my local project directory. Then I performed an osc ci and it checked in three files that I had changed but failed to include the above mentioned package is this normal and I should manually upload new files or is this a bug? Regards Dave P -- 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] BUG: self-dependency in build problem on OBS
by David Greaves 17 Aug '09

17 Aug '09

If I want to build a deb package that depends on itself for building then it fails. I assumed it was being removed by build or osc but traced it to the API response. eg: https://api.opensuse.org/build/home:lbt:arm:cross/xUbuntu_9.04/armv5el/m4/_… https://api.opensuse.org/build/home:lbt:arm:cross/xUbuntu_9.04/armv5el/dpkg… Both m4 and dpkg-dev are build-essential The first (m4) package does not have m4 in the <bdep> list but has dpkg-dev The second (dpkg) package does not have dpkg-dev in the <bdep> list but has m4 (dpkg provides dpkg-dev of course) This bites when building any package in build-essential or any other package that self build-depends; they all need modifying to build on OBS. David -- "Don't worry, you'll be fine; I saw it work in a cartoon once..." -- 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] bs and ARM
by Peter Czanik 17 Aug '09

17 Aug '09

Hello, Finally I got a little time, so I'd like to try to compile a few packages for Debian ARM. Last time I worked with the BS, I used PPC and openSUSE 11.0. Now looking for info, how to get started BS for ARM. So, I got some questions: - which version to use if I want to compile for ARM? - http://en.opensuse.org/Build_Service/Build_Service_Installation_Tutorial only has instructions up to openSUSE 11.0. Does the same apply for 11.1? Is it the doc I should use for cross builds: http://en.opensuse.org/Build_Service/Concepts/CrossDevelopment ? - Can I compile for Debian Lenny? ( http://en.opensuse.org/Build_Service/Concepts/CrossDevelopment only mentions Etch ) Some packages are not included in Debian Lenny for ARM, which are available in Ubuntu and I'd try to recompile them for Debian... - is it already possible to boot openSUSE/ARM? Would be nice to see it running at least in Qemu... Bye, CzP -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

3 7

[opensuse-buildservice] RPM signing problem
by Cristian Morales Vega 16 Aug '09

16 Aug '09

For some days I have been receiving emails about failed builds. Now I'm looking into them and seems to be a problem signing packages in Factory: sign libglpng-devel-1.45-1.41.i586.rpm failed: 256 Any idea? -- 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] [osc] patch to support overlay filesystem - RFC
by Jan-Simon Möller 14 Aug '09

14 Aug '09

Hi ! During work on openSUSE@ARM I frequently wanted to change single files or add single files to the buildroot without recompiling a dependency package or adding the files to a dummy rpm. Thus here are 2 patches for osc and build which will do this: Take all files in the specified "overlay"-folder and copy them to the buildroot before actually starting the build. This can help especially in local development with osc build if you e.g. want to delpoy a custom debugger, a custom qemu-arm or even a patched file. Best, Jan-Simon Signed-off-by: Jan-Simon Möller <jansimon.moeller(a)opensuse.org> Index: build.py =================================================================== --- build.py (Revision 7845) +++ build.py (Arbeitskopie) @@ -511,6 +511,23 @@ vm_options, build_descr, buildargs) + # special handling for overlay + if opts.overlay: + myoverlay=os.path.abspath(opts.overlay) + if os.path.isdir(myoverlay): + cmd = '%s --root=%s --rpmlist=%s --dist=%s --overlay=%s --arch=%s %s %s %s' \ + % (config['build-cmd'], + config['build-root'], + rpmlist_file.name, + bc_file.name, + myoverlay, + bi.buildarch, + vm_options, + build_descr, + buildargs) + else: + print "ERROR: OVERLAY ("+myoverlay+") is no directory." + sys.exit(1) if config['su-wrapper'].startswith('su '): tmpl = '%s \'%s\'' Index: commandline.py =================================================================== --- commandline.py (Revision 7845) +++ commandline.py (Arbeitskopie) @@ -2238,6 +2238,8 @@ @cmdln.option('--clean', action='store_true', help='Delete old build root before initializing it') + @cmdln.option('--overlay', metavar='OVERLAY', + help='Copy overlay filesystem to buildroot after installing all RPMs. This must be a valid directory (e.g. /tmp/overlay-root). The files are copied as-is.') @cmdln.option('--no-changelog', action='store_true', help='don\'t update the package changelog from a changes file') @cmdln.option('--noinit', '--no-init', action='store_true', Index: build =================================================================== --- build (Revision 7845) +++ build (Arbeitskopie) @@ -63,6 +63,7 @@ INCARNATION= DISTURL= CHANGETARGET= +OVERLAY= export PATH=$BUILD_DIR:/sbin:/usr/sbin:$PATH @@ -157,6 +158,9 @@ --icecream N use N parallel build jobs with icecream + --overlay OVERLAY + Copy overlay filesystem to buildroot after installing + all RPMs. This must be a valid directory. --debug enable creation of a debuginfo package @@ -664,6 +668,10 @@ *-changelog) CHANGELOG=true ;; + --overlay) + OVERLAY=$ARG + shift + ;; -*) echo Unknown Option "$PARAM". Exit. cleanup_and_exit 1 @@ -1332,6 +1340,17 @@ BUILD_SUCCEEDED=false + if test -n "$OVERLAY" ; then + if test -d "$OVERLAY"; then + pushd $OVERLAY + echo "Copying overlay to BUILD_ROOT" + tar -cpf - . | (cd $BUILD_ROOT ; tar -xf -) + popd + else + echo "OVERLAY ($OVERLAY) is no directory - skipping" + fi + fi + if test "$BUILDTYPE" = spec ; then test -z "$BUILD_RPM_BUILD_STAGE" && BUILD_RPM_BUILD_STAGE=-ba -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

4 13

[opensuse-buildservice] Can't commit read-only file
by Luke Imhoff 14 Aug '09

14 Aug '09

I was trying to importsrcpkg the automake.src.rpm from SLES 10 to rebuild it for SLES 11 when I came upon a bug. The tarball is unpacked as readonly: osc importsrcpkg automake-1.9.6-13.2.src.rpm A automake No files were committed to the server. Please commit them manually. Package 'automake' only imported locally % cd automake/ % ls -la automake-1.9.6.tar.bz2 -r--r--r-- 1 luke criemp 765505 2009-08-14 09:24 automake-1.9.6.tar.bz2 If I then try to commit the files: % osc addremove % osc ci -m "SLES 10 automake" ... Transmitting file data ..[Errno 13] Permission denied: '/notbackedup/users/luke/obs/devel:tools:building/automake/.osc/automake-1.9.6.tar.bz2' The file cache under .osc has automake-1.9.6.tar.bz2 as read-only also, so it can't be written when the mod is submitted to the server. -- 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] Does osc modify gcc build flags?
by Dave Plater 13 Aug '09

13 Aug '09

Hi, I have a package that when building with osc gives a warning about uninitialized variables being used but rpmbuild doesn't. Is there a way to receive these warnings using make? Regards Dave P -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

6 14

[opensuse-buildservice] Re: [opensuse-programming] What's the best way to cure uninitialized variables?
by Dave Plater 13 Aug '09

13 Aug '09

On 08/08/2009 04:11 PM, Philipp Thomas wrote: > On Sat, 08 Aug 2009 15:01:42 +0200, you wrote: > > >> The warnings come from osc, I don't get these warnings when I build the >> same package using kdevelop3. >> > The warnings definitely come from the compiler when passed the right > Options, which is mainly -Wall! But as they are only warnings the > compiler will succeed in compiling. OSC scans the comipler output and > turns some warnings into fatal errors because the past has shown us > that these lead to broken programs. > > If you carefully log the compiler output[1] and scan it afterwards > you'll see all those warnings the compiler produced. > > Philipp > > 1) My favourite for logging when not using 'osc build' is is defining > a simple shell function mk() { make "$@" 2>&1 | tee mlog; }. Now > you simply call mk (possibly whith additional options for make) and > afterwards have a complete log. > > Well I must admit I feel like an idiot, I was setting C flags in cmake and not the CXX flags (at least I'll never make the same mistake). I can now get the exact same messages to display in kdevelop3 as I receive from osc, without the summary of course. Thanks very much for your patience with me. Regards Dave P -- 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] Atomic package set updates
by Luke Imhoff 13 Aug '09

13 Aug '09

Here's the use case we have for our developers: 1) The kernel gets a change by a checkin of kernel-source by Alice. This triggers a build of kernel-FLAVORs and kernel-syms as they are all linked to the kernel-source package (and any indirect dependents). 2) kernel-source finishes building 3) kernel-source is available for build use now 4) kernel-syms hasn't finished building as it's wating on kernel-FLAVORs (which take longer than kernel-source) 5) Bob tries to build foo-kmp, which BuildRequires kernel-source and kernel-syms, but osc buildinfo says expansion error because kernel-syms cannot find the old version of kernel-source. kernel-syms has Requires: kernel-source = %{version}-%{release} to make sure they tightly match. Now we could get around this by making kernel-syms not dependent on a strict version-release match with kernel-source, but then the kernel-syms would be incorrect if the developer tried to build against it. So, is there someway to not release the changes in kernel-source that affect the buildinfo to developers doing local builds with 'osc build' until after all builds triggered by the checkin of kernel-source finishes? -- 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] kiwi >= 3.6 in obs?
by Carsten Hoeger 12 Aug '09

12 Aug '09

Hi, is it planned to have kiwi >=3.6 in obs to support images using custom branding using <preferences> [...] <boot-theme>FOO</boot-theme> [...] </preferences> -- With best regards, Carsten Hoeger

2 2

[opensuse-buildservice] osc rq list -M -s accepted doesn't show all requests
by Jan-Simon Möller 12 Aug '09

12 Aug '09

Hi ! For documentation I want to list all my accepted/declined/revoked/... requests, but osc rq list -M -s accepted doesn't show all accepted requests . Most of the 16xxx range is missing (also not in the other states). And I'm sure, I submitted stuff ;) . So the question is: are these requests lost or can I query for them somehow using my loginname ? Best, Jan-Simon -- 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] Slightly Off-Topic: How to create bootsplash logo.mng?
by Carsten Hoeger 12 Aug '09

12 Aug '09

Hi, I know, it's off-topic, but I was unable to find any _clear_ instruction on how to create bootsplash logo.mng files. Some e.g. state, that a special version of convert must be used, or sililar... Does anybody have a pointer on how to exactly do that on openSUSE (11.1)? -- With best regards, Carsten Hoeger

1 0

[opensuse-buildservice] GSoC - summary of this week's meeting
by Marcus Hüwe 12 Aug '09

12 Aug '09

Hi, here's a summary of this week's meeting: Since the rails oauth-plugin[1] got support for oauth 1.0a I started to migrate the frontend so that it also supports 1.0a. This was a nice exercise to learn how certain things are done with rails. Additionally I did some code cleanups, bugfixing etc. The goal for this week is more testing, bugfixing and writing a user documentation. Marcus [1] http://code.google.com/p/oauth-plugin -- 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] Notifications (was: Re: [opensuse-packaging] New packages for factory)
by Peter Poeml 12 Aug '09

12 Aug '09

On Mon, Aug 10, 2009 at 02:32:04 +0200, Stephan Kulow wrote: > On Monday 10 August 2009 16:45:33 Dominique Leuenberger wrote: > > I think the minimum 'feedback' we need finally to get working is hermes > > acting properly on SR creation / accepting / revoking / declining. > > > > Not having any feedback (good or bad) is unfriendly practice. Of course it > > should not be that besides a proper osc rq accept -m "Thanks for this > > wonderful package. It has just been accepted to Factory and will appear in > > the next sync" you have to do any additional steps. > > > > Unfortunately, the above does not create a mail to the person that > > initiated the osc sr create > > request. > > Agreed. Some get mails, some don't. This is something that needs to be fixed > in the build service asap. Do you get no mails at all or just some are > missing? Because I do not miss any mails (the opposite is true :) I get commit mails for some projects (Subversion), and not for some others (devel:languages:python). The "_mypackages" filter in hermes doesn't work correctly, I guess. But the largest blocker for me is that I don't get any commit diffs at all. (Not implemented.) How can I track the work of others, and review it, and how can they follow on what I do, without? So far, I have to rely on good commit messages, or dig out the changes in an elaborate manual process. Peter -- "WARNING: This bug is visible to non-employees. Please be respectful!" SUSE LINUX Products GmbH Research & Development

10 20

[opensuse-buildservice] how to find out why a package is excluded from build?
by Carsten Hoeger 11 Aug '09

11 Aug '09

Hi, I copied my branding package from the Education project: https://build.opensuse.org/package/show?package=gfxboot-branding-ox&project… It builds locally now using osc build but issues some warnings, though: RPMLINT report: =============== gfxboot-branding-ox.noarch: W: no-changelogname-tag gfxboot-branding-ox.src: W: no-changelogname-tag There is no %changelog tag in your spec file. To insert it, just insert a '%changelog' in your spec file and rebuild it. gfxboot-branding-ox.noarch: W: suse-branding-missing-conflicts otherproviders(gfxboot-branding) Any branding flavor package that provides the generic branding must also conflict with all other branding packages via a special otherproviders() gfxboot-branding-ox.noarch: W: suse-branding-supplement-missing packageand(gfxboot:branding-ox) branding packages should provide a supplemnent in the form Supplements: packageand(basepackage:branding-<flavour>) gfxboot-branding-ox.noarch: W: suse-branding-wrong-branding-supplement packageand(branding-ox:gfxboot) 2 packages and 0 specfiles checked; 0 errors, 5 warnings. mobile finished "build gfxboot-branding-ox.spec" at Mon Aug 10 18:02:25 CEST 2009. I've no idea why it insists on missing the %changelog tag, because it is really there. The other warnings also appear in the buildlog of the gfxboot package from Education, so I assume that I can just ignore them. OBS just silently excludes that package. Any idea? -- With best regards, Carsten Hoeger

3 6