Re: [FBR] Include updates-testing repo during bodhi u-t run

2018-10-29 Thread Sinny Kumari
On Tue, Oct 30, 2018 at 1:04 AM Kevin Fenzi  wrote:

> Just FYI, we should completely redo these configs using the release
> variables, but that doesn't have to be today. ;)
>
> +1 if this makes config cleaner :)


> I assume the check for f30 and using branched is only going to get used
> once we branch off f30 right (since this config doesn't compose rawhide)?
>

 That's correct!

+1
>
> kevin
>
>
>
> ___
> infrastructure mailing list -- infrastructure@lists.fedoraproject.org
> To unsubscribe send an email to
> infrastructure-le...@lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org
>


-- 
http://sinny.io/
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org


Re: Note on ansible release variables

2018-10-29 Thread Kevin Fenzi
On 10/19/18 7:00 AM, Mohan Boddu wrote:
> On Thu, Oct 18, 2018 at 3:05 PM Kevin Fenzi  wrote:
> 
>> On 10/15/18 12:21 PM, Mohan Boddu wrote:
>>
>>> Then I think we should use another variable (probably RelengFreeze)
>>> to indicate releng freeze, as they dont actually end on the same day.
>>> Also, we are using it for  automated bodhi pushes, and we start
>>> pushing stable updates once we are a GO which we generally know
>>> on Thu itself. WDYT?
>>
>> Yeah, more states. ;(
>>
>> I wonder if we could look at aligning the infrastructure and releng
>> freezes. (Either by setting a new time like 15:00UTC to start both of
>> them, or by moving both to the same time). I know many people find
>> "00:00 UTC on tuesday" confusing. If we moved both to say 15:00UTC
>> tuesday it might work better?
>>
> +1 but what do you think of late UTC time on a Monday like 20:00 UTC?

Well, it would change the schedule some, since we now always say we
freeze on tuesdays. I'd perfer something like 20:00UTC on tuesday as
that would give (at least usa folks) another morning to wrap up any
bugfixes. I guess we might ask fesco...

kevin



signature.asc
Description: OpenPGP digital signature
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org


Re: [PATCH] new-updates-sync: no longer sync stable refs for ostrees

2018-10-29 Thread Kevin Fenzi
On 10/29/18 12:30 PM, Dusty Mabe wrote:
> pushed. can one of you run the playbook?

Doing so now.

kevin




signature.asc
Description: OpenPGP digital signature
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org


Re: [PATCH] new-updates-sync: no longer sync stable refs for ostrees

2018-10-29 Thread Dusty Mabe
pushed. can one of you run the playbook?

Dusty

On 10/29/2018 02:57 PM, Mohan Boddu wrote:
> LGTM +1
> 
> On Mon, Oct 29, 2018 at 2:44 PM Kevin Fenzi  > wrote:
> 
> Sure. +1
> 
> kevin
> 
> ___
> infrastructure mailing list -- infrastructure@lists.fedoraproject.org 
> 
> To unsubscribe send an email to 
> infrastructure-le...@lists.fedoraproject.org 
> 
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org
> 
> 
> 
> ___
> infrastructure mailing list -- infrastructure@lists.fedoraproject.org
> To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org
> 
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org


Re: [PATCH] new-updates-sync: no longer sync stable refs for ostrees

2018-10-29 Thread Mohan Boddu
LGTM +1

On Mon, Oct 29, 2018 at 2:44 PM Kevin Fenzi  wrote:

> Sure. +1
>
> kevin
>
> ___
> infrastructure mailing list -- infrastructure@lists.fedoraproject.org
> To unsubscribe send an email to
> infrastructure-le...@lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org
>
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org


Re: [PATCH] new-updates-sync: no longer sync stable refs for ostrees

2018-10-29 Thread Kevin Fenzi
Sure. +1

kevin



signature.asc
Description: OpenPGP digital signature
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org


Re: [FBR] Include updates-testing repo during bodhi u-t run

2018-10-29 Thread Kevin Fenzi
Just FYI, we should completely redo these configs using the release
variables, but that doesn't have to be today. ;)

I assume the check for f30 and using branched is only going to get used
once we branch off f30 right (since this config doesn't compose rawhide)?

+1

kevin





signature.asc
Description: OpenPGP digital signature
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org


[PATCH] new-updates-sync: no longer sync stable refs for ostrees

2018-10-29 Thread Dusty Mabe
Now that we are releasing f29, no longer sync the stable refs.
The atomic host stable ref will be controlled by two week releases.
The silverblue stable ref will be aliased to the updates ref.
---
 roles/bodhi2/backend/files/new-updates-sync | 7 ---
 1 file changed, 7 deletions(-)

diff --git a/roles/bodhi2/backend/files/new-updates-sync 
b/roles/bodhi2/backend/files/new-updates-sync
index cbc8b9300..b9b9fa634 100755
--- a/roles/bodhi2/backend/files/new-updates-sync
+++ b/roles/bodhi2/backend/files/new-updates-sync
@@ -28,14 +28,7 @@ RELEASES = {'f29': {'topic': 'fedora',
 'ostrees': [{'ref': 
'fedora/29/%(arch)s/updates/atomic-host',
  'dest': ATOMICDEST,
  'arches': ['x86_64', 'ppc64le', 
'aarch64']},
-# sync base ref for now until f29 is 
released
-{'ref': 'fedora/29/%(arch)s/atomic-host',
- 'dest': ATOMICDEST,
- 'arches': ['x86_64', 'ppc64le', 
'aarch64']},
 {'ref': 
'fedora/29/x86_64/updates/silverblue',
- 'dest': ATOMICDEST},
-# sync base ref for now until f29 is 
released
-{'ref': 'fedora/29/x86_64/silverblue',
  'dest': ATOMICDEST}],
 'to': [{'arches': ['x86_64', 'armhfp', 'aarch64', 
'source'],
 'dest': os.path.join(FEDORADEST, '29', 
'Everything')},
-- 
2.14.4
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org


FBR: [PATCH] new-updates-sync: no longer sync stable refs for ostrees

2018-10-29 Thread Dusty Mabe

Can I get some votes to no longer sync stable ostree refs using
new-updates-sync?

Dusty
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org


[Fedocal] Reminder meeting : Infra Office Hours

2018-10-29 Thread cverna
Dear all,

You are kindly invited to the meeting:
   Infra Office Hours on 2018-10-30 from 18:00:00 to 19:00:00 UTC
   At fedora-ad...@irc.freenode.net

The meeting will be about:
Weekly hour dedicated to answer questions or help people with fixing tickets or 
implementing features.


Source: https://apps.fedoraproject.org/calendar/meeting/9255/

___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org


Re: [FBR] Include updates-testing repo during bodhi u-t run

2018-10-29 Thread Sinny Kumari
Updated patch which has following changes:
* Include latest updates and updates-testing repos during AH ISO
  creation.
* With F29 RC 1.2 declared Gold, update Atomic Host repo for OSTree
  and artifacts creation from /compose/branched/ to compose/29/
* With F29 RC 1.2 declared Gold, update Silverblue repo for OSTree
  creation from /compose/branched/ to compose/29/


On Mon, Oct 29, 2018 at 9:39 PM Dusty Mabe  wrote:

>
>
> On 10/29/2018 11:57 AM, Sinny Kumari wrote:
> >
> >
> > On Mon, Oct 29, 2018 at 9:25 PM Dusty Mabe  du...@dustymabe.com>> wrote:
> >
> >
> >
> > On 10/29/2018 11:16 AM, Sinny Kumari wrote:
> > >
>
> > >
> > > With RC 1.2 being Gold, does it make sense to make this
> https://kojipkgs{{ env_suffix }}.fedoraproject.org/compose/[[
>  <
> http://fedoraproject.org/compose/%5B%5B> <
> http://fedoraproject.org/compose/[[ <
> http://fedoraproject.org/compose/%5B%5B>> release.version_int
> ]]/latest-Fedora-[[ release.version_int ]]/compose/Everything/[[arch]]/os/ ?
> >
> >
> > I think probably we should just change the "if conditions" to `==
> 30` in places where it makes sense now that f29 is going to be released,
> which should achieve the same goal right?
> >
> > Yeah, I will be doing same code wise
>
> +1
>


-- 
http://sinny.io/
From 06a4940df01db0ae37a50f133895de19cc2b9a3a Mon Sep 17 00:00:00 2001
From: Sinny Kumari 
Date: Thu, 25 Oct 2018 20:57:37 +0530
Subject: [PATCH] Include multiple repos for AH ISO and update F29 repos

* Latest dnf available in F29 solves the lorax issue while
  using multiple repos - https://github.com/weldr/lorax/issues/368
  Including latest updates and updates-testing repo will help us to
  test latest fixes done in packages which composes AH ISO.
* With F29 RC 1.2 declared Gold, update Atomic Host repo for OSTree
  and artifacts creation from /compose/branched/ to compose/29/
* With F29 RC 1.2 declared Gold, update Silverblue repo for OSTree
  creation from /compose/branched/ to compose/29/
---
 .../backend/templates/pungi.rpm.conf.j2   | 32 +--
 1 file changed, 15 insertions(+), 17 deletions(-)

diff --git a/roles/bodhi2/backend/templates/pungi.rpm.conf.j2 b/roles/bodhi2/backend/templates/pungi.rpm.conf.j2
index af3f5ea29..76e8ffda8 100644
--- a/roles/bodhi2/backend/templates/pungi.rpm.conf.j2
+++ b/roles/bodhi2/backend/templates/pungi.rpm.conf.j2
@@ -130,8 +130,8 @@ ostree = {
 # In the case of testing, also inject the last stable updates
 "https://kojipkgs{{ env_suffix }}.fedoraproject.org/compose/updates/f[[ release.version_int ]]-updates/compose/Everything/$basearch/os/",
 [% endif %]
-# For f29 the compose location is under /compose/branched/
-[% if release.version_int == 29 %]
+# For f30 the compose location is going to be under /compose/branched/
+[% if release.version_int == 30 %]
 "https://kojipkgs{{ env_suffix }}.fedoraproject.org/compose/branched/latest-Fedora-[[ release.version_int ]]/compose/Everything/$basearch/os/"
 [% else %]
 "https://kojipkgs{{ env_suffix }}.fedoraproject.org/compose/[[ release.version_int ]]/latest-Fedora-[[ release.version_int ]]/compose/Everything/$basearch/os/"
@@ -174,8 +174,8 @@ ostree = {
 # In the case of testing, also inject the last stable updates
 "https://kojipkgs{{ env_suffix }}.fedoraproject.org/compose/updates/f[[ release.version_int ]]-updates/compose/Everything/$basearch/os/",
 [% endif %]
-# For f29 the compose location is under /compose/branched/
-[% if release.version_int == 29 %]
+# For f30 the compose location is going to be under /compose/branched/
+[% if release.version_int == 30 %]
 "https://kojipkgs{{ env_suffix }}.fedoraproject.org/compose/branched/latest-Fedora-[[ release.version_int ]]/compose/Everything/$basearch/os/"
 [% else %]
 "https://kojipkgs{{ env_suffix }}.fedoraproject.org/compose/[[ release.version_int ]]/latest-Fedora-[[ release.version_int ]]/compose/Everything/$basearch/os/"
@@ -238,8 +238,8 @@ image_build = {
 'target': 'f[[ release.version_int ]]',
 'arches': ['x86_64', 'aarch64', 'ppc64le'],
 'install_tree_from': 
-# For f29 the compose location is under /compose/branched/
-[% if release.version_int == 29 %]
+# For f30 the compose location is going to be under /compose/branched/
+[% if release.version_int == 30 %]
 "https://kojipkgs{{ env_suffix }}.fedoraproject.org/compose/branched/latest-Fedora-[[ release.version_int ]]/compose/Everything/$arch/os/",
 [% else 

Re: [FBR] Include updates-testing repo during bodhi u-t run

2018-10-29 Thread Dusty Mabe


On 10/29/2018 11:57 AM, Sinny Kumari wrote:
> 
> 
> On Mon, Oct 29, 2018 at 9:25 PM Dusty Mabe  > wrote:
> 
> 
> 
> On 10/29/2018 11:16 AM, Sinny Kumari wrote:
> >

> >
> > With RC 1.2 being Gold, does it make sense to make this 
> https://kojipkgs{{ env_suffix }}.fedoraproject.org/compose/[[ 
>  
>  > release.version_int 
> ]]/latest-Fedora-[[ release.version_int ]]/compose/Everything/[[arch]]/os/ ?
> 
> 
> I think probably we should just change the "if conditions" to `== 30` in 
> places where it makes sense now that f29 is going to be released, which 
> should achieve the same goal right?
> 
> Yeah, I will be doing same code wise

+1 
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org


Re: [FBR] Include updates-testing repo during bodhi u-t run

2018-10-29 Thread Sinny Kumari
On Mon, Oct 29, 2018 at 9:25 PM Dusty Mabe  wrote:

>
>
> On 10/29/2018 11:16 AM, Sinny Kumari wrote:
> >
> >
> > On Fri, Oct 26, 2018 at 7:07 PM Dusty Mabe  du...@dustymabe.com>> wrote:
> >
> >
> >
> > On 10/25/2018 01:25 PM, Sinny Kumari wrote:
> > > Hi,
> > >
> > > Here is a patch (available in email attachment) to include
> updates-testing repo
> > > as well during Atomic Host ISO creation in bodhi updates-testing
> run. Specifying
> > > multiple repos to lorax should work fine on Fedora >=29 -
> > > https://github.com/weldr/lorax/issues/368 .
> > >
> > > Can I get +1 for the patch?
> > >
> > > Thanks,
> > > Sinny
> >
> >
> > Suggested change below. I think we just need to uncomment out the
> commented out code right
> > above the lines you changed.
> >
> >
> > Thanks Dusty for reviewing it!
> >
> > - updates run will run lorax against
> > - Everything
> > - the current updates run
> >
> > +1
> >
> > - https://kojipkgs{{ env_suffix }}.
> fedoraproject.org/compose/branched/latest-Fedora-[[
>  <
> http://fedoraproject.org/compose/branched/latest-Fedora-%5B%5B>
> release.version_int ]]/compose/Everything/[[arch]]/os/
> > - the release day repo
> >
> >
> > With RC 1.2 being Gold, does it make sense to make this https://kojipkgs{{
> env_suffix }}.fedoraproject.org/compose/[[
>  <
> http://fedoraproject.org/compose/[[> release.version_int
> ]]/latest-Fedora-[[ release.version_int ]]/compose/Everything/[[arch]]/os/ ?
>
>
> I think probably we should just change the "if conditions" to `== 30` in
> places where it makes sense now that f29 is going to be released, which
> should achieve the same goal right?
>
> Yeah, I will be doing same code wise

Dusty
>


-- 
http://sinny.io/
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org


Re: [FBR] Include updates-testing repo during bodhi u-t run

2018-10-29 Thread Dusty Mabe


On 10/29/2018 11:16 AM, Sinny Kumari wrote:
> 
> 
> On Fri, Oct 26, 2018 at 7:07 PM Dusty Mabe  > wrote:
> 
> 
> 
> On 10/25/2018 01:25 PM, Sinny Kumari wrote:
> > Hi,
> >
> > Here is a patch (available in email attachment) to include 
> updates-testing repo
> > as well during Atomic Host ISO creation in bodhi updates-testing run. 
> Specifying
> > multiple repos to lorax should work fine on Fedora >=29 -
> > https://github.com/weldr/lorax/issues/368 .
> >
> > Can I get +1 for the patch?
> >
> > Thanks,
> > Sinny
> 
> 
> Suggested change below. I think we just need to uncomment out the 
> commented out code right
> above the lines you changed.
> 
> 
> Thanks Dusty for reviewing it!
> 
> - updates run will run lorax against
>     - Everything
>         - the current updates run
> 
> +1
> 
>     - https://kojipkgs{{ env_suffix 
> }}.fedoraproject.org/compose/branched/latest-Fedora-[[ 
>  
> release.version_int ]]/compose/Everything/[[arch]]/os/
>         - the release day repo
> 
> 
> With RC 1.2 being Gold, does it make sense to make this https://kojipkgs{{ 
> env_suffix }}.fedoraproject.org/compose/[[ 
>  release.version_int ]]/latest-Fedora-[[ 
> release.version_int ]]/compose/Everything/[[arch]]/os/ ?


