Re: [Mageia-dev] [changelog] [RPM] cauldron core/release kdeutils4-4.7.90-1.mga2

[Balcaen John]

Le dimanche 18 décembre 2011 04:08:57 Balcaen John a écrit :
> Le dimanche 18 décembre 2011 06:54:09 Mageia Team a écrit :
> > Name: kdeutils4Relocations: (not relocatable)
> > Version : 4.7.90Vendor: Mageia.Org
> > Release : 1.mga2Build Date: Sun Dec 18
> > 06:52:19
> > 2011 Install Date: (not installed)   Build Host: ecosse
> > Group   : Graphical desktop/KDE Source RPM: (none)
> > Size: 2915 License: GPLv2 LGPLv2 GPLD
> > Signature   : (none)
> > Packager: Mageia Team 
> > URL : http://utils.kde.org/
> > Summary : Various desktop utilities for KDE
> > Description :
> > The KDE Utilities are a compilation of various desktop utilities.
> > 
> > fwang  4.7.90-1.mga2:
> > + Revision: 183599
> > - add empty sha1.lst
> > - turned to meta package
> 
> I still thing it's not useless to carry thoses empty package just to have a
> « suggests ».
I mean it's useless of course :p

-- 
Balcaen John
Jabber-id: mik...@jabber.littleboboy.net

Re: [Mageia-dev] [changelog] [RPM] cauldron core/release kdeutils4-4.7.90-1.mga2

[Balcaen John]

Le dimanche 18 décembre 2011 06:54:09 Mageia Team a écrit :
> Name: kdeutils4Relocations: (not relocatable)
> Version : 4.7.90Vendor: Mageia.Org
> Release : 1.mga2Build Date: Sun Dec 18 06:52:19
> 2011 Install Date: (not installed)   Build Host: ecosse
> Group   : Graphical desktop/KDE Source RPM: (none)
> Size: 2915 License: GPLv2 LGPLv2 GPLD
> Signature   : (none)
> Packager: Mageia Team 
> URL : http://utils.kde.org/
> Summary : Various desktop utilities for KDE
> Description :
> The KDE Utilities are a compilation of various desktop utilities.
> 
> fwang  4.7.90-1.mga2:
> + Revision: 183599
> - add empty sha1.lst
> - turned to meta package
I still thing it's not useless to carry thoses empty package just to have a « 
suggests ».
The fix should be in task-kde.

Regards,
-- 
Balcaen John
Jabber-id: mik...@jabber.littleboboy.net

Re: [Mageia-dev] Call for translators

[andre999]

Oliver Burger a écrit :

Hi,

these days Damien contacted me about the bootloader translation.
The problem is, we do have quite some languages, that don't have i18n teams in
Mageia.
So there are quite some languages where the bootloader still contains strings
about Mandriva.

Now there are two solutions.
Either we do find translators of those languages, who fix those translations
(and while they are on it, join i18n and fix/complete all other translations as
well :D)
or we just delete those translated strings. People in those languages will
then see English strings instead but at least no Mandriva strings any more.
   


A third option could be that some enthusiastic documenters/translators 
just change Mandriva to Mageia in all the places where the English has 
Mageia.  (Where translators for the language in question haven't responded.)

If you are interested in helping us, have a look at
https://wiki.mageia.org/en/Internationalisation_Team_(i18n)
and do contact me.

Oliver
   


--
André

Re: [Mageia-dev] ANN: X11 now starts on tty1

[David Walser]

Anssi Hannula wrote:
> On 16.12.2011 20:16, Colin Guthrie wrote:
>> Hi
>> 
>> Just in case you didn't notice, X11 now starts on tty1 by default.
>> 
>> So if you want a text login shell, make sure you go to tty2!
>> 
>> I've not actually updated it for sysvinit now I think about it, so I'll
>> have to update the default inittab, but the principle is the same. We
>> want X there, not a login.
> 
> I wonder why that is needed...
> 
> If it is to prevent flickering when switching tty1->tty7, can't we just
> e.g. make the kernel use tty7 by default if needed?

+1

Also, what happens when you boot to multi-user.target instead of 
graphical.target?

Re: [Mageia-dev] mentors + apprentices

[Pierre-Malo Denielou]

On 18/12/11 02:40, You-Cheng Hsieh wrote:
> 2011/12/15 andre999 :
>> You-Cheng Hsieh a écrit :
>>> I'm not sure if I should post a new message or reply this thread, but
>>> I'm looking for a mentor.
>>
>> Yes, posting to this thread is expected :)
> 
> Hi,
> I've talked with Funda Wang and he agreed to be my mentor. Since we
> both live in UTC+8 timezone and can communicate with English and
> Chinese, there shouldn't be much problem.
> 
> Please help update the mentoring table in wiki. :)

Great. Welcome to Mageia!

Don't hesitate to come to #mageia-mentoring on IRC to chat with other
apprentices and mentors.

Cheers,
-- 
Malo
http://www.doc.ic.ac.uk/~malo/

Re: [Mageia-dev] Issues with dracut

[Colin Guthrie]

'Twas brillig, and David W. Hodgins at 18/12/11 00:04 did gyre and gimble:
> On Sat, 17 Dec 2011 15:21:14 -0500, Colin Guthrie
>  wrote:
> 
>> Dracut should install all dynamic libs needed by apps. Which app needs
>> this library specifically?
> 
> When I tried to boot after running dracut with the default config, I
> was dropped to a shell, with the non-lvm root mounted.
> 
> I then tried running "/sbin/lvm vgchange -a y --ignorelockingfailure",
> and it failed due to the missing libncursesw.so.5 module.
> 
> Now that I think about it, a bit more, I think I had already been
> chrooted into the root, so since /usr hadn't been mounted, of course
> the module could not be accessed.  Something else must have gone wrong
> before the chroot, that I didn't see.

Ahhh interesting. Could have been a filesystem check error. What
filesystem do you have on your /usr ? (obviously on top of the lvm layer).

Did typing "mount /usr" just work? After that (and typing exit) does
everything work as expected?

> Do you have /usr on a logical volume?

In my test VM yes, I had / on ext4 and /usr on LVM also with ext4.

> I've figured out now, that /lib/dracut/hooks/pre-pivot/50mount-usr.sh is
> failing, as lvm has not yet been activated.

That's strange, as lvm should be activated by then. Was the lvm module
included in your ramfs? The latest version should detect LVM on the /usr
partition, but it's perhaps not full proof (I only tested it in my test
vm when I wrote it).

> Later, I'm dropped to a shell, after the switch to the new root, and
> since /usr hasn't been mounted, any commands that try to load
> /usr/lib/libncursesw.so.5 such as lvm, grep, or less, will fail.
> 
> When I've copied /usr/lib/libncursesw.so.5* to /lib and run ldconfig,
> it still fails in 50mount-usr, but succeeds later, after the root
> switch.
> 
> The dm-mod module loading, and the "lvm vgchange -ay --sysinit" command
> should be run before looking for the root file system, as it too could be
> on a logical volume.

They all should be (and are for me). I suspect the missing link is that
the lvm module is not being included in your ramfs... If we can work out
why it would be great.

The shell script you'll need to tweak is
/usr/lib/dracut/modules.d/90lvm/module-setup.sh.

The code is fairly easy to follow and you can probably hack out the bits
to make it a simple runable script to see if you can work out why lvm is
not being included.

Col

-- 

Colin Guthrie
colin(at)mageia.org
http://colin.guthr.ie/

Day Job:
  Tribalogic Limited http://www.tribalogic.net/
Open Source:
  Mageia Contributor http://www.mageia.org/
  PulseAudio Hacker http://www.pulseaudio.org/
  Trac Hacker http://trac.edgewall.org/

Re: [Mageia-dev] mariadb

[David W. Hodgins]

On Sat, 17 Dec 2011 19:12:21 -0500, Maarten Vanraes  wrote:


oh and were any mysql libraries still loaded? ie: programs linked to mysql,
after upgrade?


See https://bugs.mageia.org/show_bug.cgi?id=3804

Regards, Dave Hodgins

Re: [Mageia-dev] mentors + apprentices

[You-Cheng Hsieh]

2011/12/15 andre999 :
> You-Cheng Hsieh a écrit :
>> I'm not sure if I should post a new message or reply this thread, but
>> I'm looking for a mentor.
>
> Yes, posting to this thread is expected :)

Hi,
I've talked with Funda Wang and he agreed to be my mentor. Since we
both live in UTC+8 timezone and can communicate with English and
Chinese, there shouldn't be much problem.

Please help update the mentoring table in wiki. :)

Thanks.

Re: [Mageia-dev] mariadb

[David W. Hodgins]

On Sat, 17 Dec 2011 19:12:21 -0500, Maarten Vanraes  wrote:


that is a lot of memory, do you have any mysqld logs? and also, for the
record, you have mariadb installed?


This is from akonadi under kde4.  I'll look to see if I can find any logs
from that.


can you check if you have the latest, if there is still a part of mysql
installed?


Yes, it's mariadb-5.5.18-0.bzr3169.20111216.3.mga2.


what kind of databases do you have, and which ones were created by mariadb?
what kind of load do you have? what app is querying mariadb? do you have a
slow-queries mysql log file?
how big are the recent mysql-binlogs?

perhaps you can make a bug report, this would be easier to follow up on.



oh and were any mysql libraries still loaded? ie: programs linked to mysql,
after upgrade?


I'll open a bug report, and attach any log files I can find.  As I only have
a few seconds after kde starts, before the system starts swapping everything
out, I can really only get debug output by putting commands in autostart, or
by looking at files from my mageia 1 install.

Regards, Dave Hodgins

Re: [Mageia-dev] Issues with dracut

[David W. Hodgins]

On Sat, 17 Dec 2011 15:21:14 -0500, Colin Guthrie  wrote:


Dracut should install all dynamic libs needed by apps. Which app needs
this library specifically?


Do you have /usr on a logical volume?

I've figured out now, that /lib/dracut/hooks/pre-pivot/50mount-usr.sh is
failing, as lvm has not yet been activated.

Later, I'm dropped to a shell, after the switch to the new root, and
since /usr hasn't been mounted, any commands that try to load
/usr/lib/libncursesw.so.5 such as lvm, grep, or less, will fail.

When I've copied /usr/lib/libncursesw.so.5* to /lib and run ldconfig,
it still fails in 50mount-usr, but succeeds later, after the root
switch.

The dm-mod module loading, and the "lvm vgchange -ay --sysinit" command
should be run before looking for the root file system, as it too could be
on a logical volume.

Regards, Dave Hodgins

Re: [Mageia-dev] Upgrade udev 175

[Colin Guthrie]

