Anne Nicolas launched a discussion about display manager.
From my part, I try to eliminate good hundred of unwanted packages
during a reduced installation (personal desk, without any group of packages,
but with X server and with urpmi).
Further to Thierry Vignaud's indications and Michael
On Mon, Feb 20, 2012 at 11:18 AM, Funda Wang fundaw...@gmail.com wrote:
I guess it is another problem, which has no relationship with lesstif or gcc.
a fixed xpdf is on the BS now
Le 20/02/2012 11:31, Païou a écrit :
Is it necessary to keep xguest?
---
I would say that yes, but on the condition of not creating unwanted effects.
No. Configuring a user computer should be left to end-user, not to
packagers providing 'just click here' blackbox
Le 20/02/2012 11:31, Païou a écrit :
Is it necessary to keep xguest?
---
I would say that yes, but on the condition of not creating unwanted
effects.
No. Configuring a user computer should be left to end-user, not to
packagers providing 'just click here' blackbox
Le dimanche 19 février 2012 à 12:19 +, Païou a écrit :
Oliver Burger oliver.bgr@... writes:
I don't see the reason for this answer.
Michael is just trying to make sure, we don't have a unmaintained major DE.
Now, some maybe a bit harsh words on the developer mailing list - this
is
Sorry, but I forgot to specify that the details of the tries
can be consulted there:
https://bugs.mageia.org/show_bug.cgi?Id=3060 attachment 1603
On Sun, Feb 19, 2012 at 08:58:21AM -0600, Richard Couture wrote:
When trying to install libavformat53-0.10-1.mga2.i586.rpm it says:
libavfilter.so.2 is needed by libavformat53-0.10-1.mga2.i586
when I try to install libavfilter it says:
libavformat.so.53 is needed by
2012/2/20 Michael Scherer m...@zarb.org:
Le dimanche 19 février 2012 à 12:19 +, Païou a écrit :
Oliver Burger oliver.bgr@... writes:
I don't see the reason for this answer.
Michael is just trying to make sure, we don't have a unmaintained major DE.
Now, some maybe a bit harsh words on
D.Morgan wrote:
On Mon, Feb 20, 2012 at 11:18 AM, Funda Wang fundaw...@gmail.com wrote:
I guess it is another problem, which has no relationship with lesstif or gcc.
a fixed xpdf is on the BS now
Thank you D Morgan, Funda Wang, and everyone else that helped along the way.
Sometimes it
Florian Hubold wrote:
Am 19.02.2012 15:59, schrieb David Walser:
Pascal Terjan wrote:
I was looking at that package, which is a collection of drivers for
some printers, not updated for years
It is one of the two packages requiring automake1.4, because of the
includeddrv_z42
Looking on
On 18/02/12 11:55, Michael Scherer wrote:
Le samedi 18 février 2012 à 10:33 +0100, Olivier Thauvin a écrit :
* Michael Scherer (m...@zarb.org) wrote:
Le vendredi 17 février 2012 à 19:18 +0100, Claire Revillet a écrit :
Hi,
As a second point : there is still no xfce-* maintainer and as many
On Mon, Feb 20, 2012 at 11:59:02AM +0100, Guillaume Rousse wrote:
No. Configuring a user computer should be left to end-user, not to
packagers providing 'just click here' blackbox solutions.
Documenting how to achieve the same result manually, and outlining
consequences, would be a far better
Le 20/02/2012 15:45, Olav Vitters a écrit :
On Mon, Feb 20, 2012 at 11:59:02AM +0100, Guillaume Rousse wrote:
No. Configuring a user computer should be left to end-user, not to
packagers providing 'just click here' blackbox solutions.
Documenting how to achieve the same result manually, and
On Mon, 2012-02-20 at 11:59 +0100, Guillaume Rousse wrote:
No. Configuring a user computer should be left to end-user, not to
packagers providing 'just click here' blackbox solutions.
One of the reaons I switched, years ago, away from Debian to Mandrake
Linux, was exactly this: debian packages
2012/2/20 Guillaume Rousse guillomovi...@gmail.com:
Le 20/02/2012 15:45, Olav Vitters a écrit :
On Mon, Feb 20, 2012 at 11:59:02AM +0100, Guillaume Rousse wrote:
No. Configuring a user computer should be left to end-user, not to
packagers providing 'just click here' blackbox solutions.
On Mon, Feb 20, 2012 at 04:01:46PM +0100, Guillaume Rousse wrote:
In order to have a 'guest user', which usually means a passwordless
user, you don't need any additional software, you just need to
configure your computer. Hence my point than using a package to
automatically performing those
2012/2/20 Olav Vitters o...@vitters.nl:
[...].
I agree that you don't want a package. But no problem with a checkbox
somewhere which does the right thing (configuring, etc). I think the
System Settings in GNOME allows you to easily setup a new account, so
IMO, functionality is not needed..
In
2012/2/20 Olav Vitters o...@vitters.nl:
On Mon, Feb 20, 2012 at 04:01:46PM +0100, Guillaume Rousse wrote:
In order to have a 'guest user', which usually means a passwordless
user, you don't need any additional software, you just need to
configure your computer. Hence my point than using a
2012/2/20 John Balcaen mik...@mageia.org:
2012/2/20 Olav Vitters o...@vitters.nl:
[...].
I agree that you don't want a package. But no problem with a checkbox
somewhere which does the right thing (configuring, etc). I think the
System Settings in GNOME allows you to easily setup a new
Olav Vitters skrev 20.2.2012 17:30:
On Mon, Feb 20, 2012 at 04:01:46PM +0100, Guillaume Rousse wrote:
In order to have a 'guest user', which usually means a passwordless
user, you don't need any additional software, you just need to
configure your computer. Hence my point than using a package
On Mon, Feb 20, 2012 at 05:03:29PM +0100, Wolfgang Bornath wrote:
BTW: I often expressed my annoyance to see system wide settings being
handled in a DE dependent tool (like this user account setting in
Gnome) while there is a tool with the same function/task in MCC. A DE
System Settings should
2012/2/20 Olav Vitters o...@vitters.nl:
On Mon, Feb 20, 2012 at 05:03:29PM +0100, Wolfgang Bornath wrote:
BTW: I often expressed my annoyance to see system wide settings being
handled in a DE dependent tool (like this user account setting in
Gnome) while there is a tool with the same
See https://bugs.mageia.org/show_bug.cgi?id=3358#c3
Anyone care to comment?
L.G.
Hello here,
Saturday I was connected to internet using wifi when I decided to update
my cauldron, so I typed urpmi --auto-update
During the update I got disconnected from wifi and I am unable to
connect to any wifi anymore (wifi I am used: at home, my android phone,
etc.).
Does anyone have
Le lundi 20 février 2012 21:01:07, Olivier Thauvin a écrit :
Hello here,
During the update I got disconnected from wifi and I am unable to
connect to any wifi anymore (wifi I am used: at home, my android phone,
etc.).
Does anyone have notice the same things ?
I had the same problem
* zezinho (lists.jjo...@free.fr) wrote:
Le lundi 20 février 2012 21:01:07, Olivier Thauvin a écrit :
Hello here,
During the update I got disconnected from wifi and I am unable to
connect to any wifi anymore (wifi I am used: at home, my android phone,
etc.).
Does anyone have notice
On Mon, Feb 20, 2012 at 05:49:49PM +0100, Wolfgang Bornath wrote:
2012/2/20 Olav Vitters o...@vitters.nl:
I have the GNOME view on the world: why have distribution specific tools
if you can configure it from GNOME itself. That said, GNOME usually
focusses on the very basic options.
Oh
'Twas brillig, and Johnny A. Solbu at 19/02/12 02:13 did gyre and gimble:
On Thursday 16 February 2012 15:51, Colin Guthrie wrote:
Can someone who can still boot (i.e. into older kernel) post a log of
the dracut command and the output from lsinitrd on the resulting image?
* Olivier Thauvin (nanar...@nanardon.zarb.org) wrote:
* zezinho (lists.jjo...@free.fr) wrote:
Le lundi 20 février 2012 21:01:07, Olivier Thauvin a écrit :
Hello here,
During the update I got disconnected from wifi and I am unable to
connect to any wifi anymore (wifi I am used: at home,
On Monday 20 February 2012 22:45, Colin Guthrie wrote:
Can you reliably reproduce this broken initrd (i.e. get the same results
from your lsinitrd-broken.txt?
And just how do I do that?
I got this problem simply by running urpmi --auto-update and rebooted.
I've had several reports about this
Hello!
I can see in some packages that hicolor-icon-theme is required,
build-required, suggested or even Required(post). This is due to the
files in the hicolor directory.
What is the right policy of using this package? Is it really needed?
Some examples below:
Hello,
I want to propose an idea for icewm packaging:
Currently, the icewm source package builds icewm-light, icewm,
icewm-gnome. But the themes and all locale files are included in the
icewm package. Even though icewm is already small, I still think it
can be better organized.
How about:
-
On Tuesday 21 Feb 2012 01:53:21 You-Cheng Hsieh wrote:
Hello,
I want to propose an idea for icewm packaging:
Currently, the icewm source package builds icewm-light, icewm,
icewm-gnome. But the themes and all locale files are included in
the
icewm package. Even though icewm is already
On 21.02.2012 02:53, You-Cheng Hsieh wrote:
Hello,
Hi!
How about:
- Pack all themes in icewm into one icewm-themes and pack all
locales into one icewm-i18n package.
OR
- Pack each theme as a single package icewm-theme-%themename, and
have a icewm-theme to install all themes.
I just did it
21.02.2012 03:53, You-Cheng Hsieh kirjoitti:
Hello,
I want to propose an idea for icewm packaging:
Currently, the icewm source package builds icewm-light, icewm,
icewm-gnome. But the themes and all locale files are included in the
icewm package. Even though icewm is already small, I still
35 matches
Mail list logo
