Opened 23 months ago

Closed 23 months ago

Last modified 23 months ago

#14487 closed task (fixed)

No haikuports updates...

Reported by: khallebal Owned by: kallisti5
Priority: normal Milestone: Unscheduled
Component: Sys-Admin Version: R1/Development
Keywords: Cc:
Blocked By: Blocking:
Platform: x86

Description (last modified by humdinger)

Although new recipes are being merged daily, the packages are not being updated, not being built perhaps? at least for 32 bits.

Change History (8)

comment:1 by humdinger, 23 months ago

Description: modified (diff)

Have you set the correct repo address (pkgman list):

comment:2 by khallebal, 23 months ago

Yes i'm using the new URL's posted by kallisti5, when i do pkgman update i get only updates from the haiku repo, and the depot server has not been updated for 4 days either.

comment:3 by waddlesplash, 23 months ago

Owner: changed from haiku-web to kallisti5
Status: newassigned

It appears the repos have been updated (e.g. pciutils 3.6) but indeed HaikuDepot is still stuck with 3.5.

comment:4 by cb88, 23 months ago

haven't gotten any OS updates insce hrev52339 here, and was getting them regularly before also... that said I am getting *some* updates.

And pciutils 3.6 is on HaikuDepot now...

comment:5 by waddlesplash, 23 months ago

Resolution: fixed
Status: assignedclosed

OK it's just the delayed Cron then.

The Haiku repository updating infrequently is a known issue. We just manually trigger a new build once every few days atm.

comment:6 by apl-haiku, 23 months ago

and the depot server ​ has not been updated for 4 days either.

Unfortunately I no longer have any access to the deployment environment for HDS; logs database etc... so am unable to comment or help around this problem until I can get some access.

Previously a cron task would invoke HDS to enqueue a task to poll the HPKR data for new packages. I don't know if this cron was re-instated after the migration to containers. If the new data is in the HPKR, it will pick it up and update its records accordingly. The API endpoint for this is;


Also, it is the intention that the event of re-building the HPKR data (eg; an update in haikuports) should raise an event with HDS to re-scan the specific HPKR data so that updates happen soon after a repository update. It is possible to trigger this with the following URL;


comment:7 by kallisti5, 23 months ago

sorry, i've been working on Haiku for a week straight and had to take a small break for a few days for real life stuff :-)


  1. Fix Buildbot scheduler for Haiku repo. It isn't triggering for some unknown reason.
  2. Deploy cron job to trigger HaikuPorts imports

I think waddlesplash already did #2?

comment:8 by waddlesplash, 23 months ago

No I didn't?

Note: See TracTickets for help on using tickets.