'Twas brillig, and Colin Guthrie at 18/12/11 01:23 did gyre and gimble:
> 'Twas brillig, and Colin Guthrie at 17/12/11 23:10 did gyre and gimble:
>> On 17 Dec 2011, at 23:00, "D.Morgan"  wrote:
>>> /sbin/usb_id is needed by mouse.pm to generate
>>> /dev/input/by-id/xxx seems we need to migrate using udevadm now.
> 
>> Hmm. Not at my computer but I thought it still existed but under a
>> different path. Maybe not, but I'll check when I get back later.
> 
> Yup, it's still there in /lib/udev/usb_id.

Erm, forget me, I forgot I'd reverted to test something :s It's gone.

> Perhaps the udevadm way is better tho'. I'll try and review.

Doing this would get the correct device path:

udevadm info --query=symlink
--path=/devices/pci:00/:00:1d.1/usb2/2-1/2-1:1.0/input/input9/mouse1
| cut -d' ' -f1
input/by-id/usb-Microsoft_Microsoft_Optical_Mouse_with_Tilt_Wheel-mouse

Col

-- 

Colin Guthrie
colin(at)mageia.org
http://colin.guthr.ie/

Day Job:
  Tribalogic Limited http://www.tribalogic.net/
Open Source:
  Mageia Contributor http://www.mageia.org/
  PulseAudio Hacker http://www.pulseaudio.org/
  Trac Hacker http://trac.edgewall.org/

Re: [Mageia-dev] Adding additional provides to php database modules

[Thomas Spuhler]

On Saturday, December 17, 2011 03:24:16 PM Oliver Burger wrote:
> Hi,
> 
> I'm maintaining mediawiki and drupal.
> 
> Both packages require a php database module but both can work with mysql,
> postgresql and sqlite.
> 
> Now the mediawiki package does simply require both php-mysql and php-pgsql,
> which is bad since it leads to installing unneeded database libraries in
> the system.
> Drupal has three sub packages which doe require the respective php database
> module and one of the three is required by drupal itself, which is some
> kind of ugly workarround.
> 
> I think it would be a cleaner solution to have php-X providing something
> common and php-pdo_X providing something common (X being one of mysql,
> pgsql or sqlite).
> 
> What do you think?
> I tried contacting the php maintainer by mail, but he didn't answer me.
> 
> Oliver
Because he is trying to get php-gkt2 built :)
-- 
Best regards
Thomas Spuhler

Re: [Mageia-dev] Umaintained packages?

[Josh King]

On 12/17/2011 07:23 PM, Malo wrote:

On 18/12/11 01:10, Josh King wrote:

Hi,

I'm looking to potentially contribute to Mageia and would like to get some
practice in packaging. I have done extensive deb packaging/maintaining but am
very behind on RPM's. I was digging around looking for someplace I could find a
list of unmaintained or orphan packages that I could maybe help with and learn
from at the same time. Is there such a list someplace? If not, any pointers
towards where to start finding what needs a potential maintainer would be
helpful. I just figure maybe I could knock out two birds with the proverbial one
stone.

Thanks,
Josh


Hi Josh,

Your help would be very welcome.
There is a list of package that have no maintainer at:
http://pkgsubmit.mageia.org/data/unmaintained.txt

If you wish to become a packager, we have a very successful apprenticeship
program: just follow the instructions at
http://wiki.mageia.org/en/Becoming_a_Mageia_Packager

and come join us at #mageia-mentoring on freenode.

Cheers,


Awesome, thanks! Look for nick dotmil on freenode soon.

Re: [Mageia-dev] Umaintained packages?

[Malo]

On 18/12/11 01:10, Josh King wrote:
> Hi,
> 
> I'm looking to potentially contribute to Mageia and would like to get some
> practice in packaging. I have done extensive deb packaging/maintaining but am
> very behind on RPM's. I was digging around looking for someplace I could find 
> a
> list of unmaintained or orphan packages that I could maybe help with and learn
> from at the same time. Is there such a list someplace? If not, any pointers
> towards where to start finding what needs a potential maintainer would be
> helpful. I just figure maybe I could knock out two birds with the proverbial 
> one
> stone.
> 
> Thanks,
> Josh

Hi Josh,

Your help would be very welcome.
There is a list of package that have no maintainer at:
http://pkgsubmit.mageia.org/data/unmaintained.txt

If you wish to become a packager, we have a very successful apprenticeship
program: just follow the instructions at
http://wiki.mageia.org/en/Becoming_a_Mageia_Packager

and come join us at #mageia-mentoring on freenode.

Cheers,
-- 
Malo

Re: [Mageia-dev] Upgrade udev 175

[Colin Guthrie]

'Twas brillig, and Colin Guthrie at 17/12/11 23:10 did gyre and gimble:
> On 17 Dec 2011, at 23:00, "D.Morgan"  wrote:
>> /sbin/usb_id is needed by mouse.pm to generate
>> /dev/input/by-id/xxx seems we need to migrate using udevadm now.

> Hmm. Not at my computer but I thought it still existed but under a
> different path. Maybe not, but I'll check when I get back later.

Yup, it's still there in /lib/udev/usb_id.

Perhaps the udevadm way is better tho'. I'll try and review.

Col

-- 

Colin Guthrie
colin(at)mageia.org
http://colin.guthr.ie/

Day Job:
  Tribalogic Limited http://www.tribalogic.net/
Open Source:
  Mageia Contributor http://www.mageia.org/
  PulseAudio Hacker http://www.pulseaudio.org/
  Trac Hacker http://trac.edgewall.org/

[Mageia-dev] Umaintained packages?

[Josh King]

Hi,

I'm looking to potentially contribute to Mageia and would like to get 
some practice in packaging. I have done extensive deb 
packaging/maintaining but am very behind on RPM's. I was digging around 
looking for someplace I could find a list of unmaintained or orphan 
packages that I could maybe help with and learn from at the same time. 
Is there such a list someplace? If not, any pointers towards where to 
start finding what needs a potential maintainer would be helpful. I just 
figure maybe I could knock out two birds with the proverbial one stone.


Thanks,
Josh

Re: [Mageia-dev] mariadb

[Maarten Vanraes]

Op zondag 18 december 2011 01:06:19 schreef Maarten Vanraes:
> Op zondag 18 december 2011 00:36:36 schreef David W. Hodgins:
> > On Sat, 17 Dec 2011 11:10:29 -0500, Maarten Vanraes  
wrote:
> > > I mentioned that this library should be versioned, and that it's not at
> > > this time, he agreed, and said that since it's ABI compatible with
> > > mysqlclient, that he should not use 0 major, but the 18 major (same as
> > > mysqlclient)
> > > 
> > > the code is still 100% exactly the same, it just went from unversioned
> > > in upstream to versioned.
> > > 
> > > since we had versioned manually mysqld to major 0, i provided the
> > > compatibility symlinks for it.
> > 
> > I've now figured out why my cauldron install is locking up.
> > 
> > I managed to get htop running before it locked.  It showed swap usage
> > climbing.  I got it to sort by vmsize.  It showed mysqldb using over
> > 2.5GB MV, and 1.5GB ram, on my 2GB ram system.
> > 
> > Regards, Dave Hodgins
> 
> that is a lot of memory, do you have any mysqld logs? and also, for the
> record, you have mariadb installed?
> 
> can you check if you have the latest, if there is still a part of mysql
> installed?
> 
> what kind of databases do you have, and which ones were created by mariadb?
> what kind of load do you have? what app is querying mariadb? do you have a
> slow-queries mysql log file?
> 
> how big are the recent mysql-binlogs?
> 
> perhaps you can make a bug report, this would be easier to follow up on.

oh and were any mysql libraries still loaded? ie: programs linked to mysql, 
after upgrade?

Re: [Mageia-dev] mariadb

[Maarten Vanraes]

Op zondag 18 december 2011 00:36:36 schreef David W. Hodgins:
> On Sat, 17 Dec 2011 11:10:29 -0500, Maarten Vanraes  wrote:
> > I mentioned that this library should be versioned, and that it's not at
> > this time, he agreed, and said that since it's ABI compatible with
> > mysqlclient, that he should not use 0 major, but the 18 major (same as
> > mysqlclient)
> > 
> > the code is still 100% exactly the same, it just went from unversioned in
> > upstream to versioned.
> > 
> > since we had versioned manually mysqld to major 0, i provided the
> > compatibility symlinks for it.
> 
> I've now figured out why my cauldron install is locking up.
> 
> I managed to get htop running before it locked.  It showed swap usage
> climbing.  I got it to sort by vmsize.  It showed mysqldb using over
> 2.5GB MV, and 1.5GB ram, on my 2GB ram system.
> 
> Regards, Dave Hodgins

and also output of "show variables;" query.

Re: [Mageia-dev] mariadb

[Maarten Vanraes]

Op zondag 18 december 2011 00:36:36 schreef David W. Hodgins:
> On Sat, 17 Dec 2011 11:10:29 -0500, Maarten Vanraes  wrote:
> > I mentioned that this library should be versioned, and that it's not at
> > this time, he agreed, and said that since it's ABI compatible with
> > mysqlclient, that he should not use 0 major, but the 18 major (same as
> > mysqlclient)
> > 
> > the code is still 100% exactly the same, it just went from unversioned in
> > upstream to versioned.
> > 
> > since we had versioned manually mysqld to major 0, i provided the
> > compatibility symlinks for it.
> 
> I've now figured out why my cauldron install is locking up.
> 
> I managed to get htop running before it locked.  It showed swap usage
> climbing.  I got it to sort by vmsize.  It showed mysqldb using over
> 2.5GB MV, and 1.5GB ram, on my 2GB ram system.
> 
> Regards, Dave Hodgins

that is a lot of memory, do you have any mysqld logs? and also, for the 
record, you have mariadb installed?

can you check if you have the latest, if there is still a part of mysql 
installed?

what kind of databases do you have, and which ones were created by mariadb? 
what kind of load do you have? what app is querying mariadb? do you have a 
slow-queries mysql log file?

how big are the recent mysql-binlogs?

perhaps you can make a bug report, this would be easier to follow up on.

Re: [Mageia-dev] Issues with dracut

[David W. Hodgins]

On Sat, 17 Dec 2011 15:21:14 -0500, Colin Guthrie  wrote:


Dracut should install all dynamic libs needed by apps. Which app needs
this library specifically?


When I tried to boot after running dracut with the default config, I
was dropped to a shell, with the non-lvm root mounted.

I then tried running "/sbin/lvm vgchange -a y --ignorelockingfailure",
and it failed due to the missing libncursesw.so.5 module.

Now that I think about it, a bit more, I think I had already been
chrooted into the root, so since /usr hadn't been mounted, of course
the module could not be accessed.  Something else must have gone wrong
before the chroot, that I didn't see.


