Re: [Mageia-dev] [changelog] [RPM] cauldron nonfree/release radeon-firmware-20120322-1.mga2.nonfree

[Anssi Hannula]

23.03.2012 00:54, Jeff Robins kirjoitti:
> On Thu, Mar 22, 2012 at 2:36 PM, Thomas Backlund  wrote:
>> I'm not sure I want to "intentionally break" working systems as it would
>> also hit users that remove the radeon-firmware rpm by mistake...
> 
> Will this cause a problem if someone installs the AMD Catalyst drivers?

Nope, it shouldn't make a difference.

> Otherwise, I tend to agree.  At least until the missing radeon
> firmware bug is fixed.


-- 
Anssi Hannula

Re: [Mageia-dev] Please push

[David Walser]

Maarten Vanraes wrote:
> Op donderdag 22 maart 2012 05:36:47 schreef Thomas Spuhler:
>> Please push php-apacheaccessor
>> 
>> I upgraded it in svn to 0.1.1 in Dec. 2011, but it either didn't build or I
>> forgot to submit it.
> 
> i'm pretty sure the requirements for freeze pushes are also at least that you 
> must know it builds and works perfectly, on top of that it usually needs to 
> be 
> only bugfixes, or due to client/server changes that it is required...
> 
> plz add more info to this request

There is a bug fix in it, actually.  The manual httpd restart has been removed 
in favor of 
filetriggers.  At this particular time, if these manual restarts are left in, 
there can be breaking 
of httpd for people doing live upgrades with urpmi.  Please let this one go 
through.

Re: [Mageia-dev] installing minimal is not really that minimal

[Maarten Vanraes]

Op donderdag 22 maart 2012 19:04:07 schreef Maarten Vanraes:
> Op donderdag 22 maart 2012 17:57:29 schreef Thomas Backlund:
> [...]
> 
> > Installer already have a option to select "do not install suggests"
> 
> and it does...
> 
> that's exactly what i stated in my original email...
> 
> PEOPLE ARE HIJACKING MY THREAD!!!

of course, this was a joke at the time...

but i should've known better...

it appears the "no suggests option" is broken, since i did minimal install, 
with and without this, and i have exactly the same system...

both times i have messages in ddebug.log saying: "... as suggested by ..."

