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

[Andreas Tille]

Source: jardiff
Version: 0.2-5.1
Severity: important
X-Debbugs-Cc: Debian Java Maintainers <pkg-java-maintainers at lists.alioth.debian.org>, Damien Raude-Morvan <drazzib at debian.org>, debian-java at lists.debian.org, Package Salvaging Team <team+salvage at 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.

-- System Information:
Debian Release: trixie/sid
  APT prefers testing
  APT policy: (501, 'testing'), (50, 'buildd-unstable'), (50, 'unstable'), (5, 'experimental'), (1, 'buildd-experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 6.12.6-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE:de
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled