Your message dated Sat, 14 Dec 2024 23:04:45 +0000
with message-id <e1tmbbl-00a351...@fasolo.debian.org>
and subject line Bug#788724: fixed in jenkins-json 2.4-jenkins-8+dfsg-1
has caused the Debian Bug report #788724,
regarding [src:jenkins-json] Some sources are not included in your package
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 ow...@bugs.debian.org
immediately.)


-- 
788724: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=788724
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:jenkins-json 
Version: 2.4-jenkins-3-3
user: lintian-ma...@debian.org
usertags: source-is-missing
severity: serious
X-Debbugs-CC: ftpmas...@debian.org

Hi,

Your package includes some files that seem to lack sources
in prefered forms of modification:

    src/site/resources/scripts/shCore.js

According to Debian Free Software Guidelines [1] (DFSG) #2:
 "The program must include source code, and must allow distribution 
  in source code as well as compiled form."

In some cases this could also constitute a license violation for some
copyleft licenses such as the GNU GPL. (While sometimes the licence
allows not to ship the source, the DFSG always mandates source code.)

In order to solve this problem, you could:
1.  add the source files to "debian/missing-sources" directory.
2. repack the origin tarball and add the missing source files to it.

Both way satisfy the requirement to ship all source code. The second option
might be preferable due to the following reasons [2]:
 - Upstream can do it too and you could even supply a patch to them, thus
   full filling our social contract [3], see particularly ยง2.
 - If source and non-source are in different locations, ftpmasters may
   miss the source and (needlessly) reject the package.
 - The source isn't duplicated in every .diff.gz/.debian.tar.* (though
   this only really matters for larger sources).

You could also ask debian...@lists.debian.org or #debian-qa for more
guidance.

[1] https://www.debian.org/social_contract.en.html#guidelines
[2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=736873#8
[3] https://www.debian.org/social_contract

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


--- End Message ---
--- Begin Message ---
Source: jenkins-json
Source-Version: 2.4-jenkins-8+dfsg-1
Done: Pierre Gruet <p...@debian.org>

We believe that the bug you reported is fixed in the latest version of
jenkins-json, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 788...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Pierre Gruet <p...@debian.org> (supplier of updated jenkins-json package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Sat, 14 Dec 2024 23:50:42 +0100
Source: jenkins-json
Architecture: source
Version: 2.4-jenkins-8+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 
<pkg-java-maintain...@lists.alioth.debian.org>
Changed-By: Pierre Gruet <p...@debian.org>
Closes: 788724 801004 1047096
Changes:
 jenkins-json (2.4-jenkins-8+dfsg-1) unstable; urgency=medium
 .
   * Team upload
   * New upstream version 2.4-jenkins-8+dfsg:
     - Checking that source package can now be built twice in a row
       (Closes: #1047096)
   * Refreshing patches
   * Repacking without obfuscated js file (Closes: #788724)
   * Refreshing d/copyright
   * Raising Standards version to 4.7.0
     - Setting Rules-Requires-Root: no
     - Using the https format for d/copyright
   * Handling the junit artifact correctly by providing its version number
   * Removing B-D on libcommons-httpclient-java (Closes: #801004)
   * Removing unneeded versioned B-D
   * Updating Maven ignoreRules
   * Marking the POM file with --no-parent
   * Simplifying d/rules
Checksums-Sha1:
 a44d847215779bf0d0a79364ec4fd601297f8fc8 2307 
jenkins-json_2.4-jenkins-8+dfsg-1.dsc
 4f0f0c1e950ee31e3a7b1a6402141e4a081d9d35 209876 
jenkins-json_2.4-jenkins-8+dfsg.orig.tar.xz
 83dde5ff70282fe4986004c24dd6831eabaa90b4 4840 
jenkins-json_2.4-jenkins-8+dfsg-1.debian.tar.xz
 66ba5c4e2b971255d442523f653d3adbecaaaf43 17973 
jenkins-json_2.4-jenkins-8+dfsg-1_source.buildinfo
Checksums-Sha256:
 5df213800d6c5366110f8d721830b302453fdd7f72efdbfd7c2b3657786ac99d 2307 
jenkins-json_2.4-jenkins-8+dfsg-1.dsc
 be26d054e88b606005ef71567881433bc17330b30f50926349c0a4fc7f711e8e 209876 
jenkins-json_2.4-jenkins-8+dfsg.orig.tar.xz
 fd0d3ff53f7a8a52810cea33e40ac432062280afa63ba2ca2af90c4a5f8d2a25 4840 
jenkins-json_2.4-jenkins-8+dfsg-1.debian.tar.xz
 8f017d1c86ecf225a4bd6a5a26d71428e6ad1b27c19f5da8569a8763efb97ac5 17973 
jenkins-json_2.4-jenkins-8+dfsg-1_source.buildinfo
Files:
 dbc9b24962f8e6fa42559cfc6607e2e9 2307 java optional 
jenkins-json_2.4-jenkins-8+dfsg-1.dsc
 9eee7f9a8597f03cd822ebe5b7d03cee 209876 java optional 
jenkins-json_2.4-jenkins-8+dfsg.orig.tar.xz
 de4ade460d22b389604cc27c9827308e 4840 java optional 
jenkins-json_2.4-jenkins-8+dfsg-1.debian.tar.xz
 29e79b033238196b065f69681bf17f3e 17973 java optional 
jenkins-json_2.4-jenkins-8+dfsg-1_source.buildinfo

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEM8soQxPpC9J9y0UjYAMWptwndHYFAmdeDBUACgkQYAMWptwn
dHZORQ/+Pxk7KUarf+jZrNuCajbzwnksCm8ITgBd6FUCM4Uh1zS/z82t6ZJJn7UX
J+PbOyfDy7TJ2RmvcsJK1rJgQRg44hgVabLvxaTSjqEJ+Lez/xTyQzydV+2ZNjqf
wgy++8oatG7vXD5WfF+pi+PRkTUAOv7+6QCjfdBk1ldhJtuipK/EmyQJn5F18aKQ
4zJOLcZFvl01Nkt9UE/DDy2ZVBXkwWPwYQIQRiE/hPqHtQTThlhd80kJFV43CfXu
hmdVH9+cnedvIAk3J8wzyswhJ6LTCze4JG1I1Mog+2OIuIt2gBSaMzJ5jqNODfYJ
gCDCiLS9NF+h0mjge3CmhZHA9+geig2C7DxmLuYlKp7q+qHRxVmrkdDdMTHm71LB
UkpZpHBQ5CwccoT5aAHWYqJeQBGdTQ8B+tUZKgYhZr6arvxt80Po2EJfgGjU7YDS
PwDyJl1HAaYaqudj3dWMoASK5lhGOQKN4U0UOzIF9+BGMoToetXJ9PrRQKraacGl
UgztLiPqCD/xKCla8RAzxHyqMfqiYGo+BWt8YpTwE8HV/jEza1qvKaKklALK0xxQ
rQVgFy6y6BGyQ5iCPDjLkQtiWX0aSQLeLKV9mXMiFNmsc1QC6bt9Ark1iIHnIZDW
pYO7nZ0xprDg3YyKB7spc8KJraGc+urnaUhObFX3axUMX/07Xsw=
=8Bhw
-----END PGP SIGNATURE-----

Attachment: pgpeeNWgwODKH.pgp
Description: PGP signature


--- End Message ---

Reply via email to