FS#61510 - [emby-server] Package version does not match installed version

Attached to Project: Community Packages
Opened by binhex (binhex) - Wednesday, 23 January 2019, 14:46 GMT
Last edited by Maxime Gauduin (Alucryd) - Wednesday, 23 January 2019, 18:57 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Maxime Gauduin (Alucryd)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description: package version does not match installed version:-

Version 4.0.0.2
A new version of Emby Server is available!
Version 4.0.1.0 is now available for download.

Additional info:
* package version(s) 4.0.1.0-2
* config and/or log files etc. n/a

Steps to reproduce: install package 4.0.1.0-2 and note how the installed version is 4.0.0.2

comment: is this going to happen for every release?, raised a VERY similar issue when going from 3.x to 4.0.0.2
This task depends upon

Closed by  Maxime Gauduin (Alucryd)
Wednesday, 23 January 2019, 18:57 GMT
Reason for closing:  Not a bug
Comment by Jelle van der Waa (jelly) - Wednesday, 23 January 2019, 14:49 GMT
IMO, we should check if there is an option to disable version checking!
Comment by binhex (binhex) - Wednesday, 23 January 2019, 14:53 GMT
you mean the application shouldn't check for updates, or you mean disable version checking for this package?.
Comment by Doug Newgard (Scimmia) - Wednesday, 23 January 2019, 16:07 GMT
Again? Upstream really needs to get their release procedures figured out.
Comment by Maxime Gauduin (Alucryd) - Wednesday, 23 January 2019, 17:42 GMT
@binhex Or maybe you could try restarting the server after updating... The version is perfectly fine.
Comment by binhex (binhex) - Wednesday, 23 January 2019, 17:52 GMT
@Alucryd i am using this package to install Emby Server as part of an automated build of a Docker image, thus "restarting the server after updating" is not really possible. The arch package version 4.0.1.0-2 did not match the installed version (was 4.0.0.2), if this is by design and the package version is in effect meaningless then i will have to rethink things.
Comment by Maxime Gauduin (Alucryd) - Wednesday, 23 January 2019, 18:57 GMT
Docker containers can be restarted, I don't see the problem. If you're updating a running container, well that's another issue, you should never do that, a docker container isn't supposed to be modified. Also there's an official image based on busybox which is certainly more lightweight than anything you'd achieve with arch as base system, or even alpine for that matter. Anyway, closing this, there is nothing wrong with the package.

Loading...