Il Dom 28 Mar 2021, 03:39 Yong Zhang ha
scritto:
> Guangning, yes. We just need to upload the inner content in the tarball.
>
> Enrico, the tarballs are generated during the release procedure and the
> files have
> already voted. That's my mistake, I should decompress the tarball and
> upload the
Guangning, yes. We just need to upload the inner content in the tarball.
Enrico, the tarballs are generated during the release procedure and the
files have
already voted. That's my mistake, I should decompress the tarball and
upload the
inner content to the dist.
On Sat, 27 Mar 2021 at 19:47, Enr
are the tarballs generated during the execution of the release
procedure or do you need to create new files that have not been
"VOTED" by the PMC during the release?
in that case (new files not voted) it is up to the PMC to decide
whether to add those files to the released artifacts repository
if
+1
I don't think you need to change the tarball, just upload the missing deb
and rpm packages so that users can continue to use the tarball and the
unpacked packages
Thanks,
Guangning
Enrico Olivelli 于2021年3月27日周六 下午5:55写道：
> Il Sab 27 Mar 2021, 08:41 Yong Zhang ha scritto:
>
> > Hi all，
> >
>
Il Sab 27 Mar 2021, 08:41 Yong Zhang ha scritto:
> Hi all，
>
> When releasing 2.7.1 DEB and RPMs packages I upload them as a tarball
> and that will make some user can not download them properly.
Do we have a github issue to track this problem?
So I want to
> decompress them and reupload it t
Hi all，
When releasing 2.7.1 DEB and RPMs packages I upload them as a tarball
and that will make some user can not download them properly. So I want to
decompress them and reupload it to solve that problem.
What do you think?
https://dist.apache.org/repos/dist/release/pulsar/pulsar-2.7.1/DEB/
ht
