August 2017 - openSUSE Factory - openSUSE Mailing Lists

[opensuse-factory] Leap 42.3, Samba and Mac OSX Server
by AW 16 Aug '17

16 Aug '17

Hi! if you'd like to connect via smb from a client (Leap 42.3) to a share on a Mac OSX server, this will fail for reasons I don't know. Bugreport: https://bugzilla.samba.org/show_bug.cgi?id=12965 Bug is fixed in Samba 4.6.7. For the sake of users who'd like to access a share on such a server it would be nice to update Samba for Leap as well as for TW. If my suggestions should be wrong for some reason, please correct me. Regards, Alexander -- 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] [Leap 42.3] VirtualBox does not start up
by Roman Bysh 16 Aug '17

16 Aug '17

Hi all, Since the original VirtualBox 5.1.26 has vboxnet0 was missing, I installed VirtualBox provided by openSUSE Leap 42.3. I can't get the program to start up. I started from konsole and the results appear below: VirtualBox VirtualBox: Error -10 in SUPR3HardenedMain! VirtualBox: Effective UID is not root (euid=1000 egid=100 uid=1000 gid=100) VirtualBox: Tip! It may help to reinstall VirtualBox. mantrid  ~  QSettings::value: Empty key passed QSettings::value: Empty key passed Is there a workaround? -- Cheers! Roman -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

4 13

[opensuse-factory] zypper dup and the "upgrade workflow"
by Tristan Miller 15 Aug '17

15 Aug '17

Dear $LIST, I recently attempted to upgrade openSUSE 13.2 to openSUSE Tumbleweed using the procedure described at <https://en.opensuse.org/openSUSE:Tumbleweed_upgrade>. That page defines "upgrade" as "moving from an older openSUSE release (eg. openSUSE 13.2 or Leap) to Tumbleweed" and describes two "supported upgrade mechanisms", including one called "online upgrade". This "online upgrade" mechanism involves replacing all the old Zypper repositories with Tumbleweed repositories and then running "zypper dup". When I ran into trouble with the "online upgrade" process, I filed a bug report and was chastised by a developer for using the "zypper dup" command instead of following the "upgrade workflow" [1]: > please notice that "zypper dup" for a distro upgrade may or may not > work; that's why we provide the upgrade workflow I asked what "upgrade workflow" he was referring to but received no response. Does anyone know what the official "upgrade workflow" is for updating older versions of openSUSE to Tumbleweed? If it's not already on the wiki, could I ask someone to please update the wiki page at <https://en.opensuse.org/openSUSE:Tumbleweed_upgrade> with it? If it is already on the wiki, perhaps <https://en.opensuse.org/openSUSE:Tumbleweed_upgrade> could redirect to it. Regards, Tristan [1] https://bugzilla.suse.com/show_bug.cgi?id=1025725#c3 -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Tristan Miller Free Software developer, ferret herder, logologist https://logological.org/ =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

3 2

[opensuse-factory] Re: openSUSE BugHunting 2017
by Petr Hodac (Hody) 15 Aug '17

15 Aug '17

