Haiku monthly activity report - 08/2017 | Haiku Project

Hi there, it's time for a new monthly report!

This report covers hrev31437-hrev51402

First of all, I have updated the git stats pages for haiku and haikuports. These provide an overview of the overall activity with various graphs, author ranking, etc.

This is a companion discussion topic for the original entry at https://www.haiku-os.org/blog/pulkomandy/2017-09-07_haiku_monthly_activity_report_august_2017/

Great to see the package builder repo is now available for testing - really does motivate the Haiku Ports recipe writers/fixers when the results are so apparent.


The builders are indeed great to QA what comes into the haikuports master branch. Though I wouldn’t trust the repo it generates yet (for instance, policy checks aren’t enforced, which is OK for testing, perl modules are broken). A beta repo will probably happens on its own branch with a full rebuild.

Yes, I think I will test on a separate installation. Once the beta branch is created, is the aim to have haikuporter contributors test out the builds on the master branch (in a separate install) and then someone will merge from there to the beta branch when packages are tested? (a bit like Debian testing to stable?)


I am going to experiment using the current package repos to see how it feels with regard to stability and problems encountered. According to that we can decide wether to use the repo directly, or have a stable/testing approach. Since there is already a review when merging pull requests to the main repo, it may not be needed, but I want to make an opinion on that by testing the repos to see what happens.

My journey did not start too well: beam does not start, so first I’ll need to fix that recipe.

Where do we report bugs in these repos?

All Haikuports bugs and pull requests can be made here:

my issue is with the automated package build system, not the haikuports recipe or haikuporter. haikuporter builds yab and yab-ide on 64 bit just fine. The automated package build system doesn’t seem to be able to build these .hpkg files.

Maybe then in the main Haiku bugtracker, or if it’s with Haikuports’ automated build system that they run, an issue there wouldn’t hurt.

The automated build system is part of haikuports/haikuporter, so report issues there.

@PulkoMandy : “hrev31437-hrev51402” this is plenty changes for just one month…

Pull requests welcome!

Now this is a problem… http://eu.hpkg.haiku-os.org/haikuports/master/repository/x86_gcc2/current/packages/ and http://packages.haiku-os.org/haikuports/master/repo/x86_gcc2/current/packages/ have broken versions of yab and http://eu.hpkg.haiku-os.org/haikuports/master/repository/x86_64/current/packages/ has no version of yab. issue https://github.com/haikuports/haikuporter/issues/138 seems to be being ignored. now what?