Bug#934665: upload grpc and protobuf to unstable

[GCS]

On Wed, Mar 18, 2020 at 10:03 PM Salvatore Bonaccorso  wrote:
> On Mon, Dec 23, 2019 at 05:47:39PM +0530, Pirate Praveen wrote:
> > On Mon, 18 Nov 2019 11:27:28 +0530 Pirate Praveen 
> > wrote:
> > > missed anbox from the second list sent by Nilesh. Now confirmed anbox
> > > also fails.
> >
> > It's been a month since we filed bugs with failing packages, can we request
> > transition now?
>
> Out of interest, was there any progress with this?
 It's really the time to push this now. Recently rebuilt affected
packages with the new protobuf package version and there's only one
FTBFS (lazily maintained package with low popcon). I couldn't get the
auto-grpc transition tracker, will try to find that out this
afternoon.

Cheers,
Laszlo/GCS

Bug#934665: upload grpc and protobuf to unstable

[Salvatore Bonaccorso]

hi all,

On Mon, Dec 23, 2019 at 05:47:39PM +0530, Pirate Praveen wrote:
> On Mon, 18 Nov 2019 11:27:28 +0530 Pirate Praveen 
> wrote:
> > missed anbox from the second list sent by Nilesh. Now confirmed anbox
> > also fails.
> 
> It's been a month since we filed bugs with failing packages, can we request
> transition now?

Out of interest, was there any progress with this?

I cannot help actually (but in my understanding Pirate proposed help),
and my question is backgrounded on seeing gitlab itself on the worry
to see in unstable an ancient gitlab version and the need of tracking
the open CVEs as per
https://security-tracker.debian.org/tracker/source-package/gitlab .

Regards,
Salvatore

Bug#934665: upload grpc and protobuf to unstable

[Pirate Praveen]

On Mon, 18 Nov 2019 11:27:28 +0530 Pirate Praveen 
 wrote:
missed anbox from the second list sent by Nilesh. Now confirmed anbox 
also fails.


It's been a month since we filed bugs with failing packages, can we 
request transition now?

Bug#934665: upload grpc and protobuf to unstable

[Pirate Praveen]

On തി, Nov 18, 2019 at 10:31, Pirate Praveen 
 wrote:
opencv built fine without ccache in chroot. So only ola and 
ignition-transport are the relvant failures now.


missed anbox from the second list sent by Nilesh. Now confirmed anbox 
also fails.

Bug#934665: upload grpc and protobuf to unstable

[Pirate Praveen]

On തി, Nov 18, 2019 at 01:16, Pirate Praveen 
 wrote:
nageru was a real failure but its maintainer fixed it as soon as I 
filed the bug. opencv seems to be fine (still building).


opencv built fine without ccache in chroot. So only ola and 
ignition-transport are the relvant failures now.

Bug#934665: upload grpc and protobuf to unstable

[Pirate Praveen]

On തി, Nov 18, 2019 at 00:36, Nilesh Patra  
wrote:



On Sun, 17 Nov 2019, 23:44 Pirate Praveen, > wrote:
These packages should rebuilt without ccache in chroot and confirm 
if ccache caused the failure: nageru, opencv


I will try checking them.



nageru was a real failure but its maintainer fixed it as soon as I 
filed the bug. opencv seems to be fine (still building).


I also rebuilt for gRPC, and I found no failed rebuilds on the 
reverse build dependencies for the same.




Thanks, that means we have to worry about ola and ignition-transport 
only.


Laszlo,

Probably we should ask release team for transition as they take time to 
give us a slot anyway and meanwhile we can try to fix the remaining 
ones.



Thanks and regards
Nilesh

Bug#934665: upload grpc and protobuf to unstable

[Nilesh Patra]

On Sun, 17 Nov 2019, 23:44 Pirate Praveen,  wrote:

> So as summary, the packages that might be failed due to protobuf change are
>
> cubemap, ignition-transport (with ignition-msgs might fix gazebo), ola,
> osmosis
>
> I will file bugs against these.
>

