February 2017 - openSUSE Factory - openSUSE Mailing Lists

[opensuse-factory] boost update and the great -devel split
by Adam Majer 03 Feb '17

03 Feb '17

Hello, Some of you may have noticed some submit requests for packages that BuildRequire: boost-devel. As of current Boost (1.63.0), the boost-devel subpackage has been split into individual libboost-*-devel subpackages. The reason for the split up is to reduce the giant dependency tree that Boost pulls in because of boost-devel. As an example. libboost_graph-devel is only required by 1 package in Factory and libboost_graph_parallel-devel is not required by anything. The latter pulls in the entire OpenMPI stack, and and this happened for every single build of anything that used any part of Boost! Splitting this up allows us to greatly reduce this dependency tree in shipped products. For now, boost-devel continues to exist in Factory, but please avoid using it in new packages. So, what are the few new packages? libboost_headers-devel libboost_atomic-devel libboost_chrono-devel libboost_container-devel libboost_context-devel libboost_coroutine-devel libboost_date_time-devel libboost_fiber-devel libboost_filesystem-devel libboost_graph-devel libboost_iostreams-devel libboost_locale-devel libboost_log-devel libboost_math-devel libboost_graph_parallel-devel libboost_mpi-devel libboost_program_options-devel libboost_python-py2_7-devel libboost_python-py3-devel libboost_random-devel libboost_regex-devel libboost_serialization-devel libboost_signals-devel libboost_system-devel libboost_test-devel libboost_thread-devel libboost_timer-devel libboost_type_erasure-devel libboost_wave-devel Quite a lot of software is only using header-only boost libraries, which means libboost_headers-devel is enough to get it to build. Currently I'm working through the list of about 200 packages that BuildRequire: boost-devel and changing these to an appropriate subset of these new subpackages. If your package BuildRequires: boost-devel and it's in Factory, I'll probably get to it in the next 24h and provide you with a submit request. Additionally, Boost package now provides full support for Python 3 as well as Python 2.7. This includes newly packaged Boost::MPI bindings for both python versions. Enjoy! - Adam -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

4 8

[opensuse-factory] Re: How to reindex akonadi database without having to reconfigure?
by ianseeks 03 Feb '17

03 Feb '17

On Thursday, 2 February 2017 09:45:59 GMT Martin Steigerwald wrote: > Am Donnerstag, 2. Februar 2017, 07:56:16 CET schrieb ianseeks: > > Hi > > > > I'm having the "Retrieving folder..." error message on every folder that > > contains an unread item. Akonadi fsck/vacuum/top/start no longer fixes the > > problem. > > I have in the past followed the how to fix akonadi when there was a failed > > migration and that did all the work but it seemed like a hammer to crack a > > nut as you have to reconfigure kmail etc. > > > > Is there a way to just delete the data and any related indexes to force a > > reindexing process? > > > > I'm running out of ideas hence i hope this idea may help > > Did you try "Clear Akonadi Cache" on one of the folders in question in > Akonadiconsole. As far as I understand this is a partial clearing of the > cache which forces Akonadi to redo the cache for the particular folder. > > I bet I´d do it in the following order: > > 1) make sure you have backup > 2) stop Kmail > 3) stop Akonadi > 4) make sure database process is gone > 5) start Akonadiconsole > 6) clear cache of one folder > 7) start kmail and test result That made no difference > As far as I understand you maybe could loose data with doing that, just as > you can loose data with removing the complete database, cause while Akonadi > is mostly a cache, there can be circumstances where it contains more than > only cached items, i.e. when an IMAP server is not reachable to add a newly > written mail into the sent folder… (but on that I also found that the sent > mail was stored into the local sent mail folder instead). > > I do not know exactly whether the data loss risk is only when you wipe the > whole database, or also when you clear only the cache of one folder, but I > warned you :) > > Also I believe there was a recent bug which caused Retrieving folder > contents displayed forever… you could research that. I am still using > KDEPIM 16.04 as Debian has nothing newer packaged due to challenges and > difficulties packaging Qt Webengine with Debian quality standards. I've been suffereing that for quite a while and it got to the point where every folder i opened gave me that message, its taken about 12 hours for trying things to be able to reply to your email > Also what I believed helped timeouts a lot is raising InnoDB buffer pool > size *a lot*. I raised it to 1 GiB. Mysqltuner.pl recommended even more. > But keep the amount of free memory on your system in mind. Whether that > helps you or not mostly depends on whether Akonadi is waiting on mysqld to > complete the queries it floods it with. That might help, i'll try that. I've deleted a lot of emails prior to 2016 and that seems to have made it possible for me to do some work again. > Thanks, Thanks for the reply -- opensuse:tumbleweed:20170131 Qt: 5.7.1 KDE Frameworks: 5.30.0 KDE Plasma: 5.9.0 kwin5-5.9.0-1.1.x86_64 kmail2 5.4.1 Kernel: 4.9.6-1-default Nouveau: 1.0.13_2.2 -- 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] KMail crashing on start with: Could not create collection trash, resourceId: 2
by Chan Ju Ping 03 Feb '17

