action #1523: Check for linked packages while adding sr - Staging project workflow - openSUSE Project Management Tool

Actions

Copy link

action #1523

closed

Check for linked packages while adding sr

Added by _miska_ about 10 years ago. Updated almost 10 years ago.

Status:

Resolved

Priority:

Urgent

Assignee:

coolo

Target version:

Staging sprint 10

Start date:

2014-02-13

Due date:

% Done:

100%

Estimated time:

5.00 h

Description

When adding rq for package A into staging project, we should check whether there is no package B that is linked to A and if so, fix link in the staging project so B wouldn't point to A in parent project but to A in staging project. Think kernel.

Actions

Copy link

Updated by _miska_ about 10 years ago

Target version deleted (~~Future~~)

Actions

Copy link

Updated by coolo about 10 years ago

I'm not sure what you're up to here.
kernel-default links to 'kernel-source', so if we take 'kernel-source' kernel-default's link will be correct. And we shouldn't take kernel-desktop - at all.

Actions

Copy link

Updated by _miska_ about 10 years ago

One think that we spoke about in Nue was that if you have a project link and you have kernel-source in staging project, kernel-default from staging project links to kernel-default in parent project, which links to kernel-source in parent project. So the end results is kernel-default pointing to kernel-source from ring instead of staging. If this is not the case, we can close this as invalid :-)

Actions

Copy link

Updated by coolo about 10 years ago

Priority changed from Normal to Low

Yes, the links are prj-local. The only harm done is with links pointing to explicit projects.

E.g. 0-Bootstrap/gettext-runtime-mini points to 1-MinimalX/gettext-runtime. A request to gettext-runtime needs to take 2 things into account:

it's actually a bootstrap package
gettext-runtime-mini needs to be created with a prj-local link

But there are very few packages with that setup. So I set the prio to low

Actions

Copy link

Updated by scarabeus_iv about 10 years ago

Target version set to Future

Actions

Copy link

Updated by coolo almost 10 years ago

Assignee set to coolo
Priority changed from Low to High
Target version changed from Future to Staging sprint 5
Estimated time set to 5.00 h

due to having 3 rings now, this raised in priority ;(

Actions

Copy link

Updated by coolo almost 10 years ago

note: when adding to ring-1, check linked_packages on minimalX to then add a link

Actions

Copy link

Updated by coolo almost 10 years ago

Assignee changed from coolo to aplanas

I think this is better done by Alberto. To translate #7 into APIs :

When adding libqt4 to a staging prj, this is what needs to be done:

coolo@gertrude#~>osc api -X POST "/source/openSUSE:Factory:Rings:1-MinimalX/libqt4?cmd=showlinked"
<collection>
<package project="openSUSE:Factory:Rings:2-TestDVD" name="libqt4-sql-plugins"/>
</collection>

As another ring has a package linking, we need to create a link from F:DVD/libqt4-sql-plugins to F/libqt4 after adding libqt4 to F.

On rm_from_prj the same has to happen the other way around.

Actions

Copy link