Here is the output of the command on a vivid installation, that has not been updated since the middle of December 2014 and where the regression was not present yet:
$ sudo apt-cache policy unity unity: Installed: 7.3.1+15.04.20141128-0ubuntu1 Candidate: 7.3.1+15.04.20150115-0ubuntu1 Version table: 7.3.1+15.04.20150115-0ubuntu1 0 500 http://ubuntu.mirror.root.lu/ubuntu/ vivid/main amd64 Packages *** 7.3.1+15.04.20141128-0ubuntu1 0 100 /var/lib/dpkg/status
And here the output of the command on my uptodate vivid installation having the regression:
$ sudo apt-cache policy unity unity: Installed: 7.3.1+15.04.20150115-0ubuntu1 Candidate: 7.3.1+15.04.20150115-0ubuntu1 Version table: *** 7.3.1+15.04.20150115-0ubuntu1 0 500 http://ubuntu.mirror.root.lu/ubuntu/ vivid/main amd64 Packages 100 /var/lib/dpkg/status
As far as I understand, the regression happened somewhere between the two versions.
Here is the output of the command on a vivid installation, that has not been updated since the middle of December 2014 and where the regression was not present yet:
$ sudo apt-cache policy unity 04.20141128- 0ubuntu1 04.20150115- 0ubuntu1 3.1+15. 04.20150115- 0ubuntu1 0 ubuntu. mirror. root.lu/ ubuntu/ vivid/main amd64 Packages 04.20141128- 0ubuntu1 0 dpkg/status
unity:
Installed: 7.3.1+15.
Candidate: 7.3.1+15.
Version table:
7.
500 http://
*** 7.3.1+15.
100 /var/lib/
And here the output of the command on my uptodate vivid installation having the regression:
$ sudo apt-cache policy unity 04.20150115- 0ubuntu1 04.20150115- 0ubuntu1 04.20150115- 0ubuntu1 0 ubuntu. mirror. root.lu/ ubuntu/ vivid/main amd64 Packages dpkg/status
unity:
Installed: 7.3.1+15.
Candidate: 7.3.1+15.
Version table:
*** 7.3.1+15.
500 http://
100 /var/lib/
As far as I understand, the regression happened somewhere between the two versions.