{ "bug_id": "1489983", "monitor": "monitoring-with-scratch", "upstreamurl": "", "namespace": "rpms", "description": "", "action": "new_repo", "branch": "master", "repo": "llvm4.0", "summary": "Compatibility package for LLVM 4.0" }
The repository name is invalid. It must be at least two characters long with only letters, numbers, hyphens, and/or underscores.
Metadata Update from @limb: - Issue close_status updated to: Invalid - Issue status updated to: Closed (was: Open)
Is this a new requirement for fedora 28? The previous compat libs for llvm have used '.' in their names. For example: https://apps.fedoraproject.org/packages/llvm3.9
I honestly don't know why the tool has decided it needs to reject those characters. They are perfectly valid and permitted (encouraged, even) by the packaging guidelines.
@pingou, @mprahl, can you answer? I don't recall.
Metadata Update from @tibbs: - Issue set to the milestone: None
@limb I believe @ralph and @kevin know the answer to this.
@tibbs is of course completely correct here.
https://fedoraproject.org/wiki/Packaging:Naming?rd=Packaging:NamingGuidelines#MultiplePackages
" The package version, which SHOULD include the periods present in the original version. "
The tool should be fixed here. I guess by allowing . in the name when the name ends in a [0-9] ?
@pingou can you modify the regex to allow this in src.fedoraproject.org please?
Honestly periods are valid in other places in the package name as well. The guidelines just say they shouldn't be used as "separators" and then doesn't really define what that is. (It means the dashes in "python-dnf-plugin-system-upgrade" and "perl-Archive-Extract-tgz-Archive-Tar-IO-Zlib".
But basically from the view that this tool has, it should simply allow dots anywhere save the beginning or end of the package name. "node.js" would have been a perfectly valid package name. There's obviously been enough confusion about this that I should dig into that language; it's the only portion of the naming guidelines I haven't rewritten at this point.
Will do, but I'll have to ask the infra list to allow the hotfix since we're in freeze and I'll try to find something more durable for pagure itself.
In the mean time, is it possible to manually create the new repository?
I thought the freeze break request for a hotfix was approved two days ago, so this might even be deployed now.
Metadata Update from @tstellar: - Issue status updated to: Open (was: Closed)
It doesn't look like the new repository has been created yet.
I guess not. That's unfortunate. I'll ping some folks to see what we can do.
This is blocked on: https://pagure.io/fedrepo_req/issue/110
It looks like all the fixes have been merged. Can this request be completed now?
The PDC branch already exists
Metadata Update from @ralph: - Issue status updated to: Open (was: Closed)
@tstellar okay, it should work the next time it's processed.
The Pagure repository was created at https://src.fedoraproject.org/rpms/llvm4.0
Metadata Update from @limb: - Issue close_status updated to: Processed - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.