From: "Markos Chandras" <hwoarang@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/qt:master commit in: Documentation/maintainers/
Date: Tue, 23 Oct 2012 17:54:20 +0000 (UTC) [thread overview]
Message-ID: <1351014854.0e39a47821ad0f6252f61b97f9addd5ed42fb018.hwoarang@gentoo> (raw)
commit: 0e39a47821ad0f6252f61b97f9addd5ed42fb018
Author: Markos Chandras <hwoarang <AT> gentoo <DOT> org>
AuthorDate: Tue Oct 23 17:54:14 2012 +0000
Commit: Markos Chandras <hwoarang <AT> gentoo <DOT> org>
CommitDate: Tue Oct 23 17:54:14 2012 +0000
URL: http://git.overlays.gentoo.org/gitweb/?p=proj/qt.git;a=commit;h=0e39a478
bump-python-revision: Fix detection for pyqt4/sip revisions
---
Documentation/maintainers/bump-python-revisions | 8 ++++----
1 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/Documentation/maintainers/bump-python-revisions b/Documentation/maintainers/bump-python-revisions
index 6d20199..87c267b 100755
--- a/Documentation/maintainers/bump-python-revisions
+++ b/Documentation/maintainers/bump-python-revisions
@@ -96,12 +96,12 @@ commit() {
getrevisions() {
pushd ${OVERLAY}/dev-python/PyQt4/ > /dev/null
pyqt4_tomove=$(find '.' -type f -name "PyQt4-*_pre*.ebuild"|tail -1)
- pyqt4_revision=$(grep ^REVISION ${pyqt4_tomove}|sed "s:^REVISION=::")
+ pyqt4_revision=$(grep ^REVISION ${pyqt4_tomove}|cut -d "=" -f 2)
PVER=$(echo ${pyqt4_tomove/\.\//}|sed "s:PyQt4-\(.*\)_pre.*:\1:")
popd > /dev/null
pushd ${OVERLAY}/dev-python/sip/ > /dev/null
sip_tomove=$(find '.' -type f -name "sip-*_pre*.ebuild"|tail -1)
- sip_revision=$(grep "HG_REVISION=" ${sip_tomove}|sed "s:HG_REVISION=::")
+ sip_revision=$(grep "HG_REVISION=" ${sip_tomove}|cut -d "=" -f 2)
SVER=$(echo ${sip_tomove/\.\//}|sed "s:sip-\(.*\)_pre.*:\1:")
popd > /dev/null
@@ -130,10 +130,10 @@ getrevisions() {
einfo "New sip snapshot@rev: ${new_sip}@${new_sip_rev}"
# Decide what to bump"
[[ -z ${new_pyqt4_rev} ]] || \
- { [[ ${pyqt4_revision} != ${new_pyqt4_rev} ]] \
+ { [[ "${pyqt4_revision}" != "${new_pyqt4_rev}" ]] \
&& dopyqt4 && FOUND=true; }
[[ -z ${new_sip_rev} ]] || \
- { [[ ${sip_revision} != ${new_sip_rev} ]] \
+ { [[ "${sip_revision}" != "${new_sip_rev}" ]] \
&& dosip && FOUND=true; }
if [[ -n ${FOUND} ]]; then
next reply other threads:[~2012-10-23 17:54 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-23 17:54 Markos Chandras [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-11-28 19:31 [gentoo-commits] proj/qt:master commit in: Documentation/maintainers/ Davide Pesavento
2014-08-10 14:29 Davide Pesavento
2014-08-19 1:07 ` Davide Pesavento
2013-06-30 23:11 Davide Pesavento
2012-10-16 18:30 Markos Chandras
2012-10-16 18:30 Markos Chandras
2012-10-14 21:30 Davide Pesavento
2012-09-22 16:43 Markos Chandras
2012-09-22 16:36 Markos Chandras
2012-09-22 12:01 Markos Chandras
2012-07-12 17:10 Markos Chandras
2012-07-10 17:23 Markos Chandras
2012-07-04 17:55 Markos Chandras
2012-06-23 11:06 Markos Chandras
2012-06-09 8:44 Markos Chandras
2012-06-08 20:24 Markos Chandras
2012-06-08 20:20 Markos Chandras
2012-06-08 20:20 Markos Chandras
2012-05-05 22:14 Markos Chandras
2012-03-29 13:56 Davide Pesavento
2012-03-25 16:46 Markos Chandras
2012-03-24 11:10 Markos Chandras
2012-03-24 11:08 Markos Chandras
2012-03-18 11:03 Markos Chandras
2012-03-18 11:00 Markos Chandras
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=1351014854.0e39a47821ad0f6252f61b97f9addd5ed42fb018.hwoarang@gentoo \
--to=hwoarang@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.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