Bug 1299629 - Update to 2.0
Summary: Update to 2.0
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: python-hypothesis
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Michel Lind
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-01-18 19:40 UTC by Nathaniel McCallum
Modified: 2016-02-22 17:26 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-02-22 17:26:01 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Nathaniel McCallum 2016-01-18 19:40:27 UTC
Spec file provided here:

https://npmccallum.fedorapeople.org/python-hypothesis.spec

First, I updated to 2.0.

Second, I enabled build on EL7.

Third, upstream tests have been removed and will not come back. I have thus removed any attempt to run them as well as the build dependencies that were formerly used for tests.

Finally, I have requested comaintainership for the package. If you approve it, I can do the work myself.

Comment 1 Michel Lind 2016-02-22 17:26:01 UTC
(In reply to Nathaniel McCallum from comment #0)
> Spec file provided here:
> 
> https://npmccallum.fedorapeople.org/python-hypothesis.spec
> 
> First, I updated to 2.0.
> 
> Second, I enabled build on EL7.
> 
> Third, upstream tests have been removed and will not come back. I have thus
> removed any attempt to run them as well as the build dependencies that were
> formerly used for tests.
> 
> Finally, I have requested comaintainership for the package. If you approve
> it, I can do the work myself.

Ah, I've updated the Rawhide build, but feel free to merge your changes (I prefer having the different branches being as closely related to each other, so that cherry-picking between them works at the very least, and ideally merging from master should just result in a fast-forward).

Approved your pending requests. Welcome!


Note You need to log in before you can comment on or make changes to this bug.