Ticket #7434 (assigned Bug Report - General)
Opened 4 years ago
Last modified 8 months ago
max episodes code doesn't respect autoexpire flag on a recording
| Reported by: | stuarta | Owned by: | stuarta |
|---|---|---|---|
| Priority: | major | Milestone: | 0.26.1 |
| Component: | MythTV - General | Version: | Master Head |
| Severity: | high | Keywords: | |
| Cc: | stuartm | Ticket locked: | no |
Description
I've a recording rule setup as follows.
- Max episodes = 20
- Record new / delete old
- Allow autoexpire
I decided i wanted to keep 1 of the 20 recordings and set autoexpire=off on that recording.
However when it recorded a new episode, that episode was removed because it was the oldest, in direct violation of autoexpire=off.
Stuart
Attachments
Change History
comment:2 Changed 3 years ago by cpinkham
- Status changed from assigned to closed
- Type changed from defect to enhancement
- Version changed from 0.22rc1 to Trunk Head
- Resolution set to wontfix
With reservation, I'm closing this as a feature request without a patch. This code has been this way for going on 6 years. The original author and the ticket reporter may reopen this and make changes later if they desire.
comment:3 Changed 3 years ago by stuarta
- Status changed from closed to new
- Resolution wontfix deleted
comment:4 Changed 3 years ago by stuarta
- Owner changed from cpinkham to stuarta
- Status changed from new to assigned
I'll take this back then. I feel it's quite a significant bug when an episode marked to not autoexpire is autoexpired.
Stuart
comment:5 Changed 3 years ago by stuartm
- Cc stuartm added
- Priority changed from minor to major
- Severity changed from medium to high
comment:6 Changed 15 months ago by stuartm
- Type changed from enhancement to Bug Report - General
- Milestone changed from unknown to 0.26
We need to simplify the behaviour here to match expectations, having two separate flags (preserve and autoexpire) is just too confusing. I appreciate the attempt to satisfy everyone, but I really do agree with Stuart that maybe it's better if disabling auto-expire acts the same way as preserve and preserve was eliminated.
If we do that then it would probably help to rename it from 'Disable Auto-expire' to 'Block Deletion' or similar and make it a catch-all state that doesn't allow any code to delete that recording without the 'block' being removed. That's simple enough for everyone to understand.
