What | Removed | Added |
---|---|---|
CC | zypp-maintainers@forge.provo.novell.com | |
Flags | needinfo?(zypp-maintainers@forge.provo.novell.com) |
Thanks, Andreas! I see the appdata situation as fixed too. However, it is still worrying that a simple "zypper se calibre" confuses names and summaries between the specfile derived ones and those from the appstream metadata. This should not happen. While I suggest that the current revision of calibre with its fixed appstream metadata be pushed to Leap and Factory, this is something the zypper guys still need to look at for Leap. @zypp-maintainers Could you please take a look at why doing zypper se calibre on openSUSE:Leap:42.1 gives a broken result? For sure it currently has a broken appstream metadata file, but shouldn't the above command return summary and name deduced from the specfile rather than from appdata? As a package management tool, one would expect zypper to prioritise package results in favour of applications, no?