From: "Daniel Campbell" <zlg@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: net-im/toxic/
Date: Thu, 28 Sep 2017 22:11:00 +0000 (UTC) [thread overview]
Message-ID: <1506636463.675810158cfecff172c501b898ff379db0051af3.zlg@gentoo> (raw)
commit: 675810158cfecff172c501b898ff379db0051af3
Author: Daniel Campbell <zlg <AT> gentoo <DOT> org>
AuthorDate: Thu Sep 28 22:07:43 2017 +0000
Commit: Daniel Campbell <zlg <AT> gentoo <DOT> org>
CommitDate: Thu Sep 28 22:07:43 2017 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=67581015
net-im/toxic: correct version string in package
Upstream's first commit after the Release fixes this. This is a quick
fix that will need to be removed for the next version bump, assuming
upstream remembers to update the string before tagging a release.
No input or review was received for over two weeks, leaving me with
little choice but to push, as it works for me.
Thanks to Dennis New for reporting.
Closes: https://bugs.gentoo.org/630370
Package-Manager: Portage-2.3.8, Repoman-2.3.3
net-im/toxic/toxic-0.8.0.ebuild | 9 +++++++++
1 file changed, 9 insertions(+)
diff --git a/net-im/toxic/toxic-0.8.0.ebuild b/net-im/toxic/toxic-0.8.0.ebuild
index c8827675bcf..4758d0bbde4 100644
--- a/net-im/toxic/toxic-0.8.0.ebuild
+++ b/net-im/toxic/toxic-0.8.0.ebuild
@@ -35,6 +35,15 @@ pkg_setup() {
use python && python-single-r1_pkg_setup
}
+src_prepare() {
+ default
+ # bug 630370: version string correction 0.7.2 -> 0.8.0
+ # REMOVE THIS FOR toxic != 0.8.0
+ sed -i \
+ -e 's/^\(TOXIC_VERSION =\).*$/\1 0.8.0/' \
+ cfg/global_vars.mk || die "Version string correction failed."
+}
+
src_configure() {
if ! use av; then
export DISABLE_AV=1
next reply other threads:[~2017-09-28 22:11 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-28 22:11 Daniel Campbell [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-01-25 20:47 [gentoo-commits] repo/gentoo:master commit in: net-im/toxic/ Jimi Huotari
2025-01-25 20:47 Jimi Huotari
2024-11-22 15:43 Joonas Niilola
2024-11-21 6:45 Sam James
2024-07-30 19:09 Pacho Ramos
2024-07-30 19:09 Pacho Ramos
2024-07-30 19:09 Pacho Ramos
2024-07-30 19:09 Pacho Ramos
2023-12-18 7:13 Joonas Niilola
2023-12-18 4:51 Sam James
2023-04-10 8:10 Joonas Niilola
2023-04-10 8:10 Joonas Niilola
2021-12-10 22:17 Jakov Smolić
2021-12-10 16:26 Jakov Smolić
2021-08-24 8:50 Joonas Niilola
2021-08-24 8:50 Joonas Niilola
2021-06-10 8:13 Joonas Niilola
2021-01-02 0:49 Sam James
2021-01-02 0:49 Sam James
2020-12-16 8:29 Joonas Niilola
2020-12-16 8:29 Joonas Niilola
2020-12-16 8:29 Joonas Niilola
2020-09-04 20:53 Sam James
2020-07-17 15:17 Agostino Sarubbo
2020-07-17 15:05 Agostino Sarubbo
2020-06-08 7:46 Joonas Niilola
2020-06-08 7:46 Joonas Niilola
2018-12-09 8:43 Michał Górny
2018-11-12 23:00 Andreas Sturmlechner
2018-08-12 16:58 Michał Górny
2017-12-13 9:03 Michael Palimaka
2017-12-12 21:46 Daniel Campbell
2017-08-30 17:19 Daniel Campbell
2017-02-24 1:06 Daniel Campbell
2017-02-22 9:21 Daniel Campbell
2016-12-19 20:17 Michał Górny
2016-10-28 8:00 Daniel Campbell
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=1506636463.675810158cfecff172c501b898ff379db0051af3.zlg@gentoo \
--to=zlg@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