Package: jgit-cli Version: 3.7.1-4 Tags: upstream patch fixed-upstream Severity: important Justification: renders feature unusable
Steps to reproduce: git clone https://kernel.googlesource.com/pub/scm/git/git cd git make -j8 cd t ./t5512-ls-remote.sh -v -i Expected result: test passes Actual result: java.lang.IllegalStateException: Cannot set value to a final field 'org.eclipse.jgit.pgm.Daemon.enable'. at org.kohsuke.args4j.spi.Setters.create(Setters.java:32) at org.kohsuke.args4j.ClassParser.parse(ClassParser.java:34) at org.kohsuke.args4j.CmdLineParser.<init>(CmdLineParser.java:96) at org.kohsuke.args4j.CmdLineParser.<init>(CmdLineParser.java:71) at org.eclipse.jgit.pgm.opt.CmdLineParser.<init>(CmdLineParser.java:119) at org.eclipse.jgit.pgm.opt.CmdLineParser.<init>(CmdLineParser.java:102) at org.eclipse.jgit.pgm.TextBuiltin.parseArguments(TextBuiltin.java:224) at org.eclipse.jgit.pgm.TextBuiltin.execute(TextBuiltin.java:208) at org.eclipse.jgit.pgm.Main.execute(Main.java:223) at org.eclipse.jgit.pgm.Main.run(Main.java:124) at org.eclipse.jgit.pgm.Main.main(Main.java:98) Fixed upstream by v4.9.0.201710071750-r~33 (Remove final modifier on args4j option or argument fields, 2017-09-04, https://git.eclipse.org/r/104304). I suspect this was triggered by an args4j update. Once jgit is updated, can args4j get a Breaks to force upgrades? Thanks, Jonathan