August 2009 - openSUSE Build Service - openSUSE Mailing Lists

[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