I managed to upload the wheels to pypi. Here is the current status
with the updated assignments:

1. [done] make the released version as "RELEASED" on JIRA
2. [done] start the new version on JIRA
4. [done] upload source
5. [done] upload binaries
6. [in-pr] update website
7. [todo:kou] update Homebrew packages
8. [todo:kou] update MSYS2 package
9. [todo:kou] upload RubyGems
10. [done] upload JS packages
11. [done] upload C# packages
12. [todo:unassigned] update conda recipes
13. [done] upload wheels/sdist to pypi
14. [todo:kszucs] publish Maven artifacts
15. [todo:nealrichardson] update R packages
16. [todo:ianmcook] update vcpkg port
17. [done] bump versions
18. [done] update tags for Go modules
19. [in-pr] update docs

On Thu, Feb 3, 2022 at 10:26 PM Neal Richardson
<neal.p.richard...@gmail.com> wrote:
>
> I will handle the R package submission to CRAN.
Thanks Neal!
>
> Neal
>
> On Thu, Feb 3, 2022 at 4:11 PM Sutou Kouhei <k...@clear-code.com> wrote:
>
> > Hi,
> >
> > I'll update/upload Homebrew, MSYS2 and RubyGems.
Thanks Kou!
> >
> > 1. [done] make the released version as "RELEASED" on JIRA
> > 2. [done] start the new version on JIRA
> > 4. [done] upload source
> > 5. [done] upload binaries
> > 6. [in-pr] update website
> > 7. [todo:kou] update Homebrew packages
> > 8. [todo:kou] update MSYS2 package
> > 9. [todo:kou] upload RubyGems
> > 10. [done] upload JS packages
> > 11. [done] upload C# packages
> > 12. [todo:unassigned] update conda recipes
> > 13. [blocked:kszucs] upload wheels/sdist to pypi
> > "Project size too large. Limit for project 'pyarrow' total size is 10
> > GB. See https://pypi.org/help/#project-size-limit";
> > Filed an issue to increase the project limit, waiting for the
> > response: https://github.com/pypa/pypi-support/issues/1653
> > 14. [todo] publish Maven artifacts
> > Micah did you have a chance to verify the staged maven artifacts? I'd
> > wait for your response before pushing the release button.
> > 15. [todo:unassigned] update R packages
> > 16. [todo:ianmcook] update vcpkg port
> > 17. [done] bump versions
> > 18. [done] update tags for Go modules
> > 19. [in-pr] update docs
> >
> >
> > Thanks,
> > --
> > kou
> >
> > In <CAHM19a6RWn-mvOArwnH4d5WwQ=pcb70w-nxkpl_y_w5bpl6...@mail.gmail.com>
> >   "Re: [VOTE] Release Apache Arrow 7.0.0 - RC10" on Thu, 3 Feb 2022
> > 21:38:17 +0100,
> >   Krisztián Szűcs <szucs.kriszt...@gmail.com> wrote:
> >
> > > On Thu, Feb 3, 2022 at 8:58 PM Ian Cook <i...@ursacomputing.com> wrote:
> > >>
> > >> Thanks Krisztián!
> > >>
> > >> I will update the vcpkg port.
> > > Thanks Ian!
> > >
> > > Here is the updated todo list:
> > >
> > > 1. [done] make the released version as "RELEASED" on JIRA
> > > 2. [done] start the new version on JIRA
> > > 4. [done] upload source
> > > 5. [done] upload binaries
> > > 6. [in-pr] update website
> > > 7. [todo:unassigned] update Homebrew packages
> > > 8. [todo:unassigned] update MSYS2 package
> > > 9. [todo:unassigned] upload RubyGems
> > > 10. [done] upload JS packages
> > > 11. [done] upload C# packages
> > > 12. [todo:unassigned] update conda recipes
> > > 13. [blocked:kszucs] upload wheels/sdist to pypi
> > > "Project size too large. Limit for project 'pyarrow' total size is 10
> > > GB. See https://pypi.org/help/#project-size-limit";
> > > Filed an issue to increase the project limit, waiting for the
> > > response: https://github.com/pypa/pypi-support/issues/1653
> > > 14. [todo] publish Maven artifacts
> > > Micah did you have a chance to verify the staged maven artifacts? I'd
> > > wait for your response before pushing the release button.
> > > 15. [todo:unassigned] update R packages
> > > 16. [todo:ianmcook] update vcpkg port
> > > 17. [done] bump versions
> > > 18. [done] update tags for Go modules
> > > 19. [in-pr] update docs
> > >
> > >>
> > >> Ian
> > >>
> > >> On Thu, Feb 3, 2022 at 2:35 PM Krisztián Szűcs
> > >> <szucs.kriszt...@gmail.com> wrote:
> > >> >
> > >> > Current status of the post release tasks:
> > >> >
> > >> > 1. [done] make the released version as "RELEASED" on JIRA
> > >> > 2. [done] start the new version on JIRA
> > >> > 4. [done] upload source
> > >> > 5. [done] upload binaries
> > >> > 6. [in-pr] update website
> > >> > 7. [TODO] update Homebrew packages
> > >> > 8. [TODO] update MSYS2 package
> > >> > 9. [TODO] upload RubyGems
> > >> > 10. [done] upload JS packages
> > >> > 11. [done] upload C# packages
> > >> > 12. [TODO] update conda recipes
> > >> > 13. [kszucs/problem] upload wheels/sdist to pypi
> > >> > "Project size too large. Limit for project 'pyarrow' total size is 10
> > >> > GB. See https://pypi.org/help/#project-size-limit";
> > >> > Filed an issue to increase the project limit, waiting for the
> > >> > response: https://github.com/pypa/pypi-support/issues/1653
> > >> > 14. [TODO] publish Maven artifacts
> > >> > 15. [TODO] update R packages
> > >> > 16. [TODO] update vcpkg port
> > >> > 17. [kszucs] bump versions
> > >> > 18. [kszucs] update tags for Go modules
> > >> > 19. [in-pr] update docs
> > >> >
> > >> > Any help with the tasks flagged as TODO is appreciated.
> > >> >
> > >> >
> > >> > On Thu, Feb 3, 2022 at 5:51 PM Micah Kornfield <emkornfi...@gmail.com>
> > wrote:
> > >> > >
> > >> > > Sorry I wasn't able to verify Java last night, I will try to check
> > tonight.
> > >> > >
> > >> > > On Thu, Feb 3, 2022 at 6:16 AM Rok Mihevc <rok.mih...@gmail.com>
> > wrote:
> > >> > >
> > >> > > > +1 (non-binding)
> > >> > > >
> > >> > > > I've successfully ran the following on Apple M1 Pro (macOS 12.1
> > >> > > > (21C52), Kernel Darwin 21.2.0):
> > >> > > > TEST_PYTHON=0 TEST_GLIB=0 TEST_RUBY=0
> > >> > > > ./dev/release/verify-release-candidate.sh source 7.0.0 10
> > >> > > >
> > >> > > > There was a minor issue with protobuf on M1:
> > >> > > > https://issues.apache.org/jira/browse/ARROW-15549
> > >> > > >
> > >> > > > I'll try to get Ruby to pass too. I'm assuming the Python build
> > issue
> > >> > > > is about conda and since I can build fine on Brew it's probably
> > ok.
> > >> > > >
> > >> > > > Rok
> > >> > > >
> > >> > > > On Wed, Feb 2, 2022 at 6:25 PM Antoine Pitrou <anto...@python.org>
> > wrote:
> > >> > > > >
> > >> > > > >
> > >> > > > > I've successfully tested the following configuration on a Apple
> > M1 with
> > >> > > > > macOS 11.2.3:
> > >> > > > >
> > >> > > > > ARROW_GANDIVA=OFF TEST_DEFAULT=0 TEST_CPP=1 \
> > >> > > > > ./dev/release/verify-release-candidate.sh source 7.0.0 10
> > >> > > > >
> > >> > > > > Regards
> > >> > > > >
> > >> > > > > Antoine.
> > >> > > > >
> > >> > > > >
> > >> > > > > Le 02/02/2022 à 17:45, Krisztián Szűcs a écrit :
> > >> > > > > > I'm planning to close the VOTE tomorrow, but it would be
> > great to have
> > >> > > > > > results for the following scenarios:
> > >> > > > > >
> > >> > > > > > - Verify the staged maven artifacts: this is the first time
> > we ship
> > >> > > > > > java jars with bundled shared libraries, but we don't have
> > scripting
> > >> > > > > > to test that. For more context see issue
> > >> > > > > > https://issues.apache.org/jira/browse/ARROW-15486
> > >> > > > > >
> > >> > > > > > - Verify the the release on Windows
> > >> > > > > >
> > >> > > > > > - Verify the release on Apple M1
> > >> > > > > >
> > >> > > > > > Thanks, Krisztian
> > >> > > > > >
> > >> > > > > > On Wed, Feb 2, 2022 at 5:36 PM Krisztián Szűcs
> > >> > > > > > <szucs.kriszt...@gmail.com> wrote:
> > >> > > > > >>
> > >> > > > > >> +1 (binding)
> > >> > > > > >>
> > >> > > > > >> - Verified the binaries (though I had to restart several
> > times because
> > >> > > > > >> artifactory dropped me off)
> > >> > > > > >> - Verified the source tarball (required to define
> > DYLD_LIBRARY_PATH
> > >> > > > > >> instead of LD_LIBRARY_PATH)
> > >> > > > > >> - Verified the wheels (without problems)
> > >> > > > > >>
> > >> > > > > >> on Intel macOS 12.
> > >> > > > > >>
> > >> > > > > >> On Mon, Jan 31, 2022 at 9:58 PM David Li <
> > lidav...@apache.org> wrote:
> > >> > > > > >>>
> > >> > > > > >>> +1
> > >> > > > > >>>
> > >> > > > > >>> Tested source (C++/Java with integration), binaries, and
> > wheels on
> > >> > > > Ubuntu 18.04.
> > >> > > > > >>>
> > >> > > > > >>> I ran into the same error as Antoine with the wheels;
> > adding `conda
> > >> > > > activate base` also fixed it for me. I had to disable Gandiva for
> > source
> > >> > > > verification due to a linking error with LLVM (though my system
> > >> > > > repositories don't have an appropriate version of LLVM in the
> > first place).
> > >> > > > > >>>
> > >> > > > > >>> -David
> > >> > > > > >>>
> > >> > > > > >>> On Mon, Jan 31, 2022, at 05:59, Antoine Pitrou wrote:
> > >> > > > > >>>> Le 30/01/2022 à 11:15, Krisztián Szűcs a écrit :
> > >> > > > > >>>>>>
> > >> > > > > >>>>>> (*) Here is the end of the logs:
> > >> > > > > >>>>>>
> > >> > > > > >>>>>> + pushd binaries
> > >> > > > > >>>>>> /tmp/arrow-7.0.0.C5b7S/binaries /tmp/arrow-7.0.0.C5b7S
> > >> > > > > >>>>>> ++ uname
> > >> > > > > >>>>>> + '[' Linux == Darwin ']'
> > >> > > > > >>>>>> + test_linux_wheels
> > >> > > > > >>>>>> ++ uname -m
> > >> > > > > >>>>>> + '[' x86_64 = aarch64 ']'
> > >> > > > > >>>>>> + local arch=x86_64
> > >> > > > > >>>>>> + local 'py_arches=3.7m 3.8 3.9 3.10'
> > >> > > > > >>>>>> + local
> > 'platform_tags=manylinux_2_12_x86_64.manylinux2010_x86_64
> > >> > > > > >>>>>> manylinux_2_17_x86_64.manylinux2014_x86_64'
> > >> > > > > >>>>>> + for py_arch in ${py_arches}
> > >> > > > > >>>>>> + local env=_verify_wheel-3.7m
> > >> > > > > >>>>>> + '[' 3.7m = 3.10 ']'
> > >> > > > > >>>>>> + local 'channels=-c conda-forge'
> > >> > > > > >>>>>> + mamba create -yq -n _verify_wheel-3.7m -c conda-forge
> > python=3.7
> > >> > > > > >>>>>> ./dev/release/verify-release-candidate.sh: line 646:
> > mamba:
> > >> > > > command not
> > >> > > > > >>>>> Could you please try to `conda activate base` before the
> > mamba
> > >> > > > command
> > >> > > > > >>>>> and if that doesn't work simply replace `mamba` with
> > `conda` and
> > >> > > > test
> > >> > > > > >>>>> the wheels again?
> > >> > > > > >>>>
> > >> > > > > >>>> Adding `conda activate base` solved the issue indeed.
> > >> > > > > >>>>
> > >> > > > > >>>> Regards
> > >> > > > > >>>>
> > >> > > > > >>>> Antoine.
> > >> > > >
> >

Reply via email to