:-(

can someone fix this one?

Re: [Mageia-dev] installing minimal is not really that minimal

[Maarten Vanraes]

Op donderdag 22 maart 2012 00:30:53 schreef Maarten Vanraes:
[...]

in a chroot, i did a test with requiring plymouth or suggesting it (from 
dracut)

the difference is:

with plymouth: 301 packages/335MB
without plymouth: 294 packages/294MB

i'm gonna try a minimal install and see how much this'll differ

Re: [Mageia-dev] Tonight's meeting

[Johnny A. Solbu]

On Thursday 22 March 2012 03:06, Thomas Spuhler wrote:
> I am a packager, but I have never been able to attend any of the meetings 
> because they are conducted during a time I really need to be at work.

I have the same problem. Real life events prevents me from attending every 
second wednesday. I also, during the summer I can't attend a single wednesday, 
for the next few years.
If there where to be a reschedule to another day, for me the fridays are also a 
busy day, as I'm part of a team that run PA sound and light mixers at 
youthmeetings, which I've been doing for the last 18 years.

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


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

Re: [Mageia-dev] please push libnetfilter_queue

[Luis Daniel Lucio Quiroz]

The fact is Im fixing snort, snort uses daq, and daq uses libnetfilter_queue.  
So i was expecting to place all dependencies up to date

Enviado desde mi teléfono Verizon Wireless

-Mensaje original-
De: Pascal Terjan 
Para: Mageia development mailing-list 
Enviado: vie, mar 23, 2012 00:40:37 GMT+00:00
Asunto: Re: [Mageia-dev] please push libnetfilter_queue

On Thu, Mar 22, 2012 at 13:49, Luis Daniel Lucio Quiroz
wrote:

> On Jue 22 Mar 2012 07:41:02 Anne Nicolas escribió:
> > Le 22/03/2012 14:38, Luis Daniel Lucio Quiroz a écrit :
> > > Helo
> > >
> > > Please push libnetfilter_queue, it updates from 1.0.0 to 1.0.1
> > >
> > > LD
> >
> > Reasons...
>
> I'm not a kernel developer, here it is the changelog
>
> https://git.netfilter.org/cgi-bin/gitweb.cgi?p=libnetfilter_queue.git;a=shortlog
>
> There are more than 18 months of difference between 1.0.0 and 1.0.1, I
> guess
> since this is a kernel matter, 18 months ago we were using 2.6, now 3.3.


Looking at the changes, it seems safe to update but there is also no real
reason to do so...
Only real change is
https://git.netfilter.org/cgi-bin/gitweb.cgi?p=libnetfilter_queue.git;a=commit;h=1154021c599257edf2c3dcb4d29f6b4dcb67643a
Other changes are doc or build changes + licence change to GPLv2+

Email Shield provided by NOCWorldWide.com

Re: [Mageia-dev] please push libnetfilter_queue

[Pascal Terjan]

On Thu, Mar 22, 2012 at 13:49, Luis Daniel Lucio Quiroz
wrote:

> On Jue 22 Mar 2012 07:41:02 Anne Nicolas escribió:
> > Le 22/03/2012 14:38, Luis Daniel Lucio Quiroz a écrit :
> > > Helo
> > >
> > > Please push libnetfilter_queue, it updates from 1.0.0 to 1.0.1
> > >
> > > LD
> >
> > Reasons...
>
> I'm not a kernel developer, here it is the changelog
>
> https://git.netfilter.org/cgi-bin/gitweb.cgi?p=libnetfilter_queue.git;a=shortlog
>
> There are more than 18 months of difference between 1.0.0 and 1.0.1, I
> guess
> since this is a kernel matter, 18 months ago we were using 2.6, now 3.3.


Looking at the changes, it seems safe to update but there is also no real
reason to do so...
Only real change is
https://git.netfilter.org/cgi-bin/gitweb.cgi?p=libnetfilter_queue.git;a=commit;h=1154021c599257edf2c3dcb4d29f6b4dcb67643a
Other changes are doc or build changes + licence change to GPLv2+

Re: [Mageia-dev] please push libnetfilter_queue

[Luis Daniel Lucio Quiroz]

Allors?

Enviado desde mi teléfono Verizon Wireless

-Mensaje original-
De: Luis Daniel Lucio Quiroz 
Para: Mageia development mailing-list 
Enviado: jue, mar 22, 2012 13:50:44 GMT+00:00
Asunto: Re: [Mageia-dev] please push libnetfilter_queue

On Jue 22 Mar 2012 07:41:02 Anne Nicolas escribió:
> Le 22/03/2012 14:38, Luis Daniel Lucio Quiroz a écrit :
> > Helo
> > 
> > Please push libnetfilter_queue, it updates from 1.0.0 to 1.0.1
> > 
> > LD
> 
> Reasons...

I'm not a kernel developer, here it is the changelog
https://git.netfilter.org/cgi-bin/gitweb.cgi?p=libnetfilter_queue.git;a=shortlog

There are more than 18 months of difference between 1.0.0 and 1.0.1, I guess 
since this is a kernel matter, 18 months ago we were using 2.6, now 3.3.

LD
Email Shield provided by NOCWorldWide.com

[Mageia-dev] New security issues affect libzip and php (freeze push will be needed)

[David Walser]

New vulnerabilities CVE-2012-1162 (heap overflow) and CVE-2012-1163 (integer 
overflow) in libzip, which also affect PHP (probably the php-zip subpackage) 
were recently announced.

libzip 0.10.1 has been released to fix these.  I have updated it in SVN and 
confirmed it builds, but I have not tested it yet.

PHP has not yet issued an update for this.

References:
https://bugs.mageia.org/show_bug.cgi?id=5063
http://seclists.org/oss-sec/2012/q1/710
https://bugzilla.redhat.com/show_bug.cgi?id=802564
https://bugzilla.redhat.com/show_bug.cgi?id=803028

Re: [Mageia-dev] [push] gstreamer0.10-plugins-ugly

[Dimitri Jakov]

The corresponding bug is: https://bugs.mageia.org/show_bug.cgi?id=4830

If the build fails, please save build logs somewhere (or just send them
to me) so that we can analyze them afterwards.

Mitya

Re: [Mageia-dev] installing minimal is not really that minimal

[Maarten Vanraes]

Op vrijdag 23 maart 2012 00:44:09 schreef Pascal Terjan:
[...]
> next:
> > - lib64pam0
> > - bootsplash
> > 
> > am i missing something, i have the feeling there's another file that has
> > effect
> > to these stuff?
> 
> Well all the packages have plenty of dependencies...

bootsplash is a good thing to look for:

see the relevant part of ddebug.log: http://paste.pocoo.org/show/569781/

look for bootsplash, it gets selected, but never chosen nor required, but it's 
somehow there... and it should need CAT_X... to get selected...

also see that the lib64drm_radeon1 is the very first in the ddebug.log...? why 
first? somehow it's been preselected, but it's not even in rpmsrate...

[Mageia-dev] [push] gstreamer0.10-plugins-ugly

[Dimitri Jakov]

Please somebody push gstreamer0.10-plugins-ugly to tainted/release, it
seems to be out of sync with core/release. Thanks!

Mitya

Re: [Mageia-dev] installing minimal is not really that minimal

[Pascal Terjan]

On Thu, Mar 22, 2012 at 23:33, Maarten Vanraes  wrote:

> Op donderdag 22 maart 2012 00:30:53 schreef Maarten Vanraes:
> > i did a network install
> >
> > and choose 'custom', then deselected everything, pressed next
> >
> > i got to the next menu of installation and left these to default:
> >
> >  - no X
> >  - no suggestions
> >  - basic doc still on
> >  - truly minimal was off
> >
> > but, i ended up with x libraries, fonts, etc...
> >
> > so i dug a bit deeper as to why and looked at the ddebug.log file:
>
> i looked once more, after the choose packages step:
>
> these are the categories selected:
>
> CAT_MINIMAL_DOCS
> CAT_SYSTEM
> CHARSET"C"
> LOCALES"en"
> LOCALES"_"
> LOCALES"en_US"
> META_CLASS"download"
> TRUE
> USB
> UTF8
>
> this should be:
> man info man-pages eject ldetect harddrake sharutils locales iputils urpmi
> tmpwatch dmidecode ntfs-3g pm-utils numlock lftp mageia-release-Default
>
> + basesystem-minimal at least


> these should result in a selection of 235 packages (i tried to track these
> manually through the rpmsrate file
>
> however, somehow other packages seem to be getting extra installed anyway
> (during the choosePackages step)!
>
> first package being selected is:
>
> - lib64drm_radeon1 ... even in rpmsrate radeon-firmware (the closest thing
> i
> can imagine), needs CAT_X 
>

Hard to say without the full list
I would guess plymouth got selected or maybe lsl-lib64

plymouth requires libdrm_radeon.so.1
lsb-lib64 rquires lib64mesagl1 which requires lib64dri-drivers which
requires libdrm_radeon.so.1

next:
> - lib64pam0
> - bootsplash
>
> am i missing something, i have the feeling there's another file that has
> effect
> to these stuff?
>

Well all the packages have plenty of dependencies...

Re: [Mageia-dev] installing minimal is not really that minimal

[Maarten Vanraes]

Op donderdag 22 maart 2012 00:30:53 schreef Maarten Vanraes:
> i did a network install
> 
> and choose 'custom', then deselected everything, pressed next
> 
> i got to the next menu of installation and left these to default:
> 
>  - no X
>  - no suggestions
>  - basic doc still on
>  - truly minimal was off
> 
> but, i ended up with x libraries, fonts, etc...
> 
> so i dug a bit deeper as to why and looked at the ddebug.log file:

i looked once more, after the choose packages step:

these are the categories selected:

CAT_MINIMAL_DOCS
CAT_SYSTEM
CHARSET"C"
LOCALES"en"
LOCALES"_"
LOCALES"en_US"
META_CLASS"download"
TRUE
USB
UTF8

this should be:
man info man-pages eject ldetect harddrake sharutils locales iputils urpmi 
tmpwatch dmidecode ntfs-3g pm-utils numlock lftp mageia-release-Default


these should result in a selection of 235 packages (i tried to track these 
manually through the rpmsrate file

however, somehow other packages seem to be getting extra installed anyway 
(during the choosePackages step)!

first package being selected is:

- lib64drm_radeon1 ... even in rpmsrate radeon-firmware (the closest thing i 
can imagine), needs CAT_X 

next:
- lib64pam0
- bootsplash

am i missing something, i have the feeling there's another file that has effect 
to these stuff?

Re: [Mageia-dev] Freeze push: foomatic-filters

[David Walser]

Florian Hubold  writes:
> Am 20.03.2012 10:36, schrieb David Walser:
> > Minor foomatic-filters update (4.0.14) contains just one change, should be
safe to go in:
> > * foomaticrip.c: If the input data is PDF but the driver requires
> >   PostScript, use the pdftops CUPS filter when CUPS is the spooler.
> >   This way we always use the same method to convert PDF to PostScript
> >   in the whole system, including any workarounds applied in the CUPS
> >   filter.
> >
> > Confirmed that it builds and installs fine locally.
> >
> >
> Well, does it also work just fine?

Yes.  Thanks for asking and sorry I didn't mention it earlier.

I tested this at work printing PDFs to a printer configured to use PostScript
and it works fine.

Re: [Mageia-dev] [changelog] [RPM] cauldron nonfree/release radeon-firmware-20120322-1.mga2.nonfree

[Jeff Robins]

On Thu, Mar 22, 2012 at 2:36 PM, Thomas Backlund  wrote:
> I'm not sure I want to "intentionally break" working systems as it would
> also hit users that remove the radeon-firmware rpm by mistake...

Will this cause a problem if someone installs the AMD Catalyst drivers?

Otherwise, I tend to agree.  At least until the missing radeon
firmware bug is fixed.

--Jeff

Re: [Mageia-dev] Latest kernels vs IDE/libata

[Thomas Backlund]

Anssi Hannula skrev 22.3.2012 23:33:


Note that it was/is untested (forgot to mention that). So please check
locally first before submitting that it doesn't completely break
everything :)
Though I guess you already test your kernels...



Yep :)

--
Thomas

Re: [Mageia-dev] [changelog] [RPM] cauldron nonfree/release radeon-firmware-20120322-1.mga2.nonfree

[Thomas Backlund]

Jeff Robins skrev 22.3.2012 23:27:

Thomas,

Does this fix bug 5018 (https://bugs.mageia.org/show_bug.cgi?id=5018)?
  Bugzilla says the bug is still open.



Nope.

I'm not sure I want to "intentionally break" working systems as it would 
also hit users that remove the radeon-firmware rpm by mistake...


--
Thomas

Re: [Mageia-dev] Latest kernels vs IDE/libata

[Anssi Hannula]

22.03.2012 23:30, Thomas Backlund kirjoitti:
> Anssi Hannula skrev 22.3.2012 22:35:
>>
>> I'm not sure how it worked previously (hack in mkinitrd, or luck?), but
>> if we don't want to disable the IDE drivers completely, attached is a
>> kernel patch that makes modprobe load ATA drivers before IDE drivers.
>>
>> Thomas?
>>
> 
> ACK.
> 
> Committed to svn, thanks.

OK.

Note that it was/is untested (forgot to mention that). So please check
locally first before submitting that it doesn't completely break
everything :)
Though I guess you already test your kernels...

-- 
Anssi Hannula

Re: [Mageia-dev] Latest kernels vs IDE/libata

[Thomas Backlund]

Anssi Hannula skrev 22.3.2012 22:35:


I'm not sure how it worked previously (hack in mkinitrd, or luck?), but
if we don't want to disable the IDE drivers completely, attached is a
kernel patch that makes modprobe load ATA drivers before IDE drivers.

Thomas?



ACK.

Committed to svn, thanks.


--
Thomas

Re: [Mageia-dev] [changelog] [RPM] cauldron nonfree/release radeon-firmware-20120322-1.mga2.nonfree

[Jeff Robins]

Thomas,

Does this fix bug 5018 (https://bugs.mageia.org/show_bug.cgi?id=5018)?
 Bugzilla says the bug is still open.

Thank you,

Jeff

[Mageia-dev] Bug off!

[Remco Rijnders]

In order to reach as wide a target audience as we have in mind with it, 
please find below a courtesy copy of the latest blog post.


http://blog.mageia.org/en/2012/03/22/bug-off/
===

The past months, Mageia has been hard at work getting Alpha and Beta 
releases out for our upcoming release Mageia 2. With Beta 2 out of the 
door, and the release candidate on the way, it is time to reflect for a 
moment on our current situation.


A lot of hard work has been done by a lot of people. Developers, QA & and 
triaging teams, and not in the least beta testers have worked hard to 
improve our distribution to the best of our abilities and to ensure that 
Mageia 2 will become a release for everyone to enjoy.


During the testing, a number of bugs have been found which have been 
marked as release blockers. While we are hard at work on resolving them, 
there still is a lot to be done, and we can’t release while any release 
blocking bugs are still outstanding.


To this end, we’d like to invite everyone to participate in Mageia’s first 
bug squashing party!


The bug squash party will take place this weekend from friday 4 PM CET, to 
monday 10 PM CEST in #mageia-bugsquad on the Freenode IRC network.


We invite you to join in during this weekend to help us fix as many bugs 
as we can! Everyone can help! If you are a packager, we encourage you to 
get outside of your comfortzone and also have a look for example at 
installer bugs, wifi bugs, systemd issues, and so on! As end user you can 
help as well, we are still looking at increasing testing coverage to see 
if we catch all major issues before going gold with our release. Some bugs 
only manifest themselves on certain hardware profiles… if your computer is 
affected by one of these bugs, we especially appreciate your availability 
to help with testing to see if we can squeeze those nasty bugs!


Over the weekend, we will have a special page on our wiki where we will 
track the status of all issues we’re working on, as well as a daily update 
of our progress and work outstanding on the mailinglists -discuss and 
-dev.


We hope to see you on IRC in #mageia-bugsquad this weekend to help us make 
Mageia even better and make Mageia 2 a rock solid release!


Mageia Triage Team


pgpA7ieJnsovX.pgp
Description: PGP signature

Re: [Mageia-dev] [changelog] [RPM] cauldron nonfree/release radeon-firmware-20120322-1.mga2.nonfree

[Thomas Backlund]

Pascal Terjan skrev 22.3.2012 23:08:

On Thu, Mar 22, 2012 at 11:39, tmb mailto:buildsystem-dae...@mageia.org>> wrote:

Name: radeon-firmware  Relocations: (not
relocatable)
Version : 20120322  Vendor: Mageia.Org
Release : 1.mga2.nonfreeBuild Date: Thu Mar 22


[...]


    tmb  20120322-1.mga2:


It conflicts with kernel-firmware < %{version}-1 and kernel-firmware is
currently 20120219


Doh, forgot about that...

Fixed in 20120322-2.mga2

Thanks for noticing.

--
Thomas

Re: [Mageia-dev] [changelog] [RPM] cauldron nonfree/release radeon-firmware-20120322-1.mga2.nonfree

[Pascal Terjan]

On Thu, Mar 22, 2012 at 11:39, tmb  wrote:

> Name: radeon-firmware  Relocations: (not relocatable)
> Version : 20120322  Vendor: Mageia.Org
> Release : 1.mga2.nonfreeBuild Date: Thu Mar 22
> 12:39:11 2012
> Install Date: (not installed)   Build Host: jonund.mageia.org
> Group   : System/Kernel and hardwareSource RPM: (none)
> Size: 56508License: Freeware
> Signature   : (none)
> Packager: tmb 
> URL : http://ati.amd.com/
> Summary : ATI/AMD Radeon firmware files
> Description :
> Firmware files for ATI/AMD Radeon graphics cards.
>
> This package contains all the firmware files (including RLC) for the
> following Radeon series: R100, R200, R300, R400, R500, R600, R700,
> Evergreen, Fusion, Northern Islands, Southern Islands, Cayman, Llano,
> Trinity.
>
> tmb  20120322-1.mga2:
>

It conflicts with kernel-firmware < %{version}-1 and kernel-firmware is
currently 20120219

Re: [Mageia-dev] lighttpd and others now require apache

[Anssi Hannula]

20.03.2012 18:48, Guillaume Rousse kirjoitti:
> Le 17/03/2012 03:22, Anssi Hannula a écrit :
>> Hence I suggest a single user id to be used. (I'm fine with any other
>> solution which works as well)
> My main concern is the fuzziness of the current situation where we have
> - one virtual package 'webserver' corresponding to four implementations
> (apache, lightpd, nginx, cherooke)
> - one common base (webserver-base) only used by the two first ones
> - all our web applications packages using 'apache' as mandatory dependency
> 
> If the main concern is file ownership, I'd propose for the next release
> to have each of these servers use a distinct uid, document root and
> index page, but use a shared 'webserver' or 'www' gid, and ensure all of
> those applications use group-based permission, instead of user-based.
> I'd find this setup a bit clearer.

I'd rather they all use the traditional document root "/var/www/html",
but I don't really care much as long as the webapps are usable with both
apache and lighttpd.

I'm not sure if all webapps can easily work with group-based
permissions, but maybe they do (I don't know much about them)...

-- 
Anssi Hannula

Re: [Mageia-dev] freeze push: drakx-net

[Anne Nicolas]

Le 22/03/2012 21:37, Thierry Vignaud a écrit :
> Hi
> 
> Please let in drakx-net:
> 
> - fix CRDA never set to 'US' when country not in CRDA domains
>   (might help #1015 & the like)
> - fix bogus messages about 3rd party drivers
> - drakfirewall:
>   o fix listing NFS ports
>   o fix cleaning old rules
> - nfs: add .conf suffix to lockd.drakx file in /etc/modprobe.d
> 
> See you

submitted

-- 
Anne
http://mageia.org

Re: [Mageia-dev] Latest kernels vs IDE/libata

[Anssi Hannula]

20.03.2012 10:50, JA Magallón kirjoitti:
> Hi all...
> 
> I have a queston about an issue that should be decided by the 'thinkin
> minds' in the distro, that probably have have wider sight than me...
> 
> I have some boxes with ide disks, that long tine ago were driven by
> the libata subsystem, as the pure PATA susbsytem is being slowly
> deprecated. Perhaps the kernel driver loading priorities have changed,
> perhaps before IDE was not builtin into kernel.
> But now, to get my IDE drove again by libata, I have to blacklist
> generic-ide and company.
> So I had to put a file ide.conf into modules.d like:
> 
> blacklist ide-generic
> blacklist ide-pci-generic
> blacklist piix
> 
> so ata_piix drives my ICH5 again.
> 
> I think it is desirable, libata works much better than old IDE driver,
> all your drives are sdX, instead of mixing sdX for SATA and hdX for PATA,
> etc...
> 
> Would it be desirable to have an ide-blacklist.conf file just to go
> migrating all working-ok-with-libata controllers to libata, and only
> leave pure PATA drivers for non supported oldies ?

I'm not sure how it worked previously (hack in mkinitrd, or luck?), but
if we don't want to disable the IDE drivers completely, attached is a
kernel patch that makes modprobe load ATA drivers before IDE drivers.

Thomas?

-- 
Anssi Hannula
>From 9f04e51293b130474504216a477bb2a73cbf59e1 Mon Sep 17 00:00:00 2001
From: Anssi Hannula 
Date: Thu, 22 Mar 2012 22:29:11 +0200
Subject: [PATCH] ata: prefer ata drivers over ide drivers when both are built

Currently the old IDE drivers are preferred over ATA drivers when both
are built, since ide/ is listed first in drivers/Makefile and therefore
the IDE drivers end up before ATA drivers in modules.order which is used
by depmod/modprobe for module ordering.

Change it so that ATA drivers are preferred over IDE driver by moving
the ide/ entry under ata/ in drivers/Makefile.

Signed-off-by: Anssi Hannula 
---
 drivers/Makefile |2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/Makefile b/drivers/Makefile
index 932e8bf..e8df3d0 100644
--- a/drivers/Makefile
+++ b/drivers/Makefile
@@ -47,9 +47,9 @@ obj-$(CONFIG_PARPORT)		+= parport/
 obj-y+= base/ block/ misc/ mfd/ nfc/
 obj-$(CONFIG_NUBUS)		+= nubus/
 obj-y+= macintosh/
-obj-$(CONFIG_IDE)		+= ide/
 obj-$(CONFIG_SCSI)		+= scsi/
 obj-$(CONFIG_ATA)		+= ata/
+obj-$(CONFIG_IDE)		+= ide/
 obj-$(CONFIG_TARGET_CORE)	+= target/
 obj-$(CONFIG_MTD)		+= mtd/
 obj-$(CONFIG_SPI)		+= spi/
-- 
1.7.9.3

[Mageia-dev] Freeze push: autojump

[Samuel Verschelde]

Hi,

Please push if possible autojump. I thought I had committed and submitted it 
already weeks ago but it looks like I forgot (only uploaded the tar.gz).

Changes from versions 17 to 19 include mainly fixes. Unfortunately there is a 
new feature, so it's not a bugfix-only release, but it doesn't change user 
habits.

If the push is refused, then I'll try to backport some fixes, but given the 
non-criticity of the package and the unlikeliness of big regressions (I've 
been using it locally without any problem for some weeks), I would not be 
against having more time for more important matters :)

Best regards

Samuel Verschelde

Re: [Mageia-dev] Tonight's meeting

[zezinho]

Em 22-03-2012 03:06, Thomas Spuhler escreveu:

I am a packager, but I have never been able to attend any of the meetings
because they are conducted during a time I really need to be at work.
  Well, it may not that important, but it helps team building.
Could we consider to hold some of these meetings at a weekend?



+1 (could only attend 1 time because of real life)

Re: [Mageia-dev] rescue has mount.nfs, but no statd

[Maarten Vanraes]

Op donderdag 22 maart 2012 10:14:27 schreef Maarten Vanraes:
> at $dayjob, we're testing out the rescue.
> 
> so at first we're doing an rsync, but we need to do it on a network disk.
> 
> cifs was not available, but that's not a big issue.
> 
> nfs was available, so we wanted to mount
> 
> but the mount failed, because nfs module wasn't modprobed, and drvinst
> didn't fix that (maybe it should modprobe nfs as well)
> 
> or maybe mount.nfs should try to modprobe nfs if needed.
> 
> however, statd wasn't there and it complained that it needed that for
> locking
> 
> atm we're doing -o nolock and that works... but... statd would be quite
> usefull here...

perhaps i should rephrase...

can i fix this by adding statd on the rescue? or would this take too much 
space?

plz advise...

Re: [Mageia-dev] Mageia on Raspberry-Pi (ARM port)

[Colin Guthrie]

'Twas brillig, and brett at 22/03/12 15:12 did gyre and gimble:
>>>iinm we're actually still starting it up... contact rtp for more info
> regarding this.
> 
> Can you please expand rtpI don't know what that stands for.

rtp is his IRC nick name :)

rtp = Arnaud Pitard

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] installing minimal is not really that minimal

[Maarten Vanraes]

Op donderdag 22 maart 2012 17:57:29 schreef Thomas Backlund:
[...]
> Installer already have a option to select "do not install suggests"

and it does...

that's exactly what i stated in my original email...

PEOPLE ARE HIJACKING MY THREAD!!!

Re: [Mageia-dev] installing minimal is not really that minimal

[Maarten Vanraes]

Op donderdag 22 maart 2012 08:40:14 schreef Thierry Vignaud:
[...]

ic your point, i too am interested in non-bloated install.

however, this mail is specifically on installing WITHOUT suggests, or X. and in 
this particular case, i'd like to get it really really small.

atm i'm looking at 670MB... which is way to bloated. at time of mga1, i had a 
similar install of around 450MB IIRC.
 
> > thing is, without a full kickstart (which i don't want to, i'd like to
> > keep doing partitioning manually, but kickstart seems not to do the
> > interactive requests), i can't really make a minimal system to begin
> > with...
> 
> you can still do a semi automatic install.

kickstart=file didn't seem to honor the interactive steps, and gave error 
because no / was found.

defcfg=file seemed to have a little bit of default settings, but still i had to 
go through every step...

i haven't found a way to have the middle ground. (or it needs some love)

Re: [Mageia-dev] installing minimal is not really that minimal

[Thomas Backlund]

Samuel Verschelde skrev 22.3.2012 17:06:

Le jeudi 22 mars 2012 16:05:09, Samuel Verschelde a écrit :

Le jeudi 22 mars 2012 16:01:22, John Balcaen a écrit :

2012/3/22 Olav Vitters:
[...]


But in a minimal install it
should ignore the Suggests, no?


By default urpmi install suggests, so if they are available they're
going to be installed.


I don't understand why you are saying this John. It's not really hard to
add a "minimal install" option that makes urpmi use the --no-suggests
switch.



And before someone answers "so provide a patch", it's not because I say "not
really hard" that I'm telling anyone to do it, including myself. I'm just
stating how I think it should be.


Installer already have a option to select "do not install suggests"

--
Thomas

Re: [Mageia-dev] installing minimal is not really that minimal

[Thierry Vignaud]

On 22 March 2012 13:20, Olav Vitters  wrote:
> I'm willing to assist when there are too big dependency chains. But, I
> don't get why in a minimal install it installs "Suggests:"? I can
> understand that it takes space on the DVD.

> But in a minimal install it
> should ignore the Suggests, no?

This option is only available for really minimal install.
But if you select anything else, you won't have the option.
So suggests will be used.
Eg: if you select just networking stuff.

And suggests are only half the issue.
Requires hurt too, especially library-requiring-tools-that-requires...

See the infamous  systemd | initscripts > lib64glib2.0_0 >
glib2.0-common > libgio > libgvfs >
libgnome-keyring > gnome-keyring > seahorse > libgpg > gnugpg > dirmngr
+ gnome-keyring > libgtk > gtk+ > colord > libcolord
+ libgvfs > libavahi > avahi
+ libgio > libfam > libgamin > gamin
+ libgio > libfuse > fuse
+seahore > libldap > openldap

They're suggests here but they're also requires
And having one gtk+ app can bring quite a lot of
stuff here b/c of:
- gvfs pulling avahi
- gio pulling gamin, fuse, gnome-keyring, gnugpg, dirmngr, seahhorse, openldap
- gtk+ pulling colord

Whereas most gtk+ apps don't need any of that.
And worse there're programs using glib for dbus (eg: systemd) but nothing
else, yet we end wio gio,gvfs,gtk+ then daemons

Some of these should be moved at top of the stack and be required
by task-foobar instead.
Any single of those was bring without the intention to hurt but
together they do hurt.

In the old days we could do a minimal install under 80M, now 525Mb is fine.
And those packages can have side effect : eg:
- avahi can prevent network to work
- too many "useless" services slow down the boot and makes mga looks
  awful against other distros
- ...

> I think we should have something which tracks these things
> automatically.

+1
But I've already asked for this once but got no answer.

> Meaning:
> - a way to see the dependency chains over time
>  (e.g. something which logs it per day)
> - a way to see the size of various "targets" over time
>  (e.g. KDE, GNOME, XFCE, minimal)
> - an email when the size changes compared to previous day
>  (e.g. new dependency, or maybe 100MB of documentation in some package)

Re: [Mageia-dev] New strings in drakx and urpmi - please do warn i18n

[Thierry Vignaud]

On 22 March 2012 16:44, Oliver Burger  wrote:
> I have again to ask to at least notify i18n upon string changes in our soft.
> Especially now, quite some time after i18n freeze, we NEED TO KNOW
> things like that.
>
> We could of course wach all commits to svn and see for ourselves, but
> I don't have the time for that and I think most others don't as well.

This should be automated which I cannot do anything for it.
As for drakx, AFAIC it's actually the I18N people who pushed for the change.

As for urpmi, I fixed a bug where a debug message wasn't displaying anything
(once again a late mdv breakage)
http://svnweb.mageia.org/soft?view=revision&sortby=date&revision=3639

I fixed it an restored the gratuitously removed call for translating.
I've also immediately restored the lost translations from mdv:
http://svnweb.mageia.org/soft?view=revision&revision=3641

The other one is just for helping debugging issues when people reports
bugs whose real cause is bogus options in /etc/urpmi/urpmi.cfg (such as
--allow-force or --keep).

For the rest, just open a bug report as release_blocker/critical so that
automatic mailing is done.

Re: [Mageia-dev] New strings in drakx and urpmi - please do warn i18n

[Olav Vitters]

On Thu, Mar 22, 2012 at 04:44:17PM +0100, Oliver Burger wrote:
> We could of course wach all commits to svn and see for ourselves, but
> I don't have the time for that and I think most others don't as well.

GNOME uses "Damned Lies" (http://l10n.gnome.org/) which notifies of
string changes (you have to tell it that you're in "string freeze").
Perhaps Blue Sky idea to have something like that.

I have no clue how "Damned Lies" itself. I do know that after each
commit (anything on git.gnome.org) "Damned Lies" is informed; it then
pulls the latest changes and somehow figures out that stuff changed. It
then sends emails.

-- 
Regards,
Olav

[Mageia-dev] New strings in drakx and urpmi - please do warn i18n

[Oliver Burger]

Hi there,

I have again to ask to at least notify i18n upon string changes in our soft.
Especially now, quite some time after i18n freeze, we NEED TO KNOW
things like that.

We could of course wach all commits to svn and see for ourselves, but
I don't have the time for that and I think most others don't as well.

Oliver

Re: [Mageia-dev] Freeze push - drakx-installer-help 2.2 and rebuild drakx-installer-stage2

[Kamil Rytarowski]

On 22.03.2012 14:20, Kamil Rytarowski wrote:

Hello!

Please push new drakx-installer-help 2.2
- new version 2.2
* add new images: note.png tip.png and warning.png
* fix typo in README (thanks Simon Parsons)

And rebuild against new drakx-installer-help drakx-installer-stage2
Please do NOT push it at the moment, the added icons are wrong and shall 
be fixed soon.

Re: [Mageia-dev] Mageia on Raspberry-Pi (ARM port)

[brett]

>>iinm we're actually still starting it up... contact rtp for more info
regarding this.

Can you please expand rtpI don't know what that stands for.

Re: [Mageia-dev] installing minimal is not really that minimal

[Samuel Verschelde]

Le jeudi 22 mars 2012 16:05:09, Samuel Verschelde a écrit :
> Le jeudi 22 mars 2012 16:01:22, John Balcaen a écrit :
> > 2012/3/22 Olav Vitters :
> > [...]
> > 
> > > But in a minimal install it
> > > should ignore the Suggests, no?
> > 
> > By default urpmi install suggests, so if they are available they're
> > going to be installed.
> 
> I don't understand why you are saying this John. It's not really hard to
> add a "minimal install" option that makes urpmi use the --no-suggests
> switch.
> 

And before someone answers "so provide a patch", it's not because I say "not 
really hard" that I'm telling anyone to do it, including myself. I'm just 
stating how I think it should be.

Samuel

Re: [Mageia-dev] installing minimal is not really that minimal

[Samuel Verschelde]

Le jeudi 22 mars 2012 16:01:22, John Balcaen a écrit :
> 2012/3/22 Olav Vitters :
> [...]
> 
> > But in a minimal install it
> > should ignore the Suggests, no?
> 
> By default urpmi install suggests, so if they are available they're
> going to be installed.

I don't understand why you are saying this John. It's not really hard to add 
a "minimal install" option that makes urpmi use the --no-suggests switch.

It doesn't prevent from being careful with deps, but I agree with Olav : a 
minimal install should ignore Suggests.

Samuel

Re: [Mageia-dev] installing minimal is not really that minimal

[John Balcaen]

2012/3/22 Olav Vitters :
[...]
> But in a minimal install it
> should ignore the Suggests, no?

By default urpmi install suggests, so if they are available they're
going to be installed.


> I think we should have something which tracks these things
> automatically.
>
> Meaning:
> - a way to see the dependency chains over time
>  (e.g. something which logs it per day)
> - a way to see the size of various "targets" over time
>  (e.g. KDE, GNOME, XFCE, minimal)
> - an email when the size changes compared to previous day
>  (e.g. new dependency, or maybe 100MB of documentation in some package)
Luc did a similar work regarding that between mga1 & mga2 focus indeed
on  kde (package & size), there's a bug report on it (but i don't
remember the number immediatly.




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

Re: [Mageia-dev] KWin Segfault - sporatic

[John Balcaen]

2012/3/22 Manuel Hiebel :
> Le 22/03/2012 15:28, Robert Fox a écrit :
>
>> I have been experiencing a sporadic KWin segfault crash - it can not be
>> forced and happens very rarely.  When it does happen, I can not access
>> the KDE panel anymore, but the desktop continues to work.  The only
>> resolve it to logout and restart KDE -
>>
>> Here is the backtrace:
>>
> [...]
>
>>
>> Should I file a bug??
>>
> With a quick query:
> https://bugs.mageia.org/show_bug.cgi?id=4600
>
> so feel free to help
I'm not sure it's the same crash.


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

Re: [Mageia-dev] KWin Segfault - sporatic

[John Balcaen]

2012/3/22 Robert Fox :
> I have been experiencing a sporadic KWin segfault crash - it can not be
> forced and happens very rarely.  When it does happen, I can not access
> the KDE panel anymore, but the desktop continues to work.  The only
> resolve it to logout and restart KDE -
>
> Here is the backtrace:
[...]
> Should I file a bug??
You should install -debug packages & reported a bug with a way to
reproduce it (plasmoid installed/effects enabled etc etc )
>



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

Re: [Mageia-dev] KWin Segfault - sporatic

[Manuel Hiebel]

Le 22/03/2012 15:28, Robert Fox a écrit :

I have been experiencing a sporadic KWin segfault crash - it can not be
forced and happens very rarely.  When it does happen, I can not access
the KDE panel anymore, but the desktop continues to work.  The only
resolve it to logout and restart KDE -

Here is the backtrace:


[...]


Should I file a bug??


With a quick query:
https://bugs.mageia.org/show_bug.cgi?id=4600

so feel free to help


Thx,
R.Fox

Re: [Mageia-dev] KWin Segfault - sporatic

[Thierry Vignaud]

On 22 March 2012 15:28, Robert Fox  wrote:
> Should I file a bug??

Yes. Instead of posting here.
But install first the needed debug packages (at least glibc-debug,
qt4-debug, kde*-debug)

[Mageia-dev] KWin Segfault - sporatic

[Robert Fox]

I have been experiencing a sporadic KWin segfault crash - it can not be
forced and happens very rarely.  When it does happen, I can not access
the KDE panel anymore, but the desktop continues to work.  The only
resolve it to logout and restart KDE -

Here is the backtrace:

KDE Application: KWin (kwin), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7feeb5682740 (LWP 4822))]

Thread 2 (Thread 0x7fee92c90700 (LWP 4827)):
#0  0x7feeb0253594 in pthread_cond_wait@@GLIBC_2.3.2 ()
from /lib64/libpthread.so.0
#1  0x7feeb1952bd2 in ?? () from /usr/lib64/libQtScript.so.4
#2  0x7feeb1952c09 in ?? () from /usr/lib64/libQtScript.so.4
#3  0x7feeb10fd354 in ?? ()
from /usr/lib64/nvidia-current/libGL.so.1
#4  0x7feeb024fb99 in start_thread () from /lib64/libpthread.so.0
#5  0x7feeb4ec30cd in clone () from /lib64/libc.so.6
#6  0x in ?? ()

Thread 1 (Thread 0x7feeb5682740 (LWP 4822)):
[KCrash Handler]
#6  0x7fee982cd285 in ?? ()
from /usr/lib64/kde4/kwin4_effect_builtins.so
#7  0x7feeb5246878 in ?? () from /usr/lib64/libkdeinit4_kwin.so
#8  0x7feeb5246878 in ?? () from /usr/lib64/libkdeinit4_kwin.so
#9  0x7feeb522583e in ?? () from /usr/lib64/libkdeinit4_kwin.so
#10 0x7feeb523befd in ?? () from /usr/lib64/libkdeinit4_kwin.so
#11 0x7feeb521fbac in ?? () from /usr/lib64/libkdeinit4_kwin.so
#12 0x7feeb05f5a59 in QObject::event(QEvent*) ()
from /usr/lib64/libQtCore.so.4
#13 0x7feeaf74fb84 in QApplicationPrivate::notify_helper(QObject*,
QEvent*) () from /usr/lib64/libQtGui.so.4
#14 0x7feeaf754a03 in QApplication::notify(QObject*, QEvent*) ()
from /usr/lib64/libQtGui.so.4
#15 0x7feeb492c9c6 in KApplication::notify(QObject*, QEvent*) ()
from /usr/lib64/libkdeui.so.5
#16 0x7feeb05dce7c in QCoreApplication::notifyInternal(QObject*,
QEvent*) () from /usr/lib64/libQtCore.so.4
#17 0x7feeb060d9c2 in ?? () from /usr/lib64/libQtCore.so.4
#18 0x7feeb060e4a4 in
QEventDispatcherUNIX::processEvents(QFlags) () 
from /usr/lib64/libQtCore.so.4
#19 0x7feeaf7f3868 in ?? () from /usr/lib64/libQtGui.so.4
#20 0x7feeb05dbc62 in
QEventLoop::processEvents(QFlags) ()
from /usr/lib64/libQtCore.so.4
#21 0x7feeb05dbeb7 in
QEventLoop::exec(QFlags) ()
from /usr/lib64/libQtCore.so.4
#22 0x7feeb05e09a5 in QCoreApplication::exec() ()
from /usr/lib64/libQtCore.so.4
#23 0x7feeb51d5416 in kdemain () from /usr/lib64/libkdeinit4_kwin.so
#24 0x7feeb4e0a32d in __libc_start_main () from /lib64/libc.so.6
#25 0x00400671 in _start ()