I think probably we should just change the "if conditions" to `== 30` in places 
where it makes sense now that f29 is going to be released, which should achieve 
the same goal right? 

Dusty
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org


Re: [FBR] Include updates-testing repo during bodhi u-t run

2018-10-29 Thread Sinny Kumari
On Fri, Oct 26, 2018 at 7:07 PM Dusty Mabe  wrote:

>
>
> On 10/25/2018 01:25 PM, Sinny Kumari wrote:
> > Hi,
> >
> > Here is a patch (available in email attachment) to include
> updates-testing repo
> > as well during Atomic Host ISO creation in bodhi updates-testing run.
> Specifying
> > multiple repos to lorax should work fine on Fedora >=29 -
> > https://github.com/weldr/lorax/issues/368 .
> >
> > Can I get +1 for the patch?
> >
> > Thanks,
> > Sinny
>
>
> Suggested change below. I think we just need to uncomment out the
> commented out code right
> above the lines you changed.
>

Thanks Dusty for reviewing it!

- updates run will run lorax against
> - Everything
> - the current updates run
>
+1

- https://kojipkgs{{ env_suffix }}.
> fedoraproject.org/compose/branched/latest-Fedora-[[
> 
> release.version_int ]]/compose/Everything/[[arch]]/os/
> - the release day repo
>

