From: "Joonas Niilola" <juippis@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: net-news/rssguard/
Date: Sat, 30 Oct 2021 06:24:38 +0000 (UTC) [thread overview]
Message-ID: <1635574880.04163fb434f6fcf0fcd00746f8dc10b18a7ab62c.juippis@gentoo> (raw)
commit: 04163fb434f6fcf0fcd00746f8dc10b18a7ab62c
Author: Anna Vyalkova <cyber+gentoo <AT> sysrq <DOT> in>
AuthorDate: Sat Oct 30 06:21:20 2021 +0000
Commit: Joonas Niilola <juippis <AT> gentoo <DOT> org>
CommitDate: Sat Oct 30 06:21:20 2021 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=04163fb4
net-news/rssguard: add 4.0.4, drop 4.0.3
* Drop REPLACING_VERSIONS warning (to be replaced by a news item)
* Drop MPL-2.0 license (no occurences in the source code)
Signed-off-by: Anna Vyalkova <cyber+gentoo <AT> sysrq.in>
Signed-off-by: Joonas Niilola <juippis <AT> gentoo.org>
| 2 +-
| 11 +----------
2 files changed, 2 insertions(+), 11 deletions(-)
--git a/net-news/rssguard/Manifest b/net-news/rssguard/Manifest
index e176bc34ad1..e45d6f14dd1 100644
--- a/net-news/rssguard/Manifest
+++ b/net-news/rssguard/Manifest
@@ -1,2 +1,2 @@
DIST rssguard-3.9.2.tar.gz 13607587 BLAKE2B 45b3dd406e64bb13a19580255971b0d5eb1fd90d70d8559c736366af7792e7fc0627ee254dce79936ce6a179399271958b7795279a359306e345ec086081fc37 SHA512 30d2524f4ca42d903a047fe39de925268a1aac65192a8b1089b6ec0ec0a9dfef09c535fe391f750149063c06e3275b2632cc2ea2c24ded178760070abcea4958
-DIST rssguard-4.0.3.tar.gz 14427592 BLAKE2B d01969e10eddd837d9e6541e573e6a5bd353eed8cc78508591340ffc354de877b392b79c80f4df725d06be84363412615fa941cc0895fddfd6c9b2e9751bdda9 SHA512 831b99d0b320338bf497ad1ca67120c5b2ee806c61fc1b82b08debc1904222757c3bf3aa068ea7e37bee93be061d444204e6982d2fb0ece2f26f8b4004f7132e
+DIST rssguard-4.0.4.tar.gz 14433147 BLAKE2B 6453d16cb440117c335d6773e675399ae4bee2d9226a2e920ffd1e10cc2d5025fc4c302357974352fad41f637aa33c3b66af2444d969f5e934d7432a16b7cb24 SHA512 8c69ec372a54e7e1ad4ff15476d2387fc84cd9d29c5031f9e5c18dcdf833781c54417101f252d23868eedc91262a9ac6446eb09104f5707b08fa92342d565481
--git a/net-news/rssguard/rssguard-4.0.3.ebuild b/net-news/rssguard/rssguard-4.0.4.ebuild
similarity index 74%
rename from net-news/rssguard/rssguard-4.0.3.ebuild
rename to net-news/rssguard/rssguard-4.0.4.ebuild
index 8f40201072b..9fbe9cc1ee9 100644
--- a/net-news/rssguard/rssguard-4.0.3.ebuild
+++ b/net-news/rssguard/rssguard-4.0.4.ebuild
@@ -9,7 +9,7 @@ DESCRIPTION="Simple (yet powerful) feed reader"
HOMEPAGE="https://github.com/martinrotter/rssguard"
SRC_URI="https://github.com/martinrotter/${PN}/archive/${PV}.tar.gz -> ${P}.tar.gz"
-LICENSE="|| ( LGPL-3 GPL-2+ ) AGPL-3+ BSD GPL-3+ MIT MPL-2.0"
+LICENSE="|| ( LGPL-3 GPL-2+ ) AGPL-3+ BSD GPL-3+ MIT"
SLOT="0"
KEYWORDS="~amd64"
IUSE="debug webengine"
@@ -31,15 +31,6 @@ RDEPEND="${DEPEND}"
DOCS=( README.md resources/docs/Documentation.md )
-pkg_pretend() {
- if [[ -n ${REPLACING_VERSIONS} ]] && ver_test ${REPLACING_VERSIONS} -lt 4.0; then
- ewarn "RSS Guard 4.x is NOT backwards compatible with 3.x line."
- ewarn "You have to either export your feeds in OPML format or"
- ewarn "manually update your database.db file to 4.x.x format:"
- ewarn "https://github.com/martinrotter/rssguard/blob/master/resources/docs/Documentation.md#migrating-user-data-from-392-to-4xx"
- fi
-}
-
src_prepare() {
default
sed -e 's:$$PREFIX/lib:$$PREFIX/'$(get_libdir)':' -i pri/install.pri || die
next reply other threads:[~2021-10-30 6:24 UTC|newest]
Thread overview: 74+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-30 6:24 Joonas Niilola [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-01-05 2:55 [gentoo-commits] repo/gentoo:master commit in: net-news/rssguard/ Michał Górny
2024-12-20 8:23 Michał Górny
2024-10-12 15:47 Michał Górny
2024-10-12 14:57 Sam James
2024-10-07 18:48 Michał Górny
2024-09-27 6:32 Michał Górny
2024-08-10 11:16 Michał Górny
2024-08-10 10:28 Michał Górny
2024-07-26 15:28 Michał Górny
2024-06-15 8:42 Michał Górny
2024-06-15 8:40 Arthur Zamarin
2024-05-31 15:21 Michał Górny
2024-05-31 15:21 Michał Górny
2024-05-30 3:31 Michał Górny
2024-05-15 2:08 Michał Górny
2024-03-30 14:27 Michał Górny
2024-03-30 14:25 Michał Górny
2024-03-15 13:15 Michał Górny
2024-01-18 18:46 Michał Górny
2024-01-18 17:37 Arthur Zamarin
2023-12-15 16:59 Michał Górny
2023-12-09 6:53 Michał Górny
2023-12-07 17:24 Michał Górny
2023-12-02 11:12 Michał Górny
2023-12-02 10:35 Arthur Zamarin
2023-11-14 20:06 Michał Górny
2023-11-13 17:41 Michał Górny
2023-11-12 3:59 Michał Górny
2023-11-11 22:41 Sam James
2023-11-02 14:28 Michał Górny
2023-11-01 16:05 Michał Górny
2023-10-05 14:59 Michał Górny
2023-08-25 9:49 Michał Górny
2023-08-20 10:57 Michał Górny
2023-08-20 10:29 Sam James
2023-07-10 19:26 Arthur Zamarin
2023-06-28 5:06 Michał Górny
2023-05-13 9:04 Michał Górny
2023-05-13 8:40 Arthur Zamarin
2023-05-13 8:35 Michał Górny
2023-05-08 7:44 Joonas Niilola
2023-05-08 7:44 Joonas Niilola
2023-04-04 16:43 Arthur Zamarin
2023-02-09 15:53 Joonas Niilola
2023-02-09 15:53 Joonas Niilola
2023-01-13 13:47 Joonas Niilola
2023-01-13 13:47 Joonas Niilola
2022-10-03 18:34 Ionen Wolkens
2022-06-09 0:57 Ionen Wolkens
2022-03-24 7:28 Ionen Wolkens
2022-01-19 16:28 Joonas Niilola
2021-09-28 13:26 Joonas Niilola
2021-09-09 11:30 Joonas Niilola
2021-09-09 11:30 Joonas Niilola
2021-07-07 13:41 Joonas Niilola
2020-12-17 17:33 Sam James
2020-12-16 1:44 Sam James
2020-12-15 3:25 Sam James
2020-12-15 3:25 Sam James
2020-01-18 17:16 Andreas Sturmlechner
2020-01-05 20:08 Jeroen Roovers
2020-01-05 17:00 Andreas Sturmlechner
2020-01-05 17:00 Andreas Sturmlechner
2018-10-20 12:17 Pacho Ramos
2018-10-20 12:17 Pacho Ramos
2018-07-18 21:11 Jonas Stein
2017-11-29 23:19 Andreas Sturmlechner
2017-11-29 23:19 Andreas Sturmlechner
2017-08-13 13:23 Patrice Clement
2017-08-13 13:23 Patrice Clement
2017-06-20 12:37 Pacho Ramos
2016-11-24 10:54 Michael Palimaka
2015-10-01 14:21 Michael Palimaka
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=1635574880.04163fb434f6fcf0fcd00746f8dc10b18a7ab62c.juippis@gentoo \
--to=juippis@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