Overview
Request 720684 accepted
Newer pending source available from package origin. See request#720638. (host boomba-work)
- Created by origin-manager
- In state accepted
Request History
origin-manager created request
Newer pending source available from package origin. See request#720638. (host boomba-work)
licensedigger accepted review
ok
origin-manager added origin-reviewers as a reviewer
Changing to a higher priority origin, but from another family.
origin: SUSE:SLE-15-SP1:Update
origin_old: openSUSE:Leap:15.1:Update
factory-auto accepted review
Check script succeeded
origin-manager accepted review
origin: SUSE:SLE-15-SP1:Update
origin_old: openSUSE:Leap:15.1:Update
staging-bot set openSUSE:Leap:15.2:Staging:C as a staging project
Being evaluated by staging project "openSUSE:Leap:15.2:Staging:C"
staging-bot accepted review
Picked openSUSE:Leap:15.2:Staging:C
jberry accepted review
resolved by openSUSE/openSUSE-release-tools#2143
lnussel_factory accepted review
ok
lnussel_factory accepted review
ready to accept
lnussel_factory approved review
ready to accept
lnussel_factory accepted request
Accept to openSUSE:Leap:15.2
missing newer yast2 https://build.opensuse.org/project/show/openSUSE:Maintenance:10689, I wonder why do origin-manager does not submit it, @jberry what is origin-manager's log says?
It's because origin-manager does not consider
yast2to be coming from :Update likeyast2-packager. http://paste.opensuse.org/view/raw/50644160This is due to the fact that when no maintenance update is available for a package the sources are inherited and thus match the base product. Once an update is provided the revision history only includes the update and not the original value which was inherited. I worked around this elsewhere by including the inherited revisions in the history, but was not 100% sure if I should always do so. If I flip the flag to true to include them we see the following.
Which makes sense since SLE :Update mirrors the same process and thus also has the revision in the base product, but not the maintenance update revisions. I'll submit a PR to change this to always be enabled and see were we get from there.
See PR 2143.