July 2015 - openSUSE Factory - openSUSE Mailing Lists

[opensuse-factory] The Name & Version for the new openSUSE Regular Distribution
by Richard Brown 06 Jul '15

06 Jul '15

Hi all, Drum roll please. First we would like to thank everyone who participated in the naming discussion [1][2] for the input and for entrusting the board to bring the process to a conclusion. After due deliberations and consulting with the release and maintenance teams we have decided the name and version of the next release should be openSUSE Leap 42.x We felt that Leap, with reference to motion, i.e. how the distribution moves forward, provides a nice contrast to Tumbleweed. It also represents that we are taking a leap to get there. It does not cast is into a mold that would set the precedence of openSUSE <plant_name> which we think would have encouraged a regular debate as new <plant_names> were considered for each product or release to go with the theme. Finally it leaves the door open for plenty of options should there be other efforts to create an openSUSE release based on Factory snapshots at some point in the future. As far as the version number is concerned we concluded that 42 is a great starting point due to the historical reference in the project. It's quirky and we felt it suits us well. We deliberated other options such as starting at 1.x or some other arbitrary number such as 22 but we preferred 42. Additionally 42 has already gotten some notoriety and thus we might as well stick with it. In the end we all know the number is more or less arbitrary and the important point is that it increases going forward ;) .x is used to indicate the service pack of SLE from which the sources originate. We expect the first release to be 42.1 because we intend to have the release aligned and sharing code with SLE 12 SP1. The major version will increase alongside the major version of the shared SLE sources, therefore a SLE 13 SP2 servicepack based release would be named openSUSE Leap 43.2 Thanks again to everyone for helping out. Special thanks to Rainer Fiebig, a new contributor who after seeing a news article about 'openSUSE 42' joined our mailinglist and proposed this new name for our new baby. Your openSUSE Board [1] http://lists.opensuse.org/opensuse-factory/2015-06/msg00314.html [2] http://lists.opensuse.org/opensuse-project/2015-06/msg00340.html -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

4 4

Re: [opensuse-factory] How to develop the baby
by Mathias Homann 06 Jul '15

06 Jul '15

>> The article basically doesn't make "42" look very good. Less >> drivers, older software, less software than the current 13.2. > > Well if one just looks at the version number that is certainly the conclusion one can draw. However, just a bit below the surface a different picture presents itself. How to communicate this will > certainly be an interesting challenge for the marketing and messaging of Leap. > > However, this discussion is really way of topic and we should stop this part of the thread. not exactly: for my hardware I need to have the latest e1000 drivers, and the latest nvidia drivers. If that is not available for Leap I will stay on 13.2 and re-evaluate that decision when Leap+1 rolls around. ----------------------------------------- This email was sent using SquirrelMail. "Webmail for nuts!" http://squirrelmail.org/ ----------------------------------------- This email was sent using SquirrelMail. "Webmail for nuts!" http://squirrelmail.org/ -- 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] Default btrfs subvolume after a rollback
by Achim Gratz 06 Jul '15

06 Jul '15

6 18

[opensuse-factory] Fwd: Request 315181 changed to declined (submit openSUSE:Factory/calibre)
by Cor Blom 06 Jul '15

06 Jul '15

Can someone tell me why this request was declined? Nothing changed that affects the license. Thanks, Cor -------- Doorgestuurd bericht -------- [...] Visit https://build.opensuse.org/request/show/315181 State of request 315181 was changed by licensedigger: review -> declined Actions: - submit Documentation:Tools/calibre => openSUSE:Factory/calibre -- Configure notifications at https://build.opensuse.org/user/notifications openSUSE Build Service (https://build.opensuse.org/) -- 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] New Tumbleweed snapshot 20150702 released!
by Ludwig Nussel 06 Jul '15

06 Jul '15

