BAlchemyLab / bal

Block[Chain] Alchemy Laboratory Framework
GNU General Public License v3.0
4 stars 5 forks source link

Problem with RPM package creating #4

Open sadov opened 6 years ago

sadov commented 6 years ago

I trying to create RPM package by using of setup.py, seems some problem with README.md placement:

$ LANG=C python setup.py bdist_rpm /usr/lib64/python2.7/distutils/dist.py:267: UserWarning: Unknown distribution option: 'python_requires' warnings.warn(msg) running bdist_rpm running egg_info writing requirements to blockchain_alchemy.egg-info/requires.txt writing blockchain_alchemy.egg-info/PKG-INFO writing top-level names to blockchain_alchemy.egg-info/top_level.txt writing dependency_links to blockchain_alchemy.egg-info/dependency_links.txt reading manifest file 'blockchain_alchemy.egg-info/SOURCES.txt' writing manifest file 'blockchain_alchemy.egg-info/SOURCES.txt' writing 'build/bdist.linux-x86_64/rpm/SPECS/blockchain-alchemy.spec' running sdist warning: sdist: standard file not found: should have one of README, README.rst, README.txt

running check creating blockchain-alchemy-1.0.0 creating blockchain-alchemy-1.0.0/blockchain-alchemy creating blockchain-alchemy-1.0.0/blockchain_alchemy.egg-info making hard links in blockchain-alchemy-1.0.0... hard linking setup.py -> blockchain-alchemy-1.0.0 hard linking blockchain-alchemy/BaseBlockChain.py -> blockchain-alchemy-1.0.0/blockchain-alchemy hard linking blockchain-alchemy/POWBlockChain.py -> blockchain-alchemy-1.0.0/blockchain-alchemy hard linking blockchain-alchemy/QuantumBlockChain.py -> blockchain-alchemy-1.0.0/blockchain-alchemy hard linking blockchain-alchemy/init.py -> blockchain-alchemy-1.0.0/blockchain-alchemy hard linking blockchain-alchemy/version.py -> blockchain-alchemy-1.0.0/blockchain-alchemy hard linking blockchain-alchemy/balmn.py -> blockchain-alchemy-1.0.0/blockchain-alchemy hard linking blockchain-alchemy/bcmn_test.py -> blockchain-alchemy-1.0.0/blockchain-alchemy hard linking blockchain-alchemy/bcnode.py -> blockchain-alchemy-1.0.0/blockchain-alchemy hard linking blockchain-alchemy/blockchain.py -> blockchain-alchemy-1.0.0/blockchain-alchemy hard linking blockchain_alchemy.egg-info/PKG-INFO -> blockchain-alchemy-1.0.0/blockchain_alchemy.egg-info hard linking blockchain_alchemy.egg-info/SOURCES.txt -> blockchain-alchemy-1.0.0/blockchain_alchemy.egg-info hard linking blockchain_alchemy.egg-info/dependency_links.txt -> blockchain-alchemy-1.0.0/blockchain_alchemy.egg-info hard linking blockchain_alchemy.egg-info/requires.txt -> blockchain-alchemy-1.0.0/blockchain_alchemy.egg-info hard linking blockchain_alchemy.egg-info/top_level.txt -> blockchain-alchemy-1.0.0/blockchain_alchemy.egg-info Writing blockchain-alchemy-1.0.0/setup.cfg Creating tar archive removing 'blockchain-alchemy-1.0.0' (and everything under it) copying dist/blockchain-alchemy-1.0.0.tar.gz -> build/bdist.linux-x86_64/rpm/SOURCES building RPMs rpmbuild -ba --define _topdir /home/sadov/work/blockchains/BAlchemyLab/bal/build/bdist.linux-x86_64/rpm --clean build/bdist.linux-x86_64/rpm/SPECS/blockchain-alchemy.spec Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.XVVU1P

RPM build errors: Bad exit status from /var/tmp/rpm-tmp.YEBf4v (%build) error: command 'rpmbuild' failed with exit status 1

manishlamichhane commented 6 years ago

Currently, I am fetching the description from README.md file in project root. The build folder doesnot have README.md which is why the error. Would it be reasonable to add description directly as text to the setup.py? It just looks redundant to maintain description in two places.

sadov commented 6 years ago

Sure -- duplication is a bad practice. Usually detailed instructions are not included directly in Python packages -- in general case, it can be pretty large tutorials/references. But we may place our README in modified RPM-package. In any case we will must to add package requirements to corresponded SPEC-file by hands.