From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [IPFire-SCM] [git.ipfire.org] IPFire 3.x development tree branch, master, updated. 0a8170acd183f925aae9285fa14319ed319773e0
Date: Thu, 19 Apr 2012 23:15:21 +0200 [thread overview]
Message-ID: <20120419211521.BC3B0200BC@argus.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1731 bytes --]
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "IPFire 3.x development tree".
The branch, master has been updated
via 0a8170acd183f925aae9285fa14319ed319773e0 (commit)
from 9d87f344cb9d90a86da6fbd7f483d3fc38c2ff43 (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
commit 0a8170acd183f925aae9285fa14319ed319773e0
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date: Thu Apr 19 23:14:26 2012 +0200
python-cairo: Fix packaging.
The development package has not been correctly configured
and thus all files were put into the -devel package.
I added the template and now it's much better.
-----------------------------------------------------------------------
Summary of changes:
python-cairo/python-cairo.nm | 5 +++--
1 files changed, 3 insertions(+), 2 deletions(-)
Difference in files:
diff --git a/python-cairo/python-cairo.nm b/python-cairo/python-cairo.nm
index e1e90fc..b10076e 100644
--- a/python-cairo/python-cairo.nm
+++ b/python-cairo/python-cairo.nm
@@ -5,7 +5,7 @@
name = python-cairo
version = 1.8.10
-release = 2
+release = 3
groups = Development/Tools
url = http://cairographics.org/pycairo
@@ -31,9 +31,10 @@ end
packages
package %{name}
- end
package %{name}-devel
+ template DEVEL
+
# The development headers need the cairo headers.
requires
cairo-devel
hooks/post-receive
--
IPFire 3.x development tree
reply other threads:[~2012-04-19 21: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=20120419211521.BC3B0200BC@argus.ipfire.org \
--to=git@ipfire.org \
--cc=ipfire-scm@lists.ipfire.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