#7070 Latest FlightGear build in f28 is not the newest (2017.2.1-5.fc28 and 2017.3.1-1.fc28)
Closed: Fixed 6 years ago Opened 6 years ago by bellet.

FlightGear-2017.2.1-5.fc28 and FlightGear-2017.3.1-1.fc28 have been built in this order the same day, but version 2017.2.1 is still reported as the latest one by koji (and I'm bugged about broken deps for this reason). What should I do to make 2017.3.1 the latest one ?

$ koji list-tagged --latest-n=1 f28 FlightGear
Build                                     Tag                   Built by
----------------------------------------  --------------------  ----------------
FlightGear-2017.2.1-5.fc28                f28                   corsepiu
$ koji list-tagged --latest-n=2 f28 FlightGear
Build                                     Tag                   Built by
----------------------------------------  --------------------  ----------------
FlightGear-2017.2.1-5.fc28                f28                   corsepiu
FlightGear-2017.3.1-1.fc28                f28                   bellet

@bellet The problem is FlightGear-2017.2.1-5.fc28 tagged into f28 later than FlightGear-2017.3.1-1.fc28. My guess is something went wonky during signing and @kevin has to retag some of the builds to make it work and thats what created the issue.

$ koji list-history --build=FlightGear-2017.2.1-5.fc28
Thu Sep 21 11:14:33 2017 FlightGear-2017.2.1-5.fc28 tagged into f28-pending by corsepiu
Sat Sep 23 16:14:58 2017 FlightGear-2017.2.1-5.fc28 untagged from f28-pending by kevin
Sat Sep 23 16:15:01 2017 FlightGear-2017.2.1-5.fc28 tagged into f28-pending by kevin
Sat Sep 23 16:15:43 2017 FlightGear-2017.2.1-5.fc28 untagged from f28-pending by autopen
Sat Sep 23 16:15:43 2017 FlightGear-2017.2.1-5.fc28 tagged into f28 by autopen [still active]

$ koji list-history --build=FlightGear-2017.3.1-1.fc28
Thu Sep 21 12:22:27 2017 FlightGear-2017.3.1-1.fc28 tagged into f28-pending by bellet
Thu Sep 21 12:23:04 2017 FlightGear-2017.3.1-1.fc28 untagged from f28-pending by autopen
Thu Sep 21 12:23:04 2017 FlightGear-2017.3.1-1.fc28 tagged into f28 by autopen [still active]

The easiest way to handle this is rebuilding FlightGear(probably FlightGear-2017.3.1-2.fc28) with a bump to release number.

OK, I'll bump and rebuild.

Bump to the release number fixed the issue:

 $ koji list-tagged --latest-n=1 f28 FlightGear
Build                                     Tag                   Built by
----------------------------------------  --------------------  ----------------
FlightGear-2017.3.1-2.fc28                f28                   bellet 

Closing the ticket.

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

6 years ago

Login to comment on this ticket.

Metadata