4.1.X install from "unstable" APT repo -> 4.0.X install from self-built release/4.0 branch .deb

c128 m

Hi,

Bit of advice required...

I'm currently running 4.1.18~gec3ba93~utopic installed from the "unstable" APT repository, but would like to shift to always using the latest "stable" 4.0.X delivery - this is mainly because I'm seeing a couple of issues with 4.1.18 at the moment (high CPU usage and recordings non-playable in Kodi) but I'd like to make the shift as soon as possible anyway.

As the APT "stable" and "beta" repos aren't yet shifted to delivering around the new 4.0/4.1 plan, I've built my own .deb - currently tvheadend_4.0.1-5~ge776d34~precise_amd64.deb (with a plan to re-build it and re-install it as and when required).

I guess I'm wondering whether stuff has diverged enough in the 4.1.X deliveries I'm already using that there'll be issues in doing this i.e. incompatibilities with my current setup that mean I'll have to start from scratch with my pre-existing setup/configuration if I make the shift... I could go for a clean install, but that would be a bigger project.

Given where I am starting from, and where I want to get to, should it be a simple case of removing the "unstable" repo from my

sources.list

and just dpkg installing the new

.deb

and all should be well?

Thanks.

Anonymous

agree...

the "unstable" repo isn`t as actual as it should. it seems, that the nightly biuld process failed, bcoz there is no actual package available (as i reported in ticket-system).

please fix it.

thx

ProfYaffle

Folks are working on updating the whole build/release system - work-in-progress - it's clear that the current stable/beta/unstable model doesn't reflect how it works now. It's likely to move to a stable/testing/master model, with 4.0 moving to testing (so more of a rolling test vs clear alpha/beta releases) and 4.1 sitting in master, but that's to be concluded based on how often fixes are to be backported from 4.1 to the 4.0 branch.

@c128: no major config changes that I'm aware of. Take a good backup just in case (preserve permissions and file ownership when cp-ing) and you should be able to 'downgrade' cleanly. Remove the unstable repo, as you say, otherwise the next apt-get will just upgrade again because it sees unstable as a later version.

FWIW, I've gone up and down the 3.9.x tree many times, with very few problems.

c128 m

Prof Yaffle wrote:
> @c128: no major config changes that I'm aware of. Take a good backup just in case (preserve permissions and file ownership when cp-ing) and you should be able to 'downgrade' cleanly. Remove the unstable repo, as you say, otherwise the next apt-get will just upgrade again because it sees unstable as a later version.
>

> FWIW, I've gone up and down the 3.9.x tree many times, with very few problems.

Thanks Prof Yaffle - will give this a spin (hopefully today) and see how it goes ;) .

Anonymous

thx 4 the info... :)

c128 m

Just as a report back, it was (mostly) a success.

Everything seems to be running fine, overall CPU use has dropped dramatically and recordings are now playable again within Kodi.

However...something odd.

My Recordings list has been emptied - both within the tvheadend "Digital Video Recorder | Finished Recordings" view and within Kodi. It looks like they've all been shifted to be under "Digital Video Recorder | Failed Recordings" (that was previously empty). They all have the Status of "time missed", but were all successful "Finished Recordings" before the change.

Only thing I can see in the logs that looks (vaguely) relevant to the version migration is this:


May 26 19:14:42 tv tvheadend[9857]: config: backup: migrating config from 4.1.18~gec3ba93~utopic (running 4.0.1-5~ge776d34)
May 26 19:14:42 tv tvheadend[9857]: config: backup: running, output file /home/hts/.hts/tvheadend/backup/4.1.18~gec3ba93~utopic.tar.bz2
May 26 19:14:42 tv tvheadend[9857]: spawn: Executing "/bin/tar"
May 26 19:14:42 tv tvheadend[9857]: config: loaded

Also, the my upcoming recording timers were deleted (but still exist, so I guess re-created, and not an issue) e.g. :

May 26 19:14:48 tv tvheadend[9857]: dvr: delete entry 97aea402e7f5e04a481b98064707b185 "Have I Got News For You" on "BBC One HD" start time 1432929600, scheduled for recording by "Auto recording by: generic" (duplicate with 40acd7e3b8483fb8db949dec3dab3afc) May 26 19:14:48 tv tvheadend[9857]: dvr: delete entry c4af5ee3e88a73244c05dd6bbd8fdbdd "Episodes" on "BBC Two HD" start time 1433192400, scheduled for recording by "Auto recording by: generic" (duplicate with f087622c0d8880477ded30f315476b1c)

Dunno if something like what's directly above happens often with an upgrade (or, downgrade, in my case) and I just haven't noticed.

Either way, the missing older recordings isn't an issue for me at all as they still physically exist and I can watch them directly in Kodi under "Videos" through a share (which had been my workaround for the 4.1 recordings not playing directly in Kodi anyway). New recordings seem to turn up fine. Unless, that is, there's a manual way to update these older recordings to be successful as Kodi/tvheadend sees them?

ProfYaffle

I've heard of other folks having the same issue, but not seen it myself - indeed, I play recordings over a share as you do, so wouldn't immediately notice anyway. All I can suggest is log it as a bug and hang on to any relevant log files - it shouldn't happen, and hasn't with 3.9.x version moves, but that doesn't mean that something's broken...

c128 m

Will do - thanks for the help.

Anonymous

when will be build actual *.deb-packages...?

ProfYaffle

4.0 automatic builds are coming shortly - a few more days, please...

Anonymous

some news...? :D

rgds mad

Mathias Neuhaus

seems like something is happening ...

--> https://tvheadend.org/projects/tvheadend/wiki/AptRepository

((!) I didn't test this yet!)

Anonymous

seems working...!

thx... :)