Re: [Mageia-dev] A note on autologin and startx

[Jose Jorge]

Le 06/04/2012 22:53, Colin Guthrie a écrit :

Couldn't agree more. I'd say we can happily provide a tool to configure
autologin, but if that is configured, it basically just sets the DM to
gdm, and lets' it do the autologin.

The fact that gdm is used should be mostly hidden from users.

> From what I've seen, gdm seems to be the best implementation of the
whole pam and authentication stuff, so this would be my personal favourite.

Col
Please note that autologin is lightweight and fast, so I use it for very 
old systems, where even the 30Mb of RAM eaten by gdm count.
But I just can agree that if no one has time to fix it, we can drop it. 
I'll be away from computers for  15 days ...

[Mageia-dev] Freeze push: webkit 1.8.0

[Funda Wang]

Hello,

Could somebody push webkit 1.8.0 into cauldron? We are aiming at 1.8.0
stable in mga2, while we current have 1.7.92 unstable for cauldron.

Thanks.

[Mageia-dev] nvidia

[Pascal Terjan]

Hi,

regarding http://check.mageia.org/cauldron/tmb/dependencies.html do you
know if nvidia173/kmod-nvidia173 and nvidia-96xx/kmod-nvidia96xx should be
obsoleted by something (nouveau?)?

I don't know anything about nvidia but internet says 173 and 96xx are not
compatible with x11-server 1.11
Compatibility with 1.10 was added in the latest version, in August last
year, 6 months after 1.10 was released, and a week before 1.11 was
released. It has now been more than 6 months since 1.11 was released, 1.12
was released last month, so should we still expect 1.11 (and recent
kernels) support to happen?

Re: [Mageia-dev] rtl819xxx support seems broken

[Frank Griffin]

On 04/06/2012 04:39 PM, simple w8 wrote:
You need to install the package kernel-firmware-nonfree thats the one 
who haves the firmawsre files for Realtek 8192 drivers. But with me 
that didnt solve the case completly, since i had some keyboard/mouse 
behaviour caused by it, so i entered Realtek website and downloaded 
and build the latest drivers avaialble. You can also copy the 
firmaware files from the mandriva package kernel-firmware-extra, with 
me they worked great. 


Already installed.  And Mageia had worked just fine with this chip 
prior  to the last update.  Somebody fumble-fingered an ldetect update 
most likely.

Re: [Mageia-dev] [changelog] [RPM] cauldron core/release perl-Dist-Zilla-PluginBundle-Author-JQUELIN-2.120.970-1.mga2

[Pascal Terjan]

On Fri, Apr 6, 2012 at 11:02, jquelin  wrote:

> Name: perl-Dist-Zilla-PluginBundle-Author-JQUELIN  Relocations:
> (not relocatable)
> Version : 2.120.970 Vendor: Mageia.Org
> Release : 1.mga2Build Date: Fri Apr  6
> 11:59:56 2012
> Install Date: (not installed)   Build Host: jonund.mageia.org
> Group   : Development/Perl  Source RPM: (none)
> Size: 19350License: GPL+ or Artistic
> Signature   : (none)
> Packager: jquelin 
> URL :
> http://search.cpan.org/dist/Dist-Zilla-PluginBundle-Author-JQUELIN
> Summary : Build & release a distribution like jquelin
> Description :
> This is a plugin bundle to load all dist-zilla plugins that jq is using.
>
> jquelin  2.120.970-1.mga2:
> + Revision: 228900
> - update to 2.120970
> - dist renamed upstream
>

but upstream did not update Task-Dist-Zilla, bad upstream ! :)

Re: [Mageia-dev] A note on autologin and startx

[Colin Guthrie]

'Twas brillig, and Olav Vitters at 06/04/12 21:10 did gyre and gimble:
> On Fri, Apr 06, 2012 at 05:14:04PM +0100, Colin Guthrie wrote:
>> Overall, however, the autologin code is pretty broken. I *should*
>> register a graphical login after starting X (the same way gdm does it),
>> that way it will remain active and there won't be vt switch related issues.
> 
> IMO (and take into account + as said many times before, I almost only
> care about GNOME), drop it (Mageia 3?).
> 
> Within GNOME you can configure the GDM autologin via System Settings. If
> the patches are hackish, why support it while loads of extra display
> managers are being added. Just creates more problems IMO.

