Request History
gmbr3 created request
updated SR
gmbr3 added gmbr3 as a reviewer
Prevent early acceptance to Factory
factory-auto added opensuse-review-team as a reviewer
Please review sources
factory-auto accepted review
Check script succeeded
licensedigger accepted review
ok
favogt_factory added openSUSE:Factory:Staging:adi:12 as a reviewer
Being evaluated by staging project "openSUSE:Factory:Staging:adi:12"
favogt_factory accepted review
Picked "openSUSE:Factory:Staging:adi:12"
RBrownFactory added factory-staging as a reviewer
Being evaluated by group "factory-staging"
RBrownFactory accepted review
Unstaged from project "openSUSE:Factory:Staging:adi:12"
RBrownFactory set openSUSE:Factory:Staging:N as a staging project
Being evaluated by staging project "openSUSE:Factory:Staging:N"
RBrownFactory accepted review
Picked "openSUSE:Factory:Staging:N"
dimstar accepted review
gmbr3 accepted review
let's go
dimstar added dimstar as a reviewer
I'll be mean and add a review on me - this is not a staging I want to merge on Saturday/Sunday, sorry for the extra delay
dimstar accepted review
ready, set, ....
dimstar_suse accepted review
Staging Project openSUSE:Factory:Staging:N got accepted.
dimstar_suse approved review
Staging Project openSUSE:Factory:Staging:N got accepted.
dimstar_suse accepted request
Staging Project openSUSE:Factory:Staging:N got accepted.
@RBrownFactory @favogt_factory @dimstar
get python-packaging python-pyparsing and python-flit-core from :L ?
Ok
sr#991949
Somehow my testing went wrong. I had concluded that the BuildIgnores looks at package names, not capabilities. Apparently that is not the case, it must be the same string as the requirement.
It should work for package names just fine...
Then maybe it is the macro expansion. As far as I remember I HAD tested with
osc buildinfo -M primaryand my conclusion was to use the macro so that it resulted in#!BuildIgnores: python310-packaging, but now, with a checkout of Staging:N/python-packaging it only breaks the unresolvable with#!BuildIgnores: python3-packaging.Only if the package has been built before... Does not work in initial bootstrap, as nothing provides python3- yet, so no package to ignore
Makes sense. So the new
BuildIgnores: python3-packagingis correct, even when it is provided by a then builtpython310-packaging?So all that blocks N now is that review on this package. Respect!
@gmbr3, your turn :)
Thanks @coolo 😀
No worries @dimstar :)