[Mageia-dev] Pushing KDE 4.9.95
Hello, Sorry for the delay, but work is quite busy thoses days. Anyway i'm pushing today KDE 4.9.95 aka KDE 4.10 RC1 I did not test it against the new mesa because when i build initially cauldron was still using the old llvm. Hopefully everything should build smoothly. Regards, -- Mageia Contributor
[Mageia-dev] strange error on build host
This happens when building krb5: gcc -L../../lib -O2 -g -pipe -Wp,-D_FORTIFY_SOURCE=2 -fstack-protector --param=ssp-buffer-size=4 -fstack-protector-all -fomit-frame-pointer -march=i586 -mtune=generic -fasynchronous-unwind-tables -I/usr/include/et -fPIC -pie -Wl,-z,relro -Wl,-z,now -Wl,--as-needed -Wl,--no-undefined -Wl,-z,relro -Wl,-O1 -Wl,--build-id -Wl,--enable-new-dtags -o t_export_name t_export_name.o common.o -lgssapi_krb5 -lkrb5 -lk5crypto -lcom_err -lkrb5support -lresolv -ldl common.o: file not recognized: File truncated collect2: error: ld returned 1 exit status Is there any kind of file size limit ? -- BOFH excuse #436: Daemon escaped from pentagram
[Mageia-dev] how to update mageia rpmlint configuration on submission host ?
I can't suceed submitting metasploit, because of some rpmlint error: Submission errors, aborting: - metasploit-4.5-1.mga3: - unexpanded-macro /usr/share/metasploit/lib/gemcache/ruby/1.9.1/gems/railties-3.2.8/lib/rails/generators/rails/plugin_new/templates/lib/%name%/engine.rb %name I did update rpmlint-mageia-policy a week ago (0.2.25), but the configuration used on the host running the check seems to still use the previous version. Do we need an explicit actions from sysadmins here ? -- BOFH excuse #423: It's not RFC-822 compliant.
Re: [Mageia-dev] how to update mageia rpmlint configuration on submission host ?
Guillaume Rousse skrev 31.12.2012 16:24: I can't suceed submitting metasploit, because of some rpmlint error: Submission errors, aborting: - metasploit-4.5-1.mga3: - unexpanded-macro /usr/share/metasploit/lib/gemcache/ruby/1.9.1/gems/railties-3.2.8/lib/rails/generators/rails/plugin_new/templates/lib/%name%/engine.rb %name I did update rpmlint-mageia-policy a week ago (0.2.25), but the configuration used on the host running the check seems to still use the previous version. Do we need an explicit actions from sysadmins here ? Yep. I'll check it out tonight unless any other sysadmin beats me to it -- Thomas
Re: [Mageia-dev] strange error on build host
On Mon, Dec 31, 2012 at 2:06 PM, Guillaume Rousse guillomovi...@gmail.com wrote: This happens when building krb5: gcc -L../../lib -O2 -g -pipe -Wp,-D_FORTIFY_SOURCE=2 -fstack-protector --param=ssp-buffer-size=4 -fstack-protector-all -fomit-frame-pointer -march=i586 -mtune=generic -fasynchronous-unwind-tables -I/usr/include/et -fPIC -pie -Wl,-z,relro -Wl,-z,now -Wl,--as-needed -Wl,--no-undefined -Wl,-z,relro -Wl,-O1 -Wl,--build-id -Wl,--enable-new-dtags -o t_export_name t_export_name.o common.o -lgssapi_krb5 -lkrb5 -lk5crypto -lcom_err -lkrb5support -lresolv -ldl common.o: file not recognized: File truncated collect2: error: ld returned 1 exit status Is there any kind of file size limit ? It could be a disk full but I would rather think of some problem with parallel build and the file not being fully written at that time
Re: [Mageia-dev] how to update mageia rpmlint configuration on submission host ?
Thomas Backlund skrev 31.12.2012 17:09: Guillaume Rousse skrev 31.12.2012 16:24: I can't suceed submitting metasploit, because of some rpmlint error: Submission errors, aborting: - metasploit-4.5-1.mga3: - unexpanded-macro /usr/share/metasploit/lib/gemcache/ruby/1.9.1/gems/railties-3.2.8/lib/rails/generators/rails/plugin_new/templates/lib/%name%/engine.rb %name I did update rpmlint-mageia-policy a week ago (0.2.25), but the configuration used on the host running the check seems to still use the previous version. Do we need an explicit actions from sysadmins here ? Yep. I'll check it out tonight unless any other sysadmin beats me to it New rpmlint and policy now in place. Also -debuginfo packages should now be ok and the changes for /run, and checking for udev, systemd and tmpfiles location are now in effect -- Thomas
[Mageia-dev] DVD install feedback for mga3 beta 1
Hi there, I have just installed mga3 beta1 on a brand new machine for my folks and everything went fantastically fine in a first try. Congrats. So I decided to test other options and managed to end up in an infinite loop that hung the installer. There how to do it: 1) choose additional sources with http 2) accept the default mirror chosen (which was in Germany). Unfortunately that default mirror was very very slow 3) Many packages got downloaded from that mirror with an estimated time of 3-4 hours, so I clicked on Annuler (french install) 4) The installer went on with only the DVD package but ended up being frozen soon after. Playing with the CTRL+ALT+Fi, the do loop was due to pango packages already installed from the network before the annuler and more recent that the ones on the DVD. The log were incessantly showing: Chosen pano-1.32.4... for pango more recent pango-1.32.5... is installed but does not provide 1.32.4... Selecting pango 1.32.4... Unselecting pango 1.32.4... and the same message repeted forever Hope it helps! Cheers, Chris
Re: [Mageia-dev] acpid under systemd
On 12/31/2012 09:46 AM, Olav Vitters wrote: systemd starts daemons in a clean environment. I'm guessing some environment variables are missing. Most likely DISPLAY, maybe others. I see, although I tried to set up the DISPLAY variable without success :-/ Thanks, Chris.
Re: [Mageia-dev] [changelog] cauldron core/release iurt-0.6.16-1.mga3
pterjan skrev 31.12.2012 23:58: Name: iurt Relocations: (not relocatable) Version : 0.6.16Vendor: Mageia.Org Release : 1.mga3Build Date: Mon Dec 31 22:55:20 2012 pterjan pterjan 0.6.16-1.mga3: + Revision: 336797 - 0.6.16 * fix chroot cleaning in parallel mode * fix for some packages missing from status file btw, 0.6.15 broke the BS on valstar with this error: Not a HASH reference at /usr/bin/emi line 195. So I rolled back to 0.6.13 that was in use before. Is this package safe to install ? -- Thomas
Re: [Mageia-dev] [changelog] cauldron core/release iurt-0.6.16-1.mga3
On 31 Dec 2012 22:48, Thomas Backlund t...@mageia.org wrote: pterjan skrev 31.12.2012 23:58: Name: iurt Relocations: (not relocatable) Version : 0.6.16Vendor: Mageia.Org Release : 1.mga3Build Date: Mon Dec 31 22:55:20 2012 pterjan pterjan 0.6.16-1.mga3: + Revision: 336797 - 0.6.16 * fix chroot cleaning in parallel mode * fix for some packages missing from status file btw, 0.6.15 broke the BS on valstar with this error: Not a HASH reference at /usr/bin/emi line 195. So I rolled back to 0.6.13 that was in use before. Is this package safe to install ? Probably not, I haven't touched emi (I think boklm and tv did in previoys version). I'll have a look
[Mageia-dev] path of libexec
Hello! Name: rpm-mageia-setup Relocations: (not relocatable) Version : 1.165 Vendor: Mageia.Org Release : 1.mga3Build Date: Mon Dec 31 20:22:14 2012 Install Date: (not installed) Build Host: ecosse.mageia.org Group : System/Configuration/Packaging Source RPM: (none) Size: 271779 License: GPLv2+ Signature : (none) Packager: tmb tmb URL :http://www.mageia.org/ Summary : The Mageia rpm configuration and scripts Description : The Mageia rpm configuration and scripts. tmb tmb 1.165-1.mga3: + Revision: 336686 - set libexec dir to /usr/libexec Is this libexec the final change? If yes, then we should update i.a. cmake.macros.
Re: [Mageia-dev] how to update mageia rpmlint configuration on submission host ?
Le lundi 31 décembre 2012 20:39:16 Thomas Backlund a écrit : Thomas Backlund skrev 31.12.2012 17:09: Guillaume Rousse skrev 31.12.2012 16:24: I can't suceed submitting metasploit, because of some rpmlint error: Submission errors, aborting: - metasploit-4.5-1.mga3: - unexpanded-macro /usr/share/metasploit/lib/gemcache/ruby/1.9.1/gems/railties-3.2.8/lib/rai ls/generators/rails/plugin_new/templates/lib/%name%/engine.rb %name I did update rpmlint-mageia-policy a week ago (0.2.25), but the configuration used on the host running the check seems to still use the previous version. Do we need an explicit actions from sysadmins here ? Yep. I'll check it out tonight unless any other sysadmin beats me to it New rpmlint and policy now in place. Also -debuginfo packages should now be ok and the changes for /run, and checking for udev, systemd and tmpfiles location are now in effect -- hi, but it seems debuginfo packages are not going on the debug media but on the main media ( see in core/release )
