Bug 1282201 - libssh2-python: Python 3 support
Summary: libssh2-python: Python 3 support
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: libssh2-python
Version: 27
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Chris Lalancette
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: PYTHON3 PY3PATCH-AVAILABLE
TreeView+ depends on / blocked
 
Reported: 2015-11-15 12:56 UTC by Francesco Frassinelli (frafra)
Modified: 2022-12-21 09:51 UTC (History)
6 users (show)

Fixed In Version: libssh2-python-0.7.1-18.fc27
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-11-11 02:55:03 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Python3 subpackage (4.58 KB, patch)
2017-08-24 09:55 UTC, Jan Beran
no flags Details | Diff

Description Francesco Frassinelli (frafra) 2015-11-15 12:56:23 UTC
The code seems to work when building with Python 3. spec should be changed accordingly (a subpackage is needed for Python 3 libraries).

https://fedoraproject.org/wiki/Packaging:Python
https://fedoraproject.org/wiki/Changes/Python_3_as_Default

Comment 1 Jan Kurik 2016-02-24 13:58:30 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 24 development cycle.
Changing version to '24'.

More information and reason for this action is here:
https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora24#Rawhide_Rebase

Comment 2 Dominika Krejčí 2016-05-06 16:22:30 UTC
Hello Chris,

Do you need any help adding Python 3 support to the RPM?

If you need more instructions, a [guide] for porting Python-based RPMs is available.

[guide] http://python-rpm-porting.readthedocs.org/en/latest/index.html

Comment 3 Jan Beran 2016-11-06 11:09:55 UTC
There is reported a warning related to PyString_AsStringAndSize function in src/session.c, as argument 3 type has changed since Python 2.5 (have a look at https://docs.python.org/2/c-api/string.html). Github issue opened [https://github.com/snoack/ssh4py/issues/9], waiting for upstream fix.

Comment 4 Fedora End Of Life 2017-07-25 19:30:13 UTC
This message is a reminder that Fedora 24 is nearing its end of life.
Approximately 2 (two) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 24. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '24'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 24 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 5 Fedora End Of Life 2017-08-08 12:24:51 UTC
Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

Comment 6 Charalampos Stratakis 2017-08-08 12:39:59 UTC
Still valid

Comment 7 Fedora End Of Life 2017-08-08 18:58:45 UTC
Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

Comment 8 Petr Viktorin (pviktori) 2017-08-09 08:36:46 UTC
Still valid.

Comment 9 Jan Kurik 2017-08-15 07:50:21 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 27 development cycle.
Changing version to '27'.

Comment 10 Jan Beran 2017-08-24 09:55:15 UTC
Created attachment 1317561 [details]
Python3 subpackage

Comment 11 Jan Beran 2017-08-24 09:59:59 UTC
Hello Chris,

may I ask you to review the updated specfile, and if it is fine, to build the package in Fedora?

Thank you.

Jan

Comment 12 Chris Lalancette 2017-09-12 12:48:45 UTC
I'm sorry for the very long wait time here.

I just took a look at the specfile.  Things seem pretty reasonable, but there are at least a couple of problems that need to be solved.  In particular, if I run rpmlint on the resulting rpms, I get the following:

clalancette@archangel:~/fedora/libssh2-python (master u+1)$ rpmlint results_libssh2-python/0.7.1/18.fc28/python2-libssh2-0.7.1-18.fc28.x86_64.rpm 
python2-libssh2.x86_64: W: private-shared-object-provides /usr/lib64/python2.7/site-packages/libssh2.so libssh2.so()(64bit)
python2-libssh2.x86_64: W: hidden-file-or-dir /usr/lib/.build-id
python2-libssh2.x86_64: W: hidden-file-or-dir /usr/lib/.build-id
1 packages and 0 specfiles checked; 0 errors, 3 warnings.

(a similar problem exists with the python3 version of the package).  Indeed, if I take a look at the resulting RPM, it includes that /usr/lib/.build-id directory, which seems incorrect.  Once we fix that (and the other rpmlint warning), I think this will be OK.  Thanks for your work so far.

Comment 13 Charalampos Stratakis 2017-09-12 15:56:35 UTC
The .build-id issue is a bug with rpmlint and not an issue with the package, you can safely ignore that warning. See bug 1431408 .

Comment 14 Jan Beran 2017-09-13 21:28:44 UTC
I can see /usr/lib/debug/.build-id directory in the libssh2-python-debuginfo RPM file of the new version as well as previous versions, but neither any */.build-in directory in the python2-libssh2 nor python3-libssh2 RPM files. Please, could you check again?

Comment 15 Chris Lalancette 2017-10-02 23:18:38 UTC
All right, I've done a bit of digging, and Comment 13 was right, the .build-id issue was a red-herring.  There was still the other rpmlint issue about .so provides; I took a look into that, and that was not new, but I fixed it anyway.  I've pushed the whole thing onto the master branch (targetting F28).  It would be easiest for me to just have it target f28 (instead of backporting to F27), but if you really need it in F27, let me know.

Comment 16 Charalampos Stratakis 2017-10-03 09:23:48 UTC
Hello Chris.

If you don't mind, it would be great to have this for F27 as well.

The changes can be fastforwarded to the F27 branch.

Comment 17 Fedora Update System 2017-10-16 12:29:13 UTC
libssh2-python-0.7.1-18.fc27 has been submitted as an update to Fedora 27. https://bodhi.fedoraproject.org/updates/FEDORA-2017-b5b607a136

Comment 18 Fedora Update System 2017-10-17 02:25:14 UTC
libssh2-python-0.7.1-18.fc27 has been pushed to the Fedora 27 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-b5b607a136

Comment 19 Fedora Update System 2017-11-11 02:55:03 UTC
libssh2-python-0.7.1-18.fc27 has been pushed to the Fedora 27 stable repository. If problems still persist, please make note of it in this bug report.

Comment 20 Florian Weimer 2022-12-21 09:51:08 UTC
Python 3 support was not actually achieved, see bug 2154193.


Note You need to log in before you can comment on or make changes to this bug.