Couldn't agree more. I'd say we can happily provide a tool to configure
autologin, but if that is configured, it basically just sets the DM to
gdm, and lets' it do the autologin.

The fact that gdm is used should be mostly hidden from users.

>From what I've seen, gdm seems to be the best implementation of the
whole pam and authentication stuff, so this would be my personal favourite.

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] rtl819xxx support seems broken

[simple w8]

2012/4/5 Frank Griffin :
> On 04/05/2012 12:37 PM, Frank Griffin wrote:
>>
>> It looks like it should either be r8192e_pci or else rtl8192se.
>>
>> Any ideas ?
>>
> According to an lsmod | grep 819 on an older partition that works, the
> correct module is rtl8192se.

You need to install the package kernel-firmware-nonfree thats the one
who haves the firmawsre files for Realtek 8192 drivers.
But with me that didnt solve the case completly, since i had some
keyboard/mouse behaviour caused by it, so i entered Realtek website
and downloaded and build the latest drivers avaialble.

You can also copy the firmaware files from the mandriva package
kernel-firmware-extra, with me they worked great.

Re: [Mageia-dev] A note on autologin and startx

[Olav Vitters]

On Fri, Apr 06, 2012 at 05:14:04PM +0100, Colin Guthrie wrote:
> Overall, however, the autologin code is pretty broken. I *should*
> register a graphical login after starting X (the same way gdm does it),
> that way it will remain active and there won't be vt switch related issues.

IMO (and take into account + as said many times before, I almost only
care about GNOME), drop it (Mageia 3?).

Within GNOME you can configure the GDM autologin via System Settings. If
the patches are hackish, why support it while loads of extra display
managers are being added. Just creates more problems IMO.

-- 
Regards,
Olav

[Mageia-dev] Freeze push: compiz 0.9.7.6

[Julien]

Hi,

please push compiz 0.9.7.6 which contains several bugfix and performance
optimizations
Thanks

Regards
Julien

Re: [Mageia-dev] Release_blocker bugs

[Colin Guthrie]

'Twas brillig, and Thierry Vignaud at 06/04/12 19:24 did gyre and gimble:
> On 6 April 2012 19:38, Thomas Backlund  wrote:
>>> There was one issue regarding the kernel *bin depmods files and dracut
>>> that someone reported as being due to that dracut was using kmod but the
>>> kernel's *.bin files were created with m-i-t... I forget the details, so
>>> not sure if it's an issue or not.
>>
>> Since everything else uses kmod, even if it's late in the game I think
>> we should do the switch now for the userland tools too before we release
>> beta3.
>>
>> That way the tools would be unified, and we still would have time to
>> revert for RC if needed...
>>
>> Any objections ?
> 
> No

Sounds good to me.

New kmod should be with you shortly.

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] Freeze push: nvidia-current 295.33

[Thomas Backlund]

06.04.2012 21:02, Anssi Hannula skrev:
> Please submit nvidia-current, new version 295.33.
> 
> It is a long-lived branch release (we have now 295.20), and contains
> several important bugfixes and official support for the first Kepler
> GPUs (we already have nouveau support for those).
> 
> http://www.nvnews.net/vbulletin/showthread.php?p=2538961
> 
> Sorry for not pushing this through earlier, I was completely under the
> impression we already had this already (even pushed the ids to
> ldetect-lst), until Sander requested it in IRC today...
> 
> I've been running this on one cauldron system for two weeks without issues.
> 

Pushed.

--
Thomas

Re: [Mageia-dev] Release_blocker bugs

[Thierry Vignaud]

On 6 April 2012 19:38, Thomas Backlund  wrote:
>> There was one issue regarding the kernel *bin depmods files and dracut
>> that someone reported as being due to that dracut was using kmod but the
>> kernel's *.bin files were created with m-i-t... I forget the details, so
>> not sure if it's an issue or not.
>
> Since everything else uses kmod, even if it's late in the game I think
> we should do the switch now for the userland tools too before we release
> beta3.
>
> That way the tools would be unified, and we still would have time to
> revert for RC if needed...
>
> Any objections ?

No

Re: [Mageia-dev] Pleash push snort

[Anssi Hannula]

06.04.2012 20:51, Luis Daniel Lucio Quiroz kirjoitti:
> Please push snort 2.9.2.2 .  It fixes too many false
> positives.