So I've got the necessary lib... I wonder if this is a side effect of me
having lib64ncursesw-devel-5.9-2.mga2 installed (i.e. the dev package)?
Perhaps it's someone the key to including the right lib? Perhaps you can
test by installing the 32 bit devel package and seeing if the lib is
then included automatically?


I'll test that, and report back.

Regards, Dave Hodgins

Re: [Mageia-dev] mariadb

[David W. Hodgins]

On Sat, 17 Dec 2011 11:10:29 -0500, Maarten Vanraes  wrote:


I mentioned that this library should be versioned, and that it's not at this
time, he agreed, and said that since it's ABI compatible with mysqlclient,
that he should not use 0 major, but the 18 major (same as mysqlclient)

the code is still 100% exactly the same, it just went from unversioned in
upstream to versioned.

since we had versioned manually mysqld to major 0, i provided the
compatibility symlinks for it.


I've now figured out why my cauldron install is locking up.

I managed to get htop running before it locked.  It showed swap usage
climbing.  I got it to sort by vmsize.  It showed mysqldb using over
2.5GB MV, and 1.5GB ram, on my 2GB ram system.

Regards, Dave Hodgins

Re: [Mageia-dev] [changelog] [RPM] cauldron core/release oxygen-icon-theme-4.7.90-1.mga2

[Thierry Vignaud]

On 18 December 2011 00:10, Mageia Team  wrote:
> mikala  1:4.7.90-1.mga2:
> + Revision: 182202
> - Update tarball to KDE SC 4.7.90
> - use kde4_macros

BTW, if you could not fill the building queue with too many packages
so that other can have a reasonable build time...

Think about too many buffered packets in a router that
kills latency w/o improving the bandwith for nobody...

Re: [Mageia-dev] Upgrade udev 175

[Thierry Vignaud]

On 18 December 2011 00:08, Thierry Vignaud  wrote:
>>> Does anyone know what needs to be done to port drakx?
>>>
>>> I'm running the newer udev without any problems here.
>>
>> Running yes but this will break the installer.
>>
>> /sbin/usb_id is needed by mouse.pm to generate /dev/input/by-id/xxx
>> seems we need to migrate using udevadm now.
>
> See https://bugs.mageia.org/show_bug.cgi?id=3654#c1, still waiting for your
> input.
> Colin, can you test the suggested change?

And BTW please upload udev-175 in core/updates_testing so that
we can test w/o everyone having to locally build newer udev after
rediffing patches

Re: [Mageia-dev] Upgrade udev 175

[Thierry Vignaud]

On 18 December 2011 00:00, D.Morgan  wrote:
>> 178334    dmorgan # /!\ Do not update to version 175, drakx needs to be
>> ported before
>>
>> Does anyone know what needs to be done to port drakx?
>>
>> I'm running the newer udev without any problems here.
>
> Running yes but this will break the installer.
>
> /sbin/usb_id is needed by mouse.pm to generate /dev/input/by-id/xxx
> seems we need to migrate using udevadm now.

See https://bugs.mageia.org/show_bug.cgi?id=3654#c1, still waiting for your
input.
Colin, can you test the suggested change?

Re: [Mageia-dev] Upgrade udev 175

[D.Morgan]

On Sat, Dec 17, 2011 at 9:11 PM, Colin Guthrie  wrote:
> Hi,
>
> This comment is in the udev spec:
>
> 178334    dmorgan # /!\ Do not update to version 175, drakx needs to be
> ported before
>
>
> Does anyone know what needs to be done to port drakx?
>
> I'm running the newer udev without any problems here.

Running yes but this will break the installer.

/sbin/usb_id is needed by mouse.pm to generate /dev/input/by-id/xxx
seems we need to migrate using udevadm now.

[Mageia-dev] Call for translators

[Oliver Burger]

Hi,

these days Damien contacted me about the bootloader translation.
The problem is, we do have quite some languages, that don't have i18n teams in 
Mageia.
So there are quite some languages where the bootloader still contains strings 
about Mandriva.

Now there are two solutions.
Either we do find translators of those languages, who fix those translations 
(and while they are on it, join i18n and fix/complete all other translations as 
well :D)
or we just delete those translated strings. People in those languages will 
then see English strings instead but at least no Mandriva strings any more.

If you are interested in helping us, have a look at 
https://wiki.mageia.org/en/Internationalisation_Team_(i18n)
and do contact me.

Oliver

[Mageia-dev] Adding additional provides to php database modules

[Oliver Burger]

Hi,

I'm maintaining mediawiki and drupal.

Both packages require a php database module but both can work with mysql, 
postgresql and sqlite.

Now the mediawiki package does simply require both php-mysql and php-pgsql, 
which is bad since it leads to installing unneeded database libraries in the 
system.
Drupal has three sub packages which doe require the respective php database 
module and one of the three is required by drupal itself, which is some kind 
of ugly workarround.

I think it would be a cleaner solution to have php-X providing something 
common and php-pdo_X providing something common (X being one of mysql, pgsql 
or sqlite).

What do you think?
I tried contacting the php maintainer by mail, but he didn't answer me.

Oliver

Re: [Mageia-dev] RFP: commenting obsoletes for later removal

[Maarten Vanraes]

Op zaterdag 17 december 2011 16:39:31 schreef Thomas Spuhler:
> On Saturday, December 17, 2011 08:04:42 AM Johnny A. Solbu wrote:
[...]
> > A combination of that and Anssi's suggestion could work.
> > # Obsoleted in: mga2 - added 2011-04
> 
> I don't care about the form, but I think it's a good idea and when someone
> will put it into the documentation, even better :)

i'll second both your opinions

Re: [Mageia-dev] RFP: commenting obsoletes for later removal

[Maarten Vanraes]

Op zaterdag 17 december 2011 14:37:50 schreef Anssi Hannula:
> On 17.12.2011 15:13, Maarten Vanraes wrote:
[...]
> For the record, I'd prefer e.g.
> 
> # added 2011-04
> Obsoletes: foobar < 3.4

imho, it should be more the last time this obsolete is adapted.

and adding a date, doesn't really say much about the release it's for, what if 
it's been done with update after release? that would mean we got the wrong 
release if we counted.

Re: [Mageia-dev] ANN: X11 now starts on tty1

[Maarten Vanraes]

Op zaterdag 17 december 2011 18:09:48 schreef Wolfgang Bornath:
> 2011/12/17 Thierry Vignaud :
[...]
> > you're kidding...
> 
> If you read some other comments here you think they are kidding, too?
> As a special service I will tell you next time when I'm kidding.

if ever :-)

Re: [Mageia-dev] ANN: X11 now starts on tty1

[Maarten Vanraes]

Op zaterdag 17 december 2011 14:10:37 schreef Wolfgang Bornath:
> 2011/12/17 Maarten Vanraes :
> > if we get such a dynamic scheme, that would be nice. but that will likely
> > only work on systemd... what about sysvinit? it was still supposed to be
> > the default for mga2 ...
> > 
> > but we can test, and work on that... if it doesn't work with sysvinit
> > properly, i still vote for returning to F7 ... but we can change that for
> > beta release...
> 
> Yes.
>  - test on developer side until the questions are answered, AFTER that
>  - announce and explain in Errata, discuss mailing list, forum, AFTER that
>  - start to implement into cauldron.
> 
> A bit more is needed than "Just in case you didn't notice, X11 now
> starts on tty1 by default."
> But I'd rather favor the solution of the related bug to avoid this
> whole "workaround"

otoh, i can understand if people want to temporarily put things in cauldron, 
so they are tested.

and likely he did test, but didn't think as far ahead as the rest of us.

Re: [Mageia-dev] mariadb

[Maarten Vanraes]

Op zaterdag 17 december 2011 16:22:50 schreef Balcaen John:
> Le samedi 17 décembre 2011 17:14:52 Anssi Hannula a écrit :
> > On 17.12.2011 15:59, Oliver Burger wrote:
> > > Am Samstag, 17. Dezember 2011, 15:45:42 schrieb Anssi Hannula:
> > >> +1 for not naming it as libmariadb18 if it actually contains
> > >> libmysqlclient.so.18.
> > > 
> > > But mariadb is not mysql, it's a kind of fork of mysql.
> > > 
> > > We don't call libreoffice openoffice and we don't call Mageia Mandriva,
> > > do we?
> > 
> > Fair points.
> > 
> > IMHO library packages should still be primarily named after the library
> > they contain, regardless of project name.
> > 
> > But indeed we have no clear policy regarding that, making it kind of
> > maintainer decision.
> 
> Well since we still don't know if we're going to follow mariadb path or
> mysql, we should probably better stick to mariadb inside the library name.
> (Not to mention we don't know if mariadb is not going to change the
> library's name from libmysql to libmariadb.)
> 
> Regards,

knowing that almost all "Mysql AB" programmers are now in "Monty Program" and 
together with alot other devs are now in mariadb, and oracle had to hire alot 
of new devs to work on mysql... and that Oracle is already busy close-sourcing 
stuff...

i have a feeling that it'll go from a drop-in replacement to a full fork 
somewhere in the future. thus it's not farfetched that they would actually 
rename it.

i'd like to keep it like this for now, we'll see how things evolve.

AL13N

PS: original founder monty, however feels actually no need to rename any of 
it, since he sees it as a continuation and that his programs are named after 
his kids :-). other people feel they should break with oracle and thus do 
different naming...

Re: [Mageia-dev] mariadb

[Maarten Vanraes]

Op zaterdag 17 december 2011 14:45:42 schreef Anssi Hannula:
> On 17.12.2011 15:23, Funda Wang wrote:
> > 2011/12/17 Maarten Vanraes :
> >> ah, didn't see that one... i've put the mklibnames in variables and
> >> resubmitted.
> >> 
> >> perhaps this can be documented somewhere(.spec file policy), or even
> >> better, fixed?
> > 
> > %mklibname takes a lot of parameters, so:
> >Requires: %mklibname mysql %{major} = %{version}-%{release}
> > 
> > will let %mklibname think its parameters are:
> > %1: mysql
> > %2: %{major}
> > %3: =
> > %4: %{version}-%{release}
> > 
> > After parsing, %mklibname only recognize the first three paramerters,
> > and put an underscore between %2 and %3. so it becomes:
> > 
> > %{_lib}mysql%{major}_=
> > 
> > And, %4(%{version}-%{release}) will be throw away.
> > 
> >> PS: I provided the exact provides as mysql, just to be sure that there
> >> is no mageia (or otherwise 3rd party package) could be having troubles
> >> finding the correct packages.
> > 
> > As mariadb is a binary replacement for mysql, why not just named the
> > libs as %{_lib}mysql18 and %{_lib}mysqld18, which is more accurate
> > than %{_lib}mariadb18. Almost all the packages are using binary
> > dependencies (libmysqlclient.so.18) rather than rpm name dependencies,
> > which is more nature than package name, and more reliable.
> 
> +1 for not naming it as libmariadb18 if it actually contains
> libmysqlclient.so.18.