Thanks a lot!

These packages should rebuilt without ccache in chroot and confirm if
> ccache caused the failure: nageru, opencv
>

I will try checking them.

I also rebuilt for gRPC, and I found no failed rebuilds on the reverse
build dependencies for the same.

Thanks and regards
Nilesh

Bug#934665: upload grpc and protobuf to unstable

[Pirate Praveen]

On ഞാ, Nov 17, 2019 at 23:44, Pirate Praveen 
 wrote:

vlc rebuild is still going on


vlc was built successfully.

Bug#934665: upload grpc and protobuf to unstable

[Pirate Praveen]

So as summary, the packages that might be failed due to protobuf change 
are


cubemap, ignition-transport (with ignition-msgs might fix gazebo), ola, 
osmosis


I will file bugs against these.

These packages should rebuilt without ccache in chroot and confirm if 
ccache caused the failure: nageru, opencv


vlc rebuild is still going on

Bug#934665: upload grpc and protobuf to unstable

[Pirate Praveen]

On ഞാ, Nov 17, 2019 at 17:33, Nilesh Patra  
wrote:





 But the latest available package version is 3.10.1-1 and the rebuild
 should be done with that.


Rebuilt with the new version, these are the newer failing depends:
anbox, astroidmail, bookkeeper, collectd, containerd, 
cubemap,docker.io , etcd, gazebo, go-dep, gobgp, 
ignition-transport, mahimahi, nageru, ola, opencv, osmosis, shogun, 
vlc


mahimahi already FTBFS with gcc 9 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925774


nageru - possibly failed due to ccache in chroot, try without ccache in 
chroot


ola - seems a related failure

g++ -DHAVE_CONFIG_H -I.   -Wdate-time -D_FORTIFY_SOURCE=2 -I./include 
-I./include -Wall -Wformat -W -fvisibility-inlines-hidden -pthread 
-Werror -Werror -Wno-error=unused-parameter 
-Wno-error=deprecated-declarations -Wno-error=sign-compare 
-Wno-error=deprecated-declarations -Wno-error=unused-parameter 
-std=gnu++11 -Wno-error=deprecated-declarations -pthread -c -o 
protoc/ola_protoc_plugin-ola-protoc-generator-plugin.o `test -f 
'protoc/ola-protoc-generator-plugin.cpp' || echo 
'./'`protoc/ola-protoc-generator-plugin.cpp
protoc/StrUtil.cpp: In function ‘char* ola::FastHexToBuffer(int, 
char*)’:
protoc/StrUtil.cpp:256:3: error: ‘GOOGLE_CHECK’ was not declared in 
this scope

 256 |   GOOGLE_CHECK(i >= 0)
 |   ^~~~
protoc/StrUtil.cpp: In function ‘char* 
ola::FastUInt64ToBufferLeft(uint64_t, char*)’:
protoc/StrUtil.cpp:436:3: error: ‘GOOGLE_DCHECK_LT’ was not 
declared in this scope

 436 |   GOOGLE_DCHECK_LT(digits, 100);
 |   ^~~~

opencv - possibly ccache related failure, try without ccache in chroot

shogun - ftbfs with gcc 9 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925827


osmosis - seems related failure

/<>/osmosis-osm-binary/gen-src/main/java/org/openstreetmap/osmosis/osmbinary/Osmformat.java:13871: 
error: cannot find symbol

 Visitor visitor = (Visitor) arg0;
 ^
 symbol:   class Visitor
 location: class Relation
/<>/osmosis-osm-binary/gen-src/main/java/org/openstreetmap/osmosis/osmbinary/Osmformat.java:13871: 
error: cannot find symbol

 Visitor visitor = (Visitor) arg0;
^
 symbol:   class Visitor
 location: class Relation
