Re: [Mageia-dev] freeze push: Libreoffice
D.Morgan skrev 10.1.2013 09:28: Hi, please push Libreoffice, i have enabled system cpp instead of ucpp to try to fix build. submitted. -- Thomas
Re: [Mageia-dev] rpmrc [5221] build with -fPIC on x86_64 too (pok, mdv)
On 10/01/13 02:54, Anssi Hannula wrote: I have to strongly disagree with this. - This hides problems in build scripts. Shared libraries should normally be linked with -fPIC on *all* architectures. Not doing this causes some issues, like the library to actually become unshareable across different processes. Since these are allowed in iX86 but not on x86_64, building all objects on x86_64 with -fPIC will hide any missing -fPIC from build script issues. Note that there can't be very many problematic failing packages, since we and mdv have managed this far without it. - It is not needed except on shared libraries, and will cause a small performance penalty (due to one less register being available when using relative addressing). (AFAIU it is negligible, but still..) +1 That's killing flies with a steamroller.
[Mageia-dev] ANN: kernel-3.8-rc3 landing in Cauldron...
Hi, this is a heads-up that I'm about to push kernel-3.8-rc3 to Cauldron. As we will use 3.8 as release kernel, we better start testing it right now and adapt everything needed for it ... You have been warned :) -- Thomas
Re: [Mageia-dev] Freeze push: lcov
On Thu, 10 Jan 2013, Kamil Rytarowski wrote: Hello, lcov 1.9 isn't working with the current GCC, upgrade to 1.10 fixes it. Fedora uses a patch against 1.9 [1], not needed anymore with the current version. Please push this package. Submitted.
Re: [Mageia-dev] Version freeze
On Thu, 10 Jan 2013, nicolas vigier wrote: Hello, The version freeze is now active on Cauldron, and focus is now on fixing bugs. You can still submit new packages, or new release of packages, but cannot change the version of existing packages. If you need an exception to the version freeze, send an email to the mailing list with subject Freeze push: packagename and explain the reasons why an exception is needed, and any information that can help decide quickly about the freeze exception (changelog since previous version, whether it's a bugfix only release, whether a lot of things depend on this package, etc ...). And the list of people who can submit push requests : boklm, ennael, guillomovitch, tmb
Re: [Mageia-dev] Kernel Panic after latest Mageia-3-Alpha2 s/w update c
On Wed, 09 Jan 2013 14:35:41 -0500, Frank Griffin wrote: If this was a previous kernel installed on this partition, then your menu.lst should already have a version-specific entry for it. The thougjht did occur to me also, but the one I tried also gave kernel panic. Perhaps I should have tried others. -- /\/\aurice
Re: [Mageia-dev] Regression testing for generated RPM
Thanks Guillame. I wasn't aware of this and did not manage to find that in the wiki. I thought the only tests performed where RPM lint checks, manual checks by the QA and some undefined checks by the maintainers. Anyhow, I assume the 'make test' is performed on the build server. Your experiences might prove me wrong, but wouldn't it be better to perform tests on a different installation? 2013/1/4 Guillaume Rousse guillomovi...@gmail.com Le 04/01/2013 10:15, Jochen Breuer a écrit : 2013/1/4 Guillaume Rousse guillomovi...@gmail.com mailto:guillomovitch@gmail.**com guillomovi...@gmail.com We already run existing tests suite during package build... Running them again on a different host would just change the execution environment to use runtime dependencies instead of build time dependencies. I don't know if the potential results are worth the additional infrastructure needed. I was under the impression, that only some kind of lint checking of the RPM was performed. I'm talking about checking the functionality of the packaged software. Are you already doing that? What kind of tests are performed during packaging? Running 'make check', or 'make test', or any other software test suite. Just check for %check section in package spec file, for instance: http://svnweb.mageia.org/**packages/cauldron/python/** current/SPECS/python.spec?**revision=278990view=markuphttp://svnweb.mageia.org/packages/cauldron/python/current/SPECS/python.spec?revision=278990view=markup -- BOFH excuse #66: bit bucket overflow
Re: [Mageia-dev] Kernel Panic after latest Mageia-3-Alpha2 s/w update c
On Wed, 09 Jan 2013 21:40:25 +0100, eatdirt wrote: Check for typos in the names. For instance you have one above: 3-7-0 instead of 3.7.0. I was careful, but will check again. (The typo may Have been when transcribing into posting to newsgroup on different m/c.) -- /\/\aurice
Re: [Mageia-dev] Freeze push
On Wednesday, January 09, 2013 08:28:36 PM Thomas Spuhler wrote: Please push ghostpcl-9.06 9.05 doesn't build. Ping -- Best regards Thomas Spuhler signature.asc Description: This is a digitally signed message part.
Re: [Mageia-dev] Kernel Panic after latest Mageia-3-Alpha2 s/w update c
On Wed, 09 Jan 2013 19:26:04 +, Dick Gevers wrote: If you change menu.lst, you also have to execute /boot/grub/install.sh, else it does not have any effect. My understanding of that aspect of GRUB2 is that one *can* change menu.lst, but if the GRUB2 'config' file is not given the same change then that change will be lost the next time install.sh is executed. But - hold on - Mageia-3 is not into GRUB2 yet, is it? (The last I heard GRUB2 was going to be an *option* during installation of Mageia-3 Final.) I still have Mageia-3-Alpha2's GRUB in the MBR, and can still boot Mageia-2 from its menu.lst (which I appended earier). -- /\/\aurice
Re: [Mageia-dev] /usr/bin/file broken on cauldron
On Thu, Jan 10, 2013 at 12:56 AM, Olivier Blin mag...@blino.org wrote: Luc Menut lme...@free.fr writes: It's better, but file-5.12-5 still mis-detects some script files; I can see that some Perl or shell scripts are reported as 'assembler source text' with 5.12-5. [...] /usr/bin/automake: assembler source text /usr/bin/iurt: assembler source text It's very annoying because /usr/bin/file is used by find-requires and [...] find-provides, and if we do the mass rebuild with a broken /usr/bin/file, we will build some rpms with incorrect provides and requires. Hi again, This might be this one: http://mx.gw.com/pipermail/file/2013/001026.html Which is claimed to be fixed by the maintainer: http://mx.gw.com/pipermail/file/2013/001040.html Can you try with upstream git? https://github.com/glensc/file/commits/master This is fixed in git but I couldn't find the specific commit
Re: [Mageia-dev] Regression testing for generated RPM
Le 10/01/2013 14:18, Jochen Breuer a écrit : Thanks Guillame. I wasn't aware of this and did not manage to find that in the wiki. I thought the only tests performed where RPM lint checks, manual checks by the QA and some undefined checks by the maintainers. Anyhow, I assume the 'make test' is performed on the build server. Your experiences might prove me wrong, but wouldn't it be better to perform tests on a different installation? Probably, indeed, because the environment would be closer to an actual usage environment. But this is hardly measurable. And you have to balance the added value of those additional tests with the manpower needed to setup a new test infrastructure, integrate it with current build system, and maintain it... I heard the sysadmin team was looking for volonteers, if you're interested :P -- BOFH excuse #174: Backbone adjustment
Re: [Mageia-dev] /usr/bin/file broken on cauldron
On Thu, Jan 10, 2013 at 3:51 PM, Pascal Terjan pter...@gmail.com wrote: On Thu, Jan 10, 2013 at 12:56 AM, Olivier Blin mag...@blino.org wrote: Luc Menut lme...@free.fr writes: It's better, but file-5.12-5 still mis-detects some script files; I can see that some Perl or shell scripts are reported as 'assembler source text' with 5.12-5. [...] /usr/bin/automake: assembler source text /usr/bin/iurt: assembler source text It's very annoying because /usr/bin/file is used by find-requires and [...] find-provides, and if we do the mass rebuild with a broken /usr/bin/file, we will build some rpms with incorrect provides and requires. Hi again, This might be this one: http://mx.gw.com/pipermail/file/2013/001026.html Which is claimed to be fixed by the maintainer: http://mx.gw.com/pipermail/file/2013/001040.html Can you try with upstream git? https://github.com/glensc/file/commits/master This is fixed in git but I couldn't find the specific commit The fix is https://github.com/glensc/file/commit/834831f53398cf2a1cfcd1daaf88c437bbf8d21f
Re: [Mageia-dev] Kernel Panic after latest Mageia-3-Alpha2 s/w update c
On Wed, 09 Jan 2013 19:13:14 +, I wrote: (replaced:) initrd /boot/initrd.imgwith initrd /boot/initrd-3-7-0-desktop-1-mga3.img There were 2 errors there: (1) -mga3 should have been .mga3 (2) .img should have been .img.old (I first tried with the .old affix, but wrongly assumed that it hung because of the .old.) So, Mga3-A2 now boots again! Many thanks to all for your help. Much appreciated. -- /\/\aurice
Re: [Mageia-dev] Kernel Panic after latest Mageia-3-Alpha2 s/w update c
On Wed, 09 Jan 2013 14:35:41 -0500, Frank Griffin wrote: your menu.lst should already have a version-specific entry for it. Try booting that directly without modifying anything. I've now tried all the 'mga3' stanzas (3.6.5-1, 3.7.0-1, 3.7.1-1), and they all gave Kernel Panic. -- /\/\aurice
Re: [Mageia-dev] /usr/bin/file broken on cauldron
Pascal Terjan pterjan@... writes: On Thu, Jan 10, 2013 at 3:51 PM, Pascal Terjan pterjan@... wrote: This is fixed in git but I couldn't find the specific commit The fix is https://github.com/glensc/file/commit/834831f53398cf2a1cfcd1daaf88c437bbf8d21f Fixed in file-5.12-6.mga3, but this is a bit more interesting... If you actually look at that commit, you see: -# $File: assembler,v 1.1 2011/12/08 12:12:46 rrt Exp $ +# $File: assembler,v 1.2 2012/10/31 18:41:42 christos Exp $ But the file in the tarball already reflects the v 1.2 christos (who is the one who made this commit), while the rest of the contents of that file reflect the previous version, aka the rest of that commit isn't applied in the tarball. Anyway, I verified that fixing this fixes the detection for /usr/bin/automake.
Re: [Mageia-dev] Kernel Panic after latest Mageia-3-Alpha2 s/w update c
On Wed, 09 Jan 2013 14:35:41 -0500, Frank Griffin wrote: bug 8614 for all this was just fixed. It says: Fixed with: glibc-2.17-2.mga3 and util-linux-2.22.2-2.mga3 but in my (newly-recovered from Kernel Panic) Mga3-A2, MCC/SW/Update shows the following packages available: glib v2.17 glibc-devel v2.17 meta-task v3 The $64 questions are: (1) Do I need to install them now, and - if so - does anything need to be done with them immediately? (2) Any reason why I should not go ahead with any further s/w updates?! -- /\/\aurice
Re: [Mageia-dev] freeze push: Libreoffice
On 10 January 2013 08:28, D.Morgan dmorga...@gmail.com wrote: please push Libreoffice, i have enabled system cpp instead of ucpp to try to fix build. if you'd look at SVN history, you'd seen that both ways already were tried git svn clone svn+ssh://svn.mageia.org/svn/packages/cauldron/libreoffice/current/
[Mageia-dev] freeze-push: ocaml-pgocaml
Currently we have version 1.7. Today was released a bug-fix-only release 1.7.1. Please push it. -- Malo
Re: [Mageia-dev] freeze-push: ocaml-pgocaml
On Thu, 10 Jan 2013, Pierre-Malo Deniélou wrote: Currently we have version 1.7. Today was released a bug-fix-only release 1.7.1. Submitted.
Re: [Mageia-dev] Freeze push
On Wed, 09 Jan 2013, Thomas Spuhler wrote: Please push ghostpcl-9.06 9.05 doesn't build. build was successful on 2013-01-02 : http://pkgsubmit.mageia.org/autobuild/results.php?run=2013-01-02 failed on 2013-01-04 : http://pkgsubmit.mageia.org/autobuild/results.php?run=2013-01-04 This looks like a problem of parallel make, and can maybe be fixed by using make instead of %make.
Re: [Mageia-dev] /usr/bin/file broken on cauldron
Op donderdag 10 januari 2013 17:20:04 schreef David Walser: Pascal Terjan pterjan@... writes: On Thu, Jan 10, 2013 at 3:51 PM, Pascal Terjan pterjan@... wrote: This is fixed in git but I couldn't find the specific commit The fix is https://github.com/glensc/file/commit/834831f53398cf2a1cfcd1daaf88c437bbf8d2 1f Fixed in file-5.12-6.mga3, but this is a bit more interesting... If you actually look at that commit, you see: -# $File: assembler,v 1.1 2011/12/08 12:12:46 rrt Exp $ +# $File: assembler,v 1.2 2012/10/31 18:41:42 christos Exp $ But the file in the tarball already reflects the v 1.2 christos (who is the one who made this commit), while the rest of the contents of that file reflect the previous version, aka the rest of that commit isn't applied in the tarball. Anyway, I verified that fixing this fixes the detection for /usr/bin/automake. that's bad practice
[Mageia-dev] Freeze push: gnome-color-manager 3.6.1
This is a bugfix release. -- Regards, Olav ---BeginMessage--- About GNOME Color Manager = GNOME Color Manager is a set of graphical utilities for color management to be used in the GNOME desktop. News Released: 2013-01-10 * Translations - Added Bengali India translation (Sayak Sarkar) - Added Slovak translation (Roman Mátyus) - Updated Bulgarian translation (Alexander Shopov) - Updated Bulgarian translation (Ivaylo Valkov) - Updated Catalan translation (Gil Forcada) - Updated Catalan (Valencian) translation (Carles Ferrando) - Updated gujarati file (Sweta Kothari) - Updated kn translation (Shankar Prasad) - Updated Latvian translation (Rūdolfs Mazurs) - Updated Norwegian bokmål translation (Kjartan Maraas) - Updated Odia translation (ManojKumar Giri) - Updated Slovak translation (Pavol Klačanský) - Updated Telugu translations (Krishnababu Krothapalli) - Updated Uyghur translation (Gheyret Kenji) * Bugfix: - Better initial orientation for the Lab hull (Pascal de Bruijn) - Calculate the profile whitepoint using the profile transform (Richard Hughes) - Default to normal calibration (Pascal de Bruijn) - Detect Ubuntu casper based livecd's as well (Pascal de Bruijn) - For dispread skip instrument recalibration for the ColorMunki (Pascal de Bruijn) - For the ColorMunki use high resolution measurement mode (Pascal de Bruijn) - Get the ICC profile pre-cooked MD5 value if it is available (Richard Hughes) - Honour precision for dispcal (Pascal de Bruijn) - Large default window size, to prevent mid operation automatic resizing (Pascal de Bruijn) - Move gcm-calibrate to lower right of the screen (Pascal de Bruijn) - Show temperature page for more devices (Pascal de Bruijn) - Use a 0.8 instead of 1.2 sized test window for Argyll (Pascal de Bruijn) ChangeLog = http://download.gnome.org/sources/gnome-color-manager/3.6/gnome-color-manager-3.6.1.changes (6.54K) Download http://download.gnome.org/sources/gnome-color-manager/3.6/gnome-color-manager-3.6.1.tar.xz (2.48M) sha256sum: c5fb0903d5570c50fbb2347db314bef0c57b293302e48e0b73f57f426fb7 ___ ftp-release-list mailing list ftp-release-l...@gnome.org https://mail.gnome.org/mailman/listinfo/ftp-release-list---End Message---
Re: [Mageia-dev] Kernel Panic after latest Mageia-3-Alpha2 s/w update c
Maurice Batey maur...@bcs.org.uk writes: On Wed, 09 Jan 2013 14:35:41 -0500, Frank Griffin wrote: bug 8614 for all this was just fixed. It says: Fixed with: glibc-2.17-2.mga3 and util-linux-2.22.2-2.mga3 but in my (newly-recovered from Kernel Panic) Mga3-A2, MCC/SW/Update shows the following packages available: glib v2.17 glibc-devel v2.17 meta-task v3 You might need to run this command to update initrds: bootloader-config --action rebuild-initrds -- Olivier Blin - blino
Re: [Mageia-dev] /usr/bin/file broken on cauldron
Le 10/01/2013 18:20, David Walser a écrit : Pascal Terjanpterjan@... writes: On Thu, Jan 10, 2013 at 3:51 PM, Pascal Terjanpterjan@... wrote: This is fixed in git but I couldn't find the specific commit The fix is https://github.com/glensc/file/commit/834831f53398cf2a1cfcd1daaf88c437bbf8d21f Fixed in file-5.12-6.mga3, but this is a bit more interesting... If you actually look at that commit, you see: -# $File: assembler,v 1.1 2011/12/08 12:12:46 rrt Exp $ +# $File: assembler,v 1.2 2012/10/31 18:41:42 christos Exp $ But the file in the tarball already reflects the v 1.2 christos (who is the one who made this commit), while the rest of the contents of that file reflect the previous version, aka the rest of that commit isn't applied in the tarball. Anyway, I verified that fixing this fixes the detection for /usr/bin/automake. Thanks to all for the fix. I confirm that file-5.12-6 fixes the problem. After some quick tries, it seems that file 5.12 gives now the same results as file 5.11. regards, Luc -- Luc Menut
Re: [Mageia-dev] Kernel Panic after latest Mageia-3-Alpha2 s/w update c
On 01/10/2013 03:26 PM, Olivier Blin wrote: You might need to run this command to update initrds: bootloader-config --action rebuild-initrds Or just update to current cauldron, which includes the 3.8 kernel, the installation of which will rebuild the initrd.
Re: [Mageia-dev] ANN: kernel-3.8-rc3 landing in Cauldron...
On Thu, 10 Jan 2013 12:27:01 +0200 Thomas Backlund wrote: You have been warned :) Are you envisioning the apocalypse ;) Booted without issues here. Nvidia driver works and everything appears to be performing normally. Charles -- Do not count your chickens before they are hatched. -- Aesop -- Mageia release 3 (Cauldron) for x86_64$ On SuperSizehttp://www.eslrahc.com Registered Linux user #182463 3.8.0-server-0.rc3.1.mga3 x86_64 -- signature.asc Description: PGP signature
Re: [Mageia-dev] ANN: kernel-3.8-rc3 landing in Cauldron...
On 10/01/13 22:56, Charles A Edwards wrote: On Thu, 10 Jan 2013 12:27:01 +0200 Thomas Backlund wrote: Booted without issues here. Nvidia driver works and everything appears to be performing normally. Well, it does not build dkms-nvidia-current for me! But the nouveau driver automatically came as a rescue without trouble. /var/lib/dkms/nvidia/current-310.19-1.mga3.nonfree/build/nv.c: In function ‘nvidia_init_module’: /var/lib/dkms/nvidia/current-310.19-1.mga3.nonfree/build/nv.c:873:5: error: implicit declaration of function ‘NV_KMEM_CACHE_CREATE’ [-Werror=i mplicit-function-declaration] /var/lib/dkms/nvidia/current-310.19-1.mga3.nonfree/build/nv.c:873:58: error: expected expression before ‘nv_stack_t’ /var/lib/dkms/nvidia/current-310.19-1.mga3.nonfree/build/nv.c:883:9: error: implicit declaration of function ‘NV_KMEM_CACHE_DESTROY’ [-Werror= implicit-function-declaration] /var/lib/dkms/nvidia/current-310.19-1.mga3.nonfree/build/nv.c:981:54: error: expected expression before ‘nv_pte_t’ /var/lib/dkms/nvidia/current-310.19-1.mga3.nonfree/build/nv.c:990:13: error: expected expression before ‘nvidia_p2p_page_t’ /var/lib/dkms/nvidia/current-310.19-1.mga3.nonfree/build/nv.c: In function ‘nv_kern_open’: /var/lib/dkms/nvidia/current-310.19-1.mga3.nonfree/build/nv.c:1521:30: warning: passing argument 2 of ‘request_irq’ from incompatible pointer type [enabled by default] In file included from /var/lib/dkms/nvidia/current-310.19-1.mga3.nonfree/build/nv-linux.h:128:0,
Re: [Mageia-dev] ANN: kernel-3.8-rc3 landing in Cauldron...
eatdirt skrev 11.1.2013 00:20: On 10/01/13 22:56, Charles A Edwards wrote: On Thu, 10 Jan 2013 12:27:01 +0200 Thomas Backlund wrote: Booted without issues here. Nvidia driver works and everything appears to be performing normally. Well, it does not build dkms-nvidia-current for me! But the nouveau driver automatically came as a rescue without trouble. you need the fixed 310.19-2.mga3 I have fixed all nvidia* and fglrx* drivers now so they all build with kernel-3.8, just wait for them to show up on the mirror you use... -- Thomas
Re: [Mageia-dev] /usr/bin/file broken on cauldron
Luc Menut lme...@free.fr writes: Thanks to all for the fix. I confirm that file-5.12-6 fixes the problem. After some quick tries, it seems that file 5.12 gives now the same results as file 5.11. Actually, there is one patch I reverted, thinking it was merged because patch detected it as reversed, but it was again because of a modified RCSID in the new 5.12 tarball. I'll add the patch back, this should fix file -i for ELF shared libraries and executables. -- Olivier Blin - blino
[Mageia-dev] libreoffice 4.0.0.0-0.beta2 : Missing signature
Hi, Trying to install libreoffice 4 beta 2, I have: The following packages have bad signatures: /var/cache/urpmi/rpms/libreoffice-calc-4.0.0.0-0.beta2.mga3.x86_64.rpm: Missing signature (OK ((none))) /var/cache/urpmi/rpms/libreoffice-core-4.0.0.0-0.beta2.mga3.x86_64.rpm: Missing signature (OK ((none))) /var/cache/urpmi/rpms/libreoffice-draw-4.0.0.0-0.beta2.mga3.x86_64.rpm: Missing signature (OK ((none))) /var/cache/urpmi/rpms/libreoffice-emailmerge-4.0.0.0-0.beta2.mga3.x86_64.rpm: Missing signature (OK ((none))) /var/cache/urpmi/rpms/libreoffice-graphicfilter-4.0.0.0-0.beta2.mga3.x86_64.rpm: Missing signature (OK ((none))) /var/cache/urpmi/rpms/libreoffice-impress-4.0.0.0-0.beta2.mga3.x86_64.rpm: Missing signature (OK ((none))) /var/cache/urpmi/rpms/libreoffice-kde-4.0.0.0-0.beta2.mga3.x86_64.rpm: Missing signature (OK ((none))) /var/cache/urpmi/rpms/libreoffice-langpack-fr-4.0.0.0-0.beta2.mga3.x86_64.rpm: Missing signature (OK ((none))) /var/cache/urpmi/rpms/libreoffice-math-4.0.0.0-0.beta2.mga3.x86_64.rpm: Missing signature (OK ((none))) /var/cache/urpmi/rpms/libreoffice-ogltrans-4.0.0.0-0.beta2.mga3.x86_64.rpm: Missing signature (OK ((none))) /var/cache/urpmi/rpms/libreoffice-opensymbol-fonts-4.0.0.0-0.beta2.mga3.noarch.rpm: Missing signature (OK ((none))) /var/cache/urpmi/rpms/libreoffice-pdfimport-4.0.0.0-0.beta2.mga3.x86_64.rpm: Missing signature (OK ((none))) /var/cache/urpmi/rpms/libreoffice-presentation-minimizer-4.0.0.0-0.beta2.mga3.x86_64.rpm: Missing signature (OK ((none))) /var/cache/urpmi/rpms/libreoffice-pyuno-4.0.0.0-0.beta2.mga3.x86_64.rpm: Missing signature (OK ((none))) /var/cache/urpmi/rpms/libreoffice-ure-4.0.0.0-0.beta2.mga3.x86_64.rpm: Missing signature (OK ((none))) /var/cache/urpmi/rpms/libreoffice-writer-4.0.0.0-0.beta2.mga3.x86_64.rpm: Missing signature (OK ((none))) /var/cache/urpmi/rpms/libreoffice-xsltfilter-4.0.0.0-0.beta2.mga3.x86_64.rpm: Missing signature (OK ((none))) Do you want to continue installation ? (y/N) regards, Luc -- Luc Menut
[Mageia-dev] Freeze push: sqlite3
Hello, Please push sqlite3 version 3.7.15.2, it's a patch release against our version 3.7.15.1. It's fixing an single bug introduced with 3.7.15.x. [1] Regards, [1] 2013-Jan-09 - Release 3.7.15.2 SQLite version 3.7.15.2 is a patch release that fixes a single bug that was introduced in version version 3.7.15. The fix is a 4-character edit to a single line of code. Other than this 4-character change and the update of the version number, nothing has changed from version 3.7.15.1. source: http://sqlite.org/news.html
Re: [Mageia-dev] Freeze push: gnome-color-manager 3.6.1
On Thu, 10 Jan 2013, Olav Vitters wrote: This is a bugfix release. Submitted.
Re: [Mageia-dev] Freeze push: firefox-beta
On Thu, 10 Jan 2013, Thierry Vignaud wrote: Hi Please let in firefox-beta. It build fine locally, it doesn' impact anything in the distro and nothing depends on this package, etc ...). Submitted.
Re: [Mageia-dev] Freeze push: sqlite3
On Fri, 11 Jan 2013, Kamil Rytarowski wrote: Hello, Please push sqlite3 version 3.7.15.2, it's a patch release against our version 3.7.15.1. It's fixing an single bug introduced with 3.7.15.x. [1] Submitted.
