July 2017 TC meeting is at 'Wed Jul 19 19:00:00 UTC 2017'

2017-07-17 Thread Didier 'OdyX' Raboud
The monthly Debian Technical Committee Meeting is happening in two days:

date -d 'Wed Jul 19 19:00:00 UTC 2017'
in #debian-ctte on irc.debian.org

The agenda was updated accordingly in git; please make any necessary changes 
or additions.

Cheers,
OdyX

signature.asc
Description: This is a digitally signed message part.


Bug#862051: Refer #862051 to ctte

2017-07-17 Thread Ian Jackson
How about this:

  1. The CTTE decision in from 2012-07-12 in bug #614907 is repealed.
  2. The nodejs package shall be free to provide /usr/bin/node.
 Eventually, packages which use node.js will use /usr/bin/node,
 and the nodejs-legacy package will become obsolete, and be
 removed.
  3. All of this should be managed according to Debian's usual
 backwards-compatibility arrangements, and without needlessly
 breaking anything.
  4. /usr/bin/nodejs should continue to exist indefinitely.

Ian.



Re: Bug#862051: Refer #862051 to ctte

2017-07-17 Thread Philip Hands
Ian Jackson  writes:

> Anthony DeRobertis writes ("Re: Bug#862051: Refer #862051 to ctte"):
>> On 07/14/2017 12:57 PM, Tollef Fog Heen wrote:
>> > Fair point.
>> >
>> >3. Once a new nodejs package providing /usr/bin/node is in the
>> >   archive, other packages in the archive are free to depend on the
>> >   nodejs package and use /usr/bin/node .
>> 
>> That should probably be a versioned Depends, at least until a stable 
>> release includes /usr/bin/node in nodejs. Otherwise upgrades may break.
>> 
>> OTOH, is this paragraph (or 2, for that matter) really needed? They're 
>> just restating (somewhat imperfectly) Policy and/or normal practice in 
>> Debian, which presumably come back into effect anyway once the 
>> 2012-07-12 decision is repealed.
>
> It would be better to simply say "following Debian's existing backward
> compatibility practices" or something, than trying to restate it all.

Quite -- I think we just need to have clause 1 in the resolution itself.

We could have some suggestions as additional notes to describe the
consequences of the revocation.

Like mentioning that where a versioned depends on nodejs is deemed
necessary, the Depends: should probably also allow nodejs-legacy as an
alternative option, since that also provides /usr/bin/node.

Cheers, Phil.
-- 
|)|  Philip Hands  [+44 (0)20 8530 9560]  HANDS.COM Ltd.
|-|  http://www.hands.com/http://ftp.uk.debian.org/
|(|  Hugo-Klemm-Strasse 34,   21075 Hamburg,GERMANY


signature.asc
Description: PGP signature


Re: Bug#862051: Refer #862051 to ctte

2017-07-17 Thread Ian Jackson
Anthony DeRobertis writes ("Re: Bug#862051: Refer #862051 to ctte"):
> On 07/14/2017 12:57 PM, Tollef Fog Heen wrote:
> > Fair point.
> >
> >3. Once a new nodejs package providing /usr/bin/node is in the
> >   archive, other packages in the archive are free to depend on the
> >   nodejs package and use /usr/bin/node .
> 
> That should probably be a versioned Depends, at least until a stable 
> release includes /usr/bin/node in nodejs. Otherwise upgrades may break.
> 
> OTOH, is this paragraph (or 2, for that matter) really needed? They're 
> just restating (somewhat imperfectly) Policy and/or normal practice in 
> Debian, which presumably come back into effect anyway once the 
> 2012-07-12 decision is repealed.

It would be better to simply say "following Debian's existing backward
compatibility practices" or something, than trying to restate it all.

Ian.

-- 
Ian JacksonThese opinions are my own.

If I emailed you from an address @fyvzl.net or @evade.org.uk, that is
a private address which bypasses my fierce spamfilter.