Rerun with cosmic and the successfully built ARM packages.

On Fri, Jan 31, 2020 at 12:57 PM Sutou Kouhei <k...@clear-code.com> wrote:
>
> Hi,
>
> One more thing.
>
> It seems that some .deb/.rpm files for arm64 aren't
> uploaded. Could you re-run "crossbow download-artifacts
> build-730" and re-run "dev/release/03-binary.sh"?
>
>
> Thanks,
> --
> kou
>
> In <20200131.205531.1001999778589734260....@clear-code.com>
>   "Re: [VOTE] Release Apache Arrow 0.16.0 - RC2" on Fri, 31 Jan 2020 20:55:31 
> +0900 (JST),
>   Sutou Kouhei <k...@clear-code.com> wrote:
>
> > Hi,
> >
> > "dev/release/verify-release-candidate.sh binaries 0.16.0 2"
> > is still failing. And I found the cause of the problem.
> >
> > Could you re-run 03-binary.sh with the change?
> >
> > ---
> > diff --git a/dev/release/binary-task.rb b/dev/release/binary-task.rb
> > index 4b5960445..3dd1d9c08 100644
> > --- a/dev/release/binary-task.rb
> > +++ b/dev/release/binary-task.rb
> > @@ -1015,6 +1015,7 @@ class BinaryTask
> >        ["debian", "buster", "main"],
> >        ["ubuntu", "xenial", "main"],
> >        ["ubuntu", "bionic", "main"],
> > +      ["ubuntu", "cosmic", "main"],
> >        ["ubuntu", "disco", "main"],
> >        ["ubuntu", "eoan", "main"],
> >      ]
> > ---
> >
> > Existing APT metadata files for Ubuntu Cosmic has
> > problem (.sha512 file is missing). So we need to re-generate
> > it only for 0.16.0 release. We don't need to do this for the
> > next release.
> >
> >
> > Thanks,
> > --
> > kou
> >
> > In <cahm19a73azqzndbonhvtpwekfkfjfxehkh2nxnyg6h1xsfo...@mail.gmail.com>
> >   "[VOTE] Release Apache Arrow 0.16.0 - RC2" on Fri, 31 Jan 2020 04:13:12 
> > +0100,
> >   Krisztián Szűcs <szucs.kriszt...@gmail.com> wrote:
> >
> >> Hi,
> >>
> >> I would like to propose the following release candidate (RC2) of Apache
> >> Arrow version 0.16.0. This is a release consisting of 728
> >> resolved JIRA issues[1].
> >>
> >> This release candidate is based on commit:
> >> 729a7689fd87572e6a14ad36f19cd579a8b8d9c5 [2]
> >>
> >> The source release rc2 is hosted at [3].
> >> The binary artifacts are hosted at [4][5][6][7].
> >> The changelog is located at [8].
> >>
> >> Please download, verify checksums and signatures, run the unit tests,
> >> and vote on the release. See [9] for how to validate a release candidate.
> >>
> >> The vote will be open for at least 72 hours.
> >>
> >> [ ] +1 Release this as Apache Arrow 0.16.0
> >> [ ] +0
> >> [ ] -1 Do not release this as Apache Arrow 0.16.0 because...
> >>
> >> [1]: 
> >> https://issues.apache.org/jira/issues/?jql=project%20%3D%20ARROW%20AND%20status%20in%20%28Resolved%2C%20Closed%29%20AND%20fixVersion%20%3D%200.16.0
> >> [2]: 
> >> https://github.com/apache/arrow/tree/729a7689fd87572e6a14ad36f19cd579a8b8d9c5
> >> [3]: https://dist.apache.org/repos/dist/dev/arrow/apache-arrow-0.16.0-rc2
> >> [4]: https://bintray.com/apache/arrow/centos-rc/0.16.0-rc2
> >> [5]: https://bintray.com/apache/arrow/debian-rc/0.16.0-rc2
> >> [6]: https://bintray.com/apache/arrow/python-rc/0.16.0-rc2
> >> [7]: https://bintray.com/apache/arrow/ubuntu-rc/0.16.0-rc2
> >> [8]: 
> >> https://github.com/apache/arrow/blob/729a7689fd87572e6a14ad36f19cd579a8b8d9c5/CHANGELOG.md
> >> [9]: 
> >> https://cwiki.apache.org/confluence/display/ARROW/How+to+Verify+Release+Candidates

Reply via email to