Hello all, as we all survived the Bugzilla sprint [1] it is time to take a look at what happened. We closed approx 1 thousand of bugs, which is quite nice. Following products are without bugs: * openSUSE12.1 0 * openSUSE11.4 0 * openSUSE11.3 0 * openSUSE11.2 0 * openSUSE11.1 0 * openSUSE11.0 0 * openSUSE10.3 0 The newer versions show bit different story: * Tumbleweed 1626 * Leap42.3 279 * Leap42.2 714 * Leap42.1 527 * openSUSE13.2 371 * openSUSE13.1 420 * openSUSE12.3 160 * openSUSE12.2 65 You can take a look at detailed graphs and charts in the attached pictures. Now what should we take to future from this excersize: We still have many open bugs. At the end of a product we end up with approx 400 open bugs on average. On a generic note there are teams containing most of the bugs (based on amount of assigned bugs): * Yast * KDE * Gnome * Mozilla As a solution maybe we should directly forward these to RESOLVED->UPSTREAM since the experience shows that they will otherwise be open for years. For some non-apparent reason people like Adrian to suffer and assign him ton of weirdly unrelated bugs. But apart from feeling sorry for him I have no idea how to deal with this ;) Unrelated as it was not included to the sprint the openSUSE.org assignee is utter garbage of invalid bugs and assignees that are not existing, there are ~670 bugs and huge chunk of them does not make sense. Petr Hodac (hody) University and community coordinator [1] https://etherpad.opensuse.org/p/openSUSE-bughunting On 10.8.2017 20:07, Petr Hodac (Hody) wrote: > > Hello > > The first day is behind us. openSUSE 10.3 and 11.0 are nice but other > :( . I have prepared some chart from today and current situation. I > believe it will be better tomorrow. > > Hody > > [info] https://etherpad.opensuse.org/p/openSUSE-bughunting > > Bugs > > openSUSETumbleweed 1585 > Leap42.3 254 > Leap42.2 715 > Leap42.1 534 > openSUSE13.2 377 > openSUSE13.1 446 > openSUSE12.3 195 > openSUSE12.2 176 > openSUSE12.1 196 > openSUSE11.4 189 > openSUSE11.3 127 > openSUSE11.2 165 > openSUSE11.1 202 > openSUSE11.0 0 > openSUSE10.3 0 > Total 5161 > > > On 31.7.2017 16:54, Petr Hodac (Hody) wrote: >> Hello >> >> We were looking in Bugzilla queue and the number is horrible. We have >> loads of issues reported on products that are no longer supported or >> loads of bugs reported against Tumbleweed. >> >> See the following table for yourself: >> openSUSE Tumbleweed 1633 >> openSUSE Leap 42.3 9 >> openSUSE Leap 42.2 220 >> openSUSE Leap 42.1 280 >> openSUSE 13.2 0 >> openSUSE 13.1 457 >> openSUSE 12.3 198 >> openSUSE 12.2 178 >> openSUSE 12.1 199 >> openSUSE 11.4 193 >> openSUSE 11.3 132 >> openSUSE 11.2 170 >> openSUSE 11.1 221 >> openSUSE 11.0 31 >> openSUSE 10.3 12 >> >> Total 3933 >> >> As such we decided to organize BugHunting event on *August >> 10.-12.8.2017*. It will be online event and we should organize at irc >> #opensuse-bughunting on freenode and technical discussion should >> happen on opensuse-factory(a)opensuse.org >> >> If you decide to join in, feel free to pick any query bellow and >> start closing issues. Possible bug resolutions are: >> Fixed: when you fix the bug >> Worksforme: well the bug is no longer there or we fix it when found >> Wontfix/Feature: issue is a feature request/or something that >> should not be fixed by us >> Upstream: well it is open for ages and it is issue in the >> software itself rather than in package/distribution thus the report >> should go there >> >> Supported: >> openSUSE >> Tumbleweed https://bugzilla.opensuse.org/buglist.cgi?bug_status=__open__&limit=0&list_… >> openSUSE Leap >> 42.3 https://bugzilla.opensuse.org/buglist.cgi?bug_status=UNCONFIRMED&bug_status… >> openSUSE Leap >> 42.2 https://bugzilla.opensuse.org/buglist.cgi?bug_status=UNCONFIRMED&bug_status… >> >> Unsupported: >> openSUSE Leap >> 42.1 https://bugzilla.opensuse.org/buglist.cgi?bug_status=UNCONFIRMED&bug_status… >> openSUSE >> 13.2 https://bugzilla.opensuse.org/buglist.cgi?bug_status=__open__&list_id=72512… >> openSUSE >> 13.1 https://bugzilla.opensuse.org/buglist.cgi?bug_status=__open__&list_id=72512… >> openSUSE >> 12.3 https://bugzilla.opensuse.org/buglist.cgi?bug_status=__open__&list_id=72519… >> openSUSE >> 12.2 https://bugzilla.opensuse.org/buglist.cgi?bug_status=__open__&list_id=72519… >> openSUSE >> 12.1 https://bugzilla.opensuse.org/buglist.cgi?bug_status=__open__&list_id=72519… >> openSUSE >> 11.4 https://bugzilla.opensuse.org/buglist.cgi?bug_status=__open__&list_id=72519… >> openSUSE >> 11.3 https://bugzilla.opensuse.org/buglist.cgi?bug_status=__open__&list_id=72519… >> openSUSE >> 11.2 https://bugzilla.opensuse.org/buglist.cgi?bug_status=__open__&list_id=72520… >> openSUSE >> 11.1 https://bugzilla.opensuse.org/buglist.cgi?bug_status=__open__&list_id=72519… >> openSUSE >> 11.0 https://bugzilla.opensuse.org/buglist.cgi?bug_status=__open__&list_id=72519… >> openSUSE >> 10.3 https://bugzilla.opensuse.org/buglist.cgi?bug_status=__open__&list_id=72519… >> >> If you happen to have any questions please reply to this email. >> >> Petr "Hody" Hodac >> University and community coordinator >

