Skip to content
Snippets Groups Projects

Upgrade to new upstream release 0.16.0

Closed Julian Rüth requested to merge saraedum-guest/python-future:master into master
3 unresolved threads

To create these changes, I did:

# download orig.tar.gz
git-dpm import-new-upstream --rebase ../python-future_0.16.0.orig.tar.gz
# fix conflicts
git-dpm update-patches
pristine-tar commit ../python-future_0.16.0.orig.tar.gz upstream
git-dpm dch -- -v 0.16.0-1 "new upstream version 0.16.0"

So there are also corresponding upstream and pristine-tar branches in my fork of this repository.

Note that this resolves https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863215.

I ran the tests and did not see any failures: https://salsa.debian.org/saraedum-guest/python-future/-/jobs/14758

I am new to debian/python-future, so I am very happy to get any feedback :)

Edited by Julian Rüth

Merge request reports

Loading
Loading

Activity

Filter activity
  • Approvals
  • Assignees & reviewers
  • Comments (from bots)
  • Comments (from users)
  • Commits & branches
  • Edits
  • Labels
  • Lock status
  • Mentions
  • Merge request status
  • Tracking
13 --- a/tests/test_future/test_bytes.py
14 +++ b/tests/test_future/test_bytes.py
15 @@ -7,6 +7,8 @@ from __future__ import absolute_import, unicode_literals, print_function
16 from future.builtins import *
17 from future import utils
18
19 +import sys
20 +
21 from numbers import Integral
22 from future.tests.base import unittest, expectedFailurePY2
23
24 @@ -552,103 +554,105 @@ class TestBytes(unittest.TestCase):
25 self.assertRaises(ValueError, bytes.maketrans, b'abc', b'xyzq')
26 self.assertRaises(TypeError, bytes.maketrans, 'abc', 'def')
27
28 - # def test_mod(self):
  • Julian Rüth changed the description

    changed the description

  • @onovy hello, I don't know if you gets merge requests emails... can you please have a look?

    thanks for the upload!

  • hi, i just fixed RC bug and one other, i'm not maintainer of this package, you know? :)

    BTW: This MR is not mergeable now, because we are using gbp and not git-dpm now and there is git conflict.

  • oops, true! @barry or @bernat might want to update it then :)

  • It looks like both 0.16.0 and 0.18.2 have been imported since independently of this merge request, so I think this can be closed as obsolete. Sorry that we didn't merge this merge request earlier.

  • Please register or sign in to reply
    Loading