Hi Axel, haskell-hoogle maintainers,
Le 31/10/2016 à 13:25, Axel Beckert a écrit :
> David Prévot wrote:
>> Package: libjs-chosen
>> Version: 0.9.11-2
>> Severity: serious
>> Tags: sid stretch
>>
>> [ Filled as an RC-bug by the maintainer to see the package auto-removed
>> from testing. ]
>>
>>
Hi,
David Prévot wrote:
> Package: libjs-chosen
> Version: 0.9.11-2
> Severity: serious
> Tags: sid stretch
>
> [ Filled as an RC-bug by the maintainer to see the package auto-removed
> from testing. ]
>
> I packaged libjs-chosen as used by owncloud, but owncloud is going away,
> see #816376.
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Mon, 31 Oct 2016 20:42:42 +0100
Source: libjs-jquery-colorpicker
Binary: libjs-jquery-colorpicker
Architecture: source
Version: 1.2.6-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers
Package: libuv1-dev
Version: 1.9.1-1
Severity: important
Hi,
Trying to build software with libuv1-dev on kFreeBSD results in errors similar
to the following:
> cmake --build .
> [ 1%] Building C object CMakeFiles/neat.dir/neat_addr.c.o
> In file included from /usr/include/uv.h:62:0,
>
Package: npm2deb
Version: 0.2.5-3
Severity: minor
Tags: patch
Ohai,
d/copyright lists the following URLs for upstream:
Upstream-Contact: https://github.com/LeoIannaone/npm2deb/issues
Source: https://github.com/LeoIannaone/npm2deb
but upstream's username is LeoIannacone, with a c ;)
obvious
Processing commands for cont...@bugs.debian.org:
> forwarded 841995 https://github.com/LeoIannacone/npm2deb/pull/28
> (https://github.com/LeoIannacone/npm2deb/pull/28)
Bug #841995 [npm2deb] when package.json has a files section, install them
Set Bug forwarded-to-address to
libjs-jquery-colorpicker_1.2.6-1_source.changes uploaded successfully to
localhost
along with the files:
libjs-jquery-colorpicker_1.2.6-1.dsc
libjs-jquery-colorpicker_1.2.6.orig.tar.gz
libjs-jquery-colorpicker_1.2.6-1.debian.tar.xz
Greetings,
Your Debian queue daemon (running on
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Thu, 27 Oct 2016 20:25:13 +0200
Source: node-klaw
Binary: node-klaw
Architecture: source
Version: 1.3.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers
Hi,
On 31/10/2016 08:01, Lucas Nussbaum wrote:
On 29/10/16 at 11:14 +0200, Julien Puydt wrote:
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
FYI: The status of the uglifyjs source package
in Debian's testing distribution has changed.
Previous version: 2.4.15-6
Current version: 2.4.15-6.1
--
This email is automatically generated once a day. As the installation of
new packages into testing happens multiple times a day you will
FYI: The status of the node-ws source package
in Debian's testing distribution has changed.
Previous version: 1.0.0+ds1.e6ddaae4-1
Current version: 1.1.0+ds1.e6ddaae4-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-map-obj 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 day
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Mon, 31 Oct 2016 15:54:34 +0530
Source: node-global-modules
Binary: node-global-modules
Architecture: source all
Version: 0.2.3-1
Distribution: unstable
Urgency: low
Maintainer: Debian Javascript Maintainers
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Sun, 30 Oct 2016 07:51:19 +
Source: node-wcwidth.js
Binary: node-wcwidth.js
Architecture: source all
Version: 1.0.0-1
Distribution: unstable
Urgency: low
Maintainer: Debian Javascript Maintainers
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Mon, 31 Oct 2016 11:42:16 +0530
Source: node-for-own
Binary: node-for-own
Architecture: source all
Version: 0.1.4-1
Distribution: unstable
Urgency: low
Maintainer: Debian Javascript Maintainers
binary:node-cache-base is NEW.
source:node-cache-base 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
binary:node-global-modules is NEW.
source:node-global-modules 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
node-cache-base_0.8.4-1_amd64.changes uploaded successfully to localhost
along with the files:
node-cache-base_0.8.4-1.dsc
node-cache-base_0.8.4.orig.tar.gz
node-cache-base_0.8.4-1.debian.tar.xz
node-cache-base_0.8.4-1_all.deb
Greetings,
Your Debian queue daemon (running on host
node-global-modules_0.2.3-1_amd64.changes uploaded successfully to localhost
along with the files:
node-global-modules_0.2.3-1.dsc
node-global-modules_0.2.3.orig.tar.gz
node-global-modules_0.2.3-1.debian.tar.xz
node-global-modules_0.2.3-1_all.deb
Greetings,
Your Debian queue
Source: libuv
Severity: normal
Dear Maintainer,
The package libuv is failing to build from source on ppc64el, because
it is not passing on the test suite.
As you might see in the build log:
https://buildd.debian.org/status/fetch.php?pkg=libuv=ppc64el=0.10.36-4=1477310619
It failed on
Your message dated Mon, 31 Oct 2016 11:35:37 +
with message-id
and subject line Bug#842668: fixed in node-extend-shallow 2.0.1-2
has caused the Debian Bug report #842668,
regarding node-extend-shallow: FTBFS (Cannot find module 'is-extendable')
to be
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Mon, 31 Oct 2016 15:21:53 +0530
Source: node-extend-shallow
Binary: node-extend-shallow
Architecture: source
Version: 2.0.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers
node-extend-shallow_2.0.1-2_source.changes uploaded successfully to localhost
along with the files:
node-extend-shallow_2.0.1-2.dsc
node-extend-shallow_2.0.1-2.debian.tar.xz
Greetings,
Your Debian queue daemon (running on host usper.debian.org)
--
Pkg-javascript-devel mailing list
Your message dated Mon, 31 Oct 2016 10:49:59 +
with message-id
and subject line Bug#842669: fixed in node-map-visit 0.1.5-2
has caused the Debian Bug report #842669,
regarding node-map-visit: FTBFS (Cannot find module 'should')
to be marked as done.
This
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Mon, 31 Oct 2016 15:13:13 +0530
Source: node-map-visit
Binary: node-map-visit
Architecture: source
Version: 0.1.5-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers
node-map-visit_0.1.5-2_source.changes uploaded successfully to localhost
along with the files:
node-map-visit_0.1.5-2.dsc
node-map-visit_0.1.5-2.debian.tar.xz
Greetings,
Your Debian queue daemon (running on host usper.debian.org)
--
Pkg-javascript-devel mailing list
Your message dated Mon, 31 Oct 2016 10:35:35 +
with message-id
and subject line Bug#842667: fixed in node-collection-visit 0.2.3-2
has caused the Debian Bug report #842667,
regarding node-collection-visit: FTBFS (Cannot find module 'should')
to be marked
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Mon, 31 Oct 2016 15:13:56 +0530
Source: node-collection-visit
Binary: node-collection-visit
Architecture: source
Version: 0.2.3-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers
node-collection-visit_0.2.3-2_source.changes uploaded successfully to localhost
along with the files:
node-collection-visit_0.2.3-2.dsc
node-collection-visit_0.2.3-2.debian.tar.xz
Greetings,
Your Debian queue daemon (running on host usper.debian.org)
--
Pkg-javascript-devel mailing
Quoting Pirate Praveen (2016-10-31 10:39:58)
> On Monday 31 October 2016 03:07 PM, Jonas Smedegaard wrote:
> >> reducing severity to important, this does not have to block the release
> >> as it happens only in a few packages and which can easily be fixed.
> >
> > The tag is "severity", not
On Monday 31 October 2016 03:07 PM, Jonas Smedegaard wrote:
>> reducing severity to important, this does not have to block the release
>> as it happens only in a few packages and which can easily be fixed.
>
> The tag is "severity", not "complexity": If the bug cause failure to
> build packages
Quoting Pirate Praveen (2016-10-31 06:46:56)
> Control: severity -1 important
>
> On Sun, 9 Oct 2016 11:32:47 +0530 Pirate Praveen wrote:
> > severity: grave
> > justification: breaks package build
>
> reducing severity to important, this does not have to block the release
>
Package: src:node-extend-shallow
Version: 2.0.1-1
Severity: serious
Dear maintainer:
I tried to build this package in stretch with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:
Package: src:node-collection-visit
Version: 0.2.3-1
Severity: serious
Dear maintainer:
I tried to build this package in stretch with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:
Package: src:node-map-visit
Version: 0.1.5-1
Severity: serious
Dear maintainer:
I tried to build this package in stretch with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:
binary:node-for-own is NEW.
source:node-for-own 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 routinely
node-for-own_0.1.4-1_amd64.changes uploaded successfully to localhost
along with the files:
node-for-own_0.1.4-1.dsc
node-for-own_0.1.4.orig.tar.gz
node-for-own_0.1.4-1.debian.tar.xz
node-for-own_0.1.4-1_all.deb
Greetings,
Your Debian queue daemon (running on host
On 29/10/16 at 11:14 +0200, Julien Puydt wrote:
> 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
binary:node-wcwidth.js is NEW.
source:node-wcwidth.js 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
node-wcwidth.js_1.0.0-1_amd64.changes uploaded successfully to localhost
along with the files:
node-wcwidth.js_1.0.0-1.dsc
node-wcwidth.js_1.0.0.orig.tar.gz
node-wcwidth.js_1.0.0-1.debian.tar.xz
node-wcwidth.js_1.0.0-1_all.deb
Greetings,
Your Debian queue daemon (running on host
On Saturday 29 October 2016 08:52 PM, Debian FTP Masters wrote:
>
>
> Accepted:
Any idea why this is still stuck in NEW and not getting built?
https://ftp-master.debian.org/new/npm2deb_0.2.5-3.html
I see some other packages in NEW with similar issue where maintainer
looks like "all Build
41 matches
Mail list logo