Bug 1631325 - gr-iio: Remove (sub)packages from Fedora 30+: python2-gr-iio
Summary: gr-iio: Remove (sub)packages from Fedora 30+: python2-gr-iio
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: gr-iio
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Miro Hrončok
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: PY2REMOVAL
TreeView+ depends on / blocked
 
Reported: 2018-09-20 11:12 UTC by Miro Hrončok
Modified: 2019-01-10 10:57 UTC (History)
7 users (show)

Fixed In Version: gr-iio-0.2-7.20170705git54c86a5.fc30
Clone Of:
Environment:
Last Closed: 2019-01-10 10:57:27 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Miro Hrončok 2018-09-20 11:12:44 UTC
In line with the Mass Python 2 Package Removal [0], the following (sub)packages of gr-iio were marked for removal:

 * python2-gr-iio

According to our query, those (sub)packages only provide a Python 2 importable module. If this is not true, please tell us why, so we can fix our query.

Please remove them from your package.

As said in the change document, if there is no objection in a week, we will remove the package(s) as soon as we get to it. This change might not match your packaging style, so we'd prefer if you did the change. If you need more time, please let us know here.

We hope this doesn't come to you as a surprise. If you want to know our motivation for this, please read the change document [0].

[0] https://fedoraproject.org/wiki/Changes/Mass_Python_2_Package_Removal

Comment 1 Miro Hrončok 2019-01-10 10:57:27 UTC
I could only remove the legacy python package by actually removing/excluding the files. The build seems to be very tightly coupled with the Python bindings.

That is a hack and I don't really like it, but it got the job done.

Eric, if you are actually reading this, feel free to redo the change somehow better. Also, there is this comment in the spec from 2017-09-21:

# NOTE: gnuradio 3.8 is expected to have Python 3 support. When that
# becomes available, Python 3 support should be added to this package.

So maybe not worth touching until then.


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