On 02/19/2017 06:03 PM, Mike Gilbert wrote:
> On Sun, Feb 19, 2017 at 12:32 PM, Mike Pagano wrote:
>> Upstream does not version patches and every change breaks the manifest
>> which
>> breaks the tree. This results in a constant chasing of bugs since we can't
>> predict the breakage.
>
> Sounds
On 02/19/2017 05:55 PM, Andrew Savchenko wrote:
> On Sun, 19 Feb 2017 12:32:26 -0500 Mike Pagano wrote:
>> Upstream does not version patches and every change breaks the manifest
>> which
>> breaks the tree. This results in a constant chasing of bugs since we can't
>> predict the breakage.
>
> Ha
-crypt/dirmngr 20170218-01:23 alonbl 42e6297a6d
app-emacs/imaxima 20170213-12:27 ulm4d72ebeab4
dev-libs/pth 20170218-01:24 alonbl fd4eb6d607
dev-ml/ocamlgsl20170219-15:37 soap bfd2150a89
On Sun, Feb 19, 2017 at 12:32 PM, Mike Pagano wrote:
> Upstream does not version patches and every change breaks the manifest
> which
> breaks the tree. This results in a constant chasing of bugs since we can't
> predict the breakage.
Sounds good to me.
> @@ -1517,17 +1425,11 @@ kernel-2_src_pre
On Sun, 19 Feb 2017 12:32:26 -0500 Mike Pagano wrote:
> Upstream does not version patches and every change breaks the manifest
> which
> breaks the tree. This results in a constant chasing of bugs since we can't
> predict the breakage.
Have you tried to contact upstream and fix this issue there?
W dniu 19.02.2017, nie o godzinie 12∶32 -0500, użytkownik Mike Pagano
napisał:
> Upstream does not version patches and every change breaks the manifest
> which
> breaks the tree. This results in a constant chasing of bugs since we can't
> predict the breakage.
Shouldn't you also remove python-any-
Upstream does not version patches and every change breaks the manifest
which
breaks the tree. This results in a constant chasing of bugs since we can't
predict the breakage.
Signed-off-by: Mike Pagano
---
eclass/kernel-2.eclass | 102
+
1 file chan
W dniu 19.02.2017, nie o godzinie 09∶03 +0100, użytkownik Hans de Graaff
napisał:
> jruby has not been supported for some time. Removing support for it in
> EAPI 6 allows us to drop the java-utils-2 eclass which in turn also
> inherits eutils.
> ---
> eclass/ruby-ng.eclass | 10 +++---
> 1 fil
W dniu 19.02.2017, nie o godzinie 09∶03 +0100, użytkownik Hans de Graaff
napisał:
> This also removes the need for inheriting eutils in EAPI 6.
> ---
> eclass/ruby-ng.eclass | 23 ---
> 1 file changed, 20 insertions(+), 3 deletions(-)
>
> diff --git a/eclass/ruby-ng.eclass b/e
jruby has not been supported for some time. Removing support for it in
EAPI 6 allows us to drop the java-utils-2 eclass which in turn also
inherits eutils.
---
eclass/ruby-ng.eclass | 10 +++---
1 file changed, 7 insertions(+), 3 deletions(-)
diff --git a/eclass/ruby-ng.eclass b/eclass/ruby-n
This also removes the need for inheriting eutils in EAPI 6.
---
eclass/ruby-ng.eclass | 23 ---
1 file changed, 20 insertions(+), 3 deletions(-)
diff --git a/eclass/ruby-ng.eclass b/eclass/ruby-ng.eclass
index cd6a5ae..bc42e66 100644
--- a/eclass/ruby-ng.eclass
+++ b/eclass/ru
---
eclass/ruby-ng.eclass | 14 ++
1 file changed, 10 insertions(+), 4 deletions(-)
diff --git a/eclass/ruby-ng.eclass b/eclass/ruby-ng.eclass
index c83778d..cd6a5ae 100644
--- a/eclass/ruby-ng.eclass
+++ b/eclass/ruby-ng.eclass
@@ -81,7 +81,7 @@ case ${EAPI} in
0|1)
12 matches
Mail list logo