i686 failures

[Christopher]

I'm trying to revive rpms/hadoop, but am running into some failures[1] on
i686 in koji that I cannot reproduce locally in x86_64. The thing is... I
don't really have any good 32-bit environment to test this locally. Hadoop
isn't really suitable for 32-bit architectures (IMO) and I doubt it's a
well-tested upstream arch.

Any suggestions for how I should proceed? Is it really necessary that *all*
packages support i686 arch, even when it doesn't make sense for the
application's users?

[1]: http://koji.fedoraproject.org/koji/taskinfo?taskID=14521689

[Stephen Gallagher]

On 06/16/2016 03:16 PM, Christopher wrote:
>  I'm trying to revive rpms/hadoop, but am running into some
> failures[1] on i686
>  in koji that I cannot reproduce locally in x86_64. The thing is... I don't
>  really have any good 32-bit environment to test this locally. Hadoop isn't
>  really suitable for 32-bit architectures (IMO) and I doubt it's a well-tested
>  upstream arch.
>  
>  Any suggestions for how I should proceed? Is it really necessary that *all*
>  packages support i686 arch, even when it doesn't make sense for the
>  application's users?
>  
>  [1]: http://koji.fedoraproject.org/koji/taskinfo?taskID=14521689
>   

Probably best to engage upstream to figure out what's wrong (or if they want to
assert that i686 is unsupported). If i686 is truly not ever going to work,
that's what ExcludeArch is for.

[gil]

Il 16/06/2016 21:19, Stephen Gallagher ha scritto:
>  On 06/16/2016 03:16 PM, Christopher wrote:
> > >I'm trying to revive rpms/hadoop, but am running into some failures[1] on
> i686
> > >in koji that I cannot reproduce locally in x86_64. The thing is... I don't
> > >really have any good 32-bit environment to test this locally. Hadoop isn't
> > >really suitable for 32-bit architectures (IMO) and I doubt it's a
> well-tested
> > >upstream arch.
> > >
> > >Any suggestions for how I should proceed? Is it really necessary that*all*
> > >packages support i686 arch, even when it doesn't make sense for the
> > >application's users?
> > >
> > >[1]:http://koji.fedoraproject.org/koji/taskinfo?taskID=14521689
> > >
>  Probably best to engage upstream to figure out what's wrong (or if they want to
>  assert that i686 is unsupported). If i686 is truly not ever going to work,
>  that's what ExcludeArch is for.
>
>  
please do not write hogwash
the build fails because of maven-jar-plugin >= 3.0.0
is available a workaround, reported by mizdebsk
see [fedora-java] Common problems with maven-jar-plugin 3.0.0 @ 
java-devel(a)lists.fedoraproject.org
examples to resolve this inconvenience are available
see (in this case) 
http://pkgs.fedoraproject.org/cgit/cal10n.git/commit/?id=f6b14c5
or
http://pkgs.fedoraproject.org/cgit/rpms/easymock.git/tree/easymock-port-t...


regards
.g

[Dan Horák]

On Thu, 16 Jun 2016 19:16:38 +0000
Christopher <ctubbsii(a)fedoraproject.org&gt; wrote:

>  I'm trying to revive rpms/hadoop, but am running into some
> failures
>  [1] on i686 in koji that I cannot reproduce locally in x86_64. The
>  thing is... I don't really have any good 32-bit environment to test
>  this locally. Hadoop isn't really suitable for 32-bit architectures
>  (IMO) and I doubt it's a well-tested upstream arch.
>  
>  Any suggestions for how I should proceed? Is it really necessary that
>  *all* packages support i686 arch, even when it doesn't make sense for
>  the application's users? 
you should be able to reproduce the issue using mock, which is what
koji does too

with "mock -r fedora-rawhide-i386 hadoop.srpm" or maybe "fedpkg
mockbuild" can do it too


		Dan

[gil]

Il 16/06/2016 22:32, Dan Horák ha scritto:
>  On Thu, 16 Jun 2016 19:16:38 +0000
>  Christopher <ctubbsii(a)fedoraproject.org&gt; wrote:
>
> > I'm trying to revive rpms/hadoop, but am running into some failures
> > [1] on i686 in koji that I cannot reproduce locally in x86_64. The
> > thing is... I don't really have any good 32-bit environment to test
> > this locally. Hadoop isn't really suitable for 32-bit architectures
> > (IMO) and I doubt it's a well-tested upstream arch.
> >
> > Any suggestions for how I should proceed? Is it really necessary that
> > *all* packages support i686 arch, even when it doesn't make sense for
> > the application's users? 
how i wrote before is a problem related to newer
maven-jar-plugin release
if you run also for x64 build should fails

add this instruction:
%pom_xpath_inject 
"pom:plugin[pom:artifactId='maven-jar-plugin']/pom:executions" "
  <execution>
  <id>default-jar</id>
  <phase>skip</phase>
  </execution>" [PATH OF THE POM FILE WHERE HAPPEN THE FAILURE]

