#11261 Unretire google-crosextra-caladea-fonts
Closed: Fixed a year ago by humaton. Opened a year ago by pnemade.

Name of the package?

google-crosextra-caladea-fonts

FAS username of the new maintainer?

pnemade

Branches that you need it to be unretired for?

f36, f37, f38, main

Package re-review BZ URL?

https://bugzilla.redhat.com/show_bug.cgi?id=2166813

As per https://bugzilla.redhat.com/show_bug.cgi?id=2162532, we need to revert current Caladea font to previous release to have Caladea available metrically same as Cambria font.

Any extra information?


Metadata Update from @phsmoura:
- Issue tagged with: low-gain, low-trouble, ops

a year ago

Can this be fixed soon?

@releng Is there no one available to work on this ticket?

releng has been very busy with the mass branching, fixing things and then a s390x outage.

Someone should be able to process this soon, thanks for your patience.

The package is now unretired. For missing branches please use $fedpkg request-branch

Metadata Update from @humaton:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

a year ago

Metadata Update from @pnemade:
- Issue status updated to: Open (was: Closed)

a year ago

I always assumed unretirement comes with unblocking....
Please I request to unblock this package for F37, F38, F39/main branches

When I tried to build this package I got
google-crosextra-caladea-fonts-1.002-0.15.20130214.fc39
FAILED: BuildError: package google-crosextra-caladea-fonts is blocked for tag f39-updates-candidate

I think releng should either change the template for this request which includes which branches to unblock or they should do it implicitly from answer to unretirement branches.
Because the guidelines says do all things in single releng ticket -> https://docs.fedoraproject.org/en-US/package-maintainers/Package_Retirement_Process/#claiming

You are not the only one affected by this for some reason a bunch of unretirement requests didn't work correctly. Also please note main is not a branch just a symlink if you push to main you create a new branch that will be out of sync with the rawhide branch.

I rebuilt the the package https://koji.fedoraproject.org/koji/buildinfo?buildID=2153834

Metadata Update from @humaton:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

a year ago

Thank you so much for your help @humaton

Log in to comment on this ticket.

Metadata
Boards 1
Ops Status: Backlog