Should I file a bug??


Thx,
R.Fox

Re: [Mageia-dev] Freeze push: systemd

[Colin Guthrie]

'Twas brillig, and Colin Guthrie at 22/03/12 13:48 did gyre and gimble:
> 'Twas brillig, and Luis Daniel Lucio Quiroz at 22/03/12 12:50 did gyre
> and gimble:
>> I dont know if this is usefull for you, 
>> Mar 21 21:09:09 1000 systemd[1]: [/lib/systemd/system/ntop.service:23] 
>> Assignment outside of section. Ignoring.
>> Mar 21 21:09:09 1000 systemd[1]: [/lib/systemd/system/ntop.service:24] 
>> Assignment outside of section. Ignoring.
> 
> Yup, this is just reporting that the ntop.service file has invalid syntax.
> 
> I'll add it to my todo list.

Actually it was just a typo in the spec file that installed the
initscript as the systemd unit which is certainly not going to work!

I've replaced it with the real unit file now. Hopefully all fixed in the
next version of ntop.

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] please push libnetfilter_queue

[Luis Daniel Lucio Quiroz]

On Jue 22 Mar 2012 07:41:02 Anne Nicolas escribió:
> Le 22/03/2012 14:38, Luis Daniel Lucio Quiroz a écrit :
> > Helo
> > 
> > Please push libnetfilter_queue, it updates from 1.0.0 to 1.0.1
> > 
> > LD
> 
> Reasons...

