I'm on a recent system (emerge.info attached) and I tried using Seahorse 3.34.1 but that one kept crashing on me -- with and without the USE="ldap" flag (my default is USE="-ldap") so then I just copied the ebuild for 3.34.1 and it worked awesome. ``` cp seahorse-3.34.1.ebuild seahorse-3.36.2.ebuild ebuild seahorse-3.36.2.ebuild digest emerge seahorse ``` Reproducible: Always Steps to Reproduce: I didn't save any of the console spew when 3.34.1 was crashing, sorry. But, I simply installed it, then ran and it would crash. Actual Results: Not sure what to put here, just copy the ebuild with a new version number and it worked perfectly for me. (which is what I expected) Expected Results: I expected to copy an ebuild to a new file to simply bump the version number and it should work OK (it was only a minor update). Just like the last dozen or so times I've done that "hack" on Gentoo to get a newer version it "just worked". I've been using Gentoo for like 15 years now, I still love it. Keep up the good work team!
Created attachment 647110 [details] My emerge --info
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=d556dbd3f16534a51dbe08cf8a3943eae8d26928 commit d556dbd3f16534a51dbe08cf8a3943eae8d26928 Author: Mart Raudsepp <leio@gentoo.org> AuthorDate: 2020-07-17 20:43:35 +0000 Commit: Mart Raudsepp <leio@gentoo.org> CommitDate: 2020-07-17 20:44:03 +0000 app-crypt/seahorse: bump to 3.36.2 Closes: https://bugs.gentoo.org/730194 Package-Manager: Portage-2.3.84, Repoman-2.3.20 Signed-off-by: Mart Raudsepp <leio@gentoo.org> app-crypt/seahorse/Manifest | 1 + app-crypt/seahorse/seahorse-3.36.2.ebuild | 73 +++++++++++++++++++++++++++++++ 2 files changed, 74 insertions(+)
