On 02 mars 2025 08:34, James Abernathy <jfabernathy@???> wrote:
[...]
> This may be a dumb question, but why require the unstable branch? In
> testing the recent v35 branch of mythtv, I've been building the .deb
> packages on Debian 12 bookworm using the mythtv-light method. The
> only downside is that mythtv-light provides no mythconverg database,
> mythtv user setup, or Storage Group directory setup. But that is a
> script I've had for years.
As Debian new packages are always uploaded to unstable, then moved to
testing after 4 days without bug reports.
As Debian too, I don't try to upload new version to stable, oldstable
or oldodstable. For that we have *-backports distributions.
As you can see below, each distribution have a new version in backports.
I'll backport 35.0 to stable-backports today.
,----
| mythtv-dmo | 30.0+fixes20210328.git7d297b1fb8-dmo0+deb10u1 | oldoldstable | source
| mythtv-dmo | 31.0+fixes20220227.git7e4ce1ba98-dmo0~bpo10+2 | oldoldstable-backports | source
| mythtv-dmo | 1:31.0+fixes20220227.git7e4ce1ba98-dmo0+deb11u1 | oldstable | source
| mythtv-dmo | 1:33.1+fixes20240210.git512d723c83-dmo0~bpo11+2 | oldstable-backports | source
| mythtv-dmo | 1:33.1+fixes20240210.git512d723c83-dmo0+deb12u1 | stable | source
| mythtv-dmo | 1:34.0+really34+fixes20250116.gitf4cbdd37a5-dmo0~bpo12+1 | stable-backports | source
| mythtv-dmo | 1:35.0-dmo1 | testing | source
| mythtv-dmo | 1:35.0-dmo1 | unstable | source
`----
Christian
