aboutsummaryrefslogtreecommitdiff
path: root/0.8.0/doc/doc_known_issues.doxygen
blob: db7b5627372949b93788ccc88ad9b95793ad3a6b (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
/* vim: set ft=cpp tw=80 sw=4 et : */

/**
\page KnownIssues Known Issues and Non-Issues

\section KnownIssuesMain About the issues

This document describes some of the more commonly encountered problems, issues
and things that aren't bugs but might look like they are. Pestering anyone about
these is liable to get you hurt.

\section KnownIssuesMain About the non-issues

This document also describes some things that are not bugs or missing functionality. Pestering anyone about these is liable to get you hurt a lot.

\section KnownIssuesPackages Packages

\subsection KnownIssuesUdev sys-fs/udev

Problem: <code>sys-fs/udev</code> will fail at the merge stage.

Workaround: Use <code>~arch</code> for this package. We don't support merging
fancy things like device files.

\subsection KnownIssuesKDE Some KDE libraries are broken on some amd64 profiles

Problem: Various KDE applications install libraries into the wrong libdir.

Workaround: Make sure you're running 0.6.1 or later.

Workaround: Check your profile. You can't use <code>default-linux/amd64/</code>
directly -- you have to use one of the release subdirectories. If this still
fails, someone who knows what they're doing needs to sit down and figure out
exactly what's going on for the profile in question.

\subsection KnownIssuesCheck Various packages fail src_test

Problem: Various packages fail <code>src_test</code>

Workaround: You can <code>export SKIP_FUNCTIONS="test"</code> to skip tests. This
is best done on a per-package basis via <code>bashrc</code>:

\verbatim
case "${PN}" in

    automake|glibc|e2fsprogs|neon|gettext|tar)
        export SKIP_FUNCTIONS=test
        ;;

esac
\endverbatim

Unfortunately not all package maintainers care about making their package's test
suite work. This is a nuisance, a) because it makes things much harder for arch
teams and b) because it makes it harder for users to catch bugs.

\subsection KnownIssuesRootSandbox Sandbox violations when ROOT!=/

Problem: Sandbox violations when ROOT!=/

Workaround: Paludis enforces ROOT. However, some packages don't honour ROOT. To
temporarily disable sandbox for these packages, <code>export SANDBOX_PREDICT=/</code>.

\section KnownNonIssuesPortageThings Things Portage Does

\subsection KnownNonIssuesWget wget Resume Support

Non-Problem: With Portage, <code>wget -c</code> is used to attempt to resume downloads of partial files. With Paludis, resumes are not allowed.

Rationale: This leads to corruption and wasted bandwidth far too frequently. In particular, if an error page that isn't recognised as a 404 is fetched from one server (this is common for <code>mirror://sourceforge/</code>), resume support means <code>wget</code> would then download all but the first few hundred bytes of the file from somewhere else, leading to a corrupt distfile notice only after lots of bandwidth has been wasted.

\subsection KnownNonIssesResume Resume / Skip First Support

Non-Problem: Paludis doesn't have an equivalent to --resume --skipfirst in Portage.

Rationale: Too unreliable, too flaky and far too widely abused. There's talk of echoing a command (<code>paludis -i10 =sys-apps/foo-1.23-r1 =app-misc/fnord-2 ...</code>) that can be used to resume if an ebuild exits with an error, but that's not set in stone.

*/