Bug#847091: [Pkg-javascript-devel] Bug#847091: Bug#847091: update node-extend to latest upstream release

2016-12-14 Thread Paolo Greppi
On 14/12/2016 10:55, Pirate Praveen wrote: > > > On 2016, ഡിസംബർ 14 2:16:46 PM IST, Paolo Greppi > wrote: >> That's because also node-liftoff (which is my ITP pipeline after >> node-fixed) depends on node-extend >= 3.0.0 >> > I think easier option would be to see if liftoff tests pass with node

Bug#847091: [Pkg-javascript-devel] Bug#847091: update node-extend to latest upstream release

2016-12-14 Thread Paolo Greppi
On 14/12/2016 10:53, Pirate Praveen wrote: > > > On 2016, ഡിസംബർ 14 2:16:46 PM IST, Paolo Greppi > wrote: >> >> Assuming we want to keep node-xtend and node-extend separate, I have >> prepared the update for this one in the alioth repo. >> >> That's because also node-liftoff (which is my ITP pi

Bug#847091: [Pkg-javascript-devel] Bug#847091: Bug#847091: update node-extend to latest upstream release

2016-12-14 Thread Pirate Praveen
On 2016, ഡിസംബർ 14 2:16:46 PM IST, Paolo Greppi wrote: >That's because also node-liftoff (which is my ITP pipeline after >node-fixed) depends on node-extend >= 3.0.0 > I think easier option would be to see if liftoff tests pass with node-extend 2.0 and relax dependencies in debian/control. --

Bug#847091: [Pkg-javascript-devel] Bug#847091: update node-extend to latest upstream release

2016-12-14 Thread Pirate Praveen
On 2016, ഡിസംബർ 14 2:16:46 PM IST, Paolo Greppi wrote: > >Assuming we want to keep node-xtend and node-extend separate, I have >prepared the update for this one in the alioth repo. > >That's because also node-liftoff (which is my ITP pipeline after >node-fixed) depends on node-extend >= 3.0.0 >

Bug#847091: [Pkg-javascript-devel] Bug#847091: update node-extend to latest upstream release

2016-12-14 Thread Paolo Greppi
On 05/12/2016 15:44, Pirate Praveen wrote: > On തിങ്കള്‍ 05 ഡിസംബര്‍ 2016 08:08 വൈകു, Jérémy Lal wrote: >> Do you mean node-xtend ? > > I think we missed avoiding duplication here (today I saw npm2deb warns > about it, though node-xtend was uploaded by someone else). > > $ apt-cache policy node-e

Bug#847091: update node-extend to latest upstream release

2016-12-05 Thread Jérémy Lal
2016-12-05 15:32 GMT+01:00 Pirate Praveen : > package: node-extend > version: 2.0.0-1 > severity: wishlist > control: block 847052 by -1 > > node-through2-filter depends on node-extend (>= 4.0.0) Do you mean node-xtend ? Jérémy

Bug#847091: update node-extend to latest upstream release

2016-12-05 Thread Pirate Praveen
On തിങ്കള്‍ 05 ഡിസംബര്‍ 2016 08:08 വൈകു, Jérémy Lal wrote: > Do you mean node-xtend ? I think we missed avoiding duplication here (today I saw npm2deb warns about it, though node-xtend was uploaded by someone else). $ apt-cache policy node-extend node-extend: Installed: 2.0.0-1 Candidate: 2.0

Bug#847091: update node-extend to latest upstream release

2016-12-05 Thread Pirate Praveen
package: node-extend version: 2.0.0-1 severity: wishlist control: block 847052 by -1 node-through2-filter depends on node-extend (>= 4.0.0) signature.asc Description: OpenPGP digital signature