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 1919351

Summary: rubygem-jbuilder-2.11.2 is available
Product: [Fedora] Fedora Reporter: Upstream Release Monitoring <upstream-release-monitoring>
Component: rubygem-jbuilderAssignee: Vít Ondruch <vondruch>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: pvalena, strzibny, vondruch
Target Milestone: ---Keywords: FutureFeature, Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: rubygem-jbuilder-2.11.2-1.fc35 rubygem-jbuilder-2.11.2-1.fc34 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-03-04 10:39:03 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
[patch] Update to 2.11.0 (#1919351)
none
[patch] Update to 2.11.1 (#1919351) none

Description Upstream Release Monitoring 2021-01-22 16:06:19 UTC
Latest upstream release: 2.11.0
Current version/release in rawhide: 2.10.1-1.fc34
URL: http://rubygems.org/gems/jbuilder

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

Comment 1 Upstream Release Monitoring 2021-01-22 16:06:29 UTC
Created attachment 1749825 [details]
[patch] Update to 2.11.0 (#1919351)

Comment 2 Upstream Release Monitoring 2021-01-22 16:10:18 UTC
the-new-hotness/release-monitoring.org's scratch build of rubygem-jbuilder-2.11.0-1.fc32.src.rpm for rawhide completed http://koji.fedoraproject.org/koji/taskinfo?taskID=60229258

Comment 3 Upstream Release Monitoring 2021-01-25 16:44:57 UTC
Latest upstream release: 2.11.1
Current version/release in rawhide: 2.10.1-1.fc34
URL: http://rubygems.org/gems/jbuilder

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

Comment 4 Upstream Release Monitoring 2021-01-25 16:44:59 UTC
Created attachment 1750562 [details]
[patch] Update to 2.11.1 (#1919351)

Comment 5 Upstream Release Monitoring 2021-01-25 17:00:58 UTC
the-new-hotness/release-monitoring.org's scratch build of rubygem-jbuilder-2.11.1-1.fc32.src.rpm for rawhide completed http://koji.fedoraproject.org/koji/taskinfo?taskID=60473934

Comment 6 Upstream Release Monitoring 2021-01-27 12:59:25 UTC
Latest upstream release: 2.11.2
Current version/release in rawhide: 2.10.1-1.fc34
URL: http://rubygems.org/gems/jbuilder

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

Comment 7 Upstream Release Monitoring 2021-01-27 12:59:28 UTC
An unexpected error occurred while creating the scratch build and has been automatically reported. Sorry!

Comment 8 Vít Ondruch 2021-02-10 17:32:42 UTC
jbuilder is currently FTBFS due to Rails 6.1:

https://github.com/rails/jbuilder/issues/500

Comment 9 Fedora Update System 2021-03-04 10:39:03 UTC
FEDORA-2021-6b3f154b06 has been pushed to the Fedora 35 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 10 Fedora Update System 2021-03-04 10:40:19 UTC
FEDORA-2021-612c0c3115 has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2021-612c0c3115

Comment 11 Fedora Update System 2021-03-04 16:59:18 UTC
FEDORA-2021-612c0c3115 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-612c0c3115`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-612c0c3115

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

Comment 12 Fedora Update System 2021-03-19 20:02:48 UTC
FEDORA-2021-612c0c3115 has been pushed to the Fedora 34 stable repository.
If problem still persists, please make note of it in this bug report.