Incorrect sorting produces bogus warning when running build-source

[Andreas Hasenack]

Hi,

I was building a source package out of the trusty branch of libvirt and got this sort of "warning":
(trusty-libvirt-apparmor-cache-1707400)andreas@nsn7:~/git/packages/libvirt$ git ubuntu build-source --sign
08/01/2017 12:14:50 - INFO:New upstream version detected (1.2.2) which is after the last published upstream version (1.2.16). Falling through to just calling dpkg-buildpackage.

(trusty-libvirt-apparmor-cache-1707400)andreas@nsn7:~/git/packages/libvirt$ head debian/changelog
libvirt (1.2.2-0ubuntu13.1.21) trusty; urgency=medium

  * d/libvirt-bin.postinst: call apparmor_parser with options to
    ignore the apparmor cache and rebuild it, otherwise old apparmor
    rules are used and this might break upgrades (LP: #1707400)

 -- Andreas Hasenack <email address hidden> Tue, 01 Aug 2017 11:58:38 -0300

libvirt (1.2.2-0ubuntu13.1.20) trusty; urgency=medium

It looks like it's doing ascii sorting and decided that 1.2.2 is higher than 1.2.16 or something like that.

Regardless, the source package was created correctly as far as I can see.