I'm not a kernel developer, here it is the changelog
https://git.netfilter.org/cgi-bin/gitweb.cgi?p=libnetfilter_queue.git;a=shortlog

There are more than 18 months of difference between 1.0.0 and 1.0.1, I guess 
since this is a kernel matter, 18 months ago we were using 2.6, now 3.3.

LD

Re: [Mageia-dev] Freeze push: systemd

[Colin Guthrie]

'Twas brillig, and Luis Daniel Lucio Quiroz at 22/03/12 12:50 did gyre
and gimble:
> I dont know if this is usefull for you, 
> Mar 21 21:09:09 1000 systemd[1]: [/lib/systemd/system/ntop.service:23] 
> Assignment outside of section. Ignoring.
> Mar 21 21:09:09 1000 systemd[1]: [/lib/systemd/system/ntop.service:24] 
> Assignment outside of section. Ignoring.

Yup, this is just reporting that the ntop.service file has invalid syntax.

I'll add it to my todo list.

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] installing minimal is not really that minimal

[Olav Vitters]

On Thu, Mar 22, 2012 at 10:45:44AM +0100, Thierry Vignaud wrote:
> I've made quite some changes for mga2 in order to bring minimal
> install under control.
> But that can't work in the long term.

Let's ignore all the other stuff and focus on how to solve it.

