[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#881339: marked as done (allow node-babel-preset-env to build depend on itself)

Your message dated Wed, 21 Feb 2018 19:54:43 +0100
with message-id <2a308575644ced7853bf3b37f4f644cb@debian.org>
and subject line Closing without action: the TC can't overrule delegates
has caused the Debian Bug report #881339,
regarding allow node-babel-preset-env to build depend on itself
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
881339: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881339
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: tech-ctte

node-babel-preset-env is a collections of plugins for babel transpiler
(node-babel package).

Babel is a transpiler to convert source written in new versions of
javascript to code that can be run by current versions of javascript
runtimes like nodejs and browsers.

node-babel-preset-env uses its own binary package during build. This is
similar to  how other packages currently in the archive which were
circularly build depending, like node-babel build depends on itself and
node-babylon, then node-babylon build depends on node-babel (this was
the same case of jison and one of its build dependencies). In these
situations a binary included upload had to be used to bootstrap and
later versions can just be built in main using the previous versions. I
don't think node-babel-preset is in principle any different from
node-babel, node-babylon or jison.

But node-babel-preset-env was rejected "it is strange that the package
Build-Depends: on itself!?"

http://lists.alioth.debian.org/pipermail/pkg-javascript-devel/2017-November/022197.html

Alternatives would be to use another transpiler to build the package.
But I don't think that should be required as a condition as it means
this same principle will need to be applied for other packages already
in main. Is gcc built using a different compiler?

I would like to ask CTTE to consider this case and overrule ftp masters
decision and allow node-babel-preset-env to be in main as it has dfsg
compliant license, has corresponding source and can be built using tools
in main (with an initial bootstrapping).

Attachment: signature.asc
Description: OpenPGP digital signature


--- End Message ---
--- Begin Message --- 
Hi!

I'm sorry this took so long to be actioned by us. This is on me.

In previous bugs that have been raised to the technical committee
it has already been discussed and agreed that the technical
committee does not have the power to overrule official Debian
delegates.  This covers the decisions taken for example by the
FTP Masters or the Release Team.

Thus, we are closing this bug now, as it's not actionable.

We suggest that you work together with the FTP Masters in
figuring out a solution to this problem.

--
Thanks.
Marga, on behalf of the Technical Committee.

--- End Message ---
Reply to: