So I went to http://code.dlang.org/register_package to register a new package. I got errors. First, "License is missing". That should have a pointer to the pertinent documentation. Second, "No tags". There were a few explanations, but again it would be great to point to the appropriate documentation.

Sadly after those two and after getting my package in order, I got: "A package with the same name is already registered" with no pointer to it. (I assume it is @tsbockman's work.) Fine, the problem now is there's no option on how to publish a package that keeps the same github name yet exposes a different name...


Andrei

On 08/23/2016 02:11 PM, Andrei Alexandrescu wrote:
> So I went to http://code.dlang.org/register_package to register a new
> package. I got errors. First, "License is missing". That should have a
> pointer to the pertinent documentation. Second, "No tags". There were a
> few explanations, but again it would be great to point to the
> appropriate documentation.
>
> Sadly after those two and after getting my package in order, I got: "A
> package with the same name is already registered" with no pointer to it.
> (I assume it is @tsbockman's work.) Fine, the problem now is there's no
> option on how to publish a package that keeps the same github name yet
> exposes a different name...
>
>
> Andrei

Hm, after removing the old remote and creating a new one called "checkedint_andralex" which does not exist on code.dlang.org, I still get "A package with the same name is already registered.". No idea how to proceed, please advise. -- Andrei

On Tuesday, 23 August 2016 at 18:17:33 UTC, Andrei Alexandrescu wrote:
> On 08/23/2016 02:11 PM, Andrei Alexandrescu wrote:
>> So I went to http://code.dlang.org/register_package to register a new
>> package. I got errors. First, "License is missing". That should have a
>> pointer to the pertinent documentation. Second, "No tags". There were a
>> few explanations, but again it would be great to point to the
>> appropriate documentation.
>>
>> Sadly after those two and after getting my package in order, I got: "A
>> package with the same name is already registered" with no pointer to it.
>> (I assume it is @tsbockman's work.) Fine, the problem now is there's no
>> option on how to publish a package that keeps the same github name yet
>> exposes a different name...
>>
>>
>> Andrei
>
> Hm, after removing the old remote and creating a new one called "checkedint_andralex" which does not exist on code.dlang.org, I still get "A package with the same name is already registered.". No idea how to proceed, please advise. -- Andrei

It referes to the package name set in the SDL/JSON configuration. You have to change that. The GitHub project name means nothing for DUB.

On 08/23/2016 02:17 PM, Andrei Alexandrescu wrote:
> On 08/23/2016 02:11 PM, Andrei Alexandrescu wrote:
>> So I went to http://code.dlang.org/register_package to register a new
>> package. I got errors. First, "License is missing". That should have a
>> pointer to the pertinent documentation. Second, "No tags". There were a
>> few explanations, but again it would be great to point to the
>> appropriate documentation.
>>
>> Sadly after those two and after getting my package in order, I got: "A
>> package with the same name is already registered" with no pointer to it.
>> (I assume it is @tsbockman's work.) Fine, the problem now is there's no
>> option on how to publish a package that keeps the same github name yet
>> exposes a different name...
>>
>>
>> Andrei
>
> Hm, after removing the old remote and creating a new one called
> "checkedint_andralex" which does not exist on code.dlang.org, I still
> get "A package with the same name is already registered.". No idea how
> to proceed, please advise. -- Andrei

And then in desperation I used mcookie to create repo 6c47688463988a65cbe25a9f44977a74, which I tried to register. No avail. -- Andrei

On 08/23/2016 02:18 PM, Lodovico Giaretta wrote:
> It referes to the package name set in the SDL/JSON configuration. You
> have to change that. The GitHub project name means nothing for DUB.

Thank you. That should definitely be part of the documentation. -- Andrei

On 08/23/2016 02:18 PM, Lodovico Giaretta wrote:
> It referes to the package name set in the SDL/JSON configuration. You
> have to change that. The GitHub project name means nothing for DUB.

Now I have successfully published it: http://code.dlang.org/my_packages/checkedint_andralex. However, I see this error on the page:

Version 0.0.1: Package name (checkedint) does not match the original package name (checkedint_andralex). Check dub.sdl.

What should I check? My dub.sdl lists checkedint_andralex.


Andrei

On Tuesday, 23 August 2016 at 18:28:54 UTC, Andrei Alexandrescu wrote:
> On 08/23/2016 02:18 PM, Lodovico Giaretta wrote:
>> It referes to the package name set in the SDL/JSON configuration. You
>> have to change that. The GitHub project name means nothing for DUB.
>
> Now I have successfully published it: http://code.dlang.org/my_packages/checkedint_andralex. However, I see this error on the page:
>
> Version 0.0.1: Package name (checkedint) does not match the original package name (checkedint_andralex). Check dub.sdl.
>
> What should I check? My dub.sdl lists checkedint_andralex.
>
>
> Andrei

Because version 0.0.1 will always refer to your 0.0.1 tag. And in the commit referred by the tag, the SDL name is still "checkedint". The config file may change between releases, and DUB will always use the config file that shipped with each tag. So the only way to solve the problem is to create a new tag with the correct name setting, and maybe remove the old tag.

On Tuesday, 23 August 2016 at 18:28:54 UTC, Andrei Alexandrescu wrote:
> On 08/23/2016 02:18 PM, Lodovico Giaretta wrote:
>> It referes to the package name set in the SDL/JSON configuration. You
>> have to change that. The GitHub project name means nothing for DUB.
>
> Now I have successfully published it: http://code.dlang.org/my_packages/checkedint_andralex. However, I see this error on the page:
>
> Version 0.0.1: Package name (checkedint) does not match the original package name (checkedint_andralex). Check dub.sdl.
>
> What should I check? My dub.sdl lists checkedint_andralex.
>
>
> Andrei

By the way, posting links to code.dlang.org/my_packages/<package name> is useless, as that page is only available to the package owner.

On Tuesday, 23 August 2016 at 18:32:50 UTC, Lodovico Giaretta wrote:
> On Tuesday, 23 August 2016 at 18:28:54 UTC, Andrei Alexandrescu wrote:
>> Now I have successfully published it: http://code.dlang.org/my_packages/checkedint_andralex. However, I see this error on the page:
>>
>> Version 0.0.1: Package name (checkedint) does not match the original package name (checkedint_andralex). Check dub.sdl.
>>
>> What should I check? My dub.sdl lists checkedint_andralex.
>>
>>
>> Andrei
>
> Because version 0.0.1 will always refer to your 0.0.1 tag. And in the commit referred by the tag, the SDL name is still "checkedint". The config file may change between releases, and DUB will always use the config file that shipped with each tag. So the only way to solve the problem is to create a new tag with the correct name setting, and maybe remove the old tag.

Expanding on this, you can see from the public package page https://code.dlang.org/packages/checkedint_andralex that the only available version is ~master. There's no mention of v0.0.1, as the SDL file shipped with that tag has a name mismatch with the registered package name, so the release is discarded by DUB.

On 08/23/2016 02:32 PM, Lodovico Giaretta wrote:
> On Tuesday, 23 August 2016 at 18:28:54 UTC, Andrei Alexandrescu wrote:
>> On 08/23/2016 02:18 PM, Lodovico Giaretta wrote:
>>> It referes to the package name set in the SDL/JSON configuration. You
>>> have to change that. The GitHub project name means nothing for DUB.
>>
>> Now I have successfully published it:
>> http://code.dlang.org/my_packages/checkedint_andralex. However, I see
>> this error on the page:
>>
>> Version 0.0.1: Package name (checkedint) does not match the original
>> package name (checkedint_andralex). Check dub.sdl.
>>
>> What should I check? My dub.sdl lists checkedint_andralex.
>>
>>
>> Andrei
>
> Because version 0.0.1 will always refer to your 0.0.1 tag. And in the
> commit referred by the tag, the SDL name is still "checkedint". The
> config file may change between releases, and DUB will always use the
> config file that shipped with each tag. So the only way to solve the
> problem is to create a new tag with the correct name setting, and maybe
> remove the old tag.

OK, bumped the version and then removed the old tag. Thanks! -- Andrei