openSUSE Release Process » openSUSE Leap 42.3 Release

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 :)

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?

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?

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.

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.

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