Bug 1285587 - vym-2.5.0-2.7 is available
vym-2.5.0-2.7 is available
Status: CLOSED NOTABUG
Product: Fedora
Classification: Fedora
Component: vym (Show other bugs)
rawhide
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Gwyn Ciesla
Fedora Extras Quality Assurance
: FutureFeature, Triaged
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2015-11-25 19:31 EST by Upstream Release Monitoring
Modified: 2015-11-29 12:37 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2015-11-29 12:37:46 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Upstream Release Monitoring 2015-11-25 19:31:52 EST
Latest upstream release: 2.5.0-2.7
Current version/release in rawhide: 2.5.0-1.fc24
URL: http://download.opensuse.org/repositories/home://insilmaril/openSUSE_Factory/src/

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-11-25 19:32:13 EST
Failed to kick off scratch build.

spectool was unable to grab new sources

old source: vym-2.5.0.tar.bz2
old sha256: 55550549fcc8cc151ff6235a09bb8fc1412f0b598cc6f9072345058c5e12b9f3

new source: ./vym-2.5.0.tar.bz2
new sha256: 55550549fcc8cc151ff6235a09bb8fc1412f0b598cc6f9072345058c5e12b9f3

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