Hi,
I submitted the bug report plus patch to SourceForge also, because I see
no change here at Debian.
https://sourceforge.net/p/unixodbc/bugs/46/
For almost two years, we have a confirmed problem with libodbc1 *and*
the solution, and the patch is just not going into mainline.
I wonder if
Hello,
after more than a year, I am resending this message I already sent in
Feb 2018:
two more weeks have passed, and with the revised patch there was not a
single incident with a truncated INI file.
To make applying the patch easier, find attached a patch against version
2.3.4-1.1,
Hello Steve,
A few more months have now passed, so I thought I'd write a reminder.
If there is anything you still need to include this patch into the
distribution, or if there are open questions, please don't hesitate to
enlist my help.
- Ján
Package: libodbc1
Version: 2.3.4
Severity: critical
Justification: causes serious data loss
Tags: patch upstream
Dear Maintainer,
*** Reporter, please consider answering these questions, where
appropriate ***
* What led up to the situation?
Using unixodbc + freetds as a backend to
Hello Steve,
After a few weeks of tests in the field, the attached, revised patch has
resulted in no further accidentally truncated odbc.ini files.
I have changed four places in the code where I found suspicious "w"
options to uo_fopen(). In these four places, I changed the "w" option to
Hello Steve,
two more weeks have passed, and with the revised patch there was not a
single incident with a truncated INI file.
To make applying the patch easier, find attached a patch against version
2.3.4-1.1, which is currently in "testing".
If there is anything else I can help with,
Hello Steve,
Since I last contacted you on 2 Feb 2018 we have no further problems
with truncated odbc.ini files using the patch I submitted.
The patch seems to be working perfectly.
Is there anything further that I can contribute to help get this patch
into the Debian package?
As always,
7 matches
Mail list logo
