Opened 16 years ago
Closed 4 years ago
#7434 closed Bug Report - General (Trac EOL)
max episodes code doesn't respect autoexpire flag on a recording
| Reported by: | Stuart Auchterlonie | Owned by: | Stuart Auchterlonie |
|---|---|---|---|
| Priority: | major | Milestone: | 29.2 |
| 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
Change History (14)
comment:1 by , 15 years ago
| Status: | new → assigned |
|---|
comment:2 by , 15 years ago
| Resolution: | → wontfix |
|---|---|
| Status: | assigned → closed |
| Type: | defect → enhancement |
| Version: | 0.22rc1 → Trunk Head |
comment:3 by , 15 years ago
| Resolution: | wontfix |
|---|---|
| Status: | closed → new |
comment:4 by , 15 years ago
| Owner: | changed from to |
|---|---|
| Status: | new → 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 by , 15 years ago
| Cc: | added |
|---|---|
| Priority: | minor → major |
| Severity: | medium → high |
comment:6 by , 14 years ago
| Milestone: | unknown → 0.26 |
|---|---|
| Type: | enhancement → Bug Report - General |
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.
comment:7 by , 13 years ago
| Milestone: | 0.26 → 0.26.1 |
|---|
comment:8 by , 12 years ago
| Milestone: | 0.26.1 → 0.28 |
|---|
comment:9 by , 10 years ago
| Milestone: | 0.28 → 0.29 |
|---|
comment:11 by , 8 years ago
| Milestone: | 29.0 → 29.1 |
|---|
comment:12 by , 8 years ago
| Milestone: | 29.1 → 0.28.2 |
|---|
Moving remaining open tickets to 0.28.2 milestone
comment:13 by , 8 years ago
| Milestone: | 0.28.2 → 29.2 |
|---|
Moving remaining open tickets to 29.2 milestone
comment:14 by , 4 years ago
| Resolution: | → Trac EOL |
|---|---|
| Status: | assigned → closed |
We have moved all bug tracking to github [1]
If you continue to have this issue, please open a new issue at github, referencing this ticket.
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.