Re: [opensuse-factory] Fwd: [obs submit-request 70847] openSUSE:Factory/curl: declined by coolo
Am Samstag, 21. Mai 2011, 18:44:16 schrieb Cristian Rodríguez:
https://hermes.opensuse.org/messages/8534295
Are This rejection messages automated in any way ?
Yes, they are. They are the decline reasons for "factory-auto", the auto implies the automation.
It is the third or forth time the submission is rejected for totally bogus reasons.
Comment: please make sure to wait before these depencencies are in openSUSE:Factory: stunnel
It has never been required, it is an optional build dependency !!
Then use some other then the devel project of Factory for experiments. I won't take packages into Factory I can't guarantee they'll build in factory. If it takes project config tricks to build them, I want to check.
Greetings, Stephan
Stephan Kulow wrote:
Am Samstag, 21. Mai 2011, 18:44:16 schrieb Cristian Rodríguez:
It is the third or forth time the submission is rejected for totally bogus reasons.
Comment: please make sure to wait before these depencencies are in openSUSE:Factory: stunnel
It has never been required, it is an optional build dependency !!
Then use some other then the devel project of Factory for experiments. I won't take packages into Factory I can't guarantee they'll build in factory. If it takes project config tricks to build them, I want to check.
One could argue that devel projects must have an empty prjconf and no contain no packages that are not meant or not in Factory. The build service could even enforce that.
cu Ludwig
Am Montag, 23. Mai 2011, 10:31:06 schrieb Ludwig Nussel:
Stephan Kulow wrote:
Am Samstag, 21. Mai 2011, 18:44:16 schrieb Cristian Rodríguez:
It is the third or forth time the submission is rejected for totally bogus reasons.
Comment: please make sure to wait before these depencencies are in openSUSE:Factory: stunnel
It has never been required, it is an optional build dependency !!
Then use some other then the devel project of Factory for experiments. I won't take packages into Factory I can't guarantee they'll build in factory. If it takes project config tricks to build them, I want to check.
One could argue that devel projects must have an empty prjconf and no contain no packages that are not meant or not in Factory. The build service could even enforce that.
I'm fine with a prjconf if it's not affecting factory builds. E.g. in Base:System it's sometimes not possible to stage factory builds unless you change the projconfig
Greetings, Stephan
Stephan Kulow wrote:
Am Montag, 23. Mai 2011, 10:31:06 schrieb Ludwig Nussel:
Stephan Kulow wrote:
Am Samstag, 21. Mai 2011, 18:44:16 schrieb Cristian Rodríguez:
It is the third or forth time the submission is rejected for totally bogus reasons.
Comment: please make sure to wait before these depencencies are in openSUSE:Factory: stunnel
It has never been required, it is an optional build dependency !!
Then use some other then the devel project of Factory for experiments. I won't take packages into Factory I can't guarantee they'll build in factory. If it takes project config tricks to build them, I want to check.
One could argue that devel projects must have an empty prjconf and no contain no packages that are not meant or not in Factory. The build service could even enforce that.
I'm fine with a prjconf if it's not affecting factory builds. E.g. in Base:System it's sometimes not possible to stage factory builds unless you change the projconfig
Well, rpm should probably have it's own devel project anyways :-) At the time of creating the submit request to Factory there should be no prjconf modification needed anymore though. In some cases it may even be useful if the submit request could include actually needed prjconf changes too (e.g. for gcc update).
cu Ludwig
On Mon, 2011-05-23 at 10:31 +0200, Ludwig Nussel wrote:
One could argue that devel projects must have an empty prjconf and no contain no packages that are not meant or not in Factory. The build service could even enforce that.
Hardly: how else would I ever create a new package for inclusion into Factory, if the devel project is not allowed to have packages that are not in Factory :) (you can't automatically decide if a package is MEANT for Factory... so I assume the check would be 'is not in Factory')
As for prjconf: this should ONLY check for the build against Factory please! (GNOME:Apps for example requires a prjconf to introduce special tweaks for some combination of repos. But none should exist IIRC for a 'clean' factory build)
Dominique
El 22/05/11 19:01, Stephan Kulow escribió:
Then use some other then the devel project of Factory for experiments. I won't take packages into Factory I can't guarantee they'll build in factory. If it takes project config tricks to build them, I want to check.
There is no experiment, the spec file optional buildrequires have been there since at least 3 releases, from the time human beings with the criteria that a bot lacks, actually checked if there was something wrong.
-
Cristian Rodríguez -
Dimstar / Dominique Leuenberger -
Ludwig Nussel -
Stephan Kulow