Comment # 5 on bug 990425 from Atri Bhattacharya

(In reply to Cor Blom from comment #4)
> I can confirm the bug was introduced with the last Leap update. With update
> repo disabled and the previous version installed, zypper se is working as
> with other applications.
> 

I still don't get why. The appdata changes should not affect the specfile
descriptions of calibre, which I did not touch! If it does that's a zypper
problem. zypper se is supposed to show the specfile description corresponding
to the package, not confuse it with appdata description. Two distinct things.

> 
> (In reply to Atri Bhattacharya from comment #3)
> > 2. zypper se calibre
> > Loading repository data...
> > Reading installed packages...
> > 
> > S | Name    | Summary                      | Type   
> > --+---------+------------------------------+--------
> >   | calibre | EBook Management Application | package
> > 
> 
> Do I understand this correctly that zypper se on TW works correclty with
> calibre? If so, we can revert the latest change and submit 2.62 again
> without the app store change. That is, if we consider this bug serious
> enough. I'm prepared to do the work then.

Yes it works perfectly, but please don't revert this change in Leap either. The
"fix" should not be to ship broken appstream metadata, and the previous appdata
was broken. Instead, what I can do is try to fix the descr txt in appdata
(which is currently blank), but my commit did not change that either. It has
always been so.

I think it might be a rather major bug for the zypper guys to look into.