Greetings, I built a package feed based on Poky Nanbield (tip of the branch) using these settings: MACHINE = "qemux86-64" EXTRA_IMAGE_FEATURES += "package-management" DISTRO = "poky-altcfg" PACKAGE_CLASSES = "package_deb" PRSERV_HOST = "localhost:0" INHERIT += "buildhistory" BUILDHISTORY_COMMIT = "1" Then I built an image on another based on Poky Nanbield 4.3.1 using these settings: MACHINE = "qemux86-64" EXTRA_IMAGE_FEATURES += "package-management" DISTRO = "poky-altcfg" PACKAGE_CLASSES = "package_deb" PACKAGE_FEED_URIS = "http://192.168.1.20:8000" PRSERV_HOST = "localhost:0" INHERIT += "buildhistory" BUILDHISTORY_COMMIT = "1" Then, if I start this image through QEMU and run: root@qemux86-64:~# apt update root@qemux86-64:~# apt list --upgradable Listing... Done acl/unknown 2.3.1-r0.0 amd64 [upgradable from: 2.3.1-r0.0] apt/unknown 2.6.1-r0.0 amd64 [upgradable from: 2.6.1-r0.0] ... It wants to upgrade all packages though the package version and revision are exactly the same! I ran the same experiment with "package_ipk" and "package_rpm", and in both cases, only the packages with a higher version need upgrading (apparently the same number in both cases, about 12 of them). I'm lacking time to investigate this right now, and it's not exactly within the binary distro project deliverables, but I'll be happy to make quick tests if someone has ideas or patches, or to investigate this further once the binary distro project deliverables are available.
Bulk move of 5.1 M4 to 5.2 M2 as approved by AlexB.
Bulk move of bugs I am assigned to from Milestone 5.2M4 to 5.3M1.
Bulk move of unassigned 6.0-M* bugs to 6.1-M2.