July 2017 - openSUSE Factory - openSUSE Mailing Lists

[opensuse-factory] Recommended and *-lang packages conflict (dup and not only)
by Mykola Krachkovsky 23 Jul '17

23 Jul '17

Hi, So ATM correct way to update Tubleweed considered zypper dup I'm usually using zypper dup --no-recommends Because a lot of packages I don't need are recommended for install (like Mesa- dri-nouveau, some texlive packages, etc.) But there is a conflict — this way will not install matching -lang package (if it would be added). And now I've even got a proposition for deletion of gstreamer-lang. Why? Is any possibility to care for -lang packages but ignore recommended? Yes, I can mark that hundreds of packages taboo, but it's boring. -- Kind regards, Mykola Krachkovsky -- Найкращі побажання, Микола Крачковський

3 9

[opensuse-factory] Missing download help on download page.
by Carlos E. R. 23 Jul '17

23 Jul '17

Hi, with the coming release of Lep 42.3 I notice that the download page got a new face: https://software.opensuse.org/distributions/leap https://software.opensuse.org/distributions/tumbleweed I see there is a table with links on how to burn the ISO on different operating systems. But there is no info on how to download the image. There is some help on how to verify the image. Previously there was extensive info on this. It is still here, hidden: https://en.opensuse.org/SDB:Download_help -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)

2 1

[opensuse-factory] my impression
by James 22 Jul '17

22 Jul '17

This is the impression I had of this list: https://en.opensuse.org/Portal:Factory -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

15 35

[opensuse-factory] 42.3/Plasma yast2-online-update installed but missing from YaST2 Control Center
by Felix Miata 22 Jul '17

22 Jul '17

Plasma5 is default DE on desktop PC. Others installed are Mate and IceWM. yast2-online-update 3.1.11-8.3 is installed. plasma5-pk-updates is not. YCC has only 3 items in software: media check, repos & management. Is YOU somehow disabled or hidden until after 42.3 gets officially released? Is plasma5-pk-updates going to be the preferred automatic updater for Plasma users in 42.3? If not, what is or will be? Is release still expected last week of this month as stated on https://en.opensuse.org/openSUSE:Roadmap ? -- "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

4 7

[opensuse-factory] BLAS implementations
by Dmitry Roshchin 21 Jul '17

21 Jul '17

BLAS (Basic Linear Algebra Subprograms) is a library that provides standard blocks for performing basic vector and matrix operations. Currently openSUSE uses reference BLAS/LAPACK implementations from netlib by default. This versions are very stable, but not fast. There are optimized implementations: opensource - openBLAS, Atlas and proprietary - Intel MKL, AMD CML. openSUSE repositories contain only openBLAS. We have update-alternatives mechanism for choosing BLAS implementations: /usr/sbin/update-alternatives --config libblas.so.3 All implementations have the same API/ABI, so user can choose system BLAS on local machine easily. And user can use proprietary BLAS library. We don't have policy for package maintainers. Most part of packages use default reference implementation, but some scientific packages are configured to use openBLAS directly: opencv, suitesparce, scipy. And only a little amount of openSUSE users know about update-alternatives configuration. Unfortunately openBLAS not so stable and contains bugs. Additionally we still have problems with AMD CPUs: https://bugzilla.opensuse.org/show_bug.cgi? id=1006743 Are there any ideas about the best solution? Do we need to use reference BLAS in all cases or maintainers can use openBLAS directly? -- 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] Leap 42.3 development finished
by Ludwig Nussel 21 Jul '17

21 Jul '17

Hi, The first stable distro fully developed with Tumbleweed rolling release technology has finished it's final build. All engines are stopped now, the project does not accept submissions anymore and goes to maintenance mode. So openSUSE Leap 42.3 is done! The final images will not be visible on download.o.o before the official release on Wednesday 26th to let the mirrors warm up. Important fixes need to be submitted via the update project¹ now. If anything needs to be fixed urgently to be available at the release day, please talk to maintenance² and thoroughly test your changes! Remaining glitches should be documented in the release notes³. Thanks everyone for your contributions and hard work to make 42.3 a great release! cu Ludwig [1] openSUSE:Leap:42.3:Update [2] set Bugzilla NEEDINFO to maintenance(a)opensuse.org [3] https://github.com/openSUSE/release-notes-openSUSE -- (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

4 4

[opensuse-factory] Tumbleweed - Review of the weeks 2017/28 & 29
by Dominique Leuenberger / DimStar 21 Jul '17

21 Jul '17

