Re: [Mageia-dev] freeze push: ldetect-lst
Thierry Vignaud skrev 10.4.2013 19:12: Hi Please let in ldetect-lst. It fix using modesetting instead of fbdev for Poulsbo US15W(GMA500) (mga#8258) Please rebuild drakx-installer-stage2 with it once available. Thx Done .. Thomas
Re: [Mageia-dev] freeze push: drakxtools drakx-installer-stage2
Thierry Vignaud skrev 9.4.2013 09:07: Hi Please let in drakxtools drakx-installer-stage2. Submitted. -- Thomas
Re: [Mageia-dev] Upcoming release freeze: 14 packages needs fixing, by Sunday
Pascal Terjan skrev 10.4.2013 00:23: On Tue, Apr 9, 2013 at 11:07 PM, Juergen Harms juergen.ha...@unige.ch mailto:juergen.ha...@unige.ch wrote: On 04/09/2013 11:03 AM, Christiaan Welvaart wrote: ... cross-avr-gcc ... The current package has the same rpmlint warnings so you don't need to fix this right now INHO. The hardlinks are only a problem when /usr/bin is on a different filesystem than /usr. I see there are still packages being pushed - if I manage tomorrow to submit a new cross-avr-gcc, would that still have a chance to get pushed before the freeze? would be nice if Mageia-3 contains a properly working avr cross compiler - and would reduce the count of packages that dont build. Well, given that current version can not even be installed, I don't think anyone will argue against getting the package pushed, it can't be worse. And since avr stuff is also pretty selfcontained its ok. -- Thomas
Re: [Mageia-dev] M3 beta - where to report problems?
Frank Griffin skrev 4.4.2013 19:12: On 04/04/2013 10:59 AM, Anne Wilson wrote: Not much progress. My usual method of editing the kernel line to get a level 3 boot doesn't work - same blank (but lit) screen. Failsafe appears to be doing better - at least I can see messages. It reaches Reached target Multi-User Reached target Graphical Interface and there it sticks. Does that give any clue as to what is failing, and what I need to do to rescue the system? Boot a rescue disk and mount your root partition. In /etc/systemd/system you should see a symlink like: lrwxrwxrwx 1 root root 36 Mar 29 11:00 default.target - /lib/systemd/system/runlevel5.target Just remove this and re-symlink to /lib/systemd/system/runlevel3.target and you should get a level 3 boot. It's actually easier than that. Add systemd.unit=multi-user.target on kernel / grub command line and ith will boot to runlevel 3 -- Thomas
Re: [Mageia-dev] M3 beta - where to report problems?
Colin Guthrie skrev 9.4.2013 00:31: 'Twas brillig, and Thomas Backlund at 08/04/13 13:20 did gyre and gimble: It's actually easier than that. Add systemd.unit=multi-user.target on kernel / grub command line and ith will boot to runlevel 3 Or simply add a 3 onto the command line as has been the case for many years :) Of course I should probably discourage that seeing as 3 is pretty meaningless in absolute terms these days! :) Are you sure ? IIRC there has been reports of people doing it and still eneded up at graphical.target ... -- Thomas
Re: [Mageia-dev] freeze push: ldetect
Thierry Vignaud skrev 5.4.2013 13:40:
Hi
Please let in ldetect
It fixes detecting Xen blk net controllers on dom0:
- do not fake Xen blk net controllers on dom0 (mga#9546)
This resulted in a warning popup on x86_64 (which has support for dom0
by default)
since xen-*front could not be loaded.
Please rebuild drakx-installer-{binaries,stage2,rescue}.
Also push drakx-installer-images once d-i-binaries is available.
I can take care of the bump if needed.
thx
In progress...
--
Thomas
Re: [Mageia-dev] urpmi - strange read lock messages
Robert Fox skrev 5.4.2013 15:23: This is still occurring in latest Cauldron - I know the messages are harmless, but maybe they should be suppressed? You shouldn't get read lock messages unless you manually have aborted urpmi... -- Thomas
Re: [Mageia-dev] freeze push: glpi
Guillaume Rousse skrev 5.4.2013 15:06: Le 02/04/2013 20:54, Guillaume Rousse a écrit : This is a bugfix release. ping ? Submitted. -- thomas
Re: [Mageia-dev] admin intervention needed
Guillaume Rousse skrev 5.4.2013 16:21: Please remove vim-puppet and emacs-puppet (previously generated from puppet3 package) from mirrors, they block submission from default puppet package. Done. -- Thomas
[Mageia-dev] Headsup: KDE 4.10.2 is landing on cauldron...
Hi, seems our KDE guys forgot to announce it so I do it... -- Thomas
Re: [Mageia-dev] freeze push: drakx-installer-stage2 drakxtools
Thierry Vignaud skrev 4.4.2013 17:03: Hi Please let in drakx-installer-stage2 drakxtools. drakx-installer-stage2 fixes missing groups in live CDs (mga#9326). drakxtools fixes writing bogus root=/dev/ in bootloader config (mga#8717) drakx-installer-stage2: = - drakx-in-chroot: o do not copy /etc/resolv.conf in chroot if not using either remote display or remote repository (thus fixing goup lookups, mga#9326) drakxtools: - bootloader-config: o fix adding bogus bootloader entries (root=/dev/) when silently failing to lookup / partition (mga#8717) o try harder to lookup / partition y looking at mounted points (mga#8717) thx submitted. -- Thomas
Re: [Mageia-dev] freeze push: drakx-installer-stage2
Thierry Vignaud skrev 4.4.2013 19:59: Hi please let in drakx-installer-stage2. It has a better fix for mga#9326 (covering uses of draklive we don't use for now). It also logs when ignoring some dmraid devices, which I hope should help some bug reports. details: = - force loading NSS modules (mga#9326) - log ignored dmraid devices (might help mga#9467) - drakx-in-chroot: o always copy /etc/resolv.conf again thx Submitted. -- Thomas
Re: [Mageia-dev] Headsup: KDE 4.10.2 is landing on cauldron...
Nicolas Lécureuil skrev 4.4.2013 13:59: Le jeudi 4 avril 2013 13:14:01 Thomas Backlund a écrit : Hi, seems our KDE guys forgot to announce it so I do it... sorry i got a pb in my mailer :( i wrote a mail but seems it didn't pass the ML see it : Hello, the maybe last KDE Update will start in some minutes. KDE and Telepathy-kde will be updated. sorry again :( No worries, it happends... :) please notify the list when its all done -- Thomas
Re: [Mageia-dev] Freeze push: qmmp
Kamil Rytarowski skrev 30.3.2013 19:09: On 30.03.2013 17:30, Kamil Rytarowski wrote: Hello! Please let-in qmmp 0.6.8, it's a new release and fixes various core dump problems. https://bugs.mageia.org/show_bug.cgi?id=9468 Regards, Ah, and please push it to core and tainted. Remove *qmmp* from nonfree. removed from nonfree, tainted pushed, core ok -- Thomas
Re: [Mageia-dev] freeze push: perl-URPM
Thierry Vignaud skrev 23.3.2013 18:07: Hi Please let it in perl-URPM It fixes an important bug where we would select the wrong flavor of kernel dkms packages: - fix selecting right DKMS flavor (mga#9172) Once it's available, please rebuild drakx-installer-stage2 with it and include new drakx in beta 4 thx In progress... -- Thomas
Re: [Mageia-dev] freeze push: urpmi rpmdrake
Thierry Vignaud skrev 19.3.2013 20:03: Hi Please let in urpmi rpmdrake: Submitted. main news: - global progress bar a crash fir for rpmdrake - gurpmi displays erasure progress now. - urpmi enables gurpmi rpmdrake to display erasure progress. - urpmi will look in other media for requires when looking at updates only And I think I speak for all involved in QA maintenance/security updates... _BIG_ thanks for your work and especially for squashing #2317 urpmi: = - library: o drop 'callback_report_uninst' now that 'callback_uninst' enables to get erasure progress o enable rpmdrake/gurpm/drakx to pass their own callbacks for erasure progress errors o enhanced doc o revert 'fixing (g)urpmi --auto-select --update defaulting to all media when there're no update media (#1024)' as it break looking for deps in other media with --update (mga#2317) - gurpmi: o split global progress bar widget for rpmdrake (mga#778) o show removed packages in progress too o support exceptions in callback in main wrapper too o support other distros which do not handle exceptions in gtk+ callbacks o use new exception management rpmdrake: - do not offer to pick only update media unless using --expert (mga#2317) - use a global progress bar when installing (mga#778) - workaround a crash (mga#9197) Thx -- Thomas
Re: [Mageia-dev] Corrupt packets with ath5k
JA Magallón skrev 16.3.2013 03:04: I found a possible clue, it references a patch: http://blog.gmane.org/gmane.linux.drivers.ath5k.devel https://bugzilla.kernel.org/show_bug.cgi?id=55211 Can you test with kernel-3.8.3-2.mga3 when it lands on the mirrors (currently building)... I've merged a fix that got suggested today on -pci ml. -- Thomas
Re: [Mageia-dev] freeze push: drakx-installer-binaries
AL13N skrev 14.3.2013 08:38: Op woensdag 13 maart 2013 21:00:45 schreef AL13N: Please push: drakx-installer-binaries: - fix loading modules with - in their names (mga#9242) in the stage1 window to load extra modules (eg: xen-netfront), all modules with '-' in the name failed. this fix allows those modules to be loaded when requested. ping d-i-b was pushed ~10 h ago by guillomovitch I just pushed stage2/images/rescue to pick up latest d-i-b. -- Thomas
Re: [Mageia-dev] Why is AHCI statically compiled into kernel?
R James skrev 5.3.2013 19:34: On Tue, Mar 5, 2013 at 9:41 AM, Thomas Backlund t...@mageia.org mailto:t...@mageia.org wrote: It's needed to be able to boot new hw without need for initrd. https://wiki.mageia.org/en/Feature:BootSansRamdisk Ah, I didn't know about that. It seems like the target systems will need to be simple AND have ahci compliant boot controllers. Otherwise a bunch of SATA drivers will need to be statically compiled in kinda like the old IDE days. It'll be interesting to see how many users complain because they think they shouldn't need an initrd... :o) yeah, we / I chose to make only AHCI builtin as pretty much all new hw coming out theese days are ahci-compliant, so it works out of the box. And to not bloat the kernel the rest of the hw support got left as modules. Now this feature booting without initrd is obviously targetted for laptops/netbooks desktops where people care about fast boot. For servers ( bigger workstations) where you rely on SCSI / SAS / FC / you still need initrds, and usually you dont really care if a boot take a little longer. -- Thomas
Re: [Mageia-dev] Why is AHCI statically compiled into kernel?
R James skrev 5.3.2013 19:53: On Tue, Mar 5, 2013 at 11:11 AM, Colin Guthrie mag...@colin.guthr.ie mailto:mag...@colin.guthr.ie wrote: Anything that relies on ordering is just broken by design. We need to handle things gracefully regardless of the order they are detected. This is why UUIDs are the defacto method for filesystem identification these days and why in mga4 we'll likely switch to a consistent naming scheme for networking devices too. Yes, I understand that cryptic-looking UUIDs are the defacto identifiers but when mdadm reports that /dev/sdf1 has failed in a parity RAID setup, it will be good if a mere mortal can know which drive to replace. :o) If you follow raid devel list you will soon learn that they dont recommend trusting the /dev/sd* naming either as it is by no means static... :) depending on your hw, they may for example hange place if you happend to have a usb disk plugged at boot and so on. so the thing to check is for example what disk is mapped as /dev/disk/by-id/* where you can match on actual disc serial number and so on... then you can be sure wich disk is failing / has failed... -- Thomas
Re: [Mageia-dev] Freeze push: desktop-common-data
Guillaume Rousse skrev 4.3.2013 13:52: Le 03/03/2013 00:57, nicolas vigier a écrit : Ok your buggy script has been restored. Now someone need to submit desktop-common-data again. A different conclusion could have been than two different usages requires two different scripts, and than they could perfectly coexist with two different names... Yep, that would be the best way forward. -- Thomas
Re: [Mageia-dev] freeze push: erl-Glib-Object- Introspection
Thierry Vignaud skrev 3.3.2013 11:46: Hi Please let in perl-Glib-Object-Introspection. It's bug fixes, all of whose we already have. It's just reblessing them as a new version It doesn't impact much submitted. -- Thomas
Re: [Mageia-dev] Freeze push: desktop-common-data
nicolas vigier skrev 2.3.2013 17:50: Please push desktop-common-data. In this new version /usr/bin/editor has been changed to try to use $VISUAL and $EDITOR instead of only $TEXTEDITOR : http://svnweb.mageia.org/soft/desktop-common-data/trunk/bin/editor?view=log submitted. -- Thomas
Re: [Mageia-dev] EFI/GPT
Oliver Burger skrev 1.3.2013 20:47: Hi there, I have a question here in the german forums from ixsoft - a company selling linux based operating systems and much open source and linux related stuff. Do we have support for EFI/GPT in Mga3? Bernd Hentig from ixsoft says something about GPT partitions and EFI (without the secure boot stuff). I have not looked into that topic at all until now and don't know anything about it. Well, technically we already support both, but not OOB with the installer. If you create gpt partitions with parted, the installer will happily install mga on them, and it will boot and run correctly. The efi part can also be managed, but you have some manual work to get it to boot properly. I'm working on making mga3 beta3 live images capable of booting in efi mode, and then if it works ok, I'll extend it to normal install isos, and then we'll have to see what adaptions need to be done in the installer to properly install efi bootloader and we'll be done. Can anyone help me? Perhaps it would be good for someone with knowledge about that topic to contact Bernd himself. ixsoft is a major player in that field in Germany... Well, I do intend to make sure mga3 will boot install on uefi hw. (as for secure boot, that I wont ever support) -- Thomas
Re: [Mageia-dev] EFI/GPT
Oliver Burger skrev 1.3.2013 21:48: Sounds good. So we aim to support UEFI (without secure boot) for Mga3? I will forward this to the German forums then... Yep. -- Thomas
Re: [Mageia-dev] EFI/GPT
Bruno Cornec skrev 1.3.2013 22:28: Thomas Backlund said on Fri, Mar 01, 2013 at 09:42:41PM +0200: Well, I do intend to make sure mga3 will boot install on uefi hw. Great ! (as for secure boot, that I wont ever support) Hummm. Why can't Mageia supoprt it the way Fedora and Ubuntu are doing ? Using a shim boot loader ? Well, I dont drink the MS cool-aid... so I wont spend a minute worrying about that crap. the secure boot crap is a vendor lock-in thought up by MS disguised as a security feature so they can own your hw and tell you what you can and cannot run... sure, it can currently be disabled... but as soon as people start accept this there will soon be a Secure Boot v2 mandating it be enabled all the time, and those that want complete freedom will be screwed as MS gets in a position to control what can boot on your system... We are promoting freedom and open source, not MS crap. So the time to speak up is _now_ and fight this vendor lock-in. -- Thomas
Re: [Mageia-dev] freeze push: drakxtools drakx-installer-stage2
Thierry Vignaud skrev 28.2.2013 10:03: Hi please push drakxtools drakx-installer-stage2 drakxtools - drakboot: o allow installing grub2 on a partition (mga#8462) o try harder not to have duplicate stuff on grub2 cmd line drakx-installer-stage2 - bootloader: o allow installing grub2 on a partition (mga#8462) o try harder not to have duplicate stuff on grub2 cmd line - do not put entry for CD/DVD in /etc/fstab (mga#7657) (it breaks urpmi) Thx Submitted. -- Thomas
Re: [Mageia-dev] Freeze push: sudo
David Walser skrev 28.2.2013 20:13: This updates to 1.8.6p7 which fixes a security issue only. Ubuntu has rated this as a high-severity security issue. http://www.sudo.ws/sudo/alerts/epoch_ticket.html http://www.sudo.ws/sudo/stable.html http://www.ubuntu.com/usn/usn-1754-1/ I've verified that it builds and works fine in Cauldron. Submitted. -- Thomas
Re: [Mageia-dev] freeze push: openmpi 1.6.4
Arnaud Patard (Rtp) skrev 28.2.2013 22:39: Hi, Please push openmpi 1.6.4. It's a bug fix release and this one is building on arm. Amongst the various fixes, it's fixing some accidental abi breaking on the f90 librarie (it's putting back the right lib version number so would be annoying to release with wrong version). Thanks, Arnaud Submitted. -- Thomas
Re: [Mageia-dev] Nouveau nvidia vesa conflict
Jose Jorge skrev 24.2.2013 20:54: Le 24/02/2013 12:32, André Salaün a écrit : It is not possible to use nvidia drivers neither vesa with nouveau (nvidia 9600 gt, all updated today)? Even if I blacklist nouveau and uninstall it I have a conflict. I experience something like that : even when nvidia driver is configured, nokmsboot is selected, but nouveau is loaded in the initrd. This is a new bug as in Beta1 it was not there, but I was waiting to do a clean install as my setup had lots of updates. I suppose it is something in dracut? Yep, bug is found and fixed in dracut-025-5.mga3 So just install that one, regenerate the initrd and reboot. It should work properly then. -- Thomas
Re: [Mageia-dev] Freeze push: gnome-shell 3.6.3.1
Jani Välimaa skrev 23.2.2013 14:26: Hi, please push new gnome-shell 3.6.3.1. It fixes a regression [1]. Submitted. -- Thomas
Re: [Mageia-dev] dhclient lease files location
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... -- Thomas
Re: [Mageia-dev] Gnome mess in Mageia SVN...
Olav Vitters skrev 21.2.2013 11:08: On Thu, Feb 21, 2013 at 01:10:33AM +0200, Thomas Backlund wrote: Can you _please_ kill your automatic upload scripts... done. Thanks. It should have been killed as soon as we hit version freeze. It's making a mess in Mageia SVN. I see several uploads by ovitters, but no freeze push requests, and also some 3.7.90 stuff getting uploaded and seveal version bumps that is not bugfixes only... 3.7.90? It will not upload that. It will only upload if someone before uploaded such a version. that may be ... we need to review and fix the packages / downgrades... but someone uploading wrong package does not excuse doing more of it... but that's exactly the issue of running unmonitored bots when version freeze is in effect... I see a new NetworkManager also just ended up in SVN, despite iirc you earlier stated you'd probly need to roll down to an older one... Indeed, seems that there is a still a bug. So you are making the same mess for upcoming mga3, that is also in mga2 updates svn, making everyone elses work harder, when svn does not match what's on mirrors... this is painful for QA and security maintenance... Apologies for trying to provide a new GNOME as requested _on_my_own_ and not finishing it. Not what I wanted, but not done on purpose. Yeah, well, stuff going to updates_testing is meant for updates, so when you start a push, please follow up on it, or dont push at all... and automated bots pushing stuff on its own to updates_testing is not something that helps... official updates needs to be thought out, and monitored so you really know what is pushed and needs to be validated. But enough about that... updates_testing got cleaned so we will have to cope only with the svn stuff if/when pushing gnome and gnome deps releated security updates .. Automated scripts can be ok during open cauldron, but _never_ when we try to stabilize for a release. Meanwhile, Mageia 3 keeps getting delayed and delayed and not due to me. So what... I know you want to push GNOME 3.8 as it's always more fun to work with the latest/greatest yet but the sad fact is that there does does not seem to be enough gnome maintenance/maintainers interests to really pull it off... Not to mention there is serious doubts the the 3.8.0 release will be good enough to work properly for all endusers when the fallback is dropped, so it would need atleast a update to 3.8.x as a followup later to provide something that actually works, wich comes back to lack of maintainers... So ... once again... please kill the script, clean up svn, revert packages to latest stable, and try to focus on providing a good / fully updated Gnome 3.6 will be available for Mga3. I rather take a break from Mageia. Just because we ask you to focus on distro quality thinking for a while and not as a gnome dev only wanting to play with latest code ? And we get stuck with cleaning up... Oh well... I guess that just confirms that 3.6 is a safer road for us then... I do hope you reconsider, but everyone is here by their own free will... And I hate these personal email habits. CC'ing mageia-dev. I thought it only concerned you for now, as it was your bot running wild (and unmonitored) that got me to mail you... But if that's what you want... Fine by me... I'll post on -dev for now then... -- Thomas
Re: [Mageia-dev] dhclient lease files location
Sander Lepik skrev 23.2.2013 17:47: -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. In progress... -- Thomas
Re: [Mageia-dev] Freeze push: stog
Pierre-Malo Deniélou skrev 23.2.2013 23:11: Le 23/02/13 20:59,Pierre-Malo Deniélou nous adresse ces quelques mots : Le 22/02/13 23:51,Guillaume Rousse nous adresse ces quelques mots : Le 22/02/2013 19:19, Malo a écrit : Hello, Please submit stog-0.7.0. Build failure: http://pkgsubmit.mageia.org/uploads/failure/cauldron/core/release/20130222183213.guillomovitch.valstar.4971/log It should be ok now to try again. Thanks, Thanks Guillaume, but you were too fast :-). The last submission was still using the unfixed ocaml-config-file-1.1-2.mga3 Submitted. -- thomas
Re: [Mageia-dev] Corrupt packets with ath5k
JA Magallón skrev 21.2.2013 02:28: On 02/20/2013 08:14 PM, JA Magallón wrote: Hi all... I have a strange problem with latest kernels. When I updatw my netbook I get many Installation failed, bad rpms: mesages. First I thougt that the oldie cheap ssd was failing (it is an Aspire AOA110). But the updates work always fine when plugged to ethernet. Now i tried to copy a couple RPMS via ssh over wifi and got: mplayer-1.1-11.r35916.1.mga3.tainted.i586.rpm 100% 2192KB 2.1MB/s 00:00 Received disconnect from 192.168.1.51: 2: Packet corrupt lost connection I try scp'ing a folder with 3 cauldron kernel rpms. Possible clues: - 3.7.1: works fine - warm boot in 3.8.0: transfer stalls and scp looks hanged, speed drops to zero, but no error message - cold boot in 3.8.0: transfer stops with Packet corrupt error or sometimes stalls.. Will ask in LKML. Does kernel-linus-3.8.0-1.mga3 work ?
Re: [Mageia-dev] Freeze push: dbus-glib (security update)
David Walser skrev 16.2.2013 19:00: This updates to 0.100.1, which literally contains just one change, a fix for security issue CVE-2013-0292: http://cgit.freedesktop.org/dbus/dbus-glib/commit/?id=166978a09cf5edff4028e670b6074215a4c75eca I've confirmed that it builds and installs fine in Cauldron. Submitted. -- Thomas
Re: [Mageia-dev] Freeze push: firefox, firefox-l10n
FundaWang skrev 16.2.2013 20:08: Hello, Could firefox and firefox-l10n 17.0.3esr be pushed? See you. Submitted. -- Thomas
Re: [Mageia-dev] Freeze push: gambas3
Matteo Pasotti skrev 10.2.2013 23:04: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 10/02/2013 19:52, Thomas Backlund wrote: 10.02.2013 20:46, Matteo Pasotti skrev: Hello, can someone push gambas3 please? Some informations from the original announce: This new release fixes about 240 bugs and adds about 270 new features. So 240 fixes, and atleast 270 new bugs introduced, eh ... :) Hello Thomas, even backporting 240 fixes to the current package it's not that easy imho but, I think that the real point (I'm criticizing myself) is that I've completely missed this sentence[1] from the release notes :-/ Is there a way I can cancel this freeze push request and restore the previous svn/binrepo state? I do not think that keeping version 3.3.4 it's the best solution because there are many improvements not related to new features shipped with 3.4.0 but, I clearly understand your reasons and I can try to backport the missing fixes without package version changes. You missed the smiley, didn't you :) gambas3 3.4.0 submitted -- Thomas
Re: [Mageia-dev] Freeze push: razor-qt (fixes mga2-mga3 update)
Matteo Pasotti skrev 16.2.2013 23:45: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 16/02/2013 19:52, Florian Hubold wrote: Hi there, please push razor-qt. It's a bugfix release only to 0.5.2, and i've worked on it so that upgrading from mga2 - 3 works now, as it was broken before. And i've added a missing BuildRequire for two of the basic panel plugins, which was unnoticed until now, it seems. I've also enabled tests, and replaced the URL with the current one, as the github one is not working anymore. Yeap, no new features, just fixes (systemd fix was already applied through a patch - razorqt-0.5.0-systemd.patch). The maintainer (Matteo aka pasmatt) told me he's currently quite busy and he's okay with me committing those fixes. I can confirm :) Well, it would be easier if you would suggest correct package, as the srpm is called razorqt (and not razor-qt like upstream) Anyway... submitted... -- Thomas
Re: [Mageia-dev] [changelog] [RPM] cauldron core/release x11-driver-video-intel-2.21.0-1.mga3
10.02.2013 18:25, Thierry Vignaud skrev: On 7 February 2013 00:06, tmb buildsystem-dae...@mageia.org wrote: tmb tmb 2.21.0-1.mga3: + Revision: 395015 - 2.21.0: improved haswell support, bugfixes http://cgit.freedesktop.org/xorg/driver/xf86-video-intel/commit/?id=617fadf3acf7bf75fb203c1e85fd0ddb98b3dbb9 +Release 2.21.1 (2013-02-10) +=== Oh, I'll go for 2.21.2 instead :)... -- Thomas
Re: [Mageia-dev] freeze push: perl-URPM urpmi
09.02.2013 12:23, Thierry Vignaud skrev: On 8 February 2013 23:26, Pascal Terjan pter...@gmail.com wrote: please let in perl-URPM urpmi perl-URPM fixes a bug regarding installing delta rpm urpmi fixes counting erasures in progress bar. I think urpmi should probably not count erasures at all in the $cur/$total number, since IMHO the count should be for the packages installed instead of applied transactions, and package removal is usually much faster than installation. Try that on texlive-texmf :-) This does what you want, a separate counter for erasures Nice :) Probably should see if others agree with me or not before applying I guess... Everyone, WDYT? I thought of requesting such change when I ran the new version but then decided it was not important :) Should I wait for one more vote before dcommiting releasing? Go ahead and add it, I liked it too :) -- Thomas
Re: [Mageia-dev] freeze push: perl-URPM urpmi
09.02.2013 14:22, Thierry Vignaud skrev: On 9 February 2013 12:06, Thomas Backlund t...@mageia.org wrote: Try that on texlive-texmf :-) This does what you want, a separate counter for erasures Nice :) Probably should see if others agree with me or not before applying I guess... Everyone, WDYT? I thought of requesting such change when I ran the new version but then decided it was not important :) Should I wait for one more vote before dcommiting releasing? Go ahead and add it, I liked it too :) then push it please Submitted. -- Thomas
Re: [Mageia-dev] Logging + Provides/Requires (Re: [RFC] rsyslog vs journalctl)
08.02.2013 15:19, Olav Vitters skrev: On Fri, Feb 08, 2013 at 02:07:52PM +0100, Anne Nicolas wrote: Le 08/02/2013 13:14, Olav Vitters a écrit : On Fri, Feb 08, 2013 at 10:31:42AM +, Colin Guthrie wrote: Q) Will we make persistent disk-based journals optional? Yes: Makes it harder to ask a consistent question to extract debug. No: Some people will moan. It is either persistent logging or logging in memory right? I assume people won't understand that it'll log anyways, just in memory. So no point in giving an option that does not do what people might expect. Just one point about this. It was said during meeting that having journalctl by default could break some other software like fail2ban. This should be checked. Some software relies on /var/log/messages and as such syslog. Journal does not break anything. But if you then remove syslog, then result is that such things will break. Same for gnome-system-log. IMO we should fix that software which relies on /var/log/messages (before 3 and if found afterwards, provide updates). For unmaintained software, deal with it as any other. /var/log/messages usually contains this weeks log messages. It is pretty trivial to replace that with the output of journalctl. I think the best thing for Mga3 is to both install journald and upgrade rsyslog too by sticking it on install medias. Then we add in Mga 3 release notes that for upgrades rsyslog will be upgraded, but new installs will only have journald, so people wanting / needing it _must_ install it manually. And we also add the in the notes that we *might* obsolete (but not remove from repos, to still keep it as an option) it during upgrades in coming mga releases if journald gains all the features needed to really replace rsyslog. So we suggest people start trying to see if journald can provide all that they need. As a side note... when journald was first introduced I had the what for... reaction too as I was so used to grepping syslogs for stuff I needed... :) But now when I have gotten used to journalctl and the power of it, I dont really need the old logs anymore :) -- Thomas
Re: [Mageia-dev] Freeze push: flash-player-plugin 11.2.202.262
08.02.2013 19:20, David Walser skrev: Anssi Hannula anssi@... writes: Adobe Flash Player 11.2.202.262 contains fixes to critical security vulnerabilities found in earlier versions. Ping? This is now pushed in Mageia 2. Submitted. -- Thomas
Re: [Mageia-dev] Freeze push: openttd
08.02.2013 19:38, Jani Välimaa skrev: Hi, please push new openttd. Currently we have beta1 and new beta2 fixes several issues [1]. [1] http://ftp.snt.utwente.nl/pub/games/openttd/binaries/releases/1.3.0-beta2/changelog.txt Submitted. -- THomas
Re: [Mageia-dev] Freeze push: eog 3.7.4
Sander Lepik skrev 5.2.2013 11:15: 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.. Nope. It needs to be rolled back to 3.6 stable -- Thomas
Re: [Mageia-dev] Freeze push: vinagre 3.7.4
nicolas vigier skrev 24.1.2013 16:31: On Tue, 15 Jan 2013, Colin Guthrie wrote: 'Twas brillig, and Olav Vitters at 14/01/13 23:26 did gyre and gimble: bersuit pushed an unstable version of vinagre. maintainer is set as nobody. not sure why it was done, but should update from 3.7.3 to 3.7.4. We can always revert it an earlier version if you'd prefer. Ditto for eog if that's also preferred. Cauldron users manually downgrading is fine IMO. Should we revert to stable version ? Yes. -- Thomas
Re: [Mageia-dev] Freeze push: vino 3.7.4
nicolas vigier skrev 24.1.2013 16:33: On Tue, 15 Jan 2013, Olav Vitters wrote: Same as vinagre, bersuit pushed an unstable version while there is no maintainer. Almost no changes in this version, should be safe to update. Should we revert to stable version ? Yes. -- Thomas
Re: [Mageia-dev] freeze push: perl-URPM urpmi
05.02.2013 16:34, Thierry Vignaud skrev: Hi please let in perl-URPM urpmi perl-URPM fixes a bug regarding installing delta rpm urpmi fixes counting erasures in progress bar. Both testsuites pass. thx Submitted. -- Thomas
Re: [Mageia-dev] freeze push: perl-URPM urpmi
05.02.2013 17:17, Thierry Vignaud skrev: On 5 February 2013 15:56, Thomas Backlund t...@mageia.org wrote: please let in perl-URPM urpmi perl-URPM fixes a bug regarding installing delta rpm urpmi fixes counting erasures in progress bar. Both testsuites pass. thx Submitted. BTW core/updates_testing still need cleaning *rpm*4.11.0* thx Cleaned. -- Thomas
Re: [Mageia-dev] Freeze push gsoap (needed to build virtualbox vboxwebsrv)
05.02.2013 21:41, Angelo Naselli skrev: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Il 05/02/2013 10:22, Sander Lepik ha scritto: 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 It should be ok tmd did it: anaselli :v gsoap Sophie anaselli: 2.7.17-1.mga1 // core-release (Mga, 2, i586), core-release (Mga, 1, i586) anaselli :v gsoap -v cauldron Sophie anaselli: 2.8.12-2.mga3 // core-release (Mga, cauldron, i586) Maybe we should ping tmb for virtualbox... if it is not built against new gsoap yet... No need, I just haven't had time to write systemd service files for it yet... (I know there is a sysvinit script available, but as we are nuking that stuff, I'm not sure I want to add it...) -- Thomas
Re: [Mageia-dev] Critical Samsung UEFI bug: Booting Linux using UEFI can brick Samsung laptops
Johnny A. Solbu skrev 1.2.2013 06:57: http://www.h-online.com/open/news/item/Booting-Linux-using-UEFI-can-brick-Samsung-laptops-1793958.html Booting Linux using UEFI just once on various Samsung laptops is enough to permanently stop them working. Several reports have been posted on the Ubuntu bug tracker, but the problem is likely to also be present in other Linux distributions, as it appears to be caused by a kernel driver for Samsung laptops. Kernel developers are currently discussing a change which would disable the driver when booting via UEFI. Mageia is most likely also affected by this. Well, sort of... but it's not so critical as we dont support UEFI Installs / boots OOB so far, so people have to to many things manually to boot in UEFI mode. Nevertheless it is fixed upstream in 3.8-rc6, so cauldron/mga3 will be safe after I upload 3.8.0-0.rc6.1.mga3 (probably tonight)... And for mga2 it will be fixed in upcoming upstream 3.4.30. -- Thomas
Re: [Mageia-dev] Latest update borked my x server
Wolfgang Bornath skrev 29.1.2013 10:26: Installed MGA3 Beta2 including proprietary nvidia driver, working nicely. After doing updates including kernel 3.8.0-desktop-0.rc5.1.mga3 the startup process stopped and showed a message that a display driver module is loaded which conflicts with the current setup (translation from German) and so x server may not start correctly. And so it was: after Started LSB: Nameserver information manager the start process hangs. Switching to VT2 and logging in, giviong the command 'startx' fails: modprobe: ERROR: could not insert 'nvidia_current': No such device modprobe: ERROR: Error running install command for nvidia modprobe: ERROR: could not insert 'nvidia'; Operation not permitted (EE) Server termibnated with error (1) xinit: giving up xinit: unable to connect to X server: Connection refused xinit: server error That's it. Seems nouveau blacklisting is being ignored :/ So it blocks the nvidia driver from loading properly https://bugs.mageia.org/show_bug.cgi?id=8863 -- Thomas
Re: [Mageia-dev] [council] *ping* Media query: secure boot support
Olav Vitters skrev 29.1.2013 10:43: On Sun, Jan 27, 2013 at 01:43:25PM +0100, Marja van Waes wrote: From: Sam Vargheses...@gnubies.com [..] I would like to know what Mageia plans to do about secure boot - when you will have a release that supports booting on hardware on which this feature is enabled. I'm wondering as well. I've been thinking to upgrade my system somewhere this year. This means secure boot, UEFI, etc. It would be nice if Mageia supports that nicely. Supporting (U)EFI does not require SecureBoot support... we wont support SecureBoot for Mga3, and there is no rush considering a lot of changes is still happening on several fronts... I will try to see if I can fix the UEFI part for ~beta3, but no promises yet 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... -- Thomas
Re: [Mageia-dev] [council] *ping* Media query: secure boot support
Olav Vitters skrev 29.1.2013 13:12: On Tue, Jan 29, 2013 at 11:11:55AM +0200, Thomas Backlund wrote: And personally, I dont think we should ever bother with the SecureBoot crap as its flawed in so many ways... I quite like SecureBoot. This way you can avoid attacks on the boot sector. Yeah, and when MS screws up with one of the master keys (or some hw wendor) think about the dual-booters Microsft pushes revocation key through windowsupdate, and you suddenly find out your linux wont boot anymore, beacuse the signature that is supposed to validate your boot has been revoked... Or a local dos: just add a single byte to the end of some of the signed files/images and the signature checks fail, ending up with non-bootable system you dont even need to exploit it further Or MS alters license rules around key signing, so when your key expires, guess what... and ms wont be in a hurry to fix it look at the time it has taken so far for linux foundation to try and get proper signatre key or... There is so many fun ways to screw up this security illusion, that it should be buried forgotten already... this secure boot pushed by ms is also in reality a ms-restricted boot... -- Thomas
Re: [Mageia-dev] [council] *ping* Media query: secure boot support
Colin Guthrie skrev 29.1.2013 11:30: 'Twas brillig, and Thomas Backlund at 29/01/13 09:11 did gyre and gimble: Olav Vitters skrev 29.1.2013 10:43: On Sun, Jan 27, 2013 at 01:43:25PM +0100, Marja van Waes wrote: From: Sam Vargheses...@gnubies.com [..] I would like to know what Mageia plans to do about secure boot - when you will have a release that supports booting on hardware on which this feature is enabled. I'm wondering as well. I've been thinking to upgrade my system somewhere this year. This means secure boot, UEFI, etc. It would be nice if Mageia supports that nicely. Supporting (U)EFI does not require SecureBoot support... we wont support SecureBoot for Mga3, and there is no rush considering a lot of changes is still happening on several fronts... I will try to see if I can fix the UEFI part for ~beta3, but no promises yet 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... On a semi-related note, it would be nice to package gummiboot although I have no h/w to test it on. Yep, that is one of the things I'm looking at... For mga4 it might make sense to integrate it (assuming it's still a good solution) properly into our tools. Personally, I'm going to avoid grub2. It seems insane to me to implement all kinds of exotic filesystem supoort and even md stuff in a bootloader... Well, I think for next 3.8 kernel build I think I will make ahci, ext4 and btrfs builtin so you can boot without initrd on new hw, and if you install the kernel in correct place on the efi partition, you can boot the kernel directly without bootloader... :) -- Thomas
Re: [Mageia-dev] [council] *ping* Media query: secure boot support
Olav Vitters skrev 29.1.2013 14:40: On Tue, Jan 29, 2013 at 01:38:56PM +0200, Thomas Backlund wrote: Olav Vitters skrev 29.1.2013 13:12: On Tue, Jan 29, 2013 at 11:11:55AM +0200, Thomas Backlund wrote: And personally, I dont think we should ever bother with the SecureBoot crap as its flawed in so many ways... I quite like SecureBoot. This way you can avoid attacks on the boot sector. Yeah, and when MS screws up with one of the master keys (or some hw wendor) think about the dual-booters Microsft pushes revocation key through windowsupdate, and you suddenly find out your linux wont boot anymore, beacuse the signature that is supposed to validate your boot has been revoked... In which case I'd just turn secure boot off? Same for all the other examples. Maybe it at one point it has to be disabled, but at the moment that is not the case and it provides something useful. and if the hw vendor has not implemented a way to turn it off... -- Thomas
Re: [Mageia-dev] Freeze push: libssh (security update)
David Walser skrev 29.1.2013 02:42: Updating to version 0.5.4, which just fixes 3 crasher bugs: -CVE-2013-0176 – NULL dereference leads to denial of service -Fixed several NULL pointer dereferences in SSHv1. -Fixed a free crash bug in options parsing. http://www.libssh.org/2013/01/22/libssh-0-5-4-security-release/ Confirmed it builds successfully locally. Submitted. -- Thomas
Re: [Mageia-dev] freeze push: libroffice
Thierry Vignaud skrev 28.1.2013 07:37: Hi Please let in freeze push: libroffice-4.0.0.2 This is RC2, we have RC1. Thx Submitted. -- Thomas
Re: [Mageia-dev] freeze push: libroffice
Thomas Backlund skrev 29.1.2013 06:36: Thierry Vignaud skrev 28.1.2013 07:37: Hi Please let in freeze push: libroffice-4.0.0.2 This is RC2, we have RC1. Thx Submitted. http://pkgsubmit.mageia.org/uploads/failure/cauldron/core/release/20130129043512.tmb.valstar.7406/log/libreoffice-4.0.0.2-1.mga3/build.0.20130129043609.log -- Thomas
Re: [Mageia-dev] Freeze Push: bootsplash
Colin Guthrie skrev 27.1.2013 12:23: This is one of our packages thus semi-exempt from freeze rules. But either way it fixes a potential security issue. Col Submitted. -- thomas
Re: [Mageia-dev] freeze push: perl-URPM
Thierry Vignaud skrev 21.1.2013 20:07: On 20 January 2013 22:16, Thierry Vignaud thierry.vign...@gmail.com wrote: Hi Please let in perl-URPM. It fixes scoring locale packages in urpmi. Ping? Submitted. -- Thomas
Re: [Mageia-dev] freeze push: perl-URPM
Thomas Backlund skrev 21.1.2013 20:09: Thierry Vignaud skrev 21.1.2013 20:07: On 20 January 2013 22:16, Thierry Vignaud thierry.vign...@gmail.com wrote: Hi Please let in perl-URPM. It fixes scoring locale packages in urpmi. Ping? Submitted. http://pkgsubmit.mageia.org/uploads/failure/cauldron/core/release/20130121180936.tmb.valstar.20102/log/perl-URPM-4.23-1.mga3/build.0.20130121181003.log -- THomas
Re: [Mageia-dev] freeze push: perl-URPM
Thierry Vignaud skrev 21.1.2013 20:58: On 21 January 2013 19:13, Thomas Backlund t...@mageia.org wrote: Please let in perl-URPM. It fixes scoring locale packages in urpmi. Ping? Submitted. http://pkgsubmit.mageia.org/uploads/failure/cauldron/core/release/20130121180936.tmb.valstar.20102/log/perl-URPM-4.23-1.mga3/build.0.20130121181003.log I hate myself too :-( Please try again No worries :) Submitted. -- Thomas
Re: [Mageia-dev] Freeze push: amarok
Luc Menut skrev 19.1.2013 12:34: Hello, Le 18/01/2013 10:34, fundawang a écrit : Hello, Could amaork 2.7.0 stable be pushed into cauldron? We target at 2.7.x for mga3, and we currently have 2.6 beta version in cauldron. Thanks. ping It would be nice to have amarok 2.7.0 final release in upcoming beta 2; it seems to fix crashes reported in release_blocker #7748 (it fixes crashes for Nikita Krupenko, and myself with a local build of amarok 2.7.0). https://bugs.mageia.org/show_bug.cgi?id=7748 Submitted. -- Thomas
Re: [Mageia-dev] Freeze push wxsvg for bug#8727
eatdirt skrev 20.1.2013 01:48: Hi there, please push wxsvg, that's a bumped version to 1.1.11 that fixes https://bugs.mageia.org/show_bug.cgi?id=8727 on dvdstyler. As far as I can test, dvdstyler does not need a rebuild, but feel free to do it if you juge so. urpmq --whatrequires lib64wxsvg0 dvdstyler lib64wxsvg-devel lib64wxsvg0 so nothing else should be affected. Submitted. -- Thomas
Re: [Mageia-dev] Freeze push: eclipse-texlipse
D.Morgan skrev 20.1.2013 04:06: Hi, Please push eclipse-texlipse, this is a new version that compiles with new eclipse Submitted. -- Thomas
Re: [Mageia-dev] freeze push: firefox-aurora
Thierry Vignaud skrev 20.1.2013 12:13: On 18 January 2013 16:51, Thierry Vignaud thierry.vign...@gmail.com wrote: Hi Please let in firefox-aurora. It doesn't impact anything in the distro and nothing depends on this package,. ping? ping? Submitted. -- Thomas
Re: [Mageia-dev] Freeze push request - python-pygments
Barry Jackson skrev 20.1.2013 14:52: On 19/01/13 16:31, Colin Guthrie wrote: 'Twas brillig, and Barry Jackson at 19/01/13 14:51 did gyre and gimble: On 19/01/13 14:41, Barry Jackson wrote: In order to fix https://bugs.mageia.org/show_bug.cgi?id=7906 which is about the poor display of many spec files in ViewVC. We need the latest version of python-pygments which has just been released with RPM spec lexer included. This would also need to be installed on the ViewVC server. The new version is 1.6 rc1 http://pygments.org/download/ It is not in svn yet and I have not yet managed to contact the maintainer (philippem), although I have built it locally, and it's ready to upload. I forgot the questions :/ Will it be possible to include this in Mga3 or should it wait until Mga4 Cauldron? If it waits, then will we be able to install the Cauldron version on the server to fix this bug before Mga4 ? Assuming the upstream is not deprecating anything and is aiming for api compatibility etc. then I think we should probably include it in mga3, but that's just my opinion. Col OK - Since time is passing, I have committed the new version and patched a minor bug. Please can we push python-pygments to fix Bug 7906 so that ViewVC will display spec files correctly. I have changed Subject line accordingly. Thanks Submitted. -- Thomas
Re: [Mageia-dev] Freeze push: stompserver (for new ruby version)
Colin Guthrie skrev 20.1.2013 18:03: Hi, In order to fix the runtime dir stuff in stompserver, it needed a lot of work to make the package build and pass it's tests. Firstly it seems no longer able to cope with newer ruby, so I switched it to the newer stompserver_ng which has ruby 1.9+ compatibility. This needed a new dep, ruby-uuid which in turn needed ruby-macaddr which in turn needed ruby-systemu. It now builds and I've written a systemd unit for it such that it starts and stops successfully. I didn't test it further than that, but it's certainly better than the current version which even without the runtime dir problems in the package, doesn't run with our ruby. Submitted. -- Thomas
Re: [Mageia-dev] Free push: iurt
Pascal Terjan skrev 20.1.2013 01:10: This is a bug fix release: 0.6.19 - fix missing used function in emi and ulri - use unique tmpfile for dumping macros Submitted. -- Thomas
Re: [Mageia-dev] Freeze push: drupal
Funda Wang skrev 20.1.2013 19:58: ping? -- Original -- From: Funda Wangfundaw...@fundawang.name; Date: Fri, Jan 18, 2013 08:19 PM To: mageia-devmageia-dev@mageia.org; Subject: [Mageia-dev] Freeze push: drupal Hello, Could drupal 7.19 be pushed into cauldron? It is a security release only, fixing multiple vulnerabilities[1]. Regards. [1]: http://drupal.org/SA-CORE-2013-001 Submitted. -- Thomas
Re: [Mageia-dev] Grub2 vs. Grub Legacy in M3
Maurice Batey skrev 20.1.2013 19:59: On Fri, 18 Jan 2013 23:04:13 +, Barry Jackson wrote: Have any of you actually installed grub2 in Cauldron and read /usr/share/doc/grub2/README.Mageia and then actually tried it? No, only Ubuntu 12.01 Mint 13. Can you provide e.g. a URL where I can find the text you refer to, please, Barry? http://svnweb.mageia.org/packages/cauldron/grub2/current/SOURCES/README.Mageia?view=markup -- Thomas
Re: [Mageia-dev] Freeze push: Sauerbraten
Juan Luis Baptiste skrev 20.1.2013 20:04: On Fri, Jan 18, 2013 at 4:20 PM, Juan Luis Baptiste juan...@mageia.org wrote: It's a bugfix only release: Ping ? Submitted. -- Thomas
Re: [Mageia-dev] What's the point of the latest nvidia update?
Robert Wood skrev 20.1.2013 23:16: So you're saying that because v295 has been out a while you feel it's stable so you're happy to have that in the official repositories? I can kind of understand that, although in the case of nvidia you'd think they had already done the bug fixing. If that ever would be true... many times when they add support for new hardware, old support gets either broken or dropped... for example going past 304.x to 310.x or higher drops hardware support for older hw. Anyway, in the case of the latest nvidia version it certainly does have new features, because it supports newer cards. In this case, it's not a big thing because it's relatively easy for me to install, but I would think that for new users who have modern software you'd really want them to have access to it. After all M2 is the latest stable release. But yes, this is a thing we need to improve... without breaking anything in the process... The best way for now to get newer drivers is to rebuild the srpm in cauldron and install that. -- Thomas
Re: [Mageia-dev] Freeze push: eclipse-jgit
D.Morgan skrev 19.1.2013 02:34: Hi, please push eclipse-jgit, this is a fixed version that compiles against latest eclipse ( needed to fix the whole eclipse stack ) Submission errors, aborting: - eclipse-jgit-2.1.0-5.mga3: - Current or newer revision(s) already exists in core/release for cauldron: 2.1.0-5.mga3 -- Thomas
Re: [Mageia-dev] Freeze push: eclipse-jgit
Thomas Backlund skrev 19.1.2013 02:37: D.Morgan skrev 19.1.2013 02:34: Hi, please push eclipse-jgit, this is a fixed version that compiles against latest eclipse ( needed to fix the whole eclipse stack ) Submission errors, aborting: - eclipse-jgit-2.1.0-5.mga3: - Current or newer revision(s) already exists in core/release for cauldron: 2.1.0-5.mga3 Seems to have been a temp. problem... Now submitted... -- Thomas
Re: [Mageia-dev] Freeze push: eclipse-egit
D.Morgan skrev 19.1.2013 03:05: Hi, please push eclipse-egit this version compiles with new eclipse. Submitted. -- Thomas
Re: [Mageia-dev] freeze push: matio / jgraphx
D.Morgan skrev 16.1.2013 11:59: On Tue, Jan 15, 2013 at 10:50 PM, D.Morgan dmorga...@gmail.com wrote: Hi, please push matio and jgraphx in cauldron, this is scilab deps, ( needed by nothing but scilab ), w/o them we can't build scilab. Regards, D. ping Done. -- Thomas
Re: [Mageia-dev] freeze push: matio / jgraphx
D.Morgan skrev 16.1.2013 12:18: On Wed, Jan 16, 2013 at 11:15 AM, Thomas Backlund t...@mageia.org wrote: D.Morgan skrev 16.1.2013 11:59: On Tue, Jan 15, 2013 at 10:50 PM, D.Morgan dmorga...@gmail.com wrote: Hi, please push matio and jgraphx in cauldron, this is scilab deps, ( needed by nothing but scilab ), w/o them we can't build scilab. Regards, D. ping Done. -- Thomas sorry for matio, i added hdf5-devel as BR, please push it again Pushed. -- Thomas
Re: [Mageia-dev] Features
Colin Guthrie skrev 16.1.2013 17:34: 'Twas brillig, and mustafaa1...@yahoo.com at 16/01/13 15:18 did gyre and gimble: On Tuesday, January 15, 2013 05:56:34 PM Mustafa Muhammad wrote: On 01/15/2013 03:42 PM, Thomas Backlund wrote: Mustafaa Al-Hamdaani skrev 15.1.2013 14:35: Hi, Are features still accepted for Mageia 3? I have these three: 1) Enable vertical two finger scrolling by default, simple but important. 2) Desktop greeter (like kaptan of pardus or its fork for Chakra, kapudan): http://www.chakra-linux.org/wiki/index.php/Kapudan 3) catalyst-legacy for AMD cards 4xxx and before. This one depends on AMD. They have not released any legacy driver since 12.6 last summer, and that is not supporting x11-server 1.13 we use. I know, I just hoped we can ship x11-server 1.12 and 1.13 and only one of them is installed, the power consumption with the open source drivers is just insane, especially for a laptop (and the quality too). I asked yesterday and the answer was too late, but if this is technically possible, I think it will make a huge difference for a big number of Mageia users, maybe 25% of all users use those AMD cards, so please would you reconsider shipping catalyst-legacy if it is technically feasible. For such a benefit for the community, I think it worth considering (from catalyst maintainer and others). Being realistic, shipping two x servers is simply not going to happen in time. or ever... It'll need lots of extra work including more h/w detection and automatic installation of the legacy x server (assuming the user wants the proprietary drivers only, the free drivers will of course want the latest xserver instead). I feel it's just too much complication at this late stage to do this. There is way too much stuff integrated / interacting with x11-server, to sanely provide 2 of them without introducing regressions on either side... Perhaps someone can do some clever edits on the binaries to make them work with the newer xserver... Nope. No can do... that would violate the license. -- Thomas
Re: [Mageia-dev] Freeze Push: glusterfs
David Walser skrev 17.1.2013 01:07: Colin Guthrie mageia@... writes: Hi, glusterfs won't build (autoreconf bails), but also it's a new version which was never pushed (presumably because it didn't build then?) Anyway, there is an even newer version now, so I've packaged that up. +1 as the new version also fixes CVE-2012-4417. Submitted. -- Thomas
Re: [Mageia-dev] Freeze Push: glusterfs
Thomas Backlund skrev 17.1.2013 01:09: David Walser skrev 17.1.2013 01:07: Colin Guthrie mageia@... writes: Hi, glusterfs won't build (autoreconf bails), but also it's a new version which was never pushed (presumably because it didn't build then?) Anyway, there is an even newer version now, so I've packaged that up. +1 as the new version also fixes CVE-2012-4417. Submitted. http://pkgsubmit.mageia.org/uploads/failure/cauldron/core/release/20130116230917.tmb.valstar.1955/log/glusterfs-3.3.1-1.mga3/build.0.20130116231002.log -- Thomas
Re: [Mageia-dev] Freeze push: mojarra
D.Morgan skrev 16.1.2013 23:41: Hi, Please push mojarra, this is a new version ( previous one do not build with java7 ), i tested and the 2 deps of mojarra still builds OK ( no API changes ) Mojarra is important in the java stack and need to be kept, only this version will allow this. Regards, D Pushed. -- Thomas
Re: [Mageia-dev] Freeze Push: glusterfs
Colin Guthrie skrev 17.1.2013 01:17: 'Twas brillig, and David Walser at 16/01/13 23:13 did gyre and gimble: Thomas Backlund tmb@... writes: David Walser skrev 17.1.2013 01:07: +1 as the new version also fixes CVE-2012-4417. Submitted. Thanks, but it needs BuildRequires: openssl-devel added. Done that now. If you could resubmit when you can and I'll see what the next error is :D Done. -- Thomas
Re: [Mageia-dev] Freeze push: scribus
Funda Wang skrev 15.1.2013 16:06: Hello, Could scribus 1.4.2 be pushed? It features a hunspell based spellchecker, which obsoletes aspell checker. Thus, we could finally throw all aspell related pacakges in mga3, as planed. \o/ Regards. Sounds good to atleast being able to drop some deps... Pushed. -- Thomas
Re: [Mageia-dev] [changelog] [RPM] cauldron core/release mesa-9.1.0-0.git20130114.1.mga3
Charles A Edwards skrev 17.1.2013 02:19: On Wed, 16 Jan 2013 23:06:48 +0100 (CET) cjw wrote: Name: mesa Relocations: (not relocatable) Version : 9.1.0 Vendor: Mageia.Org Release : 0.git20130114.1.mga3 Build Date: Wed Jan 16 22:55:25 2013 Install Date: (not installed) Build Host: jonund.mageia.org Group : System/Libraries Source RPM: (none) Size: 5537681 License: MIT Signature : (none) Packager: cjw cjw URL : http://www.mesa3d.org What happened to tainted? Just submitted... -- Thomas
Re: [Mageia-dev] tmpfiles conversion: Thanks! Only 30 pkgs to go!
Colin Guthrie skrev 15.1.2013 12:58: Today's status update. Feel free to fix anything you fancy. Use https://wiki.mageia.org/en/System_Service_policy as a guide. I should be able to finish them off some night this week. uuidd:/var/run/uuidd I'll fix atleast this... Also some of the udev things (just need the rules moving from /etc/udev/rules.d to /usr/lib/udev/rules.d (aka %_udevrulesdir)): drbd-utils:/etc/udev/rules.d/65-drbd.rules util-linux:/etc/udev/rules.d/60-raw.rules virtualbox:/etc/udev/rules.d/virtualbox.rules virtualbox-guest-additions:/etc/udev/rules.d/vbox-additions.rules and theese... -- Thomas
Re: [Mageia-dev] freeze push: ldetect
Thierry Vignaud skrev 14.1.2013 22:31: Hi Please let in ldetect. It fixes for good the issue with max devices limit by reallocating memory when hitting the limit (mga#8320) Thx Done. -- Thomas
Re: [Mageia-dev] libvirt fails to build
Colin Guthrie skrev 13.1.2013 18:00: Hi, libvirt failed to build with mass-rebuild. I also tweaked it's tmpfiles support but it too didn't build (unsurprising as it fails in configure). I tried with both kernel-headers and kernel-source but it didn't help. Can someone with more clue here have a look? http://pkgsubmit.mageia.org/uploads/failure/cauldron/core/release/20130113155229.colin.valstar.17600/log/libvirt-1.0.1-5.mga3/build.0.20130113155250.log Feel free to remove my kernel-source BR if it's bogus. I'll take a look. -- Thomas
Re: [Mageia-dev] libvirt fails to build
Christiaan Welvaart skrev 13.1.2013 18:18: On Sun, 13 Jan 2013, Colin Guthrie wrote: libvirt failed to build with mass-rebuild. I also tweaked it's tmpfiles support but it too didn't build (unsurprising as it fails in configure). I tried with both kernel-headers and kernel-source but it didn't help. Can someone with more clue here have a look? http://pkgsubmit.mageia.org/uploads/failure/cauldron/core/release/20130113155229.colin.valstar.17600/log/libvirt-1.0.1-5.mga3/build.0.20130113155250.log This likely the same problem as: http://pkgsubmit.mageia.org/uploads/failure/cauldron/core/release/2013061923.umeabot.valstar.10551/log/connman-1.9-4.mga3/build.0.2013062158.log I tried to fix one such issue in bridge-utils, but I think the header file linux/if_bridge.h itself is wrong. It uses struct in6_addr but doesn't #include in6.h . Indeed looks that way. I've sent a patch upstream to see if they agree. I will then add it to our kernel build too. -- Thomas
Re: [Mageia-dev] libvirt fails to build
Thomas Backlund skrev 13.1.2013 20:40: Christiaan Welvaart skrev 13.1.2013 18:18: On Sun, 13 Jan 2013, Colin Guthrie wrote: libvirt failed to build with mass-rebuild. I also tweaked it's tmpfiles support but it too didn't build (unsurprising as it fails in configure). I tried with both kernel-headers and kernel-source but it didn't help. Can someone with more clue here have a look? http://pkgsubmit.mageia.org/uploads/failure/cauldron/core/release/20130113155229.colin.valstar.17600/log/libvirt-1.0.1-5.mga3/build.0.20130113155250.log This likely the same problem as: http://pkgsubmit.mageia.org/uploads/failure/cauldron/core/release/2013061923.umeabot.valstar.10551/log/connman-1.9-4.mga3/build.0.2013062158.log I tried to fix one such issue in bridge-utils, but I think the header file linux/if_bridge.h itself is wrong. It uses struct in6_addr but doesn't #include in6.h . Indeed looks that way. or not... building connman shows that was wrong: In file included from /usr/include/arpa/inet.h:22:0, from ./include/connman/inet.h:25, from src/connman.h:128, from src/tethering.c:40: /usr/include/netinet/in.h:35:5: error: expected identifier before numeric constant /usr/include/netinet/in.h:197:8: error: redefinition of 'struct in6_addr' In file included from /usr/include/linux/if_bridge.h:17:0, from src/tethering.c:38: /usr/include/linux/in6.h:30:8: note: originally defined here In file included from /usr/include/arpa/inet.h:22:0, from ./include/connman/inet.h:25, from src/connman.h:128, from src/tethering.c:40: /usr/include/netinet/in.h:238:8: error: redefinition of 'struct sockaddr_in6' In file included from /usr/include/linux/if_bridge.h:17:0, from src/tethering.c:38: /usr/include/linux/in6.h:46:8: note: originally defined here In file included from /usr/include/arpa/inet.h:22:0, from ./include/connman/inet.h:25, from src/connman.h:128, from src/tethering.c:40: /usr/include/netinet/in.h:274:8: error: redefinition of 'struct ipv6_mreq' In file included from /usr/include/linux/if_bridge.h:17:0, from src/tethering.c:38: /usr/include/linux/in6.h:54:8: note: originally defined here CC src/src_connmand-stats.o make[1]: *** [src/src_connmand-tethering.o] Error 1 make[1]: *** Waiting for unfinished jobs make: *** [all] Error 2 -- Thomas
Re: [Mageia-dev] missing tainted non-free rebuild
Thierry Vignaud skrev 13.1.2013 22:07: Hi the rebuild bot doesn't rebuild tainted non-free, which is needed: - for new toolchain (glibc/binutils/gcc) - for s/debug/debuginfo/ - for mini debuginfo - for core-tainted synchronization nonfree are rebuilt. the dual media ones (core / tainted) only is rebuilt on media last submitted ... but this is known and missing packages will be pushed after initial full rebuild is done. -- Thomas
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
[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] 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] UAS module (was: PHP treadsafe)
Frederik Himpe skrev 8.1.2013 12:04: Another example is the uas kernel module, of which I saw a complaint recently in this mailing list. This module is known to be buggy, and disabled in Debian. It's also disabled as broken upstream, in cauldron and in mga2 kernels currently in updates_testing. -- Thomas
Re: [Mageia-dev] [343016] provide need /var/run/ nscd in nscd package otherwise nscd failed to start
root-odjjhxpcy38dnm+yrof...@public.gmane.org skrev 8.1.2013 20:06:
Revision
343016
Author
nanardon
Date
2013-01-08 19:06:55 +0100 (Tue, 08 Jan 2013)
Log Message
provide need /var/run/nscd in nscd package otherwise nscd failed to start
Modified Paths
* cauldron/glibc/current/SPECS/glibc.spec
#cauldronglibccurrentSPECSglibcspec
Modified: cauldron/glibc/current/SPECS/glibc.spec
===
--- cauldron/glibc/current/SPECS/glibc.spec 2013-01-08 17:58:03 UTC (rev
343015)
+++ cauldron/glibc/current/SPECS/glibc.spec 2013-01-08 18:06:55 UTC (rev
343016)
@@ -1041,6 +1041,7 @@
install -m 644 %{SOURCE7} %{buildroot}%{_unitdir}/nscd.socket
mkdir -p %{buildroot}%{_prefix}/lib/tmpfiles.d/
install -m 644 %{SOURCE9} %{buildroot}%{_prefix}/lib/tmpfiles.d/nscd.conf
+mkdir -p %{buildroot}%{_var}/run/nscd
%endif
# These man pages require special attention
@@ -1673,6 +1674,7 @@
%{_unitdir}/nscd.service
%{_unitdir}/nscd.socket
%{_prefix}/lib/tmpfiles.d/nscd.conf
+%{_var}/run/nscd
%endif
Nope, wrong fix...
if there is something wrong, it must be fixed in SOURCE9 (nscd.conf) as
/run (to wich /var/run point at) is a tmpfs
--
Thomas
Re: [Mageia-dev] help for libreoffice packaging
Thierry Vignaud skrev 8.1.2013 22:13: Hi We need some help with building libreoffice which fails for a couple months. We follow RH packaging, tracking it regularly. They successfully packaged LO-4.0b but we fail to compile both 3.6.x 4.0. Which hints that maybe a 3rd party library has broken in the mean time. We've tried various tricks w/o much success. We could disable every failing test until it works but others have succeeded. Also some very similar errors have been seen by people on both linux bsd with prior releases too. So we need fresh eyes to look for the issue. 4.0 failure: http://pkgsubmit.mageia.org/uploads/failure/cauldron/core/release/20130107211950.tv.valstar.7795/log/libreoffice-4.0.0.0-0.beta2.mga3/build.0.20130107212026.log 3.6 failure: http://pkgsubmit.mageia.org/uploads/failure/cauldron/core/release/20130107210604.tv.valstar.29241/log/libreoffice-3.6.3.2-6.mga3/build.0.20130107210655.log Here's 4.0 3.6 branches: http://svnweb.mageia.org/packages/cauldron/libreoffice/current/ http://svnweb.mageia.org/packages/cauldron/libreoffice/branches/3.6/current/ So if someone can help (it takes one day for me to locally build). it took ~5h for me to build libreoffice-4.0.0.0-6.beta2.mga3 beta on a core i7, and x86_64 built ok ??? maybe we should limit LO build to 4 cores ? -- Thomas
