On Sat, 29 Oct 2016 13:13:51 + shana...@disroot.org wrote:
> All npm modules should have a package.json.
>
> The issue is npm2deb retrieves module source from git repo instead of npm
> registry.
>
> This will be fixed with #842465
>
FYI: The status of the node-get-value source package
in Debian's testing distribution has changed.
Previous version: (not in testing)
Current version: 2.0.6-1
--
This email is automatically generated once a day. As the installation of
new packages into testing happens multiple times a day
FYI: The status of the node-isexe source package
in Debian's testing distribution has changed.
Previous version: (not in testing)
Current version: 1.1.2-1
--
This email is automatically generated once a day. As the installation of
new packages into testing happens multiple times a day you
FYI: The status of the node-collection-visit source package
in Debian's testing distribution has changed.
Previous version: (not in testing)
Current version: 0.2.3-1
--
This email is automatically generated once a day. As the installation of
new packages into testing happens multiple
FYI: The status of the node-object-visit source package
in Debian's testing distribution has changed.
Previous version: (not in testing)
Current version: 0.3.4-1
--
This email is automatically generated once a day. As the installation of
new packages into testing happens multiple times a
node-global-prefix_0.1.4-1_amd64.changes uploaded successfully to localhost
along with the files:
node-global-prefix_0.1.4-1.dsc
node-global-prefix_0.1.4.orig.tar.gz
node-global-prefix_0.1.4-1.debian.tar.xz
node-global-prefix_0.1.4-1_all.deb
Greetings,
Your Debian queue daemon
binary:node-global-prefix is NEW.
source:node-global-prefix is NEW.
Your package has been put into the NEW queue, which requires manual action
from the ftpteam to process. The upload was otherwise valid (it had a good
OpenPGP signature and file hashes are valid), so please be patient.
Packages
All npm modules should have a package.json.
The issue is npm2deb retrieves module source from git repo instead of npm
registry.
This will be fixed with #842465
(https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=842465)
--
Pkg-javascript-devel mailing list
Your message dated Sat, 29 Oct 2016 15:22:26 +
with message-id
and subject line Bug#836182: fixed in npm2deb 0.2.5-3
has caused the Debian Bug report #836182,
regarding [npm2deb] npm2deb is unable to detect already available dependencies
to be marked as
Your message dated Sat, 29 Oct 2016 15:22:26 +
with message-id
and subject line Bug#836182: fixed in npm2deb 0.2.5-3
has caused the Debian Bug report #836182,
regarding [npm2deb] npm2deb unable to detect already available dependencies
to be marked as done.
FYI: The status of the node-component-emitter source package
in Debian's testing distribution has changed.
Previous version: (not in testing)
Current version: 1.2.1-1
--
This email is automatically generated once a day. As the installation of
new packages into testing happens multiple
FYI: The status of the node-fill-range source package
in Debian's testing distribution has changed.
Previous version: (not in testing)
Current version: 3.0.3-1
--
This email is automatically generated once a day. As the installation of
new packages into testing happens multiple times a
FYI: The status of the node-concat-map source package
in Debian's testing distribution has changed.
Previous version: (not in testing)
Current version: 0.0.1-1
--
This email is automatically generated once a day. As the installation of
new packages into testing happens multiple times a
FYI: The status of the node-extend-shallow source package
in Debian's testing distribution has changed.
Previous version: (not in testing)
Current version: 2.0.1-1
--
This email is automatically generated once a day. As the installation of
new packages into testing happens multiple times
Processing commands for cont...@bugs.debian.org:
> forwarded 840169 https://github.com/LeoIannacone/npm2deb/pull/25
> (https://github.com/LeoIannacone/npm2deb/pull/25)
Bug #840169 [npm2deb] npm2deb search lex-parser crashes
Set Bug forwarded-to-address to
Package: npm2deb
Version: 0.2.5-1
Severity: important
Dear Maintainer,
Using git repo url in debian/watch file creates the following issues.
1. Tags in git repo need not match with npm versions, in such cases npm2deb
fails to get exact version that npm registry holds
2. In some packages even
node-to-regex_3.0.1-1_amd64.changes uploaded successfully to localhost
along with the files:
node-to-regex_3.0.1-1.dsc
node-to-regex_3.0.1.orig.tar.gz
node-to-regex_3.0.1-1.debian.tar.xz
node-to-regex_3.0.1-1_all.deb
Greetings,
Your Debian queue daemon (running on host
FYI: The status of the node-filename-regex source package
in Debian's testing distribution has changed.
Previous version: (not in testing)
Current version: 2.0.0-1
--
This email is automatically generated once a day. As the installation of
new packages into testing happens multiple times
FYI: The status of the node-signal-exit source package
in Debian's testing distribution has changed.
Previous version: (not in testing)
Current version: 3.0.1-1
--
This email is automatically generated once a day. As the installation of
new packages into testing happens multiple times a
FYI: The status of the node-map-visit source package
in Debian's testing distribution has changed.
Previous version: (not in testing)
Current version: 0.1.5-1
--
This email is automatically generated once a day. As the installation of
new packages into testing happens multiple times a day
FYI: The status of the node-hosted-git-info source package
in Debian's testing distribution has changed.
Previous version: (not in testing)
Current version: 2.1.5-1
--
This email is automatically generated once a day. As the installation of
new packages into testing happens multiple times
FYI: The status of the node-map-cache source package
in Debian's testing distribution has changed.
Previous version: (not in testing)
Current version: 0.2.2-1
--
This email is automatically generated once a day. As the installation of
new packages into testing happens multiple times a day
FYI: The status of the node-is-primitive source package
in Debian's testing distribution has changed.
Previous version: (not in testing)
Current version: 2.0.0-1
--
This email is automatically generated once a day. As the installation of
new packages into testing happens multiple times a
Processing commands for cont...@bugs.debian.org:
> owner 835125 !
Bug #835125 [src:jqueryui] jqueryui: Wrong licensing information: Licensed
under MIT, *not* GPL-2
Owner recorded as Paul Gevers .
> tags 835125 pending
Bug #835125 [src:jqueryui] jqueryui: Wrong licensing
binary:node-to-regex is NEW.
source:node-to-regex is NEW.
Your package has been put into the NEW queue, which requires manual action
from the ftpteam to process. The upload was otherwise valid (it had a good
OpenPGP signature and file hashes are valid), so please be patient.
Packages are
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Sat, 29 Oct 2016 13:57:45 +0530
Source: npm2deb
Binary: npm2deb
Architecture: source
Version: 0.2.5-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers
On 28/10/2016 15:24, Mattia Rizzolo wrote:
> IMHO, you could join the team if you haven't, commit your changes, and
OK, I have sent a couple of commits to
https://anonscm.debian.org/cgit/pkg-javascript/node-findup-sync.git,
they are the changes with higher priority (0.1.3-2).
As I am not 100%
2016-10-29 15:08 GMT+02:00 Shanavas M :
> Package: npm2deb
> Version: 0.2.5-1
> Severity: important
>
> Dear Maintainer,
>
> Using git repo url in debian/watch file creates the following issues.
>
> 1. Tags in git repo need not match with npm versions, in such cases
>
node-globule 0.2.0-1 is marked for autoremoval from testing on 2016-12-05
It (build-)depends on packages with these RC bugs:
841698: node-lodash: FTBFS with bash as /bin/sh
--
Pkg-javascript-devel mailing list
Pkg-javascript-devel@lists.alioth.debian.org
node-findup-sync 0.1.3-1 is marked for autoremoval from testing on 2016-12-05
It (build-)depends on packages with these RC bugs:
841698: node-lodash: FTBFS with bash as /bin/sh
--
Pkg-javascript-devel mailing list
Pkg-javascript-devel@lists.alioth.debian.org
node-lodash 2.4.1+dfsg-3 is marked for autoremoval from testing on 2016-12-05
It is affected by these RC bugs:
841698: node-lodash: FTBFS with bash as /bin/sh
--
Pkg-javascript-devel mailing list
Pkg-javascript-devel@lists.alioth.debian.org
On Sun, 9 Oct 2016 14:18:47 +0530 Pirate Praveen wrote:
> uupdate -b can also be run automatically. Once we have all required
> files, we should run dpkg-buildpackage as well like gem2deb does for
> ruby gems.
>
We can make this with just 'npm2deb ' (instead of changing
Processing commands for cont...@bugs.debian.org:
> forwarded 840207 https://github.com/LeoIannacone/npm2deb/pull/27
Bug #840207 [npm2deb] dependency formats are not converted
Set Bug forwarded-to-address to
'https://github.com/LeoIannacone/npm2deb/pull/27'.
>
End of message, stopping processing
Hi,
I tried to "pbuilder create" a new base.tgz, but it still had tzdata and
lsb-base, so I had to "pbuilder login --save-after-login" and remove
them by hand using "dpkg --purge" (then "apt-get autoremove" that did
nothing). I still had no problem building node-es6-promise.
How can I get
npm2deb_0.2.5-3_source.changes uploaded successfully to localhost
along with the files:
npm2deb_0.2.5-3.dsc
npm2deb_0.2.5-3.debian.tar.xz
Greetings,
Your Debian queue daemon (running on host usper.debian.org)
--
Pkg-javascript-devel mailing list
35 matches
Mail list logo