03 Feb '17

Upon starting Kontact or KMail iva the terminal, the following warning occurs before crashing: org.kde.pim.akonadicore: Failed SpecialCollectionsRequestJob::slotResult "Could not create collection trash, resourceId: 2" org.kde.pim.mailcommon: "The Email program encountered a fatal error and will terminate now.\nThe error was:\nCould not create collection trash, resourceId: 2" Has anyone encountered this error before and how would I fix it?

3 3

[opensuse-factory] New Tumbleweed snapshot 20170201 released!
by Dominique Leuenberger 03 Feb '17

03 Feb '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: blog build (20161206 -> 20170112) ca-certificates-mozilla (2.7 -> 2.11) elilo gcc geany-plugins (1.28 -> 1.29) gpg2 (2.1.17 -> 2.1.18) grub2 libisoburn (1.4.4 -> 1.4.6) libvirt-python (2.5.0 -> 3.0.0) llvm3_9 mirror perl-Bootloader (0.916 -> 0.917) tgt === Details === ==== blog ==== - Use github source from tagged version - Use https://github.com/bitstreamout/showconsole as URL ==== build ==== Version update (20161206 -> 20170112) Subpackages: build-mkbaselibs build-mkdrpms - fix haskell builds (bsc#1018895) - fix multi type kiwi profile handling - minor distribution config and bug fixes ==== ca-certificates-mozilla ==== Version update (2.7 -> 2.11) - updated to 2.11 state of the Mozilla NSS Certificate store. - removed CAs: - Buypass_Class_2_CA_1:2.1.1.crt serverAuth - EBG_Elektronik_Sertifika_Hizmet_Sa?lay?c?s?:2.8.76.175.115.66.28.142.116.2.crt codeSigning emailProtection serverAuth - Equifax_Secure_CA:2.4.53.222.244.207.crt emailProtection - Equifax_Secure_eBusiness_CA_1:2.1.4.crt emailProtection - Equifax_Secure_Global_eBusiness_CA:2.1.1.crt emailProtection - IGC_A:2.5.57.17.69.16.148.crt codeSigning emailProtection serverAuth - Juur-SK:2.4.59.142.75.252.crt codeSigning serverAuth - Root_CA_Generalitat_Valenciana:2.4.59.69.229.104.crt codeSigning emailProtection serverAuth - RSA_Security_2048_v3:2.16.10.1.1.1.0.0.2.124.0.0.0.10.0.0.0.2.crt codeSigning emailProtection serverAuth - Sonera_Class_1_Root_CA:2.1.36.crt emailProtection - S-TRUST_Authentication_and_Encryption_Root_CA_2005_PN:2.16.55.25.24.230.83.84.124.26.181.184.203.89.90.219.53.183.crt emailProtection - Verisign_Class_1_Public_Primary_Certification_Authority:2.16.63.105.30.129.156.240.154.74.243.115.255.185.72.162.228.221.crt emailProtection - Verisign_Class_2_Public_Primary_Certification_Authority_-_G2:2.17.0.185.47.96.204.136.159.161.122.70.9.184.91.112.108.138.175.crt emailProtection - Verisign_Class_3_Public_Primary_Certification_Authority:2.16.112.186.228.29.16.217.41.52.182.56.202.123.3.204.186.191.crt emailProtection - added CAs: + AC_RAIZ_FNMT-RCM:2.15.93.147.141.48.103.54.200.6.29.26.199.84.132.105.7.crt serverAuth + Amazon_Root_CA_1:2.19.6.108.159.207.153.191.140.10.57.226.240.120.138.67.230.150.54.91.202.crt emailProtection serverAuth + Amazon_Root_CA_2:2.19.6.108.159.210.150.53.134.159.10.15.229.134.120.248.91.38.187.138.55.crt emailProtection serverAuth + Amazon_Root_CA_3:2.19.6.108.159.213.116.151.54.102.63.59.11.154.217.232.158.118.3.242.74.crt emailProtection serverAuth + Amazon_Root_CA_4:2.19.6.108.159.215.193.187.16.76.41.67.229.113.123.123.44.200.26.193.14.crt emailProtection serverAuth + Certplus_Root_CA_G1:2.18.17.32.85.131.228.45.62.84.86.133.45.131.55.183.44.220.70.17.crt emailProtection serverAuth + Certplus_Root_CA_G2:2.18.17.32.217.145.206.174.163.232.197.231.255.233.2.175.207.115.188.85.crt emailProtection serverAuth + Hellenic_Academic_and_Research_Institutions_ECC_RootCA_2015:2.1.0.crt emailProtection serverAuth + Hellenic_Academic_and_Research_Institutions_RootCA_2015:2.1.0.crt emailProtection serverAuth + ISRG_Root_X1:2.17.0.130.16.207.176.210.64.227.89.68.99.224.187.99.130.139.0.crt (bsc#1010996) serverAuth + LuxTrust_Global_Root_2:2.20.10.126.166.223.75.68.158.218.106.36.133.158.230.184.21.211.22.127.187.177.crt serverAuth + OpenTrust_Root_CA_G1:2.18.17.32.179.144.85.57.125.127.54.109.100.194.167.159.107.99.142.103.crt emailProtection serverAuth + OpenTrust_Root_CA_G2:2.18.17.32.161.105.27.191.189.185.189.82.150.143.35.232.72.191.38.17.crt emailProtection serverAuth + OpenTrust_Root_CA_G3:2.18.17.32.230.248.76.252.36.176.190.5.64.172.218.131.27.52.96.63.crt emailProtection serverAuth + Symantec_Class_1_Public_Primary_Certification_Authority_-_G4:2.16.33.110.51.165.203.211.136.164.111.41.7.180.39.60.196.216.crt emailProtection + Symantec_Class_1_Public_Primary_Certification_Authority_-_G6:2.16.36.50.117.242.29.47.210.9.51.247.180.106.202.208.243.152.crt emailProtection + Symantec_Class_2_Public_Primary_Certification_Authority_-_G4:2.16.52.23.101.18.64.59.183.86.128.45.128.203.121.85.166.30.crt emailProtection + Symantec_Class_2_Public_Primary_Certification_Authority_-_G6:2.16.100.130.158.252.55.30.116.93.252.151.255.151.200.177.255.65.crt emailProtection - diff-from-upstream-2.7.patch: removed as we should be able to do intermediate root chains now with openssl 1.0.2 and also gnutls 3.5 is able to do so. ==== elilo ==== - Do not include rebuild counter in rpm to make build-compare happy ==== gcc ==== Subpackages: cpp gcc-c++ gcc-fortran gcc-info gcc-objc libstdc++-devel - Remove java related packages, those are in a separate gcc-java now. ==== geany-plugins ==== Version update (1.28 -> 1.29) Subpackages: geany-plugins-lang - Update to version 1.29 (boo#1022222): + General: - Rename plugin GeanyLipsum to Lipsum (gh#geany/geany-plugins#472). + Addons: - Add a function to deselect marked words with one click (gh#geany/geany-plugins#481). + Commander: - Add keybindings for triggering a particular filter type (gh#geany/geany-plugins#468). + GeanyGenDoc: - Fix typos in README (gh#geany/geany-plugins#476). + Git-Changebar: - Fix an issue access the git repository in combination with libgit2 0.24.2. - Fix an off-by-one issue in tooltip hunk width calculation cropping 1px on the right. - Fix handling of documents starting with a BOM (gh#geany/geany-plugins#483, gh#geany/geany-plugins#482). + Spellcheck: - Strip single quotes from words' beginning and end (gh#geany/geany-plugins#484). - Fix a memory leak on duplicate dictionaries (gh#geany/geany-plugins#480). + Treebrowser: - Fix a typo in configuration parsing causing option for "open new files" have not being save/restored correctly (gh#geany/geany-plugins/#469, gh#geany/geany-plugins#473). + Updated translations. ==== gpg2 ==== Version update (2.1.17 -> 2.1.18) - GnuPG 2.1.18: * gpg: Remove bogus subkey signature while cleaning a key (with export-clean, import-clean, or --edit-key's sub-command clean) * gpg: Allow freezing the clock with --faked-system-time. * gpg: New --export-option flag "backup", new --import-option flag "restore". * gpg-agent: Fixed long delay due to a regression in the progress callback code. * scd: Lots of code cleanup and internal changes. * scd: Improved the internal CCID driver. * dirmngr: Fixed problem with the DNS glue code (removal of the trailing dot in domain names). * dirmngr: Make sure that Tor is actually enabled after changing the conf file and sending SIGHUP or "gpgconf --reload dirmngr". * dirmngr: Fixed Tor access to IPv6 addresses. Note that current versions of Tor may require that the flag "IPv6Traffic" is used with the option "SocksPort" in torrc to actually allow IPv6 traffic. * dirmngr: Fixed HKP for literally given IPv6 addresses. * dirmngr: Enabled reverse DNS lookups via Tor. * dirmngr: Added experimental SRV record lookup for WKD. See commit 88dc3af3d4ae1afe1d5e136bc4c38bc4e7d4cd10 for details. * dirmngr: For HKP use "pgpkey-hkps" and "pgpkey-hkp" in SRV record lookups. Avoid SRV record lookup when a port is explicitly specified. This fixes a regression from the 1.4 and 2.0 behavior. * dirmngr: Gracefully handle a missing /etc/nsswitch.conf. Ignore negation terms (e.g. "[!UNAVAIL=return]" instead of bailing out. * dirmngr: Better debug output for flags "dns" and "network". * dirmngr: On reload mark all known HKP servers alive. * gpgconf: Allow keyword "all" for --launch, --kill, and --reload. * tools: gpg-wks-client now ignores a missing policy file on the server. * Avoid unnecessary ambiguity error message in the option parsing. * Further improvements of the regression test suite. * Fixed building with --disable-libdns configure option. * Fixed a crash running the tests on 32 bit architectures. * Fixed spurious failures on BSD system in the spawn functions. This affected for example gpg-wks-client and gpgconf. ==== grub2 ==== Subpackages: grub2-i386-pc grub2-snapper-plugin grub2-systemd-sleep-plugin grub2-x86_64-efi grub2-x86_64-xen - info-dir-entry.patch: Update info dir entry to follow renaming to grub2 ==== libisoburn ==== Version update (1.4.4 -> 1.4.6) Subpackages: libisoburn1 xorriso - Update to 1.4.6: * Bug fix: The default setting of -compliance did not apply rec_mtime to Joliet and ISO:1999. mkisofs emulation was not affected by this bug. * Bug fix: -file_size_limit did not increase ISO level if necessary. Thanks Mattias Schlenker. * New API calls isoburn_igopt_set_gpt_guid(), isoburn_igopt_get_gpt_guid() * New command -use_immed_bit, new -as cdrecord option use_immed_bit= * New -volume_date mode "all_file_dates" * New -as mkisofs option --set_all_file_dates * New bootspec "gpt_disk_guid=", new -as mkisofs option - -gpt_disk_guid * New -report_system_area modes "gpt_disk_guid", "make_guid" * New environment variable SOURCE_DATE_EPOCH * New -find action "set_to_mtime" ==== libvirt-python ==== Version update (2.5.0 -> 3.0.0) - Update to 3.0.0 - Add all new APIs and constants in libvirt 3.0.0 ==== llvm3_9 ==== - libc++ must depend on libc++abi - Stop using otherproviders() due to an rpm parser bug, use self-conflicts instead as suggested by mls. ==== mirror ==== - Cleanup with spec-cleaner, use sane description bsc#1022798 - Refresh patches to use unified diff: * dont-build-as-root.diff * mirror-2.9.gzip.patch * mirror-2.9.name_map-default.patch * mirror-2.9.patch * mirror-2.9.y2k-fix.patch * mirror-exec-path.dif * mirror-timelocal.patch * mirror-2.9.ftp-ls-timeout.patch ==== perl-Bootloader ==== Version update (0.916 -> 0.917) - grub2: drop trailing space from saved entry - grub2: parse initrd (bsc#1007335) - 0.917 ==== tgt ==== - Adding documentation files to SPEC file to silence rpmlint -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

1 0

Re: [opensuse-factory] Next snapshot with updated systemd and plymouth
by Robby Engelmann 02 Feb '17

02 Feb '17

Ohh, there are more than that one. I remember, that I also commented on one of these: no graphical input, instead textmode input is shown. The question is, whether these are indeed related... This time, no imput is shown at all (here in approx. 20% of the reboots). Cheers, Robby. -- On Dienstag, 31. Januar 2017 15:55:56 CET Jeroen Mathon wrote: > Hey Robby, > > It seems that Chan Ju Ping also made a bug report in 2016. > > https://bugzilla.opensuse.org/show_bug.cgi?id=997200 > > Perhaps also worth looking at or marking as duplicate to avoid people > recreating the wheel. > > On 31-01-17 15:48, Robby Engelmann wrote: > > You may want to have a look here: > > https://bugzilla.novell.com/show_bug.cgi?id=1020283

19 35

[opensuse-factory] systemd 232 makes problems on updated systems
by Rainer Klier 02 Feb '17

02 Feb '17

hi all, i have a tumbleweed x86_64 system which was installed years ago as 13.1. after installation i upgraded to every new opensuse release. i never did a new/fresh install. and this approach worked very well. then i upgraded/changed to tumbleweed. also without big problems. now systemd 232 is available for tumbleweed. i updated and then systemd-journald.service and other didn't work any more. downgrading back to systemd 228 made it work again. then i made a diff from 232 version of /usr/lib/systemd/system/systemd-journald.service with the version from 228. and there are 4 lines which are only in the 232 version: MemoryDenyWriteExecute=yes RestrictRealtime=yes RestrictAddressFamilies=AF_UNIX AF_NETLINK SystemCallFilter=~@clock @cpu-emulation @debug @keyring @module @mount @obsolete @raw-io i found all the service files in /etc/systemd /usr/lib/systemd which use these new properties and commented them out in all service files. and then, everything again works like expected. on another notebook, i freshly installed tumbleweed, of course with systemd 232 from the beginning. and this system didn't have any problems with it. so, WHY does the upgraded/updated system has problems with these new systemd properties??? does anybody know anything about this? -- Best Regards | Freundliche Grüße | Cordialement | Cordiali Saluti | *DI Rainer Klier* Research & Development, DevOps Namirial GmbH -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

3 5

[opensuse-factory] rpmlint warning for no dependencies needed
by Dave Plater 02 Feb '17

02 Feb '17

Hi, I found a package that had been converted from wxWidgets-2.8 which needed manual requires, to wxWidgets3 which works with rpm automatic find requires and the manual requires macro failed but the package still built with an empty requires. see: openSUSE:Leap:42.2 wxhexeditor. IMHO there should at least be an rpmlint warning for a binary package that builds with no requires, this is possibly the cause of https://bugzilla.opensuse.org/show_bug.cgi?id=1022460 . I wonder if there are anymore packages out there that also have this problem, does anyone know how to search for them? Thanks Dave P (user plater) -- 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] add pam_faillock for factory, 42.2, SLES 12 SP2
by Jason Newton 02 Feb '17

02 Feb '17

I'd consider adding it as an update, too, to 42.1 and SP1, at least in aux repositories - preferably to updates :-). I've spoken with the author of pam_faillock and I believe it to be superior to pam_tally2, particularly concerning handling of screensaver handling. pam_faillock is part of the recommended RHEL configuration for secured computers and holding out for pam_tally2 also presents a nasty non-uniformity for nearly the same functionality (although, weaker). I've asked the author, Tomas Mraz, to make the patch available standalone - which he has provided here: http://people.redhat.com/tmraz/pam_faillock/ I would've have submitted my branch against factory pam incorporating the patch - but unfortunately I seem to be having some automake/libtool issues in the build that I cannot figure out - so I'm going to have to leave that effort to someone who knows those build tools better than I. I also intend to poke upstream to ask them to reconsider adding that patch into master. -Jason -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

3 7

[opensuse-factory] Tumbleweed on rsync.opensuse.org
by mh＠mike.franken.de 02 Feb '17

02 Feb '17

Hi *, is there any reason, why rsync.opensuse.org::opensuse-full/opensuse/tumbleweed/ does not offer the latest Tumbleweed packages, while I can find them on ftp.gwdg.de::opensuse/tumbleweed/ ?? rsync.opensuse.org latest versions are from 28.12.2016. In the meantime there were lots of new packages. Thx and bye. Michael. -- Michael Hirmke -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

5 8

[opensuse-factory] nm-applet fails to start
by Michael Ströder 01 Feb '17

01 Feb '17

HI! After a recent Tumbleweed update on one notebook I can't get nm-applet running anymore: --------------------------- snip --------------------------- $ nm-applet (nm-applet:2581): GLib-GIO-ERROR **: Settings schema 'org.gnome.nm-applet' is not installed Trace/Breakpoint ausgelöst (core dumped) --------------------------- snip --------------------------- Any hint what's missing here? Thanks in advance. Ciao, Michael.

4 7