From: "Thomas Deutschmann" <whissi@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-db/myodbc/
Date: Wed, 28 Aug 2019 11:17:46 +0000 (UTC) [thread overview]
Message-ID: <1566991048.5a9ae6e84952723c20132860a0301622f87910cd.whissi@gentoo> (raw)
commit: 5a9ae6e84952723c20132860a0301622f87910cd
Author: Thomas Deutschmann <whissi <AT> gentoo <DOT> org>
AuthorDate: Wed Aug 28 11:08:06 2019 +0000
Commit: Thomas Deutschmann <whissi <AT> gentoo <DOT> org>
CommitDate: Wed Aug 28 11:17:28 2019 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=5a9ae6e8
dev-db/myodbc: rev bump to ease migration to dev-db/mysql-connector-c
Commit e86f812ab4677da3ba7d70d8d104c1dec4461710 replaced
virtual/libmysqlclient dependency with dev-db/mysql-connector-c atom
without a rev bump.
To avoid unecessary user interaction for users not using emerge's
--changed-deps=y because we are already pushing towards removal of
virtual/libmysqlclient (see commit 08b83d736f77fd5dffa9cd5f6b1b44771726ce94),
this commit will now force the re-installation through rev bump
to ease migration.
Package-Manager: Portage-2.3.72, Repoman-2.3.17
Signed-off-by: Thomas Deutschmann <whissi <AT> gentoo.org>
dev-db/myodbc/{myodbc-5.3.10-r2.ebuild => myodbc-5.3.10-r3.ebuild} | 0
1 file changed, 0 insertions(+), 0 deletions(-)
diff --git a/dev-db/myodbc/myodbc-5.3.10-r2.ebuild b/dev-db/myodbc/myodbc-5.3.10-r3.ebuild
similarity index 100%
rename from dev-db/myodbc/myodbc-5.3.10-r2.ebuild
rename to dev-db/myodbc/myodbc-5.3.10-r3.ebuild
next reply other threads:[~2019-08-28 11:17 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-28 11:17 Thomas Deutschmann [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-09-23 20:16 [gentoo-commits] repo/gentoo:master commit in: dev-db/myodbc/ Andreas Sturmlechner
2024-09-16 23:55 Jakov Smolić
2024-09-16 23:55 Jakov Smolić
2024-04-24 19:08 Sam James
2023-12-14 4:12 Sam James
2022-04-23 2:09 Sam James
2022-03-03 21:22 David Seifert
2022-01-13 4:18 Sam James
2022-01-13 4:18 Sam James
2021-11-14 3:49 Thomas Deutschmann
2021-10-16 3:48 Sam James
2021-08-04 19:13 Thomas Deutschmann
2021-05-12 15:38 Thomas Deutschmann
2021-05-11 10:03 Agostino Sarubbo
2021-05-11 10:02 Agostino Sarubbo
2021-04-26 14:56 Thomas Deutschmann
2021-04-26 1:03 Thomas Deutschmann
2021-02-03 14:30 Agostino Sarubbo
2021-02-03 14:28 Agostino Sarubbo
2021-01-21 22:32 Thomas Deutschmann
2021-01-21 22:32 Thomas Deutschmann
2020-11-27 17:53 Thomas Deutschmann
2020-11-27 16:08 Agostino Sarubbo
2020-11-27 16:04 Agostino Sarubbo
2020-11-25 16:34 Thomas Deutschmann
2020-10-20 18:56 Thomas Deutschmann
2020-08-07 11:53 Agostino Sarubbo
2020-08-07 11:44 Agostino Sarubbo
2020-08-06 11:49 Agostino Sarubbo
2020-07-26 1:46 Thomas Deutschmann
2020-05-23 21:45 Thomas Deutschmann
2020-02-18 9:54 Agostino Sarubbo
2020-02-16 21:14 Thomas Deutschmann
2020-02-15 12:15 Mikle Kolyada
2019-08-24 10:30 Thomas Deutschmann
2019-08-17 13:48 Thomas Deutschmann
2018-08-24 1:40 Thomas Deutschmann
2018-08-21 0:09 Sergei Trofimovich
2018-08-18 23:14 Mikle Kolyada
2018-05-17 14:39 Brian Evans
2018-03-27 12:51 Brian Evans
2018-03-01 16:01 Brian Evans
2018-01-18 17:38 Brian Evans
2018-01-18 17:38 Brian Evans
2018-01-18 14:31 Brian Evans
2017-06-13 15:00 Brian Evans
2017-06-09 18:21 Brian Evans
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=1566991048.5a9ae6e84952723c20132860a0301622f87910cd.whissi@gentoo \
--to=whissi@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