April 2018 - openSUSE Users - openSUSE Mailing Lists

[opensuse] experimental packages
by Dave Howorth 13 Apr '18

13 Apr '18

I'm considering installing mosquitto on my 42.3 system. I'd previously installed it on earlier openSUSE versions from a home repository. So I went to https://software.opensuse.org/package/mosquitto and I see that there are now official releases for Tumbleweed and 15.0, but not for 42.3 or older systems. In addition to various home repositories (listed under community packages), I see there is also a package marked 'experimental'. What exactly is an 'experimental' package? Is it better than a home package or more dangerous? There's no tooltip or other explanation of the meaning on that web page, so I clicked on Documentation which took me to https://doc.opensuse.org/ and then I typed 'experimental package' into the search box and it said 'Unauthorized access to internal API. Please refer to https://support.google.com/customsearch/answer/4542055' which isn't very useful. So I searched for 'opensuse experimental packages' on google, but it shows me lots of hits for particular packages that are 'experimental' but I don't see any definition of what that means. Cheers, Dave PS I did the searches without quotes. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

[opensuse] the kernel version
by George from the tribe 13 Apr '18

13 Apr '18

Ok, I am confused. The last thread talked about the kernel being used in Leap 15 that is coming out, as being kernel 4.12. Then this website that was linked on the thread: http://news.softpedia.com/news/linux-kernel-4-12-reached-end-of-life-users-… talks about how kernel 4.12 has reached end of life and everyone should move to 4.13. So I looked on my desktop running 42.3 with all the latest updates, and this is my kernel: > uname -r 4.4.120-45-default Then I looked on my laptop running 42.3 with all the latest updates as of a week ago, which uses the kernel:stable repository, and this is the kernel it is using: > uname -r 4.15.15-1.g4904fc3-default So if 4.12 has reached end of life, then 4.4 (which is what is available in the distribution repos for 42.3) must be really old. But 4.15, which is available from the kernel:stable repository, is far out in the future and not yet being really developed. My conclusions there must be wrong, but why? Is there something to the way they number the kernels that I am missing here? Does openSUSE have a different numbering scheme than the rest of the linux world? -- George Box: 42.3 | KDE Plasma 5.8 | AMD Phenom IIX4 | 64 | 32GB Laptop #1: 42.3 | Gnome 3.20 | AMD FX 7TH GEN | 64 | 32GB Laptop #2: 42.3 | Gnome 3.20 | Core i5 | 64 | 8GB -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

8 21

[opensuse] Leap-15 Beta 187.1 - Wohoo! GCC 7.3!
by David C. Rankin 13 Apr '18

13 Apr '18

Now we are talking, A shiny new custom install of Leap-15 Beta with Minimal X, via IceWM and Low and Behold GCC 7.3! # gpasswd -a david wheel # visudo ... ## Same thing without a password %wheel ALL=(ALL) NOPASSWD: ALL # vi /etc/pam.d/su ...(see 2 comment lines and 2 additions below) #%PAM-1.0 auth sufficient pam_rootok.so # Uncomment the following line to implicitly trust users in the "wheel" group. auth sufficient pam_wheel.so trust use_uid # Uncomment the following line to require a user to be in the "wheel" group. auth required pam_wheel.so use_uid auth include common-auth account sufficient pam_rootok.so account include common-account password include common-password session include common-session session optional pam_xauth.so # exit $ su # ... (bingo - works fine) # hostname myhostname.mydomain.tld # echo myhostname > /etc/hostname # systemctl reboot ... $ done :) - painlessly, now to finish the KDE3 build... -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

[opensuse] leap15 build 187.1 - zypper up vs zypper dup
by Per Jessen 13 Apr '18

13 Apr '18

Just in case somebody should not be not yet be convinced - this is a diff between the output of "zypper dup" and "zypper up": http://files.jessen.ch/office38-zypper-dup-up.diff 'office38' is a test desktop machine. -- Per Jessen, Zürich (11.9°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 1

[opensuse] Question re security updates (shibboleth-sp)
by Josef Fortier 13 Apr '18

13 Apr '18

