Overview
Request 991573 accepted
Automatic submission by obs-autosubmit
- Created by factory-maintainer
- In state accepted
Request History
factory-maintainer created request
Automatic submission by obs-autosubmit
factory-auto added opensuse-review-team as a reviewer
Please review sources
factory-auto accepted review
Check script succeeded
licensedigger accepted review
ok
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
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 This is a ring 0 package and needs to go to staging A/B/C
A/B/C/N/O
Indeed, that changed at some point. I wonder why not ABCDE.
Whenever debugedir changes version, we're in deep waters. rpm-build won't be installable when debugedit 5.1 exists, which will block 'everything forever'
@mls - did you mean
>= 5.0
?No, that's on purpose. debugedit must not be updated without rpm knowing it, as the find-debuginfo script is very rpm version dependent.
(That was the reason why it was "bundled" into the rpm source before.)
grmbl.. that's gonna be... painful.
i.e:
Based on the fact I tested upgrading from 0.3 to 5.0 of debugedit in home prj I seriously don't get this. There was major issues in the earlier previews but nothing since. RPM upstream agrees since INSTALL reads debugedit >= 0.3 not = 5.0