Bug 1446608 - vagrant-libvirt-0.0.40 is available
Summary: vagrant-libvirt-0.0.40 is available
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: vagrant-libvirt
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Vít Ondruch
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-04-28 12:24 UTC by Upstream Release Monitoring
Modified: 2017-06-20 10:56 UTC (History)
7 users (show)

Fixed In Version: vagrant-libvirt-0.0.40-1.fc27
Doc Type: Enhancement
Doc Text:
Clone Of:
: 1463183 1463184 (view as bug list)
Environment:
Last Closed: 2017-06-20 10:18:37 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Upstream Release Monitoring 2017-04-28 12:24:02 UTC
Latest upstream release: 0.0.38
Current version/release in rawhide: 0.0.37-4.fc26
URL: https://github.com/vagrant-libvirt/vagrant-libvirt

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/5783/

Comment 1 Upstream Release Monitoring 2017-04-28 12:24:11 UTC
An unexpected error occured creating the scratch build: please report this issue to the-new-hotness issue tracker at https://github.com/fedora-infra/the-new-hotness/issues

Comment 2 Upstream Release Monitoring 2017-04-29 12:21:29 UTC
Latest upstream release: 0.0.39
Current version/release in rawhide: 0.0.37-4.fc26
URL: https://github.com/vagrant-libvirt/vagrant-libvirt

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/5783/

Comment 3 Upstream Release Monitoring 2017-04-29 12:21:34 UTC
An unexpected error occured creating the scratch build: please report this issue to the-new-hotness issue tracker at https://github.com/fedora-infra/the-new-hotness/issues

Comment 4 Upstream Release Monitoring 2017-04-30 00:22:55 UTC
Latest upstream release: 0.0.40
Current version/release in rawhide: 0.0.37-4.fc26
URL: https://github.com/vagrant-libvirt/vagrant-libvirt

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/5783/

Comment 5 Upstream Release Monitoring 2017-04-30 00:23:02 UTC
An unexpected error occured creating the scratch build: please report this issue to the-new-hotness issue tracker at https://github.com/fedora-infra/the-new-hotness/issues

Comment 6 Brian J. Murrell 2017-06-15 12:30:55 UTC
Does anything happen with these "Upstream Release Monitoring" tickets?

As this ticket says, 0.0.40 of vagrant-libvirt is out.  Can we get updated packages for Fedora 25?

Comment 7 Vít Ondruch 2017-06-15 12:52:11 UTC
(In reply to Brian J. Murrell from comment #6)
> Does anything happen with these "Upstream Release Monitoring" tickets?

Of course they are resolved from time to time

> As this ticket says, 0.0.40 of vagrant-libvirt is out.  Can we get updated
> packages for Fedora 25?

I don't typically update stable versions, unless there is specific reason. So could you please elaborate why F25 should be updated? Thx

Comment 8 Brian J. Murrell 2017-06-15 13:00:11 UTC
Because 0.0.40 has additional useful features such as:

https://github.com/vagrant-libvirt/vagrant-libvirt/commit/d78d8969098bbe466d8381a90914a799bb563485

Undoubtedly it has bug fixes in it also.

Comment 10 Vít Ondruch 2017-06-16 08:41:05 UTC
Thx for elaborating. The former was already part of 0.0.36 while the later is not released yet I am afraid. But I'll consider the update.

Comment 11 Brian J. Murrell 2017-06-16 11:24:54 UTC
Alternatively, both patches backport rather easily.  I can attach the backported patches here if you like, since I have already rolled my own 0.0.35 + those two patches and those two features are working just fine.

Comment 12 Upstream Release Monitoring 2017-06-20 10:10:37 UTC
vondruch's vagrant-libvirt-0.0.40-1.fc27 completed http://koji.fedoraproject.org/koji/buildinfo?buildID=909809

Comment 13 Vít Ondruch 2017-06-20 10:18:37 UTC
(In reply to Brian J. Murrell from comment #11)
> Alternatively, both patches backport rather easily.  I can attach the
> backported patches here if you like, since I have already rolled my own
> 0.0.35 + those two patches and those two features are working just fine.

I rebased vagrant-libvirt in Rawhide, therefore I'm going to close this ticket now. It would be nice if you could open separate ticket for the backports you are referencing above. Thx.

Comment 14 Brian J. Murrell 2017-06-20 10:56:58 UTC
Thanks for the update!


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