From: Dario Faggioli <dario.faggioli@citrix.com>
To: George Dunlap <george.dunlap@eu.citrix.com>
Cc: Ian Jackson <ian.jackson@citrix.com>,
Ian Campbell <ian.campbell@citrix.com>,
xen-devel@lists.xen.org
Subject: Re: [PATCH] Add a "make rpmball" target
Date: Mon, 3 Mar 2014 23:52:59 +0100 [thread overview]
Message-ID: <1393887179.4058.158.camel@Solace> (raw)
In-Reply-To: <1393858780-11628-1-git-send-email-george.dunlap@eu.citrix.com>
[-- Attachment #1.1: Type: text/plain, Size: 1593 bytes --]
On lun, 2014-03-03 at 14:59 +0000, George Dunlap wrote:
> Build a simplistic dummy package, similar to "make debball", for
> developers on rpm-based systems.
>
Importing this produced the following output:
$ stg import -M /home/dario/patch-export.mbox
Checking for changes in the working directory ... done
Importing patch "add-a-make-rpmball-target" ... <stdin>:43: trailing whitespace.
if test -z "$1" -o -z "$2" ; then
<stdin>:46: trailing whitespace.
fi
<stdin>:106: trailing whitespace.
# Point xen.gz to the real binary.
<stdin>:108: trailing whitespace.
ln -sf %{name}-%{version}-%{release}.gz xen.gz
warning: 4 lines add whitespace errors.
done
Now at patch "add-a-make-rpmball-target"
Trying to `make rpmball' both on debian (after having installed the
relevant rpm* packages) and on Fedora tells me this:
install -d -m0755 -p /home/dario/Sources/xen/xen/xen.git/dist/
install -m0644 -p ./COPYING /home/dario/Sources/xen/xen/xen.git/dist
install -m0644 -p ./README /home/dario/Sources/xen/xen/xen.git/dist
install -m0755 -p ./install.sh /home/dario/Sources/xen/xen/xen.git/dist
sh ./tools/misc/mkrpm /home/dario/Sources/xen/xen/xen.git $(make -C xen xenversion | grep -v :)
error: line 3: Illegal char '-' in: Version: 4.5-unstable
make: *** [rpmball] Error 1
Regards,
Dario
--
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://about.me/dario.faggioli
Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
prev parent reply other threads:[~2014-03-03 22:52 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-03 14:59 [PATCH] Add a "make rpmball" target George Dunlap
2014-03-03 16:07 ` George Dunlap
2014-03-03 22:34 ` Don Slutz
2014-03-03 23:08 ` Don Slutz
2014-03-03 23:37 ` M A Young
2014-03-03 23:46 ` Don Slutz
2014-03-03 23:52 ` M A Young
2014-03-04 10:26 ` George Dunlap
2014-03-03 16:23 ` Olaf Hering
2014-03-03 16:34 ` George Dunlap
2014-03-03 16:36 ` George Dunlap
2014-03-03 17:31 ` Olaf Hering
2014-03-03 17:23 ` Olaf Hering
2014-03-03 17:27 ` Dario Faggioli
2014-03-03 17:30 ` George Dunlap
2014-03-03 17:59 ` Ian Jackson
2014-03-03 22:53 ` Dario Faggioli
2014-03-03 23:11 ` Olaf Hering
2014-03-04 12:19 ` Ian Jackson
2014-03-03 18:19 ` Ian Campbell
2014-03-03 23:06 ` Olaf Hering
2014-03-03 20:51 ` Don Slutz
2014-03-04 11:41 ` George Dunlap
2014-03-03 22:52 ` Dario Faggioli [this message]
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=1393887179.4058.158.camel@Solace \
--to=dario.faggioli@citrix.com \
--cc=george.dunlap@eu.citrix.com \
--cc=ian.campbell@citrix.com \
--cc=ian.jackson@citrix.com \
--cc=xen-devel@lists.xen.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 NNTP newsgroup(s).