Le 07/01/2012 11:14, ptyxs a écrit :
Le 06/01/2012 17:55, Colin Guthrie a écrit :
'Twas brillig, and Robert Fox at 06/01/12 10:16 did gyre and gimble:
After latest Cauldron updates, I got a real long list of suggested
orphans - but I believe some of these packages are needed (like hal or
Le 07/01/2012 21:13, Maarten Vanraes a écrit :
Op zaterdag 07 januari 2012 17:48:36 schreef Thomas Spuhler:
[...]
It seems to me, auto-orphans gives more headaches than benefits. Why are we
clinching to it?
because it works for me (and several others)
It works SOMETIMES and sometimes it
2012/1/8 ptyxs pt...@free.fr:
Le 07/01/2012 21:13, Maarten Vanraes a écrit :
Op zaterdag 07 januari 2012 17:48:36 schreef Thomas Spuhler:
[...]
It seems to me, auto-orphans gives more headaches than benefits. Why are
we
clinching to it?
because it works for me (and several others)
It
On Sat, Jan 7, 2012 at 16:48, Thomas Spuhler tho...@btspuhler.com wrote:
On Friday, January 06, 2012 12:57:39 PM Sander Lepik wrote:
06.01.2012 21:06, Dale Huckeby kirjutas:
Evidently once I've installed package A which requests X, sometimes
packages F, L, and T might subsequently get
On Sat, Jan 7, 2012 at 14:24, Wolfgang Bornath molc...@googlemail.com wrote:
2012/1/7 Sander Lepik sander.le...@eesti.ee:
07.01.2012 13:39, Wolfgang Bornath kirjutas:
Of course this is one way to find bugs in packages. But what about the
documented (in German) case where
- after fresh
Le 08/01/2012 16:59, Pascal Terjan a écrit :
On Sat, Jan 7, 2012 at 16:48, Thomas Spuhlertho...@btspuhler.com wrote:
On Friday, January 06, 2012 12:57:39 PM Sander Lepik wrote:
06.01.2012 21:06, Dale Huckeby kirjutas:
Evidently once I've installed package A which requests X, sometimes
On Sun, Jan 8, 2012 at 16:04, ptyxs pt...@free.fr wrote:
Le 08/01/2012 16:59, Pascal Terjan a écrit :
On Sat, Jan 7, 2012 at 16:48, Thomas Spuhlertho...@btspuhler.com wrote:
On Friday, January 06, 2012 12:57:39 PM Sander Lepik wrote:
06.01.2012 21:06, Dale Huckeby kirjutas:
Evidently
07.01.2012 01:09, Johnny A. Solbu kirjutas:
On Friday 06 January 2012 18:54, Balcaen John wrote:
I guess when you did encounter that you just remove task-kde from your system
I did not. I should have been more clearly with my example. :-)=
The packages in my example where all console program,
Le 06/01/2012 17:55, Colin Guthrie a écrit :
'Twas brillig, and Robert Fox at 06/01/12 10:16 did gyre and gimble:
After latest Cauldron updates, I got a real long list of suggested
orphans - but I believe some of these packages are needed (like hal or
basesystem-minimal) -
How do I clear out
Sander Lepik a écrit :
07.01.2012 01:09, Johnny A. Solbu kirjutas:
On Friday 06 January 2012 18:54, Balcaen John wrote:
I guess when you did encounter that you just remove task-kde from
your system
I did not. I should have been more clearly with my example. :-)=
The packages in my example
Le 07/01/2012 11:18, andre999 a écrit :
Sander Lepik a écrit :
07.01.2012 01:09, Johnny A. Solbu kirjutas:
On Friday 06 January 2012 18:54, Balcaen John wrote:
I guess when you did encounter that you just remove task-kde from
your system
I did not. I should have been more clearly with my
07.01.2012 12:18, andre999 kirjutas:
It is not exactly the same thing, but in more than one occasion when I installed packages
with similar functions at the same time, to compare them, say A, B, and C, and later
uninstalled B and C, I have found A to be declared an orphan. Only to find that it
2012/1/7 andre999 andre999...@laposte.net:
Sander Lepik a écrit :
07.01.2012 01:09, Johnny A. Solbu kirjutas:
On Friday 06 January 2012 18:54, Balcaen John wrote:
I guess when you did encounter that you just remove task-kde from your
system
I did not. I should have been more clearly with
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
2012/1/7 Thomas Backlund t...@mageia.org:
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
2012/1/7 Wolfgang Bornath molc...@googlemail.com:
Of course this is one way to find bugs in packages. But what about the
documented (in German) case where
Sorry, documented is not the correct word. I could not document it
with logs or namng of files. I only stated what I did and what it
07.01.2012 13:39, Wolfgang Bornath kirjutas:
Of course this is one way to find bugs in packages. But what about the
documented (in German) case where
- after fresh installation, reboot (ok) and updates right after
installation I was presented with a list of more than 100 orphans.
- I ran
On Saturday 07 January 2012 09:42, Sander Lepik wrote:
Give us command line example. Install something and remove it and then show
me what got
orphaned if it wasn't orphan before. What you claim here doesn't sound right
as i haven't
seen it myself.
I'll do that next time I come across
Sander Lepik a écrit :
07.01.2012 12:18, andre999 kirjutas:
It is not exactly the same thing, but in more than one occasion when
I installed packages with similar functions at the same time, to
compare them, say A, B, and C, and later uninstalled B and C, I have
found A to be declared an
2012/1/7 Sander Lepik sander.le...@eesti.ee:
07.01.2012 13:39, Wolfgang Bornath kirjutas:
Of course this is one way to find bugs in packages. But what about the
documented (in German) case where
- after fresh installation, reboot (ok) and updates right after
installation I was presented
07.01.2012 16:24, Wolfgang Bornath kirjutas:
Used the full DVD (32-bit) Mageia 2 Alpha 2
- minimal install with X
How? AFAIK this is not one of the default options.
--
Sander
2012/1/7 Sander Lepik sander.le...@eesti.ee:
07.01.2012 16:24, Wolfgang Bornath kirjutas:
Used the full DVD (32-bit) Mageia 2 Alpha 2
- minimal install with X
How? AFAIK this is not one of the default options.
It is.
1. Select Custom at the DE selection
2. Unmark all package groups
3. Up
07.01.2012 17:09, Wolfgang Bornath kirjutas:
2012/1/7 Sander Lepiksander.le...@eesti.ee:
07.01.2012 16:24, Wolfgang Bornath kirjutas:
Used the full DVD (32-bit) Mageia 2 Alpha 2
- minimal install with X
How? AFAIK this is not one of the default options.
It is.
1. Select Custom at the DE
On 07/01/12 15:30, Sander Lepik wrote:
07.01.2012 17:09, Wolfgang Bornath kirjutas:
2012/1/7 Sander Lepiksander.le...@eesti.ee:
07.01.2012 16:24, Wolfgang Bornath kirjutas:
Used the full DVD (32-bit) Mageia 2 Alpha 2
- minimal install with X
How? AFAIK this is not one of the default
On Friday, January 06, 2012 12:57:39 PM Sander Lepik wrote:
06.01.2012 21:06, Dale Huckeby kirjutas:
Evidently once I've installed package A which requests X, sometimes
packages F, L, and T might subsequently get installed which also need X
*and presumably would have requested it had it not
07.01.2012 17:09, Wolfgang Bornath skrev:
2012/1/7 Sander Lepiksander.le...@eesti.ee:
07.01.2012 16:24, Wolfgang Bornath kirjutas:
Used the full DVD (32-bit) Mageia 2 Alpha 2
- minimal install with X
How? AFAIK this is not one of the default options.
It is.
1. Select Custom at the DE
Op zaterdag 07 januari 2012 17:48:36 schreef Thomas Spuhler:
[...]
It seems to me, auto-orphans gives more headaches than benefits. Why are we
clinching to it?
because it works for me (and several others)
After latest Cauldron updates, I got a real long list of suggested
orphans - but I believe some of these packages are needed (like hal or
basesystem-minimal) -
How do I clear out the orphans - like reset the logic behind it so the
correct packages will be orphaned? Or is a fresh install in
I guess a lot of them are suggested by other packages, rather than required.
On Fri, 2012-01-06 at 12:32 +0200, Shlomi Fish wrote:
On Fri, 06 Jan 2012 11:16:52 +0100
Robert Fox l...@foxconsult.net wrote:
After latest Cauldron updates, I got a real long list of suggested
orphans - but I believe some of these packages are needed (like hal or
basesystem-minimal) -
On Fri, 06 Jan 2012 11:16:52 +0100
Robert Fox l...@foxconsult.net wrote:
After latest Cauldron updates, I got a real long list of suggested
orphans - but I believe some of these packages are needed (like hal or
basesystem-minimal) -
How do I clear out the orphans - like reset the logic
On Fri, 06 Jan 2012 11:43:21 +0100
Robert Fox l...@foxconsult.net wrote:
On Fri, 2012-01-06 at 12:32 +0200, Shlomi Fish wrote:
On Fri, 06 Jan 2012 11:16:52 +0100
Robert Fox l...@foxconsult.net wrote:
After latest Cauldron updates, I got a real long list of suggested
orphans - but I
On 6 January 2012 18:43, Robert Fox l...@foxconsult.net wrote:
On Fri, 2012-01-06 at 12:32 +0200, Shlomi Fish wrote:
On Fri, 06 Jan 2012 11:16:52 +0100
Robert Fox l...@foxconsult.net wrote:
After latest Cauldron updates, I got a real long list of suggested
orphans - but I believe some of
2012/1/6 Robert Fox l...@foxconsult.net:
After latest Cauldron updates, I got a real long list of suggested
orphans - but I believe some of these packages are needed (like hal or
basesystem-minimal) -
How do I clear out the orphans - like reset the logic behind it so the
correct packages
On Fri, 2012-01-06 at 12:27 +0100, Wolfgang Bornath wrote:
2012/1/6 Robert Fox l...@foxconsult.net:
After latest Cauldron updates, I got a real long list of suggested
orphans - but I believe some of these packages are needed (like hal or
basesystem-minimal) -
How do I clear out the
On Friday, January 06, 2012 05:16:59 AM Wolfgang Bornath wrote:
2012/1/6 Wolfgang Bornath molc...@googlemail.com:
2012/1/6 Thierry Vignaud thierry.vign...@gmail.com:
On 6 January 2012 12:27, Wolfgang Bornath molc...@googlemail.com wrote:
This is a well known issue.
To clear out the list
2012/1/6 Robert Fox l...@foxconsult.net:
After latest Cauldron updates, I got a real long list of suggested
orphans - but I believe some of these packages are needed (like hal or
basesystem-minimal) -
How do I clear out the orphans - like reset the logic behind it so the
correct packages
2012/1/6 Thierry Vignaud thierry.vign...@gmail.com:
On 6 January 2012 13:16, Wolfgang Bornath molc...@googlemail.com wrote:
This is just a bogus claim:
If some apps break after removing orphan packages, they'll break too
after manually removing such packages, meaning they lack some
On 6 January 2012 15:53, LinuxBSDos.com fi...@linuxbsdos.com wrote:
This is a well known issue.
To clear out the list you need a deep knowledge of the system to
determine which packages are really not needed anymore.
Lately this --auto-orphans line shreddered my whole system on a fresh
On 6 January 2012 16:13, Wolfgang Bornath molc...@googlemail.com wrote:
This is just a bogus claim:
If some apps break after removing orphan packages, they'll break too
after manually removing such packages, meaning they lack some
requires...
Yes, right, I'd not remove such packages manually
06.01.2012 12:16, Robert Fox skrev:
After latest Cauldron updates, I got a real long list of suggested
orphans - but I believe some of these packages are needed (like hal or
basesystem-minimal) -
How do I clear out the orphans - like reset the logic behind it so the
correct packages will be
Le 06/01/2012 16:13, Wolfgang Bornath a écrit :
Ah, I see your reasoning, of course, if the packager forgot to name
the requires then urpmi declares them as orphans. But then, to be
safe, you have to forget about auto-orphans altogether because you can
not be sure that all packagers did their
Am 06.01.2012 16:48, schrieb Guillaume Rousse:
Le 06/01/2012 16:13, Wolfgang Bornath a écrit :
Ah, I see your reasoning, of course, if the packager forgot to name
the requires then urpmi declares them as orphans. But then, to be
safe, you have to forget about auto-orphans altogether because
'Twas brillig, and Robert Fox at 06/01/12 10:16 did gyre and gimble:
After latest Cauldron updates, I got a real long list of suggested
orphans - but I believe some of these packages are needed (like hal or
basesystem-minimal) -
How do I clear out the orphans - like reset the logic behind it
On Friday 06 January 2012 16:13, Thierry Vignaud wrote:
The system has to be intelligent enough to know what is or is not an orphan.
It is.
We claim that it is not.
orphan packages are packages that were never directly requested/installed;
they're packages that got installed because they
06.01.2012 19:40, Johnny A. Solbu kirjutas:
On Friday 06 January 2012 16:13, Thierry Vignaud wrote:
The system has to be intelligent enough to know what is or is not an orphan.
It is.
We claim that it is not.
Well, the system is ok. Just some packages are probably bogus and don't require all
Am 06.01.2012 17:55, schrieb Colin Guthrie:
'Twas brillig, and Robert Fox at 06/01/12 10:16 did gyre and gimble:
After latest Cauldron updates, I got a real long list of suggested
orphans - but I believe some of these packages are needed (like hal or
basesystem-minimal) -
How do I clear out
On 6 January 2012 18:54, Balcaen John mik...@mageia.org wrote:
The bug is not in urpmi but in the installer phase here.
No.
(Anyway the installer uses urpmi)
I guess when you did encounter that you just remove task-kde from your system,
this one is pulling all kde deps, so when removed it's
06.01.2012 21:06, Dale Huckeby kirjutas:
Evidently once I've installed package A which requests X, sometimes packages
F, L, and T might subsequently get installed which also need X *and presumably
would have requested it had it not already been installed*. But when I
uninstall
A it orphans X
On Friday 06 January 2012 18:54, Balcaen John wrote:
I guess when you did encounter that you just remove task-kde from your system
I did not. I should have been more clearly with my example. :-)=
The packages in my example where all console program, that I installed and
removed using urpm[ie].
Op vrijdag 06 januari 2012 13:02:26 schreef Thierry Vignaud:
On 6 January 2012 12:27, Wolfgang Bornath molc...@googlemail.com wrote:
This is a well known issue.
To clear out the list you need a deep knowledge of the system to
determine which packages are really not needed anymore.
51 matches
Mail list logo