Re: Question concerning BTS, my own patch and upstream bugfix

On Mon, 16 Apr 2018 15:02:43 +0500 Andrey Rahmatullin <w...@debian.org> wrote: >On Mon, Apr 16, 2018 at 11:38:25AM +0200, Oliver Meißner wrote: >> How should I deal with this patch? >> >> * Leave it inside my current package (ver 3.5-2), close the bug via

Question concerning BTS, my own patch and upstream bugfix

Hi, just a short Question how to handle following situation properly I'm about to adopt the storebackup package and fixed bug #893812 by including a patch into the package. While waiting for a sponsor I got the information from the upstream author, that he'd fixed that bug in his next release,

Bug#895589: RFS: storebackup/3.5-2+nmu3 [ITA] -- fancy compressing managing checksumming deduplicating hard-linkin 'cp -ua'

>If you upload a newer version, you recycle >the old one and just change title. makes sense, thanks for the info. Olly

Bug#895730: RFS: storebackup/3.5-2 [ITA] -- fancy compressing managing checksumming deduplicating hard-linking cp -ua

Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "storebackup" * Package name: storebackup Version : 3.5-2 Upstream Author : Heinz-Josef Claes * URL : http://savannah.nongnu.org/projects/storebackup * License

Bug#895589: RFS: storebackup/3.5-2+nmu3 [ITA] -- fancy compressing managing checksumming deduplicating hard-linkin 'cp -ua'

at 16 Feb 2014 says, that the maintainer did not reply to any email. Best Regards, Oliver Meißner