[Debian-med-packaging] Bug#831833: Bug#831833: Tagged as fixed-upstream - do you intend to upload?

[Charles Plessy]

> On Wed, Nov 02, 2016 at 09:03:45PM +0900, Charles Plessy wrote:
> > 
> > I was hoping that Upstream would make a new release with the fix :(
> > 
> > So one would need to check if the following commit would be enough as a patch...
> > 
> > https://github.com/arq5x/bedtools2/commit/be2633d4951328264611e4cabc65e12fa8fef1cd

Hi again,

it turns out that the patch representing the commit be2633d fixing the issue
can not be applied alone; the package fails to build.

Then, I tried to look for other commits to apply in order to make the patched
package buildable, and I realised that first, there has been only 16 commits in
total since the last upstream release, and second, some of these commits do fix
other bugs, less severe, but real bugs.  None of them introduce novel
unreleased features.

So I am tempted to propose to distribute the current contents of Upstream's
master branch in Squeeze.  Technically, I can:

 - Just drop a big monolithic patch in debian/patches, or
 - drop the patches produced by `git format-patch v2.26.0, or
 - make a new tarball, version 2.26.0-19-g6bf23c4 (`git describe --tags`).

What do other people think about this ?

Have a nice day,

Charles

-- 
Charles Plessy
Debian Med packaging team,
http://www.debian.org/devel/debian-med
Tsurumi, Kanagawa, Japan