Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1463183 - vagrant-libvirt-0.0.40 is available
Summary: vagrant-libvirt-0.0.40 is available
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: vagrant-libvirt
Version: 25
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Vít Ondruch
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-06-20 10:54 UTC by Brian J. Murrell
Modified: 2017-06-28 20:51 UTC (History)
9 users (show)

Fixed In Version: vagrant-libvirt-0.0.35-4.fc25
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1446608
Environment:
Last Closed: 2017-06-28 20:51:49 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Brian J. Murrell 2017-06-20 10:54:21 UTC
+++ This bug was initially created as a clone of Bug #1446608 +++

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/

--- Additional comment from Upstream Release Monitoring on 2017-04-28 08:24:11 EDT ---

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

--- Additional comment from Upstream Release Monitoring on 2017-04-29 08:21:29 EDT ---

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/

--- Additional comment from Upstream Release Monitoring on 2017-04-29 08:21:34 EDT ---

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

--- Additional comment from Upstream Release Monitoring on 2017-04-29 20:22:55 EDT ---

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/

--- Additional comment from Upstream Release Monitoring on 2017-04-29 20:23:02 EDT ---

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

--- Additional comment from Brian J. Murrell on 2017-06-15 08:30:55 EDT ---

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?

--- Additional comment from Vít Ondruch on 2017-06-15 08:52:11 EDT ---

(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

--- Additional comment from Brian J. Murrell on 2017-06-15 09:00:11 EDT ---

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.

--- Additional comment from Brian J. Murrell on 2017-06-15 10:15:53 EDT ---

And https://github.com/vagrant-libvirt/vagrant-libvirt/commit/59edda86239b4b33d24f809177c4bc7e3036307a

--- Additional comment from Vít Ondruch on 2017-06-16 04:41:05 EDT ---

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.

--- Additional comment from Brian J. Murrell on 2017-06-16 07:24:54 EDT ---

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.

--- Additional comment from Upstream Release Monitoring on 2017-06-20 06:10:37 EDT ---

vondruch's vagrant-libvirt-0.0.40-1.fc27 completed http://koji.fedoraproject.org/koji/buildinfo?buildID=909809

--- Additional comment from Vít Ondruch on 2017-06-20 06:18:37 EDT ---

(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.


Requesting backport of this to Fedora 25

Comment 1 Fedora Update System 2017-06-20 13:58:04 UTC
vagrant-libvirt-0.0.35-4.fc25 has been submitted as an update to Fedora 25. https://bodhi.fedoraproject.org/updates/FEDORA-2017-eb854ff756

Comment 2 Fedora Update System 2017-06-21 04:28:40 UTC
vagrant-libvirt-0.0.35-4.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-2017-eb854ff756

Comment 3 Brian J. Murrell 2017-06-21 11:02:54 UTC
(In reply to Fedora Update System from comment #2)
> vagrant-libvirt-0.0.35-4.fc25 has been pushed to the Fedora 25 testing
> repository. If problems still persist, please make note of it in this bug
> report.

Unfortunately while this has included the shareable disk option, it didn't include the second patch I requested in bug #1446608 at https://bugzilla.redhat.com/show_bug.cgi?id=1446608#c9 for specifying a serial number for a disk.

Comment 4 Vít Ondruch 2017-06-21 16:13:14 UTC
It does, unless I missed something:

http://pkgs.fedoraproject.org/cgit/rpms/vagrant-libvirt.git/log/?h=f25

Comment 5 Brian J. Murrell 2017-06-21 16:30:28 UTC
Oh yes, you are correct.  I missed that it was done as two separate commits.  My apologies.

Comment 6 Fedora Update System 2017-06-28 20:51:49 UTC
vagrant-libvirt-0.0.35-4.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.