err... no it doesn't, i just said it had the same ABI compatibility, it has 
nothing to do with libmysqlclient

> Even better, just make it libmysqlclient18 for consistency.
> 
> > Personally, I don't think libmysqld18 (now it is named
> > libmariadb-embedded18) should have any relationship with libmysqld0.
> > They have different libmajor, which means all the packages depending
> > on libmysqld0 should be recompiled. So basically, they are different
> > libs actually. Adding symbolic link won't provide any help, either.
> 
> +1 for removal of symlink, and +1 for rename to libmysqld18.

ok, as i replied before, the story is a bit different.

and also, libmysqld0 contains (contrary to intuition), libmysqld.so.X, which 
is the "embedded" mysql version.

calling it libmariadb-embedded (i could hardly have called it libmariadbd or 
something), is actually quite a better name.

Re: [Mageia-dev] ANN: X11 now starts on tty1

[Colin Guthrie]

'Twas brillig, and Kamil Rytarowski at 17/12/11 20:30 did gyre and gimble:
> W dniu 17.12.2011 21:24, Colin Guthrie pisze:
>> 'Twas brillig, and Wolfgang Bornath at 17/12/11 10:58 did gyre and
>> gimble:
>>> About the question how hard it is to press another key: not hard. But
>>> the Ctrl-Alt-F1 has been a standard in ALL distributions and ALL
>>> documentations.
>> [..]
>>
>> That's my take on it.
>>
>> Col
>>
>>
> Hello, I have tested in cauldron and it's working fine. Please add an
> end message at the end of the boot-procedure "Bott procedure succeed.
> Hit ALT-F2 for text log-in.". Some people use minimal systems for simple
> tests - I'm doing it for my packages in a pure environment.

I'll work something out... perhaps starting getty on tty1 automatically
if e.g. prefdm does not run a graphical login. (this would be easy
enough to hack in).

Col


-- 

Colin Guthrie
colin(at)mageia.org
http://colin.guthr.ie/

Day Job:
  Tribalogic Limited http://www.tribalogic.net/
Open Source:
  Mageia Contributor http://www.mageia.org/
  PulseAudio Hacker http://www.pulseaudio.org/
  Trac Hacker http://trac.edgewall.org/

Re: [Mageia-dev] Issues with dracut

[Colin Guthrie]

'Twas brillig, and Colin Guthrie at 17/12/11 20:21 did gyre and gimble:

> So I've got the necessary lib... I wonder if this is a side effect of me
> having lib64ncursesw-devel-5.9-2.mga2 installed (i.e. the dev package)?
> Perhaps it's someone the key to including the right lib? Perhaps you can
> test by installing the 32 bit devel package and seeing if the lib is
> then included automatically?

I tried removing the devel pkg and I still got it... I guess it might be
a 32-bit issue?

If you just checkout the dracut source package (plus our patches) you
can run it in tree with "./dracut -l -H -f foo.img" and inspect with
"lsinitrd foo.img", so if you can have a fiddle that would be great.

Col

-- 

Colin Guthrie
colin(at)mageia.org
http://colin.guthr.ie/

Day Job:
  Tribalogic Limited http://www.tribalogic.net/
Open Source:
  Mageia Contributor http://www.mageia.org/
  PulseAudio Hacker http://www.pulseaudio.org/
  Trac Hacker http://trac.edgewall.org/

Re: [Mageia-dev] ANN: X11 now starts on tty1

[Kamil Rytarowski]

W dniu 17.12.2011 21:24, Colin Guthrie pisze:

'Twas brillig, and Wolfgang Bornath at 17/12/11 10:58 did gyre and gimble:

About the question how hard it is to press another key: not hard. But
the Ctrl-Alt-F1 has been a standard in ALL distributions and ALL
documentations.

[..]

That's my take on it.

Col


Hello, I have tested in cauldron and it's working fine. Please add an 
end message at the end of the boot-procedure "Bott procedure succeed. 
Hit ALT-F2 for text log-in.". Some people use minimal systems for simple 
tests - I'm doing it for my packages in a pure environment.


Regards!

Re: [Mageia-dev] ANN: X11 now starts on tty1

[Colin Guthrie]

'Twas brillig, and Colin Guthrie at 17/12/11 20:24 did gyre and gimble:
> 'Twas brillig, and Wolfgang Bornath at 17/12/11 10:58 did gyre and gimble:
>> About the question how hard it is to press another key: not hard. But
>> the Ctrl-Alt-F1 has been a standard in ALL distributions and ALL
>> documentations.
> 
> Back in the day, text logins were the norm, graphical logins came later.
> Text logins got ttys 1-7... These days they are pretty much useless for
> 99.5% of the use cases and we have to move with the times. There is no
> point keeping this static for the sake of "that's how it's been done
> before". This is the kind of mentality that block progress.
> 
> If we don't want progress and if we don't want to shake of some of the
> hangovers from the old Unix days, we wouldn't have udev, we wouldn't
> have systemd and we wouldn't have numerous other bits.
> 
> The same arguments can easily be applied to other areas (people expect
> system service scripts to be in /etc/init.d/ etc.). We need to let it go.
> 
> As graphical logins are the norm, we should be be catering to them
> first, and leave text logins for special cases.
> 
> That's my take on it.

Oh and I forgot to say Fedora have been doing this for a long time and
other distros have also been experimenting with it too, so this is very
much not something we're going out on a limb to do, but we are trying to
push things forward a bit.

Col


-- 

Colin Guthrie
colin(at)mageia.org
http://colin.guthr.ie/

Day Job:
  Tribalogic Limited http://www.tribalogic.net/
Open Source:
  Mageia Contributor http://www.mageia.org/
  PulseAudio Hacker http://www.pulseaudio.org/
  Trac Hacker http://trac.edgewall.org/

Re: [Mageia-dev] ANN: X11 now starts on tty1

[Colin Guthrie]

'Twas brillig, and Wolfgang Bornath at 17/12/11 10:58 did gyre and gimble:
> About the question how hard it is to press another key: not hard. But
> the Ctrl-Alt-F1 has been a standard in ALL distributions and ALL
> documentations.

Back in the day, text logins were the norm, graphical logins came later.
Text logins got ttys 1-7... These days they are pretty much useless for
99.5% of the use cases and we have to move with the times. There is no
point keeping this static for the sake of "that's how it's been done
before". This is the kind of mentality that block progress.

If we don't want progress and if we don't want to shake of some of the
hangovers from the old Unix days, we wouldn't have udev, we wouldn't
have systemd and we wouldn't have numerous other bits.

The same arguments can easily be applied to other areas (people expect
system service scripts to be in /etc/init.d/ etc.). We need to let it go.

As graphical logins are the norm, we should be be catering to them
first, and leave text logins for special cases.

That's my take on it.

Col


-- 

Colin Guthrie
colin(at)mageia.org
http://colin.guthr.ie/

Day Job:
  Tribalogic Limited http://www.tribalogic.net/
Open Source:
  Mageia Contributor http://www.mageia.org/
  PulseAudio Hacker http://www.pulseaudio.org/
  Trac Hacker http://trac.edgewall.org/

Re: [Mageia-dev] Issues with dracut

[Colin Guthrie]

'Twas brillig, and David W. Hodgins at 17/12/11 20:00 did gyre and gimble:
> On Fri, 16 Dec 2011 09:11:48 -0500, Colin Guthrie
>  wrote:
> 
>> I'll have a look and if I cannot come up with something better, I'll
>> just give up and force grep to be installed :D
> 
> With the current versions of dracut and lvm, lvm is failing to load
> due to libncursesw.so.5 not loading.

This is strange. I've got LVM on my system and it works fine :s

Dracut should install all dynamic libs needed by apps. Which app needs
this library specifically?

> I've solved it on my system for now, by copying
> # ll /usr/lib/libncursesw.so.*
> lrwxrwxrwx 1 root root 18 Jul  1 13:41 /usr/lib/libncursesw.so.5 ->
> libncursesw.so.5.9*
> -rwxr-xr-x 1 root root 369968 Jul  1 04:01 /usr/lib/libncursesw.so.5.9*
> 
> to /lib, running ldconfig and adding
> install_items+=(/lib/libncursesw.so.5.9 /lib/libncursesw.so.5)
> to /etc/dracut.conf.

Cool, good to know it works with tweaks... now to make it automatic.

What is strange is that my initrd contains:

[root@jimmy ~]# lsinitrd| grep libnc
lrwxrwxrwx   1 root root   18 Dec 17 10:41
usr/lib64/libncursesw.so.5 -> libncursesw.so.5.9
-rwxr-xr-x   1 root root   399664 Jul  1 09:00
usr/lib64/libncursesw.so.5.9
lrwxrwxrwx   1 root root   18 Dec 17 10:41
usr/lib64/libncursesw.so -> libncursesw.so.5.9


So I've got the necessary lib... I wonder if this is a side effect of me
having lib64ncursesw-devel-5.9-2.mga2 installed (i.e. the dev package)?
Perhaps it's someone the key to including the right lib? Perhaps you can
test by installing the 32 bit devel package and seeing if the lib is
then included automatically?


FWIW, dracut is crazy easy to hack on so if you can have a play with it,
I'll happily review and merge your patch into our package and push it
upstream if needed.

Col


-- 

Colin Guthrie
colin(at)mageia.org
http://colin.guthr.ie/

Day Job:
  Tribalogic Limited http://www.tribalogic.net/
Open Source:
  Mageia Contributor http://www.mageia.org/
  PulseAudio Hacker http://www.pulseaudio.org/
  Trac Hacker http://trac.edgewall.org/

Re: [Mageia-dev] Issues with dracut

[David W. Hodgins]

On Fri, 16 Dec 2011 09:11:48 -0500, Colin Guthrie  wrote:


I'll have a look and if I cannot come up with something better, I'll
just give up and force grep to be installed :D


With the current versions of dracut and lvm, lvm is failing to load
due to libncursesw.so.5 not loading.

I've solved it on my system for now, by copying
# ll /usr/lib/libncursesw.so.*
lrwxrwxrwx 1 root root 18 Jul  1 13:41 /usr/lib/libncursesw.so.5 -> 
libncursesw.so.5.9*
-rwxr-xr-x 1 root root 369968 Jul  1 04:01 /usr/lib/libncursesw.so.5.9*

