Opened 13 months ago

Closed 3 months ago

Last modified 3 months ago

#14717 closed bug (fixed)

HaikuDepot Server doesn't get new packages

Reported by: CodeforEvolution Owned by: kallisti5
Priority: normal Milestone:
Component: Website/HaikuDepotServer Version:
Keywords: Cc: kallisti5
Blocked By: Blocking: #14727, #15265
Has a Patch: no Platform: All


I’ve found despite new packages being added and updated on my system, such new packages and updates haven’t been represented in the packages tab on the main Haiku website as normal.

Change History (12)

comment:1 by waddlesplash, 13 months ago

Cc: kallisti5 added
Component: Website/www.haiku-os.orgWebsite
Owner: changed from waddlesplash to apl-haiku
Status: newassigned

comment:2 by waddlesplash, 12 months ago

Blocking: 14727 added

comment:3 by waddlesplash, 12 months ago

Summary: Packages Tab on Haiku Website Doesn’t UpdateHaikuDepot Server doesn't get new packages

comment:4 by apl-haiku, 12 months ago

It would be easier if we keep operational queries on the mailing list in the first instance. That would be helpful because the problem here is most likely related to the HDS deployment environment rather than a software bug. As I no longer have access to the deployment environment, I cannot diagnose this issue.

Last edited 12 months ago by apl-haiku (previous) (diff)

comment:5 by apl-haiku, 12 months ago

Owner: changed from apl-haiku to kallisti5

comment:6 by exlmotodev, 12 months ago

Any news?

comment:7 by kallisti5, 12 months ago

There aren't many details in this ticket, but the original description was the biggest give-away "Packages Tab on Haiku Website Doesn’t Update"

I never added the cron jobs per I went ahead and configured the import job for haikuports.

I think I need to add additional cron jobs for the other configured repositories?

  • BeSly
  • Clasqm
  • FatElk

I really wish 152 above would get some love :-| Cron jobs work, but are kind of a hack.

comment:8 by apl-haiku, 12 months ago

Hello Alex; You do not need to setup cron tasks for each repository. You only need to setup the following cron tasks;

32 * * * * curl ...../__maintenance/hourly
45 3 * * * curl ...../__maintenance/daily

In particular, the daily maintenance task scheduled with cron above will, amongst other things, refresh the data for all active repositories in the HDS system.

As part of a given repository's presumably scripted (Python etc...) build/update process it is advisable but not necessary for the repository build script (note: not cron) to invoke a URL such as...


...when it (eg: Python script) finishes building/updating the repository. The documentation for this HDS endpoint are described at [1]. By having the repository build/update script do this, HDS will import the repository data faster without having to wait for periodic polls performed during the HDS daily maintenance task.

I am happy to help anybody with questions about this on the HDS mailing list.

I will take a look to see if I can setup task-scheduling inside HDS using Quartz scheduler, but am presently (slowly) busy with changes in the C++ code of the desktop application.


comment:9 by waddlesplash, 4 months ago

Blocking: 15265 added

comment:10 by diver, 3 months ago

Resolution: fixed
Status: assignedclosed

Seems to be fixed now.

comment:11 by diver, 3 months ago

Component: WebsiteWebsite/HaikuDepotServer

And now it doesn't get new packages again.

comment:12 by apl-haiku, 3 months ago

The cron based scheduling discussed above was replaced with an internal-application-server scheduler in commit 656292be79c087dc267418ad0f5fb38df3c3b7ba (2018-12-18). This was then deployed in 1.0.108 sometime after 2019-01-25.

Note: See TracTickets for help on using tickets.