https://bugzilla.redhat.com/show_bug.cgi?id=2502106

Cristian Le <[email protected]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|Review Request: pyclibrary  |Review Request:
                   |- C parser and ctypes       |python-pyclibrary - C
                   |automation for python       |parser and ctypes
                   |                            |automation for python



--- Comment #3 from Cristian Le <[email protected]> ---
Indeed so, probably was a bit too jet-lagged when I was doing this one. For
context this one I was doing as part of
https://copr.fedorainfracloud.org/coprs/lecris/cuda-example/, still valid to
include on our side though.

I think the wheel part will fix it once upstream decides on a path. There is
something funky because in the `MANIFEST.in` we are not supposed to have the
test files, but we clearly do.

Spec URL:
https://lecris.fedorapeople.org/reviews/python-pyclibrary/python-pyclibrary.spec
SRPM URL:
https://lecris.fedorapeople.org/reviews/python-pyclibrary/python-pyclibrary-0.3.0-1.fc46.src.rpm
Scratch build: https://koji.fedoraproject.org/koji/taskinfo?taskID=149196274


-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are always notified about changes to this product and component
https://bugzilla.redhat.com/show_bug.cgi?id=2502106

Report this comment as SPAM: 
https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-spam&short_desc=Report%20of%20Bug%202502106%23c3

-- 
_______________________________________________
package-review mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/[email protected]
Do not reply to spam, report it: 
https://forge.fedoraproject.org/infra/tickets/issues/new

Reply via email to