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 the files have already been voted, we should have them on the staging area (if it has not been dropped yet) and we can simply move them to the dist area Enrico Il giorno sab 27 mar 2021 alle ore 12:29 Guangning E <eguangn...@gmail.com> ha scritto: > > +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 <eolive...@gmail.com> 于2021年3月27日周六 下午5:55写道： > > > Il Sab 27 Mar 2021, 08:41 Yong Zhang <y...@apache.org> 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 to solve that problem. > > > > > > > If you decompress them, why can't yours do the same? > > Is it a problem in the packaging? > > > > Enrico > > > > > > > What do you think? > > > > > > https://dist.apache.org/repos/dist/release/pulsar/pulsar-2.7.1/DEB/ > > > https://dist.apache.org/repos/dist/release/pulsar/pulsar-2.7.1/RPMS/ > > > > > > Sorry for the inconvenience to you. > > > > > > Thanks, > > > Yong > > > > >