Changed packages: ==== android-tools ==== - 51-android.rules: Use TAG+="uaccess" instead of using group/mode access control. ==== ant ==== Subpackages: ant-jmf ant-scripts ant-swing - Do better quoting to get better error messages when it fails ==== ant-junit ==== - Do better quoting to get better error messages when it fails ==== clamav ==== - Make clamd and clamav-milter services depend on freshclam as they need it ==== cron ==== Subpackages: cronie - revert last change, it is a bug in sssd.service, fixed in SR#313709 - add support for MAILFROM, MAIL_CONFIG and different mailer binaries in run-crons (bnc#812367, bnc#366762) - Start cron after sssd.service bnc#926961 - Redo the post/pre update approach to fix migration from SLE11. Should fix bnc#919028 - update to 1.5.0 * crond: Job environment variables are set also when executing sendmail. * crond: Adding duplicate orphans on reload is now prevented. * crond: The regular crond shutdown is now logged. * crontab: PAM is not called in crontab command if the caller's uid is 0. * crond: PAM is not called from crond for system cron jobs (/etc/crontab, /etc/cron.d) which are run for uid 0. * crond: The existence of an user is checked at time when job is run and not when the crontab is parsed on database reload. - use spec-cleaner ==== ipset-kmp-default ==== Version update (6.24_k4.0.5_3 -> 6.25.1_k4.0.5_3) Subpackages: ipset-kmp-desktop ipset-kmp-xen - Update to new upstream release 6.25.1 * Add element count to all set types header * Add element count to hash headers * Support linking libipset to C++ programs * When a single set is destroyed, make sure it cannot be grabbed by dump * Check CIDR value only when attribute is given * Permit CIDR equal to the host address CIDR in IPv6 ==== libedit0 ==== Version update (3.1.snap20141030 -> 3.1.snap20150325) - Cleanup a bit with spec-cleaner * remove pkg_name variable which is equal to name variable - Update to 20150325-3.1 * version info: 0:53:0 * all: sync with upstream source ==== libetonyek-0_1-1 ==== Version update (0.1.2 -> 0.1.3) - Version bump to 0.1.3: * Various small fixes * More imported now imported * Now use mdds to help with some hashing - Remove included patch: * 0001-fix-test-on-i386.patch ==== libgcrypt-devel ==== Subpackages: libgcrypt20 libgcrypt20-32bit - Fix gpg2 tests on BigEndian architectures: s390x ppc64 libgcrypt-1.6.3-aliasing.patch ==== mate-desktop-gsettings-schemas ==== Version update (1.8.1 -> 1.10.0) - Update to version 1.10.0 * Bugfixes release - Remove mate-desktop-no-return-in-nonvoid-function.patch.patch; fixed on upstream release - Update to version 1.9.90 (unstable) * Bugfixes release - Update to version 1.9.4 (unstable) * Turn MateRRScreen, GnomeRRConfig and GnomeOutputInfo into a GObject. * Add gobject introspection * Many RANDR fixes * interface: add automatic-mnemonics key for Gtk xsetting * use GDK_WINDOW_XID for inter-GTK compatibility - Update to version 1.9.3 (unstable) + Updated mpaste for website change - Update to version 1.9.2 (unstable) + Added org.mate.debug GSettings schema - Changes from version 1.9.1 (unstable) + Added MateColorButton class to have traditional color selection dialog with GTK3 - Changes from version 1.9.0 + Removed desktop-docs + Removed user guide + Removed libunique optional dependency + Added MateAboutDialog class to have traditional about dialog with GTK3 too - Remove pkgconfig(unique-1.0) BuildRequires; upstream removed dependency ==== osc ==== Version update (0.151.2 -> 0.152.0) - 0.152.0 - add support searching for groups via "group:" prefix - show possible used incident projects on "maintained" command OBS 2.7 only: - support buildtime source services - support maintenance_incident requests with acceptinfo data - support maintenance_release requests with acceptinfo data ==== p7zip ==== - fixed CVE-2015-1038 [bnc#912878] + p7zip-CVE-2015-1038.patch ==== perl-Archive-Zip ==== Version update (1.46 -> 1.48) - updated to 1.48 see /usr/share/doc/packages/perl-Archive-Zip/Changes 1.48 Thu 18 Jun 2015 - Wrap skip in a SKIP: block [github/plicease] 1.47 Wed 17 Jun 2015 - zip file with a deflated directory cannot be written out again [github/ntyni] - add missing test data to MANIFEST ==== perl-CPAN-Changes ==== Version update (0.400001 -> 0.400002) - updated to 0.400002 see /usr/share/doc/packages/perl-CPAN-Changes/Changes 0.400002 - 2015-06-21 - revert whitespace changes that were inadvertantly included in previous release. - escape curly brackets in test to avoid warning in perl 5.22 ==== perl-Config-IniFiles ==== Version update (2.86 -> 2.87) - updated to 2.87 see /usr/share/doc/packages/perl-Config-IniFiles/Changes ==== perl-DBD-SQLite ==== Version update (1.46 -> 1.48) - updated to 1.48 see /usr/share/doc/packages/perl-DBD-SQLite/Changes 1.48 2015-06-12 - Switched to a production version. (ISHIGAKI) 1.47_05 2015-05-08 - Updated to SQLite 3.8.10 1.47_04 2015-05-02 - Used MY_CXT instead of a global variable 1.47_03 2015-04-16 - Added :all to EXPORT_TAGS in ::Constants 1.47_02 2015-04-16 - Updated to SQLite 3.8.9 - Added DBD::SQLite::Constants, from which you can import any "useful" constants into your applications. - Removed previous Cygwin hack as SQLite 3.8.9 compiles well again - Now create_function/aggregate accepts an extra bit (SQLITE_DETERMINISTIC) for better performance. 1.47_01 2015-02-17 * ** (EXPERIMENTAL) CHANGES THAT MAY POSSIBLY BREAK YOUR OLD APPLICATIONS *** - Commented OPTIMIZE out of WriteMakefile (RT #94207). If your perl is not compiled with -O2, your DBD::SQLite may possibly behave differently under some circumstances. (This release is to find notable examples from CPAN Testers). - Set THREADSAFE to 0 under Cygwin to cope with an upstream regression since 3.8.7 (GH #7). - Updated to SQLite 3.8.8.2 - Resolved #35449: Fast DBH->do (ptushnik, ISHIGAKI) ==== polkit-default-privs ==== - polkit-default-privs: PackageKit (bnc#929212) ==== gvim ==== Version update (7.4.729 -> 7.4.763) Subpackages: vim vim-data - Updated to revision 763, fixes the following problems * Appending in Visual mode with 'linebreak' set does not work properly. Also when 'selection' is "exclusive". (Ingo Karkat) * Using CTRL-A in Visual mode does not work well. (Gary Johnson) * It is not easy to count the number of characters. * Cannot detect the background color of a terminal. * When 'conceallevel' is 1 and quitting the command-line window with CTRL-C the first character ':' is erased. * Spelling mistakes are not displayed after ":syn spell". * The request-background termcode implementation is incomplete. * Comment for may_req_bg_color() is wrong. (Christ van Willegen) - Updated to revision 752, fixes the following problems * When setting the crypt key and using a swap file, text may be encrypted twice or unencrypted text remains in the swap file. * The tab menu shows "Close tab" even when it doesn't work. * The cursor line is not always updated for the "O" command. * ml_get error when using "p" in a Visual selection in the last line. * Wrong argument for sizeof(). * In a string "\U" only takes 4 digits, while after CTRL-V U eight digits can be used. * ":1quit" works like ":.quit". (Bohr Shaw) * When using += with ":set" a trailing comma is not recognized. (Issue 365) * Cannot specify a vertical split when loading a buffer for a quickfix command. * "p" in Visual mode causes an unexpected line split. * No tests for Ruby and Perl. * The entries added by matchaddpos() are returned by getmatches() but can't be set with setmatches(). (Lcd) * ":[count]tag" is not always working. (cs86661) * ":cnext" may jump to the wrong column when setting 'virtualedit=all' * For some options two consecutive commas are OK. (Nikolay Pavlov) * It is not obvious how to enable the address sanitizer. * Unicode 8.0 not supported. ==== vsftpd ==== - Fix logrotate script to not fail when vsftpd is not running, bnc#935279 ==== x11-tools ==== - Xim script: Allow to simply touch an empty ~/.i18n to override ~/.profile or ~/.login. Also make sure that all bourne shells are able to export the variables like INPUT_METHOD. - Xim script: Allow background processes in ~/.profile and ~/.login (bsc#934720) also use ~/.i18n of exist instead of ~/.profile or ~/.login Removed packages: Added packages: pullin-bcm43xx-firmware -- 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] flash-player update
by Fabian Niepelt 05 Jul '15

