net-mail/dbmail: version bump to 3.2.5

[KenjiBrown]

Signed-off-by: Sandino Araico Sanchez sandino@sandino.net
Bug: https://bugs.gentoo.org/728060

[gentoo-bot]

Pull Request assignment

Submitter: @KenjiBrown
Areas affected: ebuilds
Packages affected: acct-group/dbmail, acct-user/dbmail, net-mail/dbmail

acct-group/dbmail: @gentoo/proxy-maint (new package)
acct-user/dbmail: @gentoo/proxy-maint (new package)
net-mail/dbmail: @LordVan

Linked bugs

Bugs linked: 728060

---

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: 2020-08-04 04:25 UTC
Newest commit scanned: 0183a81
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/3af878d7fe/output.html

[gentoo-repo-qa-bot]

Pull request CI report

Report generated at: 2020-08-17 05:56 UTC
Newest commit scanned: b1f51e9
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/b56baa8585/output.html

[KenjiBrown]

I know there are existing issues already in previous ebuilds. I have not touched them because they are stabilized and this new one is not.
Would it suffice if I just add a 3.2.3-r3 using eapi 7, acct/user and acct/group and wait for people to test it and ask for stabilization?

[juippis]

It wouldn't matter, really. We require all new ebuilds to be up to our standards when pushing. And revbumping for EAPI change etc requires a complete new copy.

All that being said, I only see one cosmetic issue in the ebuild? And it's probably not merged because @LordVan is on devaway. If you answer my question about ACCT_USER_HOME I'll push it forward.

Oh and please bump to latest version already, no reason to push 3.2.4 to the tree when next day you'd make an ebuild for 3.2.5. Just push it as a new commit here and remove 3.2.4 if you don't know how to rebase and reorder/squash your commits with git.

[gentoo-repo-qa-bot]

Pull request CI report

Report generated at: 2020-09-18 07:52 UTC
Newest commit scanned: 2c8d8cc
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/fb85fd51c4/output.html

[juippis]

Hi, sorry it's taken so long. It's apparent @LordVan is not coming back in a while so I took another peek. Do I dare to ask you to hone the small issues I found off? Got my eyes on this now.

[gentoo-repo-qa-bot]

Pull request CI report

Report generated at: 2021-01-10 10:10 UTC
Newest commit scanned: c4031ab
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/16a9e2f7ee/output.html