debian/ubuntu packages have wrong time stamps

[ggzengel]

Every file from 3.5.3 and 3.6.0 have time stamps from 2017-08-21 22:51

# dpkg -c emby-server-deb_3.5.3.0_amd64.deb | grep -v "2017-08-21 22:51" | wc
      0       0       0

# dpkg -c emby-server-deb_3.5.3.0_amd64.deb | head -n 15
drwxr-xr-x root/root         0 2017-08-21 22:51 ./
drwxr-xr-x root/root         0 2017-08-21 22:51 ./etc/
-rw-r--r-- root/root        23 2017-08-21 22:51 ./etc/emby-server.conf
drwxr-xr-x root/root         0 2017-08-21 22:51 ./etc/firewalld/
drwxr-xr-x root/root         0 2017-08-21 22:51 ./etc/firewalld/services/
-rw-r--r-- root/root       354 2017-08-21 22:51 ./etc/firewalld/services/emby-server.xml
drwxr-xr-x root/root         0 2017-08-21 22:51 ./etc/init/
-rw-r--r-- root/root       244 2017-08-21 22:51 ./etc/init/emby-server.conf
drwxr-xr-x root/root         0 2017-08-21 22:51 ./opt/
drwxr-xr-x root/root         0 2017-08-21 22:51 ./opt/emby-server/
drwxr-xr-x root/root         0 2017-08-21 22:51 ./opt/emby-server/bin/
-rwxr-xr-x root/root       647 2017-08-21 22:51 ./opt/emby-server/bin/emby-server
-rwxr-xr-x root/root    268416 2017-08-21 22:51 ./opt/emby-server/bin/ffmpeg
-rwxr-xr-x root/root    153752 2017-08-21 22:51 ./opt/emby-server/bin/ffprobe
drwxr-xr-x root/root         0 2017-08-21 22:51 ./opt/emby-server/etc/

[LukePulverenti]

Hi, we don't believe there's an issue here. mtime is bumped when we make a change to the files, it just means they haven't changed since then.

[LukePulverenti]

Thanks for reporting.

[ggzengel]

How do you distribute your new version if no file is changing?

[ggzengel]

I wrote every file

[ggzengel]

Need more info?
3.6.0.74 released at 2017?

$ ls -la control/control
-rw-r--r-- 1 ggz ggz 269 Aug 22 2017 control/control

$ cat control/control
Package: emby-server
Version: 3.6.0.74
Architecture: amd64
Maintainer: Emby LLC apps@emby.media
Installed-Size: 222268
Depends: libc6 (>= 2.17)
Section: misc
Priority: optional
Description: Emby Server is a personal media server with apps on just about every device.

[LukePulverenti]

Hi, yes it looks like you're right. I'm re-opening this ticket for tracking purposes. Is this causing you any problem?

[ggzengel]

Thanks for reopening.

I did investigate the filesystem while migrating to a new server and didn't find the "new" release files.
There is no actual problem but perhaps it breaks some expectations with backup or install scripts.