Hello,
Le 2018-11-26 03:01, Pirate Praveen a écrit :
You can try using node-neo-async instead for your package. It is
supposed to be a drop in replacement for node-async.
https://tracker.debian.org/pkg/node-neo-async
Thanks for pointing out node-neo-async!
I ran a manual test of the package
On 2018, നവംബർ 26 2:01:18 AM IST, Jonas Smedegaard wrote:
>Please note that packaging multiple major versions of Nodejs packages
>is
>unusual in Debian. You might want to hear the opinions of others in
>the
>team as well. My reason for suggesting it here is that we are close to
>
>freeze - a
Quoting Nicolas Mora (2018-11-25 20:57:41)
> Le 18-11-25 à 13 h 56, Jonas Smedegaard a écrit :
> > Did you check that none of the 6 reverse dependencies and none of
> > the 67 reverse build-dependencies break when doing such a major
> > upgrade? Beware of packages with no or inferior or skipped
Hello,
Le 18-11-25 à 13 h 56, Jonas Smedegaard a écrit :
> Did you check that none of the 6 reverse dependencies and none of the 67
> reverse build-dependencies break when doing such a major upgrade?
> Beware of packages with no or inferior or skipped testsuites: Quite
> likely manual inspecti
Hi Nicolas,
Quoting Nicolas Mora (2018-11-25 19:05:38)
> In order to package node-istanbuljs, I made a new package for
> node-async based on the original node-async package.
Did you check that none of the 6 reverse dependencies and none of the 67
reverse build-dependencies break when doing such
Hello Jonas,
In order to package node-istanbuljs, I made a new package for node-async
based on the original node-async package. The new features for the
package are:
* New upstream version
* Add node-babel-plugin-add-module-exports as dependency
* Bump Standards-Version to 4.2.1, no changes