to /lib, running ldconfig and adding
install_items+=(/lib/libncursesw.so.5.9 /lib/libncursesw.so.5)
to /etc/dracut.conf.

Regards, Dave Hodgins

Re: [Mageia-dev] KDE 4.8 alpha2

[John Balcaen]

2011/12/15 John Balcaen :
> 2011/12/15 John Balcaen :
> [...]
> One more thing, i did use gold as linker for test purpose as suggested
> some day^^^months ago by Thierry.
>
Ok so i'll start pushing today KDE 4.8 once qtwebkit build is done.




-- 
Balcaen John
Jabber-id: mik...@jabber.littleboboy.net

Re: [Mageia-dev] [changelog] cauldron core/release postfix-2.8.7-1.mga2

[Luis Daniel Lucio Quiroz]

I will in a moment. Dont know what happened since i only update tarball

Enviado desde mi teléfono Verizon Wireless

-Mensaje original-
De: Thierry Vignaud 
Para: Mageia development mailing-list 
Cc: Luis Daniel Lucio Quiroz 
Enviado: sábado 17 de diciembre de 2011 16:58:44 GMT+00:00
Asunto: Re: [Mageia-dev] [changelog] cauldron core/release postfix-2.8.7-1.mga2

On 17 December 2011 02:59, D.Morgan  wrote:
>>> At some point all the Magiaification of postfix has been undone and it
>>> refers again to Mandriva Linux in various man pages and config files etc...
>>>
>>> Not sure if it was this version or from before, but it should certainly
>>> be fixed.
>>
>> It was
>> http://svnweb.mageia.org/packages?view=revision&revision=158099

All of this should be reverted

> i really think that this have nothing to do on our rpms
>
> +%if "%{distribution}" == "Mandriva Linux"
> +       %if %mdkversion < 200900
> +       %post -n %{libname} -p /sbin/ldconfig
> +
> +       %postun -n %{libname} -p /sbin/ldconfig
> +       %endif
> +%endif
Email Shield provided by NOCWorldWide.com

Re: [Mageia-dev] ANN: X11 now starts on tty1

[Sander Lepik]

17.12.2011 19:14, Johnny A. Solbu kirjutas:
Another friend of mine which is not in any of these lists, and is blind, was surprised to 
hear about this change, and was wondering whether this was a Mageia specifi change. I said 
I believe it was.

Well, it's not.

--
Sander

Re: [Mageia-dev] ANN: X11 now starts on tty1

[Johnny A. Solbu]

On Saturday 17 December 2011 17:46, Thierry Vignaud wrote:
> On 17 December 2011 11:26, Wolfgang Bornath  wrote:
> > So, my question is whether a second's flickering during startup really
> > justifies such a strong change?

I was thinking the same thing, but hold it to myself.
Another friend of mine which is not in any of these lists, and is blind, was 
surprised to hear about this change, and was wondering whether this was a 
Mageia specifi change. I said I believe it was.

> you're kidding...

No, we're not.

-- 
Johnny A. Solbu
PGP key ID: 0xFA687324


signature.asc
Description: This is a digitally signed message part.

Re: [Mageia-dev] ANN: X11 now starts on tty1

[Wolfgang Bornath]

2011/12/17 Thierry Vignaud :
> On 17 December 2011 11:26, Wolfgang Bornath  wrote:
>
>> May be yes, may be no. I'm thinking about those computer adepts who
>> have spent 10-15 years with the Ctrl-Alt-F1 combo, is it so easy to
>> change a grown habit which is like the "Red = Stop!" paradigma? I'm
>> thinking also about all those who spend time with different distros,
>> having to change one of the most common procedures just for Mageia.
>> I'm thinking of rather new Linuxers who follow advice in documentation
>> - ALL docs on the net talk about Ctrl-Alt-F1, all generic books like
>> Linux in a Nutshell or others talk about Ctrl-Alt-F1.
>
> quite a lot more end users have tested other distro such as fedora so I
> think there're now quite a lot more users who expect x11 on tty1 than
> on those who expect it on tty7

Ah, is Fedora also doing this? I haven't heard that before.

>> So, my question is whether a second's flickering during startup really
>> justifies such a strong change?
>
> you're kidding...

If you read some other comments here you think they are kidding, too?
As a special service I will tell you next time when I'm kidding.

-- 
wobo

Re: [Mageia-dev] [changelog] cauldron core/release postfix-2.8.7-1.mga2

[Thierry Vignaud]

On 17 December 2011 02:59, D.Morgan  wrote:
>>> At some point all the Magiaification of postfix has been undone and it
>>> refers again to Mandriva Linux in various man pages and config files etc...
>>>
>>> Not sure if it was this version or from before, but it should certainly
>>> be fixed.
>>
>> It was
>> http://svnweb.mageia.org/packages?view=revision&revision=158099

All of this should be reverted

> i really think that this have nothing to do on our rpms
>
> +%if "%{distribution}" == "Mandriva Linux"
> +       %if %mdkversion < 200900
> +       %post -n %{libname} -p /sbin/ldconfig
> +
> +       %postun -n %{libname} -p /sbin/ldconfig
> +       %endif
> +%endif

Re: [Mageia-dev] ANN: X11 now starts on tty1

[Thierry Vignaud]

On 17 December 2011 11:26, Wolfgang Bornath  wrote:

> May be yes, may be no. I'm thinking about those computer adepts who
> have spent 10-15 years with the Ctrl-Alt-F1 combo, is it so easy to
> change a grown habit which is like the "Red = Stop!" paradigma? I'm
> thinking also about all those who spend time with different distros,
> having to change one of the most common procedures just for Mageia.
> I'm thinking of rather new Linuxers who follow advice in documentation
> - ALL docs on the net talk about Ctrl-Alt-F1, all generic books like
> Linux in a Nutshell or others talk about Ctrl-Alt-F1.

quite a lot more end users have tested other distro such as fedora so I
think there're now quite a lot more users who expect x11 on tty1 than
on those who expect it on tty7

> So, my question is whether a second's flickering during startup really
> justifies such a strong change?

you're kidding...

Re: [Mageia-dev] mariadb

[Maarten Vanraes]

Op zaterdag 17 december 2011 14:23:54 schreef Funda Wang:
> 2011/12/17 Maarten Vanraes :
> > ah, didn't see that one... i've put the mklibnames in variables and
> > resubmitted.
> > 
> > perhaps this can be documented somewhere(.spec file policy), or even
> > better, fixed?
> 
> %mklibname takes a lot of parameters, so:
> 
>Requires: %mklibname mysql %{major} = %{version}-%{release}
> 
> will let %mklibname think its parameters are:
> %1: mysql
> %2: %{major}
> %3: =
> %4: %{version}-%{release}
> 
> After parsing, %mklibname only recognize the first three paramerters,
> and put an underscore between %2 and %3. so it becomes:
> 
> %{_lib}mysql%{major}_=
> 
> And, %4(%{version}-%{release}) will be throw away.

right, i figured it out, after i saw it. thanks for the lengthy explanation. 
Speaking with Anssi about this, he mentions that

%{mklibname mysql %{major}} = %{version}-%{release}

would have also solved the issue.

> > PS: I provided the exact provides as mysql, just to be sure that there is
> > no mageia (or otherwise 3rd party package) could be having troubles
> > finding the correct packages.
> 
> As mariadb is a binary replacement for mysql, why not just named the
> libs as %{_lib}mysql18 and %{_lib}mysqld18, which is more accurate
> than %{_lib}mariadb18. Almost all the packages are using binary
> dependencies (libmysqlclient.so.18) rather than rpm name dependencies,
> which is more nature than package name, and more reliable.

i understand, however the %mklibname macro is actually meant for this, and 
will not change.

furthermore, speaking with Anssi about this, 

> Personally, I don't think libmysqld18 (now it is named
> libmariadb-embedded18) should have any relationship with libmysqld0.
> They have different libmajor, which means all the packages depending
> on libmysqld0 should be recompiled. So basically, they are different
> libs actually. Adding symbolic link won't provide any help, either.

in respect to the embedded libraries, it's not actually,

their upstream version was more or less copied from mysql and the developer 
who implemented the cmake change in 5.5 branch for mysql, is the same person 
who's now maintaining that 5.5 cmake branch.

I mentioned that this library should be versioned, and that it's not at this 
time, he agreed, and said that since it's ABI compatible with mysqlclient, 
that he should not use 0 major, but the 18 major (same as mysqlclient)

the code is still 100% exactly the same, it just went from unversioned in 
upstream to versioned.

since we had versioned manually mysqld to major 0, i provided the 
compatibility symlinks for it.

Re: [Mageia-dev] RFP: commenting obsoletes for later removal

[Thomas Spuhler]

On Saturday, December 17, 2011 08:04:42 AM Johnny A. Solbu wrote:
> On Saturday 17 December 2011 14:13, Maarten Vanraes wrote:
> > so that later <...> we can remove older obsoletes in a structured way.
> 
> This might be obvious, but just in case it ain't.
> One need to make sure that the obsoleted package is removed from the new
> release's and mirrors before removing the obsoletes from the spec file, if
> that's what you were thinking of. The proposed wiki article('s) and
> documentation should say something about it.
> 
> > # Obsoletes: mga2
> > (before the obsolete line)
> 
> The wording needs a little working on. The example suggest that mga2 is to
> be obsoleted. and clearly that ain't the intetion. ;-)= I'd sugest
> "Obsoleted in: mga2"
> 
> A combination of that and Anssi's suggestion could work.
> # Obsoleted in: mga2 - added 2011-04
I don't care about the form, but I think it's a good idea and when someone 
will put it into the documentation, even better :)

-- 
Best regards
Thomas Spuhler

Re: [Mageia-dev] ANN: X11 now starts on tty1

[Thomas Spuhler]

On Saturday, December 17, 2011 03:54:33 AM P. Christeas wrote:
> On Saturday 17 December 2011, Wolfgang Bornath wrote:
> > That's one matter, the other one will be teaching all users who were
> > used to the current scheme,
> 
> ++
> 
> Don't underestimate the power of habits, versus the 'flicker'
> inconvenience.
> 
> It is a long habit, it is written in all How-To's, many also have panic
> scripts that do 'chvt 1' when something goes wrong[1]
> 
> I'd say, a bug in plymouth/systemd/whatever needs to be fixed as a bug, not
> trigger such a change of habits and/or standardisation.
> 
> Please don't break our text consoles. We may be spending 99.9% of our time
> in X, but this 0,1% that we need the ttys is priceless!
> 
> [1] remember, a few years ago.. ? the acpi power trick..
+1
-- 
Best regards
Thomas Spuhler

Re: [Mageia-dev] ANN: X11 now starts on tty1

[Anssi Hannula]