2 1

[opensuse-factory] NVIDIA gfx driver RPMs available for Tumbleweed ... (follow-up)
by Stefan Dirsch 15 Aug '17

15 Aug '17

Hi The gdm issue (gdm doesn't come up at all) mentioned below has been handled in boo#1053115 and the culprit has been identified. https://bugzilla.suse.com/show_bug.cgi?id=1053115 Workaround available: https://bugzilla.suse.com/show_bug.cgi?id=1053115#c11 https://bugzilla.suse.com/show_bug.cgi?id=1053115#c12 I'll send fixed packages to NVIDIA begin of next week. Usually it's not a good idea to do this friday. If issues arise due to the update, this may become an inconvenient weekend for users, NVIDIA and me. So I would like to avoid this. ;-) Another issue has been *re*discovered at the same time. TW users, who are/were using the manual NVIDIA installer can be affected by this. If you had NVIDIA driver installed manually when updating TW from Mesa to libglvnd+Mesa, you'll see an orphaned libGL.so.1.2* in /usr/lib64 and /usr/lib. This may have happened unnoticed. So please check this after running nvidia-installer --uninstall and remove these files, if available via rm -f /usr/lib*/libGL.so.1.2* before installing the NVIDIA RPMs. This is already documented in https://en.opensuse.org/SDB:NVIDIA_the_hard_way Thanks, Stefan > Hi > > Since yesterday there are NVIDIA gfx driver RPMs available for > Tumbleweed. Feel free to give them a try by adding the repository manually via > > zypper ar https://download.nvidia.com/opensuse/tumbleweed nvidia-tumbleweed > > and install them via > zypper inr > The kernel module is being built during installation (as it's done with the > Leap packages). But the kernel module is also being rebuilt and reinstalled > after a kernel update has been done, since we don't necessarily keep the kABI > stable for TW. This has been implemented by making use of RPM's trigger > scripts. > > Known issues/limitations: > > https://download.nvidia.com/opensuse/tumbleweed nvidia-tumbleweed is a > non-browsable directory, so please don't tell me it doesn't exist after > pasting it into your favorite web-browser. ;-) > > Packages are only available for the latest long lived branch (currently > 384.59). Reason is, that with TW we switched to libglvnd, which is not > supported by the legacy driver series 340.xx and 304.xx. > > If gdm doesn't come up, try using another DM. xdm worked fine for me. > Something is weird with gdm, but I couldn't figure out yet, what. :-( > > > You can provide feedback here in this mail thread or via bugzilla. If you use > Bugzilla, please use > Product: openSUSE Tumbleweed > Component: X11 3rd party Driver Public Key available ------------------------------------------------------ Stefan Dirsch (Res. & Dev.) SUSE LINUX GmbH Tel: 0911-740 53 0 Maxfeldstraße 5 FAX: 0911-740 53 479 D-90409 Nürnberg http://www.suse.de Germany --------------------------------------------------------------- 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

1 1

[opensuse-factory] New Tumbleweed snapshot 20170806 released!
by Dominique Leuenberger 15 Aug '17

15 Aug '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: at (3.1.16 -> 3.1.20) bluez (5.45 -> 5.46) dracut git (2.13.3 -> 2.14.0) gstreamer-plugins-bad hwinfo (21.46 -> 21.47) icoutils (0.31.1 -> 0.31.3) inst-source-utils k3b libdrm obs-service-source_validator (0.6+git20170111.82ea590 -> 0.6+git20170719.d4384e5) perl-File-Path (2.140000 -> 2.150000) perl-URI (1.71 -> 1.72) perl-XML-XPath (1.40 -> 1.41) postfix pulseaudio (10.0 -> 10.99.1) rsyslog (8.27.0 -> 8.28.0) sqlite3 (3.19.3 -> 3.20.0) subversion wicked (0.6.40 -> 0.6.41) xli (20061110 -> 1.17+git20170726.0bb4fb4) xosd xscreensaver (5.36 -> 5.37) === Details === ==== at ==== Version update (3.1.16 -> 3.1.20) - Drop patch at-3.1.8-eal3-manpages.patch merged upstream differently - Version update to at 3.1.20 to match latest upstream: * Pam and selinux implemented upstream * various tiny fixes - Rebase patches: * at-3.1.13-documentation-dir.patch * at-3.1.13-massive_batch.patch * at-3.1.14-joblist.patch * at-3.1.14-parse-suse-sysconfig.patch * at-3.1.14-usePOSIXtimers.patch * at-3.1.14.patch - Drop no longer needed patches: * at-3.1.13-formatbugs.patch * at-3.1.13-pam-session-as-root.patch * at-3.1.13-pam.patch * at-3.1.13-queue-nice-level.patch * at-3.1.14-selinux.patch ==== bluez ==== Version update (5.45 -> 5.46) Subpackages: bluez-cups bluez-devel libbluetooth3 - update to version 5.46: * Fix issue with handling ATT over BR/EDR connections. * Fix issue with SDP browsing cleanup after connection. * Fix issue with pointer dereference and OPP Put request. * Fix issue with identity address updates during pairing. * Fix issue with not removing services that had disappeared. * Add support for improved discovery of included services. * Add support for simplified characteristics discovery. * Add support for GATT caching configuration option. * Add experimental support for AcquireWrite and AcquireNotify. ==== dracut ==== - Ensure dracut.sh responds properly to hostonly cmdline (bsc#1048748) * adds 0528-Ensure-dracut.sh-responds-properly-to-hostonly_cmdli.patch ==== git ==== Version update (2.13.3 -> 2.14.0) Subpackages: git-core git-cvs git-daemon git-email git-gui git-svn git-web gitk - git 2.14.0: * Use of an empty string as a pathspec element that is used for 'everything matches' is deprecated, use '.' * Avoid blindly falling back to ".git" when the setup sequence indicates operation not on a Git repository * "indent heuristics" are now the default. * Builds with pcre2 * Many bug fixes, improvements and updates - git 2.13.4: * Update the character width tables. * Fix an alias that contained an uppercase letter * Progress meter fixes * git gc concurrency fixes ==== gstreamer-plugins-bad ==== Subpackages: libgstadaptivedemux-1_0-0 libgstbadaudio-1_0-0 libgstbadbase-1_0-0 libgstbadvideo-1_0-0 libgstbasecamerabinsrc-1_0-0 libgstcodecparsers-1_0-0 libgstgl-1_0-0 libgstmpegts-1_0-0 libgstphotography-1_0-0 libgsturidownloader-1_0-0 libgstwayland-1_0-0 - Add pkgconfig(libsrtp) BuildRequires: Build srtp support. ==== hwinfo ==== Version update (21.46 -> 21.47) Subpackages: hwinfo-devel - merge gh#openSUSE/hwinfo#53 - really set default timeout to 20s for Video BIOS emulation calls (bsc#1051076) - 21.47 ==== icoutils ==== Version update (0.31.1 -> 0.31.3) - Update to 0.31.3. * Fixed wrestool being broken. - Changes in 0.31.2. * Various security fixes: CVE-2017-6009, CVE-2017-6010, CVE-2017-6011 (boo#1025700, boo#1025703). ==== inst-source-utils ==== - drop requires for recode ==== k3b ==== - Add Add-forceCheck-for-ManualCheckSystem.patch to make the manual system check work again after the previous fix - Add upstream patches to not show the system configuration problems dialog if disabled (kde#381368, boo#1051368) * Fix-do-not-show-again.patch * Add-readCheckSystemConfig.patch ==== libdrm ==== Subpackages: libdrm-devel libdrm2 libdrm_amdgpu1 libdrm_intel1 libdrm_nouveau2 libdrm_radeon1 - build-require util-macros-devel for suse_version > 1320 ==== obs-service-source_validator ==== Version update (0.6+git20170111.82ea590 -> 0.6+git20170719.d4384e5) - Update to version 0.6+git20170719.d4384e5: * Don't complain about Debian manpages files missing in *.spec * Add README.md file * Fix service run mode check for localonly * Add 80-multibuild_xor_multispec: only multibuild OR multispec is supported * extract GPG_OPTIONS variable for multiple runs * For signature verification, use trust model "always" - Update to version 0.6+git20170715.607b861: * - support obspcio also in osc case * Remove provides and obsoletes from the spec ==== perl-File-Path ==== Version update (2.140000 -> 2.150000) - updated to 2.15 see /usr/share/doc/packages/perl-File-Path/Changes 2.15 2017-07-29 - Correct documentation error re possible arguments for rmtree(). ==== perl-URI ==== Version update (1.71 -> 1.72) - updated to 1.72 see /usr/share/doc/packages/perl-URI/Changes 1.72 2017-07-25 - Convert the dist to Dist::Zilla for authoring. - Remove recommendation of Business::ISBN as urn/isbn.pm is deprecated - Use Test::Needs instead of raw eval in urn-isbn.t ==== perl-XML-XPath ==== Version update (1.40 -> 1.41) - updated to 1.41 see /usr/share/doc/packages/perl-XML-XPath/Changes 1.41 2017-07-28 MANWAR - Fixed GitHub issue #4 (can't use non-ascii first character as element name). Thanks @nanis, @ikegami. ==== postfix ==== Subpackages: postfix-doc - bnc#1045264 L3: postmap problem * Applying proposed patch of leen.meyer(a)ziggo.nl in bnc#771811 ==== pulseaudio ==== Version update (10.0 -> 10.99.1) Subpackages: libpulse-devel libpulse-mainloop-glib0 libpulse0 pulseaudio-bash-completion pulseaudio-esound-compat pulseaudio-module-bluetooth pulseaudio-module-gconf pulseaudio-module-jack pulseaudio-module-lirc pulseaudio-module-x11 pulseaudio-module-zeroconf pulseaudio-utils - Fix Requires(post) and Requires(pre) mixup - Update to 11 RC1 (10.99.1) * Support for newer AirPlay hardware * USB and bluetooth devices preferred over internal sound cards * Bluetooth HSP headset role implemented * Bluetooth HFP audio gateway role implemented (requires oFono) * Bluetooth HSP audio gateway and HFP hands-free unit roles can be enabled simultaneously * Upmixing can now be disabled without bad side effects * Avoid having unavailable sinks or sources as the default * Option to avoid resampling more often * Option to automatically switch bluetooth profile to HSP more often * Better latency control in module-loopback * Changed module argument names in module-ladspa-sink and module-virtual-surround-sink * Fixed input device handling in module-waveout * Improved bluetooth MTU configuration (warning! this causes some hardware to not work any more, see the details below for how to fix it) * Applications can request LADSPA or virtual surround filtering for their streams * Support for 32-bit applications on 64-bit systems in padsp - add --with-pulsedsp-location='/usr/\\$$LIB/pulseaudio' to enable upstream padsp multiarch fix - remove patch4 padsp-biarch.patch, fixed upstream - remove patch5 pulseaudio-vala-0.36.patch, fixed upstream ==== rsyslog ==== Version update (8.27.0 -> 8.28.0) Version 8.28.0 [v8-stable] 2017-06-27 * omfwd: add parameter "tcp_frameDelimiter" * omkafka: large refactor of kafka subsystem * imfile: improved handling of atomically renamed file (w/ wildcards) * imfile: add capability to truncate oversize messages or split into multiple * mmdblookup fixes and extensions * bugfix: fixed multiple memory leaks * imptcp: add new parameter "flowControl" * imrelp: add "maxDataSize" config parameter * multiple modules: gtls: improve error if certificate file can't be opened * omsnare: allow different tab escapes * omelasticsearch: converted to use libfastjson instead of json-c * imjournal: _PID fallback * added fallback for _PID proprety when SYSLOG_PID is not available * introduced new option "usepid" which sets which property should rsyslog use, it has 3 states system|syslog|both, default is both * deprecated "usepidfromsystem" option, still can be used and override the "usepid" * it is possible to revert previous default with usepid="syslog" * multiple modules: add better error messages when regcomp is failing * omhiredis: fix build warnings * imfile bugfix: files mv-ed in into directory were not handled * omprog bugfix: execve() incorrectly called * imfile bugfix: multiline timeout did not work if state file exists * lmsig_ksi-ls12 bugfix: build problems on some platforms * core bugfix: invalid object type assertion * regression fix: local hostname was not always detected properly... * bugfix: format security issues in zmq3 modules (bsc#1051798) * bugfix build system: add libksi only to those binaries that need it * bugfix KSI ls12 components: invalid tree height calculation ==== sqlite3 ==== Version update (3.19.3 -> 3.20.0) Subpackages: libsqlite3-0 libsqlite3-0-32bit sqlite3-devel sqlite3-doc - Update to 3.20.0: * Potential incompatible change for clients incorrectly relying on unspecified behavior: column names returned by sqlite3_column_name() and sqlite3_column_name16() may return different names when views or subqueries are used in the FROM clause, and AS clauses are not used (as they should be) * Text of some error messages changed. Applications that depend on specific error message text may be impacted. ==== subversion ==== Subpackages: libsvn_auth_gnome_keyring-1-0 libsvn_auth_kwallet-1-0 subversion-bash-completion subversion-devel subversion-perl subversion-python subversion-server subversion-tools - Add instructions for running svnserve as a user different from "svn", and remove sysconfig variables that are no longer effective with the systemd unit. bsc#1049448 ==== wicked ==== Version update (0.6.40 -> 0.6.41) Subpackages: libwicked-0-6 wicked-service - version 0.6.41 - dhcp6: fix to send up to 5 release retransmissions - ifconfig: do not stop adding routes on one bad route (bsc#1036619) - dhcp4: fix to use rfc4361 client-id on infiniband (bsc#1022872) - man: ifcfg.5: Fix directory name for compatibility scripts - dhcp4: own check for user class id strings (bsc#1045522) - dhcp: cleanup common option update flags (bsc#1027099) - vxlan: convert ifcfg VXLAN_REMOTE_IP to remote-ip ==== xli ==== Version update (20061110 -> 1.17+git20170726.0bb4fb4) - Drop patches merged in the git repo: * xli-1.17.0-8bit_palette.patch * xli-1.17.0-configfile.patch * xli-1.17.0-overflow.patch * xli-1.17.0.patch * xli-png-alpha.patch * xli-png_check_sig.patch - Update to version 1.17+git20170726.0bb4fb4: * Respect destdir during install * Symlink with relative path in makefile * Add support for 8bit pallete * Make xli handle arrow keys to move image * Add temp files and patches to gitignore * Implement zoom functionality * Adds support for the special "None" colour in XPMs * Document zooming control * Add a -forall option * A bug with all merging * Do not read past buffer end - Allow xli to load up on alpha backgrounded png, if there would be upstream this should be upstreamed: * xli-png-alpha.patch - Cleanup a bit with spec-cleaner ==== xosd ==== - Cleanup with spec-cleaner - Use configure switches from Fedora and Debian - Split out library to specific subpackage ==== xscreensaver ==== Version update (5.36 -> 5.37) Subpackages: xscreensaver-data xscreensaver-data-extra - Update to version 5.37: * New hack vigilance. * Updates of bsod and webcollage. * Bug fixes. - Added vigilance hack to xscreensaver-data-extra.list. - Split -lang package with translations. -- 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] kmail troubling behaviour
by constant＠indo.net.id 15 Aug '17

15 Aug '17

After having troubles with the setup I was using daily for over a year I decided to start a new user. Everything wordked out well except kmail. After the initial setup I could not make new folders. After several trialruns I finaly got some new subfolders who were sticking in place. Lookong into the /.local/share directory I discovered that my mail was not found in akonadi_maildir_resource_0 but found its place in the old kind of /.local-mail.directory. I ran akonadictl fsck and got the feeling that also there was no real information about my mail setup. See for yourself. How to get a functioning kmail? ------------------------------------ > akonadictl fsck Looking for resources in the DB not matching a configured resource... Looking for collections not belonging to a valid resource... Checking collection tree consistency... Looking for items not belonging to a valid collection... Looking for item parts not belonging to a valid item... Looking for item flags not belonging to a valid item... Looking for overlapping external parts... Verifying external parts... Found 0 external files. Found 0 external parts. Found no unreferenced external files. Checking size treshold changes... Found 0 parts to be moved to external files Found 0 parts to be moved to database Looking for dirty objects... Collection "Search" (id: 1) has no RID. Found 1 collections without RID. Found 0 items without RID. Found 0 dirty items. Looking for rid-duplicates not matching the content mime-type of the parent collection Checking Birthdays & Anniversaries Checking Local Folders Checking Notes Checking Personal Contacts Checking Search Checking akonadi_ical_resource_0 Checking commics Checking drafts Checking inbox Checking outbox Checking rotzooi??? Checking sent-mail Checking suse Checking susekde Checking suseot Checking templates Checking trash Migrating parts to new cache hierarchy... Consistency check done. ---------------- -- opensuse:tumbleweed:20170806 Qt: 5.9.1 KDE Frameworks: 5.36.0 kf5-config: 1.0 KDE Pl -- 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] Intentional flatpak downgrade (was: New Tumbleweed snapshot 20170810 released!)
by Robert Munteanu 14 Aug '17

