December 2013 - openSUSE Factory - openSUSE Mailing Lists

[opensuse-factory] nVidia repo for 13.1 missing?
by Jim Henderson 19 Dec '13

19 Dec '13

A few days ago, the repository hosted by nVidia for their drivers for oS 13.1 was made available, but the directory seems to have gone missing - anyone know what happened, or who to contact/notify? We've had a couple questions on the forums about this. Thanks. Jim -- Jim Henderson Please keep on-topic replies on the list so everyone benefits -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

15 31

[opensuse-factory] Upcoming changes to Enlightenment (e16, e17, e18) + libraries, Includes package add remove and rename
by Simon 19 Dec '13

19 Dec '13

Hi All, before everyone heads off for Christmas / summer / winter breaks, i'd like to give a heads up of some changes coming to openSUSE:factory over the next few weeks we will try to limit breakages however some temporary issues may be unavoidable. Firstly the existing enlightenment package will be removed and replaced with one called e16, this is the only change for e16 users i'll get back to whats happening with the enlightenment package in a little bit. The biggest change will be to the enlightenment foundation libraries (efl) used by e17, e18 and terminology. As of efl 1.8 all the components of the efl with the exception of elementary are shipped as one source tar and are built together as such we have added one new package efl and will be removing the following packages, eina, eet, evas, eio, emotion, efreet, e_dbus, embryo, edje and eeze. As not all the extra modules / themes are available with e18 and because it requires compositing to be enabled we have had some requests to keep e17 around. For now we will be keeping e17 pretty much as is but probably at version 0.17.6 instead of 0.17.3 unless it is found unusable by a number of people, it will also build from the new efl package rather then the older split libraries. Enlightenment e18 will be built in the enlightenment package, this is because upstream have indicated they would like to do a new release at least every year possibly less and i don't want to change the package name that often. I will try and come up with a way for e17.3 in 13.1 to automaticlly update to the new enlightenment e18 package that doesn't ask people who are using e17.6 from 13.2 to update, if someone could help with that it would be great, i don't know how to do it. Previously themes were named e-theme-* and modules e-module-* as themes and modules need to be built against the right version of enlightenment the package naming will change to e17-module-* and e17-theme-* for e17 and enlightenment-module-* and enlightenment-theme-*, e17 users who use terminology will also need both the e17 and enlightenment theme as e18 and later themes are used by the libraries as well Currently we don't plan to keep e18 around when e19 etc come out like we have with e16 and e17. Summary of changes: Stage 1 (Basics): * Add efl * replace existing enlightenment package with e16) Stage 2 (core components) * Update elementary, terminology and e17 to use efl rather then older libs. * add new enlightenment package Stage 3 (everything else) * replace / add modules, themes and branding * update other packages i forgot about. * remove old libraries Almost all the changes have already been made in the X11:Enlightenment:Factory Thanks for your time Simon (Simotek) Maintainer for enlightenment on openSUSE -- 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] Playing again with rings
by Stephan Kulow 19 Dec '13

19 Dec '13

Hi, Trying to find more options for the staging workflow, I played again with the ring idea. The rings I have so far are: openSUSE:Factory:Build the minimal bootstrap cycle gcc,binutils, ... (106 packages) openSUSE:Factory:Core packages required for DVD with minimalx installation (976 packages). This DVD is 522 MB at the moment and we have already openQA support for running the minimalx installation on it. openSUSE:Factory:MainDesktops packages required to build GNOME and KDE Live media, this adds to the above alot of the desktop stuff including java and libreoffice (817 packages) The next ring I'd add is a project that builds the x86_64 DVD. This will include quite some packages (at least 1050 are needed to build it right now). So we had ~3000 packages in rings - the 3800 packages in factory not in one of these rings would be in a "nice to have" ring. The idea would be then: - packages in "nice to have" don't get any staging - packages in rings need to build the rings up. If it's a :Build package, it first needs to prove :Build is green, then build :Core's minimal DVD, test it in openqa, then MainDesktop Live CDs, test, then DVD, test -> profit. Every package only has to prove it's greenness for the state it submitted to. For longer running projects we need to rebase, but not in the usual case. The rest of the ideas from Michal's staging concept still apply of course. E.g. we need to find a way to group the packages *before* we create the staging projects. Greetings, Stephan -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

3 3

[opensuse-factory] OpenSUSE 13.1 on ThinkPad X60s
by Thorolf Godawa 18 Dec '13

