public inbox for ipfire-scm@lists.ipfire.org
 help / color / mirror / Atom feed
From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [IPFire-SCM] [git.ipfire.org] IPFire 3.x development tree branch, master, updated. a965b2ddd4d401dea070c75b38150b87f8fb3da6
Date: Wed, 20 Jun 2012 21:40:48 +0200	[thread overview]
Message-ID: <20120620194049.467C22006B@argus.ipfire.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1451 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  a965b2ddd4d401dea070c75b38150b87f8fb3da6 (commit)
      from  5b1f5bb1ea7de4ed03ed6b88eccbdc1599f44a01 (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 a965b2ddd4d401dea070c75b38150b87f8fb3da6
Author: Stefan Schantl <stefan.schantl(a)ipfire.org>
Date:   Wed Jun 20 18:36:59 2012 +0200

    newt: Fix packaging of python-newt on x86_64.

-----------------------------------------------------------------------

Summary of changes:
 newt/newt.nm |    4 ++--
 1 files changed, 2 insertions(+), 2 deletions(-)

Difference in files:
diff --git a/newt/newt.nm b/newt/newt.nm
index e1092b7..94ef180 100644
--- a/newt/newt.nm
+++ b/newt/newt.nm
@@ -5,7 +5,7 @@
 
 name       = newt
 version    = 0.52.13
-release    = 1
+release    = 2
 
 groups     = System/Libraries
 url        = https://fedorahosted.org/releases/n/e/newt/
@@ -58,7 +58,7 @@ packages
 		end
 
 		files
-			/usr/lib/python*/site-packages/*snack*
+			%{libdir}/python*/site-packages/*snack*
 		end
 	end
 


hooks/post-receive
--
IPFire 3.x development tree

                 reply	other threads:[~2012-06-20 19:40 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=20120620194049.467C22006B@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