Re: [Mageia-dev] HEADSUP: Full git clone of all package specs (with history)
On Saturday 23 March 2013, Colin Guthrie wrote: > 'Twas brillig, and Colin Guthrie at 22/03/13 09:32 did gyre and gimble: > > Hi, > > > > Just to avoid a crazy amount of scripting with svn checkouts and such > > like, I've set running a git svn clone of the cauldron package > > subversion tree. > That said, running git blame takes *ages* even on an SSD drive. It was > at least a couple minutes to display the results of a blame on a spec file. > Let me remind you of the other suggestion: Put each package in a separate git repo, and then use "submodules" to bind all of them together into the "Mageia" repo.. IMHO, keeping a cross-package fully-connected history (the SVN way) is not worth it. OTOH, having a commit (in the "Mageia" repo) which means "all packages are OK now, they can be built" is closer to what a distro would need. -- Say NO to spam and viruses. Stop using Microsoft Windows!
[Mageia-dev] Freeze push: ffmpeg, mplayer
Hello, Could ffmpeg 1.1.4 be pushed into both core and tainted? It fixed a lot of security vulnerabilities: http://www.ffmpeg.org/security.html Please note that mplayer is needed to be rebuilt against latest ffmpeg also, in both core and tainted. Regards.
[Mageia-dev] Freeze push: opera-12.15
Hello, Could opera-12.15 be pushed? It fixed several security problems as stated here: http://www.opera.com/docs/changelogs/unified/1215/ Regards.
[Mageia-dev] Freeze push: postgresql-(8.4,9.0,9.1,9.2)
Hello, Could postgresql-(8.4,9.0,9.1,9.2) be pushed to fix several security Vulnerabilities? CVE-2013-1899, CVE-2013-1900, CVE-2013-1901 Regards.
Re: [Mageia-dev] Update to boost-1.53 ?
On 04/04/13 14:24, Angelo Naselli wrote: Barry i cannot test this now, but if i understood correctly the problem and talking to libyui developer this patch should work. Can you test it and tell me if it's ok please? Thanks Angelo I'll try it tomorrow - been out most of the day.
Re: [Mageia-dev] automated installer testing
On Thu, 04 Apr 2013, Nicolas Lécureuil wrote: > Le jeudi 28 mars 2013 13:57:11 Glen Ogilvie a écrit : > > Hi, > > > > Has anyone done, or thought about, setting up some automated testing > > of the Mageia installer? > > > > I am thinking something based on: > > https://wiki.mageia.org/en/Auto_inst, testing inside a VM, with > > a range of different installer configurations, like: > > > > * different languages > > * Free / non-free > > * package selections, minimal, full, custom > > * partitioning optons > > * LVM options > > * encryption options > > * filesystem types > > * software raid options > > * known error cases (too small / filesystem), /boot on something not > > supported * grub and grub2 > > * different CPUs, RAM, architectures. > > > > I am thinking that if we had an auto-inst, with maybe 50 or so > > different test cases, all of which would then be verified by an ssh > > script connecting to the VM, or something like that. > > > > I've found 3 bugs recently, all of which would have been able to be > > detected by something like what I am suggesting. > > > > > > Suggestions so far are: > > > > nicolas vigier: > > * For automatic testing it would be possible to use OS-autoinst : > > http://www.os-autoinst.org/ > > * What we need is someone to add support for Mageia installer : > > https://github.com/bmwiedemann/os-autoinst/tree/master/distri > > > > Pierre-Malo Deniélou: > > "Great idea. Can you prototype it? We should use something like that for > > mageia 4." > > > > Anne Nicolas: > > "I remember some people starting something about it Furthermore it could > > be interested to have some virtualization for basic tests once rebooted" > > > > Regards > > Glen Ogilvie > > we should look to openQA too. ( https://github.com/bmwiedemann/openQA ) > but seems it needs a huge work to adapt but i think t's worth it openQA is a web frontent for OS-autoinst.
Re: [Mageia-dev] automated installer testing
Le jeudi 28 mars 2013 13:57:11 Glen Ogilvie a écrit : > Hi, > > Has anyone done, or thought about, setting up some automated testing > of the Mageia installer? > > I am thinking something based on: > https://wiki.mageia.org/en/Auto_inst, testing inside a VM, with > a range of different installer configurations, like: > > * different languages > * Free / non-free > * package selections, minimal, full, custom > * partitioning optons > * LVM options > * encryption options > * filesystem types > * software raid options > * known error cases (too small / filesystem), /boot on something not > supported * grub and grub2 > * different CPUs, RAM, architectures. > > I am thinking that if we had an auto-inst, with maybe 50 or so > different test cases, all of which would then be verified by an ssh > script connecting to the VM, or something like that. > > I've found 3 bugs recently, all of which would have been able to be > detected by something like what I am suggesting. > > > Suggestions so far are: > > nicolas vigier: > * For automatic testing it would be possible to use OS-autoinst : > http://www.os-autoinst.org/ > * What we need is someone to add support for Mageia installer : > https://github.com/bmwiedemann/os-autoinst/tree/master/distri > > Pierre-Malo Deniélou: > "Great idea. Can you prototype it? We should use something like that for > mageia 4." > > Anne Nicolas: > "I remember some people starting something about it Furthermore it could > be interested to have some virtualization for basic tests once rebooted" > > Regards > Glen Ogilvie we should look to openQA too. ( https://github.com/bmwiedemann/openQA ) but seems it needs a huge work to adapt but i think t's worth it
Re: [Mageia-dev] Headsup: KDE 4.10.2 is landing on cauldron...
Nicolas Lécureuil skrev 4.4.2013 13:59: Le jeudi 4 avril 2013 13:14:01 Thomas Backlund a écrit : Hi, seems our KDE guys forgot to announce it so I do it... sorry i got a pb in my mailer :( i wrote a mail but seems it didn't pass the ML see it : Hello, the "maybe" last KDE Update will start in some minutes. KDE and Telepathy-kde will be updated. sorry again :( No worries, it happends... :) please notify the list when its all done -- Thomas
Re: [Mageia-dev] possible security issues affecting Cauldron (please help)
And of course as soon as I send this a bunch of new ones show up today. See the bottom for the additional ones. mediawiki needs updated: https://bugs.mageia.org/show_bug.cgi?id=3448 v8 needs updated: https://bugs.mageia.org/show_bug.cgi?id=8567 libvirt CVE-2013-1766 (see comment 11): https://bugs.mageia.org/show_bug.cgi?id=6526 not sure if all issues in xen are fixed: https://bugs.mageia.org/show_bug.cgi?id=6931 util-linux CVE-2013-0157: https://bugs.mageia.org/show_bug.cgi?id=8615 nginx possible spec change needed: https://bugs.mageia.org/show_bug.cgi?id=9268 openstack-keystone CVE-2013-1865: https://bugs.mageia.org/show_bug.cgi?id=9473 Just added -- nrpe CVE-2013-1362: https://bugs.mageia.org/show_bug.cgi?id=9615 ffmpeg needs updated to 1.1.4: https://bugs.mageia.org/show_bug.cgi?id=9616 postgresql packages need updated: https://bugs.mageia.org/show_bug.cgi?id=9617 puppet needs updated to 2.7.21: http://lwn.net/Vulnerabilities/542701/
Re: [Mageia-dev] freeze push: drakx-installer-stage2
Thierry Vignaud skrev 4.4.2013 19:59: Hi please let in drakx-installer-stage2. It has a better fix for mga#9326 (covering uses of draklive we don't use for now). It also logs when ignoring some dmraid devices, which I hope should help some bug reports. details: = - force loading NSS modules (mga#9326) - log ignored dmraid devices (might help mga#9467) - drakx-in-chroot: o always copy /etc/resolv.conf again thx Submitted. -- Thomas
[Mageia-dev] freeze push: drakx-installer-stage2
Hi please let in drakx-installer-stage2. It has a better fix for mga#9326 (covering uses of draklive we don't use for now). It also logs when ignoring some dmraid devices, which I hope should help some bug reports. details: = - force loading NSS modules (mga#9326) - log ignored dmraid devices (might help mga#9467) - drakx-in-chroot: o always copy /etc/resolv.conf again thx
[Mageia-dev] possible security issues affecting Cauldron (please help)
Since we're getting close to the end, I just wanted to make sure everyone was aware of possible security issues affecting Cauldron, so we can try to get these fixed. mediawiki needs updated: https://bugs.mageia.org/show_bug.cgi?id=3448 v8 needs updated: https://bugs.mageia.org/show_bug.cgi?id=8567 libvirt CVE-2013-1766 (see comment 11): https://bugs.mageia.org/show_bug.cgi?id=6526 not sure if all issues in xen are fixed: https://bugs.mageia.org/show_bug.cgi?id=6931 util-linux CVE-2013-0157: https://bugs.mageia.org/show_bug.cgi?id=8615 nginx possible spec change needed: https://bugs.mageia.org/show_bug.cgi?id=9268 openstack-keystone CVE-2013-1865: https://bugs.mageia.org/show_bug.cgi?id=9473
Re: [Mageia-dev] M3 beta - where to report problems?
On 04/04/2013 10:59 AM, Anne Wilson wrote: Not much progress. My usual method of editing the kernel line to get a level 3 boot doesn't work - same blank (but lit) screen. Failsafe appears to be doing better - at least I can see messages. It reaches Reached target Multi-User Reached target Graphical Interface and there it sticks. Does that give any clue as to what is failing, and what I need to do to rescue the system? Boot a rescue disk and mount your root partition. In /etc/systemd/system you should see a symlink like: lrwxrwxrwx 1 root root 36 Mar 29 11:00 default.target -> /lib/systemd/system/runlevel5.target Just remove this and re-symlink to /lib/systemd/system/runlevel3.target and you should get a level 3 boot.
Re: [Mageia-dev] Update to boost-1.53 ?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Il 04/04/2013 17:29, Olivier Blin ha scritto: > Angelo Naselli writes: > >>> Hi, The problem is in this build log:- >>> http://mtf.no-ip.co.uk/pub/linux/barjac/distrib/cauldron/x86_64/log/libyui-2.42.4-0.git20130107.3.mga3.src.rpm/build.0.20130328124443.log >> >> >>> Barry i cannot test this now, but if i understood correctly the problem >> and talking to libyui developer this patch should work. >> >> Can you test it and tell me if it's ok please? > > Hi, > > It does not seem your patch will fix this build issue, there is no > error in YUIException.h Well the line /home/baz/rpmbuild/BUILD/libyui-2.42.4-623354b/src/YApplication.cc:63:5 is YUI_CHECK_NEW( priv ); and the definition of YUI_CHECK_NEW is in YUIException.h. But probably that does not fixing "no match for 'operator!" because it probably doesn't work for != or == either. It's just a try, as suggested by libyui developers. Unfortunately as i said i cannot test it here because i don't have cauldron :/ > > Did you try the one I already mentionned in this thread earlier? > > Quoting below: > > We could backport this in boost 1.53 to fix libyui: > https://svn.boost.org/trac/boost/changeset/82103 > > See https://svn.boost.org/trac/boost/ticket/7809 (libyui is built > with -std=c++0x) > No, for the same reason as above, sorry. Angelo -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlFdoM0ACgkQqEs9DA4DquDfPgCcD8EsstuOfHBUB5+AH8Yx5CVU r4MAnRYwGXF2tn+tkxI7WDqt/X44O5tA =AmXL -END PGP SIGNATURE-
Re: [Mageia-dev] Update to boost-1.53 ?
Angelo Naselli writes: >> Hi, The problem is in this build log:- >> http://mtf.no-ip.co.uk/pub/linux/barjac/distrib/cauldron/x86_64/log/libyui-2.42.4-0.git20130107.3.mga3.src.rpm/build.0.20130328124443.log > > Barry i cannot test this now, but if i understood correctly the problem > and talking to libyui developer this patch should work. > > Can you test it and tell me if it's ok please? Hi, It does not seem your patch will fix this build issue, there is no error in YUIException.h Did you try the one I already mentionned in this thread earlier? Quoting below: We could backport this in boost 1.53 to fix libyui: https://svn.boost.org/trac/boost/changeset/82103 See https://svn.boost.org/trac/boost/ticket/7809 (libyui is built with -std=c++0x) -- Olivier Blin - blino
Re: [Mageia-dev] freeze push: drakx-installer-stage2 & drakxtools
Thierry Vignaud skrev 4.4.2013 17:03: Hi Please let in drakx-installer-stage2 & drakxtools. drakx-installer-stage2 fixes missing groups in live CDs (mga#9326). drakxtools fixes writing bogus "root=/dev/" in bootloader config (mga#8717) drakx-installer-stage2: = - drakx-in-chroot: o do not copy /etc/resolv.conf in chroot if not using either remote display or remote repository (thus fixing goup lookups, mga#9326) drakxtools: - bootloader-config: o fix adding bogus bootloader entries (root=/dev/) when silently failing to lookup / partition (mga#8717) o try harder to lookup / partition y looking at mounted points (mga#8717) thx submitted. -- Thomas
Re: [Mageia-dev] M3 beta - where to report problems?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/04/13 17:50, Anne Wilson wrote: > > This is an Acer Aspire One 533, with Intel N550 chipset, everything > on-board. I wasn't doing anything unusual, so there does seem to > be a real problem. Tomorrow I'll try to get a console login - is > there a boot log that I could rename to keep it so that you can see > what went wrong? Maybe some other logs too? I don't want to > jeopardise the chances of finding the cause of this. > Not much progress. My usual method of editing the kernel line to get a level 3 boot doesn't work - same blank (but lit) screen. Failsafe appears to be doing better - at least I can see messages. It reaches Reached target Multi-User Reached target Graphical Interface and there it sticks. Does that give any clue as to what is failing, and what I need to do to rescue the system? Anne -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlFdlToACgkQj93fyh4cnBdB+gCfdXhYmJtw/Eo5l79EDlS3yose jUcAnjxI4SnlAsUYqKP+k053NkQVkM4e =c5Ia -END PGP SIGNATURE-
Re: [Mageia-dev] Freeze push: rpm-mageia-setup 1.170
David Walser writes: > Indeed, please do not push this. This is still being worked on. I believe I've found the fix for this minor regression, which was fixed by the fix I proposed previously, but the other problem Luc uncovered actually was a pre-existing bug which has just been uncovered by this: https://bugs.mageia.org/show_bug.cgi?id=3697#c21 This fixes the minor regression without reverting the fix for the major problem Thierry's change was trying to fix in the first place, by fixing the major problem in a more proper way.
[Mageia-dev] freeze push: drakx-installer-stage2 & drakxtools
Hi Please let in drakx-installer-stage2 & drakxtools. drakx-installer-stage2 fixes missing groups in live CDs (mga#9326). drakxtools fixes writing bogus "root=/dev/" in bootloader config (mga#8717) drakx-installer-stage2: = - drakx-in-chroot: o do not copy /etc/resolv.conf in chroot if not using either remote display or remote repository (thus fixing goup lookups, mga#9326) drakxtools: - bootloader-config: o fix adding bogus bootloader entries (root=/dev/) when silently failing to lookup / partition (mga#8717) o try harder to lookup / partition y looking at mounted points (mga#8717) thx
Re: [Mageia-dev] Update to boost-1.53 ?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> Hi, The problem is in this build log:-
> http://mtf.no-ip.co.uk/pub/linux/barjac/distrib/cauldron/x86_64/log/libyui-2.42.4-0.git20130107.3.mga3.src.rpm/build.0.20130328124443.log
>
>
>
> I have builds of boost-1.53 in here
> http://mtf.no-ip.co.uk/pub/linux/barjac/distrib/cauldron/x86_64/media/extra/release/
>
> and
> http://mtf.no-ip.co.uk/pub/linux/barjac/distrib/cauldron/i586/media/extra/release/
>
> media-info is up to date.
>
> Thanks, Barry
>
Barry i cannot test this now, but if i understood correctly the problem
and talking to libyui developer this patch should work.
Can you test it and tell me if it's ok please?
Thanks
Angelo
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iEYEARECAAYFAlFdfxIACgkQqEs9DA4DquBWiACgkPTPxVHaUcWxEVAmyrZ2FzGN
x94AoI6W7dDPTBJ5SEAGf7YH1NhL3cMt
=xU47
-END PGP SIGNATURE-
diff --git a/src/YUIException.h b/src/YUIException.h
index f0dcb21..91ee5a0 100644
--- a/src/YUIException.h
+++ b/src/YUIException.h
@@ -147,7 +147,7 @@ class YWidget;
#define YUI_CHECK_NEW( PTR )\
do \
{ \
- if ( ! (PTR) ) \
+ if ( (PTR == 0) ) \
{ \
YUI_THROW( YUIOutOfMemoryException() ); \
} \
@@ -162,7 +162,7 @@ class YWidget;
#define YUI_CHECK_PTR( PTR )\
do \
{ \
- if ( ! (PTR) ) \
+ if ( (PTR == 0) ) \
{ \
YUI_THROW( YUINullPointerException() ); \
} \
Re: [Mageia-dev] Freeze push: rpm-mageia-setup 1.170
Thierry Vignaud writes: > On 4 April 2013 09:12, Luc Menut wrote: > > Please, can someone push rpm-mageia-setup 1.170 ? > > > > It fixes a regression introduced with 1.168: all the directories found by > > find-lang are not owned by packages when --with-man is used (mga 3697c10). > > err people disagree on this BR! Indeed, please do not push this. This is still being worked on.
Re: [Mageia-dev] freeze push 389-ds-base
Thomas Spuhler writes: > It also fixes security issue mga Bug # 9605 Ping? This fixes CVE-2013-1897. https://bugs.mageia.org/show_bug.cgi?id=9605
Re: [Mageia-dev] freeze push: firefox-beta & firefox-beta-l10n
On 3 April 2013 21:45, Thierry Vignaud wrote: >> Please let in firefox-beta & firefox-beta-l10n >> they doesn't affect other packages are not on the install DVD. >> thx > > there was an issue installing two files. > I've fixed that. > Can you resubmit it? > thx ping?
Re: [Mageia-dev] Headsup: KDE 4.10.2 is landing on cauldron...
Le jeudi 4 avril 2013 13:14:01 Thomas Backlund a écrit : > Hi, > > seems our KDE guys forgot to announce it so I do it... > sorry i got a pb in my mailer :( i wrote a mail but seems it didn't pass the ML see it : Hello, the "maybe" last KDE Update will start in some minutes. KDE and Telepathy-kde will be updated. sorry again :(
[Mageia-dev] Headsup: KDE 4.10.2 is landing on cauldron...
Hi, seems our KDE guys forgot to announce it so I do it... -- Thomas
Re: [Mageia-dev] Update to boost-1.53 ?
On 03/04/13 17:05, Angelo Naselli wrote: Il 02/04/2013 02:31, Barry Jackson ha scritto: So now only libyui remains. Oops, i've just saw it now sorry. What is the issue? I could try to work on it tonight at home should i build boost locally first or it's on some mirrors? Angelo Hi, The problem is in this build log:- http://mtf.no-ip.co.uk/pub/linux/barjac/distrib/cauldron/x86_64/log/libyui-2.42.4-0.git20130107.3.mga3.src.rpm/build.0.20130328124443.log I have builds of boost-1.53 in here http://mtf.no-ip.co.uk/pub/linux/barjac/distrib/cauldron/x86_64/media/extra/release/ and http://mtf.no-ip.co.uk/pub/linux/barjac/distrib/cauldron/i586/media/extra/release/ media-info is up to date. Thanks, Barry
Re: [Mageia-dev] Freeze push: rpm-mageia-setup 1.170
On 4 April 2013 09:12, Luc Menut wrote: > Hello, > > Please, can someone push rpm-mageia-setup 1.170 ? > > It fixes a regression introduced with 1.168: all the directories found by > find-lang are not owned by packages when --with-man is used (mga #3697c10). err people disagree on this BR!
Re: [Mageia-dev] [changelog] [RPM] cauldron core/release apache-2.4.4-6.mga3
Le 04/04/2013 04:01, luigiwalser a écrit : luigiwalser 2.4.4-6.mga3: + Revision: 407569 - fix userdir configuration again Changing the redirection operator is indeed a fix, but the real question is: why mess with default upstream configuration ? Is there an actual and objective reason in the distribution to provide by default a cgi-ready directory in each user public directory ? -- BOFH excuse #446: Mailer-daemon is busy burning your message in hell.
[Mageia-dev] Freeze push: rpm-mageia-setup 1.170
Hello, Please, can someone push rpm-mageia-setup 1.170 ? It fixes a regression introduced with 1.168: all the directories found by find-lang are not owned by packages when --with-man is used (mga #3697c10). regards, Luc -- Luc Menut
