> On Dec 23, 2014, at 7:01 AM, Tom Hughes <[email protected]> wrote:
>
>> On 23/12/14 11:45, Piotr Popieluch wrote:
>>
>> I am packaging nodejs-archiver but it depends on nodej-async ~0.9.0. The
>> tests fail with the current nodejs-async (0.2.10). It seems that there
>> are new methods in async 0.9 which archiver uses.
>>
>>
>> Could nodejs-archiver please be updated in Rawhide?
>>
>>
>> I see that this will break a couple of packages which require npm(async)
>> < 0.3:
>> jake-0:8.0.10-3.fc22.noarch
>> nodejs-form-data-0:0.1.1-2.fc21.noarch
>> nodejs-grunt-contrib-less-0:0.12.0-1.fc22.noarch
>> nodejs-grunt-contrib-watch-0:0.6.1-2.fc21.noarch
>> nodejs-grunt-init-0:0.3.1-2.fc21.noarch
>> nodejs-grunt-legacy-util-0:0.1.2-2.fc21.noarch
>> nodejs-utile-0:0.2.1-3.fc21.noarch
>> nodejs-winston-0:0.7.3-2.fc21.noarch
>> uglify-js-0:2.4.13-6.fc21.noarch
>>
>> I think this should be easily fixed by adding a %nodejs_fixdep or
>> updating to newest version, but I am not experienced with situations
>> like this... Any advice on how to handle this?
>
> That's usually the first thing to try, yes. I think jake is the only one
> there that is mine so I can take care of that if you shout once the new async
> is built.
>
> Tom
>
Please be very careful with uglifyjs; there are many packages which
BuildRequires it, and if that gets broken by this async update, it can have
far-reaching effects.
> --
> Tom Hughes ([email protected])
> http://compton.nu/
> _______________________________________________
> nodejs mailing list
> [email protected]
> https://admin.fedoraproject.org/mailman/listinfo/nodejs
_______________________________________________
nodejs mailing list
[email protected]
https://admin.fedoraproject.org/mailman/listinfo/nodejs
