Project

General

Profile

Actions

action #6380

closed

staging accept: checking for new .spec files no longer works

Added by dimstar about 9 years ago. Updated about 9 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Target version:
-
Start date:
2015-02-23
Due date:
% Done:

0%

Estimated time:

Description

It seems the latest rewrite of the configuration changed the meaning of self.api.project when accepting packages (or it never worked, which is hard to believe.

We have this code:
for req in rqlist:
oldspecs = self.api.get_filelist_for_package(pkgname=req['packages'][0], project=self.api.project, extension='spec')
print 'Accepting request %d: %s' % (req['id'], ','.join(req['packages']))
change_request_state(self.api.apiurl, str(req['id']), 'accepted', message='Accept to %s' % self.api.project)
# Check if all .spec files of the package we just accepted has a package container to build
self.create_new_links(self.api.project, req['packages'][0], oldspecs)
changed = True

self.api.project USED to point to openSUSE:Factory (so we get the file list, accept the package, get the file list of the now checked in package and compare).

Currently, self.api.project seems to be pointing to the Staging project a package is coming from (no longer the target).

Actions #1

Updated by aplanas about 9 years ago

  • Assignee set to aplanas
Actions #2

Updated by coolo about 9 years ago

there is another problem - I guess related: staging select links 2nd ring packages into ring1.

Actions #3

Updated by aplanas about 9 years ago

  • Status changed from New to In Progress
Actions #4

Updated by dimstar about 9 years ago

Actions #5

Updated by aplanas about 9 years ago

  • Status changed from In Progress to Resolved

I added a test case for the multiple spec scenario. I guess that is safe to close this for now.

Actions

Also available in: Atom PDF