public inbox for crossgcc@sourceware.org
 help / color / mirror / Atom feed
From: Martin Weber <fifteenknots505@gmail.com>
To: crossgcc@sourceware.org
Subject: RPM packages
Date: Wed, 24 Aug 2016 19:15:00 -0000	[thread overview]
Message-ID: <6189963.5xiskyZXR4@linux> (raw)

Hi all,

I have set up a project that can create RPM packages for crosstool-ng for 
various linux distros. It can be found here [1].

Currently I get some rpmlint warnings, see below.

[   15s] RPMLINT report:
[   15s] ===============
[   16s] crosstool-ng.i586: W: script-without-shebang /usr/lib/crosstool-
ng/kconfig/kconfig.mk
[   16s] This text file has executable bits set or is located in a path 
dedicated for
[   16s] executables, but lacks a shebang and cannot thus be executed.  If the 
file is
[   16s] meant to be an executable script, add the shebang, otherwise remove 
the
[   16s] executable bits or move the file elsewhere.

Could some of the maintainers please tell me how to deal with this?

TIA,
	Martin

[1] https://build.opensuse.org/package/show/home:15knots/crosstool-ng

-- 
Cd wrttn wtht vwls s mch trsr.



--
For unsubscribe information see http://sourceware.org/lists.html#faq

                 reply	other threads:[~2016-08-24 19:15 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=6189963.5xiskyZXR4@linux \
    --to=fifteenknots505@gmail.com \
    --cc=crossgcc@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).