[ 
https://issues.apache.org/jira/browse/HADOOP-13363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16246154#comment-16246154
 ] 

Dmitry Chuyko commented on HADOOP-13363:
----------------------------------------

Current usage scheme leads to a small tricky problem. Consider available 
versions:

apt-cache showpkg protobuf-compiler

'2.6.1-1.3' only on Ununtu 16.04 (LTS) aarch64
'3.0.0-9ubuntu5' only on Ubuntu 17.10 amd64

Probably both versions will work when manually installed.

Also if I understand it right build system docker image will need an update.

Not sure about other distros and release schedules but it looks right to stick 
to a current version from some LTS distro of next such version. For next LTS 
Ubuntu it is currently also 3.0.0: '3.0.0-9ubuntu5' 
https://packages.ubuntu.com/search?keywords=protobuf-compiler

> Upgrade protobuf from 2.5.0 to something newer
> ----------------------------------------------
>
>                 Key: HADOOP-13363
>                 URL: https://issues.apache.org/jira/browse/HADOOP-13363
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: build
>    Affects Versions: 3.0.0-alpha1, 3.0.0-alpha2
>            Reporter: Allen Wittenauer
>            Assignee: Tsuyoshi Ozawa
>         Attachments: HADOOP-13363.001.patch, HADOOP-13363.002.patch, 
> HADOOP-13363.003.patch, HADOOP-13363.004.patch, HADOOP-13363.005.patch
>
>
> Standard protobuf 2.5.0 does not work properly on many platforms.  (See, for 
> example, https://gist.github.com/BennettSmith/7111094 ).  In order for us to 
> avoid crazy work arounds in the build environment and the fact that 2.5.0 is 
> starting to slowly disappear as a standard install-able package for even 
> Linux/x86, we need to either upgrade or self bundle or something else.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to