Re: Status of libewf, transition to handle

[Aleksey Kravchenko <rhash.admin@gmail.com>]

Hello Raphael,

The work in libewf salsa repository was interrupted by upstream maintainer Joachim Metz.
He was against publishing libewf-experimental-20171104 [1] into debian unstable and insisted on using legacy version libewf-20140807 [2].

Salsa watch file points to the wrong repository, the version 20140807 is last stable version, and the version 20171104 from experimental should not migrate.

I and Hilko did not had time to correct wrong and half-done salsa git history. I believe we should

1. Rename current debian/master branch to debian/master-old (or something)

2. Start new debian/master from the commit it diverged with published version and use gbp import-orig/import-dsc

3. Do the same for the debian/expiremental branch

Some time ago I've partly done this work in [3], but now I'm overloaded with another project.

[1] https://github.com/libyal/libewf/releases

[2] https://github.com/libyal/libewf-legacy/releases

[3] https://salsa.debian.org/alexk-guest/libewf

On Thu, Nov 28, 2019 at 8:54 PM Raphael Hertzog <hertzog@debian.org> wrote:

Hello,

I wanted to upload all the packages that still have a bad maintainer
field (old list) and libewf is among them. But there's a new upstream
version available in experimental.

That version was prepared in debian/experimental (note that the tag has not
been pushed) but in parallel I see other diverging commits by Aleksey Kravchenko
in debian/master.

Can one of you merge both branches and handle the library transition
in unstable in coordination with the release managers ?

Cheers,
--
Raphaël Hertzog ◈ Debian Developer

Support Debian LTS: https://www.freexian.com/services/debian-lts.html
Learn to master Debian: https://debian-handbook.info/get/