1.0.0 has been in tree for long enough, though may need to wait for stabilisation bug 631124 in order to fix pinentry bug 609678
(In reply to Andreas Sturmlechner from comment #0) > 1.0.0 has been in tree for long enough, though may need to wait for > stabilisation bug 631124 in order to fix pinentry bug 609678 Either that or backport the two patches from master as discussed with robbat some days ago for a -r2. Except for that I'm fine with stabilizing the new pinentry version though
@robbat2: can you confirm that -r2 is working for awesomewm?
no response is positive response?
(In reply to Andreas Sturmlechner from comment #3) > no response is positive response? I have no objection to calling for stable.
ia64 stable
Stable on amd64
x86 stable
Stable on alpha.
ppc64 stable
ppc stable
arm stable
hppa stable
seems all stable arches are done, cleanup ready?
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=cec537a1e49f84fbd3ec055fcbf7e80fd825ecf4 commit cec537a1e49f84fbd3ec055fcbf7e80fd825ecf4 Author: Andreas Sturmlechner <asturm@gentoo.org> AuthorDate: 2017-12-21 14:58:29 +0000 Commit: Andreas Sturmlechner <asturm@gentoo.org> CommitDate: 2017-12-21 14:59:02 +0000 app-crypt/pinentry: Drop 0.9.7-r1 Bug: https://bugs.gentoo.org/632293 Package-Manager: Portage-2.3.19, Repoman-2.3.6 app-crypt/pinentry/Manifest | 1 - ...pinentry-0.9.7-require-CPP11-for-qt-5-7.patches | 48 -------- app-crypt/pinentry/pinentry-0.9.7-r1.ebuild | 122 --------------------- 3 files changed, 171 deletions(-)}
sparc stable (thanks to Rolf Eike Beer)
arm64 stable. Last arch, closing
