Your message dated Mon, 1 Nov 2021 13:16:13 +0100
with message-id <420fcb72-faa8-7b5f-fc51-4473ec606...@debian.org>
and subject line Closing bug
has caused the Debian Bug report #753666,
regarding sqlalchemy 0.9.x broke out parameters in postgresql stored procedures
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
753666: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=753666
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
package: python-sqlalchemy
version: 0.9.6-1
I'm packaging gnukhata and it uses out parameters in postgresql stored
procedures. It is working well with sqlalchemy 0.7.x but it fails in
0.9.x hence I cannot upload the package to unstable. I have made a
personal repo of the package which you can try
http://people.debian.org/~praveen/gnukhata
we have reported it upstream
https://bitbucket.org/zzzeek/sqlalchemy/issue/3103/nosuchcolumnerror-could-not-locate-column
but they are not very helpful (in one comment they even said - "Note
that there has never been support for this (OUT parameters
specifically). If your function worked on 0.7 with OUT parameters, it
was a cooincidence.").
In my repo, I have rebuilt sqlalchemy 0.7.8 on unstable as
python-sqlalchemy7 and added it as a dependency.
It would be nice if you can help me solve this issue. We'll need to
change either gnukhata or sqlalchemy.
Thanks
praveen
signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Hi,
This bug concerns oldoldoldstable so I'm closing it. Hopefully, this
isn't relevant anymore.
Cheers,
Thomas Goirand (zigo)
--- End Message ---
