Bug#1017083: [pkg-crosswire-devel] Bug#1017083: Path forward

2022-08-27 Thread Teus Benschop
On Sat, 27 Aug 2022 at 20:55, Roberto C. Sánchez  wrote:

> I agree with your approach.  Including the source now to address the bug
> and ensure that package is not removed is something that should be done
> soon.  The introduction of the new package could also be pursued in
> parallel and once it is accepted into the archive, then bibledit could
> be updated to depend on the package and remove the duplicate components.
>
> Thank you for the support for this approach Roberto.
Upstream now has created a new tarball that includes the missing source
code.
This addresses the bug.
It took quite a while to be able to get things work out well, upstream, but
anyway, it's done now.
That tarball was used to create a new package for Debian.
Then the upload was done.
Likely things will be moving fast now, and hopefully this fixes the issue
completely.
Teus.


Bug#1017083: [pkg-crosswire-devel] Bug#1017083: Path forward

2022-08-27 Thread Roberto C . Sánchez
On Sat, Aug 27, 2022 at 07:48:11PM +0200, Teus Benschop wrote:
> The bug report states this:
> 
> > In order to solve this problem, you could:
> > 1. add the source files to "debian/missing-sources" directory.
> > 2. repack the origin tarball and add the missing source files to it.
> 
> The intention just now is to go for something similar to the proposed
> solution number 2.
> That means in this case that upstream will provide a new tarball that
> includes the missing source files.
> Then once this is done, a new Bibledit package can be created based on this
> tarball.
> 
> The intention is to do the above before the package will be
> automatically removed from the testing distro,
> and then let the new changelog close this bug in time.
> 
I agree with your approach.  Including the source now to address the bug
and ensure that package is not removed is something that should be done
soon.  The introduction of the new package could also be pursued in
parallel and once it is accepted into the archive, then bibledit could
be updated to depend on the package and remove the duplicate components.

Regards,

-Roberto

-- 
Roberto C. Sánchez