Submitted.

-- 
Anssi Hannula

[Mageia-dev] Freeze push: nvidia-current 295.33

[Anssi Hannula]

Please submit nvidia-current, new version 295.33.

It is a long-lived branch release (we have now 295.20), and contains
several important bugfixes and official support for the first Kepler
GPUs (we already have nouveau support for those).

http://www.nvnews.net/vbulletin/showthread.php?p=2538961

Sorry for not pushing this through earlier, I was completely under the
impression we already had this already (even pushed the ids to
ldetect-lst), until Sander requested it in IRC today...

I've been running this on one cauldron system for two weeks without issues.

-- 
Anssi Hannula

[Mageia-dev] Pleash push snort

[Luis Daniel Lucio Quiroz]

Please push snort 2.9.2.2.  It fixes too many false positives.

Enviado desde mi teléfono Verizon Wireless

Re: [Mageia-dev] Release_blocker bugs

[Thomas Backlund]

06.04.2012 19:19, Colin Guthrie skrev:
> 'Twas brillig, and Maarten Vanraes at 06/04/12 16:43 did gyre and gimble:
>> Op vrijdag 06 april 2012 13:17:46 schreef Anne nicolas:
>> [...]
>>> Does not seem to be release_blocker
>>> ===
>>> 4301bugsq...@mageia.org Migration of module-init-tools to kmod 
>>> lib in
>>> Mageia 2 - specifications
>>> => 4802
>> [...]
>>
>> i may understand this wrong, but iinm, module-init-tools doesn't work with 
>> current kernel anymore, and kmod is now required => doublecheck with tmb
> 
> I'm not sure what the specifications specifically meant in this regard,
> but we did used to have a lib made from module-init-tools which was then
> used elsewhere. We've not dropped that lib, and now use libkmod directly
> everywhere it's needed.
> 
> The only thing we've not done is to actually use the kmod binaries for
> modprobe, insmod, rmmod, lsmod, etc.
> 
> That said, it's a simple switch in the kmod spec to turn it on (and
> obsolite module-init-tools). I've mentioned this before, but no one
> really picked up on it. It's very late in the day to do this switch
> (although I have personally be running it for a while without any issues).
> 
> There was one issue regarding the kernel *bin depmods files and dracut
> that someone reported as being due to that dracut was using kmod but the
> kernel's *.bin files were created with m-i-t... I forget the details, so
> not sure if it's an issue or not.
> 

Since everything else uses kmod, even if it's late in the game I think
we should do the switch now for the userland tools too before we release
beta3.

That way the tools would be unified, and we still would have time to
revert for RC if needed...

Any objections ?

--
Thomas

Re: [Mageia-dev] Freeze push: KDE 4.8.2

[Thomas Backlund]

06.04.2012 14:25, Thomas Backlund skrev:
> 06.04.2012 13:52, Thomas Backlund skrev:
>> 06.04.2012 13:21, Funda Wang skrev:
>>> Hello,
>>>
>>> Could somebody pushing kde 4.8.2 into cauldron? So that we could test
>>> it in beta3? FYI, the pushing order is listed here:
>>> https://wiki.mageia.org/en/Packagers_KDE_SC_build#Build_Order_for_KDE_SC_4.8
>>>
>>> Regards.
>>
>> I'm on it.
>>
> 
> seems libkdcraw isn't updated in svn...
> 
> Submission errors, aborting:
> - libkdcraw-4.8.1-1.mga2.src:
>  - Current or newer revision(s) already exists in core/release for
> cauldron: libkdcraw-4.8.1-1.mga2.src
> 

And now all of KDE 4.8.2 is built and available on primary mirror.

--
Thomas

Re: [Mageia-dev] Release_blocker bugs

[Colin Guthrie]

'Twas brillig, and Maarten Vanraes at 06/04/12 16:43 did gyre and gimble:
> Op vrijdag 06 april 2012 13:17:46 schreef Anne nicolas:
> [...]
>> Does not seem to be release_blocker
>> ===
>> 4301 bugsq...@mageia.org Migration of module-init-tools to kmod lib in
>> Mageia 2 - specifications
>> => 4802
> [...]
> 
> i may understand this wrong, but iinm, module-init-tools doesn't work with 
> current kernel anymore, and kmod is now required => doublecheck with tmb

