It seems can not check signature: yumwang@G9L07H60PK Downloads % gpg --keyserver hkps://keys.openpgp.org --recv-key FC3AE3A7EAA1BAC98770840E7E1ABCC53AAA2216 gpg: key 7E1ABCC53AAA2216: no user ID gpg: Total number processed: 1 yumwang@G9L07H60PK Downloads % gpg --batch --verify spark-3.5.0-bin-hadoop3.tgz.asc spark-3.5.0-bin-hadoop3.tgz gpg: Signature made 二 8/29 14:46:14 2023 CST gpg: using RSA key FC3AE3A7EAA1BAC98770840E7E1ABCC53AAA2216 gpg: issuer "liyuanj...@apache.org" gpg: Can't check signature: No public key
On Thu, Aug 31, 2023 at 11:36 AM Sean Owen <sro...@apache.org> wrote: > It worked fine after I ran it again I included "package test" instead of > "test" (I had previously run "install") +1 > > On Wed, Aug 30, 2023 at 6:06 AM yangjie01 <yangji...@baidu.com> wrote: > >> Hi, Sean >> >> >> >> I have performed testing with Java 17 and Scala 2.13 using maven (`mvn >> clean install` and `mvn package test`), and have not encountered the issue >> you mentioned. >> >> >> >> The test for the connect module depends on the `spark-protobuf` module to >> complete the `package,` was it successful? Or could you provide the test >> command for me to verify? >> >> >> >> Thanks, >> >> Jie Yang >> >> >> >> *发件人**: *Dipayan Dev <dev.dipaya...@gmail.com> >> *日期**: *2023年8月30日 星期三 17:01 >> *收件人**: *Sean Owen <sro...@gmail.com> >> *抄送**: *Yuanjian Li <xyliyuanj...@gmail.com>, Spark dev list < >> dev@spark.apache.org> >> *主题**: *Re: [VOTE] Release Apache Spark 3.5.0 (RC3) >> >> >> >> Can we fix this bug in Spark 3.5.0? >> >> https://issues.apache.org/jira/browse/SPARK-44884 >> <https://mailshield.baidu.com/check?q=cuZ00%2b0zbrN1TxhY0HTgyAub3lGN0J5FSjbfsBPL0yoIU71LdJTYoAVapkFmUjxgZT0WPdJBLus%3d> >> >> >> >> >> On Wed, Aug 30, 2023 at 11:51 AM Sean Owen <sro...@gmail.com> wrote: >> >> It looks good except that I'm getting errors running the Spark Connect >> tests at the end (Java 17, Scala 2.13) It looks like I missed something >> necessary to build; is anyone getting this? >> >> >> >> [ERROR] [Error] >> /tmp/spark-3.5.0/connector/connect/server/target/generated-test-sources/protobuf/java/org/apache/spark/sql/protobuf/protos/TestProto.java:9:46: >> error: package org.sparkproject.spark_protobuf.protobuf does not exist >> >> >> >> On Tue, Aug 29, 2023 at 11:25 AM Yuanjian Li <xyliyuanj...@gmail.com> >> wrote: >> >> Please vote on releasing the following candidate(RC3) as Apache Spark >> version 3.5.0. >> >> >> >> The vote is open until 11:59pm Pacific time *Aug 31st* and passes if a >> majority +1 PMC votes are cast, with a minimum of 3 +1 votes. >> >> >> >> [ ] +1 Release this package as Apache Spark 3.5.0 >> >> [ ] -1 Do not release this package because ... >> >> >> >> To learn more about Apache Spark, please see http://spark.apache.org/ >> <https://mailshield.baidu.com/check?q=eJcUboQ1HRRomPZKEwRzpl69wA8DbI%2fNIiRNsQ%3d%3d> >> >> >> >> The tag to be voted on is v3.5.0-rc3 (commit >> 9f137aa4dc43398aafa0c3e035ed3174182d7d6c): >> >> https://github.com/apache/spark/tree/v3.5.0-rc3 >> <https://mailshield.baidu.com/check?q=M8bk44BhojXSL5a%2bfp%2fAiXPgzvf1z8IY9RiBF4qXAQxEMaMvBeSTzrTW4aDYfv61SNEvZQ%3d%3d> >> >> >> >> The release files, including signatures, digests, etc. can be found at: >> >> https://dist.apache.org/repos/dist/dev/spark/v3.5.0-rc3-bin/ >> <https://mailshield.baidu.com/check?q=Y5B1AfmG5NfNnTciPizGUdNVAVSofSiQkkSPsdSlVX%2fPPccSlHQtGK4nriJZRzVyOyOEL1evkXHLFUDt%2fF%2fl9Q%3d%3d> >> >> >> >> Signatures used for Spark RCs can be found in this file: >> >> https://dist.apache.org/repos/dist/dev/spark/KEYS >> <https://mailshield.baidu.com/check?q=E6fHbSXEWw02TTJBpc3bfA9mi7ea0YiWcNHkm%2fDJxwlaWinGnMdaoO1PahHhgj00vKwcbElpuHA%3d> >> >> >> >> The staging repository for this release can be found at: >> >> https://repository.apache.org/content/repositories/orgapachespark-1447 >> <https://mailshield.baidu.com/check?q=RKosLPjotKC8t%2fbhRUl%2fPI4aNpBuK2BpNhu6N7dXyO7vfBBIc2nx2st8hHY8kR%2f%2byciK%2bMWsc9QPqZCv6O3A2prmaWrVFOSOjhTPWA%3d%3d> >> >> >> >> The documentation corresponding to this release can be found at: >> >> https://dist.apache.org/repos/dist/dev/spark/v3.5.0-rc3-docs/ >> <https://mailshield.baidu.com/check?q=UisDsKXdd3IJ4Kv657YN4LyF4nLuG%2bzB3bin1GDxnnjSLLtyS4sJmD%2f3asF8Ihv6p62TDzMlUG%2fg5wYGfJ0EfUSOJL0%3d> >> >> >> >> The list of bug fixes going into 3.5.0 can be found at the following URL: >> >> https://issues.apache.org/jira/projects/SPARK/versions/12352848 >> <https://mailshield.baidu.com/check?q=rOHxO3EFdnYTS41rF0m9qsTrteyGHUmLHghEJgmTMLY2%2bhbNu4VZqqsL4J8TXbsKbVjS4fDayxhT%2fqjJjgSX8zM00bc%3d> >> >> >> >> This release is using the release script of the tag v3.5.0-rc3. >> >> >> >> FAQ >> >> >> >> ========================= >> >> How can I help test this release? >> >> ========================= >> >> If you are a Spark user, you can help us test this release by taking >> >> an existing Spark workload and running on this release candidate, then >> >> reporting any regressions. >> >> >> >> If you're working in PySpark you can set up a virtual env and install >> >> the current RC and see if anything important breaks, in the Java/Scala >> >> you can add the staging repository to your projects resolvers and test >> >> with the RC (make sure to clean up the artifact cache before/after so >> >> you don't end up building with an out of date RC going forward). >> >> >> >> =========================================== >> >> What should happen to JIRA tickets still targeting 3.5.0? >> >> =========================================== >> >> The current list of open tickets targeted at 3.5.0 can be found at: >> >> https://issues.apache.org/jira/projects/SPARK >> <https://mailshield.baidu.com/check?q=4UUpJqq41y71Gnuj0qTUYo6hTjqzT7oytN6x%2fvgC5XUtQUC8MfJ77tj7K70O%2f1QMmNoa1A%3d%3d> >> and >> search for "Target Version/s" = 3.5.0 >> >> >> >> Committers should look at those and triage. Extremely important bug >> >> fixes, documentation, and API tweaks that impact compatibility should >> >> be worked on immediately. Everything else please retarget to an >> >> appropriate release. >> >> >> >> ================== >> >> But my bug isn't fixed? >> >> ================== >> >> In order to make timely releases, we will typically not hold the >> >> release unless the bug in question is a regression from the previous >> >> release. That being said, if there is something which is a regression >> >> that has not been correctly targeted please ping me or a committer to >> >> help target the issue. >> >> >> >> Thanks, >> >> Yuanjian Li >> >>
