#8599 Periodic e-mail reminders with FTBFS packages - similar to orphaned ones
Closed: Fixed 3 years ago by kevin. Opened 4 years ago by churchyard.

We have just retired F30FTBFS packages. Their dependent packages didn't get any notice. Arguably, this is not ideal.

Previously, this was solved by orphaning the FTBFS packages prior to their retirement. This now however only happens if somebody actively tries to orphan the package (and so far, only I have been doing that for Python 2 packages).

Instead, we could possibly generate a report of packages to be retired, similar to the Orphaned packages report I send every week, the report would include dependencies. We should start sending those cca 6 weeks before the retirement actually happens.

Adapting the orphaned packages script to fetch FTBFS packages should be trivial and I'll hope to get to it after the Python 3.8 transition.

If you can, please assign this issue to me.


I just got bitten by this, so big +1 from my to also do email reminders about FTBFS packages similar to the orphan ones (so with a depchain report).

Or alternatively, maybe go FTBFS -> orphan -> retire? I don't have much of a preferences either way, but having packages other packages depends just go "poof" and disappear into a cloud of smoke without any warnings is not ideal.

I plan to propose to go FTBFS -> orphan -> retire as a policy change, but I was still waiting for FESCo feedback in the thread on devel. That's not going to happen, so I'll start with a FESCo ticket soon.

FTR we went with FTBFS -> orphan in https://pagure.io/releng/issue/8917

And I still plan to do the reminders (in fact I made sure the reminders are part of the policy).

Metadata Update from @churchyard:
- Issue assigned to churchyard

4 years ago

These are going out now... closing this.

I suppose ideally we would automate all this and not require @churchyard to run the process, but that could be another ticket?

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

3 years ago

Login to comment on this ticket.

Metadata