14 Aug '17

Hi, On Sat, Aug 12, 2017 at 4:11 PM, Dominique Leuenberger <dimstar(a)suse.de> wrote: > flatpak (0.9.1 -> 0.8.7) Was this intentional? Same question was asked at [1] but did not get any reply so I'm curious about the reason. Robert [1]: https://build.opensuse.org/request/show/511902 -- http://robert.muntea.nu/ -- 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] DNF package manager packages for openSUSE
by Neal Gompa 14 Aug '17

14 Aug '17

Hey all, As some of you may know, the Fedora community has moved from Yum to DNF for its primary package manager. Like Zypper, it uses libsolv as a dependency resolver. A couple of months back, I requested a devel subproject[1] to work on this from Philipp Thomas. I've now managed to get the core stuff going, and I'd like to start submitting stuff into Factory so that they can be integrated in. The primary reason for having the DNF package manager in openSUSE is for KIWI, actually. The new KIWI supports building Fedora 22+ and Mageia 6+ appliance images, which use the DNF package manager. And of course, the next version of RHEL/CentOS will use this package manager as the default, too. Like the Yum package manager for openSUSE, the DNF package manager is not set up at all to function as the primary package manager, and only enough of the package manager stack was packaged for KIWI and tools like Mock to use. Anyway, I'm not exactly sure how to get my project to be recognized as a valid devel project source for Factory so that things "work" like they should when submitting. Is there anything else that needs to be done, or is sending SRs enough? Thanks in advance, Neal [1]: https://build.opensuse.org/project/show/system:packagemanager:dnf -- 真実はいつも一つ！/ Always, there's only one truth! -- 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] upstream fix only in next version: file openSUSE bug anyway?
by Felix Miata 13 Aug '17

13 Aug '17

Midnight Commander has no "branches". It has current release, and it has GIT. Current TW release version 4.8.19 is broken in manner for which only workarounds are reverting to a non-available version, (4.8.18 was also broken; Leap has only 4.8.15; 4.8.17 was good for me), or self-building (not an option for me). Next release I estimate to occur would be October. I don't find any roadmap for a next relase. Is there any point in filing an openSUSE bug in such a case? Mailing list thread starter: https://mail.gnome.org/archives/mc/2017-August/msg00000.html https://mail.gnome.org/archives/mc/2017-August/msg00003.html points to supposed upstream closed bug, in which I am unable to discern any correlation to the problem I'm encountering: https://midnight-commander.org/ticket/3821 All recent changelog entries for openSUSE's MC package are for same person, who has reported he is no longer providing maintenance on the package. -- "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

2 2