linux-traipu team mailing list archive

[Manfred Thole <manfred@xxxxxxxxx>]

Fixed with update from last Wednesday (2018-08-16). Frontend on amd64
connects now successfully with backend on armhf.

** Changed in: mythbuntu
       Status: New => Fix Released

-- 
You received this bug notification because you are a member of UBUNTU -
AL - BR, which is subscribed to Mythbuntu.
https://bugs.launchpad.net/bugs/1708946

Title:
  MythTV Schema Version (DBSchemaVer) still on 1347 for armhf

Status in Mythbuntu:
  Fix Released

Bug description:
  Today I upgraded my mythtv-backend server (on armhf) and my mythtv-
  frontend clients (amd64) from 0.28.1 to (0.)29 using the
  mythbuntu/0.29 ppa.

  The backend migrated the DBSchemaVer from 1344 to 1347. Even
  restarting the backend doesn't trigger any further migration of
  DBSchemaVer.

  Now the mythtv-frontends complain that the DBSchemaVer is one version
  behind and are refusing to start.

  Digging into this I noticed that the current libmyth package on armhf
  has the version:

     2:0.29.0~master.20170608.f593e23-0ubuntu0mythbuntu4

  whereas on amd64 the version is:

     2:29.0~master.20170714.7a1ab50-0ubuntu0mythbuntu4

  I assume this is the root cause of the DBSchemaVer mismatch between
  armhf and amd64.

  Some more findings:

  Running mythlink.pl on the backend gives:

     Database schema 1347 not supported.
     Bindings support schema version 1348

To manage notifications about this bug go to:
https://bugs.launchpad.net/mythbuntu/+bug/1708946/+subscriptions