#550 New Repo for "rpms/compat-ImageMagick6.9.3"
Closed: Invalid 6 years ago Opened 6 years ago by pwalter.

{
 "action": "new_repo",
 "branch": "master",
 "bug_id": "1485869",
 "description": "",
 "monitor": "monitoring-with-scratch",
 "namespace": "rpms",
 "repo": "compat-ImageMagick6.9.3",
 "summary": "Compat package with ImageMagick 6.9.3 libraries",
 "upstreamurl": ""
}

The PDC branch already exists

Metadata Update from @limb:
- Issue close_status updated to: Invalid
- Issue status updated to: Closed (was: Open)

6 years ago

Reopening. The repo didn't seem to get created.

Metadata Update from @pwalter:
- Issue status updated to: Open (was: Closed)

6 years ago

This was the error:
Error: A failure occurred while creating a new project in Pagure at https://src.fedoraproject.org/api/0/new. The status code was "400". The error was "{'error': 'Invalid or incomplete input submited', 'error_code': 'EINVALIDREQ', 'errors': {'name': ['Invalid input.']}}".

@pingou , @mprahl ?

Metadata Update from @limb:
- Issue set to the milestone: None

6 years ago

The PDC branch already exists

Metadata Update from @limb:
- Issue close_status updated to: Invalid
- Issue status updated to: Closed (was: Open)

6 years ago

I am getting the same error. I'll check the Pagure source code.

It seems like periods are blocked in the validation regex in Pagure. I submitted a PR to allow periods:
https://pagure.io/pagure/pull-request/2553

Should be hotfixed in pagure prod. Reopening.

Metadata Update from @pwalter:
- Issue status updated to: Open (was: Closed)

6 years ago

The PDC branch already exists

Metadata Update from @limb:
- Issue close_status updated to: Invalid
- Issue status updated to: Closed (was: Open)

6 years ago

Hey - after talking to @pbrobinson and @ausil, we figured out that package names with . characters should be disallowed. It's going to cause problems with rpmlib's parsing later down the line.

The package should instead be called compat-ImageMagick693. @pwalter, sorry for the confusion. We'll keep this closed. Can you re-do the review with the new package name and then send it back here afterwards with the new name?

Sure, no problem! I'll update the name. Thanks for looking at this.

I'll note that dots are explicitly allowed (and required in this case for parallel installable packages) in the packaging guidelines. We should probably get the guidelines updated as well then if you are saying that dots can cause issues.

I responded in the FPC ticket, but to reiterate: the guidleines are pretty clear that the periods are in fact desired here. I have not previousy heard any suggestion that periods would somehow break something.

Login to comment on this ticket.

Metadata