Project

General

Profile

action #16804

submit new Factory packages to Leap

Added by lnussel over 3 years ago. Updated about 3 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Release Engineering
Target version:
Start date:
2017-02-07
Due date:
2017-05-31
% Done:

100%

Estimated time:
Duration: 82

Description

for all packages that were added to Factory after the last leap release, set up https://build.opensuse.org/project/show/openSUSE:42:Factory-Candidates-Check to check build success and activate the https://github.com/openSUSE/osc-plugin-factory/blob/master/fcc_submitter.py


Related issues

Copied from openSUSE Leap 42.2 Release - action #13062: submit new Factory packages to LeapClosed2016-08-082016-08-25

Copied to openSUSE Leap 15.0 - action #24840: submit new Factory packages to LeapClosed2018-01-082018-03-15

History

#1 Updated by lnussel over 3 years ago

  • Copied from action #13062: submit new Factory packages to Leap added

#2 Updated by lnussel over 3 years ago

  • Category deleted (Release Engineering)
  • Assignee changed from lnussel to mlin7442

Max, could you take care of this again?
Please make sure it only submits packages added after 42.2 was done. Maybe use _frozenlink to restrict the packages tried in the first place?

#3 Updated by mlin7442 over 3 years ago

  • Checklist set to [ ] set up ptoject, [ ] adjust fcc_submitter, [ ] announce to Factory mailing list

#4 Updated by mlin7442 over 3 years ago

  • Checklist set to [x] set up ptoject

#5 Updated by mlin7442 over 3 years ago

lnussel wrote:

Max, could you take care of this again?
Please make sure it only submits packages added after 42.2 was done. Maybe use _frozenlink to restrict the packages tried in the first place?

if the source were copied to 42.3 properly from 42.2, then it is :)

#6 Updated by lnussel over 3 years ago

mlin7442 wrote:

lnussel wrote:

Max, could you take care of this again?
Please make sure it only submits packages added after 42.2 was done. Maybe use _frozenlink to restrict the packages tried in the first place?

if the source were copied to 42.3 properly from 42.2, then it is :)

what about the ones we intentionally didn't take?

#7 Updated by mlin7442 over 3 years ago

lnussel wrote:

mlin7442 wrote:

lnussel wrote:

Max, could you take care of this again?
Please make sure it only submits packages added after 42.2 was done. Maybe use _frozenlink to restrict the packages tried in the first place?

if the source were copied to 42.3 properly from 42.2, then it is :)

what about the ones we intentionally didn't take?

yeah, I can adds an double check with 42.2 too. but I also curious which ones we didn't take?

#8 Updated by lnussel over 3 years ago

I think lua was one of the examples. Ie cases where we have a certain version in Leap and factory has the package renamed. We don't want the renamed package in Leap and need to avoid having to reject it again and again ie we did it now for 42.1 and 42.2 and should avoid doing it again for 42.3.

#9 Updated by mlin7442 over 3 years ago

if you mean lua52 what was dropped from 42.3, fcc_submitter will ignore it since fcc_submitter also checks the deleted request history and ignores them.

#10 Updated by mlin7442 over 3 years ago

  • Checklist changed from [x] set up ptoject, [ ] adjust fcc_submitter, [ ] announce to Factory mailing list to [x] set up ptoject, [x] adjust fcc_submitter
  • Due date changed from 2017-02-28 to 2017-05-31

extend the due date, fcc_submitter is submitting the package depend on the status between 42.3 and Factory, and new merged packages in 42.3.

#11 Updated by lnussel about 3 years ago

we should do a final round on Friday, then be done with it.

#12 Updated by lnussel about 3 years ago

  • % Done changed from 0 to 90

#13 Updated by lnussel about 3 years ago

  • Category set to Release Engineering
  • Status changed from New to Closed
  • % Done changed from 90 to 100

done

#14 Updated by lnussel almost 3 years ago

  • Copied to action #24840: submit new Factory packages to Leap added

Also available in: Atom PDF