Skip to content

server: Consider 'unknown' to be an arbitrarily new version#42

Merged
swinslow merged 1 commit intofossology:masterfrom
smcv:treat-unknown-as-new-version
May 24, 2022
Merged

server: Consider 'unknown' to be an arbitrarily new version#42
swinslow merged 1 commit intofossology:masterfrom
smcv:treat-unknown-as-new-version

Conversation

@smcv
Copy link
Copy Markdown
Contributor

@smcv smcv commented Jan 17, 2022

Recent Docker container images from
https://hub.docker.com/r/fossology/fossology show up as version
'unknown', which is not comparable. It seems like the best we can do
here is to assume that 'unknown' means a modern version.

Resolves: #41

@smcv
Copy link
Copy Markdown
Contributor Author

smcv commented Jan 17, 2022

This is really more of a workaround than a solution, but it seems better than nothing. (Testing it now.)

Recent Docker container images from
https://hub.docker.com/r/fossology/fossology show up as version
'unknown', which is not comparable. It seems like the best we can do
here is to assume that 'unknown' means a modern version.

Resolves: fossology#41
Signed-off-by: Simon McVittie <smcv@collabora.com>
@smcv smcv force-pushed the treat-unknown-as-new-version branch from 912419d to 7482145 Compare January 17, 2022 15:37
@smcv smcv marked this pull request as ready for review January 17, 2022 17:46
@swinslow
Copy link
Copy Markdown
Contributor

Thanks @smcv! (And apologies for the long delay in circling back on this.)

I think you're right, this seems like the best of the options for handling this unideal situation. I'm merging this now -- thank you!

@swinslow swinslow merged commit 75b9b29 into fossology:master May 24, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Can't identify whether server version 'unknown' is recent

2 participants