Failed to kick off scratch build.

list index out of range

Obviously 3.0.0 is not released yet, but there is a newer release version 2.6.1 that's available. 2.5.0 is 2 versions out of date.

Latest upstream release: v3.0.0-alpha-3.1
Current version/release in rawhide: 2.6.1-2.fc23
URL: https://github.com/google/protobuf

Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy

More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring

Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream.

Failed to kick off scratch build.

list index out of range

Latest upstream release: v3.0.0-beta-1
Current version/release in rawhide: 2.6.1-2.fc23
URL: https://github.com/google/protobuf

Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy

More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring

Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream.

Failed to kick off scratch build.

list index out of range

Latest upstream release: v3.0.0-beta-1-bzl-fix
Current version/release in rawhide: 2.6.1-2.fc23
URL: https://github.com/google/protobuf

Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy

More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring

Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream.

Failed to kick off scratch build.

list index out of range

Latest upstream release: 3.0.0-beta-2
Current version/release in rawhide: 2.6.1-4.fc24
URL: https://github.com/google/protobuf

Please, enable "javanano" sub-module

Latest upstream release: v3.0.0
Current version/release in rawhide: 2.6.1-5.fc25
URL: https://github.com/google/protobuf

Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy

More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring

Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream.

Based on the information from anitya:  https://release-monitoring.org/project/3715/

Patching or scratch build for protobuf-2.6.1 failed.

Created attachment 1185083 [details]
Rebase-helper rebase-helper-debug.log log file.
See for details and report the eventual error to rebase-helper https://github.com/phracek/rebase-helper/issues.

Patches were not touched. All were applied properly

Latest upstream release: v3.0.0-javalite
Current version/release in rawhide: 2.6.1-5.fc25
URL: https://github.com/google/protobuf

Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy

More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring

Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream.

Based on the information from anitya:  https://release-monitoring.org/project/3715/

Patching or scratch build for protobuf-2.6.1 failed.

Created attachment 1185395 [details]
Rebase-helper rebase-helper-debug.log log file.
See for details and report the eventual error to rebase-helper https://github.com/phracek/rebase-helper/issues.

Patches were not touched. All were applied properly

Latest upstream release: v3.0.1-javalite
Current version/release in rawhide: 2.6.1-5.fc25
URL: https://github.com/google/protobuf

Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy

More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring

Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream.

Based on the information from anitya:  https://release-monitoring.org/project/3715/

Patching or scratch build for protobuf-2.6.1 failed.

Created attachment 1185702 [details]
Rebase-helper rebase-helper-debug.log log file.
See for details and report the eventual error to rebase-helper https://github.com/phracek/rebase-helper/issues.

Patches were not touched. All were applied properly

It appears that the build really requires org.easymock.classextension now:

[ERROR] COMPILATION ERROR : 
[ERROR] /builddir/build/BUILD/protobuf-3.0.0/java/core/src/test/java/com/google/protobuf/ServiceTest.java:[47,35] package org.easymock.classextension does not exist

Latest upstream release: 3.0.1-jaalite
Current version/release in rawhide: 2.6.1-5.fc25
URL: https://github.com/google/protobuf

Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy

More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring

Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream.

Based on the information from anitya:  https://release-monitoring.org/project/3715/

Patching or scratch build for protobuf-2.6.1 failed.

Created attachment 1197734 [details]
Rebase-helper rebase-helper-debug.log log file.
See for details and report the eventual error to rebase-helper https://github.com/phracek/rebase-helper/issues.

Following patches has been deleted:
['lis-1.5.60-optflags.patch']

Latest upstream release: 3.0.2
Current version/release in rawhide: 2.6.1-5.fc25
URL: https://github.com/google/protobuf

Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy

More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring

Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream.

Based on the information from anitya:  https://release-monitoring.org/project/3715/

Patching or scratch build for protobuf-2.6.1 failed.

Created attachment 1198463 [details]
Rebase-helper rebase-helper-debug.log log file.
See for details and report the eventual error to rebase-helper https://github.com/phracek/rebase-helper/issues.

Patches were not touched. All were applied properly

Seeing compile errors with gcc6:

google/protobuf/unittest_lite.pb.cc: In member function 'virtual bool protobuf_unittest::TestAllExtensionsLite::IsInitialized() const':
google/protobuf/unittest_lite.pb.cc:8544:3: error: this 'if' clause does not guard... [-Werror=misleading-indentation]
   if (!_extensions_.IsInitialized()) return false;  return true;
   ^~
google/protobuf/unittest_lite.pb.cc:8544:53: note: ...this statement, but the latter is misleadingly indented as if it is guarded by the 'if'

tracked upstream

I can't figure out how to build the java components of 3.0.2.  Build fails when it appears it cannot access the generated classes:

[ERROR] COMPILATION ERROR : 
[INFO] -------------------------------------------------------------
[ERROR] /builddir/build/BUILD/protobuf-3.0.2/java/core/target/generated-test-sources/com/google/protobuf/test/TestWellKnownTypes.java:[322,30] cannot find symbol
  symbol:   class Any
  location: package com.google.protobuf

http://koji.fedoraproject.org/koji/taskinfo?taskID=15534310

Latest upstream release: 3.1.0
Current version/release in rawhide: 2.6.1-5.fc25
URL: https://github.com/google/protobuf

Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy

More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring

Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream.

Based on the information from anitya:  https://release-monitoring.org/project/3715/

