Entering freeze for libvirt-6.8.0

[Neal Gompa]

On Fri, Sep 25, 2020 at 4:35 AM Daniel P. Berrangé <berrange at redhat.com> wrote:
>
> On Thu, Sep 24, 2020 at 03:39:03PM -0400, Neal Gompa wrote:
> > On Thu, Sep 24, 2020 at 3:00 PM Jiri Denemark <jdenemar at redhat.com> wrote:
> > >
> > > On Thu, Sep 24, 2020 at 18:38:18 +0200, Andrea Bolognani wrote:
> > > > On Thu, 2020-09-24 at 15:13 +0200, Jiri Denemark wrote:
> > > > > I have just tagged v6.8.0-rc1 in the repository and pushed signed
> > > > > tarballs and source RPMs to https://libvirt.org/sources/
> > > >
> > > > Can we please stop generating and publishing the source RPMs? They're
> > > > of little use considering that you can easily run
> > > >
> > > >   $ rpmbuild -ta libvirt-x.y.z.tar.xz
> > > >
> > > > to obtain RPMs from a release archive, so all they really do is
> > > > clutter the directory listing.
> > >
> > > The nice thing about the source RPMs is that they are internally signed
> > > (in contrast to an external signature in *.asc for tarballs). Personally
> > > I don't find them useful either, but some people may think otherwise and
> > > I'm not sure they will raise their voice here. We could just stop
> > > creating source RPMs and wait if anyone complains. Or we could be a
> > > little bit more conservative and just move them to a subdirectory
> > > perhaps. I don't mind either way.
> > >
> >
> > I like that Source RPMs are produced, because I can trivially use them
> > in my import->build->test pipeline, since my build system accepts
> > SRPMs as input and not random tarballs. :)
>
> If you have the tarball you can trivially generate the source RPM if
> you need it because the tarball still contains the .spec file. IOW
> just run
>
>   $ rpmbuild -ts libvirt-6.7.0.tar.xz
>   Wrote: /home/berrange/rpmbuild/SRPMS/libvirt-6.7.0-1.fc32.src.rpm
>

That assumes I have the ability to add such a mechanism that can do
that automatically. :)


-- 
真実はいつも一つ！/ Always, there's only one truth!