#6181: atomic: testing/ ref for f22

Fedora Release Engineering rel-eng at lists.fedoraproject.org
Sat May 23 20:50:13 UTC 2015


#6181: atomic: testing/ ref for f22
------------------------------+-----------------------
  Reporter:  walters          |      Owner:  rel-eng@…
      Type:  task             |     Status:  new
 Milestone:  Fedora 22 Final  |  Component:  other
Resolution:                   |   Keywords:
Blocked By:                   |   Blocking:
------------------------------+-----------------------

Comment (by lmacken):

 Yep, you're right. I have this patch queued up in git and will push it out
 after the current updates push is done.

 {{{
 #!patch

 --- a/modules/bodhi/files/atomic-config.py
 +++ b/modules/bodhi/files/atomic-config.py
 @@ -17,7 +17,7 @@ config = dict(
              'tree': 'docker-host',
              'treefile': {
                  'include': 'fedora-atomic-docker-host.json',
 -                'ref': 'fedora-atomic/f22/x86_64/updates/docker-host',
 +                'ref': 'fedora-atomic/f22/x86_64/docker-host',
                  'repos': ['fedora-22-branched', 'updates'],
                  'packages': [],
              },
 @@ -44,7 +44,7 @@ config = dict(
              'tree': 'docker-host',
              'treefile': {
                  'include': 'fedora-atomic-docker-host.json',
 -                'ref': 'fedora-atomic/f22/x86_64/docker-host',
 +                'ref': 'fedora-atomic/f22/x86_64/testing/docker-host',
                  'repos': ['fedora-22-branched', 'updates', 'updates-
 testing'],
                  'packages': [],
              },

 }}}

 Since we're currently frozen, a +1 or two would be helpful.

 Also, do we want to clean up these stray refs before the final release? If
 so, how do we go about doing that?

-- 
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/6181#comment:4>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project


More information about the rel-eng mailing list