March 2012 - openSUSE Factory - openSUSE Mailing Lists

[opensuse-factory] GCC 4.7 Build Status
by Dominique Leuenberger a.k.a DimStar 26 Mar '12

26 Mar '12

Hi everybody, As you all know, coolo suggested to have a look at GCC 4.7 as the default compiler for openSUSE 12.2 (which surprisingly I have already seen as a 'fact to be' on some news pages... always nice to see how things are interpreted). For this to be successful, of course, we need to ensure that our distribution builds fine with GCC 4.7. A bunch of us joined forced and had a look at how much is currently creaking and took some efforts in fixing a bunch of those. Some small stats for fixes being sent out of my branch (home:dimstar:gcc47) which we all together used as source. Number of SRs in this state 12 new 7 review (For most here I wonder if the projects are aware of this configuration) 76 accepted 0 declined 11 revoked 5 superseded I would say quite impressive. Of course, most of the changes were rather trivial (missing include a very common one). Yet, all those packages needed to be looked at and fixed. Currently, there are 37 packages failing in home:dimstar:gcc47, which still need some work. Not all of them are forcibly related to gcc 4.7 failures (due to the logic of 'what' I branched). Some seem to be rather nasty ones (libzypp for example) and others are failing as a consequence of an error in another package (PackageKit for example fails due to libzypp's headers) Thus, together with the status overview, I would like to put out a call for help as well! Don't be shy, just chime in and fix one or two more of those packages. Dominique / DimStar -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

2 1

Re: [opensuse-factory] Tumbleweed 3.3.0-16.1 kernel does not allow install of nvidia driver
by Larry Finger 26 Mar '12

26 Mar '12

On 03/23/2012 11:58 PM, Basil Chupin wrote: > On 24/03/12 15:40, Larry Finger wrote: >> On 03/23/2012 05:51 AM, Basil Chupin wrote: >>> On 23/03/12 16:36, Larry Finger wrote: >>> >>> [pruned] >>> >>> >>>> My system has kernel 3.3 from mainline on it. >>> >>> The term "mailine" must be local jargon as I don't know what it means. >>> >>>> I could finally get access to it. I downloaded a fresh copy of the patch, >>>> applied it there, and rebuilt the x86_64 driver without any problems. A copy >>>> of that patch is attached. >>>> >>>> Larry >>> >>> To begin, I offer my most sincere apologies for writing that your patch >>> contained an error (re "x86"). After all the attempts at getting the driver >>> patched my brain was addled. I now realised that I had altered that parameter >>> when I was looking for wording which did not match the 32-bit nvidia driver I >>> needed and seeing "x64_64" changed that to "x86" and without paying attention to >>> the "i386" just before it (I did say I haven't a damn clue what I am doing). >>> >>> Anyway, the whole sheebang has beaten me into a pulp and I am giving up on the >>> whole business of getting a driver for MS #2. (MS #2 is, as far as I am >>> concerned, the worst disaster in oS history to date.) >>> >>> The new patch which you provided with your reply worked OK but when I tried to >>> compile the driver I got the same result at the finish - Could not compile the >>> driver. I attach the log file for the sake of interest. >>> >>> Many, many thanks for your help in this matter and I am sorry to have taken up >>> your time - and wasted your time with my alteration to your patch. >> >> I finally figured it out. In /lib/modules/`uname -r` are two links called >> "build" and "source". When you build your own kernel, those links are >> identical, but with the openSUSE-installed kernel, the pointers are different. >> Before 3.3, it did not matter, but now it does. There is a new patch for >> Nvidia drivers 295.20 and 295.33 at http://www.lwfinger.com/nvidia_patches/. >> >> Do not blame openSUSE for this problem - it is the fault of Nvidia for not >> updating their driver to handle the differences between kernels 3.2 and 3.3! >> >> Larry > > Many thanks, Larry, for the above. > > I have finally managed to install the (latest, 295.33) driver using the > information provided by Christian in the factory ML - see my reply to him which > I posted a minute or so ago. > > The latest nVidia driver - 295.33 released yesterday - contains the patch which > you have but the darn thing still does NOT install unless you also use the > script file mentioned in that URL given by Christian. So, for the normal user > the nVidia driver is still unusable unless they know how to overcome the problem. > > When you say, "When you build your own kernel, those links are identical, but > with the openSUSE-installed kernel, the pointers are different." and not to > blame openSUSE sounds a bit strange because it seems that openSUSE does a fiddle > with the kernel compilation. What happens with other distros using the 3.3 > kernel? are they also in the poo re the nVidia driver installation? Just asking > 'cause I don't know how these things work. It is the difference between having built the kernel, and having downloaded the kernel headers. It is not the fault of openSUSE. Larry -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

6 10

[opensuse-factory] I am asking for confirmation...
by Basil Chupin 26 Mar '12

26 Mar '12

...please that what is now available for downloading as Milestone #2 (Build 0258) is what is going to be announced on Monday (as per Kulow) as the release of Milestone #2 and which has been sent to the mirrors. Thanks for your response. BC -- The vulgar crowd always is taken by appearances, and the world consists chiefly of the vulgar. Niccolo Machiavelli -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

5 10

[opensuse-factory] Cleanup in security:apparmor and security:apparmor:factory
by Christian Boltz 25 Mar '12

25 Mar '12

