2233 2012-04-02 22:59:18 +0000 invalid error message "Package version for package ... went backwards" 2012-04-14 11:16:21 +0000 1 1 7 Build System, Metadata & Runtime Other YP Layers layers unspecified x86 Multiple RESOLVED FIXED (1.2) Medium normal 1.2 M4 1 obi lianhao.lu jessica.zhang lianhao.lu meta.layer.watcher meta.watcher sgw --- --- --- oldest_to_newest 19804 0 obi 2012-04-02 22:59:18 +0000 When appending strings to PR, errors like these appear, causing bitbake to return a non-zero exit code: ERROR: Package version for package mtd-utils-dbg went backwards which would break package feeds from (0:1.4.9-r1 to 0:1.4.9-r1-dream1) ERROR: Package version for package mtd-utils-staticdev went backwards which would break package feeds from (0:1.4.9-r1 to 0:1.4.9-r1-dream1) ERROR: Package version for package mtd-utils went backwards which would break package feeds from (0:1.4.9-r1 to 0:1.4.9-r1-dream1) ERROR: Package version for package mtd-utils-doc went backwards which would break package feeds from (0:1.4.9-r1 to 0:1.4.9-r1-dream1) ERROR: Package version for package mtd-utils-dev went backwards which would break package feeds from (0:1.4.9-r1 to 0:1.4.9-r1-dream1) ERROR: Package version for package mtd-utils-locale went backwards which would break package feeds from (0:1.4.9-r1 to 0:1.4.9-r1-dream1) However, the feed isn't broken. Running opkg upgrade works as expected: Upgrading mtd-utils on root from 1.4.9-r1 to 1.4.9-r1-dream1... This also happens with "r1" vs. "r1.1", for example. On Feb 24, I reported this to the OE-Core mailing list. http://comments.gmane.org/gmane.comp.handhelds.openembedded.core/15986 Regards, Andreas 20043 1 lianhao.lu 2012-04-09 03:35:06 +0000 Some initial investigation result at http://lists.linuxtogo.org/pipermail/bitbake-devel/2012-April/002641.html 20126 2 lianhao.lu 2012-04-10 14:18:20 +0000 This bug should be fixed in the following steps: 1. update opkg-compare-versions to match the latest opkg. 2. modify the bitbake bb.utils.vercmp() to match opkg. 3. check bitbake bb.utils.vercmp_string() if it's consistent with opkg. 4. check if the above steps results different build result, especially the rpm build and other openembedded build. 20226 3 lianhao.lu 2012-04-12 09:38:22 +0000 (In reply to comment #2) > This bug should be fixed in the following steps: > > 1. update opkg-compare-versions to match the latest opkg. The patch for opkg-utils upgrade is at http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/commit/?h=llu/opkg-utils&id=bffb0b638d931fb399fdc1d9d455c661a6c141ce, pending for review & merge. We also need a update to opkg-utils' recipe in metadata after the upstream check in the above patch. > 2. modify the bitbake bb.utils.vercmp() to match opkg. The patch is sent out for review/merge at http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/commit/?h=llu/vercmp_bitbake&id=00fda8f184223f4e189786da33d2c7d6b9c617fe. > 3. check bitbake bb.utils.vercmp_string() if it's consistent with opkg. > 4. check if the above steps results different build result, especially the rpm > build and other openembedded build. 20364 4 lianhao.lu 2012-04-14 11:16:21 +0000 This bug is fixed by the following commits: opkg-utils: http://git.yoctoproject.org/cgit/cgit.cgi/opkg-utils/commit/?id=16665959c330b5958c0f0f4624a9ca7f823f98de bitbake: http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=811f7d8ebfe9d55b0244d8284a04b0ef6902adbb meta data: http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=f09a5e176f74985363b65e473ff833801613d25e (contributed by RP)