Hi,
> > So while I'm all for making things a little more independent,
> > let's not do it in a way that makes life difficult for downstreams.
> > There are more there than just a couple of big distro builders.
>
> I think this is fine. Firmware blobs aren't needed to build QEMU, only
> to run t
On Mon, Oct 11, 2021 at 08:28:34AM -0600, Warner Losh wrote:
> On Mon, Oct 11, 2021 at 4:59 AM Stefan Hajnoczi wrote:
>
> > On Mon, Oct 11, 2021 at 09:21:30AM +0200, Gerd Hoffmann wrote:
> > > Hi,
> > >
> > > > > I guess the main question is who is using the ROM/BIOS sources in the
> > > > > ta
On Fri, Oct 1, 2021 at 12:20 AM Stefan Hajnoczi wrote:
> On Thu, Sep 30, 2021 at 03:57:49PM +, Eldon Stegall wrote:
> > Hello!
> > I'd be happy to help with this. I'm mostly a consumer of QEMU, but
> > greatly appreciate all the work this community has done, and was able
> > to contribute a l
On Mon, Oct 11, 2021 at 4:59 AM Stefan Hajnoczi wrote:
> On Mon, Oct 11, 2021 at 09:21:30AM +0200, Gerd Hoffmann wrote:
> > Hi,
> >
> > > > I guess the main question is who is using the ROM/BIOS sources in the
> > > > tarballs, and would this 2-step process work for those users? If
> there
> >
On Mon, Oct 11, 2021 at 09:21:30AM +0200, Gerd Hoffmann wrote:
> Hi,
>
> > > I guess the main question is who is using the ROM/BIOS sources in the
> > > tarballs, and would this 2-step process work for those users? If there
> > > are distros relying on them then maybe there are some more logisti
Hi,
> > I guess the main question is who is using the ROM/BIOS sources in the
> > tarballs, and would this 2-step process work for those users? If there
> > are distros relying on them then maybe there are some more logistics to
> > consider since the make-release downloads are both time-consumi
gt; QEMU downloads are currently hosted on qemu.org's Apache web server.
> > > > Paolo and I were discussing ways to reduce qemu.org network traffic to
> > > > save money and eventually turn off the qemu.org server since there is no
> > > > full-time sy
> Paolo and I were discussing ways to reduce qemu.org network traffic to
> > > save money and eventually turn off the qemu.org server since there is no
> > > full-time sysadmin for it. I'd like to discuss moving QEMU downloads to
> > > GitLab Releases.
> >
On Fri, Oct 01, 2021 at 09:52:20AM +0100, Daniel P. Berrangé wrote:
> On Fri, Oct 01, 2021 at 08:11:35AM +0100, Stefan Hajnoczi wrote:
> > We need to keep the security of QEMU releases in mind. Mike Roth
> > signs and publishes releases. Whoever facilitates or hosts the files
> > should not be able
ffic to
> > save money and eventually turn off the qemu.org server since there is no
> > full-time sysadmin for it. I'd like to discuss moving QEMU downloads to
> > GitLab Releases.
> >
> > Since you create and sign QEMU releases I wanted to see what you think
> &g
On 10/1/21 12:34, Gerd Hoffmann wrote:>> Maybe we should also discuss
again whether we could decrease the size of the
>> release tarballs. Someone recently mentioned that we could e.g. remove the
>> edk2 sources from the tarballs - edk2 is licensed under a BSD-style license,
>> so we are not forced
Hi,
> Maybe we should also discuss again whether we could decrease the size of the
> release tarballs. Someone recently mentioned that we could e.g. remove the
> edk2 sources from the tarballs - edk2 is licensed under a BSD-style license,
> so we are not forced to ship its sources in our tarball
On Fri, Oct 01, 2021 at 08:11:35AM +0100, Stefan Hajnoczi wrote:
> We need to keep the security of QEMU releases in mind. Mike Roth
> signs and publishes releases. Whoever facilitates or hosts the files
> should not be able to modify the files after Mike has blessed them. One
> way to do this is to
time sysadmin for it. I'd like to discuss moving QEMU downloads to
> GitLab Releases.
>
> Since you create and sign QEMU releases I wanted to see what you think
> about the idea. GitLab Releases has two ways of creating release assets:
> archiving a git tree and attaching arbitr
f the qemu.org server since there is no
full-time sysadmin for it. I'd like to discuss moving QEMU downloads to
GitLab Releases.
Daniel Berrange posted this in another discussion:
"gitlab releases have a per-file size limit that is somewhere on the
order of 10 MB IIRC. Our release tarballs ar
On Thu, Sep 30, 2021 at 03:57:49PM +, Eldon Stegall wrote:
> Hello!
> I'd be happy to help with this. I'm mostly a consumer of QEMU, but
> greatly appreciate all the work this community has done, and was able
> to contribute a little by helping with QEMU advent this past year. I
> would be happ
g's Apache web server.
> > Paolo and I were discussing ways to reduce qemu.org network traffic to
> > save money and eventually turn off the qemu.org server since there is no
> > full-time sysadmin for it. I'd like to discuss moving QEMU downloads to
> > G
e there is no
> full-time sysadmin for it. I'd like to discuss moving QEMU downloads to
> GitLab Releases.
Daniel Berrange posted this in another discussion:
"gitlab releases have a per-file size limit that is somewhere on the
order of 10 MB IIRC. Our release tarballs are 100+ MB, s
Hi Mike,
QEMU downloads are currently hosted on qemu.org's Apache web server.
Paolo and I were discussing ways to reduce qemu.org network traffic to
save money and eventually turn off the qemu.org server since there is no
full-time sysadmin for it. I'd like to discuss moving QEMU do
19 matches
Mail list logo