Dear Tumbleweed users and hackers, What a luck I did not get around to write the review last week - I'd have a hard time this week otherwise. As you certainly realized, we did not have a snapshot for a long time already (in fact 0712 is currently the last release). Since the last review of two weeks ago, there have been 5 snapshots released (0707, 0708, 0709, 0710 and 0712) Let's focus on what those snapshots delivered, then I'll try to give some information of why we stalled for 10 days now. * Qt 5.9.1 * libzypp: dup defaults now to --allow-no-vendor-change * wine 2.12 * Mesa 17.1.4 * NetworkManager 1.8.2 * All the nice things the YaST Team is blogging about with snapshot 0712 I was approached by SUSE internally for a small 'break', as SLE15 did not keep up with building on the linked infrastructure (mainly due to archs building slower than x86_64 does, like aarch64 and s390x). So I basically granted them the weekend until July 17, by when the internal infrastructure was indeed ready and we wanted to resume Tumbleweed snapshots. Of course, we had been working a lot on the Staging areas and were ready for quite some massive changes on Monday (for the 0717 snapshot) Among the interesting things there were: * Linux kernel 4.12 * ruby 2.4 as default, with ruby 2.2 and ruby 2.3 being removed from the repositories Turns out, one of our bots had a mistake and the removal of ruby 2.2 would have disrupted our users: the bot did not flag the removal of ruby 2.2 in the product and as a consequence, ruby 2.4 moving to be default would have conflicted with the old ruby 2.2 package. Nothing we wanted to see shipped to our users. Once the bot was fixed, we had a new snapshot coming up, 0719. The issues seen with the ruby migration were all gone, but now kernel 4.12 started to show its face: an installation running on a RAID10 setup simply started locking up. Of course, the kernel team is looking into that and as soon as a patch is ready, we will be able to ship 4.12. Until then, and to unblock Tumbleweed, we reverted back to kernel 4.11.8 (the one shipped in 0712 already). This is currently building - but I'm not yet daring to make a statement if this will be released or not. Time (and openQA) will tell. In any case, staging work is still moving along in parallel too, and we are also preparing these updates: * Mozilla Firefox 52.2.1esr * KDE Applications 17.04.3 * Libreoffice5.4.02, with google online capabilities, enabled * Linux kernel 4.12.x, that won't crash RAID10 setups If you have updates you want to see in Tumbleweed (or new packages) don't be shy, speak up and help out with the packaging work. Cheers - and have a lot of fun, Dominique

1 0

[opensuse-factory] is it me?
by James 20 Jul '17

20 Jul '17

I'm just wondering if it is me. I have not seen updates in a long time now and things are being released like the kernel 4.12 and Plasma among other things. Am I on the wrong repos? Jim -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

7 15

[opensuse-factory] Re: in-toto opensuse demo
by Marcus Hüwe 19 Jul '17

19 Jul '17

Hi, On 2017-07-17 15:53:10 -0400, Shikher Verma wrote: > I am Shikher Verma, I'm working on the in-toto project[2] under the guidance of > Professor Cappos. in-toto is a tool which provides secure auditable trail of > development. We want to integrate in-toto in Open Build Service, osc & zypper. > > I have put together a demo[1] to showcase how in-toto could be integrated with > the Open Build Service and zypper. Hmm maybe I missed something, but the demo does not really answer what you exactly want to achieve/integrate. For instance, what do you want to integrate into osc? From what I see, both, in-toto and osc, keep track of source files: do you want to "unify" this, for instance, into a single osc command? E.g., osc in-toto add <file1> <file2> ... <fileN> in order to instruct in-toto and osc to keep track of the passed files? If so, you could use osc's plugin mechanism to add custom commands to osc. However, I'm not sure if this really helps, because, if I understand in-toto correctly, you might end up with different sets of "osc in-toto" commands per "software project/layout"... (maybe it is the other way around and you actually want to integrate "osc" into "in-toto"?:) ) A conceptual question: why should an end-user (or "client" in the in-toto spec parlance) verify all the source files etc. that were used to create the package? Wouldn't it be sufficient, if she just checks if the package, which she is going to install, was signed with a known/trusted key? (The obs can be used to sign packages and the package manager usually checks the signatures before the installation). > The demo does not include making and > accepting Submit Requests since I was unable to deploy OBS in a docker > (systemd/openrc got in the way). > Hmm what would/should happen in case of a submit request? > I have already discussed this with Bernhard Wiedemann. He suggested that we > discussed with the community about how to integrating in-toto with these tools. > > You can read more about the project and take a look at the specification > on our website[2]. We are still shy of our 1.0 release, so some things > may move around a little bit. How would you guys suggest we start taking > a look at a task that seems so daunting? Marcus -- 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] Call for Review of Release Notes
by Sarah Julia Kriesch 19 Jul '17

19 Jul '17

Dear openSUSE Contributors, Our Release Day isn't far away. So we need your help. Can you check our Release Notes [1] whether all important things are listed, please? If something is missing, you can create a Pull Request on github [2] or you inform the Release Management Team about adding parts via Bugzilla and "Release Notes". Thanks for your Contributions! Let's looking forward to a successfull and last 42 release, that we can continue with 15. Best regards, Sarah [1] https://doc.opensuse.org/release-notes/x86_64/openSUSE/Leap/42.3/ [2] https://github.com/openSUSE/release-notes-openSUSE -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

5 7