18 Dec '13

Hi everybody, it's not "really" factory anymore, but I think it should work, because I don't have the problems with 12.1 and I havn't found any solution right now. I'm trying to install openSUSE 13.1 on a ThinkPad X60s (CoreDuo, Intel 950 graphics, Intel 3945ABG wifi, SanDisk 128GB SSD). The installation went through mostly fine, all hardware was detected correctly but I was not able to establish a wifi-connection during installation (shows SSIDs for available APs, but does not get an IP), so I went for cable to finish the installation including all available updates. On next reboot, it takes quite long (>60s) to go over the Grub showing the boot menu and even worse, the system is not booting into runlevel 5 at all, last message seen is "Started SuSEfirewall2 phase 2". I can change to an other console, after connecting a cable I have working network and I can start XFCE4 manually from there. Now I am also able to connect to my wifi-network, using the NetworkManager. I can get over the "Started SuSEfirewall2 phase 2" if I switch the network from NetworkManager to ipup, but then I'm not able to get a Wifi connection anymore (only SSIDs viewable, but no IP-connection). Any idea what I can check to solve this problem? I'm using 13.1, because it should be a "evergreen" version, while I was a SuSE user for long time, I stopped using it some time ago, because I was not willing to do frequent distribution upgrades, so "evergreen" seems to be a good option for me. -- kind regards, Thorolf -- 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] up zypper/libzypp wants to remove YaST
by Felix Miata 17 Dec '13

17 Dec '13

Is there an ETA on this not happening any more? I don't see a bug opened on it. -- "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/ -- 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] upgrade of xorg-x11-server breaks NVidia 331.20 driver
by Sid Boyce 17 Dec '13

17 Dec '13

Bug #855541 submitted. The module gets loaded. # lsmod|grep nvidia nvidia 10609843 0 I also added this to /etc/X11/xorg.conf but it still fails the same way:- Section "ServerFlags" Option "IgnoreABI" "true" EndSection [ 6969.136] Loading extension GLX [ 6969.136] (II) LoadModule: "nvidia" [ 6969.136] (II) Loading /usr/lib64/xorg/modules/drivers/nvidia_drv.so [ 6969.137] (II) Module nvidia: vendor="NVIDIA Corporation" [ 6969.137] compiled for 4.0.2, module version = 1.0.0 [ 6969.137] Module class: X.Org Video Driver [ 6969.137] ================ WARNING WARNING WARNING WARNING ================ [ 6969.137] This server has a video driver ABI version of 15.0 that is not supported by this NVIDIA driver. Please check http://www.nvidia.com/ for driver updates or downgrade to an X server with a supported driver ABI. [ 6969.137] ================================================================= [ 6969.137] (WW) NVIDIA: The driver will continue to load, but may behave strangely. [ 6969.137] (WW) NVIDIA: This server has an unsupported input driver ABI version (have 20.0, need < 20.0). The driver will continue to load, but may behave strangely. [ 6969.137] (II) NVIDIA dlloader X Driver 331.20 Wed Oct 30 17:16:53 PDT 2013 [ 6969.137] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs [ 6969.137] (++) using VT number 7 <STUFF DELETED> [ 6970.042] (II) NVIDIA: Using 3072.00 MB of virtual memory for indirect memory [ 6970.042] (II) NVIDIA: access. [ 6970.045] (II) NVIDIA(0): ACPI: failed to connect to the ACPI event daemon; the daemon [ 6970.045] (II) NVIDIA(0): may not be running or the "AcpidSocketPath" X [ 6970.045] (II) NVIDIA(0): configuration option may not be set correctly. When the [ 6970.045] (II) NVIDIA(0): ACPI event daemon is available, the NVIDIA X driver will [ 6970.045] (II) NVIDIA(0): try to use it to receive ACPI event notifications. For [ 6970.045] (II) NVIDIA(0): details, please see the "ConnectToAcpid" and [ 6970.045] (II) NVIDIA(0): "AcpidSocketPath" X configuration options in Appendix B: X [ 6970.045] (II) NVIDIA(0): Config Options in the README. [ 6970.051] (II) NVIDIA(0): Setting mode "CRT-1:nvidia-auto-select" [ 6970.097] Loading extension NV-GLX [ 6970.102] (EE) [ 6970.102] (EE) Backtrace: [ 6970.102] (EE) 0: /usr/bin/Xorg (xorg_backtrace+0x48) [0x58a268] [ 6970.102] (EE) 1: /usr/bin/Xorg (0x400000+0x18df59) [0x58df59] [ 6970.102] (EE) 2: /lib64/libpthread.so.0 (0x7f57adf58000+0xf9f0) [0x7f57adf679f0] [ 6970.102] (EE) 3: /usr/lib64/xorg/modules/drivers/nvidia_drv.so (0x7f57a7b40000+0x4e427f) [0x7f57a802427f] [ 6970.102] (EE) 4: /usr/lib64/xorg/modules/drivers/nvidia_drv.so (0x7f57a7b40000+0x4eb501) [0x7f57a802b501] [ 6970.102] (EE) 5: /usr/bin/Xorg (AddScreen+0x71) [0x43b6b1] [ 6970.102] (EE) 6: /usr/bin/Xorg (InitOutput+0x3df) [0x47c58f] [ 6970.102] (EE) 7: /usr/bin/Xorg (0x400000+0x3f06b) [0x43f06b] [ 6970.102] (EE) 8: /lib64/libc.so.6 (__libc_start_main+0xf5) [0x7f57acba9b25] [ 6970.102] (EE) 9: /usr/bin/Xorg (0x400000+0x2a7fe) [0x42a7fe] [ 6970.102] (EE) [ 6970.102] (EE) Segmentation fault at address 0x18 [ 6970.102] (EE) Fatal server error: [ 6970.103] (EE) Caught signal 11 (Segmentation fault). Server aborting [ 6970.103] (EE) [ 6970.103] (EE) Please consult the The X.Org Foundation support at http://wiki.x.org Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Senior Staff Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

6 12

[opensuse-factory] [HEADSUP] headless mode for openjdk
by Michal Vyskocil 16 Dec '13

16 Dec '13

Hi, as Fedora have implemented one of my long standing items in TODO [1] - headless mode [2] for openjdk, I've did the same in Java:openjdk6:Factory. The java-1_7_0-openjdk is now almost empty as it contains only a few so files libjsoundalsa.so libpulse-java.so libsplashscreen.so libmawt.so and the rest is in java-1_7_0-openjdk-headless, which does not now require anything like X, alsa or pulseaudio, so fits better to servers. [1] https://lists.fedoraproject.org/pipermail/java-devel/2013-October/004975.ht… [2] https://fedoraproject.org/wiki/Changes/HeadlessJava Regards Michal Vyskocil

1 0

[opensuse-factory] discussing timeline
by Jos Poortvliet 16 Dec '13

16 Dec '13

Hi all, I send a mail about the consequences of implementing (some of) our proposals in a reasonable time frame to the project ML, see http://lists.opensuse.org/opensuse-project/2013-12/msg00287.html Please reply there ;-) Hugs, J

1 0

[opensuse-factory] Are openqa tests broken/stuck
by doiggl＠velocitynet.com.au 16 Dec '13

16 Dec '13

Hello, l:46 mark the openqa seems to be stuck. Are openqa tests broken/stuck, can it be fixed ? --Glenn http://openqa.opensuse.org/openqa/video/openSUSE-Factory-NET-x86_64-Build07… -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

3 2

[opensuse-factory] Policies, or why it's good to know how to change things
by Antonio Larrosa 14 Dec '13

14 Dec '13

Hi all, We got lots of feedback from you all, also on the process. Many did not appreciate the long and complicated emails. We discussed this in the team and Tomáš Chvátal told us how Gentoo shares a nicely documented change process with Python and Debian already. Essentially, they use a standardized document which ensures that whenever something has to be discussed, all information is there right at the start. This shortens discussions, avoids bikeshedding (see [1]) and afterwards you have a nice stash of proper proposals in archive. The proposal is essentially based off of the Python document, simplified and adapted to openSUSE. It does not change how decisions are made or by who, just speeds up the process, keeps the discussions clean and documents their results thus avoiding future flames. We think it would be great for openSUSE to adapt them. Attached to this mail there's a draft with a recursive OSEP in the proper, proposed form, let us know what you think ;-) Note that the draft we made only proposes to use this for big changes to our process, not technical things like replacing sysvinit with systemd. FYI, Agustin has written on our team blog about the proposals, giving an overview of what's out: http://lizards.opensuse.org/?p=10230 -- The openSUSE Team [1] http://blog.jospoortvliet.com/2011/09/bikeshedding-and-cls.html

14 39