public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Alfredo Tupone" <tupone@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-ada/libadalang/files/, dev-ada/libadalang/
Date: Sun, 26 Feb 2023 16:23:12 +0000 (UTC)	[thread overview]
Message-ID: <1677428565.78332276fb6993d830c1c869970f66726969921b.tupone@gentoo> (raw)

commit:     78332276fb6993d830c1c869970f66726969921b
Author:     Alfredo Tupone <tupone <AT> gentoo <DOT> org>
AuthorDate: Sun Feb 26 16:21:50 2023 +0000
Commit:     Alfredo Tupone <tupone <AT> gentoo <DOT> org>
CommitDate: Sun Feb 26 16:22:45 2023 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=78332276

dev-ada/libadalang: py3.11, gcc_12 & EAPI 8

Closes: https://bugs.gentoo.org/896668
Signed-off-by: Alfredo Tupone <tupone <AT> gentoo.org>

 dev-ada/libadalang/files/libadalang-23.0.0-test.patch         | 11 +++++++++++
 .../{libadalang-23.0.0.ebuild => libadalang-23.0.0-r1.ebuild} |  8 +++++---
 2 files changed, 16 insertions(+), 3 deletions(-)

diff --git a/dev-ada/libadalang/files/libadalang-23.0.0-test.patch b/dev-ada/libadalang/files/libadalang-23.0.0-test.patch
new file mode 100644
index 000000000000..ac5738d5a685
--- /dev/null
+++ b/dev-ada/libadalang/files/libadalang-23.0.0-test.patch
@@ -0,0 +1,11 @@
+--- a/user_manual/changes/V325-006.yaml	2022-09-15 14:51:28.000000000 +0200
++++ b/user_manual/changes/V325-006.yaml	2023-02-26 16:41:25.121927720 +0100
+@@ -1,7 +1,7 @@
+ type: bugfix
+ title: Fix exponentiation in Ada integer literal decoding
+ description: |
+-  Libadalang’s decoder for integer literals (the
++  Libadalang's decoder for integer literals (the
+   ``Libadalang.Sources.Decode_Integer_Literal`` procedure) applied the exponent
+   in base 10 regardless of the base of the literal being evaluated. This is
+   wrong, as the ARM (2.4.2) states:

diff --git a/dev-ada/libadalang/libadalang-23.0.0.ebuild b/dev-ada/libadalang/libadalang-23.0.0-r1.ebuild
similarity index 95%
rename from dev-ada/libadalang/libadalang-23.0.0.ebuild
rename to dev-ada/libadalang/libadalang-23.0.0-r1.ebuild
index 7ebaec865511..6df305d7916c 100644
--- a/dev-ada/libadalang/libadalang-23.0.0.ebuild
+++ b/dev-ada/libadalang/libadalang-23.0.0-r1.ebuild
@@ -1,10 +1,10 @@
 # Copyright 1999-2023 Gentoo Authors
 # Distributed under the terms of the GNU General Public License v2
 
-EAPI=7
+EAPI=8
 
-PYTHON_COMPAT=( python3_10 )
-ADA_COMPAT=( gnat_2021 gcc_12_2_0 )
+PYTHON_COMPAT=( python3_{10..11} )
+ADA_COMPAT=( gnat_2021 gcc_12 gcc_12_2_0 )
 
 inherit ada python-single-r1 multiprocessing
 
@@ -43,6 +43,8 @@ BDEPEND="test? (
 		<dev-lang/ocaml-4.14
 	)"
 
+PATCHES=( "${FILESDIR}"/${P}-test.patch )
+
 pkg_setup() {
 	python-single-r1_pkg_setup
 	ada_pkg_setup


             reply	other threads:[~2023-02-26 16:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-26 16:23 Alfredo Tupone [this message]
  -- strict thread matches above, loose matches on Subject: below --
2020-03-26 20:02 [gentoo-commits] repo/gentoo:master commit in: dev-ada/libadalang/files/, dev-ada/libadalang/ Alfredo Tupone
2019-06-10 17:07 Alfredo Tupone
2018-11-12  7:43 Alfredo Tupone
2018-07-05 19:21 Alfredo Tupone

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=1677428565.78332276fb6993d830c1c869970f66726969921b.tupone@gentoo \
    --to=tupone@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