I'm willing to assist when there are too big dependency chains. But, I
don't get why in a minimal install it installs "Suggests:"? I can
understand that it takes space on the DVD. But in a minimal install it
should ignore the Suggests, no?


I think we should have something which tracks these things
automatically.

Meaning:
- a way to see the dependency chains over time
  (e.g. something which logs it per day)
- a way to see the size of various "targets" over time
  (e.g. KDE, GNOME, XFCE, minimal)
- an email when the size changes compared to previous day
  (e.g. new dependency, or maybe 100MB of documentation in some package)

-- 
Regards,
Olav

Re: [Mageia-dev] please push libnetfilter_queue

[Anne Nicolas]

Le 22/03/2012 14:38, Luis Daniel Lucio Quiroz a écrit :
> Helo
> 
> Please push libnetfilter_queue, it updates from 1.0.0 to 1.0.1
> 
> LD

Reasons...

-- 
Anne
http://mageia.org

[Mageia-dev] please push libnetfilter_queue

[Luis Daniel Lucio Quiroz]

Helo

Please push libnetfilter_queue, it updates from 1.0.0 to 1.0.1

LD

Re: [Mageia-dev] Freeze push: Banshee 2.4.0 security push

[Olav Vitters]

On Mon, Mar 19, 2012 at 11:13:03PM +0100, Olav Vitters wrote:
> Banshee 2.4.0 contains a security fix. I tried to include just the
> patch, but failed to build it and in the meantime 2.4.0 was released.

