Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

python setup.py bdist --format=rpm #767

Closed
ByteOven opened this issue Aug 29, 2016 · 2 comments
Closed

python setup.py bdist --format=rpm #767

ByteOven opened this issue Aug 29, 2016 · 2 comments

Comments

@ByteOven
Copy link

running install_scripts
Installing easy_install script to /home/builder/tmp/setuptools-26.0.0/build/bdist.linux-x86_64/rpm/BUILDROOT/setuptools-26.0.0-1.x86_64/usr/bin
Installing easy_install-2.7 script to /home/builder/tmp/setuptools-26.0.0/build/bdist.linux-x86_64/rpm/BUILDROOT/setuptools-26.0.0-1.x86_64/usr/bin
writing list of installed files to 'INSTALLED_FILES'

  • /usr/lib/rpm/find-debuginfo.sh --strict-build-id -m --run-dwz --dwz-low-mem-die-limit 10000000 --dwz-max-die-limit 110000000 /home/builder/tmp/setuptools-26.0.0/build/bdist.linux-x86_64/rpm/BUILD/setuptools-26.0.0
    /usr/lib/rpm/sepdebugcrcfix: Updated 0 CRC32s, 0 CRC32s did match.
    find: ‘debug’: No such file or directory
  • /usr/lib/rpm/check-rpaths /usr/lib/rpm/check-buildroot
  • /usr/lib/rpm/redhat/brp-compress
  • /usr/lib/rpm/redhat/brp-strip-static-archive /usr/bin/strip
  • /usr/lib/rpm/brp-python-bytecompile /usr/bin/python 1
    Bytecompiling .py files below /home/builder/tmp/setuptools-26.0.0/build/bdist.linux-x86_64/rpm/BUILDROOT/setuptools-26.0.0-1.x86_64/usr/lib/python2.7 using /usr/bin/python2.7
  • /usr/lib/rpm/redhat/brp-python-hardlink
  • /usr/lib/rpm/redhat/brp-java-repack-jars
    Processing files: setuptools-26.0.0-1.noarch
    error: File must begin with "/": (dev).tmpl

RPM build errors:
File must begin with "/": (dev).tmpl
error: command 'rpmbuild' failed with exit status 1

@ByteOven
Copy link
Author

The reason is the space you have space in file name:

setuptools/script (dev).tmpl

@jaraco
Copy link
Member

jaraco commented Aug 30, 2016

Setuptools does have spaces in some of the filenames in the package. I believe it generates everything properly.

I'm a little surprised that rpm can't handle spaces properly. I'm pretty sure this issue would have been reported before if RPM had issues handling spaces in package filenames.

If there's something Setuptools could do to better support RPM, we can consider that, but renaming the files will only be considered as a last resort.

@jaraco jaraco closed this as completed Aug 30, 2016
SpyderRivera pushed a commit to SpyderRivera/incubator-superset that referenced this issue Nov 6, 2017
I was having issues getting an RPM to build. My error was

Processing files: superset-0.20.1-1.noarch
error: File must begin with "/": Lockup
error: File must begin with "/": With
error: File must begin with "/": Text.svg
error: File must begin with "/": Lockup
error: File must begin with "/": With
error: File must begin with "/": [email protected]
error: File must begin with "/": Lockup
error: File must begin with "/": Without
error: File must begin with "/": [email protected]
error: File must begin with "/": Lockup
error: File must begin with "/": Without
error: File must begin with "/": [email protected]
error: File must begin with "/": Mark.png
error: File must begin with "/": [email protected]

for ref pypa/setuptools#767
File renaming fixes this issue
mistercrunch pushed a commit to apache/superset that referenced this issue Nov 7, 2017
I was having issues getting an RPM to build. My error was

Processing files: superset-0.20.1-1.noarch
error: File must begin with "/": Lockup
error: File must begin with "/": With
error: File must begin with "/": Text.svg
error: File must begin with "/": Lockup
error: File must begin with "/": With
error: File must begin with "/": [email protected]
error: File must begin with "/": Lockup
error: File must begin with "/": Without
error: File must begin with "/": [email protected]
error: File must begin with "/": Lockup
error: File must begin with "/": Without
error: File must begin with "/": [email protected]
error: File must begin with "/": Mark.png
error: File must begin with "/": [email protected]

for ref pypa/setuptools#767
File renaming fixes this issue
michellethomas pushed a commit to michellethomas/panoramix that referenced this issue May 24, 2018
I was having issues getting an RPM to build. My error was

Processing files: superset-0.20.1-1.noarch
error: File must begin with "/": Lockup
error: File must begin with "/": With
error: File must begin with "/": Text.svg
error: File must begin with "/": Lockup
error: File must begin with "/": With
error: File must begin with "/": [email protected]
error: File must begin with "/": Lockup
error: File must begin with "/": Without
error: File must begin with "/": [email protected]
error: File must begin with "/": Lockup
error: File must begin with "/": Without
error: File must begin with "/": [email protected]
error: File must begin with "/": Mark.png
error: File must begin with "/": [email protected]

for ref pypa/setuptools#767
File renaming fixes this issue
wenchma pushed a commit to wenchma/incubator-superset that referenced this issue Nov 16, 2018
I was having issues getting an RPM to build. My error was

Processing files: superset-0.20.1-1.noarch
error: File must begin with "/": Lockup
error: File must begin with "/": With
error: File must begin with "/": Text.svg
error: File must begin with "/": Lockup
error: File must begin with "/": With
error: File must begin with "/": [email protected]
error: File must begin with "/": Lockup
error: File must begin with "/": Without
error: File must begin with "/": [email protected]
error: File must begin with "/": Lockup
error: File must begin with "/": Without
error: File must begin with "/": [email protected]
error: File must begin with "/": Mark.png
error: File must begin with "/": [email protected]

for ref pypa/setuptools#767
File renaming fixes this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants