#9943 DNF in F32 stable updates went backwards
Closed: Fixed 3 years ago by mohanboddu. Opened 3 years ago by kkofler.

  • Describe the issue
    This F32 update: https://bodhi.fedoraproject.org/updates/FEDORA-2020-e49210967b was just pushed to stable, replacing the newer DNF from https://bodhi.fedoraproject.org/updates/FEDORA-2020-4f53b68751 which went stable 4 days ago, so DNF went backwards.
    (dnf and libdnf and their subpackages were downgraded.)
    Some tagging magic needs to happen to make Koji etc. believe that the latest version is actually the latest.

  • When do you need this? (YYYY/MM/DD)
    no concrete deadline, but the sooner, the better

  • When is this no longer needed or useful? (YYYY/MM/DD)
    F32 EOL, or if a newer DNF gets pushed as an update to F32 stable updates

  • If we cannot complete your request, what is the impact?
    dnf distro-sync will want to downgrade dnf, and users upgrading now will not get the newer version.


Issue status updated to: Open (was: Closed)

3 years ago

I tagged the latest builds of dnf and libdnf back into f32-updates tag and running a f32 stable push which should fix the issue for the users.

Metadata Update from @mohanboddu:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)
- Issue tagged with: medium-gain, medium-trouble, ops

3 years ago

This should be fixed now.

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

3 years ago

Login to comment on this ticket.

Metadata
Boards 1
Ops Status: Backlog