On 3/11/19 3:43 PM, Stephen John Smoogen wrote:
> I tried to make format-patch work but I have some problems in places
> still in my setup :/
>
> From 49ab54526b57d0cde534b2887a4e77cf021090ea Mon Sep 17 00:00:00 2001
> From: Stephen Smoogen
> Date: Mon, 11 Mar 2019 22:39:30 +
> Subject:
On Mon, 2019-03-11 at 11:24 -0700, Kevin Fenzi wrote:
> On 3/11/19 12:26 AM, Jonathan Dieter wrote:
> > This adds zchunk support for the updates and updates-testing
> > repositories for both rpms and modularity. We already have zchunk
> > metadata being generated for the fedora repository. I'd
On 3/11/19 7:31 AM, Neal Gompa wrote:
> I double-checked this and you're sadly right. I've fixed this so
> koji-builder is now using Python 2 again.
>
> I thought I had validated all the dependencies for Koji we use in
> infra to have been ported, but alas, imgfac hasn't been done yet.
>
>
+1 also. thank you for answering my questions.
On Mon, 11 Mar 2019 at 14:31, Kevin Fenzi wrote:
>
> +1 to the change here.
>
> If it gives us any problems we can adjust it later...
>
> kevin
>
>
> ___
> infrastructure mailing list --
+1 to the change here.
If it gives us any problems we can adjust it later...
kevin
signature.asc
Description: OpenPGP digital signature
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to
On 3/11/19 12:26 AM, Jonathan Dieter wrote:
> This adds zchunk support for the updates and updates-testing
> repositories for both rpms and modularity. We already have zchunk metadata
> being generated for the fedora repository. I'd like to get this in before
> Beta comes out so Beta users
Sure, +1
note that we have no updates repo for f30 yet (until really close to
final release), but we could test this out with updates-testing.
kevin
signature.asc
Description: OpenPGP digital signature
___
infrastructure mailing list --
Thanks for +1's and its going into the doc.
On Mon, Mar 11, 2019 at 1:26 PM Kevin Fenzi wrote:
> +1
>
> (and also update the branching docs to do this on branch next time. ;)
>
> kevin
>
>
> ___
> infrastructure mailing list --
+1
(and also update the branching docs to do this on branch next time. ;)
kevin
signature.asc
Description: OpenPGP digital signature
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to
Thanks for the +1's. This change has been deployed and I've confirmed
that I can push F30 updates between the 3 and 7 day mark.
signature.asc
Description: This is a digitally signed message part
___
infrastructure mailing list --
+1
On Mon, Mar 11, 2019 at 4:22 PM Mohan Boddu wrote:
>
> This patch will add fedora-30 key to bodhi modular pungi config.
>
> diff --git a/roles/bodhi2/backend/templates/pungi.module.conf.j2
> b/roles/bodhi2/backend/templates/pungi.module.conf.j2
> index bb021eb..43c6a7e 100644
> ---
This patch will add fedora-30 key to bodhi modular pungi config.
diff --git a/roles/bodhi2/backend/templates/pungi.module.conf.j2
b/roles/bodhi2/backend/templates/pungi.module.conf.j2
index bb021eb..43c6a7e 100644
--- a/roles/bodhi2/backend/templates/pungi.module.conf.j2
+++
+1
On Mon, 11 Mar 2019 at 10:50, Mikolaj Izdebski wrote:
>
> +1
>
> On Mon, Mar 11, 2019 at 3:45 PM Randy Barlow
> wrote:
> >
> > Greetings!
> >
> > The Bodhi frontend container was not rebuilt when the Fedora 30
> > configurations were added to production.ini. This means that the
> > frontend
+1
On Mon, Mar 11, 2019 at 3:45 PM Randy Barlow
wrote:
>
> Greetings!
>
> The Bodhi frontend container was not rebuilt when the Fedora 30
> configurations were added to production.ini. This means that the
> frontend is not aware of the policy of 3 days to stable, while the
> backend is aware.
Greetings!
The Bodhi frontend container was not rebuilt when the Fedora 30
configurations were added to production.ini. This means that the
frontend is not aware of the policy of 3 days to stable, while the
backend is aware. This means that the backend is adding comments to
updates to tell
On Mon, Mar 11, 2019 at 9:44 AM Peter Robinson wrote:
>
> > I disabled autopushing precisely so that there's no accidental pushing
> > to stable updates. The worst thing that can happen is that we have to
> > unpush the update from testing. Seriously, that's really not the end
> > of the world.
>
On Mon, Mar 11, 2019 at 12:41 PM Stephen John Smoogen wrote:
>
> On Mon, 11 Mar 2019 at 06:55, Mikolaj Izdebski wrote:
> >
> > On Mon, Mar 11, 2019 at 10:43 AM Stephen John Smoogen
> > wrote:
> > >
> > > On Mon, 11 Mar 2019 at 04:52, Mikolaj Izdebski
> > > wrote:
> > > >
> > > > I would like
On Mon, 11 Mar 2019 at 06:55, Mikolaj Izdebski wrote:
>
> On Mon, Mar 11, 2019 at 10:43 AM Stephen John Smoogen
> wrote:
> >
> > On Mon, 11 Mar 2019 at 04:52, Mikolaj Izdebski wrote:
> > >
> > > I would like to propose increasing NUM_CONCURRENT_BUILDS for MBS to
> > > value 100 after beta
On Mon, Mar 11, 2019 at 10:43 AM Stephen John Smoogen wrote:
>
> On Mon, 11 Mar 2019 at 04:52, Mikolaj Izdebski wrote:
> >
> > I would like to propose increasing NUM_CONCURRENT_BUILDS for MBS to
> > value 100 after beta freeze is over.
> >
> > The above MBS setting controls how many parallel
On Mon, 11 Mar 2019 at 04:52, Mikolaj Izdebski wrote:
>
> I would like to propose increasing NUM_CONCURRENT_BUILDS for MBS to
> value 100 after beta freeze is over.
>
> The above MBS setting controls how many parallel component builds MBS
> can run at the same time. Current value is only 20. That
I would like to propose increasing NUM_CONCURRENT_BUILDS for MBS to
value 100 after beta freeze is over.
The above MBS setting controls how many parallel component builds MBS
can run at the same time. Current value is only 20. That value was
defined 3 years ago, in March 2017 when there were much
This adds zchunk support for the updates and updates-testing
repositories for both rpms and modularity. We already have zchunk metadata
being generated for the fedora repository. I'd like to get this in before Beta
comes out so Beta users will have zchunk-enabled updates-testing repositories
22 matches
Mail list logo