Hello, security:apparmor and security:apparmor:factory contain lots of old packages. I'd like to do some cleanup there if nobody objects. (I don't want to break anything, but OTOH I see lots of *very* old packages in those repos that probably nobody needs nowadays.) Note that I started maintaining the apparmor only half a year ago, therefore I might not know everything that still needs one of the packages. @Jeff: Please reply even if you agree with the cleanup - you as the former maintainer of the apparmor package probably know better if one of the packages is still needed somewhere. Let me first give you a short overview what is in the repos right now. Note that build is disabled for most packages - I added a note to all packages with build active. * Packages in security:apparmor: (repos: SLE_10 and factory) apparmor-admin_en [2] apparmorapplet-gnome - 0.9 [1] apparmor-dbus - 1.1 [1] (SLE_10 build enabled) libapparmor1 - 2.2 (SLE_10 build enabled) apparmor-profile-editor (only a broken link to factory) apparmor - 2.5.1 (the package in openSUSE:11.4:Update is newer) (SLE 11 SP2 also uses this version AFAIK) apparmor_2_6 - 2.6.1 * Packages in security:apparmor:factory (repos: 11.4, 12.1, factory, tumbleweed) apparmor-admin_en [2] (build active, but has a broken link) apache2-mod_apparmor - 2.0.2 tomcat_apparmor - 2.0.2 apparmor-dbus 2.3 [3] apparmor-parser - 2.3.1 [3] apparmor-profiles - 2.3 [3] apparmor-utils - 2.3 [3] libapparmor1 - 2.3 [3] pam_apparmor - 2.3 [3] apparmorapplet-gnome - 0.9 apparmor-profile-editor - 0.9.1 apparmor - 2.7.2 - that's the latest available packaged version (and building is of course enabled) If nobody objects within a week, I will - delete all pre-2.5 packages without any active repo - delete apparmor-admin_en - rename security:apparmor apparmor (2.5.1) to apparmor-2_5 and include the changes from 11.4:Update - move the active development to security:apparmor instead of security:apparmor:factory (and send a changedevelrequest for factory) - add 11.4, 12.1 and tumbleweed repos in security:apparmor - drop security:apparmor:factory (it will be empty after applying the changes above) In other words: after the cleanup, there will only be security:apparmor with the following packages: - apparmor-dbus 1.1 and libapparmor1 2.2 because they have the SLE_10 build enabled - apparmor_2.5 (with build disabled and the changes from 11.4:Update included) - apparmor_2.6 (with build disabled) - and of course the apparmor package (currently 2.7.2) with the latest version If you still need one of the packages I'm planning to delete, please speak up now - or remain silent forever ;-) Regards, Christian Boltz [1] I'm not sure to which apparmor versions those packages belong, however I'm quite sure they belong to version 2.4 or older (the apparmor-* packages were merged to a single apparmor package in 2.5) [2] outdated, now part of the Security Guide, and Karl Eichwalder wrote on opensuse-doc that I "probably can delete it" [3] the 2.3 / 2.3.1 packages were included in openSUSE 11.1, 11.2 and 11.3. Those releases are out of maintenance (with the exception of evergreen) and the packages in 11:3:Update are newer. Therefore I don't think it makes sense to keep them in security:apparmor. (If evergreen needs a fix for the apparmor packages, I'll of course help.) -- [18:16] <psankar> suseROCKs, sorry. didnt follow the conversation [...] [18:16] <suseROCKs> psankar, content is irrelevnt. You are simply here to nod yes to everyting I say with total and fervent agreement. [from #opensuse-project] -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

2 1

[opensuse-factory]
by Παναγιώτης Πιτέλος 25 Mar '12

25 Mar '12

-- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

1 0

[opensuse-factory] KDE 4.8 is now landing in openSUSE:Tumbleweed
by Greg KH 24 Mar '12

24 Mar '12

After 2+ weeks of messing with KDE 4.8 to get it to build and work properly in openSUSE:Tumbleweed:Testing, all seems good, so it's starting to show up, slowly, in openSUSE:Tumbleweed this weekend. I'm announcing this here as I know a lot of people mix the KDE:4.8 repo with Tumbleweed on their systems, and that might cause problems if the KDE repo is allowed to remain as packages get duplicated. So, if you have KDE:48 in your repo list, I strongly suggest you remove it in the next few days, as I can not support mixing the two at all, sorry. Note, if anyone has any problems with the KDE packages in Tumbleweed, please let me know. Odds are I messed something up, not the KDE developers. thanks, greg k-h -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

1 0

[opensuse-factory] Tumbleweed 3.3.0-16.1 kernel does not allow install of nvidia driver
by Patrick Shanahan 24 Mar '12

24 Mar '12

12.1 tumbleweed x86_64 kernel-desktop-3.3.0-16.1.x86_64 trying to update nvidia driver with new kernel fails sh ./NVIDIA-Linux-x86_64-295.20.run -a -K fails, log below : ~ # rpm -qa *kernel* |grep 3.3 kernel-desktop-3.3.0-16.1.x86_64 kernel-devel-3.3.0-16.1.noarch kernel-source-3.3.0-16.1.noarch kernel-desktop-devel-3.3.0-16.1.x86_64 nvidia-installer.log: http://wahoo.no-ip.org/~pat/nvidia-installer.log -- (paka)Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 http://en.opensuse.org openSUSE Community Member Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

5 13

[opensuse-factory] nothing provides libxcrypt
by Ilya Chernykh 23 Mar '12

23 Mar '12

Hi! In Factory I heve the following: nothing provides libxcrypt Is there a replacement for libxcrypt? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

2 2

[opensuse-factory] xcb/xcb_keysyms.h gone in Factory?
by Greg KH 23 Mar '12

23 Mar '12

I can't seem to find where the xcb/xcb_keysyms.h file went in Factory, what package did it move to? I see that the xcb packages got split up, but this file seems to have disappeared. The i3 window manager seems to need it to build properly, as it's failing in Factory, and I would like to fix it up. Any hints? thanks, greg k-h -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

2 2

[opensuse-factory] nothing provides libnetcdf-devel
by Ilya Chernykh 23 Mar '12

23 Mar '12

is there a substitution? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

2 2