On 03/15/2015 10:29 PM, Jérémy Lal wrote:
> i'd rather not fix the situation right now with an epoch, and instead
> please upload your merged version instead, and let it hang in unstable
> until global warming (as opposed to deep freeze).
> If you want to have a usable node-tar 1.0.3, you can updat
Le dimanche 15 mars 2015 à 20:44 +0100, Sebastiaan Couwenberg a écrit :
> Hi Jérémy,
>
> On 03/14/2015 01:38 PM, Sebastiaan Couwenberg wrote:
> >> On Sat, Mar 14, 2015 at 2:29 AM, Jérémy Lal wrote:
> >>> >> Did you just hijack node-tar that was already in the archive ?
> > Apparently I fucked tha
Hi Jérémy,
On 03/14/2015 01:38 PM, Sebastiaan Couwenberg wrote:
>> On Sat, Mar 14, 2015 at 2:29 AM, Jérémy Lal wrote:
>>> >> Did you just hijack node-tar that was already in the archive ?
> Apparently I fucked that up. I didn't look well enough to see that it
> was already packaged.
>
> I'm sorr
On 03/14/2015 11:23 AM, Leo Iannacone wrote:
> On Sat, Mar 14, 2015 at 2:29 AM, Jérémy Lal wrote:
>> Did you just hijack node-tar that was already in the archive ?
Apparently I fucked that up. I didn't look well enough to see that it
was already packaged.
I'm sorry about that, and I will revert
On Sat, Mar 14, 2015 at 2:29 AM, Jérémy Lal wrote:
> Did you just hijack node-tar that was already in the archive ?
>
> Please contact pkg-javascript and try to coordinate your uploads with
> this team. Check its wiki, read what npm2deb says about the modules
> you're packaging.
>
> For instance,
Did you just hijack node-tar that was already in the archive ?
Please contact pkg-javascript and try to coordinate your uploads with
this team. Check its wiki, read what npm2deb says about the modules
you're packaging.
For instance, the team was avoiding node-readable-stream for some
reason.
It w