Wondering how security updates are handled at the tail of an active cycle. The immediate concern, shibboleth-sp has a security issue in the current package. Looking at software.opensuse.com (hoping there'd be some updated package for opensuse there) I see that Tumbleweed and SLES variants, as well as the (beta) of 15 have updates. More surprisingly openSUSE 12.3 has an update (this seems to be the work of the Shibboleth people). But no package update for Leap. I'd guess this is because 15 is due out in May, but this seems a long time to me. Is there a policy that governs this? Thansk -- __________________________________________________________________________ Josef Fortier Systems Administrator fortier(a)augsburg.edu Phone: 612-330-1479 __________________________________________________________________________ -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 2

[opensuse] Bug fixes in opensuse are somewhat of a bad joke nowadays...
by David C. Rankin 13 Apr '18

13 Apr '18

What Removed Added ----------+----------+---------- status NEW RESOLVED ----------+----------+---------- Resolution --- WONTFIX ----------+----------+---------- Comment # 8 on bug 924818 from Tomáš Chvátal This version of openSUSE changed to end-of-life (EOL [1]) status. As such it is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of openSUSE, or consider the bug still valid, please feel free to reopen this bug against that version, or open a new ticket. Thank you for reporting this bug and we are sorry it could not be fixed during the lifetime of the release. [1] https://en.opensuse.org/Lifetime -------------- Thanks -- that really helped. -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

7 6

[opensuse] leap 15
by jdd＠dodin.org 12 Apr '18

12 Apr '18

hello, is this now the right place to ask about leap 15? I don't want to add factory to my already too large subscription list :-( thanks jdd -- http://dodin.org -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 3

[opensuse] Late to Game, but finally moved to 42.3, clean install a bit awkward, but completes fine.
by David C. Rankin 11 Apr '18

11 Apr '18

All, I finally moved my laptop to 42.3 (even though I booted 42.2 here, because I haven't finished the hours of config still to come...), but nonetheless I have a blazing Leap_42.3 install with a fresh KDE3 desktop, all on 500G of Samsung SSD -- and yes -- the speed difference (especially compiling) is very noticeable. All in all the Leap 42.3 install was.. cumbersome, frustrating, took a bit of coaxing to install what I wanted installed and not what I didn't want, but it worked just fine. The cumbersome part was the inability to add repos prior to the install (or at any point during). This was compounded by the truly insane default partition scheme suggested using btrfs for a user-laptop?? We have dumbed-down the desktop to the point of file managers that have a shadow of the capabilities they provided a decade ago so they are "easier for the new user", but now we somehow expect the newbie to master an enterprise level filesystem notorious for snapshotting all usable space into oblivion? I guess the really smart people see the logic in that, but that logic just escapes us lesser mortals... The good parts of the install, after nuking the btrfs suggestion and the secondary non-native XFS suggestion and dropping back to the wasteful old ext4 that has never lost a file for me in a decade, the remainder went great. Both wired and wireless Intel 82579LM Gigabit Network Connection (wired) and Intel Centrino Ultimate-N 6300 (wireless) -- so kudos to that. A bit more of the cumbersome was completing the entire install in text mode with minimal yast modules present as the frustrating part of the install provided no KDE3 pattern, despite providing every other minor semi-maintained option of enlightenment, lxde, mode, cinnamon, icewm, windowmaker, etc.. You guys have a fantastic option in KDE3 that installs flawlessly, there is no reason not to have a patter for it for install. (enlightenment but KDE?) If you go this route, at least install the X-server and icewm so you will get the full yast. Even installing xterm, firefox, LibreOffice, etc.. still did not pick up the X-server dependency leading to needing to complete the install via out old buddy the yast2 interface (which is quite fine). The other slightly frustrating part (which has been there since at least 7.0) is clicking of a repo and.... waiting while the package info is loaded (and reloaded each time you move up/down the repo list) That and the 'tab-order' of all the text mode controls obviously haven't been revisited since the 10.0 days despite the letters changing. (tabbing reminds me of a pinball machine -- with no hope of shift-tab actually backing up to the previous pane) All-in-all other than the btrfs, awkward desktop pattern selection, and no X-server dependency -- there is not much to complain about. There was no fuss on the network-install connection or package retrieval, it just worked, there are some dependency issue when selecting packages without packman and/or videolan configured. The last surprise was the missing convenience directives in /etc/pam.d/su that no longer provided an easy uncomment to allow users of 'wheel' to su without a password, e.g. # Uncomment the following line to implicitly trust users in the "wheel" group. auth sufficient pam_wheel.so trust use_uid # Uncomment the following line to require a user to be in the "wheel" group. auth required pam_wheel.so use_uid ... the removal may be a security enhancement, but thankfully I have a ssh client on my phone that I could jump on an older install and get the details (heaven know I didn't recall the specifics) Maybe next time I'll take the less painful route of upgrade, but I've done a clean install of every release (other than those I skipped when we were on the 6-month rapid-fire rabbit-pellet release cycles) back in the good ole days (when that steel-trap type logic reared it head in the name of progress) So now I sit with the shiny new ssd as sda and this old platter as sdb in my laptop, just wait to finish the bulk of the install by mounting the other under /mnt and rolling all the needed files and configs back over. (and tweaking the users/groups, etc.) That will be as a time-allows project over the next few days. So good job again. Leap 42.3 installs just fine. Other than the somewhat ironic logic of making things easier for new users while feeding them btrfs there were really no hiccups in the network install. (that speaks well, I don't think I've had a serious install problem in 15 years, sure there are things that could be made better, but the installer still mows the grass) -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

9 43

[opensuse] Its NOT supported
by John Andersen 11 Apr '18

11 Apr '18

But it worked for me. I upgraded from 42.2 directly to Leap 15 without installing 42.3. (Took an extra backup before I started). Everything worked fine. System boots fine, and seems as responsive as ever. (Its an SSD system). There were some dependency conflicts to resolve and I carefully selected the option to switch back to Opensuse packages for almost all the multimedia things I had installed from Packman. (as I've been assured here on this list that Opensuse has ceased sending crippled packages and all those issues are handled like every other distro - it just works). This may have been an error, as I can't get any video to play. Music does play. I'll hunt down this problem later. I half expected this to be the case anyway). The upgrade loaded a boatload of texlive stuff that I did not previously have, and have no use for, but I can clean that up later. -- After all is said and done, more is said than done. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

12 45

[opensuse] how to install viber7 on oS or TW
by Oszkó Albert 11 Apr '18

11 Apr '18

Hi all, I tried to install viber the other day on my laptops, but I met some missing dependencies - like libcrypto.so libssl.so and libpng.so named file. There are files with similar names in /usr/lib64. I tried to soft link them to the names that are expected, but without success. So how to proceed? Thanks, Albert

4 5