From: "Zac Medico" <zmedico@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: net-libs/libslirp/
Date: Sat, 19 Jun 2021 16:03:22 +0000 (UTC) [thread overview]
Message-ID: <1624118586.c12ee84df0feb4f2b0d21d8048abb4796d6c459c.zmedico@gentoo> (raw)
commit: c12ee84df0feb4f2b0d21d8048abb4796d6c459c
Author: Zac Medico <zmedico <AT> gentoo <DOT> org>
AuthorDate: Sat Jun 19 16:01:34 2021 +0000
Commit: Zac Medico <zmedico <AT> gentoo <DOT> org>
CommitDate: Sat Jun 19 16:03:06 2021 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=c12ee84d
net-libs/libslirp: Bump to version 4.6.1
Closes: https://bugs.gentoo.org/796737
Package-Manager: Portage-3.0.20, Repoman-3.0.3
Signed-off-by: Zac Medico <zmedico <AT> gentoo.org>
net-libs/libslirp/Manifest | 2 +-
net-libs/libslirp/{libslirp-4.6.0.ebuild => libslirp-4.6.1.ebuild} | 0
2 files changed, 1 insertion(+), 1 deletion(-)
diff --git a/net-libs/libslirp/Manifest b/net-libs/libslirp/Manifest
index d764e25575b..b2523bed1cc 100644
--- a/net-libs/libslirp/Manifest
+++ b/net-libs/libslirp/Manifest
@@ -1 +1 @@
-DIST libslirp-4.6.0.tar.gz 135533 BLAKE2B 62be67192a68b4c8bdc0b84f1ba2f1d3617a2c94c14720f9eb2f4ca317af59b59ce4d2147903b4055e60f4de262db7500345db6341b083a1d6f48e9f6a2edd04 SHA512 f3464818182bd2d8d21fd1f158172acd84523d8c252f21cab4f29317606b01ebd772a612dc522255e7f4a169608e6604b389e433e65d3163ba591f639e744a81
+DIST libslirp-4.6.1.tar.gz 135569 BLAKE2B 7a890912f2a8ce9d6820870e2d29b9c7a2253c403c2bcb127a38e02b2b81d1e262f34571c8a4c05fbf46874b9b2967cb5597cabe169ad54f12702fdd8b90bb3c SHA512 04a9dd88cd58c849a24b9cff405d951952760d99ea2bef0b070463dff088d79f44557a13c9427ba0043f58d4b9e06b68ff64a4f23a7b0d66df594e32e1521cae
diff --git a/net-libs/libslirp/libslirp-4.6.0.ebuild b/net-libs/libslirp/libslirp-4.6.1.ebuild
similarity index 100%
rename from net-libs/libslirp/libslirp-4.6.0.ebuild
rename to net-libs/libslirp/libslirp-4.6.1.ebuild
next reply other threads:[~2021-06-19 16:03 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-19 16:03 Zac Medico [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-06-02 21:41 [gentoo-commits] repo/gentoo:master commit in: net-libs/libslirp/ Sam James
2023-05-16 1:52 Sam James
2023-05-01 1:58 Sam James
2023-04-30 23:53 Sam James
2023-04-30 23:50 Sam James
2023-04-30 23:50 Sam James
2022-05-19 12:19 WANG Xuerui
2022-04-28 0:53 Zac Medico
2022-02-07 21:45 James Le Cuirot
2021-12-31 3:42 Yixun Lan
2021-12-26 0:20 Sam James
2021-06-19 15:37 Zac Medico
2021-06-18 22:38 Sam James
2021-06-18 6:30 Agostino Sarubbo
2021-06-18 6:28 Agostino Sarubbo
2021-06-18 6:27 Agostino Sarubbo
2021-06-16 15:09 Zac Medico
2021-06-16 15:07 Zac Medico
2020-12-19 0:07 Zac Medico
2020-12-18 10:25 Sergei Trofimovich
2020-12-15 10:37 Sam James
2020-12-15 6:28 Sam James
2020-12-14 20:18 Thomas Deutschmann
2020-12-14 10:07 Zac Medico
2020-11-07 3:49 Georgy Yakovlev
2020-08-30 1:32 Thomas Deutschmann
2020-08-29 18:49 Zac Medico
2020-08-20 21:53 Zac Medico
2020-08-19 22:40 Sam James
2020-08-16 14:46 Agostino Sarubbo
2020-07-17 17:27 Sam James
2020-07-17 0:35 Sam James
2020-07-12 8:29 Sergei Trofimovich
2020-07-09 21:57 Zac Medico
2020-07-09 4:27 Zac Medico
2020-04-24 2:37 Zac Medico
2020-04-24 1:56 Zac Medico
2020-04-24 1:56 Zac Medico
2020-04-19 22:30 Zac Medico
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=1624118586.c12ee84df0feb4f2b0d21d8048abb4796d6c459c.zmedico@gentoo \
--to=zmedico@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