April 2017 - openSUSE Factory - openSUSE Mailing Lists

[opensuse-factory] Re: [opensuse-packaging] Proposal: Update rpm configuration to fix issues and rationalize configuration
by Ludwig Nussel 26 Apr '17

26 Apr '17

Michael Matz schrieb: > On Wed, 26 Apr 2017, Ludwig Nussel wrote: > >>>> What's wrong with /usr/lib/name/? >>> >>> Everything. lib shall not contain executables. lib shall not contain >>> subdirectories. lib shall contain only libraries. lib shall contain >>> _nothing_ on lib64 platforms. >> >> A pretty radical demand. I guess you have technical insight that makes >> you say that? > > It's not so much technical, but as I said there are also no technical > reasons why e.g. /usr/include would be separate, all its content could > just as well be stuffed into /usr/lib. It's about what conceptually /usr/include is rather special as it's really only for C. All others have to live with a subdir in /usr/share or - /usr/lib. > belongs where, header files to /usr/include, libraries to /usr/lib and > executables called only internally by other tools into /usr/libexec, or > /usr/libexec/$toolname (modules would belong into this category) and > other files associated with a tool into /usr/share. > > From there it follows fairly easily that /usr/lib should be empty on a > pure lib64 system. Also /usr/lib should be able to be mounted noexec, and So where would you move /usr/lib/perl5 then? I has it's own architecture specific subdirectories. And where to put plugins in general? They ought to be in subdirectories of lib to not interfere with the dynamic linker. > everything should continue to work. One advantage of putting executable > helpers for a tool into libexec, not lib{,64} would be that the path > doesn't depend on architecture bits (as it should be, because for > executables the bitness doesn't matter, for libraries it does). Packages that put helper binaries in lib64 are doing it wrong unless the binary has an ABI incompatible with a 32bit library that calls it. On a system without libexec, /usr/lib/%name is the right choice rather than %_libdir/%name. >> Even the dynamic linker may read libraries from subdirectories. > > Only if configured in /etc/ld.so.conf or LD_LIBRARY_PATH. It looks into e.g. tls and x86_64 subdirectories on x86_64 cu Ludwig -- (o_ Ludwig Nussel //\ V_/_ http://www.suse.com/ SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) -- 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] Re: [opensuse-packaging] Proposal: Update rpm configuration to fix issues and rationalize configuration
by Ludwig Nussel 26 Apr '17

26 Apr '17

Michael Matz schrieb: > Hi, > > On Tue, 25 Apr 2017, Ludwig Nussel wrote: > >>> I'd personally like this to happen, yeah. It's in line with the >>> original intent of libexec and lib, and that the FHS didn't recognize >>> it was a long standing bug (IMHO, it certainly was a long-standing >>> annoyance :) ). >> >> What's wrong with /usr/lib/name/? > > Everything. lib shall not contain executables. lib shall not contain > subdirectories. lib shall contain only libraries. lib shall contain > _nothing_ on lib64 platforms. A pretty radical demand. I guess you have technical insight that makes you say that? Even the dynamic linker may read libraries from subdirectories. Also, what about multilib approaches? >> IMO /usr/libexec is redundant. > > 20 years of linux distros doing it wrong by overriding perfectly fine > autoconf defaults (caused by the FHS not grasping the concept) makes you > think so. Perfectly fine defaults like /usr/com? :-) Fedora seems to be rather lonely in the Linux world by using libexec. cu Ludwig -- (o_ Ludwig Nussel //\ V_/_ http://www.suse.com/ SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

5 5

[opensuse-factory] The reasons why openSUSE should continue to use KDE by default
by Farhad Mohammadi Majd 26 Apr '17

26 Apr '17

Hello again :P recently I did start a thread with the subject: "Why openSUSE uses KDE by default?" at that time I was *fanboy* of GNOME and GTK, but I thought deeper and understand that GNOME 3 due to its Human Interface Guidlines is really unusable for Desktop, specialy and totall GNOME due to exclusively use of C language -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

6 7

[opensuse-factory] YaST: highlights of development sprint 33
by Ancor Gonzalez Sosa 26 Apr '17

26 Apr '17

With a little bit of delay, the latest YaST Team development report has finally arrived. Enjoy it at https://lizards.opensuse.org/?p=12416 Cheers. -- Ancor González Sosa YaST Team at SUSE Linux GmbH -- 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] openSUSE Leap's Next Major Version Number
by Richard Brown 26 Apr '17

26 Apr '17

Hi all, On behalf of the openSUSE Board and Leap Release Management I am pleased to announce the next version of openSUSE Leap after 42.3 will be: openSUSE Leap 15 As with Leap 42.x, minor releases are expected annually for at least 3 years, so you can expect a Leap 15.1 to follow, then 15.2 and onwards. Obviously this is quite a dramatic change from the current version number of 42.x, so I will explain what justifies this change in some detail below. First, some history. When we started openSUSE Leap, the version number was an issue that needed addressing. openSUSE at that time was at 13.2, but SUSE Linux Enterprise (SLE) was at 12 and heading towards 12 SP1. As the main unique selling point of Leap compared to every other distribution is the fact it is based on SLE sources. We wanted to reflect that in the version number. This was particularly important when you consider that a major version in SLE really means something ("major architectural changes from the last version are introduced here") whereas minor versions/service packs have a very different message ("easy to upgrade to, no major workflow breaking changes"). Leap follows a similar philosophy, so we wanted a versioning scheme to reflect SLEs. But openSUSE had already had versions starting with 12, so we couldn't sync up with SLE. This is where 42.x came from. It gave us the opportunity to establish a relationship with SLE versions (SLE Version + 30 = Leap Version), reflect the major/minor nature of Leap releases, and avoid clashes with version numbers we'd already used. The choice of 42 doubled as a humorous nod to hitchhikers guide to the galaxy and the first version numbers of SuSE Linux and YaST (4.2 and 0.42 respectively). The plan was therefore for the next version of Leap to be 43 with it's release aligned with SLE 13, followed by Leap 43.1 (with SLE 13 SP1), Leap 43.2 (w. SP2), etc However, like all good plans, things change. SUSE have decided that their next version of SLE will be 15, not 13. Upon learning of SUSE's plans the Board and Leap release team have been considering our options. This included ignoring the changes to SLE and releasing Leap 43 as planned, at the cost of the link between SLE versions and Leap versions. 45 was also considered, as were some frankly hilarious ideas that made me worry about my own sanity and that of my fellow contributors. After considering the pros and cons of all the options however, the decision has been that Leap 15 will be our next version. SUSE's decision to skip SLE 13 and 14 gave us a perfect opportunity to sync up with SLE versions like we always wanted to originally with Leap. It's an opportunity we will not be able to take so easily a few years from now if we continued with Leaps current versioning. There are only a few packages in our distribution that reference the 42.x versioning, and they should be easily handled as part of a zypper dup, so we are not concerned about this decision impacting users upgrading. We are aware that this decision could be a minor annoyance for users of Leap with configuration management tools like saltstack and puppet, but the long term opportunity to simplify such configuration (by being able to treat SLE and Leap similarly) outweighed our desire to avoid a 'one-time' effort for people currently handling the overly complicated situation caused by Leap being at 42.x and SLE being at 12 SPx. Packagers should be able to look forward to an easier time of things as a result of this change. We intend to deprecate the 0%{leap_version} macro and simplify the current complex nest of suse_version and sle_versions that can make it very frustrating to build packages appropriately for Tumbleweed, Leap and SLE. 0%{suse_version} should continue to be available as a simple indicator of the major version of Leap & SLE for packagers (eg, 0%{suse_version} == 1500 is the expected value for SLE 15 and Leap 15 and all of their minor versions/service packs). 0%{sle_version} should remain as a more precise indicator when packagers need to handle specific versions of Leap and SLE (eg. 0%{sle_version} == 150000 is the expected value for SLE 15 & Leap 15, with 150100 being the expected value for SLE 15 SP1 & Leap 15.1) 0%{is_opensuse} will continue for those times when packagers need to distinguish between Leap and SLE even though they will now more closely share their versions. The above examples and what the future suse_version number will be for Tumbleweed is not yet final, so expect to see emails from ludwig in opensuse-factory(a)opensuse.org when they are set. Thanks to everyone involved in this so far, I'm looking forward to seeing what we make out of Leap 15, and even though I cross-posted this I would like to ask that any followup conversation is kept to the opensuse-project(a)opensuse.org thread. Regards, Richard Brown on behalf of the openSUSE Board -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

44 144

[opensuse-factory] Kodi/openssl/python segfault on TW
by Albert Koelmans 26 Apr '17

26 Apr '17

Kodi on my TW system has suddenly started to crash after showing the main screen on startup. The cause is a segfault in libcrypto.so. Top of the stack trace: #0 0x00007fffee2cf2e5 in OPENSSL_ia32_cpuid () from /lib64/libcrypto.so.1.0.0 #1 0x00007fff288e2943 in ?? () from /usr/lib64/libcrypto.so.38 #2 0x00007fff288c4c17 in _init () from /usr/lib64/libcrypto.so.38 #3 0x00007fff2888aaf0 in ?? () from /usr/lib64/libcrypto.so.38 #4 0x00007ffff7de83ba in call_init.part () from /lib64/ld-linux-x86-64.so.2 #5 0x00007ffff7de850b in _dl_init () from /lib64/ld-linux-x86-64.so.2 #6 0x00007ffff7dec9b8 in dl_open_worker () from /lib64/ld-linux-x86-64.so.2 #7 0x00007fffef0d1924 in _dl_catch_error () from /lib64/libc.so.6 #8 0x00007ffff7dec159 in _dl_open () from /lib64/ld-linux-x86-64.so.2 #9 0x00007ffff5eb4ff6 in dlopen_doit () from /lib64/libdl.so.2 #10 0x00007fffef0d1924 in _dl_catch_error () from /lib64/libc.so.6 #11 0x00007ffff5eb56d9 in _dlerror_run () from /lib64/libdl.so.2 #12 0x00007ffff5eb5092 in dlopen@@GLIBC_2.2.5 () from /lib64/libdl.so.2 #13 0x00007fff29943321 in ?? () from /usr/lib64/python2.7/lib-dynload/_ctypes.so #14 0x00007ffff61ca771 in PyEval_EvalFrameEx () from /usr/lib64/libpython2.7.so.1.0 #15 0x00007ffff61c9884 in PyEval_EvalCodeEx () from /usr/lib64/libpython2.7.so.1.0 #16 0x00007ffff61779ee in ?? () from /usr/lib64/libpython2.7.so.1.0 #17 0x00007ffff6160723 in PyObject_Call () from /usr/lib64/libpython2.7.so.1.0 The kodi crash log shows no useful info whatsoever. I don't remember any recent updates to kodi or openssl, so I'm puzzled. Any suggestions? Thanks Albert -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

2 5

[opensuse-factory] Re: [opensuse-project] Re: openSUSE Leap's Next Major Version Number
by Richard Brown 25 Apr '17

25 Apr '17

On 23 April 2017 at 10:55, Matwey V. Kornilov <matwey.kornilov(a)gmail.com> wrote: > 22.04.2017 14:37, Richard Brown пишет: >> Hi all, >> >> On behalf of the openSUSE Board and Leap Release Management I am >> pleased to announce the next version of openSUSE Leap after 42.3 will >> be: >> >> openSUSE Leap 15 > > What version will be after openSUSE Leap 41? Leap and SLE major versions come out on average about once every 4 years. So with this plan, starting at openSUSE Leap 15 in 2018, Leap 41 should be 104 years away Ask this question again in 2122 and we'll figure out the answer then. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

12 25

[opensuse-factory] New Tumbleweed snapshot 20170424 released!
by Dominique Leuenberger 25 Apr '17

25 Apr '17

Please note that this mail was generated by a script. The described changes are computed based on the x86_64 DVD. The full online repo contains too many changes to be listed here. Please check the known defects of this snapshot before upgrading: https://openqa.opensuse.org/tests/overview?distri=opensuse&groupid=1&versio… When you reply to report some issues, make sure to change the subject. It is not helpful to keep the release announcement subject in a thread while discussing a specific problem. Packages changed: brasero (3.12.1 -> 3.12.2+20170302.8d6244fa) cppunit (1.13.2 -> 1.14.0) google-croscore-fonts (1.23.0 -> 1.31.0) grub2 hardlink (1.0.g50 -> 1.0+git.e66999f) jack kdebase4-workspace libinput libiscsi perl-Image-ExifTool (10.40 -> 10.50) tmux (2.3 -> 2.4) virtualbox xine-ui === Details === ==== brasero ==== Version update (3.12.1 -> 3.12.2+20170302.8d6244fa) Subpackages: brasero-lang brasero-nautilus libbrasero-burn3-1 libbrasero-media3-1 libbrasero-utils3-1 - Update to version 3.12.2+20170302.8d6244fa: + Updated translations. + build: - Disable format-y2k error. - Honor ABI version for introspection. - Use modern autotools integration for introspection. - Use -Wno-error=format-y2k. - Use -Wno-error=format-nonliteral. - Switch to service generated git checkout. Following this, add gnome-common BuildRequires and pass autogen.sh to bootstrap. Also pass --enable-gtk-doc to configure to build documentation. This fixes build with gcc 7 (boo#1030239). - Conditionally apply translations-update-upstream BuildRequires and macro for non-openSUSE only. ==== cppunit ==== Version update (1.13.2 -> 1.14.0) - Version update to 1.14.0: * TestCaller supports any callable that can be put into std::function<void()>. * CPPUNIT_TEST_PARAMETERIZED executes a test for any value in an iteratable. * Added new Assertion macros: ASSERT_LESS, ASSERT_GREATER, ASSERT_LESSEQUAL, ASSERT_GREATEREQUAL * Remove QT test runner ==== google-croscore-fonts ==== Version update (1.23.0 -> 1.31.0) Subpackages: google-arimo-fonts google-cousine-fonts google-tinos-fonts - Updated to verison 1.31, which removes Symbol Neau ==== grub2 ==== Subpackages: grub2-i386-pc grub2-snapper-plugin grub2-systemd-sleep-plugin grub2-x86_64-efi grub2-x86_64-xen - update grub2-btrfs-workaround-grub2-once.patch to also store saved_entry in additional environment block (boo#1031025) - fix building with GCC (bsc#1030247) * add grub2-fix-uninitialized-variable-in-btrfs-with-GCC7.patch * grub2-add-FALLTHROUGH-annotations.patch ==== hardlink ==== Version update (1.0.g50 -> 1.0+git.e66999f) - Switch to source service and update git snapshot to e66999f: * Make hardlinking atomic wrt replacing existing files * Fixed 32 bit build with gcc7 (rh#1422989) (boo#1030251) ==== jack ==== Subpackages: libjack-devel libjack0 - Fix gcc7 build failure with jack-fixgcc7.patch, sent to github jack2 issue#253 ==== kdebase4-workspace ==== Subpackages: kdebase4-workspace-libs python-kdebase4 - Add gcc7-fix.diff to fix an error reported by GCC7 (boo#1031317) ==== libinput ==== Subpackages: libinput-udev libinput10 - Add libinput-elantech-pressure-levels.patch to fix pressure sensitivity for ELANTECH touchpads causing uncomfortable two-finger taps, scrolls (boo#1034335, fdo#100463). ==== libiscsi ==== - Do not build with -Werror ==== perl-Image-ExifTool ==== Version update (10.40 -> 10.50) Subpackages: exiftool perl-File-RandomAccess - Update to version 10.50 (changes since 10.40): * Add an experimental metadata validation feature (invoked either by requesting the new Extra Validate tag or by setting the API Validate option). * Add support for the PSDT file extension. * Add age.config to the distribution. * Add a new Sony lens. * Add a new PentaxModelID. * Enhance the -p option to allow files to be grouped in sections. * Made the makernote offset warning minor. * Relaxe parsing of NMEA GGA sentence so comma after the geoid units is now optional. * Patch the problem extracting value of an unsafe binary tag with the -b option when specified using -TAG# instead of -TAG with -n. * Add an ability to read/write PNG eXIF and zXIF chunks, and make these the place where new EXIF is created in PNG images (zXIF if the -z option is used, or eXIF otherwise). * Add an ability to copy Photoshop OriginPathInfo with photoshop_paths.config. * Make FileUserID and FileGroupID writable. * Change format for the Sony ImageCount tag. * Improvements to the experimental Validate feature. * Fix an incorrect XMP swf namespace URI. * Fix a problem using new -p section feature when combined with - w or -ee. * Fix a formatting problem in -listx output when the -lang option was used. * Fix a problem where UserComment wasn't removed if found in IFD0 when writing it to the correct IFD. * Restrict writing of EXIF:FlashEnergy to a single value as per EXIF spec. * Revert format change of the Sony ImageCount tag. * Change PNG new eXIF/zXIF chunk names to "exIf" and "zxIf" until the proposed chunks are accepted (of course, while maintaining backward compatibility for reading/updating the other chunks). * Lower priority of XMP-pdf:Keywords so it doesn't take precedence over PDF:Keywords when the Duplicates option is not used. * Improve config_files/convert_regions.config to handle the case where the RegionInfoMP is missing a Rectangle. * Add a few new CanonModelID values and a new Canon LensType. * Add two new Nikon lenses. * Add a few new Sony/Minolta lenses. * Add two new Sony MeteringMode values. * Improve verbose dump of Photoshop Layer information. * Patch to allow "FileName encoding not specified" warnings to be avoided by setting -charset filename="". * Fix a problem in photoshop_paths.config printing some paths. * Add an ability to write a number of macOS system tags (including the file creation date!). * Add an ability to extract macOS extended attributes ("XAttr" tags). * Move macOS System tags from the Extra table into a new macOS group and add an ability to extract them by requesting the macOS group. * Update QuickTime GenreID list. * Fix the "Invalid xref" problem when reading some PDF files. * Fix an error in Minolta lens list. * Fix a minor problem with the -U option generating Unknown tags for some known bytes in variable-sized strings. * Add read support for JSON-format files. * Add two new Sony/Minolta lenses. * Add a number of new Pentax tag values. * Decode a new Canon CR2 tag. * Decode WB information for Canon 800D. * Improve config_files/photoshop_paths.config to indicate start of paths. * Experimental Validate feature no longer warns about Windows XP tags. * Fix a problem extracting layer information from very large PSD/PSB files. * Add some new FujiFlashMode values. * Add a new Sony LensType. * Add a new Canon LensType. * Add a new CanonModelID and minor changes to some others. * Decode two Pentax tags and add a number of new values for other Pentax tags. * Decode a new Sony tag. * Improvements to the experimental Validate feature. * Fix a problem which could cause hang when reading bad PPT documents. * Add a "DateFmt" utility function for use in advanced formatting expressions. * Add a new Sony/Minolta LensType. * Decode a new Panasonic tag. * Fix a problem decoding Sony VariableLowPassFilter values. * Fix a problem setting XMP:About when creating new XMP in a file. * Fix an incorect Pentax DriveMode value. * Decode a new Pentax tag. * Improve decoding of Olympus DriveMode. * Improve handling of errors from utime when setting file times. * Fix a potential hang problem when reading corrupted QuickTime metadata. * Fix a problem deleting duplicate EXIF tags when writing other tags at the same time. * API Changes: + add an experimental Validate option; + add an XAttrTags option; + enhance the RequestAll option; + enhance the RequestTags option to allow groups to be requested; + allow access to the advanced formatting expression via a new ExifTool "FMT_EXPR" member variable. ==== tmux ==== Version update (2.3 -> 2.4) - Fix tmux-socket-path.patch to create directories inside of /run/tmux - update to 2.4 - refresh tmux-socket-path.patch + Incompatible Changes * Key tables have undergone major changes. Mode key tables are no longer separate from the main key tables. All mode key tables have been removed, together with the -t flag to bind-key and unbind-key. The emacs-edit, vi-edit, emacs-choose and vi-choose tables have been replaced by fixed key bindings in the command prompt and choose modes. The mode-keys and status-keys options remain. The emacs-copy and vi-copy tables have been replaced by the copy-mode and copy-mode-vi tables. Commands are sent using the -X and -N flags to send-keys. So the following: bind -temacs-copy C-Up scroll-up bind -temacs-copy -R5 WheelUpPane scroll-up Becomes: bind -Tcopy-mode C-Up send -X scroll-up bind -Tcopy-mode WheelUpPane send -N5 -X scroll-up This changes allows the full command parser (including command sequences) and command set to be used - for example, the normal command prompt with editing and history is now used for searching, jumping, and so on instead of a custom one. The default C-r binding is now: bind -Tcopy-mode C-r command-prompt -p'search up' "send -X search-backward '%%'" There are also some new commmands available with send -X, such as copy-pipe-and-cancel. * set-remain-on-exit has gone -- can be achieved with hooks instead. * Hooks: before hooks have been removed and only a selection of commands now have after hooks (they are no longer automatic). Additional hooks have been added. * The xterm-keys option now defaults to on. + Normal Changes * Support for mouse double and triple clicks. * BCE (Background Colour Erase) is now supported. * All occurrences of a search string in copy mode are now highlighted; additionally, the number of search results is displayed. The highlighting updates interactively with the default emacs key bindings (incremental search). * source-file now understands glob patterns. * Formats now have simple comparisons: [#]{==:a,b} [#]{!=:a,b} * There are the following new formats: - #{version} -- the tmux server version; - #{client_termtype} -- the terminal type of the client; - #{client_name} -- the name of a client; - #{client_written} -- the number of bytes written to the client. * The configuration file now accepts %if/%endif conditional blocks which are processed when it is parsed; the argument is a format string (useful with the new format comparison options). * detach-client now has -E to execute a command replacing the client instead of exiting. * Add support for custom command aliases, this is an array option which contains items of the form "alias=command". This is consulted when an unknown command is parsed. * break-pane now has -n to specify the new window name. * OSC 52 support has been added for programs inside tmux to set a tmux buffer. * The mouse "all event" mode (1003) is now supported. * Palette setting is now possible (OSC 4 and 104). * Strikethrough support (a recent terminfo is required). * Grouped sessions can now be named (new -t). * terminal-overrides and update-environment are now array options (the previous set -ag syntax should work without change). * There have been substantial performance improvements. ==== virtualbox ==== Subpackages: virtualbox-guest-kmp-default virtualbox-guest-tools virtualbox-guest-x11 - Add File "vbox_fix_42.3_api.patch" to handle the get_user_pages() API change in Leap 42.3. - Package VBoxVNC.so. This extension is already being built, just not packaged. This feature is requested in bsc #1024671. ==== xine-ui ==== - Fix desktop file with xine-ui-desktop.patch -- 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] Re: [opensuse-packaging] Proposal: Update rpm configuration to fix issues and rationalize configuration
by Ludwig Nussel 25 Apr '17

25 Apr '17

Michael Matz schrieb: > On Mon, 24 Apr 2017, Neal Gompa wrote: > >> * Backport the --changes option from RPM git master to rpm 4.13. This >> * Change the default binary package payload compression algorithm from >> old-lzma to xz. Apparently, this change was supposed to have already >> * Define %_sharedstatedir as /var/lib instead of /usr/com. The current > > I think all of these are no brainers. > >> * Revert %_libexecdir to /usr/libexec. > > I'd personally like this to happen, yeah. It's in line with the original > intent of libexec and lib, and that the FHS didn't recognize it was a long > standing bug (IMHO, it certainly was a long-standing annoyance :) ). What's wrong with /usr/lib/name/? IMO /usr/libexec is redundant. cu Ludwig -- (o_ Ludwig Nussel //\ V_/_ http://www.suse.com/ SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) -- 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] NVidia driver: An incomplete installation of libglvnd was found.
by Patrick Shanahan 25 Apr '17

25 Apr '17

* Andrei Dziahel <develop7(a)develop7.info> [04-20-17 10:14]: > Affects me too, NVidia driver v381.09 > > /cc Stefan Dirsch > > 2017-04-15 23:06 GMT+03:00 Michal Hlavac <miso(a)hlavki.eu>: > > Hi, > > after this release I get this error while installing nvidia driver: > > > > "An incomplete installation of libglvnd was found. Do you want to > > install a full copy of libglvnd?" > > > > Overwriting existing libraries do the job, but I think it's not OK PLEASE, there is no reason to quote the entire update email. Even instructions posted AT THE TOP of that mail: When you reply to report some issues, make sure to change the subject. It is not helpful to keep the release announcement subject in a thread while discussing a specific problem. and TOP POSTING is BAD and against openSUSE mailing lists policy. there is a simple answer to the problem with libglvnd available by rtfd for the installer: sh ./NVIDIA-Linux-x86_64-381.09.run -aqs --install-libglvnd I would have responded sooner, but my server dissolved. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 Photos: http://wahoo.no-ip.org/piwigo @ 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

4 7