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

app-vim/vim-spell-*: EAPI8 bump #36652

Closed
wants to merge 14 commits into from
Closed

Conversation

mm1ke
Copy link
Contributor

@mm1ke mm1ke commented May 12, 2024

This updates the vim-spell-* ebuilds for EAPI8.
I made a revision bump and dropped stable keywords for all of them, but since they only install some files i wondering if we can keep KEYWORDS here?


Please check all the boxes that apply:

  • I can submit this contribution in agreement with the Copyright Policy.
  • I have certified the above via adding a Signed-off-by line to every commit in the pull request.
  • This contribution has not been created with the assistance of Natural Language Processing artificial intelligence tools, in accordance with the AI policy.
  • I have run pkgcheck scan --commits --net to check for issues with my commits.

Please note that all boxes must be checked for the pull request to be merged.

mm1ke added 14 commits May 12, 2024 13:20
Signed-off-by: Michael Mair-Keimberger <mmk@levelnine.at>
Signed-off-by: Michael Mair-Keimberger <mmk@levelnine.at>
Signed-off-by: Michael Mair-Keimberger <mmk@levelnine.at>
Signed-off-by: Michael Mair-Keimberger <mmk@levelnine.at>
Signed-off-by: Michael Mair-Keimberger <mmk@levelnine.at>
Signed-off-by: Michael Mair-Keimberger <mmk@levelnine.at>
Signed-off-by: Michael Mair-Keimberger <mmk@levelnine.at>
Signed-off-by: Michael Mair-Keimberger <mmk@levelnine.at>
Signed-off-by: Michael Mair-Keimberger <mmk@levelnine.at>
Signed-off-by: Michael Mair-Keimberger <mmk@levelnine.at>
Signed-off-by: Michael Mair-Keimberger <mmk@levelnine.at>
Signed-off-by: Michael Mair-Keimberger <mmk@levelnine.at>
Signed-off-by: Michael Mair-Keimberger <mmk@levelnine.at>
Signed-off-by: Michael Mair-Keimberger <mmk@levelnine.at>
@gentoo-bot
Copy link

Pull Request assignment

Submitter: @mm1ke
Areas affected: ebuilds
Packages affected: app-vim/vim-spell-cs, app-vim/vim-spell-da, app-vim/vim-spell-de, app-vim/vim-spell-el, app-vim/vim-spell-en...

app-vim/vim-spell-cs: @jktjkt, @gentoo/vim
app-vim/vim-spell-da: @gentoo/vim
app-vim/vim-spell-de: @gentoo/vim
app-vim/vim-spell-el: @gentoo/vim
app-vim/vim-spell-en: @gentoo/vim
app-vim/vim-spell-es: @gentoo/vim
app-vim/vim-spell-fr: @gentoo/vim
app-vim/vim-spell-he: @gentoo/vim
app-vim/vim-spell-hu: @gentoo/vim
app-vim/vim-spell-it: @gentoo/vim
app-vim/vim-spell-nl: @gentoo/vim
app-vim/vim-spell-pl: @gentoo/vim
app-vim/vim-spell-pt: @gentoo/vim
app-vim/vim-spell-ru: @gentoo/vim

Linked bugs

No bugs to link found. If your pull request references any of the Gentoo bug reports, please add appropriate GLEP 66 tags to the commit message and request reassignment.

If you do not receive any reply to this pull request, please open or link a bug to attract the attention of maintainers.


In order to force reassignment and/or bug reference scan, please append [please reassign] to the pull request title.

Docs: Code of ConductCopyright policy (expl.) ● DevmanualGitHub PRsProxy-maint guide

@gentoo-bot gentoo-bot added assigned PR successfully assigned to the package maintainer(s). no bug found No Bug/Closes found in the commits. labels May 12, 2024
@mm1ke mm1ke changed the title app-vim/vim-speel-*: EAPI8 bump app-vim/vim-spell-*: EAPI8 bump May 12, 2024
@gentoo-repo-qa-bot
Copy link
Collaborator

Pull request CI report

Report generated at: 2024-05-12 11:59 UTC
Newest commit scanned: 3370f18
Status: ✅ good

There are existing issues already. Please look into the report to make sure none of them affect the packages in question:
https://qa-reports.gentoo.org/output/gentoo-ci/f56880b1e6/output.html

Copy link
Member

@arthurzam arthurzam left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I prefer we walk the same way, by destabilizing like you did, and then stablereq it.
But we can wait shorter period, let's say 14 days.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
assigned PR successfully assigned to the package maintainer(s). no bug found No Bug/Closes found in the commits.
Projects
None yet
4 participants