Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Detect if a cycle provides a new package, if not, ignore the cycle. #290

Merged
merged 1 commit into from Feb 12, 2015
Merged

Detect if a cycle provides a new package, if not, ignore the cycle. #290

merged 1 commit into from Feb 12, 2015

Conversation

aplanas
Copy link
Contributor

@aplanas aplanas commented Feb 11, 2015

No description provided.

@aplanas
Copy link
Contributor Author

aplanas commented Feb 12, 2015

r? @DimStar77 @coolo

@coolo
Copy link
Member

coolo commented Feb 12, 2015

I can't help reviewing this

@DimStar77
Copy link
Contributor

I think the code changes themselves make sense, but the warning should be put into some comment on the staging project;

as the repo-checker runs in a loop over everything, there is close to no way anybody would see this warning if it happens (which would mean we could as well just not warn at all).

@aplanas
Copy link
Contributor Author

aplanas commented Feb 12, 2015

@DimStar77 You are right.

  • Remove the comment when there are not new packages in the cycle.

aplanas added a commit that referenced this pull request Feb 12, 2015
Detect if a cycle provides a new package, if not, ignore the cycle.
@aplanas aplanas merged commit 8270699 into openSUSE:master Feb 12, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants