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

Warn if a lib32-$package exists and no open AVG exists #120

Open
jelly opened this issue Mar 19, 2018 · 0 comments · May be fixed by #129
Open

Warn if a lib32-$package exists and no open AVG exists #120

jelly opened this issue Mar 19, 2018 · 0 comments · May be fixed by #129

Comments

@jelly
Copy link
Member

jelly commented Mar 19, 2018

When creating an AVG for libvorbis, warn that lib32-vorbis also exists in the repositories and most likely also needs an AVG (they have a different pkgbase).

Test case

  • Create an AVG for libvorbis
  • Check if lib32-libvorbis exists
  • Inform the reporter via a flash message that lib32-libvorbis also exists if there is no open AVG for it.
@jelly jelly changed the title Warn if a lib32-$package exists and no AVG is created Warn if a lib32-$package exists and no open AVG exists Mar 19, 2018
jelly added a commit to jelly/arch-security-tracker that referenced this issue Jun 11, 2018
When adding a new group, warn if the lib32 variant does not exists via a
flashcard.

Closes: archlinux#120
@jelly jelly linked a pull request Jun 11, 2018 that will close this issue
jelly added a commit to jelly/arch-security-tracker that referenced this issue Jun 18, 2018
When adding a new group, warn if the lib32 variant does not exists via a
flashcard.

Closes: archlinux#120
jelly added a commit to jelly/arch-security-tracker that referenced this issue Jun 18, 2018
When adding a new group, warn if the lib32 variant does not exists via a
flashcard.

Closes: archlinux#120
@anthraxx anthraxx added this to the 0.9 milestone Oct 24, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants