eom-transform.c:135:15: warning: using integer absolute value function ‘abs’ when argument is of floating point type ‘gdouble’ {aka ‘double’} [-Wabsolute-value]
eom-transform.c:136:16: warning: using integer absolute value function ‘abs’ when argument is of floating point type ‘gdouble’ {aka ‘double’} [-Wabsolute-value]

egg-toolbars-model.h:113:10: warning: redundant redeclaration of ‘egg_tb_model_flags_get_type’ [-Wredundant-decls]
eggtypebuiltins.h:13:23: warning: redundant redeclaration of ‘egg_tb_model_flags_get_type’ [-Wredundant-decls]
eom-thumb-view.c:91:40: warning: redundant redeclaration of ‘eom_thumb_view_init’ [-Wredundant-decls]

eom-window.c:3153:20: warning: variable ‘priv’ set but not used [-Wunused-but-set-variable]

This is mostly useful for PNG images for now but could also help
with TIFF files in the future. LittleCMS will still ignore the
alpha channel, so this should be harmless.

https://bugzilla.gnome.org/show_bug.cgi?id=725357

upstream commit:
https://gitlab.gnome.org/GNOME/eog/commit/80b536bc

The values used for sRGB in cHRM and gAMA chunks do not compute to a
profile that exactly matches the built-in profile. Catch this case and
use the built-in profile instead to avoid color differences.

upstream commit:
https://gitlab.gnome.org/GNOME/eog/commit/9589430c

It's more likely that such an image had a (stripped) sRGB profile or chunk.
And thus rather than trying to build a profile from only half the necessary
information, eom should not.

https://bugzilla.gnome.org/show_bug.cgi?id=725359

upstream commit:
https://gitlab.gnome.org/GNOME/eog/commit/78c0153e