Bug 1402176 - pitivi-0.98 is available
Summary: pitivi-0.98 is available
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: pitivi
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Gwyn Ciesla
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-12-07 00:24 UTC by Upstream Release Monitoring
Modified: 2016-12-23 12:19 UTC (History)
4 users (show)

Fixed In Version: pitivi-0.98-2.fc25
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-12-23 12:19:52 UTC
Type: ---

Attachments (Terms of Use)
Rebase-helper rebase-helper-debug.log log file. See for details and report the eventual error to rebase-helper https://github.com/phracek/rebase-helper/issues. (6.90 KB, patch)
2016-12-07 00:25 UTC, Upstream Release Monitoring 		no flags Details | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Description Upstream Release Monitoring 2016-12-07 00:24:30 UTC 
Latest upstream release: 0.98
Current version/release in rawhide: 0.97.1-5.fc26
URL: http://download.gnome.org/sources/pitivi/

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.

Based on the information from anitya:  https://release-monitoring.org/project/3647/
Comment 1 Upstream Release Monitoring 2016-12-07 00:25:10 UTC 
Patching or scratch build for pitivi-0.97.1 failed.
Comment 2 Upstream Release Monitoring 2016-12-07 00:25:12 UTC 
Created attachment 1228758 [details]
Rebase-helper rebase-helper-debug.log log file.
See for details and report the eventual error to rebase-helper https://github.com/phracek/rebase-helper/issues.
Comment 3 Upstream Release Monitoring 2016-12-07 00:25:15 UTC 
Patches were not touched. All were applied properly
Comment 4 Gwyn Ciesla 2016-12-07 14:37:00 UTC 
Working on this but not all deps are available yet.
Comment 5 Upstream Release Monitoring 2016-12-12 15:36:28 UTC 
limb's pitivi-0.98-1.fc26 completed http://koji.fedoraproject.org/koji/buildinfo?buildID=824867
Comment 6 Upstream Release Monitoring 2016-12-13 08:47:26 UTC 
ignatenkobrain's pitivi-0.98-2.fc26 completed http://koji.fedoraproject.org/koji/buildinfo?buildID=825045
Comment 7 Fedora Update System 2016-12-14 16:26:52 UTC 
pitivi-0.98-2.fc25 has been submitted as an update to Fedora 25. https://bodhi.fedoraproject.org/updates/FEDORA-2016-a4ce94588e
Comment 8 Fedora Update System 2016-12-15 05:08:46 UTC 
pitivi-0.98-2.fc25 has been pushed to the Fedora 25 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-a4ce94588e
Comment 9 Upstream Release Monitoring 2016-12-20 14:06:19 UTC 
churchyard's pitivi-0.98-3.fc26 completed http://koji.fedoraproject.org/koji/buildinfo?buildID=826950
Comment 10 Upstream Release Monitoring 2016-12-20 16:06:18 UTC 
ignatenkobrain's pitivi-0.98-4.fc26 completed http://koji.fedoraproject.org/koji/buildinfo?buildID=828455
Comment 11 Upstream Release Monitoring 2016-12-22 14:31:52 UTC 
churchyard's pitivi-0.98-5.fc26 completed http://koji.fedoraproject.org/koji/buildinfo?buildID=828825
Comment 12 Fedora Update System 2016-12-23 12:19:52 UTC 
pitivi-0.98-2.fc25 has been pushed to the Fedora 25 stable repository. If problems still persist, please make note of it in this bug report.
Note You need to log in before you can comment on or make changes to this bug.