Hi Gary, Sorry for the late reply. It could be possible that the packages index files are not re-generated when you run 'bitbake package-index'. Depending on the PM you use, can you please try to remove the index files in all the directories in tmp/deploy/(ipk|deb|rpm)? So, before "Rebuild package database (bitbake package-index)" step, remove the index files.
Does it work after that? laurentiu On Mon, Apr 14, 2014 at 09:47:34AM -0600, Gary Thomas wrote: > I'm using a local PR server and for the most part, it works great! > No more messing about with PR and PRINC and ... > > However, I have a situation where it doesn't do what I expect. > Here's my scenario: > * Build some package X > * Rebuild package database (bitbake package-index) > * Update package database on target > * Install package X on target > * Update the RRECOMMENDS_${PN} in the recipe and rebuild. > I can see that the package is updated - everything from > do_package onwards is updated. > * Rebuild package database (bitbake package-index) > * Update package database on target > * Try to install/update package X. I'm told that it is up > to date. > > I can see that the package _was_ updated on the build host even > if the PR value was not changed because if I remove package X > and reinstall it, the new RRECOMMENDS_${PN} packages are also > being installed. > > Am I missing something? Shouldn't this work and the PR value > be bumped by the PR server, even if all that happened was the > list of recommendations was changed? > > -- > ------------------------------------------------------------ > Gary Thomas | Consulting for the > MLB Associates | Embedded world > ------------------------------------------------------------ > -- > _______________________________________________ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto -- _______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto