March 2013 - openSUSE Factory - openSUSE Mailing Lists

[opensuse-factory] after dup fro 12.2 to 12.3 grub menu still 12.2
by Daniele 05 Apr '13

05 Apr '13

Hi guys, I'm not a big fun of zypper dup but I did it ! New system is up and running but grub menu still show 12.2 instead of 12.3. Under Yast, boot loader options: Distributor and Default section -> openSUSE 12.2 Is a known issue ? worth a bugreport ? Better way to fix menu entry ? I never touched grub 2 configuration files... Daniele. -- *** Linux user # 198661 ---_ ICQ 33500725 *** *** Home http://www.kailed.net *** *** Powered by openSUSE *** -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

9 15

[opensuse-factory] Multiple repos during installation?
by Andrey Borzenkov 05 Apr '13

05 Apr '13

Is it possible to use multiple repo (like primary and update) during installation? I do not see where I can add them in installer. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

13 30

[opensuse-factory] 'su' seems to ignore "-p" (preserve environment)... in factory...
by Linda Walsh 03 Apr '13

03 Apr '13

Plays havoc with my remoteX stuff... -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

11 44

[opensuse-factory] 'which' missing from 'base build root'
by Dimstar / Dominique Leuenberger 02 Apr '13

02 Apr '13

Hi all, What a nice surprise I had to see this morning: some 'old' package (last touched > 12 months ago) suddenly fails to build.. Builderror? -bash: which: command not found yes, right: which was split out into a sep. package. No consideration or pre-announcement was done (or I missed it). And to make the whole story fun: BuildRequires: which => unresolvable: nothing provides which great stuff! I think everybody would appreciate if such fundamental changes, if not handled transparently, would be communicated upfront. As a wrapup: the 'submit' came in with: https://build.opensuse.org/request/show/161218 The submitter added as submit text: "Please wait for which, adjtimex, time to go in first since those packages have been split from util-linux." * Are we (packagers) now supposed to add BuildRequires: which to whatever uses it (I don't object it.. but where does it stop?) * When can we expect 'which' to actually appear in Factory, so that builds are possible again? Best regards, Dominique -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

9 20

[opensuse-factory] Proposal for new Bugzilla category
by Robert Schweikert 02 Apr '13

02 Apr '13

Hi developers, Yes, as a rare occasion a mail from the board on the factory list. The board has been approached about consideration of a new Accessibility (a11y) category in Bugzilla. While this is a technical issue, this specific technical issue carries with it a large community component and thus after discussion during the last board call we felt it was appropriate to approach the developer community with the proposal outlined below. We have weight both pros and cons for adding a new category in Bugzilla. The summary of the board discussion is available in the meeting minutes of the board call from 2013-03-25 (https://en.opensuse.org/openSUSE:Board_meeting#Meeting_2013-03-25). Proposal: Add an Accessibility category to Bugzilla Accessibility bugs should be treated as major bugs, even issues that may appear small or minor to non handicapped users may have a profound effect on users that depend on a11y technology. It is preferable that accessibility fixes get released as updates in the current distribution. We do not have a dedicated team to address a11y bugs, thus the regular development teams and package maintainers are responsible for fixing a11y issues, just as they are today. However, these bugs will likely have a higher priority assignment than they have today. ========= The board is in favor of having an accessibility category in Bugzilla. However, ultimately this is a decision that rests with the development community. If there is no clear consensus within the developer community the board would appreciate if the release team could reach a conclusion and post a decision to the list. The developer community and release team may of course consider alternate proposals or work flows to address this expressed need. We would very much appreciate if you would consider this request and discuss the issue. Thank you, Your openSUSE Board -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

8 12

[opensuse-factory] Problems with VMware-Workstation
by James PEARSON 31 Mar '13

31 Mar '13

Hello all I am hoping that someone can provide me with some advice about the missing header.h file issue I am encountering when trying to install VMware-Workstation on V12.3 # Issue When VMware-Workstation starts and tries to compile its required internal modules I get the following error: C header files matching your running kernel were not found. # How to reproduce I did a fresh installation of v12.3 x86_64 this morning using the openSUSE-12.3-DVD-Build0094-x86_64.iso Then I did a zypper up and tried to install the lastest version of VMware-Workstation (VMware-Workstation-Full-9.0.1-894247.x86_64.bundle) # Comments As I recall in order to build an out-of-kernel driver, you need to have the proper kernel headers installed. kernel-desktop-devel-3.7.9-1.1.2.x86_64 is installed but /lib/modules/3.7.9-1.1-desktop/build/include/linux/version.h does not exist in the same place as on V12.2 Has the "linux/version.h" changed directories or do I need to install another programme in order to get it? VMware-Workstation works fine on V12.2 and I have compared V12.3 and V12.2 below ############### V12.3 ############### # [3.7.9-1.1-desktop] VMware-Workstation installation programme : START... # OS Info: Linux M2N32 3.7.9-1.1-desktop #1 SMP PREEMPT Thu Feb 21 16:15:10 UTC 2013 (8dec968) x86_64 x86_64 x86_64 GNU/Linux # Listing the versions of installed packages... kernel-source-3.7.9-1.1.2.noarch kernel-desktop-3.7.9-1.1.2.x86_64 kernel-desktop-devel-3.7.9-1.1.2.x86_64 gcc-4.7-7.1.1.x86_64 make-3.82-154.1.1.x86_64 gcc-c++-4.7-7.1.1.x86_64 # Making sure that the kernel headers exist before installing VMware... # /lib/modules/3.7.9-1.1-desktop/build/include/linux/version.h ERROR: /lib/modules/3.7.9-1.1-desktop/build/include/linux/version.h was not found... ############### V12.2 ############### # [3.4.28-2.20-desktop] VMware-Workstation installation programme : START... # OS Info: Linux Sabertooth 3.4.28-2.20-desktop #1 SMP PREEMPT Tue Jan 29 16:51:37 UTC 2013 (143156b) x86_64 x86_64 x86_64 GNU/Linux # Listing the versions of installed packages... kernel-source-3.4.28-2.20.1.noarch kernel-desktop-3.4.28-2.20.1.x86_64 kernel-desktop-devel-3.4.28-2.20.1.x86_64 gcc-4.7-2.1.1.x86_64 make-3.82-151.1.2.x86_64 gcc-c++-4.7-2.1.1.x86_64 # Making sure that the kernel headers exist before installing VMware... # /lib/modules/3.4.28-2.20-desktop/build/include/linux/version.h # Checking to see if /lib/modules/3.4.28-2.20-desktop/build/include/linux/version.h exists... /lib/modules/3.4.28-2.20-desktop/build/include/linux/version.h exists... All comments welcome TIA James -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

7 7

[opensuse-factory] Broken factory repo
by Jiri Slaby 30 Mar '13

30 Mar '13

Hi, for a couple of days I'm seeing factory repo broken. Is this expected? Checking whether to refresh metadata for factory-oss Retrieving: http://download.opensuse.org/factory/repo/oss/content [done] Retrieving: http://download.opensuse.org/factory/repo/oss/media.1/media [done] Retrieving: http://download.opensuse.org/factory/repo/oss/content [done] Retrieving: http://download.opensuse.org/factory/repo/oss/media.1/media [done] Retrieving: http://download.opensuse.org/factory/repo/oss/media.1/media [done] Retrieving: http://download.opensuse.org/factory/repo/oss/content.asc [done] Retrieving: http://download.opensuse.org/factory/repo/oss/content.key [done] Retrieving repository 'factory-oss' metadata [error] Repository 'factory-oss' is invalid. [|] Valid metadata not found at specified URL History: - File /var/tmp/TmpFile.51yVt5 doesn't contain public key data Please check if the URIs defined for this repository are pointing to a valid repository. Warning: Disabling repository 'factory-oss' because of the above error. # zypper lr factory-oss Alias : factory-oss Name : factory-oss URI : http://download.opensuse.org/factory/repo/oss/ Enabled : Yes Priority : 99 Auto-refresh : On Keep Packages : Off Type : yast2 GPG Check : On GPG Key URI : Path Prefix : Parent Service : MD Cache Path : /var/cache/zypp/raw/factory-oss thanks, -- js suse labs -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

4 4

[opensuse-factory] auditing what process forked binary X ?
by Cristian Rodríguez 28 Mar '13

28 Mar '13

Hi: In about 3 machines I have the following annoying log message: modprobe[1062]: FATAL: Error inserting padlock_sha (/lib/modules/3.9.0-rc3-1-desktop/kernel/drivers/crypto/padlock-sha.ko): No such device This means: - Something is forking modprobe and trying to probe a module that is not going to ever work in the machines, since they have no VIA processors. - It should not be doing that and has to be stopped :-) the module will load automatically if the running system matches x86cpu:vendor:*:family:*:model:*:feature:*00AA* - It is not systemd, udev or any of the service files. - It is also not any of the few remaining legacy sysvinit scripts. - It is not a custom configuration. - I suspect it might be Networkmanager but have no evidence to prove it. Is there any way to know "what process forked modprobe" using the audit subsystem or any other facility ? thanks. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

7 19

[opensuse-factory] lua v5.2 & v5.1 coexistence -- separate -devel/headers should be allowed
by darx＠sent.com 27 Mar '13

27 Mar '13

Default lua install on 12.3/Factory is v5.2, rpm -qa | grep -i lua | sort liblua5_2-5.2.1-2.2.1.x86_64 lua-5.2.1-62.1.x86_64 lua-devel-5.2.1-2.2.1.x86_64 lua-doc-5.2.1-2.2.1.noarch It is installed with alternatives support, update-alternatives --list lua /usr/bin/lua5.2 Attempt to co-install lua51 requires *deinstall* of lua 52 devel, zypper in lua51 lua51-devel lua51-doc Loading repository data... Reading installed packages... Resolving package dependencies... Problem: lua51-devel-5.1.5-2.1.3.x86_64 conflicts with lua-devel provided by lua-devel-5.2.1-2.2.1.x86_64 Solution 1: deinstallation of lua-devel-5.2.1-2.2.1.x86_64 Solution 2: do not install lua51-devel-5.1.5-2.1.3.x86_64 Choose from above solutions by number or cancel [1/2/c] (c): Lua v51 & v52 headers represent different lua API. E.g., luajit build (from upstream) requires 5.1 API. The lua v51 & v52 app & devel packages should install in separate namespaces, and be selectable with update-alternatives. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

4 11

[opensuse-factory] Adding "Wine" YAST Pattern?
by Trent Hawkins 27 Mar '13

27 Mar '13

Hi Factory, I'm busy playing with 12.3 release. Unfortunately Crossover stopped playing nicely with openSUSE sometime last year and requires a bit of mucking around with dependencies. See this thread here for more details: http://forums.opensuse.org/english/get-technical-help-here/applications/484… Codeweavers themselves said: "Unfortunately we no longer support Crossover 12.x on Opensuse 12.x because of all the missing libraries in the distro and other issues like you're seeing. We gave up after Crossover 11.3 because trying to keep Crossover installing and running correctly on OpenSuse was like playing whack-a-mole and as soon as we would fix for one missing library another would disappear, be moved, or renamed." Anyway i've had problems with 12.2 and 12.3 on 64 bit installing all the necessary dependencies to make Crossover run. Now i can get it to work by installing all the dependencies listed here: http://wiki.winehq.org/Recommended_Packages and here http://wiki.winehq.org/WineOn64bit, but this is a bit cumbersome. Therefore i was wondering what the possibility might be of having a new Pattern in Yast Software Management for "Wine/Crossover" which i can click to get all the necessary dependencies in one go? Obviously this is a longer term request, so i'm just putting it out there for people's opinions. Cheers, Trent -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

10 14