The upstream updates are not really ones

[Sebastien Bacher]

There is a new version available

[Till Kamppeter (till-kamppeter)]

Note that there is a cron job on www.openprinting.org which every day generates a tarball with the date of the day as the version number but there are no new commits to the GIT repository every day, leading to certain tarballs being identical.

The last commit was on Aug 19, 2019:

https://github.com/OpenPrinting/foomatic-db/commits/master

So the 20190820 tarball currently used for the Ubuntu and Debian packages is up to date.

[Sebastien Bacher (seb128)]

Thanks Till, that feels like a suboptimal process. What is the recommended way for distributor to know when they should do an update if it's not by watching out for new tarballs?

[Till Kamppeter (till-kamppeter)]

Currently it is the GIT repository, to check whether there is some commit newer than the date of the packaged version.

We need some improvement in the cron script to only generate a tarball when there is a change. Do you get a "daily nag" of a new foomatic-db version every day now?

[Sebastien Bacher (seb128)]

No nagging but our versions page lists is as outdated since the package is older than the current upstream 'release', I'm going to hack that around and remove foomatic-db from the list saying that upstream doesn't do release anymore and tarballs are just daily snapshots

[Sebastien Bacher (seb128)]

@Till, I'm reopening that bug and keeping it open to document that those are buggy tarballs/not to package, that way our tools stop nagging about an update being available to package