Bug 1320568

Summary:	PyYAML upstream seems to be dead
Product:	[Fedora] Fedora	Reporter:	Matěj Cepl <mcepl>
Component:	PyYAML	Assignee:	John Eckersberg <jeckersb>
Status:	CLOSED NOTABUG	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	25	CC:	jeckersb, mcepl
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-08-29 21:46:28 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Matěj Cepl 2016-03-23 14:05:52 UTC

Description of problem:
The last commit to the official SVN repo was 5 years ago (http://pyyaml.org/browser, http://pyyaml.org/changeset/385/), the last ticket modified on 
http://pyyaml.org/query?status=assigned&status=closed&status=new&status=reopened&col=id&col=summary&col=status&col=owner&col=type&col=priority&col=component&col=changetime&desc=1&order=changetime

There is a message summarizing the situation
http://thread.gmane.org/gmane.text.yaml.general/3961

Owner of the project has the Bitbucket repo on https://bitbucket.org/xi/pyyaml/commits/all

Unrealted, bug 1204833 is still unresolved.

Version-Release number of selected component (if applicable):
PyYAML-3.11-12

Comment 1 Jan Kurik 2016-07-26 04:23:29 UTC

This bug appears to have been reported against 'rawhide' during the Fedora 25 development cycle.
Changing version to '25'.

Comment 2 John Eckersberg 2016-08-29 21:46:28 UTC

Upstream has released new version of PyYAML and libyaml on 2016-08-28, so for the moment upstream is still alive.