arrow-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kouhei Sutou <...@clear-code.com>
Subject Re: 0.13.0 APT repository is broken
Date Wed, 03 Apr 2019 00:42:46 GMT
Hi Wes,

Thanks for your response.
I'll regenerate the API metadata and make 0.13.0 APT
repository unofficial.


Thanks,
--
kou

In <CAJPUwMDJZhq4ApLVSo8=XCeH60rz1sPu51OByrDnpN2Env3CwA@mail.gmail.com>
  "Re: 0.13.0 APT repository is broken" on Tue, 2 Apr 2019 19:29:48 -0500,
  Wes McKinney <wesmckinn@gmail.com> wrote:

> hi Kou,
> 
> Either solution you propose seems OK to me. Regenerating the APT
> metadata and marking the packages as non-official would be OK if it
> saves you and others the effort of doing a full release. We made
> enough process changes from 0.12.0 to 0.13.0 that it seemed inevitable
> for some things to break.
> 
> Thanks,
> Wes
> 
> On Tue, Apr 2, 2019 at 4:54 PM Kouhei Sutou <kou@clear-code.com> wrote:
>>
>> Hi,
>>
>> Our APT repositories for Debian and Ubuntu are broken:
>>   https://issues.apache.org/jira/browse/ARROW-5087
>>
>> It seems that APT metadata (package list) is only broken. So
>> we can fix this by re-generate APT metadata. We can still
>> use voted binary artifacts.
>>
>> Can we re-generate APT metadata and upload it without vote?
>> Or should we create 0.13.1 for it?
>> Or can we re-generate APT metadata and upload it without
>> vote by adding "(Unofficial)" mark to
>> https://arrow.apache.org/install/ ?
>>
>>
>> I'll add verification scripts for APT and YUM repositories
>> to prevent this problem in future releases:
>>   https://issues.apache.org/jira/browse/ARROW-5094
>>
>>
>> Thanks,
>> --
>> kou

Mime
View raw message