profiles/base: use.mask dev-java/{ant-apache-,}bsf}[python] | profiles/package.mask: Last rite dev-java/jython

[vaukai]

Bug: https://bugs.gentoo.org/825486

[gentoo-repo-qa-bot]

Pull request CI report

Report generated at: 2023-04-03 08:08 UTC
Newest commit scanned: 7a47679
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/aebdd7b463/output.html

[gentoo-repo-qa-bot]

Pull request CI report

Report generated at: 2023-04-05 12:38 UTC
Newest commit scanned: d7e148f
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/57735e1ee5/output.html

[gentoo-bot]

Pull Request assignment

Submitter: @vaukai
Areas affected: profiles
Packages affected: (none)

@gentoo/github

Linked bugs

Bugs linked: 825486

New packages

This Pull Request appears to be introducing new packages only. Due to limited manpower, adding new packages is considered low priority. This does not mean that your Pull Request will not receive any attention, however, it might take quite some time for it to be reviewed. In the meantime, your new ebuild might find a home in the GURU project repository: the ebuild repository maintained collaboratively by Gentoo users. GURU offers your ebuild a place to be reviewed and improved by other Gentoo users, while making it easy for Gentoo users to install it and enjoy the software it adds.

---

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

Docs: Code of Conduct ● Copyright policy (expl.) ● Devmanual ● GitHub PRs ● Proxy-maint guide

[gentoo-repo-qa-bot]

Pull request CI report

Report generated at: 2023-04-05 12:53 UTC
Newest commit scanned: eb78be0
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/2ffe8933cd/output.html

[gentoo-repo-qa-bot]

Pull request CI report

Report generated at: 2023-04-05 13:13 UTC
Newest commit scanned: 54adcdc
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/3e6c02e079/output.html

[vaukai]

@fordfrog are there any objections against last riting dev-java/jython?

[gentoo-repo-qa-bot]

Pull request CI report

Report generated at: 2023-04-08 09:38 UTC
Newest commit scanned: ef59716
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/344218fd0c/output.html

[fordfrog]

@fordfrog are there any objections against last riting dev-java/jython?

i checked the github project and there is no jython-3 afaics, so imo it's ok to drop it. i'm just not sure about he process of dropping the use flags. is the mask needed or we can just drop them?

[vaukai]

@fordfrog are there any objections against last riting dev-java/jython?

i checked the github project and there is no jython-3 afaics, so imo it's ok to drop it. i'm just not sure about he process of dropping the use flags. is the mask needed or we can just drop them?

I think the procedure should be similar to what we did with dev-tex/pdfannotextractor in #23049.
The difference is, we can remove dev-java/jython as it's maintained by Java team while we could not remove pdfannotextractor which is not maintained by Java team.
So the package.use.mask could stay until there is a reason to touch those use-masked ebuilds.

[fordfrog]

oki, done! you can send the email now.