[Christopher]

On Thu, Jun 16, 2016 at 4:45 PM gil <puntogil(a)libero.it&gt; wrote:

>  Il 16/06/2016 22:32, Dan Horák ha scritto:
>
>  On Thu, 16 Jun 2016 19:16:38 +0000
>  Christopher <ctubbsii(a)fedoraproject.org&gt; wrote:
>
>
>  I'm trying to revive rpms/hadoop, but am running into some failures
>  [1] on i686 in koji that I cannot reproduce locally in x86_64. The
>  thing is... I don't really have any good 32-bit environment to test
>  this locally. Hadoop isn't really suitable for 32-bit architectures
>  (IMO) and I doubt it's a well-tested upstream arch.
>
>  Any suggestions for how I should proceed? Is it really necessary that
>  *all* packages support i686 arch, even when it doesn't make sense for
>  the application's users?
>
>  how i wrote before is a problem related to newer maven-jar-plugin release
>  if you run also for x64 build should fails
>
>  add this instruction:
>  %pom_xpath_inject
>  "pom:plugin[pom:artifactId='maven-jar-plugin']/pom:executions" "
>   <execution>
>   <id>default-jar</id>
>   <phase>skip</phase>
>   </execution>" [PATH OF THE POM FILE WHERE HAPPEN THE FAILURE]
>
>  
Thanks! This makes sense. I still don't understand why it didn't fail for
me locally (x86_64), but this should fix it regardless.

(Note to self: add rule to Gmail so I don't have to keep fishing gil's
email out of spam folder.)

[Mat Booth]

On 16 June 2016 at 20:16, Christopher <ctubbsii(a)fedoraproject.org&gt; wrote:

>  I'm trying to revive rpms/hadoop, but am running into some
> failures[1] on
>  i686 in koji that I cannot reproduce locally in x86_64. The thing is... I
>  don't really have any good 32-bit environment to test this locally. Hadoop
>  isn't really suitable for 32-bit architectures (IMO) and I doubt it's a
>  well-tested upstream arch.
>
>  Any suggestions for how I should proceed? Is it really necessary that
>  *all* packages support i686 arch, even when it doesn't make sense for the
>  application's users?
>
>  [1]: http://koji.fedoraproject.org/koji/taskinfo?taskID=14521689
>
>  --
>  devel mailing list
>  devel(a)lists.fedoraproject.org
>  https://lists.fedoraproject.org/admin/lists/[e-mail]
>
>  
Actually nothing to do with arch, all arches would fail, it just failed on
i686 first and koji cancelled the others ;-)

The maven-jar-plugin was updated to new version in Fedora, which has this
new behaviour, but the error message should be self-explanatory: "You have
to use a classifier to attach supplemental artifacts to the project instead
of replacing them." It is due to the jar:jar goal being executed twice for
the same artifact for some reason. Try eliminating the second invocation
from the pom file of the broken module.

-- 
Mat Booth
http://fedoraproject.org/get-fedora

[Christopher]

On Thu, Jun 16, 2016 at 7:40 PM Mat Booth <fedora(a)matbooth.co.uk&gt; wrote:

>  On 16 June 2016 at 20:16, Christopher
> <ctubbsii(a)fedoraproject.org&gt; wrote:
>
> > I'm trying to revive rpms/hadoop, but am running into some failures[1] on
> > i686 in koji that I cannot reproduce locally in x86_64. The thing is... I
> > don't really have any good 32-bit environment to test this locally. Hadoop
> > isn't really suitable for 32-bit architectures (IMO) and I doubt it's a
> > well-tested upstream arch.
> >
> > Any suggestions for how I should proceed? Is it really necessary that
> > *all* packages support i686 arch, even when it doesn't make sense for the
> > application's users?
> >
> > [1]: http://koji.fedoraproject.org/koji/taskinfo?taskID=14521689
> >
> > --
> > devel mailing list
> > devel(a)lists.fedoraproject.org
> > https://lists.fedoraproject.org/admin/lists/[e-mail]
> >
> >
>
>  Actually nothing to do with arch, all arches would fail, it just failed on
>  i686 first and koji cancelled the others ;-)
>
>  The maven-jar-plugin was updated to new version in Fedora, which has this
>  new behaviour, but the error message should be self-explanatory: "You have
>  to use a classifier to attach supplemental artifacts to the project instead
>  of replacing them." It is due to the jar:jar goal being executed twice for
>  the same artifact for some reason. Try eliminating the second invocation
>  from the pom file of the broken module.
>
>  
Yeah, I saw that error message and behavior, but I thought I might be able
to rule out the possibility that it was a simple maven problem, since it
built perfectly fine locally in mock. I figured it might be a problem with
maven executing different tasks under different arch's, but didn't have a
way to easily test a 32-bit arch locally to reproduce.

I'll try playing with fedpkg mock-config to see if I can do a mock build
with i686 arch locally.