I have the ability to submit, but that is just for GNOME, and Banshee is
not part of GNOME Core/Apps.

So: ping :)

-- 
Regards,
Olav

[Mageia-dev] Freeze push - drakx-installer-help 2.2 and rebuild drakx-installer-stage2

[Kamil Rytarowski]

Hello!

Please push new drakx-installer-help 2.2
- new version 2.2
* add new images: note.png tip.png and warning.png
* fix typo in README (thanks Simon Parsons)

And rebuild against new drakx-installer-help drakx-installer-stage2

Re: [Mageia-dev] Freeze push: systemd

[Luis Daniel Lucio Quiroz]

On Mié 21 Mar 2012 03:30:42 Anne nicolas escribió:
> 2012/3/21 Olav Vitters 
> 
> > On Wed, Mar 21, 2012 at 10:47:16AM +0200, Thomas Backlund wrote:
> > > Anne nicolas skrev 21.3.2012 10:23:
> > > >2012/3/19 Colin Guthrie  > > >>
> > > >
> > > >>Please see thread from earlier today on this topic.
> > > >>
> > > >>If needed I can do the complicated job of cherry picking most of
> > 
> > the
> > 
> > > >>patches instead if the version bump scares people :)
> > > >
> > > >I must say I miss here some knowledge to take this decision and I'd
> > > >like some other opinions on this
> > > 
> > > Reading the changes in git, I see enough fixes that I also think we
> > > need, so I'd say lets push it as it would otherwise be mostly a
> > > systemd v44 disguised as a v43  with a lot of patches.
> > 
> > Agree. Only possible problem is enforcement of UTF-8 in configuration
> > files. I don't think that'll cause problems and even if so, easily
> > fixed.
> 
> ok thanks for your comments. Colin be prepared to fix any problem :)
> 
> > --
> > Regards,
> > Olav

I dont know if this is usefull for you, 
Mar 21 21:09:09 1000 systemd[1]: [/lib/systemd/system/ntop.service:23] 
Assignment outside of section. Ignoring.
Mar 21 21:09:09 1000 systemd[1]: [/lib/systemd/system/ntop.service:24] 
Assignment outside of section. Ignoring.



I dont have a very common configuration, in fact this is an appliance, i do 
connections using ttyS0 and pts (by ssh).  Also look i dont have common 
hostname

Hope this help you,

Re: [Mageia-dev] [changelog] [RPM] cauldron nonfree/release radeon-firmware-20120322-1.mga2.nonfree

[Thomas Backlund]

Thierry Vignaud skrev 22.3.2012 14:12:

On 22 March 2012 12:39, tmb  wrote:

tmb  20120322-1.mga2:
+ Revision: 225670
- add new firmwares:
  * PITCAIRN, TAHITI, VERDE (Southern Islands / HD7xxx)
  * ARUBA (trinity APU)


That's useless unless we backport kernel&  x11-driver-video-ati support
Do you plan to do so?


Yep. That's the idea.

--
Thomas

Re: [Mageia-dev] [changelog] [RPM] cauldron nonfree/release radeon-firmware-20120322-1.mga2.nonfree

[Thierry Vignaud]

On 22 March 2012 12:39, tmb  wrote:
> tmb  20120322-1.mga2:
> + Revision: 225670
> - add new firmwares:
>  * PITCAIRN, TAHITI, VERDE (Southern Islands / HD7xxx)
>  * ARUBA (trinity APU)

That's useless unless we backport kernel & x11-driver-video-ati support
Do you plan to do so?

Re: [Mageia-dev] installing minimal is not really that minimal

[Kamil Rytarowski]

On 22.03.2012 10:48, Anne nicolas wrote:

2012/3/22 Thierry Vignaud:

On 22 March 2012 09:31, You-Cheng Hsieh  wrote:

note that having a couple x11 package is not installing x11.
I've made the minimal install quite a lot smaller.

We still have issues with suggests that makes installation explodes.
I've reports some bugs but maintainers just don't care.
See eg: https://bugs.mageia.org/show_bug.cgi?id=4357 that got
reaffected to me because the maintainer doesn't care about
bloating the install
This particular one isn't about minimal install but about gnome install
but the underlying issue will bloats any minimal install + light desktop
+ _one_ gtk+ application.


Both gnome-keyring and task-gnome are maintained by nobody, could you
modify the spec and close the bug?

I've made quite some changes for mga2 in order to bring minimal
install under control.
But that can't work in the long term.
I'ven't enough time&  I cannot do it alone.
I did it twice back @mdv and yet people keep introduced new interesting
ways to bloat again.

I don't want to imply Olav did it. But he's packager of one of the offending
packages, and so inherited part of mdv heritage.
So I wrote a bug about it in order to pull maintainers in.

Every packager should be made aware of Implications of:
- suggests
- library requiring the tools they were created for

It's easy to add a suggest ("hey it'll just make the user experience better"),
but eventually the suggested package can start a cycles that will pull
quite a lot more packages.

See https://bugs.mageia.org/show_bug.cgi?id=4357#c5
systemd was initially pulling:
- the whole gtk+ stack,
- openldap,
- avahi,
- gamin,
- fuse,
- colord,
- gnome-keyring,
- seahorse,
- dirmngr
- python

And none of it (but python) has actually to do with systemd.
It was just that required library actually suggest or requires another one
which also suggested or required ...

Everyone should be concerned about that.

I've broke some requires/suggest cycles, but I cannot do it alone,
everyone should contribute (and also should try not to introduce
new ones)

I think that some of those "comfort" suggests should be moved
from some low level library or tool package to task-
packages.

Thus no I won't fix every issue.
People have to test install and have to get interested in reducing
size of install.
This is not a personal attack against Olav that does a good job.
That means for everyone to get in the implications of requires&
suggests.
Not looking only at that particular package but at the global view,
the installed system.

Not all suggests will bloat installing from DVD as some won't make
it into the DVD image. But some will b/c they're required by other
packages and thus will succeed in being suggested.

Minimal install won't be as perfect as installing basesystem with urpmi
because of installer also pulling packages needed for HW (eg: LVM,
SMP, bluetooth, ...)

At least for mga2, it's has been reduced.
But it could be more.

Also installing a desktop (GNOME&  KDE) is huge these days.
Something should be made about it.
Maybe splitting task-{gnome,kde}-networking and the like and moving
them under CAT_NETWORK, CAT_OFFICE, CAT_GAMES, CAT_INTERNET,
CAT_MULTIMEDIA and the like in rpmsrate.

But this is the job of everyone.
Not just me.

My 2 cents

Thanks for your proposal. But anyway this is for Mageia 3. Could we
please calm down and focus again on coming release? We do have work
enough for everybody :)

Cheers


Yes, I completely agree.

