pagure

#4886 'vagrant up' runs into trouble during provisioning
Closed: Fixed by wombelix. Opened by sudoman.

Closed: Fixed
Reopen Issue

I recently attempted to run a fresh vagrant up on Debian 10 and Fedora 32. There was an issue with creating a symlink, so I added a rule to create the parent directory for that symlink. However provisioning ran into further trouble, due to a missing pagure.lib module. Thanks : )

Metadata Update from @ngompa:
- Issue set to the milestone: 5.12

Metadata Update from @ngompa:
- Issue set to the milestone: None (was: 5.12)

Metadata Update from @wombelix:
- Issue assigned to wombelix

@sudoman the issue is quite old, does it still exist? Debian 10 hit EOL in August 2022 and is since then in LTS state, F32 became EOL in May 2021. So I guess you use different OS versions in the meantime? Also if you could share some more details, like error message, would be very helpful to understand the problem and see if / what might need to be fixed.

No feedback and the last commit to fix/improve vagrant was half a year ago https://pagure.io/pagure/pull-request/5415, so we can assume this isn't relevant anymore.

Metadata Update from @wombelix:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)
Metadata
None
None
None
None
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.