Bug 1480119

Summary:	linkchecker updated with new source location
Product:	[Fedora] Fedora	Reporter:	Brian (bex) Exelbierd <bexelbie>
Component:	linkchecker	Assignee:	W. Michael Petullo <redhat>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	27	CC:	bex, i, mike, redhat
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	linkchecker-9.3.1-1.fc26	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-08-16 00:39:29 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:
Embargoed:

Description Brian (bex) Exelbierd 2017-08-10 08:32:05 UTC

Description of problem:

linkchecker moved to a new GitHub organization sometime around Jan 2017

It is now found at: https://github.com/linkcheck/linkchecker

They have released a new version.

Can we get this packaged for 25, 26, and Rawhide?

Would you like me to prepare a spec file patch?

Comment 1 Jan Kurik 2017-08-15 07:50:55 UTC

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

Comment 2 W. Michael Petullo 2017-08-16 00:39:29 UTC

Updated 26, 27, and rawhide.

Comment 3 Brian Exelbierd 2017-08-18 08:28:55 UTC

When should this make it to testing so I can give it karma?

Comment 4 W. Michael Petullo 2017-08-20 17:44:50 UTC

See https://bodhi.fedoraproject.org/updates/FEDORA-2017-210bdf53a9.

Comment 5 Fedora Update System 2017-08-20 17:45:49 UTC

linkchecker-9.3.1-1.fc26 has been submitted as an update to Fedora 26. https://bodhi.fedoraproject.org/updates/FEDORA-2017-210bdf53a9

Comment 6 Fedora Update System 2017-08-28 16:19:02 UTC

linkchecker-9.3.1-1.fc26 has been pushed to the Fedora 26 stable repository. If problems still persist, please make note of it in this bug report.