RejectedSoftware Forums

Sign up

The registry won't update a package of mine?

I've been clicking the Trigger manual update button for a while now and the package is not updating. It still shows v1.1.1 when i've released v1.1.2 on github.

http://code.dlang.org/packages/tkd

Are there any issues with the registry?

Re: The registry won't update a package of mine?

I have identic problem. Remove package and register it again made my package unavailable.

I change description in dub.json. Can it cause of problem?

http://code.dlang.org/packages/descore

On Wed, 18 Feb 2015 17:09:21 GMT, Gary Willoughby wrote:

I've been clicking the Trigger manual update button for a while now and the package is not updating. It still shows v1.1.1 when i've released v1.1.2 on github.

http://code.dlang.org/packages/tkd

Are there any issues with the registry?

Re: The registry won't update a package of mine?

Am 18.02.2015 um 21:15 schrieb Oleg B:

I have identic problem. Remove package and register it again made my package unavailable.

I change description in dub.json. Can it cause of problem?

http://code.dlang.org/packages/descore

On Wed, 18 Feb 2015 17:09:21 GMT, Gary Willoughby wrote:

I've been clicking the Trigger manual update button for a while now and the package is not updating. It still shows v1.1.1 when i've released v1.1.2 on github.

http://code.dlang.org/packages/tkd

Are there any issues with the registry?

In such cases, the most common cause is an error in dub.json. Do you (or
Gary) get any errors listed on the package management page
(http://code.dlang.org/my_packages/<package name>)?

The plan is to send an explicit e-mail is such a case, but nobody had
the time to implement this so far.

Re: The registry won't update a package of mine?

Am 19.02.2015 um 20:50 schrieb Sönke Ludwig:

Am 18.02.2015 um 21:15 schrieb Oleg B:

I have identic problem. Remove package and register it again made my
package unavailable.

I change description in dub.json. Can it cause of problem?

http://code.dlang.org/packages/descore

On Wed, 18 Feb 2015 17:09:21 GMT, Gary Willoughby wrote:

I've been clicking the Trigger manual update button for a while now
and the package is not updating. It still shows v1.1.1 when i've
released v1.1.2 on github.

http://code.dlang.org/packages/tkd

Are there any issues with the registry?

In such cases, the most common cause is an error in dub.json. Do you (or
Gary) get any errors listed on the package management page
(http://code.dlang.org/my_packages/<package name>)?

The plan is to send an explicit e-mail is such a case, but nobody had
the time to implement this so far.

Okay, tkd already seems to be updated. What was the cause?

Re: The registry won't update a package of mine?

On Thu, 19 Feb 2015 20:53:38 +0100, Sönke Ludwig wrote:

Okay, tkd already seems to be updated. What was the cause?

Nothing on my end. The project is nearly a year old and i haven't touched the dub.json file. I just make changes to code occasionally and create a new release in github. So i've done nothing since raising this issue.

Re: The registry won't update a package of mine?

The registry seems to run in a continuous loop of updating. I usually see the following message:

Package is scheduled for an update check. Still have to wait for 407 other packages to complete.

Then i can't update my package. I wonder if a cron job is not finishing before it is run again?

Re: The registry won't update a package of mine?

Am 25.02.2015 um 12:47 schrieb Gary Willoughby:

The registry seems to run in a continuous loop of updating. I usually see the following message:

Package is scheduled for an update check. Still have to wait for 407 other packages to complete.

Then i can't update my package. I wonder if a cron job is not finishing before it is run again?

Something like that. I've observed yesterday how the update queue seemed
to get reset when the half-hourly update of all packages was triggered.
But it's supposed to just add those packages that are not already in the
queue - I'll need to dig a little deeper. There were also some random
characters in the log file, so maybe it's something worse.