Menu
▾
▴
pythondialog-users
|
From: Jakub W. <jak...@gm...> - 2015-04-02 10:53:12
|
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
While working on the Let's Encrypt [1] client we have hit the
following python2-pythondialog bug [2] on Debian squeeze (tested on
digitalocean droplet):
(venv)root@le-squeeze:/tmp# pip install python2-pythondialog
Downloading/unpacking python2-pythondialog
Downloading python2-pythondialog-3.0.1.tar.bz2 (76Kb): 76Kb downloaded
Running setup.py egg_info for package python2-pythondialog
No .git directory, using the 'ChangeLog' file as is.
Installing collected packages: python2-pythondialog
Running setup.py install for python2-pythondialog
No .git directory, using the 'ChangeLog' file as is.
Successfully installed python2-pythondialog
Cleaning up...
(venv)root@le-squeeze:/tmp# python -c 'import dialog; dialog.Dialog()'
Version: 1.1-20100428
Traceback (most recent call last):
File "<string>", line 1, in <module>
File "/tmp/venv/lib/python2.6/site-packages/dialog.py", line 1366, in __init__
self.backend_version())
File "/tmp/venv/lib/python2.6/site-packages/dialog.py", line 2028, in backend_version
"{1!r}".format(self._dialog_prg, output))
dialog.UnableToRetrieveBackendVersion
Please note that the version string is printed on the terminal. I have
checked (using pdb) that "output" on line 2028 is set to empty string:
''. More debug output:
(venv)root@le-squeeze:/tmp# dialog --print-version 2>/dev/null
Version: 1.1-20100428
We don't have this problem on neither Debian wheezy nor Ubuntu 14.04
nor Ubuntu 14.10.
BTW I wanted to use sourceforge bug tracker [3] to report this
problem, but it says: "To create a new ticket, you must be authorized
by the project admin.".
[1] https://letsencrypt.org
[2] https://github.com/letsencrypt/lets-encrypt-preview/issues/280
[3] http://sourceforge.net/p/pythondialog/bugs/
- --
Your's virtually,
Jakub Warmuz
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQJ8BAEBCgBmBQJVHR90XxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRGMzBGQ0QzNkIzOTBBOTMwODc1OTAzREYy
QTdCQUQzQTQ4OUI1MkVBAAoJECp7rTpIm1LqSBIP/34LRqVn0Ij9Ieml07zYvpB/
ocVVCRMF/j7ghH/u1zDARNXstmPH3zN/teQW+GJpml6LTe248r519/6AJq/PcR8v
lIdODhrISp78ULuaNU12mvVkFABB5yiVUu9d8WH5wKL/30jn5vUBnp+ej59Ywfx9
7OTk8EcFhRLNBNCJHyxEMTLYuQqzkXxhHZE03o8B7JsK1NzCHwPB9XoDaOE0Nj3q
Zs3yVfHMiPIbUJDmXREgFdg7tqf2LC6DJYC9IhvIWFllJ0zfMvBNqarG9b1NGQha
q9H8Bsp+QFKRPOZhxmPrSuUFMvGNoKAMJh98kSLO4itq6TVEQ/KIm2t+6RAdKvwb
9jPZpSgJkqlLPbifQ4XNPp/jeDBzbPYsTB7Bzw6QZTA2mmRHjQKm+YDhAHuGvqix
X26qOXd9hua7gHzihQukldHBLzW7L13rLWZJsig6lv/oBlKKfQfb7OseUboqrZt1
SfFT8z00nS6bL6Jz2KU80efcF8Roq3Rv0DqQKjjzeTJA9CMl0gXB2zryFDv258le
qTZ+kFkz7W9cn8z3GSlIipXVNwj6nxEy3Biz3Hg9Rrb+c4Ma7fabvhssDeT/C5jd
mN0JhaB3VYcrYu2tqHamf2oTnfru9fYhlaAx1gWhYtoxj9b498CMkuKP/wvJZGn2
mqtB5o/h2YOQxX2YUMOn
=EHS8
-----END PGP SIGNATURE-----
|
|
From: Florent R. <f.r...@fr...> - 2015-04-02 14:11:00
|
Hello, Thanks for your detailed report. Jakub Warmuz <jak...@gm...> wrote: > While working on the Let's Encrypt [1] client we have hit the > following python2-pythondialog bug [2] on Debian squeeze (tested on > digitalocean droplet): [...] > Please note that the version string is printed on the terminal. I have > checked (using pdb) that "output" on line 2028 is set to empty string: > ''. More debug output: > > (venv)root@le-squeeze:/tmp# dialog --print-version 2>/dev/null > Version: 1.1-20100428 Yup, this must be the root of the problem. Normally, dialog prints the version on stderr, but it seems that old or buggy versions print it on stdout instead. The cleanest workaround would be to manage to tell dialog to print the version on stderr. What is the output of the following command on the affected system? dialog --print-version --stderr >/dev/null > We don't have this problem on neither Debian wheezy nor Ubuntu 14.04 > nor Ubuntu 14.10. OK. > BTW I wanted to use sourceforge bug tracker [3] to report this > problem, but it says: "To create a new ticket, you must be authorized > by the project admin.". Ah, thank you for reporting this! Silly permission problem for the tracker. I thought it was working since there were a few bug reports in it when I took over in 2013. Who knows how long it has been broken?.. Regards -- Florent |
|
From: Jakub W. <jak...@gm...> - 2015-04-02 14:45:59
|
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
On Thu, Apr 02, 2015 at 04:03:20PM +0200, Florent Rougon wrote:
> Yup, this must be the root of the problem. Normally, dialog prints the
> version on stderr, but it seems that old or buggy versions print it on
> stdout instead. The cleanest workaround would be to manage to tell
> dialog to print the version on stderr. What is the output of the
> following command on the affected system?
>
> dialog --print-version --stderr >/dev/null
>
Debian squeeze (afftected, deb version: 1.1-20100428-1):
root@le-squeeze:~# dialog --print-version --stderr >/dev/null
root@le-squeeze:~# dialog --print-version --stderr >/dev/null | wc
0 0 0
and for wheezy (unaffected, deb version: 1.1-20120215-2):
root@le-wheezy-64:~# dialog --print-version --stderr >/dev/null
Version: 1.1-20120215
I'm afraid --stderr in squeeze is broken as well :(
- --
Kuba
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQJ8BAEBCgBmBQJVHVYVXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRGMzBGQ0QzNkIzOTBBOTMwODc1OTAzREYy
QTdCQUQzQTQ4OUI1MkVBAAoJECp7rTpIm1Lq8+YP/Aqo7+MAgAAF13fhbTGvz/Mc
LCsW0k2VrBzkwHrCZNXnHxDCl8eOkUTG+S/3+mnBBmtygIcQqb4rb3Wc0z8/Utu0
rOXUwnTvoa/jn33DYrOmxmZo+DgC8JFfLdjyEdgTelRrYXSzOkWKrfFyMlKdENUc
aBHdP6F7pKX+eHowbrM1EYvthPufYUHM/00scS1AxxZPA5HvTg6FvVwk82o25MGp
yNIoiP6uRT5XvelCBOQ+raHWhYTPRq3Ljb6dNohAZsmzI88r2yIrgPt0jXZ6DbpL
f1T3RlEtaONTfcChdP4H9ySINSAY++mgYXayC1mZCH/fJ3ZycMi1FwFVf6i+YK+l
UzhkDgZkifZW8pQf4RZ6FCD0FFQBCeBOLHd+nqYGI3Xry3VjjdJ2La6hNQJtt4Bx
9Zqq74XKUVPIiSXf/UO6X3L4GghEXK1Z7kwtGo+YLEYI0xEJNbfHlCVOw4Pr+92h
IbDSZZG5THZC1+eEOvocCHCJPxmuSKYaKeUtO6ho6gd4YiDIGtxSCzIJ/qN7DAUd
sqQHZMLDc3Cv++GdzIGWGIvgtVegv0DmjDW0Dk7vVXT6sx3xYRQkkryiAMzAI5Fq
ae7jRuzFYoKt0Qe5T/tiRf76T0Rs+NBb9zs0fG1nBxbIDm5VnF1BEkCWS5SZu26R
l/AskZm01roAX1uPWmoA
=DVYB
-----END PGP SIGNATURE-----
|
|
From: Florent R. <f.r...@fr...> - 2015-04-03 21:09:03
|
Hello, Jakub Warmuz <jak...@gm...> wrote: > Debian squeeze (afftected, deb version: 1.1-20100428-1): > > root@le-squeeze:~# dialog --print-version --stderr >/dev/null > root@le-squeeze:~# dialog --print-version --stderr >/dev/null | wc > 0 0 0 > > and for wheezy (unaffected, deb version: 1.1-20120215-2): > > root@le-wheezy-64:~# dialog --print-version --stderr >/dev/null > Version: 1.1-20120215 > > I'm afraid --stderr in squeeze is broken as well :( Okay. I've pushed a workaround that works on squeeze with Python 3.1, along with a few other fixes for bugs uncovered by the "new" test environment. They are in the master branch of the Git repo (http://pythondialog.sourceforge.net/), i.e. for Python 3. I will backport them to Python 2. -- Florent |
|
From: Florent R. <f.r...@fr...> - 2015-04-04 20:25:38
|
Hello again, I have merged all changes from the master branch into the py2 branch. This means that the Python 2 backport should now have all improvements that were made to the reference implementation since version 3.0.1, including the "autowidgetsize feature". I have uploaded version 3.2.2rc1 for both Python 3 (tested with Python 3.1 and 3.4) and Python 2 (tested with Python 2.6 and 2.7). All these work with dialog from Debian squeeze as well as unstable. Please test on your side and report. Regards -- Florent |
|
From: Jakub W. <jak...@gm...> - 2015-04-05 07:56:56
Attachments:
signature.asc
|
On Sat, Apr 04, 2015 at 10:17:55PM +0200, Florent Rougon wrote: > I have uploaded version 3.2.2rc1 for both Python 3 (tested with Python > 3.1 and 3.4) and Python 2 (tested with Python 2.6 and 2.7). All these > work with dialog from Debian squeeze as well as unstable. Please test on > your side and report. I did a quick test run of the letsencrypt client and I can now confirm that the problem has been fixed and everything else seems to work OK. Thank you for a very prompt response, great job! People working on the "dialog" part of the project will probably want to make some more thorough testing of this new RC as soon as the time allows it. -- Kuba |
|
From: Florent R. <f.r...@fr...> - 2015-04-06 14:17:16
|
Hi, Jakub Warmuz <jak...@gm...> wrote: > I did a quick test run of the letsencrypt client and I can now confirm > that the problem has been fixed and everything else seems to work > OK. Thank you for a very prompt response, great job! I'm glad it works fine. Your report was useful, thank you. Good luck with your project! -- Florent |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X