/<>/osmosis-osm-binary/gen-src/main/java/org/openstreetmap/osmosis/osmbinary/Osmformat.java:13882: 
error: cannot find symbol
 if (visitor == 
com.google.protobuf.GeneratedMessageLite.MergeFromVisitor

^
 symbol:   variable MergeFromVisitor
 location: class GeneratedMessageLite
/<>/osmosis-osm-binary/gen-src/main/java/org/openstreetmap/osmosis/osmbinary/Osmformat.java:13888: 
error: an enum switch case label must be the unqualified name of an 
enumeration constant

   case MERGE_FROM_STREAM: {
^
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: 
/<>/osmosis-osm-binary/src/main/java/org/openstreetmap/osmosis/osmbinary/StringTable.java 
uses or overrides a deprecated API.

Note: Recompile with -Xlint:deprecation for details.
98 errors
:osmosis-osm-binary:compileJava FAILED
:osmosis-osm-binary:compileJava (Thread[Task worker for ':' Thread 
2,5,main]) completed. Took 6.226 secs.
:osmosis-core:compileJava (Thread[Task worker for ':',5,main]) 
completed. Took 6.785 secs.
:osmosis-hstore-jdbc:javadoc (Thread[main,5,main]) completed. Took 4.72 
secs.


FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':osmosis-osm-binary:compileJava'.
> Compilation failed; see the compiler error output for details.

Bug#934665: upload grpc and protobuf to unstable

[Pirate Praveen]

On ഞാ, Nov 17, 2019 at 17:33, Nilesh Patra  
wrote:





 But the latest available package version is 3.10.1-1 and the rebuild
 should be done with that.


Rebuilt with the new version, these are the newer failing depends:
anbox, astroidmail, bookkeeper, collectd, containerd, 
cubemap,docker.io , etcd, gazebo, go-dep, gobgp, 
ignition-transport, mahimahi, nageru, ola, opencv, osmosis, shogun, 
vlc





continuing the analysis,

gobgp already FTBFS 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871692


relevant failure

google.golang.org/grpc
github.com/osrg/gobgp/api
# github.com/osrg/gobgp/api
src/github.com/osrg/gobgp/api/grpc_server.go:2753:75: too few values in 
 literal

github.com/spf13/cobra

go-dep already failing in reproducible builds 
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/go-dep.html 
(seems related to upstream golang issue)


ignition-transport many errors like this

149 |   ::google::protobuf::uint8* 
InternalSerializeWithCachedSizesToArray(
 |  
^~~
In file included from 
/usr/include/ignition/msgs1/ignition/msgs/MessageTypes.hh:103,
from 
/usr/include/ignition/msgs1/ignition/msgs/Utility.hh:29,

from /usr/include/ignition/msgs1/ignition/msgs.hh:25,
from 
/<>/include/ignition/transport/Node.hh:32,

from /<>/src/Node.cc:31:
/usr/include/ignition/msgs1/ignition/msgs/model_configuration.pb.h:142:8: 
error: ‘bool 
ignition::msgs::ModelConfiguration::MergePartialFromCodedStream(google::protobuf::io::CodedInputStream*)’ 
marked ‘final’, but is not virtual


possibly ignition-msgs needs to be rebuilt first.

Bug#934665: upload grpc and protobuf to unstable

[Pirate Praveen]

On ഞാ, Nov 17, 2019 at 17:16, Pirate Praveen 
 wrote:

will check the remaining ones as well now.


docker.io - 19.03.4+dfsg2-2 built fine

etcd - I think the relevant failure is

github.com/coreos/etcd/etcdserver/auth
# github.com/coreos/etcd/etcdserver/api/etcdhttp
src/github.com/coreos/etcd/etcdserver/api/etcdhttp/base.go:57:26: 
undefined: prometheus.Handler

github.com/coreos/etcd/etcdserver/api/v3rpc

but it is ftbfs already 
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/etcd.html


gazebo - not in testing for so many days and seems to be related to 
ignition not rebuilt with new protobuf


In file included from /<>/gazebo/msgs/msgs.hh:32,
from /<>/gazebo/msgs/msgs.cc:27:
/usr/include/ignition/msgs1/ignition/msgs/color.pb.h:17:2: error: 
#error This file was generated by an older version of protoc which is
  17 | #error This file was generated by an older version of protoc 
which is

 |  ^
/usr/include/ignition/msgs1/ignition/msgs/color.pb.h:18:2: error: 
#error incompatible with your Protocol Buffer headers. Please

  18 | #error incompatible with your Protocol Buffer headers.  Please
 |  ^
/usr/include/ignition/msgs1/ignition/msgs/color.pb.h:19:2: error: 
#error regenerate this file with a newer version of protoc.

  19 | #error regenerate this file with a newer version of protoc.
 |  ^
In file included from 
/usr/include/ignition/msgs1/ignition/msgs/color.pb.h:33,

from /<>/gazebo/msgs/msgs.hh:32,
from /<>/gazebo/msgs/msgs.cc:27:
/usr/include/ignition/msgs1/ignition/msgs/header.pb.h:17:2: error: 
#error This file was generated by an older version of protoc which is
  17 | #error This file was generated by an older version of protoc 
which is

 |  ^
/usr/include/ignition/msgs1/ignition/msgs/header.pb.h:18:2: error: 
#error incompatible with your Protocol Buffer headers. Please

  18 | #error incompatible with your Protocol Buffer headers.  Please
 |  ^
/usr/include/ignition/msgs1/ignition/msgs/header.pb.h:19:2: error: 
#error regenerate this file with a newer version of protoc.

  19 | #error regenerate this file with a newer version of protoc.
 |  ^
In file included from 
/usr/include/ignition/msgs1/ignition/msgs/header.pb.h:33,
from 
/usr/include/ignition/msgs1/ignition/msgs/color.pb.h:33,

from /<>/gazebo/msgs/msgs.hh:32,
from /<>/gazebo/msgs/msgs.cc:27:
/usr/include/ignition/msgs1/ignition/msgs/time.pb.h:17:2: error: #error 
This file was generated by an older version of protoc which is
  17 | #error This file was generated by an older version of protoc 
which is

 |  ^
/usr/include/ignition/msgs1/ignition/msgs/time.pb.h:18:2: error: #error 
incompatible with your Protocol Buffer headers. Please

  18 | #error incompatible with your Protocol Buffer headers.  Please
 |  ^
/usr/include/ignition/msgs1/ignition/msgs/time.pb.h:19:2: error: #error 
regenerate this file with a newer version of protoc.

  19 | #error regenerate this file with a newer version of protoc.
 |  ^
In file included from /<>/gazebo/msgs/msgs.hh:33,
from /<>/gazebo/msgs/msgs.cc:27:
/usr/include/ignition/msgs1/ignition/msgs/material.pb.h:17:2: error: 
#error This file was generated by an older version of protoc which is
  17 | #error This file was generated by an older version of protoc 
which is

 |  ^
/usr/include/ignition/msgs1/ignition/msgs/material.pb.h:18:2: error: 
#error incompatible with your Protocol Buffer headers. Please

  18 | #error incompatible with your Protocol Buffer headers.  Please
 |  ^
/usr/include/ignition/msgs1/ignition/msgs/material.pb.h:19:2: error: 
#error regenerate this file with a newer version of protoc.

  19 | #error regenerate this file with a newer version of protoc.
 |  ^
In file included from 
/usr/include/ignition/msgs1/ignition/msgs/header.pb.h:33,
from 
/usr/include/ignition/msgs1/ignition/msgs/color.pb.h:33,

from /<>/gazebo/msgs/msgs.hh:32,
from /<>/gazebo/msgs/msgs.cc:27:
/usr/include/ignition/msgs1/ignition/msgs/time.pb.h:139:8: error: 
‘bool 
ignition::msgs::Time::MergePartialFromCodedStream(google::protobuf::io::CodedInputStream*)’ 
marked ‘final’, but is not virtual

 139 |   bool MergePartialFromCodedStream(
 |^~~
/usr/include/ignition/msgs1/ignition/msgs/time.pb.h:141:8: error: 
‘void 
ignition::msgs::Time::SerializeWithCachedSizes(google::protobuf::io::CodedOutputStream*) 
const’ marked ‘final’, but is not virtual

 141 |   void SerializeWithCachedSizes(
 |^~~~
/usr/include/ignition/msgs1/ignition/msgs/time.pb.h:143:30: error: 
‘google::protobuf::uint8* 
ignition::msgs::Time::InternalSerializeWithCachedSizesToArray(bool, 
google::protobuf::uint8*) const’ marked ‘final’, but is not 
virtual
 143 |   ::google::protobuf::uint8* 

Bug#934665: upload grpc and protobuf to unstable

[Nilesh Patra]

 But the latest available package version is 3.10.1-1 and the rebuild
> should be done with that.
>

Rebuilt with the new version, these are the newer failing depends:
anbox, astroidmail, bookkeeper, collectd, containerd, cubemap,docker.io,
etcd, gazebo, go-dep, gobgp, ignition-transport, mahimahi, nageru, ola,
opencv, osmosis, shogun, vlc

Thanks and Regards
Nilesh

Bug#934665: upload grpc and protobuf to unstable

[Pirate Praveen]

astroidmail - failing with exact same error already, so we can ignore it

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/astroidmail.html

bookkeeper - already FTBFS and not in testing

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906340

collectd 5.9.2.g-1 built fine

containerd - not in testing, ftbfs with missing build dependencies,
possibly rebuild version in experimental (but not a blocker I think)

cubemap - fails with the following error (rebuild in unstable works)

g++ -o cubemap main.o client.o server.o stream.o udpstream.o
serverpool.o input.o input_stats.o httpinput.o udpinput.o parse.o
config.o acceptor.o stats.o accesslog.o thread.o util.o log.o
metacube2.o sa_compare.o timespec.o state.pb.o tlse/tlse.o -lprotobuf
-lsystemd -ltomcrypt -Wl,-z,relro
/usr/bin/ld: thread.o: undefined reference to symbol
'pthread_join@@GLIBC_2.2.5'
/usr/bin/ld: /lib/x86_64-linux-gnu/libpthread.so.0: error adding
symbols: DSO missing from command line
collect2: error: ld returned 1 exit status

will check the remaining ones as well now.

Bug#934665: upload grpc and protobuf to unstable

[Pirate Praveen]

On Thu, 7 Nov 2019 18:53:29 +0530 Nilesh  wrote:
> 
> I rebuilt the reverse build dependencies for protobuf-3.10.0 and these
> are the packages that failed:
>

Thanks a lot for this.

> astroidmail, bookkeeper, collectd, containerd, cubemap, docker.io, etcd,
> gazebo, go-dep, gobgp, ignition-transport, mahimahi, nageru, ola,
> opencv, osmosis, paraview, shogun, vlc
> 
> I think we can try fixing them and go ahead with transitioning protobuf.

First we should file bugs against these packages with severity important. 
Include the relevant logs and ask them to fix it.

> Thanks and Regards
> 
> Nilesh
> 
> 
> 

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

Bug#934665: upload grpc and protobuf to unstable

[GCS]

Hi Nilesh,

On Thu, Nov 7, 2019 at 2:27 PM Nilesh  wrote:
> I rebuilt the reverse build dependencies for protobuf-3.10.0 and these
> are the packages that failed:
 But the latest available package version is 3.10.1-1 and the rebuild
should be done with that.

> astroidmail, bookkeeper, collectd, containerd, cubemap, docker.io, etcd,
> gazebo, go-dep, gobgp, ignition-transport, mahimahi, nageru, ola,
> opencv, osmosis, paraview, shogun, vlc
 Any pointers what was the issue with these packages?

> I think we can try fixing them and go ahead with transitioning protobuf.
 Next thing is that ProtoBuf is a double transition with gRPC. Any
rebuild done with that and its reverse dependencies?
For your interest, just uploaded gRPC 1.25.0 to experimental, but it
will stuck in NEW queue.

Regards,
Laszlo/GCS

Bug#934665: upload grpc and protobuf to unstable

[Nilesh]

On Sun, 8 Sep 2019 23:37:10 +0200
=?UTF-8?B?TMOhc3psw7MgQsO2c3rDtnJtw6lueWkgKEdDUyk=?=  wrote:
> On Sun, Sep 8, 2019 at 3:03 PM Pirate Praveen
 wrote:
> > Now autopkgtest results for packages in experimental is also available.
> >
> > See https://release.debian.org/britney/pseudo-excuses-experimental.html
> >
> > Migration status for protobuf (3.6.1.3-2 to 3.9.1-2): BLOCKED:
Rejected/violates migration policy/introduces a regression
> All of these are expected. Need to transition (rebuild) these with
> the Protobuf 3.9.1 version. But as the 3.10.0 release is around the
> corner, I plan to package its RC release tomorrow.
>
> Regards,
> Laszlo/GCS
>

Hi!

I rebuilt the reverse build dependencies for protobuf-3.10.0 and these
are the packages that failed:

astroidmail, bookkeeper, collectd, containerd, cubemap, docker.io, etcd,
gazebo, go-dep, gobgp, ignition-transport, mahimahi, nageru, ola,
opencv, osmosis, paraview, shogun, vlc

I think we can try fixing them and go ahead with transitioning protobuf.

Thanks and Regards

Nilesh

Bug#934665: upload grpc and protobuf to unstable

[GCS]

On Sun, Sep 8, 2019 at 3:03 PM Pirate Praveen  wrote:
> Now autopkgtest results for packages in experimental is also available.
>
> See https://release.debian.org/britney/pseudo-excuses-experimental.html
>
> Migration status for protobuf (3.6.1.3-2 to 3.9.1-2): BLOCKED: 
> Rejected/violates migration policy/introduces a regression
 All of these are expected. Need to transition (rebuild) these with
the Protobuf 3.9.1 version. But as the 3.10.0 release is around the
corner, I plan to package its RC release tomorrow.

Regards,
Laszlo/GCS

Bug#934665: upload grpc and protobuf to unstable

[Pirate Praveen]

On Tue, 13 Aug 2019 12:33:08 +0530 Pirate Praveen  
wrote:
> package: grpc, protobuf
> 
> Hi Laszlo,
> 
> Did you get a chance to rebuild all reverse dependencies yet? If you
> have not started, I'd like to help with the rebuilds.
> 
> I'd like to get gitlab to unstable and I need these two in unstable.
> 
> Thanks
> Praveen
> 

Now autopkgtest results for packages in experimental is also available.

See https://release.debian.org/britney/pseudo-excuses-experimental.html

Migration status for protobuf (3.6.1.3-2 to 3.9.1-2): BLOCKED: 
Rejected/violates migration policy/introduces a regression

Issues preventing migration:

autopkgtest for ignition-msgs/1.0.0+dfsg1-5: amd64: Regression ♻

autopkgtest for ignition-transport/4.0.0+dfsg-4: amd64: Regression ♻

autopkgtest for ola/0.10.7.nojsmin-2: amd64: Regression ♻

Additional info:

Cannot be tested by piuparts (not a blocker) - (no link yet)

14 days old


-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

Bug#934665: upload grpc and protobuf to unstable

[Pirate Praveen]

package: grpc, protobuf

Hi Laszlo,

Did you get a chance to rebuild all reverse dependencies yet? If you
have not started, I'd like to help with the rebuilds.

I'd like to get gitlab to unstable and I need these two in unstable.

Thanks
Praveen