Latest upstream release: 0.8.0 Current version/release in rawhide: 0.7.0-3.fc37 URL: https://github.com/vagrant-libvirt/vagrant-libvirt Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/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/
Created attachment 1872339 [details] Update to 0.8.0 (#2075223)
the-new-hotness/release-monitoring.org's scratch build of vagrant-libvirt-0.8.0-1.fc34.src.rpm for rawhide failed http://koji.fedoraproject.org/koji/taskinfo?taskID=85632545
Latest upstream release: 0.8.1 Current version/release in rawhide: 0.7.0-3.fc37 URL: https://github.com/vagrant-libvirt/vagrant-libvirt Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/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/
Created attachment 1874210 [details] Update to 0.8.1 (#2075223)
the-new-hotness/release-monitoring.org's scratch build of vagrant-libvirt-0.8.1-1.fc34.src.rpm for rawhide failed http://koji.fedoraproject.org/koji/taskinfo?taskID=86037912
Latest upstream release: 0.8.2 Current version/release in rawhide: 0.7.0-3.fc37 URL: https://github.com/vagrant-libvirt/vagrant-libvirt Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/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/
Scratch build failed. Details below: GenericError: File upload failed: cli-build/1651710873.4816456.rVPlXnDT/vagrant-libvirt-0.8.2-1.fc34.src.rpm Traceback: File "/usr/local/lib/python3.9/site-packages/hotness/use_cases/package_scratch_build_use_case.py", line 56, in build result = self.builder.build(request.package, request.opts) File "/usr/local/lib/python3.9/site-packages/hotness/builders/koji.py", line 198, in build output["build_id"] = self._scratch_build(session, package.name, srpm) File "/usr/local/lib/python3.9/site-packages/hotness/builders/koji.py", line 451, in _scratch_build session.uploadWrapper(source, serverdir) File "/usr/lib/python3.9/site-packages/koji/__init__.py", line 3053, in uploadWrapper self.fastUpload(localfile, path, name, callback, blocksize, overwrite, volume=volume) File "/usr/lib/python3.9/site-packages/koji/__init__.py", line 2988, in fastUpload raise GenericError("File upload failed: %s/%s" % (path, name)) If you think this issue is caused by some bug in the-new-hotness, please report it on the-new-hotness issue tracker: https://github.com/fedora-infra/the-new-hotness/issues
@vondruch can we get the new version packaged, the existing package breaks kdevops.
Releases retrieved: 0.9.0 Upstream release that is considered latest: 0.9.0 Current version/release in rawhide: 0.7.0-3.fc37 URL: https://github.com/vagrant-libvirt/vagrant-libvirt Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/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/ To change the monitoring settings for the project, please visit: https://src.fedoraproject.org/rpms/vagrant-libvirt
Tried manually build 0.9.0 from F36 specfile. * 0.7.0 was release 2021-11-08. * F36 spec includes patch for https://github.com/vagrant-libvirt/vagrant-libvirt/pull/1416 * PR 1416 was merged on Dec 3, 2021. * F36 spec includes patch for https://github.com/vagrant-libvirt/vagrant-libvirt/pull/1424 * PR 1424 was merged on Dec 11, 2021. * According to 0.8.0 changelog, pr 1416 and 1424 were included in this release (https://github.com/vagrant-libvirt/vagrant-libvirt/releases/tag/0.8.0). So I removed both of these patches from the spec for my 0.9.0 testing. There's also a patch100 (file: vagrant-libvirt-0.0.45-enable-qemu-session-by-default.patch) that the spec comment references this upstream issue: https://github.com/vagrant-libvirt/vagrant-libvirt/pull/969 This patch does _not_ apply cleanly to v0.9.0. It seems there was a syntax change in spec/unit/action/create_domain_spec.rb. The F36 patch is trying to comment out this line: allow(domain_volume).to receive(:[]).with('name').and_return('vagrant-test_default.img') However that line appears to have changed to: allow(domain_volume).to receive(:path).and_return('/var/lib/libvirt/images/vagrant-test_default.img') For testing purposes, I commented out the application of this patch since this patch appears to be just changing a default setting in the vagrant plugin. Next, there are a string of rspec failures like this: + bundle exec rspec spec An error occurred while loading ./spec/unit/action/clean_machine_folder_spec.rb. Failure/Error: require 'spec_helper' SyntaxError: /home/shawn/rpmbuild/BUILD/vagrant-libvirt-0.9.0/usr/share/vagrant/gems/gems/vagrant-libvirt-0.9.0/spec/spec_helper.rb:58: syntax error, unexpected end-of-input, expecting `end' # ./spec/unit/action/clean_machine_folder_spec.rb:3:in `require' # ./spec/unit/action/clean_machine_folder_spec.rb:3:in `<top (required)>' # /usr/share/gems/gems/bundler-2.3.7/libexec/bundle:48:in `block in <top (required)>' # /usr/share/gems/gems/bundler-2.3.7/libexec/bundle:36:in `<top (required)>' -----END SAMPLE RSPEC FAILURE----- I suspect this is an upstream issue in the referenced spec/spec_helper.rb. There is a block commented out at the beginning of this file that has a "begin" but the correspinding "end" is ommented out. For testing, if I skip the rspec run in the spec (comment out: bundle exec rspec spec), then I can successfully generate an RPM. If I install this 0.9.0 RPM, it appears to resolve bug 2100543 since 0.9.0 includes the upstream fixes to that issue.
Releases retrieved: 0.10.0 Upstream release that is considered latest: 0.10.0 Current version/release in rawhide: 0.7.0-4.fc37 URL: https://github.com/vagrant-libvirt/vagrant-libvirt Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/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/ To change the monitoring settings for the project, please visit: https://src.fedoraproject.org/rpms/vagrant-libvirt
Releases retrieved: 0.10.1 Upstream release that is considered latest: 0.10.1 Current version/release in rawhide: 0.7.0-4.fc37 URL: https://github.com/vagrant-libvirt/vagrant-libvirt Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/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/ To change the monitoring settings for the project, please visit: https://src.fedoraproject.org/rpms/vagrant-libvirt
(In reply to Shawn K. O'Shea from comment #10) > Tried manually build 0.9.0 from F36 specfile. > > * 0.7.0 was release 2021-11-08. > * F36 spec includes patch for > https://github.com/vagrant-libvirt/vagrant-libvirt/pull/1416 > * PR 1416 was merged on Dec 3, 2021. > * F36 spec includes patch for > https://github.com/vagrant-libvirt/vagrant-libvirt/pull/1424 > * PR 1424 was merged on Dec 11, 2021. > * According to 0.8.0 changelog, pr 1416 and 1424 were included in this > release > (https://github.com/vagrant-libvirt/vagrant-libvirt/releases/tag/0.8.0). > > So I removed both of these patches from the spec for my 0.9.0 testing. Sounds good. > There's also a patch100 (file: > vagrant-libvirt-0.0.45-enable-qemu-session-by-default.patch) that the spec > comment references this upstream issue: > https://github.com/vagrant-libvirt/vagrant-libvirt/pull/969 > > This patch does _not_ apply cleanly to v0.9.0. It seems there was a syntax > change in spec/unit/action/create_domain_spec.rb. The F36 patch is trying to > comment out this line: > allow(domain_volume).to > receive(:[]).with('name').and_return('vagrant-test_default.img') > However that line appears to have changed to: > allow(domain_volume).to > receive(:path).and_return('/var/lib/libvirt/images/vagrant-test_default.img') > > For testing purposes, I commented out the application of this patch since > this patch appears to be just changing a default setting in the vagrant > plugin. Yes, it just changes default, but we want to keep that, so the patch needs to be adjusted. > Next, there are a string of rspec failures like this: > + bundle exec rspec spec > > An error occurred while loading > ./spec/unit/action/clean_machine_folder_spec.rb. > Failure/Error: require 'spec_helper' > > SyntaxError: > > /home/shawn/rpmbuild/BUILD/vagrant-libvirt-0.9.0/usr/share/vagrant/gems/gems/ > vagrant-libvirt-0.9.0/spec/spec_helper.rb:58: syntax error, unexpected > end-of-input, expecting `end' > # ./spec/unit/action/clean_machine_folder_spec.rb:3:in `require' > # ./spec/unit/action/clean_machine_folder_spec.rb:3:in `<top (required)>' > # /usr/share/gems/gems/bundler-2.3.7/libexec/bundle:48:in `block in <top > (required)>' > # /usr/share/gems/gems/bundler-2.3.7/libexec/bundle:36:in `<top (required)>' > -----END SAMPLE RSPEC FAILURE----- > I suspect this is an upstream issue in the referenced spec/spec_helper.rb. > There is a block commented out at the beginning of this file that has a > "begin" but the correspinding "end" is ommented out. Clearly, the spec/spec_helper.rb has invalid syntax and I think this is due to [1] in combination with this [2] change. IOW, it should be enough to remove the lines [1]. [1]: https://src.fedoraproject.org/rpms/vagrant-libvirt/blob/rawhide/f/vagrant-libvirt.spec#_100-103 [2]: https://github.com/vagrant-libvirt/vagrant-libvirt/commit/380b3c2096c1df428ed7376c5e7596fe1cdb380e > For testing, if I skip the rspec run in the spec (comment out: bundle exec > rspec spec), then I can successfully generate an RPM. > > If I install this 0.9.0 RPM, it appears to resolve bug 2100543 since 0.9.0 > includes the upstream fixes to that issue.
Releases retrieved: 0.10.2 Upstream release that is considered latest: 0.10.2 Current version/release in rawhide: 0.7.0-4.fc37 URL: https://github.com/vagrant-libvirt/vagrant-libvirt Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/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/ To change the monitoring settings for the project, please visit: https://src.fedoraproject.org/rpms/vagrant-libvirt
Releases retrieved: 0.10.3 Upstream release that is considered latest: 0.10.3 Current version/release in rawhide: 0.7.0-4.fc37 URL: https://github.com/vagrant-libvirt/vagrant-libvirt Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/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/ To change the monitoring settings for the project, please visit: https://src.fedoraproject.org/rpms/vagrant-libvirt
Releases retrieved: 0.10.4 Upstream release that is considered latest: 0.10.4 Current version/release in rawhide: 0.7.0-4.fc37 URL: https://github.com/vagrant-libvirt/vagrant-libvirt Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/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/ To change the monitoring settings for the project, please visit: https://src.fedoraproject.org/rpms/vagrant-libvirt
Releases retrieved: 0.10.5 Upstream release that is considered latest: 0.10.5 Current version/release in rawhide: 0.7.0-4.fc37 URL: https://github.com/vagrant-libvirt/vagrant-libvirt Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/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/ To change the monitoring settings for the project, please visit: https://src.fedoraproject.org/rpms/vagrant-libvirt
Releases retrieved: 0.10.6 Upstream release that is considered latest: 0.10.6 Current version/release in rawhide: 0.7.0-4.fc37 URL: https://github.com/vagrant-libvirt/vagrant-libvirt Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/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/ To change the monitoring settings for the project, please visit: https://src.fedoraproject.org/rpms/vagrant-libvirt
Releases retrieved: 0.10.7 Upstream release that is considered latest: 0.10.7 Current version/release in rawhide: 0.7.0-4.fc37 URL: https://github.com/vagrant-libvirt/vagrant-libvirt Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/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/ To change the monitoring settings for the project, please visit: https://src.fedoraproject.org/rpms/vagrant-libvirt
Releases retrieved: 0.10.8 Upstream release that is considered latest: 0.10.8 Current version/release in rawhide: 0.7.0-4.fc37 URL: https://github.com/vagrant-libvirt/vagrant-libvirt Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/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/ To change the monitoring settings for the project, please visit: https://src.fedoraproject.org/rpms/vagrant-libvirt
@Vít Ondruch are you still working on this? I was expecting updates with Fedora 37, but it's the same version as it was 6 months ago in Fedora 36. I would be very happy if you could accelerate the development schedule for this.
(In reply to Philipp Trulson from comment #21) I would certainly welcome some help with this. @pvalena was also looking into updating this, but he is also sidetracked by other projects :/
Releases retrieved: 0.11.0 Upstream release that is considered latest: 0.11.0 Current version/release in rawhide: 0.7.0-4.fc37 URL: https://github.com/vagrant-libvirt/vagrant-libvirt Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/ More information about the service that created this bug can be found at: https://docs.fedoraproject.org/en-US/package-maintainers/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/ To change the monitoring settings for the project, please visit: https://src.fedoraproject.org/rpms/vagrant-libvirt
Releases retrieved: 0.11.1 Upstream release that is considered latest: 0.11.1 Current version/release in rawhide: 0.7.0-4.fc37 URL: https://github.com/vagrant-libvirt/vagrant-libvirt Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/ More information about the service that created this bug can be found at: https://docs.fedoraproject.org/en-US/package-maintainers/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/ To change the monitoring settings for the project, please visit: https://src.fedoraproject.org/rpms/vagrant-libvirt
Releases retrieved: 0.11.2 Upstream release that is considered latest: 0.11.2 Current version/release in rawhide: 0.7.0-4.fc37 URL: https://github.com/vagrant-libvirt/vagrant-libvirt Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/ More information about the service that created this bug can be found at: https://docs.fedoraproject.org/en-US/package-maintainers/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/ To change the monitoring settings for the project, please visit: https://src.fedoraproject.org/rpms/vagrant-libvirt
(In reply to Vít Ondruch from comment #22) > (In reply to Philipp Trulson from comment #21) > I would certainly welcome some help with this. @pvalena was also looking > into updating this, but he is also sidetracked by other projects :/ Is this a task that would be suitable for an experienced developer but unexperienced Fedora packager to take on? If yes: do you have any hints on what I'd need to do (on a high level).
@Mattias Thanks for asking. The most basic approach would be to open PR against vagrant-libvirt [1] with the proposed changes and of course elaborating that you did whatever testing you could. But if you wanted to contribute long term, then this [2] is the right guide. There are references to various tools (but also small reference for one off contributions [3]) and there is also Join SIG [4] helping with onboarding. Also feel free to ping me on IRC [5] at #fedora-ruby should you have more questions. [1] https://src.fedoraproject.org/rpms/vagrant-libvirt [2] https://docs.fedoraproject.org/en-US/package-maintainers/Joining_the_Package_Maintainers/ [3] https://docs.fedoraproject.org/en-US/package-maintainers/Joining_the_Package_Maintainers/#one_off_contributions [4] https://fedoraproject.org/wiki/SIGs/Join [5] https://fedoraproject.org/wiki/Communicating_and_getting_help#IRC_for_interactive_community_support
Not sure how to link it to this bug, but this PR should solve this issue: https://src.fedoraproject.org/rpms/vagrant-libvirt/pull-request/8