Rename from 1.4.0 works fine. Btw, how many test failures do you run into? I want to start filing upstream but feel that test reporting from portage is somewhat unreliable. I get two fails: [% 10|+ 26|- 0|T 0|S 0]: pipe_set_non_blocking `pipe_set_non_blocking` failed: exit code 6 Output from process `pipe_set_non_blocking`: Assertion failed in /var/tmp/portage/dev-libs/libuv-1.4.2/work/libuv-1.4.2/test/test-pipe-set-non-blocking.c on line 51: n == 0 [% 82|+ 193|- 1|T 0|S 11]: fs_fstat `fs_fstat` failed: exit code 6 Output from process `fs_fstat`: Assertion failed in /var/tmp/portage/dev-libs/libuv-1.4.2/work/libuv-1.4.2/test/test-fs.c on line 1115: s->st_atim.tv_nsec == 0
test outside of portage before reporting bugs upstream
(In reply to Julian Ospald (hasufell) from comment #1) > test outside of portage before reporting bugs upstream I always do. I'm pretty active contributing upstream to both io.js (and libuv by extension) - every now and then I encounter bugs that's specific to running from portage which is why I asked you for your output.
+*libuv-1.4.2 (05 Mar 2015) + + 05 Mar 2015; Julian Ospald <hasufell@gentoo.org> +libuv-1.4.2.ebuild: + version bump