On 16.12.2011 20:16, Colin Guthrie wrote:
> Hi
> 
> Just in case you didn't notice, X11 now starts on tty1 by default.
> 
> So if you want a text login shell, make sure you go to tty2!
> 
> I've not actually updated it for sysvinit now I think about it, so I'll
> have to update the default inittab, but the principle is the same. We
> want X there, not a login.

I wonder why that is needed...

If it is to prevent flickering when switching tty1->tty7, can't we just
e.g. make the kernel use tty7 by default if needed?

-- 
Anssi Hannula

Re: [Mageia-dev] mariadb

[Balcaen John]

Le samedi 17 décembre 2011 17:14:52 Anssi Hannula a écrit :
> On 17.12.2011 15:59, Oliver Burger wrote:
> > Am Samstag, 17. Dezember 2011, 15:45:42 schrieb Anssi Hannula:
> >> +1 for not naming it as libmariadb18 if it actually contains
> >> libmysqlclient.so.18.
> > 
> > But mariadb is not mysql, it's a kind of fork of mysql.
> > 
> > We don't call libreoffice openoffice and we don't call Mageia Mandriva, do
> > we?
> Fair points.
> 
> IMHO library packages should still be primarily named after the library
> they contain, regardless of project name.
> 
> But indeed we have no clear policy regarding that, making it kind of
> maintainer decision.
Well since we still don't know if we're going to follow mariadb path or mysql, 
we should probably better stick to mariadb inside the library name.
(Not to mention we don't know if mariadb is not going to change the library's 
name from libmysql to libmariadb.)

Regards,
 
-- 
Balcaen John
Jabber-id: mik...@jabber.littleboboy.net

Re: [Mageia-dev] mariadb

[Anssi Hannula]

On 17.12.2011 15:59, Oliver Burger wrote:
> Am Samstag, 17. Dezember 2011, 15:45:42 schrieb Anssi Hannula:
>> +1 for not naming it as libmariadb18 if it actually contains
>> libmysqlclient.so.18.
> But mariadb is not mysql, it's a kind of fork of mysql.
> 
> We don't call libreoffice openoffice and we don't call Mageia Mandriva, do we?

Fair points.

IMHO library packages should still be primarily named after the library
they contain, regardless of project name.

But indeed we have no clear policy regarding that, making it kind of
maintainer decision.

-- 
Anssi Hannula

Re: [Mageia-dev] RFP: commenting obsoletes for later removal

[Johnny A. Solbu]

On Saturday 17 December 2011 14:13, Maarten Vanraes wrote:
> so that later <...> we can remove older obsoletes in a structured way.

This might be obvious, but just in case it ain't.
One need to make sure that the obsoleted package is removed from the new 
release's and mirrors before removing the obsoletes from the spec file, if 
that's what you were thinking of. The proposed wiki article('s) and 
documentation should say something about it.

> # Obsoletes: mga2 
> (before the obsolete line)

The wording needs a little working on. The example suggest that mga2 is to be 
obsoleted. and clearly that ain't the intetion. ;-)=
I'd sugest "Obsoleted in: mga2"

A combination of that and Anssi's suggestion could work.
# Obsoleted in: mga2 - added 2011-04

-- 
Johnny A. Solbu
PGP key ID: 0xFA687324


signature.asc
Description: This is a digitally signed message part.

Re: [Mageia-dev] mariadb

[Funda Wang]

2011/12/17 Oliver Burger :
> Am Samstag, 17. Dezember 2011, 15:45:42 schrieb Anssi Hannula:
>> +1 for not naming it as libmariadb18 if it actually contains
>> libmysqlclient.so.18.
> But mariadb is not mysql, it's a kind of fork of mysql.
The fact is, if package foo is requiring libmysqlclient.so.18, and
there are libmysql18-5.5.15 and libmariadb18-5.5.18, urpmi will select
libmariadb18 because of its higher version. And, from [1], it is said,
mariadb is a binary drop in replacement for mysql, which quite
different from the word of fork.

[1]: http://kb.askmonty.org/en/mariadb-versus-mysql

> We don't call libreoffice openoffice and we don't call Mageia Mandriva, do we?
>
> Oliver

Re: [Mageia-dev] mariadb

[Oliver Burger]

Am Samstag, 17. Dezember 2011, 15:45:42 schrieb Anssi Hannula:
> +1 for not naming it as libmariadb18 if it actually contains
> libmysqlclient.so.18.
But mariadb is not mysql, it's a kind of fork of mysql.

We don't call libreoffice openoffice and we don't call Mageia Mandriva, do we?

Oliver

Re: [Mageia-dev] mariadb

[Anssi Hannula]

On 17.12.2011 15:23, Funda Wang wrote:
> 2011/12/17 Maarten Vanraes :
>> ah, didn't see that one... i've put the mklibnames in variables and
>> resubmitted.
>>
>> perhaps this can be documented somewhere(.spec file policy), or even better,
>> fixed?
> %mklibname takes a lot of parameters, so:
> 
>Requires: %mklibname mysql %{major} = %{version}-%{release}
> 
> will let %mklibname think its parameters are:
> %1: mysql
> %2: %{major}
> %3: =
> %4: %{version}-%{release}
> 
> After parsing, %mklibname only recognize the first three paramerters,
> and put an underscore between %2 and %3. so it becomes:
> 
> %{_lib}mysql%{major}_=
> 
> And, %4(%{version}-%{release}) will be throw away.
> 
>> PS: I provided the exact provides as mysql, just to be sure that there is no
>> mageia (or otherwise 3rd party package) could be having troubles finding the
>> correct packages.
> As mariadb is a binary replacement for mysql, why not just named the
> libs as %{_lib}mysql18 and %{_lib}mysqld18, which is more accurate
> than %{_lib}mariadb18. Almost all the packages are using binary
> dependencies (libmysqlclient.so.18) rather than rpm name dependencies,
> which is more nature than package name, and more reliable.

+1 for not naming it as libmariadb18 if it actually contains
libmysqlclient.so.18.

Even better, just make it libmysqlclient18 for consistency.

> Personally, I don't think libmysqld18 (now it is named
> libmariadb-embedded18) should have any relationship with libmysqld0.
> They have different libmajor, which means all the packages depending
> on libmysqld0 should be recompiled. So basically, they are different
> libs actually. Adding symbolic link won't provide any help, either.

+1 for removal of symlink, and +1 for rename to libmysqld18.

-- 
Anssi Hannula

Re: [Mageia-dev] RFP: commenting obsoletes for later removal

[Anssi Hannula]

On 17.12.2011 15:13, Maarten Vanraes wrote:
> Hi all,
> 
> Annsi, misc and myself were discussing obsoletes, and i think we should make 
> a 
> policy for a structured comment, so that later (in some timeperiod that's as 
> of yet unspecified) we can remove older obsoletes in a structured way.
> 
> I propose we put a comment in the spec file, with the version the package 
> will 
> be first used, so likely that is cauldron, so example:
> 
> # Obsoletes: mga2
> (before the obsolete line)
> 
> if noone objects, we can put the policy on the wiki somewhere
> 

For the record, I'd prefer e.g.

# added 2011-04
Obsoletes: foobar < 3.4

-- 
Anssi Hannula

Re: [Mageia-dev] mariadb

[Funda Wang]

2011/12/17 Maarten Vanraes :
> ah, didn't see that one... i've put the mklibnames in variables and
> resubmitted.
>
> perhaps this can be documented somewhere(.spec file policy), or even better,
> fixed?
%mklibname takes a lot of parameters, so:

   Requires: %mklibname mysql %{major} = %{version}-%{release}

will let %mklibname think its parameters are:
%1: mysql
%2: %{major}
%3: =
%4: %{version}-%{release}

After parsing, %mklibname only recognize the first three paramerters,
and put an underscore between %2 and %3. so it becomes:

%{_lib}mysql%{major}_=

And, %4(%{version}-%{release}) will be throw away.

> PS: I provided the exact provides as mysql, just to be sure that there is no
> mageia (or otherwise 3rd party package) could be having troubles finding the
> correct packages.
As mariadb is a binary replacement for mysql, why not just named the
libs as %{_lib}mysql18 and %{_lib}mysqld18, which is more accurate
than %{_lib}mariadb18. Almost all the packages are using binary
dependencies (libmysqlclient.so.18) rather than rpm name dependencies,
which is more nature than package name, and more reliable.

Personally, I don't think libmysqld18 (now it is named
libmariadb-embedded18) should have any relationship with libmysqld0.
They have different libmajor, which means all the packages depending
on libmysqld0 should be recompiled. So basically, they are different
libs actually. Adding symbolic link won't provide any help, either.

[Mageia-dev] RFP: commenting obsoletes for later removal

[Maarten Vanraes]

Hi all,

Annsi, misc and myself were discussing obsoletes, and i think we should make a 
policy for a structured comment, so that later (in some timeperiod that's as 
of yet unspecified) we can remove older obsoletes in a structured way.

I propose we put a comment in the spec file, with the version the package will 
be first used, so likely that is cauldron, so example:

# Obsoletes: mga2
(before the obsolete line)


if noone objects, we can put the policy on the wiki somewhere

Re: [Mageia-dev] ANN: X11 now starts on tty1

[Wolfgang Bornath]

2011/12/17 Maarten Vanraes :
>
> if we get such a dynamic scheme, that would be nice. but that will likely only
> work on systemd... what about sysvinit? it was still supposed to be the
> default for mga2 ...
>
> but we can test, and work on that... if it doesn't work with sysvinit
> properly, i still vote for returning to F7 ... but we can change that for beta
> release...

Yes.
 - test on developer side until the questions are answered, AFTER that
 - announce and explain in Errata, discuss mailing list, forum, AFTER that
 - start to implement into cauldron.

A bit more is needed than "Just in case you didn't notice, X11 now
starts on tty1 by default."
But I'd rather favor the solution of the related bug to avoid this
whole "workaround"

-- 
wobo

Re: [Mageia-dev] mariadb

[Maarten Vanraes]

Op zaterdag 17 december 2011 13:12:52 schreef Funda Wang:
> 2011/12/17 Maarten Vanraes :
> > %mklibname works fine,
> 
> Did you really have tests that if %mklibname works as expected?
> $ rpm -qp --obsoletes
> libmariadb18-5.5.18-0.bzr3169.20111216.2.mga2.i586.rpm libmysql18_<
> $ rpm -qp --provides libmariadb18-5.5.18-0.bzr3169.20111216.2.mga2.i586.rpm
> mariadb-shared-libs = 5.5.18-0.bzr3169.20111216.2.mga2
> mariadb-shared = 5.5.18-0.bzr3169.20111216.2.mga2
> libmysql18_=
> libmysqlclient.so.18
> libmysqlclient.so.18(libmysqlclient_16)
> libmysqlclient.so.18(libmysqlclient_18)
> libmariadb18 = 5.5.18-0.bzr3169.20111216.2.mga2
> libmariadb18(x86-32) = 5.5.18-0.bzr3169.20111216.2.mga2
> 
> Please notify the empty version string in provides and obsoletes after "=".
[...]

