[Mageia-dev] Freeze push: kdenlive
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi! This is a bugfix release with a few minor features. - From KDE Community's post (https://plus.google.com/u/0/105126786256705328374/posts/UPmCW4Xiq7o): ... Kdenlive adds a Reverse clip option to Clip Jobs that creates a backwards clip.The list of audio / video bitrates can now be customized in custom rendering profiles. Version 0.9.6 also fixes several bugs and crashes, including a very annoying bug that caused project files to seem corrupted. We really need this one as for some people 0.9.4 is quite unusable. - -- Sander -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.13 (GNU/Linux) iQEcBAEBAgAGBQJRYW9GAAoJECMkkFJIyHr8saAH/00BiQSWz+rEidNrOWugEt7i fRsCDN7yM4evbBG8yPy7YSPB/D+Vd3zfCLC+4qpeRSacAa0FJRL9E8/FlOGl63uU uWefNHWhzPbMjGNIE7D+NgftbykAJVibXMGSlYucKUJH1zsP1+9qb2eVXL7eKrGM YYIUjYoepR+hpEwSZQTb+8XXX5GL0Z7lnTsMxhgrxQOAj4k49+lfuC2BmGcJTTL5 sf04gPFog3n2ZSuwRNEhmVQI9f+Lct2M+yTuVaB6pZFgE985/RqiLob7ja3M0OZw xmmxjnsDfLKvJTVGQCW+sX6paf0+66T3UP/oWqrQbU2PHxZQI2EXHwMZzdnTFwY= =4Oso -END PGP SIGNATURE-
Re: [Mageia-dev] Update to boost-1.53 ?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 02.04.2013 03:31, Barry Jackson kirjutas: I will try to test rebuild all the packages using boost in i586 in iurt in the next few days - just wish urpmi-proxy would work with iurt (if anyone knows how to enable extra media in iurt let me know) My iurt command with local repo that is soft-linked into /media: LC_ALL=C linux32 iurt --delete-on-success --chrooted-urpmi http://my.domain.com/mga/distrib --media core/release local/release -r cauldron i586 - -- Sander -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJRWozaAAoJECMkkFJIyHr8K3YH/RChnina1eDzocf1rYBmcFJK RqmljHyrSy40nzHZ0YUjFP31aAygEfvfnxvYisxc45010NkUiAU4W4QBJn14reHD SiVUUj1QXGCBaL0hM/x4bK1c3HqKAwhlvOaaG1XlW44WNgkAlE7g2mrugWMVy953 v/HgcYbDirqskmYFUpA0a5fz9PHr6AqLvBdqWAjyomo74vytmEZnOpXZ6BcL8l7q 2Vg0d6zSajAD/EsR4VgBz3idBe6ymYOB4YInct0fdfr/bL0OF/hnLS1PVG5t6FVR NjruaDQeTC558QtQL/4K4xFyHjTjEadUinG47lkQHcezJ8ArOTw67sZvzplJTfw= =0iyj -END PGP SIGNATURE-
[Mageia-dev] Freeze push: hexchat
This version fixes quite a few bugs + adds some new features. Some important ones to bring out: - fix tray icon not reappearing if the tray crashes - add Plugin-Tray option to disable blinking With those improvements HexChat can be used longer than 2-3 days w/o restarting X (blinking icons in KDE's tray cause huge memory leaks). This package is new to Mageia (read: introduced in Mageia 3) and nothing depends on it, so should be safe to push. -- Sander
Re: [Mageia-dev] Update to boost-1.53 ?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 31.03.2013 18:37, David Walser kirjutas: Barry Jackson wrote: As mentioned in last week's packager's meeting, there is a problem with our gnuradio package, because upstream have blacklisted boost-1.52. https://bugs.mageia.org/show_bug.cgi?id=8789 I have spent considerable time test rebuilding all packages from current svn that BuildRequire boost, against boost-1.53 to see if an update of boost is viable. (x86_64 only so far) Fixes have been applied to some packages and now there are just two remaining that fail to build:- Now that it's down to these two, I think this should be done. libyui is only here for the new MCC which won't be ready at least until mga4, and it seems this gnuradio is important to some people, while vegastrike is just a game I think. And how sure are you that all those recompiled packages are working as well as they do now? :) Compiling is one thing, running them is something else. - -- Sander -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.13 (GNU/Linux) iQEcBAEBAgAGBQJRWFlVAAoJECMkkFJIyHr8RGsIALa94pTk92GhggGZdFt54o3W 2hoRaVDjEvoc/qPw/IJYggu70HJgFEW34ztEck5ChXfLN6EkZ3ZztgF7iMvS8vYq ipSOQUCxMrzD5CTCSU2rh1s3kI2MOMyY5qY9epEa5/3KM8LgWm3wTSw+JjYDggiy Pr3Wa2yPPbURsMWi29T88R1w9PNVlUO8Z1qUkYfMr0aUheqxg6DnOcZoroa166z1 tdhdEDATMj60WmqdQ2NzeTXbwDFyQssA4IfCe58z8VIDJrQ5yp3j838ZOxe7U/LL 2atiOseSLc/NODwIZiRSpJcxxVahIzzjVWDUGfzW/NjImXbHB7jxdmvx/yUZRmI= =XQ3a -END PGP SIGNATURE-
Re: [Mageia-dev] Fw: Wifi
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 23.03.2013 04:09, Trish Fraser kirjutas: Hi all, This seems to be an ongoing issue - can someone please help me with an answer for this user? And the magical bug number is? :) - -- Sander -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.13 (GNU/Linux) iQEcBAEBAgAGBQJRTd2/AAoJECMkkFJIyHr8QVsH/Ar+k6O0pMDdHdVHL0g389YU V3BSAuWXEX5CSCBlLOQUAdUWLUbbWpD+9w7SyHrAgOMIVcwNa+fYfb+SEEloztZT 3XoaSattc+2n7q/wTXPYAdbFlQfsqpkM3rEZQ3/7+UDA/xBoYjzJyKpknAejRHyk gsJlhaxG1QFDCci1u9hPW4d6AGrZ2mOyZ8Q/M2ldfd9fwMoc82lwszLO3sPOBOdo yTbPlQRrHMqZgz9+o+dO7OIUH5oFXdx80m/8WATZfuRtsbvs8/CoBU0T91zohpyF lIofCzMP9xGJJ5LLJWGyasQOgW+dAbjRs9jBElVYoSZgJ8EgrREvtB3H8VRgM0g= =kYCr -END PGP SIGNATURE-
[Mageia-dev] Bug #7633
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi! https://bugs.mageia.org/show_bug.cgi?id=7633 Can we do something about this bug? 80+ people in CC getting spammed every second day. If we can't fix it then let's drop it. - -- Sander -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJRLyLrAAoJECMkkFJIyHr8C/YH/02QozXAYzIR1MZGA3WGAW+y FMTvP9+12ubVgDDaJOr2yVmm8xCB7rgaM/Tu24vfhypr6+KOEhMjyTJr/FwIuYkC lykEvw+2Ta2EwJez6J6YTEml5/hUwvhXMRpYq7niVjBz2KhTiJJFvPa2ONNRaYDa JdHHotPd5dtDBiI3V2ICFMQpMv1c0D/MZziYgZAMnCWvySgh0cMmkK/A/vF6EDDq TPaZtQKjEVFsyBmTlTT9OcpEOymDDX0n/X+gD/Z5BO00Ref6gdfaOTkgkcoy28Z9 eK9kmLHa+5H6E9xdu1uIv4SHYj2h7OIqeg3BANaJY7TtoO29Af2Xk5f5TflZpAA= =bYyY -END PGP SIGNATURE-
Re: [Mageia-dev] dhclient lease files location
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 23.02.2013 15:42, Thomas Backlund kirjutas: Guillaume Rousse skrev 23.2.2013 14:57: Le 14/02/2013 11:07, Olav Vitters a écrit : On Wed, Feb 13, 2013 at 09:56:50AM +0100, Olav Vitters wrote: NetworkManager uses a stupid version numbering. It should have stayed with 0.9.6.x. My bot accidentally upgraded it to 0.9.7.x, which is wrong. Bot accidentally upgraded some more NetworkManager stuff. Still planning to revert that all. Hi Olav. Any ETA on this issue ? BTW, you could also accidentaly slip to 0.9.8 now it has been released, as it would also close my own original issue :) Well, his bot already updated svn to 0.9.8 :) And reading the changelog for NetworkManager I think we should push it... Yes, I agree, someone with permissions please push. We have enough time to revert but I hope we don't have to. - -- Sander -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.13 (GNU/Linux) iQEcBAEBAgAGBQJRKOSlAAoJECMkkFJIyHr8UL0H/jGBWjILbYVspaOfB4Q6uD+o xCjNKVqONNsfwi4TJy+UFqn6/EXHs0s3RQSCRx7CxxhO8nvfqu6F//NqqpCN+HAV 6whXo+EYkl2gqZ/h5MdO9Iw/O2sSw7B9RcZ5bRNK1H57ZQkEMoAVsF8ad4r9wHMG apY6Wu2t5pfH/W/EhyBTyj4a/ZGh9xtd2FOyVDKb3xjzBrntuh6VlcTtgyb9x7AA igy3eJp7aYLoWEMO0B5Xdo9UQjHgTMi8vy87yDOgtOWCLF2bi3lMSkxP5NiEiQ10 jwVlrnerx/xtetI5CsiPiPWbNMNh8923H4kfhqRuzraUkYYxJ1ViMYi1HtTuOT0= =94pe -END PGP SIGNATURE-
Re: [Mageia-dev] Why ntpdate still there?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 22.02.2013 01:04, Colin Guthrie kirjutas: So perhaps we should restore the previous setup? Yes, i think so too. At least now i know why my ntp service was stopped for no reason :P - -- Sander -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJRJyaoAAoJECMkkFJIyHr8ZWEH/RD3MSXunXAVzvp/aBJ3dagV 5ubvJj83Vjy6HVFpHgPCxqJ+sQq1CcxtLHI3cSwBrCeZ4LYPCNUM1TlW/cSery5d 3hwfnmol4amazzjTwZsq8NB03kNWdCze2ogMkYRd+eFmjwWHKl/Mc8GNDyGd5yLo D+kG+nHfRUpY2qJZ0gOCtwKjyI2oWFW8dov+9nwyOrOCcu2wbioXnDVBnaHwyPd8 smFQNKYjcFPsSemoBsmWFJmkztPjgyxih7R/SZIAUAME2WB7hztgQxdz7iHZbmp0 7+OmGY1rsu3WlSbkxYH2lk0L43T5VKnb2I7gxHGFDv5W7yLnhlow1a2u6/szQ18= =EoXS -END PGP SIGNATURE-
[Mageia-dev] NetworkManager 0.9.8
Hi! NetworkManager 0.9.8 has been released: https://mail.gnome.org/archives/networkmanager-list/2013-February/msg00156.html - and it contains at least one very-very-very important change (don't keep asking for a password). So long this is a real pain in the butt if connection is configured as system connection and it then happens to drop. User is asked for root password and when s/he doesn't have it... well, reboot is the only option. So what are the chances to have this version in Mageia 3. Or can we somehow cherry-pick this change? -- Sander
Re: [Mageia-dev] oxygen-gtk2-1.3.2-1
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 13.02.2013 15:14, FundaWang kirjutas: Date: Wed, 13 Feb 2013 14:01:44 +0100 From: h...@oxygen-icons.org To: mageia-dev@mageia.org Subject: [Mageia-dev] oxygen-gtk2-1.3.2-1 Hello folks, could someone build and upload oxygen-gtk2-1.3.2.1 from the tarball at: http://download.kde.org/stable/oxygen-gtk2/1.3.2.1/src/oxygen-gtk2-1.3.2.1.tar.bz2 Previous release was crashing several apps at startup due to a regression introduced while attempting to fix other issues when running oxygen-gtk from Gnome-Shell Sure, updated. Now who to push it? Ping.. - -- Sander -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJRHK/lAAoJECMkkFJIyHr8KpkH/28RCjNF+4X7maWjFN9iHNoz 1vSDHpOG2indz9Pd+3PXY9rmOlfRV3hkV7lYiiga6scOWB6qeOjTI3zOMovuQ4Xp ItGxgWO89T1DvNFW3eMCGymbAKDi188fXkKM8Hv09UY/Yv+KkzUVlulwj2qlV63d Snlb/oQlloVypGmzaa2AQ9ArYoQTBRcyEPovcdzRPA32fav2QPivKkCKplVZSim/ 9LkIjKJn39HIxO4RqO6k8Zu0/1qNYE7SMSVQ3gtXPofOHyQGKkth16baylesjn8f GsB24GgmSDDeDj9npVoX7lys5uosviNkbe/tWOfhM2YI2DO+kLwfLXPOr7ph/j4= =/AwY -END PGP SIGNATURE-
Re: [Mageia-dev] freeze push: sympa
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 06.02.2013 10:52, Guillaume Rousse kirjutas: Comrade submission master, there is another release for sympa, could you please push it ? Sure, comrade packager. You may be funny to yourself, but another release doesn't quite explain why we should have it?! I think you still miss the point why permission is asked... And you shouldn't push your own packages.. - -- Sander -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJREjABAAoJECMkkFJIyHr8gu0H/2Z1y1dlYDKsi+0jDYsYHNX2 bw3SrZ6fLogZ9tTutcPVhaGl8qOkSle3jx0MVTjD3jfe7ew1JldSqbEVxCgzGMKP j8DhsBbF9DDVNCrMS5pAHwZ1L0uxV2ani9MtQFZdJzOLuBifZCMPzSADngG/39nS D8fcqkrfosl+6mQXvNgnvkFllCmLtYVrsOlAmBhf88fjguJSqZiLl4BxTV00mdEd vMCBNupRxtf4vj/3FMB3ciAWKRQ6zZL76C89Ajnd5aesqixciyFp6wtABCXyiLMg FZ0x91FtHcS6lQdHdvb41VEQfatLT1+nV6n9OidTqFnj9vw8IysgJrhqnoipu2A= =MT0P -END PGP SIGNATURE-
Re: [Mageia-dev] Freeze push: eog 3.7.4
14.01.2013 20:51, Olav Vitters kirjutas: vaci0 pushed eog 3.7.2. At least we should go for latest unstable… not sure if it works with our gtk+ version though. ping.. -- Sander
Re: [Mageia-dev] Freeze push gsoap (needed to build virtualbox vboxwebsrv)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 14.01.2013 22:50, Angelo Naselli kirjutas: Il 12/01/2013 20:26, Angelo Naselli ha scritto: Please push gsoap. I tried to have it before freeze time, but a nasty error blocked me, now it's fixed thanks to barjac. tmb can you please go on with virtualbox to fix this bug also: https://bugs.mageia.org/show_bug.cgi?id=7021? Thanks, Angelo Ping I don't see new version here :) You did some changes but didn't change version. Well, you also didn't bump release :P - -- Sander -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJREM9MAAoJECMkkFJIyHr851kH/A5j9UfRK2BEI3cjPQqjliy6 QB8AuiKcIDx4LKa+SVevmF7bAGLeL9+LxFNdguTJyMmWU6yJKCvVsHPnsSoRbZs5 JAoY4VG/ZrkM9eOJ8njbBNTmQbjW95P524qa5HQM0PB/bsYiUuGwMqZrN3yulfTL 7c1eMKi/f2PKX5YSfUQ4ucqiYuC3IvU7gLEZd++8EaaxZwQ+2LMcSBbueiaaT/dX wVil7CyCW8FA+a96eOznlwlwAyyArD6bWByN4pYL6/uipbDssaCwqCwgFqMi6anX ESdpa2/+QpYXj4YG3D6PxpB1rk0CqaFVbHDHauDpOoRD1crekSYDqi8V66Cs2FI= =lOF5 -END PGP SIGNATURE-
Re: [Mageia-dev] Freeze push: transfugdrake
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 15.01.2013 14:58, D.Morgan kirjutas: On Tue, Jan 15, 2013 at 9:17 AM, D.Morgan dmorga...@gmail.com wrote: Hi, please push transfugdrake, this is the version in svn and it builds. regards, D. ping ping #2 - -- Sander -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJRENDEAAoJECMkkFJIyHr8R40IALBYn6HbNSqOHlNpfLnjSeYb 8dS+hxGdSVtp7WfAbnJJ8JL6h7Apj5OOM+B8pTGOdVhNiigC/jpoe/hR2+U5eCzs r5JHnbYhks0orS8I+1cNS8Y3i9Yh6l0vlxN1Htl/Rt379trbUhkGY4LjDvkwiZRG MYv4i0Hn6Pmkg4smX+UafVXuskuf8Os/KkCSrrUwYunPrGzRzVyVZNbsE6FNfQzi IMkj6/n0Rn6JlmkhHgnTRZgPg6D+4De6+o/8isd+L8wVVLbj/lNdkzMvrb7Ry8we ofZaAypVwBcTG8xE0AVbCVSWc0387j9UXHGmY8keugrQDNJwuqH7dOtIQQPwJ9c= =aPhK -END PGP SIGNATURE-
Re: [Mageia-dev] Freeze push: libchewing scim-chewing
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 28.01.2013 04:15, You-Cheng Hsieh kirjutas: 2013/1/24 You-Cheng Hsieh yochenhs...@gmail.com: Hello, libchewing scim-chewing dev (quietly) released new versions near the end of last year, and I missed both of them before version freeze.:( For libchewing, 0.3.4 includes more fixes than new features and I highly suggest we should push it for Mageia 3 release: https://github.com/chewing/libchewing/blob/master/NEWS For scim-chewing 0.3.5, only minor changes have been made and scim is still not usable in Cauldron now(?). If you worry about stability issue, this one can be skipped. But I still think it should be OK, though. https://github.com/chewing/scim-chewing/blob/master/NEWS Both of them can be built successfully in my Cauldron VM and I've commit them to svn. Please help submit them. Thanks, You-Cheng Hsieh ping? ping #2 - -- Sander -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJRENOyAAoJECMkkFJIyHr8fVoIAKIp8qqENcbe5PVAuwNUnkVa eDsCviEAuPdkOn1FYPzpou9l4HkHEqiVMOPyD8cOiIqMFaUP4ASicqhOs3yyCGXU sTNKHMQJ0Hku6z+pV2/t2uW8tgWX3FPoN3zYI0Uf1os9sn66sVklGw0mKqExgD4l lF2NqFBt4q9MikYqX+NrHTkeQa8UO9EYviLLWcWxhPSU/+j8HSXSA1qvIf7OprJe Xtp/bsjxHYPC03scbKB5LcGnAvXGxLg6i7a7+Qwp7zquAFrSSOH0pi2hvdARJbjJ 6TowPJnCMxUUPyow73/Dz2Cs12S5cDUcb2X6RdK5URshlFCMYkatjauG8h0FvO4= =SovE -END PGP SIGNATURE-
Re: [Mageia-dev] freeze push phpMyAdmin 3.5.6
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 31.01.2013 22:49, zezinho kirjutas: It is a pure bugfix release: Welcome to phpMyAdmin 3.5.6, a bugfix release. 3.5.6.0 (2013-01-28) - bug #3593604 [status] Erroneous advisor rule - bug #3596070 [status] localStorage broken in server status monitor - bug #3598736 [routines] Editing a procedure with special characters - bug #3600322 [core] Visualize GIS data throws Fatal Error - bug #3599362 [core] Double-escaped error message - bug #3776 [cookies] Login without auth on second server Pushed by GR. - -- Sander -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJRENb6AAoJECMkkFJIyHr83usIAKI/YoxkWik50MoBS3sT0odZ rAfhgTjsl0h0Q4rslMlMzXWatJkW1ggRYiIofm5180cezytbHpM/KO8UA/lupff6 27M5p4j5tQV9zafEhMC+wVBGFJ00SafLMu9R80mS1VTI51vsnXKot12lvbFPYRIJ Ty3sD9yTO+gLZYF3ULJ6IO1KHx0cE+3HJaRar+Zijyxwit96oxJCGpRZoqQEmyfI 76fyJX7PbfYXDExSuWR4oAeC0r3H4ygvnXS6F0Y+n8CKmm7zqxsisv4v0xqPPXvW +Dz1Wkx1wgmQZdp8stgvfqX+vRkNSXxAdN6hlMmQ7Nq6k2OZVZjywkPJFk01Abw= =asUV -END PGP SIGNATURE-
Re: [Mageia-dev] freeze push request uhd
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 01.02.2013 01:38, Barry Jackson kirjutas: Please push uhd new minor version. It only affects gnuradio which I will rebuild against it later. Thanks. Pushed by GR. - -- Sander -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJRENc6AAoJECMkkFJIyHr8LVQH/jbE9N3EnkpibDbCfcbsBz0h /qD9XaptQBT6zND0EIWoOX5AiR/OOVUXLR9lqTeVqvu9JgAX4z7oPZBpNZnAprzZ oqdVe/Lv3OQK4igKmPRkNPcXBLPRQ0/f/PA+UDM1ZzVTYn8rVFOfogGVtXNlA1Jp yL4uMAvqfDSm5bTRsaAKxdUy3Dr7hQQIbNEcaiUl7zqee8enWXfP6FfH2yMjCVYx kKCoKm0CoYbS/8L87Rgae0DzCkmJU3PWV0x3pPLU22XdUn47zwBW/VsCcZ5STfPK ir/E/5rVVeuUlKqdll4G2zcZ8M9ubRNjG2F5AaANzI+ugAj+fo8tvdkYQNYIVNU= =oMjx -END PGP SIGNATURE-
Re: [Mageia-dev] Freeze push: calibre
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 01.02.2013 16:43, Damien Lallement kirjutas: Please push calibre 0.9.17: - Fix regression that caused some svg images to be rendered as black rectangles. - News download: Do not convert all downloaded images to JPG format. This fixes the problem of PNG images with transparent backgrounds being rendered with black backgrounds - News download: Add support for logging in to sites that require javascript for their logins. - Fix out-of-bounds data causing errors in the Tag Browser - Driver for LG E400 and SayCoolA710 - Replace all non-ascii characters in CSS class names, as they cause problems with some broken EPUB renderers. - Do not choke when reading metadata from MOBI files with incorrectly encoded metadata fields - MTP driver: detect devices that have MTP interfaces even if their USB ids are not known - Allow choosing which page of a PDF to use as the cover. - Add PocketBook Pro 912 driver - Update amazon/waterstones/libri plugins to account for website changes - Fix 'X' being droppen from isbns on export - Fix using incorrect escaping for non-ascii attachment filenames - Update metadata when serving azw3 files - Fix wrong icons - Fix bug to prevent deleting files by device after upload - Add and improve news sources Thanks! Pushed by GR. - -- Sander -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJRENePAAoJECMkkFJIyHr8Ec4H/iZw+DUNKoZjesF+3xVcIORX M2dLKscVaChuDlLEvflhcxwsNj7SlFybxfq0TzYesDo038f8c8O95Dqra5uRDmGG J50urksKsjFMepQLK9XYIXkv526Fmv5IrOPxm/pUtetwDUTsotTOsoyvKepzF+pQ iZNAZMVBFkcw6NphNWzf9Kqx5MqwxCfW4CjursWAHdISDI19qqr6NkZ9FTxUnsCs cdNkDAv4qwlb61FqmmqoDngBM+ss4QbLKKQYlvtV8Jbm7Foo45HPwUgXyuQdnNqy il1cVUo/2CyGM0LAfFldl3C/kd2cfs4S80OSmObX+a6u2l+FxTJoKpSrvfx3pec= =na+m -END PGP SIGNATURE-
Re: [Mageia-dev] Freeze push: mercurial-server 1.3
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 03.02.2013 12:04, Kamil Rytarowski kirjutas: Hello! Please push mercurial-server 1.3, it's mostly a maintenance release - no new features, mostly clean-ups [1]. Regards, [1] http://hg.opensource.lshift.net/mercurial-server/file/default/NEWS Pushed by GR. - -- Sander -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJRENe4AAoJECMkkFJIyHr8etEIAJS/CKjsWu34Y4n3tCloT3ug Ojx69YvudjUvWtX/pI9UQb7K2oFRnOKW+1NiLaambUu7upvxKgodr+P4o9r0dHur y8/h0tieZgzYaS1w1yrFfgkR/GTNa0LI4AKvwA/9Bkqi2YHaU0Ms58aMzJM8cddP tr+L0pnZTgnVrfH5Pa5NAtnrG3NTSBwDfEOmAoG0IU/e2fDMutV3YR+oMP3Axzwe ulAhD7GpRyNRyFegzC05lTh4ttE6AcsucpgglZSfm6LhD1rDUAYObbs3YqkzB3vX +8cYGK+BGVD7o2x2lg3H0otPYUkEtffCmVVsDliHX2CtOxPSYq02adylbWvAI54= =CCtO -END PGP SIGNATURE-
Re: [Mageia-dev] freeze push: libktorrent ktorrent
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 03.02.2013 15:21, Nicolas L￩cureuil kirjutas: Le dimanche 3 f￩vrier 2013 13:10:59 Guillaume Rousse a ￩crit : Le 02/02/2013 22:51, Nicolas L￩cureuil a ￩crit : Hi, please push libktorrent ( and when available please push ktorrent ) this is a bugfix release only. Build error for the second one: http://pkgsubmit.mageia.org/uploads/failure/cauldron/core/release/2013020311 4409.guillomovitch.valstar.31274/log please push, i just fixed linkage Pushed by GR. - -- Sander -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJRENfbAAoJECMkkFJIyHr8eJkIAJ12M2M/nLWCW8pXlN6qjeMn H7VVrB5MQC5v0ms8IUyMYDYmFHymmXPgLldbDkj0w2iQwk557sWQvmEVDZJrCBPz dm/xYoBONxKPgDrQRFJgrV2nSc+9sir+N8gpVSGRn4/95AqzPG5Z689Ov+AHh+EC vNkq/UB2EJO4umVgUQKK+uPK3hHkbrNeLvOBxByBX1IB1N4L9syj2oTbfX+vPdXm 8smU05A02LKA2ME3KyTwAIR7J7J7NfcubbpiTBvjMgxarz95vtXZULT17R/IK4ou xEq+VDbWpsZF33+5G0rlh7ib2Cm/o/bej9p2R43RB0xJd6CE1TstHva9UYwZFDY= =7S9o -END PGP SIGNATURE-
Re: [Mageia-dev] Freeze push: mercurial 2.5
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 03.02.2013 16:52, Kamil Rytarowski kirjutas: Hello! Please push new release of mercurial 2.5. We have currently 2.4.2. It's a regularly-scheduled feature release, but it also ships with a lot of important bugfixes [1]. Regards, [1] http://mercurial.selenic.com/wiki/WhatsNew#Mercurial_2.5_.282013-02-01.29 Pushed by GR. - -- Sander -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJRENf3AAoJECMkkFJIyHr81kQH/i78DxMdarVARgVI+X4UMpBb 9qFzqr7EjKNlSBONu9h4BKuMwPLBTVFfgKZGUnv4H/Gh3cXhzUYMIufjWamm/mbU GCfSivPwvM4JM/o0M0ZudOLkkZ3XWgRTSuZO1gXKNT2flSX0cFEQt5My73YmdEiy sI8OACFY8eqpED2Bcv40gQJQCK8SZFGw+rzUtf2tPHcD+72J/8cbWJ+wA2Meq0ER LJ+lJDsmVmvdiRrPRApTU9CXdpc8WPkmsAXCXnxIDMLEKRAIoeGxoRcIbm58sNIm ufrmO9lRcnu7Odm71h+Hi1FGjt2Zid4ZHtOYL1sOm3VXaGFRcfBnxvkVJz3P/jk= =d5Hl -END PGP SIGNATURE-
Re: [Mageia-dev] freeze push powermanga
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 03.02.2013 21:40, zezinho kirjutas: Em 03-02-2013 12:44, Guillaume Rousse escreveu: Le 02/02/2013 22:24, zezinho a ￩crit : Please push leaf package powermanga : new version 0.91 mainly fixes music not playing in game Build error: http://pkgsubmit.mageia.org/uploads/failure/cauldron/core/release/20130203112829.guillomovitch.valstar.15104/log Sorry, I missed a new BR. Please submit again. Pushed by GR. - -- Sander -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJRENg7AAoJECMkkFJIyHr8D4UH/ik/xW2+edhO5aBayasM3ags xf593EmDDvl5uIjOTcYfXP8g4i3rVpdTjWlbMnL2QyRhp2Fk9XzcQn7H3CR19m9e JkcP/LCCfUnbmQmL8/xr2k2Mj8Chj5d3gd0fwzoz+NERXUNIBj8dEScHaf1S7atH 0/RCUR/zYJQtp2LVQjc2eIzONK3jOMDVkmlcWAgY09ErTwbZQ7iQCsyP01l1jH5j VazQn8rJ43JfaEDHMEi32gguNVMIu+4i6q2nMM2c7YSlaJ4D9eNR7xC7guMDeYdZ jFDtAdrizsn8L1/Bp38OUp9xQwqxtwsxtmDqODGY1EQna4F+EWlIwdvVQ5plJPs= =iuhm -END PGP SIGNATURE-
Re: [Mageia-dev] Packager's meeting
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 05.02.2013 13:04, Pascal Terjan kirjutas: On Tue, Feb 5, 2013 at 9:03 AM, Anne Nicolas enna...@gmail.com wrote: Hi there I am planning to try building failing packages with -j4 instead of -j12 to get a list of the ones which are really broken but I don't know how to handle the discussion on which ones to drop and which ones really need to be fixed Can't we have some macro for that in the build system. %make_j4 ? So we could fix them and switch the build system's %make to -j12 by default in the future? - -- Sander -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJREOlpAAoJECMkkFJIyHr8+joH/0IIsUBUkAfm+NXGRCNbu8PO nkYZT4KJE4q3a4StsL1cGIjjcivQ8J3hHtTRQf9V2ef8hL1qBCnmEwi7/e5oEltp xjRorZiYMZVs43aINjEsGURwxR786xorW/obT2GRXcEqjKyAS7TDf/1bAx8+L/e4 jxA02RLZBd1L3TQpcXqU/rkBGMBtiQjpfnRCBbBE7ZqlmeUr2yfSSqyFqtjW2uDJ Hl22r43VLKKMIkYi2j+NbMQvlk9RszETC1/jTHkIFOcWfYRoceKOwTBiODl7THCd k0Cxa6H5ZNgkiMW+PCYY5YezLawDzS+bJ8L9GNMsMiZFyvJLbv+V8XwOORCxzkg= =945f -END PGP SIGNATURE-
Re: [Mageia-dev] Segfault with new LibreOffice packages
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 31.01.2013 13:39, Robert Fox kirjutas: kernel: soffice.bin[4875]: segfault at 105cc098f ip 7f9d7d720907 sp 7fff9135ccd0 error 4 in libicule.so.50.1.2[7f9d7d70e000+3e000] Before I raise a bug, I want to check if I am the only one here . . . Since last updates of LibreOffice in cauldron - I can not start it: New icu was pushed. Maybe packages depending on it need to be rebuilded. - -- Sander -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJRClmBAAoJECMkkFJIyHr8npwH/jkTPG/eOl358NAq2mr9e2Wv NRXHnnACVRyJAw1/2xNdRaBGzCk+P9oMPMHUZ2VvDlL3z1Rk7mvfRFL2s/ZLwJor GptQ46U4WqFA91ScF/WHg++zGYpII3n3jiy2kmE1eoNrbwNxYMigctChWfANdGxM V2ylJ+cVkv21vUbbTVag9hvB07DOEpYhAfZ16I8/jDcwcbvl2jrk82wfWjTKTi/8 QzM8h9D/DRUhUKGBw6m8G6qkpXT5Snnzv9Xzzbxagn6rJ8yMmNwCcidOVn2x+kAc NScqpKmNkcBT9mV54FPxUut/EvddthMbD1LLlfMnXbRzrwaKjlGp3up0//9KS08= =MwM4 -END PGP SIGNATURE-
Re: [Mageia-dev] Segfault with new LibreOffice packages
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 31.01.2013 18:47, zezinho kirjutas: Em 31-01-2013 12:39, Robert Fox escreveu: kernel: soffice.bin[4875]: segfault at 105cc098f ip 7f9d7d720907 sp 7fff9135ccd0 error 4 in libicule.so.50.1.2[7f9d7d70e000+3e000] Before I raise a bug, I want to check if I am the only one here . . . Since last updates of LibreOffice in cauldron - I can not start it: I can start it on x86_64. Did you update icu to latest version before your test? - -- Sander -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQEcBAEBAgAGBQJRCqQNAAoJECMkkFJIyHr8bW4IALQ0mpx3oMck0fT/TvTPKeda D6SlkB2VawCAGE3hClYfcb9862dmfwEpU6nqbHm02uEVojPbRsxRV9vn7bRqGJzp y7A5e/yZmO8jCjq7YkTd4/zeN3H6EJUAW3P5Ki8UYZ/ty7Q0Lkf9ojURytv0lATT 5k6W8+R8nZs17LR2D3uhtR+M180Oqs5AkSuVpOIrIY5mZI15c/5ux8oXJ1vyJJ3P 4s0AzdLktih4oXBhE4cFtAG0082xSCUZg2bu8yH3vXLGzuIEy7Lbg7C1OVhCgcPF 1vmcDup6voFDVNu0wC09wOMa1/fyE3lIo07r7Ir7eJg/7xoXVAc2fpdChm3QjBA= =hBh+ -END PGP SIGNATURE-
Re: [Mageia-dev] [council] *ping* Media query: secure boot support
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 29.01.2013 11:11, Thomas Backlund kirjutas: And for people thinking of Windows 8 dual boot... Win8 does not _require_ SecureBoot either... (only the overprized RT does) And personally, I dont think we should ever bother with the SecureBoot crap as its flawed in so many ways... Well, the problem with SecureBoot is in the systems that are sold with W8 sticker on them. AFAIK, if manufacturer wants to have windows hardware sertification it has to enable secure boot by default. And I'm not sure how many systems allow to disable it or how easy it will be for normal user. - -- Sander -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJRB5XNAAoJECMkkFJIyHr8D64H/AqdTMOOdd/xbjgHUESDLsDo GAmg86vQL/7c845uE7LYzteDxCbaBJDaI+Xpirn0RARdKL7jvRcrhAYJSB6V3EI5 i0gfkFlz4u5j0YD+NAyTz9RBxijp2St4Tvaw1nND3BQmKGcV+kUmNwCZj/Fg9w5Z RSfJzV+0qHk5Bw/tWyzH703vaUbqbBSgdu/pl86Bg9kf0yhCe8dnINFkIfv0Nx19 JmaJ7dpdplYdgEFRhNaMzpIa5g6Xy+w95S1xGAnrH5A6P30DKUT7C0BUbS1wl/i7 veiqBXFtRFQCErga7cFHaK1b/9ZWmtHZE3edp8LRBUsDacNOhsd3j7kVPxC8qdw= =FaR/ -END PGP SIGNATURE-
Re: [Mageia-dev] Power consumption disaster with AMD open source drivers
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 30.01.2013 08:55, Mustafa Muhammad kirjutas: ... I still have a feeling to AMD, they were always better in Performance/Price) And they have never really cared about open source users.. We as a community can't do much about non-free drivers. - -- Sander -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJRCM5JAAoJECMkkFJIyHr8RVIH/1DjsFHEIjad6N5s1W979Wgv WB6tLjODuEcGqKFPd9JWQjLNXAkGIPQ+Yj9RbwbHEv5mrC1XDGN10grwf2qpKQ0f hbwOg/BGjSnNtgYfg9VC5SBZmn+yCtTkmqZPJIb3k/pqnQlK8XZUtdxSuMpMBWAb E35lJ5048D+qvNtdfpqC5KxpW5ipcPmAuodbyF3z37YSQIGmWLn85FfOwFKW+9Nm /IfcC4FJbNCw2F/saysUAMUd4uxv6nTDIdicSM0PO7I9QNI5I6jL7FIELXM2LhLj Kg05Q0VfJQU2xXaxAmOLYc/31O5xaMXlyexDhkE+XNy6UlUqRBz9qgDK/l/t9jw= =aM3p -END PGP SIGNATURE-
Re: [Mageia-dev] [changelog] [RPM] cauldron core/release hydra-7.4.2-1.mga3
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 28.01.2013 15:43, guillomovitch kirjutas: Name: hydraRelocations: (not relocatable) Version : 7.4.2 Vendor: Mageia.Org Release : 1.mga3 Build Date: Mon Jan 28 14:42:18 2013 Install Date: (not installed) Build Host: jonund.mageia.org Group : Security Source RPM: (none) Size: 669125 License: GPLv3 Signature : (none) Packager: guillomovitch guillomovitch URL : http://www.thc.org/thc-hydra/ Summary : Network logon cracker Description : A very fast network logon cracker which support many different services. guillomovitch guillomovitch 7.4.2-1.mga3: + Revision: 392917 - new version I think that's not the first package from you that breaks the version freeze w/o any notice or request on dev-ml. I know you were given the permissions to do so, but does that mean you don't have to explain anything? (just curious..) - -- Sander -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJRBoM4AAoJECMkkFJIyHr8+iwH/Roeuz9IerVnUmOHH12x9OBP bkeA1dTo9MBL0NjsptdXZNgO7aECqndbyQuNTrTcF7wUrtqJaMDqTJw+B+V+QTVL eKlR5B8AX3lTwWXuI5dZTYXX5esY0PxT4LKAlLdeykmoPvVb+ovXQJJgmNBCz5Fs 0cr2oqHkEtSCnhafZ5633CzqDcm+T6wl8UIBLlVVDebBmnt+dV8nGFRkq8ag+KWV KcNI4COqHCux+6XTujzp9dWkhY3CMS3G9UwK6a0TQsqHwBK/EzH7f/493GeiY/7v rZVwDKjdERDPMGBmi7f1FZg7Vy1ROAg6tAFVwvkIvhooDoaGfm2MMggmP1CjfhM= =TcHm -END PGP SIGNATURE-
Re: [Mageia-dev] [changelog] [RPM] cauldron core/release hydra-7.4.2-1.mga3
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 28.01.2013 17:07, Johnny A. Solbu kirjutas: On Monday 28. January 2013 14.55, Sander Lepik wrote: think that's not the first package from you that breaks the version freeze w/o any notice or request on dev-ml. I know you were given the permissions to do so, but does that mean you don't have to explain anything? As I understand it, those of us who don't have submission rights during version freeze have to explain to those who do have permission rights, why they should to push a new version. I don't see the point in guillomovitch explaining to guillomovitch why guillomovitch should push guillomovitch's packages. :-)= Let's not create more bureaucracy for the sake of bureaucracy. Last time (during mga2 freeze) people with submission rights asked from others with the same rights like everyone else. At least the line in changelog could be a bit longer than just new version. - -- Sander -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJRBpY7AAoJECMkkFJIyHr8UywIAJfTBNE6pNADYMG9I+FvYU84 BdKzJHuvlSIVSYwQW/ZDFs3jUv456+y5mwl9DhhW2onJvmeFGULHkubo54eSgoI1 8IAW2u0YXQTs9oGRwdbj/CXq3CYVmbRt3QXYleMWyzvy3Iuj+oiJn6X/RotQHQ73 2bYBSH7iVFOFZIBwd3Pndga/Ttn7vpGW0XsOqC5PmGPYtrYS99Y/Dg4Ph/D/hiTj rR4VICs2AVkhW7hMc//JhXfBoc38gxuZjm+ZnL5ZtWjYDT09tEQCTa7qgv28EA7c G/12zmf3HpUhn7aSyRNcrRUpXk01Ey+Lx05qk/eQ6aMlCvbgmAsFdD2j8raabkw= =1nYc -END PGP SIGNATURE-
Re: [Mageia-dev] gdb suggests to use debuginfo-install (from yum-utils)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 26.01.2013 18:35, Kamil Rytarowski kirjutas: Hello! gdb suggests to use debuginfo-install to install missing -debuginfo packages This is packaged as yum-utils in Fedora. I have reimplementated it [1] in a shell script (tested with Bash and Dash). Please include it to our urpmi/rpm/gdb chain and install in /usr/sbin (it requires urpmi). Regards, [1] http://svnweb.mageia.org/soft/rpm/debuginfo-install/trunk/debuginfo-install?revision=7213view=markup I think you should submit a bug report about it. So we can mark it as release blocker. And thanks for your effort! \o/ - -- Sander -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQEcBAEBAgAGBQJRBAhwAAoJECMkkFJIyHr8ZxMH/A9H72mY6ov8HqHvRzgtxQva +L9CJ1I175ZCxBQ/fLUY+Qh8JUtK6fzwRwyH1hA/5iPAnsyhZ3OJhi4ChzlGy5CU f79pNg1cd10pw/HvUkKHxPo/OCcEcBqXaNek+A5sbhdsgXJx49ypvwZV038NzJhR pk/0Qgqv6TjQDfzEJXfzPZLV01jpBt8WkdMHmlBP1GoCYFaoNyvol/F6qFW+NyH7 n/vzptsHusewqI+bLUPBiSQjYMPSQ12jmE0rdD8YBYmLm7uJdcoSF0NVrxS0GDKI e3glVEaso+4uSj06PkuR4On/q7YMGaMkiKZba2tpQdTxfYk7JK6zFCvNmosqnKU= =wpG1 -END PGP SIGNATURE-
Re: [Mageia-dev] Mageia 3 beta 2 experiences
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 26.01.2013 20:00, Thomas Spuhler kirjutas: On Friday, January 25, 2013 04:50:32 PM Anne Nicolas wrote: Hi there The release is finally done. Isos of beta2 are available on public mirrors: http://blog.mageia.org/en/2013/01/25/time-for-tests-mageia-3-beta-2-is-out/ Thanks for all the hard work. We are now in the last run. We need tests more than ever. Enjoy! I downloaded the B 2 KDE Live CD ISO last night, burned a CD and put one on a USB stix I tried to boot an older DELL Inspiron K1405 laptop. Unfortunately, I experienced the same problem as I did with Mageia2 Live CD on several DELLs, a dark screen at about when the login windows should show up. This worked in B1 When I hit the ESC button shortly after the boot process start, I can see the progress up to the point where the network-up/down comes up and then the screen turns dark I then installed the B1on the same laptop and it went pretty smoth. The one exception is, the wireless card doesn't work as before. It wants to install the broadcom wl driver which we know doesn't work on this box as it has the BCM4311 It worked very well with the w43 driver that was on the test Live CD (I believe from tmb) Does it work with bcma (https://bugs.mageia.org/show_bug.cgi?id=7828#c14)? - -- Sander -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQEcBAEBAgAGBQJRBDtPAAoJECMkkFJIyHr8GkEH/1M0WdKOxe7H/4vYEwjAwtkA K1oZCxfXR/DfpoSSukyV46DmCTx6wDznoHDadgnnj0npm5ra2nBisSz8Wp9St8HQ Umk0vwSkjUJcRdBQ2HjlrlkrbL+am0lJKmgeX0XEpE+SBiL/DK3I35KOCmIin6WY HPl3uu4qqC9jDo2ir825gvOvrsiuK6boklJjy0J2DG6QOZq/TZ8o9MqTPR9qvaOu 40s03hhFoMIj+6a1+aK/XNulIv5iwI1i8Ikj8SrUs9Wn1xwQdqF67tbdYO6bjoIK sdav5Kqs3rDSvB2j9dxJ2pBs9Zit66KMnNlfbW6w1vShm+FwGybt5wZx1tjk7jA= =B2DQ -END PGP SIGNATURE-
Re: [Mageia-dev] [changelog] [RPM] cauldron core/release python-distribute-0.6.34-3.mga3
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 24.01.2013 05:22, Thomas Spuhler kirjutas: On Wednesday, January 23, 2013 03:29:30 PM Pascal Terjan wrote: On Wed, Jan 23, 2013 at 7:48 PM, spuhler buildsystem-dae...@mageia.org wrote: Name: python-distributeRelocations: (not relocatable) Version : 0.6.34 Vendor: Mageia.Org Release : 3.mga3 Build Date: Wed Jan 23 20:48:19 2013 Install Date: (not installed) Build Host: jonund.mageia.org Group : Development/PythonSource RPM: (none) Size : 646093 License: Zope Public License (ZPL) Signature : (none) Packager: spuhler spuhler URL : http://pypi.python.org/pypi/distribute Summary : Python Distutils Enhancements Description : A collection of enhancements to the Python distutils that allow you to more easily build and distribute Python packages, especially ones that have dependencies on other packages. spuhler spuhler 0.6.34-3.mga3: + Revision: 391715 - removed the python-pkg-resources package moved the two files into the main package It interferes with the python-setuptools package This broke the build system A requested package cannot be installed: rpm-mageia-setup-build-1.166-2.mga3.x86_64 (due to unsatisfied python-pkg-resources) I eliminated the package python-pkg-resources and put the two+ files into the basic package python- distribute. The reason is as stated below: Hey! I can see you have imported python-distribute that generates package python-pkg-resources. And now the problem: http://pkgsubmit.mageia.org/uploads/rejected/cauldron/core/release/20130113212011.umeabot.valstar.22055.youri - - python-setuptools generates package with same name. I think you should rename yours to python-pkg-resources-distribute or something like that. python-pkg-resources should come from python-setuptools but i can't push it as there is newer version from python-distribute in the repo: http://pkgsubmit.mageia.org/uploads/rejected//cauldron/core/release/20130124075645.sander85.valstar.9472.youri I think we need some help from sysadmins here :) - -- Sander -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJRAOsXAAoJECMkkFJIyHr8nAQH/RzaWel4YPJyx24KauxRnBBG 15KjFyQJtF3xYH1bSuQKw9t3vEMETt7nicBHERvQMdnaio+qXpd7kB+zyu2fIAz7 FScGmmp9dqocnts47GCmK5YYJze157AExEYDcQUxKqrb/ru/XiVRV/e08MUlUk4K LANn3RUXXRJwvXj1b18wIWsokdmibADvZCtMwILJ0BjiTa8LRxM7zwkFegu1mLEz KjMiPl/atSHIojXevvHmpvCyEleJHiNE4qlRrvy0fAxu6pke2YH+n8xzIVn/7so7 hwKaOubOBagk9cNPAQOPFHGe6GzoeFs7+TzyNDDGMsZ8NGZa+K7ilTbjQukZgh8= =HD2I -END PGP SIGNATURE-
Re: [Mageia-dev] [changelog] [RPM] cauldron core/release python-distribute-0.6.34-3.mga3
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 24.01.2013 12:28, Pascal Terjan kirjutas: On Thu, Jan 24, 2013 at 3:22 AM, Thomas Spuhler tho...@btspuhler.com wrote: I eliminated the package python-pkg-resources and put the two+ files into the basic package python- distribute. The reason is as stated below: Hey! I can see you have imported python-distribute that generates package python-pkg-resources. And now the problem: http://pkgsubmit.mageia.org/uploads/rejected/cauldron/core/release/20130113212011.umeabot.valstar.22055.youri - - python-setuptools generates package with same name. I think you should rename yours to python-pkg-resources-distribute or something like that. The problem is that python-distribute should have then been uploaded just after. python-pkg-resources got cleaned from the mirrors because it was a leftover package built from a src.rpm which no longer existed, and the one from python-distribute had not been uploaded. Not python-distribute but python-setuptools. They both had python-pkg-resources as sub-package. And as python-distribute has bigger version its subpackage was uploaded. That package should come from python-setuptools as it was before Thomas imported python-distribute. - -- Sander -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJRAQ7JAAoJECMkkFJIyHr8iJYIALJDCZI+/3RtDTVYD4pu4LOi TLRYMgPMnXWBxfvWEyIk5WS94dx6F9m3DKXkM+aVSCbytwXxXXUFom3g0HB1C2TW /n2Slcqh/HhUvtLTykXllrxjZeYM03h79lmcoeFOVUEOeb0SeZJZH1r07wER46Xw EBhkJS0JESLuDotqJwnAchs51p9/3lcoHP9MgpqMvGb7vUa8HrFYAv7Z/6+5Fluw /cX1vTItRvRtplul4/DHk65UY5Jpzytw5pFQm+1rNpsET80Wimja3JO+NrtgH00s n06mV9NkkugykoCaJ9lx/Pjr9FIHqIr5Efmk02fPgw0Z/jIlXSd93WE+ZWqgc9o= =UPge -END PGP SIGNATURE-
Re: [Mageia-dev] freeze push: perl-Class-InsideOut
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 24.01.2013 15:47, nicolas vigier kirjutas: On Thu, 24 Jan 2013, nicolas vigier wrote: On Thu, 24 Jan 2013, Jerome Quelin wrote: Hi, Can you push perl-Class-InsideOut which fixed its tests to pass with recent Scalar::Util please? This means the pkg will be rebuilt fine with the mass rebuild. Submitted. But failed : http://pkgsubmit.mageia.org/uploads/rejected//cauldron/core/release/20130124133911.boklm.valstar.21149.youri URL fixed, please submit again. - -- Sander -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJRAT0MAAoJECMkkFJIyHr8OIEH/R/VA+9cO+L9wQfTpqERPJwm GZIce7TaioSfucVeFRLXPXa1TRcLdv+8+Y9FE9sp0U/w+8kJprbL6Iwc1nB7GezC pw2ZLQIupuGt2XTwEJIkHUZ9YjmlTepoB3n1jeyTJhSkEzW/+ZuiC/MRB1tQu9Se TmKF5sXzqS0CKAkwkqRTFRQ/dTiFAHC3WgHU8obS3AC/+EAuvlUQt8RKP5pSI8Pm AVq2IKy1/YPDsnHxhEmTsTfoN/L+Ew8l+2LxJJBF+zWU/koEGjlEhiI5NzvptvH0 5Ny4HiLgaY9eS1JrRpPbQYZi3AAUhr1u0v02WC/tiyT2PERn7eDia1MYtS82sM4= =pDwh -END PGP SIGNATURE-
Re: [Mageia-dev] /run/httpd (maybe others) breaking features
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 24.01.2013 02:24, Pascal Terjan kirjutas: I was looking at perl-Apache2-DebugFilter build failure In the test it starts an apache which fails as it uses http://httpd.apache.org/docs/trunk/rewrite/rewritemap.html#prg which uses a mutex stored in /run/httpd/ [Wed Jan 23 23:49:55.962405 2013] [core:emerg] [pid 55277] (13)Permission denied: AH00023: Couldn't create the rewrite-map mutex (file /run/httpd/rewrite-map.55277) That directory is now owned by root so it can't be used for anything except creating the httpd.pid $ cat /usr/lib/tmpfiles.d/httpd.conf d /run/httpd 755 root root Fedora uses d /run/httpd 710 root apache which doesn't help in this case but fixes other problems Why can't we use d /run/httpd 710 apache apache. It's quite possible that apache is trying to create this file as apache not as root. And with current permissions only root can write into that directory. - -- Sander -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJRAOe7AAoJECMkkFJIyHr8EtYH/2/H0musOzg8hKinO0OcEj55 fkHKHFr2+m2ge9lD35TkXcXPBTAlNPILPm2d+/S6mrsmCHtEei++LJYtJXyR8m9s MZyP/r98NdDf4r2EQW+sBLm7IN1csR+pial7tGNnsjvvVZo6gQcbHNeEjZPxTjXC 2N0FGeVYljxMfjvYRbeyq7RejLmZPsEG47fqr4EhdBwp6HykyaDyk4v+0VrzJNYD fUthrGk6hBVZqgMG7GmiWzOehplKkzD3M7vGz3LNXwmpIEW+v06tXiVgHdIcQkma 4EjMast6bze+NVLhtfs4yyslkjhf5J8EnPZ//cbRiVH81sXfJOtNkWD2+N3Xzbo= =H0kN -END PGP SIGNATURE-
Re: [Mageia-dev] What's the point of the latest nvidia update?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 20.01.2013 18:30, Robert Wood kirjutas: Thanks for the reply, but it doesn't really make sense or seem to answer the question. I was wondering why bother with v295 when you could go for a more recent (ie most up to date) release?! Our goal is to keep stable releases stable. New version may introduce regressions - this is not something we want to see in stable release. - -- Sander -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQEcBAEBAgAGBQJQ/DgvAAoJECMkkFJIyHr8X8oH/3mZFCCIPjXSKtDzU+d42uIK yQxEYM+cO+hl5WhZHhi4pQ3HpNHcc77UltGdyV5I/glSknPB+cJtLbuDo/GHn7Ij Kfkvk+VuNN1GZ7KJRN2ejtcTheoW5mM87N1ForOre667kkiEf7p+JRdRhs71rAGk IxcrQjJ1A9egzuzmXF+zwzSNOU0gE/HC6MMGz6/PpJ5/fyGLwWreETy4ZmDQYz5e CZkkQproz+OY98I55nBwpgibkPH6OQKzp8QsSsop3Gv0WONrzxzVQuCasPOdL+yX DCjXkobMaSaRzbdrDMw7iv5yTxThtHZmqBWT5Uj2HTBlobiKh7C6Knh7l5CQ2hM= =jcee -END PGP SIGNATURE-
Re: [Mageia-dev] Feedback on Mageia 3 beta1
17.01.2013 01:10, Davy Defaud kirjutas: - more annoying, there was no syslog daemon and I had to install rsyslog by myself. It seems that none of the core packages is requiring a syslog daemon (unless systemd is supposed to handle the syslog in a way I'm not aware of); FYI: http://www.zarb.org/pipermail/mageia-dev/2012-October/019581.html -- Sander
Re: [Mageia-dev] [changelog] [RPM] cauldron core/release jboss-web-native-2.0.10-3.mga3
16.01.2013 10:30, dmorgan kirjutas: Name: jboss-web-native Relocations: (not relocatable) Version : 2.0.10Vendor: Mageia.Org Release : 3.mga3Build Date: Wed Jan 16 09:30:21 2013 Install Date: (not installed) Build Host: ecosse.mageia.org Group : Development/Java Source RPM: (none) Size: 4987642 License: LGPLv2+ and ASL 2.0 Signature : (none) Packager: dmorgan dmorgan URL : http://www.jboss.org/ Summary : JBoss Web Native Description : This package contains support for Apache Portable Runtime (APR) in JBoss AS. dmorgan dmorgan 2.0.10-3.mga3: + Revision: 388612 - imported package jboss-web-native I don't want to be rude but you import a lot of java packages. Are you sure that all the already imported packages are fixed? I think you should first fix those and then import more :/ (No hard feelings ;P) -- Sander
Re: [Mageia-dev] Freeze push: ibus, ibus-anthy
16.01.2013 15:31, Funda Wang kirjutas: ping? -- Original -- From: Funda Wangfundaw...@fundawang.name; Date: Wed, Jan 16, 2013 08:23 AM To: mageia-devmageia-dev@mageia.org; Subject: [Mageia-dev] Freeze push: ibus, ibus-anthy Hello, Could ibus and ibus-anthy be pushed into core/release? We target at 1.5.x for mga3, and we now have 1.4.9x beta versions. PS, you must remove corresponding packages from core/updates_testing before pushing them. Thanks. Should we think about some better system how to deal with freeze pushing? A lot of pinging but some requests get no response. And then people with proper privileges deal with some of the requests but not with all. Soon we have 3x ping and still no reply when some packages get submitted with first request. Wiki page to list requests? So submitters can have a better overview? -- Sander
Re: [Mageia-dev] Freeze push: ibus, ibus-anthy
16.01.2013 16:53, Colin Guthrie kirjutas: 'Twas brillig, and Sander Lepik at 16/01/13 14:02 did gyre and gimble: 16.01.2013 15:31, Funda Wang kirjutas: ping? -- Original -- From: Funda Wangfundaw...@fundawang.name; Date: Wed, Jan 16, 2013 08:23 AM To: mageia-devmageia-dev@mageia.org; Subject: [Mageia-dev] Freeze push: ibus, ibus-anthy Hello, Could ibus and ibus-anthy be pushed into core/release? We target at 1.5.x for mga3, and we now have 1.4.9x beta versions. PS, you must remove corresponding packages from core/updates_testing before pushing them. Thanks. Should we think about some better system how to deal with freeze pushing? A lot of pinging but some requests get no response. And then people with proper privileges deal with some of the requests but not with all. Soon we have 3x ping and still no reply when some packages get submitted with first request. Wiki page to list requests? So submitters can have a better overview? Perhaps a some kind of system whereby mgarepo submit will actually allow you to enter a reason if freeze is involved and some kind of web UI to list outstanding requests and/or authorise them if you are an admin? Or even some cmdline mgarepo freezereqs to list and mgarepo freezepush $id? Could be a Feature for the mga4 cycle perhaps? Col Bug is another way. As sometimes submitters have to ask questions. And then some saved search to find all pending requests. -- Sander
Re: [Mageia-dev] Mageia 4 question
13.01.2013 13:58, zezinho kirjutas: Em 13-01-2013 05:54, Joseph Wang escreveu: Question: I have a large number of packages on my machine that are intended for Mageia 4 release. Should I wait until after the Mageia 3 release to check them in, or can I check them in now and not submit a build request. Either is fine with me, and the only reason for checking them early is so that it doesn't get lost if I have a local machine crash. Why don't you import them now, and submit them for MGA3? New packages are still accepted! Because he was not allowed :) -- Sander
Re: [Mageia-dev] The upcomming MSN network shutdown is postponed
12.01.2013 10:05, AL13N kirjutas: We should drop all msn related things right now, just in case it's all shut down. We have no reason to drop them just yet. They will work another year. Who knows, maybe even more. -- Sander
Re: [Mageia-dev] proftpd - why was mdv package imported over ours nuking our changes???
12.01.2013 16:52, Bersuit Vera kirjutas: Hello, I'm sorry, I'm just Padawan, I thought it was working fine. I'll try to fix it as soon as possible What would be the best way to fix it? Colin already fixed it. But this should not happen again. May I ask who's your mentor? And who allowed such push? You can cherry-pick changes from other specs but you can't replace the whole spec. Your mentor should know that.. -- Sander
Re: [Mageia-dev] The upcomming MSN network shutdown is postponed
12.01.2013 23:17, AL13N kirjutas: Op zaterdag 12 januari 2013 11:23:05 schreef Sander Lepik: 12.01.2013 10:05, AL13N kirjutas: We should drop all msn related things right now, just in case it's all shut down. We have no reason to drop them just yet. They will work another year. Who knows, maybe even more. i guess you didn't see the sarcasm... I guess I didn't :) -- Sander
Re: [Mageia-dev] rootcerts: Are the certs really config files?
07.01.2013 13:51, Colin Guthrie kirjutas: Hi, I just updated rootcerts package on my cauldron box and got about 50 ish .rpmnew files for changed pem files. It seems mostly indentation changes (*sigh*) but it made me think - Are these really config files? I'd expect these to not be marked as config even if they are kept in /etc/ Ideally I'd rather see them kept in /usr/share anyway as that seems more appropriate, but that's likely not possible without causing a lot of pain. Col I fully agree. Certs are quite far from config files. And I even see some possible trouble here. If some cert is updated and the user gets it as .rpmnew file and is noob enough to not notice it then (s)he will be using wrong cert.. -- Sander
Re: [Mageia-dev] ANN: glibc-2.17 landing on cauldron...
07.01.2013 21:19, Juan Luis Baptiste kirjutas: This ssh closed connection issue I have seen it since a long time, is there any way to avoid it ? it sometimes breaks the update process of that remote vm. If i'm afraid that something might blow my connection during update then i use screen. It might drop me out but update will continue and usually quite soon i'm able to reconnect. -- Sander
Re: [Mageia-dev] RFC: dropping prebuilt broadcom-wl drivers
27.12.2012 18:28, Thomas Backlund kirjutas: Thomas Backlund skrev 27.12.2012 17:01: [...] Theese are exactly the same as the official beta1 isos, with only exceptions are the broadcom-wl tests: * No broadcom-wl drivers on iso, and no wl entries in ldetect-lst: http://distrib-coffee.ipsl.jussieu.fr/pub/linux/Mageia/people/tmb/mga3-beta1-wl-test/Mageia-3-beta1-no-wl-LiveCD-KDE4-en-i586-CD/ So i used this iso to test. At first i saw such device reported for wifi connections: Wireless (Wi-Fi) Broadcom Corporation BCM43224 802.11a/b/g/n Clicking on it prompted to install wl stuff. So no luck at first. Then i checked dmesg and saw that b43 was loaded. I ran rmmod on these modules: b43, brcmsmac, bcma After that i blacklisted b43 in /etc/modprobe.d/blacklist-mga.conf and reloaded bcma. Now i saw new interface wlan0 and i was able to configure it. But connection test failed. I think it failed because wpa_supplicant was in bad mood. As i couldn't restart LiveCD i just ran service network restart. After that my laptop connected automatically and network was usable. So if wrong modules are blocked and correct ones loaded then everything seems to work. Output of lspcidrake -v: wl : Broadcom Corporation|BCM43224 802.11a/b/g/n [NETWORK_OTHER] (vendor:14e4 device:4353 subv:1028 subd:000e) (rev: 01) -- Sander
Re: [Mageia-dev] RFC: dropping prebuilt broadcom-wl drivers
27.12.2012 00:54, Thomas Backlund kirjutas: Hi, I'm thinking of dropping the nonfree prebuilt broadcom-wl drivers (and thereby their support from live images) This means also dropping them from ldetect-lst, and if we keep/add some there, it must be for specific reason and on sub-vendor/device level to not force the wl stuff on everyone... [...] To do this I suggest we should do this asap, and keep it for atleast mga3-beta2 isos, so we can check how it works out... Comments ? I'm OK with that as currently i can't use wifi on LiveDVDs. wl driver is causing more mess than it's helping to resolve. -- Sander
Re: [Mageia-dev] Problem with urpmq ??
26.12.2012 16:33, Robert Fox kirjutas: [root@mainfox rfox]# urpmq ssh No package named ssh [root@mainfox rfox]# urpmq sshd No package named sshd [root@mainfox rfox]# urpmq kernel No package named kernel [root@mainfox rfox]# urpmq kde No package named kde Doesn't seem to work anymore . . . Merry XMas - R.Fox I think you have to use urpmq -y ssh Or --fuzzy if you like the long version. -- Sander
Re: [Mageia-dev] task-obsolete - questions about implementation details and how to disable it
25.12.2012 20:41, Florian Hubold kirjutas: Hello, this should not be about complaints, only some technical questions. How is task-obsolete supposed to work as a package, i.e. what is the mechanism used to pull it in, and then remove it again? It is required by nothing else, so i guess this is either pulled by urpmi/perl-urpm/rpmdrake itself. Can sombody enlighten me about this? AFAIK task-obsolete is pulled in by rpmsrate. And the next step would be the question for the proper way how to disable this mechanism as an enduser. As root, run this command: echo task-obsolete /etc/urpmi/skip.list This will add task-obsolete into the skip list and you can use obsoleted software. -- Sander
Re: [Mageia-dev] LastFm going subscription
14.12.2012 09:57, Götz Waschk kirjutas: On Fri, Dec 14, 2012 at 12:26 AM, Charles A Edwards c...@eslrahc.com wrote: Beginning Tuesday 15 January 2013 radio streaming within the desktop client will only be available to Last.fm subscribers (monthly fee). Due to this should not lastfm-player either be dropped or moved to nonfree now before Mga3 goes final? It could be dropped or stay for those who want to pay the 3€ a month. I don't see any reason to drop it. Only if maintainer doesn't want to maintain it anymore and there is no other maintainer to take it. But so long i was using it with paid subscription - can't do it next year, but i still think it shouldn't be dropped. -- Sander
Re: [Mageia-dev] [changelog] [RPM] cauldron core/release task-obsolete-3-37.mga3
08.12.2012 12:01, shikamaru kirjutas: Name: task-obsoleteRelocations: (not relocatable) Version : 3 Vendor: Mageia.Org Release : 37.mga3 Build Date: Sat Dec 8 10:57:14 2012 [...] shikamaru shikamaru 3-37.mga3: + Revision: 328123 - drop ruby-ParseTree https://wiki.mageia.org/en/Packaging_guidelines#Obsoleting_a_package - i can still see it in SVN: http://svnweb.mageia.org/packages/cauldron/ruby-ParseTree/current -- Sander
Re: [Mageia-dev] Mageia 1 EOL.
02.12.2012 08:46, blind Pete kirjutas: One and a half release cycles? Perhaps future realeases could have; 9 month release cycle, 12 month full support, 15 months partial support? Our releases already have 18 months full support. And as David already said, we lack enough QA people. QA can't support 2 releases + test 3rd one at the same time. If we want Mageia 3 to be good and tested distro then we have to give QA more time to play with it. -- Sander
Re: [Mageia-dev] Mageia 1 EOL.
02.12.2012 21:14, Kamil Rytarowski kirjutas: Hello! It's not the best idea to start with packaging Firefox and Thunderbird: 1. Both packages are advanced and hard to maintain 2. If someone really wants the newest release of FF or TB, then he will simply download a binary from the upstream webpage, unpack in $HOME and use... First Funda, now you.. please stop that top-posting, both of you :/ -- Sander
Re: [Mageia-dev] [changelog] [RPM] cauldron tainted/updates_testing libxcb-1.9-1.mga3.tainted
30.11.2012 10:17, Götz Waschk kirjutas: On Fri, Nov 30, 2012 at 8:50 AM, tv buildsystem-dae...@mageia.org wrote: Name: libxcb Relocations: (not relocatable) Version : 1.9 Vendor: Mageia.Org Release : 1.mga3.taintedBuild Date: Fri Nov 30 08:48:17 2012 Hi, why is this in tainted? Regards, Götz https://www.mageia.org/pipermail/mageia-sysadm/2012-November/004875.html -- Sander
Re: [Mageia-dev] Cinnamon uploaded
26.11.2012 15:23, Joseph Wang kirjutas: Hi all, I've uploaded the packages needed to get cinnamon working with Mageia. These include cinnamon nemo muffin task-cinnamon I don't have submission privileges so I'll need someone to review the packages and then kick off the build. It's a lot nicer than gnome3. I'm in the process of trying to figure out how to package some extra themes and applets. Hmm, have you missed that there will be no Cinnamon in Mageia repos? Part of packagers job is to keep eye on the dev ml. FYI: https://www.mageia.org/pipermail/mageia-dev/2012-November/020196.html -- Sander
[Mageia-dev] Mailing-list archives and robots
I was trying to find something from dev-ml archives with google and found nothing. Then i checked our archives source and found 'META NAME=robots CONTENT=index,nofollow'- is there some good reason for nofollow? Or should i use something else to search our archives? -- Sander
Re: [Mageia-dev] Mailing-list archives and robots
26.11.2012 16:52, Olav Vitters kirjutas: On Mon, Nov 26, 2012 at 03:51:11PM +0200, Sander Lepik wrote: I was trying to find something from dev-ml archives with google and found nothing. Then i checked our archives source and found 'META NAME=robots CONTENT=index,nofollow'- is there some good reason for nofollow? Or should i use something else to search our archives? Normally you'd set nofollow on individual archived messages. The general index page should NOT have nofollow. This ensures that if some spam arrives to an free to post mailing list (e.g. the sysadmin one), it doesn't put the spam site higher in Google. IMO this is good to do, and it also should indicate to Google that you're not a spam site yourself (e.g. I assume Google lowers sites which have loads of links to spam sites). Good point! So we are probably missing links to our archives (as i can't find anything that links to mageia-dev archives). -- Sander
Re: [Mageia-dev] what is this ????
24.11.2012 17:41, Wolfgang Bornath kirjutas: 2012/11/24 Johnny A. Solbu coo...@solbu.net: On Saturday 24. November 2012 12.58, PhilippeDidier wrote: Someone want to be paid for his work on Mageia I have no problems with people working on mageia for money, as long as they adhere to our rules. If this results in more bugs being fixed, then we are benefitting from it. Many of the kernel hackers are paid by their employers to work on the kernel. Others are paid to work with a distribution. This is not new. Such a page might need an agreement before being published ... don't you think so ? I think so, yes. The current page implies that this is a Mageia project. I have no problem with the content itself. But the content of that page belongs on the authors webpage, not on the Mageia wiki. The page should be deleted. Well, actually I think the page needs some editing. As it is now it may give wrong ideas (as we see in this thread). What the page really says is that if Mageia does not offer any solution for a given bug because of lack of time or lack of interest by the developers a user is able to address the developers with a financial offer like fix this bug and I would pay 50 EuroCents. What the page does not say: it is not an advertisement of one or more Mageia developers offering paid service. It is merely a text telling the users that in a certain case this option is possible - keeping in mind that the resulting fix will still be free for all Mageia users to use. So, IMO the offer is something similar to Ubuntu's offer to be able to donate to a single project inside the distribution. With a better phrasing the page may be ok. Of course the details should be discussed in public and after that the option should be advertized in a blog. +1 on that. I have had similar idea myself. Watching bug 2317 or considering the fact that we still lack backports support. If someone is willing to pay for it to get solved then why not? And as the page says, Mageia can still refuse the solution. For example: someone wants Cinnamon to work on Mageia and someone else ports it. But it won't be imported into Mageia. They can have their own repo for it. -- Sander
Re: [Mageia-dev] what is this ????
24.11.2012 18:55, PhilippeDidier kirjutas: NO ! You mean someone is paid and create a third repo for something Mageia doesn't want to import... If that thing brings a mess into Mageia, we will see bug reports in bugzilla and lot of time lost by Mageia bug-triagers, devs, packagers, before discovering that is not a Mageia problem but that this stuff brought some shit ! We suffer of lack of time... and this will consume more time from voluntary contributors to repair something badly done by someone that was paid for it ! Well, we have such repos already today and you can't stop something like that. But you saw my example the wrong way. Mageia doesn't have to support those repos and problems caused by such packages. I don't like such repos either and i hope that paid people fix things in our repos. -- Sander
Re: [Mageia-dev] [changelog] [RPM] cauldron nonfree/release get-skype-4.1.0.20-1.mga3.nonfree
21.11.2012 21:25, Olav Vitters kirjutas: On Thu, Nov 15, 2012 at 10:12:31AM +0100, sander85 wrote: sander85 sander85 4.1.0.20-1.mga3: + Revision: 318152 - New requires - New version: 4.1.0.20 A requested package cannot be installed: get-skype-4.1.0.20-1.mga3.nonfree.noarch (due to unsatisfied libqtopengl4) Does it dynamically open this or something? This should be automatically. In any case, lib64 on x86_64. You have to enable Core 32bit repos. -- Sander
Re: [Mageia-dev] Broken Mageia-Update (Urpmi)
18.11.2012 17:09, Thomas Spuhler kirjutas: On Sunday, November 18, 2012 05:20:09 AM Anssi Hannula wrote: 18.11.2012 13:30, Thierry Vignaud kirjoitti: On 18 November 2012 11:38, Anssi Hannula an...@mageia.org wrote: Bug has been filed: https://bugs.mageia.org/buglist.cgi?quicksearch=looping+forever Updating Cauldron is broken as of this morning - [root@mainfox rfox]# urpmi --auto-update -v [...] detecting looping forever while trying to resolve dependancies. Aborting... Try again with '-vv --debug' options at /usr/lib/perl5/vendor_perl/5.16.2/x86_64-linux-thread-multi/URPM/Resol ve.pm line 1061. unlocking rpm database unlocking urpmi database It seems the loop threshold Resolve.pm:1061 is way too low and detects looping when there in fact isn't any. I bumped it up by several orders of magnitude locally and then urpmi worked again. To what value did you bump it? To 10, but that was just a random value since I mainly just wanted the upgrade to work. I don't know what would be a reasonable value. Did you upgrade it on the server? if yes, this didn't solve the problem. No he didn't. Thierry, are you sure that your limit is correct? If 10 works then i don't see it as an endless loop. Current value seems to be too low and there are soon as many bugs about update problems than we have about broken draksnapshot. -- Sander
Re: [Mageia-dev] [changelog] [RPM] cauldron core/release libqwt-6.0.1-2.mga3
18.11.2012 13:43, Jose Jorge kirjutas: Le 18/11/2012 00:56, Sander Lepik a écrit : 17.11.2012 23:57, zezinho kirjutas: Name: libqwt Relocations: (not relocatable) Version : 6.0.1 Vendor: Mageia.Org Release : 2.mga3Build Date: Sat Nov 17 22:56:14 2012 zezinhozezinho 6.0.1-2.mga3: + Revision: 319237 - obsoletes qwt5 Next time please read or policy before doing something that stupid (or at least have a *very* good reason) :) Revert-revert-revert! All this shots make me understand I did something stupid, but I don't see where : I followed the libs policy page. - libqwt package went to 6 - Should I create a libqwt5 package? You should NOT obsolete library that has different major (especially if there are packages that depend on that older library). Now to fix the mess: - create libqwt5 package - do not obsolete it with libqwt - rebuild all packages depending on libqwt (if they don't build with new version, switch them to libqwt5) -- Sander
Re: [Mageia-dev] [changelog] [RPM] cauldron core/release libqwt-6.0.1-2.mga3
18.11.2012 16:52, zezinho kirjutas:
Now to fix the mess:
- create libqwt5 package
Done, but cannot submit it because a libqwt5 package already exists. Any hint?
You can't submit it because your main package (Name: libqwt5) and library
package for i586
(%define libname %mklibname qwt %{major}) have the same name. As main package
contains no
files i would probably rename it to qwt (Name %realname), but i'm not 100% sure
if that's
the right thing to do. Packagers with more knowledge may have better ideas.
--
Sander
Re: [Mageia-dev] [changelog] [RPM] cauldron core/release libqwt-6.0.1-2.mga3
17.11.2012 23:57, zezinho kirjutas: Name: libqwt Relocations: (not relocatable) Version : 6.0.1 Vendor: Mageia.Org Release : 2.mga3Build Date: Sat Nov 17 22:56:14 2012 zezinho zezinho 6.0.1-2.mga3: + Revision: 319237 - obsoletes qwt5 Next time please read or policy before doing something that stupid (or at least have a *very* good reason) :) Revert-revert-revert! -- Sander
Re: [Mageia-dev] mariadb needs to have the rel bumped
12.11.2012 00:46, Funda Wang kirjutas: So it means some bugs or even security problems are not fixed in cauldron but in stable releases? I thought they should be fixed at the same time. BTW, is there any reason why we won't upgrade to mariadb 5.5.28 at the moment? BTW, is there any reason why you don't want to respect others following this ml? I respect your work and all but your replies start to annoy me :) (Yeah, offtopic, but please try to stop top-posting...) -- Sander
[Mageia-dev] Weird memory leak in X
I opened a bug @ https://bugs.mageia.org/show_bug.cgi?id=7953 Long story short: I'm using KDE + some GTK apps that have blinking icons (XChat, Pidgin). When those icons are blinking, X will start to leak memory (~100MB per day, sometimes more). And i have no idea how to trace this leak :/ It seems to have no connection with Graphics Card, i can reproduce it with Intel and Nvidia (both drivers, nvidia and nouveau). I'm having that bug on mga2, if someone can test it on cauldron too it would be great. And all ideas on how to trace this weirdness are also very welcome! Thanks! -- Sander
Re: [Mageia-dev] Repository access problem?
29.10.2012 14:50, Frank Griffin kirjutas: On 10/29/2012 08:06 AM, Wolfgang Bornath wrote: No, not really. We sync with distrib-coffee but we do not get as far as the -delete option could do any damage: But putting rsync on hold until the situation is cleared up is certainly a good idea. 1 Minute ago distrib-coffee answered to our sync request: --- receiving incremental file list rsync: change_dir /linux/Mageia (in pub) failed: No such file or directory (2) ... I checked, all our Mageia branches with all packages are still here! :) Yes, rsync at the moment aborts because of missing directories. The danger will come as the directories get restored and are virtually empty, because rsync --delete will blow away all of the taget directory files that don't exist in the source. I hope they are smart enough to first turn off rsync, then resync everything and reenable rsync again. -- Sander
Re: [Mageia-dev] urpmi --no-md5sum
16.10.2012 14:28, Frank Griffin kirjutas: This used to allow installation of packages with no signature without prompting. Recently, there have been a bunch of packages in cauldron with no signature, but I'm finding that urpmi --auto-update --no-md5sum is prompting me anyway for each such package. Am I incorrect in my assumption of how this should work ? If not, I'll enter a bug report. Isn't --no-verify-rpm the right thing to use here? -- Sander
Re: [Mageia-dev] Tonight's meeting
16.10.2012 18:42, Anne Nicolas kirjutas: Hi there Unless you have specific topic for meeting we will postpone it until next week. About mentoring, mentors couls you please update the wiki page. Apprentice please ping me if you are still waiting for a mentor. Cheers I haven't heard a word about mass rebuild. Alpha3 seems to be the last milestone for it to happen or we have to cancel this for mga3. -- Sander
Re: [Mageia-dev] iDevices support (was Re: [changelog] [RPM] cauldron core/release libimobiledevice-1.1.4-2.mga3)
15.10.2012 02:51, Olivier Blin kirjutas: Thierry Vignaud thierry.vign...@gmail.com writes: Suggests means not having it on install DVD... Can't we fix bcd to handle suggests? Suggests usually pull in important features. I think that would bloat or image and is not really needed. -- Sander
[Mageia-dev] Problem with NetworkManager and system wide connections
Hey! I have some very stupid problem on Mageia 2 with NM. I created system wide connection so that it gets connected at boot time. Now if wifi happens to drop for some reason, NM won't reconnect and asks for *root* password. Search results so long show that i'm not the only one having that problem. And some suggest to add my user to network group. I think it's a bad idea and in Mageia we have solved such problems better. Any ideas how can i avoid that root password prompt? -- Sander
Re: [Mageia-dev] Problem with NetworkManager and system wide connections
15.10.2012 12:18, Colin Guthrie kirjutas: We could of course tweak the default polkit policy here to not require that, but is that wise in and off itself? e.g. you wouldn't want a student to reconfigure the terminals in a university network without authorisation. It should likely be tied to security levels in some capacity. Col Yes, i wouldn't want that. But the question is not about configuring. It's about reconnecting. It can perfectly connect at boot w/o asking any password. Now connection drops and all it should do is reconnect as it did at boot. Why ask for password now? :/ It should be quite easy to reproduce, just unplug router and plug it back, wifi is available but you are prompted for root password to connect. I don't want to share my root password so user could reconnect, other option seems to be reboot which isn't quite normal solution either :) -- Sander
Re: [Mageia-dev] [changelog] [RPM] cauldron core/release kwallet-4.9.2-1.mga3
15.10.2012 21:46, Guillaume Rousse kirjutas: Le 15/10/2012 19:07, Malo a écrit : On 15/10/12 17:34, Balcaen John wrote: Le lundi 15 octobre 2012 15:48:46 Marek Laane a écrit : [...] Again, is Networking/Remote access right group for Kwallet? Do you have a better group for this ? Security I expected 'security' group to contain actual security-tools, such as vuln scanners, not desktop components as kwallet or gnome-keyring. Why not just 'Graphical desktop/KDE'? It's pretty much integrated into KDE and requires a lot of KDE packages. -- Sander
Re: [Mageia-dev] Firefox 16 - security issue - withdrawn
11.10.2012 13:58, Barry Jackson kirjutas: http://www.bbc.co.uk/news/technology-19909106 Maybe we should revert in Cauldron? Well, it's cauldron and the bug will be fixed before we get it reverted. We just have to wait a day or two. 16.0.1 candidate is already uploaded, so the bug is probably already fixed.. -- Sander
Re: [Mageia-dev] Firefox 16 - security issue - withdrawn
11.10.2012 18:32, Barry Jackson kirjutas: On 11/10/12 12:29, Sander Lepik wrote: 11.10.2012 13:58, Barry Jackson kirjutas: http://www.bbc.co.uk/news/technology-19909106 Maybe we should revert in Cauldron? Well, it's cauldron and the bug will be fixed before we get it reverted. We just have to wait a day or two. 16.0.1 candidate is already uploaded, so the bug is probably already fixed.. -- Sander True - however since I use Cauldron 24/7 I have reverted to 15.0.1 and added it to skip.list for my own peace of mind ;) Barry So, instead of 1 security hole you now have 14 (most of them critical :http://www.mozilla.org/security/known-vulnerabilities/firefox.html#firefox16)? ;P Not sure if it's safer or not :) -- Sander
Re: [Mageia-dev] rehashing the faac issue
03.10.2012 17:07, Guillaume Rousse kirjutas: Which means using 'nonfree' repository instead of 'tainted'... OK, let's vote here: - how many people for using 'tainted' ? - how many people for using 'non-free' ? Any solution involving technical changes doesn't qualify for a simple solution, and doesn't seems worth the effort for just a single package... Well, you can't list 'non-free' as an option here as faac contains content that belongs to tainted repo. If you land it there we will cause problems for some mirrors and that is a no-go option. If you want to vote then we can vote between those options: - land it in 'tainted' - it remains excluded My vote goes to tainted. Yes, non-free and free packages will be mixed but most users would vote for including it. Free software lovers can just avoid it. They should be better informed than normal user anyway. -- Sander
Re: [Mageia-dev] [changelog] [RPM] cauldron core/release task-obsolete-3-27.mga3
25.09.2012 01:17, blino kirjutas: Name: task-obsoleteRelocations: (not relocatable) Version : 3 Vendor: Mageia.Org Release : 27.mga3 Build Date: Tue Sep 25 00:12:29 2012 blino blino 3-27.mga3: + Revision: 297306 - obsolete policykit, replaced by polkit - obsolete hal and hal-info, replaced by udisks and later by udisks2 I would question obsoleting hal here. Is there a serious reason to do that? What if there are 3rd party packages that still need it? Or isn't it working at all on mga3? If it still works i wouldn't obsolete it that way. -- Sander
Re: [Mageia-dev] [changelog] [RPM] cauldron core/release task-obsolete-3-27.mga3
25.09.2012 13:03, Olivier Blin kirjutas: Do you have any example of such thirdparty software using it? No. But draksnapshot was a good example for quite sometime. If there are no packages that require it and it is removed from mga3 repos then i see no reason to add it as obsolete and stop those using it who need it for some reason. To me it seems like overusing task-obsolete. But don't get me wrong, i want it to be dead :) -- Sander
Re: [Mageia-dev] ANNOUNCE: The /usr move cometh! ---- Instructions
25.09.2012 13:07, Thierry Vignaud kirjutas: On 9 September 2012 20:42, Colin Guthrie mag...@colin.guthr.ie wrote: Those cannot be done anymore. Now updating rpm in order to be able to sole the unifiedsystemdir depends pulls filesystem... Classic egg chicken issue... Yes, this has been a problem for a while now in Cauldron. But not many users are asking this question these days, so the likely path now is from mga2 - cauldron which is probably where the effort should be focused. BTW I tested live upgrade from FC17 to FC18. It works smoothly if you don't have third party packages. in FC there's no need for a special boot, everything is hanled by filesystem package's pre/post scripts: Hmm, /usr move in Fedora is already done: http://fedoraproject.org/wiki/Upgrading_Fedora_using_yum#Fedora_16_-.3E_Fedora_17 I don't see what problems you could have during upgrade from f17 to f18. Try a live upgrade from f16 to f17 w/o those steps ;) -- Sander
Re: [Mageia-dev] lib64usb1.0_0-1.0.13-1.mga3 conflict
22.09.2012 13:09, Barry Jackson kirjutas: Since update of libusb: Installation failed: file /usr/lib64/libusb-1.0.so.0.1.0 from install of lib64usb1.0_0-1.0.13-1.mga3.x86_64 conflicts with file from package lib64usbx1.0_0-1.0.12-1.mga3.x86_64 Hey, this is cauldron problem that was caused by my stupid mistake. I'm not 100% sure here, but --replacefiles should do the work. I didn't test tho'.. -- Sander
Re: [Mageia-dev] Mageia 3 final set of isos
19.09.2012 10:40, Anne Nicolas kirjutas: Hi there So here is the discussion about what isos we should keep or have for final release. We had several (many!) proposals on that topics and we need to take some decisions. Here are some prerequisites I can see for what I can read in comments and review about Mageia on the web. - provide a full open source software version - provide CD iso(s) so that it can be quick to download (people having low band-width or paying depending how much they use it) - provide live version(s) - decrease isos number. QA is just a hell on the set we had for Mageia 2 - provide localization as large as possible - provide isos including major drivers including proprietary one to make it easier to install and configure Keep in mind that what you want is not necessarily what another one want. So let start proposals here and discussion. Please add all explanations to your proposal. Let say we take one week on this so until 26/09 then we will make a final proposal Cheers My proposal: dual and DVDs - as they are today. 32-bit LiveCD-s as they are today. Replace 64-bit LiveCDs with two LiveDVDs (KDE and GNOME versions) which contain all languages. I think 32-bit LiveCDs are still needed as they will be used by those users who don't have computer that can read DVDs and when the CD is in english it will be really hard for them localize their system after installing. -- Sander
Re: [Mageia-dev] halt and shutdown users: Still needed?
16.09.2012 19:13, rihowa...@gmail.com kirjutas: On Sep 9, 2012, at 3:10 AM, Julien wrote: Le Sun, 09 Sep 2012 12:55:17 +0300, Sander Lepik sander.le...@eesti.ee a écrit : 08.09.2012 19:49, Colin Guthrie kirjutas: Hi, So there exists two users (provided by default from the setup pkg) called halt and shutdown. These users just run the halt and shutdown commands as their shell. This means su'ing or sudo'ing or setting a password and logging in as them, will shut the machine down. This seems like a relic from many years ago and there is no need to include such users in this day and age. Should we kill them off? Col +1 on removing them. I didn't even know about them :) -- Sander The same for me, didn't know they existed. Julien - 1 Removing them is a really bad idea. It violates fundamental security principles. There is a reason processes are run with their user permissions. Hmm, i'm not sure you know what you are talking about. Can you show me where in the code are we doing that? -- Sander
Re: [Mageia-dev] /run vs /var/run in configuration files
11.09.2012 12:53, Guillaume Rousse kirjutas: Hello list. Since /usrmove, /run and /var/run is actually the same location on the final running system. So, either can be used in actual configuration files, and systemd unit files. But for consistency and comparaison purpose, it would be better to enforce usage of one variant only. I initially started to use /run in a few packages, however I'm considering reverting this practice for multiple reasons: - fedora keep using /var/run, which makes comparaison harder - it make backporting more difficult - similar /lib vs /usr/lib case exist, and our %_unitdir macro, for instance, uses the second form Any other thought on this topic ? I think we should convert to /run where possible. Else i don't see much point in usrmove. Backporting - don't think it will happen any time soon. -- Sander
Re: [Mageia-dev] /run vs /var/run in configuration files
11.09.2012 13:15, Guillaume Rousse kirjutas: [...] The /run - /var/run merge (/usrmove) is supposed to make the change transparent for applications. Manually converting applications to explicitely refers to the new location doesn't change its usefulness. Well, if your system can't mount /var for some reason then keeping things on /run might make recovery easier. -- Sander
Re: [Mageia-dev] [RFC] x11-server-1.13
08.09.2012 14:02, Thierry Vignaud kirjutas: - major driver that need being tested: o video: fglrx intel nouveau o input: synaptics Nouveau tested on GTS 250 (x86_64) seems to work like before. -- Sander
Re: [Mageia-dev] [changelog] [RPM] cauldron core/release kde-base-artwork-4.9.1-1.mga3
08.09.2012 18:33, Thierry Vignaud kirjutas: On 8 September 2012 17:22, mikala buildsystem-dae...@mageia.org wrote: mikala mikala 4.9.1-1.mga3: + Revision: 289658 - Update tarball to 4.9.1 - Fix folder path - Remove epoch Which means breaking upgrades This package has been imported 2 days ago, so at most some upgrade problems in cauldron but that's all. Tho' as there was also line - imported package kde-base-artwork i don't think it was even submitted into BS yet. -- Sander
Re: [Mageia-dev] [changelog] [RPM] cauldron nonfree/updates_testing x11-driver-video-nouveau-1.0.1-4.mga3.nonfree
07.09.2012 21:55, tv kirjutas: Name: x11-driver-video-nouveau Relocations: (not relocatable) Version : 1.0.1 Vendor: Mageia.Org Release : 4.mga3.nonfreeBuild Date: Fri Sep 7 20:54:01 2012 Install Date: (not installed) Build Host: jonund.mageia.org Group : System/X11Source RPM: (none) Size: 522922 License: MIT Signature : (none) Packager: tv tv URL : http://nouveau.freedesktop.org/ Summary : Accelerated open source driver for NVIDIA cards Description : The nouveau project aims to build high-quality, open source drivers for NVIDIA cards. tv tv 1.0.1-4.mga3: + Revision: 288995 - rebuild for new xserver - rebuild for new xserver Nonfree? (Also many others that i wouldn't call nonfree) -- Sander
Re: [Mageia-dev] Package removal proposal
Sander 26.08.2012 17:15, Colin Guthrie kirjutas: 'Twas brillig, and Johnny A. Solbu at 25/08/12 02:42 did gyre and gimble: On Saturday 25 August 2012 02:33, Olivier Thauvin wrote: For me obsolete should be reserved for replacements or rename, nothing more. I agree on this. So in two years time, we add a new package with the same filename as one of these old package, we may get some very strange edge cases on package upgrades/installer because keeping these old, no longer shipped packages installed is still supported (of course this could happen even if the old package were obsoleted properly, due to package install order on upgrades) What about when there are security issues in the old package? Do we just drop it and then wash our hands of the whole affair and don't give a crap when a user's system is completely compromised? In my opinion we should run a tight ship. If users want to use something we no longer ship, then they still have several choices: 1. Don't install task-obsolete and add it to their skip.list. 2. Do a local compile+install into /usr/local of the software in question 3. Package it and become a contributor (assuming the reason for dropping the package was due to a lack of maintainer rather than a specific desire/reason (i.e. legal)) For all of these options the user is both informed and can make a very clear, concious choice about how they want to proceed and know the consequences of doing so. Obsoletes in packages which genuinely replace the old one seem reasonable and uncontroversial. Col What about new feature. Some txt file (containing obsoleted package per line and probably can be signed somehow) in the mirrors that can be updated by sysadmins. During update urpmi will check this file and will compare with local file where user has marked what (s)he wants to do with those packages (obsoleted package status: keep/remove per line). If urpmi finds package that hasn't been listed in local file it will ask the user what to do with it + will show warning that all possible security problems are not our problem anymore.
Re: [Mageia-dev] Tonight's meeting
On Aug 22, 2012 5:52 PM, Anne Nicolas enna...@gmail.com wrote: Hi there We will have a meeting tonight as usual at 19h UTC. Here are the proposed topics: - Coming Mageia 3 alpha 1 release - kernel support for Mageia 2 - mentoring review + siplew account As usual feel free to add another one I would add all the open questions that are holding back mass rebuild. :) -- Sander
Re: [Mageia-dev] The life After usrMove - KDE failure
16.08.2012 16:48, Johnny A. Solbu kirjutas: On Wednesday 15 August 2012 12:54, Colin Guthrie wrote: I wouldn't necessarily jump to the conclusion that this is *caused* by the usrmove. I never said it did, nor did I imply it. I said it happened as a result of upgrading packages, /after/ the usrmove. There is a difference. ;-)= Your title pretty much sounds like usrmove is to blame :P -- Sander
Re: [Mageia-dev] [changelog] [RPM] cauldron core/release gdb-7.4.91.20120801-1.mga3
14.08.2012 01:43, tv kirjutas: Name: gdb Relocations: (not relocatable) [...] tv tv 7.4.91.20120801-1.mga3: + Revision: 281165 - new release - sync patches with FC What is that FC? ;P Are you living in the past or is this something new i don't know yet? :) -- Sander
Re: [Mageia-dev] urpmi segfaults on the build system (was Re: Our BS is about to eat packages?)
11.08.2012 13:33, Olivier Blin kirjutas: pterjan fixed some of them, fixes are now in perl-URPM 4.12. It should help preventing build loops in the BS. Thank you! \o/ -- Sander
[Mageia-dev] Mass rebuild?
Alpha 1 is getting closer and closer but still no rebuild. AFAIK we should have all major packages in for now. So what is stopping mass rebuild? :) Even if there won't be any mass rebuild before alpha 1, can maintainers please check their packages from this list: http://check.mageia.org/cauldron/dependencies.html - some may need just a rebuild. -- Sander
Re: [Mageia-dev] [changelog] [RPM] cauldron core/release kdelibs4-4.9.0-2.mga3
01.08.2012 11:19, Anne Nicolas kirjutas: Please try to work properly ie asking maintainer before. It takes a mail to do it and save lot of work for everybody. This should be applied especially by new comers and mentors. If not we will have to write some strict rules down which is, imho, too restrictive while common sense should be enough to avoid such situation. Rondolf, please, try to follow this. Cheers What about wiki page where maintainers can state what they allow on their packages w/o asking? Like Updating minor versions is OK, Always ask before you touch, Do whatever you like, etc. So other packagers can check and don't have to wait for response. Of course maintainer can add exceptions too. WDYT? -- Sander
Re: [Mageia-dev] [changelog] [RPM] cauldron core/release kdelibs4-4.9.0-2.mga3
01.08.2012 13:00, Shlomi Fish kirjutas: BTW, you should not call me Rindolf outside IRC. My name is Shlomi. Yet another wiki page i would like to see. Place where brave people could list their email, irc nick + real name. As it's sometimes very hard to find out who is really behind the svn username :/ Of course everybody would have to list themselves as we don't disclose such info by default but if there would be such a list i would be in it.. -- Sander
Re: [Mageia-dev] [changelog] [RPM] cauldron core/release kmplot-4.9.0-1.mga3
01.08.2012 18:39, neoclust kirjutas: Name: kmplot Relocations: (not relocatable) Version : 4.9.0 Vendor: Mageia.Org Release : 1.mga3Build Date: Wed Aug 1 17:34:45 2012 [...] mikala mikala 4.9.0-1.mga3: + Revision: 277048 - Silent: Fix Source URL Hmm, I think SILENT should be used :) -- Sander
Re: [Mageia-dev] [changelog] [RPM] cauldron core/release kmplot-4.9.0-1.mga3
01.08.2012 18:45, Nicolas Lécureuil kirjutas: Le mercredi 1 août 2012 18:42:18 Sander Lepik a écrit : Hmm, I think SILENT should be used :) -- Sander or maybe silent SILENT SiLeNt SIlent, ... should be understood by the BS :) This might kill some needed comments. Or not? -- Sander
Re: [Mageia-dev] ANNOUNCE: The /usr move cometh! ---- Instructions
24.07.2012 02:32, Barry Jackson kirjutas: Updating an i586 Cauldron VM I am getting this:- Preparing... # 1/52: filesystem # error: unpacking of archive failed on file /var/run: cpio: rename failed - Is a directory error: filesystem-2.1.9-18.mga3.i586: install failed This is at the start of --auto-update after the re-boot. Is your /var on a separate partition? I had the same problem with /var/lock and /var/run. To solve this i had to rename those directories (later deleted them) and i created two symlinks /var/lock - /run/lock and /var/run - /run - after that filesystem installed w/o problems. -- Sander
Re: [Mageia-dev] ANNOUNCE: The /usr move cometh! ---- Instructions
23.07.2012 22:08, Olivier Blin kirjutas: I have updated the command in the wiki to be: urpmi --auto-update --skip '/filesystem|ncurses/' (as I have pointed earlier in this thread) This will install a lot more packages (including kernel), before the /usr move. Hmm, which initrd is dracut -f rebuilding? Current running one or latest? If it's rebuilding current one then i would add kernel into the skip list, else users are probably rebuilding wrong initrd and conversion won't work if they start with new kernel. -- Sander
