[Stephen Gallagher] > I don't want to be rude, but there's not a lot I can do to deal with > a bug related to distro-specific packaging issues. I don't really > have the spare cycles to reproduce this on an unfamiliar platform.
Sure. You asked for differences in the environment, and I tried to answer. :) > If you or the original reporter can manage to reproduce the original > upgrade problem (and from other comments in this thread, it sounds like > you cannot), then there's not a lot I can do to help. > > If you can prove that the same misbehavior happens consistently on > upgrades from 1.0.5 to 1.2.0 in the Debian package (and then ideally > provide me with access to a machine/VM to investigate) I'll happily do so. I have not had time to look into this, so I do not know if I will be able to reproduce it or not. :) > Also, regarding 1.0.2 vs. 1.0.5, there are no functional differences on > the platform in question. (All of the changes from 1.0.2 to 1.0.5 were > for support of the ARM platform, and then to handle some missing license > information for compliance reasons) So there should be no reason that > this has anything to do with it. > Good to hear. > What version of libldb is in use in Debian (both before and after the > upgrade process)? If I read <URL:http://packages.qa.debian.org/l/ldb.html> correct, version 1:0.9.10~git20100203-1 is the one in Squeeze and Sid in this period. Happy hacking, -- Petter Reinholdtsen -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
