Bug 1792666 - rubygem-mercenary-0.4.0 is available
Summary: rubygem-mercenary-0.4.0 is available
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: rubygem-mercenary
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Björn 'besser82' Esser
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-01-19 00:58 UTC by Upstream Release Monitoring
Modified: 2023-09-15 00:20 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-06-05 19:04:48 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Upstream Release Monitoring 2020-01-19 00:58:12 UTC
Latest upstream release: 0.4.0
Current version/release in rawhide: 0.3.6-7.fc31
URL: https://github.com/jekyll/mercenary

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

Comment 1 Upstream Release Monitoring 2020-01-19 00:58:15 UTC
An unexpected error occurred while creating the scratch build and has been automatically reported. Sorry!

Comment 2 Otto Liljalaakso 2021-03-14 18:24:42 UTC
Is there any possiblity to update rubygem-mercenary to 0.4.0? Jekyll actually declares minimum usable version 0.4.0, currently we patch it to accept 0.3.6. It works, but it would be nice to get the bugfix into Fedora — the bug is not serious, but still affects Jekyll.

If you prefer, you can also add me as co-maintainer for rubygem-mercenary so I can take care of the update myself.

Comment 3 Fedora Update System 2021-05-26 18:07:49 UTC
FEDORA-2021-099d090c37 has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2021-099d090c37

Comment 4 Fedora Update System 2021-05-26 18:09:16 UTC
FEDORA-2021-8bb7cf4c94 has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2021-8bb7cf4c94

Comment 5 Fedora Update System 2021-05-27 01:32:36 UTC
FEDORA-2021-8bb7cf4c94 has been pushed to the Fedora 34 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-8bb7cf4c94`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-8bb7cf4c94

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 6 Fedora Update System 2021-05-27 01:39:42 UTC
FEDORA-2021-099d090c37 has been pushed to the Fedora 33 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-099d090c37`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-099d090c37

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 7 Fedora Update System 2021-06-04 01:03:09 UTC
FEDORA-2021-099d090c37 has been pushed to the Fedora 33 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 8 Fedora Update System 2021-06-04 01:12:42 UTC
FEDORA-2021-8bb7cf4c94 has been pushed to the Fedora 34 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 9 Red Hat Bugzilla 2023-09-15 00:20:51 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 500 days


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