From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-python/utidylib/
Date: Sun, 29 Aug 2021 18:30:37 +0000 (UTC) [thread overview]
Message-ID: <1630261752.d11094516af420d1aac38e1dd978caacd406f88c.sam@gentoo> (raw)
commit: d11094516af420d1aac38e1dd978caacd406f88c
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Sun Aug 29 18:26:20 2021 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Sun Aug 29 18:29:12 2021 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=d1109451
dev-python/utidylib: [QA] revbump for changed RDEPEND
It's necessary to have a revision bump for changes in RDEPEND,
but especially where we're changing the providers of an
any-of || ( ... ) dependency.
In this case, if one already has edbrowse installed,
once/if tidy-html5 is masked for removal (which seems to be
the plan), there's no reason the package manage is obligated
to realise that the existing ebuild was modified to allow
htmltidy instead. Hence, a revision bump is required
to apply the metadata change.
Fixes: 4e3e24a192e9d620c7bcbccf536c3c68f04fd363
Signed-off-by: Sam James <sam <AT> gentoo.org>
dev-python/utidylib/{utidylib-0.6-r1.ebuild => utidylib-0.6-r2.ebuild} | 0
dev-python/utidylib/{utidylib-0.7.ebuild => utidylib-0.7-r1.ebuild} | 0
2 files changed, 0 insertions(+), 0 deletions(-)
diff --git a/dev-python/utidylib/utidylib-0.6-r1.ebuild b/dev-python/utidylib/utidylib-0.6-r2.ebuild
similarity index 100%
rename from dev-python/utidylib/utidylib-0.6-r1.ebuild
rename to dev-python/utidylib/utidylib-0.6-r2.ebuild
diff --git a/dev-python/utidylib/utidylib-0.7.ebuild b/dev-python/utidylib/utidylib-0.7-r1.ebuild
similarity index 100%
rename from dev-python/utidylib/utidylib-0.7.ebuild
rename to dev-python/utidylib/utidylib-0.7-r1.ebuild
next reply other threads:[~2021-08-29 18:30 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-29 18:30 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-05-13 19:00 [gentoo-commits] repo/gentoo:master commit in: dev-python/utidylib/ Arthur Zamarin
2024-03-22 12:37 Michał Górny
2024-03-22 6:14 Arthur Zamarin
2024-03-22 6:14 Arthur Zamarin
2024-03-22 3:58 Sam James
2024-03-22 3:58 Sam James
2024-03-21 17:45 Arthur Zamarin
2024-03-05 19:11 Michał Górny
2023-06-01 14:37 Michał Górny
2023-01-08 5:21 Michał Górny
2023-01-07 19:44 Sam James
2023-01-07 19:31 Arthur Zamarin
2023-01-07 18:35 Arthur Zamarin
2023-01-07 18:29 Arthur Zamarin
2023-01-07 18:24 Arthur Zamarin
2022-12-07 15:59 Michał Górny
2022-06-22 15:37 Michał Górny
2022-06-22 13:23 Agostino Sarubbo
2022-06-22 10:16 Agostino Sarubbo
2022-06-22 10:14 Agostino Sarubbo
2022-06-22 10:13 Agostino Sarubbo
2022-06-22 10:10 Agostino Sarubbo
2022-05-21 9:09 Michał Górny
2022-05-16 18:41 Arthur Zamarin
2022-05-16 18:41 Arthur Zamarin
2021-11-10 12:49 Jakov Smolić
2021-10-16 1:14 Sam James
2021-10-16 1:12 Sam James
2021-09-14 1:30 Yixun Lan
2021-08-31 3:54 Arthur Zamarin
2021-08-27 10:29 Marek Szuba
2021-08-23 6:48 Arthur Zamarin
2020-10-11 22:25 Andreas Sturmlechner
2020-10-11 21:33 Andreas Sturmlechner
2020-09-20 9:36 Michał Górny
2020-03-18 18:39 Michał Górny
2020-03-01 22:02 Andreas Sturmlechner
2020-01-05 3:09 Aaron Bauman
2020-01-03 14:30 Agostino Sarubbo
2020-01-03 13:44 Agostino Sarubbo
2020-01-03 13:42 Agostino Sarubbo
2020-01-03 10:06 Agostino Sarubbo
2019-11-24 21:07 Andreas Sturmlechner
2019-11-24 17:13 Andreas Sturmlechner
2019-07-29 20:02 Aaron Bauman
2019-04-27 14:46 Andreas Sturmlechner
2019-03-11 21:03 Andreas Sturmlechner
2018-12-13 14:29 Mikle Kolyada
2018-12-08 9:44 Sergei Trofimovich
2018-12-08 9:36 Sergei Trofimovich
2018-12-07 2:41 Thomas Deutschmann
2018-03-22 13:06 Patrice Clement
2017-12-25 0:03 Patrice Clement
2017-12-02 15:01 Thomas Deutschmann
2017-09-03 1:04 Mike Gilbert
2017-05-04 17:34 Manuel Rüger
2016-12-18 15:57 Agostino Sarubbo
2016-12-18 15:44 Agostino Sarubbo
2016-10-21 21:40 David Seifert
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=1630261752.d11094516af420d1aac38e1dd978caacd406f88c.sam@gentoo \
--to=sam@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