[Bug 1123011] Review Request: python-dockerpty - Python library to use the pseudo-tty of a docker container

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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



--- Comment #3 from Julien Enselme <jujens@xxxxxxxxx> ---
The python3 summary is still incorrect.

According to https://fedoraproject.org/wiki/Packaging:Python#Files_to_include
you can use:
%files
%{python2_sitelib}/foo/ (I forget the last / sorry)

or

%files
%dir %{python2_sitelib}/foo (to add the directory)
%{python2_sitelib}/foo/*

Please add
%dir %{python2_sitelib}/dockerpty
%{python2_sitelib}/dockerpty/*
%dir %{python2_sitelib}/dockerpty-0.2.1-py3.3.egg-info
%{python2_sitelib}/dockerpty-0.2.1-py3.3.egg-info/*

Idem for python3.

> I fixed up the notes that were made, however instead of listing it as "BuildArch: noarch" I actually listed it "ExclusiveArch: x86_64" because this is meant to be used with docker containers and docker itself is "ExclusiveArch: x86_64". I also made a note in a spec file for posterity.

Except that your python package does not contain any architecture specific
source and so has no binary. Hence the no-binary error from rmplint. So, as
stated here: https://fedoraproject.org/wiki/Common_Rpmlint_issues#no-binary it
must be of noarch. By doing so, you get rid of the unseful debuginfo package
and the rpmlint error.

If the only way to use this package is with docker, add docker as a dependency.
Your package then won't install on an architecture that is not supported by
docker.

-- 
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
_______________________________________________
package-review mailing list
package-review@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/package-review





[Index of Archives]     [Fedora Legacy]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [KDE Users]     [Fedora Tools]