RE: Updating the fis-gtm package to V6.2-000

2014-09-26 Thread Shah, Amul
Hi Andreas, Excuse the formatting, I'm using the corporate OWA server which mangles mail like outlook. Look for [amul:2] below. On Wed, Sep 24, 2014 at 09:41:34AM -0400, Amul Shah wrote: > >I also wonder whether you could forward the "spelling-error-in-binary" > >type lintian infos to upstream. >

RE: [fis-gtm] Updating fis-gtm to V6.2-001

2015-01-22 Thread Shah, Amul
Hi Andreas, I apologize in advance for the horrid formatting that Outlook does to mails. From: Amul Shah [amul.s...@fisglobal.com] Sent: Wednesday, January 14, 2015 9:26 AM To: debian-med@lists.debian.org Subject: Re: [fis-gtm] Updating fis-gtm to V6.2-001

RE: [fis-gtm] Updating fis-gtm to V6.2-001

2015-01-26 Thread Shah, Amul
Sent via OWA2010 From: Andreas Tille [andr...@an3as.eu] Sent: Sunday, January 25, 2015 2:47 PM To: debian-med@lists.debian.org Subject: Re: [fis-gtm] Updating fis-gtm to V6.2-001 Hi Amul, On Fri, Jan 23, 2015 at 02:01:17PM -0500, Amul Shah wrote: > > > >

[fis-gtm] FW: GT.M V6.2-002 available

2015-06-09 Thread Shah, Amul
[sorry for the top post, Outlook doesn't do proper quoting] Hi Andreas, I uploaded the latest version of GT.M that we released yesterday. I tagged the version as unstable. Let me know if that was the correct thing to do. As always, thanks for help. Amul From: Bh

RE: [fis-gtm] FW: GT.M V6.2-002A available

2015-06-29 Thread Shah, Amul
Tue, Jun 09, 2015 at 01:19:46PM +0000, Shah, Amul wrote: >> I uploaded the latest version of GT.M that we released yesterday. > Thanks for your work on this. > >> I tagged the version as unstable. Let me know if that was the correct thing >> to do. > Perfect. Unfortun

RE: Any progress with FIS GT.M?

2012-07-02 Thread Shah, Amul
Luis, GT.M Regression Test Suite results are nearly complete. With the exception of a few configuration related issues and tests that need to be fixed, everything is in good shape. The first round of testing hit a latent GT.M bug that is fixed in the upcoming release. I back ported the change w

Re: Naming scheme of fis-gtm binary packages (Was: Bug#1009900: fis-gtm: Multiple CVEs in fis-gtm)

2022-06-17 Thread Shah, Amul
ro) represents a minor feature change in the product - Patch is an alphabet denoting an emergency single change release [amul] GT.M database formats (major version) change infrequently. Inside a database version, GT.M is tested in various upgrade<->downgrade scenarios. Meaning that there should

Re: Naming scheme of fis-gtm binary packages (Was: Bug#1009900: fis-gtm: Multiple CVEs in fis-gtm)

2022-07-11 Thread Shah, Amul
ignore it with respect to the version number? Currently V6.3-014 has a FTBFS #1011722 logged against it. It would be good to get V7.0-003 in the testing stream to close the bug. Thanks, Amul From: Shah, Amul Date: Friday, 06 17, 2022 at 04:04 PM To: Andreas Tille , Debian Med Project List

Re: failed i386 build of fis-gtm 7.0-004-1

2022-10-13 Thread Shah, Amul
Hi Andreas, Thanks for updating to the latest GT.M version! GT.M V7 dropped support for x86 due to the transition to 64bit block IDs. If I could get through the corporate firewall, I would drop i386 from the “Architecture” sections in debian/control. Sorry, about that. Thanks, Amul From: Debia

Novice needs help submitting a bug report

2023-04-03 Thread Shah, Amul
All, I need some guidance. The host where we encountered a bug is sitting in a lab environment with no direct Internet access. Below is the output from reportbug with the print-only option. I am filing a bug against glibc 2.36 due to a bug in memcmp-sse2.S that causes fis-gtm to segfault possib