ah, didn't see that one... i've put the mklibnames in variables and 
resubmitted.

perhaps this can be documented somewhere(.spec file policy), or even better, 
fixed?

Thanks for letting me know, allthough i'd preferred if you spoke to maintainer 
before doing this.

AL13N

PS: I provided the exact provides as mysql, just to be sure that there is no 
mageia (or otherwise 3rd party package) could be having troubles finding the 
correct packages.

Re: [Mageia-dev] mariadb

[Funda Wang]

2011/12/17 Maarten Vanraes :
> %mklibname works fine,
Did you really have tests that if %mklibname works as expected?
$ rpm -qp --obsoletes libmariadb18-5.5.18-0.bzr3169.20111216.2.mga2.i586.rpm
libmysql18_<
$ rpm -qp --provides libmariadb18-5.5.18-0.bzr3169.20111216.2.mga2.i586.rpm
mariadb-shared-libs = 5.5.18-0.bzr3169.20111216.2.mga2
mariadb-shared = 5.5.18-0.bzr3169.20111216.2.mga2
libmysql18_=
libmysqlclient.so.18
libmysqlclient.so.18(libmysqlclient_16)
libmysqlclient.so.18(libmysqlclient_18)
libmariadb18 = 5.5.18-0.bzr3169.20111216.2.mga2
libmariadb18(x86-32) = 5.5.18-0.bzr3169.20111216.2.mga2

Please notify the empty version string in provides and obsoletes after "=".

> your issue was the bug that mysql-devel wasn't properly
> obsoleted...
I guess not, having versioned obsoletes makes it possible if we will
revert to mysql at some time in the future.

> problem is, that you've removed some provides now, so if packages will be
> depending on lib64mysql18, it'll not be working now...
I don't see any package have direct dep on lib64mysql18 as package
name, in cauldron repository.

> you also did a wrong obsolete with %{version}-%{release}
>
> also, if a package has a maintainer, i think policy (or at least common
> courtesy) is to speak with maintainer about this?
>
> and why even submitting amarok, when mikala will bring new KDE soon?
Because amarok is a package listed in meta-task, we should make sure
most of them at least installing correctly. Due to new mariadb changes
libmajor of libmysqld.

> i'm resubmitting mariadb
That leads to the problems as i said.

> you should've just fixed the wrong obsoletes and vendor tag and missing
> provides.
>
> regards,

Re: [Mageia-dev] ANN: X11 now starts on tty1

[Maarten Vanraes]

Op zaterdag 17 december 2011 11:58:31 schreef Wolfgang Bornath:
> 2011/12/17 Florian Hubold :
> > Am 17.12.2011 11:26, schrieb Wolfgang Bornath:
> >> 2011/12/17 Sander Lepik :
> >>> 17.12.2011 12:10, Wolfgang Bornath kirjutas:
>  I really beg to think the whole matter over again, at least until it
>  is mature enough to be implemented in cauldron for practical test.
> >>> 
> >>> People will get used to it rather fast.
> >> 
> >> May be yes, may be no. I'm thinking about those computer adepts who
> >> have spent 10-15 years with the Ctrl-Alt-F1 combo, is it so easy to
> >> change a grown habit which is like the "Red = Stop!" paradigma? I'm
> >> thinking also about all those who spend time with different distros,
> >> having to change one of the most common procedures just for Mageia.
> >> I'm thinking of rather new Linuxers who follow advice in documentation
> >> - ALL docs on the net talk about Ctrl-Alt-F1, all generic books like
> >> Linux in a Nutshell or others talk about Ctrl-Alt-F1.
> >> 
> >> So, my question is whether a second's flickering during startup really
> >> justifies such a strong change?
> > 
> > Well, maybe you haven't heard of the related problems yet:
> > https://wiki.mageia.org/en/Mageia_2_Errata#Xserver_crashes
> 
> Of course I read that part of the Errata but did not relate it to the
> matter of this thread - how could I as a non-developer? The relation
> has not been mentioned in the errata.
> 
> As I wrote in my first mail I am not really against this change if
> there is a reason. There seems to be a reason (as you say), so it's
> ok. But still I think all open questions (especially the one about the
> situation of a crashing or failing x server) need to be addressed
> before the change is made in cauldron to be tested by a broader
> userbase. And I still think it needs to be announced all over the
> place when the change will be implemented.

it does need to be announced all over the place.

> About the question how hard it is to press another key: not hard. But
> the Ctrl-Alt-F1 has been a standard in ALL distributions and ALL
> documentations (even in the generic books about "Learning Linux"), a
> standard like the SAA menue standard ("File" on the left, "Help" on
> the right) or the "F1 opens Help" standard. Therefore changing this is
> a bit more than usual changes between versions.

well, that may be true, but not anymore on all distros and during installation 
times not anymore as well...

if we get such a dynamic scheme, that would be nice. but that will likely only 
work on systemd... what about sysvinit? it was still supposed to be the 
default for mga2 ...

but we can test, and work on that... if it doesn't work with sysvinit 
properly, i still vote for returning to F7 ... but we can change that for beta 
release...

Re: [Mageia-dev] ANN: X11 now starts on tty1

[P. Christeas]

On Saturday 17 December 2011, Wolfgang Bornath wrote:
> That's one matter, the other one will be teaching all users who were
> used to the current scheme, 

++

Don't underestimate the power of habits, versus the 'flicker' inconvenience.

It is a long habit, it is written in all How-To's, many also have panic 
scripts that do 'chvt 1' when something goes wrong[1]

I'd say, a bug in plymouth/systemd/whatever needs to be fixed as a bug, not 
trigger such a change of habits and/or standardisation.

Please don't break our text consoles. We may be spending 99.9% of our time in 
X, but this 0,1% that we need the ttys is priceless!

[1] remember, a few years ago.. ? the acpi power trick..

-- 
Say NO to spam and viruses. Stop using Microsoft Windows!

Re: [Mageia-dev] ANN: X11 now starts on tty1

[Wolfgang Bornath]

2011/12/17 Florian Hubold :
> Am 17.12.2011 11:26, schrieb Wolfgang Bornath:
>> 2011/12/17 Sander Lepik :
>>> 17.12.2011 12:10, Wolfgang Bornath kirjutas:
 I really beg to think the whole matter over again, at least until it is
 mature enough to be implemented in cauldron for practical test.
>>> People will get used to it rather fast.
>> May be yes, may be no. I'm thinking about those computer adepts who
>> have spent 10-15 years with the Ctrl-Alt-F1 combo, is it so easy to
>> change a grown habit which is like the "Red = Stop!" paradigma? I'm
>> thinking also about all those who spend time with different distros,
>> having to change one of the most common procedures just for Mageia.
>> I'm thinking of rather new Linuxers who follow advice in documentation
>> - ALL docs on the net talk about Ctrl-Alt-F1, all generic books like
>> Linux in a Nutshell or others talk about Ctrl-Alt-F1.
>>
>> So, my question is whether a second's flickering during startup really
>> justifies such a strong change?
>>
> Well, maybe you haven't heard of the related problems yet:
> https://wiki.mageia.org/en/Mageia_2_Errata#Xserver_crashes

Of course I read that part of the Errata but did not relate it to the
matter of this thread - how could I as a non-developer? The relation
has not been mentioned in the errata.

As I wrote in my first mail I am not really against this change if
there is a reason. There seems to be a reason (as you say), so it's
ok. But still I think all open questions (especially the one about the
situation of a crashing or failing x server) need to be addressed
before the change is made in cauldron to be tested by a broader
userbase. And I still think it needs to be announced all over the
place when the change will be implemented.

About the question how hard it is to press another key: not hard. But
the Ctrl-Alt-F1 has been a standard in ALL distributions and ALL
documentations (even in the generic books about "Learning Linux"), a
standard like the SAA menue standard ("File" on the left, "Help" on
the right) or the "F1 opens Help" standard. Therefore changing this is
a bit more than usual changes between versions.

-- 
wobo

Re: [Mageia-dev] ANN: X11 now starts on tty1

[Florian Hubold]

Am 17.12.2011 11:26, schrieb Wolfgang Bornath:
> 2011/12/17 Sander Lepik :
>> 17.12.2011 12:10, Wolfgang Bornath kirjutas:
>>> I really beg to think the whole matter over again, at least until it is
>>> mature enough to be implemented in cauldron for practical test.
>> People will get used to it rather fast.
> May be yes, may be no. I'm thinking about those computer adepts who
> have spent 10-15 years with the Ctrl-Alt-F1 combo, is it so easy to
> change a grown habit which is like the "Red = Stop!" paradigma? I'm
> thinking also about all those who spend time with different distros,
> having to change one of the most common procedures just for Mageia.
> I'm thinking of rather new Linuxers who follow advice in documentation
> - ALL docs on the net talk about Ctrl-Alt-F1, all generic books like
> Linux in a Nutshell or others talk about Ctrl-Alt-F1.
>
> So, my question is whether a second's flickering during startup really
> justifies such a strong change?
>
Well, maybe you haven't heard of the related problems yet:
https://wiki.mageia.org/en/Mageia_2_Errata#Xserver_crashes
So what would be better: desktop session crashing when you press
the enter key or ttys available on different keys?

How hard is it to just press a different key or keep switching
until you hit a tty? That's what i do when i forget on which key
the damn x session was to get back to it. :)

Which is also differing between distros, some have x session on
tty 1, some on 7 and Mandriva/Mageia since some time on 8,
due to plymouth and the handover to the DM, IIRC.

Re: [Mageia-dev] ANN: X11 now starts on tty1

[Wolfgang Bornath]

2011/12/17 Sander Lepik :
> 17.12.2011 12:10, Wolfgang Bornath kirjutas:
>>
>> I really beg to think the whole matter over again, at least until it is
>> mature enough to be implemented in cauldron for practical test.
>
> People will get used to it rather fast.

May be yes, may be no. I'm thinking about those computer adepts who
have spent 10-15 years with the Ctrl-Alt-F1 combo, is it so easy to
change a grown habit which is like the "Red = Stop!" paradigma? I'm
thinking also about all those who spend time with different distros,
having to change one of the most common procedures just for Mageia.
I'm thinking of rather new Linuxers who follow advice in documentation
- ALL docs on the net talk about Ctrl-Alt-F1, all generic books like
Linux in a Nutshell or others talk about Ctrl-Alt-F1.

