On Mon, 2015-01-05 at 15:42 -0800, Albert Chu wrote: > On Mon, 2015-01-05 at 23:41 +0100, Jean-Baptiste Denis wrote: > > On 01/05/2015 11:20 PM, Albert Chu wrote: > > > > > Hi Jean, it does appear to be an issue in gcrypt. IPMI 2.0 (i.e. lan20) > > > uses > > > libgcrypt while the default (IPMI 1.5) does not. So if this is in > > > libgcrypt > > > it would make sense. > > > > OK > > > > > What version of libgcrypt is on your system? > > > > 1.6.2 (1.6.2-4+b1 is the specific debian version I'm running). This > > seems to be the last one available upstream. > > > > Are you able to reproduce it on your site with the command line I gave ? > > Haven't been able to reproduce yet. Works with all the gcrypts that I > have around.
I went ahead and built libgcrypt 1.6.2 in a local directory and have got it to reproduce. So I have something to go on. > > What is the best way to report this problem upstream ? > > Maybe ping Debian upstream? Not entirely sure. Will be glad to fix if > there's some minor subtlety in the API usage within FreeIPMI. Just hard > to tell at this moment. > > Al > > > Jean-Baptiste -- Albert Chu [email protected] Computer Scientist High Performance Systems Division Lawrence Livermore National Laboratory _______________________________________________ Freeipmi-devel mailing list [email protected] https://lists.gnu.org/mailman/listinfo/freeipmi-devel
