Re: Bug#830978: Browserified javascript and DFSG 2

2016-07-15 Thread Neil Williams
On Fri, 15 Jul 2016 23:45:01 +0530 Pirate Praveen wrote: > On 2016, ജൂലൈ 15 10:46:51 PM IST, Ian Jackson > wrote: > >Sam Hartman writes ("Bug#830978: Browserified javascript and DFSG > >2"): > >> Speaking as an individual TC member,

Re: Bug#830978: Browserified javascript and DFSG 2

2016-07-15 Thread Philip Hands
Pirate Praveen writes: ... >> * For Debian, therefore, the source code for a file or program is the >> form which can be conveniently modified and shared; specifically, >> the form in which upstream will accept patches. > > This was never the intention of dfsg, it

Bug#831426: jessie-pu: package ccache/3.1.12-1

2016-07-15 Thread Joel Rosdahl
Package: release.debian.org User: release.debian@packages.debian.org Usertags: pu Tags: jessie Severity: normal As suggested by Stefan Fritsch in #829088 ("ccache may silently miscompile symlinked source files"), I propose to upgrade ccache from 3.1.10 to 3.1.12 in jessie. I'm the upstream

Re: [release-tools] [PATCH] testing.pl is gone, update links to it to qa.d.o/excuses.php

2016-07-15 Thread Adam D. Barratt
On Fri, 2016-07-15 at 22:48 +0800, Paul Wise wrote: > --- > queue-viewer/overview.xslt | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/queue-viewer/overview.xslt b/queue-viewer/overview.xslt > index 0ec63f0..d79127c 100644 > --- a/queue-viewer/overview.xslt > +++

Re: Bug#830978: Browserified javascript and DFSG 2

2016-07-15 Thread Pirate Praveen
On 2016, ജൂലൈ 15 10:46:51 PM IST, Ian Jackson wrote: >Sam Hartman writes ("Bug#830978: Browserified javascript and DFSG 2"): >> Speaking as an individual TC member, here's my personal reading of >the >> TC discussion. >> >> It's not clear that the TC is the

Re: Bug#830978: Browserified javascript and DFSG 2

2016-07-15 Thread Ian Jackson
Ian Jackson writes ("Re: Bug#830978: Browserified javascript and DFSG 2"): > I would like to comment briefly I'm sorry that I so evidently failed ! Ian.

Re: Bug#830978: Browserified javascript and DFSG 2

2016-07-15 Thread Ian Jackson
Sam Hartman writes ("Bug#830978: Browserified javascript and DFSG 2"): > Speaking as an individual TC member, here's my personal reading of the > TC discussion. > > It's not clear that the TC is the right body for this discussion. We > certainly could offer advice, but it's not clear that the

[release-tools] [PATCH] testing.pl is gone, update links to it to qa.d.o/excuses.php

2016-07-15 Thread Paul Wise
--- queue-viewer/overview.xslt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/queue-viewer/overview.xslt b/queue-viewer/overview.xslt index 0ec63f0..d79127c 100644 --- a/queue-viewer/overview.xslt +++ b/queue-viewer/overview.xslt @@ -201,7 +201,7 @@

Bug#830805: jessie-pu: package cacti/0.8.8b+dfsg-8+deb8u4

2016-07-15 Thread Paul Gevers
On 12-07-16 22:46, Adam D. Barratt wrote: > Please go ahead. Just uploaded to jessie-proposed-updates. Paul signature.asc Description: OpenPGP digital signature

Bug#830966: transition: gdal

2016-07-15 Thread Emilio Pozuelo Monfort
On 15/07/16 11:13, Sebastiaan Couwenberg wrote: > It looks like #831336 that is preventing the rebuild of vtk6 will cause > some delay in the testing migration of the packages involved in this > transition. > > This leaves testing users of the qmapshack package affected by the > critial issue

Re: Bug#830978: Browserified javascript and DFSG 2

2016-07-15 Thread Sam Hartman
Hi. Speaking as an individual TC member, here's my personal reading of the TC discussion. It's not clear that the TC is the right body for this discussion. We certainly could offer advice, but it's not clear that the ftpmasters or release team--the parties most likely to need such advice--

Bug#830966: transition: gdal

2016-07-15 Thread Sebastiaan Couwenberg
It looks like #831336 that is preventing the rebuild of vtk6 will cause some delay in the testing migration of the packages involved in this transition. This leaves testing users of the qmapshack package affected by the critial issue reported in #831297. It's been fixed with the new upstream