Signed-off-by: Hans de Graaff
---
eclass/ruby-fakegem.eclass | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/eclass/ruby-fakegem.eclass b/eclass/ruby-fakegem.eclass
index 34eeff2fad96..76a80f6b9be2 100644
--- a/eclass/ruby-fakegem.eclass
+++ b/eclass/ruby-fakegem.eclas
Signed-off-by: Hans de Graaff
---
eclass/ruby-ng.eclass | 22 +++---
1 file changed, 11 insertions(+), 11 deletions(-)
diff --git a/eclass/ruby-ng.eclass b/eclass/ruby-ng.eclass
index d8afa207661f..ac9c117c0c02 100644
--- a/eclass/ruby-ng.eclass
+++ b/eclass/ruby-ng.eclass
@@ -8,
Signed-off-by: Hans de Graaff
---
eclass/ruby-fakegem.eclass | 14 --
1 file changed, 4 insertions(+), 10 deletions(-)
diff --git a/eclass/ruby-fakegem.eclass b/eclass/ruby-fakegem.eclass
index 9b2fd39ccf14..34eeff2fad96 100644
--- a/eclass/ruby-fakegem.eclass
+++ b/eclass/ruby-fakeg
Signed-off-by: Hans de Graaff
---
eclass/ruby-ng.eclass | 15 ++-
1 file changed, 6 insertions(+), 9 deletions(-)
diff --git a/eclass/ruby-ng.eclass b/eclass/ruby-ng.eclass
index 0c569bfcdcc6..d8afa207661f 100644
--- a/eclass/ruby-ng.eclass
+++ b/eclass/ruby-ng.eclass
@@ -8,7 +8,7 @@
Add support for EAPI 8 and remove support for EAPI 4. No real changes
needed, but standardized the EAPI check to match the proposed default.
Hans de Graaff (4):
eclass/ruby-ng.eclass: add EAPI 8 support
eclass/ruby-fakegem.eclass: add EAPI 8 support
eclass/ruby-ng.eclass: remove EAPI 4 suppo
> On Thu, 15 Jul 2021, Marek Szuba wrote:
> case "${EAPI:-0}" in
> - 0|1|2|3|4)
> + [0-6])
> die "Unsupported EAPI=${EAPI:-0} (too old) for ${ECLASS}"
> ;;
> - 5|6|7)
> + 7|8)
> ;;
> *)
> die "Unsupported EAPI=${EA
Signed-off-by: Marek Szuba
---
eclass/cuda.eclass | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/eclass/cuda.eclass b/eclass/cuda.eclass
index b1da77c69dd..08d2302d55b 100644
--- a/eclass/cuda.eclass
+++ b/eclass/cuda.eclass
@@ -1,11 +1,11 @@
-# Copyright 1999-2020 Ge
Like fortran-2 adding support for EAPI 8 appears to be trivial, unlike
fortran-2 we have no longer got any deprecated-EAPI ebuilds in the tree
inheriting it.
# John Helmert III (2021-07-14)
# Dead upstream, unfixed security issue.
# Removal on 2021-08-13. Bugs #755896, #781467.
net-proxy/polipo
signature.asc
Description: PGP signature
On Wed, Jul 14, 2021 at 10:49:34AM +0200, Andreas K. Huettel wrote:
> > >
> > > 1) either the severity assignment of this bug by the Security project as
> > > B1 wrong (i.e. it should have been classified "harmless")
> Well, over the last year or so every 2-3 months the (uninformed) discussio
On 2021-07-14 13:02, Ulrich Mueller wrote:
Shouldn't virtual/fortran go into BDEPEND in EAPIs 7 and 8?
Good point! I've created https://bugs.gentoo.org/802153 so that we do
not lose track of this, that said it is beyond the scope of the issue at
hand (the eclass will not behave any different
> On Wed, 14 Jul 2021, Marek Szuba wrote:
> On the plus side, nothing in here that requires changing to work with
> the new EAPI. On the minus side, we still got many EAPI-5 and 6
> consumers of this eclass in the tree so no chance of dropping support
> for these two at this time.
Shouldn't v
On 2021-07-13 18:54, Michał Górny wrote:
+media-sound/easyeffects is already available in the tree, and the
+remaining PipeWire-dependent ebuilds of media-sound/pulseeffects will
s/ebuilds/versions/.
Changed locally.
+be removed in 7 days.
Probably better to use an explicit date here. '
On 2021-07-13 18:35, William Hubbs wrote:
>> are there any non-cosmetic reasons for doing this?
Consistency with the rest of the tree. If you do a "git grep _R0" on the
eclass directory, the lua eclasses are the only ones that have this in
the names of the guard variables, and the eclasses the
Signed-off-by: Marek Szuba
---
eclass/fortran-2.eclass | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/eclass/fortran-2.eclass b/eclass/fortran-2.eclass
index 0bb00f475a2..9d0c71703e4 100644
--- a/eclass/fortran-2.eclass
+++ b/eclass/fortran-2.eclass
@@ -7,7 +7,7 @@
# @AU
On the plus side, nothing in here that requires changing to work with
the new EAPI. On the minus side, we still got many EAPI-5 and 6
consumers of this eclass in the tree so no chance of dropping support
for these two at this time.
> >
> > 1) either the severity assignment of this bug by the Security project as B1
> > wrong (i.e. it should have been classified "harmless")
> >
>
> The Gentoo model is not perfect and should be overhauled. However, it
> works for most things and sometimes bugs fall between the cracks.
>
> Th
17 matches
Mail list logo
