stable

glibc-2.36-11.fc37

FEDORA-2023-22c8575b95 created by fweimer a year ago for Fedora 37

This regular maintenance update incorporates fixes from the upstream 2.36 stable release branch.

How to install

Updates may require up to 24 hours to propagate to mirrors. If the following command doesn't work, please retry later:

sudo dnf upgrade --refresh --advisory=FEDORA-2023-22c8575b95

This update has been submitted for testing by fweimer.

a year ago

This update's test gating status has been changed to 'waiting'.

a year ago

This update's test gating status has been changed to 'passed'.

a year ago

This update's test gating status has been changed to 'failed'.

a year ago

This update has been pushed to testing.

a year ago

This update's test gating status has been changed to 'waiting'.

a year ago

This update's test gating status has been changed to 'failed'.

a year ago
karma
User Icon filiperosset commented & provided feedback a year ago
karma

no regressions noted

User Icon rai510 provided feedback a year ago
karma
User Icon rai510 provided feedback a year ago
karma
User Icon rai510 provided feedback a year ago
karma
User Icon dm0 provided feedback a year ago
karma
User Icon kparal commented & provided feedback a year ago
karma

no issues in common Workstation usage

User Icon nixuser commented & provided feedback a year ago
karma

No problems encountered.

This update's test gating status has been changed to 'waiting'.

a year ago

This update's test gating status has been changed to 'failed'.

a year ago

CI failure:

/var/ARTIFACTS/work-ciertxpvjs warn: /plans/ci:discover - {'how': 'fmf', 'directory': 'tests'} is not valid under any of the given schemas warn: /plans/ci:execute - {'how': 'beakerlib'} is not valid under any of the given schemas Found 1 plan.

/plans/ci summary: CI Gating Plan

plan failed

The exception was caused by 1 earlier exceptions

Cause number 1:

Unsupported execute method 'beakerlib' in the '/plans/ci' plan.

So I think https://src.fedoraproject.org/rpms/glibc/c/9e849490311d72a41a2cef43b85d2d841f617612?branch=f37 should fix this, but CI doesn't seem to want to pick up the change. Possibly we actually need to rebuild the package just to fix the CI config? That seems unfortunate.

sigh, yeah, we do. CI intentionally checks out the dist-git repo at the commit ID that koji associates with the package build, it doesn't just check out current f37. so we need to rebuild glibc to get the new CI config to be used...I guess I'll do that.

adamwill edited this update.

New build(s):

  • glibc-2.36-11.fc37

Removed build(s):

  • glibc-2.36-10.fc37

Karma has been reset.

a year ago

This update has been submitted for testing by adamwill.

a year ago

This update's test gating status has been changed to 'passed'.

a year ago

This update's test gating status has been changed to 'waiting'.

a year ago

This update's test gating status has been changed to 'passed'.

a year ago
User Icon adamwill provided feedback a year ago
karma

This update's test gating status has been changed to 'failed'.

a year ago

This update has been pushed to testing.

a year ago

This update's test gating status has been changed to 'waiting'.

a year ago

This update's test gating status has been changed to 'failed'.

a year ago

This update's test gating status has been changed to 'waiting'.

a year ago

This update's test gating status has been changed to 'passed'.

a year ago

This update has been submitted for stable by bodhi.

a year ago

This update has been pushed to stable.

a year ago

Please login to add feedback.

Metadata
Type
unspecified
Karma
1
Signed
Content Type
RPM
Test Gating
Autopush Settings
Unstable by Karma
-3
Stable by Karma
3
Stable by Time
14 days
Dates
submitted
a year ago
in testing
a year ago
in stable
a year ago
modified
a year ago
approved
a year ago

Automated Test Results