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: app-office/gnumeric/
Date: Fri, 15 Mar 2024 04:39:22 +0000 (UTC)	[thread overview]
Message-ID: <1710477506.aee3e149fc25b0998c02df227f677c380a0d49a3.sam@gentoo> (raw)

commit:     aee3e149fc25b0998c02df227f677c380a0d49a3
Author:     Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Fri Mar 15 04:38:26 2024 +0000
Commit:     Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Fri Mar 15 04:38:26 2024 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=aee3e149

app-office/gnumeric: depend on >=goffice-0.10.57

Needed for go_quad_scalbn which was added in upstream commit https://gitlab.gnome.org/GNOME/goffice/-/commit/cb43fc29f3def2b4fca2d84d9199681ad70bc41b.

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

 app-office/gnumeric/gnumeric-1.12.57.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/app-office/gnumeric/gnumeric-1.12.57.ebuild b/app-office/gnumeric/gnumeric-1.12.57.ebuild
index 3292eef94050..374314330a77 100644
--- a/app-office/gnumeric/gnumeric-1.12.57.ebuild
+++ b/app-office/gnumeric/gnumeric-1.12.57.ebuild
@@ -35,7 +35,7 @@ RDEPEND="
 	sys-libs/zlib
 	>=dev-libs/glib-2.40.0:2
 	>=gnome-extra/libgsf-1.14.33:=
-	>=x11-libs/goffice-0.10.55:0.10[introspection?]
+	>=x11-libs/goffice-0.10.57:0.10[introspection?]
 	>=dev-libs/libxml2-2.4.12:2
 	>=x11-libs/pango-1.24.0:=
 


             reply	other threads:[~2024-03-15  4:39 UTC|newest]

Thread overview: 67+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-15  4:39 Sam James [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-04-07  8:38 [gentoo-commits] repo/gentoo:master commit in: app-office/gnumeric/ Arthur Zamarin
2024-03-15  4:42 Sam James
2024-02-17 16:01 Mart Raudsepp
2024-02-17 16:01 Mart Raudsepp
2023-11-04 20:20 Mart Raudsepp
2023-03-30 15:53 Arthur Zamarin
2023-02-06  3:04 Matt Turner
2023-01-23  3:58 Matt Turner
2022-10-08 18:25 Sam James
2022-09-22  2:56 Matt Turner
2022-05-02 21:47 David Seifert
2022-04-16 12:25 Yixun Lan
2022-03-19 17:10 David Seifert
2022-03-19  7:53 Agostino Sarubbo
2022-03-15  1:48 Matt Turner
2022-03-15  1:48 Matt Turner
2022-01-22 12:34 David Seifert
2022-01-22 12:34 David Seifert
2022-01-22  9:51 Pacho Ramos
2021-06-23 21:33 David Seifert
2021-05-24 20:01 David Seifert
2021-05-24 13:19 Agostino Sarubbo
2021-05-23 22:28 Agostino Sarubbo
2021-04-29  1:05 Matt Turner
2021-04-22 12:15 David Seifert
2021-01-31 19:32 David Seifert
2021-01-31 18:48 Sam James
2021-01-26 15:19 Sam James
2020-09-12 12:47 David Seifert
2020-06-28 21:04 David Seifert
2020-06-28 20:44 Agostino Sarubbo
2020-06-28 20:27 Agostino Sarubbo
2020-06-07 14:20 David Seifert
2020-04-05 21:51 David Seifert
2020-04-05  6:38 Mikle Kolyada
2020-04-05  6:38 Mikle Kolyada
2020-02-27 23:49 David Seifert
2020-02-09 16:11 Michał Górny
2020-01-03 20:40 David Seifert
2019-09-06  7:29 Michał Górny
2019-02-04 19:58 Dennis Lamm
2018-11-17 17:22 Gilles Dartiguelongue
2018-11-17 17:22 Gilles Dartiguelongue
2018-05-06 21:41 Mart Raudsepp
2018-04-29  0:08 Mart Raudsepp
2018-04-26 17:15 Thomas Deutschmann
2018-02-07 23:20 Gilles Dartiguelongue
2017-12-20 20:23 Mart Raudsepp
2017-07-10  5:30 Mart Raudsepp
2017-07-10  5:30 Mart Raudsepp
2017-03-17 21:48 Andreas Hüttel
2016-09-05 22:37 Gilles Dartiguelongue
2016-07-02 10:43 Pacho Ramos
2016-07-02 10:43 Pacho Ramos
2016-05-28 15:49 Pacho Ramos
2016-05-28 15:49 Pacho Ramos
2016-02-20 13:55 Pacho Ramos
2016-02-20 13:55 Pacho Ramos
2016-01-10 18:30 Pacho Ramos
2015-12-26 14:20 Pacho Ramos
2015-12-26 14:20 Pacho Ramos
2015-10-17 11:24 Pacho Ramos
2015-10-17 11:24 Pacho Ramos
2015-09-07 16:24 Mikle Kolyada
2015-08-31 18:20 Gilles Dartiguelongue
2015-08-31 18:20 Gilles Dartiguelongue

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=1710477506.aee3e149fc25b0998c02df227f677c380a0d49a3.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