05 Jul '15

Hello list, Firefox has been complaining about an insecure flash-player version for a while now. I've been ignoring it for the most part and just did a zypper up every day in wait for a newer version. Now I am growing suspicious, there should be new version by now and a search on software.opensuse.org confirms my suspicion. There, the official flash-player version is said to be 11.2.202.468 for Tumbleweed. zypper info flash-player says, I've got 11.2.202.457-1.1. So why is zypper not seeing the update? I'm using the default non-free repo that came with the installation, that is http://download.opensuse.org/tumbleweed/repo/non-oss/ . Shouldn't the website reflect the state of the default repositories when the mentioned version is declared "Official"? Greetings Fabian -- 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] kscreenlocker_greet crashes
by Michael Harnden 05 Jul '15

05 Jul '15

Hi, I need some help in where to start with kscreenlocker_greet crashes. Running tumbleweed with the latest updates. Frameworks Version 5.10.0 Plasma 5-workspace 5.31-3.1 NVidia driver 352.21 I can start the computer and use my account with no problem. As soon as my wife brings up sddm to initiate a new session, I am seeing this in journalctl; Jul 05 17:07:35 den QSGRenderThread[30196]: <audit-1701> auid=1000 uid=1000 gid=100 ses=7 pid=30196 comm="QSGRenderThread" exe="/usr/lib64/libexec/kscreenlocker_greet" sig=11 This is repeated until the login process is completed. This repeats until she logs in. She can then use her account. When I switch back to my account, kscreenlocker_greet begins to crash and respawn. This pegs two of my cpu's to 100% and I receive the following in journalctl. Jul 05 15:09:20 den kscreenlocker_g[7866]: <audit-1701> auid=1001 uid=1001 gid=100 ses=3 pid=7866 comm="kscreenlocker_g" exe="/usr/lib64/libexec/kscreenlocker_gree Jul 05 15:09:20 den kscreenlocker_g[7867]: <audit-1701> auid=1001 uid=1001 gid=100 ses=3 pid=7867 comm="kscreenlocker_g" exe="/usr/lib64/libexec/kscreenlocker_gree Jul 05 15:09:20 den kscreenlocker_g[7868]: <audit-1701> auid=1001 uid=1001 gid=100 ses=3 pid=7868 comm="kscreenlocker_g" exe="/usr/lib64/libexec/kscreenlocker_gree Jul 05 15:09:20 den kscreenlocker_g[7869]: <audit-1701> auid=1001 uid=1001 gid=100 ses=3 pid=7869 comm="kscreenlocker_g" exe="/usr/lib64/libexec/kscreenlocker_gree Jul 05 15:09:20 den kscreenlocker_g[7870]: <audit-1701> auid=1001 uid=1001 gid=100 ses=3 pid=7870 comm="kscreenlocker_g" exe="/usr/lib64/libexec/kscreenlocker_gree Jul 05 15:09:20 den kscreenlocker_g[7871]: <audit-1701> auid=1001 uid=1001 gid=100 ses=3 pid=7871 comm="kscreenlocker_g" exe="/usr/lib64/libexec/kscreenlocker_gree Jul 05 15:09:20 den kscreenlocker_g[7872]: <audit-1701> auid=1001 uid=1001 gid=100 ses=3 pid=7872 comm="kscreenlocker_g" exe="/usr/lib64/libexec/kscreenlocker_gree Jul 05 15:09:20 den kscreenlocker_g[7873]: <audit-1701> auid=1001 uid=1001 gid=100 ses=3 pid=7873 comm="kscreenlocker_g" exe="/usr/lib64/libexec/kscreenlocker_gree As you can see, it's about 8 times a second. If I kill all of her running processes, then I get; At this point, you cannot switch users or initiate a new session. This started when I moved to Tumbleweed from 13.2. I thought that maybe there was some stray config file that was mucking things up, so I installed Tumbleweed fresh, with newly created user accounts. With the same results. Any hints on where to start? Thanks, Mike -- 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] cryptsetup in rescue as well as in dracut do not work
by Dr. Werner Fink 05 Jul '15

