Re: [Mageia-dev] [changelog] [RPM] cauldron core/release llvm-3.2-1.mga3
Le lundi 24 décembre 2012 12:49:23 mitya a écrit : [...] mitya mitya 3.2-1.mga3: + Revision: 334668 - Fix build - Cleanup, split apidocs to separate package + kamil kamil - get rid of %clean - remove P1, merged upstream - update Version and Release tago to 3.2 and 1 - new version 3.2 Can you also rebuild packages depending of llvm ? Regards, -- Mageia Contributor
Re: [Mageia-dev] [changelog] [RPM] cauldron core/release llvm-3.2-1.mga3
On Sat, 29 Dec 2012, Balcaen John wrote: Le lundi 24 décembre 2012 12:49:23 mitya a écrit : [...] mitya mitya 3.2-1.mga3: + Revision: 334668 - Fix build - Cleanup, split apidocs to separate package + kamil kamil - get rid of %clean - remove P1, merged upstream - update Version and Release tago to 3.2 and 1 - new version 3.2 Can you also rebuild packages depending of llvm ? AFAICT neither mesa 9.0 nor 9.1 (snapshots) build with llvm 3.2. Instead, the r600 llvm branch needs to be used for mesa 9.1, which is not in sync with the 3.2 release. Christiaan
Re: [Mageia-dev] [changelog] [RPM] cauldron core/release llvm-3.2-1.mga3
On 29.12.2012 12:19, Christiaan Welvaart wrote: On Sat, 29 Dec 2012, Balcaen John wrote: Le lundi 24 décembre 2012 12:49:23 mitya a écrit : [...] mitya mitya 3.2-1.mga3: + Revision: 334668 - Fix build - Cleanup, split apidocs to separate package + kamil kamil - get rid of %clean - remove P1, merged upstream - update Version and Release tago to 3.2 and 1 - new version 3.2 Can you also rebuild packages depending of llvm ? AFAICT neither mesa 9.0 nor 9.1 (snapshots) build with llvm 3.2. Instead, the r600 llvm branch needs to be used for mesa 9.1, which is not in sync with the 3.2 release. Christiaan There is also a problem with opengtl, upstream supports only LLVM 3.0 and 3.1 (nothing new in their Version Control). But there were promises to fix these packages (there was a code reorganization in LLVM 3.2, changed file names etc.). If moving software to llvm 3.2 isn't simply possible, then could we fork our llvm package and produce llvm31 and llvm (= 3.2)? Kamil
Re: [Mageia-dev] [changelog] [RPM] cauldron core/release llvm-3.2-1.mga3
On Sat, 29 Dec 2012 12:26:44 +0100 Kamil Rytarowski n...@gmx.com wrote: On 29.12.2012 12:19, Christiaan Welvaart wrote: On Sat, 29 Dec 2012, Balcaen John wrote: Le lundi 24 décembre 2012 12:49:23 mitya a écrit : [...] mitya mitya 3.2-1.mga3: + Revision: 334668 - Fix build - Cleanup, split apidocs to separate package + kamil kamil - get rid of %clean - remove P1, merged upstream - update Version and Release tago to 3.2 and 1 - new version 3.2 Can you also rebuild packages depending of llvm ? AFAICT neither mesa 9.0 nor 9.1 (snapshots) build with llvm 3.2. Instead, the r600 llvm branch needs to be used for mesa 9.1, which is not in sync with the 3.2 release. Christiaan There is also a problem with opengtl, upstream supports only LLVM 3.0 and 3.1 (nothing new in their Version Control). But there were promises to fix these packages (there was a code reorganization in LLVM 3.2, changed file names etc.). If moving software to llvm 3.2 isn't simply possible, then could we fork our llvm package and produce llvm31 and llvm (= 3.2)? This is a bit off topic, but if it's possible and we decide to provide llvm31, then please do the importing right/properly and do a 'svn cp' from correct llvm revision in SVN to keep revision history etc etc.
Re: [Mageia-dev] RFC: dropping prebuilt broadcom-wl drivers
On Fri, 28 Dec 2012 23:45:47 +0100, Wolfgang Bornath wrote: never with network manager That's interesting. As I said earlier, NetworkManager was the only way I could get WiFi working on Mageia-3-Alpha2. I rather like its interface, too. So if some subsequent s/w update upsets Mageia-2's WiFi again I shall try NetworkManager there, too. -- /\/\aurice
[Mageia-dev] ANN / RFT: glibc-2.17
Hi, I'm thinking of using glibc-2.17 in Mageia 3, and I have been running it for 12+ hours here doing initial tests and it seems to work ok... So I'm asking for more tests from those brave enough :) NOTE! You must be prepared that you might have to downgrade back to 2.16 either manually, or by doing a full reinstall if we find much problems with the 2.17 tests. Now with the warning out of the way, here is the fun: http://tmb.mine.nu/Mageia/Cauldron/testing/glibc-2.17/ http://tmb2.mine.nu/Mageia/Cauldron/testing/glibc-2.17/ - urpmi will complain about missing signatures, but just ansver yes if you want to help testing... If tests work out nicely, I'll push it to core/release in some days... Arnaud, can you check the arm part if you have time ? the work is stored here for now: http://svnweb.mageia.org/packages/cauldron/glibc/branches/2.17/ http://svnweb.mageia.org/packages/cauldron/locales/branches/2.17/ -- Thomas
[Mageia-dev] unreadable subject in submission error messages
Enumerating the whole list of binary packages whose submission was rejected make the resulting mail subject unreadable, as soon as there is more than one subpackage. For instance, the lastest one I received was: Subject: Upload failed for lib64ini_config-devel-0.7.0-1.mga3.x86_64.rpm libref_array-devel-0.1.3-1.mga3.i586.rpm lib64path_utils-devel-0.2.1-1.mga3.x86_64.rpm lib64basicobjects0-0.1.0-1.mga3.x86_64.rpm ding-libs-debug-0.2.91-1.mga3.i586.rpm libref_array1-0.1.3-1.mga3.i586.rpm libini_config3-0.7.0-1.mga3.i586.rpm ding-libs-debug-0.2.91-1.mga3.x86_64.rpm libdhash1-0.4.3-1.mga3.i586.rpm lib64ini_config3-0.7.0-1.mga3.x86_64.rpm libini_config-devel-0.7.0-1.mga3.i586.rpm lib64ref_array-devel-0.1.3-1.mga3.x86_64.rpm lib64ref_array1-0.1.3-1.mga3.x86_64.rpm libcollection2-0.6.2-1.mga3.i586.rpm lib64basicobjects-devel-0.1.0-1.mga3.x86_64.rpm lib64path_utils1-0.2.1-1.mga3.x86_64.rpm lib64collection2-0.6.2-1.mga3.x86_64.rpm libpath_utils-devel-0.2.1-1.mga3.i586.rpm libbasicobjects-devel-0.1.0-1.mga3.i586.rpm libbasicobjects0-0.1.0-1.mga3.i586.rpm lib64dhash-devel-0.4.3-1.mga3.x86_64.rpm lib64dhash1-0.4.3-1.mga3.x86_64.rpm libdhash-devel-0.4.3-1.mga3.i586.rpm libcollection-devel-0.6.2-1. mga3.i586.rpm libpath_utils1-0.2.1-1.mga3.i586.rpm lib64collection-devel-0.6.2-1.mga3.x86_64.rpm Using either the source package name, or even just submission error would work better. -- BOFH excuse #262: Our POP server was kidnapped by a weasel.
[Mageia-dev] Mesa 9.1 in mga3 or revert to llvm 3.1?
hi, Since Mesa 9.0 apparently doesn't build with llvm 3.2 we are getting many build failures because mesa packages depend on libllvm3.1 which isn't available. I have llvm 3.2pre+amdgpu and mesa 9.1pre ready to upload which should fix those build problems. Gnome-shell and armagetron seem to work OK with them, for neverball I get https://bugs.freedesktop.org/show_bug.cgi?id=58839 but it still works (maybe with a lower framerate). Mesa 9.1 release is scheduled for february 2013 AFAIK. So is there a reason why I should not upload these two packages? Christiaan
Re: [Mageia-dev] tomcat 5
D.Morgan wrote: On Fri, Dec 28, 2012 at 12:27 AM, Pascal Terjan pter...@gmail.com wrote: Tomcat 5 is no longer maintained (and will be removed from upstream mirrors in a few days). I guess we want to remove it from cauldron, but just wanted a confirmation :) I was looking at (currently failing to build) apache-jasper-5.5.28 and noticed it can die with tomcat5 if you make sure all rpms that have it as BR still build this is OK for me D. There are also several security issues with the tomcat packages, and updates are needed: https://bugs.mageia.org/show_bug.cgi?id=8307 D Morgan - I e-mailed you about security issues in java packages and others you maintain last week, did you get it?
Re: [Mageia-dev] MGA2 - weird usbkey udisksd error
Johnny A. Solbu wrote: On Friday 28. December 2012 16.18, Johnny A. Solbu wrote: The udisksd mesages floods in for as long as the usb key is plugged in to the system, and stops only when I remove the key. If I create an empty «/etc/crypttab» file, the flooding stops, and the key eventually show up after perhaps a minute. Does blacklisting the uas module and rebooting help? I have an external USB drive that worked fine in mga1 and didn't work at all in mga2 until I did that.
Re: [Mageia-dev] ANN / RFT: glibc-2.17
On Saturday, December 29, 2012 06:10:06 AM Thomas Backlund wrote: Hi, I'm thinking of using glibc-2.17 in Mageia 3, and I have been running it for 12+ hours here doing initial tests and it seems to work ok... So I'm asking for more tests from those brave enough :) NOTE! You must be prepared that you might have to downgrade back to 2.16 either manually, or by doing a full reinstall if we find much problems with the 2.17 tests. Now with the warning out of the way, here is the fun: http://tmb.mine.nu/Mageia/Cauldron/testing/glibc-2.17/ http://tmb2.mine.nu/Mageia/Cauldron/testing/glibc-2.17/ - urpmi will complain about missing signatures, but just ansver yes if you want to help testing... If tests work out nicely, I'll push it to core/release in some days... Arnaud, can you check the arm part if you have time ? the work is stored here for now: http://svnweb.mageia.org/packages/cauldron/glibc/branches/2.17/ http://svnweb.mageia.org/packages/cauldron/locales/branches/2.17/ -- Thomas Seems to work here on a 64bit Virtualbox -- Best regards Thomas Spuhler signature.asc Description: This is a digitally signed message part.
[Mageia-dev] Need help on cyrus-imapd
We use the below file on cyrus-imapd, taken from Fedora cyr_systemd_helper However, it uses the runuser command which dropped in the latest coreutils and as a result the cyrus-imapd doesn't start anymore. I know Colin has done some work on coreutils in mga2 https://www.mageia.org/pipermail/mageia-dev/2012-June/016135.html Would you be able to help? -- Best regards Thomas Spuhler signature.asc Description: This is a digitally signed message part.
Re: [Mageia-dev] Problem with missing signatures
On Sat, Dec 29, 2012 at 6:49 PM, Kamil Rytarowski n...@gmx.com wrote: Hello! Could we add a trigger to prevent unsigned packages from being uploaded? I've faced again bunch of unsigned packages.. and when I was trying to rebuild plexus-i18n against missing signature, with bumping the release - the build system said it's already built with that version [1]. How is it possible? I have checked the history of this package.. and it was never released as the version in the build system. Am I missing something? Was there an attack and a package injection? Kamil [1] http://svnweb.mageia.org/packages/cauldron/plexus-i18n/current/SPECS/plexus-i18n.spec?r1=268801r2=335589 It seems someone manually uploaded the package on December 1st, after building it on a machine named karamel, this seems to be dmorgan's machine
Re: [Mageia-dev] Problem with missing signatures
On 29.12.2012 20:11, Pascal Terjan wrote: On Sat, Dec 29, 2012 at 6:49 PM, Kamil Rytarowski n...@gmx.com wrote: Hello! Could we add a trigger to prevent unsigned packages from being uploaded? I've faced again bunch of unsigned packages.. and when I was trying to rebuild plexus-i18n against missing signature, with bumping the release - the build system said it's already built with that version [1]. How is it possible? I have checked the history of this package.. and it was never released as the version in the build system. Am I missing something? Was there an attack and a package injection? Kamil [1] http://svnweb.mageia.org/packages/cauldron/plexus-i18n/current/SPECS/plexus-i18n.spec?r1=268801r2=335589 It seems someone manually uploaded the package on December 1st, after building it on a machine named karamel, this seems to be dmorgan's machine Thank you Pascal for your reply, so it was injected (in other words manually uploaded). I may understand that in some circumstances there is a need to do manual operations over our buildservers, but please for the sake of security and credibility of Mageia prohibit uploading locally built packages into the outside world, servers! Without it a user or developer cannot see if a local mirror (or someone in-the-middle) is injecting Trojan packages or not.
Re: [Mageia-dev] tomcat 5
On Sat, Dec 29, 2012 at 7:06 PM, David Walser luigiwal...@yahoo.com wrote: D.Morgan wrote: On Fri, Dec 28, 2012 at 12:27 AM, Pascal Terjan pter...@gmail.com wrote: Tomcat 5 is no longer maintained (and will be removed from upstream mirrors in a few days). I guess we want to remove it from cauldron, but just wanted a confirmation :) I was looking at (currently failing to build) apache-jasper-5.5.28 and noticed it can die with tomcat5 if you make sure all rpms that have it as BR still build this is OK for me D. There are also several security issues with the tomcat packages, and updates are needed: https://bugs.mageia.org/show_bug.cgi?id=8307 D Morgan - I e-mailed you about security issues in java packages and others you maintain last week, did you get it? just answered you :)
Re: [Mageia-dev] Problem with missing signatures
On Sat, Dec 29, 2012 at 7:44 PM, Kamil Rytarowski n...@gmx.com wrote: On 29.12.2012 20:11, Pascal Terjan wrote: On Sat, Dec 29, 2012 at 6:49 PM, Kamil Rytarowski n...@gmx.com wrote: Hello! Could we add a trigger to prevent unsigned packages from being uploaded? I've faced again bunch of unsigned packages.. and when I was trying to rebuild plexus-i18n against missing signature, with bumping the release - the build system said it's already built with that version [1]. How is it possible? I have checked the history of this package.. and it was never released as the version in the build system. Am I missing something? Was there an attack and a package injection? Kamil [1] http://svnweb.mageia.org/packages/cauldron/plexus-i18n/current/SPECS/plexus-i18n.spec?r1=268801r2=335589 It seems someone manually uploaded the package on December 1st, after building it on a machine named karamel, this seems to be dmorgan's machine Thank you Pascal for your reply, so it was injected (in other words manually uploaded). I may understand that in some circumstances there is a need to do manual operations over our buildservers, but please for the sake of security and credibility of Mageia prohibit uploading locally built packages into the outside world, servers! Without it a user or developer cannot see if a local mirror (or someone in-the-middle) is injecting Trojan packages or not. This is not supposed to happen but can be done temporarily by sysadmins (usually for some kind of bootstraping when you need the package to be on the mirrors to be able to upload it or another one it requires). It seems it was the case but dmorgan forgot to upload the correct package afterwards. We should definitely improve things so that this is logged and packages get signed when uploaded manually by admins.
Re: [Mageia-dev] Problem with missing signatures
On Sat, Dec 29, 2012 at 7:49 PM, Kamil Rytarowski n...@gmx.com wrote: Hello! Could we add a trigger to prevent unsigned packages from being uploaded? I've faced again bunch of unsigned packages.. and when I was trying to rebuild plexus-i18n against missing signature, with bumping the release - the build system said it's already built with that version [1]. How is it possible? I have checked the history of this package.. and it was never released as the version in the build system. Am I missing something? Was there an attack and a package injection? Kamil [1] http://svnweb.mageia.org/packages/cauldron/plexus-i18n/current/SPECS/plexus-i18n.spec?r1=268801r2=335589 fixed
Re: [Mageia-dev] File Commander Linux repo configuration
On 2012-12-28 12:06 (GMT+0100) Florian Hubold composed: You should be able to install it via urpmi http://silk.apana.org.au/pub/fcl/filecommander-2.40-release1_fedora10.i386.rpm or urpmi http://silk.apana.org.au/pub/fcl/filecommander-2.40-release1_fedora10.x86_64.rpm for x86_64 system, but that doesn't mean that the package will necessarily work. It pulled in also lib64cairomm, lib64pangomm, lib64atkmm lib64gtkmm, and works, as I expected, since such things shouldn't differ materially if at all among Fedora, openSUSE Mageia. You can't add a Fedora/RHEL style repo as an urpmi repo, and as it only contains one package, which receives no updates, this is even quite useless. It may go a very long time between updates, but it does happen now then. It was originally developed a couple of decades ago, so doesn't really need a lot of updating. -- The wise are known for their understanding, and pleasant words are persuasive. Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/
Re: [Mageia-dev] tomcat 5
D.Morgan wrote: On Sat, Dec 29, 2012 at 7:06 PM, David Walser luigiwal...@yahoo.com wrote: D.Morgan wrote: On Fri, Dec 28, 2012 at 12:27 AM, Pascal Terjan pter...@gmail.com wrote: Tomcat 5 is no longer maintained (and will be removed from upstream mirrors in a few days). I guess we want to remove it from cauldron, but just wanted a confirmation :) I was looking at (currently failing to build) apache-jasper-5.5.28 and noticed it can die with tomcat5 if you make sure all rpms that have it as BR still build this is OK for me D. There are also several security issues with the tomcat packages, and updates are needed: https://bugs.mageia.org/show_bug.cgi?id=8307 D Morgan - I e-mailed you about security issues in java packages and others you maintain last week, did you get it? just answered you :) Thanks, I guess I ended up in your Spam folder again. Hopefully you got my reply :o)
Re: [Mageia-dev] Problem with missing signatures
On 29.12.2012 21:03, D.Morgan wrote: On Sat, Dec 29, 2012 at 7:49 PM, Kamil Rytarowski n...@gmx.com wrote: Hello! Could we add a trigger to prevent unsigned packages from being uploaded? I've faced again bunch of unsigned packages.. and when I was trying to rebuild plexus-i18n against missing signature, with bumping the release - the build system said it's already built with that version [1]. How is it possible? I have checked the history of this package.. and it was never released as the version in the build system. Am I missing something? Was there an attack and a package injection? Kamil [1] http://svnweb.mageia.org/packages/cauldron/plexus-i18n/current/SPECS/plexus-i18n.spec?r1=268801r2=335589 fixed Thank you
