public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: www-apps/jekyll/
Date: Fri, 23 Jun 2023 08:51:26 +0000 (UTC)	[thread overview]
Message-ID: <1687510264.260a4b141d39cc1946a5f6db46e9d392141d590d.sam@gentoo> (raw)

commit:     260a4b141d39cc1946a5f6db46e9d392141d590d
Author:     Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Fri Jun 23 07:59:07 2023 +0000
Commit:     Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Fri Jun 23 08:51:04 2023 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=260a4b14

www-apps/jekyll: skip network test

Closes: https://bugs.gentoo.org/880695
Signed-off-by: Sam James <sam <AT> gentoo.org>

 www-apps/jekyll/jekyll-4.3.2.ebuild | 6 +++++-
 1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/www-apps/jekyll/jekyll-4.3.2.ebuild b/www-apps/jekyll/jekyll-4.3.2.ebuild
index db9b3c7015a0..a0dc21a39fa2 100644
--- a/www-apps/jekyll/jekyll-4.3.2.ebuild
+++ b/www-apps/jekyll/jekyll-4.3.2.ebuild
@@ -3,7 +3,7 @@
 
 EAPI=8
 
-USE_RUBY="ruby27 ruby30"
+USE_RUBY="ruby30"
 
 inherit ruby-fakegem
 
@@ -95,6 +95,10 @@ all_ruby_prepare() {
 	# Avoid a test failing due to TZ differences
 	sed -e '/contain the proper page data to mimic the post liquid/askip "TZ difference"' \
 		-i test/test_excerpt.rb || die
+
+	# Confused by network-sandbox
+	sed -e "/return true if there's internet/askip \"Confused by network-sandbox\"" \
+		-i test/test_utils.rb || die
 }
 
 src_test() {


             reply	other threads:[~2023-06-23  8:51 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-23  8:51 Sam James [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-03-15  6:08 [gentoo-commits] repo/gentoo:master commit in: www-apps/jekyll/ Hans de Graaff
2023-12-13 13:16 Hans de Graaff
2023-12-13 13:16 Hans de Graaff
2023-08-19  8:36 Hans de Graaff
2023-07-20  7:23 Hans de Graaff
2023-04-01  6:35 Hans de Graaff
2023-04-01  6:25 Hans de Graaff
2023-02-22 19:56 Sam James
2022-06-18  8:40 Hans de Graaff
2022-05-20 10:36 Hans de Graaff
2022-05-20 10:36 Hans de Graaff
2021-08-29  0:40 Aaron Bauman
2020-09-09 10:07 Michał Górny
2020-08-15 10:13 Hans de Graaff
2020-08-09  7:27 Michał Górny
2020-07-27  2:09 Sam James
2020-06-19 13:09 Hans de Graaff
2019-07-17  7:37 Hans de Graaff
2019-04-12 13:58 Hans de Graaff
2018-11-25 21:58 Aaron Bauman
2018-09-06 21:22 Michał Górny
2018-06-13 11:00 Michał Górny
2018-05-06  8:14 Hans de Graaff
2018-05-06  8:14 Hans de Graaff
2018-01-24 18:33 Hans de Graaff
2017-10-09 18:06 Michał Górny
2017-10-09 18:06 Michał Górny
2017-08-28  5:54 Hans de Graaff
2017-04-28 21:15 Manuel Rüger
2017-04-28 21:15 Manuel Rüger
2016-10-24 21:24 Manuel Rüger
2016-09-17  2:47 Manuel Rüger
2016-09-17  1:34 Manuel Rüger
2016-09-05 19:44 Manuel Rüger
2016-09-05 17:52 Manuel Rüger
2016-08-28 22:59 Manuel Rüger
2016-05-20 20:17 Manuel Rüger
2016-05-20 20:14 Manuel Rüger
2016-04-29 19:44 Manuel Rüger
2016-04-19 21:54 Manuel Rüger
2016-02-21 11:05 Manuel Rüger
2016-02-21 11:05 Manuel Rüger
2016-02-18 22:52 Manuel Rüger
2016-02-18 22:52 Manuel Rüger
2016-02-18 22:48 Manuel Rüger
2016-01-23 16:31 Manuel Rüger

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=1687510264.260a4b141d39cc1946a5f6db46e9d392141d590d.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