05 Jul '15

Hi, during debugging I had done an update of dracut which had lead to a broken initrd which does not ask for passphrase anymore. After trying the rescue mode of the latest Factory ISO image I've seen that cryptsetup open --type luks /dev/sda2 myroot ask the passphrase and then hanges around for ever. After switching back to the oS 13.2 ISO image I was able to use the same command followed by vgscan and vgchange -a y. After downloading http://download.opensuse.org/update/13.2/x86_64/dracut-037-17.6.1_17.12.1.x… and forced installation of the old dracut the system is up and running again. In other words: both dracut of Factory as well as rescue mode of Factory are not able to handle encrypted root devices from a former 13.2. Werner -- "Having a smoking section in a restaurant is like having a peeing section in a swimming pool." -- Edward Burr

4 4

[opensuse-factory] How to name the baby
by Robert Schweikert 05 Jul '15

05 Jul '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Oh no, not another lengthy thread.... I am afraid it is going to be, but hopefully we can stick to the topic and only focus on the name. A brief summary: Stephan as the release manager has decided that he will concentrate on building a distribution around the project known as openSUSE:42. In [1] he also tried to start the discussion about the naming of the new distro. However, this did get sidetracked rather quickly, thus, please focus on naming only. - - Not all questions for the new release have been answered, we do not need to revisit this. Some answers will only emerge as the baby starts to crawl and then walk.... - - Just because Stephan will take on the release manager responsibilities of a distro around the SLE sources does not preclude another person or team to build/release... a distro based on Factory snapshots. As the distribution is a representation of the project as a whole, i.e. all contributors, I think it is fair that people get an opportunity to weigh in with their concerns. This view may not be shared by everyone, so please bare with the rest of us as your mailbox once again fills up ;) However, to those participating in the discussion please focus on the name not on side issues. It has been advocated in other threads that a vote on the name should be considered as the final solution. There are reasonable arguments for and against such a direction. Thus, lets not focus on the voting part at this point either, lets just focus on the name and see where the discussion goes. If this should or should not be voted on can be a separate discussion once we collectively understand the concerns people have with respect to the name. In a "thread renaming" post we have had the following suggestion: * openSUSE Oak """" So how about Oak? It's a solid tree, it fits with the green theme and it will give us: * openSUSE Tumbleweed * openSUSE Oak """" "openSLES" has also been suggested a few times but lets just say that we will probably run afoul with a number of legal restrictions. Plus it is not really SLES, it is based on SLES sources and not a verbatim build of the SLES sources. My suggestion would be to focus on the name while considering that we should not create a name that would produce a potential conflict as described in [2], also consider the reply [3] So please lets focus on the name the child might have. State your case for the name you propose, include in the proposal a numbering scheme, if you think we should stick with numbers. Staring at 1 for a numbering scheme has rather obvious disadvantages, all other numbers are probably equally arbitrary, but you can certainly state the case why the number being proposed is favorable. I propose the above as the guidelines for the naming discussion. I will add my personal opinion about the name as a follow up post. Lets see if I can manage to stay within my own proposed guidelines ;) I apologize to those that are subscribed to both the -factory and the - -project list. However I know that there are a number of people that are not following -project but follow -factory, thus the cross post. As I mentioned, I believe that the distribution represents all of us and thus everyone should have their chance to weigh in on the name given to the baby that represents the community. Let the fun begin. Robert [1] http://lists.opensuse.org/opensuse-factory/2015-06/msg00203.html [2] http://lists.opensuse.org/opensuse-project/2015-06/msg00278.html [3] http://lists.opensuse.org/opensuse-project/2015-06/msg00280.html - -- Robert Schweikert MAY THE SOURCE BE WITH YOU Public Cloud Architect LINUX rjschwei(a)suse.com IRC: robjo -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBAgAGBQJVgJlWAAoJEE4FgL32d2UkO9gH/i/TzZ9ayW2m2LAOryTk1mPT 4nViWBbxPH9NA1QVMlTc+bGpauuny7VWDz1GSZgF6aNXu8RQA+FJ914H3DOOiGJP C8y8Ik2aLikWOjVU/ZkF9F3YOY/Qt/gdia1LVJQnz5l5EsA98vjLpjNjV3grDlTy jmwogwCrR8WUoPx2YPompuqxePeZTjNFcQpa5i76TQhXj+afX5FKKVxSlWQlra8Q iS+h/3ke+28hUvAAeSQk3ufbfiuSN+93JX7R01N/Ni+03KX5CR0asTk+Go2KZ91F aQnaEXNeWWVyAB21GOcAe5m5duKWgkB59A0Wu3EjiS4Y+2+kRssZ38dF8Y/dLrI= =183F -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

25 59

[opensuse-factory] Force non-interactive fsck on btrfs / at next reboot
by Moby 05 Jul '15

05 Jul '15

OSS 13.2 tumbleweed with kernel 4.1.1-1.ga46abf6-desktop and btrfs-progs v4.1+20150622. Storage is all one big btrfs /. How can one setup the system to run a fsck, and non-interactively repair any errors, at the next reboot? All I can find on The Net is the touch /forcefsck stuff which does not seem to work at all. Thanks in advance for any help, -- --Moby -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

4 5