Your message dated Sat, 08 Oct 2016 22:45:08 +0200
with message-id <[email protected]>
and subject line "Browserified" stuff
has caused the Debian Bug report #839801,
regarding Browserified javascript and DFSG source
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 [email protected]
immediately.)


-- 
839801: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=839801
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
package: ftp.debian.org

Hi ftp masters,

A bug was filed against libjs-handlebars (#817092) with severity serious for 
missing source code.

I approached TC about this issue as I did not agree to this interpretation 
(#830978). But they asked me to talk to you.

I reopened that bug here #839570.

So I request ftp masters,

1. To make an official ruling on this issue.
2. If this is considered RC, give an exception to stretch release so there is 
enough time to package grunt and fix this properly. I believe moving these 
packages to contrib/non-free is not an ideal solution as many users will have 
to enable these sections to install packages like diaspora, gitlab, pagure, 
prometheus etc.

--- End Message ---
--- Begin Message ---
severity 817092 serious
thanks

Hi

we had a discussion inside the FTP Team about the "browserified js"
issue. We understand that "browserified" refers to various changes to
the original source, from concatenating multiple (local and remotely
fetched) files together, arbitary transformations (down to something
akin to compilation), minifying and others. Not all "browserification"
may necessarily use all of those ways.


- "Browserified", even if it may end up editable by others, is not the
  preferred form of modification as upstream uses, as such it is not
  source.

- "Browserified" files can be shipped in Debian unmodified, same as (for
  example) PDF files from upstream can. But it is the maintainers
  obligation to ensure that they are rebuildable within Debian, so their
  original source must be provided within the source package or be
  reachable via build-dependencies (in case of concatenations). If this
  can not be done (source or tools missing), they either have to be
  removed or the package must move to either contrib or non-free.

- We acknowledge that it appears to be a big task to provide a proper
  "browserification" environment within Debian. Due to the freeze coming
  up we would understand the Release Team granting an RC exception for
  stretch for such non-sources already in main, with the condition that
  this will not extend to another release.

-- 
bye, Joerg (the ftpmaster behind the curtain)

Attachment: signature.asc
Description: PGP signature


--- End Message ---

Reply via email to