How to "backport" a fix?

How to "backport" a fix?

[Hartmut Goebel]

Hi,

thanks to Marius Bakke's tip django test run fine now -- except of two.
These are errors in the test-case which have been fixed just after the
release.

What is the proper way to handle this? Include this fix as a patch? As a
snippet to the source? Or should I disable the two tests?

-- 
Regards
Hartmut Goebel

| Hartmut Goebel          | h.goebel@crazy-compilers.com               |
| www.crazy-compilers.com | compilers which you thought are impossible |

Re: How to "backport" a fix?

[Leo Famulari]

On Thu, Aug 18, 2016 at 05:24:30PM +0200, Hartmut Goebel wrote:
> Hi,
> 
> thanks to Marius Bakke's tip django test run fine now -- except of two.
> These are errors in the test-case which have been fixed just after the
> release.
> 
> What is the proper way to handle this? Include this fix as a patch? As a
> snippet to the source? Or should I disable the two tests?

If there are upstream patches that fix broken tests, then I think we
should try taking those patches from upstream and applying them in the
(source) field of the package.

The patch files we use should include a brief comment explaining what
they do (the upstream commit message might suffice) and a link to their
source.