I'm not sure what the specifications specifically meant in this regard,
but we did used to have a lib made from module-init-tools which was then
used elsewhere. We've not dropped that lib, and now use libkmod directly
everywhere it's needed.

The only thing we've not done is to actually use the kmod binaries for
modprobe, insmod, rmmod, lsmod, etc.

That said, it's a simple switch in the kmod spec to turn it on (and
obsolite module-init-tools). I've mentioned this before, but no one
really picked up on it. It's very late in the day to do this switch
(although I have personally be running it for a while without any issues).

There was one issue regarding the kernel *bin depmods files and dracut
that someone reported as being due to that dracut was using kmod but the
kernel's *.bin files were created with m-i-t... I forget the details, so
not sure if it's an issue or not.

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] A note on autologin and startx

[Colin Guthrie]

Hi,

OK, so the autologin package was a bit broken. I've fixed it up but my
patches are a bit hacky.

My patch always assumes tty1+vt1 for X which is a reasonable assumption.
It might however be better to get the current tty by reading
/sys/class/tty/tty0/active or calling ctermid(). This would have to be
passed through to the startx command as a vt number.

Overall, however, the autologin code is pretty broken. I *should*
register a graphical login after starting X (the same way gdm does it),
that way it will remain active and there won't be vt switch related issues.


Also, as per previous discussions, I've made startx reuse the current
tty when starting x (if you don't supply a vtN argument) which should
keep the login permissions. It's still a bit fugly, but it's better than
not working at all IMO.

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] Release_blocker bugs

[Maarten Vanraes]

Op vrijdag 06 april 2012 13:17:46 schreef Anne nicolas:
[...]
> Does not seem to be release_blocker
> ===
> 4301  bugsq...@mageia.org Migration of module-init-tools to kmod lib in
> Mageia 2 - specifications
> => 4802
[...]

i may understand this wrong, but iinm, module-init-tools doesn't work with 
current kernel anymore, and kmod is now required => doublecheck with tmb

Re: [Mageia-dev] [changelog] [RPM] cauldron core/release perl-Math-BaseCnv-1.800.0-2.mga2

[Thierry Vignaud]

On 6 April 2012 16:49, Jerome Quelin  wrote:
>> what for?
>
> hmm, strange, since i issued the command:
>
>    rebuild "SILENT fix bad signature"
>
> which uses the first argument as commit msg...
>
> i guess it is because of SILENT - but aren't we supposed to use SILENT
> for those non-interesting messages?

If there's nothing else, it should be described.
Especially for a rebuild.

Re: [Mageia-dev] [changelog] [RPM] cauldron core/release perl-Math-BaseCnv-1.800.0-2.mga2

[Jerome Quelin]

On 12/04/06 16:35 +0200, Thierry Vignaud wrote:
> On 6 April 2012 15:58, jquelin  wrote:
> > jquelin  1.800.0-2.mga2:
> > + Revision: 229096
> > + rebuild (emptylog)
> 
> what for?

hmm, strange, since i issued the command:

rebuild "SILENT fix bad signature"

which uses the first argument as commit msg...

i guess it is because of SILENT - but aren't we supposed to use SILENT
for those non-interesting messages?

jérôme 

Re: [Mageia-dev] [changelog] [RPM] cauldron core/release perl-Math-BaseCnv-1.800.0-2.mga2

[Thierry Vignaud]

On 6 April 2012 15:58, jquelin  wrote:
> jquelin  1.800.0-2.mga2:
> + Revision: 229096
> + rebuild (emptylog)

what for?

Re: [Mageia-dev] Freeze push: KDE 4.8.2

[Thomas Backlund]

06.04.2012 13:52, Thomas Backlund skrev:
> 06.04.2012 13:21, Funda Wang skrev:
>> Hello,
>>
>> Could somebody pushing kde 4.8.2 into cauldron? So that we could test
>> it in beta3? FYI, the pushing order is listed here:
>> https://wiki.mageia.org/en/Packagers_KDE_SC_build#Build_Order_for_KDE_SC_4.8
>>
>> Regards.
> 
> I'm on it.
> 

seems libkdcraw isn't updated in svn...

Submission errors, aborting:
- libkdcraw-4.8.1-1.mga2.src:
 - Current or newer revision(s) already exists in core/release for
