On Thu, 8 May 2008 09:57:10 +0200 Dirk Heinrichs <[EMAIL PROTECTED]> wrote: > Seems I found the reason. Wanted to test btrfs [1] and chose all > Gentoo related directories for the test ($PORTDIR, $DISTDIR and > $PORTAGE_TMPDIR were put on a btrfs volume). Remounting the old, xfs > based volumes brought paludis back to normal behaviour. However, the > question remains: Why does a change in the underlying fs affect > paludis at all (and not portage/emerge) ?
I strongly suspect it's a bug in btrfs... So let's track down which syscalls are affected... Find some small package (hilite is a good one) and try merging it. When it's merging the file, you'll get something like: >>> /usr/bin/hilite What're the three symbols in the first column when this happens? -- Ciaran McCreesh
signature.asc
Description: PGP signature
_______________________________________________ paludis-user mailing list [email protected] http://lists.pioto.org/mailman/listinfo/paludis-user
