www.digitalmars.com         C & C++   DMDScript  

digitalmars.D - Package and account on code.dlang.org acting weird

reply =?UTF-8?B?Q2zDqWJlcg==?= Zavadniak <contato+til cleber.solutions> writes:
Hey, I realized Til package is stuck on 0.2.2. While trying to 
login and, somehow, fix it, found that "Looks like you haven't 
registered any packages yet".

WEEEEEEEEEEEEIRD!

About the packages/account, it really doesn't seem like I 
registered with another e-mail, but for now I'm leaving that 
aside... However, about the package version (it should at least 
be showing 0.3.0), is there something in the git repository I'm 
getting wrong, maybe?

https://code.dlang.org/packages/til/versions

(2021-07-03T02:50:00 - it still shows only 0.2.2).
Jul 02
next sibling parent =?UTF-8?B?Q2zDqWJlcg==?= Zavadniak <contato+til cleber.solutions> writes:
Hum, okay, it has catch up and is on 0.3.1, now.
Jul 03
prev sibling parent =?UTF-8?Q?S=c3=b6nke_Ludwig?= <sludwig outerproduct.org> writes:
Am 03.07.2021 um 04:48 schrieb Cl├ęber Zavadniak:
 Hey, I realized Til package is stuck on 0.2.2. While trying to login 
 and, somehow, fix it, found that "Looks like you haven't registered any 
 packages yet".
 
 WEEEEEEEEEEEEIRD!
 
 About the packages/account, it really doesn't seem like I registered 
 with another e-mail, but for now I'm leaving that aside... However, 
 about the package version (it should at least be showing 0.3.0), is 
 there something in the git repository I'm getting wrong, maybe?
 
 https://code.dlang.org/packages/til/versions
 
 (2021-07-03T02:50:00 - it still shows only 0.2.2).
I'm unsure what happens here, everything looks fine from the inside, but the package is for some reason not updated as part of the regular automatic updates. I changed the package owner and it is listed just fine in that case. A manual update also worked normally (hence why it's up-to-date now). Also, "til_exec" seems to be updated fine. A test with a locally replicated instance also worked completely normally, even with the original user account. Next step I'd have to add some additional logging to the live instance to get more insight.
Jul 03