cauldron: libkdcraw-4.8.1-1.mga2.src

Re: [Mageia-dev] Freeze push: quagga

[nicolas vigier]

On Fri, 06 Apr 2012, Funda Wang wrote:

> Hello,
> 
> Could somebody pushing quagga 0.99.20.1 into cauldron? It is a
> security-fix release that addresses 3 pending CVEs, one in bgpd and
> two in ospfd.

Submitted.

Re: [Mageia-dev] [soft-commits] [3964] Fix partition numbering on GPT (mga#3091)

[Pascal Terjan]

On Fri, Apr 6, 2012 at 12:07, Pascal Terjan  wrote:

>
>
> On Fri, Apr 6, 2012 at 09:34, Guillaume Rousse wrote:
>
>>
>> What about using consistent variable names ? If you have a collection of
>> 'something' stored in a hash, why should it suddenly became of collection
>> of 'st' when transfering them into an array ?
>
>
> In this case, the hash contains the existing partitions, hence %parts,
> while the array represents the full partition table, hence @pt
>
> Or using a consistent format for variables storing numbers, rather than
>> having both nb_foo and bar_number ?
>>
>
> nb_primary is the number of primary partitions (count if you prefer),
> part_number is the position of a given partition in the table.
>
>
>>
>> And I don't underestand the interest of using an hash for storing content
>> with numerical indexes only. Especially if you have to convert it to an
>> array at the end...
>
>
> To easily get the (potential) one with current index when filling the
> array. The other solution would be to first create the array with 128
> default structures, then replace some of them.
>

Hmm or actually just put them in the array and then fill the holes

[Mageia-dev] Release_blocker bugs

[Anne nicolas]

Hi there

Here is a first review of release_blocker bugs. Please have a look, comment

Release Blocker (given the criteria defined during Packagers meeting)


Install
-
5044thierry.vign...@gmail.com   lilo failed commande introuvable .. sh
ligne 0 erreur d'ecriture / broken pipe
4696thierry.vign...@gmail.com   Install freeze after licence
acceptation (system without floppy disk in the drive) (error I/O fd0)

dracut
-
4298bugsq...@mageia.org [Tracker] Implement dracut in Mageia 2 -
specifications
=>   3315, release_blocker 4364 4562

Systemd
-
2120dmorga...@gmail.com [Tracker] Implement systemd in Mageia 2 -
specifications
=> 3253 3740 3744 3817 4177 4327 4541 4672  4910 5122 5143 5148 5184 ,
release_blocker 4772

Upgrade

3342bugsq...@mageia.org [Tracker] Upgrade Mga 1 > Mga 2
=>   4136 4150 4541 4569 5100 5103 5219

oxygen
--
5034bugsq...@mageia.org [TRACKER] Oxygen integration issues
=> 5132 non blocker

GNOME 3
---
4553o...@vitters.nl Gnome 3 starts in fallback mode after boot, but
Gnome Shell available after logout
4419o...@vitters.nl Change default background in gdm and default
gnome-sessions (shell+fallback)
4357thierry.vign...@gmail.com   [debloat] consider moving Suggests:
seahorse to task-gnome
3774bugsq...@mageia.org GNOME3 on free DVD? (requires non-free drivers)

Wifi
--
no release_blocker one but still wifi status is not good enough given
the number of bugs
5015bugsq...@mageia.org TRACKER: WLAN - WIFI not or badly working in 
cauldron
=> 1015 1452 1562 1806 2160 2372 3344 3398 3798 4046 4142 4635 4963

Security updates
=
To be closed after RC
5046bugsq...@mageia.org [Tracker] Security updates for Mageia 2

Live CDs
===
We are starting tests on new set of isos (pre release) and it seems
for now it's fixing blocker bugs opened on very first isos.

1812mag...@blino.orgClosing an "Advanced settings" window during
live-install quits the installer without warning
3212mag...@blino.orgmgaonline/update tries to perform update on a 
LiveCD
3621bugsq...@mageia.org [ 2 alpha1 ] LiveCD: missing desktop/menu
items for installing from the CD
3801mag...@blino.orgdrakx-finish-install doesn't set the root
password and dont create/migrate the live user

Others
==

4999bugsq...@mageia.org Mga2 Beta2 fails to boot fully into KDE
4772bugsq...@mageia.org boot hangs at 'Starting cpufreq (via systemctl)'
4645bugsq...@mageia.org udisks is not installed from x86-64 DVD
causing urpmi/rpmdrake to fail on first boot
4299bugsq...@mageia.org syslinux, gfxboot in Mageia 2
3803watersnowr...@gmail.com boot screen entries get corrupted when
switching between them, highlighting for selected and unselected items
not working properly
3375t...@iki.fi after hibernation system starts booting from scratch

Does not seem to be release_blocker
=== 
4301bugsq...@mageia.org Migration of module-init-tools to kmod lib in
Mageia 2 - specifications
=> 4802

4300bugsq...@mageia.org General artwork in Mageia 2 - specifications
=> 41 107 261 1919 3898 3900 4181 4269 4419 4651 4858 5049 5211 (no
release_blocker bug)




-- 
Anne
http://www.mageia.org

Re: [Mageia-dev] [soft-commits] [3964] Fix partition numbering on GPT (mga#3091)

[Pascal Terjan]

On Fri, Apr 6, 2012 at 09:34, Guillaume Rousse wrote:

>
> What about using consistent variable names ? If you have a collection of
> 'something' stored in a hash, why should it suddenly became of collection
> of 'st' when transfering them into an array ?


In this case, the hash contains the existing partitions, hence %parts,
while the array represents the full partition table, hence @pt

Or using a consistent format for variables storing numbers, rather than
> having both nb_foo and bar_number ?
>

nb_primary is the number of primary partitions (count if you prefer),
part_number is the position of a given partition in the table.


>
> And I don't underestand the interest of using an hash for storing content
> with numerical indexes only. Especially if you have to convert it to an
> array at the end...


To easily get the (potential) one with current index when filling the
array. The other solution would be to first create the array with 128
default structures, then replace some of them.

Re: [Mageia-dev] Freeze push: KDE 4.8.2

[Thomas Backlund]

06.04.2012 13:21, Funda Wang skrev:
> Hello,
> 
> Could somebody pushing kde 4.8.2 into cauldron? So that we could test
> it in beta3? FYI, the pushing order is listed here:
> https://wiki.mageia.org/en/Packagers_KDE_SC_build#Build_Order_for_KDE_SC_4.8
> 
> Regards.

I'm on it.

--
Thomas

[Mageia-dev] Freeze push: KDE 4.8.2

[Funda Wang]

Hello,

Could somebody pushing kde 4.8.2 into cauldron? So that we could test
it in beta3? FYI, the pushing order is listed here:
https://wiki.mageia.org/en/Packagers_KDE_SC_build#Build_Order_for_KDE_SC_4.8

Regards.

[Mageia-dev] Freeze push: quagga

[Funda Wang]

Hello,

Could somebody pushing quagga 0.99.20.1 into cauldron? It is a
security-fix release that addresses 3 pending CVEs, one in bgpd and
two in ospfd.

Thanks

Re: [Mageia-dev] [changelog] [RPM] cauldron core/release meta-task-2-36.mga2

[Thierry Vignaud]

On 6 April 2012 11:39, Luc Menut  wrote:
>>> - replace various kde4 handbooks by task-kde4-handbooks-dvd in INSTALL
>>
>>
>> This is wrong IMHO.
>> that only make sure there on the ISOs.
>
>
> This is what I wish.
> The needed handbooks will be installed by suggests, according to kde's
> components selected at install time.
> cf. http://thread.gmane.org/gmane.linux.mageia.user/6342
>
>
>> This is intended for stuff that are not picked by anything else by that
>> the
>> installer would pick according do detected hardware.
>> I even documented this in rpmsrate.
>> This is obviously not the case here.
>>
>
> Is there a better solution?

No it's fine.
I now understand what you wanted.

Re: [Mageia-dev] [changelog] [RPM] cauldron core/release meta-task-2-36.mga2

[Luc Menut]

Le 06/04/2012 10:06, Thierry Vignaud a écrit :

On 6 April 2012 00:27, lmenut  wrote:

lmenut  1:2-36.mga2:
+ Revision: 228815
- base the kde install on task-kde4-minimal instead of task-kde4


OK


  - remove meta-packages kdeaccessibility4 kdeedu4 kdegames4 kdesdk4
  - cherry pick components to install for non live kde
- move kmail in CAT_NETWORKING_MAIL
- move akregator in CAT_NETWORKING_NEWS
- remove calligra


B/c libreoffice is already here?


Yes, and iso size constraint.
(previously calligra wasn't installed by default)




- replace various kde4 handbooks by task-kde4-handbooks-dvd in INSTALL


This is wrong IMHO.
that only make sure there on the ISOs.


This is what I wish.
The needed handbooks will be installed by suggests, according to kde's 
components selected at install time.

cf. http://thread.gmane.org/gmane.linux.mageia.user/6342


This is intended for stuff that are not picked by anything else by that the
installer would pick according do detected hardware.
I even documented this in rpmsrate.
This is obviously not the case here.



Is there a better solution?


regards,
Luc


--
Luc Menut

Re: [Mageia-dev] [soft-commits] [3964] Fix partition numbering on GPT (mga#3091)

[Guillaume Rousse]

Le 06/04/2012 10:53, Thierry Vignaud a écrit :

On 6 April 2012 10:34, Guillaume Rousse  wrote:

Anyway, allocating the list content in a single pass seems simpler to
understand for me. I'd rather use something as:

# create an exhaustive list including %parts content if existing
# for given partition number, a default structure otherwise
my @pt = map {
$parts{$_} ? $parts{$_} : { part_number =>  $_ }
} 1..$nb_primary;


even simpler:
$parts{$_} || { part_number =>  $_ }

caramba :)

Re: [Mageia-dev] [soft-commits] [3964] Fix partition numbering on GPT (mga#3091)

[Thierry Vignaud]

On 6 April 2012 10:34, Guillaume Rousse  wrote:
> Anyway, allocating the list content in a single pass seems simpler to
> understand for me. I'd rather use something as:
>
> # create an exhaustive list including %parts content if existing
> # for given partition number, a default structure otherwise
> my @pt = map {
>        $parts{$_} ? $parts{$_} : { part_number => $_ }
>    } 1..$nb_primary;

even simpler:
   $parts{$_} || { part_number => $_ }

Re: [Mageia-dev] [soft-commits] [3964] Fix partition numbering on GPT (mga#3091)

[Guillaume Rousse]

Le 06/04/2012 09:58, Thierry Vignaud a écrit :

On 6 April 2012 00:00,  wrote:

Fix partition numbering on GPT (mga#3091)


(...)


@@ -27,9 +28,20 @@
  $p{start} = $5;
  $p{size} = $7;
  }
-\%p;
+$p{part_number} =>  \%p;
  } c::get_disk_partitions($hd->{file});

+my @pt = map {
+   my $part_number = $_;
+   if ($parts{$part_number}) {
+   $parts{$part_number};
+   } else {
+   my %p;
+   $p{part_number} = $part_number;
+   \%p;


This is simpler&  more readable:

{ part_number =>  $part_number };

anyway it would be maybe simpler go one of the way I attach.
WDYT?
I like the 'simpler' adjective when I have to read this stuff at least 3 
times to get an idea of what it happening... A simple comment wouldn't 
hurt there.


Anyway, allocating the list content in a single pass seems simpler to 
understand for me. I'd rather use something as:


# create an exhaustive list including %parts content if existing
# for given partition number, a default structure otherwise
my @pt = map {
$parts{$_} ? $parts{$_} : { part_number => $_ }
} 1..$nb_primary;

More general remarks:

What about using consistent variable names ? If you have a collection of 
'something' stored in a hash, why should it suddenly became of 
collection of 'st' when transfering them into an array ? Or using a 
consistent format for variables storing numbers, rather than having both 
nb_foo and bar_number ?


And I don't underestand the interest of using an hash for storing 
content with numerical indexes only. Especially if you have to convert 
it to an array at the end...


--
BOFH excuse #79:

Look, buddy:  Windows 3.1 IS A General Protection Fault.

Re: [Mageia-dev] net-snmp doesnt report cpu ussage correctly

[Thierry Vignaud]

On 4 April 2012 07:54, Luis Daniel Lucio Quiroz  wrote:
> i did compare packages, and i realiza that in mdv we have this line
> mibs BAYOUR-COM-MIB:UCD-SNMP-MIB
>
> in snmp.local.conf, but copying it in mga2 it doesnt fix this isssue.  I'vent
> test with mga1.
>
> Dont you know anything about this?

Please open a bug report in http://bugs.mageia.org

Re: [Mageia-dev] [changelog] [RPM] cauldron core/release meta-task-2-36.mga2

[Thierry Vignaud]

On 6 April 2012 00:27, lmenut  wrote:
> lmenut  1:2-36.mga2:
> + Revision: 228815
> - base the kde install on task-kde4-minimal instead of task-kde4

OK

>  - remove meta-packages kdeaccessibility4 kdeedu4 kdegames4 kdesdk4
>  - cherry pick components to install for non live kde
> - move kmail in CAT_NETWORKING_MAIL
> - move akregator in CAT_NETWORKING_NEWS
> - remove calligra

B/c libreoffice is already here?

> - replace various kde4 handbooks by task-kde4-handbooks-dvd in INSTALL

This is wrong IMHO.
that only make sure there on the ISOs.
This is intended for stuff that are not picked by anything else by that the
installer would pick according do detected hardware.
I even documented this in rpmsrate.
This is obviously not the case here.

> - install plasma-applet-kimpanel-backend-ibus for the same languages than 
> ibus-qt4
> - prefer plasma-applet-kimpanel-backend-ibus over 
> plasma-applet-kimpanel-backend-scim
> - add vlc in CAT_VIDEO for non live
> - remove iceape
>
>  + ennael 
>    - add task-obsolete

BTW we should update release notes in mageia-release

Re: [Mageia-dev] [soft-commits] [3964] Fix partition numbering on GPT (mga#3091)

[Thierry Vignaud]

On 6 April 2012 00:00,   wrote:
> Fix partition numbering on GPT (mga#3091)

(...)

> @@ -27,9 +28,20 @@
>  $p{start} = $5;
>  $p{size} = $7;
>  }
> -\%p;
> +$p{part_number} => \%p;
>  } c::get_disk_partitions($hd->{file});
>
> +my @pt = map {
> + my $part_number = $_;
> + if ($parts{$part_number}) {
> + $parts{$part_number};
> + } else {
> + my %p;
> + $p{part_number} = $part_number;
> + \%p;

This is simpler & more readable:

{ part_number => $part_number };

anyway it would be maybe simpler go one of the way I attach.
WDYT?

> [ @pt ], $info;


And this could be better:

\@pt, $info;

BTW, a "require common" would be needed b/c of common::sync() even
if all users already loaded it before, for sanity & perl_checker.


1.diff
Description: Binary data


2.diff
Description: Binary data

Re: [Mageia-dev] [soft-commits] [3971] use ~/tmp for gfxboot tempdir

[Guillaume Rousse]

Le 06/04/2012 01:25, D.Morgan a écrit :

On Fri, Apr 6, 2012 at 1:16 AM,  wrote:

Revision 3971 Author tmb Date 2012-04-06 01:16:54 +0200 (Fri, 06 Apr 2012)

Log Message

use ~/tmp  for gfxboot tempdir

Modified Paths

draklive/trunk/draklive

Modified: draklive/trunk/draklive
===
--- draklive/trunk/draklive 2012-04-05 23:14:31 UTC (rev 3970)
+++ draklive/trunk/draklive 2012-04-05 23:16:54 UTC (rev 3971)
@@ -576,7 +576,7 @@
  -f $bootlogo or return;

  my $cwd = Cwd::getcwd();
-my $tempdir = File::Temp::tempdir("mdvgfxboot", CLEANUP =>  1);
+my $tempdir = File::Temp::tempdir("tmp/mdvgfxboot", CLEANUP =>  1);


maybe this should be changed to "tmp/mgagfxboot"   WDYT ?
This is a temporary file, the name doesn't really matter. And the commit 
message was wrong: you cannot ensure ~/tmp directory is used with this 
change, you're just forcing the use of a 'tmp' subdirectory insid the 
writable directory used selectionned by File::Temp module.


--
BOFH excuse #187:

Reformatting Page. Wait...

[Mageia-dev] Latest upgrade testing

[David W. Hodgins]

I think developers may be interested in the latest
qa testing of upgrading from Mageia 1 to Caulron.

Check out https://forums.mageia.org/en/viewtopic.php?f=4&t=2187

Regards Dave Hodgins