Opened 7 years ago

Closed 6 years ago

Last modified 6 years ago

#10875 closed bug (fixed)

Paladin.1.3.pkg still fails to install

Reported by: waddlesplash Owned by: stippi
Priority: normal Milestone: R1/beta1
Component: Applications/PackageInstaller Version: R1/Development
Keywords: Cc:
Blocked By: Blocking:
Platform: All


Obtained from here:

It installs 6 files and then hits an error.

Change History (11)

comment:1 by codewrangler, 7 years ago

Try the one I posted on Haikuware....

It's in Haiku Package format. You just drop it into /boot/home/config/packages and it should just show up in your applications menu on the deskbar.

comment:2 by waddlesplash, 7 years ago

I knew that :) However, this PKG exhibits a bug in PackageInstaller, and so it still should be fixed.

comment:3 by luroh, 6 years ago

Owner: changed from sil2100 to stippi
Status: newassigned

comment:4 by kallisti5, 6 years ago

Milestone: R1R1/beta1

The .pkg files will continue to fail as they expect to be able to write things to read-only paths. We need a work around binary that will extract .pkg files to a folder so they can be repackaged / used.

The work around for the moment is to boot R1A4 and use that to extract .pkg files.

comment:5 by codewrangler, 6 years ago


That's what I have already done. I then took the additional steps to create an HPKG for Paladin. You can find it posted on

Just drop it into /boot/home/config/packages and it should just show up in your applications menu on the deskbar.

comment:6 by stippi, 6 years ago

No, the package doesn't write anywhere. It is PackageInstaller which reads the package contents and executes scripts which then tries to write in read-only locations. But one can analyse the package and fix it in PackageInstaller (rewriting paths). Even modifying the post-install scripts was not beyond me. I already do that for other packages which try to directly copy/move files to read-only locations.

comment:7 by kallisti5, 6 years ago

This one looks to have a solution as per

We need to find all paths these packages are writing to that are read-only and redirect them to something writable.

... or maybe we could wrangle all .pkg installs into a single root directory? ~/legacypackage/. That way things can be ran and repackaged into hpkg's more easily post-pm.

comment:8 by stippi, 6 years ago

You realize that "wrangling all .pkg installs into a single root directory" needs the same path rewriting implementation that already happens (although apparently incompletly so)?

comment:9 by waddlesplash, 6 years ago

Milestone: R1/beta1R1/alpha5

comment:10 by stippi, 6 years ago

Resolution: fixed
Status: assignedclosed

Fixed in hrev47275.

Last edited 6 years ago by stippi (previous) (diff)

comment:11 by pulkomandy, 6 years ago

Milestone: R1/alpha5R1/beta1
Note: See TracTickets for help on using tickets.