Re: egg-info executable files

[Ben Finney <ben+debian@benfinney.id.au>]

Brian May <bam@debian.org> writes:

> Anybody here seen this before?
>
> W: python3-apscheduler: executable-not-elf-or-script usr/lib/python3/dist-packages/APScheduler-3.0.5.egg-info/PKG-INFO
> W: python3-apscheduler: executable-not-elf-or-script usr/lib/python3/dist-packages/APScheduler-3.0.5.egg-info/requires.txt
> W: python3-apscheduler: executable-not-elf-or-script usr/lib/python3/dist-packages/APScheduler-3.0.5.egg-info/top_level.txt
> W: python3-apscheduler: executable-not-elf-or-script ... use --no-tag-display-limit to see all (or pipe to a file/program)
> W: python-apscheduler: executable-not-elf-or-script usr/lib/python2.7/dist-packages/APScheduler-3.0.5.egg-info/requires.txt
> W: python-apscheduler: executable-not-elf-or-script usr/lib/python2.7/dist-packages/APScheduler-3.0.5.egg-info/entry_points.txt
> W: python-apscheduler: executable-not-elf-or-script usr/lib/python2.7/dist-packages/APScheduler-3.0.5.egg-info/dependency_links.txt
> W: python-apscheduler: executable-not-elf-or-script ... use --no-tag-display-limit to see all (or pipe to a file/program)
>
> setuptools seems to want to make these files executable for some
> reason,

Possibly they have the executable permission in the upstream source
tarball? This is a common symptom of files from MS Windows systems.

Solution: convince upstream to build the tarball better, and/or re-pack
it to fix the permissions.

-- 
 \      “He that would make his own liberty secure must guard even his |
  `\                             enemy from oppression.” —Thomas Paine |
_o__)                                                                  |
Ben Finney