Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 984215 - koji mock-config produces overlapping configuration build directories
Summary: koji mock-config produces overlapping configuration build directories
Alias: None
Product: Fedora
Classification: Fedora
Component: koji
Version: 19
Hardware: All
OS: All
Target Milestone: ---
Assignee: Dennis Gilmore
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2013-07-13 17:07 UTC by Nico Kadel-Garcia
Modified: 2015-02-17 16:07 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2015-02-17 16:07:48 UTC

Attachments (Terms of Use)

Description Nico Kadel-Garcia 2013-07-13 17:07:00 UTC
Description of problem:
    "koji mock-config --tag" produces .cfg files with overlapping build directories. For example. this produces files with identical "root" settings, which means they'll use the same build directory for different mock processes.

    koji mock-config --tag f19-i386 > f19-i386.cfg
    koji mock-config --tag f19-x86_64 > f19-x86_64.cfg

    This is safe only if the same mock server is never used to produce software for different architectures.

Version-Release number of selected component (if applicable):

How reproducible:
   Run and compare results of "koji mock-config".

Steps to Reproduce:
1. koji mock-config --tag f19-i386 > f19-i386.cfg
2. koji mock-config --tag f19-x86_64 > f19-x86_64.cfg
3. grep "'root'" *.cfg

Actual results:
    f19-i386.cfg: config_opts['root]' = f19
    f19-x86_64.cfg: config_opts['root]' = f19

Expected results:
    f19-i386.cfg: config_opts['root]' = f19-i386
    f19-x86_64.cfg: config_opts['root]' = f19-x86_64

Additional info:

Comment 1 Nico Kadel-Garcia 2013-07-14 10:06:16 UTC
The risk is greatest for people like me who test both x86_64 and i386 builds on the same mock server.

Comment 2 Mike McLean 2013-07-16 15:48:10 UTC
These are not valid koji commands. Are you using a modified koji?

$ koji mock-config --tag f19-i386
Usage: koji mock-config [options] name
(Specify the --help global option for a list of other help options)

koji: error: Please specify a name for your buildroot

The mock-config subcommand require the name arg, which it uses in the name of the build directory.

Comment 3 Fedora End Of Life 2015-01-09 18:53:47 UTC
This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 19 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 4 Fedora End Of Life 2015-02-17 16:07:48 UTC
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this

Thank you for reporting this bug and we are sorry it could not be fixed.

Note You need to log in before you can comment on or make changes to this bug.