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 1361110 - mock does not support '@' in dist-tag
Summary: mock does not support '@' in dist-tag
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: mock
Version: 23
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Clark Williams
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-07-28 11:09 UTC by clime
Modified: 2016-07-28 15:40 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-07-28 15:38:41 UTC


Attachments (Terms of Use)

Description clime 2016-07-28 11:09:09 UTC
Description of problem:
If there is at sign '@' included in a configured value for package dist-tag

e.g. config_opts['macros']['%dist'] = "foo@1.3@4"

then mock fails with the following error:

error: line 3: Illegal char '@' (0x40) in: Release:	1.git.5.c6d3313.foo@1.23@4


How reproducible:
always


Steps to Reproduce:
- include '@' sign for a value of dist-tag in a given mock config

Actual results:
- mock complains and build fails

Expected results:
- mock doesn't complain and build succeeds

Additional info:
- This is needed for modularity movement

Comment 1 clime 2016-07-28 11:10:46 UTC
Sorry, the module version should have been 1.23 in the configuration line example, that is:

config_opts['macros']['%dist'] = "foo@1.23@4"

Comment 2 Mikhail Campos 2016-07-28 15:21:57 UTC
This is not a mock issue. I don't thing that rpm supports '@' symbol in Epoch/Version/Release tags.

Comment 3 Miroslav Suchý 2016-07-28 15:38:41 UTC
*nod* this is rpm restriction

Release: 1@

and pass it to rpmbuild. It will fail with this error.
And this will likely not change. So modularity will have to come with different character.

Comment 4 Petr Šabata 2016-07-28 15:40:20 UTC
(In reply to Miroslav Suchý from comment #3)
> So modularity will have to come with
> different character.

Yeah, it doesn't really matter what it is :)


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