[Mageia-dev] systemd network.service issues
Hi all! So, I've just upgraded my home server to mga2/cauldron. Something seems fishy in the network.service handling, systemd thinks it has failed: # systemctl status network.service network.service - LSB: Bring up/down networking Loaded: loaded (/etc/rc.d/init.d/network) Active: failed (Result: exit-code) since Fri, 16 Mar 2012 05:25:09 +0200; 11min ago CGroup: name=systemd:/system/network.service ├ 4679 /sbin/ifplugd -I -b -i eth0 ├ 4723 /sbin/ifplugd -I -b -i eth1 └ 5372 /sbin/dhclient -q -lf /var/lib/dhcp/dhclient-eth0.leases -pf /var/run/dhclient-eth0.pid -cf /etc/dhclient-eth0.conf... Mar 16 05:25:09 delta.onse.fi ifplugd(eth1)[4723]: Using detection mode: SIOCETHTOOL Mar 16 05:25:09 delta.onse.fi ifplugd(eth1)[4723]: Initialization complete, link beat not detected. Mar 16 05:25:09 delta.onse.fi network[4397]: [161B blob data] Mar 16 05:25:09 delta.onse.fi network[4397]: [14B blob data] Mar 16 05:25:13 delta.onse.fi ifplugd(eth0)[4679]: Link beat detected. Mar 16 05:25:14 delta.onse.fi ifplugd(eth0)[4679]: Executing '/etc/ifplugd/ifplugd.action eth0 up'. Mar 16 05:25:15 delta.onse.fi dhclient[5312]: DHCPREQUEST on eth0 to 255.255.255.255 port 67 Mar 16 05:25:15 delta.onse.fi dhclient[5312]: DHCPACK from 109.204.128.1 Mar 16 05:25:15 delta.onse.fi ifplugd(eth0)[4679]: client: Determining IP information for eth0... done. Mar 16 05:25:15 delta.onse.fi ifplugd(eth0)[4679]: Program executed successfully. Trying to restart it I seem to hit other issues: # systemctl restart network.service Job failed. See system journal and 'systemctl status' for details. # systemctl status network.service network.service - LSB: Bring up/down networking Loaded: loaded (/etc/rc.d/init.d/network) Active: failed (Result: exit-code) since Fri, 16 Mar 2012 05:36:39 +0200; 3s ago Process: 8027 ExecStart=/etc/rc.d/init.d/network start (code=exited, status=1/FAILURE) CGroup: name=systemd:/system/network.service ├ 8195 /sbin/ifplugd -I -b -i eth0 └ 8353 /sbin/dhclient -q -lf /var/lib/dhcp/dhclient-eth0.leases -pf /var/run/dhclient-eth0.pid -cf /etc/dhclient-eth0.conf... Mar 16 05:36:39 delta.onse.fi network[8027]: RTNETLINK answers: File exists Mar 16 05:36:39 delta.onse.fi network[8027]: RTNETLINK answers: File exists Mar 16 05:36:39 delta.onse.fi network[8027]: RTNETLINK answers: File exists Mar 16 05:36:39 delta.onse.fi network[8027]: RTNETLINK answers: File exists Mar 16 05:36:39 delta.onse.fi dhclient[8261]: DHCPREQUEST on eth0 to 255.255.255.255 port 67 Mar 16 05:36:40 delta.onse.fi dhclient[8261]: DHCPACK from 109.204.128.1 Mar 16 05:36:40 delta.onse.fi ifplugd(eth0)[8195]: client: Determining IP information for eth0...NETLINK: Error: File exists Mar 16 05:36:40 delta.onse.fi ifplugd(eth0)[8195]: client: done. Mar 16 05:36:40 delta.onse.fi ifplugd(eth0)[8195]: client: NETLINK: Error: File exists Mar 16 05:36:40 delta.onse.fi ifplugd(eth0)[8195]: Program executed successfully. Any ideas? If not, I'll investigate this myself later. On a related note, I also got dropped to emergency console on first boot, not sure why was that (it didn't tell me the reason... maybe the reason was in another virtual console, but I didn't remember to check there at the time). I just exited the console and it continued to boot... I see the following in systemctl --failed: # systemctl --failed UNIT LOAD ACTIVE SUBJOB DESCRIPTION bootparamd.service loaded ESC[1;31mfailed failedESC[0m SYSV: The bootparamd server allows older Sun workstations to net boot from Linux boxes. It (along with rarp) is rarely used anymore; bootp and dhcp have mostly replaced both of them. fedora-loadmodules.service loaded ESC[1;31mfailed failedESC[0m Load legacy module configuration network.service loaded ESC[1;31mfailed failedESC[0m LSB: Bring up/down networking systemd-modules-load.service loaded ESC[1;31mfailed failedESC[0m Load Kernel Modules -- Anssi Hannula
[Mageia-dev] php pear mga2 upgrade issues (file conflicts)
Hi! I've seen some mga1->mga2 upgrade issues with php-pear packages: file /usr/share/pear/PHPUnit/Extensions/Database/Operation/Exception.php from install of php-pear-DbUnit-1.1.2-1.mga2.noarch conflicts with file from package php-pear-PHPUnit-3.3.17-3.mga1.noarch file /usr/share/pear/PHPUnit/Extensions/SeleniumTestCase/append.php from install of php-pear-PHPUnit_Selenium-1.2.3-1.mga2.noarch conflicts with file from package php-pear-PHPUnit-3.3.17-3.mga1.noarch It looks like php-pear-PHPUnit_Selenium and php-pear-DbUnit were probably splitted from php-pear-PHPUnit and so need "Conflicts: php-pear-PHPUnit < 3.5". Similar issues seem to exist (without closer look) in other pkgs like at least php-pear-File* and php-pear-PHPUnit_Story. Attached is the output of ./check-distro-files-conflicts /mirror/mageia/1/x86_64 \ /mirror/mageia/cauldron/x86_64 | grep php-pear | grep mga2 (check-distro-files-conflicts is the old Pixel's script at http://svn.mandriva.com/viewvc/soft/build_system/distrib/cleaning/check-distro-files-conflicts) -- Anssi Hannula ERROR: conflicting file /usr/bin/plex (pkgs: php-pear-PHP_LexerGenerator-0.4.0-2.mga2.noarch, fpc-2.4.0-2.mga1.i586) ERROR: conflicting file /usr/bin/plex (pkgs: php-pear-PHP_LexerGenerator-0.4.0-2.mga2.noarch, fpc-2.4.0-2.mga1.i586) ERROR: conflicting file /usr/bin/plex (pkgs: php-pear-PHP_LexerGenerator-0.4.0-2.mga2.noarch, fpc-2.4.0-2.mga1.i586) ERROR: conflicting file /usr/share/pear/File/CSV.php (pkgs: php-pear-File_CSV-1.0.0-1.mga2.noarch, php-pear-File-1.3.0-8.mga1.noarch) ERROR: conflicting file /usr/share/pear/File/CSV.php (pkgs: php-pear-File_CSV-1.0.0-1.mga2.noarch, php-pear-File-1.3.0-8.mga1.noarch) ERROR: conflicting file /usr/share/pear/File/CSV.php (pkgs: php-pear-File_CSV-1.0.0-1.mga2.noarch, php-pear-File-1.3.0-8.mga1.noarch) ERROR: conflicting file /usr/share/pear/File/Util.php (pkgs: php-pear-File_Util-1.0.0-1.mga2.noarch, php-pear-File-1.3.0-8.mga1.noarch) ERROR: conflicting file /usr/share/pear/File/Util.php (pkgs: php-pear-File_Util-1.0.0-1.mga2.noarch, php-pear-File-1.3.0-8.mga1.noarch) ERROR: conflicting file /usr/share/pear/File/Util.php (pkgs: php-pear-File_Util-1.0.0-1.mga2.noarch, php-pear-File-1.3.0-8.mga1.noarch) ERROR: conflicting file /usr/share/pear/Horde/Config.php (pkgs: php-pear-Horde_Core-1.8.2-1.mga2.i586, horde-framework-0.0.2-7.mga1.noarch) ERROR: conflicting file /usr/share/pear/Horde/Config.php (pkgs: php-pear-Horde_Core-1.8.2-1.mga2.x86_64, horde-framework-0.0.2-7.mga1.noarch) ERROR: conflicting file /usr/share/pear/Horde/Config.php (pkgs: php-pear-Horde_Core-1.8.2-1.mga2.x86_64, horde-framework-0.0.2-7.mga1.noarch) ERROR: conflicting file /usr/share/pear/Horde/Help.php (pkgs: php-pear-Horde_Core-1.8.2-1.mga2.i586, horde-framework-0.0.2-7.mga1.noarch) ERROR: conflicting file /usr/share/pear/Horde/Help.php (pkgs: php-pear-Horde_Core-1.8.2-1.mga2.x86_64, horde-framework-0.0.2-7.mga1.noarch) ERROR: more conflicting files (pkgs: php-pear-Horde_Core-1.8.2-1.mga2.x86_64, horde-framework-0.0.2-7.mga1.noarch) ERROR: conflicting file /usr/share/pear/Horde/Kolab/Session.php (pkgs: php-pear-Horde_Kolab_Session-1.1.0-1.mga2.noarch, horde-kolab-server-0.5.0-3.mga1.noarch) ERROR: conflicting file /usr/share/pear/Horde/Kolab/Session.php (pkgs: php-pear-Horde_Kolab_Session-1.1.0-1.mga2.noarch, horde-kolab-server-0.5.0-3.mga1.noarch) ERROR: conflicting file /usr/share/pear/Horde/Kolab/Session.php (pkgs: php-pear-Horde_Kolab_Session-1.1.0-1.mga2.noarch, horde-kolab-server-0.5.0-3.mga1.noarch) ERROR: conflicting file /usr/share/pear/Horde/Menu.php (pkgs: php-pear-Horde_Core-1.8.2-1.mga2.i586, horde-framework-0.0.2-7.mga1.noarch) ERROR: more conflicting files (pkgs: php-pear-Horde_Core-1.8.2-1.mga2.i586, horde-framework-0.0.2-7.mga1.noarch) ERROR: conflicting file /usr/share/pear/PHPUnit/Extensions/Database/AbstractTester.php (pkgs: php-pear-PHPUnit-3.3.17-3.mga1.noarch, php-pear-DbUnit-1.1.2-1.mga2.noarch) ERROR: conflicting file /usr/share/pear/PHPUnit/Extensions/Database/AbstractTester.php (pkgs: php-pear-PHPUnit-3.3.17-3.mga1.noarch, php-pear-DbUnit-1.1.2-1.mga2.noarch) ERROR: conflicting file /usr/share/pear/PHPUnit/Extensions/Database/AbstractTester.php (pkgs: php-pear-PHPUnit-3.3.17-3.mga1.noarch, php-pear-DbUnit-1.1.2-1.mga2.noarch) ERROR: more conflicting files (pkgs: php-pear-PHPUnit-3.3.17-3.mga1.noarch, php-pear-DbUnit-1.1.2-1.mga2.noarch) ERROR: conflicting file /usr/share/pear/PHPUnit/Extensions/SeleniumTestCase/append.php (pkgs: php-pear-PHPUnit_Selenium-1.2.3-1.mga2.noarch, php-pear-PHPUnit-3.3.17-3.mga1.noarch) ERROR: conflicting file /usr/share/pear/PHPUnit/Extensions/SeleniumTestCase/append.php (pkgs: php-pear-PHPUnit_Selenium-1.2.3-1.mga2.noarch, php-pear-PHPUnit-3.3.17-3.mga1.noarch) ERROR: conflicting file /usr/share/pear/PHPUnit/Extensions/SeleniumTestCase/append.php (pkgs: php-pear-PHPUnit_Selenium-1.2.3-1.mga2.noarch, php-pear-PHPUnit-3.3.17-3.mga1.noarch) ERROR: more confl
Re: [Mageia-dev] icewm: [211805] Split themes and i18n as stand-alone packages
22.02.2012 05:27, r...@mageia.org kirjoitti:
> Revision
> 211805
> Author
> yochenhsieh
> Date
> 2012-02-22 04:27:45 +0100 (Wed, 22 Feb 2012)
>
>
> Log Message
>
> Split themes and i18n as stand-alone packages
>
For the record, I still disagree about splitting -i18n package.
It doesn't seem to make any sense, as the package size is only 120kB,
and if saving space is really that important, there already is an
icewm-light subpackage which doesn't contain the translation files,
without any additional need of splitting.
Additionally, splitting i18n files is quite nonstandard handling.
In any case, there are some issues with the commit which are detailed below:
> Modified: cauldron/icewm/current/SPECS/icewm.spec
[...]
> @@ -63,6 +63,9 @@
> Requires:xlockmore
> Requires:xdg-compliance-menu
> Requires:xdg-compliance-autostart
> +Suggests:%{name}-themes
> +Suggests:%{name}-i18n
> +Obsoletes: %{name} < 1.3.7-2
That obsolete doesn't make any sense, icewm-1.3.7-2 replaces
icewm-1.3.7-1 anyway.
[...]
> +%package themes
> +Summary:Extra themes of Icewm
> +Group: Graphical desktop/Icewm
> +Requires: %{name}-light >= %epoch:%{version}
> +Conflicts: %{name} < 1.3.7-2
Missing epoch from Conflicts (1:1.3.7-2).
[...]
> +%package i18n
> +Summary:locale files of Icewm
> +Group: Graphical desktop/Icewm
> +Requires: %{name}-light >= %epoch:%{version}
> +Conflicts: %{name} < 1.3.7-2
Also missing epoch from Conflicts.
Since these cause mga1->mga2 upgrade issues, I've fixed these now myself.
[...]
--
Anssi Hannula
Re: [Mageia-dev] lighttpd and others now require apache
15.03.2012 22:51, Guillaume Rousse kirjoitti: > Le 08/03/2012 16:47, Guillaume Rousse a écrit : >> Le 08/03/2012 16:13, Pascal Terjan a écrit : >>> On Thu, Mar 8, 2012 at 14:57, Romain d'Alverny >>> wrote: On Thu, Mar 8, 2012 at 15:02, Guillaume Rousse wrote: > Le 08/03/2012 14:38, Pascal Terjan a écrit : >> And for /var/www/html >> This should really be a server-neutral thing (with a better name for >> the user, like www-data) but I never took the time to do it :( > > What is needed exactly by various web servers ? I really doubt > anything else > as apache requires apache configuration file. And if it is just a > /var/www/html directory, there is no use to have a dependency for > something > any sysadmin is able to create himself. It helps when it works out of the box. A user may not be aware, at first, that a /var/www/html has to be created + an index.html file put in it, to see its Web server work. It's a good default behaviour confirming the install succeeded and that the server works, it saves a few seconds to everyone trying/doing it first. Now, maybe each web server package should check if this /var/www/html directory exists and create it if needed (or have /var/www/apache, /var/www/lighttpd, etc.)? Or should that be better handled by a separate unique package? >>> >>> I would prefer a package providing a web user and a default webroot. >>> Else we can have such shared user created in each of the packages... >>> It would be annoying to have to chown the writable directories when >>> switching between servers. >> Fine with me. > Well, some days ago I pushed a 'webserver-base' package, with the > following elements: > - /var/www and /var/www/html directories > - 'apache' user > - index.html page > > I've been curious, however, at the exact amount of shared elements our > various webservers packages currently use. And actually, only two > (apache and lighttpd) do share user and document root, the two others > (nginx and cherookee) being totally independant. > > In Fedora, they are all independant. > > So I'd rather revert the change, and make lighttpd autonomous also. > Unless someone can convince me there is an advantage having lighttpd > executing as 'apache' :) The web applications policy has files being owned by 'apache' user, and I don't see how that could work if lighttpd used a different user: https://wiki.mageia.org/en/Web_applications_policy -- Anssi Hannula
Re: [Mageia-dev] Mageia 2 Beta 2 is available
On Thu, 15 Mar 2012, Anne nicolas wrote: > Hi there > > Beta 2 is available now for tests. Here is the announcement: > http://blog.mageia.org/en/2012/03/15/mageia-2-beta-2-near-the-goal/ > > We need your tests and reports more than ever! Hi Anne, I gave feedback with regards to serious issues when trying beta 1 on a Cedarview Atom system, but apart from a couple of isolated replies (thanks to those who did reply) that unfortunately didn't solve the issues I got no further interest. Given that Cedarview Atom will be on most Netbooks this year I would have expected more interest in getting Mageia to work on them. Therefore I say it again, I'm available to do any reasonable tests you want me to do or provide any logs you need to get this solved (see my previous mails for details I already provided so far). Regards, tux99
Re: [Mageia-dev] freeze push mgaonline
15.03.2012 22:07, Dan Fandrich kirjoitti: > On Thu, Mar 15, 2012 at 03:25:40PM +0100, n...@gmx.com wrote: >> * stop using Mandriva URLs and replace them by www.mageia.org (mga#1590) >> * replace Mandriva strings by Mageia in gnome-mandrakeonline.desktop >> * replace MIME Type application/x-mdv-exec by application/x-mga-exec > > Replacing Mandriva -> Mageia in user-visible text makes sense, but what > exactly is the MIME type used for? If the underlying data format hasn't > changed (whatever it is), then this isn't something that should really be > modified, any more than renaming image/vnd.microsoft.icon to something > else. +1, we shouldn't change the MIME type here. -- Anssi Hannula
[Mageia-dev] Freeze push: mariadb (beta)
Please push mariadb: mariadb (and mysql) seem to have an odd method of increasing version number for each of there alpha/beta/rc/final versions. This updates to the 5.5 Beta release (it's not announced yet, but they are waiting for it to hit all the mirrors) Normally, the final is expected to released in about 2 weeks.
Re: [Mageia-dev] freeze push mgaonline
On 15.03.2012 22:54, Kamil Rytarowski wrote: On 15.03.2012 22:44, Dan Fandrich wrote: But it's an academic argument if this type isn't actually used for anything. The only academic thing is overwriting x-mga-* or x-mdv-* by a 3rd party source. And actually we dropped partly support for Mandriva in mgaonline, so this discussion is becoming senseless.
Re: [Mageia-dev] freeze push mgaonline
On 15.03.2012 22:44, Dan Fandrich wrote: On Thu, Mar 15, 2012 at 10:15:34PM +0100, Kamil Rytarowski wrote: If you don't know what it is used for why are you so opposed? We have our own names and suffixes, so I don't why you are against. For exactly the same reason we dropped X-Mandriva-* in favor of X-Mageia in .desktop files. If the formats are identical, then creating a brand-new MIME type is unnecessary complication. Server adminstrators who want to serve up .bundle files for both Mandriva and Mageia then have to deal with sending different two MIME types for files with the same extension. Not true! The only thing to deal with is shipping files with the same extension. The MIME type in /etc/mime.types is guaranteed to be wrong for one distribution or the other. And so on. Not true. But it's an academic argument if this type isn't actually used for anything. The only academic thing is overwriting x-mga-* or x-mdv-* by a 3rd party source. Dan
[Mageia-dev] Packagers team elections
Hi there As said during last council meeting, we need to renew packagers representatives and so organize election for coming year. After nearly 1 year working with 2 representatives, I can say personnally that having 3 people in charge would be great as todo list is quite huge. So here is the planning for this election: - apply on mageia-dev explaining why you would like to be elected, what are your motivations => until our next meeting, 21/03 - launch vote using epoll from 22 to 25/03 Cheers! -- Anne http://www.mageia.org
Re: [Mageia-dev] freeze push mgaonline
On Thu, Mar 15, 2012 at 10:15:34PM +0100, Kamil Rytarowski wrote: > If you don't know what it is used for why are you so opposed? We have > our own names and suffixes, so I don't why you are against. For > exactly the same reason we dropped X-Mandriva-* in favor of X-Mageia > in .desktop files. If the formats are identical, then creating a brand-new MIME type is unnecessary complication. Server adminstrators who want to serve up .bundle files for both Mandriva and Mageia then have to deal with sending different two MIME types for files with the same extension. The MIME type in /etc/mime.types is guaranteed to be wrong for one distribution or the other. And so on. But it's an academic argument if this type isn't actually used for anything. >>> Dan
Re: [Mageia-dev] freeze push mgaonline
On Thu, Mar 15, 2012 at 22:15, Kamil Rytarowski wrote: > I'm in favor of removing all unneeded parts from mgaonline. There were many > parts related to megapacks, server editions, club membership. If the .bundle > is unused then it too can be removed. Yes, but cutting code out of mgaonline must be done carefully (I believe tv did some cleaning already). Are there functional/features tests along with the code? That could be a start to ensure no required feature is broken.
Re: [Mageia-dev] freeze push mgaonline
On 15.03.2012 21:41, Romain d'Alverny wrote: On Thu, Mar 15, 2012 at 21:07, Dan Fandrich wrote: On Thu, Mar 15, 2012 at 03:25:40PM +0100, n...@gmx.com wrote: * stop using Mandriva URLs and replace them by www.mageia.org (mga#1590) * replace Mandriva strings by Mageia in gnome-mandrakeonline.desktop * replace MIME Type application/x-mdv-exec by application/x-mga-exec Replacing Mandriva -> Mageia in user-visible text makes sense, but what exactly is the MIME type used for? For opening files. It's linked through x-mga-exec for *.bundle files. If the underlying data format hasn't changed (whatever it is), then this isn't something that should really be modified, any more than renaming image/vnd.microsoft.icon to something else. If you don't know what it is used for why are you so opposed? We have our own names and suffixes, so I don't why you are against. For exactly the same reason we dropped X-Mandriva-* in favor of X-Mageia in .desktop files. AFAIR, it used to be for long-dead Kiosk project, several years ago (Kiosk was declared a dead project by the end of 2006). .bundle files (downloaded through http) were containing special instructions to trigger specific urpmi behaviour (adding a media, installing RPMs from this media). It was not used since. I'm in favor of removing all unneeded parts from mgaonline. There were many parts related to megapacks, server editions, club membership. If the .bundle is unused then it too can be removed.
[Mageia-dev] new urpmi release ?
I have fixed two bugs in urpmi bash completion: - https://bugs.mageia.org/show_bug.cgi?id=373 - https://bugs.mageia.org/show_bug.cgi?id=4937 However, I'm unaware of any other changes in the perl code itself. Is it sage to proceed with a new release ? -- BOFH excuse #229: wrong polarity of neutron flow
[Mageia-dev] kmail losing e-mails ?
Hi all, On #mageia-dev someone gave this link about e-mails that are eaten by akonadi/kmail https://kdeatopensuse.wordpress.com/2012/03/08/help-on-kde-pim-data-loss-bugs/ Does any one know whether this is something we should worry about? Regards, Marja
Re: [Mageia-dev] lighttpd and others now require apache
On Thu, Mar 15, 2012 at 21:51, Guillaume Rousse wrote: > So I'd rather revert the change, and make lighttpd autonomous also. Unless > someone can convince me there is an advantage having lighttpd executing as > 'apache' :) Ah, interesting point. Should two or more different webservers run at the same time (may happen for server static and dynamic contents, for instance, or for different services), shouldn't they run under distinct users?
[Mageia-dev] Sysadmin please remove from cauldron maniadrive-data
As maniadrive can't be built for now (phplib not avalaible) please remove maniadrive-data from repositories. Thanks
Re: [Mageia-dev] lighttpd and others now require apache
Le 08/03/2012 16:47, Guillaume Rousse a écrit : Le 08/03/2012 16:13, Pascal Terjan a écrit : On Thu, Mar 8, 2012 at 14:57, Romain d'Alverny wrote: On Thu, Mar 8, 2012 at 15:02, Guillaume Rousse wrote: Le 08/03/2012 14:38, Pascal Terjan a écrit : And for /var/www/html This should really be a server-neutral thing (with a better name for the user, like www-data) but I never took the time to do it :( What is needed exactly by various web servers ? I really doubt anything else as apache requires apache configuration file. And if it is just a /var/www/html directory, there is no use to have a dependency for something any sysadmin is able to create himself. It helps when it works out of the box. A user may not be aware, at first, that a /var/www/html has to be created + an index.html file put in it, to see its Web server work. It's a good default behaviour confirming the install succeeded and that the server works, it saves a few seconds to everyone trying/doing it first. Now, maybe each web server package should check if this /var/www/html directory exists and create it if needed (or have /var/www/apache, /var/www/lighttpd, etc.)? Or should that be better handled by a separate unique package? I would prefer a package providing a web user and a default webroot. Else we can have such shared user created in each of the packages... It would be annoying to have to chown the writable directories when switching between servers. Fine with me. Well, some days ago I pushed a 'webserver-base' package, with the following elements: - /var/www and /var/www/html directories - 'apache' user - index.html page I've been curious, however, at the exact amount of shared elements our various webservers packages currently use. And actually, only two (apache and lighttpd) do share user and document root, the two others (nginx and cherookee) being totally independant. In Fedora, they are all independant. So I'd rather revert the change, and make lighttpd autonomous also. Unless someone can convince me there is an advantage having lighttpd executing as 'apache' :) -- BOFH excuse #35: working as designed
Re: [Mageia-dev] freeze push mgaonline
On Thu, Mar 15, 2012 at 21:07, Dan Fandrich wrote: > On Thu, Mar 15, 2012 at 03:25:40PM +0100, n...@gmx.com wrote: >> * stop using Mandriva URLs and replace them by www.mageia.org (mga#1590) >> * replace Mandriva strings by Mageia in gnome-mandrakeonline.desktop >> * replace MIME Type application/x-mdv-exec by application/x-mga-exec > > Replacing Mandriva -> Mageia in user-visible text makes sense, but what > exactly is the MIME type used for? If the underlying data format hasn't > changed (whatever it is), then this isn't something that should really be > modified, any more than renaming image/vnd.microsoft.icon to something > else. AFAIR, it used to be for long-dead Kiosk project, several years ago (Kiosk was declared a dead project by the end of 2006). .bundle files (downloaded through http) were containing special instructions to trigger specific urpmi behaviour (adding a media, installing RPMs from this media). It was not used since.
[Mageia-dev] Please push openvpn
It updates to 2.2.2, and adds S3 to fix bug 4936 Enviado desde mi teléfono Verizon Wireless
Re: [Mageia-dev] freeze push mgaonline
On Thu, Mar 15, 2012 at 03:25:40PM +0100, n...@gmx.com wrote: > * stop using Mandriva URLs and replace them by www.mageia.org (mga#1590) > * replace Mandriva strings by Mageia in gnome-mandrakeonline.desktop > * replace MIME Type application/x-mdv-exec by application/x-mga-exec Replacing Mandriva -> Mageia in user-visible text makes sense, but what exactly is the MIME type used for? If the underlying data format hasn't changed (whatever it is), then this isn't something that should really be modified, any more than renaming image/vnd.microsoft.icon to something else. >>> Dan
[Mageia-dev] Mageia 2 Beta 2 is available
Hi there Beta 2 is available now for tests. Here is the announcement: http://blog.mageia.org/en/2012/03/15/mageia-2-beta-2-near-the-goal/ This is the last beta for Mageia 2 and before RC. We need your tests and reports more than ever! Thanks again all for the hard work Cheers -- Anne http://www.mageia.org
Re: [Mageia-dev] freeze push: setup
On 15.03.2012 20:22, Kamil Rytarowski wrote:
On 15.03.2012 19:53, nicolas vigier wrote:
On Thu, 15 Mar 2012, Guillaume Rousse wrote:
It's just an update of /etc/{services,protocols} files (current ones
are
3-years old).
Submitted.
Please push it again. It's updated. I have excluded firmly run-parts
from setup, it's provided through a stand-alone package.
Please push also run-parts, it's updated to the latest version from
Debian package and installing of localized man pages is fixed. I've
already updated it 2 months ago waiting for review...
Re: [Mageia-dev] [Freeze] please let in xonotic
Op donderdag 15 maart 2012 18:35:04 schreef Juan Luis Baptiste: > On Thu, Mar 15, 2012 at 12:24 PM, Bertaux Xavier wrote: > >> If this is the case, then I say that xonotic should be allowed to be > >> updated. > > > > I'm not about to be okay with that, a version Freeze only accepts > > updates on bug fixes and security warnings, so RC to Release is OK but > > not to revision's change, otherwise that would mean that if fate xonotic > > in version 0.7 just before the Release we should built. > > To me this should be pushed Backport, to limit the update after Release > > Backports are for new versions, not bug fixes. In this case even as > this is a new version, the use of an older version of the game client > with a new game server version could bring issues to users, so that > makes this release more of a "bug fix release", because we are trying > to avoid any possible problem to our users, not because we want to > have the latest version of the game. If we leave the current version > and then a user reports a problem while playing the game, the 0.6 or > 0.7 or whatever version is available at the time would be pushed as an > update, not as a backport. well, the version policy is for updates. my point here is that we should maybe equalize & simplify our policys by having the same kind of "exceptions" in both policies. of course, there may be a good reason to now similar exceptions to both policies, it's just that atm, i don't see any.
Re: [Mageia-dev] [soft-commits] [3526] make clean-rpmsrate 11. 5% faster on average on cached repo directory by
On 15 March 2012 20:20, Pascal Terjan wrote:
>> Modified: mgatools/trunk/clean-rpmsrate
>> ===
>> --- mgatools/trunk/clean-rpmsrate 2012-03-15 19:13:00 UTC (rev 3525)
>> +++ mgatools/trunk/clean-rpmsrate 2012-03-15 19:13:03 UTC (rev 3526)
>> @@ -18,6 +18,9 @@
>>
>> my %rpm;
>> foreach my $dir (@ARGV) {
>> - $rpm{$dir} = [ map { s!$dir/?(.*)\.rpm$!$1!; $_ } glob "$dir/*.rpm" ];
>> + chdir($dir);
>> + $rpm{$dir} = [ map { s!(.*)\.rpm$!$1!; $_ } glob "*.rpm" ];
>
> What about s!\.rpm$!! ?
Indeed we can simplify further :-)
Re: [Mageia-dev] freeze push: setup
On 15.03.2012 19:53, nicolas vigier wrote:
On Thu, 15 Mar 2012, Guillaume Rousse wrote:
It's just an update of /etc/{services,protocols} files (current ones are
3-years old).
Submitted.
Please push it again. It's updated. I have excluded firmly run-parts
from setup, it's provided through a stand-alone package.
Re: [Mageia-dev] [soft-commits] [3526] make clean-rpmsrate 11. 5% faster on average on cached repo directory by
On Thu, Mar 15, 2012 at 19:13, wrote:
> Revision 3526 Author tv Date 2012-03-15 20:13:03 +0100 (Thu, 15 Mar 2012)
>
> Log Message
>
> make clean-rpmsrate 11.5% faster on average on cached repo directory by
> doing less work in the regexp engine and less path walks
>
> elapsed time consistently go down from 0.70 to 0.62 on scores of run
> (mainly a win in time spend in the kernel)
>
> Modified Paths
>
> mgatools/trunk/NEWS
> mgatools/trunk/clean-rpmsrate
>
> Modified: mgatools/trunk/NEWS
> ===
> --- mgatools/trunk/NEWS 2012-03-15 19:13:00 UTC (rev 3525)
> +++ mgatools/trunk/NEWS 2012-03-15 19:13:03 UTC (rev 3526)
> @@ -3,6 +3,7 @@
>o fix matching dkms packages (broken for years...)
>o fix matching locales-xx_XX for localized packages
>o fix matching mga extension (broken since mga fork)
> + o 11.5% faster on average on cached repo directory
>
> 0.1:
> - initial release
>
> Modified: mgatools/trunk/clean-rpmsrate
> ===
> --- mgatools/trunk/clean-rpmsrate 2012-03-15 19:13:00 UTC (rev 3525)
> +++ mgatools/trunk/clean-rpmsrate 2012-03-15 19:13:03 UTC (rev 3526)
> @@ -18,6 +18,9 @@
>
> my %rpm;
> foreach my $dir (@ARGV) {
> -$rpm{$dir} = [ map { s!$dir/?(.*)\.rpm$!$1!; $_ } glob "$dir/*.rpm" ];
> +chdir($dir);
> +$rpm{$dir} = [ map { s!(.*)\.rpm$!$1!; $_ } glob "*.rpm" ];
What about s!\.rpm$!! ?
> }
> +chdir($ENV{PWD}); # in case -o referes to a relative path
> +
> cleanrpmsrate($rpmsrate_raw_file, $output_file, \%rpm);
>
Re: [Mageia-dev] freeze push: setup
On Thu, 15 Mar 2012, Guillaume Rousse wrote:
> It's just an update of /etc/{services,protocols} files (current ones are
> 3-years old).
Submitted.
[Mageia-dev] freeze push: setup
It's just an update of /etc/{services,protocols} files (current ones are
3-years old).
--
BOFH excuse #1:
clock speed
Re: [Mageia-dev] [Freeze] please let in xonotic
On Thu, Mar 15, 2012 at 12:24 PM, Bertaux Xavier wrote: >>> >> If this is the case, then I say that xonotic should be allowed to be updated. > I'm not about to be okay with that, a version Freeze only accepts > updates on bug fixes and security warnings, so RC to Release is OK but > not to revision's change, otherwise that would mean that if fate xonotic > in version 0.7 just before the Release we should built. > To me this should be pushed Backport, to limit the update after Release > Backports are for new versions, not bug fixes. In this case even as this is a new version, the use of an older version of the game client with a new game server version could bring issues to users, so that makes this release more of a "bug fix release", because we are trying to avoid any possible problem to our users, not because we want to have the latest version of the game. If we leave the current version and then a user reports a problem while playing the game, the 0.6 or 0.7 or whatever version is available at the time would be pushed as an update, not as a backport. -- Juancho
Re: [Mageia-dev] [Freeze] please let in xonotic
Le 15/03/2012 17:39, Shlomi Fish a écrit : > Hi all, > > On Thu, 15 Mar 2012 16:50:33 +0200 > Anssi Hannula wrote: > >> 14.03.2012 09:26, Maarten Vanraes kirjoitti: >>> Op woensdag 14 maart 2012 01:16:23 schreef Juan Luis Baptiste: On Sun, Mar 11, 2012 at 7:21 AM, Michael Scherer wrote: > Le samedi 10 mars 2012 à 10:26 +0100, Thierry Vignaud a écrit : >> Hi >> >> please let in xonotic-0.6.0 >> It's just a game that impacts nothing else. > Niet. > > That's bugfix or security fixes. Well I vote to be updated, why ? global game servers are currently running 0.6.0, and by personal experience over several years (omg how much time wasted on this) these FPS games need to have the same client/server version, in some cases different versions won't work at all (ie. Urban Terror 3.7 -> 4.0 -> 4.1, Warsow 0.5 -> 0.8 etc). I just did the test of running a 0.5.0 client on a 0.6.0 server and it works, but a big and annoying yellow announce floats across the screen remaining you that a new version is available. I also talked with one dev over IRC and he told me that there could be issues when running different client/server versions. So just to be on the safe side this new version should be pushed. If not then probably we will need to do it later as an update if any problems arise. I commit my self to test the new version, I know very well how this game works. >>> IINM we have some kind of exception regarding games for their client/server >>> relation regarding updates vs backports? if so, then perhaps we could have >>> the >>> same policy wrt updates to version freeze? >> Yes, we do. Version policy (i.e. no-new-versions-in-updates policy) has >> an exception for "Software that is version-bound to an online service >> (games, virus scanners?) and will only work with the latest version." >> >> This doesn't 100% fit xonotic, though, as online play doesn't *require* >> a specific version. However, as it does impede the online playing >> experience and (AFAIU) online-play is a significant part of xonotic, I'd >> side on the 'update' verdict here. >> >> What do other people think regarding this aspect? >> > If this is the case, then I say that xonotic should be allowed to be updated. I'm not about to be okay with that, a version Freeze only accepts updates on bug fixes and security warnings, so RC to Release is OK but not to revision's change, otherwise that would mean that if fate xonotic in version 0.7 just before the Release we should built. To me this should be pushed Backport, to limit the update after Release Cheers Xavier
Re: [Mageia-dev] [soft-commits] [3483] - stop using Mandriva URLs and replace them by www.mageia.org ( mga#1590)
On 15.03.2012 17:28, Thierry Vignaud wrote: On 15 March 2012 11:44, wrote: Revision 3483 Author kamil Date 2012-03-15 11:44:03 +0100 (Thu, 15 Mar 2012) Log Message - stop using Mandriva URLs and replace them by www.mageia.org (mga#1590) - replace Mandriva strings by Mageia in gnome-mandrakeonline.desktop - replace MIME Type application/x-mdv-exec by application/x-mga-exec - extend $MGA_YEARS in mgaupdate to 2012 - delete MANDRIVA_VERSION variable as not used You should do smaller, morea easily reviewable commits. To be done next time eg: 80%f of the above doesn't apply to Makefile, yet this is what appears in its history. For example: - 1st commit: URL change - 2nd commit: kill unused macro in Makefile - 3rd commit: extend MGA_YEARS - 4th commit: s/mdv/mga/ in .desktop - 5th commit: bump version in NEWS& Makefile Then next step is to step up as co maintainer of drakx* :-) Thank you for your comments!
Re: [Mageia-dev] [Freeze] please let in xonotic
Hi all, On Thu, 15 Mar 2012 16:50:33 +0200 Anssi Hannula wrote: > 14.03.2012 09:26, Maarten Vanraes kirjoitti: > > Op woensdag 14 maart 2012 01:16:23 schreef Juan Luis Baptiste: > >> On Sun, Mar 11, 2012 at 7:21 AM, Michael Scherer wrote: > >>> Le samedi 10 mars 2012 à 10:26 +0100, Thierry Vignaud a écrit : > Hi > > please let in xonotic-0.6.0 > It's just a game that impacts nothing else. > >>> > >>> Niet. > >>> > >>> That's bugfix or security fixes. > >> > >> Well I vote to be updated, why ? global game servers are currently > >> running 0.6.0, and by personal experience over several years (omg how > >> much time wasted on this) these FPS games need to have the same > >> client/server version, in some cases different versions won't work at > >> all (ie. Urban Terror 3.7 -> 4.0 -> 4.1, Warsow 0.5 -> 0.8 etc). > >> > >> I just did the test of running a 0.5.0 client on a 0.6.0 server and it > >> works, but a big and annoying yellow announce floats across the screen > >> remaining you that a new version is available. I also talked with one > >> dev over IRC and he told me that there could be issues when running > >> different client/server versions. > >> > >> So just to be on the safe side this new version should be pushed. If > >> not then probably we will need to do it later as an update if any > >> problems arise. I commit my self to test the new version, I know very > >> well how this game works. > > > > IINM we have some kind of exception regarding games for their client/server > > relation regarding updates vs backports? if so, then perhaps we could have > > the > > same policy wrt updates to version freeze? > > Yes, we do. Version policy (i.e. no-new-versions-in-updates policy) has > an exception for "Software that is version-bound to an online service > (games, virus scanners?) and will only work with the latest version." > > This doesn't 100% fit xonotic, though, as online play doesn't *require* > a specific version. However, as it does impede the online playing > experience and (AFAIU) online-play is a significant part of xonotic, I'd > side on the 'update' verdict here. > > What do other people think regarding this aspect? > If this is the case, then I say that xonotic should be allowed to be updated. Regards, Shlomi Fish -- - Shlomi Fish http://www.shlomifish.org/ First stop for Perl beginners - http://perl-begin.org/ Live as if you were to die tomorrow. Learn as if you were to live forever. — http://en.wikiquote.org/wiki/Mohandas_Gandhi (Disputed) Please reply to list if it's a mailing list post - http://shlom.in/reply .
Re: [Mageia-dev] [soft-commits] [3483] - stop using Mandriva URLs and replace them by www.mageia.org ( mga#1590)
On 15 March 2012 11:44, wrote: > Revision 3483 Author kamil Date 2012-03-15 11:44:03 +0100 (Thu, 15 Mar 2012) > > Log Message > > - stop using Mandriva URLs and replace them by www.mageia.org (mga#1590) > - replace Mandriva strings by Mageia in gnome-mandrakeonline.desktop > - replace MIME Type application/x-mdv-exec by application/x-mga-exec > - extend $MGA_YEARS in mgaupdate to 2012 > - delete MANDRIVA_VERSION variable as not used You should do smaller, morea easily reviewable commits. To be done next time eg: 80%f of the above doesn't apply to Makefile, yet this is what appears in its history. For example: - 1st commit: URL change - 2nd commit: kill unused macro in Makefile - 3rd commit: extend MGA_YEARS - 4th commit: s/mdv/mga/ in .desktop - 5th commit: bump version in NEWS & Makefile Then next step is to step up as co maintainer of drakx* :-)
Re: [Mageia-dev] freeze push mgaonline
On 15 March 2012 15:25, wrote: > Please push mgaonline. > > > - new tarball 2.77.32 > * stop using Mandriva URLs and replace them by www.mageia.org (mga#1590) humm, was in non used helpers but eventually was to be done someday > * replace Mandriva strings by Mageia in gnome-mandrakeonline.desktop > * replace MIME Type application/x-mdv-exec by application/x-mga-exec > * extend $MGA_YEARS in mgaupdate to 2012 > * delete MANDRIVA_VERSION variable as not used > - replace obsolete drakx-newt with drakxtools-curses > - stop using MANDRIVA_VERSION in %install > - rename mandriva-mgaonline.desktop with mageia-mgaonline.desktop > - clean Categories in the .desktop file (remove X-Mandriva-* entry) > - remove %update_desktop_database and %clean_desktop_database (not used > anymore) > - remove %update_mime_database and %clean_mime_database (not used anymore) > - clean .spec you should not list all cleanups as reasons to push :-)
Re: [Mageia-dev] freeze push: cpuid
Le 15/03/2012 15:45, Anssi Hannula a écrit : 14.03.2012 15:35, Damien Lallement kirjoitti: Hi, Can you please submit "cpuid" (already commited): http://fossies.org/linux/misc/cpuid-20120225.src.tar.gz:a/cpuid-20120225/ChangeLog Since: Sat Mar 5 2011 Todd Allen 43 * Made new release. There was a lot of commits, bug fix and improvement to detect new Intel/AMD cpus. New release is from: Sat Feb 25 2012 Todd Allen 2 * Made new release. As cpuid is only updating the "final" snapshot once a year, I think it will be good to have it uptodate for 2 (KVM, CPUs, chips updates). Agreed. It is not used by any other package, it is "unimportant", it has non-frequent releases, and it can quickly become out-of-date as new hardware is released. Submitted. Thank you Anssi! -- Damien Lallement Treasurer of Mageia.Org twitter: damsweb - IRC: damsweb/coincoin
Re: [Mageia-dev] Freeze push: firefox, xulrunner
15.03.2012 16:39, Anssi Hannula kirjoitti: > 14.03.2012 04:02, Funda Wang kirjoitti: >> Hello, >> >> Could somebody push firefox 10.0.3esr and xulrunner 10.0.3esr into >> cauldron? Thanks. >> > > Submitted. > firefox failed. xulrunner is still building. -- Anssi Hannula
Re: [Mageia-dev] [Freeze] please let in xonotic
14.03.2012 09:26, Maarten Vanraes kirjoitti: > Op woensdag 14 maart 2012 01:16:23 schreef Juan Luis Baptiste: >> On Sun, Mar 11, 2012 at 7:21 AM, Michael Scherer wrote: >>> Le samedi 10 mars 2012 à 10:26 +0100, Thierry Vignaud a écrit : Hi please let in xonotic-0.6.0 It's just a game that impacts nothing else. >>> >>> Niet. >>> >>> That's bugfix or security fixes. >> >> Well I vote to be updated, why ? global game servers are currently >> running 0.6.0, and by personal experience over several years (omg how >> much time wasted on this) these FPS games need to have the same >> client/server version, in some cases different versions won't work at >> all (ie. Urban Terror 3.7 -> 4.0 -> 4.1, Warsow 0.5 -> 0.8 etc). >> >> I just did the test of running a 0.5.0 client on a 0.6.0 server and it >> works, but a big and annoying yellow announce floats across the screen >> remaining you that a new version is available. I also talked with one >> dev over IRC and he told me that there could be issues when running >> different client/server versions. >> >> So just to be on the safe side this new version should be pushed. If >> not then probably we will need to do it later as an update if any >> problems arise. I commit my self to test the new version, I know very >> well how this game works. > > IINM we have some kind of exception regarding games for their client/server > relation regarding updates vs backports? if so, then perhaps we could have > the > same policy wrt updates to version freeze? Yes, we do. Version policy (i.e. no-new-versions-in-updates policy) has an exception for "Software that is version-bound to an online service (games, virus scanners?) and will only work with the latest version." This doesn't 100% fit xonotic, though, as online play doesn't *require* a specific version. However, as it does impede the online playing experience and (AFAIU) online-play is a significant part of xonotic, I'd side on the 'update' verdict here. What do other people think regarding this aspect? -- Anssi Hannula
Re: [Mageia-dev] freeze push: cpuid
14.03.2012 15:35, Damien Lallement kirjoitti: > Hi, > > Can you please submit "cpuid" (already commited): > http://fossies.org/linux/misc/cpuid-20120225.src.tar.gz:a/cpuid-20120225/ChangeLog > > > Since: > Sat Mar 5 2011 Todd Allen >43 * Made new release. > There was a lot of commits, bug fix and improvement to detect new > Intel/AMD cpus. > > New release is from: > Sat Feb 25 2012 Todd Allen > 2 * Made new release. > > As cpuid is only updating the "final" snapshot once a year, I think it > will be good to have it uptodate for 2 (KVM, CPUs, chips updates). Agreed. It is not used by any other package, it is "unimportant", it has non-frequent releases, and it can quickly become out-of-date as new hardware is released. Submitted. -- Anssi Hannula
Re: [Mageia-dev] Freeze push: firefox, xulrunner
14.03.2012 04:02, Funda Wang kirjoitti: > Hello, > > Could somebody push firefox 10.0.3esr and xulrunner 10.0.3esr into > cauldron? Thanks. > Submitted. -- Anssi Hannula
[Mageia-dev] freeze push mgaonline
Hi! Please push mgaonline. - new tarball 2.77.32 * stop using Mandriva URLs and replace them by www.mageia.org (mga#1590) * replace Mandriva strings by Mageia in gnome-mandrakeonline.desktop * replace MIME Type application/x-mdv-exec by application/x-mga-exec * extend $MGA_YEARS in mgaupdate to 2012 * delete MANDRIVA_VERSION variable as not used - replace obsolete drakx-newt with drakxtools-curses - stop using MANDRIVA_VERSION in %install - rename mandriva-mgaonline.desktop with mageia-mgaonline.desktop - clean Categories in the .desktop file (remove X-Mandriva-* entry) - remove %update_desktop_database and %clean_desktop_database (not used anymore) - remove %update_mime_database and %clean_mime_database (not used anymore) - clean .spec
Re: [Mageia-dev] [soft-commits] [3484] SILENT : bump VERSION (in Makefile)
'Twas brillig, and Remco Rijnders at 15/03/12 11:55 did gyre and gimble: > On Thu, Mar 15, 2012 at 11:04:07AM +, Pascal wrote in > : >>> >>> SILENT : bump VERSION (in Makefile) >> >> SILENT only applies to rpms which get their changelog generated from >> svn log > > What decides if it does or doesn't? Well, the svn changelog in soft/ isn't used for anything other than looking at by humans. The svn changelog in packages is used by tools that generate the srpm. It's not really a "decision" so much as "how it works". 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] [soft-commits] [3484] SILENT : bump VERSION (in Makefile)
On Thu, Mar 15, 2012 at 11:04:07AM +, Pascal wrote in : SILENT : bump VERSION (in Makefile) SILENT only applies to rpms which get their changelog generated from svn log What decides if it does or doesn't? Thanks, Remmy signature.asc Description: Digital signature
Re: [Mageia-dev] [soft-commits] [3484] SILENT : bump VERSION (in Makefile)
On Thu, Mar 15, 2012 at 10:50, wrote: > Revision 3484 Author kamil Date 2012-03-15 11:50:20 +0100 (Thu, 15 Mar 2012) > > Log Message > > SILENT : bump VERSION (in Makefile) SILENT only applies to rpms which get their changelog generated from svn log
Re: [Mageia-dev] NEEDHELP Bugzilla keyword
On 14/03/12 16:09, Olav Vitters wrote: On Wed, Mar 14, 2012 at 03:24:09PM +0100, Marja van Waes wrote: Do you mind testing with NEEDHELP on the whiteboard first? We can make a shared search for those bugs. Will do. Thanks, Olav :) For who wants to help, the search is here: https://bugs.mageia.org/buglist.cgi?status_whiteboard_type=allwordssubstr&query_format=advanced&order=Importance&status_whiteboard=NEEDHELP&bug_status=NEW&bug_status=UNCONFIRMED&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=VERIFIED The name of the shared search is NEEDHELP: Bugzilla - log in - Preferences - Saved Searches - scroll down to "NEEDHELP" - click on "run" (or tick the box in the last column, to get a permanent link to the search in Bugzilla's footer)