Patching or scratch build for protobuf-2.6.1 failed.

Created attachment 1204375 [details]
Rebase-helper rebase-helper-debug.log log file.
See for details and report the eventual error to rebase-helper https://github.com/phracek/rebase-helper/issues.

Patches were not touched. All were applied properly

*** Bug 1351164 has been marked as a duplicate of this bug. ***

Latest upstream release: v3.1.0
Current version/release in rawhide: 2.6.1-5.fc25
URL: https://github.com/google/protobuf

Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy

More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring

Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream.

Based on the information from anitya:  https://release-monitoring.org/project/3715/

Patching or scratch build for protobuf-2.6.1 failed.

Created attachment 1215293 [details]
Rebase-helper rebase-helper-debug.log log file.
See for details and report the eventual error to rebase-helper https://github.com/phracek/rebase-helper/issues.

Following patches has been deleted:
['0002-use-futimens-if-available-instead-of-utime.patch']

What's the latest with this? Whill we get python3 bindings too when 3.1.0 lands?

Created attachment 1216841 [details]
protobuf.spec

I've been unable to get the java components to build.  Perhaps a java expert can figure it out.  I've attached my updated spec.

Orion, ask java-devel for help, they are very helpful:
 https://lists.fedoraproject.org/admin/lists/java-devel.lists.fedoraproject.org/

Good idea. Asked: https://lists.fedoraproject.org/archives/list/java-devel@lists.fedoraproject.org/thread/JMIIX4WYLUTEDW34GGO5G5MIJL2HVG2D/

Created attachment 1217388 [details]
protobuf.spec

Task info: http://koji.fedoraproject.org/koji/taskinfo?taskID=16287066

- enable javanano sub module used by https://github.com/googlei18n/libphonenumber
- split java artifacts in they own sub packages
- marked as noarch "parent" (POM) sub package
- minor changes to adapt to current guidelines:
  * remove deprecate Group field
  * add protobuf-java backward compatibility symlink

TODO: Test failures; get them fixed and remove || :

Test failure is explored/reported here: https://github.com/google/protobuf/issues/631

It looks like just an artifact of the testing framework so I think it's safe to move forward with this.  gil, can you check this in or do you need me to?

(In reply to Orion Poplawski from comment #47)
> Test failure is explored/reported here:
> https://github.com/google/protobuf/issues/631
> 
> It looks like just an artifact of the testing framework so I think it's safe
> to move forward with this.  gil, can you check this in or do you need me to?

if you have time, i would prefer, you to move forward with this. because i have some doubts about Java sub packages. should all be marked as noarch, because they are installed in all _javadir ...

Any chance grpc.io will packaged alongside with protobuf 3+?

Hi Orion, can you please push this to rawhide?

Well, I was doing to test builds here first - https://copr.fedorainfracloud.org/coprs/orion/protobuf3/builds/

Some dependent packages are failing there and it would be nice to get them fixed up before breaking rawhide.

So with this update, the jar file moves from:

/usr/share/java/protobuf.jar

to

/usr/share/java/protobuf/protobuf-java.jar

This breaks mesos at the moment because it looks for the former.  We can override by setting PROTOBUF_JAR to the proper path.  What's the best way to determine this path at build time?  Is there some java/maven tool we can use?

In any case, mesos has been FTBFS for a while so it's not a holdup.  Also, fawkes is FTBFS due to the openssl update.  Building ola turned up some missing python requires.  So I think we're good to go now.

(In reply to Orion Poplawski from comment #52)
> So with this update, the jar file moves from:
> 
> /usr/share/java/protobuf.jar
> 
> to
> 
> /usr/share/java/protobuf/protobuf-java.jar
> 
> This breaks mesos at the moment because it looks for the former.  We can
> override by setting PROTOBUF_JAR to the proper path.  What's the best way to
> determine this path at build time?  Is there some java/maven tool we can use?
> 
See in my spec file this line "# Backward compatibility symlink
%mvn_file :protobuf-java:jar: %{name}/%{name} %{name}"
could be changenf in "# Backward compatibility symlink
%mvn_file :protobuf-java:jar: %{name}/%{name}-java %{name}" or as you want
regards

Thanks.  Needed to restructure builds so all of the %mvn macros run in the same directory.

Added python3 support in -4.  We're building now, just waiting on arm...

Thanks to you!
perhaps, the package that depend on protobuf* should be integrated (even momentarily) in https://apps.fedoraproject.org/koschei/

I think everything should be in koschei - but you need to be an admin on a package to add it.

Damn this arm build is slow - why is java on arm so slow?

(In reply to Orion Poplawski from comment #56)
> I think everything should be in koschei - but you need to be an admin on a
> package to add it.
> 
> Damn this arm build is slow - why is java on arm so slow?

Little available memory, consider for testing task to disable for this arches.

e.g.
%if %{with java}
# Waste of time on some arches
%ifarch %{arm}
opts='-f'
%endif
%mvn_build -s $opts -- -f java/pom.xml
%endif

maybe the same for
%ifnarch %{arm}
%check
# TODO: failures; get them fixed and remove || :
# https://github.com/google/protobuf/issues/631
make %{?_smp_mflags} check || :
%endif

I ended up just disabling the IsValidUtf8Test - https://github.com/google/protobuf/issues/2389

That brings the build time down to a manageable 4-5 hours, much of which is just doing the java build.  I think the lack of JIT on arm is the killer here.