If the 'crypt' use flag is not set when emerging svk, the ebuild applies a patch to remove testing for gnupg. Apparently when the svk version was bumped to 1.02, a 'nognupgtest' patch matching this version was not added to portage (at least it has never appeared for me after many 'emerge sync' sessions over the weeks. As a consequence, the emerge of svk-1.02 fails because it can't find the patch. Reproducible: Always Steps to Reproduce: 1.USE="-crypt" emerge -u svk 2.watch it fail Actual Results: The emerge fails, complaining it can't find the file svk-1.02-nognupgtest.patch Expected Results: Apply the patch and successfully merge svk.
Created attachment 67343 [details, diff] svk-1.02-nognupgtest.patch My version of the patch to allow a successful merge.
The same applies to 1.01. This is pretty poor QA.
Fixed with permission from pclouds. Thanks for reporting and providing a patch Terry.
My pleasure.
Grr. I just attempted to merge svk-1.04 after syncing portage. Same problem - missing patch. Please don't update ebuilds unless they have been tested, folks. This is easy: 'USE="-crypt" emerge -u svk' is all it takes to verify you forgot something.
Reassigned to new maintainer
I upgraded svk to 1.05. I tested with and without crypt patch. Please test and confirm that I can close the bug (or not) :)
no feedback. I assume it works for everyone now. Closing.
