Comment 2 for bug 1849972

I saw something similar a while back, and had a conversation with juliank about it:
out 09 11:22:08 <andreas> juliank: but apt list --upgradable is showing:
out 09 11:22:12 <andreas> apport/trusty-updates,trusty-security,now 2.14.1-0ubuntu3.29 all [installed,upgradable to: 2.14.1-0ubuntu3.29]
out 09 11:22:19 <andreas> i.e. upgradable to the same version
(...)
out 09 11:36:04 <juliank> andreas: this is a display bug in apt list, https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=753297
out 09 11:36:33 <juliank> Caused by weird behavior in the old pinning implementation, the fix for that is more like a workaround
out 09 11:40:20 <juliank> trusty's pinning implementation is not very good
out 09 11:41:17 <juliank> * apt-pkg/cachefile.cc:
out 09 11:41:20 <juliank> - ensure we have a Policy in CacheFile.BuildDepCache()
out 09 11:41:25 <juliank> maybe that's all that's needed really
out 09 11:49:19 <juliank> andreas: so we could fix that in ESM I guess, it's inserting two lines in cachefile.cc: https://paste.ubuntu.com/p/5FsRtcySx8/
out 09 11:50:23 <juliank> the problem was that pkgDepCache was called with Policy == NULL because Policy was never initialized
out 09 11:50:36 <juliank> other releases are not affected
out 09 11:52:03 <juliank> this caused a mismatch, because depcache never saw the policy and calculated that apport is upgradable to esm
out 09 11:52:17 <juliank> but then we print the candidate version based on policy, and it's the same one :D
out 09 12:00:21 * fginther has quit (Ping timeout: 121 seconds)
out 09 12:06:18 * fginther (fginther@50-82-191-167.client.mchsi.com) has joined
out 09 12:07:26 <juliank> andreas: Created https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1847496 but I'm not sure about the procedure here