Bug 1303379 - lastpass-cli-0.9.0 is available
Summary: lastpass-cli-0.9.0 is available
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: lastpass-cli
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Tom Prince
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-01-31 12:24 UTC by Upstream Release Monitoring
Modified: 2016-04-10 14:22 UTC (History)
1 user (show)

Fixed In Version: lastpass-cli-0.9.0-1.fc23
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-04-10 14:22:38 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
[patch] Update to 0.8.1 (#1303379) (1006 bytes, patch)
2016-01-31 12:24 UTC, Upstream Release Monitoring
no flags Details | Diff
[patch] Update to 0.9.0 (#1303379) (1.09 KB, patch)
2016-03-03 00:15 UTC, Upstream Release Monitoring
no flags Details | Diff

Description Upstream Release Monitoring 2016-01-31 12:24:16 UTC
Latest upstream release: 0.8.1
Current version/release in rawhide: 0.8.0-1.fc24
URL: https://github.com/LastPass/lastpass-cli

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 2016-01-31 12:24:25 UTC
Created attachment 1119835 [details]
[patch] Update to 0.8.1 (#1303379)

Comment 2 Upstream Release Monitoring 2016-01-31 12:49:53 UTC
Scratch build completed http://koji.fedoraproject.org/koji/taskinfo?taskID=12757069

Comment 3 Upstream Release Monitoring 2016-03-03 00:15:47 UTC
Latest upstream release: 0.9.0
Current version/release in rawhide: 0.8.0-2.fc24
URL: https://github.com/LastPass/lastpass-cli

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 4 Upstream Release Monitoring 2016-03-03 00:15:54 UTC
Created attachment 1132585 [details]
[patch] Update to 0.9.0 (#1303379)

Comment 5 Upstream Release Monitoring 2016-03-03 00:26:52 UTC
Scratch build completed http://koji.fedoraproject.org/koji/taskinfo?taskID=13207341

Comment 6 Upstream Release Monitoring 2016-03-07 05:36:25 UTC
tomprince's lastpass-cli-0.9.0-1.fc25 completed http://koji.fedoraproject.org/koji/buildinfo?buildID=742360

Comment 7 Fedora Update System 2016-04-04 00:13:26 UTC
lastpass-cli-0.9.0-1.fc23 has been submitted as an update to Fedora 23. https://bodhi.fedoraproject.org/updates/FEDORA-2016-05a6152fc0

Comment 8 Fedora Update System 2016-04-05 15:54:09 UTC
lastpass-cli-0.9.0-1.fc23 has been pushed to the Fedora 23 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-05a6152fc0

Comment 9 Fedora Update System 2016-04-10 14:22:36 UTC
lastpass-cli-0.9.0-1.fc23 has been pushed to the Fedora 23 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.