From 1be510f9529cb082f802408b472a77d074b394c0 Mon Sep 17 00:00:00 2001 From: Nicolas Vigier Date: Sun, 14 Apr 2013 13:46:12 +0000 Subject: Add zarb MLs html archives --- zarb-ml/mageia-dev/2012-January/011072.html | 102 ++++++++++++++++++++++++++++ 1 file changed, 102 insertions(+) create mode 100644 zarb-ml/mageia-dev/2012-January/011072.html (limited to 'zarb-ml/mageia-dev/2012-January/011072.html') diff --git a/zarb-ml/mageia-dev/2012-January/011072.html b/zarb-ml/mageia-dev/2012-January/011072.html new file mode 100644 index 000000000..83e6893f7 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-January/011072.html @@ -0,0 +1,102 @@ + + + + [Mageia-dev] Orphans - those poor orphans . . . + + + + + + + + + +

[Mageia-dev] Orphans - those poor orphans . . .

+ Thomas Backlund + tmb at mageia.org +
+ Sat Jan 7 11:59:30 CET 2012 +

+
+ +
07.01.2012 09:18, LinuxBSDos.com skrev:
+>
+> True that the user does not and should not care about definitions of an
+> orphan, but also, the user should not be put in a situation where he/she
+> will have to go hunting for what could or could not break anything.
+>
+
+Well urpme is not at fault. It's doing exactly what it's told.
+
+It cant solve packager errors. If a packager has forgot a "Requires",
+urpmi does not know that.
+
+The only things --auto-orphans has to go on is:
+1. is the package on the "keep list" such as basesystem -> dont remove.
+2. is the package required by some other package -> dont remove.
+3. is the package manually installed with urpmi/rpmdrake -> dont remove.
+4. is the package the current running kernel -> dont remove.
+
+
+So, if you find your system would be broken (or got broken) by running
+urpme --auto-orphans (or the same function in rpmdrake), and you want
+it fixed, file bug reports.
+
+And not against urpmi/rpmdrake, but the package that stopped working.
+
+--
+Thomas
+
+ + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ -- cgit v1.2.1