Bug 1248841

Summary:	python-phyghtmap-1.73.orig is available
Product:	[Fedora] Fedora	Reporter:	Upstream Release Monitoring <upstream-release-monitoring>
Component:	python-phyghtmap	Assignee:	Volker Fröhlich <volker27>
Status:	CLOSED NEXTRELEASE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	rawhide	CC:	volker27
Target Milestone:	---	Keywords:	FutureFeature, Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	1.73-1.fc21	Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-08-18 05:24:14 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Upstream Release Monitoring 2015-07-31 00:14:20 UTC

Latest upstream release: 1.73.orig
Current version/release in rawhide: 1.72-1.fc24
URL: http://katze.tfiu.de/projects/phyghtmap/

Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy

More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring

Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream.

Comment 1 Upstream Release Monitoring 2015-07-31 00:14:33 UTC

Failed to kick off scratch build.

cmd:  spectool -g /var/tmp/thn-ZmIuRG/python-phyghtmap.spec
return code:  22
stdout:
Getting http://katze.tfiu.de/projects/phyghtmap/phyghtmap_1.73.orig.orig.tar.gz to ./phyghtmap_1.73.orig.orig.tar.gz

stderr:
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed

  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
curl: (22) The requested URL returned error: 404 Not Found

Comment 2 Fedora Update System 2015-08-10 21:37:36 UTC

python-phyghtmap-1.73-1.fc23 has been submitted as an update for Fedora 23.
https://admin.fedoraproject.org/updates/python-phyghtmap-1.73-1.fc23

Comment 3 Fedora Update System 2015-08-10 21:38:47 UTC

python-phyghtmap-1.73-1.fc22 has been submitted as an update for Fedora 22.
https://admin.fedoraproject.org/updates/python-phyghtmap-1.73-1.fc22

Comment 4 Fedora Update System 2015-08-10 21:39:57 UTC

python-phyghtmap-1.73-1.fc21 has been submitted as an update for Fedora 21.
https://admin.fedoraproject.org/updates/python-phyghtmap-1.73-1.fc21

Comment 5 Fedora Update System 2015-08-12 07:00:30 UTC

Package python-phyghtmap-1.73-1.fc21:
* should fix your issue,
* was pushed to the Fedora 21 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing python-phyghtmap-1.73-1.fc21'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2015-13213/python-phyghtmap-1.73-1.fc21
then log in and leave karma (feedback).

Comment 6 Fedora Update System 2015-08-18 05:24:14 UTC

python-phyghtmap-1.73-1.fc23 has been pushed to the Fedora 23 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 7 Fedora Update System 2015-08-22 22:50:15 UTC

python-phyghtmap-1.73-1.fc22 has been pushed to the Fedora 22 stable repository. If problems still persist, please make note of it in this bug report.

Comment 8 Fedora Update System 2015-08-23 00:48:22 UTC

python-phyghtmap-1.73-1.fc21 has been pushed to the Fedora 21 stable repository. If problems still persist, please make note of it in this bug report.