[opensuse-buildservice] how to find out why a package is excluded from build?
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
On Monday 10 August 2009 18:12:25 Carsten Hoeger wrote:
Hi,
I copied my branding package from the Education project:
https://build.opensuse.org/package/show?package=gfxboot-branding-ox&project =server%3AOX%3Aunsupported
It builds locally now using osc build but issues some warnings, though: [...] the warnings from rpmlint (or similar the errors) can lead to a failed package but not to the package being ignored.
OBS just silently excludes that package. Any idea? looking at the above URL, I see that build is disabled for almost all distributions/architectures except for openSUSE 11.1 on i586 (where the package does build) and except for xUbuntu, where the package is probably ignored for only having a specfile and not a dsc-file (AFAIK the latter distrubutions are deb-based and not rpm based)
In other words: could you try enabling the build flags for the distributions disabled in the package flags (by clicking on the gearwheel icon) ? -- with kind regards (mit freundlichem Grinsen), Ruediger Oertel (ro@novell.com,ro@suse.de,bugfinder@t-online.de) ---------------------------------------------------------------------- Linux MacBookRudi 2.6.31-rc5-git3-2-desktop #1 SMP PREEMPT 2009-08-06 23:25:57 +0200 x86_64 Key fingerprint = 17DC 6553 86A7 384B 53C5 CA5C 3CE4 F2E7 23F2 B417 SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Am Dienstag, 11. August 2009 01:42:24 schrieb Ruediger Oertel:
On Monday 10 August 2009 18:12:25 Carsten Hoeger wrote:
Hi,
I copied my branding package from the Education project:
https://build.opensuse.org/package/show?package=gfxboot-branding-ox&proje ct =server%3AOX%3Aunsupported
It builds locally now using osc build but issues some warnings, though:
[...] the warnings from rpmlint (or similar the errors) can lead to a failed package but not to the package being ignored.
OBS just silently excludes that package. Any idea?
looking at the above URL, I see that build is disabled for almost all distributions/architectures except for openSUSE 11.1 on i586 (where the package does build) and except for xUbuntu, where the package is probably ignored for only having a specfile and not a dsc-file (AFAIK the latter distrubutions are deb-based and not rpm based)
In other words: could you try enabling the build flags for the distributions disabled in the package flags (by clicking on the gearwheel icon) ?
We discussed this on IRC yesterday, it was caused by a global setting in choegers project that all repos are type "kiwi". So a spec file was not appropriate and the scheduler excluded it. bye adrian -- Adrian Schroeter SUSE Linux Products GmbH email: adrian@suse.de -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Tuesday 11 August 2009 09:31:50 Adrian Schröter wrote:
We discussed this on IRC yesterday, it was caused by a global setting in choegers project that all repos are type "kiwi". So a spec file was not appropriate and the scheduler excluded it. thinking about it: wouldn't it be more obvious to use a different state than "excluded" if there is no matching file (.spec,.dsc, .kiwi) for a configured repo type ?
-- with kind regards (mit freundlichem Grinsen), Ruediger Oertel (ro@novell.com,ro@suse.de,bugfinder@t-online.de) ---------------------------------------------------------------------- Linux MacBookRudi 2.6.31-rc5-git3-2-desktop #1 SMP PREEMPT 2009-08-06 23:25:57 +0200 x86_64 Key fingerprint = 17DC 6553 86A7 384B 53C5 CA5C 3CE4 F2E7 23F2 B417 SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Tue, Aug 11, Adrian Schröter wrote:
I copied my branding package from the Education project:
https://build.opensuse.org/package/show?package=gfxboot-branding-ox&proje ct =server%3AOX%3Aunsupported
It builds locally now using osc build but issues some warnings, though:
[...] the warnings from rpmlint (or similar the errors) can lead to a failed package but not to the package being ignored.
OBS just silently excludes that package. Any idea?
looking at the above URL, I see that build is disabled for almost all distributions/architectures except for openSUSE 11.1 on i586 (where the package does build) and except for xUbuntu, where the package is probably ignored for only having a specfile and not a dsc-file (AFAIK the latter distrubutions are deb-based and not rpm based)
In other words: could you try enabling the build flags for the distributions disabled in the package flags (by clicking on the gearwheel icon) ?
We discussed this on IRC yesterday, it was caused by a global setting in choegers project that all repos are type "kiwi". So a spec file was not appropriate and the scheduler excluded it.
Yap. Adrian told me to add an if condition around the imaging stuff %if "%_repository" == "images" Type: kiwi Repotype: none Patterntype: none %endif Now it is working again, thanks for the help. It would, however, make sense to somehow find out why a build is excluded, e.g. an error message like "found no valid kiwi image description" or something similar. -- With best regards, Carsten Hoeger
On Tue, Aug 11, Carsten Hoeger wrote:
looking at the above URL, I see that build is disabled for almost all distributions/architectures except for openSUSE 11.1 on i586 (where the package does build) and except for xUbuntu, where the package is probably ignored for only having a specfile and not a dsc-file (AFAIK the latter distrubutions are deb-based and not rpm based)
In other words: could you try enabling the build flags for the distributions disabled in the package flags (by clicking on the gearwheel icon) ?
We discussed this on IRC yesterday, it was caused by a global setting in choegers project that all repos are type "kiwi". So a spec file was not appropriate and the scheduler excluded it.
Yap. Adrian told me to add an if condition around the imaging stuff
%if "%_repository" == "images" Type: kiwi Repotype: none Patterntype: none %endif
Now it is working again, thanks for the help.
It would, however, make sense to somehow find out why a build is excluded, e.g. an error message like "found no valid kiwi image description" or something similar.
Hm, just noticed, that now the image builds are excluded... So does that mean that I need to put the packages in a different project? -- With best regards, Carsten Hoeger
Am Dienstag, 11. August 2009 11:04:08 schrieb Carsten Hoeger:
On Tue, Aug 11, Carsten Hoeger wrote:
looking at the above URL, I see that build is disabled for almost all distributions/architectures except for openSUSE 11.1 on i586 (where the package does build) and except for xUbuntu, where the package is probably ignored for only having a specfile and not a dsc-file (AFAIK the latter distrubutions are deb-based and not rpm based)
In other words: could you try enabling the build flags for the distributions disabled in the package flags (by clicking on the gearwheel icon) ?
We discussed this on IRC yesterday, it was caused by a global setting in choegers project that all repos are type "kiwi". So a spec file was not appropriate and the scheduler excluded it.
Yap. Adrian told me to add an if condition around the imaging stuff
%if "%_repository" == "images" Type: kiwi Repotype: none Patterntype: none %endif
Now it is working again, thanks for the help.
It would, however, make sense to somehow find out why a build is excluded, e.g. an error message like "found no valid kiwi image description" or something similar.
Hm, just noticed, that now the image builds are excluded... So does that mean that I need to put the packages in a different project?
No, you need to enable the build of the .kiwi packages for the "images" instead of inside the "openSUSE_11.1" repo. bye adrian -- Adrian Schroeter SUSE Linux Products GmbH email: adrian@suse.de -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
participants (3)
-
Adrian Schröter -
Carsten Hoeger -
Ruediger Oertel