Register package about xcb.jl HOT 12 CLOSED

I think you can just answer on the General PR.
I think XCB.jl makes the most sense, and should be ok via the naming conventions, as it wraps that library.
If there's already a registered package named Xcb.jl that would be harder to resolve :D

from xcb.jl.

Registration pull request updated: JuliaRegistries/General/23401

After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.

This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:

git tag -a v0.2.0 -m "<description of version>" 902da3608ada9ee7832cad50e57fcbf5ae8c6dec
git push origin v0.2.0

Also, note the warning: This looks like a new registration that registers version 0.2.0.
Ideally, you should register an initial release with 0.0.1, 0.1.0 or 1.0.0 version numbers
This can be safely ignored. However, if you want to fix this you can do so. Call register() again after making the fix. This will update the Pull request.

from xcb.jl.

@JuliaRegistrator register()

from xcb.jl.

Registration pull request updated: JuliaRegistries/General/23401

After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.

This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:

git tag -a v0.2.0 -m "<description of version>" 46dc77d36915718627f654aa04132ad97a2d5b03
git push origin v0.2.0

Also, note the warning: This looks like a new registration that registers version 0.2.0.
Ideally, you should register an initial release with 0.0.1, 0.1.0 or 1.0.0 version numbers
This can be safely ignored. However, if you want to fix this you can do so. Call register() again after making the fix. This will update the Pull request.

from xcb.jl.

Your registry request was not accepted; you may wish to look at JuliaRegistries/General#23401 which explains why.

from xcb.jl.

I am not finding the explanation in the link you provided; where exactly should I look?
Is it because of #9? Then the situation was resolved, this XCB.jl package supersedes Xcb.jl and should go on for registration.

from xcb.jl.

Name does not meet all of the following: starts with an uppercase letter, ASCII alphanumerics only, not all letters are uppercase.
Name is not at least five characters long
The following dependencies do not have a [compat] entry that is upper-bounded and only includes a finite number of breaking releases: CEnum
Package name similar to 11 existing packages.

from xcb.jl.

That's a (badly formatted quote from JuliaRegistries/General#23401.

If you insist on the package name, you'll have to contact a human to convince them to make an exception (which might be easy, no idea; it's simply that the automated system won't accept it without a human override).

from xcb.jl.

I'd prefer to keep the name, since it wraps the existing XCB library. @SimonDanisch do you agree?
Who should I contact? Should I just leave a message in the Slack (pkg-registration) channel?

from xcb.jl.

Note that the name is not the only issue

from xcb.jl.

Note that the name is not the only issue

I added a compat entry for CEnum, so this should already be resolved

from xcb.jl.

@JuliaRegistrator register

from xcb.jl.