Re: [Mageia-dev] freeze push: drakconf
2011/5/19 Thierry Vignaud : > Hi > > Please let in drakconf: > - use proper unicode character for (TM) (mga#473) > - updated translations > done -- Anne http://www.mageia.org
Re: [Mageia-dev] freeze push: drakx-installer-stage2
2011/5/19 Thierry Vignaud : > On 19 May 2011 03:05, Thierry Vignaud wrote: >> Hi >> >> Please let in drakx-installer-stage2: >> - advertize LibreOffice instead of OpenOffice.org (mga#1323) >> - fix reading security level with new msec (mga#332) >> - translations updates > > Please note that you need to push meta-task too so that the > oooffice->libreoffice > change is OK done > -- Anne http://www.mageia.org
Re: [Mageia-dev] freeze push: drakxtools
2011/5/19 Thierry Vignaud : > Hi > > Please let in draxktools: > - draksound: > o Robustify the PulseAudio configs (don't try and write files if they > do not exists. Doing so previously would result in blank files that then > causes problems when installing PulseAudio as the "config" files are not > overwritten properly which can result in broken PA startup) > o Remove the "Enable 5.1..." option. This is now done via card profiles > in native GUIs for GNOME and KDE (or pavucontrol) > o Remove the "Enable user switching..." option as it relies on HAL > which is deprecated. > - scannerdrake: use skanlite instead of kooka > - any.pm: fix faces icons paths (mga#1315) > - fix reading security level with new msec (mga#332) > done -- Anne http://www.mageia.org
Re: [Mageia-dev] Security Update Process
Le 18/05/2011 22:38, Jérôme (saispo) Soyer a écrit : > On Mon, May 16, 2011 at 4:45 PM, Stew Benedict wrote: >> OK, >> >> Mageia 1 is approaching quickly and we need to get our process in place >> for security updates. We talked a bit about it a few weeks ago, and I >> started a wiki page, but it needs more detail. Anne and I chatted on IRC >> and it looks like we'll want to cutoff the "on the iso " updates at the >> end of this week, so we need a process in place to release post-iso updates. >> >> ref: http://mageia.org/wiki/doku.php?id=security >> >> As I see it, initially we need, in no particular order: >> >> 1) a means to build updates for the release (iurt setup for mga1?) >> 2) a means to publish updates (mail list, web page) >> 3) a means to manage/track the updates (bugzilla?) >> 4) work out/publish the process so we all know how it works >> >> And then of course we need people to be aware of vulnerabilities as they >> are exposed. For now, we'll have be be slightly trailing until we can >> show a history of releasing updates and hopefully gain access to the >> closed list to get access to embargoed issues. Once that happens we will >> possibly need additional infrastructure changes to keep the work >> non-public before the embargo date. >> >> osvdb has a nice email aggregator that sends all the distro update >> announcements, and the oss-security list has many of the CVE requests. >> Unfortunately, my personal time hasn't allowed much more than a quick >> read as they go by :/ I know many of you have been doing security >> related bug reports and updates, which is great, thank-you. If anyone >> wants to take a larger role in managing the process I'm more than happy >> to let that happen. While I have experience, the time I'm able to commit >> is less than helpful. >> >> Comments, volunteers? >> >> >> >> -- >> Stew Benedict >> New Tazewell, TN >> >> >> > > Ok for me to integrate the team, reporting CVE, fixing them quickly as > i can, and enhancing security in the distro :) Ok for me too, integrate the team and work at reporting and fixing CVE, and/or enhancing security of mga! -- Sandro Cazzaniga - https://lederniercoupdarchet.wordpress.com IRC: Kharec (irc.freenode.net) Software/Hardware geek Conceptor Magnum's Coordinator/editor (http://wiki.mandriva.com/fr/Magnum) Mageia and Mandriva contributor
[Mageia-dev] Freeze push request: tomcat6
- Replace %{_tmppath} in %%pre/posttrans with another macro defined in the spec,
%%{tmpbackup}; %{_tmppath} evaluates to /home/iurt/rpm/tmp (probably due to a
.rpmmacros in /home/iurt ?). This should fix (mga#1316)
https://bugs.mageia.org/show_bug.cgi?id=1316
--
Ahmad Samir
[Mageia-dev] Freeze push request: kdenlive
Please submit kdenlive, this adds a suggests on oxygen-icon-theme, for users installing this package and using DE's other than KDE4; without the icon theme the GUI doesn't have any icons, which is a drawback (and almost anti-HIG, as visual recognition is a major feature in today's desktops). Arguably the user can edit kdeglobals and change the icon theme that KDE uses to some other theme, but that's is not user friendly (let alone that not all users will know about that file). -- Ahmad Samir
Re: [Mageia-dev] Freeze push: sound-scripts
On 19 May 2011 01:26, Colin Guthrie wrote: > Fixes asound.state path to allow saved state to be restored properly on > boot. > > Also I made some fixes in soft for draksound to remove obsolete options > and to not create PA configs when it's not installed (a thus preventing > a clean install due to .rpmnew confusion)... not sure of the process to > bundle it up and do a fresh release of drakxtools? I think from the NEWS > file that there are other unreleased changes there waiting too Thierry Vignaud has already packaged a new drakxtools from soft with your commits (among other things), and asked for a freeze push. > > Cheers > > Col > > -- > > Colin Guthrie > mageia(at)colin.guthr.ie > 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/] > -- Ahmad Samir
[Mageia-dev] freeze push: drakconf
Hi Please let in drakconf: - use proper unicode character for (TM) (mga#473) - updated translations
[Mageia-dev] freeze push: mgaonline
Hi Please let in mgaonline (security): - use https protocol instead of http in order to retrieve distro list (like in MDV)
Re: [Mageia-dev] freeze push: drakx-installer-stage2
On 19 May 2011 03:05, Thierry Vignaud wrote: > Hi > > Please let in drakx-installer-stage2: > - advertize LibreOffice instead of OpenOffice.org (mga#1323) > - fix reading security level with new msec (mga#332) > - translations updates Please note that you need to push meta-task too so that the oooffice->libreoffice change is OK
[Mageia-dev] freeze push: drakx-installer-stage2
Hi Please let in drakx-installer-stage2: - advertize LibreOffice instead of OpenOffice.org (mga#1323) - fix reading security level with new msec (mga#332) - translations updates
[Mageia-dev] freeze push: drakxtools
Hi Please let in draxktools: - draksound: o Robustify the PulseAudio configs (don't try and write files if they do not exists. Doing so previously would result in blank files that then causes problems when installing PulseAudio as the "config" files are not overwritten properly which can result in broken PA startup) o Remove the "Enable 5.1..." option. This is now done via card profiles in native GUIs for GNOME and KDE (or pavucontrol) o Remove the "Enable user switching..." option as it relies on HAL which is deprecated. - scannerdrake: use skanlite instead of kooka - any.pm: fix faces icons paths (mga#1315) - fix reading security level with new msec (mga#332)
Re: [Mageia-dev] [1376] update for 0.95
On 18 May 2011 22:03, wrote: > Revision 1376 Author ennael Date 2011-05-18 22:03:49 +0200 (Wed, 18 May > 2011) > > Log Message > > update for 0.95 > > Modified Paths > > drakx-net/trunk/ChangeLog > drakx-net/trunk/Makefile > drakx-net/trunk/NEWS We do not need to update ChangeLog every commit. Besides svn2cl is broken and keep readding the same logs again & again. So I think it's best not to update ChangeLogs for now > Modified: drakx-net/trunk/ChangeLog > === > --- drakx-net/trunk/ChangeLog 2011-05-18 19:55:15 UTC (rev 1375) > +++ drakx-net/trunk/ChangeLog 2011-05-18 20:03:49 UTC (rev 1376) > @@ -1,3 +1,17 @@ > +2011-05-18 19:55 > + > + * data/pixmaps/wifi-020.png, data/pixmaps/wifi-040.png, > + data/pixmaps/wifi-060.png, data/pixmaps/wifi-080.png, > + data/pixmaps/wifi-100.png, data/pixmaps/wireless-128.png, > + data/pixmaps/wireless-16.png, data/pixmaps/wireless-24.png, > + data/pixmaps/wireless-32.png, data/pixmaps/wireless-48.png, > + data/pixmaps/wireless-52.png, data/pixmaps/wireless-64.png: > + update wifi status icons to be more visible > + > +2011-05-14 21:38 > + > + * ChangeLog, Makefile, NEWS: update translations > + > 2011-05-12 23:52 > > * po/fr.po: Update of the Italian po file for draklive-install with > @@ -12,6 +26,20 @@ > Update of the French po file for drakx-kbd-mouse-x11 with the > latest file from Tx. > > +2011-05-12 23:52 > + > + * po/fr.po: Update of the Italian po file for draklive-install with > + the po file from Transifex (Marcello request) > + Update of the French po file for drakx-net and drakx_share with > + the latest files from Tx. > + > +2011-05-12 19:56 > + > + * po/it.po: Update of the Italian translations for almost every > + project with the po files from Transifex. > + Update of the French po file for drakx-kbd-mouse-x11 with the > + latest file from Tx. > + > 2011-05-12 19:28 > > * po/de.po: updated German translation of drakx-net >
Re: [Mageia-dev] [1385] More PA config writing robustness
On 19 May 2011 01:06, wrote:
> Revision 1385 Author colin Date 2011-05-19 01:06:54 +0200 (Thu, 19 May 2011)
>
> Log Message
>
> More PA config writing robustness
(...)
> @@ -330,7 +333,7 @@
> if ($old_value ne $is_pulseaudio_enabled) {
> require any;
> any::ask_for_X_restart($in);
> - }
> +}
> };
please run "svn diff" before commiting in order not to commit
unrelated spaces changes
[Mageia-dev] Freeze push: sound-scripts
Fixes asound.state path to allow saved state to be restored properly on boot. Also I made some fixes in soft for draksound to remove obsolete options and to not create PA configs when it's not installed (a thus preventing a clean install due to .rpmnew confusion)... not sure of the process to bundle it up and do a fresh release of drakxtools? I think from the NEWS file that there are other unreleased changes there waiting too Cheers Col -- Colin Guthrie mageia(at)colin.guthr.ie 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] Small remarks regarding mga 1 RC update from mdv 2010.2
Le 19/05/2011 00:12, Ahmad Samir a écrit : > On 18 May 2011 23:44, Daniel Le Berre wrote: >> Hi guys, >> >> I am currently updating a MDV 2010.2 with MGA 1 RC (32 bits). >> So far, so good (the install will take more than one hour, on a PIV). >> >> I like pretty much the artwork. Very good job! >> >> I noted a few details that are not crucial but may help making mga better :) >> >> 1) When I launched the installation (using a DVD), I was a bit affraid >> when I saw only Install in the boot menu, no update choice. >> > > That's what it always said in Mandriva, even when users intended to > upgrade to the new release included on the DVD. > > [] > But this is no longer Mandriva, so there is no reason to stick with that :) Regarding the end of the installation: I was unable to launch X because my nvidia driver packages had not been updated. I uppdated those drivers with "urpmi nvidia" on the command line (I played a bit with drakxconf before with no luck) and everything went fine after rebooting the system. Overall, the update went smoothly. Daniel
Re: [Mageia-dev] Small remarks regarding mga 1 RC update from mdv 2010.2
On 18 May 2011 23:44, Daniel Le Berre wrote: > Hi guys, > > I am currently updating a MDV 2010.2 with MGA 1 RC (32 bits). > So far, so good (the install will take more than one hour, on a PIV). > > I like pretty much the artwork. Very good job! > > I noted a few details that are not crucial but may help making mga better :) > > 1) When I launched the installation (using a DVD), I was a bit affraid > when I saw only Install in the boot menu, no update choice. > That's what it always said in Mandriva, even when users intended to upgrade to the new release included on the DVD. [] -- Ahmad Samir
[Mageia-dev] Small remarks regarding mga 1 RC update from mdv 2010.2
Hi guys, I am currently updating a MDV 2010.2 with MGA 1 RC (32 bits). So far, so good (the install will take more than one hour, on a PIV). I like pretty much the artwork. Very good job! I noted a few details that are not crucial but may help making mga better :) 1) When I launched the installation (using a DVD), I was a bit affraid when I saw only Install in the boot menu, no update choice. In some ways, it makes sense since MGA 1 will be the first release of mageia but I guess that the majority of mageia adopters will migrate from mandriva so I wonder if an entry "Install/update" would not be better than just Install, since the mandriva update is properly detected afterward? 2) I noted something disturbing on the install screen: the rectangular area dedicated to Installation with the images and the progress bar is very close to the right side. I had the impression that I was mising some part of the screen. That might be dictated by the size needed to display all the information but IMHO it would be much nicer if the space from the right side could be similar to the space between the left side and the menu. My 2 cents, Daniel
Re: [Mageia-dev] [98858] SILENT: rename README.RPM to README.urpmi so it is printed by urpmi
On 15.05.2011 01:19, r...@mageia.org wrote: > Log Message > > SILENT: rename README.RPM to README.urpmi so it is printed by urpmi Probably better to make it README.install.urpmi so that it is printed only on initial installation. > > Modified Paths > > * cauldron/mediawiki/current/SPECS/mediawiki.spec -- Anssi Hannula
[Mageia-dev] current temporary tainted (codecs) submission policy
This is draft following conclusions meeting from today (someone correct me if i'm wrong): - permanent BS modification is postponed until after release, so for now we will have temporary solution - mdv "policy" will be chosen temporarily to decide wether to enable patented options go into tainted or core (plf stuff would go to tainted); a strict policy will be made later on - BS will be adapted to change distsuffix to a temporary one that will be higher in version than mga - submission to tainted will be done by adding '--define section=tainted' to mgarepo (wait until BS is fixed, and bother sysadmin until "fixed" :-P ) - some packages don't have all codecs enabled atm if i've forgotten anything, or i say incorrectness, please correct me...
Re: [Mageia-dev] Security Update Process
Le lundi 16 mai 2011 à 18:08 +0200, Thierry Vignaud a écrit : > On 16 May 2011 18:05, Ahmad Samir wrote: > >>> Mageia 1 is approaching quickly and we need to get our process in place > >>> for security updates. We talked a bit about it a few weeks ago, and I > >>> started a wiki page, but it needs more detail. Anne and I chatted on IRC > >>> and it looks like we'll want to cutoff the "on the iso " updates at the > >>> end of this week, so we need a process in place to release post-iso > >>> updates. > >>> > >>> ref: http://mageia.org/wiki/doku.php?id=security > >>> > >>> As I see it, initially we need, in no particular order: > >>> > >>> 1) a means to build updates for the release (iurt setup for mga1?) > >> > >> A iurt setup for mga1 will exist anyway, what is missing is a way to > >> later upload to non public place. > >> Initially, we can just setup youri to restrict submitting a build to > >> updates_testing or updates to the secteam and it should be enough. > >> > > > > Ideally packagers should be able to submit to update_testing when they > > want to push a fixed package to ask for testing. So restricting > > submitting to updates sounds more logical? > > What's more that matches what we were doing back @mdv. > The process was: > - trusted packagers upload into main/testing, > - all packager can upload into contrib/testing, > - ticket (for main/*) is opened & assigned to qa > - people || qa test > - if tests succeed, ticket is assigned to secteam > - secteam rebuild with its own sig & push the package I would propose the following : - packagers can upload to */updates_testing ( with some limitation and specific check ) - ticket are opened for everything, assigned to QA - people || qa test - if tests are ok, package is moved to */updates I see no need to rebuild again on a different system, as we do not have the ressources. -- Michael Scherer
Re: [Mageia-dev] Security Update Process
On Mon, May 16, 2011 at 4:45 PM, Stew Benedict wrote: > OK, > > Mageia 1 is approaching quickly and we need to get our process in place > for security updates. We talked a bit about it a few weeks ago, and I > started a wiki page, but it needs more detail. Anne and I chatted on IRC > and it looks like we'll want to cutoff the "on the iso " updates at the > end of this week, so we need a process in place to release post-iso updates. > > ref: http://mageia.org/wiki/doku.php?id=security > > As I see it, initially we need, in no particular order: > > 1) a means to build updates for the release (iurt setup for mga1?) > 2) a means to publish updates (mail list, web page) > 3) a means to manage/track the updates (bugzilla?) > 4) work out/publish the process so we all know how it works > > And then of course we need people to be aware of vulnerabilities as they > are exposed. For now, we'll have be be slightly trailing until we can > show a history of releasing updates and hopefully gain access to the > closed list to get access to embargoed issues. Once that happens we will > possibly need additional infrastructure changes to keep the work > non-public before the embargo date. > > osvdb has a nice email aggregator that sends all the distro update > announcements, and the oss-security list has many of the CVE requests. > Unfortunately, my personal time hasn't allowed much more than a quick > read as they go by :/ I know many of you have been doing security > related bug reports and updates, which is great, thank-you. If anyone > wants to take a larger role in managing the process I'm more than happy > to let that happen. While I have experience, the time I'm able to commit > is less than helpful. > > Comments, volunteers? > > > > -- > Stew Benedict > New Tazewell, TN > > > Ok for me to integrate the team, reporting CVE, fixing them quickly as i can, and enhancing security in the distro :)
Re: [Mageia-dev] Freeze push request: mysql
On Wed, 18 May 2011, Maarten Vanraes wrote: > this release has an additional warning with regards to security reasons: that > mysql is shipped with a passwordless root account, and that you should change > that asap. Done by misc.
Re: [Mageia-dev] freeze push: chromium-browser-{stable, beta, unstable}
On Wed, 18 May 2011, Thierry Vignaud wrote:
> Hi
>
> Please let in freeze push: chromium-browser-{stable,beta,unstable}
> (moving target)
Done.
[Mageia-dev] Freeze push request: mysql
this release has an additional warning with regards to security reasons: that mysql is shipped with a passwordless root account, and that you should change that asap. (i note that this fix is the result of a discussion on #mageia-dev with spturtle, stewb, misc and myself and was validated by my mentor Anssi)
[Mageia-dev] freeze push: chromium-browser-{stable,beta,unstable}
Hi
Please let in freeze push: chromium-browser-{stable,beta,unstable}
(moving target)
chromium-browser-stable:
- new upstream release 11.0.696.68 (stable)
- security fixes
* [64046] High CVE-2011-1799: Bad casts in Chromium WebKit glue.
* [80608] High CVE-2011-1800: Integer overflows in SVG filters.
chromium-browser-beta:
* UI tweaks and performance fixes
chromium-browser-unstable:
* UI, performance, and stability issues
Thx
Re: [Mageia-dev] freeze push: firefox-ext-firebug
On Wed, 18 May 2011, Thierry Vignaud wrote: > Hi > > Please let in firefox-ext-firebug-1.7.1 > It's bug fixes only. Done.
[Mageia-dev] freeze push: firefox-ext-firebug
Hi Please let in firefox-ext-firebug-1.7.1 It's bug fixes only. It only affects users enabling firebug. See http://blog.getfirebug.com/2011/05/13/firebug-1-7-1/ See you
Re: [Mageia-dev] Mageia 1 RC is out
Anne nicolas skrev 18.5.2011 13:56: 2011/5/18 John: On Wed, 18 May 2011 12:44:16 +0200 Anne nicolas wrote: Hi there Sorry about that late mail but as you may have seen RC is out http://blog.mageia.org/en/2011/05/17/final-release-approaching-now-rc-available-for-last-tests/ We released DVDs and dual iso available now on mirrors. Live CDs are a bit postponed due to pb in unionfs. Of course tests needed. Only 13 days left! Priority is all on bugs fixing and especially on release blockers. Enjoy RC! No torrent? should be available during the day, stay tuned Torrents are up and running and should show up soon on every mirror. If you are in a hurry you can grab them here: http://distrib-coffee.ipsl.jussieu.fr/pub/linux/Mageia/iso/cauldron/torrents/ -- Thomas
Re: [Mageia-dev] Mageia 1 RC is out
2011/5/18 John : > On Wed, 18 May 2011 12:44:16 +0200 > Anne nicolas wrote: > >> Hi there >> >> Sorry about that late mail but as you may have seen RC is out >> http://blog.mageia.org/en/2011/05/17/final-release-approaching-now-rc-available-for-last-tests/ >> >> We released DVDs and dual iso available now on mirrors. Live CDs are a >> bit postponed due to pb in unionfs. Of course tests needed. Only 13 >> days left! >> Priority is all on bugs fixing and especially on release blockers. >> >> Enjoy RC! > > No torrent? should be available during the day, stay tuned > > John NZ > -- Anne http://www.mageia.org
Re: [Mageia-dev] Mageia 1 RC is out
On Wed, 18 May 2011 12:44:16 +0200 Anne nicolas wrote: > Hi there > > Sorry about that late mail but as you may have seen RC is out > http://blog.mageia.org/en/2011/05/17/final-release-approaching-now-rc-available-for-last-tests/ > > We released DVDs and dual iso available now on mirrors. Live CDs are a > bit postponed due to pb in unionfs. Of course tests needed. Only 13 > days left! > Priority is all on bugs fixing and especially on release blockers. > > Enjoy RC! No torrent? John NZ
Re: [Mageia-dev] Mageia does not recognize Mandriva installation
2011/5/18 magnus : > > > 2011/5/18 Wolfgang Bornath >> >> To test a system Upgrade from Mandriva I installed Mandriva 2010.2 >> besides my existing Mageia Beta2. >> > Is it an i586 system? OMG! of course, Mandriva is i586, Mageia is x86_64! I should have thought of that! And I really thought I'd discovered my first bug in RC! :( -- wobo
[Mageia-dev] Mageia 1 RC is out
Hi there Sorry about that late mail but as you may have seen RC is out http://blog.mageia.org/en/2011/05/17/final-release-approaching-now-rc-available-for-last-tests/ We released DVDs and dual iso available now on mirrors. Live CDs are a bit postponed due to pb in unionfs. Of course tests needed. Only 13 days left! Priority is all on bugs fixing and especially on release blockers. Enjoy RC! -- Anne http://www.mageia.org
Re: [Mageia-dev] Mageia does not recognize Mandriva installation
2011/5/18 Wolfgang Bornath > To test a system Upgrade from Mandriva I installed Mandriva 2010.2 > besides my existing Mageia Beta2. > > Is it an i586 system? > During installation of Mageia RC the installer did not see the > Mandriva installation, it only offered an update of "Mageia (Cauldron) > 1" or a fresh installation. > > -- > wobo > I have no such problem (one i586, two x86_64 systems) magnus
[Mageia-dev] Next packagers meeting
Hi there We will have our next meeting as usual on #mageia-dev on Freenode at 19h UTC As stable release is very near now here the main topics: - release blocker bugs - planning from now to stable release - svn management for stable switch - secteam review As usual feel free to propose other topics. -- Anne http://www.mageia.org
[Mageia-dev] Mageia does not recognize Mandriva installation
To test a system Upgrade from Mandriva I installed Mandriva 2010.2 besides my existing Mageia Beta2. During installation of Mageia RC the installer did not see the Mandriva installation, it only offered an update of "Mageia (Cauldron) 1" or a fresh installation. -- wobo
