I assume the first one may be unavoidable and likely produced by qmake, which is instructed to copy the source directory icons to $buildroot/usr/share/filecase/, but also (where?) to copy the app icon to /usr/share/icons/hicolor/86x86/apps/.
The only thing one may check in the source tree is, if /usr/share/filecase/icons/filecase.png is directly used; still I have no idea where to put it in the first place, if it only needs to be copied to /usr/share/icons/hicolor/86x86/apps/.
The latter three are "real duplicates" and may be substituted by symbolic links, but supposedly the real resolution is to only use one of the two names throughout FileCase's source tree.
Although I am not sure, if one of each in the pairs exec.png / setting.png and document.png / txt.png is meant as a placeholder for a better suited icon (i.e. better depicting what it stands for): Only to look up the places at which these icon pairs are used will tell for sure.
rpmlintas employed by the Sailfish-OBS criticises (just warnings, no errors):I assume the first one may be unavoidable and likely produced by
qmake, which is instructed to copy the source directoryiconsto$buildroot/usr/share/filecase/, but also (where?) to copy the app icon to/usr/share/icons/hicolor/86x86/apps/. The only thing one may check in the source tree is, if/usr/share/filecase/icons/filecase.pngis directly used; still I have no idea where to put it in the first place, if it only needs to be copied to/usr/share/icons/hicolor/86x86/apps/.The latter three are "real duplicates" and may be substituted by symbolic links, but supposedly the real resolution is to only use one of the two names throughout FileCase's source tree. Although I am not sure, if one of each in the pairs
exec.png/setting.pnganddocument.png/txt.pngis meant as a placeholder for a better suited icon (i.e. better depicting what it stands for): Only to look up the places at which these icon pairs are used will tell for sure.