On 06/03/2010 02:18 PM, Petter Reinholdtsen wrote:
[Stephen Gallagher]
I had my QA team attempt to reproduce this problem and they were
unable to do so. Please examine the process below and let us know if
there's anything about your environment that differs here.
One obvious difference is that he is using the Debian packages, and
started with 1.0.5 and then went to 1.2.0. The 1.0.5 version is in
Debian/Squeeze, and version 1.2.0 is in unstable. Perhaps there are
some Debian specific library issues? Let me know if you need help
installing Debian.
I have no idea what went wrong, but thought it best to state the
obvious.
Happy hacking,
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.
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.
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.
What version of libldb is in use in Debian (both before and after the
upgrade process)?
--
Stephen Gallagher
RHCE 804006346421761
Delivering value year after year.
Red Hat ranks #1 in value among software vendors.
http://www.redhat.com/promo/vendor/
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