So, my question is whether a second's flickering during startup really
justifies such a strong change?

-- 
wobo

Re: [Mageia-dev] ANN: X11 now starts on tty1

[Sander Lepik]

17.12.2011 12:10, Wolfgang Bornath kirjutas:
I really beg to think the whole matter over again, at least until it is mature enough to 
be implemented in cauldron for practical test. 

People will get used to it rather fast.

--
Sander

Re: [Mageia-dev] ANN: X11 now starts on tty1

[Wolfgang Bornath]

2011/12/17 Maarten Vanraes :
> Op zaterdag 17 december 2011 10:52:52 schreef Florian Hubold:
>> Am 17.12.2011 02:26, schrieb Maarten Vanraes:
>> > Op zaterdag 17 december 2011 02:03:55 schreef Colin Guthrie:
>> >> 'Twas brillig, and Maarten Vanraes at 17/12/11 00:50 did gyre and gimble:
>> >>> how does this relate to multiple sessions? if it starts at tty1 and
>> >>> next session starts at tty2 and so forth, were are the textbased tty's
>> >>> then?
>> >>
>> >> 2nd session starts on tty7 (i.e. the next available tty). Not exactly
>> >> super intuitive I agree so open to suggestions here... i.e. one option
>> >> would be to only start txt ttys on 7 & 8 (two should be enough right?)
>> >> leaving tty 1 through 6 for graphical logins.
>> >
>> > if could be nice if they were "on-demand" ?
>>
>> Couldn't they be socket-activated which is one of the killer features
>> of systemd? Like with cups after Lennarts patches, which now only
>> starts on-demand?
> [...]
>
> that would be nice, but what if you do a rapid ctrl+alt+F2-F8, all your stuff
> will be tty, nothing left for sessions?

That's one matter, the other one will be teaching all users who were
used to the current scheme, many of them using it for many years.
Especially if we do not announce it with big fat red letters! Still
there will be the fast C-ALT-F1-6 just from automatic procedure,
people will be more annoyed by that than by a little flickering for a
second during system start.

I really beg to think the whole matter over again, at least until it
is mature enough to be implemented in cauldron for practical test.

-- 
wobo

Re: [Mageia-dev] ANN: X11 now starts on tty1

[Maarten Vanraes]

Op zaterdag 17 december 2011 10:52:52 schreef Florian Hubold:
> Am 17.12.2011 02:26, schrieb Maarten Vanraes:
> > Op zaterdag 17 december 2011 02:03:55 schreef Colin Guthrie:
> >> 'Twas brillig, and Maarten Vanraes at 17/12/11 00:50 did gyre and gimble:
> >>> how does this relate to multiple sessions? if it starts at tty1 and
> >>> next session starts at tty2 and so forth, were are the textbased tty's
> >>> then?
> >> 
> >> 2nd session starts on tty7 (i.e. the next available tty). Not exactly
> >> super intuitive I agree so open to suggestions here... i.e. one option
> >> would be to only start txt ttys on 7 & 8 (two should be enough right?)
> >> leaving tty 1 through 6 for graphical logins.
> > 
> > if could be nice if they were "on-demand" ?
> 
> Couldn't they be socket-activated which is one of the killer features
> of systemd? Like with cups after Lennarts patches, which now only
> starts on-demand?
[...]

that would be nice, but what if you do a rapid ctrl+alt+F2-F8, all your stuff 
will be tty, nothing left for sessions?

and what if you log into tty, and later log out again?

perhaps if it's not logged in or shown, it should disappear again, freeing up 
a spot for graphical sessions?

Re: [Mageia-dev] ANN: X11 now starts on tty1

[Florian Hubold]

Am 17.12.2011 02:26, schrieb Maarten Vanraes:
> Op zaterdag 17 december 2011 02:03:55 schreef Colin Guthrie:
>> 'Twas brillig, and Maarten Vanraes at 17/12/11 00:50 did gyre and gimble:
>>> how does this relate to multiple sessions? if it starts at tty1 and next
>>> session starts at tty2 and so forth, were are the textbased tty's then?
>> 2nd session starts on tty7 (i.e. the next available tty). Not exactly
>> super intuitive I agree so open to suggestions here... i.e. one option
>> would be to only start txt ttys on 7 & 8 (two should be enough right?)
>> leaving tty 1 through 6 for graphical logins.
> if could be nice if they were "on-demand" ?
Couldn't they be socket-activated which is one of the killer features
of systemd? Like with cups after Lennarts patches, which now only
starts on-demand?
>  
>>> what happens if X doesn't start on tty1 and tries to fall back to
>>> console? will we have a black screen?
>> Dunno about that one. We could maybe start a getty automatically on tty1
>> if this happens... will have to test how this would work in practice.
> would be nice to know what happens...
>

[Mageia-dev] mariadb

[Maarten Vanraes]

why are you doing this?

%mklibname works fine, your issue was the bug that mysql-devel wasn't properly 
obsoleted... 

problem is, that you've removed some provides now, so if packages will be 
depending on lib64mysql18, it'll not be working now...

you also did a wrong obsolete with %{version}-%{release}

also, if a package has a maintainer, i think policy (or at least common 
courtesy) is to speak with maintainer about this?

and why even submitting amarok, when mikala will bring new KDE soon?

i'm resubmitting mariadb

you should've just fixed the wrong obsoletes and vendor tag and missing 
provides.

regards,

AL13N

[alien@localhost mariadb]$ svn diff -c 182925
Index: SPECS/mariadb.spec
===
--- SPECS/mariadb.spec  (revision 182924)
+++ SPECS/mariadb.spec  (revision 182925)
@@ -49,7 +49,7 @@
 Summary:   A very fast and reliable SQL database engine
 Name:  mariadb
 Version:   5.5.18
-Release:   %mkrel 0.bzr%bzrrev
+Release:   %mkrel 0.bzr%{bzrrev}.1
 Group: Databases
 License:   GPLv2 with exceptions
 URL:   http://mariadb.org/
@@ -228,8 +228,8 @@
 Group: System/Libraries
 Provides:  %{name}-shared-libs = %{version}-%{release}
 Provides:  %{name}-shared = %{version}-%{release}
-Provides:  %mklibname mysql %{major} = %{version}-%{release}
-Obsoletes: %mklibname mysql %{major} < 5.5.18
+Provides:  %{_lib}mysql%{major} = %{version}-%{release}
+Obsoletes: %{_lib}mysql%{major} < 5.5.18
 
 %description -n%{libname}
 This package contains the shared libraries (*.so*) which certain languages 
and
@@ -239,8 +239,8 @@
 %package -n%{libmariadbservices}
 Summary:   Shared libraries
 Group: System/Libraries
-Provides:  %mklibname mysqlservices = %{version}-%{release}
-Obsoletes: %mklibname mysqlservices < 5.5.18
+Provides:  %{_lib}mysqlservices = %{version}-%{release}
+Obsoletes: %{_lib}mysqlservices < 5.5.18
 
 %description -n%{libmariadbservices}
 The libmariadbservices library provides access to the available services and 
@@ -262,11 +262,10 @@
 Requires:  %{name}-client >= %{version}-%{release}
 Provides:  %{name}-devel = %{version}-%{release}
 Provides:  %{libname}-devel = %{version}-%{release}
-Obsoletes: %{libname}-devel
+Obsoletes: %{libname}-devel < %{version}-%{release}
 Obsoletes: %{old_staticdevelname} < 5.5.10
-Obsoletes: %mklibname -d mysql < 5.5.18
-Provides:  %mklibname -d mysql = %{version}-%{release}
-Provides:  mysql-devel
+Obsoletes: %{_lib}mysql-devel < 5.5.18
+Provides:  mysql-devel = %{version}-%{release}

 %description -n%{develname}
 This package contains the development header files and libraries necessary to
@@ -277,8 +276,7 @@
 Group: System/Libraries
 Provides:  %{name}-embedded = %{version}-%{release}
 Obsoletes: %{name}-embedded < 5.5.10-6
-Provides:  %mklibname mysqld %{libmysqlembedded_major} = 
%{version}-%{release}
-Obsoletes: %mklibname mysqld %{libmysqlembedded_major} < 5.5.18
+Obsoletes: %{_lib}mysqld%{libmysqlembedded_major} < 5.5.18

 %description -n %{libmariadbembedded}
 MariaDB is a multi-user, multi-threaded SQL database server. This
@@ -292,11 +290,11 @@
 Summary:   Development files for MySQL as an embeddable library
 Group: Development/Other
 Provides:  %{name}-embedded-devel = %{version}-%{release}
-Obsoletes: %{name}-embedded-devel <  5.5.10-6
+Obsoletes: %{name}-embedded-devel < 5.5.10-6
 Requires:  %{libmariadbembedded} = %{version}-%{release}
 Requires:  %{name}-devel = %{version}-%{release}
-Provides:  %mklibname -d mysqld = %{version}-%{release}
-Obsoletes: %mklibname -d mysqld < 5.5.18
+Obsoletes: %{_lib}mysqld-devel < 5.5.18
+Provides:  mysql-embedded-devel = %{version}-%{release}

 %description -n %{libmariadbembedded_devel}
 MariaDB is a multi-user, multi-threaded SQL database server. This
@@ -381,7 +379,7 @@
 -DWITHOUT_DAEMON_EXAMPLE=1 \
 -DWITH_PLUGIN_PBXT=1 \
 -DFEATURE_SET="community" \
--DCOMPILATION_COMMENT="Mageia - MariaDB Community Edition (GPL)"
+-DCOMPILATION_COMMENT="%{_vendor} - MariaDB Community Edition (GPL)"

 cp ../libmysql/libmysql.version libmysql/libmysql.version

Re: [Mageia-dev] pixmap

[Colette Jean-Claude]

On 14/12/2011 21:49, Dan Fandrich wrote:

On Wed, Dec 14, 2011 at 09:42:54PM +0100, jcc wrote:

I have a problem with the icon of the application.

First I tried to save the icon image in pixmap directory but no icon
appears on the desktop menu bar.

What does your .desktop file look like?


Dan

Hi,

I send you the desktop file:

mkdir -p $RPM_BUILD_ROOT%{_datadir}/applications
cat > $RPM_BUILD_ROOT%{_datadir}/applications/axiom.desktop << EOF
[Desktop Entry]
Encoding=UTF-8
Name=axiom
GenericName=axiom
GenericName[fr]=axiom
Comment=Computer Algebra system
Comment[fr]=Système de calcul formel
Exec=axiom
TryExec=axiom
Icon=axiom
Terminal=true
Type=Application
Categories=Education;Science;Math;
EOF

But I have installed application launcher Lancelot in the plasmoid and 
the icon appears.

So I think that it become from the Mageia launcher under kde. :(