Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#7381 - reiser4progs-1.0.6-1 and libaal-1.0.5-2 configured with --prefix=/usr
Attached to Project:
Arch Linux
Opened by Jan Peter den Heijer (klixon) - Thursday, 07 June 2007, 05:59 GMT
Last edited by James Rayner (iphitus) - Thursday, 07 February 2008, 11:23 GMT
Opened by Jan Peter den Heijer (klixon) - Thursday, 07 June 2007, 05:59 GMT
Last edited by James Rayner (iphitus) - Thursday, 07 February 2008, 11:23 GMT
|
Detailsreiser4progs and libaal have "./configure --prefix=/usr" in their PKGBUILDs.
I have /usr on a separate partition. This effectively blocks fsck.reiser4 from running at boot time (/usr isn't mounted yet...) Could you "./configure --prefix=/" ? |
This task depends upon
changed:
- using "./configure --prefix=/usr --exec-prefix=/" in both
- using "make DESTDIR=$startdir/pkg/ install" in both
- Added license-fields to both
- Added arches to libaal
- bumped pkgrel's of both
I do advice you to thoroughly check these, but i've had no problems running these so far.
Hope it helps.