#1093830 jardiff: Should we replace jardiff with some project of the same name but maintained

#1093830#5
Date:
2025-01-23 07:54:45 UTC
From:
To:
Hi,

I'm currently checking packages in Debian Java team featuring

  1. Invalid Vcs fields
  2. cdbs

to fix the Vcs fields and replace cdbs by dh.  I'm also verifying
Homepage and watch file, etc.  I learned that the Homepage associated
with the current jardiff package vanished from the internet.  When
seeking for a new location I've found

https://github.com/lightbend-labs/jardiff

which is actively maintained.  I wonder whether we should go the "remove
old jardiff + introduce new jardiff via new" route or whether it is OK
to just inject the new project and add the change in NEWS.Debian.

I have no strong opinion here since I do not use this package.  So any
input is welcome.  I would volunteer to implement what might be
consensus of the discussion.

Kind regards
   Andreas.

#1093830#10
Date:
2025-02-02 13:32:07 UTC
From:
To:
Hi Andreas,

On Thu, 23 Jan 2025 08:54:45 +0100 Andreas Tille <tille@debian.org> wrote:
 > Source: jardiff
 > Version: 0.2-5.1
 > Severity: important
 > X-Debbugs-Cc: Debian Java Maintainers
<pkg-java-maintainers@lists.alioth.debian.org>, Damien Raude-Morvan
<drazzib@debian.org>, debian-java@lists.debian.org, Package Salvaging
Team <team+salvage@tracker.debian.org>
 >
 > Hi,
 >
 > I'm currently checking packages in Debian Java team featuring
 >
 > 1. Invalid Vcs fields
 > 2. cdbs
 >
 > to fix the Vcs fields and replace cdbs by dh. I'm also verifying
 > Homepage and watch file, etc. I learned that the Homepage associated
 > with the current jardiff package vanished from the internet. When
 > seeking for a new location I've found
 >
 > https://github.com/lightbend-labs/jardiff
 >
 > which is actively maintained. I wonder whether we should go the "remove
 > old jardiff + introduce new jardiff via new" route or whether it is OK
 > to just inject the new project and add the change in NEWS.Debian.
 >
 > I have no strong opinion here since I do not use this package. So any
 > input is welcome. I would volunteer to implement what might be
 > consensus of the discussion.
 >
 > Kind regards
 > Andreas.
 >

Thanks for drawing our attention on this!

I just uploaded jardiff to unstable (without changing the upstream
version), which fixes the Vcs fields + the cdbs matter.

However, I examined the new location you found, it seems to be
interesting but it includes some files in Scala, and requires Scala
Built Tool (sbt), which has been removed from experimental. Let's stay
with the current upstream version, and maybe reconsider the upgrade if
sbt enters Debian again one day :)

All the best,