dev-python/yara-python: update Manifest

[hamarituc]

Closes: https://bugs.gentoo.org/866115
Signed-off-by: Mario Haustein mario.haustein@hrz.tu-chemnitz.de

[gentoo-bot]

Pull Request assignment

Submitter: @hamarituc
Areas affected: ebuilds
Packages affected: dev-python/yara-python

dev-python/yara-python: @hamarituc, @thesamesam

Linked bugs

Bugs linked: 866115

---

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: 2022-08-23 15:46 UTC
Newest commit scanned: 0438e7a
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/28a7b085bd/output.html

[thesamesam]

Do we know what happened here? Can you diff the tarballs?

[hamarituc]

Do we know what happened here? Can you diff the tarballs?

Unfortunately, I don't have the original tarball anymore. But there are two release notifications from GitHub in my mailbox, one dated at Tue, 09 Aug 2022 07:51:47 UTC and one at Tue, 09 Aug 2022 14:18:40 UTC concerning version 4.2.3. My commit was at Tue Aug 9 11:38:20 2022 UTC right between the two releases. It seems upstream amended the release after my pull request.

[thesamesam]

OK. Please ask upstream to not do this again as it frightens us packagers :)

Does the diff between last version and this version look OK? (Nothing malicious)?

EDIT: I've diffed and it looks OK. I'll add your explanation into the commit message. This kind of thing is worth explaining. Thank you!