Re: [fis-gtm] Updating fis-gtm to V6.2-001
Hi Andreas,
On 01/14/15 02:12, Andreas Tille wrote:
Hi Amul,
On Tue, Jan 13, 2015 at 04:40:28PM -0500, Amul Shah wrote:
Last month FIS released GT.M V6.2-001. I have staged the changes for
upload. I will upload once I fix one minor issue with the gtmprofile
environment script.
Fine. Just tell me once you consider it ready for sponsering.
[amul:2] Will do thanks.
I was unable to reproduce the
bug using the package that I built on my workstation, but I was able
to reproduce it using the package that I downloaded from
https://urldefense.proofpoint.com/v2/url?u=https-3A__packages.debian.org_sid_fis-2Dgtm-2D6.2-2D000&d=AAIBAg&c=3BfiSO86x5iKjpl2b39jud9R1NrKYqPq2js90dwBswk&r=9ssj4QMqXvXerR0OPzrgsqFDldUsqMEK5X4uhRXsy2Q&m=TfDgPzIN1Hni668ZWcVy38TkfHzQFZuozR9w69C6blo&s=IKPE41foFP0W3Cs_636umZdsGu27MoR0FjcLqxAWWO0&e= .
How did you build the package on your workstation? If you were using
git-buildpackage in connection with pbuilder (as suggested in Debian Med
policy) it should be basically identically to the downloaded package. I
guess / hope that the solution for the bug might be hidden behind this
question - otherwise I have no idea what to do.
I checked the build logs available on
https://urldefense.proofpoint.com/v2/url?u=https-3A__tracker.debian.org_pkg_fis-2Dgtm&d=AAIBAg&c=3BfiSO86x5iKjpl2b39jud9R1NrKYqPq2js90dwBswk&r=9ssj4QMqXvXerR0OPzrgsqFDldUsqMEK5X4uhRXsy2Q&m=TfDgPzIN1Hni668ZWcVy38TkfHzQFZuozR9w69C6blo&s=ymoCTnfWgU-dY-r2mkTnVhnYhw0qng6uWb13e2eQS-M&e= , but didn't see anything
amiss. What is the usual debugging pattern for such an issue?
I personally have not faced such an issue before so I can not come up
with a "usual pattern". It might help to create a minimal chroot
environment and try to rebuild and run there. As said above please
explain how exactly you created your local package. Perhaps you can
run ldd against the binaries inside the package to see against what
these are linked?
[amul:2] Uh-oh, I used git-buildpackage. I have a clean non-GT.M development system at home to try the package build. If that
fails, I will create the minimal chroot like you suggested.
thanks,
Amul
_____________
The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you.
Reply to: