On Tue, 2018-03-27 at 11:53 -0500, Rex Dieter wrote: > Sérgio Basto wrote: > > > On Mon, 2018-03-26 at 15:33 -0500, Rex Dieter wrote: > > > Sérgio Basto wrote: > > > > > > > On Tue, 2018-03-06 at 16:15 -0600, Rex Dieter wrote: > > > > > I'd be ok with an epel7-only python3-sip > > > > > > > > > > Since it is a new package (not a branch of an existing one), > > > > > then > > > > > it > > > > > would require a new package review. > > > > > > > > > > It would be a bit of shame though, having to fork things like > > > > > that. > > > > > > > > I tried this solution (epel7-only python3-sip) but > > > > BUILDSTDERR: Error: This version of PyQt5 requires sip 4.19.4 > > > > or > > > > later. > > > > when el7 have sip-devel x86_64 4.14.6-4.el7 base > > > > > > > > if we do package sip-qt5 we must override > > > > /usr/lib64/python2.7/site- > > > > packages/sip.so > > > > it is possible sip-qt5 provides and obsolete sip (4.14.6-4.el7) > > > > ? > > > > > > Not possible (by policy). It should be able to work without > > > doing > > > that, but > > > it may require patching. > > > > I don't see how. In python2, how "import sip" will work ? "import > > sip-qt5 > > as sip" ? > > I thought the context here was your desire to add *only python3* > sip/python- > qt5 to epel ? That was if pyhton2-sip was enough , but sip 4.14.6 is not enough for python2-qt5-devel ... But thinking, we might only build python3-qt5 ? ok, let me review this again , seems enough for my openshot and subdownloader .... Thanks, -- Sérgio M. B. _______________________________________________ epel-devel mailing list -- epel-devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to epel-devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
