On Oct 22, 2012, at 10:21 AM, Elan Ruusamäe <g...@pld-linux.org> wrote:
> On 22.10.2012 04:46, Jeffrey Johnson wrote: >> There are too may possible causes to hazard a guess, including >> a well documented difference in behavior detected by Mancoosi years >> ago, and also identifying precisely what metadata (and >> what rpm version was used to build all the packages). > > rpm version used to build the package > (http://carme.pld-linux.org/~glen/ntpd-4.2.6p5-5.i686.rpm): > > # rpm -q --yaml ntpd-4.2.6p5-5.i686.rpm -p | grep Rpmversion > Rpmversion: 4.5 > > that package installs fine on other host. i'm suspecting local db error. > anything else to dig from there? > If rpm/os software are identical, and *.rpm input is the same, then I would suspect the local db as well. One does have to ensure that the installed package manifests are "sufficiently similar" (and that might mean "identical manifest" for a database retrieval loop error). For a suspected database error in the Conflictname index, then comparing the outputs with /usr/lib/rpm/macros:%_dbi_config_3_Conflictname %{_dbi_btconfig} %{?_bt_dupsort} debug may be informative. The access patterns SHOULD be similar. 73 de Jeff _______________________________________________ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en