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.

Sign up for GitHub

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

Jump to bottom

ALLARCHES incorrectly assumed done when some packages on the list don't have older keywords #47

Open
mgorny opened this issue Jul 9, 2020 · 4 comments
Open

ALLARCHES incorrectly assumed done when some packages on the list don't have older keywords #47

mgorny opened this issue Jul 9, 2020 · 4 comments

Comments

@mgorny
Copy link
Member

mgorny commented Jul 9, 2020

Example: https://bugs.gentoo.org/731414

In this case, ALLARCHES could be applied to a subset of arches but these without older keywords should be handled normally.
@thesamesam
Copy link
Contributor

This seems to have happened in https://bugs.gentoo.org/767115 where dev-python/iniconfig is ALLARCHES but has not yet been stabled on hppa in the past.

@mgorny
Copy link
Member Author

mgorny commented Jan 26, 2021

Oh my, it seems that I have forgotten to implement that part of logic entirely. Right now is_allarches() only checks metadata.xml.

@mgorny
Copy link
Member Author

mgorny commented Jan 26, 2021

Ah, nevermind. We do permit ALLARCHES on the bug and do filtering for it in match_package_list().

@thesamesam
Copy link
Contributor

This hit us in bug 775806 where we'd never stabled before anywhere.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@mgorny @thesamesam