On Sat, Nov 15, 2014 at 05:51:06PM -0800, Cameron Norman wrote: > The bug in question is here: > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768671 > > jenkins build depends on libjson-java, a package that was removed due > to being suspected of containing non-free code (the JSON "For good, > not evil" stuff), however it turned out that libjson-java was never > actually affected by that > (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=721072). > > Still, the package (libjson-java) was removed from Jessie. > > How can this bug in Jenkins be resolved (keeping it in Jessie)? Only by dropping the dependency if it's possible. > Can packages like libjson-java in sid migrate to jessie after the > freeze in situations like this? According to https://release.debian.org/jessie/freeze_policy.html no. > Or does jenkins not have any chance to be in jessie? You can always ask the release team if they can make an exception to their rules. -- WBR, wRAR
Attachment:
signature.asc
Description: Digital signature