This is a key value for the quality of distro. We can't force everyone 
to use in the most minimal setup for example rmt ("Provides certain 
programs with access to remote tape devices.") as a requirement of cpio 
and so rpm! or sound scripts as a requirement of init-scripts...


I have got a remote server and I really don't want to be forced to have 
full sound support, themed boolloader and rmt support on that computer.


This is a goal for Mga3, I have in mind some tools to help resolving the 
dependency hell.

Re: [Mageia-dev] freeze push: mesa

[Anne nicolas]

2012/3/22 Thierry Vignaud :
> Hi
>
> Please let in mesa-8.0.2.
> It's a pure bug fixes only minor release that fixes support on newer
> intel cards.
> Here's the changelog:
>
>    Bug 38720 - [SNB] Trine triggers a GPU hang
>    Bug 40059 - [SNB] hang in "Amnesia: The Dark Descent" demo
>    Bug 45216 - [SNB] GPU hang in OilRush
>    Bug 46631 - It's really hard to hit the fast path for the fallback
> glReadPixels code
>    Bug 46679 - glReadPixels on a luminance texture returns the wrong values
>    Bug 46311 - Missing support of point size in Mesa core
>    Bug 46665 - [PNV] webgl conformance case max texture fails
>    Bug 45975 - [Gen4 + ILK] render with pointcoord will fail to render
>    Bug 4 - [PNV] webgl conformance case NPOT case fails with
> TEXTURE_MIN_FILTER set to LINEAR
>
> See you

submitted by boklm

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

Re: [Mageia-dev] installing minimal is not really that minimal

[Christian Lohmaier]

On Thu, Mar 22, 2012 at 10:45 AM, Thierry Vignaud
 wrote:
> On 22 March 2012 09:31, You-Cheng Hsieh  wrote:
>
> It's easy to add a suggest ("hey it'll just make the user experience better"),
> but eventually the suggested package can start a cycles that will pull
> quite a lot more packages.

This is a lame excuse, really.
What you are actually saying is that rpmdrake sucks because it doesn't
distinguish between required and suggested packages and doesn't let
the user choose.

The topic started off with a user using minimal installation without
suggested packages - just to remind you of that.

> [...]
> And none of it (but python) has actually to do with systemd.
> It was just that required library actually suggest or requires another one
> which also suggested or required ...

Don't mix up suggests with requires in this matter please.

> Everyone should be concerned about that.

Yes, but don't force crippling of package's interdependencies/suggests
because one part of the tooling ignores the difference between
requires and suggests.

> I think that some of those "comfort" suggests should be moved
> from some low level library or tool package to task-
> packages.

I completely disagree.

Give the user control of the suggested packages, highlight stuff that
is suggested and what is required.

ciao
Christian

Re: [Mageia-dev] installing minimal is not really that minimal

[Christian Lohmaier]

On Thu, Mar 22, 2012 at 10:26 AM, Wolfgang Bornath
 wrote:
> 2012/3/22 Olav Vitters :
>> I care about GNOME and giving
>> a full experience. If people want a more minimal install to the
>> detriment of GNOME, then I don't like it.
>
> Well, no comment on the other parts of the mail, but:
>
> Despite your commitment to Gnome, isn't this for the user to select
> what he wants?

Please, don't mix up things. That bug is about a *SUGGESTS* not a
requires, it is also not part of task-gnome itself, but of
gnome-keyring.

It is perfectly reasonable to have a suggests on seahorse from
gnome-keyring. It is the only sane thing to do I'd like to add.

totem (and even more so its mozilla plugin) tearing in all this is the
bug. Don't blame Olav here.

> If he wants a minimal installation, knowing that he may
> not get the full Gnome experience, isn't that for him to decide
> instead of being forced to pack things on his machine he does not care
> for, whether you like it or not?

A suggested package is not forced on anybody.

ciao
Christian

Re: [Mageia-dev] installing minimal is not really that minimal

[Olav Vitters]

On Thu, Mar 22, 2012 at 10:31:04AM +0100, Thierry Vignaud wrote:
> On 22 March 2012 09:49, Olav Vitters  wrote:
> > If your comment starts off with a:
> > "You're playing with words here, task-gnome can be replaced by"
> >
> > while my intention is well meaning and not "playing with words", then I
> > my first thought is not anywhere near constructive.
> >
> > The bugreport was opened about KDE. I gave a solution for KDE. Instead I
> > get accusations about playing with words. I care about GNOME and giving
> > a full experience. If people want a more minimal install to the
> > detriment of GNOME, then I don't like it.
> >
> > I have 0 interest in getting more accusations about "doesn't care". I
> > gave up maintainership because of the tone, allowing you to do whatever.
> > That this is still not good enough, blergh!
> 
> My phrasing wasn't the best one, I can agree with that.
> But you did closed the bug as WONTFIX b/c I wrote "task-gnome" instead
> of "task-gnome-minimal".
> I think you can admit this wasn't fair, can't you?

I already closed it before your comment about task-gnome. The comment
you gave before (comment 3) was only about why it was added
historically. You even quoted the original reason for adding it:
| without Seahorse, there's no way to manage your gnome-keyring passwords

The bug was raised because of KDE, I was looking at it from that point
of view. You care about a minimal install, but that was not what the bug
was reported for nor what I was thinking about.

I closed it with because to me, if you don't want GNOME things in KDE,
then don't put GNOME things in CAT_KDE. And "totem-mozilla" is to me a
GNOME thing, not GTK thing. The WONTFIX is because for this specific
bugreport (KDE install having GNOME stuff), the problem is
"totem-mozilla" in KDE.

That this suggests also has an affects the minimal install, ok, but the
dependency was added (according to your comment) 1.5 years ago. So if
this dependency was ok 1.5 years ago, why not now? (read on before
replying please:)
Now if in those 1.5 years things changed (dependency changes, etc) and
this dependency now suddenly affects the minimal install, then yeah, I
think moving the suggests somewhere else makes sense.

But I didn't close it because of the minimal install. Only because of
looking at what it was filed for: KDE dependency problems.

Every time I touch task-gnome-minimal there is a huge discussion that
the change is somehow bad/imperfect/something. I don't like that. I mean
well and if task-gnome-minimal causes loads of complaints, then anything
related to it I rather avoid.

-- 
Regards,
Olav

Re: [Mageia-dev] installing minimal is not really that minimal

[Anne nicolas]

2012/3/22 Thierry Vignaud :
> On 22 March 2012 09:31, You-Cheng Hsieh  wrote:
>>> note that having a couple x11 package is not installing x11.
>>> I've made the minimal install quite a lot smaller.
>>>
>>> We still have issues with suggests that makes installation explodes.
>>> I've reports some bugs but maintainers just don't care.
>>> See eg: https://bugs.mageia.org/show_bug.cgi?id=4357 that got
>>> reaffected to me because the maintainer doesn't care about
>>> bloating the install
>>> This particular one isn't about minimal install but about gnome install
>>> but the underlying issue will bloats any minimal install + light desktop
>>> + _one_ gtk+ application.
>>>
>> Both gnome-keyring and task-gnome are maintained by nobody, could you
>> modify the spec and close the bug?
>
> I've made quite some changes for mga2 in order to bring minimal
> install under control.
> But that can't work in the long term.
> I'ven't enough time & I cannot do it alone.
> I did it twice back @mdv and yet people keep introduced new interesting
> ways to bloat again.
>
> I don't want to imply Olav did it. But he's packager of one of the offending
> packages, and so inherited part of mdv heritage.
> So I wrote a bug about it in order to pull maintainers in.
>
> Every packager should be made aware of Implications of:
> - suggests
> - library requiring the tools they were created for
>
> It's easy to add a suggest ("hey it'll just make the user experience better"),
> but eventually the suggested package can start a cycles that will pull
> quite a lot more packages.
>
> See https://bugs.mageia.org/show_bug.cgi?id=4357#c5
> systemd was initially pulling:
> - the whole gtk+ stack,
> - openldap,
> - avahi,
> - gamin,
> - fuse,
> - colord,
> - gnome-keyring,
> - seahorse,
> - dirmngr
> - python
>
> And none of it (but python) has actually to do with systemd.
> It was just that required library actually suggest or requires another one
> which also suggested or required ...
>
> Everyone should be concerned about that.
>
> I've broke some requires/suggest cycles, but I cannot do it alone,
> everyone should contribute (and also should try not to introduce
> new ones)
>
> I think that some of those "comfort" suggests should be moved
> from some low level library or tool package to task-
> packages.
>
> Thus no I won't fix every issue.
> People have to test install and have to get interested in reducing
> size of install.
> This is not a personal attack against Olav that does a good job.
> That means for everyone to get in the implications of requires &
> suggests.
> Not looking only at that particular package but at the global view,
> the installed system.
>
> Not all suggests will bloat installing from DVD as some won't make
> it into the DVD image. But some will b/c they're required by other
> packages and thus will succeed in being suggested.
>
> Minimal install won't be as perfect as installing basesystem with urpmi
> because of installer also pulling packages needed for HW (eg: LVM,
> SMP, bluetooth, ...)
>
> At least for mga2, it's has been reduced.
> But it could be more.
>
> Also installing a desktop (GNOME & KDE) is huge these days.
> Something should be made about it.
> Maybe splitting task-{gnome,kde}-networking and the like and moving
> them under CAT_NETWORK, CAT_OFFICE, CAT_GAMES, CAT_INTERNET,
> CAT_MULTIMEDIA and the like in rpmsrate.
>
> But this is the job of everyone.
> Not just me.
>
> My 2 cents

Thanks for your proposal. But anyway this is for Mageia 3. Could we
please calm down and focus again on coming release? We do have work
enough for everybody :)

Cheers

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

Re: [Mageia-dev] installing minimal is not really that minimal

[Thierry Vignaud]

On 22 March 2012 09:31, You-Cheng Hsieh  wrote:
>> note that having a couple x11 package is not installing x11.
>> I've made the minimal install quite a lot smaller.
>>
>> We still have issues with suggests that makes installation explodes.
>> I've reports some bugs but maintainers just don't care.
>> See eg: https://bugs.mageia.org/show_bug.cgi?id=4357 that got
>> reaffected to me because the maintainer doesn't care about
>> bloating the install
>> This particular one isn't about minimal install but about gnome install
>> but the underlying issue will bloats any minimal install + light desktop
>> + _one_ gtk+ application.
>>
> Both gnome-keyring and task-gnome are maintained by nobody, could you
> modify the spec and close the bug?

I've made quite some changes for mga2 in order to bring minimal
install under control.
But that can't work in the long term.
I'ven't enough time & I cannot do it alone.
I did it twice back @mdv and yet people keep introduced new interesting
ways to bloat again.

I don't want to imply Olav did it. But he's packager of one of the offending
packages, and so inherited part of mdv heritage.
So I wrote a bug about it in order to pull maintainers in.

Every packager should be made aware of Implications of:
- suggests
- library requiring the tools they were created for

It's easy to add a suggest ("hey it'll just make the user experience better"),
but eventually the suggested package can start a cycles that will pull
quite a lot more packages.

See https://bugs.mageia.org/show_bug.cgi?id=4357#c5
systemd was initially pulling:
- the whole gtk+ stack,
- openldap,
- avahi,
- gamin,
- fuse,
- colord,
- gnome-keyring,
- seahorse,
- dirmngr
- python

And none of it (but python) has actually to do with systemd.
It was just that required library actually suggest or requires another one
which also suggested or required ...

