homebridge/homebridge-apt-pkg

Latest homebridge version

tosate opened this issue · 2 comments

Current Situation

Hi there,

I am using oznu/docker-homebridge which relies on homebridge-apt-pkg version 1.0.32 as far as I can see in the Dockerfile. In the running container, homebridge shows me v1.5.0.
According to the release date, 1.0.32 contains definitely not the latest version of homebridge. Can you please do a new release so that homebridge v1.6.0 becomes available for Docker?

Kind regards,
tosate

Logs

[11/23/2022, 2:48:39 PM] [HB Supervisor] Homebridge Process Ended. Code: 143, Signal: null
[11/23/2022, 2:50:05 PM] [HB Supervisor] OS: Linux 4.4.180+ x64
[11/23/2022, 2:50:05 PM] [HB Supervisor] Node.js v18.12.1 /opt/homebridge/bin/node
[11/23/2022, 2:50:05 PM] [HB Supervisor] Homebridge Path: /var/lib/homebridge/node_modules/homebridge/bin/homebridge
[11/23/2022, 2:50:05 PM] [HB Supervisor] UI Path: /opt/homebridge/lib/node_modules/homebridge-config-ui-x/dist/bin/standalone.js
[11/23/2022, 2:50:08 PM] [Homebridge UI] Homebridge Config UI X v4.50.2 is listening on :: port 8581
[11/23/2022, 2:50:08 PM] [HB Supervisor] Starting Homebridge with extra flags: -P /var/lib/homebridge/node_modules --strict-plugin-resolution
[11/23/2022, 2:50:08 PM] [HB Supervisor] Started Homebridge v1.5.0 with PID: 147

Configuration

not applicable

Environment

  • OS: Linux 4.4.180+ x64
  • Homebridge: 1.5.0
  • Node: v18.12.1

Process Supervisor

Docker (Mention image name in Additional Context)

Additional Context

No response

Package file is fine. The issue was caused by my package.json file.

feld commented

But why is the Debian package version not matching the latest Homebridge release? Shouldn't the versions be kept in sync?