On Thu, Jun 09, 2005 at 04:18:48PM +0000, Uwe Brauer wrote: > >>>>> "Steve" == Steve Langasek <[EMAIL PROTECTED]> writes:
> Steve> On Wed, Jun 08, 2005 at 07:39:15PM +0000, Uwe Brauer wrote: > >> >>>>> "Steve" == Steve Langasek <[EMAIL PROTECTED]> writes: > Steve> Can you elaborate on what you mean by "format" here? If > Steve> you can give me a sample database schema, I can try to > Steve> reproduce the problem. > I will, right now it seems that the macro does not work any more, so > my tables continue to be _not_ editable Right, this does seem to be trivially reproducible in sarge. It looks like there's been a change in OpenOffice that triggered it, rather than a regression in libmyodbc itself; even installing the woody version of libmyodbc doesn't get me read/write table access with the sarge version of OOo. > >> I tried to install 2.50 from the oldstable release but it did not > >> work. > Steve> And what problem did 2.50 have? > >> apt-get install -t oldstable libmyodb installed 3.51.06 > Steve> I don't know what you're saying here; you just said that > Steve> you installed 2.50 from oldstable, which is the correct > Steve> version in woody -- I don't see how this commandline could > Steve> ever have installed 3.51.06 for you. 3.51.06 is no longer > Steve> in the archive. > Sorry, what I meant, I could *NOT* install 2.50 from oldstable > the command > apt-get install -t oldstable libmyodb > installed version 3.51.09 sorry for the typo. # apt-get install libmyodbc=2.50.39-3 works for me. It appears that the Release file for woody still says "stable" instead of "oldstable", so selecting by release doesn't work currently. > >> Couldn't you move that version to stable, > Steve> Well, no; first because it doesn't exist anywhere in the > Steve> archive, and second because the policy for updates to > Steve> stable releases prohibits it. This bug, if it truly > Steve> renders MyODBC unusable with the current OOo packages, is > Steve> irritating, but it doesn't make the package unusable for > Steve> all purposes. > Well and what is about 2.50 to stable then, it is irritation to have > *no* working version neither in woody, sarge nor sid. Equally infeasible given the stable release manager's policy on updates. Also wouldn't help, as noted above. And downgrading to anything earlier than 3.51.09 would also break compatibility with MySQL server 4.1. -- Steve Langasek postmodern programmer
signature.asc
Description: Digital signature