With RC 1.2 being Gold, does it make sense to make this https://kojipkgs{{
env_suffix }}.fedoraproject.org/compose/[[ release.version_int
]]/latest-Fedora-[[ release.version_int ]]/compose/Everything/[[arch]]/os/ ?


> - updates-testing will run lorax against
> - Everything
> - the current updates-testing run
> - https://kojipkgs{{ env_suffix }}.
> fedoraproject.org/compose/branched/latest-Fedora-[[
> 
> release.version_int ]]/compose/Everything/[[arch]]/os/
> - the release day repo
> - https://kojipkgs{{ env_suffix }}.
> fedoraproject.org/compose/updates/f[[
>  release.version_int
> ]]-updates/compose/Everything/[[arch]]/os/
> - the last updates run
>
>
>
> diff --git a/roles/bodhi2/backend/templates/pungi.rpm.conf.j2
> b/roles/bodhi2/backend/templates/pungi.rpm.conf.j2
> index af3f5ea29..91f8535aa 100644
> --- a/roles/bodhi2/backend/templates/pungi.rpm.conf.j2
> +++ b/roles/bodhi2/backend/templates/pungi.rpm.conf.j2
> @@ -292,13 +292,11 @@ ostree_installer = [
>  [% for arch in ['x86_64', 'aarch64', 'ppc64le'] %]
>  '[[ arch ]]': {
>  "repo": [
> -# For now we need to only provide one repo to lorax
> -# See https://github.com/weldr/lorax/issues/368
> -#   "Everything",
> -#   [% if request.name == 'testing' %]
> -#   # In the case of testing, also inject the
> last stable updates
> -#   "https://kojipkgs{{ env_suffix }}.
> fedoraproject.org/compose/updates/f[[
>  release.version_int
> ]]-updates/compose/Everything/[[arch]]/os/",
> -#   [% endif %]
> +"Everything",
> +[% if request.name == 'testing' %]
> +# In the case of testing, also inject the last
> stable updates
> +"https://kojipkgs{{ env_suffix }}.
> fedoraproject.org/compose/updates/f[[
>  release.version_int
> ]]-updates/compose/Everything/[[arch]]/os/",
> +[% endif %]
>  # For f29 the compose location is under
> /compose/branched/
>  [% if release.version_int == 29 %]
>  "https://kojipkgs{{ env_suffix }}.
> fedoraproject.org/compose/branched/latest-Fedora-[[
> 
> release.version_int ]]/compose/Everything/[[arch]]/os/"
>


-- 
http://sinny.io/
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org


Re: FBR: F29 is now GA and no need of special policy changes

2018-10-29 Thread Kevin Fenzi
+1

kevin




signature.asc
Description: OpenPGP digital signature
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org