Closed trentm closed 3 years ago
note that I published a trentm-hashlib 1.0.1 to npm until you're able to publish a new hashlib.
Sorry for the late answer, was too busy last week. Already send email to Isaac.
Regards, Oleg Illarionov (Олег Илларионов) icq 816969 jabber oleg@emby.ru email oleg@emby.ru skype webmovement
On 20 July 2011 02:25, trentm < reply@reply.github.com>wrote:
Illarionov,
Could you increment the hashlib version (in package.json, e.g. to "1.0.1") and publish a new version of hashlib, please? I need a new release with the fix for issue #16 (build fix for solaris/smartos from Ryan) to be able to use "hashlib" in my own node.js project's "package.json" file.
From reading
npm info hashlib
and speaking with @isaacs, my understanding is that isaacs published "hashlib" to the npm registry. Isaac would be fine cleaning up ownership of "hashlib" in the npm registry so that you're the owner. First you'd need to create an user account with the npm registry vianpm adduser
and then pass your npm username on to Isaac to clean up. I can help co-ordinate that, if that would help.Thanks, Trent
Reply to this email directly or view it on GitHub: https://github.com/brainfucker/hashlib/issues/20
Should be resolved now, thanks Oleg. (This was the last "admin party" module that I'd had to take ownership of, so it's nice to finally have that all cleared up!)
Thanks very much =)
Regards, Oleg Illarionov (Олег Илларионов) icq 816969 jabber oleg@emby.ru email oleg@emby.ru
On 26 July 2011 02:16, isaacs < reply@reply.github.com>wrote:
Should be resolved now, thanks Oleg. (This was the last "admin party" module that I'd had to take ownership of, so it's nice to finally have that all cleared up!)
Reply to this email directly or view it on GitHub: https://github.com/brainfucker/hashlib/issues/20#issuecomment-1649877
Illarionov,
Could you increment the hashlib version (in package.json, e.g. to "1.0.1") and publish a new version of hashlib, please? I need a new release with the fix for issue #16 (build fix for solaris/smartos from Ryan) to be able to use "hashlib" in my own node.js project's "package.json" file.
From reading
npm info hashlib
and speaking with @isaacs, my understanding is that isaacs published "hashlib" to the npm registry. Isaac would be fine cleaning up ownership of "hashlib" in the npm registry so that you're the owner. First you'd need to create an user account with the npm registry vianpm adduser
and then pass your npm username on to Isaac to clean up. I can help co-ordinate that, if that would help.Thanks, Trent