Everyone should be concerned about that.

I've broke some requires/suggest cycles, but I cannot do it alone,
everyone should contribute (and also should try not to introduce
new ones)

I think that some of those "comfort" suggests should be moved
from some low level library or tool package to task-
packages.

Thus no I won't fix every issue.
People have to test install and have to get interested in reducing
size of install.
This is not a personal attack against Olav that does a good job.
That means for everyone to get in the implications of requires &
suggests.
Not looking only at that particular package but at the global view,
the installed system.

Not all suggests will bloat installing from DVD as some won't make
it into the DVD image. But some will b/c they're required by other
packages and thus will succeed in being suggested.

Minimal install won't be as perfect as installing basesystem with urpmi
because of installer also pulling packages needed for HW (eg: LVM,
SMP, bluetooth, ...)

At least for mga2, it's has been reduced.
But it could be more.

Also installing a desktop (GNOME & KDE) is huge these days.
Something should be made about it.
Maybe splitting task-{gnome,kde}-networking and the like and moving
them under CAT_NETWORK, CAT_OFFICE, CAT_GAMES, CAT_INTERNET,
CAT_MULTIMEDIA and the like in rpmsrate.

But this is the job of everyone.
Not just me.

My 2 cents

Re: [Mageia-dev] installing minimal is not really that minimal

[Thierry Vignaud]

On 22 March 2012 09:49, Olav Vitters  wrote:
> If your comment starts off with a:
> "You're playing with words here, task-gnome can be replaced by"
>
> while my intention is well meaning and not "playing with words", then I
> my first thought is not anywhere near constructive.
>
> The bugreport was opened about KDE. I gave a solution for KDE. Instead I
> get accusations about playing with words. I care about GNOME and giving
> a full experience. If people want a more minimal install to the
> detriment of GNOME, then I don't like it.
>
> I have 0 interest in getting more accusations about "doesn't care". I
> gave up maintainership because of the tone, allowing you to do whatever.
> That this is still not good enough, blergh!

My phrasing wasn't the best one, I can agree with that.
But you did closed the bug as WONTFIX b/c I wrote "task-gnome" instead
of "task-gnome-minimal".
I think you can admit this wasn't fair, can't you?

Re: [Mageia-dev] installing minimal is not really that minimal

[Wolfgang Bornath]

2012/3/22 Olav Vitters :
> I care about GNOME and giving
> a full experience. If people want a more minimal install to the
> detriment of GNOME, then I don't like it.

Well, no comment on the other parts of the mail, but:

Despite your commitment to Gnome, isn't this for the user to select
what he wants? If he wants a minimal installation, knowing that he may
not get the full Gnome experience, isn't that for him to decide
instead of being forced to pack things on his machine he does not care
for, whether you like it or not?

-- 
wobo

[Mageia-dev] rescue has mount.nfs, but no statd

[Maarten Vanraes]

at $dayjob, we're testing out the rescue.

so at first we're doing an rsync, but we need to do it on a network disk.

cifs was not available, but that's not a big issue.

nfs was available, so we wanted to mount

but the mount failed, because nfs module wasn't modprobed, and drvinst
didn't fix that (maybe it should modprobe nfs as well)

or maybe mount.nfs should try to modprobe nfs if needed.

however, statd wasn't there and it complained that it needed that for locking

atm we're doing -o nolock and that works... but... statd would be quite
usefull here...

Re: [Mageia-dev] installing minimal is not really that minimal

[Olav Vitters]

On Thu, Mar 22, 2012 at 08:40:14AM +0100, Thierry Vignaud wrote:
> We still have issues with suggests that makes installation explodes.
> I've reports some bugs but maintainers just don't care.
> See eg: https://bugs.mageia.org/show_bug.cgi?id=4357 that got
> reaffected to me because the maintainer doesn't care about
> bloating the install

If your comment starts off with a:
"You're playing with words here, task-gnome can be replaced by"

while my intention is well meaning and not "playing with words", then I
my first thought is not anywhere near constructive.

The bugreport was opened about KDE. I gave a solution for KDE. Instead I
get accusations about playing with words. I care about GNOME and giving
a full experience. If people want a more minimal install to the
detriment of GNOME, then I don't like it.

I have 0 interest in getting more accusations about "doesn't care". I
gave up maintainership because of the tone, allowing you to do whatever.
That this is still not good enough, blergh!

-- 
Regards,
Olav

Re: [Mageia-dev] lighttpd and others now require apache

[Guillaume Rousse]

Le 22/03/2012 02:51, David Walser a écrit :

Guillaume Rousse wrote:

Le 17/03/2012 03:22, Anssi Hannula a écrit :

Hence I suggest a single user id to be used. (I'm fine with any other
solution which works as well)

My main concern is the fuzziness of the current situation where we have
- one virtual package 'webserver' corresponding to four implementations
(apache, lightpd, nginx, cherooke)
- one common base (webserver-base) only used by the two first ones
- all our web applications packages using 'apache' as mandatory dependency

If the main concern is file ownership, I'd propose for the next release
to have each of these servers use a distinct uid, document root and
index page, but use a shared 'webserver' or 'www' gid, and ensure all of
those applications use group-based permission, instead of user-based.
I'd find this setup a bit clearer.


I also noticed two of the php subpackages adding the apache user in %post.
Should they be doing this, should they Requires(post): webserver-base, or
should this be handled some other way?

Sure, that's wrong.

Either they need apache itself, in this case this dependency is already 
ensured. Either they can be used without a web server, in this case they 
shouldn't use apache server anyway.


--
BOFH excuse #161:

monitor VLF leakage

Re: [Mageia-dev] installing minimal is not really that minimal

[You-Cheng Hsieh]

2012/3/22 Thierry Vignaud :
> On 22 March 2012 00:30, Maarten Vanraes  wrote:
>> i did a network install
>>
>> and choose 'custom', then deselected everything, pressed next
>>
>> i got to the next menu of installation and left these to default:
>>
>>  - no X
>>  - no suggestions
>>  - basic doc still on
>>  - truly minimal was off
>>
>> but, i ended up with x libraries, fonts, etc...
>
> note that having a couple x11 package is not installing x11.
> I've made the minimal install quite a lot smaller.
>
> We still have issues with suggests that makes installation explodes.
> I've reports some bugs but maintainers just don't care.
> See eg: https://bugs.mageia.org/show_bug.cgi?id=4357 that got
> reaffected to me because the maintainer doesn't care about
> bloating the install
> This particular one isn't about minimal install but about gnome install
> but the underlying issue will bloats any minimal install + light desktop
> + _one_ gtk+ application.
>
Both gnome-keyring and task-gnome are maintained by nobody, could you
modify the spec and close the bug?

[Mageia-dev] freeze push: mesa

[Thierry Vignaud]

Hi

Please let in mesa-8.0.2.
It's a pure bug fixes only minor release that fixes support on newer
intel cards.
Here's the changelog:

Bug 38720 - [SNB] Trine triggers a GPU hang
Bug 40059 - [SNB] hang in "Amnesia: The Dark Descent" demo
Bug 45216 - [SNB] GPU hang in OilRush
Bug 46631 - It's really hard to hit the fast path for the fallback
glReadPixels code
Bug 46679 - glReadPixels on a luminance texture returns the wrong values
Bug 46311 - Missing support of point size in Mesa core
Bug 46665 - [PNV] webgl conformance case max texture fails
Bug 45975 - [Gen4 + ILK] render with pointcoord will fail to render
Bug 4 - [PNV] webgl conformance case NPOT case fails with
TEXTURE_MIN_FILTER set to LINEAR

See you

Re: [Mageia-dev] installing minimal is not really that minimal

[Thierry Vignaud]

On 22 March 2012 00:30, Maarten Vanraes  wrote:
> i did a network install
>
> and choose 'custom', then deselected everything, pressed next
>
> i got to the next menu of installation and left these to default:
>
>  - no X
>  - no suggestions
>  - basic doc still on
>  - truly minimal was off
>
> but, i ended up with x libraries, fonts, etc...

note that having a couple x11 package is not installing x11.
I've made the minimal install quite a lot smaller.

We still have issues with suggests that makes installation explodes.
I've reports some bugs but maintainers just don't care.
See eg: https://bugs.mageia.org/show_bug.cgi?id=4357 that got
reaffected to me because the maintainer doesn't care about
bloating the install
This particular one isn't about minimal install but about gnome install
but the underlying issue will bloats any minimal install + light desktop
+ _one_ gtk+ application.

> thing is, without a full kickstart (which i don't want to, i'd like to keep
> doing partitioning manually, but kickstart seems not to do the interactive
> requests), i can't really make a minimal system to begin with...

you can still do a semi automatic install.

Re: [Mageia-dev] Freeze push: libpng12-1.2.48

[nicolas vigier]

On Thu, 22 Mar 2012, Funda Wang wrote:

> Hello,
> 
> Could somebody push libpng12-1.2.48 into cauldron? It fixed a security
> problem CVE-2011-3045 (buffer overflow in png_inflate caused by
> invalid type conversions).

Submitted.

Re: [Mageia-dev] Freeze push: Thunderbird

[nicolas vigier]

On Thu, 22 Mar 2012, Funda Wang wrote:

> Errr, you may want to submit thunderbird-l10n also.

I forgot this one. Submitted now.