#10014 Unretire rpms/biblesync
Closed: Fixed 3 years ago by humaton. Opened 3 years ago by greghellings.

  • Describe the issue

This package was auto-retired for no discernible reason. There are bugs claiming it FTBFS in F33, but it has always appeared to build whenever I try.

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

  • If we cannot complete your request, what is the impact? The Xiphos package will also need to be retired, as it has a hard dependency on this library.


Thanks for claiming the package back!

Just a few comments about the reasons this happened:

This package was auto-retired for no discernible reason.

The package was retired, because it was orphaned for 6+ weeks.

There are bugs claiming it FTBFS in F33, but it has always appeared to build whenever I try.

The package was orphaned because nobody responded to those bugs since August. Whether the bugs were legitimate or not, all that needed to be done to avoid the orphaning was to respond.

Anyway, you are correct that the package appears to build just fine. Apparently, the FTBS bug was opened based on some transient failure. If you have tips how to improve the process to avoid "auto-retirement for no discernible reason", please do let me know, I'd be happy to improve it.

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

3 years ago

The package is now unretired.

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

3 years ago

Thanks for claiming the package back!

Just a few comments about the reasons this happened:

This package was auto-retired for no discernible reason.

The package was retired, because it was orphaned for 6+ weeks.

Huh, I must have missed the orphan notifications for it. Mea culpa!

There are bugs claiming it FTBFS in F33, but it has always appeared to build whenever I try.

The package was orphaned because nobody responded to those bugs since August. Whether the bugs were legitimate or not, all that needed to be done to avoid the orphaning was to respond.

Has this auto-orphaning changed? In the past I've had packages FTBFS, then auto-build again. I thought that closed the FTBFS tickets.

Anyway, you are correct that the package appears to build just fine. Apparently, the FTBS bug was opened based on some transient failure. If you have tips how to improve the process to avoid "auto-retirement for no discernible reason", please do let me know, I'd be happy to improve it.

The only thing I can think is, if it's possible to auto-close the FTBFS tickets once the package builds successfully again? I thought that used to happen. Maybe the messages from back then were manual closings by rel-eng people.

Other than that, probably just an issue in self-improvement on my end to pay better attention to the notices. Thanks!

Indeed, the closing was always done by individual people, as far as I remember.

Login to comment on this ticket.

Metadata
Boards 1
Ops Status: Backlog