You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2024/04/04 12:55:00 UTC

[jira] [Commented] (HADOOP-19005) Upgrade Guava to 32.0.1 due to CVE-2023-2976

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

ASF GitHub Bot commented on HADOOP-19005:
-----------------------------------------

steveloughran commented on PR #6344:
URL: https://github.com/apache/hadoop/pull/6344#issuecomment-2037137869

   can you do a rebase and then a forced push? that'll kick off another build and test
   
   Internally we always use our hadoop thirdparty guava jar, this change will not directly cause problems.
   
   This declaration is for things we pull down, so we should get another test run in.
   
   we can't test downstream -we just have to see what breaks. 




> Upgrade Guava to 32.0.1 due to CVE-2023-2976
> --------------------------------------------
>
>                 Key: HADOOP-19005
>                 URL: https://issues.apache.org/jira/browse/HADOOP-19005
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: hadoop-thirdparty
>            Reporter: Bilwa S T
>            Assignee: Palakur Eshwitha Sai
>            Priority: Major
>              Labels: pull-request-available
>
> Upgrade Guava to 32.0.1 due to CVE-2023-2976



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org