#11151 can no longer push to f35 branch in dist-git: early / wrong EOL date in PDC?
Closed: Fixed a year ago by humaton. Opened a year ago by decathorpe.

  • Describe the issue

It looks like PDC flipped the switch for f35 being EOL a few minutes ago. I pushed one package, built it, waited for newRepo, tried to push and build the second package, and now the pre-receive hook fails with "Branch refs/heads/f35 is unsupported"

  • When do you need this? (YYYY/MM/DD)

ASAP

  • When is this no longer needed or useful? (YYYY/MM/DD)

At F35 EOL (in 3-4 weeks).

  • If we cannot complete your request, what is the impact?

I cannot push a critical bugfix update to F35, which is possibly also required for testing the new Sequoia PGP backend in RPM.


This was due to fedscm-admin having old f35 EOL. It affects only a minimal subset of packages added after 31.10 when we updated EOL for all packages in PDC to the correct date.

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

a year ago

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

a year ago

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

a year ago

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

a year ago

Login to comment on this ticket.

Metadata
Boards 1
Ops Status: Backlog